[ownership] Only allow BranchPropagatedUser to be constructed from Operands.

This commit only changes how BranchPropagatedUser is constructed and does not
change the internal representation. This is a result of my noticing that
BranchPropagatedUser could also use an operand internally to represent its
state. To simplify how I am making the change, I am splitting the change into
two PRs that should be easy to validate:

A commit that maps how the various users of BranchPropagatedUser have been
constructing BPUs to a single routine that takes an Operand. This leaves
BranchPropagatedUser's internal state alone as well as its user the Linear
Lifetime Checker.

A second commit that changes the internal bits of the BranchPropagatedUser to
store an Operand instead of a PointerUnion.

This will allow me to use the first commit to validate the second.

NOTE: I split off two small helper adding commits.

@swift-ci test

Once this is done, I am going to be able to introduce a new BorrowScopeIntroducingOperand higher level construct. This is going to let me change the place I marked with HERE, to use that to add support for checking an owned value being used in a guaranteed position of begin_apply as well as add support for adding in an implicit scope for mark_dependence and a new instruction called end_mark_dependence that I am going to add once this lands.

It should also let me add support pretty easily for adding ref_element_addr users to the verification here.

Also note, my hope is that this is a stepping stone to getting rid of BranchPropagatedUser (or at least hiding it).

Build failed
Swift Test Linux Platform
Git Sha - 12aa95ac1e101a0266d4bc887e6cd232878ee1b6

@swift-ci test linux platform

Seems fine. I don't think you need to put effort into getting rid of BranchPropagatedUser. The underlying problem goes away when cond_br args go away. I had a patch for that about a year ago but didn't get around to updating all the SIL tests. I really think I'll be able to revive that soon.

@atrick I am doing this for a bigger reason. I need this to add a BorrowScopeIntroducingOperand higher level construct.


TypeError, while creating timeseries windows for training and validation data in TFX

I'm using TensorFlow version: 2.3.1 and TFX version: 0.24.1.
I am developing machine learning workflow for timeseries using TFX. The ExampleGen, StatisticsGen, SchemaGen and Example validator and transform components worked fine. In the Trainer component, i used the tf.keras.preprocessing.timeseries_dataset_from_array API within the run_fn() of the Trainer component to generate the train and evaluation windows then i got a TypeError: dataset length is infinite.  Below is the modification i made to the run_fn() in the Trainer module file and the error message;
def run_fn(fn_args: TrainerFnArgs):
    """Train the model based on given args.

    Args:
    fn_args: Holds args used to train the model as name/value pairs.
    """
    # Number of nodes in the first layer of the DNN
    first_dnn_layer_size = 100
    num_dnn_layers = 4
    dnn_decay_factor = 0.7

    sequence_length = 144
    batch_size = 1

    tf_transform_output = tft.TFTransformOutput(fn_args.transform_output)

    train_dataset = _input_fn(fn_args.train_files, fn_args.data_accessor,
                            tf_transform_output, 40)

    # Generate timeseries sliding window for the training data
    train_dataset = tf.keras.preprocessing.timeseries_dataset_from_array(train_dataset, train_dataset, sequence_length=sequence_length , batch_size=batch_size)

    # Generate timeseries sliding window for the eval data
    eval_dataset = _input_fn(fn_args.eval_files, fn_args.data_accessor,
                           tf_transform_output, 40)
    eval_dataset = tf.keras.preprocessing.timeseries_dataset_from_array(eval_dataset, eval_dataset, sequence_length=sequence_length , batch_size=batch_size)

    model = _build_keras_model(
      # Construct layers sizes with exponetial decay
      hidden_units=[
          max(2, int(first_dnn_layer_size * dnn_decay_factor**i))
          for i in range(num_dnn_layers)
      ])

    tensorboard_callback = tf.keras.callbacks.TensorBoard(
      log_dir=fn_args.model_run_dir, update_freq='batch')
    model.fit(
      train_dataset,
      steps_per_epoch=fn_args.train_steps,
      validation_data=eval_dataset,
      validation_steps=fn_args.eval_steps,
      callbacks=[tensorboard_callback])

    signatures = {
      'serving_default':
          _get_serve_tf_examples_fn(model,
                                    tf_transform_output).get_concrete_function(
                                        tf.TensorSpec(
                                            shape=[None],
                                            dtype=tf.string,
                                            name='examples')),
    }

trainer = Trainer(
    module_file=os.path.abspath(trainer_module_file),
    custom_executor_spec=executor_spec.ExecutorClassSpec(GenericExecutor),
    examples=transform.outputs['transformed_examples'],
    transform_graph=transform.outputs['transform_graph'],
    schema=schema_gen.outputs['schema'],
    train_args=trainer_pb2.TrainArgs(num_steps=10000),
    eval_args=trainer_pb2.EvalArgs(num_steps=5000))
context.run(trainer)

Error message:
INFO:absl:Running driver for Trainer
INFO:absl:MetadataStore with DB connection initialized
INFO:absl:Running executor for Trainer
INFO:absl:Train on the 'train' split when train_args.splits is not set.
INFO:absl:Evaluate on the 'eval' split when eval_args.splits is not set.
INFO:absl:Training model.
INFO:absl:We decided to produce LargeList and LargeBinary types.
INFO:absl:Feature Appliances_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature Press_mm_hg_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_1_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_2_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_3_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_4_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_5_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_6_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_7_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_8_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_9_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature RH_out_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T1_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T2_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T3_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T4_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T5_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T6_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T7_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T8_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T9_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature T_out_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature Tdewpoint_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature Visibility_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature Windspeed_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature lights_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature rv1_xf has a shape . Setting to DenseTensor.
INFO:absl:Feature rv2_xf has a shape . Setting to DenseTensor.
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-21-cc5cfdc341eb> in <module>()
      7     train_args=trainer_pb2.TrainArgs(num_steps=10000),
      8     eval_args=trainer_pb2.EvalArgs(num_steps=5000))
----> 9 context.run(trainer)

7 frames
/usr/local/lib/python3.6/dist-packages/tensorflow/python/data/ops/dataset_ops.py in __len__(self)
    443     length = self.cardinality()
    444     if length.numpy() == INFINITE:
--> 445       raise TypeError("dataset length is infinite.")
    446     if length.numpy() == UNKNOWN:
    447       raise TypeError("dataset length is unknown.")
TypeError: dataset length is infinite.

Are you using Tensorflow addons features?


[WIP] Added the batch endpoint

Hey there!
I've created and somehow tested the batch endpoint, but I'm not familiar with the test system you use in this project, could you please help me to add some?

Hi, thanks for the contribution!
At the moment, there are two types of tests:

Unit tests of the client and models (tests/test_client.py and tests/test_models.py)
Integration tests of the LivySession helper (tests/test_integration.py)

Tests are run using pytest -- you might want to take a look at some minimal examples in their documentation first. I suggest running the tests with tox, which will install additional dependencies required:
tox -e py36

Replace py36 with py37 to run on Python 3.7 instead of Python 3.6.
By default, this will not run the integration tests, as they are slower and require a running Livy server to test against. To run integration tests, you can run a Livy server with Docker:
docker run --publish 8998:8998 acroz/livy

Then, in a separate shell, run the integration tests with:
tox -e py36-integration

You can also run linting checks and type checks with the following:
tox -e flake8
tox -e black
tox -e mypy

Adding tests
I suggest starting with a test for the new Batch model you've added, in particular testing its from_json method in a similar way to the existing tests in tests/test_models.py.
After that, I'd suggest adding tests to tests/test_client.py to test the methods you've added to LivyClient. Those tests use the requests_mock to mock out the actual HTTP calls so it's possible to test the client logic without an actual livy server running. These tests also mock out the from_json (e.g. mocker.patch.object(Statement, "from_json")) and assert they got passed the right things rather than implicitly test that logic a second time in the client tests.
Finally, adding integration tests for the LivyBatch object you've added would be strongly valuable. As you can see from tests/test_integration.py, these tests run the code against an actual livy server in a realistic-ish setting. The batch tests should be simpler than the session ones, as you don't have all the dataframe export logic to test, but it would be good to see a test that causes some code to be run on the server side, and some expected output appear in the logs.

Oh, and can you also please add yourself to the AUTHORS file?

Thank you for describing that thoroughly, fix will take some time.

@acroz , When will the Batches endpoint be merged in ? Our requirement currently needs to use batches endpoint. Thanks!

@dineshdharme Hi, that's my bad. I've got no time to finish the tests yet.
If you can finish them your help will be very appreciated

@acroz, could you please rebuild the docker image acroz/livy so that I could finish the integration tests?
https://issues.apache.org/jira/browse/SPARK-21917 blocks me from that now.

@JustEdro You can use the following docker file to create Livy+Spark image for testing:
FROM debian:stretch
MAINTAINER Ketan Goyal

RUN apt-get update \
 && apt-get install -y locales \
 && dpkg-reconfigure -f noninteractive locales \
 && locale-gen C.UTF-8 \
 && /usr/sbin/update-locale LANG=C.UTF-8 \
 && echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen \
 && locale-gen \
 && apt-get clean \
 && rm -rf /var/lib/apt/lists/*

# Users with other locales should set this in their derivative image
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8

RUN apt-get update \
 && apt-get install -y curl unzip \
    python3 python3-setuptools \
 && ln -s /usr/bin/python3 /usr/bin/python \
 && easy_install3 pip py4j \
 && apt-get clean \
 && rm -rf /var/lib/apt/lists/*

# http://blog.stuart.axelbrooke.com/python-3-on-spark-return-of-the-pythonhashseed
ENV PYTHONHASHSEED 0
ENV PYTHONIOENCODING UTF-8
ENV PIP_DISABLE_PIP_VERSION_CHECK 1

# JAVA
RUN apt-get update \
 && apt-get install -y openjdk-8-jre \
 && apt-get clean \
 && rm -rf /var/lib/apt/lists/*

# HADOOP
ENV HADOOP_VERSION 3.0.0
ENV HADOOP_HOME /usr/hadoop-$HADOOP_VERSION
ENV HADOOP_CONF_DIR=$HADOOP_HOME/etc/hadoop
ENV PATH $PATH:$HADOOP_HOME/bin
RUN curl -sL --retry 3 \
  "http://archive.apache.org/dist/hadoop/common/hadoop-$HADOOP_VERSION/hadoop-$HADOOP_VERSION.tar.gz" \
  | gunzip \
  | tar -x -C /usr/ \
 && rm -rf $HADOOP_HOME/share/doc \
 && chown -R root:root $HADOOP_HOME

# SPARK
ENV SPARK_VERSION 2.4.1
ENV SPARK_PACKAGE spark-${SPARK_VERSION}-bin-without-hadoop
ENV SPARK_HOME /usr/spark-${SPARK_VERSION}
ENV SPARK_DIST_CLASSPATH="$HADOOP_HOME/etc/hadoop/*:$HADOOP_HOME/share/hadoop/common/lib/*:$HADOOP_HOME/share/hadoop/common/*:$HADOOP_HOME/share/hadoop/hdfs/*:$HADOOP_HOME/share/hadoop/hdfs/lib/*:$HADOOP_HOME/share/hadoop/hdfs/*:$HADOOP_HOME/share/hadoop/yarn/lib/*:$HADOOP_HOME/share/hadoop/yarn/*:$HADOOP_HOME/share/hadoop/mapreduce/lib/*:$HADOOP_HOME/share/hadoop/mapreduce/*:$HADOOP_HOME/share/hadoop/tools/lib/*"
ENV PATH $PATH:${SPARK_HOME}/bin
RUN curl -sL --retry 3 \
  "https://archive.apache.org/dist/spark/spark-${SPARK_VERSION}/${SPARK_PACKAGE}.tgz" \
  | gunzip \
  | tar x -C /usr/ \
 && mv /usr/$SPARK_PACKAGE $SPARK_HOME \
 && chown -R root:root $SPARK_HOME

# Livy
ENV LIVY_VERSION 0.7.0
ENV LIVY_PACKAGE apache-livy-${LIVY_VERSION}-incubating-bin
ENV LIVY_HOME /usr/livy-${LIVY_VERSION}
ENV PATH $PATH:${LIVY_HOME}/bin
RUN apt-get update \
 && apt-get install -y procps
RUN curl -sL --retry 3 \
  "http://mirror.cogentco.com/pub/apache/incubator/livy/${LIVY_VERSION}-incubating/${LIVY_PACKAGE}.zip" > ${LIVY_PACKAGE}.zip \
  && unzip -d /usr/ ${LIVY_PACKAGE}.zip \
  && rm ${LIVY_PACKAGE}.zip \
  && mv /usr/$LIVY_PACKAGE $LIVY_HOME \
  && mkdir ${LIVY_HOME}/logs \
  && chown -R root:root $LIVY_HOME

CMD ["livy-server"]

I have a need for the batches API and am really looking forward to this pull request being merged.
Hope that helps!

@ketgo, when running tests against your Docker setup, things run fine on Scala and R, but I'm having issues with PySpark. Specifically, I get the following error, which causes the session to crash:
Exception in thread "Thread-25" java.lang.NoClassDefFoundError: org/apache/spark/sql/hive/HiveContext

Is this something you've encountered? I'm able to run and use the PySpark shell directly by shelling into the running container without issues.

Hi @acroz, I have not run into this issue before. Can you point to the test or code for which you are observing the error. I would like to reproduce it for debugging.
My initial guess would be it seems that some of the hive libs are missing or there is a version mismatch.

Hey @JustEdro - I finally managed to muster the motivation to fix the integration tests. There was some hairy stuff going on with the Python interpreter failing as a particular Java class was not available.
Anyway, I've merged the latest master with fixed tests on to your branch! Can I help at all to fix any of the issues revealed?

Hi @acroz, sorry for the belated reply
I've run the tests on the updated Docker image, and everything works like a charm.
The endpoint itself works well, so I think these changes are ready to be merged to master if you don't mind.

@ketgo, when running tests against your Docker setup, things run fine on Scala and R, but I'm having issues with PySpark. Specifically, I get the following error, which causes the session to crash:
Exception in thread "Thread-25" java.lang.NoClassDefFoundError: org/apache/spark/sql/hive/HiveContext

Is this something you've encountered? I'm able to run and use the PySpark shell directly by shelling into the running container without issues.

@ketgo, when running tests against your Docker setup, things run fine on Scala and R, but I'm having issues with PySpark. Specifically, I get the following error, which causes the session to crash:
Exception in thread "Thread-25" java.lang.NoClassDefFoundError: org/apache/spark/sql/hive/HiveContext

Is this something you've encountered? I'm able to run and use the PySpark shell directly by shelling into the running container without issues.

Hi @acroz,
I encounter the same thing as you. It throws me the same exception when I post single statements when I used the same Dockerfile provided by @ketgo above. How did you solve this?
Help would be much appreciated!

Hi @jespercedergren, I added a command to the Dockerfile to install
spark-hive, which provides the missing dependency. You can see it here:
https://github.com/acroz/pylivy-test-server/blob/17d690bf0d1dacafb1a9413e49ccdedef190a07a/Dockerfile#L63-L66
Hope this helps!
On Tue, 19 May 2020 at 18:03, jespercedergren<EMAIL_ADDRESS>wrote:

@ketgo https://github.com/ketgo, when running tests against your Docker
setup, things run fine on Scala and R, but I'm having issues with PySpark.
Specifically, I get the following error, which causes the session to crash:
Exception in thread "Thread-25" java.lang.NoClassDefFoundError: org/apache/spark/sql/hive/HiveContext
Is this something you've encountered? I'm able to run and use the PySpark
shell directly by shelling into the running container without issues.
@ketgo https://github.com/ketgo, when running tests against your Docker
setup, things run fine on Scala and R, but I'm having issues with PySpark.
Specifically, I get the following error, which causes the session to crash:
Exception in thread "Thread-25" java.lang.NoClassDefFoundError: org/apache/spark/sql/hive/HiveContext
Is this something you've encountered? I'm able to run and use the PySpark
shell directly by shelling into the running container without issues.
Hi @acroz https://github.com/acroz,
I encounter the same thing as you. It throws me the same exception when I
post single statements when I used the same Dockerfile provided by @ketgo
https://github.com/ketgo above. How did you solve this?
Help would be much appreciated!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/acroz/pylivy/pull/60#issuecomment-630953244, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMCZPUHREHEOG3ZRT3ZAPDRSK3XZANCNFSM4H66NQ7A
.

Thanks @acroz for you quick response!


Details button in Data table not working

Sorry I missed before, not positive when this stopped working— possibly when we moved when we re-routed Details— but clicking on the old Details icon second from left for any record in Data doesn't seem to do anything now

Can close/delete if this is the same as #248!

'tis!


Kulfy: Watch freefireforpcwindows.com

Kulfy requests the watch of the watch_keyword freefireforpcwindows\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

freefireforpcwindows\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ

Unclear why this was originally watched, but the watch was useful now; https://metasmoke.erwaysoftware.com/post/307474


URLs ($id field) returning 404 (not found)

Hi, the URLs ($id field) for the schemas https://github.com/peiffer-innovations/json_dynamic_widget/blob/main/lib/src/schema/schemas/measured_schema.dart and https://github.com/peiffer-innovations/json_dynamic_widget/blob/main/lib/src/schema/schemas/layout_builder_schema.dart are returning 404 (the other schemas are working).
Thanks for this project, it's awesome o/

Yep, seems I missed those.  The release posted a few minutes ago fixes them.  Thanks for letting me know.

Thanks!


Add Python 3.9 support

Pull Request Checklist
Thank you for taking the time to improve Arrow! Before submitting your pull request, please check all appropriate boxes:

[x] 🧪 Added tests for changed code.
[x] 🛠 All tests pass when run locally (run tox or make test to find out!).
[x] 🧹 All linting checks pass when run locally (run tox -e lint or make lint to find out!).
[x] 📚 Updated documentation for changed code.
[x] ⏩ Code is up-to-date with the master branch.

If you have any questions about your code changes or any of the points above, please submit your questions along with the pull request and we will try our best to help!
Description of Changes

Codecov Report

Merging #801 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #801   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           10        10
  Lines         1713      1698   -15
  Branches       295       295
=========================================
- Hits          1713      1698   -15

Impacted Files
Coverage Δ

arrow/arrow.py
100.00% <0.00%> (ø)

arrow/parser.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

@jadchaar looks solid man, kinda lame that GH actions doesn't support 3.9 yet but also funny that Travis is bailing us out here.
Speaking of which has Travis CI run on this PR, I don't see it?

I don't know why GH is not showing it. It might that GH prioritizes GH Actions now over Travis, which would be kind of funny if true.
Here is the run: https://travis-ci.org/github/crsmithdev/arrow/builds/695468398. I had to find it by manually going to https://travis-ci.org/github/crsmithdev/arrow/.
GH Actions is still developing and expanding, so hopefully we will see this dev/nightly support before 3.10 :).


Reduce log level, no connection is normal in some cases

When is this normal ? It has not been able to get contact for quite some time.
I think that there should be some traces of that.
An improvement would be to have it edge triggered. First time, and then silence util good again.

the config agent also logs about this, with a more informative message

K, then we are good.


Limit the usage of token networks

Description
We need to have the possibility to limit the token networks the user can choose.
Acceptance criteria

Tasks

[ ]

@christianbrb Is that practical? currently you can limit the token networks on the SC level. If you don't limit them in the SC then anyone can register a token and deploy their own tokens. I don't see how we could potentially limit the tokens on the light client or how this would be practical. Do you have any specific scenario/use case/example that would help understand what you mean?

I agree with Kelsos. Our source of truth is the blockchain, if somewhere, the limits should be there, the dApp/SDK/light-client is an interface for it and should reflect what's registered there.

@kelsos @andrevmatos Sounds reasonable. Closing :)


Upgrade to Node 16 and add outputs

Github Actions is deprecating Node 12.
Added the following outputs:

found-artifact: boolean
path : string

@jgillick thanks for submit PR - I will review and come to you with update. BTW. sorry for so late response 🙏🏻

Github is now deprecating node16 and using node20

If anybody else want to use this before the PR is merged, you can update your YML files to use jgillick/actions-download-artifact@master


Failed to add reference

Install-Package : Failed to add reference. The package 'SuaveControls.FloatingActionButton' tried to add a framework reference to 'System.Runtime' which was not found in the GAC. This is possibly a bug in the package. Please contact the package owners for assistance.
Error HRESULT E_FAIL has been returned from a call to a COM component.
trying to install with Xamarin Forms <IP_ADDRESS>2 and Xamarin.Android.Support 25.3.1.

SuaveControls.FloatingActionButton.2018.1.5
Att,
Altevir Cardoso Neto
<EMAIL_ADDRESS>TIM: (45) 9988-0515
Skype: altevir.cardoso
Linkedin: br.linkedin.com/pub/altevir-cardoso-neto/32/b84/178
2018-04-05 14:22 GMT-03:00 Alex Dunn<EMAIL_ADDRESS>
Which version of the package
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SuavePirate/Xamarin.Forms.Controls.FloatingActionButton/issues/19#issuecomment-379012535,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQZ46-zzBVBSbnGiYZfLI9Lpu-yY9afks5tllLjgaJpZM4TDCi0
.

What kind of project were you trying to add it to?

Same problem, I'm trying to use it in PCL with android and ios

I think this is part of the consequences I've mentioned in a few other places with the .netstandard changes and the fact that the .nuproj builds add all the dependent system dlls to the nuget package for no apparent reason.

Same problem, on androic and PCL projct
Severity	Code	Description	Project	File	Line	Suppression State
Error		Failed to add reference. The package 'SuaveControls.FloatingActionButton' tried to add a framework reference to 'System.Runtime' which was not found in the GAC. This is possibly a bug in the package. Please contact the package owners for assistance.
Reference unavailable.

Any solution to this problem?


Update dependencies in Gradle

Many dependencies are very outdated at this point.
We should update them to the most recent or more recent versions (if needed due to compatibility).
e.g. Mockserver-netty always throws an exception whilst running JUnit tests.
This is fixed in newer versions.
@Acconut do we want to stay at JUnit 4 or do we want to upgrade to JUnit 5?
Maybe we have to find out how much this would hurt first.

Maybe let's do:

uprade of okhttp
maybe use okhttp mockserver instead of mockserver-netty
upgrade JSON Builder
upgrade Joda Time


Allow generateNodeNames to handle names containing regex control chars

Fixes #3813
Handles names that contain things like + by escaping them.

Coverage remained the same at 68.199% when pulling d8e350d60394046d5a4accb095450f4b4ff047e7 on fix-regex-name-handle into dc7fef63952548277d7759c327ce2909fdce0a3c on master.


add configs for block fp8 related kernels

Motivation
tune by @HandH1998 I help verify.

Modifications

Checklist

[ ] Format your code according to the Contributor Guide.
[ ] Add unit tests as outlined in the Contributor Guide.
[ ] Update documentation as needed, including docstrings or example tutorials.

All checks have passed

cc @BBuf


readme snippet tool needs cushion between tags and python snippets for github.io

A sample without a newline between the tags and the python snippet:

will render like this in the github.io docs:

FYI @xiangyan99

Form Recognizer snippets are also looking like that ^


feat: refactor the node key as version + local nonce(seq id)

benchmark results between path and local nonce
name                                                                 old time/op    new time/op    delta
Large/memdb-1000000-100-16-40/query-no-in-tree-guarantee-fast-6        3.49µs ± 3%    3.27µs ± 3%   -6.51%  (p=0.000 n=16+18)
Large/memdb-1000000-100-16-40/query-no-in-tree-guarantee-slow-6        17.4µs ±11%    12.9µs ± 7%  -26.14%  (p=0.000 n=17+18)
Large/memdb-1000000-100-16-40/query-hits-fast-6                        4.35µs ± 4%    4.03µs ± 9%   -7.45%  (p=0.000 n=18+20)
Large/memdb-1000000-100-16-40/query-hits-slow-6                        21.8µs ± 8%    16.1µs ± 7%  -26.00%  (p=0.000 n=18+19)
Large/memdb-1000000-100-16-40/iteration-fast-6                          591ms ± 5%     544ms ± 4%   -7.94%  (p=0.000 n=20+20)
Large/memdb-1000000-100-16-40/iteration-slow-6                          9.07s ± 2%     6.67s ± 2%  -26.43%  (p=0.000 n=16+19)
Large/memdb-1000000-100-16-40/update-6                                  218µs ±15%     174µs ± 6%  -19.85%  (p=0.000 n=19+19)
Large/memdb-1000000-100-16-40/block-6                                  23.9ms ± 4%    19.7ms ± 5%  -17.58%  (p=0.000 n=18+19)
Large/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-fast-6    9.49µs ± 5%    9.38µs ± 3%     ~     (p=0.086 n=19+19)
Large/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-slow-6    25.8µs ±35%    21.8µs ±23%  -15.53%  (p=0.000 n=18+19)
Large/goleveldb-1000000-100-16-40/query-hits-fast-6                    9.67µs ± 3%   10.05µs ± 4%   +3.94%  (p=0.000 n=20+20)
Large/goleveldb-1000000-100-16-40/query-hits-slow-6                    32.0µs ± 4%    27.3µs ±10%  -14.54%  (p=0.000 n=20+20)
Large/goleveldb-1000000-100-16-40/iteration-fast-6                      1.28s ± 2%     1.30s ± 6%     ~     (p=0.429 n=20+20)
Large/goleveldb-1000000-100-16-40/iteration-slow-6                      24.2s ± 2%     15.9s ± 4%  -34.35%  (p=0.000 n=18+19)
Large/goleveldb-1000000-100-16-40/update-6                              343µs ±21%     298µs ±17%  -13.16%  (p=0.000 n=19+19)
Large/goleveldb-1000000-100-16-40/block-6                              38.1ms ±11%    34.2ms ±17%  -10.21%  (p=0.000 n=19+20)

name                                                                 old alloc/op   new alloc/op   delta
Large/memdb-1000000-100-16-40/query-no-in-tree-guarantee-fast-6         88.0B ± 0%     88.0B ± 0%     ~     (all equal)
Large/memdb-1000000-100-16-40/query-no-in-tree-guarantee-slow-6        1.07kB ±10%    0.85kB ± 0%  -20.61%  (p=0.000 n=16+16)
Large/memdb-1000000-100-16-40/query-hits-fast-6                          210B ± 2%      210B ± 2%     ~     (p=0.978 n=16+16)
Large/memdb-1000000-100-16-40/query-hits-slow-6                        1.31kB ± 0%    1.08kB ± 0%  -17.75%  (p=0.000 n=17+20)
Large/memdb-1000000-100-16-40/iteration-fast-6                          232MB ± 0%     232MB ± 0%   -0.00%  (p=0.037 n=20+17)
Large/memdb-1000000-100-16-40/iteration-slow-6                         1.22GB ± 0%    1.10GB ± 0%  -10.50%  (p=0.000 n=18+18)
Large/memdb-1000000-100-16-40/update-6                                 26.4kB ± 1%    24.1kB ± 1%   -8.71%  (p=0.000 n=19+18)
Large/memdb-1000000-100-16-40/block-6                                  2.78MB ± 0%    2.55MB ± 1%   -8.37%  (p=0.000 n=19+20)
Large/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-fast-6      993B ± 0%      996B ± 1%   +0.27%  (p=0.000 n=19+20)
Large/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-slow-6    2.63kB ±61%    2.23kB ±14%  -15.15%  (p=0.000 n=18+17)
Large/goleveldb-1000000-100-16-40/query-hits-fast-6                    1.03kB ± 1%    1.03kB ± 1%     ~     (p=0.770 n=18+18)
Large/goleveldb-1000000-100-16-40/query-hits-slow-6                    3.12kB ± 1%    3.00kB ± 1%   -3.97%  (p=0.000 n=19+20)
Large/goleveldb-1000000-100-16-40/iteration-fast-6                      298MB ± 0%     298MB ± 0%   +0.07%  (p=0.000 n=19+18)
Large/goleveldb-1000000-100-16-40/iteration-slow-6                     3.44GB ± 0%    2.53GB ± 0%  -26.46%  (p=0.000 n=18+18)
Large/goleveldb-1000000-100-16-40/update-6                             51.9kB ±10%    47.4kB ±10%   -8.63%  (p=0.000 n=19+19)
Large/goleveldb-1000000-100-16-40/block-6                              6.42MB ± 7%    5.50MB ±12%  -14.33%  (p=0.000 n=20+20)

name                                                                 old allocs/op  new allocs/op  delta
Large/memdb-1000000-100-16-40/query-no-in-tree-guarantee-fast-6          3.00 ± 0%      3.00 ± 0%     ~     (all equal)
Large/memdb-1000000-100-16-40/query-no-in-tree-guarantee-slow-6          58.4 ± 6%      36.0 ± 0%  -38.33%  (p=0.000 n=16+16)
Large/memdb-1000000-100-16-40/query-hits-fast-6                          4.00 ± 0%      4.00 ± 0%     ~     (all equal)
Large/memdb-1000000-100-16-40/query-hits-slow-6                          65.5 ± 1%      43.0 ± 0%  -34.35%  (p=0.000 n=20+20)
Large/memdb-1000000-100-16-40/iteration-fast-6                          4.00M ± 0%     4.00M ± 0%     ~     (p=0.307 n=19+20)
Large/memdb-1000000-100-16-40/iteration-slow-6                          39.1M ± 0%     33.0M ± 0%  -15.53%  (p=0.000 n=18+18)
Large/memdb-1000000-100-16-40/update-6                                    711 ± 1%       554 ± 1%  -22.05%  (p=0.000 n=19+15)
Large/memdb-1000000-100-16-40/block-6                                   73.6k ± 1%     57.4k ± 1%  -22.03%  (p=0.000 n=20+20)
Large/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-fast-6      19.0 ± 0%      19.0 ± 0%     ~     (all equal)
Large/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-slow-6      81.7 ±37%      51.9 ±12%  -36.47%  (p=0.000 n=18+17)
Large/goleveldb-1000000-100-16-40/query-hits-fast-6                      19.0 ± 0%      19.0 ± 0%     ~     (all equal)
Large/goleveldb-1000000-100-16-40/query-hits-slow-6                      90.5 ± 1%      64.0 ± 0%  -29.28%  (p=0.000 n=20+16)
Large/goleveldb-1000000-100-16-40/iteration-fast-6                      5.31M ± 0%     5.31M ± 0%   +0.00%  (p=0.000 n=19+19)
Large/goleveldb-1000000-100-16-40/iteration-slow-6                      70.5M ± 0%     57.2M ± 0%  -18.89%  (p=0.000 n=18+18)
Large/goleveldb-1000000-100-16-40/update-6                                939 ± 4%       775 ± 5%  -17.52%  (p=0.000 n=18+19)
Large/goleveldb-1000000-100-16-40/block-6                                100k ± 4%       83k ± 8%  -16.54%  (p=0.000 n=19+20)

👍 I like it, the only issue is how to efficiently assign nonce by version during import.
I guess int16 array with a map to handle overflows would be more memory efficient.

Cool that local_version + nonce is faster on all metrics!

👍 I like it, the only issue is how to efficiently assign nonce by version during import. I guess int16 array with another map to handle overflows would be more memory efficient. Another idea to reduce memory usage is, we don't have to track nonce for each version strictly, we can do that for a version range, that'll greatly reduce the array size.

the idea of version range is interesting, is there a way to know about the approx count of leaves in one block?

can you update the docs associated with this change, also the orphan docs need updating

This maybe out of scope for this PR but I think we should change the key format for leaf nodes to be version | l | key where key is the value's key. Doing so, we can fetch key/value fair from iavl.Store and iterate without tree traversal.

Shouldn't hardware prefetching mostly eliminate that as a time overhead?

This maybe out of scope for this PR but I think we should change the key format for leaf nodes to be version | l | key where key is the value's key. Doing so, we can fetch key/value fair from iavl.Store and iterate iavl.Store without tree traversal.

This may not serve what you want because you don't know what exact version the key is modified, unless also maintain some other indexes.

This maybe out of scope for this PR but I think we should change the key format for leaf nodes to be version | l | key where key is the value's key. Doing so, we can fetch key/value fair from iavl.Store and iterate iavl.Store without tree traversal.

Shouldn't hardware prefetching mostly eliminate the tree traversal as a time overhead?

Tree nodes are scattered at different versions, prefetching don't help much I think.

This maybe out of scope for this PR but I think we should change the key format for leaf nodes to be version | l | key where key is the value's key. Doing so, we can fetch key/value fair from iavl.Store and iterate iavl.Store without tree traversal.

Sounds like a very clever idea, but this may not serve what you want because you don't know what exact version the key is modified, unless also maintain some other indexes.

But we always know the version since when we load iavl.Store, we always specify the version

That is the version you want to query in, not the version the key is last modified, the version contained in the node is the version the node is created in, aka. when the key is modified or inserted.

This maybe out of scope for this PR but I think we should change the key format for leaf nodes to be version | l | key where key is the value's key. Doing so, we can fetch key/value fair from iavl.Store and iterate iavl.Store without tree traversal.

Sounds like a very clever idea, but this may not serve what you want because you don't know what exact version the key is modified, unless also maintain some other indexes.

But we always know the version since when we load iavl.Store, we always specify the version

@yihuang is right, we have different versions, how is key-iteration query possible? since the version prefix is different

Here is the rocksDB benchmarking result, there is not much improvement in RocksDB
iavl: 0.20.0-alpha1-23-gde1532f goos: linux goarch: amd64 pkg: github.com/cosmos/iavl/benchmarks cpu: DO-Premium-Intel                                                                      │   old.txt          │   new.txt    │                                                                          │    sec/op          │    sec/op    │  Larger/memdb-1000000-100-16-40/query-no-in-tree-guarantee-fast-4       3.818µ ±  3%         4.010µ ±  3%  Larger/memdb-1000000-100-16-40/query-no-in-tree-guarantee-slow-4       20.66µ ±  6%         18.34µ ±  5%  Larger/memdb-1000000-100-16-40/query-hits-fast-4                       5.650µ ±  7%         5.913µ ±  4%  Larger/memdb-1000000-100-16-40/query-hits-slow-4                       25.17µ ±  8%         22.22µ ±  2%  Larger/memdb-1000000-100-16-40/iteration-fast-4                        592.3m ±  3%         553.8m ±  5%  Larger/memdb-1000000-100-16-40/iteration-slow-4                         12.78 ±  4%          6.023 ±  2% Larger/memdb-1000000-100-16-40/update-4                                317.9µ ±  5%         212.5µ ± 10% Larger/memdb-1000000-100-16-40/block-4                                 34.30m ±  6%         24.11m ±  3% Larger/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-fast-4   4.123µ ±  7%         4.169µ ±  2% Larger/goleveldb-1000000-100-16-40/query-no-in-tree-guarantee-slow-4   32.94µ ± 12%         26.92µ ±  6% Larger/goleveldb-1000000-100-16-40/query-hits-fast-4                   12.36µ ±  3%         12.22µ ±  4% Larger/goleveldb-1000000-100-16-40/query-hits-slow-4                   41.00µ ±  5%         33.70µ ±  4% Larger/goleveldb-1000000-100-16-40/iteration-fast-4                    780.4m ±  3%         819.9m ± 10% Larger/goleveldb-1000000-100-16-40/iteration-slow-4                     30.43 ±  3%          13.92 ±  2% Larger/goleveldb-1000000-100-16-40/update-4                            373.6µ ±  9%         276.1µ ± 10% Larger/goleveldb-1000000-100-16-40/block-4                             50.60m ±  3%         35.58m ±  5% Larger/rocksdb-1000000-100-16-40/query-no-in-tree-guarantee-fast-4     6.655µ ±  6%         6.695µ ±  8% Larger/rocksdb-1000000-100-16-40/query-no-in-tree-guarantee-slow-4     22.06µ ±  9%         25.07µ ±  7% Larger/rocksdb-1000000-100-16-40/query-hits-fast-4                     8.097µ ±  4%         8.287µ ±  3% Larger/rocksdb-1000000-100-16-40/query-hits-slow-4                     29.97µ ±  4%         28.99µ ±  4% Larger/rocksdb-1000000-100-16-40/iteration-fast-4                       4.352 ±  2%          4.359 ±  3% Larger/rocksdb-1000000-100-16-40/iteration-slow-4                       16.81 ±  2%          15.28 ±  2% Larger/rocksdb-1000000-100-16-40/update-4                              436.1µ ± 10%         281.0µ ± 10% Larger/rocksdb-1000000-100-16-40/block-4                               45.70m ±  6%         32.38m ±  4% geomean                                                                1.356m               1.135m

:tada:


Added Python < 3.5 compatible Fraction object with _normalize

This is to accommodate the _normalize parameter in fractions.Fraction from Python >= 3.5 and the compatible Fraction from nltk.compat.Fraction allows _normalize by overloading the fraction.Fraction from Python < 3.5.
This PR:

Added a new Fraction object in nltk.compat to use the _normalize parameter for Python < 3.5
Re-added the _normalize=False code in nltk.translate.bleu_score.py from #1319
Added test cases for the new nltk.compat.Fraction object and also fringe cases of BLEU scores.

@stevenbird This PR should resolve the #1319 and also re-patch the Fractions with _normalize=False and allow all Python versions to use Fraction  with _normalize parameters =)
I'll continue to handle the fringe BLEU situations and modify the code to emulate mteval-13a.pl after this is merged.

Thanks @alvations, sorry for being slow to review this


Fix re render bug when using ResponsiveDataTable

Notes for Reviewers
This PR fixes #521
Issue was
The issue was that the useEffect hook was directly dependent on columns and updateCols, causing unnecessary re-renders. This occurred because columns and updateCols were passed as dependencies but were not used within the effect.
What are the changes

Applied useCallback: We applied the useCallback hook to the updateColumnsEffect function. This memoizes the function and prevents unnecessary re-renders when its dependencies (columnVisibility and updateCols) change.

Removed Dependencies: We removed columns and updateCols from the dependency array of updateColumnsEffect. This prevents re-renders caused by changes in these dependencies, as they are not directly used within the function.

Optimized useEffect: We updated the useEffect hook to only depend on updateColumnsEffect. This ensures that the effect runs whenever updateColumnsEffect changes, effectively triggering the updates related to column visibility.

[!NOTE]
This table will be using the  standard pagination

Signed commits

[x] Yes, I signed my commits.

@nebula-aac will you help in testing this and if its the issue then we can move forward

Likely came from this commit. https://github.com/layer5io/sistent/commit/b8b1d30972975e80450fb26a2cfc8266507824e1#diff-a318854e14bd1a20ebfda1c84a3b949f8809c9a49c7787a61b448cc8a4d37ff8L117

yes @theBeginner86 you got it right that commit is the issue which was giving the re rendering bug. Thanks for that.
Though this pr resolves this issue anyhow by removing that from dependency array and wrap in callback .

can we move forward here @nebula-aac


Histogram panel update

Updates the histogram panel to only render on field (histogram) at a time to improve performance.
Nominal e2e tests have been added to assert the plot renders on panel open and change and that a correct list of fields are shown in the plot selector. Better coverage for field selection can be handled in unit tests in the future.

Undrafted

lgtm with the new commits, just waiting for e2e tests to pass

Working on adding linux screenshots right now. Some other tests seem to be failing as well


Need the new "unreachable" field to be supported by BigQuery::listDatasets API

We are facing the same problem as issue googleapis/google-api-ruby-client#16987.
We need java API support for the new "unreachable" property in the BigQuery::listDatasets API response.
This is urgent, as this change will take place starting on Feb 15th, as announced by Google.

FYI, we're currently discussing how to approach this internally.
I'll post if there are any updates (ETA Feb [12, 13, 14] 2024).

Thanks @PhongChuong .
Given we're getting an answer (and probably not a release) the earliest by Feb 12th, would it be possible for you to contact the BigQuery team and hold off this change while the community has time to adapt their software? The fact we're the only ones who submitted an issue shows a lot of lack of unawareness about the topic in general and certainly users won't upgrade timely and handle the new API results.

Hi,
Sorry for the delay. We're still in discussion on how to forward the unreachable information to the users in a manageable manner.
I can pass the information to the BigQuery team to hold off this change. However, can you help me understand why that is needed?
In particular, what is concern regarding enabling the feature.

@PhongChuong , sorry for the delay as I was on vacation.
As stated by Google itself in the announcement sent to users:

"Today, in the uncommon case of one or more GCP regions being unreachable for a prolonged amount of time, datasets.list and jobs.list API calls will fail if the response should contain data from the unreachable region.
Starting February 15, 2024, these calls will succeed, with the additional field unreachable added to mark the locations in which data might have been skipped from dataset.list and jobs.list response in case of a prolonged unreachability of the entire region or multi-region.
Under normal circumstances, the field will be empty. However, if you rely on getting a full list of all your datasets and jobs from dataset.list and jobs.list API, you should start interpreting values of the new field if present."

Our use case - and most users, I guess - depends on this call being 100% reliable, i.e., either failing with an exception or returning all the datasets. Now an empty return in a region might mean "temporarily off" or no "datasets at all", which completely break the API.
As suggested by Google itself:

"Check the content of this field to see if there are any unreachable locations. If your API integration with BigQuery depends on getting a full list of datasets/jobs from all regions/multi-regions for which relevant data exists, make sure to adjust it depending on specific circumstances.
You may choose to fail the workflow, issue a warning, or continue without warning in case an unreachable field is populated."

We must fail the workflow given our use case - and I guess that's what most users want to do -, but currently there is no way to find out the empty response is due to an unreachable location and to do so.

@sjmisterm, thanks for the context.
We'll add the unreachable field to this library. I'll update with an ETA soon.

Hi @PhongChuong ,
It's been a while since the last message. Is there an ETA already?

Sorry for the delay. We're still trying to find staffing to work on this issue. I'll update as soon as we have a clear ETA.

Hi @PhongChuong . It's been over 3 months since this change has been deployed and any partial results delivered by the API are wrongly assumed to be the whole data by all Java clients.
I understand you're not the one to blame, but this can potentially cause us a major problem at any time. Does Google really intend to fix this API issue or to revert this backend change?

Hi @PhongChuong . Just pinging you again since it's been over three months from your last message and my previous one was ignored. Any news?

Hi, @sjmisterm ,
Sorry. I should have been more on top of this issue and keep everyone posted.
Unfortunately, my original proposal for Unreachable field fell through. The issue is that listDatasets and listJobs returns Page of dataset, job respectively which requires a longer term solution to how we handle additional fields in a paginated resource.
I'll bring this issue up again to see if we can raise the priority.
Meanwhile, if you have a support contract with Google, please create this issue in the support console will help us prioritize the effort.


Switch from request to axios

Addresses #19

Although.. it would nice to add tests that ensure that the error paths include both HTTP (404) and network (ENOTFOUND) errors.

I added a few more tests, and better defensive code around the err object that comes back.  Thanks!


Update registry-consistency-ci.yml for Julia 1.11

Add 1.11 to registry consistency check

How does one mark 1.11 to be Required like the others?

How does one mark 1.11 to be Required like the others?

That's a setting in the branch protection rules of the master branch.

Would it be ok to remove some of the older ones (like pre 1.6) to save CI time?

How about we keep 1.3, but we drop 1.4 and 1.5? That way, the only bugs we miss would be bugs introduced in 1.4 but fixed by 1.6.

Seems reasonable.

I wonder if we can also get rid of a few other versions like 1.7 and 1.8. Or would that be too aggressive?


New tab homepage: disabled in Settings, but still shows

Describe the bug
I disabled homepage in Settings, but still shows on new tabs
To Reproduce
Settings > Homepage > Off
New tab
Shows 2 rows of links to Facebook, Amazon, Yahoo... and "Discover" news
Expected behavior
New tab should show a blank page
Smartphone (please complete the following information):

Device: Xiaomi Mi Lite 11 5g
Android Version :  A11
Kiwi Browser Version 98.0

Additional context
Would love to show bookmarks instead of those links & news. Or, 'Classic homepage' seems to work, it has most visited sites (?) and news can be turned off.

Would love to show bookmarks instead of those links & news.

You can add chrome://bookmarks under "Enter custom web address"

Perfect, thank you!


[REQUEST] Alternative repo address

Is your feature request related to a problem? Please describe.
This github going to get dropped as soon as it gets popular, so you should think about alternative hosting for code and releases
Describe the solution you'd like
I dont know

Totally agree. Please spread this software across all github-like services around the world.
GitHub, gitee, gitflic, etc


Fix missing translations for *.txt files

subject.txt and body.txt files in email templates have translations that were not being picked up by pybabel. Fixing pybabel config allows us to run make translations against all existing *.txt files.

This change would add a few dozen translation strings from *.txt files. I think this is the right move but let me know if we’ve left them out on purpose.

I’ll revisit this PR after #11087 is merged.

Marking this as blocked on https://github.com/pypi/warehouse/issues/7583.


dropAllForeignKeyConstraint performance problems

Environment
Liquibase Version: 4.4.2
Liquibase Integration & Version: Java
Liquibase Extension(s) & Version: -
Database Vendor & Version: PostgreSQL 12.6
Operating System Type & Version: RHEL, but happens as well on Windows 10 and centos
Description
The dropAllForeignKeyConstraints change performs poorly for bigger database schemas in PostgreSQL databases, because more or less the complete schema metadata is loaded for finding the names of the foreign key constraints of a single table.
Steps To Reproduce
You can use this changelog file to see the execution time difference between the two variants of dropping foreign key constraints.  The actual performance impact depends on the size of the schema.
db.foreignKeyDeletionTest.txt
(Note: The file should be an XML changelog, but Github won't let me upload XML files here)
Actual Behavior
Using the dropAllForeignKeyConstraints is significantly slower than using several explicit dropForeignKeyConstraint changes.
When querying the database for the names of all foreign key constraints of the specified table, the complete schema information is loaded (all tables, foreign keys, primary keys, sequences, views, indizes etc.). Therefore the performance severly deteriorates for bigger schemas.

2021-10-22 08:37:26,586 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) ChangeSet database/db.core-test-20.xml::dropTestForeignKeysFast-1634818033::rsp ran successfully in 16ms

vs

2021-10-22 08:37:27,684 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) ChangeSet database/db.core-test-20.xml::dropTestForeignKeysSlow-1634818754::rsp ran successfully in 1093ms

Here is the log output for a local execution of the provided reproducer changeset with a local database containing a relatively small schema (~ 30 tables).

2021-10-22 08:37:26,528 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Running Changeset:database/db.core-test-20.xml::setupTestResources-1634817987::rsp
2021-10-22 08:37:26,533 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Reading ChangeSet: database/db.core-test-20.xml::setupTestResources-1634817987::rsp
2021-10-22 08:37:26,539 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Table otherTable created
2021-10-22 08:37:26,549 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Table foreignKeyDeletionTest01 created
2021-10-22 08:37:26,557 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Table foreignKeyDeletionTest02 created
2021-10-22 08:37:26,561 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) ChangeSet database/db.core-test-20.xml::setupTestResources-1634817987::rsp ran successfully in 33ms
2021-10-22 08:37:26,569 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Running Changeset:database/db.core-test-20.xml::dropTestForeignKeysFast-1634818033::rsp
2021-10-22 08:37:26,571 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Reading ChangeSet: database/db.core-test-20.xml::dropTestForeignKeysFast-1634818033::rsp
2021-10-22 08:37:26,574 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Foreign key FK_foreignKeyDeletionTest01_01 dropped
2021-10-22 08:37:26,577 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Foreign key FK_foreignKeyDeletionTest01_02 dropped
2021-10-22 08:37:26,579 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Foreign key FK_foreignKeyDeletionTest01_03 dropped
2021-10-22 08:37:26,581 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Foreign key FK_foreignKeyDeletionTest01_04 dropped
2021-10-22 08:37:26,583 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Foreign key FK_foreignKeyDeletionTest01_05 dropped
2021-10-22 08:37:26,586 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) ChangeSet database/db.core-test-20.xml::dropTestForeignKeysFast-1634818033::rsp ran successfully in 16ms
2021-10-22 08:37:26,590 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Running Changeset:database/db.core-test-20.xml::dropTestForeignKeysSlow-1634818754::rsp
2021-10-22 08:37:26,592 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Reading ChangeSet: database/db.core-test-20.xml::dropTestForeignKeysSlow-1634818754::rsp
2021-10-22 08:37:27,673 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Foreign keys on base table foreignKeyDeletionTest02 dropped
2021-10-22 08:37:27,684 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) ChangeSet database/db.core-test-20.xml::dropTestForeignKeysSlow-1634818754::rsp ran successfully in 1093ms
2021-10-22 08:37:27,688 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Running Changeset:database/db.core-test-20.xml::cleanupTestResources-1634819123::rsp
2021-10-22 08:37:27,690 - FINE  [liquibase.changelog] (ServerService Thread Pool -- 58) Reading ChangeSet: database/db.core-test-20.xml::cleanupTestResources-1634819123::rsp
2021-10-22 08:37:27,692 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Table foreignKeyDeletionTest01 dropped
2021-10-22 08:37:27,693 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Table foreignKeyDeletionTest02 dropped
2021-10-22 08:37:27,696 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) Table otherTable dropped
2021-10-22 08:37:27,698 - INFO  [liquibase.changelog] (ServerService Thread Pool -- 58) ChangeSet database/db.core-test-20.xml::cleanupTestResources-1634819123::rsp ran successfully in 10ms

Expected/Desired Behavior
The dropAllForeignKeyConstraints change should not load the complete schema metadata for finding the names of the foreign key constraints of a single table.
In the same way, the execution time of the change should not significantly increase with the amount of objects in the DB schema.
Additional Context
There is another bug which could be related to this one => #1571
I commented on it, but decided to create a separete one since we are using a different database and Liquibase version.
Also, I think I know why the change misbehaves, and I might be able to provide a PR for fixing it

Hi @Spindl Thanks for bringing this issue to our attention.  And thanks for adding a PR to fix it.
We will add this to the list of issues that we are processing.

@Spindl thank you for this PR! We have a database with 1900+ tables. We are upgrading liquibase from 3.5 to the latest (4.9.0). A full database build went from about 12 minutes to over an hour. I copied your file into our custom liquibase plugin and now the processing time is back to the expected time.
@molivasdat can this issue and PR review be prioritized. It's extremely evident in our project that DropAllForeignKeyConstraintsChange has some serious performance issues with the Snapshot process.

The attached PR seems good, moving it forward. Thanks!


Issues Need Milestones

@drphilmarshall can you please give me write access so that I can put a deadline on the issues that I need to finish? Thank you!

Done! You should be able to create milestones, assign issues etc now.

Thanks for the milestones, @milanwilliams ! I moved the two outstanding issues to the TDC2 launch milestone, so yours is nice and complete. Thanks for all your help this summer! It was a real pleasure having you with us :-)


chore: bump @superset-ui/plugin-chart-table to 0.17.28

SUMMARY
bump @superset-ui/plugin-chart-table to 0.17.28 to bring in https://github.com/apache-superset/superset-ui/pull/1039
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
See https://github.com/apache-superset/superset-ui/pull/1039
TEST PLAN
Manual testing and visual confirmation
ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

Also bump chrono-node so it adds typing. https://github.com/apache/superset/pull/13797#discussion_r605869581

/testenv up


feat: add grapple window highlight groups

I was recently asked to add support for this plugin to cyberdream.nvim and was surprised to find there were no highlight groups for grapple windows.
This PR resolves that by adding the following new groups:

GrappleFloat
GrappleBorder
GrappleTitle
GrappleFooter

Showcase

Thanks for taking the time to add these 🙂


Optimize CI build matrix

In Coherent OSS, I asked jaraco about this very specific test matrix in his CI setups, used widely in projects like setuptools or pip-run.
I made him write this doc: https://blog.jaraco.com/efficient-use-of-ci-resources/
A PR utilizing this practice is going to land soon.

The matrix here is specifically meant to match that of pydantic. I don't want to change it. Also this repo is probably not going to get much activity so I don't think it's worth optimising it.


Preview is very dark

Hello people.
Just wonder why the camera's PreviewImage returned is very dark, like almost pitch black. I've switch on all the lights, face a flashlight on my face, it is still extremely dark. I see that it has some bluish tint, maybe that's the reason.
Tried with the c# example. Same with my own project.
It will ID correctly though.
Any help is greatly appreciated
-EDIT-
after calling _authenticator.Authenticate, it becomes very dark. Only after a long while, it gets brighter a bit.
-2ND EDIT-
point to a black shirt, click Authenticate, the preview becomes dark. Points to a white object, click Authenticate, the preview becomes bright a bit.  Then point back to myself. Preview then becomes dark

Hi @nickticket2u
Thanks for submitting this issue.  We will have a look into this and let you know what we find out.
Just to confirm again, you're not seeing an issue with authenticate even though the preview looks like this?

thanks for the response.
yeah authenticate works fine.
On Tue, 9 Mar 2021 at 3:29 AM, RealSenseSupport<EMAIL_ADDRESS>wrote:

Hi @nickticket2u https://github.com/nickticket2u
Thanks for submitting this issue. We will have a look into this and let
you know what we find out.
Just to confirm again, you're not seeing an issue with authenticate even
though the preview looks like this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/RealSenseID/issues/12#issuecomment-793013916,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APHASGSS4K3MXFLRFCNJZQLTCUQTLANCNFSM4YZHZMOA
.

hey @nickticket2u
I've been watching your ticket, as I recognise value in the preview feature.
Just a heads up, instead of doing edits to the first post, it might be better to make new comments, as they would alert the people involved with this project with the further information related to this issue.
On a platform such as reddit, the edits in the post work well because you are counting on continual new viewers.

I have observed an opposite behaviour. I was testing a backlight situation but this occurs in a well lit situation too. When a person enters the frame (even if it is far) there is higher exposure compensation done (light in the background gets bloated). Is this done on purpose?

@nickticket2u
Does RealSenseID/releases/tag/v0.15.0 resolve the issue for you ?

Will have time to try it next week 🙏😁
On Sat, 3 Apr 2021 at 1:55 AM, 3dsf @.***> wrote:

@nickticket2u https://github.com/nickticket2u
Does RealSenseID/releases/tag/v0.15.0 resolve the issue for you ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/RealSenseID/issues/12#issuecomment-812640598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APHASGTELYBN2GFBCA6JLR3TGYAIBANCNFSM4YZHZMOA
.

problem is solved with latest firmware


SpinLock: Overhaul false sharing prevention

This changes how false sharing in SpinLock is prevented. Formerly, alignment attributes were used. The problem with that is objects containing SpinLocks could be allocated in a way that the alignment is not honored, leading to crashes.
This PR also applies the new approach to the Apple implementation.
This approach could be refactored into a more general one that we may want to use in other sync primitives. However, the point is now to fix the only case we have at the moment.
Fixes crashes stated in https://github.com/godotengine/godot/pull/85167#issuecomment-2468695017.

@yretenai, following up here. Could you please test this one?

1000 force-pushes later... 😅

AVX2 and AVX512 builds are fixed with this patchset.

@Calinou, could you please give this a go?

Tested myself. Performance stays compared to prior to this PR, noise aside.

Thanks!

Still, for the records, we would really like to be able to rely on alignment and base this on it. @hpvb is looking into making Godot allocation aware of alignment.

@RandomShaper I'll make a pr for memory.cpp/h asap. It should be a relatively small fix.


Add a bit more logging, and split up the binds tests

Description
Bindings tests aren't checking the status code received from the bindings API. Add that and some logging.
Issue reference
ref: #3031
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test


sts-wire complains while restarting after the first setup

after a first installation , sts-wire is not starting anymore  and complain with oauth error ( seems like the callback url previously cached is not ok anymore)
ERROR:
OAuth Error
error="invalid_grant", error_description="Invalid redirect: http://localhost:54452/oauth2/callback does not match one of the registered values: [http://localhost:53742/oauth2/callback]"

Should be solved since v1.3.2


Update docker container

@JayH5 Please review

Looks great! 🍰
I'll give it a proper run-through on Monday

@JayH5 Ready for re-review

@JayH5 Please review


post method return 404

http://<IP_ADDRESS>:8100/translate/?"text"= "Hello World"&"source_lang"= "EN"&"target_lang"= "ZH"
{"code":404,"message":"No Translate Text Found"}
get method works.

You should probably learn how to initiate GET/POST requests.

BTW, I want to tell you that the project I wrote only supports POST requests.


write to stdout and and exit with error code on bad arguments

Following #147, this fix will return an error code and print the output to STDERR on bad arguments.

✨ 🍰 ✨ thanks


consul: 1.14.3 -> 1.14.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/hashicorp/consul/releases.
meta.description for consul is: Tool for service discovery, monitoring and configuration
meta.homepage for consul is: https://www.consul.io/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.14.4 with grep in /nix/store/cdmiylmrr0ak4kr7hdamhxmd98a2na3c-consul-1.14.4
found 1.14.4 in filename of file in /nix/store/cdmiylmrr0ak4kr7hdamhxmd98a2na3c-consul-1.14.4

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
consul

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cdmiylmrr0ak4kr7hdamhxmd98a2na3c-consul-1.14.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A consul https://github.com/r-ryantm/nixpkgs/archive/5a1f956291cbfbb0583c9d74a26099d19de52626.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cdmiylmrr0ak4kr7hdamhxmd98a2na3c-consul-1.14.4
ls -la /nix/store/cdmiylmrr0ak4kr7hdamhxmd98a2na3c-consul-1.14.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

consul

Maintainer pings
cc @pradeepchhetri @vdemeester @nh2 @techknowlogick for testing.

Result of nixpkgs-review pr 213964 run on aarch64-darwin 1

1 package built:

consul


Specify claims group field in auth directive

Is your feature request related to a problem? Please describe.
I need to use claims information in addition to the cognito groups to apply authentication rules. I would like to specify the identifyField for groups in a similar manner as exists for owners.
While I could overload the owner rule to have many owners, it produces ugly code that is hard to audit.
Describe the solution you'd like
graphql-auth-transformer/src/resources.ts has a TODO comment:
// TODO: Enhance cognito:groups to work with non cognito based auth.
There may be a straightforward way to allow this by overloading setUserGroups to take an optional "identityField" string.
I would like the setUserGroups function to take an optional "identityField" string to override "cognito:groups" as the claim to check against.
Describe alternatives you've considered
I could use the preToken Lambda to overload "cognito:groups" claim information, but I'd rather keep these systems separate and be clear what claims come from cognito user pools and what comes from other sources.
Additional context
Attached is a patch file based on 54a8d that accomplishes the basics with ~12 lines changed. You may want to consider a name other than identityField if you don't want to overload terminology
patch.txt

Hey @RossWilliams , Apologies for the incredibly late response. Wanted to make sure that the future readers see the resolution.
We have implemented this feature. Please refer here for more details.


Host an generated list of proxyfied sites

Hello,
I wanted to have a dynamic list of the sites proxyfied by this container. And try to mockup it.
It will generate a index.html listing all the VIRTUAL_HOST from the container. It will use the content of env variable TITLE for each container to replace the link by something more useful.
I don't know either go and go templating and this may be not sufficient for all the cases adressed by origin, but I think it could be a nice-to-have feature to be enhanced by more specialized people.

Thanks @marema31.  I think this would be better suited in a custom image derived from this image.


docs(changelog) add 0.11.1 changeset

@kinman Will you please give this a grammar review? Thank you! :)

@kinman Thank you!


Added executable flag to build.sh

Makes for a cleaner "clone and go" experience from Unix. Without this,
you have to "chmod +x build.sh" before use.

Thank you.


When I started a K8s cluster using IPv6 only mode, the calico node will fall into wrong status.

When I started a K8s cluster using IPv6 only mode, the calico node will fall into wrong status.
It is mainly like:
 Warning  Unhealthy  40s   kubelet            Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
W0617 12:35:45.538842      83 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.
  Warning  Unhealthy  39s  kubelet  Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
W0617 12:35:46.508603     160 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.

Expected Behavior

Get a k8s cluster  with calico with IPv6-only mode.

Current Behavior

a@sdn233:~/IPv6$ kubectl get pod -A
NAMESPACE     NAME                                      READY   STATUS    RESTARTS      AGE
kube-system   calico-kube-controllers-57b57c56f-dc74k   0/1     Pending   0             6m51s
kube-system   calico-node-tgjwx                         0/1     Running   5 (31s ago)   6m51s
kube-system   coredns-567c556887-h4m85                  0/1     Pending   0             14m
kube-system   coredns-567c556887-stfnp                  0/1     Pending   0             14m
kube-system   etcd-sdn233                               1/1     Running   4             14m
kube-system   kube-apiserver-sdn233                     1/1     Running   3             14m
kube-system   kube-controller-manager-sdn233            1/1     Running   3             14m
kube-system   kube-proxy-8slxg                          1/1     Running   0             14m
kube-system   kube-scheduler-sdn233                     1/1     Running   4             14m

a@sdn233:~/IPv6$ kubectl describe pod -n kube-system calico-node-tgjwx
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  7m35s                  default-scheduler  Successfully assigned kube-system/calico-node-tgjwx to sdn233
  Normal   Pulled     7m35s                  kubelet            Container image "docker.io/calico/cni:v3.25.0" already present on machine
  Normal   Created    7m35s                  kubelet            Created container upgrade-ipam
  Normal   Started    7m34s                  kubelet            Started container upgrade-ipam
  Normal   Pulled     7m33s                  kubelet            Container image "docker.io/calico/cni:v3.25.0" already present on machine
  Normal   Created    7m33s                  kubelet            Created container install-cni
  Normal   Started    7m33s                  kubelet            Started container install-cni
  Normal   Pulling    7m30s                  kubelet            Pulling image "docker.io/calico/node:v3.25.0"
  Normal   Pulled     7m10s                  kubelet            Successfully pulled image "docker.io/calico/node:v3.25.0" in 20.206903044s (20.206926398s including waiting)
  Normal   Created    7m10s                  kubelet            Created container mount-bpffs
  Normal   Started    7m10s                  kubelet            Started container mount-bpffs
  Normal   Pulled     7m4s                   kubelet            Container image "docker.io/calico/node:v3.25.0" already present on machine
  Normal   Created    7m4s                   kubelet            Created container calico-node
  Normal   Started    7m4s                   kubelet            Started container calico-node
  Warning  Unhealthy  6m15s (x7 over 7m3s)   kubelet            Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
  Warning  Unhealthy  6m5s (x4 over 6m45s)   kubelet            Liveness probe failed: calico/node is not ready: bird/confd is not live: Service bird is not running. Output << down: /etc/service/enabled/bird: 0s, normally up, want up >>
  Warning  Unhealthy  2m35s (x4 over 6m25s)  kubelet            Liveness probe failed: calico/node is not ready: bird/confd is not live: Service bird is not running. Output << down: /etc/service/enabled/bird: 1s, normally up, want up >>

kubectl logs -n kube-system calico-node-xxxx, it is too long, I show the end of the output.
2023-06-17 12:35:48.907 [INFO][128] felix/health.go 336: Overall health status changed: live=true ready=true
+---------------------------+---------+----------------+-----------------+--------+
|         COMPONENT         | TIMEOUT |    LIVENESS    |    READINESS    | DETAIL |
+---------------------------+---------+----------------+-----------------+--------+
| CalculationGraph          | 30s     | reporting live | reporting ready |        |
| FelixStartup              | -       | reporting live | reporting ready |        |
| InternalDataplaneMainLoop | 1m30s   | reporting live | reporting ready |        |
+---------------------------+---------+----------------+-----------------+--------+
2023-06-17 12:36:46.520 [INFO][127] monitor-addresses/autodetection_methods.go 117: Using autodetected IPv6 address 3001:1::233/64 on matching interface ens41f0
2023-06-17 12:36:50.480 [INFO][128] felix/summary.go 100: Summarising 23 dataplane reconciliation loops over 1m3.9s: avg=28ms longest=316ms (resync-filter-v4,resync-filter-v6,resync-ipsets-v4,resync-ipsets-v6,resync-mangle-v4,resync-mangle-v6,resync-nat-v4,resync-nat-v6,resync-raw-v4,resync-raw-v6,resync-routes-v4,resync-routes-v4,resync-routes-v6,resync-routes-v6,resync-rules-v4,resync-rules-v6,update-ipsets-4,update-ipsets-6)

Possible Solution

configure some parameters I do not know the let the cluster and cni work fine.
 This
        # container programs network policy and routes on each
        # host.
        - name: calico-node
          image: docker.io/calico/node:v3.26.0
          imagePullPolicy: IfNotPresent
          envFrom:
          - configMapRef:
              # Allow KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT to be overridden for eBPF mode.
              name: kubernetes-services-endpoint
              optional: true
          env:
            # Use Kubernetes API as the backing datastore.
            - name: DATASTORE_TYPE
              value: "kubernetes"
            # Wait for the datastore.
            - name: WAIT_FOR_DATASTORE
              value: "true"
            # Set based on the k8s node name.
            - name: NODENAME
              valueFrom:
                fieldRef:
                  fieldPath: spec.nodeName
            # Choose the backend to use.
            - name: CALICO_NETWORKING_BACKEND
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: calico_backend
            # Cluster type to identify the deployment type
            - name: CLUSTER_TYPE
              value: "k8s,bgp"
            # Auto-detect the BGP IP address.
            - name: IP
              value: "none"
            - name: IP6
              value: "autodetect"
            # Enable IPIP
            - name: CALICO_IPV4POOL_IPIP
              value: "Never"
            # Enable or Disable VXLAN on the default IP pool.
            - name: CALICO_IPV4POOL_VXLAN
              value: "Never"
            # Enable or Disable VXLAN on the default IPv6 IP pool.
            - name: CALICO_IPV6POOL_VXLAN
              value: "Never"
            # Set MTU for tunnel device used if ipip is enabled
            - name: FELIX_IPINIPMTU
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: veth_mtu
            # Set MTU for the VXLAN tunnel device.
            - name: FELIX_VXLANMTU
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: veth_mtu
            # Set MTU for the Wireguard tunnel device.
            - name: FELIX_WIREGUARDMTU
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: veth_mtu
            # The default IPv4 pool to create on startup if none exists. Pod IPs will be
            # chosen from this range. Changing this value after installation will have
            # no effect. This should fall within `--cluster-cidr`.
#            - name: CALICO_IPV4POOL_CIDR
#              value: "<IP_ADDRESS>/16"
            - name: CALICO_IPV6POOL_CIDR
              value: "3001:1::1/63"
            # Disable file logging so `kubectl logs` works.
            - name: CALICO_ROUTER_ID
              value: "hash"
            - name: IP6_AUTODETECTION_METHOD
              value: "interface=ens41f0"
              # INTERFACE_NAME=ens33
            - name: CALICO_DISABLE_FILE_LOGGING
              value: "true"
            # Set Felix endpoint to host default action to ACCEPT.
            - name: FELIX_DEFAULTENDPOINTTOHOSTACTION
              value: "ACCEPT"
            # Disable IPv6 on Kubernetes.
            - name: FELIX_IPV6SUPPORT
              value: "true"
            - name: FELIX_HEALTHENABLED
              value: "true"
.
.
.

/etc/hosts files
yxf@sdn233:~/SRv6-INT$ cat /etc/hosts
<IP_ADDRESS>       localhost
::1 localhost
<IP_ADDRESS> sdn233

::1 sdn233
3002:1::233 sdn233

#::1 sdn233
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

ip a
server interface which I can ssh to
4: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:05:5d:88:d7:74 brd ff:ff:ff:ff:ff:ff
    altname enp26s0f2
    altname ens31f2
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global noprefixroute eno3
       valid_lft forever preferred_lft forever
    inet6 fe80::b605:5dff:fe88:d774/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

used for k8s node interface
5: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:05:5d:88:d7:75 brd ff:ff:ff:ff:ff:ff
    altname enp26s0f3
    altname ens31f3
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global noprefixroute eno4
       valid_lft forever preferred_lft forever
    inet6 3002:1::233/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::b605:5dff:fe88:d775/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

used for bind calico interface
8: ens41f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 40:a6:b7:36:d0:58 brd ff:ff:ff:ff:ff:ff
    altname enp94s0f0
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global noprefixroute ens41f0
       valid_lft forever preferred_lft forever
    inet6 3001:1::233/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::42a6:b7ff:fe36:d058/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Your Environment

Calico version 3.26 and 3.25, I tried them all
Orchestrator version (e.g. kubernetes, mesos, rkt): K8s 1.26.5
Operating System and version: Ubuntu 20
Link to your project (optional):

Normal   Created    7m10s                  kubelet            Created container mount-bpffs

Do you run in bpf mode by any chance?

@xfyan0408 Do you run in bpf mode? Can you get the output of kubectl get ippools -owide and kubectl get pods -A -owide

@xfyan0408 Do you run in bpf mode? Can you get the output of kubectl get ippools -owide and kubectl get pods -A -owide

yxf@sdn233:~/SRv6-INT$ kubectl get ippools  -owide
NAME                  AGE
default-ipv4-ippool   3m32s
default-ipv6-ippool   3m32s
yxf@sdn233:~/SRv6-INT$ kubectl get pods -A -owide
NAMESPACE     NAME                                      READY   STATUS    RESTARTS      AGE     IP                            NODE     NOMINATED NODE   READINESS GATES
kube-system   calico-kube-controllers-57b57c56f-qwjtb   1/1     Running   0             3m54s   3001:1::33be:1c82:f097:5a41   sdn233   <none>           <none>
kube-system   calico-node-x6cvk                         0/1     Running   3 (23s ago)   3m54s   3002:1::233                   sdn233   <none>           <none>
kube-system   coredns-567c556887-sjthh                  1/1     Running   0             17m     3001:1::33be:1c82:f097:5a40   sdn233   <none>           <none>
kube-system   coredns-567c556887-v46zp                  1/1     Running   0             17m     3001:1::33be:1c82:f097:5a42   sdn233   <none>           <none>
kube-system   etcd-sdn233                               1/1     Running   4527          16m     3002:1::233                   sdn233   <none>           <none>
kube-system   kube-apiserver-sdn233                     1/1     Running   2             17m     3002:1::233                   sdn233   <none>           <none>
kube-system   kube-controller-manager-sdn233            1/1     Running   2             17m     3002:1::233                   sdn233   <none>           <none>
kube-system   kube-proxy-svrfh                          1/1     Running   0             17m     3002:1::233                   sdn233   <none>           <none>
kube-system   kube-scheduler-sdn233                     1/1     Running   2             17m     3002:1::233                   sdn233   <none>           <none>

When I ran  kubectl logs  -n kube-system calico-node-x6cvk
bird: /etc/calico/confd/config/bird.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird6.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird6.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird6.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird6.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird6.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird.cfg:9:11 syntax error
bird: /etc/calico/confd/config/bird6.cfg:9:11 syntax error

Hi xfyan0408，I have the same problem in my cluster. The reason is node not have ipv4 address, therefore can't generate router id in brid config. You can add this config in your calico-node daemonset, maybe will work well.
Document is in here: https://docs.tigera.io/calico/latest/reference/configure-calico-node#setting-calico_router_id-for-ipv6-only-system

Hi, I also encountered this issue, although it may not be exactly the same. Perhaps my troubleshooting steps could be helpful.
First, the issue lies in the configuration file of bird. So I use kubectl exec -it -n kube-system calico-node-x6cvk -- cat /etc/calico/confd/config/bird.cfg get bird's config. But I found there was not generate expected router id in this line. Then I checked my configuration, I ignored config CALICO_ROUTER_ID : hash. After add it in daemonset and redeployed calico. It work well. If it not work, Did your configuration persist？

@GaoChX not in ebpf?

@tomastigera Yes

I meet the same issue again.
 Can you get the output of kubectl get ippools -owide and kubectl get pods -A -owide

I do not use bpf mode, I just modify the IPv6 filed in calico.yaml

@xfyan0408 I have a vague memory (please correct me if I'm wrong) that kubernetes doesn't support a "strict" ipv6 only mode, and that you can have ipv6 by enabling dual stack ipv4+ipv6 and simply not using ipv4... If that's the case, I don't think it's right to comment out clusterCIDR in kubeadm, and the ipv4 IP pool in calico config... Could you try having those present? (maybe the correct way would be to add disabled: true to the ipv4 IP pool, and also commenting it out from the manifest might not have the desired effect, felix might still create the default ipv4 with default settings)
Could you try those? Also, if possible, enable debug logging on FelixConfig and send us the calico-node logs from the crashing pod:
kubectl patch felixconfiguration default --type merge --patch='{"spec":{"logSeverityScreen":"Debug"}}'

The output to kubectl get ippools -o yaml and kubectl get felixconfig -o yaml might also be helpful.
Thanks!

@xfyan0408 any updates on this? Could you please post the requested info?

@xfyan0408 any updates? could you please try @GaoChX 's troubleshooting step? (kubectl exec -it -n kube-system calico-node-x6cvk -- cat /etc/calico/confd/config/bird.cfg, also for bird6.cfg as bird is complaining about syntax errors in these files)

@xfyan0408 any updates? I'm leaning towards closing the issue for inactivity, feel free to reopen with more info if you're still facing this issue...


Dynamically linked library path resolution with cargo clif test --doc differs from cargo test --doc

In https://github.com/bevyengine/bevy/issues/14129, we discovered an issue when running cargo test --doc on Windows when linking Bevy dynamically. See that issue for a reproducible minimal example.
In https://github.com/bevyengine/bevy-website/pull/1522, I added a workaround to Bevy's documentation, namely:

In order to run cargo test --doc, you must also add the path returned by rustc --print target-libdir to your PATH environment variable.

This fixes this issue when running cargo test --doc, but cargo clif test --doc still results in a dynamic library resolution error:
Test executable failed (exit code: 0xc0000135).

cargo-clif uses a separate sysroot. I think you can use rustc-clif --print target-libdir where rustc-clif is the executable right next to the cargo-clif you used for running tests.

I've added the output of that command to my PATH and tried running doc tests in a project I happened to have open. One that previously failed now runs, which is good, however the other two fail with the following:
Test executable failed (exit code: 0xc000001d).

stderr:
thread 'main' panicked at D:\a\rustc_codegen_cranelift\rustc_codegen_cranelift\build\stdlib\library\std\src\sync\once.rs:217:20:
assertion failed: state_and_queue.addr() & STATE_MASK == RUNNING
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I'll try seeing if this also happens on the linked minimal example.

I did not manage to get the exact error message, but another one. Opening a new issue since this one is resolved at least.


Setup GitHub Container registry for preScaler's initContainer and Operator

Setup GitHub Container registry to store preScaler's initContainer and Operator

https://ghcr.io
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry

closing the issue as release CI was created with PR #6 #7 #8 #9 #10


Implemented Debug() call on driver, to enable debugging when running different webdrivers.

It occured twice this week that we discovered the problem when reading
the output of the driver being run.

This makes sense -- I'll merge this tonight.

Merged with some changes. I made the debug option more similar to the timeout option and added tests.


PV land area UI cleanup

Fix #1125

Fix mistake in calculation of array area in hectares (only affects UI calculated value).
Add new UI calculated variables to show module area in acres and hectares. This makes it a little clearer how module area relates to total land area, and makes the effect of GCR and tilt angle more apparent when the user changes those inputs.
Reorganize PV land area inputs and edit UI text.
Regenerate API files for new UI inputs (new inputs should not affect SSC).
Help revisions will be done separately.

The diffs loaded ok for me:


Add View Resume functionality in Resume Page

Why do we need this
The addition of the "View Resume" functionality on the Resume Page is crucial for enhancing the user experience and providing a comprehensive set of features to our users. Currently, users can upload and download their resumes, but the ability to preview the content directly on the Resume Page adds a new layer of convenience. Users often want to review the content of their resumes without the need for downloading, and this feature fulfills that need.
Scope of Impact:
Improved User Experience: Users can seamlessly review their resumes within the application, reducing the need for additional steps like downloading.
Increased Engagement: The convenience of previewing resumes on the Resume Page may encourage users to interact with the platform more frequently.
Time and Effort Saving: Users can quickly verify the content of their resumes, making the overall process more efficient.
Implementation
Create a section where the uploaded file will be available to view for the user.

This is a good idea. How are we implementing it?

We intend to showcase it by embedding it as an iframe on the page. What do you think about it ?

Yeah, that's a great idea. We can directly print from an iframe pdf viewer as well!

Yep, iframe opens up a lot of possibilitites. Go ahead

Implementing now.


Generate runtime API reference documentation

Description of changes:
Updates the API reference generator script to support the APIs defined in the runtime repository. Also updates the HTML of the API reference page to place the APIs in their own section at the top under Common.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


[multus-crd] Enables Multus with Network Plumbing Working Group CRDs

Allows cloning from alternative git sources for Multus, and includes support of modifications based on network plumbing working group spec.
PR #173 is made unnecessary with this fix.
Fixes #172

This one is well tested & is generally isolated to Multus, I'm going to bring it in. No input after a week or so.


Fix local flink test

Looks like the local Flink test was failing due to an unavailable Flink operator version.
The terraform for the AWS cloud deployment uses version 1.5.0, so starting by upgrading to that here.

So far I've got this assert to pass
https://github.com/pangeo-forge/pangeo-forge-runner/blob/db67f2232a49087ff3885dc3bc01aa1cace5b4d8/tests/integration/test_flink.py#L53
but something below there appears to be hanging, as the last test was running for > 1 hr. Just cancelled it. I'll checkout what might be hanging as the next step.

merging as improvement over status quo


vscx/ms-vsliveshare-vsliveshare: 1.0.2902 -> 1.0.3912

This was broken on vscode >= 1.53.0.
Cleans up a bunch of things:

uses substitution over sed & wrappers, messing with $PATH less and making everything more clear
substitutes xprop in the correct place (this was never actually used in the launcher scripts)
substitutes references to xsel — although this isn't strictly necessary, as it bundles the binary(!)
substitutes hardcoded /bin/bash (the vsls scheme handler cannot have actually worked before on NixOS)

Supersedes #112909.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 115277 run on x86_64-linux 1

1 package built:

vscode-extensions.ms-vsliveshare.vsliveshare

I've just tested it and it fixed for me. Now I wonder if https://github.com/NixOS/nixpkgs/pull/115249 wont break it again ?

@teto: I would hope not! This is the latest version as per mp.vs/MS-vsliveshare.vsliveshare.
The extension was broken due to not having been updated in nixpkgs for months, while depending on an unstable "proposed" API that was later removed. Having automatic update PRs for VS Code extensions would help prevent future issues of this sort cropping up (and more closely reflect how they're used by normal people). @ryantm, is this something that would be simple to add to your bot?

This is the place for API experiments and proposals.
These API are NOT stable and subject to change. They are only available in the Insiders
distribution and CANNOT be used in published extensions.

Perhaps Microsoft should read their own documentation :)

@deviant: Excellent cleanup of the original draft. :+1:

Works fine too here on nixos, using vscode 1.53.2, with extension 1.03912 both local instances built from latest nixpkgs:
$ cd /path/to/latest/nixpkgs
$ nix-build -I nixpkgs=. -E 'with import <nixpkgs> {config={allowUnfree = true;};}; vscode-with-extensions.override {vscodeExtensions = with vscode-extensions; [ms-vsliveshare.vsliveshare];}'
$ ./result/bin/code .


Fixes grammatical error in preflight exercise 4 of js3

Problem
Closes #1216

Solution
Fixes 2 typos: word "multiple" and "could call"

If you have any screenshot of what the content looks like after the fix, please include that in your PR description as well


question about how to perform the code

Why is this function not defined

I'm not experienced in resnet or NNs at all, so take my advice with a grain of salt, but I think the definition should be:
class LambdaLayer(nn.Module):
    def __init__(self, lambd):
        super(LambdaLayer, self).__init__()
        self.lambd = lambd
    def forward(self, x):
        return self.lambd(x)

I hope this helps. I agree that it is odd not to have defined this somewhere.


Delete torrent with data?

Is there any option to delete torrent and data?

Of course, just click "Remove" (you can find it in the context menu if you right-click it on the torrent; or select the torrent and choose the red X in the toolbar) and check the "Delete local data" box:


add support for Oracle "TIMESTAMP WITH (LOCAL_)TIME_ZONE" column type.

Oracle has "TIMESTAMP WITH LOCAL_TIME_ZONE" and TIMESTAMP WITH TIME_ZONE" column type, which  MetaModel doesn't support now.

Seems like a clean fix to me. Only remark is that you've used tabs instead of spaces in the Oracle class.

Sorry for tabs, I didn't notice the Coding guidelines. Do I need to fix them and PR again?

You can just make the change in the same branch. The PR will then auto-update.

Looks good - merging


[BUG]refresh of btp_subaccount_api_credential resource during planning phase resets the secret to null.

Is there an existing issue for this?

[X] I have searched the existing issues

What version of the Terraform provider are you using?
1.8.0
What version of the Terraform CLI are you using?
1.9.3
What type of issue are you facing
bug report
Describe the bug
After an initial and successful creation of a btp_subaccount_api_credential resource the subsequent planning operation reset the value of the api_credential secret to null.
This makes tf choke if the secret is used to compute the access token.
This is an unexpected behaviour and reported as such in the tf trace log
Expected Behavior
One should be able to create a single instance of the btp_subaccount_api_credential resource and be able to run the same tf configuration multiple times
Steps To Reproduce
Full GHA trace log
https://github.com/quovadis-btp/btp-boosters/actions/runs/11756380729/job/32752461363
User's Role Collections
No response
Add screenshots to help explain your problem

2024-11-09T12:50:24.963Z [WARN]  Provider "registry.terraform.io/sap/btp" produced an unexpected new value for module.custom_idp.btp_subaccount_api_credential.quovadis-haa during refresh.
      - .client_secret: was cty.StringVal("btp-bootstrap-quovadis-***$CIJqSpsC8ujOSw8W8tjHk4LKk_miMvTEAt9Bwy4ZHiM="), but now null
      - .certificate_received: was null, but now cty.StringVal("")
2024-11-09T12:50:24.972Z [DEBUG] ReferenceTransformer: "module.custom_idp.data.http.api-credential-token" references: []
Error: -09T12:50:24.972Z [ERROR] vertex "module.custom_idp.data.http.api-credential-token" error: Invalid template interpolation value
Error: -09T12:50:24.972Z [ERROR] vertex "module.custom_idp.data.http.api-credential-token (expand)" error: Invalid template interpolation value

and then further on...
2024-11-09T12:50:39.418Z [WARN]  Planning encountered errors, so plan is not applyable

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply" which may have affected this plan:

  # module.custom_idp.btp_subaccount_api_credential.quovadis-haa has changed
  ~ resource "btp_subaccount_api_credential" "quovadis-haa" {
      - client_secret        = "btp-bootstrap-quovadis-***$CIJqSpsC8ujOSw8W8tjHk4LKk_miMvTEAt9Bwy4ZHiM=" -> null
        name                 = "btp-bootstrap-quovadis-eafa589c"
        # (7 unchanged attributes hidden)
    }

Error: Invalid template interpolation value

  on .terraform/modules/custom_idp/btp-context/bootstrap-context/modules/custom-idp/bootstrap-custom-idp.tf line 196, in data "http" "api-credential-token":
 196:   request_body = "grant_type=client_credentials&client_id=${local.client_id}&client_secret=${local.client_secret}&response_type=token"
    ├────────────────
    │ local.client_secret is null

The expression result is null. Cannot include a null value in a string
template.

Additional context
Full GHA trace log
https://github.com/quovadis-btp/btp-boosters/actions/runs/11756380729/job/32752461363

The repositories are private, so we are not ables to access the code especially of the module under investigation. The Terraform team would need access or you provide the code of the module's main.tf that uses the resource in this issue

The module code is public https://github.com/quovadis-btp/btp-automation/blob/3e47ea9bbdce9cff28b7f1d168dfe84da92f5809/btp-context/bootstrap-context/modules/custom-idp/bootstrap-custom-idp.tf#L158
just mind the gap I have worked around the problem by instructing tf to recycle the resource at every plan/apply run
just remove the lifecycle section to reproduce the reported issue

Error can be reproduced
The resources btp_directory_api_credential and btp_globalaccount_api_credential also have the same issue
The BTP CLI command btp get security/api-credential does not return the secret of the created api-credential
Fix has to be made in the Read function of each of the resources

thank you. Please make sure it works with both secrets and certificates