CUDA_ERROR_ILLEGAL_ADDRESS in toy training example

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Inside virtual container:
uname -a
Linux 3558c7dc300b 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

TensorFlow installed from (source or binary): binary

TensorFlow version (use command below): v2.2.0-rc4-8-g2b96f3662b 2.2.0

Python version: Python 3.6.8

CUDA/cuDNN version:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Sun_Jul_28_19:07:16_PDT_2019
Cuda compilation tools, release 10.1, V10.1.243

GPU model and memory:

NVIDIA DGX-2
16x NVIDIA Tesla V100 (32GB)
2x Intel Xeon Platinum 8168 2.7GHz 24C/48T
1.5TB RAM
30TB Internal NVME SSD
Describe the current behavior
Crashes. Same happens in Colab and in tf-nightly.
See crash report in colab:
2020-07-30 08:06:02.330777: E tensorflow/stream_executor/cuda/cuda_event.cc:29] Error polling for event status: failed to query event: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered
Describe the expected behavior
It should work, as it does for other values of the batch and repeat parameters.
Standalone code to reproduce the issue

# This is a simplified version of https://www.tensorflow.org/guide/distributed_training

m_training_data = tf.constant([[1.1,1.]], dtype=tf.double)
dataset = tf.data.Dataset.from_tensor_slices((m_training_data,)).repeat(8*1024).batch(1024)

mirrored_strategy = tf.distribute.MirroredStrategy()
dist_dataset = mirrored_strategy.experimental_distribute_dataset(dataset)

def train_step(input):
    A = tf.matmul(input[0], tf.linalg.matrix_transpose(input[0]))
    return tf.linalg.det(A)

@tf.function
def distributed_train_step(dist_inputs):
    loss = mirrored_strategy.run(train_step, args=(dist_inputs,))
    return mirrored_strategy.reduce(tf.distribute.ReduceOp.SUM, loss,
                         axis=None)

for dist_inputs in dist_dataset:
    print(distributed_train_step(dist_inputs))

Other info / logs
crash_1002.txt

On running the Colab notebook linked, I was able to reproduce the issue with TF v2.2, TF v2.3 and TF-nightly.
Code runs without any issues for repeat(8*1024).batch(1024), but when changed to repeat(256).batch(256) session crashes. Please find the gist of it here. Thanks!

Changing labels as I don't think this is a dist-strat specific issue. The crash also occurs with Default Strategy.

Hi @fachu000, can you clarify where you are seeing the crash? Is it for the repeat(8*1024).batch(1024) example or the repeat(256).batch(256) example? Like @amahendrakar I seem to get the crash only with repeat(256).batch(256)
I can also see the crash with the following reduced code
m_training_data = tf.constant([[1,1]], dtype=tf.double)
dataset = tf.data.Dataset.from_tensor_slices((m_training_data,)).repeat(256).batch(256)

for input in dataset:
    A = tf.matmul(input[0], tf.linalg.matrix_transpose(input[0]))
    det = tf.linalg.det(A)

Hi @nikitamaia,
Colab crashes with .repeat(256).batch(256)
In the server I use (system described above), it works with .repeat(256).batch(256) but crashes with .repeat(8*1024).batch(1024)
One difference may be that I use 4 GPUs whereas Colab uses 1.
daniel

Thanks for the clarification. I'm seeing different behavior based on where I run the code and whether I use MirroredStrategy or the Default strategy.
I am able to run .repeat(256).batch(256) on GCP with 2 GPUs with MirroredStrategy, but .repeat(8*1024).batch(1024) crashes. I see the reverse behavior with 1 GPU in Colab.
I also tried running on GPU with 1 GPU and both cases worked.
However, with 2 GPUs, and using the Default strategy I get a crash on the  .repeat(256).batch(256) but .repeat(8*1024).batch(1024)  works.

@rmlarsen here cuSolverDN is failing with CUSOLVER_STATUS_EXECUTION_FAILED:
...
W tensorflow/core/framework/op_kernel.cc:1773] OP_REQUIRES failed at determinant_op.cc:228 : Internal: tensorflow/core/util/cuda_solvers.cc:466: cuSolverDN call failed with status =6
W tensorflow/core/framework/op_kernel.cc:1773] OP_REQUIRES failed at determinant_op.cc:228 : Internal: tensorflow/core/util/cuda_solvers.cc:466: cuSolverDN call failed with status =6
E tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:725] failed to record completion event; therefore, failed to create inter-stream dependency
I tensorflow/stream_executor/stream.cc:4952] [stream=0x402c0130,impl=0x402be810] did not memcpy host-to-device; source: 0x7f5089649fc0
E tensorflow/stream_executor/stream.cc:338] Error recording event in stream: Error recording CUDA event: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered; not marking stream as bad, as the Event object may be at fault. Monitor for further errors.
E tensorflow/stream_executor/cuda/cuda_event.cc:29] Error polling for event status: failed to query event: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered
F tensorflow/core/common_runtime/gpu/gpu_event_mgr.cc:220] Unexpected Event status: 1

Any idea how to debug this further?  Is it a user error?  If so, probably TF should be returning a friendlier error message.

Was able to reproduce the issue with TF v2.5 & TF v2.6.0-dev20210606 in Colab ,please find the gist here ..Thanks!

Closing this issue as it is fixed in latest version of TensorFlow. Please feel free to reopen the issue if you still have a concern. Thanks!

Is this fix in 2.5.0 or 2.6.0?

I am getting a similar issue in tensorflow 2.11.0
here are more details


Explicitly load subpackages

What does this PR do?
This introduces explicitly the concept of optimum subpackages that are loaded "dynamically" by the optimum-cli (and possibly in the future by other high-level abstraction modules that would require backend-specific implementations).
An optimum subpackage is primarily a package under the optimum namespace, but it can be also a module inside the optimum package itself, even if that module does not have its own pyproject.toml or setup.py (as a real namespace package would).
By convention, loading a subpackage means importing a subpackage module available at the root of the package.
This pull-request first adds a load_subpackages helper that will go through the installed namespace packages and try to "load" them.
It then adds a decorator to declare custom subcommands, using the same convention as the one already used in the register files.
This is by using this decorator that each subpackage can add its own subcommands, as it will be called by the optimum-cli when evaluating its commands.
In order to validate the new helpers, the onnxruntime commands are moved inside an onnxruntime/subpackage directory that is explicitly loaded by load_subpackages, but only it the onnxruntime package is available.
This improves the UX when using the optimum-cli:

commands declared as subpackages will not disappear if the content of the register directory is wiped-out by a new optimum installation,
the onnxruntime commands will only be available if the package is actually installed.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


shell_plus: get_{ipython,notebook}_arguments allow modifying extra_args

In run_notebook after get_ipython_arguments is called and the result is
modified, but since both get_ipython_arguments and get_notebook_arguments
refer to the same list this produces an invalid command line.

Coverage remained the same at 67.849% when pulling efd09cff780beb5635ca38421bc8010c5acc053c on terencehonles:fix-mutated-extra_args into dd1740815156518e96d4111969c4afa3f893f3e9 on django-extensions:master.

Coverage remained the same at 67.849% when pulling efd09cff780beb5635ca38421bc8010c5acc053c on terencehonles:fix-mutated-extra_args into dd1740815156518e96d4111969c4afa3f893f3e9 on django-extensions:master.

Think this is duplicate from the other PR's ?

@trbs I can merge it into the other PRs, but it is slightly different and is only commit 1aebcfdbdc9d5f421ee3ca8254760938b17980ee


Python: New Feature: Content Safety Layer for Python

Name : Content Safety Layer for Python
Abstract:
The idea is to have some kind of Interceptor when invoking API's that checks for Content Safety, to ensure a stable Content Safety when switching the underlaying Model. Also with Embedded Content Safety Containers, flows
Why is this a good Idea ?
When People switching from GPT4 to Anthropic for Example, they would loose the Content Safety Feature of the Azure AI Services. To ensure Responsible AI when switch between Models, we should have a layer in the Kernel to keep Content Safety when switching Model consistent.
Also when using Hugging Face Models or Onnx Models locally there is no support for content safety except in the model itself. To enable all kind of Models to work with Content Safety a seperate layer in the Kernel would be beneficial.
As far as i saw, this feature is already available in the C# Version of semantic kernel.
How can this be implemented ?
The idea here would be to add a new abstract class named ContentSafetyConnectorBase, this class would have abstract methods to enforce subclasses to implement them. Before and After sending data to the Models we could intercept the questions/answers in the ChatCompletionClientBase. We could also add an ContentSafetyException in the Semantic Kernel Exceptions and the user could catch the ContentSafetyException and deal with it accordingly.
We could also add the AzureContentSafety Service as a Connector for samples. Also there is a offline container of Content Safety, so we could have a complete offline example with SLM's and Content Safety.

Thanks for filing the feature request, @nmoeller. Could this be accomplished with our prompt filter? Not everyone may want the added latency of every request going through a content safety pipeline (I don't have data to back this up, but just a thought). We will discuss as a team, again thanks!

@moonbox3 just to clarify this is something that not everybody has to use, the simply idea would be to have something like kernel.add_content_safety(ContentSafetyConnectorBase()) and then the kernel check prompts & responses automatically. If the user does not add the ContentSafety to the Kernel everything will work like usual.
I think something like this is available in the dotnet already.
https://github.com/microsoft/semantic-kernel/tree/711afeae05eeea81e404b600d30bca2bfd206d0c/dotnet/samples/Demos/ContentSafety
But i will also check if this can be archived via prompt filters !

Understood. I see that in .Net they are using the IPromptRenderFilter interface to create the dependency for something like TextModerationFilter. I see in their getting started docs, one can download the appropriate client. This could be included in a function that implements our prompt filter and then makes the call to the content safety service.
https://learn.microsoft.com/en-us/azure/ai-services/content-safety/quickstart-text?tabs=visual-studio%2Cwindows&pivots=programming-language-python

@moonbox3 is it fine if i would start working on this ?
My Idea would be to create an folder in python/semantic-kernel/connector/content_safety.
I would implement an Class for the AzureAIContentSafety. Maybe also an Abstract Class since AWS also have something like this available.
And to demonstrate how it works i would add a Sample in Concepts using the ContentFilterConnector as a Filter.

@nmoeller do you know if something like this is already present in SK .Net? If not, we'd want to make sure we align the design for both languages before jumping into the implementation.

Sorry, I didn't even read my response to you above. :( Yeah, I think it's good to go then.


Add keyboard accessibility to toggle

Input remains in the dom (opacity: 0)
Tab to navigate to and focus on toggle
Space selects/deselects
Add focus states

Tested and verified. Nice job!


how to write kolide/fleet packs running output into kafka???

What version of fleet are you using (fleet version --full)?
What operating system are you using?
 Ubuntu 16.04

What did you do?
What did you expect to see?
               i need kolide/fleet need to read osquery from /etc/osquery/osquery.conf  and execute and write it in kafka

config i used
sudo /usr/bin/osqueryd   --enroll_secret_path=/var/osquery/enroll_secret   --tls_server_certs=/home/binu/install/8080.pem   --tls_hostname=localhost:8080   --host_identifier=hostname   --enroll_tls_endpoint=/api/v1/osquery/enroll   --config_plugin=tls   --config_tls_endpoint=/api/v1/osquery/config   --config_tls_refresh=10   --disable_distributed=false   --distributed_plugin=tls   --distributed_interval=3   --distributed_tls_max_attempts=3   --distributed_tls_read_endpoint=/api/v1/osquery/distributed/read   --distributed_tls_write_endpoint=/api/v1/osquery/distributed/write   --logger_plugin=tls,kafka_producer   --logger_tls_endpoint=/api/v1/osquery/log   --logger_tls_period=10   --logger_kafka_brokers="-----------:9091"   --logger_kafka_topic="demo-osqueryd"   --logger_kafka_compression="none"   --logger_kafka_acks="all"
but its not reading from
What did you see instead?

If you want the osquery nodes to write to Kafka, you need to set up Fleet to provide them the appropriate configuration.
If you want Fleet to collect the logs and then push to Kafka from the Fleet server, you'll need some forwarding agent on the Fleet server.


Offline install?

Is there a way to install nltk without needing access to the internet? Running python setup.py build starts immediately by attempting to download stuff from pypi, but I need to be able to control what it's downloading -- more accurately, I want to have something with which I can install nltk in an environment without internet access at all.

@adnelson this is not strictly an NLTK issue, but a setuptools issue, and so I think you need to look into the documentation for setuptools to see if there's a solution. You can't be the first person to have this requirement. One thought I had was for you to do an install on an untouched python distribution, note all the dependencies, then create a collection of packages that need to be installed before attempting to install NLTK (by which time there will be no unsatisfied dependencies).

@adnelson @stevenbird There are a number of Docker images for NLTK, e.g., https://registry.hub.docker.com/u/horkfnado/python-nltk/. One of these might be the way to go. Maybe we should think about producing an official NLTK Docker image.


Microsoft Edge 91+ supports JPEG-XL

I couldn't find any official source but I have confirmed that Microsoft Edge Beta, Dev, and Canary (91+) support JPEG XL format. To enable it, you need to run the executable file with the parameter --enable-features=JXL.
https://caniuse.com/jpegxl

I have tested and can confirm that setting the runtime flag on Edge beta 91+ on Windows and Ubuntu works. Nice catch!
I guess it's easiest to just keep this issue open and have Fyrd add this note when he adds Edge 91 to the support table :)


unable to resize chat after update dom with chartjs 2.7

It works on chartjs 2.6 but DOSE NOT on 2.7.
Could you fix this?
Here is my js code.
class DataSet extends React.Component {
  ...

  const data = {
   labels = ["aaa", "bbb", "ccc"];
   datasets = [
     { label: "xxxx", backgroundColor: "xxx", data: [...], ... },
     { label: "yyyy", backgroundColor: "yyy", data: [...], ... },
     { label: "xxxx", backgroundColor: "xxx", data: [...], ... },
   ]
  }

  const options = {
    responsive: true,
    ...
  }

  render() {
    return(<PowerMonitorGraph data={data} options={options} />)
  }
}

class PowerMonitorGraph extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      data: this.props.data,
      options: this.props.options
    }
  }

  componentWillReceiveProps(props) {
    if (props.data !== this.state.data) {
      this.setState({data: props.data});
    }
    if (props.options !== this.state.options) {
      this.setState({options: props.options});
    }
  }

  render() {
    return (
      <Line data={this.props.data} options={this.props.options} redraw={true}/>
    )
  }
}

And then here is debug.
After first rending,it works fine.

<canvas height="422" width="844" class="chartjs-render-monitor" style="display: block; width: 844px; height: 422px;"></canvas>

After update dom, resize does't work.
<canvas height="422" width="844" class="chartjs-render-monitor" style="display: block; width: 844px; height: 422px;"></canvas>

I'm having the same problem with chartjs v2.7.0

I'm not certain about what you're asking.  Can you try to be a little more clear about your question?
You want the chart to resize and fit its container after the container resizes ? I was able to make that work.

I want to get graph to switch between daily data and weekly data.
The graph which displays daily data default prints well,and resize works too.
When switch to weekly data,printing still works,but resize DOES NOT.

I have a similar problem, chart will resize it's width, but the height will never change.  Is there ANY example showing how to make a chart resize properly when it's parent resizes?

I am facing the same issue, any suggestions?

I do not care about this anymore.
so, I close this.


where to find every module's checkpoint_best.pth?

I am wondering if you could kindly send me the pretrained modules for 3D CNN and the necessary information about it. I promise they will be only used for research. Thank you very much for your kind consideration and I am looking forward to your early reply.

1、where to find .pth files
All the checkpoint files are saved in this folder: ".saved",
For example, if you run the code at "/home/haha/" in 13th February， 11:47am,
you will find your files here:
'/home/haha/saved/resnet18/0213_114719/checkpoint_best.pth'
2、pretrained models
I did not train all the models in my codes, but these 3D pretrained models may helps you:
https://github.com/kenshohara/3D-ResNets-PyTorch


Workflow files for static checking

Adds static checking workflow files
Fixed small errors raised by clippy

Let me know your thoughts!

Thanks a lot @wdoppenberg  for your contribution! I'll take a look at this workflow


Operators application channel

@Kelvin-M

Tested locally with 2 orgs: :heavy_check_mark:
with 3 orgs: it fails when adding the 3rd org to the application channel:

[DEBUG Send application channel update for MyOrg3
go package net: GODEBUG setting forcing use of Go's resolver
2020-04-21 23:32:21.437 UTC [channelCmd InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'mychannel': error authorizing update: error validating DeltaSet: policy for [Group  /Channel/Application not satisfied: implicit policy evaluation failed - 1 sub-policies were satisfied, but this policy requires 2 of the 'Admins' sub-policies to be satisfied

@Kelvin-M

Tested locally with 2 orgs: ✔
with 3 orgs: it fails when adding the 3rd org to the application channel:

[DEBUG Send application channel update for MyOrg3
go package net: GODEBUG setting forcing use of Go's resolver
2020-04-21 23:32:21.437 UTC [channelCmd InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'mychannel': error authorizing update: error validating DeltaSet: policy for [Group  /Channel/Application not satisfied: implicit policy evaluation failed - 1 sub-policies were satisfied, but this policy requires 2 of the 'Admins' sub-policies to be satisfied

Yes, as we discussed, we should have a proposal signature strategy :)


Problems with the update

I have problems updating Championify, try everything and keep telling me the same thing. Help please, thank you very much

@Reythomas Try opening Championify as an admin and see if it updates correctly. I usually see that error some with antivirus trying to block the update.

Seeing as I have the same problem, I decided to reply to you in this thread rather than opening a new one.
I have tried
-Running it as an admin
-Disabling all my active antivirus programs
-Allowing championify on firewall
-Disabling my firewall.
-Restarting my PC
None of those or a combination of those worked
Any help would be appreciated, thanks!


Button won't disappear when last page has been loaded

Live URL: http://ilovechrisbaker.com/
First, thank you for fixing the last issue with the status. Another issue I found is when using even to show and hide button. The last even not working in my case. Please check the Live URL, the console log message appeared but the button won't disappear. Here's my code:
$container = $( '.selected-projects' );

$container.infiniteScroll( {
	path: '.page-numbers .next',
	append: 'article.entry',
	scrollThreshold: false,
	status: '.page-load-status',
	history: false,
	checkLastPage: true
} );

var $viewMoreButton = $( '.more-projects' );
$viewMoreButton.on( 'click', function() {
	$container.infiniteScroll( 'loadNextPage' );
} );

$container.on( 'request.infiniteScroll', function( event, path ) {
	$viewMoreButton.hide();
} );

$container.on( 'append.infiniteScroll', function( event, response, path, items ) {
	$viewMoreButton.show();
	responsiveVideo();
} );

$container.on( 'last.infiniteScroll', function( event, response, path ) {
	$viewMoreButton.hide();
	console.log( 'Last!' );
} );

Thanks for reporting this issue. Looks like Infinite Scroll is not currently working on your site.
chrisbaker.min.js:1 Bad InfiniteScroll path option. Next link not found: .next a
r.updateGetPathSelector @ chrisbaker.min.js:1
chrisbaker.min.js:1 Disabling InfiniteScroll

Hi @desandro, please ignore the error message and please try the Load More Projects button.

This is likely caused by a race condition where last event is triggered before the final append event. You can resolve this by adding a flag in your code.
var isLast = false;

$container.on( 'append.infiniteScroll', function( event, response, path, items ) {
	if ( !isLast ) {
		$viewMoreButton.show();
	}
	responsiveVideo();
} );

$container.on( 'last.infiniteScroll', function( event, response, path ) {
	$viewMoreButton.hide();
	isLast = true;
	console.log( 'Last!' );
} );

Nice, it is working. Thanks a lot, @desandro :)


Modifier form arguments should only use a single line

In the past I have seen quite a few occurences of if and unless being used in their modifier form, but then stretching across multiple lines.
I always found this quite irritating and I feel, that the modifier form is only "intended" for single line use.
Though, as many things in rubocop, this is probably opionionated and there might be valid cases that I don't see...

Expected behavior
The following code sample raises a Style/* offense:
foo if bar.baz
          .boom

Actual behavior
It reports no offense.
Steps to reproduce the problem
Inspect the code sample above using rubocop.
RuboCop version
$ rubocop -V
0.49.1 (using Parser <IP_ADDRESS>, running on ruby 2.4.1 x86_64-linux)

There hasn't been much activity on this ticket and our Core Team is spread too thin on so many tasks, so I'll just close it for the sake of having a cleaner lists of tasks to focus on. We'd gladly review a PR, but it's unlikely that'd we're going to tackle this ourselves in the foreseeable future.


Fail to compile Vue Storefront in docker

Current behavior

I followed the document https://docs.vuestorefront.io/guide/cookbook/setup.html#_2-recipe to run the vue storefront on local computer.
At step 11, after running the
docker-compose up -d

The http://localhost:3000 has no return.
The docker log shows the following compile errors:
... ...
app_1  | Entrypoint app = manifest.js manifest.js.map vendor.js vendor.js.map app.js app.js.map
app_1  | [0] multi webpack-hot-middleware/client @babel/polyfill ./core/client-entry.ts 52 bytes {app} [built]
app_1  | [./core/app.ts] 8.36 KiB {app} [built]
app_1  | [./core/build/config.json] 15.9 KiB {app} [built]
app_1  | [./core/client-entry.ts] 9.62 KiB {app} [built]
app_1  | [./core/hooks.ts] 1.94 KiB {app} [built]
app_1  | [./core/i18n/index.ts] 6.36 KiB {app} [built]
app_1  | [./core/lib/async-data-loader.ts] 1.21 KiB {app} [built]
app_1  | [./core/lib/logger.ts] 9.35 KiB {app} [built]
app_1  | [./core/lib/multistore.ts] 12.4 KiB {app} [built] [1 error]
app_1  | [./core/lib/router-manager.ts] 5.65 KiB {app} [built]
app_1  | [./core/lib/storeCodeFromRoute.ts] 2.21 KiB {app} [built]
app_1  | [./core/lib/sync/task.ts] 15.9 KiB {app} [built]
app_1  | [./core/modules/offline-order/helpers/onNetworkStatusChange.ts] 1.36 KiB {app} [built]
app_1  |<EMAIL_ADDRESS>686 bytes {vendor} [built]
app_1  | [./node_modules/webpack-hot-middleware/client.js] (webpack)-hot-middleware/client.js 7.68 KiB {vendor} [built]
app_1  |     + 2228 hidden modules
app_1  |
app_1  | ERROR in /var/www/core/lib/multistore.ts
app_1  | ./core/lib/multistore.ts
app_1  | [tsl] ERROR in /var/www/core/lib/multistore.ts(153,43)
app_1  |       TS2345: Argument of type '{ [key: string]: unknown; }' is not assignable to parameter of type 'Record<string, string | number | boolean | (string | number | boolean)[]>'.
app_1  |   Index signatures are incompatible.
app_1  |     Type 'unknown' is not assignable to type 'string | number | boolean | (string | number | boolean)[]'.
app_1  |       Type '{}' is missing the following properties from type '(string | number | boolean)[]': length, pop, push, concat, and 26 more.
app_1  |
app_1  | ERROR in /var/www/core/lib/search/adapter/api/searchAdapter.ts
app_1  | ./core/lib/search/adapter/api/searchAdapter.ts
app_1  | [tsl] ERROR in /var/www/core/lib/search/adapter/api/searchAdapter.ts(76,45)
app_1  |       TS2345: Argument of type 'HttpQuery' is not assignable to parameter of type 'Record<string, string | number | boolean | (string | number | boolean)[]>'.
app_1  |   Index signature is missing in type 'HttpQuery'.
app_1  |
app_1  | ERROR in /var/www/core/lib/search/adapter/api-search-query/searchAdapter.ts
app_1  | ./core/lib/search/adapter/api-search-query/searchAdapter.ts
app_1  | [tsl] ERROR in /var/www/core/lib/search/adapter/api-search-query/searchAdapter.ts(84,45)
app_1  |       TS2345: Argument of type 'HttpQuery' is not assignable to parameter of type 'Record<string, string | number | boolean | (string | number | boolean)[]>'.
app_1  | Child html-webpack-plugin for "index.amp.html":
app_1  |              Asset     Size  Chunks  Chunk Names
app_1  |     index.amp.html  535 KiB       0
app_1  |     Entrypoint undefined = index.amp.html
app_1  |     [./node_modules/html-webpack-plugin/lib/loader.js!./src/index.amp.template.html] 660 bytes {0} [built]
app_1  |     [./node_modules/lodash/lodash.js] 528 KiB {0} [built]
app_1  |     [./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {0} [built]
app_1  |     [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
app_1  | Child html-webpack-plugin for "index.basic.html":
app_1  |                Asset     Size  Chunks  Chunk Names
app_1  |     index.basic.html  535 KiB       0
app_1  |     Entrypoint undefined = index.basic.html
app_1  |     [./node_modules/html-webpack-plugin/lib/loader.js!./src/themes/default/templates/index.basic.template.html] 723 bytes {0} [built]
app_1  |     [./node_modules/lodash/lodash.js] 528 KiB {0} [built]
app_1  |     [./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {0} [built]
app_1  |     [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
app_1  | Child html-webpack-plugin for "index.html":
app_1  |          Asset     Size  Chunks  Chunk Names
app_1  |     index.html  535 KiB       0
app_1  |     Entrypoint undefined = index.html
app_1  |     [./node_modules/html-webpack-plugin/lib/loader.js!./src/themes/default/templates/index.template.html] 853 bytes {0} [built]
app_1  |     [./node_modules/lodash/lodash.js] 528 KiB {0} [built]
app_1  |     [./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {0} [built]
app_1  |     [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
app_1  | Child html-webpack-plugin for "index.minimal.html":
app_1  |                  Asset     Size  Chunks  Chunk Names
app_1  |     index.minimal.html  535 KiB       0
app_1  |     Entrypoint undefined = index.minimal.html
app_1  |     [./node_modules/html-webpack-plugin/lib/loader.js!./src/themes/default/templates/index.minimal.template.html] 697 bytes {0} [built]
app_1  |     [./node_modules/lodash/lodash.js] 528 KiB {0} [built]
app_1  |     [./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {0} [built]
app_1  |     [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
app_1  | ℹ ｢wdm｣: Failed to compile.

How can I solve it? It seems to relate to the default settings.
Thanks
Expected behavior

Steps to reproduce the issue

I followed the steps in the document except in step 7 I chose the latest one, the version 1.12.2.
Version of Vue Storefront

[X] Vue Storefront
In the package.json, the version information is:
"name": "vue-storefront",
"version": "1.12.2",
[ ] Vue Storefront Next

Can you handle fixing this bug by yourself?

[ ] YES
[X] NO

Which Release Cycle state this refers to? Info for developer. (doesn't apply to Next)
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser:
Chrome/Firefox
OS:
Mac version 10.15.6
Node:
Code Version:
Docker Version: <IP_ADDRESS>

Additional information

@cartooncatfish  You can look in #4951

Recently, @AdamPawlinski had this problem and he says reinstalling project solved it.
In my opinion, in case of docker you might want to add:
- './yarn.lock:/var/www/yarn.lock'

To the docker-compose's volumes part.

solved by #4951


add feature about locking particular folder

Description of the new feature / enhancement
add a feature with help of it we can lock particular folder with password so that some important file can be secure on our pc like there is a folder of images so that whole folder can be locked with password
Scenario when this would be used?
storing important file , photoes , pdf , videos etc....
Supporting information
storing important file , photoes , pdf , videos etc....

Not planned for PowerToys.
Refer to https://github.com/microsoft/PowerToys/issues/21759#issuecomment-1304392992


Connection using oauth token

Description
Connection using oauth token
oauth token refresh when expired
possibility to notify the calling code when the oauth token is refreshed. In case the calling code needs to propagate the token among several nodes.
other modifications:

removed use of system-wide properties
OAuthApi is now fully static: the reason is that all the endpoints are static and no credentials are needed to call those endpoints

PR Checklist

[ ] Added help
[ ] Added unit test/s
[ ] Updated Change log

@jfbaraton, getAuthorizationEndpoint() method constructs and returns the oauth endpoint and it will not actually send any request to the Api. Based on the resource area id the url is constructed. If you remove the url "https://app.vssps.visualstudio.com" from Client class then it breaks the AccountsApi also as it uses the same url.
Organization name shouldn't be null as all the url requires it, hence the validation is placed in getLocationUrl() method in Client.java class. I have modified the logic to return "https://app.vssps.visualstudio.com" if the resource area id is oauth.
If there are any breaking changes in Connection.java class then it affects the entire library as all the classes depend on it. We have to find another way to refresh the token.
OAuth class should be self contained that handles all this logic.

@hkarthik7
no connection object should be needed to call
getAuthorizationEndpoint
getAccessToken
getRefreshToken
because

you don't need any token to call them (you are not supposed to already have one)
you don't need to specify any account name/ organization name. Those endpoints/urls don't contain nor depend on organization.

therefore

I made those methods static
I changed the way the POST is being sent.

I am OK to change back the way the POST are being sent, and to use again org.azd.utils.Client.send
but at the moment it blows if you don't provide a CONNECTION parameter.
do you want to change org.azd.utils.Client.send so that it works without passing a CONNECTION ?
note: for me AccountsApi is still working: I use both
api.getAccountsApi().getProfile().getId();
api.getAccountsApi().getAccounts(userDevOpsId);
and i don't have any problem

@jfbaraton I took a look the code in the branch and I'm clear now. What you said makes sense and we're not making changes to the properties in Connection class rather we're using it as a medium to refresh the token automatically. I can also see that you haven't removed the AccountsApi url. My concern is that we're duplicating the url, we can retrieve getLocationUrl() method rather than hardcoding it in the OAuthApi and using within it.
Did the "Content-Length" worked for POST request after commenting it out in BaseClient?
Rest all LGTM(Looks good to me).


build with openssl then test_crypt.exe test fail

Verified on https://github.com/DMTF/libspdm/commit/3ff968553368dd5517ca8143cc620f48c66e65f3
For x64 builds, use a x64 Native Tools Command Prompt for Visual Studio... command prompt.
cd libspdm
mkdir build_x64_Release_openssl
cd build_x64_Release_openssl
cmake -G"NMake Makefiles" -DARCH=x64 -DTOOLCHAIN=VS2019 -DTARGET=Release -DCRYPTO=openssl ..
nmake copy_sample_key
nmake
cd bin
test_crypt.exe > test_crypt.log
There is the following fail information in "test_crypt.log".
Line 29: - SM4-GCM Encryption: [Fail]
Line 158: - Context1 ... [Fail]

SM4-GCM is not supported. It is known issue.


Add support for passing commandline arguments to the Godot Engine

Is your feature request related to a problem? Please describe.
I Have a rather low-end device, which doesn't support Vulkan, so I have to use the OpenGL3 rendering driver. As a result, I must execute the engine with the command line argument --rendering-driver opengl3, which prevents me from using the Godot Manager correctly.
Describe the solution you'd like
Each engine version installed should have a settings page, where it will be possible to edit it's command line arguments (The settings page might include other settings in the future, if necessary).
An alternative is to use the current settings of each project, and add the requested command line arguments there. Though I am not sure which is more common - changing the command line arguments per project or per Godot version.
Describe alternatives you've considered
I was able to launch the project correctly by replacing the Godot version with a bat script that executes the engine with the correct arguments, but it is an ugly solution
Additional context
Not relevant

By the way, I can create a PR solving this issue when I have time, if needed.

It sounds like your using the Godot 4 branch of the project, as the released version, 0.2.3, is set to use OpenGL already.  Godot 0.3.0 will be set for OpenGL rendering to allow the most coverage for usage of the manager itself, before release.

I am actually using the 0.2.3 version of the manager (I downloaded the prebuilt version). I wasn't talking about the manager itself using Vulkan by default, but rather engine versions 4+ (that the manager installs). For example, I tried downloading Godot version 4.2-rc 2, and running an example project with it, but I failed because the default driver is Vulkan.

Ah, Ok, Now I see what you are talking about.  I will see about adding a Setting to the Project Settings dialog to switch the engine from Vulkan to OpenGL, as it would be a project setting that would be set.

Oh, I wasn't talking about the project settings (which now that I think about it, is also lacking the OpenGL renderer option, but that is ). I was talking about the rendering driver that the editor itself is using, which is Vulkan by default. To illustrate, upon opening a project, even one that is using the OpenGL rendering driver in the project settings, I get the following, well-known error:

Yes, well, the reason why I was suggesting making it a Project setting, is cause the Editor will use the setting from project.godot to determine which rendering driver to use.  So if you set it to GL Compatible, the editor will automatically launch using the OpenGL3 Renderer, instead of the Vulkan Renderer.  The setting in the project.godot is
[rendering]
renderer/rendering_method="gl_compatibility"


Add Completion result and task type to the Inference API spec

This PR adds the new completion task type and the result to the specification.
Completion result example:
{
  "completion": [
     {
       "result": "..."
      }
   ]
}

Closed for non-fork PR: https://github.com/elastic/elasticsearch-specification/pull/2471


Upgrade pxt-common-pkgs

You really want https://github.com/Microsoft/pxt/pull/5108#merged-event

Otherwise blocks are broken.


Fix flakiness in query-retry ITs

Possible fix for flakiness in query-retry ITs as explained in #12700
Tested by running locally ~ 50 times with an automation, all the runs pass.
This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] added integration tests.
[ ] been tested in a test Druid cluster.

@rohangarg, thanks for fixing this flaky test! Thanks also for your detailed analysis. From prior observations, and based on your analysis, here's my guess as to what was happening. We spin up the Docker cluster and then start tests. The current ITs don't check the status of the cluster before they run: they simply rely on the retry utility to handle any failures.
I've noticed that, on a single machine, it can take significant time for the cluster to come up. The "new ITs" specifically check the health of each service before starting the tests, and I've seen that this can take a while.
So, in the scenario you describe, it may be that the good historical comes up and serves the 50 queries before the bad one has had a chance to get itself organized. So, an alternative fix would have been to check the health of all services before running the tests.
Still, that leaves the statistical nature of the failure detection, which is unappealing. The deterministic mechanism you implemented seems much better.
One suggestion: please add your explanation of the new behavior to the test code itself as a comment. I had a hard time figuring out what the code was doing until I read your explanation, which cleared thing right up. Would be great to preserve that explanation for future readers of the code.

@paul-rogers : Thanks a lot for review and the feedback!

We spin up the Docker cluster and then start tests. The current ITs don't check the status of the cluster before they run: they simply rely on the retry utility to handle any failures.
I've noticed that, on a single machine, it can take significant time for the cluster to come up. The "new ITs" specifically check the health of each service before starting the tests, and I've seen that this can take a while.
So, in the scenario you describe, it may be that the good historical comes up and serves the 50 queries before the bad one has had a chance to get itself organized.

Yes, that's what my conjecture was too regarding the flakiness. The current test only has some application level checks which acts as a proxy for test setup valdiation too, which seems a bit shaky. The delay in test setups due to load on CI is probably the reason I can't reproduce it locally. Great to know that the new framework has first class support for test setup check!

So, an alternative fix would have been to check the health of all services before running the tests.
Still, that leaves the statistical nature of the failure detection, which is unappealing. The deterministic mechanism you implemented seems much better.

Yes, I had thought of that approach but didn't move in that direction unless we have a good reason. Seemed better to me to make the test verify only the query-retry mechanism on the bad historical.

One suggestion: please add your explanation of the new behavior to the test code itself as a comment. I had a hard time figuring out what the code was doing until I read your explanation, which cleared thing right up. Would be great to preserve that explanation for future readers of the code.

Yes, totally agree with you. I have added more explanation to the existing code documentation in the test and also updated some of it which has become outdated after the re-write. Thanks for catching that!

Thanks for the review @paul-rogers and @clintropolis!
I also ran the test via Travis multiple times and the runs were successful


auto deploy

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_nodejs_express.html


SDI support?

Feature request (or wondering out loud), could it be possible to support SDI ?

The repository is called PicoDVI, so no, SDI video won't be implemented here.


Editor won't auto-scroll to keep the cursor in view after copy-pasting something

Do you want to request a feature or report a bug?
bug
What is the current behavior?
If I copy-paste something, the view stays and doesn't scroll to keep the caret in the view
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/gmertk/e61z7nfa/.

What is the expected behavior?
Editor should auto-scroll so that the cursor/caret is visible .
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft version - 0.11.2
Browser - Chrome
OS - Windows
It didn't work in previous versions either.

I am having same issue by just using 'Enter' key. Notice the scroll doesn't scroll to the next line.

Is anyone looking into this issue?
-cc @mrkev

I have the "opposite" issue on Safari 14 on macOS Catalina.
Pasting content takes the cursor straight to the bottom, while scrolling the content as well to show the cursor.
This is also not ideal since you kind of loose track of where you pasted your content, and every time you paste you need to scroll back somewhere.

No one is, afaik

Same issue here. Any luck with finding a solution?


[SNMP] Add profile for Huawei access controllers

What does this PR do?
Add profile for Huawei access controllers
Final Huawei profile structure :

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

@NouhaManai96 Wanted to make _huawei.yaml as generic as possible, so that in the future if we have a Huawei profile that does not extend _generic_if.yaml we can still use it. Not sure it's the best option, WDYT ?

@NouhaManai96 Wanted to make _huawei.yaml as generic as possible, so that in the future if we have a Huawei profile that does not extend _generic_if.yaml we can still use it. Not sure it's the best option, WDYT ?

@TCheruy I see your point. We don't have specific guidelines for this yet so there's no wrong or right answer here, but since the huawei-all-devices.yaml/huawei.yaml extends _generic-if.yaml, I think it's safe to assume all the other devices would extend it as well

@NouhaManai96 Okay! Updating the schema and profiles

@NouhaManai96 Unfortunately, Huawei access controllers does not expose metrics collected in huawei.yaml

@NouhaManai96 Unfortunately, Huawei access controllers does not expose metrics collected in huawei.yaml

@TCheruy how so ?
from what I see both huawei.yaml and huawei-access-controllers.yaml only extend _huawei.yaml

@NouhaManai96 huawei.yaml cannot be extend by huawei-access-controllers.yaml because of the metrics it contains, that's why I've moved vendor metadata to a new _huawei.yaml so that both huawei.yaml and huawei-access-controllers.yaml can extend it.
Are you suggesting moving back vendor metadata to huawei.yaml and also adding it to huawei-access-controllers.yaml ?

@NouhaManai96 huawei.yaml cannot be extend by huawei-access-controllers.yaml because of the metrics it contains, that's why I've moved vendor metadata to a new _huawei.yaml so that both huawei.yaml and huawei-access-controllers.yaml can extend it. Are you suggesting moving back vendor metadata to huawei.yaml and also adding it to huawei-access-controllers.yaml ?

both solutions are possible, I'll let you decide what you prefer !

I'd say let's keep _huawei.yaml, there is a whole lot of Huawei MIBs and they are adding / dropping them frequently, might be easier in the future to have a vendor metadata only profile.


Changed ReactOnRails::Controller#redux_store API

2nd parameter of props with default value of { } is changed to a named
parameter props with a default value of { }
Needed for consistency with the view helper redux_store API.

This change is

@seoyoochan Please review!


Can you make this swipe-enabled for mobile?

That would be cool :)

That would also be cool for desktop, where I'm used to dragging the images to scroll. Same as Flickity slider.


It doesn't take snapshots at all.

Below is the content of /etc/zfssnapmanager.cfg
[user-data/data]
mountpoint = /mnt/data
time = 03:00
snapshot = True
schema = 7d0w0m0y

The output of zfs list
# zfs list
NAME             USED  AVAIL  REFER  MOUNTPOINT
user-data       1.07T  1.61T    96K  none
user-data/data  1.07T  1.61T  1.07T  /mnt/data

The output of systemctl status zfs-snap-manager
# systemctl status zfs-snap-manager
● zfs-snap-manager.service - ZFS Snapshot Manager
   Loaded: loaded (/usr/lib/systemd/system/zfs-snap-manager.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2015-01-30 16:58:14 KST; 4min 32s ago
  Process: 450 ExecStop=/usr/lib/zfs-snap-manager/manager.py stop (code=exited, status=0/SUCCESS)
 Main PID: 455 (manager.py)
   CGroup: /system.slice/zfs-snap-manager.service
           └─455 /usr/bin/python2 /usr/lib/zfs-snap-manager/manager.py start

Jan 30 16:58:14 arch-server systemd[1]: Started ZFS Snapshot Manager.

It should take a snapshot everyday, but it hasn't taken a single snapshot so far.
What is wrong?

Can you post the contents  of /var/log/zfs-snap-manager.log and the output of zfs list -t snapshot? You can put it on pastie.org and post the link here as there might be quite some data.

# cat /var/log/zfs-snap-manager.log
2014-12-27 15:00:04,941 - Starting up
2014-12-28 13:05:11,878 - Starting up
2014-12-28 20:19:35,208 - Starting up
2014-12-29 09:16:57,313 - Starting up
2014-12-29 09:46:51,187 - Starting up
2014-12-30 10:11:12,227 - Starting up
2015-01-04 10:29:01,325 - Starting up
2015-01-05 07:05:39,354 - Starting up
2015-01-05 09:25:04,364 - Starting up
2015-01-11 08:56:11,374 - Starting up
2015-01-11 09:10:56,869 - Starting up
2015-01-11 17:50:34,224 - Starting up
2015-01-12 00:11:43,160 - Starting up
2015-01-12 00:21:40,371 - Starting up
2015-01-12 00:29:39,269 - Starting up
2015-01-23 23:05:14,696 - Starting up
2015-01-28 18:14:19,415 - Starting up
2015-01-30 16:58:14,073 - Starting up

# zfs list -t snapshot
no datasets available

That's odd, I have no clue yet what's going on. Mind to give me the output of zfs list -H -s creation -t snapshot and zfs list -H?

zfs list -H -s creation -t snapshot prints nothing.
# zfs list -H
user-data	1.07T	1.61T	96K	none
user-data/data	1.07T	1.61T	1.07T	/mnt/data

I've reproduced the issue and I'm working on a fix. I hope I can release somewhere this weekend. I'll keep you posted with progress.

Issue found and fixed. I'm now going to apply changes to my systems and let it run for a while to make sure there are no other issues popping up.

What were the issue and the fix?

In the Helper.py, there's a function run_command(command, cwd), that has some boilerplate code for running commands and stripping out unwanted characters. At this moment, I can't completely remember what characters were causing problems in the first place, but anyway, a dash (-) is obviously not at bad character.
The script was fetching your dataset as userdata instead of user-data causing it to think it had to be skipped because [userdata] isn't in your configuration file. It would give tons of issues on other places as well because, well, it's just not what your dataset is named.

Thanks...


⚠ Bofrost.be has degraded performance

In b93c736, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2659 ms

Resolved: Bofrost.be performance has improved in e5a3d90.


Concurrency usage of client returned by NewStatsdBuffer

@quipo Can StatsdBuffer be used concurrently. Like in a production scenario if we create one instance of StatsdBuffer and use it across the code till the program exists, is it fine?

I'm also curious about this.
Moving from default to buffered client introduced data races for us. @quipo any advice on the usage of the buffered client?

I always instantiate a new buffered client from within each goroutine. Unfortunately the collector isn't thread safe.


Random fixes

Some random fixes (mainly for metamodeling on the fly) from 239

Current coverage is 27.27% (diff: 100%)

Merging #1751 into master will increase coverage by 0.22%

@@             master      #1751   diff @@
==========================================
  Files          1965       1967     +2
  Lines         81185      81842   +657
  Methods       13758      13933   +175
  Messages          0          0
  Branches       1249       1249
==========================================
+ Hits          21958      22321   +363
- Misses        59150      59444   +294
  Partials         77         77

Powered by Codecov. Last update 15399dd...f1acd59


Major refactor

@RobMeades Hi Rob, please review this. Please let me know of your views and insights.

@RobMeades In my humble opion, SystemInit() is the right place to call initialization stuff. The STM fashion has been to poke register directly, but I think we can do better with ublox_mdm* APIs (clarity is an added value with your APIs).  ublox_mdm_init() will be called from systemInit() and our recent changes will make sure that we do not have any effect of zeroing out variables on our stuff.
Target labels are key words to tell the build system that my specific target, e.g., UBLOX_C030 needs certain target modules located at various places. Consider this as an example. Say we have a label STM, which would mean that my target belongs to a family called STM so include stuff from that directory. Another label STM32F would pin us down to F4 family. UBLOX_MODEM is also a label like the ones described before. However, location of TARGET_UBLOX_MODEM is inside 'cellular' directory. When we define our target say 'UBLOX_C030', build system looks for the labels and gathers the stuff we need, e.g., things from TARGET_STM32F4 directory (label was STM32F4), things from TARGET_UBLOX_MODEM (label was UBLOX_MODEM) which happens to exist in a different location inside the tree.

Modem driver that will be fetched using UBLOX_MODEM label, is shared between C027 and C030.
We don't need to do ifdef in the driver until unless we have common ublox_mdm_* APIs.
I have tested stuff with C027 with tis configuration. I think you can test with C030. Only thing remaining in 'todo' is to actually call ublox_mdm_init() from SystemInit() for C030.

Oh, I see, I'd not spotted that this is now a common Celllular API driver to all u-blox modems on both board types.  I think that's a good step, but it does raise the question of regression test because now any change I make on C030 can have an adverse effect on C027.  I don't actually have a proper C027 (just a variant of my own) and there are none in the ARM CI system.  We desperately need to fix that.
I don't understand what you mean by "do not have any effect of zeroing out variables on our stuff".  What change have you made to prevent variables being zeroed after the call to SystemInit() on STM platforms?
On more thing: is there a reason for the ugly "goto" and the like in the Cellular driver?  It is somewhat unconventional code for no reason that I can see, and I was planning to not have it that way in the C030 driver.

@RobMeades :) gotos are fine if handled with care especially in error cases. However, if you don't like that style please go ahead and replace according to your taste. Its our driver, not only mine :D ..
in ublox_low_level_api, you can see that we have removed static variables which were being used inside the functions. These variables were getting zeroed out after systemInit() because of _start function.  I did changed the behaviour for C027 case but I left ublox_low_level_api for C030 partially done. My mistake. Please go ahead and change the ublox_low_level_api inside TARGET_UBLOX_C030 according to the one in TARGET_UBLOX_C027. Actually I can do it for you as I started this thread. Then you can add or remove stuff as you please.

I prefer to stay away from unusual constructs, keep my code boring, tell stories in comments, that kinda guy, mostly 'cos I can never remember one week what code crimes I committed the previous week :-).
Understood on the removal of the static variables.  Shall I press the merge button, or will you?

You can. I think you can gothrough the ublox_low_level_api code in TARGET_UBLOX_C030 also better than me. As I am not sure how the hardware is wired up.
Point take, I will try to use normal construct in my feature branch with unusually detailed stories :) . by the way I took the liberty to cherry-pick this commit on top of my feature branch. We are soon going to start (epochs long:D, world war like) merge process to master for my feature branch.
For the CI, I am pulling all the stringswithing my reach from the confines of my desk ofcourse to kick start a cellular-minimal-example which would run in our testing harness with just bringing up the network, i.e., a minimal test to mark health of the platform. Unfortunately, despite my valiant efforts, I could not fit our full testing harness app for C027 because of limited RAM (I can only play with 32K). Solutions to steal at least 16K of RAM from ethernet were proven to be futile as they were not portable. :( I hope you understand. Somebody needs to sit down and make the memory map automatic.

Button pressed.  I'll give it a go on my C030 board next (I've borrowed one that has a working modem).  Understood on the RAM thing, not too much that can be done there unfortunately, apart from deprecate C027 once C030 is flying off the shelves.

Sounds empowering :) .. Awesome !


Update Directory.Build.props

Arcade now already defines the property.

NetCurrent is in 6.0 and 7.0 arcade as well, will send PRs.


Still active?

Hi @sbinet
Is this repo still active (planned to continue development) or is the https://github.com/gonum/hdf5 the recommended way?
best regards

hi,
yeah... this hasn't seen much activity.
the work is laid out in #1 (with links to the specs and all) - w/o much gotchas I am aware of.
and it may happen that $WORK leads me to (again) want a pure-Go HDF5 library.
but for the time being, gonum/hdf5 is probably the best stopgap solution.

Thx for clarification


check command violates data immutability principle

According to NDN Protocol Design Principle:

Data-Centricity and Data Immutability: NDN should fetch uniquely named, immutable “data packets” requested using “interest packets”.
Data packet immutability allows disambiguation of coordination in distributed system that may not be always connected. Although data packets are immutable, applications can make changes to the communicated content by creating new versions of immutable data packets.

However, CommandChecker._check function is repeatedly sending an Interest with the same name and CanBePrefix=false, expecting to receive a different answer.
This implies that this protocol depends on Data that is not immutable.
https://github.com/JonnyKong/ndn-python-repo/blob/b5aae1bc11bcad8fc881e6692755b108c2eb63b2/ndn_python_repo/clients/command_checker.py#L59-L70

An option is to put the insert check parameter into the application parameter?

Eliminate the check command altogether and use PubSub exclusively?
Each ongoing insertion or deletion has a topic derived from its process id. The repo can periodically publish to this topic, and the client can subscribe if it wants to know the progress.

Eliminate the check command altogether and use PubSub exclusively?

Well, yes, I thought that was the eventual plan, no? Have pubsub completely replace the command-based interface. In that case, I wouldn't bother fixing this bug. Just finish the pubsub implementation and make sure it's stable and well-tested, then drop the commands.

Fixed with https://github.com/JonnyKong/ndn-python-repo/commit/c69df5bda86d14acd90c0a85ddfd7b1f3a2b7e71.


upgrade rustls, pem, tame-oauth, and webpki

These have breaking changes that were found during the last version upgrade in #643.
The relevant backouts that we would like to undo are: https://github.com/kube-rs/kube-rs/pull/643/commits/87eeb01130bbd1a972b8148620f2520651366035 and https://github.com/kube-rs/kube-rs/pull/643/commits/f2890b1e07e1948130e5f469da30aa7a0d371424 .

[ ] breaking changes in rustls - #692
[ ] pem changelog for 1.0 - pretty fresh (but also clearly not many commits)
[ ] webpki git compare - they have no changelog other than git
[ ] tame-oauth changelog for 04.7 to 0.6.0 - they have changed some names of structs and error types, then moved some fns afaikt

Also likely crypto related: we bumped tokio-tungstenite by one minor to 0.15.0, giving us<EMAIL_ADDRESS>(with some ring bump changes).

Going to take a stab at upgrading rustls.

I'll do tame-oauth. I was going to clean up OAuthError next for #688.


manage datasets

First of all thank you for the great work!
Now: I guess if there is any method to toggle visibility of the single dataset in a line chart.
can You help me?
d

I'm looking for same feature. Is that possible to hide/show only one dataset without redraw chart? v1.
Yusuf

should I assume there's no possibility of hiding/showing datasets on the fly??

Duplicate of #689 which is targeted for version 2.


[XLA:GPU] Introduce ReduceRewriter to AMDGPU XLA backend

Changed the following places in TensorFlow:

Introduce ReduceRewriter, ReduceThunk in XLA
Revise LLVM IR emitter to cope with kReduce in custom-call HLO
Adopted ReduceWriter in AMDGPU XLA compiler backend
Add ThenReduce() interface in StreamExecutor
Hook ThenReduce() to DoReduce() in rocm_dnn module
Hook DoReduce() to reduce_thunk_op custom TF op to launch rocPRIM kernels
Relevant bazel script changes

I submitted this PR to see if everything checks out on develop-upstream. We may or may not need to merge this PR as introduces undesirable dependencies changes in bazel scripts.

Can one of the admins verify this patch?


Check failure when building in a clean chroot using a source archive (not Git clone)

My old bug report from Rome is still relevant:
https://github.com/rome/tools/issues/4548
Presumably something is being assumed about the sources being a Git clone instead of being packages from the git archive tarball.
What happened?
cargo check fails.
Expected result
Sources should be self contained so git archive generated tarballs have everything needed to build and test.

Do you still experience the issue? I removed the check of the .git folder.

That does seem to have fixed the issue. For reference of anyone else landing on this from a search here is the PKGBUILD I used for testing:

PKGBUILD
# Maintainer: Caleb Maclennan<EMAIL_ADDRESS># Contributor: pinks <aur at papepati dot page>

# Tests assume Git checkout, not source archive...
# https://github.com/biomejs/biome/issues/336
# BUILDENV+=(!check)
_sha=d53b1dbdfe2e89e47fafd9f6bc51542526eeee8f

pkgname=biome
pkgver=1.2.2
pkgrel=1
pkgdesc='Formatter, linter, and more for Javascript, Typescript, JSON, and CSS'
arch=(x86_64)
url=https://biomejs.dev
license=(MIT)
depends=(gcc-libs
         glibc)
makedepends=(cargo)
replaces=(rome)
# _archive="$pkgname-cli-v$pkgver"
# source=("https://github.com/biomejs/biome/archive/cli/v$pkgver/$_archive.tar.gz")
_archive="$pkgname-$_sha"
source=("https://github.com/biomejs/biome/archive/$_sha/$_archive.tar.gz")
sha256sums=('87ec0f701e55bc4acf1d0d2b0cb67c340563f4be1b126a7dac061c39d96b1c69')

prepare() {
	cd "$_archive/crates/${pkgname}_cli"
	cargo fetch --locked --target "$CARCH-unknown-linux-gnu"
}

build() {
	cd "$_archive"
	export RUSTUP_TOOLCHAIN=stable
	export CARGO_TARGET_DIR=target
	CFLAGS+=' -ffat-lto-objects'
	cargo build -p "${pkgname}_cli"  --frozen --release --all-features
}

check() {
	cd "$_archive"
	export RUSTUP_TOOLCHAIN=stable
	cargo test -p "${pkgname}_cli" --frozen --all-features
}

package() {
	cd "$_archive"
	install -Dm0755 -t "$pkgdir/usr/bin/" "target/release/$pkgname"
	install -Dm0644 -t "$pkgdir/usr/share/licenses/$pkgname/" LICENSE
}

That build d53b1dbdfe2e89e47fafd9f6bc51542526eeee8f and it seems to work with official Arch build tooling (that builds in a clean chroot with only the specified dependencies) and passes the check() phase.


Issue #74

#74
Please don't delete my branch after merging.

Perhaps we could make the command something like /porty %d or /portx %d for quality of life, or add the option at least.


Moving Traject from orangeindex, adding Solr view of bib records

I'm :+1: but I think @tampakis should take a look as well. Let's put a deprecation note in the orangeindex README for now too, rather than just wiping it out. That way if anything was missed or broken...

Looks good to me


Support for Electron v9 ?

I believe this package breaks in v9.  addDevToolsExtension is removed , session.loadExtension is now the proper method.  Just wanted to know if you have plans to update ?

I’m gonna check it out. Hopefully it’s an easy fix.

I’m gonna check it out. Hopefully it’s an easy fix.

Just going to also point out this open ticket.  This is for loading react-tools by the path to the chrome extensions.   Thank you!
Electron-#23662

Thanks for pointing out that issue! I followed the docs but couldn't get it to work, hopefully there's a solution soon.

@dimitarnestorov in electron 12 there is a new api: targetSession.loadExtension(extensionPath, { allowFileAccess: true })
I believe using it should fix it. I tried building this package/repo, but I ran into multiple problems, maybe you could add some documentation on how to get from this repo's source-code to the npm package.

My workaround:
const reactDevToolsPath = path.join(__dirname, '../node_modules/react-devtools-electron/extension')

app.whenReady().then(async () => {
    // Load React Devtools first
    try {
        await session.defaultSession.loadExtension(reactDevToolsPath, {
            allowFileAccess: true
        })
    }
    catch (e) {
        console.log("Couldn't load react-devtools", e.message)
    }

    // Perform rest of window init
    ...
})


Version 3.2.1

Fixing pickling on python 3.7 (thanks to Martijn Pieters)
Fixing rumel loader error (thanks to richieadler)
Fixing frozen_box does not freeze the outermost BoxList (thanks to V.Anh Tran)

Hello @cdgriffith! Thanks for submitting the PR.

There are no PEP8 issues in the file box.py !

There are no PEP8 issues in the file test/test_functional_box.py !

There are no PEP8 issues in the file test/test_unittests_box.py !

Coverage decreased (-0.6%) to 99.012% when pulling 955943649f2c1c173bcb7a2bbd6100a0f82a64ff on development into d6dae6c2c3130802436469631fd07b95784fed8e on master.


Cocoapods needs update

Using the lib from cocoapods the source code is not updated to Swift 4. If I download and put manually in the project everything is ok.

you can also add that to your podfile but don't forget to remove the extra parameters when the pod is updated ;)
pod 'ENSwiftSideMenu', :git => 'https://github.com/evnaz/ENSwiftSideMenu.git', :tag => '0.1.3'


add extra documentation about the trail end

Is your feature request related to a problem? Please describe.
When creating a checkout session, the trial_end is limited by 730 days. Although the lower limit is documented (48 hours) the upper-limit is not. A quick search of the Stripe API did not show any documentation regarding this upper limit.
I get the following error from the api:
RequestError {
http_status: 400, error_type: InvalidRequest,
message: Some("The maximum number of trial period days is 730 (2 years).")

Describe the solution you'd like
There are two possible solutions.

Add Documentation about this upper limit to the  trail_end parameter in the checkout_session
Include a small piece of code to make sure that the trail_end conforms to the upper and lower limit.

I am willing to help with these solutions.
Describe alternatives you've considered
No response
Additional context
No response

We do not have a way of injecting the documentation at the moment. My suggestion would be to create an issue with stripes openapi repo to ask them to document this properly
https://github.com/stripe/openapi
That way all projects that depend on these can benefit from these changes.


Typos in changelogs

#157  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rbro112 and the rest of your teammates on  Graphite


Ending poetry init with Ctrl + D unexpectedly terminates whole init wizard

[x] I am on the latest Poetry version.

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

[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: macOS 10.13.5

Poetry version: 0.11.2

Link of a Gist with the contents of your pyproject.toml file: this error comes up while trying to generate a pyproject.toml file with Poetry

Issue
Here's the reproduction:
$ poetry -vvv init
<initial setup snipped>
Search for package: boto3

Found 47 packages matching boto3

Enter package # to add, or the complete package name if it is not listed:
 [ 0] Flask-Boto3
 [ 1] boto3
<more options snipped>
 > 1
stty: 'standard input': unable to perform all requested operations

Enter the version constraint to require (or leave blank to use the latest version):
Using version ^1.7 for boto3

Search for a package: <Ctrl + D here>
[RuntimeError]
Aborted

Exception trace:
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/application.py in run() at line 94
   status_code = self.do_run(input_, output_)
 /usr/local/lib/python3.6/site-packages/poetry/console/application.py in do_run() at line 88
   return super(Application, self).do_run(i, o)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/application.py in do_run() at line 197
   status_code = command.run(input_, output_)
 /usr/local/lib/python3.6/site-packages/poetry/console/commands/command.py in run() at line 72
   return super(BaseCommand, self).run(i, o)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/commands/base_command.py in run() at line 146
   status_code = self.execute(input_, output_)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/commands/command.py in execute() at line 107
   return self.handle()
 /usr/local/lib/python3.6/site-packages/poetry/console/commands/init.py in handle() at line 114
   self._determine_requirements(self.option("dependency"))
 /usr/local/lib/python3.6/site-packages/poetry/console/commands/init.py in _determine_requirements() at line 205
   package = self.ask("\nSearch for a package:")
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/commands/command.py in ask() at line 213
   return self.output.ask(question, default)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/styles/cleo_style.py in ask() at line 157
   return self.ask_question(question)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/styles/cleo_style.py in ask_question() at line 189
   answer = QuestionHelper().ask(self._input, self, question)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/helpers/question_helper.py in ask() at line 49
   return self._do_ask(output, question)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/helpers/question_helper.py in _do_ask() at line 91
   ret = self._read_from_input(input_stream)
 /usr/local/lib/python3.6/site-packages/poetry/_vendor/cleo/helpers/question_helper.py in _read_from_input() at line 350
   raise RuntimeError('Aborted')

init [--name NAME] [--description DESCRIPTION] [--author AUTHOR] [--dependency DEPENDENCY] [--dev-dependency DEV-DEPENDENCY] [-l|--license LICENSE]

Basically, it's a combination of two minor issues.
First, it's not clear how to terminate the repeated prompts of Search for a package:. Perhaps a hint like "Leave blank and hit Enter to move to next step" would make it more obvious.
Since I didn't know at first what to do to move to the next stage, I tried Ctrl + D, which is commonly used to mean "end of input". I guess that was the wrong thing here, since it terminated the whole initialization wizard and I had to start over.
I think a small tweak or two to poetry init could help others avoid a similar situation in the future.

Hey Nick! Great to see you here on the issue tracker in poetry :)
#1291 fixes this issue so I'll close this for now. If you think that other improvments could be made, feel free to re-open this or create a new one.


[sysbox-fs] Updating submodules.

Signed-off-by: Cesar Talledo<EMAIL_ADDRESS>

CI failed due to unrelated error (flakiness in k8s-in-pod test). I re-run this test locally and it works without problem.


Add Merge Tree Code Owners

Add owners to merge tree and merge tree related dds.
Owning team: https://github.com/orgs/microsoft/teams/fluid-cr-merge-tree/members

changes look fine assuming they resolve correctly, but I'm seeing this on the diff:

not sure why. Seems like the team is set up fine.

it works now. it just needed an approval

Huh, interesting.


Stack deployment error due to lambda runtime issue.

Reference: https://github.com/aws-ia/cfn-ps-ct-newrelic-one/blob/main/templates/control-tower-customization.template.yml#L291C2-L291C25
Error:Resource handler returned message: "The runtime parameter of python3.7 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (python3.12) while creating or updating functions. (Service: Lambda, Status Code: 400, Request ID: 91dfaa6c-f76a-4013-52-bcb0cd65)" (RequestToken: 5ce-60f9-2c6d-b6ff-8861, HandlerErrorCode: InvalidRequest)
Seems like the runtime is old version provided in template and its High time that you change it to python3.12 on the template provided in Ref.

We are also having the same issue


Calling and Meeting section needs to be updated

[Enter feedback here]
for this article. the calling and meeting section needs to be updated.
New Meeting Experience (NME) is not currently supported in VDI environments.
this is confirmed by TEAMS engineering via one of the internal escalations. can share details. please contact me.

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

ID: 85b331f4-5939-688a-31e6-7f4c5e1c185d
Version Independent ID: 42e1f341-92c0-0a9b-9c3b-efbb5238844f
Content: Microsoft Teams on Windows Virtual Desktop - Azure
Content Source: articles/virtual-desktop/teams-on-wvd.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@SanguptaMSFT -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@SanguptaMSFT -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@SanguptaMSFT -
Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@SanguptaMSFT -
Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Monika,
Can you let me know by when this will be live ?
Thanks,
Sanyog Gupta
Technical Advisor
Teams & Skype for Business
Empowering, Helping, and Advising Customers
Customer Service & Support
1(855)4251603 Ext: 81087
sangupta<EMAIL_ADDRESS>[Image result for microsoft logo]
From: MonikaReddy-MSFT<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 8:17 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Sanyog Gupta (SAN-SKYPE | TEAMS<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Calling and Meeting section needs to be updated (#69240)
@SanguptaMSFThttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSanguptaMSFT&data=04|01|sangupta%40microsoft.com|799ef647d7cc41f7f60608d8be1b5927|72f988bf86f141af91ab2d7cd011db47|1|0|637468371972243197|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dQgrSCV6nTFP6lGOinej%2FWOt8IE7X%2FQ13jj5IZ8RJ98%3D&reserved=0 -
Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F69240%23issuecomment-764692958&data=04|01|sangupta%40microsoft.com|799ef647d7cc41f7f60608d8be1b5927|72f988bf86f141af91ab2d7cd011db47|1|0|637468371972243197|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=z7HGyEe4tGECVCw%2F7l9pgMDEyS3tD8gsUeRPFlSbbrk%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJRSUB734GAYKRGQX62IRDTS3A44TANCNFSM4WM5ICEQ&data=04|01|sangupta%40microsoft.com|799ef647d7cc41f7f60608d8be1b5927|72f988bf86f141af91ab2d7cd011db47|1|0|637468371972253191|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=jvar%2BXiwttVFF6w9%2FqMJ%2FtVjA33DN%2FSEJxUrdK3gAMc%3D&reserved=0.

Monika,
Can you let me know by when this will be live ?
Thanks,
Sanyog Gupta
Technical Advisor
Teams & Skype for Business
Empowering, Helping, and Advising Customers
Customer Service & Support
1(855)4251603 Ext: 81087
sangupta<EMAIL_ADDRESS>[Image result for microsoft logo]
From: MonikaReddy-MSFT<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 8:17 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Sanyog Gupta (SAN-SKYPE | TEAMS<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Calling and Meeting section needs to be updated (#69240)
@SanguptaMSFThttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSanguptaMSFT&data=04|01|sangupta%40microsoft.com|799ef647d7cc41f7f60608d8be1b5927|72f988bf86f141af91ab2d7cd011db47|1|0|637468371972243197|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dQgrSCV6nTFP6lGOinej%2FWOt8IE7X%2FQ13jj5IZ8RJ98%3D&reserved=0 -
Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F69240%23issuecomment-764692958&data=04|01|sangupta%40microsoft.com|799ef647d7cc41f7f60608d8be1b5927|72f988bf86f141af91ab2d7cd011db47|1|0|637468371972243197|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=z7HGyEe4tGECVCw%2F7l9pgMDEyS3tD8gsUeRPFlSbbrk%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJRSUB734GAYKRGQX62IRDTS3A44TANCNFSM4WM5ICEQ&data=04|01|sangupta%40microsoft.com|799ef647d7cc41f7f60608d8be1b5927|72f988bf86f141af91ab2d7cd011db47|1|0|637468371972253191|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=jvar%2BXiwttVFF6w9%2FqMJ%2FtVjA33DN%2FSEJxUrdK3gAMc%3D&reserved=0.

@MonikaReddy-MSFT can you confirm by when this will be live ?

@MonikaReddy-MSFT can you confirm by when this will be live ?

@MonikaReddy-MSFT still waiting for confirmation

@MonikaReddy-MSFT still waiting for confirmation

@SanguptaMSFT - The changes are merged and is live now. Thank you for your patience.

@SanguptaMSFT - The changes are merged and is live now. Thank you for your patience.


Update getting-started Configuration package to use supported postgres engine version

Why?
AWS RDS for PostgreSQL is approaching end-of-life for 9.6 and starting April 26, 2022, AWS will auto-upgrade RDS databases with this engine version. This will hopefully avoid surprises for new users onboarding onto Upbound Cloud / UXP from the guide.
What?
According to the documentation, for the db.t2.small instance type, we will need to use an engineVersion < PostgreSQL 13.
Checking with aws rds describe-db-engine-versions --engine postgres, 12.10 is a good candidate:
{
            "Engine": "postgres",
            "DBParameterGroupFamily": "postgres12",
            "SupportsLogExportsToCloudwatchLogs": true,
            "SupportsReadReplica": true,
            "DBEngineDescription": "PostgreSQL",
            "EngineVersion": "12.10",
            "DBEngineVersionDescription": "PostgreSQL 12.10-R1",
            "ExportableLogTypes": [
                "postgresql",
                "upgrade"
            ],
            "ValidUpgradeTarget": [
                {
                    "Engine": "postgres",
                    "IsMajorVersionUpgrade": true,
                    "AutoUpgrade": false,
                    "Description": "PostgreSQL 13.6-R1",
                    "EngineVersion": "13.6"
                },
                {
                    "Engine": "postgres",
                    "IsMajorVersionUpgrade": true,
                    "AutoUpgrade": false,
                    "Description": "PostgreSQL 14.2-R1",
                    "EngineVersion": "14.2"
                }
            ]
        }

The engineVersion could be patched in from the sample XRD instead of being hardcoded here -- I believe that we would have to build the Configuration xpkg manually, and then push and test it (e.g. from an org repo).
xref #102

Hello! I'm new to the community so I would welcome pairing, even though this is a small issue. I'm also not sure if this should touch cluster/olm/ where there is another reference to 9.6.

Already fixed in upstream crossplane https://github.com/crossplane/crossplane/pull/2984 , we need an update for UXP

Thanks @ytsarev! Just want to confirm that backporting from upstream means no action required here (I didn't see 2984 in 1.7.0)?
As we noted on Slack once that's done we'd still need to manually build, test, and publish the package. I'm also not sure about updating the docs for UXP as I think I read somewhere they aren't open source atm.
Let me know -- thanks!

@jastang naive git grep shows some documentation samples to update
cluster/olm/clusterserviceversion.yaml.tmpl:                      "engineVersion":"9.6",
docs/getting-started/configuration/composition.yaml:            engineVersion: "9.6"

I will also double check internally if some other steps are required

@ytsarev yep, I have those two as well. After you check internally I can open a PR for this and test with my personal registry

Thank you @jastang for pointing out this issue and being willing to contribute a fix! We're happy to support your efforts here and get this contribution to the finish line.
Let's take the following steps:

I've added some manual building steps to #102 to give you a sense of how to build and test your private package while you're working on the fix
Once the fix looks good on your side, feel free to open a PR to this repo with your changes that we can review
After the PR is merged, an Upbounder will perform the build steps to publish an official package to the registry that the docs will pick up

Some notes:

I don't think there's any other docs change, just the change to the composition.yaml file
The OLM bundle stuff is more complicated, so let's put that to the side for now - perhaps we can open a specific issue to follow up on that with @turkenh?
I'm good with leaving the engineVersion inside the composition instead of patching it in from a claim - I like the separation of concerns here where the app dev doesn't have the responsibility of picking the engine version - they get what the platform team is offering.

Thanks @jbw976 for the support! #243 is now open. I think make reviewable is only applicable to upstream crossplane but let me know if any additional details or due diligence is required.

@jastang how would you feel about driving this to completion now? You could do the build/publish of this package that has your changes in it - but first it may be wise to sync up with @plumbis to see what the current status of these docs, or the plan for the near future is for them, to see if it's worthwhile to still invest in this.
What do you think? :)

@jastang how would you feel about driving this to completion now? You could do the build/publish of this package that has your changes in it - but first it may be wise to sync up with @plumbis to see what the current status of these docs, or the plan for the near future is for them, to see if it's worthwhile to still invest in this.
What do you think? :)

@jbw976 happy to build+publish the updated package -- the getting-started docs could definitely use some love and I can compile a few issues for those. the only thing that looks like it could influence the install of the Configuration is the reference to https://raw.githubusercontent.com/upbound/universal-crossplane/main/docs/getting-started/install.yaml which seems to use registry.upbound.io instead of xpkg.upbound.io -- I think that should be updated (or removed?)

good catch @jastang, it makes total sense to update https://raw.githubusercontent.com/upbound/universal-crossplane/main/docs/getting-started/install.yaml to match what's shown in the code block here:
https://cloud.upbound.io/docs/getting-started/build-control-plane/#install-a-configuration
They are supposed to be the same thing I think, and that code block within the docs is using xpkg.upbound.io.  Makes sense to also update the install.yaml.
Another place to update (that it looks like we missed) would be the reference to 9.6 that's still in https://cloud.upbound.io/docs/uxp/build-configuration/#define-a-composite-resource.  Oops 😊
I'm hoping the manual building steps captured in the description of #102 would still work well here - let me know if you encounter any issues.  Basically do the following:

Build the package and publish it to your own test org in UbC
Install the test package from your test org and make sure it's successful and healthy

Use the steps in https://cloud.upbound.io/docs/getting-started/build-control-plane, but remember to point it at your test org

If all is OK, push the exact same test package to its official home at xpkg.upbound.io/upbound/getting-started:latest

Verified successful installation (via manifest and console UI) of xpkg:

Going to push v0.0.5 + latest now.

:v0.0.5 looks good; will push to :latest as well.
➜  configuration git:(main) ✗ k get pkg
NAME                                               INSTALLED   HEALTHY   PACKAGE                                           AGE
configuration.pkg.crossplane.io/getting-started    True        True      xpkg.upbound.io/upbound/getting-started:v0.0.5    20s

https://explore.ggcr.dev/?repo=xpkg.upbound.io%2Fupbound%2Fgetting-started

:latest also looking good:
➜  getting-started git:(main) ✗ k get pkg

NAME                                               INSTALLED   HEALTHY   PACKAGE                                           AGE
configuration.pkg.crossplane.io/getting-started    True        True      xpkg.upbound.io/upbound/getting-started:latest    16s

Also verified manifests match:
https://explore.ggcr.dev/?image=xpkg.upbound.io/upbound/getting-started:latest
https://explore.ggcr.dev/?image=xpkg.upbound.io/upbound/getting-started:v0.0.5

@jbw976 I think we are good to go! check my paper trail of due diligence and feel free to do the honours of closing this out.

Thanks for the follow up on this @jastang! Your details shown look good to me, and I also took a look inside the package with up xpkg xp-extract xpkg.upbound.io/upbound/getting-started:latest.  The engineVersion field looks correctly updated inside the package's contents.
grep -F -i 'engineVersion' out
            engineVersion: "12.10"

Let's close this out but open a new docs issue for the old engineVersion field we missed in https://cloud.upbound.io/docs/uxp/build-configuration/#define-a-composite-resource.


[Bug] There are redundant loss info in train log

Describe the bug
Please click link for more information: https://github.com/InternLM/InternLM/actions/runs/6786429220/job/18447288893

We can see there are many loss about code files which are not expected
Environment
Branch: develop
Other information
No response

Fixed in https://github.com/InternLM/InternLM/pull/489


Assisted-Keys Hard Restriction

Task Description
General rules for Assisted Keys restriction:

[x] The number of assisted keys should be less than the threshold(m) for a given Vault, such that they can’t form a signing quorum by themselves.

Connected Issue:

#3939

Closing this issue as discussed with dev.


Implement get assessment by ID endpoint

Implement GET /assessments/{id}
This endpoint returns the assessment if the user making the request:

Is the allocated assessor
Is a WORKFLOW_MANAGER

Otherwise, it will return a 403.

 CRUD endpoints for Assess


The unauthenticated git protocol is no longer supported

When I try to initialize devcontainer I get an error:
ERROR: Command errored out with exit status 128: git clone -q git://github.com/home-assistant/home-assistant.git /tmp/pip-req-build-rr1_lab5 Check the logs for full command output.

Detailed log:
fatal: remote error:
  The unauthenticated git protocol on port 9418 is no longer supported.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.

Please, replace git:// to https:// in code and update docker images on DockerHub.

Use https://github.com/ludeeus/container/pkgs/container/devcontainer%2Fintegration

I've try just now. There are same error...

Another people have the same errors with devcontainer:
https://github.com/custom-components/integration_blueprint/issues/71


TensorFlow core operator ExtractImagePatches , not supported

System information.
TensorFlow version: 2.9
Are you willing to contribute it : Yes
Describe the feature and the current behavior/state.
I made a custom  layer which uses ExtractImagePatches TensorFlow operator, but it was not supported by tflite (but listed as supported). I tried to enable the op manually but was unable to find .cc and .h file. It would be great if there is a solution to this problem, since my research depends on it.
RuntimeError: Failed to initialize op resolver for calibration:
There are unresolved custom ops: [ExtractImagePatches]Encountered unresolved custom op: ExtractImagePatches.
See instructions: https://www.tensorflow.org/lite/guide/ops_customNode number 0 (ExtractImagePatches) failed to prepare.
Who will benefit from this feature?
It is beneficial for people who are trying to develop optimization algorithms for edge computing as I am trying to work on a custom developed convolution layer in which I am using ExtractImagePatches  which is listed as supported ops while converting to tflite but giving an error.
pip install tensorflow_model_optimization

import tensorflow as tf
import tensorflow_model_optimization as tfmot
import matplotlib.pyplot as plt
import numpy as np

from keras.utils import np_utils
from tensorflow.python.keras import activations
from tensorflow.keras.callbacks import EarlyStopping

def myconv2d(ix, w, padding):
   # filter shape: [filter_height, filter_width, in_channels, out_channels]
   # flatten filters
   filter_height = int(w.shape[0])
   filter_width = int(w.shape[1])
   in_channels = int(w.shape[2])
   out_channels = int(w.shape[3])
   ix_height = int(ix.shape[1])
   ix_width = int(ix.shape[2])
   ix_channels = int(ix.shape[3])
   filter_shape = [filter_height, filter_width, in_channels, out_channels]
   flat_w = tf.reshape(w, [filter_height * filter_width * in_channels, out_channels])
   patches = tf.image.extract_patches(
       ix,
       sizes=[1, filter_height, filter_width, 1],
       strides=[1, 1, 1, 1],
       rates=[1, 1, 1, 1],
       padding=padding
   )
   patches_reshaped = tf.reshape(patches, [-1, ix_height, ix_width, filter_height * filter_width * ix_channels])
   feature_maps = []
   for i in range(out_channels):
       feature_map = tf.reduce_sum(tf.multiply(flat_w[:, i], patches_reshaped), axis=3, keepdims=True)
       feature_maps.append(feature_map)
   features = tf.concat(feature_maps, axis=3)
   return features

class MyConv2D(tf.keras.layers.Layer):
    def __init__(self, filters, kernel_size, padding='SAME', **kwargs):
        self.filters = filters
        self.kernel_size = kernel_size
        self.padding = padding
        #self.units= units
        super(MyConv2D, self).__init__(**kwargs)

    def get_config(self):
        config = super().get_config()
        config.update({
            "filters": self.filters,
            "kernel_size": self.kernel_size,
            "padding" : self.padding,
        })
        return config

    def build(self, input_shape):
        # only have a 3x3 kernel
        shape = self.kernel_size + (input_shape[-1], self.filters)
        self.kernel = self.add_weight(name='kernel', shape=shape,
                                      initializer='glorot_uniform', trainable=True)
        self.b = self.add_weight(
            name="bias", shape=(self.filters,), initializer="random_normal", trainable=True
        )
        #super((MyConv2D, self).build(input_shape))

    def call(self, inputs):
        result = myconv2d(inputs, self.kernel, self.padding) + self.b
        return result

    def compute_output_shape(self, input_shape):
        return input_shape[:-1] + (self.filters,)

def load_dataset():
	# load dataset
	(trainX, trainY), (testX, testY) = tf.keras.datasets.mnist.load_data()
	# reshape dataset to have a single channel
	trainX = trainX.reshape((trainX.shape[0], 28, 28, 1))
	testX = testX.reshape((testX.shape[0], 28, 28, 1))
	# one hot encode target values
	trainY = np_utils.to_categorical(trainY)
	testY = np_utils.to_categorical(testY)
  # convert from integers to floats
	train_norm = trainX.astype('float32')
	test_norm = testX.astype('float32')
	# normalize to range 0-1
	trainX = train_norm / 255.0
	testX = test_norm / 255.0
	# return normalized images
	return trainX, trainY, testX, testY

def create_model():
  # creating a sequantial model
  model = tf.keras.Sequential()
  # adding convolution2D layer to the model of 32 filters of size 3x3
  model.add(MyConv2D(filters=32, kernel_size=(3,3)))
  model.add(tf.keras.layers.Activation(activations.relu))
  # adding a maxpooling 2D layer of size 2x2
  model.add(tf.keras.layers.MaxPooling2D(pool_size=(2,2)))
  # adding a Dropout layer
  model.add(tf.keras.layers.Dropout(0.2))
  # adding a Flatten layer
  model.add(tf.keras.layers.Flatten())
  # adding Dense layer with 'relu' activation
  model.add(tf.keras.layers.Dense(100, activation='relu'))
  # adding Dense layer with 'softmax' activation for output
  model.add(tf.keras.layers.Dense(10, activation='softmax'))
  return model

train_images, train_labels,test_images, test_labels= load_dataset()

model = create_model()
# compile model
opt = tf.keras.optimizers.Adam()
model.compile(optimizer=opt, loss='categorical_crossentropy', metrics=['accuracy'])
es = EarlyStopping(monitor='val_loss', mode='min', verbose=1, patience=5)

# fit model
history = model.fit(train_images, train_labels, epochs=5, batch_size=32, validation_data=(test_images, test_labels),callbacks=[es])
# evaluate model
scores = model.evaluate(test_images, test_labels, verbose=0)
print("Accuracy: %.2f%%" % (scores[1]*100))
# stores scores

quantize_annotate_model = tfmot.quantization.keras.quantize_annotate_model

def representative_dataset():
  for data in tf.data.Dataset.from_tensor_slices((train_images)).batch(1).take(100):
    yield [tf.dtypes.cast(data, tf.float32)]

quant_model = quantize_annotate_model(model)
quant_model.compile(optimizer=opt, loss='categorical_crossentropy', metrics=['accuracy'])
converter = tf.lite.TFLiteConverter.from_keras_model(quant_model)
converter.optimizations = [tf.lite.Optimize.DEFAULT]
converter.representative_dataset = representative_dataset
converter.allow_custom_ops = True
converter.experimental_new_converter =True
quantized_tflite_model = converter.convert()

@ManishwarG  I was able to replicate the issue on colab.Could you please find the gist here and confirm the same.
Thank you!

@sushreebarsa Thank you! for the response, I have made few changes in the code with the link. Hoping for a response soon.

@ManishwarG I was able to replicate the issue on colab.Could you please find the gist here and confirm the same. Thank you!

This is not the issue I am facing, I have made changes to my code (you can refer that above comment). I have trouble in converting a tf op to tf lite ExtractImagePatches . I am unable to do it manually as well.

@ManishwarG Thank you for the update!
@gowthamkpr Please find the reproducible gist here for your reference.Thank you!

@ManishwarG This is not a keras issue. You should only post keras related issues here.  Can you please post this issue here as tf-lite issues are tracked in tensorflow repo and close this issue. Thank you!

@gowthamkpr
This is the second time I am being redirected, hope this link is the right place to post. Thank you!


Actix web support

The pull request contains Actix web support
the way I solved the problem is to make bridge between axum and actix-web.

This repo dosen't seem to be maintained. I have made a fork  here.
https://github.com/jinseok9338/leptos_image
This will suppport leptos 5 and actix-web
More supports are coming including making optimized image for svg


Support splatnew and _apply_iterate

I run into the following issue while playing with Tapir on big Turing models.
julia> using Turing, AbstractMCMC, Tapir, ADTypes, LogDensityProblems, LogDensityProblemsAD

julia> function AbstractMCMC.LogDensityModel(m::Turing.DynamicPPL.Model, adtype::ADTypes.AbstractADType)
       f = LogDensityFunction(m, DynamicPPL.SimpleVarInfo(m))
       adf = AbstractMCMC.LogDensityModel(LogDensityProblemsAD.ADgradient(adtype, f))
       return adf
       end

julia> num_tildes = 50 # setting this to 5 runs fine.
50

julia> expr = :(function $(Symbol(:demo, num_tildes))() end) |> Base.remove_linenums!;

julia> mainbody = last(expr.args);

julia> append!(mainbody.args, [:($(Symbol("x", j)) ~ Normal()) for j = 1:num_tildes]);

julia> f = @eval $(DynamicPPL.model(:Main, LineNumberNode(1), expr, false))
demo50 (generic function with 2 methods)

julia> model = f();

julia> f = AbstractMCMC.LogDensityModel(model, AutoTapir());

julia> initial_params = rand(LogDensityProblems.dimension(f.logdensity));

julia> LogDensityProblems.logdensity_and_gradient(f.logdensity, initial_params)

Oh, interesting. I guess I just haven't previously encountered a splatnew expression. This definitely needs to be supported, and should only be a small extension of what we currently have. I'll try to isolate a MWE.

Anyway, I think I basically understand what appears to be going on here. To summarise:

Tapir doesn't support :splatnew (I'm pleased with the error message that was thrown -- it was trivial to debug), but it should.
Tapir doesn't support Core._apply_iterate but it should. We already knew this (see the note on the readme).
SimpleVarInfo has inference issues for large numbers of tilde statements. I don't know if this was known, but it's very solvable -- see the issue I've opened https://github.com/TuringLang/DynamicPPL.jl/issues/600 .

Additionally, it may transpire that there are more problems uncovered by solving these three problems.
If we're very keen to make SimpleVarInfo type stable for moderate numbers of tilde statments then I won't make solving 1 and 2 incredibly high priority -- they definitely need to be resolved at some point though.

splatnew added in #141 -- will turn my attention to apply_iterate this week.

#152 makes Core._apply_iterate work, and improves a couple of misc rrules. Doesn't look like it's everything we need to make Tapir work with Turing's VarInfo, so I'm expanding the scope of this issue to that.

This issue is resolved via #160 , specifically for SimpleVarInfo. If you encounter any more issues with SimpleVarInfo, please re-open. Note that the performance remains not great, but it does at least run.