changing bpm effects the Transport scheduling

Should the bpm of transport effect the timings of schedule events? It currently seems like it does.
To Reproduce
Schedule an event like-
Transport.schedule((time) => {
currentName = narrativeEmotion.name;
handleAudioChange(narrativeEmotion.name, results);
// setIntro(false);
// setCurName(narrativeEmotion.name);
}, 20);
If you however change the transport bpm like
Transport.bpm.value = 120
This seems to effect when the schedule is hit - I would have expected this to be independent? Is that not the case? Is there a way to change bpm but not affect transport scheduling? Or does that not make any sense?
Expected behavior
Event happens after 20 seconds.

Sorry, to provide some context - what I am trying to achieve is the following -
i) a metronome that you can dynamically adjust the bpm for (it currently plays using scheduleRepeat every 4n using a 'player' object).
ii) A timeline that triggers events, as above, after x seconds that doesn't respond / change if i edit transport.bpm.value (or if better another way to edit the speed of the metronome rather than editing transport.bpm.value)
I was kinda expecting if you triggered events in seconds, that it would ignore the bpm...

I've had similar questions to this in the past, even if you schedule something using seconds instead of a tempo-relative value it will be converted into ticks which will mean that it will stay tempo-relative.
Currently there's no mechanism to do what you're looking for in Tone.js. sorry!
Maybe a new method like scheduleAtTime or something like that would be useful for what you're doing.

When you say nothing is available, do you mean i'll have to adjust the timings myself? Does that mean if the bpm is 60 that transport schedule would happen at that actual time specified, and if it was 120bpm I would need to double the timings etc?
Or do you mean it just won't work?
scheduleAtTime sounds good - is this library still actively being updated with new versions?

Changing tempo and even time signature might not be straight forward but it is possible.
Here's an example that I did some time ago, and finally put it on CopePen:
https://codepen.io/dirkk0/pen/mdMVpzE?editors=1010
It changes the signature and the bpm twice before ramping the tempo down.


[Feature Request]: GCP Matching Engine Support

Feature Description
I would like to add  support for GCP Matching Engine as a vector store.
Reason
I don't see GCP listed in https://github.com/run-llama/llama_index/tree/main/llama_index/vector_stores . We would have to write a custom vector store, but I feel like it could be include in the repo.
Value of Feature
Allow Google Cloud Users to easily integrate with Llamaindex.

@tambulkar does GCP have it's own vectordb? Can you link some docs if so?

Yeah its part of their vertex ai product:
https://cloud.google.com/vertex-ai/docs/vector-search/overview
https://cloud.google.com/vertex-ai/docs/vector-search/create-manage-index
https://cloud.google.com/vertex-ai/docs/vector-search/query-index-public-endpoint

@tambulkar does GCP Matching Engine support upserting? I don't see any docs on iteratively updating the database, or is the database iteratively updated as new docs are added to the contentsDeltaUri location?

I think it requires an update request: https://cloud.google.com/vertex-ai/docs/vector-search/update-rebuild-index


Rosetta 2 caveat is shown on Intel Mac

brew doctor output
❯ brew doctor
Your system is ready to brew.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
❯ brew config
HOMEBREW_VERSION: 4.3.10
ORIGIN: https://github.com/Homebrew/brew
HEAD: c3ae0327c01aab461531bfc0fcdfb4dd3a779205
Last commit: 5 days ago
Core tap JSON: 23 Jul 22:59 UTC
Core cask tap JSON: 23 Jul 22:59 UTC
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.kVMDnJXCPv/org.xquartz:0
HOMEBREW_MAKE_JOBS: 4
Homebrew Ruby: 3.3.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/3.3.3/bin/ruby
CPU: quad-core 64-bit kabylake
Clang: 15.0.0 build 1500
Git: 2.45.2 => /usr/local/bin/git
Curl: 8.4.0 => /usr/bin/curl
macOS: 13.6.7-x86_64
CLT: <IP_ADDRESS>.1.1700200546
Xcode: 15.2

What were you trying to do (and why)?
I was trying to update mkvtoolnix cask and was able to reproduce by removing and reinstalling after updating brew twice and ensuring a "clean" brew doctor output
What happened (include all command output)?
❯ brew install mkvtoolnix --cask
==> Caveats
mkvtoolnix is built for Intel macOS and so requires Rosetta 2 to be installed.
You can install Rosetta 2 with:
  softwareupdate --install-rosetta --agree-to-license
Note that it is very difficult to remove Rosetta 2 once it is installed.

==> Downloading https://mkvtoolnix.download/macos/MKVToolNix-86.0.dmg
Already downloaded: /Users/jorik/Library/Caches/Homebrew/downloads/b81013a19da815bea1b09cc9701aee91635c41f653d9550907d2bdb1528155e6--MKVToolNix-86.0.dmg
==> Installing Cask mkvtoolnix
==> Moving App 'MKVToolNix-86.0.app' to '/Applications/MKVToolNix-86.0.app'
==> Linking Binary 'mkvextract' to '/usr/local/bin/mkvextract'
==> Linking Binary 'mkvinfo' to '/usr/local/bin/mkvinfo'
==> Linking Binary 'mkvmerge' to '/usr/local/bin/mkvmerge'
==> Linking Binary 'mkvpropedit' to '/usr/local/bin/mkvpropedit'
==> Linking Manpage 'mkvextract.1' to '/usr/local/share/man/man1/mkvextract.1'
==> Linking Manpage 'mkvinfo.1' to '/usr/local/share/man/man1/mkvinfo.1'
==> Linking Manpage 'mkvmerge.1' to '/usr/local/share/man/man1/mkvmerge.1'
==> Linking Manpage 'mkvpropedit.1' to '/usr/local/share/man/man1/mkvpropedit.1'
==> Linking Manpage 'mkvtoolnix-gui.1' to '/usr/local/share/man/man1/mkvtoolnix-gui.1'
🍺  mkvtoolnix was successfully installed!

What did you expect to happen?
I did not expect to see this part in the output on an Intel Mac:
==> Caveats
mkvtoolnix is built for Intel macOS and so requires Rosetta 2 to be installed.
You can install Rosetta 2 with:
  softwareupdate --install-rosetta --agree-to-license
Note that it is very difficult to remove Rosetta 2 once it is installed.

Or rather, I started a discussion: https://github.com/orgs/Homebrew/discussions/5518 and @carlocab mentioned this caveat should not be shown. I have a 2017 MacBook Pro and running latest (by Apple) supported macOS for this devices: 13.6.7
Step-by-step reproduction instructions (by running brew commands)
brew install mkvtoolnix --cask

Yea, we check whether we need to display the caveat first, but that isn't working for some reason:
https://github.com/Homebrew/brew/blob/cfb4bf7670c03a80207ce884b68177bc90ab6b6c/Library/Homebrew/cask/dsl/caveats.rb#L144

That should probably be Hardware::CPU.in_rosetta2?

Check seems fine from a glance so may need some debug prints.

Yea, probably a regression from https://github.com/Homebrew/brew/commit/a77a8ca5642b813322a8f98abdd5436c8bfd99e2.

🙏I can confirm the issue is resolved on my system after updating brew and rerunning my reproduction steps


pdf options

added pdf options:
displayHeaderFooter
preferCSSPageSize
marginTop
marginBottom
marginLeft
marginRight
Ref: https://github.com/chrome-php/headless-chromium-php/issues/49

Hi @marios88 thanks for the PR. I'll add it with next version.


Feature Request: support parallel execution of analyzers of the same type

I analyzed the quite bad runtimes for my Gradle project and observed that the CentralAnalyzer was the culprit: it performs a blocking HTTP request for each dependency. For non-trivial projects this easily sums up to a remarkable duration.
To improve one could perform the dependency analyzation tasks of the CentralAnalyzer in parallel. As a generalization one could do so for almost all analyzers (there are a couple of exceptions):

sequentially process all analyzers
for each analyzer process the analysis tasks in parallel

Running analyzers of different types in parallel would be much harder, as there a dependencies between the analyzer types.

I attached my sample Gradle build file. Runtimes on my machine using Gradle 3.1 and warmed up Gradle Daemon:

1.4.3: ~9:00 min
1.4.4-SNAPSHOT: 1:29 min (contains fixes for Dependency deduplication and improved test configuration detection)
1.4.4-SNAPSHOT + this PR: 0:22

build.gradle.txt

This is actually something I've been thinking about implementing. I'll spend tomorrow morning reviewing and testing the implementation. While I did have to change the checksum calculations (earlier today) to use a slightly less efficient algorithm - a PR like this one looks like it will make up for the minor performance hit I had to re-introduce.

@stefanneuhaus Thats a substancial improvement!

@stefanneuhaus thanks!  #592 was merged


feat: Add "--no-hooks" to helmfile template

I'd like to request this feature because I am not using the hooks that helm charts generate during the template command but would like Helmfile to support that.
Happy to make changes and take feedback. I based changes on this https://github.com/helmfile/helmfile/commit/e1ca84677248fe799a1189d01b86396fbee984f1 but am aware it's an old design and I didn't consider the "diff-args" way of doing it.

@jwlai pls rebase or sqush your commits.

@jwlai please fix the lint issue.

@jwlai almost is LGTM. but could you add some tests? thanks so much.  you can follow https://github.com/helmfile/helmfile/commit/e1ca84677248fe799a1189d01b86396fbee984f1.


EventedHTTPServer HTTP server was closed

when I see "EventedHTTPServer HTTP server was closed" or "Sending HTTP event 'keepalive' with data: {"characteristics":[]} +6s hapNodeJSClient Ending Homebridge instance discovery +19s"
in debug, it is no longer possible to connect to devices in the home program (via remote access via Apple tv)
everything reconnects properly on the local network, but there is no access outside the network until http server reconnects
I also noticed that a device with another email id that is invited to the house, when trying to connect to the local network, gives
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: POST /pair-verify +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Pair verify step 2/2 +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Client DF368DF5-7C7A-4F65-A7B9-7B5DA26D7002 attempting to verify, but we are not paired; rejecting client
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +1ms
EventedHTTPServer [<IP_ADDRESS>] Client connection closed +6ms
EventedHTTPServer [<IP_ADDRESS>] HTTP connection was closed +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server was closed +1ms
and further connection is already through apple tv even in local network
i use node-red-contrib-homekit-bridged 6.2.0
and homebridge 0.4.50
ios 13.2

Full log
hapNodeJSClient HAP Device discovered HB Bridge [ '<IP_ADDRESS>', '<IP_ADDRESS>' ] +1s
hapNodeJSClient HAP instance address: HB Bridge -> 0E_C9_99_2C_A2_C6.local -> <IP_ADDRESS>:51826 +4ms
hapNodeJSClient HAP Device discovered TV Гостиная [ '<IP_ADDRESS>', '<IP_ADDRESS>' ] +18ms
hapNodeJSClient HAP instance address: TV Гостиная -> 45_80_EC_29_9E_90.local -> <IP_ADDRESS>:35227 +1ms
hapNodeJSClient Homebridge instance discovered HB Bridge-ABF3 with 7 accessories +104ms
hapNodeJSClient Homebridge instance discovered TV Гостиная-6842 with 1 accessories +20ms
EventedHTTPServer Server listening on port 41773 +0ms
hapNodeJSClient HAP Device discovered NR Bridge [ '<IP_ADDRESS>', '<IP_ADDRESS>' ] +6s
hapNodeJSClient HAP instance address: NR Bridge -> 00_2c_44_f9_30_8f_d1_2e.local -> <IP_ADDRESS>:41773 +1ms
EventedHTTPServer [<IP_ADDRESS>] New connection from client +849ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server listening on port 42505 +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /accessories +21ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: GET /accessories +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +51ms
hapNodeJSClient Homebridge instance discovered NR Bridge-F266 with 30 accessories +156ms
EventedHTTPServer [<IP_ADDRESS>] Client connection closed +49ms
EventedHTTPServer [<IP_ADDRESS>] HTTP connection was closed +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server was closed +3ms
EventedHTTPServer [<IP_ADDRESS>] New connection from client +100ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server listening on port 34993 +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +4ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: POST /pair-verify +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Pair verify step 1/2 +3ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +284ms
EventedHTTPServer [<IP_ADDRESS>] New connection from client +16ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server listening on port 34659 +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +35ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: POST /pair-verify +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Pair verify step 2/2 +3ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Client FE512FBA-A970-46D4-9A0C-6B350DCAFDA3 verification complete +126ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +3ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: POST /pair-verify +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Pair verify step 1/2 +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +131ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /accessories +15ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: GET /accessories +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +45ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +258ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: POST /pair-verify +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Pair verify step 2/2 +2ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Client 75F95F7A-3109-4B30-A9C6-78D4A0E864E1 attempting to verify, but we are not paired; rejecting client +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +1ms
EventedHTTPServer [<IP_ADDRESS>] Client connection closed +93ms
EventedHTTPServer [<IP_ADDRESS>] HTTP connection was closed +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server was closed +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /characteristics +95ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: PUT /characteristics +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +15ms
EventedHTTPServer [<IP_ADDRESS>] New connection from client +2s
EventedHTTPServer [<IP_ADDRESS>] HTTP server listening on port 39667 +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +12ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: POST /pair-verify +0ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Pair verify step 1/2 +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +167ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +34ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: POST /pair-verify +1ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Pair verify step 2/2 +2ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] Client FE512FBA-A970-46D4-9A0C-6B350DCAFDA3 verification complete +84ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +3ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /accessories +7ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: GET /accessories +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +30ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /characteristics +481ms
HAPServer [00:2c:44:f9:30:8f:d1:2e] HAP Request: PUT /characteristics +0ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +12ms
hapNodeJSClient Ending Homebridge instance discovery +12s

One thing I noticed is, that the username (device id) for your accessory (00:2c:44:f9:30:8f:d1:2e) is not valid. This must be a valid Mac address, six 8 bit hex codes like XX:XX:XX:XX:XX:XX.
Could be that this is the root cause. Note that you will need to completely repair your device if you change the username.

HAPServer [00:2c:44:f9:30:8f:d1:2e] Client DF368DF5-7C7A-4F65-A7B9-7B5DA26D7002 attempting to verify, but we are not paired; rejecting client

Regarding the client which is rejected. Could you navigate into the persist folder inside you homebridge folder an open file called something like AccessoryInfo.002C44F9308FD12E.json and check if the client id is present in the pairedClients clients property.
If it is not present' try removing and adding the person to your home again in the Home App.
But it could well be resolving the issue with the id length above could also resolve this issue.

Completely reinstalled everything from scratch, the problem with HAPServer [00:2c:44:f9:30:8f:d1:2e] Client DF368DF5-7C7A-4F65-A7B9-7B5DA26D7002 attempting to verify, but we are not paired; rejecting client disappeared. But remote access still works through time. Please explain for stupid, how to solve a problem with

One thing I noticed is, that the username (device id) for your accessory (00:2c:44:f9:30:8f:d1:2e) is not valid. This must be a valid Mac address, six 8-bit hex codes like XX:XX:XX:XX:XX:XX.

My full log now:
hapNodeJSClient HAP Device discovered TV Гостиная [ '<IP_ADDRESS>' ] +1s
hapNodeJSClient HAP instance address: TV Гостиная -> 45_80_EC_29_9E_90.local -> <IP_ADDRESS>:37925 +4ms
hapNodeJSClient HAP Device discovered HB [ '<IP_ADDRESS>' ] +18ms
hapNodeJSClient HAP instance address: HB -> CC_62_5E_E9_B2_11.local -> <IP_ADDRESS>:28888 +1ms
28 Oct 17:27:07 - [info] [tcp out:yeelight 650] connected to <IP_ADDRESS>:55443
28 Oct 17:27:07 - [info] [deconz-server:Deconz-rask] WebSocket opened
hapNodeJSClient Homebridge instance discovered TV Гостиная-6842 with 1 accessories +192ms
hapNodeJSClient Homebridge instance discovered HB-CF4A with 7 accessories +15ms
EventedHTTPServer Server listening on port 46261 +0ms
hapNodeJSClient HAP Device discovered NR [ '<IP_ADDRESS>' ] +6s
hapNodeJSClient HAP instance address: NR -> 00_0e_d5_7d_6c_84_e0_05.local -> <IP_ADDRESS>:46261 +1ms
EventedHTTPServer [<IP_ADDRESS>] New connection from client +883ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server listening on port 41689 +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /accessories +9ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: GET /accessories +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +44ms
hapNodeJSClient Homebridge instance discovered NR-C350 with 33 accessories +130ms
EventedHTTPServer [<IP_ADDRESS>] Client connection closed +58ms
EventedHTTPServer [<IP_ADDRESS>] HTTP connection was closed +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server was closed +3ms
EventedHTTPServer [<IP_ADDRESS>] New connection from client +40ms
EventedHTTPServer [<IP_ADDRESS>] HTTP server listening on port 35681 +0ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +5ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: POST /pair-verify +0ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] Pair verify step 1/2 +4ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +297ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +32ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: POST /pair-verify +1ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] Pair verify step 2/2 +3ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] Client FE512FBA-A970-46D4-9A0C-6B350DCAFDA3 verification complete +163ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +4ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /accessories +21ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: GET /accessories +0ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +66ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /characteristics +531ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: PUT /characteristics +0ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +16ms
hapNodeJSClient Ending Homebridge instance discovery +12s
hapNodeRed Discovered 122 new evDevices +19s
hapNodeRed Discovered 91 new ctDevices +9ms
EventedHTTPServer [<IP_ADDRESS>] New connection from client +2m
EventedHTTPServer [<IP_ADDRESS>] HTTP server listening on port 34521 +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +7ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: POST /pair-verify +0ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] Pair verify step 1/2 +5ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +163ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /pair-verify +32ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: POST /pair-verify +1ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] Pair verify step 2/2 +1ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] Client DF368DF5-7C7A-4F65-A7B9-7B5DA26D7002 verification complete +117ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +3ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /accessories +12ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: GET /accessories +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +43ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /characteristics +634ms
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: PUT /characteristics +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +19ms

now such things began to appear:
EventedHTTPServer [<IP_ADDRESS>] Muting event '6.10' notification for this connection since it originated here. +2ms
EventedHTTPServer [<IP_ADDRESS>] HTTP Response is finished +1ms
EventedHTTPServer [<IP_ADDRESS>] HTTP request: /characteristics +1s
HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: PUT /characteristics +0ms
EventedHTTPServer [<IP_ADDRESS>] Muting event '6.10' notification for this connection since it originated here.

So you installed homebridge, right? In your config.json you have something like the following:
{
    "bridge": {
        "name": "some name",
        "username": "00:2c:44:f9:30:8f:d1:2e",
        "port": <some port number>,
        "pin": "xxx-xx-xxx"
    },
    ...
}

As of your logs it seems the username property should be set to 00:2c:44:f9:30:8f:d1:2e in your configuration. This is the part which you need to change as it is formatted incorrectly. It has 8 hexadecimal digits separated by : while it should have 6. Just delete two of them (for example 44:f9:30:8f:d1:2e, but anything you like works) and restart homebridge and then repair it to your home (the old installation will become invalid in the home app).

Not only, yet node-red
Config homebridge ->

Okay but that is not the homebridge instance which from which the logs are, isn't it? 🤔
And I hope the pin is not the real one 😅
The username in the config differs from the username found in the logs

HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: GET /accessories +1ms

... is one log message where 00:0e:d5:7d:6c:84:e0:05 is the username.

maybe it's a nodred, but neither bridge works normal outside local network. In node-red i can't indicate username.
this is my real config, but what is wrong with the pin?) all works wonderful inside my wi-fi, there were no errors when adding bridges into homekit

Okay then. Remote access doesn't work at all? What are you using as your Home Hub? Apple TV 4th Gen? What tvOS version is running?

From the outside sometimes everything works well, but basically I always see the update status on all devices in homekit, waiting a few minutes and then no response. After some time, access appears again and so cyclically.
There are no problems on the apple's side, I did a complete reset apple tv, home app, in and out in icloud on all devices, check few different internet providers.
node v10.17.0
npm 6.12.0
apple tv 4k with tvOs 13
iphone 8 with iOs 13.2

@daddvok @Supereg The malformed username is definitely node-red and the node-red-contrib-homekit-bridged node.  I saw the same thing when I was looking at mdns requests on my network with WireShark, and saw the same malformed names.  At the time I had just ignored it, but when you saw the same same it was a quick aha moment. After reviewing the code, I can confirm it.
@Shaquu I wondering if this may be causing some of the stability issues with the node?
The problematic spot in the code
https://github.com/NRCHKB/node-red-contrib-homekit-bridged/blob/72d07f3b0456b722020bf71b46c61f4a28712c03/lib/HAPBridgeNode.js#L64

@NorthernMan54 it was always like that. But it indeed looks like it is wrong so I will have to fix it.
I am concerned about backward compatibility though.

I submitted a pull request that resolves the name issue, but it is a breaking change for existing users.  They will need to unpair and repair their devices in the Home app as part of implementing
https://github.com/NRCHKB/node-red-contrib-homekit-bridged/pull/172

any news?

After updating to 0.5.4 the problem with apple tv “no response” was resolved, but there are still some problems, sometimes devices are updated outside the home network for a very long time, and sometimes everything is fine. If once it was updated normally, then within 10 minutes everything is updated as expected, and then I assume the connection is broken and again a long update

@daddvok regarding 0.5.4 and MAC address generation fix it was merged on the latest dev branch of nrchkb.


Not using proxy

App version: <IP_ADDRESS>
OS Build: Windows 10 Pro 1809
A working HTTP proxy is set in Internet Options, and access to tumblr.com is verified no problem using web browsers.
All blogs reported offline by TumblThree, while looking at the verbose log of my proxy application, there's no traffic to tumblr through the proxy.

I found the cause of this issue. In Setteings.json, the proxy related keys are set to outdated value. Remove the value of these keys solved the problem.
The keys may be deprecated in the new version but it is stilled used  and the app does not provide a setting to change that. Please cosider remove or disable this in Settings.config

It already is. Read the change log. New users will not have this problem.


Chips component

Describe the solution you'd like
Chips components.
Chips are often interactive and used to allow users to filter or categorize content.
Used to display small pieces of information, such as tags or categories.
Features:

Interactive (e.g: on:click)
Toggable: indicating the state (with an icon?)
Leading Icon
Size
Dismissible with an "x" icon
Color

In addition to being used for (un)checking options, maybe it could also be used inside a select input that allows multiple selectable options as dismissible selected options if set with a toggle property. The select component could use these chips within the same line for options with a short text. Otherwise, when showing the list of multiple selectable options, the select could use checkboxes.
Describe alternatives you've considered
Badges, But I think it differs in terms of other features and behaviors.
Additional context
References and examples:

https://sveltematerialui.com/demo/chips/
https://tailwind-elements.com/docs/standard/components/chips/.

Thanks @renatocaliari
I also add https://m3.material.io/components/chips/guidelines for future reference.


sbt gives error: scalapb.sbt:1: error: object trueaccord is not a member of package com addSbtPlugin("com.trueaccord.scalapb" % "sbt-scalapb" % com.trueaccord.scalapb.Version.sbtPluginVersion) This happens after downloadin zipfile from github and running sbt in the e2e folder (Fedora)

After downloading the zip file, you need to run ./e2e.sh first. This creates a few class files inside the e2e project. After that, you can run sbt inside that directory as usual.


Nether

There is no oxygen in the nether but to make oxygen you need glowstone, sooo derp I guess.

Nether is supposed to have O2.  I think I know what happened though.  I'll have a fix out I'm a few hours.  In the meantime O2 can be disabled via config if needed.

I would just hard code the main dim to have O2 in your hasO2 method

That's the plan
On Jun 5, 2016 5:56 PM, "Robert WC Seifert"<EMAIL_ADDRESS>wrote:

I would just hard code the main dim to have O2 in your hasO2 method
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/zmaster587/AdvancedRocketry/issues/121#issuecomment-223840274,
or mute the thread
https://github.com/notifications/unsubscribe/ADX3LexIY_j5oqbOmFe5QTewlq4Gtrp2ks5qI0YfgaJpZM4IucmZ
.


Faster batch OCR via ThreadPoolExecutor

This speeds up OCR via multithreaded tesseract instances. Useful for batch-OCRing hundreds of notes.
I personally have about 10,000 notes to OCR, so this fix was necessary.

This isn't still optimal, as it issues a new instance of tesseract for each image. Optimally it should batch images to some chunks that are OCRed on one tesseract run. Tesseract can OCR multiple images at once.
If you're OCRing 100+ images addon could split them into a list of 10 images segment and apply tesseract to each of them.

Thanks for looking into this, I'll have a crack at batching them today or
tomorrow and push a change out.
On Mon, 9 Nov 2020 at 11:41, 박현우<EMAIL_ADDRESS>wrote:

This isn't still optimal, as it issues a new instance of tesseract for
each image. Optimally it should batch images to some chunks that are OCRed
on one tesseract run. Tesseract can OCR multiple images at once.
If you're OCRing 100+ images addon could split them into a list of 10
images segment and apply tesseract to each of them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cfculhane/AnkiOCR/pull/7#issuecomment-723694256, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRYIU7RVJ3HF7KR7PO5LCTSO43E7ANCNFSM4TKFJHIA
.

In the middle of a big re-factor which I think will help allow this approach. The aim it so untangle the processing step which is currently in one function OCR.ocr_process() , into three steps, allowing easier batching and debugging.
Steps would be :

Collect all notes via a query to the collection, and build a List of notes to process, represented as a list of NoteImages dataclasses (which will have a hierarchy of NoteImages -> FieldImages - OCRImage , all lightweight dataclasses.
Pass this into a process_notes() method, allowing it to be batched/split up, multithreaded etc
After processing is complete, or even concurrently with the above asynchronously, add these modified NoteImages back into the collection and save the updates to the db.

That'd be great. I havent modified the overall structure to keep the code consistent with previous version, but if you're in for structural change that'd of course be better :)

Looking more into this, as you noted Tesseract can already consume a list of images to batch-process. The PyTesseract library has an issue that discusses speed: https://github.com/madmaze/pytesseract/issues/261
I then tried the difference in speed between sending each image path to pytessert sequentially, or sending a list of paths to tesseract in a text file, and the final option - using multiprocessing.pool to spawn multiple tesseract processes. For a small number of images (say 5) the overhead from multiprocessor is not worth it, but over lots of images (e.g. 200), the difference was significant, for 200 images:
time_multiprocessing = 57 s
time_multiprocessing_batched 43.982 s(sending batches of 10 images to each worker) = **s
time_batched_input = 139.3 s (input.txt sent to tesseract)
time_iter = 171s (each image path sent sequentially to tesseract)
Note that tesseract already uses multi threading, but doesn't appear to use multiple cores. Also, using the same number of cores as exists in your machine locked things up pretty well with 100% utilisation on all cores!

My current PR utilizes ThreadPool, which acts like a multiprocessing but with way less overhead (python thread based). Note that current performance bottleneck is the OCR process itself, which is not in Python so GIL doesn't affect much.

Even better then, results with ThreadPool are faster than mp.Pool which surprised me. Due to the refactoring changes, I won't merge this PR, but rest assured the next version will be using ThreadPool with a user-configurable MAX_THREADS, as it tends to hog all of the CPU haha.
Final results, showing 4.4x improvement:
NUM PROCESSES/THREADS : 3
BATCH_SIZE : 10
Number of images = 200
'gen_batched_txts' completed in 0.008 s
Generated 20 batches of max 10 images
'seq_iter' completed in 170.1169 s
'big_batch' completed in 132.7926 s
'mp_pool' completed in 63.4509 s
'mp_pool_batched' completed in 57.1407 s
'thread_pool_exec' completed in 48.9472 s
'process_pool_exec' completed in 41.051 s
'process_pool_exec_batched' completed in 38.7359 s
'thread_pool_exec_batched' completed in 38.5955 s

Thanks again for raising this PR!

Thanks for having time :)

Closing, dev branch now uses ThreadedPoolExecutor, see https://github.com/cfculhane/AnkiOCR/commit/ecc36c8e87f1e971c4c2f6a2956850e86e863ae0

Hi, sorry to reopen this,
Reading this thread made me wonder something. I reaaally don't want to sound like an a****** but aren't you both confusing multithreading and multiprocessing?
I actually learned today that I was mistaking the two for a while. So I figured I'm maybe not alone..
I spent the whole morning trying different script for myself comparing different implementation and different settings and (not related to OCR) and it seems to me like multiprocessing seems more interesting in this case than multithreading don't you think? Especially if tesseract already uses multiple threads on its own.
@cfculhane That would explain why I didn't get 6 core at 100% when I was setting the num_thread to 6 some time ago... That's so obvious now.
I would think this might be related to why anki is often freezing during the execution.
I gathered quite a lot of snippets from this morning if you are interested in taking a look.
Again, I really don't want to appear like I'm not grateful or anything, especally given that you two are obviously better coders..

That's a very legitimate question, actually.

I spent the whole morning trying different script for myself comparing different implementation and different settings and (not related to OCR)

You should try with OCR. OCR is not in python, so the limitations of multithreading in python don't apply here. Python uses multiprocessing instead of multi-threading because of GIL. See

Note that current performance bottleneck is the OCR process itself, which is not in Python so GIL doesn't affect much.

That is extremely useful to me. Thank you very much.


⚠ Bofrost.at has degraded performance

In 73b774b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2890 ms

Resolved: Bofrost.at performance has improved in 72e5103 after 44 minutes.


Rename the metric lidarr_songs_missing_total

The metric lidarr_songs_missing_total should be called lidarr_albums_missing_total
My config:

Exportarr v1.1.0
Sonarr <IP_ADDRESS>7
Radarr <IP_ADDRESS>75
Lidarr <IP_ADDRESS>92

I don't personally use lidarr so I can't verify this -- can someone share their /api/v1/wanted/missing endpoint output, as well as the number of songs & albums that they expected to be "missing"?
You should be able to:
curl https://your.lidarr.deploy/api/v1/wanted/missing -H "X-Api-Key: <yourapikey>"

That would be what I need to verify & fix. otherwise, definitely open to a PR

nvm, @onedr0p beat me to it :-D

Thank you!


judgeAssignment linked to a pool

It would be nice to limit a judge assignment to a pool as well, this would be helpful for speed judging or events with dual panels. Today you can submit scores for another entry than you're supposed to

implemented in 5c711120d5f69389e49e0a1aee5fa08c81a80673 and RopeScore/api@c8d67eeff1adba2067a8ac77c3b542142ff1361a


Add modules from bootcamp23

This adds the new repos/pages from the bootcamp to the (currently hidden) curriculum page.

Preview: https://output.circle-artifacts.com/output/job/6dac14e8-24b3-404c-a4d0-ff27bcfefb48/artifacts/0/intersect-training.github.io/curriculum/index.html
I thought this would be easier to have everything in a single place that to go hunting for them. We might want to share it later too.

https://output.circle-artifacts.com/output/job/7f57bd31-e1da-4a02-8e7d-0ee013aacc6b/artifacts/0/intersect-training.github.io/curriculum/index.html


LintDiff and Avocado support request by Haoling Dong: false positives on a PR

See here

The PR got merged. I asked the Haoling if there is a need to file a bug against our tooling. Waiting for reply.

I asked if this was a problem with the tool here but I never got a reply. So closing as "nothing to do".


HMAC authN mode

There's already a placeholder for it at https://github.com/3scale-labs/authorino/blob/2b6a6f8016a5837650506cd125751f8d95ea4197/pkg/config/identity/hmac.go.

Hey, @guicassolato I'd like to work on this...any prereqs?

@Rohith-Raju, I think this issue lacks definition. Because of that, I'll remove participation/good first issue label for now.

Azure's HMAC authentication for REST APIs could be a good reference here. I like it because it's flexible (the contract includes telling the server what the source of the hash is) and because it doesn't use the request body in the string-to-sign (the contrary often makes HMAC authn impractical due to encoding issues, amongst other problems). Moreover, Azure's API HMAC authentication is simple and easy to implement in both ends (client and server).
However, Azure's approach is not a standard. To make it more generic, at least those Microsoft-specific required headers need to be dropped of course – although Date is probably better keeping.
AWS's HMAC authn uses a sightly different, more complex approach, where users first need to generate a temporary signing key out of the long-lived secret access key, the date and other attributes (AWS service name and region), and only then HMAC the message, including the payload.
We need to gather some inputs from the field to choose which model we want to support.


MSID: 90600 Version: 1 DOI: 10.1101/2<IP_ADDRESS>5015

MSID: 90600
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>5015
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=90600
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>5015

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/90600v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>5015
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/90600/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Hi @acollings, does the eLife assessment need tweaking in this one?

(BTW this ticket was originally raised with the wrong version number so that screenshot above is for the already published v1!)

I will proceed with publishing the v2 for this one.

Thanks @fred-atherden: the V1 can be repulled to fix the issue in the assessment

Thanks!


MIAD-112 add resync audit when processing resync request

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

Project coverage is 94.54%. Comparing base (ce9d215) to head (ae6ee50).
Report is 2 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #164      +/-   ##
============================================
+ Coverage     94.43%   94.54%   +0.10%
- Complexity      555      562       +7
============================================
  Files            91       92       +1
  Lines          1834     1869      +35
  Branches         99       99
============================================
+ Hits           1732     1767      +35
  Misses           69       69
  Partials         33       33

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


Remove unused deprecated integation tests

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@carolynhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
1ebc0feebca14beee23b8dd6829c8dceec743ced
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Improve error when manifest doesn't parse

It would be very helpful to know which manifest doesn't parse. Currently the only error I see is:
2024-07-23T20:03:33.474Z	FATAL	build/build.go:102	An error occurred building the image: configuring combustion: configuring component "embedded artifact registry": configuring embedded artifact registry: parsing manifests: reading manifest: invalid manifest

What version of EIB are you running? It looks like this error message now includes the manifest path, but that change was added 2 months ago and wouldn't have been in 1.0.


Fix issue with buildscript classpath state being discarded

This prevents the state required for resolving the buildscript classpath from being discarded when we discard the resolution results.  This allows the buildEnvironment task to correctly re-resolve the buildscript classpath later.
Fixes #27521
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


Did you make any profitable flash loans with this arbitrage?

What should we put in flashloanerAddress? My own address?
What is bakery flash loan fee?

You have to deploy the FlashLoaner Contract and use that address


"Add" Button Greyed Out Visual Studio 2019

Hey Microsoft, I want to add a symbol that will appear in the "Task List" window that says "DEBUG". It is my understanding we do this through the token symbol options window like mentioned above but I am not sure if it's working properly in 2019 or if it's just my own environment that is malfunctioning. Thanks!

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

ID: a1261884-8284-53f9-a325-15061bf897f8
Version Independent ID: 4520c20f-86f6-5066-298b-d3d428901f87
Content: Use the Task List - Visual Studio
Content Source: docs/ide/using-the-task-list.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @gewarren
Microsoft Alias: gewarren

@evanricard This is working for me. The trick is that you have to enter a name and then Add becomes enabled. It's not a good design, I agree. I'll make this more clear in the document.


Tutorial

EDIT:
New plan is finally just to update the old tutorial.

It reads really nicely, I just had some very minor corrections :)

Updated the iframe to @ewels updated presentation.
We would need to update the actual file on the website as well actually.

And now we have an updated presentation as well

The PR was already merged when you made the suggestion comments @olgabot so we can't just commit them in any more sadly, they need to be made in a new PR..


Support Deis Workflow for Kubernetes 12 Factor apps deployments

Also Deis Workflow should be supported as it makes an easy way to deploy 12 Factor apps to Kubernetes

Workflow is no longer maintained so supporting it doesn't make sense.


Carthage and Bitcode Support

Pull requests gives an update to the framework. It enables modern iOS development technologies.

Carthage Support
Bitcode Enabled
Swift 4 Example

I dropped iOS 8 support.

What's stopping this PR to get merged? @eduardo22i can you please resolve these conflicts that will be so nice of you. 😄

please solve conclicts

conflicts solved @zsajjad @gali8 :)

@eduardo22i Why did you remove the function recognizedHierarchicalBlocksByIteratorLevel:(G8PageIteratorLevel)pageIteratorLevel from G8Tesseract.h? Can this function be added again?

Good catch, it was my mistake. I'll add it again!

Good catch @juergenm, it was my mistake. I'll add it again!


Support dev extensions

Changes to the core CLI needed to better support extension development scenarios alongside production scenarios.
Collects sources of development extensions (identified by egg-info instead of dist-info) from a config entry or ENV variable called AZURE_EXTENSION_DEV_SOURCES which accepts a comma-separated list. These core changes will be leveraged in the new azdev to streamline development tasks for extension developers.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

@williexu opening with DNM label for your initial code review. I plan to do more testing and, at least temporarily, check for dev extensions in the standard extensions folder by default so the flow described in the current extensions doc continues to work.

@williexu please take a look. I'm working on fixing up the last two unit tests (that use a mock get_extensions… yaaaaaay…)

@williexu changes are made and CI passing. Please take another look and let me know what you think.


MINOR: Clarify <IP_ADDRESS> upgrade docs

This is a minor change to fix the most glaring issues. We have another JIRA to revamp the upgrade docs.

@ijuma Left a comment on the untouched instruction. The rest seems clearer to me.

@hachikuji thanks, updated that bit too.

LGTM. Thanks Ismael, this is much clearer.


Playback Options Bug (Video Player)

Steps to reproduce
There's a bug when I clicked the playback options
Expected behavior
After using the playback options, I should be watching anime freely without hindrance.
Actual behavior
After I clicked the playback options, my notification bar and navigation buttons (virtual buttons) is stuck. It feels as if there's a watermark.
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 10
Device
Realme 5i
Other details

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have tried the troubleshooting guide.
[x] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[x] I will fill out all of the requested information in this form.

Steps to reproduce
There's a bug when I clicked the playback options
Expected behavior
After using the playback options, I should be watching anime freely without hindrance.
Actual behavior
After I clicked the playback options, my notification bar and navigation buttons (virtual buttons) is stuck. It feels as if there's a watermark.
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 10
Device
Realme 5i
Other details

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Downgrade to v<IP_ADDRESS> and update the extensions. <IP_ADDRESS> is not working for pretty everyone.

same as #341. Discussion is taking place there. @jmir1 You can close this issue


problems autolinking to a property in a different level of same spec

I tried to add an issue in https://drafts.csswg.org/css-text-4/ that referred to the text-align property, which I wrote with single quotes.  (css-text-4 currently defines a new value for text-align, but doesn't redefine the property since it's currently a delta spec.)
This leads to:
FATAL ERROR: No 'property' refs found for 'text-align' with spec 'css-text-3'.
(I worked around it by not quoting 'text-align', so there's no autolinking.)
If I change the shortname in css-text-4/Overview.bs, things works fine, so it seems there's something weird about trying to autolink to a property in a different level of the same spec.

Dupe of #585


[19] Update browser

See Issue #19 for details.

There is now one major issue in the code.
When I go to options --> search (main menu) and I want to load the results into the main browser table, the first column contains the path of the object or collection and not the "Status".
I need the path somewhere in the table, since the label "iRODS path" is not valid for the searched objects and collections. So maybe we have to merge that in the column "Name"?
Currently any actions on searched objects and collections in the main browser table fail
[2023-02-13 14:21:41,060] {IrodsBrowser.py:396} INFO - ERROR in Browser
Traceback (most recent call last):
  File "/Users/staig001/RUG/iBridges/gui/IrodsBrowser.py", line 393, in fillInfo
    self._fill_acls_tab(obj_path)
  File "/Users/staig001/RUG/iBridges/gui/IrodsBrowser.py", line 207, in _fill_acls_tab
    self.owner_label.setText(f'Owner: {obj.owner_name}')

I fixed the this bug.


Add type to Session begin and begin_nested

Add complete types information for begin and begin_nested

Just submitted a CLA under the company Flare systems.

Thanks!


Rest sensor

This is a basic implementation of a REST sensor.

Ups, there seems to be a bug...only the first entry in the configuration.yaml is working.

This is the doc for this sensor.

Those are points to implement (collected here and in gitter):

allow POST request
parse nested responses (like http://docs.zwayhomeautomation.apiary.io/)


Select public or private methods inside a macro

Is there a way select all public or all private methods from @type.methods inside a macro ? For example
macro public_methods
  {% public_methods = @type.methods.public.map(&.name.stringify) %}
  {{ public_methods }}
end

No, we may only access these methods: https://github.com/manastech/crystal/blob/master/src/compiler/crystal/macros/methods.cr#L620
I agree it would be nice to access the visibility attribute of Def types.

@ysbaddaden it would be good if someone implemented that. I don't have enough knowledge and experience for this. Maybe you could?

@Codcore @ysbaddaden We'll do. Ideally you should be able to reflect on all attributes of AST nodes, but we add them slowly as we need them.

@asterite good news. But what is priority of visibility attribute for Defs? Maybe leave this opened until it will be done?

OK, I'll try!

@ysbaddaden oh, it would be cool :+1:

Probably it should be something similar to https://github.com/manastech/crystal/commit/1842ba1e2df9f71245484a0586bed2e3f0373c59 and https://github.com/manastech/crystal/commit/5bfee485b20f456aa9f8f0e7a367b72e95b730ee
Happy coding!

This is now implemented


TRANSCRIPT 4/8/27/28

Revised homepage design, main picture to be changed after upload page is done

Commented


[PE-D][Tester B] Typo in SOCompiler

Should be SOCompiler, right?

Labels: type.DocumentationBug severity.VeryLow
original: florentianayuwono/ped#24

Thanks, have fixed the error on UG.


Create example non-Spring project

Create an example project to demonstrate how to use EasyLog in non-Spring projects

Created Easy Log for non-Spring projects - example


[SPARK-34863][SQL][FOLLOW-UP] Handle IsAllNull in OffHeapColumnVector

What changes were proposed in this pull request?

This PR fixes an issue of reading null columns with the vectorised Parquet reader when the entire column is null or does not exist. This is especially noticeable when performing a merge or schema evolution in Parquet.
The issue is only exposed with the OffHeapColumnVector which does not handle isAllNull flag - OnHeapColumnVector already handles isAllNull so everything works fine there.
Why are the changes needed?
The change is needed to correctly read null columns using the vectorised reader in the off-heap mode.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
I updated the existing unit tests to ensure we cover off-heap mode. I confirmed that the tests pass with the fix and fail without.

cc @sunchao @cloud-fan. I am going to update the description and add a test but would like you to take a look.

The implications of the bug are the following:

All missing columns are treated as null and either report wrong results or crash JVM.
All fully null columns have a similar behaviour.

Examples of errors:
[info]
[info]   == Results ==
[info]   !== Correct Answer - 3 ==   == Spark Answer - 3 ==
[info]   !struct<>                   struct<_1:struct<_3:int,_4:bigint>>
[info]   ![null]                     [[336920597,0]]
[info]   ![null]                     [[827474256,0]]
[info]   ![null]                     [[872417200,1447062946291269968]] (QueryTest.scala:243)

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007ff3dd03ec6e, pid=19511, tid=0x00007ff2b39db700
#
# JRE version: OpenJDK Runtime Environment (8.0_292-b10) (build 1.8.0_292-8u292-b10-0ubuntu1~18.04-b10)
# Java VM: OpenJDK 64-Bit Server VM (25.292-b10 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 7824 C1 org.apache.spark.sql.execution.vectorized.OffHeapColumnVector.getLong(I)J (41 bytes) @ 0x00007ff3dd03ec6e [0x00007ff3dd03eb60+0x10e]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/ivan.sadikov/spark-oss/sql/core/hs_err_pid19511.log
Compiled method (c1)    9692 7823       3       org.apache.spark.sql.vectorized.ColumnarRow::getLong (16 bytes)
 total in heap  [0x00007ff3dd03cd90,0x00007ff3dd03d2f8] = 1384
 relocation     [0x00007ff3dd03ceb8,0x00007ff3dd03cf08] = 80
 main code      [0x00007ff3dd03cf20,0x00007ff3dd03d160] = 576
 stub code      [0x00007ff3dd03d160,0x00007ff3dd03d218] = 184
 oops           [0x00007ff3dd03d218,0x00007ff3dd03d220] = 8
 metadata       [0x00007ff3dd03d220,0x00007ff3dd03d228] = 8
 scopes data    [0x00007ff3dd03d228,0x00007ff3dd03d268] = 64
 scopes pcs     [0x00007ff3dd03d268,0x00007ff3dd03d2d8] = 112
 dependencies   [0x00007ff3dd03d2d8,0x00007ff3dd03d2e0] = 8
 nul chk table  [0x00007ff3dd03d2e0,0x00007ff3dd03d2f8] = 24
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

Merged to master/3.3

Thank you!


new datasource with CSV file of sales , but status is always "Preparing"

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

s

after the source create about one hour, the status of the source change to "FAILED"
I will see the failed reason first

there are many this exception

@larrychao It seems that underscores in hostname are not allowed like this link in Java. Can you change the hostname?
On the other hand, we check the status of the druid task at the time of ingestion like UI you captured. I think we will check the part that does not change to the failed state for that exception.

@kyungtaak thanks
now i run metatron-discovery at my mac-book, all as the install guid:https://metatron.app/download/installation-guide-custom-install/
but when i new datasource with sales.csv all failed
in the log files can catch WARN:
2019-08-14T03:00:56,017 WARN [Coordinator-Exec--0] io.druid.server.coordinator.helper.DruidCoordinatorRuleRunner - Uh... I have no servers. Not assigning anything...
i just run as guid, no others works

That's weird.
@larrychao Can you check all of druid service ports are running well?

Service ports : 8081 / 8082 / 8083 / 8090 / 8091

Other services may be occupied the above ports, so please shutdown Druid and check the above ports are NOT opened.
Finally, start the Druid and check all ports are opened well.

thanks @alchan-lee
i have change all port to new
and rerun create source
catch errors
'Found no files to ingest! Check your schema.'

I think the data : "sales-data-sample.csv" may has some problem at my environment,
because when i get little data form "sales-data-sample.csv" and save to a new file , named "samp-part.xlsx",
then i take "samp-part.xlsx" to create datasource ,sucess!!!


karthikeyan97 implementation

Check List:

[x] Tests pass (./test.sh <username> shows no differences between expected and actual outputs)
[x] All formatting changes by the build are committed
[x] Your launch script is named calculate_average_<username>.sh (make sure to match casing of your GH user name) and is executable
[x] Output matches that of calculate_average_baseline.sh

Execution time:4.5
Execution time of reference implementation:208

Hey, thx for particpating! As per the README and the PR template, new entries should run under 10 sec at this point, as it's just getting to hard to operate otherwise. It's not a hard and fast rule, but this one comes in at 39.995 s, i.e. way beyond the threshold. So maybe move it to draft state for now and iterate a bit on your end until it's there? Thx!

Hi made some changes and think this will do the magic.Can u please run this once again


Added support for new URL scheme for Youtube channels without the "@" (#274)

>>> from pytubefix import Channel
>>>
>>>
>>> urls = {
...     "url1": "https://www.youtube.com/joerogan",
...     "url2": "https://www.youtube.com/c/joerogan",
...     "url3": "https://www.youtube.com/@joerogan"
... }
>>>
>>>
>>> for key, url in urls.items():
...     c = Channel(url)
...     print(f'Channel name: {c.channel_name}')
...
Channel name: PowerfulJRE
Channel name: PowerfulJRE
Channel name: PowerfulJRE
>>>

we will keep it as it was for now


SignalR services are still running in Azure

If SignalR support is being sunsetted, we should finalize cancelling these services at some point.

Yes. Just do it.
Better to create them again if we decide to use it.

Deleted services vsm-sr-prod, vsm-sr-qa, vsm-sr-test, vsm-sr-dev from the Azure resource groups.


brew cask install docker failed

==> Satisfying dependencies
complete
==> Downloading https://get.docker.com/builds/Darwin/x86_64/docker-1.11.2.tgz
Already downloaded: /Users/lingchaox/Library/Caches/Homebrew/docker-1.11.2.tgz
==> Verifying checksum for Cask docker
Error: It seems the symlink source is not there: '/usr/local/Caskroom/docker/1.11.2/docker-1.11.2'

From this moment on docker installs the GUI app. If you want the CLI, use homebrew.

Just in case someone would still hit the same issue, the root cause of the above error is running old version of brew cask. All works as expected after brew cask update is performed.


Throw errors when job.complete is given invalid data

SDK Component
Zeebe
Expected Behavior
When passing an array of data to job.complete, I would expect an error to be thrown since zeebe doesn't seem to be able to properly deal with arrays.
Current Behavior
Possibly related to: https://github.com/camunda/camunda-8-js-sdk/issues/236
Currently passing an array of data to job.complete (job.complete([{ var1: 1 }])) does not throw an error, and the token is stuck on that task
Possible Solution
In parseVariablesAndCustomHeadersToJSON, add
if(Array.isArray(response.variables)) {
  throw new Error('Unable to parse Array into variables'); //Or something like that
}

Also if there's any other values that would cause this behavior, it would be nice to have those explicitly thrown
Steps to Reproduce
When handling a ZeebeJob, pass an array of data into job.complete

job.complete([{ var1: 1 }] as any)

Notice that the token is stuck with no incidents reported, and no errors thrown
Context (Environment)
I know the typing for complete technically doesn't allow arrays, due to a type assertion we ended up accidentally passing an array. While this was easy to fix, it was difficult to diagnose the issue since from adding console.logs it seemed like everything ran successfully

Thanks for reporting this.
Hmmmm... this is a very strange behaviour, and I don't know that a run-time type guard here is the best place to address this in the system.
I would expect that if no error is thrown by the gRPC API call to Zeebe that the CompleteJob operation completed successfully.
I tested this scenario, and I see what you report: the gRPC API throws no error, the process does not throw an incident and the job is not completed. The job is sent for a retry, but because it doesn't fail on the client, no retry decrement occurs (retry decrement is the responsibility of the client making the FailJob RPC call).
Thus, the job goes into an infinite retry loop.
I will check with the Zeebe engineering team. I have a vague memory of this coming up a few years ago. Let me look into it.

We'll guard against it in the client immediately - I don't know at what point they'll be able to re-engineer the API.
The new REST API endpoint for completing a job (in 8.6) throws a 400 if you try to post an array to it.

stringifyVariables is the function that needs the guard. That one JSON stringifies the variables for a request to the gateway, and is called from the ZBClient completeJob method - which is how the worker completes jobs.
The parseVariablesAndCustomHeadersToJSON function is used for parsing responses from the gateway from stringified JSON to JS objects.


RCT_EXPORT_METHOD that takes no parameters and returns a promise throws error

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
yes
Environment
Environment:
OS: macOS Sierra 10.12.6
Node: 8.9.0
Yarn: 1.3.2
npm: 5.5.1
Watchman: 4.9.0
Xcode: Xcode 9.1 Build version 9B55
Android Studio: 3.0 AI-171.4408382
Packages: (wanted => installed)
react: 16.0.0-beta.5 => 16.0.0-beta.5
react-native: 0.49.3 => 0.49.3
Target Platform: iOS (10.3)
Steps to Reproduce

(Write your steps here:)

Create a native module that returns a promise

TestNativeModule.h
#import <Foundation/Foundation.h>
#import <React/RCTBridgeModule.h>

@interface TestNativeModule : NSObject <RCTBridgeModule>
@end

TestNativeModule.m
@implementation TestNativeModule
RCT_EXPORT_MODULE();

RCT_EXPORT_METHOD(get: findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject) {
  resolve("test");
}
@end

Call it from JS:

const promise = NativeModules.CallToAdventureNative.get();

See the error:

CallToAdventureNative.get was called with 0 arguments but expects 1 arguments. If you haven't changed this method yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away.

Note: It works if you pass Anything to the .get function.
Expected Behavior
It would call the function.
Actual Behavior
The error posted above.
Reproducible Demo
It's a native module, can't repro the web

What are you talking about

On Nov 30, 2017, at 8:48 PM, JPTeasdale<EMAIL_ADDRESS>wrote:
Is this a bug report?
Yes
Have you read the Contributing Guidelines https://facebook.github.io/react-native/docs/contributing.html?
yes
Environment
Environment:
OS: macOS Sierra 10.12.6
Node: 8.9.0
Yarn: 1.3.2
npm: 5.5.1
Watchman: 4.9.0
Xcode: Xcode 9.1 Build version 9B55
Android Studio: 3.0 AI-171.4408382
Packages: (wanted => installed)
react: 16.0.0-beta.5 => 16.0.0-beta.5
react-native: 0.49.3 => 0.49.3
Target Platform: iOS (10.3)
Steps to Reproduce
(Write your steps here:)
Create a native module that returns a promise
TestNativeModule.h
#import <Foundation/Foundation.h>
#import <React/RCTBridgeModule.h>
@interface TestNativeModule : NSObject
@end
TestNativeModule.m
@implementation TestNativeModule
RCT_EXPORT_MODULE();
RCT_EXPORT_METHOD(get: findEventsWithResolver:(RCTPromiseResolveBlock)resolve
rejecter:(RCTPromiseRejectBlock)reject) {
resolve("test");
}
@end
Call it from JS:
const promise = NativeModules.CallToAdventureNative.get();
See the error:
CallToAdventureNative.get was called with 0 arguments but expects 1 arguments. If you haven't changed this method yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away.
Note: It works if you pass Anything to the .get function.
Expected Behavior
It would call the function.
Actual Behavior
The error posted above.
Reproducible Demo
It's a native module, can't repro the web
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/facebook/react-native/issues/17037, or mute the thread https://github.com/notifications/unsubscribe-auth/ATjBYY2wbFr95EoBzkAMulkOdI59QFynks5s71rlgaJpZM4QxwA9.

Try:
RCT_EXPORT_METHOD(get:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject) {
  resolve("test");
}

FWIW this is still broken as of 0.53, although I believe you can get around it via the hacky solution stated above:
RCT_EXPORT_METHOD(someMethodName: (NSString *)blank
        resolve(RCTProniseResolveBlock)resolve
        reject(RCTPromiseRejectBlock)reject) {
    // Do something
    resolve(nil);
}

Then in JS
SomeModule.someMethodName("");

Like I said, super hacky.

@anderskev Have you tried:
RCT_EXPORT_METHOD(someMethodName:(RCTPromiseResolveBlock)resolve
                  reject:(RCTPromiseRejectBlock)reject) {
  // Do something
  resolve(nil);
}

?
This is the expected Objective-C signature for a method receiving only resolve & reject arguments.

the function
RCT_EXPORT_METHOD(get: findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject) {
  resolve("test");
}

should be:
RCT_EXPORT_METHOD(get: (RCTPromiseResolveBlock)resolve rejecter:(RCTPromiseRejectBlock)reject) {
  resolve("test");
}

I'm just checking in on this. I'm also running into this error. Is there a better solution than that empty string hack?

@cmwall The issue here was a incorrect syntax, there's no need for an empty string. What's your native method signature?


Remove TLS 1.0 as it is deprecated

PCI Council release version 3.1 of their Data Security Standard (DSS) has decided that SSL and TLS 1.0 can no longer be used after June 30, 2016.
With 1.0 as insecure as it is with the current attacks I think the application should no longer be enabling it.

Sorry it took me a while to test this.
It worked just fine on a test server.

This has been removed in #268 as Server 2008 doesn't have TLS 1.1 or TLS 1.2 and needs TLS 1.0 enabled.


using drag and drop plugin doesn't update selection order

Did I miss some configurations or is this a bug or intended to work like this?
If you use ember-selectize with the drag_drop plugin enabled and change the order of selection it won't update the selection property accordingly.

You mean it won't change the order in the selection array?
It's neither a bug or a question of configuration, it's just something that isn't implemented.
It could be useful.

Can you point me to the part which needs to be changed? Couldn't find a proper place to handle it.
Is it best to subscribe to the selectize change event and update the selection accordingly? I could try to prepare a PR

@mszoernyi Looking through selectize docs. It looks like we need to include jQuery UI for that.
Probably you could have a better luck extending selectize in our own app, and handle events accordingly.
In principle one would try to catch whatever selectize event a drag n drop triggers and change the selection array accordingly.

Thanks @miguelcobain, I will extend the component first and maybe I figure our how to add this.


Direct users to milli for the core library in the README

Hello @okyanusoz! thanks for the PR. I would rather ask for a review of our tech writing team before any merge, but they have a lot on their plate right now.
So, sorry for the delay, but the review will come :) We'll come back to you

No problem.

@guimachiavelli, when you have time to check this 😇

Merging without bors since clippy errors are fixed on release-v0.21.0 and does not concern this PR.


Add connectionbroker package

This package is a small abstraction on top of Remotes that provides a
gRPC connection to a manager. If running on a manager, it uses the unix
socket, otherwise it will pick a remote manager using Remotes. This
will allow things like agent and certificate renewal to work even on a
single node with no TCP port bound.
This is a piece of #1826. The next PR will convert the CA and agent to
use connectionbroker.

Looks good to me.

Close won't be called when SelectRemote returns an error. The success parameter is determined later on. For example, if something tries an RPC and that RPC fails, success will be set to false when closing the connection so that a negative observation is made and future attempts will prefer a different remote.
I think Dial generally doesn't fail immediately (since Dial is an async call), but it's probably a good idea to automatically perform a negative observation if Dial returns an error. I'll add that.

LGTM


Update README.md

:+1:
What the program do ?

In what programming language it is written?

This pull request do not contains files in specific folders. Please fix it and reopen


Updating the GitHub Action File

This PR updates the GH Actions file to have the following changes:

Renaming the steps in the workflow to make it more meaningful (code readability).
Disabling prombench trigger on release cut (prombench now works only upon commenting on a PR).
Adding comments to a PR when a prombench run is cancelled.
Adding labels to a PR when a prombench run is triggered.
Fixing the docker image URLs to point to the GHCR repo instead of a personal dockerhub account.

Thanks!


DX: Code coverage feels broken due to only re-running one test file

Describe the bug
When requiring 100 % code coverage (for example), vitest feels broken: It sometimes says that the coverage goals weren’t met, but they are! This happens when you edit a test while vitest is running and watching, which seems to trigger only that test to run, which results in – technically – not all source code being run (unless every test file tests everything). This is confusing to me. The tool is reporting a problem that isn’t a problem. This makes vitest feel broken to me: I can’t really trust what I see after I save a file – I need to manually trigger a run for it to “work”.
A potential solution is to print something like “Not all tests were run, so coverage was not considered. Press Enter to run all tests and check coverage.” (Instead of showing coverage and if the goals were met.)
Note: There might be more situations when the whole test suite isn’t run, which should lead to the same issue.
Reproduction

Clone https://github.com/lydell/vitest-quirk

npm cit
added 92 packages, and audited 93 packages in 597ms

18 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

> test
> vitest

 DEV  v0.34.6 /Users/simon/stuff/vitest-quirk
      Coverage enabled with v8

 ✓ test1.test.ts (1)
 ✓ test2.test.ts (1)

 Test Files  2 passed (2)
      Tests  2 passed (2)
   Start at  22:43:18
   Duration  133ms (transform 24ms, setup 0ms, collect 20ms, tests 4ms, environment 0ms, prepare 88ms)

 % Coverage report from v8
----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |     100 |      100 |     100 |     100 |
 index.ts |     100 |      100 |     100 |     100 |
----------|---------|----------|---------|---------|-------------------

 PASS  Waiting for file changes...
       press h to show help, press q to quit

✅ 100 % code coverage.

In another terminal, run touch test1.test.ts
 RERUN  test1.test.ts x1

 ✓ test1.test.ts (1)
   ✓ myFunction1

 Test Files  1 passed (1)
      Tests  1 passed (1)
   Start at  22:44:57
   Duration  9ms

 % Coverage report from v8
----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |     100 |      100 |      50 |     100 |
 index.ts |     100 |      100 |      50 |     100 |
----------|---------|----------|---------|---------|-------------------
ERROR: Coverage for functions (50%) does not meet global threshold (100%)

 PASS  Waiting for file changes...
       press h to show help, press q to quit

🤔 Suddenly I only have 50 % coverage?

Workaround: Press Enter in the vitest terminal.
 RERUN

 ✓ test2.test.ts (1)
 ✓ test1.test.ts (1)

 Test Files  2 passed (2)
      Tests  2 passed (2)
   Start at  22:45:58
   Duration  14ms

 % Coverage report from v8
----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |     100 |      100 |     100 |     100 |
 index.ts |     100 |      100 |     100 |     100 |
----------|---------|----------|---------|---------|-------------------

 PASS  Waiting for file changes...
       press h to show help, press q to quit

✅ Now it reports 100 % coverage again.

This makes vitest feel broken to me: I can’t really trust what I see after I save a file – I need to manually trigger a run for it to “work”.
System Info
System:
    OS: macOS 13.6
    CPU: (10) arm64 Apple M1 Pro
    Memory: 186.52 MB / 32.00 GB
    Shell: 3.6.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 20.5.0 - ~/.local/share/nvm/v20.5.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.8.0 - ~/.local/share/nvm/v20.5.0/bin/npm
    pnpm: 8.8.0 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 118.0.5993.96
    Safari: 16.6
  npmPackages:
    @vitest/coverage-v8: 0.34.6 => 0.34.6
    vitest: 0.34.6 => 0.34.6

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

✅ 100 % code coverage.
In another terminal, run touch test1.test.ts
🤔 Suddenly I only have 50 % coverage?

Works as expected.
Coverage report includes coverage generated by the test files that are run. If you run only a subset of your test files, you cannot see coverage of all test files. As far as I know, every (Javascript) code coverage tool works like this. You cannot see coverage of test files that are not run.

Works as expected.

Yeah, it’s expected when you think about it. But until then it feels broken. Stupid humans running computers 😄

As far as I know, every (Javascript) code coverage tool works like this.

Then let’s be better than all the other tools! Feels on-brand for vitest 😄

Watch mode re-runs only the test files that are changed or that are affected by the changed source files. In order to show coverage report of all test files, all test files need to be run. Running all tests when a single file changes during watch mode makes no sense as it would make developer experience worse.
Any suggestions what to change here?

Quoting from first post:

A potential solution is to print something like “Not all tests were run, so coverage goals were not considered. Press Enter to run all tests and check coverage.”

My first idea was to not show coverage at all when not all tests are run, but now I realize that people might use the output to quickly iterate on the coverage of a certain file via a certain test. So maybe it makes sense to print the table, but not the ERROR: Coverage for functions (50%) does not meet global threshold (100%) lines. It could look like this (see the added NOTE line):
 RERUN  test1.test.ts x1

 ✓ test1.test.ts (1)
   ✓ myFunction1

 Test Files  1 passed (1)
      Tests  1 passed (1)
   Start at  22:44:57
   Duration  9ms

 % Coverage report from v8
----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |     100 |      100 |      50 |     100 |
 index.ts |     100 |      100 |      50 |     100 |
----------|---------|----------|---------|---------|-------------------
NOTE: Not all tests were run, so global threshold was not checked. Press Enter to run all tests and check coverage thresholds.

 PASS  Waiting for file changes...
       press h to show help, press q to quit

Feel free to change the wording of the NOTE line – the point here is that something along those lines is more helpful to the user than ERROR that you need to learn to ignore and not ignore depending on the situation.

My first idea was to not show coverage at all when not all tests are run, but now I realize that people might use the output to quickly iterate on the coverage of a certain file via a certain test. So maybe it makes sense to print the table, but not the ERROR: Coverage for functions (50%) does not meet global threshold (100%) lines.

They may also be using the coverage threshold information when iterating on the tests - especially if they are using coverage.perFile option. It still makes sense when a single test file is used to cover source files enough.
I think if we did not show coverage threshold information during watch mode re-runs we would get bug reports stating we should. Especially since other tools (like Jest) do it too.
If you want to disable coverage thresholds like this on your project by patching Vitest, you can change if-block's condition below. There's already allTestsRun variable in that scope which indicates wheter all teste were run.
https://github.com/vitest-dev/vitest/blob/4293e1b15111316b8ef622d04f4e5d8b70ad9474/packages/coverage-v8/src/provider.ts#L157-L171
Or simply not use thresholds in watch mode at all:
// package.json
"test": "vitest run --coverage.enabled --coverage.100",
"test:watch": "vitest watch",

Here’s how I ended up creating this issue.
I was migrating from Jest. In Jest, I run jest --watch while developing and have a separate script that runs jest --coverage like you suggested. I tried replicating that in vitest, but didn’t manage to get the coverage flags working (#4307) so I went with vitest.config.ts instead.
I ran vitest in my project, and all was well. Tests passed, coverage was 100 %. I then made a small tweak to an error message in the library I was working on. vitest then showed me that some snapshots were out-of-date. They looked good, so I pressed u to update them.
Then vitest told me I didn’t have 100 % coverage anymore, and I was confused. It didn’t make sense – the change I had made shouldn’t have resulted in less coverage … or should it? But then I did the classic solve-all-solution: I pressed Enter to run the tests again. Then they passed.
This then happened a couple of times more, and I still couldn’t figure out why. Knowing that vitest is 0.x, I was thinking maybe there’s a bug around watch mode and code coverage (I’ve written watch modes for CLI tools myself, and they can be pretty tricky).
After a couple of days I finally understood what was happening. When pressing u to update a snapshot, vitest writes to some .test.ts files and then its watcher picks up those changes and only re-runs those files, and then all source code isn’t run.
In Jest, I have always used jest --coverage because that’s what I read somewhere once. I haven’t even checked if it’s possible to turn on coverage always in the config file. Now that I had tested having it on always in vitest, I kinda liked it. It’s easy to miss some coverage otherwise during development.
I know that vitest cares a lot about DX – it is the most delightful test runner I’ve ever used – so I thought I’d open this issue to let you know. So now you have the full story from a beginner, and it’s up to you if you think this is good enough, or if you’d like to go the extra mile.

I think we could display an informative message above coverage threshold messages to indicate that not all tests were run so thresholds may be incorrect. We should not disable coverage thresholds completely in these cases as they provide very good feedback to developers who have only a single test covering the file.
 % Coverage report from v8
|----------|---------|----------|---------|---------|-------------------
 File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
|----------|---------|----------|---------|---------|-------------------
 All files |     100 |      100 |      50 |     100 |
  index.ts |     100 |      100 |      50 |     100 |
|----------|---------|----------|---------|---------|-------------------

+NOTE: Only the changed tests were run. Coverage thresholds do not include coverage of all test files.
ERROR: Coverage for functions (50%) does not meet global threshold (100%)

 PASS  Waiting for file changes...
       press h to show help, press q to quit

Or maybe even something like ${testCount}/${allTests} if we have that information available easily:
NOTE: Only 1/52 tests were run. Coverage thresholds do not include coverage of all test files.

That looks good! :+1:

In order to show coverage report of all test files, all test files need to be run.

Completely naively, if my test suites run in isolation and each of them covers a certain set of statements, the full coverage report is given by the union of all of these sets. So, it seems possible in theory that, when I edit a test suite, my test runner could re-run just that one test and take the union of [its new coverage report] + [the cached results of the other tests from the previous run] to produce a full, up-to-date coverage report.
Similarly, if my test runner can tell which tests depend on which modules, as Vitest does, then when I edit a module, it should only need to recalculate the partial coverage reports of the tests that have been re-run.
I don't know what the memory overhead of remembering which tests ran which lines would look like, and I also don't know whether coverage reporters expose that information at all :sweat_smile: But that would be the ideal developer experience, I think!

Yep, sounds possible in theory. At the moment we don't know test file specific coverage so preserving previous results will cause incorrect results when they are merged.
This is where the results are collected:
https://github.com/vitest-dev/vitest/blob/c321a3fd29902fa9295fe219816381884c40a8cd/packages/vitest/src/runtime/runners/index.ts#L86-L99
To preserve the results from previous run you can use coverage.cleanOnRerun in watch-mode.
https://github.com/vitest-dev/vitest/blob/c321a3fd29902fa9295fe219816381884c40a8cd/packages/coverage-v8/src/provider.ts#L278-L279


jsp hook template

take care Greg, this may conflict with #34

hey @AndyWu2015 can you rebase?  I've merged #34


Build pipeline

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: AnneliseD sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


cannot find aurora-postgresql 10.12

hi everyone, I'm trying to run https://github.com/yetanalytics/lrsql/blob/main/dev-resources/template/1_db.yml but AWS returns this issue

Not sure if changing the PostgreSQL version is the right thing to do.
Am I doing something wrong or does the config file need an update?
Thank you

Hi @AltiMario! It looks like 10.12 is EOL per AWS. Try changing it to 10.18, see https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Updates.20180305.html
We provide that template as-is, for demonstration purposes, but we'll put in a ticket to get it updated and tested.


test: test dns.response.answer.name - v1

Test for https://github.com/OISF/suricata/pull/9686.

New PR coming.


Issues using custom list items with an enhanced Select

When using a custom list with an enhanced select we have run into two issues:

Selecting an item correctly floats the label, but the label floats down again when the select loses focus.
The text displayed when selecting an item contains all the text from all the ListItem child elements and no obvious way to override this behaviour (this is certainly an MDC issue.)

Demo: https://codesandbox.io/s/jovial-night-64nbf

Released with 5.7.0


Proper way to send an encoded data

Hi,
I'm trying to send an encoded buffer (array of unsigned char) from a server to a client with an http request. My first attempt was to convert the array of unsigned char to equivalent ASCII string and then send throw the network. for example, suppose this buffer:
unsigned char buffer[] = {72, 101, 108, 108, 111, 32, 119, 111, 114, 108, 100, 0, 24, 1, 32, 1, 40, 0};

And if I convert it to a string I would have this:

Hello world  (

which has null terminating chars and I have problems on the client side to read it back because I can't find the end of the message and reconstruct the buffer. Is there any way to create a string from ProtoBuf output with minimal length?
I found that there is SerializeToString in ProtoBuf but it is missing in NanoPB.

I see you've already asked the same question on StackOverflow ( https://stackoverflow.com/questions/53736331/input-string-consists-of-null-terminating-chars ).
Please wait to see if the answers you get there help you forwards.
Even SerializeToString in C++ protobuf library will have null bytes in the string. C++ strings can store null bytes, while C strings cannot. Encoded protobuf data is always binary data and you have to treat it as such, i.e. don't use string functions on it.

@PetteriAimonen OK, but what is the proper way to send them over a network?

https://github.com/nanopb/nanopb/tree/master/examples/network_server  For example like this example does it.

@PetteriAimonen I saw that example but can't understand how you send an unsigned char array, can you explain a little bit?
@KidVizious Thank you it is a good idea but I don't have enough resource to encode to base64.

@masoudr Obviously, I don't know your resource requirements, but you can Base64 encode with about 50 lines of code.

@KidVizious Thanks, sure I will give it a shot.


Macro for InputValue creation

Resolves #503
Synopsis
We have a graphql_value!() macro which allows Values creation in a convenient way.
We don't have similar for InputValues and Variables, however. Which makes test cases unergonomic, harder to write and read.
Solution
Introduce graphql_input_value!() and graphql_vars!() macros for that purpose.
Additionally
While graphql_value!() exists, it has some inconveniences at the moment:

It accepts None for null values. It would be better to follow serde_json::json!() macro here and accept nulls too instead of None.
It doesn't play well with accepting expressions. In some cases it just fails.

To cover those needs, it is worth to look at how serde_json::json!() is implemented and repeat the simplified version for our needs, both for graphql_input_value!() and graphql_value!() macros.

@ilslv it would be better also to move macros definitions into their own modules.

@tyranron graphql_input_value! should be able to encode InputValue::Variable and InputValue::Enum. GraphQL uses $ prefix to indicate variable: example. But rust declarative macros can't match $, so we could possibly use something like # or @, but it will be hard to remember and it doesn't solve InputValue::Enum. So using let and enum prefixes makes most sense to me:
graphql_input_value!({
    "key": 123,
    "var": let variable,
    "enum": enum ENUM,
    "arr": [123, let another, enum OTHER]
});

@ilslv it's seems that for enums there should be just an ident usage, if we want to comply with GraphQL syntax.
So, we have the following options here:

Either use the variant you've proposed, which is unintuitive and compliant with GraphQL syntax, but it's macro_rules so good IDE assist.
Or implement via proc macro and support syntax for variables as $var and enum values as UPPERCASED_IDENT, but then loose IDE assist.
Or throw support for variables and enums and don't bother at all.
Or throw support for variables only while stringify!(ident) should work for enum values, so we still may use macro_rules for that, and preserve IDE assist.

Considering that this feature is primarily for internal usage, what do you prefer?

@tyranron great idea with ident, completely missed that.
I think we should stick with declarative macros, because of IDE support and much simpler implementation. It may be less robust, but I don't think it has to be, considering usage.
I lean towards stringify!(ident) for enums and #var for variables. It gives us most amount of flexibility and if this macro will become more popular than we expect, we'll be able to rewrite it into proc macro with $var and least amount of breaking changes.

@ilslv ok, let's do this way then.

#var for variables

Maybe @var then? # is usually associated with comments or meta.

FCM
Implement `graphql_input_value!` and `graphql_vars!` macros (#996, #503)

- add `From` impls to `InputValue`, that mirror `Value` impls to provide better support for `Option` handling
- support expressions in `graphql_value!` macro
- use `null` in addition to `None` to create `Value::Null` in `graphql_value!` macro to mirror `serde_json::json!`

@tyranron this PR is ready for review. I've left support for creating Value::Null with None because this feature is part of support for better handling of Options:
#[test]
fn option_support() {
    let val = Some(42);
    assert_eq!(graphql_value!(None), V::Null);
    assert_eq!(graphql_value!(null), V::Null);
    assert_eq!(graphql_value!(Some(42)), V::scalar(42));
    assert_eq!(graphql_value!(val), V::scalar(42));
}


Fix usage

Checklist:

[x] Was this PR discussed in a issue? It is recommended to first discuss a new feature and let the community know whether you are planning or have started working on it before opening a PR.
[ ] Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).
[ ] Update the API documentation if a new function is added or an existing one is deleted.
[x] Added a news entry.

copy news/TEMPLATE.rst to news/my-feature-or-branch.rst) and edit it.

This PR fixes #32


docs/how-to, reference: update Region Merge

What have you changed? (mandatory)
Please explain IN DETAIL what the changes are in this PR and why they are needed:

This PR added the documentation for Region Merge, including

a Region Merge topic under how-to
update on existing PD Control reference

What are the type of the changes? (mandatory)
The currently defined types are listed below, please pick one of the types for this PR by removing the others:

Doc update

@Connor1996 @Hoverbear PTAL again. Thanks.

@Hoverbear  PTAL and merge. thanks.


Links redirects to 404 page

When I try to download this project in website, the links below redirect me for 404 page.
http://imagehover.io/bicexternal/https://github.com/ciar4n/imagehover.css/archive/master.zip
http://imagehover.io/bicexternal/https://github.com/ciar4n/imagehover.css

Hello
This appears to be an issue if you have accessed the site via the Frontend Buzz news letter. To amend try accessing imagehover.io directly.. http://imagehover.io/
Ciarán


Data Model Review - New Process Test

Original Profile

Link to Powerpoint for review: Borehole Profile
Please use Review Tab in the powerpoint file to add NEW issues as comments (not additional boxes). Check existing comments boxes to add to the discussion on existing issues before creating new issues.Please reply to this comment with subjects of issues raised on powerpoint to track review progress.
@GSQ-AI

Added Comments:
Borehole Drilling Method - Intent and Definition

@DavidCrosswellGSQ
Please see above comments for new method to collaboratively comment and review data model profiles.

Added a comment:
General - Borehole - Audit trail & scope of document.

Added new slides
Stricter Level 0 diagram
Revised Profile with temporally sensitive elements identified
State Diagrams for Borehole Status and Agent

Proposed revision in Borehole Profile


New User: npm

Please fill the following out:

Name: npm
Homepage url: https://www.npmjs.com
Brand Guidelines/Licensing: https://www.npmjs.com/policies/trademark#why-npm-inc-has-a-trademark-policy
Logo: https://www.npmjs.com/static/images/npm-logo.svg

Note: npm is always lowercase.

Woot! Thanks @zeke @seldo


param binding /1

Fixes #26540
Internal review URL
@martincostello this works for API controllers too, right?

@Rick-Anderson I’m not actually sure if this was lit-up for MVC too or not.


Support VS 2022

I updated one of my repositories to use VS 2022 and MSVC Tools v143 to build, and although I could use the latest "windows-2022" hosted runner to successfully build my solution, CodeQL failed. After digging around I found #821 which is the exact same issue, and from the linked support page it states that VS support is only up to 2019.
Can VS 2022 support be added? Thanks.

For now I reverted my repository back to use VS 2019.

Yes, database creation on Windows 2022 is currently broken. The system libraries in the OS update change some details that CodeQL was depending upon for observing what the build process does. We have some engineers working urgently on getting it to work again, but it's complicated and we have no firm ETA for a fix yet. :-(

This eventually got fixed.


Scaffold: animate the FloatingActionButton with the SnackBar.

This introduces the concept of an Anchor, which you can use to link
transitions together. I've used this in the Fitness and Stocks apps to
link the FAB and SnackBar to animate together by sharing the
SlideTransition.
I also fixed the Scaffold hit testing code to apply sub-widget
transforms, so it works with Transformed nodes.

LGTM w/ globalToLocal call removed...


Ability to delete reminders

Closed with https://github.com/interstateone/remind/commit/cc33aa347b7bffdb2fe1eb774265902e6cfacf5c


support for python-oracledb driver in thin and thick mode - closes #1

Issue #1
Description of changes:
Adds support for the new oracle python driver in thin and thick mode.
see: https://oracle.github.io/python-oracledb/
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@nicolasbaer is this PR blocked on something?

@nicolasbaer ping

@nicolasbaer can you merge this?


test: add fail test '[sqlite] insert with explicit PK value'

fixes #302

I don't understand why ci-db-core-test fail on coverage... 😕
I have changed other files!

It's not failing for low coverage, there is a test failing with MariaDB.

The CI is somewhat flaky. If you get a failure on Windows don't worry about it.


Implement Fortuna as an EntropySource

From @izaera on January 3, 2014 8:7
Copied from original issue: izaera/cipher#35

From @izaera on March 7, 2014 10:13
Example of fortuna in JS: https://github.com/bitwiseshiftleft/sjcl/blob/master/core/random.js

From @izaera on March 7, 2014 8:2
Info on decisions made: http://crypto.stackexchange.com/questions/14816/unpredictability-vs-randomness?noredirect=1#comment30515_14816

From @izaera on March 12, 2014 8:3
Link to Fortuna description: https://www.schneier.com/fortuna.html
Link to paper with theoretical founding (brand new :-)): http://eprint.iacr.org/2014/167


For pinging during communication problems

If you get pinged by this, a communication problem is suspect and I have your Github handle and want you to email me at<EMAIL_ADDRESS>so please do that. I am not doing that lightly.

@blueskyj1337 please get in touch with me, I believe you used an invalid (dead since) email in our first contact.

@WhizvK please get in touch with me, there might be an issue with your account