Api responded with ECONNREFUSED undefined

Condition:

Fn Server is running on port 8080

I have deployed UI for Fn using docker.
docker run --rm -it --link fnserver:api -p 4000:4000 -e "FN_API_URL=http://localhost:8080" fnproject/ui

But I got a problem:
><EMAIL_ADDRESS>start /app
> node server

WARNING: NODE_ENV value of 'production' did match any deployment config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
info: Using API url: localhost:8080
info: Server running on port 4000
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined
error: Error. Api responded with  ECONNREFUSED undefined

When I access the portal (http://localhost:4000/#/), a notification appears: Something went terribly wrong (Status Code: 0)

What happens if you use:
docker run --rm -it --link fnserver:api -p 4000:4000 -e "FN_API_URL=http://api:8080" fnproject/ui

Instead?
Notice the api:8080 vs localhost:8080 in the FN_API_URL

Hi muhammadhanif,
Thank you for your interest in the fnproject.
With regards to your question, try using this instead:
docker run --rm -it --link fnserver:api -p 4000:4000 -e "FN_API_URL=http://api:8080" fnproject/ui

Notice the api:8080 vs localhost:8080 in the FN_API_URL.
I'm expecting this is just a typo/oversight but for those that come across this and don't see what's wrong, it's because the FN_API_URL needs to point to the fnserver docker container (which you specify in --link). Currently it's pointing to port 8080 on the UI container where nothing is listening which is why it's giving the connection refused error.

Hi vzDevelopment,
Thank you for your clear explanation. It works.
docker run --rm -it --link fnserver:api -p 4000:4000 -e "FN_API_URL=http://api:8080" fnproject/ui

Yes, it's just a typo and it's my fault :D.


Allow for other python language packages.

This wasn't working with MagicPython (https://github.com/MagicStack/MagicPython), (or 'Python Django' for that matter). This PR takes care of that by making the checkForPythonContext more permissible.

@joaoponceleao Can you please rebase your PR?

any movement on this?

Sorry about this. Not using atom anymore and quite busy. Will look into it this weekend.

@joaoponceleao Bump on this one?

@cclauss @bh @chaffeqa
Sorry about this everyone (trying to finish a phd and been out of atom for a long time so...).
I've rebased this by request.
I removed @lexicalunit 's PR since it did not seem to be working with magicpython on my system. It should be noted that he has his own fork of this package (although I haven't actually tried it).

Hey, ping on this, I've had to install MagicPython because the built in language-python does not work with Pyton 3.5+ syntax, but now isort isn't working.
Happy to help out get this working if I can?

I use MagicPython as well and atom-isort supports this.

Oh nice, thanks!

On 6 Dec 2017, at 17:53, Amy Troschinetz<EMAIL_ADDRESS>wrote:
I use MagicPython as well and atom-isort supports this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Keep Relations via a Junction Table DRY

When I use Relations via Junction Table I often repeat the same join logic twice.
As in the example i have
return $this->hasMany(Item::className(), ['id' => 'item_id'])
            ->via('orderItems');

but in such case I would already have relation item defined in OrderItem. To avoid duplicating those join-logic I need to write code like
$query = (new OrderItem)->getItem();
$query->primaryModel = $this;
$query->via('orderItems');
return $query;

I think ActiveRecord needs way of defining those relations in way that reuses existing relations in other models. It will encourage writing code with higher quality.

Personally I don't think it would be good because it will be hard to find where the relation is defined exactly. Currently you can surely expect that everything used on a model is defined within the model.

@cebe, @SilverFire, @klimov-paul need opinions.

I think ActiveRecord needs way of defining those relations in way that reuses existing relations in other models.

It is already possible to use relation of the related model. Both eager and lazy loading is covered: no one forces you to define relation item using via - you may select primary models with relation orderItems, which will select its own relation item. Then you can use code like following:
$model->orderItems[0]->item;

I can not see any problem here.

@zuozp8 Not sure what you are aiming at. You are worried about duplicating ['id' => 'item_id'] ? Quite sure it is not worth the effort implementing something that removes that and replaces it with a method call that hides the information at this place making someone reading the code to look it up in the other class. I do not think it is worth implementing.

@klimov-paul I think @zuozp8 is asking about reusing definition from another model, not returning related model itself...

I noticed.
However defining duplicating relation using via() at main model is absolutely unnecessary.
You may avoid not only duplication of junction keys but the whole relation all together.
It is your choice to dulicate relation to Item at main model, you can use oderItems->item instead just fine. Thus I can not see why any changes are necessary here.

I see. So it seems we all agree that it won't be implemented.


The Old JS Libraries

Hi Frank...
I checking you native implementation.... I nice and certainly cleaner in some ways without all the JS wrapping.
I just wanted to drop you a line to try to understand, if you had any issues to with 0.6.0 interop.
I am middle to move some JS stuff to Dart and mostly not a problem. Except promises. I know +jacob richman is working to harmonise Futures/Await and promises.
My real question is did you come across something that made you want to dump the wrapping.... or was it case of native Async Observable was cleaner approach....
Thanks in advance, hope the question is not too fluffy..

Hey there,
Don't worry too much, the main reason to step away from the JS version, is to open up the library for server (or soon Flutter use) as well.
That said, I did have some issues before, but nothing that couldn't be worked around:

operator overloads: often used in JS land, just check the argument's type at runtime and do different things, sure you could type arguments as dynamic in Dart and just do the same, but I'm no fan of this.
Here union types would be very helpful, I worked around by just creating multiple functions for each supported argument type in Dart land.

rest arguments, again no go in Dart, rxjs merge allows you to pass n amount of Streams, in Dart I went with using a List instead, and using the old context interop way to call Function.apply on the JS side.

having to use allowInterop is very annoying, I did my very best to hide that, allow Dart users to just pass methods as-is, and wrap in allowInterop within the library code before going to the JS side.

I opened a ticket because some functions I ported did run fine with Dartium and the Dart VM, but failed after dart2js. As a workaround I again just used the old context way as I'm sure it will be fixed at some point later.

So again, this move is mainly to have rxdart working everywhere, not just in a browser :)


APT GPG key not available in packages.cloud.google.com

This is a Bug Report

Problem:
APT GPG key not available at the expected URL:
# curl -w "%{http_code}\n" -s -o /dev/null https://packages.cloud.google.com/yum/doc/apt-key.gpg.asc
500

Proposed Solution:
Provide a working URL. If changed, pages like "Installing kubeadm" should be adapted.
Page to Update:
https://kubernetes.io/...

N/A

N/A

Closing in favor of #39707


app.js seems not working on production build

Hi! 👋
(First of all, thanks for this template, it's super useful for a newbie like me)
I'm trying to install alpine.js using NPM, and although it's working locally (npm start) it doesn't work when deploying on Netlifly (NPM run build)
This is what I did:

I install Alpine.js using npm i alpinejs
I added import 'alpinejs' to  src/_assets/scripts/site.js (first line)

These are the things I checked that make me think maybe app.js is not loading on production

Show/hide behaviors are not working
Console.log message is not loading
I can't access /static/app.bundled.js (Netlify screen file not found)
I also checked https://webstarter.chriscollins.me/ with same results

Is it possible there is a problem when building the  app.bundled.js?
Site on Production: https://baterias-gesell.netlify.app/
Repo: https://github.com/LouRaul/baterias-gesell
Thnaks!

Hey @LouRaul,
Thanks for flagging this.
This appears to be a strange recent issue with Netlify and applying the .gitignore contents to the /dist folder.
There's a post on Netlify Community about this and although they've made changes, I'm still seeing this behaviour.
I've pushed an update to directly bundle the script into /dist on production and Netlify is sucessfully uploading the bundle now.
Once again, thanks for taking the time to flag this 👍

I've opened a PR for your repo to update the project 😄

Thanks for doing this!
Your template is amazing!


Change to "greater than" for limit on number of elements

Fixes #149

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

This is basically the fix described by @funkswing, with an updated test to get the tests passing (basically, now that we're looking for > 7 vs >= 7, the # of elements in that array has to increase by one).


load_state_dict stuck!

when load ckpt (multiGPU), it is stuck in load_state_dict () in the defined dist_util.py. But it is fine for one GPU. Anybody knows about this?

Same question

I got the solution from https://github.com/openai/guided-diffusion/issues/23. Just delete "if dist.get_rank() == 0" in train_util.py when loading ckpt with multi-GPUs

So the problem seems to be in version of the PyTorch in your notebook's configurations. From the looks of it, Colab and Jupyter notebooks use  0.4.0. So I added strict=False attribute to load_state_dict().
model.load_state_dict(checkpoint, strict=False)
Answer from https://stackoverflow.com/a/54058284


AWS Parameter Store with Hoxton SR8+ doesn't override properties when using multiple profiles

Type: Bug
Component:

Parameter Store
Describe the bug
When using multiple active profiles with spring cloud Hoxton SR10 and boot 2.3.9 we have noticed that property order seems to have changed, for example if we have two properties set E.g.
spring.profiles.active=profile_a,profile_b
Parameter Store configured as:
application/profile_a/app.secret-key: abc-123
application/profile_b/app.secret-key: efd-213

and in our bean we have
@Value("${app.secret-key}")
private String secretKey;

the value resolved will be abc-123 instead of efd-213
I looked through the commit history for AwsParamStorePropertySourceLocator and the issue seems to have been introduced in https://github.com/spring-cloud/spring-cloud-aws/commit/582fdc6691ead7904aaed176af2cf85221edacd5 where the Collections.reverse has been removed due to switching to using a LinkedHashSet
This looks like an accidental bug to me and the same bug exists in master and the 2.3.x branch

@MatejNedic can you take a look at this one? We should fix it in both 2.2.x in this repo and 2.3.x in awspring.

@WtfJoke You're correct the same issue exists with secrets manager too @maciejwalkowiak & @MatejNedic any chance of getting this merged in?

I'm happy to create a separate PR for the secrets manager fix too if there is a appetite for this

@peteguyatt the PR https://github.com/awspring/spring-cloud-aws/pull/195 contains fixes for both (secrets manager and parameter store).
Its probably better if we discuss in the new (migrated) issue 👍

@WtfJoke Thanks for porting the fix to the new repo and fixing secrets manager while you were at it, would you mind adding me as a contributor to the unit tests/PR in general?


Error while  performing benchmarking

Hello all,
I am having raspberry pi 3b+ installed with 32bit raspbian os  when I try to do benchmarking from the documentation https://docs.larq.dev/compute-engine/benchmark/ I am getting the following error as shown in the picture.
pi@pi:~/Desktop $ chmod +x lce_benchmark_model
pi@pi:~/Desktop $ ./lce_benchmark_model --graph=quicknet.tflite --num_threads=4
./lce_benchmark_model: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.29' not found (required by ./lce_benchmark_model)
./lce_benchmark_model: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.33' not found (required by ./lce_benchmark_model)
./lce_benchmark_model: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.32' not found (required by ./lce_benchmark_model)
./lce_benchmark_model: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.34' not found (required by ./lce_benchmark_model)
./lce_benchmark_model: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./lce_benchmark_model)
./lce_benchmark_model: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./lce_benchmark_model)
pi@pi:~/Desktop $

ldd --version gives ldd (Debian GLIBC 2.28-10)2.28
Also the process for performing inference on raspberry pi is not so clear for me. I trained my own model using larq library, converted the model to tflite format as given in end to end guide https://docs.larq.dev/compute-engine/end_to_end/,  but after generating the tflite , I am struck what to do, how to perform inference using this tflite file on raspberry pi. I was looking at building models for arm https://docs.larq.dev/compute-engine/build/arm/ , but I am not able to perform inference. Can anyone please guide me how to perform inference on raspberry pi board and please help in resolving the issue. Thank you in advance.

Hi @sandeep1404, thanks for trying out Larq Compute Engine!
The lce_benchmark_model binary requires a more recent C library than the one that comes with Raspbian. So you either need to install a more recent OS, or compile lce_benchmark_model on the Raspberry Pi itself. The instructions for that can be found here: https://docs.larq.dev/compute-engine/build/arm/ under the tab 'Building with CMake'
The documentation for doing inference is here: https://docs.larq.dev/compute-engine/inference/

Hi @Tombana Thanks for the reply, I have raspberry pi 4 loaded with 64bit os, when I try to build with cmake, the first step is to clone the Larq Compute Engine repository and make sure the TensorFlow submodule is loaded:
So I cloned the LCE and when I try the below command for TensorFlow submodule to be loaded it got struck at that point.
git submodule update --init

Submodule 'tensorflow' (https://github.com/tensorflow/tensorflow.git) registered for path 'third_party/tensorflow'
Cloning into '/home/pi/larq/compute-engine/third_party/tensorflow'...

It got struck since from long time saying that its cloning. Whats the issue am I gng in right direction, can you please help me in this regard. Thank you in advance.

Hi @Tombana  Thanks for the reply, I have a question, I built a larq model for image denoising, the model is working well for image denoising, now I converted the model to tflite  and I want to perform inference on raspberry pi using larq compute engine, so as per my understanding I need to perform the following steps, please correct me If I am wrong :

I converted my Image denoising model to tflite model using larq converter
I build with cmake on raspberry pi 4 with 64bit os
Now after building I need to perform inference using C++ using the documentation  https://docs.larq.dev/compute-engine/inference/

Are these steps correct, and can we perform image denoising inference on raspberry pi since its a kind of regression problem, I see all image classification problems performing inference on raspberry pi using larq compute engine.
Also, I am not able to get a clear picture on how to perform inference on our custom model using C++ since it is unclear from the documentation, I checked the example https://github.com/larq/compute-engine/tree/main/examples but still its not so clear about the process of performing Image denoising inference on raspberry pi using LCE. please help me in this regard. Thanks in advance

Q1: This is correct.
Q2: The example is not for image classification in particular, it is for general inference. You still have to add code that generates the input to the neural network and code that handles the output.
Q3: This is possible using our "testing" interpreter, see here: https://docs.larq.dev/compute-engine/api/python/#interpreter . To get that to work on aarch64, please see this issue: https://github.com/larq/compute-engine/issues/653

Hi @Tombana  Thanks for the reply. So using the testing interpreter based on python API as mentioned in https://docs.larq.dev/compute-engine/api/python/#interpreter, so this interpreter testing code is as follows which accepts the tflite file as input
larq_compute_engine.testing.Interpreter(
    flatbuffer_model,
    num_threads=1,
    use_reference_bconv=False,
    use_indirect_bgemm=False,
    use_xnnpack=False,
)

lce_model = convert_keras_model(model)
interpreter = Interpreter(lce_model)
interpreter.predict(input_data, verbose=1)

do I need to run all these codes on raspberry pi for inference, since if I run all these codes on my CPU it doesn't make any difference in inference time is that correct?

You can run the convert_keras_model part on your other computer. The interpreter.predict(..) part is what you can run on the Raspberry Pi.

Hi @Tombana Thanks for the reply, I got it now. But what is the difference between doing inference with C++ as mentioned in https://github.com/larq/compute-engine/issues/url and inference using python API https://github.com/larq/compute-engine/issues/url, are the both same or different? Thank you in adavance

The C++ and Python versions both do the same. However the Python version has more overhead, so if latency is crucial then you could use C++.
Indeed the larq-compute-engine package is not available on the RPi4 by default, but here it is explained how you can compile it yourself: https://github.com/larq/compute-engine/issues/653

Hi @Tombana Thanks for answering all my queries patiently.  I have gone through #653 and started building pip package for lce as mentioned in that by removing  few of the code lines as mentioned in the issue #653, I performed the following steps:
when I perform the bazel build using the below command it got build completed sucessfully
bazel build :build_pip_pkg --config=aarch64

after that bazel-bin directory got created but the directory is empty and when I ran the below command it gives me an error showing that no such file or directory. I am attaching the picture for the reference.

bazel-bin/build_pip_pkg artifacts --plat=linux_aarch64

What is the issue, can you please help in resolving the issue and how to verify whether the pip package for LCE is installed or not?

I believe the issue might be the first output after bazel build :build_pip_pkg --config=aarch64:
WARNING: Download from https://..... GET returned 404 Not Found

Do you have a working internet connection on your device? If so, perhaps just re-try again later.

Hi @CNugteren Thanks for the reply, My board is connected to the internet, I retired building again using the command
bazel build :build_pip_pkg --config=aarch64 but still it gives me the same warning as mentioned in the picture and then said build completed successfully :
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/... GET returned 404 Not Found

Hi @Tombana  Thanks for the reply, there are some files in bazel-out directory but I cannot able to see any files in bazel-bin even when I used run instead of build. when  I use run it got run but there are no files in bazel-bin
I am attaching the picture for the reference

Please have a look into it and kindly help me in this regard, Thank you in advance.

Hi @Tombana Thanks for the response, I checked the contents of bazel-out/aarch64-opt and its subfolder, there is nothing in it, also I run the command bazel info bazel-bin and checked the path and there is nothing inside that path as well, I am attaching the picture for your kind reference. Thank you in advance.

I have searched a bit but I'm afraid I don't have a solution. Since you're building on the raspberry pi itself, maybe it works if you remove the --config=aarch64 flag from bazel build.

Hi, @Tombana Thanks for the reply, I followed all your steps but still, I cannot able to find anything in the Bazel-bin directory, but I found the  build_pip_package.sh file in Bazel-compute-engine and when I tried to execute the command It was giving me the error, I am attaching the pictures for reference, can you please have a look at it, and if you can able to debug the issue please help in resolving this, or is there is any other way where I can run the inference on raspberry pi using python API, any clear example would be beneficial to understand. Thanks for the help.

Those bazel errors that you get with bazel build //larq_compute_engine/tflite/python:interpreter are the problem. (I think maybe also you modified some BUILD files where you excluded //larq_compute_engine/tflite/python:interpreter from build_pip_pkg or something, otherwise this error would've shown up before).
I think the problem might be the version of bazel. Can you try to use bazelisk instead of bazel?
Download it from https://github.com/bazelbuild/bazelisk/releases and then replace the bazel command with ./bazelisk

I'm afraid I don't have any other ideas. I'm pretty sure that the errors at bazel build //larq_compute_engine/tflite/python:interpreter are the main problem, but I don't know how to fix that. I've never tried to use bazel directly on a Raspberry Pi.
I think it might be easier to just build the RPi package on your other computer instead of building it on the RPi itself. Then you need --config=aarch64 so that it will build for aarch64.

Hi @Tombana Thanks for the reply, I will try the other way in building the package on another computer and try to config on RPi, I will post if I face any further issues, Thank you for the help and patience in looking at the issues.

Hi @Tombana I am confused about how to build the package on another computer and try to config on RPi, can you give me an insight in understanding the process of how to do that? Thanks in advance.

It's the same steps as on the Pi itself, except that you have to use --config=aarch64 when you run bazel build. And when you run the python wheel packaging step, you have to use --plat=linux_aarch64, as described in https://github.com/larq/compute-engine/issues/653.

Hi @Tombana Thanks for the reply, is there any example or any repo for end to end guide for deploying a custom BNN model on raspberry pi with Larq compute engine doing inference with Python API, if so can you please share it here, Thank you in advance.

Hi @Tombana I am trying to build the package on Ubuntu 20.04, using the command bazel build :build_pip_pkg --config=aarch64 but the build was not successful I am attaching the picture that shows logs for error

Can you please have a look and help me in resolving the issue, Thank you in advance.

Hi @Tombana I followed the instructions specified in #653 to build the pip package in Ubuntu 20.04, I followed the below steps:
step1:
build using the command bazel build :build_pip_pkg --config=aarch64  the following are the logs on my system with Ubuntu:
WARNING: Option 'java_toolchain' is deprecated
WARNING: Option 'host_java_toolchain' is deprecated
INFO: Analyzed target //:build_pip_pkg (9 packages loaded, 68 targets configured).
INFO: Found 1 target...
Target //:build_pip_pkg up-to-date:
  bazel-bin/build_pip_pkg
INFO: Elapsed time: 4.005s, Critical Path: 0.89s
INFO: 4 processes: 4 internal.
INFO: Build completed successfully, 4 total actions

After a successful build I found files in bazel-bin, where earlier when I build on RPi I cannot able to find the files in bazel-bin
step 2:
Next I ran this command  on my computer bazel-bin/build_pip_pkg artifacts --plat=linux_aarch64 and below are the logs for the command
++ uname -s
++ tr A-Z a-z
+ PLATFORM=linux
+ is_windows
+ [[ linux =~ msys_nt*|mingw*|cygwin*|uwin* ]]
+ PIP_FILE_PREFIX=bazel-bin/build_pip_pkg.runfiles/larq_compute_engine/
+ main artifacts --plat=linux_aarch64
+ DEST=artifacts
+ BUILD_FLAG=--plat=linux_aarch64
+ [[ -z artifacts ]]
+ mkdir -p artifacts
++ abspath artifacts
+++ dirname artifacts
++ cd .
+++ basename artifacts
++ echo /home/sandeep/compute-engine/artifacts
++ cd /home/sandeep/compute-engine
+ DEST=/home/sandeep/compute-engine/artifacts
+ echo '=== destination directory: /home/sandeep/compute-engine/artifacts'
=== destination directory: /home/sandeep/compute-engine/artifacts
++ mktemp -d -t tmp.XXXXXXXXXX
+ TMPDIR=/tmp/tmp.T5Njh7hkNJ
++ date
+ echo Tuesday 25 April 2023 10:45:43 PM IST : '=== Using tmpdir: /tmp/tmp.T5Njh7hkNJ'
Tuesday 25 April 2023 10:45:43 PM IST : === Using tmpdir: /tmp/tmp.T5Njh7hkNJ
+ echo '=== Copy Larq Compute Engine files'
=== Copy Larq Compute Engine files
+ cp bazel-bin/build_pip_pkg.runfiles/larq_compute_engine/setup.py /tmp/tmp.T5Njh7hkNJ
+ cp bazel-bin/build_pip_pkg.runfiles/larq_compute_engine/MANIFEST.in /tmp/tmp.T5Njh7hkNJ
+ cp bazel-bin/build_pip_pkg.runfiles/larq_compute_engine/README.md /tmp/tmp.T5Njh7hkNJ
+ cp bazel-bin/build_pip_pkg.runfiles/larq_compute_engine/LICENSE /tmp/tmp.T5Njh7hkNJ
+ is_linux
+ [[ linux == \l\i\n\u\x ]]
+ touch /tmp/tmp.T5Njh7hkNJ/stub.cc
+ is_windows
+ [[ linux =~ msys_nt*|mingw*|cygwin*|uwin* ]]
+ rsync -avm -L '--exclude=*_test.py' bazel-bin/build_pip_pkg.runfiles/larq_compute_engine/larq_compute_engine /tmp/tmp.T5Njh7hkNJ
building file list ... done
larq_compute_engine/
larq_compute_engine/__init__.py
larq_compute_engine/mlir/
larq_compute_engine/mlir/__init__.py
larq_compute_engine/mlir/python/
larq_compute_engine/mlir/python/__init__.py
larq_compute_engine/tflite/
larq_compute_engine/tflite/__init__.py
larq_compute_engine/tflite/python/
larq_compute_engine/tflite/python/__init__.py
larq_compute_engine/tflite/python/interpreter.py
larq_compute_engine/tflite/python/interpreter_base.py
larq_compute_engine/tflite/python/interpreter_wrapper_lite.so

sent 3,704,866 bytes  received 183 bytes  7,410,098.00 bytes/sec
total size is 3,703,194  speedup is 1.00
+ pushd /tmp/tmp.T5Njh7hkNJ
/tmp/tmp.T5Njh7hkNJ ~/compute-engine
+ is_windows
+ [[ linux =~ msys_nt*|mingw*|cygwin*|uwin* ]]
+ echo '=== Stripping symbols'
=== Stripping symbols
+ chmod +w /tmp/tmp.T5Njh7hkNJ/larq_compute_engine/tflite/python/interpreter_wrapper_lite.so
+ strip -x /tmp/tmp.T5Njh7hkNJ/larq_compute_engine/tflite/python/interpreter_wrapper_lite.so
strip: Unable to recognize the format of the input file `/tmp/tmp.T5Njh7hkNJ/larq_compute_engine/tflite/python/interpreter_wrapper_lite.so'

These are the different folders in Bazel bin
build_pip_pkg  build_pip_pkg.runfiles  build_pip_pkg.runfiles_manifest  examples  external  larq_compute_engine

I am unaware of what to do next, what files need to be copied and where they are located and how to install those files on RPi and do inference using python based interpreter.

The lce_benchmark_model binary requires a more recent C library than the one that comes with Raspbian. So you either need to install a more recent OS, or compile lce_benchmark_model on the Raspberry Pi itself. The instructions for that can be found here: https://docs.larq.dev/compute-engine/build/arm/ under the tab 'Building with CMake'
The documentation for doing inference is here: https://docs.larq.dev/compute-engine/inference/

Hi there, I have the same problem with the Raspberry Pi OS Lite (64-bit), which was released on 2023-02-21. Is there any suggestion for which OS I should use?

@sandeep1404
It seems like the strip utility does not accept aarch64 libraries. Can you comment-out the strip command from the build_pip_package.sh script, and then try to run it again?
Once that's successful, a .whl file should appear in the folder artifacts. You can copy that .whl file to your raspberry pi and then just use pip install ./filename.whl on it.

Hi there, I have the same problem with the Raspberry Pi OS Lite (64-bit), which was released on 2023-02-21. Is there any suggestion for which OS I should use?

Hi @bywmm, I recommend Manjaro Linux (easy setup) or Arch Linux (for more advanced users) for Raspberry Pi. These distributions usually come with the newest packages.

It seems like --plat=linux_aarch64 might be ignored by the python tools. Can you try to update the setuptools and wheel packages?
pip install setuptools wheel --upgrade

Hi @Tombana, I tried  updating the setup tools and wheel with the command pip install setuptools wheel --upgrade , but still I am facing the same issue as mentioned in above: ERROR: larq_compute_engine-0.11.0-cp310-cp310-linux_x86_64.whl is not a supported wheel on this. What is the issue, can you please help me in resolving this issue? Thank you in advance.

I meant upgrading those packages on your Ubuntu machine, and then recreating the .whl file.

Maybe it's a python version mismatch? I see that you built a python 3.10 wheel on your Ubuntu machine. Maybe the raspberry Pi has another python version? They have to be the same.

Hi @Tombana, I created a new environment with python=V3.9 and build the packages, now the .whl file ran successfully and installed larq_compute_engine-0.11.0, but when I try to import lce import larq_compute_engine as lce it is throwing me a Module not found error as shown in the figure below. What are the next steps, is the LCE installed properly, can I load the interpreter and run the inference now. Sorry for troubling you
by asking many questions this is a part of my thesis work, So I need to resolve and do inference. Thank you in advance.

As described in https://github.com/larq/compute-engine/issues/653, you have to remove from larq_compute_engine.mlir.python.converter import convert_keras_model from __init__.py and remove convert_keras_model from __all__, that should fix this issue.

Hi @Tombana , I started Performing Inference on RPI, I converted the model to tflite on my computer and loaded the tflite file on RPI, but I am getting the following error:
Traceback (most recent call last):
  File "/home/pi/larq/larq_bnn_test/larq_bnn_test.py", line 10, in <module>
    interpreter=lce.testing.Interpreter(
  File "/home/pi/.local/lib/python3.9/site-packages/larq_compute_engine/tflite/python/interpreter.py", line 48, in __init__
    from larq_compute_engine.tflite.python import interpreter_wrapper_lite
ImportError: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/pi/.local/lib/python3.9/site-packages/larq_compute_engine/tflite/python/interpreter_wrapper_lite.so)

I have lib6 and lib6-dev already installed
libc6 is already the newest version (2.31-13+rpt2+rpi1+deb11u5).
libc6-dev is already the newest version (2.31-13+rpt2+rpi1+deb11u5).

I have no clue how to resolve this issue, I have GLIBC 2.31 installed in my system, it is the latest version, but it ask for GLIBC_2.32. Can you kindly help me in resolving the issue. I am attaching the picture for reference.Thank you in advance.

You'll have to get an OS for your raspberry pi with a newer glibc, such as (probably) Manjaro or Arch.
The alternative was to build the code with an older compiler so that it does not depend on the new glibc anymore. Unfortunately using an older crosscompiler in bazel is not so easy. That leaves the option of building it on the raspberry pi itself, but that gave the "empty bazel-bin" issue.

Hi @Tombana, So that means should I use Manjaro OS on my raspberry pi? If I use the OS should I build the files again and generate the .whl file or I can use the .whl file generated and can do pip install  ./filename.whl, I hope since the packages are built upon linux-aarch64, the older .whl file should work is it right?
Now after installing the manjaro OS on my RPI, I will install the LCE with the earlier generated .whl file and perform inference is this correct please correct me if I am wrong, or can I use the current OS and resolve the issue of  GLIBC, if I use the older compiler then you mentioned it will give "empty bazel-bin" issue. So the best option is to go with new OS is it so?

That is all correct. You can use Manjaro OS on our Raspberry Pi. If you go to https://manjaro.org/download/ you can select Raspberry Pi as device and then choose a desktop environment. You can use the .whl file that you built before; there is no need to rebuild it.

Thanks @Tombana It is working with Manjaro OS, Finally BNN inference is done on RPI using LCE. Really appreciate your continuous help and patience.

Hi @Tombana I have a question related to flags in LCE interpreter, when I call the interpreter as mentioned below
larq_compute_engine.testing.Interpreter(
    flatbuffer_model,
    num_threads=1,
    use_reference_bconv=False,
    use_indirect_bgemm=False,
    use_xnnpack=False,
)

What are the different flags here like use_reference_bconv , use_indirect_bgemm and use_xnnpack and one more question is related to num_threads, I got to know that raspberry pi has 4 cores and it supports multithreading, so for  num_threads=1 I am getting inference of 0.12s for a batch of 8 images while when I set  num_threads=2 or   num_threads=3 or  num_threads=4 the inference time for all 3 different cases is same almost it is 0.1s for a batch of 8 images, why is it so, as the number of threads increases the design becomes more parallel and inference should be faster, please correct me If I am wrong, what is the maximum value of   num_threads we can assign for raspberry pi 4. Thank you in advance.

use_reference_bconv should be left to False. It is only used for unittests and uses a slow implementation
use_indirect_bgemm can often result in faster inference for binary layers, so you should try both options and see which one is faster
use_xnnpack specifies if XNNPACK should be used to run all the non-binary layers. Usually it's faster to enable it, but again it should be tested.

As for num_threads, you are right that it should become faster if you use more threads, and it should be at most 4.
However it does not use the threads across the batch dimension, it uses threads for each individual input in the batch.
It is common that you don't get a 4X speedup with 4 threads: if the input sizes are not large enough, there is a lot of overhead from parts of the computation that are not parallelized.

Hi @Tombana Thank you for your suggestions, I Will try using lce_benchmark_model  again and observe the results

Hi @Tombana Thank you for your suggestions, I Will try using lce_benchmark_model  again and observe the results

so is this compulsory to install other OS? cant we do this on Raspbian OS?

It will probably work on newer versions of Raspbian OS if they update the gcc/glibc version.

its showing error with python 3.8.10 if i want to install .whl file on raspbian os......it says python 3.8.10 not included in the >=3.10.......in your example it was working with python 3.9 as well

We always support the 3 most recent Python versions, so in this case that is 3.10, 3.11, 3.12. Python 3.8 and 3.9 are no longer supported in the latest release.

You have to install the wheel package by running pip install wheel.

You have to install the wheel package by running pip install wheel.

can you please provide me any script for minimal.cc that we can use for input output of imagenet or any dataset


{HDInsight}Remove encryptionAtHost property

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

@aim-for-better this is a breaking change. please clarify if there's any customer impact.

@aim-for-better this is a breaking change. please clarify if there's any customer impact.

No existing customers will be impacted, because we haven't published SDK based previous swagger.


[SMALLFIX] Use field property for 'AbstractCmdRunner'

What changes are proposed in this pull request?
Use field property 'mActiveJobs' for 'AbstractCmdRunner' instead of the default value DEFAULT_ACTIVE_JOBS which is hardcoded with 3000.
Why are the changes needed?
Currently, the number of active jobs are limited at 3000 which is not enough when we have lots of loading tasks on huge cluster. We will add command line args to allow user pass the limit of active jobs (set the value of 'mActiveJobs') the  in the future.
Does this PR introduce any user facing changes?
N/A

Thank you for your pull request.
In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement (CLA).
It's all electronic and will take just a few minutes. Please download CLA form here, sign, and e-mail back to<EMAIL_ADDRESS>
I already sign the CLA and send it to<EMAIL_ADDRESS>.

alluxio-bot, merge this please

alluxio-bot, merge this please

alluxio-bot, merge this please


Add VideoStats HUD element.

Derived from mrdoob's stats.js.
Usage:

Create VideoStats
add to DOM using stats.domElement
call stats.start(videoElement)
Will display resolution and a framerate graph for that video element.

@samdutton @fippo @jiayl PTAL

So what's the plan for this?

I have a new version I am working on that is more flexible.

Are you going to push it to this pull request or make a new one?

Any news on this?


not work when PHP_VERION = 7.2

Info:

Docker version ($ docker --version): 18.03.1-ce, build 9ee9f40
Laradock commit ($ git rev-parse HEAD): 0c41fceae1b23089f5360dc4f8aeb85719c7bf5a
System info (Mac, PC, Linux): Mac
System info disto/version: High Sierra 10.13.4

Issue:

When I change the PHP_VERSION to 7.2 in .env file , and  run docker-compose build php-fpm,the build will fail with the following error
E: Unable to locate package jpegoptim
E: Unable to locate package pngquant
ERROR: Service 'php-fpm' failed to build: The command '/bin/sh -c if [ ${INSTALL_IMAGE_OPTIMIZERS} = true ]; then     apt-get install -y --force-yes jpegoptim optipng pngquant gifsicle ;fi' returned a non-zero code: 100

Expected behavior:

Reproduce:

docker-compose build php-fpm

Relevant Code:
// place a code sample here

Look at #1476


Seperate Interfaces to Contract project to provide abstraction layer

Move interfaces away from implementation provides flexibility when projects are separated in consumer code base.

To add to this, I was thinking today whether it would be possible to have IRequestHandler in another package (or in the MediatR.Contracts package if that's possible (probably not, I'd guess).
The reason is because I have a Presentation layer of my architecture that uses IMediator to send requests, and the handlers are in a different project, as part of the Application layer, and implement IRequestHandler. But I want to avoid being able to inject IMediator into those handlers to prevent handlers sending out more requests.
I wish the handlers didn't have a reference to IMediator because I think it would solve this issue. They only need IRequestHandler but that's not in the Contracts package unlike IRequest. I found this a bit unusual.

Physically separating types to enforce architectural styles sound like a slippery slope. What you're requesting sounds like a few types per assembly, which seems excessive. Why don't you write some architecture tests or a Roslyn analyzer to enforce your requirements instead?

Is this something that could be done in a way that's backwards compatible with previous versions of MediatR?

No, the old assembly/package would need to still reference the new assembly/package and apply a TypeForwardedToAttribute in order to make it backwards compatible, but that seems to defeat your requirement(s).

Any objections to the pr being approved?
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Kristian Hellang @.>
Sent: Thursday, April 4, 2024 9:10:40 PM
To: jbogard/MediatR @.>
Cc: harrypooni @.>; Author @.>
Subject: Re: [jbogard/MediatR] Seperate Interfaces to Contract project to provide abstraction layer (Issue #1014)
Physically separating types to enforce architectural styles sound like a slippery slope. What you're requesting sounds like a few types per assembly, which seems excessive. Why don't you write some architecture tests or a Roslyn analyzer to enforce your requirements instead?
Is this something that could be done in a way that's backwards compatible with previous versions of MediatR?
No, the old assembly/package would need to still reference the new assembly/package and apply a TypeForwardedToAttributehttps://learn.microsoft.com/en-us/dotnet/api/system.runtime.compilerservices.typeforwardedtoattribute?view=net-8.0 in order to make it backwards compatible, but that seems to defeat your requirement(s).
—
Reply to this email directly, view it on GitHubhttps://github.com/jbogard/MediatR/issues/1014#issuecomment-2038121850, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI3M6WSZEP65UZFQ5WVCMTLY3WXUBAVCNFSM6AAAAABFJE7OLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZYGEZDCOBVGA.
You are receiving this because you authored the thread.Message ID: @.***>

@harrypooni I would very much appreciate just one other project containing the abstractions for IMediator and ISender instead of including them in the Contracts project because this would solve my issue mentioned above. The issue with sending nested requests inside handlers has been mentioned a number of times on previous issues and blogs/posts across the internet, and having this other project is a very simple change, especially since you've already done most of the work in this PR.

Also, a software component is often designed with required interfaces and provided interfaces. It is quite common for these interfaces to be placed in two separate abstraction projects. The required interfaces have an implementation contained within the component. These are input interfaces used to communicate indirectly with the component (e.g., the IMediator). The provided interfaces (e.g. the ones contained in the current Contracts project) are ones that we can provide implementations of. For example, a custom application request or handler that implements IRequest/IRequestHandler.
This design is not unusual and is quite common in many architectures I have worked on, so I don't think my request is unusual and actually provides a lot of flexibility and encapsulation benefits.

You could also keep IMediator and ISender in the MediatR project as a temporary measure, but I appreciate the original issue of keeping abstractions away from the implementation project, which is why I'd suggest 2 abstraction projects.

I created a new PR to solve an issue with the initial one, and to implement the design I mentioned above:
https://github.com/jbogard/MediatR/pull/1020

I'm not splitting packages or projects out any further for any opinionated code architectural styles. There are better, more effective ways to solve these problems that also don't involve myself having to maintain even more packages.
The current packages are split ONLY because disparate applications often need to reference a "contracts" project in teams where that contracts are things like API DTOs. The separate Contracts package removes a "diamond dependency" on MediatR.


TLS Session ticket

I tried to implement ssl tls ticket feature. But haven't enough skill.
So can someone help me with it. Any examples will be good. I stack with callback function implementation in cgo.
I'm talking about this: https://www.openssl.org/docs/ssl/SSL_CTX_set_tlsext_ticket_key_cb.html
Thank you.

I think I did this without knowing this was a thing. Sorry! Gonna close for now.


[Feature] Fix fangorn move actions [OSF-7164]

Purpose
There are a number of issues with fangorn moving and dropping that lead to some strange WB issues that should not be able to occur at all. This PR helps block a few of those by locking down files while waiting for the WB ajax to respond before releasing the file. In addition, this includes a number of other fixes and brand new fangorn unit test file testing every bit of the move/copy/forbid logic.

Changes

Blocks clicking on files that have a pending waterbutler ajax (move/rename/copy) action. This releases when a response is returned. This means that weird things can still occur if the 202 'taking longer than expected' modal pops up, but was done this way to avoid infinite lockups that require a page refresh. [OSF-7164]
Blocks dragging of folders that have a child with a pending wb action. Folders will just not have any droppable targets allowed. [OSF-7164]
Parent folders can no longer be dragged into own children folders [OSF-7162]
Fangorn data undefined error on folder moves was occuring in the move/copy/forbidden logic. Returns forbidden if data is undefined. So rarely all drop actions will be disabled if folders are not fully populated when dragging starts [OSF-7162]
Add a boat load of unit tests for move/copy/forbidden drag and drop logic.

Side effects

Figshare file drop logic was wrong and attempted to allow files in public figshare projects to be copied out. Waterbutler denied these calls. Now drops should be prevented. Private figshare projects might allow dropping out. If this is tested and throws an error, please let me know and I'll disable it.
Dropping on files was allowed and actually defaulted to moving the object to the parent of the child. After conferring with Nici and Sara this behavior was removed as it was strange, and possibly lead to some fun edge cases.

Ticket
https://openscience.atlassian.net/browse/OSF-7162
https://openscience.atlassian.net/browse/OSF-7163
https://openscience.atlassian.net/browse/OSF-7164
[#OSF-7164]

QA Considerations
This is unfortunately a beast of a changelog for file/folder dragging and dropping. This will probably require testing some addons that have weird move/copy/forbidden behavior.
The ones that should be tested are figshare, dataverse, and github. Only the actions that result in different behaviors need to be tested for these specific addons (e.g., draft versus published figshare).

Closing in favor of #6525 which merged all of these changes and more.


assertion failed: sbo.0.x % (1 << sb_shift) == 0 since earlier this week

If you run cargo test in
https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/tree/master/gst-plugin-rav1e
it will fail with panics
thread 'test_encode_y444' panicked at 'assertion failed: sbo.0.x % (1 << sb_shift) == 0', /home/slomo/.cargo/git/checkouts/rav1e-14e16d25dd5cd9c0/aa4271e/src/tiling/tile_restoration_state.rs:369:1
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:47
   3: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:36
   4: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:200
   5: std::panicking::default_hook
             at src/libstd/panicking.rs:211
   6: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:477
   7: std::panicking::begin_panic
             at /rustc/eae3437dfe991621e8afdc82734f4a172d7ddf9b/src/libstd/panicking.rs:411
   8: rav1e::tiling::tile_restoration_state::TileRestorationStateMut::new
             at /home/slomo/.cargo/git/checkouts/rav1e-14e16d25dd5cd9c0/aa4271e/src/tiling/tile_state.rs:0
   9: rav1e::tiling::tile_state::TileStateMut<T>::new
             at /home/slomo/.cargo/git/checkouts/rav1e-14e16d25dd5cd9c0/aa4271e/src/tiling/tile_state.rs:110
  10: <rav1e::tiling::tiler::TileContextIterMut<T> as core::iter::traits::iterator::Iterator>::next
             at /home/slomo/.cargo/git/checkouts/rav1e-14e16d25dd5cd9c0/aa4271e/src/tiling/tiler.rs:187
  11: alloc::vec::Vec<T>::extend_desugared
             at /rustc/eae3437dfe991621e8afdc82734f4a172d7ddf9b/src/liballoc/vec.rs:2003
  12: <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T,I>>::spec_extend
             at /rustc/eae3437dfe991621e8afdc82734f4a172d7ddf9b/src/liballoc/vec.rs:1900
  13: <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T,I>>::from_iter
             at /rustc/eae3437dfe991621e8afdc82734f4a172d7ddf9b/src/liballoc/vec.rs:1895
  14: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter
             at /rustc/eae3437dfe991621e8afdc82734f4a172d7ddf9b/src/liballoc/vec.rs:1796
  15: core::iter::traits::iterator::Iterator::collect
             at /rustc/eae3437dfe991621e8afdc82734f4a172d7ddf9b/src/libcore/iter/traits/iterator.rs:1466
  16: rav1e::api::ContextInner<T>::compute_lookahead_motion_vectors
             at /home/slomo/.cargo/git/checkouts/rav1e-14e16d25dd5cd9c0/aa4271e/src/api/mod.rs:1464
  17: rav1e::api::ContextInner<T>::compute_lookahead_data
             at /home/slomo/.cargo/git/checkouts/rav1e-14e16d25dd5cd9c0/aa4271e/src/api/mod.rs:1681
  18: rav1e::api::ContextInner<T>::send_frame
             at /home/slomo/.cargo/git/checkouts/rav1e-14e16d25dd5cd9c0/aa4271e/src/api/mod.rs:1181

This was working fine with the version of rav1e on Tuesday.

I think the test that was disabled here was catching this.

This only happens when setting tile rows/cols to some value, at least setting both to 2 makes it happen.

Reproducible with one tile with the following test:
#[test]
fn get_units_region_assert() {
  let config = Config {
    enc: EncoderConfig {
      width: 65,
      height: 158,
      bit_depth: 8,
      chroma_sampling: ChromaSampling::Cs420,
      chroma_sample_position: ChromaSamplePosition::Unknown,
      pixel_range: PixelRange::Limited,
      color_description: None,
      mastering_display: None,
      content_light: None,
      still_picture: true,
      time_base: Rational { num:<PHONE_NUMBER>, den:<PHONE_NUMBER>560342528 },
      min_key_frame_interval: 12,
      max_key_frame_interval: 240,
      reservoir_frame_delay: None,
      low_latency: true,
      quantizer: 100,
      min_quantizer: 0,
      bitrate: 0,
      tune: Tune::Psychovisual,
      tile_cols: 0,
      tile_rows: 0,
      tiles: 0,
      rdo_lookahead_frames: 0,
      speed_settings: SpeedSettings {
        min_block_size: BlockSize::BLOCK_64X64,
        multiref: false,
        fast_deblock: true,
        reduced_tx_set: true,
        tx_domain_distortion: true,
        tx_domain_rate: false,
        encode_bottomup: false,
        rdo_tx_decision: false,
        prediction_modes: PredictionModesSetting::Simple,
        include_near_mvs: false,
        no_scene_detection: true,
        diamond_me: true,
        cdef: true,
        quantizer_rdo: false,
        use_satd_subpel: false,
      },
      show_psnr: false,
      train_rdo: false,
    },
    threads: 1,
  };

  let mut ctx: Context<u8> = config.new_context().unwrap();
  ctx.send_frame(ctx.new_frame()).unwrap();
  ctx.flush();

  ctx.receive_packet().unwrap();
}

Weird time base seems essential (1/25 doesn't trigger the assertion).

Weird time base seems essential (1/25 doesn't trigger the assertion).

wat.
Well, you have my attention, that's for sure.
I mean you had it, I am working on this 'right now' which means today
around other tasks.
Monty

The above example isn't one tile.  There's three tiles stacked vertically.


redux keep telling me: You are currently using minified code outside of NODE_ENV === 'production'.

Do you want to request a feature or report a bug?
BUG
What is the current behavior?
Whenever I use Redux, I get this:
You are currently using minified code outside of NODE_ENV === 'production'. This means that you are running a slower development build of Redux. You can use loose-envify (https://github.com/zertosh/loose-envify) for browserify or DefinePlugin for webpack (http://stackoverflow.com/questions/30030031) to ensure you have the correct code for your production build.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar.
I build with Webpack. I have the EnvironmentPlugin who set the NODE_ENV to "production", I tried it in the DefinePlugin too. I know that React have a similar warning, but it didn't show up. It should show this message for both if it was incorrect.
I tried to run NODE_ENV=production webpack -p --define process.env.NODE_ENV='\"production\"' to be sure it build in production mode. But nothing works for Redux only.
When I check into the package at [My Project]/node_modules/redux/dist/redux.js, I see this:
if ("development" !== 'production' && typeof isCrushed.name === 'string' && isCrushed.name !== 'isCrushed') {
  warning('You are currently using minified code outside of NODE_ENV === \'production\'. ' + 'This means that you are running a slower development build of Redux. ' + 'You can use loose-envify (https://github.com/zertosh/loose-envify) for browserify ' + 'or DefinePlugin for webpack (http://stackoverflow.com/questions/30030031) ' + 'to ensure you have the correct code for your production build.');
}

It's probably the installation who won't put my real NODE_ENV in place of "development".
let clientPlugins = [
  new webpack.EnvironmentPlugin({
    NODE_ENV: 'production',
  }),
  new webpack.optimize.CommonsChunkPlugin({
    name: 'packages',
    filename: 'packages.min.js',
    minChunks: function(module) {
      return module.resource && (/node_modules/).test(module.resource);
    }
  }),
];

What is the expected behavior?
It should not print this warning.
Which versions of Redux, and which browser and OS are affected by this issue? Did this work in previous versions of Redux?
Version: "redux": "^3.7.2",

You're not importing the right version of Redux. The one at dist/redux.js is the UMD development build. Since you're using webpack, make sure you're doing import { createStore } from 'redux' or const { createStore } = require('redux').
Direct imports from the npm package will be going away in 4.0.

There's all the imports of redux in my project.

I have the same issue in my project and my import looks in that way:
import { createStore, applyMiddleware, combineReducers, compose } from 'redux';

any follow ups?

@timdorr Will be any alternative for devs using umd?

@stat92 UMD isn't going away<EMAIL_ADDRESS>

+1 warning with production mode

Hi guys, please remove {compose} from import. I think you aren't using anything relating to it. :)

Came across same issue, initially had the exact same issue as described in issue description. For future reference would like to leave the description of my case here.
After trying to reproduce the issue in a new project realized that we had
// webpack.config.js
module.exports = {
  // ...
  resolve: {
    mainFields: ['unpkg', 'main', 'module']
  }
}

Since unpkg version from dist/redux.js had this warning regardless of having NODE_ENV, the warning was present in the production bundle. Simply removing mainFileds or replacing the line to mainFields: ['module', 'main', 'unpkg'] fixes the issue and also improves the treeshaking done by the minifier.

@antonk52 It works, But It might lead to a series of problems, such as resolution strategy for module changes. Here is a better solution.
  module: {
    rules: [
      {
        test: /redux$/,
        resolve: { mainFields: ['module', 'main', 'unpkg'] }
      }
    ],
  },

@antonk52 It works, But It might lead to a series of problems, such as resolution strategy for another module changes. Here is a better solution.
  module: {
    rules: [
      {
        test: /redux$/,
        resolve: { mainFields: ['module', 'main', 'unpkg'] }
      }
    ],
  },

@antonk52 It works, But It might lead to a series of problems, such as resolution strategy for another module changes. Here is a better solution.
// webpack.config.js
module.exports = {
  // ...
  rules: [{
    test: /redux$/,
    resolve: {
      mainFields: ['module', 'main', 'unpkg']
    }
  }]
}

@antonk52 It works, But It might lead to a series of problems, such as resolution strategy for another module changes. Here is a better solution.
// webpack.config.js
module.exports = {
  // ...
  rules: [{
    test: /redux$/,
    resolve: {
      mainFields: ['module', 'main', 'unpkg']
    }
  }]
}

I am using parcel to build the application, in my case how can i able to add this to fix the issue.


Verify ALU

Yeah, simple. Add a + b, make sure it works :)
Write a test run for Icarus to check it.
Let's NOT concentrate on the flag setting logic for now, it's complicated. Check CLA.

There seems to be extra carry crawling through all the guts somehow.

Took most of the ALU apart, but still 5+7 = 8 lol....

Let's move on.

I suspect there's a bug somewhere in the Carry generator.

Better:

But still not very well (77+35=144):

Issue in SET/RES/DAA random logic.

Fixed.

@Rodrigodd,
Hi, I fixed 2 bugs in ALU.v, you might be interested.

Now the ALU should be adding things up correctly :)

Good work! I should be able the test the ALU when progressing more in the dmg-sim integration. I am focusing in running dmg-sim's quickboot.bin for now, which is currently stuck in writing to memory (#239).

Closing this one :)


Rework formatting

The current formatting code is a huge blob of spaghetti with barely any structure and full of hacks.
Things to consider:

make it more modular
drop building green trees and work with strings only
write more tests to make sure nothing breaks compared to the current behaviour

This is mostly done, new formatter options are yet to be documented on the website.

People are asking me on the formatting front if it's possible to not linebreak if there's just one item in the list.
E.g. stick with this:
sp-core = { git = "https://github.com/paritytech/substrate", branch = "master", features = ["std"]  }
rather than what currently happens:
sp-core = { git = "https://github.com/paritytech/substrate", branch = "master", features = [
    "std",
]  }

Ah it was hitting the line width. Thank you so much for this crate!


Add non-english charatcher support

That is incorrect.
Also, such a change has to come with tests, showing that it can match several languages, but nothing else.

May that dumb, but I don't know how to make unit tests.

Then I just updated the regex to match only 1 char.

Are you serious ? LMAO

@midnio Thank you for trying to help. I hope this won't dissuade you from contributing to open-source in the future, when you have improved your skills.

@erezsh Actually programming for 3 years (I'm 12-13 yo tho) but I'm still new to regex, that's normal :sweat_smile:

Then i'll try to implement it for myself first and open another pull request.


Gh 1793 Moved OperationDetail and OperationField to outer classes

Fixes #1793

Closing this PR because it contains a breaking change and therefore can't go into the next release.

Started to investigate but looks like it was superseded by #2336


SkiaRenderer and SkiaTexture not working together

After placing a SkiaTexture into a patch which uses a SkiaRenderer connected to a RenderEntity the drawn text disappears.
See attached patch
MultipleSkiaRenderersIssue.zip

Just checked with 2021.4.5 and works fine.


Servlet mapping for a._f url pattern and servlet class for file upload is not been added

entries added


Pre-built binary for darwin/arm64 wasn't released at v0.6.44

https://github.com/container-tools/spectrum/releases/tag/v0.6.44

spectrum_0.6.44_Darwin_arm64.tar.gz wasn't released.
https://github.com/container-tools/spectrum/actions/runs/9543698903/job/26300819613#step:7:30
         • DEPRECATED: skipped darwin/arm64 build on Go < 1.16 for compatibility, check https://goreleaser.com/deprecations/#builds-for-darwinarm64 for more info.

https://goreleaser.com/deprecations/#builds-for-darwinarm64

I'll send a pull request to resolve this issue soon.


Need multi language

Hello
Thanks for this remote. Need more language for this remote.
Thank you.

Yes we do, we will always need more languages for the remote. If you'd like to add a specific translation, please submit a PR.


quickSuggestions stop working when triggerCharacters from another completion provider contain a-z since 1.37.0

I am not sure if this undocumented change in 1.37.0 (comparing to 1.36.1) is intended, but it surely causes some issues.

Version: 1.37.0 (user setup)
Commit: 036a6b1d3ac84e5ca96a17a44e63a87971f8fcc8
Date: 2019-08-08T02:33:50.993Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17763
Steps to Reproduce:

Write an extension which contributes a completion item provider.
Add a-z character to triggerCharacters.
Run vscode with that extension. Now the default completion provider will not trigger on key type. (Still triggers on ctrl+space).

Does this issue occur when all extensions are disabled?: No
Example extension code:
import * as vscode from "vscode";

export async function activate(context: vscode.ExtensionContext) {
    const jsprovider = {
        async provideCompletionItems(document: vscode.TextDocument, position: vscode.Position, token: vscode.CancellationToken, completionContext: vscode.CompletionContext): Promise<vscode.CompletionItem[] | vscode.CompletionList> {
            return null;
        },
        resolveCompletionItem(): vscode.ProviderResult<vscode.CompletionItem> {
            return null;
        },
    };
    const triggerCharacters = [".", "/", "@", "<", "=", "_", "$", "a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m", "n", "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z"];
    context.subscriptions.push(vscode.languages.registerCompletionItemProvider({ language: "javascript", scheme: "file" }, jsprovider, ...triggerCharacters));
}

Completions marked by a yellow star are provided by a third-party plugin. Please notice how completion results changed before and after a-z characters in triggerCharacters are removed.

Maybe related to https://github.com/microsoft/vscode/issues/76354 (which is a good bug fix). Generally, I would describe the behaviour as correct because trigger characters only target certain providers (those that contribute said characters) but the design is clearly for non-word characters like . or >, e.g. trigger member completion, and not for all characters (that's what quick suggest is for)

@felixhao28 What's the reason for adding trigger characters a-z?

So if I understand it correctly, every completion provider will be triggered on characters a-z because quick suggest (unless turned off in the settings). Trigger characters are simply additional characters that triggers the completion other than a-z. By design, trigger characters should not overlap with quick suggest triggers (a-z).
If so, adding a-z to trigger characters was a mistake.

So if I understand it correctly, every completion provider will be triggered on characters a-z because quick suggest (unless turned off in the settings).

Yes, whenever a "word" is typed (the languages defines what a word is, but generally it's a-z), suggestions are triggered. Additional trigger characters are for scenarios like member completions, e.g console. should trigger suggestions to console.log, console.warn etc

I pushed an additional jsdoc comment to clarify trigger character and how to use them.


Where can I find some mor infos about this?

I test it in my enviroment and didn't see a usefull result?!
https://github.com/camunda/camunda-modeler/blob/c2626b39ad22fc97387c7813ab95528d5c8e1d85/resources/element-templates/xss.json#L21

What is your request about in terms of our clearly defined issue templates?


Recipe app project

Project requirements

You should follow the layout of the wireframes provided. You should personalize the rest of the design including colors, typographies, spacings, etc.
Login page and registration page:

Should be built with Devise.

Food list (only for a group that has less than 3 members):

Should display a list of food added by the logged-in user as in the wireframe (display also quantity of a given food).
Should lead to a form that allows users to add new food.

Recipes list:

Should display a list of recipes created by the logged-in user as in the wireframe.
Should lead to recipe details.
If the user is the owner of the recipe, should allow the user to delete it.

Public recipe list:

Should display a list of all public recipes ordered by newest as in the wireframe.
Should lead to recipe details.

Recipe details:

Should display a toggle button that allows for a recipe to be made public or private.
If the recipe is public or the user is the owner of the recipe, should display the recipe details as in the wireframe.
If the user is the owner of the recipe, should lead to the form that allows the user to add new food.

General shopping list view (only for a group that has less than 3 members):

Should show the list of food that is missing for all recipes of the logged-in user (compare the list of food for all recipes with the general food list of that user).
Should count the total food items and total price of the missing food.

Make sure there are no N+1 queries happening.
Create a navigation menu that allows users to open all of the pages you created.
Write unit and integration tests

Hey @Qoosim Thanks for the review ❤

You're most welcome
On Sat, Jul 1, 2023, 5:17 AM Williams Serubiri @.***>
wrote:

Hey @Qoosim https://github.com/Qoosim Thanks for the review ❤
—
Reply to this email directly, view it on GitHub
https://github.com/veronica365/recepies-app/pull/21#issuecomment-1615458597,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGK5QOGX2W56N47RVFMZ3UDXN6QFVANCNFSM6AAAAAAZYKUL6U
.
You are receiving this because you were mentioned.Message ID:
@.***>


Login Page

closes #1

Hey , @Kanishk3813  Can i get any preview ?? u can use vercel or netlify for it??

Sure, here's the link: https://login-theta-woad2.vercel.app

Thanks ,
LGTM.


Added multiple instances support to calendar module

Adds multiple instance support to calendar as described in issue #1109

Closed. See https://github.com/MichMich/MagicMirror/issues/1109 for more info.


Allow personal statement to be saved even if over word limit

One of the most common errors shown within our service is when people submit a personal statement that is over the 600 word limit.
This happens even though we have a feature which displays the number of words left as you type, and turns the border of the field red and displays an red message if you are over the word limit.
When you submit an answer that is over the word limit, you're returned to the same page with an error message at the top. The answer is not saved until you edit it down to under the word limit.
Our assumption is that either users are not seeing the as-you-type word count, or they are seeing it but want to save anyway and edit it down later.
This PR explores how we might allow users to save a personal statement even if it is over the word limit, but still not allow them to submit their application until it has been edited to within the word limit.
Other minor changes:

The review page no longer shows "Why you want to be a teacher" within the summary list - this repeats the h1 and uses up extra horizontal space.
Error message has been reworded from "Tell us why you want to be a teacher must be 600 words or fewer" to "Your answer must be 600 words or less
Change link text changed from "Change" to "Edit your answer"

🗂 Trello card
➡ Related: Update personal statement flow and return to application if empty
How it works
When pressing the green "Continue" button on the personal statement form, the answer is always saved and the user is redirected to the review page.
On the review page, if the answer is above the word count, then an error message is shown, and the user cannot mark the section as completed.
If the answer is below the word count, then the section can be marked as completed.
If a user marks the section as completed, but then edits their answer to be above the word count, then the section is marked as incomplete again.
Screenshots
Before: Error shown above the form itself

Before: Section review page

After: Section review page showing an error

After: Section review page showing no errors

After: Section review page showing no errors (mobile view)

Notes for reviewers
Firstly, this ended up requiring a lot more code changes than I expected, so please review the code carefully and let me know if you spot any mistakes, confusing code, or opportunities for improvements.
Please also check it in browser! This pattern has been applied to both the old (2 personal statement sections) and new (combined personal statement) flows, so you'll need to check both by turning the feature flag on and off.
Also worth checking on mobile viewports, and seeing if there are any edge cases or flows I'd not thought of.

@frankieroberto ah ok, so basically I'm still learning about the intricacies of the design system!
For no. 2, I'd expect that Continue button to go back to the task list page. At least that's what makes the most sense to me.

I see, I see. I wonder if we take a similar approach then to what we did with the 'combined' personal statement message to say they don't need to change anything. So like: 'Your statement must be 600 words or less. You can edit your statement now, or come back later.' or 'Your statement must be 600 words or less. You do not have to edit it now, but you must edit it before you submit your application.'

Ah ok, maybe they have a good reason for it to be like that then. Maybe mine are a bit wordy but maybe slightly clearer?...

Closing to fix review app

This looks good to me and is working on both merged statement and where we still have the 2 questions. Works on mobile too. Originally I suggested to say 'Edit your statement' instead of 'answer' however, where we still have 2 questions, I don't think 'statement' quite makes sense. So happy to leave that as 'answer' for everything.


Layout related FlutterErrors do net get reported in release mode

Steps to Reproduce

Build an app in release mode with any of these errors.
Report all errors from FlutterError.onError to a service like Sentry or Firebase Crashlytics.
Trigger one of the errors from step 1.

The layout error does not get reported.
Expected results:
The error should be reported.
Actual results:
The error does not get reported.
More context
The Flutter docs state, that some debug and diagnostic information gets stripped in release mode, such as

https://flutter.dev/docs/testing/build-modes
https://api.flutter.dev/flutter/foundation/FlutterError/diagnostics.html

However this doc states, that every error gets catched.
So another question is, how do I catch and report layout errors in release mode?

Hi @ueman
As far as I know UI errors are not sent to FlutterError.onError. Please see https://api.flutter.dev/flutter/widgets/ErrorWidget-class.html.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

In debug mode they are reported to FlutterError.onError. So that's kinda the issue. Is there a page where this is better documented?

Hi @ueman
Can you please provide your flutter doctor -v a minimal complete reproducible code sample?
Thank you

Sure.

  `flutter doctor -v`
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale de-DE)
    • Flutter version 1.22.5 at /Applications/flutter
    • Framework revision<PHONE_NUMBER> (8 days ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/jonas/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Users/jonas/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6953283/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    • CocoaPods version 1.8.4

[!] Android Studio (version 4.1)
    • Android Studio at /Users/jonas/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6953283/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.17.0

[✓] Connected device (1 available)
    • SM A405FN (mobile) • R58MC11CB7R • android-arm64 • Android 10 (API 29)

! Doctor found issues in 1 category.

Example time
I guess I found the error myself.
In order for FlutterError.onError to be called, you have to call WidgetsFlutterBinding.ensureInitialized(); before.
Otherwise only the callback for the ErrorWidget will be called. It is also an issue in debug and release mode.
Still I think this should be documented somewhere.
pubspec.yaml
name: crashy1
description: crashy1

publish_to: 'none' # Remove this line if you wish to publish to pub.dev

version: 1.0.0+1

environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  cupertino_icons: ^1.0.0
  share: ^0.6.5+4

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true

main.dart
import 'package:flutter/material.dart';
import 'package:share/share.dart';

void main() {
  // if the following line gets removed, FlutterError.onError will not be called anymore
  WidgetsFlutterBinding.ensureInitialized();
  FlutterError.onError = errorHandler;
  ErrorWidget.builder = errorWidgetBuilder;
  runApp(MyApp());
}

void errorHandler(FlutterErrorDetails details) {
  final message = details?.exceptionAsString() ?? "no message";
  Share.share("onError " + message);
}

Widget errorWidgetBuilder(FlutterErrorDetails details) {
  final message = details?.exceptionAsString() ?? "no message";
  Share.share("builder " + message);
  return Text(message);
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  Widget builderWidget = Text('something');

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Title'),
      ),
      body: Column(
        mainAxisAlignment: MainAxisAlignment.start,
        children: <Widget>[
          RaisedButton(
            // only works in debug mode, because it is an AssertionError
            child: Text('return null widget (ErrorWidget.builder)'),
            onPressed: () {
              setState(() {
                builderWidget = null;
              });
            },
          ),
          RaisedButton(
            child: Text('throw inside build method'),
            onPressed: () {
              setState(() {
                builderWidget = ThrowingWidget();
              });
            },
          ),
          RaisedButton(
            child: Text(
                'throw inside build method with slivers'),
            onPressed: () {
              setState(() {
                builderWidget = SimpleSliver();
              });
            },
          ),
          ColoredBox(
            color: Colors.amberAccent,
            child: SizedBox(
              width: 300,
              height: 100,
              child: Builder(
                builder: (context) {
                  return builderWidget;
                },
              ),
            ),
          ),
        ],
      ),
    );
  }
}

class ThrowingWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    throw Exception('foo bar');
  }
}

class SimpleSliver extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CustomScrollView(
      semanticChildCount: 1,
      slivers: <Widget>[
        SliverList(
          delegate: SliverChildBuilderDelegate(
            (BuildContext context, int index) {
              throw Exception('foo bar');
            },
            semanticIndexCallback: (Widget widget, int localIndex) {
              if (localIndex.isEven) {
                return localIndex ~/ 2;
              }
              return null;
            },
            childCount: 1,
          ),
        ),
      ],
    );
  }
}

Reproducible on lates master channel.
flutter doctor -v
[✓] Flutter (Channel master, 1.26.0-2.0.pre.86, on Mac OS X 10.15.7 19H2 darwin-x64, locale en)
    • Flutter version 1.26.0-2.0.pre.86 at /Users/pedromassango/dev/SDKs/flutter_master
    • Framework revision b793285329 (3 days ago), 2020-12-18 10:14:36 -0800
    • Engine revision 7983c6fda0
    • Dart version 2.12.0 (build 2.12.0-167.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 52.0.5
    • Dart plugin version 203.5981.152

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • Mac OS X 10.15.7 19H2 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 87.0.4280.88

! Doctor found issues in 1 category.
Process finished with exit code 0

This is WAI. These errors are wrapped in an assert which will get stripped out in release mode.


Rviz crash using VirtualBox

[rviz_ubuntu_VirtualBox_12943_201842339635357345-5] process has died [pid 13001, exit code -11, cmd /home/ubuntu/ws_moveit/devel/lib/rviz/rviz -d /home/ubuntu/ws_moveit/src/panda_moveit_config/launch/moveit.rviz __name:=rviz_ubuntu_VirtualBox_12943_201842339635357345 __log:=/home/ubuntu/.ros/log/c6b4f42a-3fa5-11e8-a4ca-080027304e5a/rviz_ubuntu_VirtualBox_12943_201842339635357345-5.log].
log file: /home/ubuntu/.ros/log/c6b4f42a-3fa5-11e8-a4ca-080027304e5a/rviz_ubuntu_VirtualBox_12943_201842339635357345-5*.log

I tried installing rviz from source as well as from deb and neither worked

I just emailed the guy from CU who ran this stuff


Fixes 4218: Prevent occasional double url entry on tests

Summary

Added a couple checks for the OuiaSafe to hopefully prevent double url input issues on tests.

Testing steps

https://issues.redhat.com/browse/HMS-4218


Fix typo in TcpStream and UdpSocket documentation

Fixed a small typo of 'writey' where it was expected to be 'ready' in TcpStream and UdpSocket documentation.

Thanks!


MongoShell command to create TTL index, not JS code snippet.

[Enter feedback here]
JavaScript example:
JavaScript
Copy
globaldb:PRIMARY> db.coll.createIndex({"_ts":1}, {expireAfterSeconds: 10})
{
"_t" : "CreateIndexesResponse",
"ok" : 1,
"createdCollectionAutomatically" : true,
"numIndexesBefore" : 1,
"numIndexesAfter" : 4
}

This is a MongoShell command, not a JavaScript snipped, please correct the name.
Also if there is any JS code example, please add to code example so it will be more complete. Thanks!

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

ID: 0196349a-477b-281e-4143-9f5e51713327
Version Independent ID: a6abda68-9066-0199-1b2b-219a8a0ca0cb
Content: MongoDB per-document TTL feature in Azure Cosmos DB
Content Source: articles/cosmos-db/mongodb/mongodb-time-to-live.md
Service: cosmos-db
Sub-service: cosmosdb-mongo
GitHub Login: @gahl-levy
Microsoft Alias: gahllevy

@MS-jeremy Thank you for the feedback. This is being assigned to the content author to evaluate and update as appropriate.

@AnuragSharma-MSFT  @gahl-levy , can you please check this doc issue?

assign:markjbrown

#assign:markjbrown

Thank you for your feedback and apologies for the long delay here.
I have updated this to correct the text to say MongoShell and not Javascript. Also fixed the snippit syntax hint as well.
This is now in a PR and merged. Should publish by tomorrow AM.
Thanks again.
#please-close