Trouble Running TensorFlow v2.16.1 with NVIDIA GeForce 940MX GPU #914

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
binary
TensorFlow version
tf 2.16.1
Custom code
Yes
OS platform and distribution
Linux
Mobile device
Linux
Python version
3.12
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
12.4/V11.8.89
GPU model and memory
No response
Current behavior?
I attempted to run TensorFlow version 2.16.1 on my local machine, which is equipped with an NVIDIA GeForce 940MX GPU. However, I encountered a kernel crash error while executing the following code in a Jupyter Notebook cell,
This code snippet worked perfectly fine when I used TensorFlow v2.4.1, which I installed using Conda (conda install anaconda::tensorflow-gpu==2.4.1). However, after upgrading to TensorFlow v2.16.1 via Conda (conda install anaconda::tensorflow-gpu==2.16.11), the kernel crashed with the error message:
"The Kernel crashed while executing code in the current cell or a previous cell. Please review the code in the cell(s) to identify a possible cause of the failure."
System Configuration:

CUDA Version: 12.4
cuDNN Version: Not specified
GPU: NVIDIA GeForce 940MX
Driver Version: 550.54.14

Issue is,

Verified that the code runs successfully with TensorFlow v2.4.1.
Encountered a kernel crash error when running the code with TensorFlow v2.16.1.

Seeking guidance on how to resolve the kernel crash issue and successfully run TensorFlow v2.16.1 with my NVIDIA GeForce 940MX GPU. Any insights, troubleshooting steps, or workaround suggestions would be greatly appreciated.
Thank you for your assistance!
Standalone code to reproduce the issue
model = keras.Sequential(
    [
        keras.layers.Flatten(input_shape=(28, 28)),
        keras.layers.Dense(100, activation="relu"),
        keras.layers.Dense(10, activation="sigmoid"),
    ]
)

Relevant log output
16:43:31.562 [info] Generated code for 5 = <ipython-input-5-4e58535241f8> with 6 lines
16:43:32.012 [error] Disposing session as kernel process died ExitCode: undefined, Reason: 2024-05-27 16:43:14.979186: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-05-27 16:43:31.611060: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.678484: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.678870: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.679090: W tensorflow/core/common_runtime/gpu/gpu_device.cc:2343] TensorFlow was not built with CUDA kernel binaries compatible with compute capability 5.0. CUDA kernels will be jit-compiled from PTX, which could take 30 minutes or longer.
2024-05-27 16:43:31.680484: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.680861: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.681155: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.681340: W tensorflow/core/common_runtime/gpu/gpu_device.cc:2343] TensorFlow was not built with CUDA kernel binaries compatible with compute capability 5.0. CUDA kernels will be jit-compiled from PTX, which could take 30 minutes or longer.
2024-05-27 16:43:31.741853: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.742222: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.742465: I external/local_xla/xla/stream_executor/cuda/cuda_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-05-27 16:43:31.742647: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1928] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 1169 MB memory:  -> device: 0, name: NVIDIA GeForce 940MX, pci bus id: 0000:01:00.0, compute capability: 5.0

16:43:32.071 [info] Cell 4 completed in -1716808411.592s (start:<PHONE_NUMBER>592, end: undefined)
16:43:38.622 [error] Failed to write data to the kernel channel shell [
  <Buffer 3c 49 44 53 7c 4d 53 47 3e>,
  <Buffer 64 34 30 65 66 35 36 34 32 62 65 33 61 61 63 36 30 32 62 32 61 65 33 32 30 36 62 30 36 36 34 36 61 33 39 38 32 61 62 32 31 32 39 39 64 34 62 33 38 37 ... 14 more bytes>,
  <Buffer 7b 22 64 61 74 65 22 3a 22 32 30 32 34 2d 30 35 2d 32 37 54 31 31 3a 31 33 3a 33 38 2e 36 32 31 5a 22 2c 22 6d 73 67 5f 69 64 22 3a 22 34 62 61 36 35 ... 177 more bytes>,
  <Buffer 7b 7d>,
  <Buffer 7b 7d>,
  <Buffer 7b 22 73 69 6c 65 6e 74 22 3a 66 61 6c 73 65 2c 22 73 74 6f 72 65 5f 68 69 73 74 6f 72 79 22 3a 66 61 6c 73 65 2c 22 75 73 65 72 5f 65 78 70 72 65 73 ... 12329 more bytes>
] Error: Socket is closed
    at a.postToSocket (/home/~/.vscode/extensions/ms-toolsai.jupyter-2024.4.0-linux-x64/dist/extension.node.js:318:10349)
    at /home/~/.vscode/extensions/ms-toolsai.jupyter-2024.4.0-linux-x64/dist/extension.node.js:318:10099 {
  errno: 9,
  code: 'EBADF'
}

To troubleshoot the kernel crash issue with TensorFlow v2.16.1, it's crucial to ensure that the environment is correctly set up and all dependencies are compatible. Here’s a detailed approach to diagnose and potentially resolve the problem.
Steps to Reproduce the Issue

Set Up the Environment: Create a clean environment and install the required packages.
conda create -n tf_env python=3.10
conda activate tf_env
conda install tensorflow-gpu==2.16.1

Verify CUDA and cuDNN Versions: Ensure the correct versions of CUDA and cuDNN are installed.
conda install cudatoolkit=12.4 cudnn=8.9

Install Jupyter Notebook:
conda install jupyter

Install IPython Kernel:
pip install ipykernel
python -m ipykernel install --user --name=tf_env --display-name "Python (tf_env)"

Launch Jupyter Notebook:
jupyter notebook

Run the Provided Code:
In a new Jupyter notebook cell, execute the following code:
import tensorflow as tf
from tensorflow import keras

model = keras.Sequential(
    [
        keras.layers.Flatten(input_shape=(28, 28)),
        keras.layers.Dense(100, activation="relu"),
        keras.layers.Dense(10, activation="sigmoid"),
    ]
)
print("Model created successfully")

Diagnose the Error
Based on the provided log output, the error messages indicate potential issues with CUDA compatibility and kernel binaries. The critical error messages are:

CUDA Kernel Compatibility:
TensorFlow was not built with CUDA kernel binaries compatible with compute capability 5.0. CUDA kernels will be jit-compiled from PTX, which could take 30 minutes or longer.

NUMA Node Read Failures:
successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero.

Potential Solutions

Ensure Correct CUDA Installation:
Ensure that the CUDA installation is complete and the paths are correctly set.
nvcc --version

Verify that the CUDA version matches the expected version (12.4).

Check GPU Driver:
Ensure that the GPU driver is up to date and compatible with the CUDA version.
nvidia-smi

Verify that the driver version supports CUDA 12.4.

Update TensorFlow:
If using the nightly version or building from source, ensure the latest updates are included:
pip install tf-nightly-gpu

Environment Variables:
Set the environment variables to ensure TensorFlow uses the correct CUDA and cuDNN libraries.
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64
export CUDA_HOME=/usr/local/cuda

Check Compute Capability:
The GeForce 940MX has a compute capability of 5.0, which is quite old. Make sure TensorFlow is configured to support this.

Full Reproduction Script
import tensorflow as tf
from tensorflow import keras

# Define a simple model
model = keras.Sequential(
    [
        keras.layers.Flatten(input_shape=(28, 28)),
        keras.layers.Dense(100, activation="relu"),
        keras.layers.Dense(10, activation="sigmoid"),
    ]
)

print("Model created successfully")

# Verify GPU availability
print("TensorFlow version:", tf.__version__)
print("Is TensorFlow built with CUDA:", tf.test.is_built_with_cuda())
print("Is GPU available:", tf.config.list_physical_devices('GPU'))

Additional Steps

Consult TensorFlow GitHub Issues:
Search for similar issues in the TensorFlow GitHub repository.

Revert to an Older TensorFlow Version:
If the issue persists, consider using an older TensorFlow version that you know works:
conda install tensorflow-gpu==2.4.1

@KushanManahara If you're using TensorFlow v2.16.1, kindly ensure your CUDA and cuDNN versions are compatible.
Please refer to TensorFlow documentation for supported versions for TensorFlow v2.16.1 and let us know?
Thank you!


Documentation for df codegen workflow

https://github.com/Kotlin/dataframe/pull/763

Closed because the PR is merged


Transactions support

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Examples
#Starts and commits transaction in easy mode
yii::$app->mongodb->transaction(function($clientSession){
    #Your codes in transaction
},[
    'readConcern' => 'snapshot',
    'writeConcern' => 'majority',
]);

#Supports nested calling (this is not nested transaction!)
yii::$app->mongodb->transaction(function(){

    User::deleteAll(...);

    yii::$app->mongodb->transaction(function(){
        #Execute your mongodb commands in new session and transaction
        User::deleteAll(...);

        yii::$app->mongodb->noTransaction(function(){
             #Execute your mongodb commands in out of session and transaction
             //your codes ...
        });
    });

    return false; #Roll backing the current transaction
});

#Other way
yii::$app->mongodb->startTransaction([
    'readConcern' => 'snapshot', #transaction options
],[
    'causalConsistency' => true, #session options
]);

#your codes ...

yii::$app->mongodb->commitTransaction(); #or yii::$app->mongodb->rollBackTransaction();

Once feature
Starts and commits transaction in easy mode if the previous transaction was not executed, otherwise only runs your actions in previous transaction.
yii::$app->mongodb->transaction(function(){
    yii::$app->mongodb->transactionOnce(function(){
        #Execute your mongodb commands in previous transaction.
    });
});

yii::$app->mongodb->startSession(); #Ends the previous session and starts the new session.
yii::$app->mongodb->startSessionOnce(); #The session does not start.

Lock a document for update
yii::$app->mongodb->transaction(function($clientSession){
    #Locks a document of the collection in a transaction(like `select for update` feature in mysql)
    try{
        $doc = MyActiveRecordClass::LockDocument(new ObjectId('5e5fa6125845350caf596ed6'), '_lock');
        if($doc === null)
            echo 'document not found!';
        else{
            #The document is locked and you can have a safe update
        }
    }
    catch(\Exception $e){
        #see https://github.com/yiisoft/yii2-mongodb/pull/306
        if(ErrorCode::is($e,ErrorCode::WriteConflict))
            echo 'This is a mongodb write conflict error.';
    }
},[
    'readConcern' => 'snapshot',
    'writeConcern' => 'majority',
]);

Stubbornly lock feature
When doc1 is locked in a transaction(t1) and when other transactions(t2) want to update doc1, they will confront 'writeConflict' error. if you don't want to have a  'writeConflict' error , you can use the 'stubbornly lock' feature in application level.
this feature will wait until the document unlocks.
#notice : you can not use stubborn mode if transaction is started in current session(or use your session with `mySession` parameter).
#starts new transaction in current session(create new session if it doesn't exist)
$doc = MyActiveRecordClass::LockDocumentStubbornly('5e652b4a81eb9b37cac99a2b','_lock',[
    'mySession' => [],        #a custom session instance of ClientSession for starting a transaction.
    'modifyOptions' => [],    #see $options in ActiveQuery::modify()
    'sleep' => 1000000,       #a time parameter in microseconds for waiting. the default is one second.
    'try' => 0,               #maximum number of retrying. throw write conflict error after it has reached this value. the zero default is unlimited.
    'transactionOptions' => [ #new transaction options. see $transactionOptions in Transaction::start()
        'readConcern' => 'majority',
        'writeConcern' => 'majority',
    ]
]);
$doc->f1++;
$doc->Save();
yii::$app->mongodb->CommitTransaction();

Tests seems to fail: https://github.com/yiisoft/yii2-mongodb/pull/294/checks?check_run_id=484726582

@samdark for fixing this errors , i must be change version of mongodb to 4.0 (also mongodb php driver to 1.5).
do problem solved if i change .travis.yml:28 to - mongodb-4.0-precise ?
please see MongoDB Compatibility

@ziaratban you can try adjusting .travis.yml and pushing it. Travis will automatically pick it up so you'll see results after test run.

@samdark
Test on php 5.5 and 5.6 fails because the test environment has bugs.
please see #316 .

Thank you @ziaratban for the PR
Is there any update for this?

Thank you @ziaratban for the PR Is there any update for this?

I think it is over and I am waiting for @samdark to have a code review and I have been using this feature in my products for about a year now.
If you have a code to add, we will be very happy.

@ziaratban thanks for patience and sorry it takes so long.

Overall it looks alright but, it seems, public interfaces are changed so that should be a major release. Right?

Overall it looks alright but, it seems, public interfaces are changed so that should be a major release. Right?

Of course!

Merged. Thank you for working on it.


Support for advertising

Currently the library supports master/scan/central role, but not the slave/advertise/peripheral role.
Android supports this in the 5.0 (Lollipop) preview, so Xamarin should support it too.

This project is open-source ~ we have already had some great contributions from the community.
Note that this project is intended to a cross-platform library that abstracts a BLE API so that iOS, Android, and Windows Phone can use it. Therefore any functionality that is surfaced needs to be available on all three platforms.
I'm not aware if the slave/advertise/peripheral role is already present in iOS and Windows Phone... but if it is only available on Android 5.0 and newer, that still severely limits its usefulness in the short term.

Not clear to me if this has been implemented yet? I know for a fact that iOS and android support the peripheral mode now. Can someone please clarify?


Hologram  dissappears from Cliff House after adding a second one

It has come to my attention that when I insert an Hologram to the Cliff House from the 3D Viewer App and exit the Mixed reality app and re-enter it and add a second hologram and exit mixed reality that when I open the app again the first hologram disappears from the original spot I placed it. When I move the controller to the spot of the first Hologram and "click" on it even though it is no longer visible, the first Hologram re-appears but with an error message that it cannot be placed there.

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

ID: 7e0a0135-d443-a905-bd6a-5f6700afb4e4
Version Independent ID: 27962279-8d07-cc59-a870-a58f37df7142
Content: Give us feedback - Mixed Reality
Content Source: mixed-reality-docs/give-us-feedback.md
Product: mixed-reality
GitHub Login: @mattzmsft
Microsoft Alias: mazeller

I have a similar problem. I used the 3D Viewer App and after rebooting my device the holograms were still there, but not alaways visible any more. The error that is displayed sometimes: "This hologram could not be placed"


threshold_match_weight in linker.predict() not checked when equal to 0

What happens?
Weird edge case, but when calling linker.predict with a threshold_match_weight of 0 to remove negative weighted records, the threshold isn't applied and it returns all records. There is a logical check on threshold_match_weight but it should check that threshold_match_weight is not None, to handle the case it may be set to zero.
https://github.com/moj-analytical-services/splink/blob/868fefba022483f4cb0d05822aa55d62ee9b92fa/splink/predict.py#L58
To Reproduce
From the rough and ready example, last two lines of interest.
from splink.datasets import splink_datasets
from splink.duckdb.linker import DuckDBLinker
from splink.duckdb.blocking_rule_library import block_on
import splink.duckdb.comparison_library as cl

df = splink_datasets.historical_50k

settings = {
    "link_type": "dedupe_only",
    "blocking_rules_to_generate_predictions": [
        block_on("full_name"),
        block_on(["substr(full_name,1,6)", "dob", "birth_place"]),
        block_on(["dob", "birth_place"]),
        block_on("postcode_fake"),
    ],
    "comparisons": [
        cl.jaro_at_thresholds("full_name", [0.9, 0.7], term_frequency_adjustments=True),
        cl.levenshtein_at_thresholds("dob", [1, 2]),
        cl.levenshtein_at_thresholds("postcode_fake", 2),
        cl.jaro_winkler_at_thresholds("birth_place", 0.9, term_frequency_adjustments=True),
        cl.exact_match("occupation",  term_frequency_adjustments=True),
    ],
}

linker = DuckDBLinker(df, settings)
deterministic_rules = [
    "l.full_name = r.full_name",
    "l.postcode_fake = r.postcode_fake and l.dob = r.dob",
]

linker.estimate_probability_two_random_records_match(deterministic_rules, recall=0.6)
linker.estimate_u_using_random_sampling(max_pairs=2e7)

results = linker.predict(threshold_match_weight=0) # set threshold weight to 0

assert results.as_pandas_dataframe()['match_weight'].min() >= 0 # Fails if there are still negative weights

OS:
Windows 10
Splink version:
3.9.8
Have you tried this on the latest master branch?

[X] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] I agree

Thanks for the report! If you are happy to feel free to put in a PR with the fix for this.
Otherwise someone from the team will have a look into it when there's some space to do so


PS script to upload pypi packages

would it make sense to have a mode for the script which can print the list of potential wheels it may publish ? This can help the user to get an understanding of the wheels he may end up publishing once the script runs.

in vsts cli repo, most of the scripts are py scripts..
ps1 seems to be odd one out
not that I have any issues with that :) but just pointing out

I am not very sure if this kind of script should go in repo or in the CI/CD pipeline somewhere
because most of the contributors/ developers can't/ won't run it..
like normal contributes cannot update the pypi for vsts packages, it will always be just a handful of users who can do that


Liquibase failed when apostrophe char in table container name

Environment
Liquibase Version: Community 4.2.0 and newest PRO version
Liquibase Integration & Version: CLI
Database Vendor & Version: PostgreSQL 12, MySQL 5.5
Operating System Type & Version: Windows 10
Description
I can't properly compare schemas/databases containing apostrophe chars (single quotes) in their names with liquibase diffChangeLog command in some cases.
Steps To Reproduce

Create the database with the name "test's" in PostgreSQL
Add
url: jdbc:postgresql://localhost:5432/test's
referenceUrl: jdbc:postgresql://localhost:5432/postgres
to properties file (with other neseccery properties)
use liquibase diffChangeLog command in CLI in community version

or

Create the database with the name "test's" in MySQL and database "test"
Add
url: jdbc:mysql://localhost:3306/test's
referenceUrl: jdbc:mysql://localhost:3306/test
to properties file
use liquibase diffChangeLog command in CLI with liquibaseProLicenseKey parameter

Actual Behavior
The error appears for PostgreSQL:
Unexpected error running Liquibase: liquibase.exception.DatabaseException: org.postgresql.util.PSQLException: Unterminated string literal started at position 195 in SQL select CONSTRAINT_NAME, TABLE_NAME from information_schema.table_constraints where constraint_catalog='test's' and constraint_schema='public' and constraint_type='UNIQUE' and table_name='newtable'. Expected  char

MySQL:
liquibase.exception.DatabaseException: Error executing SQL select action_statement as OBJECT_BODY, trigger_name as OBJECT_NAME, event_object_table as TABLE_NAME, event_object_schema as TABLE_OWNER, event_manipulation as TRIGGERING_EVENT, action_timing as WHEN_CLAUSE FROM INFORMATION_SCHEMA.TRIGGERS WHERE trigger_schema = 'test's';: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's'' at line 1

Small comment: diffChangeLog works fine with MySQL 5.5 with community version.
Expected/Desired Behavior

Liquibase command 'diffChangeLog' was executed successfully.

Screenshots (if appropriate)

Additional Context
Add any other context about the problem here.

https://github.com/liquibase/liquibase/issues/1640 may be some connection is with this ticket.

Hi @LonwoLonwo Thanks for writing up this issue.  We will add it to the list of issues that we are processing.  In the meantime can you create and use databases that do not have an apostrophe in the name?

Ok @molivasdat
Thanks for the advice.

Looks like the issue still exists on liquibase 4.14.  I got a different error msg:
Unexpected error running Liquibase: Error executing SQL SELECT replace(CAST(conrelid::regclass as text), n.nspname || '.','') AS TABLE_NAME, conname as CONSTRAINT_NAME,  replace(pg_get_constraintdef(c.oid),'CHECK ','') as SEARCH_CONDITION, 'ENABLED' AS STATUS FROM pg_constraint c  JOIN   pg_namespace n ON n.oid = c.connamespace   WHERE  contype IN ('c') AND n.nspname = 'test's'  AND conrelid <> '-'::regclass  ORDER  BY conrelid::regclass::text, contype DESC: Unterminated string literal started at position 344 in SQL SELECT replace(CAST(conrelid::regclass as text), n.nspname || '.','') AS TABLE_NAME, conname as CONSTRAINT_NAME,  replace(pg_get_constraintdef(c.oid),'CHECK ','') as SEARCH_CONDITION, 'ENABLED' AS STATUS FROM pg_constraint c  JOIN   pg_namespace n ON n.oid = c.connamespace   WHERE  contype IN ('c') AND n.nspname = 'test's'  AND conrelid <> '-'::regclass  ORDER  BY conrelid::regclass::text, contype DESC. Expected  char

Hello @FBurguer
I think, the message depends on a database.
The main issue here - that catalog name is not quted in statements and other places.

But thanks for the interest to my issue. It is still actual for me.


TS7016: Could not find a declaration file for module 'webpack-bundle-tracker'. '.../node_modules/webpack-bundle-tracker/index.js' implicitly has an 'any' type.

I'm trying to make use of webpack-bundle-tracker with a typescript configuration for webpack.
It seems typescript is not happy, because it spits out the message mentioned above and exists with a non-zero exit code.
I assume webpack-bundle-tracker needs to ship a type definition file for it to be happy.

Am having the same issue, Any help Please?

Also got
ERROR in /mnt/c/Users/tony/..../webpack.common.ts(9,27):
TS7016: Could not find a declaration file for module 'webpack-bundle-tracker'. '/mnt/c/Users/tony/.../node_modules/webpack-bundle-tracker/index.js' implicitly has an 'any' type.
  Try `npm install @types/webpack-bundle-tracker` if it exists or add a new declaration (.d.ts) file containing `declare module 'webpack-bundle-tracker';`
Version: typescript 3.4.3, tslint 5.15.0

If anyone wants to contribute a typescript definition file, feel free to do it in this repo.
If not, you can also contribute it to https://github.com/DefinitelyTyped/DefinitelyTyped
Second you can post it as a gist so we can use it.

This is my stab at it:
I am very very green when it comes to defining new types. I am likely wrong:
import { Plugin } from 'webpack'

declare module 'webpack-bundle-tracker';

export = WebpackBundlePlugin

declare class WebpackBundlePlugin extends Plugin {
  constructor(options?: WebpackBundlePlugin.Options)
}

declare namespace WebpackBundlePlugin {
  interface Options {
    filename?: string;
    logTime?: boolean;
    path?: string;
    publicPath?: string;
  }
}

Another thing I tried, inspired off this autogenerated stub: https://github.com/mazurbeam/django-react-forum/blob/master/frontend/flow-typed/npm/webpack-bundle-tracker_vx.x.x.js
import { Plugin } from 'webpack'

declare module 'webpack-bundle-tracker' {
  declare module.exports = WebpackBundlePlugin

        declare class WebpackBundlePlugin extends Plugin {
                constructor(options?: WebpackBundlePlugin.Options)
        }

        declare namespace WebpackBundlePlugin {
                interface Options {
                        filename?: string;
                        logTime?: boolean;
                        path?: string;
                        publicPath?: string;
                }
        }
}

declare module 'webpack-bundle-tracker/index' {
  declare module.exports: $Exports<'webpack-bundle-tracker'>;
}

declare module 'webpack-bundle-tracker/index.js' {
  declare module.exports: $Exports<'webpack-bundle-tracker'>;
}

Thanks to @melck, we do ship type definition now. It's not released yet but you can test latest code from master and let us know if it works.


Merge CI.next branch into master

We've been using these cinext branch changes for a few weeks now during CI.next development.
We're ready to merge into master and cut a gem release so we can stop pinning projects to the cinext branch on GitHub and just have them depend on the new gem release like normal.

@puppetlabs/cinext for review / merge.


TODO keyword is invisible when being visually highlighted

The reason is that they used the same color as shown below:
https://github.com/rebelot/kanagawa.nvim/blob/c19b9023842697ec92caf72cd3599f7dd7be4456/lua/kanagawa/highlights/editor.lua#L125
https://github.com/rebelot/kanagawa.nvim/blob/c19b9023842697ec92caf72cd3599f7dd7be4456/lua/kanagawa/highlights/syntax.lua#L78
https://github.com/rebelot/kanagawa.nvim/blob/c19b9023842697ec92caf72cd3599f7dd7be4456/lua/kanagawa/themes.lua#L112
https://github.com/rebelot/kanagawa.nvim/blob/c19b9023842697ec92caf72cd3599f7dd7be4456/lua/kanagawa/themes.lua#L95

I also suffer from this problem. Have you solved it? If so, can you tell me your solution?

This is what I temporarily used:
         overrides = function(C)
             local T = C.theme
+            local P = C.palette

             return {
                 -- https://github.com/rebelot/kanagawa.nvim#dark-completion-popup-menu
@@ -25,7 +26,9 @@ return {
                 PmenuSbar = { bg = T.ui.bg_m1 },
                 PmenuThumb = { bg = T.ui.bg_p2 },

+<EMAIL_ADDRESS>= { fg = P.fujiWhite },
<EMAIL_ADDRESS>= { link =<EMAIL_ADDRESS>},
+                Todo = { fg = P.fujiWhite },
             }

Awesome! Thank you bro


Common code across plugins

For kn-source-kafka and kn-source-github and various planned plugins, @daisy-ycguo and I have a common set of code we use as kn-source-pkg. We would like to have this here.
While kn-source-pkg is structured like a plugin, it is not. So putting it in this repo’s plugins directory would not be correct. So I am suggesting we create a top level lib directory (like we did for client and put it there. This could also serve for a good place for other such common code.
Thoughts? Please respond soon. I will leave this open after Thursday like the other recent global issues for this repo.

@daisy-ycguo, @rhuss, @navidshaikh See ^^^
Please comment if you have different suggestions or opinions. Thursday’s TOC will also help in case we decide something different.

This is duplicate to #56 since that same repo should contain all common code. So closing this.


⚠ Bofrost.at has degraded performance

In 7da23ca, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 914 ms

Resolved: Bofrost.at performance has improved in 27c4a40.


Telemetry CR in UI

Description
Add UI extension for Telemetry CRD.
ACs:

[ ] it is possible to manage Telemetry CR using Kyma dashboard
[ ] UI is tested with automated test
[ ] enhance access logs operational guide with UI instructions

Reasons
Improve UX of Istio module
DoD:

[ ] Provide unit and integration tests.
[ ] Provide documentation.
[ ] Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
[ ] If you changed the resource limits, explain why it was needed.
[ ] Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
[ ] Add release notes.

Attachments
https://kyma-project.io/#/istio/user/operation-guides/02-30-enable-istio-access-logs
https://istio.io/latest/docs/reference/config/telemetry/
https://github.com/kyma-project/istio/tree/main/config/ui-extensions

I assume not all options should be supported in the form view as they are not part of any documented use case. We should select wisely and promote the settings important for our flows like the simple activation of access logs using the predefined provider (not any custom provider)


[todo-mvvm-databinding_newarch] New branch which uses new android arch components

New branch: todo-mvvm-databinding_newarch
I have made an attempt to integrate the new arch components into the todo-mvvm-databinding. So, all the ViewModels now extend android.arch.lifecycle.ViewModel.
The original plan was to remove the Observables all together and use LiveData only but it came out that Livedata doesnt support databinding as of now.

So all the observables which were interacting with data-binding are still as is.
The snackbarText is implemented using LiveData
All the @Bindable methods are now removed and are instead implemented as Observables (only for now). Once the android lifecycle hits 1.0 stable api we can remove all the observables and use LiveData only.
Next, I would want to integrate the android.arch.persistence.room for Tasks storage.

Please don't create PR against existing samples, create a new one in your own repo and post it in the issue. Thanks!

@JoseAlcerreca Sorry, I didnt get you. You want to me to first create a pull request in my own repo and then post it in the issues #337 and/or #343 ?
Please correct me if I am wrong. Thanks!


ec_deployment: Remove APM secret_token from config

Description

Removes the secret_token and secret_token parsing from the config
blob under the apm object.
Instead of relying on the GET /deployment/<id> to populate the field,
it is instead parsed from the Create / Update API response, saving
it to a key named apm_secret_token.
Updates the tests and the defined Deployment version.
Related Issues

Resolves #56
Types of Changes

[x] Breaking change (fix or feature that would cause existing functionality to change)

$ make testacc
-> Formatting Go files...
-> Formatting Terraform documentation blocks...
-> Done.
-> Running terraform acceptance tests...
=== RUN   TestAccDatasourceDeployment_basic
=== PAUSE TestAccDatasourceDeployment_basic
=== RUN   TestAccDeployment_basic
=== PAUSE TestAccDeployment_basic
=== RUN   TestAccDeploymentTrafficFilter_basic
=== PAUSE TestAccDeploymentTrafficFilter_basic
=== CONT  TestAccDatasourceDeployment_basic
=== CONT  TestAccDeploymentTrafficFilter_basic
=== CONT  TestAccDeployment_basic
--- PASS: TestAccDeploymentTrafficFilter_basic (13.89s)
--- PASS: TestAccDatasourceDeployment_basic (575.68s)
--- PASS: TestAccDeployment_basic (954.22s)
PASS
ok  	github.com/terraform-providers/terraform-provider-ec/ec/acc	955.125s


Challenge http://www.freecodecamp.com/challenges/waypoint-add-different-padding-to-each-side-of-an-element has an issue

Please tell us in detail here how we can make this challenge better. Padding-right should say 20px in directions on the bottom, it says 40px.

Thanks, this is a duplicate of several opened and closed issues and has been addressed in a commit and will be released soon!


Any way to connect to an account using email and password?

Title ^

Yes, you can supply a password field per prismarine-auth. However, this is not a reliable form of authentication.


installed nextjs for frontend

installed nextjs for frontend
Next.js is a powerful React framework for building fast, scalable, and server-side-rendered web applications.
Reasons why nextjs is a game changer!

[ ] Server-side Rendering (SSR): Next.js offers built-in SSR, allowing pages to be rendered on the server and delivered to the
client as fully rendered HTML. This improves SEO, performance, and enables faster initial page loads.
[ ] Static Site Generation (SSG): With Next.js, you can pre-render entire pages at build time, resulting in static HTML files. This approach ensures incredible performance, as the server doesn't need to regenerate the page for each request.
[ ] Automatic Code Splitting: Next.js automatically splits code into smaller chunks, loading only the required JavaScript for each page. This reduces initial bundle size and speeds up page loads.
[ ] API Routes: Next.js provides a simple way to create serverless API endpoints directly within the application, streamlining the process of developing backend functionality.
[ ] And much more.

If there is any additional information that is relevant

Thanking you, am happy to work on your project for self improvement.

Yes bro, though I installed the nextjs application purposely on the home directory , I will  move it in the front end folder.
But it gonna cause some issues on the react files installed on the front end while starting react.
May be I will get read of all the react files,  fix nextjs install folder into the front end directory making nextjs permanent application for the frontend.
If there is any additional information that is relevant

Yes bro, though I installed the nextjs application purposely on the home directory , I will move it in the front end folder. But it gonna cause some issues on the react files installed on the front end while starting react.
May be I will get read of all the react files, fix nextjs install folder into the front end directory making nextjs permanent application for the frontend.

alright.
Resolve it before I merge

Yes bro, though I installed the nextjs application purposely on the home directory , I will move it in the front end folder. But it gonna cause some issues on the react files installed on the front end while starting react.
May be I will get read of all the react files, fix nextjs install folder into the front end directory making nextjs permanent application for the frontend.

alright. Resolve it before I merge

or rather, make a new pr for it @OLINYA-PAUL


Allow multiple mappings for source elements

Clearing out everything seems to work but the 'Select mapping' dropdown appears so the user can distinguish which mapping they want:

Yep, until we address #635 it's a bit annoying, but from functionality this is better I would say.


catch error in multi-query batches

Fixes: #139, #135
#124 modified core adapter macros (e.g.create_view_as()) to be multi-query batches that were previously single queries.
This PR attempts to use @jeroen-mostert's solution to iteration through each query in a query batch looking for errors

@jtcohen6, I'm struggling with how to fetch then handle the pyodbc's ProgrammingError exception. More generally I'm trying to understand how the SQLConnectionManager class works with query batches...
current approach to fixing
I've implemented @jeroen-mostert's approach. I'm not exactly sure what cursor.nextset() does, but when you call it on a batch query where the 2nd query has a syntax error, the pyodbc Programming Error exception pops up... This error doesn't surface if you only call query.exectue()
this PR now surfaces an "unhandled" error, but doesn't return the Database Error line about where the error occurred.

desired (and previous state)
this is what the output should look like using a version of dbt-sqlserver before the adapter macros had query batches.

alternative solution split the queries and add/execute them independently?
One approach would be to implement something like SnowflakeConnectionManager._split_queries(), but my reservations are:

would this work for an adapter macro like sqlserver__create_view_as()
will executing a database switch command in two different batches work (I have to test this w/ a SQL Server instance)
where does snowflake.connector.util_text.split_statements() come from?

If it helps (actually I'm pretty sure it doesn't but I'm putting it out here anyway :-)) there's something weird with how pyodbc treats multi-statement batches for SQL Server. Calling .nextset() advances to the next result set of a batch -- this is a general mechanism surfaced also in, for example, .NET's SqlDataReader.NextResult(). However, this should not generally be necessary for statements that do not produce result sets -- USE [database]; SELECT 1 a is an example of a batch with two statements that produces one result set, not two. In .NET you would never need to call .NextResult() to make this batch return, but for some reason pyodbc will treat every statement result as a distinct result set, even if the statement just completed and nothing more. And instead of surfacing execution errors, it will treat an error that results from .nextset() as a programming error (?). Basically, pyodbc demands that you know in advance exactly how many statements you have and what each of them will return even if they don't return anything, which is quite a nasty restriction that I haven't seen in DB libs for other languages.
All this is not to suggest this is something that could or should be changed in the pyodbc layer just to make dbt happy, of course, since that might be quite impactful; executing individual statements is still the safest way to go. A USE database persists on the connection across batches, provided of course that 1) you do not close it and open a new one and 2) you do not use a separate EXEC for the statement, as that gets its own context and the DB is reverted at the end. (EXEC 'USE db; <other stuff>' works, of course, but you'll probably run into the same multi-statement result set gotchas again.)
Parsing batches and splitting them manually on anything but a dedicated batch separator like good old GO requires a T-SQL parser with full fidelity if there's any chance your statements contain escaped or quoted semicolons anywhere; I wouldn't recommend that path. T-SQL's a hideously byzantine language and the fact that the statement separator is mostly optional doesn't help; you really want to split your statements on a higher level if possible.

Awesome fix! 👍 Faced with this today in my work with snapshot functionality.

@jeroen-mostert I really find myself agreeing. It's not good how pyodbc treats errors from multi-statement batches. It's also preferable, wherever possible, to supply individual queries one at a time, so long as they can be executed within a single transaction/session. EXEC perhaps can't be helped. Lacking other alternatives, pushing the error to stdout, even if imperfectly, is still a huge improvement.

where does snowflake.connector.util_text.split_statements() come from?

That comes from the Snowflake python connector here. The logic in this method is somewhere between "just split on semicolon" and "SQL parser with full fidelity." If I remember right, the Snowflake python connector does not properly handle multiple query statements at once (semicolon-delimited), so this is what we have to use instead.

Thank you for pushing this up!
Sorry I didn't give better instructions for how to reproduce the error :D
So far (even with the cursor2 oddity) runs with this new setup, and I'm seeing failures where I would expect now. And I'm catching errors I was missing :O
(installed on a new venv with
pip install git+https://github.com/dbt-msft/dbt-sqlserver.git@cb12056e18ad60859eeaa34217bc3a8762551d02  , is there an easier way to install over an existing installation? pip install --upgrade  git+https://github.com/dbt-msft/dbt-sqlserver.git@cb12056e18ad60859eeaa34217bc3a8762551d02 wasn't doing it for me, and cloning and running python setup.py install wasn't either (it looked like pip thought the existing package was the most recent)

Noticed another regression but it's not related to this (Caught because of this fix though).  https://github.com/dbt-msft/dbt-sqlserver/issues/143

Using this right now in my environment. So far so good, I've caught 20 plus errors I was missing :O

@jeroen-mostert, you are my hero -- not only for the fix but the depth of knowledge you were able to share. You certainly make me feel a lot saner, now that I know that both pyodbc and TSQL are at fault here.
That said, these EXEC statements are only needed to support the multi-database scenario that is only possible with on-premise SQL Server. There's a part of me that wants to kick this behavior into it's own adapter (dbt-sqlserver-multi-db) so single-database SQL Server users and Azure SQL users don't have to experience this workaround stdout behavior. @jtcohen6 @periclesrocha, the database version telemetry MSFT has on connections coming from dbt would greatly inform the right path to take...
For now, we should definitely merge and release this to everyone. @mikaelene would you do the honors of releasing a v0.19.2 once this is merged?


Missing documentation

Missing documentation
Relevant URLs

https://docs.influxdata.com/telegraf/v1.22/administration/configuration/

What products and version are you using?

Telegraf issues at https://github.com/influxdata/telegraf

Duplicate of #3983
Closing.


Day48: Number of Substrings Containing All Three Characters - SlidingWindow

Number of Substrings Containing All Three Characters
https://leetcode.com/problems/number-of-substrings-containing-all-three-characters/
Given a string s consisting only of characters a, b and c.
Return the number of substrings containing at least one occurrence of all these characters a, b and c.

Example 1:
Input: s = "abcabc"
Output: 10
Explanation: The substrings containing at least one occurrence of the characters a, b and c are "abc", "abca", "abcab", "abcabc", "bca", "bcab", "bcabc", "cab", "cabc" and "abc" (again).
Example 2:
Input: s = "aaacb"
Output: 3
Explanation: The substrings containing at least one occurrence of the characters a, b and c are "aaacb", "aacb" and "acb".
Example 3:
Input: s = "abc"
Output: 1


HTTPS/Adsense

What needs to be edited to make this scoreboard HTTPS?  I have been attempting to make an instance of this HTTPS and add google analytics and adsense to it with no success.  Any help would be greatly appreciated.  Thanks in advance.

HTTPS should be straight forward, if you're using appengine, setting
secure: always should do the trick, along with some config modifications.
As for adsense, It's likely you'll need to add a custom CSP policy so that
adsense can load javascript / do whatever it does.
Take a look at
https://github.com/google/ctfscoreboard/blob/013018c3685cc6a42daf5c6b81c42c45ebb39264/scoreboard/config_defaults.py#L21
and
https://github.com/google/ctfscoreboard/blob/14b276213c9aa628d26f3da56a42fe62460eb619/scoreboard/context.py#L28
and that should give you an idea of what you need to do. You'll probably
want to enable developer tools in your browser to see what is causing
conflicts.
On Tue, May 9, 2017 at 8:29 AM, HackMethod<EMAIL_ADDRESS>wrote:

What needs to be edited to make this scoreboard HTTPS? I have been
attempting to make an instance of this HTTPS and ad google adsense to it
with no sucess. Any help would be greatly appreciated. Thanks in advance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/ctfscoreboard/issues/126, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKVZCRwYXZVfJlFP4ywCs0LZ1ZHqWSP3ks5r4IZZgaJpZM4NVfGv
.

I think I may have been editing the wrong nginx.conf (not the doc/nginx.conf) when attempting HTTPS, I will revisit this issue.
The CSP is very new to me and I am not entirely certain what I am looking at when those lines.  I did run developer tools and just noticed the "blocked" portion on any adsense or google metrics I had added to the base page.  Any chance you have a tutorial on writing a custom CSP policy before I start googling my heart out?

Sorry, I don't have any specific advice on what your policy should look
like.
On Tue, May 9, 2017 at 9:13 AM, HackMethod<EMAIL_ADDRESS>wrote:

I think I may have been editing the wrong nginx.conf (not the
doc/nginx.conf) when attempting HTTPS, I will revisit this issue.
The CSP is very new to me and I am not entirely certain what I am looking
at when those lines. I did run developer tools and just noticed the
"blocked" portion on any adsense or google metrics I had added to the base
page. Any chance you have a tutorial on writing a custom CSP policy before
I start googling my heart out?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/ctfscoreboard/issues/126#issuecomment-300216869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKVZCbN0Rkn3GWK45KvfO7FjCkd3uRivks5r4JCsgaJpZM4NVfGv
.


Mongolia International University

@sinclaireo First stage of verification passed, official domain is instagram.com as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.instagram.com/2002_miukorea/

When I try to apply and put<EMAIL_ADDRESS>on the email address it says "Your email address does not belong to any university that we know. You can apply with another method (see tabs above) or add your school to JetBrains' list."
How can I resolve this?

Can you please help me?

@sinclaireo Pull request merged. Thank you.
Please wait at least 60 minutes after you received this message. Then please apply again. Thank you.


[BUG] MultiFileCloudParquetPartitionReader can trigger NPE

Describe the bug
One of the nightly pipelines that uses an S3 input recently crashed with the following exception:
17:22:13  Caused by: java.lang.NullPointerException
17:22:13  	at org.apache.hadoop.fs.s3a.S3AInputStream.lambda$read$3(S3AInputStream.java:450)
17:22:13  	at org.apache.hadoop.fs.s3a.Invoker.once(Invoker.java:109)
17:22:13  	at org.apache.hadoop.fs.s3a.Invoker.lambda$retry$3(Invoker.java:265)
17:22:13  	at org.apache.hadoop.fs.s3a.Invoker.retryUntranslated(Invoker.java:322)
17:22:13  	at org.apache.hadoop.fs.s3a.Invoker.retry(Invoker.java:261)
17:22:13  	at org.apache.hadoop.fs.s3a.Invoker.retry(Invoker.java:236)
17:22:13  	at org.apache.hadoop.fs.s3a.S3AInputStream.read(S3AInputStream.java:446)
17:22:13  	at java.io.DataInputStream.readFully(DataInputStream.java:195)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.copyDataRange(GpuParquetScan.scala:509)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.copyDataRange$(GpuParquetScan.scala:497)
17:22:13  	at com.nvidia.spark.rapids.MultiFileCloudParquetPartitionReader.copyDataRange(GpuParquetScan.scala:975)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.$anonfun$copyBlocksData$3(GpuParquetScan.scala:580)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.$anonfun$copyBlocksData$3$adapted(GpuParquetScan.scala:580)
17:22:13  	at scala.collection.mutable.ResizableArray.foreach(ResizableArray.scala:62)
17:22:13  	at scala.collection.mutable.ResizableArray.foreach$(ResizableArray.scala:55)
17:22:13  	at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:49)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.copyBlocksData(GpuParquetScan.scala:580)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.copyBlocksData$(GpuParquetScan.scala:525)
17:22:13  	at com.nvidia.spark.rapids.MultiFileCloudParquetPartitionReader.copyBlocksData(GpuParquetScan.scala:975)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.$anonfun$readPartFile$3(GpuParquetScan.scala:669)
17:22:13  	at com.nvidia.spark.rapids.Arm.closeOnExcept(Arm.scala:87)
17:22:13  	at com.nvidia.spark.rapids.Arm.closeOnExcept$(Arm.scala:85)
17:22:13  	at com.nvidia.spark.rapids.FilePartitionReaderBase.closeOnExcept(GpuMultiFileReader.scala:236)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.$anonfun$readPartFile$2(GpuParquetScan.scala:666)
17:22:13  	at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:28)
17:22:13  	at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:26)
17:22:13  	at com.nvidia.spark.rapids.FilePartitionReaderBase.withResource(GpuMultiFileReader.scala:236)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.$anonfun$readPartFile$1(GpuParquetScan.scala:664)
17:22:13  	at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:28)
17:22:13  	at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:26)
17:22:13  	at com.nvidia.spark.rapids.FilePartitionReaderBase.withResource(GpuMultiFileReader.scala:236)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.readPartFile(GpuParquetScan.scala:663)
17:22:13  	at com.nvidia.spark.rapids.ParquetPartitionReaderBase.readPartFile$(GpuParquetScan.scala:658)
17:22:13  	at com.nvidia.spark.rapids.MultiFileCloudParquetPartitionReader.readPartFile(GpuParquetScan.scala:975)
17:22:13  	at com.nvidia.spark.rapids.MultiFileCloudParquetPartitionReader$ReadBatchRunner.call(GpuParquetScan.scala:1043)
17:22:13  	at com.nvidia.spark.rapids.MultiFileCloudParquetPartitionReader$ReadBatchRunner.call(GpuParquetScan.scala:999)
17:22:13  	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
17:22:13  	... 3 more

It may be impacted by the service down of internal s3. Assign to Bobby W first. Let's check it after the service is back.

Let's check it after the service is back.

I disagree. This is an NPE.  Software should never throw an NPE to the user.  We need to walk the stacktrace to determine what was null to cause the NPE to be thrown and whether our software triggered the null dereference in the S3 client (e.g.: by passing null buffers, trying to use the connection after it was closed, etc.).  If the NPE was solely a problem in the S3 client then there's not much for us to do other than recommend users upgrade if they are hit by this condition, but if our software triggered it indirectly then we need to fix it.  Waiting for the S3 service to be restored and seeing it work afterwards does not necessarily mean a bug doesn't exist in our software.

Let's check it after the service is back.

I disagree. This is an NPE. Software should never throw an NPE to the user. We need to walk the stacktrace to determine what was null to cause the NPE to be thrown and whether our software triggered the null dereference in the S3 client (e.g.: by passing null buffers, trying to use the connection after it was closed, etc.). If the NPE was solely a problem in the S3 client then there's not much for us to do other than recommend users upgrade if they are hit by this condition, but if our software triggered it indirectly then we need to fix it. Waiting for the S3 service to be restored and seeing it work afterwards does not necessarily mean a bug doesn't exist in our software.

Got it. @wbo4958 Can you check the call stack and figure out where caused the NPE?

From the exception stack and the code,
It seems the wrappedStream is null. Looks like when one thread is trying to read, the other thread has closed the Stream.
But the DEBUG log is not enabled, I can't find any suspicious log.
BTW,  When this issue happened, our swiftstack is unstable. And the issue is gone when swiftstack is stable.
@tgravescs Would you help to look at this issue?

so taking a look it would have had to have closeStream called on it. The S3AInputStream does have a OnReadFailure.reopen call which would close it and attempt to create new one.  This is called from the retry logic there.
It does seem like on the reopen call that they check to make sure the wrappedStream came back as non-null:
https://github.com/apache/hadoop/blob/f6c4e006cd1190e27fadbe0a38ce09782f45ca04/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInputStream.java#L186
If that line number is right though it wasn't in the reopen case so perhaps it just got closeStream called on it by someone else.
We open the file in a single thread, its not shared across threads so it shouldn't be our code closing during read.
I think we'd have to rebuild it with some debugging to see for sure.

I tried to repro this issue locally by breaking the network connection but failed to repro. :(

I found Hadoop-aws may have  a corner case can result in the NPE issue,
Before NPE happened, there were other exceptions happened, see below
21/07/12 22:19:17 INFO S3AInputStream: Got exception while trying to read from stream XXX trying to recover: javax.net.ssl.SSLException: Read timed out

when reading from S3 storage, SSLException (which extends IOException) happens, which will trigger onReadFailure.
onReadFailure calls reopen. it will first close the original wrappedStream and set wrappedStream = null, and then it will try to re-get wrappedStream.  But what if the previous code obtaining S3Object throw exception, then "wrappedStream" will be null.
And the retry mechanism may re-execute the wrappedStream.read and cause NPE.
I will try to verify my guess by hacking some code.

Good progress. From the code, it seems possible. If we can understand the retryPolicy, it'll help.
If so, I think it should be a bug in hadoop aws.

diff --git a/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInputStream.java b/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInputStream.java
index 68f98e4abea..d615d9a5c95 100644
--- a/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInputStream.java
+++ b/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInputStream.java
@@ -157,7 +157,7 @@ private void setInputPolicy(S3AInputPolicy inputPolicy) {
    */
   @Retries.OnceTranslated
   private synchronized void reopen(String reason, long targetPos, long length,
-          boolean forceAbort) throws IOException {
+          boolean forceAbort, boolean hack) throws IOException {

     if (wrappedStream != null) {
       closeStream("reopen(" + reason + ")", contentRangeFinish, forceAbort);
@@ -181,6 +181,9 @@ private synchronized void reopen(String reason, long targetPos, long length,
         (opencount == 0 ? "open" : "re-open"), uri, targetPos);
     S3Object object = context.getReadInvoker().once(text, uri,
         () -> client.getObject(request));
+    if (hack) {
+      throw new IOException("reopen hack");
+    }
     wrappedStream = object.getObjectContent();
     contentRangeStart = targetPos;
     if (wrappedStream == null) {
@@ -325,7 +328,7 @@ private void lazySeek(long targetPos, long len) throws IOException {

           //re-open at specific location if needed
           if (wrappedStream == null) {
-            reopen("read from new offset", targetPos, len, false);
+            reopen("read from new offset", targetPos, len, false, false);
           }
         });
   }
@@ -403,7 +406,7 @@ private void onReadFailure(IOException ioe, int length, boolean forceAbort)
     LOG.info("Got exception while trying to read from stream {}" +
         " trying to recover: " + ioe, uri);
     streamStatistics.readException();
-    reopen("failure recovery", pos, length, forceAbort);
+    reopen("failure recovery", pos, length, forceAbort, true);
   }

   /**
@@ -448,6 +451,9 @@ public synchronized int read(byte[] buf, int off, int len)
           int bytes;
           try {
             bytes = wrappedStream.read(buf, off, len);
+            if (bytes >= -10000) {
+              throw new IOException("Hacked --- ");
+            }
           } catch (EOFException e) {
             // the base implementation swallows EOFs.
             return -1;

After applying the patch by simulating the exceptions, I can repro the NPE everytime even with CPU read. So it's typically a hadoop-aws issue.
21/07/22 07:46:53 INFO S3AInputStream: Got exception while trying to read from stream XXXXX trying to recover: java.io.IOException: Hacked ---
21/07/22 07:46:54 ERROR Executor: Exception in task 0.0 in stage 0.0 (TID 0)
org.apache.spark.SparkException: Exception thrown in awaitResult:
	at org.apache.spark.util.ThreadUtils$.awaitResult(ThreadUtils.scala:301)
	at org.apache.spark.util.ThreadUtils$.parmap(ThreadUtils.scala:375)
	at org.apache.spark.sql.execution.datasources.parquet.ParquetFileFormat$.readParquetFootersInParallel(ParquetFileFormat.scala:450)
	at org.apache.spark.sql.execution.datasources.parquet.ParquetFileFormat$.$anonfun$mergeSchemasInParallel$1(ParquetFileFormat.scala:496)
	at org.apache.spark.sql.execution.datasources.parquet.ParquetFileFormat$.$anonfun$mergeSchemasInParallel$1$adapted(ParquetFileFormat.scala:490)
	at org.apache.spark.sql.execution.datasources.SchemaMergeUtils$.$anonfun$mergeSchemasInParallel$2(SchemaMergeUtils.scala:75)
	at org.apache.spark.rdd.RDD.$anonfun$mapPartitions$2(RDD.scala:863)
	at org.apache.spark.rdd.RDD.$anonfun$mapPartitions$2$adapted(RDD.scala:863)
	at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52)
	at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:373)
	at org.apache.spark.rdd.RDD.iterator(RDD.scala:337)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)
	at org.apache.spark.scheduler.Task.run(Task.scala:131)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:497)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1439)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:500)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Could not read footer for file: FileStatus{path=XXXXX; isDirectory=false; length=1403; replication=0; blocksize=0; modification_time=0; access_time=0; owner=; group=; permission=rw-rw-rw-; isSymlink=false; hasAcl=false; isEncrypted=false; isErasureCoded=false}
	at org.apache.spark.sql.execution.datasources.parquet.ParquetFileFormat$.$anonfun$readParquetFootersInParallel$1(ParquetFileFormat.scala:463)
	at org.apache.spark.util.ThreadUtils$.$anonfun$parmap$2(ThreadUtils.scala:372)
	at scala.concurrent.Future$.$anonfun$apply$1(Future.scala:659)
	at scala.util.Success.$anonfun$map$1(Try.scala:255)
	at scala.util.Success.map(Try.scala:213)
	at scala.concurrent.Future.$anonfun$map$1(Future.scala:292)
	at scala.concurrent.impl.Promise.liftedTree1$1(Promise.scala:33)
	at scala.concurrent.impl.Promise.$anonfun$transform$1(Promise.scala:33)
	at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64)
	at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1402)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)
Caused by: java.lang.NullPointerException
	at org.apache.hadoop.fs.s3a.S3AInputStream.lambda$read$3(S3AInputStream.java:453)
	at org.apache.hadoop.fs.s3a.Invoker.once(Invoker.java:109)
	at org.apache.hadoop.fs.s3a.Invoker.lambda$retry$3(Invoker.java:265)
	at org.apache.hadoop.fs.s3a.Invoker.retryUntranslated(Invoker.java:322)
	at org.apache.hadoop.fs.s3a.Invoker.retry(Invoker.java:261)
	at org.apache.hadoop.fs.s3a.Invoker.retry(Invoker.java:236)
	at org.apache.hadoop.fs.s3a.S3AInputStream.read(S3AInputStream.java:449)
	at java.io.DataInputStream.readFully(DataInputStream.java:195)
	at org.apache.parquet.hadoop.util.H1SeekableInputStream.readFully(H1SeekableInputStream.java:51)
	at org.apache.parquet.hadoop.ParquetFileReader.readFooter(ParquetFileReader.java:522)
	at org.apache.parquet.hadoop.ParquetFileReader.readFooter(ParquetFileReader.java:505)
	at org.apache.parquet.hadoop.ParquetFileReader.readFooter(ParquetFileReader.java:499)
	at org.apache.parquet.hadoop.ParquetFileReader.readFooter(ParquetFileReader.java:476)
	at org.apache.spark.sql.execution.datasources.parquet.ParquetFileFormat$.$anonfun$readParquetFootersInParallel$1(ParquetFileFormat.scala:457)
	... 13 more

create a hadoop jira https://issues.apache.org/jira/browse/HADOOP-17812 and a PR https://github.com/apache/hadoop/pull/3222

close this issue, since the PR has been merged in to Hadoop trunk.


Preparing for next developer iteration, 3.1.1.

Description
Preparing for next developer iteration, 3.1.1.
Waiting on https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v3
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@Jakob3xD I tried releasing 3.1.0 following standard instructions, but it's not appearing in https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v3.
I read https://go.dev/doc/modules/publishing and tried running GOPROXY=proxy.golang.org go list -m<EMAIL_ADDRESS>but that fails with not found: ... invalid version: go.mod has post-v3 module path "github.com/opensearch-project/opensearch-go/v3" at revision v3.1.0.
What am I doing wrong?


Tag not firing - Error on writing to data layer.

Hello,
I followed the steps provided here in the documentation : https://avoy.me/blog/hubspot-cmp
When doing a preview of my website, I see that the tag fails to trigger.
When looking into the errors, here is the error message:
Tag Hubspot CMP failed write_data_layer permission check. Prohibited write to data layer variable: ads_data_redaction.
Below the screenshots:

Hey @emilefyon thanks for reaching out!
I've actually made a fix for this, but having a hard time updating the live template. In the meantime, you can download the template.tpl file from the main branch and import it manually in the tag manager.
Let me know if that helps!

@emilefyon Update: the new version is also now available in the gallery. Update it in your tag manager and it should fix this issue!

Hey @emilefyon did you get a chance to try the updated version yet?


[core] Defer Error construction

Packages impacted by this PR
@azure/core-rest-pipeline
@azure/core-http
Issues associated with this PR
Partner report of memory leak in test bench.
Describe the problem that is addressed by this PR
Eager error construction on module load can cause trouble when the Error constructor is hooked/cached by development tooling. This PR changes the pattern of caching the Error object to a more typical new-on-throw pattern. This should also improve the stack trace to be more accurate on the thrown Error.

API change check
API changes are not detected in this pull request.

Since this change, I'm getting the following error in a Deno envrionemnt:
Error: proxyPolicy is not supported in browser environment
    at https://esm.sh/v132/@azure/core-rest-pipeline@1.12.0/deno/core-rest-pipeline.mjs:2:11023

Is there a way to flag it off?

@adamcohenhillel could you file a new issue for this error? It would be strange that moving the construction of the Error to when the class executes it changes behavior, but I can imagine our isNode() check misbehaving.

Done https://github.com/Azure/azure-sdk-for-js/issues/27077


Prefer literals over list and dict constructors

This is just some search and replace to improve readability:

d = dict() --> d = {}
l = list() --> l = []

Some nice benefit of this is that literals in Python are quite a bit faster (though only 60 ns - 75 ns):
In [1]: %timeit d = dict()
101 ns ± 0.0829 ns per loop (mean ± std. dev. of 7 runs, 10000000 loops each)

In [2]: %timeit dl = {}
34.1 ns ± 0.378 ns per loop (mean ± std. dev. of 7 runs, 10000000 loops each)

In [3]: %timeit l = list()
101 ns ± 0.541 ns per loop (mean ± std. dev. of 7 runs, 10000000 loops each)

In [4]: %timeit l = []
25.4 ns ± 0.346 ns per loop (mean ± std. dev. of 7 runs, 10000000 loops each)

@lgeiger I think you don't need to request the entire team to review your PR next time, just let one of our people watching the PR queue assign you an appropriate reviewer :-)
That said, thanks for the change!

I think you don't need to request the entire team to review your PR next time, just let one of our people watching the PR queue assign you an appropriate reviewer :-)

Yes, I'm sorry for the noise. It wasn't me, it was the bot 🤖
I don't have access to request reviews from the tensorflow team.

Rebased!


[feature request] DNS Fallback (DNS transport over TCP)

request: DNS Transport over TCP rfc5966
reference: DNS Fallback article by eycorsican

DNS Fallback
Next, let’s talk about a technology called DNS fallback (this name may not be right). When the proxy server does not support UDP, a simple global TCP/UDP traffic proxy will have a problem, because UDP is needed to resolve DNS.  , The server cannot handle DNS if it does not support UDP, so it cannot handle all domain name requests. DNS fallback is a technology that can force applications to send DNS requests as TCP traffic.

requirement: remote dns for udp-unsupported server https://github.com/2dust/v2rayNG/issues/709
one implementation: https://github.com/eycorsican/go-tun2socks/tree/master/proxy/dnsfallback
this is also an dns alternative to fakedns #377

vmess websocket + CDN（cloudflare）udp被阻止。
我尝试开/关多路复用器和其他电击服务器没有任何变化。
没有CDN, 黄色的udp标志出现
netch ntt.log
Other address is
Binding test: Fail
Local address:
Mapped address:
Nat mapping behavior: Unknown
Nat filtering behavior: Unknown
result: Unknown

vmess websocket + CDN（cloudflare）udp被阻止。
我尝试开/关多路复用器和其他电击服务器没有任何变化。
没有CDN, 黄色的udp标志出现
netch ntt.log
Other address is
Binding test: Fail
Local address:
Mapped address:
Nat mapping behavior: Unknown
Nat filtering behavior: Unknown
result: Unknown


Bug: Focus Reset creates a blank space on the next set of previews when using a lock group.

Video
https://github.com/user-attachments/assets/4f803be6-2c3a-4f5c-83f3-c1b122e18cb4
Expected behaviour
Focused Preview is locked and the next set of previews are the same amount as defined by the config.

This happens because SeedQueueWallScreen#blockedMainPositions is cleared when focus reset is pressed, but the locked preview is only moved to the locked group at the start of the next frame in updatePreparingPreviews.


Fix copy/paste error where "import logging" wasn't brought over

This is causing an error in _ipmtool() if status != 0.

This is a bug pep8 test should spot. Thanks BMI team for spotting it.
+1

+1, merging.


include Bonsai index annotations in generated asset configs

Have bonsai include a set of annotations in the generated asset configs that users can use to identify where they got a particular asset config.
We should probably have a discussion concerning the naming convention of the annotations.
But here are my strawman annotations to include:

sensio.io.bonsai.url -> string
sensio.io.bonsai.tier -> string
sensio.io.bonsai.version -> string
sensio.io.bonsai.tags   -> this a comma delimited string or perhaps a JSON encoded array of strings

Ex output with new annotations:
---
type: Asset
api_version: core/v2
metadata:
  name: sensu-plugins-cpu-checks
  namespace: default
  labels: {}
  annotations:
    sensio.io.bonsai.url: "https://bonsai.sensu.io/assets/jspaleta/sensu-plugins-cpu-checks"
    sensio.io.bonsai.tier: "Community"
    sensio.io.bonsai.version: "4.0.0-pre"
    sensio.io.bonsai.tags: "experimental, ruby-runtime"

spec:
  url: https://github.com/jspaleta/sensu-plugins-cpu-checks/releases/download/4.0.0-pre/sensu-plugins-cpu-checks_4.0.0-pre_alpine_linux_amd64.tar.gz
  sha512: 92a57b54b297b5a90011c3472a48c5b4357dbfa123ad391386e6aafe29e6212b6db5da7e4a80514e938361f3030df1ef5022fb99f64e5cc46ed6d8bdc1c7927c
  filters:
  - entity.system.os == 'linux'
  - entity.system.arch == 'amd64'
  - entity.system.platform == 'alpine'

Also i would LOVE to be able to provide an annotation that suggested necessary dependency assets
  annotations:
    sensio.io.bonsai.url: "https://bonsai.sensu.io/assets/jspaleta/sensu-plugins-cpu-checks"
    sensio.io.bonsai.tier: "Community"
    sensio.io.bonsai.version: "4.0.0-pre"
    sensio.io.bonsai.suggested_runtime_asset: "https://bonsai.sensu.io/assets/sensu/sensu-ruby-runtime"
    sensio.io.bonsai.suggested_runtime_asset_version: "0.0.5"
    sensio.io.bonsai.tags: "experimental, ruby-runtime"

Now in this example i'm treating runtime as a very special case and one that exists right now to make the ruby plugins work as assets.   I explicitly state is a suggestion as a breadcrumb for users.
The more general case is that assets can depend on an array of other assets, which is a bit harder.. we'd have to encode that list as a json string packed into a single annotation. That get's complicated and messy.

I've added what I've called common annotations that can be generated from the data.  If you add any key value pair to the  bonsai.yml annotations key, it will be incorporated into the annotations generated on download.

Just pulled the asset config from:
https://bonsai-asset-index-staging.herokuapp.com/assets/sensu-plugins/sensu-plugins-cpu-checks
A few problems in the metadata section

the sensu.io.bonsai.tags   must be a string or null or it won't parse correctly into sensuctl

the sensu.io.bonsai.tags: []

should read as
the sensu.io.bonsai.tags: null

when there are no tags.

labels/annotations should read as null if no labels/annotions are defined

labels: []

should read as
labels: null

version is not valid

namespace should always be default, the sensu concept of namespace isn't the same as the github user namespace.

Problems with the spec section

asset_url  key should not exist, value there should be reported in the url key

last_modified should be an annotation perhaps sensu.io.bonsai.last_modified

Here's a version of the config with corrections.  Original lines are prefixed with ##
---
type: Asset
api_version: core/v2
metadata:
  name: sensu-plugins-cpu-checks
  ##namespace: sensu-plugins
  namespace: default
  ##labels: []
  labels: null
  ##version: 4.0.0
  annotations:
    sensio.io.bonsai.url: https://s3.us-west-2.amazonaws.com/staging.assets.bonsai.sensu.io/68546e739d96fd695655b77b35b5aabfbabeb056/sensu-plugins-cpu-checks_4.0.0_alpine_linux_amd64.tar.gz
    sensio.io.bonsai.tier: Community
    sensio.io.bonsai.version: 4.0.0
    ##sensio.io.bonsai.tags: []
    sensio.io.bonsai.tags: null

spec:
  url: https://github.com/sensu-plugins/sensu-plugins-cpu-checks/releases/download/4.0.0/sensu-plugins-cpu-checks_4.0.0_alpine_linux_amd64.tar.gz
  sha512: b2da25ecd7642e6de41fde37d674fe19dcb6ee3d680e145e32289f7cfc352e6b5f9413ee9b701d61faeaa47b399aa30b25885dbc1ca432c4061c8823774c28f3
  ##asset_url: https://s3.us-west-2.amazonaws.com/staging.assets.bonsai.sensu.io/68546e739d96fd695655b77b35b5aabfbabeb056/sensu-plugins-cpu-checks_4.0.0_alpine_linux_amd64.tar.gz
  ##last_modified: '2019-05-14T17:11:12.000Z'
  filters:
  - entity.system.os == 'linux'
  - entity.system.arch == 'amd64'
  - entity.system.platform == 'alpine'

url should point to base url of asset on bonsai


Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.0:compile (default-compile) on project dubbo-admin-server: Compilation failure

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the REAMDE of this repository and believe that this is not a duplicate.

Environment

Dubbo Admin version: centos
Registry center detail (type and version): zookeeper
Operating System version:  7.5
Java version: java-1.8.0-openjdk-<IP_ADDRESS>5.b01-0.el7_9

Steps to reproduce this issue

mvn clean package

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps？
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for dubbo-admin 0.3.0-SNAPSHOT:
[INFO]
[INFO] dubbo-admin ........................................ SUCCESS [ 52.594 s]
[INFO] dubbo-admin-ui ..................................... SUCCESS [ 42.424 s]
[INFO] dubbo-admin-server ................................. FAILURE [ 28.249 s]
[INFO] dubbo-admin-distribution ........................... SKIPPED
[INFO] dubbo-admin-test ................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:06 min
[INFO] Finished at: 2021-04-16T17:21:36+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.0:compile (default-compile) on project dubbo-admin-server: Compilation failure
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :dubbo-admin-server

mvn -v
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-25T02:41:47+08:00)
Maven home: /var/tmp/apache-maven-3.6.0
Java version: 1.8.0_275, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>5.b01-0.el7_9.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1127.19.1.el7.x86_64", arch: "amd64", family: "unix"


feat(EG K8S Provider): Improve EG Gateway xDS & startup reliability

What type of PR is this?
feat(EG K8S Provider): Improve EG Gateway xDS & startup reliability
What this PR does / why we need it:
This pull request guarantees that new editions of EGs won't initiate unless they've successfully completed at least one reconciliation loop and that the xDS server has commenced and is ready to serve envoys.
Which issue(s) this PR fixes:
This enhancement facilitates the safer upgrades of EG gateways and features improved xDS consistency on startup.
High Level Changes
A custom health check is implemented to ensure that EG controller is deemed ready only once the xDS snapshot is persisted, or after at least one reconciliation is completed for empty or new clusters.
A custom watcher is added to initiate an initial dummy reconciliation, this ensures empty or news deployments can start (as a successful reconcile is a trigger for startup)
https://github.com/envoyproxy/gateway/issues/2810
! Draft !

/retest

@alexwo is this necessary ?
based on https://github.com/envoyproxy/gateway/blob/main/internal/xds/cache/snapshotcache.go I believe we only push a snapshot if the IR exists

@alexwo is this necessary ? based on https://github.com/envoyproxy/gateway/blob/main/internal/xds/cache/snapshotcache.go I believe we only push a snapshot if the IR exists, so if a IR hasn't been translated yet, it shouldnt result in a xds response (this needs to be cross checked)

Sure, If there are no items requiring translation, we don't anticipate an XDS response. Our focus is solely on verifying that the XDS server has successfully initiated and that a reconciliation loop, albeit inactive, has been executed. (empty / new cluster)
If there are any IRs translated due to a reconciliation loop containing items needing processing, we verify that a snapshot has indeed been persisted before deeming the instance ready.
There are essentially two conditions that indicate the instance's health. (cluster with resources for xDS)

@alexwo You closed this PR in favor of @arkodg 's suggestion (https://github.com/envoyproxy/gateway/issues/2810#issuecomment-1981979019) to use longer initialDelaySeconds ?


When will Dav4 and Dasv4-series be added

Hi,
The Dav4 and Dasv4-series have recently been released (https://docs.microsoft.com/en-us/azure/virtual-machines/dav4-dasv4-series). When will they be added to the benchmark?
Regards,
Aede

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

ID: c005a93a-6fce-d270-9bb5-8e7213156b70
Version Independent ID: 844d62d4-a06b-1578-488f-f6441242a07d
Content: Compute benchmark scores for Azure Linux VMs - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/compute-benchmark-scores.md
Service: virtual-machines-linux
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

We are currently cleaning up old issues and closing out items that are greater than 90 days old. If an issue is still present, please open a new feedback item on the document so we can prioritize correctly.
#please-close


[REQUEST] DB SAVE OPTIONS

**.DB corrupts with a high frequency.
Or when it's full it takes too long to open.
It would have as an option to save the combos in .txt instead of .DB
Or save with the names of the configs.**

Duplicate

https://github.com/openbullet/openbullet/issues/629


Track only Create (Not Updates or Deletes)

Dear All.
Is it possible to track only the "Create" on a Model but not the Updates and Deletes? We are only interested in knowing who created the model instance for certain models.
Regards,
Anurag

Hello @gudddu. This isn't exactly a feature... But it looks like setting skip_history_when_saving = True on your model as a class attribute might do the trick.

Thanks Micah, It worked like a charm.
Regards,
Anurag
On Wed, Aug 10, 2016 at 5:56 AM, Micah Denbraver<EMAIL_ADDRESS>wrote:

Hello @gudddu https://github.com/gudddu. This isn't exactly a
feature... But it looks like setting skip_history_when_saving = True on
your model as a class attribute might do the trick.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/treyhunner/django-simple-history/issues/235#issuecomment-238732913,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPpLfzCFpQPK6FBOr4XfjO06yzAFFP8ks5qeRq7gaJpZM4JgaIY
.

Glad to hear!


Date not showing in chat

Rocket chat android mobile app message date not showing. please fix the build.

Hi @Anish-addweb , where the data isn't shown?

@filipedelimabrito issue fixed in new 2.5.0 release.


The root_dir macro matches /root123abc

The root_dir macro is currently defined as:
- macro: root_dir
  condition: ((fd.directory=/ or fd.name startswith /root) and fd.name contains "/")

Unfortunately, this matches on any fd.name beginning with the word "root", even if that's not a sensitive location. This is triggering a number of alerts for containers that place files in locations like /rootDir and similar, causing them to be misclassified as sensitive.

To reproduce, create a container with a directory named /rootDir or /root123abc and modify a file within one of those locations. Falco will report "File below / or /root opened for writing".

Only files immediately under / and /root should match this macro.

Falco version: 0.21.0
System info:
{
"machine": "x86_64",
"nodename": "[redacted]",
"release": "4.15.0-1065-aws",
"sysname": "Linux",
"version": "#69-Ubuntu SMP Thu Mar 26 02:17:29 UTC 2020"
}
Cloud provider or hardware configuration: AWS
OS:

NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Kernel: 4.15.0-1065-aws
Installation method: DEB

I've made a PR to fix this issue :point_right: #1279
/assign
/milestone 0.24.0


GEODE-10400: Fix metadata completion detection

Whenever execution server functions with isHA=false, hasResult=true
and optimizeForWrite=true, if the metadata is incomplete a request of
type EXECUTE_REGION_FUNCTION_SINGLE_HOP is sent with an invalid
bucket set partition. This causes an
InternalFunctionInvocationTargetException exception
In order to solve this issue, now, whenever calling
groupByServerToBuckets, if there isn't a valid location for one of
the buckets, it returns nullptr, triggering the fallback mechanism
which would be sending EXECUTE_REGION_FUNCTION to one of the nodes
instead.

I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state.


GITF/GIB compression (similar question with #issue 558)

Recently，I am trying to do some work based on Filament ,and I also noticed the Draco.
Dose Filament has some tools to support the gITF or glb compression ?or Filament has already  realized this funcion just I didn't found it.
I noticed you have mentioned  may  add this Draco compression in issue 558.
Thanks for your great work

Yes, our glTF reader library (gltfio) already supports Draco decoding.  We do not provide tools for encoding or writing glTF files.  Feel free to use our "discussions" tab for further questions.


Duplicate Header Clobbering

I have emails with duplicate header names. When I call the "getHeader" method on these names it returns the last entry only. It would be desirable if it would return an array in this case.

Released in 1.0-beta.  If you have a chance to look over it and report any issues that would be great :)


Disable ability to select a date that is in the past

Added js function to only allow the current date and future dates to be selected in the pickupEditCreate folder.  Also updated the html file to use the js function.

Does it make sense to you? It doesn't work, can you guess why?

After the changes you made I was able to compile but the test environment
still won't launch. I was up messing around with it last night so without
being able to test and see the errors it it's hard to guess
On Thu, May 11, 2017 at 12:37 AM Tilmann Becker<EMAIL_ADDRESS>wrote:

Does it make sense to you? It doesn't work, can you guess why?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yunity/foodsaving-frontend/pull/490#issuecomment-300687288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI9y4Ee2FUfxHk9wrMRr7cgNNYX0uxoIks5r4p6NgaJpZM4NWA62
.

Solved via #517


Add support for range indexed data in DataSet.write_mtz() and DataSet.to_gemmi()

PR fixes #255.
Currently, DataSet objects with a pd.RangeIndex() (for example, due to a call to DataSet.reset_index()) end up causing trouble due to an extra call to reset_index() within rs.io.mtz.to_gemmi(). To resolve this issue, this PR uses the range_indexed decorator to ensure that the relevant functions can assume the calling DataSet object is always range indexed. This simplifies the control flow for these functions.
As part of this PR, I also modified range_indexed to handle use cases where the decorated function returns None or non-DataSet types.

Yep -- that might be a worthwhile enhancement if we ever want to look into performance-related improvements.
I'll merge this in


Adding support for https healthcheck

addresses issue #772
I haven't had a chance to test it in a running environment

@drexin Any other concerns with this? I think it might need the HTTPS specification added to the blob at https://github.com/CashStar/marathon/blob/https_health_check/src/main/java/mesosphere/marathon/Protos.java#L12689 but I'm unsure of the format

Closing this pull request to rebase against the master branch


#2548 allow to invalidate evaluation results from bridge

The evaluation tile now allows to invalidate evaluation results from the bridge by clicking on the "Ignore for comparison"-Button.

It will ask the user for confirmation and allow to provide a reason as well.

Codecov Report

Merging #2604 into master will increase coverage by 3.02%.
The diff coverage is 5.71%.

@@            Coverage Diff             @@
##           master    #2604      +/-   ##
==========================================
+ Coverage   33.40%   36.43%   +3.02%
==========================================
  Files         161      166       +5
  Lines        9040    10611    +1571
  Branches      185      188       +3
==========================================
+ Hits         3020     3866     +846
- Misses       5520     6142     +622
- Partials      500      603     +103

Flag
Coverage Δ

moduleA
23.29% <5.71%> (-0.21%)
:arrow_down:

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

Impacted Files
Coverage Δ

bridge/client/app/_models/event-labels.ts
100.00% <ø> (ø)

bridge/client/app/_services/api.service.ts
14.58% <0.00%> (-0.64%)
:arrow_down:

bridge/client/app/_services/data.service.ts
1.11% <0.00%> (-0.02%)
:arrow_down:

bridge/client/app/app.module.ts
100.00% <ø> (ø)

...uation-details/ktb-evaluation-details.component.ts
11.64% <3.57%> (-0.48%)
:arrow_down:

bridge/client/app/_models/event-types.ts
100.00% <100.00%> (ø)

cli/cmd/delete_service.go
13.88% <0.00%> (-2.12%)
:arrow_down:

cli/cmd/install.go
13.36% <0.00%> (-1.51%)
:arrow_down:

helm-service/pkg/helm/generated_chart_handler.go
0.00% <0.00%> (ø)

.../pkg/configurationchanger/configuration_changer.go
0.00% <0.00%> (ø)

... and 21 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70119cf...81ad43e. Read the comment docs.


Error out or throw warning if invalid console is set

If possible, we should error out if someone tries to set a rancher console that doesn't exist.
$ sudo ros config set rancher.console test1
# ERROR NEEDED
$ sudo ros console switch test2
# ERROR NEEDED

This is weird that after I incorrectly set the console using sudo ros config set, it shows me the invalid console in my cloud-config.
$ sudo ros config export
rancher:
  console: test1

When I go to reboot the host, I end up back in the default console.

https://github.com/rancher/os/pull/1074

Verified with v0.8.0-rc4
$ sudo ros console switch test2
> FATA[0000] test2 is not a valid console


option to remove upload

right now it is not possible to remove an upload.
imagine you notice that it is blurry and not readable in the black out phase, so you upload a new version of that page. there is no option to delete the blurry one.
when you go back, it looks like you lost every upload, but later every upload is there. maybe show in every step your uploads...

we look into this


Recommended way to get account_id throughout project?

Hey all, thanks for building this library! I'm currently doing something like this:

User signs up with some provider (Google for example)
We create a team account for that user using the RPC 'create_account' since personal accounts are disabled
Access the account_id throughout other components that need it?

I'm stuck on step 3 right now. I'm currently debating on creating a bespoke provider to pass this account_id where needed to other client components in my application, but wasn't sure if there was a better way to do this. I'm essentially creating an app that has projects (folders) and documents that are owned by each project. Each project should be owned by only one account and each user should only be able to belong to one team account. Would appreciate any guidance on how to move forward!

I think the simplest solution is either

a public.profiles table and use a team_id column to reference the basejump.accounts(id) or
save the account_id into auth.users raw_user_metadata column

I choose something similar to the first option. Since I use personal accounts also, I set it up like auth.users, public.profiles, and basejump.accounts share the same ID, so it makes it easy to cross-reference. Plus I also utilize a slugified, unique username for routing.
I had to overwrite the basejump.run_new_user_setup() function tho. Here's the code. You may be able to get along by changing personal_account to false and use something else for slug & name instead of username.
create or replace function basejump.run_new_user_setup()
    returns trigger
    language plpgsql
    security definer
    set search_path = public
as
$$
declare
    first_account_id    uuid;
begin
    -- create the new users's personal account
    insert into basejump.accounts (name, primary_owner_user_id, personal_account, id, slug, created_by, updated_by)
    values (NEW.raw_user_meta_data->>'username', NEW.id, true, NEW.id, NEW.raw_user_meta_data->>'username', NEW.id, NEW.id)
    returning id into first_account_id;

    -- add them to the account_user table so they can act on it
    insert into basejump.account_user (account_id, user_id, account_role)
    values (first_account_id, NEW.id, 'owner');

    -- create a profile for the user
    insert into public.profiles (id, email, username, account_id)
    values (NEW.id, NEW.email, NEW.raw_user_meta_data->>'username', first_account_id);

    return NEW;
end;
$$;

-- trigger the function every time a user is created
create or replace trigger on_auth_user_created
    after insert
    on auth.users
    for each row
execute procedure basejump.run_new_user_setup();


When extension installation fails - show error message

Scenario:

Visual Studio code version was not supported by extension
Installation succeeded, however 'reload' appeared on the extension and reloading did not work.

Solution:
Show an error message like the one below using the existing mechanism:

This is entirely VSCode error reporting, no real way to interact with it.
Closing.


Increase incarnation for pod tasks as well.

Summary:
Follow up to #6677. We did not raise the incarnation for ephemeral pod tasks.
This diff solves it and cleans up the task ids a little bit.

why do we have reservationId on Task.Id at all? Even for ephemeral? I think the only usage is for task labels, we can use idString directly there maybe?

Well, we have the EphemeralOrReservationId type for historical reasons. I did not manage to separate them. Ideally we would introduce a ReservationId type that is completely indepenent of task ids. However, that is not easy.

why is fromReservation special? Why can't we use forInstanceId there? It seems to be doing the same thing...

forReservation returns the id for a reservation not for a resident task. It has nothing to do with ids for launched tasks.

@timcharper, @alenkacz and @meln1k I created a new Reservation.Id type in #6687. I hope that clears up a few things. Please not that #6687 has some outstanding todos. I really would like to merge this pull request before.


[FLINK-33198] support local timezone timestamp logic type in AVRO

What is the purpose of the change
From the latest Avro Spec, local-timestamp-millis and local-timestamp-micros logical types are added. This PR is to support Local timezone logic type in Avro related classes.
Brief change log

Add logic to handle TIMESTAMP_WITH_LOCAL_TIME_ZONE in AvroToRowDataConverters
Add logic to handle TIMESTAMP_WITH_LOCAL_TIME_ZONE in RowDataToAvroConverters
Add logic to handle TIMESTAMP_WITH_LOCAL_TIME_ZONE in legacy AvroRow Ser and Des Schema
Add new fields for test cases

Verifying this change
Extended existing test cases for Avro
Does this pull request potentially affect one of the following parts:

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

Documentation

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

@flinkbot run azure

@flinkbot  run azure

@flinkbot run azure

Thank you @HuangZhenQiu a lot for contributing this.
After reading the Avro spec, I think we have wrongly mapped the Avro timestamp.
Avro spec says:

Timestamp (millisecond precision)
The timestamp-millis logical type represents an instant on the global timeline, independent of a particular time zone or calendar, with a precision of one millisecond. Please note that time zone information gets lost in this process. Upon reading a value back, we can only reconstruct the instant, but not the original representation. In practice, such timestamps are typically displayed to users in their local time zones, therefore they may be displayed differently depending on the execution environment.
A timestamp-millis logical type annotates an Avro long, where the long stores the number of milliseconds from the unix epoch, 1 January 1970 00:00:00.000 UTC.

Consistent timestamp types in Hadoop SQL engines also pointed out:

Timestamps in Avro, Parquet and RCFiles with a binary SerDe have Instant semantics

So Avro Timestamp is a Java Instant semantic that should map to Flink TIMESTAMP_LTZ, but currently, it maps to TIMESTAMP_NTZ.
On the contrary,

Local timestamp (millisecond precision)
The local-timestamp-millis logical type represents a timestamp in a local timezone, regardless of what specific time zone is considered local, with a precision of one millisecond.
A local-timestamp-millis logical type annotates an Avro long, where the long stores the number of milliseconds, from 1 January 1970 00:00:00.000.

Avro LocalTimestamp is a Java LocalDateTime semantic that should map to Flink TIMESTAMP_NTZ.
If we agree with this behavior, we may need to open a discussion in the dev ML about how to correct the behavior in a backward-compatible or incompatible way.

@wuchong Thanks for the feedback according to the hadoop alignment doc. Beside this, I also feel unclear on how to converting timestamp data to TimestampData which is the RowData internal representation. A Flink user can define a dynamic table with Avro format on a timestamp field with a target timestamp with time zone, but we we can't convert the Avro long typed data to the target timestamp with time zone as the target Flink type is missing in Converters. I would like to open a discussion in dev ML after our offline sync.

@flinkbot run azure

@flinkbot run azure

Hi @PatrickRen @leonardBang , do you have time to help review this PR?

Hi, @HuangZhenQiu Would you like to rebase the PR to the latest master branch ?

@flinkbot run azure

@leonardBang
Thanks for providing valuable comments. I have refactor the code to resolve your comments. Another following PR will be created to change precision. Thanks!

@flinkbot run azure

@leonardBang
Thanks for the comprehensive review. It not help me dig out the bug, and also make the feature easy to use by adding more context in variable name, flag description and comments.

@leonardBang Rebased master. Let's see the CI result.

@flinkbot run azure

Hit a code style issue which is fixed in the latest master. Rebase master again.

@flinkbot run azure


Turn on source mode by default

Is there a way to turn on source mode by default?

why would you need it in WYSIWYG?