text:
TFLite conversion works in TF 2.8 / fails in 2.7.1, both produce large file sizes and incorrect input size of 1x1x1x3

1. System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
TensorFlow installation (pip package or built from source): pip install
TensorFlow library (version, if pip package or github SHA, if built from source): test 2.7.1 and 2.8

2. Code
Provide code to help us reproduce your issues using one of the following options:
TensorFlow 2.8
https://colab.research.google.com/drive/1uYZOrPJWbSGfhf-DYEgMtCVmy5xLBE5G?usp=sharing
TensorFlow 2.7.1
https://colab.research.google.com/drive/15kzXMSF2olfzNskYN99WKq7DarUy-3tj?usp=sharing
3. Failure after conversion
Used ssd_resnet101_v1_fpn_640x640_coco17_tpu-8 from model zoo to train a custom model since SSD models are supported in TF lite conversion. Exported the model using 'exporter_main_v2.py' from model zoo repo and the saved model was 16 Mb.
All TFLite models incorrectly have an input size of 1x1x1x3
TF 2.8 converts all 3 different quantizations tested (see relevant colab)
TF Lite Dynamic Range file size is 73.5 Mb
TF Lite Int with float fallback file size is 267.7 Mb
TF lite Full integer quantization file size is 271.2 Mb
TF 2.7.1 integer quantization fails with
Failed to quantize: :0: error: loc("Postprocessor/Slice;Postprocessor/Slice"): 'tfl.slice' op quantization parameters violate the same scale constraint: !quant.uniform<i8:f32, 2.5953195290639997E-4:-128> vs. !quant.uniform<i8:f32, 0.0011857558274641633:-128>
5. (optional) Any other info / logs
For the large file size generation I have also commented over at #54405 as well but I created new issue for the incorrect input size and failure of conversion for 2.7.1
I also tried using the 'export_tflite_graph_tf2.py' (not sure if that is what I should be using) to export my saved model which seems to correctly generate the input signature of 1,640,640,3 though I am not sure about the generated tflite yet but the converted tflite files are still 70 Mb.

@sachinprasadhs I was able to reproduce the issue on colab using TF v2.7.1 and 2.8.0 .Please find the attached gists.Thanks!

I also have a colab that allows one to easily test the conversion of the models available in the model zoo
https://colab.research.google.com/drive/1nHWL9MaZ-em6gfKC8fBP4RnS9nQq4ZyP#scrollTo=aLZGB8dsH1iD
It allows you to quickly change the model name in the forms of tar.gz that are over at the model zoo along with the image input size and test that output of the conversion. Similar issue with the large file size can be seen there as well.
The 'export_tflite_graph_tf2.py' is used to export the graph as that seems to be the correct way to do it which also fixed the input signature as already mentioned.

@cstamatopoulos I used the colab in your latest comment.

I don't see the shape issue, can you explain how i can find it ?

For the large files, i think you are missing few things:

a) saved_model.pb stores the actual graph, but it doesn't store the variables or assets. Variables are stored in variables directory in the checkpoint format.
TFLite have everything in the .tflite file, which means the variables values (either frozen or initialized as variables) are present inside the TFLite file.
b) TFLite converter optimizes the graph for inference latency, this means that in many cases if an op value can be inferred during conversion we will do this and fold the results as constant tensors in the graph to be used by dependent layers. This means that the amount of data in the file can be bigger than TF equivalent.
Let me know if you have any questions.
Thanks

@karimnosseir The latest colab uses a different command to export the saved model.
Namely "export_tflite_graph_tf2.py" vs "exporter_main_v2.py" from the model zoo.
Documentation is a bit unclear as the documentation for tf lite says that all that is needed a saved model and there are various posts about setting the fixed size and re-saving the model as I show below which does not work.
"export_tflite_graph_tf2.py" seems to do the trick
If you notice in the first 2 colabs you will see that
'shape': array([1, 1, 1, 3]
even though I am saving the model as advised with an input size
model = tf.saved_model.load(tfmodel_path)         model.signatures[tf.saved_model.DEFAULT_SERVING_SIGNATURE_DEF_KEY].inputs[0].set_shape([1, 640, 640, 3])         tf.saved_model.save(model, "saved_model_updated", signatures=model.signatures[tf.saved_model.DEFAULT_SERVING_SIGNATURE_DEF_KEY])
I can provide the same input data to tf lite model maker and I get a model for efficientdet_lite3 that is around 12Mb.
Maybe that is not fair comparison as as you say the size of the model variables is what matters.
I was initially using TF 2.7.1 that was generating files that were 270 Mb.
Then I tested 2.8 and it was 70 Mb so it made me skeptical.

I see them now, thanks.
So this is working as expected. Let me explain the output to you
{'name': 'serving_default_input_tensor:0', 'index': 0, 'shape': array([1, 1, 1, 3], dtype=int32), 'shape_signature': array([ 1, -1, -1,  3], dtype=int32)

There are 2 parts that have shape, shape and shape_signature

shape: Is the default shape of the tensor, IOW if you just decided to load the model and run this is the shape of the tensor.
So what is shape_signature then
shape_signature: Is similar to shape but instead might have some dimensions labeled with -1, these dimensions are the dimensions that are dynamic and can be resized.

That means that the model you are converting has shape [1, None, None, 3] and TFLite honor this and you can resize the 'None' dimensions at runtime.
Hope it is more clear now.
Thanks

Hi, Could you please refer the above comment which should clarify your confusion.
In addition to that could you please refer the document here https://www.tensorflow.org/lite/guide/signatures which explains the Signatures in Tensorflow Lite for Inputs, Outputs and Signature Key.

authors: cstamatopoulos karimnosseir sachinprasadhs sushreebarsa


text:
TFlite conversion Doesn't support dense layers with inputs of rank greater than 2

1. System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): windows 10 64 bit
TensorFlow installation (pip package or built from source): Python 3.8.2, pip: 22.1, pip package
TensorFlow library (version, if pip package or github SHA, if built from source): TF version:'2.9.0'

2. Code
Provide code to help us reproduce your issues using one of the following options:
import tensorflow as tf
import numpy as np
import pathlib

def tflite_convert(model,data):
    def representative_data_gen():
            for input_value in data:
                input_value = input_value[np.newaxis, ...]
                yield [input_value] # shape should be (1, <data point size))
    converter = tf.lite.TFLiteConverter.from_keras_model(model)
    converter.optimizations = [tf.lite.Optimize.DEFAULT]
    converter.representative_dataset = representative_data_gen
    # Ensure that if any ops can't be quantized, the converter throws an error
    converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS_INT8]

    converter.inference_input_type = tf.int8
    converter.inference_output_type = tf.int8

    tflite_model = converter.convert()
    tflite_models_dir = pathlib.Path("./output/tflite_models/")
    tflite_models_dir.mkdir(exist_ok=True, parents=True)
    tflite_model_file = tflite_models_dir/"model_{0}.tflite".format(model.name)
    tflite_model_file.write_bytes(tflite_model)

def tflite_explore(path):
    tflite_interpreter = tf.lite.Interpreter(model_path=path)
    tflite_interpreter.allocate_tensors()

    '''
    Check input/output details
    '''
    input_details = tflite_interpreter.get_input_details()
    output_details = tflite_interpreter.get_output_details()

    print("== Input details ==")
    print("name:", input_details[0]['name'])
    print("shape:", input_details[0]['shape'])
    print("type:", input_details[0]['dtype'])
    print("\n== Output details ==")
    print("name:", output_details[0]['name'])
    print("shape:", output_details[0]['shape'])
    print("type:", output_details[0]['dtype'])

def make_dense_model():
    input_layer = tf.keras.Input(shape=(1,5,12))
    dense_layer=tf.keras.layers.Dense(3)(input_layer)
    model=tf.keras.Model(input_layer,dense_layer)
    return model

def generate_Noise_Data(shape,batch_size):
    if None in shape:
        shape=list(shape)
        shape[0]=batch_size
    noise=np.array(np.random.randint(0,255,shape).astype(np.float32))
    return noise/255

model=make_dense_model()
print(model.summary())
in_value=generate_Noise_Data(model.layers[0].input_shape[0],2)
print(model(in_value))
model.save("./output/dense1layer.h5")
tflite_convert(model,in_value)
tflite_explore("./output/tflite_models/model_{0}.tflite".format(model.name))

3. Failure after conversion
If the conversion is successful, but the generated model is wrong, then state what is wrong:

Model produces wrong results
here i use a keras model that is converted to .tflite file. the keras model's HDF5 save and its tflite converted '.tflite' are visualized in netron. their outputs don't match.
in the keras model: the input is of shape (none,1,5,12) (shape is>2D ).the model has a single dense layer with 3 nodes. its kernal are of shape [12,3]. the model produces an output of shape (none,1,5,3).
in the .tflite converted file the output is of shape [1,1,1,3] (not [1,1,5,3]) and input is of shape [1,1,5,12]

this is the output i have obtained with the above code:

its netrons with .h5 on the left and .tflite on the right

Hi @sachinprasadhs !
Could you look at this issue. Attached gist in 2.8, 2.9 and nightly for reference.

@Saar-Ken-Ji The issue seems to be resolved in TF Nightly 2.12.0-dev20230117. The output shape of TF lite converted model is obtained as [1,1,5,3] . Please find the gist here and let us know if it helps. Thank you.

source: gharchive/issue

authors: Saar-Ken-Ji mohantym pjpratik

repo: tensorflow/tensorflow

license_type: permissive

license_source: github-api


text:
tensorflow static library of windows: missing few files

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with the
documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go
here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script
provided in TensorFlow): Its tensorflow provided code as given in https://www.tensorflow.org/install/lang_c
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue
happens on a mobile device: Laptop
TensorFlow installed from (source or binary): static library from https://www.tensorflow.org/install/lang_c
TensorFlow version (use command below): 2.11
Python version: NA
Bazel version (if compiling from source): NA
GCC/Compiler version (if compiling from source): 12.2
CUDA/cuDNN version:NA
GPU model and memory: NA
Exact command to reproduce: Took static library from tensorflow ebsite from link below : https://www.tensorflow.org/install/lang_c
Have taken windows version of https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-windows-x86_64-2.11.0.zip (CPU version)
unzipped and created hello_tf.c as mentioned in same webpage.
Compiled the hello_tf.c as below :
gcc hello_tf.c -I D:\tensorflow_lib\include -lD:\tensorflow_lib\lib\tensorflow -o hello_tf

Got error as
In file included from hello_tf.c:2:
D:\tensorflow_lib\include/tensorflow/c/c_api.h:23:10: fatal error: tensorflow/c/tf_buffer.h: No such file or directory
23 | #include "tensorflow/c/tf_buffer.h"
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Then took tf_buffer.h from github repo , to see if the error is only dependent on tf_buffer.h, but then got another error :
D:\tensorflow_lib>gcc hello_tf.c -I D:\tensorflow_lib\include -lD:\tensorflow_lib\lib\tensorflow -o hello_tf
In file included from D:\tensorflow_lib\include/tensorflow/c/tf_tstring.h:19,
from D:\tensorflow_lib\include/tensorflow/c/c_api.h:27,
from hello_tf.c:2:
D:\tensorflow_lib\include/tensorflow/core/platform/ctstring.h:19:10: fatal error: tensorflow/tsl/platform/ctstring.h: No such file or directory
19 | #include "tensorflow/tsl/platform/ctstring.h"
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Took static library from tensorflow ebsite from link below : https://www.tensorflow.org/install/lang_c
Have taken windows version of https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-windows-x86_64-2.11.0.zip (CPU version)
unzipped and created hello_tf.c as mentioned in same webpage.
Compiled the hello_tf.c as below :
gcc hello_tf.c -I D:\tensorflow_lib\include -lD:\tensorflow_lib\lib\tensorflow -o hello_tf
Got error as
In file included from hello_tf.c:2:
D:\tensorflow_lib\include/tensorflow/c/c_api.h:23:10: fatal error: tensorflow/c/tf_buffer.h: No such file or directory
23 | #include "tensorflow/c/tf_buffer.h"
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Then took tf_buffer.h from github repo , to see if the error is only dependent on tf_buffer.h, but then got another error :
D:\tensorflow_lib>gcc hello_tf.c -I D:\tensorflow_lib\include -lD:\tensorflow_lib\lib\tensorflow -o hello_tf
In file included from D:\tensorflow_lib\include/tensorflow/c/tf_tstring.h:19,
from D:\tensorflow_lib\include/tensorflow/c/c_api.h:27,
from hello_tf.c:2:
D:\tensorflow_lib\include/tensorflow/core/platform/ctstring.h:19:10: fatal error: tensorflow/tsl/platform/ctstring.h: No such file or directory
19 | #include "tensorflow/tsl/platform/ctstring.h"
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

Hi, @ignvinay
Apologize for the delay and I was able to replicate same issue on Google Colan which uses Ubuntu OS so it's working as expected, here is gist-file so we'll try on Windows 10 and we'll let you know soon and Thank you for noticing this issue. Thank you!

Hi, i got the same issue on Win10 and Visual Studio 2019 and the prebuild Tensorflow lib in Version 2.11 (https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-windows-x86_64-2.11.0.zip).
Also tried older versions of TF like 2.6 and there is the same problem.
There is no tensorflow/c/tf_buffer.h. The file doesnt exist.
I downloaded the linux version and here the tf_buffer.h exists.
Please help :(

Hi Zarzaro and gaikwadrahul,
I could able to get it working. The include folder is missing two folders which are required for building.
These two folders i picked it from linux version of package as include files are more of header files, which would be independent of OS.
Here is comparision: (right side of the figure is my working directory).

JUst incase if you still need whole include folder, i am attaching here for your reference. Please replace this include folder with include folder of tensorflow.
include.zip

Hm okay at least that seems to be a solution. But its not straight forward. Is that a build bug? Are we the first two persons that are using the prebuilt lib from tensorflow for Windows? A prebuilt lib should be straight forward to use in my opinion.
I even tried to build the dll etc from tensorflow since since 3 days without final success. The bazel build of dll, lib and headers is finally completed successfully but i get errors in Visual Studio as well when i try to run a simple hello world project.
It seems Tensorflow is not meant to be used in c++. Very little documentation for this inconvenient build process.

Yeah, it's cool that there's a workaround, but it would be much better if we could find the script that makes these, and fix it.

also missing from the include "patch" is file "tensorflow/tsl/c/tsl_status.h" (there might be others)

authors: MarkDaoust esohns gaikwadrahul8 ignvinay zarzaro


text:
tensorflow/core/common_runtime/gpu/gpu_device.cc:1956] Cannot dlopen some GPU libraries

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
2.12
Custom Code
No
OS Platform and Distribution
Ubuntu 22.04
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
This command:
import tensorflow as tf
print(tf.config.list_physical_devices('GPU'))

returns:
W tensorflow/core/common_runtime/gpu/gpu_device.cc:1956] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
[]

So no GPU is detected. I have NVIDIA drivers installed correctly cuda and cudnn installed correctly as advised on https://www.tensorflow.org/install/pip#linux_setup
There is nothing about setting path, so I have not set path.
Standalone code to reproduce the issue
import tensorflow as tf
print(tf.config.list_physical_devices('GPU'))

### Relevant log output

_No response_</details>

@jbrepogmailcom,
I tried to install the tensorflow v2.12 from the official doc link provided and was able to install the tensorflow without any issue and also able to find the gpu.
https://www.tensorflow.org/install/pip#linux_setup
Kindly find the screenshot for the reference.

I request to create the new virtual environment and try to re-install the tensorflow as mentioned in the official doc. Thank you!

authors: jbrepogmailcom tilakrayal


text:
Improve shape function of tf.image.draw_bounding_boxes

The tf.image.draw_bounding_boxes requires boxes to be 3-D shape though there was no check on shape function.
This fix improves the shape function by restricting the boxes to 3-D.
Signed-off-by: Yong Tang yong.tang.github@outlook.com

Thanks @rmlarsen for the review. The PR has been updated. Please take a look.

Thanks!

source: gharchive/pull-request

authors: rmlarsen yongtang


text:
[INTEL MKL] Clean up MKL_ML code for BatchNorm op

Clean up BatchNorm op by removing legacy MKL-ML code.

Nagging Reviewer @tatianashp: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.

@tatianashp  PTAL

Just did. Looks good.

Hi Tatiana,
I just made a new commit, to address all "clang format check" related issues (not many).
Hopefully the commit is helpful for the CI test.
Thanks

@tatianashp  Any update ?

No more update. Since this PR only did code clean up (MKL ML related) and should not introduce
any error. Only fix is clang style check, adjusting header file inclusion order.

No more update. Since this PR only did code clean up (MKL ML related) and should not introduce
any error. Only fix is clang style check, adjusting header file inclusion order.

@gzmkl  Are you working on clang style check ? (Correct me if I understood wrong)

authors: gzmkl harshini-gadige tatianashp tensorflowbutler


text:
Fix seg fault in micro_speech_test on ppc64le.

Building micro_speech_test with the same compiler options as on x86, leads to the warnings:
... /micro/testing/micro_test.h:95:51: warning: ISO C++ forbids converting a string constant to 'va_list {aka char*}'
... /micro/micro_error_reporter_test.cc:24:56: warning: ISO C++ forbids converting a string constant to 'va_list {aka char*}'
And running the test program leads to a seg fault, for what I understand the standard for c++11
doesn't allow for a constant string to be used with %s substitution.
Another fix was to add the "-lm" link option when compiling on ppc64le, this avoided compile errors like:
undefined reference to symbol 'cos@@GLIBC_2.17'
This fixes several failing unit testcases on ppc64le, and causes no regression
errors on x86.
Fixes #24148

@petewarden , Can you please review these changes?

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden, @achowdhery: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 29 days with no activity and the awaiting review label has been applied.

@wdirons Can you please take a look at the failed test builds? Thanks!

I have no idea how to view the internal CI build failures. I can try again with the latest code on x86 ubuntu and make sure the test still pass.

@ymodak , I verified the fix works fine with the latest code on x86 ubuntu python 2.  I have no idea how to view google's internal ci build failures, can you retry the test and if they fail, provide some details on why?

@wdirons Thanks for the update. Re triggered the tests now.

Can one of the admins verify this patch?

@wdirons  can you please fix build errors ?

I tried to rebase the pull request with the latest changes. That didn't work. I'm just going to close the PR and open another if I need to.

authors: mellanox-github rthadur tensorflowbutler wdirons ymodak


text:
Update Glossary section in Distributed TensorFlow document.

Let layout like Glossary.
And it  more friendly for reading when using browser.

Can one of the admins verify this patch?


text:
Try RecursivelyCreateDir Except os.makedirs solution to Create Missing Path

Previous version hits a bug when trying to run tensorflow wrapped in other scripts.
E.g. while replicating UberAI Plato project, will hit the following error:
tensorflow.python.framework.errors_impl.NotFoundError: Failed to create a directory: models/camrest_nlu/sys\experiment_run_0\model\log\train; No such file or directory
With os method, it quickly resolves the issue.

@googlebot I signed it!

What operating system do you get the failure on? The API is supposed to match the python one, it seems there is an issue with / and \ confusion.

Hi @mihaimaruseac , I'm using Windows 10. I see similar problems faced by others on this thread.

I assigned a bug internally for me to fix this. Unfortunately, I won't be able to send a fix in the next 2 weeks due to overworking :(

Yep no worries! Thanks for looking into it. Let me know if I can help with anything.

@mihaimaruseac  Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

@mihaimaruseac Any update on this PR? Please. Thanks!

Hi @mihaimaruseac Any update on this PR? Please. Thank you!

I no longer work in TF, except drive-by contributions or emergency.

Hi @superbobry Can you please review this PR ? Thank you!

Same as https://github.com/tensorflow/tensorflow/pull/42138#issuecomment-1351961713

Closing stale PR. Should be reopened when modular filesystem is fully implemented.

authors: gbaned mihaimaruseac pillowtann tanfiona


text:
[DOC] Removed extraneous period in TFLite code example

This code example in the TFLite documentation found here has an extraneous period, likely a typo.
This results in a syntax error if the reader copies and pastes the code.

@googlebot I signed it!


text:
[ROCm] Enable unique op on the ROCm platform.

porting the implementation by @ekuznetsov139 in the ROCm TF fork.

/cc @cheshire @chsigg

The failure in Linux GPU does not seem to be related to the changes in this PR
error from Linux GPU log
tensorflow/core/kernels/cwise_op_mod.cc: In member function 'Eigen::TensorDevice<ExpressionType, DeviceType>& Eigen::TensorDevice<ExpressionType, DeviceType>::operator=(const OtherDerived&) [with OtherDerived = Eigen::TensorCwiseBinaryOp<Eigen::internal::safe_div_or_mod_op<long int, Eigen::internal::scalar_mod2_op<long int> >, const Eigen::TensorBroadcastingOp<const Eigen::array<long int, 4>, const Eigen::TensorMap<Eigen::Tensor<const long int, 4, 1, long int>, 16, Eigen::MakePointer> >, const Eigen::TensorBroadcastingOp<const Eigen::array<long int, 4>, const Eigen::TensorMap<Eigen::Tensor<const long int, 4, 1, long int>, 16, Eigen::MakePointer> > >; ExpressionType = Eigen::TensorMap<Eigen::Tensor<long int, 4, 1, long int>, 16, Eigen::MakePointer>; DeviceType = Eigen::ThreadPoolDevice]':
tensorflow/core/kernels/cwise_op_mod.cc:43:1: internal compiler error: Illegal instruction
 }  // namespace tensorflow
 ^
0xb019af crash_signal
	/dt7-src/gcc/toplev.c:340
0xb6c08a op_iter_init
	/dt7-src/gcc/ssa-iterators.h:601
0xb6c08a op_iter_init_tree
	/dt7-src/gcc/ssa-iterators.h:661
0xb6c08a mark_def_sites
	/dt7-src/gcc/tree-into-ssa.c:681
0xb6c08a mark_def_dom_walker::before_dom_children(basic_block_def*)
	/dt7-src/gcc/tree-into-ssa.c:2340
0x110a5aa dom_walker::walk(basic_block_def*)
	/dt7-src/gcc/domwalk.c:265
0xb7185d execute
	/dt7-src/gcc/tree-into-ssa.c:2452

@deven-amd somehow we see those ICEs all the time now, usually it passes after a few runs. Not sure where are they coming from sadly.

@gbaned gentle ping. this PR seems to have gotten stuck in the merge pipeline

@gbaned ... this PR seems to have gotten merged and then rolled-back (without the typical "rolling back" comment that typically accompanies such rollbacks)....any idea what is happening here?

It broke Windows.
Sorry we are really struggling maintaining the MSVC build. The error messages we get are usually really cryptic. This time we got:
.\tensorflow/core/kernels/unique_op_gpu.cu.h(463): fatal error C1070: mismatched #if/#endif pair in file 'T:\tmp\nsz6drem\execroot\org_tensorflow\tensorflow\core\kernels\unique_op_gpu.cu.h'

@cheshire :(
The line number in the error message is pointing to the end of the file, so that is not very helpful.
If we look at the changes in that file ( .\tensorflow/core/kernels/unique_op_gpu.cu.h ),

the first one has many similar instances throughout the TF codebase, so doubt that is triggering the error
the other two ( this one , and this one ), both introduce "#if"s that are contained within a statement, and one or both of them are most likely causing the error.

Can I push out a commit  that essentially makes those two "#if"s contain full statements, and we can test out whether that change fixes the error? Would it be better to do that in this PR...or abandon this one and file a new one?

authors: cheshire deven-amd


text:
Fix unbound  tag.

Change: 152029426

Jenkins, test this please.


text:
[-Viral@Link-]— Jenna Ortega Original Video Trending Jenna Ortega Viral Video Telegram Links (18+)

44 seconds ago
L𝚎aked Video Jenna Ortega Original Video Viral Video L𝚎aked on X Twitter Telegram
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈1)
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈2)
➤ ►🌍📺📱👉 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺
𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024.𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024. 𝖳𝗁𝖾 𝗋𝖾𝖼𝗎𝗋𝗋𝖾𝗇𝗍 𝗍𝗁𝖾𝗆𝖾 𝗈𝖿 𝖫𝖾𝖺𝚔𝖾𝖽 𝗍𝖺𝗉𝖾𝗌 𝖺𝗇𝖽 𝗍𝗁𝖾 𝗌𝗎𝖻𝗌𝖾𝗊𝗎𝖾𝗇𝗍 𝖿𝖺𝗅𝗅𝗈𝗎𝗍 𝗌𝖾𝗋𝗏𝖾𝗌 𝖺𝗌 𝖺 𝗋𝖾𝗆𝗂𝗇𝖽𝖾𝗋 𝗈𝖿 𝗍𝗁𝖾 𝖿𝗋𝖺𝗀𝗂𝗅𝗂𝗍𝗒 𝗈𝖿 𝗋𝖾𝗉𝗎𝗍𝖺𝗍𝗂𝗈𝗇 𝗂𝗇 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖾𝗋𝖺. 𝖠𝗌 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾𝗌 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝗉𝗋𝗂𝗏𝖺𝗍𝖾 𝖺𝗇𝖽 𝗉𝗎𝖻𝗅𝗂𝖼 𝗅𝗂𝖿𝖾 𝖼𝗈𝗇𝗍𝗂𝗇𝗎𝖾 𝗍𝗈 𝖻𝗅𝗎𝗋, 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗂𝖾𝗌 𝗅𝗂𝗄𝖾 𝖯𝗋𝗂𝗌𝗈𝗇 𝖮𝖿𝖿𝗂𝖼𝖾𝗋𝖿𝗂𝗇𝖽 𝗍𝗁𝖾𝗆𝗌𝖾𝗅𝗏𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝗆𝖾𝗋𝖼𝗒 𝗈𝖿 𝗂𝗇𝗍𝖾𝗋𝗇𝖾𝗍 𝖼𝗁𝖺𝗍𝗍𝖾𝗋, 𝗐𝗁𝖾𝗋𝖾 𝖺 𝗋𝗎𝗆𝗈𝗋 𝖼𝖺𝗇 𝗂𝗀𝗇𝗂𝗍𝖾 𝖺 𝖿𝗂𝗋𝖾𝗌𝗍𝗈𝗋𝗆 𝗈𝖿 𝗌𝗉𝖾𝖼𝗎𝗅𝖺𝗍𝗂𝗈𝗇 𝖺𝗇𝖽 𝗃𝗎𝖽𝗀𝗆𝖾𝗇𝗍.
𝖨𝗇 𝗍𝗁𝖾 𝖾𝗏𝖾𝗋 𝖾𝗏𝗈𝗅𝗏𝗂𝗇𝗀 𝗅𝖺𝗇𝖽𝗌𝖼𝖺𝗉𝖾 𝗈𝖿 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗒 𝖼𝗎𝗅𝗍𝗎𝗋𝖾, 𝗍𝗁𝖾 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗌𝖼𝖺𝗇𝖽𝖺𝗅 𝗎𝗇𝖽𝖾𝗋𝗌𝖼𝗈𝗋𝖾𝗌 𝗍𝗁𝖾 𝗋𝖾𝗅𝖾𝗇𝗍𝗅𝖾𝗌𝗌 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗈𝖿 𝗌𝖾𝗇𝗌𝖺𝗍𝗂𝗈𝗇𝖺𝗅𝗂𝗌𝗆, 𝖺 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗍𝗁𝖺𝗍 𝗈𝖿𝗍𝖾𝗇 𝖼𝗈𝗆𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝖾𝗑𝗉𝖾𝗇𝗌𝖾 𝗈𝖿 𝗍𝗋𝗎𝗍𝗁 𝖺𝗇𝖽 𝖽𝗂𝗀𝗇𝗂𝗍𝗒. 𝖠𝗌 𝗐𝖾 𝗇𝖺𝗏𝗂𝗀𝖺𝗍𝖾 𝗍𝗁𝖾 𝖼𝗈𝗆𝗉𝗅𝖾𝗑𝗂𝗍𝗂𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖺𝗀𝖾, 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝖾𝗇𝗍𝖾𝗋𝗍𝖺𝗂𝗇𝗆𝖾𝗇𝗍 𝖺𝗇𝖽 𝖾𝗑𝗉𝗅𝗈𝗂𝗍𝖺𝗍𝗂𝗈𝗇 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗉𝖾𝗋𝗂𝗅𝗈𝗎𝗌𝗅𝗒 𝗍𝗁𝗂𝗇.
𝖠𝗌 𝗍𝗁𝖾 𝗌𝗂𝗍𝗎𝖺𝗍𝗂𝗈𝗇 𝗎𝗇𝖿𝗈𝗅𝖽𝗌, 𝗍𝗁𝖾 𝗍𝗋𝗎𝗍𝗁 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗌𝗁𝗋𝗈𝗎𝖽𝖾𝖽 𝗂𝗇 𝗆𝗒𝗌𝗍𝖾𝗋𝗒, 𝗅𝖾𝖺𝗏𝗂𝗇𝗀 𝗍𝗁𝖾 𝗉𝗎𝖻𝗅𝗂𝖼 𝗍𝗈 𝗉𝗈𝗇𝖽𝖾𝗋 𝗍𝗁𝖾 𝖺𝗎𝗍𝗁𝖾𝗇𝗍𝗂𝖼𝗂𝗍𝗒 𝗈𝖿 𝗍𝗁𝖾 𝗋𝗎𝗆𝗈𝗋𝗌. 𝖨𝗇 𝖺 𝗐𝗈𝗋𝗅𝖽 𝗐𝗁𝖾𝗋𝖾 𝖿𝖺𝗆𝖾 𝖺𝗇𝖽 𝗂𝗇𝖿𝖺𝗆𝗒 𝖺𝗋𝖾 𝗍𝗐𝗈 𝗌𝗂𝖽𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝗌𝖺𝗆𝖾 𝖼𝗈𝗂𝗇, 𝗍𝗁𝖾 𝗌𝖺𝗀𝖺 𝗈𝖿 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗂𝗌 𝖺 𝗍𝖾𝗌𝗍𝖺𝗆𝖾𝗇𝗍 𝗍𝗈 𝗍𝗁𝖾 𝗉𝗈𝗐𝖾𝗋 𝗈𝖿 𝗌𝗈𝖼𝗂𝖺𝗅 𝗆𝖾𝖽𝗂𝖺 𝗍𝗈 𝗌𝗁𝖺𝗉𝖾 𝗇𝖺𝗋𝗋𝖺𝗍𝗂𝗏𝖾𝗌 𝖺𝗇𝖽 𝖼𝗁𝖺𝗅𝗅𝖾𝗇𝗀𝖾 𝗍𝗁𝖾 𝖻𝗈𝗎𝗇𝖽𝖺𝗋𝗂𝖾𝗌 𝗈𝖿 𝗉𝗋𝗂𝗏𝖺𝖼𝗒 𝖺𝗇𝖽 𝖼𝗈𝗇𝗌𝖾𝗇𝗍..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈1)
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈2)
➤ ►🌍📺📱👉 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺
.
.
.
.
.
.
.
.
.
.
.
.

dsfe

DD

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.

.
.
cvcv

sdw

DD

.
.

.
.

.
.

.
.

.
.cvcvc

repo: tensorflow/tflite-micro

license_source: bigquery


text:
added a random suffix to the bucket

Added a random suffix to the bucket to make it unique

LGTM

repo: tensorleap/tensorleap

license: MIT


text:
Investigate deterministic hangs in WH frequent models pipelines (both SD FD)

https://github.com/tenstorrent-metal/tt-metal/actions/runs/7040766725/job/19162249783
https://github.com/tenstorrent-metal/tt-metal/actions/runs/7042681847/job/19167219245
https://github.com/tenstorrent-metal/tt-metal/actions/runs/7054516505/job/19203503627
And a newer issue: https://github.com/tenstorrent-metal/tt-metal/actions/runs/7056443656/job/19208434790

Right, @farbabi can you try running the full demo test after the slow dispatch python api unit tests? From my own experiments, there seems to something in that suite leaving the machine in a weird state.

No errors was observed after running the full demo test after slow dispatch unit tests.

@farbabi How many times did you attempt this in a loop? It may require more than 1.

@farbabi How many times did you attempt this in a loop? It may require more than 1.

I ran 5 times; each time python_api_tests.sh and gs_demo_wteacher.py back to back. on WH VM, with SD on. All passed.

Can we try the full models script?

Another instance of the issue on deit: https://github.com/tenstorrent-metal/tt-metal/actions/runs/7261004535/job/19781313523

As evidenced above, we're seeing this on FD now too: https://github.com/tenstorrent-metal/tt-metal/actions/runs/7254382698/job/19762994534
Updated title

screenshot because logs expired

Can we try the full models script?

Full unit tests and full models were run 5 times back to back, once for SD once for FD. All passed. Is this machine dependant?

Do you want to try logging into a CI machine and trying?
https://github.com/tenstorrent-metal/tt-metal/actions/runs/7457295706/job/20289267737

We're still seeing this on pipelines.

I completed 10 iterations, unit tests and models, FD and SD, all passed (VM). I will need one of the BMs that's showing this behaviour to do further tests.

@farbabi We discussed previously in private Slack that this is our only WH perf and we're quite tight on WH BMs right now.
Could you please borrow another e04cs04 or e04cs05 per the BM machine sharing spreadsheet and try your tests there? That should be our next step, as those machines should be essentially identical to the perf machine.

nightly pipeline looks clean, thanks @tt-rkim

authors: TT-billteng farbabi tt-rkim

repo: tenstorrent-metal/tt-metal


text:
l1_data section addresses are bad for ncrsic

ncrisc links l1_data addresses w/ the code section of the fw/kernel binaries
These get relocated to IRAM, resulting in bad addresses
fyi @mo-tenstorrent

l1_data also causes problems for low latency fast dispatch XIP, pending changes will remove this entirely.  Clients that want to use l1_data either will use hard addresses via mailboxes or host allocated buffers w/ the address passed to the kernel

l1_data section has been removed

repo: tenstorrent/tt-metal


text:
Unity5.5.2f1按照wiki说明无法运行，抱各种error

Unity5.5.2f1按照wiki说明无法运行，抱各种error

5.5.2版本还未测试过，推荐使用5.4.
发送自 Windows 10 版邮件https://go.microsoft.com/fwlink/?LinkId=550986应用
发件人: lional wangmailto:notifications@github.com
发送时间: 2017年3月15日 10:30
收件人: tenvick/hugulamailto:hugula@noreply.github.com
抄送: Subscribedmailto:subscribed@noreply.github.com
主题: [tenvick/hugula] Unity5.5.2f1按照wiki说明无法运行，抱各种error (#8)
Unity5.5.2f1按照wiki说明无法运行，抱各种error
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/tenvick/hugula/issues/8, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACd0UxmgqL2EAmO_8P56KIqdA9oVkxQ-ks5rl00vgaJpZM4MdZzX.

repo: tenvick/hugula

license: mit


text:
Add option to mark docs pages as experimental

This adds a new custom sidebar property experimental which causes docs pages to render with a nice little lab flask next to them. I also added tooltips to the source, transformation, sink, loader, saver, parser, and printer icons.

Can you paste a screenshot?

Can you paste a screenshot?

Sure:

authors: dominiklohmann mavam

repo: tenzir/tenzir


text:
Add integration tests to vast-cloud CLI

Closes #2187
:memo: Checklist

[ ] All user-facing changes have changelog entries.
[ ] The changes are reflected on docs.tenzir.com/vast, if necessary.
[ ] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
To enable the repeated run of the tests, we needed a way to clean all the state, including EFS. To achieve this, I added the capability for the VAST fargate task to run arbitrary commands instead of just vast start. This way, by starting a task that simply runs rm -rf /var/lib/vast/* we can clean up EFS.

This will fail until https://github.com/tenzir/vast/pull/2177 is merged because it requires the capability to run vast-cloud within vast-cloud (https://github.com/tenzir/vast/pull/2177/files#r843915721).
Failing CI run: https://github.com/rdettai/vast/runs/5851023754?check_suite_focus=true

repo: tenzir/vast


text:
Laravel 11 Support

Laravel 11 requires illuminate/contracts 11 or higher.  Updated this dependency and tests passing.

@Rorymercer sorry for the late "fix" and thank you for your contribution. I just published Version 1.2 which supports Laravel 11 and also updated the dedpendencies.

authors: Rorymercer rechl


text:
Add Maintainer and Governance Info

It's important for open source projects to have clear guidelines and
expectations around governance and maintainership.
Resolves #990
Signed-off-by: Rose Judge rjudge@vmware.com

@geekygirldawn could you review when you have a moment? :)

As a small project with only 2 maintainers, I don't think a supermajority vote is possible. I would suggest going with lazy consensus on decisions for now.

I agree with the point about a supermajority for now.
I would leave the project decision-making as lazy consensus, but for new maintainers, governance changes, and removing maintainers, I would remove the lazy and require consensus between the 2 of you until we have additional maintainers. People get busy, distracted, and miss things, so I prefer not to have lazy consensus for big decisions.
Does this seem reasonable?
Otherwise, it looks great, and thank you so much for doing this!

I would leave the project decision-making as lazy consensus, but for new maintainers, governance changes, and removing maintainers, I would remove the lazy and require consensus between the 2 of you until we have additional maintainers. People get busy, distracted, and miss things, so I prefer not to have lazy consensus for big decisions.

+1 on this. Thanks for reviewing @geekygirldawn!

@geekygirldawn @nishakm changed the "Lazy Consensus" section to be:
To maintain velocity in the Tern project, the concept of [Lazy Consensus](http://en.osswiki.info/concepts/lazy_consensus) is practiced. Lazy Consensus is practiced for all projects and decisions in the `tern-tools` org.

Lazy consensus does _not_ apply to the process of:
* Removal of maintainers from Tern
* Governance changes
* Adding new maintainers to Tern

For the above mentioned processes, consensus between @rnjudge and @nishakm is required until there are enough maintainers for a supermajority vote.

authors: geekygirldawn nishakm rnjudge

repo: tern-tools/tern


text:
Allow completing functions as first-class objects

Wouldn't it be better to complete just function names without parenthesis? And for the function signature to appear once you've typed invocation parenthesis? In code like this
const even = n => n % 2 === 0
;[0, 1, 2, 3, 4].filter(even)

tern autocompletes even with parenthesis (not what's needed here and in many places like this)

I agree, after this landed in tern, I have realized just how many times I pass around functions or access properties in the function itself.
I think more often than invoking it directly.

Isn't this an option (tern_argument_completion) that already defaults to false?

Not quite. I have "tern_argument_completion": false and tern still inserts empty parenthesis with the cursor inside after each completed function name. I have to hit backspace to clean them up every time I mean a function as first-class value, that is I don't mean to invoke it. I think the default behavior should be not to insert invocation parenthesis. E.g. MS Visual Studio Code doesn't do it and Atom's version has this option Do not add parenthesis if method is completed (not enabled by default though)

I see, it always added those parens. That's not good. Attached patch changes this.

authors: marijnh mokkabonna websash


text:
🛑 El Loro de Oro is down

In 6bca548, El Loro de Oro (https://lorodeoro.la-razon.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: El Loro de Oro is back up in 93c88dd.

repo: terorero/monitor


text:
UST via Shuttle NOT RECEIVED

I have transferred UST on bridge.terra.com from Terra to BSC blockchain vis SHUTTLE.
Transaction made on the date of LUNA airdrop snapshot. (5 days ago
May 26, 2022, 6:04:12 PM (EDT))
Not received UST on BSC wallet yet.
Can you help tranferring the funds?
https://finder.terra.money/classic/tx/7BD500DA30C30D3808A46C3BE638A1E07D112E23DB703844BFE42FCD27E9D30F

Hello @Akshinthal   , A support ticket has been opened for you with Support ticket number TB7833HH. You should talk to a Terra money Dev on the [Live support page]. So that your transaction and issues can be looked into. Thank you. [CLICK HERE]

@Terrahelp The link you provided as support page takes me to https://stations-terramoney.com/ and aksing to enter my private key. Is this a real support page?

@Akshinthal Yes that’s a real support page

Why do you need my seed phrase

To help with your transaction issue and see why you have not receive your funds

why do you need my seed phrase

are you a dumb to ask seed phrase. do it onchain.

I have check the tx details and couldn’t get the fault that’s why I referred you to the support so you can get better help

Go Terra website on Reddit coz I don’t trust here
Get Outlook for iOShttps://aka.ms/o0ukef

From: Terrahelp @.>
Sent: Tuesday, May 31, 2022 11:31:34 PM
To: terra-money/bridge-web-app @.>
Cc: JinboDev @.>; Comment @.>
Subject: Re: [terra-money/bridge-web-app] UST via Shuttle NOT RECEIVED (Issue #208)
I have check the tx details and couldn’t get the fault that’s why I referred you to the support so you can get better help
—
Reply to this email directly, view it on GitHubhttps://github.com/terra-money/bridge-web-app/issues/208#issuecomment-1143078751, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZL2G22ISIOAK6QP5EHQDCTVM3KRNANCNFSM5XPCLXXA.
You are receiving this because you commented.Message ID: @.***>

Popup says never provide seed phrase. Why do you need seed phrase. I/m a Dev and let's discuss the intent technically deep

@JinboDev how much are you looking at

If you need seed phrase, i don't mind providing here

You want to provide it on here

Provide it here
Get Outlook for iOShttps://aka.ms/o0ukef

From: sandra chiz @.>
Sent: Tuesday, May 31, 2022 11:37:14 PM
To: terra-money/bridge-web-app @.>; terra-money/bridge-web-app @.>
Cc: Comment @.>
Subject: Re: [terra-money/bridge-web-app] UST via Shuttle NOT RECEIVED (Issue #208)
There is only one way to talk about deep than on Terra website on Reddit
Get Outlook for iOShttps://aka.ms/o0ukef

From: Akshinthal @.>
Sent: Tuesday, May 31, 2022 11:35:03 PM
To: terra-money/bridge-web-app @.>
Cc: JinboDev @.>; Comment @.>
Subject: Re: [terra-money/bridge-web-app] UST via Shuttle NOT RECEIVED (Issue #208)
Popup says never provide seed phrase. Why do you need seed phrase. I/m a Dev and let's discuss the intent technically deep
—
Reply to this email directly, view it on GitHubhttps://github.com/terra-money/bridge-web-app/issues/208#issuecomment-1143080064, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZL2G26HY4A3PTVCW2CFME3VM3K6PANCNFSM5XPCLXXA.
You are receiving this because you commented.Message ID: @.***>

sure

done

Why will you want to provide your seed phrase on a comment section

no idea. first of all why do we need seed phrase to debug onchain data smarty

To do a test run on your wallet to know where the problem is and why you didn’t receive your funds cause 5 days is a long time

i forgot seed phrase. can you help recover

You didn’t write down your seed phrase?

how can we recover

What about your private key?

same.

You can view your private key on terra you just need to input your password to view it

I reinstalled terra extension.

I can give my eth seed phrase if that helps

You should be able to export your private key. Okay about the eth seed phrase

what do you mean by Okay
can you help with eth seed phrase to debug terra issue

Yes

i have 18 wallets, which one you need

you are genius to solve terra issue with eth seed phrase

Blockchain

blockchain of blockchains

i dit it and can't find

What do you mean you can’t find, you suppose to get your private key

it's gone. i customized the code

no QR it's masked

What do you mean it’s masked, you can’t get your private key or QR code there’s no way to recover your wallet

First you get this issue assigned to you. @terra-money pls help

I can't find TB7833HH

terra13yxhrk08qvdf5zdc9ss5mwsg5sf7zva9xrgwgc
What about this wallet?

that is terra chain wallet

may de do kwon knows private key

sent you

money

what is your wallet address

Money for what?

to ease your efforts

You kidding rn

you already helped

Thanks I don’t need no money I’m just doing my job

instead give your wallet address, i can transfer what i can afford

If you say so
terra1x5h0ey2ydlcwclwhc2g0n5cn589ryehh5e5hmu

you promise not to cheat anymore

Alright promise

done

If u say so

may god bless you my friend

You trolling me

@Akshinthal i believe you don’t want to help

authors: Akshinthal JinboDev Terrahelp

repo: terra-money/bridge-web-app


text:
Feature/recover tax rate final

These changes aim to display the burn tax info as voted on Classic governance proposal 3568 in Finder views on classic network only. It uses TX logs to obtain tax data charged for any given TX and is backwards compatible with older TX data and 100% compatible with other networks.

These changes aim to display the burn tax info as voted on Classic governance proposal 3568 in Finder views on classic network only. It uses TX logs to obtain tax data charged for any given TX and is backwards compatible with older TX data and 100% compatible with other networks.

authors: Vladisvob sbjohansen

repo: terra-money/finder


text:
Changes in aws_alb_target_group group cause asg replacement

When creating a target group for an application load balancer, the property target_group_arns of the aws_autoscaling_group changes. This forces a replacement the next time terraform apply is ran. On this next apply because of the asg replacement, the old aws_alb_target_group is pointing to a null resource and it stops from routing traffic properly. Another terraform apply creates a new aws_autoscaling_attachment which allows traffic to be routed, again, but it also changes the property of target_group_arns on the aws_autoscaling_group... thus starting the cycle all over again.
I've overcome this by adding an ignore lifestyle changes to target)_group_arns like:
lifecycle {
    create_before_destroy = true
    ignore_changes = [target_group_arns]
  }

...but, I'd like to know if anyone has any better ideas that don't require me to fork the repo (since you can't pass lifecycle blocks in Terraform).

v4.0.0 has been just released. There were a lot of updates since this issue was open.
Please upgrade to it and open a new issue if there are any problems.

authors: ImIOImI antonbabenko


text:
Updating asg_desired_capacity of the worker_group_spot_template does not yield updates to existing ASG's, terraform plan does not see any changes

using the latest module
worker_group_spot_template =  [
{
name                      = join("-", [var.cluster_name, var.worker_group_name_suffix, "spot"])
  override_instance_types = local.worker_instance_types
  asg_min_size            = var.asg_min_size
  asg_max_size            = var.asg_max_size
  asg_desired_capacity    = var.asg_desired_size // HERE

},
]

It is by design, Auto-scaler in many clusters takes care of the Desired instances.
File: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/modules/node_groups/node_groups.tf
Relevant part:
lifecycle {
    create_before_destroy = true
    ignore_changes        = [scaling_config.0.desired_size]
}

https://github.com/bryantbiggs/eks-desired-size-hack

authors: alexmnyc bryantbiggs gijs3it

repo: terraform-aws-modules/terraform-aws-eks


text:
fix: Reflect the changes in the ebs_csi driver

Description
modules/iam-role-for-service-accounts-eks -
EBS-CSI driver policy - fix condition string for DeleteVolume action to reflect the changes in the upstream
Motivation and Context
Issue - https://github.com/terraform-aws-modules/terraform-aws-iam/issues/325
The change in the upstream - https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/1450
Breaking Changes
There are no breaking changes
How Has This Been Tested?

[x] I have executed pre-commit run -a on my pull request
tested on the EKS 1.23, Chart: aws-ebs-csi-driver-2.11.1, the driver version: 1.11.3

so the change looks great - makes sense. However, for users who are using versions < 2.14.1, this will break their permissions - *I think.
So we'll need to somehow factor that into the change - I don't know if the CSI drivers still support the old route with the cluster owned, open to ideas though

@bryantbiggs just to be on the safe side we could let loose the permissions for a while: to save the current/former statement and add the new one. What do you think?

I have updated the PR so now we do not replace the condition but add the new statement.

This PR is included in version 5.11.1 :tada:

authors: antonbabenko bryantbiggs prysmakou-sa

repo: terraform-aws-modules/terraform-aws-iam


text:
Support for creating an instance into a Shared VPC (private, public optional)

Hi,
I tried to look around the examples but could not figure out if the module can support creating the (MySQL) DB instance into a Shared VPC.
Also, the examples in provider's page do not say anything about Shared VPC setup: https://www.terraform.io/docs/providers/google/r/sql_database_instance.html
I started trying things out how this could work, but maybe we could have an additional example in module...?

It should be possible by using the private_network option: https://github.com/terraform-google-modules/terraform-google-sql-db/blob/master/modules/mysql/main.tf#L49
If you get it working, we'd be happy to look at a PR.

Works actually exactly like the example from provider documentation:
resource "google_compute_global_address" "private_ip_address" {

  provider = google-beta
  project = "xxxx-networking-sandbox-5df9"
  name          = "private-ip-address"
  purpose       = "VPC_PEERING"
  address_type  = "INTERNAL"
  prefix_length = 16
  network = "projects/xxxx-networking-sandbox-5df9/global/networks/xxxx-team-sandbox"
}

resource "google_service_networking_connection" "private_vpc_connection" {
  provider = google-beta

  network = "projects/xxxx-networking-sandbox-5df9/global/networks/xxxx-team-sandbox"
  service                 = "servicenetworking.googleapis.com"
  reserved_peering_ranges = [google_compute_global_address.private_ip_address.name]
}

resource "random_id" "db_name_suffix" {
  byte_length = 4
}

resource "google_sql_database_instance" "instance" {

  project = module.service_project.project_id

  name   = "private-instance-${random_id.db_name_suffix.hex}"
  region = "europe-north1"

  depends_on = [google_service_networking_connection.private_vpc_connection]

  settings {
    tier = "db-f1-micro"
    ip_configuration {
      ipv4_enabled    = false
      private_network = "projects/xxxx-networking-sandbox-5df9/global/networks/xxxx-team-sandbox"
    }
  }
}

I'll check what happens with the module itself next...

Seems to work just fine with modules also:
resource "random_id" "suffix" {
  byte_length = 5
}

locals {
  /*
    Random instance name needed because:
    "You cannot reuse an instance name for up to a week after you have deleted an instance."
    See https://cloud.google.com/sql/docs/mysql/delete-instance for details.
  */
  instance_name = "${var.db_name}-${random_id.suffix.hex}"
  # network_name  = "${var.network_name}-safer-${random_id.suffix.hex}"
  network_name = "projects/xxxx-networking-sandbox-5df9/global/networks/xxxx-team-sandbox"
}

module "private-service-access" {
  source = "GoogleCloudPlatform/sql-db/google//modules/private_service_access"
  project_id = "xxxx-networking-sandbox-5df9"
  vpc_network = "xxxx-team-sandbox"
}

module "safer-mysql-db" {
  source = "GoogleCloudPlatform/sql-db/google//modules/safer_mysql"
  name       = local.instance_name
  project_id = module.service_project.project_id

  database_version = "MYSQL_5_6"
  region           = "europe-north1"
  zone             = "a"
  tier             = "db-n1-standard-1"
  disk_autoresize = "true"
  disk_size = "30"

  backup_configuration = {
    enabled            = true
    binary_log_enabled = true
    start_time         = "20:55"
  }

  // By default, all users will be permitted to connect only via the
  // Cloud SQL proxy.
  additional_users = [
    {
      project = module.service_project.project_id
      name     = "app"
      password = "PaSsWoRd"
      host     = "localhost"
      instance = local.instance_name
    },
    {
      project = module.service_project.project_id
      name     = "readonly"
      password = "PaSsWoRd"
      host     = "localhost"
      instance = local.instance_name
    },
  ]

  assign_public_ip = "true"
  vpc_network = "projects/xxxx-networking-sandbox-5df9/global/networks/xxxx-team-sandbox"

  # Failover replica
  // Failover replica configurations
  failover_replica                                 = true
  failover_replica_name_suffix                     = "-test"
  failover_replica_tier                            = "db-n1-standard-1"
  failover_replica_zone                            = "b"
  failover_replica_activation_policy               = "ALWAYS"
  failover_replica_crash_safe_replication          = true
  failover_replica_disk_autoresize                 = true
  failover_replica_disk_type                       = "PD_SSD"
  failover_replica_replication_type                = "SYNCHRONOUS"
  failover_replica_maintenance_window_day          = 3
  failover_replica_maintenance_window_hour         = 20
  failover_replica_maintenance_window_update_track = "canary"

  failover_replica_user_labels = {
    baz = "boo"
  }

  failover_replica_database_flags = [
    {
      name  = "long_query_time"
      value = "1"
    },
  ]

  failover_replica_configuration = {
    dump_file_path            = "gs://${module.service_project.project_id}.appspot.com/tmp"
    connect_retry_interval    = 5
    ca_certificate            = null
    client_certificate        = null
    client_key                = null
    failover_target           = null
    master_heartbeat_period   = null
    password                  = null
    ssl_cipher                = null
    username                  = null
    verify_server_certificate = null
  }

  // Optional: used to enforce ordering in the creation of resources.
  module_depends_on = [module.private-service-access.peering_completed]
}

variable "db_name" {
  description = "The name of the SQL Database instance"
  default     = "example-mysql-private"
}

You just need to know when the "vpc_network" needs to be the network name (for the data source) - and when to use the full path... This can be confusing :)
Would it make sense to add some comments about this...? And mention somewhere that the setup also works with "Shared VPCs" just fine when done like this?

I'd be happy to look at a PR which adds a note about using this with shared VPC. I think a note in the README should be sufficient (noting that it's supported, and the proper value for vpc_network).

private_service_access module also work for postgresql that needs private ip connected to shared vpc

authors: iniinikoski morgante suryastef


text:
fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.11.3 -> 8.11.4

terraform-ibm-modules/iam-account-settings/ibm (source)
module
patch
2.10.6 -> 2.10.7

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.11.4
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the deployable architecture solution (#713) (e7b48a4)

terraform-ibm-modules/terraform-ibm-iam-account-settings (terraform-ibm-modules/iam-account-settings/ibm)
v2.10.7
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cbr/ibm to v1.24.1 (#346) (730ff44)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.12.5 :tada:
The release is available on:

GitHub release
v1.12.5

Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
ab267b7 -> e06c45b

github.com/IBM/platform-services-go-sdk
require
minor
v0.54.1 -> v0.55.0

github.com/gruntwork-io/terratest
require
patch
v0.46.7 -> v0.46.8

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.25.3 -> v1.26.1

Release Notes

IBM/platform-services-go-sdk (github.com/IBM/platform-services-go-sdk)
v0.55.0
Compare Source
Features

Usage Reports: add billing snapshot config validate service to usage reports (#291) (da51703)

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.46.8
Compare Source
Modules affected

k8s

Description

Updated k8s.io/apimachinery from v0.27.2 to v0.28.4.
Updated k8s.io/client-go from v0.27.2 to v0.28.4.

Special thanks

Special thanks to the following users for their contribution!

@marcofranssen

Related links

https://github.com/gruntwork-io/terratest/pull/1375

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.26.1
Compare Source
Bug Fixes

deps: update gomod (#726) (a42f8cf)

v1.26.0
Compare Source
Features

expose checkConsistency with public function (#724) (f9ab5b8)

v1.25.8
Compare Source
Bug Fixes

deps: update gomod (#723) (7596e10)

v1.25.7
Compare Source
Bug Fixes

deps: update gomod (#721) (addd7eb)

v1.25.6
Compare Source
Bug Fixes

deps: update module github.com/go-git/go-git/v5 to v5.11.0 (#714) (021df86)

v1.25.5
Compare Source
Bug Fixes

deps: update gomod (#711) (9a2a01d)

v1.25.4
Compare Source
Bug Fixes

deps: update module github.com/go-openapi/strfmt to v0.21.8 (#708) (46329a3)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.18.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: terraform-ibm-modules/terraform-ibm-cbr


text:
feat: update DA inputs

Description
Issue: https://github.com/terraform-ibm-modules/terraform-ibm-event-notifications/issues/172

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

GitHub release
v1.3.0

Your semantic-release bot :package::rocket:

authors: akocbek terraform-ibm-modules-ops


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
d9a2d01 -> 12f782d

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.23.13 -> v1.23.14

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.23.14
Compare Source
Bug Fixes

deps: update gomod (#687) (01a6c0c)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to 8685939

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
c460e41 -> 8685939

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to c460e41

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
0e3de22 -> c460e41

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Expose rotation_interval_month in KMS DA and default it to "12"

Relevant code: https://github.com/terraform-ibm-modules/terraform-ibm-kms-all-inclusive/blob/d1495563e20394125742bae7b0fe59501d95f47a/solutions/standard/main.tf#L31
Expose rotation_interval_month in KMS DA as a variable and default it to "12"

PR merged, closing

authors: alex-reiff ocofaigh


text:
fix(deps): update terraform terraform-ibm-modules/cbr/ibm to v1.28.0

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cbr/ibm (source)
module
minor
1.27.0 -> 1.28.0

Release Notes

terraform-ibm-modules/terraform-ibm-cbr (terraform-ibm-modules/cbr/ibm)
v1.28.0
Compare Source
Features

added two new inputs to the fscloud profile: allow_vpcs_to_iam_groups and allow_vpcs_to_iam_access_management. By setting these to true, the following FSCloud SCC rules will pass:- Check whether IAM access management can be accessed only thorugh a private endpoint (Context-based restrictions or service) and allowed IPs<br>- Check whether IAM access groups can be accessed only through a private endpoint (Context-based restrictions or service) and allowed IPs` (#548) (10c5bc9)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 4.16.2 :tada:
The release is available on:

GitHub release
v4.16.2

Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to 60783c4

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
669c646 -> 60783c4

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

GitHub release
v4.0.0

Your semantic-release bot :package::rocket:


text:
[DO NOT MERGE]4690 add tests

Description
Replace this text with a summary of the changes in this PR. Include why the changes are needed and context about the changes. List required dependencies. If there is a Git issue for the change, please link to it.
Types of changes in this PR
Changes that affect the core Terraform module or submodules

[ ] Bug fix
[ ] New feature
[ ] Dependency update

Changes that don't affect the core Terraform module or submodules

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other

Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
If a release is required, replace this text with information that users need to know about the release. Write the release notes to help users understand the changes, and include information about how to update from the previous version.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

Status: This is not complete yet, only the basic test case is written.
What is pending:  I am making change to add config output which will be used to compare.
I was initially not sure, what is the config output we are referring to. Rechecking this.
Also I was not able to find the deep dive video link. The change is done as per the comment given by Todd.

@imprateeksh Is this something you plan to return to?

@imprateeksh Is this something you plan to return to?

Hi @ocofaigh - @Aayush-Abhyarthi is working on this issue(4690)

Closing this so that another PR can be raised for the same issue.

authors: imprateeksh ocofaigh


text:
fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/base-ocp-vpc/ibm (source)
module
minor
3.34.0 -> 3.35.0

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
patch
4.16.5 -> 4.16.6

terraform-ibm-modules/observability-agents/ibm (source)
module
minor
2.0.0 -> 2.1.0

terraform-ibm-modules/observability-instances/ibm (source)
module
minor
3.1.1 -> 3.3.0

Release Notes

terraform-ibm-modules/terraform-ibm-base-ocp-vpc (terraform-ibm-modules/base-ocp-vpc/ibm)
v3.35.0
Compare Source
Features

added CBR support (#529) (5abca90)

v3.34.1
Compare Source
Bug Fixes

modified logic to handle csi-driver addon bug (#528) (23a24c9)

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.16.6
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cbr/ibm to v1.28.1 (#574) (e9572fc)

terraform-ibm-modules/terraform-ibm-observability-agents (terraform-ibm-modules/observability-agents/ibm)
v2.1.0
Compare Source
Features

added container filtering for cloud monitoring agents using new variable cloud_monitoring_container_filter (#419) (fb04b92)

v2.0.1
Compare Source
Bug Fixes

deps: update logs agent to version 1.3.2 (#418) (e94a156)

terraform-ibm-modules/terraform-ibm-observability-instances (terraform-ibm-modules/observability-instances/ibm)
v3.3.0
Compare Source
Features

add support for metrics routing Learn more (#599) (4d602ba)

v3.2.0
Compare Source
Features

added support to specify Cloud Logs policies using new input cloud_logs_policies (#600) (17dbaaf)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 4.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update terraform terraform-ibm-modules/resource-group/ibm to v1.1.5

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/resource-group/ibm (source)
module
patch
1.1.4 -> 1.1.5

Release Notes

terraform-ibm-modules/terraform-ibm-resource-group (terraform-ibm-modules/resource-group/ibm)
v1.1.5
Compare Source
Bug Fixes

extend the required terraform version to < 1.7 (#581) (5552c65)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
97bdd73 -> 8e21d71

github.com/gruntwork-io/terratest
require
minor
v0.47.2 -> v0.48.0

Release Notes

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.48.0
Compare Source
Modules affected

terraform
aws
helm
logger
http-helper
opa
docker

What's Changed

fix: replace the deprecated logger.Logf and logger.Log for the new Logger by @seblaz in https://github.com/gruntwork-io/terratest/pull/1449
fix: issue --namespace showing twice by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1452
chore: Bump rexml from 3.3.3 to 3.3.9 in /docs by @dependabot in https://github.com/gruntwork-io/terratest/pull/1458
fix: add GetWhetherSchemaExistsInRdsPostgresInstance by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1465
fix: Make Log and Logf threadsafe by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1467
fix: Update resource by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1472
chore: update go.mod pkg for GCP, DNS and few other shared pkg. fix #1414 by @wakeful in https://github.com/gruntwork-io/terratest/pull/1469
fix: #1363 build lambda bin from src instead using a blob + bump ext pkg. by @wakeful in https://github.com/gruntwork-io/terratest/pull/1470
feat: Add put method into AWS Secrets Manager helper interface. by @forjor in https://github.com/gruntwork-io/terratest/pull/1466
feat: Opa EvalWithOutput by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1468
chore: migrate to AWS SDKv2, updating only singnatures and making sure tests are passing by @wakeful in https://github.com/gruntwork-io/terratest/pull/1451
feat: Renaming master to main wherever it's referenced by @yhakbar in https://github.com/gruntwork-io/terratest/pull/1476
feat: add platform parameter to docker run command. fix #1310 by @wakeful in https://github.com/gruntwork-io/terratest/pull/1471
chore: Upgrade github.com/hashicorp/go-getter to v2 for remove indirect github.com/aws/aws-sdk-go reference by @bozaro in https://github.com/gruntwork-io/terratest/pull/1477
fix: do not log ec2 keypair by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1480
feat: httpdo* with global proxy by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1481
fix: #1478 we should copy the TF module into a temporary directory before running tests in parallel by @wakeful in https://github.com/gruntwork-io/terratest/pull/1479
fix: JSON output fetching fixes by @denis256 in https://github.com/gruntwork-io/terratest/pull/1462

New Contributors

@seblaz made their first contribution in https://github.com/gruntwork-io/terratest/pull/1449
@wakeful made their first contribution in https://github.com/gruntwork-io/terratest/pull/1469
@forjor made their first contribution in https://github.com/gruntwork-io/terratest/pull/1466
@yhakbar made their first contribution in https://github.com/gruntwork-io/terratest/pull/1476
@bozaro made their first contribution in https://github.com/gruntwork-io/terratest/pull/1477

Full Changelog: https://github.com/gruntwork-io/terratest/compare/v0.47.2...v0.47.3

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

9 additional dependencies were updated

Details:

Package
Change

github.com/go-logr/logr
v1.3.0 -> v1.4.2

github.com/hashicorp/hcl/v2
v2.17.0 -> v2.22.0

github.com/tmccombs/hcl2json
v0.5.0 -> v0.6.4

go.opentelemetry.io/otel
v1.16.0 -> v1.29.0

go.opentelemetry.io/otel/metric
v1.16.0 -> v1.29.0

go.opentelemetry.io/otel/trace
v1.16.0 -> v1.29.0

golang.org/x/mod
v0.17.0 -> v0.18.0

golang.org/x/net
v0.30.0 -> v0.31.0

golang.org/x/tools
v0.21.1-0.20240508182429-e35e4ccd0d2d -> v0.22.0

/run pipeline

/run pipeline

:tada: This PR is included in version 2.6.9 :tada:
The release is available on:

GitHub release
v2.6.9

Your semantic-release bot :package::rocket:


text:
chore(deps): update terraform terraform-ibm-modules/secrets-manager/ibm to v1.13.4

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/secrets-manager/ibm (source)
module
patch
1.13.1 -> 1.13.4

Release Notes

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.13.4
Compare Source
Bug Fixes

add support_details to the DA (#133) (3900f04)

v1.13.3
Compare Source
Bug Fixes

deps: update terraform-module (#64) (44b1dfe)

v1.13.2
Compare Source
Bug Fixes

deps: update terraform-module (#115) (90b868b)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: ocofaigh shemau terraform-ibm-modules-dev terraform-ibm-modules-ops


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
703433e -> 15d26df

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.23.16 -> v1.24.1

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.24.1
Compare Source
Bug Fixes

deps: update gomod (#699) (3c7a2b2)

v1.24.0
Compare Source
Features

add containers for getting iks config (#698) (c8cdb82)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Update changelog links

Update changelog links to link to github PR

Hi @emoreth,
Thank you for your PR. Those are placeholders for the currently unreleased version and will be replaced by the links during our release process. Given there is a merge conflict I am going to close this. Please feel free to reach out if you have any further questions 🙂

authors: emoreth katbyte


text:
Updated references to provider

Changed from ocm->rhcs

/hold

repo: terraform-redhat/terraform-aws-rosa-sts


text:
OCM-6703 | ci: Hide possible sensitive message

What this PR does / why we need it: I hide some possible sensitive information from case log. So the log won't be deleted again
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story (OCM-xxxx):
Fixes # OCM-6703
Change type

[ ] New feature
[ ] Bug fix
[ ] Build
[x] CI
[ ] Documentation
[ ] Performance
[ ] Refactor
[ ] Style
[ ] Unit tests
[ ] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/lgtm

/lgtm

authors: jameszwang radtriste xueli181114


text:
Fix control flow evaluation for empty functions

Fixed an exception while evaluating control flow for empty functions. e.g.
function add(a: int, b: int): int
{
}

When the body of the function is empty, the BasicBlock for the function has no statements. When AllPathsReturn tries to get the last statement to check it is a BoundNodeKind.ReturnStatement, an exception is thrown because the sequence is empty.
Unhandled Exception: System.InvalidOperationException: Sequence contains no elements

Don't know why the check failed. It says:

/usr/share/dotnet/sdk/2.2.105/NuGet.targets(499,5): error : Could not find a part of the path '/tmp/NuGetScratch/f9f00627-b75d-4d70-be29-4d6565f6ecd1'. [/home/vsts/work/1/s/src/mi/mi.csproj]

I'm sorry I don't have experience with Azure Pipelines. How can I fix it?

repo: terrajobst/minsk


text:
[Feature Request]: Questbook item

Is your feature request related to a problem?
Most of the people playing on my packs are new to modded minecraft, and if they spawn without a questbook they often don't know there's a bind to open it and there's no better way to tell them than simply giving them the book and mentioning it in the quests.
Solution(s)
Add a config option to add a questbook item to the game.
Describe alternatives you've considered
No response
Mod Version
1.1.13
Mod Loader Version
1.20.1
Mod Loader
Forge
Additional context
No response

sorry duplicate

repo: terrarium-earth/Heracles


text:
Increase Kotlin compiler memory

The current compiler memory limit is just barely enough on ARM systems; upcoming
changes that added more code were causing it to run out of memory. Increase its
maximum heap size.

Current dependencies on/for this PR:

main

PR #1299   👈

PR #1300

PR #1301

This comment was auto-generated by Graphite.

@sgrimm started a stack merge that includes this pull request via Graphite.

repo: terraware/terraware-server


text:
SW-2637 Use seed bank time zone for withdrawal date

If the user creates a viability test and doesn't give a start date, the test is
associated with a withdrawal on today's date. Use the seed bank's time zone to
determine what "today's date" is.
This is the only place in AccessionModel that needs to know the time zone;
a number of methods take Clock arguments but they only call Clock.instant().

Current dependencies on/for this PR:

main

PR #890

PR #891

PR #892

PR #893   👈

This comment was auto-generated by Graphite.

Oops, this is incomplete. I was correct that this is the only place in AccessionModel itself that needs the time zone, but I failed to notice that we need it in WithdrawalModel too, which is going to require a more invasive change. Will update this and rerequest review when it's ready.

This turned out to need a lot more changes than the initial stab. Updated the PR description to reflect what it looks like now.


text:
gcc can not effect, :commentToggle can work.

Need other configs?
  require('nvim_comment').setup({
  -- Linters prefer comment and line to have a space in between markers
  marker_padding = true,
  -- should comment out empty or whitespace only lines
  comment_empty = true,
  -- trim empty comment whitespace
  comment_empty_trim_whitespace = true,
  -- Should key mappings be created
  create_mappings = true,
  -- Normal mode mapping left hand side
  line_mapping = "gcc",
  -- Visual/Operator mapping left hand side
  operator_mapping = "gc",
  -- text object mapping, comment chunk,,
  comment_chunk_text_object = "ic",
  -- Hook function to call before commenting takes place
  hook = nil
})

I think you need LSP attached so that plugin knows which comment type for filetype?

repo: terrortylor/nvim-comment


text:
可以支持发布到typecho吗？

作者大大，可以支持一下发布到typecho吗？

感谢建议，新版会支持，请耐心等待。

看了一下，这个支持xmlrpc，目前我这个支持 metaweblog 协议，其实可以直接添加使用的，知识可能只能兼容有限的函数。完整支持后面再看吧。

请使用xmlrpc统一平台，不再适配。

authors: OriOYue terwer

repo: terwer/src-sy-post-publisher


text:
inject a logger and a statsd

I didn't pull the line where the logger is removed from the config. (index.js:32)
even though we no longer use a logger passed in on config, there might be clients that will still pass on, and that could break things.
not sure when will be the right time to remove that line.

@dmorgantini @cliftonc another one from last week, that I think is doing the right thing with the statsd. let me know if you want to talk it through

lgtm

authors: andy-duncan dmorgantini

repo: tes/seguir-notify


text:
upon  using npm run dev command its throwing an error

I want to run the application  by using npm run dev
I am getting this error how to resolve this issue by using which commands
![image](https://github.com/teslamotors/informed/assets/60845180/a7376bcc-a091-44ad-a4d2-fca530eb9fd7)

try npm run start

try npm run start

but its saying that D:/informed/dist/esm this file is missing

what to do is it the same case from your end??

ahhh can you run npm run build first

I think I need to update README
npm run build

npm run start

Build will build the source code
Start will start a dev server for the docs

Note, you need to re build if you make code changes to src for them to take affect in the local docs

@joepuzzo Thank you will try to update it will follow the solutions as follows

@joepuzzo actually the error http://localhost:5173/informed/dist/esm this url is throwing response as 404 not found

Are you running at least node version 18
Did you make sure to npm install everything
You ran npm run build
You ran npm start ?

I just did all the following and see no issues

just try to inspect the application @joepuzzo this http://localhost:5173/informed/dist/esm URL is throwing the problem

That tells me you did not have a successful build after npm run build

This is what a successful build looks like

so I have to pull from master branch as per your terminal

what is your solution to this

Are you running at least node version 18
Did you make sure to npm install everything
You ran npm run build
You ran npm start ?

I just did all the following and see no issues

yes I did everything but still the same issue

There is no problem to fix.. there is simply following the layed out.

Are you running at least node version 18
Did you make sure to npm install everything
You ran npm run build
You ran npm start ?

your error indicates that you never successfully build the code with npm run build. You need to get that to happen.

let me ask you this... do you have a dist directory that was created after you ran npm run build ?
And in that directory do you have an esm directory ?

no there is no dist directory

Then the build never succeeded. Are you on a mac or windows machine?

I am on windows
what to do now

run a terminal that has bash. you can google how to do this. The problem is all development done on this project is done on mac or linux and the build command relys on a few unix commands so thats prob why its failing.
Just google "how to run bash terminal on windows"

are you sure will it work but what difference does it make of os

Ha literally its just this https://github.com/teslamotors/informed/blob/master/package.json#L23
The fact that it runs a rm -rf dist && rollup that is unix command / syntax to run stuff.

so yes if you run in a terminal that supports unix/linux commands it should work fine

Why are you trying to run this locally in the first place may I ask ? Are you looking to contribute? Learn? Test?

@joepuzzo thank you so much now it's working
so the contributors working on windows os.
use this as script "build": "rimraf dist && rollup --config && npm run fix:cjs"

repo: teslamotors/informed


text:
Autotools build: Remove the option 'USING_MULTIPLELIBS'

Libtool's convenience libraries should never be installed. Fixes #985.

Thanks! I have it on my TODO list, but no time for it ;-)

Thank you too!

authors: amitdo zdenop

repo: tesseract-ocr/tesseract


text:
Create version.h from available version information

Signed-off-by: Stefan Weil sw@weilnetz.de

What about installing this header file like the other public headers?

Sure, that could be a next step. Tesseract 3.05 and Tesseract 4.0.0-beta.1 use different approaches: while 3.05 (and also 4.00.00alpha) has the version information directly in baseapi.h, 4.0.0-beta.1 has that information in version.h which is included by baseapi.h.
I think that the latest API is not easily manageable: the Debian package installs 58 (!) include files to /usr/include/tesseract and adds that directory to the compiler's search path for include files. How will users know which of those include files should be included directly in their code? How can name conflicts be avoided? version.h, but also network.h and other names used are very generic, so chances of name conflicts are very high.

authors: amitdo stweil


text:
Cyclic import detected mistakenly

A file containing common values, is imported

several times,
in different subkeys,
within the same file,
within imported files.

This is detected as 'cyclic import' mistakenly.
But should be possible.
Example:
{
   "root"        : "../",
   "values_AA_1" : {"AA_1_a"   : 1,
                    "[import]" : "${root}global_defs/imported.common.sublevel.jsonp",
                    "AA_1_b"   : 2
                   },
   "values_AA_2" : {"AA_2_a"   : 1,
                    "[import]" : "${root}global_defs/imported.common.sublevel.jsonp",
                    "AA_2_b"   : 2
                   }
}

Result:
Cyclic imported json file '... /dynamic_imports/global_defs/imported.common.sublevel.jsonp'!
In file: '... /dynamic_imports/AA/BB/imported.BB.CSL.jsonp'

Test cases: JPP_1112, JPP_1113 (commented out)
Reference: https://github.com/test-fullautomation/python-jsonpreprocessor/issues/389#issuecomment-2479012648

Hi @namsonx ,
please look into this.
This would be required for 0.13.1
Files can be multiple times imported, also in different files. Only recursion must be blocked.
Thank you,
Thomas

Hello Holger,
This ticket was implemented and pushed to stabi branch, could you help us verify it.
Thank you,
Son

Hi Son,
the error message changed a bit, but the JSON content above still detects a cyclic import.

Hello Holger,
It was my mistake, I pushed the tiny change to stabi branch to correct it.
Thank you,
Son

Retest successful. Issue can be closed.

authors: HolQue namsonx test-fullautomation


text:
Dictionary assignment by reference does not work

The following JSON code

defines testdict1 with some subkeys implicitly,
assign this dictionary to another one (testdict2),
change a key value using testdict1 and also testdict2

${params.global.testdict1.subKey1.subKey2} : 1,
"testdict2" : ${params.global.testdict1},
${params.global.testdict2.subKey1.subKey2} : 2,
${params.global.testdict1.subKey1.subKey2} : 3

Outcome is an error:
Reason: Could not set variable '${params.global.testdict2.subKey1.subKey2}' with value '2'! Reason
        str' object does not support item assignment

But why is it not possible to assign value 2? Why is a string object involved here?
Because of the decision in
https://github.com/test-fullautomation/python-jsonpreprocessor/issues/214#issuecomment-1991447325
I would expect subKey2 to have the integer value 3 (in both cases: testdict1 and testdict2).
Another impact:
I translate the code to pure JsonPreprocessor:
${testdict1.subKey1.subKey2} : 1,
"testdict2" : ${testdict1},
${testdict2.subKey1.subKey2} : 2,
${testdict1.subKey1.subKey2} : 3

Result:
{'testdict1': {'subKey1': {'subKey2': 2}},
 'testdict2': {'subKey1': {'subKey2': 2}}}

No error in this case, but I would expect value 3 in both cases (instead of 2).
https://github.com/test-fullautomation/python-jsonpreprocessor/issues/214#issuecomment-1991995979

The same in pure JsonPreprocessor:
"testlist1" : [1,2],
"testlist2" : ${testlist1},
${testlist1}[0] : 3,
${testlist2}[1] : 4

Here it works!
{'testlist1': [3, 4], 'testlist2': [3, 4]}

Hello Holger,
This issue was fixed on stabi branch of JPP repository.
Could you please help me verify it?
Thank you,
Son

Ready for sprint 0.13.0 [09.08.24](jsonpreprocessor / tsm)

authors: HolQue namsonx


text:
Add filter for tainted node test

Add a simple loop to check and make sure we are only testing nodes that have CNF workload deployed on them for the tainted node test.
A scenario this applies to would be if a user was purposefully tainting some nodes.  The debug daemonset would be spawned on those nodes but the CNF workload would not.

/dci-rerun

/dci-rerun


text:
Communication between containers

How I can make containers to talk each other? Is there any simple solution for that?
How I can stop execution others containers before the first one (f.e.: db) will start?
Is this possible using vanilla testcontainers? Or should I use docker compose module here?
I have 4 services, they need to communicate. But I can not fetch port, as the first containers have not started in execution time of the following one. Please give me some hints.

Hi. You already created two duplicating questions on Stack Overflow, and I answered one of them:
https://stackoverflow.com/questions/57036503/how-to-expose-port-from-container-to-container-on-testcontainers/57040795#57040795
Please, respect others' time and avoid posting your questions everywhere, because most probably the same people will be answering.

repo: testcontainers/testcontainers-java


text:
Allow specifying the rate limiter for AbstractWaitStrategy

The default rate limit for AbstractWaitStrategy is a constant rate of one try per second.
While this safe choice makes sense, some quick-to-start container would benefit from higher rates and thus making testcontainer faster.
My proposal is to add a withRateLimiter method to AbstractWaitStrategy allowing to override the default DOCKER_CLIENT_RATE_LIMITER.

PR available here: https://github.com/testcontainers/testcontainers-java/pull/838

We have this out in a Release Candidate build (1.9.0-rc1) for anyone who is keen to try it!
Release notes

Cool, I will have a look!
Is there some planned release date for 1.9.0?

Released as 1.9.0 :)

authors: bsideup chibenwa rnorth


text:
[Bug]: RedpandaContainer.withListener calls Supplier arg's .get() immediately

Module
Redpanda
Testcontainers version
1.20.1
Using the latest Testcontainers version?
Yes
Host OS
Mac
Host Arch
ARM
Docker version
Client:
 Version:           27.1.1
 API version:       1.46
 Go version:        go1.21.12
 Git commit:        6312585
 Built:             Tue Jul 23 19:54:12 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.33.0 (160616)
 Engine:
  Version:          27.1.1
  API version:      1.46 (minimum version 1.24)
  Go version:       go1.21.12
  Git commit:       cc13f95
  Built:            Tue Jul 23 19:57:14 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.19
  GitCommit:        2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
 runc:
  Version:          1.7.19
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

What happened?
RedpandaContainer.withListener accepts a Supplier<String> and parses it in order to create a Supplier<Listener> to be added to listenersValueSupplier, which is used later in configure and containerIsStarting.
The parsing is happening across three operations -

The string is split with the colon character into its two parts (host:port)
The port is converted into an int
A Listener object is constructed from the host and converted port

The problem is that the first operations happens outside of the Supplier lambda added to listenersValueSupplier, which effectively means the Supplier<String> passed to withListener isn't really lazy as it is meant to be.
Relevant log output
No response
Additional Information
A fix is available in https://github.com/testcontainers/testcontainers-java/pull/9173

Hi @YanivKunda, the ideal workflow would be to raise a issue or discussion, triage it and then raise the PR. Since the PR was raised first then there is no need to raise the issue later. I'm closing it in favor of #9173

Thanks @eddumelendez, please let me know if there are any clarifications or action items needed from me in #9173.

authors: YanivKunda eddumelendez


text:
Add custom LogMessageWaitStrategy startup timeout

For some long starting services like kafka+zookeper it could take more than 60 sec to start and configure. As currently there is no possibility to set it to some custom timeout I propose this change.

There exists a public withStartupTimeout in AbstractWaitStrategy. So I don't think there is a need for this ?

Yes, my bad. I missed that one, closing PR.

authors: jonasgeiregat vadymfutorianskyy


text:
migrate to latest react

Trying to provide overrides for certain components, but since the React version used in znai is pre-hook, override components can't use hooks

closed by #411

repo: testingisdocumenting/znai


text:
Update m12-circuit.adoc

Added Section 4 in line 2 for the issue #108

Not needed

repo: tetrabiodistributed/papra


text:
Support to select2 ajax

fix error

option 'ajax' is not allowed for Select2 when attached to a <select> element

Sorry, I don't understand this.
This shows ajax being used with a  https://select2.org/data-sources/ajax

I think is this an issue for versions of Select2 before version 4.
Thanks but I don't think I want to merge this. All the examples for Select2 v4 use . I think we might have to accept that we only support Select2 v4 moving forward.
https://select2.org/getting-started/basic-usage

This should definitely not be merged. It wouldn't only add compatibility issues, but even remove functionality.

I'm all for closing this. If anyone really needs to support select <4.0, they will simply have to extend the .select2entity() function themselves.

authors: DubbleClick morra850 tetranz