Rewrite GitHub commit status

This decorates response errors with the response and response buffer, to make it easy for a service to parse an error response when it needs to. Since this is needed so rarely, I didn't put the error-parsing functionality in BaseJsonService, to save resources in the vast majority of cases.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 32ca6b000725f57a1f93d75b1f051c3f9513e639


Aclfix

Cache the plugin iterator so that it's not recreated after the filters have been added (and causing a bug where the Acl is not functioning).

Closing this since we determined this solution isn't workable.


net/http: Setting r.Close = true in a handler does not cause the server to close the connection

Go version
go version go1.23.4 darwin/arm64
Output of go env in your module/workspace:
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/jmaguire/Library/Caches/go-build'
GOENV='/Users/jmaguire/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/jmaguire/go/pkg/mod'
GONOPROXY='github.com/DefinedNet'
GONOSUMDB='github.com/DefinedNet'
GOOS='darwin'
GOPATH='/Users/jmaguire/go'
GOPRIVATE='github.com/DefinedNet'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.23.4/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.23.4/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.23.4'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/Users/jmaguire/Library/Application Support/go/telemetry'
GCCGO='gccgo'
GOARM64='v8.0'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/jmaguire/src/junkcode/read-deadline-empty-body/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/2t/rbxbv8612sq9_rdrxhtw8rzc0000gn/T/go-build893276654=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?
Issue two requests against a handler that sets r.Close = true: https://go.dev/play/p/1OVTsaO82br
What did you see happen?
Both requests used the same connection (see "Remote address" and "Close" flag on the client.)
What did you expect to see?
The server close the connection to the client per the Request docs:

// Close indicates whether to close the connection after
// replying to this request (for servers) or after sending this
// request and reading its response (for clients).

The docs do state the following:

// For server requests, the HTTP server handles this automatically
// and this field is not needed by Handlers.

The wording here ("not needed") implies that handlers can access it, but do not need to. In our case, we wanted to explicitly close the HTTP connection. Setting this flag did not achieve that. Setting r.Header().Set("Connection", "close") did.

Related Issues

x/net/http2: setting Request.Close doesn't close TCP connections #49375 (closed)
net/http, x/net/http2: TCP connection is not closed after http client request times out after missing RST (TCP) or GOAWAY(HTTP/2) frame #36026
net/http: TCP connection is not closed after http client makes a https request via a http proxy server which doesn't response #28012 (closed)
net/http: Response.Write adds redundant "Connection: Close" headers #19499 (closed)
net/http: Server still handling new connections after Close (or Shutdown) returns #36093 (closed)
net/http, x/net/http2: http server shutdown doesn't gracefully shut down HTTP2 connections #39776 (closed)
net/http: Errors from persistConn.readLoop not returned to client still writing a request #62447
net/http: request.Body.Close can be called more than once #40382 (closed)

Related Code Changes

net/http: close connection if `Connection: close` is set

Related Discussions

Calling Close() on http.Request.Body

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

I believe this is expected behavior, but poorly worded documentation

The docs for http.Handler explicitly state that handlers should not modify the request. I don't think we need to reducument that for every field.

Thanks @seankhliao - the phrasing "this field is not needed by Handlers" is what threw me off here. Something to the effect of "Changing this field from Handlers has no effect" might be more helpful.


#47 Example fix

When starting the application with an example, an error occurs if you immediately select a picture for recognition. This is due to the fact that the model for which recognition will occur has not yet been selected. In this PR we can see the fix for this error.
This PR can be linked to Issue #47

Thank you!


Create base architecture

Design core architecture for the project. The current idea is to use 3-layered architecture with a library for providing domain-wide interfaces and entities. As a result of this issue, all components and entities of these layers should be documented.

 first version.


Documentation does not include Changeset APIs

Changeset APIs are not included in documentation here. Please update the documentation to include parameters, expected behavior, and responses for:

Creating a changeset
Modifying a changeset
Checking the status of a changeset
Merging a changeset
Triggering CI for a changeset
Updating CI status of a changeset

Added:
https://mergequeue.com/documentation#change-sets


[Bug]: not support security WPA3 on Windows 10

Expected behavior
can connect to wifi witch the security is WPA3 on Windows 10
Current behavior
can't connect to wifi witch the security is WPA3 on Windows 10
Which are the affected features

[X] node API
[ ] CLI

Which is your operating system?
Windows
Environment
No response
Version of node-wifi
2.0.16
Steps to Reproduce
wifi.connect({ ssid: 'ssid', password: 'password' }, (err) => {
console.log('Connected');
});
Solutions
if (selectedAp.security.includes('WPA3')) {
profile_content += <connectionType>ESS</connectionType> <connectionMode>auto</connectionMode> <autoSwitch>true</autoSwitch> <MSM> <security> <authEncryption> <authentication>WPA3SAE</authentication> <encryption>AES</encryption> <useOneX>false</useOneX> </authEncryption> <sharedKey> <keyType>passPhrase</keyType> <protected>false</protected> <keyMaterial>${key}</keyMaterial> </sharedKey> </security> </MSM>;
}

Hi, I add this feature in my todo list but I am not sure to have the bandwith for that. Can you write a PR for this feature?


setuptools marked as a transitive dependency

Describe the bug
setuptools is marked as a transitive dependency if it is imported in the code. Is this correct, or should it always be ignored, since it is in a poetry environment by default?

Looked into this, and I think that if the package uses it, it is good to explicitly mark it as a dependency. Although tools like virtualenv and poetry add it to the environment by default, it is not part of the standard library.


added rivets definition and test

rivets/rivets.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/rivets
http://bower.io/search/?q=rivets
others?

[X] has a test file? (rivets/rivets-tests.ts or others)
[ ] pass the Travic-CI test?

@TrevorDev thanks mate!


Update TRG CheckList TRG 7.x

Reason
Next TRG Check will come
AC

current TRGś are available in Checklist
links are uptodate

Additional information / links
https://eclipse-tractusx.github.io/docs/release/trg-7/trg-7-00

@AngelikaWittek please review: https://github.com/eclipse-tractusx/.github/pull/7 😊

approved and merged


docs: Provide Docs Feedback & Fix Markdown and Metadata for Consistency

Description
This PR fixes the following:

Markdown (spacing, indentation, etc.)
Metadata (punctuations, etc.)
Typo and capitalization
Wordings adjustment

Providing Feedback
This PR also contains feedback for the docs that will be written in the reviews and comments.

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[x] 📝 Documentation ~Update~ Feedback and Consistency
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
As per discussion with @BekahHW, there is no issue made for this PR as the main purpose is to provide feedback and the fixes made here are not meant to change the docs.

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@BekahHW there are some questions and feedback that I can't put in the PR review like this one, so I'm using the comment. :)
https://github.com/open-sauced/docs/blob/e248a4213eb1fa3fd3818be275eaf8db1f9be969/docs/introduction.md?plain=1#L1-L6
Above code is from the introduction.md. Does it need title in the metadata instead of # Introduction to OpenSauced? And does it need keywords?

We have an empty welcome-to-the-community.md on the root. Should we remove that?

I added an issue for storybook: https://github.com/open-sauced/docs/issues/225

@BekahHW there are some questions and feedback that I can't put in the PR review (like this one) because there's no changes in the lines. So I'm using the comment instead. :)
https://github.com/open-sauced/docs/blob/e248a4213eb1fa3fd3818be275eaf8db1f9be969/docs/introduction.md?plain=1#L1-L6
Above code is from the introduction.md.

Does it need title in the metadata instead of # Introduction to OpenSauced?
Does it need keywords?

I think we can test it. Add those fields and see if it renders properlyl

I tested it out and it renders properly. So I added title and keywords for this.

@BekahHW I've checked the links and wordings and made necessary changes.
Need Review
Below are link to the comments that I need you to review and let me know if I need to fix anything before we merge in this PR:

https://github.com/open-sauced/docs/pull/213#issuecomment-1826425592
https://github.com/open-sauced/docs/pull/213#discussion_r1405387246
https://github.com/open-sauced/docs/pull/213#discussion_r1405392112
https://github.com/open-sauced/docs/pull/213#discussion_r1406067339
https://github.com/open-sauced/docs/pull/213#discussion_r1406385638
https://github.com/open-sauced/docs/pull/213#discussion_r1411360023
https://github.com/open-sauced/docs/pull/213#discussion_r1413958152 (this can also be a good first issue)

Potential New Issues & PRs
And below are potential new issues & PRs (please be noted that I don't include all comments for the resolving conflicts section here):
100 Days of OSS

https://github.com/open-sauced/docs/pull/213#discussion_r1405358366

Pizza CLI
https://github.com/open-sauced/docs/pull/213#discussion_r1405434510
https://github.com/open-sauced/docs/pull/213#discussion_r1405435475
Chrome Extension
Code Explanation

https://github.com/open-sauced/docs/pull/213#discussion_r1405460110

PR Description

https://github.com/open-sauced/docs/pull/213#discussion_r1405468056
https://github.com/open-sauced/docs/pull/213#discussion_r1405471684
https://github.com/open-sauced/docs/pull/213#discussion_r1405472781

Refactoring and Testing

https://github.com/open-sauced/docs/pull/213#discussion_r1406091477

Viewing Insights and Invitations

https://github.com/open-sauced/docs/pull/213#discussion_r1406379091

@BekahHW I made the changes and merged in Jessica's changes in this PR.
If there's no other suggestion, then it's ready to go. 👍


Click to deploy link

This change is

Turns out this doesn't work with the markdown github uses :( Closing.


Use Vagrant to set the VM hostname

This has the benefit that Salt will automatically pick up on the
hostname and use it as the minion id, removing the need to manually
pass the minion ID in the Vagrantfile and when debugging inside the VM.
This is blocked on https://github.com/mitchellh/vagrant/pull/7137 landing
and getting released in a new Vagrant version.
Reminder to self: update the wiki when this lands.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

:umbrella: The latest upstream changes (presumably #394) made this pull request unmergeable. Please resolve the merge conflicts.

Vagrant 1.8.5 will pass --retcode-passthrough to Salt, even in masterless mode. r? @edunham

:umbrella: The latest upstream changes (presumably #350) made this pull request unmergeable. Please resolve the merge conflicts.

I need to make another vagrant PR to add file_root and pillar_root options for the Salt provisioner, now that we're using those after #350, so this is blocked again.

Happily, this is no longer blocked as the Vagrant upstream feature this depended on has been merged and released as part of Vagrant 2.0: https://github.com/mitchellh/vagrant/blob/a124f6635844848f4369e620e1607701d22ddcb9/CHANGELOG.md.
I will try to update this PR soon.


Fix Stax/Flex: incomplete APDU is returned

Checklist

[x] App update process has been followed
[x] Target branch is develop
[x] Application version has been bumped

__


Fix build on master

script/generate-coverage expects at least one test file for each directory.

@nathanleclaire can you sign the commit?  thx

LGTM


fix a failure when dirs is empty at changes job.

fix https://github.com/containers/youki/issues/284

Codecov Report

Merging #294 (23f478f) into main (5d2901e) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #294      +/-   ##
==========================================
+ Coverage   69.76%   69.78%   +0.01%
==========================================
  Files          46       46
  Lines        5699     5699
==========================================
+ Hits         3976     3977       +1
+ Misses       1723     1722       -1

Patterns with changes in Rust code https://github.com/containers/youki/actions/runs/1223845447

@YJDoc2 This seems to work for now. The pattern with no code changes is ci of this PR ;)

Also in one of previous commits in this PR, you had made a separate job for dependencies, was there any issue with that? Or were the dependencies not sharable across jobs?

Also in one of previous commits in this PR, you had made a separate job for dependencies, was there any issue with that? Or were the dependencies not sharable across jobs?

That way of writing was completely wrong and I needed to think of another way.


Add AsyncSubject

Add AsyncSubject to RxJS v5. Other subjects can be added in the future, but this one is tried and true and used by many community members.

@blesh @staltz correct me if I'm wrong, but wouldn't it be as simple as this?
import {Subject} from '../Subject';
import {Subscriber} from '../Subscriber';
import {Subscription} from '../Subscription';

export class AsyncSubject<T> extends Subject<T> {
  constructor () {
    super();
    this.value = void 0;
    this.hasNext = false;
  }

  _subscribe(subscriber: Subscriber<any>): Subscription<T> {
    const subscription = super._subscribe(subscriber);
    if (!subscription) {
      return;
    } else if (!subscription.isUnsubscribed && this.hasNext) {
      subscriber.next(this.value);
      subscriber.complete();
    }
    return subscription;
  }

  _next(value: T): void {
    this.value = value;
    this.hasNext = true;
  }
}

LGTM.
I think once this completes, you could set _isScalar to true on it and get some benefits from operators that fast-track scalar observables.

:+1:  for AsyncSubject, thanks!
Just one question: what would be the difference with new ReplaySubject(1) (if any)? I just learnt about this alternative from angular2 gitter.

@architruc very different. AsyncSubject does not emit next values before it completes. It only emits on completion, and after completion for late subscribers.

@staltz Okay, if I understand well ReplaySubject emits at each value (let's say each next() in the source), but AsyncSubject on complete() in the source, right?
Yes, it is different, seems I misunderstood, although AsyncSubject could still help in my usecase. Thanks!

This can be closed now, I think.


fix cmake downstream find_package failure in double mode in windows

I realized I only fixed the problem of #229 for Linux while I was trying to update tinyobjloader for vcpkg. This fix allows double mode to work correctly in windows as well. I've tested it on vcpkg and it installs successfully with this change, and a minimal downstream example also works correctly.

Awesome! Merged!

@syoyo can we get another release? or retag the 2.0.0-rc2 to the current master, thanks!

@jasjuang Okay, v2.0.0-rc2 has been retagged.


git actions - clone repository by URL

Feature Request
Motivation Behind Feature
Sometimes it's important to work with another repository (not the one in which Fastlane is currently running).
For example, in this setup:

Clone sources from a remote repository (not the one where Fastlane is installed)
Compile sources
Put the artifacts into current repository, replace old artifacts
Commit & Push changes to current repository

Git actions, such as git_pull cannot help with the step 1, so I have to resort to sh scripts to achieve the desired result.
Feature Description
Accept additional parameters such as:

source URL
branch
etc, e.g. commit / tag

in git commands.
Code example:
git_pull(source: "https://github.com/fastlane/fastlane", folder: "fastlane_repository")

This won't break anything for the current users.
Alternatives or Workarounds
    # Getting Proto files
    sh('git clone https://github.com/fastlane/fastlane')

    # Getting version number
    last_tag = sh("
                        cd fastlane
                        git describe --abbrev=0 --tags | tr -d '\n'
                      ")

Moved from #14358

@fastlane-bot issue still persists.

@fastlane-bot doesn’t work
Sent with GitHawk

@fastlane-bot doesn't work

@fastlane-bot I need you to hurry up now
'Cause I can't wait much longer
I know I got to be right now
'Cause I can't get much wronger

@fastlane-bot doesn't work

@fastlane-bot doesn't work

@fastlane-bot


chore(master): release 0.3.0

:robot: I have created a release beep boop
0.3.0 (2023-11-23)
Features

add audit sink configuration (08f3cd4)
add automated integration tests (8351eb3)

Miscellaneous Chores

deps: update everything (31d39dd)
deps: upgrade dependencies (9b2a359)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/indykite/terraform-provider-indykite/releases/tag/v0.3.0 :sunflower:


Add required packs to decklist page

It would be great to add a list similar to the card list that includes all of the packs you'd need to own in order to build the current deck. Maybe including the number of packs in the case of the core set. Another similar feature could be letting users submit what packs they own and be able to filter by decks they could build.
Something roughly like this:

Maybe you don't need to break it out by big box vs data packs. Maybe you just list them in 2 columns in either alpha or chrono (release) order.

As a workaround, you can sort by Set on the decklist page, and it makes it pretty easy to see which packs you need, although it won't tell you if you need multiple core sets.

I didn't count the number of packs needed. Too lazy. But PR are welcome =)

Killer - thank you


Remote headless chrome

Is it possible to use a headless chrome running on a remote host?

Yes, take a look at the headless example in L23
https://github.com/knq/chromedp/blob/50c2d576db8913bb0f0d29dc148a1d8886c11c80/examples/headless/main.go#L23
and use a client.Option to give an URL:
https://github.com/knq/chromedp/blob/50c2d576db8913bb0f0d29dc148a1d8886c11c80/client/client.go#L300

Yes, as @martint17r has pointed out. You just need to point the client to connect to the remote host.


fix(rules): export subject-min-length rule

Hi, subject-min-length rule in<EMAIL_ADDRESS>has been missing since 80cd7cc.
source/rules/index.js should export source/rules/subject-min-length.js :smiley:
my-sharable-config/index.js:
module.exports = {
    rules: {
        'subject-min-length': [
            1,
            'always',
            0
        ]
    }
};

Stack trace:
/home/user/project/node_modules/conventional-changelog-lint/distribution/cli.js:235
                throw err;
                ^

TypeError: rule is not a function
    at /home/user/project/node_modules/conventional-changelog-lint/distribution/index.js:133:20
    at Array.map (native)
    at _callee$ (/home/user/project/node_modules/conventional-changelog-lint/distribution/index.js:112:10)
    at tryCatch (/home/user/project/node_modules/regenerator-runtime/runtime.js:64:40)
    at Generator.invoke [as _invoke] (/home/user/project/node_modules/regenerator-runtime/runtime.js:299:22)
    at Generator.prototype.(anonymous function) [as next] (/home/user/project/node_modules/regenerator-runtime/runtime.js:116:21)
    at step (/home/user/project/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
    at /home/user/project/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14
    at F (/home/user/project/node_modules/core-js/library/modules/_export.js:35:28)
    at /home/user/project/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12

Thanks for contributing - it's very late where I live and I don't have access to a full working machine right now, so I'll release in approx. 12 hours


added BernoulliNB

Added StandardScalar
Added RobustScalar
Added MinMaxScalar
Added normalize
Added scale

Hey,
For individual files create a single Pull Request.


wallet charts take too long to load

20-30 seconds on initial load.

checklist taking a while too.

fixed by a bunch of other work.


[tcp] Handle RST Packets

Description
Currently, we are not handling RST packets. For instance, in protocols::tcp::peer::Inner::send_rst() we are not waiting for ARP replies if needed.

Hello @BrianZill any updates on this?

Hello @BrianZill any updates on this?

As I mentioned in my May 10, 2022 comment, it's not entirely clear to me exactly what problem this Issue is about.  From the title, I would think it was complaining about receiving RST packets, while the description references sending RST packets.  And if the only problem is with not waiting for ARP, we have other Issues (yes, multiple) around that.


fix docker need to read load config after save

This has been added as part of another fix https://github.com/alseambusher/crontab-ui/commit/42e677d8d26d11dfc0ade2fade80fbca8c120fd5


Prepare the go-to-prod steps

@lalalaurentiu we need to have here the steps needed to switch the current website from Google Sites as it is today to deliver https://oportunitatisicariere.ro/ from this repo from main branch from GitHUB Pages as custom domain
this include:

[ ]  identify rotld login credentials
[ ] identify CloudFlare credentials
[ ] DNS updates needed
[ ] GitHUB Actions needed including build and deploy

Fixed


Remove PHP 5.2 Support

Along with the PSR-0 update, Stash should move fully to PHP 5.3 support, utilizing namespaces and eliminating the hack method we use to maintain 5.2 compatibility.

We can close this issue.

@kbond, have you already removed the "staticHack" methods that were there to support 5.2 users? If that's done I'll close the ticket, otherwise I'll leave this open until I can take that out (worst case scenario tomorrow, unless someone gets to it first).

I have not removed those methods - I will let you take care of it.

Sounds good. You have no idea how much I've been looking forward to that change (big performance boost from it).

All set, I guess this is another one we can close out.


Failed to build and serve mkdocs with multi repo plugin

Failed to build and serve mkdocs with multi repo plugin.
I created this master mkdocs project with a standard layout. And I was hoping to import Backstage docs just for testing.
# mkdocs.yaml
site_name: Master

theme:
  name: material

nav:
  - Intro: 'index.md'
  - Backstage: '!import https://github.com/backstage/backstage'

plugins:
  - multirepo

mkdocs-multirepo-plugin Version
pip show mkdocs-multirepo-plugin
Name: mkdocs-multirepo-plugin
Version: 0.3.5

Python version
python --version
Python 3.9.12

If I run mkdocs serve or mkdocs build I get this message:
INFO     -  Building documentation...
DEBUG    -  Loading configuration file:
            /Users/aborkovac/work/mkdocks/master/mkdocs.yml
DEBUG    -  Loaded theme configuration for 'material' from
            '/usr/local/lib/python3.9/site-packages/material/mkdocs_theme.yml':
            {'language': 'en', 'direction': None, 'features': [], 'palette':
            {'primary': None, 'accent': None}, 'font': {'text': 'Roboto', 'code':
            'Roboto Mono'}, 'icon': None, 'favicon': 'assets/images/favicon.png',
            'include_search_page': False, 'search_index_only': True,
            'static_templates': ['404.html']}
DEBUG    -  Config value: 'config_file_path' =
            '/Users/aborkovac/work/mkdocks/master/mkdocs.yml'
DEBUG    -  Config value: 'site_name' = 'Master'
DEBUG    -  Config value: 'nav' = [{'Intro': 'index.md'}, {'Backstage': '!import
            https://github.com/backstage/backstage?multi_docs=False'}]
DEBUG    -  Config value: 'pages' = None
DEBUG    -  Config value: 'site_url' = ''
DEBUG    -  Config value: 'site_description' = None
DEBUG    -  Config value: 'site_author' = None
DEBUG    -  Config value: 'theme' = Theme(name='material',
            dirs=['/usr/local/lib/python3.9/site-packages/material',
            '/usr/local/lib/python3.9/site-packages/mkdocs/templates'],
            static_templates=['sitemap.xml', '404.html'],
            locale=Locale(language='en', territory=''), language='en',
            direction=None, features=[], palette={'primary': None, 'accent': None},
            font={'text': 'Roboto', 'code': 'Roboto Mono'}, icon=None,
            favicon='assets/images/favicon.png', include_search_page=False,
            search_index_only=True)
DEBUG    -  Config value: 'docs_dir' = '/Users/aborkovac/work/mkdocks/master/docs'
DEBUG    -  Config value: 'site_dir' =
            '/var/folders/k_/f24rkbz57zz51gtyhvh094bm0000gn/T/mkdocs_h0qztwe9'
DEBUG    -  Config value: 'copyright' = None
DEBUG    -  Config value: 'google_analytics' = None
DEBUG    -  Config value: 'dev_addr' = Address(host='localhost', port=8002)
DEBUG    -  Config value: 'use_directory_urls' = True
DEBUG    -  Config value: 'repo_url' = ''
DEBUG    -  Config value: 'repo_name' = ''
DEBUG    -  Config value: 'edit_uri' = ''
DEBUG    -  Config value: 'extra_css' = []
DEBUG    -  Config value: 'extra_javascript' = []
DEBUG    -  Config value: 'extra_templates' = []
DEBUG    -  Config value: 'markdown_extensions' = ['toc', 'tables', 'fenced_code']
DEBUG    -  Config value: 'mdx_configs' = {}
DEBUG    -  Config value: 'strict' = False
DEBUG    -  Config value: 'remote_branch' = 'gh-pages'
DEBUG    -  Config value: 'remote_name' = 'origin'
DEBUG    -  Config value: 'extra' = {}
DEBUG    -  Config value: 'plugins' = PluginCollection([('multirepo',
            <mkdocs_multirepo_plugin.plugin.MultirepoPlugin object at
            0x103415850>)])
DEBUG    -  Config value: 'watch' = None
INFO     -  Multirepo plugin importing docs...
                    :   0%|                                  | 0/1 [00:00<?, ?it/s]

or
DEBUG    -  Loading configuration file:
            /Users/aborkovac/work/mkdocks/master/mkdocs.yml
DEBUG    -  Loaded theme configuration for 'material' from
            '/usr/local/lib/python3.9/site-packages/material/mkdocs_theme.yml':
            {'language': 'en', 'direction': None, 'features': [], 'palette':
            {'primary': None, 'accent': None}, 'font': {'text': 'Roboto', 'code':
            'Roboto Mono'}, 'icon': None, 'favicon': 'assets/images/favicon.png',
            'include_search_page': False, 'search_index_only': True,
            'static_templates': ['404.html']}
DEBUG    -  Config value: 'config_file_path' =
            '/Users/aborkovac/work/mkdocks/master/mkdocs.yml'
DEBUG    -  Config value: 'site_name' = 'Master'
DEBUG    -  Config value: 'nav' = [{'Intro': 'index.md'}, {'Backstage': '!import
            https://github.com/backstage/backstage?multi_docs=False'}]
DEBUG    -  Config value: 'pages' = None
DEBUG    -  Config value: 'site_url' = ''
DEBUG    -  Config value: 'site_description' = None
DEBUG    -  Config value: 'site_author' = None
DEBUG    -  Config value: 'theme' = Theme(name='material',
            dirs=['/usr/local/lib/python3.9/site-packages/material',
            '/usr/local/lib/python3.9/site-packages/mkdocs/templates'],
            static_templates=['sitemap.xml', '404.html'],
            locale=Locale(language='en', territory=''), language='en',
            direction=None, features=[], palette={'primary': None, 'accent': None},
            font={'text': 'Roboto', 'code': 'Roboto Mono'}, icon=None,
            favicon='assets/images/favicon.png', include_search_page=False,
            search_index_only=True)
DEBUG    -  Config value: 'docs_dir' = '/Users/aborkovac/work/mkdocks/master/docs'
DEBUG    -  Config value: 'site_dir' = '/Users/aborkovac/work/mkdocks/master/site'
DEBUG    -  Config value: 'copyright' = None
DEBUG    -  Config value: 'google_analytics' = None
DEBUG    -  Config value: 'dev_addr' = Address(host='<IP_ADDRESS>', port=8000)
DEBUG    -  Config value: 'use_directory_urls' = True
DEBUG    -  Config value: 'repo_url' = ''
DEBUG    -  Config value: 'repo_name' = ''
DEBUG    -  Config value: 'edit_uri' = ''
DEBUG    -  Config value: 'extra_css' = []
DEBUG    -  Config value: 'extra_javascript' = []
DEBUG    -  Config value: 'extra_templates' = []
DEBUG    -  Config value: 'markdown_extensions' = ['toc', 'tables', 'fenced_code']
DEBUG    -  Config value: 'mdx_configs' = {}
DEBUG    -  Config value: 'strict' = False
DEBUG    -  Config value: 'remote_branch' = 'gh-pages'
DEBUG    -  Config value: 'remote_name' = 'origin'
DEBUG    -  Config value: 'extra' = {}
DEBUG    -  Config value: 'plugins' = PluginCollection([('multirepo',
            <mkdocs_multirepo_plugin.plugin.MultirepoPlugin object at
            0x107451460>)])
DEBUG    -  Config value: 'watch' = None
INFO     -  Multirepo plugin importing docs...
                    :   0%|                                  | 0/1 [00:00<?, ?it/s]

@borkke, I wasn't able to reproduce your error. Actually, I'm not sure what the error is. Is the last console output just hanging? Maybe it's something with the environment (i.e., OS) your running. I used the below configuration and was able to import the project's docs.
site_name: Master

theme:
  name: material

nav:
  - Intro: 'index.md'
  - Backstage: '!import https://github.com/backstage/backstage'

plugins:
  - multirepo

I then build a python venv and pip installed mkdocs, mkdocs-material and mkdocs-multirepo-plugin. After setting up the venv I was able to successfully run mkdocs serve.
I ran this on a Windows machine with Python 3.9.2.
(env) C:\> mkdocs serve
INFO     -  Building documentation...
INFO     -  Multirepo plugin importing docs...
✅ Got Backstage Docs: 100%|██████████████████████████████████████████████████████████████| 1/1 [00:05<00:00,  5.49s/it]
INFO     -  Cleaning site directory
INFO     -  The following pages exist in the docs directory, but are not included in the "nav" configuration:
              - testing.md
              - Backstage\README.md
              - Backstage\publishing.md
              - Backstage\api\backend.md
              - Backstage\architecture-decisions\adr000-template.md
              - Backstage\auth\atlassian\provider.md
              - Backstage\auth\google\gcp-iap-auth.md
              - Backstage\features\software-templates\migrating-from-v1beta2-to-v1beta3.md
              - Backstage\features\software-templates\writing-custom-field-extensions.md
              - Backstage\getting-started\configuration.md
              - Backstage\getting-started\homepage.md
              - Backstage\releases\v1.0.0.md
              - Backstage\tutorials\backend-to-backend-auth.md
              - Backstage\tutorials\configuring-plugin-databases.md
WARNING  -  A relative path to 'Backstage/features/software-templates/legacy.md' is included in the 'nav' configuration,
            which is not found in the documentation files
WARNING  -  A relative path to 'Backstage/features/software-templates/migrating-from-v1alpha1-to-v1beta2.md' is included
            in the 'nav' configuration, which is not found in the documentation files
WARNING  -  A relative path to 'Backstage/features/search/configuration.md' is included in the 'nav' configuration, which
            is not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/index.md' is included in the 'nav' configuration, which is not found in
            the documentation files
WARNING  -  A relative path to 'Backstage/plugins/existing-plugins.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/create-a-plugin.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/plugin-development.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/structure-of-a-plugin.md' is included in the 'nav' configuration, which
            is not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/plugin-development.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/integrating-plugin-into-software-catalog.md' is included in the 'nav'
            configuration, which is not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/composability.md' is included in the 'nav' configuration, which is not
            found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/analytics.md' is included in the 'nav' configuration, which is not
            found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/proxying.md' is included in the 'nav' configuration, which is not found
            in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/backend-plugin.md' is included in the 'nav' configuration, which is not
            found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/call-existing-api.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/github-apps.md' is included in the 'nav' configuration, which is not
            found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/url-reader.md' is included in the 'nav' configuration, which is not
            found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/testing.md' is included in the 'nav' configuration, which is not found
            in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/publish-private.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/add-to-marketplace.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/plugins/observability.md' is included in the 'nav' configuration, which is not
            found in the documentation files
WARNING  -  A relative path to 'Backstage/support/project-structure.md' is included in the 'nav' configuration, which is
            not found in the documentation files
WARNING  -  A relative path to 'Backstage/glossary.md' is included in the 'nav' configuration, which is not found in the
            documentation files
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createplugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createplugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.useapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.withapis.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.useapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apifactory.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apifactory.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.alertapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createapifactory.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.configapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\app-defaults.createapp.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to 'Backstage\reference\app-defaults.md'
            which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apifactory.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createplugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\app-defaults.createapp.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.errorapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createplugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createplugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.createapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to 'Backstage\reference\test-utils.md'
            which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to 'Backstage\reference\dev-utils.md'
            which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\dev-utils.createdevapp.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\app-defaults.createapp.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\api\utility-apis.md' contains a link to
            'Backstage\reference\dev-utils.createdevapp.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\auth\using-auth.md' contains a link to 'Backstage\reference\core-plugin-api.md'
            which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\conf\reading.md' contains a link to 'Backstage\reference\config.config.md'
            which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\conf\reading.md' contains a link to
            'Backstage\reference\core-plugin-api.configapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\features\software-catalog\index.md' contains a link to
            'Backstage\plugins\index.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\getting-started\configuration.md' contains a link to
            'Backstage\plugins\github-apps.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\getting-started\running-backstage-locally.md' contains a link to
            'Backstage\plugins\create-a-plugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\getting-started\running-backstage-locally.md' contains a link to
            'Backstage\plugins\structure-of-a-plugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\integrations\github\discovery.md' contains a link to
            'Backstage\plugins\github-apps.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\integrations\github\locations.md' contains a link to
            'Backstage\plugins\github-apps.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\local-dev\cli-commands.md' contains a link to
            'Backstage\plugins\github-apps.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\overview\adopting.md' contains a link to 'Backstage\plugins\index.md' which is
            not found in the documentation files.
WARNING  -  Documentation file 'Backstage\overview\adopting.md' contains a link to
            'Backstage\plugins\call-existing-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\overview\architecture-overview.md' contains a link to
            'Backstage\plugins\composability.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\plugins\call-existing-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\plugins\call-existing-api.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\plugins\backend-plugin.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\plugins\proxying.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\reference\core-plugin-api.createapiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\reference\core-plugin-api.apiref.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\reference\core-plugin-api.apifactory.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\reference\core-plugin-api.createapifactory.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\reference\core-plugin-api.useapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\reference\core-plugin-api.discoveryapi.md' which is not found in the documentation files.
WARNING  -  Documentation file 'Backstage\tutorials\using-backstage-proxy-within-plugin.md' contains a link to
            'Backstage\reference\core-plugin-api.useapi.md' which is not found in the documentation files.
INFO     -  Multirepo plugin is cleaning up temp_dir/
INFO     -  Documentation built in 8.64 seconds
INFO     -  [09:40:20] Watching paths for changes: 'docs', 'mkdocs.yml'
INFO     -  [09:40:20] Serving on http://<IP_ADDRESS>:8000/
INFO     -  [09:40:24] Browser connected: http://<IP_ADDRESS>:8000/Backstage/overview/what-is-backstage/

Yeah, it just hangs. That's the case for both commands.
I'll dig deeper to figure out what the problem is.
PS. I'm running on mac

Can't reproduce error.


Connection with readonly user fails

When using readonly user credentials - connection fails with Code: 164. DB::Exception: Cannot modify 'join_use_nulls' setting in readonly mode. (READONLY) (version <IP_ADDRESS> (official build))

It's a known limitation of the Connector (and it is made intentionally).
Session settings (ie join_use_nulls=1) couldn't be modified by the 'readonly' user --
or any other user from the 'readonly' profile set in the /etc/clickhouse-server/users.xml.
A more straightforward approach is to GRANT SELECT ON <schema>.* TO <username>

Didn't work, I've created the user via
GRANT SHOW TABLES, SELECT ON * TO tableau2;```
and getting the same error:
`Code: 164. DB::Exception: Cannot modify 'join_use_nulls' setting in readonly mode. (READONLY) (version <IP_ADDRESS> (official build))`

SETTINGS PROFILE 'readonly'  is the point of concern.
Could you test by creating yet another user without applying the PROFILE settings?

yep, it works without PROFILE 'readonly',


Beavers placing doors seems broken

Beavers tore apart a village and started building a dam out of it. When they pick up doors, they try to place them as part of the dam but they are placed as one block tall (just the bottom half of the door) and glitch out if a player tries to interact with them.

I had no idea they could even pick up doors that's really funny


haskell.packages.ghc94.gtk2hs-buildtools: remove patch for upstream fix

Description of changes

The gtk2hs-buildtools-fix-ghc-9.4 patch was introduced in 7409480d5c8584a1a83c422530419efe4afb0d19 to address https://github.com/gtk2hs/gtk2hs/issues/323. That issue has since been fixed upstream and a new release added to hackage on 2023-05-12, so if you try to run nix build .#haskell.packages.ghc945.gtk2hs-buildtools now you get an error like:
gtk2hs-buildtools> src/Gtk2HsSetup.hs:297:20: error:
gtk2hs-buildtools>     duplicate field name ‘ppOrdering’ in record construction
gtk2hs-buildtools>     |
gtk2hs-buildtools> 297 | ourC2hs bi lbi _ = PreProcessor {
gtk2hs-buildtools>     |                    ^^^^^^^^^^^^^^...
error: builder for '/nix/store/v138akp5dfcjky86d83gzgjgij64p2zr-gtk2hs-buildtools-<IP_ADDRESS>.drv' failed with exit code 1;
       last 10 log lines:
       > [43 of 46] Compiling GenBind          ( c2hs/gen/GenBind.hs, dist/build/GenBind.o, dist/build/GenBind.dyn_o )
       > [44 of 46] Compiling Version          ( c2hs/toplevel/Version.hs, dist/build/Version.o, dist/build/Version.dyn_o )
       > [45 of 46] Compiling Gtk2HsC2Hs       ( c2hs/toplevel/Gtk2HsC2Hs.hs, dist/build/Gtk2HsC2Hs.o, dist/build/Gtk2HsC2Hs.dyn_o )
       > [46 of 46] Compiling Gtk2HsSetup      ( src/Gtk2HsSetup.hs, dist/build/Gtk2HsSetup.o, dist/build/Gtk2HsSetup.dyn_o )
       >
       > src/Gtk2HsSetup.hs:297:20: error:
       >     duplicate field name ‘ppOrdering’ in record construction
       >     |
       > 297 | ourC2hs bi lbi _ = PreProcessor {
       >     |                    ^^^^^^^^^^^^^^...
       For full logs, run 'nix log /nix/store/v138akp5dfcjky86d83gzgjgij64p2zr-gtk2hs-buildtools-<IP_ADDRESS>.drv'.

due to both upstream and the patch adding the ppOrdering field. This PR removes the unnecessary patch.
Thanks!
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Thanks!
Could you rebase this on the haskell-updates branch?  We generally ask all Haskell-related PRs to be targeted on the haskell-updates branch.
https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging

Ah of course, oversight.

Looks like it now builds fine, thanks!

Thank you!


annotations attribute is missing in the SDK

What happened:
spec defines annotations attribute on the workflow but it does not exist in the SDK
https://github.com/serverlessworkflow/specification/blob/main/specification.md#Workflow-Definition-Structure
What you expected to happen:
annotations should be available in SDK
How to reproduce it:
use SDK to parse any workflow that uses annotations attribute, it won't be available

Thanks @tsurdilo for amazing speed on fixing it!


Add base hostname to cluster_infos.json

Would be helpful to have also the base domain (xxx.xxx.xxx.xxx.nip.io) in the output json.

Aren't we already doing this?
https://github.com/crc-org/snc/blob/791d8e2cda8042c7fa0ff81187aab6df3b1f46d7/crc-bundle-info.json.sample#L34

I'm not sure if we're talking about the same thing, but the crc-cloud script, when the instance is created, produces an output file in the working directory, in the machine that launched the script, containing the console address and the api address
{
  "api": {
    "address": "https://api.<IP_ADDRESS>.nip.io",
    "port": "6443"
  },
  "console": {
    "address": "https://console-openshift-console.apps.<IP_ADDRESS>.nip.io",
    "port": "443"
  }
}

the purpose of this script is to pass these infos to the next steps of the automation in which it might be included (like CI/CD) pipelines, I noticed that it might be helpful to have the base address as well.

they are included in the bundles we deliver, so this might the result of another step that you aren't performing... and perhaps need to be seperated from the final bundling.

@tsebastiani We build api and console address using the api.<cluster_name>.<baseDomain> and console-<namespace>.apps-<cluster_name>.<baseDomain> and in the cloud-script it changes because we add additional domain for nip.io and also patch the console domain to consume nip.io . I think SNC side we don't need to add those details since it is already correct for crc context.

the problem is that now, in my github action, so from outside the VM, in order to have the base hostname , I've to do something like that
BASE_HOST=`$JQ -r '.api.address'  $CLUSTER_INFO_PATH | sed -r 's#https:\/\/api\.(.+\.nip\.io)#\1#'`

That's not the most comfortable thing, having it as a property in cluster_infos.json is one line of code and wouldn't bother too much IMHO

If you are talking about cluster_infos.json, it's a file generated by crc-cloud https://github.com/crc-org/crc-cloud/blob/6869ce2ee817066b3cc02836f0323d3e1893360a/crc-cloud.sh#L175-L183 so I would move this issue/the discussion to crc-cloud.
snc generates a crc-bundle-info.json file with this kind of content: https://github.com/crc-org/snc/blob/master/crc-bundle-info.json.sample
Since it's crc-cloud doing the .nip.io patching, I agree with Praveen that it's up to crc-cloud to do any patching/provide any additional info which might be missing.

If you are talking about cluster_infos.json, it's a file generated by crc-cloud https://github.com/crc-org/crc-cloud/blob/6869ce2ee817066b3cc02836f0323d3e1893360a/crc-cloud.sh#L175-L183 so I would move this issue/the discussion to crc-cloud. snc generates a crc-bundle-info.json file with this kind of content: https://github.com/crc-org/snc/blob/master/crc-bundle-info.json.sample
Since it's crc-cloud doing the .nip.io patching, I agree with Praveen that it's up to crc-cloud to do any patching/provide any additional info which might be missing.

If you are talking about cluster_infos.json, it's a file generated by crc-cloud https://github.com/crc-org/crc-cloud/blob/6869ce2ee817066b3cc02836f0323d3e1893360a/crc-cloud.sh#L175-L183 so I would move this issue/the discussion to crc-cloud.
snc generates a crc-bundle-info.json file with this kind of content: https://github.com/crc-org/snc/blob/master/crc-bundle-info.json.sample
Since it's crc-cloud doing the .nip.io patching, I agree with Praveen that it's up to crc-cloud to do any patching/provide any additional info which might be missing.
You're perfectly right, just figured out was in the wrong place, that was the root cause of the misunderstanding, I was following the notifications and didn't see that was placed in the wrong repo 😅, sorry about that


Request: provide full reference

It would be useful to have a class/function API reference in addition to the current narrative documentation.

Sorry for the delay on this, I've just added autodoc for some of the classes and will continue to add more as I go along. PR's with doc string would be greatly appreciated


Ghost 1.0.0 Documentation

This issue is a placeholder for keeping a list of documentation we're going to need to write/rewrite for Ghost 1.0.0.
pre-tasks from meeting

help.ghost.org - stays as is
themes.ghost.org stays as it
docs.ghost.org - die, but it will be the new developers/core documentation
[x] http://support.ghost.org - migrate to docs.ghost.org @cobbspur
[ ] academy.ghost.org - die (move to help.ghost.org) - @frantzypants will care
[x] move github wiki to docs.ghost? (except of contributing.md, which links to readme) which includes tooling, apps, how to develop with server/client etc @kevinansfield @kirrg001
[x]  @sebgie support.ghost.org dies

required
@AileenCGN

[x] http://themes.ghost.org/ + documentation for package.json theme validation
[x] from #8348: additional theme documentation updates
[x] new error templates. base / 5xx errors should never use any helpers other than asset.
[x] mail config
[x] ghost.org/developers shows API, themes, core (developers) and docs.ghost.org

@kirrg001

[x] How to use the new config (http://support.ghost.org/config)
[x] How to use the new CLI installer
[x] improve working with Ghost 1.0 guide
[x] remove remote authentication configuration option in our docs/wiki
[x] ?formats query param
[x] update ghost-server.js -> change Alpha to Beta
[x]  go over LTS branch and update broken links e.g. in the content folder or readme
[x] Update installation guide for self hoster
[x] update storage and scheduling guides - adapter location
[x] https://dash.readme.io/legacy/project/ghost/v1.0.0/docs/how-to-setup-ssl-for-self-hosted-ghost - what about this page? stay as is
[x]  https://dash.readme.io/legacy/project/ghost/v1.0.0/docs/how-to-setup-ssl-for-self-hosted-ghost - what about this page? stay as is
[x]  https://docs.ghost.org/docs/troubleshooting-guide

@kevinansfield

[x] cleanup wiki pages
[x] document grunt master
[x] yarn run init -> explain that this command is only for initial setup + warning on feature branches!
[x] grunt file: go over documentation and double check if we have old documentation for 1.0 for old commands
[x] grunt dev documentation to explain when/why to use the individual commands
[x] Add client documentation for developing
[x] https://www.google.co.uk/search?client=safari&rls=en&q=site:support.ghost.org&ie=UTF-8&oe=UTF-8&gfe_rd=cr&ei=YOgrWdioG-_GXqvOvvgO - replace and then redirect the old content (the new content should live on another readme.io site)
[x] Update README master + remove alpha wording
[x] Update contributing guide master
[x] highlight github README (GHOST PRO) section

@cobbspur

[x] http://support.ghost.org/supported-node-versions/ - LTS vs. 1.0
[x] documentation suggestions: https://github.com/TryGhost/Ghost/issues/8421
[x] server logs - explain server logs and logging - support.ghost.org + wiki?
[x] how to migrate from LTS to 1.0 - page?
[x] https://support.ghost.org/v1-0-alpha to https://support.ghost.org/v1-0-beta?
[x] manage alpha/beta pages on General category

@frantzypants

[x] help.ghost.org to the list - the settings screens and anything with the editor will need updating.

optional

Github wiki

[ ] rework main contributing guide
[ ] clean up gruntfile
[ ] readme.io -> segment link
[ ] redirects - maybe support.ghost.org, but need to measure traffic first

We have added two new wiki pages so far. Both need a final review.
https://github.com/TryGhost/Ghost/wiki/Working-with-Ghost

this is a developer documentation
it will be referenced in the Ghost README.md via #8175.
we should reference the new developer documentation here as well https://github.com/TryGhost/Ghost/blob/master/.github/CONTRIBUTING.md#installation--setup-instructions.
the documentation needs some more guidance about how to develop the client @kevinansfield

https://github.com/TryGhost/Ghost/wiki/How-to-run-your-Ghost-1.0.0-beta-blog

as soon as we release the first 1.0.0 beta version, this documentation will guide people how to install and start the Ghost 1.0.0 beta. A final review from @acburdine would be great.

Thinking we should add updating help.ghost.org to the list - the settings screens and anything with the editor will need updating.

Some notes:
alpha-and-beta-versions

this mentions doing a release "today"
doesn't explain the difference between alpha and beta, not really important tho

installing-ghost-via-the-cli

missing explanation of the system stack e.g. for production the fact that MySQL and nginx are required
this may need to cover users and permissions? Not sure if Ghost-CLI is going to handle this
missing explanation ghost install vs ghost install local
ghost doctor, ghost config & ghost setup are not documented
mentions<EMAIL_ADDRESS>but I'm not sure this is this a real address?

configuring ghost

location of configuration files is different in Ghost-Cli
still says Ghost is configured with sqlite3 by default

1-Click installer & Hosting

IMHO this should be "Hosting" with an explanation of the supported stack (see https://github.com/TryGhost/Ghost-CLI/wiki/System-Stack) & where to get a suitable server. Any mention of 1-click installers or other hosts should be that it's not officially supported?

General:

I think we need to make the new officially supported stack front-and-centre for everything to do with self-hosting
I think we're missing a page about how to install ghost (using ghost install local if you're developing themes etc - would be really to have a theme devs guide/landing page that explains gscan and links to themes.ghost.org as well)
I believe Ghost-CLI is likely to need its own section of extended documentation beyond the main how-to-install type guide, covering the advanced commands & what it's doing behind the scenes. I 100% approve of the new all-docs-live-at docs.ghost.org, so would strongly advocate for moving the docs at https://github.com/TryGhost/Ghost-CLI/wiki & removing the extra wiki?

These are opinions & I haven't read everything, just a few bits from the perspective of being a CLI user.

@ErisDS
I have added this issue back to the Ghost backlog.
Thanks for your notes 👍
We kept the CLI documentation for the first beta release short on purpose (was discussed/agreed in slack). The goal was to cover the basic CLI commands for development install. See e.g. https://docs.ghost.org/docs/basic-nginx-config-self-hosted-with-custom-domain, we added notes to share what's upcoming. As soon as we are ready for CLI production, we will extend the CLI guides.

I didn't see that page in the docs, I was only looking for information on ghost-cli, which does the nginx config for me.
That nginx config page is very confusing, as the only thing that should be done before running ghost-cli is getting rid of the default vhost (and perhaps set the client_max_body_size). If you create this nginx setup before you run ghost-cli, then your blog will not work as there will be multiple sites listening on port 80.
What I think we ought to do, is document what ghost-cli does in terms of nginx setup - e.g. show the configuration it creates.

The goal was to cover the basic CLI commands for development install.

Quick Q to clarify what is meant by a development install? Did you mean self-hoster install here? because a development install would be ghost install local which has not yet been documented.

Oh that is interesting. It was ghost install local before 😕  I will change it back for now.

I am still not sure if there is clarity here:
ghost install local = developer install, for running on your local machine and testing. Does not setup nginx etc, uses sqlite3. Meant for quick tests or installing locally to create themes and apps.
ghost install = for production servers, only runs on linux and warns if it is not ubuntu 16.04
I don't understand why we have cli + separate nginx documentation in the same section?
If the current CLI guide is meant to just be for developers testing out locally, it doesn't fit under a section called "Self-host" & also this should be clearer. If it's meant to be the self-hosting instructions, then it should be documenting that ghost install does the nginx setup.
I know that next sprint is going to be a CLI sprint, and I understand wanting to keep it short to start with, however I'm double checking this because the documentation makes it seem like the difference between ghost install and ghost install local is not well understood.

I know that next sprint is going to be a CLI sprint

Correct.

ghost install local = developer install, for running on your local machine and testing

Yes absolutely correct. In theory, you can use ghost install local in your droplet, configure the rest yourself (e.g. nginx) and you can test the beta. But sure, it was designed for local install.

I absolutely agree having this section under Self Hosters might be a big confusion, but that's why we have put warnings everywhere. I can't remember that we have gotten feedback that the guide is very bad/confusing, but i might be wrong.
We all knew that the CLI was and is not ready yet and we all knew that the the next sprint is going to be a pure CLI sprint pulling it straight. Let's tackle this together 😎

Hi, have you considered adding a section for self-hosters with non-standard stack? I could provide some key information for RedHat/Centos users regarding firewall, selinux and nginx settings.

This would defeat the point of having an "official" stack.
What we are trying to achieve is not having the core team spending large amounts of time trying to add support for every possible self-hoster setup & adding a ridiculous QA overhead that literally stops us from being able to do anything ever. Instead, we have one stack that we support for self-hosters and that is Ubuntu 16.
You are more than welcome to ignore the official recommendation, but in that case you would need to refer to community documentation not official documentation.

@ErisDS yes I understand the point with official stack and i fully agree with that aproach. I wouldn't want you guys to spend your time on documenting or developing for hundreds of possible builds. What I ment is to actually host or indicate (link from ghost.org) place where community could keep such documentation so that it's kept in one place. That's just an idea anyway.

All of the tasks here were resolved. We can re-open this issue if we discover any missing tasks or raise a new one 👍  Closing.


Thoughts on padded-blocks rule?

What are your thoughts on the padded-blocks rule?
http://eslint.org/docs/rules/padded-blocks.html
I have some code like this:
function foo () {
  return doAsync()
    .then(function () {
      return ...
    }, function () {
      // user exited early
      return ...
    })
}

But because of this rule I am getting an error because // user exited early is treated as a blank line.
Personally I find super strict rules like this just slow down my dev cycle.

hmm wouldn't a fix be to treat comments as non-blank lines?

I was able to verify that this passes with no linting problems:
function doAsync () {}

function foo () {
  return doAsync()
    .then(function () {
      return 'yay'
    }, function () {
      // user exited early
      return 'wee'
    })
}

module.exports = foo

Is it possible to run standard --verbose to see what rule is being violated for your snippet?

Error: Use JavaScript Standard Style (https://github.com/feross/standard)
  foobar.js:17:24: Block must not be padded by blank lines. (eslint/padded-blocks)

Exact code:
var argv = {}
commit()

//commits current working dir, resolves to html_url
function commit (result) {
  var url = result.html_url
  //user opted not to commit anything
  if (argv.b || argv.bare) {
    return Promise.resolve(url)
  }
  return getMessage().then(function (message) {
    return gitCommit({
      message: message,
      url: url + '.git'
    }).catch(function () {
      return Promise.resolve(url)
    }).then(function () {
      // some stuff
      return url
    })
  })
}

function getMessage () {

}

function gitCommit () {

}

For that snippet w/ latest npm standard I get:
$ standard
Error: Use JavaScript Standard Style (https://github.com/feross/standard)
  index.js:4:0: Expected space or tab after // in comment.
  index.js:7:2: Expected space or tab after // in comment.
  index.js:30:1: Newline required at end of file but not found.

@maxogden same! After fixing them it is clean.

I'm using latest as well (3.2.1). I get the newline issue but not the space or tab after //.
I think this is related to the babel-eslint issue.

Resolved after #85 was fixed


Alert always shows close button

The alert directive always shows the close button ('x'), even if no close attribute is present.
This behaviour only occurs when using Angular.js v. 1.4.1. With version 1.4.0 everything is Ok.
To reproduce:
Use Angular.js v. 1.4.1 and use alert directive without 'close' attribute.

Could you setup a plunkr please? thx

We don't officially support Angular 1.4 yet so it is possible that some bugs occur. In the meanwhile, it helps if you provide a plunkr like @antoinepairet asked.

http://plnkr.co/edit/gcnHKbhzbt6u7eFCDisK?p=preview

This should be an easy fix on your side via CSS.
However, this does appear to be a bug in Angular 1.4 though.

Linking a version of the Plunker based off of current master here for reference.

According to my setup including AngularJS 1.4.2 this fix isn't working for $attrs always containing property close, most probably due to its explicit declaration in scope definition of directive alert. Putting aside concerns about using in-operator it might require some more complex logic like this:
$scope.closeable = !!$attrs.close && $attrs.close !== "undefined";

I tried the previous test - not the one proposed here, but the one "fixed" above - with
<alert type="danger"></alert>

(no close attribute at all)
<alert type="danger" close></alert>

and
<alert type="danger" close=""></alert>

In every case $scope.closeable is falsy in AngularJS 1.4.2, thus not showing close icon.


Is it possible to add code to c3runtime/types.js

In SDKV1, I am adding a 'central' object to the type which I can use from each object instance, howwould I add similar code in this frame work (I tried modifying the files under _base in my addon project dir, but I think it is being pulled from the jsr library path instead.)

https://github.com/lostinmind-dev/lost-c3/releases/tag/1.2.4


Verify if it is possible to change the warning window in exitScript for a Modal window

Moved from GCCode: https://gccode.ssc-spc.gc.ca/iitb-dgiit/nw-ws/sgdc-cdts/issues/133
@StdGit created this issue
https://ssl-templates.services.gc.ca/app/cls/WET/gcweb/v4_0_32/cdts/samples/exitscript-en.shtml

If you look modal-popup
https://wet-boew.github.io/wet-boew/demos/lightbox/lightbox-en.html
And you click in the dark area, the window doesn’t close
in cdts it's closing. It is an enhacement...
But perhaps user prefer the way it is.
https://ssl-templates.services.gc.ca/app/cls/WET/gcweb/v4_0_32/cdts/appTop/refFooter_exitscript-en.shtml
https://ssl-templates.services.gc.ca/app/cls/WET/gcintranet/v4_0_32/cdts/appTop/refFooter_exitscript-en.shtml
Contenu superposé centré - Modal (Lightbox + Modal)
Secure exit notice

Warning

This is a custom message. You are about to leave a secure site, do you wish to continue?
NopeSureCloseClose overlay

× Close overlay (escape key)

@MaximMartel Could you confirm this issue is still valid for version 4.0.39 ? Thanks.

In the latest release (v4.0.39), we are now using the exitScript feature provided by WET. We can modify the content (i.e. the message, button labels) but cannot change the the warning window itself.

In the latest release (v4.0.39), we are now using the exitScript feature provided by WET. We can modify the content (i.e. the message, button labels) but cannot change the the warning window itself.


Invalid Array Length when window has low width

When using lerna I'm getting its bootstrap failing sometimes when the window has very low width.

This is on Windows 10, node v6.2.2, npm 3.10.6.

Should be able to do:
Array(Math.max(0, width - completeLength + 1))

Want to make a PR?

Sure, will try an toss it together in the morning.


Consider renaming if_ and while_ to static_if and static_while

Why? Could they be dynamic (and still be in hana)?

for statements that would be used frequently like those I would lean towards the current names

Why? Could they be dynamic (and still be in hana)?

Currently, if_ and while_ can be used with runtime boolean conditions too, so indeed static_xxx would be a bad name. However, I'm looking at the possibility of only supporting integral_constant-like conditions for a first release, because that would allow simplifying the Logical concept, which I don't like all that much.

for statements that would be used frequently like those I would lean towards the current names

From my experience, those statements are not used all that frequently. while_ definitely isn't, and if_ is slightly more common but not that bad. If using static_if can add clarity, that should be the main goal. Note that this is motivated by a comment by someone during my CppCon talk; I was explaining code with an if_ in it, and when a person asked me whether that was basically a static if, it made everything much simpler I think.

Screw this for now; let's not lose generality by implying that they can only be used with IntegralConstants. There does not seem to be a sufficiently compelling reason to rename them.


Default value for datetime type not working for sqlite

The following annotation
    /**
     * @ORM\Column(name="changed_at", type="datetime", options={"default": 0})
     */
    private $changedAt;

should produce this outcome in sqlite
changed_at DATETIME DEFAULT CURRENT_TIMESTAMP
but produces
changed_at DATETIME DEFAULT '0' NOT NULL
in version 2.6.2.
Did something change in the API or is this a bug?
Thanks in advance.

You have to change your annotation to:
    /**
     * @ORM\Column(name="changed_at", type="datetime", options={"default": "CURRENT_TIMESTAMP"})
     */
    private $changedAt;

0 definitely doesn't look correct, was it ever working before?
There were some changes affecting CURRENT_TIMESTAMP, see https://github.com/doctrine/doctrine2/issues/6698 / https://github.com/doctrine/dbal/issues/2859, but those should be resolved as of DBAL 2.7.

@caciobanu: Thanks. Works like a charm.


Fix svg spacing

This UI change adds spacing between the svg icon and text in header and reduce the left/right padding to prevent the tabs from wrapping.
Before:

After:

Before:

After:

Codecov Report

Merging #14638 (d3ffa88) into master (ac97ea5) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #14638      +/-   ##
==========================================
- Coverage   42.21%   42.21%   -0.01%
==========================================
  Files         765      765
  Lines       81451    81451
==========================================
- Hits        34387    34384       -3
- Misses      41451    41457       +6
+ Partials     5613     5610       -3

Impacted Files
Coverage Δ

modules/util/timer.go
42.85% <0.00%> (-57.15%)
:arrow_down:

models/unit.go
46.57% <0.00%> (-2.74%)
:arrow_down:

modules/queue/workerpool.go
58.77% <0.00%> (-1.23%)
:arrow_down:

models/repo_list.go
77.87% <0.00%> (-0.89%)
:arrow_down:

services/pull/pull.go
42.15% <0.00%> (ø)

modules/git/batch_reader_nogogit.go
46.26% <0.00%> (+1.49%)
:arrow_up:

modules/git/repo_language_stats_nogogit.go
63.82% <0.00%> (+6.38%)
:arrow_up:

modules/indexer/stats/db.go
68.00% <0.00%> (+12.00%)
:arrow_up:

Continue to review full report at Codecov.

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

@kdumontnu  i don't see any visible changes on before/after comparison images here.

Have to agree with @bagasme there - it's not obvious what the problem you're fixing is here.

Have to agree with @bagasme there - it's not obvious what the problem you're fixing is here.

To be fair, it's a rather minor change. Added a short description above. The svgs should not be touching the text. This more closely matches how we style icons in other sections.

@kdumontnu can you "Update Branch" please :)

This has created some over-generalization issues. Take a look at the clone link panel on the repo page, for example, or the branch selector dropdown, which belong to the secondary menu class. Those child items are not direct children of the whole menu, but actually their own small menu class, and should obey their own rules.
So at least it should be > .svg to avoid recursion.
But again in your second example, on the top right corner, those children in the radio-style menu have also been affected by this. The spacing there was a lot smaller - though not necessarily optimal - and this change has made those gaps larger than expected.
Octicons were introduced in phases to replace FontAwesome, and are governed by different spacing strategies. Some are direct margins in stylesheets. Some are normal inline spacing with whitespace characters. Some are set with Flex boxes. The units are also a mix of em and px. And sometimes even overriding rules aren't made with such a general rule in mind, and might break as a result.
The icons of the top navbar (login, register, and dropdown items) are affected by this change, and has previously let me believe there was a design change in general (which I of course welcome, I very much appreciate your effort to fix these uniformity issues) and made the language switcher icon closer to the text in #14575. The dropdown menu itself now has one remaining FontAwesome icon that stands out as a result of this probably unintended override, which I thought was a miss, but turns out to be coincidental after all.
 I just want to make my points clear, in hope that this kind of mistakes would happen fewer in the future.
I believe the correct fix would be to go through a checklist of spacing issues to be fixed, implement them locally in their respective scopes, and finally try to generalize bit by bit. Since there aren't "unit tests" for this kind of stuff, a lot of testing should be done in the browser's inspector, with measurements taken. Note that rules seen as sourced from semantic.css might actually be a bug due to code tidying, refactoring and dependency updates - which is frustrating and takes a long time to find out (for example, those overly wide labels everywhere: they were styled to be narrower since way back at Gogs and only broke until recently).

@CL-Jeremy commenting on closed issues/PRs is a recipe for loosing comments to the ether, please open a new issue with these comments so that someone could follow up on them.


FDS-77 - Bump Next to the latest version

Hi team,
We are bumping Next to its latest release. This build will probably fail because we still need to merge FDS-76 - use the correct version of nodejs for vercel (12.x) for Vercel to pick the new config up.
Cheers

@lordpixel as part of this PR can we also see why the docs are failing? Vercel looks like it is good, so we just need to get CI working and this can come in.

@lordpixel as part of this PR can we also see why the docs are failing? Vercel looks like it is good, so we just need to get CI working and this can come in.


Ionic push message keeps in Queue status

Short description of the problem:
I am testing the ionic push on browser. I already set dev_push to true.
I am using this https://apps.ionic.io/app/787eb344/push/alpha/tools to send the push message in development mode.
What I get from checking message status is
{"errors":[],"ios":{"failure_reason":"","success":false,"sent":0},"status":"Queued","android":{"failure_reason":"","success":false,"sent":0},"app_id":"787eb344"}

It's been like more than 1 hr already. here is the message id 0eb20b08eded11e5a02b0e1560be0420
Which Ionic Version? 1.x or 2.x
1.x
Run ionic info from terminal/cmd prompt: (paste output below)

If the status stays at "Queued" you have an error on your push notification code, copy and paste the exactly example code that the plugin provides you, also try setting dev_push to false, set it to true when trying on a real device.

Thanks for opening this issue with us! As this issue is more related to the ionic platform and not the actual framework i will be moving this issue to the correct repo. Please feel free to move the conversation over there!

This issue was moved to driftyco/platform-client-node#2


Easee connection failure

Describe the bug
Does anyone else have problems with the Easee Wallbox today? I get lots of failure messages today when EVCC tries to send new Amperage limits to the Easee, just want to know if there is a common problem maybe with Easee servers or new config at Easee or if it is a problem with my installation (where I did not change anything since weeks and it worked until today)
Steps to reproduce
Every change on Limitation of Amperage creates an error

Configuration details
Not changed
Log details
Will send as soon as I am at home again
What type of operating system are you running?
Linux
Version
0.100

Timeout bei Easee, siehe https://github.com/evcc-io/evcc/discussions/4413


Circular dependency: brewer2mpl depends on ggplot

We had some trouble internally building ggplot, and eventually worked back to this being the issue:
https://github.com/conda-forge/ggplot-feedstock/blob/master/recipe/meta.yaml#L20
It's pretty crazy that ggplot requires all of these things as build-time dependencies.  I don't think it's necessarily ours to fix, but we should be wary of it.
CC @bryevdv

I think the next release won't need all those. See https://github.com/yhat/ggplot/commit/792e4294cd8ce820a307e1f66dc43c35ae16ce95

We could use that commit as a patch if it would make life easier.

@msarahan what version of ggplot are you building internally?

I was trying to build 0.9.4

I was trying to build 0.9.4

OK. That is the same we built. (The inconsistent, also fixed in that commit, is that __init__.py had 0.9.3.)

I vote apply as patch for now - but I'm unclear why we wouldn't have seen the same circular issue when the CI was running.

My guess would be that the older ggplot (perhaps from defaults) sufficed to
build brewer2mpl, which then allowed us to build this one.
On Mon, Jun 20, 2016 at 1:46 PM, Peter M. Landwehr<EMAIL_ADDRESS>
wrote:

I vote apply as patch for now - but I'm unclear why we wouldn't have seen
the same circular issue when the CI was running.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/ggplot-feedstock/issues/1#issuecomment-227232766,
or mute the thread
https://github.com/notifications/unsubscribe/AACV-U2lh99CuDyNoHv9D3dzflJ_2MDkks5qNuAHgaJpZM4I57Ho
.

My guess would be that the older ggplot (perhaps from defaults) sufficed to
build brewer2mpl

I don't think so. We did not specify ggplot as a dependency in the brewer2mpl recipe nor it was downloaded at build time. See https://travis-ci.org/conda-forge/brewer2mpl-feedstock/jobs/138134095#L377
I am guessing this is a re-herring. The run time dependencies are really not needed in ggplot, but that does not cause any harm here. Maybe you have another set of dependencies/versions there?

This is a non-issue at this point as we have passed the troublesome version, right?

Closing this. I no longer believe this is an issue. Please re-open if I am wrong.


Missing TICS Pro files used for ext clock progamming for ZCU111 (maybe other boards?)

Some older designs rely on 245.76MHz would it be possible to add this setting to the list of supported external clock freqs?
The 245.76MHz TICS PRO settings file for the LMX part is missing from here:
https://github.com/Xilinx/PYNQ/tree/master/sdbuild/packages/xrfclk/package/xrfclk
The SD image for PYNQ v2.7 also matches and does not have this file, only the following are present:
root@pynq:/usr/local/share/pynq-venv/lib/python3.8/site-packages/xrfclk# ll
total 64
drwxr-xr-x   3 root root  4096 Nov 18  2021 ./
drwxr-xr-x 236 root root 16384 Nov 18  2021 ../
-rw-r--r--   1 root root  1751 Nov 18  2021 __init__.py
-rw-r--r--   1 root root   386 Nov 18  2021 LMK04208_122.88.txt
-rw-r--r--   1 root root  1742 Nov 18  2021 LMK04832_122.88.txt
-rw-r--r--   1 root root  1472 Nov 18  2021 LMX2594_102.4.txt
-rw-r--r--   1 root root  1472 Nov 18  2021 LMX2594_204.8.txt
-rw-r--r--   1 root root  1472 Nov 18  2021 LMX2594_409.6.txt
-rw-r--r--   1 root root  1472 Nov 18  2021 LMX2594_737.0.txt
drwxr-xr-x   2 root root  4096 Nov 18  2021 __pycache__/
-rw-r--r--   1 root root  9944 Nov 18  2021 xrfclk.py
root@pynq:/usr/local/share/pynq-venv/lib/python3.8/site-packages/xrfclk#

Closing due to lack of activity. If this is still an issue re-open it as a [discuss.pynq.io](https://discuss.pynq.io/) post.


Simpified Chinese Translation Finished

Hi dev!
Just translated this project into Simpified Chinese.
Unfortunately, I currently do not have a Vue compile kit at my computer, so I chose the uglier way to present it to you.
chinesesimpified.zip
Thanks for this awesome project!

Thank you very much for this. Your translation is included.
Cheers!


ingestion example

examples writing pandas -> lance and also converting parquet -> lance

Lgtm overall, can you also add this to docs?
https://github.com/eto-ai/lance/blob/main/docs/howtos.rst


Not able to run benchmark test when dats source is S3

Which version of the AzCopy was used?
azcopy 10.18.0
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
azcopy benchmark "//?S3AccessKey=&S3SecretKey=" --duration 10m
What problem was encountered?
not able to get the result. I am migrating TB's of data using S3 need to run benchmark test.
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?

Hi @bharat149 ! Please try added --mode=Download to your command as seen here: https://learn.microsoft.com/en-us/azure/storage/common/storage-ref-azcopy-bench?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json

@siminsavani-msft we are testing benchmarking for upload part and by default --mode is set to upload that is why we have not added in the shared azcopy command

You cannot upload to S3 using AzCopy, only downloading S3 to Azure is supported.
If you are using Upload by default, you will want to include the destination.

azcopy bench [destination] [flags]

https://learn.microsoft.com/en-us/azure/storage/common/storage-ref-azcopy-bench?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json


Use xcodebuild directly when on Xcode 8

On Xcode 8, we'll just pass-through the output and check the error code of xcodebuild.

Hm. Do you say xcodebuild-shim doesn't work at all in Xcode 8?

To link dynamically against xcodebuild, we need to have a binary signed with certificate of Apple.
(It's complaining about Developer Team ID)

The build & tests passed!

+1 Yah, we have to remove xcodebuild-shim in Xcode 8.

fprintf(stdout, "%s\n", [line UTF8String]);

I don't like this at all =( This will break most of CIs which rely on custom reporters, for example. Let's better assert there and let users know why it is done and how to resolve the issue.

Other alternative is to use new -json option of xcodebuild, parse results in xctool and reformat for our own reporters format. But I think we should just stop supporting build features in xctool.


Unbound local error when not defining '--model-file'

seems like there could be a bug that requires the use of --model-file rather than it be Optional.
When I pass in --model-file the program runs.
fastapi_code_generator/__main__.py", line 33, in main
    return generate_code(input_name, input_text, output_dir, template_dir, model_path)
UnboundLocalError: local variable 'model_path' referenced before assignment

This can be closed with #223


collection.count is ignoring options

on monk 3.1.1, doing collection.count({},{limit:7}, function(err, count){
returns the total number of documents in collections, while it should return 7. seems the options is ignored.

fix by 55c2aaddd1bb6446c1aa8883fef935129f787123


Torg Eternity sheet - Bugfix for Multi-Actions

Submission Checklist
Required

[x ] The pull request title clearly contains the name of the sheet I am editing.
[x ] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x ] The pull request makes changes to files in only one sub-folder.
[ ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

There was a bug in the roll makro for the chat buttons for possibility and up in multi-action rolls. This bug is fixed and the buttons should work as intended now

Character Sheet Info Roll20 Internal Use only.


I am writing a native Angular application for this as well

Using the React code as a baseline I am writing a version of this code that uses everything Angular rather than requesting an image from the website.
I have currently added the ability to create an avatar and custom the body color, and the shirt type.
As I progress in writing this Angular module I will update this issue with a github repo for anyone that is looking to create an Angular app with this.

Nice. I'd be interested in using this. Let me know if you need any help

I am essentially do what the react components do and add svg files together to generate a complete svg tag

@BaileyMillerSSI  @fangpenlin  @gkoberger  @weisisheng I have also tried to cloned this website for creating avtaars in native angular and angular material, and mainly for open project work, should i keep working and  deploy it or It can be a copyright issue to do so. I must add that this is just for project work only.

Any updates?


Bloom Not Seeing Database

I am having recent connection issues.
Database 4.4.8 which was previously working fine
Open in Bloom and perspective is empty and no option to generate one.
Also Noticing trouble connecting via Desktop Browser.  Open the database via open button and it does not connect.
I need to use the connect server button and it is using port 11003 instead of the normal 7687 port.
Also if I close the browser and reopen I also have to reconnect via different port connection.
I think this also may have occurred when the python driver was upgraded to version 5.

Version
4.4.8

Edition
enterprise

Status
Active

IP address
localhost

Bolt port
11003

HTTP port
11004

HTTPS port
7473

Andy

hi, it looks like a connection issue, but we are investigating it. Meanwhile, could you check your logs if an error message indicates any issues on binding to the port?

I am also running into this running a local instance of 5.8 using ports 7687 and 7474.
I had just installed a new version of the Bloom app.
I tried forcing a reinstall of Bloom, but that didn't change anything.
Sometimes Bloom will load the default database no problem, and usually if I reload Bloom it will tell me that there is no active DB. I can't find errors on the Neo4j Desktop side. When it does load, under perspectives it behaves normally for the default DB, but I cannot switch to my other DB.
I also spun up a new 5.8 DBMS to test there, same results.
Message in Bloom after a reload:

We couldn't find an active graph in Neo4j Desktop. Please check that you have connected to a graph.

I will be closing this issue since it's been some time since the last reply. If you have any issues with Bloom, please feel free to raise a new issue here or on Canny https://neo4j-aura.canny.io/explore


Fix/enum return types and query params

fix #588 and #591
not 100% sure that dartType.element is EnumElement is the best way to check if a type is an enum (dartType.isDartCoreEnum does not work in this case). Just let me know if there's another way please.
edit: i also found the open issues  #559 and #536 that would be fixed by this pr

Great work. Thanks for the contribution.

Hi, I have a question about this.
How should I use the json value on the query parameter after the change?
Thanks.

Hi, I have a question about this. How should I use the json value on the query parameter after the change? Thanks.

Hi, I'm not sure I got your question, I'll try to explain then if you still have doubts feel free to ask.
The only difference is how the enum is serialized and deserialized, it should not impact your use of the retrofit generated classes.
 This is unnecessary since Dart offers Enum.name which automatically gives you the string corresponding to your enum value.
When converting back string values to its corresponding enum value instead, there was a bug in retrofit_generation (now fixed by this pr) and .fromJson method was called on enums in order to deserialize them. In that situation, what is done now is iterating through enum values, until one with the same name as the string you want to convert to enum is found. Otherwise it just throws an error.
Don't know if this clarifies your doubts

My question has been resolved with #596, thanks a lot.