Need NodeJS Version Communications & Plan

We've gotten bit a few times this week, and earlier this year, by a lack of communication around the NodeJS plans for the tasks. Is there a document somewhere describing the roadmap and expectations of what versions of NodeJS the pipeline agent tasks are expected to be able to use? Also specifically what versions it shouldn't be using so we can set reasonable policies on our agent's endpoint monitoring to alert (or not) on EOL versions of NodeJS.

Is there a doc for extension developers too? There are a number of constraints we need to work with to support older TFS server versions that are still out there in the field and that don't ship with Node16 handlers.
I see in the tasks updated so far that both the Node and Node16 handlers point to the same js file, but if they use any node16 features, I suspect they'll break on Node 6 and Node 8 and Node 10 that shipped with older TFS and Azure DevOps Servers.
I tried compiling some of my extensions to 8, 10 and 16, but then the file size for the extension becomes too large for the marketplace, and I can't publish the extension.
I also see the MinAgentVersion being raised by quite a bit, that means none of these tasks can be installed into Azure DevOps Server 2020 or below to fix bugs it looks like.

I just noticed that some details are on the Azure DevOps Roadmap page here. Looks like they should all be Node 16 relatively soon actually. Though there's still the challenge of figuring out what other versions the rest of our extensions are actually using. Some flag in the runner to restrict or warn on older versions would be really nice.

What's missing in the documentation is how to properly handle targeting multiple TFS/ADS and Azure DevOps versions.
If I need to make changes to the code or pull in different dependency versions for say TFS 2018 support, should I package 2 folders with 2 cross compiled versions of the task each with their own node_modules? Cause in that case I'm likely going to hit the 20MB size limit for extensions.
Or should I add a new major version of the task and leave other versions on the last major version? This will also consume space in the extension zip.
I can't split the extension in a node10 and a node16 version without breaking my consumers since the taskid and she task name are forced to change and people will need to change all their yml files and ui pipelines.
I have extensions that still support TFS 2015 all the way up to ADS 2022 and since the marketplace doesn't provide any metrics I can't easily deprecate some of them.
Ideally the team would ship an update for old servers versions that contains the new agent and provide official support on that. It's a security patch, depending on how you look at it.

A blog post for task authors is coming up soon.


How to use a  row picture to validate the model?

Thank for your outstanding work. I have finished training the model, how do I validate the model using the original images or videos?  Can you give me  some advice?

Hi @Aangss
Thank you for your interest in DEVIANT.

I have finished training the model, how do I validate the model using the original images or videos? Can you give me some advice?

My hunch is you wanted to be sure if your model has converged well. I could think of following ways:

AP: If you have GT available, consider getting AP numbers similar to KITTI, Waymo or nuScenes dataset.
Depth: As stated in the paper, depth remains the hardest parameter to estimate for monocular 3D detection task. You could report MAE error on the TP boxes (boxes which has 2D IoU > 0.7 with the GT similar to Tab. 6 of our paper)
Qualitative: You could use our visualization scripts to plot the boxes in frontal view and BEV on random images of the dataset.

Thank for your answer. But I'd like to verify the model using pictures I've taken myself,can I do that?   Or if I use the original photo or video, does the photo/video format need to be changed?

I'd like to verify the model using pictures I've taken myself,can I do that? Or if I use the original photo or video, does the photo/video format need to be changed?

You can do that but that requires the following:

Prepare your dataset in the  following order:

├── data
│      ├── Your_dataset
│      │      ├── ImageSets
│      │      └── testing
│      │            ├── calib
│      │            └── image_2

The image_2 is your images in .png format.

The calib contains camera calibration (intrinsics) as the following line: P2 as 1x12 matrix. If you do not have camera calibration, use the following approximate COCO intrinsics from height h and width w of your image.

import numpy as np
def get_intrinsics(h, w):
    intrinsic_matrix = np.zeros((3,4))
    f = 2 * h
    intrinsic_matrix[0, 0] = f
    intrinsic_matrix[1, 1] = f
    intrinsic_matrix[0, 2] = w / 2.0
    intrinsic_matrix[1, 2] = h / 2.0
    intrinsic_matrix[2, 2] = 1

    return intrinsic_matrix.flatten().tolist()

Take your trained model and run the testing script.
Finally run the visualization script plot/plot_qualitative_output.py. If you want videos, combine the frames together.

@abhi1kumar Thanks for your advice,I will try it.

@abhi1kumar  I'm so sorry to bother you. I completed the above steps, but the visualization seems to be bad,can you give me some advice?

Let us do it step by step. Can you show share the screenshot of the directory structure and paste the content of your calibration file here?

Okay. I have pasted the information as follows

This is the contents of the 000001 txt file:
P0: 3.400000000e+03 0.000000000e+00 6.380000000e+02 0.000000000e+00 0.000000000e+00 3.400000000e+03 8.510000000e+02 0.000000000e+00 0.000000000e+00 0.000000000e+00 1.000000000e+00 0.000000000e+00
P1: 3.400000000e+03 0.000000000e+00 6.380000000e+02 0.000000000e+00 0.000000000e+00 3.400000000e+03 8.510000000e+02 0.000000000e+00 0.000000000e+00 0.000000000e+00 1.000000000e+00 0.000000000e+00
P2: 3.400000000e+03 0.000000000e+00 6.380000000e+02 0.000000000e+00 0.000000000e+00 3.400000000e+03 8.510000000e+02 0.000000000e+00 0.000000000e+00 0.000000000e+00 1.000000000e+00 0.000000000e+00
P3: 3.400000000e+03 0.000000000e+00 6.380000000e+02 0.000000000e+00 0.000000000e+00 3.400000000e+03 8.510000000e+02 0.000000000e+00 0.000000000e+00 0.000000000e+00 1.000000000e+00 0.000000000e+00
These photos were all taken by ipone13,and P0-P3 were all converted to SciTech by generating a 12×1 matrix from the code you provided!

Thank you. The calibration files look OK to me. I believe the image resolution is hxw = 680x1276. Let us say you want to run over the Waymo (run_1051) model.

Change the input resolution in the config from 768x512 to 960x512 (to maintain the same aspect ratio).
Finally type the following:

CUDA_VISIBLE_DEVICES=0 python -u tools/train_val.py --config=experiments/run_1051.yaml --resume_model output/run_1051/checkpoints/checkpoint_epoch_30.pth -e

You should see some text files in the output/run_1051 directory. These should be our predictions. I hope these are non-empty
Finally, use the visualization scripts.

If I want to run a KITTI model, is that the same thing?  I've only used kitti before.

If I want to run a KITTI model, is that the same thing? I've only used kitti before.
The KITTI model is trained on 3.7k images, while the waymo ones are trained on >50k images (which may make them more robust). You could try the waymo model first. Hopefully, my waymo dataloader does not break.

Okay,I will try it.  Need to change the dataset' name in config? Having just started first grade, your paper was the first one I read and I want to reproduce it to the best of my ability.

Okay,I will try it.

Please let us know if you could run inference on other dataset images.

Need to change the dataset' name in config?

Check the paths and see if the images, calibs are being read.

Having just started first grade, your paper was the first one I read and I want to reproduce it to the best of my ability.

You should start with our released KITTI pretrained-models on KITTI and see if you could reproduce the KITTI numbers on your end. Then, move to cross-dataset experiment of KITTI model on nuScenes. And finally to your own custom dataset.

Sorry, I wasn't able to test the model on my own dataset image, I think some of my paths weren't modified correctly causing it to still be a KITTI dataset when performing the inference process. Can you tell me exactly where to modify the paths to put into my own dataset? Thanks.

Change the eval_dataset in the following KITTI config: Change this line to YSS_data
Then, see if the code goes to the following lines of KITTI dataloader
Before doing this part, were you able to reproduce our KITTI numbers with the pre-trained model on your end? That will indicate that you have setup the environment correctly.

I reproduced the pre-trained model with some of the KITTI images, I think the environment should be fine.
But when I run the test script, the following error is reported
2023-11-09 10:01:30,021   INFO  ==> Loading from checkpoint 'output/run_221/checkpoints/checkpoint_epoch_140.pth'
2023-11-09 10:01:32,223   INFO  ==> Done
Evaluation Progress:   0%|                                                                                | 0/52 [00:00<?, ?it/s]Traceback (most recent call last):
File "tools/train_val.py", line 159, in
main()
File "tools/train_val.py", line 135, in main
tester.test()
File "/home/yss/DEVIANT/code/lib/helpers/tester_helper.py", line 50, in test
for batch_idx, (inputs, calibs, coord_ranges, _, info) in enumerate(self.data_loader):
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 652, in next
data = self._next_data()
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1347, in _next_data
return self._process_data(data)
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1373, in _process_data
data.reraise()
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/_utils.py", line 461, in reraise
raise exception
AssertionError: Caught AssertionError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
data = fetcher.fetch(index)
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 49, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 49, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/yss/DEVIANT/code/lib/datasets/kitti.py", line 104, in getitem
img = self.get_image(index)
File "/home/yss/DEVIANT/code/lib/datasets/kitti.py", line 82,  in get_image
assert os.path.exists(img_file)
AssertionError

I reproduced the pre-trained model with some of the KITTI images, I think the environment should be fine.
But when I run the test script, the following error is reported
2023-11-09 10:01:30,021   INFO  ==> Loading from checkpoint 'output/run_221/checkpoints/checkpoint_epoch_140.pth'
2023-11-09 10:01:32,223   INFO  ==> Done
Evaluation Progress:   0%|                                                                                | 0/52 [00:00<?, ?it/s]Traceback (most recent call last):
File "tools/train_val.py", line 159, in
main()
File "tools/train_val.py", line 135, in main
tester.test()
File "/home/yss/DEVIANT/code/lib/helpers/tester_helper.py", line 50, in test
for batch_idx, (inputs, calibs, coord_ranges, _, info) in enumerate(self.data_loader):
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 652, in next
data = self._next_data()
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1347, in _next_data
return self._process_data(data)
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1373, in _process_data
data.reraise()
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/_utils.py", line 461, in reraise
raise exception
AssertionError: Caught AssertionError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
data = fetcher.fetch(index)
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 49, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 49, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/yss/DEVIANT/code/lib/datasets/kitti.py", line 104, in getitem
img = self.get_image(index)
File "/home/yss/DEVIANT/code/lib/datasets/kitti.py", line 82,  in get_image
assert os.path.exists(img_file)
AssertionError

I reproduced the pre-trained model with some of the KITTI images, I think the environment should be fine.
But when I run the test script, the following error is reported
2023-11-09 10:01:30,021   INFO  ==> Loading from checkpoint 'output/run_221/checkpoints/checkpoint_epoch_140.pth'
2023-11-09 10:01:32,223   INFO  ==> Done
Evaluation Progress:   0%|                                                                                | 0/52 [00:00<?, ?it/s]Traceback (most recent call last):
File "tools/train_val.py", line 159, in
main()
File "tools/train_val.py", line 135, in main
tester.test()
File "/home/yss/DEVIANT/code/lib/helpers/tester_helper.py", line 50, in test
for batch_idx, (inputs, calibs, coord_ranges, _, info) in enumerate(self.data_loader):
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 652, in next
data = self._next_data()
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1347, in _next_data
return self._process_data(data)
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1373, in _process_data
data.reraise()
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/_utils.py", line 461, in reraise
raise exception
AssertionError: Caught AssertionError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
data = fetcher.fetch(index)
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 49, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/yss/.conda/envs/ysbt/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 49, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/yss/DEVIANT/code/lib/datasets/kitti.py", line 104, in getitem
img = self.get_image(index)
File "/home/yss/DEVIANT/code/lib/datasets/kitti.py", line 82,  in get_image
assert os.path.exists(img_file)
AssertionError

os.path.exists(img_file)

Can you check the image_paths and print out the path which the dataloader is looking for and is not able to find.

2023-11-09 10:36:19,195   INFO  ==> Loading from checkpoint 'output/run_221/checkpoints/checkpoint_epoch_140.pth'
2023-11-09 10:36:21,446   INFO  ==> Done
Evaluation Progress:   0%|                                                                                | 0/52 [00:00<?, ?it/s]Checking img_file: /home/yss/DEVIANT/code/data/YSS_data/validation/image/000000.png
Checking img_file: /home/yss/DEVIANT/code/data/YSS_data/validation/image/000002.png
Checking img_file: /home/yss/DEVIANT/code/data/YSS_data/validation/image/000004.pngChecking img_file: /home/yss/DEVIANT/code/data/YSS_data/validation/image/000006.png

Checking img_file: /home/yss/DEVIANT/code/data/YSS_data/validation/image/000006.png

This is different from the path I had suggested. You should rename the testing folder to validation and image_2 folder to image.  The final structure is now as follows:
├── data
│      ├── YSS_data
│      │      ├── ImageSets
│      │      └── validation
│      │            ├── calib
│      │            ├── image
│      │            └── label

Would you mind trying once again?

ok, I will try

But does the validation set's label also need to have content?

But does the validation set's label also need to have content?

Only if you need to run evaluation against GT.

Why does the generated result visualize the output image as it was during training?   Generated results Why does the visualization output the image as it was during training? The visualization program I have modified.

Do you see some results in these text files? or are these files empty?

Why does the generated result visualize the output image as it was during training?

The visualization code is only for KITTI, Waymo or nusc_KITTI datasets, and not for your custom dataset which has different sizes than these datasets.
Consider extending plot/plot_qualitative_output.py for your own dataset.

These files are not empty, there are some results.

I tried to put some test photos from KITTI into YSS as I recall and evaluated them with config221 and the output file seems to be ok .
Here are the results of my attempts to visualize the results, the evaluation did not plot correctly in the YSS plot, it seems that, as you say, I need to  extend my own dataset in the visualization scripts

It stands to reason that the plotting of the following figure should be in the upper figure. That's just my personal opinion.

This is the result of my visualization of the YSS dataset using KITTI model.(run_221)  It seems that the resolution is quite important for the visualization result, I don't know how to modify the proper resolution with the P2 matrix, can you please give me some suggestions? Thank you very much!

P2:  3.404000000000e+03 0.000000000000e+00 6.380000000000e+02 0.000000000000e+00 0.000000000000e+00 3.404000000000e+03 8.510000000000e+02 0.000000000000e+00 0.000000000000e+00 0.000000000000e+00 1.000000000000e+00 0.000000000000e+00


Is "caption" meaningful for the model?

Hi there,
I've noticed that within the inputs of the model, the "caption" is randomly selected from the strings in ldm/data/personalized.py
=> imagenet_templates_small.
However, given that this selection process is random, I'm curious about the significance of this caption for the model. Since both training and inference processes utilize this caption as one of the inputs, it's likely to have an impact on the model's output. Therefore, I find it a bit puzzling and would like to confirm with you, if I may be misunderstanding something.

I think the caption do not matter. Since the caption number is limited. The captions in inference time have been used in the training time. So, it would not influence the results too much. It is originally designed for the generation diversity.


Added SDP for probator

Relevant components:

[ ] Signalling server
[x] Frontend library
[ ] Frontend UI library
[ ] Matchmaker
[ ] Platform scripts
[x] SFU

Problem statement:
The current SFU does not always select the appropriate resolution stream even when simulcast is configured.
This may be because mediasoup is sending a stream for inspection under the name "probator", but it is not receiving this stream properly, so the inspection is not performed properly and the bitrate estimation is not done properly.
Solution
Fixes #85

@zuvola Thanks for this digging any reference in mediasoup docs/discussion about this "probator"?
Also, when you remove this, does it fix the problem of not selecting the appropriate resolution stream?

Some further reading: https://mediasoup.discourse.group/t/probator-pli/3898/5

@lukehb
Unfortunately I have not found any useful documentation.
The simulcast was working fine in the mediasoup demo at the following URL, and I found the probator when I was trying to find the difference.
https://v3demo.mediasoup.org/
https://github.com/versatica/mediasoup-demo
I just added the probator to the SDP using the mediasoup-client source as a reference and it works correctly, but I am not sure if this modification eliminates the root cause.
I am also not sure what happens when the probator packets are removed. Perhaps the bandwidth estimation will stop working.

With your PR applied, does automatic layer switching work when you restrict the bandwidth?
I do agree the probator does seem like a likely mechanism the mediasoup authors are using the probe for bitrate.

I am also not sure what happens when the probator packets are removed. Perhaps the bandwidth estimation will stop working.

I agree that bandwidth estimation will likely fail if probator is munged out.
I think further investigation of the media soup demo is a good idea, perhaps we are configuring wrong.

By applying this PR, I have confirmed that it is working correctly, at least in my and my team member's environment.
It's a little hard to see, but I attached a working gif above.


Cure HTTP Authentication Singleton's Password Overwrite

HTTP Basic Authentication support in the Schema Registry Client that Registry Helper relies on uses a Singleton pattern to implement its strategies each of the three credential sources it implements a strategy for interfacing with.
Because Registry Helper uses the client for both source as well as destination access, this causes a problem if a user configured both source and destination authentication, and uses different credentials, but acquires them from the same source strategy on both ends of the line.
At runtime, registry helper first initialized the source registry client with no issues, then it proceeds to configure the destination registry client and ends up accessing the same basic HTTP Authentication helper object already in use by the source registry.  It winds up overwriting the credentials and wires the resulting client to the destination registry.  The first time the SMT attempts to read a schema using the source registry's client object, it fails due to the fact that the credentials are now for the destination registry instead of its own.
This is a little complicated to fix--we cannot modify the client to replace the existing implementation with one that is not a singleton without breaking encapsulation.  For now, this PR only includes additional test cases, with the intent to discuss an approach to fix the underlying cause and add it to the PR before it is merged.
I think the most likely approach to work is going to involve either creating a second set of identical implementations of the three basic HTTP authentication singletons.  A prefix or a suffix would be added to the three new instances and the registry client would re-map the service's lookup key (USER_INFO, URL, or SASL) to include the appropriate prefix for either the source or destination client.
I'm not sure if the shade plugin could be configured in a way to assist with this issue.  It might be able to handle a second relocation, but I don't think it could be told to add a prefix or suffix to the services' lookup keys in the process.  The former approach might require making a hand copy of the three strategies as part of this project's own codebase.  I'm open to suggestions!
Alternately, we could pursue a more heavy weight but more conservative approach and arrange for a second relocation of the entire client, perhaps by using the shade plugin in a dependency to relocate the client twice, once to a namespace intended for the source, and again to a different namespace intended for the destination.

This branch now has a solution to its associated complication that leverages "SRC" and "DEST" prefixes to give Schema Registry a distinct singleton for each direction of Schema Registry transfer, so no more overwritten credentials.

Hey @jheinnic , would you mind making a new comment to update the README to include all these new properties?
Happy to merge after that

I seem to recall having thought the name spacing was reconciling some early issue I had with the shade plugin, but I can neither recall what that was nor reproduce it by staying within the cricket.jmoore namespace, so I've renamed these with Src and Dest prefixes and moved them to a closer package namespace.  I was successfully able to subclass the original concrete types with only the alias method override required to give them each a unique lookup key that does not conflict with the repository client's own original singleton instances.
No problem getting the new test case to pass as-is and a manual inspection of the jar file revealed no surprised.  I'm folding the jar into a container now as a last precaution, but expect no trouble!
Thanks for the sound feedback!

I see this PR has been approved, but it looks like its merge is still pending, FYI.

I'm folding the jar into a container now as a last precaution, but expect no trouble!

Sounded like you were still building it, and were going to test out those changes? Or you think it's good to go?

Coming back to this a little late, but I finally managed to get a copy of an image with this change included pre-merge and confirmed that it does indeed work as desired.  It was a little harder this time than with previous commits because I'm not longer adding a jar to the image, but attempting to override one and had to figure out a way to do that after the container launched, but before connect's isolating class loader saw the jar file.  I finally realized I could suspend the launch script without losing the ability to docker cp files in by setting environment flags so the launcher would suspend-on-startup waiting for a debugger to be attached.
Anyhow, I see you've already merged the request, so will go ahead and revert my workarounds from our deployment and go back to using a build of our base image that includes this latest commit.  Thanks again for taking the submission!


Create Game Page

[ ] #21
[ ] #22
[ ] #23
[ ] #24

Additional tasks to be done:

check dependencies arrays in useEffect hooks on this page;
make the right answer to turn into green after ~20 seconds, then after ~10 more sec. automatic rerouting;
a user cannot click an answer after the right answer is displayed;
add countdown.

Commits:

client: 95a90c6a591e93f7f4e9bbdbf7e6f222dd43b13d
server: 3620d95597891a50bc030ebf6dbe0a98bbe5eab6


Rounded corners on rect, but only for some corners

As originally suggested in #1201, this is a common request, and the workaround isn’t always feasible (for example with diverging bars).

Thinking about this has sent me into a rabbit hole. Two issues:

how do we name this option (maybe "high-end radius—rh"—knowing that high will be bottom for negative values, right for horizontal bars and left for horizontal-negative)?
instead of a svg:rect we'll now have a generic svg:path. We can do one that just implements rh (if not nullish[1]), and keep it at this.

But there might be future use cases (some we already have in mind) where the element we create is completely different: what if, for example, if we want bars that follow a radial coordinate system (#133). (Or even, marks that are rendered with the same visual logic but using canvas instead of SVG…)
So, while we can implement this with a simple test like (rh != null ? "rect" : "path") (and maybe we should, I can put up a PR for this anyway), it's also tempting to take this as an opportunity to think more globally about how we'd want to be able to pass new "visual materializers" to marks.
[1] I'd want an explicit rh: 0 to opt-in to a svg:path, in order to make it possible to transition from rh=0 to rh=5 without discontinuity.

Hmm, one possibility is an ry2 option that rounds the corners corresponding to the y2 edge. Then you could have similar options ry1, rx1, rx2 for the other sides — but you’d have to define which side takes precedence since the sides would compete for the corners.
Another possibility is separate radii for each corner, like CSS does for border-radius (which also supports elliptical corners!).
Complicated!

I'm going to give up on that one, because a clean generalization with all the possibilities is just too much work — too many "corner" cases, for a limited usage. Instead let's create examples to show how to use a render transform?
For instance: https://observablehq.com/@observablehq/dog-eared-bars (although the implementation is not optimal since it creates rects then discards them… I find it easier that way).


ImprovementImprove stats sample strategy.

Improve the accuracy of sample stats collection. For non distribution columns, use
n*d / (n - f1 + f1*n/N)
where f1 is the number of distinct values that occurred exactly once in our sample of n rows (from a total of N),
and d is the total number of distinct values in the sample.
For distribution columns, use ndv(n) * fraction of tablets sampled for NDV.
For very large tablet to sample, use limit to control the total lines to scan (for non key column only, because key column is sorted and will be inaccurate using limit).

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


events?

Hi, first of all, thanks for this nice plugin. Just noticed you built it as different panels. Great decision, very useful!
I don't know about what's currently possible with the API, which obviously is still a work in progress, but I'm working a lot with events in analytics as they are pretty useful for all sorts of things. Would there be a panel with events coming up (preferrably being able to show multiple events panels, per panel configurable which events to show per that panel)?
Keep up the great work! This makes the Craft dashboard very useful!

Hi, first of all, thanks for this nice plugin. Just noticed you built it as different panels. Great decision, very useful!

Thanks. I wasn't sure what would be best, but decided that not everyone will want to see all the information so possibly better to split it up.

Would there be a panel with events coming up (preferrably being able to show multiple events panels, per panel configurable which events to show per that panel)?

AFAIK the api currently doesn't support events. They do have plans to support them in and when they're available, I'll certainly look to add them in. 👍

Thanks, great!

Hi,
It seems plausible has support for events now, if you look at the example at the bottom of this page:
https://plausible.io/docs/stats-api
Do you still plan on implementing this?


WIP: Adds filter_requires_grad.

Resolves #260.
filter_requires_grad accepts a list of pgroups dictionaries and yields a list of pgroups with the parameters that have requires_grad==False filtered out. All other values in the dictionaries are left alone.

I'm going to put this on hold till the details on how to use this is laid out in   https://github.com/dnouri/skorch/issues/261.
I would prefer these functions be hidden from the user, and NeutralNet be able to filter out require_grads==False be default.

I would prefer these functions be hidden from the user, and NeutralNet be able to filter out require_grads==False be default.

In general, I would agree that this the more sensible default. pytorch, however, does explicitely not do it, and according to the principle of least surprise, I lean towards going with pytorch.
Still, it should be easy for the user to change the behavior and a helper function + docs is probably sufficient.

Sorry that I haven't thought of it earlier, but could you please add a test that shows that if I initialize a net with additional optimizer arguments, the arguments are correctly passed to the optimizer:
NeuralNet(..., optimizer=filtered_optimizer(torch.optim.SGD), optimizer__momentum=0.9)

Update this PR with:

Adds test to check that arguments are correctly passed to the optimizer. (test_passes_kwargs_to_neuralnet_optimizer)
Moves functions to skorch.helper.

I updated this PR with your suggestions.
If optimizer__filter_requires_grad gets accepted as a parameter to NeutralNet, these functions would be moved to util, and a user would not need to worry about importing filter_requires_grad.

All in all, this looks good, but I'm not yet satisfied with the name filter_requires_grad. First it sounds as if it were a "filter that requires gradients". Second, it's not really a filter but a wrapper. A more telling name would be optimizer_with_only_params_that_require_grad, which obviously is too long. So more along optimizer_params_requires_grad?

I think we can avoid the naming issue by generalising, e.g.:
def filtered_optimizer(optimizer, filter_fn):
    der opt(params, **kwargs):
        return optimizer(filter_fn(params), **kwargs)
    return opt

Thanks, good work.


Update deprecated circleci images to latest

Update deprecated circleci images to latest

Thanks for review! Merging now.


WIP, sriov, Wait for cloud-init done indication

Only the last commit is unique, rest are rebase on top of two PRs, that this PR depends on
None

@rmohr
just fyi, this is what i started once, in case we will want it again


[SPARK-22703][SQL] make ColumnarRow an immutable view

What changes were proposed in this pull request?
Similar to https://github.com/apache/spark/pull/19842 , we should also make ColumnarRow an immutable view, and move forward to make ColumnVector public.
How was this patch tested?
Existing tests.
The performance concern should be same as https://github.com/apache/spark/pull/19842 .

cc @ueshin @hvanhovell @kiszk @gatorsmile

Test build #84488 has started for PR 19898 at commit 0771ffc.

Test build #84488 has finished for PR 19898 at commit 0771ffc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84488/
Test PASSed.

LGTM.

thanks, merging to master!


feat(React): Auto import React in our components

Been wanting to get to this for a while.
Ended up being a bit tricky due to how we alias things in our webpack config, but figured it out. Issue is we were aliasing react, which then prevented us from properly aliasing react/jsx-runtime (aliases aren't recursive). And so i just removed the react alias since we no longer need to commonly yarn link with reaction, etc.
I then updated all of our files via a codemod: npx react-codemod update-react-imports

Some conflicts here; I also worry about conflicts in open and about to be opened PRs

The conflicts aren't extreme. Remove react import here, destructure it there. I'll put a notice out to #dev for folks who need help.


Desmodder not loading

Desmodder not loading on desmos
desmos link I was using: https://www.desmos.com/calculator/fwiptpooji
error logs and my guesses on what they mean
DevTools failed to load source map: Could not load content for chrome-extension://eclmfdfimjhkmjglgdldedokjaemjfjp/index.js.map: System error: net::ERR_BLOCKED_BY_CLIENT
"eclmfdfimjhkmjglgdldedokjaemjfjp" matches the chrome webstore download link for desmodder
Uncaught ReferenceError: require is not defined     at fwiptpooji:307:5
"fwiptpooji" is the id of the desmos graph I was using
Uncaught Error: No parser     at q (calculator_desktop-94dae14e922dce67996c9d11483cca99b6f3dcf7.js:1:1012)     at r (calculator_desktop-94dae14e922dce67996c9d11483cca99b6f3dcf7.js:1:2221)     at Object.apply (script.js:2114:23)     at script.js:2369:26     at script.js:6981:2     at script.js:6982:12

The first error just means that the source map isn't including, which is ok.
The second error is expected because part of DesModder's operation is blocking the initial load of Desmos in order to modify some stuff before Desmos loads.
The third error Uncaught Error: No parser is unexpected. It occurs because Desmos removed their parser module, which Desmodder depends on. I fixed this issue earlier today in 0.7.3 (https://github.com/DesModder/DesModder/releases/tag/v0.7.3), but Chrome still has to approve it. If you want to use this fixed version of DesModder now, then install it on Firefox (Firefox doesn't go through an approval process) or download the dist-chrome.zip on the 0.7.3 release page, and install the extension from that zip file.
To install from zip, follow these installation instructions (based on this):

You probably want to do this in a separate Chrome profile to be safe; otherwise remove any existing DesModder install to avoid duplication
Download dist-chrome.zip, and unpack it to somewhere safe (not Desktop or Downloads where it might get accidentally deleted)
Visit chrome://extensions (via omnibox or menu -> Tools -> Extensions).
Enable Developer mode by ticking the checkbox in the upper-right corner.
Click on the "Load unpacked" button in the upper-left corner
Select the directory of your unpacked extension.

This is now approved for the Chrome webstore!
If you uninstalled DesModder, you can re-install it.
If you installed DesModder from zip, I suggest removing that install and installing directly from the Chrome webstore so you can get future updates automatically.
If you kept DesModder around, it may still be in 0.7.2 and buggy as before. You might want to force update to 0.7.3 by going to chrome://extensions, enabling Developer mode (in the top right), and pressing the update button (top left).
The following image from CloudHQ demonstrates how to force update:

I'll leave this post open and pinned for a few days so people can see it.


update: Flink ref doc link version to 1.16

Describe your changes
Updated links referring to Apache Flink® documentation from v1.15 to v1.16 and aligned content with the style guide and format.
HH-1604
Checklist

[x] The first paragraph of the page is on one line.
[x] The other lines have a line break at 90 characters.
[x] I checked the output.
[x] I applied the style guide.
[x] My links start with /docs/.

Flink 1.19 is out. Should the docs point to Flink 1.19?

Flink 1.19 is out. Should the docs point to Flink 1.19?

Make senses. I updated the link to version 1.19.


Refactor handling of count message in character count JS

The “count message” refers to the “You have x characters remaining” message in the character count (govuk-character-count__message).
Original issue
The original issue raised by @36degrees  was fixed by https://github.com/alphagov/govuk-frontend/pull/1347. This allowed a value for aria-describedby to be passed through to the textarea component. This means that the character count component can correctly pass the id of the count message to the textarea component to associate the two.
Fixes in this PR
There was a bit of refactoring to do in terms of how the JS of the character count handles defining the count message so this PR does that. I’ve tried to break the changes into smaller commits to make it clear what’s going on but can squash them before merging if that makes more sense.
Making the count message markup required
The count message markup is now always present (since https://github.com/alphagov/govuk-frontend/commit/7b534bf734cd0a1be2cff34d64018aa89abdabb6). This PR makes the markup for it required, instead of giving the option to add it with Javascript - the message markup should always exist so that user is notified of the character limit, even if JS doesn’t run.
This PR removes the branching logic and the code that added the count message markup dynamically in createCountMessage(). It’s worth nothing that the code inside the block hasn’t been executed since https://github.com/alphagov/govuk-frontend/commit/7b534bf734cd0a1be2cff34d64018aa89abdabb6.  As using the character count without  the count message markup and relying it to be added with JS is not part of the public API, removing this functionality is not considered a breaking change.
Defining the count message
The count message DOM element is now defined at the top of the module with the other required DOM elements.
We check whether the textarea is present before getting its id to get the count message DOM element - the check prevents an error with getting $textarea.id if the script is run without component markup being present present on the page. Alternatively we could define the count message in init() after doing a check for textarea which would require another check for it and wouldn’t make it as clear that it’s required as when placed at the top of module. See below for the code. Thoughts?
CharacterCount.prototype.init = function () {
  var $module = this.$module
  var $textarea = this.$textarea

  if (!$textarea) {
    return
  }

  this.$countMessage = $module.querySelector('[id=' + this.$textarea.id + '-info]')

  if (!$countMessage) {
    return
  }

Moving the count message markup inside govuk-form-group
The original code for checking/creating the count message markup moves it in the DOM to be inside govuk-form-group. This was probably useful when the message markup was created dynamically. This PR retains the bit of code that moves the element for backwards compatibility. It’s important that the count message markup is inside govuk-form-group so that it gets wrapped within the error block (see screen grab below).

However we should look to remove moving the markup with JS and instead change the component markup so that the count message is inside govuk-form-group. This would be a breaking change so shall leave it for now and create an issue.
Fixes https://github.com/alphagov/govuk-frontend/issues/1106

Couple of minor typos in the commit messages:
3b52b27a34d03de78645cf6f7ab1aed43b2e3f0e

We check whether the textarea is present before trying to its id to find the count message

814935a1afc2925bd9278f896160f414431a261e

It’s worth nothing that the code inside the block hasn’t been executed since [].

Thanks @36degrees I've just fixed those


Increase badge cache time & add control

Increase the default time that badges are cached
and the default time that badges are served by the CDN when stale.
Also add environment variables to control these values.
The increased default BADGE_CACHE_MAX_AGE (from 1 day to 10 days)
reduces server effort. Badge responses are very fast, but
it's even faster when we don't have to deal with them at all.
The current (1 day) setting means that in practice every day
we must reply a badge for every single project. We don't need to do
that; let's distribute the work further.
The increased BADGE_CACHE_STALE_AGE (from 10 days to 100 days)
provides us with greater protection from server problems.
If the server goes down, badges will continue to be served for a
long period of time, so many people won't even realize we're down.
We can purge them all if needed.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

@jdossett and others - what do you think? I've been keeping badges to 1 day in the CDN cache, so that if we get it wrong they'll age out in a day. But we've had no problems for a long time, we could purge if we did need to erase them early, and caching them 10x longer reduces the average number of badge requests a day (to 1/10the current value).
We don't have a problem speedwise because badges are very quick. But we serve a lot of badges (1/project), so this is an easy way to scale up to many more projects & on average will reduce our load. I want to make things so that everything quietly "just works".

@david-a-wheeler This looks good to me.


fix typo fix in auto-partition page

Proposed changes
auto-partition page typo fix

run buildall

LGTM


Update website-monitoring.md

Removes extra whitespace in preformatted section that is breaking syntax coloring

@markwolff : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the update.


Remove the four npm dependencies of which use software licenses that violate the tenets of open source and are incompatible with parent MIT licensed modules.

What problem does this feature solve?
The following four deeply nested dependencies use DBAD licenses, which are incompatible with MIT Licenses, due to the fact that they state that a pint is owed to the maintainer of these modules if significant amount of wealth is made off of software that uses these modules.
Whether or not this is what the maintainer intended, the license implies that not sharing a pint with the maintainer is a direct violation of the license.
https://github.com/RIAEvangelist/node-ipc
https://github.com/RIAEvangelist/js-queue
https://github.com/RIAEvangelist/js-message
https://github.com/RIAEvangelist/easy-stack
I would like to recommend to the entire Vue.js community, that we take a stance similar to the one that Apache takes on nonsensical licenses:
Nonsensical licenses
These licenses while amusing to their creators are legally problematic. They often include subjective Field of use restrictions e.g. “Don’t be evil” with no arbiter for that subjective restriction defined. In some cases they may not even grant sufficient rights to conform to the OSI open source definition. Since we do not wish to surprise our downstream consumers we forbid the use of such licenses.
I am aware that there are a large amount of libraries used by the node.js community that have these modules as dependencies - however, I think this is due to unawareness not by choice. I am not suggesting we convince the entire node.js community to discontinue usage of these libraries, however I would like to encourage at least the Vue community look into finding out what options we have.
Everything I am saying is out of pure individual interest. I am not an informed lawyer. I do not represent the views of a company.
Licenses such as DBAD will cause useful libraries to be avoided by entire companies so as to steer clear of what is implied by the DBAD license terms.
If we can come up with a solution, we can benefit the community in two main ways:

Increase the amount of adoption of the Vue.js framework and all of its associated tools (For the companies that would only consider seriously adopting the framework if they also adopted usage of the vue-cli)
Remove the risk of legal implications and public embarrassment of lawsuits that could possibly occur over the terms that are implied in the DBAD license text.

Again- I do not represent the views of a company nor of a lawyer.
My main goal is to increase the adoption and usage of Vue.js and the Vue-cli.
If there is a better forum to bring this issue to the attention of the community, can someone help me do so? I have never had to do something like this before.
What does the proposed API look like?
There is no API for this feature request. I was not sure if this should be opened as a Bug Report or Feature Request since those are the only two options on this form.
Regarding the approaches we could take to mitigate this problem:

Ask the maintainer to change the license of these four modules himself
I know of one individual who asked already, and the maintainer didn't seem to want to drop the DBAD license completely. I'm not sure if the maintainer will listen if the entire community chimes in.

Ask the maintainer to dual license. If the maintainer wants to be able to make a statement with the DBAD license, he will still be able to do so - however adding a second license like the MIT license will remove the risk that is currently imposed on the rest of the community

Get the Vue-cli community to investigate and develop different solutions to our problems. If it comes to it, the only way to get away from using the software in these modules may be to remove the current usage of those for modules with the DBAD license. Other solutions will have to be considered.

The downside of this last approach, is that finding alternative solutions may in fact be difficult.
https://dbad-license.org/

@sodatea Thanks a ton for putting this on your radar

@sodatea Unfortunately it appears that the original maintainer really doesn't want to change their license away from DBAD to MIT or some other approved license. ( https://github.com/RIAEvangelist/node-ipc/issues/133 )
Is it even feasible to have a future version of vue/cli drop those four modules as dependencies?

So I've just run into this exact same problem in the same circumstances. It looks like the 4 repos are a dependency of node-ipcwhich in itself is a dependancy of @vue/cli-shared-utils. I wonder if there is an ability to turn off certain utility libraries if one wasn't building the vue app to connect to say a node.js server?

I guess we can refactor to websockets and drop node-ipc.

Would be ideal, although would it be needed for people using node.js? Not 100% sure on how to contribute to the @vue/cli-shared-utils repo but happy to contribute where I can! 😄

Hum people using vue cli already need node.js. node-ipc is mainly used for plugin to communicate with the vue cli UI server.

Ah apologies, that didn't click before, makes sense now

Forgive my ignorance on the subject but would there be a way to remove the UI part of vue-cli? If that's the only part of the project that's using it and we don't have to use the UI couldn't we get by without it?

Hey guys, maintainer of all of those packages here.
Apologies, for the delay in everything. I'm going to be updating all of the licenses to apache 2.0 from DBAD.

Hello @RIAEvangelist ... We are running into the same issue for one of our projects. With the DBAD license we are not able to pass the license check.
So we would be really happy if you could update the license of your packages from DBAT to apache 2.0 as suggested.
(PS: Will also be happy to buy you a pint. Will send you a mail about this.)

Guys, @RIAEvangelist, any progress on this one? This becomes an issues that can impact our decision on to use Vue or stick to Angular despite how painful is it going to be...

What would be the best license and why? My goal is to make this as
open-source as possible. I do not want someone to say they own this code in
the future thereby preventing others from using it.
On Fri, Oct 30, 2020 at 9:15 AM bkhatkov<EMAIL_ADDRESS>wrote:

Guys, @RIAEvangelist https://github.com/RIAEvangelist, any progress on
this one? This becomes an issues that can impact our decision on to use Vue
or stick to Angular despite how painful is it going to be...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-cli/issues/2621#issuecomment-719648519, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC2DEOP42DDOVVLGOXFIG3SNLRDTANCNFSM4FXOXYHA
.

Updated each to MIT, then published the updated version.

@RIAEvangelist, hey. That is highly appreciated. Thank you.

@RIAEvangelist Thank you so much!
One small problem, though, is that the js-message dependency is pinned to the old version, as said in https://github.com/RIAEvangelist/node-ipc/issues/184

OK, fixed in patch 9.1.3 thanks.

I believe this ticket can be closed.

👍 Thanks! Really appreciate all the help


[Solutions] Update Search Payload

Need to update payload for Search Query.
Add parseInt() to documentPosition value in Click analytics call

Using https://stage.lifesciences.danaher.com/us/en/solutions/mabs/cell-line-development/products.html as an Example.
This is what I expect the search payload to look like:
{
"actionsHistory": [
{
"name": "Query",
"time": ""2024-03-08T16:23:24.210Z""
},
{
"name": "PageView",
"time": "2024-03-08T16:23:22.913Z",
"value": "/content/danaher/ls/us/en/search"
}
],
"analytics": {
"actionCause": "interfaceLoad",
"clientId": "4414778d-f983-4c99-a9ae-91a3a984fc6d",
"clientTimestamp": "2024-03-08T16:23:24.212Z", //time stamp of when the search call started
"customData": {
"context_host": "stage.lifesciences.danaher.com",
"context_internal": false,
},
"documentReferrer": "https://stage.lifesciences.danaher.com/us/en/solutions/mabs/cell-line-development.html", //document.referrer
"documentLocation": "https://stage.lifesciences.danaher.com/us/en/solutions/mabs/cell-line-development/products.html", //this is the current page
"originContext": "DanaherLifeSciencesCategoryProductListing" //this is whatever we put for the originLevel1 in the analytics call
},
"aq": "@workflow==mabs|cell-line-development",
"context": {
"host": "stage.lifesciences.danaher.com",
"internal": false
},
"firstResult": 0, //this can be hardcoded
"locale": "en", //this can be hardcoded
"numberOfResults": 48, //this can be hardcoded
"pipeline": "Danaher LifeSciences Category Product Listing", //this can be hardcoded
"referrer": "https://stage.lifesciences.danaher.com/us/en/solutions/mabs/cell-line-development.html", //document.referrer,
"searchHub": "DanaherLifeSciencesCategoryProductListing", // this can be hardcoded
"tab": "Solutions", // this can be hardcoded
"timezone": "America/New_York"
}


Make XRPFees a non-breaking API change

Issue Description
https://github.com/XRPLF/rippled/pull/4247 introduces an amendment, featureXRPFees (XRPFees for short), and causes some breaking API changes.
The motivations for the amendment:

The fee code is unnecessarily complex due to arcane concepts like "fee units" and "reference transactions" - represented as integers of various widths. A lot of effort is expended to keep all that straight and prevent developers from doing the wrong thing.
Fee units are hard-coded to 10 and the "reference transaction" fee is also 10, so there is an opportunity to reduce complexity: replace "fee units" with XRPAmount for all fees. Scaling/adjusting of fees can operate directly on XRPAmount objects instead.

XRPFees converts all representations of fees in the code, ledger, and protocol into XRPAmounts.
Currently, in the FeeSettings singleton object, BaseFee is serialized as hexadecimal; ReferenceFeeUnits, ReserveBase, ReserveIncrement are serialized as integers (when they would make more sense as strings because they are XRP amounts).
With XRPFees, the replacement fields are named BaseFeeDrops, ReserveBaseDrops, and ReserveIncrementDrops, and they are all XRP amounts serialized as strings.
It appears that there are likely impacts to server_info, SetFee (transaction type) txs, and Subscription messages for the ledger and validations stream.
Expected Result
Ideally, gain the benefits of XRPFees without the downside of breaking existing API consumers + client libraries.
Actual Result
Some field names and types have changed in the APIs, which would break existing integrations and client library versions.

Consider changing the API back to undo any breaking changes that #4247 can cause.
If there are case(s) where it really makes sense to break the API (i.e. it is impossible or infeasible to support existing clients), clearly document the change and offer a straightforward migration path for existing users.

@ximinez thinks it may be worth changing the APIs to avoid breaking changes.

Contexts

Direct rippled API consumers (WebSocket, HTTP JSON-RPC)
Client libraries (xrpl.js, xrpl-py, xrpl4j)

Related

https://github.com/XRPLF/xrpl.js/issues/2219

thinks it may be worth changing the APIs to avoid breaking changes.

changing how?

Ideally, the PR and the amendment would not affect any values returned by the API, so client libraries and other integrations don't need to update.
In cases where we do make a change, it would ideally be additive; i.e. add a new field with the nicely-formatted values. We can mark/document some existing fields as deprecated. Then, in 1-2 years, we remove them.
In cases where we make a breaking change today (i.e. an existing field goes away or its value changes), it should be very deliberate and necessary. I don't think that's the case here, where the PR and amendment are purely "cleanup" - it doesn't address any specific user feedback or problems, and it doesn't add any new functionality.

I was incorrect in thinking this amendment changed server_info.  While fields were updated in many places three did not change even though all three fields (base_fee_xrp, reserve_base_xrp, reserve_inc_xrp) use xrp decimal formats instead of drops.
https://github.com/ximinez/rippled/blob/e7a9e66148c7b4de57b0140d779d757d391e52b0/src/ripple/app/misc/NetworkOPs.cpp#L2596-L2599


Mental health & Spiritual Health Sections Enhancement (Solved)

Still I have some doubts on which font will look better. I have almost used 30 fonts but the default one looks more attractive in terms of reading. Also added background images on "mental health" and "spiritual wellness" section, if its not looking good do let me know I will change it with something else. Till now I think I have done my work.
Any type of suggestions are always welcomed, Thank you.

Ouk mam I have just copy pasted the social media as these were already written in a pre build one. If u want i will remove them for sure.
And sorry i have added that image by mistake.

No issues, looks good to merge 👍
Thank you for your contribution!

Thanks mam, this was my very first contribution in Open Source. Hope you like my work. Also looking forward to contribute more in the upcoming days.
And mam how we can see our scores ? Is there any system to see score for now or this will automatically be keeps on updating ?

Yes, you definitely did a good job 🚀
You would be able to see your scores in the leaderboard, which would be revealed after a few days. Your score will automatically update with every successfully merged PR with relevant labels.

Mam anything went wrong?
You have assigned me again in this issue?

No, nothing went wrong. I've assigned it for the leaderboard purpose.


Fixes to wavie.js

Added #announcements exception which fixes #182
Also fixed incorrect groups API calls/checks

@CameronAavik I made some additional changes and decided to just keep them in this PR. Could you review again?


Error / Filament : Material version mismatch

Hello, I got this error :
E/Filament: Panic in filament::Material *filament::Material::Builder::build(filament::Engine &):86
reason: Material version mismatch. Expected 4 but received 1.
because of this line :
.setSource(this, R.raw.andy)
Android Studio 3.5
Emulator Pixel 2 Android 8.1
CPU/ABI: Google APIs Intel Atom (x86)
Target: google_apis [Google APIs] (API level 27)
Project using AndroidX, Kotlin
Thanks for the library.
PS: I am not able to open the sfb in Android studio, I got this error :
java.lang.Exception: Bundle version 0,51:1 too old for this executable (max 0,54:1)
Edit: I am able to use the library using a sfb from Poly website, but the distance do not appear, I guess it is because I should use the andy from the library (?)
Please help me
Edit2 : I get a different error using lower versions of arcore/sceneform :
E/Filament: Panic
in Handlefilament::HwProgram filament::details::FMaterial::getProgramSlow(uint8_t) const:294
reason: The material 'FBX Material' has not been compiled to include the required GLSL or SPIR-V chunks for the vertex shader (variant=0xd, filtered=0xd).

https://github.com/appoly/ARCore-Location/issues/87

https://developers.google.com/sceneform/develop/create-renderables


Roundup: [oss-security] Re: GraphicsMagick heap out of bounds write issue

Here is a report from the oss-security mailing list for Vulnerability Roundup 27.
Skip to First Email
Instructions:
Identification
Identify if we have the software, in 16.09, 17.03, and unstable. Then determine if we are vulnerable, and make a comment with your findings. It can also be helpful to specify if you think there is a patch, or if it can be fixed via a general update.
Example:
unstable: we are not vulnerable (link to the package)
17.03: we are vulnerable (link to the package)
16.09: we don't have it packaged

IMPORTANT: If you believe there are possibly related issues, bring them up on the parent issue!
Patching
Start by commenting on this issue saying you're working on a patch. This way, we don't duplicate work.
If you open a pull request, tag this issue and the master issue for the roundup.
If you commit the patch directly to a branch, please leave a comment on this issue with the branch and the commit hash, example:
fixed:

release-16.09: abc123

Skip to First Email
Upon Completion ...

[ ] Update Graham's database

Info
Triage Indicator:
-needs-triage +roundup27 thread:0000000000003e08

File Search: https://search.nix.gsc.io/?q=graphicsmagick&i=fosho&repos=nixos-nixpkgs
GitHub Search: https://github.com/NixOS/nixpkgs/search?utf8=✓&q=graphicsmagick+in%3Apath&type=Code

Should the search term be changed from graphicsmagick? Suggest a new package search by commenting:
-suggested:graphicsmagick +suggested:correctPackageName thread:0000000000003e08

Known CVEs: CVE-2017-6335

Skip to End
Thu, 23 Feb 2017 21:18:17 -0600 (CST) Bob Friesenhahn <bfriesen-at-simple.dallas.tx.us><EMAIL_ADDRESS>GraphicsMagick versions up to 1.3.25 encounter a write beyond an
allocated heap buffer when reading CMYKA TIFF files which claim to
offer fewer samples per pixel than required.

This is the tiffinfo description of the problematic TIFF file:

TIFF Directory at offset 0x808 (2056)
   Image Width: 34 Image Length: 48
   Bits/Sample: 8
   Sample Format: unsigned integer
   Compression Scheme: None
   Photometric Interpretation: separated
   Extra Samples: 1<unassoc-alpha>
   Orientation: row 0 top, col 0 lhs
   Samples/Pixel: 2
   Rows/Strip: 32
   Planar Configuration: single image plane

The fix for this is Mercurial changeset 14998:6156b4c2992d which may
be viewed at SourceForge via this link:

https://sourceforge.net/p/graphicsmagick/code/ci/6156b4c2992d855ece6079653b3b93c3229fc4b8/

A minimal patch to correct the problem is attached.

This issue was reported to us on February 15, 2017 by Valon Chu.

Bob
--
Bob Friesenhahn
<EMAIL_ADDRESS>http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

tiff.c.patch
diff -r 0392c4305a43 -r 6156b4c2992d coders/tiff.c
--- a/coders/tiff.c	Sun Jan 29 10:04:57 2017 -0600
+++ b/coders/tiff.c	Thu Feb 23 21:06:50 2017 -0600
@@ -1230,8 +1230,8 @@
                   case 0:
                     if (samples_per_pixel == 1)
                       *quantum_type=GrayQuantum;
-                      else
-                        *quantum_type=RedQuantum;
+                    else
+                      *quantum_type=RedQuantum;
                     break;
                   case 1:
                     *quantum_type=GreenQuantum;
@@ -1411,12 +1411,12 @@
               }
             else
               {
-                if (image->matte)
+                if (image->matte && samples_per_pixel >= 5)
                   {
                     *quantum_type=CMYKAQuantum;
                     *quantum_samples=5;
                   }
-                else
+                else if (samples_per_pixel >= 4)
                   {
                     *quantum_type=CMYKQuantum;
                     *quantum_samples=4;

Skip to End

Fri, 24 Feb 2017 08:23:21 -0600 (CST) Bob Friesenhahn <bfriesen-at-simple.dallas.tx.us><EMAIL_ADDRESS>I would like to ammend this report in that the situation is a read
beyond an allocated heap buffer rather than a write beyond the end of
an allocated heap buffer as was originally reported.  The application
may crash but should not be otherwise compromised.

Bob

On Thu, 23 Feb 2017, Bob Friesenhahn wrote:

> GraphicsMagick versions up to 1.3.25 encounter a write beyond an allocated
> heap buffer when reading CMYKA TIFF files which claim to offer fewer samples
> per pixel than required.
>
> This is the tiffinfo description of the problematic TIFF file:
>
> TIFF Directory at offset 0x808 (2056)
>  Image Width: 34 Image Length: 48
>  Bits/Sample: 8
>  Sample Format: unsigned integer
>  Compression Scheme: None
>  Photometric Interpretation: separated
>  Extra Samples: 1<unassoc-alpha>
>  Orientation: row 0 top, col 0 lhs
>  Samples/Pixel: 2
>  Rows/Strip: 32
>  Planar Configuration: single image plane
>
> The fix for this is Mercurial changeset 14998:6156b4c2992d which may be
> viewed at SourceForge via this link:
>
> https://sourceforge.net/p/graphicsmagick/code/ci/6156b4c2992d855ece6079653b3b93c3229fc4b8/
>
> A minimal patch to correct the problem is attached.
>
> This issue was reported to us on February 15, 2017 by Valon Chu.
>
> Bob
>

--
Bob Friesenhahn
<EMAIL_ADDRESS>http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

Skip to End

Tue, 28 Feb 2017 08:19:36 -0600 (CST) Bob Friesenhahn <bfriesen-at-simple.dallas.tx.us><EMAIL_ADDRESS>This problem has been issued CVE-2017-6335.

The original reporter has tried to post CVE-assignment information to
the list but the mail has not made it through yet.

Bob

On Fri, 24 Feb 2017, Bob Friesenhahn wrote:

> I would like to ammend this report in that the situation is a read beyond an
> allocated heap buffer rather than a write beyond the end of an allocated heap
> buffer as was originally reported.  The application may crash but should not
> be otherwise compromised.
>
> Bob
>
> On Thu, 23 Feb 2017, Bob Friesenhahn wrote:
>
>> GraphicsMagick versions up to 1.3.25 encounter a write beyond an allocated
>> heap buffer when reading CMYKA TIFF files which claim to offer fewer
>> samples per pixel than required.
>>
>> This is the tiffinfo description of the problematic TIFF file:
>>
>> TIFF Directory at offset 0x808 (2056)
>>  Image Width: 34 Image Length: 48
>>  Bits/Sample: 8
>>  Sample Format: unsigned integer
>>  Compression Scheme: None
>>  Photometric Interpretation: separated
>>  Extra Samples: 1<unassoc-alpha>
>>  Orientation: row 0 top, col 0 lhs
>>  Samples/Pixel: 2
>>  Rows/Strip: 32
>>  Planar Configuration: single image plane
>>
>> The fix for this is Mercurial changeset 14998:6156b4c2992d which may be
>> viewed at SourceForge via this link:
>>
>> https://sourceforge.net/p/graphicsmagick/code/ci/6156b4c2992d855ece6079653b3b93c3229fc4b8/
>>
>> A minimal patch to correct the problem is attached.
>>
>> This issue was reported to us on February 15, 2017 by Valon Chu.
>>
>> Bob
>>
>
>

--
Bob Friesenhahn
<EMAIL_ADDRESS>http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

Skip to End

Working on

Well, we just need to cut out more from the patch and bring it back to the mailing-list minimalistic glory!
fixed:

master: 7b706900e7dd3ec55eb46a366f0bc47858fb7633
release-16.09: 065343bf7cba327dc3873365da9e4f5775edd954
release-17.09: a8baac668faca19f1c42d1f01b2b2c12db1bbb7a

I wonder if either of you saw that tiff.c.patch was listed here in this thread? Looks good!

«mailing-list minimalistic glory» was an explicit reference to tiff.c.patch. I just decided to keep the Mercurial revision reference anyway.


Security hole

We can whitelist App Insights IP addresses, but this seems to defeat all networking security. (Anyone can create an Azure account, and use their own availability tests to call our apps)
Is there any solution to this now or planned? For example, do availability tests support VNET integration?

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

ID: 3942b937-b212-3ceb-d356-450b7f598f68
Version Independent ID: 8b015b42-cf02-3942-3cc3-6e0f977d191a
Content: IP addresses used by Application Insights and Log Analytics
Content Source: articles/azure-monitor/app/ip-addresses.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@ishepherd Thank you for the feedback!  We are investigating this and will get back to you shortly.

@ishepherd We don't appear to have any documentation on VNET integration for availability tests and this feedback request appears to suggest that the need for a solution that would match your scenario has been recognized:
https://feedback.azure.com/forums/357324-azure-monitor-application-insights/suggestions/5395254-add-support-for-intranet-application-testing-not
I'm following up on this, but it doesn't look like this is something we can solve through documentation (unless you feel that it would be beneficial to cover future plans and current options in Data collection, retention, and storage).
As always, you can make your own request for integration here:
https://feedback.azure.com/forums/357324-azure-monitor-application-insights

If for security reasons you don't want to allow any inbound traffic other than from resources you fully control you can use the TrackAvailability() method call to create your own custom availability tests.
We have a doc that describes the basics of using TrackAvailability within an Azure Function. The TrackAvailability() method itself as described in the doc is fully supported, but you have to write/support your own HTTP test code.
There is also an open-source community project that I wrote called the availability-minion. It provides a windows service that can be installed and run on any windows system to allow at scale availability monitoring in on prem/hybrid/secure scenarios where inbound firewall exceptions are not an option. Under the hood it is using the TrackAvailability() method. This is just a side project I work on when I have free time, so it is not officially supported, but it might help unblock you or give you ideas if you decide you want to write you own custom availability monitoring.

@ishepherd We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Thanks, @mrbullwinkle! Sorry for incredibly late response, I did not see the updates to this issue.


Add a verify method that also takes an uncompressed public key

Supercedes #7. Commit is (cherry picked from commit 2ab46c56cd4957d3e0060ef46d50a6341fcd379d) in #7.
A verification method using the uncompressed pubkey is useful for the proof of stake use case, since we often validate multiple signatures from the same public key. Based off of the numbers in the official Ed25519 paper, the function with the uncompressed pubkey should save about 10% of the computation time.

repo abandoned


To add calculator for calculating scalar and vector projection

Is your feature request related to a problem? Please describe.
To add calculator for calculating scalar and vector projection

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018

Go ahead
Deadline 11 May,2021


Limit order investigation

Collect transactions for limit orders through gelato and plan a way to track open orders and transactions

Limit order transaction (link)
This transaction doesn't have any additional events for placing or executing orders.

Would like events in these three places:

Order created
Order executed
Order canceled


Missing icons in jupyterlab

Issue: Icons missing from tree in JupyterLab

Icons render as 'empty' images (i.e. blank squares). I am guessing that the CSS is buggered.

Here is code to reproduce this:

from ipytree import Node, Tree

tree = Tree()

root_node = Node('Root 1', opened = False)

tree.add_node(root_node)

new_child = Node('Child 1')

new_child.model = 1

root_node.add_node(new_child)

root_node = Node('Root 2', opened = False)

tree.add_node(root_node)

new_child = Node('Child 2')

new_child.model = 1

root_node.add_node(new_child)

tree

setup for jupyterlab:

JupyterLab v2.1.4

Known labextensions:

   app dir: /opt/app-root/share/jupyter/lab

        @j123npm/jupyterlab-dash v0.1.0-alpha.4  enabled  OK

        @jupyter-widgets/jupyterlab-manager v2.0.0  enabled  OK

        @jupyterlab/debugger v0.3.0-alpha.1  enabled  OK

        @jupyterlab/git v0.20.0  enabled  OK

        @jupyterlab/latex v2.0.0  enabled  OK

        ipytree v0.1.8  enabled  OK

        jupyterlab-plotly v4.8.0  enabled  OK

        jupyterlab-sql v0.3.3  enabled   X

        nbdime-jupyterlab v2.0.0  enabled  OK

        plotlywidget v4.8.0  enabled  OK

        qgrid2 v1.1.3  enabled  OK

   The following extension are outdated:

        jupyterlab-sql

   Consider running "jupyter labextension update --all" to check for updates.

I cannot reproduce locally. Installing JupyterLab 2 with latest ipytree seems to work properly. Do you see any error in the JavaScript console?

Hi I didn't make it clear that I was experiencing this issue in Jupyterhub with JupyterLab.  That is probably the reason why you were not able to reproduce it.

And there were no issues in the console

And there were no issues in the console

Not even a 404 error? Do you see any other missing icons in the JupyterLab UI?
FontAwesome might not be in the page :S But I am not sure. JupyterLab should include it in the page.

Nothing. It's odd for sure


Added copyright references

Adapted copyright info based on the given example. Extended "attribution" info a bit.

Oh, seeing #6420, reference-1.3.4.html is generated automatically from the source code.
@joostschouppe Here is the JS file to edit: https://github.com/Leaflet/Leaflet/blob/master/src/layer/tile/TileLayer.js

@joostschouppe being on holidays, I took the liberty to submit a new PR (#6439).

Superseded by #6439


Remove Geometry requires from vector formats

Would suggest removing requires for geometries other than point from vector formats, and making it website developers' responsibility to include whatever they need in their build config files. That way, if I know for example that I'm only dealing with point data, I do not have unneeded classes in my build files.
Point can be left in as it's the common denominator, used by all geometry types.
Example of suggested change at https://github.com/probins/openlayers/blob/geometryremoves/lib/OpenLayers/Format/GeoJSON.js
If people agree with this, I will change the other vector formats, and issue a pull request.

That's more responsibility for the application developer but that sounds good to me.

I think more interesting to follow the current requirements, but allows to build compressed code as proposed in http://trac.osgeo.org/openlayers/ticket/3496
This is what I use in production, e.g. to remove required features as OpenLayers/Tween.js in maps without controls
(But the programmer must ensure that the resulting code works e.g. without Tween currently it requires a dummy as OpenLayers.Easing={Expo:{easeOut:null}};)

I think I would distinguish between 'real' requires (meaning, code won't function without it) and 'optiional' requires (code will function ok as long as you don't try and use a function that needs that class). I think the requires instructions for the build program should be limited to the former - stuff that really is required. The formats are clearly the latter case - if you only have point data, there is no requirement for LineString, Polygon etc: the code works perfectly well without them.
There are quite a few inconsistencies at present, for example, with the Formats, WKT has no requires of geometries at all. I would propose standardising this, to the lowest common denominator.

Yes I agree (sometimes I think too much in the inexperienced user, sorry, is best to minimize @requires, but ticket/3496 is designed for the experienced user)
To fix some inconsistencies would be nice to have the clause @include as in jstools
(e.g. OpenLayers/BaseTypes/Bounds.js fails without OpenLayers/Utils.js, but do not have @requires OpenLayers/Utils.js to avoid circular requires, and more... I'm not OpenLayers team and I can do little in this way, sorry)
In WKT did not requires geometries to avoid a circular inclusion, because geometry requires WKT. I think currently (after SHA: 66de55ef9b12b435c6488873f59f3863b9635b65) it should be added @requires OpenLayers/Geometry/Point.js in WKT

ok, as 'excludes' works well, I've convinced myself that it's better to stick with the existing situation.
Issue closed


Add instructions on how to unminify main.js for easier browser debugging

This is a documentation change.
Summary
Add instructions on how to unminify the main.min.js for easier browser debugging.
Context
I'm having issues looking very much the same like already reported in #2664 (that the greedy-nav is not consistent in how it hides/shows navigation items), even though the fix for this issue is included in the theme release that I'm using.
I've nailed it down to that the browser reports the wrong outerWidth() of the navigation items some times and thus the jquery.greedy-navigation.js logic will compute the wrong thing as the calculations are based on wrong values. From here I've not gotten further though on how/why the browser on some page loads reports the wrong element widths.
Anyways to figure this out I had the need to unminify the main JavaScript file to set some debugger breakpoints in my browser. I just wanted to share back to the documentation on how one can easily prevent the minification.
Maybe there's even a better way? This is what made it for me though.

Thanks @iBug. The PR is updated!


Temporary fix for sites with multi-pnns

I don't get why it fails to run this script during the agent deployment
Executing wmagent-resource-control --add-T1s --plugin=SimpleCondorPlugin --pending-slots=50 --running-slots=50 --down ...
./manage: line 821: /data/srv/wmagent/v1.1.8.patch1/sw.sryu/slc7_amd64_gcc630/cms/wmagent/1.1.8.patch1/bin/wmagent-resource-control: Permission denied

it's not executable on the node, while it is in my local repo(?)


Two entries for SOD2 in Platform

After reviewing the target tractability file for duplicates, I have noted that the Platform contains two entries for SOD2:
https://www.targetvalidation.org/target/ENSG00000285441 - 270 disease associations
https://www.targetvalidation.org/target/ENSG00000112096 - 462 disease associations
Can we please investigate the evidence strings and why there are two entries?
As we are already working with submissions for 20.04, I have tagged this for review in the 20.06 release.

These are two overlapping genes in the same strand with the same name:

It seems that ENSG00000112096 is a more complete gene model given that it has multiple transcripts and associated UniProt accessions, whereas ENSG00000285441 has a single transcript an no UniProt accessions. We could ask Ensembl to review the gene models to make sure that they are really two independent genes.
In terms of evidence, both genes have evidence from data sources that provide evidence at the gene level but only ENSG00000112096 has evidence those using proteins, such as UniProt and text mining.

Ensembl will merge the two SOD2 genes as they agree that ENSG00000285441 looks like a transcript of ENSG00000112096, with the latter being the kept id. The change will be effective in Ensembl 101 due to be released later this year, not the upcoming 100.

Ticket closed as Ensembl has responded - see above.
Thanks @AsierGonzalez! 👍

Note that, however, this will not be fixed in until Ensembl 101 is released and we use it, which could be 20.06 or, possibly, later.


Question: In preview is it possible to show window as a dialog like we do in WPF with window.ShowDialog(); method.

I'm guessing no, but @MikeHillberg might know better.

@MikeHillberg


stale closure in invalidated queries

Describe the bug
First off thank you so much for this library it is tremendously useful. I understand this is quite a long bug report so if there is anything I can clarify or simplify please let me know.
I have a query which I want to refetch based on a combination of custom logic and a throttle. I don't want the query to fetch immediately so I set initialData to null and staleTime to Infinity. The thought is I can completely control when the query fetches by calling queryCache.invalidateQueries. Every time I invalidate the query the query should fetch. The problem is I am running into a stale closure issue. The code is a bit long but most of it is boilerplate simple requests. The issue may be related to the fact that I am using useThrottledFn to invalidate the query.
My confusion stems from the fact that I would expect the enabled flag and the queryFn to be updated simultaneously so I'm struggling to understand why there is a stale closure issue happening here at all.
Edit: Code Sandbox Repro with stale closure highlighted.
Edit 2: It seems like one fix is to include the dependencies in the query key. For example making the query key ["note", "cache", init.data !== undefined, patientInfo.data !== undefined]. I may be able to solve my problem using that approach but adding dependencies to the query key was not necessary in the dependent queries example from your react course.
/**
 * this is the custom hook which contains the problem
 */
const useQueryCacheNoteDTOQueryKey = ["note", "cache"];
const useQueryCacheNoteDTO = () => {

  // init is the first query, called once
  const init = useQuery(["init"], fetchApiInitObject, {
    staleTime: Infinity,
  });

  // patient info depends on init and is called once
  // this query works perfectly
  const patientInfo = useQuery(
    ["patient info"],
    () => fetchPatientInfo(init.data!),
    {
      enabled: init.data !== undefined,
      staleTime: Infinity,
    }
  );

  // the final query depends on init and patient info
  // and is called whenever I invalidate useQueryCacheNoteDTOQueryKey
  return useQuery(
    useQueryCacheNoteDTOQueryKey,
    () => {
      // the problem I run into is a stale closure here
      // init.data and patientInfo.data are undefined
      // even though I include checks for both in the enabled
      // parameter
      console.log("cached", init.data, patientInfo.data);
    },
    {
      enabled: init.data !== undefined && patientInfo.data !== undefined,
      initialData: null,
      staleTime: Infinity,
    }
  );
};

/**
 * this query invalidates the above query on a throttle,
 * in practice there is some logic which is included
 * to determine when the throttled function is called
 * but I removed it here
 */
export const useQueryAutoCacheNoteDTO = () => {
  const queryCache = useQueryCache();
  const cacheResult = useQueryCacheNoteDTO();

  const cacheNote = useThrottledFn(
    () => {
      queryCache.invalidateQueries(useQueryCacheNoteDTOQueryKey);
    },
    timeIntervals.autoCache,
    {
      leading: false,
      trailing: true,
    },
    [queryCache]
  );

  cacheNote();

  return cacheResult;
};

Update
I found a way to fix this problem by keeping a ref to the function I want to call and then calling that ref in a separate closure.
type ClosureFunc<TArgs extends unknown[], TResult> = (
  ...args: TArgs
) => TResult | undefined;

/**
 * Create a query function which updates based on dependencies
 */
export default function useSafeClosure<TArgs extends unknown[], TResult>(
  queryFn: ClosureFunc<TArgs, TResult>,
  deps: DependencyList
): ClosureFunc<TArgs, TResult> {
  const closureCb = useCallback<ClosureFunc<TArgs, TResult>>((...args) => {
    return queryFn(...args);
    // eslint-disable-next-line react-hooks/exhaustive-deps
  }, deps);

  const closureRef = useRef<typeof closureCb>();
  useEffect(() => {
    closureRef.current = closureCb;
  }, [closureCb]);

  const safeClosure = useCallback(
    (...args: TArgs) => closureRef.current?.(...args),
    []
  );
  return safeClosure;
}

I then replaced my queries with.
useSafeClosure(() => {
      console.log("cached", init.data, patientInfo.data);
}, [init.data, patientInfo.data])

Now everything is defined. Still not sure if there is a bug hidden in this mess but I'll close it since I think its probably impossible to deduce anything from this mess.

Hm, I’m not really sure what you are trying to achieve. It looks like you are invalidating the query cache in the render function (whenever the useQueryAutoCacheNoteDTO is rendered), which seems like a side-effect during render. And then, possibly throttling is introduced because it happens too often (sorry, many assumptions here, I could be wrong).
I would put the call to cacheNote() into a useEffect and make sure that it only runs when needed via the effect’s dependencies, or try invalidating more imperatively, e.g. on click of a button.
A completely different (and possibly preferred) approach would be to let react-query handle the fetching rather than doing it manually via invalidation. If you want more control over when the data is fetched, you can use the enabled flag to turn off the query depending on some state.

this is super helpful @TkDodo and what you said about side effects in render may in fact have been the issue. I think I just found it complicated to use useEffect and throttle together but I'm sure it's possible. My eventual solution is similar to what I described here with some slight modifications. Its definitely hacky and I wouldn't recommend to others but it solves a ton of issues for my use case.

Part of my final solution is to use a flag to control enabled and I toggle the flag and invalidate the query in onSuccess. This combination means I can get the query to run whenever I want to which was really the entire goal.

Part of my final solution is to use a flag to control enabled and I toggle the flag and invalidate the query in onSuccess. This combination means I can get the query to run whenever I want to which was really the entire goal.

this sounds reasonable. The enabled flag is a very powerful thing - I have actually never done a manual refetch 😅


Load data for backbone from file

I am using the FPN model from this library when I try to the run on a supercomputer, I don't have internet access to download the weight. I am using FPN with the backbone of efficient netb3. Instead of downloading the efficient data from the GitHub link is there any to load from the computer file.
@qubvel

Here are the weights that you can download directly:
https://github.com/qubvel/efficientnet/releases/
Then transfer them, along with all of your other files/scripts to your super computer to work offline.

Thanks. I just load them in encoder weights right.

Yup! You should be able to pass the weights path.

Can you please specify where exactly you entered the local path?

model = sm.Unet('resnet34', encoder_weights='weights//best_model.h5')

So you can replace encoder_weights with a local path if you want (maybe you've trained the same CNN architecture for image classification and you want to reuse it for semantic segmentation).
If you're trying to load the weights for the entire model then you just create the model and load the weights like normal:
model = sm.Unet('resnet34')
model.load_weights('best_trained_model.h5')

Thank you. :)


Error Compipling

Pods/DKPhotoGaller
    y/DKPhotoGallery/Preview/ImagePreview/DKPhotoBaseImagePreviewVC.swift:11:8:
    error: compiling for iOS 9.0, but module 'SwiftyGif' has a minimum
    deployment target of iOS 10.0:

Can we update the framework pls

How do you solve this?

Normally you can manually update the Swift version of DKPhoto Gallery to iOS10 or iOS13
or better
if ['DKImagePickerController'].include? target.name
        target.build_configurations.each do |config|
            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
        end
    end
    if ['DKPhotoGallery'].include? target.name
        target.build_configurations.each do |config|
            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
        end
    end

Thanks a lot!!!

@basilmariano Not sure exactly how or where to add this code to the podfile. I get error: [!] Invalid Podfile file: syntax error, unexpected end, expecting then or ';' or '\n'
if ['DKPhotoGallery'].in...
...                            ^~~

@basilmariano Not sure exactly how or where to add this code to the podfile. I get error: [!] Invalid Podfile file: syntax error, unexpected end, expecting then or ';' or '\n'
if ['DKPhotoGallery'].in...
...                            ^~~


Deleting OperationHandler for handling /operation endpoint on server

Replaces https://github.com/GoogleCloudPlatform/kubernetes/pull/3697
For https://github.com/GoogleCloudPlatform/kubernetes/issues/3644

Assigning to @bgrant0607 because #3697 that this replaces was.

LGTM


dataflow_runner.py: use the pbegin's pipeline

Sometimes the transform doesn't have a pipeline for a read step.

R: @robertwb

Looks like the python precommit passes: @robertwb Please merge.


Add @Deprecated annotation to deprecated JAX-RS resources for Swagger

Swagger API document displays endpoints with @Deprecated annotation
with grayed out.

@frsyuki  I guess it is better to leave comments why these APIs are deprecated.

Added some more comments.
ApiOperation is added for #1292.


Cleanup/Do not keep encryption keys in bridge memory

Storing encryption keys in memory increases the risk of vulnerabilities being exploited to obtain the keys. Therefore, it is better to adopt an approach where keys are not kept in memory and all temporary variables related to the keys are promptly cleaned up after their usage.

see https://github.com/opiproject/opi-intel-bridge/blob/e01c025c6b0af31140aee8d0c53e580cc937e0f2/pkg/middleend/middleend.go#L55

also see https://github.com/opiproject/opi-spdk-bridge/commit/bc19cac914d5174566dfc17f2823bd8f0e9fba47
need to avoid storing them in the DB


Add reveal.js support

Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
Some users of the pad used the reveal.js support to make presentations.
This a geeky feature but it really aligns with our values of putting content first.
With reveal.js you make presentation using only text and don't do any formatting.
Describe the solution you'd like
Create BlockNote plugin that makes it compatible with reveal.js

Today i was thinking about how we could implement this.
We could create a custom block, something like the block code where you can write markdown and html.
The block could have 2 buttons : preview / edit  and another one for full screen.

It could be a blockcode option like it's done for mermaid.js in outline

Ping @YousefED

Feature Request
Is your feature request related to a problem or unsupported use case? Please describe. Some users of the pad used the reveal.js support to make presentations. This a geeky feature but it really aligns with our values of putting content first. With reveal.js you make presentation using only text and don't do any formatting.
Describe the solution you'd like Create BlockNote plugin that makes it compatible with reveal.js

Interesting! Will give this some thought. Was reveal.js directly integrated in the pad? Or do you have examples of other applications where it's integrated well?

Yes it's integrated directly. You type in your content and have a menu opens a presentation view.


Connecting to digital ocean droplet using SSH fails

Bug
Environment

Platform: digital-ocean

OS: container-linux

Terraform: v0.11.5

Plugins:
provider.ct (unversioned)
provider.digitalocean v0.1.3
provider.local v1.1.0
provider.null v1.0.0
provider.template v1.0.0
provider.tls v1.1.0

Ref: 7186aa4

Problem
When DigitalOcean is used as a provider, connecting to individual droplets using SSH seems to fail. The droplet does not recognize the SSH key and asks for a password. Using the same key on a droplet which was created via the DigitalOcean UI directly works as expected, however.
Desired Behavior
Droplet login should be possible using SSH on DigitalOcean.
Steps to Reproduce
Create the cluster as described in the docs for installation on DigitalOcean. Try to login to a droplet using the SSH key corresponding to the fingerprint configured in "ssh_fingerprints".

Closed because this is not a bug but a user error. The user on the remote host is "core" and "root" will not work.


replay software   Error:There should be 'SGame_Data' folder next to the executable

Hi,I'm trying to  visualize the matches by running the  ABSTool.exe.
However, I met this error

Even after building a new folder named SGame_Data and putting my abs files under it ,the error still appears.
Could you show me which folder I should put the abs files in and how to run the ABSTool.exe?
Thx.

i have another issue ,  it dont provide a complete error information ,just like this

Hello, cjy. I think you can check and download the updated gamecore and follow the instructions carefully. Put the generated .abs file in the corresponding path, like Replays. And open ABSTool.exe to select the .abs file you want to see the visualize the game.


[Bug]: Remix is starting on the same port as create-react-app and replacing the other frontend as long as its running

Which Remix packages are impacted?

[X] remix (Remix core)
[X] create-remix
[ ] @remix-run/architect
[ ] @remix-run/cloudflare-workers
[ ] @remix-run/dev
[ ] @remix-run/express
[ ] @remix-run/netlify
[ ] @remix-run/node
[X] @remix-run/react
[ ] @remix-run/serve
[ ] @remix-run/server-runtime
[ ] @remix-run/vercel

What version of Remix are you using?
1.0.4
Steps to Reproduce
Start a CRA-app and Remix at the same time:

 npm start

> react-scripts start

Attempting to bind to HOST environment variable: localhost
If this was unintentional, check that you haven't mistakenly set it in your shell.
Learn more here: https://cra.link/advanced-config

ℹ ｢wds｣: Project is running at http://localhost:3000/
ℹ ｢wds｣: webpack output is served from
ℹ ｢wds｣: Content not from webpack is served from ...
ℹ ｢wds｣: 404s will fallback to /
Starting the development server...
Compiled successfully!

You can now view panos in the browser.

  http://localhost:3000

Note that the development build is not optimized.
To create a production build, use npm run build.

And then start remix-react:
> remix start

Remix App Server started at http://localhost:3000

(One time to reproduce I had to restart the create react again, but then the beheavior was stable, that all the time I opened some site I ended up on remix and after quitting I fell back to the other CRA)
Expected Behavior
Remix should check not only for remix-apps themselves (it's not starting at the same time), but for processes listening on the port.
Actual Behavior
We first thought, that the OS (macOS BigSur, 11.2.3) should prevent this, but no, there is a problem in node https://medium.com/@eplawless/node-js-is-a-liar-sometimes-8a28196d56b6 That beheavior of the OS is dangerous for man in the middle attacks and for building pishing sites.
How remix looks for other processes on this port?

we implemented a check for finding an unused port in remix dev in 1.2.0
I'm going to close this now, but feel free to re-open if you're still running into issues


TypeScript auto-complete only shows JSDoc for first function overload

Issue Type: Bug
Steps:

Paste this into a TypeScript file:

/** 5-arg overload */
function add(a: number, b: number, c: number, d: number, e: number): number;
function add(a: number, b: number, c: number, d: number): number;
/** 3-arg overload */
function add(a: number, b: number, c: number): number;
function add(a: number, b: number): number;
function add(...numbers: number[]) {
  let total = 0;
  for (const num of numbers) {
    total += num;
  }
  return total;
}
add(1, 2, 3, 4);

Start typing add( at the bottom to bring up auto-complete, then hit the Down arrow to go to the second overload.

Expected: The auto-complete for the second overload shows docs from the doc-comment, same as it did the first overload.
Actual: The auto-complete for the second overload does not show docs.
Additional note: If you hover over the fully completed add(1, 2, 3, 4);, which is an overload without a doc-comment, it mostly works, showing a merged version "5-arg overload 3-arg overload". This behavior is totally OK for functions where there's one single doc-block above all overloads, it's just a bit odd in the case where you document 2+ overloads but not all of them.
VS Code version: Code - Insiders 1.38.0-insider (3db7e09f3b61f915d03bbfa58e258d6eee843f35, 2019-09-03T23:11:54.533Z)
OS version: Darwin x64 18.7.0
Extensions: none

I did a bit more searching of issues, and I noticed a lot of VS Code issues were re-filed upstream on TypeScript.
So I did some searching there and found two relevant issues:

https://github.com/microsoft/TypeScript/issues/27981
https://github.com/microsoft/TypeScript/issues/30181

For the second issue, it looks like there's a PR open: https://github.com/microsoft/TypeScript/pull/30253
I'm not sure if the vscode project's policy is to leave issues open until TypeScript fixes are merged, so I'll leave it up to a maintainer to decide whether to close this one or not.

Closing as upstream


[5.1] Escape path directly in build command

Closes #11517
I've managed to replicate the issue and test it locally
We added output path escaping in late 5.1.* version.
But it should not be escaped in setter because some other stuff want to use it as it is.
For example file_get_contents() in emailOutputTo() doesn't play nice with escaped path.
Escaping right before building a crontab command is much safer.
We really lack test coverage here, but all those file_get_contents are not easy to test.
Sigh.

We really lack test coverage here, but all those file_get_contents are not easy to test.

Don't worry about mocking. Tests that actually hit the filesystem arn't massively bad. Infact, better than crazy mocking.

Has this been resolved or is it still being tested?
If it's resolved how does one apply the fix?

All three unit tests fail on Windows, because it escapes with double quotes.
Plus, in first test the generated php -i > "NUL" creates a file named "NUL". :trollface:

My mistake, just forgot NULL (2 L's) is not recognized as a keyword... Escaping "NUL" seems fine.
Still, the tests are to be fixed.


Should include an example other than a 404. I'm stuck on how to do this.

Should include an example other than a 404. I'm stuck on how to do this.

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

ID: 9421feee-5207-e379-00fb-847cc880014c
Version Independent ID: 8415adee-793e-2ba7-b97b-672b493ba42b
Content: Test ASP.NET Core middleware
Content Source: aspnetcore/test/middleware.md
Product: aspnet-core
Technology: aspnetcore-test
GitHub Login: @Tratcher
Microsoft Alias: riande

Hi @NealCallaghan. Thanks for the feedback. What exactly is it that you're getting stuck with here?

Hi. I agree with @serpent5 's sentiment.
The title is called "Test ASP.NET Core middleware", and the examples contain references to the type MyMiddleware, but we're not given any insight as to the context of what is being tested, i.e. we don't know what MyMiddleware look like.
What, for example, could a person do to check whether or not the "next" request delegate has been called (under certain conditions)?

Comments on closed issues are not tracked, please open a new issue with the details for your scenario.