hxl-yml-spec-to-hxl-json-spec

Quick links:

"JSON processing specs for HXL data, David Megginson, 2021-03-11"

https://docs.google.com/presentation/d/17vXOnq2atIDnrODGLs36P1EaUvT-vXPjsc2I1q1Qc50/edit#slide=id.p

Test online

https://proxy.hxlstandard.org/api/from-spec.html

Let's do an proof of concept of the thing!

Maybe this
hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
and an file like this
- hsilo: "test1"
  hrecipe:
    - id: recipe1
      source:
        - iri: https://docs.google.com/spreadsheets/d/12k4BWqq5c3mV9ihQscPIwtuDa_QRB-iFohO7dXSSptI/edit#gid=0
          filters:
            - filter: with_columns
              with_columns: "#vocab+id+v_iso6393_3letter,#vocab+code+v_6391,#vocab+name"
            - filter: without_rows
              without_rows: "#vocab+code+v_6391="

could be a good starting point. But form my experience with Ansible (and very, very large Ansible playbooks) we could do from start allow parsing several YAML files at once and just output all the json specs line by line.
But the come to this point, the hdpcli needs to implement some way to at least concatenate more than one YAML file. (the part about include_file options may be something for later).

This is the yaml file (there is some extra markup, but ignore for now).
fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ cat tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml | grep "^[^#;]"
---
- hsilo:
    name: "test1"
    desc: from https://docs.google.com/presentation/d/17vXOnq2atIDnrODGLs36P1EaUvT-vXPjsc2I1q1Qc50/
  hrecipe:
    - id: example-processing-with-a-JSON-spec
      iri_example:
        - iri: https://data.humdata.org/dataset/yemen-humanitarian-needs-overview
          sheet_index: 1
      recipe:
        - filter: count
          patterns: "adm1+name,adm1+code"
          aggregators:
            - "sum(population) as Population#population"
        - filter: clean_data
          number: "population"
          number_format: .0f

This is the json spec result
fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
{
    "input": "https://data.humdata.org/dataset/yemen-humanitarian-needs-overview",
    "recipe": [
        {
            "aggregators": [
                "sum(population) as Population#population"
            ],
            "filter": "count",
            "patterns": "adm1+name,adm1+code"
        },
        {
            "filter": "clean_data",
            "number": "population",
            "number_format": ".0f"
        }
    ],
    "sheet_index": 1
}

fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml | hxlspec
ERROR (hxl.io): Skipping column(s) with malformed hashtag specs: #
Gov,Gov Pcode,Population
#adm1+name,#adm1+code,#population
Abyan,YE12,618892
Ad Dali',YE30,818507
Aden,YE24,1053455
Al Bayda,YE14,795107
Al Hodeidah,YE18,2996334
Al Jawf,YE16,633596
Al Maharah,YE28,175606
Al Mahwit,YE27,770920
Amran,YE29,1221908
Dhamar,YE20,2194159
Hadramawt,YE19,1551347
Hajjah,YE17,2630678
Ibb,YE11,3143818
Lahj,YE25,1076296
Ma'rib,YE26,1086663
Raymah,YE31,562930
Sa'dah,YE22,934201
Sana'a,YE23,1370798
Sana'a City,YE13,3296342
Shabwah,YE21,676408
Socotra,YE32,69004
Ta'iz,YE15,3104579

And actually, redirecting to command line hxlspec actually worked. Just a quick warning, but worked!
fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ pip3 show libhxl | grep Version
Version: 4.22

We need some way to make 'inline' data tables that could work an some way to test if an HXL Data processing specs is working (and needs to work offline).
This implies add some new attributes, in special the concept of inline data and expected result data. Or maybe the concept of 'example'.

Current example
fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ cat tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
# yaml-language-server: $schema=https://raw.githubusercontent.com/EticaAI/HXL-Data-Science-file-formats/main/hxlm/core/schema/hdp.json-schema.json

# How to run this file? Version tested: v0.7.4
# @see https://github.com/EticaAI/HXL-Data-Science-file-formats/issues/14#issuecomment-798454298

# To inspect the result (pretty print)
#     hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
# To pipe the result direct to hxlspec (first item of array, use jq '.[0]')
#     hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml | jq '.[0]' | hxlspec
# To pipe the result direct to hxlspec (first item of array, use jq '.[1]')
#     hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml | jq '.[1]' | hxlspec

---

# See also https://proxy.hxlstandard.org/api/from-spec.html
# http://json-schema.org/understanding-json-schema/
# Test schema online https://www.jsonschemavalidator.net/
# Validate schema here: https://www.json-schema-linter.com/
# TODO: better validate HERE https://jsonschemalint.com/#!/version/draft-07/markup/json

- hsilo: "test1"
  hrecipe:
    - id: recipe1
      _recipe:
        - filter: with_columns
          includes: "#vocab+id+v_iso6393_3letter,#vocab+code+v_6391,#vocab+name"
        - filter: without_rows
          queries: "#vocab+code+v_6391="
      exemplum:
        - fontem:
            iri: https://docs.google.com/spreadsheets/d/12k4BWqq5c3mV9ihQscPIwtuDa_QRB-iFohO7dXSSptI/edit#gid=0

- hsilo:
    nomen: "test1"
    descriptionem: from https://docs.google.com/presentation/d/17vXOnq2atIDnrODGLs36P1EaUvT-vXPjsc2I1q1Qc50/
  hrecipe:
    - id: example-processing-with-a-JSON-spec
      _recipe:
        - filter: count
          patterns: "adm1+name,adm1+code"
          aggregators:
            - "sum(population) as Population#population"
        - filter: clean_data
          number: "population"
          number_format: .0f
      exemplum:
        - fontem:
            iri: https://data.humdata.org/dataset/yemen-humanitarian-needs-overview
            _sheet_index: 1

fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
[
    {
        "input": "https://docs.google.com/spreadsheets/d/12k4BWqq5c3mV9ihQscPIwtuDa_QRB-iFohO7dXSSptI/edit#gid=0",
        "recipe": [
            {
                "filter": "with_columns",
                "includes": "#vocab+id+v_iso6393_3letter,#vocab+code+v_6391,#vocab+name"
            },
            {
                "filter": "without_rows",
                "queries": "#vocab+code+v_6391="
            }
        ]
    },
    {
        "input": "https://data.humdata.org/dataset/yemen-humanitarian-needs-overview",
        "recipe": [
            {
                "aggregators": [
                    "sum(population) as Population#population"
                ],
                "filter": "count",
                "patterns": "adm1+name,adm1+code"
            },
            {
                "filter": "clean_data",
                "number": "population",
                "number_format": ".0f"
            }
        ]
    }
]

Now the hdpcli --export-to-hxl-json-processing-spec, to generate the input parameter specified by the HXL data processing specs, should be as first item of an array. If using the internal language, this means put in something like hrecipe.[0].exemplum.[0].fontem.iri instead of hrecipe.[0].iri_example.[0].iri.
The idea of use 'exemplum' is because if one goal of recipes would be reusability, this means that any input data there would be... just as example/reference.
The inpact of this is that now, the first item when exporting will always be without example inputs, but the second one would be like before.
Both 'input_data' / 'output_data' actually are one way to express, as inline data, input data (to not use external link) and 'output_data' is if eventually we implement some way to use an recipe to be able to be tested on different proxies.
Also, the idea of 'input_data' / 'output_data', even if ignored by HXL data processing specs, can be used to just looking at one YAML file have an idea of what the recipe would do. (ok that the idea is actually test if really works, but at least for documentation it already serve!)

fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats/tests/hrecipe$ cat hello-world.hrecipe.hdp.yml
# cd tests/hrecipe
# hdpcli --export-to-hxl-json-processing-specs hello-world.hrecipe.hdp.yml
# hdpcli --export-to-hxl-json-processing-specs hello-world.hrecipe.hdp.yml | jq '.[1]' | hxlspec
---
- hsilo:
    nomen: hello-world.hrecipe.hdp.yml
    linguam: mul # https://iso639-3.sil.org/code/mul
  hrecipe:
    - id: example-processing-with-a-JSON-spec
      _recipe:
        - filter: count
          patterns: "adm1+name,adm1+code"
          aggregators:
            - "sum(population) as Population#population"
        - filter: clean_data
          number: "population"
          number_format: .0f
      # iri_example:
      #   - iri: https://data.humdata.org/dataset/yemen-humanitarian-needs-overview
      #     sheet_index: 1
      exemplum:
        # Example one
        - fontem:
            iri: https://data.humdata.org/dataset/yemen-humanitarian-needs-overview
            _sheet_index: 1

        # Example two includes both an inline data
        - fontem:
            # Note: fontem.datum not fully implemented. But the idea here is
            #       be able to create an ad-hoc table instead of use
            #       external input. So help show as quick example or...
            #       as some sort of unitary test for an HXL data processing
            #       spec!
            datum:
              - ["header 1", "header 2", "header 3"]
              - ["#item +id", "#item +name", "#item +value"]
              - ["ACME1", "ACME Inc.", "123"]
              - ["XPTO1", "XPTO org", "456"]
          objectivum:
            # Note: fontem.objectivum not fully implemented. But the idea here
            #       is (like the fontem.datum) work as ad-hoc table, but is
            #       really allow create some sort of unitary test for a HXL
            #       data processing spec!
            datum:
              - ["header 1", "header 2", "header 3"]
              - ["#item +id", "#item +name", "#item +value"]
              - ["ACME1", "ACME Inc.", "123"]
              - ["XPTO1", "XPTO org", "456"]

fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats/tests/hrecipe$ hdpcli --export-to-hxl-json-processing-specs hello-world.hrecipe.hdp.yml
[
    {
        "recipe": [
            {
                "aggregators": [
                    "sum(population) as Population#population"
                ],
                "filter": "count",
                "patterns": "adm1+name,adm1+code"
            },
            {
                "filter": "clean_data",
                "number": "population",
                "number_format": ".0f"
            }
        ]
    },
    {
        "input": "https://data.humdata.org/dataset/yemen-humanitarian-needs-overview",
        "recipe": [
            {
                "aggregators": [
                    "sum(population) as Population#population"
                ],
                "filter": "count",
                "patterns": "adm1+name,adm1+code"
            },
            {
                "filter": "clean_data",
                "number": "population",
                "number_format": ".0f"
            }
        ],
        "sheet_index": 1
    },
    {
        "input_data": [
            [
                "header 1",
                "header 2",
                "header 3"
            ],
            [
                "#item +id",
                "#item +name",
                "#item +value"
            ],
            [
                "ACME1",
                "ACME Inc.",
                "123"
            ],
            [
                "XPTO1",
                "XPTO org",
                "456"
            ]
        ],
        "output_data": [
            [
                "header 1",
                "header 2",
                "header 3"
            ],
            [
                "#item +id",
                "#item +name",
                "#item +value"
            ],
            [
                "ACME1",
                "ACME Inc.",
                "123"
            ],
            [
                "XPTO1",
                "XPTO org",
                "456"
            ]
        ],
        "recipe": [
            {
                "aggregators": [
                    "sum(population) as Population#population"
                ],
                "filter": "count",
                "patterns": "adm1+name,adm1+code"
            },
            {
                "filter": "clean_data",
                "number": "population",
                "number_format": ".0f"
            }
        ]
    }
]

fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ cat tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
# yaml-language-server: $schema=https://raw.githubusercontent.com/EticaAI/HXL-Data-Science-file-formats/main/hxlm/core/schema/hdp.json-schema.json

# How to run this file? Version tested: v0.7.4
# @see https://github.com/EticaAI/HXL-Data-Science-file-formats/issues/14#issuecomment-798454298

# To inspect the result (pretty print)
#     hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
# To pipe the result direct to hxlspec (second item of array, use jq '.[1]')
#     hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml | jq '.[1]' | hxlspec
# To pipe the result direct to hxlspec (4º item of array, use jq '.[1]')
#     hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml | jq '.[3]' | hxlspec

---

# See also https://proxy.hxlstandard.org/api/from-spec.html
# http://json-schema.org/understanding-json-schema/
# Test schema online https://www.jsonschemavalidator.net/
# Validate schema here: https://www.json-schema-linter.com/
# TODO: better validate HERE https://jsonschemalint.com/#!/version/draft-07/markup/json

- hsilo: "test1"
  hrecipe:
    - id: recipe1
      _recipe:
        - filter: with_columns
          includes: "#vocab+id+v_iso6393_3letter,#vocab+code+v_6391,#vocab+name"
        - filter: without_rows
          queries: "#vocab+code+v_6391="
      exemplum:
        - fontem:
            iri: https://docs.google.com/spreadsheets/d/12k4BWqq5c3mV9ihQscPIwtuDa_QRB-iFohO7dXSSptI/edit#gid=0

- hsilo:
    nomen: "test1"
    descriptionem: from https://docs.google.com/presentation/d/17vXOnq2atIDnrODGLs36P1EaUvT-vXPjsc2I1q1Qc50/
  hrecipe:
    - id: example-processing-with-a-JSON-spec
      _recipe:
        - filter: count
          patterns: "adm1+name,adm1+code"
          aggregators:
            - "sum(population) as Population#population"
        - filter: clean_data
          number: "population"
          number_format: .0f
      exemplum:
        - fontem:
            iri: https://data.humdata.org/dataset/yemen-humanitarian-needs-overview
            _sheet_index: 1

fititnt@bravo:/workspace/git/EticaAI/HXL-Data-Science-file-formats$ hdpcli --export-to-hxl-json-processing-specs tests/hxl-processing-specs/hxl-processing-specs-test-01.hdp.yml
[
    {
        "recipe": [
            {
                "filter": "with_columns",
                "includes": "#vocab+id+v_iso6393_3letter,#vocab+code+v_6391,#vocab+name"
            },
            {
                "filter": "without_rows",
                "queries": "#vocab+code+v_6391="
            }
        ]
    },
    {
        "input": "https://docs.google.com/spreadsheets/d/12k4BWqq5c3mV9ihQscPIwtuDa_QRB-iFohO7dXSSptI/edit#gid=0",
        "recipe": [
            {
                "filter": "with_columns",
                "includes": "#vocab+id+v_iso6393_3letter,#vocab+code+v_6391,#vocab+name"
            },
            {
                "filter": "without_rows",
                "queries": "#vocab+code+v_6391="
            }
        ]
    },
    {
        "recipe": [
            {
                "aggregators": [
                    "sum(population) as Population#population"
                ],
                "filter": "count",
                "patterns": "adm1+name,adm1+code"
            },
            {
                "filter": "clean_data",
                "number": "population",
                "number_format": ".0f"
            }
        ]
    },
    {
        "input": "https://data.humdata.org/dataset/yemen-humanitarian-needs-overview",
        "recipe": [
            {
                "aggregators": [
                    "sum(population) as Population#population"
                ],
                "filter": "count",
                "patterns": "adm1+name,adm1+code"
            },
            {
                "filter": "clean_data",
                "number": "population",
                "number_format": ".0f"
            }
        ],
        "sheet_index": 1
    }
]


django-debug-toolbar

Django-debug-toolbar causes FileNotFoundError at /admin/ and prevents Django form finding static.
The error disappears if INTERNAL_IPS is commented but the toolbar does not appear.
Folling are settings.py and urls.py renamed in .txt
urls.txt
settings.txt

Which files cannot be found?
It's quite probable that the reason for this is a misconfiguration or a missing deployment step. But additional details and a full traceback would help greatly debugging this issue.

I am in development phase and so there is no deployment.  here is the traceback
http://dpaste.com/16CJDAT
Is this the appropriate way to give you full traceback?

@piscvau Is this still an issue or can this be closed?

Closing due to lack of response.


Image getting flushed to the right side of the  tag

Hi,
The image is getting flushed to the right side of the  tag leaving quite some space at left, top & bottom. In other words, image is not aligned centrally inside the  tag. I tried float or padding but with this part of the image is not visible when zooming. Any suggestions on how I can align the image centrally within the  tag?
Here is the code:

	<button class="zoom-in">+</button>
	<button class="zoom-out">-</button>
	<button class="reset">Reset</button>

I think this can be accomplished by setting an appropriate center value to the startTransform option. It will always reset to that transform.


change /accounts/ routes to /accounts/

I liked the idea of using usernames as IDs in the URLs, but it’s inconsistent with all the rest of our APIs, and could potentially cause issue with JSON API clients.
For example GET /accounts/jane-doe would return
{
    "links": {
        "self": "https://example.com/accounts/jane-doe"
    },
    "data": {
        "id": "def678",
        "type": "account",
        "attributes": {
            "username": "jane-doe",
        }
    },
    "relationships": {
        "profile": {
            "links": {
                "related": "https://example.com/accounts/jane-doe/profile"
            },
            "data": {
                "id": "def678-profile",
                "type": "accountProfile"
            }
        }
    }
}

But data.id is "def678", not "jane-doe". I'm not sure if this is JSON API compliant or not, but when in doubt, I'd rather avoid confusion.
Not using the username in the URLs also prevents issues with weird characters in usernames.

[x] start a pr #11
[x] make the fix (breaking change)
[x] review & merge

ping @patriciagarcia

done via #11


Skip EL part of graffiti when EL info not available

PR Description
We are currently filling it with something like NA0000, which is not beautiful, so we decided to skip it at all in this case.
Also behavior was updated to push UNKNOWN version in channel when it's not known due to failure or whatever, but do it only once per client start. So we could have normal log line with expected graffiti on start when execution client is not supporting the new API and it will be not noisy if there are issues with EL.
PS: I don't try to put more CL info in graffiti when EL version is unknown to make it simpler.
Fixed Issue(s)

Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

Isn't it better if the length requirements change if EL information is not available because less bytes are needed?

Also I think better to use null and remove UNKNOWN in some improbable case where some EL sends us same as UNKNOWN 😁


'NoneType' object has no attribute 'set_cookie'

Hi, Could you possibly help me to solve the problem when I start the server, thank you very much!
AttributeError at /
'NoneType' object has no attribute 'set_cookie'
Request Method: 	GET
Request URL: 	http://localhost:8000/
Django Version: 	1.9
Exception Type: 	AttributeError
Exception Value:
'NoneType' object has no attribute 'set_cookie'
Exception Location: 	C:\Users\dlwkwok\Envs\tweeter\lib\site-packages\django\middleware\csrf.py in process_response, line 229
Python Executable: 	C:\Users\dlwkwok\Envs\tweeter\Scripts\python.exe
Python Version: 	3.5.1
Python Path:
['C:\tweeter',
'C:\Users\dlwkwok\Envs\tweeter\Scripts\python35.zip',
'C:\Users\dlwkwok\Envs\tweeter\DLLs',
'C:\Users\dlwkwok\Envs\tweeter\lib',
'C:\Users\dlwkwok\Envs\tweeter\Scripts',
'c:\users\dlwkwok\appdata\local\programs\python\python35\Lib',
'c:\users\dlwkwok\appdata\local\programs\python\python35\DLLs',
'C:\Users\dlwkwok\Envs\tweeter',
'C:\Users\dlwkwok\Envs\tweeter\lib\site-packages']
Server time: 	Wed, 16 Dec 2015 16:46:46 +0800

anyone can help me, thank you very much!

If you look at the views.py in the index method, nothing is being returned if the user is not logged in. There are two optional workarounds for this:

You are using django==1.9. If you use virtualenv and download django from the requirements file, it will work as intended.

Handle the case for if the user is None by adding an else statement. To get it to run properly, try adding this:

else:
        return render(request, 'tweeter/index.html’)


Create package-level documentation page

Create a package-level documentation page with a summary of the main functions that is accessible with ?gemma.R

Added in e4b0b51a9be30a1b621737597fb8be28bc57ec74


Configure bors for crates.io

Do not merge this yet, let's configure bors when we migrate the repo to travis-ci.com.
In their meeting the crates.io team agreed to move from bors-ng to homu, and this PR adds the configuration to make it happen. List of reviewers allowed to merge code:

@carols10cents
@sgrif
@jtgeibel

After this PR is merged someone will need to add a new secret key on the RCS machine and configure the webhook with it.
cc @rust-lang/crates-io

Er I didn't read the "do not merge this yet" too closely. In any case this is fine to just have sitting on the side, I'll go configure a secret key before I forget

So uh... Does this mean it's up and running?

No, the webhook is disabled. We'll enable it once we migrate the repo to travis-ci.com.


hwmv2: port STM32H7 SoCs and boards

Doc update remains

There is a mention of stm32h747i_disco_m7 in boards/shields/st_b_lcd40_dsi1_mb1166/doc/index.rst as well :)

to be ignored

Needs rebase

Rebase needed and fixes for doc build to pass

@nordicjm rebased PTAL

@nordicjm This should be fine now. Are you able to merge ?


[fplive.net] down

[X] I've verified and I assure that I'm running youtube-dl 2017.01.10
[X] At least skimmed through README and most notably FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

C:\Users\rumag\Desktop\youtube-dl>youtube-dl.exe -f best --embed-subs --all-subs --convert-subs srt --username NoneofUrBusiness --password july1987 --ap-username sup --ap-password july1987 --ap-mso DTV --no-check-certificate "nick.com/videos/clip/the-thundermans-402-full-episode.html" -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-f', 'best', '--embed-subs', '--all-subs', '--convert-subs', 'srt', '--username', 'PRIVATE', '--password', 'PRIVATE', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', '--ap-mso', 'DTV', '--no-check-certificate', 'nick.com/videos/clip/the-thundermans-402-full-episode.html', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2017.01.08
[debug] Python version 3.4.4 - Windows-10-10.0.10586
[debug] exe versions: ffmpeg N-82966-g6993bb4
[debug] Proxy map: {}
WARNING: The url doesn't specify the protocol, trying with http
[nick.com] the-thundermans-402-full-episode.html: Downloading webpage
[nick.com] c3d21540-b607-11e6-bfd4-0026b9414f30: Downloading info
[nick.com] 296a81a1-9306-4b18-8ff6-e93d89e64f7a: Extracting information
[nick.com] 296a81a1-9306-4b18-8ff6-e93d89e64f7a: Downloading video urls
[nick.com] e6635c56-48dd-4f1d-b7d1-744f0ef458e7: Extracting information
[nick.com] e6635c56-48dd-4f1d-b7d1-744f0ef458e7: Downloading video urls
[nick.com] 0368e230-4252-4110-8e41-c65ff7497040: Extracting information
[nick.com] 0368e230-4252-4110-8e41-c65ff7497040: Downloading video urls
[nick.com] dbd52286-d74b-4292-9576-186409ca183c: Extracting information
[nick.com] dbd52286-d74b-4292-9576-186409ca183c: Downloading video urls
[download] Downloading playlist: The Thundermans: "Smells Like Team Spirit"
[nick.com] playlist The Thundermans: "Smells Like Team Spirit": Collected 4 video ids (downloading 4 of them)
[download] Downloading video 1 of 4
[info] Writing video subtitles to: The Thundermans - 'Smells Like Team Spirit' S1-296a81a1-9306-4b18-8ff6-e93d89e64f7a.en.vtt
[debug] Invoking downloader on 'http://viacommtvstrmfs.fplive.net/gsp.alias/mediabus/kids.com/2016/12/21/04/50/30/cbda52af52aa4a6fac2df1f7a840b32d/1497974/uDCJVLrQA2_HDTHN402A1_1497974_6918242_1920x1080_5128.mp4'
ERROR: unable to download video data: HTTP Error 404: Not Found
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp9qq9vblw\build\youtube_dl\YoutubeDL.py", line 1699, in process_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp9qq9vblw\build\youtube_dl\YoutubeDL.py", line 1641, in dl
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp9qq9vblw\build\youtube_dl\downloader\common.py", line 353, in download
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp9qq9vblw\build\youtube_dl\downloader\http.py", line 61, in real_download
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp9qq9vblw\build\youtube_dl\YoutubeDL.py", line 2001, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
  File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
urllib.error.HTTPError: HTTP Error 404: Not Found
...
<end of log>

Single video: nick.com/videos/clip/the-thundermans-402-full-episode.html
Single video: http://beta.nick.com/videos/clip/the-thundermans-402-full-episode.html

fplive.net seems to be down
MTV ,Nick and many others rely on viacommtvstrmfs.fplive.net
Comedy Central already switched to m3u8,akamaihd from fplive

This is already fixed.

No, it's not fixed. When I do it on my PC, it's still not working.
C:\Users\BARN\Desktop\youtube-dl>youtube-dl.exe -f best http://www.nick.com/videos/clip/the-thundermans-402-full-episode.html -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-f', 'best', 'http://www.nick.com/videos/clip/the-thundermans-402-full-episode.html', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2017.01.10
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: ffmpeg N-83034-gf48b6b8
[debug] Proxy map: {}
[nick.com] the-thundermans-402-full-episode.html: Downloading webpage
[nick.com] c3d21540-b607-11e6-bfd4-0026b9414f30: Downloading info
[nick.com] 296a81a1-9306-4b18-8ff6-e93d89e64f7a: Extracting information
[nick.com] 296a81a1-9306-4b18-8ff6-e93d89e64f7a: Downloading video urls
[nick.com] e6635c56-48dd-4f1d-b7d1-744f0ef458e7: Extracting information
[nick.com] e6635c56-48dd-4f1d-b7d1-744f0ef458e7: Downloading video urls
[nick.com] 0368e230-4252-4110-8e41-c65ff7497040: Extracting information
[nick.com] 0368e230-4252-4110-8e41-c65ff7497040: Downloading video urls
[nick.com] dbd52286-d74b-4292-9576-186409ca183c: Extracting information
[nick.com] dbd52286-d74b-4292-9576-186409ca183c: Downloading video urls
[download] Downloading playlist: The Thundermans: "Smells Like Team Spirit"
[nick.com] playlist The Thundermans: "Smells Like Team Spirit": Collected 4 video ids (downloading 4 of them)
[download] Downloading video 1 of 4
[debug] Invoking downloader on 'http://viacommtvstrmfs.fplive.net/gsp.alias/mediabus/kids.com/2016/12/21/04/50/30/cbda52af52aa4a6fac2df1f7a840b32d/1497974/uDCJVLrQA2_HDTHN402A1_1497974_6918242_1920x1080_5128.mp4'
ERROR: unable to download video data: ''
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu7wtweqp\build\youtube_dl\YoutubeDL.py", line 1699, in process_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu7wtweqp\build\youtube_dl\YoutubeDL.py", line 1641, in dl
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu7wtweqp\build\youtube_dl\downloader\common.py", line 353, in download
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu7wtweqp\build\youtube_dl\downloader\http.py", line 61, in real_download
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu7wtweqp\build\youtube_dl\YoutubeDL.py", line 2001, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 464, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 482, in _open
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu7wtweqp\build\youtube_dl\utils.py", line 877, in http_open
  File "C:\Python\Python34\lib\urllib\request.py", line 1186, in do_open
  File "C:\Python\Python34\lib\http\client.py", line 1227, in getresponse
  File "C:\Python\Python34\lib\http\client.py", line 386, in begin
  File "C:\Python\Python34\lib\http\client.py", line 356, in _read_status
http.client.BadStatusLine: ''

It's not yet released.


sky_tool listen always loads the main view (navigator should save state)

At least in debug mode I want navigator to serialize its state to memory or disk so that when listen pokes SkyShell to reload it reloads in the same navigation state as before.
@iansf @collinjackson

https://github.com/domokit/sky_engine/issues/908 covers scroll behavior


Add slepc to requirements

Now that slepc is available in conda-forge, we can build libadjoint with slepc support. This PR adds that along with a minor update in the license field and a re-render with conda-smithy 1.5.3.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Can you please try re-rendering again, @johannesring ? If it still fails, then some of it may need to be manually reverted.

Thanks @jakirkham, re-rendering again did not help, so I reverted manually.

All checks pass - ok to merge this now @jakirkham?


method to make field Computed?

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
I was working on https://github.com/pulumi/pulumi-command/issues/166. Afaik there's not a way to indicate that a field is computed. I believe that the provider is returning an empty string.
Some ideas:

[ ] make properties on resources computed by default
[ ] extend WireDependencies

Affected area/feature

There isn't a way to mark a field as "always computed".
Computed-ness should be part of the depends on relationship defined by infer.OutputField.DependsOn. It looks like the problem occurs when we trigger an update without any input changing.

I'm seeing spurious quote marks around command.local.Command.stdout which is causing a similar issue with JSON parsing (in my case, from an AWS CLI command).


Fix bug when traceparent is too small

for https://github.com/census-instrumentation/opencensus-java/issues/2038

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

Codecov Report

Merging #2047 into master will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #2047      +/-   ##
============================================
- Coverage     83.06%   83.04%   -0.03%
+ Complexity     2251     2249       -2
============================================
  Files           319      319
  Lines         10529    10528       -1
  Branches       1048     1047       -1
============================================
- Hits           8746     8743       -3
- Misses         1446     1447       +1
- Partials        337      338       +1

Impacted Files
Coverage Δ
Complexity Δ

...implcore/trace/propagation/TraceContextFormat.java
94.02% <100.00%> (-0.09%)
15.00 <0.00> (-1.00)

...pencensus/implcore/trace/RecordEventsSpanImpl.java
92.34% <0.00%> (-1.03%)
49.00% <0.00%> (-1.00%)

Continue to review full report at Codecov.

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

@nilebox Can you review these changes? This seems to be a higher priority during the opencensus transition to Opentelemetry.


Add license title

Hi @raybellis -- could you comment on why this PR was closed? I can better justify the proposed changes if needed.


cmd/compile: rewrite interface args by actual type args in functions called only with a single set of argument types

Sometimes programs use only a single set of interface implementations for every function call accepting interface args. In this case the compiler may safely rewrite such functions, so they'll accept actual type args instead of interface args.
This brings the following benefits:

removal of interface conversion overhead;
removal of interface method call overhead;
inlining short interface method calls and further optimizations based on the inlining.

The idea may be extended further. For instance, the compiler may generate specialized functions for each unique set of arg types passed to interface args (aka "generic" functions :)) . But naive implementation may lead to uncontrolled code bloat and performance degradation, so it must be carefully designed beforehand. One possible idea - specializing the function only if the following conditions are met:

all the interface methods for the arg implementation may be inlined (i.e. may lead to performance optimizations);
the function body is short (i.e. reducing generated code bloat).

This could inline and optimize sort.Interface implementations inside sort.Sort calls.

cc @randall77 , @dr2chase

This optimization is also known as devirtualization in C++ compilers.

How would this impact stack traces appearing after a panic that refer to rewritten funcs?

It's not obvious to me how this works with package-at-a-time compilation. For example, it would seem to require re-compiling package sort when a new type satisfying sort.Interface shows up.
This can be done semi-manually with an source code rewriter/specializer--which the sort package in fact has internally. :)

@josharian what about unexported funcs?

How often does that happen? This optimization would (I think) take pretty significant effort to implement. And if all the code is in the same package, then it could be specialized manually or with a source code generator, like in package sort.

How often does that happen?

One example that comes to mind is funcs that you want to test, so you make them take interfaces to help with the mocking. If you made it take an interface just for that, when compiling in non-test mode the interface type could be swapped with a single specific type.
I don't think you could specialize this manually, and I think this pattern is fairly well regarded.
I agree that this optimization would probably be far from trivial and most interface uses wouldn't benefit, though (unless inlining takes place?).

Forgot mentioning that the devirtualization may help escape analysis leaving more variables on stack. For instance, currently all the variables passed to interface functions are escaped because the compiler doesn't know all the function implementations which may be used in the program. With the devirtualization step the compiler may leave part of such variables on stack.

How would this impact stack traces appearing after a panic that refer to rewritten funcs?

This shouldn't change stack traces at all

It's not obvious to me how this works with package-at-a-time compilation. For example, it would seem to require re-compiling package sort when a new type satisfying sort.Interface shows up.

I don't know how the current compiler works, but here is a naive sketch how the devirtualization may be implemented:

Step 1 - AST building. Each package is parsed into AST and the results are marshaled to cache files.
Step 2 - Analysis. Scan each AST and fill the calls map[funcName]set[argTypes] for all the functions accepting at least one interface argument.

funcName is fully qualified function name: path/to/package.funcName
argTypes - a tuple of real argument types used in each call to the function.

Step 3 - Rewriting. For each function that that has only a single element in the set[argTypes] rewrite its' AST by substituting interface args with real args from argTypes.
Step 4 - Compilation. Compile each packages' AST.


Slide indices are incorrectly generated

Creating new slides results in slides with the same index every time, which means only the last created slide is actually visible in the web interface.

Fixed in commit c4c9551713978270ba58469a389a6f89f3081fdc


[Bug]: Should remove an editable category from the list

What happened?
A category cannot be its own parent.
If I select the current edited category as its parent, then I get an unpredictable binding:

And real parent not display (need an extra click):

How to reproduce the bug
public static function form(Form $form): Form
{
    return $form
        ->schema([
            TextInput::make('name')->maxLength(255)->required(),
            TextInput::make('slug')->maxLength(255)->required(),
            TextInput::make('position')->numeric(),
            SelectTree::make('parent_id')
                ->withCount()
                ->enableBranchNode()
                ->relationship('parent', 'name', 'parent_id')
        ]);
}

Package Version
3.1.25
PHP Version
8.3
Laravel Version
10.43
Which operating systems does with happen with?
No response
Notes
No response

This is not something the field should enforce, if you want to disable certain options you can with ->disabledOptions()


Bad calculation, it cannot add numbers with dots

Microsoft PowerToys version
0.71.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
you need to look at your calculator
she can't count!
123.01+52.30 = 175.4 there's a bug on numbers with dots
✔ Expected Behavior
a good calculation
123.01+52.30 = 175.31
❌ Actual Behavior
a bad calculation
123.01+52.30 = 175.40

Other Software
No response

@crutkas @jaimecbernardo

hello, update.
if I activate " use english numeric format for output " it works fine, else it requires commas (,) to work correctly.

I just ran into this one as well, actually used it for numbers I was about to send over to accounting. Ouch!

Ping @crutkas @jaimecbernardo

Ping @crutkas @jaimecbernardo

This has been worked on for the 0.74.0 release. Please update PowerToys to the latest version. 😉
https://github.com/microsoft/PowerToys/releases


Data object

Here is a series of commits that implement an object DataHolder that, er, holds the data.
The advantages are:

I like the syntax m.X = X_new, instead of m.update_data(X_new, Y_new).
The minibatching in SVGP is now much simpler, and incorporated into the same mechanism
It's easier to add new models that want to do minibatching (Deep GPs, perhaps?)
We can get at the data values in the same way as parameters through m.X.value
All the tests pass

The disadvantages are:

A new class. I'm wary of class bloat.
Some new tests are needed, and documentation needs improving before this can be merged onto master (this PR is to merge into Placeholder, for the moment).

@fujiisoup I'd welcome your thoughts on this approach.


[Fair map] Annotations are clipped on iOS 8

nice spot

This appears to only be a problem on the simulator, I was unable to reproduce it on a device. I suspect it has to do with me having a non-retina mac. Thus, closing this.


Does LGBMClassifier take the class_weight parameter into account while calculating metrics?

I'm trying to solve a multi-class classification problem with imbalanced data. I've 53 classes and data skewed towards 5 of them. I passed class_weights to account for data distribution.
Does LGBMClassifier take the class_weight parameter into account while calculating metrics? If not, what's the best way to create a custom metric? I can't find an option to do it using LGBMClassifier API. TIA

class_weight is python-only parameter. And i believe it actually converts to sample weight. And in metric, sample weight is taken into account.  refer to https://github.com/microsoft/LightGBM/blob/1617a63e96333cd0b129a38e6292e19fe989b759/src/metric/multiclass_metric.hpp#L89


Error pulling image (latest) from base, image ID '27cf784147099545' is invalid

Docker 1.4.1.
I have just developed on #9774, so it's very possible that I did something that messed up my installation (I've reproduced elsewhere). However, I have completely wiped /var/lib/docker and tried from fresh and I still get this problem:
$ docker run base echo hi
Unable to find image 'base:latest' locally
Pulling repository base
b750fe79269d: Error pulling image (latest) from base, image ID '27cf784147099545' is invalid
27cf78414709: Error downloading dependent layers
FATA[0003] Error pulling image (latest) from base, image ID '27cf784147099545' is invalid

I instrumented the docker source here with a log message to verify that it's really where the error message is coming from, and sure enough it is.
So is it possible this is a new bug? This behaviour was changed very recently (25 days ago): https://github.com/docker/docker/commit/bff1d9dbce76bed1e267a067eb4a1a74ef4da312

Ping @crosbymichael, this one means that lots of instructions on the internet are broken for anyone who tries to build an image from base or tries a tutorial which tells them to say docker run base <foo>. I keep encountering this and I have to remove base from lots of places. I'm a bit surprised this has happened and few people seem to be noticing..

Confirmed in OpenSUSE thumbleweed, docker 1.4.0
xxx@suseee:~/ubuntu> sudo docker pull base
Pulling repository base
b750fe79269d: Error pulling image (latest) from base, image ID '27cf784147099545' is invalid v1/, image ID '27cf784147099545' is invalid
FATA[0004] Error pulling image (latest) from base, image ID '27cf784147099545' is invalid
xxx@suseee:~/ubuntu> docker --version
Docker version 1.4.0, build 4595d4f

I see the problem. The base image has been deprecated. That's fine, except there is lots of stuff (such as docker tutorials!) in the wild that depends on it working :(. It also seems like a simple fix, the base images just need re-pushing, I would have thought.
Also summon @tianon in case he knows what's up.

IMO, any tutorial or document anywhere that mentions the use of base needs to be updated, and I would consider the very mention of that image a firm bug.  If it were entirely up to me, I'd have deleted it quite some time ago and just ripped that band-aid right off.
It hasn't been updated in ages, and won't be, especially since the name itself is so confusing.

To further drive home the point, a quote from the image's metadata on that page:

Updated 1 year, 8 months ago

As if all that wasn't enough justification for not using this image anymore, it's Ubuntu 12.10, which is officially EOL as of May 16, 2014.

The problem is, there are a lot of things in the wild depending on it. If there was an announcement about base being deprecated, I missed it (if there was, can someone please link to it?).
Google docker run base (estimates ~360,000)
Even though it's broken, lots of people are still using it. Given that I had not heard that the image was  dead, I think the message is unlikely to get through very easily.
I think we need to fix the problem that docker run base currently gives this cryptic fatal error. I don't mind how it is fixed, but it seems like a problem to me. It could be fixed by having docker check the name and give a more sensible messages, or just by re-pushing the existing image with the new digest format.

I just realised that google returned results matching docker run foo/centos-base and all sorts of other things, so the 360,000 estimate is way off.

@tianon

IMO, any tutorial or document anywhere that mentions the use of base needs to be updated, and I would consider the very mention of that image a firm bug.

Just noticed that all the API documentation uses base:latest in the examples :smile:

Gar, but it shouldn't be for a very long time now: #1914

@tianon also made this as a suggestion; https://github.com/docker/docker/issues/10142

So how do we fix all of the other broken tutorials on the internet? Can we make docker give a warning if you try to use the base image? This error is pretty insidious and gives docker a bad image (punintended) to newcomers.

Is the current warning better or worse than a 404 would be? :wink:

It is worse, since it looks broken and breaks in one version of a docker and not another. But still not ideal since it doesn't tell the user what alternative action they need to take.
On 16 January 2015 17:55:38 GMT+00:00, Tianon Gravi<EMAIL_ADDRESS>wrote:

Is the current warning better or worse than a 404 would be? :wink:

Reply to this email directly or view it on GitHub:
https://github.com/docker/docker/issues/9775#issuecomment-70293275

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

I have to agree it is worst than a 404, as a new user the reason I came here is because I thought Docker was broken, if I hadn't found this page I might have given up on Docker thinking it was broken and not production ready. This kind of error should always produce some form of valuable error message, the current message does not.

$ docker pull base
Pulling repository base
FATA[0001] Error: image library/base:latest not found

Unless it seems possible that anyone will consider making it a warning in docker, I guess that's as good as it gets and brings this issue to a close.

This issue is about "image ID '27cf784147099545' is invalid", right? This bug prevents me from removing any images from my disc, which is critical for me.
Is there a possible workaround?

@mborho what command are you trying to run when you hit that error? You might try deleting the base image directly.

@pwaller 'docker rmi IMAGE-ID' Where I can delete the base images? Somewhere under /var/lib/docker I guess, but where?

@mborho I meant if you run docker rmi <image id of the base image>. But I assume you've tried that and it didn't work. Are you getting errors about the base image when you try to delete images which are not the base image?

@pwaller I got this error message when I've tried to delete any image, actually. Switched back to 1.3.2 now, but I'll install the latest version again and will try again.

@pwaller it fails at every "docker rmi" command with 1.4.1. The base-image on my hardrive is from Dec 2013. "27cf784147099545" is the only ID in /var/lib/docker/graph in the old short form.
I can imagine, this bug will bite many people.

validHex = regexp.MustCompile(`^([a-f0-9]{64})$`)

is causing this, see https://github.com/docker/docker/commit/acf1720b3f6035f0ab2c9658371ae8302851ffa3#diff-cd575165f84eed10d10eb1460b0927b4R35

rm -rf /var/lib/docker/graph/27cf784147099545 fixed this for me, thanks @mborho

Hi
This is my first go running docker and I using it in Hyper V running v 1.4.1, what is the work around to fix library/d:latest not found when I try to pull a repository e.g.
docker run –d –p 1880:1880 cpswan/node-red
Many thanks
Andy

Ping @shin- @ewindisch @tianon
Did we (finally) remove base? I have FATA[0005] Error: image library/base:latest not found

I believe It had one of the legacy image IDs that we stopped supporting in 1.4+, and @tianon removed it as a result a few months ago.
tl;dr yes

Anybody who's using the extremely old base image, should rebuild them using ubuntu, really sorry for the inconvenience!


expose settings/config via localstorage

This PR exposes the user's current settings/configuration through localStorage, which allows injected scripts to read what features the user enabled.
This would be useful in #3/#1 where the "skip for now" button should also confirm skipping the question for now if the user has skip confirmation enabled. It also allows the textSkipConfirm.js and alwaysSkipConfirm.js scripts to be combined in one file.

I changed the variable name. Is it ready now?

Just realized I misunderstood your code lol. A couple potential changes now that I understand what it is actually doing:

have you considered using sessionStorage instead of localStorage, since this doesn't need to be persistent?
I had thought that it was ttcSettings that was going into a public namespace; since it's actually "cfg", I think that is probably the one that needs a more specific name.
Once these are addressed, I'll merge it :)


fix publishing

The Central Repository is the new service from Sona
https://central.sonatype.org/publish/publish-portal-maven/#managing-your-credentials
I lost my old credentials, but we probably have to start over anyway.

https://central.sonatype.org/publish/requirements/gpg/

Successfully claimed the domain.
The Central Repository Documentation

After your namespace has been verified, you're finally ready to start uploading components to Maven Central! See the following documentation for further instructions:

Maven
Uploading a bundle
Component Validation

https://central.sonatype.org/publish/requirements/

Javadoc
Sources
Checksums
GPG

Does the plug-in do most of this?
https://docs.gradle.org/current/userguide/publishing_maven.html
No. The good / bad news is there's lots of options for maven central...
https://plugins.gradle.org/search?term=maven-central

Okay, this seems like the 800lb gorilla of plugins.
https://github.com/vanniktech/gradle-maven-publish-plugin/
Specifically, it claims to provide general Maven support (including Maven Central), and has 1.1K stars (versus, like, 15 for all the others put together).
Err... not quite. That one uses the old API.  There's an plugin-to-the-plugin that seems to fix that (45 stars).
https://github.com/GradleUp/nmcp

Of the remaining options, the best two seem to be:

https://github.com/Im-Fran/SonatypeCentralUpload
https://gitlab.com/thebugmc/sonatype-central-portal-publisher

The first one has Groovy documentation, so I will try that first.

https://docs.gradle.org/current/userguide/plugins.html

Non-core plugins must be resolved before they can be applied. Non-core plugins are identified by a unique ID and a version in the build file:

plugins {
    id «plugin id» version «plugin version»
}

And the location of the plugin must be specified in the settings file:
settings.gradle
pluginManagement {
    repositories {
        gradlePluginPortal()
    }
    maven {
        url 'https://maven.example.com/plugins'
    }
}

Ah! The gorilla plugin DOES work. They updated the docs for me :-)
https://vanniktech.github.io/gradle-maven-publish-plugin/central/#configuring-maven-central

Fixed!


Need an uptade for 13.4 it doesnt work anymore

Need an uptade for 13.4 it doesnt work anymore

Need an uptade for 13.4 it doesnt work anymore

What do you mean it doesn't work anymore? I have no problem using it

Need an uptade for 13.4 it doesnt work anymore

What do you mean it doesn't work anymore? I have no problem using it

No it doesnt work anymore. It always says "object not set" when im trying to open it.

I used it yesterday and it was working normally.

我的可以正常使用


Cleanup Monitor log page

Added stacktrace column and expand button to view whole stacktrace
Format the timestamp similar to actual logs

To be clear, the stack trace was there before, right? This just makes it more presentable?

Correct.  It was there before but taking up a lot of screen space and not formatted nicely.


Problem with update_channel gossip propagation across LND nodes (wrongly marked as zombie channels?).

I have small routing node.
It is running Core Lightning 24.02.
My node is active for more than 2 years and is running on proper server 24/7 the whole time.
It has just few channels, because I am not trying to be big routing node, the purpose of this node is to serve me and my friends and family.
Recently I noticed that LND nodes that are not my direct peers have very wrong information about my channels.
For example here is my direct peer (we have channel) with LND node, here is how his node sees my channels:
https://gist.github.com/urza/f5e758b2fdc56f79c2d64e02e43084fd
They see all 7 channels in active state with correct fee info.
But here is LND node just one hop away sees my channels:
https://gist.github.com/urza/05d2c97cee6c948500a2229c3c91fa2c
They only know about 2 of my channels!! The rest is not even listed!
When I asked if they would run getchaninfo about one of the missing channels, the direct LND peer returned correct information about the channel, however the one hop away node returned:
[lncli] rpc error: code = Unknown desc = edge marked as zombie
However the channel is alive and working. I tried to rebalance this channel from both sides and it worked without any issues.
Also for the last few days I changed fees on all of my channels once a day to be sure that update_channel gossip is sent out about all my channels.
I also connected to other nodes besides those that I have channel with. CLN should be sending update_channel to all connected peers.
But still the same result.
My direct peers and CLN nodes that are farther away see my channels correctly, but LND nodes that are not my direct peers see wrong information and miss most of my channels.
From this I suspect that LND nodes somehow mark most of my channels as zombie and refuse to propagate the gossip.
This is bad for me as it decreases my ability to receive payments if senders might not know about most of my channels. And is also bad for network if LND nodes have such inaccurate information about the network graph.

I connected to a friend with LND node (we don't have channel) and he has this in his terminal:
GossipSyncer - applying new update horizon: start=2106-02-07 07:23:15, end=2242-03-16 13:56:30

We have no idea what it means, but it doesn't look healthy :)

For the part relating to channels being marked as zombies when they have recent channel_updates, I think that will be addressed in the next release when https://github.com/lightningnetwork/lnd/pull/8030 is included.
As for the weird update horizon.... that seems like a different issue 🤔

The two dates, when interpreted as seconds since 1970, correspond to<PHONE_NUMBER> and<PHONE_NUMBER> (ignoring the time zone?). The first number is double the second number. Furthermore,<PHONE_NUMBER> is 2^32 - 1. To me, this looks like some kind of default is used for both values.

ah also - if the LND node is printing this after receiving the GossipTimestampRange message from you (CLN) node, then it looks like it is CLN sending these dates

@saubyk I believe this deserves higher priority then P3. Because LND has such a high share of the whole lightning network, this issue causes that almost all nodes have very distorted view of the network graph.
This can be seen in public network explorers like amboss, 1ML and ligthtning lab's terminal. They have very wrong information about nodes. In last week I talked to many node operators trying to figure out my gossip issues, and almost nobody has correct information on these explorers about their node.
I now believe it is becuase LND doesn't propagate channel_update gossip messages when it should. And because it has such a high share of the network it is serious issue for the whole network.

@urza  - as mentioned before, this should be addressed by https://github.com/lightningnetwork/lnd/pull/8030 which will be in the next release. So I dont think there is any work that needs to be done... hence the P3 status

In fact, I think we could even close this issue.

@urza - as mentioned before, this should be addressed by #8030 which will be in the next release. So I dont think there is any work that needs to be done... hence the P3 status

Ok, I was more reacting to the "nice to have" description in P3 label.


Static Forms and Mailchannels Plugin breaking other forms

While the documentation says these plugins "intercept all form submissions made which have the data-static-form-name attribute set", they were breaking the search function and other forms on my site which do not have that attribute set. I was able to restore the expected behavior by replacing:
return new HTMLRewriter().on("form", {
with:
return new HTMLRewriter().on('[data-static-form-name]', {

Fixed by #41


Pause and Resume watch/reconcile of custom resource by helm-operator

Feature Request
Describe the problem you need a feature to resolve.
For a particular scenario, we temporarily scale down a deployment (which is part of our product) by updating the replica value to zero in the spec.  However, it seems the helm-operator-controller interferes with this and scales it back up to the replica count set for the operand install.
Describe the solution you'd like.
It would be very helpful if the helm controller could temporarily pause reconciliation for a resource and then resume later. Maybe this could be triggered by a paused annotation on the resource?
The operator-lib project has support for such a feature - https://github.com/operator-framework/operator-lib/pull/60
If such a feature already exists for the helm-operator, kindly guide us with the related resource.
/language helm

@sukhil-suresh Unfortunately, we don't have this feature in Helm operators. The available set of annotations for Helm operators are here: https://sdk.operatorframework.io/docs/building-operators/helm/reference/advanced_features/annotations/.

@varshaprasad96 Thanks for sharing the annotations supported by the Helm operator.
We have an (untested) workaround for the problem we faced, which involves updating the operand spec to have support for the deployment replica. The assumption is that the helm operator will respect the operand spec value change.
Feel free to close the issue, if needed. I still believe there is value in an annotation that allows pause/unpause of the helm-based operator reconciliation.

/close


[Win] Oh snap container is not ready (invalid state)

Install fresh Subutai
create environment 1 container
try to ssh to container (you will see shell trying to connect with timeout) - as expected
generate ssh-key in tray
try to ssh to container (you will see error oh snap) - seem like the state of container is saved somewhere

I had to restart the tray in order to run ssh container again

also found that during connection in the console the following:
Could not create directory /home/2ch/.ssh
Connection closed <IP_ADDRESS>

usually "Could not create directory /home/2ch/.ssh" allows to connect with ssh, it's not an error
Please, this error is not related to installer, its tray/hub/p2p issue

Digging into a problem, we found that it occurs, because we cannot ping resource host in windows, windows and p2p related problem.
https://github.com/subutai-io/p2p/issues/152


Compilation error using carthage

Hi... just tried to add Box to a brand new project using Carthage (my cartfile contains github "robrix/Box" ~> 1.2.0) and get the following error when I run carthage update:
clang: error: invalid architecture 'aarch64' for deployment target '-mios-simulator-version-min=8.0'

If I manually open and build Carthage/Checkouts/Box/Box.xcodeproj in Xcode (6.3, if it matters) it compiles OK.  The one difference that I can see between the two compilation commands are that carthage is using Release-iphoneos, whereas Xcode uses Debug-iphonesimulator.
The full transcript of the carthage build is https://gist.github.com/edwardaux/8a2319844ba00582c0b7
Any thoughts? Thanks.

I’m afraid I don’t have any ideas here. I can‘t reproduce the issue :confused:
Are any of your other dependencies using Box?

Interesting. I originally discovered it because my project was was using Carthage to embed Argo, which has its own Cartfile that pulls in Box as a sub-dependency. However, after a bit of testing, I discovered that I could reproduce the error just by using Box.
For me, reproducing is literally as simple as the following:

Create new Swift Project (doesn't matter if iOS or OS X)
Create a Cartfile that contains github "robrix/Box" ~> 1.2.0
Run carthage update

Could I trouble you to share your Carthage build log from the above steps? That might help me figure out what is different on my machine.
In case anyone is playing along at home, for reference, I'm using Xcode 6.3 (6D570) and Carthage (0.6.3).

rob@Resonance ~/D/Foo /master> carthage update
*** Fetching Box
*** Checking out Box at "1.2.0"
*** xcodebuild output can be found in /var/folders/9y/f7n4rvx901nctm_5d16c1wm40000gn/T/carthage-xcodebuild.my0DyZ.log
*** Building scheme "Box-iOS" in Box.xcodeproj
*** Building scheme "Box-Mac" in Box.xcodeproj

/var/folders/9y/f7n4rvx901nctm_5d16c1wm40000gn/T/carthage-xcodebuild.my0DyZ.log

Thanks Rob. Turns out that your Foo project doesn't build on my machine either, so it must be something screwy in my environment.
I think the gist you created with the log must be a private one... as I get a 404 when I access it. Once I get that, hopefully that will give me a clue as to what is wrong with my setup.  Thanks.

There’s no such thing as private gists only public & secret (unlisted) ones, but I’ve gone ahead and made it public.

Since this doesn’t repro for me I’m going to go ahead and close this issue out.

@edwardaux I’ve just uploaded a binary for 1.2.1, so carthage may be able to avoid building Box altogether now.

Thanks @robrix.
FYI, I was doing some more googling and found some other reports of a similar problem in ReactiveCocoa. Their "fix" was to uninstall Xcode 6.3 and re-install it - which I tried, but no luck.
I downloaded the source to Carthage and started poking around to see what arguments they use when they invoke xcodebuild. The way I read it, the Carthage script basically boils down to the following (which doesn't work on my, and also one other colleague's, machine):
xcodebuild -project Box.xcodeproj -configuration Release -sdk iphonesimulator -scheme Box-iOS

By contrast, building by specifying the target works ok:
xcodebuild -project Box.xcodeproj -configuration Release -sdk iphonesimulator -target Box-iOS

The one thing that jumped to mind in the failing log is that even though the sdk is reporting as iphonesimulator8.3, the first few lines of the log have somehow morphed into using iphoneos.
Build settings from command line:
	SDKROOT = iphonesimulator8.3

=== BUILD TARGET Box-iOS OF PROJECT Box WITH CONFIGURATION Release ===

Check dependencies

Write auxiliary files
/bin/mkdir -p /Users/edwardsc/Library/Developer/Xcode/DerivedData/Box-bvdyjxluqbdcwqeoagemfoykznjg/
Build/Intermediates/Box.build/Release-iphoneos/Box-iOS.build/Objects-normal/arm64
write-file /Users/edwardsc/Library/Developer/Xcode/DerivedData/Box-bvdyjxluqbdcwqeoagemfoykznjg/
Build/Intermediates/Box.build/Release-iphoneos/Box-iOS.build/Objects-normal/arm64/Box.LinkFileList
...

Weirdly enough, I see the exact same conditions when I tried the same for Prelude.
No action required on your part... just thought I'd update this issue in case others have a similar problem. Will report more when I get to the bottom of it.

Interesting findings. What happens if you specify both target and scheme? This may be worth opening an issue against carthage.

I'm seeing the same results as @edwardaux on my machine. Thanks for digging into what's causing this.

Has the binary for 1.2.1 helped anything here?

I forgot to mention, I'm seeing the same thing with https://github.com/LlamaKit/LlamaKit, I haven't used this lib specifically.
I did just add it to my project to try though, and it installed successfully. It didn't build though, I'm guessing that's because you have the .framework in the release?

@jakecraige That’s right, binary release == downloadable .framework for 1.2.1. So that much is working at least!

As it turns out, @robrix, I don't believe that it is specifically related to Box (oh, and to answer your earlier question, scheme and target are mutually exclusive).
When using -target, it compiles correctly regardless of the -sdk value.
When using -scheme, it compiles correctly for the device if I pass -sdk iphoneos or nothing at all.  If I pass -sdk iphonesimulator the compile log says SDKROOT = iphonesimulator8.3, the -isysroot flag gets set to the simulator SDK path, but for some reason it is using an arm architecture - which causes the compilation error.
Stepping back a little, I created a brand new iOS framework project (and also a static library project) and they both have exactly the same problem.  A brand new app, however, does not exhibit the problem.
Based on this, I think the problem can correctly framed as:
Using Xcode 6.3, when compiling iOS static libraries or frameworks, incorrect xcodebuild flags are getting set if both -scheme XXX and -sdk iphonesimulator are passed.
The weird thing is that everything compiles OK in Xcode.
At this stage, it is looking more and more like an xcodebuild bug. Apologies Rob for clogging up your Box issue tracker. By copy, @jspahrsummers, while I don't believe it is strictly related to Carthage, I'm curious if you'd seen anything like this in your travels?

@edwardaux Sounds related to https://github.com/Carthage/Carthage/issues/347 or https://github.com/Carthage/Carthage/issues/417.

Ooh, yes.  https://github.com/Carthage/Carthage/issues/417 is on the money. If I pass in -destination 'platform=iOS Simulator,name=iPhone 4s,OS=latest' then it builds just fine.
I'll do a bit more digging on the -destination flag and see if I can't create a Carthage pull request. I'll also raise a radar against xcodebuild.


Add ATRI

@eozdem thanks for your contribution. Are you sure that this is how the Atari logo should look like? Can you also add some links about the project in this PR?

Hi, I've updated logo.
Website: https://atarichain.com/
https://coinmarketcap.com/currencies/atari-token/
https://www.coingecko.com/en/coins/atari/

Hi @eozdem

In PR you still are keeping the old SVG version - can you remove it please?
There is a requirement that icons have to be SVG and you uploaded a jpeg with over 90kB size. Can you please upload SVG one? Maybe you can just use the red one used in Eetherscan or a token website

https://www.ataritokens.com/myportal/home
https://etherscan.io/token/0xdacD69347dE42baBfAEcD09dC88958378780FB62


Strict json validation

This uses JsonSlurper, which is by default stricter than JSON.parse.
It does not strictly follow the JSON spec, however. I have found that it deviates from the spec by allowing trailing commas, and possibly is lax in other ways.
EDIT: Performance may also be improved, but I haven't benchmarked it and I doubt we care.

I'm assuming we're all good to close this out in favor of the new nano parser.


On small screens (1366 x 768), the scroll bar for the main div is outside

It is about 50% outside the right side of the screen

Fixed


widbaroalarm: plot + fix interval on start

Do not immediately measure on start, use previous value to always stay in interval
Add plot pressure history to settings

Nice ideas, thanks!


Can't get the reported result in paper

Sorry, I've got a problem. I  train RCAN , RDN and EDSR according to your setting. Data preprocess is also done by your scripts. But I can't get the reported results in those papers. Empirically there is always 0.09dB difference. I wonder if you have this difference too.  If so, Is that a problem about data preprocess?  Thank you.

I have not tested these algorithms in mmsr.
For EDSR, do you also encounter 0.09dB performance drop?
In mmsr, we use a variant of EDSR_baseline_x4 (1.52 M) (namely, the modified SRResNet) and we can get the comparable (slightly better) performance.
If you train a large model, the performance drop may arise from the data or the optimization strategy.

Sorry, I've got a problem about the training iteration. I am trying to reproduce the results of ESRGAN_PSNR_oriented model but I have no idea how many iterations I should set to get optimal results.
To be honest, I have read the paper of ESRGAN muptiple times, but it seems that there is no exact iteration numbers in it, only said, 'The learning rate is initialized as 2e-4 and decayed by a factor of 2 every 2e5 of mini-batch updates'.
Hope Professor Xintao or greatlog can share the iterations's setting of ESRGAN_PSNR_oriented model when the batch_size is 16 to save my aimless trying times. Thank you!

@greatlog
Hello, do you modify EDSR from EDSR-Pytorch. I noticed that in EDSR-Pytorch repo, the data fed into model has range of [0,255] but in the repo the data has range of [0,1]. Did you compare the result of such different setting in mmsr? Thanks!

@greatlog
Hello, do you modify EDSR from EDSR-Pytorch. I noticed that in EDSR-Pytorch repo, the data fed into model has range of [0,255] but in the repo the data has range of [0,1]. Did you compare the result of such different setting in mmsr? Thanks!

I tested last week, there is no big difference between range [0,1] and range [0,255], the PSNR and SSIM results are about the same.

@ascetic-yuanma Thanks for you reply!

@ascetic-yuanma Could you successfully reproduce EDSR model in mmsr, I copy EDSR from EDSR-pytorch and modify rgb_range from 255 to 1.0. but also  encounter about 0.09dB performance drop even with same  configs and dataset.

@John-Yao Hi John, I did some extending work these days, and found there's a huge drop of PSNR on Set5 at scaling ratio 4 when reproducing MSRN on this framework.
Futhermore, I noticed a PSNR&SSIM drop when calculating PSNR on Matlab using default psnr and ssim functions.
For instance, the PSNR&SSIM of my reproduced MSRN calculated by mmsr are 32.10dB/0.8934, while the PSNR&SSIM of my reproduced MSRN calculated by matlab are 32.07dB/0.8923.

@John-Yao The reported PSNR&SSIM of MSRN on Set5_X4 are 32.25/0.8958 collected from https://github.com/MIVRC/MSRN-PyTorch.

@John-Yao Will keep you informed if figured out what caused this. Hope we can figure it out!

Forgot to @greatlog  :) Hope we can figure this out!

I think the drop of PSNR/SSIM is due to the code of PSNR function by different repo.
In my exp,   PSNR of my reproduced EDSR is slightly higher than origin repo using the same evaluation function.
About MSRN, I think is due to some different settings such as lr scheduler...

@John-Yao So did you successfully reproduce EDSR model in mmsr and get reported PSNR in EDSR paper?

@ascetic-yuanma I didn't  run exp on public dataset. In our dataset, my reproduced EDSR in mmsr repo is slightly higher than the origin repo(using the same evaluation function).

@John-Yao Sure, thank you for your reply!


phoebemirman/ch17078/caps-lock-are-being-added-here-to-additional

Story details: https://app.clubhouse.io/augur/story/17078

Coverage remained the same at 63.168% when pulling 828235716d9b9dc55b729a0a9a85e6ac00c1daaa on phoebemirman/ch17078/caps-lock-are-being-added-here-to-additional into 1da955dde173bf27ba219b886314d4452958ea5c on master.


How to use just RPN for text detection

Hi,
I want to use RPN only and no RCNN to generate region proposals for text regions. Is there a way to do it?

Yes, you can use the RPN class in faster_rcnn/faster_rcnn.py for your tasks.

Hey @sarthak1996 I wanted to know why you chose only rpn for your task?


Removing bullet-core that is now its own artifact

Coverage increased (+0.06%) to 99.296% when pulling daa27cf0c9b6d9e354dcfb91ff53a59757f212b0 on bullet-core-removal into 19c9b0510f8631cff9935441aa551d2df1da6abb on master.

Coverage increased (+0.06%) to 99.296% when pulling 1c219371b662b6868af04150354cda218ef34d89 on bullet-core-removal into 19c9b0510f8631cff9935441aa551d2df1da6abb on master.


Fix SetState & GetState Typescript declaration in create function arg…

The create function typescript definition has a generic parameter that helps to define the final state that will be used : TState extends State. This state has to extend State (Record<string, any>) which is relevant for  a state.
Unfortunately both set and get parameters types don't use this generic parameter and instead are bound to State as we can see :
  createState: (set: SetState<State>, get: GetState<State>, api: any) => TState
It is not very anoying for the set parameter, but it is really a pity that when one uses the get method, the definition does not simply type the return to TState instead of the very neutral State.
Is it just a mistake ? Or is there a reason not to have used TState in set: SetState<State> and get: GetState<State> ? (I must admit that I would expect set: SetState<TState> and get: GetState<TState> instead).

This is similar to a PR I had opened (#27) but I believe this change breaks autocompletion for non typescript users.

@JeremyRH @Magellol @jfbrazeau could we discuss this again? We just run into it as well. Is it important that non TS users get broken intellisense? TBH, as a non TS use im kinda used to nothing giving me autocomplete. But now that i work on a TS project, passing on set/get into a factory, it's a little annoying the way it is.

This is similar to a PR I had opened (#27) but I believe this change breaks autocompletion for non typescript users.
I think the workaround is to do
create<MyState>((set: SetState<MyState>, get: GetState<Mystate>) => {}})

I'm afraid I don't understand your workaround.
I've tried it to see what it gives and here is the result :

As you can see I've described a very simple state (MyState) and applied your workaround. Typescipt complains that (as you can see in the 'PROBLEMS' view of VSCode (see screenshot) :
Argument of type '(setState: SetState<MyState>, getState: GetState<MyState>) => MyState' is not assignable to parameter of type '(set: SetState<Record<string, any>>, get: GetState<Record<string, any>>, api: any) => MyState'.   Types of parameters 'getState' and 'get' are incompatible.     Type 'Record<string, any>' is missing the following properties from type 'MyState': stateParm1, stateParm2, anAction
The (very unsatisfying) workaround I found consists in duplicating the zustand defintion file (index.d.ts) in my module and configure Typescript to use it to override zustand definitions (in tsconfig.json) ; in other words, this line :
export default function create<TState extends State>(createState: (set: SetState<State>, get: GetState<State>, api: any) => TState): [UseStore<TState>, StoreApi<TState>];

becomes in my environment this one :
export default function create<TState extends State>(createState: (set: SetState<TState>, get: GetState<TState>, api: any) => TState): [UseStore<TState>, StoreApi<TState>];

When you are a Typescript user, the default zustand definition is very strange. The create function is parameterized with TState. That function returns itself a TState, but it provides setter and getter for....  State instead of TState !... So if you plan to use this setter/getter pair, you will have to cast the state as soon as you want to use it. Very strange when you consider that you already gave the state type through the TState parameter.

Here is a workaround that seems to work :

You have to cast the state every time you want to use it.
Possible workaround, but which is not relevant as far as I can see. Unfortunately I prefer to duplicate the zustand definition file to get rid of that problem (even if this is not satisfying me at all).
(But I must admit that if I omit tlittle typescript issue, I really like zustand, so for now I accept my unsatisfying workaround... ;) )

Could some kind of function overloading solve the problem?  Or the definition of a second, typed function to create a store?
export function createT<TState extends State>(   createState: (set: SetState<TState>, get: GetState<TState>, api: any) => TState ): [UseStore<TState>, StoreApi<TState>] {   return create<TState>(createState as any); }

closed in favour of https://github.com/react-spring/zustand/pull/35


Changed all references to manimcm to manimce

List of Changes

All references to manimcm have been changed to manimce.
Motivation

Discussed in #615
Explanation for Changes

By making sure manimcm isn't used anymore.
Further Comments
This should be added to the changelog, but I don't know if I should add a line to v0.1.0 or add it above for the next version?
Acknowledgement

[x] I have read the Contributing Guidelines

Great, thank you!


gitHash returns hash as variable rather than logging it

Return hash value instead of logging it
By setting the returned value to process.stdout, it seems like the result of the execSync call was being logged to the screen while the value returned to the app was 000000.
The docs say that the default value is 'pipe', so I've reset the first two std values to 'pipe'
Note: I tried to write tests for this, but ran into two problems

I can't predict whether this will be run from a git repo or not, so I don't know what value to expect
I couldn't figure out how to get the logged hash from the original function while still in a test

I think it's okay as-is, but open to suggestions.

A+


how to change the selected index of page menu

How could change the default selected page?

Already find the answer in this issue : https://github.com/uacaps/PageMenu/issues/176
thanks for reading


Can't instell Prisma Client with Node 16

Bug description
Prisma should support all LTS versions of Node as stated here:
https://www.prisma.io/docs/reference/system-requirements
When installing prisma client with<EMAIL_ADDRESS>I'm seeing the following error:
warning Pattern ["<EMAIL_ADDRESS>is trying to unpack in the same destination "/Users/.../Library/Caches/Yarn/v6/npm-@prisma-client-3.13.0-84511ebdf6ba75f77ca08495b9f73f22c4255654-integrity/node_modules/@prisma/client" as pattern ["<EMAIL_ADDRESS>This could result in non-deterministic behavior, skipping.
error workspace-aggregator-50e17904-eb66-4bdd-9b1b-b4b23daac4e4@: The engine "node" is incompatible with this module. Expected version ">= 14 <15". Got "16.10.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

How to reproduce
yarn add @prisma/client
Expected behavior
Should install with Node 16
Prisma information
No applicable
Environment & setup
<EMAIL_ADDRESS>Prisma Version
<EMAIL_ADDRESS>

Hi @janpio,
sorry my bad :(
I'm using a monorepo and have specified my engine entry wrongfully. Sorry for causing some work! Thank you for your response. Now it works!


Follow up to #1231

My apologies after merging #1231 (whilst writing the changelog!) I noticed the spec is actually wrong, the implementation is correct but the spec was calling to and not to_not. This fixes that.

No apology needed @benoittgt I missed it too :p


make tag more typesafe

introduced in #72
Essentially get rid of the any

Tag can extend the HTMLElement interface. Something like:
interface Tag extends HTMLElement {
    att$: (name: string, value: string) => Tag
    onclick$: (callback: (this: GlobalEventHandlers, ev: MouseEvent) => Tag) => Tag
}

A Tag can then be created with:
const result: Tag = Object.assign(document.createElement(name), {
    att$: function(name, value) {
        this.setAttribute(name, value);
        return this;
    } as Tag["att$"],
    onclick$: function(callback) {
        this.onclick = callback;
        return this;
    } as Tag["onclick$"]
});

The Object.assign() stuff might not be as clean as one would like. Another way to assign att$ and onclick$ to result would be:
const result = document.createElement(name);
(result as Tag).att$ = function(name, value) {
    this.setAttribute(name, value);
    return this;
};
(result as Tag).onclick$ = function(callback) {
    this.onclick = callback;
    return this;
};
// ...
return result as Tag;


Command - Add .help

Add a help command to send the user a PM with all available commands.

This is was resolved with 2af111f


Dark mode

Preview is available here:http://stellar-demo-wallet-pr215.previews.kube001.services.stellar-ops.com/

Excited to see the dark theme landing!
I've found an issue with the light theme colors in:

@marcelosalloum The dark mode is not completed yet, there are plenty of issues at the moment. Very soon. 🤓

Preview is available here:http://stellar-demo-wallet-pr215.previews.kube001.services.stellar-ops.com/


Restore wallet functionality

On mainnet when i try to restore a with a mnemonic that previously done transactions on other wallets it does not retrieve me all transactions, showing a blank list instead.

On further investigation it might be that only testnet L-BTC is currently supported and hardcoded as a asset, but I am not sure this is the case.

Hey! Yah, currently get Transactions has hardcoded Test-LBTC
amount: wallet_tx
                .balance
                .get(&AssetId::from_str(TLBTC_ASSET_ID).unwrap())
                .unwrap_or(&0)
                .to_owned()
                .abs() as u64,
          ```

We have to allow the user to input AssetId so its not adapted to Mainnet but also allows other assets to be used.

Similar thing happens in balance, we need to upgrade it to allow any Asset, currently we only allow lbtc, lcad and usdt

Will make this update by the end of the week.

Okay, i tried a few things.
flutter_rust_bridge does not support HashMaps which is required to have a map of assetIds and balances.
Earlier we had our own struct like this:
struct Balances{
 pub lbtc: u64,
 pub ltest: u64,
 pub lcad: u64,
...

The advantage is that the end user need not bother about AssetId's when parsing balances and such a type is compatible with frb.
Disadvantage is that we would have to keep adding support for new assets.
IF we can use a HashMap, then the end user can just scan the HashMap by AssetId and find the approprioate balance.
For now we have to stick with our own Balance struct until frb supports HashMap unfortunately.
I will add support for LBTC (Mainnet) for now.

This is what would be ideal:
pub struct AssetIdMapUInt(pub HashMap<AssetId, u64>);
pub struct AssetIdMapInt(pub HashMap<AssetId, i64>);

pub type Balances = HashMap<String, u64>;
impl From<AssetIdMapInt> for Balances {
    fn from(asset_id_map: AssetIdMapInt) -> Self {
        asset_id_map.0.into_iter()
            .map(|(key, value)| {
                let converted_value = if value < 0 { 0 } else { value as u64 };
                (key.to_string(), converted_value)
            })
            .collect()
    }
}
impl From<AssetIdMapUInt> for Balances {
    fn from(asset_id_map: AssetIdMapUInt) -> Self {
        asset_id_map.0.into_iter()
            .map(|(key, value)| (key.to_string(), value))
            .collect()
    }
}

Also tried with bleeding edge FRB and get the same error:
not yet implemented: generate code for type "HashMap < String , u64 >"

https://cjycode.com/flutter_rust_bridge/guides/types/translatable/detailed/map_set
Their docs says it supports it but, not able to get it to work.

HACKED!
pub type Balances = Vec<(String, u64)>;

This works.

This should also be patched in 0.1.1 and current trunk branch

I'll help you fix that, so contact me immediately!

HACKED!
pub type Balances = Vec<(String, u64)>;

This works.

This works well in rust, but i think in flutter we cannot access the id as it is a tuple and we cannot access the value of the items without some getters 🤔


com.google.android.gms:play-services-auth versioning problem

Currently I believe we should use the latest play-service-auth version which is 10.0.1, but somehow my emulator's play service is not up-to-date (9.8). I tried to re-download the images and it's still out of date. Does anyone know how to solve this?

Same issue here.

I have also face the same problem,
I have run it on real device rather than emulator....

In an effort to clean the issues up, this is being closed. Please open a new issue if you're still experiencing a problem.


1.21?

yea I need 1.21 too but I think this is gonna take them a while to update the mod to using the new components system

^ skull emoji react these users


Review and update skos:narrowMatch and skos:broadMatch mappings

This PR and issue in the SSSOM repo showed that - by following the old SSSOM guidance - we have sometimes used the SKOS predicates for narrow match and broad match incorrectly.
Definition in old SSSOM guidance:

skos:narrowMatch: The subject is taxonomically narrower than the object.
skos:broadMatch: The subject is taxonomically broader than the object.

The updated definitions are in accordance with the SKOS specs:

skos:narrowMatch: From the SKOS primer: A triple <A> skos:narrower (and skos:narrowMatch) <B> asserts that <B>, the object of the triple, is a narrower concept than <A>, the subject of the triple
skos:broadMatch: From the SKOS primer: A triple <A> skos:broader (and skos:broadMatch) <B> asserts that <B>, the object of the triple, is a broader concept than <A>, the subject of the triple

The SSSOM guidance has since been updated.
In this issue we will review and update our mapping files to fix this.

Please see below for a list of the mappings that use skos:narrowMatch or skos:broadMatch and may require updating:
Semantic mappings
V1 skos:broadMatch, potentially need to be update to skos:narrowMatch

dwc:verbatimCoordinates [Verbatim Coordinates] to MIXS:0000009 [lat_lon]
dwc:country [Country] to MIXS:0000010 [geo_loc_name]
dwc:waterBody [Water Body] to MIXS:0000010 [geo_loc_name]
dwc:associatedOrganisms [Associated Organisms] to MIXS:0000028 [biotic_relationship]
dwc:samplingProtocol [Sampling Protocol] to MIXS:0000002 [samp_collect_device] update comment!
dwc:sampleSizeValue [Sample Size Value] to MIXS:0000001 [samp_size]
dwc:sampleSizeUnit [Sample Size Unit] to MIXS:0000001 [samp_size]

V1 skos:narrowMatch, potentially need to be updated to  skos:broadMatch

dwc:decimalLatitude [Decimal Latitude] to MIXS:0000009 [lat_lon]
dwc:decimalLongitude [Decimal Longitude] to MIXS:0000009 [lat_lon]
dwc:verbatimLatitude [Verbatim Latitude] to MIXS:0000009 [lat_lon]
dwc:verbatimLongitude [Verbatim Longitude] to MIXS:0000009 [lat_lon]
dwc:verbatimDepth [Verbatim Depth] to MIXS:0000018 [depth]
dwc:minimumDistanceAboveSurfaceInMeters [Minimum Distance Above Surface in Meters] to MIXS:0000018 [depth]
dwc:maximumDistanceAboveSurfaceInMeters [Maximum Distance Above Surface in Meters] to MIXS:0000018 [depth]
dwc:minimumDepthInMeters [Minimum Depth In Meters] to MIXS:0000018 [depth]
dwc:maximumDepthInMeters [Maximum Depth In Meters] to MIXS:0000018 [depth]
dwc:minimumDistanceAboveSurfaceInMeters [Minimum Distance Above Surface in Meters] to [alt]
dwc:maximumDistanceAboveSurfaceInMeters [Maximum Distance Above Surface in Meters] to [alt]
dwc:minimumElevationInMeters [Minimum Elevation in Meters] to MIXS:0000093 [elev]
dwc:maximumElevationInMeters [Maximum Elevation in Meters] to MIXS:0000093 [elev]
dwc:eventDate [Event Date] to MIXS:0000011 [collection_date]
dwc:samplingProtocol [Sampling Protocol] to MIXS:0000016 [samp_mat_process]
dwc:associatedSequences [Associated Sequences] to MIXS:0000091 [url]
dwc:associatedTaxa [Associated Taxa] to MIXS:0000091 [url]

Syntactic mappings
V1 skos:narrowMatch, potentially need to be updated to skos:broadMatch

dwc:decimalLatitude [Decimal Latitude] to MIXS:0000009 [lat_lon]
dwc:decimalLongitude [Decimal Longitude] to MIXS:0000009 [lat_lon]
dwc:minimumDepthInMeters [Minimum Depth In Meters] to MIXS:0000018 [depth]
dwc:maximumDepthInMeters [Maximum Depth In Meters] to MIXS:0000018 [depth]
dwc:minimumDistanceAboveSurfaceInMeters [Minimum Distance Above Surface in Meters] to [alt]
dwc:maximumDistanceAboveSurfaceInMeters [Maximum Distance Above Surface in Meters] to [alt]
dwc:minimumElevationInMeters [Minimum Elevation in Meters] to MIXS:0000093 [elev]
dwc:maximumElevationInMeters [Maximum Elevation in Meters] to MIXS:0000093 [elev]

List of terms with updated semantic mappings
skos:broadMatch updated to skos:narrowMatch
"subject has skos:narrowMatch object"

dwc:verbatimCoordinates [Verbatim Coordinates] skos:narrowMatch MIXS:0000009 [lat_lon]

xRef https://github.com/tdwg/gbwg/issues/12#issue-805145896
"original spatial coordinates of the location" is semantically broader than "latitude and longitude"

dwc:samplingProtocol [Sampling Protocol] skos:narrowMatch MIXS:0000002 [samp_collect_device]

xRef https://github.com/tdwg/gbwg/issues/20#issue-805169799
Update comment: dwc:samplingProtocol covers both of the concepts samp_collect_device and samp_collect_process. Both of these terms list both, the names of (or links to) methods, or devices (either in the definition or in the examples). Based on the examples these could be skos:exactMatch, focusing on the definition, skos:narrowMatch would be appropriate. The information that this term and the samp_mat_process capture is often captured in the method steps in the EML (metadata about the dataset, not indexed in GBIF’s case), and less in the DwC terms themselves. This influences how people will use the terms in reality.

List of terms with updated semantic mappings
skos:narrowMatch updated to skos:broadMatch
"subject has skos:broadMatch object"

dwc:decimalLatitude [Decimal Latitude] to MIXS:0000009 [lat_lon]

xRef https://github.com/tdwg/gbwg/issues/12#issuecomment-810125107
DwC expects only the latitude (narrower), while MIxS expects both latitude and longitude (broader)

dwc:decimalLongitude [Decimal Longitude] to MIXS:0000009 [lat_lon]

xRef https://github.com/tdwg/gbwg/issues/12#issuecomment-810125107
DwC expects only the longitude (narrower), while MIxS expects both latitude and longitude (broader)

dwc:verbatimLatitude [Verbatim Latitude] to MIXS:0000009 [lat_lon]

xRef https://github.com/tdwg/gbwg/issues/12#issuecomment-810125107
DwC expects only the latitude (narrower), while MIxS expects both latitude and longitude (broader)

dwc:verbatimLongitude [Verbatim Longitude] to MIXS:0000009 [lat_lon]

xRef https://github.com/tdwg/gbwg/issues/12#issuecomment-810125107
DwC expects only the longitude (narrower), while MIxS expects both latitude and longitude (broader)

dwc:minimumDistanceAboveSurfaceInMeters [Minimum Distance Above Surface in Meters] to MIXS:0000018 [depth]

xRef https://github.com/tdwg/gbwg/issues/13#issue-805149090
DwC expects only the upper depth limit - negative value for depth - in meter (narrower), while MIxS expects either a single depth measurement or a range

dwc:maximumDistanceAboveSurfaceInMeters [Maximum Distance Above Surface in Meters] to MIXS:0000018 [depth]

xRef https://github.com/tdwg/gbwg/issues/13#issue-805149090
DwC expects only the lower depth limit - negative value for depth - in meter (narrower), while MIxS expects either a single depth measurement or a range

dwc:minimumDepthInMeters [Minimum Depth In Meters] to MIXS:0000018 [depth]

xRef https://github.com/tdwg/gbwg/issues/13#issuecomment-818165921
DwC expects only the upper depth limit in meter (narrower), while MIxS expects either a single depth measurement or a range

dwc:maximumDepthInMeters [Maximum Depth In Meters] to MIXS:0000018 [depth]

xRef https://github.com/tdwg/gbwg/issues/13#issuecomment-818165921
DwC expects only the lower depth limit in meter (narrower), while MIxS expects either a single depth measurement or a range

dwc:minimumDistanceAboveSurfaceInMeters [Minimum Distance Above Surface in Meters] to [alt]

xRef https://github.com/tdwg/gbwg/issues/14#issue-805153888
DwC expects only the lower altitude limit - positive value for altitude - in meter (narrower),  while MIxS expects a single altitude measurement at which the sample was taken

dwc:maximumDistanceAboveSurfaceInMeters [Maximum Distance Above Surface in Meters] to [alt]

xRef https://github.com/tdwg/gbwg/issues/14#issue-805153888
DwC expects only the upper altitude limit - positive value for altitude - in meter (narrower), while MIxS expects a single altitude measurement at which the sample was taken

dwc:minimumElevationInMeters [Minimum Elevation in Meters] to MIXS:0000093 [elev]

xRef https://github.com/tdwg/gbwg/issues/15#issuecomment-810365548
DwC expects only the lower elevation limit in meter (narrower), while MIxS expects a single elevation measurement at which the sample was taken

dwc:maximumElevationInMeters [Maximum Elevation in Meters] to MIXS:0000093 [elev]

xRef https://github.com/tdwg/gbwg/issues/15#issuecomment-810365548
DwC expects only the upper elevation limit in meter (narrower), while MIxS expects a single elevation measurement at which the sample was taken

dwc:associatedSequences [Associated Sequences] to MIXS:0000091 [url]

xRef https://github.com/tdwg/gbwg/issues/23#issuecomment-810376934
DwC expects only the identifiers (DOI to publication, global unique ID, URI) to associated taxa, while MIxS expects a url to anything related

dwc:associatedTaxa [Associated Taxa] to MIXS:0000091 [url]

xRef https://github.com/tdwg/gbwg/issues/23#issuecomment-810376934
DwC expects only the identifiers or names of associated taxa, while MIxS expects a url to anything related

List of terms with updated syntactic mappings
skos:narrowMatch updated to skos:broadMatch
"subject has skos:broadMatch object"

dwc:decimalLatitude [Decimal Latitude] to MIXS:0000009 [lat_lon]
dwc:decimalLongitude [Decimal Longitude] to MIXS:0000009 [lat_lon]
dwc:minimumDepthInMeters [Minimum Depth In Meters] to MIXS:0000018 [depth]
dwc:maximumDepthInMeters [Maximum Depth In Meters] to MIXS:0000018 [depth]
dwc:minimumDistanceAboveSurfaceInMeters [Minimum Distance Above Surface in Meters] to [alt]
dwc:maximumDistanceAboveSurfaceInMeters [Maximum Distance Above Surface in Meters] to [alt]
dwc:minimumElevationInMeters [Minimum Elevation in Meters] to MIXS:0000093 [elev]
dwc:maximumElevationInMeters [Maximum Elevation in Meters] to MIXS:0000093 [elev]

While reviewing the mapping, the following mappings were additionally updated:
syntax
xRef https://github.com/tdwg/gbwg/issues/13 (previously skos:exactMatch)

dwc:minimumDistanceAboveSurfaceInMeters skos:broadMatch MIXS:0000018[depth] (the DwC term only expects the value, while the MIxS term expects both value and unit)
dwc:maximumDistanceAboveSurfaceInMeters skos:broadMatch MIXS:0000018[depth] (the DwC term only expects the value, while the MIxS term expects both value and unit)