In-file search does not reveal hidden unchanged regions

Type: Bug
Steps to reproduce:

Configure Diff Editor to hide unchanged regions
Open a file's diff so that parts of it will be hidden
Ctrl/cmd+F and search for something that is in the hidden portions of the document

Expected result:

Found text should be revealed (and some lines around it preverably as well)
Searching for pieces of text/code should make it easy to spot occurrences of the search term immediately

Actual result:

Found text remains in hidden portions of the file, making it difficult to locate it
It took me some time to realize it was hidden; until then I was just searching among the visible portions of the file
Search functionality that does not make it easy to quickly reach found terms becomes frustrating; even more so than having to scan a long document without hidden regions

VS Code version: Code 1.82.2 (Universal) (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:59:47.790Z)
OS version: Darwin arm64 22.5.0
Modes:

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
2, 3, 3

Memory (System)
8.00GB (0.05GB free)

Process Argv
--crash-reporter-id d4b76660-9f36-4272-adde-460b64a90944

Screen Reader
yes

VM
0%

Extensions (81)

Extension
Author (truncated)
Version

vscode-nvm
abu
0.0.1

Bookmarks
ale
13.4.1

vscode-css-modules
and
1.2.3

lit-html
bie
1.11.1

vscode-intelephense-client
bme
1.9.5

mermaid-markdown-syntax-highlighting
bpr
1.5.2

vscode-tailwindcss
bra
0.10.0

vscode-toggle-max-editor
cbu
0.0.2

js-auto-backticks
cha
1.0.0

path-intellisense
chr
2.8.4

package-json-upgrade
cod
2.1.0

meld-diff
dan
1.4.1

vscode-eslint
dba
2.4.2

xml
Dot
2.5.1

es7-react-js-snippets
dsz
4.4.3

gitlens
eam
14.3.0

vscode-html-css
ecm
1.13.1

EditorConfig
Edi
0.16.4

vscode-npm-script
eg2
0.3.29

prettier-vscode
esb
10.1.0

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

copilot
Git
1.115.430

copilot-chat
Git
0.7.1

vscode-pull-request-github
Git
0.73.2023091209

vscode-graphql-syntax
Gra
1.2.2

json2ts
Gre
0.0.6

todo-tree
Gru
0.0.226

debug-visualizer
hed
2.4.0

output-colorizer
IBM
0.1.2

css-to-jss
inf
1.0.7

path-autocomplete
ion
1.25.0

vscode-peacock
joh
4.2.2

sftp
lix
1.12.10

ts-extension-pack
loi
0.3.0

call-graph
Luo
1.1.2

layout-editor
luv
0.0.1

camelcasenavigation
map
1.1.5

syntax-project-pbxproj
mar
0.1.3

git-graph
mhu
1.30.0

dotenv
mik
1.0.1

vscode-docker
ms-
1.26.1

vscode-kubernetes-tools
ms-
1.3.13

isort
ms-
2023.10.1

python
ms-
2023.16.0

jupyter
ms-
2023.8.1002501831

remote-containers
ms-
0.309.0

remote-ssh
ms-
0.106.4

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.81.4

vscode-remote-extensionpack
ms-
0.24.0

powershell
ms-
2023.6.0

remote-explorer
ms-
0.4.1

remote-server
ms-
1.4.3

vsliveshare
ms-
1.0.5883

vscode-react-native
msj
1.12.0

sftp
Nat
1.16.3

back-n-forth
nic
3.1.1

fix-json
oli
0.1.2

tsimporter
pmn
2.0.1

vscode-css-peek
pra
4.4.1

vscode-thunder-client
ran
2.12.1

vscode-yaml
red
1.14.0

jsrelativeimport
rom
1.0.8

partial-diff
ryu
1.4.3

text-marker
ryu
1.11.0

svg-preview
Sim
2.8.3

diff-ui
sol
0.0.5

move-ts
str
1.12.0

vscode-editor-group-minimizer
suh
1.3.2

vscode-mermaid-editor
tom
0.19.1

vscode-mdx
uni
1.4.0

errorlens
use
3.13.0

highlight-matching-tag
vin
0.11.0

console-ninja
Wal
0.0.226

quokka-vscode
Wal
1.0.565

wallaby-vscode
Wal
1.0.370

vscode-todo-highlight
way
1.0.5

fig
wit
0.0.7

vscode-import-cost
wix
3.3.0

pretty-ts-errors
yoa
0.5.2

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
89544117:30613380
showlangstatbar:30737416
962ge761:30841074
a2ce3375:30757347
7ij38806:30736111
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
copilotsettingc:30839828
synctok:30821570
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015:30829745

This seems to have been slightly improved recently, i.e. text is revealed, but together with potentially hundreds of other lines, which is impractical. I guess that only a small fragment of contextLineCount lines surrounding the text should be revealed instead.
The current behaviour can be reproduced in the Monaco Playground.

For clarity, currently the effect in my example is like this:

And what one would most probably expect is this:

Since the whole folding machinery is already in place, I thought it would be an easy fix to reveal just the small fragment around the text instead of those large sections. But if for some reason it's more complicated and the current behaviour is on purpose, then I guess this issue can just be closed, as the original problem seems to be resolved.

@adamsol can you create a new issue? I like the idea, but it is not trivial.


ACM-4357 Fix create cluster catalog card alignment

https://issues.redhat.com/browse/ACM-4357

Remove indent from the ExpandableSection

/test unit-tests-sonarcloud


Improve createSandbox

Closes: https://github.com/metarhia/impress/issues/1419

[x] tests and linter show no problems (npm t)
[x] code is properly formatted (npm run fmt)

Landed in https://github.com/metarhia/impress/commit/c5eb1ba118a1a37855b60638a0d59ffea8c6e9f3


Hyperparams for results reported in the paper

Hello,
is it possible to have hyperparameters values that reproduce the NVRNN and LM results on the PTB dataset ?
Many thanks,
Lucas

Hi,
thanks for the fast response, and for your insight on PTB! is it also possible to get LM paramaters in the standard setting ?

Hi,
thanks for the fast response, and for your insight on PTB! is it also possible to get LM paramaters in the standard setting ?

The configuration of the word language model example will help.

great! thanks again


cgit: 1.2.1 -> 1.2.3

Motivation for this change
cgit now supports lzip and zstd compression.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks!


Clarification about Twin Update Notifications

I raised a question with my team about using device twins, particularly as a mechanism for reporting the last known state of device alarms that can occur.  I was pointed to the linked page.  There are a few notes about twin use that I couldn't sufficiently understand.  The first is:

Note
Reported properties simplify scenarios where the solution back end is interested in the last known value of a property. Use device-to-cloud messages if the solution back end needs to process device telemetry in the form of sequences of timestamped events, such as time series.

I think I understand this and why it might be suggested and how I should decide between twins and device-to-cloud messages but then under device twin notifications, I read something far more difficult to understand:

If the rate of change is too high, or for other reasons such as internal failures, the IoT Hub might send only one notification that contains all changes. Therefore, if your application needs reliable auditing and logging of all intermediate states, you should use device-to-cloud messages.

Of particularly need for clarification is "IoT Hub might send only one notification that contains all changes".
Does this mean the latest set value (or all changes collapsed together to the latest known value)?  Does it mean that we get an ordered list of updates in a batch where the order represents the order with which changes were made on the device?
If this is guaranteed to eventually become consistent with the device software's last reported value for each attribute then this could be acceptable.  It seems this guidance could be cautioning that if the device is updating the local twin every nanosecond that some of those changes will not be transmitted and thereby the listener notified.  That seems something obvious to expect.  On the other hand, it could mean that local device twin updates on the device are queued or even periodically checked.  Modifications in a queue could end up being transmitted and/or received out of order and as a result, the latest reported state could become inconsistent until the next device update.
In the context of an infrequently occurring alarm that last scenario could result in a persistent report of the alarm being active when in fact it was cleared and maybe even validated physically at the device.  I would expect the consequences for user trust in the system to be unacceptable for our particular circumstance.
How can we determine whether we should use the device twin or device-to-cloud messaging for a specific purpose?
IoT Hub users really need to understand exactly what the implications of the system behavior are so that we can make the right decision for our use cases.
Thank you!

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

ID: 8ff6fbb2-5679-a9e7-b9f3-40d638cadae8
Version Independent ID: fa51c99a-0df6-cebf-aecc-b08df5f85454
Content: Understand Azure IoT Hub device twins
Content Source: articles/iot-hub/iot-hub-devguide-device-twins.md
Service: iot-hub
GitHub Login: @wesmc7777
Microsoft Alias: wesmc

@erikerikson Thanks for the feedback. We are actively investigating and will get back to you soon.

Hello @erikerikson,
I am sorry for taking some time getting back to you.

Does this mean the latest set value (or all changes collapsed together to the latest known value)? Does it mean that we get an ordered list of updates in a batch where the order represents the order with which changes were made on the device?

It means that, if the reported property on device side changes too fast, eg: {16:26:01 "buttonclickState":"on" ; 16:26:02 "buttonclickState":"off" ; 16:26:03 "buttonclickState":"on"} , it is not guaranteed that twinChangeEvents will route 3 notification messages ... it can send only 1 notification message with all changes, and the application will need to deal with it. The order should be guaranteed on the batch with timestamps, aka operationTimestamp

It seems this guidance could be cautioning that if the device is updating the local twin every nanosecond that some of those changes will not be transmitted and thereby the listener notified.

All changes will be transmitted though not in real-time. As you well mentioned, local device twin updates on the device are queued if IoTHub cannot handle twinChangeEvents - this is guaranteed if using azure iot device sdk.

How can we determine whether we should use the device twin or device-to-cloud messaging for a specific purpose?

Think of twin notifications as an IoT Hub internal facilitator (free of cost) to route non-critical\non-timesensitive changes on your devices. For critical scenarios and high rate changes you should opt out by D2C messages. Then, since you need ordered messages and reliable alarmistic dashboards, you can implement a similar scenario as this: Order device connection events from Azure IoT Hub using Azure Cosmos DB. In your device-side code you will need to come-up with your customized sequenceNumber so that Cosmos DB Stored Procedure can do something like:
if (sequenceNumber > document.sequenceNumber) {
      ...
      document.sequenceNumber = sequenceNumber;

      console.log('replace doc - ');
      isAccepted = collection.replaceDocument
...

At the end, your backend application will display the status of different properties of your devices based on each document (aka device properties) stored on your Cosmos DB.
Hope this can help clarify some of your questions.
Let us know how can we help further?
Thanks!

Thank you @asergaz, this is very helpful!  Reasonably timely too, I understand there must be many demands on time and attention.
I'd like to verify my understanding:

The order should be guaranteed on the batch with timestamps, aka operationTimestamp

To avoid concerns... (I don't expect an answer of yes and will state what I do expect next)  Are you suggesting the timestamps are the basis of ordering?  i.e. that we should sort any batch we receive by timestamp?  We don't expect particularly high volumes of update by any single device, my goal in engaging with the docs is ensuring the correctness of my mental model of the system and its guarantees.
I would expect the way this would work is that as changes happen and are reported to the Azure IoT Device SDK by the device, that the updates would be enriched for platform purposes (e.g. with a device-local timestamp) and they would be written to an ordered queue and then that queue would be transmitted to IotHub in the order the updates were written to that queue and not removed from the device local queue until receipt is acknowledged by the IotHub (and potentially further enriched).  Given the EventHub (as opposed to EventGrid) mechanism I understand IotHub to use, I would expect order to be maintained in transmission and cloud-side durable storage (for the duration of the retention period) and then delivered via the twin change events subscription in that same order.  I am assuming that the partition key is the deviceId and that as a result reconnections will be consistently ordered due to the use of a consistent write leader/shard.  Is that right?  If the messages were routed directly to a separate EventHub instance (via built-in IotHub routing), I'd expect the ordering to continue to also be maintained by the distribution logic.  Please enlighten me if my expectations don't reflect reality!
To address the link you provided, it seems that reordering based on sequenceId is necessary due to the use of the order-not-guaranteed EventGrid product (was that produced prior to EventHub routing?).  If I'm being really paranoid, I could be concerned that the reconnection being discussed in that article indicates that a device can be reassigned shards when reconnecting and that as a result, reconnection can create a potential reordering event as the logs of two shards get merged.  While our devices do supply a custom sequenceId for each message, we opt to use EventHub which I understand to respect order of delivery (at least based on commit to durable storage/an offset in the log).  Of course, this is why I am asking about the delivery behaviors of the SDK and about any potential delivery reordering risks of transmission to and from the backing infrastructure.
If I missed a document explicitly discussing the chain of guarantees of these systems, I apologize and please link it.  I'm fairly new to Azure and getting my feet under me.
Thank you once again!

Hello @erikerikson , thank you so much for the valuable discussion!

Are you suggesting the timestamps are the basis of ordering? i.e. that we should sort any batch we receive by timestamp?

I cannot think of a more reliable way than to trust on the "operationTimeStamp" , that from my understanding is written using the device-local timestamp itself. I don't have access to the internals of message routing to validate how it is done though... Nevertheless I spent some more time researching and clarified that routing guarantees ordered and at least once delivery of messages to the endpoints (see doc): "This means that there can be duplicate messages and a series of messages can be retransmitted honoring the original message ordering. For example, if the original message order is [1,2,3,4], you could receive a message sequence like [1,2,1,2,3,1,2,3,4]. The ordering guarantee is that if you ever receive message [1], it would always be followed by [2,3,4]."
Even greater is that device twin notifications, needs you to create a route and to set the Data Source equal to twinChangeEvents. So, you will have the guarantee of ordered and at least once delivery of the notifications :).

I am assuming that the partition key is the deviceId and that as a result reconnections will be consistently ordered due to the use of a consistent write leader/shard. Is that right?

Yes

To address the link you provided, it seems that reordering based on sequenceId is necessary due to the use of the order-not-guaranteed EventGrid product (was that produced prior to EventHub routing?)

No, EventGrid was available after EventHub. Yes sequenceId on the link I've provided is necessary due to the use of the order-not-guaranteed EventGrid product.
Though, like confirmed above, order is guaranteed and at least once delivery for message routing. When using an EventHub as the endpoint (see here): "For handling message duplicates, we recommend stamping a unique identifier in the application properties of the message at the point of origin, which is usually a device or a module. The service consuming the messages can handle duplicate messages using this identifier." I am not an expert on EventHub, therefore I am not sure if it needs that unique identifier and what should be it's name?
Hope it helps clarify. Do you still believe we need to enhance this doc?
Thanks!

Thank you @asergaz - another very helpful and very appreciated response.  In order, at least once transmission was exactly what I was hoping for.  Our monotonically increasing sequenceId makes idempotence trivial.
I might suggest the following modification:

IoT Hub might send only one notification that contains all changes".

to read:
"IoT Hub might send multiple update messages in a single notification"  (a link to the format documentation would be very useful to ground this, probably here: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-event-grid#event-schema, to ground this).
As we've discussed it now, the fact that there is a message per update/other type of event and then a message that is the notification which might normally contain only a single change message but under other conditions (as described) could contain multiple events (including twin updates) messages is pretty clear.  My attempt to rephrase is trying to draw the distinction between the different message types/groundings to make it more clear but I'm not convinced mine is necessarily better.  Definitely my failure to originally understand that distinction was at play in my confusion.  Thank you very much for clearing it up.
It seems to imply that delays will happen if the rates described in the limits occur, not to mention "internet weather".
Taking a step back, having read that document and particularly also https://github.com/microsoft/azure-docs/blob/master/articles/iot-hub/iot-hub-devguide-d2c-guidance.md (which was linked at the top), it's become clear that a big part of my confusion was my only dipping my toes in the docs while splitting my focus over a set of things.  Thank you for being gracious about this.  I've attempted to explain the source of my confusion but this is a high context subject and understanding the text properly required some context/synthesis for me.
On that note, thanks for calling out my knee-jerk assumption about timestamps, which are generally reliable from a single (well designed) clock (as opposed to across them), particularly if you have guaranteed order maintenance to deal with identical timestamps.  ;D
Please feel welcome to close this or leave it open to take action as you see fit.  Thank you very much!

It was a pleasure to discuss this with you @erikerikson ! A great learning for me to :). I will proceed and close this issue for now. Others will have access to this issue\discussion if they ever come to similar questions as yours :). @wesmc7777 will definitely be on top of this doc for any doc-enhancements needed based on valuable feedback as yours.
Please enjoy using Azure IoT Hub and feel free to reach out for any other questions on the forums listed in Azure IoT support and help options.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[WIP] Naive attempt to build universal2 wheels as well on github per https:…

…//cibuildwheel.readthedocs.io/en/stable/faq/#universal2
Pylibmagic wants to build as a purepy wheel -- do we actually need python-magic built here as universal2 instead?

Maybe it's easier to add this upstream at https://github.com/kratsg/pylibmagic/blob/main/pyproject.toml ?

I did try that already as well, but i haven't figured out how to get a m1 version of libmagic installed. Maybe we should rent a M1 instance and just build m1 wheels there, instead of universal2 ?

(in https://github.com/mvdbeek/pylibmagic/runs/6715461801?check_suite_focus=true#step:3:460 )

Yeah, I saw (in the doc linked) "Here's an example GitHub Actions workflow with a job that builds for Apple Silicon:" and thought this might just work.  But without actual m1 runners installing libmagic, I guess it won't.  Someday!  Closing this for now.


Add unit test of aria-expanded to dropdown suite

Add test for aria-expanded to dropdown unit tests

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: b441658d791683597d4f110beb828e277e7e539a
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/51869037
(Please note that this is a fully automated comment.)

Rebased to use propEqual instead of equal to ensure it is a strict type and value check.

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: 0a0d3033a8eea0cf4dcb757b5669b0cc88d4823b
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/51871033
(Please note that this is a fully automated comment.)

Perhaps I'm mistaken, but it seems like strictEqual would make the most sense.

strictEqual is also what we use elsewhere in the unit tests, FWIW.

Rebased to StrictEqual — sorry used to karma and apparently didn't read down far enough in the QUnit api docs.

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: 843bc35bc5a38cc0d5bfd81fcab2b5237680838d
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/51980322
(Please note that this is a fully automated comment.)

This broke when rebasing with the updates to QUnit were made. Need to remake this.


Security Issue: Ledger does not check operation mode and signs transaction for any coin in any mode

Nano Ledger S displays incorrect destination address when bitcoin wallet used in test-net mode. It displays main-net style adress (1...), instead of test-net one (m...). Everything else seems to work fine: amount and fee displayed correctly and transaction get signed. However, displaying main-net address may scare user away if he stores both main-net and test-net coins in the wallet.

Yes, there are two ways to fix that : either build the BTC app (https://github.com/ledgerhq/blue-app-btc) with COIN=bitcoin_testnet or invoke SET ALTERNATE COIN VERSION (https://github.com/LedgerHQ/blue-app-btc/blob/master/src/btchip_apdu_set_alternate_coin_version.c) in your code to set the new value (APDU would be E014000005006F00C401)

@btchip Thank you for your reply!
Actually, it not my code. I have been testing Electrum and Mycelium wallets in test-net mode. I will report this issue to them and send link to your reply.
However, I think that it is a big security issue, that Ledger allows to sign transaction for any coin in any mode. I have made more tests, and was able to send bitcoin while Ledger was in DASH mode. Hardware wallets promise that you can use them even on infected computer and your coins will be safe. But this issue kills this promise. Consider following scenarios:

Buggy multi-currency wallet. You request to send 10 DASH, but wallet for some reason creates transaction which sends 10 BTC to BTC address with same derivation path as DASH you requested. In this case Ledger will ask you to confirm to send 10 DASH to correct address, but will sign transaction which sends 10 BTC.

Malicious shop. You come to the shop and want to pay with your Ledger there. They offer you to connect Ledger to their wallet to make payment and you agree, because it should be safe, since it is hardware wallet and you confirm transaction on device yourself. Then they generate DASH and BTC addresses with same derivation path from the same BIP39 seed, Ledger in DASH mode shows you DASH address, you confirm, but they sign BTC transaction for the same amount and broadcast it. They will be able to spend BTC since they have private keys for both addresses (BTC and DASH).

Ledger should check in which mode it running and sign transaction only for corresponding network. I hope you can fix this issue in the next firmware update.

Thanks for the report - such control can be added easily in the application (no need to wait for a firmware update). I'll think a bit about it to support it in a way that doesn't make BIP 44 mandatory.

@btchip Great! Let me know when application updates will be available. Thank you!

@btchip Regarding BIP 44, one solution could be to add (on by default option) to enforce BIP44. Allow user to disable it if he wants to use non standard derivation paths (after showing security warning). Or even better, allow user to add custom derivations paths (per coin) without disabling BIP44 checks completely.

The way I plan to do it is to check BIP 44 coin type when it's used (through an API accepting a signed blob linking the coin type to the other former ALTERNATE COIN parameters). Non BIP 44 derivation will still be allowed without security prompts, otherwise it'd get too confusing for many third party services (mostly those using different scheme for multisignature services)
This doesn't prevent malicious services from accepting deposits on a non BIP 44 path then spend on a different coin on the same non BIP 44 path, but at that point the community should blacklist them quickly.

@btchip Few more thoughts regarding this issue:

It would be great to protect public keys for BIP44 derivations as well. Applications able to get BTC public keys (so they can check balances) without any confirmations when ledger is connected in altcoin mode.

BIP49 derivations should be protected as well (SegWit addresses).

Similar problem exists for ETH, ETC, ETH tesnets, RSK testnet. There is no way to tell which one coin is used. Ledger displays just ETH for all of them. This is a serious issue, because market price for ETH and ETC is 20 fold difference now.

There should be option to display derivation path for advanced users. Otherwise how do you expect community would  blacklist malicious services quickly?

Alternatively way of protecting keys: Generate different keys for every altcoin by specifying altcoin name as seed password phrase. If users specifies his own password phrase, then add both strings. Eg., LTC seed password phrase "apple" would become "LTCapple". Document this behaviour and prompt user which method he want to use during seed restoration (this one as more secure, or original for users who transfered coins already to seed generated with it).

Could you describe how SSH and PGP keys derived form BIP39 seed? Is there any chance that they can reveal any information about coin keys?

@btchip Any updates here?  There are some good questions from @yura-pakhuchiy which are unanswered since June. :/

We're redesigning many things around the locking mechanism and the way the client application interacts with the device. Should be available around Q1 2018.

After 3 years Ledger seems fixed the issue after someone: made more noise about it
https://www.ledger.com/updating-the-bitcoin-app-to-enhance-security


[Dubbo-nondeterministic iteration order] Use ConcurrentLinkedHashMap for deterministic iteration order

What is the purpose of the change
The test org.apache.dubbo.common.bytecode.WrapperTest#test_getMethodNames_ContainExtendsParentMethods can fail due to a different iteration order of ConcurrentHashMap. The failures are as follows:
[ERROR] test_getMethodNames_ContainExtendsParentMethods  Time elapsed: 0.03 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: array contents differ at index [0], expected: <hello> but was: <world>                                                                     at org.apache.dubbo.common.bytecode.WrapperTest.test_getMethodNames_ContainExtendsParentMethods(WrapperTest.java:125)

The fix is to change it to a ConcurrentLinkedHashMap(ref) so that the iteration order remains stable and the failure will not occur any more. In this way, the test will be more stable.
Brief changelog
use ConcurrentLinkedHashMap instead of ConcurrentHashMap
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[x] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[x] If this contribution is large, please follow the Software Donation Guide.

Currently, there is a lru implementation in Dubbo. You can refer LRUCache.
How about change to it?

Close for long time no response.
Please feel free to reopen if you have any question.
If you think these changes still useful in the latest master branch, please submit a new pull request.


feat: add ethereumjs to nightly runners

Changelog picked up from commits here:
feat: add ethereumjs to nightly runners

Depends on https://github.com/kurtosis-tech/eth-network-package/pull/107


chests not rendered

Chests don't render in my screenshots, is there any reason why? and or can i activate it somewhere?

glisco is working on block + entity support, chests will be able to be rendered properly soon. For now you can use Enhanced Block Entities mod


Replace PayPal donations with Gratipay

Something to consider: https://gratipay.com/radiant-player/

Our project has been approved!

Our project has been approved!

@radiant-player/radiant-player-mac any thoughts?

@radiant-player/radiant-player-mac any thoughts?

@jacobwgillespie Maybe something like Square Cash too, love that service!

@jacobwgillespie Maybe something like Square Cash too, love that service!

I've not used gratispay before. How did it work?

I've not used gratispay before. How did it work?

@jadengore Square Cash is awesome, though not sure how it'd work in our context...
@chrismou essentially people contribute a certain amount of money per month (could be a super small amount) and that money is owned by the "organization" account.  Eventually people who work on the project can withdraw that money into their own accounts as part of "payroll" for working on the project.  Kinda the patron model.  Anyways, I say "eventually" because Gratipay is currently reworking the payroll system so for now donations are owned by the org but don't go anywhere (this is temporary as they upgrade from v1.0 to v2.0).  Do check them out though as they're a completely "open" company and kinda fascinating to investigate.

I'll ping @twolfson since he works on Gratipay.  :)

Heh, more like contributed to a few times than "works on". @jacobwgillespie has got most of it right.
In the v1 model, everything aggregates into a main account and then contributors "take when they want".
In v2, they are still building out payroll but I don't know whether they are planning on keeping that model or allowing people to roll their own.
https://github.com/gratipay/gratipay.com/issues/3433
One large benefit for organizations is that all the inbound donations are transparent whereas with tools like Paypal its limited to the account holder.
One large negative is that people need to sign up for an account rather than enter credit card info. Also, it's a recurring payment -- no one-offs =/


Are there any settings? Not clear how to use it...

It wasn't clear from the Readme.md what the suggestion library/dictionary will suggest, whether it will suggest a particular language or terms from body of knowledge or a basic dictionary...?

Understood it is for Latex.

Understood it is for Latex.

Hello @viaahmed,
As stated in the readme, this plugin is still WIP, so I've done only a tiny part of what I have in mind to do (that's why there aren't settings, ...).
Since I created this plugin mainly to suggest latex functions, that's the main feature for it, as of now. Later on, I will add different providers (most used words into the current file, custom file given by the user, ...) and the user will be able to enable them individually, based on needs.
Let me know what priorities I should give to the features, given also the TODOs in the README.
Unfortunately, right now I am in the middle of the exam session so the development is slowed down.

Hello @viaahmed,
As stated in the readme, this plugin is still WIP, so I've done only a tiny part of what I have in mind to do (that's why there aren't settings, ...).
Since I created this plugin mainly to suggest latex functions, that's the main feature for it, as of now. Later on, I will add different providers (most used words into the current file, custom file given by the user, ...) and the user will be able to enable them individually, based on needs.
Let me know what priorities I should give to the features, given also the TODOs in the README.
Unfortunately, right now I am in the middle of the exam session so the development is slowed down.

No problem, take your time, Thanks for the efforts 🙂😊

No problem, take your time, Thanks for the efforts 🙂😊

Would it be possible to add a general autcomplete function with all words in the current file like in Sublime Text?

Yeah, it is in the Roadmap, @yeboster told me.
On 2/17/21, phlind<EMAIL_ADDRESS>wrote:

Would it be possible to add a general autcomplete function with all words in
the current file like in Sublime Text?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/Yeboster/autocomplete-obsidian/issues/3#issuecomment-780402406

Hello,
I've almost finished the exam session so the development will start soon 👍
@phlind yes, I've already started to develop the settings tab locally, but I'm thinking of what is the best architecture to manage everything correctly.

Settings tab has added in last releases. Closing the issue.


Wrong emoji

In my db I have the sad emoji
![Image of sad]
(http://i.imgur.com/Hw8Rd0t.jpg)
But using this code:
emojify(Rumoji.encode(comment.content))

I get this emoji displayed
![Image of the wrong emoji]
(http://i.imgur.com/FtJHoM5.png)
Usually it work but not for the decoding of this smiley (Have been using the plugin for 2 weeks so I may find other wrong smiley in the future)
Here is the information I could get about the smiley in db:
![Image info]
(http://i.imgur.com/k9LwuIP.jpg)

This does not appear to be a bug in Rumoji:
comment = "oh no!!😢"
Rumoji.encode(comment)
#=> "oh no!!:cry:"
Rumoji.decode(Rumoji.encode(comment))
#=> "oh no!!😢"
Rumoji::Emoji.find(:cry).hex
#=>"1F622"

Would seem to me that emojify might be the culprit here


Main logo overflows on mobile

To repro
Visit the home page on mobile.
The logo should be overflowing over the nav bar
It should not be overflowing

Fixed in #509


chore(perf): ignore package-lock.json file

Informations

Type
Breaking change

Chore
Yes

Description
I added the package-lock.json file to the gitignore file.
Revise Only gitignore file
Todos

[ x ] Tests
[ x ] Coverage
[ x ] Example
[ x ] Documentation

From: https://docs.npmjs.com/files/package-lock.json

This file is intended to be committed into source repositories

Thanks @swtpumpkin for your PR but as had explained @cyrixmorten the package-lock must be committed  ^^.
See you


fix(linter): workaround non local workspace

Fix #536

I will test this as well, I was able to replicate the issue.

For me the same issue happened:

Did you test it as well?

@felipecrs  Yes, however I encountered the error just during shellcheck process spawn.
Since we are using bundled shellcheck, so I guess ENOENT occurred when we are using an invalid working directory.

Now it works for me too!

Now I've restored th original prettier config. And add a another fix for file matchers

I think we can also rename the PR to something like:
fix: not working together with the SSH FS extension

WDYT?

I just renamed this PR title, I think after squash the title will be used instead of the original commit messages.


What is the difference between meteredService in InfoFields and MeterCategory for usage API?

When I query using the usage API as follows:
https://management.azure.com/subscriptions/<subscription_id>/providers/Microsoft.Commerce/UsageAggregates?api-version=2015-06-01-preview&reportedStartTime=2015-06-01&reportedEndTime=2015-08-19&aggregationGranularity=daily&showDetails=true
one of the usage aggregates I get is as follows:
    {
        "id": "/subscriptions/<subscription_id>/providers/Microsoft.Commerce/UsageAggregates/Daily_BRSDT_20150601_0000",
        "name": "Daily_BRSDT_20150601_0000",
        "type": "Microsoft.Commerce/UsageAggregate",
        "properties": {
            "subscriptionId": "152a5174-2ead-46e5-804d-053bf15ca286",
            "usageStartTime": "2015-08-18T00:00:00+00:00",
            "usageEndTime": "2015-08-19T00:00:00+00:00",
            "meterName": "Data Transfer In (GB)",
            "meterRegion": "Zone 1",
            "meterCategory": "Networking",
            "unit": "GB",
            "meterId": "32c3ebec-1646-49e3-8127-2cafbd3a04d8",
            "infoFields": {
                "meteredRegion": "Central US",
                "meteredService": "Compute",
                "meteredServiceType": "External",
                "project": "ubuntu-server-p8y4lkv4(ubuntu-server-p8y4lkv4)"
            },
            "quantity": 0.000525
        }
    }

Here, as you see, I have something called a meteredService which is compute and meterCategory which is Networking, two completely different service types.
What do the two indicate? What is the correct interpretation of the two fields. In the documentation, I see meterCategory is defined as:

Category of the consumed resource.

However, there is no definition for meteredService and that infoFields will soon be deprecated.

Hi again Jobin :)
Infofields.meteredService is something that legacy resource providers have been providing to give more details about the resource consumed, and this is not enforced between providers and this version of the metadata is not necessarily in sync with the metadata that we show in the marketing pages.
Therefore, to learn more about what has been consumed, please use the resource metadata fields (meterName, meterCategory, meterSubCategory, meterRegion. unit). The resource metadata will be consistent and from the same source of truth, and most of the resource metadata should be present in every response.
Net-net: please take a dependence on the resource metadata and not infoFields to learn more about what has been consumed.


ORC-929: Fix NaN error at orc-tools meta command

What changes were proposed in this pull request?
This PR aims to fix NaN error at orc-tools meta command.
Why are the changes needed?
To fix invalid output
$ orc-tools meta zero.orc 2> /dev/null | grep Padding
Padding length: 0 bytes
Padding ratio: �%

How was this patch tested?
Manual.
$ java -jar tools/target/orc-tools-1.8.0-SNAPSHOT-uber.jar meta ../examples/zero.orc

I landed this to branch-1.6, too.


Removing resize tracking for iOS and Android

Apologies for all the spacing notes; my texteditor automatically removes unnecessary spaces at the end of lines.
This PR changes trackomatic so it won't track resize events on phones. This is an issue because iOS and Android both fire a resize event on scroll (when the menu bar disappears). Updating this logic should make the resize count more reliable.

Heh, good to clean that up.
Thanks for the update.


RPI4 gpioTerminate() Hangs

guymcswain asked me to create a new issue for this - before I was adding comments to issue #478
I'm using pigpio library on a raspberry 4 with a buildroot aarch64 custom image using BusyBox as init system.
Problem:
I had problems with a simple test program, that would work fine when running, but would hang once I called gpioTerminate().
Inspection:
When trying to pinpoint the error, I started with the pigpiod application. The pigpiod application would also hang when I sent it a SIGHUP or SIGTERM signal - although reading the source code it should terminate nicely also using the gpioTerminate() call.
After investigating a bit more with my limited gdb skills, it seems like the fifo interface is causing problems in my case. When I start pigpiod with the -f option, I can stop it with a SIGTERM signal.
Solution:
That means in my program I can use this code to disable the fifo interface and everything works as expected:
gpioCfgInterfaces(PI_DISABLE_FIFO_IF); // call before gpioInitialise()
Calling gpioTerminate() will not hang anymore and I can stop my test program nicely.
Out Words:
In my case this solution is sufficient, because I don't need a fifo interface. I opened this issue to make you guys aware of this and to offer a solution to users that might end up with a similar problem.

I have this exact issue on a Raspberry Pi Zero running Alpine. I'd assume this occurs on all Pi's then, unfortunately.

You should try the ‘develop’ branch; It has an improved signal handler.

I'm glad it resolved your issue.  I probably will.  I was waiting for some feedback and then sort of lost interest for a while.


Copy the text output for suggested indexes from "Explain" query

When evaluating which indexes to create, SQL Server comes with good suggestions when using "Explain" in the query editor. However these suggestions cannot be copied, as text can not be selected from the "Query plan" tab.
Describe the solution or feature you'd like
If the text was selectable, it would be a benefit to copy the output
Describe alternatives you've considered
I have written the text manually, because i could not select it. I also considered taking a screenshot and running it through OCR, so I would not have to type everything out.

We have a new extension coming out that you might want to try. Stay tuned for July release.

Hi! @yualan what about the extension. I'm looking forward to try it. It would be so great if I it works similar as works on SQL Server Management Studio where you can click on right button and click on "Missing Index Details" option that open a new tab with the SQL of the recommended Index.
Regards!

Any update on this?

This is fixed in the new execution plan feature. You can just click on the recommendation, and it will open the missing index query in a new window.


nested define: ERR out

I tried this: nested define:
rs.lisp:
; if these defines are not nested, it works.
; (define take (lambda (n seq) (if (<= n 0) (quote ()) (cons (car seq) (take (- n 1) (cdr seq))))))
; (define drop (lambda (n seq) (if (<= n 0) seq (drop (- n 1) (cdr seq)))))
; (define mid (lambda (seq) (/ (length seq) 2)))

(define combine (lambda (f)
        (lambda (x y)
          (if (null? x) (quote ())
              (f (list (car x) (car y))
                 ((combine f) (cdr x) (cdr y)))))))

; but not inside:
(define riff-shuffle (lambda (deck) (begin
      (define take (lambda (n seq) (if (<= n 0) (quote ()) (cons (car seq) (take (- n 1) (cdr seq))))))
      (define drop (lambda (n seq) (if (<= n 0) seq (drop (- n 1) (cdr seq)))))
      (define mid (lambda (seq) (/ (length seq) 2)))
      ((combine append) (take (mid deck) deck) (drop (mid deck) deck)))))

(riff-shuffle (list 1 2 3 4 5 6 7 8))

unbound take ERR 3 unbound symbol:
6322+1929>(load "rs.lisp")
(load "rs.lisp")
combine
riff-shuffle
unbound take ERR 3 unbound symbol

6024+1921>(riff-shuffle (list 1 2 3 4 5 6 7 8))
unbound take ERR 3 unbound symbol

the correct output should be:
> (load "rs.lisp")
> (riff-shuffle (list 1 2 3 4 5 6 7 8))
(1 5 2 6 3 7 4 8)

Indeed, you cannot use nested defines and I know this to be the case. This lisp does not copy common lisp or other dialects. You can use let and letrec to define local bindings to functions,lambdas.

OK, thanks for the info. But after I changed to let it still error out:
$ cat rs.lisp

; (define take (lambda (n seq) (if (<= n 0) (quote ()) (cons (car seq) (take (- n 1) (cdr seq))))))
; (define drop (lambda (n seq) (if (<= n 0) seq (drop (- n 1) (cdr seq)))))
; (define mid  (lambda (seq) (/ (length seq) 2)))

(define combine (lambda (f)
        (lambda (x y)
          (if (null? x) (quote ())
              (f (list (car x) (car y))
                 ((combine f) (cdr x) (cdr y)))))))

(define riff-shuffle (lambda (deck) (begin
      (let take (lambda (n seq) (if (<= n 0) (quote ()) (cons (car seq) (take (- n 1) (cdr seq))))))
      (let drop (lambda (n seq) (if (<= n 0) seq (drop (- n 1) (cdr seq)))))
      (let mid (lambda (seq) (/ (length seq) 2)))
      ((combine append) (take (mid deck) deck) (drop (mid deck) deck)))))

(riff-shuffle (list 1 2 3 4 5 6 7 8))

$ ./lisp
...
6322+1929>(load "rs.lisp")
(load "rs.lisp")
combine
riff-shuffle
ERR 1 not a pair

(let (take (lambda ...))  (drop (lambda ...))  and so  on, is the syntax of let in this lisp.
Lisp syntax is not forgiving and this lisp has no compile-time syntax checks and errors.

Sorry about the syntax error.
I change it to:
(define combine (lambda (f)
        (lambda (x y)
          (if (null? x) (quote ())
              (f (list (car x) (car y))
                 ((combine f) (cdr x) (cdr y)))))))

(define riff-shuffle (lambda (deck) (begin
      (letrec* ((take (lambda (n seq) (if (<= n 0) (quote ()) (cons (car seq) (take (- n 1) (cdr seq))))))
             (drop (lambda (n seq) (if (<= n 0) seq (drop (- n 1) (cdr seq)))))
             (mid  (lambda (seq) (/ (length seq) 2))))
      ((combine append) (take (mid deck) deck) (drop (mid deck) deck))))))

(riff-shuffle (list 1 2 3 4 5 6 7 8))

and verified with the other interpreter to get verified:
> (riff-shuffle (list 1 2 3 4 5 6 7 8))
(1 5 2 6 3 7 4 8)

Now I run this lisp again, it still error out with different error:
6068+1921>(riff-shuffle (list 1 2 3 4 5 6 7 8))
unbound drop ERR 3 unbound symbol

The README says that all let use a different syntax than commonlisp. You don't need to put the bindings in a list. The let special forms are tested and work fine. Note the syntax in this example:
(letrec* (x 4) (f (lambda (n) (if (= n 0) 1 (* n (f (- n 1)))))) (f x))
Also, I recommend to use (trace) with some small input to find out where something goes wrong in your code.

Thanks. Indeed, this worked:
(define riff-shuffle (lambda (deck) (begin
      (letrec* (take (lambda (n seq) (if (<= n 0) (quote ()) (cons (car seq) (take (- n 1) (cdr seq))))))
             (drop (lambda (n seq) (if (<= n 0) seq (drop (- n 1) (cdr seq)))))
             (mid  (lambda (seq) (/ (length seq) 2)))
      ((combine append) (take (mid deck) deck) (drop (mid deck) deck))))))


Fix: #5. Build with docker.

This PR
builds with docker locally

@netfl0  you welcome! Give it a spin, since I just ran it on my laptop :) You can probably create a github-ci out of it using a gh-action that just runs docker-compose up :)


Specify a config file, or cluster to use directly from the command line

Is your feature request related to a problem? Please describe.
When working with the CLI in an automation space, being able to define a specific config file or cluster options directly when running commands
Describe the solution you'd like
Be able to either specify the path to a custom config file
lagoon --config-file /path/to/config.yml list projects

or the main config options for api/ssh access, which will ignore any config files
lagoon --graphql https://api.example.com/graphql \
  --token "ey...xyz" \
  --port 2020 \
  --hostname ssh.example.com \
  list projects

it would be awesome to also be able to specify this via an environment variable.
basically the same way kubectl has the KUBECONFIG environment variable.

Definitely!


new sensor WH57 lightning not recognized

Hello, the sensor WH57 is not included:
Error messages from home assistant:
Unhandled sensor type lightning_time value , file a PR.
Unhandled sensor type lightning_num value 0, file a PR.
Unhandled sensor type lightning value , file a PR.
Unhandled sensor type wh57batt value 3, file a PR.
Raw data sent by ecowitt:
raw data: PASSKEY=XXXX&stationtype=GW1000B_V1.6.1&dateutc=2020-07-17+20:32:47&tempinf=73.8&humidityin=60&baromrelin=29.864&baromabsin=29.864&tempf=74.8&humidity=58&soilmoisture1=51&soilmoisture2=42&soilmoisture3=42&lightning_time=&lightning_num=0&lightning=&wh26batt=0&soilbatt1=1.5&soilbatt2=1.5&soilbatt3=1.5&wh57batt=3&freq=915M&model=GW1000
raw packet: {'dateTime':<PHONE_NUMBER>, 'usUnits': 1, 'temperature_in': 73.8, 'humidity_in': 60.0, 'pressure': 29.864, 'temperature_out': 74.8, 'humidity_out': 58.0, 'soil_moisture_1': 51.0, 'soil_moisture_2': 42.0, 'soil_moisture_3': 42.0, 'lightning_time': 0, 'lightning_strike_count': 0.0, 'lightning_distance': 0, 'wh26_battery': 0.0, 'soilBatt1': 1.5, 'soilBatt2': 1.5, 'soilBatt3': 1.5, 'wh57_battery': 3.0}
Sorry, new sensor, so I didn't have lightning yet!

OK, I'm putting these in as integers for now.  If you ever get a strike, the raw data would be extremely useful, to make sure I'm not hosing the data...

Please try the new version (master).  There is a possibility it will crash if it turns out one of those values is a float though, if so, please let me know and I will fix asap.

Here's what the output looks like for strikes on this...
These are the sensors:
2020-09-04 12:15:58 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_time
2020-09-04 12:15:58 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_num
2020-09-04 12:15:58 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning
2020-09-04 12:15:58 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type wh57batt
Sample of Multiple Strikes.... I live in Tampa...lightning capital or so they say... :) please let me know if you need anything else. Thank you so much for your contributions.
2020-09-04 12:17:28 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_time value<PHONE_NUMBER>, file a PR.
2020-09-04 12:17:28 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_num value 2, file a PR.
2020-09-04 12:17:28 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning value 20, file a PR.
2020-09-04 12:17:28 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type wh57batt value 5, file a PR.
Sample 2
2020-09-04 15:42:14 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_time value<PHONE_NUMBER>, file a PR.
2020-09-04 15:42:14 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_num value 3, file a PR.
2020-09-04 15:42:14 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning value 20, file a PR.
2020-09-04 15:42:14 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type wh57batt value 5, file a PR.
Sample 3
2020-09-04 21:47:48 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_time value<PHONE_NUMBER>, file a PR.
2020-09-04 21:47:48 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning_num value 7, file a PR.
2020-09-04 21:47:48 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type lightning value 20, file a PR.
2020-09-04 21:47:48 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type wh57batt value 5, file a PR.

Needs testing.. Will check..

@garbled1 Awesome, please feel free to reach out if you need any help with testing. Thanks.

Yes, I'll publish a new release today/tomorrow once I do some basic testing.  But be aware the new release needs 115 or later of HA.

@gilperme One question.. do you happen to know if the strike timestamp is in UTC?

@garbled1 the latest time stamp shows as<PHONE_NUMBER> which in epoch translates to 1:49:57 AM EST which is the last time reported on the app itself, so it appears it's sending it ETC.

Oh thank goodness. I had literally no idea how I would fix it if it was localtime to the device.  This makes it so much easier.

Actually.. do you have an opinion:
I'm thinking of implementing this as an "age".  Like it would display time since last strike, rather than time OF last strike. Opinion on which you would rather have?

Personally,  I don't want to give you more work...really do appreciate what you're doing here, but I think that the time stamp is best...just thinking ahead if you want to drop this into a grafana dashboard or look at data after a period of time, you're going to have to do some number juggling to get it accurately represent the information over time. Just my two cents.

Nope.  Grafana is a fair use, and one I'm actually 99% likely to actually use.
I just pushed in 0.3.2 release.  If your HA is running at least 0.115, please update to this.  If it breaks you, roll back to 0.3.1.  In theory, lightning should work now?

Ok will give it a try, I'll keep you posted. Thanks for all the work!

Ok so far it looks good, sensors setup fine (see log) and the UI is showing them as expected (see attached). Nicely done! I checked the data on the app to verify it matches. Please let me know if you need anything else. I'll keep you posted if anything happens.

Oh very nice!  I'll have to double check why you are getting both miles and km, but it's good to know its working!

Fixed in 0.4.  Thank you!

Installed .4, metric is gone as expected. Looks good so far, thank you for all of your contributions.


Should --dont-left-align-indels and bamleftalign be hidden ?

Just a thought.

Not sure. What do you mean?
On Jun 14, 2015 12:28 AM, "Torsten Seemann"<EMAIL_ADDRESS>wrote:

Just a thought.
—
Reply to this email directly or view it on GitHub
https://github.com/ekg/freebayes/issues/175.

It's one year later, and I'm not sure what I meant!


Merge ign-gui6 ➡  main

➡  Forward port
Port ign-gui6  ➡  main
Branch comparision: https://github.com/ignitionrobotics/ign-gui/compare/main...ign-gui6
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

I found a couple more renaming places. Do we need to move include/ignition/gui/* to include/gz/gui? Also, are we renaming IgnHelpers.qml to GzHelpers.qml?

Nice catch, I'll look into that soon

Do we need to move include/ignition/gui/* to include/gz/gui? Also, are we renaming IgnHelpers.qml to GzHelpers.qml?

Ahh I forgot that those were duplicated. Fixed in 593ccb0680a6b8890cd0e7b8cab6421bccbcbda8. I'd like to revisit that eventually and see if we can get away without duplicated files.

I can reproduce the HFOV test failure locally, but I haven't figured out how to fix it:
   /github/workspace/test/integration/minimal_scene.cc:158: Failure
  The difference between 60 and camera->HFOV().Degree() is 15.009121067327513, which exceeds 1e-4, where
  60 evaluates to 60,
  camera->HFOV().Degree() evaluates to 75.009121067327513, and
  1e-4 evaluates to 0.0001.

It looks like the aspect ratio is changing in the middle of the test, so the HFOV changes. @AzulRadio @jennuine , any tips?

Currently, I think there is a bug in gz-rendering. This line here seems to be the source of the issue: https://github.com/gazebosim/gz-gui/blob/6059daacf60fcadfaee952806a710342eb4f1b2e/src/plugins/minimal_scene/MinimalScene.cc#L321
Looking at camera->HFOV() before the camera->PreRender() call, the HFOV() returns 60 degrees. After camera->PreRender() it returns 75.0091 degrees, which cases the test to fail. I'll take a closer look at gz-rendering tomorrow

Looking at camera->HFOV() before the camera->PreRender() call, the HFOV() returns 60 degrees. After camera->PreRender() it returns 75.0091 degrees

Thanks for the lead, @jennuine ! I believe the issue is that we were setting the aspect ratio every time the texture is dirty, but now that we want to keep a constant FOV, we should be setting that instead. Also since https://github.com/gazebosim/gz-rendering/pull/635 the aspect ratio is updated automatically with the SetImage[Height|Width] calls.
See the fix in c7cac24 and let me know if you're ok with it. The test passes now, and I checked locally that resizing a window behaves correctly.

Are we still deprecating gz-sim scene3d? If not, we should update it too (and update the deprecated warning version numbers)l: https://github.com/gazebosim/gz-sim/blob/ff101099698da7795fe25f9c03b0bc34a7a25f5e/src/gui/plugins/scene3d/Scene3D.cc#L688-L689

Are we still deprecating gz-sim scene3d?

Yup, that's being removed in

https://github.com/gazebosim/gz-sim/pull/1605


examples/windowsize: pressing N to minimizes causes app to freeze

Ebitengine Version
@d15b12b4
Operating System

[ ] Windows
[X] macOS
[ ] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] PlayStation 5
[ ] Xbox
[ ] Web Browsers

Go Version (go version)
go version go1.22.1 darwin/arm64
What steps will reproduce the problem?
Press 'N' after running examples/windowsize
What is the expected result?
To minimize but still be runnable.
What happens instead?
The app freezes and becomes unresponsive even after returning focus.
Anything else you feel useful to add?
No response

The app freezes and becomes unresponsive even after returning focus.

It depends. You have to call SetRunnableOnUnfocused(false).

Oh? I'll try

I failed to reproduce this.
                    'c<EMAIL_ADDRESS>                 ,xNMM.          -------------------------------------
               .OMMMMo           OS: macOS 14.2.1 23C71 arm64
               OMMM0,            Host: Mac15,6
     .;loddo:' loolloddol;.      Kernel: 23.2.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Uptime: 59 days, 42 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    Packages: 77 (brew)
 XMMMMMMMMMMMMMMMMMMMMMMMX.      Shell: zsh 5.9
;MMMMMMMMMMMMMMMMMMMMMMMM:       Resolution: 1800x1169
:MMMMMMMMMMMMMMMMMMMMMMMM:       DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.      WM: Quartz Compositor
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.    WM Theme: Blue (Light)
 .XMMMMMMMMMMMMMMMMMMMMMMMMMMk   Terminal: tmux
  .XMMMMMMMMMMMMMMMMMMMMMMMMK.   CPU: Apple M3 Pro
    kMMMMMMMMMMMMMMMMMMMMMMd     GPU: Apple M3 Pro
     ;KMMMMMMMWXXWMMMMMMMk.      Memory: 3500MiB / 18432MiB
       .cooc,.    .,coo:.

What is your macOS version?

Version 14.4 (23E214)

I'll try to update. macOS14.4 seems notorious
https://news.ycombinator.com/item?id=39741115

I failed to reproduce this 14.4 and the example still worked as expected:
                    'c<EMAIL_ADDRESS>                 ,xNMM.          -------------------------------------
               .OMMMMo           OS: macOS 14.4 23E214 arm64
               OMMM0,            Host: Mac15,6
     .;loddo:' loolloddol;.      Kernel: 23.4.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Uptime: 3 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    Packages: 77 (brew)
 XMMMMMMMMMMMMMMMMMMMMMMMX.      Shell: zsh 5.9
;MMMMMMMMMMMMMMMMMMMMMMMM:       Resolution: 1800x1169
:MMMMMMMMMMMMMMMMMMMMMMMM:       DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.      WM: Quartz Compositor
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.    WM Theme: Blue (Light)
 .XMMMMMMMMMMMMMMMMMMMMMMMMMMk   Terminal: tmux
  .XMMMMMMMMMMMMMMMMMMMMMMMMK.   CPU: Apple M3 Pro
    kMMMMMMMMMMMMMMMMMMMMMMd     GPU: Apple M3 Pro
     ;KMMMMMMMWXXWMMMMMMMk.      Memory: 2875MiB / 18432MiB
       .cooc,.    .,coo:.

My guess is that there is a very slight difference between my MacBook M3 Pro and yours.

Ok, I figured it out. I had Stage Manager enabled. After I disabled it the app seems to work as expected. Now why does stage manager cause the issue 🤔

The problem is (*UserInterface).iconifyWindow(). There is a for loop in this function that checks if the window has been iconified with u.window.GetAttrib(glfw.Iconified). The issue happens when using MacOS's Stage Manager feature when the window is "minimized" it is still visible in the side panel so [window->ns.object isMiniaturized] in cocoa_window_darwin.m never returns true which means the for loop is never broken. Changing the line to [window->ns.object isMiniaturized] || ![window->ns.object isMainWindow]; fixes the issue. I'm not sure this is the intended behavior or not while using Stage Manager. Perhaps, instead the iconifyWindow function should be updated to ensure the app is placed in the app tray instead of stage manager?

This behavior is reproducible even in standard glfw 3.3:

package main

import (
	"fmt"
	"runtime"

	"github.com/go-gl/glfw/v3.3/glfw"
)

func init() {
	// This is needed to arrange that main() runs on main thread.
	// See documentation for functions that are only allowed to be called from the main thread.
	runtime.LockOSThread()
}

func main() {
	err := glfw.Init()
	if err != nil {
		panic(err)
	}
	defer glfw.Terminate()

	window, err := glfw.CreateWindow(640, 480, "Testing", nil, nil)
	if err != nil {
		panic(err)
	}

	window.MakeContextCurrent()
	var i = 0
	for !window.ShouldClose() {
		// delay the iconify process so the window can be fully loaded
		// if it isn't fully loaded then the Iconify function actually does
		// put the app in the tray.
		if i > 1000 {
			window.Iconify()
		}
		i++
		fmt.Println(i, window.GetAttrib(glfw.Iconified))
		// Do OpenGL stuff.
		window.SwapBuffers()
		glfw.PollEvents()
	}
}

Should we create a ticket in the GLFW project?

That's interesting. This seems a bug in GLFW. If this is a serious issue, I'm fine to fix this in our internal/glfw.

Should we create a ticket in the GLFW project?

Yes, if we can reproduce this without the Go binding.

I don't think this is a serious issue since it only happens with Stage Manager enabled, and minimizing the window in software. The yellow minimize button works as expected. If you wanted a simple temporary fix you could just limit the number of attempts the for loop does to check if it has been minimized

Sure. As this is not a serious issue, I'd like to hear what the GLFW people would say for this issue.


NuGet restore fails when encountering netcoreapp2.0 -> netstandard2.0 references

It appears that the NuGet restore task in VSTS uses some old version of NuGet that is unable to deal with netcoreapp2.0 projects that reference netstandard2.0 projects.
This is running on a custom agent with VS 2017 update 3 and .NET Core SDK 2.0.0.
Directly invoking nuget.exe restore with NuGet 4.3.0 instead of using the NuGet task works fine. I would expect the NuGet task to also work fine here.
Task log attached: 4_NuGet restore.txt

I am having the same issue. Using this workaround allowed to build on hosted agent

If you need a more recent version of NuGet you need to specify that in your definition. Due to a wide variety of compatibility issues in NuGet.exe we can't blindly update everyone to more recent versions

Thank you @chrisrpatterson, I just found a vsts task to update a nuget. Is there an option to always use the most recent one?

If you're using the NuGet Tool Installer task, you can use wildcards (e.g. 4.* or *) to always use the latest version available from https://dist.nuget.org. Note that things sometimes break or change between (even minor) versions, so this can introduce some instability to your build.

Thanks @alexmullans, 4.3.0 works for us now


Pull request template for ensuring consistent PR formatting

We need to add a Pull Request (PR) template to our repository to ensure that all contributors follow a consistent structure when submitting pull requests. This will help streamline the review process and ensure that all necessary information is included in each PR.
The template should include sections for describing changes, URL link to related issue, type of change, testing methods, and a checklist for the contributor(feel free to include any needed info)
Implementation details

Create a new file named PULL_REQUEST_TEMPLATE.md in the .github/ directory.
Add content to PULL_REQUEST_TEMPLATE.md

Content example
Description
Please include a summary of the changes and the related issue.
Related Issue
Please link to the issue that this PR addresses.
Resolves: #<issue_number>
Note: to mark a box, replace [ ] with [x].
Type of change

[ ] Bug fix (non-breaking change)
[ ] New feature (non-breaking change)
[ ] Breaking change
[ ] Documentation update

How Has This Been Tested?
Describe the tests that were run to verify the changes.
Checklist

[ ] I have performed a self-review of my code.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.

@TimOsahenru please can you assign this to me

A PR came in for this already @JohananOppongAmoateng - Sorry about that.
They were cleared to work on it from our Office Hours held in the discord.
I will mention to them that they should use the standard procedure of claiming a task before getting the work done.


Fixed minor misspelling (Swedish translation)

Fixed “packet” to “paket” - minor misspelling in Swedish translation

Thanks for your contribution to Homebrew!  You rock!


feat: upgrade angular version

Description
This PR is raised to update the version from Angular 9 to Angular 13

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[N/A] My change requires a change to the documentation.
[N/A] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[N/A] I have added tests to cover my changes.
[x] All new and existing tests passed.

Great job @mariuscernescu!


Split 3.1

Explanation: Arrays.swift.gyb contains a lot of tests for all array types in a single file. Which leads to CI timeouts.
Scope of Issue: Rearranging the code is necessary to achieve better parallelism and avoid timeouts.
Origination: The test suite has grown to the point where it started to timeout.
Risk: Minimal (has been done in master)
Reviewed By:
Testing: Tested in master CI bots
Directions for QA: N/A

Radar: rdar://problem/30495828

@swift-ci please smoke test


rated_by doesn't work for embedded rateables

class Foo
  include Mongoid::Document
  embeds_many :bars
end
class Bar
  include Mongoid::Document
  include Mongoid::Rateable
  embedded_in :foo
end
class User
  include Mongoid::Document
end

user = User.create
foo = Foo.create
bar = foo.bars.create
bar.rate(5, user)
Bar.rated_by(user).to_a

Mongoid::Errors::InvalidCollection: Access to the collection for Bar is not allowed since it is an embedded document, please access a collection from the root document.

Is there a solution for this or do I have to refactor?

BTW, this also doesn't work:
foo.bars.rated_by(user).to_a # returns []
but...
foo.bars.first.rated_by? user # returns true

I know that it doesn't work with embedded objects ( https://github.com/proton/mongoid_rateable/blob/master/TODO ).
I'll try to implement it on next week (I'm busy at this week).
Or you can implement it yourself.


refactor(network): move to converters-starknetapi Header & Signature to protobuf SignedBlockHeader

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1766  👈
#1765
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nagmo-starkware and the rest of your teammates on  Graphite


change basepath in bpmn-service

Describe the bug
change basePath in bpmn-service from '/workflow' to '/workflows'

@AnkurBansalSF


register

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/71256
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" f62f491b9cda449a6af12005c7c681829f6051ce
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/71257
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 1cff0f6f5319db4ee7ff870c9e09b71e61965180
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/71262
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 29655dc810c2299cacb7ebb8b98e0c08ed67830f
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/71262
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 2407fd9762371313151bae4211fcbacd4863c5bc
git push origin v0.1.0


Export ESM

getstream is currently exported as UMD only. ESM support has been around in NodeJS (and the browser) for some time and, I believe, since v12.20 it can be used without a flag. With NodeJS 16 being LTS at the time of this writing, I think it would be nice to provide an ESM export. The main advantage (for me, anyway) would be to use the same syntax when importing from a CDN and node_modules, rather than using a global variable.
Further reading:

https://medium.com/swlh/npm-new-package-json-exports-field-1a7d1f489ccf
https://blog.sindresorhus.com/get-ready-for-esm-aa53530b3f77
https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c

While I don't want to get too specific on my own code, I would like to provide an example where this would help developers. When using Vite's development server, I can't import getstream from without running into NodeJS-specific problems (this issue is possibly related). The same import works fine when Vite builds my code and optimizes it for the browser. Currently, my only workaround is to change the import from import stream from "getstream" to import<EMAIL_ADDRESS>However, I need to undo this change whenever I build, since I want to import the locally installed npm package of getstream. If you provided an (browser-optimized) ESM, I could simply put a condition on NODE_ENV in my config file (example below), not rewriting my import on every switch between development and build.
resolve: {
  alias: {
    "getstream": process.env.NODE_ENV ? "https://cdn.skypack.dev/getstream" : "getstream"
  }
}

I came here to say the same thing. Thanks for the workaround but any ETA on a fix?

Does anyone have a working Vue3 client example of this? I'm just bouncing between errors at the moment.

Hi! Any updates?

Can we give a test drive to<EMAIL_ADDRESS>? Thanks

Can we give a test drive to<EMAIL_ADDRESS>? Thanks

Thanks for the heads up. I'm currently on paternal leave and won't have a chance to touch company code before December :(


When I use vue/cli: 5.0.0-rc1 creating a project and using module Federation, there was a problem with hot update

Version
5.0.0-rc.1
Reproduction link
github.com
Environment info
System:
    OS: macOS 11.4
    CPU: (8) x64 Apple M1
  Binaries:
    Node: 14.16.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.11 - /usr/local/bin/npm
  Browsers:
    Chrome: 97.0.4692.71
    Edge: Not Found
    Firefox: Not Found
    Safari: 14.1.1
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.1.1
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  5.0.0-rc.1
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  5.0.0-rc.1
    @vue/cli-plugin-babel: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-eslint: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-router: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-typescript: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-vuex: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-service: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-shared-utils:  5.0.0-rc.1
    @vue/component-compiler-utils:  3.3.0
    @vue/eslint-config-typescript: ^9.1.0 => 9.1.0
    @vue/web-component-wrapper:  1.3.0
    eslint-plugin-vue: ^8.0.3 => 8.2.0
    typescript: ~4.1.5 => 4.1.6
    vue: ^2.6.14 => 2.6.14
    vue-class-component: ^7.2.3 => 7.2.6
    vue-eslint-parser:  8.0.1
    vue-hot-reload-api:  2.3.4
    vue-loader:  16.8.3 (15.9.8)
    vue-property-decorator: ^9.1.2 => 9.1.2
    vue-router: ^3.5.1 => 3.5.3
    vue-style-loader:  4.1.3
    vue-template-compiler: ^2.6.14 => 2.6.14
    vue-template-es2015-compiler:  1.9.1
    vuex: ^3.6.2 => 3.6.2
  npmGlobalPackages:
    @vue/cli: 5.0.0-rc.1

Steps to reproduce
When I modify the HTML content and save it, the console reports the following error.
remoteEntry.js:2779 Uncaught TypeError: Cannot set properties of undefined (setting './node_modules/cache-loader/dist/cjs.js?{"cacheDirectory":"node_modules/.cache/vue-loader","cacheIdentifier":"6abb76a0-vue-loader-template"}!./node_modules/@vue/cli-service/node_modules/@vue/vue-loader-v15/lib/loaders/templateLoader.js??vue-loader-options!./node_modules/cache-loader/dist/cjs.js??ruleSet[0].rules[0].use[0]!./node_modules/@vue/cli-service/node_modules/@vue/vue-loader-v15/lib/index.js??vue-loader-options!./src/App.vue?vue&type=template&id=7ba5bd90&')
    at webpackHotUpdatevue_demo_2 (remoteEntry.js:2779:39)
    at src_bootstrap_ts.9881d289310e02fc.hot-update.js:10:74

What is expected?
The browser changes when HTML content is modified and saved
What is actually happening?
When the HTML content is modified and saved, the browser does not change, and an error is reported on the console

Happens to me too, any update?

No.

I have this same issue. HMR doesn't work when using the module federation plugin. If I comment out the plugin in my vue.config.js file, then HMR works as expected.

it should be able to resolve your problem.
you can try it.
https://www.npmjs.com/package/@module-federation/fmr

I think this is happening because the remoteEntry.js file is auto-injected into the html page. I tried to use html-webpack-skip-assets-plugin to remove it, but it didn't work for some reason. The remoteEntry.js file still ends up in the index.html file.


Timecode not applying to folders in Image Save node

When using the [time(format_code)] token to try and make dated subfolders for generations, the folders instead take the name as the text typed in rather than turning into the appropriate date. This issue is not present on images, which have converted the timecode to the appropriate time of generation.

Right, that makes sense to have, so I went ahead and tossed that in here b023926f59d57b720f706974a710830958bf5226

Updated file comes back with this error, and the Image Save nodes now look like this and are inoperable.

No clue what that's about. I don't have that error. Did you update comfy? Looks like something weird. Why would my username and the repo commit be in a HTMl title? Lol

There is no HTML at all in my node class so maybe you downloaded it wrong?

Seems to be the case, I had originally downloaded the updated .py file by saving linked content. Cloning the repo again has fixed the issue.


Directed camera still follows on a different scene

While using directed camera, switching to another scene without activating it makes the camera follow to the coordinates on the new scene, but the streaming player is still on the active map and shows the wrong place.
This can be troublesome if I want to check something before moving the players there, since if I switch to Automatic before switching, I lose my previous camera position as well.
Maybe a toggle to pause the camera could be added to the Streaming Toolbar?
Otherwise make it so Directed camera doesn't follow the GM view when he is somewhere else?
EDIT: Sorry for the half-assed issue at first, submitted it incomplete by accident

I think the pause button might be a little difficult to manage, but I think your idea of not tracking when the GM is on a scene that's not active makes a lot of sense, I'll try to find a little time to implement this in the near future.

thank you so much for taking it into consideration!

This feature should be available in v0.3.0, please let me know if you encounter any issues.

Works fine! Thanks a lot!


package name cleanup

Desired Behavior
Rename java packages.
Benefits

And Avro namespaces

I just discussed with @neoword and @vinayakponangi and we decided to split the Avro namespace change into a new issue because it breaks compatibility.


ericklein/pm25 might contain a better network.begin()

Minor code optimizations in that branch. If those are stable, bring them back to AQ and RCO2.

pm25 code rolled into main()


#432 - External Redirect Asset Rendition Dispatcher

This adds a new ExternalRedirectAssetRenditionDispatcher that will 301/302 to a new URL location, which can be tokenized in a similar fashion as the other AssetRenditionDispatchers.
It's worth noting that it doesnt seem like Dynamic Media support asset files names with plus signs (+) in them.

When you reference 'smart crop' to you mean the Sensei-based feature (or however you want to refer to it)?

@bstopp yup - the smart crop is just the AEM Assets + Dynamic Media (S7) Smart Crop Image profile.

You cant create URL objects with spaces in them; I’m not sure if they have other corner cases wrt to escaping.


Update reserved-addrs.mdx

{
"id": "ra_2NTUzbDPGnHYVI8K3hYBaPfGia3",
"uri": "https://api.ngrok.com/reserved_addrs/ra_2NTUzbDPGnHYVI8K3hYBaPfGia3",
"created_at": "2023-03-24T19:59:24Z",
"description": "SSH for device #001",
"metadata": "{"proto": "ssh"}",
"addr": "1.tcp.ngrok.io:20000",
"region": "us",
"endpoint_configuration": {
"id": "ec_2NTVGguD2ttxSD5NMcng2lM4sIn",
"uri": "https://api.ngrok.com/endpoint_configurations/ec_2NTVGguD2ttxSD5NMcng2lM4sIn"
}
}

Thanks for the submission but it appears that this was done in error. If any information on this was from your account I would suggest removing deleting and re-creating to avoid security leaks.


Accessing MongoDB from pymongo client

From pymongo, I can access the mongodb setup by Meteor-up by doing
client = MongoClient('mongodb://<IP_ADDRESS>:3001/myAppName')
However, it gives me the error message:
pymongo.errors.ConnectionFailure: [Errno 111] Connection refused
I tried setting the bindip to <IP_ADDRESS> or commenting it out entirely but had no luck with it.
Do you have any idea?

Oh, I should've left out the port actually.
client = MongoClient('mongodb://<IP_ADDRESS>/myAppName')
Do you think such information might be useful in README? I can submit a PR.

You don't need to mention about pyMongo.
But, check whether we have some information about the mongodb setup.
If it's not, try to add about hosts and ports about it.
On Mon, Apr 6, 2015 at 10:38 AM Howon Song<EMAIL_ADDRESS>wrote:

Oh, I should've left out the port actually.
client = MongoClient('mongodb://<IP_ADDRESS>/myAppName')
Do you think such information might be useful in README? I can submit a PR.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/357#issuecomment-89920918.


H5 wont build in Jenkins with MSBUILD

When I used Bridge.net i remember that i installed Bridge.net extension (in Visual Studio Manage Extensions) and Jenkins (running as LOCAL SYSTEM) build Bridge.net without problem.
When I using H5, i installed the H5 compiler with the Visual Studio Developer Promt with:
dotnet tool update --global h5-compiler
It installs and compiles directly in Visual Studio in the Jenkins server.
When I now build the project in Jenkins it tells me that the H5 is not installed. I am trying to run dotnet tool update in jenkins as bat command but I get strange errors like:
In an uninitialized command prompt, please 'set VSCMD_DEBUG=[value]' and then re-run
is there anyone who has used H5 in jenkins?

I got it to work now. I added this bat script before MSBuild is running for the Jenkins project:
REM Install H5 compiler, reinstall it if it already exist.
pushd "%ProgramFiles%\Microsoft Visual Studio\2022\Community\Common7\Tools\"
call VsDevCmd.bat
dotnet tool update --global h5-compiler

Now it seems to reinstall H5 everytime jenkins is building the project, but it works for now and it compiles.
If anyone has a better solution, let me know :)

Hi @Riccsson , that's exactly how we use it as well. You'll need to install the tool before building. It's also possible to use it as a local tool on your project, so it's usually installed automatically on package restore, but the practical effect is the same - i.e. no time savings from doing either way.


Better test case for 15861 fix

Courtesy of @CyberShadow posted in https://github.com/D-Programming-Language/dmd/pull/5650

Auto-merge toggled on


Philo MSO

https://github.com/ytdl-org/youtube-dl/pull/17821
by @Aniruddh-J

@jlick @Aniruddh-J
I was asking if this worked because I don't have the account to test it and wanted to know that the patch still worked. Sorry for any confusion. I couldn't mention that I am looking to merge it into my fork because the youtube-dl maintainers strictly censor any mention of alternate forks

@jlick @Aniruddh-J
I was asking if this worked because I don't have the account to test it and wanted to know that the patch still worked. Sorry for any confusion. I couldn't mention that I am looking to merge it into my fork because the youtube-dl maintainers strictly censor any mention of alternate forks

No problem. :)

No problem. :)


Last.fm Group Sessions

Two options/modes:

(1) Start a new session and allow people to join it

(2) Follow/track another user

allow users to "catch up in a session" ("what was the last song you heard from this user?")

for "listening activity", use the UI to manually change the nowplaying status. Too heavy to use backend to sync up now playing status through that endpoint.

Concerns:

how to end sessions? If not ended, when do they expire?
"Last.fm with Friends is not responsible for group sessions left unattended and/or any scrobbles untruthfully attributed to any user in a session. By using this feature, you are allowing Last.fm with Friends to scrobble tracks on your behalf. In order to uphold the integrity of Last.fm scrobbles, sessions will expire automatically if the last played track time exceeds 20 minutes."
"This feature will NOT sync your "now playing" status on Last.fm itself, as this would be tricky to implement; however, it WILL make sure you end up with the same scrobbles as the user you are following, with the same timestamp too."

Some commits have been logged under #49 by mistake.


Enable customizing a client directly

Describe the feature
Given a Client, object, I want to be able to create a new client that is identical but with small changes, e.g. with an additional interceptor added
Use Case
I want to be able to create sub-clients for specific use cases.
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

A note for the community

Community Note

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

Closing, duplicate of https://github.com/awslabs/aws-sdk-rust/issues/634


IGNITE-21279: Sql. Partition pruning. Integrate static partition pruning into READ statements execution pipeline

Introduces PartitionPruner called by MappingService to update fragments to exclude unnecessary partitions.

PartitionPruner is called when a list of mapped fragment is build by MappingService. It traverses thatt list and updates fragments by updating ColocationGroups if partition pruning can be applied.  See PartitionPruner ::apply for algorithm 's description.

PartitionPruner uses PartitionPruningPredicate  to compute required partitions for a ColocationGroup.

ColocationGroup is modified to include remaining partitions after partition pruning is applied.

Fixes a bug in PartitionPruningExtractor related to column mapping.

Updates mapping tests to include partitions from colocation groups (so it becomes clear that partitions are removed).

Updates mapping tests to include sourceByExchangeid mapping (exchangeId -> node name list) because it is used by Inbox to send requests for data.

Benchmark results:

Benchmark                                           (clusterSize)  (fsync)  Mode  Cnt    Score    Error  Units
SqlPartitionPruningBenchmark.selectByKey                        3    false  avgt    5  124.886 ±  3.635  us/op
SqlPartitionPruningBenchmark.selectWithNoPrunining              3    false  avgt    5  716.286 ± 50.063  us/op
SqlPartitionPruningBenchmark.selectWithPruning                  3    false  avgt    5  294.329 ± 14.878  us/op

https://issues.apache.org/jira/browse/IGNITE-21279

Thank you for submitting the pull request.
To streamline the review process of the patch and ensure better code quality
we ask both an author and a reviewer to verify the following:
The Review Checklist

[ ] Formal criteria: TC status, codestyle, mandatory documentation. Also make sure to complete the following:
- There is a single JIRA ticket related to the pull request.
- The web-link to the pull request is attached to the JIRA ticket.
- The JIRA ticket has the Patch Available state.
- The description of the JIRA ticket explains WHAT was made, WHY and HOW.
- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] Design: new code conforms with the design principles of the components it is added to.
[ ] Patch quality: patch cannot be split into smaller pieces, its size must be reasonable.
[ ] Code quality: code is clean and readable, necessary developer documentation is added if needed.
[ ] Tests code quality: test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources.

Notes

Apache Ignite Coding Guidelines

Fixed benchmarks code.


Where can I find the settings on WoW 1.12.1?

I'm on WoW 1.12.1 and on the bottom left of the avatar pop-up window, there's a small circle which shows the following tooltip:

Frame position can be locked in settings

How or where can I find those settings?
:heart: Thanks!

type /vo or click the minimap icon.


What is Broadcaster ID?

There is no information about this on main page.
Also documentation has some pictures but no explanation.
What should be in this fields?

broadcaster_id 	< Your broadcaster id you can convert it here https://www.streamweasels.com/tools/convert-twitch-username-to-user-id/


base64 files

How to attach base64 files?

The MailService API allows you to attach files from disk locations.
If you need to attach a file that is already a base64 string, you will need to add a Mime\Part to the body of the email.
This is internally done by the mail service, so you can take a look at the code if you need to do it by yourself.

Finally I did it in this way:
foreach ($docAdj as $docName => $docBase64) {
                $outputPath = tempnam(realpath("tmp"), $docName . '.pdf');  //generate unique temp file name
                chmod($outputPath, 0766);
                $handle = fopen($outputPath, 'a');
                fwrite($handle, base64_decode($docBase64));
                $mailService->addAttachment($outputPath, $docName);
                fclose($handle);
 }

Good! Thanks for posting your approach.


chore(integratedservices): regenerated mock file, added ApplyDeploymentV3

Q
A

Bug fix?
no

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
-

License
Apache 2.0

What's in this PR?

Run make generate and committed the resulting diff.
Why?

While I was working on another issue, I had to regenerate some mock code and I noticed a totally unrelated generated change which is missing from the master branch.
Additional context

What is our stance on adding a CI/Action step which would check whether the code generation make directive on the current commit's code would result in a non-zero diff (and fail if it is a non-zero diff)?
Checklist

[X] Implementation tested (with at least ~one cloud provider~ tests were run locally)
[X] Code meets the Developer Guide

👍


Add example of C++ logging implementation

(Referenced in #2026)

I'm not sure if this should be a separate issue, but it is within the scope of this one.
Under Logging Usage for C++ at the Concept page (https://docs.ros.org/en/rolling/Concepts/About-Logging.html), there probably should be a C++ implementation demo similar to the Python's one. Probably something like:

https://github.com/ros2/demos/tree/master/logging_demo ?

Yeah just thought it'd be good to put a link for that there, in a similar fashion to the Python demo.

Having similar content present under different languages makes a lot of sense to me. However, the package you mentioned seems to serve a little bit different purpose and is not as intuitive as Python example. I have found similar implementation in C++ which implements the same example and could fit better.

We've significantly redone the logging documentation since this issue was opened, and I now think that http://docs.ros.org/en/rolling/Concepts/About-Logging.html does a much better job of explaining what is available.
Based on that, I'm going to close this out.  But feel free to reopen if you still think this is an issue.


How should I integrate in nuxt3

Please fill in at least the mandatory (*) questions below, or I will immediately close this issue without reading. Thanks
Environment *
node: v20.12.2
"nuxt": "^3.11.2",

Description *
Hope to have a basic case integrated in nuxt3

Does the current plugin support nuxt3

https://nuxt.com/modules/gtag
FYI

nuxt has already a module available as @ernestchu suggested


Allow to remove static formats from cache if they are no longer needed

Originally by arwagner on 2013-07-01
It would be nice to have an bib-un-reformat like option to remove unnecessary bibformats from the db cache.

The issue is addressed in Invenio v2.0 via inveniomanager.  For Invenio v1.x, let's use the dbexec example as a workaround.