fix: render ipywidgets property as a vue child component

There were two things that could go wrong when rendering an ipywidget as a child of the vue component using the createObjectForNestedModel. First, since create_child_view is async, the vue component could be destroyed before the child view is created. In that case, we should not attach the view, but directly remove it again.
Second, child views were not removed properly since we did not listen to the destroyed/beforeDestroy life-cycled events of the vue component.
We now remove the ipywidget view when the vue component is destroyed, but only when it's already created.

i guess we need to pin black?


Unknown issue...

When I create a quest I can fill in all the boxes perfectly, no problem there. The only issues are when I made a quest I now get spammed with the letter 'a' in chat... Also there apparently is an internal error when I do ./questadmin reload. It's quite a vital command as you probably know. We on FlameSurvival RPG use quests a lot and consider it one of our main plugins, the reload issue only appears when we attempt to save a quest and reload them. Exiting the quest without saving has no error.
We currently use [this] (https://www.spigotmc.org/resources/quests.3711/) version of Quests, and we're running 1.9 Minecraft.
With the reload issue we get an NPE in console [logs.] (http://pastebin.com/gPAELr9p)
Any advice would be appreciated,
-Rookie
@FlyingPikachu

One of your NPCs is invalid or there is an issue with Citizens. Make sure Citizens is setup properly and all of your NPC ids in quests.yml are correct.

Thanks, I removed a bunch of quests that could only be found in 'quests.yml' for some reason. The commands ./questadmin reload still won't execute correctly but I do have a hunch like yours that the problem is in the Citizens plugin.

Here is a thread with a similar error: https://www.spigotmc.org/threads/citizen-2-0-17-plugin-cant-work-on-1-9.132505/
The current suggestion seems to be updating Spigot, then Java. Since this problem is outside the scope of Quests, I must close this issue. If the problem persists after updating, please open a new ticket. Thanks!

Thanks @FlyingPikachu, you've been a great help. :3


Quietly adding the lbry-desktop app to autostart on Linux is undesirable behavior

On Windows it might be normal for applications to quietly add itself to autostart without asking the user for consent. On Linux and other FOSS operating systems this is considered intrusive and undesirable behavior.
It is fine if the application has the option. but it should only add itself to autostart if the user gives it the OK to do so.
The solution:

On first start show a popup and ask the user if it is ok to add itself to autostart detailing all the benefits of doing so. (Quicker load times, helping the LBRY network etc..)
Only of the user says OK add the app to autostart, otherwise don't.

Thanks for filing!

2+ years past and it still open issue?
Not just that, you cant even get it right after all this time:
$ cat ~/.config/autostart/lbry.desktop
[Desktop Entry]
Type=Application
Version=1.0
Name=lbry
Comment=lbrystartup script
Exec=/tmp/.mount_LBRY_0MtBwKy/lbry --hidden
StartupNotify=false

# while rebooting system:
<timestamp> systemd-xdg-autostart-generator[1656]: Exec binary '/tmp/.mount_LBRY_0MtBwKy/lbry' does not exist: No such file or directory
<timestamp> systemd-xdg-autostart-generator[1656]: /home/myusername/.config/autostart/lbry.desktop: not generating unit, error parsing Exec= line: No such file or directory

At least nowadays it gets removed when user removes said check from certain box.
Try detecting how app is being run, native install or appimage or whateverelse... Or better yet, remove it as OP suggested.


FastAPI 0.89.0 support

Hello,
I was wondering what is the support intended for FastAPI. I see that here, in the repo, you have this line in the readme file:

Fastapi: >=0.78, <0.90

But on pypi you have this:

Fastapi: >=0.78, <0.89

So when I am trying to test your package with FastAPI 0.89 I can't actually install it. Just for a quick test I downloaded the code and used it like that for a proof of concept and it seems to be working fine with 0.89, but I would like to install it "properly" before deciding if we can use your library.
Really appreciate your work,
Thank you!

Side note: only after I made some changes locally to get searching and sorting in joined tables I saw that you have something very similar prepared in this PR, with the only difference that I used dot as a separator in my approach (as there's a smaller chance it will be part of a real column name and it's more in line with how you would use such relationships).
Do you think that those updates could be part of a future release that can be installed for recent versions of FastAPI?

@mihaiz-ogre I just made a release with updated dependencies 👍🏻

with the only difference that I used dot as a separator in my approach

I used the double underscore separator to be consistent with related fields filtering. I'll try to make it configurable if it doesn't add too much complexity.

@mihaiz-ogre I just made a release with updated dependencies

@arthurio awesome, thank you!


bazel build nvcc: nvcc fatal : Unsupported gpu architecture 'compute_21'

After I executed the command
bazel build -c opt --config=cuda //tensorflow/cc:tutorials_example_trainer
I get an error like
ERROR: /home/rajarshee/tensorflow/tensorflow/core/kernels/BUILD:517:1: error while parsing .d file: /home/rajarshee/.cache/bazel/_bazel_rajarshee/0d043bf46cad9f31127eb8d06453610d/tensorflow/bazel-out/local_linux-py3-opt/bin/tensorflow/core/kernels/_objs/adjust_contrast_op_gpu/tensorflow/core/kernels/adjust_contrast_op_gpu.cu.d (No such file or directory). nvcc warning : option '--relaxed-constexpr' has been deprecated and replaced by option '--expt-relaxed-constexpr'. nvcc fatal   : Unsupported gpu architecture 'compute_21' Target //tensorflow/cc:tutorials_example_trainer failed to build
I provided 2.1 gpu compute capability in ./configure earlier.

Thanks to @zheng-xq, we figured out that compute_21 is not a valid architecture (instead it is a virtual architecture). We need to provide a way to pass a compute capability of 2.0 to nvcc. Currently our build scripts do not support that, but you can hack in support by editing the crosstool wrapper. After you rung ./configure, replace the loop on L253--256 with the following:
nvccopts += r'-gencode=arch=compute_20,\"code=sm_21,compute_20\" '

While the previous is no more appearing, a new incompatibility with my gcc version has occured. please note that i have both 5.2 and 4.9 versions of gcc and my cuda located at /usr/local/cuda has the gcc already linked to /usr/bin/gcc-4.9
error -- unsupported GNU version! gcc 4.5 and up are not supported!

And after I changed gcc to gcc-4.9 here the error was gone but this error came
9 errors detected in the compilation of "/tmp/tmpxft_00005b89_00000000-7_adjust_contrast_op_gpu.cu.cpp1.ii". ERROR: /home/rajarshee/tensorflow/tensorflow/core/kernels/BUILD:517:1: output 'tensorflow/core/kernels/_objs/adjust_contrast_op_gpu/tensorflow/core/kernels/adjust_contrast_op_gpu.cu.o' was not created. ERROR: /home/rajarshee/tensorflow/tensorflow/core/kernels/BUILD:517:1: not all outputs were created. Target //tensorflow/cc:tutorials_example_trainer failed to build

@rajarsheem, you'll have to post the errors here. In general, TF is tested on compute_35. While compute_20 may work for now, which I am not sure, there is no guarantee that it will keep working in the long term.

@zheng-xq
INFO: Found 1 target... ERROR: /home/rajarshee/tensorflow/tensorflow/core/kernels/BUILD:212:1: error while parsing .d file: /home/rajarshee/.cache/bazel/_bazel_rajarshee/0d043bf46cad9f31127eb8d06453610d/tensorflow/bazel-out/local_linux-py3-opt/bin/tensorflow/core/kernels/_objs/gather_op_gpu/tensorflow/core/kernels/gather_op_gpu.cu.d (No such file or directory). nvcc warning : option '--relaxed-constexpr' has been deprecated and replaced by option '--expt-relaxed-constexpr'. In file included from third_party/gpus/cuda/include/cuda_runtime.h:76:0,                  from <command-line>:0: third_party/gpus/cuda/include/host_config.h:115:2: error: #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!  #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!   ^ Target //tensorflow/cc:tutorials_example_trainer failed to build INFO: Elapsed time: 1.447s, Critical Path: 1.19s

unsupported GNU version! gcc versions later than 4.9 are not supported!

This problem is that your GCC and NVCC is not compatible. Which Cuda SDK
are you using? Could you try the latest Cuda 7.5 and GCC 4.8, which are
heavily tested.
Thanks.
-XQ
On Mon, Mar 14, 2016 at 1:04 PM, Rajarshee Mitra<EMAIL_ADDRESS>wrote:

@zheng-xq https://github.com/zheng-xq
INFO: Found 1 target...
ERROR: /home/rajarshee/tensorflow/tensorflow/core/kernels/BUILD:212:1:
error while parsing .d file:
/home/rajarshee/.cache/bazel/_bazel_rajarshee/0d043bf46cad9f31127eb8d06453610d/tensorflow/bazel-out/local_linux-py3-opt/bin/tensorflow/core/kernels/_objs/gather_op_gpu/tensorflow/core/kernels/gather_op_gpu.cu.d
(No such file or directory).
nvcc warning : option '--relaxed-constexpr' has been deprecated and
replaced by option '--expt-relaxed-constexpr'.
In file included from third_party/gpus/cuda/include/cuda_runtime.h:76:0,
from :0:
third_party/gpus/cuda/include/host_config.h:115:2: error: #error --
unsupported GNU version! gcc versions later than 4.9 are not supported!
#error -- unsupported GNU version! gcc versions later than 4.9 are not
supported!
^
Target //tensorflow/cc:tutorials_example_trainer failed to build
INFO: Elapsed time: 1.447s, Critical Path: 1.19s
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/1498#issuecomment-196498691
.

I am using Cuda 7.5 and two gcc versions installled - 4.9 and 5.2. the cuda located in /usr/local/cuda has it's gcc linked to gcc-4.9. (the gcc incompatibility issue earlier occured with theano and was solved after the linking)

I don't think GCC 4.9 is officially supported by Cuda 7.5. Look at
include/host_config.h
#if defined(GNUC)
#if GNUC > 4 || (GNUC == 4 && GNUC_MINOR > 9)
#error -- unsupported GNU version! gcc versions later than 4.9 are not
supported!
#endif /* GNUC > 4 || (GNUC == 4 && GNUC_MINOR > 9) */
You are better off with GCC 4.8 and use that instead.
Thanks.
-XQ
On Mon, Mar 14, 2016 at 1:19 PM, Rajarshee Mitra<EMAIL_ADDRESS>wrote:

I am using Cuda 7.5 and two gcc versions installled - 4.9 and 5.2. the
cuda located in /usr/local/cuda has it's gcc linked to gcc-4.9. (the
gcc incompatibility issue earlier occured with theano and was solved after
the linking)
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/1498#issuecomment-196502623
.

@zheng-xq  upto 4.9 is supported.
`#if GNUC > 4 || (GNUC == 4 && GNUC_MINOR > 9)
#error -- unsupported GNU version! gcc versions later than 4.9 are not supported!`

I stand corrected. It is a good idea to check which version of your GCC was
actually used. A few things you can try:

You can add "-s" to your bazel to print out the crosstools command line.
Add "--copt=--cuda_log", which is passed to crosstools to print out the
nvcc command line.

That should be enough to see which version of the gcc was actually used.
On Mon, Mar 14, 2016 at 1:42 PM, Rajarshee Mitra<EMAIL_ADDRESS>wrote:

@zheng-xq https://github.com/zheng-xq upto 4.9 is supported.
`#if GNUC > 4 || (GNUC == 4 && GNUC_MINOR > 9)
#error -- unsupported GNU version! gcc versions later than 4.9 are not
supported!`
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/1498#issuecomment-196512886
.

@zheng-xq  May this be of help.
http://paste.ubuntu.com/15387128/
(note that default /usr/bin/gcc is actually the 5.2 one!)

I think that might be the problem. The default gcc 5.2 is used instead. You
have a few options:

Symlink your default /usr/bin/gcc to gcc 4.9.
Modify
third_party/gpus/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc to
point to your gcc-4.9 location.

On Mon, Mar 14, 2016 at 2:18 PM, Rajarshee Mitra<EMAIL_ADDRESS>wrote:

@zheng-xq https://github.com/zheng-xq May this be of help.
http://paste.ubuntu.com/15387128/
(note that default /usr/bin/gcc is actually the 5.2 one!)
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/1498#issuecomment-196524722
.

Sorry. A mistake! Default gcc version is 4.9.3

@zheng-xq
I changed all the variables below
CPU_COMPILER,GCC_HOST_COMPILER_PATH and LLVM_HOST_COMPILER_PATH by replacing gcc with gcc-4.9. While the gcc issue seems to be vanished, this came:
5 errors detected in the compilation of "/tmp/tmpxft_00005de0_00000000-7_sparse_tensor_dense_matmul_op_gpu.cu.cpp1.ii".
Full output:
http://paste.ubuntu.com/15387425/

Unfortunately, Eigen starts to pick up warp shuffle capabilities recently,
which requires compute_30 support.
On Mon, Mar 14, 2016 at 3:09 PM, Rajarshee Mitra<EMAIL_ADDRESS>wrote:

@zheng-xq https://github.com/zheng-xq
I changed all the variables below
CPU_COMPILER,GCC_HOST_COMPILER_PATH and LLVM_HOST_COMPILER_PATH by
replacing gcc with gcc-4.9. While the gcc issue seems to be vanished, this
came:
5 errors detected in the compilation of
"/tmp/tmpxft_00005de0_00000000-7_sparse_tensor_dense_matmul_op_gpu.cu.cpp1.ii".
Full output:
http://paste.ubuntu.com/15387425/
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/1498#issuecomment-196542169
.

all I can pray for is to officially add the support for compute_21 :'(

@benoitsteiner to comment on the Eigen request.
@rajarsheem in this thread wants to support compute_20 device. However, since Eigen starts to use warp shuffling instructions, which is only available for compute_30 devices and later, it won't work.
Benoit can tell you whether Eigen will support older devices without the warp shuffling or not.

Official support for compute_20 device will be highly appreciated.
For now, let's count on @benoitsteiner ; may he throw some light.

I'm having the same problem. Did someone find a solution to make Tensorflow work with compute capability 2.1 GPU's ?

Eigen only supports compute 3.0 and above. Old GPUs tend to run slower than a decent CPU these days, so there is little incentive to remove this restriction at the moment.
@rajarsheem @marcdumon: What are your use cases for GPUs that only support compute capabilities 2.1 ?

Automatically closing because there was no response. Please reopen if it is still an issue.

@benoitsteiner : Have witnessed that computations with my gpu (2.1) tend to be much faster than with just CPU when I used previously with Theano. Even that performance improvement can be highly beneficial.

@rajarsheem I have fixed the Eigen reduction to remove the dependency on warp shuffles. The next time we update TensorFlow to pick up the latest version of Eigen it should be possible to run with older gpus.

hey! @benoitsteiner When it could happen? =)

@AlexJoz i checked that the code now compiles with architecture 2.0 and cuda 7.0.


Can't see Last Posts Info

Hi, I can't see last posts info column on my right side pannel, what's wrong? I run bash init.sh already.
My repo: https://github.com/virgulco/virgulco.github.io Live: https://virgul.co

Thank you for your kindly support.

I took a look at the contents of your blog repository and found that init.sh is an old version that did not trigger the last updated script.
To solve this problem, update the following files of template:

_scripts  (Python3.5 or above is required)
init.sh

In additional, the run.sh and build.sh should be updated, too.

 Thank you!

The mktemp command
I wrote the bash scripts with GUN/Linux environment (althought my machine is MacBook Pro), so they haven't been tested on Mac's original mktemp command before. Thanks for report this problem.
The argument -t of command mktemp holds different meaning bettween Darwin(macOS) and GUN/Linux. So just simply remove the -t options, the tool scripts in this project will work well on Mac and Linux.
Fixed at: 3540feb32514984e34c195e68cf8b6b4fe30cdde
Why the Lastmod of Posts still not shown
The other template code of your project is not updated, which I didn't notice that yesterday. So that the lastmod of posts still not shown on your site.
The lastmod list implemented here:
https://github.com/cotes2020/jekyll-theme-chirpy/blob/master/_includes/panel.html#L11
Due to the project code has been updated a lot since the day you cloned it, to reduce other unnecessary problems in the future, please update all other parts of the template code.

Thanks a lot!


Update sourcekit xfails for a fixed code completion issue

It now hits a different crash at a later offset in the same file.

@swift-ci test


Stream from outside should not be closed

I'm trying to use this class in a small WCF project where I don't want to add another 3rd party lib.
I want to use the stream mode for packaging and then send the zip stream to another machine. Unfortunately the internal zipfilestream is closed and disposed within the Close() method. If I don't close the zip, then the EndRecord is not written. But when I close the zip then the underlying stream is closed.
My suggestion is to set a flag when a filename is provided for Open() or Create(). When this is set, then ZipFileStream.Dispose(); and ZipFileStream = null; in function Close() should be omitted.
I have a working solution here and can provide a pull request later.

Hi, sounds reasonable, please provide the pull request.

Really, this is a problem.
This class should NOT close a stream which it didn't create.
I'm using it on a application, to create a zipfile (in a memory stream) which I'm going to send to my enduser.  Right now,I can't send him a valid file, because I can't use Close to save the central directory information.
If you don't want to change this comportment, can you at least add a method to save  the central directory information without closing the stream ?

I fixed it right now creating an optional parameter on Close. Maybe it would have been better to create a CloseWithoutClosingExternalStream methode ? (not sure..)

If you are using a memory stream, you can always recreate another memory stream based on your underlying byte array. Something like:
memoryStream = new MemoryStream(memoryStream.ToArray());


maximumFileSizeToCacheInBytes to 5Mb

The main javascript file is not being cached by the service worker be cause it passes the 4Mb limit.
The problem here is the server updates. If you update the server with a new build, the page won't open because the service worker will try to fetch and old javascript file which doesn't exist anymore.
It can be stuck forever. For it to update you have to shutdown the browser (not just refresh the page or close the tab/window) so that all clients release the active service worker.
If we cache the main javascript we won't have this problem, the page will open and the popup for the update will appear.

I say we pick a higher number, like 10MB. Also let's make it proper 10MB (10 * 1024 * 1024).


Out-of-sync mouse scrolling in neovim diff mode with airline + 'set lazyredraw'

environment

neovim: 0.4.4 (Arch), and neovim master (ff749e3)
vim-airline: master
OS: Archlinux x86_64
Have you reproduced with a minimal vimrc: yes
What is your airline configuration: vanilla
terminal: tilix
$TERM variable: xterm-256color
does it happen in Vim: not tested

Minimal init.vim that can recreate the issue:
if empty(glob('~/.config/nvim/autoload/plug.vim'))
  silent !curl -fLo ~/.config/nvim/autoload/plug.vim --create-dirs
    \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
  autocmd VimEnter * PlugInstall --sync
endif

call plug#begin('~/.config/nvim/plugged')

Plug 'vim-airline/vim-airline'

call plug#end()

set mouse=a
set lazyredraw

Run nvim -d file1 file2, scroll the diff view up and down using the mouse on the left file.
actual behavior
The two files become out-of-sync and the file on the right becomes a mess.
expected behavior
The two files stays perfectly in sync all the time.
screen shot (if possible)

The two files used in my example are attached, but any two files that are different and are long enough should be able to trigger the issue.
log1.txt
log2.txt

vim-airline merely sets the statusline using some custom statusline atoms (which call vimscript functions internally). If you notice any scrolling issues, then this should be reported to vim or neovim with a clear reproduction (start from vim --clean)
In any case, I noticed something like what you described above. With :set mouse=a  and having the mouse over an inactive window (where the cursor is currently not), allows to scroll that window temporarily, while with the mouse on the active window, both windows are scrolled. I consider this a feature however. If you do not like this behaviour, use :set mouse= and have the terminal handle the scrolling event. Setting lazyredraw does not seem to make a difference here.
In any case, if you think this is a bug, it should be reported to neovim then.

@chrisbra, this is an actual issue, and only happens in the presence of vim-airline (It's not about only one window being scrolled if mouse is on inactive window, which is indeed intended, but about the file contents looking completely haywire). I'm facing this same issue on both Linux and macOS. Can you please look into it?

Also, FWIW, it happens only in nevoid, and not on vim. No other plugin I have (other than airline) causes this issue.

I still do not see how vim-airline should be involved. Please show exactly what happened with a minimal vimrc if possible

To reproduce:
Vimrc is the same as provided in the original issue (which just installs vim-airline, and sets mouse=a and lazyredraw)

Create two files called /tmp/a.txt and /tmp/b.txt using the command
head -c 5000 /dev/urandom | xxd | tee /tmp/a.txt | awk 'NR % 5' > /tmp/b.txt
This creates a.txt using some random bits, and deletes every fifth line of it to create b.txt.
Open them in diff mode using nvim -d /tmp/a.txt /tmp/b.txt
With your mouse pointer over the active window (left by default), scroll up and down fast repeatedly.
The output is now entirely messed up (in any sane output, every fifth line should have shown up as deleted)

that actually sounds like an neovim issue. Vim-airline merely sets the statusline, I don't know how it could affect scrolling issue. As a workaround, please do not set lazyredraw instead.


Re-apply TArgs to CSF render type

For #41
Fix issue where render() has Args as type for first argument.

📦 Published PR as canary version: 0.0.2--canary.43.5edcaf6.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Hi, just a friendly ping!  I'd really love to try out the 6.5.0 beta in my app at work, but so far I'm blocked on this.

:rocket: PR was released in v0.0.2-next.0 :rocket:

:rocket: PR was released in v0.1.0 :rocket:


dims/openstack-cloud-controller-manager no config in environment

2018-03-14 10:29:06.315888 | ubuntu-xenial-large | === RUN   TestRoutes
2018-03-14 10:29:06.315929 | ubuntu-xenial-large | --- SKIP: TestRoutes (0.00s)
2018-03-14 10:29:06.315987 | ubuntu-xenial-large | 	openstack_routes_test.go:34: No config found in environment
2018-03-14 10:29:06.316511 | ubuntu-xenial-large | === RUN   TestNewOpenStack
2018-03-14 10:29:06.316543 | ubuntu-xenial-large | --- SKIP: TestNewOpenStack (0.00s)
2018-03-14 10:29:06.316588 | ubuntu-xenial-large | 	openstack_test.go:464: No config found in environment
2018-03-14 10:29:06.316616 | ubuntu-xenial-large | === RUN   TestLoadBalancer
2018-03-14 10:29:06.316648 | ubuntu-xenial-large | --- SKIP: TestLoadBalancer (0.00s)
2018-03-14 10:29:06.316693 | ubuntu-xenial-large | 	openstack_test.go:476: No config found in environment
2018-03-14 10:29:06.316768 | ubuntu-xenial-large | === RUN   TestVolumes
2018-03-14 10:29:06.316815 | ubuntu-xenial-large | --- SKIP: TestVolumes (0.00s)
2018-03-14 10:29:06.316862 | ubuntu-xenial-large | 	openstack_test.go:540: No config found in environment

Have switched to new repo kubernetes/cloud-provider-openstack , the issue have been resolved in https://github.com/theopenlab/openlab-zuul-jobs/issues/101


API accepts any existing user for "authorUser" field

Currently, any API caller can put any user ID in the "authorUser" field, which means, people can comment in place of each other.
Neither the authorId nor the Created By fields have information about the original submitter of the comment based on authentication token.

@Mo9a7i so if I understood you correctly while making a PUT request you're able to change the authorUser field value. That was your observation?

@Mo9a7i I've made a test.
Got 2 users with ids 1 and 2.

Create comment for user with id 1
Try to update the comment using id 2 -> Results as 409. Expected
Try to update the comment using id 1 -> Results as 200. Expected.

See the attachments.
Can you please describe in more details what was the case?
Important note. If you're using default Strapi Content Manager endpoints we're not responsible for their behavior and changes made there. Usage of plugin endpoints described in the Readme.md is only supported and is going to be investigated.

Hello Boss,
The issue is with the original Post call
see screenshot below, the jwt token is for user 1250
I can submit with authorUser 505 for example

"strapi": "3.3.4",
"strapi-plugin-comments": "^1.0.0-beta.6",

Plugin is prepared to work with both, Strapi & non-Strapi users. That's why you're controlling explicit which user have to be assigned to the comment. It is not checking the jwt of logger user to not be strict with Strapi users only.

I have built a small hack, based on documentation and online solutions for the problem, have a look and if its good, just take it.

You would be welcome to contribute to the plugin also :)

async create(ctx) {
      let entity;
      let user = {};
      if (!ctx.state.user) { user.id = 88; } // here I have registered user called "Anonymous" that has id 88, so any unauthenticated request I give it user id 88, for complete anonymous, you can just move the if statement to the below if statement, and not add an author object to the data if there was no author.
      else { user = ctx.state.user; }

      if (ctx.is('multipart')) {
        const { data, files } = parseMultipartData(ctx);
        data.author = user.id;
        entity = await strapi.services.jokes.create(data, { files });
      }
      else {
        ctx.request.body.author = user.id;
        entity = await strapi.services.jokes.create(ctx.request.body);
      }

      return sanitizeEntity(entity, { model: strapi.models.jokes });
    },

You would be welcome to contribute to the plugin also :)

it would be an honor, I'm just trying to figure out your way of coding, so I can contribute the way that suites you.

Closing in relation to the raised feature request for v1.1.1.


App crashes immediately after launch

On MacBook Pro 16" 2019

Could you change the language to English, French, Spanish, or a Romanian please ? Thank you so much. Cannot read the error message.

"About This Hack" has been unexpectedly terminated.
Click on "Open Again" to start the program again. Click on "Report" to show further information and send a report to Apple.

Open Again
Report...
Ignore

Creating the report leads to the following:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               About This Hack [3016]
Path:                  /Applications/About This Hack.app/Contents/MacOS/About This Hack
Identifier:            app.netlify.0xCUBE.About-This-Hack
Version:               1.0.0 (1337)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2023-10-10 11:20:44.8569 +0200
OS Version:            macOS 13.4.1 (22F770820d)
Report Version:        12
Bridge OS Version:     7.5 (20P5060)
Anonymous UUID:        FBC0458E-F4CE-875A-3226-0B575496E39D

Time Awake Since Boot: 2600 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process:   exc handler [3016]

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   About This Hack               	       0x103df1701 0x103dde000 + 79617
1   About This Hack               	       0x103df1d97 0x103dde000 + 81303
2   About This Hack               	       0x103de2ce6 0x103dde000 + 19686
3   About This Hack               	       0x103de2bed 0x103dde000 + 19437
4   About This Hack               	       0x103de2c18 0x103dde000 + 19480
5   AppKit                        	    0x7ff803e1b33d -[NSViewController _sendViewDidAppear] + 50
6   AppKit                        	    0x7ff8046174e5 -[NSView _windowDidOrderOnScreen] + 67
7   AppKit                        	    0x7ff80461757b -[NSView _windowDidOrderOnScreen] + 217
8   AppKit                        	    0x7ff80461757b -[NSView _windowDidOrderOnScreen] + 217
9   AppKit                        	    0x7ff80461757b -[NSView _windowDidOrderOnScreen] + 217
10  AppKit                        	    0x7ff804630066 -[NSWindow _reallyDoOrderWindowAboveOrBelow:] + 2077
11  AppKit                        	    0x7ff804630a9a -[NSWindow _reallyDoOrderWindow:] + 99
12  AppKit                        	    0x7ff804630d10 -[NSWindow _doOrderWindow:] + 295
13  AppKit                        	    0x7ff803e086dc -[NSWindow makeKeyAndOrderFront:] + 47
14  QuickLookUI                   	    0x7ffb02ecf87b -[QLSeamlessDocumentOpener showWindow:contentFrame:withBlock:] + 169
15  AppKit                        	    0x7ff803f089c2 -[NSWindowController showWindow:] + 672
16  AppKit                        	    0x7ff803caddb6 NSApplicationMain + 997
17  About This Hack               	       0x103de40ac 0x103dde000 + 24748
18  dyld                          	    0x7ff80082041f start + 1903

Thread 1:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 4:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 5:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 6:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 7:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 8:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 9:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 10:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 11:
0   libsystem_pthread.dylib       	    0x7ff800b75bb0 start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x40006000004372d0  rbx: 0x0000000000000001  rcx: 0x0000000000000000  rdx: 0x0000000000000002
  rdi: 0x00007ff843159ce0  rsi: 0x00007ff843159cf8  rbp: 0x00007ff7bc120f60  rsp: 0x00007ff7bc120ed0
   r8: 0x0000000000000030   r9: 0x00000000000001ff  r10: 0x0000000000000030  r11: 0x000000008ca21ffb
  r12: 0x0000600001fafa80  r13: 0x0000600000437300  r14: 0x0000600001fafc00  r15: 0x0000000000000000
  rip: 0x0000000103df1701  rfl: 0x0000000000010297  cr2: 0x00000001125e9000

Logical CPU:     0
Error Code:      0x00000000
Trap Number:     6

Thread 0 instruction stream:
  00 00 4c 89 e9 e8 85 b3-ff ff 4c 89 f9 49 89 c5  ..L.......L..I..
  e9 01 fc ff ff 31 c9 48-85 c0 0f 95 c1 89 4d a0  .....1.H......M.
  49 89 fc e8 2b 62 00 00-8b 7d a0 48 8b 75 c0 ba  I...+b...}.H.u..
  01 00 00 00 4c 89 e9 e8-53 b3 ff ff 49 89 c5 e9  ....L...S...I...
  3f fc ff ff 48 8d 3d 2c-05 01 00 48 8d 35 dd 1d  ?...H.=,...H.5..
  00 00 e8 56 62 00 00 e9-42 fd ff ff 0f 0b 0f 0b  ...Vb...B.......
 [0f]0b 66 2e 0f 1f 84 00-00 00 00 00 0f 1f 00 55  ..f............U	<==
  48 89 e5 41 57 41 56 41-55 41 54 53 48 83 ec 28  H..AWAVAUATSH..(
  80 3d 90 14 01 00 00 0f-85 83 06 00 00 49 be 00  .=...........I..
  00 00 00 00 00 00 e1 48-bb 00 00 00 00 00 00 00  .......H........
  e0 49 bc 10 00 00 00 00-00 00 d0 e8 ff e6 ff ff  .I..............
  48 89 05 a0 0d 01 00 48-8d 3d 41 0d 01 00 e8 7c  H......H.=A....|

Binary Images:
       0x103dde000 -        0x103dfdfff app.netlify.0xCUBE.About-This-Hack (1.0.0) <c90a0bf5-0cd9-3b37-9e93-6fa3a1b7e7d3> /Applications/About This Hack.app/Contents/MacOS/About This Hack
       0x10dc1b000 -        0x10dc2afff libobjc-trampolines.dylib (*) <48a76ddd-8a45-3498-a5a3-86a9976e68e5> /usr/lib/libobjc-trampolines.dylib
    0x7ff803caa000 -     0x7ff804cb1ff8 com.apple.AppKit (6.9) <935dfca1-61f9-377d-895a-99ef90266c86> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7ffb02e28000 -     0x7ffb02f5bff8 com.apple.QuickLookUIFramework (5.0) <a1b3245d-8a1e-34c7-abdd-9877919b824d> /System/Library/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI
    0x7ff80081a000 -     0x7ff8008b25cf dyld (*) <5db85b72-c63a-3182-91e5-5c942ec30e48> /usr/lib/dyld
    0x7ff800b74000 -     0x7ff800b7ffff libsystem_pthread.dylib (*) <8cb0b396-011f-31f2-8915-94cde1abae84> /usr/lib/system/libsystem_pthread.dylib

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=760.8M resident=0K(0%) swapped_out_or_unallocated=760.8M(100%)
Writable regions: Total=638.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=638.3M(100%)

                                VIRTUAL   REGION
REGION TYPE                        SIZE    COUNT (non-coalesced)
===========                     =======  =======
Accelerate framework               128K        1
Activity Tracing                   256K        1
CG image                            88K        1
ColorSync                          236K       26
CoreServices                       176K        1
CoreUI image data                  992K        6
Foundation                          16K        1
Kernel Alloc Once                    8K        1
MALLOC                           239.8M       57
MALLOC guard page                   32K        8
MALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)
STACK GUARD                       56.0M       12
Stack                             13.6M       12
VM_ALLOCATE                         16K        4
__CTF                               824        1
__DATA                            29.9M      532
__DATA_CONST                      36.4M      345
__DATA_DIRTY                      1703K      204
__FONT_DATA                        2352        1
__INFO_FILTER                         8        1
__LINKEDIT                       170.9M        4
__OBJC_RO                         66.3M        1
__OBJC_RW                         2013K        2
__TEXT                           589.9M      560
dyld private memory                260K        2
mapped file                      200.1M       23
shared memory                      776K       16
===========                     =======  =======
TOTAL                              1.8G     1824
TOTAL, minus reserved VM space     1.4G     1824

-----------
Full Report
-----------

{"app_name":"About This Hack","timestamp":"2023-10-10 11:20:45.00 +0200","app_version":"1.0.0","slice_uuid":"c90a0bf5-0cd9-3b37-9e93-6fa3a1b7e7d3","build_version":"1337","platform":1,"bundleID":"app.netlify.0xCUBE.About-This-Hack","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 13.4.1 (22F770820d)","roots_installed":0,"name":"About This Hack","incident_id":"42E62AAB-118E-4169-AEAA-FF83C0B58C73"}
{
  "uptime" : 2600,
  "procRole" : "Foreground",
  "version" : 2,
  "userID" : 501,
  "deployVersion" : 210,
  "modelCode" : "MacBookPro16,1",
  "coalitionID" : 1036,
  "osVersion" : {
    "train" : "macOS 13.4.1",
    "build" : "22F770820d",
    "releaseType" : "User"
  },
  "captureTime" : "2023-10-10 11:20:44.8569 +0200",
  "incident" : "42E62AAB-118E-4169-AEAA-FF83C0B58C73",
  "pid" : 3016,
  "cpuType" : "X86-64",
  "roots_installed" : 0,
  "bug_type" : "309",
  "procLaunch" : "2023-10-10 11:20:42.5097 +0200",
  "procStartAbsTime" :<PHONE_NUMBER>390,
  "procExitAbsTime" :<PHONE_NUMBER>155,
  "procName" : "About This Hack",
  "procPath" : "\/Applications\/About This Hack.app\/Contents\/MacOS\/About This Hack",
  "bundleInfo" : {"CFBundleShortVersionString":"1.0.0","CFBundleVersion":"1337","CFBundleIdentifier":"app.netlify.0xCUBE.About-This-Hack"},
  "storeInfo" : {"deviceIdentifierForVendor":"A3D9D479-D001-5A1F-95AF-6F6C4F4F9102","thirdParty":true},
  "parentProc" : "launchd",
  "parentPid" : 1,
  "coalitionName" : "app.netlify.0xCUBE.About-This-Hack",
  "crashReporterKey" : "FBC0458E-F4CE-875A-3226-0B575496E39D",
  "codeSigningID" : "app.netlify.0xCUBE.About-This-Hack",
  "codeSigningTeamID" : "T474C55Q79",
  "codeSigningFlags" :<PHONE_NUMBER>,
  "codeSigningValidationCategory" : 3,
  "codeSigningTrustLevel" : 0,
  "bridgeVersion" : {"build":"20P5060","train":"7.5"},
  "sip" : "enabled",
  "exception" : {"codes":"0x0000000000000001, 0x0000000000000000","rawCodes":[1,0],"type":"EXC_BAD_INSTRUCTION","signal":"SIGILL"},
  "termination" : {"flags":0,"code":4,"namespace":"SIGNAL","indicator":"Illegal instruction: 4","byProc":"exc handler","byPid":3016},
  "extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0},
  "faultingThread" : 0,
  "threads" : [{"triggered":true,"id":46261,"instructionState":{"instructionStream":{"bytes":[0,0,76,137,233,232,133,179,255,255,76,137,249,73,137,197,233,1,252,255,255,49,201,72,133,192,15,149,193,137,77,160,73,137,252,232,43,98,0,0,139,125,160,72,139,117,192,186,1,0,0,0,76,137,233,232,83,179,255,255,73,137,197,233,63,252,255,255,72,141,61,44,5,1,0,72,141,53,221,29,0,0,232,86,98,0,0,233,66,253,255,255,15,11,15,11,15,11,102,46,15,31,132,0,0,0,0,0,15,31,0,85,72,137,229,65,87,65,86,65,85,65,84,83,72,131,236,40,128,61,144,20,1,0,0,15,133,131,6,0,0,73,190,0,0,0,0,0,0,0,225,72,187,0,0,0,0,0,0,0,224,73,188,16,0,0,0,0,0,0,208,232,255,230,255,255,72,137,5,160,13,1,0,72,141,61,65,13,1,0,232,124],"offset":96}},"threadState":{"r13":{"value":105553120686848},"rax":{"value":4611791571548074704},"rflags":{"value":66199},"cpu":{"value":0},"r14":{"value":105553149492224},"rsi":{"value":140704254106872,"symbolLocation":0,"symbol":"_swiftEmptyDictionarySingleton"},"r8":{"value":48},"cr2":{"value":4603154432},"rdx":{"value":2},"r10":{"value":48},"r9":{"value":511},"r15":{"value":0},"rbx":{"value":1},"trap":{"value":6},"err":{"value":0},"r11":{"value":2359435259},"rip":{"value":4359919361,"matchesCrashFrame":1},"rbp":{"value":140701988949856},"rsp":{"value":140701988949712},"r12":{"value":105553149491840},"rcx":{"value":0},"flavor":"x86_THREAD_STATE","rdi":{"value":140704254106848,"symbolLocation":8,"symbol":"_swiftEmptyArrayStorage"}},"queue":"com.apple.main-thread","frames":[{"imageOffset":79617,"imageIndex":0},{"imageOffset":81303,"imageIndex":0},{"imageOffset":19686,"imageIndex":0},{"imageOffset":19437,"imageIndex":0},{"imageOffset":19480,"imageIndex":0},{"imageOffset":1512253,"symbol":"-[NSViewController _sendViewDidAppear]","symbolLocation":50,"imageIndex":2},{"imageOffset":9884901,"symbol":"-[NSView _windowDidOrderOnScreen]","symbolLocation":67,"imageIndex":2},{"imageOffset":9885051,"symbol":"-[NSView _windowDidOrderOnScreen]","symbolLocation":217,"imageIndex":2},{"imageOffset":9885051,"symbol":"-[NSView _windowDidOrderOnScreen]","symbolLocation":217,"imageIndex":2},{"imageOffset":9885051,"symbol":"-[NSView _windowDidOrderOnScreen]","symbolLocation":217,"imageIndex":2},{"imageOffset":9986150,"symbol":"-[NSWindow _reallyDoOrderWindowAboveOrBelow:]","symbolLocation":2077,"imageIndex":2},{"imageOffset":9988762,"symbol":"-[NSWindow _reallyDoOrderWindow:]","symbolLocation":99,"imageIndex":2},{"imageOffset":9989392,"symbol":"-[NSWindow _doOrderWindow:]","symbolLocation":295,"imageIndex":2},{"imageOffset":1435356,"symbol":"-[NSWindow makeKeyAndOrderFront:]","symbolLocation":47,"imageIndex":2},{"imageOffset":686203,"symbol":"-[QLSeamlessDocumentOpener showWindow:contentFrame:withBlock:]","symbolLocation":169,"imageIndex":3},{"imageOffset":2484674,"symbol":"-[NSWindowController showWindow:]","symbolLocation":672,"imageIndex":2},{"imageOffset":15798,"symbol":"NSApplicationMain","symbolLocation":997,"imageIndex":2},{"imageOffset":24748,"imageIndex":0},{"imageOffset":25631,"symbol":"start","symbolLocation":1903,"imageIndex":4}]},{"id":46284,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46285,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46298,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46445,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46446,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46447,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46448,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46449,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46450,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46451,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":46452,"frames":[{"imageOffset":7088,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]}],
  "usedImages" : [
  {
    "source" : "P",
    "arch" : "x86_64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "1.0.0",
    "CFBundleIdentifier" : "app.netlify.0xCUBE.About-This-Hack",
    "size" : 131072,
    "uuid" : "c90a0bf5-0cd9-3b37-9e93-6fa3a1b7e7d3",
    "path" : "\/Applications\/About This Hack.app\/Contents\/MacOS\/About This Hack",
    "name" : "About This Hack",
    "CFBundleVersion" : "1337"
  },
  {
    "source" : "P",
    "arch" : "x86_64h",
    "base" :<PHONE_NUMBER>,
    "size" : 65536,
    "uuid" : "48a76ddd-8a45-3498-a5a3-86a9976e68e5",
    "path" : "\/usr\/lib\/libobjc-trampolines.dylib",
    "name" : "libobjc-trampolines.dylib"
  },
  {
    "source" : "P",
    "arch" : "x86_64",
    "base" :<PHONE_NUMBER>27840,
    "CFBundleShortVersionString" : "6.9",
    "CFBundleIdentifier" : "com.apple.AppKit",
    "size" : 16809977,
    "uuid" : "935dfca1-61f9-377d-895a-99ef90266c86",
    "path" : "\/System\/Library\/Frameworks\/AppKit.framework\/Versions\/C\/AppKit",
    "name" : "AppKit",
    "CFBundleVersion" : "2299.60.124"
  },
  {
    "source" : "P",
    "arch" : "x86_64",
    "base" :<PHONE_NUMBER>17184,
    "CFBundleShortVersionString" : "5.0",
    "CFBundleIdentifier" : "com.apple.QuickLookUIFramework",
    "size" : 1261561,
    "uuid" : "a1b3245d-8a1e-34c7-abdd-9877919b824d",
    "path" : "\/System\/Library\/Frameworks\/QuickLookUI.framework\/Versions\/A\/QuickLookUI",
    "name" : "QuickLookUI",
    "CFBundleVersion" : "965.6"
  },
  {
    "source" : "P",
    "arch" : "x86_64",
    "base" :<PHONE_NUMBER>12064,
    "size" : 624080,
    "uuid" : "5db85b72-c63a-3182-91e5-5c942ec30e48",
    "path" : "\/usr\/lib\/dyld",
    "name" : "dyld"
  },
  {
    "source" : "P",
    "arch" : "x86_64",
    "base" :<PHONE_NUMBER>26432,
    "size" : 49152,
    "uuid" : "8cb0b396-011f-31f2-8915-94cde1abae84",
    "path" : "\/usr\/lib\/system\/libsystem_pthread.dylib",
    "name" : "libsystem_pthread.dylib"
  }
],
  "sharedCache" : {
  "base" :<PHONE_NUMBER>89472,
  "size" :<PHONE_NUMBER>0,
  "uuid" : "9f83a7ef-adbb-380d-9d27-bace557e7d62"
},
  "vmSummary" : "ReadOnly portion of Libraries: Total=760.8M resident=0K(0%) swapped_out_or_unallocated=760.8M(100%)\nWritable regions: Total=638.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=638.3M(100%)\n\n                                VIRTUAL   REGION \nREGION TYPE                        SIZE    COUNT (non-coalesced) \n===========                     =======  ======= \nAccelerate framework               128K        1 \nActivity Tracing                   256K        1 \nCG image                            88K        1 \nColorSync                          236K       26 \nCoreServices                       176K        1 \nCoreUI image data                  992K        6 \nFoundation                          16K        1 \nKernel Alloc Once                    8K        1 \nMALLOC                           239.8M       57 \nMALLOC guard page                   32K        8 \nMALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)\nSTACK GUARD                       56.0M       12 \nStack                             13.6M       12 \nVM_ALLOCATE                         16K        4 \n__CTF                               824        1 \n__DATA                            29.9M      532 \n__DATA_CONST                      36.4M      345 \n__DATA_DIRTY                      1703K      204 \n__FONT_DATA                        2352        1 \n__INFO_FILTER                         8        1 \n__LINKEDIT                       170.9M        4 \n__OBJC_RO                         66.3M        1 \n__OBJC_RW                         2013K        2 \n__TEXT                           589.9M      560 \ndyld private memory                260K        2 \nmapped file                      200.1M       23 \nshared memory                      776K       16 \n===========                     =======  ======= \nTOTAL                              1.8G     1824 \nTOTAL, minus reserved VM space     1.4G     1824 \n",
  "legacyInfo" : {
  "threadTriggered" : {
    "queue" : "com.apple.main-thread"
  }
},
  "logWritingSignature" : "eef1642247a4b7bb55f36457a10dbf9a101e2b94",
  "trialInfo" : {
  "rollouts" : [
    {
      "rolloutId" : "60356660bbe37970735c5624",
      "factorPackIds" : {

      },
      "deploymentId" : 250000016
    },
    {
      "rolloutId" : "5f72dc58705eff005a46b3a9",
      "factorPackIds" : {

      },
      "deploymentId" : 240000015
    }
  ],
  "experiments" : [
    {
      "treatmentId" : "6dd670af-0633-45e4-ae5f-122ae4df02be",
      "experimentId" : "64406ba83deb637ac8a04419",
      "deploymentId" : 900000017
    },
    {
      "treatmentId" : "a092db1b-c401-44fa-9c54-518b7d69ca61",
      "experimentId" : "64a844035c85000c0f42398a",
      "deploymentId" : 400000019
    }
  ]
}
}

Model: MacBookPro16,1, BootROM 19<IP_ADDRESS>.0 (iBridge: 20.16.5060.0.0,0), 6 processors, 6-Core Intel Core i7, 2,6 GHz, 16 GB, SMC
Graphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In
Graphics: AMD Radeon Pro 5300M, AMD Radeon Pro 5300M, PCIe, 4 GB
Display: Color LCD, 3072 x 1920 Retina, MirrorOff, Online
Display: LG HDR 4K, 5120 x 2880 (5K/UHD+ - Ultra High Definition Plus), Main, MirrorOff, Online
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR4, 2667 MHz, SK Hynix, HMA81GS6CJR8N-VK
Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, DDR4, 2667 MHz, SK Hynix, HMA81GS6CJR8N-VK
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x7BF), wl0: Dec  9 2022 17:02:25 version 9.30.4<IP_ADDRESS>.87 FWID 01-e7856862
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: Extreme SSD
USB Device: USB3.1 Hub
USB Device: USB3.1 Hub
USB Device: Dell Universal Dock D6000
USB Device: USB31Bus
USB Device: USB 2.0 BILLBOARD
USB Device: USB2.1 Hub
USB Device: USB 2.0 Hub [MTT]
USB Device: EFM8 HID ISP
USB Device: USB2.0 Hub
USB Device: USB Receiver
USB Device: T2Bus
USB Device: composite_device
USB Device: Touch Bar Backlight
USB Device: Touch Bar Display
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 63.5
Thunderbolt Bus: MacBook Pro, Apple Inc., 63.5

Can you try to run from command line?
$ ~/Downloads/About-This-Hack.app/Contents/MacOS/*
Or whatever the path to your app instance is. Thanks!

@MDNich

Ok this issue is the same as the display one #60 , closing this one to move to there


allow external input connection to multiple ports with same name

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (6edbc76) 90.09% compared to head (280b8da) 90.14%.

Files
Patch %
Lines

src/named_systems2.jl
90.32%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #99      +/-   ##
==========================================
+ Coverage   90.09%   90.14%   +0.04%
==========================================
  Files          19       19
  Lines        2696     2719      +23
==========================================
+ Hits         2429     2451      +22
- Misses        267      268       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


add supports for wordpress example demo with KubeVela Application and related Alicloud RDS resources

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

Ref: #87

2. What is the scope of this PR (e.g. component or file name):
modified:
base/pkg/kusion_models/kube/frontend/server.k
base/pkg/kusion_models/kube/render/render.k
base/pkg/kusion_models/kube/backend/server_backend.k
added:
base/pkg/kusion_clouds/alicloud/alicloud_db_connection.k
base/pkg/kusion_clouds/alicloud/alicloud_db_instance.k
base/pkg/kusion_clouds/alicloud/alicloud_rds_account.k
base/pkg/kusion_clouds/alicloud_backend/alicloud_rds_backend.k
base/pkg/kusion_models/kube/frontend/storage/database.k
appops/wordpress-kubevela

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[x] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

A new item "renderType" is added in server frontend to support rendering KubeVela Application, and a related wordpress example is given, along with relevant alicloud rds resource schemas for hybrid resource support.

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[x] Manual test (add detailed scripts or steps below)
[ ] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

PR  has conflicts, please resolve


[settings] able to pull up old and new settings dialog at same time

On machine start, i kept clicking on the PT icon.
0.18 build

Can't reproduce it, could be fixed now.  Haven't seen it since this


Notebook Climatological_ESP_forecasting fails with timeout errors

Notebook Climatological_ESP_forecasting fails with timeout errors, even with relatively small forecast durations. This is run on JupyterLabs notebooks, in the tutorial_notebooks folder.
The timeout occurs in the call to the WPS for climatological ESP forecasting, in the second cell.

Seems this is not the case anymore, simple retest and it worked.

Nope, still time-outing after all, this seems shaky.

This one is very weird.  If I use the Raven on my dev server lvupavics.ouranos.ca instead of prod pavics.ouranos.ca, I don't have the timeout error.  But both prod and my dev server are using the exact same config and same docker image versions (using same commit of the birdhouse-deploy repo).

Another notebook with similarly weird timeout error https://github.com/Ouranosinc/raven/issues/362#issuecomment-772189628


Delete old runs, protocols, and analyses

Overview
Currently, robot-server never deletes the things that it persists across reboots. They will accumulate indefinitely and eventually make the database very big. To prevent performance and storage capacity problems, robot-server should automatically trim these records.
Acceptance criteria

A heavily-used robot must not create persistent records infinitely. At some reasonable limit, creating new records should be disallowed, or old records should be automatically deleted, or both.
Consistency of the database and the API must be preserved. For example, we shouldn't leave runs that refer to protocols that no longer exist.
Auto-deletion behavior must be documented in the OpenAPI spec.
Auto-deletes should be logged, for debuggability.

Implementation proposal
Analyses
The server will store a small, bounded number of analyses (maybe 5) for each protocol. When something creates an additional analysis, the server will automatically push out the oldest one on that protocol to make room, if needed.
Runs
The server will store a bounded number of runs. (Approximately 20—see #9367.)
When the client POSTs a new run, if the server has reached its run limit, the server will make room by automatically deleting the oldest run.
This is automatic instead of explicit to relieve client-side burden. In particular, v5.0 clients expect to be able to POST runs over and over without limit.
Protocols
The server will store a bounded number of protocols. (20 is reasonable, to match the limit on runs.)
When the client POSTs a new protocol, if the server has reached its protocol limit, the server will make room by automatically deleting the oldest protocol that is not linked to a run.
If every existing protocol is linked to a run, the server can't safely delete any of them without violating the database's consistency. In this case, the server will repeatedly delete the oldest run that is linked to a protocol until any protocol is orphaned, and then delete that protocol.
As with runs, this is automatic instead of explicit in order to relieve client-side burden.
When we need to delete runs to free up some protocols to be deleted, we delete the oldest runs, not the runs with the oldest protocols, to avoid confusing scenarios where runs disappear from the middle of a robot's run history. With our current UIs, preserving a sensible run history is more important than preserving a sensible protocol history.
When the client explicitly DELETEs a protocol, the server will return some kind of conflict error (like a 409) if that protocol is linked to a run. We can reconsider this in the future, but for now, this seems like the simplest and most explicit thing.
Whenever a protocol is deleted, all of its analyses are also deleted automatically.

I think this is a good spec. If we encounter any roadblocks during implementation, I believe we have an simplification offramp available that might help:

If every existing protocol is linked to a run, the server can't safely delete any of them without violating the database's consistency. In this case, the server will repeatedly delete the oldest run that is linked to a protocol until any protocol is orphaned, and then delete that protocol.

We could potentially drop this requirement for simplicity and still maintain consistency, by treating the 20 protocol limit as soft and allowing the POST to succeed.
Then, one of two things will happen:

User will POST /runs using the new protocol

New run will cause the oldest run to be evicted, probably orphaning a protocol
Subsequent POST /protocols will evict that newly orphaned protocol

User will POST /protocols with another new protocol, without ever creating a run

Since the previously created protocol that exceeded the limit was never used in a run, it is deleted
New protocol is created

The simplification here might be worth it:

POST /runs never has to modify the protocols table
POST /protocols never has to modify the runs table

Interesting, yeah, that could work.
One possible downside is that, in a sense, it sort of degenerates to a maximum protocol limit of 1, I think.

We start with 20 protocols and 20 runs (mapped 1:1) uploaded.
Client A uploads protocol 21. This is over the soft limit, but doesn't evict anything because everything else is linked to a run.
Client B uploads protocol 22. This evicts protocol 21.
Client A tries to start a run with protocol 21, but it's already gone.

I think we could solve this in practice by making the protocol limit something like 40, keeping the run limit at 20? It's making my head hurt.


luci-app-mwan3: start adding german translation a new max_ttl option

Start of adding german translation
Add new max_ttl option see https://github.com/openwrt/packages/commit/c9d8fceb63a425f19fc12bee7ee4191fad514b6e#diff-87268a842bab5effbe181f9f18b2d348

Merged, thanks!


node & npm command can't find when rebooted

Hi , I got this issue:
Every time I reboot, node & npm command not found
Here is my "nvm debug"
➜ ~ nvm debug
nvm --version: v0.33.2
$SHELL: /bin/zsh
$HOME: /home/choyt
$NVM_DIR: '$HOME/.nvm/'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'zsh 5.1.1 (x86_64-ubuntu-linux-gnu)'
uname -a: 'Linux 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux'
OS version: Ubuntu 16.04.3 LTS
curl: /usr/bin/curl, curl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3
wget: /usr/bin/wget, GNU Wget 1.17.1 在 linux-gnu 上编译。
git: /usr/bin/git, git version 2.7.4
nvm current: none
which node: node not found
which iojs: iojs not found
which npm: npm not found
npm config get prefix: nvm:143: command not found: npm
npm root -g: nvm:143: command not found: npm
System: ubuntu 16.04
bash: oh-my-zsh & terminal

Try nvm alias default node, and ensure you have a node version installed?

Hi ,
I'v tried some times, but never help. And when I run "nvm use
--lts=boron" I got the prompt:
~ nvm use --lts=boron
nvm is not compatible with the npm config "prefix" option: currently set to
"/home/choyt/.nvm/versions/node/v6.11.2"
Run nvm use --delete-prefix to unset it.
And npm can't found still.
2017-09-02 14:32 GMT+08:00 Jordan Harband<EMAIL_ADDRESS>
Try nvm alias default node, and ensure you have a node version installed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/creationix/nvm/issues/1603#issuecomment-326725929,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANPF0F__VquQZT55drNsghlYoJ3YeeXPks5sePaGgaJpZM4PK0RZ
.

@zhouytforever i see you're using oh-my-zsh. What setopt options do you have set?
Is your home dir a symlink? does whoami print out choyt - all lowercase?

whoami print out choyt
Here are the .zshrc
2017-09-02 14:58 GMT+08:00 Jordan Harband<EMAIL_ADDRESS>
@zhouytforever https://github.com/zhouytforever i see you're using
oh-my-zsh. What setopt options do you have set?
Is your home dir a symlink? does whoami print out choyt - all lowercase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creationix/nvm/issues/1603#issuecomment-326726932,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANPF0MLZIGTD_XbRayZHNpbdAzI5cr0bks5sePx5gaJpZM4PK0RZ
.

If you come from bash you might have to change your $PATH.
export PATH=$HOME/bin:/usr/local/bin:$PATH
export NVM_NODEJS_ORG_MIRROR=https://npm.taobao.org/mirrors/node
Path to your oh-my-zsh installation.
export ZSH=/home/choyt/.oh-my-zsh
Set name of the theme to load. Optionally, if you set this to "random"
it'll load a random theme each time that oh-my-zsh is loaded.
See https://github.com/robbyrussell/oh-my-zsh/wiki/Themes
ZSH_THEME="robbyrussell"
Uncomment the following line to use case-sensitive completion.
CASE_SENSITIVE="true"
Uncomment the following line to use hyphen-insensitive completion. Case
sensitive completion must be off. _ and - will be interchangeable.
HYPHEN_INSENSITIVE="true"
Uncomment the following line to disable bi-weekly auto-update checks.
DISABLE_AUTO_UPDATE="true"
Uncomment the following line to change how often to auto-update (in days).
export UPDATE_ZSH_DAYS=13
Uncomment the following line to disable colors in ls.
DISABLE_LS_COLORS="true"
Uncomment the following line to disable auto-setting terminal title.
DISABLE_AUTO_TITLE="true"
Uncomment the following line to enable command auto-correction.
ENABLE_CORRECTION="true"
Uncomment the following line to display red dots whilst waiting for completion.
COMPLETION_WAITING_DOTS="true"
Uncomment the following line if you want to disable marking untracked files
under VCS as dirty. This makes repository status check for large repositories
much, much faster.
DISABLE_UNTRACKED_FILES_DIRTY="true"
Uncomment the following line if you want to change the command execution time
stamp shown in the history command output.
The optional three formats: "mm/dd/yyyy"|"dd.mm.yyyy"|"yyyy-mm-dd"
HIST_STAMPS="mm/dd/yyyy"
Would you like to use another custom folder than $ZSH/custom?
ZSH_CUSTOM=/path/to/new-custom-folder
Which plugins would you like to load? (plugins can be found in ~/.oh-my-zsh/plugins/*)
Custom plugins may be added to ~/.oh-my-zsh/custom/plugins/
Example format: plugins=(rails git textmate ruby lighthouse)
Add wisely, as too many plugins slow down shell startup.
plugins=(git)
source $ZSH/oh-my-zsh.sh
User configuration
export MANPATH="/usr/local/man:$MANPATH"
You may need to manually set your language environment
export LANG=en_US.UTF-8
Preferred editor for local and remote sessions
if [[ -n $SSH_CONNECTION ]]; then
export EDITOR='vim'
else
export EDITOR='mvim'
fi
Compilation flags
export ARCHFLAGS="-arch x86_64"
ssh
export SSH_KEY_PATH="~/.ssh/rsa_id"
Set personal aliases, overriding those provided by oh-my-zsh libs,
plugins, and themes. Aliases can be placed here, though oh-my-zsh
users are encouraged to define aliases within the ZSH_CUSTOM folder.
For a full list of active aliases, run alias.

Example aliases
alias zshconfig="mate ~/.zshrc"
alias ohmyzsh="mate ~/.oh-my-zsh"
export NVM_DIR="$HOME/.nvm/"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
source ~/.nvm/nvm.sh

And here my choyt dir
2017-09-02 15:15 GMT+08:00 yt zhou<EMAIL_ADDRESS>
whoami print out choyt
Here are the .zshrc
2017-09-02 14:58 GMT+08:00 Jordan Harband<EMAIL_ADDRESS>
@zhouytforever https://github.com/zhouytforever i see you're using
oh-my-zsh. What setopt options do you have set?
Is your home dir a symlink? does whoami print out choyt - all lowercase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creationix/nvm/issues/1603#issuecomment-326726932,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANPF0MLZIGTD_XbRayZHNpbdAzI5cr0bks5sePx5gaJpZM4PK0RZ
.

总用量 312K
-rw-rw-r--   1 choyt choyt   29 6月  14 23:38 .appcfg_nag
-rw-------   1 choyt choyt  607 6月  14 23:52 .bash_history
-rw-r--r--   1 choyt choyt  220 6月  14 23:09 .bash_logout
-rw-r--r--   1 choyt choyt 3.7K 6月  14 23:09 .bashrc
drwx------  26 choyt choyt 4.0K 8月  31 00:10 .cache
-rw-rw-r--   1 choyt choyt    0 9月   2 15:16 choyt.txt
drwx------  28 choyt choyt 4.0K 8月  31 03:15 .config
drwx------   3 choyt choyt 4.0K 6月  14 23:11 .dbus
drwxrwxr-x   4 choyt choyt 4.0K 6月  15 00:11 Desktop
-rw-r--r--   1 choyt choyt   25 6月  14 23:11 .dmrc
drwxrwxr-x   2 choyt choyt 4.0K 6月  15 00:08 Document
drwxrwxr-x   3 choyt choyt 4.0K 9月   2 15:14 Download
drwx------   2 choyt choyt 4.0K 9月   2 14:23 .gconf
-rw-rw-r--   1 choyt choyt  174 9月   2 15:03 .gitconfig
drwx------   3 choyt choyt 4.0K 6月  14 23:35 .gnome2
drwx------   2 choyt choyt 4.0K 6月  14 23:35 .gnome2_private
drwx------   3 choyt choyt 4.0K 9月   2 14:21 .gnupg
-rw-------   1 choyt choyt  11K 9月   2 14:21 .ICEauthority
drwxrwxr-x   3 choyt choyt 4.0K 6月  30 22:08 .kingsoft
-rw-------   1 choyt choyt   79 9月   2 14:44 .lesshst
drwx------   3 choyt choyt 4.0K 6月  14 23:11 .local
drwx------   4 choyt choyt 4.0K 6月  14 23:17 .mozilla
drwx------   2 choyt choyt 4.0K 6月  15 00:03 Music
drwxrwxr-x 384 choyt choyt  12K 9月   1 01:44 .npm
drwx------   3 choyt choyt 4.0K 6月  15 01:01 .nv
drwxrwxr-x   9 choyt choyt 4.0K 9月   1 04:22 .nvm
drwxr-xr-x  11 choyt choyt 4.0K 9月   1 01:34 .oh-my-zsh
drwxrwxr-x   2 choyt choyt 4.0K 6月  15 00:08 Picture
drwx------   3 choyt choyt 4.0K 6月  14 23:42 .pki
drwx------   2 choyt choyt 4.0K 6月  14 23:11 .presage
-rw-r--r--   1 choyt choyt  675 6月  14 23:09 .profile
drwxrwxr-x   4 choyt choyt 4.0K 8月  31 04:45 project
drwxrwxr-x   2 choyt choyt 4.0K 6月  15 00:08 Public
drwx------   2 choyt choyt 4.0K 8月  31 04:43 .ssh
-rw-r--r--   1 choyt choyt    0 6月  14 23:13 .sudo_as_admin_successful
drwx------   2 choyt choyt 4.0K 6月  14 23:52 .sunpinyin
drwxrwxr-x   2 choyt choyt 4.0K 6月  15 00:08 Template
drwx------   4 choyt choyt 4.0K 8月  20 19:39 .thunderbird
drwxrwxr-x   2 choyt choyt 4.0K 6月  15 00:08 Video
drwxrwxr-x   3 choyt choyt 4.0K 9月   2 14:39 .vim
-rw-------   1 choyt choyt  11K 9月   2 15:14 .viminfo
-rw-rw-r--   1 choyt choyt 2.5K 9月   2 14:17 .vimrc
-rw-rw-r--   1 choyt choyt  217 9月   1 01:37 .wget-hsts
-rw-------   1 choyt choyt   64 9月   2 14:21 .Xauthority
-rw-rw-r--   1 choyt choyt  132 6月  14 23:28 .xinputrc
-rw-------   1 choyt choyt   84 9月   2 14:21 .xsession-errors
-rw-------   1 choyt choyt 1.3K 9月   2 14:20 .xsession-errors.old
drwxrwxr-x   6 choyt choyt 4.0K 9月   2 15:04 XX-Net
-rw-rw-r--   1 choyt choyt 4.5K 9月   1 04:18 yankring_history_v2.txt
-rw-rw-r--   1 choyt choyt  39K 6月  14 23:53 .zcompdump
-rw-rw-r--   1 choyt choyt  39K 6月  14 23:53 .zcompdump-choyt-ThinkPad-T450-5.1.1
-rw-------   1 choyt choyt 4.1K 9月   2 15:16 .zsh_history
-rw-r--r--   1 choyt choyt 3.1K 9月   1 04:18 .zshrc
-rw-r--r--   1 choyt choyt   17 9月   1 01:38 .zsh-update

I'm not really sure - it would have helped if you'd filled out the entire issue template when creating the issue in the first place.
What's the full output when you try nvm use node? (please do not email it in; please post it with the github web interface, and surround it in triple-backticks so there's nice syntax highlighting)


internal/dag: reject * from IngressRoute FQDN

Disallow wildcarded FQDNs for IngressRoutes

Will check and reject any FQDN containing * at DAG build time
Wont check Ingress

Implementation details

CDR untouched, there is a regex already in place that does this check among others
Tests for IngressRoutes using * have been replaced with bar.com. foo.com is been used at other tests, but wanted to make it easy for reviewers to diff
Added a test case at TestDAGIngressRouteStatus

Fixes #1167
Signed-off-by: Pablo Mercado<EMAIL_ADDRESS>

Rejecting * for ingresses might need some clarification:

Ingress objects without FQDN have historically targeted every upstream service defined in the spec. That configuration at envoy means setting a * domain.
rejecting * will means that current behaviour where non informed Spec.Rules[].Host at Ingress object is translated here, will be noop
If we noop on Ingress objects that have no Host we will need to update its status with a message, probably adding an IngressStatus here

If that sounds right, I'm happy to start with that. If this requires some more design I'm ok dropping this PR

Let's break this out. please open a new issue for rejecting * from Ingress,
lets leave this PR as IngressRoute only.
On Mon, 8 Jul 2019 at 17:30, Pablo Mercado<EMAIL_ADDRESS>wrote:

Rejecting * for ingresses might need some clarification:

Ingress objects without FQDN have historically targeted every
upstream service defined in the spec. That configuration at envoy means
setting a * domain.
rejecting * will means that current behaviour where non informed
Spec.Rules[].Host at Ingress object is translated here
https://github.com/heptio/contour/blob/6a855c2e1144da613baaf06a487211ff49021216/internal/dag/builder.go#L437,
will be noop
If we noop on Ingress objects that have no Host we will need to
update its status with a message, probably adding an IngressStatus here
https://github.com/heptio/contour/blob/6a855c2e1144da613baaf06a487211ff49021216/internal/k8s/status.go#L27

If that sounds right, I'm happy to start with that. If this requires some
more design I'm ok dropping this PR
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/heptio/contour/pull/1227?email_source=notifications&email_token=AAABYAYCDGM4KIGEVMCD7CTP6LUJXA5CNFSM4H6VOGVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZMHDNI#issuecomment-509112757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABYA2RLLIA2KUQETDXNEDP6LUJXANCNFSM4H6VOGVA
.


Any suggestions for what is wrong? A total newbie here

The packages were installed using package-install command

Also Firefox couldn't connect to the server <IP_ADDRESS>:8080.

Also Firefox couldn't connect to the server <IP_ADDRESS>:8080.


No data sending

Hi so I'm having this issue where everything is setup perfectly. The server is starting on the pc and the app is on the watch along side the data has been put into the app on the phone (IP and port) but no data is being sent across to the pc at all the heart rate just sits at 0

Hmmm. Seems similar to https://github.com/bfroggio/heart-of-frogg/issues/13. Could you share your watch model and its firmware version number? Curious if it's different from mine. Also, what phone type (Android or iPhone) and Fitbit app version number are you using?

Closing due to inactivity from the initial poster.


support get_FOO_display and related objects

For example:
@python_2_unicode_compatible
class Car(models.Model):
    EMISSION_CHOICES = (
        ( 0, 'Unknown'),
        ( 1, 'Euro I'),
        ( 2, 'Euro II'),
        ( 3, 'Euro III'),
        ( 4, 'Euro IV'),
        ( 5, 'Euro V'),
    )

    ...
    emission = models.IntegerField(max_length=2, choices=EMISSION_CHOICES),
    ...

@python_2_unicode_compatible
class CarImage(models.Model):
    car = models.ForeignKey(Car, related_name='images')
    image = ProcessedImageField(upload_to=settings.UPLOAD_ROOT+'car/images/%Y/%m/%d',
                                processors=[ResizeToFit(1200, 1200)],
                                format='JPEG',
                                options={'quality': 60})

Then we could have something like below for better and easier representation:
preparer = FieldsPreparer(fields={
        ...
        'emission' : 'get_emission_display',
        'image' : 'images.first.image.url',
        ...
    })

Coverage decreased (-0.43%) to 95.6% when pulling b9a1289d6a7651e010d4a8ca144cde3e6e2df704 on Xiaoli:master into 4fff54b9f56d829d6ed76bb225c263c8442d0074 on toastdriven:master.

Thanks @Xiaoli! Sorry for taking so long to get a feedback. Could you please add some tests?

Your commit was added to PR #99. Thanks!


Added hindi translation for Passing props to a component

Let me know if any changes are required. Thank you.

@sanskar-mk2 Can you translate the full file and let me know once done.
I will start review once the translation of complete file is done.

@sanskar-mk2 I was checking the page which was assigned to you, in the PR you have translated the wrong page.
This is the page assigned to you https://github.com/reactjs/hi.reactjs.org/blob/main/beta/src/pages/learn/passing-props-to-a-component.md
Can you work on translating this and update the PR.


fix: types for block_id in query provider

I spent some time to figure out why my code was not working until I realized that the interface BlockReference  was not correct for RPC calls...
https://docs.near.org/docs/api/rpc#using-block_id-param

@vgrichina


Need apoptosis to kill serverless functions if total time has expired.

If the genesis time plus the total time for all phases exceeds the current time by more than , function should never start a new generation of worker Lambdas.
Design consideration: how would this interact with a "live" switch?

I've been considering the idea of a live switch at its simplest: Provide a URL to GET which should always return 200 OK. It could even be the target of the load test: automatically stopping the test if you ever actually affect the target.
With that thinking, a live switch could be an on/off feature, which stops the test given any error response.
But a more sophisticated use of that feature would be to provide a URL to query to continue the test, which could be backed by a simple service, tied to a control dashboard.
Or it could be a service which is coordinating the overall load test. (Maybe the controller lambda?) The coordinator could be keeping track of the number of worker lambdas being spawned. Or maybe just querying CW.
If the coordinator detects an anomaly, it flips the live switch.

Saying the above about the live switch feature, I think that would be separate from a self-contained feature which would have no external dependencies or signal but would cause the Lambda to self-terminate based on the amount of time which has passed.
But how does that differ from the AWS Lambda built-in timeout feature? If the Lambda is configured with a 5m runtime, AWS seems to be pretty efficient and stopping them on time.

Yup, this should be a distinct feature, may be some overlap in design thinking - just throwing that in for discussion.  The issue this is preventing is when multiple generations of lambdas continue to be created and used well past the end time of the test run.  We have historically seen a number of odd edge cases (and fixed all that we're aware of) - this would be a watchdog feature that would basically refuse to create more Lambdas if the time of the test had passed.  For example, last week an acceptance test continued running in a loop for 4 hours before we manually killed it.  This would have stopped that.

To be clear, the goal is to create a self-destruct mechanism that doesn't prevent live switch, not to design live switch.

Hehe. Right. We can put a pin in all that stuff above.
Can imagine the required feature would be:

Upon invocation, SA analyzes the script and calculates the Apoptosis Time (AT) to be the total run time of the script plus some reasonable buffer.
On calculated, the AT is passed to the load providing code (maybe this Lambda or others workers). The signal to calculate AT could be the fact that it was not included in the invocation.
As soon as any SA Lambda is invoked, it checks the current time to see if exceeds the AT. If not, testing continues. Otherwise, it exits with success code.

What am I missing?

Maybe #3 is a periodic check, not just on startup.

A periodic check seems like it could introduce risks and greater complication.  My understanding of this feature is a rough grained safety check for gratuitous failures.
I think this can ignore the function mode (i.e. controller vs worker) but simply check at invocation whether the complete-by time has passed and refuse to continue if it has.  It would be like:
!(AT in script) ? add it
Date.now() > AT ? exit : proceed

LGTM


issues with the unicode_literals future import

On Mac OS X El Capitan, I get the following message:
/Library/Python/2.7/site-packages/subliminal/cli.py:115: Warning: Click detected the use of the unicode_literals future import.  This is heavily discouraged because it can introduce subtle bugs in your code.  You should instead use explicit u"" literals for your unicode strings.  For more information see http://click.pocoo.org/python3/
While it's just a warning, it causes the Automator workflow to abort.

See #495


return preset normal for stats true

What kind of change does this PR introduce?
closes #11072

Did you add tests for your changes?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

Thanks


Shadowrun Sixth World v.64 - 1 Bugfix

[X] The pull request title clearly contains the name of the sheet I am editing.

[X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).

[X] The pull request makes changes to files in only one sub-folder.

[X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

[X] I have followed the Character Sheets Standards when building this sheet.

Changes / Description
Bugfix - PC Judge Intentions wasn't updating on Willpower changes.

Character Sheet Info Roll20 Internal Use only.


Make Q better

Apologies for my design skill, haha: https://github.com/ludi317/github-graphiti/issues/2

Nvm, looks like you fixed it


ARROW-7400: [Java] Avoid the worst case for quick sort

This issue is in response of a discussion in: https://github.com/apache/arrow/pull/5540#discussion_r329487232.
The quick sort algorithm can degenerate to an O(n^2) algorithm, if the pivot is selected poorly. This is an important problem, as the worst case can happen, if the input vector is alrady sorted, which is frequently encountered in practice.
After some investigation, we solve the problem with a simple but effective approach: take 3 samples and choose the median (with at most 3 comparisons) as the pivot. This sorts the vector which is already sorted in O(nlogn) time.

@liyafan82 Thanks for the improvement.
I have a question: Looking at the improvement approach (esp. after adding the insertion sort under threshold, this much looks like the Introspective Sorting and Selection Algorithms . I am not 100% sure but I think the C++ std::sort also use very similar algorithm @pitrou?

@walterddr Thanks a lot for your comments.
I think our approach is similar to the reference, with two differences:

We do not limit the recursive depth, as we have revised the algorithm to a non-recursive one in a previous issue.
When the range is small enough, we switch to insertion sort, instead of heap sort. (The insertion sort cannot be used if the recursive depth is limited, as the worst case time complexity can be O(n^2). But this is not a problem, if the threshold to switch algorithm is a constant, as in our approach).

According to my investigation, the implementation of C++ std::sort is very close to the reference (limit recursive depth & switch to heap sort). I am using gcc 4.8.5.

@walterddr This implementation doesn't protect against O(n**2) worst case, it just tries to make it unlikely.

thanks for the explanation @pitrou and @liyafan82 . That's also what I thought as well. This might be a dumb question.. but any reason why we can't implemented the algorithm in the paper or similar to how C++ does it to prevent the worse case O(n^2)? (of course, with the non-recursive way as suggested in #5540)?

thanks for the explanation @pitrou and @liyafan82 . That's also what I thought as well. This might be a dumb question.. but any reason why we can't implemented the algorithm in the paper or similar to how C++ does it to prevent the worse case O(n^2)? (of course, with the non-recursive way as suggested in #5540)?

Good question.
IMO, a non-recursive algorithm is in general faster than a recursive one.
In addition, insertion sort is faster than heap sort for small data sets. For example, intensive sort benchmarks have been performed in http://alejandroerickson.com/j/2016/08/02/benchmarking-int-sorting-algorithms.html and results show that insertion sort is much faster than heap sort for small data sets (e.g. with no more than 100 elements).
I think C++ library does not switch to insertion sort, because it has to control the recursive depth (to avoid stack overflow), and so it cannot control the data set size to switch algorithm. In the extreme case, the algorithm may degenerate to a O(n^2) algorithm (even if the pivots are selected perfectly). The fundamental reason is that it is a recursive algorithm.
@pitrou Please correct me if I am wrong.

@walterddr It seems you are interested algorithms implemented in Java. We have a design doc (https://docs.google.com/document/d/17nqHWS7gs0vARfeDAcUEbhKMOYHnCtA46TOY_Nls69s/edit#heading=h.3432tw3uqfeg) discussing the algorithms.
Maybe you can find some points that can be useful in your scenario, and we would like to provide anything to help :-)

@liyafan82 appreciate the quick reply and the explanation, after some digging I think in order to avoid worst case O(n^2), a linear time median computation is needed in order to avoid choosing pivot at extreme. however, in your explanation - it seems to make more sense to avoid doing so in practices, as compute the real median has a high constant/linear penalty.
Also I would definitely take a deeper look at the algorithm design doc, thanks for sharing!

@walterddr As you have indicated, by choosing the pivot inappropriately, the algorithm may degenerate to O(n^2) time. IMO, most practical algorithms find pivots by heuristics or randomized algorithms. The reasoning is that finding the median exactly is expensive, and the theoretical worst case happens rarely (even if we ignore the problem of selecting pivot completely, we get O(nlogn) time on average, if the input data set is uniformly distributed. What we are doing is to further reduce the probability of the worst case).
Glad that you are interested in the doc, if there is anything we can do, please feel free to contact us. Thank you in advance.

+1 thank you.


Branch find task

Codecov Report

Merging #50 (1f2ead1) into branch-task (3ec15bf) will decrease coverage by 0.77%.
The diff coverage is 0.00%.

Continue to review full report at Codecov.

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


Implement array and dynamic array state variable types

We have a Map type for state variables, but we don't have Array or DynamicArray types yet, for storing indexed arrays of state.

Maybe a DynamicArray should be called a Vec in rust speak?

@LHerskind @nventuro this one came up at the offsite. Might be a nice simple task for someone.


html comments in markdown quietly break rich-text field

If you have a rich-text field with html comments like <!-- TODO --> in the body, using a rich-text field puts everything in block quotes.
The easy answer is "don't use html comments in markdown", however we don't catch this in our audit, and it's supported by ReactMarkdown.

I believe that there is a broader issue.
I am migrating from forestry to TinaCMS (hugo based site), and my theme makes use of <!-- more --> comment to split pages.
running npx tinacms audit brings in a lot of errors, all related to this
Error parsing file threat-detection-tools-for-containers.md from collection posts.
    Unexpected character `!` (U+0021) before name, expected a character that can start a name, such as a letter, `$`, or `_` (note: to create a comment in MDX, use `{/* text */}`)
Error parsing file use-terraform-http-data-source-to-wait-for-cluster-coming-up.md from collection posts.
    Unexpected character `!` (U+0021) before name, expected a character that can start a name, such as a letter, `$`, or `_` (note: to create a comment in MDX, use `{/* text */}`)
Error parsing file useful-debugging-tools-for-kubernetes.md from collection posts.
    Unexpected character `!` (U+0021) before name, expected a character that can start a name, such as a letter, `$`, or `_` (note: to create a comment in MDX, use `{/* text */}`)

as a result, admin page is completely unusable atm

@alekc is there any fix or workaround you may have found for this?

Nope, I began to look to other solutions as consequence
On Sun, 7 May 2023, 10:42 Palash Shrivastava, @.***>
wrote:

@alekc https://github.com/alekc is there any fix or workaround you may
have found for this?
—
Reply to this email directly, view it on GitHub
https://github.com/tinacms/tinacms/issues/3213#issuecomment-1537371758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJ5V3CXOXVPNXGJUFGLB3XE5VBFANCNFSM6AAAAAAQRMMN2U
.
You are receiving this because you were mentioned.Message ID:
@.***>


Does not work even with the example

I've been trying to get the range for some animals for my thesis. But even when I try to execute the example presented, to understand how could I use this package for my study, the example does not work.
When I run the function get_gbif, the package returns an empty object with the follow output:
obs.pt = get_gbif(sp_name="Panthera tigris",                    basis=c("OBSERVATION","HUMAN_OBSERVATION","MACHINE_OBSERVATION"))

Total number of records: 4236
...GBIF records of Panthera tigris : download of all records starting...
100 %...
---> Grain filtering...
Records removed: 3440
---> Removal of duplicated records...
Records removed: 344
---> Removal of absence records...
Records removed: 14
---> Basis of records selection...
Records removed: 429
---> Time period selection...
Records removed: 0
No records left after selection...

How can I get the range if I can't even get the occurrence??

Hi there,
I apologize, we are in the process of updating the package, it's not surprising that you run into issues. I can have a look tomorrow and tell you what's wrong.
Best,
Yohann

I am also having this issue.

Hi there,
Everything should be running smoothly from now on. Just keep in mind that evaluation functions such as cross validation are not yet implemented, as this the next steps of the package development. Let me know if you run (or not) into any problems so I can close this issue.
Best,
Yohann

Hi @8Ginette8,
The code as posted on GitHub does work for me now; however, when I uninstall and reinstall the package, I'm not getting the fix. Not sure what is going on there.
Thanks!

Hi there,
Hum that's odd, everything works on our side as we tried on several laptops after your comment. I have updated the examples, maybe it was that. Let me know.
Best,
Yohann

I will close it, just update me in case you run into some issues again


Not possible to combine doxygen + sphinx

Details

Project URL: http://github.com/molpopgen/fwdpy11
Build URL (if applicable): https://readthedocs.org/projects/fwdpy11/builds/5585367/
Read the Docs username (if applicable): molpopgen

Expected Result
breathe to be installed, either via conda or pip
Actual Result
RTD pins Sphinx at 1.3.5.  Breathe requires >= 1.4.  Attempting to install breathe either via conda or pip therefore fails.  The end result is that doxygen output cannot be used in a build.

Hi, I just saw your latest builds are passing, were you able to solve the problem? BTW, you can specify a requirements file with the sphinx version that you want.

I gave up on doxygen, at least for now.
On Tue, May 1, 2018, 12:38 AM Santos Gallegos<EMAIL_ADDRESS>wrote:

Hi, I just saw your latest builds are passing, were you able to solve the
problem? BTW, you can specify a requirements file with the sphinx version
that you want.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rtfd/readthedocs.org/issues/2958#issuecomment-385617436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGHnH2iyLviAsIJbC9bUkgq1ty6Xu-2eks5tuBDNgaJpZM4N_-rt
.

--
Kevin Thornton
Associate Professor
Ecology and Evolutionary Biology
UC Irvine
http://www.molpopgen.org
http://github.com/ThorntonLab
http://github.com/molpopgen

If the issue was because of the sphinx version, rtd now uses 1.7.x as default, and you can always pin the version that you need on your requirements file.

Closing this as the user hasn't responded or given more information, feel free to reopen with more information if you are still having this problem :).


Cant clone git

Hi everyone. Im a noob so im sorry if I am clueless here.
I tried cloning the git / repository using cmd / windows terminal. (if that is where I am supposed to start?).
Anyways I get this error :
PS C:\Users\Greg> git clone git@github.com:Stability-AI/generative-models.git
Cloning into 'generative-models'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
PS C:\Users\Greg> cd generative-models
Thanks for any help!
(I have downloaded the zip folder here plus the model weights for the xl version.

That's your public key setup, not the repo.
Do this https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
Do this https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.
Then this https://docs.github.com/en/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection
Finally, git clone.


Fix documentation param annotations.

Thanks @rhg-square, I need to wait on your CLA in order to merge.

Closing as stale, please reopen if still interested


[AMBARI-24637] Ambari metrics service check failed during UI deploy.

Duplicate of https://github.com/apache/ambari/pull/2315 for trunk.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3950/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3951/
Test PASSed.


create security fix

Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version <IP_ADDRESS> or later. For example:

com.fasterxml.jackson.core
jackson-databind
[<IP_ADDRESS>,)

Always verify the validity and compatibility of suggestions with your codebase.

@andxu I was able to resolve the build failure by updating maven-plugin-plugin version to 3.6.0 .
Not sure if that is the correct fix or not. Please check.

Replace it with new PR https://github.com/microsoft/azure-maven-plugins/pull/777


"pam_authenticate failed" what drives this message?

2019-10-30 15:51:03.239 ERROR 20613 --- [nio-8443-exec-4] o.o.a.s.CustomAuthenticationProvider     : PAM authentication failed: pam_authenticate failed : Authentication failure -- org.jvnet.libpam.PAMException: pam_authenticate failed : Authentication failure
	at org.jvnet.libpam.PAM.check(PAM.java:106)
	at org.jvnet.libpam.PAM.authenticate(PAM.java:124)

Getting this in my program.   Tryied on three different linux OS same result.   Can't seem to figure out what this message is telling me.   Did I miss a step somewhere?
pamtester -v login **** authenticate
This works... but fails via the java program running as the same user.
Tried on Fedora 27, Fedora 29, even a Oracle Linux 7 I had kicking around.

ok finally found the problem.    Never fails I search at a problem but the minute I have to document it into an issue like this I find it.
So my problem was this:
            Collection<? extends GrantedAuthority> authorities = Collections.singleton(new SimpleGrantedAuthority("ROLE_USER"));
            return new UsernamePasswordAuthenticationToken(authentication.getPrincipal(),
                                                           authentication.getCredentials(),
                                                           authorities);

vs
                                                           authentication.getCredentials());

Without the ROLES at the end it authenticates once fine (which I missed in the logs) then blanks out the password.  Then tries a second attempt with a null password.  Which is what I saw above.   When it was a wrong password the thing would fail on first try.
So resolution... pay attention to the logs more closely.      Posting here in case anyone else falls into the same trap but the issue can be closed.


no log delay

Configure Yii logging to immediately output log messages, rather than cache them up. Prevents messages from being lost if the container crashes (e.g. out of memory).

email-service/application/frontend/config/main.php doesn't have the same cache => null that was in the others.

That's because I did the dependency update on a different feature branch. Didn't want a merge conflict on composer.lock.


fix: snapshot comparison with no common keys

Description
This change avoids an unhandled exception when no common keys exist in snapshot comparison and generate an output with added/missing keys.
Also fixes #82 where snapshot comparison properties are getting ignored occasionally.
Motivation and Context
In snapshot comparison when snapshots to be compared had no common keys, this resulted in an un-handled lndexError exception given below. This was happening mostly on arp table comparison where two snapshots had no common entries.
Traceback (most recent call last):
  File "snapshot_load_compare.py", line 39, in <module>
    report = compare.compare_snapshots(reports)
  File "/Users/akose/Development/paloalto/pan-os-upgrade-assurance/panos_upgrade_assurance/snapshot_compare.py", line 126, in compare_snapshots
    {report_type: self._functions_mapping[report_type](**report_config)}
  File "/Users/akose/Development/paloalto/pan-os-upgrade-assurance/panos_upgrade_assurance/snapshot_compare.py", line 565, in get_diff_and_threshold
    diff = SnapshotCompare.calculate_diff_on_dicts(
  File "/Users/akose/Development/paloalto/pan-os-upgrade-assurance/panos_upgrade_assurance/snapshot_compare.py", line 400, in calculate_diff_on_dicts
    if isinstance(right_side_to_compare[list(common_keys)[0]], str)
IndexError: list index out of range

Regarding issue #82 - the check was to compare with string type to find out if we are at the lowest level, and when we encountered a null/None value ConfigParser was not called which resulted in properties not getting processed. This happened randomly since we are checking a value within the common keys and null/None value might or might not be present for the selected key.
How Has This Been Tested?
It has been tested with example scripts in the repository and ansible playbooks.
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

This also fixes #1 for the root level keys, where arp_table might be empty dict for the left or right snapshot and might be present for the other snapshot.
However the requested root level keys must always be present (even as an empty dict), it's not possible to compare snapshots when the requested report is not present at all on one side of the snapshots like "nics".