Dev fix log exception

Coverage increased (+0.01%) to 90.909% when pulling 0d9e8209c854feea3e87bdcfbc6f29970b78de98 on dev_fix_log_exception into 458626464e1ffb38851768b173c8afc8a4485bce on fix_log_exception.

Coverage increased (+0.01%) to 90.909% when pulling b5a2fa2284d512f14337bfe4c12cf19a42bf3d5f on dev_fix_log_exception into 458626464e1ffb38851768b173c8afc8a4485bce on fix_log_exception.


Add "eslint-import-resolver-typescript" to the remix template

When creating a new project with create-remix@latest, if you attempt to import a *.css file (for instance, when using Tailwind), eslint complains about the resolver:

The fix is to run npm install -D eslint-import-resolver-typescript, after which eslint will no longer complain about the wrong interface or the *.css file.

I did this and grabbed the original fix from #8337 in #8441 so closing this in favor of that


Pressing an accent key followed by T reloads emotes

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running a recent nightly build or the newest stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues for similar looking reports

Describe your issue
Steps to reproduce:

Select a keyboard layout with dead keys (Tested with US-International and ABNT)
Reload emotes once using F5
Press any accent character (' " ` ~ ^) followed by the letter T

(Video is using Chatterino7 but it also happens with regular Chatterino Nightly 2.3.4)
Screenshots
https://user-images.githubusercontent.com/95153760/143726544-cf9a8826-49f0-4d53-805e-77db8cd5a613.mp4
OS and Chatterino Version
Chatterino Nightly 2.3.4 on Windows 11

Unable to reproduce:
Chatterino 7.3.4 (commit d8bc1afa) on Arch Linux (5.15.5-zen), picom, bspwm
Chatterino 2.3.4 (commit 4e5170799) on Windows 10 21H1

I didn't notice the layout being part of it, thanks @Felanbird. Tested again and there is some weirdness around the accent not showing until the next character is pressed. Still can't reproduce the issue on Win 10, have to get a Win 11 user to check.

I assume it is a Chatterino issue because this doesn't seem to refresh anything else you can refresh with F5, and it doesn't happen unless I'm on a Nightly version.
The "weirdness around the accent" is the expected behavior, pressing ' on these layouts will only input the ' character once a space or a character that doesn't support accents is pressed.

After more testing and using the latest nightly, can reproduce.
Chatterino 2.3.4 (commit 0deedf019) on Windows 10 21H1
Call to SplitHeader::reloadChannelEmotes() appears to come from the "reloadEmotes" shortcut action. Not sure how to trace signals and the hotkey system is confusing to me. @Mm2PL bing

The "weirdness around the accent" is the expected behavior, pressing ' on these layouts will only input the ' character once a space or a character that doesn't support accents is pressed.

Thanks for clearing that up, I wasn't aware that's how that keyboard worked!

@jammehcow calls to actions are made from lambdas created in HotkeyController::shortcutsForCategory. See around line 70 in src/controllers/hotkeys/HotkeyController.cpp

Unable to replicate on Ubuntu Linux 20.04.1, i3, IBus using AltGr+(Shift)?+[;'].

After further investigation, this seems like a QT issue. The caller to that method 100% bound to the F5 key. I assume QT is interpreting it weirdly as F5 or something.

After further investigation, this seems like a QT issue. The caller to that method 100% bound to the F5 key. I assume QT is interpreting it weirdly as F5 or something.

It's indeed a Qt bug. It's misinterpreting WM_CHAR's wParam as a keycode. I reported QTBUG-117903 (feels like it would've been reported before, but I couldn't find a similar issue).

This is fixed in Qt:

6.5.X after 6.5.4
6.6.X after 6.6.2
6.7.0 (whenever it releases)

Only thing to do now is to ensure that CI uses appropriate versions of Qt and this is noted down in build instructions.


st_isvalid difference

in postgis:
select st_isvalid("POINT (30)");
select st_isvalid("POINT (,)");
select st_isvalid("POINT (a b)");
select st_isvalid("MULTIPOINT ()");
select st_isvalid("MULTIPOINT (,)");
select st_isvalid("POINT(1 2 3 4 5 6 7)");
select st_isvalid("LINESTRING(1 1)");
select st_isvalid("MULTIPOINT(1 1, 2 2");
all return ERROR while executing these in psql
in arctern, all of them return FALSE

I presume that 'return FALSE' is also reasonable, what's your opinion ? @GuoRentong @guoxiangzhou @liangliu

the arctern results returned is OK in my thoughts, however it's just different with postgis results, if we accept that, it's fine.

please let me know if you have diff options on this @GuoRentong @guoxiangzhou
I'll close this issue if no comments given

I think 'return parser error' for SQL and 'return false' for API are actually equivalent . But, I got some bad input case which return true in arctern.Please refer to #161

close this issue


DLQ, Pyarrow, backoff

Without pyarrow installed, I got the following error:
2021-11-05 16:10:20.389 | INFO     | __main__:stac:33 - using satextractor.stac.gcp_region_to_item_collection stac creator.
Error executing job with overrides: []
Traceback (most recent call last):
  File "venv/lib/python3.9/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 62, in _call_target
    return _target_(*args, **kwargs)
  File "venv/lib/python3.9/site-packages/satextractor/stac/stac.py", line 47, in gcp_region_to_item_collection
    df = get_sentinel_2_assets_df(client, region, start_date, end_date)
  File "venv/lib/python3.9/site-packages/satextractor/stac/stac.py", line 168, in get_sentinel_2_assets_df
    dfs.append(query_job.to_dataframe())
  File "venv/lib/python3.9/site-packages/google/cloud/bigquery/job/query.py", line 1644, in to_dataframe
    return query_result.to_dataframe(
  File "venv/lib/python3.9/site-packages/google/cloud/bigquery/table.py", line 1938, in to_dataframe
    record_batch = self.to_arrow(
  File "venv/lib/python3.9/site-packages/google/cloud/bigquery/table.py", line 1713, in to_arrow
    raise ValueError(_NO_PYARROW_ERROR)
ValueError: The pyarrow library is not installed, please install pyarrow to use the to_arrow() function.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "sat-extractor/src/satextractor/cli.py", line 185, in main
    stac(cfg)
  File "sat-extractor/src/satextractor/cli.py", line 44, in stac
    item_collection = hydra.utils.call(
  File "venv/lib/python3.9/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 180, in instantiate
    return instantiate_node(config, *args, recursive=_recursive_, convert=_convert_)
  File "venv/lib/python3.9/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 249, in instantiate_node
    return _call_target(_target_, *args, **kwargs)
  File "venv/lib/python3.9/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 64, in _call_target
    raise type(e)(
  File "venv/lib/python3.9/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 62, in _call_target
    return _target_(*args, **kwargs)
  File "venv/lib/python3.9/site-packages/satextractor/stac/stac.py", line 47, in gcp_region_to_item_collection
    df = get_sentinel_2_assets_df(client, region, start_date, end_date)
  File "venv/lib/python3.9/site-packages/satextractor/stac/stac.py", line 168, in get_sentinel_2_assets_df
    dfs.append(query_job.to_dataframe())
  File "venv/lib/python3.9/site-packages/google/cloud/bigquery/job/query.py", line 1644, in to_dataframe
    return query_result.to_dataframe(
  File "venv/lib/python3.9/site-packages/google/cloud/bigquery/table.py", line 1938, in to_dataframe
    record_batch = self.to_arrow(
  File "venv/lib/python3.9/site-packages/google/cloud/bigquery/table.py", line 1713, in to_arrow
    raise ValueError(_NO_PYARROW_ERROR)
ValueError: Error instantiating 'satextractor.stac.stac.gcp_region_to_item_collection' : The pyarrow library is not installed, please install pyarrow to use the to_arrow() function.

DLQ fixed following #10

And added exponential backoff

Feel free to pick and choose!


Write a GO program to find sum of squares of numbers

Description
Write a GO program to find sum of squares of numbers
Suppose you have a list of numbers, and you want to find the sum of the squares of those numbers. For example, if you have the list [1, 2, 3], you want to find the sum of the squares of those numbers, which is 1^2 + 2^2 + 3^2 = 14.
Input  : 1 2 3 4 5
Output : 55

How to contribute

Save the solution in find_sum_of_squares_of_numbers.go file
Add find_sum_of_squares_of_numbers.go file in program/find-sum-of-squares-of-numbers folder

!assign

assign

!assign


How to install ext-rar

Hello, I need to install UnifiedArchive so far I created a new condition in the dockerfile file and added the key in the file docker-compose.yml, then run docker build php-fpm
ARG INSTALL_RAR_ARCHIVE=false
RUN if [ ${INSTALL_RAR_ARCHIVE} = true ]; then \
    # Install the rar extension
    pecl install rar && \
    docker-php-ext-enable rar \
;fi

Error message
/tmp/pear/temp/rar/rar.c: At top level:
cc1: warning: unrecognized command line option "-Wno-logical-op-parentheses"
Makefile:194: recipe for target 'rar.lo' failed
make: *** [rar.lo] Error 1
ERROR: `make' failed
error: /usr/local/lib/php/extensions/no-debug-non-zts-20151012/rar does not exist

usage: /usr/local/bin/docker-php-ext-enable [options] module-name [module-name ...]
   ie: /usr/local/bin/docker-php-ext-enable gd mysqli
       /usr/local/bin/docker-php-ext-enable pdo pdo_mysql
       /usr/local/bin/docker-php-ext-enable --ini-name 0-apc.ini apcu apc

Possible values for module-name:
gd.so mcrypt.so opcache.so pdo_mysql.so pdo_pgsql.so zip.so
ERROR: Service 'php-fpm' failed to build: The command '/bin/sh -c if [ ${INSTALL_RAR_ARCHIVE} = true ]; then     pecl install rar &&     docker-php-ext-enable rar ;fi' returned a non-zero code: 1`

That's not a laradock issue, a quick google gave me this https://bugs.php.net/bug.php?id=63016, so it looks like it's a bug in the rar package. You might need to try and make a fix yourself and build it from the .tgz. Doesn't look like it's maintained anymore, last release being in 2013.

Actually it looks like the problem is that the gcc version is too old and doesn't have that -Wno-logical-op-parentheses option included.

Closing this based on @francislavoie 's comment that this issue is not Laradock related

If anyone stumbles this thread why having rar extension issues...
On php 7.4 given pecl extensions couldn't compile, this repo saved me https://github.com/esminis/php_pecl_rar


Removing unused parameter output as per #15

is it a pre requisite to work with python >=3.2?

yes

I made a confusion, I fixed two bugs on the same PR, just consider the #15
I'll raise a new PR for the bug #30 later
Can you check this before?

I will be going through all the PRs after I finish up what I've been working on. Do what you want, I'm busy at the moment.

Fixed with recent commit


Model Complexity

Dear authors,
I tried to reproduce the results on the IDRiD dataset and have concerns regarding the computational resources you used for the experiments.
You reported that H2Former only takes 33.56G of FLOPs with an input size of 512x512.
When I ran your code, it took 156.8G of FLOPs. Therefore, my system (2xA6000 GPUs: 96GB) runs out of memory, while you only used an RTX3090 GPU (24GB) for training.

Can you clarify this problem?
Thank you very much.

We use mixed-precision for training, and  you can try to reduce the memory footprint in this  way.  In our system, the  FLOPs is 33G.

I've tried your suggestion but the problem remains the same.
Can you please provide the training script that you used to produce the FLOPs of 33G?
Thank you very much.

The script that  used to produce the FLOPs.

I'm sorry for the confusion.
What I meant is the training script that used mixed precision for training.
I used the following code (attached figure) but it does not work.

Thank you very much.

I also have the same problem, how did you solve it?

@RongcanChen I cannot solve it.


fix typo

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks for the PR. The typo got already addressed :-)
Closing


[openshift/tokman.yml.j2] create route

In 'distributed workers' scenario we need tokman to be publicly accessible.
https://github.com/packit/tokman/issues/7
Tested with a worker in PSI and haven't seen any errors.

That's a valid question and reason I filled https://github.com/packit/tokman/issues/7

Closing per Franta's valid objection, let's discuss in https://github.com/packit/tokman/issues/7


Ensure HelpInfo.Category is consistently a string

PR Summary
The Category member is a NoteProperty so depending on the code path, it is mostly a string, but sometimes is the HelpCategory type.  Fix all instances where this value is set as a string to ensure consistency.
PR Context
Fix https://github.com/PowerShell/PowerShell/issues/18224
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@adityapatwardhan Can you please review this PR?


Add support for static entropy

We have to target it for v0.11 since it breaks APIs - and there is no way of adding support for the feature without the API break

This should help with unit testing, I would think

@zoedberg already fixed in previously merged PRs


chore(release): publish configuration fixes

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Trafficserver no longer available in EPEL repositories

https://docs.trafficserver.apache.org/en/7.1.x/getting-started/index.en.html#rhel-centos
wget https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
sudo rpm -Uvh epel-release-7*.rpm
sudo yum install trafficserver
output:
No package trafficserver available.
Error: Nothing to do

Fedora's trafficserver RPM repo links to FESCo issue #2080, which mentions unsuccessful attempts to contact the package's maintainer, @janfrode, followed by a vote to orphan the package.
Either

The EPEL section should be removed from the Getting Started page, or
Someone could go to https://src.fedoraproject.org/rpms/trafficserver and adopt the package.

Any news on how to get an RPM for version 9 or 10?
Thanks!

@jeredfloyd volunteered to maintain the trafficserver EPEL package. His trafficserver 9.1.2 RPM was approved in Red Hat bug 2076374, and he adopted the trafficserver RPM in FESCo issue #10795. Not sure what happens now, but presumably the trafficserver RPM will be in EPEL sometime in the near future.
Thanks @jeredfloyd!

Second the Thanks @jeredfloyd!

  I should have 9.1.2 submitted for review later this week.

Being a bit of an RPM novice,  how can I obtain the RPM from this repo?
https://github.com/jeredfloyd/rpm-trafficserver

Awesome!   Any guidance on best one to use for CentOs 7?

You would use the EPEL 7 repo for CentOS 7.

ATS 9.1.2 is now in the Fedora and EPEL8 repos, and should land in EPEL7 and EPEL9 shortly:
https://bodhi.fedoraproject.org/updates/?packages=trafficserver

Thanks @jeredfloyd
When I try to install it, I see the below dependencies are missing and the installation therefore is failing.
hwloc-libs-2.2.0-3.el8.x86_64.rpm
hwloc-2.2.0-3.el8.x86_64.rpm

@vgrme Can you tell me a bit more about how you are trying to install it, and on what sort of system?  yum/dnf should pull those requirements in from the repo.

I did yum install trafficserver :-)
I just looked up one of the mirrors I dont see those rpms
hwloc-libs-2.2.0-3.el8.x86_64.rpm
hwloc-2.2.0-3.el8.x86_64.rpm

Are you on RHEL, CentOS, Rocky, Alma... ?

RHEL 8.5

Does the same problem occur on RHEL 8.6?

A few other possible things to try:

Are the codeready-builder repos enabled as needed for EPEL 8? (https://docs.fedoraproject.org/en-US/epel/#_el8)
Is the repo medata old?  Try dnf clean and then yum install trafficserver

@jeredfloyd  I'm getting the below error
Error:
Problem: conflicting requests

nothing provides libhwloc.so.15()(64bit) needed by trafficserver-9.1.2-7.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

@vgrme That's very strange.  Can you give me the results of these commands, in this order?
subscription-manager list
dnf clean
dnf repolist enabled
dnf whatprovides libhwloc.so.15
dnf whatprovides trafficserver
rpm -qi hwloc-libs
rpm -qi trafficserver
dnf install trafficserver

Hey @vgrme -- are you still having problems?  What are the results of the commands above?
Also note that I've pushed out a new -8 build that makes some changes to OpenSSL usage to support RHEL 9.  This shouldn't affect anything about hwloc, though.

Hi @vgrme -- can you provide the ouput of the commands in https://github.com/apache/trafficserver/issues/6855#issuecomment-1163047602 ?  Otherwise I will close as can't reproduce.


Analytics: register SDK language and data source

Closes https://github.com/rerun-io/rerun/issues/396
Contains a bug fix for what SDK the log events originate from (we would before always set Python SDK as the source).
Also contains a new event new_data_source which contains the field data_source which can be any of:

file (.rrd)
sdk (likely show())
ws_client (likely spawn())
tcp_server (likely connect())

Also renames the event data_source_opened to new_recording, which is more descriptive (multiple recordings could, theoretically, stream through the same data source).
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[ ] I've included a screenshot or gif (if applicable)
[ ] I've added a line to CHANGELOG.md (if this is a big enough change to warrant it)

I don't think we should go with the name new_recording since it is easy to confuse it with "created new recording" when we actually mean something like "viewer opened new recording".  I'd prefer open_recording


copying forwarded port in embedder side doesn't work

VSCode Version: 1.49.0
OS Version: any

Steps to Reproduce:

from [https://github.com/codespaces] create a codespace and connect to it
try forwarding a port (any port)
on the Ui side, right click and choose "Copy Address"

expected: you should see an address like https://<guid>-<port>.apps.<subdomain>.codespaces.githubusercontent.com/
actual: you will see <IP_ADDRESS>:<port>

Does this issue occur when all extensions are disabled?: No

FYI @alexr00

I debugged and found that the embedder is returning the wrong value here.

shouldn't we follow same logic as openPortInBrowserAction for copy as well?


Perform external usability test and improve UX of developer portal

Problem description
After releasing the 5.11.0 with the fresh developer portal. We need to do usability testing and get feedback from users.
Preferred Solution
After collecting the usability testing data we need to work on fixing the identified issues.
Sub Tasks

[ ] Carry out a usability testing
[ ] Fix identified issues

Effort FE::15

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Remove file: TSMo3.v02.gra from list of files to link (inexistent file).

This file was rever used by any fizhi experiment
On dec 26, 2011, file TSMo3.v02.gra was removed from: fizhi-cs-32x32x40/input
got removed from prepare_run of other fizhi experiment:fizhi-cs-aqualev20
few months later (2012-03-11) but forgot to remove it from this prepare_run.

Please check that the PR fulfils our requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What changes does this PR introduce?
minor bug fix that was triggering a harmless error message
when running this experiment.
What is the current behaviour?
(You can also link to an open issue here)
What is the new behaviour ?
running  experiment: fizhi-gridalt-hs is now cleaner
Does this PR introduce a breaking change?
No
Other information:

LGTM


[FLINK-14478][python] optimize current python test cases to reduce test time.

What is the purpose of the change
This pull request optimizes current python test cases to reduce the test time from 24 minutes to 16 minutes.
Brief change log

Limit parallelism of ExecutionEnvironment/StreamExecutionEnvironment used in test cases to 2 except for test cases that use CSV table sink.
Remove some unnecessary tests from PyFlinkBlinkStreamUserDefinedFunctionTests and PyFlinkBlinkBatchUserDefinedFunctionTests.
Add durations option in tox.ini to display the time used in each test case.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@WeiZhong94 Thanks a lot for improving the test.  Besides, it seems we can also use pytest-xtool or other tools to run the tests parallelly. Have you ever tested with it?

@hequn8128 Thanks for your comments! I have tried running the tests with pytest-xdist and pytest-parallel. They reduce the test time significantly in my local machine, but not work on travis (The test time even increased). I guess that travis allocates too few resources to each task so that parallel execution does not lead to higher performance.
The build of using pytest-parallel is https://travis-ci.org/WeiZhong94/flink/builds/602249179
The build of using pytest-xdist is https://travis-ci.org/WeiZhong94/flink/builds/602626771

@hequn8128 I have moved those tests to PyFlinkBlinkStreamUserDefinedFunctionTests in the latest commit.

@hequn8128 Thanks for your comments! I have tried running the tests with pytest-xdist and pytest-parallel. They reduce the test time significantly in my local machine, but not work on travis (The test time even increased). I guess that travis allocates too few resources to each task so that parallel execution does not lead to higher performance.
The build of using pytest-parallel is https://travis-ci.org/WeiZhong94/flink/builds/602249179
The build of using pytest-xdist is https://travis-ci.org/WeiZhong94/flink/builds/602626771

Thanks for your investigation! I will merge this PR now as it reduces the test time from about 28min to about 12min. We can do more investigation about those parallel test framework later.
Best, Hequn

Will resolve the conflicts and merge this.


[Site] Updated Home Page

Description
Updated the Home Page Section style as given in mockup design.
Changes Made

Updated Background color
Updated NavBar Color
Updated Buttons color
Updated Image position
Take care of responsiveness for smaller devices

After Changes

Notes for Reviewers
Let me know if there are any other changes we can make.
Signed commits

[x] Yes, I signed my commits.

@NikhilSharma03 have you also changed the logo of community bridge to LFX on this PR?

@NikhilSharma03 has done a nice job here. Tagging with issue/willfix

What is the status on this one?

@Mr-DG-Wick this PR is on hold for later, this is basically for dark mode on the website.

Gotit 👍🏽

A great effort by @NikhilSharma03, @Mr-DG-Wick would you like to tie this off?


Strange checkpoints at the end of IbisLocalSender execution

This issue was found by examining a report in the debug tree that contains an IbisLocalSender.

There are a few checkpoints that I do not trust:

SessionKey exitCode: 0 - I would expect a HTTP code like 200, because that is what you provide in the  element.
SessionKey exitState contains some HTML as value. I would expect "SUCCESS", like the state in an  element.
success: This should be a value, not the name of a checkpoint.
forwardName: 0 - I do not think there is a forward named "0".
errorMessage: exitState=SUCCESS - Looks strange to me.

This issue replaces https://github.com/wearefrank/ladybug-frontend/issues/469.

Superseeded by FF! issue https://github.com/frankframework/frankframework/issues/7260.


Set translated slugs

Let's say I have this page in two languages:

/contacts
/it/contatti

How can I set translated slugs inside a page? Translated slugs comes from an API call from a headless CMS

There's a PR for this, it is being worked on by @Alexandre-Fernandez : https://github.com/yassinedoghri/astro-i18next/pull/49

Hi there, any news on that PR?

Hi there, any news on that PR?

Hey, I'm currently working on it. I'll probably be releasing tomorrow.

@yassinedoghri wow, amazing mate. This would be so useful, thanks.


Define policy regarding use of minCardinality and minQualifiedCardinality 0

Spinoff of #582.
Discussion:
Policy moving forward needs to be defined. Possibilities are:

Use a scopeNote; since min 0 has no inferencing power a scopeNote is equivalent. Use SHACL for data validation if needed.
Continue to use min 0.

@Jamie-SA: it's useful because we don't have SHACL for gist.

@rjyounes What is the status of this?

This has been done. We have agreed to use someValuesFrom rather than min(Qualified)Cardinality. Closing the issue.


test: add test proving limit/offset for bigint is fixed

Current dependencies on/for this PR:

main

PR #105   👈

This comment was auto-generated by Graphite.


Feature/2761/null alias

For dockstore/dockstore#2761
Eagerly load the aliases object. Shouldn't be too bad since it's not collection within collection. Can revisit if it ever does.
Also threw in the ntp (no transfer progress) to shorten logs.

Also threw in the ntp (no transfer progress) to shorten logs.

:+1:

A little too broad, but the tests are a good start.
Would prefer the use of something more focused like running Hibernate.initialize or similar to pull all aliases only when a single organization or workflow is pulled by ID, but not all aliases when grabbing a number of organizations or workflows.
i.e. this should also add a test to make sure that hitting https://dockstore.org/api/static/swagger-ui/index.html#/containers/allPublishedContainers doesn't grab all aliases for all published tools

I thought the intent was that it should grab all the aliases the make it searchable.

Adding Louise because not sure what use case the issue is trying to solve.

A fair question:
My response is based on the following assumptions/suggestions

A user wants to see the aliases for a tool/workflow when visiting that specific tool/workflow
There's no point in looking at all aliases for a group of tools/workflows or to re-phrase, it wouldn't be useful enough to warrant the potential performance hit
If the aliases are just needed to populate search (ES) to be searchable, then they should only be grabbed when entries are added to ES

I assume that current organizations should be searchable by the alias which means the get-all-organizations endpoint should return all aliases.
I also assume that we're adding something similar for my-entries.
There is currently no discernable performance impact (heavily overshadowed by eager versions)
At this point, all the major endpoints are loading it so, might as well make it eager.

@Ldcabansay  I think we probably need more feedback on the use-case for this to figure out the optimal approach

I think the main use case is to be able to search by alias, similar to how we can search by labels. We could probably optimize just for this now.
I'm not sure how useful it would be in general to display to users all aliases a particular object has, but it could be useful--somewhat similar to how Zenodo shows related identifiers. Could probably implement this later.


virtual scroll getting stuck

I have implemented a virtual scroll. The data in the virtual scroll is refreshed every-time, and then I scroll to the top of the virtual scroll.

     <ion-card style="width: 100px;
                    border-radius: 5px;
                    border: 0.55px solid #c8c7cc; box-shadow: none !important">
                 <ion-avatar style="width: 100px; height: 100px;">

                  </ion-avatar><ion-item style="border-bottom: 0.55px solid #c8c7cc; padding-left: 5px !important;" *ngIf="sortBy == 'firstname'">

{{ item.firstname }}

{{ item.lastname }}

                  </ion-item><ion-item style="border-bottom: 0.55px solid #c8c7cc; padding-left: 5px !important;" *ngIf="sortBy == 'lastname'">

{{ item.lastname }}

{{ item.firstname }}

                  </ion-item>
            </ion-card>

</virtual-scroller>

But if the virtual scroll is already on the top, it gets stuck, and does scroll or move anymore. When I switch tabs or perform a hard-coded based- scrollTO method to scroll a little and then come back to the top, it works fine. Did anyone else experience something similar?

@luqmaants I'm seeing something similar. Here is what i'm seeing.
On a list that I have virtual scrolled I scroll down a little bit so that the start index is no longer 0. If I then quickly scroll back up and then try to scroll back down the scroll behavior is now stuck. The list will not scroll up or down until I pause for a second and/or move the mouse then continue scrolling. I can also reproduce this on the sample page https://rintoj.github.io/ngx-virtual-scroller/samples
At least scrolling starts to work again after pausing for a second, but it is pretty annoying. I hope this can be fixed.

Issue still persists, any updates?


Unable to update the road centre line of an existing Proposed address.

originally opened as part of #229 and the below is copied over.
Issue 2 - Unable to update the road centre line of an existing Proposed address.
Steps to reproduce the error message is as follows:

Search for an existing proposed address.
Click on the Update AIMS Feature button.
Click on the button used to select a new road centre line.
Select a different road centre line and submit.

This causes issues because if a road centre line needs to be changed, the address has be retired and then re-entered.  The user has to attach the address to the correct centre line and make it proposed again.

reading this again it makes sense to manage as part of #229

The UI had a check put in place to stop addresses being updated to proposed (see #213). Its need at the UI level is questionable.
Triage-ing this issue will begin with removing this check and performing this action against the API to confirm the API allows this action. If so, removing the UI check should be considered

I have built a test environment and confirmed the UI is blocking this action that the API will allow.
The below code can be safely removed from the UI to allow AIMS users to update proposed address properties.
https://github.com/linz/QGIS-AIMS-Plugin/blob/e1303f21924f5ddea87959e9efb1308c3ae4f4c9/AimsUI/AimsClient/Gui/UiUtility.py#L380-L383
This will not have any adverse effects as the API checks for addresses being changed from current to proposed, a situation that may lead to data corruption (see #229)
@MarksNgahi if you would like this improvement made to allow the updating of proposed address properties, please request this work via @TrentGulliver as he will have a better understanding as to how this piece of work would fit into the addressing programme.
This would involve:

Removing the above check in the UI
A release being created and pushed to the LINZ plugin server
The addressing team performing regression testing

Note #213 is related to this.


Add measurement files, update readme, and setup repo

What does this Pull Request accomplish?
Saved the measurement files, pyinstaller setup, and NI Package Builder configuration. Added demo files and sample PinMap.
What testing has been done?
Manual tested measurement, pyinstaller, and package locally in InstrumentStudio.

Looks good. For future phase, we should consider adding the driver into the name of the measurement if it's only going to support a single driver and so we are consistent in the naming of the measurement with the repo it's in. We'll also want to update the tags for the measurement so usability is more clear when creating a panel from scratch in IS.


Use blocking thread pool in the Prometheus metrics

CollectorRegistry.clear, CollectorRegistry.register, CollectorRegistry.unregister may block threads so it's better to use blocking thread pool.

What sort of blocking do they do?  A synchronized lock?

@rossabaker Yep, it uses synchronized locks.


chore: remove entry only on same endpoint

Purpose
We have bug that @mfrankovi found that we drop peer even if there was successful ping to another endpoint
How does the solution address the problem

Changes made

prnet cleaned-up successfully


Installation fails if performed in a pipenv

The installation process fails at the migration level, when executing python manage.py migrate defender at this point the process fails due to an unexisting module:
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'defendercore'

Version: Pypi (Installed using pipenv install django-defender), redis is installed as well.

That is weird, I'm not sure where defendercore is coming from. Can you give more of the stack trace?

Double check you have a comma after defender in your settings.INSTALLED_APPS:
INSTALLED_APPS = [
...
'defender',
'core',
...
]

I had it, installed. I ended dropping if in favour of django-axes, sorry for the late response :)


how to inject multiple OP_RETURN outputs in one transaction

In a bitcoin's transaction, Whether it can contain more than one OP_RETURN, it is beneficial to generate multiple omni transactions in one transaction. I think it can improve transaction efficiency.
@dexX7

Hi @wupeaking,
you can manually add multiple OP_RETRURN outputs with the raw transaction RPC omni_createrawtx_opreturn (see a walkthrough with example here).
But: these transactions won't be relayed or mined by other peers, because only on OP_RETURN per transaction is considered "standard" by the rest of the network.

Dexx has a Send to Many tx in the roadmap, we're all looking forward to being able to use that.
The design there, is to insert payload referring to more outputs in the same OP_Return.

This is correct. There are a few ideas to add this to Omni Layer.
One idea is documented here: https://gist.github.com/dexX7/ba45d52d8edd084357253d93360e1519

This is correct. There are a few ideas to add this to Omni Layer.
One idea is documented here: https://gist.github.com/dexX7/ba45d52d8edd084357253d93360e1519

How to create a transaction by this way? can it specify recipients address？


Code generation gets confused with PK and FK on the same field

At least with SQLite, when a table has primary key and foreign key constraints defined on the same field, the code generation doesn't generate the field on the model (I guess because it thinks it's a relation).
An example schema:
CREATE TABLE a (id INTEGER PRIMARY KEY);

CREATE TABLE b (
    id INTEGER PRIMARY KEY,
    some_other_field TEXT,
    FOREIGN KEY (id) REFERENCES a (id)
);

No relation fields are generated directly on the model. The relation should be attached to the R field which would be of the type modelR (dependendent on the name of the model).

Is there no R field on the struct? If there is, what does it look like?

No, the R field looks fine (I guess, still learning this part of bob). But the problem is that the ID field doesn't get generated on the model, and looks like other parts of code are expecting it and things don't compile.

Fixed and released in v0.20.1

Fixed and released in v0.20.1

Thanks for the quick response! So far, I'm pretty impressed with the quality of documentation and good reasoning behind how things are put together, congrats!


Support Protocol Buffers serialisation.

It would be useful if we could have Protobuf support in dart-rpc, or even any serialisation methods other than JSON, maybe specify which one to use (like a content-type) using the Accept request header.
Even though JSON is most broadly used, for many situations, others are required as well.
See related StackOverflow question

Supporting protobuf and in general having a way to plugin serialization is something we have discussed. It would be very nice to have, but it is not planned for the near term.

Has this been revisited?  I'd like to consider using Dart for client-side work, but my clients must support protobuf grpc gen.

You can already use generated grpc models with dart client with whatever server language.
You can use the fromJson ctor of the generated model.
Look at the grpc-dart repos and more precisely to this like on your model.

I see.  Thanks for clarifying!


Character.AI

Good day, Rubiksman78
I am able to get your Mod working now and I wanted to thank you for going through the trouble of creating it.
I wanted to know if there was any way to change the @Snikm Monika Character.AI for the @Geechan Monika Character.AI?

Awe I figured it out.
I ended up looking in the main.py folder, at lines 214-216 for the characters_pages.
my main confusion was when I used the run.bat file and it brought up the choose AI part of the login in screen.
I assumed that you could only pick from characters 0 or 1 if you had the "No choose character selected"
I fixed it by changing both characters into:
https://beta.character.ai/chat?char=EdSSlsl49k3wnwvMvK4eCh4yOFBaGTMJ7Q9CxtG2DiU
Which is the AI created by @Geechan.
In my opinion, her responses have more articulation than @Snikm's version. Snikm's Monika uses more emotive language and has a harder time understanding what the player is talking about.
Anyway, thank you so much, Rubiksman78! I'm really happy that you had already incorporated @Geechan's work into the submod.
Fantastic work!


Clean Pull Requests

Summary
There's a few pull requests at the bottom there merging into f4-port, or perhaps are not relevant anymore. They should probably be deleted.

All have been closed. Please re-open if I've made a mistake.


Release v0.1.0a0

@webknjaz Could you drop in the PyPI key? Also, if possible, it would be nice to rename the project without the underscore, for consistency with other projects.

Also, if possible, it would be nice to rename the project without the underscore, for consistency with other projects.

Not all of the projects use dashes, though. FWIW the dist name is controlled with whatever is in setup.cfg. PyPI, pip and the rest of the ecosystem apply normalization. Though, I'm not sure that it's possible to update the canonical dist name on PyPI. Anyway, it should be possible to use either dash or underscore when installing with pip.

It seems like PyPI's canonical form might already be dashed internally.

Alright, the secret has been provisioned.


Space wizard ui fixes

Space name is the default repo name
If the user changes this, then used as new default repo name  if the user steps through the wizard
space name as default repo name when opening existing space

There were the following issues with your Pull Request

Commit: 616e4014666ad367d0444fa84b02b22ae2f8b19d
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

Can one of the admins verify this patch?

@mitchharpur snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-936-fabric8-ui.int.rdu2c.fabric8.io

There were the following issues with your Pull Request

Commit: cce0f786efd9628cbc892897f6465090572a68c6
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

@mitchharpur snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-936-fabric8-ui.int.rdu2c.fabric8.io

There were the following issues with your Pull Request

Commit: cce0f786efd9628cbc892897f6465090572a68c6
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

@mitchharpur snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-936-fabric8-ui.int.rdu2c.fabric8.io

[test]


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2623

Questions ?
Please refer to the Backport tool documentation


Add a storage-agnostic cache manager to backend-common

Signed-off-by: Eric Peterson<EMAIL_ADDRESS>Hey, I just made a Pull Request!
I was hacking internally on updates to the TechDocs backend that could really use a simple, performant, cache store.  I wanted to get the ball rolling on how we want to support caching across Backstage before iterating on and opening up the improvements to the TechDocs plugin specifically.
Proposal is to use an existing storage-agnostic cache library: Keyv.  This PR adds config schema and support for an in-memory key-value store (pre-packaged with keyv) as well as memcache.
Rather than exposing the cache clients returned by Keyv directly, I'm wrapping them in a CacheClient interface for a couple of reasons:

The wrapper handles some annoying stuff that developers may run into (e.g. key normalization)
We may not want to tie ourselves to Keyv long-term, so this wrapper interface gives us a way to transition to something else if we need to.
We can open up the interface to more advanced cache patterns on top of simple get/set/delete calls.

Usage would be something like the following:
# app-config.yaml
backend:
  cache:
    store: memcache
    connection: user:pass@cache.example.com:11211

// packages/backend/src/plugins/some-plugin.ts
export default async function createPlugin(env: PluginEnvironment) {
  return await createRouter({
    cache: env.cache,
    logger: env.logger,
  });
}

// @backstage/some-plugin-backend
export async function createRouter(options: RouterOptions): Promise<express.Router> {
  const logger = options.logger;
  const cache = options.cache.getClient();
  const router =  router();

  router.use(async (req, res, next) => {
    const cached = await cache.get(req.path);
    if (cached) {
      res.status(200).send(cached);
    } else {
      next();
    }
  });

  router.get('/some/path', async (req, res) => {
    const someString = await somethingExpensive();
    res.status(200).send(someString);
    cache.set(req.path, someString);
  });

  return router;
}

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Tugboat has finished building the preview for this pull request!
Link:

https://pr5551-t8y4hvs1ytrsmqluyvm0b50audkh05yp.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/608daf2a088413ab03e9f6d7

Tugboat has finished building the preview for this pull request!
Link:

https://pr5551-t8y4hvs1ytrsmqluyvm0b50audkh05yp.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/608daf2a088413ab03e9f6d7

Oh and a final thought - is it time to put this in common already? Or shall we take the exact same code inside the first consumer and let it incubate a bit until we see the need in more places, and then see if it's evolved or had fixes until then?
You know what they say, about only consolidating until you see at least three usages :)

Thanks for the thorough review, @freben!  Ended up implementing most/all of your rec's in some form.
And regarding...

is it time to put this in common already? Or shall we take the exact same code inside the first consumer and let it incubate a bit until we see the need in more places, and then see if it's evolved or had fixes until then?
You know what they say, about only consolidating until you see at least three usages :)

Yeaaaah I know what you mean.  But the mental overhead of implementing only in TechDocs, then iterating, then moving into common, then deprecating, and then eventually removing...  Is not super appealing.
I'm thinking caching is a fairly universal concern that has a fairly well-understood interface; I figure as long as it's set up in a way where the implementation can be swapped out without much concern from users, seems okay to just start in common?

A while back I created a simple caching system in our backend specifically for custom catalog processors to cache API results for external system lookups. It's simple in memory version based on a TTL for the external API call result (backed by keyv. Looking through this, it seems like we could easily replace that custom cache with this using the optional TTL on the set call.

(backed by keyv)

Ooooh, I wish I'd seen that.  Looks like a little better tended-to ecosystem than cache-manager.

We also have some simple internal in memory cache interface. When I look at the libraries they often provide simple get and set operations. But often you have more high level patterns that you implement on it. Like read-through pattern, different ways to handle failures (like returning stale data), etc...  This is probably not part of this PR but would be cool to have out of the box, build on the interface provided by this PR.

We also paired it with opossum to implement a circuit breaker. In our case the external lookup is triggered by each catalogue entry so if the external service is down or overloaded already we don't want to keep hammering it. The combination of the caching and circuit breaker has helped a lot.

This is probably not part of this PR but would be cool to have out of the box, build on the interface provided by this PR.

@iamEAP following on from what @freben mentioned, this is kind of the reason i'd be hesitant to push this straight into common as there's some usage patterns that we should try and dogfood first before creating breaking changes for people.
Maybe we can get @fox32 to open source some of his patterns with this 👍

We also paired it with opossum to implement a circuit breaker. In our case the external lookup is triggered by each catalogue entry so if the external service is down or overloaded already we don't want to keep hammering it. The combination of the caching and circuit breaker has helped a lot.

Oh opossum looks cool too, we went with cockatiel.

(backed by keyv)

Ooooh, I wish I'd seen that. Looks like a little better tended-to ecosystem than cache-manager.

I mean it's not too late ... :)

Aaaalright, lemme find some time swap out the underlying client (might be a few days yet, though).

there's some usage patterns that we should try and dogfood first before creating breaking changes for people.

Yep; maybe we can land on a really simple base interface and then augment from there?
Love the ideas (and existing implementations) re: higher-order patterns.  Perhaps with that in mind, I can go back and make the base get/set/delete operators super transparent, and any other logic that doesn't just pass through between caller/client, we'll reserve for additional methods (e.g. client.readThrough('key', () => {}), etc)

Re-implemented! And behavior simplified.


Optional null value with model_fields_set

Environment:

Python version: 3.12
Operating system: Windows 11
Flask version: 3.0.0
flask-openapi3 version: 3.0.1

That's the only way of declaring a field which will be:

Not required
Accepting null values

from uuid import UUID

class PatchRequest(BaseModel):
    sth_id: Optional[UUID] = None

The problem is when you want to set this field in a PATCH request as null:
{
    "sth_id": null
}

this if condition evaluates to false:
if 'sth_id' in patch_request.model_fields_set:
    # do sth

In 2.x version of the flask-openapi3 it was possible to make it work, because the field declaration for such situation was different (without "= None").
So what I'm trying to achieve is a field which will be:

Not required
Accepting null values
Present in model_fields_set when it's value in the request is set as null

I can't seem to reproduce your issue. body.model_fields_set equals to {'sth_id'} in flask-openapi3 v2.x and v3.x.
class PatchRequest(BaseModel):
    sth_id: Optional[UUID] = None

@app.patch("/book")
def patch_book(body: PatchRequest):
    print(body.model_fields_set)  # {'sth_id'}

    return "ok"

Sorry, I actually meant sth different.
When you declare a field in this way
from uuid import UUID

class PatchRequest(BaseModel):
    sth_id: Optional[UUID] = None

and your PATCH request won't contain this field at all, then it will be present in model_fields_set.
This means there is now no option to differentiate between provided and not provided value in the request for not required fields.
For example:

User wants in to set sth_id to some actual ID.
Then in another request, the user wants to set the ID to None
And then in a 3rd request, the user wants to set some other fields without specifying the sth_id field in the request at all, because it was not changed.
In the 3rd scenario, it's currently not possible to tell if the field was provided in the request or not.

Regardless of whether it is a v1 or a v2 version, sth_id in the fields_set absence does not depend on whether the "= None" part is declared or not, only whether the sth_id is passed or not.
You need to provide executable code examples, otherwise I can't figure out what the problem is.
from typing import Optional
from uuid import UUID

from pydantic.v1 import BaseModel

class PatchRequestV1(BaseModel):
    sth_id: Optional[UUID]
    # There is no different
    # sth_id: Optional[UUID] = None

patch_request = PatchRequestV1()

print(patch_request.__fields_set__)

from pydantic import BaseModel

class PatchRequestV2(BaseModel):
    sth_id: Optional[UUID] = None

patch_request = PatchRequestV2()
print(patch_request.model_fields_set)


workflow: ibmcloud e2e-tests base on iks clusters

add e2e-test base on IKS with s390x worker nodes
build podvm inside container
provision/clean e2e-test resources via e2e-go-framework

Fixes: #828

Sample jobs https://github.com/liudalibj/cloud-api-adaptor/actions/workflows/daily-e2e-tests-ibmcloud.yaml

both amd64 and s390x e2e-test are passed https://github.com/liudalibj/cloud-api-adaptor/actions/runs/4721862699
amd64 passed and s390x failed https://github.com/liudalibj/cloud-api-adaptor/actions/runs/4721711282


Get components from generated private key

Hey. Thanks for your great library. I'm integrating ursa in OpenPGP.js for native RSA under node. I saw that there is a way to create a private key from components:
ursa.createPrivateKeyFromComponents(modulus, exponent, p, q, dp, dq, inverseQ, d)

But is there also the other way around ... to get the components from a generated private key? I need the following components:
https://github.com/openpgpjs/openpgpjs/blob/master/src/crypto/public_key/rsa.js#L198-L204
Thanks!

Ha! Just saw there is already an issue: https://github.com/quartzjer/ursa/issues/121


Rancher being insistent about having stopped containers.

Ok, I'm at a loss... Rancher seems to like randomly creating copies of containers that are running quite happily.
For instance I have one host that insists on having a stopped copy of the ipsec router and ipsec containers.  If I delete them it'll recreate them, start them, then stop them again.  Completely ignoring the running ones.
I have the same thing happening with healthcheck containers and even most of my Prometheus stack.
I don't know where to even start debugging this since I can't work out which part of rancher is doing it.  Is it a healthcheck thing?  A metadata confusion?  Scheduling trying to enforce requirements improperly?  Where should I start looking for some kind of reasoning for this?

Useful
Info

Versions
Rancher v1.3.3 Cattle: v0.175.9 UI: v1.3.5

Orchestration
Cattle

Sometimes the stopped containers appear in the stack...

Sometimes they appear as stand alone...

Sometimes they remember they're supposed to be sidekicks but not that they're in a stack...

My first guess would be multiple server containers running at the same time because of --restart=always instead of --restart=unless-stopped and they're pointed at the same database

I can see the logic there but I've double checked and there's not two running.

@vincent99 I guess the documentation leads to this interpretation when setting up HA:

Running Rancher server in High Availability (HA) is as easy as running Rancher server using an external database, exposing an additional port, and adding in an additional argument to the command for the external load balancer. (Source: http://docs.rancher.com/rancher/v1.2/en/installing-rancher/installing-server/#multi-nodes)

I assumed I can just connect two server to the same external database and rancher "will just work".

@kaithar Did you figure this out, can we help debugging?


here is my Itc EDA app

🛠 Related Issue

Closes #[issue_number]

📝 Description

[Provide a concise description of the changes. Include the purpose and any relevant context or details.]
🔍 Type of PR

[ ] 🐛 Bug fix
[ ] ✨ Feature enhancement
[ ] 📚 Documentation update
[ ] 🛑 Other (specify): _______________

📸 Screenshots / 🎥 Videos (if applicable)

[Attach screenshots or videos]
✅ Checklist

[ ] I have performed a self-review of my code.
[ ] I have read and followed the Contribution Guidelines.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.

ℹ Additional Context

[Include any additional context or information that might assist reviewers in understanding the changes]

coming same only because stock data set patter is same

it will be different

ok sir I will give

sir now it correct ??


Splitting the Repository Up

This repository has a few crates inside it: imgui; glium and glow renderers; and sdl2 and winit platform support.
I propose here that we should move all the crates which aren't imgui out of here.
There are a few reasons for this, but first and foremost, it will make imgui significantly easier to maintain. Although it is perfectly reasonable to update imgui without updating other platform dependencies, in practice, things tends to all go at once. It would be nice for imgui updates to not necessarily depend so much on the platforms.
Secondarily, it will simplify issue creation tremendously. Users won't be reporting to an omni-repository, but rather, to individual repositories.
We can see that in imgui-wgpu, which is a successful example we should follow.
What do you all think?

I'm in favour of this.
Part of this is we should decouple the versions of imgui-rs and the support/renderer modules (their release cycles should be independent - e.g the winit changes didn't necessitate any change in imgui-rs itself). We could do within the same monorepo approach, but as you say there's other organization benefits to having them as separate repos
Another (rare) benefit would be deprecating repos like happened with gfx - if they are separate repos, they can just be wrapped up and archived, whereas currently we have to move the code elsewhere (which is a bit more work)
It also would make it "cleaner" if someone was to take over maintenance of a specific renderer-integration, and if was value/interest in moving imgui-wgpu-rs etc into the imgui-rs org
The only downside I can think of is the examples - since they rely on a renderer, they also either need to move to a separate repo (which makes keeping them in sync a tiny bit harder), or have a weird circular dependency. However practically I think having them in a separate repo would work okay - there shouldn't be a huge amount of churn in those examples
I think @thomcc was a big proponent for the monorepo approach - he may have some opinions (or not, as he's very busy with other things!)

Exactly -- @dbr , I don't know about you, but I actually use none of our integrations personally -- my projects at work use their own integrations, since it tends to be easier. These repositories should have maintainers who are more personally invested in them, whereas my interest is in imgui itself! To continue to use the imgui-wgpu repository as an example, it was started by wgpu affiliated folks primarily. I think having many of our repositories have more support from the relevant platforms would be ideal -- in practice, we don't really use very many platform specific features, it's more just the types tend to come out platform particular

I think it's a good plan but there is one issue that I've been running into when trying to go between versions of imgui-rs.
Since imgui-sys sets the links property in the Cargo.toml, when compiling a dependency that has a dependency on imgui-rs, cargo ends up breaking. Which means that if you pull one dependency using imgui-rs, all dependencies using imgui-rs have to use the same version. I've managed to get SxS imgui-rs working (for example 11 and 12 in the same project behind feature flags) but I had to fork the repo, rename imgui to imgui_xx and then change all the dependents to reference the _xx version (including imgui-wgpu).
I'm not sure what a solution would look like or how to address this problem but I think it would support the goal of making imgui-rs is easier to maintain.

ahh @juliusl good point. I think leaving imgui and imgui-sys in the same repository is very sensible. supporting having two different imgui-rses does sound very challenging and niche to me, so accepting that hard requirement seems fine

supporting having two different imgui-rses

It's not necessarily about having two different imgui-rses (and I think for the most part this might get solved w/ the repo split) and more about the dependencies outside of imgui-rs. Say for example you need a more recent version of winit or wgpu.
Since both these libraries have a history of having breaking changes between apis, it's helpful to feature-flag them while other dependencies catch up and while they take time to stabalize.
If you're on an older version of imgui-rs/imgui-rs-winit that means you might need an updated version so that you can test these changes with but you can't nesscarilly move forward w/ all your dependencies yet so you want to feature-flag the updated stack.
So for example something like this:
imgui12 = { package = "imgui", version = "0.12.0", optional = true }
imgui11 = { package = "imgui", version = "0.11.0", optional = true }

imgui_winit_support_12 = { package = "imgui-winit-support", version = "0.12.0", optional = true }
imgui_winit_support_11 = { package = "imgui-winit-support", version = "0.11.0", optional = true }

winit29 = { package = "winit", version = "0.29.0", optional = true }
winit27 = { package = "winit", version = "0.27.0", optional = true }

[features]
stable = [ "dep:imgui11", "dep:imgui_winit_support_11", "dep:winit27" ]
vnext = [ "dep:imgui12", "dep:imgui_winit_support_12", "dep:winit29" ]

The problem is that cargo only lets you link one version of a crate at a time, so the above will fail to compile even if you're not even referencing both versions at the same time. Just because the second version is in the manifest at all will cause cargo to fail. The only solution I've found that doesn't fracture my repo was to rename the package name of the later version of imgui to imgui_xx and than cargo is happy again.
This is friction being caused by cargo and not anything imgui-rs is doing wrong (I think the openssl based crates have run into this before as well).
Not trying to push for a solution, but I just wanted to call out a realistic complication I'm running into downstream.

I have made a draft PR for this repository. Equally, the other split crates now exist in imgui-rs
https://github.com/imgui-rs/imgui-rs/pull/793
I'll move discussion over to this PR going forward!

Closing as done!


how to create index with crawl website?

Is your feature request related to a problem? Please describe.
how to create index with crawl website?
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Need understand automated index process to use  MeiliSearch

Hello @chintan9 I'm not sure to understand your need (could you explain it more if I didn't 😄),
but we made a scrapper to index websites in meilisearch,
Is this fit your need ?


Add ability to view teammate stats

Maybe a modal or tooltip?

why not just reenable the stats that was removed here

We removed those because most people didn't want to see the stats, and they were taking up too much space. So my thought was to have a little tooltip or modal to show the stats instead of always showing them

Maybe a switch can be added to the setting page to meet the needs of different users? Now the setting page is mainly a database manager. I think we can make use of it to provide more customizable experience.

Probably just add an accordion with a header, no need to have a additional external toggle.


Batch labels for training and inference through TED to reduce memory consumption

Proposed changes:

Fixes https://github.com/RasaHQ/rasa/issues/8025

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

could you please rebase it to policy-train-in-chunk, since I don't think we're going to properly finalize core chunking in the near future

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Daksh seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing for now, I think this is not relevant anymore


Add RefSeq Cut-Offs to JSON File, Show Species Cut-Offs

Overview

Adds RefSeq cut-offs (always)
Adds species cut-offs when available
Harmonizes reports so they work better with both stdout and JSON
Updates tests

Example Outputs
Let me know if there's any concerns about having "null" in the JSON output, or if there's any ideas for how to handle it differently when the species isn't present and the RefSeq cut-offs are used instead.
Species Known
stdout
WARNING: The N50 is somewhat smaller than expected: 68259. The N50 lower bound is: 62773.95.
WARNING: The number of contigs is somewhat larger than expected: 99. The number of contigs upper bound is: 120.25.
WARNING: The L50 is somewhat larger than expected: 16. The L50 upper bound is: 18.0.
PASS: The assembly length is comparable to similar assemblies: 3446920. The acceptable assembly length range is: (3275866.4, 3679514.2).

JSON
    "Assembly Thresholds": {
        "N50 Low Error": 62773.95,
        "N50 Low Warning": 129926.6,
        "N50 High Warning": 476380.8,
        "N50 High Error": 476485.3,
        "L50 Low Error": 3.0,
        "L50 Low Warning": 3.0,
        "L50 High Warning": 9.0,
        "L50 High Error": 18.0,
        "Contigs Low Error": 21.0,
        "Contigs Low Warning": 30.0,
        "Contigs High Warning": 83.0,
        "Contigs High Error": 120.25,
        "Length Low Error": 3275866.4,
        "Length Low Warning": 3366843.8,
        "Length High Warning": 3576354.8,
        "Length High Error": 3679514.2
    },
    "NCBI RefSeq Exclusion Criteria": {
        "Minimum Length": 5000,
        "Minimum N50": 5000,
        "Maximum L50": 500,
        "Maximum Contigs": 2000
    },
    "Heuristic Evaluation": {
        "Success": true,
        "N50 Pass": true,
        "N50 Report": "WARNING: The N50 is somewhat smaller than expected: 68259. The N50 lower bound is: 62773.95.",
        "Contigs Pass": true,
        "Contigs Report": "WARNING: The number of contigs is somewhat larger than expected: 99. The number of contigs upper bound is: 120.25.",
        "L50 Pass": true,
        "L50 Report": "WARNING: The L50 is somewhat larger than expected: 16. The L50 upper bound is: 18.0.",
        "Length Pass": true,
        "Length Report": "PASS: The assembly length is comparable to similar assemblies: 3446920. The acceptable assembly length range is: (3275866.4, 3679514.2)."
    },

Species Unknown
stdout
The species is not present in the database.

WARNING: No assembly statistics available for the species!

PASS: The N50 is acceptable: 88901. The N50 lower bound is: 5000.
PASS: The number of contigs is acceptable: 104. The number of contigs lower bound is: 5000.
PASS: The L50 is acceptable: 15. The L50 upper bound is: 500.
PASS: The length is acceptable: 3939096. The length lower bound is: 5000.

JSON
    "Assembly Thresholds": {
        "N50 Low Error": null,
        "N50 Low Warning": null,
        "N50 High Warning": null,
        "N50 High Error": null,
        "L50 Low Error": null,
        "L50 Low Warning": null,
        "L50 High Warning": null,
        "L50 High Error": null,
        "Contigs Low Error": null,
        "Contigs Low Warning": null,
        "Contigs High Warning": null,
        "Contigs High Error": null,
        "Length Low Error": null,
        "Length Low Warning": null,
        "Length High Warning": null,
        "Length High Error": null
    },
    "NCBI RefSeq Exclusion Criteria": {
        "Minimum Length": 5000,
        "Minimum N50": 5000,
        "Maximum L50": 500,
        "Maximum Contigs": 2000
    },
    "Heuristic Evaluation": {
        "Success": true,
        "N50 Pass": true,
        "N50 Report": "PASS: The N50 is acceptable: 108383. The N50 lower bound is: 5000.",
        "Contigs Pass": true,
        "Contigs Report": "PASS: The number of contigs is acceptable: 89. The number of contigs lower bound is: 5000.",
        "L50 Pass": true,
        "L50 Report": "PASS: The L50 is acceptable: 12. The L50 upper bound is: 500.",
        "Length Pass": true,
        "Length Report": "PASS: The length is acceptable: 3970349. The length lower bound is: 5000."
    },

New output when species exists in the database:
{
    "Version": {
        "Software": "1.0.0a2",
        "Model": "2021-07-26",
        "Database": "2021-07-26"
    },
    "Technology": "Unidentifiable",
    "Species": "Legionella pneumophila",
    "Reads": {
        "Forward": "/home/eric/Downloads/NC_018140_reads.fq.gz",
        "Reverse": null
    },
    "Read Quality": {
        "Total Reads": 139700,
        "Total Bases": 34925000,
        "Q20 Bases": 33335178,
        "Q20 Rate": 0.9544789692197566,
        "Q30 Bases": 31867698,
        "Q30 Rate": 0.9124609305654975,
        "GC Content": 0.385883
    },
    "Assembly Quality": {
        "N50": 68259,
        "L50": 16,
        "Number of Contigs": 99,
        "Assembly Size": 3446920
    },
    "Heuristic Evaluation": {
        "Evaluation Method": "Species",
        "Success": true,
        "N50 Pass": true,
        "N50 Report": "WARNING: The N50 is somewhat smaller than expected: 68259. The N50 lower bound is: 62773.95.",
        "Contigs Pass": true,
        "Contigs Report": "WARNING: The number of contigs is somewhat larger than expected: 99. The number of contigs upper bound is: 120.25.",
        "L50 Pass": true,
        "L50 Report": "WARNING: The L50 is somewhat larger than expected: 16. The L50 upper bound is: 18.0.",
        "Length Pass": true,
        "Length Report": "PASS: The assembly length is comparable to similar assemblies: 3446920. The acceptable assembly length range is: (3275866.4, 3679514.2)."
    },
    "Assembly Thresholds": {
        "N50 Low Error": 62773.95,
        "N50 Low Warning": 129926.6,
        "N50 High Warning": 476380.8,
        "N50 High Error": 476485.3,
        "L50 Low Error": 3.0,
        "L50 Low Warning": 3.0,
        "L50 High Warning": 9.0,
        "L50 High Error": 18.0,
        "Contigs Low Error": 21.0,
        "Contigs Low Warning": 30.0,
        "Contigs High Warning": 83.0,
        "Contigs High Error": 120.25,
        "Length Low Error": 3275866.4,
        "Length Low Warning": 3366843.8,
        "Length High Warning": 3576354.8,
        "Length High Error": 3679514.2
    },
    "Machine Learning Evaluation": {
        "Success": true,
        "Probability": 0.92,
        "Report": "The probability of the assembly being a good assembly is: 0.92."
    }
}

Notably, "Evaluation Method": "Species" exists and the NCBI cutoffs are not shown.
New output when the species is not determined or not found in the database:
{
    "Version": {
        "Software": "1.0.0a2",
        "Model": "2021-07-26",
        "Database": "2021-07-26"
    },
    "Technology": "Unidentifiable",
    "Species": "Unknown",
    "Reads": {
        "Forward": "/home/eric/Downloads/cholerae.fastq",
        "Reverse": null
    },
    "Read Quality": {
        "Total Reads": 1303389,
        "Total Bases": 312635875,
        "Q20 Bases": 285035679,
        "Q20 Rate": 0.9117177579188569,
        "Q30 Bases": 273575582,
        "Q30 Rate": 0.8750613857094935,
        "GC Content": 0.482739
    },
    "Assembly Quality": {
        "N50": 108383,
        "L50": 12,
        "Number of Contigs": 89,
        "Assembly Size": 3970349
    },
    "Heuristic Evaluation": {
        "Evaluation Method": "Fallback",
        "Success": true,
        "N50 Pass": true,
        "N50 Report": "PASS: The N50 is acceptable: 108383. The N50 lower bound is: 5000.",
        "Contigs Pass": true,
        "Contigs Report": "PASS: The number of contigs is acceptable: 89. The number of contigs lower bound is: 5000.",
        "L50 Pass": true,
        "L50 Report": "PASS: The L50 is acceptable: 12. The L50 upper bound is: 500.",
        "Length Pass": true,
        "Length Report": "PASS: The length is acceptable: 3970349. The length lower bound is: 5000."
    },
    "NCBI RefSeq Exclusion Criteria": {
        "Minimum Length": 5000,
        "Minimum N50": 5000,
        "Maximum L50": 500,
        "Maximum Contigs": 2000
    },
    "Machine Learning Evaluation": {
        "Success": false,
        "Probability": 0.0,
        "Report": "The species is not present in the database."
    }
}

Notably, there are "Evaluation Method": "Fallback" and "NCBI RefSeq Exclusion Criteria". "Assembly Thresholds" do not exist.
To answer your question about the species @sciguy, the species should be listed near the top under "Species": "Unknown" (or the species name in particular, if it is known).


Adding Glasgow Caledonian University domain .caledonian

Adding Glasgow Caledonian University domain .caledonian

@Jochii96 I am sorry, the domain caledonian.ac.uk is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


[Project] Ability for Fiscal Hosts to "un-host" Collectives

User story
As a fiscal host admin, I want to be able to unhost Collectives under my host, even if the Collective admin is not available or responsive.
Best solution for this problem
Give fiscal host admins access to unhost a Collective, similar to the root action we have currently
Specs
See https://github.com/opencollective/opencollective/issues/3330#issuecomment-779706601

In our current model being a fiscal host does not give you full admin permissions on the collective, it only gives you the admin permissions on their finances (expenses, orders). I see a risk of host admin deleting a collective by mistake or after they get into an argument, and it seems to me that this permission is too broad for their role.
As the action to "Un-host" a collective is already planned, wouldn't that solve it?

Yes an un-host option would help in this case. That probably makes more sense.
So if a Collective admin is MIA and a host has to stop hosting it, the host admin can submit, approve, and pay an expense to zero the balance, and then un-host? If so that would be ok.
Does the host admin also have access to the 'zero balance' button on their Collective? If not, we won't be able to complete the above due to the lack of a '100% balance' option on expenses. There's likely to be a small amount left in the balance due to variable fees, preventing un-hosting.

Does the host admin also have access to the 'zero balance' button on their Collective?

Not at the moment, we can look toward enabling that in the new dashboard.

Bump!  In these cases, the Collectives were inactive and their admins nonresponsive.
A Host really needs this ability because they need to be in control of the Collectives they allow. For example, if the NZ charity host finds out a Collective was supporting non-charitable activities, we'd have to boot them out immediately or risk losing the whole entity's charity status.
Above we talked about access to "zero balance" since a Collective needs to be at zero to change host. But we have a workaround where the host admin can submit and pay an expense to achieve this, so the most important thing we need is an "unhost" option for after the Collective is at zero balance.
I suggest we make the "unhost" action a button or option on the Collective card on the Hosted Collectives tab of the Host Dashboard.

We have a design for that in https://www.figma.com/file/5pclePpILM2ja3aYsHuex7/[OC.com]-03-Admin-Panels-%2F-◉?node-id=9%3A37827:

Specs
API

[ ] In server/graphql/v2/mutation/HostApplicationMutations.ts, create a removeHost mutation:

[ ] Args: account, message (optional)
[ ] Can only be used by host admins or collective admins
[ ] Calls changeHost with newHostCollectiveId = null
[ ] If changeHost succeed, send an email. Include the custom message if there's one

Frontend

[ ] Implement the design proposal from https://github.com/opencollective/opencollective/issues/3330#issuecomment-779701300
[ ] Use the removeHost mutation previously created
[ ] Add E2E test in test/cypress/integration/29-host.dashboard.test.js

It's for legal/compliance reasons, practical reasons, and customer service reasons.  This is not a tenable situation for a Host as a legal entity. If a Collective violates their policies, what can they do? Also we are often trying to help people change Hosts or close down their Collective and the users are confused or nonresponsive so we can't help them.

Bump. This came up again today in support. A Host admin is trying to shut down their Host but they are stuck because there's an abandoned Collective that they are not admin of. This prevents a Host from being archived or deactivated, and the Host admin can't do anything about it.

This issue is becoming critical, especially in light of #4928
A Host right now needs to remove a Collective for violating their ethics policies, but there is currently no way for them to do it. I really think this is a key compliance/legal/policy risk and it's not fair to our Hosts to force them to keep Collectives hosted that they want to remove.

+1 ing as we manually unhost another collective today after a request...

Hi
🪴🪴❤🪴🪴

I feel a lot of tension around this feature. I'll be pushing a quick hack to add it to the root dashboard so that the rest of the support team can take action when it needs to be done.

[ ] @opencollective/design we need a link towards the latest design for this, the one previously shared doesn't work anymore
[ ] @hdiniz to synchronize with @opencollective/design this week to make sure they integrate the latest constraints

Questions for Support/Ops

@alanna do we want to keep the root action? Will we need to keep the ability for support to unhost accounts for anyone? Our current assumption is that it won't be needed anymore.

Specs
API

[ ] Review the current removeHost(null) call (unhost) to make sure all related data is being taking care of

[ ] Recurring contributions should be cancelled (same as archiveCollective)

[ ] In server/graphql/v2/mutation/HostApplicationMutations.ts, update removeHost mutation to allow any host admin to unhost an account under their fiscal host.
[ ] Implement a new customMessage argument on the mutation
[ ] Implement a new activity
[ ] Implement an email notification for collective admins
[ ] Add tests for this new mutation in test/server/graphql/v2/mutation/HostApplicationMutations.test.ts

[ ] Needs to be authenticated
[ ] Needs to be host admin or collective admin
[ ] Collective must have an empty balance
[ ] Returns an error if collective has no host
[ ] Sends an email with the custom message

Frontend

[ ] Implement the design proposal
[ ] Make sure there's a clear path to empty the balance
[ ] Use the removeHost mutation previously created
[ ] Add E2E test in test/cypress/integration/29-host.dashboard.test.js

Yes I think we should keep the root action.

@alanna, to zero out the Collective, where does the host send the money to?

I don't think zeroing needs to be in scope of this issue. Hosts can already zero as needed by processing an expense.

Design update

Freeze Collective
Un-host Collective

@alanna can you help me review it and write a better copy?
cc @hdiniz

I don't think zeroing needs to be in scope of this issue. Hosts can already zero as needed by processing an expense.

I think this would streamline the experience by a lot, instead of having to surface the warning about the balance, expect the host to switch context, create an expense, figure the right recipient, approve it, pay it, then come back to the un-host button.
What do we gain by not doing it?

@znarf, what's the most common case to zero out a Collective's balance with an expense? Who is this right recipient?

@znarf, what's the most common case to zero out a Collective's balance with an expense? Who is this right recipient?

I'm not sure? Switching Host? Archiving the Collective? The balance can go the the Host as recipient or an admin of the Collective.

A couple of questions:

What's the case for the host to keep the Collective's money?
It sounds like hosts will use the invite expense feature. Does it make sense to add an option to set "Collective admins" as a recipient and let the Collective admin team choose what admin gets the money? (I see a risk of going back and forth with admins to decide who ends up receiving the $)
Do we have an option to send the funds to another Collective with a different host? (What if the original admins want to transfer the funds to another Collective instead of putting them into any of the admins' accounts?)

These questions also tell me this project needs an extra round of design definition to set the right expectation in terms of the timeline. This current design iteration should be discussed and get some team approval before moving forward.
cc @alanna @znarf @hdiniz

I do not think zeroing should be in scope of this feature because the scenarios are too diverse to design for. It completely depends on the legal terms of the Host and the specific situation of the Collective. See the termination sections of the terms of fiscal hosting for various hosts to see examples.
It's not the case that Hosts will always be moving the funds to their own budgets. They might be moving funds to another Collective or an outside payee via an expense. It can actually cause a lot of problems to move the balance to the Host without careful consideration. If the Host wants to move the balance to its own budget, they can do so easily via an Expense already.
If we want to give Hosts access to the 'zero balance' function that Collective admins have in their settings currently, which sends the money to the host, that is a good idea, but should be a separate issue and separate button in the interface. If a Host admin tries to unhost a Collective and gets an error saying "balance must be at zero to unhost" then that's a good thing, because it tells the admin exactly what they need to do and they can pause and consider the best way to achieve that.
@Memo-Es the answers to your questions depend on the legal terms of the specific Host.
This project does not need another round of design, and all these questions are overcomplicating it. All needed features are already in place for the Host admin or Collective admin to zero a balance. We just need Host admins to have access to an 'unhost' button, which only works when the balance is zero.

OK, copy feedback:
I think you can remove the repeated word 'Collective' from the little menu and just say contact, freeze, unhost.
For the modal popup

Are you sure you want to un-host [Collective name]?

(include the name so they are sure they have selected the right one)

[Fiscal host name] will no longer be the Fiscal Host for this Collective.

Only show the warning about needing zero balance if it does not have zero balance and grey the button (as it has in the design already)

The Collective's balance must be zero to un-host, including its Events or Projects. There is a remaining balance of [$x]. You can pay out these funds by processing expenses.

remaining balance of [$x]

This number should include Events, Projects, and the parent balances together.

For consistency in project management, would be great to create a project board for the project. See https://github.com/opencollective/opencollective/projects/77 and https://github.com/opencollective/opencollective/projects/78 for example with other projects.

@shannondwray for docs

Re-opening as it's not yet released publicly. We want to make sure https://github.com/opencollective/opencollective/issues/5993 is properly done before doing so.

reviewing related PRs re cancelling recurring contributions and virtual cards

Enabling the unhost action in production with this PR: https://github.com/opencollective/opencollective-frontend/pull/8260
When the collective still has balance, we direct the host admin to this doc to submit an expense and clear the balance
We are also updating the unhost email notification copy to indicate that non transferable recurring contributions and virtual card will be canceled: https://github.com/opencollective/opencollective-api/pull/8031

Reposting from slack: the user who is unhosting a Collective is the host admin, who does not have access to a Collective’s “zero balance” button. This is why the instructions specify processing an expense to empty the balance, so the link should be to docs about submitting a normal expense, not using the zero balance button.

@alanna thanks! we updated the link to the expenses docs.
@shannondwray we are enabling this feature in production, do you need support with the documentation?

I tried to use the feature but it's not clear how I do so. I couldn't find it from opensource's hosted collectives as indicated. In general it would be good to post the demo here once we're 'done' and ready to release.
Could someone drop that here and we'll get documentation and release done?

Hi @BenJam, I recorded a loom for this one: Un-hosting Collectives Demo

Docs issue - #6136
Release Issue - #6135

Closing as it's released & documented


Push Fails on 1.0

I have existing repo using 0.53 and git-lfs-s3 that works.
I tried upgrading to the 1.0 release, and the push just hangs in the middle - no error.
Any ideas on how to troubleshoot?
Is 1.0 compatible with git-lfs-s3, or are changes needed?

You can set the GIT_TRACE environment variable to get some debugging info. E.g. GIT_TRACE=1 git push origin master.
If 0.6.x worked with git-lfs-s3, then 1.0 should. If it doesn't that's probably a bug.

Is this your first push in the repo?
#687 will hang indefinitely on the first push in a repo and is in 0.6 and 1.0.  There's a pending fix at #690

I think the first push after 0.53 in an existing repo will hang indefinitely because of #687 which has a pending fix in #690. You can verify if GIT_TRACE shows infinite 401s.

@WillHipschman, that is the exact problem I'm having.

@AlicanC The fix is in and tested. Just waiting for them to merge it :smile:

What happened to this? Still not fixed (or merged)?

It made it into v1.0.1.

Great news.


[SSP]Issue with access of buckets of users across tenants

Issue/Feature Description:
Buckets created by user of a tenant are able to be seen by user of another tenant.
Why this issue to fixed / feature is needed(give scenarios or use cases):
Because the buckets created by a user should be private to only the tenant of the user.
How to reproduce, in case of a bug:
Install multi-cloud with SSP enabled.
Now go to dashboard,
In identity:
create tenant1 and tenant2
create user1 with tenant1
create user2 with tenant2
create user3 with tenant1 and tenant2
Now login as user3:
create a bucket (buck1) with  tenant1
create a bucket(buck2) with tenant2
Now user3 with tenant1 is able to view both buck1 and buck2 in buckets
Also user3 with tenant2 is able to view both buck1 and buck2 in buckets
But buckets of a tenant shouldnt be able to access by other tenant users
Also Now when login as user1:
user1 is able to access both buck1 and buck2
But as user1 is part of tenant1 he should be able to access only tenant1 bucket buck1 but not buck2
Now login as user2:
user2 is  not able to access both buck1 and buck2
But as user2 is part of tenant2 he should be able to access tenant2 bucket buck2
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)
Tenant1 users:

Tenant2 users:

user3 with tenant1 buckets:

user3 with tenant2 buckets:

user1 buckets:

user2 buckets:

issue explained  clearly in issue#1303


NPE in TextFileEditorModel after switching language

open the settings editor
add the following

	"files.associations": {
		"foo.txt": "json"
	}

make changes to the langage (json -> jsonc)
dev tools console shows:
4log.js:199   ERR Cannot read property 'substr' of null: TypeError: Cannot read property 'substr' of null
at TextFileEditorModel.BaseTextEditorModel.getFirstLineText (file:///home/aeschli/workspaces/vscode/out/vs/workbench/common/editor/textEditorModel.js:99:52)
at TextFileEditorModel.updateTextEditorModelMode (file:///home/aeschli/workspaces/vscode/out/vs/workbench/services/textfile/common/textFileEditorModel.js:133:38)
at TextFileEditorModel.onFilesAssociationChange (file:///home/aeschli/workspaces/vscode/out/vs/workbench/services/textfile/common/textFileEditorModel.js:127:18)
at file:///home/aeschli/workspaces/vscode/out/vs/workbench/services/textfile/common/textFileEditorModel.js:67:107
at Emitter.fire (file:///home/aeschli/workspaces/vscode/out/vs/base/common/event.js:104:38)
at TextFileService.onFilesConfigurationChange (file:///home/aeschli/workspaces/vscode/out/vs/workbench/services/textfile/common/textFileService.js:292:48)
at file:///home/aeschli/workspaces/vscode/out/vs/workbench/services/textfile/common/textFileService.js:103:27
at Emitter.fire (file:///home/aeschli/workspaces/vscode/out/vs/base/common/event.js:104:38)
at WorkspaceService.triggerConfigurationChange (file:///home/aeschli/workspaces/vscode/out/vs/workbench/services/configuration/node/configurationService.js:534:48)
at WorkspaceService.onUserConfigurationChanged (file:///home/aeschli/workspaces/vscode/out/vs/workbench/services/configuration/node/configurationService.js:387:18)

textSnapshot.read() returns null.

Can't remember which issue but I remember that we fixed this bug already. Verified with latest version as well.


slimmelezer-luxembourg: Make energy a map instead of array

I was too quick to publish the previous PR . This uses the correct type for the energy config.
References #17807

Can you please push full PR again- I had unfortunately already reverted.


SDK-1300: An attempt to show an alternative way for handling media

@echarrod in other SDKs we create Media for Doc Scan media responses - with this approach, we would need to create specific media based on the response content type, e.g. application/pdf.
To keep this simple, perhaps we should just have a media.Media struct that's used for everything?

That was my initial thought as well, however then you would have to other kinds of inspection to determine what kind of media it is. With this approach you can do
func DoStuff(m media.Media) {
  switch t := m.(type) {
     case PNGImage:
       // Do PNG stuff
     case JPEGImage:
      // Do JPEG stuff
     case ....
  }

This is a more go-like way of doing it IMO.
You should be careful not to try to put a Square plug into a round hole. Other languages have features that may make some things easier (like generics, which Go doesn't have for now), but on the other hand Go have things that can make your life easier as well, and not taking advantage of them, makes your life unnecessarily difficult. In addition your integrators will not enjoy using your SDK if they have to treat it like a Java application.

The one reservation I have with this approach is that we want to be able to support new media types when we call DocScanClient.GetMediaContent, which I don't think this method will currently do. See Java for an example - https://github.com/getyoti/yoti-java-sdk/blob/6e4fe69d4cc02f237d3095152dd8ded4fcccbdea/yoti-sdk-impl/src/main/java/com/yoti/api/client/docs/DocScanService.java#L268
If we can allow for that somehow, then I'm happy to go with this

@echarrod @davidgrayston sorry for being a bit slow in understanding the requirements. I've pushed an update adding a media.Generic type.


Add test for declared params with multiple types

Adds tests from https://github.com/ruby-grape/grape/pull/2112

my question was also whether it matters if we put Hash in requires :bar, type: Array do, so whether we need to have this test try both Hash and Array?

@dblock If I use requires :bar, type: Set, I get:
     Failure/Error: raise Grape::Exceptions::UnsupportedGroupTypeError.new unless Grape::Validations::Types.group?(type)

     Grape::Exceptions::UnsupportedGroupTypeError:
       group type must be Array, Hash, JSON or Array[JSON]

It seems that Hash and Array are not valid group types: https://github.com/ruby-grape/grape/blob/f3073e6123a55e4ec9faa268b741d28502d2dcbc/lib/grape/validations/types.rb#L114
Do we need a test for this?

Oh, you were asking about Hash. Let me look at that.

@stanhu want to finish this?


Cannot load pretrain metafg_2_inat21_384

I use default config for MetaFG_2 but the errors in load_state_dict occured. Could you provide config of MetaFG_2_384 ?

Config file for metafg_2_inat21_384:
DATA:
  IMG_SIZE: 384
  ADD_META: True
MODEL:
  TYPE: MetaFG
  NAME: MetaFG_meta_2
  EXTRA_TOKEN_NUM: 3
  META_DIMS: [ 4, 3 ]
  NUM_CLASSES: 10000

I am not a member of their team. I just tried it out.


How to use extrinsics utility.batch and utility.batchAll ?

I try to use utility.batchAll() with polkawallet_sdk.
This what i'm trying:
final txInfo = TxInfoData(
  'utility',
  'batchAll',
  sender,
);

final txOptions = [
  'universalDividend.claimUds()',
  'balances.transferKeepAlive($destAddress, $amountUnit)'
];

await sdk.api.tx
          .signAndSend(
            txInfo,
            txOptions,
            password,
          ).timeout(
            const Duration(seconds: 12),
            onTimeout: () => {},
          );

This this throw a timeout after 12s.
This 2 calls works fine one by one.
Do you have an example how to use batchAll here ?

https://github.com/polkawallet-io/polkawallet_plugin_kusama/blob/master/lib/pages/staking/actions/stakePage.dart


feat: Update zk netplan render to handle docker bridge network interface

Problem: We have noticed when docker has a network interface the zookeeper netplan render is confused and can't correctly pick the ENI ifname. For example with the following network interfaces, the zookeeper_user_data will pick up both br-146bd07d2fbf and eth1 then render into /etc/netplan/99_config.yaml, and the netplan is broken.
ip -j link show | jq .
[
  {
    "ifindex": 3,
    "ifname": "br-146bd07d2fbf",
    "flags": [
      "NO-CARRIER",
      "BROADCAST",
      "MULTICAST",
      "UP"
    ],
    "mtu": 1500,
    "qdisc": "noqueue",
    "operstate": "DOWN",
    "linkmode": "DEFAULT",
    "group": "default",
    "link_type": "ether",
    "address": "02:42:01:07:1e:1c",
    "broadcast": "ff:ff:ff:ff:ff:ff"
  },
  {
    "ifindex": 4,
    "ifname": "eth1",
    "flags": [
      "BROADCAST",
      "MULTICAST"
    ],
    "mtu": 1500,
    "qdisc": "noop",
    "operstate": "DOWN",
    "linkmode": "DEFAULT",
    "group": "default",
    "txqlen": 1000,
    "link_type": "ether",
    "address": "0e:f1:0b:65:44:d3",
    "broadcast": "ff:ff:ff:ff:ff:ff"
  }
]

Solution: We are adding in additional filtering when finding the INTFERFACE_NAME, so it filter out any docker bridge network interface, which start with "br-".
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi Paul,
Thanks for the fix. Nice work. 👍


[fuzz] types/proof fuzzers

Motivation
fuzz types/proofs that have verify method and Arbitrary trait.

@bors-libra land


Expand Documentation

More detailed and structured documentation. Maybe describe all available methods and properties.
Possibly with GitHub pages or as GitHub wiki?

@jnt0r ,  think more examples and an explanation of the flow in the README would be enough for most users.
I'm happy to help you polish it if you write a draft. I just don't have enough understanding of how it all works to do it myself.
Does this look right to you or is there a better way of doing it?
// only authenticated users may access this Vue app
// the auth should apply to the entire site, not just select routes
router.beforeEach(async () => {
  // an early exit if the user has been auth'd earlier
  if (AuthenticationState && AuthenticationState.authenticated) {
    return true;
  }

  // it could that the authentication is still in progress
  // the problem with this call is that it never returns if authenticated
  const isAuthed = await AuthenticationState.getAuthenticatedAsPromise();

  // try to log in if not authenticated up to this point
  if (!isAuthed) {
    // this redirects to Auth0 login form, but sometimes it just logs me in
    // even if I delete all auth0 cookies
    auth.loginWithRedirect();
  }

  // recheck if the user was logged in successfully
  // redirect to a public welcome page on failure
  if (!auth || !auth.authenticated) {
    console.log("failed to auth");
    location.assign("https://stackmuncher.com");
  }

  // all navigation
  return true;
});


jUnit Extension

Implements #7.
Major changes:

move to the jUnit 5 platform
add jUnit 5 extension

Minor changes:

update README, add code highlighting
update myself info as a contributor (vitalijr2 AKA radio_rogal)

The good guy found the workaround:

add another branch in the repository, exclude it from workflow (now it should works)
then I make another PR to this branch
then you merge my PR to this branch
and last step: you make PR from this branch to develop with regular checks and SONAR

Awesome, @.*** Could you please follow the recommendation:create a feature branchmerge your changes into thatthen make a pull request?That will trigger the workflow with credentials.On Sep 24, 2024, at 1:05 PM, Vitalij Berdinskih @.***> wrote:
The good guy found the workaround:
add another branch in the repository, exclude it from workflow (now it should works)
then I make another PR to this branch
then you merge my PR to this branch
and last step: you make PR from this branch to develop with regular checks and SONAR
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi Owen, the feature branch must be created in a target repository, that is ocarlsen/mock-slf4j-impl ;)