No feedback when error occur during planning execution

Describe the bug
When the plan command fails, there is no status change nor feedback given to the user; when getting the plan via the API, we still get 204 response code instead of an error
To Reproduce
Steps to reproduce the behavior:

Create a workspace and a project
Start a plan via the API with invalid input with remote source, ie: wrong url so the plan will fail
Command executed should be similar to plan --name a --plan-progress-port 32881 --log-file m2kcli.log --source git+ssh://bitbucket.com/gfarache31/m2k-test@master --disable-local-execution
Check the logs to see the error, something similar to:

time="2024-03-12T09:47:17Z" level=info msg="plan cmdArgs: [plan --name a --plan-progress-port 32881 --log-file m2kcli.log --source git+ssh://bitbucket.com/gfarache31/m2k-test@master --disable-local-execution]"
time="2024-03-12T09:47:17Z" level=info msg="Project: 4a3d44ae-ba55-49b9-ae67-9b0b6d66640e; level=info msg=\"Cloning the repository using git into '/tmp/move2kube3232420242/m2ksources' . This might take some time.\""
time="2024-03-12T09:47:18Z" level=info msg="Project: 4a3d44ae-ba55-49b9-ae67-9b0b6d66640e; level=fatal msg=\"failed to create the plan. Error: \\\"failed to clone the repo 'git+ssh://bitbucket.com/gfarache31/m2k-test@master'. Error: failed to clone using vcs url 'git+ssh://bitbucket.com/gfarache31/m2k-test@master' and clone options {CommitDepth:1 Overwrite:true MaxSize:-1 CloneDestinationPath:/tmp/move2kube3232420242/m2ksources}. Error: failed to perform clone operation using git. Error: repository already exists\\\"\""
time="2024-03-12T09:47:18Z" level=error msg="failed to update the database after planning finished. Error: \"failed to copy the plan file from /tmp/plan-4a3d44ae-ba55-49b9-ae67-9b0b6d66640e-4058952779/m2k.plan to /move2kube-api/data/projects/4a3d44ae-ba55-49b9-ae67-9b0b6d66640e/inputs/expanded/m2k.plan after planning finished. Error: \\\"failed to open the source file at path \\\\\\\"/tmp/plan-4a3d44ae-ba55-49b9-ae67-9b0b6d66640e-4058952779/m2k.plan\\\\\\\" Error: \\\\\\\"open /tmp/plan-4a3d44ae-ba55-49b9-ae67-9b0b6d66640e-4058952779/m2k.plan: no such file or directory\\\\\\\"\\\"\""

Send a GET request to the plan and see you have a 204 response code instead of a 5XX one as the planning has failed

Expected behavior
I expect that plan status to change to failed or similar and to be able to get the error information via the API (maybe not the full reason but at least that it failed)
Screenshots
N/A
Desktop (please complete the following information):

OS: [e.g. iOS] Fedora
Browser [e.g. chrome, safari] chrome
Version [e.g. 22] v0.3.11

Additional context
Related to https://github.com/konveyor/move2kube-ui/issues/169

@seshapad @HarikrishnanBalagopal Any thoughts on a fix for this issue?

FYI, it appears that the logs in the log file m2kcli.log are the same as the one in the output
So the issue may come from the move2kube CLI itself

The weird error originates from here https://github.com/konveyor/move2kube/blob/main/common/vcs/git.go#L260
Here, m2k is retrying to clone the repo but not on the target branch directly but the directory is not cleaned so it appears the directory that should have host/contained the cloned repository was created so when we try to clone again, it fails because a folder with the same name already exists.
By setting the loc to Warning instead of Debug I see the follwing log:
time="2024-07-05T14:58:48Z" level=info msg="Project: 80cc87ba-5c30-42ac-ac79-e9ad29bf9237; level=info msg=\"failed to clone the given branch 'masters': \\\"couldn't find remote ref \\\\\\\"refs/heads/masters\\\\\\\"\\\" . Will clone the entire repo and try again.\""

which confirm my above assumption.
I'll create a PR to clean the folder and to better log what is happening

Thanks @gabriel-farache . Please let us know when the PR is ready for review

@ashokponkumar My PR is ready for review, please let me know your feedback.

@ashokponkumar do you know when a new release with the fixes can be released?

@ashokponkumar do you know when a new release with the fixes can be released?

@HarikrishnanBalagopal @seshapad Can we please trigger a new release?

@HarikrishnanBalagopal Thank you! Now I see a v0.3.14-rc.0 tag in quay, should I use this or should I wait for the v0.3.14?

@HarikrishnanBalagopal @ashokponkumar Any update on the release? Thx :)

@HarikrishnanBalagopal Thank you! Now I see a v0.3.14-rc.0 tag in quay, should I use this or should I wait for the v0.3.14?

@gabriel-farache yes please go ahead.


Issues with parenthesis and variables

In the JS version this seems to work, but not in the Python version.
! var test = Hi there

+ hi
- <bot test>

+ get lost
% <bot test>
- why?

The same also applies for utf8 characters.
! var test = hæ there

+ hi
- <bot test>

+ get lost
% <bot test>
- why?

Anybody know how to fix this?

This should be fixed using the current master branch of this repo. I'll do a deployment to PyPI later.
https://github.com/aichaos/rivescript-python/commit/5c5157455ff9a3f92f550d709435694940128f42
The root cause was that the <bot test> was returning a string with capital letters, so "Hi there" wasn't matching "hi there". I also fixed a similar issue with lowercasing @Redirects that I found on the Go version.


Regridder: wrong dimension 'y' in result grid using method="nearest"

In GitLab by @FransRoelofsen on Apr 14, 2022, 16:38
The result of the following command produces a 'wrong' DataArray in case 'nearest' is used.
tmp = imod.prepare.Regridder(method="nearest").regrid(dem_idf, IDF_master)
Using this "tmp" in the next command produces a ValueError: "indexes along dimension 'y' are not equal"
riv_bottom = xr.where(lake_idf== 0,x=tmp,y=np.nan)
Correction is needed in def regrid(self, source, like, fill_value=np.nan) in the section if self.method == "nearest":

The regridder in iMOD Python is deprecated and is planned to be removed in the v1.0 release.
Use the xugrid regridder for single arrays
Or use iMOD Python to regrid entire MODFLOW6 simulations and packages


Observable subscription in constructor.

Multiple issues - no finalizers, also this leak as it is against safe construction techniques. check blog


Custom attributes as dynamic virtual columns in reports

Purpose or intent
Note: There are still couple issue in diplaying this field etc. Mostly of them are tracked in pivot tracker. Link below
Initial implementation of reporting custom attributes with behaviour as normal field.
Is basically normalizing custom attributes in report and you can generated reportf(after):

instead of(before):

with using all common features(filtering, ... ) in report definition
I can separated this PR into parts:
1. Building list for Available Fields with custom attributes

Commits:
https://github.com/ManageIQ/manageiq/pull/9451/commits/fa127742b0e92a63430f92f49130b6f149e3cc37
https://github.com/ManageIQ/manageiq/pull/9451/commits/bfa7ba8eccf07df02df21884106d22c44aee9d06
https://github.com/ManageIQ/manageiq/pull/9451/commits/4be4a0ee72e4fcc9b23f65ca11a4303731bc1c73
2. Support for loading dynamic virtual columns
This is adding virtual columns dynamically.
Commit: https://github.com/ManageIQ/manageiq/pull/9451/commits/5cb347f6d08a4f57b960b1832a4233d3ff93a453
3. Load these virtual columns when report generated
Commit: https://github.com/ManageIQ/manageiq/pull/9451/commits/bebbd7d48ca60f980d38b6f8a53f745c3482543e
4. Other issues: Tackling with saving report a removing association for build report
https://github.com/ManageIQ/manageiq/pull/9451/commits/0c5a34f3b9d684f5b19d1456bda93f146ffa747c
https://github.com/ManageIQ/manageiq/pull/9451/commits/c9f8d004f85f7448d95bd60faedb9a56f1a2edfe
...
What needs to be stored in report definition (MiqReport)
Let's assume that we have Vm report and one field for name of VM and 3 our new virtual columns, so then we have minimally in db:
MiqReport#cols
[
    [0] "name",
    [1] "virtual_custom_attribute_attr_name_1_1",
    [2] "virtual_custom_attribute_attr_name_1_3",
    [3] "virtual_custom_attribute_attr_name_2_1"
]

MiqReport#col_order
[
    [0] "name",
    [1] "virtual_custom_attribute_attr_name_1_1",
    [2] "virtual_custom_attribute_attr_name_1_3",
    [3] "virtual_custom_attribute_attr_name_2_1"
]

MiqReport#include
{
    :custom_attributes => {}
}

^^ this is need for preloading this table in base query for reporting.
Utility  scripts
How to add some custom attributtes for Vms
Vm.all.each do |vm|
  $evm = MiqAeMethodService::MiqAeService.new(MiqAeEngine::MiqAeWorkspaceRuntime.new)
  vm = $evm.vmdb('vm', vm.id )
  vm.custom_set("ATTR_Name_1_#{vm.id}", 'Some string you want to add')
  vm.custom_set("ATTR_Name_2_#{vm.id}", 'Some string you want to add')
end
```

## Links
https://bugzilla.redhat.com/show_bug.cgi?id=1292860
https://www.pivotaltracker.com/n/projects/1608513/stories/121954975

@miq-bot add_label wip

@gtanzillo
It seems that I solved performance issue when we are building querying as you told me.
I am generating all in query (I guess that it is even better than we are using ordinarily relations report ) because custom_attributes are loaded  here already https://github.com/ManageIQ/manageiq/pull/9451/files#diff-7e58626b2d588f087774d0d023c0ba90R41  and then I just searching in array for value of custom attribute
@kbrock so I need you performance eye here, whether it is ok:

Building list of custom attributes with available fields:
it is done basically by this query: https://github.com/ManageIQ/manageiq/pull/9451/commits/fa127742b0e92a63430f92f49130b6f149e3cc37

Query for generating report with our new virtual columns
https://github.com/ManageIQ/manageiq/pull/9451/commits/5cb347f6d08a4f57b960b1832a4233d3ff93a453 - adding dynamic virtual columns
https://github.com/ManageIQ/manageiq/pull/9451/commits/58aa1c13414839c692aa13b6def79ae0236dd6d8 -  loading for report

Thanks!!!

I ran the numbers with VmOrTemplate: 100 records
Grain of salt for some of those numbers. it is a small query to be testing and the overhead of my tools will come into play. but the number of objects created is far less.  100 rows came back for me in both. it just isn't showing in the second case because it never instantiates an object for those.
But the difference in object allocation speaks for itself.
before
VmOrTemplate.all.map(&:name).uniq
  VmOrTemplate Load (1.3ms)  SELECT "vms".* FROM "vms"
  VmOrTemplate Inst Including Associations (8.6ms - 100rows)

ms
bytes
objects
queries
query (ms)
rows
comments

105.6
769,835
5,923    1
9.5
100
no name-1

9.5

1.0
100
.SELECT "vms".*

after
VmOrTemplate.all.distinct.pluck(:name)
   (0.7ms)  SELECT DISTINCT "vms"."name" FROM "vms"

ms
bytes
objects
queries
query (ms)
rows
comments

99.4
55,090
977
1
0.4

no name-1

0.4

0.4

.SELECT DISTINCT "vms"."name"

@kbrock thanks for you feedback!! I made your suggestions but there is question here https://github.com/ManageIQ/manageiq/pull/9451#discussion_r69287007

This is looking very good @lpichler

@miq-bot remove-label wip

@gtanzillo I have added specs, ready for final review, remaining issues are tracked in pivotracker.
I'll update screenshots tommorrow.

Thanks @lpichler, looks good 👍

@gtanzillo screenshots and description updated.


trt_export error in "lung_nodule_ct_detection"

03/15/2024 02:05:41 AM bundle_test _run_commands INFO: Executing export PYTHONPATH=$PYTHONPATH:/workspace/lung_nodule_ct_detection && echo $PYTHONPATH && python -m monai.bundle trt_export --net_id network_def --filepath /workspace/lung_nodule_ct_detection/models/model_trt.ts --ckpt_file /workspace/lung_nodule_ct_detection/models/model.pt --precision fp16 --meta_file /workspace/lung_nodule_ct_detection/configs/metadata.json --config_file /workspace/lung_nodule_ct_detection/configs/inference.json --logging_file /workspace/lung_nodule_ct_detection/configs/logging.conf  --input_shape "[1, 1, 512, 512, 192]" --use_onnx "True" --use_trace "True" --onnx_output_names "['output_0', 'output_1', 'output_2', 'output_3', 'output_4', 'output_5']" --network_def#use_list_output "True"  2>&1 | tee running.log
:/workspace/lung_nodule_ct_detection
2024-03-15 02:05:52,411 - INFO - --- input summary of monai.bundle.scripts.trt_export ---
2024-03-15 02:05:52,411 - INFO - > net_id: 'network_def'
2024-03-15 02:05:52,411 - INFO - > filepath: '/workspace/lung_nodule_ct_detection/models/model_trt.ts'
2024-03-15 02:05:52,411 - INFO - > meta_file: '/workspace/lung_nodule_ct_detection/configs/metadata.json'
2024-03-15 02:05:52,411 - INFO - > config_file: '/workspace/lung_nodule_ct_detection/configs/inference.json'
2024-03-15 02:05:52,411 - INFO - > ckpt_file: '/workspace/lung_nodule_ct_detection/models/model.pt'
2024-03-15 02:05:52,411 - INFO - > precision: 'fp16'
2024-03-15 02:05:52,411 - INFO - > input_shape: [1, 1, 512, 512, 192]
2024-03-15 02:05:52,411 - INFO - > use_trace: True
2024-03-15 02:05:52,411 - INFO - > use_onnx: True
2024-03-15 02:05:52,411 - INFO - > onnx_output_names: ['output_0', 'output_1', 'output_2', 'output_3', 'output_4', 'output_5']
2024-03-15 02:05:52,411 - INFO - > logging_file: '/workspace/lung_nodule_ct_detection/configs/logging.conf'
2024-03-15 02:05:52,411 - INFO - > network_def#use_list_output: True
2024-03-15 02:05:52,412 - INFO - ---

There is no dynamic batch range. The converted model only takes [1, 1, 512, 512, 192] shape input.
Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
Encountering a list at the output of the tracer might cause the trace to be incorrect, this is only valid if the container structure does not change based on the module's inputs. Consider using a constant container instead (e.g. for `list`, use a `tuple` instead. for `dict`, use a `NamedTuple` instead). If you absolutely need this and know the side effects, pass strict=False to trace() to allow this behavior.
[03/15/2024-02:06:57] [TRT] [W] onnx2trt_utils.cpp:374: Your ONNX model has been generated with INT64 weights, while TensorRT does not natively support INT64. Attempting to cast down to INT32.
[03/15/2024-02:11:40] [TRT] [E] 10: Could not find any implementation for node {ForeignNode[/classification_head/conv/conv.1/Constant_1_output_0 + (Unnamed Layer* 130) [Shuffle].../regression_head/conv/conv.2/Relu]}.
[03/15/2024-02:11:40] [TRT] [E] 10: [optimizer.cpp::computeCosts::3869] Error Code 10: Internal Error (Could not find any implementation for node {ForeignNode[/classification_head/conv/conv.1/Constant_1_output_0 + (Unnamed Layer* 130) [Shuffle].../regression_head/conv/conv.2/Relu]}.)
Traceback (most recent call last):
  File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.10/dist-packages/monai/bundle/__main__.py", line 31, in <module>
    fire.Fire()
  File "/usr/local/lib/python3.10/dist-packages/fire/core.py", line 143, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/usr/local/lib/python3.10/dist-packages/fire/core.py", line 477, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/usr/local/lib/python3.10/dist-packages/fire/core.py", line 693, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/monai/bundle/scripts.py", line 1516, in trt_export
    _export(
  File "/usr/local/lib/python3.10/dist-packages/monai/bundle/scripts.py", line 1091, in _export
    net = converter(model=net, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/monai/networks/utils.py", line 965, in convert_to_trt
    trt_model = _onnx_trt_compile(
  File "/usr/local/lib/python3.10/dist-packages/monai/networks/utils.py", line 849, in _onnx_trt_compile
    f.write(serialized_engine)
TypeError: a bytes-like object is required, not 'NoneType'

I think this line here is the reason:
[03/15/2024-02:11:40] [TRT] [E] 10: Could not find any implementation for node {ForeignNode[/classification_head/conv/conv.1/Constant_1_output_0 + (Unnamed Layer* 130) [Shuffle].../regression_head/conv/conv.2/Relu]}.

The serialized engine is not generated due to an unsupported operator.

This one is about the wrong driver version. Please update the driver to the latest one.


Error

OpenWrt R24.2.2
6.1.76
https://github.com/coolsnowwolf/lede
Configuring luci-i18n-nlbwmon-zh-cn.
Collected errors:

check_data_file_clashes: Package iperf3-ssl wants to install file /home/powerccc/lede/build_dir/target-x86_64_musl/root-x86/usr/bin/iperf3
But that file is already provided by package  * iperf3
opkg_install_cmd: Cannot install package iperf3-ssl.
make[2]: *** [package/Makefile:70: package/install] Error 255
make[2]: Leaving directory '/home/powerccc/lede'
make[1]: *** [package/Makefile:111: /home/powerccc/lede/staging_dir/target-x86_64_musl/stamp/.package_install] Error 2
make[1]: Leaving directory '/home/powerccc/lede'
make: *** [/home/powerccc/lede/include/toplevel.mk:231: world] Error 2

make menuconfig，Network ->  IPERF3-SSL，取消它，保存了.CONFIG，重新编译后成功。

This project does not support Lean lede.


chore(release): Release 4.0.2

Retrying after 4.0.1 failed at publication, thinking it was a temporary issue:
https://github.com/quarkiverse/quarkus-logging-splunk/actions/runs/11614875606/job/32344067568

Maven central is facing some timeout issues. I'll rerun the release job once it gets back: https://github.com/quarkiverse/quarkiverse-release/actions/runs/11616384164


Expose TPVWSimplifier

Does shapely already expose the GEOS implementation of Topology-Preserving Visvalingam-Whyatt Line Simplification through its Python API? (I couldn’t find it in the docs, but I might have looked at the wrong place). If it’s not exposed yet, would a Python wrapper be in scope for shapely?

It is being implemented... https://github.com/shapely/shapely/pull/1969


Sample config files?

Hey, nice work on the stack. All of these services volume out a config directory, any plans on sharing some example configs?

Thanks, appreciate the feedback.
No plans to supply example configs for services at the moment, in part because I don't want to dictate configuration to users beyond the structure of the stack.
Additionally, having a set of example configs would likely result in users being lazy and not changing the API keys to unique ones. Ideally we'd be able to supply a file location for API keys on per-service basis, allowing the use of Docker secrets - but I don't have much desire to submit a PR to each project to enable that.

Makes sense, thank you. Secrets would indeed be nice. These stacks populate the config directory with config files if the files don't exist, so that makes it easy to modify.
I ask primarily with Traefik in mind as I am having a hard time getting the [acme] config to work properly. It either fatals out with an unknown entrypoint message, or it redirects endlessly and eats up 16GB RAM in 30 seconds.
There is a catch (and possibly something that warrants a README update) - if individual files are volumed in, and the files don't already exist on the host, Docker will create directories with these names instead of files. This causes Traefik to have a hissy fit.
  traefik:
    image: traefik:latest
    ...
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ${CONFIG}/traefik/acme.json:/acme.json
      - ${CONFIG}/traefik/traefik.toml:/etc/traefik/traefik.toml
      - ${CONFIG}/traefik/.htpasswd:/etc/traefik/.htpasswd:ro

For example, if traefik/acme.json does not exist on the host, Docker creates traefik/acme.json/ (a directory) instead of a file. The easy solution is to ensure that these files exist on the host before starting this container.
This brings me to my current problem of trying to configure Traefik - I have created traefik.toml and am trying to populate it using various web examples, but I either get a fatal or an endless redirect loop and massive memory leak.
More questions:

Would you be willing to share a cleaned copy of traefik.toml from your setup?
Are you attached to Traefik?
I'm a co-author of https://github.com/CausticLab/rgon-proxy which we wrote to be a simpler Nginx reverse proxy option - would you be interested in seeing a PR to swap Traefik for Rgon?

For example, if traefik/acme.json does not exist on the host, Docker creates traefik/acme.json/ (a directory) instead of a file. The easy solution is to ensure that these files exist on the host before starting this container.

Indeed, this is expected behaviour from Docker (although whether it's desirable is another thing).  The README does contain steps that, if followed, should ensure users don't end up encountering that issue.

Would you be willing to share a cleaned copy of traefik.toml from your setup?

My setup, sans email, is below. It should be identical to the provided example in the repo. It's odd you're encountering issues, could you attach the Traefik log?
debug = false

logLevel = "ERROR"
defaultEntryPoints = ["https","http"]

[entryPoints]
  [entryPoints.http]
  address = ":80"
    [entryPoints.http.redirect]
    entryPoint = "https"
  [entryPoints.https]
  address = ":443"
  [entryPoints.https.tls]

[entryPoints.https.auth.basic]
  usersFile = "/etc/traefik/.htpasswd"

[retry]

[acme]
email =<EMAIL_ADDRESS>storage = "acme.json"
entryPoint = "https"
OnHostRule = true
[acme.httpChallenge]
entryPoint = "http"

Are you attached to Traefik?

In the sense of wanting to continue to use it? I am.
In the sense of being involved with the project in a role other than consumer? I am not.

I'm a co-author of https://github.com/CausticLab/rgon-proxy which we wrote to be a simpler Nginx reverse proxy option - would you be interested in seeing a PR to swap Traefik for Rgon?

Right now Traefik fulfills my requirements well, but should that change in the future I'll definitely keep Rgon in mind.


Misleading behavior on matrix and vector division, which is in contradiction with the documentation in nn.softmax

System information

Have I written custom code: Yes
OS Platform and Distribution: Linux-5.4.104+-x86_64-with-Ubuntu-18.04-bionic
TensorFlow version (use command below): 2.7.0
Python version: 3.7.12

Describe the current behavior
I found a misleading behavior when using broadcast between matrix and vectors. I will use the example of softmax to demonstrate the issue, which if it's not a bug then the following documentation I believe it is wrong " https://www.tensorflow.org/api_docs/python/tf/nn/softmax".
# random matrix
A = tf.random.uniform((4,4), maxval=10, dtype=tf.float64)

# softmax by hand, as suggested in: https://www.tensorflow.org/api_docs/python/tf/nn/softmax
A_softmax = tf.exp(A) / tf.reduce_sum(tf.exp(A), axis=-1)
tf.reduce_sum(A_norm, axis=-1)
# >>> <tf.Tensor: shape=(4,), dtype=float64, numpy=array([0.79724022, 0.34883704, 3.8507741 , 2.37962821])>

A_nn_softmax = tf.nn.softmax(A, axis=-1)
tf.reduce_sum(A_nn_softmax, axis=-1)
# >>> <tf.Tensor: shape=(4,), dtype=float64, numpy=array([1., 1., 1., 1.])>

In the above example, I use the tf.nn.softmax as a baseline and then use the corresponding computation as described in the documentation ( that is also the way I usually implement the softmax operation ). However, as you can see, A_softmax (direct computation) and A_nn_softmax (from the function nn.softmax) gave two different outputs, which according to the documentation should have not happened. I expect the same output for both matrices.
After some time I realise that the problem was related to the column-wise division that has, what I believe to be, a misleading behaviour.
tf.exp(A) / tf.reduce_sum(tf.exp(A), axis=-1)

In the above computation, I am dividing a (4, 4) matrix per (4,) vector, which I expect to perform a column-wise division since it is a column vector. However, it performs a row-wise division. I would like to know if this is an intended behavior and if so, I believe that the documentation of nn.softmax is wrong and should be "tf.exp(logits) / tf.reduce_sum(tf.expand_dims(tf.exp(logits), axis=-1), axis=-1)".
Describe the expected behavior
I expect that A_softmax equals A_nn_softmax.
To achieve the expected behavior I need to implicitly add an additional dimension to the denominator vector, becoming (4, 1).
In code correspond to:
tf.exp(logits) /tf.expand_dims(tf.reduce_sum(tf.exp(logits), axis=-1), axis=-1)

In alternative I can also use "keepdims=True" when doing the reduce_sum
Standalone code to reproduce the issue
https://colab.research.google.com/drive/1Iv7cw4_gddfaxre5AD_oBQlGih6cJvMM?usp=sharing

I was able to run more experiments, and now I believe that is indeed the intended behavior and after all, what was misleading was the documentation in nn.softmax "tf.exp(logits) / tf.reduce_sum(tf.exp(logits), axis)", since is wrong when axis=-1 which is the default behavior.
Maybe change this to a documentation issue?

@T-Almeida ,
I ran the code shared and face a different error, please find the gist here and share all dependencies to replicate the issue.

Hi, indeed I change the code and forgot to update that line, my mistake.
Instead of "tf.reduce_sum(A_norm, axis=-1)" it should be "tf.reduce_sum(A_softmax, axis=-1)". Then the output of this should be ones (correct normalization sums to 1), as suggested in https://www.tensorflow.org/api_docs/python/tf/nn/softmax . However, you will see that this is not true because the vector resulting from the reduce_sum operation is handled as a row-vector (I believe). Therefore, I consider this to be an issue related to the documentation. Nevertheless, I found that to be also misleading since a column-wise reduce operation results in a row-vector.

@T-Almeida,
In this case of documentation bug, Would you like to submit a PR addressing the issue? Thanks!

Hi, @sanatmpa1 yes sure, I can open a PR.

@T-Almeida,
As the PR that you have submitted is merged, Can you confirm if we are good to close this issue? Thanks!


How to “EXPIRE” the “HSET”  key in redis?

The think  is here:
First,I SetCacheDuration
RedisCache.Expire(key string, expiration time.Duration)
Second,I HSetCache
RedisCache.HSet(key, field string, value interface{})
Thind,I HGetCache
RedisCache.HGetAll(key string)
but the EXPIRE is does't work,and  HGetAll is always exsist ,even though the first and second does't execute and as a result the map is [].
please deal this issues ,   Thank very much;
best wishes！

I believe that is how Redis works - HGetAll returns empty result even when key does not exist:
<IP_ADDRESS>:6379> hgetall this-key-does-not-exist
(empty list or set)


:host CSS selector not working on live reload when Ivy enabled

🐞 Bug report
Command
- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?
Yes, the previous version in which this bug was not present was: when Ivy is not enabled it works as expected.
Description
I have a shared component in my app that has this kind of template:
<div class="wrapper">
  <ng-content></ng-content>
</div>

A couple of routed components are using that shared component in a normal way:
<shared-component input="myInput">HTML content here!</shared-component>

All components (the shared one and the entry ones) are using changeDetection: ChangeDetectionStrategy.OnPush.
The routed components have an extra meta property: host: { class: 'routed-content' }.
And also all of them are styling the element that hosts their corresponding component by using the :host pseudo-class in the *.scss file.
Now, the problem is that when you run npm start (ng serve) it loads all the styles property on the first load but we perform any changes either in the HTML template or in the Sass filed the live reloading is not rendering the app correctly. All styles applied to the host are missing.
🔬 Minimal Reproduction
Simply create an Ivy enabled app with a SharedModule imported in the AppModule and set the components as described above.
Then check the missing styles on the reloads.
🌍 Your Environment
Angular CLI: 8.1.1
Node: 10.15.3
OS: darwin x64
Angular: 8.1.1
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, language-service, material, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.801.1
@angular-devkit/build-angular     0.801.1
@angular-devkit/build-optimizer   0.801.1
@angular-devkit/build-webpack     0.801.1
@angular-devkit/core              8.1.1
@angular-devkit/schematics        8.1.1
@ngtools/webpack                  8.1.1
@schematics/angular               8.1.1
@schematics/update                0.801.1
rxjs                              6.4.0
typescript                        3.4.5
webpack                           4.35.2

I tried this locally and it seems to work.
First load

Second load on changing the color

I'm sorry, but we can't reproduce the problem following the instructions you provided.
Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue.
Short, explicit instructions make it much more likely we'll be able to reproduce the problem so we can fix it.
If the problem persists, please open a new issue following our submission guidelines.
A good way to make a minimal repro is to create a new app via ng new repro-app and add the minimum possible code to show the problem. Then you can push this repository to github and link it here.


Live Server not working properly

Type: Performance Issue
When i open the server, the page opens up but when i edit or change the coding or contents the changes doesnt apply when i refresh the page. It only applies when i close the server and reopen the live server. How do i fix this as it is frustrating to keep on closing and opening the live server.
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:

Hi,
Thanks for reaching VS Marketplace Support Team, could you please share detailed steps to reproduce the issue, details of the publisher and Extension details to investigate further.
Regards,
VS Marketplace Team

Closing the issue since there has been no updates on the information requested. If the issue still persists, please feel free to reopen or create a new issue.
Regards,
VS Marketplace Team


ONNX runtime support for MPSoC devices

Hello all,
https://github.com/Xilinx/Vitis-AI/tree/master/external/onnxruntime, Here, as you have mentioned, the Vitis ai execution provider in ONNX runtime supports DPUCADX8G(u200/250) devices.
So my question is, do we need to wait for future releases for targeting other DPU architectures or is it possible to do the same on a user level. If that's the case, it would be really helpful, if someone can provide me some resources.
Thanks in Advance.

Hi @zackdilan , we currently have an open PR on the ONNX Runtime repo to add support for other DPU's: https://github.com/microsoft/onnxruntime/pull/6690. As stated in the PR, it's targeted at adding support for DPUCZDX8G (Zynq devices), but as the PR allows passing the DPU identifier as a provider option to the ONNX Runtime inference session, it will make it more easy to add support for other DPU's too. For example, DPUCAHX8H (u50, u280) support is upcoming. Did you have any specific DPU in mind?

Thanks @jtuyls . No I was actually looking for implementations for DPUCZDX8G (Zynq devices). When we can expect this?

@zackdilan Ah, I missed the MPSoC in the title. The DPUCZDX8G target will be enabled when the PR gets merged. The timeline depends on when ONNX Runtime people can review and approve it. If you want to try it out you can use the PR though. Documentation is work in progress but I will do a separate PR for that shortly.

@jtuyls thanks again ... I will keep an eye on the PR then. So in the meantime, I will keep this issue open for few weeks, I m not sure when I have time to explore it.  let's say 2 weeks, otherwise, we can close this issue.

Also want to use onnxruntime on the ZCU106 with dpu.
And could the onnxruntime will be supported in the future device such as AIE board?

Hi,
About the soc Zynq UltraScale+ MPSoCs EV XCZU4EV-1SFVC784I supporting for onnx?

Hi,
it is written in documentation that  DPUCZDX8G (Zynq) is supported for onnxruntime. But I can not find any installation instructions
Will you have any updates soon?
Thanks

I'm seeing some interesting notes in the PR as well, as the PR references the vitis-ai docker (x86), but also adds the cross-compilation tools. What it does not seem to have is a way actually actually push and RUN the model on the edge device, even if the provider field now supports this. I'm not sure how onnxruntime would work on a Zynq device without some other layer in there, even if it does support building and optimizing a model for the DPU

I'm sorry, but why was this issue closed with no comment? Does Xilinx have a statement on this at all? I'd love to know if an ONNXruntime with an xrt backend will be available for Zynq DPUs, and the toolflow is definitely tied to Vitis-AI,.
If there was a recent push to Vitis-AI, can you at least reference the commit?


Channel specific welcome messages (MOTD)

Being able to set a message that's sent in the UsersOnline packet, with some information about the channel, specific to the current channel.
With the amount of people asking about 'hacking' related content, it might be nice to have a channel oriented message on join. To remind people about the target topic of discussions.
additionally a command for moderators to set the message for a certain channel
send({cmd:'motd', test:'Welcome to the programming channel.'});


[Gatsby] Update gatsby-theme-newrelic to remove trailing-slash-related code

Another finding from our build audit that this code is causing some performance impacts so we no longer need this, let's remove it to clean up the code.

Effort
Impact

TBD
TBD

References
The complete build audit can be found in the directory: G:drive: Gatsby Cloud Build Audit
Acceptance Criteria

[ ] remove all code relating to trailing slashes

I'm not sure if this is relevant anymore, we have a config setting for this found here as well as some code here


Clarify permissions issue with managing forking policies

Code of Conduct

[x] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

"Managing the forking policy of your repository"

What part(s) of the article would you like to see updated?
After step 3, add some context to explain to users the most common likely next action if they're unable to complete the step.
Add a new paragraph such as the following:
If you do not have this option, you may not have permissions for this setting. Check with the owner of the organization that administers the repository.

Additional information
In GitHub Docs reader feedback, we've received comments from people who weren't able to complete this task. Comments this month included:

No such option exist in current version of GitHub
'Allow forking' does not appear under features
There simply is no option called "Allow Forking" under settings
The allow forking is not on the 2023 version

We reviewed the article for accuracy with the repositories team, and our hypothesis is that these users don't have the permissions needed to manage the forking policy for a repository. They likely did not see the permissions statement at the top of the article or the introductory info explaining permissions.
Adding this new bit of text should help people who get stuck and aren't sure what to do. It doesn't merit a full Troubleshooting section with its own header, but it's worth adding nonetheless.

Hello @meowius
I am interested in doing this issue
so kindly assign me this
so that i can get started with it
Thank You : )

this option, you may not have permissions for this setting. Check with the owner of the organization that administers the repository

ในวันที่ อา. 1 ต.ค. 2023 1:55 AM Vincent Calderone @.***>
เขียนว่า:

this option, you may not have permissions for this setting. Check with the
owner of the organization that administers the repository
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/issues/28608#issuecomment-1741841266, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCWIOFLTQ6E2GTYMRC5GM6TX5BWZRANCNFSM6AAAAAA5MS4N6A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add tests for setting the new params

What ❔
Add additional tests for setting the new params
Why ❔

Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.

@vladbochok in any case, the changes from this branch has been included in the following release: https://github.com/matter-labs/era-contracts/pull/167


Uncaught RangeError: Maximum call stack size exceeded

Hi. I'm new in d3.js and I'm trying to render a huge graph by using d3.layout.force.
My graph has a more that 5000 nodes and more than 8000 links. Maybe there is a limitation for nodes and links count?
When I render only a nodes, all looks fine(rendered slowly, but it's not a critical)
In url you can find JSON and html
https://drive.google.com/folderview?id=0BzE3fJc8LPFWQS1naGk5OVlfVVU&usp=sharing

I expect the issue is that many of the nodes are coincident, causing the quadtree to be degenerate and then causing very deep recursion.

This has been fixed in 4.0 thanks to the new non-recursive d3-quadtree implementation.


Do not use bare except: clauses

https://docs.python.org/2/howto/doanddont.html#except

@andersk Forgot to say thanks :) I merged it when I was quite sleepy.


fix: Prevent page reload when launching an application from the applications dashboard

Description
Prevent page reload when launching an application from the applications dashboard
Fixes #11537
Type of change

Performance fix

How Has This Been Tested?

Manual

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

/ok-to-test sha=5a78850

/ok-to-test sha=4154296

/ok-to-test sha=a87ec00


Catch exception when delegate exception handler process.

If someone define a exception handler which will throw exception when process, catch it to avoid program exit.

Hi @horizonzy , thank you for taking the time to send us a pull request.
Unfortunately I do not think this is a change we would want to make.
The default exception handler is the FatalExceptionHandler and it's main job is to be fatal, and throw an exception after logging.
Wrapping the code that calls this with a try-catch, handling that exception, would go against that purpose.
If you wanted an exception handler to not throw an exception, to avoid the program exiting, then you can define an exception handler that does such a thing, like the IgnoreExceptionHandler for example.
Exception handlers throwing exceptions is an exceptional event, and should be treated accordingly.

Also, from a code-review point of view, I see you used catch (Exception e) and e.printStackTrace(), both of which I would probably advise against.
In your case it seems you want to try and catch any possibly problem from the handler, and log the error. Catching Throwable might have been preferred given that covers Exception as well as Error which could have been thrown.
e.printStackTrace() is generally bad practice as it's going to print that stack trace to System.err and where that gets redirected is out of the libraries control.
If we want to log the stack trace we should use the logging framework, and you can see that's what we do in the FatalExceptionHandler and IgnoreExceptionHandler.

Hi @horizonzy , thank you for taking the time to send us a pull request.
Unfortunately I do not think this is a change we would want to make.
The default exception handler is the FatalExceptionHandler and it's main job is to be fatal, and throw an exception after logging.
Wrapping the code that calls this with a try-catch, handling that exception, would go against that purpose.
If you wanted an exception handler to not throw an exception, to avoid the program exiting, then you can define an exception handler that does such a thing, like the IgnoreExceptionHandler for example.
Exception handlers throwing exceptions is an exceptional event, and should be treated accordingly.
Also, from a code-review point of view, I see you used catch (Exception e) and e.printStackTrace(), both of which I would probably advise against.
In your case it seems you want to try and catch any possibly problem from the handler, and log the error. Catching Throwable might have been preferred given that covers Exception as well as Error which could have been thrown.
e.printStackTrace() is generally bad practice as it's going to print that stack trace to System.err and where that gets redirected is out of the libraries control.
If we want to log the stack trace we should use the logging framework, and you can see that's what we do in the FatalExceptionHandler and IgnoreExceptionHandler.

Hi @horizonzy , thank you for taking the time to send us a pull request.
Unfortunately I do not think this is a change we would want to make.
The default exception handler is the FatalExceptionHandler and it's main job is to be fatal, and throw an exception after logging.
Wrapping the code that calls this with a try-catch, handling that exception, would go against that purpose.
If you wanted an exception handler to not throw an exception, to avoid the program exiting, then you can define an exception handler that does such a thing, like the IgnoreExceptionHandler for example.
Exception handlers throwing exceptions is an exceptional event, and should be treated accordingly.
Also, from a code-review point of view, I see you used catch (Exception e) and e.printStackTrace(), both of which I would probably advise against.
In your case it seems you want to try and catch any possibly problem from the handler, and log the error. Catching Throwable might have been preferred given that covers Exception as well as Error which could have been thrown.
e.printStackTrace() is generally bad practice as it's going to print that stack trace to System.err and where that gets redirected is out of the libraries control.
If we want to log the stack trace we should use the logging framework, and you can see that's what we do in the FatalExceptionHandler and IgnoreExceptionHandler.

Thanks for your suggestion.


Fix test for intial state dispatch upon subscription

I noticed that the test for initial state dispatching to subscribers contained a state change via SetValueAction.
So the test didn't actually assert what it said.
I split this into 3 tests: one for simple state change, two for initial state dispatching.
This is such a weird oversight that I wonder if I interpreted the tests wrong, though.

Oh no, forgot Travis CI is broken here as well :|

I have disabled the branch protection requirement for Travis for the time being. We will need to be extremely diligent that everything compiles + tests pass before merging.
This PR is 👍  because it is only in test code. No actual framework code affected.

Was hesitant to disable protection, but it's probably better than not making any progress until we add GitHub Actions to this repo. -- If any one of you has an idea how we can make the multi-platform and version testing better than the abomination I came up with in ReSwift-Thunk, please do share :) https://github.com/ReSwift/ReSwift-Thunk/blob/master/.github/workflows/cross-platform-compile.yml


Meteor server debug fails

Using the recipe I timout with ECONNREFUSED <IP_ADDRESS>.9229.

Same for me.

update plz?

Specifically, from PowerShell:
meteor update --patch
meteor install --save @babel/runtime
meteor install --save bcrypt

So the recipe actually worked for you thereafter?

No such luck... But it does not throw that error.
Now there are no errors; I can connect a browser to it and see a correctly titled window with the correct background, but no data on the screen.
Still troubleshooting.

The Meteor recipe won't work for me either on macOS. I only get the connection refused error message. If I start npm run debug on the command line, everything works fine.

I've had exact same problem all week and I've been trying hard to get it going. I finally succeeded with server side debugging, havn't quite worked out server/client at same time, but Im happy.
Try this

launch.json:

    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "attach",
            "name": "server",
            "restart": true,
            "port": 9229,
        },
    ],
}

run meteor in its own terminal
meteor run --inspect

Start up vscode debugger.
Take note of debugger attached output in meteors terminal

Open up browser localhost:3000 and go for it!

For client side as well:
5. Chrome devtools > Sources: Add your work directory, then add client breakpoints there.
Has worked flawlessly for me so far.


Commits messages

Generated CHANGELOG.md, but it shows only Merged pull requests, shall I get git commits message along with Merged pull requests. Generated  CHANGELOG.md content below :
Change Log
Unreleased
Full Changelog
Merged pull requests:

Add Staticman data #10 (staticmanapp)
Add Staticman data #9 (staticmanapp)
Add Staticman data #7 (staticmanapp)
Add Staticman data #5 (staticmanapp)

* This Change Log was automatically generated by github_changelog_generator

I would like to get commit messages as well, at least as an option. We work using master as a dev branch, and not every thing that goes in has an issue associated with it. If it does then put it under issues, otherwise having a section for general commits would be useful (excluding merge commits etc. of course).

I really need to be able to display commits instead/alongside issues as well


rsync complains about error in bash-completion

Category

[ ] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[x] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

This is fzf 0.17.4, because I haven't managed to persuade openSUSE build system to build with more recent Go, but I don't think file shell/completion.bash is the same.
However, whenever I run rsync, I get this error:
~$ rsync -avz --delete home:Knihy/ /home/matej/Knihy/
/usr/share/bash-completion/completions/fzf: line 33: bind: warning: line editing not enabled
receiving incremental file list

sent 49 bytes  received 25,553 bytes  17,068.00 bytes/sec
total size is 350,759,695  speedup is 13,700.48
~$

Actually, looking at this, I am not sure whether the error is on my side or on the other side of rsync.

In the latest version, we have an extra guard statement (see https://github.com/junegunn/fzf/commit/8cf45a519788c42ae4312fe9295e3cd9b988f372) so that the script is not loaded in a non-interactive session.
Note that the change is only needed if you don't use the install script to generate ~/.fzf.bash which already handles the case: https://github.com/junegunn/fzf/blob/ff951341c993ed84ad65344e496e122ee3dddf67/install#L261

prefs.js.source.txt
prefs.js.target.txt


Dev Tools launch to <IP_ADDRESS> instead of localhost

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
yes
Environment
Environment:
OS: macOS High Sierra 10.13.3
Node: 8.7.0
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.7.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 2.3 AI-162.4069837
Packages: (wanted => installed)
react: 16.2.0 => 16.2.0
react-native: 0.53.0 => 0.53.0
Steps to Reproduce

Run app on Android.
Turn on Debug mode.
Bundler says "Launching Dev Tools..." and it opens chrome to http://<IP_ADDRESS>:8081/debugger-ui, which hangs because the debugger is on localhost.

Expected Behavior
I expect the debugger to open Chrome to localhost:8081/debugger-ui as it always has before I upgraded to version 0.53.0.
Actual Behavior
As mentioned, it opens to http://<IP_ADDRESS>:8081/debugger-ui, which is inoperable. Nothing ever loads. The Devtools middleware has the wrong host for some reason.
Reproducible Demo
You can literally react-native init a new app right now, and it will do this. Here's a package json of an app I just generated that has this issue
{
  "name": "testingtesting",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "react": "16.2.0",
    "react-native": "0.53.0"
  },
  "devDependencies": {
    "babel-jest": "22.2.2",
    "babel-preset-react-native": "4.0.0",
    "jest": "22.3.0",
    "react-test-renderer": "16.2.0"
  },
  "jest": {
    "preset": "react-native"
  }
}

It appears the app bundle is also being loaded from <IP_ADDRESS>, but the debugger is not functioning at this host, which I'm guessing means that even if I navigate to a "working" debugger @ localhost, it's still not going to work. Credit to #17910 for first assuring me I was not crazy and this was a real issue.
Edit: Complete shot in the dark here, but could it have something to do with fa574c6 ? (happy to pr this with some direction, although I know at least part of the issue is in a separate file where it is also incorrect about the host when launching chrome).

(The bot might mark this as no-template, but it's because this issue is missing the first line from the template. Disregard)

@hramos (edited to add it in)

Reopened, sorry about that. The bot is pretty naive when it comes to checking the template is followed, but it manages to catch the issues we really want to close immediately (where the whole template is deleted).

I'm getting this too on Windows. Really annoying.
Environment:
OS: Windows 10
Node: 6.11.1
Yarn: 1.3.2
npm: 5.6.0
Android Studio: 2.3 AI-162.4069837

I'm getting this issue too on my new react-native project, although even manually going to http://localhost:8081/debugger-ui/ doesn't work.
I could swear this was working fine several weeks ago on a different react-native project.
Environment:
OS: Windows 10
Node: v9.4.0
npm: 5.6.0
Android Studio: 3.0.1
react-native-cli: 2.0.1
react-native: 0.53.0

I can confirm that on my older react-native version 0.52.2 project work perfectly fine in terms of remote debugging.
The new 0.53.0 might be the cause of this issue.

Go to http://localhost:8081/debugger-ui/ . Then stop remote js debugging and run your react native app again. Finally debug js remotely. Has worked for me.

@perseyMudzinga Ok, that's good to know for when I need it. I was worried it wouldn't connect at all anymore.
Still, I'm wondering why the function that launches chrome in the middleware is wrong about the host (it thinks the host is, I believe, the location where the Android emulator runs, rather than localhost).

The original post refers to https://github.com/facebook/react-native/commit/fa574c60920588e29d7b642e547e240ac8655e66 as a possible cause. Commenting here to point to https://github.com/facebook/react-native/pull/15547 which is the PR that introduced that commit.

Running into this as well.  I only started running into this on 0.53.x.  Didn't have this problem on 0.50.x.  I grepped through node_modules/react-native and notice a few places where <IP_ADDRESS> is hard coded.  I'm not using remote js debugging.... I'm just trying to run from Android Studio.

I also have this issue on 0.53.x, but not any version prior.

@perseyMudzinga Your solution works for me. I've checked react-native modules and @rgoldiez is correct, AndroidIfoHelpers.java has the hard coded <IP_ADDRESS> for emulator localhost:

It would really help development to change the hardcoded 10.0.x.x IPs to localhost.  Any chance this fix could be released as 0.53.4 ?  If not, when is 0.54 going to be final, and will this fix be incorporated?

How is this such BASIC problem not yet fixed?

I also have this problem and the workaround from @perseyMudzinga worked for me.  Thanks!

"How is this such BASIC problem not yet fixed?"
Apparently debugging isn't a priority for FB 😜

For us with JS Deltas disabled and manually opening a tab to localhost:8081 and refreshing again the debugger works. It seems like there's a bug where the emulator is opening a chrome tab against EMULATOR_LOCALHOST but should be opening it against DEVICE_LOCALHOST?

Confirm the same issue on Ubuntu. Hope this will be fixed soon. It's worse if someone is using standalone react-native debugger. I'm investigating how to change the URL, though.

The <IP_ADDRESS> is an Android Emulator setup (which internally points to localhost on your computer), as localhost on the the emulator would point to itself as a device.
Need to be a concession made to always open debugger against DEVICE_LOCALHOST as @esprehn mentioned just before.

Same issue here. changing localhost:8081 worked for me. Thanks.

Workaround given by perseyMudzinga gives me the following, unfortunately.

I did some digging and it looks like this may be the responsible commit, but the logic around host / port names in react native for serving bundles is a bit confusing so I'm not sure.

What is the solution? @facebook-github-bot. Are we downgrade to lowest version?

I am getting the same issue for react-native 0.54.4 version. Can anyone solve the problem? I follow the above all option to fix the problem but those all are not worked for me.

workaround from  @perseyMudzinga  opens the debugger but I am unable to access any of my sources file. :(

I have changed the default browser to Firefox and also followed the process @perseyMudzinga mentioned. I am using ubuntu's chrome. Now the issue is fixed after doing this. But each time I have to first open firefox with localhost URL. So it's annoying.

I am new to react native. I have the same problem on Ubuntu 16.04
react-native-cli: 2.0.1
react-native: 0.55.2
I have tried to change the value in AndroidInfoHelpers.java but it I don't know how to rebuild/recompile things so that it gets fixed in my project.
Please let me know the steps to rebuild after change <IP_ADDRESS> to localhost.
Thank you

Change your default browser to firefox. Windows and ubuntu have few problem in this version.

@Msspl-PrashenjeetRoy How is that done? Thanks

@mehdiesteghamat Which OS you are using right now? I have fixed it with ubuntu. And I am working in Mac, there is no issue with mac.
1- After changing the default browser to firefox, you have to follow second step:
2- Follow @perseyMudzinga comment
Go to http://localhost:8081/debugger-ui/ . Then stop remote js debugging and run your react native app again. Finally debug js remotely. Has worked for me.

I could do it with chrome... I just had to reinstall chrome. (Ubuntu 16.04)
The trick was as below after I reinstalled:
[https://stackoverflow.com/questions/40898934/unable-to-connect-with-remote-debugger?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa]("To solve the issue: Before enabling remote debugging on your emulator, open http://localhost:8081/debugger-ui in chrome. Then enable remote debugging and go back to the chrome page where you should see your console logs.")

It looks to me that it's this commit that's causing the local dev tools to launch against <IP_ADDRESS> (getting request host from the app inside emulator) instead of localhost.  Maybe a combination of that and the other change?

Try adding localhost:8081 to Debug server host and port settings.
Ctrl+m -> Dev settings -> Debugging.  Add localhost:8081

@vyshakh it's not working for my system, and it needs to do every time after building in the emulator. It's very difficult way.

Looks like this is causing the issue. @tseever @MSSPL-PiyaleeMaiti  https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/modules/systeminfo/AndroidInfoHelpers.java

@vyshakh I know about this file but if I changed host id for emulator it's not working. I hope to react native developer should fix that issue with new version release. It's a big issue for debugging when a developer working with react native.

me too,I can't debugging

I solve the issue by:

Press Cmd + M on emulator screen
Go to Dev settings > Debug server host & port for device
Set localhost:8081
Rerun the android app: react-native run-android

Debugger is connected now! :)

Have tried all options in this thread including going directly to localhost:8081. The CORS issue is fixed when doing that, however all requests are routed directly to localhost rather than localhost:8081 which of course fails.
Is there a setting I'm missing somewhere, or is this currently not working?

And the CORS issue can't be fixed when/if I need to use my computer's IP on network, for testing android on device untethered.

This issue is confirmed in windows 7 32 bits :P, also in Linux Mint 64 18.3
react-native-cli: 2.0.1
react-native: 0.55.3

@kamranyounis12 , workaround from @perseyMudzinga opens the debugger , To access source code we need to setup
found in https://stackoverflow.com/questions/49340074/chrome-debug-tools-for-react-native-mutiple-issues/49676564
ctrk+m on your emulator.
click on Dev Settings.
Disable Use JS Delta
restart the react native server.
then Go to http://localhost:8081/debugger-ui/ . Then stop remote js debugging and run your react native app again. Finally debug js remotely.
This worked for me

Is there any traction on this? The debugger has been broken for 5 months now.

@esprehn I don't know about broken, the debugger still works. The workarounds are more of an inconvenience. As @perseyMudzinga and @timscott have mentioned, for now do either of the following:

Replace <IP_ADDRESS> with locahost in the address bar, and re-run your app
From the emulator, CMD+m > Debug server host & port for device, set to locahost:8081, and re-run your app (need to do this each time the app is installed)

Debugging should still work after doing one of these.

Re-installing Android Emulator gives me solution.

In addition to @davebro comment I would like to add that you need to unplug ANY OTHER physical devices from computer.

This issue definetely break developer experience of react-native. Fresh new developer hit a lot of issues, and this is one of them.

Ya this is stupidly tedious even for those like me who does know about this issue, and every time having to change chrome's debugger url from <IP_ADDRESS> to localhost.
And this is only on Android. On iOS, I changed my AppDelegate.m with this line:
jsCodeLocation = [NSURL URLWithString:@"http://<IP_ADDRESS>:8081/index.bundle?platform=ios&dev=true"];

With <IP_ADDRESS> my mac's LAN ip. It can be localhost or any ip I want it to be. Is there no similar config option for Android, and shouldn't there be?

For android emulator, CMD+m > Debug server host & port for device and changing it to localhost does not change the chrome devtools url launch behavior for me. It still always open with <IP_ADDRESS>.

For android emulator, CMD+m > Debug server host & port for device and changing it to localhost does not change the chrome devtools url launch behavior for me. It still always open with <IP_ADDRESS>.

I also face the same problem.

How such basic things like this can be a problem for RN developers? That's just sad.

Nowadays, I don't see there's much case left for <IP_ADDRESS>. I've went from Mac to Windows dev, and for both iOS and Android (emulators). localhost works in all cases, <IP_ADDRESS> doesn't. And for Android, I've used both genymotion and standard android emulator.

Have RN read from an env variable like RN_DEBUGGER_URL, instead of using that garbage hard-coded string that only works for 50% of people.
Problem solved.  Thank me later.

And/or config variable in package.json

I have zero use case for <IP_ADDRESS>.

There are still problems.

I solved the issue by:

Press Cmd + M on emulator screen
Go to Dev settings > Debug server host & port for device
Set localhost:8081
Rerun the android app: react-native run-android

Debugger is connected now!

Solution works fine for me, however had to change from localhost to my machine IP address. e.g. <IP_ADDRESS>:8081

@Ndukuzempi I try this slution before it's not working.
Admin should find permanent solution for this, otherwise it's so difficult for developer to debug their project.

I got this to work by following a combination of above comments. Maybe this will help someone.
react-native 0.57.4
react-native-cli 2.0.1

Ensure adb is in PATH
Start Android emulator
Run react-native run-android
Open http://localhost:8081/debugger-ui/
cmd + m on emulator screen
Select "Enable Remote JS Debugging"
Select "Enable Hot Reloading"
Select "Reload"

Soon one year later and I'm still having this issue on Windows

I can confirm no single solution works here.
I keep getting banned for saying it, but it's worth saying. React Native is being Industrially Sabotaged. Anyone that's been in software this long knows these kinds of bugs are virtually impossible to attain. The individual library maintainers are being secretly paid to exploit existing bugs in their libraries. But they aren't covering their tracks very well. Lots of recent version changes and new bugs!

I honestly can't tell if the comment above is just trolling.
But ofc I've screenshotted it, deleted it and reported this person as it ofc violates all the kinds of CoC I can think of.
Let me be extremely clear: as someone who doesn't work for Facebook and help with React Native without getting any kind of payment, seeing comments like those is embarassing. The community we have been trying to cultivate can and should be better than that.

deleted?

you deleted my post suggesting this library is being censored? Are you serious kelset? I'm linking everyone to this thread.

Thank you for your reply Victor, I don't have a copy of it. Only Kelset does.
Here's what I suggested, which will apparently get me banned?!?#
Facebook might be depreciating these libraries on purpose by encouraging it's remaining supporters to

Not fix long term bugs
Cause unnecessary library conflicts
Hardcode values to favor one OS over another

I could go on and on. I believe I have the right to suggest this without being banned, right?

@clevertree I think it might be perfectly possible. Either way it is very sad that a library used and starred by so many have such a poor environment for the developer. Turns out that for me it seems so much easier to just develop for Android using the available tools and go native whenever it is needed. Unfortunately, at the end of the day, going native is the best way of developing reliable applications.

Your conspiracy theories make 0 sense. You seem to know nothing about how OSS works nor how Facebook's business works. Either contribute here or get out, simple.

@fungilation you're entitled to your opinion. Do you agree that I am entitled to mine? That @kelset should not have deleted my comment?
This library is broken and getting worse by the day. If you have nothing to say about it, please keep your opinions of me to yourself.

Thanks everyone for participating in this discussion. As @TheSavior pointed out, it seems depending on environment setup, the debugger should be using different addresses. However in this issue we have not made any progress in trying to understand what the actual root cause for the difference is, which makes it hard to figure out the right fix.
The good news is though that we have just extracted the cli/debugger related code into a new repository that is entirely managed by the open source community since we are not using this code at Facebook. I'll close this issue here and will let somebody from this thread create a new issue in the react-native-cli repo. I encourage you to try to understand the cause for the differences, and then submitting a PR to that repo with a fix that will work for all users, rather than one subset or the other.
The discussion here has been quite heated and unproductive in finding a resolution so I'll lock this issue.


docs: Add ApolloDriver to introduction's code example

Fixes https://github.com/TriPSs/nestjs-query/issues/77

Thanks for the PR!


Karpenter not creating nodes

[X] ✋ I have searched the open/closed issues and my issue is not listed.
Please describe your question here
When using Karpenter, the nodes are not being created and the logs says this:
"You are not authorized to perform this operation. Encoded authorization failure message: HZ_v......"
Thank you in advance!
karpenter = {
    repository_username = data.aws_ecrpublic_authorization_token.token.user_name
    repository_password = data.aws_ecrpublic_authorization_token.token.password
}
karpenter_instance_profile = {
    name = module.karpenter.instance_profile_name
    iam_role_name = module.eks.fargate_profiles["karpenter"].iam_role_name
}

karpenter_enable_spot_termination = true

I am using this configuration.
Provide a link to the example/module related to the question
Additional context

hi @BrandonEscamilla - could you please provide a full reproduction that we can deploy and demonstrate this error plus the steps you took to re-create the error?

closing for now - please feel free to respond with additional details and we can take a look


Not working with Credentials provider

Environment
Nuxi 3.0.0-rc.11
Nuxt 3.0.0-rc.11 with Nitro 0.5.4
@sidebase/nuxt-auth 0.0.1-beta.3
Reproduction
No response
Describe the bug
Thank you for this awesome module, it is the missing piece for the Nuxt universe.
I have try to setup nuxt-auth with the credentials Provider which is the most common type when using a decoupled backend.
this is my auth config in nuxt.config.ts copied from official docs in NextAuth
NUXT_URL =  http://localhost/api/auth/
  auth: {
    nextAuth: {
      url: process.env.NUXT_URL,
      options: {
        secret: process.env.NUXT_SECRET,
        providers: [
          CredentialsProvider({
            // The name to display on the sign in form (e.g. 'Sign in with...')
            name: 'Credentials',
            // The credentials is used to generate a suitable form on the sign in page.
            // You can specify whatever fields you are expecting to be submitted.
            // e.g. domain, username, password, 2FA token, etc.
            // You can pass any HTML attribute to the <input> tag through the object.
            credentials: {
              username: { label: 'Username', type: 'text', placeholder: 'jsmith' },
              password: { label: 'Password', type: 'password' },
            },
            async authorize(credentials, req) {
              // You need to provide your own logic here that takes the credentials
              // submitted and returns either a object representing a user or value
              // that is false/null if the credentials are invalid.
              // e.g. return { id: 1, name: 'J Smith', email<EMAIL_ADDRESS>}
              // You can also use the `req` object to obtain additional parameters
              // (i.e., the request IP address)
              // eslint-disable-next-line no-console
              console.log(credentials)
              const user = { id: '1', name: 'J Smith', email<EMAIL_ADDRESS>}

              if (user) {
                // Any object returned will be saved in `user` property of the JWT
                return user
              }
              else {
                // If you return null then an error will be displayed advising the user to check their details.
                return null

                // You can also Reject this callback with an Error thus the user will be sent to the error page with the error message as a query parameter
              }
            },
          }),
        ],
      },
    },

Login form its showing but not matter what is the input for username and password it always show the error: "Sign in failed. Check the details you provided are correct."
the authorize function its never reach when submitting the form.
Is there anything else I am missing in order to make it work
Additional context
No response
Logs
No response

Thanks for opening the issue!
I'm on vacay, but already know what's going on and will comment that for the benefit @valiafetisov and @zoey-kaiser who may further this issue until I'm back:

In order to setup the providers in the backend, we serialize each provider and then reconstruct it in the backend:

serialization: https://github.com/sidebase/nuxt-auth/blob/a1269537c721aa60aebe5e452fe3044c55fc1b6d/src/module.ts#L67-L96
deserialization in runtime: https://github.com/sidebase/nuxt-auth/blob/a1269537c721aa60aebe5e452fe3044c55fc1b6d/src/runtime/server/api/auth.ts#L30-L35

The problem is that authorize does not de-/serialize correctly as it's a function

this is a known limitation / feature, as described by @danielroe:

https://github.com/nuxt/framework/issues/8419#issuecomment-1289287990
https://github.com/sidebase/nuxt-auth/issues/1#issuecomment-1293378274

we need to find a way to pass authorize to the runtime (this would also enable a lot of other stuff). Options I already know of:

some sort of de-/serialize for non-0natively serializable things
change the module so that the user creates their own endpoint files in their codebase, where their config is parsed at runtime, thus removing this barrier (e.g., user creates their own /server/api/auth.ts)

It rains a lot here atm, so I was able to open: #10 that would resolve this and basically bring us onto feature parity with next-auth.js a lot quicker!

@jorgv  checkout 0.0.1-beta.4 -> credentials flow should work. Please give feedback here (:
@zoey-kaiser please update the nuxt auth demo!

Hey @jorgv we got the credentials flow working with our nuxt auth demo app, check it out! Link is on main page of repo.
Please let me know if it works for you now, so thst we can close this issue (:

Hey guys I will test them and get back to you

@BracketJohn works perfectly! Thanks so much. I will leave my [...].ts in case someone else needs it for Credentials provider:
import CredentialsProvider from 'next-auth/providers/credentials'
import { NuxtAuthHandler } from '#auth'

export default NuxtAuthHandler({
  providers: [
    // @ts-expect-error Import is exported on .default during SSR, so we need to call it this way. May be fixed via Vite at some point
    CredentialsProvider.default({
      name: 'Credentials',

      credentials: {
        username: { label: 'Username', type: 'text', placeholder: 'jsmith' },
        password: { label: 'Password', type: 'password' },
      },
      async authorize(credentials, req) {

        // const user = { id: '1', name: 'J Smith', email<EMAIL_ADDRESS>}
        const token = Buffer.from(`${credentials.username}:${credentials.password}`).toString('base64')
        const res = await fetch('http://localhost/login', {
          method: 'post',
          headers: {
            'Content-Type': 'application/json',
            'Authorization': `Basic ${token}`,
          },
        })
        const user = await res.json()
        // If no error and we have user data, return it
        if (res.ok && user) {
          return user
        }
        else {
          // If you return null then an error will be displayed advising the user to check their details.
          return null
          // You can also Reject this callback with an Error thus the user will be sent to the error page with the error message as a query parameter
        }
      },
    }),
  ],
})

Superb! Glad that it works and sure thing!

For future readers: In the above code sample by @jorgv the credentials are checked against a locally available service that has a /login endpoint. In your code you could replace the fetch call with a database query to get and compare known usernames and passwords, with opening a file that contains known usernames and passwords, with looking into an env variable that contains known username and password, ...
The above are jist examples to show that a lot is possible. In practice implementing a login + stpring credentials correctly often requires a lot of care, but it is also use-case specific how mich care is sctually needed. So stay safe out there!

@BracketJohn works perfectly! Thanks so much. I will leave my [...].ts in case someone else needs it for Credentials provider:
import CredentialsProvider from 'next-auth/providers/credentials'
import { NuxtAuthHandler } from '#auth'

export default NuxtAuthHandler({
  providers: [
    // @ts-expect-error Import is exported on .default during SSR, so we need to call it this way. May be fixed via Vite at some point
    CredentialsProvider.default({
      name: 'Credentials',

      credentials: {
        username: { label: 'Username', type: 'text', placeholder: 'jsmith' },
        password: { label: 'Password', type: 'password' },
      },
      async authorize(credentials, req) {

        // const user = { id: '1', name: 'J Smith', email<EMAIL_ADDRESS>}
        const token = Buffer.from(`${credentials.username}:${credentials.password}`).toString('base64')
        const res = await fetch('http://localhost/login', {
          method: 'post',
          headers: {
            'Content-Type': 'application/json',
            'Authorization': `Basic ${token}`,
          },
        })
        const user = await res.json()
        // If no error and we have user data, return it
        if (res.ok && user) {
          return user
        }
        else {
          // If you return null then an error will be displayed advising the user to check their details.
          return null
          // You can also Reject this callback with an Error thus the user will be sent to the error page with the error message as a query parameter
        }
      },
    }),
  ],
})

Impressive!


Add date filter with date search

Need to add filter for user to have opportunity to see data with their own date search

Any progress on this?

Still figuring out in this one. For filter any data using date for now only available with this feature : https://coroo.github.io/nova-chartjs/#/?id=adding-condition :pray:

Hi @orangelabs-dev , sorry for take so long for this feature. For now, we use button filter just like metrics-range in laravel nova. For using this feature, you need to use latest version (>v.0.2.1), also please see documentation in here: https://coroo.github.io/nova-chartjs/#/?id=metrics-filter


Open source storybook-addon-amp

Request to spin off the storybook AMP addon (currently living under build-system/tasks/storybook/amp-env) as a standalone repository (ampproject/storybook-addon-amp) and publish it on npm as storybook-addon-amp.
This allows:

AMP can now simply import { withAmp } from "storybook-addon-amp" instead of using a long relative path to the addon
Separate storybook dependencies from the addon's specific dependencies inside the amphtml repository
Provide outside projects with a way to render AMP components inside storybook
Provide a natural place for documentation of the usage of the addon

@ampproject/tsc @ampproject/wg-ui-and-a11y

Good idea

Can someone guide us though the aproval process and creating a repository under ampproject/

@mrjoro

So, far this is still the google launch process for OSS projects (pending switch over to the foundation)

Since the switch to the foundation is over, let's approve this here.
Approved from me. Still need 2 more approvers from @ampproject/wg-approvers

LGTM2

LGTM3. Glad to see this grow into a standalone piece of infrastructure.

Great!  I've created https://github.com/ampproject/storybook-addon-amp and made @wassgha , @dvoytenko and @kristoferbaxter admins. :)

Closing since this has been resolved.


Add explanations and restructure into themes

We need more verbal explanations about what each status and command is used for, how you use it, pitfalls, etc. It would also be good to add example messages.
I think the documentation would be easier to read if it was organised into themes, e.g:

Signal programs
Connected equipment
Dynamic traffic control
Monitoring and errors

That would also quickly give readers an impression about what can be achieved with RSMP for traffic signals.
Index of all status, commands, alarms, etc can still be used as well, with links to the relevant sections.

Going to split into smaller tasks


fix(error) Lock newErrorFromWasmer to OS thread

Revamping of https://github.com/wasmerio/wasmer-go/pull/117. See
https://github.com/wasmerio/wasmer-go/issues/96 to get more details.
This patch renames newErrorFromWasmer to _newErrorFromWasmer. It creates a new function named maybeNewErrorFromWasmer which creates a new *Error from the Wasmer API, if and only if the given block returns true (which means that it has failed).
Then the code has been adapted consequently.

bors try


Merge major networking components into dcos-net service

High Level Description
DCOS network consist of erlang applications such as Spartan (DNS dual-dispatcher), Minuteman (Layer 4 load balancer), Navstar (Network Util) and Networking-API (Network Metrics). These applications run independently but have a dependency on Lashup (distributed key-value store). They use Lashup as a distributed key-value store and for failure detection. In theory, each application can run their own Lashup instance however, this is undesirable as separate Lashup instances would consume a lot of system resource. An alternate approach could be to run these application together in a single erlang VM so that they all could benefit from single lashup instance.
Related Issues

DCOS_OSS-1241 Merge Spartan and Navstar into dcos-net

Checklist for all PR's

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[x] Test Results: [link to CI job test results for component]
[x] Code Coverage (if available): [link to code coverage report]

https://github.com/mesosphere/dcos-net
https://github.com/mesosphere/dcos-net/pull/1
https://github.com/mesosphere/dcos-enterprise/pull/1113

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot label [Ready For Review]

This looks quite good already! Let's have more reviews, please.
I refrain from pushing this forward myself today because it's such a big change. Creating master train 224 right now w/o this.

@urbanserj do we need to re-base the enterprise build? We should try to get this committed at the earliest.

One test is failing here. I'm working on it.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

It seems like disabled -> permissive upgrade test is broken: https://jira.mesosphere.com/browse/DCOS_OSS-1721.

@mesosphere-mergebot label [Ready For Review]

@lingmann can you take another look at this.
@jgehrcke @gpaul a look at the bootstrap changes would be helpful as well.

@lingmann once we get the approvals on the enterprise PR, can we try putting this on its own train? Would like to see this move forward at the earliest.

Ship-it was applied prematurely. See DCOS-19252.

No bump-ee was performed after adding the last commits here. Doing that now. Also rebasing one more time.

@mesosphere-mergebot bump-ee

@gpaul can you please give this another sanity check?

Has anything been done regarding the observed issue where dcos-net-watchdog was killing bootstrap? Having the watchdog kill arbitrary ExecStartPre= commands which then roll forward to the next ExecStartPre= / ExecStart= clearly leads to undefined behaviour.
If our recent experiments are correct, we will have a watchdog service running every 60s which will "kill -9 whatever ExecStartPre= is currently being executed by the dcos-net unit and proceed to the next ExecStartPre= / ExecStart=."
The current workaround of lazy-initializing the ZK client just hides the symptom. If dcos_net ever needs to do something with ZK (ie., the dcos_net bootstrapper is no longer "noop") the symptom will resurface and once more take several days to debug.

Hence, my question regarding --kill-who=main

Hi @gpaul,
SIGTERM signal caused that issue. systemctl kill kills everything properly if it uses SIGKILL, so I added -s 9 here as a workaround. Thank you for mentioning --kill-who=main argument. I still need some time to check how it works. I'd like to be sure that it will kill main process and all child/forked processes in dcos-net cgroup as well.

@gpaul Exactly. I tested -s 9 without the lazy-loading patch. As it was mentioned here I didn't revert my bootstrap patch just because it speeds up agent node initialization.

@lingmann can we build a separate train for this branch and move forward?

@lingmann  / @jgehrcke  - Just a note. This PR and the corresponding EE PR needs to land in a separate train. Please do not include this as part of another integration train. /cc: @mellenburg

Making a note here.  I triggered the train tests in this PR itself and I will work on taking this over the finish line.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot merge-it


[Bug] Could not resolve dependency:

Version
1.2.0
Reproduction link
http://na.na
Operating System
linux mint
Device
laptop
Browser & Version
na
Steps to reproduce
git clone from repo
npm install
What is expected?
success installation
What is actually happening?
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-datetime
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Solution
added --force
Additional comments

Hi
Thanks for using our products, we just solve this issue its a problem with NodeJS version you have to download the NodeJS LTS version and it will fix the problem.
All the best
Sajad

Encountered the same issue.
Had some headache until finding this issue.
Sadly the --force did not work for me.
I reinstalled the LTS version from official source and looks good now.
Thanks @sajadevo for solution.


replace builder structs with derive_builder

derive_builder

I have never used derive_builder, but it seems convenient at a glance.


refactor: add tailcall-core workspace

add core project
add core files
update dependencies

/tip @mehulmathur16 50$
Thanks @mehulmathur16!

There is too much effort required in this. Closing for now.


[Tree] Allow tree root to be a separate entity

This would be a nice feature if we could define TreeRoot as for instance, ManyToOne relationship. Consider such a use case:
Entity\Navigation
Entity\Page (nested set).
Now each Entity\Navigation has it's own nested set of Entity\Page.
Currently two solutions are possible: fake root node for each Entity\Navigation or InheritanceMapping, eliminating Entity\Navigation.

Hi all, Unable to get oneToMany, ManyToOne and ManyToMany associated entities on a Tree entity. How to do this? Thanks

@etoileweb this has nothing to do with it, relations should be working as expected

implemented in master


fix issue #2172

Codecov Report
Base: 76.49% // Head: 76.49% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (f988094) compared to base (127e8af).
Patch coverage: 26.66% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2173      +/-   ##
==========================================
- Coverage   76.49%   76.49%   -0.01%
==========================================
  Files         580      578       -2
  Lines       48087    47979     -108
==========================================
- Hits        36785    36702      -83
+ Misses       9291     9265      -26
- Partials     2011     2012       +1

Flag
Coverage Δ

go-1.15-386
?

go-1.15-amd64
?

go-1.16-386
?

go-1.16-amd64
?

go-1.17-386
?

go-1.17-amd64
76.49% <26.66%> (-0.02%)
:arrow_down:

go-1.18-386
?

go-1.18-amd64
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

encoding/gjson/gjson.go
83.22% <0.00%> (-0.79%)
:arrow_down:

encoding/gjson/gjson_implements.go
80.00% <0.00%> (-20.00%)
:arrow_down:

net/ghttp/ghttp_server_graceful.go
60.00% <0.00%> (ø)

encoding/gjson/gjson_api.go
94.59% <100.00%> (+0.15%)
:arrow_up:

encoding/gjson/gjson_api_new_load.go
96.68% <100.00%> (ø)

os/gcron/gcron_schedule_fix.go
87.50% <0.00%> (-12.50%)
:arrow_down:

os/gspath/gspath_cache.go
84.21% <0.00%> (-10.53%)
:arrow_down:

os/gfsnotify/gfsnotify_watcher_loop.go
75.63% <0.00%> (-9.25%)
:arrow_down:

net/gtcp/gtcp_pool.go
68.18% <0.00%> (-6.82%)
:arrow_down:

os/gfsnotify/gfsnotify_filefunc.go
70.12% <0.00%> (-3.90%)
:arrow_down:

... and 6 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Final Touch: CSS

For this PR, I:

Modified styles to make it look great in both mobile and desktop

Thank you for the approval!


Apply highlight tags on numbers (not only strings)

Check with our PR @gmourier, this addition can be implemented by the community 🎉

Currently, the search engine does not highlight the number in _formatted because it's impossible to add  tag around a number (not a string) in JSON.
What we expect?
Return the raw document (so the number) but the "transformed" document (so with the number surrounded of the tag in a string) in _formatted.
Example:
{
    "hits": [
        {
            "book_id": 456,
            "title": "Le Petit Prince",
            "_formatted": {
                "book_id": "456",
                "title": "Le Petit Prince"
            }
        }
    ],
    "offset": 0,
    "limit": 20,
    "processingTimeMs": 0,
    "query": "4"
}

@curquiza I'll do, please assign it to me.

@MarinPostma or @irevoire can maybe give you some clarification about the issue 🙂

Hello @spinales, I think all your work will be in the meilisearch-lib/src/index/search.rs file.
You should notice that the big perform_search function is executed for every search.
And that at the end of a search it's calling the format_fields on every returned document.
And in the end, it's in the format_value that decide how to highlight each fields.
And I'll let you guess what you need to do here :+1:
I think this should suffice but I may be wrong, do not hesitate to ask more questions if it doesn't work :smile:

@irevoire  Hi, how can test the changes i did?
i did a change, i want to do test, how can generate JSON file with field _formatted, how showed the first comment on this issue?

Hello @spinales, I will remove the assignation since we did not get any PR from you, we can understand this is not an easy PR and you may not have the time to do it 🙂
In general, and from now, we prefer not assigning people to our issues because sometimes people ask to be assigned and never come back, which discourages the other volunteers contributors to open a PR to fix this issue.
We will accept and merge the first PR that fixes correctly and well implements the issue following our contributing guidelines.
thanks again for your involvement and feel free to still open a PR if you have the time 🙂

Will this also affect queries using the matches query parameter, @curquiza?

Nope, matches still do not work with numerical values.
But maybe it could now work... I have to check with the dev team if it's doable. In any case, it will be another issue if matches finally works with numerical value, so you will know it 🙂

It changes the json data type of _formatted.id from Number to String? Is this going to be a problem? @curquiza
Before (on v0.23.1):
{
            "id": 4,
            "title": 1,
            "_formatted": {
                "id": 4, <-- Number
                "title": 1
            }
}

After:
{
            "id": 4,
            "title": 1,
            "_formatted": {
                "id": "4", <-- String
                "title": 1
            }
}


add_to_index() one/few documents throws error

Hello!
Great work on the tool so far! Really loving it! I have a question, I apologize if it has already been answered. I am trying to add a single document to an index using the add_to_index() function. However, I get the following error:
RuntimeError: Error in void faiss::Clustering::train_encoded(faiss::idx_t, const uint8_t*, const faiss::Index*, faiss::Index&, const float*) at /project/faiss/faiss/Clustering.cpp:275: Error: 'nx >= k' failed: Number of training points (11) should be at least as large as number of clusters (32)

I looked more into the source code and found that:
(colbert.py: add_to_index())
 current_len = len(searcher.collection)
        new_doc_len = len(new_documents)
        new_documents_with_ids = [
            {"content": doc, "document_id": new_pid_docid_map[pid]}
            for pid, doc in enumerate(new_documents)
            if new_pid_docid_map[pid] not in self.pid_docid_map
        ]

        if new_docid_metadata_map is not None:
            self.docid_metadata_map = self.docid_metadata_map or {}
            self.docid_metadata_map.update(new_docid_metadata_map)

        if current_len + new_doc_len < 5000 or new_doc_len > current_len * 0.05:
            self.index(
                [doc["content"] for doc in new_documents_with_ids],
                {
                    pid: doc["document_id"]
                    for pid, doc in enumerate(new_documents_with_ids)
                },
                docid_metadata_map=self.docid_metadata_map,
                index_name=self.index_name,
                max_document_length=self.config.doc_maxlen,
                overwrite="force_silent_overwrite",
            )

If current_length of the collection + the length of the new collection, it is re-indexing the documents, which might be more efficient  than IndexUpdater, but in the re-indexing process, I suspect that only the new documents are being indexed, in this case 1 and so it is throwing the following error. I could be wrong, can you confirm this?
Thank you!

Good catch! It seems like that's indeed what's happening. This got introduced sneakily because the CRUD aspect hasn't gotten a lot of love yet. Will resolve in a PR soon, thank you!

cc @anirudhdharmarajan I'll try to attend to this, but if you'd like to, feel free! (It's about updating the CRUD support to make sure it actually loads up all the existing metadata/pid/etc... and merges the existing collection with the new one before regenerating)

@bclavie I can take this on, I'll have a PR open either today or tomorrow!

Thank you for the excellent works. What's the progress about this issue?

Thanks @anirudhdharmarajan! The PR was published as part a post release and now properly as a main release item with 0.0.8.


Deliver CORS response headers on error responses raised by exceptions

The CORS headers such as Access-Control-Allow-Origin are added by an after_filter. This works for successful responses, but can't intercept responses where an exception was raised and then rescued with rescue_from to render an error response.
This can be a problem for clients making CORS requests; they can get responses to successful calls, but errors can't be handled because the browser blocks access to those responses due to the missing CORS headers.
Here, we change the after_filter to an around_filter which adds the CORS headers to the response before passing on the exception.
@steved @grosser

Thanks!

Released as 2.1.0.


merge Develop to master

Update Webpack version

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:white_check_mark: All tests successful. No failed tests found.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


[frontend][backend]Admin profile

http://localhost:5173/admin

who is ben

 who is ben

approve by @NOOBDY

這邊的user權限 我想改成1,2,3去設定權限 這樣不會有身份重複問題

 who is ben

approve by @NOOBDY

fix

i think this may be a problem

 i think this may be a problem

fix


iTerm2 and colordiff

I've been using the Build <IP_ADDRESS>10908b of iTerm2, and it seems that the colordiff program seems to create output that is not very readable.
I've uploaded some screenshots of what I'm seeing here in the dark theme here:
https://picasaweb.google.com/lh/photo/uODZ_JZ7htaGdQcdRNT0Yg?feat=directlink
And the light theme here:
https://picasaweb.google.com/lh/photo/bV7nr9m5Mm9KO0y_rc_DXQ?feat=directlink
The screenshots show the output of git diff that looks fine, then the output of git diff filtered through colordiff. The reason I use colordiff is that I still have many projects on Subversion. If this is a bug in colordiff, let me know and I can take it up with them. However, when using the stock Dark theme it looks like:
https://picasaweb.google.com/lh/photo/r6s9MRidt0zgPKhrBzQC9A?feat=directlink

Colordiff uses a few bright colors (in particular bright green for added stuff). You can configure it to use colors more compatible with Solarized; for instance see https://github.com/cdlm/infrastructure/blob/master/dotfiles/colordiffrc (put that in your ~/.colordiffrc).

This indeed fixed the issue. Thanks!


Fixing overridden methods not receiving header parameter

Description
Fixing overridden methods(create, retrieve!, delete) not receiving header parameter.
Issues Resolved
#294
Check List

[ ] New functionality includes testing.

[x] All tests pass ($ rake test).

[ ] New functionality has been documented in the README if applicable.

[ ] New functionality has been thoroughly documented in the examples (please include helpful comments).

[ ] New endpoints supported are updated in the endpoints-support.md file.
[x] Changes are documented in the CHANGELOG.

@fgbulsoni , I tried to put some headers with the default value. But I saw that I also needed to replace the creation! method. So I guess this doesn't look cool. What do you think?

I actually have a suggestion.
It would have been more compliant with best practices if instead setting the default header to {}, expecting user to pass something or defaulting it to the default header, and merging with a actual default value, i.e.:
DEFAULT_REQUEST_HEADER = {}
def create(header = DEFAULT_REQUEST_HEADER)
        super(header.merge('Accept-Language' => 'en_US'))

Actually using this actual default value in the default header, and merging it always with the parameter header, i.e.:
DEFAULT_REQUEST_HEADER = { 'Accept-Language' => 'en_US' }
def create(header = {})
        super(header.merge(DEFAULT_REQUEST_HEADER))

This way the default header would make sense to exist, because right now it is a simple constant that actually does nothing.

@tmiotto , Your suggestion helped me and I did it in a way that I think has gotten better.


for secondary camera

to use other web cam you can use this sysntax
cap = cv2.VideoCapture(1)
What type of PR is this? (check all applicable)

[ ] 🚀 Added Name
[x] ✨ Feature
[ ] 🌟 stared the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Add Link of GitHub Profile

if you got some new things than i am happy


Fix code coverage for #515

@markvdw think we can merge this one, no?

Is the base branch correct? It's not currently merging into master? Otherwise, this is a fix we need!

Good point re base branch