Feedback from Yi Yan

The overall dashboard looks well functional. Some points may be considered in the future improvement:

[ ] The bar chart shows the CO2 emission based on each country, while the line chart I guess is cumulative. It would be easy to navigate if separating the line chart for comparison or changing the title so that readers can easily follow.
[ ] Might add a card for the 'Total CO2 emissions', instead of using plain text.
[ ] Header font size could be differentiated from the filter option, and the 'filter option' font size now is larger than 'Total CO2 emissions', which could also be adjusted.
[ ] Add a background color to the title might help to grab a reader's attention about the dashboard topic.
[ ] Too much whitespace, a good suggestion might use a color theme.

The bar chart shows the CO2 emission based on each country, while the line chart I guess is cumulative. It would be easy to navigate if separating the line chart for comparison or changing the title so that readers can easily follow.

Considering that all of our plots updated given the (1) year range and (2) countries selected, we decided to make it extra clear by including this information in our sidebar widget ✅

Might add a card for the 'Total CO2 emissions', instead of using plain text.

We tried a card implementation of this, but it actually ended up looking too busy. To keep our dashboard clean/simple, we decided to retain the current layout (but moved the Total CO2 emission section to the middle so it's clearly separated from the rest of the input widgets ✅

Header font size could be differentiated from the filter option, and the 'filter option' font size now is larger than 'Total CO2 emissions', which could also be adjusted.

Thanks for the suggestion! We've adjusted the header font size throughout the dashboard ✅

Add a background color to the title might help to grab a reader's attention about the dashboard topic.

We attempted to add a background colour to the title, but it ended up making our dashboard look too clunky/busy. The current layout (greyed out widget + white background everywhere else) was the most optimal dashboard layout after testing a few different combinations ✅

Too much whitespace, a good suggestion might use a color theme.

We adjusted the sizes of the plots and changed the dashboard layout to reduce the amount of extra/unnecessary white spaces throughout ✅

Closing issue as all comments have been addressed


added info market value per point (rebase)

This is the rebase of #33,

I checked this feature on your instance. It's a interessting value. Maybe as a little improvement at offers/sell page should be a additional information about KpP Value with purchase price instead of market value. So you can see also the performance of your invest!
e.g.:

Nice idea, thanks. I'm sure this shouldn't be too hard to implement. I'll look into it.


distro: bump up version for EMLinux 2.9 release

Update DISTRO_VERSION from 2.8 to 2.9

@teradat thanks.


[Feature]: show full error or object in promised expect

🚀 Feature Proposal
When using expect(promise).resolves or expect(promise).rejects, and having the opposite resolution than expected, only the error message or the type of the value are being shown, hidding information. OTOH, if awaiting the Promise object and fails, full exception with its trace is being shown. I think expect(promise) should show the full error with exception or the original value instead if receiving an unexpected resolution.
Motivation
Easier debugging, being able to have the original error object with the additional Promise related info details provided by expect(promise).
Example
No response
Pitch
Capture of failed Promises is already being done by Jest, I just only have the same behaviour when using expect(promise). Since it's returning a Promise itself, probably would make sense to put the original failed one in the cause field of the exception.

no stale

No stale

No stale.

No stale.

No stale

Using cause seems like a good idea 👍 wanna send a PR?

Using cause seems like a good idea 👍 wanna send a PR?

I would like to have the same behaviour both when using expect() or await. cause would make sense if we want expect() to throw a specific exception about the expectation and not the exception itself, in that case we can add it.


Support 1-dimensional matrix for HLSL

Closes #4395
This commit allows Slang to use 1-dimensional matrix when targetting HLSL. The 1-dimensional matrix is supported by DXC natively.
GLSL/Vulkan doesn't support the 1-dimensional matrix natively. It is not trivial for Slang to convert all of matrix functions to vector or scalar at the emitting step. We can implement this later if there are needs. This commit disallows the use of 1-dimensional matrix for targetting GLSL/Vulkan by the capability system; in other words, the new 1-dimentional functions have "[require(hlsl)]".

I spent some time implementing for GLSL but I realized that all of matrix functions need to be mapped to vector/scalar versions when one of dimensions is 1-dimensional.
That seemed overkill for a such a rare case support, and I retreated to support only for HLSL.


Python bindings give "AttributeError: auth_request_callback" when server returns 401

This issue is a repitition of # 35.
wsman-client.i:
/*

The Transport instance associated to the client
*/
WsManTransport *transport() {
wsmc_transport_init($self, NULL);
wsmc_transport_set_auth_request_func( $self, auth_request_callback );

return (WsManTransport *)$self;

}
/*

Send a (raw) SOAP request to the client

call-seq:
client.send_request(XmlDoc.new("<xml ...>...")) -> Integer

*/
int send_request(WsXmlDocH request) {
return wsman_send_request($self, request);
}
pywsman.py:
def transport(self):
    """transport(Client self) -> Transport"""
    return _pywsman.Client_transport(self)

**def auth_request_callback(self, *args):
    """auth_request_callback(Transport self, Client client, name auth_type)"""
    return _pywsman.Transport_auth_request_callback(self, *args)**

def send_request(self, *args):
    """send_request(Client self, XmlDoc request) -> int"""
    return _pywsman.Client_send_request(self, *args)

To solve the issue, pywsman.py has to be patched at line 1800 to 1802 as shown above.
Seems to be a problem of SWIG.

Which version of SWIG are you using ?

btw, #35 asked for community input from someone with more Python experience than myself.

On CentOS Linux release 7.8.2003 swig answers:
swig -version
SWIG Version 2.0.10
Compiled with g++ [x86_64-redhat-linux-gnu]
I am not sure whether it is a problem of this version. The problem was
already reported a long time ago, possibly with an older swig version.
Am Mo., 21. Sept. 2020 um 11:54 Uhr schrieb Klaus Kämpf <
<EMAIL_ADDRESS>
btw, #35 https://github.com/Openwsman/openwsman/issues/35 asked for
community input from someone with more Python experience than myself.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Openwsman/openwsman/issues/146#issuecomment-696014995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIARK464EPOYVDKH3UJXAXLSG4PGLANCNFSM4RPKFXYQ
.

SWIG 2 ??! :open_mouth: upstream is at 4 !

Yes, the newest rpm version installed by yum on CentOS7 is 2.
Ubuntu 18 newest installed package ist version 3.0.
Tomorrow I will install swig 4 by source and test again on CentOS.
Am Di., 22. Sept. 2020 um 18:11 Uhr schrieb Klaus Kämpf <
<EMAIL_ADDRESS>
SWIG 2 ??! 😮 upstream http://swig.org/ is at 4 !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Openwsman/openwsman/issues/146#issuecomment-696822655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIARK45JLS5P7FK5QBZVKH3SHDEC5ANCNFSM4RPKFXYQ
.

Quick Check with swig 3.0 on ubuntu 18, same issue.
Am Di., 22. Sept. 2020 um 20:50 Uhr schrieb Michael Stumpf <
<EMAIL_ADDRESS>
Yes, the newest rpm version installed by yum on CentOS7 is 2.
Ubuntu 18 newest installed package ist version 3.0.
Tomorrow I will install swig 4 by source and test again on CentOS.
Am Di., 22. Sept. 2020 um 18:11 Uhr schrieb Klaus Kämpf <
<EMAIL_ADDRESS>
SWIG 2 ??! 😮 upstream http://swig.org/ is at 4 !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Openwsman/openwsman/issues/146#issuecomment-696822655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIARK45JLS5P7FK5QBZVKH3SHDEC5ANCNFSM4RPKFXYQ
.

Attached you can find the file pywsman.py created by the latest version of
swig 4.0.2 (see header).
It includes a manually patch in line 2262 - 2265. I am not a swig expert,
perhaps the patch is not very correct, but it resolves the issue which
otherwise still exists.
Am Di., 22. Sept. 2020 um 21:20 Uhr schrieb Michael Stumpf <
<EMAIL_ADDRESS>
Quick Check with swig 3.0 on ubuntu 18, same issue.
Am Di., 22. Sept. 2020 um 20:50 Uhr schrieb Michael Stumpf <
<EMAIL_ADDRESS>
Yes, the newest rpm version installed by yum on CentOS7 is 2.
Ubuntu 18 newest installed package ist version 3.0.
Tomorrow I will install swig 4 by source and test again on CentOS.
Am Di., 22. Sept. 2020 um 18:11 Uhr schrieb Klaus Kämpf <
<EMAIL_ADDRESS>
SWIG 2 ??! 😮 upstream http://swig.org/ is at 4 !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Openwsman/openwsman/issues/146#issuecomment-696822655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIARK45JLS5P7FK5QBZVKH3SHDEC5ANCNFSM4RPKFXYQ
.


[BUG]: ModuleNotFoundError when running matcha provision

Contact details [optional]
No response
Tell us about the bug in plenty of detail
Just installed the tool via poetry add, got nothing else installed.
Running Python 3.12.0
Steps to reproduce the bug

poetry init
add matcha-ml
poetry install
activate venv
matcha provision

Any relevant log output
❯ matcha provision
Traceback (most recent call last):
  File "/Users/fschulz/dev/learn-matcha/.venv/bin/matcha", line 5, in <module>
    from matcha_ml.cli.cli import app
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/matcha_ml/cli/cli.py", line 6, in <module>
    from matcha_ml import __version__, core
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/matcha_ml/core/__init__.py", line 2, in <module>
    from .core import (
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/matcha_ml/core/core.py", line 6, in <module>
    from matcha_ml.cli._validation import get_command_validation
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/matcha_ml/cli/_validation.py", line 9, in <module>
    from matcha_ml.core._validation import is_valid_prefix, is_valid_region
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/matcha_ml/core/_validation.py", line 4, in <module>
    from matcha_ml.services import AzureClient
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/matcha_ml/services/__init__.py", line 2, in <module>
    from .azure_service import AzureClient
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/matcha_ml/services/azure_service.py", line 8, in <module>
    from azure.identity import AzureCliCredential, CredentialUnavailableError
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/azure/identity/__init__.py", line 10, in <module>
    from ._credentials import (
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/azure/identity/_credentials/__init__.py", line 11, in <module>
    from .default import DefaultAzureCredential
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/azure/identity/_credentials/default.py", line 20, in <module>
    from .vscode import VisualStudioCodeCredential
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/azure/identity/_credentials/vscode.py", line 22, in <module>
    from .._internal.macos_vscode_adapter import get_refresh_token, get_user_settings
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/azure/identity/_internal/macos_vscode_adapter.py", line 8, in <module>
    from msal_extensions.osx import Keychain, KeychainError
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/msal_extensions/__init__.py", line 11, in <module>
    from .cache_lock import CrossPlatLock
  File "/Users/fschulz/dev/learn-matcha/.venv/lib/python3.12/site-packages/msal_extensions/cache_lock.py", line 7, in <module>
    from distutils.version import LooseVersion
ModuleNotFoundError: No module named 'distutils'

❯ poetry show
azure-common             1.1.28     Microsoft Azure Client Library for Python (Common)
azure-core               1.29.5     Microsoft Azure Core Library for Python
azure-identity           1.15.0     Microsoft Azure Identity Library for Python
azure-mgmt-authorization 3.0.0      Microsoft Azure Authorization Management Client Library for Python
azure-mgmt-confluent     1.0.0      Microsoft Azure Confluent Management Client Library for Python
azure-mgmt-core          1.4.0      Microsoft Azure Management Core Library for Python
azure-mgmt-resource      23.0.1     Microsoft Azure Resource Management Client Library for Python
azure-mgmt-storage       21.1.0     Microsoft Azure Storage Management Client Library for Python
azure-mgmt-subscription  3.1.1      Microsoft Azure Subscription Management Client Library for Python
azure-storage-blob       12.18.3    Microsoft Azure Blob Storage Client Library for Python
backoff                  2.2.1      Function decoration for backoff and retry
certifi                  2023.7.22  Python package for providing Mozilla's CA Bundle.
cffi                     1.16.0     Foreign Function Interface for Python calling C code.
charset-normalizer       3.3.1      The Real First Universal Charset Detector. Open, modern and actively maintained alternative to Chardet.
click                    8.1.7      Composable command line interface toolkit
colorama                 0.4.6      Cross-platform colored terminal text.
commonmark               0.9.1      Python parser for the CommonMark Markdown spec
cryptography             41.0.5     cryptography is a package which provides cryptographic recipes and primitives to Python developers.
dataclasses-json         0.5.9      Easily serialize dataclasses to and from JSON
idna                     3.4        Internationalized Domain Names in Applications (IDNA)
isodate                  0.6.1      An ISO 8601 date/time/duration parser and formatter
marshmallow              3.20.1     A lightweight library for converting complex datatypes to and from native Python datatypes.
marshmallow-enum         1.5.1      Enum field for Marshmallow
matcha-ml                0.2.9      Matcha: An open source tool for provisioning MLOps environments to the cloud.
monotonic                1.6        An implementation of time.monotonic() for Python 2 & < 3.3
msal                     1.24.1     The Microsoft Authentication Library (MSAL) for Python library
msal-extensions          1.0.0      Microsoft Authentication Library extensions (MSAL EX) provides a persistence API that can save your data on disk, encrypted on Windows, macOS and Linux. Concurrent data access will ...
msrest                   0.7.1      AutoRest swagger generator Python client runtime.
mypy-extensions          1.0.0      Type system extensions for programs checked with the mypy type checker.
oauthlib                 3.2.2      A generic, spec-compliant, thorough implementation of the OAuth request-signing logic
packaging                23.2       Core utilities for Python packages
portalocker              2.8.2      Wraps the portalocker recipe for easy usage
pycparser                2.21       C parser in Python
pygments                 2.16.1     Pygments is a syntax highlighting package written in Python.
pyjwt                    2.8.0      JSON Web Token implementation in Python
python-dateutil          2.8.2      Extensions to the standard Python datetime module
python-terraform         0.10.1     This is a python module provide a wrapper of terraform command line tool
pyyaml                   6.0.1      YAML parser and emitter for Python
requests                 2.31.0     Python HTTP for Humans.
requests-oauthlib        1.3.1      OAuthlib authentication support for Requests.
rich                     12.6.0     Render rich text, tables, progress bars, syntax highlighting, markdown and more to the terminal
segment-analytics-python 2.2.3      The hassle-free way to integrate analytics into any python application.
shellingham              1.5.4      Tool to Detect Surrounding Shell
six                      1.16.0     Python 2 and 3 compatibility utilities
typer                    0.7.0      Typer, build great CLIs. Easy to code. Based on Python type hints.
types-pyyaml             <IP_ADDRESS>  Typing stubs for PyYAML
types-urllib3            <IP_ADDRESS> Typing stubs for urllib3
typing-extensions        4.8.0      Backported and Experimental Type Hints for Python 3.8+
typing-inspect           0.9.0      Runtime inspection utilities for typing module.
urllib3                  1.26.6     HTTP library with thread-safe connection pooling, file post, and more.

downgrading to Python 3.8 lets me run the command matcha provision, but finally results in another error:
⠦ 0:10:28 ApplyingWARNING:python_terraform:error: b'\nError: Provider configuration: cannot load Kubernetes client config\n\n  with provider["registry.terraform.io/hashicorp/kubernetes"],\n  on kubernetes.tf line 15, in provider "kubernetes":\n  15: provider "kubernetes" {\n\ninvalid configuration: [client-cert-data and client-cert are both specified\nfor custom. client-cert-data will override., client-key-data and client-key\nare both specified for custom; client-key-data will override]\n'
⠦ 0:10:28 Applying
Terraform failed because of the following error: '
Error: Provider configuration: cannot load Kubernetes client config

  with provider["registry.terraform.io/hashicorp/kubernetes"],
  on kubernetes.tf line 15, in provider "kubernetes":
  15: provider "kubernetes" {

invalid configuration:
'.

running matcha destroy to unprovision all created resources throws another error:
❯ matcha destroy

The following resources will be destroyed:

1. Azure Kubernetes Service (AKS): A kubernetes cluster
2. Two Storage Containers: A storage container for experiment tracking artifacts and a second for model training artifacts
3. Seldon Core: A framework for model deployment on top of a kubernetes cluster
4. Azure Container Registry: A container registry for storing docker images
5. ZenServer: A zenml server required for remote orchestration
6. Azure Resource Group: The resource group containing the provisioned resources
7. Matcha State Container: A storage container for tracking matcha state

Destroying the resources may take approximately 20 minutes. May we suggest you grab a cup of 🍵?

Are you happy for 'destroy' to run? [y/N]: y

⏳ Destroying Matcha resources...

⠼ 0:00:01 Destroying
Terraform failed because of the following error: '
Error: Failed to read variables file

Given variables file
/Users/fschulz/dev/learn-matcha/.matcha/infrastructure/resources/terraform.tfvars.json
does not exist.
'.


Chart loading time is too much

I am trying this code, and it's working fine but when I opened this link to other browser or incognito window then it's taking too much time and not loading many times.
This error showing in the browser console
Uncaught (in promise) Error: Preset not sepcified in configuration     at Object.config (webcontainer.a966dcc4085d3fff5bb.js:15)     at t.config (webcontainer.a966dcc4085d3fff5bb.js:15)     at Object.PREVIEW_INSTANTIATE_BUNDLE (preview-3a0c9433aa42f56dbd90b.js:1)     at preview-3a0c9433aa42f56dbd90b.js:1     at Array.map (<anonymous>)     at Object.dispatch (preview-3a0c9433aa42f56dbd90b.js:1)     at preview-3a0c9433aa42f56dbd90b.js:1

Have you tried that code within a Create React App or something?
You shouldn't use Stackblitz for performance testing - Stackblitz is downloading the Node dependencies and compiling the code in the browser, so isn't a true representation of a what happens in a real application. These would usually be done as part of a build process before deployment.

sorry, I didn't realize this. Yes, This performance issue is not in create-react-app


Google account token

I migrated my Nest account over to Google. Now I cannot use the script to get a token. Is there something I am missing?

Can you get a token by logging into https://home.nest.com on a desktop browser, and then going to the URL https://home.nest.com/session ? In the text output, I see an "access_token":"b.............." value and put that in my config.json file. But I haven't migrated to a Google Account yet.

same here, migrated to a google account and now my token (extracted from home.nest.com/session) expires very shortly, hope we can find a fix soon.

Guess I'm glad I didn't migrate it then for both this Nest-Cam and the -Nest Homebridge plugins. .

@muzzymate have you tried creating an app password in google and using that to login?

No I havent! Run me through that. Do you know if that works?
Sent from my iPhone

On Nov 14, 2019, at 8:34 PM, Beni Katznelson<EMAIL_ADDRESS>wrote:

@muzzymate have you tried creating an app password in google and using that to login?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

No I havent! Run me through that. Do you know if that works?
Sent from my iPhone

On Nov 14, 2019, at 8:34 PM, Beni Katznelson<EMAIL_ADDRESS>wrote:

@muzzymate have you tried creating an app password in google and using that to login?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

 No I havent! Run me through that. Do you know if that works?
…
Sent from my iPhone

On Nov 14, 2019, at 8:34 PM, Beni Katznelson @.***> wrote:  @muzzymate have you tried creating an app password in google and using that to login? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

So I deleted my comment because I realized afterwards that it wouldn't solve the problem. If you generate an app password for google it will just replace using a username and password to login. But the result of that is a token that will expire and that will need to be refreshed.
I think the only solution to the problem is to add code that will refresh your authentication token.


fix: Update menu link visibility for Mobile

Altered the css so the Menu links Dark Mode and X are no longer hidden by the site header on Mobile

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


Settings of "View changes" feature

How can I exclude files/folders from list? (e.g. bundle - I know that a bad practice to push bundle into git, but "C'est la vie")

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Unable to make femtolisp

Will it not build on OSX?
~/Pork/femtolisp on master
$ make
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c flisp.c -o flisp.o
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c builtins.c -o builtins.o
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c string.c -o string.o
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c equalhash.c -o equalhash.o
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c table.c -o table.o
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c iostream.c -o iostream.o
cd llt && make
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c flmain.c -o flmain.o
gcc -O3 -DNDEBUG -Wall -Wno-strict-aliasing  -DLINUX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -c bitvector.c -o bitvector.o
In file included from bitvector.c:36:
dtypes.h:32:22: error: features.h: No such file or directory
dtypes.h:33:20: error: endian.h: No such file or directory
dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from bitvector.c:32:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from bitvector.c:36:
dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from bitvector.c:32:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from bitvector.c:36:
dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from bitvector.c:32:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from bitvector.c:36:
dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from bitvector.c:32:
/usr/include/i386/endian.h:97:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from table.c:8:
llt/dtypes.h:32:22: error: features.h: No such file or directory
llt/dtypes.h:33:20: error: endian.h: No such file or directory
llt/dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from table.c:1:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from table.c:8:
llt/dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from table.c:1:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from table.c:8:
llt/dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from table.c:1:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from table.c:8:
llt/dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from table.c:1:
/usr/include/i386/endian.h:97:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from iostream.c:8:
llt/dtypes.h:32:22: error: features.h: No such file or directory
llt/dtypes.h:33:20: error: endian.h: No such file or directory
llt/dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from iostream.c:1:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from iostream.c:8:
llt/dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from iostream.c:1:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from iostream.c:8:
llt/dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from iostream.c:1:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from iostream.c:8:
llt/dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from iostream.c:1:
/usr/include/i386/endian.h:97:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from equalhash.c:8:
llt/dtypes.h:32:22: error: features.h: No such file or directory
llt/dtypes.h:33:20: error: endian.h: No such file or directory
llt/dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from equalhash.c:1:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from equalhash.c:8:
llt/dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from equalhash.c:1:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from equalhash.c:8:
llt/dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from equalhash.c:1:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from equalhash.c:8:
llt/dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from equalhash.c:1:
/usr/include/i386/endian.h:97:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from builtins.c:16:
llt/dtypes.h:32:22: error: features.h: No such file or directory
llt/dtypes.h:33:20: error: endian.h: No such file or directory
llt/dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from builtins.c:5:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from builtins.c:16:
llt/dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from builtins.c:5:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from builtins.c:16:
llt/dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from builtins.c:5:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from builtins.c:16:
llt/dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from builtins.c:5:
/usr/include/i386/endian.h:97:1: warning: In file included from llt/llt.h:5,
                 from string.c:16:
llt/dtypes.h:32:22: error: features.h: No such file or directory
llt/dtypes.h:33:20: error: endian.h: No such file or directory
llt/dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from string.c:4:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from string.c:16:
llt/dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
this is the location of the previous definitionIn file included from /usr/include/machine/endian.h:35
,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from string.c:4:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from string.c:16:
llt/dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from string.c:4:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from string.c:16:
llt/dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from string.c:4:
/usr/include/i386/endian.h:97:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flmain.c:14:
llt/dtypes.h:32:22: error: features.h: No such file or directory
llt/dtypes.h:33:20: error: endian.h: No such file or directory
llt/dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flmain.c:1:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flmain.c:14:
llt/dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flmain.c:1:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flmain.c:14:
llt/dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flmain.c:1:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flmain.c:14:
llt/dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flmain.c:1:
/usr/include/i386/endian.h:97:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flisp.c:45:
llt/dtypes.h:32:22: error: features.h: No such file or directory
llt/dtypes.h:33:20: error: endian.h: No such file or directory
llt/dtypes.h:34:1: warning: "LITTLE_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flisp.c:32:
/usr/include/i386/endian.h:93:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flisp.c:45:
llt/dtypes.h:35:1: warning: "BIG_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flisp.c:32:
/usr/include/i386/endian.h:94:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flisp.c:45:
llt/dtypes.h:36:1: warning: "PDP_ENDIAN" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flisp.c:32:
/usr/include/i386/endian.h:95:1: warning: this is the location of the previous definition
In file included from llt/llt.h:5,
                 from flisp.c:45:
llt/dtypes.h:37:1: warning: "BYTE_ORDER" redefined
In file included from /usr/include/machine/endian.h:35,
                 from /usr/include/sys/wait.h:193,
                 from /usr/include/stdlib.h:65,
                 from flisp.c:32:
/usr/include/i386/endian.h:97:1: warning: this is the location of the previous definition
make[1]: *** [bitvector.o] Error 1
make: *** [equalhash.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [llt/libllt.a] Error 2
make: *** [string.o] Error 1
make: *** [builtins.o] Error 1
make: *** [iostream.o] Error 1
make: *** [table.o] Error 1
make: *** [flmain.o] Error 1
In file included from operators.c:5,
                 from cvalues.c:1,
                 from flisp.c:390:
llt/ieee754.h:14: error: duplicate member ‘mantissa’
llt/ieee754.h:15: error: duplicate member ‘exponent’
llt/ieee754.h:15: error: duplicate member ‘({anonymous})’
llt/ieee754.h:16: error: duplicate member ‘negative’
llt/ieee754.h:16: error: duplicate member ‘({anonymous})’
llt/ieee754.h:16: error: duplicate member ‘({anonymous})’
llt/ieee754.h:34: error: duplicate member ‘mantissa1’
llt/ieee754.h:35: error: duplicate member ‘mantissa0’
llt/ieee754.h:35: error: duplicate member ‘({anonymous})’
llt/ieee754.h:36: error: duplicate member ‘exponent’
llt/ieee754.h:36: error: duplicate member ‘({anonymous})’
llt/ieee754.h:36: error: duplicate member ‘({anonymous})’
llt/ieee754.h:37: error: duplicate member ‘negative’
llt/ieee754.h:37: error: duplicate member ‘({anonymous})’
llt/ieee754.h:37: error: duplicate member ‘({anonymous})’
llt/ieee754.h:37: error: duplicate member ‘({anonymous})’
llt/ieee754.h:56: error: duplicate member ‘mantissa1’
llt/ieee754.h:57: error: duplicate member ‘mantissa0’
llt/ieee754.h:57: error: duplicate member ‘({anonymous})’
llt/ieee754.h:58: error: duplicate member ‘exponent’
llt/ieee754.h:58: error: duplicate member ‘({anonymous})’
llt/ieee754.h:58: error: duplicate member ‘({anonymous})’
llt/ieee754.h:59: error: duplicate member ‘negative’
llt/ieee754.h:59: error: duplicate member ‘({anonymous})’
llt/ieee754.h:59: error: duplicate member ‘({anonymous})’
llt/ieee754.h:59: error: duplicate member ‘({anonymous})’
llt/ieee754.h:60: error: duplicate member ‘empty’
llt/ieee754.h:60: error: duplicate member ‘({anonymous})’
llt/ieee754.h:60: error: duplicate member ‘({anonymous})’
llt/ieee754.h:60: error: duplicate member ‘({anonymous})’
llt/ieee754.h:60: error: duplicate member ‘({anonymous})’
make: *** [flisp.o] Error 1

I try to compile with mingw64 on Windows and I get the following error:
c:\src\femtolisp>make
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPU
TED_GOTO -c flisp.c -o flisp.o
In file included from llt/llt.h:5:0,
                 from flisp.c:46:
llt/dtypes.h:29:0: warning: "WIN32" redefined
 #  define WIN32
 ^
<built-in>: note: this is the location of the previous definition
In file included from llt/llt.h:6:0,
                 from flisp.c:46:
llt/utils.h:10:6: error: #error "unsupported target: 16-bit x86"
 #    error "unsupported target: 16-bit x86"
      ^
Makefile:26: recipe for target 'flisp.o' failed
make: *** [flisp.o] Error 1

c:\src\femtolisp>

Can somebody help me please?

I'm seeing a different problem on current macOS:
I followed the readme for building femtolisp on current macOS. It fails with the following errors:
cc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt -DUSE_COMPUTED_GOTO -DMACOSX -DARCH_X86_64 -DBITS64 -D__CPU__=686 -I"/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/Developer/Headers" flisp.o builtins.o string.o equalhash.o table.o iostream.o flmain.o
-o flisp llt/libllt.a -lm -framework ApplicationServices libflisp.a
ld: warning: ld: warning: ignoring file libflisp.a, file was built for archive which is not the architecture being linked (x86_64): libflisp.aignoring file llt/libllt.a, file was built for archive which is not the architecture being linked (x86_64): llt/libllt.a
Undefined symbols for architecture x86_64:
"_D_NINF", referenced from:
_isnumtok_base in flisp.o
"_D_NNAN", referenced from:
_isnumtok_base in flisp.o
"_D_PINF", referenced from:
_isnumtok_base in flisp.o
....
So it appears that the linker command is not correct. Also, the SDK header path does not seem to be used (and carbon is no longer available on 64 bit platforms). I was able to compile without the above SDK header path.


Feature Request: iCloud Settings Backup

Feature Request
With the addition of community videos (which require custom links) as well as the addition of numerous other ways to modify settings in Aerial, I would like to recommend the addition of iCloud Backup support for settings.
This would allow for a few useful things:

Any time a computer is wiped and Aerial is installed again, the user can be prompted to restore settings.
A user that wants to keep Aerial consistent across multiple Apple Devices could sync the settings across all devices.
When community videos are purchased, the link is given in a temporary manner. This means that there's no way to get back to the link should they be disassociated in the future. Having a backup would save these links in iCloud

Thanks!
P.S. It should be noted that if this is implemented, I would not expect iCloud backup of the videos themselves, just the settings text. Additionally, DropBox support could be warranted here as well, but I think should be secondary given how small the settings file would be. Even a free iCloud account should be able to support that.

So in order to use iCloud, you need to setup an entitlement, and I can't do that for a screensaver since I can't set my own entitlements (we live under legacyScreenSaver's entitlements). So long story short, not possible.
(Dropbox, nope, never)

What about a manual export and manual import option to save it as a document that we can then import ourselves?

I'll put it on my maybe list

What about a manual export and manual import option to save it as a document that we can then import ourselves?

I'd really love&appreciate it! Have it been implemented?


Build using Ninja on Windows and Linux Desktop

What does this Pull Request accomplish?
Update the build step to use the ninja build system for both Windows and Linux. Also simplifies the build steps and removes things that were not being used.
Also a side note is that on Windows using ninja provides better developer efficiency as it appears to track dependencies better and reduces the amount of things being rebuilt after a first full build unlike Visual Studio which I have experience rebuilding much of the project over repeatedly even though there were no changes to those files. This doesn't help with the build but might help with developers wanting to build grpc-device this way.
Why should this Pull Request be merged?

Build times are reduced using ninja

Windows Average build times

Before Change: 1 hr 30 min
After Change: 50 min (about a 45% build time reduction)

Linux Average build times

Before Change:  1 hr
After Change: 50 min (about a 17% build time reduction)

The steps have been simplified to just cmake command calls making it easier to understand.
Removed things like CMAKE_VERSION which didn't appear to be doing anything as the build before were using the version that was provided by the github provided runner images.

What testing has been done?

PR Build

Windows still specifies using MSVC 19.40.33811.0 for the CC and CXX compilers
Linux still specifies using GNU 9.4.0 for the CC and CXX compilers

This one's good to go whenever you're ready since Alex is out.


Streamline builds (dependency resolution)

User story
As a developer/user, I want the dependencies to be as optimized as possible, so I can install the package as quickly as possible.
Acceptance criteria

[ ] When the package is installed via pip, botocore is installed without downloading a lot of different versions
[ ] pyminizip is installed via conda-forge.

Sprint Ready Checklist

[ ] 1. Acceptance criteria defined
[ ] 2. Team understands acceptance criteria
[ ] 3. Team has defined solution / steps to satisfy acceptance criteria
[ ] 4. Acceptance criteria is verifiable / testable
[ ] 5. External / 3rd Party dependencies identified
[ ] 6. Ticket is prioritized and sized

Notes
Here is the output for botocore:
Collecting s3transfer<0.7.0,>=0.6.0
  Using cached s3transfer-0.6.0-py3-none-any.whl (79 kB)
Collecting boto3
  Using cached boto3-1.26.87-py3-none-any.whl (134 kB)
  Using cached boto3-1.26.86-py3-none-any.whl (134 kB)
  Using cached boto3-1.26.85-py3-none-any.whl (134 kB)
  Using cached boto3-1.26.84-py3-none-any.whl (134 kB)
  Using cached boto3-1.26.83-py3-none-any.whl (134 kB)
  Using cached boto3-1.26.82-py3-none-any.whl (134 kB)
  Using cached boto3-1.26.81-py3-none-any.whl (134 kB)
  Using cached boto3-1.26.80-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.79-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.78-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.77-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.76-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.75-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.74-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.73-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.72-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.71-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.70-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.69-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.68-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.67-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.66-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.65-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.64-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.63-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.62-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.61-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.60-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.59-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.58-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.57-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.56-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.55-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.54-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.53-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.52-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.51-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.50-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.49-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.48-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.47-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.46-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.45-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.44-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.43-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.42-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.41-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.40-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.39-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.38-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.37-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.36-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.35-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.34-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.33-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.32-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.31-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.30-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.29-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.28-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.27-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.26-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.25-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.24-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.23-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.22-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.21-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.20-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.19-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.18-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.17-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.16-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.15-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.14-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.13-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.12-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.11-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.10-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.9-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.8-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.7-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.6-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.5-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.4-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.3-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.2-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.1-py3-none-any.whl (132 kB)
  Using cached boto3-1.26.0-py3-none-any.whl (132 kB)
Collecting google-cloud-core<3.0dev,>=2.3.0

For botocore and boto3, we can probably pin it those versions to:
boto3                         1.26.0
botocore                      1.29.0


Zoom in and zoom out pdf

This PR is a collaboration with @philmcmahon and @joelochlann
What does this change?
This PR updates the pdf viewer with zoom-in/zoom-out functionality. It adds a scale state to the PageViewer which is used to control the container size and as a result controls how big or small the page should be rendered.
A new function refreshPreview is added in the  in PageCache class, that is responsible to update the existing preview in cache by rendering a new page and replacing the current preview in cache with the new preview. This way we avoid calling the server to retrieve preview for the page number.
In PdfHelpers, a new function updatePreview is implemented and when given the preview and a container size it renders a new page for that container size.
In the Page component, the pageHeight added to the component properties, is used to trigger updating the existing canvas with the canvas of the new preview.
Because we always render only 3 pages at a time (for performance reasons), it was made sure that when the page range changes, the page in the new range is re-rendered if the scale (container size) has changed.
Below is demoing a long vertical page pdf and how the zooming and finding works.

Below is demoing a landscape page pdf and how the zooming and finding works.

Below is demoing how the zooming works with search query.

TODO in future PRs:

When using the zoom with search query avaiable, it's responding more slowly. Also, some pages could be left un-rendered!! this was resolved
when clicking on zoom for several times e.g. 3 time, the page is rendered 3 times. For optimisation, we could maybe cancel the previous rendering tasks!? this is now resolved by using debounce & useMemo
We could give user control on the scale of zooming e.g. 100%, 150%, etc.
Currently a new function is created in PageCache in order to refresh and re-render the relevant pdf page based on the container size. But this is not fully optimised, because it's replacing the existing cache, while it's best if we could just add to the cache in case the old preview size is needed again in the future. Since this optimisation needs change in the cache logic, and needs extra care, I will create a ticket to do this work separately.

🎉 This is superb work @marjisound! The page viewer clientside code is notoriously complex so getting a working PR up so quickly is a huge accomplishment. Was also really fun pairing on it 🤓
I was going to say that most of the remaining things weren't blockers and could be fixed in subsequent PRs.
But... I just spotted one other thing. There is a noticeable flicker after loading, without touching any of the zoom functionality. Adding some logging in here, it seems that we're now doing an unnecessary re-render.
Since this affects the render even when not using the zoom functionality, it probably needs to be resolved before merging. 😔
before

after

@joelochlann Thanks so much Jo for looking at the re-rendering issue. I had actually noticed that as well and was digging to find a fix for it. I'll definitely fix it and will let you know to look again when it's ready. I've also found a fix for the horizontal scrolling issue and will let you know when that's pushed as well (needs a bit of cleaning up). I'm off the rest of afternoon, so will be doing it tomorrow if that's OK?

Nice work fixing the double-render issue! 🎉
It seems to be working well when zooming into the first page of a document.
However, something is off with the vertical scroll position that becomes evident when you zoom into a high-numbered page on a multi-page doc.
Here, I zoom into page 28, but end up on page 16:
https://github.com/guardian/giant/assets/5122968/b99fc040-8e4e-4429-94b3-15e6d63d305b

Oh, I guess it's just that the scrollbar needs to be adjusted because the total height of its container has changed, i.e. it was at pixel 1000 of 1000 pixel total height (end of doc), but then on zoom it's at pixel 1000 of a 2000 pixel total height (middle of doc)


feat: Added icons - binding, bill, file-paper

Description
This PR adds binding-new, bill-line, file-paper-2-line
Fixes #https://github.com/appsmithorg/appsmith/issues/27142
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual on storybook
Manual on main repo
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/generate-alpha


Websocket transport for the JS driver

https://github.com/rethinkdb/rethinkdb/pull/4211 got closed; I'm making an issue here.  Maybe this would be useful to somebody... in some application.  Note my comment at the end about the licensing.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

It's unclear why Github says I added the enhancement and question labels.


Afreeca tv 19+ streams?

Ive tryed using livestreamer to watch the 19+ streams but ive had no success. I can watch the other ones. Can anyone help me?

afreecatv is working for you with livestreamer?

yes it is

#1303 How is yours working? There is an active post about afeeecatv no longer working.

http://livestreamer-builds.s3.amazonaws.com/livestreamer-latest-win32.zip
i used this and it worked

I tried it with the version you provide, but I'm still getting the same message. This is very odd.

try this command "livestreamer afreeca.com/das18121"

wow thanks that worked. so instead of afreecatv.com its afreeca.com.

Same problem to me. 19+ streams no work.
I did this guide http://defiler.ru/?ft=4444 with changed afreecatv.pyc and hls.pyc
How to get worked 19+ streams now?

Try this
livestreamer.zip
to watch 19+ streams you have to load the stream before the streamer changes to 19+, however if the streamer is already streaming 19+, you cant watch.

Yes we need that fix if the streamer already took 19+
I'm sure someone will find a way to pass the limitation


(ruby.portable) Migrate package, update code and metadata, add AU

Description
This migrates in ruby.portable.
The metadata is updated in accordance with the ruby package's metadata, the package is switched to embedded, and the install script code style is updated.
An AU script is also added,
Motivation and Context
Part of #1757
Should not be merged until #1786 is merged
How Has this Been Tested?
Ran update.ps1 to validate that it creates packages for the various minor releases (2.4 and newer).
Installed and uninstalled packages in test env to validate that they work.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[x] My change requires a change to documentation (this usually means the notes in the description of a package).
[x] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues Add the different issues underneath, and tick those that are fixed in this PR
[x] File removal PR
[x] The migration guidelines have been followed

:white_check_mark: Package verification completed without issues. PR is now pending human review

:white_check_mark: Package verification completed without issues. PR is now pending human review

@AdmiringWorm Updated this PR, thanks for the review. I think the formatting should be ok now?

:white_check_mark: Package verification completed without issues. PR is now pending human review

The Code Owners has been decided upon, as such I have merged this PR now.
@TheCakeIsNaOH thank you for updating the package and getting it here.


chore(build): get rid of obsolete Go build tags

What this PR does / why we need it:
Since Go 1.18 the new directive //go:build is now preferred and the toolchain will actively remove old directives; as mentioned in Go 1.18 release notes:

In Go 1.18, go fix now removes the now-obsolete // +build lines in modules declaring go 1.18 or later in their go.mod files.

KIC  specifies in go.mod Go version 1.20.

Which issue this PR fixes:
It's part of the https://github.com/Kong/team-k8s/issues/286

Codecov Report
Patch coverage has no change and project coverage change: -34.00 :warning:

Comparison is base (bc6cc42) 59.70% compared to head (8496b6b) 25.70%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #723       +/-   ##
===========================================
- Coverage   59.70%   25.70%   -34.00%
===========================================
  Files          43       43
  Lines        3474     3474
===========================================
- Hits         2074      893     -1181
- Misses       1131     2448     +1317
+ Partials      269      133      -136

Flag
Coverage Δ

integration-test
25.70% <ø> (-34.00%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 31 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Multiple private folder support

Pretty self explanatory, the code detects if the privateDir configuration option is an array, and if so it does the same operation on all of the directories inside the array, if its in interactive mode, it asks what to do once and then executes the same action on all of them unless the "allDifferent" configuration option is set to true which if so it asks what to do multiple times.
This sounds a bit complicated but I would imagine its as simple as a single for loop and a few configuration tweaks.

I think I might give this issue a try. Could you please assign me?

@OllyFN Just to make sure. Do you want allDifferent only accessible in interactive mode, or should there be a way of using allDifferent for auto? For example, an array of actions?

@LyubomirT allDifferent wouldn't affect the auto mode as that mode requires no user input so it would execute the same action for all the all the privateDirs regardless of the allDifferent setting but if you have any ideas I'm open to hearing them

@LyubomirT allDifferent wouldn't affect the auto mode as that mode requires no user input so it would execute the same action for all the privateDirs regardless of the allDifferent setting but if you have any ideas I'm open to hearing them

I'm thinking about implementing something like:
const defaultConfig = {
  debug: {
    showCopied: false,
    showNotCopied: false,
  },
  publicDir: "dir",
  privateDir: [{"dir1": stuff}, {"dir2": stuff}]
  excludeDirs: excludeDirs,
  overrideExceptions: [],
  addExcludes: [],
  interactive: false,
  override: true,
  allDifferent: true,
};

Means that normal actions will only work for single-directory / allDifferent: false while the array type will include parameters for directories. Might not be the most convenient way to do that, though...

@LyubomirT That sounds like a great idea, how about having 3 different ways to initialize privateDir, string which points to a single directory, array of strings which points to multiple directories with all executing the same action and array of objects with the key being the directory and the value being some privateDir actions array or config, unsure if you want to do all the work yourself as I'm happy to help you with this.

@LyubomirT That sounds like a great idea, how about having 3 different ways to initialize privateDir, string which points to a single directory, array of strings which points to multiple directories with all executing the same action and array of objects with the key being the directory and the value being some privateDir actions array or config, unsure if you want to do all the work yourself as I'm happy to help you with this.

Sounds good! I'll take note of that when implementing the update. And don't worry about me doing all the work myself, I'm actually very happy to contribute to the project, and as it seems appealing to me it would be even somewhat fun for me to work on this, rather than difficult.

@OllyFN Currently implementing a solution for the issue. I found out that if I use the method of automatically determining the private dir execution type, allDifferent will have to only be used for interactive as it will be completely useless for auto. Does that sound alright for you?

@LyubomirT Yup, that sounds about right

@LyubomirT Yup, that sounds about right

Roger that, thanks for the info.

@OllyFN The base algorithm is now done for both Auto and Interactive. Interactive is a bit broken at the moment now (I have some useless iterations present), I'll create the pull request when I return from this consultation with a doctor and finish some documents. Might take a while, though.

@LyubomirT That sounds great, take your time, I appreciate your work & interest in the project a lot

@OllyFN Sorry for the delay, I couldn't continue working on the update due to having to travel to a different city. 🙏
I'll let you know when I'm done.

Update
Stuck with some sort of infinite loop, trying to patch stuff up.

Update
Stuck with some sort of infinite loop, trying to patch stuff up.

Update
Almost done with the interactive mode, and finished with auto completely—just final touches remaining.

@OllyFN Done! Please take a look at #7 and let me know if you would like to change something.


chore: update golang version to 1.22.2

Description
Changes proposed in this pull request:

update golang to 1.22.2 (both builder and used go patch version)

Related issue(s)

closing as go version 1.22.5 was released


Travis CI Builds are way too long

The Travis CI builds are too long, after a commit it takes > 2 hours – not minutes – to get the final result. There are builds taking almost 30 minutes and a total build count of 20 is huge.

Here's an idea:
Some days ago, travis added support for Cron Job Builds1) (per day / week / month). This allows following splitting:

Fast Builds (each commit) — Some fast builds (~ 5 min total) for each commit that (a) build the project, (b) execute the tests and (c) do some checking steps like Coveralls
Slow Builds (Cron) — all the extensive other builds, eg. gtest builds, autotools, rare compilers etc.

This will give fast feedback for commits / PR's while maintaining the exhaustive build suite2).

1) I use them in some other projects, really nice feature.
2) This also allows some kind of nightly builds or version. That's full tested and created by the cron.

Yeah, I guess that makes sense.

I think some of the build count comes from the recent additions of Mac OSX.  It's probably not needed to run all of the same build tools as we do on the other environments there, mostly just need to check the compiler.  I think that was mentioned on a different pull request when Mac OSX got added.
That said, it appears that cmake is faster than autotools, so does it make sense to keep those then?  I don't know enough off the top of my head what the check_all target does under autotools, so maybe there's more going on there than needs too for the quick build.  It looks like the coverage build runs using the cmake toolchain, so maybe just run that configuration (cmake_coverage) for each compiler and platform only?  That would be 4 builds that run for each commit, serially probably about 5-10 minutes, with parallel builds (seems to be the default behavior) less.
Some questions, do the cron job builds only run if the repository has changed, or do they always run?  What do they run against (my first guess would be master)? Do we have a way to force a full build if the PR is changing stuff that is normally only checked during the cron job build?

Some questions, do the cron job builds only run if the repository has changed, or do they always run? What do they run against (my first guess would be master)? Do we have a way to force a full build if the PR is changing stuff that is normally only checked during the cron job build?

They run always, you can select between once a day, a week or a month. The branches are selected in the settings, so eg. "master once a day"* and "feature-xy once a week". Have a look at the travis blog article, there's a screenshot showing the options.
As cron builds do not depend on any commit or PR, I don't know whether it's possible build on a PR. But a build > 2 h is really long, even for a PR. Better give a fast feedback. Or maybe there's a wildcard for branch selection.

Well, Mac builds are terrible slow in Travis, they said they would improve servers but I guess they are not being able to handle it.
Depending on where you are commiting, some travis builds might work fine while others will not. Mac build were added after a difference between OSX LLVM and other platforms headers were detected. Anyways, maybe we don't need all that Mac builds.
What I do is to do the CI on my own fork, there I'll select which builds I'll run whenever I push. I'll only let all the builds go trough if I am about to Pull Request.

I guess we can close here 👍


support REDIS_REPLY_EMPTY_ARRAY  as a new return type.

In case of hgetall where key doesn't exist,  there is an empty array, isn't it more convenient to add a new return type for this
instead of array type with elements = 0.
It could be equivalent to NIL in case of get command.

What's your thinking behind that?
Due to Redis semantics, an empty array (RESP2) or an empty map (RESP3) convey to the caller that the key does not exist, as Redis does not store zero length keys.
how would the new type be useful?

thanks for your reply @michael-grunder
I know it's not an issue, it's about convenience, so instead of checking the reply->type == REDIS_REPLY_ARRAY and then check if reply->elements == 0  to decide if the key exists, we could decide that the key doesn't exist if we added this new return type  REDIS_REPY_EMPTY_ARRAY.

I can see where you're coming from but unfortunately we can't actually change this as it would be a massive breaking change (also Redis would need to be changed as well).
What I would suggest is doing this check in your app in a convenience function.


Multiverse - World keeps unloading

Hey there,
Every-time I make a new world, when I restart the server and use the command "/mv list" the world is renamed "1" and it says unloaded next to it.
Also in the   multiverse.core   worlds.yml   it is renamed 1 and I get the following line in the config that clearly shouldn't be there:
spawnLocation:
==: MVNullLocation (It's a bug if you see this in your config file)
How do I stop my new world unloading?
Many thanks,
Matt.

I have this error too.

I have the same issue :(

I am still having this issue on my server, even after the command

@RPS1222 This is from 2012. Request assistance in the Discord or make a new ticket.


Is it available for Kde , i am using kubuntu.

Is it available for Kde , i am using kubuntu.

Fly-Pie is only available for GNOME. However, I am currently working on its cross-platform successor Kando, which also supports KDE. You can follow its progress and support the project on my Ko-fi page :wink:.


added translation to spanish of several sections

Some sections have no links or special formatting.

Awesome, thank you so much @nelruk for this PR. Little by little, block by block, we'll have this paper in spanish soon 🙌🏽.
Read over and fixed a few typos, overall good job. I saw your comment on formatting in line 32 and didn't see any issues, looks like it's linking to the 'Background' div just fine. We can fix anything later at any time.
This PR brings up good questions on how should we translate some terms:

I like how 'la Fundación Democracy Earth' sounds.
Should blockchain be translated to 'cadena de bloques'?
smart contract: 'contratos inteligentes'?
VOTE (token) == 'voto'?

Maybe there's not a right or wrong answer, not sure what will be most understandable for most people. Pinging @santisiri in case you have an opinion.
This is a good start though, let's keep up the good work 👍. Will merge this PR now.


Update osmdroid-android-binding for Xamarin to latest version

@neilboyd it looks like the Xamarin component is out of date.  Please update to the latest.

See OsmdroidXamarin issue 8

It is possible to get the latest metadata.xml for xamarin?


[supply] when promoting to rollout release notes are not being updated.

Question Checklist

[yes] Updated fastlane to the latest version
[yes] I read the Contribution Guidelines
[yes] I read docs.fastlane.tools
[yes] I searched for existing GitHub issues

Question Subject
Supply
Question Description
When uploading the app to beta track release notes are being uploaded but when promoting it to rollout the release notes are not being uploaded. Here are the lanes to deploy and promote:
  desc "Deploy a new version to Google Play Beta track"
  desc 'Options:'
  desc ' - `brand` (required).'
  lane :deploy_to_store do |options|
    flavor = ANDROID_PRODUCTION_FLAVORS[options[:brand]]
     if flavor
        upload_to_play_store(
          package_name: ANDROID_PRODUCTION_PACKAGE_NAMES[options[:brand]],
          json_key: get_google_play_api_access_key(options[:brand]),
          metadata_path: 'fastlane/'+options[:brand]+'/metadata/android',
          track: 'beta',
          aab: '/home/circleci/react_courier/output/'+flavor.sub(flavor[0],flavor[0].downcase)+'Release.aab',
        )
      else
          UI.user_error!("Incorrect brand provided")
      end
  end

  desc "Promote specific brand app from beta track to production with a rollout %"
  desc 'Options:'
  desc ' - `rollout` (required).'
  desc ' - `brand` (required).'
  lane :promote_app_to_production do |options|
      if options[:rollout]
        supply(
          package_name: ANDROID_PRODUCTION_PACKAGE_NAMES[options[:brand]],
          json_key: get_google_play_api_access_key(options[:brand]),
          track: 'beta',
          track_promote_to: 'rollout',
          rollout: options[:rollout],
          skip_upload_apk: true,
          skip_upload_aab: true,
          skip_upload_metadata: false,
          skip_upload_images: true,
          skip_upload_screenshots: true,
         )
     else
         UI.user_error!("Parameter rollout must be provided")
     end
  end

Looking into!

@mhdtouban I'm having a hard time replicating this 🤔 Is rollout still a valid track? I think what you are looking to do is go from beta to production and specify a value in the rollout option, right? And pre-thanks for helping me understand this 😊

thanks for looking into that @joshdholtz right I want to promote the app from beta to production and according to docs the track has to be rollout and the user fraction is provided with a rollout parameter. https://docs.fastlane.tools/actions/supply/#parameters

this has already worked out but the release notes were only uploaded to beta track and weren't uploaded when promoting to production aka running promote_app_to_production

Can you try changing your track_promote_to: 'rollout' to track_promote_to: 'production' and see if that takes the release notes with you? When I to go from beta to production, my release notes ended up going with my app 🤔

the thing when you do track_promote_to: 'production' the user fraction (rollout parameter) won't work and thus you end up having a full release

Ah, really? I thought that was working for me 😱 Lemme try again!

yeah this is pretty confusing and caused us having a major release rollout to 100% of our users.. the docs needs to be much clearer since it says
rollout: The percentage of the user fraction when uploading to the rollout track
but also the track description doesn't list the rollout track:
The default available tracks are: production, beta, alpha, internal

I see the issue now! 😱 Going to fix and then update the docs too

@joshdholtz I saw your changes now and updated doc. Just a question here, if we want to release to prod with user fraction we would use the production track with the rollout parameter and the release_status would be inProgress and when we want to have a complete rollout we update the  release_status to completed? Also, the release notes would be uploaded when we set release_status to completed   Let me know if am missing anything here.

If you wanted to do a rollout production (in the next version which will be 2.136.0), you would set...
track: “beta”,
track_promote_to: “production”,
rollout: 0.5

or something to that effect ☝ That will promote with a rollout (unlike in the current live version)


List force upgraded dependencies for a particular group / artifact

One of the potential sources of binary compatibility issues is when an artifact is compiled with v1 of a dependency, and the wrapper is compiling with v2. Being able to list cases where dependencies specified for a particular group id or artifact are bumped might be helpful for identifying these issues early.

this was already done in #16


Add reactive hooks

Added @when_not('ruby.installed') in place of @hook('install')
Added ruby_avail handler, config.changed handler for ruby version

This also fixes an issue where ruby gets re-downloaded and re-installed every time the install hook runs.

Thanks!


Files with numeric prefixes are sorted incorrectly.

See https://github.com/benweet/stackedit/pull/1497
I order my files by prepending a number.
1. Filename
2. Filename
10. Filename
20. Filename

The default collation does not use the numeric option, so my files get ordered like this:
1. Filename
10. Filename
2. Filename
20. Filename

Should be fixed in v5.14.

@benweet I have a better version of this that handles 1.25, 1.5, etc.  Interested?


[otbn] Produce an area estimate for the final netlist (gold)

Assess the area impact of planned features and add them to the current area.

estimate 2

Done, discussed in the meeting today and added to the planning spreadsheet.


Open Grants Program application for project Pearlmanent

Grant Application Checklist

[x] The application-template.md has been copied, renamed ( "project_name.md") and updated.
[x] A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[x] The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).
[x] The grant will only be announced once we've successfully delivered the first milestone.

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

Thanks for the application and all the effort you put into this. However, most of the technical deliverables already exist in our ecosystem or are currently under development. For example, you should take a look at FRAME Pallet: NFTs for Substrate or NFT Parachain by usetech and obviously the balance module also already exists. We only support projects via our grants program that develop new open source software for our ecosystem (plus research). I’m therefore closing the application for now. Feel free to reapply with a project that focuses on unique code/research, which you need to develop for your project. Btw. you might also want to take a look at the nft strategy for kusama: https://kusama.polkassembly.io/post/303 and the different initiatives around it.


API create resource

Send metadata through API and create -work- item
I am working in my lms, I create instance of the book 'history of Bruges', that not yet exists: I can send titel, author via API to sinopia in order to create a work-record, in the response I can get the identifier that I can add to my record in my own lms
Describe alternatives you've considered
Once a week do a manuel export (lms) import (sinopia) and add identifiers to lms-records

Closing as this functionality is already supported from the Sinopia API.


Activity tracking using flutter

I am developing activity tracker desktop application for business organisations, as part of that i need to capture current active desktop at random intervals. But i was able to capture current widget of flutter application always even I am using any other applications. I want to track all activities on the machine while flutter application is running in background. for example when flutter app is running in background and chrome is active on screen, it should capture present visible screen of the machine.
Is this possible with flutter?

Hi @Jagadeesh09-dev,
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this.
You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


White screen when created build version for Cordova

I used xCode to compiled the iOS app. When app installed and started, it's showing white screen. I have external js files placed in assets/js/. Those files are not moving to /www folder

Hello @asifkilwani
Firstly you need to learn how webpack works for use this template. You can use static folder for static assets (  ) or you can assign a variable into the vue for non-static assets:
<template>

</template>

Have a great day!


Memory leak when contiune update config file which wunderctl started by up command

Bug description
1: use cmd start server:
wunderctl --debug true --wundergraph-dir wundergraph/examples/simple/.wundergraph
2: update wundergraph.config.json
3: use memory continue increase
4: i think this is because NewInMemory continue apply memory but not relase
How to reproduce

Expected behavior
No response
WunderGraph information

Environment & setup

OS:  mac os
Go version:  go version go1.19 darwin/arm64
Database:
Node.js version:

WunderCtl Version

commit: be612bb

func NewInMemory(maxSize int64) (*InMemoryCache, error) { 	inMemoryCache, err := ristretto.NewCache(&ristretto.Config{ 		NumCounters: maxSize / 10, 		MaxCost:     maxSize, 		BufferItems: 64, 	}) 	if err != nil { 		return nil, err 	} 	return &InMemoryCache{ 		c: inMemoryCache, 	}, nil }
it will continuse apply memory when config.json changes, i thik we should release it

Hi @javacode123 thank you for opening an issue. We will take a look at it asap.

@javacode123 Thanks a lot for your report. We've reproduced the problem and identified a problem in our usage of ristretto. We'll have a fix ready tomorrow.

thx, could please add the pr when you fix this problem. i want to learn how to fix it

@javacode123 We were missing a call to ristretto.Cache.Close. See #401 for the whole PR. If you have any questions about it, we're more than happy to help.


Setting a configurable element position

In my project, we have a sidebar that is positioned absolutely in its default state. This is just a small change to make the default position property configurable so it doesn't always revert to relative

Please close this PR in favor of https://github.com/WeCodePixels/theia-sticky-sidebar/pull/41.


WCLL scripts

Here's some the scripts to be able to reproduce the temperature, velocity and mobile concentration fields. Would you like more inline comments or anything within the scripts @RemDelaporteMathurin. Would you like the results files as well?

@jhdark I cannot run hydrogen_transport_sim.py with festim 1.0.
I have the following error:
Succesfully load mesh with 298149 cells
No Jacobian form specified for nonlinear variational problem.
Differentiating residual form F to obtain Jacobian J = F'.
Solving nonlinear variational problem.
  Newton iteration 0: r (abs) = 0.000e+00 (tol = 1.000e-10) r (rel) = -nan (tol = 1.000e-09)
  Newton solver finished in 0 iterations and 0 linear solver iterations.
No Jacobian form specified for nonlinear variational problem.
Differentiating residual form F to obtain Jacobian J = F'.
Solving nonlinear variational problem.
  Newton iteration 0: r (abs) = 1.463e-04 (tol = 1.000e-10) r (rel) = 1.000e+00 (tol = 1.000e-09)
  Newton iteration 1: r (abs) = 5.779e-21 (tol = 1.000e-10) r (rel) = 3.949e-17 (tol = 1.000e-09)
  Newton solver finished in 1 iterations and 1 linear solver iterations.
Traceback (most recent call last):
  File "/home/remidm/FESTIM-review/gallery/breeding_blanket/hydrogen_transport_sim.py", line 217, in <module>
    my_model.initialise()
  File "/home/remidm/anaconda3/envs/festim-review-env/lib/python3.11/site-packages/festim/generic_simulation.py", line 266, in initialise
    if self.T.is_steady_state():
       ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/remidm/anaconda3/envs/festim-review-env/lib/python3.11/site-packages/festim/temperature/temperature.py", line 54, in is_steady_state
    return "t" not in sp.printing.ccode(self.value)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/remidm/anaconda3/envs/festim-review-env/lib/python3.11/site-packages/sympy/printing/codeprinter.py", line 739, in ccode
    return c_code_printers[standard.lower()](settings).doprint(expr, assign_to)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/remidm/anaconda3/envs/festim-review-env/lib/python3.11/site-packages/sympy/printing/codeprinter.py", line 156, in doprint
    expr = self._handle_UnevaluatedExpr(expr)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/remidm/anaconda3/envs/festim-review-env/lib/python3.11/site-packages/sympy/printing/codeprinter.py", line 116, in _handle_UnevaluatedExpr
    return expr.replace(re, lambda arg: arg if isinstance(
           ^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'replace'

I successfully ran heat_transfer_sim_and_slice.py before that

Yeah this was the bug I was talking about on the forum. It can run in a docker container but not a conda one

It can run in a docker container but not a conda one

This doesn't make sense. I've tracked the bug to these lines in festim/temperature/temperature.py
https://github.com/festim-dev/FESTIM/blob/56089a544a7f21e2d9fe4c1b18d3b17ec7396509/festim/temperature/temperature.py#L53-L54
self.value is None in the case of TemperatureFromXDMF so unless we fix this bug it shouldn't work, docker or conda.


when restoring settings from a file, does a check mark not show up for use turning switch (the last setting)

this is not an issue, it's fine. The check mark shows up after a split second.
There appears to be a delay if the settings file includes settings for button control and those settings are hidden when button control is not active.
Removing button control settings from files would be a good idea, in cases where button control won't be used.


Update error message styles: fix #67

close #67

Current coverage is 92.91%

Merging #81 into master will not affect coverage as of b019eb4

@@            master     #81   diff @@
======================================
  Files           28      28
  Stmts          847     847
  Branches         0       0
  Methods          0       0
======================================
  Hit            787     787
  Partial          0       0
  Missed          60      60

Review entire Coverage Diff as of b019eb4

Powered by Codecov. Updated on successful CI builds.

user_profile_update.html 正常來講怎麼樣會出現 non_field_errors 啊？

不太確定，但如果放了就加 style 比較好吧。

沒辦法試出來，我也不方便叫設計師看啊 XD

我另外開個 issue 之後再來寫吧！edit proposal 那邊似乎比較容易試出來～

@uranusjr 我先 merge，non_field_errors 的問題我另外開在 #82。


Loading from best checkpoint

🚀 Feature
Currently Pytorch lightning uses the latest version of the model for testing. In research, we want to first load the best checkpoint and do the testing from there. Also it would be good to restart from the best checkpoint after learning rate plateau as an option.
Motivation
We want the best model for training/testing. Also for NLP it is more natural to go to the best checkpoint and restart with decayed learning rate.
Alternatives
Manual loading and checking of the validation value (which is against lightning principal).

this makes sense. how do you suggest to do it?  ideally you do this in lightning
model = Model.load_from_checkpoint(PATH)
trainer.test(model)
why doesn’t this fit your use case?

There are 2 issues here:

Trainer has a training loop which involves testing (test_end, test_end) which does not behave as above [it uses the latest version of the model during training]. Meaning that I have to make a separate script for testing that load this checkpoint manually.
After loss increased in the development set, we would want to restart from best checkpoint, reduce the learning rate and restart the epoch totally from that checkpoint. Currently this can't be achieved without an external bash script that tracks the model evaluation performace and (1) kill the training if loss increased, (2) restart with decayed learning rate. Which is too much work.

At the beginning I think it is as easy as loading the checkpoint internally. But I realized that in multi GPUs setting, these parameters need to be copied to each pytorch module inside every GPU.
In summary:

Let's implement module.restart_from_checkpoint_(.) for pytorch lightning module.

Not in the plan?

This will need to have the specific checkpoint path right?
Is there a way to give it the dir path, and it will load the best ckpt based on CheckpointModel obejct logic?

this makes sense. how do you suggest to do it? ideally you do this in lightning
model = Model.load_from_checkpoint(PATH)
trainer.test(model)
why doesn’t this fit your use case?

This will need to have the specific checkpoint path right?
Is there a way to give it the dir path, and it will load the best ckpt based on CheckpointModel obejct logic?

yes the path is in the Checkoint

already solved... 🐰

any update on this? Do we have the option to restore best model weights currently?

Please consider adding the restore_best_weights functionality similar to Keras. Currently, this feature is not available.