Unexpected Unspent UTXO balance in the on-chain section

Background
Hi,
I am not 100% sure if this issue is LND specific but since I am observing it LND, I am going to open an issue here first.
I am at a loss here as I can't understand what happend to an on-chain balance of my node for a few days now.
It is currently shown as unconfirmed and I have no way of spending it.
The screenshot below was taken from Thunderhub shows three unspent UTXOs where the bottom two are spendable, i.e. I can send these balances but the top balance is not for some reason.

About a month ago, I moved 8million sats from my samourai wallet to LND on-chain wallet. Right after the transfer, I verified that the funds arrived to LND wallet. About a week or so ago, I connected to a new node and created a channel but it got stuck in pending state. After further investigation I realized that available balance (confirmed) is smaller than a new channel amount and probably caused the channel opening not being resolved.
So, as I was going through the history of chain transactions, I saw that the initial balance of 8 million that I received from my samourai wallet was being spent into another addresses through a number of transactions. Moreover, there were few received transaction that have no balance shown at all:

What next steps can I take to debug this issue further? Why is the balance stuck in unconfirmed state? How can I make it to be unstuck or at least, make it spendable?
Your environment

lnd version 0.11.1-beta commit=v0.11.1-beta

Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux

Bitcoin Core version v0.20.0

There have been some bugs within the wallet in previous versions that caused UTXOs to not be tracked properly. It'll be somewhat involved to identify the issue unless you have logs going back to the initial wallet deposit. You could also force a wallet rescan, which will make sure you're wallet is in sync with the chain.

There have been some bugs within the wallet in previous versions that caused UTXOs to not be tracked properly. It'll be somewhat involved to identify the issue unless you have logs going back to the initial wallet deposit. You could also force a wallet rescan, which will make sure your wallet is in sync with the chain.

Thank for the pointers!
Just wanted to clarify something. When you say I could force wallet rescan, what do you mean exactly?
When I run the flag , I get an error message saying: "unknown flag `reset-wallet-transactions'.
I searched in lnd --help  for this flag but there is no reference of it or how to use it.
Thanks

The flag was added only recently. Try upgrading to v0.12.1-beta, it should work there.

Awesome advice, thank you! I updated to v0.12.1-beta from the previous release and ended up having 0 sats in my lnd walletbance, after I did an lncli close with a delivery_addr, which was ignored (for a reason I still don't know). Instead, the sats were withdrawn to a new address of the lnd wallet. I was super confused, because in the transaction it showed a totally different delivery_addr than I submitted and the lnd walletbalance remained 0.
--reset-wallet-transactions really did the trick and I got my money back - all sats where shown as confirmed in my walletbalance. ;)
But: I then sent out a small test transaction, which worked fine, so afterwards I did an lncli sendcoins sweepall, which failed (utxos already spent).
I went through a --reset-wallet-transactions again, did another lncli sendcoins sweepall - which worked fine now.
I saved all .lnd data and set up a new wallet, idk, maybe something is still not 100% correct after the --reset-wallet-transactions process.
If you need my lnd data for analysis, pls let me know. :)

It sounds to me like your node somehow falls out of sync with bitcoind. Not sure how else the test transaction wouldn't be picked up by lnd. Or when you say "I sent out a small test transaction", you mean through lncli right? Or are you using the same seed in another wallet somehow?


Feature: Reconstruct our Buildroot image to follow Google Hardened Image

Is your feature request related to a problem? Please describe.
No
Describe the feature you are requesting, as well as the possible use case(s) for it.
We should save RAM only for execution (as it is limited). All other artifacts (Linux files, algrotihm, Agent and other binaries, downloaded Docker images, Pytorch libraries, etc...) should live on disk.
Google proposes following: https://cloud.google.com/docs/security/confidential-space

Root FS - probably ext4 - OS artifacts on the disk, including Agent. This one should be immutable (read-only) - no one should ever change Agent or OS files.
Mutable (read-write) disk partition, but this one then must be encrypted, as it will contain downloaded Docker images or algorithm binaries and potentially also datasets. Result can be written there.
tmpfs - this is the one in which execution must be done, so that we guarantee that it is in RAM.

An additional research needs to be done on this, but those changes make sense in order to better optimize RAM usage and protect Agent and other artifacts further (immutable partition), protect downloaded algo (when not put in RAM - foroptimization - Docker image needs to we written in encrypted mutable partition) and result, and ensure execution in tmpfs without swap.
Indicate the importance of this feature to you.
Must-have
Anything else?
No response

@danko-miladinovic @SammyOina @rodneyosodo can you please verify this:

If this is true, and it is like this for Intel TDX also, then we do not have to disable swap. Moreover - we should enable swap and use it, in order to preserve RAM.

Yes, based on the paper SEV-SNP formal security analysis the pages are encrypted when they are swapped to disk.

@drasko What are the benefits of this approach? We need to put most of it into RAM to make it run anyway, and adding disk support is quite a significant change that requires disk encryption. @danko-miladinovic I don't think we are talking about process pages, but everything else that is not part of the process, but the system.

There are many benefits. For example swap. Then - Linux system can be on RO unencrypted (no jeed to put everything in RAM). And so on. Also big data files that can be treated one by one.


Time-out issues with DataUpdateCoordinator

[x] I have read the Readme, including the Advanced section regarding debugging.

Describe the bug
it's random, sometimes daily, sometimes 3 times a week ... the controls for my shutters for my tahoma do not work.
In the log I have the message: Timeout fetching TaHoma Event Fetcher data.
After restarting the server, everything works again.
I am using HA on container / Qnap.
To Reproduce
Steps to reproduce the behavior:
Just wait several minutes or hours...and in my log I have:
Timeout fetching TaHoma Event Fetcher data
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

ha-tahoma version: lastest
Home Assistant version: Home Assistant 2020.12.1
Platform: [e.g. cover, sensor, binary_sensor]
roller
Device: (if your problem is related to a specific device)
Tahoma
Model: [e.g. PositionableScreen, can be gathered from device list in HA]
Type: [e.g. io:DimmableLightIOComponent, can be gathered from device page in HA looking at Firmware] /config/devices/dashboard]

Additional context
Add any other context about the problem here.

Thanks for reporting @Tonylolo. I haven't seen these issues yet. What is your update interval? (Settings -> Integrations).
Do you have debug mode enabled and could you share more parts of your log? I would like to understand more about this behaviour. Normally, controlling your covers is not related to the event fetcher. The event fetcher is able to recover from any timeouts, thus that should not be a big issue.

Thanks for reporting @Tonylolo. I haven't seen these issues yet. What is your update interval? (Settings -> Integrations).
Do you have debug mode enabled and could you share more parts of your log? I would like to understand more about this behaviour. Normally, controlling your covers is not related to the event fetcher. The event fetcher is able to recover from any timeouts, thus that should not be a big issue.

My update interval : 30s, I test with 3200 same things.
I don't know how enable debug mode ?

My update interval : 30s, I test with 3200 same things.
I don't know how enable debug mode ?

In our readme, we documented how to enable debug logging: https://github.com/iMicknl/ha-tahoma#enable-debug-logging
Could you clarify what the issue is. Is it just the message in the log, or does it also happen when you try to execute a command? (via automations?)

In our readme, we documented how to enable debug logging: https://github.com/iMicknl/ha-tahoma#enable-debug-logging
Could you clarify what the issue is. Is it just the message in the log, or does it also happen when you try to execute a command? (via automations?)

my log has been cleaned, so as soon as the message, I copy here.
It's just a message in the log, when a command doesn't work I go see. in log and I find the message :...fetcher....

my log has been cleaned, so as soon as the message, I copy here.
It's just a message in the log, when a command doesn't work I go see. in log and I find the message :...fetcher....

 I am a bit clue less why you receive so many Not authenticated exceptions in combination with very high response times.

Could you update to the latest available version of this integration (via HACS / GitHub)
What is your current update interval? (the one you shared the log from)
Could it be that you have network issues?

2021-01-15 09:38:09 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 320.920 seconds
2021-01-15 09:39:19 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 40.897 seconds
2021-01-15 09:40:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 41.022 seconds

This is very very slow compared to my installation. The events should be fetched in less than a second normally...
2021-01-15 16:20:12 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.132 seconds
2021-01-15 16:21:12 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.122 seconds
2021-01-15 16:22:12 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.122 seconds

Thanks for sharing your log. I am a bit clue less why you receive so many Not authenticated exceptions in combination with very high response times.

Could you update to the latest available version of this integration (via HACS / GitHub)
What is your current update interval? (the one you shared the log from)
Could it be that you have network issues?

2021-01-15 09:38:09 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 320.920 seconds
2021-01-15 09:39:19 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 40.897 seconds
2021-01-15 09:40:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 41.022 seconds

This is very very slow compared to my installation. The events should be fetched in less than a second normally...
2021-01-15 16:20:12 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.132 seconds
2021-01-15 16:21:12 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.122 seconds
2021-01-15 16:22:12 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.122 seconds

I have alreadu update hacs integration
Interval update: 30s
HA is installing on Qnap, via container, on network via ethernet cable, none wireless between qnap and tahoma. Only a tplink router and box.
Time between action on button(ios app of HA) and moving of roller is randomary; fast and some times several seconds...

I have alreadu update hacs integration
Interval update: 30s
HA is installing on Qnap, via container, on network via ethernet cable, none wireless between qnap and tahoma. Only a tplink router and box.
Time between action on button(ios app of HA) and moving of roller is randomary; fast and some times several seconds...

I don't think we can offer a solution for this issue... We haven't had any user with those issues yet and I don't believe this is part of this integration. The event fetcher is a really simple API endpoint. It should not happen that a request takes 40 seconds, instead of 0.1 second.
Are you able to ping tahomalink.com from your QNAP? I wonder what kind of latency you have.

I don't think we can offer a solution for this issue... We haven't had any user with those issues yet and I don't believe this is part of this integration. The event fetcher is a really simple API endpoint. It should not happen that a request takes 40 seconds, instead of 0.1 second.
Are you able to ping tahomalink.com from your QNAP? I wonder what kind of latency you have.

Yes i test the ping: 21ms from nas to tahomalink.com

Yes i test the ping: 21ms from nas to tahomalink.com

So about this issue i ll continue to search...
Another issue if you cn jelp me, when i use stop command on a roller with ha, roller doesn't take myposition , there is nothing. But if the rolling moves it's ok it stops.
Thk

So about this issue i ll continue to search...
Another issue if you cn jelp me, when i use stop command on a roller with ha, roller doesn't take myposition , there is nothing. But if the rolling moves it's ok it stops.
Thk

Another issue if you cn jelp me, when i use stop command on a roller with ha, roller doesn't take myposition , there is nothing. But if the rolling moves it's ok it stops.

This is currently not mapped to the stop service in Home Assistant. If you would like to utilize my position, you can the following service call. tahoma.set_cover_my_position

Another issue if you cn jelp me, when i use stop command on a roller with ha, roller doesn't take myposition , there is nothing. But if the rolling moves it's ok it stops.

This is currently not mapped to the stop service in Home Assistant. If you would like to utilize my position, you can the following service call. tahoma.set_cover_my_position

Great !

Great !

Hi,
In order to validate if it is my installation or the integration; I installed the official SOMFY integration (which works on shutters).
As usual, 2-3 days without any problem and then one morning no shutter responds or so under several tens of seconds and I even have an error:
Failed to call the cover / open_cover service. 500 Server error: Internal Server Error for url:
https://api.somfy.com/api/v1/device/9894282d-b0f29..../exec
I use this time to compare the official and it works perfectly! so the error is on your integration.
I will try with nodered for another comparison.
Do you have more idea?
Thank you

@Tonylolo the error you quoted come from the official api integration not from this one.
The official api is known to be flaky as the Somfy server returns often errors like yours. The only thing you can do is to contact their support. Like I already did several times. Sadly they don't give resources to this api.

Hi
Are you sure because it's appears when i use an entity cover make with tahoma custom integration.
And i always have issue after 1-2days with this integration. Since somfy official is ok...
Sadly i would like use custom that is very good in term of functions!

hi,
i complete following to issue this night:
2021-03-01 19:06:25 INFO (MainThread) [backoff] Backing off execute_commands(...) for 0.9s (pyhoma.exceptions.NotAuthenticatedException: Not authenticated)
2021-03-01 19:06:26 INFO (MainThread) [backoff] Backing off execute_command(...) for 0.5s (pyhoma.exceptions.TooManyExecutionsException: Server busy, please try again later. (Too many executions))
2021-03-01 19:06:27 INFO (MainThread) [backoff] Backing off execute_command(...) for 0.2s (pyhoma.exceptions.TooManyExecutionsException: Server busy, please try again later. (Too many executions))
2021-03-01 19:06:27 INFO (MainThread) [backoff] Backing off execute_command(...) for 3.1s (pyhoma.exceptions.TooManyExecutionsException: Server busy, please try again later. (Too many executions))
2021-03-01 19:06:30 INFO (MainThread) [backoff] Backing off execute_command(...) for 0.4s (pyhoma.exceptions.TooManyExecutionsException: Server busy, please try again later. (Too many executions))
2021-03-01 19:06:31 INFO (MainThread) [backoff] Backing off execute_command(...) for 2.1s (pyhoma.exceptions.TooManyExecutionsException: Server busy, please try again later. (Too many executions))
2021-03-01 19:06:33 INFO (MainThread) [backoff] Backing off execute_command(...) for 29.0s (pyhoma.exceptions.TooManyExecutionsException: Server busy, please try again later. (Too many executions
After that I test with "official SOMFY" integration and all is ok.


How to run via npx

I guess npx is for most scenario, but I can't find the support of it.

it is unnecessary. just run with node https://github.com/swc-project/swc-node?tab=readme-ov-file#usage


BinaryField doesn't show up in populate

I think maybe columns that do not show up in the Admin page does not show up the in populate page?
We're trying to save gv.dump() to a binary type.

Hey, thanks for pointing this out.
This might be related to #60. Is it the string of instances which does not show the field. If so, this might be fixed soon.
If this is not what you are asking:  get_open_fields decides which columns are detectable. E.g., if it is not id, user, not editable or  a pointer field, it should be present.
If that's the case, can you point me to your implementation or provide a minimal example?


WIP: Upgrade and adapt new WorkerPoolHash function in Gardener v1.98

How to categorize this PR?

/area dev-productivity
/kind enhancement
/platform equinix-metal
What this PR does / why we need it:
This Pull Requests upgrades the Gardener dependency v1.95 -> v1.98.
This includes also the new WorkerPoolHash function, which now needs an additional variable to be passed.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/2590 in Gardener/Gardener.
Special notes for your reviewer:
Release note:

Upgrade and adapt new `WorkerPoolHash` function in Gardener `v1.98`.

/hold we need more context for adapting the new Workerpoolhash function (see TODO)


Loosen dependency requirements

Currently we seem to be requiring exact versions of dill and ndcctools in the *-env.yml files. Is there some reason for this? If not, we should remove those requirements.
Also, gfortran should not be necessary for build-env.yml

I remember those versions of dill and ndcctools are needed by a specific version of work_queue? @tjstruck
I can't remember why I added gfortran into the environment.

Well we should test with the updated versions of dill and ndcctools (especially since ndcctools provides work_queue). There's no need to pin ourselves to outdated versions.

The cloud computers installing dadi-cli from the cloud-env.yml (no version requirement on ndcctools or dill) work fine, so the version requirement can probably be removed.


question: v0.8.0 vs v0.8.1

Hey @erusev and @aidantwoods
Why do the 0.8.0 and 0.8.1 versions look so different (from the packagist point of view)?

0.8.0 was meant to resolve some issues with PHP 7.4 comparability, but was released from a version of the codebase which was designed for the Parsedown 1.8.0-beta series. This means that using 0.8.0 would require using a beta version of the Parsedown core class which would cause installation issues where minimum stability is enforced.
After gearing up for 1.8 it became evident that the way in which extensions utilise Parsedown lacks a clear interface definition, meaning it is unclear which internal behaviours can be changed without causing breakage. Hence Parsedown 1.8 hasn't been released and Parsedown-Extra 0.8.0, which was meant to be a bug fix release, shouldn't be depending on this version.
0.8.1 branches only slightly upstream from the previous 0.7.1 release, and brings the fixes from 0.8.0 without the potential breakage (hence looks a bit different because it doesn't include a lot of mistakenly included new code).

@aidantwoods cool, then I'll use the 0.8.1 waiting for the 1.8 to be finalize. Thanks for all the work.


3.3.4 replication error "replication dump - unable to find context (it could be expired)"

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[ ] 3.1
[ ] 3.2
[v ] 3.3
[ ] self-compiled devel branch

Mode:

[ ] Cluster
[ v] Single-Server

Storage-Engine:

[ ] mmfiles
[v ] rocksdb

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[ ] Ubuntu .deb
[ ] SUSE   .rpm
[ v] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[ ] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

this is an AQL-related issue:
[ ] I'm using graph features
I'm issuing AQL via:

[ ] web interface with this browser:     running on this OS:
[ ] arangosh
[ ] this Driver:

I've run db._explain("<my aql query>") and it didn't shed more light on this.
The AQL query in question is:
The issue can be reproduced using this dataset:
Please provide a way to create the dataset to run the above query on; either by a gist with an arangodump, or `db.collection.save({my: "values"}) statements. If it can be reproduced with one of the ArangoDB example datasets, it's a plus.
Foxx
this is a web interface-related issue:
I'm using the web interface with this browser:     running on this OS:

[ ] authentication is enabled?
[ ] using the cluster?
[ ] _system database?

These are the steps to reproduce:

open the browser on http://<IP_ADDRESS>:8529
log in as ...
use database [ ] _system [ ] other:
click to ...
...

The following problem occurs: [Screenshot?]
Instead I would be expecting:
this is an installation-related issue:
Describe which steps you carried out, what you expected to happen and what actually happened.
Greetings,
I've tried to build All-in-one Asynchronous Replication setup between two single hosts, both 3.3.4 version.
The total size of all the  DBs at Master is about 50GB.
On the Slave host i've ran the following commands on 2018-03-15T14:33:15 :
db._useDatabase("_system");
require("@arangodb/replication").setupReplicationGlobal({
endpoint: "tcp://vm-tskdbn1:8529",
username: "root",
password: "mypass",
autoStart: true
});
That setup ran about 36 hours, most of the 50GB was copied from the Master to the Slave, but then the replication failed. The following messages appeared in the slave's arangod.log file :
2018-03-15T14:33:15 [25118] INFO {replication} connected to master at tcp://vm-tskdbn1:8529, id<PHONE_NUMBER>93947, version 3.3, last log tick 623793780
2018-03-17T02:06:07 [25118] ERROR {replication} error while running applier thread for global database: got invalid response from master at tcp://vm-tskdbn1:8529 for URL /_api/replication/dump?collection=_appbundles&batchId=286819227&flush=true&flushWait=15&from=0&to=623793781&serverId=159757613179818&chunkSize=2097152&includeSystem=true: HTTP 404: Not Found - {"error":true,"errorMessage":"replication dump - unable to find context (it could be expired)","code":404,"errorNum":400}
2018-03-17T02:06:07 [25118] INFO {replication} stopped replication applier for global database
Few questions on that issue :
Q1. What's the reason of that replication failure ?
Q2. May it be that some replication-critical information became obsolete (deleted ?) on the Master - during those 36 hours setup ran ? May be i shall set some (which ?) parameters to allow Arango to keep some (which ?) information at the Master for more than 36 hours ?
Q3. Is it possible to resume the replication from that point ?
Please , see also my previous cases on the replication-related subjects (<3.3.4v) :
https://github.com/arangodb/arangodb/issues/4305
https://github.com/arangodb/arangodb/issues/4585
https://github.com/arangodb/arangodb/issues/4654
Best regards and looking forward your assistance,
Avi Vainshtein

Q4. and also - the most important question: how/is it possible to fasten the initial replication ? The initial replica of 50GB took almost 36 hours. If i just copy 50GB of data (like scp/ftp) between those two hosts - it will take less than 2 hours...

Hi @avive99,
in order to fasten the initial replication the slave can be initialized using a backup of the master. A cookbook, that describes this procedure, is available in the documentation.

Hey @maxkernbach ,
Thanks for your remarks.
As per your mentioned cookbook - the suggested type of master backup is arangodump.
I've tried already to dump that given 50gb database with arangodump - it took about 16 hours.
(you can see the details in my other issue "https://github.com/arangodb/arangodb/issues/4654" )
I don't know how much time it will take to run the arangorestore from that dump at the slave - but could it be it will take no less that another 16 hours ?
Even in a very optimistic scenario that the arangorestore of 50gb db will take one hour - the total time will be more than 17 hours, and that isn't too fast, isn't it ? Any way, that's no so realistic, especially taking into account that our main database (production host) is about 300gb size, so only the arangodump will run a few days...
Let's say that i find another way to copy the whole contents of the master database directory contents to the slave host - by advanced storage techniques (snap, clone, etc.). Is there any supported way to start replication slave and start replication in such a case ? And mean the all-on-one replication (i.e. all the master databases to be replicated)...
Many thanks and best regards,
Avi

We have added multithreadding to arangodump in devel in the last weeks; you may want to try the nightly client package whether it improves your situation and performance.
You can't compare the netto bandwith you can achieve with a raw file transfer with what the database has to do. You expect from it to be persistent at document level, durable etc. So behind the curtains it has to do much more than a simple scp would have to do.

Hey @dothebart and @vinaypyati ,
Many thanks for your comments.
I understand that 3.3.8 version is available now.
So in the next few days i'll upgrade the arango from 3.3.4 to 3.3.8, and test again both replication setup and arangodump facilities. I'll update that case with new experience.

Hi @avive99
For your information, we have released version 3.3.9
Bes

Hi @avive99
Just sending a quick followup - How do the tests with replication and arangodump are going?
Could you please send us a quick update on this ticket?
FYI version 3.3.10 is available
Best,

Hi @avive99,
did you have a chance to try the nightly build, which includes multithreading for arangodump?
Also, how are things going with the latest version 3.3.13?

Closing this issue for now since we have not heard back from you recently.
Please feel free to send us some feedback and reopen this issue.


Add documentation of header and footer for AutoComplete component

Closes #2522
Description
Add header and footer prop descriptions to AutoComplete component documentation.
Current behavior (updates)

New behavior
https://github.com/user-attachments/assets/b0af9dc8-ee55-4ff0-8200-8270894e194c
Is this a breaking change (Yes/No):

Additional Information

Thanks!


Update react-sortable-hoc

We'll need to update react-sortable-hoc to the lates version.
There is a collapse issue with SidebarCollapsibleCard though. The card doesn't collapse during the sort phase. It looks like the library changed it's rendering methods to clone the DOM node during sorting. It doesn't look like we can get React to re-render things when sorting happens.
Hopefully we can tap into the new updateBeforeSortStart callback to resolve this.

Bump, for @plbabin


feat: implement 0x51 - MLOAD Opcode

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] 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?

Resolves: #242
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

Awaiting resolution of #283

Hey @khaeljy #283 have been resolved and merged, could you resolve conflicts and check again? :)

Hey @khaeljy #283 have been resolved and merged, could you resolve conflicts and check again? :)

Done!


[Fix] Fixed duplicated choice view

This fixes duplicated choice view when using SettingPicker.
Related to https://github.com/aheze/Setting/issues/34

@aheze


modal display shrinked in ios with react-native-webview

Using react-native-webview library I am encountering different behaviour on android and ios in regards to how a modal that contains input field that opened will be displayed.
The issue occurs when focusing on input field, as expected the keyboard opens but on ios the modal get squashed whereas on android the content is displaying fine.
See screenshot below:
[android ios]

I wonder if there is a particular trick to adjust ios behaviour in this case?
We have such requirement to display some pages written in React.js (that we control) in the app via web-view and  so I have access to source code for this modal on the web which looks something like:
.modal {   border-radius: 8px;   left: 50%;   max-height: 100%;   position: fixed;   top: 50%;   transform: translate(-50%,-50%);   width: calc(100% - 40px);   z-index: 995; }
Environment:
OS: ios, any version
"react-native-webview": "13.2.2",
"react-native": "0.72.6",
I am a bit clueless where to look honestly. Looked up similar issues on stackoverflow and the library github repo but no luck.
I could inspect the same page on ios simulator on safari web inspector and play with properties but issue is not present

Do you know how to resolve this issue yet?

Do you know how to resolve this issue yet?

Nope 😞


[irods/irods_6465] add INST_NAME for py_remote microservice (4-2-stable)

squashed, not #-d

formatting looks good, please squash to one again

Done

remove the discovered issue paragraph in commit comment.

Same comments here as in #128.

done


Tado Device Tracker async errors

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (0.37.1):
Python release (python3 --not sure - whatever version docker uses):
Component/platform:
Tado Device Tracker (introduced in release: 0.37)
Description of problem:
Does not seem to work - no devices tracked, and fills log with errors...
17-01-31 07:59:31 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "uvloop/future.pyx", line 372, in uvloop.loop.BaseTask._fast_step (uvloop/loop.c:112669)
File "/usr/src/app/homeassistant/components/device_tracker/__init__.py", line 649, in async_device_tracker_scan
found_devices = yield from scanner.async_scan_devices()
File "/usr/src/app/homeassistant/components/device_tracker/tado.py", line 65, in async_scan_devices
yield from self._update_info()
TypeError: 'NoneType' object is not iterable
17-01-31 07:59:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved....

Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:

device_tracker:
  - platfom: tado
    username: XXXXX
    password: XXXXX

Traceback (if applicable):

Additional info:

these issues are still present in 0.38 & 0.38.1
Also no new devices show up in known_devices.yaml
Has anyone else tried? 🤔

Have been looking into this to try to find out why it doesn't work for me, and I have actually discovered that it was my tado password that contained a hash (#) symbol that was causing this issue. My new password only contains letters & numbers now and ta-da! (ta-do!) I now have new devices showing in known_devices
The errors in the log still show every 30 seconds but I think there has been a pr in dev to fix this
TL:DR don't have symbols in tado passwords!

This happens to me to and I have no symbols in my password. No new users are added and the log is full of errors. Very frustrating!


Upgrade DirectML version to 1.6.0

I tried to upgrade to 1.8.0 or 1.7.0, but encounter some issues: some Conv2d end2end case will get wrong result value.
[  FAILED  ] Conv2dTests.FusedDepthwiseConv2dDefault
[  FAILED  ] Conv2dTests.FusedDepthwiseConv2dNchwOhwi
[  FAILED  ] Conv2dTests.DepthwiseConv2dWithNchwOihw

So I can only upgrade to 1.6.0 (DML_FEATURE_LEVEL_4_0). I will also raise an issue to DirectML repo. @fujunwei @BruceDai

Is the failure of "check memory leak for DirectML backend (windows)" bot a known issue? @BruceDai @fujunwei

@mingmingtasd

I will also raise an issue to DirectML repo

What's the issue? Are they issues of DirectML or WebNN-native implementation? Do you have any investigations on the root cause?
I am fine to upgrade to a version with no issues, but we eventually need to support the latest DirectML release.

@mingmingtasd

I will also raise an issue to DirectML repo

What's the issue? Are they issues of DirectML or WebNN-native implementation? Do you have any investigations on the root cause?
I am fine to upgrade to a version with no issues, but we eventually need to support the latest DirectML release.

I am doing investigations now, will try to re-produce with the DirectML samples. I think it looks like a DirectML issue. @huningxin

Is the failure of "check memory leak for DirectML backend (windows)" bot a known issue? @BruceDai @fujunwei

Should we revert the CI with https://github.com/webmachinelearning/webnn-native/pull/236?

I have confiremd that the conv2d issue on DirectML 1.7.0/1.80 should be their own issue. I have provided a case using their python sample to reproduce the issue and raise issue #234 to them. @fujunwei @huningxin

Merge it.


Bug: App does not start if docker daemon is not running

If docker is not running and try do start dockyard then app does not start. It is observed on Macos but may not be specific to it.

Expected Behavior
App should start and show the message that it is not able to connect to docker
Current Behavior
App does not start
Possible Solution
May be it has do something with initializing docker connection start the start
Steps to Reproduce

Stop docker daemon
Try to open Dockyard app

Context (Environment)
Detailed Description
If docker is not running and try do start dockyard then app does not start. It is observed on Macos.
Possible Implementation

I think this is because of the panic! in state.rs while trying to set up docker. I'm just guessing, but AppState might want to find a way to still create a Docker struct. Not sure. I did try manipulating AppState to use an Optional or Result<Docker, E>, but I think this would only work if the commands try to update the AppState's docker each time it encounters a None/Error from the Optional/Result.
Clearly without any changes dockyard works fine when docker stops once dockyard is running -- I tested this by running colima stop after dockyard had started up. The ping interval could be a bit tighter, the UI has issues when navigating/using actions before the 30s ping kicks in to force the error page, but that's a separate thing. But this seems to mean if the docker struct is correct, it doesn't actually need docker to be up. Unfortunately, the methods in bollard return an error if docker.sock isn't there, rather than just returning the (possibly?) viable struct that could later be used if/when the docker.sock is there.


Regeneration of YOLOX model with quantize INT8

Hi,
I'm trying to regeneration of YOLOX nano model with quantize INT8 using your onnx and openvino files(get from PINTO_model_zoo). I also use your docker image and convert_script.
I can run using your quantize int8 tflite file but, can not run my quantized model using your onnx or openvino files.
I got error message "node XXX(tflite nnapi delegate) failed to invoke". but, I can run quantize model only cpu or no quantize(FP32) model. Really confused this situation can you help solve this problem?

It's probably a problem with NNAPI.

Thanks for reply.
I wonder why your quantize model(get from PINTO_model_zoo) running on my chip.
So, can you tell me version of ONNX, Openvino, openvino2tensorflow, tensorflow when you convert YOLOX?
I will try to make same environment and convert.

I am only using the Docker containers listed in the README.


(Feature) Add Ethereum support to GoodDollar Wallet

Description

added option to switch Goerli & Mainnet (PROD only)
TBA

About #3927
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request (for frontend tasks)
[ ] I have pasted a gif showing the feature.
[x] @mentions of the person or team responsible for reviewing proposed changes

all changes requested had been done @sirpy

@johnsmith-gooddollar please resolve conflicts.
specifically take care of the goodwalletclass changes  of handling txs, new contracts etc...

@johnsmith-gooddollar please resolve conflicts.
specifically take care of the goodwalletclass changes of handling txs, new contracts etc...

So just resolve conflicts and I could merge ?

How about the package ? When you release non-alpha contracts having goerli network and when you will add  networkId field there (so I could avoid using patch)?

i will go over the code again and update the goerli contracts

@sirpy done

@sirpy done, see comments in resolved. the request about titles moved to the separate issue #4083 as a) it looks like enhancement b) it's more complex rather than simple change/fix c) eToro are asking to merge this and test ASAP

@johnsmith-gooddollar

i've pushed some fixes/updates please review
regarding nativetxs there is an edge case. if a single transaction does both native transfer and token transfer then they will override each other. open a new issue to handle that.
open an issue to find solution for unsafe wallet passing to threaddb

@sirpy

I've optimized code a bit, please look
when You could update contracts package ?

@johnsmith-gooddollar you should be able to upgrade the contracts package. there's a development-goerli entry in the contracts now


⚠ Bofrost.at has degraded performance

In 272182b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1110 ms

Resolved: Bofrost.at performance has improved in 9bc8e73 after 9 minutes.


Update install-kubeadm.md

Added PPC repo for k8s packages

/check-cla

@Alok0587 👋 Please sign the contributor agreement in order to continue.
/close


fix relative path problem

I want to configure the base property to './', but I found that using this plugin will cause cesium loading errors in development mode; after packaging, the links in the index.html file also have problems.

after build

So I added some code to fix this.

sorry @lovefengruoqing , I haven't check your PR yet, because I was busy with something else, and  I didn't understand what is the base usage in vite.
is this https://github.com/nshen/vite-plugin-cesium/pull/24 new PR meets your needs?


is CASE WHEN supported?

[Err] 1064 - SQL parse error: Expected ",", ";", "FROM", "GROUP", "HAVING", "LIMIT", "ORDER", "WHERE", or end of input but "f" found. on 'select f_corp_id,f_user_id,f_in_out_type,
case when f_status = 0 && f_Calltime>0 then 1 else 0 end as connect,
case when f_crm_id < 80000000 then 0 else 1 end as custome,
sum(f_Calltime),count(1)
from tel_record2
where f_Endtime between '2017-05-15 00:00:00' and '2017-05-15 23:59:59'
group by f_corp_id,f_user_id,f_in_out_type,connect,custome;'

or like: if(exp,v1,v2) as c_name


Store command

Easily locate the raw text file for editing and potentially syncing the file to a cloud storage service

merging soon


Consistency between process nodes

I am slightly suprised that sky130 and gf180mcu are diverging far more than I expected, e.g. one of them seems to be still(?) using the config.tcl and the other already(?) config.json .  Or the missing verification in #233 . I am trying to maintain my StdCellLib flow in a way that it supports all processes, so more coherency between the processes would be very helpful.

@mkkassem


lint fixes

ran lint and it fixed a bunch of trivial format issues

tests fail that seem to have nothing to do with lint format changes.


Can't resize bottom panel

Description
Since the most recent release on Fairground I can't resize the panel with orders, positions, etc. vertically on Firefox, Mac.
Steps to Reproduce

Open Console https://console.fairground.wtf
go to a market view
Try to resize the bottom panel to make it taller or shorter

Expected behavior
Panel should be resizable.
Device details

OS: macOS
Browser: Firefox
Version: 113.0.1 (64bit)

Looks like this bug maybe only occurs when no wallet is connected.

Seems to have gone after some refresh, closing.


Move location of accessibility-alt-text-bot.yml

What
Change file location .github/workflows as noted on https://github.com/github/markdownlint-github/pull/43#issuecomment-1554851376.

#68


Secret Santa [Template Submission]

#twiliohackathon
What's the use case for the template?
You and your friends want to do the secret santa this christmas and you need a way to randomly pick secret santas for each in the group.
What's the programming language?

Backend: Nodejs + Firebase
Frontend: React

Template GitHub URL:
https://github.com/jakate/secret-santa
Author Information (please fill out):

Author name: Jaakko Tepponen
Author GitHub organization/user: https://github.com/jakate/
GitHub username you used to sign jakate

Additional dependencies:

Firebase
Twilio

Checklist:

Please check every part of this checklist for us to process your request. You can do this by marking them with [x] instead of [ ].

[x] I've filled out the form at ahoy.twilio.com/code-exchange-community
[x] My sample application is open source and has a permissive license such as MIT or Apache-2
[x] There are no known security vulnerabilities and I'm following security best practices
[x] I've read Twilio's best practices coding guidelines for my project
[x] I agree and adhere to the Code of Conduct
[x] The template has been authored by me / or my organization and will be kept up-to-date. If the template will not longer be maintained, I'll notify this project.

This submission is not a hackathon submission
Thank you for your submission! Just a reminder that if you are intending to submit to the hackathon, you have to do this separately to this submission by creating a post on dev.to/new/twiliohackathon

Thanks! Done that :)


[Spanish] localize 'Multitenancy'

Localize the content/en/multitenancy.md document to Spanish

Hey @electrocucaracha, Can you please assign me this issue?

@tinniaru3005 did you still working on this? Can I reassign this one?

No I don't. I got busy with my preparations for my Masters entrance exam and completely for got about the issues. So sorry for the delay.

I can help here


Fix references to o.j.nullness -> o.j.annotations

I believe this gets them all, from this tree.

The diff shows changes from your previous PR, but I'm optimistic that merging is going to Just Work.


Failure to run tests on 1.9.0 (beta) and nightly

Most likely linked to this:
https://github.com/JuliaLang/julia/pull/45540
Try to add DelimitedFiles to compat section of Project.toml, but didn't solve the problem. 508db61

Removing the Manifest.toml file solved the problem.  0c26583
Many other packages don't have the Manifest file in the repo so that should be OK.


support weapons during kicks always target legs as well

v5.6.1 while kicking support weapons also fire so target the legs.
Knees.zip
video of it as well from user https://discordapp.com/channels/587764595888881670/587765800052457474/731033046450700328

Should be fixed in 0.5.13


Try fix missing upb.hpp in python source wheel.

@donnadionne

Adhoc distribtest flow: https://g3c.corp.google.com/results/invocations/7a9a3047-95ec-4b14-9607-1a80d2f6532b

Resulting grpcio-1.31.0.dev0.tar.gz for the adhoc build https://pantheon.corp.google.com/storage/browser/grpc-testing-kokoro-prod/test_result_public%2Fprod%2Fgrpc%2Fcore%2Fmaster%2Flinux%2Fgrpc_build_packages%2F13059%2F20200721-041828%2Fgithub%2Fgrpc%2Fartifacts%2F still doesn't contain the .hpp files, looks like python is actively resisting adding them.
Maybe the graft command and recursive-include are clashing with each other?

I think I found the real reason why upb.hpp is not included in the python source wheel and it's really wicked :-)
I think graft third_party/upb works just fine, but then the *.hpp file gets stripped out of the tar.gz
https://github.com/grpc/grpc/blob/5d803dcd3f24cbac609fa2390ff897b3243f14d2/tools/run_tests/artifacts/build_artifact_python.sh#L55
I'm testing a fix right now.

Also looks like I'm not the only one who got bitten by the "garbage exclusion": https://github.com/grpc/grpc/pull/19891 (found that when searching though history of build_artifact_python.sh).
CC @veblush  :-)

I verified locally that the file upb.hpp is not missing anymore from the sdist package.
(by running DOCKERHUB_ORGANIZATION=grpctesting tools/run_tests/task_runner.py -f python artifact manylinux2010 cp37-cp37m x64 and inspecting the grpcio-1.31.0.dev0.tar.gz under artifacts/ directory)
I started another adhoc distribtest flow to double check:
https://g3c.corp.google.com/results/invocations/d155a522-30a2-42fd-9223-d00577b5473a

Created a separate PR with a fix: https://github.com/grpc/grpc/pull/23565

All distribtests are passing: https://sponge.corp.google.com/target?id=eb9511e8-30f4-41ff-8847-76b105f84a30&target=grpc%2Fcore%2Fexperimental%2Fgrpc_distribtests_multiplatform&searchFor= (which also means that both #23552 and https://github.com/grpc/grpc/pull/23565 are good fixes).


Feature/connection middleware

Closes #16
Connections (and transports in general) now have a full set of middleware and handlers.
However the way this is exposed to the User leads a lot to be desired. We should probably move towards a Config-Driven way of handling middleware configuration, so middleware is set up before the channel / connection is created rather than on it once it is running.

Checks passed on forced re-run


GitHub Profile Social Links not recognized

The Github Link in the Profile is defined as
<a rel="nofollow me" class="Link--primary" href="https://server.tld/@user"><EMAIL_ADDRESS>and is not recognized by StreetPass.
It would be great if I could collect these links as well.
Thanks for a great Browser extension

It works for me at the moment:

Went to your GitHub page.

Sometimes if the mastodon server is down it doesn’t track a valid link as a profile. Only bummer is I permanently cache that link as a “not-profile” value so it won’t be fixed next time you go to the page with the server working. This issue is on the roadmap for fixes!

Another thing it could have been: if you’ve seen this profile on another site already, it doesn’t get added a 2nd time to the list

Another thing it could have been: if you’ve seen this profile on another site already, it doesn’t get added a 2nd time to the list

I assume that was the trap i fell into, it's working for me as well.
Thank you for the clarification!


Historical energy data in OpenNEM (wildly) inconsistent with CER data

I'm not sure of the data source for the opennem generation data for coal and gas but because I was interested in emissions intensity I started looking at the Clean Energy Regualtor's generation by facility data for 2019-20 (FY20).
It's probably to be expected that there will be differences in emissions data between sources due to the rubbery nature of emissions intensity indexes (used in openNEM to convert the energy [MWh] database to emissions [tCO₂-e] for the UI views/reporting), measurement and national reporting. What I wasn't expecting was big differences in the underlying energy (MWh) data between openNEM and the CER data.
I've only compared 4 facilities so far, all gas and all in WA. But some of the comparable numbers are close and others are dramatically different.
Here's a sample of the reporting differences (link to excel file)

Reporting entity
Facility name
State
Electricity production [MWh]
OPENNEM Energy FY20 [MWh]
delta
% Delta A
% Delta B

AGL ENERGY LIMITED
Kwinana Swift Power Station
WA
123,007
122,394
-613
0%
-1%

ELECTRICITY GENERATION AND RETAIL CORPORATION
Kwinana Power Station
WA
793,439
1,414,799
621,360
78%
44%

INTERNATIONAL POWER (AUSTRALIA) HOLDINGS PTY LIMITED
Kwinana Cogeneration Plant
WA
940,981
241,884
-699,097
-74%
-289%

NEWGEN KWINANA HOLDINGS PTY LTD
Kwinana Gas Fired Power Station
WA
1,724,343
1,695,385
-28,958
-2%
-2%

I guess next step is to DL and compare with AEMO SCADA data.

I should add that CER data is widely regarded as having lots of issues, so I'm not pointing the finger at OpenNEM at all, just raising the issues for further discussion/investigation.

I've now compared all the fossil generation on the SWIS and most of the comparisons for energy and emissions between CER and openNEM data are out buy at least a magnitude of ~10%, some much greater than that (up to 153%).
Excel file here.
Numbers file here

Facility name
Electricity production (MWh)
Total emissions (t CO2-e)
Emission  intensity  (t CO2-e /  MWh)
Primary fuel
OpemNEM Facility name
Technology
Capacity
Emissions  Intensity [kgCO₂e / MWh]
OpemNEM Electricity [MWh]
OpemNEM Emissions [tCO2-e / MWh] (Inferred)
EnergyDifference CER vs OpenNEM[MWh]
Energy2*Difference / (CER + OpenNEM)[%]
Emissions Difference [tCO2-e / MWh]
Emissions 2*Diff / (CER + OpenNEM)

Bluewaters Power 1
1,613,610
1,219,437
0.75
Black Coal
Bluewaters G1
Coal
217
880
1,466,669
1,290,669
146,941
9.5%
-71,232
-5.7%

Bluewaters Power 2
1,689,841
1,256,311
0.74
Black Coal
Bluewaters G2
Coal
217
910
1,535,867
1,397,639
153,974
9.5%
-141,328
-10.7%

Collie Power Station
1,043,412
958,188
0.92
Black Coal
Collie G1
Coal
318
910
950,734
865,168
92,678
9.3%
93,020
10.2%

Muja Power Station
3,587,410
3,262,123
0.91
Black Coal
Muja C & D Total (4 units)
Coal
814.6
920
3,342,375
3,074,985
245,035
7.1%
187,138
5.9%

Kalamunda Power Station
0
1
0.00
Diesel

Ravensthorpe Power Station
69
50
0.72
Diesel

Alinta Pinjarra Generation Facility
1,594,393
1,087,443
0.68
Gas
Pinjara
OCGT
286
670
1,558,189
1,043,987
36,204
2.3%
43,456
4.1%

Cockburn Power Station
130,959
52,840
0.40
Gas
Cockburn
CCGT
250
390
123,474
48,155
7,485
5.9%
4,685
9.3%

Kalgoorlie Gas Turbine Station
5,433
5,283
0.97
Gas

Kalgoorlie Power Station
279,941
156,822
0.56
Gas

Kambalda Power Station
284,226
155,829
0.55
Gas
Kambalda
OCGT
23
960
131,827
126,554
152,399
73.3%
29,275
20.7%

Kemerton Power Station
131,827
88,548
0.65
Gas
Kemerton
OCGT
309
700
950,734
665,514
-818,907
-151.3%
-576,966
-153.0%

Kwinana Cogeneration Plant
780,046
403,357
0.52
Gas
Kwinana Cogen
OCGT?
42
580
241,876
140,288
538,170
105.3%
263,069
96.8%

Kwinana Gas Fired Power Station
2,027,187
795,906
0.39
Gas
Newgen Kwinana
CCGT
335
540
1,989,822
1,074,504
37,365
1.9%
-278,598
-29.8%

Kwinana Power Station
669,920
355,381
0.53
Gas
Kwinana
OCGT
296
520
1,227,361
638,228
-557,441
-58.8%
-282,847
-56.9%

Kwinana Swift Power Station
34,511
20,977
0.60
Gas
Kwinana Swift
OCGT
116
578
34,364
19,877
147
0.4%
1,100
5.4%

Mungarra Gas Turbine Station
30,926
25,262
0.82
Gas
Mugarra
OCGT
117
780
30,585
23,856
341
1.1%
1,406
5.7%

Newgen Neerabup Power Station
200,465
124,564
0.60
Gas
Neerabup
OCGT
342
600
198,685
119,211
1,780
0.9%
5,353
4.4%

Parkeston Power Station
261,661
146,132
0.56
Gas
Parkeston
OCGT
68
600
46,994
28,196
214,667
139.1%
117,936
135.3%

Pinjar Gas Turbine Station
559,454
497,194
0.89
Gas
Pinjar
OCGT/Distillate
576
820
552,704
453,217
6,750
1.2%
43,977
9.3%

Wagerup Power Station
334,356
189,349
0.55
Gas
Wagerup
OCGT
408
560
387,887
217,217
-53,531
-14.8%
-27,868
-13.7%

any ideas could possibly be going on here @simonhac ?
There are very large discrepancies in some cases, very similar numbers in other cases and some in between.

Facility name
WA
Electricity (MWh)
emissions (tCO2e)
OpemNEM [MWh]
OpemNEM [tCO2e/MWh]
Energy Difference / (CER + OpenNEM)[%]
Emissions Diff / (CER + OpenNEM)

Bluewaters Power 1
WA
1,613,610
1,219,437
1,466,669
1,290,669
4.8%
-2.8%

Bluewaters Power 2
WA
1,689,841
1,256,311
1,535,867
1,397,639
4.8%
-5.3%

Collie Power Station
WA
1,043,412
958,188
950,734
865,168
4.6%
5.1%

Muja Power Station
WA
3,587,410
3,262,123
3,342,375
3,074,985
3.5%
3.0%

Kalamunda Power Station
WA
0
1

Ravensthorpe Power Station
WA
69
50

Alinta Pinjarra Generation Facility
WA
1,594,393
1,087,443
1,558,189
1,043,987
1.1%
2.0%

Cockburn Power Station
WA
130,959
52,840
123,474
48,155
2.9%
4.6%

Kalgoorlie Gas Turbine Station
WA
5,433
5,283

Kalgoorlie Power Station
WA
279,941
156,822

Kambalda Power Station
WA
284,226
155,829
131,827
126,554
36.6%
10.4%

Kemerton Power Station
WA
131,827
88,548
950,734
665,514
-75.6%
-76.5%

Kwinana Cogeneration Plant
WA
780,046
403,357
241,876
140,288
52.7%
48.4%

Kwinana Gas Fired Power Station
WA
2,027,187
795,906
1,989,822
1,074,504
0.9%
-14.9%

Kwinana Power Station
WA
669,920
355,381
1,227,361
638,228
-29.4%
-28.5%

Kwinana Swift Power Station
WA
34,511
20,977
34,364
19,877
0.2%
2.7%

Mungarra Gas Turbine Station
WA
30,926
25,262
30,585
23,856
0.6%
2.9%

Newgen Neerabup Power Station
WA
200,465
124,564
198,685
119,211
0.4%
2.2%

Parkeston Power Station
WA
261,661
146,132
46,994
28,196
69.5%
67.7%

Pinjar Gas Turbine Station
WA
559,454
497,194
552,704
453,217
0.6%
4.6%

Wagerup Power Station
WA
334,356
189,349
387,887
217,217
-7.4%
-6.9%

related #104


Added indicator for most cost effective upgrade

Change the color from yellow to red, maybe, we could add some explaination about this, too.
@xPaw

Red would be too much, color is fine. Perhaps, add toggle for this, which would also explain what it does.

There's no need for a toggle, just a simple note somewhere would do.

@xPaw should work on chrome now

I think changing the color of the upgrade's background would look better than changing the color of the name.

Agree'd yellow text is far too subtle.

By Reading the code, it does not look like this code take in consideration that the price of 10 lvl 1 upgrades need to be cheap than 1 lvl 2 upgrade for that to be "better".
Is there a function in the core of s() that calculate this?

@luanmuniz if that's your conclusion then you are reading the code wrong

is the price increase taken into account at all? 10x tier 2 upgrades does
not cost the same as 1x tier 3 upgrade
On Mon, Jun 15, 2015, 18:49 Rossen Georgiev<EMAIL_ADDRESS>wrote:

@luanmuniz https://github.com/luanmuniz if that's your conclusion then
you are reading the code wrong
—
Reply to this email directly or view it on GitHub
https://github.com/SteamDatabase/steamSummerMinigame/pull/143#issuecomment-112134024
.


Feat: Improving UI of trending bookd section

Describe the feature
Hello @anuragverma108 , I would like to improve the UI of trending books section in book recommendation page.
Kindly assign me this issue under GSSoC'244, I'll do my best.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello @anuragverma108 ,
Can this issue be assigned to me for Gssoc'24.
Regards,
V Meenakshi Iyer


Added guidelines for Java code reviews.

Added guidelines for Java code reviews.

I think it's really important to mention the usage of build automation tools. Every java project should benefit form one of these tools to manage project dependencies as well as facilitate project's integration with CI/CD.
tools such as:
Maven: http://maven.apache.org/
Gradle: https://gradle.org/
Ant: http://ant.apache.org/

@polarapfel Thank you so much for this contribution - the playbook has undergone a facelift/structural change, please could you rebase and update the PR. We are working on a process to make approval faster so please reach out once you have updated. Thanks!

Please could you update and open a new PR for this given the new playbook structure? The content should be moved to this location https://github.com/microsoft/code-with-engineering-playbook/tree/master/pull-requests/code-reviews/recipes. Thank you.


Solve soft AP issues with S7 device

See slack convo here:
https://s.slack.com/archives/mobile/p1484187354000151

The proposed fix for this is on this pr

Just wanted to check in on if this issue is fixed yet. I have tested on the latest version 0.4.5 and with the latest Particle app in the play store and still can't seem to detect a device on a Galaxy S7 and Android version 6.0.1

@sismanis Works fine on my Galaxy S7 6.0.1 (each app and library version is tested on this device). Is it single Photon device that isn't showing up or multiple ones?


new: Write a Get involved/Request new features doc

Published file: https://athensresearch.gitbook.io/handbook/community/get-involved/learning-at-athens-academy-education/request-new-features
Markdown file: https://github.com/athensresearch/handbook/blob/main/community/get-involved/learning-at-athens-academy-education/request-new-features.md

This is a really important page for the Athens community, as we have lots of feature requests, and we want to make sure they're managed thoughtfully through the entire process.
This document should answer the following questions:

How can I put my support behind an existing request?

Find the request on GitHub and give it an vote.

What are some prerequsites to filing a feature request?

Search Github Issues and Github Discussions to see if your feature has already been requested

Where do feature requests go?

Informally, in the #feature-requests channel on Discord.
Formally, in the feature requests Discussion page: https://github.com/athensresearch/athens/discussions/categories/feature-requests

What is a good feature request?

Look at https://github.com/athensresearch/athens/discussions/826 for context.
More information and discussion probably needed here.

What are the next steps?

A few possible outcomes:

The core team puts it on the roadmap and starts working on it.
An external contributor starts working on it.
The core team creates a Gitcoin bounty on it to prioritize and incentivize the work.
Nothing. Sometimes we can't support feature requests, for example, if they conflict with our vision.

Fixed by 022143f


Mask for disabled / inactive components

Variant on LoadMask, but without the spinner.
Could be integrated in forthcoming Panel component via a convenience disabled prop there, but also might be useful in other standalone cases for other containers, etc.

From ATM:
I think it would be very useful if we could integrate into Panel from the get-go via a disabled (or masked?) prop, as I bet that will be the most common case. Could you please look at doing so?


[Snyk] Upgrade puppeteer from 19.2.2 to 19.3.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade puppeteer from 19.2.2 to 19.3.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released a day ago, on 2022-11-23.

Release notes

Package name: puppeteer

19.3.0 - 2022-11-2319.3.0 (2022-11-23)
Miscellaneous Chores

puppeteer: Synchronize puppeteer versions

Dependencies

The following workspace dependencies were updated

dependencies

puppeteer-core bumped from 19.2.2 to 19.3.0

19.2.2 - 2022-11-0319.2.2 (2022-11-03)
Dependencies

The following workspace dependencies were updated

dependencies

puppeteer-core bumped from 19.2.1 to ^19.2.2

    from puppeteer GitHub release notes

Commit messages

Package name: puppeteer

c4803e4 chore: release main (#9313)
689a084 chore(ng-schematics): Spawn server when running `ng e2e`  (#9306)
181b20f test: mark Frame.waitForSelector test as flaky in headful Firefox (#9307)
0ed361d chore: update latest release sha (#9311)
3994cdc chore: specify latest-release for puppeteer (#9309)
750f236 chore: include component in puppeteer tag (#9303)
eda1827 docs: add bug triage guidelines (#9305)
bef1061 feat(puppeteer-core): Infer element type from complex selector (#9253)
16784fc chore(ng-schematics): Update `ng e2e` to custom builder (#9300)
0107ad8 chore: use groupName in release-please manifest (#9292)
0a2d310 docs: fix typo in Viewport fields (#9293)
b6ffa73 docs: fix cross-browser.js example (#9291)
078d385 chore(ng-schematics): publish v0.0.1 (#9290)
65007a2 chore: deprecate old versions (#9277)
be33929 feat(ng-schematics): Release @ puppeteer/ng-schematics (#9244)
1b3dfec chore: Update ng-schemactics README (#9269)
57f7366 chore: Add Node testing option in ng-schematics (#9266)
e003513 fix: remove boundary conditions for visibility (#9249)
86abe68 chore: Add Mocha option to ng-schematic (#9259)
1bbecb3 chore: Add Jest as a ng-schematics option (#9257)
9545691 chore: define release-please component (#9252)
b57b5b3 chore: try linked versions for release (#9245)
e55fed9 chore: use npm 8.3 on windows with node 14 (#9246)
30c6b13 chore: re-export all exports (#9241)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Coverage remained the same at 99.223% when pulling 949e92e53a7851d54f9113838fa260420b5747ae on snyk-upgrade-0ece50a3f80c060356dafdcb67a82376 into b441d1e6c0bd3e607744a9c41548b10a719a8d73 on master.


chore: add error instructions for lake build failure troubleshooting

This PR add some error instructions for lake build failure troubleshooting, especially when failed to build some executable targets.
Closes #4752
Related to #288

I should only filter error logs...


refactor(resolve): remove allowLinkedExternal parameter from tryNodeResolve

Description
allowLinkedExternal was only used for createIsConfiguredAsExternal so I moved that logic to there and remove it from tryNodeResolve.
Also removed some | undefined to make the types more simple.

Superseded by https://github.com/vitejs/vite/pull/18670


How can I dynamically increase the height of the tooltip based on the content

Can you please be more specific about what content you are trying to display, using what method, and what is not working?

I have a similar issue, where the the text is just overflowing out of the toopTip container. Instead, I want the tool tip with fixed width and the height to increase based on content instead of single line text.

Same as above, currently the tooltip only accept  to start a newline, however it could introduce issues for user who uses smaller screen resolution.
I think maybe it's better to implement a "maxwidth" props so we can control the style easier.
Thanks.


feat(StepNavigation) Add StepNavigation component

Co-authored-by: Sungwon Ma<EMAIL_ADDRESS>Co-authored-by: Jenn Miller<EMAIL_ADDRESS>Title
Description

Merging your changes
When you are ready to merge to master and publish your changes, use the "squash and merge" button in GitHub, and follow the PR Title Guide to format your PR title and write your PR merge description.
IMPORTANT: If your PR contains breaking changes, please remember to follow the instructions for breaking changes!

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


EverParse3d.InputStream.Extern.fst: fix proof regression

This proof regressed again. I tried to stabilize it by splittin queries, but ran into this:
(EverParse3d.InputStream.Extern.fst(246,1-271,5))	Query-stats (EverParse3d.InputStream.Extern.peep, 63)	failed {reason-unknown=unknown because Overflow encountered when expanding old_vector} in 42 milliseconds with fuel 0 and ifuel 1 and rlimit 256

which is a z3 bug. To work around it I also added --z3refresh, and now this works reliably, albeit slowly.
I wanted to add hints but noticed there are none in the repo?

We have not been using hints in EverParse. The proofs have generally been stable without them.
But this particular proof is a repeat offender.
@tahina-pro can you take a look at this proof and see if it can be made more explicit/split into smaller parts etc.?

But this particular proof is a repeat offender. @tahina-pro can you take a look at this proof and see if it can be made more explicit/split into smaller parts etc.?

I claim #115 should make this proof much more robust.


RFE: Allow setting of fsType, format, and mount options

Allow setting of fsType (ex: ext4, xfs), format options (ex: -b blocksize), and mount options for dynamically provisioned volumes.
It could be implemented via Trident annotations or leverage k8s constructs if they become available, see:

PR45345
issue37801
mount options

Looks great, thanks!
# cat pvc-bronze-xfs.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: bronzetest
  annotations:
    trident.netapp.io/fileSystem: xfs
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
  storageClassName: bronze

# kubectl create -f pvc-bronze-xfs.yaml
persistentvolumeclaim "bronzetest" created

# kubectl get pvc bronzetest
NAME         STATUS    VOLUME                     CAPACITY   ACCESSMODES   STORAGECLASS   AGE
bronzetest   Bound     default-bronzetest-09f5e   5Gi        RWO           bronze         14s

# kubectl describe pv default-bronzetest-09f5e
Name:           default-bronzetest-09f5e
Labels:         <none>
Annotations:    pv.kubernetes.io/provisioned-by=netapp.io/trident
                volume.beta.kubernetes.io/storage-class=bronze
StorageClass:   bronze
Status:         Bound
Claim:          default/bronzetest
Reclaim Policy: Delete
Access Modes:   RWO
Capacity:       5Gi
Message:
Source:
    Type:               ISCSI (an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod)
    TargetPortal:       <IP_ADDRESS>:3260
    IQN:                iqn.2010-01.com.solidfire:pnay.default-bronzetest-09f5e.2569
    Lun:                0
    ISCSIInterface      default
    FSType:             xfs
    ReadOnly:           false
    Portals:            []
    DiscoveryCHAPAuth:  false
    SessionCHAPAuth:    false
    SecretRef:          <nil>
Events:                 <none>

Requested mount options in https://github.com/NetApp/trident/issues/49
Format options are not currently supported by k8s, so this request is withdrawn until support in k8s arrives.


engine/sched: modify sched interface

Due to the modification of the scheduler, the initialization of
environment variables needs to be adapted to the customizable scheduler.
Signed-off-by: Longfang Liu<EMAIL_ADDRESS>

The current patch relies on the patch integration of the uadk scheduler, and then the patch is combined


Read a FASTA file containing multiple sequences, extract the definition and sequence from each.

Fasta files contain multiple sequences, delimited by an empty line. Each sequence contains a header line that begins with '>' and then multiple lines of sequence data.
This pull request assumes that there are one or more sequences per file, and reads them into an array. Sequence.Definition and Sequence.Sequence are populated per sequence.
The sequences themselves are not validated, and nor are the header lines.

@0x106 this looks awesome. The only thing I'd do is create a separate BuildFasta function from WriteFasta but these changes can be squashed and merged before then. I'll also close out issue #10.


Use steam market_hash_name as name in Skin Endpoint

Hi @ByMykel,
first of all, this project is super nice and very helpful! Thank you for creating this API! :-)
As I played around with the data, I found that the "wears" in the Skins endpoint might be not the best solution, when the idea is to use this API as a starting point and get for example price information from a second API, as you suggested in https://github.com/ByMykel/CSGO-API/issues/34.
The "problem" is that a lot of other services uses the market_hash_name from steam as unique identifier for a skin.
In the market_hash_name the structure of the name is something like this:
%Stattrack% %NAME_OF_SKIN% (%WEAR%)
It would be easier to connect third party services when your naming system would follow this structure.
I understand that this would mean that the JSON File would grow a lot, so this is just a suggestion, as it is also possible to transform the data on "our" side, when we aggregate the data in a database.
Nevertheless I suggest to follow the market_hash_name pattern, as you do this already in the Sticker Endpoint.

first of all, this project is super nice and very helpful! Thank you for creating this API! :-)

Thank you for opening issues suggesting things to improve this project.

It would be easier to connect third party services when your naming system would follow this structure.
I understand that this would mean that the JSON File would grow a lot, so this is just a suggestion, as it is also possible to transform the data on "our" side, when we aggregate the data in a database.

As you mention that would make the JSON File grow a lot, public/api/en/all.json is already 6.6 MB.
My idea with name imitate the community market, but I run into this #32 issue that i kind of know how to solve.
I had the idea of making a separate endpoint that returs all the skins in every state (stattrak, not stattrak, FN, MW, etc) without grouping them and I think it making sense to implement it.
Solution
New endpoint /skins_not_grouped.json (provisional name) that would not be in public/api/en/all.json with the new attribute market_hash_name
What do you think @RatzeR, with this new endpoint should we group doppler and gamma doppler skins as suggested in #37 ??

I think this is a good idea! So you avoid breaking changes in the current API and also provide a new one which is aligned with the Community Market!
Regarding the Gamma Doppler Skins:
In this new API I would suggest to go with you first suggestion:
{
    "phases": [
        { "phase": "Phase 1", "paint_index": 852, "image": "phase1_url"  },
        { "phase": "Phase 2"," paint_index": 853, "image": "phase2_url"  },
        { "phase": "Phase 3", "paint_index": 854, "image": "phase3_url" },
    ]
}


client.Integrations.Get() error

After last fix there is a new issue:
System.Runtime.Serialization.SerializationException
HResult=0x8013150C
Message=There was an error deserializing the object of type SendCloudApi.Net.Models.Integration[]. String '2021-03-08T11:00:24.277796+01:00' was not recognized as a valid DateTime.
Source=System.Private.DataContractSerialization
StackTrace:
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializerImpl.ReadObject(XmlDictionaryReader reader)
at System.Runtime.Serialization.Json.DataContractJsonSerializerImpl.ReadObject(Stream stream)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(Stream stream)
at SendCloudApi.Net.Helpers.JsonHelper.Deserialize[T](String json, String dateTimeFormat)
at SendCloudApi.Net.SendCloudApi.d__251.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at SendCloudApi.Net.SendCloudApi.d__221.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at SendCloudApi.Net.Resources.SendCloudApiAbstractResource.d__141.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at SendCloudApi.Net.Resources.SendCloudApiIntegrationsResource.d__1.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
Inner Exception 1:
FormatException: String '2021-03-08T11:00:24.277796+01:00' was not recognized as a valid DateTime.
I think the issue is that you use DateTime instead of DateTimeOffset everywhere

This one should also be solved now.

Yes, it works


Add the unmark command

Add the unmark command to mark a student as not having attended the class.

Unmark command should only modify the right side

Completed via #180


[skip ci] docs: add instructions for installing Ansible

Add RPM and DEB instructions for installing Ansible.

thanks @ktdreyer

@ktdreyer this PR is perfect example of PR that should have [skip ci]  in their title :). For next time ;).
Thanks!

I was just wondering why the CI was red ;)


Projected zenith convenience function

[x] Closes #1734
[x] I am familiar with the contributing guidelines
[x] Tests added
[x] Updates entries in docs/sphinx/source/reference for API changes.
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Adds a function that calculates the projected solar zenith.
Pending tasks:

[ ] Add paper references
[ ] Add diagram?

about the diagram, should I replicate it?

Such a diagram might be helpful, but no need in this PR IMHO.  I'm not sure where it would live anyway.  I don't think we currently have any diagrams in function-level documentation.  I guess it could be in a gallery example (or a new User's Guide page) but unless it improves on the references, I'd say let's not bother :)

may be better to write pure NumPy python so anyone can numba-decorate it

Is there a reason this function needs JIT more than the rest of pvlib does?  We use sind et al for code readability, so unless this function is special somehow, I think we should stick with that convention.  (as an aside, I'd be surprised if numba couldn't handle pvlib.tools.sind, but I don't know for sure either)

About the tests, do you have any data handy for that

Slope-Aware Backtracking has a small validation dataset in a table at the end.  It's not enough on its own for this PR, but it's at least a start, and can be easily extended in at least one way (subtract 180 from axis_azimuth and negate the expected PSZAs).  I'm not aware of any other existing datasets to use.  The tracker_theta output of pvlib.tracking.singleaxis with backtrack=False and max_angle=180 can be used to calculate expected values for additional test cases.

subtract 180 from axis_azimuth and negate the expected PSZAs

I can't make this work. Could you double check if that's supposed to happen?
    # test by changing array azimuth
    psz = psz_func(
        array_tilt,
        array_azimuth-180,
        timedata["Apparent Elevation"],
        timedata["Solar Azimuth"],
    )
    assert_allclose(psz, -timedata["True-Tracking"], atol=1e-3)

subtract 180 from axis_azimuth and negate the expected PSZAs

I can't make this work

My mistake, I forgot those test cases used a nonzero axis_tilt.  Negate the axis tilt as well and I think that little trick should work.

I've left out whether the result is valid like pvlib.tracking.singleaxis does.

@kandersolar , GitHub does not allow me to reply to your last review message, so here it goes:

we might as well choose axis_ for consistency with the reference

I agree it's a good point. It's difficult to understand exactly the vectors and the projection plane without reading it. In fact, such a recommendation would be a nice addition the notes section.

we're going to have to include some kind of explanation/clarification

I also agree with that. But regarding the suggested explanations, I think it would be better to describe the use cases with real examples in general. If I didn't already know about the internals and purposes, I wouldn't understand why the math is also applicable to fixed-tilt arrays since the paper only talks about SATs and the optimal rotation angle. I would ask myself what would be the rotation angle in a fixed-tilt array. My suggestion, feel free to edit as much as yall want:
    Notes
    -----
    This projection has a variety of applications in PV. For example:

    - Given a single-axis tracker, a plane whose normal vector's
      ``axis_azimuth`` equals the torque tube direction and its ``axis_tilt``
      is the zero rotation angle, this function yields the optimal angle to
      point to in order to maximize direct irradiance capture (this is called
      :ref:`true-tracking
      <sphx_glr_examples_plot_single_axis_tracking.py:True-tracking>`).

    - Given rows of PV arrays (or other sunlight obstacles), a projection plane
      that contains the module's normal vector (i.e., its ``axis_azimuth`` is
      the module's normal vector's azimuth shifted ``-90º``) and its
      ``axis_rotation`` is zero, the result is the smallest angle between the
      shadow plane and a horizontal plane.
      See :py:func:`pvlib.shading.tracker_shaded_fraction`.

I wouldn't change the current arguments definitions (almost due to the 1:1 relation with the paper). Maybe move your suggested clarifications to the notes section, although I'm not sure of how to integrate them.
I'd like to clear up that I don't have a problem applying your suggestions straight forward if you want to, specially due to my lack of experience in PV and the language barrier. And that I hope this comment helps improving the quality of the PR and doesn't add noise to the conversation.

I'd like to move forward this PR another bit, specially the docstring. Would you like me to push @kandersolar suggestions, or give another suggestions? Feel free to request anything from my side.

Thanks @echedey-ls for keeping this going :)
Describing some real use cases is a great idea, and I like your proposed text.  What do you think about a combination of Notes and Examples like this?
    Notes
    -----
    This projection has a variety of applications in PV. For example:

    - Projecting the sun's position onto the plane perpendicular to
      the axis of a single-axis tracker (i.e. the plane
      whose normal vector coincides with the tracker torque tube)
      yields the tracker rotation angle that maximizes direct irradiance
      capture.  This tracking strategy is called
      :ref:`true-tracking
      <sphx_glr_examples_plot_single_axis_tracking.py:True-tracking>`.

    - Self-shading in large PV arrays is often modeled by assuming
      a simplified 2-D array geometry where the sun's position is
      projected onto the plane perpendicular to the PV rows.
      The projected zenith angle is then used for calculations
      regarding row-to-row shading.

    Examples
    --------

    Calculate the ideal true-tracking angle for a horizontal north-south
    single-axis tracker:

    >>> rotation = projected_solar_zenith_angle(solar_zenith, solar_azimuth,
    >>>                                         axis_tilt=0, axis_azimuth=180)

    Calculate the projected zenith angle in a south-facing fixed tilt array
    (note: the ``axis_azimuth`` of a fixed-tilt row points along the length
    of the row):

    >>> psza = projected_solar_zenith_angle(solar_zenith, solar_azimuth,
    >>>                                     axis_tilt=0, axis_azimuth=90)

I like that pretty much, thanks for the improvements. I will add the still inexistent pvlib.shading.tracker_shaded_fraction to the see also section and the notes section in its PR (#1962). Just in case anyone heard of the PSZA for the calculation of shadows so that s/he finds the upcoming feature.
You can check the docs out here.

I had some trouble finding the example's link. I can add a section link too but reading it all seems a better choice.
From my side, this looks like it can be merged!

Thanks for this contribution and the patience @echedey-ls :)


Change Server motd and image

Like the title say:
How can i change the motd message of the minecraft server and how can i change the server logo?

You can configure the MOTD on first-startup using the config in
https://github.com/itzg/docker-minecraft-server#message-of-the-day
however, changing it later requires manually modifying server.properties (until I enhance that process)
You can have it download and convert a server icon using the config in
https://github.com/itzg/docker-minecraft-server#server-icon
however, if there is already a server-icon.png file in the data directory it will skip that process. To change it later, you could manually place the new file there or delete the existing one and let the next container startup re-process it.

Thank you.


Fix Safari spinner rendering

Fixes: https://github.com/go-gitea/gitea/issues/29041
Fixes: https://github.com/go-gitea/gitea/pull/29713
Any of the width: *-content properties seem to workaround this Webkit bug, this one seemed most suitable.
Before:

After:

Tested in Safari 17.4 😉

Not sure if 1.20 will see more releases, but this should be a clean merge 😆

Ah, I think I may have confused the bot. Well, I assume 1.20 isn't going to get any more releases.


Make the website responsive to different browsers, browser sizing, mobile, tablet, etc.

The application isn't working in Internet Explorer. Please test functionality in Firefox and Edge.

Make separate tickets for each page that requires an update. Only pages that are not behind a log-in screen.


Use git subtree mechanism for simdcomp to simplify build (cf. #24)

This should make the initial checkout and build more robust
The subtree was created with
git remote add simdcomp https://github.com/lemire/simdcomp.git
git fetch simdcomp
git subtree add --prefix cpp/simdcomp simdcomp 0dca28668f1fb6d343dc3c62fa7750a00f1d7201 --squash

Coverage remained the same at 92.123% when pulling a667394a49754062f430573163c2f41f429555d2 on manuel-woelker:pr-subtree into f729edb529a4caabcbd0f8fd9953660091e36e40 on tantivy-search:master.

Awesome thank you!


Listener bindings - part of #6

URL of codelab
https://github.com/google-developer-training/android-basics-kotlin-cupcake-app
In which task and step of the codelab can this issue be found?
#6 - Adding android:onClick="@{()...." to radio buttons on the fragment_flavor.xml layout.
Describe the problem
If you select any flavor (I selected "salted caramel", the app terminates with this exception:
java.lang.IllegalStateException: Could not find method @{() -> viewModel.setFlavor(@string/salted_caramel)(View) in a parent or ancestor Context for android:onClick attribute defined on view class com.google.android.material.radiobutton.MaterialRadioButton with id 'salted_caramel'
Steps to reproduce?

Add the listener bindings to the fragment_flavor.xml layout
Build and run the app
Select a quantity on 1st fragment screen
Select ANY flavor on the 2nd fragment screen
You'll get the above error

Versions
Studio Build: AI-211.7628.21.2111.8193401
Version of Gradle Plugin: 7.1.2
Version of Gradle: 7.2
Version of Java: Could not find a JAVA version anywhere, but found this: default JDK: 11.0.11
OS: Windows 10
Kotlin Plugin: JetBrains 211-1.6.10-Release-923-AS7442.40
Additional information
Include screenshots if they would be useful in clarifying the problem.

Typo error...found it!  Sorry...


Sample Project Not Running

First thanks for providing an elaborate example on how to implement the graphql-sse using nestjs
But I am facing on issue, i am unable to access the graphql subscription upon starting the nestjs application
http://localhost:3333/graphql-subscription
{"statusCode":404,"message":"Cannot GET /graphql-subscription","error":"Not Found"}
If you can provide a way to fix this it would be very helpful
Once again thanks for this awesome examples

Hey, sorry about the late response. Did you manage?


translationFilterProviderError AngularJS Error if International is not used.

I started a new Jhipster application and chose not to have International support. When I started adding my entities AngularJs failed to boot strap on my entities and started to get the following AngularJS error:
Error: [$injector:unpr] Unknown provider: translateFilterProvider <- translateFilter
This is without me adding a single character of code.
I then regenerated the project and this time I chose International support and that went fine and smooth without error.
I created all my entities using jhipster-uml (V1.6.1) JDL script.

This doesn't concern JHipster UML. Post it in the main project's issue tracker.


Create a Business Service with Node.js Using Visual Studio Code

Tutorial: https://developers.sap.com/tutorials/cp-apm-nodejs-create-service.html
Write here what you need help with ...
At Step7: the url 'http://localhost:4004/catalog/Authors?$expand=books($select=ID,title)' was listing all the authors with their books(with ID and Title params) as below:-

To get 'book titled Jane Eyre' one of the possible options on the Books entity would be as below:-
'http://localhost:4004/catalog/Books(207)/title'

Thanks,
Jakes

Hi Jakes,
Thank you for your feedback. As these are only recommendations we would close the issue here and consider your suggestions for the next update of the tutorial.
Best regards,
Iwona

Hi Jakes,
Thank you for your feedback. As these are only recommendations we would close the issue here and consider your suggestions for the next update of the tutorial.
Best regards,
Iwona

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


test_import_time fails with Python 2.7

It can very hardly pass before (about 1/4), but since release 11.4.0 (and maybe because of backports.os?) it cannot pass here after dozens of retries. It passes very stably on Python 3.7 on the same machine, though.
=================================== FAILURES ===================================
____________________ TestPerformance.test_import_time[Path] ____________________

self = <test_path.TestPerformance instance at 0x7f104f62dd88>
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f104f388b50>

    def test_import_time(self, monkeypatch):
        """
            Import of path.py should take less than 100ms.

            Run tests in a subprocess to isolate from test suite overhead.
            """
        cmd = [
            sys.executable,
            '-m', 'timeit',
            '-n', '1',
            '-r', '1',
            'import path',
        ]
        res = subprocess.check_output(cmd, universal_newlines=True)
        dur = re.search(r'(\d+) msec per loop', res).group(1)
        limit = datetime.timedelta(milliseconds=100)
        duration = datetime.timedelta(milliseconds=int(dur))
>       assert duration < limit
E       assert datetime.timedelta(0, 0, 233000) < datetime.timedelta(0, 0, 100000)

test_path.py:257: AssertionError
__________________ TestPerformance.test_import_time[FastPath] __________________

self = <test_path.TestPerformance instance at 0x7f104f62bea8>
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f104f291fd0>

    def test_import_time(self, monkeypatch):
        """
            Import of path.py should take less than 100ms.

            Run tests in a subprocess to isolate from test suite overhead.
            """
        cmd = [
            sys.executable,
            '-m', 'timeit',
            '-n', '1',
            '-r', '1',
            'import path',
        ]
        res = subprocess.check_output(cmd, universal_newlines=True)
        dur = re.search(r'(\d+) msec per loop', res).group(1)
        limit = datetime.timedelta(milliseconds=100)
        duration = datetime.timedelta(milliseconds=int(dur))
>       assert duration < limit
E       assert datetime.timedelta(0, 0, 214000) < datetime.timedelta(0, 0, 100000)

To prove a counterpoint, I just hit that test on a late-2016 MBP and on Python 3.6; the threshold was exceeded by 10 %, or:
E       assert datetime.timedelta(0, 0, 110000) < datetime.timedelta(0, 0, 100000)

I'd still recommend making the critical limit, say, 200 ms instead, and maybe log a warning when duration turns out to be over the old limit of 100 ms.

I'll add a note here: on my aarch64 build-box (quad-core 2GHz Cortex-A72), with Python 3.6.6, this test is taking 277ms.  So yeah...this is a pretty brittle test.


feat(input): create input component

add new component input
add new component textarea
add new component file upload
refactor icon in storybook (use grid for demo)
add validation (check the file type and size)
add hint component

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement searchScopes sans tests

Fixes #23952
Implements a new compiler option called searchScopes. I did implementation first, so I need to implement tests to earn back the changes.

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

I was pleased at how easily I could navigate the TypeScript code base! I earned back the code in the first commit by verifying (via git checkout HEAD~2 ...) that the tests check for the new behavior.
Replying to #23952 commenters @weswigham and @mhegazy, and CCing @DanielRosenwasser whom I spoke to at Build about this. I believe I've implemented the feature I'm requesting here. Or at least I've implemented the tsconfig portion of this, right?
I think I still need to implement something in vscode for the automatic type acquisition, and not just the use of additional search scopes?
Of course, this feature may not end up being accepted. I would be disappointed by that but I do hope an alternative would be proposed to support alternative scope searching for private NPM repositories and to support alternatives to Definitely Typed.

I'd need this too. I have exactly the same setup. A private registry with types that I'd like to supplement the @types with. Also this is very nice for testing types before pushing them to definitelytyped/definitelytyped too


Add generic utils: DeepReadonly and VersionInfo.

This will be used in upcoming locator-related changes.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
~[ ] Has a news entry file (remember to thank yourself!).~
[x] Appropriate comments and documentation strings in the code.
~[ ] Has sufficient logging.~
~[ ] Has telemetry for enhancements.~
[x] Unit tests & system/integration tests are added/updated.
~[ ] Test plan is updated as appropriate.~
~[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).~
~[ ] The wiki is updated with any design decisions/details.~

Codecov Report

Merging #13591 into master will decrease coverage by 0.00%.
The diff coverage is 52.27%.

@@            Coverage Diff             @@
##           master   #13591      +/-   ##
==========================================
- Coverage   59.73%   59.72%   -0.01%
==========================================
  Files         670      670
  Lines       37467    37511      +44
  Branches     5378     5394      +16
==========================================
+ Hits        22382    22405      +23
- Misses      13916    13937      +21
  Partials     1169     1169

Impacted Files
Coverage Δ

src/client/common/utils/misc.ts
73.33% <ø> (ø)

src/client/common/utils/version.ts
49.01% <52.27%> (+20.44%)
:arrow_up:

Continue to review full report at Codecov.

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


Enriching the Lua plugin environment

Hi,
I like coding in Lua, but am finding it difficult to write plugins for micro.
Please correct me if I am wrong - but it feels like a very small proportion of micro is exposed in Lua. Furthermore, to use those objects exposed (as none-iterable userdata) I need to have the skills of a Go programmer to read the source code and discover the object's properties and  methods.
As an example I would like to write a Lua function that returns the word on the left of the cursor:
function selectwordleft(Current)
-- Word to the left
    Current.Buf:SelectWordLeft() -- Fails
    return util.String(Current.Cursor:GetSelection()) or nil
end

I cannot iterate the BufferPane userdata object for a list of its methods/properties, but I know there is a SelectWordLeft method as it is a bindable action and the code is in actions.go - I just can't figure out how to call this from Lua!
If functions are useful/mature enough to be offered as bindable actions - then could they also all be exposed in Lua for scripting?
To make the environment more "Lua like" would it be possible to place the actions in a real Lua  table - micro/actions. The actions table would be discoverable (iterable) and could be included in plugins for easy use:
local act = include(micro/actions)

Sorry I obviously don't have the "GoFu" to offer a pull request :(
Kind Regards Gavin Holt
Specifications
OS: Windows 10
Terminal: Console - (not Legacy, not Terminal App)
Version: 2.0.8
Commit hash: cfcb2e45
Compiled on October 06, 2020

PS. Table iteration to discover functions (helpful unless the function returns a userdata object we can't inspect - catch22!)
function iterate(t,name)
-- Dump table index to terminal
    if type(t)~="table" then return end
    local o = {}
    for i,v in pairs(t) do
        table.insert(o,name.."."..i.." "..type(v).."\n")
    end
    micro.TermMessage(o)
end

-- Using init.lua you can display at startup
    config = include("micro/config")
    iterate(config,"config")

SelectWordLeft is a method of BufPane, so this should work for you:
Current:SelectWordLeft()

Generally, you don't necessarily need to look into the code, you can just look at the documentation (though yeah, a bit of familiarity with Go is expected). Here is the documentation for SelectWordLeft: https://pkg.go.dev/github.com/zyedidia/micro/v2/internal/action#BufPane.SelectWordLeft
As the plugins help says:

The Lua plugin may access any public methods of an object returned by any of the functions above. Unfortunately it is not possible to list all the available functions on this page. Please go to the internal documentation at https://godoc.org/github.com/zyedidia/micro to see the full list of available methods. Note that only methods of types that are available to plugins via the functions above can be called from a plugin. For an even more detailed reference see the source code on Github.

This help probably needs updating, since now godoc.org redirects to pkg.go.dev and it's not obvious how to locate the internal packages documentation at https://pkg.go.dev/github.com/zyedidia/micro. FYI it is at https://pkg.go.dev/github.com/zyedidia/micro/v2/internal.

Hi,
Many thanks, great to see that all the actions are exposed and the pkg.go.dev documents are really helpful. I have downloaded all the documents in the internal section to my help folder for grepping!
Sorry to be so dense.
Kind Regards Gavin Holt

For what it's worth, I also had a hard time finding things when I was trying to write plugins, and though I don't know go, I was fine with trying to read the code.
Dynamic inspectability would be very helpful.
I'm not sure it's technically possible without code generation?


Launching with CreateProcess function

Summary of the new feature/enhancement
Add the ability to launch using the Windows CreateProcess function https://docs.microsoft.com/en-us/windows/desktop/api/processthreadsapi/nf-processthreadsapi-createprocessa so that the terminal can be launched programmatically. Ideally this would mean it would also be possible to launch via command line, with arguments to specify which shell(s) should open in the tabs etc. I'm not sure if this will at all be possible as in the current state I am only able to launch via the start menu, with no launch time parameters available. The only settings I can change are in profiles.json.

This already exists. wt.exe or wtd.exe should be in your PATH, and we have #607 tracking command line arguments.