ERROR: Network outputted NaN for "loss_bbox" (Train phase). Try decreasing your learning rate.

Hi there!
I'm trying to use Detectnet network on DIGITS to detect blood vessels in ultrasound images (only one blood vessel per image).
At first, I tried to use Detectnet, with Lenet instead of Googlenet (because I'm sure that Googlenet is too big for my needs), but I couldn't make it work. Later on, I decided to use the original Detectnet network, yet the data images I use are originally 128x128 pixels and grayscale. So I had to do some resizing (512x512) so that its easier for the network to place the bounding box and convert the images to RGB.
For the images of the labels I use the following format:
car 0.0 0 0.0 126.0 172.0 317.0 318.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
I have checked it out, and the bounding box usually is between 50x50 and 400x400 pixels, so that shouldn't be a problem.
The following error occurred in the vast majority of my tests: ERROR: Network outputted NaN for "loss_bbox" (Train phase). Try decreasing your learning rate.
I also tried all different types of solver types and very low learning rates (even 0), and yet I keep getting the same error.
https://stackoverflow.com/questions/33962226/common-causes-of-nans-during-training?noredirect=1&lq=1
Here I saw the most common causes of NaNs during training, but I cannot see which one should be the one I'm facing...

Gradient blow up: I've tested it with learning rate of 0 and I keep getting the error.

In this image we can see how in a test with learning rate 0, the loss_bbox (train) went to a really, really high number. It just stop before getting a NaN, but sometimes it does get to NaN.

Faulty Loss function: I don't think it is this one because the network is not designed by me...

Faulty input: For all the images and labels, I do a very careful search for NaNs or errors of any kind, so that should not be the cause of the problem. In fact, I tried to run the network with few images and labels which I was 99% sure they were correct, and still the error happens to occur at some point.

stride larger than kernel size in "Pooling" layer: I've checked all pooling layers and the have the kernel size larger than the stride.

In addition, if the error happens in the 30 epoch for example, and I try to test one of the first images, I can see that the network is not placing the Bounding Box. I have heard that mAP usually takes more than 30 epoch to be non-0, so I guess it's normal, but I still point it out in case it's important.
I want to point out that I haven't used any information of the pre-trained Googlenet network because the Imagenet dataset and the dataset I'm working with are really different.
Finally, I also changed the probability of placing a bounding box with a line like this:
param_str: "512, 512, 16, 0.03, 3, 0.02, 10,1" but the error is still occurring.
Do you guys have any idea of what could be going wrong? Any kind of help would be appreciated.
Here is an image of what one of the last tests looked like:

I also attach the caffe_output.log document so you can check the layout of the network and the information of the errors:
caffe_output.txt
Finally, here is the network I'm using:
detectnet.txt
Thank you for your time and I'm looking forward to reading your answers!

Do you have (many) images with no bounding boxes at all by any chance?

Thanks for the answer, gheinrich.
No, all the images have one and only one bounding box. Do you think this could cause a problem?

That shouldn't be an issue... I encourage you to try using a pre-trained model (from Imagenet) even if your images appear different to you. A lot of the low-level filters (e.g. edge detectors) can be reused. I've never seen a case where it didn't help.

Thanks for the tip, In the last attempt I've used a pre-trained model and I'll keep doing it in the future.
But, even with the pre-trained model, the same error is appearing.
I've thought about changing the source code for, instead of returning an error when the NaN appears, just change the value of loss_bbox for a really, really, big number. Do you think this could be useful or this will affect negatively to the final result?

I have just changed the database for another smaller (in number of images, they still are 512x512), directly from the internet (not related to ultrasound images) and hand-labeled. The same error has appeared even with learning rate = 0.
I have no idea of what could be causing it, but the cause doesn't seem the be the database, unless the labeling format used (car 0.0 0 0.0 126.0 172.0 317.0 318.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0) is not correct.

Is it solved? I have the same problem.

Same problem here too.

I am also facing this problem. Although i am using KITTI dataset i am getting same error ERROR: Network outputted NaN for "loss_bbox" (Train phase). Try decreasing your learning rate..
Is here anyone who encounter this problem.?

Hey, sorry for letting this post go unresolved for so long; I forgot to update this thread after the solution was found.
After some work on it, I finally managed to get some nice results. Apparently the network was totally fine. The way we solved it is by getting a bigger GPU, with more memory, so a bigger batch size could be used.
I know it's a disappointing way of solving the issue - just buy a better GPU - but it worked fine so we stopped spending our time and resources on solving the problem with the initial requirements. I hope you guys struggling with this error have better luck with it!

Hi Alex,
Thanks for replying.
I have NVIDIA DIGITS with 4 GPUs each have 12GB memory. Can you please tell
me now which batch size and batch accumulation size now should I select
for KITTI dataset training.? Also please tell me which learning rate is to
be set for this dataset.?
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Dec 5, 2017 at 9:03 PM, AlexPalauDomenech<EMAIL_ADDRESS>wrote:

Hey, sorry for letting this post go unresolved for so long; I forgot to
update this thread after the solution was found.
After some work on it, I finally managed to get some nice results.
Apparently the network was totally fine. The way we solved it is by getting
a bigger GPU, with more memory, so a bigger batch size could be used.
I know it's a disappointing way of solving the issue - just buy a better
GPU - but it worked fine so we stopped spending our time and resources on
solving the problem with the initial requirements. I hope you guys
struggling with this error have better luck with it!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIA/DIGITS/issues/1288#issuecomment-349284602, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AcrU8Dr94IKCEKFp39CfIL2VFI-ETEseks5s9TEYgaJpZM4K4RSx
.

--
Best Regards,
Syed Ibrahim Hassan
*Research Assistant *
Computer Vision Lab.
Sejong University, Seoul, South Korea


PMID:16360688

Equational sister chromatid separation at meiosis I
is_a abnormal meiotic sister chromatid segregation
not sure what has been used before for this
need a term like this without the "kinetochre  dissociation part"
FYPO:0005633	sister kinetochore dissociation in meiotic metaphase I, normal chromosome segregation in meiosis I, and unequal sister chromatid segregation in meiosis II
primary name
"nondisjunction at meiosis II"

sister chromatid non-disjunction at meiosis II

obsolete
abolished meiotic sister chromatid separation (1 annotation)
same meaning as
unequal meiotic sister chromatid segregation in meiosis II
(because id you are unequal you haven't separated)
relabel
unequal meiotic sister chromatid segregation in meiosis II
to
"sister chromatid nondisjunction at meiosis II"


warnings of validations while signing in

Describe the bug
validations gives warning while filling the fields in sign in

Already fixed, you need to pull development

closed by the fixes of #174


Added a great book

Added "Hacking: The Art of Exploitation" to the "Other" category

[ x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@cpk86 Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality >standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


Training: image-based batch size can lead to very uneven batches

Mini-batch size calculation:
    # Calculate max nbr images to keep in memory (for 5000 samples total).
    max_imgs_in_memory = 5000 // labels.samples_per_image

samples_per_image is taken from the first image in the input:
    @property
    def samples_per_image(self):
        return len(next(iter(self.data.values())))

So I tried a training job where the first image has 10 points, followed by a bunch of images with 1000 points (unheard of for a single CoralNet source, but possible if multiple sources are incorporated). Logs confirmed that it decided on 500 images per mini-batch. Then it got this:
Traceback (most recent call last):
  File "/workspace/spacer/spacer/tasks.py", line 122, in process_job
    results.append(run[job_msg.task_name](task))
  File "/workspace/spacer/spacer/tasks.py", line 45, in train_classifier
    clf, val_results, return_message = trainer(
  File "/workspace/spacer/spacer/train_classifier.py", line 50, in __call__
    clf, ref_accs = train(train_labels, feature_loc, nbr_epochs, clf_type)
  File "/workspace/spacer/spacer/train_utils.py", line 83, in train
    clf.partial_fit(x, y, classes=classes)
  File "/usr/local/lib/python3.10/dist-packages/sklearn/neural_network/_multilayer_perceptron.py", line 1215, in partial_fit
    super().partial_fit(X, y)
  File "/usr/local/lib/python3.10/dist-packages/sklearn/neural_network/_multilayer_perceptron.py", line 790, in partial_fit
    return self._fit(X, y, incremental=True)
  File "/usr/local/lib/python3.10/dist-packages/sklearn/neural_network/_multilayer_perceptron.py", line 394, in _fit
    X, y = self._validate_input(X, y, incremental, reset=first_pass)
  File "/usr/local/lib/python3.10/dist-packages/sklearn/neural_network/_multilayer_perceptron.py", line 1109, in _validate_input
    X, y = self._validate_data(
  File "/usr/local/lib/python3.10/dist-packages/sklearn/base.py", line 596, in _validate_data
    X, y = check_X_y(X, y, **check_params)
  File "/usr/local/lib/python3.10/dist-packages/sklearn/utils/validation.py", line 1074, in check_X_y
    X = check_array(
  File "/usr/local/lib/python3.10/dist-packages/sklearn/utils/validation.py", line 856, in check_array
    array = np.asarray(array, order=order, dtype=dtype)
numpy.core._exceptions._ArrayMemoryError: Unable to allocate 4.53 GiB for an array with shape (475192, 1280) and data type float64

This machine had close to 16 GB RAM, so maybe there were multiple similarly large arrays in memory at the time (which might indicate a bit of memory optimization to be done in the code). But the point is, the batch size is supposed to be part of the instance-requirements design. Also, I imagine that the intent of the training algorithm is to have somewhat uniform batch sizes, and having them vary so much may be considered an improper implementation with undefined behavior. So making the batch size consistent (in annotation count) regardless of variable points per image seems worthwhile, as long as it's not a big implementation chore.
I've actually been working on this, issue #59, and issue #60 together as they touch common parts of the code, but I wanted to document this behavior while I was at it.

Resolved in PR #71. The batch size no longer cares about points per image, and in addition, it no longer cares about image 'boundaries' at all. So a single image's points can go into multiple batches. A generator function made this decently clean to code (IMO).
Note that the preprocess_labels() train/ref/val split is still done on the image level though, not the point level. But I think that's acceptable because: it may make the sets simpler to reason about, the potential unevenness isn't nearly as bad as the original issue, and it's still possible to make your own train/ref/val split that has a single image in multiple sets.


Feature: Service Discovery

Support a DNS based for registering and discovery of "Services" across multiple environments.
Support for a basic "Red/Green" health checks.

There have been some strides with (Registrator)[https://github.com/progrium/registrator] and consul. Maybe that could be pulled in or used. I think that the maintainer may be interested for this to be pulled in somewhere else as I know he has been sponsored for work on Dokku his pet project.


Segfault with shapely operations using fiona and shapely wheels

@sgillies I'm getting a segfault on OSX using the latest Python 3.6 wheels for Fiona and Shapely. Here's the steps to reproduce:
Set up a virtual env with wheels
⭆ virtualenv -p python3.6 /tmp/segfault
⭆ source /tmp/segfault/bin/activate
⭆ pip install shapely fiona
Collecting shapely
  Downloading Shapely-1.6.2-cp36-cp36m-macosx_10_6_intel.whl (2.8MB)
Collecting fiona
  Using cached Fiona-1.7.9.post1-cp36-cp36m-macosx_10_6_intel.whl
...

Run the following python script
#!/usr/bin/env python3.6

# import fiona
from shapely.geometry import shape

a = shape(
    {'type': 'Polygon',
     'coordinates': ((
         (-179.95983122707207, 85.04766197798072),
         (-179.95983122707207, 85.04321428424322),
         (-179.90833283542793, 85.04321428424322),
         (-179.90833283542793, 85.04766197798072),
         (-179.95983122707207, 85.04766197798072)),)})

b = shape(
    {'type': 'Polygon',
     'coordinates': ((
         (-179.9222362115971, 85.04614454850956),
         (-179.9222362115971, 85.04728275377343),
         (-179.93883444063917, 85.04728275377343),
         (-179.93883444063917, 85.04614454850956),
         (-179.9222362115971, 85.04614454850956)),)})

print("Is b within a?")
print(b.within(a))

This works as expected. But if we import fiona before the shapely import, we get a Segmentation fault: 11.
Importing Fiona after Shapely seems to work. And when either Fiona or Shapely is installed from source (e.g. with pip install --no-binary :all: fiona shapely) the segfault disappears. So it appears to be some interaction between Shapely and Fiona wheels.
I haven't been able to reproduce on Linux yet, OSX only so far.

@perrygeo the shapely and fiona wheels have different versions of GEOS. Fiona doesn't care, but it matters to Shapely. I've got new Fiona 1.7.10 wheels coming up that won't mess with Shapely 1.6.1 or 1.6.2.

@sgillies still hitting the segfault with Fiona 1.7.10
⭆ pip install shapely fiona
Collecting shapely
  Using cached Shapely-1.6.2-cp36-cp36m-macosx_10_6_intel.whl
Collecting fiona
  Using cached Fiona-1.7.10-cp36-cp36m-macosx_10_6_intel.whl
...
⭆ python try.py
Is b within a?
Segmentation fault: 11

Argh.
Here's the stack trace using Shapely 1.6.2 and Fiona 1.7.10. GEOS 3.6.2.
$ lldb python
(lldb) target create "python"
Current executable set to 'python' (x86_64).
(lldb) run try.py
Process 33823 launched: '/Users/sean/envs/162_1710/bin/python' (x86_64)
Is b within a?
Process 33823 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x7fff5afffff8)
    frame #0: 0x00007fffd934fdea libc++abi.dylib`__cxxabiv1::__vmi_class_type_info::search_below_dst(__cxxabiv1::__dynamic_cast_info*, void const*, int, bool) const + 12
libc++abi.dylib`__cxxabiv1::__vmi_class_type_info::search_below_dst:
->  0x7fffd934fdea <+12>: pushq  %rbx
    0x7fffd934fdeb <+13>: subq   $0x18, %rsp
    0x7fffd934fdef <+17>: movl   %r8d, %r13d
    0x7fffd934fdf2 <+20>: movl   %ecx, -0x2c(%rbp)
Target 0: (python) stopped.
(lldb) up
frame #1: 0x00007fffd934feaa libc++abi.dylib`__cxxabiv1::__vmi_class_type_info::search_below_dst(__cxxabiv1::__dynamic_cast_info*, void const*, int, bool) const + 204
libc++abi.dylib`__cxxabiv1::__vmi_class_type_info::search_below_dst:
    0x7fffd934feaa <+204>: addq   $0x10, %rbx
    0x7fffd934feae <+208>: cmpq   %r12, %rbx
    0x7fffd934feb1 <+211>: jb     0x7fffd934fe8b            ; <+173>
    0x7fffd934feb3 <+213>: jmp    0x7fffd9350066            ; <+648>
(lldb) up
frame #2: 0x00007fffd934fb2c libc++abi.dylib`__dynamic_cast + 281
libc++abi.dylib`__dynamic_cast:
    0x7fffd934fb2c <+281>: movq   -0x48(%rbp), %rax
    0x7fffd934fb30 <+285>: movq   %rax, %rcx
    0x7fffd934fb33 <+288>: shrq   $0x20, %rcx
    0x7fffd934fb37 <+292>: orl    %eax, %ecx
(lldb) up
frame #3: 0x00000001043766dc libgdal.20.dylib`geos::operation::predicate::RectangleContains::isContainedInBoundary(geos::geom::Geometry const&) + 92
libgdal.20.dylib`geos::operation::predicate::RectangleContains::isContainedInBoundary:
    0x1043766dc <+92>:  movq   %rax, -0x58(%rbp)
    0x1043766e0 <+96>:  jmp    0x1043766f2               ; <+114>
    0x1043766e5 <+101>: xorl   %eax, %eax
    0x1043766e7 <+103>: movl   %eax, %ecx

I'm going to find Shapely and Fiona versions using a different GEOS.

Same problem with Shapely 1.6.0 + Fiona 1.7.9.post1 (frs-wheel-builds 1.4.0). At least with Python 3.6.

Results of analysis of Python 2.7 macosx wheels on PyPI are in. I'm almost certain they apply to the other Python versions.
The first (in time) wheel combination that breaks is Shapely 1.6b5 and Fiona 1.7.7. Shapely 1.6b4 works with all Fiona wheels from 1.7.1 to 1.7.10. Fiona 1.7.6 works with all Shapely wheels from 1.6b4 to 1.6.2.
Now to track down the actual build bug now that we've found where it lives in time.

The most recent change to frs-wheel-builds before Shapely 1.6b5 or Fiona 1.7.7 is this: https://github.com/sgillies/frs-wheel-builds/blob/master/CHANGES.txt#L18-L28. My hypothesis is that it's the macosx deployment target. I'm testing by building Fiona 1.7.10 using the old 10.6 target (if possible.

Good news! GDAL 2.2.2 builds with XCode 8.2.1 MACOSX_DEPLOYMENT_TARGET=10.6 and --without-cp11 where GDAL 2.2.0 did not.

Same crash with the MACOSX_DEPLOYMENT_TARGET=10.6 wheels :(.
Next thing to try is reverting to GDAL 2.1.3.

There's a chance this has almost nothing to do with GDAL and my build configuration.
After finding that reverting to frs-wheel-builds 1.3.0 didn't help (same error), I noticed my Xcode and command line tools were out of synch. How this happened, I'm not sure, but by reverting my command line tools to match Xcode 8.2.1 I'm able to get pairs of Shapely and Fiona wheels that don't crash each other. More details soon.

I can't find any evidence that the problem was anything other than Xcode mis-configuration.
Summary here: https://sgillies.net/2017/10/31/trued-macosx-wheels.html.


Efficiency, not effectivity

All visible references to the Efficiency modules use "effectivity" (its internal name) instead of "efficiency".

I am closing this as a duplicate of #92, as it is a subset of that problem.


api/uniform/registration is POST, should be GET request

When I load Uniform page in UI I see "api/uniform/registration" is a POST request and the response is the data of the page which is loaded.

a comment from the developer in scope of this issue:
we would need to move that logic to the bridge-server, because with GET we can't send any body.

The list of timestamps can potentially be huge and thus, the team preferred to use a POST API.
This API is also not public facing.


docs(readme): remove c4 models

Moved c4 models to the internal sepes repo
fixed markdownlint warnings in readme.md

fyi @HansKristianVikOlsen


Translation for VolumeDisplayPresets.json

Was mapped in issue #41, the tooltip(when you hover the cursor) from the predefinitions still appears in English.

As mentioned by @lassoan,

Need to implement translation for Modules\Loadable\Volumes\Resources\VolumeDisplayPresets.json - similarly to how CLI module descriptor .xml files are translated.

Similar preset translations would be needed for:

Color tables (Base\Logic\Resources\ColorFiles)
Volume rendering presets (Modules\Loadable\VolumeRendering\Resources\presets.xml)

A new extract_translatable_from_volume_rendering_presets(...) function could be added to Utilities\Scripts\update_translations.py that would be called similarly to extract_translatable_from_cli_modules(...).


don't receive LOG on my gmail...

Please fix it...
I run it and don't receive anything from it, Even i enable "Less secure apps" in gmail

I have a similar issue too. no logs even with the "less secure apps" enabled. Tried multiole gmails

Clone from this link https://github.com/jinwei908/BeeLogger you will start getting logs after this.

I cloned it from that link I still don't get the logs to my gmail.


MovieClip HTML5 frame labels not loading

In the HTML5 target, a Movie Clip's frame labels list is empty. I have a MovieClip that has a main timeline with frame labels:
var future = AssetLibrary.loadFromFile ("myswf.bundle");
future.onComplete (library_onComplete);

//function library_onComplete
var clip = library.getMovieClip ("");
addChild (clip);
clip.gotoAndStop( "SomeFrameLabel" );

Upon tracing out clip information, currentFrameLabel, and currentLabel are null and currentLabels is empty []. currentFrame seems to accurately report the frame number. The frame label information seems to be contained in swflite.dat file, but perhaps not processed into the array of FrameLabel. Other than this, the logic looks like it should work at first glance.
target: HTML5
openfl: 4.9.2
lime: 4.0.3

This also appears to be working, I updated my sample project from https://github.com/openfl/openfl/issues/1552 like this:
var clip = library.getMovieClip ("");

		trace (clip.currentFrameLabel);
		trace (clip.currentLabel);
		trace (clip.currentLabels);

		addChild (clip);
		clip.gotoAndStop( "SomeLabel" );

		trace (clip.currentFrameLabel);
		trace (clip.currentLabel);
		trace (clip.currentLabels);

		clip.stop();

It's behaving as I would expect 😕


ReadsToDistmap: dump sam header somewhere (feature request)

Following up on this idea of working with a bam pipeline and uploading the demultiplexed bams, it would be super useful if you could also dump the SAM header in a user-specified location.

Thanks for the proposal - that's a really easy feature to include: just requires a new optional boolean argument (default: false) and before starting processing output the formatted header into the output path. Do you want to give it a try to start your first contribution, @robmaz?
By the way, what do you mean with the bam-pipeline?

What I have in mind specifically is that people would demultiplex the raw data with readtools already using the various options to assign maximally informative readgroups, and then directly submit the generated bams to distmap (I believe this also was a long-standing plan of yours).  The current problem is that the conversion to the tabbed pseudo-fastq in between loses the carefully constructed header and RG info. Saving the header and then merging it back in on download would solve that problem. (The GATK pipeline suggests a similar procedure, as you probably know.)

I can find some issues arising from this:

If a multi-RG SAM/BAM file is converted to a pseudo-fastq, assigning the @RG requires to assign the barcode again.
The distmap output is a SAM/BAM file with it's own header, and thus download something that might have already a @RG header might generate conflicts (see my concerns in https://github.com/magicDGS/ReadTools/issues/511#issuecomment-415497816).

I think that a way to make this easier and happening in Distmap will be to discuss a new format (e.g., the tfq from #404) where we can construct a distmap-specific read name containing the information required (e.g., @{{read_name}}#1:{{barcode_seq}} will indicate the read group index from the header) or have two options to avoid barcode/read-group lost (@{{read_name}}#{barcode_req}} if no read-group is present like in a FASTQ file, and @{{read_name}}#{{rg_id}} for cases where read-group is present, but it will lose the BC tags). We should probably have a different issue for discussing this distmap-pipeline integration, as different issues open without any connection will make this impossible to discuss in an organize way.


Difference on time series labels between versions

Different versions, different results.
How can I, using v2.8 have the same labels on x axis as the v2.6.
The problem is that the first and last label are missing when using v2.8.
Links to reproduce:
v2.6: https://jsfiddle.net/2avdLxbk/
v2.8: https://jsfiddle.net/2avdLxbk/1/
I already tried:
...
stepSize: 10,
unit: 'second',
tooltipFormat: 'HH:mm:ss'
...

and:
...
autoSkip: false
...

You are using time scale like category scale.
example
When you specify labels, those are strings and the length of that string is affecting the display of ticks (this might be a bug).
For time scale, I think you have to use {x, y} data (and no labels).

Seems like the previous answer covered this and this issue is quite old


[LinalgToXeGPU] Lower linalg.matmul_transpose_b into xegpu.dpas

Closes #340
Support lowering of linalg.matmul_transpose_b as well as linalg.transpose %b + linalg.matmul %a %b into xegpu.dpas.
To make a transposed multiplication we have to load B chunks with xegpu.load_nd ... <transpose = array<i64: 1, 0>> attribute and also change the iteration dimension (from rows to cols).

This seem to be almost generic enough to support transpose A and the batched transposed versions. Could you try making the interfaces amenable to all the matmul variations? Implementation can stay as is.

Regarding batched transpose: at the moment there's no support for either linalg.batch_matmul or for linalg.batch_reduce_matmul in linalg-to-xegpu pass. Trying YOLO approach by simply adding those ops to the list of allowed ops causes a segfault, so probably a different handling is needed in those cases. Anyway, the 'transpose_b' logic shouldn't change at all if createDPASKernel() would support batched matmuls sometime. You would just need to add BatchMatmulOp everywhere and it should work.

Regarding 'transpose A': this one also requires special handling. Following the current logic of createDPASKernel() we can't use transpose attribute of xegpu.load_nd to transpose A argument since it only can transpose 32bit blocks (and we only support f16 in our lowering). This means, that instead of using xegpu.load_nd <transpose> we would need to use vector.transpose on the loaded vector. Since it doesn't correlate with the changes in this PR and seems like a separate feature, I would propose to consider it as a separate issue (#361). Anyway, the general logic of detecting "if there's a transpose before matmul" stays the same. Added an argument to findAndReplaceTranspose() function indicating which matmul operand we're processing.
Example of why 32bit transpose causes problems for f16 data
A(f16): // original matrix
[1,   2,  3,  4]
[5,   6,  7,  8]
[9,  10, 11, 12]
[13, 14, 15, 16]

xegpu.load_nd A(f16) <transpose>: // transposed 32bit blocks
[1, 2,  9, 10]
[5, 6, 13, 14]
[3, 4, 11, 12]
[7, 8, 15, 16]

vector.transpose A(f16): // expected transpose result
[1, 5,  9, 13]
[2, 6, 10, 14]
[3, 7, 11, 15]
[4, 8, 12, 16]

Why it doesn't cause any problems for B argument
In contrast with 'A' argument we load 'B' with 'packed/vnni' attribute which apparently involves some special handling which is properly aligned with our needs of B transpose.

P.S. there's transpose_bit_width attribute that should in theory solve this problem, but setting it to 16 does nothing. Not sure if this an intended behavior or just a bug in xegpu-to-vc-func lowering. Submitted a question to IMEX (intel/mlir-extensions#895).

This seem to be almost generic enough to support transpose A and the batched transposed versions. Could you try making the interfaces amenable to all the matmul variations? Implementation can stay as is.

Regarding batched transpose: at the moment there's no support for either linalg.batch_matmul or for linalg.batch_reduce_matmul in linalg-to-xegpu pass. Trying YOLO approach by simply adding those ops to the list of allowed ops causes a segfault, so probably a different handling is needed in those cases. Anyway, the 'transpose_b' logic shouldn't change at all if createDPASKernel() would support batched matmuls sometime. You would just need to add BatchMatmulOp everywhere and it should work.

Regarding 'transpose A': this one also requires special handling. Following the current logic of createDPASKernel() we can't use transpose attribute of xegpu.load_nd to transpose A argument since it only can transpose 32bit blocks (and we only support f16 in our lowering). This means, that instead of using xegpu.load_nd <transpose> we would need to use vector.transpose on the loaded vector. Since it doesn't correlate with the changes in this PR and seems like a separate feature, I would propose to consider it as a separate issue ([LinalgToXeGPU] Support linalg.matmul_transpose_a #361). Anyway, the general logic of detecting "if there's a transpose before matmul" stays the same. Added an argument to findAndReplaceTranspose() function indicating which matmul operand we're processing.
Example of why 32bit transpose causes problems for f16 data
A(f16): // original matrix
[1,   2,  3,  4]
[5,   6,  7,  8]
[9,  10, 11, 12]
[13, 14, 15, 16]

xegpu.load_nd A(f16) <transpose>: // transposed 32bit blocks
[1, 2,  9, 10]
[5, 6, 13, 14]
[3, 4, 11, 12]
[7, 8, 15, 16]

vector.transpose A(f16): // expected transpose result
[1, 5,  9, 13]
[2, 6, 10, 14]
[3, 7, 11, 15]
[4, 8, 12, 16]

Why it doesn't cause any problems for B argument
In contrast with 'A' argument we load 'B' with 'packed/vnni' attribute which apparently involves some special handling which is properly aligned with our needs of B transpose.
P.S. there's transpose_bit_width attribute that should in theory solve this problem, but setting it to 16 does nothing. Not sure if this an intended behavior or just a bug in xegpu-to-vc-func lowering. Submitted a question to IMEX ([xegpu-to-vc-func] Is transpose_bit_width=16 supported? mlir-extensions#895).

Sure, I did not suggest adding support for other flavors right away, only to make the interfaces friendly. Supporting other matmuls is a separate issue.

There's also the bool transpose param in a couple places that could be generalized but that's a minor thing.

This bool parameter is used in functions that also take a matmul operand, so this parameter can be used with both of the operands (and with any matmul op). Is this generic enough or you had something else on your mind?
bool transposeA = true;
bool transposeB = false;

auto tilesA = createTiles(matA, ..., /*transpose=*/transposeA);
auto tilesB = createTiles(matB, ..., /*transpose=*/transposeB);

There's also the bool transpose param in a couple places that could be generalized but that's a minor thing.

This bool parameter is used in functions that also take a matmul operand, so this parameter can be used with both of the operands (and with any matmul op). Is this generic enough or you had something else on your mind?

bool transposeA = true;

bool transposeB = false;

auto tilesA = createTiles(matA, ..., /*transpose=*/transposeA);

auto tilesB = createTiles(matB, ..., /*transpose=*/transposeB);

Yup. Sounds good!


Convert units to SI

You would enter a command and the bot will respond with a message where the imperial units will be converted to SI

@diminDDL can do this :trollface:

I assigned myself to it for a reason

This should be part of the units implementation.

implemented in beefdf9

Things to still add to the lookup table:
temperatures


test: add code cov to ut

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


[rust] make a musl build

ct does not work on alpine (non glibc env). Make a build that work under alpine

It is properly working starting with 1.0.4 builds.


NSHTTPURLResponse missing an init method

initWithURL:statusCode:HTTPVersion:headerFields: missing

Fix is available in 0.1 Preview (December 3, 2015)


Make path-prefixing of served HTTP routes optional.

This allows use cases where one wants to use the Prometheus UI through a
proxy which maps only a trailing part of the proxied path to the backend
path.
Fixes https://github.com/prometheus/prometheus/issues/1191

@fabxc @brian-brazil @neelance This PR may serve as a basis for discussion for how to solve https://github.com/prometheus/prometheus/issues/1191... I know that adding boolean flags is not great, but I couldn't think of a better way at the moment.

Ugh. I'd love to find a different solution than adding another flag.

@grobie Me too :) So if anyone can think of something brilliant...

any chance we could get this into the main branch?

See #1191 – there is an alternative proposal now too.

Obsoleted by #1791


Doesn't translate messages

I think in di.php incorrect 'tags'(need 'translation.categorySource'?)
Additional info

Q
A

Version
3

PHP version
8.2

Yes. Likely. Would you please try?

Yes, I tried. After changed it worked

https://github.com/yiisoft/yii-dataview/blob/master/tests/GridView/TranslatorTest.php

@terabytesoftw I see that tests are using different container config than what's in config, right? Maybe that's the issue?

Done by #132


Opening the same wallet multiple times should no-op

:tada: This issue has been resolved in version 1.0.0-dev.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Debugger] Unable to run modules with following launch configurations

Description:
Unable to run modules with following launch configurations
Steps to reproduce:
 {
            "type": "ballerina",
            "request": "launch",
            "name": "GRPC Service",
            "script": "${workspaceRoot}/grpc_service",
            "networkLogs": true
        },
        {
            "type": "ballerina",
            "request": "launch",
            "name": "GRPC Client",
            "script": "${workspaceRoot}/grpc_client",
            "networkLogs": true
        },

Suggested Labels (optional):
Component/Debugger,
Component/VScode Plugin
Sample
https://github.com/ballerina-guides/backend-for-frontend/blob/master/README.md/

@srsharon what is the error you get?


fix(security): address CVE-2019-5413

https://github.com/advisories/GHSA-gwg9-rgvj-4h5j

@charellesandig Yup, assigning now. Thank you!


mesh: Race condition when processing message segments

Moved from https://github.com/apache/mynewt-core/issues/1433
Original description:
"I found a multi-thread safety issue in mesh stack code and it still exist in the newest version.
When "seg_ack" was called by callout module, there was anthoer thread which receive mesh datas was calling "seg_rx_reset()" and set the "rx->sub" to NULL, then "seg_ack" called "send_ack" and acess the rx->sub->net_idx, so it crashed.
The adv-sending task and ble-data-receiving task and each "callout" are not in the same thread, why don't you add the Multi-thread protection mechanism in mesh stack? or something I used the wrong way?
Waiting for your replies! thank you so much!"
by @justabetterman

@justabetterman Are you able to reproduce this issue?

There was already an issue in nimble https://github.com/apache/mynewt-nimble/issues/199. Closing this one.


Add unapply.

Codecov Report

Merging #108 into master will decrease coverage by 0.05%.
The diff coverage is 37.5%.

@@            Coverage Diff             @@
##           master     #108      +/-   ##
==========================================
- Coverage   27.91%   27.85%   -0.06%
==========================================
  Files          49       49
  Lines        1254     1260       +6
  Branches       48       40       -8
==========================================
+ Hits          350      351       +1
- Misses        904      909       +5

Impacted Files
Coverage Δ

.../scalax/fsn/common/helper/FAtomicValueHelper.scala
26.92% <0%> (-3.52%)
:arrow_down:

.../main/scala/net/scalax/fsn/core/FAtomicValue.scala
50% <60%> (-16.67%)
:arrow_down:

Continue to review full report at Codecov.

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


Some configurations are not reflected in the drivers.js

Some configurations are not only applicable for the generation of api-schema, resolvers and which driver to select etc.. Some are also relevant when actually running the driver (as they are setup now).
Currently field_for_creation_date and field_for_last_update_date are both expected to always be set to true in the driver, and actually setting them to false would lead to errors when creating objects etc., as the driver would try to insert fields that does not exists.
How to solve this might not be obvious. My suggestions would be to either keep keep the relevant configurations as actually values in the drivers file(s), or have lines in the driver(s) files that are added/removed dynamically during generations depending on the configurations.
I should have realized this earlier....
@hartig @keski @rcapshaw

@keski do you have an opinion of what might be a good way to address this?

Let's leave this issue open for the time being. It's not an actual problem for SPIRIT, but it may become an issue for other projects that use woo.sh and don't want the automatically maintained creationDate and lastUpdateDate fields.

I believe that currently field_for_creation_date and field_for_last_update_date are the only things really affected in the driver, since all other features simply unavailable in the generated API schema. This means we don't have to remove large chunks from the driver or rearrange the code, but simply toggle the inclusion of the date fields.

Okay.


fix test

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.84%. Comparing base (efe5ba2) to head (743f355).
Report is 23 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #59   +/-   ##
=======================================
  Coverage   92.84%   92.84%
=======================================
  Files          40       40
  Lines         699      699
  Branches       98       98
=======================================
  Hits          649      649
  Misses         46       46
  Partials        4        4

Flag
Coverage Δ

frontend
92.84% <ø> (ø)

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

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


shimv2: handle ctx passed by containerd

Sometimes shim process cannot be shutdown because of container list
is not empty. This container list is written in shim service, while
creating container. We find that if containerd cancel its Create
Container Request due to timeout, but runtime didn't handle it properly
and continue creating action, then this container cannot be deleted at
all. So we should make sure the ctx passed to Create Service rpc call
is effective.
Fixes: #2992

/test

cc @lifupan @liubin

How does it affect other CRIs?

@YvesChan do you think you could create a test case that specifically tests that scenario?

How does it affect other CRIs?

Since I'm using containerd in my environment, I can only confirm this patch works for containerd right now. But I think this patch will only enhance the robustness of runtime/shimv2 but not do any harm?

@YvesChan do you think you could create a test case that specifically tests that scenario?

I have reproduced this issue in my environment but it's a little bit complicated to configure. Let me try to simplify it first.

/test

How does it affect other CRIs?

This fix will work for any other CRIs which compatible with shimv2  api.

Thanks @YvesChan. Please review the CI failures though - shimv2 tests are failing with SEGV...

/cc @cmaf as this may impact #2980.

@YvesChan - there are a lot of failing CI's - have you looked at the logs to see why?

@YvesChan - there are a lot of failing CI's - have you looked at the logs to see why?

Working on it. It seems the TestCreateContainerFail did not pass correctly.

/test

/test

@crosbymichael - could you respond to @YvesChan's comment so we can progress this? It's unclear if your comment are an ack or a nack?

I've opened an issue for the failure on jenkins-ci-podman-clh-fedora-31: https://github.com/kata-containers/tests/issues/2946
It's not related to this series.

Hi @YvesChan - It looks like this hasn't been ported to 2.x (https://github.com/kata-containers/kata-containers/tree/2.0-dev/src/runtime) yet. Would you be able to look at doing that?

Hi @YvesChan - It looks like this hasn't been ported to 2.x (https://github.com/kata-containers/kata-containers/tree/2.0-dev/src/runtime) yet. Would you be able to look at doing that?

OK, I'll do it later

forward port pr: https://github.com/kata-containers/kata-containers/pull/1166


data:pritamrajput

I want to contribute to the linkfree project by creating my profile on Linkfree.

My PR is not merged yet

My PR is not merged yet

Your PR will be merged once another maintainer approves it. 🙂

My PR is not merged yet

Your PR will be merged once another maintainer approves it. 🙂

okay thanks for the reply 🙂


Support more named timestamps

As of #250, cli/src/argparse/args/time.rs contains parsers for a few named timestamps such as tomorrow and today, but not all.
Add the rest -- at least, those which are not specific to a culture other than "international business" (that is, "eocq" makes sense as "quarter" is a business-culture thing, but "ascencion" does not).  We want to avoid privileging any one culture as we cannot possibly support all cultures.
We may at some point allow localization (local names for days, months, etc.) but that is not part of this issue.

Oops, @gravityvi fixed this!


base functionality to create aws resources

Closes #279 with basic functionality. Would love some feedback on making this more robust.

I didn't look in details yet but could you please rename minion to node?https://github.com/kubernetes/kubernetes/issues/1111

@Smana I tested @rsmitty code I it works just fine! It's a good base to begin with.
@rsmitty I'm working on putting k8s instances on AS group to handle High Availability, do you mind if I make something on the top of this work ?

Great job, thank you @rsmitty !
Thanks to @darkwise for testing.

I need to work on the documentation


Support istio report protocol and attribute protocol, make mixer unrequired

We have received many feedbacks about the concerns of Istio mixer, so, I am proposing we support Mixer Report Protocol with Istio Attribute Protocol.
Also from Istio 1.1.0, the compress has been turned off.
But, anyway, we use particular keys(and types) we need, to pick the telemetry values. Then we could generate SkyWalking native format, and push forward to SkyWalking.receiver.

Intend to use ALS, see https://github.com/apache/skywalking/pull/2460 . Close this for now.


Verify Yeelight XianYu C2001S500 support

Hi,
I have this lamp c2001s500. It is stated that it is untested. Which tutorial should I follow?
Thanks!

Could you disassemble the lamp and provide some photos?

Of course!
https://photos.app.goo.gl/PqsT2dfM7g3MV6599
If you could provide a detailed guide for flashing that would be awesome!

I look at the description, It's kind of mystery for me where to solder RX,TX, GND and 3.3V from TTL module to Yeelight ESP module?
I guess that flashing is typical, do I need additional power supply or anything else to enter bootloader mode to load up ESPhome?
Sorry, I'm not super experienced.

Lets start with making familiar with your lamp / mainboard. The big mainboard is called LED driver and can be ignored. We want to focus on this daugther board:

You can see here some round pads labeled as TP1, TP2, ..., TP5. You have to find all 5 test points.
In best case the meaning of each test point is already known and documented here:
https://github.com/syssi/esphome-yeelight-ceiling-light?tab=readme-ov-file#yeelinklightceil26
To be on the safe side, we will determine all points again. You will need a multimeter for this.
Ping me as soon you are ready to move on. :-)

Daughter board - identified ;)
TP1 to TP5 - located :)
Multimeter present :)

We can proceed. :)

This is the pin layout of an generic ESP32:

The pins around the ESP32 are labeled and we are interested in these pins:
pin1 GND
pin2 3V3
pin25 GPIO0
pin35 GPIO1 (TXD)
pin34 GPIO3 (RXD)

Make sure your lamp is unplugged / without any power. Use the continuity tester of your multimeter to measure the continuity between ESP pin1 and TP2. If it does beep we have verified GND is attached to TP2. Do this for each test point.

Ok test done.
It was easy for GND and 3.3V and between pin25 and TP3 but for RX and RX I could get a connection between RX - TP4 and TX -TP5. TP4 and TP5 are really hardly accessible, I suppose it is easier to solder directly to ESP32 and trust that it is exactly the same chip as C2001C450.
Ok what's next? :)

This guide should give some guidance too: https://github.com/syssi/esphome-zb-gw03/blob/main/docs/flashing.md
This device (zigbee gateway) is also equipped with an ESP32 and the guide explains how to backup und flash the ESP. Your job is done after section "Flash new ESPHome firmware" already. The Zigbee section of the guide can be ignored.

I have 2 different ones. Which one would you reccomend?

The first ine looks like 5v only?

The one with the 3.3 voltage pin.

Thanks. The guide looks good and quite understandable for me. I will try later to continue, I need to find a way to solder those tiny wires :/

@VoyteckPL because I'm not capable of soldering such things I used PCbite from Sensepeek (for me it was worth the investment because I flashed over w dozen devices). A cheaper solution are acupuncture needles. Just wanted to let you know in case you have "two left" soldering hands like me;D

Nice idea but too expensive for just one use 🙂 the problem is my hands get a little shaky when soldering so small things so I need to be extra careful (or maybe have a shot of vodka 😂) Just 3 wires are problematic in this case.

Good luck with both the soldering and also the right vodka choice 😅 as mentioned the acupuncture needles are much cheaper alternative to PCBite, so in case it's not working out well this could be a backup option

Guys, any videos of these acupuncture needles? Never heard of this.

Nice. I think I will use plasticine and normal needles just for this single project.


[v1.6] pkg/k8s: delete toCIDRSets for more than 2 endpoints

In case a toServices selected a service that contained more than 1
endpoint, the generated rules could never be deleted. This can easily be
reproducible by adding one more endpoint to the unit test of the
deleteToCidrFromEndpoint function.
Fixes: bae09f7cc960 ("Move ToCIDR gen logic to k8s package")
Signed-off-by: André Martins<EMAIL_ADDRESS>Avoid duplication of generated toCIDRs when using a toServices based CNP (or CCNP)

never-tell-me-the-odds


@attribute supports default value

I'm closing this, just because it's been open for so long. Can always reopen, if badly wanted or needed.


Development

heh, accident?

This is so embarrassing I’m so sorry…Sent from my iPhoneOn Jan 11, 2024, at 6:52 AM, fiveoutofnine @.***> wrote:
heh, accident?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

hahaha no worries at all :) glad you are taking inspo/bits from my site; as a fyi I will be doing a big update soon (next 14+app router, _many_ new components, couple new pages, etc.)

That’s awesome! I actually did a nextjs13 version initially but I couldn’t get this one thing working so I gave up and straight up forked your repo … I’m looking forward to it. Won’t be sending embarrassing PRs for that one 🫢.Sent from my iPhoneOn Jan 11, 2024, at 7:28 AM, fiveoutofnine @.***> wrote:
hahaha no worries at all :) glad you are taking inspo/bits from my site; as a fyi I will be doing a big update soon (next 14+app router, many new components, couple new pages, etc.)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Updated FW for Skoda Superb III 2016

I have added my FW fingerprints for Skoda Superb III 2016 and tested that it works for my car.

Can you add your dongle id?

Any updates @tivvit?

Hi, sorry for the delay. The dongle id is: fad463f1498cfb3f

Thanks!


Add test for struct default parameter valued

Tests for https://github.com/aspnet/Home/issues/2072

Not sure why github does not pickup branch commits, but they there: https://github.com/aspnet/DependencyInjection/commits/pakrym/struct-default-test


_Unwind_GetIP returns 0x0, and then jumps to it.

In certain cases (I'm not sure exactly which), _Unwind_GetIP inside of _Unwind_Backtrace is returning a null pointer, and then jumping to it after the callback completes. This is my code:
fn stack_trace() -> heapless::Vec<usize, 512> {
    extern "C" fn callback(
        unwind_ctx: &unwinding::abi::UnwindContext<'_>,
        arg: *mut core::ffi::c_void,
    ) -> unwinding::abi::UnwindReasonCode {
        let data = unsafe { &mut *arg.cast::<heapless::Vec<usize, 512>>() };
        let _ = data.push(_Unwind_GetIP(unwind_ctx));
        unwinding::abi::UnwindReasonCode::NO_REASON
    }

    let mut trace = heapless::Vec::new();
    _Unwind_Backtrace(callback, core::ptr::addr_of_mut!(trace).cast());
    trace
}

It's pretty much copied from panic_handler.rs, but pushed to a vec instead of immediately printed.
An example panic results in:
[ERROR] (panic) Panic! panicked at src/init.rs:148:5:
       │ oops
       │
       │ Stack trace:
       │   4: 0xffffffff80002eec
       │   3: 0xffffffff8001d338
       │   2: 0xffffffff80007804
       │   1: 0xffffffff800074dc
       │   0: 0x0000000000000000

Followed by a prefetch data abort when trying to read from 0x0.

Now I'm not 100% familiar with the heapless Vec, but from its source I see that it is not a transparent array, which means you're probably better off using as_mut_ptr instead of addr_of_mut!.
See playground for the difference. My guess would be that you have 5 stack frames, but the first stack frame address goes into the len field, which makes the Vec longer than it should be.
The remaining memory is probably zeroed because your allocator zeroes allocations by default.

That's interesting, Frame::from_context should return None when IP is 0, and that'll be treated as end of frame. Would you be able to share more details about architecture, how things are compiled, etc?

Could you provide a MCVE?

You could see if it also happens on the existing example. Otherwise, I can try I guess, but it might be long.


Alexa support?

Do you plan to add Alexa/Google home support?
Maybe with FauxmoESP is easy, even for multiple switchbots

I wasn't planning of having it as part of the main branch, but I added a separate branch for Alexa if you want to test it out. I just quickly wrote this and would need someone to test since I don't own alexa/echos. I have google homes which don't have a similar integration
https://github.com/devWaves/SwitchBot-MQTT-BLE-ESP32/blob/alexaBranch/Arduino IDE Files/SwitchBot-BLE2MQTT-ESP32.ino
You will need to add the FauxmoESP library and also manually add the AsyncTCP library using the zip https://github.com/me-no-dev/AsyncTCP/archive/master.zip
The code currently still requires that you have MQTT setup and working, but you should be able to make the calls directly from Alexa for bots and curtain (ON,OFF). Position isn't setup to work through alexa yet
The standard code heavily expects MQTT to be connected, so I would need to remove those checks in order to not use MQTT
Again, I coded this with zero Alexa testing since I don't own one, so good luck

Hi, at home i own an Alexa Echo dot so i will test soon...according docs should be easy to implement percent position.
Maybe i will try to issue some voice commands to alexa and try to write some code.
I'll let you know :)

I can do the percentage part so u dont need to worry about that, the code now is just a preliminary test to see that it works for on/off. I might switch to espalexa... not sure yet
If it works I"ll make changes so you can disable the need for mqtt

okok, anyway i'll use both alexa (voice) and mqtt with my hub.
If you need some logs and prints about input parameters provided by alexa...let me know.
Did you find some improvements to use espalexa over Fauxmoesp? Maybe light bulb colors?

Without an alexa/echo to test with it is difficult to tell if one is better than the other (fauxmoesp or espalexa). I know aircoookies WLED work and espalexa is slightly easier to install (no zip to download). espalexa didnt look like it was setup for dynamic device names though

According to my experiments they are pretty mush the same, maybe the espalexa is more oriented to colors and brightness...as well as percentage but fauxmoesp also support boolean state and percent but colors are in a separate branch. The developer says he is not very happy with implementation.
Anyways both solutions seem to work good

@fabiosoft have u have the chance to test? if it works I'll look at removing the mqtt requirement

Closing this for now. Can be reopened later if needed


Unable to run the irrigation_classification notebook

In which step did you encounter the bug?
Notebook execution
Are you using a local or a remote (AKS) FarmVibes.AI cluster?
Local cluster
Bug description
I'm trying to run the Irrigation Classification Notebook, but I'm getting the following error:

When I run " run.reason", the log file looks as follows:
"RuntimeError: Failed to run op stack_landsat_bands in workflow run id cb40bb24-ebf0-4f82-96af-c87fa9df479c for input with message id 00-cb40bb24ebf04f8296afc87fa9df479c-7f94920eace13cef-01. Error description: <class 'RuntimeError'>:  self._exception\npebble.common.ProcessExpired: Abnormal termination\n."
I also tried to change the buffer size to download a smaller image, but I'm getting the same error.
Can you also advise on how to customise the workflow for my study area ? I get see that the model was calibrated using training samples collected in a field in Nebraska. How do I use my own model ?

Hi @ZoloKiala , it looks like you have run out-of-memory. If you are running this in a VM, you are able to see OOM messages with dmesg (you may need to run this as root). This specific model is a simple logistic regression with parameters you can adjust (please see the parameters in the https://microsoft.github.io/farmvibes-ai/docfiles/markdown/workflow_yaml/farm_ai/water/irrigation_classification.html ). If you want more sophisticated models, you can express them as Onnx files (see an example as in https://github.com/microsoft/farmvibes-ai/blob/main/notebooks/crop_cycles/crop_cycles.ipynb). Please let us know if you have any further question.

@edrodrigues-ag Thanks for your prompt reply. I'm using WSL. My computer has 10 processing cores (I think it's good enough). Should I move to a VM ?
I will try to more sophisticated models as suggested.

I increased the memory amount allocated to WSL. It's working now. Thank you very much!


docs(getting started guide) Declarative config examples and instructions

Updating the getting started guide to include declarative config examples.
Previews:
Overview: updated the Using this Guide section to include decK
New decK tabs:

Prepare to Administer Kong
Expose your Services:

Add a Service
Add a Route
Note: also added a sample of a deck dump command to the Route section as part of the topic rollup, to show that Kong also implicitly adds some default values.

Rate Limiting
Proxy Caching
Protect Services:

Enable Key Auth
Create a consumer
Disable Key Auth

Load Balancing

Manage Admin Teams: added reference section on how to use decK after having enabled RBAC, and for workspaces

For the sake of having a paper trail, feedback from Fel on Slack:

I like how under route you showed the entire deck file. We should do the same for the other parts as well.
This way people can just copy paste. Otherwise this will be very error prone.


Add code for phase 1 of analysis

Add the code for the first phase to create ntuples from the full dataset persisted to tape

EAZE job code has been added to data_preparation folder


emitDeclarationOnly compilerOption leads to error

When I have "emitDeclarationOnly": true set in my tsconfig.json, jest errors out with the following:
    Debug Failure. False expression: Output generation failed

      at Object.transpileModule (node_modules/typescript/lib/typescript.js:96861:18)
      at transpileViaTranspileModile (node_modules/ts-jest/src/transpiler.ts:105:13)
      at Object.transpileTypescript (node_modules/ts-jest/src/transpiler.ts:19:10)
      at process (node_modules/ts-jest/src/preprocessor.ts:50:26)
      at Object.process (node_modules/ts-jest/index.js:8:51)

When I remove or set that option to false, tests work fine.

Can you please create a minimal repo that reproduces this issue?

Can you please create a minimal repo that reproduces this issue?

Here you go: https://github.com/Swatinem/ts-jest-593

What would you expect to happen when you try to pile typescript through the compiler and tell it not to actually emit any javascript output?

I would expect ts-jest to override this options, because the output related options should not matter for a jest transform.
I mean running my tests should neither create .d.ts declaration files not .js transpiled files nor any other side effects.

I think that makes sense. Would love to accept a PR with this change.


The TextField widgetcannot limit input to only two decimal places

The TextField widgetcannot limit input to only two decimal places

@gionchat
Please provide flutter doctor -v and a minimal code sample that shows the issue you are facing.
Thanks.

I think you mean that you can't add more than two digits after decimal point. It can be fixed by putting this in your TextField widget:
inputFormatters: [DecimalTextInputFormatter(decimalRange: 2)],
or using regex:
inputFormatters: [WhitelistingTextInputFormatter(RegExp(r'^\d+.?\d{0,2}')),],

I think you mean that you can't add more than two digits after decimal point. It can be fixed by putting this in your TextField widget:
inputFormatters: [DecimalTextInputFormatter(decimalRange: 2)],
or using regex:
inputFormatters: [WhitelistingTextInputFormatter(RegExp(r'^\d+.?\d{0,2}')),],

yes，Thanks！

I think you mean that you can't add more than two digits after decimal point. It can be fixed by putting this in your TextField widget:
inputFormatters: [DecimalTextInputFormatter(decimalRange: 2)],
or using regex:
inputFormatters: [WhitelistingTextInputFormatter(RegExp(r'^\d+.?\d{0,2}')),],

yes，Thanks！

Thanks！


Unavailable on Microsoft Store

It's unable to find/install the DisplayHDRTest App via Microsoft Store. By clicking the URL https://www.microsoft.com/store/productId/9NN1GPN70NF3 I can only get such an error page: https://www.microsoft.com/library/errorpages/smarterror.aspx?correlationId=+5UJzruCEEy/gEFf.0.2.

I had the same issue. I came here too via a link on the website.
In the Releases link you can get download the zip which includes the DisplayHDRComplianceTests.exe - which is the same app experience as the store app.
An update to the Windows store app with a link would have been nice though as this is a very useful utility, though I understand if app depreciation isn't well supported by the Store.

I had the same issue. I came here too via a link on the website.
In the Releases link you can get download the zip which includes the DisplayHDRComplianceTests.exe - which is the same app experience as the store app.
An update to the Windows store app with a link would have been nice though as this is a very useful utility, though I understand if app depreciation isn't well supported by the Store.

I wrote to VESA, and here is the reply:

Our experts have confirmed that the removal was intentional. Please download the tools from VESA’s website.
The link is on this page:
https://displayhdr.org/performance-criteria/
Actual link that this page points to, with the ZIP file:
https://github.com/vesa-org/DisplayHDRTest/releases/tag/v1.1e2


Allow to use it without babel

Hi Tivac.
Loved you module so far. Now as it requires babel to run not so much.
Would love allow to use it as plain browserify transform again.

2.2.5 still works fine if you're really dead-set against babel. I like having reasonable source maps (falafel provided zero options there) and it's trivial to use babel w/o all the ES2015 -> ES5 plugins if you want.

I'm afraid future optimisations will not be backported. I'm fine with ver 2.2.5.
I use mithril-objectify only in production/staging and not in develop. Thats why lack of sourcemaps are no issue for me.
Thanks for your work anyways.

Installing babelify and using mithril-objectify as the only babel plugin you run in it is pretty simple to do. It also means that I don't have to support a browserify/rollup/webpack/etc transform, since that work is already done by other people :smile:

Tools can break. More tools, higher probability that something breaks... So I just use Browserify (the API in a express-server not commandline) and Uglify (for production). I try to keep things as simple as possible. I once tried babel.  Hopefully I never need this.


For now, docker stats appears to be libcontainer only

Signed-off-by: Sven Dowideit<EMAIL_ADDRESS>in light of #10498
@fredlf @jamtur01 @crosbymichael

@fredlf @jamtur01 @crosbymichael

LGTM

LGTM


Windows compatibility.

#9 tells about two places with Windows path separators in $adminDir. 454 was fixed in a9abf97 but 874 is not.

Thank you very much, picked to master as<PHONE_NUMBER>fa0ffebc08e28ebec0485e1ad8ba67.


Docker images

What is the best way to build and run docker images for light4j rest apis? I see that a Dockerfile is generated from codegen. When I build the image and run it I get this error.
Error: Could not find or load main class com.networknt.server.Server
Caused by: java.lang.ClassNotFoundException: com.networknt.server.Server

I am using the following command to build and run the image.
docker build -t catalog:1.0.2 -f docker/Dockerfile .
docker run catalog:1.0.2

Are we adding all the pom dependencies when building a fatjar?

We also generate build.sh to create docker images and publish them to the docker hub. Modify it based on your docker hub account or internal artifact repository.
To build fatjar, you need to use -Prelease as we don't want to generate farjar during the development.


Please invite me to the Recode-Hive GitHub Community Organization

Name
Revanth
Discord Username (if applicable)
revanth1325
Additional Context
To Learn and Contribute.

Invitation sent to join the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/Recode-Hive/people

ok sir


#118 bug window size with optical flow

When using the optical flow algorithm, a bug was discovered when the windows size parameter contained a value of 1.
Modifications were then made in the optical_flow.py file to set a condition to check the window size.

As per the schedule, the evaluation and integration of this branch will be executed from the CNES gitlab. Appreciate your efforts.

Merged into CNES GitLab, it will be included in the upcoming release. Thanks once more!


allow to get a wholeFile starting at some offset

This change makes the offset variable in getWholeFile() an optional parameter. This allows to tail -f a file comfortably using the getWholeFile() helper function, where previously it was only possible to retrieve the whole file.

https://github.com/retz/retz/commit/49ea9bc0f12f279e0f6594f3d8fa7354e3c4dd66 was merged manually, as this required merge commit which I didn't understand... Thank you for contribution.


Feat: Confetti animation on verified page

What feature?
When user visits on /verify page after clicking on verification link, a confetti animation will be shown to them representing that they are successfully verified.
You can use any confetti library but it should not be large
Add screenshots
No response
Record

[X] I agree to follow this project's Code of Conduct
[ ] I want to work on this issue

Hey, I'd like to work on this. I'm open to others also working on this since I'm new to the language if that's possible!

Hi @Sanchitbajaj02 , I want to work on this issue!!

Hey, I'd like to work on this. I'm open to others also working on this since I'm new to the language if that's possible!

Sure you can work on it. Explore the language and its libraries and let me know if you need any help😊

Hi @Sanchitbajaj02 , I want to work on this issue!!

 You can explore more issues or create new ones 😊

okay sure! also @Kanavmh feel free to ask if needed 🚀

@Kanavmh Are you still working on this issue?

@Sanchitbajaj02 I would like to work on this issue

@Sanchitbajaj02 I would like to work on this issue

Sure, assigned to you


Update change log with v0.7.x releases

Contains the work in the following commits:

v0.7.8 20b7298fe0d3da04b965ec4a379db0247cd632be.
v0.7.9 07bc32f27b4f2488de91a66cfd489eae97551635.
v0.7.10 b7006d710821f1d6aa0d5a63948dc21b4433ddbf.
v0.7.11 772c692150c711d7bdd72b5c6287072b8914e519.
v0.7.12 7adfb75fdefe98e3b57438bafa36c09a85377777.
v0.7.13 75f41fb304d299dfbc07679d15193e03273c4597.

With this the v0.7.x and master branches should be equal again.

hmm, why is CI unhappy?

hmm, why is CI unhappy?

Stricter lints, specifically the dead_code lint now ingores derived Debug and Clone impls. I got a couple fixes in https://github.com/tokio-rs/mio/pull/1514.


Introduce __ModelicaAssociation_Impure

Replace annotation(__OpenModelica_Impure=true, __iti_Impure=true) by annotation(__ModelicaAssociation_Impure=true) that was added to MSL 3.2.2.

I propose to add __OpenModelica_Impure again in order to not break backwards-compatibility, i.e. have __OpenModelica_Impure and __ModelicaAssociation_Impure.

This issues was only relevant if it were fixed for v1.4.4 = MSL v3.2.2 dependency.


Inconsistent behavior of IncludeFile when invoked within a flow vs using the client

self.file = IncludeFile(...)

The value of self.file is set to the contents of the file inside the flow but in the client, the value of run.data.file is set to a json blob with a pointer to the actual file.

fixed.


Is Description to code generation available here?

I want to generate code from description, For example, if I give - " Write a code for the addition of two numbers". It should return a code for the same. Is it available here? If not any suggestions?

Try here.


Dev update ontobuiltenv address data

Updated address information to better accomodate information about flat and building names (see MIRO board for details: https://miro.com/app/board/uXjVOIznYOU=/)

I guess the range of isPresumedMatchOf cannot be made more specific than owl:Thing?

I guess the range of isPresumedMatchOf cannot be made more specific than owl:Thing?

For the Land Registry data only we could use http://landregistry.data.gov.uk/def/common/BS7666Address, but I am not sure as this property could also be used for linking to other data sets

I guess the range of isPresumedMatchOf cannot be made more specific than owl:Thing?

For the Land Registry data only we could use http://landregistry.data.gov.uk/def/common/BS7666Address, but I am not sure as this property could also be used for linking to other data sets

...and I imagine this would be too specific to be useful...


Exhale errors stop rosdoc2 in multiple package mode

Exhale handles errors (in utils.fancyError) with a shutdown:
def fancyError(critical_msg=None, lex="py3tb", singleton_hook=None):
    if critical_msg:
        sys.stderr.write(critical(critical_msg))

    sys.stderr.write(fancyErrorString(lex))

    if singleton_hook:
        # Only let shutdown happen once.  Useful for when singleton_hook may also create
        # errors (e.g. why you got here in the first place).
        fancyError.__defaults__ = (None, None)
        try:
            singleton_hook()
        except Exception as e:
            sys.stderr.write(critical(
                "fancyError: `singleton_hook` caused exception: {0}".format(e)
            ))

    os._exit(1)

This cannot be caught, so rosdoc2 fails to continue in multi package mode.

I fixed this in scan by using processes.


Re-added missing react icon

Added back react icon which was removed in a recent commit since it is still being referenced for react filetypes which do not have a new icon (ie. typescript tsx)
If needed I can go through and find other icons which have been removed but are still referenced in the icons JSON and include them in this PR
If this is something that is currently being fixed and will have updated icons in a future build feel free to close this PR

This was already fixed but not included in the latest release. Pushed a new release (0.14.0) now!


Explore parallelizing lint step in sigh.

I noticed the lint phase of sigh runs in serial, ~500 total files, batched into 100 at a time (due to Windows command buffer limits according to a comment), and takes ~12s on my workstation. I thought perhaps we could parallelize this. My initial naive attempt to do so via spawn appears to roughly work on Linux and takes ~5s, but on Windows I've not yet figured out how to wait for the spawned child processes to return (and gather their exit codes) before proceeding.
Hackery here note the commented out bit at bottom must be flipped.
cross-spawn could be helpful.

We have npm-run-all as a devDependency, the node API might be an option. I think that'll be a little higher level than cross-spawn.

Consider only linting changed files?  I did a quick search and found this:
https://www.npmjs.com/package/lint-changed
Not sure if it's directly usable since I'm still an npm n00b.
On Tue, Jun 19, 2018 at 9:31 AM Matt Small<EMAIL_ADDRESS>wrote:

We have npm-run-all https://www.npmjs.com/package/npm-run-all as a
devDependency, the node API
https://github.com/mysticatea/npm-run-all/blob/HEAD/docs/node-api.md
might be an option. I think that'll be a little higher level than
cross-spawn.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PolymerLabs/arcs/issues/1506#issuecomment-398462663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAF5y9pTpJPqbAi2jMCr3vM4jqRLF4Btks5t-SdqgaJpZM4UsnCL
.


feat: add attachment.sidecar publish option

The term "sidecar" is what Threads uses to represent a group of images and/or videos that share the same post.
Upload ID collisions
I also added logic to make sure that upload IDs never collide (i.e. if two publish calls happen at the same time).
Deprecations
As part of this PR, I propose we deprecate the url and image publish options, replacing them with a single attachment option which can be { url }, { image }, or { sidecar }.
Before
await threads.publish({
  text: "Hello",
  url: options.url,
  image: options.image,
  sidecar: options.sidecar,
})

After
await threads.publish({
  text: "Hello",
  attachment: options.attachment,
})

This means we can…

better enforce one property only (i.e. url and image cannot both be defined)
and it gives users a useful PostAttachment type

The example below demonstrates the strict enforcement:
https://www.typescriptlang.org/play?useUnknownInCatchVariables=false&ssl=9&ssc=1&pln=10&pc=1#code/C4TwDgpgBACgrgIwDYEsDOALA8mYKD2AdmgGoCMUAvFAN4BQUjUwEAHsAFxRrABOKhAOYBuOgF8oAMigAKGlDi8kAfi49+QqBIA+tKCgC2AQ0ERV3PgMFaAlHToATCAGMkR3tABmcQs7xEoMERUTAB9ADcyGXxcAmIueGR0bFiiUjIbLnD8FAd7UEgoABkBAGsAQWBgI2cMAwhCYCo9RSQ1S00xOgLoAEljU0rq2vrG5vlDEwh2jWsuugEWXk8a6ESQlP9iEgAmWgYmFnYZq1EmKCMqmrqG4HMAZUs-AFVCOIAeEsIKq5HbqF0-SmQ2uo2AAD5xPYnK53F4fH44oFgskIjtoql4rAUZgcFtSDtMlBsrl7N5fFsoGwjAYwEgIBEojZ9ucPMBFIRkUkwpE5AdzowjpwoAAiAASECQSHwUAA7vglA4RQAafkCgD06rV501UGeaAgvH0aCgACoAHJYAAqprl7kIEAcFwQ+DgTRdwAwUAABpNTN6LoQnd7WgG2Og8EIAHTapia2OMP3TKAAcgwVTAaA4mpQUcMgkUUec+AM6oAouVCHBemgDFGAFaQQQp5VQBMKJRcNMZrOawT4fCCelFksptvnMR2ebkxEBam0+lomTM+isiDs3icoLcjBL1cCwVsYXiyXSuUKpBK1UHxjxm9QXX6w3Gu2bx3MDCXUVJkWBp0i1pf2cIxCEIfB3XAr1wx4KMoAATSMEAAEJ2zvG9LmGG5Gi4eR23OJMu3TYBM2zdVc3zQti1LCsqxrOtGwgZtWzwphWkIntSP7Qdhyosd2zEa8mEnKFunAaB7kMOkUE8EB3itcFxgkaR5AAbRgfROVKCAQHwTwoCtABdLgrTUgytFEUTCkefgXjeIg5IU6gAGESwQAQIFeD55KpdgGgcE0BE8Z9ngOZR9J8lggxNECQDVMKJIXaTZKtKQ9BUgBpDSoDLVhXDgJx3i0nS9OeVsit0-TwQM8wfCcTx3KdMRIXOLgHXCQ0DlaiB2t4CyeigFyDDch1PPs7zqBgFBnFKOSyu0irvMkA4YHcPAjCQd4ZBSo8-OiwgQCgMKZFYYzmUoBSYqgLqeuZHaotkE6NKCo1njOi79sOvUrqgNrDXBUQgA
Finally, I propose that we deprecate the exported types whose name begins with ThreadsAPI (except for ThreadsAPIOptions), since this isn't a naming convention we apply evenly. Therefore, ThreadsAPIImage becomes ImageDefinition (as Image alone seems too vague?). If we wanted to, we could put all types in an export namespace ThreadsAPI block instead. But whatever we do, let's keep it consistent. 👍

I'm onboard with namespacing any unofficial data structure with ThreadsAPI. I propose we go with a namespace ThreadsAPI approach, as it's more readable, requires less importing, and I don't see a reason not to take advantage of TypeScript's namespace feature.

I'm onboard with namespacing any unofficial data structure with ThreadsAPI. I propose we go with a namespace ThreadsAPI approach, as it's more readable, requires less importing, and I don't see a reason not to take advantage of TypeScript's namespace feature.

Looks great to me! Thanks, I'll merge. 👍


v0.0.7 "locked folders/files" doesn't work properly with relative links.

  good catch! "locked folders/files" doesn't work properly with relative links.

Originally posted by @EdoFro in https://github.com/EdoFro/Freeplane_Map-Drive-Inator/discussions/19#discussioncomment-4855625

@bepolymathe,
download v0.0.7 again and try it

solved #23


Some  issues(maybe performance affected) found when reading the source code

Hi there:
I have began to study tantivy's source code,and found two issuses:

why not use std::chan but use a third-party chan (eg: in index_writer.rs), and this third-party one seems to be performance loss

2. In the function open_index_writer(index_writer.rs), index.opstamp() has been called twice, which seems to be very expensive(meta.json open_read)

What do you mean std::chan ? Are you talking about mpsc ?

About point 1. What makes you think it would make a difference?
chan is used as a job channel dispatch channel. I don't think we are in the range where chan's performance is a problem.
If you are talking about mpsc, it is multi producer and single consumer while want the opposite. It is possible to wrap it in a Arc<RwLock>, but it probably has similar performance issues.
About point 2. It is a good point, I'll fix it... but not for the performance but for consistency and code quality. AFAIK Nobody cares if opening an IndexWriter is 0.1ms longer.

got it , thanks for reply.

Reopening. Your point 2 is valid.


devicetree: Remove DT_SRAM_{BASE_ADDRESS,SIZE}, use CONFIG_* versions

The SRAM address and size are currently available as both
DT_SRAM_{BASE_ADDRESS,SIZE} and as CONFIG_SRAM_{BASE_ADDRESS,SIZE} (via
the Kconfig preprocessor).
Use the CONFIG_SRAM_* versions everywhere, and remove generation of the
DT_SRAM_* versions from gen_defines.py.
The Kconfig symbols currently depend on 'ARC || ARM || NIOS2 || X86'.
Not sure why, so I removed it.
It looks like no configuration files set CONFIG_SRAM_* at the moment, so
another option might be to use the DT_* symbols everywhere instead. Some
Kconfig.defconfig.series files add defaults to them though.
Also improve the help texts for CONFIG_SRAM_* to say that they normally
come from devicetree rather than configuration files.

Should we use DT_SRAM_* instead of CONFIG_SRAM_*? As far as I know, we are using DT to describe hardware. Did something change?

Mentioned it in the commit message:
It looks like no configuration files set CONFIG_SRAM_* at the moment, so another
option might be to use the DT_* symbols everywhere instead. Some
Kconfig.defconfig.series files add defaults to them though.

Getting rid of CONFIG_SRAM_* later would be nice. It would break compatibility with any external projects that set them, but maybe no one does, and it's probably easy to fix.
While they're there, it's nice to have things consistent at least.


[Backport 2.x]  Add model version to model metadata and change model metadata reads to be from cluster metadata

Description
Backport of https://github.com/opensearch-project/k-NN/pull/2005
Note: GetModelResponseTests are expected to fail, will be fixed by https://github.com/opensearch-project/k-NN/pull/2062
Check List

[x] New functionality includes testing.
[x] New functionality has been documented.
[x] API changes companion pull request created.
[x] Commits are signed per the DCO using --signoff.
[x] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ryanbogan the tests are still failing.


[1.3] Media Playback Cluster XML has to be updated as per spec (update to revision 2)

Description

Below mentioned attributes are missed to define in XML file
ActiveAudioTrack
AvailableAudioTracks
ActiveTextTrack
AvailableTextTracks
AudioAdvanceMuted

Below mentioned commands are missed to define in XML file
ActivateAudioTrack
ActivateTextTrack
DeactivateTextTrack

Below mentioned features are missed to define in XML file
TextTracks
AudioTracks

Below mentioned features are missed to define in XML file
TrackStruct Type
TrackAttributesStruct Type
CharacteristicEnum Type

Update the cluster revision attribute in the XML file to a value of 2

Spec Reference :
https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/app_clusters/media/MediaPlayback.adoc
XML Reference :
https://github.com/project-chip/connectedhomeip/blob/master/src/app/zap-templates/zcl/data-model/chip/media-playback-cluster.xml

Above described issues are all resolved in latest XML.


fix: Add a Default Level

This PR adds the functionality to make sure a default Level is added when initially adding points.
The default level added is 1 or whatever is supplied in the starting level config.

That's cool


Need ability to set that not calling "done()" on a mock is expected

There are cases in testing where calling "done()" on the Mock is not practical within the given test case, and it would be useful to be able to tell the Mock to not expect done() to be called and to not emit a warning in that case.
This came up in porting the @eldruin's mlx9061x-rs to embedded-hal 1.0
Failing test cases are here: https://github.com/Radiator-Labs/mlx9061x-rs/actions/runs/9104910268/job/25029588644
The tests that fail are calling a fallible object create, which does not release the Mock and does not return the object when the creation fails. This means there is nothing to call done() on. Other test cases are able to call .destroy().done() on the returned object, which calls done() on the mock in the test context.

You should be able to pass a clone of the mock to the driver, and then call .done() on your copy, right?
(The mock has an Arc internally, so only a reference is being cloned.)

That sounds great. I'll give it a try right now.

Using clone() solves my issue. I am closing this request.
Thank you for the assist!


Internal Server Error when create ANY_MAP Delivery Service

I'm submitting a ...

[x] bug report
[ ] new feature / enhancement request
[ ] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[x] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

Create an ANY_MAP delivery service. Choose Fullfill Request Immediately. It will not create new Delivery Service and return Internal Server Error.
Expected / new behavior:

Let user create new Delivery Service and return different message.
Minimal reproduction of the problem with instructions:

Anything else:

So any other type of Delivery Service can be created successfully?

it does look like the error for the any_map is related if you chose a CDN that is dnssecenabled that doesnt have keys created it will error with 500 and log:
ERROR: api.go:180: 2020-03-27T16:29:32.990780963Z: <IP_ADDRESS>:54722 creating DNSSEC keys: getting DNSSec keys from Riak: no DNSSec keys found

Yeah, I chose different CDN and Delivery Service created successfully.

dup of https://github.com/apache/trafficcontrol/issues/4451 btw

Close it, then?

yes please

Duplicate of #4451


New version: Jackett.Jackett version 0.20.1108.0

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Jackett
Jackett

Version
0.20.1108.0
0.20.1108

Publisher
Jackett
Jackett

ProductCode

{C2A9FC00-AA48-4F17-9A72-62FBCEE2785B}_is1

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1758
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Optimize Code Splitting

Currently all dependencies are bundled in one giant chunk, that is loaded on every page, which results in long loading times, when not cached yet.

[ ] Dynamic Import of @sovryn/react-wallet
[ ] Check for further heavy dependencies to split off

Should be started after #1475 (now #1347) is merged.

Stopped working on it for now. Dynamic Import of @sovryn/react-wallet requires changes to the react-wallet and wallet projects themselves, because the usage of React.Context prevents a the use of dynamic imports. One cannot dynamically import and use a ContextProvider via hooks, without breaking react. The usage of @sovryn/wallet also has to be made dynamic to reduce the bundle size dramatically since it includes heavy dependencies.

Migrated to Taiga in https://taiga.sovryn.app/project/sovryn-light/us/165


feat: add loadWallet option for faster testing

LND still timed out in the first run, but faster on the second run:
module.bitcoin.helm_release.lnd: Creation complete after 7m3s [id=lnd1]

vs in https://github.com/GaloyMoney/charts/actions/runs/4174578931/jobs/7228334686
module.bitcoin.helm_release.lnd: Creation complete after 9m53s [id=lnd1]

With increased CPU to 200m still failed first. but the second run is fast:
module.bitcoin.helm_release.lnd: Creation complete after 3m13s [id=lnd1]

Locally LND on regtest uses 997m RAM:

With the three things altogether there is a 3x gain here. Running the dev tests took ~45 minutes on other pending PRs, here it is 14 minutes.
lnd now deploying in under 2 minutes:
module.bitcoin.helm_release.lnd: Creation complete after 1m17s [id=lnd1]

using the pregenerated wallet reduced  the time for lnd to finish to roughly half in my local env from 3 minutes to similar as here.

local with loadWallet enabled:
time make redeploy-bitcoin
...
module.bitcoin.helm_release.lnd: Creation complete after 33s [id=lnd1]

Apply complete! Resources: 9 added, 4 changed, 1 destroyed.

real    1m42.527s
user    0m15.001s
sys     0m1.671s

local test with loadWallet disabled:
time make redeploy-bitcoin
...
module.bitcoin.helm_release.lnd: Creation complete after 43s [id=lnd1]

Apply complete! Resources: 8 added, 6 changed, 1 destroyed.

real    1m39.290s
user    0m13.423s
sys     0m1.685s

As using a pregenerated wallet does not make much difference will remove the option.


logging and update library policy only if latest evaluationTimestamp

logging and update library policy only if latest evaluationTimestamp

not needed


Formatting units

Is there any way to get a format like "4D15H"?
I know there's locale support, but that doesn't seem the right thing for this.

Not at the present point in time. You could create another locale with just keys for this then you could pass :locale to it and have it use that.
On 09/01/2012, at 12:36, Michael<EMAIL_ADDRESS>wrote:

Is there any way to get a format like "4D 15H"?
I know there's locale support, but that doesn't seem the right thing for this.

Reply to this email directly or view it on GitHub:
https://github.com/radar/dotiw/issues/25

Thanks. I think a locale may introduce some necessary whitespace due to the "and", so for now it may be easier to post-process the result. Either way, not a problem and something I can work around.

FYI I made a little helper using dotiw, to generate strings like "27 minutes" "4 hours" "3 days, 15h" "4 months, 9d"
https://gist.github.com/1664524

Looks good. Any particular reason not to use \d+ for the numbers rather than [0-9]+?

Should have done. Updated: https://gist.github.com/1664524/619ddbe23e6200cd12c4d45c62ed988499ef553d


runtime fixes

needed these little fixes to run it locally - it now trains but instantly runs out of memory on my laptop (understandably)

@DavidDemitriAfrica can you add the typo you can found


remote_server: Handle invalid server uuid being given authing to API.

get_remote_server_by_uuid (called in validate_api_key) raises
ValidationError when given an invalid UUID due to how Django handles
UUIDField. We don't want that exception and prefer the ordinary
DoesNotExist exception to be raised.

Merged, thanks @mateuszmandera!


jr:choice-name changes are not immediately propagated to all 2nd-level dependencies

Version: 4.27.2
From https://github.com/medic/medic-webapp/issues/3281
With the following form, change the textfield and see the new value immediately reflected in the choice labels below.  However, the bold-faced label below that will not update until the radio button is changed:
<?xml version="1.0"?>
<h:html xmlns="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:h="http://www.w3.org/1999/xhtml" xmlns:jr="http://openrosa.org/javarosa" xmlns:orx="http://openrosa.org/xforms" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <h:head>
    <h:title>Test Issue 3281</h:title>
    <model>
      <instance>
        <issue-3281 delimiter="#" id="issue_3281" prefix="J1!issue_3281!" version="2017-03-24">
          <input>Default Value</input>
          <translator>clinic</translator><output/><debug/>
          <note/>
          <meta>
            <instanceID/>
          </meta>
        </issue-3281>
      </instance>
      <bind nodeset="/issue-3281/input" type="string"/>
      <bind nodeset="/issue-3281/translator" type="select1"/>
      <bind calculate="jr:choice-name( /issue-3281/translator ,' /issue-3281/translator ')" nodeset="/issue-3281/output" type="string"/>
      <bind nodeset="/issue-3281/debug" readonly="true()" type="string"/>
      <bind nodeset="/issue-3281/note" readonly="true()" type="string"/>
      <bind calculate="concat('uuid:', uuid())" nodeset="/issue-3281/meta/instanceID" readonly="true()" type="string"/>
    </model>
  </h:head>
  <h:body>
    <input ref="/issue-3281/input">
      Input
    </input>
    <select1 ref="/issue-3281/translator">
      Translator
      <item>
        [<output value=" /issue-3281/input "/>] District
        <value>district_hospital</value>
      </item>
      <item>
        [<output value=" /issue-3281/input "/>] Health Center
        <value>health_center</value>
      </item>
      <item>
        [<output value=" /issue-3281/input "/>] Area
        <value>clinic</value>
      </item>
    </select1>
    <input ref="/issue-3281/debug">
      jr:choice-name($ {translator},'$ {translator}') = **<output value=" /issue-3281/output "/>**
    </input>
    <input ref="/issue-3281/note">
      The value above is stale if _Input_ is changed and you leave the textbox since it modifies the choice label for _Translator_ but not the value. The choice-name function gets updated if the choice value is modified, but should also update if the choice label changes.
    </input>
  </h:body>
</h:html>

I'm planning to dig further into this, but figured it's worth sharing here in case it's a known issue or expected behaviour.

Thanks. It doesn't ring any bell, so it's a new one I think.

Current hypothesis:

the <select1>'s item labels are changed by outputUpdate()`
outputUpdate() does not trigger calcUpdate() on calculations with jr:choice-name

Sorry, for not looking at your PR till now.  It's just that I feel such an intense dislike for the utterly non-sensible jr:choice-name() function and often would rather remove it completely ;).
However, I had a look and the issue, or at least part of it, is that calc.update() doesn't seem to find the dependency on /issue-3281/input to trigger a recalculation of /issue-3281/output.
I'll look further.
P.S. I do not understand why jr:choice-name's 2nd param has to be a string but am just ignoring that for now.

Oh, I see. The label is dynamic. So changing the output would have to trigger calculations that rely on the label that contains that output.
Yes... sorry, that's just another reason that jr:choice-name() should not exist at all. I now even more regret having added support for this function. I don't think we should let outputs trigger re-calculations and thereby go even deeper into this choice-name mess. Sorry about that.
However, the good news is that in the latest Enketo-core it has become much easier to extend and replace almost everything including output.js. So it's possible to customize this and still use the npm-published enketo-core!
FWIW, I think you'd have to search for all jr:choice-name() uses in the form that refer to the question of which the output is a part.

Thanks for the comprehensive response!  I'll have a think about how we support this in the medium-term.
Are there any obvious alternatives to jr:choice-name()?  If so, perhaps it could be deprecated.

It might be possible to place labels into a secondary instance and use <output> to display them. This way they can become queryable in any XPath expression without resorting to calculating with view elements.
The translation aspect is a bit harder. Enketo has a secret way of supporting translations in secondary instances (developed for external, but also working for internal instances). This is simply using lang attributes. I haven't proposed or announced this as I'm trying to take it one step at a time (my priority - by many miles - is this and this would come before).
Having a calculation change if the language changes means we'd need so add something quite radically new to XForms and that may be quite a hard problem to solve.

Overriding ./output for require() calls works a treat 😄.  My only concern is the risk of collisions if we ever have another relative path to a file called output.js in our project.

Maybe another technique could avoid that risk if you add a file in your app that calls Enketo's output.js and then changes or overrides it. The downside, is that the overridden code will still be in your compiled js (doing nothing). This is the approach we're taking in OpenClinica, e.g. here (note, we've called the file branch.js but we could have given it any other name like enketo-core.override.branch.js)
To avoid the issue of having significant redundant code, I have been splitting up Enketo Core modules in smaller functions (the ones we'd like to override) which would be fine to do in output.js as well, I think.

Finally we're patching the output.js file in local node_modules at build time, so no immediate worried about collisions :slightly_smiling_face:


removed error logging for NoSectionError

This is more of a question than a PR. I'm not really a proponent of putting a pass in an except block.
This error logging is clogging up the airflow logs with what looks like messages we don't care about re: our airflow config. Maybe we are supposed to have these sections/options but keep them blank? Maybe we should forcibly suppress the logging? Any thoughts?

Make sure you have checked all steps below.
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[ ] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

This is an issue with our Airflow configuration; 1.10 changed something in the default configuration behavior beyond what we we supported for the initial launch. It is on our radar and should be resolved soon.


nature is taking industry back.

can trees destroy buildings?
if not can you build something like that?
for example that 1 tree destroyed a building after 100 years.
and that 10 trees destroyed a building after 10 years
nature is taking industry back.
so the forgotten bases remain forgotten.

I've had an idea like that on my shelves for a while now but it won't be part of this mod (it is just outside of its scope). If I have some more spare time I might actually get to making that mod idea a reality.
However it won't be part of this mod so closing the issue ;)


Bump Win64 OpenSSL version from 1.1.1k to 1.1.1L

Closes #2007
See also #1337
Signed-off-by: Christophe Bedard<EMAIL_ADDRESS>

This should be backported to Foxy and Galactic of course.


BUG: The Hover effect is not there for electronics

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The hover effect is not here in the electronics page.
I can add the Hover effect for each category which will make this page more responsible and creative.
Please assign this task to me under GSSoC'24.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

I can add the Hover effect for each category which will make this page more responsible and creative.
Please assign this task to me under GSSoC'24.

@arghadipmanna101 Embark on a journey of creativity and functionality with a mission to enhance the user experience on our Electronics page! Picture this: with a simple hover, users will be treated to an interactive and visually captivating experience unlike any other.
I propose to add a stunning hover effect to each category on the Electronics page, elevating its responsiveness and injecting a touch of innovation. Imagine seamlessly gliding your cursor over each category, only to be met with an enticing visual cue that beckons exploration and engagement.
I'm eager to take charge of this task and breathe new life into our Electronics page. Please entrust me with this opportunity under GSSoC'24, where I'll infuse creativity and functionality into every pixel. Together, let's craft an experience that leaves users spellbound and coming back for more!


I want see the English documentation but I can't find the button to change language!

What needs to be done?
Thank you for page showing Chinese for me, but the page don't have a button to change language the writer wrote by. I want to see documentation between Chinese and English，just like when I read in MDN(it so nice to provide a language button),  it can help me understand the document deeply in my mother-language, improve read English document speed and build my confidence and patience.  I search the stackoverflow and can't find the similar problem. And some article didn't translate, so it still english, so if it having, could you tell me where is, if it's not having, could you provide in future, Thx.
souce-page-link

There is a button at the bottom of the page on the left side.

There is a button at the bottom of the page on the left side.
Thx, and I never scroll to  such bottom😭


Enable inlining into functions which have try-catch/try-finally

@dotnet-bot test this please

There are issues that need to be worked in the stack walker, I will reopen once they are fixed.

@dotnet-bot dotnet-bot Linked test this please

@rajatd Addressed review comments


[Mod] GemstoneLV - Stockalike JAXA / NASDA

Mod info

Mod name: GemstoneLV - Stockalike JAXA / NASDA
Author(s): Beale
License: MIT
Homepage: https://forum.kerbalspaceprogram.com/index.php?/topic/204309-112x-gemstonelv-stockalike-jaxa-nasda-10/
Download: https://github.com/Tantares/GemstoneLV/releases

Apologies for confusion, is it possible to specify with NetKan that it requires the following?

B9 Part Switch
Community Resource Pack
Simple Adjustable Fairings

Thanks for the submission, it should be there now:


Opt out of nextjs telemetry

Fixes https://github.com/rootzoll/raspiblitz/issues/2620

@dipunm can you base the PR on the dev branch, which we use to prepare the next release?