Landing Page: Test/Fix Responsive Design

Ensure that page looks ok on super widescreen monitors.
Test page on mobile's and slim width laptop windows
Optimize page

For all of this stuff, we can use online tools to help us test.

It's good enough for now. :)


python37Packages.zc_lockfile: 1.3.0 -> 1.4

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-zc.lockfile/versions.
meta.description for python37Packages.zc_lockfile is: '"Inter-process locks"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.4 with grep in /nix/store/47d0v019iysdf2wvh3fr899g53fsrhnd-python3.7-zc.lockfile-1.4

directory tree listing: https://gist.github.com/457682e9ef6e0872d550b47c9f7b61e8

du listing: https://gist.github.com/cb50cd8f7ba68c27d842006187127000

Rebuild report (if merged into master) (click to expand)

36 total rebuild path(s)
9 package rebuild(s)
9 x86_64-linux rebuild(s)
9 i686-linux rebuild(s)
9 x86_64-darwin rebuild(s)
9 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
flexget
mnemosyne
python27Packages.zc_lockfile
python27Packages.zodb
python37Packages.cherrypy
python37Packages.zc_lockfile
python37Packages.zerobin
python37Packages.zodb
vulnix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/47d0v019iysdf2wvh3fr899g53fsrhnd-python3.7-zc.lockfile-1.4 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python37Packages.zc_lockfile https://github.com/r-ryantm/nixpkgs/archive/2651bf40673e95501771b13ac97e9731ea6ef6e0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/47d0v019iysdf2wvh3fr899g53fsrhnd-python3.7-zc.lockfile-1.4
ls -la /nix/store/47d0v019iysdf2wvh3fr899g53fsrhnd-python3.7-zc.lockfile-1.4/bin

cc @cillianderoiste for testing.

@GrahamcOfBorg build python27Packages.zodb python37Packages.cherrypy python37Packages.zc_lockfile python37Packages.zerobin python37Packages.zodb flexget
mnemosyne vulnix

@GrahamcOfBorg build mnemosyne vulnix python2Packages.zc_lockfile python37Packages.zodb python27Packages.zodb
Ignoring python37Packages.zerobin because it's already broken https://hydra.nixos.org/build/86429018 because of clize. Think I can fix that quick anyway.

@GrahamcOfBorg build python37Packages.zerobin pythonPackages.zerobin


RelationalLogger logs differently on different cultures

In particular parameter values, which makes some Asserts brittle - PR in the works, that avoids dependency on Mirosoft.AspNet.Testing

Merged


Sp schedule feature

PR summary

Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Commit Message Guidelines in the CONTRIBUTING.md.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

@subhpa01 this looks now, but can you please update the role so it matches what is done in the node role


Outdated API

It looks like this package cannot currently obtian the IP and port of a realm. The endpoint for that on the realms API seems to have moved to /worlds/v1/$ID/join/pc. This seems like a relatively simple fix of refactoring some of the API interaction. I'd be happy to make a PR if I find the time.

It looks like this package cannot currently obtian the IP and port of a realm. The endpoint for that on the realms API seems to have moved to /worlds/v1/$ID/join/pc. This seems like a relatively simple fix of refactoring some of the API interaction. I'd be happy to make a PR if I find the time.

The endpoint you provided /worlds/v1/$ID/join/pc is the same endpoint as mc-realms is currently using, so I am not quite sure what your point is.  I also do not use realms any more so I will not be updating this at any time in the near future; however, feel free to clone this repo and update whatever you need.

Sorry, that's completely my bad! I had misread the errors I was getting. Apologies for the mix up. Thanks for the info on the future of this project.


Add helpers to stringify coins

I have this in some contracts to produce events. Maybe this would be a useful helper in cosmwasm_std?
#[inline]
fn coin_to_string(coin: &Coin) -> String {
    format!("{} {}", c.amount, c.denom)
}

fn coins_to_string(coins: &[Coin]) -> String {
    let strings: Vec<_> = coins
        .iter()
        .map(coin_to_string)
        .collect();
    strings.join(",")
}

The first one looks like a very good candidate for a Display implementation of Coin.
For the second one I'd rather wait for https://doc.rust-lang.org/std/slice/trait.Join.html, which can cover the boilerplate. The separator is mostly caller specific I think. For human readable outputs you'd susually prefer ", ".

The separator is mostly caller specific I think. For human readable outputs you'd susually prefer ", ".

Given that this is amount and denom, " " makes sense as a separator, i.e. 1 ATOM.

Given that this is amount and denom, " " makes sense as a separator, i.e. 1 ATOM.

Right. I'm referring to the element separator in coins_to_string

But even for a Coin I'm not sure anymore. They are written as<PHONE_NUMBER>4uatom without space in many other places in the Cosmos ecosystem. Do we want<PHONE_NUMBER>4 uatom for a CosmWasm Coin?

If that's a "standard", I guess sticking to it makes sense.

Creating a coin denom that starts with numbers (i.e 00coin) may confuse some parsers. I guess this is just for logging / display. So, no big deal.

Looking at https://github.com/cosmos/cosmos-sdk/blob/master/types/coin.go we seem to get "guarantee" that the denom does not start with a digit. Also note Expected format: "{amount}{denomination}" and Expected format: "{amount0}{denomination},...,{amountN}{denominationN}" for the parsers. I guess it helps to align with that.

I agree with implementing Display for Coin. Ideally using something equivalent to format!("{} {}", c.amount, c.denom) (I had it without space until Mauro's PR comment - I agree it looks nice his way, but sticking with sdk standard is good.

I'm thinking about the second part again. We could add and maintain it here. This gives us the opportunity to optimize the implementation in a way that you don't want every contract developer to be aware of. Collecting into Vec<String> and using join created n+1 heap cllocated strings. Of we implement it via a loop utilizing Display, we only need a single string. See https://stackoverflow.com/questions/28333612/how-can-i-append-a-formatted-string-to-an-existing-string

Good point with optimization.
But after updating the contracts, I realized that in practice we only ever have one coin, so coin.to_string() is plenty.
Happy if you want to add it, but it seems not so important as impl Display for Coin (which also gives a standard format)

An optimized version is here:
/// Creates a comma separated string representation of the Display representation of the coins.
///
/// E.g. "" for the empty list, "123ustake" for a single element list and "123ucosm,8910ustake" for two elements.
pub fn coins_to_string(coins: &[Coin]) -> String {
    let separators = coins.len().saturating_sub(1);
    let mut out = String::with_capacity(coins.len() * 20 + separators);
    let mut first = true;
    for coin in coins {
        if !first {
            out.push(',');
        } else {
            first = false;
        }
        write!(out, "{}", coin).unwrap(); // See https://stackoverflow.com/a/28333723/2013738 for why unwrap is okay
    }
    out
}

However, the smaller the API the better. We have to maintain this stuff basically forever. If we don't need it, let's not add it.


Use friendly exception on get non exist default roles

https://github.com/yiisoft/rbac/blob/3e8562574952925c827a25ffdd0fe186d2985377/src/Manager.php#L464
We can explain that default roles should be added before using as default.

I'll take it


parse datapacks for their name

Parse all enabled datapacks for their real name (not the filename). Put all found datapacks in a list in WorldInfo, support zipped and unzipped storage. Can be used to query whether a specific datapack is used in that world.
Refactored Custom Dimension parsing into the same code.
Example usage:
Just call e.g. WorldInfo::isDatapackEnabled("Chunklock") to query if the datapack (in this case "Chunklock") is used.

Does this work for server worlds, too? Are the folders the same?

Yes, in (downloaded) server worlds it is the same.


GH workflows with newest Ruby versions

The actual workflow is only testing ruby 2.6 and 2.7. We should add the following 3.0 to 3.2 and probably truffle-ruby, jruby.

Fix with #91


TypeError in Event Handler on Chrome Extension Post-Update

After a recent update, I encountered the following error in a Chrome extension:
Error in event handler: TypeError: Cannot read properties of undefined (reading '0') at chrome-extension://mjfblbggcgffnijgopjiocacoajgnjak/service_worker.js:1:277 at Array.forEach (<anonymous>) at chrome-extension://mjfblbggcgffnijgopjiocacoajgnjak/service_worker.js:1:259

I see, I updated the model to gpt-4 so some users are getting this error because they only have key for 3.5
I will add a feature for selecting model

You can change the model and API server in options page now.


PDFs in the /pdf directory are all invalid 15 byte files

I updated the PDFs. They aren't perfect yet but at least they aren't dead files!
https://github.com/JNPRAutomate/JNPRAutomateDemo-Class/releases/tag/v1.2

Looks good and I also concatenated them all into a single file
https://github.com/JNPRAutomate/JNPRAutomateDemo-Class/releases/tag/v1.3


Rendered picture is still on the screen after exiting rnvimr

nvim --version:v0.4.4
Operating system/version: 5.8.18-1-MANJARO
nvim +'checkhealth rnvimr':

## OS
  - OK: Name: Linux

## Ranger
  - OK: Version: ranger-master

## Python
  - OK: Version: 3.8.6 (default, Sep 30 2020, 04:00:38) [GCC 10.2.0]

## Pynvim
  - OK: Version: 0.4.2

## Ueberzug (optional)
  - OK: Ueberzug is ready

## RPC
  - OK: RPC echo: Neovim send "Give me five!" and receive "Give me five!"

Describe the bug
A clear and concise description of what the bug is.
Ranger rendered picture still on the screen after exiting rnvimr
Steps to reproduce the behavior:

open nvim using nvim
toggle rnvimr
using ranger browsing and previewing your images
toggle rnvimr

Expected behavior
The rendered image should also be closed after toggle rnvimr
Screenshots

Thanks for your feedback, I'm knowing this issue, but not sure someone cares about this. I will fix it later.

Update the plugin will fix the issue.

Thank you for your so quick response!
I also think it's not a big deal.


Issue110

Added OracleLinux support in packages.pp, also updated the fail messages. The existing test was also updated in gitlab_spec.rb.
The changes in install.pp ensure that the install package for Centos is downloaded (there is no separate OracleLinux install package). Only works for Gitlab version 7.4.3 and lower (see #100).

Thanks for the merge request. This looks really good.
This needs to be added to the readme and the changlog, but I'll do that myself.


Set Up Integration Suite Trial - Booster is failing - US region

Tutorials: https://developers.sap.com/tutorials/cp-starter-isuite-onboard-subscribe.html
Hello,
Step 4: Automatically assign roles and create service instances using Booster
In this step, the booster is failing in the US region saying the Integration suite service is not subscribed.
Even though the service is subscribed and capabilities are also added.
please check the issue.

Thanks,
Shubham
Labels to be added:
prior - HIGH-prio
Sprint Label: SCPTest-2204A
Scenario label: SCPTest-cloudin
Landscape: trial2 (US)

Hello @i353590 , @MamathaKH , @AnnikaGonnermann
Thanks for the patience and apologies for the long delay. There were issues in the Integration Suite trial offerings which are resolved now. You shouldn't be facing this issue anymore.
Regards,
Karuna


fix(@angular/build): force HTTP/1.1 in dev-server SSR with SSL

When server-side rendering (SSR) is enabled with SSL and Express, Vite must use HTTP/1.1 because Express does not support HTTP/2. This is achieved by setting an empty proxy configuration.
Reference: https://github.com/vitejs/vite/blob/c4b532cc900bf988073583511f57bd581755d5e3/packages/vite/src/node/http.ts#L106
Closes #29142

The changes were merged into the following branches: main, 19.0.x


Reconcile refactoring of main/geo.js with recent changes

This is a port of the changes from #1 (which I didn't see because I disabled auto-follow of new projects1 😳 and the code it they relied on went through substantial changes)
cc @cabello
1seems silly, but try joining an organization with a bazillion repos and auto-watch all of them for just a few minutes... 😆

LGTM 🚀


[Storage] Rollup for tests in storage

Update rollup-config as per the template.
Rollup for both the node and browser tests
Updated test:node command to use the generated dist-test/index.node.js instead of running ts-node on the test files.

"test:node": "cross-env TS_NODE_COMPILER_OPTIONS="{\"module\": \"commonjs\"}" nyc mocha --compilers ts-node/register --require source-map-support/register --reporter mocha-multi-reporters --reporter-options configFile=mocha.reporter.config.json --full-trace --no-timeouts test/*.test.ts test/node/*.test.ts",

updated to

"test:node": "mocha --reporter mocha-multi-reporters --reporter-options configFile=mocha.reporter.config.json -t 120000 dist-test/index.node.js",

Minor changes to rollup.base.config.js to get rollup working.
Restructured commands in package.json.
Renamed test files for consistency across packages.

@HarshaNalluru Will coverage report still work for Node.js test after this update?

@HarshaNalluru Will coverage report still work for Node.js test after this update?

Thanks for asking.
Something is wrong with the coverage for node tests. I'm looking into it.


[Adding Tool]: Fullstack.cafe for preparing for tech interviews :)

What tool are you adding and to what category?
We need to add Fullstack.cafe for preparation for tech interviews.
i want to add this resource assign it to me under Gssoc2023!!!
Add Tool Link
Add tool link fullstack.cafe. Most of the questions are provided free and can be downloaded via pdf.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] The tool is free for use

@Ujjwal-soni98 , is this free

many questions are free to view over many tech stacks and save them as pdf. but some of the questions are paid also. so can't say that it is completely free.

@JasonDsouza212  please add GSSoC23 tag in this.

GSSoC program is going to end so please add it sooner, i am having my exams right now so cannot look to contribute to any new issue  :)


Allow use of sources as unit testing inputs

resolves #8507
Problem
We want to support the use of sources as inputs in unit test cases.
Solution
Created a UnitTestSourceDefinition object, which acts as a source for purposes of resolving "source" calls, but acts as a model for purpose of executing the test case.
Checklist

[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
[x] This PR includes type annotations for new and modified functions

I looked at taking out the special casing of UnitTestSourceDefinition, but unfortunately there are subtle differences in the specification of quoting between sources and models, and so I think it's best to actually use the relation.create_from_source to get the quoting right.


k8s service headless support

Is your feature request related to a problem? Please describe.
When I create an hdfs cluster, I want to access it through a headless service.
For example, I created a service like this:
kubectl get svc
NAME               TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)    AGE
kubernetes         ClusterIP   <IP_ADDRESS>   <none>        443/TCP    16m
namenode-service   ClusterIP   None              <none>        9870/TCP   12m
datanode-service   ClusterIP   None              <none>        <none>     9m17s

kubectl get pod
NAME         READY   STATUS    RESTARTS   AGE
namenode-0   1/1     Running   0          21m
datanode-0   1/1     Running   0          18m
datanode-1   1/1     Running   0          17m
datanode-2   1/1     Running   0          17m

I want to access the namenode through namenode-service or view it through the webui.
such as namenode-service:9870.
When I want to see the datanode, internal addresses are usually http://datanode-0.datanode-service.default.svc.cluster.local:9864 but cannot access.
So, I have to modify the hosts file myself to solve the problem?
Thanks！
Describe the solution you'd like
Supports k8s Headless service name routing
Describe alternatives you've considered
No
Additional context
No

Added for the next version.

Released in v1.3.0 Canary 1.

Released in v1.3.0.


ubuntu 20.04.2 and bind9 vs named

Hello here
thank for you work
I'm not sure what I'm saying but it's look like on ubuntu20.04 the default file for bind is /etc/default/named not /etc/default/bind9
that's mean the "-4" option is not applied and the NSD failed to install because udp6:53 is used by bind9
I'm trying from a fresh ubuntu install but I don't understand why I'm the only one with this issue,
Thanks

hi! (and sorry for the delay 😅)
a little bit of network background: ip's are bound to interfaces. So your local addresses are bound to an interface, your public address(es) (that are used to communicate to the world) are bound to another interface.
We want named (or bind9) to bind to the private addresses (<IP_ADDRESS> and ::1) while nsd binds to the public addresses.
Likely the issue here is that in your ubuntu image, bind9 was already bound to the public addresses. The following will possibly solve your issue - but do not do this if you already have MiaB installed, as it will bring the box down for a bit;
sudo apt remove --purge --autoremove bind9
echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf

then run the setup as usual, then after it:
echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf

Hello David thanks for you reply but I wasn't very clear I'm sorry my bad! :) (my english is bad sorry for that)
Yes I know but what i mean is in the file
setup/system.sh line 309
you add "-4" to file /etc/default/bind9
but What i understand it's on Ubuntu 20.04 the file should be
/etc/default/named (not /etc/default/bind9)
(/etc/default/bind9 is not used anymore at the named startup)

Alright, got it. Managed to grab a case where not configuring /etc/default/named could cause problems.
I'm probably going to push an update soon that will write to both files (/etc/default/bind9 and /etc/default/named) as I'm not sure how this works on Debian.

A little bit late but finally got around to deploy a fix: https://github.com/ddavness/power-mailinabox/releases/tag/v0.54.POWER.4
See if it works now? :)


Updated the structure of template

added poetry
updated pre-commit
added sample pytest case
updated README & LICENSE
setup flake8, black, isort etc.
removed unwanted files

# Whitespace Before
E203
``` We can add this to `tox.ini`


integrated terminal colors are off (git-bash.exe)

Version: 1.43.2
Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
Date: 2020-03-24T07:38:38.248Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Steps to Reproduce:

install vscode (default dark+ theme, "terminal.integrated.minimumContrastRatio": 1,)
"terminal.integrated.shell.windows": "C:\git-bash\bin\bash.exe",
open integrated terminal ➡ colors are kinda off
😕

Does this issue occur when all extensions are disabled?: Yes/

The colors are defined by the theme. You can also change them to whatever you want in settings like this:
"workbench.colorCustomizations": {
    "terminal.ansiBlack": "#000000",
    // ...
}


The list of component records is not valid.

I use two blazor components in _layout.cshtml as follows, but the components don't work.
// _layout.cshtml
@(await Html.RenderComponentAsync<Counter>(RenderMode.ServerPrerendered))

    @RenderBody()

// Test.cshtml
@page
@model Web.Pages.TestModel
@(await Html.RenderComponentAsync<Counter>(RenderMode.ServerPrerendered))

But, It works if the component is used after @RenderBody() as follows.

    @RenderBody()

@(await Html.RenderComponentAsync<Counter>(RenderMode.ServerPrerendered))

@asdux Thanks for contacting us.
This might be an issue in the way we store the component sequence numbers in the ViewContext. We'll have to check that the data in the ViewContext gets copied properly.

Closing as dup of https://github.com/aspnet/AspNetCore/issues/14474. We'll use the other issue to track resolving this.


Git LFS feature fails to build on Linux/ARM64

Will update as I get more info, but was able to build things recently and now all ARM image builds are failing.
This was noticed running the devcontainer command. I attempted to reproduce this with a minimal tester devcontainer and was successful in doing so.
Steps to Reproduce:

Add "git-lfs": "latest" to the features definition
Build for linux/arm64 using the devcontainer cli

Error message:
[19231 ms] ------
 > [stage-0 3/3] RUN cd /tmp/build-features/local-cache && chmod +x ./install.sh && ./install.sh:
...
#13 13.36 git-lfs-linux-arm64-v3.2.0.tar.gz: OK
#13 13.72 ./git-lfs-debian.sh: line 163: ./install.sh: No such file or directory

Base image:
FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
In case that's relevant

This sounds like the issue, as mentioned in the linked issue for git-lfs:

we now ship our tarballs such that all files are in a top-level directory, since the old way of doing things is called a tarbomb and is generally undesirable.

The workaround is to use the version prior
"features": { "git-lfs": "3.1.4" }

@joshspicer, @samruddhikhandale

Thanks for the report!  What base docker image are you using (is it based on ubuntu 22.04 jammy)?

Reproduces with jammy (eg repo: https://github.com/codspace/git-lfs-jammy/tree/main)

Hey! This should be all fixed in the PR above - thanks for the report.  Note that it'll take a few days for the cached copies of this feature to land in CLI/Codespaces/Remote-Containers.
If you'd like to use this feature in the interim, you could try out our preview syntax to remotely reference the feature:
"features": {
<EMAIL_ADDRESS>"latest"
}


Is this project a dead one?

It looks like this repository hasn't been updated in a year or more, yet there is activity in terms of issues and pull requests.
Should this project for forked to an active one that keeps up with GTK3 developments?

Development continues over at https://github.com/gotk3/gotk3 but it's no longer being developed by Conformal.

Aha, already forked. I had missed that. Thanks for letting me know. Appropriate action now being taken. :-)


Fails to kill discord: powershell.exe not on PATH

BetterDiscord Installer stuck in loop
Installer stuck in a loop if Powershell is not set in the environment variable.
To Reproduce
Steps to reproduce the behavior:

Remove Powershell  from to environment variable.
Run the installer till it reaches Attempting to kill Discord.

Expected behavior
Installer doesn't do anything after reaching  Attempting to kill Discord.
Screenshots

System Information:

OS: Windows 11 Version 22H2
Discord Version: Stable 183813 (7a19dec)

Suggestion

Letting the user know about this issue.
This issue can be fixed by checking if Powershell is in their path, if not  logging the error.
This issue has somewhat been fixed in my version.

This is ultimately an issue with one of our dependencies, but we can definitely handle it more gracefully.

can confirm this was still an issue for me with installer 1.3.0.
When i added "C:\Windows\System32\WindowsPowerShell\v1.0" to my PATH it started to work like advertised. but it took me a LONG long time to find this about it's being due to missing powershell PATH.
Also allegedly even if system32 is in PATH windows have issues finding stuff in it's own subfolders which i found here: https://confluence.atlassian.com/bamkb/powershell-is-not-recognized-as-an-internal-or-external-command-1095246216.html#:~:text=It's%20usually%20located%20at%20C,the%20executable%20within%20its%20subfolders.

I also just had this problem and adding the path variable fixed it for me, would be nice if there could be some error displayed.


Update security at metamask email everywhere

We have a number of places on the website that point to<EMAIL_ADDRESS>We're going to be disabling that address and would like to replace all instances of it with<EMAIL_ADDRESS>

Can I work on this issue?

Hi @spiritanand ,
This work has been completed in ticket https://github.com/ConsenSys/dx-team/issues/1377 . Let me know if there is further work, we can re-open the ticket...

So will this issue be closed soon?

Closed :)On Jan 30, 2023, at 1:11 PM, Suryansh Anand @.***> wrote:
So will this issue be closed soon?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>


Integration Test - Release - 2019/06/17 23:57:46

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#reassign PRMergerTest2

GitHub user PRMergerTest1 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#reassign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#please-close


Remove "Back" button on Dao Core screen

Back will be not visible if opened using dao core button.

Checked


Green area.

Good day!
Beautiful project, I'm trying to run in сolab on my video and get unsatisfactory results, I guess because of the low quality of the picture + bad road markings, isn't it?
What does the green area on the picture mean?

Dear Moshe,
Thank you for your interest in our project.
The green area indicates crosswalks on the street. We used classic computer vision algorithms used for this particular task, and the thresholds are hand-chosen. Therefore, it's not robust against low-quality images. We are, however, trying to fix that in near future.

One little thing, notice that in PINet.py, in the description of the LaneDetection() class, in the Testing(self, frame, mask) function there is an unpleasant line: ti[0] = cv2.resize(ti[0], (1280,720)).
If we run on a video with a different size, there will be an AssertationError somewhere in the mask overlay process.
Good luck!

@MosheMikhael Thanks for noticing the issue and telling us about it, we will soon work on fixing the issues you mentioned.

Dear @MosheMikhael,
I added a quick fix to the assertion error problem you mentioned.
Thank you for your feedback.


[Masthead] Focus goes to the hidden element - DDS Consulting

Detailed description
Issue:
Doing tab key from IBM logo focus goes to the menu items which is hidden because of the open search edit field.
Expected:
Doing tab key navigation from the IBM logo focus should go to the open search field, not on the hidden menu items.
Additional information

Hybrid Cloud developer:
HC Jira ticket:
DDS consultant:

@Praveen-sr Can you provide a video screenshot of the issue you're seeing? Thanks!

@Praveen-sr not able to replicate this, could you re-test?

@Praveen-sr has re-tested and is not able to reproduce anymore - will close this ticket.


Map Message Structure

Tutorial URL: https://developers.sap.com/tutorials/cp-integration-convert-message-structure.html
Please specify the step you are referring to
the path was not found https://sap-my.sharepoint.com/:u:/p/meghna_shishodiya/EaqbQ9t0jGFMvSzYPnowpVABk4l6mnN50prkKIAez1UMYA?e=lsrj63

The links are updated now.

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


WIP: Scan stake pool registrations during wallet restoration.

:construction:
Issue Number
#899
Overview

[ ] I have ...

Comments

@jonathanknowles why is this one still a draft + WIP ?
Also, the PR description is somewhat ... missing :grimacing:
Is it actually ready for review, what are the next steps?

@jonathanknowles why is this one still a draft + WIP ?

Because I had put this on hold (temporarily) to work on other things. (Namely: PR #1057).

Also, the PR description is somewhat ... missing

Understood. I'll update this shortly.

Is it actually ready for review.

Not yet.

what are the next steps?

Three things:

To adjust the definition of applyBlock to identify delegations relevant to the specified wallet, and return the final registration as part of ApplyBlockResult.
To adjust the definition of restoreBlocks so that it correctly processes the registrations returned by applyBlocks.
Tests for the above.

I've noted a quite important change to do when storing the delegation after discovery, but I'll make it another PR to keep this one concise. It doesn't affect the core functionality, but is important in terms of reliability and data consistency.

bors r+

bors r+


Add "source" value to tiled::Tileset to allow additional functionality.

I was using this library to load map data for my game, and came across an issue. That issue being that tiled::Image::source is a path relative to the path of the tile set it belongs to. As such, trying to load images referenced in an external tile set results in errors. To fix this, I've added a "source" value to tiled::Tileset so that one could do
for tset in map.tilesets.iter() {
    for img in tset.images.iter() {
        let mut image_file = File::open(Path::new(tset.source).join(img.source);
    }
}

However, I'm not quite sure what should be used in the case of directly loading a tileset, so one of the 7 tests fail ("" is used as a fallback).

I have the same issue, see #94

Added in #106.


UI Lag when book is being parsed

The reader works great when parsing english epubs, but when it comes to different languages like hindi and tamil, UI gets stuck while parsing. There is an initial UI lag when reader is being instantiated. But even after the content is loaded and I scroll fast to bottom,  UI gets stuck for a while. Also, if I scroll to top, the book cover gets elongated for some reason. Is there a way to show an activity indicator while parsing is in progress??
You can try this book to test UI lag.
tamil book sample

I have tested it, I will take a look..

This should be fixed.


nixos/bookstack: Improve configuration handling and fix issues

Motivation for this change
Improve the configuration handling in the BookStack module and solve a few issues which prevented me from deploying it:

Replace the services.bookstack.extraConfig option with services.bookstack.config
services.bookstack.config implements a settings-style configuration interface. It's able to handle arbitrary secrets and doesn't suffer from the unescaping issues that the old one did.

Clear the cache more reliably
When upgrading bookstack, if something in the cache conflicts with the new installation, the artisan commands might fail. To solve this, make the cache lifetime bound to the setup service. Also, remove the cacheDir option, since the path is now handled automatically by systemd.

Make the hostname configurable and set a reasonable default appURL based on it
This is pretty much required when configuring ACME, and useful in general.

Simplify the nginx setup
Use the recommended defaults and remove unnecessary configuration.

Things done

Deployed manually to test systems
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

[ ] 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/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[x] (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
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Sorry for taking a bit longer to respond, but I wanted to wait to have a chance to try this in my setup.
Seems to be working perfectly fine. Thanks for your great work!

Wait, I do have one question: should we prefix base64: to the appkey by default? Then we could remove that line from documentation and it feels "cleaner".

@ymarkus Sure! I've changed the code to check for base64: at the beginning of the value and append it if it's missing.


Prometheus Monitoring Mixin for etcd.

This PR contains a set of Prometheus alerts for etcd, based on a new format for distributing reusable, customisable alerts called "monitoring mixins".
The mixin is based on the existing alerts in the repo; this format more flexible that as it allows users to customer the selectors used in the alerts.  Coupled with the new package manager, users can contribute to and easily stay up to date with alert definitions.  I suggest we remove the existing alerts and include instructions to generate them from the mixin.  WDYT?
See https://docs.google.com/document/d/1A9xvzwqnFVSOZ5fD3blKODXfsat5fg6ZhnKu9LK3lB4/edit# for more details on the format.
/cc @brancz

lgtm

I suggest we remove the existing alerts and include instructions to generate them from the mixin. WDYT?

I'm wondering if for some backward compatibility we should generate the yaml in this repo from this jsonnet?

I'm wondering if for some backward compatibility we should generate the yaml in this repo from this jsonnet?

Indeed! Thats what I'm suggesting.

@jdbaldry can I get a 👍 on this please?

@tomwilkie Thanks for contribution. Could you squash two commits into one and reformat the git commit title to something like Documentation: ...? Thanks!

The Travis failure just seems to be a timeout, which I doubt is related.

The Travis failure just seems to be a timeout, which I doubt is related.

Agreed. @gyuho can probably say best.
The file descriptor alerts are missing from this set, which is a not uncommon outage. I think they're worth having, or have you made other experiences (happy to change the default thresholds and range queries if necessary)?
I can take care of the dashboard as a follow up.

have you made other experiences

Nope, don't know why they're missing.  Let me have a look.

This lgtm :+1: thanks a lot for your effort @tomwilkie !

@gyuho now it’s up to you :) (probably just squash both commits into one if you want to merge)


[php ext] bad reported version

From pecl package
$ php  --re grpc | head -1
Extension [ <persistent> extension #15 grpc version 0.1.0 ] {

Should be 1.2.0 (or whatever next version will be)

we should also update PHP_GRPC_VERSION in php_grpc.h file.

Notice, things are better, but not perfect ;)
Version 1.4.0RC1 reports as 1.4.0...

I see. Will fix.


Fix filenames for case-sensitive filesystems

Make the extension work on operating systems with case sensitive file system (such as Linux)

Brilliant! Many thanks, thought I fixed all of these in #19


Stop write warning in redisb if no keys configuration

Hi!
redisdb integration supports keys configuration setting to collect length of Redis keys.
But if I am not interested in this functionality – my check becomes WARNING state because of this https://github.com/DataDog/integrations-core/blob/master/redisdb/datadog_checks/redisdb/redisdb.py#L248.
My redisdb check shouldn't become WARNING if don't use keys.
See https://github.com/DataDog/integrations-core/commit/bb4e550980d803228b5468455260ad9bf0cbfb28, previously there was guard if
/notify @masci @ofek

Should be fixed by https://github.com/DataDog/integrations-core/pull/4641 from 4 days ago.

You can update the integration by using sudo -u dd-agent datadog-agent integration install datadog-redisdb==1.12.2 (more info on this command here https://www.datadoghq.com/blog/agent-integration-management/)
It will be also included in the next release of the agent 6.15.

Hi @xkrt did this resolve your issue?

@agottlie yes, thx!

I had the same issue on v6.14.0 I confim that bumping to v6.15.1 fixed it. Thanks!

Thanks everyone!


Make tests work after the changes introduced in #3793

lgtm other than the unnecessary dependency. but why didn't you push this directly to your branch?

I wanted to ping Jim about this without DM-ing him about the changes.


[snap] Expose mongoimport as an app

Allowing access to mongoimport allows easy import of
Blackbox test data required to run blackbox tests.
Signed-off-by: Tony Espy<EMAIL_ADDRESS>

recheck

@tsconn23 @JPWKU @jpwhitemn can we override the docs-verify check for this PR? We want to get this into california ASAP, and this change doesn't do anything with the docs.
Also, the docs-verify job for california has been failing for a few days now: https://jenkins.edgexfoundry.org/job/edgex-go-docs-california-verify-docs/

recheck

recheck


Update zio, zio-test, zio-test-sbt to 2.0.0-RC1

Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.0.0-M6-2 to 2.0.0-RC1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Codecov Report

Merging #175 (385bc17) into master (8588fd0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #175   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           41        41
=========================================
  Hits            41        41

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 8588fd0...385bc17. Read the comment docs.


Can I have the protocols only in a category

Let's say my model is something like this:
@interface ProductModel : JSONModel
@property (assign, nonatomic) int id;
@property (strong, nonatomic) NSString<Optional>* name;
@property (assign, nonatomic) float price;
@property (strong, nonatomic) NSNumber<Optional>* uuid;
@property (strong, nonatomic) NSString<Ignore>* customProperty;
@property (strong, nonatomic) NSArray<WhateverModel, ConvertOnDemand>* whatever;
@end

Now, I don't really like all these optionals in my public header files. So I was hoping I could have clean header files and then overwrite the properties in a private category
// .h
@interface ProductModel : JSONModel
@property (assign, nonatomic) int id;
@property (strong, nonatomic) NSString* name;
@property (assign, nonatomic) float price;
@property (strong, nonatomic) NSNumber* uuid;
@property (strong, nonatomic) NSString* customProperty;
@property (strong, nonatomic) NSArray* whatever;
@end

// .m
@interface ProductModel ()
@property (assign, nonatomic) int id;
@property (strong, nonatomic) NSString<Optional>* name;
@property (assign, nonatomic) float price;
@property (strong, nonatomic) NSNumber<Optional>* uuid;
@property (strong, nonatomic) NSString<Ignore>* customProperty;
@property (strong, nonatomic) NSArray<WhateverModel, ConvertOnDemand>* whatever;
@end

Sadly though this doesn't seem to work, instead of an array of objects I get an array of nsdictionaries. Is there any other way of marking these relationships other then the public header files?

This is down to how Obj-C works. It's not something JSONModel can influence.
However, you can also mark properties as optional in the implementation file:
+ (BOOL)propertyIsOptional:(NSString*)propertyName
{
  if ([propertyName isEqualToString:@"name"])
    return YES;
  return NO;
}


Add reference to papers in respective blogposts

Laion400m and laion5B

Added reference papers for LAION-5B and LAION-400M.


0.3.0 create transports

Will be used by socket.rs
transport_new needs to be renamed after https://github.com/1c3t3a/rust-socketio/pull/56 is merged

Yep that looks reasonable so far. Maybe we could try to get the base address to be a &'_ str, to get rid of the clone, but that could be saved for later!

I've been adding //TODOs whenever there is something we need to get back to later. In base_url's case it will be a Url (new struct) eventually (added a todo for it).

Tests will be added later once EngineIoSocket is generic enough to lock it to one transport


onClick Pie chart code breaks

Hi,
When I click on pie chart my code breaks, I have tried all possibilities, I found an error in Chart.js, getDatasetAtEvent calling Chart.Interaction.modes.dataset(this, e); this dataset function called by passing 2 params but actually it has 3 params and also there is no check of undefined for 3rd param
Chart.js:6252 Uncaught TypeError: Cannot read property 'intersect' of undefined
    at Object.dataset (https://cdnjs.cloudflare.com/ajax/libs/Chart.js/2.4.0/Chart.js:6252:24)
    at Chart.Controller.getDatasetAtEvent (https://cdnjs.cloudflare.com/ajax/libs/Chart.js/2.4.0/Chart.js:4418:35)
    at HTMLCanvasElement.$elem.(anonymous function).onclick (http://localhost:63342/admin/src/vendor/tc-angular-chartjs-2.1.3.js:121:31)dataset @ Chart.js:6252getDatasetAtEvent @ Chart.js:4418$elem.(anonymous function).onclick @ tc-angular-chartjs-2.1.3.js:121

Please resolve it asap, or I can create pull request for it please let me know
Thanks
Yougesh

Duplicate of #3606 please pr a fix

I have created pull request of this issue, please check


Broken link in readme?

Hi all. I'm pretty sure there's a broken link in the OHS-badge README.md file. I'm thinking maybe the link after "A simplified sample is provided in the main directory" should be "OHS2024Badge.ino" instead of "OHS2024BadgeDefault.ino" and should point to OHS2024Badge.ino instead of OHS2024BadgeDefault.ino?
Looking forward to next weekend!

Oh yes thanks for the notice, I pushed the fix https://github.com/oshwa/OHS2024Badge/commit/0241a4110217f65bb9124f84b633a1485e378abe


updated aerial seeding to work properly with the comparion tool

updated aerial seeding to be recognized by the logic to display info for when aerial seeding is false

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

lgtm


FR: Add Alternative Checkboxes toggle in Style Settings

This request comes as part of the initiative I've started for Obsidian October 2024. Additional information and progress on this project can be found here: https://github.com/damiankorcz/Alternative-Checkboxes-Reference-Set
The current goal is to make it easier for users to implement their own CSS Snippets with Alternative Checkboxes, regardless of the theme they use. At the moment, any theme that doesn't present an option to disable their Alternative Checkboxes implementation, requires the snippet to overwrite the existing theme's code. This can become complicated and hard to maintain as currently 44 themes implement Alternative Checkboxes. Ideally, if all themes have the option to disable their implementation, the snippets can be simpler, and work universally across all themes.
If this is something you are interested in implementing, it would require the following code to be added to your theme:
body.enable-alternative-checkboxes {

/* Encapsulate all code relevant to Altenative Checkboxes here */

}

Add a toggle in the Style Settings code:
-
    id: enable-alternative-checkboxes
    title: Enable Alternative Checkboxes
    description: Disable this if you are using your own implementation via a CSS Snippet.
    default: true
    type: class-toggle
-

Since your theme already implements the feature, the code above enables it by default, in order to not change the existing functionality for users.
When the theme implementation is disabled, all additional checkboxes should be styled the same as the default - [x] checked checkbox; removing any changes to color, icons, fonts, backgrounds, etc.
If you need any help implementing this, let me know! I can also look into making a Pull Request if you would prefer.

Thanks @damiankorcz, I'll implement this soon and I really like the initiative! I've made an effort with Kakano to provide what I think are the most widely-used and useful alternative checkboxes, and I'd be pleased to support a reference set once that's available.
I plan to put this under a Compatibility heading in Style Settings, unless you have any thoughts on how you'd like theme developers to present it. I can also include a brief description linking back to the project page.
The Theme Dev Vault repository would be a good place to document the reference set. I use that vault as a reference during theme development, and I'm sure other theme developers do likewise.
I also like to credit people who have helped me with theme development. Are you happy to be mentioned in the README? I can link to your Github profile, or some other page if you prefer.

Hi @isaacfreeman,
At the moment, I'm focusing on getting all themes with Alternative Checkboxes onto common ground so that it's easy to overwrite their implementation before continuing on the Reference Set.
There isn't really a preference as to where the toggle should go. Feel free to put it where you think is the most logical. I'm documenting each one here regardless, so you can have a look where other themes are putting it:
https://github.com/damiankorcz/Alternative-Checkboxes-Reference-Set/blob/main/09 Style Settings Toggle Review.md
At the moment I made the vault on my account to keep things together and for an easy way to track the progress. I'll probably look into merging whatever info is important into Obsidian Community repositories such as the Theme Dev Vault.
You are welcome to put me in the README. My GitHub account is fine. Don't feel obliged to as I'm just doing this as a fun project on the side.

Implemented in version 4.2.0.


FMWK-545 Update golangci-lint configuration

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.27%. Comparing base (9bcd40e) to head (da4e93e).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #136   +/-   ##
=======================================
  Coverage   82.27%   82.27%
=======================================
  Files          65       65
  Lines        3730     3730
=======================================
  Hits         3069     3069
  Misses        426      426
  Partials      235      235

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Keyboard release latency after long press

Hi,
Thanks for the amazing repository. I have tested the keyboard.c and keyboard.py using rpi4 and found that when I keep pressing one button and then release it, the android/PC would keep adding characters for quite some time. Is this caused by the throughput?
Best

If you are holding the button down for some time, then you are seeing the normal key repeat that is generated by the operating system, and the keyboard code is correctly receiving multiple LE_KEYPRESS calls. If the key press is short, but multiple characters appear on the client, then it a a tricky problem caused by the Bluetooth adapter. The send_key function sends the key code to signal a key down, and then immediately a "no key pressed" all-zero packet. The Bluetooth adapter can only cope with packets sent at a certain rate, and if they are sent too fast, then packets are lost. So if the no key pressed packet is lost, the client thinks the key is held down. The packet transmissions are deliberately slowed down to avoid this, but may need to be even slower - so in send_key add a delay between the key down write_ctic packet and the all-zero key up packet.

It sounds like the opposite problem - too much delay. Remove the 0.04 delay and run this from the command line before starting keyboard. It slows the keyboard repeat rate.
kbdrate -r 2.0 -d 1000


Issue with k8s.io/docs/setup/independent/install-kubeadm/

This is a problem

[ ] Feature Request
[ ] Bug Report

Problem:
kubeadm init fails with below error message:
[preflight] Running pre-flight checks.
[WARNING Firewalld]: firewalld is active, please ensure ports [6443 10250] are open or your cluster may not function correctly
[WARNING FileExisting-crictl]: crictl not found in system path
[preflight] Some fatal errors occurred:
[ERROR Swap]: running with swap on is not supported. Please disable swap
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
OS: CentOS Linux release 7.4.1708 (Core)
Docker Version:
Client:
Version:         1.12.6
API version:     1.24
Package version: docker-1.12.6-68.gitec8512b.el7.centos.x86_64
Go version:      go1.8.3
Git commit:      ec8512b/1.12.6
Built:           Mon Dec 11 16:08:42 2017
OS/Arch:         linux/amd64
Server:
Version:         1.12.6
API version:     1.24
Package version: docker-1.12.6-68.gitec8512b.el7.centos.x86_64
Go version:      go1.8.3
Git commit:      ec8512b/1.12.6
Built:           Mon Dec 11 16:08:42 2017
OS/Arch:         linux/amd64
Kubadm and kubectl versions: 1.9.0-0
QUEMU and Libvirt details:
Compiled against library: libvirt 2.0.0
Using library: libvirt 2.0.0
Using API: QEMU 2.0.0
Running hypervisor: QEMU 2.6.2
Baremetal OS: Opensuse 42.2
Proposed Solution:
Page to Update:
http://kubernetes.io/...

Tried Below and went a step further but endedup with another issue:
kubeadm reset
systemctl restart kubelet
kubeadm init --skip-preflight-checks
[root@K8S-Master openstack]# kubeadm reset
[preflight] Running pre-flight checks.
[reset] Stopping the kubelet service.
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Removing kubernetes-managed containers.
[reset] No etcd manifest found in "/etc/kubernetes/manifests/etcd.yaml". Assuming external etcd.
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[root@K8S-Master openstack]# systemctl restart kubelet
[root@K8S-Master openstack]# kubeadm init --skip-preflight-checks
Flag --skip-preflight-checks has been deprecated, it is now equivalent to --ignore-preflight-errors=all
[init] Using Kubernetes version: v1.9.0
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
[WARNING Firewalld]: firewalld is active, please ensure ports [6443 10250] are open or your cluster may not function correctly
[WARNING Swap]: running with swap on is not supported. Please disable swap
[WARNING FileExisting-crictl]: crictl not found in system path
[certificates] Generated ca certificate and key.
[certificates] Generated apiserver certificate and key.
[certificates] apiserver serving cert is signed for DNS names [k8s-master.ap.local kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [<IP_ADDRESS> <IP_ADDRESS>]
[certificates] Generated apiserver-kubelet-client certificate and key.
[certificates] Generated sa key and public key.
[certificates] Generated front-proxy-ca certificate and key.
[certificates] Generated front-proxy-client certificate and key.
[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"
[kubeconfig] Wrote KubeConfig file to disk: "admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf"
[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".
[init] This might take a minute or longer if the control plane images have to be pulled.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://localhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.

I tried Ubuntu 16.04.3, same issue. Solution: swapoff -a and then run kubeadm init --ignore-preflight-errors=all . Installation went through but the node status is showing as NotReady and when i join worker nodes it joins and same problem, Work node shows status is showing as not ready with no Name.


(PDB-2548) prepared statement array in resource-exists?

This changes the resource-exists? function to use an array-valued prepared
statement parameter, rather than a list of parameters that could potentially
exceed max_short.

@wkalt not sure what we should do about rollup here.


fix: eliminate goroutine leak in the authenticators

This PR fixes some possible goroutine leak in the authenticators' getToken methods.
Closes #108

:tada: This PR is included in version 5.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add warning about message length limit

Show warning when character limit is reached during entering of the message text and add disabled and loading states to send message button.
MOB-1797

!squash

!merge


WIP: [FEATURE] Send Progress Report via WhatsApp

#292

@AronNovak please review.
Since there's another feature that we may need to deliver before this one, please DO NOT MERGE this PR.
Also, there're couple of @todos here, that are handle in follow up PRs.


Img not exported

Heyoo there!
Super cool lib, and great documentation at that! However, I stumble when trying to reproduce the img.pixel demo. However I try, I can't seem to construct myself an Img 😅.
The Image-guide and docs tells me I can either create one using the constructor new Img(), or the static method Img.load().
Yet when installing via npm and in codepen it seems like Img isn't exported. When cloning the source myself and building the source myself I can successfully import { Img } from "pts"
Cheers and thanks,
/ Freddy

Hi @fredrikelmegren -- sorry for the late response. This bug should be fixed in the latest build 0.10.6. Give it a try :)

Closing this issue now. Please reopen if there're still issues. Thanks for reporting!


Improve documentation, restrict dependencies versions, switch to standard AWS S3 auth env variables

Apologies for the several changes, but wanted to get several things done quickly.
This PR :

Removes the custom environment variables used for AWS S3 authentication ("OSC_S3_KEY" ...). We shouldn't define such logic and let clients configure credentials the standard way (either with standard environment variable names, or with profiles, etc...).
Rearranges documentation to be more developer-friendly. More precisely, the main README has a standard structure (quickstart : installation and usage, and contribution), and a second document called HAZARD is linked in the main one and contains modelling specific information.
Adds an example usage of the CLI that produces output locally in the README. This closes #64.
Restricts dependencies versions so as to not automatically update to the next minor version. This closes #53. Updates the pdm lockfile accordingly.
Removes documentation here and there (for example, IDE set up). These informations hide the other actual essential pieces while not providing great value (it's not the goal of this repo to explain how to set up an IDE).

Following comments on Slack by @joemoorhouse, I made the following changes to the PR:

Keep the legacy custom AWS env vars, just make them optiona. For backward compatibility.
Change version restrictions in pyproject.toml : allow for minor updates but prevent automatic major updates.


fix: rename giscus-frame class to giscus

Fix #154.
The error:

It is caused by a recent update in giscus: https://github.com/laymonage/giscus/commit/ae401f85cea100381554f7a739cb7fe7a415f2b4
The update was done to prevent iFrameResizer from interfering with other <iframe> elements on the page. (I think by default it applies to all <iframes> that exist on the page.)
However, the error exists because you use the giscus-frame class for the div. The giscus-frame is meant to be used by giscus' <iframe> tag only, and it's managed by the client script. You should use the giscus class instead to tell giscus where to put the <iframe>.
From the docs:

Thanks for the quick fix!


[Bug] Fix Tuple is null predicate may cause be cores

Proposed changes
#0  0x0000000001491696 in operator bool (this=<optimized out>) at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/stl_bvector.h:916
#1  operator* (this=<optimized out>) at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/stl_bvector.h:348
#2  operator[] (__n=<optimized out>, this=<optimized out>) at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/stl_bvector.h:918
#3  doris::RowDescriptor::tuple_is_nullable (this=this@entry=0x16943c78, tuple_idx=384727376) at ../src/runtime/descriptors.cpp:358
#4  0x00000000012346d7 in doris::TupleIsNullPredicate::prepare(doris::RuntimeState*, doris::RowDescriptor const&, doris::ExprContext*) () at ../src/exprs/tuple_is_null_predicate.cpp:39
#5  0x000000000120784c in doris::ExprContext::prepare(doris::RuntimeState*, doris::RowDescriptor const&, std::shared_ptr<doris::MemTracker> const&) () at ../src/exprs/expr_context.cpp:61
#6  0x00000000011fda8e in doris::Expr::prepare(std::vector<doris::ExprContext*, std::allocator<doris::ExprContext*> > const&, doris::RuntimeState*, doris::RowDescriptor const&, std::shared_ptr<doris::MemTracker> const&) ()
    at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/stl_vector.h:1061
#7  0x00000000019d5226 in doris::SortExecExprs::prepare(doris::RuntimeState*, doris::RowDescriptor const&, doris::RowDescriptor const&, std::shared_ptr<doris::MemTracker> const&) () at ../src/exec/sort_exec_exprs.cpp:52
#8  0x0000000001a8405a in doris::SpillSortNode::prepare(doris::RuntimeState*) () at ../src/exec/exec_node.h:179
#9  0x00000000019b0d41 in doris::ExecNode::prepare(doris::RuntimeState*) () at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/stl_vector.h:1043
#10 0x0000000001ac2dac in doris::AnalyticEvalNode::prepare(doris::RuntimeState*) () at ../src/exec/analytic_eval_node.cpp:142
#11 0x00000000019b0d41 in doris::ExecNode::prepare(doris::RuntimeState*) () at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/stl_vector.h:1043
#12 0x0000000001a98338 in doris::PartitionedAggregationNode::prepare(doris::RuntimeState*) () at ../src/exec/partitioned_aggregation_node.cc:188
#13 0x000000000154eeba in doris::PlanFragmentExecutor::prepare(doris::TExecPlanFragmentParams const&, doris::QueryFragmentsCtx const*) () at /home/disk4/xuyang/work/baidu/bdg/doris/thirdparty-gcc10/installed/include/boost/smart_ptr/scoped_ptr.hpp:109
#14 0x00000000014c6ebe in doris::FragmentExecState::prepare (this=this@entry=0x16ef8000, params=...) at ../src/runtime/fragment_mgr.cpp:228
#15 0x00000000014caea2 in doris::FragmentMgr::exec_plan_fragment(doris::TExecPlanFragmentParams const&, std::function<void (doris::PlanFragmentExecutor*)>) () at ../src/runtime/fragment_mgr.cpp:606
#16 0x00000000014ccb12 in doris::FragmentMgr::exec_plan_fragment(doris::TExecPlanFragmentParams const&) () at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/std_function.h:87
#17 0x000000000159409e in doris::PInternalServiceImpl<doris::PBackendService>::_exec_plan_fragment (this=this@entry=0x731f680, ser_request=...) at ../src/runtime/exec_env.h:117
#18 0x000000000159419f in doris::PInternalServiceImpl<doris::PBackendService>::exec_plan_fragment (this=0x731f680, cntl_base=<optimized out>, request=<optimized out>, response=0x161fd660, done=0x169b0c80)
    at /home/disk4/xuyang/work/baidu/bdg/doris/thirdparty-gcc10/installed/include/google/protobuf/arenastring.h:231
#19 0x000000000217b1b7 in brpc::policy::ProcessHttpRequest(brpc::InputMessageBase*) () at ../src/brpc/policy/http_rpc_protocol.cpp:1484
#20 0x00000000021485d7 in brpc::ProcessInputMessage (void_arg=void_arg@entry=0x1622f210) at ../src/brpc/input_messenger.cpp:135
#21 0x000000000214949e in operator() (last_msg=0x1622f210, this=<synthetic pointer>) at ../src/brpc/input_messenger.cpp:141
#22 ~unique_ptr (this=<synthetic pointer>, __in_chrg=<optimized out>) at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/unique_ptr.h:360
#23 brpc::InputMessenger::OnNewMessages(brpc::Socket*) () at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/unique_ptr.h:354
#24 0x00000000021f19fe in brpc::Socket::ProcessEvent(void*) () at ../src/brpc/socket.cpp:1017
#25 0x000000000229a25f in bthread::TaskGroup::task_runner(long) () at ../src/bthread/task_group.cpp:296
#26 0x000000000228b661 in bthread_make_fcontext () at /home/opt/compiler/gcc-10-r5/include/c++/10.1.0/bits/stl_iterator.h:953

Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have created an issue on (Fix #6462 ) and described the bug/feature there in detail
[x] Compiling and unit tests pass locally with my changes

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Please add some unite test.
Could you please give a example query of this bug


Add FORCE_CUDA option

This commit allows cuda code to be generated in a non-cuda environment such as docker, similar to https://github.com/pytorch/vision/pull/927/files#diff-2eeaed663bd0d25b7e608891384b7298

Thanks for the contribution!


Bruise packs are once again OP (ointment too)

Description
bruise packs and ointments (probably all other similar things) no longer interupts whne used again so you can spam using it without autoclicking
Intended?
Screenshots
https://user-images.githubusercontent.com/97402700/167459253-802ce17c-b2c9-4147-9bcb-acff3dd56efd.mp4
Additional context

Same thing is happening for drinks and I think food too

Are you sure because they haven't been touched in a while. At any rate the others are fixed on master.


It can not work well on the latest version of Xcode:8.3.3

100% crash on [KeychainItemWrapper writeToKeychain].
NSAssert error:"Couldn't add the Keychain Item."

You should enable Keychain Sharing in Xcode, Xcode Capabilities editor on the target settings panel to turn on Keychain Sharing.
It will help you

I have solved it. Group is incorrect. Thank you anymore


Azure Virtual Machine Import

Im getting error in importing resources only happens for virtual machine, please advice

Getting the same thing for virtual machines.
Terraform 0.15 installed via brew, Azure provider 2.63.0, Mac OS BigSur.

Same error with multiple terraform versions (0.13, 0.14, 1.0). I have also tried multiple azurerm provider versions from 2.49 to 2.66. In all cases, the result is the same as above, it fails for virtual_machine.

I got the same error for my virtual machines.
Having tried changing Terraform versions and azurerm provider versions but still not working.

Likewise. Looks like this has been the case for some time.

I may have found some interesting things about this. The problem occurs when I use Azure Migrate to create the virtual machine. For some reason I don't understand yet, the generated virtual machine resource does not contain an osProfile block. This explains the failure when terraformer tries to check if it is a Linux or a Windows, using the fore mention block.

https://github.com/GoogleCloudPlatform/terraformer/blob/a535b6d3a6243c3127d24ed355ca02780e8403ab/providers/azure/virtual_machine.go

It should be fixed when the following pull request is merged #989


History search with fzf is broken in the VSCode integrated terminal

Type: Bug

Install fzf which will install keybindings for bash, including setting up a keybinding on Ctrl + R for history search
Type Ctrl + R in the VSCode integrated terminal and select a command from bash history

VSCode then adds ^[]633;C^G^[]633;E;__fzf_history__^G to the start of the command, breaking things

I don't think this is a fzf issue given fzf works fine in iTerm2/Mac Terminal, and used to work in VSCode until around a month ago.
The only possibly related bugs I could find were #120825 and #120352, but the fix from those bugs ("terminal.integrated.localEchoLatencyThreshold": -1) did not appear to change anything.
VS Code version: Code 1.72.0
(Universal) (64bbfbf67ada9953918d72e1df2f4d8e537d340e, 2022-10-04T23:21:58.256Z)
OS version: Darwin x64 21.6.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz (8 x 2800)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
6, 7, 5

Memory (System)
16.00GB (0.18GB free)

Process Argv
--disable-extensions example.js --crash-reporter-id 79432e7f-4a1f-43a9-8f9b-83374fb3df76

Screen Reader
no

VM
0%

Extensions disabled
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
2144e591:30553903
pyindex848:30577860
nodejswelcome1:30583747
fc301958:30573243

@scheibo does disabling shell integration workaround the problem? "terminal.integrated.shellIntegration.enabled": false

I recently had my terminal search history stop working with zsh. Disabling terminal.integrated.shellIntegration.enabled and restarting my integrated terminal fixed it for me as well.  I only just started seeing this issue in the latest release (1.74.0). I am also running oh my zsh.

/duplicate https://github.com/microsoft/vscode/issues/168396
will be fixed in the recovery build


Add Support for Batch STARKs with Proving, Verification, and Recursion

The method used in this PR can be found in Section 3.2 in the paper.

Hi @sai-deng! This is quite a consistent PR, would you mind posting a description of the changes, including the rationale please? Thank you!

Hey @sai-deng! Thank you for the PR! As this is quite dense, could you write some explanation about the approach taken, and any specific parts that may help reviewers?
Also could you explain how this impacts STARK recursive verification now that they're batched together? Thanks!

Hey @sai-deng! Thank you for the PR! As this is quite dense, could you write some explanation about the approach taken, and any specific parts that may help reviewers? Also could you explain how this impacts STARK recursive verification now that they're batched together? Thanks!

The paper is still WIP,  the method used in this PR can be found in Section 3.2

Still in the middle of reviewing. Looks really nice!
I have a random question: from what I'm seeing you can only open leaves from the bottom layer, and you open all intermediary leaves you encounter on your way to the top. If for some reason you want to open only a leaf from one of the smaller trees, can't you have a shorter proof starting at the smaller tree's height?

Thanks for reviewing! In this case, you'd better not use a field Merkle tree since it will not reduce the Merkle proof size.

Fairly minor comments as well for now, will do another pass at FRI later.

Thanks for the careful reviews! Comments are addressed in 59d637f.

I have a question with regards to STARK batching in general. From section 3.3 of the paper, I understand that for each individual STARK you pad it to the maximum length it can have given a normal execution (determined via testing with a bunch of different inputs) to have a fixed length you can build a recursion circuit from.
In our zkEVM, we have very wide discrepancies between best and worst case scenarios for individual trace lengths, which can range e.g. from 16 to 2^20. Does that mean we would be forced to make a circuit accommodating a 2^20-length trace, and pad the trace to this length for every single execution?

I have a question with regards to STARK batching in general. From section 3.3 of the paper, I understand that for each individual STARK you pad it to the maximum length it can have given a normal execution (determined via testing with a bunch of different inputs) to have a fixed length you can build a recursion circuit from. In our zkEVM, we have very wide discrepancies between best and worst case scenarios for individual trace lengths, which can range e.g. from 16 to 2^20. Does that mean we would be forced to make a circuit accommodating a 2^20-length trace, and pad the trace to this length for every single execution?

Yes, we have to pad the trace to a length of 2^20. Alternatively, we can use a Merkle tree to save all the valid recursion circuits hash and treat the Merkle root hash as the public parameters.

Hi @sai-deng, sorry for the wait!
I'm currently implementing STARK batching on our zkEVM alongside the review, which I treat as another layer of testing. I should be done by the end of the week; if there's no issue I'll approve the PR then!

Hi @sai-deng, sorry for the wait! I'm currently implementing STARK batching on our zkEVM alongside the review, which I treat as another layer of testing. I should be done by the end of the week; if there's no issue I'll approve the PR then!

Batch STARKs are already implemented in our zkVM; unfortunately, the code is not open-sourced yet. Let me know if you need any help during the implementation.


Add WhatsApp redirect button

How to: https://faq.whatsapp.com/5913398998672934
https://about.meta.com/br/brand/resources/whatsapp/whatsapp-brand

[X] Add WA image to project;
[X] Create personalized WA link;
[x] Make WA image float, always on top of everything, in the bottom right corner;
[x] Wrap image with Anchor tag using personalized WA link;

PRs #21, #23 and #25 resolve this issue.


Avoid hashing in da.from_array if no name desired

cc @anton-malakhov

👍 Thank you!

Merging this tomorrow if no further comments


JsonReaderException: Unexpected character encountered while parsing value: T. Path 'ListOnMasterServer'

I'm having issues getting this v-rising container up and running. The container seems to be crashing with the following error:
JsonReaderException: Unexpected character encountered while parsing value: T. Path 'ListOnMasterServer', line 12, position 25.
  at Newtonsoft.Json.JsonTextReader.ReadAsBoolean () [0x00000] in <00000000000000000000000000000000>:0
  at Newtonsoft.Json.JsonReader.ReadForType (Newtonsoft.Json.Serialization.JsonContract contract, System.Boolean hasConverter) [0x00000] in <00000000000000000000000000000000>:0
  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00000] in <00000000000000000000000000000000>:0
  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Populate (Newtonsoft.Json.JsonReader reader, System.Object target) [0x00000] in <00000000000000000000000000000000>:0
  at Newtonsoft.Json.JsonSerializer.PopulateInternal (Newtonsoft.Json.JsonReader reader, System.Object target) [0x00000] in <00000000000000000000000000000000>:0
  at Newtonsoft.Json.JsonConvert.PopulateObject (System.String value, System.Object target, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.Shared.SettingsBase.TryLoadJsonFile (System.String path, System.Boolean logWarning, System.Boolean defaultSettings) [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.Shared.SettingsBase..ctor (System.String defaultFilePath, System.Boolean loadDefault, System.Boolean applyEnvironmentVariables) [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.ServerHostSettings..ctor () [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.SettingsManager.VerifyServerSettings () [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.SettingsManager.get_ServerHostSettings () [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.Auth.SteamPlatformSystem.TryInitServer () [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.Auth.SteamPlatformSystem.OnCreate () [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.ComponentSystemBase.CreateInstance (Unity.Entities.World world, Unity.Entities.SystemState* statePtr) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.World.AddSystem_OnCreate_Internal (Unity.Entities.ComponentSystemBase system) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.World.GetOrCreateSystemsAndLogException (System.Collections.Generic.IEnumerable`1[T] types, System.Int32 typesCount) [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.CustomWorldSpawning.AddSystemsToWorld (Unity.Entities.World world, ProjectM.WorldType worldType, System.Type[] systemTypes, System.Type initializationSystemGroupType, System.Type simulationSystemGroupType, System.Type presentationSystemGroupType, ProjectM.CustomWorld customWorld) [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.Bootstrap.Unity.Entities.ICustomBootstrap.Initialize (System.String defaultWorldName) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.DefaultWorldInitialization.Initialize (System.String defaultWorldName, System.Boolean editorWorld) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.AutomaticWorldBootstrap.Initialize () [0x00000] in <00000000000000000000000000000000>:0
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception)
Unity.Entities.World:GetOrCreateSystemsAndLogException(IEnumerable`1, Int32)
ProjectM.CustomWorldSpawning:AddSystemsToWorld(World, WorldType, Type[], Type, Type, Type, CustomWorld)
ProjectM.Bootstrap:Unity.Entities.ICustomBootstrap.Initialize(String)
Unity.Entities.DefaultWorldInitialization:Initialize(String, Boolean)
Unity.Entities.AutomaticWorldBootstrap:Initialize()

NullReferenceException: Object reference not set to an instance of an object.
  at ProjectM.CustomWorldSpawning.AddSystemsToWorld (Unity.Entities.World world, ProjectM.WorldType worldType, System.Type[] systemTypes, System.Type initializationSystemGroupType, System.Type simulationSystemGroupType, System.Type presentationSystemGroupType, ProjectM.CustomWorld customWorld) [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.Bootstrap.Unity.Entities.ICustomBootstrap.Initialize (System.String defaultWorldName) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.DefaultWorldInitialization.Initialize (System.String defaultWorldName, System.Boolean editorWorld) [0x00000] in <00000000000000000000000000000000>:0
  at Unity.Entities.AutomaticWorldBootstrap.Initialize () [0x00000] in <00000000000000000000000000000000>:0

NullReferenceException: Object reference not set to an instance of an object.
  at GameVersionUtils.TryInitializePersistenceVersion () [0x00000] in <00000000000000000000000000000000>:0
  at GameVersionUtils.GetOrLoadPersistenceVersion () [0x00000] in <00000000000000000000000000000000>:0
  at ProjectM.GameBootstrap.Start () [0x00000] in <00000000000000000000000000000000>:0

After this error shows in the logs, I just get a repeated message:
Stuck main thread detected. Last system started: . Last system finished: . Last subnode: PrefabGuid: 0 NodeIndex: 0.
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:Log(Object)
Unity.Entities.<>c__DisplayClass8_0:<Initialize>b__0(Object)
System.Runtime.Serialization.DeserializationEventHandler:Invoke(Object)
System.Threading.SendOrPostCallback:Invoke(Object)
System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object)
System.Runtime.Serialization.DeserializationEventHandler:Invoke(Object)

Im using the image in this compose file:
version: "3.4"
services:
  v-rising:
    container_name: v-rising
    image: mephi00/v-rising-wine
    restart: unless-stopped
    volumes:
      - /docker/v-rising/saves:/saves
    ports:
        - 9876:9876/udp
        - 9877:9877/udp
    environment:
        - TZ=America/New_York
        - PUID=1000
        - PGID=1000
        - V_RISING_NAME=VRising Server
        - V_RISING_SAVE_NAME=vrising_server
        - V_RISING_PUBLIC_LIST=True
        - V_RISING_PASSW=${V_RISING_PASS}
        - V_RISING_DESC=Big ol Vampire
        - V_RISING_MAX_USER=20
        - V_RISING_MAX_ADMIN=4
        - V_RISING_GAME_MODE=PvE

I cant really tell what the error is, but if you need any more info let me know and I will be happy to provide it.

Seems all it takes is reading my own issue to figure out what was wrong...
V_RISING_PUBLIC_LIST=True was the problem. This has to be lowercase, my Python is showing... Setting to true will fix the problem. I dont know if this is worth mentioning in the docs to prevent other people from making the same mistake