Add Plugin download+install

Also

move plugins to PluginApi
add some new fields to the Plugin model

future enhancements:

create/ensure the download folder on startup, instead of API call
clean out the downloads folder on startup


[Draw an area] Dialog shown only after adding point, text incorrect

Screenshot pending
Expected:

Note: I was unable to reproduce the issue where the dialog would only show up when the first point was added but I noticed that we were determining the task visibility state by overriding setMenuVisibility() which was a deprecated in newer versions of Android (+28). I decided to refactor by using onResume() instead.


Failed to load module "canberra-gtk-module"

I've installed tomboy-ng through the .deb file in an "almost fresh" Ubuntu 18.04. Installation didn't showed any errors but when run from the launcher it doesnt show any new window. Running it from the terminal shows the following error:
~$ tomboy-ng
Gtk-Message: 19:25:41.263: Failed to load module "canberra-gtk-module"

Wow, I have never even heard of canberra-gtk-module.
I googled for it and seems there can be an issue if you have some 32bit software running on a 64bit machine.
Any chance you downloaded the 32bit version of tomboy-ng and are using a 64bit system ?
Mr Google suggests also installing the 32bit library but I'd rather see you using the 64bit tomboy-ng if that is the issue.
Worth noting that tomboy-ng has not been tested on 18.04 yet but I'd be very surprised if there is a comparability issue.....
Davo

Hi David, I'm positive I installed and ran tomboy-ng_0.14-0_amd64.deb from this github. I already reinstalled it by apt purge tomboy-ng and reinstalling it and it shows the same error.
Further testing the some install issues, I deleted the config files from my home dir and the program started with it's initial setup dialog. I set up a directory outside the home folder and the following error apears:
luis@lambda:~$ tomboy-ng  Gtk-Message: 13:56:09.661: Failed to load module "canberra-gtk-module" ERROR - File not found, cant read note change date for /mnt/sda5/Dropbox/Tomboy-ng Notes/0/116/ba80cc10-dc32-4937-b17e-677e39bd3b8c.note . . . <lots of other files, but same error>
I also tried using the default location for notes but still no window appeared other than that named KTomboy-NG Settings.

just a wild guess here ...
You say no window appears ?  Normally tomboy-ng does not show a window until you open a note, it keeps out of your way. Can you see the small system tray icon, bright green, probably top right of your screen ?
You interact with tomboy-ng all through that system tray icon.
The error you are seeing now (about missing files) somehow relates to you deleting the config files. I am wondering if you did that while tomboy-ng is still running ....
David

A little research, libcanberra seems to be there to play some sound effects, tomboy-ng does not make any sounds (afaik).  And ldd tells me that tomboy-ng does not call libcanberra itself in any way. Perhaps it calls another GTK library that, iin turns calls libcanberra ?   I have no idea why.
That being the case, if it does not cause tomboy-ng to crash (as seems to be the case?) you can safely ignore it.
The real issue is "is tomboy-ng actually running" and I suspect that may relate to you expecting to see a window pop up ?  My fault for not uploading any appropriate images of tomboy-ng running. Sorry !
Please look for that green system tray icon.....
Davo

Hi, David,
If your refer to an app indicator on the upper right corner on GNOME, there is none while tomboy-ng running. I am familiar with that icon since I am very accustome to the tomboy "classic"(?) icon. About libcanberra, this might indicate it is just a warning and not necessarily an error that might cause it not to run? I remember in some distros there was a similar problem with Dropbox indicator icon not appearing on some dark themes (which I am using adwaita-dark), requiring to change the running environment or something like that.

Hi, David,
If your refer to an app indicator on the upper right corner on GNOME, there is none while tomboy-ng running. I am familiar with that icon since I am very accustome to the tomboy "classic"(?) icon. About libcanberra, this might indicate it is just a warning and not necessarily an error that might cause it not to run? I remember in some distros there was a similar problem with Dropbox indicator icon not appearing on some dark themes (which I am using adwaita-dark), requiring to change the running environment or something like that.

And to further complicate, I am about to release v0.15 which has a substantially different startup model. Not because I was having trouble on Linux, because of a need to transition from 32bit t 64bit on the Mac, Cocoa required some changes.
So, I need to do a lot of 'other' platform testing.
Davo

OK, so forget all I have written above.
The underlying issue is that Ubuntu seems to have now removed all support for the System Tray. In 17.10 it did work but not as I have been describing, I only remembered when I fired up a Gnome3 VM. Sigh. In previous versions of Gnome3 you could access a System Tray by moving your mouse down into the lower left hand corner of the screen. But not in U18.04 / Gnome 3.28 !
There is a Gnome Extension designed to put the System Tray back were it belongs, top Right but apparently it too is having problems with 3.28 - not a good sign.
https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/127
I am not sure what all this means, I do have a solution to a similar solution under Mac's Cocoa but really don't like it, and am not sure I want to use it on Linux. So, until I have done a lot more research, I think I'll have to say that tomboy-ng does not work with any Gnome 3 based system.
I continue to use Ubuntu Mate and, of course, that works fine.

OK, I have a temp and very ugly workaround in mind, but first a summary of the situation.
System Tray is not the same thing as AppIndicator, might look similar but quite different underneath. Gnome3, for whatever reason, does not want to support the System Tray preferring the dumbed down AppIndicator.  Linux distros using Gnome3 have had various 'extensions' built in or added later to make apps using SystemTray work. Since Gnome3.28 thats got harder and apparently none of the fixes currently work. Some abandoned.
https://github.com/wincinderith/topicons
https://github.com/mjnaderi/TopTray
https://github.com/phocean/TopIcons-plus
https://github.com/laike9m/topIcons
My plan, as a temp measure until things become clearer is to turn on some code I have already written for Mac's Cocoa using either command line switches or, if possible, env vars.
The result will be an ugly and inconvenient interface for Gnome3 users. Instead of an always visible SystemTray icon, you will need to click on the tomboy-ng icon on the (whats its called?) dock or plank or toolbar to the left to bring a small tomboy-ng window into focus and then choose what you want to do from its menus.
Maybe, long term, Ubuntu (and others) will fix their Gnome3 extensions, maybe Lazarus will alter its SystemTray component to target the AppIndicator model, maybe Gnome3 user will decide they like the little window model (I doubt it).
Version 0.15 was nearly ready for release, I'll now need to incorporate these changes (easy) and test, should, if all goes well, be a week.

What I don't understand about this is that the "regular" tomboy worked with its indicator

Oh, indeed ?  That surprises and somewhat confronts me ! Apparently, most SystemTray apps don't work. The original Tomboy must have some concessions to the AppIndicator model, thats good.
If you are interested, here is a link (for a few days only) to my fairly untested v0.15 for linux64. Start it from command line and add either -g or --gnome3
https://drive.google.com/file/d/14D1TwGu77KCVjB6GYI-K7FbFjcLBSgUb/view?usp=drivesdk
You can operate tomboy-ng from the menus on the little window you see or by clicking anywhere in that window.
And, yep, I still see warning about libcanberra.
And, by the way, if you can still get real Tomboy running and only use Linux, well, don't expect -ng to be better !
Davo

Woops, did not intend to close this issue just yet.

Woops, did not intend to close this issue just yet.
(stop it Github you are guessing !)

sigh....

OK, here is the solution. You need to install gnome-tweak-tool (probably should have it anyway) and a particular gnome shell extension, 'topicons' (which Ubuntu should have rather than their own version that mostly fails).
In the Ubuntu Software application, search for "gnome shell extensions topicon", install it.
Then fire up Activities and search for gnome-tweak-tool, if you don't have it already, it will help you install it. Start it up. Click extensions, turn off the "Ubuntu Application Indicators", turn on "TopIcons" and exit.
Stop tomboy-ng, restart it without the command line switches and if you see the green icon top right, all is good. And in less time than it would take to install Ubuntu Mate (but I still prefer Mate).
Trouble Shooting notes -

I tested this with Topicon, not Topicon Plus.
Some people seem to indicate you need to restart - wow, just like Win95 ! (I did not need a restart but a bit of nostalgia does no harm)
While testing, make sure you don't dismiss the tomboy-ng startup window until you can see the green tomboy-ng icon on the Application Indicator panel, top right. Otherwise, you will loose sight of tomboy-ng and have to resort to killing the process manually. Sigh....
Gee, that icon does not look good there does it ? But at least its there and works.

Refs -
https://askubuntu.com/questions/1030833/app-indicator-not-working-on-ubuntu-18-04
https://extensions.gnome.org/extension/495/topicons/
https://askubuntu.com/questions/75530/how-do-i-install-and-manage-gnome-shell-extensions

Just a progress report on this issue.
I have had a patch accepted in Lazarus's LCL that fixes this issue on Ubuntu type distros and any other that include support for the "Unity System Tray" model. If you build from source, using Lazarus 1.8x, apply the patch in the kits patches directory (ensuring you have write permission to the relevant files). If you use Lazarus trunk, no need.
The non Ubuntu like distros that follow Gnomes strict model and are using Gnome 3.28 still don't work in the system tray mode and therefore must be started with the --gnome3 switch.
I don't consider this solved yet.

tomboy-ng now works seamlessly on Ubuntu and its derivatives.
Other Linux flavours based on Gnome 3.28 are usable if the startup window is allowed to remain in place (it forced to stay with --gnome3 switch). Or it works seamlessly if the TopIcons Gnome Extension is installed.
Not the end of this issue but will have to do unless I get some feedback from users that this is unsatisfactory.


Suggestion: Add option to remove first attack card after initiating an attack

The module is great, except my chat log keeps getting gummed up with attack cards before the actual roll. It'd be good to be able to disable this as it's meaning with a few quick attack from a couple of monsters and the log is clogged up with double the messages.

Based on this on the player's side when I select an attack they are able to see the weapon/attack that is going to hit them (which is fine) but they can also see the information below it which means they can see the hit die for the weapon and the modifier based on the attack of said weapon/attack.
Would it be possible to have an option to remove the first card that's displayed to the players and only display the GM one you created?

This won't be fixed, only update for mess that will be coming (regarding rolling issues) is removing them.
My replacement is now submitted and waits for approval. Meanwhile you can download the module and look at its features from its repository:
https://github.com/Moerill/fvtt-mars-5e
Manifest: https://raw.githubusercontent.com/Moerill/fvtt-mars-5e/master/module.json
(I'm currently going through all rolling related issues, pasting this as information and closing them)


Setup package publishing workflow

Even though these packages are not released commonly, we should still have a clearly defined workflow for publishing these packages when they do change.

Fixed in #29


how to support vertical direction?

maybe try using the standard UIPickerView instead?

Actually, I'm considering whether I should add vertical option to AKPickerView which was originally made as "a horizontal version of UIPickerView," and I think you should use standard libraries when you can use it.
Of course I know there is a PR which implements vertical option, but currently I don't have enough time to review it…


DDPB-3772 - Post Aurora Migration Cleanup.

Force merging as env is destroyed but pipeline was somehow cancelled..


Wait for order-controller to add certificate data to the Order

Added a check for the length of Order.Status.Certificate before attempting to decode it and copy it to the CertificateRequest.
I also considered adding a Ready condition to the Order which would only be set to true once all the ACME operations had been completed by the order controller.
That might be a cleaner way for the certificaterequest-controller to know when it should examine the Order.
Fixes: #2667
Release note:
NONE

/retest

Looking good! just one question on error handling then LGTM

/assign @meyskens
PTAL

/lgtm

/kind bug


[Snyk] Security upgrade @babel/traverse from 7.8.6 to 7.23.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

packages/node/base/package.json
packages/node/base/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

751/1000  Why? Recently disclosed, Has a fix available, CVSS 9.3
Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – 78faea81-ea94-4793-b12d-8044317fdf44
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

Aurora With Disabled at Rest Encryption
/rds.tf: 1
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 49
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 17
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 97
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 130
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 81
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 65
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 113
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Aurora With Disabled at Rest Encryption
/rds.tf: 33
Amazon Aurora does not have encryption for data at rest enabled. To prevent such a scenario, update the attribute 'StorageEncrypted' to 'true'.

Azure App Service Client Certificate Disabled
/app_service.tf: 22
Azure App Service client certificate should be enabled

Azure App Service Client Certificate Disabled
/app_service.tf: 43
Azure App Service client certificate should be enabled

Azure Instance Using Basic Authentication
/instance.tf: 9
Azure Instances should use SSH Key instead of basic authentication

CVE-2021-46877
Maven-com.fasterxml.jackson.core:jackson-databind-2.12.4
Vulnerable Package

CVE-2022-23539
Npm-jsonwebtoken-8.5.1
Vulnerable Package

CVE-2022-23540
Npm-jsonwebtoken-8.5.1
Vulnerable Package

CVE-2022-25881
Npm-http-cache-semantics-4.1.0
Vulnerable Package

CVE-2022-25881
Npm-http-cache-semantics-3.8.1
Vulnerable Package

CVE-2022-25883
Npm-semver-7.3.5
Vulnerable Package

CVE-2022-25883
Npm-semver-7.0.0
Vulnerable Package

CVE-2022-25883
Npm-semver-6.3.0
Vulnerable Package

CVE-2022-25883
Npm-semver-5.7.1
Vulnerable Package

CVE-2022-25883
Npm-semver-5.6.0
Vulnerable Package

CVE-2022-25893
Npm-vm2-3.9.5
Vulnerable Package

CVE-2022-25927
Npm-ua-parser-js-0.7.31
Vulnerable Package

CVE-2022-37599
Npm-loader-utils-3.0.0
Vulnerable Package

CVE-2022-37599
Npm-loader-utils-2.0.2
Vulnerable Package

CVE-2022-37599
Npm-loader-utils-1.4.0
Vulnerable Package

CVE-2022-37599
Npm-loader-utils-1.2.3
Vulnerable Package

CVE-2022-37601
Npm-loader-utils-2.0.2
Vulnerable Package

CVE-2022-37601
Npm-loader-utils-1.4.0
Vulnerable Package

CVE-2022-37601
Npm-loader-utils-1.2.3
Vulnerable Package

CVE-2022-37603
Npm-loader-utils-3.0.0
Vulnerable Package

CVE-2022-37603
Npm-loader-utils-2.0.2
Vulnerable Package

CVE-2022-37603
Npm-loader-utils-1.4.0
Vulnerable Package

CVE-2022-37603
Npm-loader-utils-1.2.3
Vulnerable Package

CVE-2022-46175
Npm-json5-2.2.0
Vulnerable Package

CVE-2022-46175
Npm-json5-1.0.1
Vulnerable Package

CVE-2022-48285
Npm-jszip-3.7.1
Vulnerable Package

CVE-2023-24580
Python-Django-1.2
Vulnerable Package

CVE-2023-26115
Npm-word-wrap-1.2.3
Vulnerable Package

CVE-2023-26136
Npm-tough-cookie-2.5.0
Vulnerable Package

CVE-2023-28154
Npm-webpack-5.64.1
Vulnerable Package

CVE-2023-29017
Npm-vm2-3.9.5
Vulnerable Package

CVE-2023-29199
Npm-vm2-3.9.5
Vulnerable Package

CVE-2023-30547
Npm-vm2-3.9.5
Vulnerable Package

CVE-2023-31047
Python-Django-1.2
Vulnerable Package

CVE-2023-32314
Npm-vm2-3.9.5
Vulnerable Package

CVE-2023-32695
Npm-socket.io-parser-4.0.4
Vulnerable Package

CVE-2023-36665
Npm-protobufjs-6.11.2
Vulnerable Package

CVE-2023-37466
Npm-vm2-3.9.5
Vulnerable Package

CVE-2023-37903
Npm-vm2-3.9.5
Vulnerable Package

Cloud Storage Bucket Versioning Disabled
/gcs.tf: 1
Cloud Storage Bucket should have versioning enabled

GKE Legacy Authorization Enabled
/gke.tf: 12
Kubernetes Engine Clusters must have Legacy Authorization set to disabled, which means the attribute 'enable_legacy_abac' must not be true

Geo Redundancy Is Disabled
/sql.tf: 80
Make sure that on PostgreSQL Geo Redundant Backups is enabled

MySQL Server Public Access Enabled
/sql.tf: 59
MySQL Server public access should be disabled

Network Policy Disabled
/gke.tf: 6
Kubernetes Engine Clusters must have Network Policy enabled, meaning that the attribute 'network_policy.enabled' must be true and the attribute 'ad...

Network Watcher Flow Disabled
/networking.tf: 126
Check if enable field in the resource azurerm_network_watcher_flow_log is false.

Node Auto Upgrade Disabled
/gke.tf: 24
Kubernetes nodes must have auto upgrades set to true, which means Node 'auto_upgrade' should be enabled for Kubernetes Clusters

Passwords And Secrets - Generic Access Key
/lambda.tf: 44
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Access Key
/providers.tf: 10
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/instance.tf: 11
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/instance.tf: 45
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/sql.tf: 50
Query to find passwords and secrets in infrastructure code.

Pod Security Policy Disabled
/gke.tf: 6
Kubernetes Clusters must have Pod Security Policy controller enabled, which means there must be a 'pod_security_policy_config' with the 'enabled' a...

RDS Storage Not Encrypted
/rds.tf: 49
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 17
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 130
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 81
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 33
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 113
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 65
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 97
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

RDS Storage Not Encrypted
/rds.tf: 1
RDS Storage should be encrypted, which means the attribute 'storage_encrypted' should be set to 'true'

SQL DB Instance Backup Disabled
/big_data.tf: 16
Checks if backup configuration is enabled for all Cloud SQL Database instances

SQL DB Instance With SSL Disabled
/big_data.tf: 8
Cloud SQL Database Instance should have SLL enabled

SSL Enforce Disabled
/sql.tf: 85
Make sure that for PosgreSQL, the 'Enforce SSL connection' is set to 'ENABLED'

Stackdriver Logging Disabled
/gke.tf: 8
Kubernetes Engine Clusters must have Stackdriver Logging enabled, which means the attribute 'logging_service' must either be undefined or set to 'l...

Stackdriver Monitoring Disabled
/gke.tf: 13
Kubernetes Engine Clusters must have Stackdriver Monitoring enabled, which means the attribute 'monitoring_service' must either be undefined or set...

Web App Accepting Traffic Other Than HTTPS
/app_service.tf: 27
Web app should only accept HTTPS traffic in Azure Web App Service.

AKS Network Policy Misconfigured
/aks.tf: 1
Azure Kubernetes Service should have the proper network policy configuration to ensure the principle of least privileges, which means that 'network...

AKS RBAC Disabled
/aks.tf: 23
Azure Container Service (AKS) instance should have role-based access control (RBAC) enabled

CVE-2022-23541
Npm-jsonwebtoken-8.5.1
Vulnerable Package

CVE-2023-0842
Npm-xml2js-0.4.23
Vulnerable Package

CVE-2023-28155
Npm-request-2.88.2
Vulnerable Package

CVE-2023-31125
Npm-engine.io-6.1.0
Vulnerable Package

CVE-2023-32313
Npm-vm2-3.9.5
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.3.11
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.39
Vulnerable Package

Default Azure Storage Account Network Access Is Too Permissive
/mssql.tf: 1
Default Azure Storage Account network access should be set to Deny

Default Azure Storage Account Network Access Is Too Permissive
/storage.tf: 23
Default Azure Storage Account network access should be set to Deny

EBS Volume Encryption Disabled
/ec2.tf: 34
EBS volumes should be encrypted

ECR Image Tag Not Immutable
/ecr.tf: 3
ECR should have an image tag be immutable. This prevents image tags from being overwritten.

ElasticSearch Not Encrypted At Rest
/es.tf: 1
Check if ElasticSearch encryption is disabled at Rest

Elasticsearch Domain Not Encrypted Node To Node
/es.tf: 1
Elasticsearch Domain encryption should be enabled node to node

Elasticsearch Log Disabled
/es.tf: 1
AWS Elasticsearch should have logs enabled

Email Alerts Disabled
/security_center.tf: 6
Make sure that alerts notifications are set to 'On' in the Azure Security Center Contact

Encryption On Managed Disk Disabled
/storage.tf: 9
Ensure that the encryption is active on the disk

Hardcoded AWS Access Key In Lambda
/lambda.tf: 44
Lambda access/secret keys should not be hardcoded

IP Forwarding Enabled
/instances.tf: 17
Instances must not have IP forwarding enabled, which means the attribute 'can_ip_forward' must not be true

Neptune Cluster With IAM Database Authentication Disabled
/neptune.tf: 7
Neptune Cluster should have IAM Database Authentication enabled

Neptune Database Cluster Encryption Disabled
/neptune.tf: 9
Neptune database cluster storage should have encryption enabled

PostgreSQL Log Checkpoints Disabled
/sql.tf: 109
Make sure that for Postgre SQL Database Server, parameter 'log_checkpoints' is set to 'ON'

PostgreSQL Server Without Connection Throttling
/sql.tf: 102
Ensure that Connection Throttling is set for the PostgreSQL server

Security Center Pricing Tier Is Not Standard
/security_center.tf: 2
Make sure that the 'Standard' pricing tiers were selected.

Small Activity Log Retention Period
/logging.tf: 8
Ensure that Activity Log Retention is set 365 days or greater

Small Flow Logs Retention Period
/networking.tf: 132
Flow logs enable capturing information about IP traffic flowing in and out of the network security groups. Network Security Group Flow Logs must be...

Small Flow Logs Retention Period
/networking.tf: 133
Flow logs enable capturing information about IP traffic flowing in and out of the network security groups. Network Security Group Flow Logs must be...

Unscanned ECR Image
/ecr.tf: 1
Checks if the ECR Image has been scanned

WAF Is Disabled For Azure Application Gateway
/application_gateway.tf: 1
Check if Web Application Firewall is disabled or not configured for Azure's Application Gateway.

Dashboard Is Enabled
/aks.tf: 19
Check if the Kubernetes Dashboard is enabled.

Lambda Functions Without X-Ray Tracing
/lambda.tf: 31
AWS Lambda functions should have TracingConfig enabled. For this, property 'tracing_Config.mode' should have the value 'Active'

Lambda IAM InvokeFunction Misconfigured
/iam.tf: 29
Lambda permission may be misconfigured if the action field is not filled in by 'lambda:InvokeFunction'

RDS Instance Log Connections Disabled
/rds.tf: 16
'log_connections' parameter should be set to ON for RDS instances

RDS Instance Log Disconnections Disabled
/rds.tf: 16
log_disconnections parameter should be set to ON for RDS instances

RDS Instance Log Duration Disabled
/rds.tf: 16
log_duration parameter should be set to ON for RDS instances

Fixed Issues

Severity
Issue
Source File / Package

Azure App Service Client Certificate Disabled
/app_service.tf: 43

Azure App Service Client Certificate Disabled
/app_service.tf: 22

CVE-2021-23440
Npm-set-value-2.0.1

CVE-2022-37616
<EMAIL_ADDRESS>

CVE-2022-37616
Npm-xmldom-0.5.0

Client Certificate Disabled
/gke.tf: 6

Cloud Storage Bucket Versioning Disabled
/gcs.tf: 1

Cluster Master Authentication Disabled
/gke.tf: 6

GKE Basic Authentication Enabled
/gke.tf: 6

GKE Legacy Authorization Enabled
/gke.tf: 12

Geo Redundancy Is Disabled
/sql.tf: 80

IAM Policy Grants Full Permissions
/iam.tf: 29

IAM Policy Grants Full Permissions
/db-app.tf: 209

MySQL Server Public Access Enabled
/sql.tf: 59

Network Policy Disabled
/gke.tf: 6

Network Watcher Flow Disabled
/networking.tf: 126

Node Auto Upgrade Disabled
/gke.tf: 24

Pod Security Policy Disabled
/gke.tf: 6

RDS Storage Not Encrypted
/rds.tf: 49

RDS Storage Not Encrypted
/rds.tf: 130

RDS Storage Not Encrypted
/rds.tf: 97

RDS Storage Not Encrypted
/rds.tf: 113

RDS Storage Not Encrypted
/rds.tf: 1

RDS Storage Not Encrypted
/rds.tf: 81

RDS Storage Not Encrypted
/rds.tf: 33

RDS Storage Not Encrypted
/rds.tf: 17

RDS Storage Not Encrypted
/rds.tf: 65

SQL DB Instance Backup Disabled
/big_data.tf: 16

SQL DB Instance With SSL Disabled
/big_data.tf: 8

SSL Enforce Disabled
/sql.tf: 85

Stackdriver Logging Disabled
/gke.tf: 6

Stackdriver Monitoring Disabled
/gke.tf: 6

Web App Accepting Traffic Other Than HTTPS
/app_service.tf: 27

AKS Network Policy Misconfigured
/aks.tf: 1

AKS RBAC Disabled
/aks.tf: 23

Cx65603961-769c
Npm-debug-3.1.0

Cx65603961-769c
Npm-debug-2.6.9

EBS Volume Encryption Disabled
/ec2.tf: 34

ECR Image Tag Not Immutable
/ecr.tf: 3

ElasticSearch Not Encrypted At Rest
/es.tf: 1

Elasticsearch Domain Not Encrypted Node To Node
/es.tf: 1

Elasticsearch Log is disabled
/es.tf: 1

Email Alerts Disabled
/security_center.tf: 6

Encryption On Managed Disk Disabled
/storage.tf: 9

IAM Access Key Is Exposed
/iam.tf: 21

Neptune Cluster With IAM Database Authentication Disabled
/neptune.tf: 7

Neptune Database Cluster Encryption Disabled
/neptune.tf: 9

PostgreSQL Log Checkpoints Disabled
/sql.tf: 109

PostgreSQL Server Without Connection Throttling
/sql.tf: 102

Security Center Pricing Tier Is Not Standard
/security_center.tf: 2

Small Activity Log Retention Period
/logging.tf: 8

Small Flow Logs Retention Period
/networking.tf: 132

Small Flow Logs Retention Period
/networking.tf: 133

Unscanned ECR Image
/ecr.tf: 1

WAF Is Disabled For Azure Application Gateway
/application_gateway.tf: 1

Dashboard Is Enabled
/aks.tf: 19

EC2 Instance Using API Keys
/db-app.tf: 242

Lambda Functions Without X-Ray Tracing
/lambda.tf: 31

RDS Instance Log Connections Disabled
/rds.tf: 1

RDS Instance Log Disconnections Disabled
/rds.tf: 1

RDS Instance Log Duration Disabled
/rds.tf: 1


feat: add opt-out of new signmessage

Link this PR to an issue
Fixes #629
Type of change (Remove other not matching type)

Breaking change (fix or feature that would cause existing functionality to not work as expected)
Users can opt-out of the new login method by checking a setting.

Describe the changes you have made in this PR -

A new "private key" format for LNDhub connectors
Hash the message that we need to sign in both LNBits and LNDhub connectors.
Add a toggle in the Settings so people can sign in the old way and recover their old accounts.

Screenshots of the changes (If any) -

How Has This Been Tested?

Check out the master branch of the extension and go to https://lnurl.fiatjaf.com
Make sure that you have a LNDhub wallet as your current wallet in Alby.
Click on LNURL Auth QR code
Make a note of the key value. This is your identity on this site.
Now, check out this PR, reload the extension, refresh the page and do this again. Your key should be different.
Toggle the setting to use the legacy LNURL auth. Your key should be the same again.

To test that it is compatible with Bluewallet, use Bluewallet connected to an Alby account to login to https://lnurl.fiatjaf.com. Make a not of the public key. This should be the same key as the one that you get by logging in with Alby, if you use the new login and are connected to the same account.
Alternatively, go to a site where you have logged in with Alby like lnmarkets.com or stacker.news. If you log in with the new method, you should have a fresh, empty account. If you toggle the legacy LNURL auth setting, you should have your old account back.
TODO: new key format for LNBits? @bumi ?

this is for LNbits: https://github.com/getAlby/lightning-browser-extension/issues/631#issuecomment-1082897771
we should just change the format on how we create the root signing key to follow a the same format as lndhub does


WIP: Adds Tautulli as a sensor platform.

Description:
This PR adds a Tautulli sensor platform to display statistics from a Tautulli server.
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#7151
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: tautulli
    api_key: 24b6eac0a858748664878d146bf63623b4
    host: <IP_ADDRESS>

Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass

Some tests failed https://hastebin.com/huyoqejuja.http unrelated to this change.

If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Thanks for the input @fabaff

Cool to see this being folded in!  Great job!  Curious if we would be able to added two Tautulli different IP monitoring sessions with this?

@digiblur when if this gets accepted you can add multiple sensors like most other entities in Home Assistant:
sensor:
  - platform: tautulli
    host: <IP_ADDRESS>
    ...
  - platform: tautulli
    host: <IP_ADDRESS>
    ...

@fabaff I think I have now changed all requested parts.
Like you said I had to rewrite the library it uses :+1:

Can be merged when build passes.

Sorry, but:
tautulli: Error on device update!
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 248, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 347, in async_device_update
    await self.async_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/sensor/tautulli.py", line 93, in async_update
    self._attributes['Top Movie'] = self.home[0]['rows'][0]['title']
IndexError: list index out of range

Please open an issue if you suspect a bug. If you need help please use our help channels:
https://home-assistant.io/help/#communication-channels
Merged PRs should not be used for support or bug reports. Thanks!


Node install fail silently

If the nodejs install generate an error, it fail without any notice (white line)
TASK [composer : add composer binary dir to path] ******************************
changed: [default]

TASK [nodejs : fail] ***********************************************************

TASK [nodejs : fail] ***********************************************************

TASK [nodejs : Make sure APT supports HTTPS sources] ***************************

Reproduction Steps:

Write a broken package.json script
vagrant uo
See that there was no error message

Expected behavior:
Provisionning should fail
Drifter version: 1.1.1
Vagrant version: 1.8.5

Ok, it seems that this is the normal behavior: http://docs.ansible.com/ansible/fail_module.html#synopsis
It's just that the output is misleading...
Can we cleanup that output?

The node role doesn't run npm install or anything that would use package.json. Since the virtualenv role for Python and the ruby role for Ruby both try to install requirements files I guess it would make sense to have the node role install the package.json.

Closing this in favour of #161.


size placed before shift has inconsistent non-zero size when shifting

Describe the bug
When using size before  shift and scrolling toward a side where the available size reduces (eg. to the left for a bottom-start placement LTR), the floating element size should reach 0 before shifting, but is instead inconsistent (and depends on the scrolling speed).
To Reproduce
Steps to reproduce the behavior:

Go to https://codesandbox.io/p/sandbox/floating-ui-zero-width-f62m3k
Scroll slowly to the far left of the container (or click on the "< Slow" button).
The floating element size down until its width reaches almost zero, then starts shifting.
Return to a middle scroll position (or click on the "Reset" button).
Scroll rapidly to the far left of the container (or click on the "<< Fast" button).
The floating element shifts while still having a large width.

Expected behavior
The floating element should have a width of zero when it starts shifting.
Screenshots

Context:

OS: Linux
Browser: Chrome 127.0.6533.99
Version: @floating-ui/dom 1.6.10

Additional context
This is due to the overflow being greater than the width for a moment, resulting in a negative availableWidth :
https://github.com/floating-ui/floating-ui/blob/0918dddda0be8ca40e30402de5e3cb207df7f465/packages/core/src/middleware/size.ts#L75-L78
When feeding availableWidth directly into the CSS maxWidth property, the negative value is ignored and so maxWidth keeps its previous value.
I propose to clip the availableWidth and availableHeight to 0 if negative, as I see no interest in having negative values.
If we want to keep negative values however (as there is an obvious workaround - clipping the values in the apply function), I think we should update the doc to state that these values can be negative and therefore be ignored by the CSS style (and maybe change the Usage examples).

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

I propose to clip the availableWidth and availableHeight to 0 if negative, as I see no interest in having negative values.

Could be valid indeed. I'm not sure when you'd want negative values given it's generally used as the maxHeight property; though the current setup is technically more flexible given the consumer can clamp it like Math.max(0, availableHeight) themselves if necessary. I guess to avoid breaking changes, we should simply add docs instead as you mentioned:

I think we should update the doc to state that these values can be negative and therefore be ignored by the CSS style (and maybe change the Usage examples).

https://github.com/floating-ui/floating-ui/commit/805d4077f70a0573bb33c596b7a20f513848f29f


Platform compatibility with MinGW and HPE NonStop

Fix a couple of platform compatibility issues with MinGW and HPE NonStop. These patches are required by Git to make the clar work for all currently tested platforms.
The HPE NonStop changes have been picked from https://github.com/clar-test/clar/pull/96, removing the other changes to make the CFLAGS overridable. The Windows fixes have been picked from the downstream patch series in Git.
The patches were originally by @rsbeckerca and @dscho. I have noted authorship via Original-patch-by trailers, but am happy to attribute full authorship of the commits if preferred by the authors.

Note that I'm wiring up support for Win32 CI in https://github.com/clar-test/clar/pull/100, which surfaces some of the Windows issues here.

Thanks!


Increased code coverage

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[X] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Added unit tests for whitespace and localdb. Added code coverage for more properties.

looks like it's just tests so bon!

ty for the tests, which are never "just" - i meant.. kinda read-only since it's a test 🌮 💯 👍


Adapt to interrupt trussed changes

Depends on

https://github.com/trussed-dev/trussed/pull/125
https://github.com/trussed-dev/usbd-ctaphid/pull/5
https://github.com/trussed-dev/ctaphid-dispatch/pull/4

TODO:

[ ] changelog

Rebased to the current main

I'm waiting for Nick to review that, and I'd like some feedback on the general architecture: https://github.com/trussed-dev/trussed/discussions/124

@szszszsz we can merge this now.


Combine commands to lower amount of layers

Combines some of the commands in the Dockerfile in order to reduce the amount of layers in the container image.

Thank you for this!


cranelift: Remove brz and brnz

Remove the brz and brnz instructions, as their behavior is now redundant with brif.

As further cleanup I think block_likely_branches and canonical_branch_inst can be removed.

Given how big of a monster this PR is, I'm going to turn it back into a draft and try to pull out as many smaller PRs as possible so that the review process isn't quite as onerous as it would be now :)


CMake targets set include path incorrectly

When installed into a non-default location, using the installed hiredis-config.cmake does not set the include path correctly such that the downstream project cannot be compiled.

Fixed by 07c361.


add support for the connection_started event

Codecov Report

Merging #2353 into master will decrease coverage by 0.07%.
The diff coverage is 70.27%.

@@            Coverage Diff             @@
##           master    #2353      +/-   ##
==========================================
- Coverage   86.22%   86.15%   -0.07%
==========================================
  Files         117      117
  Lines        8648     8685      +37
==========================================
+ Hits         7456     7482      +26
- Misses        900      905       +5
- Partials      292      298       +6

Impacted Files
Coverage Δ

client.go
74.71% <0%> (-0.89%)
:arrow_down:

server.go
83.33% <0%> (-0.57%)
:arrow_down:

qlog/qlog.go
92.86% <76.47%> (-3.44%)
:arrow_down:

qlog/event.go
95.95% <81.25%> (-4.05%)
:arrow_down:

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 81cf5ba...14a5cc8. Read the comment docs.


fix: move publishCmd to semantic release github

closes #32

:tada: This PR is included in version 2.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


incorrect url format

Hello there, I was just surfing forked repo's of Halve to see what new features people had added to it and I saw your website and found this:
imgur image
are you sure you are using correct url styling? two "/"s are after each other.
I didn't look into your codes because it's 2 AM and I'm too tired to do code review, but it might be a result of  a bad "href" linkage in your layouts.

Hey Mahdi - thank you for noticing that and sending in a note! I just saw this, hahaha. I was surprised to see an issue on my little blog. :)
It was a much simpler problem - when I defined my url in the _config.yaml file, I added a trailing /. Deleted it, and all is well.
Loving your fork of Halve, btw. I might nab that light/dark button. :)

:)
my forked halve repo is outdated, I develop the fork in a new repo at https://github.com/azadeh-afzar/Kianic-Jekyll-Theme


CGrid_geo' object has no attribute 'Vtransform

Good day.
The above-mentioned error happened shortly after running this code line (from notebook manual) :
lonp, latp, zp, t, T0, U, V = tracpy.run.run(tp, date, lon0, lat0)
error:  'CGrid_geo' object has no attribute 'Vtransform'

See #13.


SW-5431 Don't require site and zone shapefiles

The GIS team currently produces the zone and site shapefiles by merging the
subzone boundaries. There's no need for them to do that manually; we can do
geometry merging as part of the shapefile import process.
Update the importer so that it expects a zipfile with either one or two
shapefiles: the subzones and optionally the exclusions.
Zone-level settings such as target planting density are pulled from the
subzones shapefile; they only need to be set on one subzone per zone.

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

#1992  👈
#1991
#1990
#1988
#1987
main

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

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

May 24, 5:05 PM EDT: @sgrimm started a stack merge that includes this pull request via Graphite.


override remove method on instance to behave as expected

#97 I have to say this was a fun one with a annoyingly simple solution.
Now calling remove on an instance has the expected behavior and simply deletes that instance.
Calling remove on the class will still behave the same way.
I would also suggest removing the query=None from storedobject's remove method as it behaves different without a query based on which database you are using. i.e. the behavior referenced in #97 is only present in one of the test cases (mongo).
running this test:
def test_remove_without_query(self):
        self.Foo.remove()
        self.assertEqual(
            self.Foo.find().count(),
            4
        )

will fail with:
======================================================================
FAIL: test_remove_without_query (tests.queries.test_update_queries.UpdateQueryTestCaseEphemeral)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/adam/code/modular-odm/tests/queries/test_update_queries.py", line 75, in test_remove_without_query
    4
AssertionError: 5 != 4

======================================================================
FAIL: test_remove_without_query (tests.queries.test_update_queries.UpdateQueryTestCaseMongo)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/adam/code/modular-odm/tests/queries/test_update_queries.py", line 75, in test_remove_without_query
    4
AssertionError: 0 != 4

======================================================================
FAIL: test_remove_without_query (tests.queries.test_update_queries.UpdateQueryTestCasePickle)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/adam/code/modular-odm/tests/queries/test_update_queries.py", line 75, in test_remove_without_query
    4
AssertionError: 5 != 4

----------------------------------------------------------------------
Ran 580 tests in 2.535s

FAILED (SKIP=18, failures=3)

Something of this sort definitely needs to happen, and sooner rather than later.  That said, I'm not 100% certain yet what path we'll need to take on it.
Your PR makes sense to me, but I'm a little torn on the fact that there is still a StoredObject.remove classmethod that behaves differently than the instance method of the same name.
I'll put together a short list of possible approaches (including this one) into an Issue and ping you. In the meantime, I'll leave this open.

Cool, at this point I am going to close this PR.


Union type overload inference don't match if types are in different definitions

Bug Report
🔎 Search Terms
overload inference union type
🕗 Version & Regression Information
4.5.4

This is the behavior in every version I tried, and I reviewed the FAQ for entries about  it.

⏯ Playground Link
Playground link with relevant code
💻 Code

// library function definition

function libFunction(id: string | number): void;
function libFunction(conditions: {[key: string]: string}): void;
function libFunction(idOrConditions: string | number | {[key: string]: string}): void {
    console.log(idOrConditions);
}

// working example that matches a single definition
function myWrapper(id: string | number){
    libFunction(id);
}

myWrapper("something");
myWrapper(23)

// working example casting the param to any
// That's what I want to avoid
// Our code base is strict and using `any` obriglate
// me to use `eslint-disable` everywhere
function myWrapperAny(idOrConditions: string | {[key: string]: string}){
    // eslint-disable-next-line
    libFunction(idOrConditions as any);
}

myWrapperAny("something");
myWrapperAny({name: "John"});

// non working wrapper
// Even if there are overloads from both types
// This just don't compile
function myWrapper2(idOrConditions: string | {[key: string]: string}){
    libFunction(idOrConditions);
}

myWrapper2("something");
myWrapper2({name: "John"});

🙁 Actual behavior
No overload signature matches and code don't compile
🙂 Expected behavior
Overload signature matches and code compile

Duplicate of https://github.com/microsoft/TypeScript/issues/14107


🐞 Bug – Unable to set HTML attributes in the  tag

Problem
When using the app.html.attributes.body property in the elm-land.json.
The HTML attributes are there on page load, but the Elm runtime is clearing them out when the app starts.
( This was originally reported by Avinal in the Elm Land Discord's #report-a-bug channel. )
Your setup
Operating System: MacOS 12.5.1
Node version: v16.17.0
Elm Land version: v0.18.0
Notes
After taking a look, it appears to be caused by Elm's Browser.document function:

The patches list has an item that tells Elm to clear out the attributes on the <body> tag on startup.
Possible solutions:

Do not clear out attributes
Do not provide app.html.attributes.body as an option

I am just wondering why it works when I build the app first and then serve. Shouldn't the elm runtime clear then as well?

I am in favor of removing the body attribute completely since this functionality can be entirely achieved using a div and doesn't mess with elm-runtime defaults.


[Event Request] Codeunit 5334 "CRM Setup Defaults"

The events in codeunit 5334 do not make it easy to extend the CRM integration. The most common scenario is to be able to add additional field mappings for custom fields.
In all the Reset*Mapping procedures the only event is at the start of the procedure and the only way to add a field is to recreate the entire procedure and set the Ishandled to true. The danger with this is that you lose any changes to the standard code.
It would be beneficial to have an additional event after the fields have been created. For example in procedure ResetItemProductMapping have a new event:
OnResetItemProductMappingAfterInsertFields(IntegrationTableMappingName);
Immediatley before the line:
RecreateJobQueueEntryFromIntTableMapping(IntegrationTableMapping, 30, EnqueueJobQueEntry, 1440);
An equivalent event is required for each procedure that handled field mappings for the tabled.
The procedure 'InsertIntegrationFieldMapping' should also not be set to local.
If these changes were made it would be easy for partners to call InsertIntegrationFieldMapping for additional custom fields.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Migration Doc (v8 to v10)

Publishing the existing migration doc to master branch.

@aishmanoh please take a look when you have time. This is a great doc to add into the repo but some comments need to be addressed.

@zezha-msft
FYI: Merged directly to master?

Yes @mohsha-msft, since it's a doc independent of 10.10.


unsupported URL error

I'm getting this error when trying to sign in. Any ideas?
Task <79D85877-20B0-494B-A188-EE88B405D96C>.<3> finished with error - code: -1002
unsupported URL
/users/google_sign_in/

Yup. We refactored our backend api url to be in the Keys.plist. You will see api-url has an empty string in that property list. We have made it so only our team's developers can access the backend url.


⚠ Jenkins Plugins Artifactory has degraded performance

In 53fc024, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1170 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 3159583 after 13 minutes.


RealmSwift CocoaPod Lexical or Preprocessor Issue

Goals
Create a dynamic framework.
Expected Results
Build success.
Actual Results
Build failed.
Steps to Reproduce
Podfile:
    pod 'CocoaLumberjack/Swift'
    pod 'RxAlamofire', '~> 4.2'
    pod 'ObjectMapper', '~> 3.3'
    pod 'AlamofireObjectMapper', '~> 5.0'
    pod 'RealmSwift', '~> 3.11'

Realm framework version: 3.11.1
Xcode version: 10.0
iOS/OSX version: 4.1
Dependency manager + version: Cocoapod 1.5.3

Building on XCode returns error:
*hidden*/Pods/Realm/Realm/ObjectStore/src/impl/weak_realm_notifier.cpp:19:10: 'impl/weak_realm_notifier.hpp' file not found

Tried deleting DerivedData, Build and Index folder and rebuilding with no success.

The submodules for the repo are missing. This should only be possible if you specify a git URL for the pod rather than a version number, and fail to include submodules: true.

Closing this issue with no recent activity. I assume this issue has been resolved -- please let us know if that is not the case.


1.19.2 startup crash

java.lang.RuntimeException: Could not execute entrypoint stage 'main' due to errors, provided by 'morebundles'!
Caused by: java.lang.ClassCastException: class [B cannot be cast to class [I ([B and [I are in module java.base of loader 'bootstrap')

not a config issue this time xd
full log here: https://mclo.gs/fX3Mmbz
This seems like a really cool mod, so I'd love to see it working!

It errors here:

@BelgianSalamander

Ironic how #20 fixed some issue. The CurseForge version is a broken jar file. @BelgianSalamander didn't test the curseforge jar...
Just grab the jar from the .zip in number 20 issue.


Cannot read property 'addEventListener' of null

I'm receiving this error in my angular/webpack app. This issue started while migrating from webpack 1.x to 2.x. Materialize was working in my app with webpack 1.13.2.

I've gone over the angular2-materialize docs as well as rubyboy's angular2-webpack-starter fork with a fine toothed comb. The places where materialize code is imported in my app is almost identical to what's in the angular2-webpack-starter.

I'm adding import 'materialize-css'; and import { MaterializeModule } from 'angular2-materialize'; in the top of my app.module.ts and I'm adding materialize.min.css in the head of my index.html. Let me know what else is needed from me to further troubleshoot this.

@Tbull187 maybe share a repo for someone to help out. Given that there's a working project example (angular2-webpack-starter) I'd say you can try starting with it (check that it works before adding any code) and then start modifying the code slowly to how it looks for you and see when it breaks.

No response. Closing.


SSL certificate problem

0.05s$ bash <(curl -s https://codecov.io/bash)
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

Closing stale issue, I am not aware of this still being a problem


Fixing #SubExec bug in P2PBenchmark

There are multiple test failures. This needs to be looked into.


feat: update Chip subsection

Per REP-26, this PR updates the Chip subsection.

@iavl can u confirm this is what's being implemented for the staking contract?

@iavl can u confirm this is what's being implemented for the staking contract?

all good！


Add yolo as an example

The ocaml-torch bindings now have a yolo-v3 implementation. Port this to tch-rs as the two frameworks are quite similar.
https://github.com/LaurentMazare/ocaml-torch/blob/master/examples/yolo/yolo.ml

There is now a working implementation of yolo-v3 in the examples directory, a readme file describing it would be nice though.
https://github.com/LaurentMazare/tch-rs/tree/master/examples/yolo


Adding VERI Logo

https://github.com/firebird-finance/firebird-assets#quick-starter
path file should be "blockchains/polygon/assets/0xA8FC7CD1ea3A65574368fAddB4B1190aa3Fd6560/logo.png
"


Set Rating, Company name, Jobtitles as Mandatory field for the rating POST request

So now the company_name and the ratings are not mandatory anymore, but we should check for the cities. This change should ve reflected on #207

So now the company_name and the ratings are not mandatory anymore, but we should check for the cities. This change should ve reflected on #207

@elhmn  changes applied on #207


Landing page improvements and refactoring

A landing page example was added in #51 and it demonstrates how to use a HTML form for uploads. To extend this, we can introduce a new option called landing_page_file which will read the contents of a file to serve it as the landing page. The reasoning behind this is that an user might not want to put X lines of HTML code into the configuration file.
[server]
# landing_page = ""
landing_page_file = "index.html"
landing_page_content_type = "text/html; charset=utf-8"

Another idea is to refactor the landing page configuration into a separate section:
[landing_page]
# text = ""
file = "index.html"
content_type = "text/html; charset=utf-8"

I think this would be cleaner but we can go with the first option as the first stage of the implementation. More comments needed.

Just a suggestion, it would also be nice to allow a user of the landing page to provide server side auth_token in the input form.

This is now implemented in #65

Just a suggestion, it would also be nice to allow a user of the landing page to provide server side auth_token in the input form.

Feel free to submit a new issue for tracking!


[1.8.9] Dropping items = non-SpawnCause root cause (sometimes)

the Cause for SpawnEntityEvent is always supposed to be a SpawnCause object, but in the case of dropping an item, it  is a spawncause if you drag-drop an item out of your inventory screen.
But if you throw an item away with the keyboard drop-key with just the normal hotbar display, the cause isn't caught as a dropped-item:
   @Listener
    public void s1(SpawnEntityEvent event) {
        SpawnCause sc;
        if (event.getCause().root() instanceof SpawnCause) {
            sc = (SpawnCause) event.getCause().root();
        } else {
            System.out.println("The system has a spawn cause root that isnt a spawncause: " + event.getCause().root());
            return;
        }

results in:

The system has a spawn cause root that isnt a spawncause: EntityPlayerMP['BooMod'/134, l='world', x=-41.06, y=67.00, z=267.81]

======
System:  Forge 1.8.9, 1890  SpongeForge 1890-4.1.0-1378 ; api 4.1.0 -51  ZERO client or server Forgemods other than sponge and testplugin

Fixed in commits https://github.com/SpongePowered/SpongeCommon/commit/8eca553ee8592c67a390d351dbf90306c87b92dc
and
https://github.com/SpongePowered/SpongeCommon/commit/09962ddfd0b2a90ea9f0771ffcda047b11e83ddc


Don't exclude the library itself from npm

Allows other developers to manage the build themselves if they wish.
Fixes #31.
R: @jeffposnick
CC: @localnerve

:+1:

We'll have to republish eventually—want to cut a new npm release now with these changes and a patch version bump, or wait until the cache expiration stuff lands and bump the minor version?

@jeffposnick @localnerve I tagged 2.1.0 and pushed to npm. I bumped the minor because the networkTimeoutSeconds change came in since 2.0.4.
On a side note, we should stop bumping the version in package.json except when actually tagging a release.


Implement Linear Regression (without Library) in C language

🛠 Issue (Number)

Closes #
👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Due to inactivity this PR is marked STALE and INVALID


When using the jdbc catalog to query a column containing Chinese, the column length was incorrectly calculated.

Steps to reproduce the behavior (Required)

CREATE MYSQL TABLE

CREATE TABLE `mysql_table_for_test` (
  `varchar_column` varchar(20) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4

2.INSERT DATA INTO MySQL TABLE
INSERT INTO test.mysql_table_for_test (varchar_column) VALUES ('这里只有几个汉字')

3.CREATE JDBC CATALOG
CREATE EXTERNAL CATALOG jdbc_catalog_test1
PROPERTIES
(
    "type"="jdbc",
    "user"="user",
    "password"="password",
    "jdbc_uri"="jdbc:mysql://host:port",
    "driver_url"="http://host:port/mysql-connector-java-8.0.28.jar",
    "driver_class"="com.mysql.cj.jdbc.Driver"
);

QUERY VIA JDBC CATALOG

SELECT varchar_column from jdbc_catalog_test1.test.mysql_table_for_test;

Expected behavior (Required)
return data
Real behavior (Required)
return exception:
[42000][1064] Value length exceeds limit on column[varchar_column], max length is [20], value is [这里只有几个汉字]
StarRocks version (Required)
3.1.2-4f3a2ee

The length of varchar in starrocks is in bytes, but in MySQL it is in characters.

The length of varchar in starrocks is in bytes, but in MySQL it is in characters.

Got it, are you planning to fix the problem caused by the difference in varchar length calculation?


Improve wildcard typing

Currently we get errors like this:
$ gr tests/regression/illtyped/wild2.gr

Checking tests/regression/illtyped/wild2.gr...
Linearity error: tests/regression/illtyped/wild2.gr: :1:1:
  Linear variable `_` is never used.
Failed

(where wild2.gr contains foo _ = 0)
This indeed should be an error, but we want a better error message. Related to this but more serious is the example:
-- This should be ok:
isZero : Int -> Bool
isZero x = case x of 0 -> True; _ -> False

This should be allowed as the concrete pattern match of 0 means we use x exactly once, but this is not allowed at the moment due to the second pattern which is a wildcard.
This relates slightly to issue https://github.com/dorchard/granule/issues/64  but should be more to do with the role of concrete patterns with a linear guard.

This has been fixed now.


First-class control on loaded relationships

Checklist

[X] There are no similar issues or pull requests for this yet.

Is your feature related to a problem? Please describe.
Recently noticed that one of my list views was taking a bit longer to render than expected. After profiling the code, I determined it was because during the async def list() function, each of the relationships were being joinedload()'d. In the case of this particular model, the model being joined had a field with many MB of JSON data that would be parsed. So it was loading, but then not being used in the rendering of the list view, or details view for that matter.
Describe the solution you would like.
I wonder if there should be a class var describing which relationships to load (or maybe how to load them). I'm aware that it is currently being done to reduce the likeliness of an attribute access error (or even slower loading if they were accessed without the prefetching) when rendering the list or details view.
Describe alternatives you considered
I worked around this right now by using this sort of code in my view class definition.
class MyModelView(ModelView, model=MyModel):
    def __init__(self):
        super()__init__()
        this._relations = []

This seems to work, but is reliant on a private variable, which isn't guaranteed to always exist, of course.
Additional context
No response

Thanks,
I've prepared the fix but maybe a bit differently.
In the list page and export page it was by default loading all relationships, but it should actually only use the relationships of the columns you want to display.


[WIP][BACKEND] Refactored the MoveConvertOutOfIf conversion to handle scf.if correctly

Also removed duplicate code for simulateBackwardRematerialization.
Fix issues https://github.com/openai/triton/issues/1105 and https://github.com/openai/triton/issues/1063
There's a problem worth discussing:
    if row_id + p == 0:
        output = x
    else:
        r = tl.zeros([BLOCK_SIZE, BLOCK_SIZE],tl.float32)
        x_keep = r > p
        # write-back
        output = tl.where(x_keep, x / (1 - p), 0.0)

We see problems in r and x_keep because they are only defined in the else block but not the then block.
For everything defined in the local block, we yield it in the end. Since r and x_keep are not defined, we first look it up in the parent block. But in this case the parent block also doesn't define the variables, and therefore a segment fault is raised:
https://github.com/openai/triton/blob/bc8a26d56f68b7d1206dcd2076a604ada0a44a43/python/triton/compiler.py#L402
I'm not sure if this PR proposes the right solution for this problem. The fix logic is:

If we see r in liveins_copy, we copy it for the yield op of the then block (then.yield).
Otherwise, we make a copy from else_defs.
If r is not used after scf.if, then.yield's r will get removed after the Canonicalizer.
If r is used after scf.if, there will a compilation error since r isn't produced from the then block.

FYI I've found a looooot of issues in the frontend. I have a PR that fixes a lot of things, and I believe it does address this problem too


warmupToWidget with CapsuleContainer

warmupToWidget is really helpful for setting up widgets but there doesn't appear to be an equivalent when using CapsuleContainer s directly. When writing tests against the CapsuleContainer (instead of a widget test with RearchBootstrapper) it would be helpful if you could wait on capsules to be ready e.g.

AppointmentService appointmentService(CapsuleHandle use) {
  final venuesService = use(venuesService);
  final appointmentService = AppointmentService(venuesService);
}

final container = CapsuleContainer();
await container.read(futureVenuesService);
container.read(appointmentService);

Currently it's possible using
final container = CapsuleContainer();
await container.read(futureVenuesService);
container.onNextUpdate(futureVenuesService, () {
  final appointmentService = container.read(appointmentService);
})

but it would be good to have an official way to do it.

https://github.com/GregoryConrad/rearch-dart/discussions/125


Contact Info returns {}

Contact info returns empty {}.
Template to handle selection is outdated.

@muchai-mercy are you using hasToGetContactInfo parameter in options object?
It has to be set to return contact information

Yes @leonardiwagner I have it set to true

@muchai-mercy alright, so we should update that template section, I'm quite busy to do that today, but if you are going to update that please send a pull-request here as well, thanks :smile:

@leonardiwagner if I manage to get to it as well I will

Is this still a problem as of version 1.0.16?

@kf6kjg I still have this issue in most contacts... I get an empty array contact: []

@grapevineai have you tried to set getContactInfoas true on options?

@leonardiwagner I think I know why I get inconsistent results with contact info...the timeout to get the contact info page is only 500ms. I increased it to 2000ms and now I always get the contact info.
Instead of waiting 2 seconds, shouldn't we wait for the #pv-contact-info to show up? I will propose a PR.


Design MoonSheet Logo

Is your feature request related to a problem? Please describe.
Logo and Favicon design
Describe the solution you'd like
N/A
Describe alternatives you've considered
N/A
Additional context
N/A

wait i have more i will send

auto generated logos?

no they are just preview if you liked i will finalize one all images are used licensed in Adobe Stock Images

here's the new ones


broken connection not detected

Expected behavior
Actual behavior
we see some redis tcp connection status is ESTABLISHED, but the file descriptor is missing, the reason is unknown, but if redisson use these connections, netty writeFuture always timeout and we get org.redisson.client.RedisTimeoutException
Steps to reproduce or test case
don't know, we experience this twice in last month
Redis version
4.0
Redisson version
3.13.3
Redisson configuration
redisson-spring-boot-starter default
hope redisson can provide testOnBorrow or some method to solve this, thanks

set pingConnectionInterval setting

thanks mrniko! this helps a lot


Unable to use dt$ or ct$ in tex file

Steps to reproduce:

Create a new TeX file and save it as test.tex
Type the following single line in it:

a $test$

Move the cursor to the beginning of the line
Type dt$

Expected behavior: The part "a " is deleted.
Actual behavior: A "$" is inserted.
A similar error exists for ct$
I am using atom-latex.

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


Groups: Frequent disconnects, broken visual assets on e1abg

Since e1abg, I've seen the "You are currently offline" banner pop up every few minutes, and many messages I have posted have vanished even during periods when the offline banner was not present. When the "You are currently offline" banner appears posting is impossible. Group avatars, hero images, and user avatars are also inconsistently broken (showing a broken image link placeholder) across groups.
This issue is reported by at least two other users in UC/help.

To Reproduce

Upgrade groups to e1abg.
Note that things are screwy.

Expected behaviour
Graphics render correctly and users are not disconnected constantly.
Additional context:

Ship type: Planet
Instance type: CLI self-hosted
OS/browser: Vivaldi on Linux

I'm also seeing the frequent disconnects bug on macOS Safari, connected to a self-hosted ship running on an old MacBook Pro via Tailscale.

To expand on this, my pier is currently on localhost. In the terminal, whenever I interrupt with ctrl-c I get a bit of a seeming backlog of various stack traces, e.g.:
~litmus-ritten:dojo>
recover: dig: intr

interrupt
crud: %ames-wake event failed
[%poke %wake]
wire=/pump/~raphut-fantun/1.693
bar-stack=[i=[i=/ames t=~] t=[i=[i=//behn t=~] t=~]]
take: failed
/sys/vane/ames/hoon:<[1.232 3].[1.252 20]>
/sys/vane/ames/hoon:<[1.233 3].[1.252 20]>

[...]

I'm experiencing the same issue running on a VPS. CPU usage of the urbit process is running abnormally high (>=96%)

See CPU usage for the past 24 hours (GMT). Shortly before 15:00 on Saturday, cpu usage increased dramatically and then dropped off to normal level after about 3 hours. This morning cpu usage was high again. I then updated to v1.22 and am still seeing high cpu levels

I'm seeing the same thing since Tuesday. I suspect it has to do with the recent base OTA. I have the ames spam as well.

This looks fixed in 8j82a. Thanks all.


TO-DO Bug fix for using the new version of Native AOT

https://github.com/nifanfa/Solution1/commit/80e166f0832001d1334987cb58d03a957c3304a0


x87 FPU isn't handled correctly by the decompiler

Describe the bug
The decompiler fails to analyze correctly code that is making use of the x87 FPU subset of instructions.
To Reproduce
Import the binary attached(it is a standard PE), several mistakes can be seen at the following adresses:

0x40d770, decompiler output being:

    if ((((bullet->state != 0) && (bullet->state != 5)) &&
        (bullet->sprites[0].additional_infos != (something_56_bytes *)0x0)) &&
       ((!in_PF && (!in_PF)))) {

while the correct output should be something more along the lines of
if bullet->state != 0 && bullet->state != 5 && (bullet->sprites[0].additional_infos) != 0x0 && (30. <= (bullet->sprites[0].additional_infos)->height) && bullet->speed == 0. {

0x40dbc0, where the decompiler is showing a fsincos being unused, while it is actually used in the binary.

Expected behavior
The decompiler analyzing correctly the file
Attachments
binary.txt
Environment (please complete the following information):

OS: Gentoo Linux
Java Version: 11.0.4
Ghidra Version: 9.1 2019-Oct-22

The first issue is resolved now in the master branch with the addition of full support for the x86 parity flag. The fsincos problem is a different issue with the detection of stack aliases but is also resolved in master; thanks for reporting it.  Fixes should be present in the 9.2 release.


[Bug]: No devices/stations found

Version
0.8.4
Node version
16.13.2
Operating System type
Windows
Operating system version
Windows 11
Describe the bug
Related to #74
When setting up a sharing with Eufy App v4 by either sharing a home or sharing devices with Admin (extended) proviledges I don't see devices nor stations in the websocket using the shared to account.
Devices / Stations still show ok using the main account (no sharing)
To reproduce

Go to Eufy App and share a home or device with a previously created Eufy Account.
With the shared to account accept the invitation. Verify you see the devices in this account.
Setup eufy-security-ws as described using a config.json file.
Take special care to select the correct country so you are pointed to the correct Eufy cloud. In my case DE for Germany.
Start the node in verbose mode.
No devices/stations are found. In log details country is still defaulting to US, therefore pointing to the incorrect cloud instance unable to find stations/devices.

Screenshots & Logfiles
No response
Additional context
Shared a detailed debug log of server.js as well as the config.json on your email.
Made sure to use the latest versions of the WS and the eufy-security-client (as of today 18FEB2022).

Hi, I already send node server.js debug logs to your email<EMAIL_ADDRESS>for reference. Let me know if you need more information.
I just created a fresh account which I shared devices with, still no devices show up. Please note that sharing and the new account gave been done with Eufy app > 4.x


Inline math not rendered correctly

Issue Summary
I have encountered several inline math rendering problems when using a Jekyll theme jekyll-theme-chirpy. I've posted an issue in that repo but the author thinks it's not relevant to that repo, so I'm trying to find some help here.
Steps to Reproduce
Here are several examples where my math equations were not rendered correctly.
The following markdown file summarizes the problems I encountered so far. It can be found here
---
comments: true
title: MathJax Problems
math: true
image:
  path: https://images.ctfassets.net/3viuren4us1n/1Ghw96A2tcYRfRezOwtmjx/e646778f3f53e50ea3e857e9cdb23120/Computer_vision.jpg?fm=webp&w=1920
date: 2023-09-20 12:00:00
categories: [machine-learning, computer-vision]
tags: [machine-learning, computer-vision]
---

## MathJax Problem
### No.1 - I found an unuseful fix
### When two inline equations are in the same line

For each RoI (also for each class), PS RoI pooling is applied to obtain *normalized* offsets $ \Delta \hat{p}_{i, j} $ and then transformed to the real offsets $ \Delta p_{i, j} $3

### When moving the 2nd to a new line

For each RoI (also for each class), PS RoI pooling is applied to obtain *normalized* offsets $ \Delta \hat{p}_{i, j} $ and then transformed to the real offsets

$ \Delta p_{i, j} $

### No.2 - Still can't fix them

$ E = (b_{30}b_{29}...b_{23})_2 = (01111100)_2 = (124)_{10} \in \{1, ..., (2^8-1) - 1 \} = \{1, ..., 254\} $

$ (1.b_{22}b_{21} \dots b_{0})_2 = 1 + \sum_{i=1}^{23} b_{23 - i}2^{-i} = 1.25 $

$ (3 + 127)_{10} = (10000010)_2 = (b_{30}b_{29} \dots b_{23})_2 $

$ (1.b_{22}b_{21} \dots b_{0})_2 = (1.01011 \underbrace{0 \dots 0}_{18})_2 $

### No.3 - Found a fix, but shouldn't MathJax have consistent behavior?

Problem with `|` `{` `}`

#### When not escaping `|` `{` `}`

$ x_i \longrightarrow P(y | x_i; \Theta) \longrightarrow P^*(y | x_i) $

$ {C_2, C_3, C_4, C_5 } $

#### When escaping  `|` `{` `}` with a single `\`

$ x_i \longrightarrow P(y \| x_i; \Theta) \longrightarrow P^*(y \| x_i) $

$ \{C_2, C_3, C_4, C_5 \} $

#### When escaping `{` `}` with `\\`

$ \\{C_2, C_3, C_4, C_5 \\} $

This is what it looks like on the GitHub page, and a live version can be found here

(Strange behavior with No.1, can't render with No.2)

(Escape | with \ is working, but { and } need to be escaped with \\)

This is what it looks like on Typora (which also uses MathJax for rendering, check here),

(No.1 and No.2 have no problem with Typora)

(Typora requires escaping { and } but not |)
Technical details:

MathJax Version: 3.2.2
Client OS: Mac OS X 13.6 (22G120)
Browser: Chrome 117.0.5938.88

(The MathJax configuration was copied from the inspect of this GitHub page)
I am using the following MathJax configuration:
<script>
/* see: <https://docs.mathjax.org/en/latest/options/input/tex.html#tex-options> */
MathJax =
{
  tex: {
  /* start/end delimiter pairs for in-line math */
  inlineMath: [ ['$', '$'], ['\\(', '\\)'] ],
  /* start/end delimiter pairs for display math */
  displayMath: [ ['$$', '$$'], ['\\[', '\\]'] ]
   }
 };
</script>

and loading MathJax via
<script id="MathJax-script" async=""<EMAIL_ADDRESS>
Summary and Questions
I'm not sure how to check the MathJax version that is being used on Typora, so I can't provide any useful information on that.
My questions are:

Can I expect Typora and my GitHub Page (powered by Jekyll) can have the same behavior in terms of math equation rendering since they are both using MathJax?
I think maybe it's a MathJax configuration problem, can anyone give me some tips on how to modify my GitHub page configuration to match them?

Thanks!

This is due to an interaction between Markdown and LaTeX notation.  In particular, the underscore, _, is used in Markdown to indicate italics, and you can see in your Jekyll output that portions of your un-typeset mathematics are in italics and certain underscores are missing.  E.g., you have

$ (3 + 127){10} = (10000010)_2 = (b{30}b_{29} \dots b_{23})_2 $

in your output, which shows that the first and third underscores are being matched as the delimiters for italics, and have been removed by the Jekyll markdown engine and replaced by <emph>...</emph> or some other HTML to produce the italics.  Because MathJax doesn't process math that contains HTML tags, this expression is not being typeset.  Similarly for your other examples in your no. 1 and no. 2 sections, all of which have underscores that are being interpreted as italic delimiters.  In your first example, were there are two in-line expressions, each containing an underscore, those two underscores cause <emph> and </emph> to replace them, and that means the closing dollar sign for the first expression and the opening one for the second are now inside <emph>...</emph>.  That means MathJax doesn't find the closing dollar sign for the first expression and doesn't typeset it; instead, the two dollar signs inside the <emph> are found as math delimiters, and the words between them are interpreted as math (which is why they show in math italics with no spaces).
For your no. 3, it looks like Jekyll is interpreting the | characters as having meaning in Markdown.  It looks like they might be indicating the break between table cells (you may have a table extension in use that is doing that).  The second expression is properly typeset, since { and } are grouping symbols in TeX, so don't produce braces in the output.  Both Jekyll and Typora produce the same output for these.  You would want to use \{ and \} in TeX notation to produce actual braces in the output.  But in Markdown, \ is an escape character used to prevent the usual meaning of the following character, so the backslash is removed (when the following character has special meaning in Markdown), and the following character is included literally in the HTML page.  That is why the \| in Jekyll prevents the | from forming a table, and MathJax can then typeset it properly.  On the other hand, \{ and \} are replaced by { and } by Jekyll, and MathJax gets $ {C_2, C_3, C_4, C_5 } $ as its input, which (as before) has the braces as grouping characters that are not output by MathJax (or TeX).  On the other hand, when you use double backslashes, Markdown concerts this to a single one in the HTML, and so $ \\{C_2, C_3, C_4, C_5 \\} $ becomes $ \{C_2, C_3, C_4, C_5 \} $ in the HTML page, and so MathJax will get \{ and \} rather than { and }, which produce literal braces in the output.
All of these problems are due to the fact that Markdown engine you are using in Jekyll doesn't know anything about mathematical notation and is trying to interpret the LaTeX as Markdown commands.  Since Markdown is being run on the server to produce the HMTL page that is sent to the browser, and MathJax runs in the browser, the damage to the mathematics is done long before MathJax sees it, and there is nothing MathJax can do about that.
Typora uses a markdown engine that knows about mathematical notation, and is able to protect the mathematics from being processed as Markdown, and that is why the results work properly for you there.  This is not about the consistency of MathJax, but of the consistency of the Markdown processors in use.  They are not the same, and don't handle the mathematics the same.
Here are some articles about using MathJax in Jekyll that might help you get a more consistent experience.  I have not tested any of them.

Creating a Mathematics Blog with Jekyll
MathJax 3 in Jekyll and Kramdown
Jekyll and Mathjax

This is due to an interaction between Markdown and LaTeX notation. In particular, the underscore, _, is used in Markdown to indicate italics, and you can see in your Jekyll output that portions of your un-typeset mathematics are in italics and certain underscores are missing. E.g., you have

$ (3 + 127){10} = (10000010)2 = (b{30}b{29} \dots b_{23})_2 $

in your output, which shows that the first and third underscores are being matched as the delimiters for italics, and have been removed by the Jekyll markdown engine and replaced by <emph>...</emph> or some other HTML to produce the italics. Because MathJax doesn't process math that contains HTML tags, this expression is not being typeset. Similarly for your other examples in your no. 1 and no. 2 sections, all of which have underscores that are being interpreted as italic delimiters. In your first example, were there are two in-line expressions, each containing an underscore, those two underscores cause <emph> and </emph> to replace them, and that means the closing dollar sign for the first expression and the opening one for the second are now inside <emph>...</emph>. That means MathJax doesn't find the closing dollar sign for the first expression and doesn't typeset it; instead, the two dollar signs inside the <emph> are found as math delimiters, and the words between them are interpreted as math (which is why they show in math italics with no spaces).
For your no. 3, it looks like Jekyll is interpreting the | characters as having meaning in Markdown. It looks like they might be indicating the break between table cells (you may have a table extension in use that is doing that). The second expression is properly typeset, since { and } are grouping symbols in TeX, so don't produce braces in the output. Both Jekyll and Typora produce the same output for these. You would want to use \{ and \} in TeX notation to produce actual braces in the output. But in Markdown, \ is an escape character used to prevent the usual meaning of the following character, so the backslash is removed (when the following character has special meaning in Markdown), and the following character is included literally in the HTML page. That is why the \| in Jekyll prevents the | from forming a table, and MathJax can then typeset it properly. On the other hand, \{ and \} are replaced by { and } by Jekyll, and MathJax gets $ {C_2, C_3, C_4, C_5 } $ as its input, which (as before) has the braces as grouping characters that are not output by MathJax (or TeX). On the other hand, when you use double backslashes, Markdown concerts this to a single one in the HTML, and so $ \\{C_2, C_3, C_4, C_5 \\} $ becomes $ \{C_2, C_3, C_4, C_5 \} $ in the HTML page, and so MathJax will get \{ and \} rather than { and }, which produce literal braces in the output.
All of these problems are due to the fact that Markdown engine you are using in Jekyll doesn't know anything about mathematical notation and is trying to interpret the LaTeX as Markdown commands. Since Markdown is being run on the server to produce the HMTL page that is sent to the browser, and MathJax runs in the browser, the damage to the mathematics is done long before MathJax sees it, and there is nothing MathJax can do about that.
Typora uses a markdown engine that knows about mathematical notation, and is able to protect the mathematics from being processed as Markdown, and that is why the results work properly for you there. This is not about the consistency of MathJax, but of the consistency of the Markdown processors in use. They are not the same, and don't handle the mathematics the same.
Here are some articles about using MathJax in Jekyll that might help you get a more consistent experience. I have not tested any of them.

Creating a Mathematics Blog with Jekyll
MathJax 3 in Jekyll and Kramdown
Jekyll and Mathjax

❤❤❤ Thanks so much for your reply. Now I have direction on what to do next, and I'll post a possible fix after testing.

As explained by @dpvc, the problem I had was due to the markdown engine kramdown. After reading the krandown doc from here, it appears kramdown is using slightly different syntax with standard markdown.

For block math, it's the same that you enclose your math code with $$ math $$;
If you have a paragraph that looks like a math block but should actually be a paragraph with just an inline math statement, you need to escape the first dollar sign: \$$ math $$;
If you don’t even want the inline math statement, escape the first two dollar signs: \$\$ math $$;

In short, always use $$ with kramdown, escape the first dollar sign for inline math.
Although I'm pretty confused why kramdown won't use the standard markdown syntax 💔 and I can't have consistent output with Typora or VSCode unless I can find a way to configure their markdown engine accordingly.

As explained by @dpvc, the problem I had was due to the markdown engine kramdown. After reading the krandown doc from here, it appears kramdown is using slightly different syntax with standard markdown.
For block math, it's the same that you enclose your math code with $$ math $$;
If you have a paragraph that looks like a math block but should actually be a paragraph with just an inline math statement, you need to escape the first dollar sign: $$ math $$;
If you don’t even want the inline math statement, escape the first two dollar signs: $$ math $$;
In short, always use $$ with kramdown, escape the first dollar sign for inline math.
Although I'm pretty confused why kramdown won't use the standard markdown syntax 💔 and I can't have consistent output with Typora or VSCode unless I can find a way to configure their markdown engine accordingly.


Unable to show all markers

These are the settings in ~/.vit/config.ini for [marker] section
enabled = True
columns = all
header_label = Marker
require_color = False
include_subprojects = False
due.today.label = (DT)
tag.remindme.label = (R)

The Marker column is shown. But it only shows marker (P) for project and nothing else. There are no color related settings in ~/.taskrc. Not sure what I am doing wrong here.
vit --version
2.0.0

task --version
2.5.1

My guess is you're misunderstanding the purpose of markers. Markers are only displayed when the relevant column they would be coloring is not displayed in the report, otherwise the column itself is colored.
See https://github.com/scottkosty/vit/blob/2.x/COLOR.md

Okay. Thanks. In my humble opinion such a condition limits the use case for the markers. For example, I use row coloring with task next report to quickly identify the task that are due today. Then the Due column shows which task is due first (1h, 5h etc.) and I can work on the task that is due first. With vit 2.x, if I use marker (DT) to identify the tasks that are due today but then the Due column is suppressed. I have no way of knowing which task is due first by simply looking at the report. The more helpful implementation at least for me would be to allow markers (with or without colors) to show independently of the columns displayed in the report. Columns simply offer more information than text indicators. This way markers can be perfect replacement of row coloring. Users can customize what columns and markers to be displayed at the same time.

I'm not sure what you mean. If you have a Due column in your report, it will be properly colored based on your .taskrc configuration for due/overdue/etc. The purpose of markers is to supply color information for a task when a report doesn't include a column.

The attached image illustrates what I'm talking about.

Okay. I understand. I thought to use marker as replacement for row coloring, but may be not. It is acceptable when the column itself is not offering any additional information. In your example, The text indicator (BG) indicates whether blocking or not. However, take for example of Due column. Consider the screenshot from vit 1.x below:

I will complete task 49 first followed by 45,51,43,46,47 in the order of due time.
Now if the markers enabled in vit 2.x, the screenshot looks like:

Now, I have no way to know which task is  due first since I need to disable Due column to enable corresponding marker. In this case I guess it is not advisable to use markers. They are useful when indicating a boolean value.

I'm not sure you do understand. Look at the following image. The colors for due and overdue are there, in the Due column itself. You don't need markers for that:

Please re-read https://github.com/scottkosty/vit/blob/2.x/COLOR.md -- it explains the tradeoffs that were made with this new color approach, which I believe is superior overall.
You are, of course, welcome to continue using Vit 1.x if you prefer that coloring approach. No further development is planned for that branch.

Thanks. That is sort of my point. Vit 2.x does provide markers for a columns like "due" that can be colored directly and using the marker does not offer any additional advantage. I am aware that markers are useful when the report does not have that specific column. I would rather include that column instead. At least for my cases, I could not find any use for markers. I really wish vit 2.x could support row based coloring from taskrc. Personally, I find it more elegant in terms of visualization and the background color of the columns also remain consistent.

I would rather include that column instead

I'm afraid I don't understand what you mean by that.

I really wish vit 2.x could support row based coloring from taskrc

You don't have to wish -- Vit is open source software, and you are free to fork and modify it as you like. If your code is clean, I might consider merging it into the project. I will say, however, that the work done around color management was some of the most difficult in the rewrite, and for me, supporting two different coloring schemes wasn't worth it -- I personally hate the default task coloring approach -- it's not only loud, but it also results in the loss of visual cues in more complicated cases, and the color merging is confusing IMO.
One last point to make here: if part of the issue is that the coloring is too subtle for you, you do have full control over the color output for due/overdue. Something like this:
  color.due=black on brown
  color.overdue=white on red

Which gives some pretty obvious visual indicators, no markers necessary:

You don't have to wish -- Vit is open source software, and you are free to fork and modify it as you like.

I can give it a try. I am afraid my coding skills are not good enough to implement something as complex as row-coloring with no knowledge of curses module or code structure. That is why I am sincerely grateful to developers like you who put in the time and effort to build such great open source projects.
I use taskwarrior synced with google calendar (there is another open source project for syncing to google calendar called taskw_gcal_sync) for day to day task management. My use case/tasks are fairly trivial and the task coloring approach seem to work for them. One glance of task next gives me a good idea of what needs to done next since rows are uniformly colored. Regarding color noise, I sincerely think task coloring can be customized to subtle colors on a 256 color palette.  I do also agree with you. A single unified row color might not work for complicated cases. I presumed that markers would be the solution for it such that most of the report will be no colors and markers will be colored to highlight relevant attributes of the task. It turns out the purpose of markers is entirely different.


need an exclude folder list - general comment on folders as well

I have a folder for templates and another for tests and "tasks" from these folders are showing up in "today" in the timeline.  At least can we have an "excluded folder" list added where each folder listed and its children are excluded from the timeline.
More generally, the include is automatically populated.  If one uses daily notes there can be a LOT of  notes listed here.  But you ask for the daily notes folder already.  Why not just an "include list" that can take a folder or note to include beyond the daily notes.

Thanks for the advice, the automatic populating of include files is actually a bug, I will fix it asap.
Also, the folder-based organization is good, I think it will work well in this plugin.

Hi @pcause , with the new version 0.1.0 released, the excluded folder feature is now added to the options.


Update case-study-looking-through-holes-in-your-reality.md - Fixed padding around About the author tile

Fixed padding around About the author tile

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/case-study-looking-through-holes-in-your-reality.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Admin Theme - RTL : Properties tab of layout is not positioned correctly

Properties tab of layout is positioned as LTR. Also all buttons will be reversed

Is this an issue of just the new admin theme, or does it also occur on the old admin? If so, then this should be labeled as an RTL issue of the Layouts module instead.

Both on new and old. I changed the title


Add dark mode

Bootstrap Library
Bootstrap has supports with dark mode and you can add in your project. Link (https://getbootstrap.com/docs/5.3/customize/color-modes/#dark-mode). It's so easy to use, in this document have all ways to use the dark-mode, you can find your alternative and use how you want.

Add library in your project
Only thing you need to do is download to add in your project or you can reference into head the link for library, but all this is write in website (https://getbootstrap.com/).
Download into project:
npm install<EMAIL_ADDRESS>

Observation
It's important to see what is the best for your project, it's only an ideia.

@JeanPasquini Issue already exists #20


Vulkan support?

So Vulkan is now released, and we also got Vulkan support in GLFW and the drivers are also available now..
It will be really cool to see the support in LWJGL3. Could you add this very soon please??

Wouldn't it make more sense to make a complete new library (similiar to lwjgl) but on top of vulkan?

I don't think so, since we already got support for Vulkan in GLFW that LWJGL3 already provides support for, it is better to use existing library here. Also there went a lot of work into LWJGL 3 till now.

Wait, this is a duplicate and already mentioned in #50 so I'm closing this issue. Sorry for not looking up early before posting.

Check issue #50.
Specifically this comment: https://github.com/LWJGL/lwjgl3/issues/50#issuecomment-159048360

@johnnic431 It's now available to public, and LunarG has also released a complete Vulkan SDK.

@sriharshachilakapati I'm aware, but the comment mentions that it will take a little while to release a LWJGL update.

Hey guys,
I'm fully aware how excited everyone is to give Vulkan a try. But as I mentioned in #50, I haven't had access to the spec before today. I'm currently setting everything up and will be working on the bindings until late tonight. It's all new to me, but I'll try to push something usable as soon as possible.

The utmost respect to you, @Spasi , and all the sympathy for pulling this off and realizing a 631 pages spec with LWJGL. :)
I mean, it took a lot of time and effort for you guys to fully reflect the OpenGL API.
But now that there actually are C header files for Vulkan, it'd probably be good to first invest (if not already happened) to some automatic C header file to Kotlin template files generator?

Yes, I'll think about that after 3.0 is released, it'd be useful to have a decent parser (libclang bindings?).   The converter we have in LWJGL is too limited and too OpenGL-oriented. I was actually just adding support for enums, there's a ton of them in Vulkan.
At least the work on struct support is paying off. 124 struct types in Vulkan 1.0 + first extensions, if my count is correct.

I'll see if I can help you with that. I started a clang project for that some months ago, which however made use of clang as a tool and interfaced with its printed AST output to parse that.
But that might not be your preferred solution, of course.