Update all angular stuff to 1.6.0 at the same time

Still needs an angular material update, which isn't out yet. It's broken with angular 1.6.0, but we needed to update all the angular stuff at once, not in separate PRs.

It looks like the build is broken -- is that related to the angular stuff?

Did you read my comment? We need to wait for angular material to update.
On Fri, 9 Dec 2016, 00:53 Teddy Katz<EMAIL_ADDRESS>wrote:

It looks like the build is broken -- is that related to the angular stuff?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/porygonco/porybox/pull/565#issuecomment-265901913,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACD_4cKGt29C0VJSmDN1DNRXTuR1Gmlaks5rGKaVgaJpZM4LHyo1
.

I saw it, but again, the build is broken right now. We should probably fix that sooner rather than waiting for angular-material to upgrade, even if it means pinning things to 1.5 for the time being.

Oh wait, you mean on master. I thought you meant this branch. See, this is
why I like pinning things always.
On Fri, 9 Dec 2016, 05:55 Teddy Katz<EMAIL_ADDRESS>wrote:

I saw it, but again, the build is broken right now. We should probably fix
that sooner rather than waiting for angular-material to upgrade, even if it
means pinning things to 1.5 for the time being.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/porygonco/porybox/pull/565#issuecomment-265939811,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACD_4XOVW1c6hGoofJb0cViFl4M7rcEzks5rGO04gaJpZM4LHyo1
.

Looks like the 1.6.1 fixes these issues. Will fix up this pr this week sometime.

@not-an-aardvark I don't think I'm causing problems with using the old angular-mocks with new angular, as everything is working. I detailed the issues with the new angular-mock on #586
Can you just give this a quick review before I merge?

Thanks, @not-an-aardvark


Pagerank 6.7.1

This PR add the pagerank example.
The code base contains:

graphit: constains the host code that handling different preprocessing methods over graphs.
kernels: contains different optimization strategies of kernels in pagerank.
Other folders: contains the host code and scipt of running different optimization strategies.

@zzy82518996 do we need the graphit code to compile and run your implementation?

Yes, there are some modifications on the code inside graphit. But most of the modified code corresponds to HB host.

what are the modifications to graphit? can you send me a diff? i'm a bit hesitant to just merge a copy of the graphit source code into this repo. the way we usually handle this at UW is we include a rule for cloning the subrepo in a makefile.
which graphit for is this source code from? i imagine it would be the one associated with BSG?


[Bug] Apt install instructions not working

Describe the bug
Instructions tell us to apt-get install the liblapacke library, however the liblapacke-dev library is needed to get the proper header files in order to properly install.
To Reproduce
Steps to reproduce the behavior:

Open up Ubuntu or Debian based system
Copy-paste install instructions
See that cmake and sudo make install both fail due to liblapacke.h not being installed

Additional context
After sudo apt install liblapacke-dev, I can cmake and install properly, so simply updating the install instructions with the proper library should fix this issue

Many thanks for this feedback, @Polidori-112! We will fix the error in the installation instructions shortly.

The installation instructions are now fixed. Thanks again @Polidori-112 for helping us fix this error.


git command example is incorrect on Authenticating as a GitHub App installation page

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app-installation
What part(s) of the article would you like to see updated?
In the first section About authentication as a GitHub App installation there is an example that has an erroneous " character: git clone<EMAIL_ADDRESS>Additional information
No response

@dom111 Thank you for opening an issue and linking it to your PR! ✨


[deepbook] Better errors, better borrow, more documentation, cleanups

Description
Contains:

cleanups
better variable names
errors cleanup and documentation
better use of coin and balance APIs
removes "returns" in many places

Deprecates (and removes all non-public members):

clob (v1)
custodial (v1)

Only micro-refactoring is adding a function: all_orders_canceled_from_order to reduce code duplication.
Test Plan
Current tests pass, no new features introduced.

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

@healthydeve @666lcz closing this one.


Add right panel for quick navigation of chapters sections

If a story has many chapters and sections, the page can get too long. It will be nice to have a navigation panel to jump to these chapters and sections very fast.

Any news on this? Is there a way of at least showing the nested chapters?


TF Coil Mass Calculation

In GitLab by @jmorris-uk on May 13, 2019, 09:30
The TF coil mass calculation includes a factor of 2.2 to match the ITER98 TF coil mass. However, recent feedback from Pierluigi suggests that the PROCESS TF coil mass output for the 2018 baseline (1400t) it significantly over the estimates from manufacturers (900t).
Removing the 2.2 factor for the 2018 baseline file gives a mass of 875t per coil. Much closer to the manufacturers 900t.

@clmould  I would suggest using data on ITER and JT-60SA coils, rather than estimates for DEMO.  However, you should be careful not to count the intercoil structures twice.
Having said that, it's not clear where you would fit an extra 120% of the calculated coil mass.   :confused:


Involvement flair requirements is incorrectly going based off of number given (from the wrong sub too)

My SVeX "giveaway" with 100 given counted towards the poketrades involvement flair total and it let me apply for flair. However, my poketrades giveaway with 2 does not increment the total, and thus does not count towards flair.
Honestly, I feel like maybe you could split off the giveaway/contests section for /r/pokemontrades into its own thing.

You sure? I tested this one. I would really father not have a separate
section.
On 8 Mar 2015 22:43, "NotRaia"<EMAIL_ADDRESS>wrote:

My SVeX "giveaway" with 100 given counted towards the poketrades
involvement flair total and it let me apply for flair.
Honestly, I feel like maybe you could split off the giveaway/contests
section for /r/pokemontrades into its own thing.
—
Reply to this email directly or view it on GitHub
https://github.com/YaManicKill/flairhq/issues/222.

I'll try again later to confirm.


Fix chat history wrapping

Fixes #1162
I had to edit mixins so I can't actually test one half of this change, but the reason for chat history not wrapping was because of the nbsp() method in the chat history plugin. It was a small hack to prevent chat history messages from triggering various plugins that detect chat messages. It did this by replacing spaces with non-breaking-spaces and that's what broke the wrapping.
However I figured that a better way of doing this now is to not send ChatMessage events for any chat message with a timestamp from before you logged in.

I don't think this will work because the timestamps are applied after the event fires.

That would be a problem. Is it possible to change that?

Closing seeing as the idea behind this won't work.


[sw, dif_plic] Remove redundant code and tidy up the code

There is no need to calculate the multireg register count and register
width in bits, as these values are now auto generated.
MAX Priority is useful outside of the DIF, so it has been exposed to
the consumers of the DIF.

Addressed @lenary comments.
Modified commit message slightly.


Network timeouts from a third party within an atomic phase

Thanks so much for putting this and the corresponding block together. I have a question about wrapping a third party request in a database transaction.
We have a system setup very similar to what is described in the article. The issue that we are facing is that if a third party has a major outage, it can result in long request times and therefore long database connections due to the open transaction. If this is a frequently used third party service, the database connection problem compounds. Many clients are trying to do the same thing over and over and due to the network timeouts from the third party, the database transactions will remain open until they, themselves timeout.
What is the best way of thinking about this? It seems dangerous to couple third party requests with database transactions for this reason.

Hey @tonestrike, just looking over this code again, I think it was a bit of a mistake to have the actual call to Stripe inside a transaction. Long lived transactions are bad, and Postgres connections are finite, so much better to not keep them around network calls (even in non-degenerate situations).
Instead, I'd make sure that information is persisted on both sides of the API call:

If the API supports idempotency keys, generate one and save to the DB (for reuse in the event of a failure), along with committing any other work that was in progress.
Make the API call.
Persist the result of the API call to the DB before moving on to the next phase of work that might fail (so in case it does fail, you don't have to make the API call again).

Hey @brandur, I was wondering how the proposed solution might be introduced with the current implementation of the atomic_phase function?
Currently it wraps the entire block inside a transaction – would you have a version of atomic_phase that doesn't create a transaction but still updates the idempotency key with some new RecoveryPoint at the end?

@brandur I somehow just saw this. Thanks for getting back to me! That makes sense.


Add localization to boilerplate

I think in most common cases at a point in your project you want to be able to roll out your application for multiple languages. With i18next we have a standard and also a react connector to do so. It would be great to have it build right into the boilerplate.

Would love a PR for this :smile

I'll see what I can do. ;)

Hi,
I integrate react-intl in my app ! Maybe i can help !


Docker CLI client not correctly authorizing to private registry with token auth

Description
I am having an issue with my private docker registry, which is using a token auth server I have written.
The registry is set to use https://mydomain.io/imagetoken for REGISTRY_AUTH_TOKEN_REALM. This endpoint responds to basic auth with a JWT token.
I am able to manually retrieve a token by making a request against my endpoint:
curl -v -d -X POST -u "username:password" "https://authserver.io/v1/imagetoken"
Response:
{"token":"token","access_token":"token"}

I am able to use that token to hit the registry successfully:
curl -H "Authorization: Bearer TOKEN" https://private-registry.io/v2/
Response:
{}
However, when I attempt to use docker login to authenticate with my private registry I run into issues.
docker login -u foo -p bar private-registry.io
Response:
Error response from daemon: Get "https://private-registry.io/v2/": received unexpected HTTP status: 501 Not Implemented
And I see this in the logs of the private registry:
REDACTED - - [12/Apr/2024:20:46:07 +0000] "GET /v2/ HTTP/1.1" 200 2 "" "curl/8.4.0"
REDACTED - - [12/Apr/2024:20:46:13 +0000] "GET / HTTP/1.1" 200 0 "" "curl/8.4.0"
REDACTED - - [12/Apr/2024:20:50:52 +0000] "GET /v2/ HTTP/1.1" 401 87 "" "docker/24.0.9 go/go1.20.13 git-commit/fca702d kernel/6.5.0-15-generic os/linux arch/arm64 UpstreamClient(Docker-Client/26.0.1 \\(darwin\\))"
time="2024-04-12T20:50:52.094748733Z" level=debug msg="authorizing request" go.version=go1.20.8 http.request.host=private-registry.io http.request.id=REDACTED http.request.method=GET http.request.remoteaddr=REDACTED http.request.uri="/v2/" http.request.useragent="docker/24.0.9 go/go1.20.13 git-commit/fca702d kernel/6.5.0-15-generic os/linux arch/arm64 UpstreamClient(Docker-Client/26.0.1 \(darwin\))"
time="2024-04-12T20:50:52.094832267Z" level=warning msg="error authorizing context: authorization token required" go.version=go1.20.8 http.request.host=private-registry.io http.request.id=REDACTED http.request.method=GET http.request.remoteaddr=REDACTED http.request.uri="/v2/" http.request.useragent="docker/24.0.9 go/go1.20.13 git-commit/fca702d kernel/6.5.0-15-generic os/linux arch/arm64 UpstreamClient(Docker-Client/26.0.1 \(darwin\))"

Reproduce

Create server that takes basic auth and returns valid JWT
Start registry version registry:2.8.3
Attempt to curl the registry using JWT from auth server
Try to docker login to the registry

Expected behavior
The registry should log in successfully if it is just passing the basic auth credentials to the token server
registry version
registry:2.8.3
Additional Info
No response

This is a question for https://github.com/moby/moby project I believe. CC: @thaJeztah
My general suspicion is: docker daemon does not seem to be able to handle calls to private registry. I am going to assume that your private registry is served over trusted TLS cert otherwise you'd need to explicitly tell docker daemon it is untrusted i.e. insecure in docker daemon.json settings. If you dont, the daemon will barf. The config goes something like this IIRC -- please check the official docs.
{
  "insecure-registries" : ["<my-registry-ip>:5000"]
}

If the registry does serve the API using a trusted TLS cert then yeah, please ask in moby/moby.
Finally, I'd strongly encourage you to stop using v2.8.x version. It's missing a lot of patches, bug fixes and performance improvements.


SimpleSCPIGetEntity crashes when "base_str" is wrong

For a SCPI device that accepts READ? for readout, if I put READ? in the base_str (which is wrong; should be READ), Dripline crashes instead of printing an error message:
Emss-Cath-Egun_1   | Formatting socket_info: ("<IP_ADDRESS>",10001)
Emss-Cath-Egun_1   | Ethernet socket ('<IP_ADDRESS>', 10001) established
Emss-Cath-Egun_1   | sending: b'*RST\nRANG:AUTO ON\nSYST:ZCH OFF\nFORM:ELEM READ\n*IDN?\r'
Emss-Cath-Egun_1   | 'KEITHLEY INSTRUMENTS INC.,MODEL 6485,4572064,C01   Jun 23 2010 12:22:00/B01  /J\r'
Emss-Cath-Egun_1   | sync: '*RST\nRANG:AUTO ON\nSYST:ZCH OFF\nFORM:ELEM READ\n*IDN?\r' -> 'KEITHLEY INSTRUMENTS INC.,MODEL 6485,4572064,C01   Jun 23 2010 12:22:00/B01  /J'
Emss-Cath-Egun_1   | service built
Emss-Cath-Egun_1   | creating object from:
Emss-Cath-Egun_1   | {'name': 'nA_Emss_Cath_Egun', 'log_on_set': True, 'base_str': 'READ?', 'module': 'SimpleSCPIGetEntity', 'log_interval': 10, 'get_on_set': True}
Emss-Cath-Egun_1   | ...
Emss-Cath-Egun_1   | queue up start logging for 'nA_Emss_Cath_Egun'
Emss-Cath-Egun_1   | should start logging every 0:00:10
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) ary/scheduler.hh(228): Scheduling a repeating event
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) ary/scheduler.hh(250): New first event
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) ary/scheduler.hh(259): That event was first; waking execution thread
Emss-Cath-Egun_1   | log action id is 0
Emss-Cath-Egun_1   | about to start the service
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [ INFO] (tid<PHONE_NUMBER>46560) brary/service.cc(141): Connecting to <rabbit-broker:5672>
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) brary/service.cc(269): Opening channel for service <Emss_Cath_Egun>
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) /library/core.cc(287): Opening AMQP connection and creating channel to rabbit-broker:5672
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) /library/core.cc(288): Using broker authentication: dripline:dripline
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(310): Executing first event from the map
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(56): executing
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(232): wrapped execution
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(228): Scheduling a repeating event
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(236): executing the wrapped executable
Emss-Cath-Egun_1   | 2023-09-29 20:44:43 [ERROR] (tid<PHONE_NUMBER>28384) ity/terminate.cc(53): Caught unhandled exception. what(): Exception: name 'ThrowReply' is not defined
Emss-Cath-Egun_1   |
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) brary/service.cc(306): Binding keys for synchronous children
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) /library/core.cc(373): Binding key <nA_Emss_Cath_Egun.#> to queue <Emss_Cath_Egun> over exchange <requests>
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) brary/service.cc(314): Binding keys for asynchronous children
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>46560) /library/core.cc(399): Starting to consume messages on queue <Emss_Cath_Egun>
Emss-Cath-Egun_1   | services started, now to listen
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(292): Starting scheduler
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [ INFO] (tid<PHONE_NUMBER>46560) brary/service.cc(370): Listening for incoming messages on <Emss_Cath_Egun>
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [ INFO] (tid<PHONE_NUMBER>21088) y/heartbeater.cc(68): Starting heartbeat loop
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(310): Executing first event from the map
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(56): executing
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(232): wrapped execution
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(228): Scheduling a repeating event
Emss-Cath-Egun_1   | 2023-09-29 20:44:23 [DEBUG] (tid<PHONE_NUMBER>28384) ary/scheduler.hh(236): executing the wrapped executable
Emss-Cath-Egun_1   | 2023-09-29 20:44:43 [ERROR] (tid<PHONE_NUMBER>28384) ity/terminate.cc(53): Caught unhandled exception. what(): Exception: name 'ThrowReply' is not defined
Emss-Cath-Egun_1   |
Emss-Cath-Egun_1   | At:
Emss-Cath-Egun_1   |   /usr/local/lib/python3.5/site-packages/dripline/implementations/ethernet_scpi_service.py(153): send_to_device
Emss-Cath-Egun_1   |   /usr/local/lib/python3.5/site-packages/dripline/implementations/entity_endpoints.py(48): on_get
Emss-Cath-Egun_1   |   /usr/local/lib/python3.5/site-packages/dripline/core/calibrate.py(26): wrapper
Emss-Cath-Egun_1   |   /usr/local/lib/python3.5/site-packages/dripline/core/entity.py(135): scheduled_log
Emss-Cath-Egun_1   |
Emss-Cath-Egun_1   | 2023-09-29 20:44:43 [ERROR] (tid<PHONE_NUMBER>28384) ity/terminate.cc(64): Backtrace from terminate() returned 22 frames
Emss-Cath-Egun_1   |
Emss-Cath-Egun_1   | 2023-09-29 20:44:43 [ERROR] (tid<PHONE_NUMBER>28384) ity/terminate.cc(73): Backtrace:
Emss-Cath-Egun_1   | [bt]: (0) /usr/local/lib/libScarab_Dripline_DriplinePy.so(_ZN6scarab9terminateEv+0x50) [0x7fca6c04a99d]
Emss-Cath-Egun_1   | [bt]: (1) /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x928c6) [0x7fca6bce28c6]
Emss-Cath-Egun_1   | [bt]: (2) /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92901) [0x7fca6bce2901]
Emss-Cath-Egun_1   | [bt]: (3) /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92b34) [0x7fca6bce2b34]
Emss-Cath-Egun_1   | [bt]: (4) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(+0xad101) [0x7fca6baf9101]
Emss-Cath-Egun_1   | [bt]: (5) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(+0x9bc19) [0x7fca6bae7c19]
Emss-Cath-Egun_1   | [bt]: (6) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(+0x134c82) [0x7fca6bb80c82]
Emss-Cath-Egun_1   | [bt]: (7) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(+0x14a308) [0x7fca6bb96308]
Emss-Cath-Egun_1   | [bt]: (8) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(_ZNKSt8functionIFvvEEclEv+0x32) [0x7fca6bae9c86]
Emss-Cath-Egun_1   | [bt]: (9) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(+0xc36a5) [0x7fca6bb0f6a5]
Emss-Cath-Egun_1   | [bt]: (10) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(+0x108a7d) [0x7fca6bb54a7d]
Emss-Cath-Egun_1   | [bt]: (11) /usr/local/lib/python3.5/site-packages/_dripline.cpython-35m-x86_64-linux-gnu.so(_ZNKSt8functionIFvvEEclEv+0x32) [0x7fca6bae9c86]
Emss-Cath-Egun_1   | [bt]: (12) /usr/local/lib/libDripline_DriplinePy.so(_ZN8dripline15simple_executorclESt8functionIFvvEE+0xf1) [0x7fca6b97f029]
Emss-Cath-Egun_1   | [bt]: (13) /usr/local/lib/libDripline_DriplinePy.so(_ZN8dripline9schedulerINS_15simple_executorENSt6chrono3_V212system_clockEE7executeEv+0x33b) [0x7fca6b9800f7]
Emss-Cath-Egun_1   | [bt]: (14) /usr/local/lib/libDripline_DriplinePy.so(_ZSt13__invoke_implIvMN8dripline9schedulerINS0_15simple_executorENSt6chrono3_V212system_clockEEEFvvEPNS0_7serviceEJEET_St21__invoke_memfun_derefOT0_OT1_DpOT2_+0x74) [0x7fca6b981d66]
Emss-Cath-Egun_1   | [bt]: (15) /usr/local/lib/libDripline_DriplinePy.so(_ZSt8__invokeIMN8dripline9schedulerINS0_15simple_executorENSt6chrono3_V212system_clockEEEFvvEJPNS0_7serviceEEENSt15__invoke_resultIT_JDpT0_EE4typeEOSC_DpOSD_+0x37) [0x7fca6b9803e3]
Emss-Cath-Egun_1   | [bt]: (16) /usr/local/lib/libDripline_DriplinePy.so(_ZNSt6thread8_InvokerISt5tupleIJMN8dripline9schedulerINS2_15simple_executorENSt6chrono3_V212system_clockEEEFvvEPNS2_7serviceEEEE9_M_invokeIJLm0ELm1EEEEDTcl8__invokespcl10_S_declvalIXT_EEEEESt12_Index_tupleIJXspT_EEE+0x43) [0x7fca6b985517]
Emss-Cath-Egun_1   | [bt]: (17) /usr/local/lib/libDripline_DriplinePy.so(_ZNSt6thread8_InvokerISt5tupleIJMN8dripline9schedulerINS2_15simple_executorENSt6chrono3_V212system_clockEEEFvvEPNS2_7serviceEEEEclEv+0x18) [0x7fca6b9853b8]
Emss-Cath-Egun_1   | [bt]: (18) /usr/local/lib/libDripline_DriplinePy.so(_ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJMN8dripline9schedulerINS3_15simple_executorENSt6chrono3_V212system_clockEEEFvvEPNS3_7serviceEEEEEE6_M_runEv+0x1c) [0x7fca6b9852ee]
Emss-Cath-Egun_1   | [bt]: (19) /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xbbb2f) [0x7fca6bd0bb2f]
Emss-Cath-Egun_1   | [bt]: (20) /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7fca6d036fa3]
Emss-Cath-Egun_1   | [bt]: (21) /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fca6cdda4cf]

@SanshiroEnomoto do you have a suggested solution?

This could also get caught up in better error handling that Christine mentioned on today's call - so it may be part of a broader problem/solution

As Walter said, I think this is an issue related to error reporting. Crashing is fine, as keeping going would not produce useful data anyway (stopping would be better, though), but it was very difficult for me (who is not familiar with the code set) to figure out the reason. The worst thing is the message of Caught unhandled exception. what(): Exception: name 'ThrowReply' is not defined, which I consider is a bug and needs to be fixed.

I believe the unhandled exception in this issue will be fixed by one of the deficiencies listed in https://github.com/driplineorg/dripline-cpp/issues/103.
I've also made a dedicated issue for exception handling in dl-py itself: #166.  I have not yet looked through the code in Implementations to consider its exceptions use.


Add specific application/x-binary mime type for bin extension files to mime type mapping

Enhancement: Add specific mime type for bin files
We've added the specific mime type 'application/x-binary' for bin files to the list of mime types.

I think the problem is here https://github.com/owncloud/ocis/blob/4d5168f6c3ab182db596c996e8b9090f4dedc55e/services/collaboration/pkg/helpers/registration.go#L41
	mimeTypesMap := make(map[string]bool)
	for _, extensions := range appUrls {
		for ext := range extensions {
			m := mime.Detect(false, ext)
			mimeTypesMap[m] = true
		}
	}

The mime.Detect returns the "application/octet-stream" as default. So, we could skip there the "application/octet-stream" mime type.

And then the files have no mime type anymore? I think the default is there on purpose.
I am wondering why OnlyOffice and Collabora are set to be able to be able to open especially the application/ocet-stream mime type.
Shouldn't we just avoid that ?

Fixed in a ocis


Data Domain Boost and SQL Backup Compression

Should SQL Backup compression be enabled or not when using Dell EMC Data Domain Boost? Thanks!
https://blog.dellemc.com/en-us/sql-server-maintenance-solution-supports-dell-emc-data-protection/

The backup will always be compressed in Data Domain Boost, when you specify @BackupSoftware = 'DATA_DOMAIN_BOOST'.
The @Compress parameter is not used with Data Domain Boost, so you don't need to specify it.


Run dnsd inside a container

Is there a way to run this service inside a container?
I tried the first example (the one that returns <IP_ADDRESS> always) with a Dockerfile that exposes port 6464 and then built it and ran it with the command:
> docker run --name dns -d --restart=always --publish 53:6464/tcp --publish 53:6464/udp --volume :/code dns
When I run dig:
> dig @localhost -p 53 foo.example A
I get:
;; connection timed out; no servers could be reached.
I am running MacOSX and I am trying to setup a local DNS server that I can then add into the /etc/resolv.conf as a nameserver.
Thank you

Hi! That is a great question.
Perhaps use docker exec to get into a shell inside your container, then
run dig from inside there?
If it works, then it is an issue with networking, connecting from your host
into the Docker service. If it does not work, then the problem is with
actually running dnsd correctly in that container.
(Also, if your needs are modest, dnsmasq may be a plan B as well.)
On Tue, Aug 14, 2018 at 1:53 PM Kostas Bariotis<EMAIL_ADDRESS>wrote:

Is there a way to run this service inside a container?
I tried the first example (the one that returns <IP_ADDRESS> always) with a
Dockerfile that exposes port 6464 and then built it and ran it with the
command:

docker run --name dns -d --restart=always --publish 53:6464/tcp
--publish 53:6464/udp --volume :/code dns

When I run dig:

dig @localhost -p 53 foo.example A

I get:
;; connection timed out; no servers could be reached.
I am running MacOSX and I am trying to setup a local DNS server that I can
then add into the /etc/resolv.conf as a nameserver.
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iriscouch/dnsd/issues/22, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABEp_vSEKXj7EAB88XW2rq55axZzVvYks5uQw6HgaJpZM4V85Dr
.

Actually running it directly from my laptop (not inside a container) works fine. Haven't tried to log into the container, will do though.
I am experimenting to find a way to access containers (different ports on localhost) using domain names. I want to setup my MacOS to use the localhost as a nameserver that will then redirect requests to a local reverse proxy.

Also, something I have seen is that MacOS is able to use a custom DNS server for a specific domain
So rather than have a server "proxy" your queries, you could possibly just run dnsd but tell MacOS to query it only for a specific domain.


Notify BatchStartAware event handlers of batch size before processing…

… a batch in BatchEventProcessor
Motivation:
The event handler may wish to change its behaviour if the batch size is large.
For example: Imagine a situation where:

the events being sent are coalesceable in some way
the processing of each event is potentially expensive.

If the event handler knows, before a batch is processed, that the batch is large (and therefore the opportunity to coalesce is high) it can switch to a coalescing mode prior to batch processing, coalesce whatever events in the batch and then perform the necessary processing on a much smaller set of events at batch end. This should save cpu time and hopefully help make future batches smaller.
Another example: Monitoring - a large batch is a potentially useful performance metric. At the moment, we can detect large batches by being mildly clever and detecting batch end; it'd be nice to know the metric at the start of the batch, though.
Notes:
This doesn't have to go in disruptor, but it would be handy to not have to reproduce the entirety of BatchEventProcessor in order to do it.
I haven't written any tests (even with BEP's interface I think we should be able to write at least one...) - I wanted to get an opinion on whether this is going to fly or not first :-)

Looks good, can we have a unit test for the new feature too.

Well, that's made a right mess.

Ok - rebased from master, fixed some issues, made a hash of writing the test (fell into the 'stopping event processor before it started' hole), wrote test again, 'push -f'ed.
Result: everything's in that last commit, ignore the others.


example/all

Added JavaScript test cases
Added no-unsafe-negation tests
Added valid-typeof tests
Fixed prettified tests
Removed random tests
Disabled irrelevant lint rules
Added tests for arrow-body-style & capitalized-comments
Added 4 fix tests
Added 4 tests
Added all remaining suggestion tests
Added no-extra-semi test
Added more fix tests
Separating tests of different configs
Separating tests of different configs
Added more tests for fixes
Added more tests for fixes
Added more tests for fixes
Added more tests for fixes
Added tests for prefer-destructuring
Added more tests for fixes
Removed .DS_Store
Added layout fix tests
Added more layout fix tests
Added more layout fix tests
Added more layout fix tests
Bump typescript from 4.6.3 to 4.6.4 (#81)
Bump @types/node from 17.0.31 to 17.0.33 (#105)
yarn upgrade (#107)
Fixed prettified tests
Bump typescript from 4.6.3 to 4.6.4 (#81)
Bump @types/node from 17.0.31 to 17.0.33 (#105)
yarn upgrade (#107)

Current dependencies on/for this PR:

main

PR #110   👈

This comment was auto-generated by Graphite.


For Wizard control , navigation list missing when put  tag in a sub component

Select one ...  (check one with "x")
[x ] bug
[ ] feature request
[ ] enhancement

Expected behavior
we have a wizard component which need to add wizard step programmatically, so we put wizard step into a component, e.g. named: app-page1, we add the component tag into the clr-wizard tag:
<clr-wizard #wizardmd [(clrWizardOpen)]="mdOpen" clrWizardSize="lg">
                  <clr-wizard-title>Medium-Sized Wizard</clr-wizard-title>
                  <clr-wizard-button [type]="'previous'">Back</clr-wizard-button>
                  <clr-wizard-button [type]="'next'">Next</clr-wizard-button>
                  <app-page1></app-page1>
 </clr-wizard>

we expected the wizard can render the page defined in the sub component.
Actual behavior
the first page content and title are displayed, but the navigation items are empty, and we cannot navigate to next page by click next button also
Reproduction of behavior
Environment details

**Angular version: 5.2.0

**Clarity version: 0.11.3

**OS and version: Windows 10

Browser: [all]

The wizard expects to have a clr-wizard-page element to project the content, otherwise it doesn't work. Without the page element, the internal selection of what should be displayed is unclear, so put your component inside of the page like so.
https://stackblitz.com/edit/clarity-light-theme-v11-6vy6dm?file=app%2Fapp.component.html
			<button class="btn" (click)="wizardOpen = true">Open</button>
			<clr-wizard #wizardmd [(clrWizardOpen)]="wizardOpen" clrWizardSize="lg">
				<clr-wizard-title>Medium-Sized Wizard</clr-wizard-title>
				<clr-wizard-button [type]="'previous'">Back</clr-wizard-button>
				<clr-wizard-button [type]="'next'">Next</clr-wizard-button>
				<clr-wizard-page>
					<ng-template clrPageTitle>Page 1</ng-template>
					<app-page1></app-page1>
				</clr-wizard-page>
			</clr-wizard>

I don't believe this is a bug but an implementation question so I'm going ahead and closing it. Feel free to repoen it if there are additional issues, or post to StackOverflow for help.


"Docroot Location" should pick up normal directory roots

What happened (or feature request):
Feature request
What you expected to happen:
When I configured a composer based Drupal project, I figured it would pick up web or docroot when "Docroot Location"  was asked.
How to reproduce this:
Run ddev config
Related source links or issues:
Example of what I did in my tool platform-docker
                // Platform.sh scaffold docroot.
                if (is_dir($this->cwd . '/' . Platform::DEFAULT_WEB_ROOT)) {
                  Config::set('docroot', Platform::DEFAULT_WEB_ROOT);
                }
                // Typical app location.
                elseif (is_dir($this->cwd . '/web')) {
                    Config::set('docroot', 'web');
                }
                // Acquia.
                elseif (is_dir($this->cwd . '/docroot')) {
                    Config::set('docroot', 'docroot');
                }
                else {
                  $question = new Question("<info>What is the document root for the project?");
                  $answer = $helper->ask($input, $output, $question);
                  Config::set('docroot', $answer);
                }

source: https://github.com/mglaman/platform-docker/blob/develop/src/Command/InitCommand.php#L48
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)
1

I think this is totally reasonable. I'd think

probe those in order of most likely, looking for an index.php in them.
Prompt with the discovered docroot as default rather than just going with it.

I actually can't tell you how many times I've had to ctrl-c in the middle of a config operation or use another window to go find what the docroot is.

Flagging in the milestone to provide better CMS UX. There is a little bit of a challenge in that this may be CMS specific because some codebases (notably TYPO3) can sometimes have two index.php files and we need to have more than just a file/directory check to accurately detect with a 99+% hit rate.

So, I know this is in Go. But are option selects possible, like in Symfony Console?
" We detected these docroots, please select correct one", because don't some even use index_dev.php? So if someone want to point to dev or something crazy.

Okay, giving this a whirl. Looks like all the work needs to be done in pkg/ddevapp/config.go:358 at func (app *DdevApp) docrootPrompt() error {

I believe this is a duplicate of #663, which has a PR in the final review stages. Going to close this out, but feel free to re-open if it's separate functionality.

@rickmanelius this is #663, and the PR is #678


What is the license of the polly scene assets?

For both the exported glTF files (https://github.com/KhronosGroup/glTF-Blender-Exporter/tree/master/polly) and the original blender files (https://github.com/KhronosGroup/glTF-Blender-Exporter/tree/master/scenes)

@UX3D-nopper when skinning issues are resolved and we're able to export the Polly model again, would you be OK with moving the model over to glTF-Blender-IO (or perhaps just the samples repo?) and adding a Creative Commons Attribution 4.0 International License or Creative Commons 1.0 Universal Public Domain Dedication?

The polly project is included in the old glTF exporter and was part of the delivery. So at this point of time, it is Apache 2.0. Propably not suitable for an asset, so we can change it.

Thanks @UX3D-nopper

Could it be possible to transfer the Polly model to glTF-Sample-Models ?

https://github.com/KhronosGroup/glTF-Blender-IO/issues/371#issuecomment-781263165

@vpenades This is a good idea. Could you open an issue on glTF-Sample-Models? My understanding is that the .blend will need some changes, to use the Principled BSDF material rather than the old custom nodes. In the past there were some problems supporting it, but it looks like re-importing the original .glb and then exporting from Blender works correctly, so maybe all of those issues have been fixed...


use non-private attributes for service name and endpoint URL

What does this pull request do?
Avoid accessing private attributes to be a little safer from API changes
Also, introduce a way for boto3 < 1.7 to get a conformant service name.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #1079 opened

Start Time: 2021-03-24T12:50:07.205+0000

Duration: 21 min 19 sec

Commit: 34c10e33a52ee9ac5f5670fc68734b4e46dfe2d9

Test stats :test_tube:

Test
Results

Failed
0

Passed
9718

Skipped
7614

Total
17332

Trends :test_tube:

:green_heart: Flaky test report
Tests succeeded.

Expand to view the summary

Test stats :test_tube:

Test
Results

Failed
0

Passed
9718

Skipped
7614

Total
17332


Style guide

Style guide for Tezos docs based on things I've observed. Very open to suggestions here.
This guide does not take a stance on US English vs. British English. en_US is more popular but en_GB would be fine because TriliTech is a British-based company.
Preview: https://docs-staging-git-style-guide-trili-tech.vercel.app/reference/style-guide

We could enrich this guide with pragmatic rules, such as: in the beginning of each tutorial, clearly mention what versions are used for each tool involved. This ensures more robustness in time.

We could enrich this guide with pragmatic rules, such as: in the beginning of each tutorial, clearly mention what versions are used for each tool involved. This ensures more robustness in time. Or maybe this is not a style issue?

Yes, that could be  good follow-up: standards for tutorials, diagrams, code samples, descriptions of tools and programs, and page structure.


Fix a false positive for RSpec/RepeatedExampleGroupBody when pending or skip have argument(s).

RSpec/RepeatedExampleGroupBody does not register offenses when example group body is skip or pending.
describe 'alpha' do
  skip
end

describe 'bravo' do
  skip
end

But each of them has a same argument, registers offenses.
describe 'alpha' do
^^^^^^^^^^^^^^^^^^^ Repeated describe block body
  skip 'something needed'
end

describe 'bravo' do
^^^^^^^^^^^^^^^^^^^ Repeated describe block body
  skip 'something needed'
end

I thinks this is a false positive.
This PR allows this.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[ ] Updated documentation.
[x] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

If you have created a new cop:

[ ] Added the new cop to config/default.yml.
[ ] The cop is configured as Enabled: pending in config/default.yml.
[ ] The cop documents examples of good and bad code.
[ ] The tests assert both that bad code is reported and that good code is not reported.
[ ] Set VersionAdded in default/config.yml to the next minor version.

If you have modified an existing cop's configuration options:

[ ] Set VersionChanged in config/default.yml to the next major version.

@pirj Are you happy with this PR as it is? (We can resolve the Changelog conflict on merge).


Could not initialize SDL joystick subsystem (Gamepads not supported) on firefox

My game does not use any joystick-related functionality, it only uses love.keypressed and love.keyreleased. When building (using the -c flag) and running in firefox, I get the following error in a popup window:
An error occurred before the game window could be initialised. Please check the console!
When checking the console, I see the following message
Could not initialize SDL joystick subsystem (Gamepads not supported)
The game runs fine in chrome with the -c flag, no issues. This only seems to happen on firefox.
Is there a special way I need to handle input to resolve this? I've checked my project and I don't have any gamepad support enabled, I only use basic keyboard functions from love2D. Is there a way around this? I'm using firefox version 91.0.
EDIT: On second look, it seems to work fine on itch.io with the web version, despite throwing the above error when running it through a local webserver. Perhaps it has something to do with my local server? I'm using npx http-server to run the game locally in a browser, but when I run it through itch.io, it seems to work fine.

I ran into this issue too:  Ubuntu 20.04, Firefox 91.0.  My game also works on Itch.io.

This is likely due to browsers limiting certain APIs to be available on HTTPS origins only.
You can work around this by adding t.modules.joystick = false to your conf.lua


Bot doesn't work

I did everything according to the instructions, but the bot does not work.
He's not online, he's not responding

looking at the screen hosting cuz i use this code to run my bot too and it work


Logs from Sonoff B1 and Sonoff SC (Plz add)

Sonoff B1 logs

19:45:14 MQT: Attempting connection...
19:45:14 MQT: Connected
19:45:14 MQT: SHOME/sonoff/LED1/LWT = Online (retained)
19:45:14 MQT: SHOME/sonoff/LED1/cmnd/POWER =
19:45:14 MQT: SHOME/sonoff/LED1/INFO1 = {"Module":"Sonoff B1","Version":"5.9.1f","FallbackTopic":"LED1","GroupTopic":"sonoffs"}
19:45:14 MQT: SHOME/sonoff/LED1/INFO2 = {"WebServerMode":"Admin","Hostname":"LED1","IPAddress":"<IP_ADDRESS>"}
19:45:14 MQT: SHOME/sonoff/LED1/INFO3 = {"RestartReason":"Power on"}
19:45:15 MQT: SHOME/sonoff/LED1/RESULT = {"POWER":"ON"}
19:45:15 MQT: SHOME/sonoff/LED1/POWER = ON
19:45:22 MQT: SHOME/sonoff/LED1/STATE = {"Time":"2018-01-19T19:45:22","Uptime":0,"Vcc":3.289,"POWER":"ON","Wifi":{"AP":1,"SSId":"SmartHOME","RSSI":96,"APMac":"60:31:97:3E:74:B4"}}
19:50:22 MQT: SHOME/sonoff/LED1/STATE = {"Time":"2018-01-19T19:50:22","Uptime":0,"Vcc":3.280,"POWER":"ON","Wifi":{"AP":1,"SSId":"SmartHOME","RSSI":82,"APMac":"60:31:97:3E:74:B4"}}
19:55:07 APP: Serial logging disabled
19:55:22 MQT: SHOME/sonoff/LED1/STATE = {"Time":"2018-01-19T19:55:22","Uptime":0,"Vcc":3.280,"POWER":"ON","Wifi":{"AP":1,"SSId":"SmartHOME","RSSI":86,"APMac":"60:31:97:3E:74:B4"}}
20:00:22 MQT: SHOME/sonoff/LED1/STATE = {"Time":"2018-01-19T20:00:22","Uptime":0,"Vcc":3.279,"POWER":"ON","Wifi":{"AP":1,"SSId":"SmartHOME","RSSI":88,"APMac":"60:31:97:3E:74:B4"}}
20:02:00 MQT: SHOME/sonoff/LED1/UPTIME = {"Time":"2018-01-19T20:02:00","Uptime":1}
20:02:50 CMD: color 12
20:02:50 MQT: SHOME/sonoff/LED1/RESULT = {"POWER":"ON","Dimmer":100,"Color":"FFFFFF0000"}
20:02:58 CMD: Dimmer
20:02:58 MQT: SHOME/sonoff/LED1/RESULT = {"Dimmer":100}
20:07:18 CMD: CT
20:07:18 MQT: SHOME/sonoff/LED1/RESULT = {"CT":499}

Command options Color
Command | Payload | Description
Color | 1 | Set color to Red
Color | 2 | Set color to Green
Color | 3 | Set color to Blue
Color | 4 | Set color to Orange
Color | 5 | Set color to Light Green
Color | 6 | Set color to Light Blue
Color | 7 | Set color to Amber
Color | 8 | Set color to Cyan
Color | 9 | Set color to Purple
Color | 10 | Set color to Yellow
Color | 11 | Set color to Pink
Color | 12 | Set color to White
Command options CT
CT |   | (Sonoff B1 and Led) Show current Color Temperature (153 = Cold, 500 = Warm)
CT | 153..500 | (Sonoff B1 and Led) Set color temperature from cold to warm
CT | + | Increment CT in 10 steps
CT | - | Decrement CT in 10 steps
Command options Dimmer
Dimmer |   | Show current dimmer setting from 0 to 100%
Dimmer | 0..100 | Set dimmer value from 0 to 100%
Dimmer | + | Increment brightness in 10 steps
Dimmer | - | Decrement brightness in 10 steps
Command options Scheme
Scheme |   | Show current selected scheme
Scheme | 0 | (default) Use a single color for all pixels in light/strip/ring
Scheme | 1 | (= Wakeup) Start wake up sequence
Scheme | 2 | Cycle through RGB colors using speed option
Scheme | 3 | Cycle through RBG colors using speed option
Scheme | 4 | Random cycle through colors using speed and fade options
Sonoff SC logs

20:15:08 MQT: SHOME/sonoff/HomeMonitor/INFO1 = {"Module":"Sonoff SC","Version":"5.9.1f","FallbackTopic":"HomeMonitor","GroupTopic":"sonoffs"}
20:15:08 MQT: SHOME/sonoff/HomeMonitor/INFO2 = {"WebServerMode":"Admin","Hostname":"HomeMonitor","IPAddress":"<IP_ADDRESS>"}
20:15:08 MQT: SHOME/sonoff/HomeMonitor/INFO3 = {"RestartReason":"Power on"}
20:15:16 MQT: SHOME/sonoff/HomeMonitor/STATE = {"Time":"2018-01-19T20:15:16","Uptime":0,"Vcc":3.170,"Wifi":{"AP":1,"SSId":"SmartHOME","RSSI":100,"APMac":"60:31:97:3E:74:B4"}}
20:15:16 MQT: SHOME/sonoff/HomeMonitor/SENSOR = {"Time":"2018-01-19T20:15:16","Temperature":20.0,"Humidity":16.0,"Light":10,"Noise":60,"AirQuality":90,"TempUnit":"C"}

Command options
Altitude |   | Show current Altitude to be used by calculating Sea level Pressure
Altitude | -30000..30000 | Set local Altitude in meters
AmpRes |   | Show current Current Resolution
AmpRes | 0..3 | Set Current Resolution
Counter |   | Show current Counter 1..4 value
Counter | 0 | Reset Counter 1..4
Counter | 1..64900 | Preset Counter 1..4
CounterDebounce |   | Show current global Counter debounce time in mSec
CounterDebounce | 0 / off | Turn global Counter debounce off
CounterDebounce | 1..3200 | Set global Counter debounce in mSec
CounterType |   | Show current Counter 1..4 type as pulse Counter or pulse Timer
CounterType | 0 / off | Set current Counter 1..4 type as pulse Counter
CounterType | 1 / on | Set current Counter 1..4 type as pulse Timer
EnergyRes |   | Show current Energy Resolution
EnergyRes | 0..5 | Set Energy Resolution
HumRes |   | Show current Humidity Resolution
HumRes | 0..3 | Set Humidity Resolution
Ina219Mode |   | Show current Ina219 Calibration Mode
Ina219Mode | 0 | Set Ina219 Calibration to max 32V and 2A
Ina219Mode | 1 | Set Ina219 Calibration to max 32V and 1A
Ina219Mode | 2 | Set Ina219 Calibration to max 16V and 0.4A
PressRes |   | Show current Pressure Resolution
PressRes | 0..3 | Set Pressure Resolution
SetOption8 |   | Show current Temperature as either Celsius or Fahrenheit
SetOption8 | 0 / celsius | Set Temperature to Celsius
SetOption8 | 1 / fahrenheit | Set Temperature to Fahrenheit
SetOption18 |   | Show Signal Light state - currently used with CO2 sensors only
SetOption18 | 0 / off | (default) Disable signal light
SetOption18 | 1 / on | Enable signal light
TempRes |   | Show current Temperature Resolution
TempRes | 0..3 | Set Temperature Resolution
TempUnit |   | Replaced by SetOption8
VoltRes |   | Show current Voltage Resolution
VoltRes | 0..3 | Set Voltage Resolution
WattRes |   | Show current Power Resolution
WattRes | 0..3 | Set Power Resolution
Link to tasmota wiki commands: https://github.com/arendst/Sonoff-Tasmota/wiki/Commands#ws2812-ailight-sonoff-led-b1-bn-sz01-h801-and-magichome

Hi, I wanted to clarify enough information to add functionality. Or add something. I can also be a beta test

Das wäre echt der Hammer, wenn man die B1 direkt über den Adapter steuern könnte, freu.


Want to add bottom button to website (such that user can automatically go to the home section without scrolling)

Want to add bottom button to website (such that user can automatically go to the home section without scrolling)
Please assign this issue to me, under @GSSOC2023

Sure @Lobi29
make sure to match with the theme

Hey, @agamjotsingh18 if the issue is not yet resolved then I would like to work on it under GSSoC23. You can assign it to me.


improve start_customized_path output log

System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04):
Apollo installed from (source or binary):
Apollo version (3.5, 5.0, 5.5, 6.0):
Output of apollo.sh config if on master branch:

Steps to reproduce the issue:
start_customized_path output log default to nohup.out, when use script to start module, we often forget to look in nohup.out if we encounter errors.
We'd better move the logs into data/log
Supporting materials (screenshots, command lines, code/script snippets):

fix #14656


[Firmware v.9] Set sensible default values in Firmware to avoid potentially dangerous side effects

I am currently working with the UpsPlus v5.0 PCB 01b Revision with Firmware v.9 flashed to it and it seems that the firmware does not use appropriate default values. The values discussed in this repo (e.g. PROTECT_VOLT = 3700) are only properly configured using various python files. I would expect something like the following as default in the firmware binary so that usage is safe even though the recommended software is not installed and the UPS can be used safely out of the box with e.g. a read-only Linux.
Device: 0x17

Register 0x11 - 0x12 : 3500 mV
Register 0x15 - 0x16 : 2 Minutes

The behavior of the firmware in the actual state is unclear and not (fully) documented so I am not sure what potential effects of the default parameters are. However, I expect that with the default protection voltage the UPS never shuts down and drains the batteries to a potentially dangerous low level?
Can you please offer a firmware with updated defaults? I am happy to provide a PR, given that the source of the firmware is made available.

Frtz13's and my tests show that the UPS will cut off the load at the
empty voltage value even without any control script running. The empty
voltage is learned (adjusted while the batteries are discharged) from
the protection voltage set by the user while the batteries are
discharged (no AC). If there is no control script running, the UPS will
just cut power to the load as soon as the empty voltage is reached.
The control script with its 200 mV margin safeguards the OS from
sustaining damage by shutting down the Pi in good order and well ahead
of the empty voltage being reached. Depending on settings and
circumstances a sudden increase in load current might cause the actual
battery voltage to drop below the empty voltage, which would trigger the
UPS. It's not what you want to happen, so a sensible control script
imposes a 200 mV safety margin ...
I agree that the UPS is not fully documented ...
Op 07-08-2021 om 13:35 schreef Benjamin Buchwitz:

I am currently working with the |UpsPlus v5.0 PCB 01b Revision| with
|Firmware v.9| flashed to it and it seems that the firmware does not
use appropriate default values. The values discussed in this repo
(e.g. |PROTECT_VOLT = 3700|) are only properly configured using
various python files. I would expect something like the following as
default in the firmware binary so that usage is safe even though the
recommended software is not installed and the UPS can be used safely
out of the box with e.g. a read-only Linux.
Device: 0x17

Register 0x11 - 0x12 : 3500 mV
Register 0x15 - 0x16 : 2 Minutes

The behavior of the firmware in the actual state is unclear and not
(fully) documented so I am not sure what potential effects of the
default parameters are. However, I expect that with the default
protection voltage the UPS never shuts down and drains the batteries
to a potentially dangerous low level?
Can you please offer a firmware with updated defaults? I am happy to
provide a PR, given that the source of the firmware is made available.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/geeekpi/upsplus/issues/68, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANCBKNT2FWTODQ7XKZS52PDT3ULAPANCNFSM5BXKOAUA.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

Thanks for providing those insights. The function of the control script is clear but irrelevant for the issue. The protection voltage has default 65535. The defaults for full and empty voltage are also 65535.
When the control script is never executed, the protection voltage stays at 65535, which is unsafe. Properly configured default values would allow safe usage out of the box. Can you adjust the default values in the next FW release @nickfox-taterli ?


Updated test command line parsing to support common commands

Allows running a single test via the command line option -test X (where X is a id)
Other commands supported include:
-help to show usage
-list to display the id:name of tests
-iter X to specify a single iteration to run
It uses apps/opt.c to specify the options for both the common commands (e.g: -help) as well as the test specific options. The options are all set by the test apps (similar to the openssl apps)
If the test setup() returns 0 now the usage is displayed. (options can be specified for a test via a test_get_options() method). The inbuilt commands must be ignored by the test app as they are handled internally.
There is a unit test for app ui, so I have seperated out the UI specific code to avoid conflicts with the test system.
Checklist

[ ] documentation is added or updated
[x] tests are added or updated

Because there are multiple layers of options it could not use the apps/options directly.

Could you explain that with a bit more detail?  Perhaps it is worth changing the tests to be able to make it possible to use the API directly.

The main change that the new code handles are multiple OPTIONS.
To use the apps API directly would require the changes to be merged back into apps, as they are a bit more complex when you have multiple options lists (global options and test specific options). Some of the complexities involved are:

The global shared layer consumes its own options, so the test only sees/processes its own specific options. Any remaining arguments that are not part of either options are then passed to the test. It will get a lot more complex if it needs to process the arguments multiple times and then pull out bits at a time, before then passing it to a layer that processed the options again :)
(2) The help usage needs to be built up from the two layers which is a bit more complex. This would need to be allocated and then copied to combine the usages.
(3) I had some issues with the BIO_print calls in the opt code as it was causing some tests to have multiply defined symbols. i.e- using bio_err causes the tests to pull in basic_output.o. Any tests that then override the functions in this file will cause multiply defined symbols.

There are some opt functions are exactly the same e.g- opt_int() so I could potentially pull them out to a common file in apps.

Look at the OPT_X_ stuff for tips on way to handle common options.

The first thing that comes to mind is that the tests would then rely on the command line parsing to work.

That seems okay to me; equivalent to someone breaking the TEST_ macros.

Look at the OPT_X_ stuff for tips on way to handle common options.
It would work, but it seems a bit broken if you need to specify global options that should be in all tests files.

The default function could just have these global options in it, but I guess I dont really like having to specify them again in any test that needs to have any options at all..  The usage help for the tests could just be tacked onto the end of the usage, but its not ideal..
i.e: (It wouldnt list the extra test parameters on the first line)
test1 -test 1
Valid Options are:
-test
Other tacked on parameters are
privkey
certfile

No, I think it would work fine, and it would match the way the apps do common flags.  I guess you could say it's just a matter of taste, but using the OPT_X macros have consistency on their side. :)

That seems okay to me; equivalent to someone breaking the TEST_ macros.

There are tests for the TEST_ macros in test_test.c which is run very early on.  I don't think there is anything equivalent for the apps command line parsing.

ping - rebased to head

I still think that using the opt_ API the way the apps do is the right way to do things.
If that is inconvenient, create a utility routine that takes an OPTION list and adds the default ones, and a wrapper around opt_next that implements the common ones.

Yes you did.  I was looking at, I'm not sure what.  Sorry.  I withdraw my concern.

FWIW, I think this could be a smaller change if you had this
void test_setup_opt(const OPTIONS *o, const char *helpstring);
int test_opt_next();

The first takes an "additional" set of options for a test, or NULL if there are none.  It creates a new option list of both the baseline and the per-test options.
The second calls opt_next(), handles the common options, and only returns the test-specific values.

Hi Rich,
That solution was thought of originally - I don't think you gain a great deal doing this.
The way it currently works is more in line with how the apps options work (which skip options they dont care about). Combining the options just makes the code more complex for little gain. i.e- you need to call test_setup_opt() instead of setting a one line macro. It would also require an test_opt_rest() in order to deal with the extra non optional parameters.
Note also that the opt_next() is only used by a few tests.

Thanks for the explanation.

ping

This PR is primarily adding the ability to pass command line arguments to the test framework in addition to individual tests.  Without it we can only pass command line arguments to the tests themselves and things were a little ad hoc.
The other significant change is to allow individual tests (or test iterations) to be run individually.
There are a few minor extras.

Sorry, this pr has been hanging around for too long. Now it has conflicts and needs to be rebased.

Rebased to remove conflicts.

I assume current approvals stand, so will merge now.

Merged.
a43ce58f5569a160272c492c680f2e42d38ec769 Updated test command line parsing to support commmon commands


Sample code does not provide same context clues as IDE

Sample code in both api docs and on flutter.dev does not contain the same context clues to identify closing brackets, braces, and parentheses. This can be a bit frustrating when just starting out, especially when trying to debug and compare to a sample snippet.
Illustrated below:
Sample Code from Flutter Cookbook

Code Reproduced in VSCode

Issue moved to flutter/website #2445 via ZenHub


Added --oauth2 flag for Oauth2 authorization code flow

Insert a description of your pull request (PR) here, and check off the boxes below when they are done.

Contributor checklist

[ ] :tada: This PR closes #ISSUE_NUMBER.
[ ] :scroll: I have broken down my PR into the following tasks:

[ ] Task 1
[ ] Task 2

[ ] :robot: I have added tests, or extended existing tests, to cover any new features or bugs fixed in this PR.
[ ] :book: I have considered adding a new entry in CHANGELOG.md, and added it if should be communicated there.

This is great @thezultimate. 🎉👍🥳
One thing I've been thinking about: Should we remove the --oauth command line argument? Instead I have a suggestion we can discuss going along something like this:

Plugins (which are Python classes) can choose to have a @property method def oauth2(self): (or some other descriptive name.
In the jinja2 generated app script, if >=1 plugin instances have that property method defined AND it returns True during app startup, we do what you know do when --oauth2 is provided.

Being a plugin property method, the plugins will also be able to give True / False based on user configuration input in the YAML file (e.g. the plugin deduces that if user has not specified files on disk, it is expected to use external API etc... the logic here will be plugin specific).
We can take a short video session and discuss? I'm also open for contributing myself in the same PR here in order to move it to 🥅 .

I think I have implemented the changes you suggested in the last commit. Would it be possible for you to check? Or someone else if you are not available? Thanks.

This is great @thezultimate. 🎉👍🥳
One thing I've been thinking about: Should we remove the --oauth command line argument? Instead I have a suggestion we can discuss going along something like this:

Plugins (which are Python classes) can choose to have a @property method def oauth2(self): (or some other descriptive name.
In the jinja2 generated app script, if >=1 plugin instances have that property method defined AND it returns True during app startup, we do what you know do when --oauth2 is provided.

Being a plugin property method, the plugins will also be able to give True / False based on user configuration input in the YAML file (e.g. the plugin deduces that if user has not specified files on disk, it is expected to use external API etc... the logic here will be plugin specific).
We can take a short video session and discuss? I'm also open for contributing myself in the same PR here in order to move it to 🥅 .

I think I have implemented the changes you suggested in the last commit. Would it be possible for you to check? Or someone else if you are not available? Thanks.


Add "Prettify GraphQL" button

The goal is to achieve the same behavior from Insomnia which allow to format a GraphQL query using prettier (see).
I moved the prettier deps from devDependencies to dependencies because it's now used within the application. I was forced to import prettier/standalone & prettier/parser-graphql (as it is explained here) otherwise I got that error:

Couldn't resolve parser "graphql". Parsers must be explicitly added to the standalone bundle.

Things I'm not sure:

I used this.editor.setValue() to update the GraphQL query, is there a better way or it's ok?

The button is badly rendered for now (I'm really not sure about all the CSS classes). I tried to put it in the same place as Insomnia (right below the code editor) but I failed. So it is defined above the editor. I think we can find a better place.

In case of error because the GraphQL query is badly formatted, I raise a toast error:

@j0k3r looks good to me, Can you resolve the package-lock conflicts?
I don't think you could hand resolve them, unless there is a better way - you basically sync your fork with the main, and delete package-lock.json and recreate it.

@helloanoop conflicts resolved. Looks like moving prettier doesn't generate change in package-lock.json anymore 🤷♂

Why not use the same prettier to also prettify JSON request body?

@helloanoop any chance to get this merged?

It's already done here: #604

I think the linked PR only handles REST requests and this PR is about formatting GraphQL queries which is not supported yet. I would also appreciate this feature. The added logic in the other PR can also surely be reused.

@j0k3r looks like there are conflicts again

Well, I can handle the rebase.

But looks like some upstream tests are failing..

Merged.
Appreciate the patience on this PR. Thank you @j0k3r !


[BUG]The Comick extension is very slow in Aniyomi

Source information and language
1.4.26
Steps to reproduce
The slowness (takes 20-25 seconds to load) can be observed when you disable all languages apart from English and try to open the source and when you search for manga or when you trying to migrate one .

Go to manga extensions
Select comick
Disable all languages apart from English
Go to manga source and open comick
Or
Migrate a manga
Or
Search for a manga

Expected behavior
When you do any of the above the display of manga should be loaded instantly . It should only take like 1-3 seconds in theory . The above works when I try repeat the same steps in Tachiyomi-priview and Tachij2K .
Actual behavior
In Aniyomi the mangas are not loaded for a good 20-30 seconds . I have confirmed this by only searching through comick by pinning and enabling search only pinned sources.
Aniyomi version
Beta r6150
Android version
Android 13
Other details
This issue is not observed on Tachiyomi or Tachij2k .
Acknowledgements

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

Can anyone also know how comick changes the mangas title when you search for them . Can it be reproduced artificially ? I would like to convert all my non English title mangas to English ones . ( It worked for martial peak and jujutsu kaisen (from peak of martial arts to martial peak and magical fights to jujutsu kaisen). But it didn't work for Yuusha Party o Oida Sareta Kiyou Binbou ( it reverted from The Jack-of-all-trades Kicked Out of the Hero’s Party ~ The Swordsman Who Became a Support Mage Due to Party Circumstances, Becomes All Powerful to Yuusha Party o Oida Sareta Kiyou Binbou)

Closed as this issue has nothing to do with Aniyomi extensions. If the issue still persists, please open a new issue in the repo for the main app.


(select) onOpen and onClose are not executed

I noticed that the onOpen and onClose functions for the select are not executed. The `md-on-open' attribute gets added, but it won't trigger the function.
<md-select ng-model="model[options.key]" md-on-open="options.templateOptions['onOpening']">

I think it should create the following html
<md-select  md-on-open="options.templateOptions['onOpening'](model[options.key], options, this, $event)">

I played around with the options, I noticed that the following will work:
{
    type: 'select',
    key: 'category',
    templateOptions: {
        label: 'Category',
        labelProp: 'name',
        valueProp: 'id',
        options: [],
        onOpening: function ($modelValue, $inputValue, scope) {
            console.log('Load options');
        }
    },
    ngModelAttrs: {
        onOpening: {
            statement: 'md-on-open'
        }
    }
}

So I assume that 'bound' has to be changed to 'statement'. See Codepen: http://codepen.io/BiteCodes/pen/mEOamo

Feel free to create a PR for it! :)


Add support for disabling all staged content at build time

Proposed Changes
Put the k3s manifests and static content inside a build tag so that we can disable them when compiling for rke2
Types of Changes

build tag

Verification

Add no_stage to TAGS in scripts/build
Build k3s
Start k3s on clean system
Note that /var/lib/rancher/k3s/server/manifests and /var/lib/rancher/k3s/server/static are not created

Linked Issues
Related to https://github.com/rancher/rke2/issues/232
Further Comments
This breaks k3s unless the user provides their own copy of all the core manifests (role bindings, coredns, etc), but this is the desired behavior for RKE2 which provides its own content.

So @brandond - this also lays the ground work for addressing https://github.com/rancher/rke2/issues/171, right?
Do you want to handle both 171 and 232 together and in rke2 GA or do you want to just get 171 addressed for GA and do the rest of 232 in a post-ga follow up?


how should we determine the order of validators

there are many ways we can determine the order of the validator set list in voyager. we should decided on the methodology sooner rather than later.

random
pseudo random
random but consistent for each user
?

Here is my take on this. I would display validators in random order, but organize validators in 3 categories. This means that validators would be displayed randomly inside each category. However, validators in category 1 would always show above validators in category 2.

First category: Validators I have bonded stake to.
Second category: Validators with %vote >0 (i.e. currently validating)
Third category: Validator candidates with %vote = 0.

One possible idea would be to factor in the %vote, in inverse relationship. The more stake you have, the higher the chance you'd be displayed lower in your category. This might increase decentralisation.

I would vote against randomness as I assume it will be confusing for the user to look for a validator once and after a refresh of the page / restart of Voyager. I would vote for pseudo randomness.

@gamarin2

First category: Validators I have bonded stake to.

is this accomplished by the new "my stake" section or do you think we should show this list again on the main validators list?

Second category & Third Category

makes a lot of sense to me

One possible idea would be to factor in the %vote, in inverse relationship

i like you're thinking here - but we will be offering filters for users. does this still make sense when with one click a user can sort by whatever they please?
@faboweb

pseudo randomness that stays consistent for each user.

yeah, i think this is a cool idea. so every validator list on voyager will be randomized - but the order will persist for that user and list. what happens when the validator set changes?

is this accomplished by the new "my stake" section or do you think we should show this list again on the main validators list?

I don't see a way to increase your bonds on the "My Stake" section, so yes. And I'm not sure we should have an "Increase Bond" button on the "My Stake" section since it would incentivise concentrating bonds.

i like you're thinking here - but we will be offering filters for users. does this still make sense when with one click a user can sort by whatever they please?

I do. This is just the default when first clicking. After that users can filter however they want. But we'll get a non-negligible amount of users not filtering, and that's why it matter imo.

Should we then even split in validators and candidates? This already concentrates bond on validators.

@gamarin2

I don't see a way to increase your bonds on the "My Stake" section, so yes. And I'm not sure we should have an "Increase Bond" button on the "My Stake" section since it would incentivise concentrating bonds.

good feedback. have you seen this? https://sketch.cloud/s/xKnxA/all/voyager-wireframes/validator-profile
maybe it's not obvious enough - but we're thinking that clicking on a validator will take you to this page where delegation buttons will be.

Should we then even split in validators and candidates? This already concentrates bond on validators.

i think having one list would be fine - but i think we should indicate the difference between validators and candidates in addition to just the % of vote stat.

good feedback. have you seen this? https://sketch.cloud/s/xKnxA/all/voyager-wireframes/validator-profile

No, will check it out.

maybe it's not obvious enough - but we're thinking that clicking on a validator will take you to this page where delegation buttons will be.

True, I had not realized that we moved away from the sliders. That's not trivial. Here is my current thinking:
I think the "My stake" page is fine as is (except for the comments I already made). However, on the Validator List, I think it would be valuable to add checkboxes at the far right of each validator. After you've checked some validators, you could click on a "Delegate" button. Then a popup window shows up, and you're presented with multiple slides. One for each validator you've checked. This process would act as a "Quick delegation mechanism".
Now you also have a way to bond/unbond from the validator page. IMO the best/most user-friendly to do it is to have a slider that is very visible on the validator page (top right would be ideal).
The slider would go from left to right. If I have bonded stake to this validator, the slider would be moved to the right. Dragging the slider to the left would unbond, while dragging to the right would increase my bonds to this validator.
All in all there would be two ways to bond. One quick way to bond to multiple validators from the Validator List. And one way to bond/unbond from a single validator from the validator page.

i think having one list would be fine - but i think we should indicate the difference between validators and candidates in addition to just the % of vote stat.

I second that.

i like your ideas - but they feel like advanced features / workflows. as such, i don't think they are appropriate for our MVP.

Fair enough! It's true that it might be good to "force" the user to see the validator profile before delegating.
Please consider the other ideas too :p


Handle subexpressions, parentheses and binary operators

Doesn't seem to have settled down ready for review yet? When merged I would change it to be Result without the panics but that can wait.

At least fix the clippy/lint issues?

This PR feels a bit ugly - I think we can do better.

I like this as a starting point; having some code that works, and some tests we can expand on, is better than having an idea and no code.
I think I'd have approached the "bit in the middle" (finding precedence of operators) differently, but this approach feels simpler. My idea was to build a tree and parse left to right. If a higher precedence operator appears, we replace the closest rhs with the new node op(lhs, rhs) where lhs is the old rhs...
The advantage of having code in and working, with tests, is that we can explore alternate parsing strategies with some guarantee that they are at least as good as the one they're replacing, through the safety net of the tests.


Different language support

Hi, I don't know if I'm asking this in the right section as I'm new to the Github environment:
Would it be possible to have a variable to change the language of the installers, if applicable, for applications when using PackageFactory? Or something that we could precise the installer's language and pick a different description (fitting the language picked)?
I'm going to use Mozilla Firefox as an example, here's what’s in the "App.json" for Mozilla Firefox:
"Filter": "Get-EvergreenAppFromApi -Name \"MozillaFirefox\" -ErrorAction \"SilentlyContinue\" -WarningAction \"SilentlyContinue\" | Where-Object { $_.Channel -eq \"Current\" -and $_.Architecture -eq \"x64\" -and $_.Type -eq \"msi\" -and $_.Language -eq \"en-GB\" }",
The installer is locked with the "en-GB" language. I would like the possibility to change it.
When I'm using Evergreen manually, I can use:
Get-EvergreenApp -Name "MozillaFirefox" -AppParams @{Language="fr"}
And it will get the French installer.
I could change it manually through the "App.json" but then if I want to update the versioning of all the apps when using "git pull" on my local repo, it'll get replaced by "en-GB" again.
Maybe there's a better way to do it, I'm not familiar enough with "git" to know.
TLDR: I want to download/import applications in Intune with the help of PackageFactory but still being able to control which language is picked for the application, if applicable (also being able to modify the "description" field so my users can read the description with the language I picked) without it being reverted by updating the repo.
If I didn't post this in the right section, could you please direct me where I should?
Thank you very much for reading through this

You could do a couple of things:

Fork the repo, update your copy of the Firefox app.json, and don't pull changes from this repo
Create a new Firefox en-GB app package and create a pull request back to this repo, so that there are two Firefox packages

Hey Aaron!
Thank you very much for replying! I have some questions about your ideas:
If I fork the repo but don't pull changes from the repo, I will not benefit from the updated versioning of the App.json that happens from your Github Workflow (Update Package Manifests)?
If I create a different Firefox package, only 1 of the 2 packages will be updated? Unless your Update Package Manifests go through all the App.json and update only the versions + detection method?


[style]:

What's the style idea?
We need to improve
Add screenshots
Add screenshots
Code of Conduct

[ ] I agree to follow this project's Code of Conduct

Created by accident.


Enhancement Request: Nicer Json output for info command

When I run:
java -jar apkeditor.jar info -i input.apk -t json
It outputs a JSON list of many Dicts. For example:
[
 {
  "package":"com.waze"
 },
 {
  "VersionCode":1021577
 },
 {
  "VersionName":"99<IP_ADDRESS>"
 },
 {
  "AppName":"Waze"
 },
 {
  "AppIcon":"res/drawable-ldpi-v4/launch_icon.png"
 },
 {
  "application-class":"com.waze.WazeApplication"
 },
 {
  "activity-main":"com.waze.FreeMapAppActivity"
 }
]

This isn't the most optimized output for anything automated. Lookups are not easy. It would better to have this output:
[
 {
  "package":"com.waze",
  "VersionCode":1021577,
  "VersionName":"99<IP_ADDRESS>",
  "AppName":"Waze",
  "AppIcon":"res/drawable-ldpi-v4/launch_icon.png",
  "application-class":"com.waze.WazeApplication",
  "activity-main":"com.waze.FreeMapAppActivity",
 }
]

With this output, it will be easy to lookup any key and get a value. Example: result.getString("activity-main");. The current implementation looking through each set of key, value to find the right one.
@REAndroid please let me know your thoughts, thank you for this amazing project!

@SZRabinowitz
Sorry for late reply,
Your points makes much sense, my initial thought while designing info was to provide information specific as per user demand in  any of offered formats, for example you might need only to print package and dex.
This info feature needs a lot modifications including using uniform and widely used names like the one defined under AndroidManifest.
I currently busy at massive rework on ARSCLib, I highly appreciate if you (or someone) do PR.
Thank you!


Switch to using the serde derive feature

The serde docs now recommend using the derive feature over using serde_derive.

Decided against this since there wasn't that much benefit.


fix($templateRequest): cache downloaded templates as strings

Fixes #10630

FWIW I don't think this is the right fix at all =)

@pkozlowski-opensource lets just add a method to $templateCache like getTemplate() or something, which will dig the string out of the response array.

@caitp I'm also not happy about how this code looks like but I think it is less evil than adding new API and duplicating logic from $http. Actually I was really surprised to see that we've got those checks for an array / string inside $http...
I don't feel strongly about this fix at all (I think it is kind of corner case) but I think that it does what most people would expect...

If you don't want to add a new function, then I think we should change the approach taken by $http and store the "full response" cache in a different place somehow.

The storing of the promise while the request is still pending should also be in this "different place" then... But what is this different place? A cache key with a special prefix that can't exist in url's? Sounds kinda hackish...

a different cache object. it would be best to use WeakMaps to map between http's internal cache and the used cache object, but it's not really an option unfortunately.

Soooooo... @caitp / @petebacondarwin / @shahata / whoever - could one of you guys make a call on this one? Funnily enough I had someone few days back who bumped into this one but the use-case was debatable and I agree that people shouldn't be just using $templateCache as a synchronous substitute of the API that is asynchronous by nature ($templateCache).
Personally I don't feel too strong about this one, let's just make some decision.

OK, so I think we should land this since clearly users are doing things this way. It is kind of reasonable to want to access the cached template from inside the then handler of $templateRequest since arguably at that point it should be there.
For the record, the $templateCache is not designed to be accessed directly. You should always go through the $templateRequest since this the way to ensure that you do get the template you want - for example, something you don't have control over in your app might clear the cache in the background.
We should merge this and add it as a lesson learned to be very careful about what appear to public APIs.


Fix symlink detect if it points to nothing

If symlink points to the deleted folder, os.Stat doesn't work and user is not able to use nvm use ... command. os.Lstat works fine in this case.

Thank you!


SIL: Final methods need a subclass scope if they override something [5.1]

... otherwise we compute the wrong visibility in IRGen.
Fixes rdar://problem/55559104.

@jckarter Mind taking a look?

@swift-ci Please test


Improve architecture and compiler coverage in CI

Here's the new build matrix:

To keep results from CI relatively quick, I purposefully only added the new builds for gcc -- hopefully bugs that occur on Clang (but not GCC) and on, say, aarch64 (but not x86_64) will be very rare.
See individual commits for more details.

@asteinha this is now ready for review. Sorry for the torrent of commit spam.


Add Unit Tests for CopyUtils.java

@md5sha256 This should be pretty straight-forward to unit-test, right?
https://github.com/baked-libs/dough/blob/main/dough-data/src/main/java/io/github/bakedlibs/dough/collections/CopyUtils.java

Yes

This was a scaringly fast reply... 👻

I know right


Bug in all_descendant()

Hello!
the parent_ref value is a string for the first 100 iterations when iterating through entity.all_descendants(folder)
The value becomes an object starting at iteration 101... seems like something is going on with the generator function subsequent calls....
see attached image

debugger

code (which is close to the online example)

Hi
I managed to reproduce the issue.
I have published a new version of pyPreservica
https://pypi.org/project/pyPreservica/2.7.0/
Could you update your version to 2.7.0 and try again.
pip install --upgrade pyPreservica

I used the following to test the fix.
from pyPreservica import *

client = EntityAPI()

i : int = 0
for e in filter(only_assets, client.all_descendants(None)):
    i = i + 1
    print(i, e.parent)

I padded the error, but your timely update is much appreciated.

closed.


feat: ✨ add out-of-the-box support for NextAuth.js

Summary
Adds out of the box support for NextAuth.js by setting the NEXTAUTH_URL to the URL representing the main address of the Netlify site when the next-auth package is detected.
A user will still be required to set the NEXTAUTH_SECRET in production in order to encrypt the NextAuth.js JWT and hash email verification tokens. Related docs
Test plan

Visit the Deploy Preview (here) ...

Relevant links (GitHub issues, Notion docs, etc.) or a picture of cute animal
Fixes #1242

Standard checks:

[ ] Check the Deploy Preview's Demo site for your PR's functionality
[ ] Add docs when necessary

🧪 Once merged, make sure to update the version if needed and that it was published correctly.

This looks great! Can we get the demo site setup to build for PRs? I'd say this is a boulder unless there's a good reason not to


[$500] mWeb - LHN - When LHN is loading, fab not displaying all menu options

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.71
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Enter mail id and tap continue
Enter magic code and sign in
Note LHN is loading
When LHN is loading, tap fab and note fab options
Wait still LHN is loaded and reports in LHN are visible
Now note more fab options are displayed

Expected Result:
When LHN is loading, fab must display all menu options
Actual Result:
When LHN is loading, fab not displaying all menu options
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/c508a634-aab6-40f2-bd6e-61bd31f29e48
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01807feace10021d17
Upwork Job ID:<PHONE_NUMBER>079589376
Last Price Increase: 2024-06-04

Issue OwnerCurrent Issue Owner: @laurenreidexpensify

@bfitzexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Waiting on proposals.

It doesn't display the menu options until it has received the menu options from the server.
Possible solutions:

Server-side render the whole app
Split the server request so it gets the menu options before other data
Server-side render only the menu options state

@james-tindal thank you for your proposal, unfortunately we can not change current api. Please consider doing more research on the project

Waiting for a proposal

Not much action here, doubling the bounty.

I'm not sure what's the expected output here. There's no possible solution here because the actions which are shown after loading complete are depended on the API data which are available after getting all data which means they load only after the loading screen is done.
We can't defer the sections without any data available before which is what we wanted.
Maybe we can disable the FAB while data is loading?

Adding a second BZ member while I'm OOO until June 11th.
@laurenreidexpensify current status:

@b4s36t4 has pointed out that the ideal fix here isn't possible

I've raised this in #vip-vsb here to get some other opinions. I think we either:

close this as expected (in the sense that since the page isn't fully loaded, not all options might show)
go with the alternative solution to disable FAB until the LHN is fully loaded (not sure this is better, tbh)

Proposal
Please re-state the problem that we are trying to solve in this issue
While LHN is loading, FAB popover is not displaying all menu options.
What is the root cause of that problem?
In FloatingActionButtonAndPopover we're conditionally rendering some of the menu options based on variables which are related to the same loading variable the LHN is related to.
What changes do you think we should make in order to solve the problem?
Remove the variable and conditional rendering of the menu options and instead invert the variable boolean and pass it to the menu item's disabled prop. This way we see all the menu options from the beginning, but they are grayed-out (disabled) and the user cannot click on them until the data is actually loaded.
Note: When offline we keep the options disabled.

[!important]

We skip doing this for the Book travel option since canUseSpotnanaTravel is based on permissions and there's no delay when it comes to what UI is shown based on permissions.
For the Quick action item we have to default the getQuickActionIcon to Expensicons.MoneyCircle and add the Loading... label instead of the quick action name, until the actual Quick action data is loaded.
Note: ^ The Quick action disabled UI / label will be discussed with the design team.

Video

MacOS: Chrome
https://github.com/Expensify/App/assets/56457735/e911e653-d4ef-440d-be66-67136bd6742e

What alternative solutions did you explore? (Optional)
Disable the FAB button until the LHN is loaded and all options are available.
Video

MacOS: Chrome
https://github.com/Expensify/App/assets/56457735/5c330cd9-7c04-47c1-bf75-72466ae58b4d

Proposal
Please re-state the problem that we are trying to solve in this issue
While LHN is loading, FAB popover is not displaying all menu options.
What is the root cause of that problem?
In FloatingActionButtonAndPopover we're conditionally rendering some of the menu options based on variables which are related to the same loading variable the LHN is related to.
What changes do you think we should make in order to solve the problem?
Remove the variable and conditional rendering of the menu options and instead invert the variable boolean and pass it to the menu item's disabled prop. This way we see all the menu options from the beginning, but they are grayed-out (disabled) and the user cannot click on them until the data is actually loaded.

[!important]

We skip doing this for the Book travel option since canUseSpotnanaTravel is based on permissions and there's no delay when it comes to what UI is shown based on permissions.
For the Quick action item we have to default the getQuickActionIcon to Expensicons.MoneyCircle and add the Loading... label instead of the quick action name, until the actual Quick action data is loaded.
Note: ^ The Quick action disabled UI / label will be discussed with the design team.

Video

MacOS: Chrome
https://github.com/Expensify/App/assets/56457735/e911e653-d4ef-440d-be66-67136bd6742e

What alternative solutions did you explore? (Optional)
Disable the FAB button until the LHN is loaded and all options are available.
Video

MacOS: Chrome
https://github.com/Expensify/App/assets/56457735/5c330cd9-7c04-47c1-bf75-72466ae58b4d

@ikevin127 Thank you for your proposal I don't think disabling menu items is solving the direct problem of them not being usable till data is loaded.
I agree with @b4s36t4's take here. I think we should close this issue since there is no direct solution for the issue
@laurenreidexpensify Can you share the outcome of the discussion here:

I've raised this in #vip-vsb here to get some other opinions. I think we either:

@ikevin127 Thank you for your proposal I don't think disabling menu items is solving the direct problem of them not being usable till data is loaded.

I'm a bit lost as to where does it state that the expected result is that the options have to be usable before the LHN is loaded 🤔
Expected result states:

When LHN is loading, fab must display all menu options

This is why I proposed showing the options but disabling them until the data is available instead of not rendering them at all and having them pop when the data becomes available (bad UX).
In my view this fulfils the expected result from a UI/UX perspective while also keeping the FAB enabled for access to the other options that don't depend on the data being loaded.
I feel this is the best compromise in this situation, without restructuring BE.

I'm also curious what was the consensus of the discussion from the #vip-vsb slack thread.

@ikevin127 Your take is completely valid. I just didn't accept your solution directly since expected result is not clear, and I disabling menu items cannot be directly derived from expected result pointed out in OP. Moreover, in my opinion, disabling menu items is major UI/UX change and we should move forward with this solution if internal team approves it.
Let's just wait for @laurenreidexpensify to check on here and give us final result.

@Expensify/design can you take a look at this one and confirm if it's something we want to fix?

Oof this is a tricky one. It seems like the ideal fix is to make the app load faster so that the API request to get all the global create options doesn't take so long? But obviously that's not super actionable. I'm struggling to decide if I think it's better to disable global create (or add some kind of loading indicator to the menu while we're still loading) or just leave it as is. Curious for the rest of the design team's thoughts, but I think I'm leaning towards just leaving this as is for now.

Yeah, I totally agree - the real solution here is to make the app faster!
I don't really know that any alternatives or proposals feel that great... I'm basically on the same page as you, blocking the FAB feels bad and giving the FAB any kind of loading state also feels bad. So I think I would also just do nothing, unless we think there's anything from the BE side we can do to speed things up. Can we get an opinion from one of our engineers maybe?

@thienlnam @quinthar @puneetlath @techievivek any thoughts on the above? Thanks

@thienlnam @quinthar @puneetlath @techievivek any thoughts on the above? Thanks

Agree on doing nothing - this is already something that is being worked on with #fast-apis and #newdot-performance, and so doesn't feel worth doing some intermediary step here

I agree with do nothing. I'll close this, but feel free to reopen if you disagree.


API(s) SDK for v2 endpoints

add interfaces for all the endpoints
add v2 streaming to to the SDK
add implementation for all API endpoints
add super basic unit tests

Looks good to me.


GTMOAuth2ViewCOntrollerTouch.h file not found

Hello there, I have googled a good bit for the answer to this question but cant find much. I transferred my project to a new machine and now im getting this error. Screen shot below :

How do you have the code checked out?  pods or directly?  If pods, what pods?

Directly. I assume the fact that the project cant find GTL.xcodeproj has something to do with it. I just havent touched this project in a while so once I transferred it I realized im a bit clueless as to whats going on.

Yea, in that case, you hadn't touched it in a very long time.  The GTL project is gone and we have the GTLCore one.  It doesn't expose a static lib any more either, does have a Framework target.   You'll likely want to start with the BuildingTheLibrary wiki page to reconstruct things.
As mentioned on the docs, we've released a newer project to replace this one GTLR.  It is an more modern version that also moves from JSON-RPC to JSON/REST to support more google services.  There's a migration doc on that wiki also to help coach though some of the api changes when moving.

Okay awesome thats exactly what im looking for. Thank you


Raftstore may broadcast too many messages after one peer store become unreachable

Bug Report
After one store disconnected, StoreFsm would broadcast a StoreUnreachable message to all regions to mark unreachable peers. https://github.com/tikv/tikv/blob/0dff1be50281c72c55c5464751cd733032115ce4/components/raftstore/src/store/fsm/store.rs#L378
But if TiKV has too many regions, handling these StoreUnreachable messages could eat raftstore CPU and block all other messages, making TiKV getting stucked.

cc @BusyJay

Is there any statistics? Like with how many regions will it become a problem?

In about 800k regions, raftstore could eat up to 800% CPU usage.

How many cores? And why setting 30 threads for store pool? Most of resources may probably waste in context switch during broadcast.

How many cores? And why setting 30 threads for store pool? Most of resources may probably waste in context switch during broadcast.

At least 40 cores for one TiKV as I remember, actually we tried to scale it to 4 and 8, but raftstore threads CPU still be eaten up, then finally set it to 30