too many request. try again in some time

Describe Your Problem:
Getting this error in logs, even after leaving homebridge off all night and reinstalling the alexa addon
[6/2/2024, 2:48:20 PM] [HomebridgeAlexaSmartHome] Alexa-Remote: rate exceeded response ... Retrying once in 58696ms [6/2/2024, 2:48:20 PM] [HomebridgeAlexaSmartHome] Alexa-Remote: rate exceeded response ... Retrying once in 37645ms [6/2/2024, 2:49:18 PM] [HomebridgeAlexaSmartHome] BEGIN capabilities for all devices: {   "message": "Too many requests. Try again in some time." } END capabilities for all devices [6/2/2024, 2:49:18 PM] [HomebridgeAlexaSmartHome] After initialization - RequestUnsuccessful(Error getting smart home device state(s). Response: {   "message": "Too many requests. Try again in some time."
Plugin Config:
{     "bridge": {         "name": "Homebridge 1262",         "username": "",         "port": 51582,         "pin": "202-30-841",         "advertiser": "bonjour-hap"     },     "accessories": [],     "platforms": [         {             "name": "Config",             "port": 8581,             "platform": "config"         },         {             "devices": [                 "Thermostat",                 "Speakers"             ],             "excludeDevices": [],             "auth": {                 "refreshInterval": 4,                 "proxy": {                     "clientHost": "homebridge.local",                     "port": 9000                 }             },             "amazonDomain": "amazon.com",             "language": "en-US",             "performance": {                 "cacheTTL": 30,                 "backgroundRefresh": false             },             "debug": true,             "platform": "HomebridgeAlexaSmartHome"         }     ],     "disabledPlugins": []
Environment:

Plugin Version: = 2.1.4
Homebridge Version: = 2023-12-30
Node.js Version: = v18.19.0
NPM Version:
Operating System: = Ubuntu Jammy Jellyfish (22.04.3 LTS)

Same issue just observed.

+1 issue

same for me

me too!

Me too. Return to 2.1.2 helps

Having the same issue. I downgraded problem solved.

Me too. Return to 2.1.2 helps

Downgrading also solved my issue!!

I also had this issue. As soon as I reverted back to 2.1.2 everything worked again.

had the same issue. following suggested rolling back to 2.1.2, seems fixed

Downgrade to 2.1.2 with
hb-service add<EMAIL_ADDRESS>

same issue. downgrading to 2.1.2 OR 2.1.1 did NOT work

+1 same issue. Downgrading did NOT work, also newest version. Its kind of strange, bc it worked till yesterday with 2.1.4 and suddenly stopped with this error. Someone any ideas or help?

@joeyhage +1

i have this same problem... @joeyhage

i hvae the exact same issue

I have tried to figure out the issue, and both authentication and finding the devices are fine, but it fails when retrieving the state. I believe the error comes from all calls to /api/phoenix/state. I was working on a new installation and I have been able to drop the calls that get the state and the devices are added successfully... but without any useful communication with HB.

yeah, I believe Amazon did some backend changes to the API, effectively bricking the retrieval of device states.

The requests are made with a copy of the alexa-remote2 npm package: https://www.npmjs.com/package/alexa-remote2
If the author of the plugin is no longer active, the authors of alexa-remote2 might be able to help here.

Downgrading to version 2.1.2 worked for a few days, but it stopped working today. I was trying to figure out what changes broke the plugin.
I suspected changes in the API, but I'm not certain. Here's what I found so far:

In version 2.1.3, the alexa-remote2 dependency was upgraded from v6.1.2 to v7.0.3, according to the changelog.
In version 2.1.4, alexa-remote.js was added to the repository. It's an edited copy of alexa-remote2 with unnecessary APIs removed.
I compared the alexa-remote.js in this repo to the one from alexa-remote2 v6.2.0, which should be the version 2.1.2 dependency at this moment, and didn't find many meaningful changes.
I discovered an upstream bug in alexa-remote2 v6.2.0, where the getAuthApiBearerToken function incorrectly referenced a fixed Germany API endpoint https://api.amazon.de/auth/token, regardless of the user's settings. This bug was fixed in v7.0.4, as well as in the version manually copied into the repo.

My guess is that Amazon recently changed the authorization API, rolling it out in the US a few days before Germany. This would explain why version 2.1.2 with the hardcoded Germany endpoint worked for a few days before failing. However, if my assumptions are correct, I'm unsure why we were able to use the Germany authorization API while all the other APIs were for the US.

2.1.2 also stopped working for me today as well.
On Wed, Jun 12, 2024 at 10:45 PM shenghan97 @.***>
wrote:

Downgrading to version 2.1.2 worked for a few days, but it stopped working
today. I was trying to figure out what changes broke the plugin.
I suspected changes in the API, but I'm not certain. Here's what I found
so far:

In version 2.1.3, the alexa-remote2 dependency was upgraded from
v6.1.2 to v7.0.3, according to the changelog.
In version 2.1.4, alexa-remote.js was added to the repository. It's
an edited copy of alexa-remote2 with unnecessary APIs removed.
I compared the alexa-remote.js in this repo to the one from alexa-remote2
v6.2.0, which should be the version 2.1.2 dependency at this moment,
and didn't find many meaningful changes.
I discovered an upstream bug in alexa-remote2 v6.2.0, where the
getAuthApiBearerToken function incorrectly referenced a fixed Germany API
endpoint https://api.amazon.de/auth/token, regardless of the user's
settings. This bug was fixed in v7.0.4, as well as in the version manually
copied into the repo.

My guess is that Amazon recently changed the authorization API, rolling it
out in the US a few days before Germany. This would explain why version
2.1.2 with the hardcoded Germany endpoint worked for a few days before
failing. However, if my assumptions are correct, I'm unsure why we were
able to use the Germany authorization API while all the other APIs were for
the US.
—
Reply to this email directly, view it on GitHub
https://github.com/joeyhage/homebridge-alexa-smarthome/issues/129#issuecomment-2164250545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIKPASUBLFSVNMIXICGICOTZHEBTLAVCNFSM6AAAAABIVKK2E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGI2TANJUGU
.
You are receiving this because you commented.Message ID:
@.***>

I'm using an air conditioner, I'm from Poland and given a .com domain in the app (as if it were American, not German).
I did a downgrade to 2.1.2 - it started working.
It stopped.
I did downgrade to 2.1.4 - the air conditioner is visible in homekit, but does not respond to temperature change.

Yep, 2.1.2 worked for a while but stopped working for me today. 2.1.4 stopped working for me almost 2 weeks ago at this point.

Same problem.
HomeBridge: v1.8.2
Node.js:	v20.12.2
Homebridge Alexa Smart Home: v2.1.2
END devices connected to Alexa account
[6/13/2024, 8:03:10 PM] [HomebridgeAlexaSmartHome] Found all 2 devices in plugin settings.
[6/13/2024, 8:03:10 PM] [HomebridgeAlexaSmartHome] Updating device states
[6/13/2024, 8:03:10 PM] [HomebridgeAlexaSmartHome] Alexa-Remote: rate exceeded response ... Retrying once in 41915ms
[6/13/2024, 8:03:10 PM] [HomebridgeAlexaSmartHome] Alexa-Remote: rate exceeded response ... Retrying once in 55804ms
[6/13/2024, 8:03:52 PM] [HomebridgeAlexaSmartHome] BEGIN capabilities for all devices: {
  "message": "Too many requests. Try again in some time."
} END capabilities for all devices
[6/13/2024, 8:04:06 PM] [HomebridgeAlexaSmartHome] After initialization - RequestUnsuccessful(Error getting smart home device state(s). Response: {
  "message": "Too many requests. Try again in some time."
})

I can get device capabilities just fine. It fails later when retrieving
device states. I actually could add new devices after modifying the code a
bit, but they are just useless without the ability of getting or setting
the state.
El El vie, 14 jun 2024 a las 16:56, Erik Abele @.***>
escribió:

My guess is that Amazon recently changed the authorization API, rolling it
out in the US a few days before Germany. This would explain why version
2.1.2 with the hardcoded Germany endpoint worked for a few days before
failing. However, if my assumptions are correct, I'm unsure why we were
able to use the Germany authorization API while all the other APIs were for
the US.
When looking at my logs (debug enabled), I can see authorization working
fine here (I'm in DE and using amazon.de) but right after that when
alexa-remote is trying to get the device capabilities it gets a response of
429 (too many requests). Don't have the time to dig deeper but obviously
Amazon changed some limits here and either amazon-alexa is really doing to
many requests or Amazon did this intentionally to block it...
—
Reply to this email directly, view it on GitHub
https://github.com/joeyhage/homebridge-alexa-smarthome/issues/129#issuecomment-2168217547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO4I6MWMSL4PAXIWLD3Y33ZHMAAXAVCNFSM6AAAAABIVKK2E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGIYTONJUG4
.
You are receiving this because you commented.Message ID:
@.***>

Yes, that's where the issue happened. I can't find any documentation about this /api/phoenix/state API, was this maybe never intended to be used publicly?

I did some more digging and finally found the cause—it looks like the Alexa API now rejects requests and returns a 429 error whenever the user agent string includes "AlexaRemote."
The quickest fix is to set the user agent suffix to an empty string, like this:
this._options.apiUserAgentPostfix = ''

You can find this in the alexa-remote.js file at line 118:
https://github.com/joeyhage/homebridge-alexa-smarthome/blob/32176a6ca03186afed1d5200593ca73c0146854f/src/alexa-remote.js#L118
I've fixed this on my end by manually editing the file in the node_modules folder at homebridge/node_modules/homebridge-alexa-smarthome/dist/alexa-remote.js.
I can make a pull request this weekend, but I'm not sure when it will be merged.

Yes, that's where the issue happened. I can't find any documentation about this /api/phoenix/state API, was this maybe never intended to be used publicly?

Yes, this seems to be a private API, there's zero docs and other devs are reverse engineering it, e.g. here.

The quickest fix is to set the user agent suffix to an empty string, like this:

Haha, I was thinking about that too but didn't bother to try it; anyway, can confirm that changing the UA fixes the issue. So we can be pretty sure that this was an intentional block by Amazon.

I can make a pull request this weekend, but I'm not sure when it will be merged.

Yes, would be great. OTOH, I guess they will block empty UA strings then or find some other way to block it, oh my...

Yeah, me too. It gets the cookie and authenticates, gets the devices, but then when when trying to get their states fails.

I did some more digging and finally found the cause—it looks like the Alexa API now rejects requests and returns a 429 error whenever the user agent string includes "AlexaRemote."
The quickest fix is to set the user agent suffix to an empty string, like this:
this._options.apiUserAgentPostfix = ''

You can find this in the alexa-remote.js file at line 118:
https://github.com/joeyhage/homebridge-alexa-smarthome/blob/32176a6ca03186afed1d5200593ca73c0146854f/src/alexa-remote.js#L118
I've fixed this on my end by manually editing the file in the node_modules folder at homebridge/node_modules/homebridge-alexa-smarthome/dist/alexa-remote.js.
I can make a pull request this weekend, but I'm not sure when it will be merged.

Great find. I would be happy to review the PR. Sorry all that I’ve been MIA, I got back from vacation today.

 I thought you had abandoned the plug-in.

I can make a pull request this weekend, but I'm not sure when it will be merged.

Did you make the poll request yet?

Tested and published a new version, v2.1.5. I tested the prior and new user agents side by side:  the prior user agent resulted in the too many requests error, the new user agent worked seamlessly. Please let me know if this didn’t resolve your issue, otherwise I will assume this has been fixed.

Just updated to 2.1.5 and can confirm that the 429 errors are gone. Thank you, Joey!

Same for me. Everything fine - thank you!

Works fine by me, thanks for the fix.Envoyé de mon iPadLe 16 juin 2024 à 21:39, Joey Hage @.***> a écrit :
Tested and published a new version, v2.1.5. I tested the prior and new user agents side by side:  the prior user agent resulted in the too many requests error, the new user agent worked seamlessly. Please let me know if this didn’t resolve your issue, otherwise I will assume this has been fixed.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi Joey, thanks for the fix. I updated to 2.1.5 and the too many requests error went away. A new one popped up saying “after initialization http error.”
My devices are from the smart life through Alexa. Kind of like this issue here:
https://github.com/joeyhage/homebridge-alexa-smarthome/issues/121
Is there any troubleshooting steps you suggest with this to get them working again?

Hi Joey, thanks for the fix. I updated to 2.1.5 and the too many requests error went away. A new one popped up saying “after initialization http error.”
…

I would recommend using the @0x5e/homebridge-tuya-platform plugin for those devices. That’s what I use and it works great.

Thanks for the help!

I am still seeing Too many requests error on 2.1.5

@joeyhage I'm still getting these errors on version 2.1.5. I have double confirmed I'm on the latest version. Any ideas on how to fix it?
[6/25/2024, 3:22:06 AM] [homebridge-alexa-smarthome] Alexa-Remote: rate exceeded response ... Retrying once in 48225ms
[6/25/2024, 3:22:06 AM] [homebridge-alexa-smarthome] Alexa-Remote: rate exceeded response ... Retrying once in 41445ms
[6/25/2024, 3:22:55 AM] [homebridge-alexa-smarthome] BEGIN capabilities for all devices: {
"message": "Too many requests. Try again in some time."
} END capabilities for all devices
[6/25/2024, 3:22:55 AM] [homebridge-alexa-smarthome] After initialization - RequestUnsuccessful(Error getting smart home device state(s). Response: {
"message": "Too many requests. Try again in some time."
})

try change time from 30s to 40s

Just tried it. Still getting the same error.

I'm also getting the same error - seemingly regardless of the cache lifetime setting

@jlupini @jmantheitguy Just checked here and it works flawlessly for me. We would need to debug again to find out if there's some edge case where the user-agent is set a second time. Maybe you can simply grep the codebase for something like 'AlexaRemote' or 'UserAgent' and see if something pops up. Hope that helps.

i have this same problem, air conditionier not working
[6/27/2024, 10:18:54 AM] [homebridge-alexa-smarthome] Child bridge process ended
[6/27/2024, 10:18:54 AM] [homebridge-alexa-smarthome] Process Ended. Code: 143, Signal: null
[6/27/2024, 10:19:01 AM] [homebridge-alexa-smarthome] Restarting Process...
[6/27/2024, 10:19:01 AM] [homebridge-alexa-smarthome] Launched child bridge with PID 9236
[6/27/2024, 10:19:02 AM] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.1.5 child bridge successfully
[6/27/2024, 10:19:02 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Klimatyzator
[6/27/2024, 10:20:01 AM] [homebridge-alexa-smarthome] After initialization - RequestUnsuccessful(Error getting smart home device state(s). Response: {

I'm also getting the same error - seemingly regardless of the cache lifetime setting
same

I'm also getting the same error - seemingly regardless of the cache lifetime setting

same


3Sum

Leetcode Question no. - 15
Problem name - 3Sum
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Programming Language

[x] Python

Happy Coding

Can I work on this issue?

Please assign this issue to me


Lara/profilePic

I have created the profile pic component, you can select a sport and it will show your ability level for that sport

@WilfSilver please can you review and merge

Due to lack of response from lara, I am taking over this branch


Make it a portable IDE like VSCode.

Feature Description:
I can add a folder called data in root directory of vscode, then it will become portable, and store all data in that folder. I hope I can do that in theia as well as vscode.

Hi @StellarH ,
This sounds interesting. Do you have a link for related documentation?

Hi @StellarH ,
This sounds interesting. Do you have a link for related documentation?

Maybe this?

Actually, it also can be used with an installed vscode.

"Portable mode is supported on the ZIP download for Windows, and the TAR.GZ download for Linux, as well as the regular Application download for macOS"

I suspect that portable mode does not really care about which packaging of vscode was used to  install it. However, it probably makes sense not to officially support using a modified system-wide installation of a tool, and the permission and other various issues, likely to follow. I think Theia should probably do similar.


The Witcher 3 crashes when using nvidia 450.66

I tried installing the latest nvidia driver 450.66, but it randomly crashes when I play The Witcher 3 while the previous driver 440.100 works perfectly, but the 450 driver has a way better performance. It also feezes the game sometimes when I adjust sound/brightness and gnome OSD shows up.
In the changelog of the 450.66 driver, there's this thing Fixed triple buffering support of Vulkan X11 swapchains when applications are syncing to vblank. Could it be the cause of the issue since I had no problems on previous versions?
Sadly there's nothing shown in dxvk, wine or system logs when it freezes/crashes.
Software information
The Witcher 3, ultra settings, 1920x1080 on Ubuntu 20.04.
System information

GPU: Nvidia RTX 2070 Super
Driver: 450.66
Wine version: 5.7
DXVK version: 1.7.1L

* DXVK version: 1.7.1L

Does this mean you're using the latest dev build? I've had similar issues with The Witcher 3 ever since switching to the 450 Nvidia driver branch (including on 450.57), but I haven't seen crashes since 16a51f3 . Then again I haven't played all that much lately. Going back to 440.100 also makes it rock solid again (no crashes) regardless of the DXVK version you use, as you've also noted.

I tried to compile master, but I get the following error :
Compiling C++ object 'src/util/ed6d25d<EMAIL_ADDRESS>FAILED: src/util/ed6d25d<EMAIL_ADDRESS>x86_64-w64-mingw32-g++ -Isrc/util/ed6d25d@@util@sta -Isrc/util -I../src/util -I.././include -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++17 -O3 -DNOMINMAX -MD -MQ 'src/util/ed6d25d<EMAIL_ADDRESS>-MF 'src/util/ed6d25d<EMAIL_ADDRESS>-o 'src/util/ed6d25d<EMAIL_ADDRESS>-c ../src/util/log/log_debug.cpp In file included from ../src/util/log/log_debug.h:5,                  from ../src/util/log/log_debug.cpp:1: ../src/util/log/log.h:50:10: error: ‘mutex’ in namespace ‘std’ does not name a type
The driver 440.100 worked perfectly yea, but there's a performance bump by ~15 fps with 450.66, so I'd like to use this one.
The 1.7.1L is how lutris named it, but I also tried with 743f309 and it still crashes.

error: ‘mutex’ in namespace ‘std’ does not name a type

https://github.com/doitsujin/dxvk#troubleshooting

but I also tried with 743f309 and it still crashes.

743f309 precedes 16a51f3, so I'm not too surprised you still get crashes. You also don't have to compile master yourself, since you can usually find relatively new builds here.

I managed to compile master, and it seems stable. I played for like 15 minutes but there wasn't a single crash. I'll try more longer sessions to test it but so far it seems that it's fixed.

Should 41a49a9c do the job?

Should 41a49a9 do the job?

Yes, pretty much anything that comes after 16a51f3 should be fine, including 41a49a9.

Thank you very much :)


Update to Ember 4.8, address deprecations

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Appveyor integration

Add basic AppVeyor inegration, you only need to login to AppVeyor and add this repository.
I can also add:

[ ] code coverage
[ ] generate nuget packges
[ ] SonarQube integration
[ ] TravisCI integration for cross-platform testing

AppVeyor is now running for each push, and I added the status badge in 9ad475b.

AppVeyor is now publishing versioned NuGet packages from master.


Creation of vmware node template failed

Steps to reproduce (least amount of steps as possible):
Appropriate values for the below fields were entered.
vCenter or ESXi Server
Username
Password
Data Center
Pool
Host
Data Store
Network
Expected Result
Template should be created successfully.
Actual result:
Validation failed in API: vmwarevsphereConfig password=NotNullable 422:
Response from UI:
{"baseType":"error","code":"InvalidFormat","fieldName":"vmwarevsphereConfig","message":"password=NotNullable 422: ","status":422,"type":"error"}
Request:

Environment information

Rancher version: rancher:master(02/12/2019)

@westlywright It looks like we're sending empty password even if the credential is set, don't see the secretKey or clientSecret getting sent for other node templates, could you confirm this is the issue?

@kinarashah it is a UI issue, the vmwarevsphereConfig is being initialized with the password field which is breaking stuff. I'll assign to myself and have a fix in shortly.

verified on latest master build rancher:master (02/14/2019).
Able to create a vSphere node template.


[mgmt] netapp release

https://github.com/Azure/sdk-release-request/issues/5168

breaking caused by https://github.com/Azure/azure-rest-api-specs/pull/28617

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-netapp


Start work on supporting Maps and Workflows

Codecov Report

Merging #237 (f6eca41) into main (deccef6) will decrease coverage by 0.65%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #237      +/-   ##
==========================================
- Coverage   90.64%   90.00%   -0.65%
==========================================
  Files          19       20       +1
  Lines         556      560       +4
==========================================
  Hits          504      504
- Misses         52       56       +4

Impacted Files
Coverage Δ

src/NavAbilitySDK.jl
100.00% <ø> (ø)

src/services/Map.jl
0.00% <0.00%> (ø)


All attempts for divergence time estimation were failed. Exiting.

RADTE version: 0.2.0
ape version: 5.6.2
rkftools version: 0.0.1
R version 4.1.2 (2021-11-01)
RADTE run_mode: batch
arguments:
species_tree = /gfe_data/species_tree/dated_species_tree.generax.nwk
generax_nhx = /gfe_data/orthogroup/generax.tree/OG0006851.generax.nhx
max_age = 1000
chronos_lambda = 1
chronos_model = discrete
pad_short_edge = 0.001

--generax_nhx was detected. GeneRax mode.

Start: species tree processing
Read 1 item
Minimum edge length: 5.6516
Number of short edges ( length < 0.001 ): 0
The tree is not ultrametric. Adjusting the branch length.
Total branch length difference between before- and after-adjustment: 0.001273899
Nonzero tip age(s) were detected (max=2.8421709430404e-14). Coercing to 0.
End: species tree processing

Start: gene tree processing
Reading GeneRax tree.
1 out of 54 branches have small length. Padding with 0.001.
Minimum branch length in gene tree: 0.001
End: gene tree processing

# species in the gene tree: 19
Species in the gene tree: Oryza_sativa, Aldrovanda_vesiculosa, Dionaea_muscipula, Drosera_spatulata, Drosophyllum_lusitanicum, Ancistrocladus_abbreviatus, Nepenthes_gracilis, Triphyophyllum_peltatum, Hylocereus_undatus, Spinacia_oleracea, Beta_vulgaris, Amaranthus_hypochondriacus, Vitis_vinifera, Arabidopsis_thaliana, Populus_trichocarpa, Cephalotus_follicularis, Averrhoa_carambola, Aquilegia_coerulea, Amborella_trichopoda
Divergence time of the parent species tree clade: 1000
Divergence time of the MRCA species tree clade: 193.0061
calibration node removed because of the constraint identical to or greater than one of the upper nodes (name/id/lower/upper):
n28/31/1000/193.0061
n79/34/1000/193.0061
n55/36/1000/193.0061
n31/40/1000/193.0061
n76/48/1000/193.0061
n70/50/1000/193.0061
n82/52/1000/193.0061
n91/53/1000/193.0061

Number of constrained speciation nodes: 19
Number of constrained duplication nodes: 0

chronos, calibrated nodes: RS

Setting initial dates...
Fitting in progress... get a first set of estimates
Error in if (sum(freq) > 1) return(-1e+100) :
  missing value where TRUE/FALSE needed

chronos, calibrated nodes: S

Setting initial dates...
Fitting in progress... get a first set of estimates
         (Penalised) log-lik = -34.34865
Optimising rates... frequencies...Error in if (sum(freq) > 1) return(-1e+100) :
  missing value where TRUE/FALSE needed

chronos, calibrated nodes: R

Setting initial dates...
Fitting in progress... get a first set of estimates
Error in if (sum(freq) > 1) return(-1e+100) :
  missing value where TRUE/FALSE needed
All attempts for divergence time estimation were failed. Exiting.

This error was obtained on Linux, but it didn't reproduce on Intel Mac.
RADTE version: 0.2.0
ape version: 5.6.2
rkftools version: 0.0.1
R version 4.1.1 (2021-08-10)

...

chronos, calibrated nodes: RS

Setting initial dates...
Fitting in progress... get a first set of estimates
         (Penalised) log-lik = -33.32539
Optimising rates... frequencies... dates... -33.32539
Optimising rates... frequencies... dates... -32.49264
Optimising rates... frequencies... dates... -32.49223

log-Lik = -32.49222
PHIIC = 118.98


Make fork even with submodules

Note: Building some examples causes shader compilation errors. The ones that commented:
Line 252
Line 268
Line 272

Can you expand on why bgfx-shader-spirv is renamed?

Can you expand on why bgfx-shader-spirv is renamed?

Build scripts are updated and renamed in original repo. That's the commit: https://github.com/bkaradzic/bgfx/commit/302c978b1d2a066035df2803395fbe4df67a4aa8


Telemetry from device that has NOT been selected.

Describe the bug
Start Telemetry from a device (in my case GFSDev002), and I'm getting telemetry from device GFSDev001.
To Reproduce
Each device has its own connection string.

Expected behavior
Starting telemetry for GFSDev002, should only show Telemetry sent by GFSDev002.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
OS Version: 10
App version: alpha

Additional context
I'm thinking the IOT Explorer is subscribing to the Consumer Group, rather than the device? If so, then the title is confusing as it clearly states it Telemetry from GFSDev002.

I've had this happening to me as well. Steps to reproduce:

Listen to device A's Telemetry
Instead of pressing "Stop", return to the "Devices" list
Start listening to device B's Telemetry

Result: device A's telemetry is shown in between device B's telemetry.
Suspect: Forgot to unsubscribe from telemetry after navigating away from a device's telemetry page?

Seen this happen many times, but didn't realize the sequence of events to cause it. This is definitely a bug!

same here

Event hub does not support filtering on device. Yes we can only subscribe to the Consumer Group like @codeputer you've describe. We do unsubscribe when the component unmount (when the page closes), but there will be a lag. As long as the telemetry won't keep showing after about 10s, we will not able to fix this issue due the constraints we face.


no luarocks in

Whenever I start a new terminal session it writes
/usr/bin/which: no luarocks in (/home/jonathan/.luaver/lua/5.1.5/bin:/home/jonathan/.nvm/versions/node/v6.4.0/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/jonathan/.local/bin:/home/jonathan/bin)  at the top. My guess is that it can't find luarocks in path.

Does this happen 'just' as you start a new terminal session? Could you show me the contents of your ~/.bashrc or ~/.zshrc file?

I solved it by installing luarocks with my package manager too. It works now
On 5 September 2016 22:07:47 CEST, Dhaval Kapil<EMAIL_ADDRESS>wrote:

Does this happen 'just' as you start a new terminal session? Could you
show me the contents of your ~/.bashrc or ~/.zshrc file?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/DhavalKapil/luaver/issues/14#issuecomment-244806043

Even if luarocks is not installed, this error should not come. Anyways, if you face the same error again, feel free to ping here.


integrate with SFML

Hi,
how can i integrate Gainput with SFML, SFML expose only the Window ID, and how to integrate gainput event handling with sfml event Handling ?

I guess you can just get the native window handle with GetActiveWindow
https://msdn.microsoft.com/en-us/library/windows/desktop/ms646292(v=vs.85).aspx

Sorry, i forgot to specifying that i'm on Linux environnement, (i managed this issue by writting my own Window Library, but i think a solution to this issue can be useful for other peoples)
(sorry for my english, this is not my primary language)


feat: leverage resuable docker build workflow

Adds the ability to call reusable docker build workflow.

Looks good, merge it!


Crab tutorial not working

Do you want to:
Bug report
What Should Go in a Bug Report
Mac with Chrome
Visit https://tutorials.bigchaindb.com/crab/
Scroll to the bottom en click "First step: create an asset" button
Scroll to the bottom en click "Execute code" button
Error:
Something went wrong!

status: 400
BAD REQUEST

: Invalid transaction (InvalidHash): The transaction's id '128574a5e898d09318ab065243372f194720f54e33746e3c025d66eb1205cdd3' isn't equal to the hash of its body, i.e. it's not valid.`

I verified. It also doesn't work for me running Chrome 67.0.3396.62 (64-bit) on Ubuntu 17.10.

This is more than the crab tutorial. I get the same error with a current BigchainDB setup (cloned from the original repository) and the original JS driver when I run the basic usage example.


Update roadmap, or remove links to it - TBD

Describe the issue
On both https://dockstore.org/about and its docs equivalent, we link to https://github.com/dockstore/dockstore/wiki/Dockstore-Roadmap, which hasn't been updated since March 2021.
On both the main webpage and the docs version it is under the heading "future plans".
Expected behavior
If we are linking people to a roadmap, that roadmap should be updated regularly.
┆Issue is synchronized with this Jira Story
┆fixVersions: Dockstore 1.14
┆friendlyId: DOCK-2178
┆sprint: 98- Zebra fish
┆taskType: Story

THink we're going to update, it might at a get-together some time later in the year though

Yeah, I threw in that "past year" reference because we neglected to add a 2022 section and now it seems a little like rewriting history to write a pretend section as if the 1.12 and 1.13 sections were what we intended to do ahead of time. .


Options to replace and exclude deps

Hello guys!
I have been using conda-press for some days and I faced two improvements which would be nice to have.  :)
The first problem is, there are some dependencies which exist just in conda-forge or in the main packages. If I use conda-press to convert it, the wheel will try to install that dependency. For example, Caffe is a package which we have on conda-forge but we don't have it on PyPI.
It would be good to have an option such as --exclude-dep which accepts a list of deps we may exclude.
The second problem might be related to the first one, some dependencies have different names in conda-forge/main and in PyPI. For example, OpenCV is just OpenCV on conda-forge but it is different on PyPI, which is OpenCV-python. It would be interesting to have an option to replace some dependencies name or allied with the --exclude-dep we might have an option --add-dep which also accepts a list of packages to be added to the wheel.
I might try to develop it during this weekend, but if someone already knows how to implement it. It is fine for me!  :)
cc: @scopatz

Hi @marcelotrevisani! Sorry for the slow response; I was on vacation.
I think either / both of those options would be great to have. In general, it would be nice to be able to provide a mapping from the "conda name" of a package to the "pypi" name of the package.  Maybe this could live on the command line and/or in a sidecar file somewhere.  Note that it would definitely need to be something that is overrideable because conda-press can be used with channels that are not conda-forge and be targeting package indexes that aren't pypi.org.

Also, note that if we wanted a general mapping, the conda packages themselves usually contain the pypi.org name in the source code url.  We could try to generate and maintain a list with one of the bots. That will come later, though. The functionality needs to be in conda-press first.

Closing this in favor of #23 and #26


Error when deploying hive make deploy using latest master

Hi,
I just redeploy the latest master on an existing hive deployment. The previous hive deploy was deployed last Friday and I got this error.
deployment.apps/hive-operator unchanged
Error from server: error when creating "STDIN": unsupported role reference kind: ""
Error from server (Invalid): error when applying patch:
{"metadata":{"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"rbac.authorization.k8s.io/v1\",\"kind\":\"ClusterRoleBinding\",\"metadata\":{\"annotations\":{},\"name\":\"hiveapi-cluster-admin\"},\"roleRef\":{\"apiGroup\":\"rbac.authorization.k8s.io\",\"kind\":\"ClusterRole\",\"name\":\"manager-role\"},\"subjects\":[{\"kind\":\"ServiceAccount\",\"name\":\"hiveapi-sa\",\"namespace\":\"hive\"}]}\n"}},"roleRef":{"name":"manager-role"}}
to:
Resource: "rbac.authorization.k8s.io/v1, Resource=clusterrolebindings", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding"
Name: "hiveapi-cluster-admin", Namespace: ""
Object: &{map["kind":"ClusterRoleBinding" "apiVersion":"rbac.authorization.k8s.io/v1" "metadata":map["name":"hiveapi-cluster-admin" "selfLink":"/apis/rbac.authorization.k8s.io/v1/clusterrolebindings/hiveapi-cluster-admin" "uid":"6d05eb70-46fe-11ea-b860-021aed110e05" "resourceVersion":"54229499" "creationTimestamp":"2020-02-04T03:28:35Z" "annotations":map["kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"rbac.authorization.k8s.io/v1\",\"kind\":\"ClusterRoleBinding\",\"metadata\":{\"annotations\":{},\"name\":\"hiveapi-cluster-admin\"},\"roleRef\":{\"apiGroup\":\"rbac.authorization.k8s.io\",\"kind\":\"ClusterRole\",\"name\":\"cluster-admin\"},\"subjects\":[{\"kind\":\"ServiceAccount\",\"name\":\"hiveapi-sa\",\"namespace\":\"hive\"}]}\n"]] "subjects":[map["kind":"ServiceAccount" "name":"hiveapi-sa" "namespace":"hive"]] "roleRef":map["apiGroup":"rbac.authorization.k8s.io" "kind":"ClusterRole" "name":"cluster-admin"]]}
for: "STDIN": ClusterRoleBinding.rbac.authorization.k8s.io "hiveapi-cluster-admin" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"ClusterRole", Name:"manager-role"}: cannot change roleRef
make[1]: *** [deploy] Error 1
 [HIVE INSTALL] FAILURE: Failed to deploy hive

I wonder if it is not related to PR https://github.com/openshift/hive/pull/815 or one of the PR recently merged.
I deleted the hiveapi-cluster-admin and re-run but still have error
clusterrolebinding.rbac.authorization.k8s.io/hive-operator-rolebinding configured
clusterrolebinding.rbac.authorization.k8s.io/hiveadmission-hive-hiveadmission unchanged
clusterrolebinding.rbac.authorization.k8s.io/hiveapi-cluster-admin unchanged
clusterrolebinding.rbac.authorization.k8s.io/manager-rolebinding configured
deployment.apps/hive-operator unchanged
Error from server: error when creating "STDIN": unsupported role reference kind: ""
make[1]: *** [deploy] Error 1
 [HIVE INSTALL] FAILURE: Failed to deploy hive
make: *** [test] Error 2

Bad commits went in yesterday, fixed in referenced PR.

FYI not sure your use case but a major merge took place yesterday, master now has hive's v1 API and a v1alpha1 compatibility layer. This includes the bare metal provisioning work done so far, though this is not operational until #819 and #820 merge.

Thx, I will wait the PR to be merge to try again.
FYI: My use case is for our CICD automation. We have a cluster on which we deploy hive in order to create new clusters.

Are you building the Hive image from source or using one of our CI images? If so could you clarify which image ref.

From source. I do a 'make deploy'.
Do you plan to use github release tag, so we can clone a stable release as for the time being there is only 1 release tag v1alpha1.

We do not have any release tagging in play at this time, just rolling releases via git hash to our main environments. The v1alpha1 tag was created this morning and is the last commit prior to the v1 merge.
However if this is for the integration I think it is then that work should all have been targeting the v1 branch, and thus now master. Nothing should have been using v1alpha1.

Deploying with your branch git@github.com:dgoodwin/hive.git works but not with master after the merge of #818

ok found the issue... I was cloning the v1 branch instead of master and the last update was done on master and not v1.


TYPO: change bundle.yam to bundle.yaml

TYPO: change bundle.yam to bundle.yaml
CHANGE DESCRIPTION
Problem:
Simple typo fix in README.md
Short explanation of the problem.
Change bundle.yam to bundle.yaml in README.md file

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

@yeskiy thank you for contribution


3D Tiles - Dynamic Screen Space Error

For #3241
Like terrain fog, this enables a dynamic screen space error for rendering lower detail tiles based on distance. I mainly tested this with replacement refinement tilesets and I see about 20% reduction in the number of visited tiles for street-level views for city-like tilesets and anywhere from 50% to 70% improvement for more terrain-like datasets without too much loss in visual quality. These percentages fluctuate depending on the maximumScreenSpaceError that is applied, and is more favorable for lower values.
The settings can be tweaked by changing tileset.usesDynamicScreenSpaceError, tileset.dynamicScreenSpaceErrorDensity, and tileset.dynamicScreenSpaceErrorFactor.

@bagnell can you also take a quick look at this?

Just those comments.  Will also test this with some datasets once the Sandcastle example has more options.

When fog is used with a dynamic SSE for terrain, we also stop requesting tiles that are completely in fog.
It is worth doing something similar here with a max distance?

When fog is used with a dynamic SSE for terrain, we also stop requesting tiles that are completely in fog. It is worth doing something similar here with a max distance?

We could do that, but also the tiles in the distance should be pretty low res to begin with so there won't be that many requests saved.

Though it does depend on the

We could do that, but also the tiles in the distance should be pretty low res to begin with so there won't be that many requests saved.

This widely depends on the tileset.  Consider a root tile with 300 children, or just a uniform grid.

Any concerns if I merge this into 3d-tiles-temp for testing?

Any concerns if I merge this into 3d-tiles-temp for testing?

Nope, go ahead.

My testing and the code look good.  I still don't think the doc for dynamicScreenSpaceErrorDensity and dynamicScreenSpaceErrorFactor make it obvious how to use them, e.g., explain-ish how they are non-linear.  Perhaps the terrain doc also should be improved.
I'll also hold off on merging until the local coordinate system change we discussed offline.

Updated.

When fog is used with a dynamic SSE for terrain, we also stop requesting tiles that are completely in fog.

It is worth doing something similar here with a max distance?

I could be wrong, but I think it's just doing the same thing as here, requesting less because it refines less. But the uniform grid type scenario for 3d tiles is definitely worth handling. Is it ok if I handle this in another PR? I also want to clean up some of the checks we do (check sse, check visibility, compute distance, sort by distance, check request volume) that we do in multiple places.

I'll look at this

Updated. I addressed the remaining points. I just have to add one more bounding volume test, and will update this issue when its ready (should be later today).

CC @pmconne

Looks good, let me know when the tests are finished.

The last test is done now.

Do these tests fail for you?
Scene/GlobeSurfaceTileProvider fog culls tiles in full fog
Expected [ 255, 0, 0, 255 ] to equal [ 0, 0, 0, 255 ].
Error: Expected [ 255, 0, 0, 255 ] to equal [ 0, 0, 0, 255 ].
    at stack (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:1475:17)
    at buildExpectationResult (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:1445:14)
    at Spec.expectationResultFactory (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:584:18)
    at Spec.addExpectationResult (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:332:34)
    at Expectation.addExpectationResult (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:528:21)
    at Expectation.toEqual (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:1399:12)
    at http://localhost:8080/Specs/Scene/GlobeSurfaceTileProviderSpec.js:391:48
    at Promise.then (http://localhost:8080/Source/ThirdParty/when.js:196:34)
    at http://localhost:8080/Source/ThirdParty/when.js:297:13
    at processQueue (http://localhost:8080/Source/ThirdParty/when.js:647:4)
Scene/GlobeSurfaceTileProvider fog culls tiles because of increased SSE
Expected [ 255, 0, 0, 255 ] not to equal [ 255, 0, 0, 255 ].
Error: Expected [ 255, 0, 0, 255 ] not to equal [ 255, 0, 0, 255 ].
    at stack (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:1475:17)
    at buildExpectationResult (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:1445:14)
    at Spec.expectationResultFactory (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:584:18)
    at Spec.addExpectationResult (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:332:34)
    at Expectation.addExpectationResult (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:528:21)
    at Expectation.toEqual (http://localhost:8080/ThirdParty/jasmine-2.2.0/jasmine.js:1399:12)
    at http://localhost:8080/Specs/Scene/GlobeSurfaceTileProviderSpec.js:417:52
    at Promise.then (http://localhost:8080/Source/ThirdParty/when.js:196:34)
    at http://localhost:8080/Source/ThirdParty/when.js:297:13
    at processQueue (http://localhost:8080/Source/ThirdParty/when.js:647:4)

Ah those are caused by this change: https://github.com/AnalyticalGraphicsInc/cesium/pull/4307#r79319602
Because of the old math, fog would be applied in bird's eye view, which is the view these tests use. But my change prevents fog from happening for those views. @bagnell can you check that my code change makes sense?

@bagnell thoughts here? We want to merge this soon.

Updated. Those tests pass now.

👍


Fix installation of manpages

Previously, the markdown versions of the man pages were copied to their respective locations, but these cannot be parsed by the man command.  The Makefile was updated to gzip the man pages generated by go-md2man and install the gzipped files into their respective man directories.

@rhatdan PTAL

LGTM. I had to do something similar for openSUSE as well.

LGTM

This is fine, my patch was not doing the compression.  This is usually done by RPM.


backfill-tool: Fix collection CYGNSS_L2_SURFACE_FLUX_V2.0 for generating footprints

All footprints failed on the last run of the Backfill-Tool.
Please fix this collection generating footprints

Need to make sure @skorper disables footprint for this collection in cumulus


Impossible to establish external connection even by following the documentation

Hi everyone,
I migrated to Istio 1.1 a few days ago and I noticed today that one of my microservice was no longer able to reach Google APIs.
I checked it really comes from Istio by creating the same deployment without Istio injection and the microservice is able to reach Google APIs.
My previous configuration about egress was:
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: googleapis
spec:
  hosts:
  - "*.googleapis.com"
  location: MESH_EXTERNAL
  ports:
  - number: 443
    name: tls
    protocol: TLS
  resolution: DNS

but since it's no longer working I checked a new time the documentation and it seems it's more appropriate to do the following (https://istio.io/docs/examples/advanced-gateways/wildcard-egress-hosts/):
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: googleapis
spec:
  hosts:
  - "*.googleapis.com"
  ports:
  - number: 443
    name: tls
    protocol: TLS
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: googleapis
spec:
  hosts:
  - "*.googleapis.com"
  tls:
  - match:
    - port: 443
      sniHosts:
        - "*.googleapis.com"
    route:
    - destination:
        host: "*.googleapis.com"
        port:
          number: 443

So do I, but I'm still unable to make my script working to communicate with Google APIs, I directly get this error from the Google library:
{ Error: read ECONNRESET
    at _errnoException (util.js:992:11)
    at TLSWrap.onread (net.js:618:25) code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read' }

Note that by connecting through SSH to my pod, I'm able to run the following and get content of the page:
curl https://www.googleapis.com
Do you have any idea what's missing to make it working please?
By looking at Istio 1.1 changelog I don't see what could have broken my Istio settings 🤔
Thank you,

I tried to recreate your situation using Istio 1.1.1.  Before applying any Istio rules I did curl -v https://www.googleapis.com and got a "curl: (35) Unknown SSL protocol error".
I then applied this rule:
cat <<EOF | kubectl apply -f -
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: googleapis
spec:
  hosts:
  - "*.googleapis.com"
  ports:
  - number: 443
    name: tls
    protocol: TLS
EOF

After application, the same curl gave a 404 as expected.

Thanks @esnible for testing :) . But as I mentioned, after applying this ServiceEntry I'm indeed able to use the curl command from my Node.js pod. But the official Google APIs library that is run inside my JavaScript is not able to do is job while having the Envoy sidecar.
I don't understand why I'm having this kind of error (ECONNRESET) since I'm allowed all communcation with *.googleapis.com. Maybe some communications are still blocked by Istio?
How could I see each pod attempts that are catched by my sidecar? Like that I would be able to know which remaining domain is blocked to use Google APIs.
Thank you,
Note: it's working great without the sidecar

A great deal of logic is involved when pods communicate on port 443.  The application manages HTTP/TLS.  Envoy must peer into the encrypted traffic a little bit using SNI and make sure the traffic is passed unmodified to the correct destination.  This is tricky because there might be multiple destinations, and if any destination on port 443 doesn't have SNI in it's Istio rule it might capture some of the traffic.
First, verify everything works by testing that the Istio sidecar itself can reach the external service:
MYPOD=…
EXTERNAL_HOST=www.googleapis.com # or whatever
EXTERNAL_IP=$(nslookup $EXTERNAL_HOST | awk '/^Address: / { print $2 ; exit }')
HPATH=
PORT=443
kubectl exec $MYPOD -c istio-proxy -- curl -v https://$EXTERNAL_HOST/$HPATH --resolve "$EXTERNAL_HOST:$PORT:$EXTERNAL_IP" --insecure

Next, see what Envoy is logging about the failed connection following the example at https://istio.io/docs/tasks/telemetry/logs/access-log/ .  If Envoy is reporting that the certificates don't match it means that some other ServiceEntry or VirtualService on port 443 is getting the traffic.  Try adding SNI entries to the other rules to restrict what kinds of communication they manage.

Hi @esnible ,
After upgrading to 1.1.4 the work disappeared. I'm sorry I'm not able to explain why, I didn't modified the settings.
So now I'm able to reach Google APIs endpoints even without specifying any VirtualService with outboundTrafficPolicy.mode: "REGISTRY_ONLY". But it means there is no restriction because all my microservices can reach Google APIs.
How could could I restrict that?
I tried to "scope" a VirtualService with sourceLabels but it doesn't seem to cancel the authorization for all:
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: googleapis-sheet-api
  namespace: XXXXXXXX
spec:
  hosts:
  - "*.googleapis.com"
  tls:
  - match:
    - sourceLabels:
        app: app
      port: 443
      sni_hosts:
      - "*.googleapis.com"
    route:
    - destination:
        host: "*.googleapis.com"
        port:
          number: 443

Any idea please?
Thank you,

I suspect you are in a situation where Istio is configured in the newer version to allow external traffic by default.  See https://istio.io/docs/tasks/traffic-management/egress/#change-to-the-blocking-by-default-policy

As mentioned I use outboundTrafficPolicy.mode: "REGISTRY_ONLY", I just checked with kubectl get configmap istio -n istio-system -o yaml and this setting is present.
It seems according to https://github.com/istio/istio/issues/9477 that's something other people has already experienced.

So you have a service entry for googleapis and want to restrict it to only a certain namespace?
You probably want to use exportTo: . otherwise it is visible to all namespaces by default https://istio.io/docs/reference/config/networking/v1alpha3/service-entry/

Issue hasn't had any followup in 3 months, presumed fixed with exportTo. Feel free to reopen in not


Move holland into a venv

What version (commit) do you encounter this issue on?
master
What type of issue is this (bug, feature, documentation, regression)?
enhancement
What is the expected behavior?
Holland is run from a venv
What is actually happening?
Holland is installed directly in the galera containers
What were you attempting to do when you encountered this error (give as much detail as possible)?
N/A
How can we reproduce this issue?
N/A
How can we verify your issue is addressed?
Holland is contained within a venv
If this is a large issue, what can be done immediately to alleviate the issue while working on a longer-term solution?
N/A
What is your evaluation on the importance of this issue, and why?
Low. There are no known issues caused by this. This creates a layer of separation between the Python packages required by Holland and those that are required by the OSA galera containers.
What branches / milestones do you believe this issue should target?
The list below is what is currently supported for backports
Remove branches (lines) you do not wish to target.

[ ] Master

DocImpact: This section is to be completed by the issue owner as part of the issue's resolution.
Does your change require documentation?

[ ] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[ ] No documentation required for this change

We need to wait for https://github.com/rcbops/jenkins-rpc/pull/620 to merge before we can unblock this


ECO-482: Reject request when user has changed the active key when signing

Overview
The signer could change active key when approving, but deployHash is bind to the last active key, so we need to show users a message that he needs to resend the request.  And the related updates in Explorer is included in https://github.com/CasperLabs/CasperLabs/pull/2109.
back and forward compatibility
Both are supported.
If users use old version plugin and Clarity from this branch, Signer just ignores the second argument(publicKeyBase64).  Because in JavaScript:
const f = (a)=> console.log(a);
f("h", "e") // print 'h' and doesn't throw error.

If users use the plugin from this branch and Clarity without updates, the second argument(publicKeyBase64) is undefined, the plugin won't check and works as before.
Which JIRA ticket does this PR relate to?
https://casperlabs.atlassian.net/browse/ECO-482
Complete this checklist before you submit this PR

[X] This PR contains no more than 200 lines of code, excluding test code.
[X] This PR meets CasperLabs coding standards.
[X] If this PR adds a new feature, it includes tests related to this feature.
[X] You assigned one person to review this PR.
[X] Your GitHub account is linked with our Drone CI system. This is necessary to run tests on this PR.
[X] Do not forget to run bors r+ if GitHub policy is not enforced, e.g. when merging into another feature branch. It may be omitted under some circumstances if this PR intentionally assumes that integration tests will fail but will be fixed with the future PRs.

Notes
Optional. Add any notes on caveats, approaches you tried that didn't work, or anything else.

bors r+


Improve error message for negative any_instance spy expectations

Fixes https://github.com/rspec/rspec-expectations/issues/920

Thanks! Merging as build failure is an error on appveyor.

Doh, after merging this I realised theres a typo in the spec, fixed in #1232.

Oh, sorry.
I've tested on the example https://github.com/rspec/rspec-expectations/issues/920 and overlooked the specs. Next time I'll be more careful


Add check against non-array cursor selector for @branch

If you pass something else than an array to @branch, it will yield Uncaught TypeError: value.some is not a function. It would be a good idea to check against this early on (Array.isArray?) and give warnings for failing selectors.

That's weird. I thought I covered this case already. It seems I missed something. I start investigating.

Wait, what do you mean by passing an array to @branch? You're supposed to pass an object to it.

The situation was like this:
@branch({
  cursors: function() {
    return {
      lane: ['lanes', this.props.index],
      something: {...} // -> crash because Object doesn't have `some`
    };
  }
})
...

Ok, thanks. I think baobab 1.0.1 should handle the problem thusly now: you can pass as a cursor anything you could pass as first arg to .get or .select. So your object will be considered as a descriptor object filtering an array and should not throw.
But I'll test that just to be sure.

This should now be fixed.


Support arm64 architecture docker image

What changes were proposed in this pull request?

add Dockerfile-arm for Geaflow image
update mysql version, reduce the size of the image: Geaflow-console-arm

How was this PR tested?

Tests have Added for the changes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.鸑鷟 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

LGTM


Possible trigger view bug (Maybe)

When creating a trigger in the actions settings page, the newly created trigger is not visible, although it is working (tried it on pipedream).

fixed in https://github.com/saltcorn/saltcorn/commit/68f4ddb91c78170b167779764920bc920d1e02ee


Ping can't work after customizing Flatcar with Ignition

Description
Ping can't work after customizing Flatcar with Ignition
Environment and steps to reproduce

Set-up: ESXi 6.7GA, Flatcar 2345.3.0 vm

Steps to reproduce:
1)Create a Flatcar vm.
2)Before the first power on, edit its vmx file as this:
adding:
guestinfo.coreos.config.data.encoding = "base64"
guestinfo.coreos.config.data= "ewogICJpZ25pdGlvbiI6IHsgInZlcnNpb24iOiAiMi4wLjAiIH0sCiAgICJuZXR3b3JrZCI6IHsKICAgICJ1bml0cyI6IFt7CiAgICAgICJuYW1lIjogIjAwLWVuczE5Mi5uZXR3b3JrIiwKICAgICAgImNvbnRlbnRzIjogIltNYXRjaF1cbk5hbWU9ZW5zMTkyXG5cbltOZXR3b3JrXVxuQWRkcmVzcz0xMC4xMTcuMTYuOThcbkdhdGV3YXk9MTAuMTE3LjE3LjI1M1xuRE5TPTEwLjExNy4wLjFcbk5ldG1hc2s9MjU1LjI1NS4yNTQuMCIKICAgIH1dCiAgfQp9Cg=="
3)Power on the vm.
Note: above data for guestinfo.coreos.config.data is the base64 encoding for:
{
"ignition": { "version": "2.2.0" },
"networkd": {
"units": [{
"name": "00-ens192.network",
"contents": "[Match]\nName=ens192\n\n[Network]\nAddress=<IP_ADDRESS>\nGateway=<IP_ADDRESS>\nDNS=<IP_ADDRESS>\nNetmask=<IP_ADDRESS>"
}]
}
}

Expected behavior
Customized IP takes effect and network can work normally.
In fact, customized IP takes effect but network is not available.

Thank you for your report. We are aware of this issue and fixed it recently: https://github.com/flatcar-linux/scripts/pull/53
The fix has not been released yet; it will be part of the upcoming release. The next release is tracked in https://github.com/flatcar-linux/Flatcar/issues/54 .

Update ignition version as 2.2.0, and it still failed.

Sorry that we didn't have a look at this issue earlier. Recently we updated the docs to include an example with static IP addresses and other related information: https://docs.flatcar-linux.org/os/booting-on-vmware/#container-linux-configs
I'm not sure if your networkd config is correct. Do you still have the issue? What output does ip route and networkctl give you when you log in on the VGA console?
Can you try to use a networkd unit content similar to the example in the docs (i.e., separate [Address] section and a /subnet size in the Address and a [Route] section with a Destination)?

Closing this as stale, please reopen if needed.
As written in the docs, this is what should work (here both private and public IP addresses are used, only one would also work):
[Match]
Name=ens192
[Network]
DHCP=no
DNS=<IP_ADDRESS>
DNS=<IP_ADDRESS>
[Address]
Address=<IP_ADDRESS>/29
[Address]
Address=<IP_ADDRESS>/29
[Route]
Destination=<IP_ADDRESS>/0
Gateway=<IP_ADDRESS>
[Route]
Destination=<IP_ADDRESS>/8
Gateway=<IP_ADDRESS>

Closing this as stale, please reopen if needed.
As written in the docs, this is what should work (here both private and public IP addresses are used, only one would also work):
[Match]
Name=ens192
[Network]
DHCP=no
DNS=<IP_ADDRESS>
DNS=<IP_ADDRESS>
[Address]
Address=<IP_ADDRESS>/29
[Address]
Address=<IP_ADDRESS>/29
[Route]
Destination=<IP_ADDRESS>/0
Gateway=<IP_ADDRESS>
[Route]
Destination=<IP_ADDRESS>/8
Gateway=<IP_ADDRESS>

It doesn't work, please reopen this issue. Thanks a lot.

BTW, I tested it with 2765.2.0.

So, could you please tell us what output does ip route and networkctl give you when you log in on the VGA console?
Also, could you please show the config that you used in your last test?
Thanks.

My configurations are as below:
[Match]
Name=ens192
[Network]
DNS=<IP_ADDRESS>
[Address]
Address=<IP_ADDRESS>
Netmask=<IP_ADDRESS>
[Route]
Gateway=<IP_ADDRESS>
After customization, I got:

Repost.

Can you please try if adding DHCP=no under [Network] and adding the right Destination=… under [Route] makes a difference?

Can you please try if adding DHCP=no under [Network] and adding the right Destination=… under [Route] makes a difference?

Sorry for the late response.
For below configuration,
{
  "ignition": { "version": "2.0.0" },
   "networkd": {
    "units": [{
      "name": "00-ens192.network",
      "contents": "[Match]\nName=ens192\n\n[Network]\nAddress=<IP_ADDRESS>\nGateway=<IP_ADDRESS>\nDNS=<IP_ADDRESS>\nNetmask=<IP_ADDRESS>\nDestination=<IP_ADDRESS>\nDHCP=no"
    }]
  }
}
it didn't work. ip route and networkctl got the same results.

Verified it with 3139.2.0, it works. Thanks a lot.

Closing this as stale, please reopen if needed.
As written in the docs, this is what should work (here both private and public IP addresses are used, only one would also work):
[Match]
Name=ens192
[Network]
DHCP=no
DNS=<IP_ADDRESS>
DNS=<IP_ADDRESS>
[Address]
Address=<IP_ADDRESS>/29
[Address]
Address=<IP_ADDRESS>/29
[Route]
Destination=<IP_ADDRESS>/0
Gateway=<IP_ADDRESS>
[Route]
Destination=<IP_ADDRESS>/8
Gateway=<IP_ADDRESS>

It doesn't work, please reopen this issue. Thanks a lot.


Implementing a GraphQL server using Prisma, SQLite, and Nest.js with Typescript

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.
[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This Fixes #2717

Hi @JuliusGikonyoNyambura, I've started reviewing your article. Please don't make any changes since that might disrupt the review process.

@Dawe-7, I have added the changes.

@Dawe-7, I have added the changes.

plagiarism check done


Add docstrings for locale

Description
The 'locale' was added in various dashboards in RAI but no docstrings were added. Adding the missing docstrings .
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[ ] responsibleai/model-assessment

Python packages changed:

[ ] raiwidgets
[ ] responsibleai
[ ] erroranalysis
[ ] rai_core_flask

Tests

[ ] No new tests required.
[ ] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Documentation:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Codecov Report

Merging #1202 (760bcae) into main (f0f9c7f) will increase coverage by 7.89%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1202      +/-   ##
==========================================
+ Coverage   67.69%   75.58%   +7.89%
==========================================
  Files          90       10      -80
  Lines        4296      258    -4038
==========================================
- Hits         2908      195    -2713
+ Misses       1388       63    -1325

Flag
Coverage Δ

unittests
75.58% <ø> (+7.89%)
:arrow_up:

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

Impacted Files
Coverage Δ

raiwidgets/raiwidgets/error_analysis_dashboard.py

raiwidgets/raiwidgets/explanation_dashboard.py

raiwidgets/raiwidgets/fairness_dashboard.py

raiwidgets/raiwidgets/model_analysis_dashboard.py

...iwidgets/raiwidgets/model_performance_dashboard.py

raiwidgets/raiwidgets/responsibleai_dashboard.py

...sibleai/responsibleai/rai_insights/rai_insights.py

.../responsibleai/_managers/counterfactual_manager.py

...sponsibleai/responsibleai/rai_insights/__init__.py

...dgets/raiwidgets/error_analysis_dashboard_input.py

... and 70 more

Continue to review full report at Codecov.

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


Add documentation for trades for account endpoint

Ref #417
Closes #422

Let's wait until https://github.com/stellar/js-stellar-sdk/pull/167 is released.

Deployed.


when click on reload Gpu details card, it diappears.

Description

when there's error loading gpu card and i click reload, the dialog disappears.

Must include any relevant identifiers like:

Mainnet: https://dashboard.bknd1.ninja.tf/

Node ID: 780

Steps to reproduce

open https://dashboard.bknd1.ninja.tf/
navigate to dedicated machines
filter with GPU Node

Logs/Alerts
Screencast from 01-30-2024 12:37:36 PM.webm

Verified, Devnet 9280a08.
The retry doesn't disappear anymore, and I could keep pressing until it works.
screen-capture (1).webm


Facebook app-scoped user ids may break posse-post-discovery for new accounts

This only applies to Bridgy accounts created after the switch to the 2.0 API.
Bridgy gets a list of my posts, e.g.
https://www.facebook.com/[app-scoped user id]/posts/10101237953173839
Checks my homepage h-feed and finds a post that connects to
https://www.facebook.com/[global user id]/posts/10101237953173839
which will never match each other. Really ppd already didn't work super great for Facebook because they serve the same content at several different URLs (substituting username for id for example), and u-syndication could point to any of them.
Just thinking about this, I haven't actually encountered it yet that I know of.

huh. true! great point. and i don't really see a way around it either. facebook support continues to crumble day by day. :/ cc #350
we actually try pretty hard to handle many varieties of facebook post URLs, including photos and username vs ids, but it's an arms race that we obviously can't invest in as heavily as they can. ah well. :P

Mmm... This may be why I have yet to see Bridgy detect any replies or likes on my Facebook.

@nekr0z this shouldn't affect you. Your Facebook posts have a "See Original" link at the bottom, so the posse-post discovery fallback mechanism shouldn't come into play.
I just looked, and Bridgy somehow does not have the "user_posts" permission for your account. I know you just revoked and reauthorized a couple days ago, would you mind trying again (You should just be able to click the Facebook button on https://brid.gy). When I do it, it prompts me for the permissions "Bridgy will receive the following info: your News Feed, status updates, events, photos and website.". Double check that you are seeing the same?

@kylewm I've just re-wired Bridgy with Facebook again. In my case upon reauthorization the info about permission was in Russian, so no use in including it verbatim, but itonly mentioned public profile and website, and didn't mention updates, photos or events.

FB has now auto-assigned usernames to all users, and it redirects post URLs  in the browser to always use username instead of user id (whether global or app-scoped). due to that, we started inferring FB usernames in #447/#448, which is currently working well.
that should handle syndication URLs that are copy/pasted into a CMS by users. for posts that are  POSSEd programmatically, FB just returns the post id, so if any CMSes are constructing FB post URLs with user id instead of username, i guess we can lean on them to switch.
(there are also URLs that don't use user id or username, e.g. /photo.php?fbid=... and /story.php?story_fbid=..., but those don't have this problem in the first place.)
so, given all that, i think we can close this. if anyone disagrees, feel free to reopen!

, so if any CMSes are constructing FB syndication URLs with user id instead of username, i guess we can lean on them to switch.

I am apparently!

ahahahahahahaha
...but you didn't hit the bug because you authed both the bridgy and redwind FB apps before api v2.0, so both of them have your global user id. (you successfully get backfeed from FB, e.g. https://kylewm.com/2015/10/reading-https-en-wikipedia-org-wiki-steganography )

Cool that makes sense.
FWIW, Bridgy Publish uses user id too...
It turns out I don't really know the right way to get a post permalink from the ID the API returns! Part of Facebook's war on URLs.

FB has now auto-assigned usernames to all users, and it redirects post URLs in the browser to always use username instead of user id (whether global or app-scoped)

As far as I can tell, it does not redirect anymore, whether logged in or out, e.g. https://www.facebook.com/12802152/posts/10101645114169939 ... They probably realized this was a leak and plugged it.
So I don't think there is a good way to determine the username of a user... Known's FB plugin cannot do it; silo.pub has a configuration option where you can manually enter your username.
I'd like to explore the possibility of expanding inferred_username to include inferred usernames and possibly many inferred user IDs.

sure! i've noticed the same decrease in redirecting, btw. maybe i overstated it originally; not sure.
regardless, inferring user ids sgtm. we'll see some edge cases with people who have FB pages and bleed their posseing across their user and the page, but shouldn't be a big problem, and I'm fine if we start out simple and dumb and handle those if/when we see them.
I'd probably lean toward a new inferred_user_ids field instead of overloading inferred_username, but I'm probably getting ahead of myself. thanks for looking into this!

(related discussion in #650)

so @kylewm now that we infer both usernames and user ids, do you think we should close this?

I do! Thanks for the reminder, I'd intended to close it as soon as we confirmed it worked.


Add a change to dark theme feature on navigation for both mobile and desktop views.

You can refer to this link https://mui.com/customization/dark-mode/#toggling-color-mode to get information on implementing dark mode toggle with material UI. Make sure to use same Icon Transition in the link mentioned.
No need to use some global state management library as prop drilling won't affect the performance that much, because the Navigation component is the immediate child of App component.

Hi @TheNinza,
I would like to work on this issue.
If you assign me this issue, can I add the theme toggler to the right side of the navbar beside navlink.

hey @BelideNikhil , I appreciate your response, but currently this issue is there for helping our college students to get familiar with open source. So if I get no response from anyone till tomorrow, I will assign this to you.

@TheNinza sir i want to work on this issue

sure @Manoramsharma , go ahead....

@TheNinza sir any new module is not getting recognized by App.Jsx , why is its so ?

@TheNinza, getting the following error for implementing the given theme Icon Transition.
<EMAIL_ADDRESS>Module not found: Can't resolve '@mui/material/utils' in 'C:\Users\HP\Desktop\New folder\dsa-visualizer\node_modules@mui\icons-material\utils'

Basic switch base transition is done already.

You can change the switch to logo that is here https://mui.com/customization/dark-mode/#toggling-color-mode
It will be a better representation for the action.
Also about that error.... it looks like that you are missing the dependency. Install it with npm

Hey @TheNinza ,
I want to work on this.


Optional flags

Thanks for this great tool!
On the current main branch https://github.com/nesnes/teleplot/commit/493b8665d081d8c8b62e887468590db4524a95a1
By reading the doc I don't understand what the |g value corresponds to for the optional E field.

E is containing flags that carry information on how to read and display the data.

Is it still necessary ?

Also i tried using the no plot option |np  but when I refresh the page the plots are still automatically added, does it work?
When i plotted some values in c++ using stringstream I had some values that were formatted with scientific unit 3.2323e-8 and it was detected as a text so no chart was availble.  Is it mandatory to format with fixed floating point?

It can be solved on the client side with some flags, maybe we can add this to the doc ?
std::stringstream ss;
ss << std::fixed;
ss.precision(4);

Hi,
The G flag
The g flag is historical and should not be required (it was an attempt to comply with statsd but this is something that's being progressively dropped. Actually echo "myData:4" | nc -u -w0 <IP_ADDRESS> 47269 is a valid packet.
The np flag
The np flag should be working, make sure to group all the flags after a single |.
All the exemples bellow are valid:

echo "myData:4|g" | nc -u -w0 <IP_ADDRESS> 47269
echo "myData:4|g,np" | nc -u -w0 <IP_ADDRESS> 47269
echo "myData:4|gnp" | nc -u -w0 <IP_ADDRESS> 47269
echo "myData:4|npg" | nc -u -w0 <IP_ADDRESS> 47269

The scientific notation
The scientific notation should be considered as a number, not a string. This seems to be a side effect of the recently added string support. Teleplot is currently being actively improved so we can expect a few bugs like this to occur. this will be fixed very soon along with a stabilization of the 3D shapes protocol thanks to the great work of @Maximilien22 !

Thanks for feedback, I did some more tests and np actually works my bad.
Do you want me to keep sending feedback :)
I was wondering if we could add support for a binary serialization to have a more efficient transport ?


add StatelessSession.getIdentifier() because repositories need it

This was already added to ORM SS in 6.6. See #2040.

Thanks for adding this.
Next time, could you please reference the issue in the commit messages before merging it, please?

Oh c'mon man, I really am very busy and sometimes I need to optimize my use of time.

Well... next time don't merge it, so I can update it myself before merging it. This will save you even more time.


CC 93 fix buffer dpi

This fixes issue https://github.com/CodingTrain/website/issues/574 - CC 93 (p5.js version)'s buffer size for high DPI screens. I tested it on Surface Pro 4 (175%).

side note: with this fix, the buffer looks blurry as @shiffman pointed out. Better solution is this
function setup() {
  createCanvas(500, 300);
  a1 = PI / 2;
  a2 = PI / 2;
  cx = width / 2;
  cy = 50;
  let n = pixelDensity();
  buffer = createGraphics(width*n, height*n);
  buffer.background(175);
  buffer.translate(cx, cy);
}

but I found it a bit less intuitive (although it makes crisp lines)

@shiffman Should I resolve conflicts and merge?

@nilsweb sure, yes, thank you!

@nilsweb this was solved in #737


Application fails to launch throwing the following error

The plugin `extended_shared_preferences` doesn't have a main class defined in C:\Users\user\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\extended_shared_preferences-1.0.0\android\src\main\java\com\connapptivity\developer\sharedpreferences\SharedpreferencesPlugin.java or C:\Users\user\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\extended_shared_preferences-1.0.0\android\src\main\kotlin\com\connapptivity\developer\sharedpreferences\SharedpreferencesPlugin.kt. This is likely to due to an incorrect `androidPackage: com.connapptivity.developer.sharedpreferences` or `mainClass` entry in the        plugin's pubspec.yaml If you are the author of this plugin, fix the `androidPackage` entry or move the main class to any of locations used above. Otherwise, please contact the author of  this plugin and consider using a different plugin in the meanwhile.
If this is an error on my side, I will remove this, but for time being, I'm submitting this as on isse. The application fails to buils throwing the following error. Please look into this asap.

This issue happened due to a wrong config in pubspec.yaml. I think it is solved and will close this thread, but feel free to reopen if the error still occurs. Feel also free to fork, solve errors and make a pull request, since this is free for everybody.
Best regards
Marlo

Can you tell how this issue was fixed? Please tell the correct pubspec.yaml configuration. I have another issue opened for this.


JS impl of Array.OfSize should assert size<runtime.maxArraySize

There is a documented assertion, it should be implemented. @chochos can you look at this please?

Excellent, thanks.


Feature | db based on diagram

🚩We have made the following changes to complete Vet Clinic - Create db based on a diagram
Here is a summary of what has been done
Type of files changed/added
, PNG
In this new Branch, We have ➕ADDED➕ the succeeding *📂 folders and/or **📄 files to complete this milestone's requirements
*📂 root/

**📄 schema_based_on_diagram ➕

We have added the schema based on the diagram following the above requirements.

**🖼 clinic_diagram.png ➕
- We have added the diagram ERD.

We have ✏MODIFIED✏ the succeeding *📂 folders and/or 📄** files
*📂 root/

**📄 README.md ✏

We have modified the documentation to add author 2 @mwismann.

**📄 LICENSE ✏

We have added @mwismann.

Thank you for taking the time to review this PR ⭐

If you require additional information or have any questions, please contact me on Slack as Arturo (Arthur) Emanuel Guerra Iturres, Mathías Wismann We'll be happy to help you out. 🎯

Hi @Strangeal Justice! cheers for the approval! 💯 Wish you guys a great week!


launch.json args not working for a python module with active virtualenv

I hope that if I'm doing something wrong then someone can spot it, I haven't been able to get an answer elsewhere.

VS Code Version: Version: 1.60.2 (Universal)
OS Version: Mac/OSX, Darwin x64 19.6.0

I'm having the same problem talked about here https://github.com/Microsoft/vscode/issues/2167 but I'm not making the error that this user was.
I have a Python module called __main__.py that I want to run in VScode's debugger. The full path of this is ~/Code/APPRES-483/cqs/update-query-definition/__main__.py. The module uses a virtualenv located at ~/Code/APPRES-483/venv-cqs. I have it active in my vscode terminal.
Here's the command I would be using to run the script in a normal terminal: python3 . --verbose --file-to-write ../../LOCAL-query-definition.yml
This is my launch.json file
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Module",
            "type": "python",
            "python":"${env:HOME}/Code/APPRES-483/venv-cqs/bin/python",
            "request": "launch",
            "module": "__main__",
            "args":[
                "--verbose",
                "--file-to-write", "/../../LOCAL-query-definition.yml"
            ],
        }
    ]
}

When I try to run the debugger, I see this in my terminal:
cd /Users/bineyb/Code/APPRES-483/cqs/update-query-definition ; /usr/bin/env /Users/bineyb/Code/APPRES-483/venv-cqs/bin/python /Users/bineyb/.vscode/extensions/ms-python.python-2021.9.1246542782/pythonFiles/lib/python/debugpy/launcher 50826 -- -m __main__ --verbose --file-to-write /../../LOCAL-query-definition.yml
debugpy 1.4.3
See https://aka.ms/debugpy for documentation.

Usage: debugpy --listen | --connect
               [<host>:]<port>
               [--wait-for-client]
               [--configure-<name> <value>]...
               [--log-to <path>] [--log-to-stderr]
               <filename> | -m <module> | -c <code> | --pid <pid>
               [<arg>]...

Error: unrecognized switch --verbose

The first argument always causes this error message, "error unrecognized switch". I can't find out what's going wrong.

Please file this issue on the vscode-python extension's repo: https://github.com/microsoft/vscode-python/issues


Try to fix CI for CellWindow tests

Codecov Report

Merging #95 (6213474) into main (f685433) will increase coverage by 1.63%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##             main      #95      +/-   ##
==========================================
+ Coverage   73.41%   75.05%   +1.63%
==========================================
  Files          28       28
  Lines        1422     1431       +9
  Branches      189      190       +1
==========================================
+ Hits         1044     1074      +30
+ Misses        302      279      -23
- Partials       76       78       +2

Impacted Files
Coverage Δ

...poselife/ui/util/CustomTransformGestureDetector.kt
75.47% <75.00%> (+24.45%)
:arrow_up:

.../kotlin/com/alexvanyo/composelife/ui/CellWindow.kt
72.44% <100.00%> (+12.23%)
:arrow_up:

Continue to review full report at Codecov.

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


[SMALLFIX] dependency version label

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12589/
Test PASSed.


API design suggestion

s2n-quic's API uses the method chaining paradigm, which is - dare I say - often implemented poorly, and I believe s2n-quic is one of them.
The current design works fine if the caller wants to just hardcode (almost) everything, like in the examples, but what if the caller want something configured at runtime?

let's see the example of .with_gso_disabled(), the caller would need to write something like:

let mut builder = Builder::new();
if !args.gso {
    builder = builder.with_gso_disabled();
}
let server = builder.build();

which does not really conform to the method chaining paradigm.
and it doesn't work for some methods since the method might return a different type, which I gave an example here: https://users.rust-lang.org/t/a-question-about-method-chaining-with-different-return-types/104196
I think a better design would be a .with_gso() method that takes a bool value (or a enum with auto|force_on|force_off or something like that), like this:
let server = Server::builder()
    .with_gso(args.gso)
    // ...
    .start();

some methods, like the .with_congestion_controller() looks like it works like that, but since Cubic and Bbr are actually different types, we can't really do this:

builder.with_congestion_controller(if args.bbr {Bbr::default()} else {Cubic::default()}) ...

Sorry for the critical tone and strong wording.
And it's also entirely possible that it's just that my rust-fu is too weak, and this problem is entirely solvable from the caller side, if then, my sincere apologies and please show me how.

Thanks for the suggestions! I've implemented the first item in #2091.
For the second item, it's a bit trickier. But I think if you're ok with doing runtime dispatch, then we can provide a helper enum that forwards the congestion controller methods on to the correct impls. I've opened #2092 to track that.

The work to ergonomically switch CC is being tracked in https://github.com/aws/s2n-quic/issues/2092


Fix text-to-speech formatting issues

Strip unpronounceable Unicode
"degress F" should be "degrees Fahrenheir"
...

What? You think I have time on my bus ride to actually get this done!?
On Sunday, March 13, 2016, strugglingcomic<EMAIL_ADDRESS>wrote:

Strip unpronounceable Unicode
"degress F" should be "degrees Fahrenheir"
...

—
Reply to this email directly or view it on GitHub
https://github.com/strugglingcomic/CeruleanSmock/issues/2.


[Feature request] Switch or toggle between collections easily

Would love a feature where I can switch between collections easily.
I would imagine something like an icon next to the title of the collection, which upon clicking would give me the dropdown of the list of all collections that I have, and I can switch to a particular collection by clicking one among the dropdown items.
Can elaborate more if required.

@helloanoop If this sounds reasonable, I can try working on this change sometime today or tomorrow.

Hi, I think this feature could be great :)
something like workspace in Postman or "Working set" in Eclipse with multiple possible selection

@UnleashSpirit Tbvh, I wasn't really thinking of something like workspaces or working sets. But that would be cool to have too.
What I was mainly addressing is that currently if someone wants to switch to a different request in a different collection, he/she has to traverse through the collection tree on the sidebar and select the particular request (multiple mouse clicks). Instead if I could get a dropdown at the top (naive example below), it makes it a bit easier to switch - hopefully with just a single mouse click.


No issue, just a thanks

I've been struggling to bind my tx16s to the nrf24l01 for months and your library did the trick! Thanks a ton.

Thank you very much for your feedback, it's nice!


Get the Text pronounce by the user

hello!
I tried to get the text that is pronounce by the user but with the promise of the function start i only get a reference to an Ljava.lang.Object  so i'm unable to use it.
Is-it a bug?

i found a way to make it work by replacing  in speech-recognition\android\src\main\java\com\getcapacitor\community\speechrecognition\SpeechRecognition.java line 163 by :  result.put("matches", matchesList != null ? new JSArray(matchesList.toArray()) : new JSArray());

@Zarukin which version you use?

the package is in 0.0.4

The master branch work with Android and iOS.
Will be release a new version shortly!

ok thanks for your help. I will keep an eye on it! :)

Before becoming a collaborator I had released my own version on npm.
If you want to try use this -> https://www.npmjs.com/package/@mrbatista/speech-recognition (it's the same code as this repository in the master branch)


Add icon for .vagrant directory

There is already icon for Vagrantfile so I added the same icon for .vagrant directory

Thanks!


Evaluate schema transform expressions during ingestion

This PR adds the feature to execute transform functions written in the schema. This transformation will happen during ingestion. Detailed design doc listing all changes and design: Column Transformation during ingestion in Pinot.

Changes mainly are:

transformFunction can be written in the schema for any fieldSpec using Groovy. The convention to follow is:
"transformFunction": "FunctionType({function}, argument1, argument2,...argumentN)"
For example:
"transformFunction" : "Groovy({firstName + ' ' + lastName}, firstName, lastName)"
The RecordReader will provide the Pinot schema to the SourceFieldNamesExtractor utility to get source field names.
RecordExtractor interface is introduced, one per input format. The RecordReader will pass the source field names and the source record to the RecordExtractor, which will provide the destination GenericRow.
The ExpressionTransformer will create ExpressionEvaluator for each transform function and execute the functions.
ExpressionTransformer will go before all other RecordTransformers, so that every other transformer has the real values.

I'll be happy to break this down into smaller PRs, if this is getting too big to review.
I'm finding it hard to break this down, because the AvroRecordExtractor is already used in realtime decoders
Pending

Add transform functions in some integration test
JMH benchmarks

Some open questions

We no longer know the data type of the source fields. This is a problem in CSV and JSON.
CSV
a) Everything is read as String, right until the DataTypeTransformer. The function will have to take care of handling the type conversion.
b) Cannot distinguish between MV columns of single value vs single value column. Function will have to take care
c) All empty values will be null values. Cannot distinguish between genuine “” and null in String
JSON
a) Cannot distinguish between INT/LONG and DOUBLE/FLOAT, until DataTypeTransformer.
What should we do if any of the inputs to the transform function is null? Currently, it is skipped. But should we make it the responsibility of the function to handle this?
KafkaJSONDecoder needs to create JSONRecordExtractor by default. But we cannot access JSONRecordExtractor of input-format module in the stream-ingestion module. Did not face this problem in Avro, because everything is in input-format
Before ExpressionTransformer, the GenericRecord contains only source columns. After ExpressionTransformer, the GenericRecord contains source + destination columns, all the way up to the indexing. Should we introduce a Transformer which will create new GenericRecord with only the destination columns, to avoid the memory consumption by the extra columns?

Will be nice if we can completely decouple schema from RecordReader and RecordExtractor, which will make future development much easier

It's already decoupled from RecordExtractor. Do you mean pull up the schema even more, such that RecordReader also doesn't need Schema? What would we achieve by doing that?

Will be nice if we can completely decouple schema from RecordReader and RecordExtractor, which will make future development much easier

It's already decoupled from RecordExtractor. Do you mean pull up the schema even more, such that RecordReader also doesn't need Schema? What would we achieve by doing that?

@npawar RecordExtractor is for stream ingestion, and RecordReader is for batch ingestion. Think of some users trying to add a new record reader, they don't need to understand what schema is, they only need to know here are the fields that should be read.

Will be nice if we can completely decouple schema from RecordReader and RecordExtractor, which will make future development much easier

It's already decoupled from RecordExtractor. Do you mean pull up the schema even more, such that RecordReader also doesn't need Schema? What would we achieve by doing that?

@npawar RecordExtractor is for stream ingestion, and RecordReader is for batch ingestion. Think of some users trying to add a new record reader, they don't need to understand what schema is, they only need to know here are the fields that should be read.
This might be bigger change, so we can add a TODO and address it separately.

As per offline sync up, StreamMessageDecoder is the entry point for realtime, and RecordReader is the entry point for batch. The RecordExtractor is expected to be common to both of them. Picture in the design doc linked in the description.
And I've added a TODO in RecordReader class to further pull out Schema. For consistency, we should do the same in StreamMessageDecoder as well then. Since this is a bigger change, will leave it out for  the scope of this PR.

For the tests, can we hardcode more than one records to catch the problem such as ORC case?

The RecordExtractor tests are on more than 1 record

We missed to discuss the pros/cons of using Groovy on the design doc, apologies. One thing to note is that opening the door for executing an external script/code is a security risk. For example, we need to protect against malicious intent such as System.exit(), while (true), forced OOM, etc. Some of these can be prevented by using Protected/Priviliged mode in Groovy. But we should consider whether there are easier alternatives that don't require inventing another DSL.

We missed to discuss the pros/cons of using Groovy on the design doc, apologies. One thing to note is that opening the door for executing an external script/code is a security risk. For example, we need to protect against malicious intent such as System.exit(), while (true), forced OOM, etc. Some of these can be prevented by using Protected/Priviliged mode in Groovy. But we should consider whether there are easier alternatives that don't require inventing another DSL.

Let's continue the discussion on the design doc. We can always remove the Groovy function type if we decide against it. The rest of the changes should remain the same.
Regarding Protected/Privileged mode - can you point me to some docs, I can't seem to find what you're referring to.

https://github.com/apache/incubator-pinot/issues/5135

Yes, splitting it into a couple of PRs may help -- since you offered. Perhaps starting with the record extractor, but you decide.
Regarding your open questions:
1 . We face this problem because json and csv dont have any schema. Should we introduce the concept of an input schema ? Should we pick the schema from the first record? (what if it has null for some field, and we find the field later? Should we dictate that the first record MUST have all the fields they ever expect to see in the input, and take that to be the schema? Just adding some ideas for consideration. Some related discussion in PR #4968
InputSchema seems like the cleanest solution. But that's more configuration and more scope for error for the user. Giving it more thought, I think the current implementation will work fine, because most often, the same input format will be used for all pushes to the same table. The problem arises only if someone keeps switching between input formats of the data.
2. Can we assume pinot defaults if input to transform function is null? This will work until we support more input types than pinot itself supports -- far-fetched I think.
Right now, I think the best way forward is to let the function handle it. The function definition will change only if someone uses data with different input formats to push to the same schema (if they use Avro once and it succeeds, but then they use CSV and the function fails) - which is not a common practical case.


make date selection slider more obvious

couple of options:

[ ] show date slider all the time and make date bars drap-droppable instead of current click-drag

like google finance
could be more touch-friendly
[ ] what should the initial state of the time selection be? last month/year?
[x] check if technically doable with current graphing library (vega)

or just

[x] add visual hints and/or help text to explain that the time bar is selectable and zoomable

//cc @felskia

I've now added a crosshair mouse cursor on the time/experience chart to indicate that there is something selectable there.
Ideally, I'd like to have the boundaries individually adjustable (like in http://square.github.io/crossfilter/), but as far as I can see that would more or less require rewriting the chart code from scratch. :unamused:

@tyrasd I think this is fine for now. I also think that having some kind of help button might be nice. I moved it around from the last comp I attached. But I think when you press the help button it would be nice if it pulled up a modal on what you can do on the site.


feat: merge beta

🧰 Changes
Merges beta into next!
🧬 QA & Testing

Broken on production.
Working in this PR app.

BREAKING CHANGE: This is a near complete rewrite of the library, and converts it to supporting MDX instead of markdown.

This PR was released!
🚀 Changes included in v6.88.0

(ooof, squash merging this caused us to loose all the linked PR-to-commit history from the last years worth of work on the beta branch… makes it real hard to track where/why certain changes were introduced.)

(ooof, squash merging this caused us to loose all the linked PR-to-commit history from the last years worth of work on the beta branch… makes it real hard to track where/why certain changes were introduced.)

Yea, a lot of the commits were poor quality though.


Warn when no camera exists to render an object

What problem does this solve or what need does it fill?
Beginners commonly attempt to get started with adding 2D/3D/UI graphics, forget to add a camera, and then are confused when nothing appears.
What solution would you like?
Warn when no camera of the appropriate type exists.
What alternative(s) have you considered?
Improve documentation further, especially in the Bevy book.
Additional context
The exact timing / details of when this should trigger need some work by others who understand the rendering pipeline more clearly.
We should also be careful not to create unsilenceable warnings in cases where the lack of camera may actually be intended.

From a comment I left in #1440:

I think my ideal solution is to make the UiCamera completely optional (and fall back to a default value). Most people don't need control over the UI camera, so theres no real reason to dictate one (other than the fact that its easier to require one because that behavior is consistent with the other render passes)

The same argument could be made for 2D render passes. But 3d has no "reasonable default", so it might make sense to warn if you try to draw a 3d object when there is no camera.

I am here because this issue is marked as a good first issue.
However, related items indicate that this issue is possibly resolved.
Is there any more work to be done here?

Hrm :thinking: The associated PR was closed because it added a check on each frame. The goal is to achieve a warning without using a system. I'll take a poke around, see what the current state is, and whether there might be a semi-obvious solution in 2024.

Well now you've added D-Complex 🙀 😆
I see UI is already warning about this via a system:

I'll see if there's anything else to be uncovered that doesn't mess with rendering too badly.

If it's taken 3 years and multiple attempts to fix I am forced to revise my estimation of difficulty upwards ;)

Yeah, I'm gonna call defeat on this one until I am more of an "expert" (or less of an ignoramus!)