json_to_sheet hanging when using large JSON file

I've got a fairly large JSON file I'm trying to write to a sheet. The file is ~353MB, with a length (when stringified) of 361,514,182.
It just hangs. I can get it working by chunking the Object and writing it to different sheets, but I can't write it all to a single sheet. I've also tried appending the chunks to the bottom of the sheet, but that also fails once it get's to the "latter" chunks.
I've just tried moving from v0.17 to 0.18 to see if that helps, but also no luck.
Running Node 16.15.1, Windows 11. Any ideas or workarounds? It's annoying having to manually open the files and paste the sheets back together.
Perhaps also worth noting that since the move to 0.18, the filesize has gone from 37MB to 98MB.

You might be running into https://bugs.chromium.org/p/v8/issues/detail?id=6696
Try passing the option dense: true to json_to_sheet or aoa_to_sheet.

Thanks for the suggestion! Tried this let ws = XLSX.utils.json_to_sheet(fullResult, { dense: true }) but it still hangs.
I don't even see a reference to dense in the docs! I moved back to v0.17.5
on account of the file size issue, is that an option for 0.18 only?
On Sat, Jul 30, 2022 at 2:12 PM SheetJSDev @.***> wrote:

You might be running into
https://bugs.chromium.org/p/v8/issues/detail?id=6696
Try passing the option dense: true to json_to_sheet or aoa_to_sheet.
—
Reply to this email directly, view it on GitHub
https://github.com/SheetJS/sheetjs/issues/2750#issuecomment-1200268577,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3TZY6K27TSTWUJFMJPGN3VWVWCVANCNFSM545Z3FZQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

The worksheet representation has a long history.  We compared the hash vs array of arrays back in 2012 and found that IE6 performed much better with the Object.  V8 also performed better with the object approach until some major changes under the hood heavily penalized large objects.
After V8 regressed, with no sign of improvement from Google's side, we revisited the array of arrays approach.  That's what dense enables.  Changing the default representation will require a major version bump.
If you are using compression: true and seeing a jump in file size, it's because we fully switched the ZIP engine and the sliding window hasn't been optimized
Can you give a rough estimate for the number of rows in the object?  If you could find a way to share the data, that would also be helpful

Ahh IE6, to blame for so many things! ;)
In this particular case I really can't share the data because it's confidential, but I'll try and provide as much detail as possible outside the actual data.
It's a data pull from a number of data sources that are processed and put together as an array of objects. The most recent one, run just this afternoon is 269496 rows total - and array of that many objects.
While not every object contains every one of these keys, most do. I've changed the actual name in most cases, but this is a list of name and type:
UniqueID	number
Study Name	string
Modified By	string
Country	string
Language	string
Target	string
Category	string
Parent Category	string
Segment	string
Filter Type	string
Filter	string
Product	string
Description	string (longer)
Image URL	string
File Name	string
File Size	string
Tags	string
KnownTag	string
KeyTag	string
Population	number
Group	string
Status	string
Created	date
productId	number
result1	decimal
result2	decimal
result3	decimal
quad	string
index	number
keyscore	number
keyscore2	number
check	string

To be clear, I saw the jump in size (roughly x3) with compression: true in v0.18. I dropped back to .17 and it went back to normal size - approx 36MB.

Got the same error on json_to_sheet function with 421060 rows and 20 columns. it stuck almost an hour with no output
Any help?

Is there any debug mode so that I can able to see any progress and where it is stuck?

Please test with 0.19.0.  Both json_to_sheet and aoa_to_sheet accept dense: true.
Without using zip compression: https://jsfiddle.net/Lphbt2qj/
const XLSX = require('xlsx'); // nodejs
const data = Array.from({length:421060}, (_,i) => Array.from({length:20}, (_,j) => j == 0 ? "" + i : i+j));
console.time('write');
const wb = XLSX.utils.book_new();
const ws = XLSX.utils.aoa_to_sheet(data, {dense: true});
XLSX.utils.book_append_sheet(wb, ws, "SheetJS");
XLSX.writeFile(wb, "issue2750.xlsx");
console.timeEnd('write');

takes 15 seconds to write a 265MB XLSX file.
Enabling compression: https://jsfiddle.net/et0pbrv8/
const XLSX = require('xlsx'); // nodejs
XLSX.CFB.utils.use_zlib(require('zlib')); // nodejs using native zlib
const data = Array.from({length:421060}, (_,i) => Array.from({length:20}, (_,j) => j == 0 ? "" + i : i+j));
console.time('write');
const wb = XLSX.utils.book_new();
const ws = XLSX.utils.aoa_to_sheet(data, {dense: true});
XLSX.utils.book_append_sheet(wb, ws, "SheetJS");
XLSX.writeFile(wb, "issue2750.xlsx");
console.timeEnd('write');

takes 22 seconds in NodeJS to generate a 30MB file, 22 seconds in Chrome to generate a 79MB file.
For exports in this scale, it is highly encouraged to generate a blob URL in a web worker and perform the download dance in the renderer thread.  The docs site has an example

json_to_sheet( data, { dense:true } ) hangs with 766734 rows. on 0.19.1
Unless there's a workaround or a fix for this issue, are the limitations mentioned somewhere?

https://docs.sheetjs.com/docs/miscellany/errors#aw-snap-or-oops-an-error-has-occurred
That said, the current limits apply on a per-worksheet level.  The limit is driven by how the worksheet is written (a large string is constructed).
For the maximum worksheet rows (1048576 rows), you can write 10 columns (https://jsfiddle.net/L462gdjy/ demo)
For sheets with a small number of strings repeated many times, bookSST reduces size by de-duplicating text using the shared string table.


Bidirectional copy?

I think it would be useful (e.g. for building proxies) to have bidirectional copy implemented. Of course, one could do split() on two ios, then call copy() for each direction and finally join() resulting futures. There are some shortcomings with this approach:

One needs to write the code explicitly. Apart from having to type more code it decreases readability (it's easier to understand bidirectional_copy(io1, io2) than about five lines of code, especially assuming bidirectional_copy is as well-known function as copy is)
split() allocates (Arc<BiLock<_>)
The operation involves locking and could cause slow down. Bidirectional copy could avoid it.

Of course, maybe bidirectional_copy isn't the best name. I don't care much about the name as long as it will be readable.

You may want to take a look at https://github.com/tokio-rs/tokio-socks5, which has an example of how to do this.

Basically it just leverages the fact that &TcpStream: Read + Write, so the reference is held in two futures and those two futures use copy basically

If we can strike the right abstraction I think it'd be worth it, but I'm not 100% sure what that would be offhand

Closing due to inactivity. If anyone has further ideas re: this, lets open a new issue and reference this one. Thanks!


Now that these assertions run, they sporadically fail :bomb:

Before cb47c448822, the assertions below weren't running since we
weren't populating the initial records.  Now, they fail sporadically.
We'll need to come back to this as it's clear they are leaving around
state in the slave and master database.

No good deed goes unpunished ----> #5373

This is a general problem with replication specs because they leave the database in a dirty state.  This happens because they don't run in the same process, and thus can't rollback.
In the past we only had 1 test (so not a problem), then when the second test came I guess it wasn't running :/
Let's talk tomorrow on how to make the replication specs Just Work :tm:

Yes, exactly @Fryguy, I started trying to fix it for real[1] but it still didn't work so I decided to just fix the sporadic failure for now by disabling the assertions that weren't running before #5373.
[1]
diff --git a/spec/replication/evm_dbsync_spec.rb b/spec/replication/evm_dbsync_spec.rb
index 47d6b2f..8b7c08f 100644
--- a/spec/replication/evm_dbsync_spec.rb
+++ b/spec/replication/evm_dbsync_spec.rb
@@ -20,9 +20,15 @@ describe "evm:dbsync" do
     @master_connection = MasterDb.connection

     @slave_connection = ActiveRecord::Base.connection
+    @tables_to_cleanup = Set.new
   end

   after(:each) do
+    unless @tables_to_cleanup.empty?
+      sql = "TRUNCATE #{@tables_to_cleanup.to_a.join(",")}"
+      @slave_connection.execute(sql)
+      @master_connection.execute(sql)
+    end
     Object.send(:remove_const, :MasterDb)
   end

@@ -51,6 +57,7 @@ describe "evm:dbsync" do
   it ":replicate_backlog" do
     run_initial_sync
     MiqServer.my_server.update_attribute(:version, "xxx")
+    @tables_to_cleanup << "miq_servers"

     expect {
       run_rake_via_shell("evm:dbsync:replicate_backlog")
@@ -78,6 +85,7 @@ describe "evm:dbsync" do
         manager.into(arel_table)
         manager.insert(fields)
         @slave_connection.execute(manager.to_sql)
+        @tables_to_cleanup << t unless t.starts_with?(@rr_prefix)
       end
     end
   end


[FEATURE] Web login should use 2fa

🚨🚨 Feature Request

[ ] Related to an existing Issue
[ ] A new implementation (Improvement, Extension)

Given the present situation on the web, I believe all websites that try to provide “trustworthy” services should use 2fa or Mfa. Some 2fa (as minimum) solution should be implemented, like Time-based One-time Password and/or HMAC-based One-time Password. Use something readily available, like some authenticator app (Google Authenticator).
I like U2F-keys (now FIDO2), but that is just me…
Perhaps I've overlooked something, and this is already implemented, I'm new to this site.

Completely agree on this side. Currently the username/password is not stored. They are used for authenticating a session token. However, even so username/password should be removed.

Not sure if I understand you, but a 2fa auth is typically done with a password and an authenticator, not the authenticator alone. Also when I write web login I was thinking about the https://app.activeloop.ai site.
S3 has support for Mfa, so in the lib it should be fairly easy to allow use of additional tokens.
When you use 2fa (or Mfa) it is common to drop passwords and use simple pin-codes instead. I'm not a big fan of that, but hey, people do that! =)

Closing this due to inactivity, will reopen if theres widespread interest.


Bus error

Hi! I met a question about bus error using docker durring training. Someone online told me to modify num_workers to zero, but I do not know how to do this.
Here is the RuntimeError:
DataLoader worker (pid 20991) is killed by signal: Bus error. Details are lost due to multiprocessing. Rerunning with num_workers=0 may give better error trace.

The issue appeared when the model was saved at the end of iteration 5000. And I just fit the configuration in file "options/train/train_esrgen.json". Error occurred at Each time I operate to this point——validation.

I had same issue. @Dawsonpei Have you solved the problem？


Updating MVA to Microsoft Learn

MVA is being shuttered in favor of MS Learn. Correcting the branding.

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


feat(psp22 example): resolve vulnerabilities with OwnerRole and MinterRole

Introducing two new traits OwnerRole and MinterRole to protect the contract from security risks.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 51.60%. Comparing base (763c6cc) to head (2af6d70).

@@                       Coverage Diff                        @@
##           chungquantin/feat-psp22_example     #363   +/-   ##
================================================================
  Coverage                            51.60%   51.60%
================================================================
  Files                                   48       48
  Lines                                 4910     4910
  Branches                              4910     4910
================================================================
  Hits                                  2534     2534
  Misses                                2327     2327
  Partials                                49       49


Is the new tag version expected ?

Hello @hillu
I noticed that the last tag is of version: 1.3.1
While the previous one was v4.3.2
Is that expected ?

Yeah, I recently added a fix to the 1.x branch. The Go modules import logic should ignore the v1.3.1 tag if you use github.com/hillu/go-yara/v4 for imports.


feature comparision

what is the difference compared to ultimaterecyclerview

This kind of question is inappropriate for a project bug tracker. Personally, I don't really care to contrast this library with others, or to suggest one is better or worse for any reason. However, here is a revised project description for SuperSLiM, perhaps you can figure out the differences from that description.
'''
SuperSLiM provides a focused set of features centered around a logical presentation of data in a scrollable list. Specifically, it allows you to combine together different kinds of layouts in a single scrolling view. Each of these layouts is associated with a section (group of views provided by your adapter), and each section can have a header. There are various customisation options for the headers and layouts.
'''


Prefer ipv6 over ipv4

Hey,
Is there a way to set that Ipv6 would be preferred to ipv4?
If I bring up a container I get that unless spefied (or ipv6-only site) ipv4 is used:
ping www.google.com
PING www.google.com (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=110 time=69.688 ms

Only if I force ipv6 it uses it:
/ # ping -6 www.google.com
PING www.google.com (2a00:1450:4001:80f::2004): 56 data bytes
64 bytes from 2a00:1450:4001:80f::2004: seq=0 ttl=116 time=59.688 ms

Its like this for every container I tried.
docker-compose:
  ipv6:
    image: robbertkl/ipv6nat
    container_name: ipv6nat
    restart: always
    network_mode: "host"
    privileged: true
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /lib/modules:/lib/modules:ro
networks:
  default:
    enable_ipv6: true
    driver: bridge
    driver_opts:
      com.docker.network.enable_ipv6: "true"
    ipam:
      driver: default
      config:
       - subnet: fd00:0000:0000:1::/64

/etc/docker/daemon.json:
 {
          "ipv6": true,
          "fixed-cidr-v6": "fd00::/80"
}

$ sudo docker version
Client: Docker Engine - Community
 Version:           20.10.10
 API version:       1.41
 Go version:        go1.16.9
 Git commit:        b485636
 Built:             Mon Oct 25 07:42:19 2021
 OS/Arch:           linux/arm
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.10
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.9
  Git commit:       e2f740d
  Built:            Mon Oct 25 07:40:35 2021
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.4.11
  GitCommit:        5b46e404f6b9f661a205e28d59c982d3634148f8
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Thanks

You can use the subnet 2001:db8::/64
The containers will prefer IPv6 over IPv4

@vNa3006 The subnet changes the preference?
From what I understand that is an address block used for documentation examples:
https://en.wikipedia.org/wiki/IPv6_address#Special_addresses

Yes, I don't know why it works that way, but when you use 2001:db8::/64, the containers will prefer ipv6

I probably want though a subset not used for documentation :)
Any other blocks or explanation why?

I haven't tried anything else yet. I'm OK with that subnet for now.

From #ipv6 on librechat I was updated that what sets the priority is /etc/gai.conf (getaddrinfo). I am not sure how to use it though

You can backup the gai.conf file, then replace the content of the file to
label ::1/128       0
label ::/0          1
label 2002::/16    2
label ::/96         3
label ::ffff:0:0/96 4
label fec0::/10     5
label fc00::/7      6
#label 2001:0::/32   7
It should work also

@vNa3006  Does this go in the container? host? or the docker-ipv6nat container?
Does not seem to work in the container.

I've just tested with a clean ubuntu container, it works right after editing the gai.conf file without restarting the container.

For posterity sake, this is a quirk of glibc: https://codebrowser.dev/glibc/glibc/sysdeps/posix/getaddrinfo.c.html#1234.
It explicitly ignores ipv6 standards and returns ipv4 addresses first when using ULA addresses. The assumption is "ipv6 will never be NAT'd" :). This ignoring the RFC has caused many headaches.
That's why 2001 works. But ipv6nat only NATs ULA addresses, so I'm not sure how you're using the container.

@jsravn Thankgs for digging in and finding the root cause.
Its not that they don't expect ipv6 to be nated. More the logic is "if we have a ipv6 local address then we expect that we have only ipv6 locally and not globally".
So they will only route IPv6 if if there is a global address to the device.
Because the situarion of a local ipv6 and no global ipv6 is more common.
And the workaround we are doing is assigning a global address to make glibc think it has a global address and route correctly.
Sounds like a reason to file a bug on glibc:
https://sourceware.org/bugzilla/

I doubt they would change it at this point. I also noticed RFC 6724 updates the source selection logic to follow what glibc does - so it seems it will become the standard soon. As a result, seems like the "use example range" hack is going to be codified into ipv6 for all of time :).


Made some changes on my side.

@vitas-ai  can you pull from speechbrain/develop so this PR has less clutter ?

I did that, hence there is so much clutter ;-)
The dynamic_libri branch was outdated, so I fetched from dev and we set the PR to dev in the speechbrain repo (instead of to the dynamic_libri branch).


Add Sys.plan () function, to display plans from the shell

Add Sys.plan () command, to display plans from the shell. The function displays the plan of the previously executed command.
For example,
= 1 + 2;
val it = 3 : int
= Sys.plan ();
val it = "TODO" : string

Fixed in 19b06e6596ee8f1fb6b00c6446ac0d62fa7dc299.


property ex:hasReusePotential in the Construction demo

In the construction demo we used the property 'ex:hasReusePotential'.
I suppose that you will  still add this property to the construction demo ontology.

We will see if the property is generic to be added in the value or cvn module.

ReusePotential could be some specific value


feat(ui): sidenav search

Sidenav Search
Type: Feature
Description: Implement search functionality for Sidenav conversations
User Story:
As a mission hero using LeapfrogAI UI, I want to search through my conversations so that I can find previous AI responses
References:
Acceptance Criteria:

[ ] Search filters conversations while typing
[ ] Search correctly filters conversations to only conversations with matching text

Checked the branch and it passes design review


Issue when passing arguments containing space and trailing backslash

Environment data

VS Code version: 1.33.1
Extension version (available under the Extensions sidebar): 2019.4.11987
OS and version: Win 10
Python version (& distribution if applicable, e.g. Anaconda): 3.7.2 64bit
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): na
Relevant/affected Python packages and their versions: na

Expected behaviour
All the arguments from the launch.json are passed to the lauched file as specified.
I.e. The output should be list of 3 items: program and two arguments in the example below.
Actual behaviour
The arguments get mungled up, when space and trailing backslash is used.
Only two items are produced in the list: program and 'merged' args
Steps to reproduce:
example.py:
import sys
print (sys.argv)

launch.json:
        {
            "name": "Argument handling issue example",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "args": ["C:\\path to\\arg1\\","arg2"],
            "console": "integratedTerminal"
        },

Run the launch configuration with the example.py.
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Empty

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
extensionHost.ts:215 Extension Host
extensionHost.ts:216 Debugger attached.

Output of integrated terminal:
PS C:\Users\XXX> cd 'c:\Users\XXX'; ${env:PYTHONIOENCODING}='UTF-8'; ${env:PYTHONUNBUFFERED}='1'; & 'C:\Python37\python.exe' 'c:\Users\XXX\.vscode\extensions\ms-python.python-2019.4.11987\pythonFiles\ptvsd_launcher.py' '--default' '--client' '--host' 'localhost' '--port' '49818' 'c:\Users\XXX\example.py' 'C:\path to\arg1\' 'arg2'
['c:\\Users\\XXX\\example.py', 'C:\\path to\\arg1" arg2']

Issue moved to Microsoft/vscode #73099 via ZenHub


Remove PASSIVE IRQL check for SOCK_ADDR implementation of bpf_is_current_admin()

Description
This PR removes the IRQL check for SOCK_ADDR bpf_is_current_admin helper function and allows it to be called at DISPATCH also.
Testing
Updated test to validate the DISPATCH irql results for the SOCK_ADDR helper functions.
Documentation
NA

Does the test actually call it at both DISPATCH and PASSIVE? Or is there a test gap?

Yes the test already invokes the callout (and the eBPF program) at both DISPATCH (for UDP socket) and PASSIVE (for TCP). Earlier the test did not validate the helper function result in case of DISPATCH (which was for UDP). This PR now changes it to validate the result for all the socket types.


undefined method `keys' for nil:NilClass

After install gem and rails g react_webpack_rails:install I have this error:
undefined method `keys' for nil:NilClass

on this line
= javascript_include_tag 'application'

Hi @kalashnikovisme
which  version of Rails? 4,5?

@mxaly Rails 4.2.3

Checking this with fresh app. Can you also share your application.js content?
Is it failing when you will remove
//= require react_integration
//= require react_bundle

from it?

It works fine @kalashnikovisme  for new rails 4 app.
Please make sure that this error wasn't there before generating. If it wasn't and you sure that it's related with our gem, let me know pls.

@mxaly

I haven't this error before.
It's failing after remove

//= require react_integration
//= require react_bundle

Stack trace

NoMethodError - undefined method `keys' for nil:NilClass:
  react-rails (1.3.1) lib/react/jsx/babel_transformer.rb:8:in `initialize'
  react-rails (1.3.1) lib/react/jsx.rb:19:in `transform'
  react-rails (1.3.1) lib/react/jsx/template.rb:13:in `evaluate'
  tilt (2.0.1) lib/tilt/template.rb:96:in `render'
  sprockets (3.4.0) lib/sprockets/legacy_tilt_processor.rb:25:in `call'
  sprockets (3.4.0) lib/sprockets/processor_utils.rb:75:in `call_processor'
  sprockets (3.4.0) lib/sprockets/processor_utils.rb:57:in `block in call_processors'
  sprockets (3.4.0) lib/sprockets/processor_utils.rb:56:in `call_processors'
  sprockets (3.4.0) lib/sprockets/loader.rb:134:in `load_from_unloaded'
  sprockets (3.4.0) lib/sprockets/loader.rb:60:in `block in load'
  sprockets (3.4.0) lib/sprockets/loader.rb:318:in `fetch_asset_from_dependency_cache'
  sprockets (3.4.0) lib/sprockets/loader.rb:44:in `load'
  sprockets (3.4.0) lib/sprockets/cached_environment.rb:20:in `block in initialize'
  sprockets (3.4.0) lib/sprockets/cached_environment.rb:47:in `load'
  sprockets (3.4.0) lib/sprockets/bundle.rb:23:in `block in call'
  sprockets (3.4.0) lib/sprockets/utils.rb:183:in `dfs'
  sprockets (3.4.0) lib/sprockets/bundle.rb:24:in `call'
  sprockets (3.4.0) lib/sprockets/processor_utils.rb:75:in `call_processor'
  sprockets (3.4.0) lib/sprockets/processor_utils.rb:57:in `block in call_processors'
  sprockets (3.4.0) lib/sprockets/processor_utils.rb:56:in `call_processors'
  sprockets (3.4.0) lib/sprockets/loader.rb:134:in `load_from_unloaded'
  sprockets (3.4.0) lib/sprockets/loader.rb:60:in `block in load'
  sprockets (3.4.0) lib/sprockets/loader.rb:318:in `fetch_asset_from_dependency_cache'
  sprockets (3.4.0) lib/sprockets/loader.rb:44:in `load'
  sprockets (3.4.0) lib/sprockets/cached_environment.rb:20:in `block in initialize'
  sprockets (3.4.0) lib/sprockets/cached_environment.rb:47:in `load'
  sprockets (3.4.0) lib/sprockets/base.rb:66:in `find_asset'
  sprockets (3.4.0) lib/sprockets/environment.rb:30:in `find_asset'
  sprockets (3.4.0) lib/sprockets/base.rb:92:in `[]'
  sprockets-rails (2.3.3) lib/sprockets/rails/helper.rb:230:in `lookup_asset_for_path'
  sprockets-rails (2.3.3) lib/sprockets/rails/helper.rb:190:in `check_errors_for'
  sprockets-rails (2.3.3) lib/sprockets/rails/helper.rb:137:in `block in javascript_include_tag'
  sprockets-rails (2.3.3) lib/sprockets/rails/helper.rb:136:in `javascript_include_tag'
  app/views/layouts/application.html.slim:7:in `_app_views_layouts_application_html_slim__2375968872894422707_52819900'

react-rails gem working fine in app. Version 1.3.1. May be I should update it?

@kalashnikovisme react_webpack_rails is a alternative for react-rails. It's not made to work together with it.
If you want, please describe what is your goal here. Maybe i can help solving it.

Or we can try some sort of screen-share (skype/hangouts) - i'm happy to help:)

@mxaly after remove react-rails from Gemfile this error has disappear.
Please, add note to Readme or docs about incompatibility with react-rails gem.
If any other issue will appear, I'll create new issue for this. Thank you!


How to use tournamenter?

There is only little documentation for how to start the app and it doesn't work for me: I've installed tournamenter with npm and run tournamenter. The application prints the configuration parameters to the screen and then exit, without binding to the given port (which is the default 3000).
Also installng the given debian package in a docker doesn't help, this time running tournamenter-app does not print anything to the console and exits.
How should I do to get it started?

Hi @trenta3 !
Thanks for reaching out.
Currently, you can install and run Tournamenter trough the Tournamenter App:

https://github.com/TendaDigital/TournamenterApp
http://tournamenter.tenda.digital/

Also, I'm attaching a Manual used in Brazilian Robotics Olimpiad. It's in portuguese but you can try to translate:
https://drive.google.com/file/d/0B49WoqW-RRLkWDJ2MEJFMlBLd00/view?usp=sharing

Thank you for the reply, I will have a look at it!


Add dependencies for services in docker-compose.yml

Dependencies will solve problems with preterm requests to services, logs will be more clean

I agree with this change and do the same in all my Compose files as a best practice. It's worth noting that this only verifies that a container has been started, not that it is available and accepting connections. However, I think adding the necessary heartbeat checks to Postgres, etc would make this file needlessly busy, since it is intended to be a skeleton.
If @brocaar agrees with this change, can you also update the -env file as well?

Okay, I will update also -env.yml and update PR

Good, I will wait while @brocaar agree with this PR
Thanks for a quick answer

Thanks @nibbl! :+1:


Implement error message when JSON is invalid syntax

@samejr has helpfully created a ToastPopover UI element that is ready to use for this issue in the toast-ui branch. What we'd like to happen is if there is a JSON parsing error we should show this an error that displays the parsing error message in a toast (using the above UI component).  You would need to update the createFromUrl.ts action function to catch JSON parsing errors and redirect back to the root "/" path and store the toast message in a cookie (see this remix example for an example.

Can you provide more information, I think this could be within my abilities to complete for hacktoberfest :)

@kubahasek just added some more info the issue description, hope that helps!

@ericallam Hi there? I've had a look at the codebase briefly, but I am having trouble understanding where the error occurs? I understand that it redirects when it cannot parse the JSON provided, but don't know where parsing errors should occur. I've had a look at the jsonDoc.server.ts and the corresponding functions, but that didn't really help me.
Could you please point me in the right direction on where the parsing happens/error occurs. Thank you!

To start I think we need to extend the createFromUrlOrRawJson function to actually parse the raw JSON, that way we can catch the parsing error either in that function or in the createFromUrl action

Alright, so I´d add JSON.parse() in the raw JSON part, then wrap the function call in createFromUrl in a trycatch. Should I be doing that for parsing from a URL too?

@ericallam Hi again, I have succesfully gotten the cookie part working, but right now I am having trouble showing the toast on the homepage, since Remix doesn't re-render it. Somehow the loader runs (verified that with a console.log()), but UI isn't rerendering.
export async function loader({ request }: { request: Request }) {
  const cookie = request.headers.get("cookie");
  const session = await getSession(cookie);
  const errorMessage = session.get("errorMessage");
  if (!errorMessage) {
    return {};
  }

  return json(errorMessage.error, {
    headers: { "Set-Cookie": await commitSession(session) },
  });
}
export default function Index() {
  const data = useLoaderData<LoaderData>();

  return (
    <div className="overflow-x-hidden">
      {data.errorMessage && <ToastPopover message={data.errorMessage} />}
      <HomeHeader />
      <HomeHeroSection />
      <GithubBanner />
      <HomeInfoBoxSection />
      <HomeEdgeCasesSection />
      <HomeSearchSection />
      <HomeCollaborateSection />
      <HomeFeatureGridSection />
      <HomeFooter />
    </div>
  );
}

This is the code I am trying to use to display it at the moment, but I cannot seem to figure out how to do it, sorry.

Can you link me to your repo/branch and I'll take a look

https://github.com/kubahasek/jsonhero-web/tree/toast-ui here you go


chore(docker): configure better container networking in dev env

@DaTebe @jbuese
i think i have found a valuable solution to make our dev lives easier, with just two ENV's. Add to your local .env:
DOCKER_IP=<IP_ADDRESS> # docker network inspect bridge --format='{{( index .IPAM.Config 0).Gateway}}'
DIVA_HOST=diva

And map diva to localhost IP in your etc/hosts. This make all the communication happen on the same diva host, no matter how the services are running, host name will always resolve to the right IP


[Hacktoberfest] A set of functions for AI Agents

Task
Implement a set of functions for AI Agents in JavaScript SDK.
Follow similar pattern as in the Python SDK.
Here are the Python SDK docs that cover AI Agents functions.
Deliverables
Create a PR to this repository with the implementation.
:loudspeaker: Additional rewards :trophy:
This issue brings up to :five:  :zero:  points for SWAG and entry into the draw for a  :point_down: :

:three:  :x:   :computer:  Razer Blade 16 Gaming Laptop
:shirt: :bear:  MindsDB Swag

:information_source: For more info check out https://mindsdb.com/hacktoberfest :point_left:

I would like to work on this issue.

@md-abid-hussain hey are you making progress on this?

Yes I'm working on it. It will be done by tomorrow.


Get data from JSON Websocket Viewer

Dear Jebej,
I am working with Leap Motion. In my research, I want to connect multiple leap motion, but the problem is I don't know how to get data from this one. Since I use Matlab Websocket to get data from JSON Websocket Viewer, but when I perform follow your instructions It just displays the received message. I can not put the data into the file (.txt or .xlsx something like that)
Below is the link I use to describe the problem
https://drive.google.com/drive/u/0/folders/1U6nJTQiCLMAf-BO2N2PKhPG5Poi4i_Yf
Please help me to solve it.
Thank you very much

You will have to program a client class which does what you want upon receiving the data. Read the usage section in the readme and let me know if you have a more concrete question after.


Sometimes forgets types when importing via properties when using NODE resolution

When importing types using NODE resolution (i.e., via require(…)), Closure Compiler in some cases recognises the resulting types and in other cases does not.  Consider:
types.js:
/** @constructor */
function Public() {}

/** @constructor */
Public.SubType = function() {};

/** @constructor */
function Private() {}

exports.Public = Public;
exports.testOnly = {Private};

test.js:
const {Public, testOnly} = require('./types.js');
const {Private} = testOnly;

let /** !Public */ pub;  // OK
let /** !Public.SubType */ sub;  // OK
let /** !Private */ private1;  // WARNING: Unknown type Private
let /** !testonly.Private */ private2;  // WARNING: Unknown type testOnly.Private

Output (v20210406):
$ google-closure-compiler -O=ADVANCED_OPTIMIZATIONS --module_resolution=NODE --process_common_js_modules types.js test.js --entry_point=test.js
test.js:6:9: WARNING - [JSC_UNRECOGNIZED_TYPE_ERROR] Bad type annotation. Unknown type Private
  6| let /** !Private */ private1;  // WARNING: Unknown type Private
              ^

test.js:7:9: WARNING - [JSC_UNRECOGNIZED_TYPE_ERROR] Bad type annotation. Unknown type testonly.Private
  7| let /** !testonly.Private */ private2;  // WARNING: Unknown type testOnly.Private
              ^

0 error(s), 2 warning(s), 100.0% typed

It's not really clear to me why it recognises Public.SubType as a type, but not Private.  I'm not sure if this is a bug report or a feature request, but it is certainly one or the other as the present behaviour is unhelpful (and in a slightly insidious way: I've just spent several hours tracking down a bug caused by a typo that I was very surprised hadn't been caught by Closure Compiler—but it turned out it had no idea what type was being returned by calls to the Private constructor in my test harness because it had completely failed to infer a type here, and manually adding a type declaration provoked the unexpected warnings shown above).

This might be requesting a new feature. I was able to use Private as a type inside test.js only if it's exported directly (like Public), but not when it's exported as a property inside an object (your example).
The guidance here does not restrict using the latter export pattern.
Closure compiler rewrites them differently, which somehow affects type resolution:
module$types.default.Public = function() {};

v/s
function Private$$module$types() {}
module$types.default.Private = {Private:Private$$module$types};

The rewriting of CommonJS modules is less than idea and there are several edge cases. The pass needs complete refactored and the bulk of the rewriting needs moved after type checking. This is a large effort I haven't had time to work on to date.

If you are using Closure Compiler mostly to type check NodeJS code (i.e. you don't need optimization or other Closure Compiler specific features), it might be worth considering TypeScript instead. TypeScript generally has better built out support for CommonJS.

If you are using Closure Compiler mostly to type check NodeJS code it might be worth considering TypeScript instead.

This is absolutely excellent advice, but in our case TS was not clearly going to win when we started, and even if we were starting again now we probably wouldn't go that route because our project:

is a sandboxed JavaScript runtime, and we want to be able to test it by having it execute itself recursively, and
is intended for running interactive educational JavaScript programming experiences, and we want users to be able to drill down through the entire codebase (their code, our application, the web server, and the underlying JS runtime); having them all written in JavaScript makes this much more tractable.

I'll leave it to @ChadKillingsworth to comment on the problem specifically and whether we'll get around to fixing it.
To manage expectations though, Google-internally we do not use CommonJS with Closure Compiler, so it's unlikely that we'll spend substantial time improving support for it.


Added query for e.touch in updateData function

Enabled touch events for drag

Very nice thanks a lot for the PR!


Add recipe for Solr 4

For a (Drupal) project we needed to integrate Apache Solr version 4 in our DDEV setup.
The recipe shows a simple example on how to run Solr version 4 in DDEV.

Thanks! Could you say a bit about how this is different from the canonical https://ddev.readthedocs.io/en/stable/users/extend/additional-services/#apache-solr?
Also, do you recommend updates to https://www.ddev.com/ddev-local/apache-solr-with-drupal-8-and-search-api-solr/ ?
If your recipe isn't explicit about supporting Drupal, please make it more explicit, as there are a lot of differences between supporting different CMSs.

Could you say a bit about how this is different from the canonical

Ah, of course. Totally forgot about this (though I copied it initially).
Well, the main difference is the core.properties file used in the PR. Instead of using "entrypoint" to create the core, it is automatically created using the data from core.properties. I haven't tested yet, if this is the case for newer versions of Solr, too.
Additionally the Solr configuration isn't copied on startup but it is directly linked from .ddev\solr\conf. I'm unsure if there are any downsides of this. At least it works in our project ...

Also, do you recommend updates to https://www.ddev.com/ddev-local/apache-solr-with-drupal-8-and-search-api-solr/ ?

Hm, not yet :) You highlighted the most important parts ("solr host" and name of the core) so I guess its understandable for users without any (or little) experience on how to setup Solr for Drupal.

If your recipe isn't explicit about supporting Drupal, please make it more explicit, as there are a lot of differences between supporting different CMSs.

Any hints on how to make this more explicit? I could add an example for the Search API Server configuration override:
/**
 * Override Solr connection.
 */
$config['search_api.server.solr_dev'] = [
  'backend_config' => [
    'connector' => 'standard',
    'connector_config' => [
      'host' => 'solr',
      'path' => '/solr',
      'core' => 'dev',
      'port' => '8983',
      'username' => '',
      'password' => '',
    ]
  ]
];

I guess I'm concerned that having worked through Solr before, this isn't nearly enough information to help somebody be successful.
For example, what Drupal module are you using it with? Why did it require Solr 4?

Looking forward to seeing this get in @stborchert - Shouldn't take but a couple of minutes...

Looking forward to seeing this get in @stborchert - Shouldn't take but a couple of minutes...

I was beating my head against a wall trying to get the 4.x image running using older recipes. This one fixed it right up and let me create a custom core by editing the properties file.
Documentation is clear and clean. Big thumbs up.

Oddly, however, Search API still says the core is unreachable.

A little late the the update party, but I think these changes would affect the solr-5 contrib as well, which I tried to modify without success.


fix deleting of messages w/o messageid

@keybase/react-hackers @gabriel

pushed w/o jenkins as jenkins is fuxxored


A never() expectation should fail immediately if called

Right now, it looks as if flexmock waits until tearDown to verify that a never expectation is met. However, since one doesn't usually specify a return value when declaring a never, other parts of the class under test are likely to raise an error (usually a NoneType AttributeError), masking the mock failure.
Since argument validations fail upon execution, it should be simple to have a never fail when called. In fact, this should probably be generalized to fail immediately whenever an at_most(N) expectation fails (since never is equivalent to at_most(0)).
Here's a contrived example:
class TestMe(object):

  def example(self):
    if self.some_condition():
      retval = some_module.do_some_work()
      return retval.exit_status()
    else:
      return

class TestMeTest(unittest.TestCase):

  def testExample(self):
    flexmock(some_module)
    some_module.should_receive('do_some_work').never
    TestMe().example()

This test errors out with an AttributeError (specifically 'NoneType'  object has no attribute 'exit_status'). It's much more useful to see a flexmock expectation failure here instead, especially when doing TDD.

Good idea, this has bothered me for awhile as well. Fixed in 79a71e612e47026cdd3158522f83c3b1b3410186, I'll cut a new release soon to include this fix as well as the couple other outstanding issues.


0 Active Connections to Ember Network

With the new wallet I am getting 0 Active Connections - see attached debug log
debug.log

Seems ok now

yes Ember Team in discord mentioned that it just takes time. Thanks to all the Ember Team for effort. Looking for a great 2018 with Ember


Adding a "select" filter

I wanted to add a new filter in your basic.js which would be a select type
so far I've added couple more checkboxes
FilterJS(services, "#service_list", {
template: '#template',
criterias:[
{field: 'amount', ele: '#price_filter', type: 'range'},
{field: 'status', ele: '#status :checkbox'},
{field: 'size', ele: '#size :checkbox'},
{field: 'length', ele: '#length :checkbox'}
],
search: { ele: '#search_box' }
});
now I would like to add a field that will filter by color
< select name="color" >
< option value="red" > Red </ option>
< option value="blue" > Blue </ option>
</ select>
and obviously added "color" : "red" and "color" : "blue" in JSON
I was wondering how do I add this in your js file?
I tried
{field: 'color', ele: '#color :select'} then
{field: 'color', ele: '#color :option'} then
{field: 'color', ele: '#color', type: 'select'} then
{field: 'color', ele: '#color', type: 'option'} and
{field: 'color', ele: '#color:select', type: 'option'}
but neither worked
Thanks so much in advance!

In the current version (2.1.0), the following syntax works for your example:
Provide your select with an ID attribute, in my case it's "color_filter" and then
FJS.addCriteria({ field: 'color', ele: '#color_filter' });


Added linux pakcages for x86_64 for 3006.8, 3006.9 and 3007.1

What does this PR do?
Adds Linux x86_64 onedir packages for Salt 3006.8, 3006.9 and 3007.1 for testing on Linux
What issues does this PR fix or reference?
Fixes https://github.com/saltstack/salt-vmtools/issues/3

Merging since Rocky Linux 9 is passing,
Waiting on Photon 5 container that we can test on
And Windows is still to be done.


Tasks 1344-1349

Reviews: swarooprm/CSE576HW#12

So there're a couple of comments That I couldn't fix by simple editing:

The QQP examples are not quite good paraphrases. Maybe they haven't been filtered to only include those that are annotated as paraphrases.
There're some weird texts in 1348 and 1349 which can be found by searching "entailment" in the files. I don't know what they are.


NIFI-5147 Implement CalculateAttributeHash processor

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] 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 file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing..

Tested out the HashAttribute processor. This all worked fine:

MD5 and creating a new attribute
MD5 and overwriting the attribute with hashed value
SHA256 and creating a new attribute
MD5 of chinese characters using UTF-8 (matched web tool hasher and command line md5 utility)

UTF-16 is where I came unstuck:

MD5 of simple string using "UTF-16" encoding, I get a different hash to what I expect.
MD5 of simple string using "UTF-16BE" and "UTF-16LE" encoding DO match what I expect.

Test input string in all cases: “hehe”
NiFi CalculateAttributeHash:
UTF-8:MD5       = 529ca8050a00180790cf88b63468826a
UTF-16BE:MD5 = b0ed26b524e0b0606551d78e42b5b7bc
UTF-16LE:MD5 = 2db0ecc27f7abd29ba95412feb3b5e07
UTF-16:MD5     = 9b6dcd3887ebdb43d66fb4b3ef9c259b
CyberChef (https://gchq.github.io/CyberChef/#recipe=Encode_text('UTF16BE (1201)')MD5()&input=aGVoZQ):
UTF-8:MD5       = 529ca8050a00180790cf88b63468826a
UTF-16BE:MD5 = b0ed26b524e0b0606551d78e42b5b7bc
UTF-16LE:MD5 = 2db0ecc27f7abd29ba95412feb3b5e07
I found that “UTF-16” is different because when encoding, Java adds a big-endian BOM: “When decoding, the UTF-16 charset interprets the byte-order mark at the beginning of the input stream to indicate the byte-order of the stream but defaults to big-endian if there is no byte-order mark; when encoding, it uses big-endian byte order and writes a big-endian byte-order mark.” As expected, adding the BOM changes the output bytes which are then hashed, resulting in a different hash to “UTF-16BE” encoding. Is this a problem or is this simply expected behaviour - ie. should the user realize that there will be a difference between UTF-16 and UTF-16BE encoding and the resulting hash?


Update Authentication Docs - rename loadRequest to load

This pr updates the docs for Authentication since the webview.loadRequest method was renamed to load

Is this mergable now?

Is this mergeable now?

yes its a simple change to docs to explain the new method to use as loadRequest is no longer supported.

Thanks for this!


fixes annoying directionallight rotation

gizmo still flickers a bit, but at least rotation is consistent. #206

Nice, works way better! Thanks!


NumPy 2 is not supported

We hit this issue locally. Took us a while to figure out a strategy to untangle this issue from the other #3... 😅
Using the Python 3.10 CI log from https://github.com/conda-forge/numpy-allocator-feedstock/pull/9, which uses NumPy 2 at build time
2024-10-07T01:39:12.5131564Z ## Package Plan ##
2024-10-07T01:39:12.5131783Z
2024-10-07T01:39:12.5133208Z   environment location: /home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place
2024-10-07T01:39:12.5133609Z
2024-10-07T01:39:12.5134974Z
2024-10-07T01:39:12.5135426Z The following NEW packages will be INSTALLED:
2024-10-07T01:39:12.5142863Z
...
2024-10-07T01:39:12.5163127Z     numpy:             2.0.2-py311h71ddf71_0      conda-forge
...

we see the following compile-time warnings:
2024-10-07T01:39:35.6192406Z   building 'numpy_allocator' extension
2024-10-07T01:39:35.6201840Z   creating build/temp.linux-x86_64-cpython-311
2024-10-07T01:39:35.6374655Z   /home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_build_env/bin/x86_64-conda-linux-gnu-cc -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/include -fPIC -O2 -isystem /home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/include -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/include -fdebug-prefix-map=/home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/work=/usr/local/src/conda/numpy-allocator-1.2.0 -fdebug-prefix-map=/home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place=/usr/local/src/conda-prefix -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/include -fPIC -I/home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/lib/python3.11/site-packages/numpy/_core/include -I/home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/include/python3.11 -c numpy_allocator.c -o build/temp.linux-x86_64-cpython-311/numpy_allocator.o
2024-10-07T01:39:35.7566917Z   numpy_allocator.c: In function 'handles':
2024-10-07T01:39:35.7572001Z   numpy_allocator.c:417:51: warning: implicit declaration of function 'PyArray_HANDLER'; did you mean 'PyArray_SHAPE'? [-Wimplicit-function-declaration]
2024-10-07T01:39:35.7574545Z     417 |                         PyObject *array_handler = PyArray_HANDLER((PyArrayObject *) array);
2024-10-07T01:39:35.7581257Z         |                                                   ^~~~~~~~~~~~~~~
2024-10-07T01:39:35.7594984Z         |                                                   PyArray_SHAPE
2024-10-07T01:39:35.7598005Z   numpy_allocator.c:417:51: warning: initialization of 'PyObject *' {aka 'struct _object *'} from 'int' makes pointer from integer without a cast [-Wint-conversion]
2024-10-07T01:39:35.7653414Z   numpy_allocator.c: In function '__exit__':
2024-10-07T01:39:35.7655017Z   numpy_allocator.c:474:33: warning: implicit declaration of function 'PyDataMem_SetHandler'; did you mean 'PyDataMem_DefaultHandler'? [-Wimplicit-function-declaration]
2024-10-07T01:39:35.7656847Z     474 |         PyObject *old_handler = PyDataMem_SetHandler(new_handler);
2024-10-07T01:39:35.7657592Z         |                                 ^~~~~~~~~~~~~~~~~~~~
2024-10-07T01:39:35.7659682Z         |                                 PyDataMem_DefaultHandler
2024-10-07T01:39:35.7660783Z   numpy_allocator.c:474:33: warning: initialization of 'PyObject *' {aka 'struct _object *'} from 'int' makes pointer from integer without a cast [-Wint-conversion]
2024-10-07T01:39:35.7662321Z   numpy_allocator.c: In function '__enter__':
2024-10-07T01:39:35.7663633Z   numpy_allocator.c:505:33: warning: initialization of 'PyObject *' {aka 'struct _object *'} from 'int' makes pointer from integer without a cast [-Wint-conversion]
2024-10-07T01:39:35.7671137Z     505 |         PyObject *old_handler = PyDataMem_SetHandler(new_handler);
2024-10-07T01:39:35.7679441Z         |                                 ^~~~~~~~~~~~~~~~~~~~
2024-10-07T01:39:35.7687281Z   numpy_allocator.c: In function 'set_handler':
2024-10-07T01:39:35.7719293Z   numpy_allocator.c:628:24: warning: returning 'int' from a function with return type 'PyObject *' {aka 'struct _object *'} makes pointer from integer without a cast [-Wint-conversion]
2024-10-07T01:39:35.7720481Z     628 |                 return PyDataMem_SetHandler(NULL);
2024-10-07T01:39:35.7722175Z         |                        ^~~~~~~~~~~~~~~~~~~~~~~~~~
2024-10-07T01:39:35.7754551Z   numpy_allocator.c:630:24: warning: returning 'int' from a function with return type 'PyObject *' {aka 'struct _object *'} makes pointer from integer without a cast [-Wint-conversion]
2024-10-07T01:39:35.7755729Z     630 |                 return PyDataMem_SetHandler(handler);
2024-10-07T01:39:35.7773779Z         |                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2024-10-07T01:39:35.7789118Z   numpy_allocator.c: In function 'get_handler':
2024-10-07T01:39:35.7794616Z   numpy_allocator.c:648:59: warning: initialization of 'PyObject *' {aka 'struct _object *'} from 'int' makes pointer from integer without a cast [-Wint-conversion]
2024-10-07T01:39:35.7806070Z     648 |                                 PyObject *array_handler = PyArray_HANDLER((PyArrayObject *) array);
2024-10-07T01:39:35.7816807Z         |                                                           ^~~~~~~~~~~~~~~
2024-10-07T01:39:35.7831997Z   numpy_allocator.c:663:24: warning: implicit declaration of function 'PyDataMem_GetHandler'; did you mean 'PyDataMem_DefaultHandler'? [-Wimplicit-function-declaration]
2024-10-07T01:39:35.7842678Z     663 |                 return PyDataMem_GetHandler();
2024-10-07T01:39:35.7855122Z         |                        ^~~~~~~~~~~~~~~~~~~~
2024-10-07T01:39:35.7866332Z         |                        PyDataMem_DefaultHandler
2024-10-07T01:39:35.7880791Z   numpy_allocator.c:663:24: warning: returning 'int' from a function with return type 'PyObject *' {aka 'struct _object *'} makes pointer from integer without a cast [-Wint-conversion]
2024-10-07T01:39:35.7884034Z     663 |                 return PyDataMem_GetHandler();
2024-10-07T01:39:35.7894052Z         |                        ^~~~~~~~~~~~~~~~~~~~~~

https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1047781&view=logs&j=4f922444-fdfe-5dcf-b824-02f86439ef14&t=937c195f-508d-5135-dc9f-d4b5730df0f7&l=844
and the import test fails
2024-10-07T01:39:52.7336944Z import: 'numpy_allocator'
2024-10-07T01:39:52.7340790Z Traceback (most recent call last):
2024-10-07T01:39:52.7341770Z   File "/home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/test_tmp/run_test.py", line 2, in <module>
2024-10-07T01:39:52.7342443Z     import numpy_allocator
2024-10-07T01:39:52.7343762Z ImportError: /home/conda/feedstock_root/build_artifacts/numpy-allocator_1728265022062/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_/lib/python3.11/site-packages/numpy_allocator.cpython-311-x86_64-linux-gnu.so: undefined symbol: PyDataMem_SetHandler
2024-10-07T01:39:53.5108629Z WARNING: Tests failed for numpy-allocator-1.2.0-py311h18e1886_2.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken

https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1047781&view=logs&j=4f922444-fdfe-5dcf-b824-02f86439ef14&t=937c195f-508d-5135-dc9f-d4b5730df0f7&l=1009
We can reproduce the missing symbol import error locally.
This is a blocker for CuPy to adopt support for using system memory on Grace Hopper (https://github.com/cupy/cupy/pull/8442). Would be nice to know how much work is needed so that we can discuss, coordinate, and maybe help too 🙂
cc: @emcastillo @seberg @mmccarty @rongou

This issue first appears in NumPy v1.25.0.
https://github.com/conda-forge/numpy-allocator-feedstock/pull/8#issuecomment-1745039892

I think it might be related to this commit:
https://github.com/numpy/numpy/commit/3a811358830c324b7b6819b88dec4e4bcd91444a#diff-d4fc38ad3fd8b43b6569ee82dbe5ba189619e0bc4898e7ab7f723d76a839f32fL370-R371

As it turns out:
NumPy 1.22 NPY_FEATURE_VERSION == 15
NumPy 1.23 NPY_FEATURE_VERSION == 16
NumPy 1.24 NPY_FEATURE_VERSION == 16
NumPy 1.25 NPY_FEATURE_VERSION == 13 (< 15)
NumPy 1.26 NPY_FEATURE_VERSION == 13 (< 15)
NumPy 2.0 NPY_FEATURE_VERSION == 14 (< 15)
NumPy 2.1 NPY_FEATURE_VERSION == 14 (< 15)
which breaks the following check:
#if NPY_FEATURE_VERSION >= NPY_1_22_API_VERSION
...
#endif

I was missing #define NPY_TARGET_VERSION NPY_1_22_API_VERSION. I will push the fix shortly.


[Feature Request] Add option to always show all buttons

I LOVE the look of this theme, but can't stand the only-visible-while-hovering buttons.
Could you add either an easily changeable option in the .css or compatibility with obsidian-style-settings to add an option to always show all buttons?

It won't be easy, though I'm planning to restyle them in the near future (not the visibility, they stay hidden). I'll try to include a convenient way to disable them through user's snippets.
Support for Style Settings will take a lot of time as I have to overhaul the elements, as this theme is a direct copy from the previous theme, not lots of things are bound together (link colors actually uses Obsidian's default color, which is similar to the folder color, but they aren't in sync)
I do plan to do it anyway, but may not come so soon.
If you need them immediately, I'll find a time this week and provide the code to disable them, though they may look very weird as some of the collides to each other

As a workaround until I solve the issue, you may use the following code in a snippet file and adjust them as you like:
/* Dock-Ribbon */
.workspace-ribbon{
	visibility:initial;
	position:initial;
	margin-top:35px;
	background:none!important;
}
.workspace-ribbon-collapse-btn,
.side-dock-actions,
.side-dock-settings{
	position:initial;
	opacity:1;
	padding:20px 6px;
}
.side-dock-settings{
	margin-bottom:40px;
	border:none;
}
.side-dock-settings:hover,
.side-dock-actions:hover{
	border:none;
}
.side-dock-ribbon-action{
	padding:10px 0;
}

/* Titlebar */
.mod-left-split,
.mod-right-split{
	padding-top:35px;
}
.titlebar-button-container{
	opacity:1!important;
}

/* Workspace tab */
.workspace-tab-header-container{
	position:initial;
	opacity:1;
	height:auto;
}

Works great, thank you!

As a new update is live, here's a new code to unhide the buttons until I start to support Style Settings! https://github.com/hydescarf/Obsidian-Theme-Mado-Miniflow/commit/fb013389f0585408ce22c65bdff929f2530ac8d1
/* Dock-Ribbon */
.workspace-ribbon{
	opacity:1;
}
body:not(.is-mobile) .side-dock-actions,
body:not(.is-mobile) .side-dock-settings,
body:not(.is-mobile) .workspace-ribbon-collapse-btn{
	opacity:1;
}

/* Workspace tab */
.workspace-tab-header-container{
	opacity:1;
}

/* Titlebar */
.titlebar-button-container{
	opacity:1!important;
}

/* File Explorer buttons */
.mod-left-split .workspace-leaf-content[data-type="file-explorer"] .nav-header{
	opacity:1;
}

The theme has updated to v1.0.0, and is now supporting Style Settings! All buttons can now be unhidden through it!

Awesome! <3


Skyline: fix a problem reading mz-only small molecule transition list…

…s with implied isotope labeling (that is, multiple precursor mz values for same charge) and unsorted precursor mz values. Skyline would become confused if first mz value was not smaller than all the others for the same molecule and charge.

@bspratt I thought you were going to try to get this into 19.2

I thought we weren't, but I certainly can if that's what we want.

My memory was that only the Explicit RT Window fix was waiting until next release and this one just required you to refresh and fix conflicts, but was fine to commit. Let's get the conflicts resolved and get it into master. Then we can decide about cherry-picking back to skyline_19_2, even though that is the wrong direction which I just said we would try to avoid.

If we want a clean cherry pick opportunity I should probably make a new branch for this. It's just two files changing but the tree is muddied now.

committed the salient changes to 19.2 branch, and cherry picked that to master.


Switch 2.0 branch workbench to <IP_ADDRESS>

Description
Switch 2.0 branch workbench to <IP_ADDRESS>
Issues Resolved
Part of https://github.com/opensearch-project/opensearch-build/issues/2086
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

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

Codecov Report

Merging #596 (f70dbee) into main (a7d4395) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #596   +/-   ##
=========================================
  Coverage     94.59%   94.59%
  Complexity     2743     2743
=========================================
  Files           276      276
  Lines          7455     7455
  Branches        551      551
=========================================
  Hits           7052     7052
  Misses          349      349
  Partials         54       54

Flag
Coverage Δ

query-workbench
62.76% <ø> (ø)

sql-engine
97.67% <ø> (ø)

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

Continue to review full report at Codecov.

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

also remove rc1 here https://github.com/peterzhuamazon/sql/blob/opensearch-2.0.0-ga-fix/workbench/opensearch_dashboards.json#L3?
{
  "id": "queryWorkbenchDashboards",
  "version": "<IP_ADDRESS>-rc1",
  "opensearchDashboardsVersion": "2.0.0",

Since I have opened an issue for your team https://github.com/opensearch-project/sql/issues/597.
I think I will leave you guys handle it 😄 .
This PR was created under the assumption that only a few dashboards plugin has the rc1.
Thanks.


Maximum bolus is ignored

I have maximum bolus in Loop set to 1U (and 6U on the pump itself) and was just able to do a 1.5U bolus from Loop.

I tested this by setting my max to 0.1u in app and giving myself a 0.2u bolus and it gave the bolus as well.

Yep – maxBolus is never used... 😊 https://github.com/loudnate/Loop/blob/master/Loop/Managers/DoseMath.swift#L131

Related to this would be great to validate carb entry, yesterday Sam by mistake keyed 5523 gr vs 55 and Loop suggested 553 units.


JSX parsing error

I'm not entirely sure what's causing the issue here:
This fails
function play(moves) {
    var game = gamelib.create();
    var player = gamelib.createPlayer();
    return moves.reduce(
        ([[g, p], [x, y]]) => gamelib.play(g, x, y, p),
        [game, player],
        moves
    );
}

This doesn't
([[g, p], [x, y]]) => gamelib.play(g, x, y, p),

Are you getting

Syntax error: Line 5: Unexpected token =>

?
We fixed this in 0e4014d2e0d4c024c3481acdad7e7a813195527b, but we haven't pushed out a new version yet. cc @jeffmo

Well, we tried to push out a version with that :P. Let's get #89 in, merge upstream, then get a new version published so jstransform (and thus react) can get the changes.

This seems like it works in v10


Double while causing performance issues

Double while in the fitext core needs to be replaced or be more strict to prevent infinite loops

6a08e35091f5c9def0f5c04b4fd527352af2b041 - Fix this issue


Use separate prefix inside AppDir/usr

You might have noticed that in the conda plugin, we use usr/conda/ as installation prefix. The reason is, conda ships libraries that might break other applications in the AppDir by e.g., clashing with libraries deployed by linuxdeploy normally.
I presume this plugin might be affected by that, too, since libraries are downloaded from the Internet and just put into the AppDir.
There's the unwritten rule that plugins shall not break each other and that different application types should be able to coexist in the AppDir. Therefore, I suggest you to use e.g., usr/python or usr/python<version>/ and put lib, share etc. into that instead of using usr/ directly.

Indeed :) Right now I'm spamming the usr/bin and /usr/lib spaces which was very convenient so far :P Doing as you say would allow several Python version to coexists as well, if needed. Yet, I first have to solve some issues that for, related to interporating with linuxdeploy. I'll submit them as questions on the linuxdeploy page.

Done with 6ec41569cda3e65640cb72cab566376e065d42a4. The python install has been rebased to AppDir/usr/python. A priori it should be possible to install multiple Python versions as well, since Python support this natively. Yet this was not tested.
In addition C-extension modules and packaged libraries (e.g. by Numpy) are patched as well. Libraries are symlinked to AppDir/usr/bin and the RPATH of C-extension modules points to AppDir/usr/bin (using a relative path). In both cases externals dependencies are packaged as well, except if in the AppImage exclusion list.


Add CSS3 pseudo class :invalid

This is a follow up to PR #325 to add support for the :invalid css pseudo class. I have implemented the unit test discussed in the comments of that PR.

Many thanks, a new release is planned for the upcomming weekend.


Are 8C tagged strings lenght encoded?

Given #5 it is possible for strings to contain \u0000 values. With that in mind should I assume all 8C tags length-encoded instead of zero-terminated? Would it make sense to have a separate tag for adding zero-terminated strings and for length-encoded strings to the LRU?

No, 8C tag is a separate byte that goes before any string value.


chore(main): release metamask-testing-tools 1.2.5

:robot: I have created a release beep boop
1.2.5 (2024-06-03)
Bug Fixes

fix metamask setup change and improve setup steps (91f223b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/hugomrdias/metamask/releases/tag/metamask-testing-tools-v1.2.5 :sunflower:


Decide on the way to display large text blocks in the metadata table

In the metadata table, there are some very long text fields such as an abstract, method, description etc. (Very long = comparable to an A4 page of text or more.)
We need to decide on one specific option to handle these:

Display as is → this causes each entry to be rather huge, so not really an option
Display as is but in smaller text → only provides a relief, not a solution, but maybe we can be made to work with good layout decisions
Do not display at all but still do full text search on the field → potentially a good way, but may be somewhat confusing for users
Display a certain number of characters and link to expand / show more / pop up on click
Do not display at all in normal mode; when searching with a sub-string, display only the matching part with the match highlighted in bold. This is potentially the best solution but quite tricky to implement, so probably not for the MVP phase.

There's also an option to do sensible aggregations on the abstract & method texts to still display them in the main table, but avoid having too long table.


Remove one of SparseFixedBitSet/DocIdSetBuilder.Buffer [LUCENE-10443]

SparseFixedBItSet is no longer used by DocIdSetBuilder, but the class didn't get cleaned up and removed.
We only need one sparse representation and don't need to just litter up the codebase with unnecessary classes.

Migrated from LUCENE-10443 by Robert Muir (@rmuir)

SparseFixedBItSet is no longer used by DocIdSetBuilder, but the class didn't get cleaned up and removed.

In main branch, SparseFixedBItSet is used by UnicodeProps, Lucene90OnHeapHnswGraph and DocValuesFieldUpdates. There are more usages in test related code also.
@rmuir Are you thinking to replace SparseFixedBItSet with DocIdSetBuilder.Buffer in the above classes ?


fix for the prefix restore issue

Problem statement: Backup and restore features do not work when index PREFIX is provided
Solution: Backup and restore methods are enhanced to handle PREFIX
Changes: The restore command is renamed to import and the rollback command to restore

In general I like using ${PREFIX} in strings instead of just $PREFIX since its "safer".
So is the prefix in all the file names now too?

In general I like using ${PREFIX} in strings instead of just $PREFIX since its "safer".
So is the prefix in all the file names now too?

will change the $PREFIX syntax to ${PREFIX}
Yea the prefix will be appended with the basename of all the file names: basename.prefix_index.json


Enables API2 for Observations to Send a Field Slip Code

coverage: 93.453% (-0.003%) from 93.456%
when pulling a032b1f30adf23c76e2b843d2d48d75f4f0f6c28 on njw-api2-code
into 8c9c7943ac8eee56f16fb8e3a10f97a4ace80dec on main.


Add automatic dialer open when clicking phone number when clicking the site

this will help users to call the phone umbers in a much more easier manner

PRs already exists at #49 and #53 covering different use cases.

oh ok


Fixed generated column defaul value

Problem:
We has some column in table:
repeat        "journalArchive_repeat_enum" default 'first'::"journalArchive_repeat_enum" not null,

and some related type:
create type "journalArchive_repeat_enum" as enum ('first', 'repeat');

While generating model class process returns error.
There were some problems with model generation for table:  journalArchive
SyntaxError: ',' expected. (29:80)
  27 | status:"done" | "error" | "cancel";
  28 |
> 29 | @Column("enum",{ name:"repeat",enum:["first","repeat"],default: () => "'first'"journalArchive_repeat_enum"", })
     |                                                                                ^
  30 | repeat:"first" | "repeat";

also typeorm fails attempts of loading default fields in column with single quotes, after tslint
default: () => '\'start\'',

Decision:
Checking string and numbers defaults and generating it as simple value of default field:
Result of generation:
default: 'start'

@Column('enum', {
	name: 'repeat',
	enum: ['first', 'repeat'],
	default: 'first'
})

Sorry for the delay I didn't have much time for OSS lately.
Could you provide reproduction data(e.g. DDL statements) for situation when current approach fails? It would allow me to add a test to make sure that this won't be broken in the future and make sure that implementation is as general as possible(doesn't break other config options).


[wip] doctor:servers task

This is a basic version of a doctor task that shows configured servers along with their roles & options.
There are some internal api changes (public access to Configuration#servers and a new public Server#to_h method).
This version doesn't display any warnings/highlighting yet. Original issue #1684 mentions a warning about roles with whitespaces. I didn't find any definite indication that this is problematic (it probably requires some more research from my side), I'll add it if needed.
I'll run through stack overflow capistrano problems, to look for inspiration for warnings in this task, but in the meantime this basic version can be reviewed.
Preview
![Feature preview]
(http://i.imgur.com/hZ5AyNd.png)

Wow, this is excellent work! Looks good as is, once a CHANGELOG entry is added.
Regarding the whitespace warning: this came up at least once before in an issue or in Stack Overflow. Ah, here it is: http://stackoverflow.com/questions/35718268/rails-assets-arent-compiling-after-capistrano-deployment/35732693#35732693
So it would be nice to have, especially since Capistrano users not familiar with Ruby syntax might easily mistake %w{} and %{}.
Also, what do you think of sorting the servers by hostname? Might be nice for deployments with dozens of servers.

Thanks for the feedback! That SO thread makes the case obvious indeed.
I've added this whitespace check, and the changelog entry.
Please let me know if the message is ok (eg. Whitespaces detected in role(s) :"app web". This might be a result of a mistyped "%w()" array literal.).
Preview
![Feature preview]
(http://i.imgur.com/0TV1nlh.png)

Looks great! See my two minor code comments.

Fixed and pushed.

Nice! ✨


Playground "format" feature has started formatting with tabs / 4 spaces for any file not App.vue

Vue version
Playground
Link to minimal reproduction
https://play.vuejs.org/#eNp9UU9LwzAU/yoxlyrMFdltdAOVgXpQUcFLLqN96zLTJCQvdVD63X1JabeD7BLyfn+S33uv4/fWztsAfMkLXzppkXnAYNdCy8Yah6xjDnasZztnGpaRNBNa6NJoj6zxNVtF/jp7AqUM+zZOVVfZjdBFPjxHD1GB0Fi1RaCKsWJ/t+66ZO77IqcqoVLbgKy9bUwFaiU48YITVeSTm884evp6J+v5wRtNqbvoFbw0jZUK3JtFSdEEX7LERG5LyX5fEoYuwGzEyz2UP//gB3+MmODvDjy4FgSfONy6GnCgN5+vcKT7RFLyoEh9gfwAb1SIGQfZQ9AVxT7TpbTPafZS119+c0TQfmwqBo3KPukFp308Xmj9FHcxXySf0D1NMXrGtZ9249IeKtmuizyeETiffv8HHOK5Cg==
Steps to reproduce
Go to link, select Comp.vue tab, and go rightclick -> Format Document
What is expected?
To format exactly the same as App.vue
What is actually happening?
Any file that is not App.vue such as Comp.vue or somefile.js or somefile.ts they all get formatted with either Tabs or 4 spaces,
But if you tried to force 4 spaces into App.vue and do format, it strips it back down to 2 spaces (my prefered)
It's very weird that ONLY App.vue formats in one way, and EVERY OTHER file formats with completely different settings.
System Info
No response
Any additional comments?
This taken a while for me to work out, I knew something weird was going on, so I stopped formatting files, but then I did it out of habit and then 'it worked again' so I started formatting again, and then 'it was broken again'..
It has been days of using the playground on and off to realise it was File Dependant for when formatting worked vs was broken.

Unable to reproduce from my side. Always 2 spaces for all the files.

Oh, this is weird, now that I have refreshed, it's no longer doing it my end either..
I will keep this open for a little while since it seems to be an intermittent thing and I obviously thought I caught the reason for it, but it's obviously deeper than that..
If I don't see it again after significant usage, I will close this.

It's been two weeks now. So, I'm closing this issue.
If you encounter similar issues again and can follow up with more information, please open a new issue with a reference to this one.


Fix for Issue #165 missing themes

This does the following:

Updates the list of themes for gitea and forgejo to match upstream
Moves the theme vars into per fork files
Loads the theme vars based on the value of the gitea_fork var
Updates the README section on default UI vars to match these changes

It's been tested:

running Ansible on a manjaro Linux host against a Debian 12 VM, with Forgejo as the specified fork.
Leaving the vars as default resulted in the correct forgejo-auto theme being used and fixed my original issue #165
A second run overriding gitea_theme_default to forgejo-dark in my local host_vars worked as expected.
The full list of themes was available in the Forgejo web UI user settings and worked when selected.

I have not yet tested Gitea and will likely not have time for several weeks.

I personally ignore yamllint errors about line length. Has no effect on functionality and editors can wrap.
Forgejo has a long list of themes. What can I do? I have no idea how to fix this in YAML and still leave it as a comma separated list of themes. Suggestions welcome.

Is it possible to have that action set line length to a warning instead of an error?

It seems ansible-lint treats all reports from yamllint as errors regardless of whether yamllint reports them as error or warning. Essentially ansible-lint is ignoring the yamllint config.
I think the solution may be to add line-length to warn_list in an .ansible-lint file? See ansible-lint docs.

Added yamllint magic comments to ignore line-length for the forgejo themes var. Like so:
gitea_theme_default: "forgejo-auto"
# yamllint disable rule:line-length
gitea_themes: "forgejo-auto,forgejo-light,forgejo-dark,gitea-auto,gitea-light,gitea-dark,forgejo-auto-deuteranopia-protanopia,forgejo-light-deuteranopia-protanopia,forgejo-dark-deuteranopia-protanopia,forgejo-auto-tritanopia,forgejo-light-tritanopia,forgejo-dark-tritanopia"
# yamllint enable rule:line-length

As a workaround. Now passes the ansible-lint action check.
Hope that is ok.


Network firewall requirements inbound rules are not required

Network firewall requirements inbound rules are not required

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

ID: a2c9767e-8558-7b76-fc26-34c4776f7bcf
Version Independent ID: f9853d6a-639a-c9df-a82c-01afdaf43edc
Content: Collect data in a hybrid environment with Azure Log Analytics agent
Content Source: articles/log-analytics/log-analytics-concept-hybrid.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

in the Network firewall requirements https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-concept-hybrid#network-firewall-requirements. the table mentions that the direction of the communicatoins are inbound and outbound while in other documentations (https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-om-agents) it says that the communications are outbound only.

@mabushaireh Thank you for the valuable feedback,we are investigating the issue.

@MGoedtel the document states firewall rules for inbound traffic, is that correct or is only outbound needed?

@mabushaireh @jason-j-MSFT - the firewall configuration details for the agent specified in the article - https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-concept-hybrid#network-firewall-requirements is correct.  If you are integrating OpsMgr with Log Analytics to collect data from agents reporting to that management group, the firewall configuration for that scenario is correct in this article - (https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-om-agents).  The distinction is integration - am I doing a direct-agent to the service where I am leveraging additional features such as monitoring/management solutions and integrating with other services like Automation, or leveraging my existing investment in OpsMgr and integrating it with LA in order to centrally manage and pull event/log/perf data to send to LA.  This allows you to augment querying/reporting/visualizing this telemetry with OpsMgr but also the ability to store longer term in Log Analytics versus OpsMgr DW at a possible cost advantage.
Hope that helps. #please-close


YAML examples

In addition to the comments in gitter, I think the folder structure isn't so helpful. All examples should be in one directory

This PR is falling behind PR #16 and is becoming a burden to maintain. As discussed with @kwhetstone and @gautamabhishek46 at the Monday meeting, we think it makes sense to close this PR and create a new one which aligns to the most recent view of the YAML based on PR #16. @oleg-nenashev and @grandvizier do you agree?

With no comments for several days, I move to close this.

I have added YAML examples as per the new YAML format. As this will be needed in the second phase evaluation presentation.

After merging PR #16 I am getting wired results while pushing other branches. I am closing this and will open another PR with all the examples for new YAML format.


Spacing between table cells on IE11

border-radius  of materialize.css  leads to small visible spaces between table cells on IE11:

Possible fix:
table td, table th {
    border-radius: 0;
}

I do not have any device that has Windows so that I am able to reproduce or fix that. If that seems like a proper fix please pull-request that.

border: none removes the whole border and therfore the table isn't stripped anymore. The 1-pixel vertical line is also gone if you set border-radius to 0

Fixed as in #6


Docs: 7-15 update

Published what's new for the week of 7-15

@ayeshakmaz is the wind beneath my wings.

@ponori Imma need GitHub to add more emojis ✈ 🦜


Hyperledger Fabric Builder for Kubernetes proposal

External builder enabling Hyperledger Fabric peers to launch containerized chaincode using Kubernetes.
Sponsor: @lehors

I support this as well

I've prepared a branch with the missing DCO sign-offs ready for if the proposal is approved...
https://github.com/jt-nti/fabric-builder-k8s/commits/labs-dco

I support this lab as well. This lab will complement fabric-operator to provide a complete kubernetes solution for base Fabric + Chaincode.


Create btk

http://www.btk.fi/ is the official website

@DewanWK I am sorry, the website suggests that Turku Centre for Biotechnology is primarily a research institutiuon, not educational one. This repository lists colleges and universities in order to provide free licenses to students and teachers.
If there is a number of researchers in Turku Centre for Biotechnology who in fact are students and wish to use JetBrains tools for educational purposes, there are no objections to include the domain into the repository.
However, we would like to ensure that people in the Centre know that free student licenses which JetBrains grants via this repository are for educational purposes only, not for performing paid research work.
Please let us know if the Centre has educational programs and students enrolled into them.

@DewanWK You may miss the previous comment. Please give us some update on the issue, otherwise I have to close the request without merging. You also can contact<EMAIL_ADDRESS>even if the Centre does not have educational programs, JetBrains sales team will try and help in getting the licenses in the way which is most appropriate for you. Thank you for your understanding!

@DewanWK I am really sorry that you do not have any updates. As I mentioned before, I close this request. I really hope that you can send your request to JetBrains sales team if researchers need the licenses, and to<EMAIL_ADDRESS>if you have some classes which the professors and the students need the licenses for. This repository rules do not allow to include research institutions domains if there is no regular educational courses offered  by the institution. Thank you for your understanding!


Generated dictionary sometimes includes word twice, once followed by a period

For example, here.

Minimal example that causes this bug:
misspellig.

* lowercase

The following does not trigger the bug:
misspellig.

* Uppercase

Hmm on the personal tiny spellchecker I made; I just flat out removed most punctuation from words that needed spellchecked. Could we do something like this here?

While removing periods, exclamation marks, and question mark nodes from words that need spellchecked ; it could probably be helpful here?

True, that would solve this problem. I'm hesitant to have spellchecker-cli preprocess text too heavily before passing it into Retext. For example, if we removed punctuation, that might conflict with one or more Retext plugins. I have an open issue for adding support for more Retext plugins to spellchecker-cli: #18
I'd rather resolve this issue by fixing the underlying issue in Retext or remark-retext.


[VS Code] You need to sign in before joining the collaboration session.

Error:
You need to sign in before joining the collaboration session.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.379

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.24.1

platformName
Linux

platformVersion
4.2.0-27-generic

@wellyandriani By design, joining a Live Share collaboration session implies a guest user has to be authenticated. Were you experiencing any problem with the sign-in procedure?

@wellyandriani I’m going to close this, since as mentioned, we currently require users to sign in before they can join a Live Share session. Please re-open this if you notice this error even after authenticating, since that would definitely be a bug. Thanks!


Add support for System.Diagnostics.Metrics

Background and Motivation
dotnet-monitor currently only supports collection of EventCounter metrics. Given that the dotnet team's recommendation is to use System.Diagnostics.Metrics for new metrics, we should expose via the /metrics endpoint as well
Proposed Feature
There currently isn't an out-of-process consumption mechanism for System.Diagnostics.Metrics and whatever we do will be dependent on a new runtime feature. It will probably be something similar to DiagnosticsSourceEventSource

More then one year and nothing?

I am glad to see this issue has not been closed, so there is hope it will be completed.  However, in the meantime, does anyone have a workaround? Our project is being deployed in Kubernetes. In our environment, I have to use Prometheus scrape.  Right now, this is working great for the dotnet-monitor metrics. However, I am missing a lot of other metrics exposed by our application or 3rd party libraries. I could use another sidecar that does metric aggregation. I have heard that the .NET API Gateway Ocelot can aggregate responses.  I was thinking it would be possible expose a /metrics endpoint (using OpenTelemetry) in our application and have Ocelot fetch both dotnet-monitor metrics and the application metrics to the Prometheus scrape endpoint. This a more complicated than it really should be.
Does anyone have an example of exporting both dotnet-monitor metrics and System.Diagnostics.Metrics for Prometheus scrape? The metrics aggregator can use any technology. Preferred approach would not require me building a custom container. A stable container with configuration file / environment variables will minimize deployment effort.

@pbolduc I ended up using dotnet-monitor side container to export event counters and OpenTelemetry within the application itself to export everything else. Yes it's two scraping endpoints per single application instance and ideally I would love to have it all outside the application itself, but I couldn't find any better way to do it.

@pbolduc I ended up using dotnet-monitor side container to export event counters and OpenTelemetry within the application itself to export everything else. Yes it's two scraping endpoints per single application instance and ideally I would love to have it all outside the application itself, but I couldn't find any better way to do it.

Because I have to use Prometheus scrape and need to annotate the pod with the prometheus.io/scrape: true and prometheus.io/port: 52325 annotations. I do not have control of or have ability adjust the scraping service (sysdig) configuration. From my understanding, the prometheus scraping looks for annotations on the pod, not each container  in the pod for scraping. I cannot specify multiple scrape endpoints. Perhaps I am not understanding your setup.

Another option is to ditch the dotnet-monitor sidecar and just use the OpenTelemetry to export both your 'system' metrics and application metrics....you just need to add a few additional nuget packages and wire them us like this....
{
    mb.AddMeter("demo")
    .AddProcessInstrumentation() // needs OpenTelemetry.Instrumentation.Process
    .AddRuntimeInstrumentation() // needs OpenTelemetry.Instrumentation.Runtime
    .AddAspNetCoreInstrumentation()
    .AddHttpClientInstrumentation()
    .AddConsoleExporter()
    .AddPrometheusExporter();
});

var app = builder.Build();

app.UseSwagger();
app.UseSwaggerUI();

app.MapPrometheusScrapingEndpoint();

Thank you. I am going to take this approach.  I have referenced this answer in discussion #2798.

Just wanted to give an update to everyone following this issue - we've started actively working on adding support for System.Diagnostics.Metrics, but we don't have a timeline for it yet. We'll link back to this issue once we have a PR for it. Thanks!

@kkeirstead thanks for info

@kkeirstead any news?

Sure! We've just finished adding initial limited support for System.Diagnostics.Metrics, which will be available soon in the upcoming 8.0 Preview 1 release. There are currently some limitations (you can learn more here), so we'll still be making some improvements. I'll continue posting updates to this thread once the feature is available.

Quick update - 8.0 Preview 1 was released earlier this week with our initial limited support for System.Diagnostics.Metrics (you can find our release notes here). We're excited to keep making improvements to it and can't wait to hear your feedback!

Running a .NET 7.0 app and added Metrics from System.Diagnostic.Metrics assuming dotnet-monitor would support it, but I cannot get dotnet-monitor to report them via /metrics endpoint.
Also unsure what the naming convention for what Metrics should be for injestion via dotnet-monitor, My Counter or my_counter or my-counter.
I am running dotnet-monitor 8.0.0-rc.2 to try and get these metrics scraped by Prometheus in an AWS ECS cluster.
Running dotnet-counter correctly reports the metrics.
Specifying the metrics in the settings.config does not help either:
"Metrics": {
    "IncludeDefaultProviders": true,
    "Providers": [
      { "ProviderName": "System.Net.Http" },
      { "ProviderName": "System.Net.Security" },
      { "ProviderName": "MyMetrics", "MetricType": "Meter" },
      { "ProviderName": "TestMetrics.Data", "MetricType": "Meter" },
      { "ProviderName": "TestMetrics.DataSource", "MetricType": "Meter","CounterNames": ["my_counter"] }
    ]
  }

Any assistance would be appreciated, burnt a lot of time thinking that System.Diagnostics.Metrics was the way to go as it's recommended by dotnet docs.

I could be wrong, but the .NET Monitor docs might be missing/outdated for the System.Diagnostics.Metrics specification. Meters are specified separately (using the Metrics:Meters configuration section) from counters (using the Metrics:Providers sections). For now, I'll point you to the data model used for binding configuration: https://github.com/dotnet/dotnet-monitor/blob/main/src/Microsoft.Diagnostics.Monitoring.Options/MetricsOptions.cs#L51C41-L51C48

+1 to Justin's comment - we made a change to our initial schema after writing up the docs, and it looks like updating them slipped through the cracks (I believe this is the relevant PR). I've created a new issue to track this to prevent any further confusion around the docs (see here) - thanks for bringing this to our attention!
I've rewritten out your configuration using the new schema - feel free to give this a try and let me know if you have any issues so that we can get you up and running.
"Metrics": {
    "IncludeDefaultProviders": true,
    "Providers": [
      { "ProviderName": "System.Net.Http" },
      { "ProviderName": "System.Net.Security" }
    ],
    "Meters": [
      { "MeterName": "MyMetrics" },
      { "MeterName": "TestMetrics.Data" },
      { "MeterName": "TestMetrics.DataSource","InstrumentNames": ["my_counter"] }
    ]
  }

One additional note - I don't know how you've named your instrument in the target app, but I tend to do "my-counter", which is then how I would include it in the InstrumentNames

Perfect thank you guys! I hated having to add the OpenTelemetry assemblies to my app when I have a dotnet-monitor sidecar already for dumps clr metrics.
Using Meters in the config for the sources of System.Diagnostics.Metrics works perfectly.

System.Diagnostics.Metrics support has been available since .NET Monitor 8. Please see the following documentation for how to enable collection: https://github.com/dotnet/dotnet-monitor/blob/main/documentation/configuration/metrics-configuration.md#adding-metersinstruments-for-systemdiagnosticsmetrics


feat(web,dal,sdf): add code editor widget

Does not have syntax highlighter, linter, etc because it doesn't know the language, we should improve that somehow (it's not clear to me right now how to do it best and it feels like a immediate benefit even without it)

bors merge

The bors failure:

Fail: root//app/web:check-type (17.2s)
--
  | ---- STDOUT ----
  | src/components/PropertyEditor/WidgetCodeEditor.vue(10,11): error TS2322: Type 'string \| null' is not assignable to type 'string \| undefined'.
  | Type 'null' is not assignable to type 'string \| undefined'.
  | src/components/PropertyEditor/WidgetCodeEditor.vue(48,9): error TS2322: Type 'string \| null' is not assignable to type 'string \| undefined'.
  |
  | ---- STDERR ----


Updated contribution section [german]

Hey @vsxed,
will this be followed by more updates or is it just about this specific section?
There has been an update to 1.2.0 last week, which comes with some more copy changes. I am already working on translating them.

Hey @morkro
ah okay, didn't see that you were working on them. Thought i could help you a bit.
So if you're already working on them, my PR can simply be ignored and you can finish yours.
Was a bit bored and saw, that the current translation wasn't up to date.
Just started to translated section by section to finally get a bigPR together.


Can we get the statistical information of total splits processed of a query from the class 'QueryInfo'

Hi:
We have run lots of queries on Presto, and in our scenario, we realized that reading numerous splits from HDFS or OSS(provided by Alibaba Cloud) was the most important part of performance, so we would like to trace and record the number of splits of the queries for following optimization.
But so far, I haven't found any available methods to fetch the number of splits in the class of 'QueryInfo', a running context object of query. So guys, what do you suggest me to get such information?

One way is to query system.runtime.tasks. It contains information about queued, running, completed and total splits for each query.

@raunaqmorarka Which interface can I use to do so?

@raunaqmorarka Which interface can I use to do so?

You can run a query on Presto using any client. E.g.: select * from system.runtime.tasks
Another option is to implement EventListener interface in your plugin, the splitCompleted method receives a SplitCompletedEvent on completion of every split. You could export this info into some other system and make use of it from there.

@raunaqmorarka Which interface can I use to do so?

You can run a query on Presto using any client. E.g.: select * from system.runtime.tasks
Another option is to implement EventListener interface in your plugin, the splitCompleted method receives a SplitCompletedEvent on completion of every split. You could export this info into some other system and make use of it from there.

Let me have a look, Thank you~