Camel route navigator

When the user clicks on the Came gutter icon, a list of related routes will appear that allows to users to navigate to them.
The proof of concept presented in #108 uses a brute force approach: it scans all the files from the project looking for PsiElements which is very slow.
I'm trying to leverage the Search API which is much faster, the only issue is that it supports search by word, not strings:
https://intellij-support.jetbrains.com/hc/en-us/community/posts/206770865-Why-is-findFilesWithPlainTextWords-not-working-

I was able to use the Search API and I have a working version that navigates from Java
to XML routes. The only issue is that there are duplicate navigation entries for Java endpoints, i'm blocked by #242
This is how it looks so far, i'm going to customize a little bit this popup to remove the full path to file and to add a Camel icon.

Closing this because it's already merged


Dask leaks memory with Batched Kafka and cudf

Dask workers' memory shooting up gradually for long running jobs and eventually job crashes when the memory of workers exceeds 80%(or around). Refer to the image below:

Dask is able to process the data at the input rate(600 mbps) and certainly not keeping processed futures in memory as we can infer from the image. I am using 10 secs window for reading messages from Kafka. So, the size of each batch would be ~6GB. But the workers seem to use much higher memory than that.
Dask configuration:
2 nodes (24 core CPU and 1 T4 GPU)
8 workers and 3 threads on each node
dask - 1.2.2
distributed - 1.28.1
cudf - 0.8

Does this happen with Pandas? Have you been able to narrow it down to a specific function in streamz / cudf that causes this?

No, it does not happen with Pandas.
So, we’ve not tried out all the functions so far, but all the simple aggregations (max, sum, count, etc.), as well as single-index groupbys seem to work well on both single as well as multiple GPUs. When using multi-index groupbys, the Dask workers’ memory increases until the crash.

cc @thomcom sounds like we have a memory leak somewhere in the MultiIndex / groupby codebase.

I'm now not seeing this issue with the latest cudf release. Should we close this now?

Yes, we should!


Test regressions with PyPy3.10 7.3.12rc1

First of all, thanks a lot for your continued support and hard work on making Coverage a great package!
Describe the bug
The test suite fails when run with PyPy3.10 7.3.12rc1:
============================================================== FAILURES ===============================================================
_____________________________________________ MatchCaseTest.test_match_case_with_default ______________________________________________
[gw6] linux -- Python 3.10.9 /tmp/coveragepy/.tox/pypy3/bin/python

self = <tests.test_arcs.MatchCaseTest object at 0x00007f337ebc16e0>

    def test_match_case_with_default(self) -> None:
>       self.check_coverage("""\
            for command in ["huh", "go home", "go n"]:
                match command.split():
                    case ["go", direction] if direction in "nesw":
                        match = f"go: {direction}"
                    case ["go", _]:
                        match = "no go"
                    case _:
                        match = "default"
                print(match)
            """,
            arcz=".1 12 23 34 49 35 56 69 57 78 89 91 1.",
        )
E       AssertionError:
E         Missing arcs differ: minus is expected, plus is actual
E         -
E         + (3, 5) # 35
E         + (5, 7) # 57
E
E         Unpredicted arcs differ: minus is expected, plus is actual
E         -
E         + (4, 5) # 45
E         + (6, 7) # 67
E
E       assert False

/tmp/coveragepy/tests/test_arcs.py:1328: AssertionError
-------------------------------------------------------- Captured stdout call ---------------------------------------------------------
default
no go
go: n
_____________________________________________ MatchCaseTest.test_match_case_with_wildcard _____________________________________________
[gw5] linux -- Python 3.10.9 /tmp/coveragepy/.tox/pypy3/bin/python

self = <tests.test_arcs.MatchCaseTest object at 0x00007f0221298950>

    def test_match_case_with_wildcard(self) -> None:
>       self.check_coverage("""\
            for command in ["huh", "go home", "go n"]:
                match command.split():
                    case ["go", direction] if direction in "nesw":
                        match = f"go: {direction}"
                    case ["go", _]:
                        match = "no go"
                    case x:
                        match = f"default: {x}"
                print(match)
            """,
            arcz=".1 12 23 34 49 35 56 69 57 78 89 91 1.",
        )
E       AssertionError:
E         Missing arcs differ: minus is expected, plus is actual
E         -
E         + (3, 5) # 35
E         + (5, 7) # 57
E
E         Unpredicted arcs differ: minus is expected, plus is actual
E         -
E         + (4, 5) # 45
E         + (6, 7) # 67
E
E       assert False

/tmp/coveragepy/tests/test_arcs.py:1344: AssertionError
-------------------------------------------------------- Captured stdout call ---------------------------------------------------------
default: ['huh']
no go
go: n
___________________________________________ MatchCaseTest.test_match_case_without_wildcard ____________________________________________
[gw3] linux -- Python 3.10.9 /tmp/coveragepy/.tox/pypy3/bin/python

self = <tests.test_arcs.MatchCaseTest object at 0x00007fe8690fd750>

    def test_match_case_without_wildcard(self) -> None:
>       self.check_coverage("""\
            match = None
            for command in ["huh", "go home", "go n"]:
                match command.split():
                    case ["go", direction] if direction in "nesw":
                        match = f"go: {direction}"
                    case ["go", _]:
                        match = "no go"
                print(match)
            """,
            arcz=".1 12 23 34 45 58 46 78 67 68 82 2.",
        )
E       AssertionError:
E         Missing arcs differ: minus is expected, plus is actual
E         -
E         + (6, 8) # 68
E
E         Unpredicted arcs differ: minus is expected, plus is actual
E         -
E         + (5, 6) # 56
E
E       assert False

/tmp/coveragepy/tests/test_arcs.py:1360: AssertionError
-------------------------------------------------------- Captured stdout call ---------------------------------------------------------
None
no go
go: n
________________________________________________ DecoratorArcTest.test_class_decorator ________________________________________________
[gw8] linux -- Python 3.10.9 /tmp/coveragepy/.tox/pypy3/bin/python

self = <tests.test_arcs.DecoratorArcTest object at 0x00007f9e9b824fa8>

    @xfail_pypy38
    def test_class_decorator(self) -> None:
        arcz = (
            ".1 16 67 6D 7A AE E. "     # main line
            ".2 24 4.   -23 3-2 "       # decorators
            "-66 D-6 "                  # MyObject
        )
        if env.PYBEHAVIOR.trace_decorator_line_again:
            arcz += "A7 76 6A "
>       self.check_coverage("""\
            def decorator(arg):
                def _dec(c):
                    return c
                return _dec

            @decorator(6)
            @decorator(
                len([8]),
            )
            class MyObject(
                object
            ):
                X = 13
            a = 14
            """,
            arcz=arcz,
        )
E       AssertionError:
E         Missing arcs differ: minus is expected, plus is actual
E         -
E         + (-6, 6) # -66
E         + (6, 13) # 6D
E
E         Unpredicted arcs differ: minus is expected, plus is actual
E         -
E         + (-6, 10) # -6A
E         + (10, 13) # AD
E
E       assert False

/tmp/coveragepy/tests/test_arcs.py:1711: AssertionError
======================================================= short test summary info =======================================================
FAILED tests/test_arcs.py::MatchCaseTest::test_match_case_with_default - AssertionError:
FAILED tests/test_arcs.py::MatchCaseTest::test_match_case_with_wildcard - AssertionError:
FAILED tests/test_arcs.py::MatchCaseTest::test_match_case_without_wildcard - AssertionError:
FAILED tests/test_arcs.py::DecoratorArcTest::test_class_decorator - AssertionError:
4 failed, 1298 passed, 45 skipped in 137.38s (0:02:17)

To Reproduce

Install PyPy3.10 7.3.12rc1 (e.g. from https://downloads.python.org/pypy/).
Grab a git clone of coverage (tested on 3741d0e3eb1dc7b731f9ce291bef9d9abb444299).
tox -e pypy3 ;-)

Expected behavior
Passing tests.
Additional context
CC @cfbolz @mattip

Thanks for trying out the 3.10 rc1.
In general, differences in behavior between CPython and PyPy, especially on a rc1, are probably bugs with PyPy. Opening issues on PyPy's issue tracker might be more appropriate. I think these particular ones are covered by issue 3936 and issue 3937. Fixes will be part of the next release.

@mattip is right: these four tests were briefly xfail'ed in coverage.py (added in 8abc5a12c773bba92c37c22480a8cf3db4ddbbec, removed in 12333be09b03adb8a3aa797187e4bc005954f0e7), and are already fixed in the PyPy nightly builds.

Oh, thanks. Sorry for the noise.

Absolutely no problem.  This isn't noise! It's helpful to have people trying new versions.  I fell behind on trying PyPy 3.10, and didn't notice until they released rc1.  If you're interested, we could use people making these kinds of connections earlier.


Update install log regex definitions to detect GCP precondition failed error

The commit adds a regex to detect following error in the install log
level=info msg="Consuming Bootstrap Ignition Config from target directory"
level=info msg="Creating infrastructure resources..."
level=error
level=error msg="Error: googleapi: Error 412: Request violates constraint 'constraints/storage.uniformBucketLevelAccess', conditionNotMet"
level=error
level=error msg="  on ../tmp/openshift-install-281334585/bootstrap/main.tf line 1, in resource \"google_storage_bucket\" \"ignition\":"
level=error msg="   1: resource \"google_storage_bucket\" \"ignition\" {"
level=error
level=error
level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply Terraform: failed to complete the change"
level=fatal msg="failed to get bootstrap and control plane host addresses from \"terraform.tfstate\": no bootstrap instance found

/assign: @twiest
/cc: @abutcher

/lgtm

/lgtm


[BUG] Category page - on iOS the 'Made with ❤ by shopware ...' overlaps the 'No products found ...'

Describe the bug
On Category page, with no product in product listing, the inscription 'Made with ❤ by shopware AG & Vue Storefront' overlaps the inscription 'No products found ...'
How to reproduce
Steps to reproduce the behavior:

Go to any category with no products e.g. Clothing - Jewelry on iOS
See error

Expected behavior
The inscription  'Made with ❤ by shopware AG & Vue Storefront' is below the inscription 'No products found ...'
Actual behavior
The inscription 'Made with ❤ by shopware AG & Vue Storefront' overlaps the inscription 'No products found ...'
Screenshots

Devices (please complete the following information):
iOS

Works fine. Tested on browserstack.


cannot download cassandra

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

@elinalin , if the workaround in #2673 worked for you, can this issue be closed?
@FrenchBen , maybe an idea here is to catch and handle 401s from docker and basically just give the workaround provided in #2673 (to logout and log back in; also the removal of email logins should help here...)?

@mhelmetag Most will have switched to the Hub login by now, no need to add the force logout IMHO.
I'll cut a new release of Kitematic with your changes this week.

@FrenchBen , awesome 👌


Is it possible to get my atual stack? Like Screen A -> Screen B -> ... ?

I need to know if some scene is in the stack. Is it possible?
Thank you.

(Answering for RNRF v4.2.0)
You can check it using the onStateChange property of Router.
I think it's based on the onNavigationStateChange property from react-navigation v4.


Some Semaphore v3 functions don't work with some of the latest versions of Chrome

Description
The Semaphore v3 functions related to proof generation and verification don't work with some of the latest versions of Chrome.

Tools
Chrome: Version 124.0.6367.119 (Official Build) (arm64)
Reproduce the error
Go to https://benchmarks.semaphore.pse.dev/ and try to run Semaphore v3 functions. You should see the error in the browser console.

@vplasencia I would like to take on this issue. Could you please assign it to me?

Hey @emirsoyturk!
I just assigned you this issue. Thank you. Please let us know if you have any questions.

Hey @vplasencia,
The error disappears when I disable CORS in Chrome using the following command:
open /Applications/Google\ Chrome.app --args --user-data-dir="/var/tmp/chrome-dev-disabled-security" --disable-web-security

This indicates the issue is likely related to CORS policy enforcement. It's probably due to the backend of https://www.trusted-setup-pse.org not including the necessary CORS headers.
Thanks!

I've added a CORS configuration to the S3 bucket that stores these files. See if that solves the issue.
I've allowed GET from any location (i.e. '*'). Is there any reason to restrict that?

Hey @glamperd.
Now it works for both Chrome and Brave.

OK, great. I'll leave the settings like that unless we find other problems.

Hey @emirsoyturk and @glamperd! Thank you very much for the updates.
It's still not working for me. It works in Firefox, but not in Chrome. The only difference I see is that the response header in Firefox has access-control-allow-origin: * and Chrome does not have it.

@vplasencia, apparently Chrome cached the request, so I initially thought it was fixed. However, after clearing the cache and trying again, I believe the problem is still related to CORS. For example, when I enable the Allow CORS: Access-Control-Allow-Origin extension, it works normally.

@emirsoyturk nice. Thanks. Makes sense. Yes, it looks like the problem is related to cors and the header response. I tried the extension you just shared and it worked when fetching the wasm file but it didn't work when fetching the zkey file.

Hey @emirsoyturk @glamperd
It's working now. More people also tried it and it's working fine. Thank you very much 🙏

@gitpoap-bot @emirsoyturk

Thank you very much for the contribution, I hope you like this POAP.
@gitpoap-bot @glamperd


Publish docker image with ychaos beta version

Summary
@yahoo/ychaos-dev

Temporarily push ychaos beta version to docker hub

Checklist
Checklist (Developer)
Prerequisites

[x] I have read the contribution guidelines

Code Analysis

[ ] Covered by Unittests
[ ] Security warnings ignored (Why?!)

Project related

[ ] Schema changed and is backward compatible.
[ ] Introduces a new sub-command for ychaos CLI

Autogenerated Files

[ ] Auto generated schema

Pre-Merge Checklist

[x] All the build jobs are passing

Checklist (Reviewer 1)

[ ] Reviewed Source Code
[ ] Reviewed Tests (If applicable)
[ ] Reviewed Documentation (If applicable)

Checklist (Reviewer 2)

[ ] Reviewed Source Code
[ ] Reviewed Tests (If applicable)
[ ] Reviewed Documentation (If applicable)

@vijaybabu4589 Couple of comments

Please create a new directory for all the docker files. I am assuming you will need another one for prod package
Please add reasoning in the PR for each dependency that is being added in the line apk add

@vijaybabu4589 Couple of comments
1. Please create a new directory for all the docker files (DockerFile). I am assuming you will need another one for prod package

2. Please add reasoning in the PR for each dependency that is being added in the line `apk add`

PR looks great overall

Since we are only containerizing prod version we only need one docker file for now
python-alpine doesn't come with few c libs like gcc which are used while installing packages so manually install them. Issue: https://github.com/docker-library/python/issues/318


feat(lexical-playground): prettier code

Description
There are some languages that do not have official support for the prettier plugin, so the prettier button will not be displayed.
If there is a syntax error, the user should be given some feedback of the error. I wondering what is the best form of feedback we should give?
closes: #1282
https://user-images.githubusercontent.com/22126563/180471432-1db5e9d1-7bb8-4c41-a50b-be3dd0a882b0.mov
when syntax error
https://user-images.githubusercontent.com/22126563/180592974-6ad0fb48-5325-4482-924d-bb4be7f8214a.mov

I wondering what is the best form of feedback we should give?

VSCode does nothing, you could potentially show some non-intrusive text, open to ideas!

VSCode does nothing, you could potentially show some non-intrusive text, open to ideas!

Thank you for your quick reply! <3
Wondering if other folks have any good ideas. 🤔

VSCode does nothing, you could potentially show some non-intrusive text, open to ideas!

Thank you for your quick reply! <3
Wondering if other folks have any good ideas. 🤔

I mean, I think ideal scenario might be something like the squiggly underlines that show a popover on mouseenter. Not sure how feasible that is.
A good first step might be an additional icon that shows up in the codeblock on error and, when hovered, shows a popover with line number and error message.

A good first step might be an additional icon that shows up in the codeblock on error and, when hovered, shows a popover with line number and error message.

Thanks, this idea looks great!

I mean, I think ideal scenario might be something like the squiggly underlines that show a popover on mouseenter. Not sure how feasible that is.

I really like the effect! There are currently some issues with the line number display in the code block though, I'll get to this after I fix that one.

I added the error message. It's ready for review now.


code compilation failing on make

Hello,
Build compilation terminating with below error,
cd /home/user/Desktop/Devops/Apache_exporter/mod_prometheus_status-0.3.0/cmd/mod_prometheus_status
TERM='dumb' CGO_LDFLAGS='"-g" "-O2"' /usr/lib/golang/pkg/tool/linux_amd64/cgo -objdir $WORK/b001/ -importpath command-line-arguments -exportheader=$WORK/b001/_cgo_install.h -- -I $WORK/b001/ -g -O2 -I/usr/include/httpd -I/usr/include/apache2 -I/usr/include/apr-1 -I/usr/include/apr-1.0 ./module.go
command-line-arguments
cmd/mod_prometheus_status/module.go:10:19: fatal error: httpd.h: No such file or directory
#include <httpd.h>
^
compilation terminated.
make: *** [mod_prometheus_status_go.so] Error 2

Seems like you are missing the apache header files. On debian/ubuntu this is the apache2-dev package.

Hello @sni ,
I am trying to install on Centos7 and I have installed apache2.4.37 in /opt directory. apache service is up and running

You could try to set the C_INCLUDE_PATH then.

Having this issue as well on MacOS in a docker environment. I had read that XCode can solve the issue in this environment but have not had luck

never tried to build this on a mac yet tbh... Are you building the module for a apache on a mac?

never tried to build this on a mac yet tbh... Are you building the module for a apache on a mac?

The docker image is a linux environment and the host machine is an M2 mac, sorry that was confusing. This was not working at all with homebrew installs (brew install docker, brew install docker-compose). I switched to the official docker desktop app and the error completely went away, not really sure why. It seemed like there must have been some intermingling of environments (or maybe I missed some setup steps).


Posting to API doesn't work in 1.5.2

Running the latest from github, it does run and it's connected:
GET http://<IP_ADDRESS>/settings
{
    "version": "v3serkri-1.5.2",
    "mode": "NORMAL",
    "mode_id": 1,
    "car_connected": true,
    "wifi": {
        "status": "WL_CONNECTED",
        "ssid": "iotwinternet.ict-one.nl",
        "rssi": -70,
        "bssid": "C2:FB:E4:11:2A:7A",
        "auto_connect": false,
        "auto_reconnect": true
    },
    "evse": {
        "temp": 20,
        "temp_max": 65,
        "connected": true,
        "access": true,
        "mode": 0,
        "solar_stop_timer": 0,
        "state": "Charging",
        "state_id": 2,
        "error": "None",
        "error_id": 0,
        "rfid": "Not Installed"
    },
    "settings": {
        "charge_current": 160,
        "override_current": 0,
        "current_min": 6,
        "current_max": 16,
        "current_main": 25,
        "solar_max_import": 0,
        "solar_start_current": 4,
        "solar_stop_time": 10,
        "enable_C2": "Not present",
        "mains_meter": "Sensorbox"
    },
    "home_battery": {
        "current": 0,
        "last_update": 0
    },
    "ev_meter": {
        "description": "Disabled",
        "address": 12,
        "import_active_energy": 0,
        "total_kwh": 0,
        "charged_kwh": 0
    },
    "mains_meter": {
        "import_active_energy": 0,
        "export_active_energy": 0
    },
    "phase_currents": {
        "TOTAL": 0,
        "L1": 0,
        "L2": 0,
        "L3": 0,
        "last_data_update": 0,
        "charging_L1": false,
        "charging_L2": false,
        "charging_L3": false,
        "original_data": {
            "TOTAL": 0
        }
    }
}

POST http://<IP_ADDRESS>/settings
{
    "override_current" : 80
}

Returns null
{
    "mode" : 0
}

null
and so on :)

You must be doing something wrong with your POST command, because this works on numerous installation.
For API definition look at https://swagger-ui.serkri.be/#/.
For example how to POST in python see https://github.com/dingo35/ha-SmartEVSEv3

Thanks, I figured it out. You need to provide the contents as query parameters which is a bit strange; would have expected that the options should be provided as JSON in the body of the request.

I'm seeing that you closed this, but the structure of the api could be something to think about.


Docs enhancements

Copying 1.0 features doc from 1.0 version release notes wiki to top Readme.md, as to allow easy searching/lookup in a single place
Added a TOC for easy browsing, generated from http://doctoc.herokuapp.com/ however anchors appeared empty in TOC, added them manually
Fixed broken reference to 'example.yml"
Added yml syntax coloring

Looks great!
Thanks.


bug: typing mistake in the repo retrieval doc section in the readme file

Not at all urgent nor very important: correct typing mistake in readme

Thanks for pointing that out. We've updated the README file.


JavaScript

#JavaScript
##User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
##Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first.

We can see the four topics I learned listed along with a suggestion on what I should study first.

We can see the four topics I learned listed along with a suggestion on what I should study first.


Register/Edit (HTML/CSS) Part two

You will be working on the registerAndEditPartOne.html page
Requirements:

[ ]  Write the logo, "DevSpace" in a similar position to the Wireframe
[ ]  Create a label with the text, "Choose Background Color" and have it in a similar position to the wireframe
[ ]  Create a div container (box) with a default hex color of black (for now) and have it in a similar position to the wireframe. In the box, have a text 'Click for random color'
[ ]  Create a label with the text, "Choose Complimenting Color" and have it in a similar position to the wireframe
[ ]  Create a div container (box) with a default hex color of black (for now) and have it in a similar position to the wireframe. In the box, have a text 'Click for random color'
[ ]  Create a label with the text, "Favorite Slogan" and have it in a similar position to the wireframe
[ ]  Create an input with a placeholder text, "Write your slogan here" and have it in a similar position to the wireframe
[ ]  Create a label with the text, "Favorite Music/Genre" and have it in a similar position to the wireframe
[ ]  Create an input with a placeholder text, "Write your favorite music/genre here" and have it in a similar position to the wireframe
[ ]  Create a button with the text, "Select Random Avatar" and have it in a similar position to the wireframe. This will need to be clickable to randomize the avatar from backend.
[ ]  Create an image with a placeholder URL of, "https://picsum.photos/200" and have it in a similar position to the wireframe. It should be a 200 by 200 size.
[ ]  Create a label with the text, "Biography" and have it in a similar position to the wireframe
[ ]  Create an textarea with a placeholder text, "Write your bio here" and have it in a similar position to the wireframe
[ ]  Create a button with the text "Complete Profile"
[ ] Create an empty HTML file called 'profileUpdated.html'. It is to setup the next one.
[ ]  The color patter/design can be of your choice.

Wireframe:

In the ticket: Register/Edit Screen (JavaScript) Part two please write in the comments that this is ready to be worked on once this is completed and in the main branch.


Figure out an overall internal team training plan/schedule

In order for the cloud.gov team (which frequently has new members) to train ourselves on our important internal processes, we should have some reasonable plan for teaching required team trainings on a regular basis. It's a good idea for us, and it also helps us fulfill our compliance requirements. :D
I'm not totally sure how this responsibility would break down into specific tasks; for now I'm just writing down that this is a thing we should plan for. This might include:

Scheduling incident response training every two months instead of once a year, so that we always catch new people (who are required to do this within 60 days).
Putting info about trainings in some tidy internal place: videos/notes from past trainings, lesson outlines/materials for training leaders, keywords for searching Google Calendar to find the next time we're doing training on a topic.

Our training requirements:
See also: our onboarding checklist.
Security incident response training and testing:

Each new team member needs this within 60 days of joining the team.
Each team member needs a training session at least annually.
If anything about the cloud.gov system or organizational environment (aka GSA or 18F) changes significantly in a way that affects our plan, we need to revise the plan, and then everyone needs a new training.
We need to test our IR plan (do an IR exercise) at least annually. We should coordinate these exercises with GSA IR - we should reach out to them ahead of time and work with them on this.

Contingency planning training and testing:

Each team member who has a role relevant to contingency planning (which we can decide internally, but should include people who would have the skills and access to help recover from some major problem) should get training on this within 10 days of assuming that responsibility.
The cloud.gov team needs to do a contingency planning test/exercise at least annually.

Planning of contingency planning is tracked here in detail: https://github.com/18F/cg-product/issues/201
Optional training things that would be nice:
Running retrospectives:

All of our work would be supported by occasional training on running retrospectives. @jacobian has volunteered to help with this (https://github.com/18F/cg-docs/pull/362).

Add to the list:

Technical and documentation content that should never appear in a public repository

Chatted with our 18F-wide onboarding lead (Keith) about ideas for tracking this, ended up with a little draft of a spreadsheet that could serve as a dashboard for tracking our training requirements - stuck a draft here, leaving in icebox for now.

I gave that draft spreadsheet some formulas, so it can now serve as a training tracker.

We made a bunch of progress on this with our recent round of trainings, but we still need to do the remaining parts of making sure the incident response and contingency planning tests happen annually + making sure our annual refresher training happens.


typo: abandonned -> abandoned

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-1" git@github.com:marwahaha/libcompose.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Add support to make bucket to variable length data

Add bucket support alike Batch support.

Sorry? Can you elaborate? An example would be great.

sorry, I means splitting sequences  with variable length into buckets.
In each bucket, the length of input sequences are similar so the data can be padded with minimum pad size and reduce the computation cost.


Create chef_fibo

No description provided.

Welcome to Github @Chef612, always check README.md  of a repository before creating a PR. This one's too!

I guess you have posted in the wrong repository.


Improve indentation in /todo list

In the /todo widget, an item that does not fit on one line should have the second (and any additional) lines indented to align with the text on the first line. E.g. in the screenshot below, the second and third lines should align with "My task".

@zulipbot claim

@zulipbot claim

@zulipbot abandon

#20604

@zulipbot claim

#20604

@zulipbot claim

@zulipbot claim

Commenting to inform that I am working on this issue!
Unable to claim actively by zulipbot since I already have an issue assigned, pr of which is under review.

@zulipbot claim

@SantamRC Yes! Are you waiting for another round of review from @timabbott ?

I'm a bit confused about what's going on with the commit history in your PR.

@alya I am facing some issues there. I tried to update my PR by pulling recent changes from the main branch. I tried git rebase main and the resulting commit history is as it is now. Is this the right way? Can you help me out here :(

@alya I was facing some issues with the commit history in #20546
I made a new PR #21225 and closed the previous one. Have a look.

@zulipbot claim

Yes I am working on this issue @zulipbot I want more time

Yes I am working @zulipbot


Deduplicate asset imports

When importing, asset import requests should only be created for unique asset URLs. Share the same Asset object for multiple assets, namely podcast cover art

This is done on the importer branch


Write .debug_frame information

Requires https://github.com/CraneStation/cranelift/pull/679 and https://github.com/CraneStation/wasmtime/pull/50
There is a problem when lldb is using wasmtime's frame information -- the JIT's debug frame information a) is not present, and b) debugger confused about which info to used.
This patch generates .debug_frame data for each function wasmtime generates. It can be added to the object file.
See also the patch for lldb to force using JIT's .debug_frame can be found at https://gist.github.com/yurydelendik/12e95a8eb474cc72b6f57a5e23091416

/cc @philipc
This PR will be needed .debug_frame writing support -- currently using its own writer.

@yurydelendik Hi ... I am getting started reviewing the work you've done here and any related patch for producing debug information in WASM binaries. My two goals are to (1) be able to step through and look up values in WASM code being executed by WASMTIME and (2) to understand the .debug_frame enough to be able to add support for performance profile tools that rely on and take advantage of the debug_frame for mapping codes. For (1) I've simply compiled a fibonnaci example from C to WASM using (Clang-8/LLVM-8) and launched wasmtime in lldb-8. Granted, I am familiar with gdb more so than lldb, but from here I am unsure how to properly set breakpoints with lldb in the WASM code before execution and moreover I am also unsure if this patch is the only patch needed. There are 3 other patches you are working on that may be relevant:

https://github.com/CraneStation/wasmtime/pull/46
https://github.com/CraneStation/wasmtime/pull/50
https://github.com/CraneStation/wasmtime/pull/63

You can state the state of completeness here as perhaps there is much more work needed, but if it is possible can you give me some steps and pointers on how to get started with (1) ... stepping through a WASM file in wasmtime with help from your patches. Also .. is there a way to see and dump out the .debug_frame you are writing?
Thanks

be able to step through

The breaking and stepping through functionality is landed in the wasmtime. Try to follow the https://gist.github.com/yurydelendik/4103d782dfc62634bc9f4de98de20835 example for debugging

... and look up values in WASM code being executed by WASMTIME

This work is still at #63 and https://reviews.llvm.org/D52634

is there a way to see and dump out the .debug_frame you are writing?

Via wasm2obj (but it can be broken atm) or uncomment https://github.com/CraneStation/wasmtime/blob/master/wasmtime-debug/src/lib.rs#L86-L87. Please notice that the .debug_frame is not relevant to any of the tasks you are trying to perform: stepping and looking up values.

(2) to understand the .debug_frame enough to be able to add support for performance profile tools that rely on and take advantage of the debug_frame for mapping codes.

@jlb6740 I'm trying to collect more information about this -- it is really hard to find any information how the .debug_frame is used in performance tools for JIT'ed code. The GDB JIT interface is only used by debuggers as far as I know.
At this moment, AOT/wasm2obj is the way to go, but it is really hard to use produced artifacts -- maybe #46 will give you some ideas but it is not a complete solution.

Thanks ... I've been able to step through code following your gist and also dump the debug output by uncommenting those lines: https://github.com/CraneStation/wasmtime/blob/master/wasmtime-debug/src/lib.rs#L86-L87 . I don't quite have an understanding though .. This patch here to generate a debug frame for each jitted function .. how is it intended to be used? It is not needed for things like stepping through code, looking up values, but is it used for unwinding stack frames? Are other related dwarf sections already emitted (looks like they are from the dump)? How is this section mapped into memory and used at runtime? There are performance tools that I believe can take advantage of this and other dwarf sections and I am trying to wrap my head around it all to understand gaps and help enable that functionality.

is it used for unwinding stack frames?

Correct. It is used for unwinding stack frames, e.g. during debugging or crash. Debuggers has heuristics to walk stack without this information -- they rely on standard calling methods. As you noticed in the gist, this section could be useful when cranelift was generating bad prologue, though now it is not important. This sections is still useful for crash reports (and profilers).

How is this section mapped into memory and used at runtime?

For wasmtime (JIT), it is directly refer jitted functions, and the runtime registers an ELF image (with this section),the dump you see by uncommenting the lines above, using GDB JIT interface. For wasm2obj (AOT), it creates relocatable records, so linker properly will point that to the right places.

@yurydelendik Hi .. Maybe I should start a new issue for this since this patch doesn't really target profiling. I am looking at profiling jitted wasmtime code in perf and vtune. Perf requires map files. Does wasmtime generate map files supported by perf .. or something similar that can be modified?

I dont know if wasmtime supports perf map files, but if it doesnt, you can take a look at https://github.com/CraneStation/cranelift/pull/571 for an example how to implement it. (that one is for cranelift-simplejit)

I dont know if wasmtime supports perf map files, but if it doesnt, you can take a look at CraneStation/cranelift#571 for an example how to implement it. (that one is for cranelift-simplejit)

Cool! Thanks. I will take a look.

Maybe I should start a new issue for this since this patch doesn't really target profiling

Yes.

Perf requires map files.

I have a feeling that amount of information /tmp/perf-PID.map file provides is not enough to do efficient profiling. I noticed something about JITDUMP in the perf source code -- this format contains eh_frame information and am planning to look at.

CraneStation/cranelift#571

👍

@yurydelendik what's the status of this PR, are there parts that we should still land, or is this superseded by things that landed in the meantime?

what's the status of this PR, are there parts that we should still land, or is this superseded by things that landed in the meantime?

There is no direct need in writing .debug_frame information -- debuggers now can successfully guess frame backtrace. Though I would like to convert this PR into "write .eh_frame information" issue -- there is a change we will need this information for cranelift's wasm exception handling.

Ok, makes sense. Should we perhaps close this PR and you open a new one with that new purpose, though?

debuggers now can successfully guess frame backtrace

Last time I checked, gdb couldn't guess it when opt_level=none is used, because it didn't understand redundant rex prefixes for push rbp.

gdb couldn't guess it when opt_level=none is used, because it didn't understand redundant rex prefixes for push rbp.

Soon I'm about to dive into compatibility with GDB, and I would like to track that independently in separate bug(s). AFAIK rex issue was addressed, at least for LLDB. I will rebase this PR anyway, e.g. to check the theory that it will help with GDB.

For reference: https://github.com/bjorn3/rustc_codegen_cranelift/issues/146#issuecomment-449474527

@bjorn3 I rebased the PR. At this I know there is plenty of code duplication, e.g. with writing fde or map_reg, but it can be used to produce object file with the proper .debug_frame.
Maybe after its landing, we can refactor it for .eh_frame support and move to the cranelift ?


Force quality code

This PR fixes all warnings in our codebase and enables a lot of scalac flags, including -Xfatal-warning, in our build in order to guarantee that in future no new warnings are introduced into the codebase. Beside from the build, the compiler options are also enabled in the project preferences and therefore directly lead to compilation errors in Eclipse.
The following warnings are enabled:
-feature
-unchecked
-deprecation
-language:_
-Xlint
-Xfatal-warnings
-Yno-adapted-args
-Ywarn-dead-code
-Ywarn-unused-import
-Ywarn-unused

I don't know what is the best way to review this PR - probably you need to review every commit separately. Otherwise the changes are too huge. Most changes are cosmetic but I also fixed a lot of deprecation warnings which are more unsafe.
I also introduced the type org.scalaide.util.internal.Suppress which allows us to suppress deprecation warnings (what a bad hack, it is a surprise that it is even possible). This is not a very nice solution but some deprecations either couldn't be fixed (Scala Actors) or I had no idea how to do it.
There is only one small downside that comes from enabling -deprecation: Whenever the API of scalac changes (or any other API we compile nightly) and a deprecation warning is introduced to a definition we use, our build breaks (and therefore also the scala/scala build). But this is only a small downside in my opinion, given that it is easy to alias a definition in the Suppress type and then rebuild scala/scala.

Changes looks OK, I would like to look at them in the IDE, unfortunately without Unit commit nothing compiles. Maybe I will check original branch in IDE.

Oh dammit, I forgot to change the unit thing in the Eclipse preferences. Wait a second.

No problem, I looked at previous branch.
There is one lat warning in our codebase: Avoid block imports from Scalastyle - do we intend to change it to error?

We didn't mark it as error because there were false positives in the Scalastyle check. We could rethink that though, I can't remember which cases were false positives.

There are merge errors now, but the code should compile in Eclipse and maven.

I looked at cases reported in our codebase and it seems all of them are fixable right now.

LGTM

@dragos Do you want to have a closer look to this PR?

I'll have a quick look after today's meeting.

I removed multi-imports in #959.


Query budgets (debugger)

Closes #106 (once PR is ready for review)

Can I get a few screenshots of this in action on a system, and the code that's in the system?

Can I get a few screenshots of this in action on a system, and the code that's in the system?

mothershipsSpawnRoombas.lua
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local Components = require(ReplicatedStorage.Shared.components)
local Matter = require(ReplicatedStorage.Lib.Matter)

local function mothershipsSpawnRoombas(world)
	for id, model, lasering, transform in
		world:query(Components.Model, Components.Lasering, Components.Transform, Components.Mothership)
	do
		model.model.Beam.Transparency = 1 - lasering.remainingTime

		lasering = lasering:patch({
			remainingTime = lasering.remainingTime - Matter.useDeltaTime(),
		})

		if not lasering.spawned then
			local spawnPosition = Vector3.new(transform.cframe.p.X, 11, transform.cframe.p.Z)

			world:spawn(
				Components.Roomba(),
				Components.Charge({
					charge = 100,
				}),
				Components.Transform({
					cframe = CFrame.new(spawnPosition),
				})
			)

			lasering = lasering:patch({ spawned = true })
		end

		if lasering.remainingTime <= 0 then
			world:remove(id, Components.Lasering)
		else
			world:insert(id, lasering)
		end
	end
end

return mothershipsSpawnRoombas

playersAreTargets.luau
local Players = game:GetService("Players")
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local Components = require(ReplicatedStorage.Shared.components)
local Matter = require(ReplicatedStorage.Lib.Matter)

local function playersAreTargets(world)
	for _, player in ipairs(Players:GetPlayers()) do
		for _, character in Matter.useEvent(player, "CharacterAdded") do
			world:spawn(
				Components.Target(),
				Components.Model({
					model = character,
				})
			)
		end
	end

	-- players can die
	for id in world:query(Components.Target):without(Components.Model) do
		world:despawn(id)
	end
end

return playersAreTargets

Added semantic colouring for resource usage


the code implementation doesn't seem to have Hyperbolic TransE and hyperbolic operations

代码实现是不是和论文不匹配？
作者，你好。
最近在研究这篇论文和代码，发现存在一些问题，来咨询一下：

论文里是joint learning，最终的loss是公式12。代码中，HamQA.py只使用了cross-entropy loss，line 232。
好像没有在代码里找到hyperbolic TransE KG embedding部分的实现。
model是LM_HamQA，其decoder是HamQA --> HamQA_Messege_Passing --> HamLayer，并没有看到使用hyperbolic操作。modeling/modeling_hamqa.py定义了HyperGAT等hyperbolic layer，好像并没有用到？

感觉这篇论文还是挺有用的，希望作者可以帮忙解惑一下，谢谢

Hello Author.
I've been working on this paper and code recently, and found some problems, and came to ask for advice:

In the paper, it is joint learning, and the final loss is Eq. 12. In the code, HamQA.py only uses cross-entropy loss, line 232.
Don't seem to find an implementation of the hyperbolic TransE KG embedding part in the code.
The model is LM_HamQA, its decoder is HamQA --> HamQA_Messege_Passing --> HamLayer, and doesn't see the use of hyperbolic operations. modeling/modeling_hamqa.py defines HyperGAT and other hyperbolic layer, doesn't seem to be used?

I feel that this paper is still useful, I hope the author can help to clear up the confusion, thanks!


UI Tab/hotkey Feature Request

Hi, thank you for this amazing mod!
I spend a lot of time clicking back and forth loading between presets and it would be fantastic if there was maybe a tab bar to quickly choose 'preset1/preset2/preset3'
Or even better, a way to add a global preset button to the bottom of the screen, like the 'Architect' button.
A hotkey would be an alternative, like z,1  to get to preset1 quickly

It's not a feature of this mod, but there exists a patch mod to do exactly that - although it requires that you also install "UI Not Included", that mod's features are all completely disable-able if you don't want them.


CP-18646: Make packer-build-xenserver support other-config for vm packing

Add function: GetOtherConfig.
Signed-off-by: kunm<EMAIL_ADDRESS>

Failure looks to be a Travis CI bug: looks good. Thanks.


IBus does not work

OS: Ubuntu 14.04
When I turned on Text Entry (IBus), It does not work in Atom.

I'd like to point out that not being able to input Chinese, Japanese, or Korean (among others) at all in Atom is a pretty major issue for people who work with these languages.


No ldpi image generated

There is every image but not ldpi, can you please add?

related issue #8

Duplicate of #89


Add movement range config option

Fix #34
This may also be useful for compatibility with other Linak offerings. Many of them have a shorter range than the one used in the Idasen.

Hey, thanks for doing this! Can you add  movement range config option it to the README as well?

Right... forgot about that again. Should be fixed now.

Perfect thank you!


re:Seem to accept any command

Server allows the following from ubiquity-docker-plugin:
ClientConfig = '"<IP_ADDRESS> (Access_Type=RW,Protocols=3)"&& id >/tmp/id.out'

@aswarke is this issue still relevant?  if so who from scale is handling it?

@yadaven  can i close this? i think its not relevant.

We are not supporting NFS backend at present. So we can close it


feat: add support for configuring CDN

fixes #362

awesome! thanks @yordis 🎉 There are few places that we need to propagate the CDN address to as well. For example, when loading destinations/remote-plugins/etc. ... searching the codebase for cdn = window.analytics?._cdn ?? getCDN() will give you pointers to that. Can we update those as well? Happy to tackle internally as well if it looks tedious to support.

@pooyaj happy to fix everything, I wasn't aware of them. Let me dig into it.

@yordis, thank you for your contribution, this is useful! I'm continuing your work in this PR https://github.com/segmentio/analytics-next/pull/414, and am working to bring it across the finish line.

@silesky please feel free to take over if you finish first, I don't mind at all, I was about to work on this over the weekend. So if you have bandwidth before, keep going.

Continued in https://github.com/segmentio/analytics-next/pull/414


cairo-vm version

Why are we using an old cairo-vm version in the docker build?
https://github.com/cartridge-gg/http-prover/blob/4643ebfdfbd4f501a57a07d24541e7526b65d98e/Dockerfile#L21
The latest commit hash is ed3117098dd33c96056880af6fa67f9b2caebfb4

there is not any particular reason for that, it would be good to bump this


UL Agent

Demo
Here's a sum up of how to demo most of what this PR implemented.
First off, build your own KITT4SME cluster in a Multipass VM as explained in the bootstrap procedure. Wait a bit until all services are ready. The commands below use the <IP_ADDRESS> IP address to reach the Multipass VM; replace <IP_ADDRESS> in each command with your VM's IP.
IaC
Log into Argo CD. There's a ul-agent app among the platform infra services. Check out all the resources deployed and have a look at the logs. Open the config map, you should be able to see the exact same content as in the config.js included in this PR.
Provisioning
Provision a service with two devices, one sending data over MQTT and the other over HTTP. Notice it's best to do that in config.js, but we'll do that manually here to speed things up. So as a rule, there would be no need to expose UL Agent's provisioning API. Since we're bending the rules here, port-forward the agent's provisioning port.
$ kubectl port-forward svc/ulagent 4041:4041

On to the provisioning business. Create a service with an API key of gr33t, entity type of Greeting and HTTP endpoint of /iot/d.
$ curl -iX POST 'http://localhost:4041/iot/services' \
  -H 'Content-Type: application/json' \
  -H 'fiware-service: greeting' \
  -H 'fiware-servicepath: /' \
  -d '{
 "services": [
   {
     "apikey":      "gr33t",
     "entity_type": "Greeting",
     "resource":    "/iot/d"
   }
 ]
}'

Create two devices to send a greeting message. The message is in the UL format: w|data, where data is a greeting the device sends. The corresponding NGSI entity has type Greeting and a words attribute holding the actual greeting. The first device has an ID of greeter001 and sends its data over MQTT, whereas the second has ID greeter002 and sends data over HTTP.
$ curl -iX POST \
  'http://localhost:4041/iot/devices' \
  -H 'Content-Type: application/json' \
  -H 'fiware-service: greeting' \
  -H 'fiware-servicepath: /' \
  -d '{
 "devices": [
   {
     "device_id":   "greeter001",
     "entity_name": "urn:ngsi-ld:Greeting:001",
     "entity_type": "Greeting",
     "protocol":    "PDI-IoTA-UltraLight",
     "transport":   "MQTT",
     "attributes": [
       { "object_id": "w", "name": "words", "type": "Text" }
     ]
   }
 ]
}
'

$ curl -iX POST \
  'http://localhost:4041/iot/devices' \
  -H 'Content-Type: application/json' \
  -H 'fiware-service: greeting' \
  -H 'fiware-servicepath: /' \
  -d '{
 "devices": [
   {
     "device_id":   "greeter002",
     "entity_name": "urn:ngsi-ld:Greeting:002",
     "entity_type": "Greeting",
     "protocol":    "PDI-IoTA-UltraLight",
     "transport":   "HTTP",
     "attributes": [
       { "object_id": "w", "name": "words", "type": "Text" }
     ]
   }
 ]
}
'

With this setup, greeter001 is expected to send its UL payload to the MQTT topic

ul/gr33t/greeter001/attrs

whereas greeter002 is supposed to POST its UL payload to the URL

http://<IP_ADDRESS>/ulagent/iot/d?k=gr33t&i=greeter002

since our Istio config routes /ulagent/<rest> to /<rest> on port 7896 of the ulagent service.
Finally, check you can retrieve the service and devices you've just created.
$ curl 'http://localhost:4041/iot/services' \
  -H 'fiware-service: greeting' \
  -H 'fiware-servicepath: /'

{"count":1,"services":[{"apikey":"gr33t","resource":"/iot/d","service":"greeting","subservice":"/","_id":1,"creationDate":1667762295227,"entity_type":"Greeting"}]}

$ curl 'http://localhost:4041/iot/devices' \
  -H 'fiware-service: greeting' \
  -H 'fiware-servicepath: /'

{"count":2,"devices":[{"device_id":"greeter001","service":"greeting","service_path":"/","entity_name":"urn:ngsi-ld:Greeting:001","entity_type":"Greeting","transport":"MQTT","attributes":[{"object_id":"w","name":"words","type":"Text"}],"commands":[],"static_attributes":[],"protocol":"PDI-IoTA-UltraLight","explicitAttrs":false},{"device_id":"greeter002","service":"greeting","service_path":"/","entity_name":"urn:ngsi-ld:Greeting:002","entity_type":"Greeting","polling":true,"transport":"HTTP","attributes":[{"object_id":"w","name":"words","type":"Text"}],"commands":[],"static_attributes":[],"protocol":"PDI-IoTA-UltraLight","explicitAttrs":false}]}

Sending device data over MQTT
We're going to use an external WebSocket client to simulate device data coming in over MQTT.
Browse to http://www.emqx.io/online-mqtt-client. Hit the "New Connection" button and enter the following data: name=kitt4sme, client-id=tasty, host=ws://<IP_ADDRESS>, path=/mqtt/, port=80, username=iot. You also need to enter the "iot" user's password, which I can't type here obviously. Hit connect, then send the following UL message to the ul/gr33t/greeter001/attrs topic: w|howzit!.
Check the "howzit!" greeting trekked all the way to Orion. It should be stored in the "Greeting" entity having an ID of urn:ngsi-ld:Greeting:001.
$ curl \
  'http://<IP_ADDRESS>/orion/v2/entities/urn:ngsi-ld:Greeting:001/attrs/words/value' \
  -H 'fiware-service: greeting' \
  -H 'fiware-servicepath: /'

"howzit!"

Sending device data over HTTP
Let's also send a greeting from greeter002. This device sends its data over HTTP
$ curl -iX POST \
  'http://<IP_ADDRESS>/ulagent/iot/d?k=gr33t&i=greeter002' \
  -H 'Content-Type: text/plain' \
  -d 'w|ahoy, matey!'

HTTP/1.1 403 Forbidden
date: Sun, 06 Nov 2022 21:17:46 GMT
server: istio-envoy
content-length: 0

What?! Yep, that's right. Our FIWARE OPA policy checks you've got a valid JWT token, since we didn't have one, we got shown the door. How rude.

This time the POST goes through and Orion gets our friendly greeting
$ curl \
  'http://<IP_ADDRESS>/orion/v2/entities/urn:ngsi-ld:Greeting:002/attrs/words/value' \
  -H 'fiware-service: greeting' \
  -H 'fiware-servicepath: /'

"ahoy, matey!"

As expected, the greeting got stored in the "Greeting" entity having an ID of urn:ngsi-ld:Greeting:002.
Cool bananas!


MultiDex / ART support

It doesn't appear that the script supports builds that result in multiple dex files, where classes are segmented into a primary dex file and additional dex files. The script reports only 22K methods, which I believe to be merely the methods from the primary dex (mostly our own application minus libraries.)
The Android tool chain will generate multiple DEX files when your minSdkLevel is Lollipop / 21 since that is how ART deals with library code (one dex per dependency), and also when you have the multidex switch enabled.

Multi-dex support was added in https://github.com/mihaip/dex-method-counts/commit/a18e3f560d1a70b1c17dfdacaed5bff8025f8eaf and I can confirm that the tool reports more than 64k methods for our mutli-dex APKs.

Great news, thanks! Any idea yet when this might hit Central? I'm very
interested in this enhancement.
Thanks again.
On Tue, Nov 10, 2015, 09:02 Sebastian Schuberth<EMAIL_ADDRESS>wrote:

Multi-dex support was added in a18e3f5
https://github.com/mihaip/dex-method-counts/commit/a18e3f560d1a70b1c17dfdacaed5bff8025f8eaf
and I can confirm that the tool reports more than 64k methods for our
mutli-dex APKs.
—
Reply to this email directly or view it on GitHub
https://github.com/mihaip/dex-method-counts/issues/16#issuecomment-155351506
.

I'm not aware that this project publishes its binaries to Maven Central or Bintray / JCenter. There is for example this artifact, but that's not the official release as it seems.

Ah fair enough. Thanks.
On Tue, Nov 10, 2015, 09:10 Sebastian Schuberth<EMAIL_ADDRESS>wrote:

I'm not aware that this project publishes its binaries to Maven Central or
Bintray / JCenter. There is for example this artifact
https://bintray.com/sloy/maven/dex-method-counts/view, but that's not
the official release as it seems.
—
Reply to this email directly or view it on GitHub
https://github.com/mihaip/dex-method-counts/issues/16#issuecomment-155353601
.


Drive disconnecting/disappearing after several hours of working fine - ideas?

On 2019.5 with therealmarcone's mods, everything working as expected until it doesn't.  Two days in a row when I get to my car after being in Sentry mode for the day, the drive is not connected to the Tesla (no camera icon) and no recording is happening.  archiveloop is still running though - exact same session, the pi never lost power or rebooted.  When I get home it connects to WiFi and uploads files and after upload, the drive reconnects fine.  By looking at the files, I can see that at some point in the day, the recordings just stopped.
Any ideas on how to debug this?

Ya same, was wondering what I was doing wrong. Which I wonder if someone could write a Cron job to make sure it's running properly at all time and or if unmounted virtually to remount

I did the workaround as well and it appeared to work on 2019.5.15 when I plug it in to test. I could access music from the drive and also can record to the drive, but I never see it copy to my NAS. The next day, I go back out to the car and the drive doesn't appear to work anymore. No music no cam recording (not even the X icon)
I rebuilt the drive from scratch with the workaround from the very beginning and plug it in to test. It once again seemed to work for music and cam recording, but I still don't see it copying anything to the NAS. I didn't have any more time to test that same day, but the next day, the drive once again doesn't appear to work anymore just as before -- no music or cam recording.
Later the same day, I get a FW update to 2019.8.2 and after the firmware update, I noticed that the Pi doesn't have any power -- No LED light. I'm not sure if this was the same behavior with 2019.5.15 or not. I plugged my phone into the same port and no power for the phone either. I switched to the other port and the Pi's LED lights up, but it doesn't work -- no music, no cam. But after awhile, I noticed the Pi's LED is off again. I try to plug in my phone into this port as well and now I have no power to either USB port. I reboot the MCU and power comes back to both. But the drive still doesn't work.
I haven't any time to debug any further, but the Pi's two drives appear fine when I plug into my Windows machine at home.

@ken830 - I've seen the same issue with power on the pi.  When the car boots, power is provided to the pi, but doesn't appear stable and the pi powers off after a minute.  My phone will no longer charge on that port until I reboot the MCU.
I've discovered a workaround.  I'm now powering the pi via the cigarette lighter outlet and using the front USB port for communication with the MCU.  This setup has worked well this afternoon.

@ken830 - do you know if the lighter outlet says powered when the car is in Sentry mode?

It's too bad there's no clean way to route a cable from the cig light outlet to the front USB compartment.
I tried to test the cig light power with sentry mode, but power is still present at the cig outlet and front USB when I manually lock the car. Power was still present when I turned off Bluetooth to simulate a walkway locking. I didn't have enough time to wait for the car to sleep. I also tried to toggle sentry mode on and off but power remained on for both USB and cig outlet. Not sure if this is new behavior or not on this fw release. I expected it to follow the behavior of my Model S (really early 2013) and should cut power to the cig outlet as soon as the doors closed with no one in the driver seat.

I just ran into the issue again where the dashcam stops recording and there is no dashcam icon on screen in my model 3.  As mentioned before, I'm powering the pi via the cigarette lighter to ensure sufficient power with the firmware version I'm on.  The dashcam stopped while I was driving...after 35 minutes or so, I'd guess.
I ssh'd into the pi and found this information in dmesg.  Perhaps it will mean something to someone here.
[   31.087461] g_mass_storage gadget: high-speed config #1: Linux File-Backed Storage [  146.408129] CIFS VFS: Server <IP_ADDRESS> has not responded in 120 seconds. Reconnecting... [  146.419396] CIFS VFS: Free previous auth_key.response = da5c4900 [  291.287162] random: crng init done [  291.287181] random: 7 urandom warning(s) missed due to ratelimiting [ 3222.205121] CIFS VFS: Server <IP_ADDRESS> has not responded in 120 seconds. Reconnecting... [ 4089.093677] ------------[ cut here ]------------ [ 4089.093826] WARNING: CPU: 0 PID: 0 at drivers/usb/dwc2/gadget.c:300 dwc2_hsotg_init_fifo+0x1ac/0x1d0 [dwc2] [ 4089.093833] Modules linked in: g_mass_storage usb_f_mass_storage libcomposite cmac sha256_generic arc4 ecb md4 md5 hmac nls_utf8 cifs ccm bnep hci_uart btbcm serdev bluetooth ecdh_generic brcmfmac brcmutil snd_bcm2 835(C) snd_pcm cfg80211 snd_timer rfkill snd fixed uio_pdrv_genirq uio dwc2 udc_core ip_tables x_tables ipv6 [ 4089.093943] CPU: 0 PID: 0 Comm: swapper Tainted: G         C      4.14.98+ #1200 [ 4089.093947] Hardware name: BCM2835 [ 4089.093995] [<c0016420>] (unwind_backtrace) from [<c0013d40>] (show_stack+0x20/0x24) [ 4089.094020] [<c0013d40>] (show_stack) from [<c0638de4>] (dump_stack+0x20/0x28) [ 4089.094041] [<c0638de4>] (dump_stack) from [<c0021ecc>] (__warn+0xe4/0x10c) [ 4089.094057] [<c0021ecc>] (__warn) from [<c0021fc0>] (warn_slowpath_null+0x30/0x38) [ 4089.094135] [<c0021fc0>] (warn_slowpath_null) from [<bf0b1aa8>] (dwc2_hsotg_init_fifo+0x1ac/0x1d0 [dwc2]) [ 4089.094262] [<bf0b1aa8>] (dwc2_hsotg_init_fifo [dwc2]) from [<bf0b44b4>] (dwc2_hsotg_core_init_disconnected+0x88/0x3ec [dwc2]) [ 4089.094378] [<bf0b44b4>] (dwc2_hsotg_core_init_disconnected [dwc2]) from [<bf0b4f0c>] (dwc2_hsotg_irq+0x6f4/0x7c8 [dwc2]) [ 4089.094447] [<bf0b4f0c>] (dwc2_hsotg_irq [dwc2]) from [<c006230c>] (__handle_irq_event_percpu+0x94/0x1c8) [ 4089.094460] [<c006230c>] (__handle_irq_event_percpu) from [<c006246c>] (handle_irq_event_percpu+0x2c/0x68) [ 4089.094472] [<c006246c>] (handle_irq_event_percpu) from [<c00624e0>] (handle_irq_event+0x38/0x4c) [ 4089.094487] [<c00624e0>] (handle_irq_event) from [<c0065e10>] (handle_level_irq+0xa0/0x114) [ 4089.094512] [<c0065e10>] (handle_level_irq) from [<c0061590>] (generic_handle_irq+0x30/0x44) [ 4089.094528] [<c0061590>] (generic_handle_irq) from [<c0061af0>] (__handle_domain_irq+0x58/0xb8) [ 4089.094543] [<c0061af0>] (__handle_domain_irq) from [<c0009418>] (bcm2835_handle_irq+0x28/0x48) [ 4089.094562] [<c0009418>] (bcm2835_handle_irq) from [<c0652cfc>] (__irq_svc+0x5c/0x7c) [ 4089.094569] Exception stack(0xc0943ef8 to 0xc0943f40) [ 4089.094576] 3ee0:                                                       00000000 00000000 [ 4089.094588] 3f00: ffffffff c0945414 c0942000 c09450a4 c09cddc6 c0945020 c09dae00 c091ea28 [ 4089.094599] 3f20: dbfff9e0 c0943f54 c0943f48 c0943f48 c001075c c0010760 60000013 ffffffff [ 4089.094617] [<c0652cfc>] (__irq_svc) from [<c0010760>] (arch_cpu_idle+0x30/0x40) [ 4089.094632] [<c0010760>] (arch_cpu_idle) from [<c0652bac>] (default_idle_call+0x34/0x48) [ 4089.094644] [<c0652bac>] (default_idle_call) from [<c0053cf8>] (do_idle+0x8c/0xec) [ 4089.094656] [<c0053cf8>] (do_idle) from [<c0053fd4>] (cpu_startup_entry+0x1c/0x20) [ 4089.094678] [<c0053fd4>] (cpu_startup_entry) from [<c064d5bc>] (rest_init+0x7c/0x9c) [ 4089.094698] [<c064d5bc>] (rest_init) from [<c08d4d48>] (start_kernel+0x358/0x3c8) [ 4089.094706] ---[ end trace dec6fc0e363ad91e ]--- [ 4089.097916] dwc2 20980000.usb: dwc2_hsotg_ep_stop_xfr: timeout GINTSTS.GOUTNAKEFF [ 4089.098036] dwc2 20980000.usb: dwc2_hsotg_ep_stop_xfr: timeout DOEPCTL.EPDisable [ 4089.100769] dwc2 20980000.usb: new device is high-speed [ 4094.162756] dwc2 20980000.usb: new device is high-speed [ 4109.326872] dwc2 20980000.usb: new device is high-speed [ 4109.500913] dwc2 20980000.usb: new device is high-speed
The last line then repeats every few seconds.

I manually removed the g_mass_storage module and re-added it.  Once it was re-added, the dashcam in the model 3 started working again.  Perhaps there is something in the dmesg output I posted that can be listened for to reload the module?

I've updated my pi to a 4.19.29 kernel by using rpi-update.  I'll have sentry mode on quite a bit over the next few days and will report back if the pi keeps recording the entire time.
WARNING:  rpi-update will update the pi to an unstable, testing version of the kernel.  Use this at your own risk.  You can find more information here: https://www.raspberrypi.org/documentation/linux/kernel/updating.md

I tested mine with the cig-outlet workaround on this morning's commute and it was working great for over an hour.

Following all those mods from therealmarcone, I'm getting fsck errors on the mount points. I actually am doing edits to my scripts to fsck on /dev/loop0 (or loop1 when both are mounted) rather than /mnt/cam and /mnt/music. This appears to be related to the repartitioning/FS change of formatting the whole .bin file as fat32 versus partitioning then formatting it.
I noticed quite a few of these in dmesg:
[   26.189170] FAT-fs (loop0): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Still could be stemming from the power issues, but I'm looking to find a way to get around them more cleanly. I think the old script just did a better job of cleaning up the Tesla's unclean dismounting mess.

My car has been in sentry mode for about 17 hours.  Went out to drive the car and the dashcam was still working.  This is the first time for me that the dashcam worked after a few hours of sentry mode running.  So, I think the kernel update I mentioned has solved my dashcam issue.

I'll have to try that when I get home. I know when it ran for some time it
still didn't upload what was there already when it was trading.
I tried to find the dir for stored vids but didn fsee it
On Fri, Mar 22, 2019, 9:09 AM firedfly<EMAIL_ADDRESS>wrote:

My car has been in sentry mode for about 17 hours. Went out to drive the
car and the dashcam was still working. This is the first time for me that
the dashcam worked after a few hours of sentry mode running. So, I think
the kernel update I mentioned has solved my dashcam issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cimryan/teslausb/issues/128#issuecomment-475614598,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXirEj9y87BRtAvcbyBfT3h6xrURoDj_ks5vZNYBgaJpZM4b_Fai
.

Have tried maintaining solid power via 12v outlet and again with a portable battery pack.  No change in behavior, the filesystems still disconnect from the car at some point, generally 1-6 hours later.  Made it from 7:00am to noon yesterday in Sentry mode, which was a record.  Just updated to 4.19.30 and enabled persistent journaling, will report back.

So my car stopped recognizing my RasPi altogether even after the fixes I was adding into it. I even hard to hard-reboot my car because both front USB ports stopped giving power! Anyways, strange note - plugging it into a USB 2.0 hub allowed it to show up when nothing else did. Has anyone tried this approach? I'm wondering if the car wants the device detected in a certain amount of time, and if it's not - it shuts off/resets power to that port entirely? Jury's still out on this one, but I'm going to see if it continues to work this way for a few days and I'll report back.

Just updated to 4.19.30 and enabled persistent journaling, will report back.

Report is positive.  I’ve been runing for three days now without incident.  Several uses of Sentry mode included.  4.19.30 appears to fixt this for me.  Note: I’m on 2018.05.15, I have not been updated to 2018.8.3 which appears to introduce USB power issues.

@jspv, yes, I also had the random disconnect issue but after upgrading to dev kernel, its been working fine

Is it possible to roll back to an older kernel version to reliably know if mine is kernel-related?

Following all those mods from therealmarcone, I'm getting fsck errors on the mount points. I actually am doing edits to my scripts to fsck on /dev/loop0 (or loop1 when both are mounted) rather than /mnt/cam and /mnt/music. This appears to be related to the repartitioning/FS change of formatting the whole .bin file as fat32 versus partitioning then formatting it.

I found this as well.  therealmarcone has a PR up with corrections to use /dev/loop passed to fsck and it works well on my setup and 2019.8.4 so far.  With just the new partitioning, fsck would fail to run which meant that after the first dirty power off, you'd lose access to the cam/music drives on the car.  Depending on your archive method and firmware version, you may also see issues with the new/old paths PR which isn't working for all configurations yet.  In  general, you can workaround this issue by creating dummy paths for both new and old formats to avoid errors.  Remember that any fatal errors in the archiving state will leave the drives unconnected until the next reboot, so verify that archiving is running without crashing.

How do I apply the /dev/loop fix ?  I am running 2019.8.5 and the Cam doesn't show up in car, but the folder does show up in windows.

FWIW, I'm running @marcone's build on 2019.8.5. The only way I could keep it working after updating from 2019.5.15 was to plug in a USB cable to both ports on my Pi. I was seeing behavior like in #132, but once I did that, everything started working as expected.

I've got an X and a 3.  Both are currently on 2019.8.5
I've been using TeslaUsb successfully since December.   I made @marcone's changes to update to using a partitioned drive with FAT file system.
On the Model 3, everything's working great.
The X hasn't worked for a couple of months; I spent some time today to figure out what's wrong with the X.  On the Model X, it appears that the X is cutting power to the USB port every 35 seconds or so, causing the PI to reboot every time, obviously.   I've tried both my Pi's on each car.  Both Pi's work fine in the Model 3, neither of them work in the Model X.
The Model X has white lights around the USB port.  If I watch the light after plugging in the Pi, the light around the USB port flashes off and on at 35 seconds after I plug in the PI directly to the port.
My guess is that the MCU is interrogating the port to try to find a  file system, and it's taking the PI too long to boot up and present the Music / CAM drives before the MCU gives up and powercycles the port.  This appears to be new behavior in 2019.8.x   I have no idea why the behavior is different between the X and the 3, but it definitely is.   My X is relatively new (Aug 2018 build), so I assume it has the latest available hardware revision of the MCU.
I tried updating the pi to  rpi-4.19.y using rpi-update, same failure.
It's not immediately clear what's wrong, the last messages in dmesg on each boot are:
[   44.624206] FAT-fs (loop0): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   47.528652] Mass Storage Function, version: 2009/09/11
[   47.528673] LUN: removable file: (no medium)
[   47.528829] LUN: removable file: /backingfiles/music_disk.bin
[   47.528924] LUN: removable file: /backingfiles/cam_disk.bin
[   47.528933] Number of LUNs=2
[   47.543804] g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
[   47.543822] g_mass_storage gadget: g_mass_storage ready
[   47.543838] dwc2 20980000.usb: bound driver g_mass_storage
[   47.702271] dwc2 20980000.usb: new device is high-speed
[   47.735333] dwc2 20980000.usb: new address 32
[   47.768378] g_mass_storage gadget: high-speed config #1: Linux File-Backed Storage

I guess I'll give up and us the cigarette lighter trick to power the PI.

To test your hypothesis maybe altering the script to get to connecting the
usb drive asap might work?  It seems to connect to the archive first before
connecting usb which takes several seconds.
On Sat, Apr 6, 2019, 9:41 PM Jay Sauls<EMAIL_ADDRESS>wrote:

I've got an X and a 3. Both are currently on 2019.8.5
I've been using TeslaUsb successfully since December. I made @marcone
https://github.com/marcone's changes to update to using a partitioned
drive with FAT file system.
On the Model 3, everything's working great.
The X hasn't worked for a couple of months; I spent some time today to
figure out what's wrong with the X. On the Model X, it appears that the X
is cutting power to the USB port every 35 seconds or so, causing the PI to
reboot every time, obviously. I've tried both my Pi's on each car. Both
Pi's work fine in the Model 3, neither of them work in the Model X.
The Model X has white lights around the USB port. If I watch the light
after plugging in the Pi, the light around the USB port flashes off and on
at 35 seconds after I plug in the PI directly to the port.
My guess is that the MCU is interrogating the port to try to find a file
system, and it's taking the PI too long to boot up and present the Music /
CAM drives before the MCU gives up and powercycles the port. This appears
to be new behavior in 2019.8.x I have no idea why the behavior is different
between the X and the 3, but it definitely is. My X is relatively new (Aug
2018 build), so I assume it has the latest available hardware revision of
the MCU.
I tried updating the pi to rpi-4.19.y using rpi-update, same failure.
It's not immediately clear what's wrong, the last messages in dmesg on
each boot are:
[   44.624206] FAT-fs (loop0): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   47.528652] Mass Storage Function, version: 2009/09/11
[   47.528673] LUN: removable file: (no medium)
[   47.528829] LUN: removable file: /backingfiles/music_disk.bin
[   47.528924] LUN: removable file: /backingfiles/cam_disk.bin
[   47.528933] Number of LUNs=2
[   47.543804] g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
[   47.543822] g_mass_storage gadget: g_mass_storage ready
[   47.543838] dwc2 20980000.usb: bound driver g_mass_storage
[   47.702271] dwc2 20980000.usb: new device is high-speed
[   47.735333] dwc2 20980000.usb: new address 32
[   47.768378] g_mass_storage gadget: high-speed config #1: Linux File-Backed Storage
I guess I'll give up and us the cigarette lighter trick to power the PI.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cimryan/teslausb/issues/128#issuecomment-480551352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZr8rkFOWKXvAWcFVQZCb1n2e4qurroks5veUyugaJpZM4b_Fai
.

Just tried that.  Didn't seem to help.
I modified the main body of archiveloop script to:

export -f mount_mountpoint
export -f ensure_mountpoint_is_mounted
export -f retry
export -f ensure_mountpoint_is_mounted_with_retry
export -f log

log "Starting..."
mount_and_fix_errors_in_files
connect_usb_drives_to_host

@jaysauls the USB hub trick (connect RasPi to one, so the power stays powered) seems to work around the issue you are mentioning. Feel free to confirm this in your X. The behavior you are describing really doesn't sound any different from that which I was seeing in my 3.

Can someone tell me exactly where these scrips are located so I can take a look at these edits?  Sorry, complete noob.

@lapean111 They're /in /root/bin/

I have now been stable for 2 days.  I am using a cig port adaptor to power the pi, and a data only USB cable I made by covering the 5volt lead with tape.  Annoying to have 2 cables, but it has been 100% stable for 2 days.

I've been just dealing with disconnects almost every time I drive my car but I've decided it is time to try and fix it. Should I start from scratch? I added the responsive file manager so I could easily run the reconnect but now it isn't reconnecting. I'm worried I have SD corruption. Is there a start to finish?
 *** Backing up modules 4.14.98+ ############################################################# WARNING: This update bumps to rpi-4.19.y linux tree Be aware there could be compatibility issues with some drivers Discussion here: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=224931 ############################################################## Would you like to proceed? (y/N)  *** Downloading specific firmware revision (this will take a few minutes)   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   168    0   168    0     0    436      0 --:--:-- --:--:-- --:--:--   437 100 58.5M  100 58.5M    0     0  1357k      0  0:00:44  0:00:44 --:--:-- 1299k  *** Updating firmware rm: cannot remove '/boot/start_cd.elf': Read-only file system rm: cannot remove '/boot/start_db.elf': Read-only file system rm: cannot remove '/boot/start.elf': Read-only file system rm: cannot remove '/boot/start_x.elf': Read-only file system

@schmug looks like you forgot to remount boot and root as read-write. Run /root/bin/remountfs_rw before running rpi-update (or do it manually using mount -o remount,rw /boot)

@schmug looks like you forgot to remount boot and root as read-write. Run /root/bin/remountfs_rw before running rpi-update (or do it manually using mount -o remount,rw /boot)

Wow... and I swore I had done that lol. thanks

I just got an update to 2019.16.2 and noticed the TeslaCam raspberry pi is disconnecting again.  If I power cycle the raspberry pi, the dashcam will start recording again (for may be 10 minutes).
Is anyone else seeing these issues in 2019.16.2?

I manually removed the g_mass_storage module and re-added it. Once it was re-added, the dashcam in the model 3 started working again. Perhaps there is something in the dmesg output I posted that can be listened for to reload the module?
EDIT: I see reports of other, non Tesla, applications of the pi having the same issue. Sounds like a newer kernel version may fix the problem. I'll try to investigate later today if I get the chance. raspberrypi/linux#2796

FWIW, it was being used in a tesla too :)


Add traffic in metrics to the Email Alert API dashboard

This adds "Traffic In" metrics to the Email Alert API dashboard based on the "Email Alert API traffic" dashboard that exists in production right now but not in Puppet.
Trello Card

Tom and I split this into two graphs and added AWS
Looks like this in Integration:

Looks like this in production:


Order babel presets so they work correctly

Fixes #485

Coverage remained the same at 90.476% when pulling 3c0c13ce5559080c00b488a8b199d5bc5996763d on samit4me:class-properties-transform into 4fad0e5470f51fc493b05aa8a8e103e0622db24d on coryhouse:master.

Is it possible to centralize them and get the proper order?

Yes I know what you mean, it doesn't look great. I don't know of any other way but that doesn't mean you can't. Will have another look when I get some more time.

I agree centralizing would be preferable if possible, but this reads clearly as is, so I'm good w/ merging as is if @kwelch and @nickytonline are.

I'm fine with it as is. 👍

I pulled this locally to try it out and got runtime errors with the production build.
Uncaught Error: Module build failed: Error: Unexpected extra options ["react","stage-1"] passed to preset.

Coverage remained the same at 90.476% when pulling 90fe6960ad9c332e03acaf2f323d5d4b46544e83 on samit4me:class-properties-transform into 4fad0e5470f51fc493b05aa8a8e103e0622db24d on coryhouse:master.

Validated by changing SavingsForm to use arrow functions and static propTypes.

AppVeyor died for a peerDep, but I don't see any issues with merging.

Great pickup @kwelch, thank you for finding that issue ✨


fixing htmlOutputTemplate support for html2ts

htmlOutputTemplate cannot be interpolated before being passed to html2ts because it contains underscore/lodash template variables which need to be populated

What's the problem here?:
There are several pull requests pending or already merged related to this bug. But just nothing happens since weeks. I would appreciate if the fix could be released soon.
See also:
https://github.com/TypeStrong/grunt-ts/pull/298
https://github.com/TypeStrong/grunt-ts/pull/291
https://github.com/TypeStrong/grunt-ts/pull/307
https://github.com/TypeStrong/grunt-ts/pull/304

Hi - I am sorry for the delay.  I've been very busy with a new job and baby and a few other projects.  I will try to get this merged and released tonight.

@sethx Thank you so much.  This was also identified by some other folks.  I will include you in the patch notes.


[Improve] Allow choosing which global code coverage report to use with the monocart test results report

Request
Would it be possible that we could choose the html report to use for the global code coverage instead of defaulting to whatever is at coverage/index.html ?
To be more specific, what I'd like to do is be able to use with the toIstanbul code coverage option but still get the monocart html report for code coverage. The only reason I use the toIstanbul is to produce a cobertura and lcov files which I then upload to Azure Devops and Sonarqube respectively. However, when I'm looking at the code coverage I much rather the built in report from monocart, instead of the one I get from istanbul.
Basic suggestion to exemplify the request

Perhaps there could be an extra parameter on the code coverage option that would let us specify the path to the global code coverage file and if not specified default it to coverage/index.html ?

Furthermore, even if the toIstanbul is configured, could there be some option to still keep the monocart global code coverage report? In addition to this option, another option to specify the path the html report would be nice, something similar to the istanbul subDir that is mentioned on #68 but that would apply to the monocart global code coverage report.

With the above 2 points we could do something like this:
{
  name: 'playwright code coverage with monocart reporter',
  outputFile: ...,
  coverage: {
    reportFile: '<playwright configuration output dir>/coverage/monocart-code-coverage-report/global-coverage.html'
    report: {
      overwriteWithIstanbul: false,
      outputFile: '<playwright configuration output dir>/coverage/monocart-code-coverage-report/global-coverage.html'
    },
    toIstanbul: [
      {
        name: 'html-spa',
        options: {
          subdir: 'code-coverage-html-spa-report' // note that this is a valid option for the html-spa istanbul reporter
        }
      }
    ],
  },
},

Where:

coverage.report.overwriteWithIstanbul: would determine if we keep the monocart code coverage report if we're also using the toIstanbul set to anything other than false. The overwriteWithIstanbul could default to true to keep existing behavior.
coverage.report.outputFile: would define the path for the entry point html file and all related files for the monocart global code coverage report.

With the above configuration I'd get the following output for global code coverage:

folder at <playwright configuration output dir>/coverage/code-coverage-html-spa-report with the code coverage report from html-spa istanbul reporter.
folder at  <playwright configuration output dir>/coverage/monocart-code-coverage-report with the monocart code coverage report with the entry html file named global-coverage.html and all other related files inside this folder.
because I specified  coverage.reportFile to be <playwright configuration output dir>/coverage/monocart-code-coverage-report/global-coverage.html then I'd get the monocart global code coverage when I browsed the test results. But I could have set this property to <playwright configuration output dir>/coverage/code-coverage-html-spa-report/index.html and I would get the code coverage report from the html-spa istanbul reporter.

Further notes

This is a bit related with #68. If you agree with implementing something similar to what was suggested then #68 should likely be possible to close.
The istanbul reporter options can be found here.
The basic suggestion is just that, a simple idea. However it gets done I think it's fine as long as I could generate istanbul reports and still keep the monocart reporter plus then be able to choose which global code coverage report to be linked in the monocart tests report.  Perhaps we wouldn't need an option like the coverage.report.overwriteWithIstanbul or the coverage.report.outputFile if it was decided that the monocart global code coverage would always be placed in its own folder inside the coverage folder and that it would always be named index.html. This way it would solve most of this problem and we would only need an option like coverage.reportFile to be able to specify which global code coverage report to use (and this could default to the monocart global code coverage path).

Please let me know your thoughts or if I haven't made the request clear or if you think it's not worth it etc.

It's good time to think about this featrue, because i am planning to separate the coverage related features to a standalone project monocart-coverage-reports

I think we can close this one in favour of the work that you did to release v2.0.0 and this comment in #68.


Historical exposed metrics memorization

Hello,
I found out the follow unexpected beahviour between my prometheus db and customized client_python exporter:
I've tried to delete metrics from prometheus db using follow Web API commands:

curl -X POST -g 'http://localhost:9090/api/v1/admin/tsdb/delete_series?match[]=<name_metric>
curl -X POST -g "http://localhost:9090/api/v1/admin/tsdb/clean_tombstones

All the time series metric diseppeared from prometheus db but after few seconds, probably after the new scraping iteration, all the time series was restored. (I tried with a two hour time series, very short).
So, the questions is:  was the timeseries SAVED in the client_python exporter (buffer, cache, registry etc) and re-exposed every time to prometheus or the problem is at prometheus db side?
Is it a configurable option?
Thank you,
Daniele.

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


How to make heart pulse with animate.css

Hi!
Any idea how to make a heart pulse like here but with animate.css?
Example: https://codepen.io/jlong/pen/KBhDf

I would love to fix this issue and add the feature. Let me know if I may go ahead.

@phlegx I made some workarounds and submitted a PR  #830

Does this serve the purpose?

Closed by #830


add attributes support to hyperscript

We would like to test setting attributes not just properties and for that we can simply implement attributes option same way as described here https://github.com/skatejs/dom-diff#attributes

it's actually already working as hBore is setting DOM attributes property :)

it's not ;) :D
because various DOM reasons


Enormous amount of output when missing SMTLib translation running krun --prove

https://github.com/kframework/evm-semantics/issues/95
As demonstrated there, krun --prove generates an enormous amount of (highly redundant) output sometimes when Z3 translations are not present.
Is there a way we can be smarter about what is output to the user? Perhaps only output "missing SMTLib translation" once per missing symbol?

I think the simplest thing to do is just emit the error message and not the stack trace. Is anyone really gaining any information from those stack traces?

So you mean what would show up is still:
java.lang.UnsupportedOperationException: missing SMTLib translation for .WordStack

But none of the lines like:
        at org.kframework.backend.java.symbolic.KILtoSMTLib.translate(KILtoSMTLib.java:241)

This sounds like a good fix to me. I think there would still be some redundancy in the output though, as it seems that the same missing translation gets reported multiple times.

I mean, sure, but the main problem is that it's massively verbose, and this would take it from hundreds of lines down to maybe 10 at most.


Update 2-enforcement.md

No tech talk or talking about personal grievences with sansar in the sansar created worlds

2.3.2
Users may not engage in discussions about 3d modeling, how to animating, how to rigging, 3d tech talk, community guideline discussion in the official Sansar created welcome worlds for new users. Also they may not talk about their grievences with sansar in these worlds. This hurts sansar due to those areas are meant for welcoming new users to sansar. Conversations to new users of the possibilties of sansar through 3d is allowed but should be brief. Users should be encouraged to take that to  personal worlds or designated meeting places for that talk. Users should be encouraged to make a world for talking about "3d tech talk" that way its a known meeting place for users old and new to learn those things rather than discord.
Punishment will never be a permanent or temporary ban. Upon accusation with evidence moderation will privately message the offenders and ask them to leave to there experience if they want to talk about topic. The culture of sansar  needs to be that is the law and users are violating the law which is unacceptable, but not a bannable offense. It is an "educational offense" where the offending users need to educated that this does not help new users because tech talk may overwelm them.


Update to FHIR Ethnicity System

Change the supported Ethnicity System from v2 system : http://terminology.hl7.org/CodeSystem/v2-0189 to v3 system : https://terminology.hl7.org/3.1.0/CodeSystem-v3-Ethnicity.html. Update associated constants, tests, and documentation.

Included in release 1.1.0 https://github.com/LinuxForHealth/CsvToFHIR/releases/tag/1.1.0


Chinese text in english tutorial

Version
4.8.0
Steps to reproduce
https://echarts.apache.org/en/tutorial.html#Overview of Style Customization
Theme section
What is expected?
text between code block should be “Or”
What is actually happening?
it's “或者”

And
https://echarts.apache.org/en/tutorial.html#Dataset
second paragraph
More importantly, is enables data encoding
I think "is" here should be "it"

Thanks for reporting~ Would you like create a PR for this?
For the first: https://github.com/apache/incubator-echarts-doc/blob/master/en/tutorial/style-overview.md
For the second: https://github.com/apache/incubator-echarts-doc/blob/master/en/tutorial/dataset.md

Sure. https://github.com/apache/incubator-echarts-doc/pull/103

@maximesong Thanks for your contribution