Unifying resource representations and link templating

It seems that right now we have several ways of representing resources, and some discussion about this (https://github.com/json-api/json-api/issues/275, https://github.com/json-api/json-api/issues/268). I think we should unify these representations to create more common ground for shared tooling.
Goals

Resources and links are always consistently represented
Links can be templated to reduce data transfer
Individual links can override the template

Proposal
Resources can only be represented in two ways: a resource object and a link object.
Resource objects are used for resources that include attributes. They must include the id, href and all attributes that were requested. They are used only for primary and sideloaded resources.
Link objects are used for representing links to resources, they do not include attributes themselves. Link objects must include the ids of the linked resources, the type of the linked resources and the href where those resources can be requested. The type and href can be omitted if they are specified in a link template. The ids are always keyed under ids, no matter whether the link is to-one or to-many. This offers a fixed set of keys which makes parsing easier. Clients can figure out the cardinality by checking if the data is string/null or array/empty array for to-one and to-many respectively.
Resource object example
{
    "id": 1,
    "href": "http://api.example.com/posts/1",
    "title": "Post title",
    // Other attributes
}

Singular link object example
{
    "ids": 1,
    "href": "http://api.example.com/users/1",
    "type": "users"
}

Plural link object example
{
    "ids": [1,2,3,4],
    "href": "http://api.example.com/comments/1,2,3,4",
    "type": "comments"
}

Full response example
{
    "posts": [{
        "id": 1,
        "href": "http://api.example.com/posts/1",
        "title": "I love it when a plan comes together",
        // Other attributes
        "links": {
            "author": {
                "ids": 1,
                "href": "http://api.example.com/users/1",
                "type": "users"
            },
            "comments": {
                "ids": [1,2,3,4]
            }
        }
    }],
    "linked": {
        "users": [{
            "id": 1,
            "href": "http://api.example.com/users/1",
            "name": "John 'Hannibal' Smith",
            // Other attributes
            "links": {
                "posts": {
                    "refs": [1],
                    "href": "http://api.example.com/posts/1",
                    "type": "posts"
                }
            }
        }]
    },
    "links": {
      "posts.comments" {
        "href": "http://api.example.com/comments/{posts.comments}",
        "type": "comments"
      }
    }
}

Link object templating
A link object always consists of an id/href/type combination. However, to reduce data, the href and type may be specified in the top level links object like in the current spec. Resource level link objects are merged with matching template objects. The data in the resource level link always has precedence over the template.
Updating relationships
The JSON to update a relationship using a PUT request is the same as above. The only difference is that the type and href keys are left out. This differs from the current spec:
Old
PUT /articles/1
{
  "articles": {
    "title": "Rails is a Melting Pot",
    "links": {
      "author": "1"
    }
  }
}

New
PUT /articles/1
{
  "articles": {
    "title": "Rails is a Melting Pot",
    "links": {
      "author": {
        "ids": "1"
      }
    }
  }
}

Problems
One inconsistency that remains with this design is the type attribute, which is absent in a resource object. The rationale behind this is that the top level JSON object or linked object already specifies the type.
Including the type in every resource object has some upsides

It is more consistent with link objects.
Primary resources can now always be embedded in a data key, which makes parsing easier.
Resources can be parsed standalone since all needed data can be embedded in the resource itself.
It allows polymorphism in the future (although polymorphism creates a lot of other problems…)

It also has downsides, of course ;)

Keying the primary resources with data is inconsistent with the the keys under the linked object. These still needs to be keyed by resource type for ordering and quick lookup.

This is a long-running, complex discussion that is largely out of date with the current version of the specification. If there's any specific things that are still actionable here, please open smaller, focused issues on those specifics. Thanks!


Add support for chromium-based archivebox snapshots

This PR installs chromium as a dependency, so that chromium can be used for archivebox snapshots (using the pdf, and singlefile extractor, and other extractors which use headless chromium in the backend to actually archive the site).

To make this work, I also needed to modify the permissions given to the service by systemd.
I had to remove the lines:
RestrictNamespaces=yes
SystemCallFilter=~@clock @debug @module @mount @obsolete @reboot @setuid @swap

testme!

!testme


Bronze ibex

Enable remaining Ibex features for bronze

PMP with 16 regions
ICache with ECC
Security hardening

Thanks! Could you possibly follow up with a patch for master adding all the parameters you're adding here, but leave them disabled for now?


Regression: stream adler checksum no longer matches after inflateSetDictionary (bisected)

The latest version of zlib-ng produced a regression, detected by the flate2-rs testsuite: after setting a custom dictionary with inflateSetDictionary, the stream's adler checksum doesn't match that dictionary's adler checksum.
I reduced this to the new test included in this PR, and bisected with this test. This regression was introduced by commit 8550a90de4dcb8589a7d48fe308c4c45bba5a466 ("Leverage inline CRC + copy"); the test passes before that commit, and fails on or after that commit.

Good catch.  I think the issue here is the call to update window.  We want the copy behavior but not the checksum behavior in this case.

Ahh, confusingly your branch follows a much earlier revision so that test passes.  I'm going to need to cherry pick your commit onto develop.

Nice catch @joshtriplett, and awesome that you contribute a test for it 👍
I'll postpone merging the test until the fix is in develop, so other PRs can still go in, shouldn't be too long.

@joshtriplett Could you please rebase on develop, so we can see whether the fix and test light up all green?

Done.


autorefresh Alertmanager UI every minute

Allow Alertmanager to refresh every minute, to keep alerts up to date.

Sorry, this would cause sudden reloads while a user is editing a silence. This would be very bad.

I agree with you. Thank you!
p.s. Having an auto-refresh feature will be good.

Most browsers have plugins to enable auto-refreshing a tab.

Doing refersh via the javascript UI would probably be better, this way users can toggle it, and the UI can block refersh when editing.

You're right @SuperQ, that's will be better.


[Snyk] Upgrade react-syntax-highlighter from 13.0.0 to 13.5.3

Snyk has created this PR to upgrade react-syntax-highlighter from 13.0.0 to 13.5.3.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 9 versions ahead of your current version.
The recommended version was released 6 months ago, on 2020-09-03.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Cross-site Scripting (XSS) SNYK-JS-PRISMJS-597628
629/1000  Why? Has a fix available, CVSS 8.3
No Known Exploit

Regular Expression Denial of Service (ReDoS) SNYK-JS-PRISMJS-1076581
629/1000  Why? Has a fix available, CVSS 8.3
No Known Exploit

Cross-site Scripting (XSS) SNYK-JS-PRISMJS-597628
629/1000  Why? Has a fix available, CVSS 8.3
No Known Exploit

Regular Expression Denial of Service (ReDoS) SNYK-JS-PRISMJS-1076581
629/1000  Why? Has a fix available, CVSS 8.3
No Known Exploit

Regular Expression Denial of Service (ReDoS) SNYK-JS-HIGHLIGHTJS-1048676
629/1000  Why? Has a fix available, CVSS 8.3
No Known Exploit

Prototype Pollution SNYK-JS-HIGHLIGHTJS-1045326
629/1000  Why? Has a fix available, CVSS 8.3
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: react-syntax-highlighter

13.5.3 - 2020-09-03Documentation update again
Remembered to update CHANGELOG at the same time as version change. We'll get this right from now on!

13.5.2 - 2020-09-03Documentation update

recreated/updated CHANGELOG for versions 10.x through current, fixing #214

13.5.1 - 2020-08-20Bugfix:

#301: brought back createElement that went missing as of version 13.5.

import createElement from "react-syntax-highlighter/create-element";
Thanks to @ samuela for spotting this one.

13.5.0 - 2020-08-17Enhancements

#299: clean up old files in project root, add jest to eslint

Grateful to @ ktmud for stepping in with that improvement.
Dependency updates

#300: Updated to refractor 3.1.0, which brings in prismjs 1.21.0. We'd pinned react-syntax-highlighter 13.3.1 to prismjs 1.21.0, but didn't realize that refractor's dependency would keep us at 1.20.0

13.4.0 - 2020-08-14Bugfixes

JS error when using lineNumberStyle() for inline line numbers (#296)
incorrect 'hljs' className applied to <pre> when using Prism (#297)

Enhancements

added ESLint (#298)
added favicon to demo (#295)
new addition to the "built with" list (#293)

Thanks to @ ktmud for jumping in with contributions!

13.3.1 - 2020-08-08Updates

prism updated to 1.21.0, with lots of improvements: CHANGELOG for prism 1.21.0
added Github repo link to the upper right corner of demo pages

Bugfixes

#287 - Truncated Prism shell-session language command output
#285 - Incorrect syntax highlighting for mutli-line comments
#278 - Unexpected behavior with useInlineStyles={false}

Thanks to @ urish and @ prichey for contributing PRs!

13.2.1 - 2020-07-31Minor bugfix: neglected to include rebuilt "Prism async light" demo files in 13.2.0 release

13.2.0 - 2020-07-31
Updates our prism-themes dependency to pull in new themes, including vsc-dark-plus
Prism async demo now dynamically loads autogenerated Prism themes list (EDIT: neglected to include built demo files, fixed in 13.2.1)

New Prism themes available

a11yDark
dracula
materialDark
materialLight
materialOceanic
nord
shadesOfPurple
synthwave84
vscDarkPlus

13.1.0 - 2020-07-31Updates to demos

indicate that Highlight powers the default demo
restored Prism demo that went missing in 13.0.0
autogenerate demo-specific style lists (and add a comment to autogenerated files pointing out that they're autogenerated)
demos now autoload full lists of languages and styles from highlight/prism
minor UI adjustments

13.0.0 - 2020-07-23

    from react-syntax-highlighter GitHub release notes

Commit messages

Package name: react-syntax-highlighter

e1d1b66 13.5.3
ab959be 13.5.2
5fec530 Recreate changelog from v10.x through v13.x (#307)
18617d2 13.5.1
7472fdb bring back createElement export at root (#304)
6656f5d Merge branch 'master' of github.com:react-syntax-highlighter/react-syntax-highlighter
6db51a5 13.5.0
91628af keep badges on same line
81d615e Update refractor to 3.1.0 (picking up Prism 1.21.0) (#300)
0f98a88 Cleanup root folder and add jest to eslint (#299)
b2a2c0d 13.4.0
d7a14d8 demo build
b3c9ad2 Add ESLint for better code quality (#298)
3310277 test fix: snapshot update
47d74a2 resolve demo build conflicts
7cc2983 Merge branch 'ktmud-bugfix-lineNumberStyle'
67b47f6 Apply correct classnames to <pre> and <code> elements (#297)
2c89a02 fix: JS error when use lineNumberStyle() for inline line numbers
ae1f270 add favicon to demo (#295)
8ae8ad8 added goodarduinocode to the "Built with" section (#293)
a69d6a2 13.3.1
d898c47 Pass customStyles and className even if useInlineStyles is false (#279)
fe5f1ac Bump prismjs from 1.20.0 to 1.21.0 (#291)
70d3809 add corner link (#292)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Hyper geometries tracker

#1093
#1100
Switch boxes to hyper boxes in benchmarks and tests
Switch spheres to hyper spheres in benchmarks and tests
Switch geometries for hyper geometires [backwards incompatible]

Forgot about this one. Duplicate of #1144.


Add functioning camera view

With help from https://libgdx.com/wiki/start/a-simple-game

The camera was there before but the batch and spriterenderer had to be told to render within those matrices


iOS: After I interacted with token my Txs are disappeared from the wallet

Describe the bug
After I interacted with token my Txs are disappeared from the wallet form the latest Tx screen
To Reproduce
Steps to reproduce the behavior:

Connect wallet with token
Do some buy/sell tx
Check wallet
See that tx are disappeared from wallet

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
ios app Superhero Wallet 2.3.2 (3)
Additional context
Add any other context about the problem here.
https://github.com/user-attachments/assets/b335e7e8-c663-4e4f-adb9-1c86c137f34b

Fixed by the latest commit 3d1e6f6. Can be closed.


Software installation failed due to protozfits

Since now the IT container is not accessible I was trying to install magic-cta-pipe in my local Mac PC. However, when trying to create an environment with anaconda3 it failed with the following error messages.
I used the latest anaconda package, pip was the latest version. It looks that installing protozfits failed due to a problem related to cmake. I looked into the protozfits repository and it seems the following function works there:
https://gitlab.cta-observatory.org/cta-computing/common/acada-array-elements/adh-apis/-/blob/master/setup.py#L30
Protozfits is needed for lstchain (and ctapipe_io_lst?) so I expected the same problem happen when installing lstchain, but strangely it was installed in my local Mac PC without this error, so I think most likely it is a problem of magic-cta-pipe, so that's why I opened this issue page here.
Did someone face this kind of error ever before? I was tying to understand the cause but gave up today... @aleberti do you happen to have any ideas?
Thank you very much in advance,

(base) gammadhcp140:magic-cta-pipe yoshiki$ conda env create -n lstmagic -f environment.yml
Collecting package metadata (repodata.json): done
Solving environment: done
Preparing transaction: done
Verifying transaction: done
Executing transaction: -
Installed package of scikit-learn can be accelerated using scikit-learn-intelex.
More details are available here: https://intel.github.io/scikit-learn-intelex

For example:

    $ conda install scikit-learn-intelex
    $ python -m sklearnex my_application.py

done
Installing pip dependencies: - Ran pip subprocess with arguments:
['/Users/yoshiki/opt/anaconda3/envs/lstmagic/bin/python', '-m', 'pip', 'install', '-U', '-r', '/Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt']
Pip subprocess output:
Collecting lstchain~=0.9.6
Using cached lstchain-0.9.6-py3-none-any.whl (15.3 MB)
Collecting ctapipe_io_magic~=0.4.5
Using cached ctapipe_io_magic-0.4.5-py3-none-any.whl (27 kB)
Collecting uproot~=4.1
Using cached uproot-4.3.3-py2.py3-none-any.whl (302 kB)
Collecting ctaplot~=0.5.5
Using cached ctaplot-0.5.6-py3-none-any.whl
Collecting pyirf~=0.6.0
Using cached pyirf-0.6.0-py3-none-any.whl (53 kB)
Requirement already satisfied: ctapipe~=0.12.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.12.0)
Requirement already satisfied: jinja2~=3.0.2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (3.0.3)
Requirement already satisfied: numpy<1.22.0a0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.21.5)
Requirement already satisfied: joblib in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.1.0)
Collecting ctapipe-io-lst~=0.18.1
Using cached ctapipe_io_lst-0.18.2-py3-none-any.whl (65 kB)
Requirement already satisfied: toml in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.10.2)
Collecting seaborn
Using cached seaborn-0.11.2-py3-none-any.whl (292 kB)
Requirement already satisfied: setuptools-scm in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (7.0.4)
Requirement already satisfied: pandas in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.3.5)
Requirement already satisfied: eventio<2.0.0a0,>=1.5.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.9.1)
Requirement already satisfied: numba in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.55.1)
Requirement already satisfied: gammapy~=0.19.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.19)
Requirement already satisfied: matplotlib~=3.5 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (3.5.1)
Requirement already satisfied: scikit-learn~=1.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.0.2)
Requirement already satisfied: scipy in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.7.3)
Collecting pymongo
Using cached pymongo-4.1.1-cp37-cp37m-macosx_10_6_intel.whl (394 kB)
Requirement already satisfied: h5py in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.10.0)
Requirement already satisfied: pyparsing in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (3.0.4)
Requirement already satisfied: astropy~=4.2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (4.3.1)
Requirement already satisfied: tables in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (3.6.1)
Requirement already satisfied: bokeh~=1.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.0.4)
Requirement already satisfied: setuptools in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from uproot~=4.1->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 3)) (61.2.0)
Requirement already satisfied: pyyaml in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (6.0)
Requirement already satisfied: jupyter in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (1.0.0)
Requirement already satisfied: ipywidgets in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (7.6.5)
Requirement already satisfied: tqdm in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from pyirf~=0.6.0->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 5)) (4.64.0)
Requirement already satisfied: importlib-metadata in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from astropy~=4.2->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (4.11.3)
Requirement already satisfied: pyerfa>=1.7.3 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from astropy~=4.2->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.0.0)
Requirement already satisfied: six>=1.5.2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from bokeh~=1.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.16.0)
Requirement already satisfied: tornado>=4.3 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from bokeh~=1.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (6.1)
Requirement already satisfied: python-dateutil>=2.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from bokeh~=1.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.8.2)
Requirement already satisfied: pillow>=4.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from bokeh~=1.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (9.2.0)
Requirement already satisfied: packaging>=16.8 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from bokeh~=1.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (21.3)
Requirement already satisfied: zstandard in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.15.2)
Requirement already satisfied: importlib-resources in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (5.2.0)
Requirement already satisfied: psutil in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (5.9.0)
Requirement already satisfied: requests in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.28.1)
Requirement already satisfied: traitlets>=5.0.5,~=5.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (5.1.1)
Requirement already satisfied: iminuit>=2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.8.4)
Collecting protozfits~=2.0
Using cached protozfits-2.0.1.post1.tar.gz (8.9 MB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Requirement already satisfied: corsikaio~=0.2.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from eventio<2.0.0a0,>=1.5.1->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.2.5)
Requirement already satisfied: pydantic>=1.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from gammapy~=0.19.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.9.0)
Requirement already satisfied: regions>=0.5 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from gammapy~=0.19.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.5)
Requirement already satisfied: click>=7.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from gammapy~=0.19.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (8.0.4)
Requirement already satisfied: MarkupSafe>=2.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jinja2~=3.0.2->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.1.1)
Requirement already satisfied: fonttools>=4.22.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from matplotlib~=3.5->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (4.25.0)
Requirement already satisfied: kiwisolver>=1.0.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from matplotlib~=3.5->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.4.2)
Requirement already satisfied: cycler>=0.10 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from matplotlib~=3.5->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.11.0)
Requirement already satisfied: llvmlite<0.39,>=0.38.0rc1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from numba->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (0.38.0)
Requirement already satisfied: threadpoolctl>=2.0.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from scikit-learn~=1.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.2.0)
Requirement already satisfied: typing-extensions in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from setuptools-scm->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (4.1.1)
Requirement already satisfied: tomli>=1.0.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from setuptools-scm->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.0.1)
Requirement already satisfied: numexpr>=2.6.2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from tables->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.8.3)
Requirement already satisfied: ipython>=4.0.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (7.31.1)
Requirement already satisfied: ipykernel>=4.5.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (6.9.1)
Requirement already satisfied: nbformat>=4.2.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (5.3.0)
Requirement already satisfied: widgetsnbextension~=3.5.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (3.5.2)
Requirement already satisfied: jupyterlab-widgets>=1.0.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (1.0.0)
Requirement already satisfied: ipython-genutils~=0.2.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.2.0)
Requirement already satisfied: qtconsole in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (5.3.1)
Requirement already satisfied: notebook in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (6.4.11)
Requirement already satisfied: jupyter-console in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (6.4.3)
Requirement already satisfied: nbconvert in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (6.4.4)
Requirement already satisfied: pytz>=2017.3 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from pandas->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2022.1)
Requirement already satisfied: debugpy<2.0,>=1.0.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipykernel>=4.5.1->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (1.5.1)
Requirement already satisfied: nest-asyncio in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipykernel>=4.5.1->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (1.5.5)
Requirement already satisfied: jupyter-client<8.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipykernel>=4.5.1->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (7.2.2)
Requirement already satisfied: matplotlib-inline<0.2.0,>=0.1.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipykernel>=4.5.1->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.1.2)
Requirement already satisfied: appnope in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipykernel>=4.5.1->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.1.2)
Requirement already satisfied: pexpect>4.3 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (4.8.0)
Requirement already satisfied: decorator in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (5.1.1)
Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (3.0.20)
Requirement already satisfied: jedi>=0.16 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.18.1)
Requirement already satisfied: pygments in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (2.11.2)
Requirement already satisfied: pickleshare in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.7.5)
Requirement already satisfied: backcall in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.2.0)
Requirement already satisfied: fastjsonschema in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbformat>=4.2.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (2.15.1)
Requirement already satisfied: jsonschema>=2.6 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbformat>=4.2.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (4.4.0)
Requirement already satisfied: jupyter-core in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbformat>=4.2.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (4.10.0)
Collecting protobuf
Using cached protobuf-4.21.2-cp37-abi3-macosx_10_9_universal2.whl (483 kB)
Requirement already satisfied: terminado>=0.8.3 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.13.1)
Requirement already satisfied: prometheus-client in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.13.1)
Requirement already satisfied: argon2-cffi in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (21.3.0)
Requirement already satisfied: pyzmq>=17 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (23.2.0)
Requirement already satisfied: Send2Trash>=1.8.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (1.8.0)
Requirement already satisfied: bleach in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (4.1.0)
Requirement already satisfied: pandocfilters>=1.4.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (1.5.0)
Requirement already satisfied: entrypoints>=0.2.2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.4)
Requirement already satisfied: defusedxml in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.7.1)
Requirement already satisfied: mistune<2,>=0.8.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.8.4)
Requirement already satisfied: testpath in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.6.0)
Requirement already satisfied: beautifulsoup4 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (4.11.1)
Requirement already satisfied: jupyterlab-pygments in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.1.2)
Requirement already satisfied: nbclient<0.6.0,>=0.5.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.5.13)
Requirement already satisfied: zipp>=0.5 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from importlib-metadata->astropy~=4.2->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (3.8.0)
Requirement already satisfied: qtpy>=2.0.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from qtconsole->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (2.0.1)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from requests->ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (1.26.9)
Requirement already satisfied: certifi>=2017.4.17 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from requests->ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2022.6.15)
Requirement already satisfied: charset-normalizer<3,>=2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from requests->ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from requests->ctapipe~=0.12.0->lstchain~=0.9.6->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 1)) (3.3)
Requirement already satisfied: parso<0.9.0,>=0.8.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jedi>=0.16->ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.8.3)
Requirement already satisfied: attrs>=17.4.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jsonschema>=2.6->nbformat>=4.2.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (21.4.0)
Requirement already satisfied: pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from jsonschema>=2.6->nbformat>=4.2.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.18.0)
Requirement already satisfied: ptyprocess>=0.5 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from pexpect>4.3->ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.7.0)
Requirement already satisfied: wcwidth in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0->ipython>=4.0.0->ipywidgets->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.2.5)
Requirement already satisfied: argon2-cffi-bindings in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from argon2-cffi->notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (21.2.0)
Requirement already satisfied: soupsieve>1.2 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from beautifulsoup4->nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (2.3.1)
Requirement already satisfied: webencodings in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from bleach->nbconvert->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (0.5.1)
Requirement already satisfied: cffi>=1.0.1 in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from argon2-cffi-bindings->argon2-cffi->notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (1.15.0)
Requirement already satisfied: pycparser in /Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages (from cffi>=1.0.1->argon2-cffi-bindings->argon2-cffi->notebook->jupyter->ctaplot~=0.5.5->-r /Users/yoshiki/Work/magic-cta-pipe/condaenv.g3b1g3qh.requirements.txt (line 4)) (2.21)
Building wheels for collected packages: protozfits
Building wheel for protozfits (setup.py): started
Building wheel for protozfits (setup.py): finished with status 'error'
Running setup.py clean for protozfits
Failed to build protozfits
Installing collected packages: uproot, pymongo, protobuf, seaborn, pyirf, protozfits, ctapipe_io_magic, ctapipe-io-lst, ctaplot, lstchain
Running setup.py install for protozfits: started
Running setup.py install for protozfits: finished with status 'error'
Pip subprocess error:
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [26 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.macosx-10.9-x86_64-3.7
creating build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/R1_NectarCam_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/any_array_to_numpy.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/L0_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/CoreMessages_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/CDTS_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/init.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/R1_DigiCam_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/R1_LSTCam_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/Auxiliary_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/Proto_R1_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/CTA_R1_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
creating build/lib.macosx-10.9-x86_64-3.7/protozfits/tests
creating build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_9evts_NectarCAM.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_100evts.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_10evts.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_LST_R1_10_evts.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_SST1M_20180822.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
running build_ext
error: cmake >= 3.15.0 is required
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for protozfits
error: subprocess-exited-with-error
× Running setup.py install for protozfits did not run successfully.
│ exit code: 1
╰─> [28 lines of output]
running install
/Users/yoshiki/opt/anaconda3/envs/lstmagic/lib/python3.7/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
setuptools.SetuptoolsDeprecationWarning,
running build
running build_py
creating build
creating build/lib.macosx-10.9-x86_64-3.7
creating build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/R1_NectarCam_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/any_array_to_numpy.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/L0_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/CoreMessages_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/CDTS_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/init.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/R1_DigiCam_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/R1_LSTCam_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/Auxiliary_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/Proto_R1_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
copying python/protozfits/CTA_R1_pb2.py -> build/lib.macosx-10.9-x86_64-3.7/protozfits
creating build/lib.macosx-10.9-x86_64-3.7/protozfits/tests
creating build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_9evts_NectarCAM.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_100evts.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_10evts.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_LST_R1_10_evts.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
copying python/protozfits/tests/resources/example_SST1M_20180822.fits.fz -> build/lib.macosx-10.9-x86_64-3.7/protozfits/tests/resources
running build_ext
error: cmake >= 3.15.0 is required
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> protozfits
note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
failed
CondaEnvException: Pip failed

Hi @YoshikiOhtani, just cy chance yesterday I had to reinstall miniconda and the MCP environment (on ubuntu 18.04). It took a long time, but there were no errors, so it may be a system dependent issue :/

Thanks for looking into that. Yes, please commit the fix, very much appreciated! :)


board_build.embed_txtfiles compilation error

Hi everyone,
I'm currently using the following configuration:
platform = https://github.com/Jason2866/platform-espressif32.git#a16e5eac65ad2b2d1421de5c0bd9769365dbad74

board_build.embed_txtfiles = data/data.txt

However, I'm encountering a compilation error:
Building in release mode
prepare_file(["build/local/data.txt.txt.o"], ["data/data.txt"])
Converting build/local/data.txt.txt.o
riscv32-esp-elf-objcopy: architecture xtensa unknown
*** [build/local/data.txt.txt.o] Error 1

Interestingly, this issue does not occur in other PlatformIO projects using the default ESP32 platform.
I'd appreciate any help in resolving this compilation error.
Thanks!
Additional notes:

This issue only occurs when using the custom ESP32 platform mentioned above.
The default ESP32 platform works as expected.

Without a full example setup, it is guess work. Please provide. Best push it in a repo.

Sorry for the incomplete setup. I checked the last commit (6cd40876e4d47bd72996e2f3cedc1a1abe44ddbf) and I see the issue is solved. Thanks!

For your information, the error occurred on the ESP32-H2 board


[azeventgrid(old)] Fixing a test error so we can deprecate this library

I needed to port this text fix over so the tests will pass so I can release the library once again to deprecate it.

/azp run go - azeventgrid


cannot deepcopy flask request ?

My code:
#!/usr/bin/env python
# -*- coding: utf-8 -*-

import copy

from flask import Flask
from flask import request

app = Flask(__name__)

@app.route('/')
def hello_world():
    return 'Hello, World!'

@app.before_request
def before_request():
    request_copy = copy.deepcopy(request)
    print request_copy.path

if __name__ == '__main__':
    app.run(debug=True)

As you see, I want copy request and log something. But it is not work.
……
  File "……/python2.7/copy.py", line 163, in deepcopy
    y = copier(x, memo)
  File "……/python2.7/copy.py", line 257, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "……/python2.7/copy.py", line 174, in deepcopy
    y = copier(memo)
TypeError: cannot deepcopy this pattern object

And copy.copy() work well.
Environment

Python version: 2.7.15
Flask version: 1.0.2
Werkzeug version: 0.14.1

No, you cannot deep copy the default request class. If this is something you need, you can subclass Request, implement __deepcopy__, and assign that class to app.request_class.


Prepared looker_instance_enterprise_full for inclusion in C.G.C. docu…

…mentation
Description
Fixes b/293521866
Checklist
Readiness

[x] Yes, merge this PR after it is approved
[ ] No, don't merge this PR after it is approved

Style

[x] My sample follows the rules described for Terraform in the Effective Samples style guide
[x] My sample follows the other requirements and best practices in the Contributing
guide

Testing

[x] I have performed tests described in the Contributing guide:

[x] Tests pass: terraform apply
[x] Lint pass: terraform fmt check

Intended location

[x] Yes, this sample will be (or already is) included on cloud.google.com
Location(s): Create a Looker (Google Cloud core) instance

[ ] No, this sample won't be included on cloud.google.com
Reason:

API enablement

[x] If the sample needs an API enabled to pass testing, I have added the service to the Test setup file -- see PR

Review

[x] If this sample adds a new directory, I have added codeowners to the CODEOWNERS file. (PR)

@rogerthatdev ready for your review again! I added the link to the CODEOWNERS update PR in my original comment. TY!

Thanks @efeelaiho. @rogerthatdev @msampathkumar ready for your review again!


Remove 'secureConversations' feature flag

Remove 'secureConversations' feature flag since it is no longer needed.
MOB-1707

!merge


NTR: 'symbiont-mediated suppression of host pro-inflammatory cytokine production' and symbiont-mediated suppression of host anti-inflammatory cytokine production'

For GO-PathGO alignment
Children of symbiont-mediated suppression of host cytokine production'

From @genegodbold

Anti-inflammatory cytokines include: interleukin (IL)-1 receptor antagonist, IL-4, IL-6, IL-10, IL-11, and IL-13

+[Term]
+id: GO:0141173
+name: symbiont-mediated suppression of host pro-inflammatory cytokine production
+namespace: biological_process
+def: "A process by which a symbiont inhibits or disrupts pro-inflammatory cytokine production in the host organism. Pro-inflammatory cytokines include: IL-1, IL-12, IL-18, TNF, IFN-gamma, and GM-CSF. The host is defined as the larger of the organisms involved in a symbiotic interaction." [GOC:pg]
+synonym: "negative regulation by symbiont of host pro-inflammatory cytokine production" EXACT []
+synonym: "suppression by symbiont of host pro-inflammatory cytokine production" EXACT []
+synonym: "suppression by symbiont of host pro-inflammatory cytokine secretion" RELATED []
+is_a: GO:0140133 ! symbiont-mediated suppression of host cytokine production
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/27129" xsd:anyURI
+created_by: pg
+creation_date: 2024-02-22T16:33:40Z
+
+[Term]
+id: GO:0141174
+name: symbiont-mediated suppression of host anti-inflammatory cytokine production
+namespace: biological_process
+def: "A process by which a symbiont inhibits or disrupts anti-inflammatory cytokine production in the host organism. Anti-inflammatory cytokines include: interleukin (IL)-1, IL-4, IL-6, IL-10, IL-11, and IL-13. The host is defined as the larger of the organisms involved in a symbiotic interaction." [GOC:pg]
+synonym: "negative regulation by symbiont of host anti-inflammatory cytokine production" EXACT []
+synonym: "suppression by symbiont of host anti-inflammatory cytokine production" EXACT []
+synonym: "suppression by symbiont of host anti-inflammatory cytokine secretion" RELATED []
+is_a: GO:0140133 ! symbiont-mediated suppression of host cytokine production
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/27129" xsd:anyURI
+created_by: pg
+creation_date: 2024-02-22T16:35:54Z

@genegodbold please provide references.

@genegodbold to provide reference for the proteins that inhibit cytokine signaling

+[Term]
+id: GO:0141184
+name: symbiont-mediated activation of host anti-inflammatory cytokine signaling
+namespace: biological_process
+def: "A process in which a symbiont subverts an anti-inflammatory cytokine signaling pathway in the host organism by initiating, promoting, or enhancing its activation." [PMID:23284742, PMID:27437422, PMID:29924996]
+is_a: GO:0052028 ! symbiont-mediated activation of host signal transduction pathway
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/27129" xsd:anyURI
+created_by: pg
+creation_date: 2024-03-19T13:30:47Z

Add related synonym cytokine storm


ee databases look deleted

my ee database sync seems off,
Nginx configuration	wp wpfc (enabled)
PHP Version	7.0
HHVM	enabled
SSL	enabled
SSL PROVIDER Lets Encrypt
SSL EXPIRY DATE Wed May 29 08:37:53 EDT 2019
access_log	/xxxxxxxx/mahirsayar.com/logs/access.log
error_log	/xxxxxxxx/mahirsayar.com/logs/error.log
Webroot	/xxxxxxxx/mahirsayar.com
DB_NAME	deleted
DB_USER	deleted
DB_PASS	deleted
i can see all the correct info in my wp-config.php - and the site works fine,
but i can't upgrade because i cant seem to get ee to accept whats actually there..
System Information

[mahirsayar.com$ sudo ee cli info
usage: ee (sub-commands ...) [options ...] {arguments ...}
ee: error: unrecognized arguments: cli info
] ee cli info

[mahirsayar.com$  lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic
mahir@txaqo:/var/www/mahirsa ] lsb_release -a

[ ] docker version

[ ] docker-compose version

@puccaso This issue seems to be of EasyEngine v3. Since we've dropped support of v3, I'm closing this issue. However you can still post this issue in community forums -  and someone might help you out.

See, if i could get EE to just accept the databases are present, i'd be able to free myself of v3, and be happy!
i'll try on the forums. thanks.
:(


New version: BRL-CAD.brlcad version 7.40.2

Pull request has been created with komac v2.6.0 :rocket:

Resolves #192947

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run

@wingetbot run

This package installs and launches normally in a Windows 10 VM.


Not always detecting closed connections on Fly.io

This follows on from: https://community.fly.io/t/upstash-redis-and-could-not-send-http-request-to-instance-connection-error-timed-out-logs/10104
The Redis service on Fly.io (provided by Upstash) closed idled connections after an hour, but ioredis didn't always recognise it. (They increased it to a day to reduce the number of errors. I've added a ping to our app's health check, which keeps the connection alive.)
I added logging for the various events ioredis emits and could see that sometimes it would recognise the connection had closed and reconnect, but sometimes it didn't. When the connection was then used, any command would just time out.
There are a few things here:

ioredis doesn't always recognise closed connections.
A 'command timeout event would be useful (for logging).
A regular ping setting would be useful to keep connections alive.

Thanks for reaching out! It would be helpful if we can reproduce the issue locally. Not sure if the keepAlive option works for the issue.

A regular ping setting would be useful to keep connections alive.

It's easy to implement this in app code so that's a major reason why it's not built in.

@luin what is the documentation for keepAlive?

It's the native one supported by Node.js: https://nodejs.org/api/net.html


Using Python sortedcontainers vs blist

First, thanks for a great package. I'm exploring real-time Django solutions and am currently evaluating this.
I noticed that the project is using the Python blist module, in particular the sorteddict data type is used for expiring subs by time. As the author of the sortedcontainers module, I wondered why. SortedContainers is a pure-Python implementation of SortedList, SortedDict, and SortedSet data types. For your use pattern of getting, setting, deleting, and iterating sortedcontainers.SortedDict looks faster than blist.sorteddict. Take a look at the benchmarks at http://www.grantjenks.com/docs/sortedcontainers/performance.html#id2
But then I noticed that your typical install instructions are a list of Debian packages. And sortedcontainers doesn't have a Debian package (though someone recently requested that (https://github.com/grantjenks/sorted_containers/issues/29) so I wanted to ask:

How did you choose blist?
Is the lack of a Debian package for sortedcontainers a deal breaker?
Would you accept a pull request that changed the dependency and made the code a bit more idiomatic? In particular, I'd be really curious to test any benchmark that might be affected by such a change.

Thanks for reading.

You guessed right: the reasoning was Debian package availability. Lack of a package for sortedcontainers is basically a dealbreaker since we wouldn't be able to make a proper Debian package for Pushpin itself.
We can throw @jannic at this problem if you'd like the assistance. He handles our Debian packages.

As Grant already noticed, there is an ITP by @sandrotosi for packaging sortedcontainers, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790504 for details. Looking at the packages Sandro maintains, he seems to have much more experience packaging python packages than I do. Still, Sandro, if you need any assistance, feel free to contact me!

Thanks @jannic but I guess I'm good here, we are just waiting for the package to be approved into our repository (it is needed only the first time a package 'appears' for inclusion into Debian)

sortedcontainers has just been accepted into Debian (unstable)

Thanks @sandrotosi !!!
@jkarneges Does this satisfy your need for a Debian package? It looks to be available in sid (unstable).

Yes. I think we should make the code work both ways for a little while though, at least until the package gets picked up by Ubuntu 15.10. Can you make a PR that opportunistically uses sortedcontainers?

Pull request merged to develop branch: #47231
Let me know when/if you want me to update the wiki pages.

Sure, you can update the wiki. Just be sure to note it as optional for now. After October we can change the default apt-get instructions.

Thanks. Done.

Thanks, looks good. I'll also update the Homebrew package to use sortedcontainers when I release a new version later this week.
The Debian packages will be updated when it makes sense to. We are considering setting up our own apt repo for backports, so this could happen sooner than later.


LE certificates not renewing

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
ACME issued LE certificates failed to renew and expired.
Investigation led me to traefik creating dual entries in the acme-dns file.

The "expected entry" using the domain named used.
And an "extra entry" using [GUID].acme-dns-domain, the GUID here doesn't match the GUID used for the CNAME DNS entry.

To the ACME-REST-API an update is posted using the "extra entry" while LE checks the "expected entry", resulting in a non-match.
What did you see instead?
Downgrade to 2.8.8 make my certificate renewed immediately.
Haven't tried intermediate versions.
What version of Traefik are you using?
Version:      2.10.1
Codename:     saintmarcelin
Go version:   go1.20.3
Built:        2023-04-27T14:52:35Z
OS/Arch:      linux/amd64
What is your environment & configuration?
  - --certificatesresolvers.le.acme.email=my@email
  - --certificatesresolvers.le.acme.storage=/certificates/acme.json
  - --certificatesresolvers.le.acme.keytype=EC384
  - --certificatesresolvers.le.acme.dnschallenge=true
  - --certificatesresolvers.le.acme.dnschallenge.provider=acme-dns
  - --certificatesresolvers.le.acme.dnschallenge.resolvers=<IP_ADDRESS>:53,<IP_ADDRESS>:53
  - --certificatesresolvers.le.acme.dnschallenge.delayBeforeCheck=20
  - --log.level=INFO

If applicable, please paste the log output in DEBUG level
The domain is changed to: the-domain.ext
The ACME-DNS is changed to: my-acme-dns.ext
level=error msg="Error renewing certificate from LE: {the-domain.ext [*.the-domain.ext]}" ACME CA="https://acme-v02.api.letsencrypt.org/directory" error="error: one or more domains had a problem:\n[*.the-domain.ext] time limit exceeded: last error: NS ns1.my-acme-dns.ext. did not return the expected TXT record [fqdn: 4c4495a6-251c-4dab-9912-f36feef12e33.my-acme-dns.ext., value: tcNgp9jvjhPMm4OYp2AS_jnRx-4A93BIYD0pgqjY0ac]: lGJWtWDN44jZe_rcWMx1If5w2K43d2S-o9xap96QQ14 ,_MunTCPqhrZFeokO8u4jekZZdGThqkkOdgQWQIffyGI\n[the-domain.ext] time limit exceeded: last error: NS ns1.my-acme-dns.ext. did not return the expected TXT record [fqdn: 4c4495a6-251c-4dab-9912-f36feef12e33.my-acme-dns.ext., value: QNZ-EdhYxzooA0wYJl8OYQVjr3ChG-hJcrPut7vbkUA]: lGJWtWDN44jZe_rcWMx1If5w2K43d2S-o9xap96QQ14 ,_MunTCPqhrZFeokO8u4jekZZdGThqkkOdgQWQIffyGI\n" providerName=le.acme

Hello,
this problem has been fixed in lego v4.11.0 (https://github.com/go-acme/lego/pull/1863).
lego has been updated in #9883.
This will be a part of the next bug fix release (traefik v2.10.2)
Duplicate of #9879


[GLUTEN-1632][CH]Daily Update Clickhouse Version (20230713)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

Compatible with current gluten


perf: Build batches directly vs queuing messages

Queuing messages causes a lot of pooled writers in memory and some people have been concerned about that
see https://discord.com/channels/343440455738064897/956506590062735390/956506591656554536 "27k arrays -> 41mb"
Note there is space for improvement here, we still copy the batch twice, by reserving space in the front of a batch for the timestamp and swapping the buffer/position of the network writer we can reduce that to copying the message only once (I'll gladly add that if we're going forward with this PR)

and swapping the buffer/position of the network writer
or just changing the NetworkWriter to be an out param I guess if we want to change the API

superseeded by #3130


An initial commit for Firebase Event Proxy

I know I still need to write integration tests.
Here were Les' original comments and my responses:

Apache License should be on all files.

Done

Some comments are helpful.

Added some comments.

Vertical whitespace is also helpful - makes things a bit more readable.

Added a whitespace.

Your up status isn't dynamic it will be coming from something other than the jetty servlet (Flex it's nginx, standard is something else)

In my opinion this sample doesn't really require a status. I just useful for detecting when the app is really having problems.

HTTPS isn't required.

I only noticed the usage of https for https://gae-fb-proxy.firebaseio.com/. I believe this encrypts traffic between the sample app and Firebase, which is a desirable behavior.

You do nothing to solve the issue for the user in your catches, it's ok in what I read, but we generally frown on it.

ACK.

I'm going to merge this.
A couple of things need to happen at some point (soon).

In your pom, please reference the parent pom in ../../pom.xml
Add your app to the listed apps for testing and codestyle. (in the parent pom.xml)

I've created a new PR to address those issues:
https://github.com/GoogleCloudPlatform/java-docs-samples/pull/239
Do you automatically get notified of these pull requests, or should I
continue to notify you?
On Thu, May 12, 2016 at 9:55 AM, Les Vogel<EMAIL_ADDRESS>wrote:

I'm going to merge this.
A couple of things need to happen at some point (soon).

In your pom, please reference the parent pom in ../../pom.xml
Add your app to the listed apps for testing and codestyle. (in the
parent pom.xml)

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/java-docs-samples/pull/236#issuecomment-218818742

I do get notified, but if you add @lesv then there is a tag that brings it to my attention.
I'm behind about 3500 emails (mostly buganizer / git) due to CDCP.  I hope to go through them while I'm on vacation. (or I might just start clean)  I do see anything from github that mentions Java in the subject.


Added a bash component for Have I been Pwned

Port of my pwned program
Closing Issue #144
Pull Request Label:

[ ] Bug
[ ] New feature
[ ] Enhancement
[x] New component
[ ] Typo

Pull Request Checklist:

[x] Have you followed the guidelines for contributing?
[x] Have you checked that there aren't other open pull requests for the same fix or component?
[ ] Have you ran the tests locally with bats tests?

It has been 11 days, and no update

Sorry super busy with final projects for school at the moment, might have a chance to look at these over thanksgiving break

Could you have this script check for the last 3-5 places you have been breached. I think just having the last place isn't as useful as this script could be (would be even better if it generated a list of all the places you have been breached)

I’ll be able to do it only with the help of jq. I think it’s time to add it as a dependency cause it’s easier than python. Else I’ll only be able to look at it after my exams (around 7-8th December ) I think once jq’s requirement is filled a lot can happen

The desired output can be achieved via jq. Look at my repo named pwned

I do agree that python does not make these things easy but it is a huge push of this repo to not have dependencies like that. I think the project as a whole is a lot more attractive when it can be installed and everything just works. Otherwise I would have never bothered to make the httpGet function and would have forced every user to have curl installed. It is very possible to utilize a loop to go through a json response until we hit an error an example of what I am referring to can be found in the cloudup tool: https://github.com/alexanderepstein/Bash-Snippets/blob/master/cloudup/cloudup#L184

Alas, the script now shows every breach

due to a bug, i'm not able to edit my pull request. therefore closing this and opening a new pr


Fixed a typo in deployment.md

Found an errant 'yuo' in the 'Using Cake' paragraph
I don't know why it lit up with so much on the merge comparison.

Thanks! Probably just highlighted the whole long line...


Parquet Files Getting Emptied After Delete ParquetWriter

Describe the bug, including details regarding any error messages, version, and platform.
Version: 1.14.1
I got the following code:
(1) writer = AvroParquetWriter
            .builder<GenericRecord>(ParquetOutputFile(localFile))
            .withSchema(SCHEMA)
            .build()
(2) writer.write(genericRecord)
(3) writer.close()
(4) writer = AvroParquetWriter
            .builder<GenericRecord>(ParquetOutputFile(localFile2))
            .withSchema(SCHEMA)
            .build()

After the third line, I can see the file with the data (genericRecord), and read it.
For some reason, after the 4th line, the file is getting empty. It contains no data and weight 0 bytes.
When trying to read it I am getting:
File(<some_name>) cannot be read as parquet. File matching that expression not found.
Without the 4th line, the file and its content remains steady.
Component(s)
No response

Thanks for reporting the issue! Could you provide the complete code to reproduce it?

Sadly I can't export it, but it is something just like what I sent.
The problem occur in line 4, where I created a new writer and delete the ole one (the garbage collector delete the old one because it is the same var name). At that moment, it emptied the file.

My example code runs fine, and I can’t reproduce your issue. Could you take a look at my sample code? The code is as follows:
import java.io.IOException;
import java.nio.file.Paths;
import org.apache.avro.Schema;
import org.apache.avro.SchemaBuilder;
import org.apache.avro.generic.GenericData;
import org.apache.avro.generic.GenericRecord;
import org.apache.parquet.avro.AvroParquetWriter;
import org.apache.parquet.hadoop.ParquetWriter;
import org.apache.parquet.io.LocalOutputFile;

public class _02_Parquet_Example {
  public static void main(String[] args) throws IOException {
    // Define the Avro schema
    Schema schema = SchemaBuilder.record("User")
        .fields()
        .name("name").type().stringType().noDefault()
        .name("age").type().intType().noDefault()
        .endRecord();

    // Create a GenericRecord
    GenericRecord genericRecord = new GenericData.Record(schema);
    genericRecord.put("name", "John Doe");
    genericRecord.put("age", 30);

    // Parquet file paths
    String localFilePath = "./output-file1.parquet";
    String localFilePath2 = "./output-file2.parquet";

    LocalOutputFile localOutputFile = new LocalOutputFile(Paths.get(localFilePath));
    LocalOutputFile localOutputFile2 = new LocalOutputFile(Paths.get(localFilePath2));

    // Write to the first Parquet file
    ParquetWriter<GenericRecord> writer = AvroParquetWriter
        .<GenericRecord>builder(localOutputFile)
        .withSchema(schema)
        .build();
    writer.write(genericRecord);
    writer.close();

    // Write to the second Parquet file with the same record
    writer = AvroParquetWriter
        .<GenericRecord>builder(localOutputFile2)
        .withSchema(schema)
        .build();
    writer.write(genericRecord);
    writer.close();

    System.out.println("Data written to Parquet files successfully.");
  }
}

@tomnoah1

You are writing it again.
Try:
writer = newWriter()
Instead of:
// Write to the second Parquet file with the same record
    writer = AvroParquetWriter
        .<GenericRecord>builder(localOutputFile2)
        .withSchema(schema)
        .build();
    writer.write(genericRecord);
    writer.close();

Now when I took a second look I see we did on the second initialization:
writer = AvroParquetWriter
        .<GenericRecord>builder(localOutputFile)
        .withSchema(schema)
        .build()

Hence, we accidentally used again localOutputFile instead of localOutputFile2, and I guess thats what cause the problem.
A new writer to the same filename with the same path.

@tomnoah1  If there are no other issues with this, you can close it. Thanks.

Thanks @FlechazoW for the help!


Create Itinerary: Title/Description screen

In this screen, the user should be able to write the title and the description of the itinerary. This task deals with the Frontend UI of the screen

resolved in PR #214


selected item in "document structure" section of custom mapping should be styled

Currently it is not styled any differently than the background, making it hard to discern which element is currently selected.
Observation that it uses the css style "selected" which might already be in use for something else.

commit 391ab8c


Port frontend to a Vue-powered SPA

This branch started as an effort to port the frontend to use Elm, but Elm was much more difficult to figure out than Vue, which I think will be beneficial to the project overall in the future.

Coverage remained the same at 99.539% when pulling 610317422ce0d455a2bb6ed1fd23f3b65c65ef3f on elm into d4625a58aeded0ccfc05e106cac12cf93762f9dc on master.


unable to finish this tutorial, where is the "Manifest node"

really can't find the "Manifest node"

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

ID: 3edfcdaa-2fac-15dd-003f-c2133daa368d
Version Independent ID: 85d95dfa-14d0-30f7-593c-0bc0e098320b
Content: Custom actions in Outlook form regions - Visual Studio
Content Source: docs/vsto/custom-actions-in-outlook-form-regions.md
Product: visual-studio-dev15
GitHub Login: @John-Hart
Microsoft Alias: johnhart

@peterremote1980 Thanks for letting us know; this content set is in our backlog to update. @John-Hart, FYI.

thanks Terry G Lee

this is fixed with PR #4107
#please-close


.Net: Specialized SSE parser as Utility

Motivation and Context

Closes #5610
Description

Specialized SSE parser implementation as internal utilities.
Code is partially borrowed from Azure sdk.
cc: @stephentoub @RogerBarreto @markwallace-microsoft
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

@Krzysztof318 can you please run dotnet format


revive timezone support

Hi Daniel,
based on Ivan Mirićs initial timezone support, I ported it to the current
schedule module.
The hard part doing it in an optional fashion isn't done yet.
I don't have a brilliant idea, how to separate the two in an useful way. The usual subclass approach would not get rid of the additional dependency for the schedule package, while refactoring the two classes into dependant projects is complete overkill. I'm not willing to do the third way of forking your project.
The forth approach: just merge is my favorite still. The additional complexity of dealing with timezones isn't exactly nice, but is a recurring problem, when it comes to scheduling. OTOH, allowing both naive and offset aware datetimes isn't appealing conceptually as well.

Why does travis not install the necessary requirements, as noted in setup.py?

Why does travis not install the necessary requirements, as noted in setup.py?

It should do it now that we're just running Tox on CI (#79).

Thanks for the PR 😃  I can see where timezone support would be useful!
The main thing I'm worried here is that we're shipping our own timezone definitions – Ideally we should pull them in from some other module so that the maintenance burden isn't on us.
Any ideas on how we could accomplish that?

Hi Daniel, nice to see you up and alive ;)
Well, the definition, which timezones have which offset, is pretty fixed, isn't it?
Okay, given the tectonic movement, these offsets might change in a few hundred thousands of years. Not sure, if schedule is still used at that time. Invention of new timezones is probably more frequent, but also not THAT common ;)..
Those are used in order to not deal with the timezones itself, e.g. to support parser of dateutil, which is a pretty common module, if you need to deal with timezones...
I haven't investigated other possibilities, yet, but they will come with a price: another dependency.

Hi Daniel, nice to see you up and alive ;)

Thanks ;)

Well, the definition, which timezones have which offset, is pretty fixed, isn't it?

That's what I thought too but it turns out it's more complicated than that :) The Olson tz database changes quite frequently: https://en.wikipedia.org/wiki/Tz_database The main reason seems to be updates in daylight savings time. I'm not looking forward to having to keep up with that as a maintainer :)
The alternative that I'd prefer is that we add an optional argument representing the timezone or the tz offset – instead of passing a human readable identifier (== the string tz abbreviation).
Then people could just use pytz or whatever other tz database they'd like to use to lookup the offset – alleviating schedule from the maintenance burden.
This needs to be fleshed out further, but how about something like this:
from pytz import timezone

EST = timezone('US/Eastern')
schedule.every().day.at("10:00", EST)

schedule.every().day.at("10:00", pytz.utc)

Does that make sense?

On Mittwoch, 9. November 2016 05:50:35 Daniel Bader wrote:

Hi Daniel, nice to see you up and alive ;)

Thanks ;)

Well, the definition, which timezones have which offset, is pretty fixed,
isn't it?
That's what I thought too but it turns out it's more complicated than that
:) The Olson tz database changes quite frequently:
https://en.wikipedia.org/wiki/Tz_database The main reason seems to be
updates in daylight savings time. I'm not looking forward to having to keep
up with that as a maintainer :)

But that's my point. Due to using dateutil, the Olson tz database is used behind the
scenes.
The mapping of timezone offsets doesn't change. What's changing on a regular base is,
when and if some daylight savings time is applied in a certain TZ.
Check the diffs: it's just an offset mapping. An those values don't change that often, as
these relate to "quite stable" geographic coordinates (e.g. tectonic drift)...

The alternative that I'd prefer is that we add an optional argument
representing the timezone or the tz offset – instead of passing a human
readable identifier (== the string tz abbreviation).
Then people could just use pytz or whatever
other tz database they'd like to use to lookup the offset – alleviating
schedule from the maintenance burden.
This needs to be fleshed out further, but how about something like this:
from pytz import timezone

EST = timezone('US/Eastern')
schedule.every().day.at("10:00", EST)

schedule.every().day.at("10:00", pytz.utc)

Does that make sense?

Sure, the only downside, I see, are schedule events from config files. In my proposed
scheme, the TZ argument is passed though and will just work. Your scheme places the
burden on the apps config parser code, that, at some point, will want to use a similar
mapping.
I'm pretty sure, that the mapping will not change in the next decade, because, even if
some pacific islands decide to change their timezone assignment, they hopefully will
choose an existing one from their neighbors in flavor of inventing some new ones, that
nobody knows.
Cheers,
Pete

Closing this for now, we need to resolve some other TZ issues with schedule first and I think we should go for an implementation that doesn't include a TZ table. Thanks for your PR though!

@dbader the system itself already contains the most complete timezone table, complete with DST oddities that is possible to have, I'm assuming this is what decent existing time libraries use. I just looked through pendulum for instance and it doesn't have that data hardcoded anywhere and reads it directly from the system. The only data table they have is converting windows timezone names to  I'm assuming the standard python libs do the same, I haven't verified that though...
anyways, including and maintaining a TZ table here is definitely the wrong idea, but the solution is already available. I imagine you wouldn't want to include pendulum as a dependency though, but some of it's code could be incorporated to accomplish this.


"Check current project" doesn't work in QtCreator 4.1.0 for Linux (x64)

Using QtCreator 4.10 in Linux (Ubuntu Gnome 16.04.1 and Ubuntu 16.04.1), the option Tools -> CppCheck -> Check current project doesn't work.
No action appears to be taken when the option is selected (or when the shortcut [Alt+C, Ctrl+A] is used).

I tested Windows version and it works fine.

Hi.
Tested on several systems including 16.04.1 - works for me.
You can enable show binary's output option to see some details about cppcheck invocation.

Do a test with Autotools project.
You need to enable AutotoolsProjectManager in Help -> About Plugins -> Build Systems.
When I did a test with Qmake project, worked without problems. But the same didn't occurs with an Autotools project.

Looks like it doesn't work only when you open project for the first time. Possible qtc can't provide project's files list when plugin requests it. It starts working when you change active project.
However, now plugin reparses project if it looked empty before.
QtcCppcheck-4.1.0-linux-x64.tar.gz


Clarify dependencies

e.g. to what extent do we depend on VTK? I personally had trouble getting Python VTK set up on my Ubuntu 18.04 system.

Also scipy

Instruct if it's necessary to install Python modules in a certain way with the Firedrake environment activated.

Don't install as user with pip in Firedrake environment.

Add section to README for installing modules in Firedrake environment.

I had to
sudo apt install python3-vtk7

It was important to also uninstall the python-vtk which I previously installed with pip, i.e.
pip3 uninstall python-vtk

and also something that had a missing DLL (reported with a Python error), e.g. with
sudo apt get install libsm6

@sajid3900 , would you let me know how installing VTK goes for you? I'll then add instructions to the README so that it's easier the next time.

I removed the VTK dependency as of 99569f136375b0a2a3ded315e3e7d46bea00b575 and moved my VTK plotting scripts, which are independent of Sapphire, to https://github.com/geo-fluid-dynamics/python-vtk-tools .

Having removed the VTK postprocessing module, there are no longer any dependencies other than what's included with Firedrake.


Use null-terminated strings for NX attribute tags

See: https://github.com/DiamondLightSource/durin/issues/28
Currently, the durin plugin for XDS looks for NX tags as with strcmp, so we should write c strings at least for anything it needs. It's probably best just to do it for anything in case there are any other c utilities we use which look for fields in the same way.
Acceptance criteria:

we use null-terminated strings in our .nxs files
they can be processed with XDS/durin

See https://stackoverflow.com/questions/38267076/how-to-write-a-dataset-of-null-terminated-fixed-length-strings-with-h5py for discussion of string types in h5py

On further discussion, won't fix this here unless it comes up again in the future, now fixed in Durin https://github.com/DiamondLightSource/durin/pull/29


Per-node performance metrics collection

Please add a section to this document to cover the additional configuration required for each node in the HDInsight cluster to send performance metrics to the Log Analytics workspace enabled for the HDInsight cluster.
To do this, navigate to the Log Analytics Workspace --> Advanced Settings. Then click Data --> Linux Performance Counters --> Check "Apply below configuration to my machines” checkbox, then add the “Processor(*)%Processor Time” counter and finally click the “Save” button.
This configuration is required for the "Management solution" to surface per-node performance information using the default CPU, Memory and Logical disks included in the graph.
Data will being flowing to the workspace after several minutes and then light up those per-node performance tiles.

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

ID: 6015786a-01a5-c01d-82bb-f375b5dc3a00
Version Independent ID: 704bde40-76d9-e261-e0e0-ef7e5de6724b
Content: Use Azure Monitor logs to monitor Azure HDInsight clusters
Content Source: articles/hdinsight/hdinsight-hadoop-oms-log-analytics-tutorial.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

@richardspitz  Thanks for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.

Fixed in this PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/84320

@richardspitz thanks for helping us improve the document with these new features. We're going to link to the official Azure monitor guide so that the customers can find updated guidance easily if things change. Thanks again.

#please-close


Question

Would you be willing to update this and have it working with updated features for some donations?

Honestly, probably not. I don't have much time. The features that aren't already implemented probably won't get implemented (they require much work) in the near future. If you have problems with something that is implemented, I could try to fix that maybe. Just open a new issue for that.

If you would or when you get the time to update the auto time warp or add a feature so it will automatically go to the next morning after the keepnet is full would be greatly appreciated


Fix League\CommonMark\Converter::convertToHtml() must be of the type string, null given exception

Laravel v6.10.0 switched to "league/commonmark instead of erusev/parsedown for mail markdown"
See: https://github.com/laravel/framework/pull/30982
league/commonmark doesn't accept null to the parse method. So this small update pass in an empty string if it is null.
Alternatively someone can make a PR at laravel/framework too to allow accepting null.

A new inspection was created.

Okay got from laravel/framework side that they won't change back to old behaviour of allowing null as they closed my issue so this is good to merge.


AVX-512 VNNI functions

https://software.intel.com/sites/landingpage/IntrinsicsGuide/#avx512techs=AVX512_VNNI
For current progress, see https://github.com/simd-everywhere/implementation-status/blob/main/x86.md#avx512_vnni

Hi, I was planning on taking a look at this PR next. I Was going to implement the functions along the lines of what's described here: https://en.wikichip.org/wiki/x86/avx512_vnni using madd and maddubs.
Let me know if there are any other considerations.

It kind of depends on what you want to get out of the exercise.  If you just want to add basic support, an implementation like madd/maddubs would work well enough and I'd certainly be happy to accept the patch.
If you're trying to get a bit more out of this then these functions are actually a really good learning opportunity if you'd like to put in a bit more time and effort. I'd still suggest starting with a basic implementation of one or two functions, but then there are some interesting opportunities for creating more optimized composable implementations of some of the operations this function performs internally that aren't part of the ISA extensions.

These are done! https://github.com/simd-everywhere/implementation-status/blob/main/x86.md#avx512_vnni


feat: voice text support

What type of pull request is this?

[x] Non-breaking code change
[ ] Breaking code change
[ ] Documentation change/addition
[ ] Tests change

Description

One may say, "Wolfhound, you are insane.  How does one implement a feature so quickly? 😌 "
To that, I say thank you. Thank you to the person who made this library so freaking easy to contribute to. The one and only @LordOfPolls
At first, I thought this was going to be difficult. Scared that the Discord developers would overcomplicate things and add more endpoints. But I was wrong. I thought about it for about 5 seconds. Typed those magical words MessageableMixin, and voilà, a perfectly working text in voice channel. I reflect on this event and think, "Maybe d.py will add it in 5 more months". This makes be proud to be a part of N.A.F.F. The name really does stand true, we are not ~fucking~ freaking fork.
Changes

Add MessageableMixin to GuildVoice

Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[x] I've tested my code

Imma be so sad if this is not all the changes that needed to be made LOL

As much as i want to take credit - the mixin system was certainly not just my creation. The bulk of the credit should really go to @artem30801 @benwoo1110 and @zevaryx - all of which contributed to the original channel structure.


React Capstone Project - Metrics WebApp

Video link: https://www.loom.com/share/13f1299bbdcf41ccb736e9559f75864d
In this final project in Microverse React/Redux module, I built a mobile web application that checks a list of numeric values. The project is a SPA built with react-redux. It gets data from the API and stores it in the redux store.
I implemented the following in this project:

Got data from Narrative API(Covid-19 data).
Built a homepage that displays a list of items that can be filtered.
Built a details page that provides more information about the filtered item.
Created unique routes for each page within the SPA.
Styled app using provided design guidelines.

Kindly review my code.
Thank you!

Thank you for the review, I have implemented all the changes.
Kindly re-review my code.
Thanks!


[WFARQ-134] Upgrade Arquillian to 1.7.0.Alpha14 and TestNG to keep co…

…nsistent with what Arquillian is using.
https://issues.redhat.com/browse/WFARQ-134
Signed-off-by: James R. Perkins<EMAIL_ADDRESS>

This replaces #281


Magic DRC check failed

Description
With OpenLane tag 2022.08.16 vsdbabysoc_wrapper design passed Magic DRC stage without any errors.
With OpenLane tag 2022.08.17 flow failed with Magic DRC errors.
Environment
Please run the following set of commands in the OpenLane folder:

make survey || python3 ./env.py issue-survey
python3 ./env.py issue-survey
Kernel: Linux v3.10.0-1160.49.1.el7.x86_64
Distribution: centos 7
Python: v3.6.8 (OK)
Container Engine: docker v20.10.16 (OK)
OpenLane Git Version: 12a7e9ccd497950b07bf5aa1c19e34655148d60a
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

12a7e9c 2022-08-17T14:09:28+05:30 [BOT] Update OpenLane tag. (#72) - github-actions[bot] -  (HEAD -> main, origin/main, origin/HEAD)
3feaa36 2022-08-15T10:17:07-03:00 Unstable s01 (#71) - vijayan -  ()
42d70a1 2022-08-11T12:49:59+05:30 [BOT] Update OpenLane tag. (#70) - github-actions[bot] -  ()
---
Git Remotes

origin	https://github.com/The-OpenROAD-Project/OpenLane-MPW-CI.git (fetch)
origin	https://github.com/The-OpenROAD-Project/OpenLane-MPW-CI.git (push)

Reproduction Material

Upload a tarball containing the relevant design.
Due to file size limit uploaded here: https://slack-files.com/T01699QAZBQ-F03TYEQENF8-e1eda559ee
List the commands used to run the design.

respective CI logs can be found here:
2022.08.16 tag: https://jenkins.openroad.tools/blue/organizations/jenkins/OpenLane-MPW-CI-Public%2Fproduction-small-3/detail/PR-72/1/pipeline/443
2022.08.17 tag: https://jenkins.openroad.tools/blue/organizations/jenkins/OpenLane-MPW-CI-Public%2Fproduction-small-3/detail/PR-74/1/pipeline/497
Expected behavior
Clean Magic drc report.
Logs
[STEP 34]
[INFO]: Running Magic DRC (log: logs/signoff/34-drc.log)...
[INFO]: Converting Magic DRC Violations to Magic Readable Format...
[INFO]: Converting Magic DRC Violations to Klayout XML Database...
[ERROR]: There are violations in the design after Magic DRC.
[ERROR]: Total Number of violations is 1592
[INFO]: Saving current set of views in 'results/final'...
[INFO]: Generating final set of reports...
[INFO]: Created manufacturability report at 'reports/manufacturability.rpt'.
[INFO]: Created metrics report at 'reports/metrics.csv'.
[INFO]: Saving runtime environment...
[ERROR]: Flow failed.
[INFO]: The failure may have been because of the following warnings:
[WARNING]: Skipping Tap/Decap Insertion.

    while executing
"flow_fail"

   (procedure "quit_on_magic_drc" line 13)
    invoked from within
"quit_on_magic_drc -log $::env(drc_prefix).tr"
    (procedure "run_magic_drc" line 27)
    invoked from within
"run_magic_drc"
    (procedure "run_drc_step" line 9)
    invoked from within
"[lindex $step_exe 0] [lindex $step_exe 1] "
    (procedure "run_non_interactive_mode" line 52)
    invoked from within
"run_non_interactive_mode {*}$argv"
   invoked from within
"if { [info exists flags_map(-interactive)] || [info exists flags_map(-it)] } {
    if { [info exists arg_values(-file)] } {
        run_file [file nor..."
    (file "./flow.tcl" line 401)
make: *** [Makefile:170: quick_run] Error 1
make: Leaving directory '/tmp/workspace/_Public_production-small-3_PR-74@2/OpenLane'

Magic DRC Screenshot

@maliberty
Reproducer attached for Magic DRC check only here.
Let me know which stage test case you're looking for, I will attach or it can be easily reproduced at your from MPW CI repo.

is it in the power grid?  In that case pdn, otherwise detailed routing

PDN stage test case:
issue_reproducible.zip
DRT test case:
issue_reproducible.zip
If need macro LEF file for reference it can be found here: https://github.com/manili/vsdbabysoc_mpw3/tree/main/lef

@maliberty
Please check this issue can be fixed from OpenROAD or move to Magic issue?

The pipeline is now green.  Does this still need attention?

@maliberty
Sorry, I forgot to update that. I used set ::env(QUIT_ON_MAGIC_DRC) 0. So even though magic reports violations flow will complete.
But originally flow reports Magic DRC errors and still need to be fixed.

I opened the out.def in the pdn reproducer and I don't see anything that looks like the magic picture:

there is no cut shape where there is a violation shown.

@vijayank88 What's actionable here?

Just checked with Latest OpenLane tag: 2022.09.16 its passed Magic DRC check without any errors.