text:
Error on AP score after training/evaluation on SecCas

Had this problem after I train, not sure why does the AP are 0

The error you show here is related to the calculation of COCO AP, which is not necessary since we only care about KITTI evaluation metric, you could simpley delete or comment the lines ''result = get_coco_eval_result(gt_annos, dt_annos, class_names)'' and related variables ('result') in trian.py (I remembered there are three places). But this error is not related to 0.0 AP issue, I guess the 0.0 AP issue is related to the evaluation script and/or the pickle info files or others. The size of "kitti_infos_train.pkl" is 12598018 bytes, "kitti_dbinfos_train.pkl" is 6983252 bytes, "kitti_infos_val.pkl" is 13016563 bytes, you could compare yours with these and see if they have been downloaded correctly. Did you modify the other places of the code? If you could sent me your train.py, config file, and /CLOCs/second/utils/eval.py,  I could have a look and see what I can do.

All 3 .pkl files were correctly downloaded. I only modified the codes for the directories. Do I have to write another function for kitti_eval?

Hi Su Pang, this is still the results I've gotten from running SecCas Pretrained:

These are the modifications that I have made for train.py as mentioned in the email:

But still, these are the results that I got:

Could you show me all the output from your terminal, it looks like something happens in eval.py.

Predict_test:  False
sparse_shape: [  41 1600 1408]
num_class is : 1
load existing model
Restoring parameters from /hpctmp/e0318980/CLOCs/model_dir/voxelnet-30950.tckpt
load existing model for fusion layer
Restoring parameters from /hpctmp/e0318980/CLOCs/model_dir/CLOCs_SecCas_pretrained/fusion_layer-11136.tckpt
remain number of infos: 3769
Generate output labels...
/hpctmp/e0318980/CLOCs/second/core/geometry.py:146: NumbaWarning:
Compilation is falling back to object mode WITH looplifting enabled because Function "points_in_convex_polygon_jit" failed type infe              rence due to: No implementation of function Function(<built-in function getitem>) found for signature:

 >>> getitem(array(float32, 3d, C), Tuple(slice<a:b>, list(int64)<iv=None>, slice<a:b>))

There are 22 candidate implementations:
   - Of which 20 did not match due to:
   Overload of function 'getitem': File: <numerous>: Line N/A.
     With argument(s): '(array(float32, 3d, C), Tuple(slice<a:b>, list(int64)<iv=None>, slice<a:b>))':
    No match.
   - Of which 2 did not match due to:
   Overload in function 'GetItemBuffer.generic': File: numba/core/typing/arraydecl.py: Line 162.
     With argument(s): '(array(float32, 3d, C), Tuple(slice<a:b>, list(int64)<iv=None>, slice<a:b>))':
    Rejected as the implementation raised a specific error:
      TypeError: unsupported array index type list(int64)<iv=None> in Tuple(slice<a:b>, list(int64)<iv=None>, slice<a:b>)
  raised from /home/svu/e0318980/.local/lib/python3.6/site-packages/numba/core/typing/arraydecl.py:69

During: typing of intrinsic-call at /hpctmp/e0318980/CLOCs/second/core/geometry.py (162)

File "../core/geometry.py", line 162:
def points_in_convex_polygon_jit(points, polygon, clockwise=True):
    <source elided>
        vec1 = polygon - polygon[:, [num_points_of_polygon - 1] +
                                 list(range(num_points_of_polygon - 1)), :]
                                 ^

  @numba.jit
/hpctmp/e0318980/CLOCs/second/core/geometry.py:146: NumbaWarning:
Compilation is falling back to object mode WITHOUT looplifting enabled because Function "points_in_convex_polygon_jit" failed type i              nference due to: Cannot determine Numba type of <class 'numba.core.dispatcher.LiftedLoop'>

File "../core/geometry.py", line 170:
def points_in_convex_polygon_jit(points, polygon, clockwise=True):
    <source elided>
    cross = 0.0
    for i in range(num_points):
    ^

  @numba.jit
/home/svu/e0318980/.local/lib/python3.6/site-packages/numba/core/object_mode_passes.py:152: NumbaWarning: Function "points_in_convex              _polygon_jit" was compiled in object mode without forceobj=True, but has lifted loops.

File "../core/geometry.py", line 157:
def points_in_convex_polygon_jit(points, polygon, clockwise=True):
    <source elided>
    # first convert polygon to directed lines
    num_points_of_polygon = polygon.shape[1]
    ^

  state.func_ir.loc))
/home/svu/e0318980/.local/lib/python3.6/site-packages/numba/core/object_mode_passes.py:162: NumbaDeprecationWarning:
Fall-back from the nopython compilation path to the object mode compilation path has been detected, this is deprecated behaviour.

For more information visit https://numba.pydata.org/numba-doc/latest/reference/deprecation.html#deprecation-of-object-mode-fall-back              -behaviour-when-using-jit

File "../core/geometry.py", line 157:
def points_in_convex_polygon_jit(points, polygon, clockwise=True):
    <source elided>
    # first convert polygon to directed lines
    num_points_of_polygon = polygon.shape[1]
    ^

  state.func_ir.loc))
/home/svu/e0318980/.local/lib/python3.6/site-packages/numba/core/typed_passes.py:316: NumbaPerformanceWarning:
The keyword argument 'parallel=True' was specified but no transformation for parallel execution was possible.

To find out why, try turning on parallel diagnostics, see https://numba.pydata.org/numba-doc/latest/user/parallel.html#diagnostics f              or help.

File "../utils/eval.py", line 127:
@numba.jit(nopython=True,parallel=True)
def build_stage2_training(boxes, query_boxes, criterion, scores_3d, scores_2d, dis_to_lidar_3d,overlaps,tensor_index):
^

  state.func_ir.loc))
/home/svu/e0318980/.local/lib/python3.6/site-packages/numba/core/typed_passes.py:316: NumbaPerformanceWarning:
The keyword argument 'parallel=True' was specified but no transformation for parallel execution was possible.

To find out why, try turning on parallel diagnostics, see https://numba.pydata.org/numba-doc/latest/user/parallel.html#diagnostics f              or help.

File "../utils/eval.py", line 231:
@numba.jit(nopython=True, parallel=True)
def d3_box_overlap_kernel(boxes, qboxes, rinc, criterion=-1):
^

  state.func_ir.loc))
[100.0%][===================>][8.58it/s][09:38>00:00]
generate label finished(6.51/s). start eval:
validation_loss: 0.0
avg example to torch time: 1.877 ms
avg prep time: 31.322 ms
/home/svu/e0318980/.local/lib/python3.6/site-packages/numba/core/typed_passes.py:316: NumbaPerformanceWarning:
The keyword argument 'parallel=True' was specified but no transformation for parallel execution was possible.

To find out why, try turning on parallel diagnostics, see https://numba.pydata.org/numba-doc/latest/user/parallel.html#diagnostics f              or help.

File "../utils/eval.py", line 231:
@numba.jit(nopython=True, parallel=True)
def d3_box_overlap_kernel(boxes, qboxes, rinc, criterion=-1):
^

  state.func_ir.loc))
Car AP@0.70, 0.70, 0.70:
bbox AP:0.00, 0.00, 0.00
bev  AP:0.00, 0.00, 0.00
3d   AP:0.00, 0.00, 0.00
Car AP@0.70, 0.50, 0.50:
bbox AP:0.00, 0.00, 0.00
bev  AP:0.00, 0.00, 0.00
3d   AP:0.00, 0.00, 0.00

Car AP@0.70, 0.70, 0.70:
bbox AP:0.00, 0.00, 0.00
bev  AP:0.00, 0.00, 0.00
3d   AP:0.00, 0.00, 0.00
Car AP@0.70, 0.50, 0.50:
bbox AP:0.00, 0.00, 0.00
bev  AP:0.00, 0.00, 0.00
3d   AP:0.00, 0.00, 0.00

I am observing the same behavior. Where should the highlighted changes be made?


text:
Feature/improve UI home page

Improve overall get started page UI.
Show nearby queues based on user current location.
Show top 3 featured restaurant queues.
Show top 3 featured general queues
Show top 3 featured hospital queues
Show top 3 featured bank queues

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 16.86747% with 69 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

participant/views.py
12.19%
36 Missing :warning:

manager/models.py
21.42%
33 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Flag
Coverage Δ

unittests
35.64% <16.86%> (-0.70%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines
Coverage Δ

participant/urls.py
100.00% <ø> (ø)

manager/models.py
44.66% <21.42%> (-3.66%)
:arrow_down:

participant/views.py
34.92% <12.19%> (-3.49%)
:arrow_down:

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

start page so cool krubb

Nice work.

source: gharchive/pull-request

authors: codecov-commenter gooddinosaur pannlnwza tanasatit

repo: pannlnwza/queue-management

license: MIT

license_type: permissive

license_source: github-api


text:
Error TS2304 on files from node_modules

TSLint for some reason checks files from node_modules and throws errors.
gulp-tslint version: 8.1.2
tslint version: 5.9.1
Operating system: iOS
Example gulp configuration:
gulp.task('check-ts', function () {
    return gulp.src(paths.ts)
        .pipe(tslint({
            formatter: 'verbose'
        }))
        .pipe(tslint.report({
            emitError: false
        }));
});

tslint.json
{
    "rules": {
        "no-duplicate-variable": true,
        "no-unused-variable": [
            true
        ]
    },
    "rulesDirectory": [
        "node_modules/tslint-eslint-rules/dist/rules"
    ]
}

tsconfig.json
{
    "compileOnSave": false,
    "compilerOptions": {
        "allowSyntheticDefaultImports": true,
        "declaration": true,
        "emitDecoratorMetadata": true,
        "experimentalDecorators": true,
        "module": "es2015",
        "moduleResolution": "node",
        "sourceMap": true,
        "target": "es5"
    },
    "exclude": [
        "node_modules"
    ],
    "files": [
        "select-searchable.ts",
        "source/select-searchable.module.ts",
        "source/select-searchable.component.ts",
        "source/select-searchable-page.component.ts"
    ]
}

Error console output:
[10:14:10] Finished 'check-ts' after 222 ms
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/common/src/directives/ng_class.d.ts(48,34): error TS2304: Cannot find name 'Set'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/core/src/change_detection/differs/default_iterable_differ.d.ts(12,32): error TS2304: Cannot find name 'Iterable'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/core/src/change_detection/differs/default_keyvalue_differ.d.ts(24,16): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/core/src/change_detection/differs/default_keyvalue_differ.d.ts(32,16): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/core/src/change_detection/differs/iterable_differs.d.ts(14,48): error TS2304: Cannot find name 'Iterable'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/core/src/change_detection/differs/keyvalue_differs.d.ts(22,18): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/core/src/di/reflective_provider.d.ts(87,123): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/core/src/di/reflective_provider.d.ts(87,165): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/platform-browser/src/browser/browser_adapter.d.ts(79,33): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/platform-browser/src/dom/dom_adapter.d.ts(97,42): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/platform-browser/src/dom/shared_styles_host.d.ts(11,30): error TS2304: Cannot find name 'Set'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/@angular/platform-browser/src/dom/shared_styles_host.d.ts(22,30): error TS2304: Cannot find name 'Set'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/ionic-angular/util/module-loader.d.ts(13,14): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/ionic-angular/util/module-loader.d.ts(14,18): error TS2304: Cannot find name 'Map'.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/rxjs/Observable.d.ts(59,60): error TS2693: 'Promise' only refers to a type, but is being used as a value here.
/Users/evgenii/Documents/Apps/ionic-select-searchable/node_modules/rxjs/Observable.d.ts(74,59): error TS2693: 'Promise' only refers to a type, but is being used as a value here.

Did you try using linterOptions.exclude in tslint.json?
https://palantir.github.io/tslint/usage/configuration/

source: gharchive/issue

authors: eakoriakin panuhorsmalahti

repo: panuhorsmalahti/gulp-tslint

license: mit

license_source: bigquery


text:
Package the proper files for the new SDKs

The latest code in the developer branch is using the new SDKs for Service Bus, Relay and Event Hubs. These dlls and most likely some of their dependencies need to be included when releasing.

To find out which files are needed I intend to test SBE on the latest release of the following OSes:

Windows 10
Windows Server 2016
Windows Server 2019

I know that Windows 7 and 8.1 are missing. If anyone wants to run SBE on any of those OSes, reply in this thread.

Microsoft ended mainstream support for Windows 7 on January 13, 2015. Extended support ended o  January 14, 2020.

Windows 8.1 falls under the same lifecycle policy as Windows 8, and will reach end of Mainstream Support on January 9, 2018.

My vote would be dropping support for those OSes.

Agreed, let's stop supporting Windows 7 and Windows 8. If Microsoft stopped supporting these OSes, I don't see why we have to continue to support them :)

Closing this as it does not seem to be a problem

authors: ErikMogensen SeanFeldman paolosalvatori

repo: paolosalvatori/ServiceBusExplorer


text:
MessageID in body of message does not match MessageId of the Message System Properties right pane

MessageId in body of a dead letter message does not match MessageId of the Message System Properties right pane.
I'm no expert on this and realize that developers may customize the properties, but it will be nice to know if the message id in both sides should match.   Additionally the session Id does not appear on the right pane.
Any comment is appreciated.  Using Service Bus Explorer ver. 5.0.3.

What do you mean by the message id in the body? Is that something the sending application put there? A screenshot may help.

Do you mean that the MessageId that you set explicitly with the UI of the tool does not correspond to the messageId you see when peeking or reading the message?

The message send from one micro service to another in our case is a Json string which contains a message ID, session ID and others.   I though that that those IDs corresponded to the IDs on the side panel, but I gather by you questions that that's not the case.  The side panel I guess has the real IDs for the message sent and not the customized content.  I'm going to close this.

authors: ErikMogensen ngreyes paolosalvatori


text:
feat: add sse service impl

adds a SSE item stream service that writes to HTTP body

I'll do another cleanup pass on this and add a few more docs

repo: paradigmxyz/mev-share-rs


text:
feat: Add dumpgenesis subcommand

Close https://github.com/paradigmxyz/reth/issues/5833
If no Dumpgenesis argument(like --mainnet) is provided, we simply use the chain argument.
./reth dumpgenesis --help
Dumps genesis block JSON configuration to stdout

Usage: reth dumpgenesis [OPTIONS]

Options:
      --goerli
          Görli network: pre-configured proof-of-authority test network

      --mainnet
          Ethereum mainnet

      --holesky
          Holesky network: pre-configured proof-of-stake test network

      --sepolia
          Sepolia network: pre-configured proof-of-work test network

      --chain <CHAIN_OR_PATH>
          The chain this node is running.
          Possible values are either a built-in chain or the path to a chain specification file.

          Built-in chains:
              mainnet, sepolia, goerli, holesky, dev

          [default: mainnet]

      --instance <INSTANCE>
          Add a new instance of a node.

          Configures the ports of the node to avoid conflicts with the defaults. This is useful for running multiple nodes on the same machine.

          Max number of instances is 200. It is chosen in a way so that it's not possible to have port numbers that conflict with each other.

          Changes to the following port numbers: - DISCOVERY_PORT: default + `instance` - 1 - AUTH_PORT: default + `instance` * 100 - 100 - HTTP_RPC_PORT: default - `instance` + 1 - WS_RPC_PORT: default + `instance` * 2 - 2

          [default: 1]

  -h, --help
          Print help (see a summary with '-h')

Logging:
      --log.stdout.format <FORMAT>
          The format to use for logs written to stdout

          [default: terminal]

          Possible values:
          - json:     Represents JSON formatting for logs. This format outputs log records as JSON objects, making it suitable for structured logging
          - log-fmt:  Represents logfmt (key=value) formatting for logs. This format is concise and human-readable, typically used in command-line applications
          - terminal: Represents terminal-friendly formatting for logs

      --log.stdout.filter <FILTER>
          The filter to use for logs written to stdout

          [default: ]

      --log.file.format <FORMAT>
          The format to use for logs written to the log file

          [default: terminal]

          Possible values:
          - json:     Represents JSON formatting for logs. This format outputs log records as JSON objects, making it suitable for structured logging
          - log-fmt:  Represents logfmt (key=value) formatting for logs. This format is concise and human-readable, typically used in command-line applications
          - terminal: Represents terminal-friendly formatting for logs

      --log.file.filter <FILTER>
          The filter to use for logs written to the log file

          [default: debug]

      --log.file.directory <PATH>
          The path to put log files in

          [default: /Users/abnerzheng/Library/Caches/reth/logs]

      --log.file.max-size <SIZE>
          The maximum size (in MB) of one log file

          [default: 200]

      --log.file.max-files <COUNT>
          The maximum amount of log files that will be stored. If set to 0, background file logging is disabled

          [default: 5]

      --log.journald
          Write logs to journald

      --log.journald.filter <FILTER>
          The filter to use for logs written to journald

          [default: error]

      --color <COLOR>
          Sets whether or not the formatter emits ANSI terminal escape codes for colors and other text formatting

          [default: always]

          Possible values:
          - always: Colors on
          - auto:   Colors on
          - never:  Colors off

Display:
  -v, --verbosity...
          Set the minimum log level.

          -v      Errors
          -vv     Warnings
          -vvv    Info
          -vvvv   Debug
          -vvvvv  Traces (warning: very verbose!)

  -q, --quiet
          Silence all log output

Updated help message:
❯ ./reth dump-genesis --help
Dumps genesis block JSON configuration to stdout

Usage: reth dump-genesis [OPTIONS]

Options:
      --chain <CHAIN_OR_PATH>
          The chain this node is running.
          Possible values are either a built-in chain or the path to a chain specification file.

          Built-in chains:
              mainnet, sepolia, goerli, holesky, dev

          [default: mainnet]

      --instance <INSTANCE>
          Add a new instance of a node.

          Configures the ports of the node to avoid conflicts with the defaults. This is useful for running multiple nodes on the same machine.

          Max number of instances is 200. It is chosen in a way so that it's not possible to have port numbers that conflict with each other.

          Changes to the following port numbers: - DISCOVERY_PORT: default + `instance` - 1 - AUTH_PORT: default + `instance` * 100 - 100 - HTTP_RPC_PORT: default - `instance` + 1 - WS_RPC_PORT: default + `instance` * 2 - 2

          [default: 1]

  -h, --help
          Print help (see a summary with '-h')

Logging:
      --log.stdout.format <FORMAT>
          The format to use for logs written to stdout

          [default: terminal]

          Possible values:
          - json:     Represents JSON formatting for logs. This format outputs log records as JSON objects, making it suitable for structured logging
          - log-fmt:  Represents logfmt (key=value) formatting for logs. This format is concise and human-readable, typically used in command-line applications
          - terminal: Represents terminal-friendly formatting for logs

      --log.stdout.filter <FILTER>
          The filter to use for logs written to stdout

          [default: ]

      --log.file.format <FORMAT>
          The format to use for logs written to the log file

          [default: terminal]

          Possible values:
          - json:     Represents JSON formatting for logs. This format outputs log records as JSON objects, making it suitable for structured logging
          - log-fmt:  Represents logfmt (key=value) formatting for logs. This format is concise and human-readable, typically used in command-line applications
          - terminal: Represents terminal-friendly formatting for logs

      --log.file.filter <FILTER>
          The filter to use for logs written to the log file

          [default: debug]

      --log.file.directory <PATH>
          The path to put log files in

          [default: /Users/abnerzheng/Library/Caches/reth/logs]

      --log.file.max-size <SIZE>
          The maximum size (in MB) of one log file

          [default: 200]

      --log.file.max-files <COUNT>
          The maximum amount of log files that will be stored. If set to 0, background file logging is disabled

          [default: 5]

      --log.journald
          Write logs to journald

      --log.journald.filter <FILTER>
          The filter to use for logs written to journald

          [default: error]

      --color <COLOR>
          Sets whether or not the formatter emits ANSI terminal escape codes for colors and other text formatting

          [default: always]

          Possible values:
          - always: Colors on
          - auto:   Colors on
          - never:  Colors off

Display:
  -v, --verbosity...
          Set the minimum log level.

          -v      Errors
          -vv     Warnings
          -vvv    Info
          -vvvv   Debug
          -vvvvv  Traces (warning: very verbose!)

  -q, --quiet
          Silence all log output

repo: paradigmxyz/reth


text:
Update README.adoc

PR MC

@paragniist MC

repo: paragniist/spring-cloud-sleuth-otel


text:
passing on return value of callback passed to EasyDB::tryFlatTransaction()

tweaking EasyDB::tryFlatTransaction() so that the return value of a callback passed to it can be used as the return value of the method itself, i.e. to avoid function ($db) use (& $out) {} as a callback.

static analysers sometimes have issues with variables passed-by-ref to closures that're modified inside the closure, i.e. analyser does not see the modification happen, considers an if statement checking for the modification to be impossible or redundant.

Psalm likes returns, especially if they're in a typehint.
~ @muglug

this change is going to be useful in situations where you're acting upon PDO::lastInsertId() as the return value of a method, since outside the scope of a transaction, it gets reset to zero.
pre-change, this would require:
class Foo {
    public function DoThing(EasyDB $db) : int {
        $out = 0;
        $db->tryFlatTransaction(function (EasyDB $db) use (& $out) : void {
            // do some stuff, then insert a thing
            $out = $db->lastInsertId();
        });
    }
}

class Bar extends Foo {
    public function DoThing(EasyDB $db) : int {
        $out = 0;
        $db->tryFlattransaction(function (EasyDB $db) use (& $out) : void {
            $out = parent::DoThing($db);
            // do some more stuff with the $out int
        });
    }
}

post-change, this can be done:
class Foo {
    public function DoThing(EasyDB $db) : int {
        return $db->tryFlatTransaction(function (EasyDB $db) : int {
            // do some stuff, then insert a thing

            return $db->lastInsertId();
        });
    }
}

class Bar extends Foo {
    public function DoThing(EasyDB $db) : int {
        return $db->tryFlattransaction(function (EasyDB $db) : int {
            $out = parent::DoThing($db);
            // do some more stuff with the $out int

            return $out;
        });
    }
}

repo: paragonie/easydb


text:
No opportunity given to change cost of password_hash function

It seems like the user should be allowed to change the cost function, to best tune the functionality for different hardware. Currently this isn't possible.

I forked and added one:
https://github.com/Cr0nixx/password_lock


text:
DB Migration Fails If Postgres < 14 is used with Paralus Version >= 0.2.2

Expected vs actual behavior
When creating triggers, migration specifies CREATE OR REPLACE which is not supported until PostgreSQL 14.
e.g. https://github.com/paralus/paralus/blob/v0.2.2/persistence/migrations/admindb/000030_pg_oidc_provider_triggers.up.sql
The result is the following error:
error: Dirty database version 30. Fix and force version.
Running it locally will yield this error instead:
error: migration failed: syntax error at or near "TRIGGER" (column 19) in line 8: CREATE OR REPLACE FUNCTION providers_after_change_trigger() RETURNS TRIGGER AS $$
  BEGIN
    PERFORM pg_notify('provider:changed', '');
    RETURN NULL;
  END;
$$ LANGUAGE plpgsql;

CREATE OR REPLACE TRIGGER providers_updated
  AFTER UPDATE ON authsrv_oidc_provider
  FOR EACH ROW EXECUTE PROCEDURE providers_after_change_trigger();

CREATE OR REPLACE TRIGGER providers_inserted
  AFTER INSERT ON authsrv_oidc_provider
  FOR EACH ROW EXECUTE PROCEDURE providers_after_change_trigger();

CREATE OR REPLACE TRIGGER providers_deleted
  AFTER DELETE ON authsrv_oidc_provider
  FOR EACH ROW EXECUTE PROCEDURE providers_after_change_trigger();
 (details: pq: syntax error at or near "TRIGGER")

Therefore, PostgreSQL 14 is a requirement for deployments now. We need to make a note in the documentation for those who deploy postgresql separately. Or add separate scripts that will do a DROP IF EXISTS and CREATE after.
Steps to reproduce the bug

Install postgresql 11
Startup paralus and have it go through the init containers.
Log will fail with error: Dirty database version 30. Fix and force version.

Are you using the latest version of the project?
You can check your version by running helm ls|grep '^<deployment-name>' or using pctl, pctl version, and provide the output.
paralus 0.2.2
What is your environment setup? Please tell us your cloud provider, operating system, and include the output of kubectl version --output=yaml and helm version. Any other information that you have, eg. logs and custom values, is highly appreciated!

(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
This is a breaking change. The SQL script for 0.2.1 is different from 0.2.2
0.2.1: https://github.com/paralus/paralus/blob/v0.2.1/persistence/migrations/admindb/000030_pg_oidc_provider_triggers.up.sql
0.2.2: https://github.com/paralus/paralus/blob/v0.2.2/persistence/migrations/admindb/000030_pg_oidc_provider_triggers.up.sql

[X ] I've described the bug, included steps to reproduce it, and included my environment setup with all customizations.
[X ] I'm using the latest version of the project.

@estein9825 Thanks for reporting. I think we recently moved to CREATE OR REPLACE statements to avoid errors in rerunning migrations, but this goes unnoticed.

add separate scripts that will do a DROP IF EXISTS and CREATE after.

This sound good approach to me. We can replace the CREATE OR REPLACE triggers with DROP IF EXISTS + CREATE statements.

Hi @akshay196 could you please assign this to me?

Hi @akshay196 please assign this to me.

repo: paralus/paralus


text:
Add test spec

Merge after #1.

Fixed code style
Add JS tests
Fixed bug in setAddress
Updated ABIs

Implemented my suggestion regarding the irrefutable require(!b.deleted) and added some extra test cases for the new require. Should have 100% coverage now.

repo: parity-contracts/badge-registry


text:
New proposals now written to DB

I broke something with #292
NODE-WATCHER: Error: Variable '$data' expected value of type 'ProposalStatusCreateInput!' but got: {"blockNumber":{"connect":{"number":1915200}},"proposal":{"connect":{"proposalId":17}},"status":"Tabled"}. Reason: 'uniqueStatus' Expected non-null value, found null. (line 1, column 11):
mutation ($data: ProposalStatusCreateInput!) {
          ^
    at BatchedGraphQLClient.<anonymous> (/node_watcher/node_modules/http-link-dataloader/src/BatchedGraphQLClient.ts:74:13)
    at step (/node_watcher/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:40:23)
    at Object.next (/node_watcher/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:21:53)
    at fulfilled (/node_watcher/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:12:58)
    at processTicksAndRejections (internal/process/task_queues.js:88:5) {
  result: { data: null, errors: [ [Object] ], status: 200 }
}

it looks like the image we use isn't from master.

Weird, what's in master is not the same sha as the last image https://github.com/paritytech/Nomidot/pull/293/files reverting to that.

I can't understand that. master has the image sha 38a.. here: https://github.com/paritytech/Nomidot/blame/master/back/node_watcher/kubernetes/nomidotwatcher-last-50k-job.yaml#L30
from #284
Which should have been changed then by #293 for f88... but this simply does appear anywhere.

@yjkimjunior can you make sense of this ^ it looks like #293 just never happened!

repo: paritytech/Nomidot


text:
Merge into yj-focus-formfield - Don't use keycodes

@yjkimjunior Can we try and use the onSubmit prop on a <form>? I proposed here just one example on AccountName, but I think the same thing could work everywhere. I.e. don't add onSubmit on fields, but on the wrapping form. We could delete all usage of event.keycode too.
To be merged into #323

Hi @amaurymartiny, I agree it is hacky but I resorted to it because the enter key press behavior maps to the back button even while the input is in focus. This happens whenever the back button is present, i.e. when currentStep > 1. In a previous commit this behavior persisted even after explicitly calling blur() on the back button as well. So far what I could come up with has been to use the keycodes or to outright disable the back button...

hmm, I'm still reluctant to merge keycodes in. Have you tried this PR? It works on my machine, on the AccountName page the enter key goes to the next page.
Also, maybe tabindex=-1 on the back button might work?

yup, I tried pulling your change and it works on AccountName which is currentStep === 1 however it has the same problem behavior if I just manually set back button enabled on that page though. Just tried setting tabIndex=-1 on the back button to same behavior. Also tried setting tabIndex=1 to the next button which causes a page reload and doesn't hit the onSubmit handler. 😞

@yjkimjunior can you try again now?

authors: amaurymartiny yjkimjunior

repo: paritytech/fether


text:
Reference Docs Hand-off to Core Devs

Ideas:

Use CLI to make sure that docs are updated
Add to contributor guidelines any documentation details we want to make sure makes it in
Keep a close eye for a while
Communicate this transition with our leadership

Use CLI to make sure that docs are updated
I believe CI is now testing the code snippets in rust files, right?
Add to contributor guidelines any documentation details we want to make sure makes it in
What's the status on this? If it isn't done, what needs to happen?
Keep a close eye for a while
It's been over 3 weeks since this was opened, how are we feeling? We're supposed to be watching that any time code changes, reference docs and examples in them are updated accordingly, right? I'll start watching too.
Communicate this transition with our leadership
Both Bjorn and Fred mentioned this in our 22 May all hands meeting.

Use CLI to make sure that docs are updated

I believe CI is now testing the code snippets in rust files, right?

This is dependent on the example, but I believe all of our SRML docs are now tested in CI, so someone would have to explicitly change it to "ignore" or "nocompile" to make it ignore them. I hope this would get caught in review.

Add to contributor guidelines any documentation details we want to make sure makes it in

What's the status on this? If it isn't done, what needs to happen?

It is in @pepyakin 's guidelines that he added to the Substrate PR form. We could do a better guide on what info needs to be included.

Keep a close eye for a while

It's been over 3 weeks since this was opened, how are we feeling? We're supposed to be watching that any time code changes, reference docs and examples in them are updated accordingly, right? I'll start watching too.

The updates have not faced as much scrutiny as the initial pass at documentation. For example we initially decided that implementation details like this wouldn't go into the docs because it's way too difficult to maintain.

authors: JoshOrndorff joepetrowski shawntabrizi

repo: paritytech/substrate-developer-hub


text:
fetchLatestSubstrate.js doesn't work on CI

https://travis-ci.org/paritytech/substrate-light-ui/builds/530671696#L733
Tbh I'd prefer to use something like https://github.com/paritytech/substrate/issues/2534

Tracking #314

repo: paritytech/substrate-light-ui


text:
Fix drips arbitrary amounts

Fix #117
Test evidence:
Before:

After fix:

@chevdor had to add tests here, please check once more

repo: paritytech/substrate-matrix-faucet


text:
Bump wasmtime to 6.0.0

This PR updates wasmtime to 6.0.0.
This new version includes my fix to make LTO work again, so we can finally get rid of our own wasmtime fork.
Also of particular note here is that wasmtime 6.0.0 enabled a new optimization framework which heavily regresses the contracts pallet's performance (cc @athei); I still haven't finished investigating why exactly this happens, but for the time being we can just revert this back to 5.0.0's behavior by changing the relevant option when initializing wasmtime. Otherwise the performance looks to be mostly unchanged.

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2423593

bot merge

authors: koute paritytech-cicd-pr

repo: paritytech/substrate


text:
Update parity-wasm to 0.40

I updated the direct parity-wasm dependencies from 0.31 to 0.40. This resolves #2517 (I think). There are still some indirect dependencies, see the output of cargo tree -p parity-wasm:0.31.3 -i.
I'm getting a few failed tests where the gas left is up by 1, but I'm not sure if these are really errors or not.
---- wasm::tests::contract_transfer stdout ----
thread 'wasm::tests::contract_transfer' panicked at 'assertion failed: `(left == right)`
  left: `[TransferEntry { to: 9, value: 6, data: [1, 2, 3, 4], gas_left: 49971 }]`,
 right: `[TransferEntry { to: 9, value: 6, data: [1, 2, 3, 4], gas_left: 49970 }]`', srml/contracts/src/wasm/mod.rs:468:3

[clabot:check]

My initial guess is that it should be OK, reasoning for that the gas metering algorithm was altered in the latest version so that it doesn't insert some superfluous metering calls.
I'd like to check that though.

It looks OK, so you can just update the expected values. Apart from that the check continuous-integration/gitlab-check-runtime fails and in order to please it you should update the runtime version here

authors: expenses pepyakin


text:
3/11 연구계획 회의

과제 목표
설계 - 스케치
HW 1. 전체 2. 전광판 확대: 세빈
SW 1. 앱 프로토: 지수
이론적/기술적 내용
비콘: 소현
앱: 지수

앱 제작 과정
공공데이터

설계
동작원리(플로우차트)
실험방법
시나리오
기대효과
응용
sample6 참고!!

버튼 1번 누르면 음성 안내
2번 누르면 클릭이벤트

repo: park-sohyeon/Senior-Project


text:
Blacklist/WhiteList with Parkpow (Script)

Add an option to set a Parkpow TAG and display it on the NX screen in case of a match

@AashishDhakal can you check the changes again?

repo: parkpow/deep-license-plate-recognition


text:
reviewed triggering paths for all the actions

added path to trigger the GH action whenever the action or other dependent action updates
reviewed git config option to not fail when an action is manually executed

Merge of this PR would trigger all the actions

@gabriel-farache PTAL at the failure:
2024-03-27T11:22:14.205634817Z stderr F time="2024-03-27T11:22:14Z" level=info msg="Project: 69f039a5-c80f-4a40-a145-cc8b2c14bc71; level=info msg=\"Cloning the repository using git into '/tmp/move2kube3657911401/m2ksources' . This might take some time.\""
2024-03-27T11:22:14.283806886Z stderr F time="2024-03-27T11:22:14Z" level=info msg="Project: 69f039a5-c80f-4a40-a145-cc8b2c14bc71; level=fatal msg=\"failed to create the plan. Error: \\\"failed to clone the repo 'git+ssh://bitbucket.org/gfarache31/m2k-test@master'. Error: failed to clone using vcs url 'git+ssh://bitbucket.org/gfarache31/m2k-test@master' and clone options {CommitDepth:1 Overwrite:true MaxSize:-1 CloneDestinationPath:/tmp/move2kube3657911401/m2ksources}. Error: failed to perform clone operation using git. Error: repository already exists\\\"\""
2024-03-27T11:22:14.286171Z stderr F time="2024-03-27T11:22:14Z" level=error msg="failed to update the database after planning finished. Error: \"failed to copy the plan file from /tmp/plan-69f039a5-c80f-4a40-a145-cc8b2c14bc71-839309155/m2k.plan to /move2kube-api/data/projects/69f039a5-c80f-4a40-a145-cc8b2c14bc71/inputs/expanded/m2k.plan after planning finished. Error: \\\"failed to open the source file at path \\\\\\\"/tmp/plan-69f039a5-c80f-4a40-a145-cc8b2c14bc71-839309155/m2k.plan\\\\\\\" Error: \\\\\\\"open /tmp/plan-69f039a5-c80f-4a40-a145-cc8b2c14bc71-839309155/m2k.plan: no such file or directory\\\\\\\"\\\"\""
2024-03-27T11:22:15.494601773Z stderr F time="2024-03-27T11:22:15Z" level=info msg="GET /api/v1/workspaces/8f4f5cc8-a0b8-461b-9dc4-bf9a35af2f33/projects/69f039a5-c80f-4a40-a145-cc8b2c14bc71/plan" request-id=6f0fbcf2-0aa6-4781-b354-214ea48f53fb
2024-03-27T11:22:15.496303175Z stderr F time="2024-03-27T11:22:15Z" level=error msg="failed to send a GET request to get the plan progress from the server at http://localhost:34943/progress . Error: \"Get \\\"http://localhost:34943/progress\\\": dial tcp [::1]:34943: connect: connection refused\""

authors: dmartinol masayag

repo: parodos-dev/serverless-workflows


text:
Should it run the command upon start up, before any files are modified?

Proposal: When cargo watch starts, run the command, even if no file has changed.
I've often started cargo watch when started working on a project, and it clearly doesn't do anything until a file has changed. Sometimes I can't remember if all the tests passed (or if the code compiles), and I'd like to see the output of cargo test. So I need to make a simple change to something so that it'll run and I can see. But if cargo watch ran the command as soon as it was started, this would be easier.
But maybe that's my workflow, does this sound useful to other people?

I'm of either mind on this, so I'll wait for community feedback too.

Yes please.
On Tue, Mar 15, 2016, 4:41 PM Félix Saparelli notifications@github.com
wrote:

I'm of either mind on this, so I'll wait for community feedback too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/passcod/cargo-watch/issues/37#issuecomment-197034361

Suggestion: Use Github's new "Add a reaction" feature for voting. Add a +1 (:+1:) to this comment to say "I would like this feature" and -1 (:-1:) to say "I would not like this feature"

If you wish to, sure, but do add your use case if it is different from the top-post. I'd love to have more insight into why people would want one or the other.

Used cargo watch run with a simple iron example server, and expected it to run the command.
Maybe it should be an optional thing or depend on the cargo command?

I think I'm going to rebuild cargo watch to more in the model of remy's
nodemon, if you know of it, after I do Notify v3. This would include the
functionality requested in this ticket.
On Thu, 30 Jun 2016, 19:36 Robin Stocker notifications@github.com wrote:

Used cargo watch run with a simple iron
http://ironframework.io/doc/iron/ example server, and expected it to
run the command.
Maybe it should be an optional thing or depend on the cargo command?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/passcod/cargo-watch/issues/37#issuecomment-229582734,
or mute the thread
https://github.com/notifications/unsubscribe/AAJgi3Z3-9fQMromw_IX0ARbfF3D1YRUks5qQ3HsgaJpZM4Hxa-W
.

I'm all for this as I wanted to watch a server, so the first run before anything changes is definitely useful. One alternate thing is to allow pressing Enter to trigger a build, regardless of the state of files. I believe that guard allows something similar.

Nodemon does it by typing rs then Enter, which guards against restarting inadvertently if an interactive program is watched, or if one likes to use blank lines to visually separate runs when doing verbose debugging. That's probably what I'll go with. I use nodemon all the time, it's a very useful tool — it is very much the vision for cargo watch.
Speaking of, as much as I'd like to keep users here, I have no illusion of being able to bring it to greatness any time soon, so if you happen to have npm/node installed and want a very good cargo-watch alternative, go with nodemon:
# With long options for clarity:
$ nodemon --ext rs,toml --exec 'cargo run' --watch src --watch test --watch examples

# Short options for brevity:
$ nodemon -e rs,toml -x 'cargo run' -w src -w test -w examples

That should have the requisite behaviour.

For other people landing here, there's now also a nodemon-like tool written in Rust: https://github.com/mattgreen/watchexec/
$ watchexec --run-initially --restart "cargo run"

Note that --run-initally is the default now, so you don't need to specify it.

This is now done with the entirely new version 4.0.0! It will run the command upon starting by default, but you can disable the behaviour using --postpone.

authors: aij passcod robinst rory shepmaster

repo: passcod/cargo-watch


text:
Free flowing 1-row ticker a la Fantastical

The iOS app Fantastical allows for fluid horizontal scrolling in a one-row calendar view. Rather than paging per week, the days slide by fluidly by any increment. How much modification to JTAppleCalendar do you think this would take?

Acknowledged.
Downloading the app to see it my self. brb.

Ok scratch that.. haha. Its not a free app >_<
So let me understand.
You want one row fluid scrolling?

On closer inspection of the gif image, you want the calendarView to be able to be incremented scrolled by one single day?

Wow I was away for a second and you did it! Thank you! I'm a beginner with iOS but I'm looking to dig into this control as I have a couple of calendar-dependent ideas. Definitely the last calendar app I'll try ;)

Thanks much. I appreciate it. Yea i pushed the update.
I'm will be updating the cocoa pod in a bit (just doing some last minute tests).
But if you want to preview it before release you can see the code already on github (here).
Looking forward to the ideas.

Also, this is a new project that has little publicity :<
If you create a cool calendar, feel free to share an image here to inspire others -> https://github.com/patchthecode/JTAppleCalendar/issues/2
cheers

authors: patchthecode soundsmitten

repo: patchthecode/JTAppleCalendar


text:
Header 'JTAppleCalendar-Swift.h' not found

Compiling app with calendar from latest master give me this error:
Header 'JTAppleCalendar-Swift.h' not found

can you try now and let me know?
I just created a sample test project and it seems to work fine (master branch)

Fixed) thanks.

authors: mecid patchthecode


text:
Why is the promtail_config_positions empty by default?

ciao, please note that i'm currently in the process to get acquainted with loki and promtail. i was just wondering why the default for promtail_config_positions is an empty mapping. the application's default is /var/log/positions.yml which it can't write to when deployed with this role.

It was kept empty to use the default from loki and allow to override it when the environment requires this.
When looking at upstream, it will default to /var/log/positions.yml - https://github.com/grafana/loki/blob/master/pkg/promtail/positions/positions.go#L33
Possible ways forward that I see:

define the variable per default and ensure that file is writeable by the promtail user/group
ensure that promtail is added to the syslog group per default, then the any file in /var/log/* would be writeable by promtail

Open to further suggestions and happy to accept a PR :-)

i hope to come back w/ a pr when i'm through w/ my whole setup. just saying that /var/log/… seems wrong, /tmp/… is okay and working, but /var/promtail/positions.yml makes the most correct impression to me.

authors: funkyfuture patrickjahns

repo: patrickjahns/ansible-role-promtail


text:
Avoid legacy stack syntax for pinned dependencies

Pinning deps in the extra-deps section works from around stack 1.5 or 1.6, so by now, quite old versions.

Dang, I’m really sorry I let this languish! I’ve switched this project to use Cabal rather than Stack, as Stack doesn’t have the Backpack support that this project now requires. Thank you for finding this, and I’m sorry to have let it die on the vine!

No prob!

authors: fosskers patrickt

repo: patrickt/effects-benchmarks


text:
GTM Support

We recently added a GTM integration, we should make it easy for someone to use GTM or GA

Closing, not going to get into analytics in this project. Going to submit a PR that removes what we do have already in.

repo: patronage/bubs-next


text:
Should Context Selector have its own element in the page header

In the page header we have containers for tools/nav etc. I placed the context selector in the nav as a demo and it looks like this:

Visuals look like this:
https://drive.google.com/file/d/1b405W_CGasRR-C7eZZl7KgigYODvtsMi/view
cc: @mcoker
Then when I put in the nav also it sat in front of the context selector because the .pf-c-page__header-nav uses grid columns/rows

@christiemolloy yep, I would expect to need to modify the page component header to position the context selector properly.

@nicolethoen Hello! I see you were assigned this issue -- I've been assigned essentially the same one in react. @jschuler mentioned that I can continue with it when the context selector functionality is implemented here. Let me know if there's anything I can do to help.

@mcarrano @maryshak1996  do you guys have designs of how the context selector should behave on mobile? Or maybe you could point me towards who originally designed the context selector/in the page

@kybaker can you help here? I know we went through all of these cases very early on when we were designing the PF4 navigation system. There should be mocks that show this.

@mcarrano This designs utilized the larger header and scrolling behavior which has since been changed. I think we will have to look at the behavior again given the new masthead design.

@kybaker @mcarrano @christiemolloy
I have made a lot of progress with this story so far, but believe it is blocked until I have the mobile mockups.

I will set up some time for us to discuss.

Met today with @christiemolloy @mcoker @nicolethoen and @kybaker to discuss next steps. Looks like this needs to be pulled back to design to consider what the mobile header should look like when a context selector is present.
I have renamed the issue and changed from a bug to an enhancement as this case was never fully implemented as a demo before. @LHinson @rachael-phillips we should consider what the priority is on this and where it lives on the roadmap.

@mcarrano assigning to you so this get added to the design board

Actually @kybaker has agreed to take a look at this. We want to take a different approach and move the context selector from the page header to the Nav sidebar.

Met today with @amysueg and Tiffany Nolan to discuss requirements from Integration products for a context selector in the masthead. This is currently being proposed as a way to switch between applications within the integration suite without the user needing to leave the active window.
Here are some current mockups/ideas (work in progress):
https://marvelapp.com/4i45j22/screen/62949664
https://marvelapp.com/449iacg/screen/61070423

Upon further discussion, we will not advertise the context selector as a standard component of the masthead. We can work with any product teams that need this feature to create a custom solution but will no longer offer this as a demo.
Have opened https://github.com/patternfly/patternfly-org/issues/1542 to remove references and mocks for this from the related design guidelines.

authors: LHinson christiemolloy jenny-s51 kybaker mcarrano mcoker nicolethoen

repo: patternfly/patternfly-next


text:
Add .pf-l-flex__item wrapper to examples

relates to: #1979
Currently, the pf-l-flex layout is only usable by applying selectors to react elements. In order for Pf-react to build a proper layout, we need to wrap flex items in .pf-l-flex__item so that properties can be passed to those items.
Also, in other react components with large stylesheets, we currently split the stylesheet into two or more partials. Doing so with the flex layout will allow for very basic, lightweight flex usage.

:tada: This issue has been resolved in version 2.31.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: mattnolting redallen


text:
fix(wizard): adjust padding, var names

fixes https://github.com/patternfly/patternfly-next/issues/1501

Deploy preview for pf-next ready!
Built with commit 02a5164b29fb719b3c87cc93aa122e90646cdf78
https://deploy-preview-1504--pf-next.netlify.com

@christiemolloy doh! thanks, updated. It is technically a breaking change, but the component was just added this week, I wonder if it would be OK. @jschuler is working on the pf-react component, and I would like to see these changes there. @dgutride what do you think?

I'd say it's still ok @mcoker - nobody is using it yet

LGTM.

authors: dgutride mcoker patternfly-build srambach


text:
Alpha 6.0 upgrade for patternfly.

Upgrade building and running how ever it needs some visual updates.

@dlabaj is this ready for review? Looks like there's some conflicts, and I'm not sure what the deal is with those snyk failures.

authors: dlabaj wise-king-sullyman

repo: patternfly/patternfly-quickstarts


text:
Allow manual choice of registry key

for example, the following doesn't work, because the orm.Session (orm.session.Session) instance that sessionmaker creates is a weird type, so it isn't simply registered in Tidi as orm.Session.
import tidi
from sqlalchemy import orm

...

session: orm.Session = orm.sessionmaker(bind=engine)
tidi.register(session)
tidi.default_tidi_registry.get(session)  # raises a `tidi.registry.RegistryLookupError` 😒

so it'd be nice if we could optionally manually elect the type or maybe even more generically a key that tidi uses to store the dependency
import tidi
from sqlalchemy import orm

...

session: orm.Session = orm.sessionmaker(bind=engine)
tidi.register(session, key=orm.Session)
tidi.default_tidi_registry.get(orm.Session)  # 🤞

decided agains a more generic key because after all we use deliberate types when injecting so that type hinting works.

repo: pattersam/tidi


text:
Fixes #374 - logging add_to_input_history if args.message is used.

Fixes https://github.com/paul-gauthier/aider/issues/374

btw. this is how I am testing it https://gist.github.com/gwpl/8faa1b314c7d5905dd23ce041d65dc79 :
# https://github.com/paul-gauthier/aider or when working on a patch on fork:
docker build --file docker/Dockerfile -t aider-image .
# to launch pytest:
docker run -it --volume $(pwd):/app --entrypoint /bin/bash aider-image -c "pip install pytest && pytest"

of course for faster runs I have docker image with already included pytest. However if someone want's just to copy&paste, above line is robust as will install pytest in case it's missing.

repo: paul-gauthier/aider


text:
chore(main): release 1.0.6

:robot: I have created a release beep boop
1.0.6 (2023-01-25)
Miscellaneous 🧹

deps-dev: bump @vercel/ncc from 0.36.0 to 0.36.1 (b1aa066)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/paulschuberth/regex-extract-action/releases/tag/v1.0.6 :sunflower:

repo: paulschuberth/regex-extract-action


text:
🛑 FIT-nl is down

In 917f79c, FIT-nl (https://www.fit.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FIT-nl is back up in e056733.

repo: paulwolters/up


text:
Added onDispose Functionality and Modified deps Type to Array in useEffect

Hello ~,
I needed an onDispose functionality within useEffect, so I've added it. Additionally, I have changed the type of deps to an array.
I would appreciate it if you could review them.

// example

    /*
    useEffect(()=>{
        console.log("Call once")
    },[])
    */
    useEffect(onEffect = {
        println("Call once")
    })

    /*
    useEffect(()=>{
        console.log("Call once")
        return  () => {
            console.log("onDispose")
        }
    },[])
    */
    useEffect(onEffect = {
            println("Call once")
        }, onDispose = {
            println("onDispose")
        }
    )

    /*
    useEffect(()=>{
        console.log("Call when the value of isOn changes")
        return  () => {
            console.log("onDispose")
        }
    },[isOn, "SOME" ])
    */
    useEffect(arrayOf(isOn,"SOME"),
        onEffect =  {
            println("Call when the value of isOn changes  [isOn] $isOn")
        }, onDispose = {
            println("onDispose")
        }
    )

In fact, every timeif  you pass deps through arrayOf, a new array instance will be created, which will cause LaunchedEffect and DisposeEffect to execute blocks. If you just want to execute when the component is loaded or when it ends, you can declare a custom hook. For example: useMount, [useUnmount](https:/ /github.com/junerver/ComposeHooks/blob/master/hooks/src/main/kotlin/xyz/junerver/compose/hooks/useUnmount.kt);
Of course, if you insist on doing this through a hook, then your deps should be vararg deps:Any, and use *deps when passing it to XXEffect so that it can be tracked correctly.

authors: junerver psyrenpark


text:
feat: switch logging to ubiquibot-logging NPM module

@pavlovcik I will let you know when it is ready to be merged.

All right! builds correctly and v0.3.0 is correctly imported
npm notice
npm notice 📦  ubiquibot-logger@0.3.0
npm notice === Tarball Contents ===
npm notice 49B    README.md
npm notice 1.9kB  dist/logs.d.ts
npm notice 12.5kB dist/logs.js
npm notice 27.2kB dist/logs.js.map
npm notice 604B   dist/pretty-logs.d.ts
npm notice 4.2kB  dist/pretty-logs.js
npm notice 9.3kB  dist/pretty-logs.js.map
npm notice 2.2kB  package.json
npm notice === Tarball Details ===
npm notice name:          ubiquibot-logger
npm notice version:       0.3.0
npm notice filename:      ubiquibot-logger-0.3.0.tgz
npm notice package size:  11.0 kB
npm notice unpacked size: 57.8 kB
npm notice shasum:        ae296958daae3169bfde2866379216621c7c41f5
npm notice integrity:     sha512-F3BExAEPfQrHK[...]oECTw1tELcn0Q==
npm notice total files:   8
npm notice
npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access
+ ubiquibot-logger@0.3.0

repo: pavlovcik/ubiquibot


text:
Add compress.lua example

I've been struggling for a while with how to use converters, so I think that this example may help others later.
If you have any questions/ideas about it, I will be glad to help with improving.

Maybe error handling would be a good idea.

@TingPing Well, I've already added checks which were required to produce meaningful errors during testing. Do you suggest to add assert on every single call which may fail in theory?

Well, at a glance the splice() call is among the more important ones. For examples I'd also say assert()s are bad compared to printing the error messages.

@TingPing Ok about more checks, will do that. What do you have against assert, by the way? They still print error message to console (and exit to prevent further problems).

@TingPing Are you fine with this now?

Guys,  this is an example, not a production application. Excessive error
checks may only obscure it
IMHO

I mean I'm not going to block it or anything. I just think examples should represent real usage and that means handling expected errors not asserting.
No big deal.

I'll count that as "reviewed by @TingPing" :-)

authors: TingPing ildar psychon v1993

repo: pavouk/lgi


text:
term_image.image.TermImage is deprecated

What happened?
term_image.image.TermImage is deprecated already in term-image==0.5.0. So I'm facing an error when using the latest version of nbpreview.
If I manually downgrade term-image you'll see the deprecation warning.

term-image also recommends
If you want to use this library in a project while it's still on version zero, ensure you pin the dependency version to a specific minor version e.g >=0.4,<0.5.

in their README.
Expect no errors to appear when I nbpreview.
nbpreview version
nbpreview 0.9.1
Output

Notebook
https://github.com/dsgibbons/shap/blob/1d9224e890e45c10f494c54eafee3f6a6ba05a11/notebooks/overviews/An introduction to explainable AI with Shapley values.ipynb
OS
macOS
Terminal
kitty
Python version
3.10

+1
term-image needs to be pinned to <0.5.0

I am experiencing the same problem.

+1
term-image needs to be pinned to <0.5.0

or just fix the bug?

For what it's worth, it seems obvious this project is no longer maintained.

For what it's worth, I believe this project is no longer maintained.

ohhh noo

For what it's worth, I believe this project is no longer maintained.

To be clear, I'm talking about nbpreview, not term_image.

repo: paw-lu/nbpreview


text:
Sl smith/issue1

first set of fixes to usernames and removing insiders & cli

I suppose you opened the PR on the wrong repository :smile:?

Yeah sorry! I tried out VS code for the first time and messed it up 😅

authors: pawamoy sl-smith

repo: pawamoy/copier-pdm

license: ISC


text:
Improved dateTime.

Improved dateTime.

Already merged changes elsewhere.

repo: payfunc/isoly


text:
Paypal checkout page text scramled in safari

Hi,
Paypal checkout page text is scramled in safari... see screenshot.
Not in Firefox and Chrome.
I am using the WP eStore shopping card plugin.
Any idea what the problem can be?
Thanks, JB

Assigning to @bluelnkd to help triage -- looks like a potential problem with the guest app.

@battem Can you share a few more details so we can work on a fix?

[ ] Version of Safari/OSX
[ ] All console logs during the time of the issue, especially error messages

I'm trying to see what I can do to run into the same on our test devices here, and make sure we can see the same issue your reporting.
As an FYI the fonts used to render the checkout experience (along with most of PayPal) is set to: font-family: HelveticaNeue-Light, Helvetica Neue Light, Helvetica, Arial, sans-serif;

Hi blueInkd,
Here is the link to the shoppingcard: http://letsgotothebeach.org/product/swim-sarong/
Im using WP eStore shopping card plugin + addon eStore Credit Card Default PayPal Checkout Option

Safari Version 10.1.1
OSX 10.11.6 El Capitan
font: https://fonts.googleapis.com/css?family=Oxygen+Mono

I did not get any error messages.
Hope you can find out whats the problem... cant imagine my font is the cause?
Thanks, Jan.

authors: battem bluelnkd bluepnume

repo: paypal/paypal-checkout


text:
(setup): Fix setup function from being called twice

Setup function is being called more than once because currentScript is always defined and there are muliple exports of setup.js. not sure if this works or if it passes tests because I wasn't able to build the project.  Probably need to take a look at the contributing documentation and make sure its accurate.

This is happening because setup is being called in the button iframe too. So I don't think this fix is going to work.
On a side note, let me add some quick-start steps in the readme.

FYI: https://github.com/paypal/paypal-checkout/blob/master/README.md#development

@bluepnume So is checkout.js required on the iframe page as well, or is it there just to have the same version of xcomponent?  Couldn't you just have xcomponent?
Is setup required to be called on the iframe page?  If not can we make a param to does not call it if set?
If its required then can we get a logPrefix param?
logPrefix:  currentScript.getAttribute('data-log-prefix'),

Then on Hermes do "data-log-prefix="ppxo_hermes"

@bluepnume So is checkout.js required on the iframe page as well, or is it there just to have the same version of xcomponent? Couldn't you just have xcomponent?

No, the way xcomponent works, the component definition needs to live in both the parent and the child. This is also necessary so we can do things like rendering paypal.Checkout up from paypal.Button's iframe.

If its required then can we get a logPrefix param?

Yeah, that's a good idea. 👍

authors: bluepnume trainerbill


text:
Live Market Data Not Working

I am trying to fetch live market data for equity but preference is not working... I am trying to do this way... please correct me if I am doing wrong....
pm.get_live_market_data('LTP', ['BSE', '523144', 'EQUITY'])
it returns the response....
{'data': [{'found': False, 'message': 'You have sent preference packet in an invalid format: BSE'}, {'found': False, 'message': 'You have sent preference packet in an invalid format: 523144'}, {'found': False, 'message': 'You have sent preference packet in an invalid format: EQUITY'}]}

Hi @knandini24x7
The pattern for preference is <exchange>:<securityId>:<scripType>.  For eg : In your case it will beBSE:523144:EQUITY.

repo: paytmmoney/pyPMClient


text:
closes stdin in shellcmd to prevent some commands for hanging

I know you haven't update your project lately, but it still works well!  I found a problem when building some scripts that some commands wouldn't exit because they were still waiting for stdin input.  So this simple fix closes it since its not used in the run command.

Hi @DaKaZ, I'm sorry for my belated response. I'll merge this & push the release.
Thanks for the PR!

Released here: https://rubygems.org/gems/scriptster/versions/0.2.3

authors: DaKaZ pazdera

repo: pazdera/scriptster


text:
🛑 Ouvidoria is down

In 356a763, Ouvidoria (https://ouvidoria.unb.br/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ouvidoria is back up in 2499c13 after 12 minutes.


text:
🛑 Departamento is down

In 50966c2, Departamento (http://cca.unb.br/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Departamento is back up in 928933d after 19 minutes.


text:
styles.action direction

Anyway to add support for the 'active' style, so that you could add the 'active' object to the element props?
Maybe something like:
styles.active = {
  left: '1rem'
};

if (this.props.styles && this.props.styles.active) {
  styles.active = objectAssign(this.props.styles.active);
}

styles.default = {
  padding: '1rem',
  background: '#212121',
  color: '#FAFAFA',
  width: 'auto',
  position: 'fixed',
  left: '-100%',
  top: '6rem',
  boxShadow: '0 0 1px 1px rgba(10,10,11,0.125)',
  borderRadius: '5px',
  cursor: 'default',
  font: '1rem normal Roboto, sans-serif',
  transition: '.5s ease'
};

if (this.props.styles && this.props.styles.bar) {
  styles.default = objectAssign(styles.default, this.props.styles.bar);
}

styles = !this.state.active ? styles.default : objectAssign(styles.default, styles.active);

return styles;

I also modified the order of how the styles are build allowing the active style to be set, then a merge of prop styles and default, then finally figuring out if you're sending the active or simply merged styles

@TeckniX yeah, this is something I can do. I'll look into it this week.

Thanks! I think the above example should be pretty close.

@TeckniX Just FYI, this will be fully supported in version 2.0.0 as:
{ barStyles, activeStyles, actionSyles }

:+1:

authors: TeckniX pburtchaell

repo: pburtchaell/react-notification


text:
Cuda ver 12 needed

Could you please update driver and Cuda version to 12? Not able to run ffmpeg 6 because it requires Cuda 12 but 11 is installed. Thanks!

+1 for this request, experiencing some containers which are requiring cuda 12 - Thanks !

fixed

authors: irishj kftar pdbear


text:
Overwrite option and MaxLength attribute in property

In my case, I spend a lot of time making changes after creating an entity by adding new properties.
For this reason I had to add this option to my fork:
add entity [/path/file.yaml] true
With this, I can overwrite the changes. In order for this to work well, in the future I need to add my personal code in partial.
It is also a lot of code that I have to write to limit the size of the text fields, I have added this option:
Entities:

Name: GeoZipCode
Features:

Type: AddRecord
Properties:
Name: AdminCode1
Type: string
MaxLength: 250   <-
CanFilter: true
CanSort: true

Sorry I'm just getting to properly look at this. Thanks for the idea!
It seems like the motivator here is to add new properties? I used to have functionality that did that without overriding the whole file, but it didn't really seem to save any dev time; it did add maintenance overhead though and was a motivator to remove it at the time. I'm considering some flows where it might more more useful though so maybe it'll make a comeback.
With this particular implementation though, I'm hesitant to bring it in as it would completely eliminate the ability to maintain any post scaffolding updates. Maybe you've added some custom helper methods, updated props to value objects, etc. This would force you to just use the boilerplate when it's not meant to be the end, just the start. Given that, I don't think this PR is a good fit for the lib but if it's working well for you're workflow in your fork that's great to hear!
With that said, adding the option for a max length would be reasonable. Personally I'm not a huge fan of using the db to enforce business rules as that should really be a domain responsibility, but that's personal preference and wouldn't add much maintenance overhead so if you'd like to submit something around that I think that's great.
Regardless, thanks again for taking the time to contribute and working to improve the tool for other devs.


text:
Array_view should return Ref when indexed

In GitLab by @ksiero on Apr 11, 2022, 11:25
I was struggling over a week with indexing an Array_view, but I think I have found missing puzzle.
Basically an Array_view holds 2 information:

Size with all dimensions of the view.
List of chunk datatypes (one chunk datatype for each Ref (with array datatype) that is part of the Array_view).

Right now index method returns pair with moved pointer and new datatype.
In case of indexing Array_view we want to return new Ref (we should reuse Referenced_buffer with the same pointer but with changed list of chunks). So ideally the indexing should not move the pointer itself, but change the size of Array_view and chunk datatypes in the list in that way, when we want the Refs from the Array_view with chunk datatypes then we get correctly moved pointers from them.
This is fundamental change of relation between Datatype and Ref. Unfortunately I don't have time to design it and implement. What I am leaving is the Chunk_datatype that is already tested and Array_view that is partly implemented and partly tested on branch view_datatype.

Thank you for these design guidelines!

repo: pdidev/pdi


text:
Render html

Add ability to render messages using html.

Resolved 250d15b

repo: pdmfc/nova-info-card


text:
Update eventsInS3ToSplunk.yml required

After follow up the steps to deploy the function, several extra steps are require while not documented:
1- Mandatory fields:

logType,
splunkHECEndpoint,
splunkHECToken,
splunkHost,
splunkIndex,
splunkSource,
splunkSourcetype,
stack-name,
capabilities

For such parameter-overrides, the following values were used:

elblog,
https://http-inputs-firehose-customized-name.splunkcloud.com/services/collector
secret-hash
loremIpsunDolor
netlb
s3-bucket-with-access-logs-unmanaged
aws:elb:accesslogs
aws-to-splunk-app-test-latest
CAPABILITY_NAMED_IAM

2- The final deploy command like looks like:
aws cloudformation deploy
--template $(pwd)/eventsInS3ToSplunk.yml
--parameter-overrides
logType=elblog
splunkHECEndpoint='https://http-inputs-firehose-customized-name.splunkcloud.com/services/collector'
splunkHECTokensecret-hasg
splunkHost=loremIpsunDolor
splunkIndex=netlb
splunkSource=s3-bucket-with-access-logs-unmanaged
splunkSourcetype=aws:elb:accesslogs
--stack-name aws-to-splunk-app-test-latest
--capabilities CAPABILITY_NAMED_IAM
3- After a successful deploy, the function start giving errors in the Lambda console like:
No more records within selected time range Retry
--
  | 2022-12-19T11:43:18.146-05:00 | START RequestId: d2300018-a8e8-5655-bb5a-5c023e2bf384 Version: $LATEST
  | 2022-12-19T11:43:18.148-05:00 | [ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'pandas' Traceback (most recent call last):
  | 2022-12-19T11:43:18.150-05:00 | END RequestId: d2300018-a8e8-5655-bb5a-5c023e2bf384
  | 2022-12-19T11:43:18.150-05:00 | REPORT RequestId: d2300018-a8e8-5655-bb5a-5c023e2bf384 Duration: 3.46 ms Billed Duration: 4 ms Memory Size: 1024 MB Max Memory Used: 53 MB Init Duration: 233.69 ms
  | 2022-12-19T11:43:18.641-05:00 | START RequestId: 7a8ad0f3-33cb-5f03-b28a-8ce9a502d968 Version: $LATEST
  | 2022-12-19T11:43:18.642-05:00 | [ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'pandas' Traceback (most recent call last):
  | 2022-12-19T11:43:18.643-05:00 | END RequestId: 7a8ad0f3-33cb-5f03-b28a-8ce9a502d968
  | 2022-12-19T11:43:18.643-05:00 | REPORT RequestId: 7a8ad0f3-33cb-5f03-b28a-8ce9a502d968 Duration: 1.91 ms Billed Duration: 2 ms Memory Size: 1024 MB Max Memory Used: 53 MB
  | 2022-12-19T11:44:50.741-05:00 | START RequestId: 6c1c4e98-cdb5-5ed8-a31a-12825aaab0f1 Version: $LATEST
  | 2022-12-19T11:44:50.742-05:00 | [ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'pandas' Traceback (most recent call last):
  | 2022-12-19T11:44:50.743-05:00 | END RequestId: 6c1c4e98-cdb5-5ed8-a31a-12825aaab0f1
  | 2022-12-19T11:44:50.743-05:00 | REPORT RequestId: 6c1c4e98-cdb5-5ed8-a31a-12825aaab0f1 Duration: 1.72 ms Billed Duration: 2 ms Memory Size: 1024 MB Max Memory Used: 54 MB
  | 2022-12-19T11:44:51.977-05:00 | START RequestId: 99b6151d-50f5-5561-b990-4907c7dff129 Version: $LATEST
  | 2022-12-19T11:44:51.978-05:00 | [ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'pandas' Traceback (most recent call last):
  | 2022-12-19T11:44:51.979-05:00 | END RequestId: 99b6151d-50f5-5561-b990-4907c7dff129
  | 2022-12-19T11:44:51.979-05:00 | REPORT RequestId: 99b6151d-50f5-5561-b990-4907c7dff129 Duration: 1.75 ms Billed Duration: 2 ms Memory Size: 1024 MB Max Memory Used: 54 MB
  | 2022-12-19T11:44:52.508-05:00CopySTART RequestId: f29659d1-1620-56e4-8197-05cb810c24c3 Version: $LATEST | START RequestId: f29659d1-1620-56e4-8197-05cb810c24c3 Version: $LATEST
  | 2022-12-19T11:44:52.510-05:00 | [ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'pandas' Traceback (most recent call last):
  | 2022-12-19T11:44:52.511-05:00 | END RequestId: f29659d1-1620-56e4-8197-05cb810c24c3
  | 2022-12-19T11:44:52.511-05:00 | REPORT RequestId: f29659d1-1620-56e4-8197-05cb810c24c3 Duration: 3.73 ms Billed Duration: 4 ms Memory Size: 1024 MB Max Memory Used: 54 MB
  | 2022-12-19T11:45:18.030-05:00 | START RequestId: 280f73fc-8981-598b-bc67-2fe61ecc5b0c Version: $LATEST
  | 2022-12-19T11:45:18.031-05:00 | [ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'pandas' Traceback (most recent call last):
  | 2022-12-19T11:45:18.031-05:00 | END RequestId: 280f73fc-8981-598b-bc67-2fe61ecc5b0c
  | 2022-12-19T11:45:18.031-05:00 | REPORT RequestId: 280f73fc-8981-598b-bc67-2fe61ecc5b0c Duration: 1.69 ms Billed Duration: 2 ms Memory Size: 1024 MB Max Memory Used: 54 MB
  | 2022-12-19T11:45:18.705-05:00 | START RequestId: 32d43449-eb7d-5bec-ac92-68537c4090e3 Version: $LATEST
  | 2022-12-19T11:45:18.706-05:00 | [ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'pandas' Traceback (most recent call last):
  | 2022-12-19T11:45:18.707-05:00 | END RequestId: 32d43449-eb7d-5bec-ac92-68537c4090e3

Is something outdated, or prior to do (kinda dependencies) before the function proper work?

Thanks for the update.
I proceed to do the update, and now I got this comming in the console:
`
-- | --
  | 2022-12-20T12:29:21.342-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.342-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.342-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.342-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.351-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.351-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.388-05:00 | Processed file s3://xxxxxxxxxxxx-us-west-2-elblog/arms/AWSLogs/xxxxxxxxxxxx/elasticloadbalancing/us-west-2/2022/12/18/xxxxxxxxxxxx_elasticloadbalancing_us-west-2_app.xxxxx.f5d69d8e559eec82_20221218T0805Z_10.128.3.227_4pt9me9a.log.gz
  | 2022-12-20T12:29:21.467-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.467-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.478-05:00 | Processed file s3://xxxxxxxxxxxx-us-west-2-elblog/arms/AWSLogs/xxxxxxxxxxxx/elasticloadbalancing/us-west-2/2022/12/18/xxxxxxxxxxxx_elasticloadbalancing_us-west-2_app.xxxxx.f5d69d8e559eec82_20221218T0805Z_10.128.1.4_2gcpog9s.log.gz
  | 2022-12-20T12:29:21.532-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.532-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.532-05:00 | Unable to extract timestamp. Falling back to current time.
  | 2022-12-20T12:29:21.541-05:00 | Processed file s3://xxxxxxxxxxxx-us-west-2-elblog/arms/AWSLogs/xxxxxxxxxxxx/elasticloadbalancing/us-west-2/2022/12/17/896552222739_elasticloadbalancing_us-west-2_app.xxxxx.f5d69d8e559eec82_20221217T1105Z_10.128.2.146_514m7xgn.log.gz
  | 2022-12-20T12:29:21.612-05:00 | Unable to extract timestamp. Falling back to current time.
`
I just want to validate if this is the expected output of the logs?.

Nope, that's not expected.  That error message indicates the function couldn't extract the timestamp.  I'd recommend making sure that the CloudFormation template was deployed with the setting specified in the documentation, specifically the appropriate settings for the splunkTimeDelineatedField and splunkTimeFormat parameters.
Also, I did fix the issue of Lambda importing pandas and pyarrow in a more permanent way.  Thanks again for pointing that one out!

Hello, related to the error Unable to extract timestamp. Falling back to current time is related to there is a prefix that comes in the log, the prefix changes to different values, a space, and then the timestamp in the ISO format. If I delete the (.{1,5})? part of the regex in the prefix-ISO8601 format, then it works with the regexgroupindex of 0 (no splunk prefix, since it dynamic not fixed). How can you suggest to approach this?
Considering that having a customized regex would be a bad practice. The prefix can be strings like

h2 2022-12-30T15:08:29.240935Z
https 2022-12-30T15:05:25.942645Z
2022-12-30T15:08:30.114770Z

So, we can adjust the regex to fit this prefix of up-to 10 char length or empty-non-exist?

Hello!  Since the ELB/ALB/NLB logs are delimited by spaces, I'd follow the specified documentation for these log types.  Specifically by setting the splunkEventDelimiter to space, splunkTimeDelineatedField to 1 for ALB logs or 0 for ELB logs or 2 for NLB logs, and splunkTimeFormat to delineated-ISO8601.
I'll get the wiki instructions updated to reflect that a setting of 1 should be used for ALB logs, 0 for ELB logs and 2 for NLB logs should be used for the splunkTimeDelineatedField parameter on the CFT.  Thanks for pointing that out!

Documentation updated!

repo: pdreeves/splunk-aws-gdi-toolkit


text:
[ldd-img_surface] Commanded_Parameters not referenced

img_surface:Commanded_Parameters is defined but not used anywhere.  Please add it (0-1) to the Surface_Imaging class, as the last item (commanded last being consistent with img:  )

fixed in v1200 release in main and v1200 branch

authors: rgdeen thareUSGS


text:
⚠ Hartman Foundation has degraded performance

In bd4dc09, Hartman Foundation (https://gordonhartman.com/) experienced degraded performance:

HTTP code: 200
Response time: 3180 ms

Resolved: Hartman Foundation performance has improved in 559fcef.

Resolved: Hartman Foundation performance has improved in 559fcef.

repo: pearanalytics/uptime


text:
🛑 edgecombe is down

In e2c373b, edgecombe (https://edgecombe.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: edgecombe is back up in 02861d4.


text:
Better Git support

Staged commits
See what files are going into a commit.

Also the ability to link the project to private repositories.

repo: pebble/cloudpebble


text:
Stream all video file types

I know that this library only supports mp4, webp, and h264 videos but, what do you suggest if I want to support all video formats?
Is convert video type is a correct way?
What is the best library to convert videos for android?

If you want use this library the only way is convert video format. I only know ffmpeg, Maybe you can use javacv (wrapper of ffmpeg for android) for it:
Example (not tested):
https://stackoverflow.com/questions/57259495/how-to-convert-video-to-mp4-javacv
LIbrary:
https://github.com/bytedeco/javacv


text:
Task Creation

Add Task Creation component.
Tale a look on Fullscreen dialog: https://material-ui.com/demos/dialogs/

Done.

repo: pedrocelso/task-ui


text:
Adding support for calling back from phantom to node

I want to be able to call from the phantom code to the node module.
The code added a function calls "nodeCallback" at the phantom side and property calls "onCallback" on the "page" object.

Coverage decreased (-1.7%) to 98.328% when pulling ff308e25520c739a7120b95aceeba5c35d084e34 on ad-venture:master into 0aa95f81dffcaab48357ebf2aab42ce64ce69247 on peerigon:master.

Thank you for your pull-request.
Can you describe a use-case where this nodeCallback is necessary and cannot be solved in other ways?

Hi jhnns
I've added this functionally because I needed to initiate an action for events at the phantomjs code.
I'm using MutationObserver to monitor changes on the page, and when change occurs, the nodeJS server need to react.
I haven't found any other way to do this in the exist code.
Thanks
Ysrael

You're right. There is currently no way to achieve this.
However, there are some problems with your implementation. What happens if I have multiple instances of Page and I would like to install event listeners individually. We somehow need to have a record so that we now where "to call back".
For instance, we could have a third argument emit:
phantom.run(function (resolve, reject, emit) {
    setInterval(() => {
        emit("hi");
    }, 100);
    resolve();
});

somePage.run(function (resolve, reject, emit) {
    setInterval(() => {
        emit("hi");
    }, 100);
});

phantom.on("hi", function () { ... });
somePage.on("hi", function () { ... });

This way...

we don't have a "magical" nodeCallback variable in the upper scope
we can collate the callbacks to their respective instance in node

However, there might be another problem: When we're inside PhantomJS, we are not inside the actual page context. When using the evaluate function provided by PhantomJS, we're not allowed to access the scope either. Hence, this code will not work:
page.run(function (resolve, reject, emit) {
    this.evaluate(function () {
        // emit is not defined because we're in the actual page context now
        emit("hi");
    });
    resolve();
});

We would need to use the onCallback mechanism as described here:
page.run(function (resolve, reject, emit) {
    this.onCallback(function (message) {
        emit(message);
    });
    this.evaluate(function () {
        window.callPhantom('hi');
    });
    resolve();
});

This is very ugly – and again, we have the same problem that we need to collate callbacks from different sources...
I totally see the use-case and I wish, phridge would provide an easy API for this. But a proper implementation takes a lot of effort...
For instance, it would be cool to have a evaluate method on our page instance that mitigates all the cruft around it. This is probably what you would like to use:
page.evaluate(function (resolve, reject, emit) {
    var observer = new MutationObserver(function(mutations) {
      mutations.forEach(function(mutation) {
        emit("mutation", mutation.type);
      });
    });

    observer.observe(document.body, {
      attributes: true,
      childList: true,
      characterData: true
    });
});

page.on("mutation", function (mutationType) {

});

authors: ad-venture coveralls jhnns

repo: peerigon/phridge

license: unlicense


text:
Collection created on server even when a document has remote connection.

Related to #39, I now run on peerdb@0.20.0 and when inspecting the local mongo database, I still see collections created on the server, even though the connection for that Document goes to a different server.
It's not a problem since queries seem to go to the other server, just thought I'd mention that you get a lingering (unused) empty collection.

Hm, on the second try now, the extra collection was not created. Maybe I had it in the DB from before. I'll reopen if I can confirm the problem.

Thanks.

I added a test. They are not created.

:+1: Great, thanks! I'll soon try to make server-server connections to test everything out.

authors: MatejJan mitar

repo: peerlibrary/meteor-peerdb


text:
Add a pass to simplify single-character choices

I have a modified version of examples/xml.peggy in my project, and was trying to optimize it for speed. I found a few places where it could be rewritten to avoid backtracking, getting about a 20% win, but with some readability cost.
Then I noticed that there are a number of long lists of alternate character classes, and they end up being implemented very inefficiently; effectively it tries one regex after another in sequence.
I manually combined all the character classes for BaseChar into a single character class, and got a nearly 2x speed up.
So I've added a pass that does that automatically. The result is a more than 3x speedup parsing the xml files that I work with (which seem fairly typical).
The pass takes a rule like chars: "a" / "b" / [d-r] and turns it into chars: [abd-r]

I've put it under an option, mergeCharacterClasses because enabling it by default breaks a number of tests, which have specific expectations for error messages:
    Expected value to strictly be equal to:
      "Expected \"a\", \"b\", or \"c\" but \"d\" found."
    Received:
      "Expected [abc] but \"d\" found."

Since that test is specifically designed to ensure that an appropriate error message is output for choice nodes I didn't want to just change the expected output. But I'd be happy to change the grammar for such tests so that the choice nodes remain as choice nodes, and enable the optimization by default if that would be preferable.

I just realized I need to update lib/peggy.js and docs/js/examples.js now that this is done unconditionally. Should I do that now, or wait until you're happy with the state of the commit?

This looks good to me, I think.  @Mingun any other comments?

Except one needed addition:  a CHANGELOG entry, please.

Except one needed addition: a CHANGELOG entry, please

I put it in "minor" updates - let me know if if should be somewhere else...

Sorry for moving the goalposts, but once I thought of coverage on #427, there are a few lines that need to be hit on this one in lib/compiler/passes/merge-character-classes.js, unless they are particularly hard to reach.

I'm going off what I see in the coverage/lcov-report directory after having run npm run build.  That dir can sometimes be a little confusing because it doesn't get cleaned up every time, and the URLs change if you rerun with a subset of the tests.  Try deleting the directory, then navigating to the correct file from index.html when you run a different set of tests.
Here are the three lines that I currently see uncovered in the full test suite: 22, 67, 73.
I don't see breakpoints hit on any of those, but checked to make sure that I have everything set up right by having breakpoints fire on other lines in your file.

Also, I'm on the Discord channel if you want to try and figure this out in realtime.

I rewrote things a little:

some things that asClass was checking for were unnecessary because merge would have already handled them
preserve locations when merging nodes
only call cleanParts after merging all the alternates for efficiency

And then I updated the tests so that everything is covered.

@Mingun, one last thumbs-up, please?

@Mingun this one needs a final thumbs-up as well, please.

Anything else to do here?

@hildjj @Mingun ping again?

repo: peggyjs/peggy


text:
Bump devDependencies

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

This mostly eliminate warning about babel-preset-es2015.

Coverage remained the same at 75.246% when pulling 4df3d65b3993663e1c66ae8592d640ea9416c434 on Mingun:update-deps-upstream into 669f782a5f3928a2958147992eb07df5b0ecf54a on pegjs:master.

That's totally the coolest way to spend New Year's night.

I'm actually spending it playing Skyforge on my PS4 with my laptop open in front of me 😆

authors: Mingun coveralls futagoza polkovnikov-ph

repo: pegjs/pegjs


text:
🛑 Beyond.pl is down

In 11247fb, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 403
Response time: 640 ms

Resolved: Beyond.pl is back up in 7d2eeb5 after 11 minutes.

repo: pejotes/upptime


text:
🛑 Beyond.pl is down

In 3f37863, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beyond.pl is back up in bae4c74.


text:
🛑 Beyond.pl is down

In 6190043, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beyond.pl is back up in 78124d6.


text:
Regenerate types after new RPC calls are included

Once this issue is merged and the new nodes are running with the changes, we need to update the types for these new RPC calls.
This will include both the manual definition in types-definitions directory and corresponding imports, and running the auto-generation script. Finally we should push these changes to npm and bump the package version.
This task is a prerequisite so that Polkadot.js UI is able to show the new calls.

@gianfra-t the linked ticket is merged. Are the nodes running with the changes already?

I just checked and no, but running locally from main do show the rpc methods. Most likely scenario is that the node clients have not been updated. We need this to show the new RPC's since we made changes to the node code.

@ebma do you know more about update plans for the node clients?

I don't but I don't think we redeployed the collator nodes yet. @pendulum-chain/product did you track the required redeployment as was asked for in the description of this PR?

@ebma is this still valid and needs a response? I am not sure of the answer.

So this ticket was so that we could see and query in Polkadot.js the new rpc methods discussed in the description above. In the screenshot are highlighted.
Right now we can see them, but they do not appear in the drop down menu.

The task of this ticket is still valid and has been unblocked by now meaning we could start working on this now. @pendulum-chain/product please prioritize this ticket. The outcome is that new convenience helper functions are available for the parachain-staking pallet. These could be used directly in the polkadot.js explorer or in the portal app. It's only a nice-to-have change.

authors: TorstenStueber ebma gianfra-t vadaynujra


text:
Losen requirement for quorum check in Stellar relay pallet

Context
The check for valid quorum sets in the Stellar relay pallet is too strict in many cases and does not work well with archived messages. For more context, see this Notion page.
TODO
Change the logic so that it doesn't require each organization to have >1/2 validators but it is still a valid quorum if the SCP messages are targeting >2/3 of organizations with at least >1/2 validators.

@ebma can we get this ticket estimated?

authors: annatekl ebma

repo: pendulum-chain/spacewalk


text:
Refress on pull on listview

I have a scaffold with a header and a listview
The pull to refresh only works when pulling down on the header, not on the list view
Is there a way to make it work on both? Thank you

I have the same problem ... did you find solution for that ?

@gehad-ahmed-mohammed yes, you need to wrap the ListView directly with the SmartRefresh, and it will work on the ListView

authors: arualana gehad-ahmed-mohammed


text:
Priority Marker Emoji White Space Collapsed

On MacOS, the white spaces of priority marker emojis collapse. Probably related to this.

Proposed solution: use both ::before and ::after to enforce margin on the emojis.
My custom.css:
/* priority marker emoji white space collapse */
a[priority]::after {
  font-size: var(--ct-inline-code-font-size);
}

a[priority="A"]::before,
a.priority[href="#/page/A" i]:before {
  content: "🔴";
  visibility: visible;
}

a[priority="B"]::before,
a.priority[href="#/page/B" i]:before {
  content: "🟡";
  visibility: visible;
}

a[priority="C"]::before,
a.priority[href="#/page/C" i]:before {
  content: "🟢";
  visibility: visible;
}

a[priority="A"]::after,
a.priority[href="#/page/A" i]:after {
  content: "A";
  visibility: visible;
}

a[priority="B"]::after,
a.priority[href="#/page/B" i]:after {
  content: "B";
  visibility: visible;
}

a[priority="C"]::after,
a.priority[href="#/page/C" i]:after {
  content: "C";
  visibility: visible;
}

a[priority]::before,
a.priority:before {
  width: initial;
  margin-left: 0;
  margin-right: .5em;
}

a[priority]::after,
a.priority:after {
  border-radius: 50%;
  color: var(--ls-primary-text-color);
  display: inline-block;
  font-size: 16px;
  font-weight: 600;
  height: 1rem;
  line-height: 1rem;
  text-align: center;
  margin-right: .3em;
}

After fix:

No, the emoji' spaces collapse without the custom css. According to this stackoverflow post, it might be related to my ultra wide external monitor.

Let me take a look at it. In the meantime, can you try put to the fix in your custom.css with the solution provided in the StackOverflow post? Let me know if it works for you.

The solution in the StackOverflow post requires me to wrap the emoji in the pseudo element with another element. I am not sure how to do it. In my proposed solution, I just use two separate pseudo elements.

I have pushed a new implementation for rendering markers without using emojis. Please take a look.

Just realized the text in the marker is not completely centered


text:
[TEST] - Continue splitting PurRepositoryTest

@mattyb149, @brosander, review it please.
I continue splitting PurRepositoryIT moving groups of linked tests to separate classes.
The fist commit fixes a lurk flaw -- it properly shutdowns PentahoSystem. Without it, each next attempt to initialise the system causes an thrown exception. It is not reproduced in tests executions, because Ant task forks JVM perTest. However, it fails when I run all tests within IDE as it executes them within one virtual machine.

Changed files:
plugins/pdi-pur-plugin/test/org/pentaho/di/repository/pur/PurRepositoryIT.java
plugins/pdi-pur-plugin/test/org/pentaho/di/repository/pur/PurRepositoryTestBase.java
plugins/pdi-pur-plugin/test/org/pentaho/di/repository/pur/PurRepository_SharedObjects_IT.java
Checkstyle violations:
No errors found
Integration test coverage change:
org.pentaho.di.repository.pur.PurRepository:

instructionPercentCoverageChange : +2.08%
branchPercentCoverageChange : +2.48%
linePercentCoverageChange : +2.77%
complexityPercentCoverageChange : +1.83%
methodPercentCoverageChange : +1.14%

authors: akhayrutdinov brosander

repo: pentaho/pentaho-kettle


text:
[SP-5280] Importing transformations with partitions enabled freeze th…

…e Server as well as the repository
@pentaho-lmartins

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/pur/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/pur/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/pur/core/src/main/java/org/pentaho/di/repository/pur/PurRepository.java

authors: ssamora wingman-pentaho


text:
[PDI-18786] CurrentDirectoryChangedListener was firing during import and

causing erroneous changes to the imported job when the directory to
contain the job did not exist prior to import.

:warning: Build finished in 36m 54s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 5 test(s) failed:
org.pentaho.di.www.ExecuteJobServletTest.testExecuteJobServletTest (click to expand)
javassist.CannotCompileException: by java.util.zip.ZipException: invalid block type

org.pentaho.di.www.ExecuteJobServletTest.testExecuteJobServletTestCantFindDirectory (click to expand)
javassist.CannotCompileException: by java.util.zip.ZipException: invalid block type

org.pentaho.di.www.ExecuteJobServletTest.testExecuteJobServletTestJobNotFoundInDirectory (click to expand)
javassist.CannotCompileException: by java.util.zip.ZipException: invalid block type

org.pentaho.di.www.ExecuteJobServletTest.testExecuteJobServletTestCantFindRepository (click to expand)
javassist.CannotCompileException: by java.util.zip.ZipException: invalid block type

org.pentaho.di.www.ExecuteJobServletTest.testExecuteJobServletTestWithUnauthorizedUser (click to expand)
javassist.CannotCompileException: by java.util.zip.ZipException: invalid block type

Tests run: 3680, Failures: 5, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 35m 53s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3680, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

authors: buildguy peterrinehart


text:
rpc: SimulateTrade is slow and contains duplicates for very large inputs

Describe the bug
Performing a trade simulation with a large quantity of input (e.g. $2^{64} -  1$ penumbra) is exceedingly slow (>2700ms!!!) and returns traces with duplicates.
To Reproduce
Steps to reproduce the behavior:

Go to
Set the request of the SimulateTrade rpc as:

{
  "input": {
    "amount": {
      "hi": "1"
    },
    "assetId": {
      "altBaseDenom": "upenumbra"
    }
  },
  "output": {
    "altBaseDenom": "ugm"
  }
}

Check the output (similar to: https://gist.github.com/erwanor/0f37887468496dbc2ee020022262c2cc)

Expected behavior
We should strive to make trade simulation execute faster (say, 100ms) and it should not contain any duplicate.

@hdevalence has determined that the slowness is caused by debug-level tracing, a full node running with info level tracing is able to return in <200ms. The duplicate traces remain a mystery for now.

The duplicate traces are caused by free cycles (cycles with cost 1) that are present in the best-path found. In #2763, we define a total ordering on Path<S> that specifies that all else being equal, a path with shorter length is better than a path with longer length. A better fix would avoid generating candidate paths with useless cycles, but this issue is considered fix for now.

repo: penumbra-zone/penumbra


text:
funding: process staking streams at end of epoch

Follow-up to #3663, we now process validator funding streams in the funding component.

Note for visibility: this PR halts the chain if an inflation invariant is breached.


text:
declutter vitest temp files

not sure why these started showing up but they're annoying. adds a specific pattern to ignorefiles, and provides a cleanup script

yeah these are annoying :/

authors: TalDerei turbocrime

repo: penumbra-zone/web


text:
optimize: local cache and avoid to use keyword type.

optimize: local cache and avoid to use keyword type.
Compatible with CRLF separator (under windows).
luarocks: release v0.1

we have used this version in APISIX for months, thanks for your great job.

:thumbsup: thanks !

authors: membphis peposso

repo: peposso/lua-tinyyaml