Postgres recovery refactor

Currently during recovery the script does overwrite the postgres database on the disk with rsync:
https://github.com/raspiblitz/raspiblitz/blob/502782f5ed4955efe63f5f3c23125808ac443d93/home.admin/config.scripts/bonus.postgresql.sh#L58-L65
We need to make sure that old data is preserved and stick to the existing postgres version.
In the future would need to deal with postgres version migration as well using pg_upgrade.
Related discussion: #4496

After installing postgres 13 the message appears:
Success. You can now start the database server using:

    pg_ctlcluster 13 main start

Processing triggers for postgresql-common (248) ...
Obsolete major version 13

The PostgreSQL version 13 is obsolete, but the server or client packages are
still installed. Please install the latest packages (postgresql-15 and
postgresql-client-15) and upgrade the existing  clusters with
pg_upgradecluster (see manpage).

Please be aware that the installation of postgresql-15 will automatically
create a default cluster 15/main. If you want to upgrade the 13/main
cluster, you need to remove the already existing 15 cluster (pg_dropcluster
--stop 15 main, see manpage for details).

The old server and client packages are no longer supported. After the
existing clusters are upgraded, the postgresql-13 and postgresql-client-13
packages should be removed.

sudggests that rather should go ahead and use postgres 15

Successful restore from pg 15 database on disk:
Creating config file /etc/postgresql-common/createcluster.conf with new version
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
  en_gb
  en_us
Removing obsolete dictionary files:
'/etc/apt/trusted.gpg.d/apt.postgresql.org.gpg' -> '/usr/share/postgresql-common/pgdg/apt.postgresql.org.gpg'
Created symlink /etc/systemd/system/multi-user.target.wants/postgresql.service → /lib/systemd/system/postgresql.service.
Setting up postgresql-15 (15.6-1.pgdg120+2) ...
Creating new PostgreSQL cluster 15/main ...
/usr/lib/postgresql/15/bin/initdb -D /var/lib/postgresql/15/main --auth-local peer --auth-host scram-sha-256 --no-instructions
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_GB.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/15/main ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Europe/London
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for libc-bin (2.36-9+rpt2+deb12u4) ...
Assertion failed on job for<EMAIL_ADDRESS>Error: cluster configuration already exists
Synchronizing state of postgresql.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable postgresql
psql (PostgreSQL) 15.6 (Debian 15.6-1.pgdg120+2)
# wait for the postgresql server to start
Setting default password for postgres user
could not change directory to "/root": Permission denied
ALTER ROLE
OK PostgreSQL installed

with the latest image postgres was recovered and running from prev pg 15 data

REstoring from pg 13 on Rpi4:
# There is old data for pg 13, start and upgrade cluster ...

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
  pi-language-support
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  postgresql-client-13
Suggested packages:
  postgresql-doc-13
The following NEW packages will be installed:                                                                                [645/4320]
  postgresql-13 postgresql-client-13
0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded.
Need to get 16.5 MB of archives.
After this operation, 59.5 MB of additional disk space will be used.
Get:1 http://apt.postgresql.org/pub/repos/apt bookworm-pgdg/main arm64 postgresql-client-13 arm64 13.14-1.pgdg120+2 [1,474 kB]
Get:2 http://apt.postgresql.org/pub/repos/apt bookworm-pgdg/main arm64 postgresql-13 arm64 13.14-1.pgdg120+2 [15.0 MB]
Preconfiguring packages ...
Fetched 16.5 MB in 1s (11.2 MB/s)
Selecting previously unselected package postgresql-client-13.
(Reading database ... 130784 files and directories currently installed.)
Preparing to unpack .../postgresql-client-13_13.14-1.pgdg120+2_arm64.deb ...
Unpacking postgresql-client-13 (13.14-1.pgdg120+2) ...
Selecting previously unselected package postgresql-13.
Preparing to unpack .../postgresql-13_13.14-1.pgdg120+2_arm64.deb ...
Unpacking postgresql-13 (13.14-1.pgdg120+2) ...
Setting up postgresql-client-13 (13.14-1.pgdg120+2) ...
Setting up postgresql-13 (13.14-1.pgdg120+2) ...
Creating new PostgreSQL cluster 13/main ...
/usr/lib/postgresql/13/bin/initdb -D /var/lib/postgresql/13/main --auth-local peer --auth-host md5
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_GB.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/13/main ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Europe/London
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Success. You can now start the database server using:

    pg_ctlcluster 13 main start

Processing triggers for postgresql-common (257.pgdg120+1) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
  en_gb
  en_us
Removing obsolete dictionary files:
# Create pg 13 config
Error: cluster configuration already exists
Setting default password for postgres user
could not change directory to "/root": Permission denied
ALTER ROLE
Error: cluster configuration already exists
# backup /mnt/hdd/app-data/postgresql/15
mv: cannot stat '/mnt/hdd/app-data/postgresql/15': No such file or directory
# Drop empty pg 15 cluster
Warning: corrupted cluster: data directory does not exist
Stopping old cluster...
Restarting old cluster with restricted connections...
Creating new PostgreSQL cluster 15/main ...
/usr/lib/postgresql/15/bin/initdb -D /var/lib/postgresql/15/main --auth-local peer --auth-host scram-sha-256 --no-instructions --encoding UTF8 --lc-collate en_GB.UTF-8 --lc-ctype e
n_GB.UTF-8
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_GB.UTF-8".
The default text search configuration will be set to "english".                                                                   [593/4349]

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/15/main ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Europe/London
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Copying old configuration files...
Copying old start.conf...
Copying old pg_ctl.conf...
Starting new cluster...
Running init phase upgrade hook scripts ...

Roles, databases, schemas, ACLs...
 set_config
------------

(1 row)

 set_config
------------

(1 row)

 set_config
------------

(1 row)

 set_config
------------

(1 row)

 set_config
------------

(1 row)

 set_config
------------

(1 row)

 set_config
------------

(1 row)
 set_config                                                                                [536/4349]
------------

(1 row)

Fixing hardcoded library paths for stored procedures...
Upgrading database template1...
Fixing hardcoded library paths for stored procedures...
Upgrading database btcpaymainnet...
Fixing hardcoded library paths for stored procedures...
Upgrading database nbxplorermainnet...
Fixing hardcoded library paths for stored procedures...
Upgrading database postgres...
Fixing hardcoded library paths for stored procedures...
Upgrading database lnbits_db...
Stopping target cluster...
Stopping old cluster...
Disabling automatic startup of old cluster...
Starting upgraded cluster on port 5433...
Running finish phase upgrade hook scripts ...
vacuumdb: processing database "btcpaymainnet": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "lnbits_db": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "nbxplorermainnet": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "postgres": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "template1": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "btcpaymainnet": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "lnbits_db": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "nbxplorermainnet": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "postgres": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "template1": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "btcpaymainnet": Generating default (full) optimizer statistics
vacuumdb: processing database "lnbits_db": Generating default (full) optimizer statistics
vacuumdb: processing database "nbxplorermainnet": Generating default (full) optimizer statistics
vacuumdb: processing database "postgres": Generating default (full) optimizer statistics
vacuumdb: processing database "template1": Generating default (full) optimizer statistics

Success. Please check that the upgraded cluster works. If it does,
you can remove the old cluster with
    pg_dropcluster 13 main

Ver Cluster Port Status Owner    Data directory              Log file
13  main    5432 down   postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log
Ver Cluster Port Status Owner    Data directory              Log file
15  main    5433 online postgres /var/lib/postgresql/15/main /var/log/postgresql/postgresql-15-main.log
# backup /mnt/hdd/app-data/postgresql/13
Warning: corrupted cluster: data directory does not exist

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  pi-language-support postgresql-client-13
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  postgresql-13
0 upgraded, 0 newly installed, 1 to remove and 4 not upgraded.                                                                    [479/4349]
After this operation, 52.3 MB disk space will be freed.
(Reading database ... 132610 files and directories currently installed.)
Removing postgresql-13 (13.14-1.pgdg120+2) ...
Processing triggers for postgresql-common (257.pgdg120+1) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
  en_gb
  en_us
Removing obsolete dictionary files:
port = 5433                             # (change requires restart)
# Switch port back to 5432
# Restart posgresql.service
Synchronizing state of postgresql.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable postgresql
Created symlink<EMAIL_ADDRESS>→<EMAIL_ADDRESS>
psql (PostgreSQL) 15.6 (Debian 15.6-1.pgdg120+2)
# wait for the postgresql server to start
Setting default password for postgres user
could not change directory to "/root": Permission denied
ALTER ROLE
OK PostgreSQL installed

Successful recovery from pg 15 lnbits on the same run:

The following packages were automatically installed and are no longer required:
pi-language-support postgresql-client-13
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
There is old data for 15, restoring ...
Assertion failed on job for<EMAIL_ADDRESS>Error: cluster configuration already exists
Synchronizing state of postgresql.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable postgresql
psql (PostgreSQL) 15.6 (Debian 15.6-1.pgdg120+2)
wait for the postgresql server to start
Setting default password for postgres user
could not change directory to "/root": Permission denied
ALTER ROLE
OK PostgreSQL installed
Generate the database lnbits_db
GRANT
could not change directory to "/root": Permission denied
Setup PostgreSQL successful, new database found:  lnbits_db
Running: 'bonus.lnbits.sh switch cl'


Regularize metric aspect API.

A metric value now holds a pointer to a MetricDefinition instead
of merely having its name. This prevents individual adapters having
to maintain a map.

Remove the Kind field from the metric value type, since it can be
obtained from the MetricDefinition instance.

Pass a map of MetricDescription into the NewMetricsAspect method.
This enforces the uniqueness of names and avoids some code in some
adapters.

Pass down the DisplayName and Description values from the
MetricDescriptor such that adapters can use those values when
configuring backends if needed.

This change is

Codecov Report

Merging #275 into master will decrease coverage by -0.25%.
The diff coverage is 97.72%.

@@            Coverage Diff             @@
##           master     #275      +/-   ##
==========================================
- Coverage   83.68%   83.43%   -0.25%
==========================================
  Files          49       50       +1
  Lines        2831     2826       -5
==========================================
- Hits         2369     2358      -11
- Misses        434      439       +5
- Partials       28       29       +1

Impacted Files
Coverage Δ

pkg/adapter/metrics.go
100% <ø> (ø)
:white_check_mark:

pkg/adapter/labels.go
100% <100%> (ø)

pkg/aspect/metricsManager.go
95.68% <100%> (ø)
:white_check_mark:

adapter/prometheus/prometheus.go
94.64% <100%> (-1.79%)
:x:

adapter/statsd/statsd.go
94.44% <83.33%> (-5.56%)
:x:

pkg/adapterManager/parallelManager.go
95.23% <ø> (ø)
:white_check_mark:

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 9ea6e90...235653e. Read the comment docs.


Error when jumping into datamapper step to edit

Not sure whether this belongs to here or to syndesis-ui:

This happens when I have a simple integration with only a datamapping step and I come back from the details page via "Edit" and klicking immediately on the datamapper step.
When first clicking on one of the connection and then on the datamapper everuthinng's fine.

@akieling if you're still looking for issues this would be a good one, might be a problem with the data mapper host component pulling the details out of the integration, not sure...

@rhuss I think there is an issue with the target connection in the 'test' integration in staging. When you click on it, you get an error message on the page saying "Please contact the administrator and file a bug report".
A post is sent to https://syndesis-staging.b6ff.rh-idev.openshiftapps.com/api/v1/connections/2/actions/io.syndesis:salesforce-upsert-sobject-connector:latest with the following payload:
{}


fix Turkish hyphenation rules

The white paper published in TUG on Turkish hyphenation specifically
mentions the special -ecek case and similar suffixes in the context of
dealing with trailing two letter suffixes. The code, however, only
matches the two letter variants with a special case for -ecek, but
overlooks -acak which is a grammatically identical variant with the same
issues.
http://www.tug.org/TUGboat/Articles/tb09-1/tb20mackay.pdf
I also submitted this tweak to the author of the upstream LaTeX package
on CPAN where these rules originated. I don't know how slow moving that
fix will be or if there will eventually be a re-import or not, but until
then I don't see a reason not to patch it here too.

Thanks! I'm not planning on doing a reimport from LaTeX - one of the goals for the next release is improving the way that language-specific typesetting information (not just hyphenation, but line breaking and other typographic conventions) gets encoded, which is the reason for the Japanese madness right now. I will probably stick with the hyphenation patterns idea from TeX, but there will be lots of other stuff added as well that means the language support files will diverge from TeX.

I follow you. It would be nice to be able to 'track' language related packages out of TeX at least to some extent as lots of little issues like this surface and get fixed across a broad spectrum of languages. In the years I've been using it I've seen even English language edge cases get fixed. As SILE is somewhat behind the adoption curve it would be nice to take advantage of the number of eyeballs on documents that the TeX world offers. But I wouldn't put that very high next to the need to being able to implement the backend in a more modern way—perhaps that means we just need to keep a weather eye out on diffs between TeX language releases and periodically manually port any relevant items.


[Blog] Add Daft + Delta Lake blog post.

This PR adds a blog post for distributed + parallel reading of large Delta Lake tables with Daft.

cc @dennyglee

@dennyglee Indeed, I'll work on fixing the spacing for some of the images!

@dennyglee I've fixed the spacing in the images and updated some of the copy. It appears that the docs preview build doesn't automatically trigger on new commits, do we need to do anything to trigger another build?

This is looking great @clarkzinzow.  super minor nit, so feel free to disregard - perhaps have the splash screen of your blog on the front screen be this image?    It's the right size (and matches the other splash screens) and its really compelling, eh?!

@dennyglee Updated with a new thumbnail and a top-of-page landing image that we're thinking about adding, could you kick off another build?

Kicked off and approved!  Please do a quick sanity check and I’ll merge.
Thanks !
On Mon, Apr 8, 2024 at 12:29 Clark Zinzow @.***> wrote:

@dennyglee https://github.com/dennyglee Updated with a new thumbnail
and a top-of-page landing image that we're thinking about adding, could you
kick off another build?
—
Reply to this email directly, view it on GitHub
https://github.com/delta-io/website/pull/390#issuecomment-2043502578,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALBHLJ5ZMQV2JFBX3OWZU3Y4LVZZAVCNFSM6AAAAABFYIPD22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTGUYDENJXHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@dennyglee M=Just made some final tweaks to the benchmarking setup info formatting, good to merge when you are!

Love it @clarkzinzow - merging now!


SQLActionException[MaxBytesLengthExceededException: bytes can be at most 32766 in length; got 75875]

CrateDB version: 3.2.6
Environment description:

Problem description: This occurs when I tried inserting data which exceeds more than 32766 bytes.
SQLActionException[MaxBytesLengthExceededException: bytes can be at most 32766 in length; got 75875]

Steps to reproduce:Try inserting a huge JSON object into a table.

See https://crate.io/docs/crate/reference/en/latest/general/ddl/data-types.html#data-type-text and https://crate.io/docs/crate/reference/en/latest/general/ddl/storage.html#ddl-storage-columnstore on how to work around the 32766 bytes limitation.


Remove dependency on regex crate

Fixes #142.
I haven't added tests on the Matcher because the different matching is tested on the different parse functions. Please let me know if I should include tests for the Matcher.
I don't have a macOS, so I'm not sure what the right way to test that is. What I did was temporarily copy relevant tests and the new function to somewhere else where I could compile and run them. It compiles, and they work, but please let me know what the proper way to test this is.
I should note, the Matcher does not work exactly like the old regex did. It's more of a \S+ rather than [\w.]+, but since all tests pass, it should be fine. Furthermore, there is no need to trim, since neither the regex or now the Matcher would ever include whitespace in the captured group!

Fair point clippy on unwrap_or(string.len()) should be unwrap_or_else(|| string.len()), although I would say the call was pretty cheap :P - force pushed a fix.

And noticed warnings on the Windows checks, so now we don't compile Matcher there (similar to how we didn't include regex).

Oh, I see, CI is the one that tests macOS. I just realized, as a nice bonus from this PR, we also don't need to depend on lazy_static ^^
But wrt. the following warning on macOS:

variant is never constructed: PrefixedWord

It's funny it only complains about PrefixedWord, when AllTrimmed is also not used in macOS. Is it worth having a different Matcher for macOS that only contains PrefixedVersion? Should we ignore the warnings? Should we conditionally compile just a few of the enum variants and have different find implementations?

Yes, I think separating the matcher into common functions rather than a different regex per use is good (it could even be implemented with regex itself, but it would defeat the purpose!).
I assume you are okay with me leaving the macOS warnings and lack of tests, so nothing more to add. It's been a pleasure.

Warnings can be fixed with additional cfg(target_os = "macos"), but I'm not sure if it is worth it. I don't like adding #[allow(dead_code)] either. I'm going to think a little more about it, but it is OK for now.


⚠ Samsung has degraded performance

In 5ae8701, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2347 ms

Resolved: Samsung performance has improved in 237dae9.


Move phpunit to require-dev

Thanks for making this library.
This pull request move the phpunit dependency to require-dev. This enable to use the library as dependency of another project.

Was going to make a pull request for this but, looks like someone beat me to it. Any chance to push this through?

@avvertix @worthwhileindustries Just resolved PR #3 which includes this; thanks for the patience and sorry for the long delay


[Enhancement] Image Gallery Overlay

Hi, I wrote an self contained Image Gallery Overlay. Which integrates will with this hugo module.
I didn't know where to put it and I thought this could be a nice addition to this module
https://gist.github.com/Darkproduct/36e354bec1eedf8c8dcfb0c73cf26a51

Sounds like a great idea, I will try to look at it today
On Wed, 12 Apr 2023, 2:06 am Darkproduct, @.***> wrote:

Hi, I wrote an self contained Image Gallery Overlay. Which integrates will
with this hugo module.
I didn't know where to put it and I thought this could be a nice addition
to this module
https://gist.github.com/Darkproduct/36e354bec1eedf8c8dcfb0c73cf26a51
—
Reply to this email directly, view it on GitHub
https://github.com/future-wd/hugo-responsive-images/issues/56, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTWGA4NUZ4HAVSGILJ2TVTXAVQNZANCNFSM6AAAAAAW2KPQRY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I had a quick look, I have come up with 2 ideas.

Create a hugo module for your gallery

you can then import the css and js easily
import my module as a sub-module (see example here - I have common code between my standard image module, and background image module https://github.com/future-wd/hugo-responsive-images/blob/master/config/_default/module.yaml)

Create a plugins folder for my image module

The same import process will happen
I'm worried your module might be hard to find via this option

For option 1 I am happy to put a link to your project on my readme.
Either way I think you should use a class other than 'img-fluid' as it clashes with my module, and also bootstrap.
If you need help with modules let me know. As long as you don't go into version 2+ its fairly straight forward.
Sean

I have set up a temporary repository
github.com/future-wd/temp-image-gallery
Clone it to your computer.
Run the test site (in the .test-site folder)
Set up the image gallery so it works. You will need to run 'hugo mod get -u' to pull the module in.
Add the requred imports as per the instructions ( I havent tested them out)
Create your own repo, and change the go.mod urls to match.
Let me know how you go.

Not sure what I'm doing wrong, but I can't get the test site to work:
❯ hugo server --navigateToChanged -D
Start building sites …
hugo v0.111.3-5d4eb5154e1fed125ca8e9b5a0315c4180dab192+extended linux/amd64 BuildDate=2023-03-12T11:40:50Z VendorInfo=gohugoio
WARN 2023/04/13 10:42:21 found no layout file for "HTML" for kind "home": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2023/04/13 10:42:21 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2023/04/13 10:42:21 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

                   | EN
-------------------+-----
  Pages            |  3
  Paginator pages  |  0
  Non-page files   |  0
  Static files     |  0
  Processed images |  0
  Aliases          |  0
  Sitemaps         |  1
  Cleaned          |  0

Built in 4 ms
Watching for changes in ~/temp-image-gallery/assets/{simple-image-gallery}
Watching for config changes in ~/temp-image-gallery/config.yaml, ~/temp-image-gallery/go.mod
Environment: "development"
Serving pages from memory
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at //localhost:1313/ (bind address <IP_ADDRESS>)
Press Ctrl+C to stop

I first updated hugo, but that didn't help. One difference I see to my site is at the end:
Web Server is available at //localhost:1313/ (bind address <IP_ADDRESS>) my site has http in front of the localhost.

Ah nvm. I should probably try to start the test site and not the module. So now in .test-site:
❯ hugo server --navigateToChanged -D
Error: module "github.com/future-wd/hugo-responsive-images" not found; either add it as a Hugo Module or store it in "~/temp-image-gallery/.test-site/themes".: module does not exist

But I did hugo mod get -u in the module. When I try the same in .test-site:
❯ hugo mod get -u
WARN 2023/04/13 11:00:02 module "github.com/future-wd/hugo-responsive-images" not found; either add it as a Hugo Module or store it in "~/temp-image-gallery/.test-site/themes".: module does not exist

I just realised I forgot to initalise the test site for use with hugo modules. I also had to disable the module replacement for local development.
Should work now.
If you want to do develop locally, the easiest way is to un comment the replacements line in config.yaml in the test site, BUT also add my responsive image module as a dependency, and remove it from your module. Replacements doesn't work with sub modules.


experiencing timeouts?

After i input my username/password, it appears the API call is made as I am left hanging for a period of 1-2 minutes. After which I will receive this error:
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.robinhood.com', port=443): Max retries exceeded with url: /api-token-auth/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x0A3456D0>: Failed to establish a new connection: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'))
Has anyone experienced this and found a fix? I am wondering if it has something to do with my PC, which is behind a corporate proxy.

Should be fixed with #36. Feel free to reopen if that's not the case.


Transfer maintainership

Hi, thanks for your work on this library!
This repository is obviously no longer maintained. Given that this project is already on MELPA, the nicest solution would be if you would transfer maintainership to someone else. I'd be willing to do it if no one else wants.

Yeah you are right that I am currently not working with C++ and thus not too involved with clang-tidy anymore.
So I would just give you maintainer rights on this repo? Gladly will do and thanks for the PR!

Alright with me. 🙂


Kip to Release NGSAFR Code

Two versions of the NGSAFR source code should be released to the public as approved in the IBM OS approval processes.  They include:  https://github.ibm.com/kip-twitchell/ngsafr/blob/master/src/main/scala/com/ibm/ngsafr/post/Posting.scala
which does not have jzos embedded in it, but rather runs on a local machine.
And then the version on KMT's machine which has the jzos code embedded in it.

Under Spark-poc:

Make new director:  poc-iterations
add projects under this, including:
ngsafr-linux (https://github.ibm.com/kip-twitchell/ngsafr/blob/master/src/main/scala/com/ibm/ngsafr/post/Posting.scala)
ngsafr-jzos (kip's machine)
spark-jzos (Neil's machine)
jni2asm (Neil's machine)
load code from various places.

All of the above is done except for the ngsafr-linux version.  Here are the steps to include it.
1- replicating that Repo from IBM’s github to your laptop
2-copying the code from that directory to the GenevaERS Spark repo in a new directory (perhaps NonzjosCKBScala)
3-adding a readme to that directory that says the relationship to the jzos versin
4-Pushing that branch to the GenevaERS Repo
5- and making a pul request for it to be merged into the Repo.
The repo for that code is on the internal IBM Github repo at:  (https://github.ibm.com/kip-twitchell/ngsafr/blob/master/src/main/scala/com/ibm/ngsafr/post/Posting.scala)


Can't release to a webapp that has letters å, ä, ö

set up a webapp name 'göm-mig-från-omvärlden'.
All works fine and we can navigate to it (göm-mig-från-omvärlden.azurewebsites.net).
But when we try to make a release from VSTS it state that the resource 'göm-mig-från-omvärlden' does not exist.
It seems our Azure webapp task does not handle the special characters.

fixed in M134. the fix will be available in next deployment.


disable pagination and prompting if stdout !isatty

Use case is for example when using drive as output to another process
e.g
drive list openSrc | wc
This PR is meant to address #119

cc @kcwu

LGTM (I just leave comment in wrong place, i guess)

Thanks @kcwu, merged into master.


IPhone XR, batchPushReceived is not triggered when application was totally closed.

I saw the error "[BatchCordovaCallback] Not sending callback to Batch, _setupCallback doesn't seem to have been called. Something bad happened." on device console.
After debugging the code, I deleted the comment from this line
[self.commandDelegate evalJs:@"batch._setupCallback()"];
from BatchCordovaPlugin.m, it works well.
I don't want to create another bug, so my question is why this line was commented at initially?

Hello,
Thanks for your report.
It was commented because it was only there for debubgging purposes.
The thing is that BatchPushReceivedNotification should not fire before Batch has been setup, and the callback should be there. The callback is right: something wrong is happening.
Maybe a change in the native component has triggered this, but we will have to investigate further.
Glad you found a workaround!

Thanks for your quick response. Maybe more detail will help for your debugging in future.
In the documentation, it says that batchPushReceived will be triggered when batch will be ready. It works as expected on Iphone 7; but not Iphone XR, event is not triggered.

Batch will NOT emit this event until it is started. As soon as it is started, it will send you the payload of the push that started the app, if there is one.

Are both phones on the same iOS version?

Yes, same version, latest for the moment, 12.3.1

Hi,
This should be fixed in the 3.0.0-beta.1 version of the plugin


Shadowing not working as I'd expect

I'd expect the definition in the local module to hide the one from the standard library.
extension Int {

  fun infix+= (_ other: Int) {
    &self = self + other
  }

}

public fun main() {
  var x = 3
  x += 1 // error: ambiguous use of 'infix+='
}

I don't think shadowing should work here. I expect that the compiler will eventually complain about an invalid redefinition of the operator.
Extensions do not introduce another scope; they are "siblings" of the original type declaration but only visible in their introduction scopes (and their siblings). I am not sure treating extensions in other modules is worth an exception to that rule.

I think the same modularity argument applies as for shadowing of conformances.  If I extend M.X with something and then use that thing, it shouldn't break my code when the author of M adds that thing themselves.

I thought it would be your answer but I think code breakage here is acceptable because extensions can add overloads, and these overloads will have your code break anyway.

Why I don't like overloads.  In a sense that's what I'm saying: a method local extension should (locally) shadow methods of the same name from elsewhere so we don't end up with an unintentional overload set.  In fact this is why I always wanted users to be explicit about which thing they're actually overloading when they create an intentional overload.  I don't think when we gave up on the policy of "no overloads" that we ever designed the intentionality feature.

"Obviously" overloading should apply to this case…
fun f(_ x: Bool) {}
public fun main() {
  fun f(_ x: Int) {}
  f(true) // OK
}

That case is exactly the sort of thing I might expect to create a shadow unless something explicit makes it an overload.

That case is exactly the sort of thing I might expect to create a shadow unless something explicit makes it an overload.

Interesting!
Could you draw a rough picture of how you would like overloading to work ideally?

@dabrahams Your original example has been "fixed".
The current definition ranking algorithm uses a definition of "depth" defined as follows:
https://github.com/hylo-lang/hylo/blob/805cacf55915a86fd701a37e68af1c511c711850/Sources/FrontEnd/TypeChecking/TypeChecker.swift#L5055-L5065
I'd like to close this issue for now. Feel free to reopen if necessary.


Reports optimised

Hello, Peter
Reports were slightly optimised and now we may seed separately Report - All and Report - Current and same for raw data as well.

Thank you!

Thank you!


Added Slanty Wavy Button

Fixes Issue
Closes #1351

Changes proposed
I added a slanty wavy Button

Screenshots

https://github.com/Spyware007/Animating-Buttons/assets/119161467/cd03a6ca-aa1c-4dbd-bd35-05ac1f424b81
Checklist

[x] You've linked this PR to the correct issue.
[x] You have checked that the code is working correctly.
[x] You ⭐ the repository!

Note to reviewers
@Souravvmishra  I am writing to kindly request your attention and consideration in reviewing and accepting my pull request. I would greatly appreciate it if you could allocate some time to review the pull request and provide your feedback. If there are any areas that require further attention or modifications, please let me know, and I will be more than willing to address them promptly.

Looks Great. But it's overflowing. Align it at the centre

Looks Great. But it's overflowing. Align it at the centre

okay

@Souravvmishra  I Have done some changes can you please check it now

Great But it seems you removed one of the two ways. Anyways I merged it.

Great But it seems you removed one of the two ways. Anyways I merged it.
@Souravvmishra  thankyou for merging my pull request but can you please add some level to my pull reuest so that i can get some points from my contribution and can you also add gssoc tag to it please.
Thankyou

Thank You @Souravvmishra  Sir for considering my request


Refactor your functions in specified files

You should separate your logic in specified files, this will allow you to better read, update and understand your code.
Plus, you may want to test your code in order to avoid a lot of errors
for example a folder lib with a folder commands with all commands so in your main file it will be more readable to just call the associated functions and don't care about what it does
https://github.com/nelak2/nwscript-sinfar-language-server/blob/c5afa5430fef7296ccdbac865df96269efc1e7b9/client/src/extension.ts#L86-L95

Yes. This makes a lot of sense.


[QUESTION] ambiguity of setup parameters

Description

Not sure if i need the cookiecutter param 'data' if i do not select 'imagenet' for the type since the description says that it is the location to store imagenet
type 'image_name' feels ambiguous. users don't know ahead of time that the are using a docker image as a control plane. maybe specify in the cookiecutter prompt that it is a docker image? or rename to docker_image_name
cookiecutter prompts for datastore name as 'account name', which is ambiguous (account of what?) and not reflected in the readme
same issue for prompting 'account key', naming is ambiguous. Also, shouldn't this be generated? instead of prompting a user for it. (also not reflected in the readme)
perhaps rename 'container_name' -> 'storage_container_name' (since people may mix up the term container)

Other Comments

Nice catches, will address


Upgrade Bootstrap to newer version (e.g. 4.5.3) so spinner works

Is your feature request related to a problem? Please describe.
The spinner used in the Location Rebuild does not work with the old version of Bootstrap currently installed.
Describe the solution you'd like
Upgrade the Bootstrap code in the project to a newer version.
Describe alternatives you've considered
Writing a spinner from scratch takes a lot more effort.
Additional context
We use the Bootstrap code locally to the server so we are not endlessly beating on the internet for every page displayed.

Evidently using Bootstrap 4.x.x causes problems with some of the pytest modules.  This needs to be resolved so we can resume using the latest bootstrap code.  Currently, the system is using version 3.3.7.


Remove terminal: true, replace with priority: 1

This fixes angular 1.5 compability issues. Original idea by @akotlar, just making the pull request. Seems a better solution to #158 than my initial approach.

This pull request already exists #157


fix(UI): make 'Tests' heading translatable

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

This heading was not translated:

Affected page:
https://www.freecodecamp.org/japanese/learn/javascript-algorithms-and-data-structures/functional-programming/combine-two-arrays-using-the-concat-method
or any other (not project based) challenges

I say separate them when issue arise. The translation is done by contributors in some languages, so consistency will be hard to achieve in them, making them the same should make it easier to stay consistent in them for now.


Feature: support goerli test network

Goerli will be the only surviving test network after the merge,  with kovan and rinkeby slated to see EOL by EOY.
What would it take to get a deployment on Goerli?
Thanks!

This is a good point thanks! Moved this issue in the next sprint board.
We need to deploy the Interep contracts on Goerli and deploy another web app: goerli.interep.link. We could keep both or replace Kovan with Georli in the near future.

This is a good point thanks! Moved this issue in the next sprint board.
We need to deploy the Interep contracts on Goerli and deploy another web app: goerli.interep.link. We could keep both or replace Kovan with Georli in the near future.

Thank you, this is a blocker for us, in the meantime let me know how i can help

@sambacha
Interep Goerli is now active on https://goerli.interep.link. New contract address here: https://github.com/interep-project/contracts.


Remove small duplicities

Description:
Remove small pieces of duplicate code.
Checklist:

[x] PR Location (usually master for hotfixes, dev for general development)

Looks good!

@lechat Thanks!
@enclarify Split into two commits and they now have a better commit message. Appreciate your comments, I'll try doing better commits in the future. That should also help when there is a need to revert something.
Okay to merge now?

Looks good

Thanks, merging.


Errors in building solution in Visual Studio

When building solution in release mode I get the following errors:

Can you try to disable detours and fork safety?
OPTION_BUILD_DETOURS=OFF
OPTION_FORK_SAFE=OFF

Anyway, I think a windows script for configuring this properly and executing the msbuild will be something more interesting, so you can avoid configuring this by hand. All the problems you had were due to configuration.

Disabling BUILD_DETOURS and FORK_SAFE worked.


 We should make them take strings instead since copying Id everyone is neither necessary nor useful since they contain extra information like spans.

Make them take AsRef<Str> or ToString instead. This will make it less verbose to use the interfaces


[otbn] Add modular multiplication with Barrett reduction

This is a generic implementation without requirements on the form
of the modulus, only the range of the modulus is limited. For
special formed moduli (e.g. generilzed Mersenne primes in p384)
we might want to provide an optimized version.
The implementation mainly follows the description of the algorithm
in the "Handbook of Applied Cryptography" (Algorithm 14.42) and
re-uses its terminology. Some changes have been made to improve
register and multiplier efficiency.
This is related to lowRISC#3192.
Signed-off-by: Felix Miller<EMAIL_ADDRESS>

Thanks @rswarbrick for having a look at this. Did all the changes as requested, otbn-as is happy now

On thing to note: The code consumes quite some registers (naturally more than the 256 bit variant). This can be probably tweaked to spare maybe two regs by changing the order of access. Created #3267 for this. This should, however have no effect on performance evaluation.

Hi! Sorry for being a bit slow: I'll try to have a proper look at this before the end of the day.

This is really neat! I'm not claiming I followed the maths properly, but it looks sensible to me. It also makes me wish we had a register allocator (I wrote one in another life at Broadcom, which would be lovely to drop in here!).
I think the commit currently at the top of the PR branch (8d78d9b) still has syntax that chokes the assembler. Could you fix that? If you rebase onto master, make sure you also cherry-pick #3270 if it isn't yet merged: I slightly broke the assembler and this fixes it!

This is a very cool implementation, and I feel a bit bad for being That Guy, but we do have an assembly style guide: https://docs.opentitan.org/doc/rm/asm_coding_style/. I think it's probably worth following it in OTBN given that it's RISC-V-enough that that probably covers it. Uniformity across the project is a very useful property.

@gkelly No worries, absolutely happy to receive some guidance here. Actually I tried to follow the style guide you linked, can you elaborate a bit?

@rswarbrick Could you have another quick look?
Changes:

Fixed all the flag parameters to uppercase now (I think some slipped on the first pass)
Replaced the multiplication kernel by one based on Greg's fully unrolled version
Added the section directive
Added ecall intstruction
Fixed some typos

I'm not sure what Garret's thoughts on style are, but the main thing I would take a look at is consistency with existing assembly files (https://github.com/lowRISC/opentitan/blob/master/sw/device/exts/common/flash_crt.S is a good example).
The following are de-facto style but we probably aught to include them in the style guide:

Lower-case mnemonics and register names (so as not to clash with macros; same reason for kConst in C/C++).
// for non-Doxygen comments, including the license header.

In addition, the style guide requires the use of pseudo instructions when possible, Given that the OBTN assembler is implemented on top of clang, I think this guidance applies here (e.g., prefer ret over jalr zero, ra, 0. This also applies to sequences like addi rd, zero, 8; prefer li 8, unless it is known that li produces more code than is appropriate (lui + addi instead of just an addi).
There is also a provision for using ABI names for RISC-V GPAs (ra over x1) that I feel applies here (though I can't remember if x0 is hard-wired to zero in OBTN or not, so maybe it's ok to just call it x0?)
Of course, since OBTN isn't exactly RISC-V, I feel it is completely valid to include provisions in the style guide specifically for it.

@mcy: In reply to your second bullet, otbn-as is not being run via gcc/clang (which strips comments), so it actually only supports /* */ style comments. (Meson runs .S files through the C compiler).
To clarify, otbn-as is a small wrapper on top of binutils' as. Lots of pseudo-instructions are not implemented in the assembler yet, and its not clear there will be support for all the same pseudo-instructions anyway, as I understand it.

Sam's right. At the moment, the only pseudo-instructions we support in otbn-as are li, ret and nop. Glancing through the code, I can spot two candidates for li (lines 245, 261) and two for ret (lines 74, 222), but I'm not sure how much this matters.

Ok, that makes sense! I'm ok submitting this PR as-is, but we should probably update the style guide with a "OTBN exceptions/weirdnesses" section, since I didn't know any of those details, which is why I didn't style-review this PR in the first place.

Pseudo instructions: So far I didn't use them, because it is still a bit of a moving target and we will have to update the code anyways at some point. So I thought let's have one change later updating everything to use the PIs. Anyways, changed the current PR to use ret and li now.

Mnemonic letter case: Also changed this but am having 2nd thoughts now and didn't update the PR yet. Wanted to get your view first. See here for a lower case variant. I am finding the UC variant much more readable. You can spot the actual instructions much better between the comments and most crypto code will look like this and contain formulas in the comments that look a bit like instructions on the first glance. I am absolutely seeing @mcy's point w.r.t. macros though. Another option would be to go for doxygen style comments everywhere (when it's multi line) to have each comment line start with a *.

Style guide: Absolutely agree that we should come up with one for OTBN at some point. From my point of view it should be a self-contained one though with as much consistency as possible with the RISC-V one. Then have a link at the top of the RISC-V one: "If you are actually writing OTBN code go there". We are not there yet there though and just having the first discussions on style.

@felixmiller: Good idea about the cross links for a style guide.
Re upper and lower case mnemonics, I probably prefer the lower case because it looks less "shouty", but I don't have strong feelings. I think both options are pretty painful to read without syntax highlighting: I'm not convinced that uppercase mnemonics help much.

Re: upper case, I mostly think we should stick to it for consistency. I myself have trouble reading instructions that are upper-case, so I think we aught to just pick whatever is consistent (FWIW, a lot of our tooling prefers lower-case: both objdump and the Ibex instruction trace are in lower-case). We don't absolutely need to make it lowercase in this PR, but I agree with @rswarbrick that it's going to be fairly hard to read without syntax highlighting (and, in my opinion, // comments) anyway.

Thanks @rswarbrick and @mcy for your feedback. Changed mnemonics to lower case now.

CI fails with
../../../../sw/otbn/code-snippets/barrett384.S:35: Invalid option value, '.z'. If specified, it should have been '.Z'.
@rswarbrick should we allow case-insensitive/lower-case options like .z? I think yes.

Ah, I am just seeing that the .z is upper case in the other snippets as well:
https://github.com/lowRISC/opentitan/blob/master/sw/otbn/code-snippets/mul384.S#L30
Is there a reason why .so is lower and Z is upper? Thought both was part of the mnemonic

Thanks for following up here @mcy. With the mnemonics updated and the correct pseudoinstructions I think this looks good to me.

Ah, the difference is that we have 3 mnemonics for bignum multiplication: mulqacc, mulqacc.so and mulqacc.wo. The .z bit is technically an "option operand": something that is encoded as 1 if present and 0 if not. (There's some magic called "glued-ops" that allows you to write mulqacc.z rather than mulqacc .z)
As it stands, obtn-as does case-folding when checking mnemonics, but not when checking option operands or enums. This seems a bit silly to me: I'll push up a PR in a minute to case-fold those too.

That turned out to be easy! Case-folding PR at #3324.

This looks good to go, let's get it in!


[Git ACL] Cannot push branch to origin

Hello all.
I've reviewed Portuguese translation but I'm getting the error "remote: Permission to fetlife/translations.git denied to ElDomJuan" after doing "git push origin pt-revision". I've also tried with SSH, having the same problem.
It's first time I use github but I've used gitlab and bitbucket in the past. Should this be done by other way? The steps were the following:
$ git clone git@github.com:fetlife/translations.git .
$ git checkout -b pt-revision
Switched to a new branch 'pt-revision'
$ gedit locales/pt.yml
$ git add locales/pt.yml
$ git commit -s -m "Reviewed Portuguese translation based on en.yml and de.yml files"
[pt-revision 872fcdb] Reviewed Portuguese translation based on en.yml and de.yml files
1 file changed, 809 insertions(+), 809 deletions(-)
rewrite locales/pt.yml (70%)
$ git push origin pt-revision
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
ERROR: Permission to fetlife/translations.git denied to ElDomJuan.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$ git remote -v
origin	git@github.com:fetlife/translations.git (fetch)
origin	git@github.com:fetlife/translations.git (push)
Similar output was presented by doing git clone HTTPS

Hi @ElDomJuan. Thank you for wanting to help. You need to create a fork first: https://guides.github.com/activities/forking/.


python3Packages.versionfinder: init at 1.1.1

Motivation for this change
https://github.com/jantman/versionfinder helps find the version of another Python package, whether installed via pip, setuptools or git.
Dependency for #141518.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[X] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

@r-burns @fabaff thanks for the reviews, suggestions applied :pray:
Also please label for Hacktoberfest once accepted :smile_cat:


Jolt physics not working

Godot now works, but when trying to load an actual project it still runs into issues with missing libraries.
List the missing libraries and add them into the dockerfile.

It seems that the issue might be more with Godot Jolt and glibc.
Jolt was complaining about missing ld-linux-x86-64.so.2, which can be remedied by either installing the gcompat package, or alpine-pkg-glibc.
This however only raises another issue to the surface, namely:
ERROR: Can't open dynamic library: /Ikaros/Ikaros/addons/godot-jolt/linux/godot-jolt_linux-x64_editor.so. Error: Error relocating /Ikaros/Ikaros/addons/godot-jolt/linux/godot-jolt_linux-x64_editor.so: __cxa_thread_atexit_impl: symbol not found.
   at: open_dynamic_library (drivers/unix/os_unix.cpp:809)
ERROR: Can't open GDExtension dynamic library: /Ikaros/Ikaros/addons/godot-jolt/linux/godot-jolt_linux-x64_editor.so
   at: open_library (core/extension/gdextension.cpp:802)
ERROR: Failed loading resource: res://addons/godot-jolt/godot-jolt.gdextension. Make sure resources have been imported by opening the project in the editor at least once.
   at: _load (core/io/resource_loader.cpp:283)
ERROR: Error loading extension: res://addons/godot-jolt/godot-jolt.gdextension
   at: load_extensions (core/extension/gdextension_manager.cpp:234)

It is unclear to me how move forward from here. We can test loading a project that doesn't use Jolt physics and make sure that that at least works. This issue might also remedy itself once Jolt becomes the official Godot physics solution.

Confirmed that a project with no Jolt physics seems to work as expected.

Jolt physics is coming with 4.4 (https://godotengine.org/article/dev-snapshot-godot-4-4-dev-7/), creating a build in a local container to see if that succeeds with no build issues.

Editor confirmed to work for CI purposes in projects using Jolt physics in 4.4.


Exclude APIs members marked with [EntityFrameworkCoreInternal]

Public docfx allows filtering out APIs marked with a specific attribute. We can do this to keep out members annotated with [EntityFrameworkCoreInternal], assuming that works.

See proposed docfx change to do this (but against the wrong repo) in #3033.

See proposed docfx change to do this (but against the wrong repo) in #3033.


Ability to Pause model / throttle CPU

Feature request
The problem I'm facing, is that a running model within an extension, even on the background script, is blocking other actions within the extension. This means we cannot interact with any extension pages whilst a model is running (for example extension options/popup/new tab).
This is weird, as from what I understand background threads should be run separately.
A fix could be the ability to pause the model (perhaps you can provide the slice time when you run), then we could sleep / similar after each time slice, allowing the UI / other threads can catch up.
Perhaps some throttling of the CPU may also work.
https://github.com/xenova/transformers.js/issues/341 is a little similar (except cancellation)

Motivation
Long-running models are not very use-able right now within extensions, is there's also a UI - this feature would aim to improve this.
Your contribution
I could perhaps look into this, but some discussion first Perhaps once I have a better understanding of any current technical limitations.

Have you tried running the inference in a web worker?


pull request for e2e test at 01/16/2017 16:56:15

:white_check_mark: Validation status: passed
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.


Create zephyr-is-cool.dev.json

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.
[x] Your website is not hosting on the following due to SSL issues: Vercel, Netlify

Description

Link to Website

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 can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

recheck

I have read the CLA Document and I hereby sign the CLA

You do not need your Discord ID added in the JSON file, also you need to add a Description, domain you are using and subdomain name to the json file, please check out Here to see the json file should look like


print one to hundered

What does the program do ?

In what programming language it is written?

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Can't load Model

Hi, I heard about you nodes on discord and am really interested in trying them out, but for some reason, the Animate Diff loader is misbehaving. When I first load it the model name reads "null," when I click on again it changes to "undefined" but it won't let me load the model. . . I have downloaded the model that is suggested but it won't let me lod it, or anything for that matter. . .Several devs have done major updates in the last week, I wonder if one of them broke you nodes. . .

Hey, no new commits were added to my nodes in almost a week (I'm busy cooking up a new feature), so the repo should still be in a stable state. If the only problem is no motion modules found to be loaded, make sure the motion modules are inside the custom_nodes/ComfyUI-AnimateDiff-Evolved/models directory. You'll probably need to refresh the page once you insert the models into that directory. Let me know if that fixes your issue!

Were you able to fix your issue?

Well that is a complicated question. . .HA HA, short answer is yes, I got the models to load in the node, the long answer is that I haven't figured out how to make you node work for me yet. I'm trying to use it img 2 img, and so far I'm getting LOTS of noise. I imagine it is mainly the I need to mess with denoise settings. . .

Well I have no idea what I'm doing wrong, but regardless of which model I use, and whatever denoise setting I try, I basically get a lot of noise shaped like my init image. Sadly, I had high hopes for this. . .

Using init images currently is best done using controlnets and LatentKeyframes. I don't have that documented yet in this repo or the Advanced-ControlNet repo, but in the next couple days I will be adding more example workflows and more nodes.
There are also some things that can help what one would intuitively consider an img2vid workflow, like some tricks with adding noise differently to different frames. I'll be experimenting more with that this week.

Never would have occurred to me that the tile/inpaint controlnets could be utilized like this (outside of single images, hadn't tested these with animatediff, and that was months ago either way).
I think this might be something worth experimenting with, had attempted using IP-Adapter after observing good results outside of the motion modules, but I suspect the VRAM usage was causing glitches in the generations as the results weren't great or coherent.

Yes that is common practice in Deforum, although Temporal Net has shown more consistent promise. I will look forward to you implementation of these ideas.


Incorrect HTTP Response Status Code for Unauthorized Access

Hello,
I noticed an incorrect HTTP Response Status code being returned on the specification definition pages of Contract Negotiation and Transfer Process. The specifications define a return code 404 (Not Found) in case of Unauthorized Access. I am curious to why this code was chosen instead of the widely known and used 401 (Unauthorized Access)?
Here are the snippets where I found the use of 404.
Thanks in advance!
https://github.com/International-Data-Spaces-Association/ids-specification/blob/36960607a67793e3fc5089655102ac6d5b9b5445/negotiation/contract.negotiation.binding.https.md?plain=1#L80-L82
https://github.com/International-Data-Spaces-Association/ids-specification/blob/36960607a67793e3fc5089655102ac6d5b9b5445/transfer/transfer.process.binding.https.md?plain=1#L45-L47

We discussed that in the group. For security reasons, it is common practice to return a 404 instead of a 401 or 403 to avoid drawing conclusions about the existence or non-existence of a resource (negotiation, transfer).

Thanks for the response. I believe however 404 is being misused here, since it is designed to specifically indicate that an endpoint does not exist. In this scenario, a more generic code (400 - Bad Request) should be returned whenver a certain criteria is not fulfilled in order to maintain the security level. 404 directly indicates that a URL is non-existent.
Nevertheless, since the IDSA is working outside the defined HTTP standard codes here, it would be helpful to mention in the documentation that the standard is not being followed.


JavaEbean and evolutions

Though the JavaEbean examples does compile and run, if you add a value to a model, the app breaks because the evolution does not run and modify the database. This creates sql errors, cause the queries do not match the underlying database.
How can we get evolutions running with this example as it used to be with play 2.6?

Not 100% sure but there is a fix related to evolutions coming to Play 2.8.2: https://github.com/playframework/playframework/pull/10030 Maybe this fixes your problem. Play 2.8.2 should be released in the week of 25th of May.

@GBeushausen Can you test again? The samples are updated to Play 2.8.2 already (#104). Please let us know if that works for you now.

@GBeushausen I assume this has been fixed, like I commented already. If not, please let us know.


[WIP][PORT]Change Comparisons to ReturnType of 'template' function use bit opera…

ref: https://github.com/microsoft/botbuilder-dotnet/issues/3755
Originally, we use exact match of returntype to validate the correctness of function parameters.
But, then Expression achieved then ability to support composite types. So, LG/Expression should change the return type comparison, as long as they have the intersection of the same return type, it is correct in the static checker stage.

Pull Request Test Coverage Report for Build 121553

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 67.336%

Totals

Change from base Build 121267:
0.0%

Covered Lines:
10341

Relevant Lines:
14534

💛  - Coveralls


feat: Carry over auto-completed location when submitting a MyC artwork

This PR resolves ONYX-1059
Description
With this update, we correctly carry over the (new) auto-completed collector location when submitting a MyC artwork.
PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Carry over auto-completed location when submitting a MyC artwork - ole

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (Carry over auto-completed location when submitting a MyC artwork - ole)

  Generated by :no_entry_sign: dangerJS against 2ca39a0ccac51628bd1e6fed040a633b72e0ec94


TrayPublisher:psd background

Brief description
Just chore PR extracting parsing methods into separate reusable file. These functions should be refined further to make them more robust.
Testing notes:
Use with https://github.com/ynput/OpenPype-premium/pull/30

Task linked: OP-4760 Background batch must be rewritten for Tray publisher


[IoT Hub] How to setup IoT Hub file upload?

I'm trying to enable the IoT Hub file upload through the Azure CLI 2.0.
What I did is using the update command to set some related properties. For example:
az iot hub update --ids <iothub_id> --set properties.storageEndpoints.$default.connectionString="DefaultEndpointsProtocol=https;EndpointSuffix=core.windows.net;AccountName=<account_name>;AccountKey=<account_key>"

And after running the command, I get:
Couldn't find 'connectionString=DefaultEndpointsProtocol=https;EndpointSuffix=core' in 'properties.storageEndpoints.$default.connectionString=DefaultEndpointsProtocol=https;EndpointSuffix=core'. Available options: ['connectionString', 'containerName', 'sasTtlAsIso8601']
Seems the Azure CLI parsing the . incorrectly? Or am I using the command incorrectly?

FYI @xscript

@jdneo This is a code bug. It is been fixed already. You can read more details at #2527 .
The fix should be rolled out at the next release.

Hi @xscript, glad to see it has been fixed. And for now, what should I do if I want to configure the connectionString?

@jdneo I think you can do that from Azure Portal or use Azure Xplat CLI.

We want to provision azure resource in CLI. The Azure Xplat CLI works. But still hope that the Azure CLI can release ASAP :)


What is the format of "list" file?

I saw list files such as "LibriSpeech/list/train.txt" are required parameters for main.py. It seems such files are not provided by librispeech officially. What is the format of them? Could you provide them or the script to generate them?

I believe they are just lists of utterance ids. In my librispeech install, I found a bunch of files ending with .txt, that had utterance ids and transcriptions. This is how I generated the list files:
# Generates train.txt, eval.txt, validation.txt, which
# are just lists of utterance ids. This script looks
# at all the .txt files within LibriSpeech to extract
# the ids and write the files.
# An utterance id is a string like "61-70968-0009".

import os

trainroot = 'LibriSpeech/train-clean-100/' #, 'train-clean-360/', 'train-other-500/'
devroot = 'LibriSpeech/dev-clean/' #, 'LibriSpeech/dev-other/'
testroot = 'LibriSpeech/test-clean/'

def generate_list(root_dir, fn):

    # get the utterance ids
    utterance_ids = []
    for subdir, _, files in os.walk(root_dir):
        for filename in [f for f in files if f.endswith(".txt")]:
            with open(os.path.join(subdir, filename)) as f:
                ids = [l.split(" ")[0] + "\n" for l in f.readlines()]
                utterance_ids.extend(ids)

    # write them
    with open(fn, "w") as of:
        of.writelines(utterance_ids)

if __name__ == "__main__":
    generate_list(trainroot, "LibriSpeech/list/train.txt")
    generate_list(testroot, "LibriSpeech/list/eval.txt")
    generate_list(devroot, "LibriSpeech/list/validation.txt")

Dataset is available at the website http://www.openslr.org/12/


tart: init at 1.5.0

Description of changes

Tart is a virtualization toolset to build, run and manage macOS and Linux virtual machines (VMs) on Apple Silicon.

https://tart.run/
@dhess I've left you as a maintainer as this derivation is based on yours
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Also see https://github.com/NixOS/nixpkgs/pull/237895.

Why 2 PRs? Which one should we close ?

I'll close this one 👍


DM statistic calculated incorrectly

Hi, I had a doubt on the way the DM test is calculated? https://epftoolbox.readthedocs.io/en/latest/modules/statest/dm.html
This disagrees with other sources:

https://real-statistics.com/time-series-analysis/forecasting-accuracy/diebold-mariano-test/
https://www.lem.sssup.it/phd/documents/Lesson19.pdf

Why do you think it is different? It is the same as the one described in https://www.lem.sssup.it/phd/documents/Lesson19.pdf.

Closing due to inactivity


Unused generic parameters should not be hard compiler errors

IIRC this has been rust behavior from the very start, so perhaps it is sacrilegious to suggest it but I don't believe that unused generic parameters on enums, structs, and traits should be a hard error, and I do not see any reason why they need to be instead of a warning.
I often find myself omitting a member from a struct that was the only instance of a generic parameter or lifetime being used to try something out. Yes, it's possible to use a phantom marker but that isn't the most ergonomic approach.
Is there a reason besides ideological purity why an unused generic parameter if implemented correctly in all references to the object must be an error?
e.g. I do not think there is actual technical reason (i.e. unsoundness or ambiguity) why the following code should fail to compile:
struct Foo<T> {
    bar: String,
    // baz: Vec<T>,
}

impl<T> Foo<T> {
    fn new() -> Self {
        Self {
            bar: String::new(),
            // baz: Vec::new(),
        }
    }
}

fn main() {
    let foo: Foo<()> = Foo::new();
}

While <T> is not used in the definition of Foo, all references to Foo (such as impl Foo and the instantiation site in main) handle it and the compiler could theoretically accept this (with lots of grimacing and complaining), no?
For reference, the following error is currently returned:
error[E0392]: parameter `T` is never used
 --> ./test.rs:1:12
  |
1 | struct Foo<T> {
  |            ^ unused parameter
  |
  = help: consider removing `T`, referring to it in a field, or using a marker such as `std::marker::PhantomData`

error: aborting due to previous error

(Originally filed as https://github.com/rust-lang/rust/issues/70792)

One reason this is like this is that the compiler cannot infer the variance of T if it is unused, so requiring the user to mention it in a PhantomData makes clear what variance is desired. It could of course have a default, but which one is appropriate is probably not a trivial question.

My understanding is that while it is technically correct that an unused generic parameter cannot cause soundness issues on its own, there's also no reason you would ever want an unused generic parameter unless there is some sort of invisible or overly indirect reference to or ownership of a T which the compiler does not fully understand, in which case soundness almost certainly does depend on getting variance and drop check right, and PhantomData<T> is how Rust does that.
For prototyping / experimental coding, I understand how this looks excessive. But consider that the Vec<T> being commented out is being used to infer a variance. If we "just" allowed the code to compile anyway, we'd potentially be changing the variance we infer for the T type parameter. And that variance changing might cause other code to suddenly stop compiling, likely with an error that's very confusing no matter how well we word it because hardly anyone is consciously thinking about variance when they write their generic code (nor should they have to).
So AFAIK, there is no "ideological purity" going on, but rather a combination of the cold facts about soundness mentioned above and these additional beliefs:

in production code, a type parameter which is truly not used in any way is always a logic error; there simply is no use case for it that we know of
in production code, when a type parameter is "used" in some way the compiler does not understand, a PhantomData<T> field is the most ergonomic way to get variance and drop check right
even in prototype code, an unused type parameter (if allowed) would often affect variance or drop check in ways that lead to hard errors elsewhere
a compile-time error about unused generic parameters asking you to use a PhantomData<T> is far, far easier to understand than a compile-time error about variance mismatches or sound generic drop requirements

If we start with the premise (which I think we can all agree on) that code should never be committed/deployed into production with warnings, that really puts a temporal restriction on how far apart "obviating an unused parameter" and "getting obscure compilation error" can be. More importantly, I think that the points you bring up can actually be copy-and-pasted more or less unchanged for most warnings emitted by the rust compiler - I don't particularly see why they would necessarily be more pertinent to an unused generic parameter over some of the other code-smell issues that currently raise warnings and not errors. In fact, I would argue that what you describe is the definition of a compiler warning: you are doing something technically correct but it is emitting great code smell and is likely to cause you grief down the line if not corrected or addressed, and can only be ignored by specifically #[allow(..)]ing the code or practice in question.
Specifically with regards to default variance, the options as I see them would be to assume an implicit PhantomData<&'a T> (assuming both an unused generic lifetime 'a and unused generic parameter T), although I do wonder if there are cases where that might trigger an  immediate compilation error rather than "at some point in the future".

We might consider const  members of structs so
struct Foo<T> {
    bar: String,
    const baz: PhantomData<Vec<T>> = PhantomData,
}

More importantly, I think that the points you bring up can actually be copy-and-pasted more or less unchanged for most warnings emitted by the rust compiler

Some can, but I believe the "lead to hard errors elsewhere" and "obscure" points are fairly unique in this case. An unused variable could conceivably lead to other self-explanatory unused/dead warnings within the same function, but it can't cause a subtle type checking failure five modules away like this could.
Assuming a default variance is certainly an option, but I doubt it'd be a net win. Both covariance and invariance are quite common in practice (even if contravariance is pretty rare), and relying on covariance is also pretty common. But I have no idea how to make that quantifiable enough to presuade anyone who feels otherwise.

If we need to pick a "default variance" it should be the most conservative variance (ie. invariant) not what covariant (as PhantomData<T> would give you).

error[E0392]: parameter T is never used implies the compiler is indeed capable of identifying the generic type parameter T as unused and could therefore ignore it and only warn. But of course this – and IMHO any warning – should not be allowed in production/final code.


[Saas Connectors] Segment Masking [#354]

Purpose
Adds demonstration of a masking for third party integration: Segment.  Rather than issuing individual updates, a data_protection_request is defined in the yaml that issues something like a GDPR delete request that removes all data, regardless of what is defined on the Policy.
Changes

Fixes some bugs in the Segment data_protection_request that was introduced in Segment access request work in #350
Adds additional segment secrets for creating test user data
Adds a segment erasure end-to-end integration test that creates user data, and events, runs an access request (which also makes sure that user data is there) and then runs an erasure.  The test confirms that the erasure was attempted, but we cannot verify the data is erased here due to the delays on the segment side (erasures I submitted 4-5 days ago have not completed yet)
Updates Segment postman collection

Checklist

[x] Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram)
[x] Good unit test/integration test coverage
[ ] This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
[x] The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket
Fixes #354

Getting this up to date ^

thanks for your review @eastandwestwind!


What is the role of Log-sum-exp?

In your code for defining Loss function, you firstly take the log of distributions then add them up, whereas the loss mentioned in Bishop is log of sum of distribution.I am confused, Maybe there is something in trick you used for log-sum-exp.
Can you please formulate this?

Hi navidstuv
See page 19 in the slides or page 39 in the MSc thesis for an explanation.
I hope this helps.

not to have a too big exponent he substracts the max


How to use renderitem?

I'm sorry that's probably a noobish question but how can I use renderItem?
I'm using the ngx-quill library to user quill-mention in Angular. Everything works like a charm but I can't figure out how to render items in a certain way using renderItem.
this.modules = {
  toolbar: null,
  mention: {
    mentionDenotationChars: ['#', '@'],
    allowedChars: /^[A-Za-z\sÅÄÖÜåäöüß]*$/,
    source: (searchTerm, renderList) => {
      this.onSearch(searchTerm, renderList);
    },
    renderItem: (item, searchTerm) => {
      console.log(item);
      return `<span>test</span>`;
    }
  },
};

const memberName = document.createElement('span');
memberName.style.color = '#fff';
memberName.textContent = item.value;
return memberName


Do not restart application if no changes

I'm testing local deplo process with ecosystem where I deploy to local machine.
I've noticed that pm2 restarts even if there is no changes (same git sha).
Is it possible to avoid application reload/restart if there are no changes to code?

Any comment on this?

you can use startOrReload if all of your application are running in cluster mode to achieve 0s downtime during the deploy.
if this is not enough, explain the problem and we will consider if implementing this as a feature. @vmarchaud what do you think about this?

@phra It's interesting, we can add an option that check the commit hash before and after the pull, but i would say that it's in the user responsibility to deploy only when there are changes to pull.
It can be confusing to add behavior like this for new user if no log are printed.

let's wait for more infos from @manico

@phra I have tried startOrReload and as I recall it made no difference.
@vmarchaud You are right, it is user responsibility. We have some automated system that runs pm2 deploy so maybe that is some use case.
Will try to create simple working example if it is needed.

i have already a minimal repro example for pm2-deploy, you can find it here: https://github.com/phra/pm2-deploy-repro-env
i will try to implement this feature if i can.


Add support for click_action

click_action    Optional, string

The action associated with a user click on the notification.

iOS: Corresponds to category in the APNs payload.
Android: If specified, an activity with a matching intent filter is launched when a user clicks on the notification.

https://developer.apple.com/documentation/usernotifications/declaring_your_actionable_notification_types?language=objc
https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/SupportingNotificationsinYourApp.html#//apple_ref/doc/uid/TP40008194-CH4-SW26

You could steal what they have in the cordova-plugin-firebase

Any updaes of this?

I am also looking for the same functionality. Any updates on this?

@chemerisuk Any updates on this?

I am not sure if i understood you right but using the onBackgroundMessage should be what you are looking for. This is called, when the user clicks on the notification and the app opens.

I am not sure if i understood you right but using the onBackgroundMessage should be what you are looking for. This is called, when the user clicks on the notification and the app opens.

But it does not fire any callback event when click on the head up notification on android

I am not sure if i understood you right but using the onBackgroundMessage should be what you are looking for. This is called, when the user clicks on the notification and the app opens.

But it does not fire any callback event when click on the head up notification on android

It should. It does fire onBackgroundMessage callback in my code. If nothing happens after the notification being clicked. One possible reason is you have click_action in your fcm notification payload but doesn't have corresponding intent filter setup in your manifest.xml

For those that haven't used Intent filters before (like me) It was a little confusing trying to get it to work but after some trial and error I managed to get it working with this code.
Inside config.xml within the android platform tags:
<!-- notification redirect on notification tap -->         <config-file target="AndroidManifest.xml" parent="/manifest/application/activity">             <intent-filter>                 <action android:name="FCM_PLUGIN_ACTIVITY" />                 <category android:name="android.intent.category.DEFAULT" />             </intent-filter>         </config-file>
This is what my cloud function looks like:


Revise headless mode

I think headless mode needs to be rethought. Instead of instant creation with applyTemplate, we should keep this a two step process. On the one hand, things will make things more consistent with popup mode. On the other hand, it will give more flexibility to how host applications can implement their workflow in headless.
The two scenarios I want to be possible are:

Picking a tag from a list/menu and then labeling (like applyTemplate works now)
Draw first, and then edit annotation contents in you own (eg sidebar) editor while the annotation is still in draft mode

Necessary changes include:

onCreateSelection event
createFromSelection(bodies) API method

Mostly done now. Needs a bit of cleanup + a decent tutorial/guide on the website.

Another advantage of the new API will be that it will allow for editable shapes (wherease applyTemplate would store the shape immediately). New API additions are

createSelection event - use this to listen to a new selection being created by the user
updateSelected(annotation, saveImmediately) API method - modify the selected annotation (and immediately save, if you want)
saveSelected() API method - "hit save" programmatically
cancelSelected() API method - "hit cancel" programmatically

Implemented (beta) for Annotorious. What's missing is an implementation in the OpenSeadragon plugin + documentation. (And probably an implementation in RecogitoJS, at least later.)

See issue #80 for the one big part that's still missing


Add text classification example

Hi Greg. This is awesome. Read the paper earlier as well and thought it was awesome. Thanks man, this is very cool!
Tried the regular approach (now busy on the alternative one).
I double checked and did exactly as was outlined. I do get an error.
The error is
/usr/share/lua/5.1/cudnn/TemporalConvolution.lua:92: bad argument #1 to 'size' (out of range)
And the verbose output of torch is
Last output:
Running initial validation before first train epoch..
Validation (epoch 0): loss = 3.2712374114555, accuracy = 0.071214285714286
Training (epoch 0.0005): loss = 4.3866891860962, lr = 0.01
/usr/share/lua/5.1/cudnn/TemporalConvolution.lua:92: bad argument #1 to 'size' (out of range)

Weird. I might try recreating the dataset to make absolutely sure i made it correctly. However, did seem to pass the Validation epoch (7.12% accuracy epoch 0) which tells me that the model and the data are probably legit.

Hi @TimZaman thanks for the feedback! I used cudnn.TemporalConvolution to train the network (I found it to be 17 times faster than the regular nn.TemporalConvolution! Just to check: did you remember to set mean subtraction to none when you created the classification model?

hi @TimZaman are you still having an issue with this example?

Hi @gheinrich, i did not use mean substraction as i was supposed to.
I have last week swapped the (bit) outdated torch-nv to the normal torch installation. This did the trick. Other than the easy install of torch-nv, are there any advantages in using torch-nv wrt the build from source?

I tested the dataset creation and import. When I tried to test the model, I got this error:
[FAIL] ...5-02/install/share/lua/5.1/cudnn/TemporalConvolution.lua:92: bad argument #1 to 'size' (out of range)

Maybe it's because I don't have this commit: https://github.com/soumith/cudnn.torch/pull/152? I had to start with a non-standard fork (16.04 issues), so I'm having trouble updating just the cudnn module. Sorry for my noobery! I'll find some time to figure out the Torch build system and keep testing this, but it looks good so far.

Oh so it's the same error @TimZaman got. You could update just cudnn by doing something like:
$ cd .../torch/extra/cudnn
$ git fetch origin && git checkout origin/master
$ luarocks make cudnn-scm-1.rockspec

Other than the easy install of torch-nv, are there any advantages in using torch-nv wrt the build from source?

I don't know of other advantages...

Yeah so the cudnn stuff is not DIGITS related. @gheinrich I would recommend just leaving out the cudnn, switch to nn, albeit 17x slower (worked fine with me, but maybe make a note about cudnn being faster but you'd have to update) and just merge.

Got it working. Cool tutorial!


Image Overlay ?

Hey, great (and fast!) Library!
I found this as most modern js image processing libraries are quite outdated, yours could be one of the best around if you gave it an update. :)
Also, using .png images as an overlay would be great as a new feature.

What sort of update? As far as I know, the library still works in all current browsers.
Adding "stickers" on top of images is way out of scope for this library - and easily solved without a library anyway. Just render the filtered image into a 2d canvas and draw the image on top.

Would be nice to have this rendered in WebGL, too. With the possibility to use some Photoshop Layer Blend modes.
See: https://www.shadertoy.com/view/XdS3RW

Most(?) of these blend modes are now supported in Canvas2D as well.
https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/globalCompositeOperation

I think this issue can be closed? Sounds like the library author has marked this out scope.


Update StrVCTVRE memory

Just a quick bump, failing job here
https://batch.hail.populationgenomics.org.au/batches/431069/jobs/127

closing


Consider recompiling libgcc/libkmc functions instead of ignoring them

Currently Recomp ignores a lot of libgcc functions and expects the user to provide manual reimplementations, Ideally those could get recompiled instead.
This was brought up here: https://github.com/Mr-Wiseguy/N64Recomp/pull/35#discussion_r1599366905

After some testing seems like the recompiler can handle just fine __muldi3 and __umoddi3, but it has problems with __divdi3, __udivdi3 and __moddi3.
This seems to be caused because the recompiler can't handle a function jumping or branching outside of the boundaries of the function.
So we would need to implement some way to handle tail call optimizations to get those working.
I'm testing libkmc btw, I haven't looked at other libgcc implementations like libegcs or a modern libgcc


CreateCollection: Check if a table follows Data API collection pattern

When user does createCollection with a collection name called apple,
table apple exists but that is not a Data API table (column missing),
we should error out and notify user.
(Previously, since Data API does not error out this situation, and that will give user a weird error with following indexes creation)
Which issue(s) this PR fixes:
#1198
Checklist

[x] Changes manually tested
[x] Automated Tests added/updated
[x] Documentation added/updated
[x] CLA Signed: DataStax CLA

Possible to add some tests?
I have tested in my local.
This is not a common Data API use case.
In order to replicate we need to create a cassandra table first, and that is a hustle we have never done in Integration Test.


arm build wheel for apple m1

Please note
If you are reporting an installation or module import issue, please note that
this project only accepts reports about problems with packages downloaded from
the Python Package Index. Conda users should take issues to one of the
following trackers:

https://github.com/ContinuumIO/anaconda-issues/issues
https://github.com/conda-forge/shapely-feedstock

Expected behavior and actual behavior.
expect to install the wheel of shapely==1.8.1
currently it downloads the source and build locally, which will be missing the libgeos
Steps to reproduce the problem.

on mac m1 using docker client

docker run --rm -it python:3.9.10-slim pip install shapely==1.8.1
Collecting shapely==1.8.1
  Downloading Shapely-1.8.1.tar.gz (278 kB)

Operating system
mac m1
Shapely version and provenance
1.8.1 and 1.8.1.post1

Encountered the same.
Weird, since looks like the tests build it correctly, but it doesn't build with docker.

Such manylinux aarch64 wheels were build for Shapely 1.8.0, so a temporary solution is to either 1) pin to 1.8.0, or 2) to ensure you have GEOS installed in the docker container before pip installing Shapely.
The reason for not having aarch64 wheels at the moment is because those are build on Travis, which is currently disabled for shapely due to their new OSS policy ("negative credit balance")

I wonder if a QEMU solution would work for Shapely: https://github.com/uraimo/run-on-arch-action

We tried that before (using the docker/setup-qemu-action action), it worked but we stopped using it because it took a very long time (for pygeos, but the wheel building infrastructure has now been copied exactly into Shapely): see https://github.com/pygeos/pygeos/issues/442
For the main branch, we have Travis set up again, so as long as that keeps working, that seems like a good alternative (although having everything in a single workflow in github actions would of course be easier to maintain)

@jorisvandenbossche That sounds great. Definitely understand the maintenance burden that comes with multiple CI systems, and the unfortunate pain caused by Travis back-peddling their "free for open source forever" statement.
Hopefully GitHub Actions/Azure will have an ARM solution soon.
Thanks!


remove jwt typ requirement

Summary
This PR removes the typ requirement for JWTs.
Rationale
section 5.1 of RFC7519 typ is not a required parameter in a JWT

Requiring that it be set and then further requiring that typ MUST be JWT is prevent folks from being able to set it to values that other specs require e.g. openid4vci-proof+jwt
Changes

removes typ requirement from Jwt.parse
adds option for caller to provide typ when calling Jwt.sign

@nitro-neal that's specific to verifiable credentials. Jwt gets used outside the context of just VCs.

@nitro-neal looks like there's a test failing bc did:dht resolution is failing


Update for compatibility with recent versions of ActiveRecord / Money gems.

Renamed Entry to Transaction
Changed use of Money gem in most cases to not use string parsing (monetise gem is included for that feature)
Workaround for composed_of.
etc.

This repo has been long overdue for a compatibility update for Rails 4.1.  And what you have changed thus far looks solid.  Much appreciated!


Option to save self_signed certs

Currently when you run caddy using the tls self_signed directive caddy regens the certs on restart meaning I then have to open each domain one by one in my browser and accept the warning. It'd be nice if Caddy had an option to just dump the certs into the path provided.
Maybe something like so? This way it can just reuse the certs the next time it starts.
tls self_signed /Users/xo/certs

Is this for a localhost domain? In Chrome, you can set this flag: #allow_insecure_localhost

I'm using example.com as well as a load of subdomains of it as localhost isn't an actual domain so it doesn't allow subdomains.

Would generating your own certs (and then point to those with the tls directive) work for you as a short term solution?

For the short term sure, that's what I ended up doing for now. In the long run this would fix the issue of needing to generate new certs myself every time I need to do testing across multiple subdomains.

Could this be implemented, please? This will save a lot of hassle for Firefox users.

We are happy to accept a PR implementing this if someone wants to give it a try.  It should be quite straightforward.
Is it possible to explain why LetEncrypt certs are not a possibility here?  If you have a simple public domain you can create any number of subdomains on it internally.  Is there a specific reason why self_signed certs are required?

It's for dev only. Firefox only allows you to add exception for certs, no way like in chrome to allow insecure certs on all local connections. And the exception becomes stale as soon as you generate a different cert, which happens every time you restart caddy.

@tobya at the time I had hit the rate limit for let's encrypt on all my domains so I had to use self signed ones while testing.

@princemaple you can still use letsencrypt for dev sites.  I still don't understand the issue that requires you to use self_signed certs.  I'm just trying to understand the real issue here.  Perhaps it is ratelimits, firewalls, company policy, but I would like to get to the real issue to see if this is the only way of solving it.
@OmgImAlexis if you use the staging environment for lets encrypt by starting caddy like this
caddy -ca https://acme-staging.api.letsencrypt.org/directory

you essentially end up with the same as self_signed certs (untrusted certs) but they will be stored and reused by caddy.  The rate limits for lets encrypt when using their staging environment is much much higher, so I think this is a solution to your problem.  Self_signed certs are really for installations that do not allow access in on :443

Letsencrypt works for local dev? I did not know that. How? The domain practically does not exist.

"Dev sites" is a bit ambiguous, yes; I do use LE's staging endpoint for "local" development sometimes; it works if the domain's records point to your home machine and you configure your home network to forward ports. But for purely local development, no, it will not work, unless you set up your own Boulder instance internally.
But that's a hassle. What if Caddy persists self-signed certs for 30 days in $CADDYPATH/self_signed?

It does fit nicely with the "easy to use" objective of Caddy.
No need to create a self signed certificate yourself. If this feature existed a few months ago I would have used it :smile:

@twdkeule To be clear, it does already exist (tls self_signed), but it's a different cert each time you run Caddy. (The intent was always to make the developer rely on self-signed certificates as seldom as possible.)

What if Caddy persists self-signed certs for 30 days in $CADDYPATH/self_signed?

It would make my life much easier :) no longer need to click 3 times to add an exception every time I restart caddy. Doing it once a month is totally acceptable.

@mholt I'm sure @twdkeule knows that, just that for persistence currently we have to generate the certificate separately and specify it with the tls <cert> <key> format.
Big 👍 from me to add persistence for self signed certs

I was talking with @mholt about this on the forums recently. We came to an agreement that the point of self-signed certs within Caddy, are by design temporary. However, I was able to modify https://github.com/openwisp/django-x509 to generate browser-friendly internal certs for my needs.

By way of update: This may become moot if localhost domains become trusted zones. There's a proposal along those lines. Until that is dismissed, I don't think I am interested in a change to Caddy that gives self-signed certs more weight than they're worth...

Another issue I've found is if you're using multiple sites with self_signed and you use SIGUSR1 it will recreate all self_signed certs.

@OmgImAlexis This is the intended behaviour.  Self Signed certs are meant as a temporary or interim solution rather than a permenant solution.

I think I will close this issue as it is not currently planned for implementation.

Caddy 2 (starting with beta 17) solves this problem.