error calling Paginate: invoked multiple times with different arguments

Environment:

Ubuntu 16.04.4
hugo v0.41
test site's src: https://github.com/Honghe/hugo_test/tree/21f247beeebb2f0fb8e2e65e19aa4e976a09fa37
used theme: https://github.com/Honghe/hugo-concise/tree/fcf7a8b17212d5118a177869e1f5ae55441991b5

What I did:
Rename a folder in site src content folder.
Running command:
hugo serve --verboseLog --renderToDisk --disableFastRender --debug

Template themes/concise/layouts/index.html

.Paginate only used in this file.
.Site.Params.mainSections not set, use the default(posts)
when modify {{ $paginator := .Paginate (where .Data.Pages "Type" "in" .Site.Params.mainSections) }} to {{ $paginator := .Paginate (.Data.Pages) }}, the bug disappeared.

{{ define "main" }}
{{ $paginator := .Paginate (where .Data.Pages "Type" "in" .Site.Params.mainSections) }}

    {{ range $paginator.Pages }}

      {{ .Title }}

        <time>{{ .Date.Format "02 Jan 2006" }}</time>
        {{ if or .Params.tags .Params.categories }} | {{ end }}
        {{ if isset .Params "categories" }}
        categories: [ {{ range .Params.categories }}{{ . }} {{ end }} ]
        {{ end }}
        {{ if isset .Params "tags" }}
        tags: [ {{ range .Params.tags }}{{ . }} {{ end }} ]
        {{ end }}

    {{ end }}

{{ partial "tag_cloud.html" . }}
{{ partial "pagination.html" . }}
{{ end }}

Log:
INFO 2018/06/09 21:30:34 Received System Events: ["/home/henry/github_pages/hugo_test/content/demo/second": RENAME "/home/henry/github_pages/hugo_test/content/demo/hello": CREATE "/home/henry/github_pages/hugo_test/content/demo/second": RENAME]
adding created directory to watchlist /home/henry/github_pages/hugo_test/content/demo/hello

Change detected, rebuilding site
2018-06-09 21:30:34.953 +0800
DEBUG 2018/06/09 21:30:34 Rebuild for events ["\"/home/henry/github_pages/hugo_test/content/demo/second\": RENAME" "\"/home/henry/github_pages/hugo_test/content/demo/hello/drawing.svg\": CREATE" "\"/home/henry/github_pages/hugo_test/content/demo/hello/index.md\": CREATE"]
Source changed "/home/henry/github_pages/hugo_test/content/demo/second": RENAME
Source changed "/home/henry/github_pages/hugo_test/content/demo/hello/drawing.svg": CREATE
Source changed "/home/henry/github_pages/hugo_test/content/demo/hello/index.md": CREATE
INFO 2018/06/09 21:30:34 found taxonomies: map[string]string{"tag":"tags", "category":"categories"}
DEBUG 2018/06/09 21:30:34 Render home to "/index.html" with layouts ["page/index.en.html.html" "theme/page/index.en.html.html" "page/home.en.html.html" "theme/page/home.en.html.html" "page/list.en.html.html" "theme/page/list.en.html.html" "page/index.html.html" "theme/page/index.html.html" "page/home.html.html" "theme/page/home.html.html" "page/list.html.html" "theme/page/list.html.html" "page/index.en.html" "theme/page/index.en.html" "page/home.en.html" "theme/page/home.en.html" "page/list.en.html" "theme/page/list.en.html" "page/index.html" "theme/page/index.html" "page/home.html" "theme/page/home.html" "page/list.html" "theme/page/list.html" "index.en.html.html" "theme/index.en.html.html" "home.en.html.html" "theme/home.en.html.html" "list.en.html.html" "theme/list.en.html.html" "index.html.html" "theme/index.html.html" "home.html.html" "theme/home.html.html" "list.html.html" "theme/list.html.html" "index.en.html" "theme/index.en.html" "home.en.html" "theme/home.en.html" "list.en.html" "theme/list.en.html" "index.html""theme/index.html" "home.html" "theme/home.html" "list.html" "theme/list.html" "_default/index.en.html.html" "theme/_default/index.en.html.html" "_default/home.en.html.html" "theme/_default/home.en.html.html" "_default/list.en.html.html" "theme/_default/list.en.html.html" "_default/index.html.html" "theme/_default/index.html.html" "_default/home.html.html" "theme/_default/home.html.html" "_default/list.html.html" "theme/_default/list.html.html" "_default/index.en.html" "theme/_default/index.en.html" "_default/home.en.html" "theme/_default/home.en.html" "_default/list.en.html" "theme/_default/list.en.html" "_default/index.html" "theme/_default/index.html" "_default/home.html" "theme/_default/home.html" "_default/list.html" "theme/_default/list.html"]
DEBUG 2018/06/09 21:30:34 Render page to "/demo/post2/index.html" with layouts ["demo/single.en.html.html" "theme/demo/single.en.html.html" "demo/single.html.html" "theme/demo/single.html.html" "demo/single.en.html" "theme/demo/single.en.html" "demo/single.html" "theme/demo/single.html" "_default/single.en.html.html" "theme/_default/single.en.html.html" "_default/single.html.html" "theme/_default/single.html.html" "_default/single.en.html" "theme/_default/single.en.html" "_default/single.html" "theme/_default/single.html"]
DEBUG 2018/06/09 21:30:34 Render page to "/demo/hello/index.html" with layouts ["demo/single.en.html.html" "theme/demo/single.en.html.html" "demo/single.html.html" "theme/demo/single.html.html" "demo/single.en.html" "theme/demo/single.en.html" "demo/single.html" "theme/demo/single.html" "_default/single.en.html.html" "theme/_default/single.en.html.html" "_default/single.html.html" "theme/_default/single.html.html" "_default/single.en.html" "theme/_default/single.en.html" "_default/single.html" "theme/_default/single.html"]
DEBUG 2018/06/09 21:30:34 Render page to "/demo/second/index.html" with layouts ["demo/single.en.html.html" "theme/demo/single.en.html.html" "demo/single.html.html" "theme/demo/single.html.html" "demo/single.en.html" "theme/demo/single.en.html" "demo/single.html" "theme/demo/single.html" "_default/single.en.html.html" "theme/_default/single.en.html.html" "_default/single.html.html" "theme/_default/single.html.html" "_default/single.en.html" "theme/_default/single.en.html" "_default/single.html" "theme/_default/single.html"]
ERROR 2018/06/09 21:30:34 Error while rendering "home" in "": template: /home/henry/github_pages/hugo_test/themes/concise/layouts/index.html:2:17: executing "main" at <.Paginate>: error calling Paginate: invoked multiple times with different arguments
WARN 2018/06/09 21:30:34 template: /home/henry/github_pages/hugo_test/themes/concise/layouts/index.html:2:17: executing "main" at <.Paginate>: error calling Paginate: invoked multiple times with different arguments
DEBUG 2018/06/09 21:30:34 Render paginator for page "_index.md"
DEBUG 2018/06/09 21:30:34 creating alias: /page/1/index.html redirecting to http://localhost:44987/hugo_test/
INFO 2018/06/09 21:30:34 Alias "/page/1/index.html" translated to "page/1/index.html"
DEBUG 2018/06/09 21:30:34 Render page to "/demo/hello/index.html" with layouts ["demo/single.en.html.html" "theme/demo/single.en.html.html" "demo/single.html.html" "theme/demo/single.html.html" "demo/single.en.html" "theme/demo/single.en.html" "demo/single.html" "theme/demo/single.html" "_default/single.en.html.html" "theme/_default/single.en.html.html" "_default/single.html.html" "theme/_default/single.html.html" "_default/single.en.html" "theme/_default/single.en.html" "_default/single.html" "theme/_default/single.html"]
DEBUG 2018/06/09 21:30:34 Render taxonomy to "/categories/cat1/index.html" with layouts ["categories/category.en.html.html" "theme/categories/category.en.html.html" "categories/taxonomy.en.html.html" "theme/categories/taxonomy.en.html.html" "categories/list.en.html.html" "theme/categories/list.en.html.html" "categories/category.html.html" "theme/categories/category.html.html" "categories/taxonomy.html.html" "theme/categories/taxonomy.html.html" "categories/list.html.html" "theme/categories/list.html.html" "categories/category.en.html" "theme/categories/category.en.html" "categories/taxonomy.en.html" "theme/categories/taxonomy.en.html" "categories/list.en.html" "theme/categories/list.en.html" "categories/category.html" "theme/categories/category.html" "categories/taxonomy.html" "theme/categories/taxonomy.html" "categories/list.html" "theme/categories/list.html" "taxonomy/category.en.html.html" "theme/taxonomy/category.en.html.html" "taxonomy/taxonomy.en.html.html" "theme/taxonomy/taxonomy.en.html.html" "taxonomy/list.en.html.html" "theme/taxonomy/list.en.html.html" "taxonomy/category.html.html" "theme/taxonomy/category.html.html" "taxonomy/taxonomy.html.html" "theme/taxonomy/taxonomy.html.html" "taxonomy/list.html.html" "theme/taxonomy/list.html.html" "taxonomy/category.en.html" "theme/taxonomy/category.en.html" "taxonomy/taxonomy.en.html" "theme/taxonomy/taxonomy.en.html" "taxonomy/list.en.html" "theme/taxonomy/list.en.html" "taxonomy/category.html" "theme/taxonomy/category.html" "taxonomy/taxonomy.html" "theme/taxonomy/taxonomy.html" "taxonomy/list.html" "theme/taxonomy/list.html" "category/category.en.html.html" "theme/category/category.en.html.html" "category/taxonomy.en.html.html" "theme/category/taxonomy.en.html.html" "category/list.en.html.html" "theme/category/list.en.html.html" "category/category.html.html" "theme/category/category.html.html" "category/taxonomy.html.html" "theme/category/taxonomy.html.html" "category/list.html.html" "theme/category/list.html.html" "category/category.en.html" "theme/category/category.en.html" "category/taxonomy.en.html" "theme/category/taxonomy.en.html" "category/list.en.html" "theme/category/list.en.html" "category/category.html" "theme/category/category.html" "category/taxonomy.html" "theme/category/taxonomy.html" "category/list.html" "theme/category/list.html" "_default/category.en.html.html" "theme/_default/category.en.html.html" "_default/taxonomy.en.html.html" "theme/_default/taxonomy.en.html.html" "_default/list.en.html.html" "theme/_default/list.en.html.html" "_default/category.html.html" "theme/_default/category.html.html" "_default/taxonomy.html.html" "theme/_default/taxonomy.html.html" "_default/list.html.html" "theme/_default/list.html.html" "_default/category.en.html" "theme/_default/category.en.html" "_default/taxonomy.en.html" "theme/_default/taxonomy.en.html" "_default/list.en.html" "theme/_default/list.en.html" "_default/category.html" "theme/_default/category.html" "_default/taxonomy.html" "theme/_default/taxonomy.html" "_default/list.html" "theme/_default/list.html"]
DEBUG 2018/06/09 21:30:34 Render taxonomy to "/tags/tag2/index.html" with layouts ["tags/tag.en.html.html" "theme/tags/tag.en.html.html" "tags/taxonomy.en.html.html" "theme/tags/taxonomy.en.html.html" "tags/list.en.html.html" "theme/tags/list.en.html.html" "tags/tag.html.html" "theme/tags/tag.html.html" "tags/taxonomy.html.html" "theme/tags/taxonomy.html.html" "tags/list.html.html" "theme/tags/list.html.html" "tags/tag.en.html" "theme/tags/tag.en.html" "tags/taxonomy.en.html" "theme/tags/taxonomy.en.html" "tags/list.en.html" "theme/tags/list.en.html" "tags/tag.html" "theme/tags/tag.html" "tags/taxonomy.html" "theme/tags/taxonomy.html" "tags/list.html" "theme/tags/list.html" "taxonomy/tag.en.html.html" "theme/taxonomy/tag.en.html.html" "taxonomy/taxonomy.en.html.html" "theme/taxonomy/taxonomy.en.html.html" "taxonomy/list.en.html.html" "theme/taxonomy/list.en.html.html" "taxonomy/tag.html.html" "theme/taxonomy/tag.html.html" "taxonomy/taxonomy.html.html" "theme/taxonomy/taxonomy.html.html" "taxonomy/list.html.html" "theme/taxonomy/list.html.html" "taxonomy/tag.en.html" "theme/taxonomy/tag.en.html" "taxonomy/taxonomy.en.html" "theme/taxonomy/taxonomy.en.html" "taxonomy/list.en.html" "theme/taxonomy/list.en.html" "taxonomy/tag.html" "theme/taxonomy/tag.html" "taxonomy/taxonomy.html" "theme/taxonomy/taxonomy.html" "taxonomy/list.html" "theme/taxonomy/list.html" "tag/tag.en.html.html" "theme/tag/tag.en.html.html" "tag/taxonomy.en.html.html" "theme/tag/taxonomy.en.html.html" "tag/list.en.html.html" "theme/tag/list.en.html.html" "tag/tag.html.html" "theme/tag/tag.html.html" "tag/taxonomy.html.html" "theme/tag/taxonomy.html.html" "tag/list.html.html" "theme/tag/list.html.html" "tag/tag.en.html" "theme/tag/tag.en.html" "tag/taxonomy.en.html" "theme/tag/taxonomy.en.html" "tag/list.en.html" "theme/tag/list.en.html" "tag/tag.html" "theme/tag/tag.html" "tag/taxonomy.html" "theme/tag/taxonomy.html" "tag/list.html" "theme/tag/list.html" "_default/tag.en.html.html" "theme/_default/tag.en.html.html" "_default/taxonomy.en.html.html" "theme/_default/taxonomy.en.html.html" "_default/list.en.html.html" "theme/_default/list.en.html.html" "_default/tag.html.html" "theme/_default/tag.html.html" "_default/taxonomy.html.html" "theme/_default/taxonomy.html.html" "_default/list.html.html" "theme/_default/list.html.html" "_default/tag.en.html" "theme/_default/tag.en.html" "_default/taxonomy.en.html" "theme/_default/taxonomy.en.html" "_default/list.en.html" "theme/_default/list.en.html" "_default/tag.html" "theme/_default/tag.html" "_default/taxonomy.html" "theme/_default/taxonomy.html" "_default/list.html" "theme/_default/list.html"]
DEBUG 2018/06/09 21:30:34 Render section to "/demo/index.html" with layouts ["demo/demo.en.html.html" "theme/demo/demo.en.html.html" "demo/section.en.html.html" "theme/demo/section.en.html.html" "demo/list.en.html.html" "theme/demo/list.en.html.html" "demo/demo.html.html" "theme/demo/demo.html.html" "demo/section.html.html" "theme/demo/section.html.html" "demo/list.html.html" "theme/demo/list.html.html" "demo/demo.en.html" "theme/demo/demo.en.html" "demo/section.en.html" "theme/demo/section.en.html" "demo/list.en.html" "theme/demo/list.en.html" "demo/demo.html" "theme/demo/demo.html" "demo/section.html" "theme/demo/section.html" "demo/list.html" "theme/demo/list.html" "section/demo.en.html.html" "theme/section/demo.en.html.html" "section/section.en.html.html" "theme/section/section.en.html.html" "section/list.en.html.html" "theme/section/list.en.html.html" "section/demo.html.html" "theme/section/demo.html.html" "section/section.html.html" "theme/section/section.html.html" "section/list.html.html" "theme/section/list.html.html" "section/demo.en.html" "theme/section/demo.en.html" "section/section.en.html" "theme/section/section.en.html" "section/list.en.html" "theme/section/list.en.html" "section/demo.html" "theme/section/demo.html" "section/section.html" "theme/section/section.html" "section/list.html" "theme/section/list.html" "_default/demo.en.html.html" "theme/_default/demo.en.html.html" "_default/section.en.html.html" "theme/_default/section.en.html.html" "_default/list.en.html.html" "theme/_default/list.en.html.html" "_default/demo.html.html" "theme/_default/demo.html.html" "_default/section.html.html" "theme/_default/section.html.html" "_default/list.html.html" "theme/_default/list.html.html" "_default/demo.en.html" "theme/_default/demo.en.html" "_default/section.en.html" "theme/_default/section.en.html" "_default/list.en.html" "theme/_default/list.en.html" "_default/demo.html" "theme/_default/demo.html" "_default/section.html" "theme/_default/section.html" "_default/list.html" "theme/_default/list.html"]
DEBUG 2018/06/09 21:30:34 Render taxonomyTerm to "/categories/index.html" with layouts ["categories/category.terms.en.html.html" "theme/categories/category.terms.en.html.html" "categories/terms.en.html.html" "theme/categories/terms.en.html.html" "categories/list.en.html.html" "theme/categories/list.en.html.html" "categories/category.terms.html.html" "theme/categories/category.terms.html.html" "categories/terms.html.html" "theme/categories/terms.html.html" "categories/list.html.html" "theme/categories/list.html.html" "categories/category.terms.en.html" "theme/categories/category.terms.en.html" "categories/terms.en.html" "theme/categories/terms.en.html" "categories/list.en.html" "theme/categories/list.en.html" "categories/category.terms.html" "theme/categories/category.terms.html" "categories/terms.html" "theme/categories/terms.html" "categories/list.html" "theme/categories/list.html" "taxonomy/category.terms.en.html.html" "theme/taxonomy/category.terms.en.html.html" "taxonomy/terms.en.html.html" "theme/taxonomy/terms.en.html.html" "taxonomy/list.en.html.html" "theme/taxonomy/list.en.html.html" "taxonomy/category.terms.html.html" "theme/taxonomy/category.terms.html.html" "taxonomy/terms.html.html" "theme/taxonomy/terms.html.html" "taxonomy/list.html.html" "theme/taxonomy/list.html.html" "taxonomy/category.terms.en.html" "theme/taxonomy/category.terms.en.html" "taxonomy/terms.en.html" "theme/taxonomy/terms.en.html" "taxonomy/list.en.html" "theme/taxonomy/list.en.html" "taxonomy/category.terms.html" "theme/taxonomy/category.terms.html" "taxonomy/terms.html" "theme/taxonomy/terms.html" "taxonomy/list.html" "theme/taxonomy/list.html" "category/category.terms.en.html.html" "theme/category/category.terms.en.html.html" "category/terms.en.html.html" "theme/category/terms.en.html.html" "category/list.en.html.html" "theme/category/list.en.html.html" "category/category.terms.html.html" "theme/category/category.terms.html.html" "category/terms.html.html" "theme/category/terms.html.html" "category/list.html.html" "theme/category/list.html.html" "category/category.terms.en.html" "theme/category/category.terms.en.html" "category/terms.en.html" "theme/category/terms.en.html" "category/list.en.html" "theme/category/list.en.html" "category/category.terms.html" "theme/category/category.terms.html" "category/terms.html" "theme/category/terms.html" "category/list.html" "theme/category/list.html" "_default/category.terms.en.html.html" "theme/_default/category.terms.en.html.html" "_default/terms.en.html.html" "theme/_default/terms.en.html.html" "_default/list.en.html.html""theme/_default/list.en.html.html" "_default/category.terms.html.html" "theme/_default/category.terms.html.html" "_default/terms.html.html" "theme/_default/terms.html.html""_default/list.html.html" "theme/_default/list.html.html" "_default/category.terms.en.html" "theme/_default/category.terms.en.html" "_default/terms.en.html" "theme/_default/terms.en.html" "_default/list.en.html" "theme/_default/list.en.html" "_default/category.terms.html" "theme/_default/category.terms.html" "_default/terms.html" "theme/_default/terms.html" "_default/list.html" "theme/_default/list.html"]
DEBUG 2018/06/09 21:30:34 Render taxonomyTerm to "/tags/index.html" with layouts ["tags/tag.terms.en.html.html" "theme/tags/tag.terms.en.html.html" "tags/terms.en.html.html" "theme/tags/terms.en.html.html" "tags/list.en.html.html" "theme/tags/list.en.html.html" "tags/tag.terms.html.html" "theme/tags/tag.terms.html.html" "tags/terms.html.html" "theme/tags/terms.html.html" "tags/list.html.html" "theme/tags/list.html.html" "tags/tag.terms.en.html" "theme/tags/tag.terms.en.html" "tags/terms.en.html" "theme/tags/terms.en.html" "tags/list.en.html" "theme/tags/list.en.html" "tags/tag.terms.html" "theme/tags/tag.terms.html" "tags/terms.html" "theme/tags/terms.html" "tags/list.html" "theme/tags/list.html" "taxonomy/tag.terms.en.html.html" "theme/taxonomy/tag.terms.en.html.html" "taxonomy/terms.en.html.html" "theme/taxonomy/terms.en.html.html" "taxonomy/list.en.html.html" "theme/taxonomy/list.en.html.html" "taxonomy/tag.terms.html.html" "theme/taxonomy/tag.terms.html.html" "taxonomy/terms.html.html" "theme/taxonomy/terms.html.html""taxonomy/list.html.html" "theme/taxonomy/list.html.html" "taxonomy/tag.terms.en.html" "theme/taxonomy/tag.terms.en.html" "taxonomy/terms.en.html" "theme/taxonomy/terms.en.html" "taxonomy/list.en.html" "theme/taxonomy/list.en.html" "taxonomy/tag.terms.html" "theme/taxonomy/tag.terms.html" "taxonomy/terms.html" "theme/taxonomy/terms.html" "taxonomy/list.html" "theme/taxonomy/list.html" "tag/tag.terms.en.html.html" "theme/tag/tag.terms.en.html.html" "tag/terms.en.html.html" "theme/tag/terms.en.html.html" "tag/list.en.html.html" "theme/tag/list.en.html.html" "tag/tag.terms.html.html" "theme/tag/tag.terms.html.html" "tag/terms.html.html" "theme/tag/terms.html.html" "tag/list.html.html" "theme/tag/list.html.html" "tag/tag.terms.en.html" "theme/tag/tag.terms.en.html" "tag/terms.en.html" "theme/tag/terms.en.html" "tag/list.en.html" "theme/tag/list.en.html" "tag/tag.terms.html" "theme/tag/tag.terms.html" "tag/terms.html" "theme/tag/terms.html" "tag/list.html" "theme/tag/list.html" "_default/tag.terms.en.html.html" "theme/_default/tag.terms.en.html.html" "_default/terms.en.html.html" "theme/_default/terms.en.html.html" "_default/list.en.html.html" "theme/_default/list.en.html.html" "_default/tag.terms.html.html" "theme/_default/tag.terms.html.html" "_default/terms.html.html" "theme/_default/terms.html.html" "_default/list.html.html" "theme/_default/list.html.html" "_default/tag.terms.en.html" "theme/_default/tag.terms.en.html" "_default/terms.en.html" "theme/_default/terms.en.html" "_default/list.en.html" "theme/_default/list.en.html" "_default/tag.terms.html" "theme/_default/tag.terms.html" "_default/terms.html" "theme/_default/terms.html" "_default/list.html" "theme/_default/list.html"]
DEBUG 2018/06/09 21:30:34 Render taxonomy to "/tags/tag1/index.html" with layouts ["tags/tag.en.html.html" "theme/tags/tag.en.html.html" "tags/taxonomy.en.html.html" "theme/tags/taxonomy.en.html.html" "tags/list.en.html.html" "theme/tags/list.en.html.html" "tags/tag.html.html" "theme/tags/tag.html.html" "tags/taxonomy.html.html" "theme/tags/taxonomy.html.html" "tags/list.html.html" "theme/tags/list.html.html" "tags/tag.en.html" "theme/tags/tag.en.html" "tags/taxonomy.en.html" "theme/tags/taxonomy.en.html" "tags/list.en.html" "theme/tags/list.en.html" "tags/tag.html" "theme/tags/tag.html" "tags/taxonomy.html" "theme/tags/taxonomy.html" "tags/list.html" "theme/tags/list.html" "taxonomy/tag.en.html.html" "theme/taxonomy/tag.en.html.html" "taxonomy/taxonomy.en.html.html" "theme/taxonomy/taxonomy.en.html.html" "taxonomy/list.en.html.html" "theme/taxonomy/list.en.html.html" "taxonomy/tag.html.html" "theme/taxonomy/tag.html.html" "taxonomy/taxonomy.html.html" "theme/taxonomy/taxonomy.html.html" "taxonomy/list.html.html" "theme/taxonomy/list.html.html" "taxonomy/tag.en.html" "theme/taxonomy/tag.en.html" "taxonomy/taxonomy.en.html" "theme/taxonomy/taxonomy.en.html" "taxonomy/list.en.html" "theme/taxonomy/list.en.html" "taxonomy/tag.html" "theme/taxonomy/tag.html" "taxonomy/taxonomy.html" "theme/taxonomy/taxonomy.html" "taxonomy/list.html" "theme/taxonomy/list.html" "tag/tag.en.html.html" "theme/tag/tag.en.html.html" "tag/taxonomy.en.html.html" "theme/tag/taxonomy.en.html.html" "tag/list.en.html.html" "theme/tag/list.en.html.html" "tag/tag.html.html" "theme/tag/tag.html.html" "tag/taxonomy.html.html" "theme/tag/taxonomy.html.html" "tag/list.html.html" "theme/tag/list.html.html" "tag/tag.en.html" "theme/tag/tag.en.html" "tag/taxonomy.en.html" "theme/tag/taxonomy.en.html" "tag/list.en.html" "theme/tag/list.en.html" "tag/tag.html" "theme/tag/tag.html" "tag/taxonomy.html" "theme/tag/taxonomy.html" "tag/list.html" "theme/tag/list.html" "_default/tag.en.html.html" "theme/_default/tag.en.html.html" "_default/taxonomy.en.html.html" "theme/_default/taxonomy.en.html.html" "_default/list.en.html.html" "theme/_default/list.en.html.html" "_default/tag.html.html" "theme/_default/tag.html.html" "_default/taxonomy.html.html" "theme/_default/taxonomy.html.html" "_default/list.html.html" "theme/_default/list.html.html" "_default/tag.en.html" "theme/_default/tag.en.html" "_default/taxonomy.en.html" "theme/_default/taxonomy.en.html" "_default/list.en.html" "theme/_default/list.en.html" "_default/tag.html" "theme/_default/tag.html" "_default/taxonomy.html" "theme/_default/taxonomy.html" "_default/list.html" "theme/_default/list.html"]
DEBUG 2018/06/09 21:30:34 Render XML for "sitemap" to "sitemap.xml"
DEBUG 2018/06/09 21:30:34 Render XML for "" to "/index.xml"
DEBUG 2018/06/09 21:30:34 Render XML for "" to "/demo/index.xml"
DEBUG 2018/06/09 21:30:34 Render XML for "Tag1" to "/tags/tag1/index.xml"
DEBUG 2018/06/09 21:30:34 Render XML for "Tag2" to "/tags/tag2/index.xml"
DEBUG 2018/06/09 21:30:34 Render XML for "Tags" to "/tags/index.xml"
DEBUG 2018/06/09 21:30:34 Render XML for "Cat1" to "/categories/cat1/index.xml"
DEBUG 2018/06/09 21:30:34 Render XML for "Categories" to "/categories/index.xml"
Total in 28 ms
ERROR 2018/06/09 21:30:34 Failed to rebuild site: logged 1 error(s)

This is the Hugo bugs issue tracker.
For support please visit https://discourse.gohugo.io

It seems this is a bug.

@Honghe there was an issue related to this, fixed in https://github.com/gohugoio/hugo/commit/dc4226a8b27e03e31068fc945daab885d3819d04

@bep It works. Nice job!

@bep, But, there is new problem, the old output not to be cleaned.
I use hugo server --renderToDisk  to debug the outputDir.
After I rename a folder, such as folder1 -> folder2, the output dir still contains the folder1, so there are duplicated document item entry in home page by paginator.
folder1
|--a.html
|--b.html
folder2
|--a.html
|--b.html

I have tried hugo  --renderToDisk --disableFastRender --cleanDestinationDir --ignoreCache --gc, it doesn't work too.
Is there something wrong with my template/theme?


Simplify user configuration

Simplify user configuration by already pre-setting map and packages properties in System.config call argument.
User configuration is now easier, redundant calls like this are a thing of the past:
const map:any = {
  map: {
    'key': 'val'
  }
};

Here's how to use it now:
const map:any = {
  'key': 'val'
};

Same goes for packages.
ps: PRing this because it took me a while to figure out why my configuration wasn't working. This small improvement may help beginners!

Just signed the CLA!

Realizing I still have issues with SystemJS user configuration.
This PR may help, but it's still not enough for me, will dig into the docs a little more...

Forget it, this PR is dumb!


Fail CI if package.json and yarn lock are out of sync

This would prevent builds for PRs that only update the package.json to succeed.

ha - much appreciated.

Thanks!


Add more info on missing alerts

FYI @udh-mendix

@MarkvanMents - would you mind taking a quick look, please? Thanks!

Thanks for the review, @MarkvanMents ! I have replied to your comments.

Yes please @MarkvanMents , and thank you!


Fixing API link in plugins view

On plugins view, when a specific api plugin is displayed, the link is not valid because expected parameter is 'api_id', not 'id'

@d3rwan , thanks for the contribution!


Different background colors for different languages in a multi-language file

I want to make my multi-language files(such as PHP or ruby on rails) more readable by having different background colors for different languages .
For TextMate it's possible to set particular background color for different scope.TextMate manual: Theme, I tried to do it on vscode but it doesn't work.
I also tried the color themes on this blog posts: Rails TextMate Themes. I still can't get different background colors for the two languages.

@aeschli not sure if you or @alexandrudima

Themes can set the background colors, but in VCOde we ignore these as it conflicts with other background colors (selection, mark occurrence, find replace...)
To make this work we would need to invest time in using transparency everywhere.

Not planned.


Modify olm version in e2e test

Description of the change:
Install OLM version "0.15.1" for e2e tests as
install manifests are present in sdk locally.
Motivation for the change:
To reduce calls to GitHub.
Issue: #3964
Note: Latest version of OLM is still being tested in subcommand-olm-install.sh and install_test.go - this wouldn't eliminate requests to GitHub entirely.
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

/lgtm


IE11, svg with tabindex=0 does not have tabIndex property

In IE11, a SVG with tabindex="0" does not have a tabIndex property so gets added to the orderedTabbables array no matter where it is in the DOM.
candidateIndex = parseInt(candidate.getAttribute('tabindex'), 10) || candidate.tabIndex;

Always triggers the OR condition if tabindex="0", which then assumes tabIndex is a valid property. SVGs return undefined for the tabIndex property.

🤔 In theory I see that there should be a possible bug here. And we should change the code regardless. But I want to make sure I'm fixing the problem you're reporting ... and I'm actually having trouble reproducing it, @straker.
I added a new test case with the following HTML:
<svg id="svg-1" height="100" width="100" tabindex="0">
  <circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="red" />
</svg>
<svg id="svg-2" height="100" width="100" tabindex="-1">
  <circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="blue" />
</svg>
<svg id="svg-3" height="100" width="100">
  <circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="green" />
</svg>

As expected, running tabbable on this case returns an array with only the first SVG — both in Chrome and in IE11. So, things actually seem to be working ok?
Could you please explain more about what the difference between expected and actual behavior is?
(Also: IE11 and maybe some Edge versions through everything off by making <svg> elements focusable by default, and you need to turn that off with focusable="false" if you want behavior to match other browsers. Maybe should document this caveat in the README, since I don't know a way around it.)

So the problem is that the svg is always added to the front of the array.
So if there are other tabble elements before the svg, the svg will still be
first on the list.
<button>1st</button>
<svg id="svg-1" height="100" width="100" tabindex="0">
  <circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="red"
/>
</svg>

Returns
[svg, button

On Sun, Apr 29, 2018, 7:56 AM David Clark<EMAIL_ADDRESS>wrote:

🤔 In theory I see that there should be a possible bug here. And we
should change the code regardless. But I want to make sure I'm fixing the
problem you're reporting ... and I'm actually having trouble reproducing
it, @straker https://github.com/straker.
I added a new test case with the following HTML:

As expected, running tabbable on this case returns an array with only the
first SVG — both in Chrome and in IE11. So, things actually seem to be
working ok?
Could you please explain more about what the difference between expected
and actual behavior is?
(Also: IE11 and maybe some Edge versions through everything off by making
 elements focusable by default, and you need to turn that off with
focusable="false" if you want behavior to match other browsers. Maybe
should document this caveat in the README, since I don't know a way around
it.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/davidtheclark/tabbable/issues/24#issuecomment-385257226,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUgwy-DaFXJJL3zbnZZ7hVvXdXGoDSWks5ttdSZgaJpZM4TkQmc
.

Ah, I see. Will fix up my test case to confirm the fix to that problem.


Build pg_catalog in an empty project

Because we create every pg table through View, if a project without any dataset, some view creating SQL will be wrong.
all_table view
https://github.com/Canner/canner-metric-layer/blob/3ef2396a31f0c9523e92e9ee04ae9ddf7046720e/core/cml-postgres-wire-protocol/src/main/java/io/cml/pgcatalog/builder/BigQueryUtils.java#L94-L99
all_columns view
https://github.com/Canner/canner-metric-layer/blob/3ef2396a31f0c9523e92e9ee04ae9ddf7046720e/core/cml-postgres-wire-protocol/src/main/java/io/cml/pgcatalog/builder/BigQueryUtils.java#L108-L115

pg-wire is archived.


Model: Use Set to track visited nodes in evaluateDerivedProps

Given an efficient implementation, this should bring lookup time
down to O(1), instead of always doing a linear search.
This PR contains:

[ ] Changelog
[ ] Documentation
[ ] Tests

@mortoray Ah, it does indeed use the ES6 Set type. We use a Set for tracking the visited node in the main diff algoritm as well. I'll write a polyfill.


readme: added link to pre-compiled binaries

Pre-compiled libuv v1.38.1 for Android, Linux, Windows, MacOS and iOS, which could both accelerate and simplify the compiling process.

Thanks for the pull request, but I don't think we'll be linking to binaries that we didn't build (and therefore can't vouch for) ourselves.
A link in the wiki is probably okay but not in the README.


[FLINK-36095][table-planner] KeyedLookupJoinWrapper should shuffle by input upsertKey instead of join key to avoid changelog disordering

What is the purpose of the change
If user encounter the NDU issue caused by a lookup join and enable the TRY_RESOLVE mode, the current KeyedLookupJoinWrapper implementation use the join key as the shuffle key, this may lead to changelog disordering issue. It should be fixed to use input upsertKey(or the complete row if upsertKey is empty) instead of join key.
Also, there's a hotfix for test values sink: KeyedUpsertingSinkFunction which didn't implement state recovery properly and will encounter a RuntimeException says  "Tried to delete a value that wasn't inserted first. "
Brief change log

fix StreamExecLookupJoin#createSyncLookupJoinWithState to use input upsertKey as the shuffle key.
update all related tests to verify the upsertKey takes effect
add a new restore case: LookupJoinTestPrograms.LOOKUP_JOIN_WITH_TRY_RESOLVE
fix KeyedUpsertingSinkFunction and add restore tests

Verifying this change

existing NonDeterministicDagTest &  LookupJoinXx tests
newly added LookupJoinTestPrograms.LOOKUP_JOIN_WITH_TRY_RESOLVE
newly added TableSinkTestPrograms.SINK_UPSERT

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no )
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

@xuyangzhong thank you for reviewing this!


Explanation of field: excludeLite

RE: : https://github.com/Esterni/pyracing/blob/2c072619ae1ef84e6452b1e67f7e1d19b2e36f4c/pyracing/client.py#L107
So this isn't a real issue that has a defect, but is some knowledge that might help understand why this parameter exists.
At some point, iRacing was considering (but it never came to light) a "lite" version of iRacing.  Not too much details were ever unveiled but it was free to play and gave you access to a limited set of content. No paid content, nor was the option to pay content available.
Some screenshots: https://imgur.com/a/4PY3l

Huh, interesting. Good to know, thanks for the info! I'll add the link to that Imgur album in the docs :)


Bump required celery version

Celery 4.x had its end of life in August 2021, which means that the dependency should probably be upgraded even though 5.x wants to move fast and break things.
Since invenio-celery already supported celery 5.0.x, upgrading to 5.1.x should probably not be too jarring of a move to make.
The relevant change that motivates this PR is the added support for usernames in addition to passwords for connections with Redis (which added this ACL feature not too long ago).
I have just taken invenio-celery for a test ride by setting up a fresh Invenio-RDM instance and keeping watch over the fixture creation, which did not show any related errors.
I'll keep an eye out for celery-related logs in invenio-cli run tomorrow.

The tasks scheduled today (cleanup_drafts from drafts-resources, update_expired_embargos from rdm-records, clean_session_table from accounts) succeeded without errors, so I'm marking this as ready for review.


Josh

Issue Type: Bug

Click on angular.json file
VSCODE freezes (happens in less than a second, based on not being able to move mouse pointer more than 1/8" on screen)
Computer automatically restarts

(I can open the above json file with other editors. I tried to open other json files with VSCODE same problem as above - these included files from sources that were edited with VSCODE and json files that were not edited in VSCODE or associated with project using VSCODE.
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-11T01:11:34.018Z)
OS version: Darwin x64 20.1.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
29, 7, 3

Memory (System)
16.00GB (7.76GB free)

Process Argv
--crash-reporter-id 70f6be8a-5381-49ff-b89e-0d4cad5986ee

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

ng-template
Ang
0.1100.1

vscode-browser-preview
auc
0.6.7

npm-intellisense
chr
1.3.1

vscode-npm-script
eg2
0.3.13

code-runner
for
0.11.1

Angular2
joh
9.1.2

mongodb-vscode
mon
0.2.1

debugger-for-chrome
msj
4.12.11

/needsMoreInfo
Is it reproducible with all extensions disabled?
You can try this with F1 and >Developer: Reload Window With Extensions Disabled

/needsMoreInfo
Is it reproducible with all extensions disabled?
You can try this with F1 and >Developer: Reload Window With Extensions Disabled

IllusionMH - I can access the the file when all extension are disabled. I guess now I need to figure out which extension it is. This issue began two days ago. Besides looking fro recently updated extensions, is there another way to do this?

It doesn't look like you have many of them. I usually either disable all one by one and see if problem is gone and recheck with only that extension enabled to confirm.
I saw there is issue tracking implementation for extensions bi-sect, but not sure if it is implemented already.


Bump identity-framework-version 5.20.280

Bump identity-framework-version 5.20.280

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/1615066284

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/1615066284
Status: failure

This version bump is already covered with another PR. Hence closing the PR.


Closes: #1 Update validations.py python script

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

ok


Mailsac.com is down

Apache Test page is showing on mailsac.com, what's wrong?

mailsac 2.0 is up and the site should be working again.
I hope to release the core of mailsac 2 relatively soon. It has been rewritten from scratch and is much, much easier to setup.

I was trying to set up mailsac on my own server yesterday but I found all the server links were hard-coded as mailsac.com, which was very confusing. And I figured out that the mailing functionality was normal, it looks like the repo's codes is somehow different with these used by mailsac.com. (Just guessing, because the UI differs very much)
And also I could not found license information about this repository.
Finally I've found this issue :) . May I ask when will the codes of mailsac 2 be updated to this repo? I'm very interested in this project, because other mail server products like Postfix or sendmail are usually hard to configure, but this one is really easy.

Hey, I estimate only a handful of hours to finish the next version to the point of re-release. I just need to sit down and do it..
The license is MIT but it may not be in full text in the repo at the moment; sorry.
v2 is a complete rewrite btw. Though even less effort to stand it up (on Ubuntu or Debian).
via mobile

On Jan 31, 2015, at 9:14 AM, Joker Qyou<EMAIL_ADDRESS>wrote:
I was trying to set up mailsac on my own server yesterday but I found all the server links were hard-coded as mailsac.com, which was very confusing. And I figured out that the mailing functionality was normal, it looks like the repo's codes is somehow different with these used by mailsac.com. (Just guessing, because the UI differs very much)
And also I could not found license information about this repository.
Finally I've found this issue :) . May I ask when will the codes of mailsac 2 be updated to this repo? I'm very interested in this project, because other mail server products like Postfix or sendmail are usually hard to configure, but this one is really easy.
—
Reply to this email directly or view it on GitHub.

Quick reply. Well, very glad to hear that, and looking forward to mailsac v2. Thx for this easy2use mail server. :)

For sure, it's been a fun and useful project. I should also note that there will be a plugin system. That's what is taking longer. It'll make it easier to add your own custom mail hooks (a little like Haraka but less sophisticated), and UI hooks.


Section Tag Support By Container Component

The following proposed pseudo code supports the <section> tag:
<Container.sec>
  ...
</Container.sec>

I'd probably opt for something like this:
tagName: PropTypes.oneOf(['div', 'section', '...any others'])
and then in the render just have something like
cont Tag = this.props.tagName || 'div'   return (    <Tag>      {this.props.children}    </Tag>   )
But that's just my personal preference.

@byrekt , I can see the flexibility with tagName prop to support many tags. I wrote the pseudo code with the thought to follow the existing dot-notation pattern in other components, i.e. <Text.span>:
https://github.com/pricelinelabs/design-system/blob/master/src/Text.js#L66
But I am happy to explore the tagName prop support approach.
@jxnblk et al, thoughts on ☝?

The is prop in Rebass is one of the reasons styled-components added .withComponent to the v2 API. For things like this, I would rather keep a separation of layout components (divs with styles) and other semantic markup. I don't see a compelling reason why someone using the design system couldn't use Container.withComponent('section') if they wanted (which is fewer custom APIs to learn) or just use composition, e.g.:
<section id='about'>
  <Container>
    {this.props.children}
  </Container>
</section>

Cool, @jxnblk. <section> wrapper outside of <Container would solve this use case. ✌


Applying colormap on color images (like ultrasounds)

Hello
First of all, I wanna thank the Cornerstone creators and team in general. For 3 years I've been using this libraries in my work. The documentation and forums also helped me a lot.
There was only one issue I couldn't find an answer for. When applying colormaps to an image in color (mostly ultrasounds), the canvas shows a distorted image (see the attached picture).

Recently i made this update to de cornerstone.js file stored in my project assets's and fixed the problem for me.
This pull request is my first ever. I have read the contributor guidelines and hope i am not violating any rules.
Above all, i expect this to be useful.
Any feedback in my pull request will be apreciated.

@Bolkonski Is it safe to ignore other colors than the Red channel?
If the acquired image has some green or blue colored region in original series, that might be considered as black when applying LUT !
Here is another existing PR for same issue. https://github.com/cornerstonejs/cornerstone/pull/545

@Bolkonski Is it safe to ignore other colors than the Red channel? If the acquired image has some green or blue colored region in original series, that might be considered as black when applying LUT ! Here is another existing PR for same issue. #545

Absolutely true! I was so fixated with image distortion that i forgot to actually convert to grayscale. There is another commit using Luminosity Method. I read #545 and got some ideas, altho I didn't understand why relative luminance. Maybe I am missing something.


add sysinfo command

requires version check!

would it make sense to extract the sysinfo stuff into it's own module?
I think at some point we could make command extensible via plugins and then it would be good to not have them in the CrateCmd class

I agree with @mfussenegger
having a separate module would make the code much cleaner!

otherwise ack


fix link

What is the purpose of the change
fix some link errors.
Brief changelog
/docs/zh-cn/user/versions/version-270.md
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Test your code locally by running docsite start, and make sure it works as expected.
[x] Make sure no files under build directory is added.
[x] If this contribution is large, please follow the Software Donation Guide.

I just noticed that you also change the suffix from md to html. I think docsite should able to handle it. refer to https://raw.githubusercontent.com/apache/dubbo-website/master/docs/en-us/admin/serviceTest.md as example

Thanks for your contribution

@htynkn Your way may not works. I did an experiment. I change the url in two ways by chrome developer tool .
My experiment is as follows:
1、Change the value of href to "/zh-cn/docs/user/demos/routing-rule.md", then click the link "路由规则". The browser shows "Not Found" error.
2、Change the value of href to "/zh-cn/docs/user/demos/routing-rule.html", then click the link "路由规则". The browser redirect successfully.

@sofkyle thanks so much for verifying this.
You are right, it must be html.
I already fix it in master branch. This change will deploy to website by CI later


Duplicated classnames in Production mode with Next.js

Update:
After wasting 2 hours fighting this issue, I realized that the Next.js example is incorrect. I should have implemented the feature follow your documentation.
Could you confirm that this is the correct render method for MuiThemeProvider so I can send a PR and update the example?
render() {
        const context = getContext()
        if (process.browser) {
          return (
            <MuiThemeProvider theme={context.theme}>
              <App />
            </MuiThemeProvider>
          )
        }
        return (
          <JssProvider registry={context.sheetsRegistry} jss={context.jss}>
            <MuiThemeProvider
              theme={context.theme}
              sheetsManager={context.sheetsManager}
            >
              <App />
            </MuiThemeProvider>
          </JssProvider>
        )
      }

Problem description
I'm working on a SSR project that uses Next.js and Material UI. I implemented the SSR style hydration follow the example here https://github.com/zeit/next.js/blob/v3-beta/examples/with-material-ui-next/README.md. But I'm getting funny result only in production mode
Here is a gif:

After removing this line jss.options.createGenerateClassName = createGenerateClassName here , the result is a lot better:

Link to minimal working code that reproduces the issue
I try to produce it but I failed. So I raised this issue hoping that you guys can point to the right direction

Versions

Material-UI: 1.0.0-beta.2
React: 15.6.1
Browser: Chrome 59.0.3071.115

I haven't upgraded my next.js project yet to the beta. Still I would expect the examples to work as expected.
Have you refactored the withRoot HOC? JssProvider has an issue where he can't be rendered twice on the client. I have open an issue for that.

@oliviertassinari I had an opening PR here https://github.com/zeit/next.js/issues/2698 . I have no idea what''s going on, just follow the docs on working with SSR.

I have accepted your PR. Thanks!


test-cases: add manifest

@pmaria I fixed the issues, I think it is now good. Would you mind to have a short look again?

The descriptions of the test cases are still with R2RML terminology, but that's something we need to fix in the spreadsheet.


Material3 Themes UI Upgrade + Update MaterialDesignThemes.MahApps

Changelog:

This updates MaterialDesignThemes.MahApps.
This now requires Material 3 so it makes the required changes in App.xaml and MainWindows.xaml in that regard.
I've also increased slightly the height of the MainWindow.
Font has been changed from the ugly Consolas to Source Code Pro (https://github.com/adobe-fonts/source-code-pro) which is more clear-looking. Presumably the installer will need to pack this font.
It also cleans up the files a bit and adds some clarifying comments.

⚠ Note that this changes the look of the UI. I didn't change any of the colours myself, this is simply how Material 3 looks.
See below the new look. I'm not thrilled about it, but think it's an improvement over the old one.
Dark Mode:

Light Mode (does anyone still use this?):

🗒 Note: Ignore the top header, that's just from the VS XAML debugger.
Old font (Consolas):

New font (Adobe Source Code Pro):

Thanks for the effort. It's a lot for me right now to review using the Github webpage. Probably after the weekend i will checkout this PR on my machine in order to do a good review.

This is how it looks like on my machine.

Yep, that's light mode. I'd suggest locking it in Dark Mode for now as the Light Mode is neither light nor very clear (black text on dark grey background).
  <!--  Material Design  -->
  <materialDesign:BundledTheme
      BaseTheme      = "Inherit"
      PrimaryColor   = "LightBlue"
      SecondaryColor = "LightBlue"
      />

would simply need to be changed to:
  <!--  Material Design  -->
  <materialDesign:BundledTheme
      BaseTheme      = "Dark"
      PrimaryColor   = "LightBlue"
      SecondaryColor = "LightBlue"
      />

(lines 34-39 in App.xaml)
Maybe I can do a more comprehensive UI redesign at a later point which includes a proper Light Mode and that embraces WinUI3 and Fluent design.

My current version looks like:

Which I like.
I'm happy to accept a PR that is updating the UI, but not if the light mode has black text like it has right now. I'm not using the black/dark mode and I don't like forcing others to do so

In your PR, can you remove the this. keyword?

In your PR, can you remove the this. keyword?

✅ Done.

My current version looks like:

Which I like.
I'm happy to accept a PR that is updating the UI, but not if the light mode has black text like it has right now. I'm not using the black/dark mode and I don't like forcing others to do so

Is it possible for you to make the text white in light mode (as it was). Then can accept your PR and merge this into main.
I really like you worked the UI as it is not my 'thing'.
Also the text in the help menu and the hamberger menu have black text.

Sure, I'll look into it.

Sure, I'll look into getting the UI right, including light mode. Apologies, I only saw your comment from 3 days ago now. GitHub notifications only showed me the comment about "this" for some reason 😅

Recommending this PR is superseded by PR #184


Check the object storage endpoint to determine which signature version to use

S3 and Minio should use the S3 V4 signature version, and Google Cloud Storage in compatibility mode should use the V2 version.
Ref https://github.com/deis/builder/issues/222

I believe it was https://github.com/deis/slugbuilder/issues/33, right @smothiki?

Thanks


Update RepositoryMap for latest drivers to date

Update RepositoryMap with all libraries to the latest versions found today.
Some of hashtypes were changed into md5 because they are shown with md5 values in their download directories

Updated to latest versions of everything today so no longer required, thanks though


[jsinterp] Actual parsing

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[ ] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[x] New feature

Description of your pull request and other information
I've started to implement an actual JavaScript syntax parser.

A notice: OrderedDict are not available in Python 2.6. There was a proposal to drop 2.6 but no consensus yet (#5697)

For some reason code this had been missed by code inspector of the IDE I'm working with. I'll try to come up a workaround. Thanks.

I've just realise my original idea, that _next_statement method would do the lexical analysis and interpret_statement the parsing is fraud. To yield a statement parsing has to had happened, since Statement is one of the symbols (along with FunctionDeclaration) replacing SourceElement in the syntactic grammar.

Review request for: test_jsinterp_parser.py

https://github.com/rg3/youtube-dl/pull/11272/commits/9b5e55a45afea978fc963bc50bb074bddd258927 looks a good way. https://pypi.python.org/pypi/unittest-data-provider may be helpful for generating test cases automatically, or you may implement your own test case generator like what test_download.py does.

If you're looking for some dirty Javascripts, here's the latest site that may benefit from a real JS interpreter, Bilibili: http://static.hdslb.com/player/js/bilibiliPlayer.min.js?v=3db87237
Ref: #11077

At the moment I'm looking for very small scripts that, uses specific JS features. Like the ones in my comment,of which review I've called out.

I guess Mozilla's test suite is enough. Or V8's test suite, ChakraCore's test suite, etc. Spidermonkey does not provide a standalone repository, and V8 requires Google's mysterious build system, so maybe ChakraCore is a choice.

I'll check them out hopefully one of them be a suit~e~able.

Can we talk about some kind of milestone and/or review criteria?
I'm thinking a fully functional parser and passing current interpreter tests.

The first milestone can be when most ES5 syntaxes are parsed

Gotcha, tests included I reckon, but I'll postpone suite integration.

I'm done wit the parser. Right now I'm adding ASTs to tests, and fixing bugs.

Parser is done. Beside some features (automatic semicolon insertion, and in for initialization), I should have marked most of those. I've also marked some parenthesis checks I've missed, but those are less bold.
I've really hoped I can also tackle some operator issues (prefix, postfix, delete, void, typeof, in, instanceof). These are going to need some attention both in parsing and interpreting.
At the current state of the test suite that would start making things messy. I might do it anyway, but sorting that out is more and more pressing.

Hmm, what's "automatic semicolon insertion"?

A feature in JS since a long time. Some of the semicolons amended by the interpreter automagicly to statements. I've marked some examples in tests.
I've run the tests in Node.js or V8 (whatever you call it) and Rhino first to see if they are actually a JS script, and got no trouble with omitted semicolons, that's how those got in the first place.

Thanks for the link. I guess that feature is necessary as lots of JS compressors remove tokens as much as possible.

True that. Yet that's entirely a parser feature, therefore it can be added later and there's also a lot to do on the interpreter (function call, property handle, built-in methods).

JSInterpreter extract_function is kept as a fallback, used solely by call_function method.
Usage of this should be discouraged, since calling function declared outside of function body will fail.

Hey, I noticed this project and I think it's interesting. I wrote Js2Py - something very similar to the interpreter your are developing here - but since it works by translating Js to Python it is bound by the limits of Python syntax (like maximum number of arguments of a function is 256 or no continue iside finally statement) and may not be suitable due to security concerns.
However, I also wrote pyjsparser which is a JS parser based on esprima.js and it supports whole ECMA 5 and parts of 6. Esprima is hevily tested so pyjsparser is virtually flawless. I was wondering why don't you adapt the pyjparser in your project?
Also, about 1 month ago I started implementing a proper interpreter with JsCode -> Bytecode conversion. But I temporarily abandoned the project after implementing the interesting parts ;) I don't think Js2Py will be useful here as we took a completely different approach.
Regarding built-in objects (they are certainly not a fun thing to implement :) )  - Js2Py has them all implemented so if you want I think it would be possible to use this implementation here.

That sound like a life saver, I'm going to definitely check it out.
I can't make any meaningful comment till then, but I can tell that I don't want to generate bytecode and I'm prepared to even sacrifice a lot of performance just to not do that.
I've used narcissus and rhino for inspiration and guidance when I had difficulty with the specs.
And thanks, I'm hoping it will be helpful.

I've created a tag here, since interpreter could be even bigger.

Would refactoring parser into separate module help with size issue?

Hope refactoring parser a tiny bit helps with size issue.

I don't think there are any more strings having ambiguity issues, since I remember getting lazy with those two.

After some cool-off time things start to catch up on the jsbuilt-ins branch. Not quite ready to merge, but I'd like to make a friendly reminder that, even if a bit slower and not pushing on this branch, I'm still working on this.

Sorry but I have neither time nor knowledge to review this. I'd like to merge it as-is. Could you move new codes to another module? (e.g., jsinterp2)

Hello @sulyi, are you still working on it?

Would like to see this. It is related to my incomplete PR https://github.com/rg3/youtube-dl/pull/14943 . Also I created this number parser according to the ECMA specifications:
from __future__ import print_function
import math
import re

regex = re.compile(r'''(?:\s+)? # StrNumericLiteral.StrWhiteSpace (optional)
            ( # StringNumericLitral.StrDecimalLiteral
                (?P<inf_sign>[\+\-])? # optional sign
                (?P<inf>Infinity)|
                [\+\-]?(?P<nan>NaN)|  # not documented, but Node returns NaN
                [\+\-]?(?:  # DecimalDigits . DecimalDigits(opt) ExponentPart(opt)
                    (?:\d+)? # DecimalDigits
                    (?:\.)
                    (?:\d+)? # DecimalDigits
                    (?:[eE] # ExponentPart.ExponentIndicator
                        [\+\=]?  # optional sign
                        (?:\d+)
                    )?
                )|
                0(?P<binary>[bB])(?P<binary_number>[01]+)|
                0(?P<octal>[oO])(?P<octal_number>[01234567]+)|
                0(?P<hex>[xX])(?P<hex_number>[0-9a-fA-F]+)
            )(?:\s+)?$''', re.X)

def getnan():
    try:
        return math.nan
    except AttributeError:
        pass
    return float('nan')

def getinf(mult=1):
    try:
        ret = math.inf
    except AttributeError:
        ret = float('inf')
    return mult * ret

def can_be_int(inp, out):
    return str(out)[-2:] == '.0' and ('.0' not in inp and not inp.endswith('.'))

def conditional_int(inp):
    # Values with leading zeros like 01.0 and 01. should fail
    if len(inp) > 1 and inp[0] == '0':
        raise SyntaxError('unexpected number; given "{}"'.format(inp))
    out = float(inp)
    return int(str(out)[:-2], 10) if can_be_int(inp, out) else out

def parse_numeric(x):
    m = re.match(regex, x)
    if not m:
        raise SyntaxError('invalid nor unexpected token; given "{}"'.format(x))

    ret = m.group(0).strip()
    groups = m.groupdict()

    if groups['inf']:
        sign = -1 if groups['inf_sign'] == '-' else 1
        ret = getinf(sign)
    elif groups['nan']:
        ret = getnan()
    else:
        base = key = None
        if groups['binary']:
            base = 2
            key = 'binary_number'
        elif groups['octal']:
            base = 8
            key = 'octal_number'
        elif groups['hex']:
            base = 16
            key = 'hex_number'
        if key and base:
            ret = int(groups[key], base)
        else:
            try:
                ret = conditional_int(ret)
            except ValueError as e:
                raise SyntaxError('invalid or unexpected token: given "{}"'.format(x))
    return ret

Passes all these, exactly the same as how Chrome parses:
parse_numeric('.1')
parse_numeric('1.')
parse_numeric('Infinity')
parse_numeric('-Infinity')
parse_numeric('+Infinity')
parse_numeric('NaN')
parse_numeric('-NaN')
parse_numeric('+NaN')
try:
    parse_numeric('01.0')
except SyntaxError as e:
    print('01.0 -> {}'.format(e))
try:
    parse_numeric('01.')
except SyntaxError as e:
    print('01. -> {}'.format(e))
parse_numeric('1.0')
parse_numeric('1.1')
parse_numeric('1.e5')
parse_numeric('1.E5')
parse_numeric('1.1e5')
parse_numeric('1.1E6')
parse_numeric('-1.1E6')
parse_numeric('+1.1')
parse_numeric('0b101')
parse_numeric('0B101')
parse_numeric('0o755')
parse_numeric('0O755')
parse_numeric('0xaf')
parse_numeric('0XDEADBEEF9')

Been a while. I'm not yet up to speed with my previous work, but managed to fix some issues with "jsbuilt-ins" and merge that branch which has some of the infrastructure ready, but most of it is still not implemented. And this needs some work beyond that before it's able to replace the functionality of the current solution, e.g. interpretation of member expression. As this test result shows, I've ran it with changing this line to:
 from ..jsinterp2 import JSInterpreter

I've totally missed @yan12125's this reply. It's a shame, really if I'd known... anyway @Kcchouette now I am intend to work on it again, but I wasn't till now. I've even considered closing it.

Note: I've added a new test, for slicing strings.

Interesting: in 50/72 rule LN is included!

Changing logging level here you can log skipped assertions.

This is of course, very neat. But a lot of Chrome's (and maybe others) standard library for many things are implemented in JavaScript. Instead of making the built-ins (like String.prototype.match) in Python, why not write them in JavaScript (where possible)?

Main thing is to get the basics of the interpreter in, which includes the built-in types, and then the JavaScript portions can be written very similarly to how polyfills are written today. So you would not need to implement Array.isArray() in Python if you have the === operator working for comparing function references and .constructor property working on all objects. Then code Array.isArray = function (x) { return x.constructor === Array }; and make this load at runtime before anything else.
I can take a look later since this does interest me. Mainly this was needed for me to get past CloudFlare anti-DDoS without needing cookies.

Well, I've already implemented operator === and most constructors I believe, but neither have been tested properly.
Also spec of isArray states:

If Type(arg) is not Object, return false.
If the value of the [[Class]] internal property of arg is "Array", then return true.
Return false.

I'm not sure when 1. would execute or whether your solution takes care of it.
My solution for this particular function would look like this:
from .internals import jstype, object_type

def _is_array(arg):
   if jstype(arg) is not object_type:
      return False
   if arg.jsclass == 'Array':
      return True
  return False

I'm not sticking to it or claim that it's elegant, but this is how I'm able to solve the task at hand.
I have way less xp programming in js than in py. So, if you could tell me what needs to be get done for this to work I can probably take care of it, but to actually implement it that would be much harder to do it like this on my own.

I've added feature to lexer (tstream.TokenStream) ability to handle line terminators. This is the first step in implementing correct line reporting.
This is also useful to have in my other plan to change the test suite using json files instead of py to generate test cases. My reasoning behind it is if jsparser.Parser would support converting  AST to estree or some pretty similar format, it would be possible to easily compare it against the output of acorn or some other parser.


typescript: Update typescript - abandoned

This PR contains the following updates:

Package
Type
Update
Change

@types/node (source)
devDependencies
patch
20.14.12 -> 20.14.13

@types/node (source)
dependencies
patch
20.14.12 -> 20.14.13

chai (source)
devDependencies
minor
4.4.1 -> 4.5.0

gdata-vaas
dependencies
patch
7.1.8 -> 7.1.9

:warning: Warning
Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

chaijs/chai (chai)
v4.5.0
Compare Source

Update type detect (#1631)  1a36d35

What's Changed

Update type detect by @koddsson in https://github.com/chaijs/chai/pull/1631

Full Changelog: https://github.com/chaijs/chai/compare/v4.4.1...v4.5.0

GDATASoftwareAG/vaas (gdata-vaas)
v7.1.9
Compare Source

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Autoclosing Skipped
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.


Error - I think dealing with models that have instruct pix2pix

@s1dlx   Was attempting to do a re-basin merge with the following model: photosomnia_v16.instruct-pix2pix.safetensors The only thing different with this model is that it has pix2pix in the architecture, so I was thinking that might be the cause of the issue. I was doing one of my follow up test. I have to check inpainting too.
CLI prompt:
H:\Users\adamf\AI_Progs\sd-meh-merge\meh>merge_models.py -a H:\Users\adamf\AI_Progs\AI_Models\test\00-regit-pwddxWDP1x5EV5SMA5URPM440EMxdream6rellyrevebmev2_dblback2_20prune.safetensors -b H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors -m weighted_sum -p 32 -o H:\Users\adamf\AI_Progs\AI_Models\test\00-regit-pwddxWDP1x5EV5SMA5URPM440EMxdream6rellyrevebmev2_dblback2pix_20prune -f safetensors -ba 0.5 -bb 0.5 -pr -rb -rbi 20
I get the following error:
before loading models: 0.000
loading: H:\Users\adamf\AI_Progs\AI_Models\test\00-regit-pwddxWDP1x5EV5SMA5URPM440EMxdream6rellyrevebmev2_dblback2_20prune.safetensors
loading: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors
models loaded: 0.000
permuting
0 iteration start: 0.000
weights & bases, before simple merge: 0.000
stage 1: 100%|████████████████████████████████████████████████████████████████████▉| 1130/1131 [00:42<00:00, 26.46it/s]
Traceback (most recent call last):
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\merge_models.py", line 151, in
main()
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1157, in call
return self.main(*args, **kwargs)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1078, in main
rv = self.invoke(ctx)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\merge_models.py", line 132, in main
merged = merge_models(
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 146, in merge_models
merged = rebasin_merge(
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 286, in rebasin_merge
thetas["model_a"] = simple_merge(
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 244, in simple_merge
res.result()
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\concurrent\futures_base.py", line 451, in result
return self.__get_result()
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\concurrent\futures_base.py", line 403, in __get_result
raise self._exception
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\concurrent\futures\thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 342, in simple_merge_key
with merge_key_context(key, thetas, *args, **kwargs) as result:
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\contextlib.py", line 135, in enter
return next(self.gen)
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 428, in merge_key_context
result = merge_key(*args, **kwargs)
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 403, in merge_key
merged_key = merge_method(**merge_args).to(storage_device)
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge_methods.py", line 27, in weighted_sum
return (1 - alpha) * a + alpha * b
RuntimeError: The size of tensor a (4) must match the size of tensor b (8) at non-singleton dimension 1

@s1dlx I tried running it on the default merger via Vlad's and got the following error on his:
RuntimeError: When merging instruct-pix2pix model with a normal one, A must be the instruct-pix2pix model.
I tried swapping A and B on yours but got the same error as in the previous message. Swapping them did work on vlad's so there might be some code in there that you can look at to see how it deals with the architecture for pix2pix at least for the normal merge.
Full read out:
23:51:36-222934 INFO     Model merge loading secondary model:
H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors
Loading weights: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors ━ 0… -…
GB
23:51:37-917656 INFO     Model merge loading primary model:
H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\HD-22-fp16-fixclip-noema.safetensors
Loading weights: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\HD-22-fp16-fixclip-noema.safetensors ━━━━ 0.0… -:--…
GB
23:51:41-717749 INFO     Model merge: running
39%|███████████████████████████████                                                | 450/1143 [00:09<00:14, 47.69it/s]
23:51:51-155872 ERROR    model merge: RuntimeError
╭───────────────────────────────────────── Traceback (most recent call last) ──────────────────────────────────────────╮
│ H:\Users\adamf\AI_Progs\VladDiffusion\automatic\modules\ui_models.py:100 in modelmerger                              │
│                                                                                │
│    99 │   │   │   │   │   try:                                                                                │
│ ❱ 100 │   │   │   │   │   │   results = extras.run_modelmerger(*args)                                                │
│   101 │   │   │   │   │   except Exception as e:                                                                     │
│                                                                                │
│ H:\Users\adamf\AI_Progs\VladDiffusion\automatic\modules\extras.py:154 in run_modelmerger                             │
│                                                                                │
│   153 │   │   │   │   if a.shape[1] == 4 and b.shape[1] == 8:                                                        │
│ ❱ 154 │   │   │   │   │   raise RuntimeError("When merging instruct-pix2pix model with a norma                       │
│   155 │   │   │   │   if a.shape[1] == 8 and b.shape[1] == 4:#If we have an Instruct-Pix2Pix m                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
RuntimeError: When merging instruct-pix2pix model with a normal one, A must be the instruct-pix2pix model.
23:51:58-233415 INFO     Available models: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion 117

That extra layer is trained along with the rest of the weights. If this is anything like inpainting, just adding the layer to a normal model works, but causes a drop in quality. I am really curios if there is a way when merging to modify the weights to the extra layer relative to model that's being merged with inapinting/pix2pix model to improve quality. A question I can't answer: Can git rebasin be repurposed for this use case where the normal sd weights are merged normally, but the entire inpainting/pix2pix model is permutated towards the normal model separately and then add at the end just the permutated layer to the merge.

just to clarify: using pix2pix as model a doesn't work on both vlad and meh?

It works in vlad's only as model a
It doesn't work in meh as a or b.

Sorry non-intended mouse click closed the issue for a sec. lol.

That extra layer is trained along with the rest of the weights. If this is anything like inpainting, just adding the layer to a normal model works, but causes a drop in quality. I am really curios if there is a way when merging to modify the weights to the extra layer relative to model that's being merged with inapinting/pix2pix model to improve quality. A question I can't answer: Can git rebasin be repurposed for this use case where the normal sd weights are merged normally, but the entire inpainting/pix2pix model is permutated towards the normal model separately and then add at the end just the permutated layer to the merge.
Edit: Git rebasin can presume the normal sd model has the extra layer, but with weights zero.

It looks from what I'm reading that unless they fine tuned their pix2pix model for extra functionality the quality loss would be negligible and it would only ever be as good as the pix2pix base model can generate. https://huggingface.co/blog/instruction-tuning-sd From that an a few other small articles that weren't a ton of help it seems like pix2pix is it's own complete model that can be added in or run separately. Correct me if I'm reading into this wrong though.
So it probably could just be pruned out and added in before saving. I'm not sure how a merge should handle 2 models with pix2pix though and I have yet to see if that generates any other errors. Similarly I'm not sure how to identify if a pix2pix model has been fine tuned.

Looked into it just to be sure. It's the same story as an inpainting model. You take a model and train all of it with an extra layer on top. It should work just by appending the layer to a normal model, but there still should be some quality loss simply because the extra layer is slightly out of sync with the normal weights. Nonetheless, I'll try to do a PR soon for meh for pix2pix(and inpainting if it doesn't already work) and somebody can test how well the resulting merge works.

@WhiteWipe I can retest it if you can fix it those portions..

Part 1: (Normal weighted Sum)
Run as:
merge_models.py -a H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors -b H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors -m weighted_sum -p 16 -o H:\Users\adamf\AI_Progs\AI_Models\test\p2pfp16test -f safetensors -ba 0.5 -bb 0.5 -pr
This outputs now too. I'll try to test the two files tomorrow if I can.
Part 2: (re-basin error)
Run as:
merge_models.py -a H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors -b H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors -m weighted_sum -p 16 -o H:\Users\adamf\AI_Progs\AI_Models\test\p2pfp16test -f safetensors -ba 0.5 -bb 0.5 -pr -rb -rbi 50
H:\Users\adamf\AI_Progs\sd-meh-merge\meh>merge_models.py -a H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors -b H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors -m weighted_sum -p 16 -o H:\Users\adamf\AI_Progs\AI_Models\test\p2pfp16test -f safetensors -ba 0.5 -bb 0.5 -pr -rb -rbi 50
INFO: Assembling alpha w&b
INFO: base_alpha: 0.5
INFO: alpha weights: [0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5]
INFO: Loading: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors
INFO: Loading: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors
INFO: start merging with weighted_sum method
INFO: Init rebasin iterations
INFO: Rebasin iteration 0
stage 1:  37%|█████████████████████████▊                                           | 423/1131 [00:00<00:01, 687.63it/s]model.diffusion_model.input_blocks.0.0.weight torch.Size([320, 8, 3, 3]) torch.Size([320, 4, 3, 3])
model.diffusion_model.input_blocks.1.1.proj_in.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.input_blocks.1.1.proj_out.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.input_blocks.1.1.transformer_blocks.0.attn2.to_k.weight torch.Size([320, 768]) torch.Size([320, 1024])
model.diffusion_model.input_blocks.1.1.transformer_blocks.0.attn2.to_v.weight torch.Size([320, 768]) torch.Size([320, 1024])
model.diffusion_model.input_blocks.2.1.proj_in.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.input_blocks.2.1.proj_out.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.input_blocks.2.1.transformer_blocks.0.attn2.to_k.weight torch.Size([320, 768]) torch.Size([320, 1024])
model.diffusion_model.input_blocks.2.1.transformer_blocks.0.attn2.to_v.weight torch.Size([320, 768]) torch.Size([320, 1024])
stage 1:  47%|████████████████████████████████▍                                    | 532/1131 [00:01<00:01, 428.63it/s]model.diffusion_model.input_blocks.4.1.proj_in.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.input_blocks.4.1.proj_out.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.input_blocks.4.1.transformer_blocks.0.attn2.to_k.weight torch.Size([640, 768]) torch.Size([640, 1024])
model.diffusion_model.input_blocks.4.1.transformer_blocks.0.attn2.to_v.weight torch.Size([640, 768]) torch.Size([640, 1024])
model.diffusion_model.input_blocks.5.1.proj_in.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.input_blocks.5.1.proj_out.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.input_blocks.5.1.transformer_blocks.0.attn2.to_k.weight torch.Size([640, 768]) torch.Size([640, 1024])
stage 1:  53%|████████████████████████████████████▋                                | 602/1131 [00:01<00:01, 420.38it/s]model.diffusion_model.input_blocks.5.1.transformer_blocks.0.attn2.to_v.weight torch.Size([640, 768]) torch.Size([640, 1024])
model.diffusion_model.input_blocks.7.1.proj_in.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.input_blocks.7.1.proj_out.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.input_blocks.7.1.transformer_blocks.0.attn2.to_k.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
model.diffusion_model.input_blocks.7.1.transformer_blocks.0.attn2.to_v.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
stage 1:  58%|████████████████████████████████████████▎                            | 660/1131 [00:01<00:01, 290.94it/s]model.diffusion_model.input_blocks.8.1.proj_in.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.input_blocks.8.1.proj_out.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.input_blocks.8.1.transformer_blocks.0.attn2.to_k.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
model.diffusion_model.input_blocks.8.1.transformer_blocks.0.attn2.to_v.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
stage 1:  62%|██████████████████████████████████████████▊                          | 702/1131 [00:02<00:02, 192.93it/s]model.diffusion_model.middle_block.1.proj_in.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.middle_block.1.proj_out.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.middle_block.1.transformer_blocks.0.attn2.to_k.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
model.diffusion_model.middle_block.1.transformer_blocks.0.attn2.to_v.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
stage 1:  69%|███████████████████████████████████████████████▉                      | 775/1131 [00:03<00:03, 99.98it/s]model.diffusion_model.output_blocks.10.1.proj_in.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.output_blocks.10.1.proj_out.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.output_blocks.10.1.transformer_blocks.0.attn2.to_k.weight torch.Size([320, 768]) torch.Size([320, 1024])
model.diffusion_model.output_blocks.10.1.transformer_blocks.0.attn2.to_v.weight torch.Size([320, 768]) torch.Size([320, 1024])
model.diffusion_model.output_blocks.11.1.proj_in.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.output_blocks.11.1.proj_out.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.output_blocks.11.1.transformer_blocks.0.attn2.to_k.weight torch.Size([320, 768]) torch.Size([320, 1024])
model.diffusion_model.output_blocks.11.1.transformer_blocks.0.attn2.to_v.weight torch.Size([320, 768]) torch.Size([320, 1024])
stage 1:  75%|███████████████████████████████████████████████████▌                 | 845/1131 [00:03<00:01, 157.70it/s]model.diffusion_model.output_blocks.3.1.proj_in.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.output_blocks.3.1.proj_out.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
stage 1:  77%|█████████████████████████████████████████████████████▍               | 875/1131 [00:04<00:02, 103.23it/s]model.diffusion_model.output_blocks.3.1.transformer_blocks.0.attn2.to_k.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
model.diffusion_model.output_blocks.3.1.transformer_blocks.0.attn2.to_v.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
stage 1:  79%|██████████████████████████████████████████████████████▊              | 898/1131 [00:04<00:02, 105.05it/s]model.diffusion_model.output_blocks.4.1.proj_in.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.output_blocks.4.1.proj_out.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
stage 1:  81%|████████████████████████████████████████████████████████▊             | 917/1131 [00:04<00:02, 91.55it/s]model.diffusion_model.output_blocks.4.1.transformer_blocks.0.attn2.to_k.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
model.diffusion_model.output_blocks.4.1.transformer_blocks.0.attn2.to_v.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
stage 1:  84%|██████████████████████████████████████████████████████████▌           | 946/1131 [00:05<00:02, 81.16it/s]model.diffusion_model.output_blocks.5.1.proj_in.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.output_blocks.5.1.proj_out.weight torch.Size([1280, 1280, 1, 1]) torch.Size([1280, 1280])
model.diffusion_model.output_blocks.5.1.transformer_blocks.0.attn2.to_k.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
model.diffusion_model.output_blocks.5.1.transformer_blocks.0.attn2.to_v.weight torch.Size([1280, 768]) torch.Size([1280, 1024])
stage 1:  87%|█████████████████████████████████████████████████████████████         | 986/1131 [00:05<00:01, 88.83it/s]model.diffusion_model.output_blocks.6.1.proj_in.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.output_blocks.6.1.proj_out.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.output_blocks.6.1.transformer_blocks.0.attn2.to_k.weight torch.Size([640, 768]) torch.Size([640, 1024])
model.diffusion_model.output_blocks.6.1.transformer_blocks.0.attn2.to_v.weight torch.Size([640, 768]) torch.Size([640, 1024])
stage 1:  90%|█████████████████████████████████████████████████████████████▏      | 1017/1131 [00:05<00:00, 129.52it/s]model.diffusion_model.output_blocks.7.1.proj_in.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.output_blocks.7.1.proj_out.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.output_blocks.7.1.transformer_blocks.0.attn2.to_k.weight torch.Size([640, 768]) torch.Size([640, 1024])
model.diffusion_model.output_blocks.7.1.transformer_blocks.0.attn2.to_v.weight torch.Size([640, 768]) torch.Size([640, 1024])
stage 1:  93%|███████████████████████████████████████████████████████████████▍    | 1055/1131 [00:05<00:00, 174.16it/s]model.diffusion_model.output_blocks.8.1.proj_in.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.output_blocks.8.1.proj_out.weight torch.Size([640, 640, 1, 1]) torch.Size([640, 640])
model.diffusion_model.output_blocks.8.1.transformer_blocks.0.attn2.to_k.weight torch.Size([640, 768]) torch.Size([640, 1024])
model.diffusion_model.output_blocks.8.1.transformer_blocks.0.attn2.to_v.weight torch.Size([640, 768]) torch.Size([640, 1024])
stage 1:  96%|█████████████████████████████████████████████████████████████████▍  | 1089/1131 [00:05<00:00, 208.53it/s]model.diffusion_model.output_blocks.9.1.proj_in.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.output_blocks.9.1.proj_out.weight torch.Size([320, 320, 1, 1]) torch.Size([320, 320])
model.diffusion_model.output_blocks.9.1.transformer_blocks.0.attn2.to_k.weight torch.Size([320, 768]) torch.Size([320, 1024])
model.diffusion_model.output_blocks.9.1.transformer_blocks.0.attn2.to_v.weight torch.Size([320, 768]) torch.Size([320, 1024])
stage 1: 100%|████████████████████████████████████████████████████████████████████| 1131/1131 [00:05<00:00, 190.52it/s]
stage 2: 100%|██████████████████████████████████████████████████████████████████| 1215/1215 [00:00<00:00, 27613.69it/s]
Traceback (most recent call last):
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\merge_models.py", line 181, in
main()
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1157, in call
return self.main(*args, **kwargs)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1078, in main
rv = self.invoke(ctx)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\merge_models.py", line 162, in main
merged = merge_models(
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 149, in merge_models
merged = rebasin_merge(
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 319, in rebasin_merge
thetas["model_a"] = apply_permutation(perm_spec, perm_1, thetas["model_a"])
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\rebasin.py", line 2197, in apply_permutation
return {k: get_permuted_param(ps, perm, k, params) for k in params.keys()}
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\rebasin.py", line 2197, in
return {k: get_permuted_param(ps, perm, k, params) for k in params.keys()}
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\rebasin.py", line 2183, in get_permuted_param
for axis, p in enumerate(ps.axes_to_perm[k]):
KeyError: 'cond_stage_model.model.ln_final.bias'

I did try running the model that I made last night for pix2pix and got an error in vlad's:
07:39:33-463643 ERROR    Error in onchange callback: sd_model_checkpoint 00-p2pfp16test.safetensors Error(s) in loading
state_dict for UNetModel:
size mismatch for input_blocks.0.0.weight: copying a param with shape torch.Size([320,
8, 3, 3]) from checkpoint, the shape in current model is torch.Size([320, 4, 3, 3]).
I'll give it a try in a little bit. I have a few maintenance things to do.

(re-basin retest) ok different looking output prior to the error this time. Looks like the same error though.
Ran as:
merge_models.py -a H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors -b H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors -m weighted_sum -p 16 -o H:\Users\adamf\AI_Progs\AI_Models\test\p2pfp16test -f safetensors -ba 0.5 -bb 0.5 -pr -rb -rbi 10
Pre error output:
H:\Users\adamf\AI_Progs\sd-meh-merge\meh>merge_models.py -a H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors -b H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors -m weighted_sum -p 16 -o H:\Users\adamf\AI_Progs\AI_Models\test\p2pfp16test -f safetensors -ba 0.5 -bb 0.5 -pr -rb -rbi 10
INFO: Assembling alpha w&b
INFO: base_alpha: 0.5
INFO: alpha weights: [0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5]
INFO: Loading: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors
INFO: Loading: H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors
INFO: start merging with weighted_sum method
INFO: Init rebasin iterations
INFO: Rebasin iteration 0
stage 1: 100%|█████████████████████████████████████████████████████████████████████| 1131/1131 [01:03<00:00, 17.95it/s]
stage 2: 100%|██████████████████████████████████████████████████████████████████| 1215/1215 [00:00<00:00, 26999.81it/s]
Traceback (most recent call last):
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\merge_models.py", line 181, in
main()
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1157, in call
return self.main(*args, **kwargs)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1078, in main
rv = self.invoke(ctx)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "C:\Users\adamf\AppData\Local\Programs\Python\Python310\lib\site-packages\click\core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\merge_models.py", line 162, in main
merged = merge_models(
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 149, in merge_models
merged = rebasin_merge(
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\merge.py", line 319, in rebasin_merge
thetas["model_a"] = apply_permutation(perm_spec, perm_1, thetas["model_a"])
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\rebasin.py", line 2197, in apply_permutation
return {k: get_permuted_param(ps, perm, k, params) for k in params.keys()}
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\rebasin.py", line 2197, in
return {k: get_permuted_param(ps, perm, k, params) for k in params.keys()}
File "H:\Users\adamf\AI_Progs\sd-meh-merge\meh\sd_meh\rebasin.py", line 2183, in get_permuted_param
for axis, p in enumerate(ps.axes_to_perm[k]):
KeyError: 'cond_stage_model.model.ln_final.bias'

Mmm this is different

@DirtyHamster I'm not able to reproduce the error...
are you sure you are using the latest sd-meh? That would be 0.9.4

The Vlads error was from doing the merge the night before if that's what your referring to? That would have been an earlier version.
The second re-basin error was with the newer version of meh. I put it in post maintenance.  I did a git clone of what you have up after blowing away the old folders so it really shouldn't have a choice. Launching it was from inside that new directory.
The only possible for an alt version responding that I can think of would be via pythons path but I didn't load python before calling the file name in the directory. Any thought on that?

Did clean installs for python and the few other python apps that I use the most. Cleaned up some system paths that I had missed the first time I did this earlier in the month. I still get the same error.
The most common line in the error points at:
Python310\lib\site-packages\click\core.py
At the moment I'm thinking that something has to be wrong with how the click module installed for me or similar that's as far as I got so far. It might be something as simple as it missing a module in it's "requirements.txt" that you might have picked up else where. It could also be a difference in versions between us too if they've depreciated or changed any functions it might also cause issues. Which could be the reason it's working for you and not me. It's hard for me to say I'm by far not an expert with python and I'd even say I'm fairly clumsy with it still lol..
The easiest trouble shoot we could start with would be version of click:
The click version I have is 8.1.6
What version do you have?
I noticed looking around in core.py at the error lines mentioned. 1434, 1157, 1078, 783 that there were some coders notes mentions changes from how version 8+ worked though they didn't point to the exact lines listed above. Being that they were both above and below some of the lines it has me a little suspect that it could be a potential cause.

@DirtyHamster the last test I did was with click 8.1.3

Ok that probably wouldn't be it then post version 8.1.4 they didn't even bother writing a changelog for them. Back to being stumped.
Was there any difference in the command line prompt when it was working for you? Just to rule something else out that is easy. Perhaps the models that I selected? Are you using different ones?
merge_models.py -a H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\photosomnia_v16.instruct-pix2pix.safetensors -b H:\Users\adamf\AI_Progs\AI_Models\Stable_Diffusion\wd-ink-fp16.safetensors -m weighted_sum -p 16 -o H:\Users\adamf\AI_Progs\AI_Models\test\p2pfp16test -f safetensors -ba 0.5 -bb 0.5 -pr -rb -rbi 10

I'm running a very simple command
python3 merge_models.py \
    -a ~/sd_models/img2imgPix2pix_v10Pruned.safetensors \
    -b ~/sd_models/lyriel_v15.safetensors \
    -m weighted_sum -ba 0.5 -rb -rbi 2

it's possibly due to the actual models. Where can I download yours?

I suppose I could try again without the extra two args in the command line -pr & -bb though that doesn't seem like a major difference. It's nice to know I could drop the -bb weight too. I'll try this a bit later as well as try some additional models as soon as I spot some with p2p in them.
The two I was using are:
https://civitai.com/models/18637?modelVersionId=29374 (this one has the pix2pix)
https://huggingface.co/waifu-diffusion/wd-1-5-beta3/blob/main/wd-ink-fp16.safetensors (this was a fairly random pick)


feat: Put the logo instead of website name

Summary

Previously we have "DevopsCloudJunction" at the top right. Now, i replaced with logo.

Basic example
Include a basic example, screenshots, or links.
Motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
Checks

[ ] Read Create a Pull Request
[ ] Supports all screen sizes (if relevant)
[ ] Supports both light and dark mode (if relevant)
[ ] Passes npm run test

Need to adjust the logo background when it is changed to dark mode.


Add parts for developing antennal disc [sf#3]

Reported by djs93 on 2013-05-09 10:51 UTC
We have parts for the developing eye disc, but lack them for the antennal disc. FBrf0044923, Fig 6 has a fate-map for the eye-antennal disc.
(this is a very long-standing request from the old tracker and so deserves a high priority)

Updated by mmc46 on 2014-02-19 18:27 UTC

status: open --> pending

Updated by mmc46 on 2014-02-25 20:23 UTC

status: pending --> closed


rp-rewards-mainnet-27.json is not generated yet

Can you please take a look?  This file is somehow missing.
https://storage.googleapis.com/lgtm-info-dev-preview/rewards-trees/mainnet/rp-rewards-mainnet-27.json is 404

Seems this is happening again, but for rp-rewards-mainnet-29.json.


Kubectl delete command's wrong synopsis

In kubectl_delete.md, It says "if both a filename and command line arguments are passed, the command line arguments are used and the filename is ignored."
but when I test,
$kubectl delete pods asdf -f pod.yaml
error: when paths, URLs, or stdin is provided as input, you may not specify a resource by arguments as well
So I think the description "if both a filename and command line arguments are passed, the command line arguments are used and the filename is ignored." is not right, we should correct it

@feihujiang do you want to submit a PR with the change ?

@ArtfulCoder Yes, I have submitted a PR with the change.

@bgrant0607  Could you please give this issue milestone?


Error-trapping of multivariate expressions defeats some valid models

Reproducible example of a Markov chain where the state of the chain is a stochastic index.  The expression i-1 in a non-scalar distribution argument triggers error-trapping where it is not necessary.
library(nimble)

mc <- nimbleCode({
   x[1] <- 1
   for(i in 2:10) {
       x[2] ~ dcat(transition_probs[x[i-1], 1:2])
   }
}
)

transition_probs <- matrix(c(.1, .9, .4, .6), nrow = 2)

m <- nimbleModel(
    mc,
    data = list(transition_probs = transition_probs)
)

closed by PR #685


⚠ Bofrost.nl has degraded performance

In dd2ba21, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1714 ms

Resolved: Bofrost.nl performance has improved in 6385632.