[match] GitLab Secure File backend not able to update profiles and certificates

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
We are currently encountering an issue where fastlane match does not seem to be able to update/override existing profiles and certificates when running
We are not sure if this is a regression or a bug we just did not notice so far. We have worked with the GitLab Secure Files API in the past as well and know that before you re-upload a file you will first need to delete it. I did a quick peek into the implementation but could not find a place where a delete would be issued to update the new certs/profiles which might be the root cause.
The issue shows as follows:
[09:56:25]: GitLab storage error: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile, API: https://gitlab.com/api/v4)
[09:56:26]: GitLab storage error: match_version.txt already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: match_version.txt, API: https://gitlab.com/api/v4)

Command executed
bundle exec fastlane match development --readonly false

Complete output when running fastlane, including the stack trace and command used

+----------------------------------------------------------------------------+
|                Detected Values from './fastlane/Matchfile'                 |
+-----------------------+----------------------------------------------------+
| gitlab_project        | xxxx/apple-certificates |
| gitlab_host           | https://gitlab.com                                 |
| storage_mode          | gitlab_secure_files                                |
| type                  | appstore                                           |
| username              |<EMAIL_ADDRESS>                             |
| app_identifier        | ["com.xxx.yyyy"]                     |
| readonly              | true                                               |
| additional_cert_types | ["mac_installer_distribution"]                     |
+-----------------------+----------------------------------------------------+
+---------------------------------------------------------------------------------------------+
|                                  Summary for match 2.220.0                                  |
+----------------------------------------+----------------------------------------------------+
| readonly                               | false                                              |
| platform                               | macos                                              |
| type                                   | appstore                                           |
| additional_cert_types                  | ["mac_installer_distribution"]                     |
| generate_apple_certs                   | true                                               |
| skip_provisioning_profiles             | false                                              |
| app_identifier                         | ["com.xxx.yyyy"]                     |
| username                               |<EMAIL_ADDRESS>                             |
| team_id                                | XXXXXXXXXX                                         |
| storage_mode                           | gitlab_secure_files                                |
| git_branch                             | master                                             |
| shallow_clone                          | false                                              |
| clone_branch_directly                  | false                                              |
| skip_google_cloud_account_confirmation | false                                              |
| s3_skip_encryption                     | false                                              |
| gitlab_project                         | xxxx/apple-certificates |
| gitlab_host                            | https://gitlab.com                                 |
| private_token                          | xxxxxxxxxxxxxxxxxxxxxxxxxx                         |
| keychain_name                          | login.keychain                                     |
| keychain_password                      | ********                                           |
| force                                  | false                                              |
| force_for_new_devices                  | false                                              |
| include_mac_in_profiles                | false                                              |
| include_all_certificates               | false                                              |
| force_for_new_certificates             | false                                              |
| skip_confirmation                      | false                                              |
| safe_remove_certs                      | false                                              |
| skip_docs                              | false                                              |
| derive_catalyst_app_identifier         | false                                              |
| fail_on_name_taken                     | false                                              |
| skip_certificate_matching              | false                                              |
| skip_set_partition_list                | false                                              |
| verbose                                | false                                              |
+----------------------------------------+----------------------------------------------------+
[09:55:49]: Initializing match for GitLab project xxxx/apple-certificates on https://gitlab.com
[09:56:09]: Verifying that the certificate and profile are still valid on the Dev Portal...
Available session is not valid anymore. Continuing with normal login.
[09:56:14]: Verifying that the certificate and profile are still valid on the Dev Portal...
Available session is not valid anymore. Continuing with normal login.
[09:56:17]: Installing certificate...
+---------------------------------------------------------------------------+
|                           Installed Certificate                           |
+-------------------+-------------------------------------------------------+
| User ID           | XXXXXXXXXX                                            |
| Common Name       | Apple Distribution: YYYYYYYYYYYYYY, Inc. (XXXXXXXXXX) |
| Organisation Unit | XXXXXXXXXX                                            |
| Organisation      | YYYYYYYYYYYYYY, Inc.                                  |
| Country           | US                                                    |
| Start Datetime    | 2024-05-09 14:45:22 UTC                               |
| End Datetime      | 2025-05-09 14:45:21 UTC                               |
+-------------------+-------------------------------------------------------+
[09:56:17]: Installing certificate...
+------------------------------------------------------------------------------------------+
|                                  Installed Certificate                                   |
+-------------------+----------------------------------------------------------------------+
| User ID           | XXXXXXXXXX                                                           |
| Common Name       | 3rd Party Mac Developer Installer: YYYYYYYYYYYYYY, Inc. (XXXXXXXXXX) |
| Organisation Unit | XXXXXXXXXX                                                           |
| Organisation      | YYYYYYYYYYYYYY, Inc.                                                 |
| Country           | US                                                                   |
| Start Datetime    | 2024-04-17 07:26:57 UTC                                              |
| End Datetime      | 2025-04-17 07:26:56 UTC                                              |
+-------------------+----------------------------------------------------------------------+
[09:56:18]: Provisioning profile '61b9a06c-4776-47a8-9a0b-977a892b270d' is not available on the Developer Portal for the user<EMAIL_ADDRESS>fixing this now for you 🔨
+---------------------------------------------------------------------------------------+
|                               Summary for sigh 2.220.0                                |
+-------------------------------------+-------------------------------------------------+
| app_identifier                      | com.xxx.yyyy                      |
| username                            |<EMAIL_ADDRESS>                          |
| force                               | false                                           |
| cert_id                             | asdasdfasd^                                      |
| provisioning_name                   | match AppStore com.xxx.yyyy macos |
| ignore_profiles_with_different_name | true                                            |
| team_id                             | XXXXXXXXXX                                      |
| fail_on_name_taken                  | false                                           |
| include_all_certificates            | false                                           |
| include_mac_in_profiles             | false                                           |
| platform                            | macos                                           |
| adhoc                               | false                                           |
| developer_id                        | false                                           |
| development                         | false                                           |
| skip_install                        | false                                           |
| skip_fetch_profiles                 | false                                           |
| skip_certificate_verification       | false                                           |
| readonly                            | false                                           |
+-------------------------------------+-------------------------------------------------+
[09:56:20]: Starting login with user<EMAIL_ADDRESS>Available session is not valid anymore. Continuing with normal login.
[09:56:23]: Successfully logged in
[09:56:23]: Fetching profiles...
[09:56:23]: Verifying certificates...
[09:56:23]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[09:56:24]: Creating new provisioning profile for 'com.xxx.yyyy' with name 'match AppStore com.xxx.yyyy macos' for 'macos' platform
[09:56:25]: Downloading provisioning profile...
[09:56:25]: Successfully downloaded provisioning profile...
[09:56:25]: Installing provisioning profile...
/var/folders/89/nf2tq6c92nz_mlzhl1xsqpk40000gn/T/d20240512-23686-eky4c7/XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile
[09:56:25]: Installing provisioning profile...
[09:56:25]: GitLab storage error: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: XXXXXXXXXX/profiles/appstore/AppStore_com.xxx.yyyy.provisionprofile, API: https://gitlab.com/api/v4)
[09:56:26]: GitLab storage error: match_version.txt already exists in GitLab project xxxx/apple-certificates, file not uploaded (File: match_version.txt, API: https://gitlab.com/api/v4)
[09:56:26]: Finished uploading files to GitLab Secure Files Storage [xxxx/apple-certificates]
+---------------------------------------------------------------------------------------------------------------------------------------------+
|                                                       Installed Provisioning Profile                                                        |
+---------------------+-----------------------------------------------------------+-----------------------------------------------------------+
| Parameter           | Environment Variable                                      | Value                                                     |
+---------------------+-----------------------------------------------------------+-----------------------------------------------------------+
| App Identifier      |                                                           | com.xxx.yyyy                                |
| Type                |                                                           | appstore                                                  |
| Platform            |                                                           | macos                                                     |
| Profile UUID        | sigh_com.xxx.yyyy_appstore_macos                          | 12312312-xxxx-4418-ae24-498fb9c95e5a                      |
| Profile Name        | sigh_com.xxx.yyyy_appstore_macos_profile-n                | match AppStore com.xxx.yyyy macos           |
|                     | ame                                                       |                                                           |
| Profile Path        | sigh_com.xxx.yyyy_appstore_macos_profile-p                | /Users/mschmieder/Library/MobileDevice/Provisioning       |
|                     | ath                                                       | Profiles/12312312-xxxx-4418-ae24-498fb9c95e5a.provisionp  |
|                     |                                                           | rofile                                                    |
| Development Team ID | sigh_com.xxx.yyyy_appstore_macos_team-id                  | XXXXXXXXXX                                                |
| Certificate Name    | sigh_com.xxx.yyyy_appstore_macos_certifica                | Apple Distribution: XXX, Inc. (TNRXXXXX)     |
|                     | te-name                                                   |                                                           |
+---------------------+-----------------------------------------------------------+-----------------------------------------------------------+

Environment

[09:57:43]: Generating fastlane environment output, this might take a few seconds...
✅ fastlane environment ✅
Stack

Key
Value

OS
14.4.1

Ruby
3.2.2

Bundler?
true

Git
git version 2.43.0

Installation Source
~/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bin/fastlane

Host
macOS 14.4.1 (23E224)

Ruby Lib Dir
~/.asdf/installs/ruby/3.2.2/lib

OpenSSL Version
OpenSSL 3.2.1 30 Jan 2024

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode-15.3.0.app/Contents/Developer/

Xcode Version
15.3

Swift Version
5.10

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.220.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.5.1

did_you_mean
1.6.3

syntax_suggest
1.0.2

bundler
2.5.6

pathname
0.2.1

rake
13.2.1

base64
0.2.0

nkf
0.2.0

rexml
3.2.6

CFPropertyList
3.0.7

bigdecimal
3.1.8

concurrent-ruby
1.2.3

connection_pool
2.4.1

drb
2.2.1

i18n
1.14.5

minitest
5.22.3

mutex_m
0.2.0

tzinfo
2.0.6

activesupport
<IP_ADDRESS>

public_suffix
5.0.5

addressable
2.8.6

artifactory
3.0.17

atomos
0.1.3

aws-eventstream
1.3.0

aws-partitions
1.927.0

aws-sigv4
1.8.0

jmespath
1.6.2

aws-sdk-core
3.195.0

aws-sdk-kms
1.80.0

aws-sdk-s3
1.149.1

babosa
1.0.4

claide
1.1.0

clamp
1.3.2

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.5

domain_name
0.6.20240107

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.110.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.4.1

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.3

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.3.1

gh_inspector
1.1.3

jwt
2.8.1

multi_json
1.15.0

os
1.1.4

signet
0.19.0

googleauth
1.8.1

httpclient
2.8.3

mini_mime
1.1.5

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

google-apis-core
0.11.3

google-apis-androidpublisher_v3
0.54.0

google-apis-playcustomapp_v1
0.13.0

google-cloud-env
1.6.0

google-apis-iamcredentials_v1
0.17.0

google-apis-storage_v1
0.31.0

google-cloud-errors
1.4.0

google-cloud-core
1.7.0

google-cloud-storage
1.47.0

json
2.7.2

mini_magick
4.12.0

naturally
2.2.1

optparse
0.5.0

plist
3.7.1

rubyzip
2.3.2

security
0.1.5

simctl
1.6.10

terminal-notifier
2.0.0

unicode-display_width
2.5.0

terminal-table
3.0.2

tty-screen
0.8.2

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.24.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

racc
1.7.3

nokogiri
1.16.4

slather
2.8.0

Same issue here with the latest stable version of fastlane at the time of writing: 2.220.0
Temporary solution, if you know what files will be updated, is to manually delete them from the repo's Secure Files, but it's definitely not an optimal long term fix.
Fortunately we don't have to update provisioning profiles often, but nevertheless I think this is a serious problem.

Have you guys found any solutions ?


Only clean docs in development

Description
Replacement PR for https://github.com/flowforge/website/pull/966, which only cleans out the docs directly in development mode.
npm run start (dev mode) will now:

Clean site (but not img)
Clear out docs/**md
Builds the javascript via terser
Run dev:docs which copies across ../flowforge/docs, if it exists
Run dev:postcss
Builds the website via netlify

In production, it'll remain as always, which Joe detailed in https://github.com/flowforge/website/pull/965#issuecomment-1633870796
Related Issue(s)
#966 and #965
~Fixes 967~
Checklist

[x] I have read the contribution guidelines
[x] I have considered the performance impact of these changes
[x] Suitable unit/system level tests have been added and they pass
[-] Documentation has been updated

@knolleary I had a working proof of concept for #967 (464e613) but have reverted it as it causes Netflify PR deploy previews to fail, as they never have the docs/ only builds from the live branch; and I time boxed this to an hour.


Can't use ray_lightning in pytest

Hi,
When I try to run the code with RayPlugin in my tests, I get the following error:
(pid=2127144) 2021-07-14 06:16:52,345   ERROR serialization.py:250 -- No module named 'test_runner'
(pid=2127144) Traceback (most recent call last):
(pid=2127144)   File "/home/rizhiy/miniconda3/envs/ntf/lib/python3.8/site-packages/ray/serialization.py", line 248, in deserialize_objects
(pid=2127144)     obj = self._deserialize_object(data, metadata, object_ref)
(pid=2127144)   File "/home/rizhiy/miniconda3/envs/ntf/lib/python3.8/site-packages/ray/serialization.py", line 190, in _deserialize_object
(pid=2127144)     return self._deserialize_msgpack_data(data, metadata_fields)
(pid=2127144)   File "/home/rizhiy/miniconda3/envs/ntf/lib/python3.8/site-packages/ray/serialization.py", line 168, in _deserialize_msgpack_data
(pid=2127144)     python_objects = self._deserialize_pickle5_data(pickle5_data)
(pid=2127144)   File "/home/rizhiy/miniconda3/envs/ntf/lib/python3.8/site-packages/ray/serialization.py", line 158, in _deserialize_pickle5_data
(pid=2127144)     obj = pickle.loads(in_band)
(pid=2127144) ModuleNotFoundError: No module named 'test_runner'

test_runner is the name of my testing script, but I'm not sure why you would need to serialize anything inside it. It just loads data and calls Runner, which is my wrapper around pl.Trainer.
How should I properly launch the training?

Hey @Rizhiy, could you share the test_runner script, the full log output, and more information about your setup (how many nodes in the cluster and ray version)

Sure, here is the relevant section of test_runner:
def _test_train(data, runner):
    train_dataset = DictTensorDataset(data["train"])
    val_dataset = DictTensorDataset(data["val"])

    rmtree(runner.output_dir, ignore_errors=True)
    runner.output_dir.mkdir()

    runner.train_model(train_dataset, val_dataset)

@pytest.mark.limit_gpus(2)
@pytest.mark.dependency()
def test_train(load_file, runner):
    _test_train(load_file("data.pkl"), runner)

Here is relevant parts of the Runner:
    def _create_trainer(self, *_, **kwargs) -> pl.Trainer:
        base_kwargs = dict(
            default_root_dir=str(self.output_dir.absolute()),
            gpus=1,
            precision=16 if self.cfg.FP16 else 32,
        )
        base_kwargs.update(kwargs)
        plugins = [
            RayPlugin(num_workers=self.cfg.NUM_GPUS, num_cpus_per_worker=1, use_gpu=True, find_unused_parameters=False),
        ]
        if "plugins" not in base_kwargs:
            base_kwargs["plugins"] = []
        base_kwargs["plugins"].extend(plugins)
        return pl.Trainer(**base_kwargs)

    def train_model(self, train_dataset: DictsDataset, val_dataset: DictsDataset):
        pip_freeze(self.requirements_path)
        seed_everything(self.cfg.SEED)
        checkpoint_callback = ModelCheckpoint(
            monitor=f"{self.cfg.VAL.SELECTION_TARGET}.{self.cfg.VAL.SELECTION_METRIC}",
            mode="min" if self.cfg.VAL.MINIMISE_METRIC else "max",
            filename="{step:05d}",
            save_top_k=1,
            save_last=True,
        )
        last_checkpoint_path = self.output_dir / "lightning_logs" / "version_0" / "checkpoints" / "last.ckpt"
        trainer = self._create_trainer(
            sync_batchnorm=True,
            max_steps=self.cfg.TRAIN.NUM_ITERS,
            resume_from_checkpoint=str(last_checkpoint_path) if last_checkpoint_path.exists() else None,
            callbacks=[checkpoint_callback],
            val_check_interval=self.cfg.VAL.FREQ,
        )

        trainer.fit(self, datamodule=self._create_datamodule({"train": train_dataset, "val": val_dataset}))

Here is extra stack trace:
tests/training/test_runner.py:114: in _test_train
    runner.train_model(train_dataset, val_dataset)
ntf/training/runner.py:243: in train_model
    trainer.fit(self, datamodule=self._create_datamodule({"train": train_dataset, "val": val_dataset}))
../../miniconda3/envs/ntf/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py:458: in fit
    self._run(model)
../../miniconda3/envs/ntf/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py:756: in _run
    self.dispatch()
../../miniconda3/envs/ntf/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py:797: in dispatch
    self.accelerator.start_training(self)
../../miniconda3/envs/ntf/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py:96: in start_training
    self.training_type_plugin.start_training(trainer)
../../miniconda3/envs/ntf/lib/python3.8/site-packages/ray_lightning/ray_ddp.py:213: in start_training
    results = self.execution_loop(trainer, tune_enabled=True)
../../miniconda3/envs/ntf/lib/python3.8/site-packages/ray_lightning/ray_ddp.py:195: in execution_loop
    results = process_results(futures, queue)
../../miniconda3/envs/ntf/lib/python3.8/site-packages/ray_lightning/util.py:103: in process_results
    ray.get(ready)
../../miniconda3/envs/ntf/lib/python3.8/site-packages/ray/_private/client_mode_hook.py:62: in wrapper
    return func(*args, **kwargs)

actually do you mind sharing the entirety of test_runner? In particular I want to see where DictTensorDataset is defined.

I think you might be running into this same error https://github.com/ray-project/ray/issues/13528

It is defined above that function, should it also be pickleable?

Ok got it, see the issue that I linked. I think this should work if you move DictTensorDataset to a separate file.

Thanks, that fixed it.


Add support for capture options in WASAPI loopback

This adds the ability to set options of WasapiCapture when constructing WasapiLoopbackCapture. I've tested it by creating an application that keeps track of the number of bytes received in DataAvailable and measures the time between each event.

Merged into Sonic Boom 1.1.0, which is a fork of NAudio. Thank you for your contribution!


update dscanner to alpha 6

This PR updates dscanner and its configuration because the old file is not compatible with a recent change in dscanner (which is that a test can be "enabled" | "disabled" | "skip-unittest")

Actually this could be unecessary (see why)

Updating is still a good idea. See https://github.com/Hackerpilot/dsymbol/issues/9 and https://github.com/dlang/phobos/pull/4336

Great - let's go? :)


add: Masonite adapter & Ping CRM

Name
Link

Masonite adapter
_https://github.com/girardinsamuel/masonite-inertia_

Ping CRM Masonite
_https://github.com/girardinsamuel/pingcrm-masonite_

Resource description here

[+] My item is in the right category
[+] My item has been added to the bottom of the list
[+] My item's name and description respects the conventions of the list
[+] I have read and followed the contributing guidelines

Thanks!


ROCm 4.1.1 OpenCL slowdown vs. ROCm 3.3.0 in gpuowl

Using gpuowl, on Linux 20.04 kernel 5.4.0, Radeon VII,
I have prepared ISA dumps compiled with rocm-opencl3.3.0 vs. rocm-opencl4.1.1, and a summary delta. The conclusion is that a 3% - 4% slowdown is observed in ROCm4.1.1. The occupancy of the critical kernels (carryFused, tailFusedSquare) is decreased, due to the number of VGPRs used.
In the delta below, left is 3.3.0 and right is 4.1.1
delta.txt
isa3.3.0.txt
isa4.1.1.txt

Hi @preda
Thanks for reaching out.
There is an active ticket already logged #1196 and its a regression between 3.3 and 3.5 and the same is there with 4.0 and 4.1 also.
So I wish to mark this as duplicate of #1196
Hope it helps.
Thank you.

Yep dup is appropriate.


How to authenticate both OpenLDAP + Mysql

Laravel Version: 5.7
Adldap2-Laravel Version: 5.1
PHP Version: 7.1.7
LDAP Type:  OpenLDAP

Description:
my user info stores in openldap and mysql ,now,I have finished authrization based on  mysql, but how to configure laravel to support mysql and ldap,prefer your answer

Steps To Reproduce:

config/auth.php:
'providers' => [
'users' => [
'driver' => 'eloquent',
'model' => App\User::class,
],
should i modify driver?

now,i have add one guard and one provider,
'guards' => [
'web' => [
'driver' => 'session',
'provider' => 'users',
],
    'api' => [
        'driver' => 'token',
        'provider' => 'users',
    ],
    'adldap' => [
        'driver' => 'session',
        'provider' => 'myldap'
    ]
],

'providers' => [
'users' => [
'driver' => 'eloquent',
'model' => App\User::class,
],
'myldap' => [
'driver' => 'ldap',
'model' => App\User::class,
],
so i try to auth like this
$c = ['username' => 'testuser', 'password' => '123456'];
dd(Auth::guard('adldap')->attempt($c)); //return false
can u help me ?

why exactly do you want LDAP and MySQL, usually, LDAP will sync any data you want to mysql, so it's only used for relevant calls and eloquent just uses mysql

why exactly do you want LDAP and MySQL, usually, LDAP will sync any data you want to mysql, so it's only used for relevant calls and eloquent just uses mysql

because my user data stores in ldap and mysql,i am also feel embarrassed ;)

Which scenario explains your situation best:
Different users exist in mysql and ldap.
The same users exist in mysql and ldap.

@sachaw
Different users exist in mysql and ldap.
user a,b,c stores in mysql
user 1,2,3 store in ldap
exactly i add user_type attribute ,which user stores in mysql is user_type_aaa
and user stores in ldap is user_type_bbb

now i use another solution to solve this problem,my login logic as follows:
public function doLogin(Request $r)
{
//users store in mysql
if ($r->input('user_type') === "1")
{
//check user password
if (Hash::check($r->input('password'), $u->password)) {
$s = [
'user_type' => 1,
'user' => $u,
.......
];
//write user info into session
session(['logined' => $s]);
return $this->redirectUrl('/home');
}
//users store in ldap
elseif ($r->input('user_type') === "2"
{
//check user password
if (Adldap::auth()->attempt($r->input('username'),$r->input('password')))
{
$u = Adldap::search()->where('uid', '=', $r->input('username'))->first();
dd($u) //return one Entry instance
$s = [
'user_type' => 2,
'user' => $u,
.......
];
//write user info into session
session(['logined' => $s]);
return $this->redirectUrl('/home');
}
}

Hi @test98123456,
I would really suggest against the code you posted using the session() helper to track logged in users in your own custom manor and stick with Laravel’s built in authentication as you’re basically creating your own auth implementation.
To use different auth guards that you’ve configured in the config code you posted earlier, simply call:
Auth::guard(‘adldap’)->attempt($credentials);

// Or:

Auth::guard(‘web’)->attempt($credentials);

Hi @test98123456,
I would really suggest against the code you posted using the session() helper to track logged in users in your own custom manor and stick with Laravel’s built in authentication as you’re basically creating your own auth implementation.
To use different auth guards that you’ve configured in the config code you posted earlier, simply call:
Auth::guard(‘adldap’)->attempt($credentials);

// Or:

Auth::guard(‘web’)->attempt($credentials);

thanks for your reply ,i did this because i can not distinguish between adldap authorized user intance and mysql authorized user instance,forgive me ,i am new laraveler,actually i am a new phper ：）
Auth::guard(‘web’)->attempt($credentials);
this method return true,and how can i discriminate this logined user ,is a mysql user ,or ldap user?
Auth::guard(‘adldap’)->attempt($credentials);
this code retrun false,and Now I'm trying to fix it and find out where the configuration is wrong.
，If the above code returns true, I will have the same problem as above.so
Can you provide me some sample code?

@stevebauman

Doesn't this automatically work if you configure both ADLDAP2 and conventional Laravel authentication correctly and then use LDAP_LOGIN_FALLBACK=true? If you use the DatabaseUserProvider and sync to the local database, then both LDAP and MySQL should work fine; if a user doesn't exist in LDAP, it falls back to the local DB.


KeyError: "SRREDSMultipleGTDataset: 'GenerateFrameIndicesForRecurrent is not in the pipeline registry'"

I get this error when trying to test basicvsr:

Please tell me how to fix it.

It seems that this function hasn't been merged. Let me check.

@ckkelvinchan pls have a test run and make sure it can train & test :)

@Gptao We have added the function (renamed as GenerateSegmentIndices). Please let us know if there are any further problems.

Closing due to inactivity. Please reopen if the problem persists.


Fixed Navigation Bar Text Visibility Issue in Dark Mode in Team Tab

Fixes Issue
#1071 Navigation Bar Text Visibility Issue in Dark Mode in Team Tab

Closes #1071
Changes proposed

Modified team.css to adjust the text colour of the navbar items for dark mode.
Ensured that the text color contrasts appropriately with the background in dark mode, improving readability.

Screenshots

In Light mode

Now in Dark Mode

Note to reviewers

Good morning
I have reviewed this.
On Fri, 17 May 2024, 20:37 Vivek Prajapati, @.***>
wrote:

@codervivek5 https://github.com/codervivek5 requested your review on:
#1077 https://github.com/codervivek5/VigyBag/pull/1077 Fixed Navigation
Bar Text Visibility Issue in Dark Mode in Team Tab.
—
Reply to this email directly, view it on GitHub
https://github.com/codervivek5/VigyBag/pull/1077#event-12849902966, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A2ZRTZWHTFBTE3LMCKLH4ODZCYMMJAVCNFSM6AAAAABH25XUZ2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSHA2DSOJQGI4TMNQ
.


Price feeder ATOM base conversion issues

Summary of Bug
Seems as though when converting a price like OSMO/ATOM, the price feeder has difficulty converting that to OSMO/USD. This should be possible going from OSMO/ATOM -> OSMO/USDT -> OSMO/USD.
This should be the last blocker before releasing price-feeder v2

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Closing this, it's not an issue with redenomination logic, just a parameter swap on the osmo api.


Difficult to avoid messages getting marked as read

There are several things about Zulip's UI that make it hard to avoid messages getting marked as read (or at least, make it feel this way - I am unsure of the exact semantics of marking messages as read). This is related to, but distinct from #5462 and #2676. Specific problems that I have:
Main page/All messages UI
When I load the main page, it defaults to the "All messages". At first, I thought that this loaded the next unread message. This is incorrect - it loads the last read message, AFAICT. However, if I inadvertently scroll down on the main page, it will being to mark messages as "read". This forces me to either read them then (often without the context I want), or to ignore them, and risk missing things.
Fix:
Either by default or with an option, replace the main page with a page that shows something more like the mobile Zulip default view. That is, a list of all streams with unread messages, and the title of all topics in each stream (with the number of unread messages next to it). This solves two problems:

It would prevent me from being stressed about accidentally marking messages as read when I load Zulip
It would allow me to see the titles of new topics in streams that I don't want to click on, due to "Streams with unread messages" (below)

I don't know anyone who finds the "All Messages" view useful, and loading it stresses me out due to the number of times I've inadvertently scrolled and marked a message as read by mistake.
Streams with unread messages
Clicking on a stream on the left hand navbar results in a message from that stream getting marked as read. AFAICT, it's the oldest message, which makes this worse - I often have things that I want to respond to, but need to spend a fair amount of time on, so I keep them unread. Once that becomes the oldest thing in a stream, I can no longer click on the stream in the left hand nav, because doing so will result in the topic or message that I want to reply to being marked as read.
Fix:
By default, highlight the most recent read message when clicking on a stream in the left hand nav. Add an option to make clicking on a stream leave the main view blank, but show the list of topic names in the stream.
Private messages
When someone sends me a private message while I have unread private messages, IIRC clicking "Private Messages" on the left nav will mark my oldest private message as read. This is often undesirable. The workflow that I have now is - if I have unread PMs and see that someone has sent me a PM (but I want to leave the old PMs unread), I look at who sent me the message in the popup notification, and search for their name on the right hand nav and click on it, so that it will narrow to just that PM. This is not a great workflow, particularly when I didn't notice the notification, and need to scroll through the entire right nav to see who has a number badge next to their name.
Fix:
Clicking on "Private Messages" in the left nav should highlight the last read message not the last unread message. Additionally, there should be an option to make clicking "Private Messages" show nothing in the main page, but instead simply expand the list of recent people. I would vastly prefer this UI, but understand that it might annoy some people, hence the suggestion for an option.

Another one of these I noticed today:
When I have my private messages selected, the list of people who I have PMs with goes off the screen, and I cannot scroll down (possibly a separate bug?). So to see anything that isn't a private message, I have to click "all messages", which marks my oldest unread message as read (really not what I want). I guess I could also either close zulip and open the main page again, or type stream:something into the search bar, but I usually don't think to do either of these things.

@WesleyAC thanks for the feedback, it's helpful!  The reason we originally designed Zulip this way was for consistency -- if you click on a stream where all the messages ever sent are unread, for example, we have no message to highlight.  I think it was a mistake, but inconsistent behavior leads to its own problems, and at least the current behavior is consistent and correct.
I have been planning to eventually move Zulip to "highlight last read message", but that model adds some significant complexity (e.g. in places with only unread messages, in order to achieve this, we need a way to have the selected message be in a special area off the top of the feed, even if there are unread messages present).
This is a larger project which is unlikely to happen without a skilled contributor motivated to make it happen; the key piece that would unblock my spending time on this transition is someone doing the work to make having the selection on the top-of-feed area (the thing with the black "Z") work.  (A potential semi-workaround is to star messages you didn't want marked read, but obviously that's not a happy solution.)

Completely agree with your characterization of the problem!

Either by default or with an option, replace the main page with a page that shows something more like the mobile Zulip default view. That is, a list of all streams with unread messages, and the title of all topics in each stream (with the number of unread messages next to it).

This is my favorite solution so far.

There's definitely an issue around somewhere for that, and it's also on our potentially high-value large projects radar.

Here's another experience that falls under this issue's title:
Search results
When I do a search, I'm typically looking for a specific old conversation I have in mind. But if I have unread messages and some of them happen to match the search query, they show up in the results... and then scrolling through the results to find the conversation I want goes and marks those messages read, which may be scattered across a wide range of different conversations.
If I don't want to risk completely losing those conversations (i.e. never becoming aware of them, because they got marked as read before I looked at them), this means I have to carefully inspect all the messages I'm scrolling past, watching for unread markers, making sure to spot them before they disappear.
Doing that is pretty much incompatible with a high-quality search experience -- I'm spending more effort preventing the search flow from causing me data loss than I am actually looking at the results I was looking for.
The simplest fix would be to make a search narrow simply not cause messages to get marked as read. I think I do pretty much never want messages to get read by virtue of seeing them in search results -- I only ever want that when reading in a more coherently threaded context. Not sure what to do about showing unread-markers (which then don't go away, unlike in other narrows), or not showing them (making it look like they're all already read, which could be misleading or confusing.)

Agreed that we should just not mark messages as read in search.

Is it worth opening another issue for "don't mark messages as read in search"? That and mobile unreads view car be independent efforts.

Is it worth opening another issue for "don't mark messages as read in search"?

Hmm, I'd say that answering that question, and then acting to make the issue tracker be the way you think it best for it to be, sounds like something you should feel empowered to just do. :wink:
In any case, I went and cloned that bit as a new issue: #12556

That and mobile unreads view can be independent efforts.

Do you perhaps want to have an issue for that effort, too? (Or find an existing one and link it here?) An earlier comment asked about that, too:

Regarding the solution of making the main page more like the mobile version - is that something that is more feasible? Should I create a separate bug for that?

This issue's title and description are about a problem, not a solution, and I count at least three different solutions discussed above for different aspects of the problem. If you want to turn this into the thread for that particular solution, that's also up to you, but I'd recommend making that explicit.

For mobile unreads view, there's #11994 open.

See also #12594

I would also find an improvement in this behavior very useful for my organization, particularly with private messages. Clicking on "Private messages" should not mark any messages as read - as noted above this allows you to leave a certain conversation as unread until you are able to respond to it, but continue to respond to a different conversation that is in progress.

I have another important use case to add to this ticket - if a user has the Zulip window maximized on a high resolution display and has unread private messages from several users (e.g. more than 3 different users), clicking on "Private messages" causes ALL of the messages from all of the users to immediately be marked as read (because the display happens to be large enough to display all of them at once). This makes it very difficult to note which users had unread messages that you now need to review or to selectively choose to look at some of them now but not others. I confirmed that if you make the Zulip window smaller, this behavior does not occur. Can this behavior be changed as part of this ticket, e.g. would the "highlight last read message" behavior mentioned above cause it to NOT mark any of these messages as read?

Another use case to add - with Zulip in the foreground, it will often automatically scroll down and mark messages as read when the Windows computer is locked, which is undesirable

Another use case to add - with Zulip in the foreground, it will often automatically scroll down and mark messages as read when the Windows computer is locked, which is undesirable

That certainly shouldn't happen!  The logic is very carefully written to not scroll down more than a screen without user input.  My guess is there's some sort of bug that's triggering a "scroll_to_end" event, potentially a resize event triggered by a change of monitor or similar, if one's only seeing it on lock/unlock?

This is definitely a major issue for me, and the opposite of “don’t miss an important conversation” selling point of Zulip.
I think the best way to fix it would be — to mark messages automatically as read only when I am inside an individual topic (or PM conversation), when I have the whole context of discussion. When I am in an “all messages” view, or when I am in a “stream” view, or in “search” view, no messages should be marked as read.
What if I read a non-active stream as a whole, should I enter each topic to mark messages as read? No, below all messages there should be a button “mark all topics as read” — to confirm that I indeed read all of the topics above.
I think this behavior would be very consistent, and would reinforce Zulip’s strengths in supporting long asynchronous conversations.

I think this is certainly viable as an option.  I'd to some extent to prefer to focus on the solution of taking you to the last read message rather than the first unread, which I think @ryanreh99 was doing some work on, but it could be sensible to do both.

I've noticed this problem recently where I'll be viewing a different message (e.g. typing a private message to User A) and a private message from User B will come in and I'll see it show up grayed out at the bottom of the window. I do not want to read it now as I need to finish what I was typing to User A, so I finish doing that and send the message. Later, I notice that the message from User B has already been marked as read and I've forgotten about it since it did not stay as unread (I would normally click Private messages and then select User B to read the message when I am ready).

A bit late in the discussion but it seems relevant here: I addressed the same problem in my question in the Zulip community when it was answered by @showell  with a rewrite of calc_can_mark_messages_read() in static/js/filter.js.
In short: with one boolean you can avoid messages being marked as read in interleaved view (i.e. when selecting a Stream, All messages, or Private messages).
There is however no UI interface force toggling this boolean for an organization or a user.
Nevertheless, it works perfectly for me to only mark messages as read when I am in a topic or in a specific PM lis for one person/group.

Clicking on a stream on the left hand navbar results in a message from that stream getting marked as read. AFAICT, it's the oldest message, which makes this worse - I often have things that I want to respond to, but need to spend a fair amount of time on, so I keep them unread. Once that becomes the oldest thing in a stream, I can no longer click on the stream in the left hand nav, because doing so will result in the topic or message that I want to reply to being marked as read.

This is a problem I ran into quite often the last weeks. :) So indeed it'd be great to find some solution here. Only marking messages as read in the per-topic view sounds good to me, but will probably be surprising to some people.

I often miss messages because I have a tab left open in zulip on private messages but I am away. When the tab is not a foreground, but I have selected the private conversation with someone, the messages received on this conversation are automatically marked as read. Looking at the source code, I see no mention of visibilityState or visibilityChange. Maybe messages shouldn't marked as read when there is no interaction at all (scrolling even when at bottom, typing, but not moving away to another user).
I don't get this kind of issues in Slack, but I don't know what they do differently.

The three items in the original issue description have all been fixed:

The default view is the inbox-style "Recent conversations" view, not "All messages".
Going to a stream via the left sidebar no longer marks a message as read.
Clicking on "Direct messages" (the new "Private messages") in the left sidebar no longer changes the message-list pane at all — it just expands a list of DM conversations in the left sidebar. But even if you hit the "interleaved view" icon to the right of those words, to go to the interleaved view of direct messages, that doesn't mark a message as read either.

Thanks @WesleyAC for raising them!
It seems we lost track of this thread and didn't cross-reference it when we made those changes. I believe the latter two happened sometime in the last year or so, but I don't see them in the Zulip Server 7 or Zulip Server 6 release blog posts, so I'm not sure when they happened. Anyway, closing now.

I often miss messages because I have a tab left open in zulip on private messages but I am away. When the tab is not a foreground, but I have selected the private conversation with someone, the messages received on this conversation are automatically marked as read.

Yeah. @vincentbernat this would be good to file as its own fresh issue.

Noting here that interleaved views will (should) mark the first message as unread unless the user has changed their display setting for automatically marking messages as read: https://zulip.com/help/marking-messages-as-read#configure-whether-messages-are-automatically-marked-as-read.
There is an issue where the mark as read automatically behavior is inconsistent: #26021.

Noting here that interleaved views will (should) mark the first message as unread unless the user has changed their display setting

Hmm, I see — thanks for catching that. I guess this should stay open, then. I've set that setting and therefore have not encountered this problem in some time :slightly_smiling_face:
@vincentbernat the behavior you described would still be good to file as its own fresh issue.

Going to a stream via the left sidebar no longer marks a message as read.

Cannot confirm. When I click a stream, the "unread" counter decrements by one. When I then scroll around more messages are marked as read. So it is still hard to navigate streams while preserving "unread" state.

Yes, to be clear, there is now (in Zulip 7.0 release) a per-user setting that allows users to set when messages are automatically marked as read.
The options are:

Never, and in this case the user has to always manually mark messages as read
Only in conversation views, and in this case messages are only marked as read in a particular stream/topic view or a particular direct message conversation. The views that contain multiple conversations (a stream view, all direct messages view, search views, all messages view) do not mark as read with this setting.
Always, and in this case messages are marked read in those interleaved views mentioned in the bullet point above.

Here's the documentation for marking messages as read in the help center: https://zulip.com/help/marking-messages-as-read. It's noted in the Zulip 7.0 blog post under the Release highlights / New and improved workflows section.
While existing Zulip users will have to go in and configure this setting, organization admins can set this as the default for new users joining the organization (if they want to); see configure default settings for new users documentation.

I agree that the pinned tab marking messages as read should be reported as a separate issue. I'll note that that issue might be fixed by the work I'm doing to fix #26021.
I don't know if this issue should remain open as the "per-user" setting does allow the control to not mark messages in interleaved views as read.

I think as long as the default settings are giving people this experience, the problem is still present and the issue should remain open.
Specifically, one of the three items in the original report still applies, namely "Streams with unread messages":

Clicking on a stream on the left hand navbar results in a message from that stream getting marked as read.

That is a pretty common thing to want to do, so I think this is still a significant issue for many users who haven't discovered the setting.
(On default settings, if you specifically go to the "All messages" view or the interleaved-DMs view, those will also start marking messages as read. But because "All messages" was replaced as the default view by "Recent conversations", and because clicking "Direct messages" in the left sidebar to try to navigate to the DM you just got now just opens a section in the left sidebar and doesn't navigate to an interleaved view, I think those two UX problems from the original report have been solved.)

A few major changes impact this issue:

The default home view is inbox, which doesn't mark anything as read.
We eliminated historical behavior related to the Combined Feed being loaded in the background for all users, whether they used that or not.
We now (via #30565 and related issues) default to having clicking a channel (formerly "stream") on the left sidebar take you to the first topic in the channel, not an interleaved view, which more or less eliminates the experience of messages being marked as read via clicking on the sidebar, unless they're specifically opted into that behavior via a setting.

I'm closing this as I believe all of the core bugs tracked here are fixed, and if there are other bugs/regressions in this area, they probably deserve their own issues, where it'll be easy to focus on those specific problems without the clutter of 6 years of discussion about problems that have now been fixed.
Thanks for all the feedback and investigation on this, folks, it's been really helpful!

Yeah, it still marks the top message as read. #30405 is our intended solution for that.
It will also mark the whole topic as read if you can see the bottom, but I'm not sure if there's a change that would improve upon that?
Also note that you can now turn off messages automatically getting marked as read altogether.

I'm not sure if there's a change that would improve upon that?

As I said, having clicking the channel open the channel view together with marking as read "only in conversations" seems like the best option to me in terms of avoiding accidental marking-as-read.

Ah, makes sense. Yeah, while we aren't making that the default, it sounds like that configuration will work well for you. :)


per origin timeout

is there any way to configure response timeout per origin, or, at least, global one?

@arnitolog I just merged this feature into master for you. I am waiting on #121 to be completed and will spin up a release, if you use our docker hub.


Cannot install lwip

Expected behavior
lwip should install normally
What actually happens
I get this error
In file included from ../src/lib/png/png.c:14: ../src/lib/png/pngpriv.h:805:4: error: ZLIB_VERNUM != PNG_ZLIB_VERNUM "-I (include path) error: see the notes in pngpriv.h" error ZLIB_VERNUM != PNG_ZLIB_VERNUM \    ^ 1 error generated. make: *** [Release/obj.target/lwip_decoder/src/lib/png/png.o] Error 1 gyp ERR! build error  gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack     at ChildProcess.onExit (/Users/MyUser/.nvm/versions/node/v7.6.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23) gyp ERR! stack     at emitTwo (events.js:106:13) gyp ERR! stack     at ChildProcess.emit (events.js:192:7) gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12) gyp ERR! System Darwin 16.3.0
I've rebuilt using npm rebuild lwip but still doesn't work. I've set up node-gyp correctly as well as the other dependencies. Is this a problem for you as well?
I think this is a compatibility problem with Node.js 7.6.0
What version are you using?

Fixed. lwip is incompatible with 7.6.0 but works with 6.10.0.


[BUG] Invalid key prefix format for dlq

Describe the bug
I have added the dlq to OpenSearch sink. And when I used "error/" as the key_path_prefix, the full output file of dlq is 'error//dlq-v2-test-pipeline-opensearch-2023-...' which contains an extra unexpected / in between.
Note that / still is a valid key in Amazon S3.
To Reproduce
Steps to reproduce the behavior:

Add below dlq config to opensearch sink

  sink:
    - opensearch:
        dlq:
          s3:
            bucket: "xxx"
            key_path_prefix: "error/"
            region: "us-west-2"

Run the pipeline and try get some errors

Check the dlq bucket for error files.

Expected behavior
The current output key is error//dlq-v2-..., expected output key is error/dlq-v2-...
Screenshots
N/A
Environment (please complete the following information):

OS: MacOS (local)
Version: 2.2

Additional context
N/A

Thanks @daixba for reporting this.
It seems that we should only add a / when the input does not already end with a /.

@asifsmohammed and I discussed this during implementation as well and I elected to leave it as is.
I find the current implement is more flexible and prefer to not dictate to the end user the possible options for their key_prefix. A key prefix is just a key and S3 has no concepts of folders.  If a customer wants an extra slash they can explicit add it with the current implementation by putting an extra/ on the end. If they want 4 / the can have it too.
@daixba if you remove the / from your configuration (key_path_prefix: "error") your dlq events appear with the key prefix: error/dlq-v2-....

@cmanning09 , As you noted, S3 doesn't have a concept of folders. And ListObjectsV2 allows for delimiters other than /.
This makes it seem that Data Prepper shouldn't take an opinion as to what the delimiter is. This would go in line with not adding a / at all in Data Prepper.
This could allow users to configure prefixes with alternate delimiters or no delimiter at all.
e.g.

error:dlq-v2-
errordlq-v2-

Good point. Given we have already released this. Any change would potentially be breaking.
I would like to propose adding a delimiter parameter. This parameter would be optional and default to "/"
Any thoughts on this?

I don't think delimiter is useful here. Eventually, user needs to Athena (or other tools) to analyze the failed objects rather than API calls, that is why dynamic prefix is more helpful here because they can do dynamic partition for prefix like  year=2021/month=01/day=26/ etc.
I raised this issue here because It's not very clear of setting key_path_prefix.  If I put error/ as the prefix, my intention is that all the keys of the error files are like error/xxx rather than error//xxx. I wouldn't expect Data Prepper add an addtional / in between of the prefix I provided and error files. Of course, people might have different understanding of the key_path_prefix, and I also understand the flexibility of adding any numbers of / at the end if I wanted to, however it's unlikely the happen.
Just for references:

When you try to enable AWS ALB access logs, you are not allowed to provide a prefix end with /.
When you set up prefix in AWS Kinesis Data Firehose, if you use prefix abc, all the files in S3 is like abcxxx, if you use prefix abc/, all the files in S3 is like abc/xxx.

So my recommendation is that either it's well documented that we will add an additional / in between or simply add key and prefix in the buildKey function.
I hope this makes sense.

@cmanning09 , Actually, I think I take back my previous comment.
A user today probably needs to configure Data Prepper as such:
key_path_prefix: "error"

If they add the / at the end, they get something they probably don't want.
So if we drop the automatic addition of the /, we will break the existing good configurations. Thus, I tend to think we should add the / only if the user did not end with a trailing /.

@cmanning09 , Actually, I think I take back my previous comment.
A user today probably needs to configure Data Prepper as such:
key_path_prefix: "error"

If they add the / at the end, they get something they probably don't want.
So if we drop the automatic addition of the /, we will break the existing good configurations. Thus, I tend to think we should add the / only if the user did not end with a trailing /.

I think this is a more thoughtable design. Especially considering this feature is already released.  I believe if a user put 'error' or 'error/', his intention is same which is to put all files under this folder.
I have just looked how AWS CloudFront service take this.  When trying to enable the CloudFront standard logging, I put 'error' or I put 'error/', I have got the same result.
Fundamentally speaking, this issue is not really a bug, it's just a clarification of the prefix and more thoughtable design based on user's intention, because regardless how we design it, customer can get what they want if they follow our guidance.

I have concerns about making the additional delimiter deterministic. The following prefixes would result in the addition of /

"error"
"error:"

The second scenario that @dlvenable raised earlier is concerning to me. I see this as a bug. We are assuming the user will always want to use / as a delimiter which is not true. I don't see a path forward without removing the automatic addition of /.

I tend to think that we can say that Data Prepper only supports / as a delimiter to avoid breaking existing configurations. I think most users are using / as the delimiter.
Another option could be to look at the last character and see if it is some symbol (not a letter or number). If it is, then we do not add anything to the end. This is basically a generalization of my comment above but for characters other than /.
Either that, or we leave the behavior as it is until 3.0.

I am onboard if we have consensus stating Data Prepper only support / as a delimiter at this time. I will update the PR. Thanks y'all for discussion.


Invalid

✄ -----------------------------------------------------------------------------
Thank you for your Pull Request! 🙏
Before you submit, please check that:

[ ] Description: You added a brief description of the PR, e.g.:

What does it do?
What important points should reviewers know?
Is there something left for follow-up PRs?

[ ] Labels: You labeled the PR appropriately if you have permissions to do so:

[ ] A* for PR status (one required)
[ ] B* for changelog (one required)
[ ] C* for release notes (exactly one required)
[ ] D* for various implications/requirements
[ ] Github project assignment

[ ] Related Issues: You mentioned a related issue if this PR is related to it, e.g. Fixes #228 or Related #1337.
[ ] 2 Reviewers: You asked at least two reviewers to review. If you aren't sure, start with GH suggestions.
[ ] Style Guide: Your PR adheres to the style guide.

In particular, mind the maximal line length of 100 (120 in exceptional circumstances).
There is no commented code checked in unless necessary.
Any panickers in the runtime have a proof or were removed.

[ ] Docs: You updated any rustdocs which may need to change, as described here.
[ ] Polkadot Companion: Has the PR altered the external API or interfaces used by Polkadot?

[ ] If so, do you have the corresponding Polkadot PR ready?
[ ] Optionally: Do you have a corresponding Cumulus PR?

Refer to the contributing guide for details.
After you've read this notice feel free to remove it.
Thank you!
✄ -----------------------------------------------------------------------------

Please refrain from opening further of such MRs, thank you.

ok


Struct Literals in ExprLet

Description
Struct literals are currently disallowed in the Parse implementation for ExprLet
I am unsure why this is the case

ran cargo test --release --all-features with let allow_struct = AllowStruct(true); and it appears to work just fine, so there are currently no tests exposing this behaviour of the Parse implementation?
is there a reason for the restriction?

Example

Fixed in 2.0.66.


Add review for Love to Sweet You

:pancakes:

Hi @lucasmdrs
would love to have your review on the review :wink:
Thank you! :sparkles:


Performance issue when loading large number of nodes

The chart is getting un-responsive when adding huge data

This is happening when adding config={{ smartRouting: true }}

Smart routing with large no of nodes causing performance issue

I'm experiencing the same issue.


[Bug fix] Fix rule B909's panic when checking large loop blocks

Summary

This pr should close #11771 by changing LoopMutationsVisitor::<field>branch from u8 to u32.
Test Plan

Tested using the example programme mentioned in the related issue.

Thanks


Add Divisible (contravariant applicative)

I deplore the lack of tests. Is there a particular reason? Flemme?

This is voluntary. I still find it hard to believe that the way we do tests is correct (it's long, wordy and we don't expose the functors that generate the tests...)
I intend to do (yet another!) pass on the tests to improve their cutting, so I didn't find it very useful to propose a test suite and then revoke it...


buildah: 1.16.5 -> 1.17.0

https://github.com/containers/buildah/releases/tag/v1.17.0

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

LGTM :)


Update headless option

Description
Update headless option
https://developer.chrome.com/docs/chromium/new-headless

Relevant Issues :
Relevant PRs :
Type of change :

[ ] New feature
[x] Bug fix for existing feature
[ ] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

@oxsoft thanks for both your PRs, I'm not sure yet if this needs to go as 1.5.0 or 1.5.1 - will update soon


feat/wizzard: Scores missing color box for scores and severities

The scores are missing two parts:

Scores missing color box for scores and severities
Attribute values should be
a) boxed and
b) collapsed by default

Score and severity (as they are readonly) could be prompted without the label if the group is labeled (cf. also https://www.first.org/cvss/calculator/3.1)

should be resolved by https://github.com/secvisogram/secvisogram/pull/412


macvlan support

Is your feature request related to a problem? Please describe.
I am trying to setup Multus CNI, but it requires macvlan. I would like to have macvlan added, or know how to add it myself.
Describe the solution you'd like
Ability to bridge host network adapter to pod for mDNS/broadcast. This is usually done via macvlan.
Describe alternatives you've considered
Not sure of any other alternatives for bridging host adapter within kubernetes for mDNS/broadcast beyond macvlan.
Additional context
I have a service that needs to be able to attach to the same subnet as the host itself, and be able to utilize mDNS/broadcast for avahi services.
failed to setup network for sandbox "105d7c9c7cf03f543f3e5504c67c8390f2569050d7aaa32df179d3ded90a85b0": [service-stack-1/mdns-bridge-5d6b9ff4c4-5bjnc/:macvlan-conf]: error adding container to network "macvlan-conf": failed to find plugin "macvlan" in path [/opt/cni/bin /var/lib/rancher/k3s/data/<hash-here>/bin]

Same here. Did you find any alternatives?

I left k3os due to it being abandoned. K3s or k0s on something like Debian or Arch should work, as there is macvlan support.


Add description of the resource to the detail page

Description
As a Concourse User
I Can see the description of the resource when I am on the resource details page
So That I can evaluate if this is a resource that I want to use
Acceptance Criteria
as OSS Concourse User
when the resource contains a description
when I am on the detail page of a resource
I can see the full description of the resource
as OSS Concourse User
when the resource does not contains a description
when I am on the detail page of a resource
I can not see the description or any other placeholder for the description
The description based on the readme for the first 30 resources including the 12 core concourse resources can be found here
Notes

description was possibly cut in the index page, here have to be completely shown
this is dependent on story #15

Accepted by @Pivotal-Kevin-Curley. Behaviour is as per acceptance criteria.


add table-of-contents command

in the notebook menu, use an hrule to make a section of the existing commands, and add "show table of contents"
show table of contents
collapse all sections
open all sections
the ToC view opens all sections except closes the leaves.

just doing it with sections doesn't work (see https://github.com/twosigma/beaker-notebook/pull/3807).
need something stronger, maybe some kind of floating element with just the section tree.


remove hand holds -> classify -> populate with hand holds

this prevents the issue of the classifier having a hard time detecting a hold because we're drawing something on top of the hold

Not going to fix at the moment unless it becomes a big problem.
Adding the following code to GrabFrameAndClassify will remove the circles and allow the projector to refresh before a frame is grabbed.
 cleanHandHolds(ref this.handholds);
 yield return new WaitForSeconds(0.1f);

For whatever reason, adding the yield return new WaitForSeconds(0.1f) seems to lead to a much higher number of frames coming back null. If the projected circles become a big issue, we can reopen and investigate.


fetching JS bundle not working

Hello,
First, thank you for your work.
Second, I have a problem when reloading my scripts on Genymotion.
When reloading JS, I have the message "Fetching JS bundle" appearing for a very quick time and then disappearing and my scripts are not reloaded.
It only works the first time after lauching react-native start.
If I want to reload it, I have to start again "react-native start".
Any ideas on how to fix this ?
Thank you very much for your help,
Jeremie

This question would probably be better suited for Stack Overflow.
Do you see any errors in the terminal window?

No errors : just "[Hot Module Replacement] Server listhening on /hot.
And when I reload I have :
[15:16:17]  request:/index.android.bundle?platform=android&dev=true&hot=f
alse&minify=false
[15:16:17]    request:/index.android.bundle?platform=android&dev=true&hot=f
alse&minify=false (43ms)

`[20:27:30]  Building Dependency Graph
[20:27:30]  Crawling File System
[Hot Module Replacement] Server listening on /hot
React packager ready.
[20:29:14]    Crawling File System (104136ms)
[20:29:14]  Building in-memory fs for JavaScript
[20:29:15]    Building in-memory fs for JavaScript (805ms)
[20:29:15]  Building in-memory fs for Assets
[20:29:15]    Building in-memory fs for Assets (696ms)
[20:29:15]  Building Haste Map
[20:29:16]  Building (deprecated) Asset Map
[20:29:16]    Building (deprecated) Asset Map (142ms)
[20:29:16]    Building Haste Map (408ms)
[20:29:16]    Building Dependency Graph (106054ms)
[20:29:25]  request:/index.android.bundle?platform=android
[20:29:25]  find dependencies
transformed 678/678 (100%)
[20:29:29]    find dependencies (4431ms)
[20:29:30]    request:/index.android.bundle?platform=android (4703ms)
[20:29:48]  request:/index.android.bundle?platform=android&dev=true&hot=true&minify=false
[20:29:48]  find dependencies
transformed 678/678 (100%)
[20:29:49]    find dependencies (942ms)
[20:29:49]    request:/index.android.bundle?platform=android&dev=true&hot=true&minify=false (1017ms)`
why so slow

@isszz me too
@Yirmeyah I've changed this index.js and it worked...."app_name\node_modules\react-native\node_modules\node-haste\lib\FileWatcher\index.js "
var MAX_WAIT_TIME = 120000;==>>
var MAX_WAIT_TIME = 360000;

@Deain Im have same Problem..and your solution not working.
see this

found "react-native/packager/react-packager/src/DependencyResolver/FileWatcher/index.js"
then change "const MAX_WAIT_TIME = 120000" to "const MAX_WAIT_TIME = 360000"

@facebook-github-bot label Icebox

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/fetching-js-bundle-not-working
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.

@facebook-github-bot close

I am also in this problem i could not get out of it.It is not serving android.bundle.js.
Everytime in mobile
Please Wait...
Fetching JS bundle


Added Telegram notify

Hi, welcome to contribute, please fix CI :) @lowk3v

This is the latest error, please use goimports -ed sort @lowk3v

@lowk3v https://github.com/arugal/frp-notify/runs/7948799412?check_suite_focus=true#step:6:71 It looks like your unit test failed


Matchers v1

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Checklist:

[x] I have ensured that all new code is covered by tests
[x] I have run make format to format the code according to guidelines
[x] I have documented any new functions introduced
[x] I have updated the changelog in accordance with https://keepachangelog.com/en/1.1.0/
[x] I have updated the README, if required

Addresses #2


[v0.12-beta2] Include required review count

This PR is important when upgrading go-github, otherwise updates using this provider will fail.
This commit includes the required_approving_review_count field on the
github_branch_protection resource, allowing to manage the minimum
amount of reviewers to allow a merge to happen.
This field must be between 1 - 6, according to the docs, and must be
valid if present.
Bumping the go-github to v24 made it default to 0 when not
present, causing the following error

GitHub API error when count is 0
422 Invalid request.

No subschema in "anyOf" matched.
0 must be greater than or equal to 1.
Not all subschemas of "allOf" matched.
For 'anyOf/1', {"dismissal_restrictions"=>{"users"=>[], "teams"=>[]}, "dismiss_stale_reviews"=>false, "require_code_owner_reviews"=>true, "required_approving_review_count"=>0} is not a null. []

Payload:
{
 "required_status_checks": {
  "strict": true,
  "contexts": [
   "lint",
   "test"
  ]
 },
 "required_pull_request_reviews": {
  "dismissal_restrictions": {
   "users": [],
   "teams": []
  },
  "dismiss_stale_reviews": false,
  "require_code_owner_reviews": true,
  "required_approving_review_count": 0
 },
 "enforce_admins": true,
 "restrictions": null
}

Needs

[ ] [v0.12-beta2] Bump go-github version v24 (https://github.com/terraform-providers/terraform-provider-github/pull/215)

Thanks, @bltavares! I'm going to merge this down into the sdk-v0.12-beta2 branch for now and then whoever drives the v0.12-compatible release for this can use that branch as a basis when ready.


Add interface to phone number client

Contributing to the Azure SDK
Add an interface to the phone numbers client, so that they can use the interface for mocking purposes.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Communication.PhoneNumbers


Bug/jenkins 45011 commit in run result header is not clickable

Description
re-factor the CommitId component so it can accept an url and generate a link in case it is present

See JENKINS-45011.

Submitter checklist

[x] Link to JIRA ticket in description, if appropriate.
[x] Change is code complete and matches issue description
[x] Appropriate unit or acceptance tests or explanation to why this change has no tests

Reviewer checklist

[ ] Run the changes and verified the change matches the issue description
[ ] Reviewed the code
[ ] Verified that the appropriate tests have been written or valid explanation given

@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@NicuPascu this will need to be moved to the dir in the blueocean-plugin repo


Issue UI BCA error because new PDF report format since Oct 2024

Hi, I love your project about "bank-pdf-statement-parser-id" and I've used it for daily purpose since 5 months ago. Usually BCA and Mandiri successfully parsed. But, since Oct 2024, BCA extend new format in their PDF format.
Problem:
The BCA e-statement PDF format has changed. When attempting to parse a BCA statement file, the app either fails to parse the document or throws an error due to unrecognized fields or mismatched data structure.
Current Behavior:

The app successfully parses Mandiri debit and Mandiri CC statements.
However, it encounters issues when parsing BCA statements
Some fields in the parsed BCA statements don’t align with TrxRecord structure.

Screenshot
Error Parsing (BCA Statement Report - Oct 2024)

Success Parsing (BCA Statement Report - Before Oct 2024)

Hi thanks for reporting! I'll need to check the new bca statement pdf file first and see how to fix it


Language button UI

Describe
i would like to add minor changes to the language change button and improve its font size and style to match the vibe of the page and navbar
To Reproduce
Steps to reproduce the behavior:

Go to site
Click on navbar
See error

Expected behavior
Screenshots

Additional context
Please assign this issue to me under gssoc'24

It seems that no further action is needed at the moment. If you have any additional issues, feel free to reach out.


THY-69 setup firebase

I learned of a problem in the cwackerfuss repo when learning more about .env variables. I'll look forward to explaining on Monday.

Should I wait to merge this in light of the .env stuff @kadenbking ?

Yeah let's hold off on reviewing until we can discuss these changes. Thanks for asking @djyarnell0

Sounds good! other than that looks great to me


NFCORE_RNASEQ:RNASEQ:ALIGN_STAR:STAR_ALIGN: failed with exit status 140 and 102

Hi,
The nfcore/rnaseq pipeline (alignment with STAR-SALMON) runs for days and eventually fails with an exit status of 140. I checked the .out files, there was no explicit error.
Tracing the .out/ pipeline_info trace files and checking the work directory, I noticed the threads for mapping were created, but did not run till completion.

I noticed this step is running with 12 threads (--runThreadsN), and may not be enough. Thus I did a bash .command.run with --runThreadN set to 128 and the step completed successfully!
However, when I am using the --runThreadsN option as one of the parameters to --extra_star_align_args --runThreadsN 128 in the script, it takes the extra parameter but does not remove the old option from the command, while executing, giving me the following error of 102.

Is there a way to handle this?

Yes, you can increase the number of threads via a custom config. Please see the documentation on custom configs and Tuning workflow resources.
I have some doubts, though, if the number of threads were truly the root cause of your initial issue. Version 2.7.9a is a couple of years old and 2.7.10 fixed a number of issues that could cause STAR to hang in perpetuity I guess there are some default settings in the config, that my not be chosen wisely for plant genomes and that may with that old version cause issues. Preferably, always try running the latest version of a pipeline.

Hi Matthias,
Thank you for the response. I am assuming if I add more cpus, it will consider it as runThreadN value, right? and ofcourse I will assign more memory. I did try custom config with more memory, but did not work and maybe need more cpus, therefore more threads.
I am using a server to work with, I will check if star version can be updated to latest. Regarding default settings for plant genomes, they have worked in the past, and hence should not be an issue.
One thing to note, my input data is a special RNAseq output which may be the cause of the problem! Bowtie works fine with the data and so I thought with STAR it would work too!
Anyways, I will try to use custom configs and see if it gets resolved.

I am assuming if I add more cpus, it will consider it as runThreadN value, right?

Yes, because the module is written in that way. You can also change the number of CPUs utilized by a process via its config.

I am using a server to work with, I will check if star version can be updated to latest.

No need to do that. The version that is installed locally on the server does not matter, since the pipeline will run its own, (potentially different) version inside a Singularity (-profile singularity) or Docker (-profile docker) container. But that it is using that old STAR version tells me, that you are running an outdated pipeline version. Must be before 3.7 or so?
But yes, if it is some kind of special RNA-seq, you need to consider this in the tools' configs.

This thread has been quiet for a while, so @DollyCM I'm assuming that @MatthiasZepper 's assistance helped you out here. Please do reopen if you feel there's a pipeline bug that persists in the latest version.

Also note that the #rnaseq channel on the nf-core Slack is a good place to ask for help.


lodestar-cli unit tests

Fixing #1255
Decided to consolidate everything into the account tests since a lot of account partially depends on init anyway

lodestar unit tests have error but for some reason check has passed. Seems like those lodestar-cli tests are taking quite long (maybe make them e2e)?

lodestar unit tests have error but for some reason check has passed. Seems like those lodestar-cli tests are taking quite long (maybe make them e2e)?

given that they run the yargs instance directly I would make them e2e too

@mpetrunic sorry, had to merge from master.  everything up-to-date now


What happened to the original master version?

This theme was made originally by AndrewQuinn (Archive.org snapshot). It was deleted, so I restored this here from a backup that I (thank God!) had, dated 13 Nov 2022 (last Archive.org snapshot is 20 Nov 2022).
Related issues:
https://github.com/hiAndrewQuinn/resorter/issues/1

Updated repo is https://github.com/Siilikuin/minimum-viable-hugo - I need to update this fork!


fix(imports): update named web exports to properly provide esm file i…

Note: this is a breaking change

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

Project coverage is 51.23%. Comparing base (a7d2277) to head (151f128).

Additional details and impacted files
@@           Coverage Diff           @@
##            alpha     #147   +/-   ##
=======================================
  Coverage   51.23%   51.23%
=======================================
  Files          29       29
  Lines        1093     1093
  Branches      211      211
=======================================
  Hits          560      560
  Misses        514      514
  Partials       19       19

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

will be merged in #152


Fix to take care of multiple author list

In case the author parameter is a []string, which is the default for ox-hugo
output.

Thanks for this, @frankieliu I've asked @regisphilibert to have a second set of eyes when he gets a chance.

This looks good to me.  Adding:
author:
  - "Tom Scanlan"
  - "Foo Bar"

shows:
By Tom Scanlan, Foo Bar

Thank you, @tompscanlan


version_bridge.fragment_upload.fragment_upload_async returns UploadSession when success

After the last chunk of file is uploaded to server, fragment_upload_async() returns a UploadSession whose _prop_dict is one for Item resource. This happens because ItemUploadFragment.post() always uses the response to construct UploadSession object. Shouldn't it return an Item directly if the session succeeds?

Thank you for reaching out and for your patience. This SDK is being officially deprecated. See #209 for more information


Is it possible to start a substrate BABE blockchain with no Grandpa authorities and BABE validators?

I'm trying to implement a PoS network on substrate using substrate provided pallets - pallet_session, pallet_staking, pallet_babe, etc. The current Runtime and chain spec implementation is similar to what is found in the substrate repository. I've realized that I need to set Session keys for GenesisConfig before starting the blockchain. I also noticed that the Session keys set for SessionConfig are used to configure the grandpa authorities.
My questions are:
Is there a way to start the blockchain such that no session keys are set?
Do all grandpa authorities need to be hardcoded in the chain spec? If not, how are the authorities added after nodes have gone live?

Is there a way to start the blockchain such that no session keys are set?

There is no other way to emit session keys from genesis as far as I know, but feel free to ask substrate stackoverflow since it has most devs active there.

Do all grandpa authorities need to be hardcoded in the chain spec? If not, how are the authorities added after nodes have gone live?

Only genesis authorities needs to be hardcoded in chainspec, if you switch to PoS which means the validators are elected based on NPoS.


WIP: interAsset contract: addVaultCollateral etc.

cc @0xpatrickdev
DRAFT until:

[x] interAsset contract: start mintHolder; add to vbank; add to vaultFactory, reserve, auction (UNTESTED)
[ ] core eval script to start interAsset contract
[ ] handle adding price feed
[ ] test adding vault collateral

stretch:

[ ] add PSM

subsume mintHolder
idea: one interchainMints contract instead of N mintHolder contracts. ...

it was pretty straightforward:
$ yarn test test/test-interchainMints.js
yarn run v1.22.21
$ ava --verbose test/test-interchainMints.js

Removing intrinsics.Symbol.dispose
Removing intrinsics.Symbol.asyncDispose
(Error#1)
Error#1: out of date: [ { relativePath: '', mtime: '2024-04-11T17:04:08.476Z' } ] . interchainMints bundled at 2024-04-11T16:45:24.237Z
  at async bootAndInstallBundles (file:///home/connolly/projects/ag-power-tools/contract/test/boot-tools.js:112:20)
  at async file:///home/connolly/projects/ag-power-tools/contract/test/test-interchainMints.js:37:31

bundles/ add: interchainMints from /home/connolly/projects/ag-power-tools/contract/src/interchainMints.js
bundles/ bundled 121 files in bundle-interchainMints.js at 2024-04-11T17:23:16.719Z
interchainMints (re-)installed as b1-0f39c
  ✔ interchainMints contract adds IBC tokens to vbank (1.6s)
    ℹ bootstrap
    ℹ brand timer: new Promise
    ℹ brand IST: new Promise
    ℹ brand Invitation: new Promise
    ℹ issuer IST: new Promise
    ℹ issuer Invitation: new Promise
    ℹ brand timer settled; remaining: [
        'IST',
        'Invitation',
      ]
    ℹ brand IST settled; remaining: [
        'Invitation',
      ]
    ℹ brand Invitation settled; remaining: []
    ℹ issuer IST settled; remaining: [
        'Invitation',
      ]
    ℹ issuer Invitation settled; remaining: []
    ℹ publish bundle interchainMints b1-0f39c
    ℹ installation interchainMints: new Promise
    ℹ installation interchainMints settled; remaining: []
    ℹ instance interchainMints: new Promise
    ℹ instance interchainMints settled; remaining: []
    ℹ interchainMintsKit {
        adminFacet: Object @Alleged: adminFacet {},
        creatorFacet: Object @Alleged: InterchainMints {},
        creatorInvitation: undefined,
        instance: Object @Alleged: InstanceHandle {},
        publicFacet: Object @Alleged: Incapable {},
      }
    ℹ {
        brand: Object @Alleged: Asset1 brand {},
        value: 0n,
      }
    ℹ {
        brand: Object @Alleged: Asset2 brand {},
        value: 0n,
      }
    ℹ {
        'ibc/1234567890123456789012345678901234567890123456789012345678901234': {
          brand: Object @Alleged: Asset1 brand {},
          denom: 'ibc/1234567890123456789012345678901234567890123456789012345678901234',
          displayInfo: {
            assetKind: 'nat',
            decimalPlaces: 6,
          },
          issuer: Object @Alleged: Asset1 issuer {},
          issuerName: 'Asset1',
          proposedName: 'Asset1',
        },
        'ibc/2234567890123456789012345678901234567890123456789012345678901234': {
          brand: Object @Alleged: Asset2 brand {},
          denom: 'ibc/2234567890123456789012345678901234567890123456789012345678901234',
          displayInfo: {
            assetKind: 'nat',
            decimalPlaces: 6,
          },
          issuer: Object @Alleged: Asset2 issuer {},
          issuerName: 'Asset2',
          proposedName: 'Asset2',
        },
      }
interchainMints start args: {
  installation: Promise { Object [Alleged: BundleIDInstallation] {} },
  privateArgs: {
    nameAdmins: {
      brand: Object [Alleged: NameHubKit nameAdmin] {},
      issuer: Object [Alleged: NameHubKit nameAdmin] {}
    },
    bankManager: Object [Alleged: BankManager] {}
  }
}
interchainMints started
  ─

  1 test passed
Done in 2.56s.

cc @0xpatrickdev


Removed cassandra-consistency from all the configs

Coverage decreased (-0.06%) to 67.887% when pulling 3e1e5c8ae24b6012beb9994e9e6c1fb35ccc1070 on anish531213:aanish/remove-cassandra-consistency-config into 61d1a8a7330101263e48a1365bcf61862f6a3818 on uber:master.


Default interfaces on multi-homed servers

I ran into a strange problem today with Unbound while using this module. I'm not sure whether this is a configuration problem or a bug, so I'm reporting it here first.
On a server with two IP addresses, I had to explicitly list both IP addresses in unbound.conf before Unbound would answer queries on the second address. This ran counter to my expectation that I could set  interface: <IP_ADDRESS> to listen on all IP addresses.
One possible solution is changing this module to explicitly list all IP addresses as listening interfaces in unbound.conf.
Before making that change, it would be prudent to:

Confirm that this is 100% reproducible on a different system
Ask the maintainers of Unbound (NLnet?) whether this behaviour is intended.

--
The full story
My server had Unbound installed and configured to listen on "<IP_ADDRESS>" interface. It was successfully responding to DNS queries for other hosts as defined by the access-control directive, even on different subnets.
Then I added a second IP address to the server as a virtual interface (eth0:0). Strangely, Unbound refused to answer DNS queries on this second IP address, even after restarting the service. Running netstat -tapn confirmed that Unbound was listening on <IP_ADDRESS>:53.
Then I explicitly listed each local IP address in unbound.conf and restarted Unbound. At that point, the server successfully responded to DNS queries as expected.
interface: <IP_ADDRESS>
interface: <IP_ADDRESS>

I'm using Scientific Linux 6.4, and the version of Unbound is 1.4.19 from EPEL.

I believe this issue has been addressed by the inclusion of the interface param in params.pp.


[Feature]: Custom export behaviour for Gitlab pages

What problem does this feature solve?
As a customer I want to publish the Rsdoctor report on a Gitlab Pages page or a custom hosting solution to be able to access the generated reports from outside. This will help customers monitor the running applications without the need of a local running system.
Acceptance:

Create a output behaviour to generate a static dist folder in the project directory
The plugin option has a new parameter to toggle the static export behaviour
Customers can use the dist export for Gitlab pages or a custom hosting

What does the proposed API look like?
New plugin option:
new RsdoctorRspackPlugin({
      [...],
      staticExport: true
    }),

Generated static files for usage:
// my-repository-path/dist/rsdoctor/index.html
// my-repository-path/dist/rsdoctor/main.css
// my-repository-path/dist/rsdoctor/main.js

Good idea! I'll include this in the plan.
Perhaps you only need to report assets once. If you need historical assets, you should keep the reports.

Thank you for the fast action on this request. Really appreciate it!

@easy1090 any rough idea when this will be implemented?

At present, in May, the high-priority requirement of Rsdoctor is to improve the efficiency of build analysis on webpack or rspack, but the ability of custom report will be realized in June or July.
Currently, the data of Rsdoctor is too large, which may cause the page to crash, so a streamlined page export is required for the custom report.
In June, the ability of the Rsdoctor plugin system will be provided. During the construction process, users can obtain and operate the Rsdoctor analysis data by themselves:

// xxx.config.js
 new RsdoctorWebpackPlugin({
      extends: [RsdoctorCustomPlugin]
 })

 // rsdoctorCustomPlugin.ts

 const RsdoctorCustomPlugin = definePlugin(() => ({
  handle(data) {
    // .. do something with the data context， the data includes rsdoctor's all analysis data.
  },
}));

@easy1090 Thank you for the insights on the current development! I will check out the custom plugin approach. Appreciate your efforts! 🥳

You can use rsdoctor's brief mode, @rsdoctor/* > 0.4.0, https://rsdoctor.dev/guide/start/cicd


DBeaver does not display new tables created in DuckDB databases connected via ATTACH

Description
When I use the ATTACH statement to connect another DuckDB database and run a create table statement, the DBeaver Database Navigator for the attached database does not show the new table even though the create table statement runs successfully.
I'm able to query the newly created table, but I can't view it in my DBeaver side panel window.
Sometimes I can get one new table to show up, but any subsequent create table statements result in no new tables showing up in the attached database's Database Navigator window. It also doesn't show up even after rebooting DBeaver.
I have tried this with multiple versions of DuckDB.
Cross posted to DuckDB Git because I'm not sure if this is a DBeaver bug or DuckDB bug.
https://github.com/duckdb/duckdb/issues/12326
DBeaver Version
24.1.0
Operating System
macOS Sonoma 14.5
Database and driver
DuckDB 1.0.0
Steps to reproduce
Open up a new SQL script for a current DuckDB database. Let's refer to this initial DB as duck1. Run the following:
attach '/path/to/duck_database2.db' as duck2;

-- confirm two database are connected to our session
show databases;

create table duck2.new_table as
select * from duck1.table limit 10;

Once the code runs, attempt to view the newly created new_table in the Database Navigator. The first attempt at this may work as expected, but subsequent create table statements have not been working for me.
Additional context
No response

@pbrady32 I'm not sure if this is a bug. This looks like an expected dbeaver behaviour. WHen you create a new table with a query in SQL Editor it won't be shown in the navigator until you manually refresh it by selecting Refresh in the context menu or pressing F5 on the tables folder or any higher level node.

@Matvey16 thanks for mentioning that. I completely forgot to say that refreshing the database and table views does not help. It still doesn’t show the newly created tables.
When I run show tables; in DuckDB it does indeed show that new tables are being created in the attached database as expected. They just refuse to show up in the Navigator.

@pbrady32 And would a select on this new table work in SQL editor?

@Matvey16 yes a select on the new table does work as expected.

@pbrady32 can you please record a video like in my comment where I can see that you create a new table and it doesn't show in the navigator after refresh? Maybe I would be able to see what we are doing differently.
Also one more question. Will the table still be invisible after disconnect and reconnect?

It's been a while since no update here. If the issue is still actual please let me know and provide additional information.

@Matvey16 @E1izabeth I'll check this soon. I've been on leave for a few weeks, so I haven't worked with our data since early July.

@pbrady32
Sure, we're waiting :)

I have the same issue. New tables sometimes don't appear when using DuckDB javascript driver as well.
SELECT * FROM AA;

works and lists the rows while
SELECT * FROM information_schema.tables

won't show the newly imported table. I am creating the tables using the CSV import feature with the following query:
CREATE TABLE ${tableName} AS SELECT * FROM read_csv('${filePath}')

So this might not be a dbeaver issue.

Had sometimes the problem : refreshing db doesn't reloaded correctly new tables // disconnect-reconnect not refreshed neither. For me only shutdown Dbeaver worked when it happened. Hope it helps

@Matvey16 Here is the video you requested. Refreshing and disconnecting both do not fix the issue.
I am on DBeaver Version <IP_ADDRESS>409011551 (installed today) and latest DuckDB 1.0.0
https://github.com/user-attachments/assets/423ee58b-c5eb-45c7-9a6e-0aea155fe885

@pbrady32 Thank you for the video. Now I can see the difference in our cases. On your video I see that you actually check tables in not only different databases, but actually different connections.
My first idea is that the attached databse in your script is called .../duck2.db and possibly the path for the database in connection settings can be .../duck2 which means those are two different files and therefore different databases. It looks likely because I see that you can simultaniously attach a database in one connection and also connect to it in another wich is impossible for me if it is the same file.
While you check this I would also like to ask you to look at this feature for DuckDB in DBeaver. YOu don't need to create a new connection if you are working with attached database. It will appear in the navigator in the same connection you are working in (After refresh)
https://github.com/user-attachments/assets/624fe81e-9fb3-48ea-b356-9a9bf7fac2ec

@Matvey16 Ahh got it! That makes sense. When I looked at the DuckDB documentation for the attach statement it wasn't clear to me that the other database should not be in another connection. This is super helpful. Thanks for the clarification!

@pbrady32 so the issue can be closed, right?

@E1izabeth yes it can, thanks!


Use capabilities not roles

Sorry, not quite sure what I am doing yet. Can you help me out jrf or grapplerulrich

@khacoder You don't need to close the PR. We can keep it open and work on it. What do you need help with? Ping me on slack.

When merged, solves #27

I am happy to make a PR upstream. I will work on here for the time being till it is fully ready.

@grappler Okidoki. let me know when you're ready for me to have another look.

I will update it for PHPCS 3.x and push the PR upstream.

Once this has been pulled upstream, this PR can be closed and a new PR will need to be opened just to add the new upstream sniff to the ruleset.

I would like to finish this one if I could please.

OK no problem, you may as well close this one??

For history:
This PR was closed when we replaced the master/develop branches with the re-organized stand-alone repo.
It will not be re-opened for the following reasons:

Once the upstream WPCS PR has been merged, that sniff should be added to the WPThemeReview ruleset instead (or extended).


Added documentation with API reference

Hi,
I've created a documentation with API reference, you can see an example at https://uvw.docsforge.com/
Hope it's helpful for anyone using UVW. The docs are built automatically every week so they should always be in sync with the code, readme, and any other tutorial files you might add.
If there are any additional tutorial pages you wish to add to the sidebar, or you wish to hide certain internal APIs from being displayed please let me know, everything is configurable.
Disclaimer - I'm the creator of docsforge

Oh... I know you! :smile:

I'm adding you to the list of contributors.
Since I know already how docsforge works, could you add me as a maintainer?
Thanks.

Thanks.
I transferred ownership.
FYI, you can see a list of all the undocumented API pages in here.
You can go over the list and if anything is important enough, maybe add something.