text:
feat: Capture values of nested blocks for custom rego policies

Is your feature request related to a problem? Please describe.
In reality, tfsec provides google-iam-no-user-granted-permissions. But, we want to allow to temporarily grant some strong IAMs of Google Cloud for temporary operations in the production environment. So, instead of turning off google-iam-no-user-granted-permissions, we tried to implement a custom rego policy to check if we grant database access permissions without IAM condition.
With IAM Conditions, you can choose to grant access to principals only if specified conditions are met. For instance, we are able to grant permissions with expirations.
However, as far as I am concerned, tfsec doesn't collect information about nested blocks. Let's consider if we have a google_project_iam_member resource with expiration by IAM condition. But, tfsec --print-rego-input doesn't show any values about the nested block.

https://aquasecurity.github.io/tfsec/v1.28.0/checks/google/iam/no-user-granted-permissions/

resource "google_project_iam_member" "test_no_project_level_spanner_data_viewer_without_iam_condition_true_01" {
  project = var.project_id
  role    = "roles/spanner.admin"
  member  = "user:dummy-user-01@example.com"

  condition {
    title      = "test"
    expression = "request.time < timestamp(\"2023-01-01T23:59:00Z\")"
  }
}

tfsec --print-rego-input | jq -r '.google.iam'

{
  "organizations": [
    {
      "__defsec_metadata": {
        "endline": 0,
        "explicit": false,
        "filepath": "",
        "fskey": "",
        "managed": false,
        "resource": "",
        "startline": 0
      },
      "projects": [
        {
          "__defsec_metadata": {
            "endline": 0,
            "explicit": false,
            "filepath": "",
            "fskey": "",
            "managed": false,
            "resource": "",
            "startline": 0
          },
          "autocreatenetwork": {
            "endline": 0,
            "explicit": false,
            "filepath": "",
            "fskey": "",
            "managed": false,
            "resource": "",
            "startline": 0,
            "value": false
          },
          "members": [
            {
              "__defsec_metadata": {
                "endline": 11,
                "explicit": false,
                "filepath": "tfsec/policies/prd/tests/test_no_project_level_spanner_data_viewer_without_iam_condition.tf",
                "fskey": "f9088d3ed2db9899500f703a07bb505300c2b5cbc122ac4365ca04af35422e64",
                "managed": true,
                "resource": "google_project_iam_member.test_no_project_level_spanner_data_viewer_without_iam_condition_true_01",
                "startline": 2
              },
              "defaultserviceaccount": {
                "endline": 11,
                "explicit": false,
                "filepath": "tfsec/policies/prd/tests/test_no_project_level_spanner_data_viewer_without_iam_condition.tf",
                "fskey": "f9088d3ed2db9899500f703a07bb505300c2b5cbc122ac4365ca04af35422e64",
                "managed": true,
                "resource": "google_project_iam_member.test_no_project_level_spanner_data_viewer_without_iam_condition_true_01",
                "startline": 2,
                "value": false
              },
              "member": {
                "endline": 5,
                "explicit": true,
                "filepath": "tfsec/policies/prd/tests/test_no_project_level_spanner_data_viewer_without_iam_condition.tf",
                "fskey": "f9088d3ed2db9899500f703a07bb505300c2b5cbc122ac4365ca04af35422e64",
                "managed": true,
                "resource": "google_project_iam_member.test_no_project_level_spanner_data_viewer_without_iam_condition_true_01.member",
                "startline": 5,
                "value": "user:dummy-user-01@example.com"
              },
              "role": {
                "endline": 4,
                "explicit": true,
                "filepath": "tfsec/policies/prd/tests/test_no_project_level_spanner_data_viewer_without_iam_condition.tf",
                "fskey": "f9088d3ed2db9899500f703a07bb505300c2b5cbc122ac4365ca04af35422e64",
                "managed": true,
                "resource": "google_project_iam_member.test_no_project_level_spanner_data_viewer_without_iam_condition_true_01.role",
                "startline": 4,
                "value": "roles/spanner.admin"
              }
            }
          ]
        }
      ]
    }
  ]
}

Describe the solution you'd like
If tfsec capture information about nested block, that would be best.
Describe alternatives you've considered
As far as I know, there is no alternative solutions.
Additional context
NA

I'm trying to understand, what would a custom policy look like? We've moved our efforts to Trivy. If the issue still persists, please open a discussion in the Trivy repo and we can assist you with it. https://github.com/aquasecurity/trivy/discussions

repo: aquasecurity/tfsec


text:
Installer

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[ ] 3.1
[*] 3.2
[ ] self-compiled devel branch

Mode:

[ ] Cluster
[*] Single-Server

Storage-Engine:

[*] mmfiles
[*] rocksdb

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[*] Ubuntu .deb
[ ] SUSE   .rpm
[ ] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[ ] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

Installer gets caught in time loop.
These are the steps to reproduce:

sudo apt install arangodb3
Type root password in dialog box, make a typo, such that you do no longer know what you wrote
In the next dialog box you can no longer proceed since you do not know the right password, click Cancel
Something happens and after a while you get an error dialog box which has only an "OK" button and if you choose it, the box comes back, caught. Not even Ctrl-C works.

ArangoDB 3.2.3 is now available for download. Please note that we switched our webserver and changed our download URLS for better performance.
Closing.

source: gharchive/issue

authors: dothebart neunhoef

repo: arangodb/arangodb

license_type: permissive

license_source: bigquery


text:
Error on 3.5.0-rc.3 arangod.exe auto-upgrade-start with 3.4.x database folder

My Environment

ArangoDB Version:        3.5.0-rc.3
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:  Manual Start
Configuration:               No changes
Infrastructure:
Operating System:        Windows 10
Total RAM in your machine:        32Gb
Disks in use:        SSD
Used Package:              Windows win64 zip Package

Component, Query & Data
Affected feature:
Upgrade

Size of your Dataset on disk: 42Gb
Steps to reproduce

Start .\arangod.exe --database.auto-upgrade true

Problem:
A error message is shown, although the upgrade was successful and the process ends:
2019-06-21T13:45:30Z [7536] ERROR [fae2c] {rocksdb} RocksDB encountered a background error during a compaction operation; The database will be put in read-only mode, and subsequent write errors are likely

I don't know whether the exit of the process is intentional, but since the upgrade did run well, maybe there should be no ERROR message. A normal start (.\arangod.exe) after the upgrade ran well and let me insert documents (no errors and no read-only mode in the new process).
Expected result:
No error message.

Hi @x3cion,
the exit of the arangod process with option --database.auto-upgrade true is intentional once the database upgrade has finished. Afterwards the same arangod command without option --database.auto-upgrade true has to be executed to startup the server again.
However it is not expected that the stated error message occurs during the upgrade. I was not able to reproduce this error when performing a 3.4.6-1 -> 3.5.0-rc.3 upgrade on a database directory with some sample data.

Do you have a backup of your 3.4.x database directory, that can be used to reproduce this error?
Which 3.4.x version did you use when performing the upgrade?
Since performing the upgrade, did you see any errors in the log?

Hi @x3cion,
Since we have not heard back from you in a while, I am closing this issue for now.
If this issue persists, please reply to my latest comment and we will reopen it.


text:
Added a forgotten Plan/Version increment.

This is a backport of a bug fix which was done in devel.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9948/

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr-linux/11718/

Tests blue.

source: gharchive/pull-request


text:
Make the reboot tracker catch failed coordinators, too.

Scope & Purpose
Make the reboot tracker catch failed coordinators, too.
Previously the reboot tracker was invoked only when a DB server failed or was restarted, and when a coordinator was restarted.
Now it will also act if a coordinator just fails (without restart).

[x] :hankey: Bugfix
[x] :pizza: New feature
[ ] :hammer: Refactoring
[x] :book: CHANGELOG entry made
[x] :muscle: The behavior in this PR was manually tested
[ ] :computer: The behavior change can be verified via automatic tests

Backports:

[x] Backports required for: 3.5 (https://github.com/arangodb/arangodb/pull/12636), 3.6 (https://github.com/arangodb/arangodb/pull/12606), 3.7

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.

http://172.16.10.101:8080/view/PR/job/arangodb-matrix-pr/11877/

http://172.16.10.101:8080/view/PR/job/arangodb-matrix-pr/11878/

http://172.16.10.101:8080/view/PR/job/arangodb-matrix-pr/11883/

Tests blue


text:
Exec tachikoma update 20160705083343

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Tachikoma.io detects file structure for david, you can set strategy, if you put .tachikoma.yml :dog:
#.tachikoma.yml
strategy: 'david'

Enjoy! :poodle:
Tachikoma.io Custom Configure

yertyeryt

etyrtyerytr

tyetry

authors: arastu pazjacket

repo: arastu/iran

license: mit


text:
Add nightly build with Clang's MemorySanitizer

Would have exposed the bug fixed in #753

https://cloud.cees.ornl.gov/jenkins-ci/blue/organizations/jenkins/MemorySanitizer/detail/MemorySanitizer/2/pipeline/12

Fix #64.

Can you please switch off all the builds, and put it in the continuous so that we could see the results. You also would want to use [ci skip] later.

repo: arborx/ArborX

license_source: github-api


text:
npx sandbox should init .arc-env

when starting it should read env vars and write them locally

it now warns if not present!

repo: arc-repos/arc-workflows


text:
Crashing

Is there any logging? This is crashing on one PC im trying to run it on, I have ran it on many others no issues. It closes after its compiled a list of apps

This are logs. The poweshell script uses transcript logging and you can find the logs in c:\BRU directory. Please zip and attach here or upload so we can find the cause. I have seen it (and other winform and gui based Powershell scripts) crash if there is an issue with dotnet. Please reboot, update or reinstall latest dotnet framework and the reboot again and see if that helps. You can also edit out the script where it hides the console and then it will show everything it is doing in the console window which should help. What error message do you get and scan you provide a screenshot?

Closing due to lack of response.

authors: SteemerSon arcadesdude

repo: arcadesdude/BRU

license: MIT


text:
🛑 ARCaptcha is down

In de2a24b, ARCaptcha (https://arcaptcha.ir) was down:

HTTP code: 502
Response time: 486 ms

Resolved: ARCaptcha is back up in bff0994.

repo: arcaptcha/ARCaptcha-monitoring


text:
Seed with nwidart.com/laravel-modules each tenant

Hi,
I'm using your fantastic package to develop a SAAS app. I'm using https://nwidart.com/laravel-modules/ and would like to seed every module foreach tenants. How can I do ?
Seeders are in each Modules/module_name/ Seeds/MySeed.php so how can I configure from your module ?
Thanks again
Regards

Hi,
I've never used that package and I unfortunately don't have the time to look into it now, so I can't really help.
I'll keep this open though, if someone has done this.

I think i have found a solution about this - tenant_route('home', [], $domain); its working perfect

Hi,
@laracodedeveloper do you have a more precise example ? Do you tell me that you redirect the route to do the seed ?

I think they're just confused and meant to answer in this thread https://github.com/stancl/tenancy/issues/325

Thanks stancl maybe we can override the seed to it in different namespaces ? Is there a way to do it ? Maybe a loop for each tenant and a seed by changing the database connection ?

Again, I have no clue and I don't have the time to focus on this right now. I suggest looking into the source code of this package and that module package.

@t-prod I'm interested why is this an issue? I haven't used both packages a lot but I think you can call your modules seeders from a master seeder just like you normally do

Hi,
When you are developing Modules with Nwidart you have the ability to seed in Modules/Database/Seeders. If you have the tenancy package is useless cause the tenant database is unknown ;) Indeed the solution it's to centralize all the seeders in the classical way database\seeds\DatabaseSeeder.php

I would like it will be in each Module for a better organization ;)

I would like it will be in each Module for a better organization

Why not call each module's seeder from the central seeder? How is that bad organization?

If you have a lot of Modules you will have to comment Seeder for each module is active or not.
It's same thing for migrations. Maybe I'm wrong but it would be easier not to centralize all of them.
For instance, if you want to migrate and seed one module.

I feel your frustration as I tend to spend hours structuring things myself but you may be overthinking it here.
This package has an artisan command tenants:run and a callback that you could use to run your own migration logic or use the built-in nWidart modules:seed  - if don't intend to publish your app so people can extend it you maybe you do not need the modules package at all ( here  is nice usage of nWidart package ) alternatively do it the laravel way and structure your app into modules where each module could have its own Providers, Migrations, Routes, Lang ect..
I recommend you watch this video as there's an interesting question at the end how to handle migrations and he suggests to provision all databases in advance which could make sense if your expecting alot of users or want to make sure everything is order.
I personally would create separate repositories and a core library that shares all the business logic ( Models, Repositories, Contracts.. ) for example a) Tenant app b) Tenant manager ( my own admin panel ) c) Marketing website / Logins / Registrations
There are many ways to do this, what I am trying to say is don't rely entirely on any package and those checks you mention you need to do them eventually - I think this package is flexible giving you the choice on how to do it.
To answer you question you can do both method centralize all migrations / seeders or keep it seperate.

If you have a lot of Modules you will have to comment Seeder for each module is active or not.
It's same thing for migrations. Maybe I'm wrong but it would be easier not to centralize all of them.
For instance, if you want to migrate and seed one module when you have more of 6.

I make a command to run migration and seeder for each modulo with this packages
Need {Module name}[are folder name into folder Modules] {tenand_id} and {--seed} flag to run seeder, I use the namespace to run using ath into migration and --class to run seeder

Thanks for sharing, we have the same problem and your solution looks great ;)

@yashiroiori thanks for your solution i will try that because i want to use nwidart/laravel-modules with this package i was also wondering how it will work with the migrations and seeders.
but this means i can no longer use the automatic migration config after creating a tenant right?.
@t-prod thanks for opening the issue i was about to ask the same thing too.

You can dynamically set tenancy.migration_parameters.
https://github.com/stancl/tenancy/blob/2.x/assets/config.php#L103
'--path' => [
    'path1',
    'path2',
],

should work

@stancl oh wow nice!!,
so basically that will solve the problem with nwidart/laravel-modules by simple configuring stancl/tenancy and tell it where the migrations are located for each module still need to try that.
thanks.

isDot()) continue;

            if ($file->isDir() && !$file->isDot()) {
                $directories[] = $path . DIRECTORY_SEPARATOR . $file->getFilename() . DIRECTORY_SEPARATOR . config('modules.paths.generator.migration.path');
            }

        }

        return $directories;
    }
}

tenancy.php
    'migration_parameters' => [
        '--force'    => TRUE, // This needs to be true to run migrations in production.
        '--path'     => modules_directoires_migration(),
        '--realpath' => TRUE,
    ],

Migrate and Seed Laravel Modules (nwidart)
Not sure if anyone else could use this but here is a solution that handles the migration and seeding of modules from within the JobPipeline.
Modify the location of module migration files.

To prevent the module's migrations from being run on the main (central) database, modify the config/modules.php file by adding 'tenant' to the path as in the example below.

        /*
        |--------------------------------------------------------------------------
        | Generator path
        |--------------------------------------------------------------------------
        | Customise the paths where the folders will be generated.
        | Set the generate key to false to not generate that folder
        */
        'generator' => [
           // ...
            'migration' => ['path' => 'Database/Migrations/tenant', 'generate' => true], // modify this line
          // ...
        ]

Move module migration files to the Modules/{ModuleName}/Database/Migrations/tenant folder.

Set the module migration path(s)

Using the earlier (thread) suggestion add the following to your helpers file

if (!function_exists('modules_directories_migration')) {
    /**
     * set modal info
     *
     * set the title, message, and any fields for the modal
     *
     */
    function modules_directories_migration(): array
    {
        $path        = base_path('Modules');
        $directories = [];
        foreach (new \DirectoryIterator($path) as $file) {
            if ($file->isDot()) continue;

            if ($file->isDir() && !$file->isDot()) {
                $directories[] = $path . DIRECTORY_SEPARATOR . $file->getFilename() . DIRECTORY_SEPARATOR . config('modules.paths.generator.migration.path');
            }

        }

        return $directories;
    }

}

Migrate and Seed as part of the Tenant creation process

Create two new Jobs MigrateModules and SeedModules, I will attach examples below.
Add the Jobs to the JobPipeline (TenancyServiceProvider::events)

use App\Jobs\MigrateModules;
use App\Jobs\SeedModules;

 JobPipeline::make([
                    Jobs\CreateDatabase::class,
                    Jobs\MigrateDatabase::class,
                    MigrateModules::class, // NEW JOB
                    SeedModules::class, // NEW JOB
                    // ...
             ]);

App/Jobs/SeedModules.php

namespace App\Jobs;

use Illuminate\Bus\Queueable;
use Illuminate\Queue\SerializesModels;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Support\Facades\Artisan;
use Illuminate\Support\Facades\Config;
use Stancl\Tenancy\Contracts\TenantWithDatabase;

class SeedModules implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    /** @var TenantWithDatabase */
    protected TenantWithDatabase $tenant;

    public function __construct(TenantWithDatabase $tenant)
    {
        $this->tenant = $tenant;
    }

    /**
     * Execute the job.
     *
     * @return void
     */
    public function handle()
    {

        $modules = \Nwidart\Modules\Facades\Module::toCollection();

        foreach( $modules as $module ){

            $path =  $module->getExtraPath('Seeders');
            $className = $path.'\\'.$module->getStudlyName().'DatabaseSeeder';
            $className = str_replace(base_path(),'', $className);
            $className = str_replace('/','\\', $className);

            $params =   [
                '--class' => $className,
                '--force' => true,
            ];

            Config::set('tenancy.seeder_parameters', $params );
            Artisan::call('tenants:seed', [
                '--tenants' => [$this->tenant->getTenantKey()],
            ]);

        }

    }
}

App/Jobs/MigrateModules.php
<?php

namespace App\Jobs;

use Illuminate\Bus\Queueable;
use Illuminate\Queue\SerializesModels;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Support\Facades\Artisan;
use Illuminate\Support\Facades\Config;
use Stancl\Tenancy\Contracts\TenantWithDatabase;

class MigrateModules implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    /** @var TenantWithDatabase */
    protected TenantWithDatabase $tenant;

    public function __construct(TenantWithDatabase $tenant)
    {
        $this->tenant = $tenant;
    }

    /**
     * Execute the job.
     *
     * @return void
     */
    public function handle()
    {
        $params =  [
            '--force'    => TRUE, // This needs to be true to run migrations in production.
            '--path'     => modules_directories_migration(),
            '--realpath' => TRUE,
        ];

        Config::set('tenancy.migration_parameters', $params );

        Artisan::call('tenants:migrate', [
            '--tenants' => [$this->tenant->getTenantKey()],
        ]);

    }
}

Migrate and Seed Laravel Modules (nwidart)
Not sure if anyone else could use this but here is a solution that handles the migration and seeding of modules from within the JobPipeline.
Modify the location of module migration files.

To prevent the module's migrations from being run on the main (central) database, modify the config/modules.php file by adding 'tenant' to the path as in the example below.

        /*
        |--------------------------------------------------------------------------
        | Generator path
        |--------------------------------------------------------------------------
        | Customise the paths where the folders will be generated.
        | Set the generate key to false to not generate that folder
        */
        'generator' => [
           // ...
            'migration' => ['path' => 'Database/Migrations/tenant', 'generate' => true], // modify this line
          // ...
        ]

Move module migration files to the Modules/{ModuleName}/Database/Migrations/tenant folder.

Set the module migration path(s)

Using the earlier (thread) suggestion add the following to your helpers file

if (!function_exists('modules_directories_migration')) {
    /**
     * set modal info
     *
     * set the title, message, and any fields for the modal
     *
     */
    function modules_directories_migration(): array
    {
        $path        = base_path('Modules');
        $directories = [];
        foreach (new \DirectoryIterator($path) as $file) {
            if ($file->isDot()) continue;

            if ($file->isDir() && !$file->isDot()) {
                $directories[] = $path . DIRECTORY_SEPARATOR . $file->getFilename() . DIRECTORY_SEPARATOR . config('modules.paths.generator.migration.path');
            }

        }

        return $directories;
    }

}

Migrate and Seed as part of the Tenant creation process

Create two new Jobs MigrateModules and SeedModules, I will attach examples below.
Add the Jobs to the JobPipeline (TenancyServiceProvider::events)

use App\Jobs\MigrateModules;
use App\Jobs\SeedModules;

 JobPipeline::make([
                    Jobs\CreateDatabase::class,
                    Jobs\MigrateDatabase::class,
                    MigrateModules::class, // NEW JOB
                    SeedModules::class, // NEW JOB
                    // ...
             ]);

App/Jobs/SeedModules.php
namespace App\Jobs;

use Illuminate\Bus\Queueable;
use Illuminate\Queue\SerializesModels;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Support\Facades\Artisan;
use Illuminate\Support\Facades\Config;
use Stancl\Tenancy\Contracts\TenantWithDatabase;

class SeedModules implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    /** @var TenantWithDatabase */
    protected TenantWithDatabase $tenant;

    public function __construct(TenantWithDatabase $tenant)
    {
        $this->tenant = $tenant;
    }

    /**
     * Execute the job.
     *
     * @return void
     */
    public function handle()
    {

        $modules = \Nwidart\Modules\Facades\Module::toCollection();

        foreach( $modules as $module ){

            $path =  $module->getExtraPath('Database/Seeders');
            $className = $path.'\\'.$module->getStudlyName().'DatabaseSeeder';
            $className = str_replace(base_path(),'', $className);
            $className = str_replace('/','\\', $className);

            $params =   [
                '--class' => $className,
                '--force' => true,
            ];

            Config::set('tenancy.seeder_parameters', $params );
            Artisan::call('tenants:seed', [
                '--tenants' => [$this->tenant->getTenantKey()],
            ]);

        }

    }
}

App/Jobs/MigrateModules.php
<?php

namespace App\Jobs;

use Illuminate\Bus\Queueable;
use Illuminate\Queue\SerializesModels;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Support\Facades\Artisan;
use Illuminate\Support\Facades\Config;
use Stancl\Tenancy\Contracts\TenantWithDatabase;

class MigrateModules implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    /** @var TenantWithDatabase */
    protected TenantWithDatabase $tenant;

    public function __construct(TenantWithDatabase $tenant)
    {
        $this->tenant = $tenant;
    }

    /**
     * Execute the job.
     *
     * @return void
     */
    public function handle()
    {
        $params =  [
            '--force'    => TRUE, // This needs to be true to run migrations in production.
            '--path'     => modules_directories_migration(),
            '--realpath' => TRUE,
        ];

        Config::set('tenancy.migration_parameters', $params );

        Artisan::call('tenants:migrate', [
            '--tenants' => [$this->tenant->getTenantKey()],
        ]);

    }
}

Excelente let me try 👍

authors: NerdSnipe laracodedeveloper lucassmacedo rajakhoury stancl t-prod thamibn yashiroiori

repo: archtechx/tenancy


text:
PyTorch 内部机制(翻译) - ArchWalker

https://archwalker.github.io/blog/2019/05/27/pytorch-internals.html
PyTorch internals转载请务必保留出处  译者序：这篇博文是一篇非常新的介绍PyTorch内部机制的文章，作者Edward Z Yang来自于Stanford大学，是PyTorch的核心开发者之一。文章中介绍了如何阅读PyTorch源码和扩展PyTorch的技巧。目前讲PyTorch底层的文章不多，...

good！

authors: Lilhxr archwalker


text:
打包构建完成后，本地使用live-server启动时，刷新后页面404

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version: arco-design-pro-vue@2.3.6
Browser: chrome101.0.4951.54
Reproduction Link: https://github.com/

What is expected?
在浏览器刷新页面，不出现404
Steps to reproduce
1、使用arco-cli创建一个arco项目
2、运行npm run build打包
3、cd dist && live-server ./ --port=$port
4、登录后进入dashboard页面，刷新浏览器

@Paradox315 这个不是pro的问题哈。看一下live-server的文档。需要配置重定向到index.html。

repo: arco-design/arco-design-pro-vue


text:
select允许搜索的情况下，输入框空值时如何能不显示下拉框

[x] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version: @arco-design/web-vue@2.55.3
Browser: chrome126.0.0.0

Steps to reproduce
popup-visible (v-model)无效

输入框为空值时，代表搜索条件为空，正常的交互应该是展示所有的选项，所以会弹出下拉框。
另外，popup-visible 好像是生效的：https://codesandbox.io/p/sandbox/sad-https-wvx286?file=%2Fsrc%2FApp.vue

authors: baisuMr rtpacks

repo: arco-design/arco-design-vue


text:
Port for Midnight Commander

I've made a Nord skin for Midnight Commander. Please include it in your repository.
https://gist.github.com/laulicus/0ea52d87b529ad712794e8b5cd73b3cb

For using skin, it needs to copied to: ~/.local/share/mc/skins/nord16M.ini or /usr/share/mc/skins/nord16M.ini

Thanks @laulicus!

I pasted the gist content to the config file ~/.local/share/mc/skins/nord16M.ini , told mc to switch to this theme, then hit F4 (I believe it launches mcedit) and got the situation in the attached image below.
These seem to be the same highlight colors as in the default mc theme.
Is the theme incomplete (does not handle what's happening in mcedit)? Or is additional configuration required?
For the record, I am using mc from Slackware64-15.0:
$ mc -V
GNU Midnight Commander 4.8.27
Built with GLib 2.68.3
Built with S-Lang 2.3.2 with terminfo database
With builtin Editor and Aspell support
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
With ext2fs attributes support
Virtual File Systems:
 cpiofs, tarfs, sfs, extfs, ftpfs, sftpfs, fish, smbfs
Data types:
 char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;

authors: laulicus paulmiddelkoop toolonely

repo: arcticicestudio/nord


text:
Add example of multiple database contexts

Would it be worth adding examples of multiple database context to align with DDD principles like bounded contexts and see how multiple contexts are implemented even if they use the same physical persistence store?

Thanks for the suggestion! Typically I prefer to use different solutions for different bounded contexts if possible but you certainly can support multiple within a solution. This is meant to be a solution template, not a full sample application, though, so in the interest of simplicity I don't think I will add multiple DbContexts. You can see an example of a similar architecture that does have that here though:
https://github.com/dotnet-architecture/eShopOnWeb

authors: ardalis lankymart

repo: ardalis/CleanArchitecture


text:
Update repositories.txt

Please add this lib to Arduino, thank you 💯

@ArduinoBot The requested change is now there

Hello @RobertByrnes. The automated system here only operates on open pull requests. Since your submission was already accepted and the pull request merged, the bot won't pay any more attention to this pull request.
But this human is happy to provide assistance. Was there something you needed from the bot?

repo: arduino/library-registry


text:
doesn't build with android studio 2023.2.1

i try to build it and i get the error:
Unable to find method ''org.gradle.api.file.DirectoryProperty org.gradle.api.file.ProjectLayout.directoryProperty(org.gradle.api.provider.Provider)''
'org.gradle.api.file.DirectoryProperty org.gradle.api.file.ProjectLayout.directoryProperty(org.gradle.api.provider.Provider)'
Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)
Re-download dependencies and sync project (requires network)
The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem.
Stop Gradle build processes (requires restart)
Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project.
In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes.

@salah-eddine-gasmi
In gradle-wrapper.properties I set
distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-bin.zip
In build.gradle Project change
 dependencies {         classpath 'com.android.tools.build:gradle:7.4.2'

authors: salah-eddine-gasmi vovanb

repo: arekolek/simple-phone


text:
ADBDEV-4902-1: Move for_each_cell under the null check

Move for_each_cell under the null check
This block of code is executed when ALTER TABLE ADD PARTITION is issued in a
query. The first element of the list will be the parent table of that partition,
and next elements will be the CREATE/ALTER TABLE queries for partitions.
If this list does not have any statements other than the first one, or lc is
NULL (there is no statements to CREATE/ALTER partitions), further logic is
useless, since statements are needed to correctly process utility statements for
the partitions.

Allure report https://allure-ee.adsw.io/launch/63103

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1025300

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1025301

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1025298

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1025294

Allure report https://allure-ee.adsw.io/launch/63127

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1026822

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1026823

Allure report https://allure-ee.adsw.io/launch/63187

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1028969

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1028970

Allure report https://allure-ee.adsw.io/launch/63396

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1038096

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1038097

authors: BenderArenadata bandetto

repo: arenadata/gpdb


text:
2022 Q2 Roadmap

Version: 0.5

[ ] Instrumentation: jedis2
[ ] Instrumentation: redission
[ ] Instrumentation: lettuce
[ ] Instrumentation: okhttp 2/3
[ ] Instrumentation: dynamic type
[ ] Instrumentation: gRPC (low priority)
[ ] Instrumentation: Servlet5
[ ] Instrumentation: Time machine (low priority)
[ ] Framework: Ignore
[ ] CLI： Config

[ ] Instrumentation: jedis2
[ ] Framework: Ignore

[ ] Instrumentation: Servlet5
[ ] Instrumentation: lettuce

Because of the lower version, okhttp2 support is abandoned.
Grpc adjusted to Q3

repo: arextest/arex-agent-java


text:
What is the format of the submission for 3D object detection competition?

The Submission Guidelines have nothing about the submission format, could you give more details? Or could you provide a submission sample?
Thank you very much!

@benjaminrwilson Thank you very much!

Thank you @benjaminrwilson , the evalai client returns an error Error: {'detail': 'Given token not valid for any token type', 'code': 'token_not_valid', 'messages': [{'token_class': 'RefreshToken', 'token_type': 'refresh', 'message': 'Token is invalid or expired'}]}
while submitting the feather file.


text:
fix: allow the specific image platform os/arch/variant to meet the requirement for a broader image platform os/arch

Fixes https://github.com/argoproj-labs/argocd-image-updater/issues/711

change WantsPlatform() method to allow match of broader platform
add unit tests for the above change
improve logs to include platform variant so it's clear why certain match is false
this fix causes some change of behavior in comparing options platforms vs platforms of available images, as shown in the changes to pkg/image/options_test.go

Codecov Report
Attention: Patch coverage is 71.42857% with 4 lines in your changes missing coverage. Please review.

Project coverage is 73.48%. Comparing base (40f260a) to head (2e4b9c0).

Files with missing lines
Patch %
Lines

pkg/registry/client.go
50.00%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #858      +/-   ##
==========================================
+ Coverage   73.43%   73.48%   +0.05%
==========================================
  Files          31       31
  Lines        3136     3142       +6
==========================================
+ Hits         2303     2309       +6
  Misses        695      695
  Partials      138      138

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

authors: chengfang codecov-commenter

repo: argoproj-labs/argocd-image-updater


text:
Allow "dag" to accept dynamic task listing

Summary
DAG steps should be able to accept a list of steps from an artifact, something like this:
metadata:
  name: test-dynamic
  namespace: default
spec:
  entrypoint: run-graph
  templates:
    - name: run-graph
      steps:
        - - name: generate-graph
            template: generate-graph
        - - name: execute-graph
            template: execute-graph
            arguments:
              parameters:
                - name: dag
                  value: "{{steps.generate-graph.outputs.dag}}"
    - name: generate-graph
      script:
        image: ubuntu:22.04
        command: [bash]
        source: |
          cat >/tmp/output.json <<EOF
          [
            [{
              "name": "A",
              "dependencies": [],
              "template": "node"
            }],
            [{
              "name": "B",
              "dependencies": ["A"],
              "template": "node"
            }],
            [{
              "name": "C",
              "dependencies": ["A"],
              "template": "node"
            }],
            [{
              "name": "D",
              "dependencies": ["B", "C"],
              "template": "node"
            }]
          ]
          EOF
      outputs:
        parameters:
          - name: dag
            valueFrom:
              path: /tmp/output.json
    - name: execute-graph
      inputs:
        parameters:
          - name: dag
      dag:
        tasksFrom:
          artifact: dag
    - name: node
      container:
        image: alpine:latest
        command: [sh, -c]
        args: ["sleep 1"]
  ttlStrategy:
    secondsAfterCompletion: 300
  podGC:
    strategy: OnPodCompletion

Use Cases
Right now the only way to dynamically generate DAGs is to use the "Workflow from Workflow" pattern. But the problem is that the spawned workflow appears separately in the Argo UI; it isn't connected to the main workflow that spawned it. So as a user I end up having to click through to a different workflow once I know the generated one has been started (and that's the one I actually care about).

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

https://argoproj.github.io/argo-workflows/walk-through/loops/ ?

That doesn't let you specify dependencies of the entries; it's just horizontal parallelisation, not a graph like the DAG node.

Hi have you found any workaround around this?
We have a similar requirement

repo: argoproj/argo-workflows


text:
Display title and description annotations on workflow archive view

Summary
In workflow archive view, display title and description if annotations exist
Related to #9805 which handles this for the main workflow view
Since we're already allowing it for the main workflow list, we should support it in the archive view also to give a consistent user experience IMO.
Use Cases
When viewing the archive list, I'd want to see the titles/descriptions just like I would on the main workflow list

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

I'm working on this already and will push PR up shortly.

Will be moot due to #11121

Thank you for working on it!

authors: jmeridth terrytangyuan


text:
Server OOM when too many executions of CronWorkflows or WorkflowTemplates

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issue exists when I tested with :latest
[X] I have searched existing issues and could not find a match for this bug
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what did you expect to happen?
This occurs when trying to view the details of each cron-workflows or workflow-template UI, which has a lot of history.
There was nothing like that in the argo-server logs.

Version
v3.5.4
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Any workflow is acceptable.

Logs from the workflow controller
workflow-controller does not seem to be involved.
Found 2 pods, using pod/workflow-controller-7bbd96c558-qss82
time="2024-02-09T09:40:00.290Z" level=info msg="Processing workflow" Phase= ResourceVersion=646930323 namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:00.691Z" level=info msg="Task-result reconciliation" namespace=develop-workflow numObjs=0 workflow=**********-1707471600
time="2024-02-09T09:40:00.790Z" level=info msg="Updated phase  -> Running" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:01.690Z" level=info msg="Created PDB resource for workflow." namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:01.690Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:01.691Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:02.290Z" level=info msg="Pod node **********-1707471600 initialized Pending" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:02.392Z" level=info msg="Created pod: **********-1707471600 (**********-1707471600)" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:02.392Z" level=info msg="TaskSet Reconciliation" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:02.392Z" level=info msg=reconcileAgentPod namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:02.691Z" level=info msg="Workflow update successful" namespace=develop-workflow phase=Running resourceVersion=646930400 workflow=**********-1707471600
time="2024-02-09T09:40:12.691Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=646930400 namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.693Z" level=info msg="Task-result reconciliation" namespace=develop-workflow numObjs=0 workflow=**********-1707471600
time="2024-02-09T09:40:12.693Z" level=warning msg="workflow uses legacy/insecure pod patch, see https://argo-workflows.readthedocs.io/en/release-3.5/workflow-rbac/" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.693Z" level=warning msg="workflow uses legacy/insecure pod patch, see https://argo-workflows.readthedocs.io/en/release-3.5/workflow-rbac/" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.694Z" level=info msg="node changed" namespace=develop-workflow new.message= new.phase=Succeeded new.progress=0/1 nodeID=**********-1707471600 old.message= old.phase=Pending old.progress=0/1 workflow=**********-1707471600
time="2024-02-09T09:40:12.694Z" level=info msg="TaskSet Reconciliation" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.695Z" level=info msg=reconcileAgentPod namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.695Z" level=info msg="Running OnExit handler: exit-handler" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.695Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.700Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.700Z" level=info msg="Steps node **********-1707471600-3586666638 initialized Running" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.700Z" level=info msg="StepGroup node **********-1707471600-4104114448 initialized Running" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.700Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.700Z" level=info msg="Steps node **********-1707471600-626938768 initialized Running" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.700Z" level=info msg="StepGroup node **********-1707471600-1958917994 initialized Running" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.701Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.701Z" level=info msg="Pod node **********-1707471600-3566325063 initialized Pending" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.809Z" level=info msg="Created pod: **********-1707471600.onExit[0].datadog-metrics[0].exit-status-count (**********-1707471600-datadog-3566325063)" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.809Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.890Z" level=info msg="Pod node **********-1707471600-1538370245 initialized Pending" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.991Z" level=info msg="Created pod: **********-1707471600.onExit[0].datadog-metrics[0].exit-duration-gauge (**********-1707471600-datadog-1538370245)" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.991Z" level=info msg="Workflow step group node **********-1707471600-1958917994 not yet completed" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:12.991Z" level=info msg="Skipping **********-1707471600.onExit[0].slack-notification: when 'false == true' evaluated false" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:13.189Z" level=info msg="Skipped node **********-1707471600-103546606 initialized Skipped (message: when 'false == true' evaluated false)" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:13.190Z" level=info msg="Workflow step group node **********-1707471600-4104114448 not yet completed" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:13.290Z" level=info msg="Workflow update successful" namespace=develop-workflow phase=Running resourceVersion=646930801 workflow=**********-1707471600
time="2024-02-09T09:40:18.490Z" level=info msg="cleaning up pod" action=deletePod key=develop-workflow/**********-1707471600/deletePod
time="2024-02-09T09:40:22.893Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=646930801 namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=info msg="Task-result reconciliation" namespace=develop-workflow numObjs=0 workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=warning msg="workflow uses legacy/insecure pod patch, see https://argo-workflows.readthedocs.io/en/release-3.5/workflow-rbac/" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=warning msg="workflow uses legacy/insecure pod patch, see https://argo-workflows.readthedocs.io/en/release-3.5/workflow-rbac/" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=info msg="node changed" namespace=develop-workflow new.message= new.phase=Succeeded new.progress=0/1 nodeID=**********-1707471600-1538370245 old.message= old.phase=Pending old.progress=0/1 workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=warning msg="workflow uses legacy/insecure pod patch, see https://argo-workflows.readthedocs.io/en/release-3.5/workflow-rbac/" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=warning msg="workflow uses legacy/insecure pod patch, see https://argo-workflows.readthedocs.io/en/release-3.5/workflow-rbac/" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=info msg="node changed" namespace=develop-workflow new.message= new.phase=Succeeded new.progress=0/1 nodeID=**********-1707471600-3566325063 old.message= old.phase=Pending old.progress=0/1 workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=info msg="TaskSet Reconciliation" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=info msg=reconcileAgentPod namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.895Z" level=info msg="Running OnExit handler: exit-handler" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Step group node **********-1707471600-1958917994 successful" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-1958917994 phase Running -> Succeeded" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-1958917994 finished: 2024-02-09 09:40:22.990379721 +0000 UTC" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Outbound nodes of **********-1707471600-3566325063 is [**********-1707471600-3566325063]" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Outbound nodes of **********-1707471600-1538370245 is [**********-1707471600-1538370245]" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Outbound nodes of **********-1707471600-626938768 is [**********-1707471600-3566325063 **********-1707471600-1538370245]" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-626938768 phase Running -> Succeeded" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-626938768 finished: 2024-02-09 09:40:22.990488334 +0000 UTC" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Step group node **********-1707471600-4104114448 successful" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-4104114448 phase Running -> Succeeded" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-4104114448 finished: 2024-02-09 09:40:22.990680607 +0000 UTC" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Outbound nodes of **********-1707471600-626938768 is [**********-1707471600-3566325063 **********-1707471600-1538370245]" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Outbound nodes of **********-1707471600-103546606 is [**********-1707471600-103546606]" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Outbound nodes of **********-1707471600-3586666638 is [**********-1707471600-3566325063 **********-1707471600-1538370245 **********-1707471600-103546606]" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-3586666638 phase Running -> Succeeded" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="node **********-1707471600-3586666638 finished: 2024-02-09 09:40:22.99083864 +0000 UTC" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.990Z" level=info msg="Updated phase Running -> Succeeded" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:22.991Z" level=info msg="Marking workflow completed" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:23.002Z" level=info msg="Deleted PDB resource for workflow." namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:23.002Z" level=info msg="Marking workflow as pending archiving" namespace=develop-workflow workflow=**********-1707471600
time="2024-02-09T09:40:23.008Z" level=info msg="cleaning up pod" action=deletePod key=develop-workflow/**********-1707471600-1340600742-agent/deletePod
time="2024-02-09T09:40:23.092Z" level=info msg="Workflow update successful" namespace=develop-workflow phase=Succeeded resourceVersion=646931206 workflow=**********-1707471600
time="2024-02-09T09:40:23.190Z" level=info msg="archiving workflow" namespace=develop-workflow uid=809ee2c5-797d-42d9-a287-5a65ac412d3f workflow=**********-1707471600
time="2024-02-09T09:40:23.325Z" level=info msg="Queueing Succeeded workflow develop-workflow/**********-1707471600 for delete in 2m59s due to TTL"
time="2024-02-09T09:40:28.190Z" level=info msg="cleaning up pod" action=deletePod key=develop-workflow/**********-1707471600-datadog-3566325063/deletePod
time="2024-02-09T09:40:28.190Z" level=info msg="cleaning up pod" action=deletePod key=develop-workflow/**********-1707471600-datadog-1538370245/deletePod
time="2024-02-09T09:43:23.000Z" level=info msg="Deleting garbage collected workflow 'develop-workflow/**********-1707471600'"
time="2024-02-09T09:43:23.009Z" level=info msg="Successfully request 'develop-workflow/**********-1707471600' to be deleted"

Logs from in your workflow's wait container
workflow-controller does not seem to be involved.
No resources found in argo namespace.

view the details of each cron-workflows

You mean the history view in the CronWorkflow Details page that was added in #11811, right?
I think for that we can just set a hard limit of say, the most recent 20 executions of the CronWorkflow.
For pagination for the CronWorkflow List page, there is #10846

or workflow-template UI

The WorkflowTemplate Details page does not currently have a history of executions -- can you elaborate on what you were referring to here? Pagination for the WorkflowTemplate List page?

Thanks for confirming.

I think for that we can just set a hard limit of say, the most recent 20 executions of the CronWorkflow.

How can this be accomplished?

The WorkflowTemplate Details page does not currently have a history of executions -- can you elaborate on what you were referring to here? Pagination for the WorkflowTemplate List page?

The perception was wrong.
WorkflowTemplate didn't have a list, so forget it.

How can this be accomplished?

We'd just need to add a limit in the pagination args of the request. As in, this line would need modification: https://github.com/argoproj/argo-workflows/blob/33c51ed17250d2a7b66bfd02badbd012ee33dfb3/ui/src/app/cron-workflows/components/cron-workflow-details/cron-workflow-details.tsx#L74
Would you like to work on that?

Can archived workflows be included?

In 3.5.x I believe they should be included by default since it has the unified API/UI.
3.5.0 had a regression that retrieved all archived workflows during deduplication (see #12025), but that was reverted in 3.5.1. I think the current issue is that the deduplication can be off (see #11715) and it can overfetch, but only to a max of limit * 2 (the same limit applies to both live and archived workflows).

Thank you, I would love to work on it, can you assign me to it?

You don't need to be assigned to work on something, can just submit a PR.


text:
fix: Enable the workflow created by a wftmpl to retry after manually stopped

…ally after manually stopped

No, I just met a problem in my work, but I made no issue but fix it myself because of time constraints
Motivation
Most of the users I am responsible for use workflow-templates to create workflows. However, there is a problem that has been bothering us: after the workflows created through the workflow templates are manually stopped, when retrying the failed node (because of the Stop operation) and all subsequent nodes will be skipped. Here is an example:
After manually stopped:

Ater manually retried:

Modifications

After carefully reading the relevant code, we finally realized that in the FormulaRetryWorkflow function, newWF.Status.StoredWorkflowSpec.Shutdown should be set to an empty string instead of keeping the shutdown information.

Verification

The following is a sample workflow template file：
metadata:
  name: clf-test-retry
  namespace: argo
spec:
  templates:
    - name: echo
      inputs:
        parameters:
          - name: message
      outputs: {}
      metadata: {}
      container:
        name: ''
        image: alpine:3.7
        command:
          - sleep
          - 1000s
        resources: {}
    - name: diamond
      inputs: {}
      outputs: {}
      metadata: {}
      dag:
        tasks:
          - name: A
            template: echo
            arguments:
              parameters:
                - name: message
                  value: A
          - name: B
            template: echo
            arguments:
              parameters:
                - name: message
                  value: B
            dependencies:
              - A
          - name: C
            template: echo
            arguments:
              parameters:
                - name: message
                  value: C
            dependencies:
              - A
          - name: D
            template: echo
            arguments:
              parameters:
                - name: message
                  value: D
            dependencies:
              - B
              - C
  entrypoint: diamond
  arguments: {}

You can just stop and retry the workflow when node A is running and the images in the Motivation can be reproduced.
After our fix, the workflow after retrying is as follows:

Signed-off-by: tongkangheng.tkh tongkangheng.tkh@bytedance.com

Tests are failing

Tests are failing

Thanks. Could you sign your commits?

I have done this

Thanks. Please fix test failures.

authors: TongKangheng terrytangyuan


text:
fix: remove JSON cast when querying archived workflows

Motivation
With PostgreSQL, the argo_archived_workflows.workflow column has been of type json ever since 8a1e611a03da8374567c9654f8baf29b66c83c6e, which was released as v2.5.0. Therefore, the ::json casts do nothing, and prevent users from improving performance by migrating to JSONB using the following query:
alter table argo_archived_workflows alter column workflow set data type jsonb using workflow::jsonb

Without the changes in this PR, running the above will massively slow down the queries, because casting JSONB to JSON is expensive. With the changes, I'm measuring a ~80% performance boost (see below). Other users have reported similar improvements.
The only downside to migrating to JSONB is it can take a long time if you've got a ton of workflows (~72s on my local DB with 100,000 workflows). I entered https://github.com/argoproj/argo-workflows/pull/13779 with the migration, but I'm entering this separately so it can hopefully go out in 3.6.0. That way, we can tell users to run the above query if they run into performance issues, without having to do a patch release with the migration.
Modifications
Replace (workflow::json) with just workflow
Verification
See https://github.com/argoproj/argo-workflows/pull/13779

Here's the PR for the migration, which builds on top of this PR: https://github.com/argoproj/argo-workflows/pull/13779

@jiachengxu Would you mind reviewing this?

@terrytangyuan Jiacheng is also apparently not in the "members" team a la https://github.com/argoproj/argo-workflows/issues/8790#issuecomment-2412016304, so that seems to be why we can't directly "request a review" via GH

Added @jiachengxu to members

Thanks Terry 👍

authors: MasonM agilgur5 terrytangyuan


text:
DOCKER_BUILD_OPTS does not work as intended

https://github.com/argoproj/argo/blob/af9f61ea7ce53f629a284a44f0106b9ed73f24e2/Makefile#L16
When running make build in a release branch, --no-cache is not added for some reason.

I can tell you why DOCKER_BUILDS_OPTS != DOCKER_BUILD_OPTS (extra "S").

make --warn-undefined-variables does not actually help.

That seems to be the error on the file as well

AFAIK, you cannot fail a Makefile, best you can do:
alias make=make --warn-undefined-variables

Just a thought. Instead of fixing, in the make clean target can you bust the Docker cache?

repo: argoproj/argo


text:
Workflow Open API validation

Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
Do you have plans to support validation of the Argo workflow spec?
It should be added here:
https://github.com/argoproj/argo/blob/06c0d324bf93a037010186fe54e40590ea39d92c/install/manifests/01_workflow-crd.yaml
Here is the documentation:
https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/
Here is a sample:
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: crontabs.stable.example.com
spec:
group: stable.example.com
version: v1
scope: Namespaced
names:
plural: crontabs
singular: crontab
kind: CronTab
shortNames:
- ct
validation:
openAPIV3Schema is the schema for validating custom objects.
openAPIV3Schema:
  properties:
    spec:
      properties:
        cronSpec:
          type: string
          pattern: '^(\d+|\*)(/\d+)?(\s+(\d+|\*)(/\d+)?){4}$'
        replicas:
          type: integer
          minimum: 1
          maximum: 10

Yes, I agree with this. I even went so far as to generate an open-api schema for exactly this purpose:
https://github.com/argoproj/argo/blob/master/api/openapi-spec/swagger.json
The main motivation for having validating schema is to avoid problems like this:
https://github.com/argoproj/argo/issues/632
That said, adding the OpenAPI validation schema to the CRD needs to be optional because once you define the schema, you may have trouble running multiple controllers at different argo versions -- which will cause problems when bundling the argo workflow controller as part of a higher level application.
Also, the internal struct representation of Item object, will be changing in the near future to support protobuf encoding. So we will want to wait for this to come in:
https://github.com/argoproj/argo/issues/853

Sounds good. It makes sense to have this optional.

Do we have any ETA for this enhancement? I filed https://github.com/argoproj/argo-events/issues/281 for the same reasons and I suspect that it impacts all the CRDs used by Argo - Worflows, Events, CD.
I did see that Rollouts has the validation in there

Re: Making it optional, it looks like that won't be possible if/when the CRDs update from apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1. I'm not sure if it's feasible to keep using the beta API version forever (some version of k8s will drop support for it eventually? not sure)

@jessesuen Now that Argo 2.6 has an OpenAPI spec (https://github.com/argoproj/argo/blob/v2.6.1/api/openapi-spec/swagger.json#L2526-L2680), can we not use that to solve this issue and migrate to apiextensions.k8s.io/v1?

My use case is just Intellij linting. Validation wouldn't even have to be built into the CRD that gets installed. It would just have to exist in another file that can be imported to Intellij's Kubernetes plugin.

@jessesuen @mukulikak I'm gathering some notes. The lack of YAML validation is one of the key reason that people want to use a Python DSL. I think we should revisit this popular issue.

authors: alexec danxmoran jessesuen logicfox mac9416 stormmore vicaire


text:
generate JSON for figma-tokens plugin to use

for #21

@argyleink, feel free to suggest changes! (especially for the "other" group - figma-tokens recognizes only certain names for the top-level groupings in the JSON)
I kinda like having the token names the same as the CSS variables

and then once the .json file is deployed to unpkg, a designer can copy a link into the Sync tab (instead of manually copy-pasting all the contents of a JSON file)

rad work! def be sweet when this is just an unpkg url away!
i have an issue tho: i cant get my plugin to be as organized as yours!? tell me your secrets!
here's my URL (https://jsonbin.io/61d91d632362237a3a343e96) and then a preview of it syncing with the plugin

the JSON seems fine to me, looks like you followed their docs super well! this a user (me) error? the ux of this plugin is a bit.. tough in some ways. how did you get all your props to show up under the group "open-props"? is it because i'm using the url feature and not jsonbin?

the PR otherwise looks solid! colors look great in there 🙂

oh, i hadn't tried the Sync tab yet, i manually pasted into the JSON text box. turns out we need to wrap all the tokens in one more key where that lone top-level key could be "open-props", like where the "global" is in this example: https://raw.githubusercontent.com/six7/figma-tokens-example/main/tokens.json
commit forthcoming

boom https://unpkg.com/open-props/open-props.figma-tokens.sync.json

authors: argyleink hchiam

repo: argyleink/open-props


text:
add_chunwei_profile

adding chunwei profile

Looks good!

repo: aria-systems-group/website


text:
upgrade from Fallen Breath's Mod Template; add 1.21.2 branch under pre3

Pending changes for 1.21.2:

Upgrade multi-version preprocess build scripts to Fallen Breath's current Mod-Template
Added 1.21.2 branch and made porting changes.

Caveats:

src/main/java/io/github/eatmyvenom/litematicin/mixin/quasiEssentialClient/ClientPlayerEntityMixin.java --> the ClientMovement Packets have been removed for the "Vehicle" packet under 1.21.2.
Cleanup extra comments / Template code stuffs from Build Scripts.
I did not copy over Fallen's GitHub Actions; I wanted you to see if you wanted to.

Also:

Updated MixinExtras with a Version Variable in the Root Directory.
buildAndGather task, now requires the Environment Variable for BUILD_RELEASE=true or else you'll get -SNAPSHOT jar files.

Also, do you want me to add the LANG file support to the config ?  The methods have been upgraded under MaLiLib since 1.21 to better support LANG json files.

Bumped to 1.21.2 release builds

apparently now there is a 1.21.3 ...

Currently updating versions and adding 1.21.4


text:
🛑 borataktik is down

In 3e83e55, borataktik (https://www.borataktik.com) was down:

HTTP code: 503
Response time: 377 ms

Resolved: borataktik is back up in df379e8 after 11 minutes.

repo: aribatturan/hcdev


text:
🛑 kahve.com is down

In ec5204b, kahve.com (https://www.kahve.com) was down:

HTTP code: 404
Response time: 367 ms

Resolved: kahve.com is back up in 5e4d8bc after 21 minutes.


text:
can UTCDateTime be replaced with Instant?

(Spun off from #59)

Ah, so you are using UTCDateTime as a substitute for Instant

The whole discussion on whether to have Instant or not probably belongs in its own issue. The fact that most modern libraries have this, is a strong signal for its usefulness. Having both UTCDateTime and Instant would probably be unnecessary

I can see some value in UTCDateTime, because it captures an  intent of the developer, and it's more ergonomic than OffsetDateTime(offset=0).
Can UTCDateTime be replaced with an Instant class? The Instant class is a wrapper around an "epoch seconds". It provides type-safety and encapsulation. There should be an unambiguous 1-to-1 conversion between an Instant and UTCDateTime.
Here are some examples from other libraries:

java.time has an Instant class that wraps a long (seconds) and an int (nanoseconds)

"the class stores a long representing epoch-seconds and an int representing nanosecond-of-second,"

NodaTime implements an Instant class

(I don't know how to access its implementation source code)
it holds at least an Int64 as "milliseconds from UNIX epoch"

GoLang provides a Time struct

it wraps 3 values: a uint64, an int64, and a pointer to a Location (i.e. TimeZone) object
Go's Time class contains a Location object, which makes it different than the Instant class in java.time and NodaTime
Go does not have a DateTime class hierarchy. Everything is derived from the Time object

C++ has std::chrono::time_point which is implemented as a std::chrono::duration

I have no idea how it is actually implemented under the covers

I don't know, I can see both Instant and UTCDateTime being useful, because they capture slightly different things, and the ergonomics for the end-users are slightly different.

It occurs to me that theInstant class would replace the float type returned by the timestamp() function mentioned in #63 .

My thoughts after some time:
Instant and UTCDateTime are very similar. In the end, if you normalize to UTC, you might as well be dealing with a timestamp/integer: you're usually not interested in the nominal month, day, hour in UTC. You're more likely interested in comparison or adding/subtracting

An update to add here: In the rust extension I'm working on, UTCDateTime is Instant in almost everything but name.
Note that I'm still hanging on to the UTCDateTime name for these reasons:

The name UTCDateTime will be more familiar to most users than Instant
a UTC datetime is more human-friendly representation of an instant in time than an opaque integer class
For some contexts such as airline or militairy, UTC datetime is a meaningful concept over an abstract integer
Having different kinds of XXXXXDateTime in the API is already complex. Making Instant separate from them may confuse users.

It occurs to me that the Instant class would replace the float type returned by the timestamp() function mentioned in https://github.com/ariebovenberg/whenever/issues/63 .

Not necessarily... Instant can be opaque while the timestamp must be a an integer with a specific value 🤔

I've come around to Instant now:

~The name UTCDateTime will be more familiar to most users than Instant~ Most modern datetime libraries have Instant (or similar)
~a UTC datetime is more human-friendly representation of an instant in time than an opaque integer class~ The Instant repr will be a UTC datetime
~For some contexts such as airline or militairy, UTC datetime is a meaningful concept over an abstract integer~ yes, but hardly anybody uses is as a "local" time for calendar operations. In the rare case it is, ZonedDateTime can be used.
~Having different kinds of XXXXXDateTime in the API is already complex. Making Instant separate from them may confuse users.~ Still true, but many people are confused by having a separate class for UTC anyway.

The next release will replace UTCDateTime with Instant

Release 0.6.0 is now out with this change

authors: ariebovenberg bxparks

repo: ariebovenberg/whenever


text:
Index Storage Parameter - Validation issue

This line right here checks for validity of a PSQL Index Storage Parameter during inspection. I'm no PSQL expert, but it seems like this storage parameter is just a generic string and only has meaning in the context of what ever index type is using it? Is there any way to treat these as opaque blobs in Atlas, or MUST they be parsed?
We use ZomboDB which has very bespoke syntax for defining cross-indexes via the Index Storage Parameters, and Atlas chokes with the error invalid index storage parameter: options=customers:(customer_id=<public.customers.idx_zdb_customers>id)
Replicating this would require you setup both ZomboDB and an Elastic instance, so it's not super straightforward. But the below SQL would cause the issue:
-- Simple parent tables
create table parent (id serial primary key);

-- Single child table for a 1:m relationship
create table child (
    id serial primary key,
    parent_id integer constraint fk_parent_id references parent
);

-- Index for both parent and child tables individually
create index idx_zdb_parent on parent using zombodb ((parent.*)) with (url='http:dokku.elasticsearch.stage:9200/');
create index idx_zdb_child on child using zombodb ((child.*)) with (url='http:dokku.elasticsearch.stage:9200/');

-- The problematic cross-join index, it doesn't like the two `=` occurrences.
alter index idx_zdb_parent set (options='children:(parent_id=<public.parent.idx_zdb_parent>id)');

Note: this issue is from this Discord thread.

Hi @a8m what can I do to help on this issue? My GoLang isn't strong enough to start really ripping into this. We would still really love to start using Atlas though 🤞

repo: ariga/atlas


text:
Create function - the planned state does not match the desired state after applying

Something seems to have changed in v0.28.0 - I can no longer apply my schema which contains functions with table row args.
> atlas.exe schema apply --env local
Abort: the planned state does not match the desired state after applying the file:

--- planned state
+++ desired state
@@ -18,7 +18,7 @@
 );
 CREATE INDEX "ix__contact__name-id" ON "contact" ("name", "id");
 CREATE INDEX "ix__contact__resource_groups-id" ON "contact" ("resource_groups", "id");
-CREATE FUNCTION "get_contact_tsv" ("data" "contact") RETURNS tsvector LANGUAGE plpgsql AS $$
+CREATE FUNCTION "get_contact_tsv" ("data" myapp.contact) RETURNS tsvector LANGUAGE plpgsql AS $$
 BEGIN
     RETURN setweight(to_tsvector(coalesce(data.name, '')), 'A');
 END;

Here's the function definition. I've also tried specifying the arg with type = table.contact but no change.
function "get_contact_tsv" {
  schema = schema.myapp
  lang   = PLpgSQL
  arg "data" {
    type = sql("contact")
  }
  return = tsvector
  as     = <<-SQL
  BEGIN
      RETURN setweight(to_tsvector(coalesce(data.name, '')), 'A');
  END;
  SQL
  depends_on = [table.contact]
}

I've also tried with v0.28.1 without luck. Where am I going wrong?

Hey @NathanBaulch 👋
Thanks for reporting this. I tried to reproduce it locally without success. Here is the schema I used:
schema "myapp" {}

table "contact" {
  schema = schema.myapp
  column "name" {
    type = text
  }
}

function "get_contact_tsv" {
  schema = schema.myapp
  lang   = PLpgSQL
  arg "data" {
    type = table.contact
  }
  return = tsvector
  as     = <<-SQL
  BEGIN
      RETURN setweight(to_tsvector(coalesce(data.name, '')), 'A');
  END;
  SQL
}

Just note, I used type = table.contact instead, since myapp.contact may differs from contact as the default search_path is public.
Could you provide a bit more information to help reproduce this? Are you using a dev-url in this env? Can you share the dev-url/url value you are using (omit the user/password/hostname before sharing).

OK, I was able to reproduce this when I scoped my connection to a specific schema.
The issue related to the new lint stage that was added to the declarative workflow (schema plan and schema apply) and it was fixed with #3201.
Thanks for reporting this.


text:
RFC5549 support for underlay

Change Summary
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes)
[x] Documentation content changes
[ ] Other (please describe):

Component(s) name
arista.avd.eos_designs
Proposed changes

How to test

Checklist:

[ ] My code has been rebased from devel before I start
[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated molecule CI testing accordingly
[ ] All new and existing tests passed (pre-commit, make linting and make sanity-lint).

Closing PR, as the source branch will change to projects/rfc5549

repo: aristanetworks/ansible-avd


text:
Typography not only setting color despite output settings

Issue description:
Using the code below, I expect a elements to pick up the set color only. But it seems to pick up other properties as well...
stilren_Kirki::add_field('stilren', array(
  'type' => 'typography',
  'settings' => 'default_text_font',
  'label' => _x('Main Font', 'Customizer → Typography', 'stilren'),
  'tooltip' => _x('Used for most text. The chosen font size will be used for paragrahps etc. The font size of other elements, such as the menu, are set automatically realtive to the font size set here.',     'Customizer → Typography', 'stilren'),
  'section' => 'typography',
  'default' => array(
    'font-family' => 'Source Sans Pro',
    'variant' => 'regular',
    'font-size' => '18px',
    'line-height' => '1.6em',
    'letter-spacing' => '0',
    'color' => '#060606'
  ),
  'priority' => 10,
  'output' => array(
    array(
      'element' => array(
        'body'
      ),
    ),
    array(
      'element' => array(
        'a',
        'a:hover',
        'a:active',
        'a:focus',
      ),
      'property' => 'color'
    )
  )
));

Version used:
3.0.15
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
See above

You need to use the choice argument.
array(
	'element'  => array( 'a', 'a:hover', 'a:active', 'a:focus' ),
	'property' => 'color',
	'choice'   => 'color',
),

The reason this is necessary is to allow for maximum flexibility.
For example it allows you to do things like this as well...
array(
	'element'       => array( 'a', 'a:hover', 'a:active', 'a:focus' ),
	'property'      => 'padding-top',
	'choice'        => 'line-height',
	'value_pattern' => 'calc($ / 2 - 3px)'
),

In the above example it sets the padding-top to be dependent on the line-height with a value of calc($line_height / 2 - 3px). It may be a useless example, but you get the point of what you can do... You can remove the line-height for example and make it depend on the font-size with some fancy calculations if that's what you want. 👍

Thanks, that worked!

authors: aristath transbetacism

repo: aristath/kirki


text:
Add way to set dns by command line

phantomjs setheader.js http://www.host1.com -d www.host1.com/127.0.0.1 -d www.host2.com/123.123.123.123
open http://www.host1.com, if some resource is from  www.host1.com or www.host2.com use the
ip replace.
This is a way to set the dns in js.

Our examples are designed to be as simple and as generic as possible. This one quite specific. I suggest creating a small project that demonstrates it, possible with an article/README/blog post to accompany the code.

OK!  I understand.

authors: ariya fengidri

repo: ariya/phantomjs


text:
How to use it properly with popup?

I'm trying to use the ng-click-outside directive, but it does not work.
It's a popup and when I click outside of the popup it should close the popup. The problem is, that when I click in the document to show the popup it triggers already the outsideClick event. How do I avoid this event to be triggered when my popup first opens?
This is my component:
<div id="template" (clickOutside)="clickOutside($event)" [style.visibility]="isVisible ? 'visible' : 'hidden'">
    <ng-content></ng-content>
</div>

  showPopup(): void {
    this._isVisible = true;
  }

  clickOutside(e: Event) {
    this._isVisible = false;
  }

The clickOutside event is triggered just after showPopup which causes the popup to close automatically.

That was my solution, but smells IMO
 showPopup(): void {
    this._active = true;
    this._isVisible = true;
  }

  clickOutside(e: Event) {
    if (!this._active) {
      this._isVisible = false;
    }

    this._active = false;
  }

Try using [delayClickOutsideInit]="true".

Ah, that makes sense. You could try [clickOutsideEnabled]="isVisible".

authors: arkon dgroh

repo: arkon/ng-click-outside


text:
Make FFTs nlog(d)

FFTs in the library are all nlog(n). However they could be nlog(d), which is an efficiency improvement when doing polynomial multiplication.
This can be taken advantage of in two possible ways:

Split up the FFT into n/d independent FFTs operating over the same polynomial, but evaluating on distinct cosets. Both of these sub-FFTs are dlog(d). At the end concatenate these two vectors.
Skip the first few rounds of butterflying / arithmetic in the current FFT algorithm, and just copy the polynomial coefficients into the correct positions. This is implemented in libiop.

This probably doesn't matter for the current pairing based SNARKs as they are dominated by MSM time.

This would help any time we do a polynomial multiplication, since the domain is necessarily equal to the sum of the degrees of the involved polynomial, and is hence usually at least double their degree.

@andrewmilson this change becomes possible with your work in #487; if you would like to take a stab at implementing the first approach @ValarDragon mentioned, that would be fantastic!

Thanks @Pratyush. Yeah keen to take a stab!

Awesome! Let me know if you have any questions about the approach; you can ask here or on Discord.

On Sep 28, 2022, at 6:01 PM, Andrew Milson @.***> wrote:
Thanks @Pratyush https://github.com/Pratyush. Yeah keen to take a stab!
—
Reply to this email directly, view it on GitHub https://github.com/arkworks-rs/algebra/issues/83#issuecomment-1261619865, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYSJ6VLKV2XS7TV5SLCEETWATS5ZANCNFSM4T4D4YUQ.
You are receiving this because you were mentioned.

@Pratyush unless I'm missing something I think it might be easier going straight to the second approach @ValarDragon mentioned.
With the first approach It's easy to obtain the values for the smaller FFTs evaluated on the coset domains but transposing the values so they are in order is not so easy. I haven't spent too much time looking into it but I don't think it's trivial to do without allocating extra memory.

You're right that the shuffles to put things in place are somewhat non-trivial, and might cause bad non-locality. It would be good to check what the situation would be like for the other approach.
Re: extra memory, we will need to allocate extra memory either way, since the output (evaluations) is larger than the input (polynomial)

With the first approach I mean additional memory on top of resizing the coefficients to the size of the domain.
The second approach has better locality and no need to allocate more memory than necessary. I put together a quick draft PR #493 just for ideas. I know you mentioned above you are "intending to refactor the FFT infrastructure". I'd be keen to hear what your thoughts are here. I'm more than happy to take the implementation further, just let me know.

authors: Pratyush ValarDragon andrewmilson

repo: arkworks-rs/algebra


text:
merge from template-sync/template-arlac77-github

.github/workflows/ci.yml

chore: (jobs.test-node.steps)

Pull Request Test Coverage Report for Build 10307116944
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.519%

Totals

Change from base Build 10293328370:
0.0%

Covered Lines:
165

Relevant Lines:
209

💛  - Coveralls


text:
bump dependencies

Applied mkpr on package.json
/tmp/mkpr.sh

Pull Request Test Coverage Report for Build 10432892899
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.807%

Totals

Change from base Build 10432870749:
0.0%

Covered Lines:
436

Relevant Lines:
461

💛  - Coveralls


text:
merge from template-sync/template-arlac77-github

package.json

chore(deps): add ^10.1.3 remove ^10.1.2 (devDependencies.c8)
chore(deps): add ^3.95.0 remove ^3.92.0 (devDependencies.wrangler)

Pull Request Test Coverage Report for Build 12266346710
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.42%

Totals

Change from base Build 12265936671:
0.0%

Covered Lines:
62

Relevant Lines:
71

💛  - Coveralls


text:
bump dependencies

Applied mkpr on package.json
/tmp/mkpr.sh

Pull Request Test Coverage Report for Build 9676467752
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.701%

Totals

Change from base Build 9673767410:
0.0%

Covered Lines:
78

Relevant Lines:
78

💛  - Coveralls


text:
Fix for routing table missing default route

This is the fix for missing default route in routing table when DHCP is triggered by maestro.

Since @cmonr is on vacation I'm going to take the liberty of merging this change.

repo: armPelionEdge/maestro


text:
🛑 miniTerm Sant Feliu is down

In 98395d5, miniTerm Sant Feliu ($SF_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: miniTerm Sant Feliu is back up in 092609c.

repo: armadillu/upptime


text:
Question: cuckoo filter

Hi,
I was wondering, using both bloom and cuckoo filters with different hash functions and thus reducing the collision rate, it would be highly unlikely that both filters could make false positive for the same element, also the overall size/memory footprint and performance would be better.
Ie. using both bloom and cuckoo filters with high FPP (0.01) would lead to wayyy lower collision rate than using only Bloom or Cuckoo filter with low FPP (0.00001) and it would be faster and smaller.
Have you considered adding support for https://github.com/efficient/cuckoofilter ?

@l15k4 It definitely looks interesting, I haven't considered it, as the algorithm was published after bloomd was written! It would be an neat extension, unfortunately I don't have time for that large of a change as the project is mostly in maintenance mode now. Would be open to a PR potentially, and happy to talk through a design doc!

repo: armon/bloomd


text:
feat(google): update gcloud sdk

for dyn-334

we gave this image to snap, so merging it 👍

repo: armory-io/clouddriver


text:
Fixed the navbar, removed the back button as not working neither need…

FIxed the navbar(linked the pages with it), removed the back button as it was not working and neither it was necessary and improbe the margin between navbar and quiz block.

Thank you for contributing! Looks good
Merging it!🚀

authors: arncv himughanakash

repo: arncv/Intima


text:
🛑 NWTFV is down

In 0b767e1, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in 9874171.

repo: arnef/status


text:
🛑 NWTFV is down

In 0450a3e, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in 25cf246.


text:
Adding Facebook clone front end template.

@arpit456jain Please assign this issue to me under GSSOC'22 contributions.

Issues for new projects will be assigned next week. This week we are only focussing on improving the existing ones. You can raise this issue / reopen it next week. Also, this is the wrong repo for this issue. You can raise it in Cool Fronted templates


text:
style_links.js not updated after removing some projects

Issue Type:

[x] Bug Report

Describe the bug

After commit #720 for solving the issue #718 some projects were removed but the style_links.js was not updated hence it yet  appear on the site
Alarm_clock, Pokemon generator,Candy Crush Clone, yet appears on search its index.html being deleted

Possible solution

Remove the links from style_links.js of all those removed projects
or replace the projects from non-plagiarised projects with similar concepts(I am ready to take this up too!)

Screenshot

@arpit456jain assign it to me I will do it


text:
defaultclient to public

change defaultclient to public for using query()

#27

Thanks!

authors: artemeff hey-jude

repo: artemeff/exredis


text:
🛑 Nitter is down

In 345574e, Nitter (https://tw.artemislena.eu) was down:

HTTP code: 502
Response time: 393 ms

Resolved: Nitter is back up in 34f692d.

repo: artemislena/upptime


text:
Looking for new maintainers

As we don't use the library day to day anymore, unfortunately we can't meet the proper maintenance requirements. To keep the project rolling, we're looking for a new maintainer (and owner).
If you're interested in taking over the project, please reach me by r@rhr.me or original project author - Gerben gerben.meyer@gmail.com

I'm the new maintainer. Feel free to address me if such a need arises!

authors: artisavotins operatino


text:
Apogee overview

An initial, non-technical overview of Apogee's development before diving into a more technical post next week. WIP because I need to finish writing it.

          4 Warnings

:warning:
Please use TypeScript, capital ‘S’

:warning:
Please use TypeScript, capital ‘S’

:warning:
Please use TypeScript, capital ‘S’

:warning:
Please use TypeScript, capital ‘S’

  Generated by :no_entry_sign: Danger

Great piece! A couple things that might be cool to touch on:

The "80/20" concept of coming up with approximate solutions to the data parsing problem, since the input data is often human formatted, with ad hoc solutions for edge cases. To me, this is an interesting subversion of the usual engineering impulse toward perfectionism.
The desire that any engineer should be able to roll out a new parser to ops with maybe 15 mins of effort.

Thanks! Agreed on both.

@acjay thanks for the thoughtful feedback – addressed in https://github.com/artsy/artsy.github.io/pull/414/commits/def7945363ff13ba4dd780a556a22a766f224310. Let me know what you think!

Awesome blarg post, merging!! 😝

authors: ArtsyOpenSource acjay ashfurrow jonallured


text:
Removes old subscriptions to improve lot list scrolling performance

Fix for https://github.com/artsy/auctions/issues/181.
Explanation: a lot's state is a mapping of its bidding status, which gets updated every time there's a new derived lot data (which happens on every related lot broadcast, which happens very very often). We weren't unsubscribing from old subscriptions, leading to hundreds of callbacks per lot in a list of hundreds of lots.
This issue is difficult to debug because it only occurs on sales with many lots, so I'll have to monitor an auction later to QA.

Conceptually looks good, would definitely require manual Q - aye 👍  (merge conflict BTW )

would definitely require manual QA

@ashfurrow I’m unsure how impactful this is and @orta’s comment makes it seem as though it might be. Are you confident enough in the change to include this in the 2nd beta we’re doing today/tomorrow?

I am, I tested locally and it works 👍

Works for me 👍

authors: alloy ashfurrow orta

repo: artsy/eigen


text:
Emission updates and new routes #trivial

Updates Emission. Follow-up to #2796 for new routes. Also includes Pulley change for LD-398. Merge on green.

This is already been queued for deploy.

merge on green

authors: ashfurrow orta


text:
Add tests for new sell tab landing page (including fixing several tracking bugs)

Collaboration with @xtina-starr
This PR adds some test coverage to the new sell tab.
It also updates the RecentlySold component to use cohesion for tracking, and fixes several tracking bugs:

we were using the wrong context_module for tracking taps of the footer button
we were not including the destination_screen_owner_id or destination_screen_owner_slug when tracking artist list taps
we were not including the context_screen_owner_type when tracking recently sold taps

LGTM!! 🎉 #mergeongreen

authors: jonallured pepopowitz


text:
User can see artist's artist series on the artwork page

The type of this PR is: feature
This PR resolves FX-2021
Description

Adds ability for users to see artist series from the artist on the artwork page (if the artist series feature flag is enabled)

Test Plan

@williardx to test in beta

Screenshots

🎉

authors: anandaroop williardx


text:
fix(SortOptions): auctions sort default options remove

The type of this PR is: Bugfix

This PR resolves CX-760
Description
For sort by, remove the "default" option – we should show that we're already sorting by lot number ascending

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

LGTM, feel free to merge once the test is fixed.

Thanks for the quick review 🙏

authors: MounirDhahri bhoggard


text:
Added code coverage w/ Coveralls.

https://coveralls.io/github/artsy/estella

Don't merge just yet, I am not seeing any results in Coveralls for some reason.

Changes Unknown when pulling a7a6720a715032127d17284ad1a35a677d31aae0 on dblock:code-coverage into ** on artsy:master**.

This is good to go @cavvia, check out  https://coveralls.io/builds/9837653.

:+1: 91% sounds pretty good to me.

authors: cavvia coveralls dblock

repo: artsy/estella


text:
@eessex => Refactor Newsfeed scrolling

Separates out NewsArticle into a subcomponent to better handle scrolling and url handling. The main change is that waypoint handling is no longer tied to the main app and each article is now responsible for its own changes. We make use of waypoints with children to handle the top and bottom of the article.
Addresses
https://artsyproduct.atlassian.net/browse/GROW-444
https://artsyproduct.atlassian.net/browse/GROW-177

@eessex rdy 4 review!

repo: artsy/force


text:
[package] Update dd-trace to use our fork with connection tracing.

https://github.com/DataDog/dd-trace-js/pull/299

Cool beans

authors: alloy orta


text:
Update what_is_artsy.md

I think the apple watch app is a good example of quality worth of art. We didn't ship because it wasn't going to be 💯  because apple watch apps weren't(/aren't still) 💯

Updated

repo: artsy/meta


text:
Why console print "rtmp" directive is not allowed?

How to soled this issue?  Thanks all!
OS: Centos 7
configure arguments: --prefix=/usr/local/nginx --modules-path=/usr/local/libexec/nginx --add-module=../nginx-rtmp-module --with-http_ssl_module.
compile and install has no errors

Maybe the "rtmp" directvie's location is not right,  it must locate in root context of the config file.

Maybe the "rtmp" directvie's location is not right, it must locate in root context of the config file.
relevant source code from ngx_conf_file.c as below:
if (found) {
        ngx_conf_log_error(NGX_LOG_EMERG, cf, 0,
                           "\"%s\" directive is not allowed here", name->data);

        return NGX_ERROR;
}

wow! Thank you very much, it works!

authors: Bingqiang-Jing yidezhangfei

repo: arut/nginx-rtmp-module


text:
Flash Clients Not Working

After 3 or so minutes of streaming, initiating playback of the stream no longer works. The timecode of the flash client reads 0:00. I've already tried the fix playback timecode config command to no avail I'm afraid.

I have the same problem, but not only with Flash clients.
After a few minutes, it's not possible anymore to connect new clients.
ffplay, vlc, jwplayer, doesn't matter. They all fail to "tune" into the stream.
ffplay doesn't even display stream metadata, it just sits there and does nothing, failing after a while:
https://gist.github.com/BtbN/9873af626908bf583af4
Clients which were already connected keep streaming, even for long periods of time.

I already fixed this. The issue was caused by "allow play all" and in the same config block "deny play all". I removed "deny play all" and it started working like a charm.

That's the relevant config i'm using currently. All the "fancy" options were added trying to fix said issue, nothing changed.
rtmp {
        server {
                listen [::]:1935 ipv6only=off;

                publish_time_fix on;
                play_time_fix on;

                application live {
                        live on;

                        wait_key on;
                        wait_video on;
                        publish_notify on;
                        play_restart on;

                        interleave on;
                        meta copy;

                        allow publish 192.168.0.0/16;
                        allow publish 127.0.0.0/8;
                        deny publish all;
                        allow play all;
                }
        }
}

Try removing publish_time_fix on; and play_time_fix on;.
The code that was behind those two directives were already integrated into the core nginx-rtmp module.

Also, I'm not sure if this module plays well with IPv6 so try using IPv4.

I added these in an attempt to fix the issue, removing all special directives makes no difference.

Have you tried using just listen 1935;?

Didn't change anything, I'm only using IPv4 anyway, as it's a local server.
Shouldn't matter at all, as it's just the underlying IP protocol.

If your using IPv6 then why... Oh nevermind. Anyways, let's try stripping down to the bare config needed to stream.
live on; allow publish all; allow play all;
I should note that I've used nginx-rtmp in a more complicated setup involving HD streaming, password auth, recording, HLS, conversation, and automatic uploading to a public webserver. I've managed to get a pretty stable stream working with 30 clients on a school network.

As i said, everything fancy in that config is just there in an attempt to fix the issue.
Even with the most basic configuration, it's not possible for new clients to tune in after a short while.

Then I'm afraid your problem is something else. What version of ffmpeg are you using? Operating system?

Nginx version?

tried various versions from both ffmpeg and nginx, currently on 1.8 nginx and git-master ffmpeg.
It's the exact same problem every single time.

Hi,
What is your Nginx version ? What is your Linux distribution and Kernel version ?

authors: BtbN joshgarde ymaheo