Use deck.gl in combination with WebGL Globe

I'm wondering if it is possible to map the visualization from my deck.gl application to a basic WebGL Globe (https://experiments.withgoogle.com/chrome/globe). How would I do that?

It's a fun idea!
A possible starting point would be the fact that all layers use a common project "shader module" to transform their coordinates, so in theory it should be possible to extend or replace this module with code that does spherical projections.
It would be a fun project, but would require a fair bit of effort, and the required 3D math should provide for some fun mental gymnastics.
If you really want to try, the shader module gets uniforms from the Viewports classes so you'd want to get up to speed on those as well.


Sum edges that have equal node ends.

Currently, the visualization on the website has 20 nodes and 15 edges that one can see. However, under the hood, there are actually hundreds of edges, because many times, the same superpac will donate to the same represenative.
Ideally, the backend should run a summing operation on the matching edges, so that the simulation will run faster.

fixed


Add a newline between crt & key.

Manual testing shows HAProxy don't mind the extra newline.

Fixes #261


Incorrect messages for array as input

Hi @solnic ,
consider such schema:
schema = Dry::Validation.Schema do
  key(:nested).each do
      key(:name).required
      key(:age).required
  end
end

p schema.({nested: [{ name: 'Jane', age: 21 }, { name: nil, age: nil }, {name: nil, age: nil}]}).messages
  # => {:nested=>{1=>{:name=>["must be filled", "must be filled"], :age=>["must be filled", "must be  filled"]}}}

schema = Dry::Validation.Schema do
  each do
      key(:name).required
      key(:age).required
  end
end

p schema.([{ name: 'Jane', age: 21 }, { name: nil, age: nil }, {name: nil, age: nil}]).messages
  # => {1=>{:name=>["must be filled", "must be filled"], :age=>["must be filled", "must be filled"]}}

In both cases it returns probably first invalid index, but do not continue with the remaining indexes (or continues, but pushes messages into first found?).

This seems like a bug in dry-logic. The error ast doesn't look correct for such use case. Funny part - it only happens when there are two inputs in the array that are equal.


Separate state detection from current animation

It's kinda ugly to do it this way.

Could be fixed in tandem with #3 hopefully.


feat: Use new theme

Change colors, font & logo
8th PR to implement the new theme from the POC https://github.com/process-analytics/process-analytics.dev/pull/424

Before
Now

✔ The rendering is OK.
❌ There is an issue with the logo IMHO, the file permissions changed.
logo_white.svg shouldn't be updated

@tbouffard logo_white.svg must be updated, because we don't use the same red.
I fixed the mistake in this file.

@tbouffard logo_white.svg must be updated, because we don't use the same red.
I fixed the mistake in this file.

OK for the color in logo_white.svg, I didn't notice that.
However, there is still an extra change: file permissions changed from 100644 to 100755 in the 2 SVG files.


Hide the python interpreter on sessions with only one

This also finally allows sessions to properly have multiple names.
Closes #118

I would like to write a few more tests to make sure the sessions are getting the right signatures in various cases, but so far this seems to work fine.


Up/down keys now move cursor up/down one line

ah, hmm. You've just made a huge change in acme behavior. Let's talk about this.

I'm agree to add this behavior (I will use it), but maybe it should be activated with a flag or with an internal command like when you activate autoindent with "indent on".

This reminds me of a change that redhat made to the default behaviour of vim in the early days. They set up the default profile of vim so that you could use cursor keys to navigate around when in insert mode. From this, a generation of users who missed the point of vi.
At the same time, something that makes Harvey exciting is that it is creating pragmatism in a community that's not known for it.
Harvey might become this: a good bridge by which people from unix backgrounds can migrate into plan9. Is that Harvey's mission? If so, is this change in the spirit of that?

oh let's try it
LGTM

@cratuki , one of the goals, but not the only one. But yes, one of the big walls to break is that weird fame of unusable for what 9 systems are sadly known. But many other things are on fly.

@rminnich @elbing @cratuki  I'm wondering if I should create a new "acme" (nadir?) and leave classic acme as it is.  There are quite a few changes I'd really like to make, but I don't want to alienate everyone??

Not bad idea, I modified rio in past and called rio2 (privately) to not breaking replica. Please, do it. Then changes on it could be introduced lab style, almost without discussion.

I'll update this tonight & retry


1024 bytes of .ext_ram_noinit cleared after esp_restart() with CONFIG_SPIRAM_2T_MODE=y (IDFGH-11231)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello,
I am facing a problem when CONFIG_SPIRAM_2T_MODE is enabled. The first 1024 bytes of noinit extram are overwritten after esp_restart() with 0xff. I am using the following code example:
#include <stdio.h>

#include <freertos/FreeRTOS.h>
#include <freertos/task.h>
#include <esp_attr.h>

#include <esp_log.h>
static const char* TAG = "main";

#define TEST_BUFFER_SIZE (16*1024/4)
static EXT_RAM_NOINIT_ATTR uint32_t s_noinit_buffer[TEST_BUFFER_SIZE];
static __NOINIT_ATTR uint32_t s_noinit_firstrun[1];

extern void esp_psram_extram_writeback_cache(void);

static void write_spiram_and_reset(void)
{
    // Fill the noinit buffer
    printf("Filling buffer\n");
    for (uint32_t i = 0; i < TEST_BUFFER_SIZE; i++) {
        s_noinit_buffer[i] = i ^ 0x55555555U;
    }
    printf("Flushing cache\n");
    // Flush the cache out to SPIRAM before resetting.
    esp_psram_extram_writeback_cache();
}

static void check_spiram_contents(void)
{
    // Confirm that the memory contents are still what we expect
    uint32_t error_count = 0;
    for (uint32_t i = 0; i < TEST_BUFFER_SIZE; i++) {
        if (s_noinit_buffer[i] != (i ^ 0x55555555U)) {
            error_count++;
        }
    }
    printf("Found %" PRIu32 " memory errors\n", error_count);
}

void app_main() {

  check_spiram_contents();
  // ESP_LOG_BUFFER_HEXDUMP(TAG, &s_noinit_buffer[0], TEST_BUFFER_SIZE, ESP_LOG_INFO);
  if(s_noinit_firstrun[0] != 0xDEADBEEF) {
    ESP_LOGI(TAG, "====> FIRST RUN");
    s_noinit_firstrun[0] = 0xDEADBEEF;
    write_spiram_and_reset();

    ESP_LOGI(TAG, "====> CHECK BEFORE RESTART");
    check_spiram_contents();

    ESP_LOGI(TAG, "====> EXPECTED RESTART");
    // Reset to test that noinit memory is left intact.
    esp_restart();
  }

}

Found 256 memory errors is the result after esp_restart(). The first 1024 bytes (256x4byte) of noinit buffer that is located at the beginning of the noinit section in extram are overwritten with 0xff.
If I disable CONFIG_SPIRAM_2T_MODE it is not overwritten (Found 0 memory errors). Can someone help me?

I can reproduce the issue.
The issue is caused by function psram_2t_mode_check() in esp_psram_impl_quad.c which overwrites the first kilobyte of every megabyte with 0xff to check whether 2T mode is already on. This only happens when CONFIG_SPIRAM_2T_MODE is enabled.
Changing psram_2t_mode_check() so that it saves and restores the written memory before/after the test solves the problem.


B405 complains about any xml.etree.ElementTree import, not just parse-related ones

B405 complains about any xml.etree.ElementTree import, not just parse-related ones
Importing like so
from defusedxml.ElementTree import Element

gives a bandit error (B405).
This error talks about parsing (which is indeed unsafe); but the imported thing is not related to parsing. At the same time, the suggested remedy (defusedxml) exclusively provides alternatives for parsing-related functions, in particular for parse, iterparse, fromstring, and XMLParser. In other words, the suggested solution of doing the following fails:
# Will fail!
from defusedxml.ElementTree import Element

Just to add to this. It's important if you are using type hints
from defusedxml.ElementTree import fromstring
from xml.etree.ElementTree import Element

root: Element = fromstring("<foo/>")

Still an issue. Simple fix is to just ignore the type-hinting elements.


Fix erroneous types

This PR fixes erroneous types for:

the ECDSA signature of the Ethereum tx
the keys an signature of the OTSchnorr

It also:

changes notations in the OTSchnorr algos to align with notations of Bellare and Shoup
Introduces more "constant" notations for base and scalar fields of interest
introduces simplified notations for elliptic curve groups

@mpzajac @dtebbs same as for #12, could you both check this one to make sure I didn't do any mistakes? :)

LGTM

LGTM


Implement ECMA262 RegExp builtin object and RegExp engine

Related ECMA2626 section: http://www.ecma-international.org/ecma-262/5.1/#sec-15.10.3

[x] Regexp Builtin components

[x] Register the RegExp built-in object.
[x] RegExp(..)

[x] RegExp(pattern)
[x] RegExp(pattern, flag)
[x] RegExp(RegExp)

[x] new RegExp(..)

[x] RegExp(pattern)
[x] RegExp(pattern, flag)
[x] RegExp(RegExp)

[x] RegExp.prototype
[x] RegExp.prototype.constructor
[x] RegExp.prototype.exec(..)
[x] RegExp.prototype.test(..)
[x] RegExp.prototype.toString(..)
[x] RegExp.source
[x] RegExp.global
[x] RegExp.ignoreCase
[x] RegExp.multiline
[x] RegExp.lastIndex

[x] Implement RegExp bytecode storage

Requirements

[x] Resize  automatically when it is needed
[x] Append and insert uint32 and uint8
[x] Read uint32 and uint8
[x] Advance in bytecode while reading
[x] Dump container (for debug)

[x] Compile RegExp bytecode

Compile RegExp pattern to an internal bytecode to be able to run it efficiently.

[x] Disjunction
[x] Alternative
[x] Assertion
[x] Atom

[x] PatternCharacter
[x] .
[x] \ AtomEscape (depends on #49)
[x] CharacterClass

[x] Quantifier

[x] Execute RegExp

Read the compiled bytecode and try to match.

[x] Disjunction
[x] Alternative
[x] Assertion
[x] Atom

[x] PatternCharacter
[x] .
[x] \ AtomEscape
[x] CharacterClass

[x] Quantifier
[x] Handle flags (depends on #49)

[x] Global
[x] IgnoreCase
[x] Multiline

[x] Set lastIndex property
[x] Set properties of the returned array object

[x] Parse RegularExpressionLiterals and create a RegExp object.

Everything is implemented, so we can close this bug.


Use a separate release profile for CI static builds

Change-type: patch
Signed-off-by: Zahari Petkov<EMAIL_ADDRESS>

@balena-ci I self-certify!


python310Packages.garminconnect: 0.1.51 -> 0.1.53

Changelog: https://github.com/cyberjunky/python-garminconnect/releases/tag/0.1.53
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 213170 run on x86_64-linux 1

2 packages built:

python310Packages.garminconnect
python311Packages.garminconnect


[Extension Bug] Can the gitlab plugin add v3 compatibility and allow switching api versions

Extension – Gitlab

Author: @tonka3000

Description
My company is using v8 version of gitlab instance and api is using v3 version, is it possible to consider compatibility?
Steps To Reproduce

Set instance url and token
Search project

The current behavior
Prompt error 404
The expected behavior
Is it possible to add v3 compatibility while allowing switching api versions
Raycast version
Version:

Raycast: 1.26.1
Extension: 1.1.0

Hi @HuangJunjia ,
I have no access to a GitLab 8.0 version. So testing it would be really hard. Since GitLab 8.0 is from 2015(!) I would not add support for v8.0 myself.
Maybe you wanna add the support for that yourself via a PR?
Greetings
Michael

Hi @HuangJunjia ,
I have no access to a GitLab 8.0 version. So testing it would be really hard. Since GitLab 8.0 is from 2015(!) I would not add support for v8.0 myself.
Maybe you wanna add the support for that yourself via a PR?
Greetings Michael

I am very sorry that my English is not very good, there is no clear expression of my thoughts.
If you don't mind, can I add support to the V8.0 version API?


Corporate Console - Once rejected CLA Manager is able to keep joining the company but request is always set as rejected

Background

Launch Corporate Console
Login as clamanager2
Search and Select the company WhitelistAcceptTest
Click Join Company
Click ok on the notification popup
Login to corporate console as nirupamavkrsna (CLA Manager of the company WhitelistAcceptTest)
Click on the company
Decline the CLA Manager request of clamanager2
Login to corporate console as clamanager2
Search and select the company WhitelistAcceptTest
11, Click Join Company
Click Ok on notification popup
Email is sent to the CLA managers of the company but clamanager2 is not able to see the company with status Awaiting Approval and Also there is no pending request for clamanager2 for the CLA Managers of the company.
I am able to repeat Step13 any number of times. Either rejected CLA Manager should not be able to join company again or if CLA manager is able to join company again, status should be pending and not rejected

@nirupamav @WillsonHG For this one, I have decided (feedback welcome):

if existing request with 'pending' or 'approved' status - return 409 conflict - UI must show error message @amolsontakke3576 (see swagger spec updated which includes 409 definition)
if existing request with 'denied' status - let's be nice, allow them to try again - set existing record status to 'pending', updated modified date/time, send emails, add event log notices, UI should refresh to show the current status.

I will create a PR shortly...

@nirupamav I didn't get a chance to do a lot of testing on this - can you help verify?  @amolsontakke3576 will want to add error handling on this request: https://github.com/communitybridge/easycla/blob/master/cla-frontend-corporate-console/src/ionic/pages/company-page/company-page.ts#L343

Issue is still reproducible

@dealako @wanyaland  I have checked the issue and as per the above comment status should be changed from rejected to pending when user request again.

Verified that the issue is fixed

Confirmed fixed. Closing issue.


NSM-544: Create SPIFFE shared library for KIC/NSM

Proposed changes
This change addresses NSM-544 by collecting several pieces of SPIFFE and Cert reload related code into one library. All non-member functions now reference the types they address. Test packages and go:generate usage has been adjusted. Unit tests pass.
Signed-off-by: Ava Hahn<EMAIL_ADDRESS>This continues #135
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

LGTM, though potential for one more change (see https://github.com/nginxinc/kubernetes-ingress/pull/3482#discussion_r1088025388O


Drop all tables on upgrade

There doesn't seem to be a good way to drop all tables on upgrade, but it would be really helpful especially when developing.
My app does not rely on IndexedDb content, if it's empty it's populated from server. Thus this would be a good way for me to tinker, since I need not to worry about upgrade process during development. When the contents of the indexeddb is always pristine, I could just change the version number and know my db is empty:
this.version(2).stores({
            projects: "++id,client,project,start,end"
        }).upgrade (() => {
            // How to drop all tables here?
        });

Edit Alternatively for my case, I could use a way to drop a whole database if the version differs before dexie creates a new one.

The upgrade() method is meant to convert existing model to a new model. If you need to drop all tables, you don't need to use upgrade().
var db = new Dexie ('dbname');
db.version(1).stores({
    projects: "++id,client,project,start,end"
});

function recreateDatabase () {
    return db.delete().then(()=> db.open());
}

recreateDatabase().then(db => {
    // Here you have a fresh empty database with tables and indexes as defined in version(1),
    // no matter what version the db was on earlier or what data it had.
});

If let's say you've released your app with db.version(1) and have changed your model so that a certain table is no more needed, you can explicitely drop the old table as such:
db.version(1).stores({
    projects: "++id,client,project,start,end",
    project_details: "++id,project_id"
});
db.version(2).stores({
    projects: "++id,client,project,start,end,details",
    project_details: null // Will delete the table
});

I don't want to drop it always, only when the version number changes. I don't think your examples cover that?
Btw, why did this work? I know it maybe because the delete runs in some cases fast enough:
        this.version(4).stores({
            projects: "++id,client,project,start,end",
        }).upgrade (async () => {
            await this.delete();
        });

But if that were allowed, it would work wonders.

Can I check the current version before I open the dexie db? I'd like to drop the db if the version differs. I'm getting all sort of troubles at the moment with versions.

Yes you can open database without specifying version:
new Dexie("dbname").open().then(db => {
    console.log (`Current version is: ${db.verno}`);
});

I couldn't get it working, when using inheritance:
class MyDb extends Dexie {
    projects: Dexie.Table<{
        id?: number;
        client: string;
        project: string;
        start: Date;
        end: Date;
    }, number>;

    constructor() {
        super("MyDb");
        this.open().then(d => {
            if (d.verno !== 30) {
                d.delete();
            }
            this.close();
        });
        this.version(3).stores({
            projects: "++id,client,project,start,end,details"
        });
    }
}

I still think the cleanest way would be a way to drop a whole database during upgrade.

That doesn't work because this.version(3) will be executed before the database is opened.
You should ideally bootstrap your app with:
async function openDatabase() {
    var tempDb = await new Dexie("dbname").open();
    if (tempDb.verno < 30) await tempDb.delete();
    tempDb.close();
    return new MyDb().open();
});

..or possibly the following:
class MyDb extends Dexie {
    projects: Dexie.Table<{
        id?: number;
        client: string;
        project: string;
        start: Date;
        end: Date;
    }, number>;

    constructor() {
        super("MyDb");
    }

    async init () => {
        await this.open();
        if (this.verno < 30) {
            await this.delete();
        } else {
            this.close();
        }
        this.version(3).stores({
            projects: "++id,client,project,start,end"
        });
        await this.open();
    }
}

Heads up that it's a highly prioritized task to improve the version handling in Dexie (See #287 and #105), and I'll take your use case into account when doing that. Expect it to be improved within the next 2-3 months or so. Some of the improvements will be:

Allow upgrade functions to access the database based on the old schema (run upgrader before old indexes and tables are deleted).
No more need to keep the definitions of older versions in the unless they have an upgrade() attached to them. Instead, Dexie should inspect the current schema and use that as the diff source instead of the specified one.
Complain if there is a diff between the actual schema and the specified schema in case no upgrade was needed. Suggest increase of version number in the exception message.

Your use case is also relevant so, maybe it could be handled via some kind of instruction for that, such as:
db.version(3).recreate({
    projects: "++id,client,project,start,end"
});

Would a recreate alternative solve your case?

Yes, it would solve my case, I appreciate the time you've taken to solve this.
I haven't yet figured out how to get the init example working, if I call init myself, the transactions doesn't seem to work afterwards, if I don't call init it's not working either.

Are you awaiting the init() Another question, is your current version 3 or 30?

Actually, I changed it to "3". But that is not the issue. The thing is, if my app is written like this:
let db = new ProjectMonitoringDb();
...
db.transaction("r", ...)
db.transaction("rw", ...)

Where could I await the init? In all transaction calls?

I get the point. There's another solution that might work better:
class MyDb extends Dexie {
    constructor() {
        super("MyDb");
        this.version(3).stores({
            projects: "++id,client,project,start,end"
        });
        let origOpen = this.open as any, // Override open like this because it's not on prototype
            initStarted = false,
            openPromise : any = null;

        (this as any).open = function () {
            if (!initStarted) {
                initStarted = true;
                openPromise = new Dexie(this.name).open().then(tempDb=>{
                    if (tempDb.verno < 3) return tempDb.delete();
                    tempDb.close();
                }).then(()=>origOpen.apply(this, arguments));
            }
            return openPromise;
        };
    }
}

Haven't compiled it but try it out, correct my bugs and see if it does it for you.

Quick testing, it seems to work, and the code (regardless of odd inheritance pattern) makes sense. Thanks a lot!

Nice to hear. If you need to keep abreast of close() / reopen to work also, you must override close:
let origClose = this.close as any;
(this as any).close = function() {
    openPromise = null;
    return origClose.apply(this, arguments);
}

This worked well for me (version 3.0.3):
import Dexie from 'dexie';

export class MyDexie extends Dexie {
  private static readonly targetVersion = 10;

  public open() {
    if (this.isOpen()) return super.open();

    return Dexie.Promise.resolve()
      .then(() => Dexie.exists(this.name))
      .then((exists) => {
        if (!exists) {
          // no need to check database version since it doesn't exist
          return;
        }

        // Open separate instance of dexie to get current database version
        return new Dexie(this.name).open()
          .then(async db => {
            if (db.verno >= MyDexie.targetVersion) {
              // database up to date (or newer)
              return db.close();
            }

            console.log(`Database schema out of date, resetting all data. (currentVersion: ${db.verno}, expectedVersion: ${MyDexie.targetVersion})`);
            await db.delete();

            // ensure the delete was successful
            const exists = await Dexie.exists(this.name);
            if (exists) {
              throw new Error('Failed to remove mock backend database.');
            }
          })
      })
      .then(() => super.open());
  }
}

Heads up that it's a highly prioritized task to improve the version handling in Dexie (See #287 and #105), and I'll take your use case into account when doing that. Expect it to be improved within the next 2-3 months or so. Some of the improvements will be:

Allow upgrade functions to access the database based on the old schema (run upgrader before old indexes and tables are deleted).
No more need to keep the definitions of older versions in the code unless they have an upgrade() attached to them. Instead, Dexie should inspect the current schema and use that as the diff source instead of the specified one.
Complain if there is a diff between the actual schema and the specified schema in case no upgrade was needed. Suggest increase of version number in the exception message.

Your use case is also relevant so, maybe it could be handled via some kind of instruction for that, such as:
db.version(3).recreate({
    projects: "++id,client,project,start,end"
});

Would a recreate alternative solve your case?

Do you have any plans to implement it in near future?

@dfahlander Do you have any plans to implement it in near future?

The quote refers to other already resolved issues. One of them was not marked as resolved but I closed it now as it has been possible for a great while to do all the things that the quote refers to: version N: access a table and do things like copying its content into a new table, version N+1: delete the table that was read from. This all enables the possibility to do things like changing foreign keys etc.
What this issue is about, is some sugar for dropping all tables and not having to explicitly specify the tables to drop (setting their value to null). I don't see it as prioritized as the referred issues.

Hi, thanks for the work on this library. Is there any documentation on how to make the ask from the original commenter easier achievable? I found https://dexie.org/docs/Tutorial/Design#database-versioning but I'm not finding the information I'm looking for.
I wasn't able to make this work: https://github.com/dexie/Dexie.js/issues/349#issuecomment-255072346 Either the open() call seems to be left hanging or I got a Dexie.delete('myDb') was blocked warning.
I am simply trying to clear the whole database on version upgrade. Right now, it's because I've changed a primary index (project is still under heavy development) but in most cases, since the data stored in this DB is non-critical, flushing is preferable to trying to migrate.
I'm on Dexie 3.0.4

Given that table: null deletes tables isn't this the final correct solution:
this.version(1).stores({
	foo: 'id',
	bar: 'id',
});

// Instead of adding one migration, add two at once, one deletes the tables, another recreates them:

this.version(2).stores({
	foo: null,
	bar: null,
});

this.version(3).stores({
	foo: 'foo',
	bar: 'bar',
});

I went through the open hacks and such before I finally noticed the null feature and it works flawlessly for me.


Datagrid Documentation: Wrong single action example video

Describe the bug
The example video for single action shows the single selection.

How to reproduce
https://clarity.design/angular-components/datagrid/#single-action
Versions
Clarity project:

[x] Clarity Angular/UI

Clarity version:

[x] v5.x

A new video has been pushed to the edge of the cdn.


Weaving segment data

Hello!
Will you upload the weaving segment data in the near future?
Thanks.

Yes, next week


Error importing database dump files

Describe the bug
I'm getting the following error:
ERROR 2006 (HY000) at line 1: MySQL server has gone away
That error occurs when I'm trying import a dump file using the following command:
kool run mysql myDatabase < myDump.slq
onde mysql => kool exec database mysql -uroot -p$DB_PORTAL_PASSWORD
The error doesn't occurs when I'm run:
docker-compose exec -T database mysql --max_allowed_packet=64M --connect-timeout=60 -uroot -p$DB_PORTAL_PASSWORD myDatabase < myDump.slq
kool version 1.14.0
OS: Ubuntu 20.04.2 LTS
Docker version 20.10.6, build 370c289
docker-compose version 1.26.1, build f216ddbf

kool info:
KOOL_DEPLOY_DOMAIN=completa-web-develop.kool.dev
KOOL_NAME=web
KOOL_GLOBAL_NETWORK=kool_global
KOOL_ASUSER=1000

@fabiocontiero - please, can you confirm you can consistently reproduce this issue? Everytime you attempt to do it using kool run mysql < ?
Then please, can you add a pastebin or forward me somehow, the whole output of running this with --verbose flag?

@fabiocontiero I can somewhat reproduce the issue.
Please can you test the very same command you are trying, but putting it within a script in kool.yml? Just to make sure the same command works when executed from there.

PR is under review, the fix will go into next release.

This has been fixed within our latest release 1.15.0.


Violinplot Stretch

In the latest commit the teammate_comp violinplot has over-stretched violins. Suspect seaborn 0.13.0 issue. Needs investigation.

Fixed in the latest commit. Only change required was updating seaborn


5-node tests are racy, disabling pending debug

I am actively debugging the issues on 5-node clusters. Until I fix them, I am disabling these tests.

Unit test code only, self-merging on green.


Improved Settings Layout

added Headline
Clickable link in description
Wider Input Fields for better overview of the path

Good work!


How to pick specific .env file?

I've read the documentation and looked at the example CRA app but I can't figure out how to pinpoint a specific .env file.
I have a brand new CRA with the following file/folder structre

I then updated my package.json with the following...
  "scripts": {
    "start": "react-env --env staging -- react-scripts start"

I was expecting this to point to my .env.staging file when doing npm start but it doesn't. Instead it just loads the .env file.
I also tried react-env --env APP_ENV=staging -- react-scripts start but it didn't work either.
Where am I going wrong here?
This is the output from my npm start
$ npm start

><EMAIL_ADDRESS>start E:\Repos\ReactEnvTest\reactenvtest
> react-env --env staging

Writing runtime env  E:\Repos\ReactEnvTest\reactenvtest/public/__ENV.js
{
  "REACT_APP_CRA": "Create React App",
  "REACT_APP_NEXT": "Next.js",
  "REACT_APP_NOT_SECRET_CODE": "1234"
}

And this is the contents of my env.staging
REACT_APP_NEXT="Staging Next.js"
REACT_APP_CRA="Staging Create React App"
REACT_APP_NOT_SECRET_CODE="12345"

@andrewmclagan ,
it would be better if you make it clear that we should set APP_ENV as an environment variable in terminal.

because for now with the example you've written, we might be confused as "you have to replace 'APP_ENV' with the name of environment you want". (As a result, we might end up writing react-env --env staging instead of APP_ENV=staging react-env --env APP_ENV.)


D3 v4 compatibility

Still backwards compatible with D3 v3.

Use the passed argument from selection.call instead of this (v4 no longer bindsthis to .call)
Switched all .attr(object) calls to singular, chained .attr statements -- compatible with both v3 and v4 without introducing a d3-selection-multi dependency

This should close #23

Thanks for the PR.
++1 for D3 v3 backwards compatibility.
Merged.

package.json needs a version bump. Do you want to just do it or would you like a PR?


make the full model in GGUF format available on HF

HF page: ibm/merlinite-7b-GGUF
criteria

make sure it works fine with ilab download with some arg
make sure it works fine with ilab chat

like chatting is fine, no weird behavior (unexpected tokens), etc.

Isn't this done?

Spoke with @jaideepr97 and he said we can close this out for now


[BUG] Multi-GPU Criteo/DLRM Benchmark not on DGX

Describe the bug
I was doing Multi-GPU Criteo/DLRM Benchmark on 4 GPUs (V100, V100s, P4, T4). Setting device-pool-frac to be 0.2 to make sure the pool size will not exceed P4's maximum memory.
There is an error about pyarrow.lib.ArrowInvalid: Buffer #0 too small in array of type string and length
Also, I am wondering is there any better methods for re-initializing RMM pool size for each GPU separately, and then client.run(_rmm_pool)
Steps/Code to reproduce bug
python3 NVT-preproc-standard.py --data-path  '/workdir/NVT-input/temp-output-dask/temp-parquet-after-feature-crossing/' --out-path '/workdir/NVT-input/temp-output-standard' --devices "0,1,2,3" --device-pool-frac 0.2
Environment details (please complete the following information):

Environment location: NGC-NVTabular 0.2 Docker
Method of NVTabular install: docker pull nvcr.io/nvidia/nvtabular:0.2
GPUs: V100, V100s, T4, P4
device-pool-frac: 0.2

Additional context
Traceback (most recent call last):
  File "NVT-preproc-standard.py", line 347, in <module>
    main(parse_args())
  File "NVT-preproc-standard.py", line 170, in main
    output_path=output_path,
  File "/nvtabular/nvtabular/workflow.py", line 734, in apply
    num_io_threads=num_io_threads,
  File "/nvtabular/nvtabular/workflow.py", line 832, in build_and_process_graph
    self.exec_phase(idx, record_stats=record_stats)
  File "/nvtabular/nvtabular/workflow.py", line 632, in exec_phase
    computed_stats, op = r.result()
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/distributed/client.py", line 225, in result
    raise exc.with_traceback(tb)
  File "/opt/conda/envs/rapids/lib/python3.7/contextlib.py", line 74, in inner
    return func(*args, **kwds)
  File "/nvtabular/nvtabular/ops/categorify.py", line 375, in _top_level_groupby
    output[k] = split.to_pandas()
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/cudf/core/dataframe.py", line 4686, in to_pandas
    out_data[i] = self._data[col_key].to_pandas(index=out_index)
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/cudf/core/column/column.py", line 128, in to_pandas
    pd_series = self.to_arrow().to_pandas(**kwargs)
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/cudf/core/column/string.py", line 4617, in to_arrow
    len(self), obuf, sbuf, nbuf, self.null_count
  File "pyarrow/array.pxi", line 1807, in pyarrow.lib.StringArray.from_buffers
  File "pyarrow/array.pxi", line 871, in pyarrow.lib.Array.from_buffers
  File "pyarrow/array.pxi", line 1168, in pyarrow.lib.Array.validate
  File "pyarrow/error.pxi", line 85, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: Buffer #0 too small in array of type string and length 352919: expected at least 44115 byte(s), got 11072

If you are having trouble setting a "normal" pool size (>=50%), there may be a problem with dask-cuda or rmm.  I wouldn't expect a smaller pool size to help with OOM errors, but I could be wrong.
Note that the multi-gpu criteo/DLRM benchmark was designed with 32GB V100s in mind, and was only tested on 16GB+.  For smaller GPUs, you may need to use a smaller --part-mem-frac option (down to 0.1 or less), and you may need to reduce --device-limit-frac (down to 0.75 or less).  Are you running into problems with 16GB?
The trouble with the smaller GPUs is likely to be with the categorical encoding.  Although it the limitations can be addressed in the future, this transformation currently requires us to temporaritly hold a significant amount of data in device memory for each categorical column.

Yes, one of my 4 gpus are just 8GB memory size.
I guess I missed the impact of device-limit-fract and part-mem-frac, and I will try more on those settings.
Thanks! I will update it after I got more test results.

retiring this bug


Refactor geo location platform

@bieniu After merging #129 some conflicts needs to be resolved

After merging #129 some conflicts needs to be resolved

Done


Serialize template contents

Template tags require special treatment for their contents to be processed.
A unit test is included for demonstration purposes.
PS: Thanks to the brave team for maintaining this project.
If you could consider this PR I would be so happy!

@fabianbieler do you want to sign your commit, or shall I land it under mine?

Sorry for not reading the contribution requirements properly and thanks for the reminder.
The commit is signed now.


MediaSession subscription

In MediaCompat when subscribing to a MediaSession you would pass a SubscriptionCallback and when unsubscribing you could also pass the same callback.
Now, in Media3 the callback is set only once in the initialization of the MediaSession, so if a caller wants to subscribe to multiple id's he has to know in advance what id's to subscribe to, or you can have a "callback manager" to handle multiple subscriptions.
My target is to be able to get a kotlin flow of all the children which now is quite impossible.
I'm suggesting to pass this callback in the subscribe function.

When you build a MediaBrowser you can pass a MediaBrowser.Listener and build the browser:
MediaBrowser.Builder(this, SessionToken(this, ComponentName(this, MyMediaLibraryService::class.java)))
.setListener(object: Listener {
  override fun onChildrenChanged(
    browser: MediaBrowser,
    parentId: String,
    itemCount: Int,
    params: MediaLibraryService.LibraryParams?
  ) {
      // use the parentId and ask the browser to get the children
      browser.getChildren(parentId, ...)
  }
})
.buildAsync()

An implementer of the MediaLibrarySessionCallback is responsible to call this method when you have subscribed (see JavaDoc of subscribe).
So if I understand correctly you register the listener once when building the browser. The service (MediaLibrarySessionCallback) is then calling that listener with the parentId so that you can get the list of items for that parentId from the browser with browser.getChildren(parentId, ...).
Can you let me know whether I understand the problem correctly and whether this solves the issue for you?

My use case is when a viewmodel wants to subscribe to a parentId of its scope.
With the current state, the viewmodel wouldn't be able to be notified about when a change in the library has occurred (because you only have 1 MediaBrowser.Listener, only the creator of the MediaBrowser will be notified).
My suggestion is to have a SubscriptionCallback class, just as the MediaCompat library.
interface SubscriptionCallback {
   fun onChildrenChange(parentId: String, params: LibraryParams) // Can also be the children directly
}

And the MediaBrowser will look like this:
class MediaBrowser {
   ...
   void subscribe(String parentId, LibraryParams params, SubscriptionCallback callback);

   void unsubscribe(SubscriptionCallback callback);
}

And getting a flow of all the children will look like this:
fun MediaBrowser.getChildrenFlow(parentId: String, params: LibraryParams): Flow<ImmutableList<MediaItem>> = callbackFlow {
   val callback = object : SubscriptionCallback {
      override fun onChildrenChange(parentId: String, params: LibraryParams) {
         launch {
            send(getChildren(parentId, 0, Int.MAX_VALUE, params).get())
         }
      }
   }
   subscribe(parentId, params, callback)

   awaitClose {
      unsubscribe(callback)
   }
}

I hope you it helped you understand my use case better.

Thanks! I'm leaving this open as an enhancement, but I don't expect that these callbacks will be added back to be honest.
I'm not super-familiar with Flow but it appears to me that you may be able to create your own object in between to which you can register with your flow. I appreciate and I haven't tried this but I don't thing this is impossible because you get the callback calls. Sorry for not being able to give you a better answer.

I'm not sure to be honest. I think rather not. The API has moved away from passing callbacks to the  methods to Futures.

Closing due to inactivity.


Setup multiarch CSV file

So the bundle knows about the compatible archs
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains a link to the JIRA issue
[ ] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

/jenkins test


Data retrieval

Different approaches for data retrieval:

aws-sdk
aws REST api use react-query + axios to make calls
aws Amplify

The solution will be used both in #3 and in #9

https://github.com/tannerlinsley/react-query/issues/47#issuecomment-559202942
@Janluke0


Enable/Disable sentry via configuration

Hi,
Currently, there's no option to disable the bundle
So our local tests and our Travis builds are sending exception to Sentry that are useless
Why not provide a configuration option like http://symfony.com/doc/current/components/config/definition.html#optional-sections ?

You can do this by not setting the DSN option in these environments.

Thanks for your reply,
I think this should be mentionned in the README something like
"If the DSN entry is left empty, it will disable sentry"

With all the respect, adding an option and two lines of code will make it looks better.
Disabling plugin and removing DSN options are two different actions. This is not explicit and actually not correct, since no one will remove the string but comment it, which makes config file messy.
My car has neutral gear and I can use it when I want engine on, but car not moving. Highly recommended.

@ryabenko-pro hey, I never said it's a good way to do it :) But it's the one chosen by core devs apparently, and works in the same manner for all SDK's, so if not very sensible, it's at least consistent. I would prefer option to disable as well, however... See #21

@Addvilz, thanks! I'll address this message there then.


[Teva 2384] create pentest application environment

Jira ticket URL

Just add the ticket number to the end:

https://dfedigital.atlassian.net/browse/TEVA-2384
Changes in this PR:
create pentest application environment

Review app deployed to https://teaching-vacancies-review-pr-3265.london.cloudapps.digital


Options specified at method level is not reset in shell mode (via jline3).

Picocli reuse command object when used in interactive mode. While reusing it clears all the instance variable annotated with @Option/@Paramters, but does not reset the options specified at method level. It looks like Picocli does not invokes method annotated with @Option unless the matching option is specified in command line. Due to this, when the command is executed with the option, then instance variable is initialized and next the command is executed without the option, then same value gets visible.
We thought of using default value attribute to get it reset, but unfortunately, in our application, we cannot predefine the default value, thus could not take this approach. Kindly check it.
Example code
package example;

import org.jline.console.SystemRegistry;
import org.jline.console.impl.Builtins;
import org.jline.console.impl.SystemRegistryImpl;
import org.jline.reader.LineReader;
import org.jline.reader.LineReaderBuilder;
import org.jline.reader.MaskingCallback;
import org.jline.reader.Parser;
import org.jline.reader.impl.DefaultParser;
import org.jline.terminal.Terminal;
import org.jline.terminal.TerminalBuilder;
import picocli.CommandLine;
import picocli.CommandLine.Command;
import picocli.CommandLine.Option;
import picocli.shell.jline3.PicocliCommands;
import picocli.shell.jline3.PicocliCommands.PicocliCommandsFactory;

import java.nio.file.Path;
import java.nio.file.Paths;
import java.util.List;
import java.util.function.Supplier;

/**
 * Example.
 */
public class Example {

    /**
     * Top-level command that just prints help.
     */
    @Command(name = "", description = "Example root command.", subcommands = {MyCommand.class})
    static class CliCommands implements Runnable {
        public void run() {
            System.out.println(new CommandLine(this).getUsageMessage());
        }
    }

    /**
     * A command with some options to demonstrate issue.
     */
    @Command(name = "cmd", mixinStandardHelpOptions = true, description = "Example test command.")
    static class MyCommand implements Runnable {
        private List<String> modules;

        @Option(names = "-c", description = "comps", split = ",")
        private List<String> comps;

        public List<String> getModules() {
            return modules;
        }
        @Option(names = "-m", description = "modules", split = ",")
        public void setModules(final List<String> modules) {
            this.modules = modules;
        }
        public void run() {
            System.out.println("Modules = " + modules);
            System.out.println("Comps = " + comps);
        }
    }

    /**
     * Main method.
     * @param args arguments.
     * @throws Exception exception.
     */
    public static void main(final String[] args) throws Exception {
        Supplier<Path> workDir = () -> Paths.get(System.getProperty("user.dir"));
        // set up JLine built-in commands
        Builtins builtins = new Builtins(workDir, null, null);
        // set up picocli commands
        CliCommands commands = new CliCommands();

        PicocliCommandsFactory factory = new PicocliCommandsFactory();

        CommandLine cmd = new CommandLine(commands, factory);
        PicocliCommands picocliCommands = new PicocliCommands(cmd);

        Parser parser = new DefaultParser();
        Terminal terminal = TerminalBuilder.builder().build();
        SystemRegistry systemRegistry = new SystemRegistryImpl(parser, terminal, workDir, null);
        systemRegistry.setCommandRegistries(builtins, picocliCommands);
        LineReader reader = LineReaderBuilder.builder().terminal(terminal).completer(systemRegistry.completer())
                .parser(parser).variable(LineReader.LIST_MAX, 50).build();
        builtins.setLineReader(reader);
        factory.setTerminal(terminal);

        String prompt = "prompt> ";
        String rightPrompt = null;

        // start the shell and process input until the user quits with Ctrl-D
        String line;
        while (true) {
            systemRegistry.cleanUp();
            line = reader.readLine(prompt, rightPrompt, (MaskingCallback) null, null);
            systemRegistry.execute(line);
        }
    }
}

Execution
prompt> cmd
Modules = null
Comps = null
prompt> cmd -c c1 -m m1
Modules = [m1]
Comps = [c1]
prompt> cmd
Modules = [m1]
Comps = null
prompt>

Thank you for raising this.
Thanks for the example code. I used that to add a failing unit test to help debug the issue.
That said, I am currently extremely busy with Log4j, so it may take me a while to get to this.

I did some analysis, here are my observations:
With tracing on, I see the following output for the last run (when cmd is invoked again, but this time without any parameters):
[picocli DEBUG] Initializing command 'null' (user object: picocli.Issue1531ResetOptionMethods$MyCommand@78186a70): 2 options, 0 positional parameters, 0 required, 0 groups, 0 subcommands.
[picocli DEBUG] Set initial value for field java.util.List<String> picocli.Issue1531ResetOptionMethods$MyCommand.comps of type interface java.util.List to null.
[picocli DEBUG] Initial value not available for method void picocli.Issue1531ResetOptionMethods$MyCommand.setModules(java.util.List<String>)
[picocli DEBUG] Applying default values for command '<main class>'
[picocli DEBUG] defaultValue not defined for field java.util.List<String> picocli.Issue1531ResetOptionMethods$MyCommand.comps
[picocli DEBUG] defaultValue not defined for method void picocli.Issue1531ResetOptionMethods$MyCommand.setModules(java.util.List<String>)

Note that the comps field (the -c option) has an initial value, where as the output says "Initial value not available for method (...)setModules". Additionally, neither option has an explicit defaultValue defined in the annotation.
This is the cause: If no explicit defaultValue is defined in the annotation, picocli uses the initial value as the default value.
For annotated fields, it is clear what their "initial value" is. See this example:
class C {

   @Option(names = "-a") int a;       // initial value is primitive int 0 (zero)
   @Option(names = "-b") int b = 123;
   @Option(names = "-c") String c;       // initial value is null
   @Option(names = "-d") String d = "abc";

For annotated methods, it is less clear what the initial value should be, so at the time I decided to do nothing.
This results in annotated methods not getting reset between invocations of parseArgs or execute.
I need to think a bit on what to do. Maybe setting to null, not sure yet.

The solution I am thinking of now requires annotated setter method options to explicitly set defaultValue = Option.NULL_VALUE.
class M {
   String x;
   @Option(names = "-x", defaultValue = Option.NULL) // reset to null between  parseArgs invocations
   void setX(String x) { this.x = x; }
}

Unfortunately this does not work correctly with picocli 4.6.2, this will be fixed in the next release.
@kaushalkumar Does that meet your requirements?

@kaushalkumar I pushed a fix for this to the master branch, can you verify?

This has been fixed in the main branch and the fix will be included in the upcoming picocli 4.6.3 release.
note to self:
TODO: update the user manual with the below

[WARNING]
====
Applications that reuse a single `CommandLine` instance for multiple `parseArgs` invocations should be aware of the following:

Annotated setter method options that explicitly set `defaultValue = Option.NULL_VALUE` will get a call with a `null` parameter when the command line did not include that option.

If the setter method annotation does _not_ explicitly set `defaultValue = Option.NULL_VALUE`, then this method will not be called when the command line did not include that option. This means then the value will retain the value of the previous `parseArgs` invocation, which may not be desirable. (This only happens for applications that reuse a single `CommandLine` instance for multiple `parseArgs` invocations.)

.Java
[source,java,role="primary"]
----
class App {
   String x;
   @Option(names = "-x", defaultValue = Option.NULL) // reset to null when option not specified
   void setX(String x) { this.x = x; }

   String y;
   @Option(names = "-y") // retains value of previous parseArgs invocation when option not specified
   void setY(String y) { this.y = y; }
}
----

.Kotlin
[source,kotlin,role="secondary"]
----
class App {
   var x
   @Option(names = ["-x"], defaultValue = Option.NULL) // reset to null when option not specified
   fun setX(x: String) { this.x = x }

   var y
   @Option(names = ["-y"]) // retains value of previous parseArgs invocation when option not specified
   fun setY(y: String) { this.y = y }
}
----

====

Closing this ticket, the documentation has been updated.


Unclear documentation for link types

Describe the bug
Visiting the Go docs on Link Type, you'll see that the comments are as follows:
const (
    LinkTypeUnspecified LinkType = iota // The relationship of the two spans is unknown.
    LinkTypeChild                       // The current span is a child of the linked span.
    LinkTypeParent                      // The current span is the parent of the linked span.
)

However, I couldn't tell if this was correct looking at how Stackdriver displays it (the wording is strange, it's vague and makes it seem as though using LinkTypeChild presents the linked span as a child of the current). I decided to take a look at some other library docs, and in the Java documentation it appears the definition is the opposite:

CHILD_LINKED_SPAN
When the linked Span is a child of the current Span.
PARENT_LINKED_SPAN
When the linked Span is a parent of the current Span.

To Reproduce
See my above documentation links
Expected behavior
Clarity needed on what is correct, expected behavior shouldn't actually change code-wise, only what choice should be made by the developer
Additional context
N/A

@samuelhorwitz Java definition is correct. i'll fix the go definition.

Fixed with https://github.com/census-instrumentation/opencensus-go/pull/1062.


Exiting python crashes LibTerm

When I exit the python command, LibTerm crashes.
Steps to reproduce:

Open LibTerm
Type "python" then return
Type "quit()" then return
OR
Type "import sys; sys.exit()" then return

Actual behaviour:
LibTerm exits immediately.
Expected behaviour:
python exits, but LibTerm does not.
Diagnostic steps:
The following commands do not crash:
The "Stop" autocompletion above the keyboard in LibTerm when python is open.
Further information:
I am using LibTerm 3.0.1 (3) on iOS 12.1 on an iPad Mini.

Thanks! I will fix it soon.

Don't update LibTerm until the next update: #14

Fixed by 795454c57e80caa78de5145eb502737e900604b3


Take python version as a string and not number?

Untested :S

Sorry resubmitting. Made a silly mistake.


Extract into multiple, more generic, libraries?

@bsbodden and @hsgubert: I'm going to switch gears to some other things for a bit, but I wanted to get your thoughts on the following for when I get some time to come back to the topic of migrations in a few weeks.
It seems to me that this gem has three component parts:

configuration and session management
rails migrations
query helpers

It also seems to me that every application (not just rails applications) needs the first problem solved.
What would y'all think about creating a separate cassandra-configuration gem that could be responsible for management of cassandra.yml and client/cluster/session management best practices?
Short term, cassandra_migrations could depend on and utilize the cassandra-configuration library. I think this simplifies maintenance of this library and benefits the community who are mostly baking their own solutions to the cassandra-configuration problems (that library would allow them to solve the problem in a lightweight and generic way).
Longer term, I think it would make sense to have something like

cassandra-configuration

Standalone configuration and session management
Depends on cassandra-driver

cassandra-migrations

Configurable versioned migration management and DSL
Depends on cassandra-configuration

cassandra-migrations-rails

Rails generators, tasks, and helpers for cassandra migrations the Rails Way
Depends on cassandra-migrations and rails

cassandra-queries

Query abstraction layer for Cassandra Ruby driver
Depends on cassandra-configuration

Thoughts?
cc: #52

This is a really tricky question. There is a trade-off between coherence and simplicity here. When this gem was created, and I and the first users just wanted a good way to integrate cassandra to a rails app. But later many people said they wanted to use a lot of the functionality in non-rails apps, so this is a real need people have.
On the other hand, we also want something easy an appealing for people to try out. When you're looking for a gem the last thing you want is a complex mosaic that you don't fully understand. I mean, one thing is rspec (that everyone knows) and the other is a more obscure/niche gem doing that.
I really don't know the answer and would love to hear other opinions. Currently my opinion is that we should break the gem if this brings benefits to the end user. For example, a version for rails and for non-rails apps is a benefit, as it allows people to use the gem in non-rails apps.
On the other hand, separating configuration/session management from migrations would be good for our internal organization, but can't we simply enforce this organization in our code? Thinking as the end user I think I prefer having a single gem and simply ignoring migrations if I don't want to, than having to understand the boundaries of 2 sub-gems.
That being said It would be great to hear other arguments

I agree with your hesitation. I'm trying to make sure my issue isn't just naming (e.g. If this were named less specifically than cassandra_migrations would I have issue with the multiple responsibilities?).
If the "client" class was designed in a way that the session could be used well outside the context of a migration, I could probably get behind combining configure/session and migrations.
Long term, I feel most strongly about the queries being in another library.
Short term I feel most strongly about allowing ruby users to have a configure/session solution that is designed to be clear and easy to use in their application code.
Thanks for the convo, will keep thinking over the weekend.

On Nov 20, 2015, at 4:11 PM, Henrique Gubert<EMAIL_ADDRESS>wrote:
This is a really tricky question. There is a trade-off between coherence and simplicity here. When this gem was created, and I and the first users just wanted a good way to integrate cassandra to a rails app. But later many people said they wanted to use a lot of the functionality in non-rails apps, so this is a real need people have.
On the other hand, we also want something easy an appealing for people to try out. When you're looking for a gem the last thing you want is a complex mosaic that you don't fully understand. I mean, one thing is rspec (that everyone knows) and the other is a more obscure/niche gem doing that.
I really don't know the answer and would love to hear other opinions. Currently my opinion is that we should break the gem if this brings benefits to the end user. For example, a version for rails and for non-rails apps is a benefit, as it allows people to use the gem in non-rails apps.
On the other hand, separating configuration/session management from migrations would be good for our internal organization, but can't we simply enforce this organization in our code? Thinking as the end user I think I prefer having a single gem and simply ignoring migrations if I don't want to, than having to understand the boundaries of 2 sub-gems.
That being said It would be great to hear other arguments
—
Reply to this email directly or view it on GitHub.

@eprothro @hsgubert I agree with the separation. I was thinking about that. I even have some partial work on a querying + ORMish type of library. I think that we should explore the capabilities of the datastax driver deeper and then see where the holes are and whether the different libraries would have enough to do to be worth writing :-)

Right. I also feel very strongly about separating the querying and ORM. I guess the only reason why this was not done yet is because the current querying/ORM capability is so little that it doesn't justify a gem.
@eprothro I also agree with your short term goal, perhaps we could start with that? Extracting a session/configuration manager that works without rails.

Sounds like the right first step to me.
Next are decisions around naming and interface for a user (unique namespace vs. sharing Cassandra namespace vs. adding functionality to Cassandra module via monkey patch). Will think about these over the Thanksgiving holiday.
A few interface scenarios for which I assume we're all thinking about what the interface should be.
Adding a session attribute, transparently
class SomeQueryClass
  # include Cassandra config/session management methods    < ------ here

  def fetch
    session.execute(some_cql)
    ...
  end
end

Adding a session attribute, with configuration
class SomeDataMapperResourceClass
  # include Cassandra config/session management methods    < ------ here

  # specify which keyspace the session for this class should be connected to < ------ here

  def self.find_by_username(username, opts={})
    session.execute(some_cql)
    ...
  end
end

Getting the cluster config
# some_task.rb
class SomeTask

  def cluster_config
    # get the current cluster connection options     < ------ here
  end
end

Managing the cluster/sessions
# some_initializer_file.rb
SomeForkedProcess.after_fork do
  # Establish unique connection for this process fork      < ------ here
end

@eprothro I think the separations make a lot of sense, but can you clear up what the scope of each gem would be? Would creating the keyspace, updating keyspace settings like RF, updating table settings all be part of cassandra-configuration (or would you have to do another migration using cassandra-migrations to update table settings)? Also what would we do about tunable consistency which can be set on a cluster, data center, or individual reads/writes? Would that be part of cassandra-queries or both cassandra-queries and cassandra-configuration?

@sstgithub Great questions.
I think the configuration gem's responsibility would be managing cluster and session configuration for multiple environments. These cluster and session objects would be instantiated cassandra-driver classes.
In that regard, I would expect to be able to tune consistency of the cluster/dc with just the configuration gem.
I don't think a configuration gem knows anything about a query, directly. So, tuning consistency for a query would be the client's responsibility, or a queries gem's responsibility if the client chose to use that.
The table settings one is an interesting question. I would expect cassandra.yml to describe connection settings. In that regard, something like replication_factor doesn't exactly belong. However, changing a replication factor probably doesn't makes sense as a traditional database (read: schema) migration, since it is something that is not shared across environments (the same way a table name, or column type is).
Currently, I only think replication_factor and class are being used for the cassandra:create task. For now, I would, personally, be ok with removing keyspace options from the cassandra.yml and having this create task simply use the defaults (e.g. simple, 1) and expect that users in production are managing non-schema properties competently.
My question would be "how are people currently managing non-schema database configuration mutations?" (e.g. keyspace properties like RF and Durable Writes, table options like compaction and cacheing).
I assume the answer is "manually" (e.g. tweaking settings and, prayerfully, documenting changes somewhere). If that's the case, I'd love to discuss and come up with a better answer eventually, but I don't know if that is the scope of this initial change.
Thoughts?

@eprothro Apologies for the late reply.
I would say that replication_factor should remain in cassandra.yml as I see cassandra.yml as handling both connection and all other initial settings for the keyspace. Also, I think it might make more sense to use well-separated modules in one gem instead of multiple gems because there will be quite a bit of overlap with the DSL (for instance, defining default consistency level initially in the configuration module and then being able to use a different consistency level with each query in the query module)
As for the non-schema db config mutations, I don't know how others using this gem manage things but we do currently manage most of those manually. It would be great if they were handled by this gem but I agree thats outside the scope of this change.

@sstgithub I've been playing with this, and I agree that a single repo with well organized and properly isolated modules is best. I think my current opinion is that this repo could still contain multiple gems, for those that want to use in isolation (similar to rails with activesupport activemodel, etc).
Regarding db config mutations, we handle these in a separate repo for our infrastructure configuration. I think this is appropriate for now, and I think just mentioning that this is a need that exists and is separate from schema mutations supported by the gem is probably responsible enough.

@sstgithub @hsgubert @bsbodden Wanted to update y'all on this.
Over the last year we've bootstrapped our way into production with Cassandra (went live in December). Along the way it turns out I've crated the libraries that we've discussed in this thread.
https://github.com/eprothro/cassie
https://github.com/eprothro/cassie-rails
In no way am I trying to be "that guy" and say "hey, let's all just use these!".
For now, I just wanted to let y'all know about them, mention that they are in line with a lot of what we've discussed here, and working well for us. I'm 100% open to any comments, questions, nits, or discussions.


Request to bundle fzy-lua

Hi @swarn
I've developed  a Neovim plugin (telescope-words) for searching dictionary and thesaurus entries, and I'd like to bundle fzy-lua with it to improve its functionality. I want to check you are okay with this before I do so.
Thank you for your work on fzy, it's a great library!
Best regards

Looks great, go for it!


[Coverity CID :189517]Control flow issues in /drivers/sensor/fxos8700/fxos8700.c

Static code scan issues seen in File: /drivers/sensor/fxos8700/fxos8700.c
Category: Control flow issues
Function: fxos8700_init
Component: Drivers
CID: 189517
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

False postive as the switch case branch skims through various
WHOAMI register to check for various supported devices.
And @ceolin I think it doesn't violate MISRA-C. Isn't it ?
https://github.com/zephyrproject-rtos/zephyr/issues/9893

It looks like a valid waring.
It violates the MISRA-C
switch (x) {
case 'a':  /* allowed */
case 'b':
do_something();
break;
**case 'c':
do_something_else(); /not allowed /
case 'd':
break;
default:
break;
}


Replace distro type

Removes the distro.Distro object in favor for a new linux.Release struct. The existing distro object takes part of the raw information that is found during analysis and attempts to identify the release relative to a hard-coded enumeration. The remaining raw information discovered is thrown away. There are problems with this:

Syft is meant to raise up as much raw information as possible and attempt not to synthesize data or conclude about interpretations of the data. The distro object is in conflict with this.
Throwing away the unused information from the underlying data source hinders downstream use of such data
Grype is really in need of this distro.Type enumeration, which leads to unnecessary updates of syft to improve grype matches (e.g. adding a new supported distro).

The new linux.Release struct raises up information found in /*/os-release, which is extremely common across all distributions.
This makes a breaking change to the JSON schema, thus, it is being bumped in this PR from 2 to 3. The existing .distro.idLike field  is a string. The underlying field is a space-separated list of distribution names which the current linux release is most close to. This field is being transformed into a list to eliminate the need for downstream consumers to split the field on space before use.
Note: this should not be merged until grype and grype-db branches are available to show correct functionality of the distro type port.
Closes #342

I'm going to hold off on merging this until the sunsetting of grype-db is completed (since this changes the types shared between grype and grype-db)


Upgrade Kiali to support configure istio_component_namespaces

Refer to https://github.com/kiali/kiali/issues/1315
Signed-off-by: Chun Lin Yang<EMAIL_ADDRESS>

@howardjohn please help to review this PR? Thanks.


Allow Elements in arrow texts

Hello!
This PR, allows the use of React elements inside of arrowLeftText and arrowRightText props. Allowing the use of navigation icons for the Carousel.
Example:
import MaterialIcon from 'react-native-vector-icons/MaterialIcons'

<Carousel
  arrows
  leftArrowText={<MaterialIcon name={'keyboard-arrow-left'} />}
  rightArrowText={<MaterialIcon name={'keyboard-arrow-right'} />} >
</Carousel>

+1 🙏

Ping @phil-r

Looks good!
Naming is a bit weird now, I think we'll need to rename leftArrowText to leftArrow and rightArrowText to rightArrow in the future

1 for this


How do I change the link color of a node for which I have id information at a certain moment?

Please describe the feature that you want to propose
My connection type between nodes is gray by default, and I want to instantly change the connection color of a node for which I have id information to a different color. How can I do this?

Do you want to colorize the handles or the connection line? Both things are possible. You can use isValidConnection in combination with the "valid" and "connecting" class names as seen in this example https://reactflow.dev/docs/examples/interaction/validation/ or use useStore in a custom node to access an ongoing connection:
const { nodeId, startHandle } = useStore(s => ({ startHandle: s.connectionStartHandle, nodeId: s.connectionNodeId }))

In v12 we will add a useConnection hook to simplify stuff like this.


AL: Publish Extension without building does not take into account EnvironmentName

Please include the following with each issue:
1. Describe the bug
When I try to debug Installation codeunit on the Sandbox, named other than 'Sandbox' i get an error 'The request for path /v2.0/sandbox/dev/apps?SchemaUpdateMode=synchronize&DependencyPublishingOption=ignore failed with code NotFound. Reason: Not Found'
2. To Reproduce

Create launch.json with the following parameters

       {             "name": "Attach: Microsoft cloud sandbox",             "type": "al",             "request": "attach",             "environmentType": "Sandbox",             "environmentName": "MySandbox",             "breakOnError": true,             "breakOnRecordWrite": false,             "enableSqlInformationDebugger": true,             "enableLongRunningSqlStatements": true,             "longRunningSqlStatementsThreshold": 500,             "numberOfSqlStatements": 10,             "breakOnNext": "WebServiceClient"         },         {             "name": "Publish: Microsoft cloud sandbox",             "type": "al",             "request": "launch",             "environmentType": "Sandbox",             "environmentName": "MySandbox",             "breakOnError": true,             "breakOnRecordWrite": false,             "launchBrowser": true,             "enableSqlInformationDebugger": true,             "enableLongRunningSqlStatements": true,             "longRunningSqlStatementsThreshold": 500,             "numberOfSqlStatements": 10         }

Go to Run and Debug and start "Attach: Microsoft cloud sandbox" session
Run: AL: Publish Extension without building

3. Expected behavior
Sending request to https://api.businesscentral.dynamics.com/v2.0/MySandbox/dev/apps?SchemaUpdateMode=synchronize&DependencyPublishingOption=ignore
4. Actual behavior
Sending request to https://api.businesscentral.dynamics.com/v2.0/sandbox/dev/apps?SchemaUpdateMode=synchronize&DependencyPublishingOption=ignore
5. Versions:

AL Language: v8.1.525271
Visual Studio Code: 1.61.2
Business Central: 19.0.29884.30390

Final Checklist
Please remember to do the following:

[X ] Search the issue repository to ensure you are reporting a new issue

[X ] Reproduce the issue after disabling all extensions except the AL Language extension

[ X] Simplify your code around the issue to better isolate the problem

I have a fix on the way for this. As a workaround until we release a new VSIX, you can use the old sandboxName property in your launch.json instead.

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 31908 and VS Code Extension Version 9.0.537507.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/


Want to install on my localhost

I need token as we getting error during installation http://prntscr.com/k8c2ja. Please help me asap

Closing as the repo is not maintained anymore.


Change Regex match to StatusCode comparison for UI error translation (common.ErrorMessageForUI)

common.ErrorMessageForUI is using regex on message to translate APIErrors. Instead, use the status code which is part of the APIError.

Kosi might take this one

Sure, @suprjinx  will work on this

@suprjinx on this task how do I determine what string should be returned based on the input status code

Also after I change the way the function operates, I would have to change the places they are called. It would be helpful if you could provide a mapping of status codes (or ranges) to messages

Going through the tests, I guess what is need to know is the status code for uniqueError and validationError

The Validation error should have the type api.ErrorResponse and contain StatusCode == http.StatusBadRequest (400). The Unique constraint violation may have a recognizable type but if not it probably needs to continue using the regex.

func (c Controller) renderIndex(ctx *fiber.Ctx, msg string) error {
	namespaces, err := c.namespaceService.ListNamespaces(ctx.Context())
	if err != nil {
		return ctx.Render("namespaces/index", fiber.Map{
			"Namespaces": namespaces,
			"Status":     StatusError,
			"Message":    common.ErrorMessageForUI("namespace", err.Error()),
		})
	}
	return ctx.Render("namespaces/index", fiber.Map{
		"Namespaces": namespaces,
		"Status":     StatusSuccess,
		"Message":    msg,
	})
}

Hey @suprjinx I was working on this PR and I'm wondering which variable I can get the status code from, the 'StatusError' variable is a fixed string, so I'm wondering where I can get the actual integer code from


Added Jetbrains IDEs

Added all professional IDEs based on IntelliJ platform + fixed alphabetical order for Android Studio

Thanks for the PR. Merged.


Adding solution of missing number using cpp

Missing number found using Gauss Formula.
Complexity Analysis : O(n) Time Complexity and O(1) Space Complexity.
Pull Request Template
What have you Changed(must)
Write here what you have changed in the codebase
Issue no.(must) -
Pr will be close and marked as spam. If issue number not found or issue was assigned to someone else.
Marking as spam can block your account from HacktoberFest.
Self Check(Tick After Making pull Request)

[ ] This issue was assigned to me if not it will be marked as spam.
[ ] My file is in the proper folder
[ ] I am following clean code and Documentation.
[x] I have added the title and what program will do first in the file
[ ] I have named the file as (Problem #). (Problem Title(in Camel Case)).(extension)
ex. 2. AddToNumbers.py

README - How to Contribute

Create an Issue and get assigned to it before making any Pull request


Ordered lists are not aligned properly when exported to PDF

When building the docs using mkdocs-with-pdf, the ordered lists appear far left than where they are supposed to be.
Here is what my markdown file looks like:
When SFTech is being setup for the first time, there are three phases of setup that need to be completed.

1. Login with the default `admin` user and then create new password for it.
2. Set the following parameters for the system:

    a. Impact Assessment Date
    b. Compounding frequency to be used. (Compounding daily or compounding each interval)
    c. Computaion model (Retrospective, Modified Retrospective or Prospective)

These steps are described in detail in the sections that follow.

When viewed on browser, the alignment of ordered list is correct:

But when exported to PDF, the alignment of ordered list is not correct:

Here is my mkdocs.yml file:
site_name: SFTech Docs
site_url: https://sftechtepal.com/docs
site_description: The official documentation of SFTech
site_author: SFTech
copyright: Copyright © 2022 Supreme Fintech Private Limited
docs_dir: docs

nav:
  - Home: index.md
  - Setup: setup.md
  - Dashboard: dashboard.md
  - Authentication: authentication.md
  - Leases: leases.md
  - Reports: reports.md
  - Approvals: approvals.md
  - User Management: user_management.md

theme:
    name: material
    logo: assets/img/sft_logo_white.svg
    favicon: assets/img/favicon.ico
    font:
        text: Nunito
    palette:
      - scheme: default
        primary: deep orange
        toggle:
            icon: material/brightness-4
            name: Switch to dark mode
      - scheme: slate
        primary: deep orange
        toggle:
          icon: material/brightness-7
          name: Switch to light mode
    features:
      - toc.integrate
      - navigation.top
      - search.suggest

markdown_extensions:
    - toc:
        permalink: "#"

plugins:
  - search
  - with-pdf

The following were used when this issue appeared:
mkdocs-with-pdf: 0.9.3
macOS Big Sur 11.6

Encountering the same problem.

Fix:
add the ol to "content indent" in mkdocs_with_pdf/themes/material.scss in line 69

    &>ul,
    &>ol {
      margin-left: 1.5rem;
    }


Add SHA3 to the list of supported hard binding hashes

From the JPEG Fake Media Group

Section 12.1 explicitly says that you can use SHA2: 256, 384, and 512 bits. It explicitly calls this "The allowed list".
What about anything from SHA3? (SHA3 became a NIST standard in 2015.)

TWG agrees to add a note about why it is not included.


Hugo error

hugo reports the error:
hugo server -D
ERROR 2021/01/08 13:57:25 Failed to read Git log: fatal: twoja obecna gałąź „master” nie ma jeszcze żadnych zapisów
ERROR 2021/01/08 13:57:25 render of "page" failed: execute of template failed: template: _default/single.html:5:7: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/noiro/Projekty/Hugo projekty/test/themes/hugo-geekdoc/layouts/partials/head.html:18:29": execute of template failed: template: partials/head.html:18:29: executing "partials/head.html" at <index .Site.Data.assets "main.min.css">: error calling index: index of untyped nil
ERROR 2021/01/08 13:57:25 render of "page" failed: execute of template failed: template: _default/single.html:5:7: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/noiro/Projekty/Hugo projekty/test/themes/hugo-geekdoc/layouts/partials/head.html:18:29": execute of template failed: template: partials/head.html:18:29: executing "partials/head.html" at <index .Site.Data.assets "main.min.css">: error calling index: index of untyped nil
ERROR 2021/01/08 13:57:25 render of "page" failed: execute of template failed: template: _default/single.html:5:7: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/noiro/Projekty/Hugo projekty/test/themes/hugo-geekdoc/layouts/partials/head.html:18:29": execute of template failed: template: partials/head.html:18:29: executing "partials/head.html" at <index .Site.Data.assets "main.min.css">: error calling index: index of untyped nil
ERROR 2021/01/08 13:57:25 render of "page" failed: execute of template failed: template: posts/single.html:5:7: executing "posts/single.html" at <partial "head" .>: error calling partial: "/home/noiro/Projekty/Hugo projekty/test/themes/hugo-geekdoc/layouts/partials/head.html:18:29": execute of template failed: template: partials/head.html:18:29: executing "partials/head.html" at <index .Site.Data.assets "main.min.css">: error calling index: index of untyped nil
Built in 102 ms
Error: Error building site: failed to render pages: render of "page" failed: execute of template failed: template: _default/single.html:5:7: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/noiro/Projekty/Hugo projekty/test/themes/hugo-geekdoc/layouts/partials/head.html:18:29": execute of template failed: template: partials/head.html:18:29: executing "partials/head.html" at <index .Site.Data.assets "main.min.css">: error calling index: index of untyped nil
noiro@debian:~/Projekty/Hugo projekty/test$

the page does not have any content yet
theme added as submodule
git submodule add https://github.com/thegeeklab/hugo-geekdoc themes/hugo-geekdoc

Please take a look at the documentation or README. If you want to use the git repo directly you have to run gulp first to preprocess required assets.

Please take a look at the documentation or README. If you want to use the git repo directly you have to run gulp first to preprocess required assets.

Ah thanks. Sorry for the confusion

Ah thanks. Sorry for the confusion

No worries. Please let us know if you have any other problems.

No worries. Please let us know if you have any other problems.


Add support for _COARSE clocks

Original idea does not work, so I'm just going to try expanding support to include the _COARSE clocks.
The original motivation for this PR is that the test suite for the crate minstant reports UB, because it tries to use a clock type Miri didn't support, but never checked for an error code and so just used the uninit libc::timespec. So, that's technically a bug in minstant, but outside of Miri you'd have to be using an incredibly old Linux to ever see an EINVAL so the more helpful thing for Miri to do is behave like a newer Linux.
So now we don't detect UB in minstant, but we have a test failure:
failures:

---- src/instant.rs - instant::Instant::as_unix_nanos (line 150) stdout ----
Test executable failed (exit status: 101).

stderr:
thread 'main' panicked at 'assertion failed: (instant.as_unix_nanos(&anchor) as i64 - expected as i64).abs() < 1_000_000', src/instant.rs:11:1

I'm having trouble getting my head around the code in minstant that's involved in this test, but as far as I can tell from the man pages, these _COARSE clocks meet the requirements.
Closes https://github.com/rust-lang/miri/issues/1983 at least as best as I can.

So the idea is that we just implement the _COARSE clock the same way as the "regular" one, since the only difference is "it's faster" and Miri doesn't implement that part of the spec anyway? Makes sense.

@bors r+

:pushpin: Commit ba9391334e8d23261eb09ce7162015993f7c2aa3 has been approved by RalfJung

:hourglass: Testing commit ba9391334e8d23261eb09ce7162015993f7c2aa3 with merge 57d8206093aaa877c01258a55455aad41ec7d99e...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 57d8206093aaa877c01258a55455aad41ec7d99e to master...


update engine types validator for AWS::RDS::DBInstance

update the RDS custom types for the validator:  https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbinstance.html

Thanks!


Unable to dynamically generate .env file in Spring Boot java application

What problem does this feature solve?
Say you are wrapping Vuejs in a Spring Boot application and deploying it as a Jar file within a docker container and being served as a microservice. By restricting developers to place their .env file within the project root you are preventing the ability to modify that or dynamically generate env vars post deployment due to the fact that the .env file is now trapped inside of a read-only jar file. I cannot generate the .env file during CI/CD build pipelines due to pipelines not having access to protected configuration server apps. I need to be able to modify .env post deployment and that isn't possible under these constraints.
I understand the philosophy of wanting all project file structures to be uniform, but in this scenario it breaks functionality. If you deploy the app as a jar file you would need to be able to access and modify the .env file from outside the jar file, but you can't because Vuejs doesn't allow it. I've read and done lots of research but I cannot figure out how to override the .env path and it sounds like it's a design feature. Am I missing something?
What does the proposed API look like?
Allow developers to override the default .env file path like webpack-dotenv allows:
webpackConfig: {
    plugins: [
      new dotenvWebpack({
        path: path.resolve(__dirname, '/root/.env')
      })
    ]
  }

Hi there, @macfisher
I kind of see your point, but want to clarify something with you first, before talking about adding some feature for this.
Question: Why do you want  or need to add a dynamic .env file instead of using actual environment variables?
The reason I am asking is that generally, in my understanding, it's recommended to not use .env files in production, especially for sensitive content like API keys and stuff like that, which I think about when hearing the need for a "dynamic" env file.
But I may be missing the use case, so can you clarify?

I need to be able to deploy a generic image that can retrieve its authentication variables when it is deployed. I do not want to have separate images for each environment that we have, i.e. Test, Production, Development etc.
To your point that I should not be doing this... why then is there a concept of the .env.local file that is git ignored? I may be missing something but I do not see an issue with having a dynamically generated .env file that only lives within the lifecycle of that image and is not committed to any source repository.
Again, if I have an external configuration server that allows the application to talk to it and get its env variables based on its environment that it is deployed to, I am currently not able to do that if I cannot move the .env file outside of the project root directory.

Not sure if we are talking past each other.
Are you aware that Vue cli also accepts wnv variables from the system itself, not just from the env files?
I was referring to setting the env variables on the system (I think for docker one uses the -e flag to set an environment variable in the container process, right?
That way, the no sensitive data is being saved in an file and the app can access them just the same, the same rules apply (VUE_APP_* variables are passed into the webpack bundle etc.)

Thank you @LinusBorg for taking the time. I had tried to do that via a Java library but it must have set the environment variable for the Java environment and Vuejs didn't know about it but I was getting a false positive because Java could read it and Vue couldn't so I apologize for making the incorrect assumption. You've been a huge help. I can close this request as this was 100% user error.


Side: feel free to commit to master directly :wink:

Fix #15


fix: disable self signed jwt if credentials provided

For debugging

I'm going to close this PR but please re-open it if you need to do more testing.


 Code: 22'" when trying to start recording with instruments?
Happens on device only right now (actually running on simulator causes a different error: "Assertion failure in -PINDiskCache dealloc, .../Pods/PINCache/Source/PINDiskCache.m:91"). Normal run of application is without issues.

@BaranEm Interesting! I haven't seen anything like that. Does this make it so you're not able to instrument your app?


The regex_replace call fails when nsds are not defined

On the master branch, when I'm running without NSD defined, I hit this :
TASK [core/cluster : storage | Find defined NSDs] ******************************
fatal: [worker0]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'nsd'\n\nThe error appears to be in '/root/ibm-spectrum-scale-install-infra/roles/core/cluster/tasks/storage.yml': line 46, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: storage | Find defined NSDs\n  ^ here\n"}
fatal: [worker1]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'nsd'\n\nThe error appears to be in '/root/ibm-spectrum-scale-install-infra/roles/core/cluster/tasks/storage.yml': line 46, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: storage | Find defined NSDs\n  ^ here\n"}
fatal: [worker2]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'nsd'\n\nThe error appears to be in '/root/ibm-spectrum-scale-install-infra/roles/core/cluster/tasks/storage.yml': line 46, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: storage | Find defined NSDs\n  ^ here\n"}
fatal: [worker3]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'nsd'\n\nThe error appears to be in '/root/ibm-spectrum-scale-install-infra/roles/core/cluster/tasks/storage.yml': line 46, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: storage | Find defined NSDs\n  ^ here\n"}

This seems to be caused by this line https://github.com/IBM/ibm-spectrum-scale-install-infra/blob/master/roles/core/cluster/tasks/storage.yml#L49 which I made before we pushed the code into the public space.
I will submit a PR to delete that.

@rajan-mis  This looks like it was changed in dev with this commit: https://github.com/IBM/ibm-spectrum-scale-install-infra/commit/97342c0d955c4860cfe068d1dd8bd59e06be7da8#diff-2c97743adfcca6c87771122a2c6a5f6d
Is there any issue in putting that change into master?  The reason is that master branch is broken currently.   I will submit a pull request that just removes the regex_replace to fix master.


Allow user to extends and define how the redirect path/process should work.

Signed-off-by: crynobone<EMAIL_ADDRESS>

[Current coverage][cc-pull] is 100%

No coverage report found for master at 14b8386.

Powered by Codecov. Last updated by [14b8386...15480a0][cc-compare]
[cc-base-branch]: https://codecov.io/gh/mpociot/reauthenticate/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/mpociot/reauthenticate/compare/14b8386b458862afbd74931b2784b2da5208304c...15480a028fad98a32aeeeb28bc1f368353d89ef1?src=pr
[cc-pull]: https://codecov.io/gh/mpociot/reauthenticate/pull/15?src=pr


The Tip URL is no longer resolving

On the section for "Apply updates automatically from an on-premises location to Office 365 ProPlus", the URL for the Tip is no longer valid.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d68af5b0-45f7-53db-8cee-f03a9ce8bd9b
Version Independent ID: f94fd8f0-6a0f-7eda-f87d-ad904a9e62f7
Content: Choose how to manage updates to Office 365 ProPlus
Content Source: DeployOffice/choose-how-to-manage-updates-to-office-365-proplus.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@kyjeeper  -- thanks for pointing that out.   We'll remove that Tip from the article. Thanks for the feedback.

Tip removed from the article.


Time zone support

Is there a way to specify the time zone of the application globally or component by component? Thanks!

Not via the Dashboard, but you can manually edit the app/config/app.php configuration file. We're going to add a panel for managing that kind of stuff though.

Duplicate of #281.


El Captain required?

My mac OS version is Yousemite and do not support Metal.
Do we need El Captain to run this library on iOS?
Thank you for providing such an awesome library!

I'm using El Capitan myself, and are (currently) not attempting to make things run on older OS X versions. But that might change at a later stage.


daemon/graphdriver/aufs fix lint errors/warnings

Addresses #14756
Signed-off-by: Srini Brahmaroutu<EMAIL_ADDRESS>

LGTM

LGTM


Incorrect attribute in example

File: docs/reference/pkg/python/pulumi_aws/elasticsearch/_index.md
argument: cluster_config
should have attribute Instance_type not cluster_config
Bad:
example = aws.elasticsearch.Domain("example",
cluster_config={
"cluster_config": "r4.large.elasticsearch",
},
Good:
example = aws.elasticsearch.Domain("example",
cluster_config={
"instance_type": "r4.large.elasticsearch",
},
Reference:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticsearch_domain

This should no longer be an issue once https://github.com/pulumi/docs/issues/4071 is complete.

This should no longer be an issue once https://github.com/pulumi/docs/issues/4071 is complete.


Slider previous and next

Hi
How would go about implementing a slider. Can I pass in something to apply a reversed animation when the I click there previous button?
Cheers
Olaf

Hi Olaf,
Yep - check out this site which does exactly that https://www.neue-london.com/collections/ss16?dir=previous
Here is the snippet I'm using:
data: {
    'gsapifyRouter.collections':
      enter: {
        'in': function ($state, $stateParams) {
          if ($stateParams.dir === 'next') {
            return {
              transition: 'slideLeft',
              priority: 3
            };
          } else {
            return {
              transition: 'slideRight',
              priority: 3
            };
          }
        },
        'out': function ($state, $stateParams) {
          if ($stateParams.dir === 'next') {
            return {
              transition: 'slideRight',
              priority: 3
            };
          } else {
            return {
              transition: 'slideLeft',
              priority: 3
            };
          }
        }
      }
    }
}

In the links (ui-sref directive) I'm setting the next/previous parameter.
Hope that helps.
James

Hi James,
Great, thank you.
Cheers
Olaf
On 11 Mar 2016, at 16:10, James Homer <notifications<EMAIL_ADDRESS>wrote:
Hi Olaf,
Yep - check out this site which does exactly that https://www.neue-london.com/collections/ss16?dir=previous
Here is the snippet I'm using:
data: {
'gsapifyRouter.collections':
enter: {
'in': function ($state, $stateParams) {
if ($stateParams.dir === 'next') {
return {
transition: 'slideLeft',
priority: 3
};
} else {
return {
transition: 'slideRight',
priority: 3
};
}
},
'out': function ($state, $stateParams) {
if ($stateParams.dir === 'next') {
return {
transition: 'slideRight',
priority: 3
};
} else {
return {
transition: 'slideLeft',
priority: 3
};
}
}
}
}
}
In the links (ui-sref directive) I'm setting the next/previous parameter.
Hope that helps.
James
—
Reply to this email directly or view it on GitHubhttps://github.com/homerjam/angular-gsapify-router/issues/23#issuecomment-195430844.


texlive: new mirror with upstream revisions

Motivation for this change
Provided mirrors do not contain revisions used by upstream. As a result we have a lot 404 error and long time waiting during i/o operations. New mirror allows to speed up build process and eliminates 404 errors related to texlive
Things done

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

[X] NixOS
[X] macOS
[X] other Linux distributions

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

would be nice to add a description of the mirror (who maintains it etc?) in the commit

would be nice to add a description of the mirror (who maintains it etc?) in the commit

Done

https://ftp.heanet.ie/mirrors/ctan.org/tex/systems/texlive/tlnet/archive

This is not a good stable mirror for texlive 2019-final, I believe. Even if it serves relevant tarballs now, they will be removed eventually.

Provided mirrors do not contain revisions used by upstream.

This is not entirely true. Some of the recent tarballs have the version. I was going to remove the revision attribute for those downloads that don't have the revision.

@fomichevmi Thanks for bringing this up. I've disabled revisioned tarballs for now. We will use those again starting texlive 2020.


Adding logseq-lilypond as a new plugin

Submit a new Plugin to Marketplace
Plugin Github repo URL: https://github.com/dot-asterisk-nl/logseq-lilypond
Github releases checklist

[x] a legal package.json file.
[x] a valid CI workflow build action for Github releases. (Optional for theme plugin only).
[x] a release which includes a release zip pkg from a successful build.
[x] a clear README file, ideally with an image or gif showcase. (For more friendly to users, it is recommended to have English version description).
[x] a license in the LICENSE file.

Hi @Vaults A helpful PR is pending https://github.com/dot-asterisk-nl/logseq-lilypond/pull/1

Hi @xyhp915, thanks for helping out :) It's merged!

Is there anything else I need to do?

Is there anything else I need to do?

Weirdly, the entry file path is still index.html

Also, I found the latest build CI script is not correct...
https://github.com/dot-asterisk-nl/logseq-lilypond/actions/runs/4308177998/workflow#L27


Enable external integration

In order for the autograder to be useful to external people, it is necessary to be able to depend on the autograder code from external projects.
It would be nice to have an example of such integration and a how-to guide too.

This has been enabled after a series of commits at 2f32566d7de59263ae80984cbf7d80cf6bceb4f5


Monochromatic SVGR icon

💬 Questions and Help
I'd like to add SVGR's icon to simpleicons.org which is a collection of high-quality monochromatic SVG icons of popular brands. When attempting to convert SVGR's icon to a monochromatic version, I stumbled over the embedded base64-encoded PNG in the center which is difficult to vectorize and make monochromatic.
What is the source of that PNG and is there also an SVG version (ideally a monochromatic one)?

Hello @sisp, I am afraid I don't have one. The logo is complex and was quickly made.

I see. Would you be open to a revision of the logo? Off the top of my head, I'd find a combination of the React logo and the SVG logo fitting for SVGR, e.g. the SVG logo could be in the center of the React ellipses, or a combination of the two logos similar to React Bootstrap's logo. Or if you like the lion (I believe that's the PNG image), perhaps we could find a vector image of a similar one? What do you think?

Creating a new logo would be great! I love the idea! I will just give you the history of the actual logo:

Take the SVGO logo (it was a tiger)
Add React logo behinds it

That's it!
Now the SVGO logo is no longer a tiger, I kind of like the lion but it could be vectorized in some way. I am open to proposals 😁

Thanks for the hints regarding the history of the current logo!
I tried to find the tiger in SVGO's Git history but couldn't find it even many years ago. Do you know a source of the SVGO tiger logo?

It was this one if I remember well.

https://upload.wikimedia.org/wikipedia/commons/f/fd/Ghostscript_Tiger.svg