Minor rearrangement of README.md

Moved the instructions on listing hooks earlier in the document, and gave it a separate heading.

ping

ping

ping

I like this idea, since it's not immediately clear how to get the list. Thanks for the PR


Interesting work

Hi Alexandros,
This work is really intesting and thoght-provoking. When I first see the title in arXiv, I wondered if this is just a 1x1 conv layer. Now I know that you have trained 9 sample-specific color transform parameters, and put them into the 1x1 conv layer.
We have neural networks that can build great non-linear systems, however, with each layers' parameters are trained linearly. Now I would like to re-consider the structure of all NN models.
Thanks for sharing your work!

However, I think that you have constructed such a complex network for trianing the color_transformer_layer,  but add no other layers in the control group. This is not fair for comparison. I suggest to add a 3*3 conv layer and a relu layer in front of the first conv layer to make your work more persuasive.

I know that in the first layer, their is some relevance in the color space. However, I think that the relevance in the spatial space is more severe. Neural network model is really not good at controlling these relevance. So I guess training more bigger filters, such as 3x3 or 5x5, may work better.

Hi Feng! Thank you for the interest in this work. I am glad that you gave it a spin.
As you pointed out this proposed layer is more of an idea that seems like a good start for further development . It needs further polishing and review. You might want to compare it against other orthogonal transformation procedures (e.g.PCA, PCA whitening and ZCA whitening algorithms). Also the layer doesn't preserve the orthogonality.
In regards to the comparison, yes you were right. I was planning to remove the conv net layers from the color space transformation sampler. I updated the code. Thanks for pointing out! The accuracy is still in upper 60s.
Lastly, can you elaborate on your last comment. What do you mean by relevance?

I am sorry that English is not my first language, so there may be some error in my expression.
What the relevance (may correlation be better? I got this word from translate software) I said is about the correlation in different dimensions. Algorithms such as PCA can eliminate the correlation. The spatial correlation problem is more severe than that in the color space. But there is no good solution for eliminating the spatial correlation in an image.
Moreover, your algorithm can be extended to any layer's paramters. In the traditional CNN, the paramters are independent with the input. I think we can have a try on adding all the parameters to the output of transformation network.
There are lots of details. Note that the early layers get more deeper gradients form the loss layer, and the latter layers get more shadow gradients, I think the best way is to make all paramters to have similar depth w.r.t the loss layer. I am not good at english, I will draw a picture to explain it.

This picture is taken from tensorflow. The thin red line denotes the connection from the input to the parameters. I think we can add these connections and see what happens.


Track names turn into ??? marks after load

After dragging 100+ mp3s into the play list, I can see the song names load correctly, but after the load is complete, 95% of the songs lose their name and it becomes ???.

Could you share one of the mp3s that results in a ???. I'd be curious to see if I can reproduce this issue myself.

This should be resolved now via https://github.com/captbaritone/winamp2-js/commit/4c555a4887b82cfabaa90fbbc214e90b674b85a9 If you could try again I'd appreciate it. If the issue persists, let me know and we can re-open this issue. Thanks for reporting!


socket.io.d.ts: Declare Socket.conn as any

SocketIO.Socket.conn is an EngineIO.Socket, not a SocketIO.Socket so use any rather declaring as the wrong type.

@elisee thanks mate!

note
https://github.com/Automattic/socket.io/blob/97c6568f656573e5575101d9c6fba7cba623fc72/Readme.md#socketconnsocket


Replacing DHTMLX grids with DataTables

If we want to use DataTables' pagination/search/ordering then it's necessary to feed our tables with JSON through AJAX and implement a compatible server side processing controller.
We need:
[ ] Separate data and view by generating JSON as an output format
[ ] Rewrite pagination to work with offsets instead of page numbers
[ ] Change our models to generate datasets based on the specification
[ ] Change our controllers to react based on the specification
[ ] Write some tests
[ ] Feed DataTables with the JSON and enjoy the endless scrolling and other cool features
[ ] Use the separated data-view solution with angular where the JSON is available
Trello issue: https://trello.com/c/aD6sHQmf/40-5-replace-dhtmlx-grids-with-patternfly-tables

This task is too hard for just me, so I'm asking for help :sos:
@martinpovolny @himdel

@skateman : As I said previously I am ready to pair on this with you so that we do the basic functionality together and then you make all the fine touches. Let me finish a bit of work on the report charts and study the links you provided so that we are at the same page. Next week we would spend a day together working on this.
As for the point "Change our models to generate datasets based on the specification above" -- I would prefer not doing that. Rather I would use some pattern that would inject the needed behaviors into the models (dynamicaly extend e.g.) or use decorators or whateve else to keep the specific functionality needed for the presentation (presenting the data as json) separate from the models. That would much better match with our long-term goal of splitting the application and talking to the models only through the API.

Because we're using AJAX with RJS, sometimes it creates collisions. In the GTL/explorer context this line has to be changed to:
if request.xml_http_request? && params[:format] != 'json'

Then the controller will search for a JSON/jbuilder file between the views when the format is set to JSON.

Looking at your first quick hack the call sequence is:

explorer
set_active_element    (root)
get_node_info (root)
process_show_list  (here we actually deal with lists)
get_view
get_db_view

We would not add ifs, branches and exceptions to this path but instead we will create a new action in the controller. Let's say tabledata.
tabledata will only support request
return if request.xml_http_request? && params[:format] != 'json'
let's do this using rails routing in the final implementation
tabledata needs to parse from the request:

pagination info
sort criteria and direction

We need to write this from scratch as this is completely different to what we have now.

conditions (not needed for the simplest use cases)

tabledata need to figure out the model to use. That is done in the ugly case in get_node_info:

    model, title =  case x_active_tree.to_s
                      when "images_filter_tree"
                        ["ManageIQ::Providers::CloudManager::Template", "Images"]
                      when "images_tree"
                        ["ManageIQ::Providers::CloudManager::Template", "Images by Provider"]
                      when "instances_filter_tree"
                        ["ManageIQ::Providers::CloudManager::Vm", "Instances"]
                      when "instances_tree"
                        ["ManageIQ::Providers::CloudManager::Vm", "Instances by Provider"]
                      when "vandt_tree"
                        ["VmOrTemplate", "VMs & Templates"]
                      when "vms_instances_filter_tree"
                        ["Vm", "VMs & Instances"]
                      when "templates_images_filter_tree"
                        ["MiqTemplate", "Templates & Images"]
                      when "templates_filter_tree"
                        ["ManageIQ::Providers::InfraManager::Template", "Templates"]
                      when "vms_filter_tree"
                        ["ManageIQ::Providers::InfraManager::Vm", "VMs"]
                      else
                        [nil, nil]
                    end

So wee need to extract that into a separate method and call it from get_node_info and our table_data.
Then there's some filtering in get_node_info that we need to take a look at:
        if x_node == "root"
          # TODO: potential to move this into a model with a scope built into it
          options[:where_clause] =
            ["vms.type IN (?)", ManageIQ::Providers::InfraManager::Vm.subclasses.collect(&:name) + ManageIQ::Providers::InfraManager::Template.subclasses.collect(&:name)] if x_active_tree ==
          process_show_list(options)  # Get all VMs & Templates

And then the get_view is called where we will need to take the search logic eventually (probably from load_default_search and adv_search_build) but can skip for the 1st approach.
Then we go to get_db_view which just loads the MiqReport with the definition of the data that we are about to serve.
So let's create some module or class such as DataTables and put the logic there. tabledata will just call DataTables and we will write specs around DataTables w/o other interaction with controllers.


Documentation on how to encode and decode a molecule

Hi, thanks for providing your code, your work seems very promising!
However I couldn't find the documentation I was looking for. If I understand correctly, GraphMVP is able to input a molecular graph, encode it into a latent space, and decode this embedding into a molecular graph again. Could you provide the documentation on how to do both of these steps, from latent space and back?
Thank you!

Hi @htalibart,
Thank you for your interest in our work!
For the 2D->3D and 3D->2D generation, GraphMVP employs an approximate solution to learn the representation, i.e., variational representation reconstruction (VRR), and no decoding is required in VRR.
However, we do have a follow-up work called MoleculeSDE, which does these two encoding steps exactly. The website together with a demo can be found here. I'm still cleaning up the codes for MoleculeSDE, which should be available in one or two weeks.
Hope this answers your question.

Thank you for your answer!
I understand that the decoding is not required for the applications you're interested in, but I would be interested in working in this latent space, for instance if I encode a molecule and slightly modify the resulting embedding would it be possible to decode it and get another (valid) molecule?

Hi @htalibart,
Welcome to play around with the decoding in MoleculeSDE, which shall be available soon. (I'm pushing this)
Meanwhile, the one you mentioned is very interesting, and I personally call this as molecule editing or molecule conditional generation. I have done several works on this (e.g., GraphCG and MoleculeSTM), and the answer is positive: changing the latent does change the output decoded molecules. I'm quite positive about getting similar observations in MoleculeSDE.

Ok many thanks for your answer and best of luck for your submissions!

Hi @htalibart, the code for MoleculeSDE is released here. Feel free to check.

Hi @htalibart, the code for MoleculeSDE is released here. Feel free to check.

Many thanks for the follow-up, I will check!


Having a no much file error during the run test/build

Hi, when using the unity-action, I always receive this error
###########################
#    Edit Mode Results    #
###########################

cat: /github/workspace/artifacts/editmode-results.xml: No such file or directory
cat: /github/workspace/artifacts/editmode-results.xml: No such file or directory

###########################
#    Play Mode Results    #
###########################

cat: /github/workspace/artifacts/playmode-results.xml: No such file or directory
cat: /github/workspace/artifacts/playmode-results.xml: No such file or directory
##[error]The process '/usr/bin/docker' failed with exit code 1

Even with files created, I still get the message, Need help please thanks

That message simply means that your tests never ran.
You'll have to scroll up for the specific reason.
In case the reason is that it doesn't find any tests; Make sure you've followed Unity's official docs (or better youtube movies) about how to setup test assembly files.
Let me know if that worked. If not, make sure you provide some extra information about the specific reason as mentioned above.

@ItsAlexou Did you get any further with this?

It's done now


Highlight active posters

Consider how to make it clear which poster sessions are active at the moment (add a list to the Posters page, maybe? and/or to the Lobby page?)

I've added the posters to the lobby (specifically: for each track that has breakout rooms, it will show the breakout rooms organized by the track along with who is in them) - I think that this might be sufficient now?

Closing as the new UI has been developed after this issue was opened and this issue relates only to the old UI.


Filter - Not

In gitlab by @sfalquier on Apr 28, 2017, 11:09
negative filter by prefixing with "-"

In gitlab by @sylvaingaudan on Apr 28, 2017, 13:46
changed milestone to %4

In gitlab by @sylvaingaudan on Apr 28, 2017, 13:53
added ~1918909 label

In gitlab by @sylvaingaudan on Jul 12, 2017, 13:43
removed milestone

In gitlab by @sylvaingaudan on May 5, 2017, 11:10
added ~1918908 and removed ~1918909 labels

In gitlab by @sylvaingaudan on Aug 10, 2017, 08:30
removed ~2424200 label

In gitlab by @sylvaingaudan on Sep 11, 2017, 11:48
changed milestone to %13

In gitlab by @sfalquier on Sep 15, 2017, 11:00
removed milestone

In gitlab by @sylvaingaudan on Jan 2, 2018, 10:41
Not applicable anymore.

In gitlab by @sylvaingaudan on Jan 2, 2018, 10:41
closed


Support SSO login buttons

Would be nice to have an easy way to add SSO buttons to a pre-configured section.

+1

+1


enhance:sending email on meshmodel generator workflow failure

Notes for Reviewers
This PR fixes #7383
Signed commits

[ ] Yes, I signed my commits.

Hey @leecalcote to whom the need to be send


refactor: remove trailing whitespace from Markdown files

Hey @haneefmubarak this one is ready for review 👍

@abracchi-tw I think we've made several significant changes to docs and this PR conflicts with them now given the size of the number of files changed. Closing this ticket in favor of smaller tickets.


bump aik

Thanks! Don't worry too much about updating aik here, I have dependabot running every monday


(Suggested fix) pthread_local_storage_thread_deleted_callback is not conforming to the specification of pthread_key_create (IDFGH-4842)

Environment

All

Problem Description

We are building support for the Rust standard library on top of ESP-IDF.
During the implementation of the support for Rust threads, we were hit by a crash which - in our opinion - is caused by the implementation of  pthread_local_storage_thread_deleted_callback
The implementation is not really conforming to the specification as outlined here
The concrete sentence in the specification which is not currently implemented correctly is, to quite the above link: "the value of the key is set to NULL, and then the function pointed to is called with the previously associated value as its sole argument" (emphasis mine)

Expected Behavior
pthread_local_storage_thread_deleted_callback should first delete the key from the linked list and then call the destructor with the original value of the key. Thus, if the destructor recursively calls into the pthread library (which is allowed by the spec), it will see a consistent local storage
Actual Behavior
pthread_local_storage_thread_deleted_callback calls the destructor without removing the entry from the list. In our code, it results in memory corruption issue, as the Rust-provided destructor calls-back into the pthread code and sees inconsistent local storage.
Steps to reproduce
Not really yet simple steps to reproduce, besides running our Rust-on-ESP32 demo code.
See the "Rough Steps" section where this issue is described, as well as the fix from below.
Fix:
Here

Anybody? This is a bit of a blocker for enabling Rust STD support for ESP32 / ESP-IDF as demoed here.

@ivmarkov Sorry for not getting back to you sooner. Could you please submit your fix as a PR? It looks okay to me, if we don't find any test failures in CI we will merge it.
P.S. the demo looks really cool!

Thanks a lot - I'll prepare a PR for that.
(BTW - I just updated the demo with type-safe Rust wrappers for WiFi, Httpd and Ping so I hope the coolness factor has grown a bit. J)

Hi @ivmarkov,
I'm sorry, I picked this task up recently but somehow didn't see the lines with "Fix: Here" in the issue report (I literally thought "I wonder what they mean by 'Suggested fix', entirely my mistake for skim-reading). As a result, I've written a slightly different fix!
This fix is a little more complex as I've tried to also address the other missing behaviour for pthread_setspecific(): if a destructor function calls pthread_setspecific() to set a different key to a non-NULL value then the destructor should also be called for this key, but only after destructor functions have been called for the existing non-NULL values.
Patch is attached, if you have any comments or concerns before I submit it for merging then please let me know.
0001-pthread-Fix-behaviour-when-pthread-destructor-calls-.patch.txt

@projectgus - I don't mind at all having your fix applied instead. I've quickly skimmed through it and it does seem to contain a fix similar to mine - which is - remove the entry from the list before calling its destructor.
I also applied your patch and then re-built my little Rust playground with it - seems to work fine in that spawning and joining Rust threads does not crash the app.
Many thanks for your work and taking my little request seriously!
===
Out of pure curiosity - why are you guys maintaining your own pthread-over-freertos support and not using this one?

Hi @ivmarkov,
Good to hear, thanks for testing and confirming! This issue will be updated when it merges to master.

Out of pure curiosity - why are you guys maintaining your own pthread-over-freertos support and not using this one?

That's a very good question, I think one historical reason and one technical reason:

Historical: At the time this pthread support was implemented in ESP-IDF the "FreeRTOS Plus" features were licensed differently. Since 2018 (I think) this project is MIT licensed, so no longer a valid reason.
Technical: "Vanilla" FreeRTOS doesn't currently support SMP. However, this situation is currently changing as well. It's very conceivable that at a future time when FreeRTOS+POSIX supports the FreeRTOS SMP kernel, and ESP-IDF uses the FreeRTOS SMP kernel, we could switch over the implementation in ESP-IDF. I can't give any estimate of when this might be, though.


Apple M1 CPU not correctly recognized

Based on some user feedback it seems like the Apple M1 CPU is not correctly recognized by primesieve. The l2 cache sharing is reported as one CPU core which seems incorrect (I think should be 4). Also primesieve reports the cache sizes of the slow CPU cores instead of the high performance CPU cores.
This CPU detection code is in src\CpuInfo.cpp. Unfortunately the new Apple M1 CPU has different cache sizes for the slow and high performance CPU cores which makes it difficult to select a good default setting in primesieve. A simple solution that would perform reasonably well would be: iterate over all CPU cores and find the largest L1 cache size then use this as sieve size (use this scheme on macos only).

Another option would be to iterate over all CPU cores until we find one of the high performance cores. If we are lucky primesieve will correctly recognize the l2 cache sharing of the high-performance core.

The bug comes from the sysctl library that primesieve uses to retrieve CPU information on macOS. Below is the sysctl output of the new Apple M1 CPU.
> sysctl -a | grep -i cpu
kern.cpu_checkin_interval: 4000
hw.ncpu: 8
hw.activecpu: 8
hw.physicalcpu: 8
hw.physicalcpu_max: 8
hw.logicalcpu: 8
hw.logicalcpu_max: 8
hw.cputype: 16777228
hw.cpusubtype: 2
hw.cpu64bit_capable: 1
hw.cpufamily: 458787763
hw.cpusubfamily: 2
machdep.cpu.cores_per_package: 8
machdep.cpu.core_count: 8
machdep.cpu.logical_per_package: 8
machdep.cpu.thread_count: 8
machdep.cpu.brand_string: Apple processor

> sysctl -a | grep -i cache
kern.flush_cache_on_write: 0
kern.kernelcacheuuid: 35A645C8-D626-1906-0673-BEF751E6A7AA
kern.namecache_disabled: 0
vm.vm_page_filecache_min: 255139
vfs.generic.nfs.client.access_cache_timeout: 60
vfs.generic.nfs.client.readlink_nocache: 0
vfs.generic.nfs.server.reqcache_size: 64
net.inet.ip.rtmaxcache: 128
net.inet.tcp.clear_tfocache: 0
net.inet.tcp.init_rtt_from_cache: 1
net.inet6.ip6.rtmaxcache: 128
debug.iosk.version: Oct 31 2020 00:21:17 /AppleInternal/BuildRoot/Library/C=
aches/com.apple.xbs/Sources/IOSkywalkFamily/IOSkywalkFamily-166.40.6
debug.didevice_cache_fully_satisfied: 0
debug.didevice_cache_spared_bytes: 0
debug.didevice_cache_size_default: 33554432
debug.didevice_enable_cache: 1
hw.cacheconfig: 8 1 1 0 0 0 0 0 0 0
hw.cachesize:<PHONE_NUMBER> 65536 4194304 0 0 0 0 0 0 0
hw.cachelinesize: 128
hw.l1icachesize: 131072
hw.l1dcachesize: 65536
hw.l2cachesize: 4194304
security.mac.asp.stats.cache_entry_count: 1517
security.mac.asp.stats.cache_allocation_count: 4557
security.mac.asp.stats.cache_release_count: 3040

There is the bug:
hw.cachesize:<PHONE_NUMBER> 65536 4194304 0 0 0 0 0 0 0
hw.cacheconfig: 8 1 1 0 0 0 0 0 0 0

This is the CPU cache info of the slow CPU cores. The 1st column corresponds to main memory, the 2nd column is the L1 data cache and the 3rd column is the L2 cache. hw.cachesize contains the cache sizes per CPU core, the L1 data cache size is correct however the L2 cache size is the total L2 cache size (of the 4 slow CPU cores) instead of the L2 cache size per core. I think it should be 4194304/4=1048576 instead of 4194304. Unfortunately sysctl also does not contain any information about the high performance CPU cores.
The other option would be that hw.cacheconfig which reports the CPU cache sharing contains an errorneous value for the l2 cache sharing (3rd column). That value is 1 but could theoretically also be 4.

I have reported this bug to Apple: https://feedbackassistant.apple.com/feedback/8916770

I have found the sysctl output (https://pastebin.com/Ay2f9mQG) of an iphone CPU from 2017. I think this is the Apple A11 CPU from the iphone 8:
hw.activecpu: 6
hw.physicalcpu: 6
hw.physicalcpu_max: 6
hw.logicalcpu: 6
hw.logicalcpu_max: 6
hw.cputype: 16777228
hw.cpusubtype: 1
hw.cpu64bit_capable: 1
hw.cpufamily: -400654602
hw.cacheconfig: 6 1 1 0 0 0 0 0 0 0
hw.cachesize:<PHONE_NUMBER> 32768 8388608 0 0 0 0 0 0 0
hw.pagesize: 16384
hw.pagesize32: 16384
hw.cachelinesize: 128
hw.l1icachesize: 32768
hw.l1dcachesize: 32768
hw.l2cachesize: 8388608

Anandtech made an indepth review of the caches of both the A11 and A12 CPUs. And it seems the total L2 cache size is 8 MiB for both CPUs. So it seems that this issue does not only effect the M1 CPU but sysctl most likely reports strange L2 cache values for all Apple Silicon (ARM) CPUs.

Since sysctl only reports the number of total CPU cores for Apple Silicon CPUs and there is no information about how many slow and fast CPU cores there are, there is no way to reliably determine the L2 cache sizes per core on these CPUs. Also for the M1 CPU sysctl clearly only reports the cache sizes of the 4 slow CPU cores, however whether the cache info relates to the slow or fast CPU cores cannot be determined programmatic ally with sysctl.
This means that it is virtually impossible to find correct L2 cache (and likely also L3) info using sysctl for Apple Silicon CPUs.

I have added a workarounds for this sysctl bug in primesieve.
CpuInfo.cpp workaround:
#if !(defined(__x86_64__) || \
      defined(__i386__) || \
      defined(__ppc64__) || \
      defined(__ppc__))

  // For Apple silicon CPUs (ARM & ARM64) sysctl returns
  // erroneous L2 cache information. For the L1 cache
  // sysctl returns the cache size per core which is correct
  // (like on x86 CPUs). However for the L2 cache sysctl
  // returns the total cache size. It is unclear whether
  // hw.cachesize or hw.cacheconfig is erroneous.
  // See: https://github.com/kimwalisch/primesieve/issues/96
  //
  // Because of this sysctl issue it is impossible to know
  // the exact L2 cache size per core and whether the L2
  // cache is private or shared. However based on benchmarks
  // of the Apple M1 CPU the L2 cache scales nicely with
  // multi-threading provided we use less or equal the
  // (total L2 cache size / threads sharing the L2 cache).
  //
  // For these reasons we make an educated guess here:
  // If the CPU has an L2 cache we assume it is fast (will
  // scale nicely with multi-threading) and that using some
  // of it will improve the sieving performance.
  //
  if (hasL2Cache())
    sysctlL2CacheWorkaround_ = true;
#endif

api.cpp workaround:
#if defined(__APPLE__)
  // On Apple's operating systems (macOS & iOS) we use
  // the sysctl library to query CPU info. Unfortunately
  // sysctl returns erroneous L2 & L3 cache information on
  // Apple silicon CPUs (ARM & ARM64). We can only know
  // if an L2 cache exists and that it is likely fast. If
  // this is the case, we make a conservative guess that
  // the L2 cache per core is at least 8x larger than the
  // L1 cache as this will likely improve performance.
  if (cpuInfo.sysctlL2CacheWorkaround() &&
      cpuInfo.hasL1Cache() &&
      cpuInfo.l2CacheSize() > cpuInfo.l1CacheSize() * 16)
  {
    // Convert bytes to KiB
    size_t size = cpuInfo.l1CacheSize() >> 10;
    size = inBetween(8, size * 8, 4096);
    size = floorPow2(size);
    return (int) size;
  }
#endif

Apple seems to have fixed the bug (I have closed the issue: https://feedbackassistant.apple.com/feedback/8916770), Apple M1 Mac Mini with latest macOS. The L2 cache sharing is now correctly indicated as 4 (3rd number of hw.cacheconfig) for the M1 CPU.
 % sysctl -a | grep -i cache
hw.cacheconfig: 8 1 4 0 0 0 0 0 0 0
hw.cachelinesize: 128
hw.cachesize:<PHONE_NUMBER> 65536 4194304 0 0 0 0 0 0 0
hw.l1dcachesize: 65536
hw.l1icachesize: 131072
hw.l2cachesize: 4194304

primesieve now works correctly because of this fix:
% primesieve --cpu-info
Apple M1
Logical CPU cores: 8
L1 cache size: 64 KiB
L2 cache size: 4096 KiB
L1 cache sharing: 1 thread
L2 cache sharing: 4 threads


Large GeoTIFF file cacheable for next rendering

Hi Stuart,
I m using a large geoTIFF file around like 500 MB , want to make it caheable for next rendering in order to make it easily accessible for second time without waiting(First time it loads for two minutes). Or else any suggestion for loading it quickly for the first time.

There is probably not much you can do. GeoTiff is not supported by browsers and there needs to be read from a file and painted to a canvas. That needs some time, especially for files that big as yours. There is no reliable way to cache this amount of data on client side. The only solution I could I could think of is to convert the GeoTIFF to PNG and display these file(s) using Leaflet. Browsers can cache and render them directly.

Thank you for your response Matthias. I have worked out your solution, for display purpose that is converting GeoTIFF to PNG. But, my concern is on the values inside the GeoTIFF file , where it's been shown on 'hover' of the map. I have only two options left to make it work i.e, placing the GeoTIFF file locally (here, it initially takes sometime to get the file locally on client and retrieve the values on hover )or else publish it on the server side and get the values from server side at every hit from client side, which hampers the performance. Any help in this regard is appreciable.

Well, this workaround probably only works for displaying the graphics, but not for your use-case where you interact with the data. With such big files you probably need to think about other solutions like the second approach you mentioned. It's never a good idea to transfer 500MB files to the user for processing so optimize it and maybe shift this to the server side. Sorry for not having a better solution for you.

@s9eenk In the long run, Cloud Optimized GeoTiff could be a solution for your problem: http://www.cogeo.org

Have you tried using cogs yet? Any pointers on how to get started using those?


wip: fix(driver): fix build of kmod on linux 6.10.

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area driver-kmod
Does this PR require a change in the driver versions?
What this PR does / why we need it:
https://github.com/torvalds/linux/commit/c4aab26253cd1f302279b8d6b5b66ccf1b120520, included in linux 6.10-rc1, moved fd_is_open away from an header we can include.
Therefore the proposed patch is to implement ourself the one-liner.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Keeping it as wip until linux 6.10 is nearly released.
I'll use this PR for tests if more changes are needed.
Does this PR introduce a user-facing change?:

fix(driver): fix build of kmod on linux 6.10.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone next-driver

Kmod build is now ok: https://github.com/falcosecurity/libs/actions/runs/9300407315/job/25596333511

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM! I would just add the kernel commit link also in the code not just in the PR

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Done, anyway, let's wait for at least 6.10-rc6 before unholding :)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97,FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

RC3: still ok: https://github.com/falcosecurity/libs/actions/runs/9544785509/job/26304199255

Hey @FedeDP
What's missing here? :thinking:

RC5 still ok: https://github.com/falcosecurity/libs/actions/runs/9675438479/job/26692952935

Green against rc7: https://github.com/falcosecurity/libs/actions/runs/9869833752/job/27254326144
Removing wip and merging.


YARN-9877 - Intermittent TIME_OUT of LogAggregationReport

In case of ACQUIRED -> RELEASED transition the LOG aggregation will time out for container.
(Based on  @adamantal works, thanks for it.)
Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
48m 48s

trunk passed

+1 :green_heart:
compile
1m  3s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 59s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m  2s

trunk passed

+1 :green_heart:
mvnsite
1m  3s

trunk passed

+1 :green_heart:
javadoc
1m  5s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 52s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
2m 10s

trunk passed

+1 :green_heart:
shadedclient
34m 40s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 50s

the patch passed

+1 :green_heart:
compile
0m 56s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 56s

the patch passed

+1 :green_heart:
compile
0m 50s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
0m 50s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 45s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 117 unchanged - 0 fixed = 118 total (was 117)

+1 :green_heart:
mvnsite
0m 51s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 43s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
1m 56s

the patch passed

+1 :green_heart:
shadedclient
34m 50s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
100m  9s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

238m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5784

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 0d5c79d4d338 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9330a4c81f50a2167981ada35f07ff7fa18035c5

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/1/testReport/

Max. process+thread count
969 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 46s

trunk passed

+1 :green_heart:
compile
1m  4s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 59s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m  6s

trunk passed

+1 :green_heart:
javadoc
1m  3s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 52s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
2m  1s

trunk passed

+1 :green_heart:
shadedclient
34m 51s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 52s

the patch passed

+1 :green_heart:
compile
0m 56s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 56s

the patch passed

+1 :green_heart:
compile
0m 47s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
0m 47s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 46s

the patch passed

+1 :green_heart:
mvnsite
0m 52s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 43s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
1m 55s

the patch passed

+1 :green_heart:
shadedclient
34m 31s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
100m 14s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

233m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5784

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux ac72a7084a9e 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9264f6f8fb91742d4deca16e180997a97b810b4d

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/2/testReport/

Max. process+thread count
948 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m 32s

trunk passed

+1 :green_heart:
compile
1m  3s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 58s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
1m  5s

trunk passed

+1 :green_heart:
javadoc
1m  3s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
2m  5s

trunk passed

+1 :green_heart:
shadedclient
34m 34s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 52s

the patch passed

+1 :green_heart:
compile
0m 54s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 54s

the patch passed

+1 :green_heart:
compile
0m 48s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
0m 48s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 45s

the patch passed

+1 :green_heart:
mvnsite
0m 51s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 41s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
1m 54s

the patch passed

+1 :green_heart:
shadedclient
34m 32s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
100m 17s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

233m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5784

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux ac26654a68a3 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fd10ab7097598543282bd35ea015aebc4268f5c9

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/3/testReport/

Max. process+thread count
993 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

LGTM

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
47m 35s

trunk passed

+1 :green_heart:
compile
1m  3s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 59s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
1m  4s

trunk passed

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
2m  2s

trunk passed

+1 :green_heart:
shadedclient
34m  9s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 49s

the patch passed

+1 :green_heart:
compile
0m 53s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 53s

the patch passed

+1 :green_heart:
compile
0m 46s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
0m 46s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 45s

the patch passed

+1 :green_heart:
mvnsite
0m 52s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 42s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
1m 58s

the patch passed

+1 :green_heart:
shadedclient
34m  9s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
100m 19s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

234m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5784

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 096104ad2e20 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7d0d44cf8eb7117b9b36f757e979039eb3d619f3

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/4/testReport/

Max. process+thread count
957 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5784/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


uv doesn't reinstall editable package when non-editable package is requested

Consider the following sequence
$ git clone https://github.com/aiidateam/aiida-core && cd aiida-core
$ uv venv --seed
$ uv pip install --no-deps -e .
   Built file:///home/hollas/atmospec/aiida-core                                                                                Built 1 editable in 170ms
Resolved 1 package in 0.71ms
Installed 1 package in 1ms
 + aiida-core==2.5.1.post0 (from file:///home/hollas/atmospec/aiida-core)

Running editable install for the second time re-installs the package, which is nice:
$ uv pip install --no-deps -e .
Built 1 editable in 183ms
Resolved 1 package in 0.93ms
Installed 1 package in 4ms
 - aiida-core==2.5.1.post0 (from file:///home/hollas/atmospec/aiida-core)
 + aiida-core==2.5.1.post0 (from file:///home/hollas/atmospec/aiida-core)

However, trying to install the package in non-editable mode does not re-install it
$ uv pip install --no-deps .
Resolved 1 package in 1ms
Audited 1 package in 0.04ms

uv version 0.1.36

Hmm interesting. Makes sense to force a reinstall here I suppose.

My understanding was that while the editable mode generally tries to emulate the actual installation, it is not guaranteed to be perfect so I think reinstalling is the only correct option here. Citing from PEP 660

Depending on the way build backends implement this specification, some minor differences may be visible such as the presence of additional files that are in the source tree and would not be part of a regular install. Build backends are encouraged to document such potential differences.

I'll label it as a bug.


Receiving multiple codeLens requests on startup

Issue Type: Bug
I am developing a language extension but it receives multiple codeLens requests when the server starts up. Whenever the documentText changes, two (or maybe more) requests are sent. Not sure if this is an intended behavior.
If I return Null for the first request, and no matter what codeLens I returned for the second one, no codeLens will not be shown.
[Trace - 1:13:20 AM] Sending request 'textDocument/codeLens - (3)'.
Params: {
    "textDocument": {
        "uri": "file:///d%3A/Projects/lsp-wl/repo/src/WolframLanguageServer/Server.wl"
    }
}

[Trace - 1:13:20 AM] Sending request 'textDocument/codeLens - (4)'.
Params: {
    "textDocument": {
        "uri": "file:///d%3A/Projects/lsp-wl/repo/src/WolframLanguageServer/Server.wl"
    }
}

[Trace - 1:13:20 AM] Sending request 'textDocument/codeLens - (5)'.
Params: {
    "textDocument": {
        "uri": "file:///d%3A/Projects/lsp-wl/repo/src/WolframLanguageServer/Server.wl"
    }
}

VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:58:56.166Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (5.83GB free)

Process Argv
--folder-uri file:///d%3A/Projects/lsp-wl/repo

Screen Reader
no

VM
0%

Extensions (23)

Extension
Author (truncated)
Version

mock-debug
and
0.35.1

ccls
ccl
0.1.28

cquery
cqu
0.1.10

vscode-eslint
dba
2.0.13

tslint
eg2
1.0.44

wolfram-language
fli
0.1.0

base16-generator
gol
1.11.0

lsp-wl-client
lsp
0.1.5

vscode-elixir
mjm
1.1.0

python
ms-
2020.1.57204

cmake-tools
ms-
1.2.3

cpptools
ms-
0.26.2

vsliveshare
ms-
1.0.1456

lsp-inspector-webview
oct
0.0.2

vscode-elixir-formatter
sam
0.2.0

code-settings-sync
Sha
3.4.3

trailing-spaces
sha
0.3.1

vscode-wl
shi
1.7.3

org-mode
too
0.5.0

cmake
twx
0.0.17

vscode-icons
vsc
9.7.0

vim
vsc
1.12.4

markdown-all-in-one
yzh
2.6.1

(1 theme extensions excluded)

Please provide a full repo sample

client: https://github.com/kenkangxgwe/vscode-lsp-wl
server: https://github.com/kenkangxgwe/lsp-wl/tree/feature/dap-wl
You also need to install wolfram engine: https://www.wolfram.com/engine/
Actually, after I disabled Live Share extension the codeLens went back to normal. Once a time.
So I guess the Live Share duplicates the request, and doesn't show the codeLens if two responses do not match, which is a wired behavior.
Not sure if you have any idea about how Live Share affects the vscode lsp client. Should it change the number of requests and behavior after responces are received?
I am also gonna file an issue for the LiveShare team and close this one after they confirm the problem.

Yeah, that afaik the expected behaviour of live share. In order to show the guest data from the host requests are re-run, e.g they have no access to our UX but to the data providers

Sounds reasonable, I will keep in mind for further implementation. Thanks

Yeah, from the vscode pov this is definitely as-designed. We expose a bunch of "api commands" (https://code.visualstudio.com/api/references/commands) which other extensions can use, e.g an extension might run the document symbol command to know where to place code lenses


cmake-tools does not use the chosen python interpreter from the vscode python extension

Brief Issue Summary
When using cmake targets which make use of external python scripts I would expect vscode-cmake-tools to invoke the cmake binary within the python virtual environment that is the currently chosen interpreter by the python extension. Currently, It doesnt meaning that any python dependencies in a cmake workflow must be installed in the global python environment when using vscode-cmake-tools. Or the user needs to step outside vscode-cmake-tools and run the cmake commands manually in a regular terminal.

Thank you for opening this report. You can try to use the environmentSetupScript of a kit to point to a script that is setting all the environment variables (path for example) as your python environment. Then when the kit is active (after a project reload or after changing to a kit that has environmentSetupScript defined) the operations like configure or build should have access to that environment.
Let us know if this isn't working for you or if you had a different scenario in mind.

Thanks for the quick response @andreeis  and thanks for the suggestion!
I find myself unsure how to use environmentSetupScript, is this a cmake-native thing or a vscode thing or a vscode-cmake-tools thing? I struggle to find any docs regarding environmentSetupScript here. Most probably looking in the wrong place, would appreciate a hint!

Good questions :). It is a CMake Tools concept. You edit the kit you want to load from cmake-tools-kits.json (you can open it with the command "CMake: Edit user level kits" in the pallette) or your project local .vscode subfolder like below:
{
"name": "Your kit",
"environmentSetupScript": "path/to/script",
... any other attributes you need for your kit ... like preferredGenerator, or visualStudio versions or compilers C/CXX pairs...
}

So, after some initial trial-n-error I ended up with creating a project-specific cmake-kits.json with the following content:
[
    {
      "name": "GCC 9.3.0 in virtualenv",
      "compilers": {
        "C": "/bin/gcc-9",
        "CXX": "/bin/g++-9"
      },
      "environmentSetupScript": "${workspaceFolder}/venv/bin/activate"
    }
]

This works relatively well and solves the "problem" even though there still is no actual integration with the vscode python extension.
Thanks for your help @andreeis !

Glad to hear this works for you now. I am closing the report.
Just to brainstorm for the future, what support exactly would you like to see in CMake Tools to integrate better with the Python extension, besides having the script in a kit? Feel free to comment on this at any time. It will be low priority to implement for sure but it never hurts to think ahead.

Hi, I hope you don't mind me posting on this closed issue. I was setting up a CMake project and stumbled upon a similar problem.

Just to brainstorm for the future, what support exactly would you like to see in CMake Tools to integrate better with the Python extension, besides having the script in a kit?

I think the problem is that when you configure the project using CMake Tools, whenever CMake is looking for Python (e.g. using FindPython3), it finds the global Python interpreter, not the one that has been set using Python: Select Interpreter. It would be nice if CMake Tools would activate the environment selected in the Python extension before configuring the project.

what support exactly would you like ... besides having the script in a kit?

Using kits and environmentSetupScript seems like a reasonable workaround to the problem above, despite it not being automatic (i.e. you have to manually set the path to the environment activation script). But what about projects that use CMake presets instead of kits and variants? According to the documentation:

We recommend CMakePresets.json as an alternative to kits and variants files.

Is there a way to have an environmentSetupScript in that case?

@yannidd , regarding this:

Is there a way to have an environmentSetupScript in that case?

We don't support yet a similar concept like environmentSetupScript in the presets scenario. Considering this kitware issue https://gitlab.kitware.com/cmake/cmake/-/issues/21619, such approach was intentionally avoided.
We looked at what environmentSetupScript achieves (sets environment, performs various operations like registry, fileIO, process execution) and brainstormed some alternatives. For various operations, one can use a toolchain file, custom targets, custom commands or CMake scripting commands (https://cmake.org/cmake/help/latest/manual/cmake-commands.7.html#scripting-commands). For capturing the environment, one can use #execute_process(https://cmake.org/cmake/help/latest/command/execute_process.html) and #set(https://cmake.org/cmake/help/latest/command/set.html#set-environment-variable).


Remove hostname from pyrsia config - since it is not used anywhere

I think it might still be useful in situations where you run have to run pyrsia in a non-default way. (e.g. binding on a specific local IP instead of localhost for some reason)
I'm moving it out of 0.2 since it would also require a lot of documentation changes.
Also, I'm going to create another issue to allow for easier configuration: when I want to switch between 2 nodes on the same localhost, I have to go through the config wizard every time, just to change the port number.

I also felt the same way while making some earlier changes. Under pyrsia config the current available options like add, edit, remove, show may be considered as subcommand. While host, port & disk space can be options under add & edit subcommands.

Perhaps we should re-examine all of the command line options at this time, and consider making them config options as well. Specifically, listen-only and the bootstrap_url seem like possibilities (perhaps still overridable by command line switches). I think that would be more consistent with the other options.

Looking at the all comments

We are not going to take out host as we might require it in future to bind on specific local IP instead of localhost for some reason
with improved pyrsia config edit now we can configure host, port and diskspace individually and in combinations as well.

pyrsia-config-edit
Edits a node configuration

USAGE:
    pyrsia config {edit|-e} [OPTIONS]

OPTIONS:
    -H, --host <HOST>               Hostname
    -p, --port <PORT>               Port number
    -d, --diskspace <DISK_SPACE>    Disk space to be allocated to Pyrsia node
    -h, --help                      Print help information


Fix 2022 base images

This is probably wrong, but closer. I assume I'm supposed to generate these, but I just got the latest tags I think are right.

/test builder-base-tooling-presubmit-2022

The periodic should have built these and updated. Let me check it out


added switch to react routes Fixes #10

Right now redirecting to / on entering misc routes.
Let me know if a custom 404 component is created 🙂

Our app is composed in a way that actually matches and renders multiple components for the same route
If you look at the documentation for Switch, you will see that it only renders one route exclusively... the first one it matches.
So this change would actually break existing functionality.

Plus, even if fixed, it solves a problem we don't really have. People manually entering the wrong url in the address bar.
Our problem is when a url that does match a route loads, but the app doesn't have the data to show it.
Thanks for digging up about  I actually didn't know of it until now... I had to read up about it. I wish I had known, it could have actually helped me in the past.

Hey @TalAter, I understood your point. I didn't noticed the route /vehicle/:uid. Yes, with switch it breaks the existing routes and the way the app is constructed. Sorry for the trouble.


Introduce a new security.devlxd key to control visibility of /dev/lxd…

… inside the container
Issue: #3997
Signed-off-by: Chris Loper

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

jenkins: test this please

I am confused by the Travis CI build failed.  Would someone mind explaining what that is actually doing?
Thanks.

<bikeshed>
@stgraber, wouldn't it make more sense to have that key named security.disable_devlxd then? The other keys security.nesting and security.privileged can really be phrased as Can be nested?, Is privileged? whereas Can devlxd? and Is devlxd? don't provide the same semantic content. I'd suggest the config key for new booleans be such that you can gather without looking whether this is an on or off switch for something without looking at the docs.
</bikeshed>

Do you want me to change it so the key is called "security.disable_devlxd" and set it up such that its default value is false then the /dev/lxd configuration is set up and if the key is set to true in the container config the /dev/lxd configuration is skipped?

Do you want me to change it so the key is called "security.disable_devlxd" and set it up such that its default value is false then the /dev/lxd configuration is set up and if the key is set to true in the container config the /dev/lxd configuration is skipped?

No, not before we have maintainer consensus. :)

@brauner we already have a couple of keys which default to true in the containers config, so I'm not too bothered by having security.devlxd default to true and it sure will be easier to remember that security.disable_devlxd :)

Once I see that @brauner comments with the go ahead i will push the request changes that he made so that the pull request process can continues.

Once I see that @brauner comments with the go ahead i will push the request changes that he made so that the pull request process can continues.

Sure, go ahead.

@brauner we already have a couple of keys which default to true in the containers config, so I'm not too bothered by having security.devlxd default to true and it sure will be easier to remember that security.disable_devlxd :)

I'm a little confused by this message and whether the "that" is supposed to be "than" but I take it that @stgraber acked the change to security.disable_devlxd and that it defaults to true. Maybe keep a backup of your current branch in case I'm misinterpreting. If you understood otherwise just go ahead with your understanding. :)

All of the changes that @brauner requested were made except for the final one regarding the check since he said that what I had was legal given the specification from @stgraber.

@brauner what I said is that security.devlxd is fine, it can default to true and we have precedent for other keys defaulting to true. disable_XYZ is a syntax we haven't used before and seems needlessly long.

My point about defaulting to true is not based on whether there's precedent or not. It's based on the fact that if you consider something security sensitive you should probably make it opt-in not opt-out. I also don't follow why this is needlessly long when it adds clarity about what the key does. However, I'm also not invested in this so let's keep it as is.

Ok.  Everything in the most recent commit is as is with the few changes requested.

@calhorn95, can you squash the two commits into one, please?

@brauner  Just squashed into one commit.  Thanks.

jenkins: test this please

You need to do a:
go fmt ./...

in the top of your tree to correctly format the go code. Otherwise compilation will fail.

Just ran that and re-pushed.  Sorry about that.  I am still becoming familiar with Go.

No worries. :)

jenkins: test this please

jenkins: test this please

Left a few comments in-line. Would also be neat to add a test for this.

I just pushed the changes that @stgraber requested.  For creating a test for this, would it consist of adding to "container_test.go"?  Also, is creating a test something that needs to be done before the changes can be merged.  Thanks.

Added a test in container_test.go in the most recent commit.

jenkins: test this please

@calhorn95 sorry for the delay, I was off all week last week. I left a few in-line comments and a suggestion on a better way to test this. With those sorted, we'll be good to merge this.

No worries.  Thank you very much for helping me along with this. Adding the test into the test suite makes much more sense.  All of your requested changes have been made.  Thanks.

jenkins: test this please


[GHSA-p99v-5w3c-jqq9] Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks

Updates

Affected products
References

Comments
Add one more patch related to CVE-2021-33571.

Hey @sunSUNQ, I'm going to close this one as the commit is not relevant for the particular affected products that we have.


blogstack.io domain doesnt resolve

the domain blogstack.io hasn't resolved for a few days, will the domain be renewed or moved elsewhere?

Let's share some alternatives here:
https://habla.news

I'm rewriting the site, it's at https://notestack.com


Add Cloud Compute ToS

The link to the policy will be in the footer of the site, consistent with other policies. You can check out the footer here: https://deploy-preview-174--suspicious-volhard-46e848.netlify.app/


SetText crush engine with AccessViolationException

Fix this in 0.1.2

Need to replace ugly TextRenderer with QuickFont


High resolution problem

Hello, I have a question to ask. I have downloaded the Samsung dataset and obtained low-resolution images, and the program runs successfully. However, I have been searching for a long time but cannot find the high-resolution images to compare the results and calculate PSNR and SSIM. I appreciate any help.
Thank you so much.

The samsung images come from the burst SR dataset https://github.com/goutamgmb/deep-burst-sr (paper explaining the collection procedure: https://arxiv.org/abs/2101.10997). Please have a look at the full-resolution dataset section to get the images, there should be a Canon folder with the targets images in it for each sample. Here is a sample of the dataset:

The goal of the authors is to learn 4x SR with DSLR high-resolution sRGB photographs as targets. They thus learn in the process the ISP for rendering a Samsung G8 raw images into a Canon 5DIV sRGB rendering, including sharpening. The targets are the canon's JPEG companion images. However a fundamental difference between deep learning approaches trained with such targets and the handheld method is that the former are pattern matching techniques that may hallucinate details whereas the latter aims solely at interpolating a good denoised and dealiased image from the noisy and aliased samples alone. Furthermore, the authors of the original paper noticed that you can really obtained new details up to 2x, beyond this point you are limited by the optics! This reasoning was made for the Google Pixel 3 phone but you can assume that the contemporary Samsung G8 model has a similar lens, and thus yields similarly aliased raw images.
As a result, the output of the handheld approach comes without the whole post-processing of any camera ISP. It is up to you to apply any post-processing you like, and it must include deconvolution/sharpening (please have a look at the explanations of papers in the same vein like: https://people.duke.edu/~sf59/SRfinal.pdf). Also, the target Canon photo and the reference frame of the burst are only weakly aligned. If you really want to measure a pixel-to-pixel loss such as the PSNR or the SSIM, you may want to use the CoBI loss from this project: https://ceciliavision.github.io/project-pages/zoom.html Note that it is beyond the scope of this repo that focused on reproducing as faithfully as possible the original handheld paper!
tl;dr: You can increase by 4x the resolution of the final image to match that of the targets of the burst SR dataset, but this comparison is comparing apples and oranges because you have to apply your own ISP pipeline to render the final sRGB image (since Canon's ISP is a black-box function, it is very unlikely that you will have a perfect 1:1 reproduction), and the regression techniques are different: pattern matching (deep learning) v. interpolation (handheld, kernel regression).
Let me know if you still have questions :)
Best,
Thomas

Hello, I've understood the method for obtaining the dataset, and I'm currently studying both the program and the paper. However, what I would like to inquire about is conducting PSNR and SSIM tests and comparisons between your super-resolution method and mine. I'm wondering if there's a faster way to obtain high-resolution results. Thank you~~


Broken link to the code repository

Hi,
I was going through "custom-response-policy-example.adoc" and found a broken link to the code repository:
https://github.com/mulesoft/api-gateway-custom-policies-examples
I would like to know proper repository link.
Thanks

Hello,
Thanks so much for bringing this to our attention. Unfortunately, the linked GitHub repository is no longer public, and another repository hasn't been made available.
I'll submit a documentation PR that removes the line containing the broken link.
Thank you again.
Regards,
Chris Campbell


Use find instead of ls -d to avoid -bash: /bin/ls: Argument list too long

First off, thanks for this handy script!
I ran into an issue because my build server had ~85k orphaned volumes (image building server from late 2014 :) ) where the ls -d ${targetdir}/* command was failing.
I was able to replace it with find ${targetdir} -maxdepth 1 -type d and continue on my merry way, however I don't have the time or criteria to test and ensure that works in all cases, so I figured an issue was better than a PR.
Thanks again and hope this helps!

Hey @drags, I ended up having the same issue and sent over pull req #23. Updated to include maxdepth.

@almonteb awesome! I should have checked PRs first. Thank you for opening this


[Fastor] add new port Fastor

Describe the pull request

What does your PR fix? Fixes #16532

Which triplets are supported/not supported? Have you updated the CI baseline?
It is a header-only library. I'm assuming it supports all triplets. CI baseline has been updated.

Does your PR follow the maintainer guide?
Yes.

Since the upstream port provides a cmake config, IMO you should install it with cmake and fixup the targets.

Hi @Hoikas and @NancyLi1013,
I'm aware that Fastor supports CMake on master branch, but the latest release tag (V0.6.3) does not have CMake. That's why I can't use CMake there.
Any suggestions on how to solve this?

Hmm... Considering how helpful cmake targets are, it might be best to use the latest commit and set the port's version to today's date.

Is it possible to port the package without cmake for now? When that repo publishes a new tag we can write a new port with cmake.

@duanqn
I agree with the proposal from @Hoikas. You can use the latest commit until the next tag is released which contains CMakeLists.txt.

Convert to draft until the upstream changes. Please ping me if it is ready for review.

Hi @duanqn
Could you please update to the latest commit that contains CMakeLists.txt for this PR?

@duanqn , Is this PR being worked on? Could you update pr based on nancy's suggestion?

@JonLiu1993 Thanks for notifying me. Please see if the current port meets the requirement.

Thanks for the new port!


Better support for multi-tenancy sites

This is a work in progress ticket, intended to gather user stories for adding multi-tenancy support to Oscar
Requirements:

[ ] Allow multiple (sub)domains to point to the same Oscar install.
[ ] Allow a subset of the catalogue to be shown on each site
[ ] Users should be able to login to each site so their address/billing information is shared
[ ] Reporting will need to distinguish between sites

Things that need to vary per site:

[ ] Offers
[ ] CMS-controlled pages
[ ] Promotions/merchandising

what is the status for this multi-tenancy ?

Hi all, I am also interested in utilizing this functionality. Has there been any advances in this area?

:+1:

We achieved multi-tenancy at edX (https://github.com/edx/ecommerce) in the following manner:

Added site foreign key to Basket model
Created a SiteConfiguration model with site-specific data, and linking Site objects to Partner objects.
Each Product has a single StockRecord whose related Partner allows us to determine which Site the product is affiliated with

In hindsight, the overloading of the Partner model is not ideal. Were I to change things, I would add a site foreign key to the Product model.
Note that we share users across the sites. This might not be desired in a truly white-label multi-tenancy scenario.


Add events model

Description & motivation
Include model to report on events, without duplicates and with clean column names
Checklist

[x] I have verified that these changes work locally
[x] I have updated the README.md (if applicable)
[x] I have added tests & descriptions to my models (and macros if applicable)

done by mistake


About start training: IndexError: tuple index out of range.

Hi, Dr.Gong,
I use AST on my own dataset. I have created the .json file and .csv file according to the guide.  The error is as shown below,

I don't know how to solve it. I would appreciate it if you can tell me the reason.
Yours

I check for the reson for a while. I printed the shape of fbank which is [128, 1024]. It seems that the spectrograms havn't trans to RGB channel. Would you please tell me how to fix it?

I cannot tell the reason either. But there's no RGB concept in the audio spectrogram. It is just 1-d information. [128,1024] means 128 frequency bins, 1024 time frames, which looks correct. The problem seems to happen in spectrogram masking.

Alright. I check line 191 in file ./dataloader, it seems that the problem happen in TimeMasking.

What's more, the average length of my dataset is only 2.5s. Do you think such a short audio will cause errors in theTimeMasking and affect the final performance of the model?

The length depends on input_tdim, for your case, you should modify run.py to set input_tdim=250. timem should be smaller than input_tdim. Again, I suggest starting from either the speechcommands or esc50 recipe to get more familiar with the code.

Hi, Dr. Gong
I comment the timem and the program worked successfully. For my own dataset, I split them for test and train. 20 percent of each class for test and the last for train. After training, I got a strange result as shown:
0.908529570359724
0.965062499999999
0.685776370522133
1
2.56357337530442
These are the value from wa_result.csv.
I'm very confused about this. Besides, the RECALL performs value of 1 each epoch. And I try to use the inference.py to predict the audio file and it seems works well.
I would appreciate it if you could tell me your train of thought to solve this problem.
Yours

I also encountered the same problem, could you please tell me how to solve it in detail,Thank you very much

I also encountered the same problem, could you please tell me how to solve it in detail,Thank you very much
what exactly is your problem?

About start training: IndexError: tuple index out of range?

About start training: IndexError: tuple index out of range?

I commented it directly. Then I performed data augmentation directly before training and took the augmented data as input.

Okay, thank you very much. I'm trying

OK, I finally find the reason.
This is due to a torchaudio issue. We use torchaudio 0.8.1, in which the input of the masking can be [freq, time] while the newer version torchaudio only accepts [1, freq, time].
I have fixed it with a workaround at https://github.com/YuanGongND/ast/blob/b7086755ebfd9f2ab018c0a40722b8418d9d41fe/src/dataloader.py#L191-L197
It should work for both old and new torchaudio
Your workaround (comment the time-masking) might cause a problem of inaccurate masking span and lead to a performance drop (while might be very small). I would suggest using our fixed code. It is very simple.

You can use the Colab script to find the bug https://colab.research.google.com/github/YuanGongND/ast/blob/master/colab/torchaudio_SpecMasking_1_1.ipynb


How to choose spacing in dynunet

Hello
I want to use dynunet for segmentation. I have dataset with different spacing. How can I choose spacing for my own dataset?

Hi @RespectKnowledge ,
Thanks for your interest here.
@wyli @rijobro , could you please help share some experience about spacing values?
Thanks in advance.

New utility function is now available https://github.com/Project-MONAI/MONAI/blob/dev/monai/data/dataset_summary.py for computing median spacing from a dataset.

Thanks for sharing


Fixed : deprecation of unescaped multiline strings

Unescaped multiline strings are deprecated and will be removed in a future version of Sass.

Hey Lucas. Unfortunately, this cannot be merged as it breaks the tests. Unfortunately, there is no fix for this and SassyJSON should not be used in production anymore.


Warnings fixes

Xcode 7 shows some extra warnings, which was hidden in Xcode 6. So this patch fixes them.

"G8Tesseract.mm:56:17: Method override for the designated initializer of the superclass '-init' not found" warning has been fixed. The default initializer implementation has been added.
Init is no longer unavailable. Instead it initializes the totally default Tesseract instance.
Unit test for the default initializer has been added.
"InitializationTests.m:265:49: Initialization of pointer of type 'id' to null from a constant boolean expression" warning has been fixed.

Can you investigate why coveralls reported that our coverage decreased from 100% to 64.557%?

@kevincon, I don't know the reason. It seems it was just a bug in coveralls. It showed that all the files were covered 100%, but total statistic was 64.557%.
I've just restarted the job and now there is 100% totally.
Pls, review. Thx!

I'm all for fixing warnings, but if the init function with no parameters is used to create a G8Tesseract object and then recognition is performed without setting a language (i.e. it's nil), then Tesseract defaults to looking for the English trained data file. That's what happened in this issue that prompted me to prevent the use of init without setting a language: #145
How about a compromise? Can you make a log message be printed out if the init function with no parameters is used to say something like:

WARNING: Initializing G8Tesseract without a language defaults to English, so make sure you either set the language afterward or have eng.traineddata in your tessdata folder, otherwise Tesseract will crash!

@kevincon, I've missed this ticket. Sorry.
I think log message is a goof idea. But I'll put it in the language setter. Since such situation may happen after the user has been changed the language manually as well.

Also there is an ambiguity in Tesseract initialization code and language setter. From one side we return nil from the initializer if we cannot init engine (so there is no tess instance at all). From other side if we try to change language from an already initialized tesseract instance and fail to initialize with it we'll have a tesseract wrapper with bad engine (that's an error actually and even if you try to change the language to a correct one later, tesseract will crash since engine is corrupted).

So I've changed the behavior, so it's similar in both cases above. An initializer now always returns a tesseract wrapper even if it cannot initialize engine. But in the fail case it will set language to nil and no engine alive will exist. In the case the users try to set wrong language using the setter they will also get a nil languages property and no tesseract engine alive. So in both cases the users are able to check the reason and recover with correct language.
@kevincon, pls, refer to the PR.
and let me know if I missed something. Thx!

I've also found that all the functions, which need tesseract engine to work properly never checks that the engine is valid. So they may crash in case the engine doesn't exist. So I've added those conditions to implementation and notes to the header. I've also will add unit tests to cover new code soon.

Okay, let me know when you add the unit tests so I can review the PR.

According to the whole idea of returning valid instance of the wrapper always, but instead have a dead engine if error occurs, I've changed the code, which returns nil, if the user tries to copy tessdata files from app bundle to the absoluteDataPath.
So we may make absoluteDataPath writable, so the user is able to change tessdata path on an existing tesseract wrapper instance :)
@kevincon, actually, I'm done with making everything similar in this PR. May also make absoluteDataPath writable if you wish, but I don't think it's so useful. Pls, review very carefully, since I've changed very basic functionality significantly. Thx!

@kevincon, is there something wrong with the PR? Can you review it and merge, if everything is ok?

Sorry for the delay, things have been really busy at work. I'll start reviewing the PR now.

Okay I finished reviewing it. I found some typos that should be fixed and I also commented about a few questions that I have, but other than that it looks pretty good. Thanks for working on this. :)

@kevincon, I've fixed most of the typos and errors you mentioned and put all of them in the separate commit, so it's easy to review them. When you confirm them, I'll squash them with the corresponding commit.
Also, I've written some comments to the rest of your notes. Pls, read them and let me know what do you think. Thx!

Looks good, thanks for fixing those typos. Can you resolve the merge conflicts and do the squash? Then I'll merge it for you.

Sure!

Thanks! Merging and closing.


Running react native on ios failing

When trying to run yarn native and then pressing i for iOS, I get the following error:
iOS Bundling failed 14290ms
error: Error: While resolving module `next/router`, the Haste package `next` was found. However the module `router` could not be found within the package. Indeed, none of these files exist:

  * `/Users/bjoern/projects/farmer-assistant-2/apps/next/router(.native|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx|.ios.js|.native.js|.js|.ios.jsx|.native.jsx|.jsx|.ios.json|.native.json|.json)`
  * `/Users/bjoern/projects/farmer-assistant-2/apps/next/router/index(.native|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx|.ios.js|.native.js|.js|.ios.jsx|.native.jsx|.jsx|.ios.json|.native.json|.json)`
    at resolveHasteName (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro-resolver/src/resolve.js:198:9)
    at Object.resolve (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro-resolver/src/resolve.js:68:20)
    at ModuleResolver.resolveDependency (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:126:31)
    at DependencyGraph.resolveDependency (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro/src/node-haste/DependencyGraph.js:264:43)
    at Object.resolve (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro/src/lib/transformHelpers.js:170:21)
    at resolveDependencies (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro/src/DeltaBundler/graphOperations.js:466:33)
    at processModule (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro/src/DeltaBundler/graphOperations.js:232:31)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async addDependency (/Users/bjoern/projects/farmer-assistant-2/node_modules/metro/src/DeltaBundler/graphOperations.js:361:18)
    at async Promise.all (index 2)

oh, might be a new bug introduced, looking into this

Fixed in the newest commit!
A couple days ago I changed our next app name from next-app to next so that the folder name and the package name is consistent. For the sake of deploying to Vercel.
Which created a conflict of namespace between "next" the node_modules framework and "next" our web app.
Should've saw that coming! Let me know if it works for you guys now.

just tried it and it works :) Thanks for the quick fix


Switching to ESLint

Branched/continued from #11644, #11693
This issue was created to track down moving to ESLint separately from the existing PR (and the general ES6 support)

[x] Update Brackets core code to ESLint (done in #11693)
[ ] Integrate ESLint to Brackets core @zaggino (https://github.com/adobe/brackets/pull/11693#issuecomment-162841573)
[ ] Decide what to do with the existing linter (JSLint)

The integration part should be easy but what about the third box? Possible options include:

Make ESLint the preferred linter and let the user use JSLint if the user decides to do so (confusing to those who have just used JSLint in the past)
Make ESLint the preferred linter and remove JSLint altogether (spinning it to non-core extension) (similar issues as above)
Just let them exist side by side and the let the user configure the settings (most confusing as files get linted twice?)
Provide UI to select the preferred linter on first launch of Brackets 1.x (most user friendly, needs UI work etc.)

@abose @ficristo @MarcelGerber

I've a biased opinion since I don't like particularly JSLint, but if we want it still in core it should be at the least updated.

Modified 3. We could default to ESLint only and provide a preference to enable JSLint also.

Submitted a PR https://github.com/adobe/brackets/pull/11988

Since the brackets-shell ticket has been merged, does that mean ESLint will be formally included in Brackets 1.8 release? Thank you!

@tclzcja no, that ticket is only about to use ESLint to lint brackets-shell code.
You will have still to use an extension for 1.8 for your code.

What's the status of this?

I can setup a PR for "Integrate ESLint to Brackets core" if desired.

Shipped in 1.11.


corrupted parameter values in ROM

I recently had INAV_ENABLED change (unexpectedly) from 1 to 0 in a Pixhawk which I had set up to run the Q estimator and INAV. This correlated with flow/POSCTL becoming unstable. Changing INAV_ENABLED back to 1 using Tower made flow based POSCTL work again, but the logfile from that flight shows "INAV_ENABLED 1.06535322E9". Rebooting the Pixhawk showed the ekf_att_pos_estimator running... no att_estimator_q or INAV.

Tower is corrupting the values. Please file an issue against it. It's a known issue as its not adhering to MAVLink specs.

@LorenzMeier Could you point me to the known issue with Tower violating the mavlink spec?

APM is not interpreting params as per the standard for non-float values. They would need to adjust their param conversion routines depending on which autopilot they are connected to. If you mention me in the issue I can provide the link.

@LorenzMeier BTW, this seems to indicate a lack of input validation on the PX4 side, since 1E9 is somewhat larger than the spec'd max value for the parameter.

@LorenzMeier https://github.com/DroidPlanner/Tower/issues/1483

There is and will be no input validation. It's pointless as its the inner working of the system and there is a million ways to crash a drone using individually correct, but collectively wrong parameters. At the point where we can validate them collectively we have built a system that doesn't need parameters anymore - that would be a great end goal though.

We might be able to add range limits cheaply which would have prevented this, to me that's not real input validation though. Is that what you meant?

yes, the valid range of INAV_ENABLE is [0,1]
I presume that PX4 behavior is "undefined" if it's not in that range

by "valid range" I mean what I read in the parameter description


fails to build on darwin

Describe the bug
See #185 for companion bug.
After adjusting the URL so that the git clone succeeds, I move onto the next step, which also fails.

To Reproduce
Steps to reproduce the behavior:
Following the Readme.md, but fixing the URL:

git clone https://github.com/nix-community/todomvc-nix
cd todomvc
nix develop
This fails with:

%  git clone https://github.com/nix-community/todomvc-nix
Cloning into 'todomvc-nix'...
remote: Enumerating objects: 1165, done.
remote: Counting objects: 100% (763/763), done.
remote: Compressing objects: 100% (426/426), done.
remote: Total 1165 (delta 341), reused 649 (delta 250), pack-reused 402
Receiving objects: 100% (1165/1165), 9.83 MiB | 2.42 MiB/s, done.
Resolving deltas: 100% (516/516), done.
sloth% cd todomvc-nix
sloth% nix develop
error: flake 'git+file:///Users/dap/proj/todomvc-nix' does not provide attribute 'devShells.x86_64-darwin.default', 'devShell.x86_64-darwin', 'packages.x86_64-darwin.default' or 'defaultPackage.x86_64-darwin'
       Did you mean devShell

Expected behavior

System information

Same as in #185.
Additional context

This error is related to the nix-community/todomvc-nix repo, you can fill in an issue here instead: https://github.com/nix-community/todomvc-nix/issues


Spot Instances Not scaling

Description
Observed Behavior:
Upgraded to v0.33.0 and spot instances do not launch. I received the error
UnauthorizedOperation: You are not authorized to perform this operation. User: arn:aws:sts::1234567890123:assumed-role/my-cluster-karpenter-controller/1234567890 is not authorized to perform: ec2:CreateTags on resource: arn:aws:ec2:us-east-1:1234567890123:spot-instances-request/* because no identity-based policy allows the ec2:CreateTags action.

Expected Behavior:
Spot instances launch correctly when required.
Reproduction Steps (Please include YAML):

Created the IAM role from https://raw.githubusercontent.com/aws/karpenter-provider-aws/v0.33.0/website/content/en/preview/upgrading/v1beta1-controller-policy.json (I got to this URL by following the the v0.32.3 upgrade guide and then changing the URL for v0.33.0).
Deployed version 0.33.0
Created a node pool with only spot instance type
Created an EC2 Node Class

I don't use CloudFormation, I use Terraform. The documentation makes it very easy to use CF, but I have to interpret many different things for Terraform. So it's possible I did something wrong along the way. I could not readily find links to standalone IAM policy files and had to fumble my way through the process.
Node Pool setting used:
      - key: karpenter.sh/capacity-type
        operator: In
        values:
        - spot

OTHER INFORMATION:
Last time something similar happened to me, the issue turned out to be that I had grabbed the wrong version of the IAM policy. Please confirm that the IAM policy URL is correct and that there is not a newer version. Or if there is a version at an alternate location.
The issue was resolved for me when I changed these sections:
		{
			"Action": "ec2:CreateTags",
			"Condition": {
				"StringEquals": {
					"aws:RequestTag/kubernetes.io/cluster/my-cluster": "owned",
					"ec2:CreateAction": [
						"RunInstances",
						"CreateFleet",
						"CreateLaunchTemplate"
					]
				},
				"StringLike": {
					"aws:RequestTag/karpenter.sh/nodepool": "*"
				}
			},
			"Effect": "Allow",
			"Resource": [
				"arn:aws:ec2:us-east-1:*:fleet/*",
				"arn:aws:ec2:us-east-1:*:instance/*",
				"arn:aws:ec2:us-east-1:*:volume/*",
				"arn:aws:ec2:us-east-1:*:network-interface/*",
				"arn:aws:ec2:us-east-1:*:launch-template/*"
			],
			"Sid": "AllowScopedResourceCreationTagging"
		},
		{
			"Action": "ec2:CreateTags",
			"Condition": {
				"ForAllValues:StringEquals": {
					"aws:TagKeys": [
						"karpenter.sh/nodeclaim",
						"Name"
					]
				},
				"StringEquals": {
					"aws:ResourceTag/kubernetes.io/cluster/my-cluster": "owned"
				},
				"StringLike": {
					"aws:ResourceTag/karpenter.sh/nodepool": "*"
				}
			},
			"Effect": "Allow",
			"Resource": [
				"arn:aws:ec2:us-east-1:*:instance/*"
			],
			"Sid": "AllowScopedResourceTagging"
		},

to this value (I added "arn:aws:ec2:us-east-1:*:spot-instances-request/*" to both sections):
		{
			"Action": "ec2:CreateTags",
			"Condition": {
				"StringEquals": {
					"aws:RequestTag/kubernetes.io/cluster/my-cluster": "owned",
					"ec2:CreateAction": [
						"RunInstances",
						"CreateFleet",
						"CreateLaunchTemplate"
					]
				},
				"StringLike": {
					"aws:RequestTag/karpenter.sh/nodepool": "*"
				}
			},
			"Effect": "Allow",
			"Resource": [
				"arn:aws:ec2:us-east-1:*:fleet/*",
				"arn:aws:ec2:us-east-1:*:instance/*",
				"arn:aws:ec2:us-east-1:*:volume/*",
				"arn:aws:ec2:us-east-1:*:network-interface/*",
				"arn:aws:ec2:us-east-1:*:launch-template/*",
				"arn:aws:ec2:us-east-1:*:spot-instances-request/*"
			],
			"Sid": "AllowScopedResourceCreationTagging"
		},
		{
			"Action": "ec2:CreateTags",
			"Condition": {
				"ForAllValues:StringEquals": {
					"aws:TagKeys": [
						"karpenter.sh/nodeclaim",
						"Name"
					]
				},
				"StringEquals": {
					"aws:ResourceTag/kubernetes.io/cluster/my-cluster": "owned"
				},
				"StringLike": {
					"aws:ResourceTag/karpenter.sh/nodepool": "*"
				}
			},
			"Effect": "Allow",
			"Resource": [
				"arn:aws:ec2:us-east-1:*:instance/*",
				"arn:aws:ec2:us-east-1:*:spot-instances-request/*"
			],
			"Sid": "AllowScopedResourceTagging"
		},

Versions:

Chart Version: 0.33.0

❯ helm ls -n kube-system | grep karpenter
karpenter                       kube-system     10              2023-12-07 11:02:39.074263 -0500 EST    deployed        karpenter-v0.33.0                               0.33.0
karpenter-crd                   kube-system     9               2023-12-07 11:02:36.084741 -0500 EST    deployed        karpenter-crd-v0.33.0                           0.33.0

Kubernetes Version (kubectl version):

❯ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:20:07Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"28+", GitVersion:"v1.28.3-eks-4f4795d", GitCommit:"e77944ea667aee90c84c48a74a2a0da7a23e0508", GitTreeState:"clean", BuildDate:"2023-10-20T23:21:39Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/amd64"}

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Your policy looks right to me. This may be something that AWS support is better equipped to help with.

I do have the service linked role. I think that the file I grabbed is not the correct one. Meaning there are two copies out there of the IAM policy file and the one I grabbed is not correct. I checked the CloudFormation code for v0.33.0 and it already includes that missing "arn:aws:ec2:us-east-1:*:spot-instances-request/*" item in the resource list.

@ellistarn - I'm not sure this should be closed. I had to manually fix the policy file I downloaded from  https://raw.githubusercontent.com/aws/karpenter-provider-aws/v0.33.0/website/content/en/preview/upgrading/v1beta1-controller-policy.json
That policy file doesn't match what is available in v0.33.0 of the CloudFormation script. So I'm assuming that the CloudFormation script is accurate but the JSON file is not. Perhaps the controller policy file should be deleted or updated?
As a non CloudFormation user, I go to the non CloudFormation files first, and I'm sure there are many others out there in the same boat. Are there plans to get documentation that isn't CloudFormation focused so us non-CloudFormation users don't have to sort through JSON files and CloudFormation scripts to find correct information?

Sorry I misinterpreted your last message.

That policy file doesn't match what is available in v0.33.0 of the CloudFormation script. So I'm assuming that the CloudFormation script is accurate but the JSON file is not.

@jonathan-innis the issue for me was that I thought that if the file  at https://raw.githubusercontent.com/aws/karpenter-provider-aws/v0.33.0/website/content/en/preview/upgrading/v1beta1-controller-policy.json has v0.33.0 in the path, then it would be the exact same policy as the v0.33.0 CloudFormation policy file. How can you have a v1beta1 policy version v0.33.0 that is different then the published CloudFormation file? I can understand why v0.32.3 would have a different policy, it is an entirely different version.

Also, thank you @ellistarn and @jonathan-innis for the help with everything, appreciate the responsiveness / support, and appreciate you're having created / contributed to this package.
One last question for you - is there another place to look for the policy file outside of CloudFormation? Is that path documented and I just missed it?
Thank you again!

is there another place to look for the policy file outside of CloudFormation