[FEA] move some deserialization code out of the scope of the gpu-semaphore to increase cpu concurrent

Is your feature request related to a problem? Please describe.
move some deserialization code out of the scope of the gpu-semaphore to increase cpu concurrent
Describe the solution you'd like
https://github.com/NVIDIA/spark-rapids/blob/625cd6c40417205a0135ad1d86219b23c4e846af/sql-plugin/src/main/scala/com/nvidia/spark/rapids/GpuColumnarBatchSerializer.scala#L152
JCudfSerialization.readTableFrom() contains both high-overhead cpu code and gpu-code, the gpu-code (include device memory allocation and copy) should be executed within the scope of gpu-semaphore, but the cpu-code DO NOT NEED
https://github.com/rapidsai/cudf/blob/19237a09fe9b80706ef463580c6a646f6f9ec2ae/java/src/main/java/ai/rapids/cudf/JCudfSerialization.java#L1505
this function i think do the following things

deserialization (not so sure)
alloc host-memory (pin-memory)
call the reloaded function to copy data form host to gpu

the step 1,2 do not need the gpu-semaphore, and it's better to get out of the gpu-semaphore
https://github.com/rapidsai/cudf/blob/19237a09fe9b80706ef463580c6a646f6f9ec2ae/java/src/main/java/ai/rapids/cudf/JCudfSerialization.java#L1522
only this line of code need the protect of the gpu-semaphore
all code before it do not touch the device memory, only touch host-buffer (pin-memory), so i think those code can be executed  without holding the gpu-semaphore (just like the Scan operator)
I thinks, we should move some code from cuDF into rapids
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context, code examples, or references to existing implementations about the feature request here.

this is the related issue: https://github.com/NVIDIA/spark-rapids/issues/622

@jlowe

@JustPlay
I agree that we could move the semaphore in this case. Any time we are doing I/O we should not hold the semaphore.  Because cudf itself has no knowledge of the semaphore we would need to add in some kind of a callback function to grab it.  I just did something similar for the arrow IPC format.
https://github.com/rapidsai/cudf/pull/6143
We should be able to move those APIs to make them more generic so we can reuse them in other places.
@jlowe I know you don't like callbacks because they make the code hard to reason about and I agree, but I was curious what you though about this situation?

I agree that we could move the semaphore in this case. Any time we are doing I/O we should not hold the semaphore. Because cudf itself has no knowledge of the semaphore we would need to add in some kind of a callback function to grab it. I just did something similar for the arrow IPC format

why not just copy the related into rapids-plugin?

why not just copy the related code snippet(s) into rapids-plugin?

We could in the short term, but it is a question of a separation of concerns, and the goals of each project.  One of the reasons we put the serialization code in cudf was so that users of the cudf library did not have to know what the exact memory layout. We have changed that somewhat when we started to implement the UCX shuffle, but I think generally it still holds true that a user of cudf should not need to know the memory layout to get decent performance.
Cudf is trying to be a generic backend and if we have run into an issue with Spark, that is not some odd corner case of how spark handles a specific SQL command, then others would likely want that same functionality. In this case I can totally see that other users might also want to know when data is completely off of the GPU, or when external I/O has completed and GPU processing is ready to start.

I know you don't like callbacks because they make the code hard to reason about

I don't mind callbacks within the JVM so much, as those can be traced without too much effort.  What becomes really hard to trace are callbacks from JNI into the JVM, as the IDE won't help you there.
If we keep the serialization logic in cudf, we could solve this in a couple of ways:

callbacks from cudf back into the application just as it's about to place data on the GPU
split the serialization into two separate cudf calls that the application makes, the first takes the input stream and returns an opaque object that must be passed to the second call to continue the deserialization.  The application can then do any "just before GPU" logic between the two calls.

The issue is about memory management.  The GpuSemaphore is in place to limit the number of tasks that can be on the GPU at any point in time so the processing cannot use too much GPU memory, which will kill the job.  If we allow a task to release the semaphore while holding on to GPU memory then the GpuSemaphore is not doing it's job.
We agree that in the ideal case I/O should not happen while the semaphore is held, but there is not a simple solution to this.  We can fix it for the deserialization code, like was requested, but it will only help for the very first batch being read.  We need a more holistic approach to this to make it work properly and quickly.
We are still trying to think through what the ideal solution would look like, but with the 0.2.0 release close by, we have been a bit distracted trying to get everything ready for that.
In general I see a few things we want.

All data that is not actively being processed needs to be stored in the RapidsBufferCatalog.

The code right now is specific to Shuffle, but I am in the process of making it more generic for 0.3.0.  There still needs to be a bunch of micro-benchmarks to see what they of performance impact this might have for code that commonly will not spill.  This is here to act as a backup in case we get something wrong when releasing the semaphore early.

Try to concentrate I/O.  There really are two approaches we could take here, and a final solution is likely to be a combination of both of them.

We could have the shuffle layer be aware of the desired batch size and wait for the desired amount of data to be available on the host side before sending any of the data on.  This should hopefully make it so that GpuCoalesceBatches does not have to wait for data. The problem is that it shifts memory pressure to the host side and/or may result in more memory pressure in general when using UCX shuffle.  So to make this work we would need to figure out a way to insert CPU side data into our RapidsBufferCatalog as well, not just GPU side data.
We could have a way for shuffle to signal that there is no more data available right now.  This would let the GPU start processing data early, even if it is less efficient at it, but would not solve the issue when all of the is required for an operation (sort for example).  The other issue with this is that spark only provides an iterator interface for us to use, so we would either have to do something out of band, or have special metadata in the batch to indicate that this is the end of the non-blocking I/O, which is not super simple, because spark does not let us extend the ColumnarBatch class.

Implement out of core processing.  This would let us move away from requiring all of the data be in memory.  The problem is that this would come with a trade-off of spilling, which is likely to slow things down even more.

RapidsBufferCatalog

can you make more detailed explanation about RapidsBufferCatalog ?
@revans2

can you make more detailed explanation about RapidsBufferCatalog

RapidsBufferCatalog is part of the spillable buffer framework in the plugin.  Columnar batches stored as a contiguous buffer can be registered with the spillable framework (entry point for buffers into the system is via RapidsDeviceMemoryStore as all buffers produced by the GPU start off in device memory.  Once registered into the spillable buffer system, buffers can automatically spill out of GPU memory into host memory (and ultimately to disk if necessary) while the buffers are left unreferenced.
When the buffer is needed later, the buffer's ID can be used to lookup and acquire (lock) the buffer via RapidsBufferCatalog.  If the buffer is not in device memory at the time, it will automatically be fetched back into device memory, potentially spilling other buffers to make room if necessary.
If all of the GPU memory being held by a task is in the form of unlocked, spillable buffers then it should be able to let go of the GPU semaphore while performing other operations, since a new task arriving will at worst force the old tasks's buffers out of the device store.  It will not lead to an OOM that wouldn't also happen with the old task.

@revans2

we have join time, build time, why not add a stream time to count the time loading the stream table (batch)?

We can fix it for the deserialization code, like was requested, but it will only help for the very first batch being read

I am a little confused。Whether moving the deserialization code out-of the gpu semaphore will only help the first batch read in the build parse OR help the whole build parse?

https://github.com/NVIDIA/spark-rapids/issues/679#issuecomment-689520518

The gpu semaphore limits the task concurrency，even the number of cpu core is bigger than gpu concurrency，they can not run once some of them are taking the semaphore (before release it)。So the shuffle data reading (disk io, net, cpu decompress) can not overlap the gpu processing, so offen, the cpu/net/io can not feed enough data to gpu
Without spilling, the gpu semaphore can not be released, So can we make some of the cpu part (e.g. data reading) async?
e.g. we can add a backgroud aync cpu thead pool to reading data for the spark tasks, the async thread reading data from disk/net to memory, so the spark task can task shuffled data directly from memory. When the async thread reading data quickly enough, the gpu will always has enough data to processing, the gpu semaphore limiting will not be a problem
I am not familiar with the shuffle fetch in cpu， not familiar with the code path of shuffle fetch in rapids，so i need some help
@revans2 @jlowe

@JustPlay
I'm not sure a thread pool is the solution in this case.  Spark already has a thread pool for these types of situations, and has a bunch of features to avoid doing a DDOS during the shuffle.  Instead what we need to to is in JCudfSerializtion have a callback  between reading the data into host memory and putting that data on the GPU.
In this case I think it is in between these two lines.
https://github.com/rapidsai/cudf/blob/c39e9168c6d08236f36e5c3203b3ba8d145e86ed/java/src/main/java/ai/rapids/cudf/JCudfSerialization.java#L1521-L1522
return readTableFrom(header, hostBuffer);

will copy the data from the host buffer to the device and then turn it into a table.
After that is done then you would change the shuffle code to grab the semaphore as a part of the callback instead.
https://github.com/NVIDIA/spark-rapids/blob/fdf731c59661d0328c591d9e90786d9ac0cd6f65/sql-plugin/src/main/scala/com/nvidia/spark/rapids/GpuColumnarBatchSerializer.scala#L152
This only fixes the reading side of the issue.  Very similar changes could be made for the write side.

@revans2
In the GpuShuffledHashJoin case，once a task had taken the semaphore，it think it should hold it until this task has finished processing all it's input data, because the hash-map should stay in the gpu memory. In this case, only the tasks holding the semaphore can do shuffle fetch from upstream, so only 2 or 3 task can do data reading from disk/net, but 2 or 3 task can not feeding the gpu enough. I do not understand whether the callback will help    https://github.com/NVIDIA/spark-rapids/issues/679#issuecomment-689520518
.

@revans2  In RapidsShuffleManager, i see there exists a producer-consumer model, does this a async thread pool to do shuffled data fetch?

This only fixes the reading side of the issue. Very similar changes could be made for the write side.

what do you mean by reading side and writing side？ @revans2

@JustPlay there is a lot going on here with shuffle.  The small change that I explained here is a simple thing that we can do right away to improve performance when spark shuffle is being used.  You are right it will not fix the issue totally, especially in the case of a join.
But like I said here that is going to take an in-depth design to work out how to fix it. If you want to try and do that design I would be happy to review it, but as it stands right now I have other things on my plate that prevent me from doing it.

what do you mean by reading side and writing side？ @revans2

In a shuffle there are two phases.  The output of one tast is written and becomes the input to another task that reads it.  The GPU semaphore is involved in both cases, although the reading side tends to be more of a problem, because it is generally remote.

Is your feature request related to a problem? Please describe.
move some deserialization code out of the scope of the gpu-semaphore to increase cpu concurrent
Describe the solution you'd like
https://github.com/NVIDIA/spark-rapids/blob/625cd6c40417205a0135ad1d86219b23c4e846af/sql-plugin/src/main/scala/com/nvidia/spark/rapids/GpuColumnarBatchSerializer.scala#L152
JCudfSerialization.readTableFrom() contains both high-overhead cpu code and gpu-code, the gpu-code (include device memory allocation and copy) should be executed within the scope of gpu-semaphore, but the cpu-code DO NOT NEED
https://github.com/rapidsai/cudf/blob/19237a09fe9b80706ef463580c6a646f6f9ec2ae/java/src/main/java/ai/rapids/cudf/JCudfSerialization.java#L1505
this function i think do the following things
1. deserialization (not so sure)

2. alloc host-memory (pin-memory)

3. call the reloaded function to copy data form host to gpu

the step 1,2 do not need the gpu-semaphore, and it's better to get out of the gpu-semaphore
https://github.com/rapidsai/cudf/blob/19237a09fe9b80706ef463580c6a646f6f9ec2ae/java/src/main/java/ai/rapids/cudf/JCudfSerialization.java#L1522
only this line of code need the protect of the gpu-semaphore
all code before it do not touch the device memory, only touch host-buffer (pin-memory), so i think those code can be executed without holding the gpu-semaphore (just like the Scan operator)
I thinks, we should move some code from cuDF into rapids
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context, code examples, or references to existing implementations about the feature request here.

why not just copy the related code snippet(s) into rapids-plugin?

We have modify rapids and tested it，the performance improvement is negligible
Just like what you have  mentioned

We agree that in the ideal case I/O should not happen while the semaphore is held, but there is not a simple solution to this. We can fix it for the deserialization code, like was requested, but it will only help for the very first batch being read. We need a more holistic approach to this to make it work properly and quickly.

The issue is about memory management. The GpuSemaphore is in place to limit the number of tasks that can be on the GPU at any point in time so the processing cannot use too much GPU memory, which will kill the job. If we allow a task to release the semaphore while holding on to GPU memory then the GpuSemaphore is not doing its job.
We agree that in the ideal case I/O should not happen while the semaphore is held, but there is not a simple solution to this. We can fix it for the deserialization code, like was requested, but it will only help for the very first batch being read. We need a more holistic approach to this to make it work properly and quickly.
We are still trying to think through what the ideal solution would look like, but with the 0.2.0 release close by, we have been a bit distracted trying to get everything ready for that.
In general I see a few things we want.
1. All data that is not actively being processed needs to be stored in the RapidsBufferCatalog.

* The code right now is specific to Shuffle, but I am in the process of making it more generic for 0.3.0.  There still needs to be a bunch of micro-benchmarks to see what level of performance impact this might have for code that commonly will not spill.  This is here to act as a backup in case we get something wrong when releasing the semaphore early.

1. Try to concentrate I/O.  There really are two approaches we could take here, and a final solution is likely to be a combination of both of them.

* We could have the shuffle layer be aware of the desired batch size and wait for the desired amount of data to be available on the host side before sending any of the data on.  This should hopefully make it so that GpuCoalesceBatches does not have to wait for data. The problem is that it shifts memory pressure to the host side and/or may result in more memory pressure in general when using UCX shuffle.  So to make this work we would need to figure out a way to insert CPU side data into our RapidsBufferCatalog as well, not just GPU side data.

* We could have a way for shuffle to signal that there is no more data available right now.  This would let the GPU start processing data early, even if it is less efficient at it, but would not solve the issue when all of the data for a given partition is required for an operation (sort for example).  The other issue with this is that spark only provides an iterator interface for us to use, so we would either have to do something out of band, or have special metadata in the batch to indicate that this is the end of the non-blocking I/O, which is not super simple, because spark does not let us extend the `ColumnarBatch` class.

1. Implement out of core processing.  This would let us move away from requiring all of the data be in memory.  The problem is that this would come with a trade-off of spilling, which is likely to slow things down even more.

We will take a deeper look at it， and hope we have the ability to try to impl them。Thanks。

The original ask in the description has been implemented in #4396, and we're working on an additional optimization to avoid holding the semaphore during shuffle in some join cases via #4539.


Code cleanup and commit after db queries

Coverage decreased (-0.07%) to 91.979% when pulling 47ad50a4133a89501713085e2d393ed76d912db0 on ehenneken:db_connections into e1aaaf17890af3743d24f79c3b97e0b3f2672ae1 on adsabs:master.


SPA code sample adds two cookies

After copying the code sample provided for use with AngularJS, I noticed that two antiforgery cookies are being added: XSRF-TOKEN and .AspNetCore.Antiforgery.xxxxxxxxxxx. This appears to be because we're calling antiforgery.GetAndStoreTokens(context) rather than antiforgery.GetTokens(context).
Given that GetAndStoreTokens will add the cookie on our behalf anyway, maybe the sample should just set the name of the cookie when configuring the service (which is what I have done in my application).

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

ID: 47b14f57-82ac-a2e2-cbc7-22a81a60f4ac
Version Independent ID: bffca13c-223f-c61f-9cb2-9da8811eecfa
Content: Prevent Cross-Site Request Forgery (XSRF/CSRF) attacks in ASP.NET Core
Content Source: aspnetcore/security/anti-request-forgery.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @steve-smith
Microsoft Alias: riande

Since I nearly assumed the same thing, I did a little research on this.  It looks like this is the correct behavior because one is the request token (stored in a cookie so that JS can access it) and another is the session cookie token.  See this excellently written article here for details: https://www.dotnetcurry.com/aspnet/1343/aspnet-core-csrf-antiforgery-token.

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.


As a familiar user, I can look for contact information quickly using keywords like name, phone number or email

... so that I can obtain the other details of the contact

#28 #23


feat: sync CRD and ingress resource to apisix mechanism.

Type of change:

[ ] Bugfix
[x] New feature provided
[ ] Improve performance
[ ] Backport patches

What this PR does / why we need it:

Pre-submission checklist:
Quote:

#234
#1022

Resolve: #1099

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Codecov Report

Merging #1102 (fa3ea55) into master (5756273) will decrease coverage by 0.60%.
The diff coverage is 6.01%.

@@            Coverage Diff             @@
##           master    #1102      +/-   ##
==========================================
- Coverage   32.08%   31.48%   -0.61%
==========================================
  Files          78       78
  Lines        8795     8969     +174
==========================================
+ Hits         2822     2824       +2
- Misses       5666     5838     +172
  Partials      307      307

Impacted Files
Coverage Δ

pkg/ingress/apisix_cluster_config.go
0.00% <0.00%> (ø)

pkg/ingress/apisix_consumer.go
0.00% <0.00%> (ø)

pkg/ingress/apisix_pluginconfig.go
0.00% <0.00%> (ø)

pkg/ingress/apisix_route.go
0.00% <0.00%> (ø)

pkg/ingress/apisix_tls.go
0.00% <0.00%> (ø)

pkg/ingress/apisix_upstream.go
0.00% <0.00%> (ø)

pkg/ingress/controller.go
0.40% <0.00%> (-0.05%)
:arrow_down:

pkg/ingress/ingress.go
6.16% <0.00%> (-0.39%)
:arrow_down:

cmd/ingress/ingress.go
79.43% <100.00%> (+0.19%)
:arrow_up:

pkg/config/config.go
66.34% <100.00%> (+0.32%)
:arrow_up:

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 0f95dbe...fa3ea55. Read the comment docs.

could you merge latest code? thanks!

could you merge latest code? thanks!

Done.


[uwp] Frame.Navigate( typeof(non_xaml_class_derived_from_Page)) crashes w/ Native Toolchain

Describe the bug
When given a Non-XAML (pure code) class derived from Page, Frame.Navigate crashes when compiled using Native Toolchain.
Steps to reproduce the bug
USING SAMPLE PROJECT

Clone the following repo: https://github.com/baskren/NativeToolchain_NonXamlPage_crash.git
Run in Debug WITHOUT Native Toolchain
Click NOT A XAML PAGE button to navigate from XAML PAGE to NOT A XAML PAGE, successfully
Run in Debug WITH Native Toolchain or run in Release
Click NOT A XAML PAGE button to crash app.

FROM SCRATCH

Create a new UWP App
Create a new class file, named NoXaml.cs and derive the class NoXaml from Windows.UI.Xaml.Controls.Page
Add [Windows.UI.Xaml.Data.Bindable] attribute to the NoXaml class
In App.xaml.cs, replace rootFrame.Navigate(typeof(MainPage), e.Arguments); with rootFrame.Navigate(typeof(NoXaml), e.Arguments);
In the project's options, enable the Native Toolchain
Build, run, watch crash

Expected behavior
Frame.Navigate works with Non-XAML Pages.
Screenshots

IDE
Visual Studio 2019
NuGet package version
No response
Project type

[X] Packaged
[X] Unpackaged

Windows version
May 2021 Update (19043)
Additional context
Note: recommendation from https://github.com/microsoft/microsoft-ui-xaml/issues/1949 was applied

Duplicate of microsoft/microsoft-ui-xaml#6250


The README cannot be read when publishing with lerna

Your Environment

verdaccio version: v6.0.2
node version [21.1.0]:
package manager<EMAIL_ADDRESS>os: [mac,  linux]
platform: [npm]

Describe the bug
With lerna, this happens, but with npm publish, it doesn't. The problem is described below:
ERROR: No README data found!

The result is:

The downloaded zip contains the README file：

Could you share how the Lerna setup looks like in your side ?

Yes, all packages have README files

Which version of lerna? What's in package.json?

8.1.9

I don't see neither with pnpm or npm as package manager at Lerna the readme content is being send. If you test with non Lerna project the readme content is a property of the body as text, this is being used as readme.
So I don't think so this is a verdaccio issue, rather Lerna is not picking up the readme content correctly.

this is how it looks like with the readme as property.


Feat/stats

This implements an endpoint /v1/stats that returns a JSON like so:
{
  "total_time_transcribed": 1233.167166
}

It's just stored in redis, so we should make sure that redis persists to disk so that we don't lose the stats (and the jobs, too) if we kill redis – do you know if it already does that @auduny? :)

I'm not a big fan of how we're passing the redis connection around to lots of functions. We can refactor this later so it's just using a global connection or something.

Actually that'd be really great to have, thanks for reminding me @Johannes-Andersen! Added a test!


AcrylicWindow Border does not respond to system color changes

Hi, When using fw:AcrylicWindow.Enabled="True", the window border does not change when the system accent color changes.

Hi, @DHitchenUK
Sorry for replying so late.
I'll fix it in next update.
Please, wait for a while.


meta: high rate of 5XX errors from go.googlesource.com since 2021-09-08

#!watchflakes
post <- `https://go\.googlesource\.com.*: The requested URL returned error: 5\d\d`

Some of the cmd/go long-mode tests end up cloning repos controlled by the Go project, such as golang.org/x/sys.
Other long-mode tests send requests to a dedicated test server (vcs-test.golang.org), various GitHub repos, packages hosted on rsc.io, and gopkg.in. The failure rate against vcs-test.golang.org is, as far as I can tell, negligible. The GitHub and gopkg.in tests for the most part check integration with services outside the control of the Go project. The rsc.io tests have a low but nontrivial failure rate (filed as #49954), and could perhaps be migrated to vcs-test.golang.org if need be.
However, the dependency on go.googlesource.com for the x repos is not easy to avoid, and as far as I can tell its failure rate since September has dwarfed all of those other services. Many of these failures already result in long (2m+) hangs that could otherwise push the test over its deadline, so I don't think it would be viable to just add retries (#28194) — especially given that if the problem could be fixed by retrying, the server could presumably do that retry internally itself.
I would rather not lose coverage or add complexity to the tests by fetching the Go repos only through proxy.golang.org — @golang/release, is it viable to get a higher SLA on go.googlesource.com?

greplogs --dashboard -md -l -e 'https://go\.googlesource\.com.* 5\d\d\b' --since=2021-01-01

2022-01-10T17:06:19-9e7ea35/linux-386-longtest
2022-01-05T21:22:03-2b39d86/linux-386-longtest
2021-12-08T15:30:52-9fe77de/linux-amd64-longtest
2021-12-03T21:23:11-b3e1fbf/linux-386-longtest
2021-12-02T23:34:26-5f65520/linux-386-longtest
2021-12-02T22:03:11-d3bf627/linux-386-longtest
2021-12-02T20:49:56-bbe1be5/linux-386-longtest
2021-12-02T20:45:47-3c6295d/linux-386-longtest
2021-12-01T17:13:34-08ecdf7/linux-386-longtest
2021-11-30T20:04:58-7ccbcc9/linux-386-longtest
2021-11-30T18:49:39-5f63f16/linux-amd64-longtest
2021-11-30T18:09:02-931d80e/linux-386-longtest
2021-11-30T18:09:02-931d80e/linux-amd64-longtest
2021-11-29T22:02:48-2f6d382/linux-386-longtest
2021-11-24T21:11:45-b77f5f9/linux-386-longtest
2021-11-24T21:09:36-7e5331a/linux-amd64-longtest
2021-11-23T19:31:05-0f64c21/linux-amd64-longtest
2021-11-19T21:36:17-0f75a9e/linux-amd64-longtest
2021-11-16T14:33:48-50dac3b/linux-386-longtest
2021-11-11T20:20:42-3e94140/linux-386-longtest
2021-11-11T13:58:28-d76b1ac/linux-386-longtest
2021-11-10T18:24:14-6406e09/linux-amd64-longtest
2021-11-09T22:58:24-578ada4/linux-386-longtest
2021-11-09T19:01:20-526b2ef/linux-386-longtest
2021-11-09T18:23:16-55e6e82/linux-amd64-longtest
2021-11-08T16:44:14-7ee3f14/linux-amd64-longtest
2021-11-05T17:47:28-6f32d20/linux-386-longtest
2021-11-05T00:52:04-1c4cfd8/linux-386-longtest
2021-11-04T21:52:36-8ad0a7e/linux-386-longtest
2021-11-04T14:17:18-901bf29/linux-386-longtest
2021-11-03T20:30:17-7f2463c/linux-amd64-longtest
2021-11-02T13:43:24-4d7bf41/linux-386-longtest
2021-11-01T19:42:30-5f1bcd1/linux-386-longtest
2021-11-01T15:55:29-0ae4c7f/linux-amd64-longtest
2021-10-29T19:35:47-5ec139f/linux-386-longtest
2021-10-29T18:56:29-6afdf01/linux-386-longtest
2021-10-29T18:35:59-5ec2427/linux-386-longtest
2021-10-29T18:35:20-9ac1ee2/linux-386-longtest
2021-10-29T18:23:03-413672f/linux-386-longtest
2021-10-28T20:27:44-5e21728/linux-amd64-longtest
2021-10-28T16:54:29-5fce1d9/linux-386-longtest
2021-10-28T01:15:26-b2fe2eb/linux-386-longtest
2021-10-27T21:37:54-749f6e9/linux-386-longtest
2021-10-27T20:24:48-a155a30/linux-386-longtest
2021-10-27T20:03:17-68bd512/linux-386-longtest
2021-10-27T19:34:49-ffd2284/linux-386-longtest
2021-10-27T19:18:20-514ebae/linux-386-longtest
2021-10-27T18:08:49-bb49eb3/linux-386-longtest
2021-10-26T20:12:32-f8779b9/linux-amd64-longtest
2021-10-26T17:10:45-76cef81/linux-amd64-longtest
2021-10-26T14:24:17-283d8a3/linux-386-longtest
2021-10-25T17:46:41-9012996/linux-amd64-longtest
2021-10-22T00:57:18-9ff91b9/linux-amd64-longtest
2021-10-21T19:08:43-b8da7e4/linux-386-longtest
2021-10-21T02:35:47-fca46d0/linux-386-longtest
2021-10-12T20:20:41-d032b2b/linux-386-longtest
2021-10-12T14:32:53-36a265a/linux-386-longtest
2021-10-05T19:28:36-7ae83c8/linux-386-longtest
2021-10-01T14:30:33-8d494b0/linux-386-longtest
2021-09-27T19:42:34-315cec2/linux-386-longtest
2021-09-21T14:02:52-7d67f8d/linux-amd64-longtest
2021-09-15T17:32:52-6196979/linux-386-longtest
2021-09-15T17:32:52-6196979/linux-amd64-longtest
2021-09-15T16:32:27-72bb818/linux-386-longtest
2021-09-15T16:32:27-72bb818/linux-amd64-longtest
2021-09-14T23:20:18-2933c45/linux-386-longtest
2021-09-14T23:07:15-137543b/linux-amd64-longtest
2021-09-14T23:03:28-3a72175/linux-amd64-longtest
2021-09-13T21:48:41-42057e9/linux-386-longtest
2021-09-13T20:42:44-81a4fe6/linux-386-longtest
2021-09-09T01:25:40-d4579c2-d62866e/darwin-arm64-11_0-toothrot
2021-09-08T16:59:47-d419f9c/linux-amd64-longtest
2021-09-08T16:19:36-409434d/linux-386-longtest
2021-05-26T22:43:54-1d5298d/linux-amd64-longtest

is it viable to get a higher SLA on go.googlesource.com?

We should also check to make sure these errors are accurately reflected in the monitoring for these services. (It isn't obvious to me that they are even showing up.)

https://storage.googleapis.com/go-build-log/ddd0e862/linux-386-longtest_852ae099.log (a TryBot on https://go.dev/cl/382839)

greplogs -l -e 'https://go\.googlesource\.com.* 5\d\d\b' --since=2022-04-12
2022-04-27T17:20:34-f0ee7fd/linux-386-longtest
And I've noticed another log pattern that seems to be the same failure mode, just through the git binary instead of go:
greplogs -l -e 'golang\.org/x.*: git fetch .*: exit status 128:\n\s+.*The requested URL returned error: 502' --since=2021-01-01
2022-05-02T17:05:14-64369c3/linux-386-longtest
2022-04-28T15:11:42-4d35071/linux-amd64-longtest
2022-01-21T16:59:19-9eba5ff/linux-amd64-longtest
2022-01-20T19:24:26-2c2e081/linux-386-longtest
2022-01-10T22:48:40-6019a52/linux-amd64-longtest
2022-01-05T21:22:03-2b39d86/linux-386-longtest
2021-12-02T22:03:54-25f06cb/linux-386-longtest
2021-11-30T18:09:02-931d80e/linux-amd64-longtest
2021-11-10T18:24:14-6406e09/linux-amd64-longtest
2021-11-09T19:01:20-526b2ef/linux-386-longtest
2021-11-04T21:52:36-8ad0a7e/linux-386-longtest
2021-11-01T22:55:50-02e5913/linux-amd64-longtest
2021-10-29T18:56:29-6afdf01/linux-386-longtest
2021-10-28T16:54:29-5fce1d9/linux-386-longtest
2021-10-28T16:08:36-6f0185b/linux-386-longtest
2021-10-27T21:37:54-749f6e9/linux-386-longtest
2021-10-27T20:03:17-68bd512/linux-386-longtest
2021-10-26T21:17:38-091db63/linux-amd64-longtest
2021-10-22T00:57:18-9ff91b9/linux-amd64-longtest
2021-10-12T20:20:41-d032b2b/linux-386-longtest
2021-09-15T17:32:52-6196979/linux-amd64-longtest
2021-09-15T16:32:27-72bb818/linux-386-longtest
2021-09-14T23:07:15-137543b/linux-amd64-longtest
2021-09-14T23:03:28-3a72175/linux-386-longtest
2021-09-08T16:19:36-409434d/linux-386-longtest
2021-06-28T23:31:05-1519271/linux-amd64-longtest
2021-05-26T22:43:54-1d5298d/linux-amd64-longtest

greplogs -l -e 'golang\.org/x.* git .*\n(\s+.*)*The requested URL returned error: 502' --since=2022-05-03
2022-05-05T14:26:30-1926fa5/linux-amd64-longtest

greplogs -l -e 'golang\.org/x.* git .*\n(\s+.*)*The requested URL returned error: 502' --since=2022-05-05
2022-05-09T20:24:02-13bda0e/linux-amd64-longtest
2022-05-09T18:06:51-0d410d6/linux-amd64-longtest
2022-05-09T16:02:28-9ae7dc3/linux-amd64-longtest
2022-05-05T14:26:30-1926fa5/linux-amd64-longtest

Converting mod_invalid_version to use the local vcweb would help a lot with these; it seems to be the one that hits this most often.


ConvoyEFS not working

Describe your issue here
I'm trying to set up a storage pool with Convoy-EFS on a cluster with 2 EC2 hosts.
The storage-pool-agent works, but the volume-agent-efs containers won't work are are stoped.

Useful
Info

Versions
Rancher v1.1.3 Cattle: v<IP_ADDRESS> UI: v1.1.12

Access
localauth admin

Orchestration
Cattle

Route
service.containers

Hi @opichon. Can you share the log output of one of the volume-agent-efs container?


 I love this theme very much. I have always missed the trapezoidal tabs from the old days. This brings it back really nicely! Thanks!
However, I noticed that when I select compact as my density, the hamburger menu in the top right corner becomes super compact.
Normal:

Compact:

I'm 80% sure that the menus in Compact weren't supposed to be that compact. Maybe you could fix this? Or maybe not because Compact is "not supported" anymore?
Steps to reproduce:

Head to about:config and set the value of browser.compactmode.show to true
Right-click anywhere on the blank space of the tab bar.
Click "Customize Toolbar..."
In the bottom left corner, click "Density" and select "Compact (not supported)"
Close the "Customize Firefox" or "Customize Nightly" tab
Click the hamburger menu, the bookmarks menu, or the downloads menu.
Admire its compactness

Firefox Nightly, version 92.0a1, build ID<PHONE_NUMBER>3320 on Manjaro

Hi. As planned, the compact mode will be used on monitors below 1080p, which is why the menus are made as compact as possible. I had plans for their revision, but all hands do not reach. Today I was going to upload an update with improvements, and since you have touched on this topic, I will try to add the ability to control the size of context menu items to the update. But if I do not have time to do it today, then I will add this feature in the next release.

The sizes of elements can now be controlled in the section "User preferences". I have already set 4px, but you can set your own. Not all elements are well-crafted, but I will refine it in the future. Check the update

Hi! I tried out the update and set --menu-margin-padding to 6px. It's compact and beautiful. Thanks! My favorite Firefox CSS theme so far!


Update contributing.md with appropriate link to golangci-lint

Two small document changes

Updated link in contributing.md to point to golangci-lint's website (it was pointing to the website for the pre-commt project).
Updated existing warning in README.md regarding auto-generated code. I simply added a Warning admonition command in Markdown to make this more easily stand out to the reader.

[x] I certify that this PR does not contain any code that has been generated with GitHub Copilot or any other AI-based code generation tool, in accordance with this project's policies.

Description
Basic documentation update to fix a link that redirects the reader to a resource not related to the link itself (goes to pre-commit instead of the link's text: golangci-lint)
Testing done

How did you test your changes?

Committed my code to my fork of the project, then clicked the link and checked that it routed me to golangci-lint.run from GitHub's markdown viewer.
Also visually verified that the Warning admonition appears in the README.md file

Does this code require any new tests to be written?

N/A - documentation change only

Additional info
Resolves issue #83

@echarlesgrasby thank you!!!


Dealing with slash in subscription name for terraform and MS quirkiness

Azure allow / in the sub name however the API endpoint return wrongly even we
encode the / into %2F. Get
https://management.azure.com/subscriptions/CALM-WFM-Development-Dev%2FTest/providers?api-version=2016-02-01
into your browser and see, azure will return sub not found and the sub name is
the first part of the slash only.
However ID seems to work.
This changes put some more debugging and try to parse and use the ID if found a slash.

Dont think we should be logging any kind of SP related data.

Ouch! Will remove it :)

Dont think we should be logging any kind of SP related data.

Ouch! Will remove it :)

Dont think we should be logging any kind of SP related data.

Hey it is just subscriptions! Is it regarded as secrets though?

Dont think we should be logging any kind of SP related data.

Hey it is just subscriptions! Is it regarded as secrets though?

Putting name into subscriptionId field is incorrect.


'node_modules' should be excluded in tsconfig.json

tsconfig.json is missing exclude for at least "node_modules" folder

I though so to, but this is not required if you run typings like so:
npm run postinstall
or
npm run typings install
or if you have typings installed globally execute:
typings install
Thus many of the "Duplicate Identifier errors" go away!

@anik786 Not sure how your answer relates to the initial issue. It is not about typings and postinstall.

I had issues when running typescript, when "node_modules" was not in the excludes of "tsconfig.json". However when I installed the typings, all the errors went away. Not sure why.
But you may still be right in that "node_modules" should still be there.

node_modules is automatically excluded unless you specify files or excludes in the tsconfig in which case you are on your own.
Closing as your issue is old. Please re-open as a new issue if problem persists.


Vue-cli create project fails with Sass/SCSS (with node-sass) in Node.js 16

Version
4.5.13
Environment info
Mac OS Big Sur 11.2.3
node v16.1.0
npm 7.13.0
@vue/cli 4.5.13

Steps to reproduce
vue create vue4
Vue CLI v4.5.13
? Please pick a preset: Manually select features
? Check the features needed for your project: Choose Vue version, Babel, TS, Router, CSS Pre-processors, Linter
? Choose a version of Vue.js that you want to start the project with 3.x
? Use class-style component syntax? No
? Use Babel alongside TypeScript (required for modern mode, auto-detected polyfills, transpiling JSX)? Yes
? Use history mode for router? (Requires proper server setup for index fallback in production) Yes
? Pick a CSS pre-processor (PostCSS, Autoprefixer and CSS Modules are supported by default): Sass/SCSS (with node-sass)
? Pick a linter / formatter config: Prettier
? Pick additional lint features: Lint on save
? Where do you prefer placing config for Babel, ESLint, etc.? In dedicated config files
? Save this as a preset for future projects? Yes
? Save preset as: LAst Vue4
What is expected?
Installed project
What is actually happening?
Too many npm errors when installing dependancies.
npm ERR! code 1
npm ERR! path /Users/admin/Documents/WWW/myland.loc/vue4/node_modules/node-sass
npm ERR! command failed
npm ERR! command sh -c node-gyp rebuild
npm ERR! CXX(target) Release/obj.target/libsass/src/libsass/src/ast.o
npm ERR!   CXX(target) Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o
.... many lines of errors ....
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR!      /Users/admin/.npm/_logs/2021-05-14T08_02_09_147Z-debug.log
ERROR  command failed: npm install --loglevel error --legacy-peer-deps

The problem occurs when Sass/SCSS (with node-sass) - selected

node-sass is deprecated, please avoid using it if possible (use sass instead). Vue CLI v5 won't provide this option on creation anymore.
Node.js 16 is too new. node-sass has only released a version that supports Node.js 16 days ago. Vue CLI still creates projects with an older version of node-sass, which supports Node.js 14 at most.

I add the same error, but I used the command:
npm install node-sass
It's working on node 16.6.1


#588 - Add missing repository rbac roles for porch controllers

This change adds missing repository rbac roles for the porch controllers.
Context -
The use cases are working, but after someone creates a PVS or PV and points to a repo, the controller logs are populated with errors saying the controllers cannot 'get' the repositories.

/approve

/lgtm
/approve


Overfitting problem

Hello,
I cloned your repo and downloaded your dataset, but I could not get the same result as yours.
I train the model on 4 GeForce GTX 1080 Ti GPUs, and keep other arguments as the same. But it turns out to be overfitting.
After 100 epochs, I got prec@1 at 99% and prec@5 at 100% on the train set, but only prec@1 at 48% and prec@5 at 73% on the test set.
Here is part of the log:
DFL-CNN <==> Train <==> Epoch: [113][103/107]
Loss 0.5459 (0.5661)	Loss1 0.0756 (0.0739)	Loss2 0.0004 (0.0289)	Loss3 4.6985 (4.6324)
Prec@1 (99.880)	Prec@5 (100.000)
DFL-CNN <==> Train <==> Epoch: [113][104/107]
Loss 0.5188 (0.5656)	Loss1 0.0508 (0.0737)	Loss2 0.0076 (0.0287)	Loss3 4.6041 (4.6321)
Prec@1 (99.881)	Prec@5 (100.000)
DFL-CNN <==> Train <==> Epoch: [113][105/107]
Loss 0.5771 (0.5657)	Loss1 0.0774 (0.0737)	Loss2 0.0189 (0.0286)	Loss3 4.8082 (4.6338)
Prec@1 (99.882)	Prec@5 (100.000)
DFL-CNN <==> Train <==> Epoch: [113][106/107]
Loss 0.8110 (0.5672)	Loss1 0.3277 (0.0753)	Loss2 0.0100 (0.0285)	Loss3 4.7324 (4.6344)
Prec@1 (99.883)	Prec@5 (100.000)

DFL-CNN <==> Test <==> Epoch: [ 106] Top1:48.050% Top5:73.093%
DFL-CNN <==> Test <==> Epoch: [ 108] Top1:48.913% Top5:73.404%
DFL-CNN <==> Test <==> Epoch: [ 110] Top1:47.515% Top5:72.575%
DFL-CNN <==> Test <==> Epoch: [ 112] Top1:48.205% Top5:72.765%

During training the model, overfitting problem is inevitable. Because there are only about 6000 images for training, but there are too many parameters in VGG16.
Have you ever met the overfitting problem? And how did you get rid of it?
Looking forward to your reply!
Thank you very much!

hello,I get the same problem,I haven't saw the "Test  Epoch"ａｐｐｅａｒｅｄ worse ,it still training...now.
I set learning-rate', default=0.001,How about you?Do you have any better ｐｒｏｐｏｓａｌｓ?
DFL-CNN <==> Train Epoch: [201][1159/1494]
Loss 1.6247 (1.4218)	Loss1 1.6245 (1.4152)	Loss2 0.0000 (0.0000)	Loss3 0.0023 (0.0649)
Top1 100.000 (100.000)	Top5 100.000 (100.000)
DFL-CNN <==> Train Epoch: [201][1160/1494]
Loss 1.5835 (1.4219)	Loss1 1.5780 (1.4154)	Loss2 0.0000 (0.0000)	Loss3 0.0543 (0.0649)
Top1 100.000 (100.000)	Top5 100.000 (100.000)

@fxle  Test log is saved in DFL_CNN/log/log_text.txt .

@pengshiqi Oh,thank you very much! I find it .It seems to be improving.Bｕｔ the Loss2 ｖａｌｕｅ looks a little strange.In addition,Do you think the idea of 'filter bank' in this paper can improve rotation invariance at the same time?
DFL-CNN <==> Test <==> Epoch: [ 198] Top1:76.338% Top5:91.284%
DFL-CNN <==> Test <==> Epoch: [ 200] Top1:75.854% Top5:91.042%
DFL-CNN <==> Test <==> Epoch: [ 202] Top1:75.837% Top5:91.111%

@fxle
DFL-CNN <==> Train Epoch: [323][2/125]
Loss 3.3836 (3.4424)	Loss1 3.1195 (3.1667)	Loss2 0.0326 (0.0284)	Loss3 2.3149 (2.4724)
Top1 100.000 (100.000)	Top5 100.000 (100.000)
DFL-CNN <==> Train Epoch: [323][3/125]
Loss 3.4611 (3.4471)	Loss1 3.2075 (3.1769)	Loss2 0.0126 (0.0245)	Loss3 2.4100 (2.4568)
Top1 100.000 (100.000)	Top5 100.000 (100.000)

DFL-CNN <==> Test <==> Epoch: [ 318] Top1:72.679% Top5:90.991%
DFL-CNN <==> Test <==> Epoch: [ 320] Top1:72.592% Top5:91.094%

Sure, the loss2 is much lower than the other losses. But I don't think that loss2 is strange. It is loss1 and loss3 that look strange. After hundreds of epochs training, they are still very large, which seems abnormal.
I think a potential cause for this problem is that the 1x1 convolutional layer is not initialized randomly, as described in Section 3.3, which has not been implemented in this code.

@ Yes, you are right.It's not initialized .Do you know how to make it? I have some ideas to communicate with you.I suggest we add a qq.my qq numbers are :260730636

@pengshiqi @fxle  I changed the model using a dropout layer. During training the model, I got loss2 decrease, loss 1 & 3 is basically not reduced. do you got same situation？

@techzhou No，I didn't use a dropout layer.Maybe you can try to use regularization or Section 3.3 Layer Initialization to make it perform better,

@techzhou
Hi, how about the accuracy after u implement dropout layer? did it increase a little bit?
I just think dropout may help.
thanks!

@pengshiqi hi, how do you solve the overfitting problem?

@pengshiqi hi, how do you solve the overfitting problem? @XIELeo @fxle @techzhou @Ien001 @

@pengshiqi hi, how do you solve the overfitting problem? @XIELeo @fxle @techzhou @Ien001 @

The default hyper-parameters are imperfect. You can adjust the learning rate and the loss weights to get a better result.

@pengshiqi hi, how do you solve the overfitting problem? @XIELeo @fxle @techzhou @Ien001 @

@wsqat  The default hyper-parameters are imperfect. You can adjust the learning rate and the loss weights to obtain better results.

@pengshiqi
Hi, I trained by adjusting the learning rate but ciuld only hit 52% accuracy. Can you share the weights of the model where you got 72% accuracy. Or can you mention any hyper parameters or code changes which could help me get better accuracy?


Add the version number to the help menu

PR related to #347, #298, #297, #296 to supply information about the currently used VOTT version. This way, the version number will simply be displayed as entry inside the "Help" menu. It may be a small stepp to add it to the titlebar or maybe as color coded information as mentioned in those issues.
Note, this is the version as defined in the package.json.
https://github.com/Microsoft/VoTT/blob/ec6057c4c95780f7547d5c55245c6f48b396e29c/package.json#L3
This works when starting the app with npm start, however may fail with a build version (not tested).

Thanks, although this touches the issues mentioned above this truly only closes #347


Add UdpSocket::PeerAddr #307

Add UdpSocket::PeerAddr in #307.
The test is passed.

Thanks for your merge. May I ask that could I look at the std-lib in rust, comparing with async-std, and add all the function that in std but not in async-std? I'd like to do this, because I see that async-std is a async version of std. ( Just my thought, I don't know whether it right or wrong).


[openssl-unix] Update header path for shared library compilation

Describe the pull request

What does your PR fix? Fixes issue #

Doesn't currently fix an issue

Which triplets are supported/not supported? Have you updated the CI baseline?

All triplets, including custom triplet for compiling Linux shared libraries

Does your PR follow the maintainer guide?

Yes

Thanks for your PR! Can you please correct the Version field in the CONTROL file? You can get more information from maintainer-guide.md.

Thanks for your PR! Can you please correct the Version field in the CONTROL file? You can get more information from maintainer-guide.md.

Thanks, I've updated the version. Sorry about that.

/azp run

/azp run

/azp run

/azp run

This PR fixes the issue for me. Thanks.

@here-mikelley Thanks for the PR and thanks @fabiencastan for confirming the fix!


Custom test function names are not handled

I am working on a project for which we have cutomized the python_functions option value (using the pyproject.toml file). In this case neotest-python does not detect the tests.
I tried fiddling with the treesitter query and it does solve the issue.

Do you have an existing workaround while this is still being looked at? I don't know how to request a bump for your pr.

There are two things you can do

Since this repo hasn't had any update since my pr, you can just point your plugin manager to my PR branch on my fork, as long as the repo is not updated you won't miss any new feature
Modify the treesitter query on your local copy of the plugin's lua code. That's what I have done at work. Personally I still use packer, so the file is located at ~/.local/share/nvim/site/pack/packer/start/neotest-python/lua/neotest-python/base.lua


SCB-1374 support fsm redis channel

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-1.7%) to 81.113% when pulling b59180ac966ef7721eb107f0fdc35d81242caed6 on cmonkey:feature/scb-1374 into 24bbd149857339a0e14e3753d8ffe401e4a7a00e on apache:master.

LGTM, Thank you for your contribution


Upgrade to eslint@2 and friends.

Closes #295

Current coverage is 84.27%

Merging #311 into next will increase coverage by +19.65% as of 66280e1

@@             next    #311   diff @@
=====================================
  Files          41      90    +49
  Stmts         540    1380   +840
  Branches        0       0
  Methods
=====================================
+ Hit           349    1163   +814
  Partial         0       0
- Missed        191     217    +26

Review entire Coverage Diff as of 66280e1

Powered by Codecov. Updated on successful CI builds.

You forgot to sync eslint config to boilerplate template.

You forgot to sync eslint config to boilerplate template.

Not sure what is the issue.

Oops. I thought the eslintConfig in boilerplate isn't compatiable with eslint 2. looks like it is


enhancement: contributing rules

Description
Create a development branch for users to develop template.
Main branch will be locked for all users, except GitHub actions
External users will fork wrappid-app and they will create Pull Request, after verification, it'll be merged to development branch
References
https://github.com/wrappid/.github-private/issues/1  (not followed now)
https://github.com/wrappid/.github/issues/8

below commit adds contributing file
99e68d12cce1ab727e7b03f04d1db0ef5ed75126
closing


Update README to reflect known issues

I was motivated to create this pull-request since I was having issues while trying to implement the library into my codebase. See the Github issue here: https://github.com/NoRedInk/elm-decode-pipeline/issues/37

Thank you for your PR!
I'm not sure this is the right place for this change.
The error in question looks like this:
-- NAMING ERROR -------------------- ./path/to/your/File.elm

This usage of variable `required` is ambiguous.

67|                         |> required "hullabaloo" string
                               ^^^^^^^^
Maybe you want one of the following?

    Json.Decode.Pipeline.required
    Html.Attributes.required

There are lots of namespace collisions across packages in Elm. Take, for instance, map which is I think in every library there is. (Maybe.map, List.map, Dict.map, Set.map, etc, etc, etc).
This type of warning feels like it's a language / error message comprehension problem. Do you have any suggestions for how that error message could have been more clear?

The error reported by Elm is a little confusing for Elm beginners, that's all. It will be nice if Elm can give you tips about how to resolve this kind of issues. And yes, this is not a bug on the elm-decode-pipeline lib, but again it will be nice to have documented this kind of scenarios somewhere in the library, maybe the README.md file is not the correct place but maybe in the Wiki page will be a good place. No?

I just think "less is more" in this regard. I appreciate the feedback and we'll keep it under consideration. If you have ideas around more helpful error messaging, the source is here: https://github.com/elm-lang/elm-compiler/blob/8a86d09f91c0b50141311309f72488074afed87a/compiler/src/Reporting/Error/Canonicalize.hs#L976

another place to report error messages is https://github.com/elm-lang/error-message-catalog/issues


creating a just for fun dataguide section and top dbs article

This PR adds a just for fun section to the data guide with an initial article covering the top database for each state in the USA
still do to - meta info

Need to also add a folder description


afl-fuzz crashes at launch (after latest commit)

Double free following the last commit
To reproduce on ubuntu 18.04
git clone https://github.com/aflnet/aflnet.git
cd aflnet; make clean all;
cd llvm_mode; make
cd .. ; make install

afl-fuzz -N tcp://<IP_ADDRESS>/1

Thank you very much for reporting the issue.
I tested that commit (contributed by an user) and the code also looks reasonable to me.
I will try to double check it soon. Do you receive the same error report when you run afl-fuzz with full arguments?

The problem occurs because a memory that defined on stack here is freed here.
The simplest code to describe this behavior (compiled with gcc 11.4 on ubuntu 22.04):
#include <stdlib.h>
int main( )
{
    char buf[8];
    char *tokens;
    //This malloc will cause the double free error probably because it affects values of the current stack
    tokens = (char*)malloc(1);
    free(buf);
    return 0;
}

I opened pull request for the fix :D

Thanks @ItsMagick . I have merged your PR.
Hi @V3rochka . Thanks for your elaboration on this. I think the issue here is because I did not call malloc for each element/string in the tokens so it does not make sense to free them one by one.
The two pieces of code you are referring have the same variable names (tokens) but they are local to the functions so I don't think that is the root cause.


command 'remote.editor.connectRemote' not found

I was able to sync once but afterwards I keep getting the error:
command 'remote.editor.connectRemote' not found

Command 'Remote Editor > Connect remote SSH' resulted in an error (command 'remote.editor.connectRemote' not found)  same problem here... any one hacked this issue ??


Error when trying to agglomerate by taxonomic level (altExp function)

Hi,
When trying to agglomerate the Summarized Experiment data by taxonomic level (e.g. Phylum) as explained in the tutorial, I get the error below:
My code:
se <- SummarizedExperiment(assays = list(counts = counts),
                                     rowData = tax,
                                     colData = samples)

altExp(se,"Phylum") <- agglomerateByRank(se, "Phylum")

The error I get:
Error in (function (classes, fdef, mtable)  :
  unable to find an inherited method for function ‘altExp<-’ for signature ‘"SummarizedExperiment", "character"’

The SE is correctly built as I can work with other functions in the package without any problems. I can also agglomerate by taxonomic level using the rank argument to perform the agglomeration on the fly and it works fine to get the prevalence. The problem seems to be only with "altExp". I don't know if it is possible to plot the prevalence using only the agglomeration on the fly.

Thank you,
Asier

Hi Asier!
Thanks for this issue. We are trying to make these tutorials as simple as possible, and that part is actually misleading.
SummarizedExperiment objects do not include altExp slot. However, TreeSummarizedExperiment objects have. You can easily convert SE into TreeSE.
That object in tutorials is actually TreeSE even though object's name is se. I think we should change that to be more consistent, because we are already using object names se and tse.
# There is no altExp slot
se
# Convert SE into TreeSE
se <- as(se, "TreeSummarizedExperiment")
# There is a altExp slot
se
# Now it works
se_phylum <- agglomerateByRank(se, "Phylum")
altExp(se,"Phylum")  <- se_phylum

I don't know if it is possible to plot the prevalence using only the agglomeration on the fly.

You can plot prevalence also by just using the SE itself. altExp(se,"Phylum") just retrieves se_phylum object from altExp slot of se.
plotRowData(se_phylum, "prevalence", colour_by = "Phylum")
and
plotRowData(altExp(se,"Phylum"), "prevalence", colour_by = "Phylum")
are the same.
-Tuomas

Yes, notation should be harmonized. se for SE and tse for TreeSE


Support for upload file size annotation

I'm using Ambassador as my api-gateway. As per default kubernetes ingress mechanism, it allows upload of files of max size 1 MB.
Currently there is no annotation or any such support to relax / customize this rule.
I'm looking for something like (this is what nginx provides)
ingress.kubernetes.io/proxy-body-size: 100m

I'm in the same boat and it would be great to have this feature

@nbkrause any update on this ?

I wonder how things are going.

Hi there. @nbkrause is there an update on this? This is a feature we would like to see.

Same for us. We are using ambassador to upload files of max size 10mb. Is it somehow possible to configure it somewhere globally (for the moment until a service annotation might be in place)?

So, Ambassador team didn't take up the feature request. That's sad indeed.
However, good news is that, there is an alternate way around.
In ambassador apiversion v1 they have allowed overriding some of the envoy properties (which are not yet implemented as ambassador annotations).
Thus, this problem can be solved by adding the following in mapping :
envoy_override:
per_connection_buffer_limit_bytes:
The mapping would hence look like this (I have allowed 32 mb):
annotations:     getambassador.io/config: |       ---       apiVersion: ambassador/v1       kind:  Mapping       name:  my-service-mapping-v1.0       prefix: /my-service/       rewrite: /my-service/       service: my-service       cors:         origins: "*"         methods: POST, GET, OPTIONS, PUT, DELETE         headers: "*"         exposed_headers: X-Custom-Header, Content-Length, Content-Range         max_age: "86400"       timeout_ms: 30000       envoy_override:         per_connection_buffer_limit_bytes: 33559432
Hope it help!

Is this
envoy_override:
    per_connection_buffer_limit_bytes:

still supported in the latest version of Mapping i.e. getambassador.io/v3alpha1?
If so, will it come under spec?


BrowserViewportService should implement IDisposable

Bug type
Component
Component name
BrowserViewportService
What happened?
Related #3741
When using new blazor web template, we use app.UseExceptionHandler("/Error", createScopeForErrors: true);.
When a new service scope is created, the old ones are disposed by framework, which results:

System.InvalidOperationException: 'MudBlazor.BrowserViewportService' type only implements IAsyncDisposable. Use DisposeAsync to dispose the container.
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.Dispose()
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.HandleException(HttpContext context, ExceptionDispatchInfo edi)

I did not investigate too much, maybe the dispose process is different between this and circuit close? I did not notice exception for the other scenarios.
Expected behavior
Implement IDisposable for BrowserViewportService.
Reproduction link
https://github.com/MudBlazor/MudBlazor/issues/3741
Reproduction steps

Create a new project of Blazor Web with default template.
Throw exception in OnInitialized() of Home page
Check console

Relevant log output
No response
Version (bug)
Latest
Version (working)
No response
What browsers are you seeing the problem on?
Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This happens regardless of Blazor Server, as it also happens during Blazor SSR (without SignalR).
Using the error handler, specifically, seems to dispose the previous ServiceProvider, because it needs to re-execute the pipeline for another URL. This explains why the framework needs to dispose of and recreate the ServiceProvider scope. It's quite hard to work around the issue as well, because you need to implement a fake on the server for yourself:
internal sealed class MudFakeServerService : IBrowserViewportService, IBreakpointService, IPopoverService, IMudPopoverService, IDisposable
{
    // implement all interface members as noop
}

// later on:
builder.Services.AddSingleton<IBrowserViewportService, MudFakeServerService>();
builder.Services.AddSingleton<IBreakpointService, MudFakeServerService>();
builder.Services.AddSingleton<IPopoverService, MudFakeServerService>();
builder.Services.AddSingleton<IMudPopoverService, MudFakeServerService>();

Yes, you need to implement it with all of the services listed above, because even though the BrowserViewportService throws the first-time, the others follow in suit.
The fix would be quite simple on the framework's side I believe, because all IAsyncDisposable implementations I came across are either sync already or do fire-and-forget async, although I haven't investigated thoroughly.
I believe @ScarletKuro would be able to elaborate. I believe this would be an easily fixable issue.

Still not resolved?

It appears to be a bug in the Microsoft code to me. Why would it only call Dispose to dispose the container?
I went to aspnetcore repository to check the ExceptionHandlerMiddlewareImpl implementation and was about to fill a bug report when I discovered that an fix was merged one week ago (https://github.com/dotnet/aspnetcore/pull/52687). However, it seems like this fix will only be shipped in .NET 9 =/
I'm aware of the recommendation provided here (https://learn.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-disposeasync), but there are scenarios where a class implementing IAsyncDisposable cannot implement IDisposable. This is our cases and they are totally valid and should not cause any problems.
The problem is that WASM doesn't support GetAwaiter().GetResult() (which would immediately deadlock). So I'm not really sure how to solve it, do we just use fire and forget or create an empty Dispose method? I find this as workarounds and they can create it's own problems.
It's worth mentioning that Microsoft also has classes that only implement IAsyncDisposable, and there are a lot of cases when it does implement both a simple GetAwaiter().GetResult() is used in the Dispose and when it doesn't it just lucky to have sync and async versions of API.

I see, I didn't investigate why it wasn't disposing of IAsyncDisposable services correctly.
I think it is safe to assume though that services that don't await anything in DisposeAsync can safely be implemented by
void IDisposable Dispose() => DisposeAsync();

This at least merits a comment in source, however.
For others that do, like PopoverService, it's more problematic. In my case specifically, this happened during an error was trying to re-execute the pipeline, so there "shouldn't" be any async work happening because of JS interop, as the browser wasn't even available (server was still prerendering). Further, this happens during SSR as well, where there is no JS interop to speak of whatsoever. There might be other async work theoretically that is not JS interop, but I'm not sure there is in MudBlazor's case.
I haven't really thought it all the way through, but maybe it would be worth considering having different service implementations for server side or client side for where it makes sense? In my case specifically, which won't be a match for everyone, the server side components should simply be noop, or at least, non-interactive, because I don't use Blazor Server in the app that produced this error. It might actually be a different issue to tackle that, but I believe it's worth considering now how you plan to integrate this along the way. I think in .NET 9 there will be a way to check the current render mode from code, which can theoretically solve a few issues, but I'm not sure work even started on that already.

Can someone actually post a minimalistic reproduction?

Reproduction steps
1. Create a new project of Blazor Web with default template.
2. Throw exception in `OnInitialized()` of Home page
3. Check console

I tied to include this steps with the app.UseExceptionHandler("/Error", createScopeForErrors: true) line in the debug mode, but I do not see the mention exception:

type only implements IAsyncDisposable. Use DisposeAsync to dispose the container.

Not in browser console, not in the service console, not in error page. I only see the exception trace that was thrown in OnInitialized.
I also tried release mode and ASPNETCORE_ENVIRONMENT on production, but no.
What I'm doing wrongly?
I just want to send this to Microsoft so they would port the fix.

I would, but I don't have access to a dev box for quite a few days, at least. You wouldn't see this happening in the browser, it only pertains to the server's service provider. From memory, all I can say is, make sure you try to use some of the affected MudBlazor services (directly or indirectly) in both the page that throws AND the Error page as well (might be both or just one or the other that causes the issue).

make sure you try to use some of the affected MudBlazor services (directly or indirectly) in both the page that throws AND the Error page as well (might be both or just one or the other that causes the issue).

I created a clean Server Side WebApp application, without MudBlazor.
Created a type that implements IAsyncDisposable only and added it as scoped to the DI.
Injected it in Home page, and throw error in OnInitialized. I see that IAsyncDisposable is called, and the error page is shown, but the error IAsyncDisposable is nowhere to seen.

That sounds suspiciously close to the underlying bug being fixed and backported to .NET 8. Someone will have to confirm if and how they're able to repro at this point.

That sounds suspiciously close to the underlying bug being fixed and backported to .NET 8. Someone will have to confirm if and how they're able to repro at this point.

I thought so too, but when navigating to ExceptionHandlerMiddleware and then ExceptionHandlerMiddlewareImpl I see the old code, at least this is what SourceLink is telling me.

Hi, I’m closing this issue since net9 will release in November this year, which includes a fix for the exception middleware. We will not implement IDisposable in our services According to Microsoft’s documentation, implementing IDisposable is only required when disposal is handled by the customer or when a class contains instances of both implementations. In our case, neither of these conditions applies, as disposal is managed by DI  and only involves asynchronous resources.


don't wrap first column (date/time) of log viewer

the date/time column of the log viewer wraps when viewing logs with
very long lines (for example when viewing the acme client log)
this adds white-space: nowrap to the first column

it would be better to directly inject the style into the required column. this PR is missing the SCSS anyway.

Not opposed to this but I'd like to point out that this will further diminish the readability on mobile devices in portrait mode.

sorry, I didn't see the scss part.
styling the first column this way uses fewer bytes than injecting the style into each first cell of each row - but it's gzipped anyway, so I think it wouldn't matter.
on my tests firefox android ignores the nobr in portrait mode.

except this will put the burden on all other theme maintainers to carry the fix too.

@fichtner you are right - doing it in the first cell is more manageable

okay, minimal width mode disables text-nowrap so we're good here :)


Support Japanese language

I am using this plugin, but it does not support Japanese. Can this feature be provided in the future?

Add Japanese translation


export_test, export_cyclic_test and generic_creation_test all new failures

As of r13478 ("Added support for exports and re-exports."), export_test, export_cyclic_test, and generic_creation_test all started failing. We need to investigate and fix this.

This can be closed. These tests are no longer failing.


Anchor rename issue in BC 14 release

Hello,
We are experiencing some issues with previously used anchor names from version 13 that now are renamed in version 14. One example is Item List repeater that had Name: <Control1> Caption: Item  but in version 14 the Name now has been changed to Control1 without <> which is giving us following error when compiling the app:
##... Item List Ext.al(7,17): error AL0270: The control 'Item' is not found in the target"

Were those control renames on purpose?
Should we update our apps to use new anchor names?
Is there a list of pages that have such anchor renames?

Thanks

Hi @JayDashti ! As you probably know, most controls in C/AL do not have the Name property set. In AL, everything must have a name as we switched from ID based to Name based. When generating symbols from the C/AL application or converting the C/AL application to AL, we used an algorithm to generate assign names to controls that did not have the Name property set.
What we discovered while converting the base application to AL was that this algorithm was generating the same name for actions and controls on the same page and this could lead to issues when using the page from test code (as a TestPage).
We had to change the naming algorithm to prevent duplicates and this meant that some controls have a different name in the 14.
You should update your apps to use the new anchor names.
Unfortunately, there is no list of pages, but the compiler will error out if you are referencing an invalid name.

I am closing this issue because it appears that it has been resolved. Please open a new issue if you believe this has not been resolved and reference the current issue.


Scrollable - stop propagation on click thumb

The issue is in our DropDown, it has Poppable and Scrollable inside. The behavior we have is on clicking on Poppable it closes the component, so if we need to keep it opened we use stopPropagation for example list of checkboxes, regarding Scrollable it works well if to use mouse wheel, but on dragging Thumb by mouse button it makes click inside of Poppable and closes the component.

This makes sense, since it's similar to how the native scrollbar would behave. Let's add this to the horizontal scrollbar as well.

:tada: This PR is included in version 1.5.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Cognito to IdentityProviderTypeType

the IdentityProviderTypeType class is missing an entry for Cognito
Description
Entries exist for Facebook, Google, etc, but not Cognito which is a supported Identity Provider Type.
Motivation and Context
I like using the constants instead of strings, but I can't because they are missing for Cognito

Testing
I ran the application and it created a UserPoolClient with Cognito enabled.
Screenshots (if appropriate)
Types of changes

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

Checklist

[*] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[*] I have read the README document
[ ] I have added tests to cover my changes
[*] All new and existing tests passed

License

[*] I confirm that this pull request can be released under the Apache 2 license

done!

This change is in the generated code for Cognito Identity Provider. I'm not a Cognito expert but if COGNITO is a valid value then we need to get the service to change their model to include that as a valid value. For background purposes here is the service model the Cognito vends the to SDK that we generate from. You can see that is missing the COGNITO enum value. https://github.com/aws/aws-sdk-net/blob/master/generator/ServiceModels/cognito-idp/cognito-idp-2016-04-18.api.json#L3809
Could you open an issue in the Cognito Forums to let them know this missing enum value. Hearing directly from users helps prioritize service teams task list.
https://forums.aws.amazon.com/forum.jspa?forumID=173


Correctly validate the response status for non-HTTP fetch requests (PR 8768 follow-up)

It seems that the status check, for non-HTTP loads, has been inverted which causes the default viewer to refuse to open local PDF files. Follow-up to PR #8768.
STR:

Make sure that fetch support is enabled in the browser. In Firefox Nightly, set dom.streams.enabled = true and javascript.options.streams = true in about:config. Edit: Just to clarify, please note that the issue is reproducible in Google Chrome too.
Open https://mozilla.github.io/pdf.js/web/viewer.html.
Click on the "Open file" button, and open a new PDF file.

ER:
A new PDF file should open in the viewer.
AR:
The PDF file fails to open, with an error message of the following format:
Message: Unexpected server response (200) while retrieving PDF "blob:https://mozilla.github.io/a4fc455f-bc05-45b5-b6aa-2ecff3cb45ce".
Edit: Fixes #8870.

/botio-linux preview

/botio test

Let's remove entire if(!isHttp) statement.

Fixed now, thanks!

Not sure if fetch() for file: protocol is returning 0 for success.

According to https://fetch.spec.whatwg.org/#scheme-fetch, it would seem that file:// isn't even in the specification.

/botio-linux preview

/botio-linux test

Thank you for the patch.

According to https://fetch.spec.whatwg.org/#scheme-fetch, it would seem that file:// support isn't even properly defined in the specification.

file: protocol is not supported by the native fetch implementation and always throws TypeError, see https://github.com/github/fetch/issues/186 .


Dropped Python 2 shims

Coverage decreased (-0.009%) to 94.237% when pulling e5848999ea9009571e8683f3108e49833efa099d on auvipy:py2 into 4fd315234a20ecedae4a9151fa27d8770b54c2ad on justquick:master.


sdk-nrf commit ID needs to be updated as the reference devices require the latest TREL updates

Could we obtain the latest OpenThread commit for the sdk-nrf ? The current codebase appears to be at least four months old. Given the substantial updates on the TREL side in OT repo, especially with its high priority for Thread 1.3.1 launch, the harness reference devices require this update.
@canisLupus1313 Is this something you can help us with?

@karthick-grl  please check #70

Thanks for quick turn around @canisLupus1313 . Will try to make a build on our side for 1.3 reference.


Generated tflm-tree is not sufficient

First, I like to discuss my way of using TFLM and make sure I'm following the correct path.
Then, I will describe the problem that shows up using this approach.
Goal
To use TFLM in an arbitrary platform for a specific microcontroller. For example, let's say I have an ARM Cortex-M4 (the NUCLEO-L4R5ZI board) microcontroller that I want to program using STM32CubeIDE, PlatformIO, or any other programming platform.
How
By some investigation, I've found tensorflow/lite/micro/tools/make to be the main Makefile of the project, having the following as some of its important parameters:

TARGET: defaults to the HOST_OS. A list of available targets can be found by following this pattern: tensorflow/lite/micro/tools/make/targets/<TARGET>_makefile.inc
TARGET_ARCH: defaults to HOST_ARCH. It seems to be important when having some targets like cortex_m_generic and doesn't matter with some others like bluepill. tensorflow\lite\micro\tools\make\targets\cortex_m_generic_makefile.inc lists available architectures for cortex_m_generic
OPTIMIZED_KERNEL_DIR: it is empty by default. cmsis_nn is a possible value (that should probably be working with all Cortex-M microcontrollers). Other values can be found by following this pattern: tensorflow/lite/micro/kernels/<OPTIMIZED_KERNEL_DIR>
BUILD_TYPE: defaults to default. It can be one of {default, debug, release, release_with_logs, no_tf_lite_static_memory}. For more info check this
TOOLCHAIN: defaults to gcc. It can be one of {gcc, armclang}. A specific version of the respective compiler will be downloaded for example in tensorflow/lite/micro/tools/make/downloads/gcc_embedded.
Some other parameters: OPTIMIZED_KERNEL_DIR_PREFIX, CO_PROCESSOR, EXTERNAL_DIR, DOWNLOADS_DIR, KERNEL_OPTIMIZATION_LEVEL, THIRD_PARTY_KERNEL_OPTIMIZATION_LEVEL

Still, to have a bag of C++ files that can be compiled and used in our C++ project, we need to use tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py as described in this document. In short, this Python script will use the abovementioned Makefile to generate a file tree for our specific hardware. Then we can copy this generated folder to our C++ project (created by STM32CubeIDE, PIO, or any other platform), add TFLM-related code in our main function (a basic example can be seen in the generated hello_world example), and compile it along with our other parts of code.
Question 1
Am I doing it right? Is there a better and simpler way of using TFLM? Is TFLM supposed to be used this way?
Question 2
What should be the TARGET, TARGET_ARCH, etc., when I want to use this project for other hardware like:

ESP32 which should belong to the xtensa family, but I don't think any available TARGET_ARCH supports ESP32, and also it seems like some other parameters (e.g., XTENSA_BASE) should be defined that I'm not aware of how to do so.
Renesas RX family. It seems like it doesn't fit in any available TARGET categories (maybe arc_custom?). Generating the tflm-tree by leaving the TARGET parameter empty (the command was executed on Google Colab, so I guess it ended up being riscv32_generic) and using the resulting tflm-tree in my project, surprisingly I was able to compile it and have TFLM on my Renesas board, but I'm pretty sure it shouldn't be the correct way. So, what should I do instead?

CMSIS-NN is designed for ARM Cortex-M microcontrollers and not Renesas RX. Still, Renesas eAI translator has an option for using CMSIS-NN. This made me think maybe it's possible to have CMSIS-NN with TFLM on the Renesas RX?

Question/Problem 3
The process of putting the generated TFLM library in our existing C++ project looks more problematic than it should be. For example:

Right now, array.h and array.cc are missing from the generated files. I should manually download them from tensorflow/lite/array.h and tensorflow/lite/array.cc and add them to the .../TFLM_lib/tensorflow/lite directory. I think this item is an independent problem, meaning that even if there exists a much simpler way of using TFLM and what I'm doing right now is wrong, this problem should still be solved.
Including the tensorflow's parent directory (.../TFLM_lib based on the previous item's example) is fine, but including third_party and even its individual elements is not enough. For example, I needed to include all the following for my project to work:.../TFLM_lib
.../TFLM_lib/third_party
.../TFLM_lib/third_party/flatbuffers/include
.../TFLM_lib/third_party/gemmlowp
.../TFLM_lib/third_party/gemmlowp/fixedpoint
.../TFLM_lib/third_party/gemmlowp/internal
.../TFLM_lib/third_party/kissfft
.../TFLM_lib/third_party/kissfft/tools
.../TFLM_lib/third_party/ruy

Also, add the following if we are using CMSIS_NN:.../TFLM_lib/third_party/cmsis
.../TFLM_lib/third_party/cmsis_nn
.../TFLM_lib/third_party/cmsis_nn/Include

(Based on our target, we might need to include more paths)
Also, we might need to define CMSIS_NN if we are using it.

Is there any solution to this hassle? At least some documentation?

Have a look at https://github.com/tensorflow/tflite-micro/issues/2444. In essence compile a static tflite micro lib and link to your application.  Some documentation:
https://github.com/tensorflow/tflite-micro/blob/main/tensorflow/lite/micro/cortex_m_generic/README.md
https://github.com/tensorflow/tflite-micro/blob/main/tensorflow/lite/micro/kernels/cmsis_nn/README.md

Thank you @mansnils for answering.
I've looked at the links, but my questions remain. Mainly, my questions are:

I want to create source files, not a static library. How can I do that?
Probably the answer is create_tflm_tree.py. If so, why this process is incomplete? It requires adding tensorflow/lite/array.h and tensorflow/lite/array.cc manually, also the include paths look a bit more complicated than what they should be (which is fine).

What if I want to have default implementations of kernels (for example, when I have a specific MCU that is not included in TFLM's supported MCUs - Let's say Renesas RX)? What should be the values of TARGET and TARGET_ARCH?

I want to create source files, not a static library. How can I do that?
Probably the answer is create_tflm_tree.py. If so, why this process is incomplete? It requires adding tensorflow/lite/array.h and tensorflow/lite/array.cc manually, also the include paths look a bit more complicated than what they should be (which is fine).

array.h and array.cc are not actually needed by TFLM. The create_tflm_tree script invokes the TFLM make build to determine which sources are needed, and since those aren't, they are not copied. If you are running into compilation issues after that, it is likely that you're missing a TF_LITE_STATIC_MEMORY define.

What if I want to have default implementations of kernels (for example, when I have a specific MCU that is not included in TFLM's supported MCUs - Let's say Renesas RX)? What should be the values of TARGET and TARGET_ARCH?

Omit the OPTIMIZED_KERNEL_DIR make flag and you'll get the default implementation of kernels.


WIP Auto detect AVD

Added a starter branch for auto detecting AVD.
The problem is that we need a WidgetsBinding before we can detect if we are running in an AVD.
This code currently causes problems when the client performs a hot restart because there is more than one widgetsBinding already initialized.
The PR is only for reference or for someone else to fix later on.
closes #253

This code currently causes problems when the client performs a hot restart because there is more than one widgetsBinding already initialized.

Not sure about that. Seems that, after client hot restart, at some time in its initialization, it will itself call widgetbinding initialization. So should have no problem.
What is the error?


App Install Location

The internal memory of my device is quite small, this PR should allow users to easily move the app to the microSD.
"To allow the system to install your application on the external storage, modify your manifest file to include the android:installLocation attribute in the element, with a value of either "preferExternal" or "auto"." (source: https://developer.android.com/guide/topics/data/install-location.html)
Thank you very much for your awesome app :)

                                                                                thank you for your interest in the project :)I am now working with other developers on the project. The most updated repo is at SecrecySupportTeam/Secrecy. You will find a lot of updates and things we have been working on there.You can join us there and rebate the changes to a new pull request thereHappy coding!


Stub out tzdb support for Windows and POSIX tz string

Builds on #99.
This PR adds resolving the POSIX tz string and should allow handling time zones on Windows via jiff_tzdb as a source, which should make the stub overall somewhat stable overall until a different solution can be put into place.

Very true. I'll update the docs now.

I'm not sure im understanding the slim format difference, the resulting Tzif result looks to be the same size (552 bytes) whichever format is used.

The "slim" vs. "fat" format is laid out by zic. Basically, all OSs are compiled using the "fat" format, but if someone does a custom compilation, then a smaller range can be set for which the transition times are computed.
The zic docs can be found here. Primarily, zic's bloat and range flags.


increase default expiry for signed url

Increase expiry for signed url to recommended minimum from aws s3

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-676
An OCP cluster where you are logged in as cluster admin is required.
To use this image run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/676/head
git checkout -b pullrequest 025289faa4d77863b3ca15be26e85dd0d82faa6c
oc new-project opendatahub
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-676"

More instructions here on how to deploy and test a Data Science Pipelines Application.

A presigned URL remains valid for the period of time specified when the URL is generated. If you create a presigned URL with the Amazon S3 console, the expiration time can be set between 1 minute and 12 hours.

ref: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html
and we've seen it be unreliable below 60 seconds. Suspect on-prem kubernetes node clocks not matching up with AWS clocks or something like that.
/lgtm
/approve

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-676


prometheus: bump aws_limits_s3_buckets to 600 for prod & prod-lon

https://www.pivotaltracker.com/story/show/180738224
What
Unless aws are lying to me it should now be 600
How to review
Look at it, be happy.

🚨⚠ Please do not merge this pull request via the GitHub UI ⚠🚨

Yes


change the kafka storage type from ephemeral to persistent-claim

Signed-off-by: myan<EMAIL_ADDRESS>Fixed: https://github.com/stolostron/multicluster-global-hub/issues/367
References:

https://github.com/strimzi/strimzi-kafka-operator/blob/main/packaging/examples/kafka/kafka-persistent.yaml
https://strimzi.io/blog/2018/06/11/deploying-kafka-on-kubernetes-with-local-storage-using-strimzi/
https://b-nova.com/en/home/content/heres-how-you-can-setup-kafka-with-strimzi-on-kubernetes-in-only-five-minutes

/test test-e2e


The accuracy of the AD is only 0.81 and it has not changed the project. Is it because MSPCA is not used?

In the default script we artificially corrupt the data and then apply rpca to fix that. If you want to try the original data, set rnn.rpca=False and rnn.spikes=0.
That said, some little random variations can still arise, due to different library versions, different GPU, etc.

Thank you for your answer. I successfully reproduced your thesis, but I hope to make full use of my own data set for practice. I would like to ask you how to perform each individual data prediction process and generate .npz individual data. My current dataset is the 5-minute resting EEG on the left, and the number of channels is 19

I have this error when I want to load data
Cannot load file containing pickled data when allow_pickle=False
I set the  allow_pickle=True but did not work
Failed to interpret file 'GAU/EEG/S01_AD.npz' as a pickle
how can I fix this error?


Update Changelog

Codecov Report

Merging #267 (870170c) into master (67c88b0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #267   +/-   ##
=======================================
  Coverage   91.39%   91.39%
=======================================
  Files          25       25
  Lines        1267     1267
  Branches      141      141
=======================================
  Hits         1158     1158
  Misses         84       84
  Partials       25       25


index name may be double escaped

In Elasticsearch, escaped characters may be contains in index name.
ref: https://www.elastic.co/guide/en/elasticsearch/reference/current/date-math-index-names.html
# PUT /<my-index-{now/d}>
PUT /%3Cmy-index-%7Bnow%2Fd%7D%3E

Notice that we have to escape the / here.
In Golang, paths are usually escaped automatically. However, / is not an escaped character.
If we specify an escaped index name, it will be double escaped.
So, the library is currently not possible to use this index.

Solution:
https://github.com/soranoba/go-elasticsearch/compare/master..fix/master/double-escape-path
The code will solve the problem, but what was previously escaped will no longer be escaped.
It may be a breaking change.
Is there a better solution?

Related issues: https://github.com/elastic/go-elasticsearch/issues/52

Hello, sorry for the delay here. Correct, there's an inconsistency with regard to the / character, due to the behaviour of URL escaping in Go. As I wrote in the related issue comment, and as you mention, this is tricky to solve without breaking backwards compatibility. I imagine this is something worth looking before releasing the 8.0 version of the package.

Thank you for your reply.
I hope that it fixes in 8.0.

Need something like:
diff --git a/typedapi/core/index/index.go b/typedapi/core/index/index.go
index d333ff570..7614c1352 100644
--- a/typedapi/core/index/index.go
+++ b/typedapi/core/index/index.go
@@ -183,7 +183,8 @@ func (r *Index) HttpRequest(ctx context.Context) (*http.Request, error) {
 		if instrument, ok := r.instrument.(elastictransport.Instrumentation); ok {
 			instrument.RecordPathPart(ctx, "id", r.id)
 		}
-		path.WriteString(r.id)
+		r.path.Path = path.String() + r.id
+		path.WriteString(url.PathEscape(r.id))

 		method = http.MethodPut
 	case r.paramSet == indexMask:
@@ -199,10 +200,10 @@ func (r *Index) HttpRequest(ctx context.Context) (*http.Request, error) {
 		method = http.MethodPost
 	}

-	r.path.Path = path.String()
+	r.path.RawPath = path.String()
 	r.path.RawQuery = r.values.Encode()

-	if r.path.Path == "" {
+	if r.path.RawPath == "" {
 		return nil, ErrBuildPath
 	}

or single-document index to work, at least.  I expect single-document get to have a similar issue.


Convert main.parameters.json to main.bicepparam

This https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/infra/main.parameters.json
Can be converted to biccepparam file.

What's the benefit?

It is the new recommend approach and less verbose.

@dantelmomsft another one for review, please


Improve Clifford Synthesis to make it more efficient

Summary
Co-autored by @gadial
Improve the code in clifford_decomposition.py to make the Clifford synthesis more efficient.
Details and comments

1-qubit decomposition - call _decompose_clifford_1q method before clifford_name

2-qubit decomposition - replace by a different code based on the Clifford group structure - will be done in a separate PR

greedy decomposition for n>=4 qubits - update the code using Pauli.evolve()

@chriseclectic - I think this can be merged and I will open another PR to improve 2-qubit Cliffords synthesis.


[core] Fix running mocha related scripts on Windows locally

I added documentation for the purpose of helping developers run unit tests if they are on a windows machine.

Hey thanks for contributing @ChristopherJamesL ~ I'm not really a windows user, just gotta wait for another reviewer to have a look

@mj12albert Can you check if the changes work on Max OS X as well?
Thanks @ZeeshanTamboli they do ~
I noticed there's also nx_test_regressions_run and nx_test_regressions_pigment_css_run that still have single quotes

I noticed there's also nx_test_regressions_run and nx_test_regressions_pigment_css_run that still have single quotes

@mj12albert They do work in single quotes. The glob pattern of asterisks (*) is recognized.


[question] is there a way also to force accept any certificate

relates to this one:
https://github.com/xamarin/xamarin-android/issues/4688#issuecomment-931628302
the workarounds seem not to work.

I'm not sure I understand your question.
Could you please provide more details?

Is there any parallel with SecureHttpClientHandler to:
                var httpClientHandler =
                    new HttpClientHandler();
                    //new SecureHttpClientHandler(null) { UseProxy = false };
                httpClientHandler.ClientCertificateOptions = ClientCertificateOption.Manual;
                httpClientHandler.ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator;

Sorry for the late answer...
I don't want to implement a way to accept any certificate, since the purpose of this library is to increase the security.
You should use the default HttpClientHandler if you want to do that.

I get your point, thanks.


Remove Jetty XML dependency.

The code is now there, but via another change than this pull request.


fix: escape reserved words

This checks against a list of reserved words for every language and appends a trailing underscore to escape an conflicting variable names.

This is a useful addition!
Thank you so much!


feat(launcher): explicitly set font-render-hinting to medium

In response to #2410.
Snapshot of properly aligned text:

Looking for feedback on snapshot test which

is probably not in the right place within the testing suite
is failing for me on Linux, with the snapshot being different from the expectation, but not visibly so.

@cfellin1 @JoelEinbinder I looked more into this. We need to fix chromium to make headful respect the --font-render-hinting flag. Otherwise there's no guarantee font hinting will be the same between headful and headless.

Closing this until upstream is fixed.


VS Code does not launch after update 1.29.1 when offline.

Issue Type: Bug

Disconnect internet.
Launch VS Code

VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.91GB (4.44GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Tracked in #7570 / electron/electron#6437
Btw on machine with older Windows version (1709) it is still possible to start VSC while offline.

Too many people faced with this issue on windows 10 (1809) and the only thing that they do is close issue!
obviously there is two way: fall backwards or migrating to Mac/Linux 👎🏻👎🏻👎🏻

From the main issue(s) tags it appears to be fixed in Electron 3; I've asked for estimate when it will come into stable branch in another dupe but got no response.
Overall it seems strange: bug in Electron core that exhibits itself only on certain Windows versions, or other yet undiscovered circumstances.  Strange that the main Electron bug is still "open" ATM.

Q1 2019.

How can you close the issue if it is still unsolved? Code still does not run without Internet on Win10-1809.

vs code opens only when it is connected to internet, if i try to open offline it is not opening.
And even when i try to troubleshoot the app from settings , vs code opens only if internet is connected when i click "Test the program" , in offline after i click "Test the program" the app doesnt open
my windows 10 os v:1809
vs code v:1.25
please help me,
thank you..


maintenance.enabled doesn't seem to do anything

Ghost-CLI version: 1.8.1
Ghost Version (at /var/www/ghost): 1.24.6
Node: v6.14.3
Database client: mysql

ghost config maintenance.enabled true
Refresh blog, note nothing happened
ghost restart
Refresh blog, note nothing happened

Am I missing something here? Configuration docs indicate this key still exists. https://docs.ghost.org/docs/config

Hey!
Good catch. The maintenance variable is configured in our overrides file, it always falls back to false. Funny, it's there for exactly 2 years now 😜It should be configured in defaults.json.
Fix is welcome 🙏🏽

The maintenance variable is configured in our overrides file

Isn't this because the feature was deprecated?

@ErisDS I wasn't able to find a note about it. In LTS we were using the maintenance mode to force db migrations in the background, because the logic was part of Ghost core. We had a clear use case.
But as @riverar said, it's still in our docs. Either we made a mistake in the config files or we forgot to remove it from our docs.
@riverar What was the reason you wanted to enable the maintenance mode for your blog frontend/site? We are always interested in use cases :)

I wanted to take the site down while I iterated on my theme, without incurring a search engine cache hit. But it's not clear if it applied to /admin, so probably not a valid use case.

But it's not clear if it applied to /admin

It does currently apply to the admin section.

@riverar You probably want to make your blog private?
https://blog.ghost.org/private-blogs/

That would get cached by search engines, and potentially impact search results, when my intention was to be temporary. 😢 (I did end up using this feature.)

Would you guys mind if I have a go at this?

I have updated the docs for now.
If somebody has an use case for which he needs to be able to configure the maintenance mode, please raise a topic in our forum.
Closing for now.


Feature snapdragon ekf2

This brings ekf2 support for Snapdragon.

[x] Compiling
[x] Running
[x] Raise rates to 1kHz
[ ] Test flown

@julianoes Could you organise with @ChristophTobler and @tumbili regarding test flights?

@LorenzMeier I'm hoping to test fly this tomorrow myself.