Allow multiple magic search to be on the same page

This fix allows multiple magic search inputs to be on the same page by limiting event handlers to the directive's element.

Interesting! I'm sure $element.find() is more efficient due to reduced scope. I like it.


Doxygen Documentation Site

Generate Doxygen documentation site and host it on this repo's GH Pages site.

Create custom Doxyfile
Generate & update GH Pages site with GH Action.

HUMMINGBIRD FCU EXAMPLE ACTION

Done!


Update esm.js

In aea4e3238d the other files were updated but esm.js seems to have been forgotten.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please sign the CLA, otherwise this looks good to me, thanks.

Thanks @WebReflection. Could you maybe release a new npm version, so that the change is also reflected there?

@martinstuecklschwaiger not sure I still have the rights to do so, maybe @bhaggs could help with that?

Just published the update to NPM. Should be all good now.


ENYO-5814: Add eslint-jest-plugin for strict mode to check focused tests

enact framework code should not ship any tests with only and error in our Travis CI. eslint-jest-plugin has a no-focused-tests rule to check these type of tests.
See https://github.com/jest-community/eslint-plugin-jest/blob/master/docs/rules/no-focused-tests.md for more details about the rule.
Note that this is only applied for strict mode. The intention is to check our framework code unit tests for now, but we may adopt jest's recommended rules in the future if we want to.
Enact-DCO-1.0-Signed-off-by: Stephen Choi<EMAIL_ADDRESS>

Can you add references to installing the plugin to the editor plugin sections of the README files and in the templates:
https://github.com/enactjs/templates/tree/master/packages/moonstone/template (maybe others, too?)
https://github.com/enactjs/eslint-config-enact/blob/develop/README.md
https://github.com/enactjs/cli/blob/develop/README.md


'change' event did not fire on radio button change

Once $input.prop('checked') set to true, it never reset to false.
It causes a bug that does not fire 'change' event if you select "B" button and back to "A".
since f9cd88e09f1375702a68f03ef9895053ed14efb3

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: f668990f1f5c5bb763d49ef2e600f1d7f5d8f3b6
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/99263122
(Please note that this is a fully automated comment.)

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: f7f2b557566d93e9730df36cfdf565958ddbaff7
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/99267115
(Please note that this is a fully automated comment.)

It was my failure. my radio buttons did not have correct name attributes.
After I set proper name attr to buttons, .prop('checked') is automatically cleared by browser.


Printing

Hey! When I try and print from a windows machine (for example), cups goes from https://i.imgur.com/8SWX8vV.png, (sending data to printer) straight to completed. It does not say "printing, 29%," it just goes to completed and does not print. Any ideas?

This is a test page. Printed from the site.
https://i.imgur.com/fZmjEMQ.png

I just managed to print my first page over the network. I added it to my phone and spammed print, then it printed. But after this I am not able to print again from the device

Phones work, windows 10 machine doesn't.

Fixed it. Thanks.


Fix error in NewFollower Event

An attempt to index a nil value error was reported on the devforum:
http://devforum.roblox.com/t/the-developer-console-core-script-bug-logs-they-burn/33356
Not sure where this error is coming from but adding this simple check
should resolve it.

This is likely a race condition. Remotes don't send instances, only references. So if a peer sends to another peer a reference to an instance that is parented to nil or no longer exists, it would appear as nil. So more than likely, the player has left the game but because of latency, the client sending a follow request is not yet made aware of that change.
However, there shouldn't be a reason for player1 to be nil, so I assume that check can be removed. If player1 is nil for some reason, then this is a bigger issue with remoteevents that would need to be addressed.

We should address the cause of the problem in the future. This PR will fix the specific symptoms mentioned.


Add iptables interface for implementing Egress

For #1924

/test-all

Codecov Report

Merging #1998 (80bcd88) into main (9b8440d) will decrease coverage by 0.11%.
The diff coverage is 5.66%.

@@            Coverage Diff             @@
##             main    #1998      +/-   ##
==========================================
- Coverage   65.39%   65.27%   -0.12%
==========================================
  Files         197      197
  Lines       17217    17268      +51
==========================================
+ Hits        11259    11272      +13
- Misses       4785     4824      +39
+ Partials     1173     1172       -1

Flag
Coverage Δ

kind-e2e-tests
56.42% <5.66%> (-0.10%)
:arrow_down:

unit-tests
41.82% <0.00%> (-0.04%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/agent/util/iptables/iptables.go
38.88% <0.00%> (-7.34%)
:arrow_down:

pkg/agent/route/route_linux.go
42.69% <9.09%> (-3.62%)
:arrow_down:

...gent/controller/networkpolicy/status_controller.go
72.60% <0.00%> (-2.74%)
:arrow_down:

...ntroller/networkpolicy/networkpolicy_controller.go
70.12% <0.00%> (-1.63%)
:arrow_down:

pkg/agent/openflow/client.go
67.19% <0.00%> (+0.52%)
:arrow_up:

pkg/agent/cniserver/pod_configuration.go
54.68% <0.00%> (+0.78%)
:arrow_up:

pkg/controller/networkpolicy/tier.go
52.50% <0.00%> (+5.00%)
:arrow_up:

pkg/monitor/controller.go
57.57% <0.00%> (+6.06%)
:arrow_up:

pkg/agent/flowexporter/flowrecords/flow_records.go
67.34% <0.00%> (+6.12%)
:arrow_up:

pkg/apiserver/certificate/certificate.go
76.71% <0.00%> (+6.84%)
:arrow_up:

/test-all

/test-windows-conformance


Update sles15sp3o image URL

What does this PR change?
Update sles15sp3o image URL.

backend_modules/libvirt/base/main.tf (sles15sp3o):
Update image URL.

Thanks!

Fastest approve ever


error when trying to reset a user password

API error log:
openmeet-api
[Nest] 19 - 11/29/2024, 3:48:35 AM  ERROR [ExceptionsHandler] 385B27D0197F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
openmeet-api

openmeet-api
Error: 385B27D0197F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:

user and password are set in the secrets.env file, not in the configmap. I think they are correct, but I'll go try to verify that.
You think that's the mail sending causing the error?  Could it be a zulip connection instead?

Checked logs as well. It's related to ssl on mail sending. I've faced it too when sending MAIL_IGNORE_TLS=false. In this case it's not ignoring ssl but throwing exception instead.

Mail sends now, but we arrive at:
https://platform.openmeet.net/auth/password-change?hash=hashstring&expires=1732911812499#/

With no request to set a new password.
We should be prompted to reset the password and use the auth api to make it so.  Now I think this is a problem in platform, but keeping here because I don't know how to move it :)

Ok, if shouldn't be there. I'll move to properly set tenant config as we should pass tenant config 'frontendDomain' instead. Will keep updated the issue


feat(capture): export logs to Arrow

feat(capture): export logs to Arrow
feat: convenience command to capture logs from external scripts
feat: support -m module-level scripts
chore: rename CLI entrypoint from capture-logs to xpy
chore: add pyarrow dependency

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4  👈
#3
#2
#1
master

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

Join @blepabyte and the rest of your teammates on  Graphite

Merge activity

Jun 17, 4:27 AM EDT: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


tensorflow + tensorboard on cifs results in PermissionDeniedError

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Using stock example script mnist.py from https://github.com/dandelionmane/tf-dev-summit-tensorboard-tutorial
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): 16.04
TensorFlow installed from (source or binary): using standard tensorflow/tensorflow:1.1.0-gpu image
TensorFlow version (use command below): using standard tensorflow/tensorflow:1.1.0-gpu image
Python version: using standard tensorflow/tensorflow:1.1.0-gpu image
Bazel version (if compiling from source): tensorflow/tensorflow:1.1.0-gpu
CUDA/cuDNN version:
GPU model and memory: Tesla K80
Exact command to reproduce:

Describe the problem
I am running stock  mnist.py from https://github.com/dandelionmane/tf-dev-summit-tensorboard-tutorial on  tensorflow/tensorflow:1.1.0-gpu and running tensorboard in parallel on the same container. Everything works well if logdir is located on local ssd.
If i am configuring logdir to be on samba directory and using tensorboard during job execution (specifically if i am using Embeddings), the job fails at writing temp checkpoint files (see logs below). If I am not using tensorboard embeddings during job's execution, the job finishes successfully.
Source code / logs
2017-10-24 17:39:31.165783: W tensorflow/core/framework/op_kernel.cc:1152] Permission denied: ./model.ckpt-500.index.tempstate18351127508205389812
Traceback (most recent call last):
File "/mnt/batch/tasks/shared/LS_root/mounts/external/tb_sample/mnist.py", line 164, in
main()
File "/mnt/batch/tasks/shared/LS_root/mounts/external/tb_sample/mnist.py", line 156, in main
mnist_model(learning_rate, use_two_fc, use_two_conv, hparam)
File "/mnt/batch/tasks/shared/LS_root/mounts/external/tb_sample/mnist.py", line 136, in mnist_model
saver.save(sess, os.path.join(LOGDIR, "model.ckpt"), i)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 1391, in save
{self.saver_def.filename_tensor_name: checkpoint_file})
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 778, in run
run_metadata_ptr)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 982, in _run
feed_dict_string, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1032, in _do_run
target_list, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1052, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.PermissionDeniedError: ./model.ckpt-500.index.tempstate18351127508205389812
[[Node: save/SaveV2 = SaveV2[dtypes=[DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT], _device="/job:localhost/replica:0/task:0/cpu:0"](_recv_save/Const_0, save/SaveV2/tensor_names, save/SaveV2/shape_and_slices, conv1/B/_41, conv1/B/Adam/_43, conv1/B/Adam_1/_45, conv1/W/_47, conv1/W/Adam/_49, conv1/W/Adam_1/_51, conv2/B/_53, conv2/B/Adam/_55, conv2/B/Adam_1/_57, conv2/W/_59, conv2/W/Adam/_61, conv2/W/Adam_1/_63, fc1/B/_65, fc1/B/Adam/_67, fc1/B/Adam_1/_69, fc1/W/_71, fc1/W/Adam/_73, fc1/W/Adam_1/_75, fc2/B/_77, fc2/B/Adam/_79, fc2/B/Adam_1/_81, fc2/W/_83, fc2/W/Adam/_85, fc2/W/Adam_1/_87, test_embedding/_89, train/beta1_power/_91, train/beta2_power/_93)]]
Caused by op u'save/SaveV2', defined at:
File "/mnt/batch/tasks/shared/LS_root/mounts/external/tb_sample/mnist.py", line 164, in
main()
File "/mnt/batch/tasks/shared/LS_root/mounts/external/tb_sample/mnist.py", line 156, in main
mnist_model(learning_rate, use_two_fc, use_two_conv, hparam)
File "/mnt/batch/tasks/shared/LS_root/mounts/external/tb_sample/mnist.py", line 114, in mnist_model
saver = tf.train.Saver()
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 1056, in init
self.build()
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 1086, in build
restore_sequentially=self._restore_sequentially)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 689, in build
save_tensor = self._AddSaveOps(filename_tensor, saveables)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 276, in _AddSaveOps
save = self.save_op(filename_tensor, saveables)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 219, in save_op
tensors)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_io_ops.py", line 780, in save_v2
tensors=tensors, name=name)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/op_def_library.py", line 768, in apply_op
op_def=op_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2336, in create_op
original_op=self._default_original_op, op_def=op_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1228, in init
self._traceback = _extract_stack()
PermissionDeniedError (see above for traceback): ./model.ckpt-500.index.tempstate18351127508205389812
[[Node: save/SaveV2 = SaveV2[dtypes=[DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT], _device="/job:localhost/replica:0/task:0/cpu:0"](_recv_save/Const_0, save/SaveV2/tensor_names, save/SaveV2/shape_and_slices, conv1/B/_41, conv1/B/Adam/_43, conv1/B/Adam_1/_45, conv1/W/_47, conv1/W/Adam/_49, conv1/W/Adam_1/_51, conv2/B/_53, conv2/B/Adam/_55, conv2/B/Adam_1/_57, conv2/W/_59, conv2/W/Adam/_61, conv2/W/Adam_1/_63, fc1/B/_65, fc1/B/Adam/_67, fc1/B/Adam_1/_69, fc1/W/_71, fc1/W/Adam/_73, fc1/W/Adam_1/_75, fc2/B/_77, fc2/B/Adam/_79, fc2/B/Adam_1/_81, fc2/W/_83, fc2/W/Adam/_85, fc2/W/Adam_1/_87, test_embedding/_89, train/beta1_power/_91, train/beta2_power/_93)]]

@dandelionmane @jart should this be filed directly against's dandelion's project?

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Do you have any recommendations for now how to avoid those errors or there is no way to store and consume the output from cifs?


remove send alert

wmagent version of #6815

But was the component crashing at this call? I though it had no use, but wouldn't complain as well.

test this please

test this please

@ticoann I'm pushing it to all FNAL nodes for now, if it really solves the issue, then we push it to the other CERN agents and also make a master branch fix.

@ticoann feel free to merge this


v2.5.0 - Add new Mocha and Jest strategies

@adamjonas — bumped it to 2.4.3 instead of 2.5.0 and added back that file-ending new line. Someone with push access will have to rake build and rake release.

@adamjonas — switching over to using a hot-reloading local server for the pre-React JavaScript labs. Should I squash commits?
Also re-bumped to 2.5.0 given the extent of the new functionality added.

@joshrowley No changes to Ironboard or Ironbroker required — the new Mocha strategy hits the exact same endpoint as the old Mocha strategy, and I structured the test results identically to how mocha-multi does it. Full integration works perfectly! 🙂
For your own testing, fork and clone https://github.com/learn-co-students/javascript-fix-this-v-000, then git remote add curriculum git@github.com:learn-co-curriculum/javascript-fix-this.git and git fetch curriculum.
Build and install this version of learn-test, checkout solution, and run learn (or learn-test). The old, Node-based Mocha suite should execute.
Then, checkout mocha-in-browser-solution, run the tests, and the new, browser-based Mocha suite will execute. If you're in the IDE, you'll have to click on the provided URL to open your browser. If you're local, your browser should open automatically when you run learn / learn-test.

Cool, thanks @gj ! This looks great, I'll try to do some more testing, review, and ship by tomorrow morning.

Sounds great — thanks again @joshrowley !

One last note @joshrowley — I have the in-browser strategy rescue-ing Interrupt, then cleaning up a file and exiting gracefully. Works perfectly with the learn-test command, but when the student simply runs learn, we still get a bit of an ugly exit from the learn-co gem. Might be worthwhile updating that gem to also exit gracefully. Thoughts?

@joshrowley removed the Interrupt funny business for now. This PR leaves open the question of what should be done with the double-whammy stack trace.

Closing this in favor of #44.


Make a parameter out of front layer elevation

Make font layer elevation a parameter, so that you can easily change the amount of shadow you want to have there.
I've discussed this with Felix (@WieFel) on gitter, he suggested that the elevation here is set to "1", so maybe you could make it a parameter?

@hendrychjan Thank you for the suggestion.
Can you write the PR for this?

Sure. How much is it urgent? Can I do it during the weekend?

@hendrychjan sure, whenever you have time! ;)

The feature has landed on pub.dev with v0.7.0.
Thanks @hendrychjan for suggesting it, check yourself in project README!


Handle NUL code point in tb_utf8_unicode_to_char.

This is a bit semantic, but assuming the return value of tb_utf8_unicode_to_char is supposed to represent the length (as in strlen) of the resulting UTF-8 string out, a NUL code point should result in a 0-length string, not 1-length.

Makes sense.

Hold on, wait. It doesn't represent strlen, but the encoded version of the unicode code point and 0 encodes as 0 in utf8.

But.. I wanted to rewrite the utf8 portion of the termbox library anyway, maybe now is a good time.

Yeah, I was unclear if it was supposed to represent strlen or size of code point in bytes. I think c==0 is the only case where strlen(out) != size of code point in bytes. But then again, strlen(out) is not safe unless you pass in a zeroed char[7]. In any case, can easily fix on call-side. Feel free to revert.

Yep, for now I'll revert it. The UTF8 functions aren't exactly best and are not suited for general purpose usage. They are here simply because standard C libraries don't provide that kind of functionality.


Searching Algorithms in Java

There are no searching algorithms under the Algorithm/Searching_Sorting folder. I would like to add a few searching algorithms in Java.
Request you to assign it to me as a part of GSSOC'21

I am a GSSOC '21 participant.
I wish to contribute a JAVA code for this issue:
My code will have comment lines to make it explanatory and understandable to everyone.
I will be very happy if I am assigned this issue and allowed to work on this.

Raise separate issues for each searching algorithms. Some of them are already being implanted by the people.


add build agent info to metrics

This adds a label "agent" with the name of the node the job ran on to the metrics.

Hi, this pull request is being closed because this repo is archived and not maintained since years.


Train metrics not finite: {'psnr': nan,} error while training

I am trying to train on very small dataset 24 images out of which 6 images are given for val.
facing the below issue can you tell me what is going wrong or is it because of dataset size ?
Max image index is 23: using dtype: <class 'numpy.uint16'>
Allocating 200 chunks to dataset path /mnt/sdb1/sumant/act_nerf/building-pixsfm/oiccdust4
200 chunks allocated
100%|████████████████████████████████████████████████████████| 24/24 [01:22<00:00,  3.46s/it]
Finished writing chunks to dataset paths
  0%|                                                 | 76/500000 [00:25<41:16:11,  3.36it/s]{
  "message": {
    "message": "Exception: Train metrics not finite: {'psnr': nan, 'depth_variance': tensor(nan, device='cuda:0'), 'photo_loss': tensor(nan, device='cuda:0', grad_fn=<MseLossBackward0>), 'loss': tensor(nan, device='cuda:0', grad_fn=<MseLossBackward0>)}",
    "extraInfo": {
      "py_callstack": "Traceback (most recent call last):\n  File \"/home/ubuntu/anaconda3/envs/mega-nerf/lib/python3.9/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py\", line 345, in wrapper\n    return f(*args, **kwargs)\n  File \"/mnt/sdb1/sumant/act_nerf/nbs/mega-nerf-main/mega_nerf/train.py\", line 24, in main\n    Runner(hparams).train()\n  File \"/mnt/sdb1/sumant/act_nerf/nbs/mega-nerf-main/mega_nerf/runner.py\", line 261, in train\n    raise Exception('Train metrics not finite: {}'.format(metrics))\nException: Train metrics not finite: {'psnr': nan, 'depth_variance': tensor(nan, device='cuda:0'), 'photo_loss': tensor(nan, device='cuda:0', grad_fn=<MseLossBackward0>), 'loss': tensor(nan, device='cuda:0', grad_fn=<MseLossBackward0>)}\n",
      "timestamp": "1660270116"
    }
  }
}
Traceback (most recent call last):
  File "/mnt/sdb1/sumant/act_nerf/nbs/mega-nerf-main/mega_nerf/train.py", line 28, in <module>
    main(_get_train_opts())
  File "/home/ubuntu/anaconda3/envs/mega-nerf/lib/python3.9/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 345, in wrapper
    return f(*args, **kwargs)
  File "/mnt/sdb1/sumant/act_nerf/nbs/mega-nerf-main/mega_nerf/train.py", line 24, in main
    Runner(hparams).train()
  File "/mnt/sdb1/sumant/act_nerf/nbs/mega-nerf-main/mega_nerf/runner.py", line 261, in train
    raise Exception('Train metrics not finite: {}'.format(metrics))
Exception: Train metrics not finite: {'psnr': nan, 'depth_variance': tensor(nan, device='cuda:0'), 'photo_loss': tensor(nan, device='cuda:0', grad_fn=<MseLossBackward0>), 'loss': tensor(nan, device='cuda:0', grad_fn=<MseLossBackward0>)}
  0%|                                                 | 76/500000 [00:25<46:26:51,  2.99it/s]

2.While preparing also what is the use of grid_dim i have given 2 2 will it effect the output ?

@hturki kindly provide some feedback ,please look into this ?

i had the same issue.  for my dataset, i had the ray_altitude_range set to [8,100], and use grid size 1, 1 to train a single small scaled scenario.
{
"message": {
"message": "Exception: Train metrics not finite: {'psnr': nan, 'depth_variance': tensor(nan, device='cuda:0'), 'photo_loss': tensor(nan, device='cuda:0', grad_fn=), 'loss': tensor(nan, device='cuda:0', grad_fn=)}",
"extraInfo": {
"py_callstack": "Traceback (most recent call last):\n  File "/home/weide/miniconda3/envs/mega-nerf/lib/python3.9/site-packages/torch/distributed/elastic/multiprocessing/errors/init.py", line 345, in wrapper\n    return f(*args, **kwargs)\n  File "/home/weide/dev/meganerf/mega-nerf/mega_nerf/train.py", line 24, in main\n    Runner(hparams).train()\n  File "/home/weide/dev/meganerf/mega-nerf/mega_nerf/runner.py", line 261, in train\n    raise Exception('Train metrics not finite: {}'.format(metrics))\nException: Train metrics not finite: {'psnr': nan, 'depth_variance': tensor(nan, device='cuda:0'), 'photo_loss': tensor(nan, device='cuda:0', grad_fn=), 'loss': tensor(nan, device='cuda:0', grad_fn=)}\n",
"timestamp": "1660596324"
}
}
}

@weidezhang are you able to prepare the dataset using pixsfm ?

@weidezhang are you able to prepare the dataset using pixsfm ?

i was using colmap to refine the poses.

You can try disabling mixed-precision training via the no-amp option if you think numerical stability is an issue, but is this a 360 degree scene? 18 images is a very small number to be training a NeRF against, and Mega-NeRF is generally designed for larger datasets. There are many NeRF variants that are likely better suited to handle low-data regimes.

@hturki
check https://github.com/cmusatyalab/mega-nerf/issues/16 this @menglongyue tried with 507 images still getting the same error .
is there something(me @weidezhang @menglongyue) we could have missed while preparing it for custom dataset ?
just to info we all creating camera poses by using colmap only instead of pixsfm

It's hard to determine from this message alone - outside of potential bugs in the codebase the main thing that the nan is calling out is that the training is not converging. You can try to trace the exact batch that's causing the nan to see if there is in fact a bug in the rendering code somewhere but if that's not the case the main thing I'd assert is that 18 images at least is a small number of images to train a large-scale 360 scene representation (what Mega-NeRF is designed for) against

I met the same problems running on custom datasets.

I also met the same problem, is it wrong with the ray_altitude_range? Then the problem is how to set the correct ray_altitude_range on custom datasets.

I had struggled with the ‘psnr: nan’ problem for a long time. And I solved this problem by using the model_aligner part in COLMAP with the gps information that my dataset contains.

@alan355 @hturki Would you please state more information regarding model_aligner of COLMAP? It seems COLMAP coordinate system is first RDF. I guess that its model_aligner with my gps information changes the coordinates system(based on ENU) to something else(I guess RFU, I have had terrible days because I don't know to handle this correctly.) MegaNeRF's preprocessing is from RDF to DRB. How would you train a geo-referenced dataset?

I had struggled with the ‘psnr: nan’ problem for a long time. And I solved this problem by using the model_aligner part in COLMAP with the gps information that my dataset contains.

hello，thank you very much，Is your colmap on linux? can you tell me how to use colmap's model_aligner on windows？

I faced the same issue. I solved it with changing parameters on yaml config file. I remove parameter ray_altitude_range and added no_ellipse_bounds: True. But when creating an octree, script throws an error because parameter ray_altitude_range is not defined. Then I defined this parameter but in Mega-NeRF I see only black rectangle.

长期以来，我一直在为“psnr：nan”问题而苦苦挣扎。我通过使用 COLMAP 中的model_aligner部分和我的数据集包含的 GPS 信息解决了这个问题。

Hi, I'm having the same problem, can you elaborate on how you solved it?

长期以来，我一直在为“psnr：nan”问题而苦苦挣扎。我通过使用 COLMAP 中的model_aligner部分和我的数据集包含的 GPS 信息解决了这个问题。

Hi, I'm having the same problem, can you elaborate on how you solved it?

The problem occurs while rendering rays. Could you analyze the context of the variable results[f'rgb_{typ}'], after the line https://github.com/cmusatyalab/mega-nerf/blob/main/mega_nerf/runner.py#L362
Analyze for its shape, search for nans, infs
Second, you should set hyper parameter fine_samples to 0 to understand if the error occurs during this
https://github.com/cmusatyalab/mega-nerf/blob/main/mega_nerf/rendering.py#L195
or this
https://github.com/cmusatyalab/mega-nerf/blob/main/mega_nerf/rendering.py#L227
Finally analyze the function _inference. I suppose the error occurs here https://github.com/cmusatyalab/mega-nerf/blob/main/mega_nerf/rendering.py#L373 when variable weights for some reasons has invalid values, therefore maybe you analyze variable weights here. This variable is fromed from two variables: 'alphas' and 'T', you should print them in console after line https://github.com/cmusatyalab/mega-nerf/blob/main/mega_nerf/rendering.py#L367.
All this you analyze after one launch of training, because I see you've trained for 4 hours, thus you should print too much to understand more at once.


nan_json.h(113): error C2660: 'v8::JSON::Stringify': function does not take 3 arguments

It appears nan 2.6 is incompatible with code written against 2.5.1. Why wasn't this a major release bump?

It's just a bug and we can fix it.  What version of node did you build against when you saw this error?

I see this could happen using v8 headers from version 5.2 ... Node 7.x uses v8 headers from version 5.4.x ...  A simple version check can fix this, so I'm putting up a new PR.  Meanwhile, it would be great to know exactly which version of node you are building against @seanzer .

Building an Electron (v1.3.1) app with Node 6.9.1. It looks like this change broke my team via keytar somehow.

OK, thanks for the report.  I'm pretty sure my PR #659 will fix this.  Hopefully somebody with merge rights can take a look at it and publish the fix ASAP.

Hey @mkrufky @kkoopa
Is there any way we can get this merged in and a build kicked off? We're really struggling to find a way to work around this for an app based on Electron V1.3.1. Honestly we're not even sure why it's picking up the latest version when all of our dependencies (key tar) specify a specific version.
We'd really appreciate an expedited release or a suggested work-around. We're using Electron V1.3.1 with electron-rebuild to build keytar.

Sorry to scream fire/wolf. We found a work-around. We were using keytar 3.0.0 instead of 3.0.2 and 3.0.2 specifies a specific version.
Thanks for looking into it @mkrufky


cannot recursively call into Core

Hello
It seems that by using tokio-executor under the hood, the behaviour changed in backwards-incompatible way. If inside one future I create a new core and try to run something in it, it panics with cannot recursively call into Core (https://github.com/tokio-rs/tokio-core/blob/master/src/reactor/mod.rs#L242).
I know this is an edge case and that I'd try to avoid it in a real application (I use it in some tests, checking some edge cases of my own) and that the reason for it is to actually disallow this degenerate case, but it was allowed before, so I don't know if it's OK to forbid it now.

This behavior was, in theory, never permitted. It was just never enforced.
Could you explain more how you were using it? It would probably be best to figure out a way around it.

If I’m understanding this properly, doesn’t this meant that two independent libraries can’t create Cores separately in the case where one might depend on the next?
Especially in the case of wrappers that might be attempting to create synchronous interfaces?
Do we need to enforce that a Core is the only Core on any particular thread?

My understanding is you can run one core, let it terminate, then run another. But if you create one core, spawn a future into it and inside that future create another core and run it, it'll panic because you most likely don't want that. The inner core would be blocking inside the outer one and the outer one would not be able to execute futures at the time.
And in my understanding libraries should never create their own cores, but be provided with a handle (or tokio::runtime) by the application and spawn whatever they need onto that.

@bluejekyll as @vorner stated above, you can create an arbitrary number of cores per thread. What you cannot do is block on a core (call run) from within a future as that would be pretty disasterous to the Async runtime characteristics.

Is this safe?
https://github.com/bluejekyll/trust-dns/blob/master/resolver/src/resolver.rs#L126

I'm hitting this issue with two libraries that manage their own cores (actix-web & ldap3). This is definitely a breaking change for me.
A few questions:

Is this actually something that should be enforced by tokio?  If there is recursive cores then the inner one will block yes, but it should still work fine otherwise (and has been working for me in the past).
If it is enforced, should it panic? I would assume that it should propagate up as a Result?
How would you manage this with two libraries that are trying to hide implementation details to support blocking use?  Seems like this is very leaky if you need to now worry about whether another core is running or not.

If there is recursive cores then the inner one will block yes, but it should still work fine otherwise [...]

Actually, there are several cases where it will grind the thread to a halt. I've seen this reported before in hyper, where people have a Core running their server, and wish to start a client to pipe a request body to another location. They end up with core.run(client.request(req_using_server_body)), and so, the inner Core will block waiting for the incoming server body to make progress, but it cannot since the thread is blocked by the inner Core. Panicking is probably better here.

I agree in my case it'd probably make sense to make the trait I was working with futures-aware, but that will take some time to refactor.  I have basically just spawned a separate thread to work around it for the time being.
I still was initially horrified over the panic, as I was not expecting it to happen at all! It would be nice if there was a Result returned instead, so I can deal with this at compile time, not when it popped up during runtime.  I understand that'd probably break the signature of run though, so may not be possible.
At the bare minimum, maybe some documentation along the lines of:  Calling this method when inside an existing future's execution (i.e, recursively) on the same thread will cause a panic, as it would otherwise cause a deadlock

Yeah, we cannot break the signature of run. The current signature is unfortunate.
Would you mind submitting a PR that includes the snippet under the "panics" section of the docs?

Ok, I will submit a PR


Markham, Ontario

broken:
http://results.openaddresses.io/sources/ca/on/city_of_markham
contacted:
<EMAIL_ADDRESS>

Justin,
Thank you for contacting the City of Markham.
If you are a company looking for data and are working on a City project, then you would make the request through the City department you are working with for the project.
If you are an individual looking for data, then you would contact the GIS Department (contact information below):
Stephen Geyer
<EMAIL_ADDRESS>OR
Matt Miller
<EMAIL_ADDRESS>Should you have any further questions, or if you are providing additional information to us, please direct your email to<EMAIL_ADDRESS> This will ensure the most timely response from our representatives.
Alternatively, you can also call us at<PHONE_NUMBER> Monday – Friday 8:00am – 5:00pm, and any one of our representatives will be pleased to assist you.
Thanks and regards,
Natasha, from your Customer Service Team
Customer Service Representative | Contact Centre | City of Markham
101 Town Centre Boulevard, Markham, ON L3R 9W3
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
<EMAIL_ADDRESS>www.markham.ca

emailed:
Stephen Geyer
<EMAIL_ADDRESS>OR
Matt Miller
<EMAIL_ADDRESS>


Minimal integration of Tiered Commitment Tree

Is your feature request related to a problem? Please describe.
#491 proposed a new structure to replace the existing note commitment tree using the incrementalmerkletree crate from Zcash.  This is now (mostly) implemented as the penumbra-tct crate.
In the meantime, we've also been running into performance issues with the incrementalmerkletree crate, so replacing it sooner rather than later seems better.
Describe the solution you'd like
The TCT design allows for the possibility of much more efficient synchronization, but as a first-pass, we should aim to drop it in place of our existing incrementalmerkletree API.  This would not use any of the tiered features of the new API, and just add every note commitment on the pd side as well as on the client side.
Making use of the new features would require changes to the client protocol, as well as the client logic, and should probably wait until after #587.

We've done this in the Pandia testnet.


Add Declared License

Type: Missing
Summary:
Add Declared License
Details:
Source declares MIT/GPLv2 dual: https://github.com/scottjehl/Respond/tree/b21c5785e8442cca651f532ce72e6e515817ad3d
Some scripts declare dual MIT/BSD.  Because type of BSD is not specified, coded to "OTHER."
Resolution:
Added declared license, copyright information.
Affected definitions:

respond 1.2.0

@royaljust - for files "content/Scripts/respond.js" and "content/Scripts/respond.min.js," would we say "(MIT OR OTHER) AND (MIT OR GPL-2.0-only)," as those files include both these references - [ Authors & copyright (c) 2012: Scott Jehl, Paul Irish, Nicholas Zakas. Dual MIT/BSD license / ] and [ /! Respond.js v1.2.0: min/max-width media query polyfill. (c) Scott Jehl. MIT/GPLv2 Lic. j.mp/respondjs  */ ]

@ariel11 thanks for the catch.  Yes to both for those files.


Extra fraction in the result of in_each_component method

Given:
time = Time.now
TimeDifference.between(time, time + 6.months).in_each_component

Then:
{
  :years   => 0.5,
  :months  => 6.02,
  :weeks   => 26.14,
  :days    => 183.0,
  :hours   => 4392.0,
  :minutes => 263520.0,
  :seconds => 15811200.0
}

The months has 0.02 more, why this difference, not just 6.0?

@wbotelhos computer calculates at a higher precision http://www.wolframalpha.com/input/?i=Time+from+now+and+6+months+later

Hi, Thanks for the answer.
I had to calculate manually using  next_month and counting the index, because we have months with 28, 29, 30 and 31 days. In a big range of months we get a big difference of amount/month. 6 months * 1 dollar is different of 6.02 months vs 1 dollar. But it works fine for weeks, days and so...
Thank you.


package:googleapis_auth/auth.dart deprecated and shouldn't be used in plugins

This is blocking CI; see here
Checking project extension_google_sign_in_as_googleapis_auth...

  info - 'package:googleapis_auth/auth.dart' is deprecated and shouldn't be used. Use `googleapis_auth.dart` instead at lib/extension_google_sign_in_as_googleapis_auth.dart:9:1 - (deprecated_member_use)

cc @stuartmorgan

Occurs on #77479.

https://github.com/flutter/plugins/pull/3689 will fix this.
This is another instance of needing https://github.com/flutter/flutter/issues/76229 so we hit these locally, not on rolls.


new warning when using Visual Studio 2022 17.9

Some of our build machines are still with a Visual Studio 2022 17.9 and not 17.10 and for internal reasons - large company, different teams, bla bla bla, the upgrade will come later this year.
but when using the latest package, we get
 CSC : warning CS9057: The analyzer assembly 'C:\Users\AzDevOps\.nuget\packages\verify.mstest\26.0.1\analyzers\dotnet\roslyn4.4\cs\Verify.MSTest.SourceGenerator.dll' references version '<IP_ADDRESS>' of the compiler, which is newer than the currently running version '<IP_ADDRESS>'.

Is it expected that Verify breaks compatibility with older visual studio version  ?
we're worried that the warning is hiding other things

@SimonCropp  thanks for your reactivity !

just pushed 26.1.1 to nuget. might take 15min for nuget to refresh its cache

@SimonCropp  Is it possible to downgrade the compiler version to 4.8?
We are getting errors from CodeQL analyser

CSC : warning CS9057: The analyzer assembly '/home/runner/.nuget/packages/verify.mstest/28.2.0/analyzers/dotnet/roslyn4.4/cs/Verify.MSTest.SourceGenerator.dll' references version '<IP_ADDRESS>' of the compiler, which is newer than the currently running version '<IP_ADDRESS>'.

https://stackoverflow.com/questions/79279857/verifytests-testcontext-is-a-type-which-is-not-valid-in-the-given-context


Removes --remote option from vd

Resolves se-passau/VaRA#532.

 Here is an overview of what got changed by this pull request:

Clones removed
==============
+ varats/development.py  -2

See the complete overview on Codacy


Create a rule checking whether the name of a variable is always written the same way

This could be a sort of extension of rule possible-variable-overwriting.
It need not be obvious that variables e.g. ${abc} and ${A_B C} are the same.  Imagine the situation: someone sees variable ${MY VAR} in a foreign code. They want to check occurences of the variable to discover where it is used and for what purpose etc. but they are not able to find all its occurences because the same variable is named e.g. ${MY_VAR} somewhere. In this case it is almost impossible to find all occurences of the variable by standard means: AFAIK, Robot language server cannot do it; and standard search for a string can usualy ignore the case of letters, but cannot ignore mismatch in spaces and underscores. The only way I consider to be usable for search for all the possible forms of the variable is regular expression [mM][_ ]?[yY][_ ]?[vV][_ ]?[aA][_ ]?[rR]. Ugh.
My suggestion: allow the only form of the name of a variable. It would be probably the best to check whether the variable is named everywhere like at its first occurence (since this will probably be its definition or first setting of its value).

Hey @MoreFamed,
I think that this is how the rule works now - it looks for any variable that looks visually differently but is exactly the same variable (as read by Robot Framework) and it reports a rule violation on each NEXT occurrence of this variable. Which means that if you have ${my var} and then ${MY_VAR} it will report only on ${MY_VAR}. Also, it only checks for an overwriting inside test case or a keyword. Unfortunately, we would not implement a more complex handling of this situation with variables coming from imported files or from higher scope, because we would need to implement context reading and remembering all variables with a reference where they appeared. Is that what you asked for? If not, please elaborate more.
Unluckily, this is how RF works and it's not perfect that it allows so much freedom when comes to the variables naming, but thanks to that, we can write tests, that are closer to the natural language than any other programming language.

Thanks. I understand difficulties of implementation of context awareness. I did not know what could be done in Robocop easily... It's a pity.
However, what about extending the rule so that it would report all usages of a variable under a different name, not only assignement to it? E.g. now, this situation is reported:
${ABC}  Set Variable  xyz
${abc}  Set Variable  123

and I consider reporting even this situation:
${ABC}  Set Variable  xyz
Log  ${abc}

But there is a "conceptual" difference: in the first case the author probably doesn't know that those variables are the same; in the second one they write one variable in a sloppy way. I don't know whether the second case occurs often, so whether extending the rule is worth the work...
If you do not like my idea, please, close this issue.

That type of check (within scope of given keyword/test case, at most reading from suite variables) can be done. But it would be then different rule - or we would need to rename this rule. For example to "inconsistent-variable-name" or similar.

Yeah, this can be done. I think we can just create a new rule so that we will have a more precise description of it.


Sending messages

[x] Subscribe confirmation
[x] Unsubscribe confirmation
[x] List subscriptions
[x] New alert notification

All done


Find total number of dads connected

DaddyLaugh
Problem:
We want to see how popular this actually gets
Solution:
Display total number of users connected at a particular instant

hey @arjun-sir, can you give me a little idea about how to solve it, if we want to count the total number of users at a particular time, the website should be live, right?? but here how can I connect this page to any database?? Correct me if I'm wrong and plz give me a little hint.

Yes, we do need to use databases to solve this.
If you're willing to solve this one, i'll get it deployed and you can work on it

Yaa plz, I also want to see how popular dad is!! 😀

Okay it is deployed here: https://lucent-moonbeam-6aa4d2.netlify.app/daddy-laugh/
Once I merge your PR, it'll reflect over here and we can test it out.
Make sure to test it in your localhost beforehand tho


Update mdillon/postgis to official image

It seems that the mdillon/postgis image that we use is outdated and moved to the new home, https://registry.hub.docker.com/r/postgis/postgis/ and renamed to postgis/postgis. I think we should update our docs and CI to use this image preferably as that seems to be the official image released by postgis. Only difference is that for this image to work we need to pass a super user password or set POSTGRES_HOST_AUTH_METHOD: trust.

I think we're rather heading in that direction :wink:

I think we're rather heading in that direction wink
(edit: that does not prevent updating the image if it improves the codebase)

Ah, didn't know we were going to remove postgis altogether. 😄

I merged the PRs.
I still think it would be valuable to get rid of postgis, the issue is still relevant. https://github.com/opencollective/opencollective/issues/3171


Safelist does not allow with src attribute on  tags

I've noticed that this code does not work:
Safelist whitelist = Safelist.relaxed();
whitelist.addTags("audio");
whitelist.addAttributes("audio", "src", "controls");

The src tag is always stripped from the <audio> element.
Am I missing something here and is there any chance we could allow audio tags with src attributes through Safelist?

Closing this because I thought the src attribute was on the audio tag itself, but actually it is a child element <source> inside the audio tag.


Notification handler overwrites valid/matching payment object key with PSP number

Describe the bug
notification module overwrites valid/matching payment object key with Adyen PSP number
To Reproduce

The web application is creating a CT payment object with key 'XT000000000000344-PY1'.
The web application is updating the CT payment object the field 'createSessionRequest'. the create session request has 'reference' set to value 'XT000000000000344-PY1'.
complete the payment in Adyen web-drop-in
notification module receives authorization success notification from Adyen.
the notification request contains the field 'merchantReference' with value 'XT000000000000344-PY1'.
notification module updates payment object key with the Adyen PSP number, but it should not change the payment object key because the field 'merchantReference' matches the payment object key.
/notification/src/handler/notification/notification.handler.js lines 221,222 do not consider the field 'notificationRequestItem.merchantReference'
as result the condition on line 223 is false and the CT payment object key is overwritten

Suggested fixed:
const newPspReference = notificationRequestItem.merchantReference || notificationRequestItem.originalReference || pspReference

Hey @lwjoergf
Please note that the Adyen extension and notification modules use the payment key for internal logic to fetch and update CT payment instance. In general case, it is not possible to keep the custom payment key since Adyen modules support custom refund reference. For more in-depth details regarding this decision please refer to Matching Adyen Notification with commercetools payment page.
Thank you,
Best regards.

Hey @lwjoergf
Do you still experience the same issue?
Best regards.


BoosterNotification Rules are validated as OPEN

Describe the bug
Rule BNR-DE-4161 is validated as OPEN when we validate a Vaccination certificate
Exception: java.lang.RuntimeException: date argument of "plusTime" must be a string
All Rules are validated as OPEN when we validate a Recovery certificate
Exception: java.lang.RuntimeException: date argument of "plusTime" must be a string
Expected behaviour
Rule should be validated as FAIL
Vaccination certificate
dataJsonNode:
{"external":{"validationClock":"2022-01-15T10:51:03.857+01:00","valueSets":{},"countryCode":"de","exp":"2022-07-30T15:01:59Z","iat":"2021-07-30T15:01:59Z","issuerCountryCode":"de","kid":"","region":""},"payload":{"issuer":"DE","validFrom":1627657319,"validUntil":1659193319,"nam":{"gn":"AstraZeneca","fn":"Vaccine","gnt":"ASTRAZENECA","fnt":"VACCINE"},"dob":"1921-08-21","v":[{"tg":"840539006","vp":"1119305005","mp":"EU/1/21/1529","ma":"ORG-100001417","dn":2,"sd":2,"dt":"2021-08-02","co":"DE","is":"Robert Koch-Institut","ci":"URN:UVCI:01DE/IBMT102/3CU9LYH1VHUMMDF86T7X3S#L"}],"t":[],"r":[],"ver":"1.3.0","dateTimeSeparator":"T","empty":0,"yearCount":4,"yearMonthCount":7,"yearMonthDayCount":10}}

Recovery certificate
dataJsonNode:
{"external":{"validationClock":"2022-01-15T10:48:01.219+01:00","valueSets":{},"countryCode":"de","exp":"2022-07-30T15:02:01Z","iat":"2021-07-30T15:02:01Z","issuerCountryCode":"de","kid":"","region":""},"payload":{"issuer":"DE","validFrom":1627657321,"validUntil":1659193321,"nam":{"gn":"Recovery","fn":"RichyThree","gnt":"RECOVERY","fnt":"RICHYTHREE"},"dob":"1921-08-21","v":[],"t":[],"r":[{"tg":"840539006","fr":"2021-08-02","df":"2021-08-30","du":"2022-02-01","co":"DE","is":"Robert Koch-Institut","ci":"URN:UVCI:01DE/IBMT102/51VONE4URYN03AO7ID2N91#S"}],"ver":"1.3.0","dateTimeSeparator":"T","empty":0,"yearCount":4,"yearMonthCount":7,"yearMonthDayCount":10}}

BoosterNotification rules:
bnr.txt

On the first view, the logic is a little bit problematic. The rule describes an AND with two concurrent conditions. If a entry in recovery exists, the rule will calculate recovery entry r.0 and compares it with entry v.0 from a vaccination certificate. Both of them are not present in the same time. So far i see you inject r:[] and t:[] and v:[] but this is not enough. It must be minimum r:[{"dt":"..."}] otherwise the expression results to null and the exception is correct (not a string). What is the intention behind that mix of different certificates in one rule? Is there maybe a mistake in the line or any misspelling? Can you please check if this is the problem?:)
"and": [ {"if": [ {"var": "payload.r.0" },
{"after": [{"plusTime": [ {"var": "payload.r.0.df" },0,"day"]},
{"plusTime": [{"var": "payload.v.0.dt"},0,"day" ]}
]
},
false
]
},
{"before": [{ "plusTime": [{"var": "payload.r.0.df"},120,"day" ]},
{"plusTime": [{ "var": "external.validationClock"},0, "day"]
}]
}] }}

@pucherd the rule BNR-DE-4161 does indeed have a logical mistake. We will fix the rule and provide an updated one. (@SchulzeStTSI thanks for the analysis).
Regarding when we validate a Recovery certificate: BNRs should only be evaluated if a Vaccination Certificate is available. If there is a VC and RC, the JSON data structure should be merged to include v[0] and r[0]. If there is only a Recovery Certificate, BNRs should not be evaluated. Thus, the behavior that you are observing in that case (i.e. rules evaluate to open) is expected, as the rules try to access VC information which is not available.

@pucherd the updated rule should look like this:
Logic:
  and:
    - if:
        - var: payload.r.0
        - after:
            - plusTime:
                - var: payload.r.0.df
                - 0
                - day
            - plusTime:
                - var: payload.v.0.dt
                - 0
                - day
        - false
    - if:
        - var: payload.r.0
        - before:
            - plusTime:
                - var: payload.r.0.df
                - 120
                - day
            - plusTime:
                - var: external.validationClock
                - 0
                - day
        - false

We'll file a CR to change it on the server...

@pucherd, @mlenkeit, @SchulzeStTSI
New rule BNR-DE-5064 with the fix is available.

@pucherd can you check please and close the issue or comment.

Thank you. Can be closed


Navigation to the exact cell with a11y issues is not working with some of the notebooks

I tried uploading a new notebook and running the extension. It listed the issues, but when I clicked on one, it didn't navigate to the cell with the issue. I've shared a screen recording in Slack for your reference. This has happened for few notebooks and not every other notebook

This is an issue that happnes when 2 notebooks are loaded at the same time. A simple fix is checking if the cell exists in the current notebook or not.

Resolved in main.

@ranashreyas I am re-opening this thread considering the issue reported in Slack. Let me know if you want me to open a new issue instead.

Fixed the partial autoscroll issue in main.

Looks like it got fixed with https://github.com/berkeley-dsep-infra/jupyterlab-a11y-checker/commit/b6150a40d379088bcc4cc54e1da198ead337d1b5


THORN-2293: Arquillian tests require the bootstrap module added as a compile time dependency

Motivation
The "findWildFlySwarmBootstrapJar" method in org.wildfly.swarm.tools.DependencyManager searches for the bootstrap jar in the "COMPILE" dependencies only.
When running Arquillian based test cases, it is not necessary that every project has an explicit "compile-time" dependency on the bootstrap module.
E.g.,
In a multi-module project, I might have modules that generate stand-alone libraries, but are still being tested using the Thorntail integration.
Modifications
Changed the DependencyManager to look for bootstrap jar in test dependencies as well.
Result
Defining the Arquillian dependency as a test scope is sufficient to get the test cases running.

[x] Have you followed the guidelines in our Contributing document?
[x] [v2] Have you created a JIRA and used it in the commit message?
[ ] [v4] Have you created a GitHub Issue and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install?

bootstrap isn't needed as a direct compile dependency, but it should be present transitively as a compile dependency of something else.
It also appears this change broke the MP TCKs

@kenfinnigan I don't expect this PR to be merged as is, because even I am not convinced of the changes. I wanted to start a discussion about it.
Based on your explanation, the only time this issue would show up is if I have a library module that is executing tests using Thorntail+Arquillian and this library does not have any direct dependencies on Thorntail modules.
Would that be a correct statement?

I believe so yes.


The type of data

I am getting real time data with cortex sub.data py but ı can’t understand what is the type of this data?
what should ı do for reachimg  voltage values from these datas

Hi @Batuhanyucel
The format of the data you receive from the Cortex API is described here:
https://emotiv.gitbook.io/cortex-api/data-subscription/data-sample-object

İt says “ For each EEG sensor, you get 1 value in microvolt” but values are over 400 mV it is real ?

Correction : over4000

Hi @Batuhanyucel
Yes, the values usually are around 4200 micro volts. It is expected.
But before you do analyze the data, it is recommended that you remove the DC offset.
https://emotiv.gitbook.io/emotivpro-v3/notes-on-the-data/dc-offset

Thank you


Refactor CCM tests.

This is #566 opened up against 2.1 branch.   I did this so was easier for me to review.

Updated a couple of tests to use CCMTestsSupport (just to get myself more familiar with the framework / test a few things). This is working super great :+1:

@tolbertam In the end I'm now in favor of allowing dirtiesContext with PER_CLASS; you can order test methods so it could make sense to have one context per class and allow methods to modify it.
I also reverted log4j.properties, that was a mistake (I use a less verbose version specially to avoid DCAwareRoundRobinPolicy to pollute the console).

A few general remarks:

maybe we could rename CCMTestMode to something more explicit; I think something like @CreateCCM(PER_METHOD) reads more nicely.
it's not clear to me when you would extend CCMTestsSupport vs "mix it in" like it's done in ControlConnectionTest.
on a related note, couldn't we use TestListener to process the annotations and avoid having to reference CCMTestsSupport altogether (except for the provider methods of course)?

maybe we could rename CCMTestMode to something more explicit; I think something like @CreateCCM(PER_METHOD) reads more nicely.
Agreed, done.

it's not clear to me when you would extend CCMTestsSupport vs "mix it in" like it's done in ControlConnectionTest.

The mixin mode would be useful if we one day create the equivalent functionality for Scassandra tests, in which case some tests could mix both CCM and Scassandra clusters. I this case, inheriting from one or the other would not be ideal.

on a related note, couldn't we use TestListener to process the annotations and avoid having to reference CCMTestsSupport altogether (except for the provider methods of course)?

I'll give it a try. I initially discarded the idea because a) the interface is cumbersome and b) we would still need an instance of CCMTestsSupport to benefit from the helper methods.

Big :+1: on the register concept, reduces putting try/finallys all over the place to make sure the cluster gets close.

Squashed commits.

very nice!  I like the recent change to removing the ccmBridgeProvider field in CCMConfig in favor of pushing the methods of CCMBridge.builder into the annotation.   Assuming everything is passing in CI, I am :+1: on this.

I have a couple commits to fix some intermittently failing tests that I thought would be good to cherry-pick in if you agree (otherwise can wait until later):
8da0b39 - Reintroduce sleep to password-based tests, since apparently they are needing for 1.2.19 (I had thought that it had been fixed by 1.2.19 since I had trouble reproducing, but I must be wrong).
bbeea1c - Change RefreshConnectedHostTest#should_refresh_single_connected_host to start 2 nodes instead of 3 (and stopping node3), and bootstrap node 3 in when needed (instead of starting it again).  Saves some time and makes the test pass more consistently in it's mock validation.

Thanks @tolbertam I cherry-picked the suggested commits.

We're almost done with this pull request and aiming to have repeatable, successful builds.
A summary of recent changes:

new ConditionChecker to periodically/asynchronously evaluate a condition. Can replace Thread.sleep() and Mockito.verify(... , timeout()) in which cases it provides a more deterministic outcome.
Using ConditionChecker to evaluate if nodes are up or down, see here and here.
Some tests that use ConditionChecker: HostConnectionPoolTest, QueryOptionsTest, AbstractPoliciesTest, AbstractReconnectionHandlerTest.
There is one change to production code in AbstractReconnectionHandler.

Squashed commits and rebased.


New build process

Switch from a Makefile to a docker-based build environment. We no longer need a mac to build hologram, and can use docker to cross-compile for both osx and linux.
Container also includes (almost) everything needed to develop hologram, so you just need to do "./hologram.sh console" from a repo containing hologram, and you can compile/test hologram without even needing to have go installed.
Fixes https://github.com/AdRoll/hologram/issues/23

To elaborate a bit: I've already packaged up hologram for nix and that has pretty good automation around building "conventional go"-flavored projects. Right now, I'm able to build all of hologram on my Nix/NixOS system without any customization whatsoever, and without using the provided Makefile. Will that change or is this just mostly replacing the Makefile to help people get from 0 to productive quickly?

@copumpkin Using docker will not be mandatory at all, we're trying to make hologram easier to use/build, not harder :)
To build hologram itself, just using the go tool in the traditional way should always be enough (go install github.com/AdRoll/hologram/...). The docker process is just an attempt to lower the barrier of entry for people curious about trying/hacking on hologram (don't need to worry about dependencies, cross-compiling, etc), and it gives us something we can stick on a CI server and have reproducible builds.
But just to be absolutely clear, provided you have the right dependencies installed you're not going to get any different results from building hologram using the go tool.

Sounds awesome :) thanks!
On Friday, March 27, 2015, Fran Garcia<EMAIL_ADDRESS>wrote:

@copumpkin https://github.com/copumpkin Using docker will not be
mandatory at all, we're trying to make hologram easier to use/build, not
harder :)
To build hologram itself, just using the go tool in the traditional way
should always be enough (go install github.com/AdRoll/hologram/...). The
docker process is just an attempt to lower the barrier of entry for people
curious about trying/hacking on hologram (don't need to worry about
dependencies, cross-compiling, etc), and it gives us something we can stick
on a CI server and have reproducible builds.
But just to be absolutely clear, provided you have the right dependencies
installed you're not going to get any different results from building
hologram using the go tool.
—
Reply to this email directly or view it on GitHub
https://github.com/AdRoll/hologram/pull/27#issuecomment-86928336.

Looks good to me. :+1:


Work around write chunk size for TLS streams for PHP < 7.1.4

PHP < 7.1.14 (and PHP < 7.0.18) suffers from a bug when writing big chunks of data over TLS streams at once. We try to work around this by limiting the write chunk size to 8192 bytes for older PHP versions only. This is only a work-around and has a noticable performance penalty on affected versions. Please update your PHP version.
Closes / resolves #105

Wait a moment, typo'd the version, this has been fixed in PHP 7.1.4, not PHP 7.1.14…

Sorry for the confusion, PR updated to reference affected PHP < 7.1.4 now :shipit:
See also https://github.com/reactphp/socket/issues/105 and https://github.com/php/php-src/commit/17e9fc9bfeaf575b25782a42937a56e809155858

:shipit:


[Feature Request] Promptflow can't save some node output when exception happens

Is your feature request related to a problem? Please describe.
At the moment when exception happens from run as a function,  for example, content management policy exception triggered all nodes output are lost:
f = load_flow(source="../../examples/flows/chat/chat-basic/")
f.context.streaming = True
try:
  result = f(
      chat_history=[
          {
              "inputs": {"chat_input": "Hi"},
              "outputs": {"chat_output": "Hello! How can I assist you today?"},
          }
      ],
      question="How are you?",
  )
except WrappedOpenAIError as exc:
  # we lost succeeded node output as well
  pass

answer = ""
# the result will be a generator, iterate it to get the result
for r in result["answer"]:
    answer += r

Describe the solution you'd like
when exception happens can we have some nodes output saved somewhere? for example: node1->node2->node3 when node2 triggers exception we can still have output from node1?
Describe alternatives you've considered
Not sure
Additional context
Not sure

Hi @vhan2kpmg , we currently model flow-as-function feature like a function call. Which means when calling the flow function, no intermedia data will be persisted. We won't change its behavior in near future. I've added a long term tag to track this.


feat req: add rem to px preview

you are so cool, thankyou big bro @voorjaar for this extension, it's best start year work)
but, i caught little flashback )
https://github.com/tailwindlabs/tailwindcss-intellisense/issues/200

Is rem*16 hard to calculate 😂?

@reslear thank you for the idea!! if you feel it, you can try to submit a pr and we go from their. Otherwise this issue is tagged with good first issue, so people you would be willed to help can take this. Please understand core contributors are working on bugs first :)

@voorjaar but i'm about tw number,  4tw-16px-1rem (for example 300px in tw ?) need use https://tailwindcss-calculator.com/


Removed Justin May's keys

In this pull request, I've removed Justin's key from templates/ssh/authorized_keys and his public key from the same directory. The effect of merging this pull request will be to revoke Justin's ssh access.

+1 looks good


Add basic parity check for API endpoints

Context
We want to have confidence that the API endpoints in NPQ reg are returning the same data/order/format as their corresponding endpoints in ECF. In order to do this we will be calling each endpoint as a lead provider and comparing the responses.
As a first pass we want to do this for the statements endpoint
Changes proposed in this pull request

Add ResponseComparison model for parity check

As part of the API parity check we will need to restore the results for each
lead provider/path that we are calling.
Add ResponseComparison model to store the comparison results. If the response
is equal we will clear the response bodies prior to saving to avoid storing
large amounts of data in the database.

Add ParityCheck service

The service will perform API requests against the ECF and NPQ services, storing the results in a ResponseComparison. We use the TokenProvider service to generate tokens at the start of the check and we benchmark the request durations to get an idea of performance between the two services.
Currently we are only testing the statements endpoint.
Comparing/diffing the results will be left to a future PR that adds the UI.
There are no differences reported in the statement endpoints after running in migration.
Guidance for review
Results from run on migration environments:
Migration::ParityCheck::ResponseComparison.any?(&:different?)
=> false

Migration::ParityCheck.new.run!

Migration::ParityCheck::ResponseComparison.all.each_with_object({}) do |comparison, result|
  result[comparison.lead_provider.name] = {
    equal: comparison.equal?,
    ecf_response_time_ms: comparison.ecf_response_time_ms,
    npq_response_time_ms: comparison.npq_response_time_ms,
    response_time_comparison: "#{(comparison.ecf_response_time_ms.to_f / comparison.npq_response_time_ms).round(1)}x faster",
  }
end

{"Ambition Institute"=>
  {:equal=>true,
   :ecf_response_time_ms=>6057,
   :npq_response_time_ms=>175,
   :response_time_comparison=>"34.6x faster"},
 "Church of England"=>
  {:equal=>true,
   :ecf_response_time_ms=>95,
   :npq_response_time_ms=>173,
   :response_time_comparison=>"0.5x faster"},
 "Education Development Trust"=>
  {:equal=>true,
   :ecf_response_time_ms=>109,
   :npq_response_time_ms=>149,
   :response_time_comparison=>"0.7x faster"},
 "Teacher Development Trust"=>
  {:equal=>true,
   :ecf_response_time_ms=>89,
   :npq_response_time_ms=>172,
   :response_time_comparison=>"0.5x faster"},
 "Teach First"=>
  {:equal=>true,
   :ecf_response_time_ms=>102,
   :npq_response_time_ms=>150,
   :response_time_comparison=>"0.7x faster"},
 "LLSE"=>
  {:equal=>true,
   :ecf_response_time_ms=>114,
   :npq_response_time_ms=>156,
   :response_time_comparison=>"0.7x faster"},
 "National Institute of Teaching"=>
  {:equal=>true,
   :ecf_response_time_ms=>95,
   :npq_response_time_ms=>158,
   :response_time_comparison=>"0.6x faster"},
 "School-Led Network"=>
  {:equal=>true,
   :ecf_response_time_ms=>98,
   :npq_response_time_ms=>134,
   :response_time_comparison=>"0.7x faster"},
 "Best Practice Network"=>
  {:equal=>true,
   :ecf_response_time_ms=>95,
   :npq_response_time_ms=>143,
   :response_time_comparison=>"0.7x faster"},
 "University College London (UCL) Institute of Education"=>
  {:equal=>true,
   :ecf_response_time_ms=>89,
   :npq_response_time_ms=>145,
   :response_time_comparison=>"0.6x faster"}}

Graphed, courtesy of ChatGPT:

Great work 👍
Ambition being so slow, is that a cold start problem?

I think its actually the lazy loading of tokens which happens in the first request; I'll put in a fix for that as its skewing the results big time 😅


Optional authFields for JWT payload.

A project that I'm currently working on for school uses this library (so thank you for that).
However, we needed more data in the JWT payload (specifically a role). So I added some code to account for that.
Putting it simply, if you want a field to be sent in the JWT payload, add it to the authFields when creating the user, like so:
{
    "email"<EMAIL_ADDRESS>    "password": "password",
    "role": "admin",
    "age": 28,
    "authFields": ["role", "age"]
}

The accessToken returned will contain the email, sub (id), and any other fields that are in the authFields array.
And as a bonus, its retroactive. So any existing users in the db.json that you would like the JWT payload to return more fields on, just add the authFields array to it, and it'll work.

Exactly what I've been looking for!

Idea: would it be possible to extends json-server.json configuration file?

Hi, people! My simple solution to return record from user table. changed user.js a little for this: in create and login function
return new Promise((resolve, reject) => {
    let usr = JSON.parse(JSON.stringify(user));
    delete usr.password;
    jwt.sign({ email, user: usr }, constants_1.JWT_SECRET_KEY, { expiresIn: constants_1.JWT_EXPIRES_IN, subject: String(user.id)      }, (error, idToken) => {...


Support for Tableau Linux Server

Greetings,
First and foremost I want to thank you for this awesome project, it works flawlessly for Tableau Desktop.
What I'm trying to do however is to install the connector on Tableau Linux Server following the steps from: https://tableau.github.io/connector-plugin-sdk/docs/run-taco#set-up-tableau-server
The ClickHouse ODBC driver is in place and works fine, I can connect to clickhouse and run queries.
The problem seems to appear when I'm trying to load the clickhouse tableau connector in Tableau Linux Server.
Some of the relevant log lines I found:
 {"ts":"2021-06-29T08:53:58.939","pid":1809,"tid":"38f3","sev":"warn","req":"YNq1dq8NLwBjJbuNh2ZvqgAAAF8","sess":"-","site":"-","user":"-","k":"excp","e":{"excp-error-code":"0x09DF5C3F","excp-source":"Client","excp-status-code":"FAILED_PRECONDITION"},"v":{"class":"clickhouse_odbc","dse-type":"DataSourceClassMissing","excp-msg":"Tableau doesn't recognize the data source type 'clickhouse_odbc'. It might not be available in this version of Tableau, or it might be a connector plugin that's not installed on this system.\n","excp-type":"ConnectivityException","is-bad-request":false,"is-capability-probe-failure":false,"is-local-configuration-error":false,"is-remote-configuration-error":false,"msg":"ConnectivityException::Init"}}
 {"ts":"2021-06-29T08:46:08.112","pid":1779,"tid":"33f2","sev":"error","req":"-","sess":"-","site":"-","user":"-","k":"connector-plugin-error","e":{"excp-error-code":"0x3834CF96","excp-source":"NeedsClassification","excp-status-code":"UNKNOWN"},"v":"Failed to validate /home/cristianc/tableau_connectors/tableau_odbc_connector"}
 {"ts":"2021-06-29T08:46:08.112","pid":1779,"tid":"33f2","sev":"info","req":"-","sess":"-","site":"-","user":"-","k":"connector-plugin","v":"Loading connector plugin /home/cristianc/tableau_connectors/tableau_odbc_connector"}
 {"ts":"2021-06-29T08:46:08.112","pid":1779,"tid":"33f2","sev":"error","req":"-","sess":"-","site":"-","user":"-","k":"connector-plugin-error","e":{"excp-error-code":"0x350ED310","excp-source":"Configuration","excp-status-code":"UNKNOWN"},"v":"Some connector plugins failed to load:"}
 {"ts":"2021-06-29T08:46:08.112","pid":1779,"tid":"33f2","sev":"error","req":"-","sess":"-","site":"-","user":"-","k":"connector-plugin-error","e":{"excp-error-code":"0x9303C451","excp-source":"Configuration","excp-status-code":"UNKNOWN"},"v":"/home/cristianc/tableau_connectors/tableau_odbc_connector failed to load"}

Thanks for letting me know if Tableau Linux Server is supported actually at all and if so if you happened to see this problem before.
All the best,
Cristian

Update: something that worked as a workaround was to package it as a taco file and self sign it then put that to the tableau linux server and add my certificate to the allowed list.

Update: something that worked as a workaround was to package it as a taco file and self sign it then put that to the tableau linux server and add my certificate to the allowed list.

Hi cristianc-ty,
could you please share the steps for the workaround you mentioned?
Thanks in advance!
JC

I followed the steps from https://tableau.github.io/connector-plugin-sdk/docs/package-sign to build a self signed taco file, added my public key to the tableau trust store with "keytool -importcert -file your_public_cert.cert -keystore /opt/tableau/tableau_server/packages/repository.20212.21.0610.0336/jre/lib/security/cacerts -alias your_alias" then placed the taco file to "/var/opt/tableau/tableau_server/data/tabsvc/vizqlserver/Connectors/clickhouse_odbc.taco" and restarted the server with "tsm restart"

Thank you cristianc-ty!
I will give this a try and see if it works. I will post back once I have the results.
Thanks again!
jc

@cristianc-ty @jorgecabrera85
its strange that Server was not load connector from folder directly.
Very soon this connector will be published in Tableau Gallery of TACO package and you dont need to do this workaround.
Stay tuned.


fix(kpop): stop document click event propagation only when event is about to hide popper

Summary
This fixes the issue where other document click event listeners were not being fired because the stopPropagation() was always being called no matter what was the actual action of the click.
Most UI libraries use document-bound click listeners for execution optimization reasons, and this behavior caused them to not work anymore.
stopPropagation() should only be called when the click event is hiding the popper.
PR Checklist

[x] Does not introduce dependencies
[x] Functional: all changes do not break existing APIs and if so, bump major version.
[x] Tests pass: check the output of yarn test
[x] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[x] Framework style: abides by the essential rules in Vue's style guide
[x] Cleanliness: does not have formatting issues, unused code (e.g., console.logs, debugger), or leftover comments
[ ] Docs: includes a technically accurate README, uses JSDOC where appropriate

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[#152231079] Add new backing services

What
Added Redis and Elasticsearch to list of available backing services.
How to review
Describe the steps required to test the changes.

Preview the content locally (see README) and check that it renders as expected.
Manually check that any removed or renamed anchor tags are not in use (linkchecker doesn't do this).
Check that the content is consistent with the story https://www.pivotaltracker.com/story/show/152231079 and the google doc https://docs.google.com/document/d/1EbuS_nWhj9PLPJ7EKGjxbooms39x7j9j_YDFtvYD0kY/edit

Who can review
Anyone but me or @samcrang
Before merging
Please squash the commits

@tomskerous would you be able to approve please? Andras has reviewed and approved


clusterloader2: Make sure the latency is not a negtive value

fix: https://github.com/kubernetes/perf-tests/issues/1307
Signed-off-by: Dave Chen<EMAIL_ADDRESS>

/cc @wojtek-t

/lgtm
/approve
Thanks!

/lgtm
Thanks!


Unable to use cosmos mongo api for form.io

https://github.com/formio/formio is a popular (501 ⭐) node application that allows for the creation and management of web forms and submissions. It uses mongoose as an ORM with mongodb as a backend.
When configuring form.io to use cosmos mongo api, the application fails when attempting to list collections...
/**
 * Test to see if the application has been installed. Install if not.
 */
var checkInstall = function(next) {
  formio.util.log('Checking for db install.');
  db.listCollections().toArray().then(function(collections) {
    debug.db('Collections found: ' + collections.length);

https://github.com/formio/formio/blob/01501250a667eef0a445031d8bd70beebb887ec6/src/db/index.js#L151
Repro steps:

git clone https://github.com/formio/formio
update connection in /config/default.json with cosmos connection string
npm i
npm start

Issue with formio: https://github.com/formio/formio/issues/539

I had an issue when using Cosmos with Form.io after the version on Mongoose was updated. There was a change in Mongoose where it no longer liked the auto-generated password generated by Cosmos resulting in an authentication error. E.g. the auto-generated password might look something like this:
6QupMFwUEdUop5pF4KdTwiPSrhmELZ5btAaVxTHGrcUAEQKN7Bnn3p59RiJi5pTa5ixRFoA2XXjstMoFLB0byQ==
To fix the issue, the "==" needs to be encoded and replaced with "%3D%3D" resulting a password that looks like this:
6QupMFwUEdUop5pF4KdTwiPSrhmELZ5btAaVxTHGrcUAEQKN7Bnn3p59RiJi5pTa5ixRFoA2XXjstMoFLB0byQ%3D%3D

Thanks a bunch @lbcgitadmin, this saved us a ton of time managing mongo instances.
URL Encoding the key worked great!
here's a relevant snippet of the formio config.
{
  "port": 3001,
  "appPort": 8080,
  "host": "localhost:3001",
  "protocol": "http",
  "domain": "http://localhost:3001",
  "basePath": "",
  "mongo": "mongodb://mongodb01:8v<snip>tA%3D%3D@mongodb01.documents.azure.com:10255/formio?ssl=true",
  "mongoSecret": "",


Quicker way how to setup all the variables?

I have a file that is reguarly updated so that new data are supplied. I from time to time take this file, upload it to raw, manually select graph type, all the dimensions and also width, height, radius on the chart options itselft.
This is quite time consuming and prevents me from me automating the process.
It would be great that such metadata would be stored somewhere...
Also what came on my mind - if the definition was part of the input file, it might be parsed and used.
Besides that I like raw a lot thank you for your effort!

in v2 you can now export/import the project


Security configuration for Glue crawler

Describe the bug
Glue crawlers do not have any security configuration attached which is flagged by checkov as FAILURE with the error message below.
CheckID		: CKV_AWS_195
CheckName	: Ensure Glue component has a security configuration associated
File		: /dataall-dataset-bphz8d77.yaml:636-672
Resource	: AWS::Glue::Crawler.dataalld1bphz8d77crawler
Guideline	: CKV_AWS_195
How to Reproduce
Run a checkov scan on the dataset template. The scan report will contain the entry mentioned above in the description.
Expected behavior
Glue crawlers should have a security configuration.
Your project
No response
Screenshots
No response
OS
Mac
Python version
3.10
AWS data.all version
2.5
Additional context
No response

Hi @mourya-33 , thanks for the issue. Security enhancements are always welcome. Do you plan to work on this issue?

Closing this issue as complete


Fixed build results page on firefox

Fixes #2261

@agjohnson: My feeling is that the fix, while imperfect, at least makes the site usable on Firefox and Chrome, whereas currently it's only usable on Chrome. Would you consider accepting this fix as a temporary measure, and then we could create a follow-up issue to address the aesthetic issue in Chrome?

Digging into this a little deeper, this margin: -16px really feels like a hack for defective rendering in Chrome.

Indeed, see the attached #2261 for more background here

Closing this PR, there is a new PR open addressing the review changes above.


[tagger/tagstore] Add DCA implementation that reduces mem usage

What does this PR do?
This PR reduces the memory used by the tagger when running in the Cluster Agent.
The tagger stores the tags by source and also stores the final result of aggregating them according to the priorities defined. This is a valid use case for the node agent because a single tagger entity can be reported by multiple sources. For example, a container might be reported by containerd but also by the Kubelet. Keeping the tags by source is used to merge them applying the priorities defined. Also agent tagger-list and some telemetry metrics show the tag source.
The case of the Cluster Agent is a bit different because tags only come from a single workloadmeta collector (kubeapiserver). That means that a single entity is not reported by multiple sources. That's why in this case we can reduce the memory used by not storing the tags by source.
This PR achieves that goal by defining a EntityTags interface that is responsible for storing the tags for a tagger entity and provides two implementations, one that handles the case of multiple sources (current implementation) and another one that assumes a single source (new optimization for the DCA).
This memory optimization is important in the Cluster Agent when the option to collect Kubernetes tags is enabled (cluster_agent.collect_kubernetes_tags) because in large clusters  the memory used to store the pod tags can be quite high.
Describe how to test/QA your changes
For the DCA try with the option to collect Kubernetes tags enabled (datadog.clusterTagger.collectKubernetesTags option in the helm chart). Check in our internal clusters using profiles that the memory used by the tagger has decreased. Do also a quick verification of agent tagger-list.
For the Agent, a sanity check should be enough. Deploy the agent and check with agent tagger-list that tags are correct.

LGTM 🙇

/merge


Some information on Data security when using the Azure hosted runtime (i.e. Default Azure IR) would be good

I'm interested in having some more insight into how the Default Azure IR are hosted and what prevents another Azure customer from 'seeing' my data? So, for instance:

Are these shared instances of the IRT or are they dedicated?
If they are shared, what prevents another Azure customer from getting access to my data? Do you, for instance use customer specific keys to encrypt the different data flows?
If they are dedicated, do these run for instance in containers and are these deleted with the ADF instance (so never reused for another customer)?
Is the data never stored on the IRT instance?
etc.
So this is not a list of specific questions to answer, I'm looking for a description on how the Default Azure IR are secured as they are used in a multi-tenant environment. Which I think is missing from the documentation.

Kind regards,
Dennis

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

ID: 567118bc-05db-cb9d-d14f-faf835da048a
Version Independent ID: 9aaa1635-bb8c-07b4-ebc5-55baeb98149c
Content: Security considerations in Azure Data Factory
Content Source: articles/data-factory/data-movement-security-considerations.md
Service: data-factory
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@Nimleth
We have pools running in different regions and on request, certain nodes are allocated to customers (dedicated) for that job. And then released back to the pool after context cleanup. In the case of Data flow, the cluster would be job cluster and gets destroyed on execution.
No data is persisted on clusters.
Azure IR is designed for multi-tenant use and we provide the precise context isolation per job activity execution.
Hope this helps?

@nabhishek
Hi Narain, thank you. This wil  suffice.
Rgds,
Dennis


When using F#, OData incorrectly interprets an int as a long

Related to StackOverflow question: https://stackoverflow.com/questions/44252103/imobileservicetablequery-generates-odata-with-the-wrong-type
Given the following types:
type DtoSource =
    | CreatedInApp
    | SynchronisedFromServer

type EntityDto() =
    [<JsonProperty("id")>] member val Id = String.Empty with get, set
    [<JsonProperty("version"); AzureVersion>] member val Version = Unchecked.defaultof<String> with get, set
    [<JsonProperty("createdAt")>] member val CreatedUtc = DateTime.MinValue with get, set
    [<JsonProperty("updatedAt")>] member val UpdatedUtc = DateTime.MinValue with get, set
    [<JsonProperty("deleted")>] member val Deleted = false with get, set
    [<JsonIgnore>] member val Source = SynchronisedFromServer with get, set

type EventOrganiserVenueDto() =
    inherit EntityDto()
    [<JsonProperty("venueNameKey")>] member val VenueNameKey = String.Empty with get, set
    [<JsonProperty("venueNameText")>] member val VenueNameText = String.Empty with get, set
    [<JsonProperty("subheadingKey")>] member val SubheadingKey = String.Empty with get, set
    [<JsonProperty("subheadingText")>] member val SubheadingText = String.Empty with get, set
    [<JsonProperty("assignedById")>] member val AssignedById = 0 with get, set
    [<JsonProperty("location")>] member val Location = new LocationDto() with get, set
    [<JsonProperty("eventOrganiserId")>] member val EventOrganiserId = 0 with get, set
    [<JsonProperty("imageUrl")>] member val ImageUrl = String.Empty with get, set
    [<JsonProperty("mapUrl")>] member val MapUrl = String.Empty with get, set
    [<JsonProperty("websiteUrl")>] member val WebsiteUrl = String.Empty with get, set
    [<JsonProperty("ianaTimeZoneId")>] member val IanaTimeZoneId = String.Empty with get, set
    [<JsonProperty("googlePlaceId")>] member val GooglePlaceId = String.Empty with get, set
    [<JsonProperty("cancelledById")>] member val CancelledById = 0 with get, set
    [<JsonProperty("addressFloorLevel")>] member val AddressFloorLevel = String.Empty with get, set
    [<JsonProperty("addressBuilding")>] member val AddressBuilding = String.Empty with get, set
    [<JsonProperty("addressLine1")>] member val AddressLine1 = String.Empty with get, set
    [<JsonProperty("addressLine2")>] member val AddressLine2 = String.Empty with get, set
    [<JsonProperty("addressCity")>] member val AddressCity = String.Empty with get, set
    [<JsonIgnore>] member this.AddressSummary with get() = sprintf "%s, %s" this.AddressLine1 this.AddressCity
    [<JsonProperty("addressStateProvince")>] member val AddressStateProvince = String.Empty with get, set
    [<JsonProperty("addressPostalCode")>] member val AddressPostalCode = String.Empty with get, set
    [<JsonProperty("addressCountryIso3Code")>] member val AddressCountryIso3Code = String.Empty with get, set

Note that the EventOrganiserId member is an int rather than a long (int64) or a uint32. However, the following lines:
let x = MobileServiceTableQueryDescription.Parse("EventOrganiserVenueDto", sprintf "$filter=eventOrganiserId%%20eq%%20%i" eventOrganiserId)
let y = xToODataString()

generate an output of $filter=(eventOrganiserId eq 2L). The int is being misinterpreted.
I have tried working around this using the WithParameters function:
let query = table.CreateQuery().WithParameters(dict ["$filter", sprintf "(EventOrganiserId%%20eq%%20%i)" eventOrganiserId])

However, for reasons I don't yet understand, the subsequent PullAsync operation fails to connect to the server. If I change the name of the parameter from $filter to filter, the PullAsync operation hits the server and pulls back all of the records in the set.

@SpiegelSoft Thanks for using Azure Mobile Apps. Please read the Readme section on this repo which talks about the future of Azure Mobile Apps. Since this issue is almost a year old, I'll close this issue for now as we are not adding new features, but feel free to ask us questions if you have any. Thanks!


Adds the payment method attribute into Plan object and changes dependencies.

This PR adds the paymentMethod attribute into the Plan Object.

Close this issue since doesn't have approval yet

Close this issue since doesn't have approval yet


add delete protection

to resolve security hub finding on network firewall delete protection

Dunno how to approve in GitHub. Approved! Can go ahead and merge


Change banner character colour

Banner before:

Banner now:

You are definitely on the right team to have noticed this and to care enough to change it!

Where's the changeLog entry ? 😄

@abhimanyugupta07 Where's the changeLog entry ? 😄

Should I have one? If so, what would should it say? 😆


Move "new to DVC" text from setup to welcome view

Simplifies setup "DVC is Incompatible" and "DVC is unavailable" text content by moving welcome-related text to the welcome view. This also would help with the setup "welcome" text possibly be misleading.
main

PR

Resolves https://github.com/iterative/vscode-dvc/pull/3993#issuecomment-1569254205

Thanks @julieg18, good update.
A few comments:

demo project - let's use the example-get-started-experiments for this please. Overall, I think our demo project is not a good fit for external users to try, so we should not be using it much.
auto-install / auto-installed - duplicate message. Let's simplify it further please. " ... installation types. It also can help to install needed packages ..."


[FEATURE] Create Post Component

Problem
Need to create profile feeds.
User Story(s):
As a user, I want to have a robust psot, so that I can reference profiles, follow, responds, likve reporst all directly form the component.
Description
Create a post component for social.near posts
Acceptance Criteria

[ ] create layout
[ ] pull from near social api to display name, .near and link to profile (potlock profile)
[ ] add markdown support
[ ] take in props posts and accountID and blockheights(can pass through URL)
[ ] add like post
[ ] and repost
[ ] display if post is a repost
[ ] able to reply to post if logged in
[ ] in reply show preview of logged in user near social profile
[ ] like replies
Future

Limitations

it will be hard to generate feeds, may need near social api
these posts will be udpated so things like embedded posts wont work, need to show some type of not supported

Resources

This could really help ecosystem if we build stand alone feeds as a nextjs app
Example of Post Feed https://near.social/mob.near/widget/MainPage.N.Post.Page

@codingshot since this is part of feeds which is larger feature, let's leave out of MVP and save for later in Q1?


Missing repository

I have been trying to build a basic image using your instructions but it looks like one of the required repositories has moved. I have tried looking for it but no luck so far.
Darren B.
ERROR: Logfile of failure stored in: /home/darren/yockto/build/tmp/work/rk3188-poky-linux-gnueabi/linux-rockchip-3.0-rk3188/1.0-r0/temp/log.do_fetch.13977
Log data follows:
| DEBUG: Executing python function do_fetch
| DEBUG: Executing python function base_do_fetch
| DEBUG: Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote git://github.com/linux-rockchip/rockchip-3.0.git refs/heads/rockchip-3.0 refs/tags/rockchip-3.0^{}
| DEBUG: Running export PATH="/home/darren/yockto/poky/scripts:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi:/home/darren/yockto/build/tmp/sysroots/rk3188/usr/bin/crossscripts:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/sbin:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/bin:/home/darren/yockto/poky/scripts:/home/darren/yockto/poky/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"; export HOME="/home/darren"; git -c core.fsyncobjectfiles=0 ls-remote git://github.com/linux-rockchip/rockchip-3.0.git refs/heads/rockchip-3.0 refs/tags/rockchip-3.0^{}
| DEBUG: Python function base_do_fetch finished
| DEBUG: Python function do_fetch finished
| ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:
| fatal: remote error:
|   Repository not found.

Please no longer use this repository, the project has moved to https://github.com/linux-rockchip/meta-rockchip . See http://layers.openembedded.org/layerindex/branch/master/layers/

Could you reopen this ticket in the project page above please ? thanks

Hi
The new repository does not seem to allow issues to be raised.
However I did a build with the new repository and the same error occured.
Happy to raise a ticket, but I can't seem to
again the error was
ERROR: Function failed: Fetcher failure: Fetch command failed with exit
code 128, output:
fatal: remote error:
Repository not found.
ERROR: Logfile of failure stored in:
/home/darren/yockto/build/tmp/work/rk3188-poky-linux-gnueabi/linux-rockchip-3.0-rk3188/1.0-r0/temp/log.do_fetch.14468
Log data follows:
| DEBUG: Executing python function do_fetch
| DEBUG: Executing python function base_do_fetch
| DEBUG: Fetcher accessed the network with the command git -c
core.fsyncobjectfiles=0 ls-remote
git://github.com/linux-rockchip/rockchip-3.0.git refs/heads/rockchip-3.0
refs/tags/rockchip-3.0^{}
| DEBUG: Running export
PATH="/home/darren/yockto/poky/scripts:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi:/home/darren/yockto/build/tmp/sysroots/rk3188/usr/bin/crossscripts:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/sbin:/home/darren/yockto/build/tmp/sysroots/x86_64-linux/bin:/home/darren/yockto/poky/scripts:/home/darren/yockto/poky/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games";
export HOME="/home/darren"; git -c core.fsyncobjectfiles=0 ls-remote
git://github.com/linux-rockchip/rockchip-3.0.git refs/heads/rockchip-3.0
refs/tags/rockchip-3.0^{}
| DEBUG: Python function base_do_fetch finished
| DEBUG: Python function do_fetch finished
| ERROR: Function failed: Fetcher failure: Fetch command failed with
exit code 128, output:
| fatal: remote error:
|   Repository not found.
|
On 6/05/2015 8:50 PM, Romain Perier wrote:

Could you reopen this ticket in the project page above please ? thanks
—
Reply to this email directly or view it on GitHub
https://github.com/neo-technologies/meta-rockchip/issues/10#issuecomment-99438810.

I have opened an issue on the other repository.
it seems that git://github.com/linux-rockchip/rockchip-3.0.git has been merged / moved somewhere else, haven't found where yet.
Thanks

Isn't it linux-rockchip repo?

It is indeed


Permission denied while building from rake

When attempting to build from rake as described on the README.md I get the following error :
Cloning into lib/httpmachine...
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Clone of 'git@github.com:bvanderveen/httpmachine.git' into submodule path 'lib/httpmachine' failed
It also failed when I tried replacing the url in .gitmodules by https://github.com/bvanderveen/httpmachine.git.
EDIT : I forgot to edit .config in .git to change the submodule url there to https://github.com/kayak/kayak.git
That made it give a different error message :
fatal: reference is not a tree: 5747f5e34db18a5461581728d3618b5c3599a4d3
Unable to checkout '5747f5e34db18a5461581728d3618b5c3599a4d3' in submodule path 'lib/httpmachine'
For some reason I still have issues with the rake file, however I was able to init and update the submodule though git bash

Could you make a pull request which adds that suggestion to the readme?

Done. I am fairly new to github as you may have noticed.
Just to clear up any misunderstanding, the problem I had when building was with github.username/github.token not being set rather than the ssh keys not being added to github


Installation failed in php 7.2

I have install package via composer in php 7.2 , but i Installation failed .
`Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for league/flysystem-azure-blob-storage ^0.1.1 -> satisfiable by league/flysystem-azure-blob-storage[0.1.1].
- league/flysystem-azure-blob-storage 0.1.1 requires phpunit/phpunit ^5.7 -> satisfiable by phpunit/phpunit[5.7.0, 5.7.1, 5.7.10, 5.7.11, 5.7.12, 5.7.13, 5.7.14, 5.7.15, 5.7.16, 5.7.17, 5.7.18, 5.7.19, 5.7.2, 5.7.20, 5.7.21, 5.7.22, 5.7.23, 5.7.24, 5.7.25, 5.7.26, 5.7.27, 5.7.3, 5.7.4, 5.7.5, 5.7.6, 5.7.7, 5.7.8, 5.7.9, 5.7.x-dev] but these conflict with your requirements or minimum-stability.
Installation failed, reverting ./composer.json to its original content.`

this issue is now fixt in commit https://github.com/thephpleague/flysystem-azure-blob-storage/commit/fc1965e3ca5172cfcc6c349be948ce17c3740c96 and in versio 0.1.2 https://github.com/thephpleague/flysystem-azure-blob-storage/releases/tag/0.1.2


Add fileds and support more Kotlin syntax

Add fields and support more Kotlin syntax.

The changes to grammar.js look good to me. But I don't see fields added to unit tests, so I guess they're failing?

The changes to grammar.js look good to me. But I don't see fields added to unit tests, so I guess they're failing?

@CamilleTeruel , all unit tests are passed, they don't check field actually, just check the real s-expression.
This's a unit test output example, you can ignore the failure message (I'm debugging the Generic support now)
➜  tree-sitter-kotlin git:(master) /Users/qintianhuan/merico/tree-sitter-demolang/node_modules/.bin/tree-sitter test
comments:
  ✓ Comments
classes:
  ✓ Classes
  ✓ Class with methods
  ✓ Generic class
  ✓ Class with methods and expressions
  ✓ Class with modifiers
  ✓ Objects
  ✓ Primary constructors
  ✓ Inheritance
  ✓ Properties
  ✓ Constructor delegation calls
  ✓ Enum classes
literals:
  ✓ Simple identifiers
  ✓ Boolean literals
  ✓ String literals
  ✓ String interpolation
  ✓ Integer literals
  ✓ Real literals
functions:
  ✓ Top-level functions
  ✗ Generic functions
  ✓ Functions with parameters
  ✓ Functions with return types
statements:
  ✓ For statements
types:
  ✓ Type references
  ✓ Nested types
  ✓ Deeply nested types
  ✓ Generic wildcard types
  ✓ Generic parameterized types
  ✓ Function types
  ✓ Function types with multiple parameters
  ✓ Function types with named parameters
  ✓ Function types with receiver
expressions:
  ✓ Multiplication expression
  ✓ Function calls
source-files:
  ✓ File annotations

1 failure:

expected / actual

  1. Generic functions:
    (source_file (ERROR (UNEXPECTED 'T')) (function_declaration (type_parameters (type_parameter (type_identifier))) (simple_identifier) (function_body)))

My bad, I thought they were checked when omitted.
I think its good to add them anyway to document and double-check.

My bad, I thought they were checked when omitted.
I think its good to add them anyway to document and double-check.

I'll add them tomorrow with a new commit which contains more syntax support 😄

LGTM