Solve issues with monitors not serving anything after some days/weeks

Describe the bug
RIPE RIS and bgpstream may suddenly stop serving BGP updates, while the connection remains open.
Affected Component(s)

[X] Back-End (Database, Microservices, Containers, etc)
[ ] Front-End (Flask, API, etc)
[ ] Docs
[ ] Build System

Additional context
Maybe periodically restart the monitors?
Need to add safe-guards and checks for:

RIPE RIS
bgpstream

one solution to this:

each monitor reads a counter (initialized to 0) from a file (e.g., ripe_ris_bgp_update_cnt.txt).
it writes to the file a +1 counter value every time it receives a valid BGP update
an hourly cron job checks the counter every hour
if < than a threshold (e.g., 1, can be an env variable), then it restarts the monitor (only if it was already active), otherwise it simply resets the counter to 0 by writing to the file

updated approach:
cron job:

connects to redis (of course we need to make sure that redis is up for this, it should retry until it is up)
checks values of type "ripe_ris_seen_bgp_update"
if it does not find anything, it checks if the corresponding monitor is running and if yes restarts it

monitor:

when it sees an update, it writes one bit to the corresponding "ripe_ris_seen_bgp_update" redis variable and resets the expiry time to e.g., 1 hour.


Flags member of struct NDIS_QOS_PARAMETERS is not defined

On this page:
https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntddndis/ns-ntddndis-_ndis_qos_parameters
The description for the Flags member of the structure has a link named "Overview of the Flags Member".  This link goes to a generic page and there is no useful description anywhere of what NDIS_QOS_PARAMETERS::Flags should contain.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f18a2491-1114-cb60-b438-8b235ef9733f
Version Independent ID: 3cd65f6b-4f79-fde8-977e-045f8c799473
Content: _NDIS_QOS_PARAMETERS (ntddndis.h) - Windows drivers
Content Source: wdk-ddi-src/content/ntddndis/ns-ntddndis-_ndis_qos_parameters.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @aviviano
Microsoft Alias: amvivian

Thanks @MrDavid949. The link should go to the section "Overview of the Flags Member" at the bottom of the page (not a new page). I'll close this issue once the fix is live on the site.


unifi-poller on windows, keep running while logged out?

How can I make it as a persistent service on a windows server background with its parameter regardless of affecting log off. I have looked at some samples but could not find a solution.
This is executed on a windows command line, below. However, I want to run it as a service. I have tried .bat, set command, nssm tool to create a service, but I could not attach its -c up.conf parameters. How can it be run as a service on a windows server? Thanks
unifi-poller.exe -c up.conf

The default config file location on Windows is C:\ProgramData\unifi-poller\up.conf
If the config file is there you do not need to pass -c anything as a parameter.
Beyond that, this app has no special hooks to make it work as a Windows service. I'm afraid I do not use Windows enough to give you information on how to run this app without logging, or after logging out.  I'll leave this issue open in case someone else knows.

Using powershell - Declare a service:
New-Service -Name "Unpoller" -DisplayName "Unpoller Service" -Description "Unpoller Service" -StartupType Manual -BinaryPathName "Path-To-Unpoller.exe --service"

Start the service:
Start-Service -Name "Unpoller"

Stop the service:
Stop-Service -Name "Unpoller"

Uninstall a service:
sc.exe Delete "Unpoller"

Someone wrote a wiki entry for unpackerr on this topic. https://github.com/davidnewhall/unpackerr/wiki/Running-unpackerr-as-a-Windows-service
Should be mostly the same process. The procedure that @platinummonkey posted looks pretty easy though.


[BUG] Recommendations List API missing attributes

API Spec link
https://learn.microsoft.com/en-us/rest/api/advisor/recommendations/list?view=rest-advisor-2023-01-01&tabs=HTTP
API Spec version
2023-01-01
Describe the bug
Response not compliant with documentation, missing some attributes
Expected behavior
"value":[    {       "id":"/resourceUri/providers/Microsoft.Advisor/recommendations/recGUID1",       "name":"recGUID1",       "properties":{          "category":"HighAvailability",          "impact":"Medium",          "impactedField":"Microsoft.Compute/availabilitySets",          "impactedValue":"armavset",          "lastUpdated":"2017-02-24T22:24:43.3216408Z",          "risk":"Warning",          "remediation":{             "additionalProperties":{                "httpMethod":"POST",                "uri":"uri",                "details":"link to document"             }          },          "shortDescription":{             "problem":"To ensure high availability add one or more virtual machines to this availability set",             "solution":"To ensure high availability add one or more virtual machines to this availability set"          },          "resourceMetadata":{             "resourceId":"/subscriptions/subscriptionId/resourceGroups/resourceGroup/providers/Microsoft.Compute/availabilitysets/abc",             "action":{                "additionalProperties":{                   "actionType":"Document",                   "link":"https://link3",                   "caption":"Enable Soft Delete to protect blob data",                   "description":"Enable Soft Delete to protect blob data"                },                "metadata":{                   "id":"/subscriptions/subscriptionId"                }             },             "singular":"Availability set",             "plural":"Availability sets"          },          "actions":[             {                "additionalProperties":{                   "actionType":"Document",                   "link":"https://link1",                   "caption":"Enable Soft Delete to protect blob data",                   "description":"Enable Soft Delete to protect blob data"                },                "metadata":{                   "id":"/subscriptions/subscriptionId"                }             }          ],          "description":"After enabling Soft Delete, deleted data transitions to a soft deleted state instead of being permanently deleted. When data is overwritten, a soft deleted snapshot is generated to save the state of the overwritten data. You can configure the amount of time soft deleted data is recoverable before it permanently expires.",          "label":"Enable Soft Delete",          "learnMoreLink":"https://link2",          "potentialBenefits":"Save and recover your data when blobs or blob snapshots are accidentally overwritten or deleted"       },       "type":"Microsoft.Advisor/recommendations"    }
Actual behavior
{ "properties":{ "category":"HighAvailability", "impact":"High", "impactedField":"MICROSOFT.COMPUTE/DISKS", "impactedValue":"AADJoinVM_OsDisk_1_01c956f5872647f3ad36daee1c169805", "lastUpdated":"2024-02-25T20:59:57.0398805Z", "recommendationTypeId":"d4102c0f-ebe3-4b22-8fe0-e488866a87af", "shortDescription":{ "problem":"Use Azure Disks with Zone Redundant Storage for higher resiliency and availability", "solution":"Use Azure Disks with Zone Redundant Storage for higher resiliency and availability" }, "extendedProperties":{ "Location":"westus2" }, "resourceMetadata":{ "resourceId":"/subscriptions/subid/resourceGroups/AVD/providers/Microsoft.Compute/disks/AADJoinVM_OsDisk_1_01c956f5872647f3ad36daee1c169805" } }, "id":"/subscriptions/subid/resourceGroups/AVD/providers/Microsoft.Compute/disks/AADJoinVM_OsDisk_1_01c956f5872647f3ad36daee1c169805/providers/Microsoft.Advisor/recommendations/99c3c772-f9f1-8447-91c2-94102cc65f97", "type":"Microsoft.Advisor/recommendations", "name":"99c3c772-f9f1-8447-91c2-94102cc65f97" }
Reproduction Steps

GET https://management.azure.com/subscriptions/subscriptionId/providers/Microsoft.Advisor/recommendations?api-version=2023-01-01
Read the response

Environment

Azure-mgmt-advisor version 9.0.0
Windows Server 2022:
Python 3.12:

@shavital7 Please help have a look, thank you.

@shavital7 Please help have a look, thank you.

@zzhxiaofeng this should be handled by Microsoft.Advisor owners, not Microsoft.RecommendationsService

@shavital7 Sorry, I see.

@brandonh1994 Please help have a look, thank you.

This is behaving as expected. The metadata returned varies based on what each PG team provides per recommendation. The documentation needs to be updated and a task has been created internally and will be prioritized with the other already in-flight work.


Only Cuda supported duh!

rzai@rzai00:~/prj/nips2016$ bash scripts/train_cub_keypoints.sh
{
img_dir : "/media/rzai/ai_data/www.vision.caltech.edu-visipedia-CUB-200-2011/CUB_200_2011/CUB_200_2011/images"
name : "cub_kp_nh1_z0_kd16_bs16_ngf128_ndf128"
txtSize : 1024
niter : 600
batchSize : 16
ndf : 128
nz : 100
numCaption : 4
gpu : 0
filenames : ""
decay_every : 100
cls_weight : 0.5
noise : "normal"
ntrain : inf
keypoint_dim : 16
num_holdout : 1
beta1 : 0.5
nThreads : 8
lr_decay : 0.5
init_g : ""
fineSize : 128
use_cudnn : 1
loadSize : 150
checkpoint_dir : "checkpoints"
init_d : ""
ngf : 128
nt : 128
dbg : 0
zero_kp : 0
print_every : 10
lr : 0.0002
num_elt : 15
data_root : "../../_reedscot/de_nips2016_data.tar.gz/nips2016_data/cub_keypoints"
save_every : 100
port : 8000
doc_length : 201
dataset : "cub_keypoint_and_image"
display_id : 7240
display : 1
}
Random Seed: 2400
Starting donkey with id: 2 seed: 2402
Starting donkey with id: 7 seed: 2407
Starting donkey with id: 5 seed: 2405
Starting donkey with id: 8 seed: 2408
Starting donkey with id: 4 seed: 2404
Starting donkey with id: 6 seed: 2406
Starting donkey with id: 3 seed: 2403
Starting donkey with id: 1 seed: 2401
Dataset: cub_keypoint_and_image	 Size: 	11788
/home/rzai/torch/install/bin/luajit: /home/rzai/torch/install/share/lua/5.1/nn/Container.lua:67:
In 1 module of nn.Sequential:
In 1 module of nn.ConcatTable:
In 1 module of nn.Sequential:
In 1 module of nn.ConcatTable:
In 1 module of nn.Sequential:
In 1 module of nn.ConcatTable:
In 1 module of nn.Sequential:
In 1 module of nn.ConcatTable:
In 2 module of nn.Sequential:
...torch/install/share/lua/5.1/cudnn/SpatialConvolution.lua:32: Only Cuda supported duh!
stack traceback:
[C]: in function 'assert'
...torch/install/share/lua/5.1/cudnn/SpatialConvolution.lua:32: in function 'resetWeightDescriptors'
...torch/install/share/lua/5.1/cudnn/SpatialConvolution.lua:96: in function 'checkInputChanged'
...torch/install/share/lua/5.1/cudnn/SpatialConvolution.lua:120: in function 'createIODescriptors'
...torch/install/share/lua/5.1/cudnn/SpatialConvolution.lua:187: in function <...torch/install/share/lua/5.1/cudnn/SpatialConvolution.lua:185>
[C]: in function 'xpcall'
/home/rzai/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/home/rzai/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function </home/rzai/torch/install/share/lua/5.1/nn/Sequential.lua:41>
[C]: in function 'xpcall'
/home/rzai/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
...
/home/rzai/torch/install/share/lua/5.1/nn/ConcatTable.lua:11: in function </home/rzai/torch/install/share/lua/5.1/nn/ConcatTable.lua:9>
[C]: in function 'xpcall'
/home/rzai/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/home/rzai/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function 'forward'
main_cub_keypoints.lua:375: in function 'opfunc'
/home/rzai/torch/install/share/lua/5.1/optim/adam.lua:37: in function 'adam'
main_cub_keypoints.lua:448: in main chunk
[C]: in function 'dofile'
...rzai/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00406670
WARNING: If you see a stack trace below, it doesn't point to the place where this error occurred. Please use only the one above.
stack traceback:
[C]: in function 'error'
/home/rzai/torch/install/share/lua/5.1/nn/Container.lua:67: in function 'rethrowErrors'
/home/rzai/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function 'forward'
main_cub_keypoints.lua:375: in function 'opfunc'
/home/rzai/torch/install/share/lua/5.1/optim/adam.lua:37: in function 'adam'
main_cub_keypoints.lua:448: in main chunk
[C]: in function 'dofile'
...rzai/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00406670
rzai@rzai00:~/prj/nips2016$

this is caused by a wrong config by myself

Hi @loveJasmine , may I know what kind of wrong configs? Because I am facing this issue now but I can't find any answers on internet.
Appreciate.

oh， the task had done several weeks ago, I am forget it.
maybe you should reinstall torch and the packages

I'm having the same issue. Is there any known solution? My Torch installation is fresh. Using Lua 5.1, CuDNN 5.1, CUDA 8.x.


Failed to deploy the azure function

I have a static website built with Hugo + TailwindCss hosted on a free plan on Azure Static Site. However I cannot deploy it to Azure when I include an api folder. The error message in Oryx logs is Failed to deploy the azure function. (I've attached the logs.txt)
How I have set-up the repo:

Site uses Hugo and Tailwind
App build command in the workflows file is as follows (file is attached)

app_build_command:  |
            npm install postcss postcss-cli tailwindcss
            npm install -D @tailwindcss/aspect-ratio
            npm install -D @tailwindcss/forms
            npm install -D @tailwindcss/typography
            npx tailwindcss init
            npx tailwindcss -i ./assets/styles/input.css -o ./assets/styles/main.css --minify
            hugo --minify

It's a private repo with a submodule for the theme
the Api is written in dotnet:6.0
I have added the "platform": {"apiRuntime": "dotnet:6.0"} in the staticwebapp.config.json (file attached.)
The api works with SWA cli on my local machine.
The api works when I deploy it as an Azure function and link it to the static website as a Bring your Own function. For which I have to use a paid subscription. 💰

staticwebapp.config.json.txt
logs.txt
Github_Action_yaml.txt

@H-Ashrafi Do you have any app settings in your api definition or your Static Web App that begin with FUNCTION_ or WEBSITE_ ? These are not allowed with the free, managed Azure Functions with Static Web Apps per these docs: https://learn.microsoft.com/en-us/azure/static-web-apps/apis-functions#constraints but are allowed when you link a Bring-Your-Own Function.

Thanks @mishapos **that solved the problem. **
There were two env variables that Azure had created automatically when I built the static web app service. It'd be a massive time saver if the portal would delete those when an api got uploaded.


Another date format: 'January 02, 2006, 15:04:05'

I've just run into a few more date formats that I think would be good to have:
January 02, 2006, 15:04:05
January 02, 2006 15:04:05
January 02, 2006 03:04:05 pm
Basically, the same as "September 17, 2012 at 10:09am PST-08" but without the 'at' and a couple variations.
Thanks!

I just noticed the very first one on the list fits, but having 24 hour as an option would be nice.

thanks for the report, will try to get them in next couple days!


Update ansible 2.1 installation instructions in hortonworks

Update ansible 2.1 installation instructions in hortonworks

closed by #25


Support codecov to show code coverage

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


"State rewind" feature.

There is an exercise in UI design lurking to allow state navigation & selection.


Add BNS api

Add api to get info on a particular BNS domain, including what address it resolves to, if any, as well as history, metadata hash, and all the other information. Thinking would be the best approach to integrate BNS into creeper, and also might be useful for the reddit and discord tip bots. Tested locally and worked, though I had to comment out some stuff because I did not have redis, etc set up.

I also "had" to bump "es2017" to "es2020" because of the new dependency, didn't seem to cause any problems. I can make the dependency work with "es2017" if that is an issue.


[EK-35] Use MemoizingRcutilsLogger in bdai_ros2_wrappers.node.Node

Follow-up to #84. In hindsight, automatically providing a memoizing logger to all bdai_ros2_wrappers.node.Node users makes for a much less painful migration and it spares us two migration cycles when and if we submit this upstream.

@mhidalgo-bdai Lets just make sure to announce this when this hits bdai


Add text_col to convert_to_id

This allows convert_to_id to be used anywhere regardless of table design. Initially done as a holdover for issue #292, but with discussion, may end up being a fine fix for it instead of redoing the DB.
Needed for the portal types, so quick review appreciated.

ready for review, should be quick.

duct tape on top of duct tape...
:+1: because is needed for portal types...

fixed comment, ready to go.

Anyone? This is urgent for the portal types.

:+1: but now I see it was just merged :smile:


1/N => 1/2

https://github.com/kreshuklab/teaching-dl-course-2019/blob/master/Webinars/exercise1/image_manipulation.ipynb?short_path=a1d32b1#L423
This should say 1/2 of the image dimensions and not 1/N.

why 2? it should work for any N given as a function argument here, 2 was just an example

ok!


Add unit tests for Liquid Prep App

Add unit tests for Liquid Prep App project

let me know how I can help.


Fix with OpenCascade 7.8.0.

This should resolves https://github.com/f3d-app/f3d/issues/1304 .

Ideally we should update the version we use in CI, testing the last release is more important. Let me know if you are ok to do that @thierry-FreeBSD

ATM most distributions keep OCCT 7.7.x, because they are waiting for upstream of dependent packages to fix them (so do we in FreeBSD, this is why I trying to send these PRs).
A list is available at Repology; it it possible to use one of these rolling releases in you CI?
Or is it possible to modify your CI to build your own release of OpenCascade from sources?

If only the module names have changed, should we just check the OCCT version and build the list of required modules based on the OCCT version?

All the changes are described in the upgrade guide.

ATM most distributions keep OCCT 7.7.x, because they are waiting for upstream of dependent packages to fix them (so do we in FreeBSD, this is why I trying to send these PRs).
A list is available at Repology; it it possible to use one of these rolling releases in you CI?
Or is it possible to modify your CI to build your own release of OpenCascade from sources?

Everything is possible. Dont worry about it, Ill take care of it.

Thanks for your contribution @thierry-FreeBSD !


add pylint

This PR adds pylint to our develop dependencies. It also includes a .pylintrc configuration file which suppresses a lot of useless warnings.

@zzhaozhe-profolio Would you review this change and approve it while Ismael is away?


Feature: permit running anything-sync-daemon as an unprivileged user

Plus a bunch of other fixes and features.  Note that this changeset includes major refactorings; I offer this PR with the expectation that its scope is too large to effectively review and therefore not reasonable to merge.  However, I've done my best to test and document the changes, and I think that they are genuinely useful, so if you've got the inclination to review this -- many thanks in advance!
Summary of changes:

Permit running asd as an unprivileged user.  This includes installing a systemd user unit, and loading asd.conf from a different location than /etc/asd.conf.  I've also added the script asd-mount-helper, based on psd-overlay-helper, to facilitate mounting and unmounting as a non-root user.
Add an anything-sync-daemon Nix package (nix/packages.nix).
Add a NixOS module (nix/nixos-module.nix) for configuring and running system and user instances of asd.service, asd-resync.service, and asd-resync.timer.
Add NixOS-based systems tests (nix/checks.nix) that verify the correct operation of system and user asd services.
Add Nix-based development tooling (nix/devshell.nix), including the shellcheck shell linter and alejandra Nix expression language formatter.
Update the GitHub actions configuration to run the NixOS-based systems tests (and replace the shellcheck workflow, as an equivalent job is included in the Nix checks).
Translate doc/asd.1 to Markdown (in USAGE.md) and generate the manpage from that Markdown.  Also expand the documentation to cover environment variables, and add some relevant links.
Factor out sync target iteration (repeated definitions of DIR, BACKUP, TMP, and so on).

I'm still ironing out the GitHub Actions workflow; currently it is quite slow (at least, the NixOS systems tests are).  But you can see a recent run here.
Thanks again for your consideration!

Hello @manorit2001 -- thank you very much for your feedback.

Is there any breaking change in this full PR w.r.t the current asd version and something that you would like to summarise based on that?

If you subscribe to Hyrum's Law, then I'm afraid there are breaking changes in just about every commit :wink: .  More seriously: a few of my changes are liable to break some setups, particularly the changes having to do with loading asd.conf and its snapshot.  However: setups broken by these changes are probably doing something (a) naughty (like messing with anything-sync-daemon's internal state) or (b) inadvisable (like launching long-running processes).  In case (a), users shouldn't do that, and in case (b) there's the workaround/escape hatch of specifying a longer timeout in ASDCONFTIMEOUT.

I see that asd is a very critical piece of software and people have actually suffered data losses in the past due to the refactor and the syncing process, if you know anything that you have done to drastically alter that process ( along with changing any names for the backup folders or anything), I would recommend giving a summary of it and maybe explaining the changes here ( or if possible pointing to those specific commits along with the explanation ) as that'd help us see the scope of the upgradation process from current asd to the new one.

I am working on a CHANGELOG.md that will cover all significant changes, highlighting especially any breaking changes.  I have not changed the names of backup folders, and any path-related changes are strictly opt-in, either by (a) running anything-sync-daemon as an unprivileged user (so should not affect existing installations, though I cannot say this for certain) or (b) setting ASDNOV1PATHS=1 or similar, which is not the default.

I see that most of your testing has been NixOS based, is there anything that you have done for arch or is there some difference in that? I haven't really ventured into NixOS so feel free to impart your knowledge

I hadn't done anything for Arch Linux, though, inspired by your mention of it, I've added a Vagrant configuration that spins up an Arch Linux machine and deploys anything-sync-daemon.  Found a few bugs in my other changes as a result, so thanks for that :slightly_smiling_face:.
Part of what I like about NixOS systems tests is how the testing framework is distributed with nixpkgs, so if you've got the Nix package manager and an internet connection, you're only a few steps from rockin' and rollin' with pkgs.testers.nixosTest.  No need to explicitly install additional tooling, or even configure much of anything outside the actual stuff of interest (in this case, settings in the config.services.asd "namespace"), as nixpkgs handles all the QEMU/KVM/networking/etc. stuff out-of-the-box.
However, I am happy to look into rigorous testing on Arch Linux, too.  Haven't found any analog of pkgs.testers.nixosTest for Arch, though perhaps Serverspec or InSpec or similar would do the trick.  WDYT?

I have added the changelog.

However, I am happy to look into rigorous testing on Arch Linux, too. Haven't found any analog of pkgs.testers.nixosTest for Arch, though perhaps Serverspec or InSpec or similar would do the trick. WDYT?

There is one test that I am particularly worried about first of all with this PR, it is basically the upgrade process, if possible could you check if we use the current asd version, stop asd ( this will happen as the part of upgradation process ) and then update your asd version to the new one with same configs as it was previously, I want to know that nothing breaks as a part of that.
W.r.t inspec or serverspec, I don't have any strong preference as I haven't worked on them, I would recommend you to choose whatever feels scalable to you for the project, would see the changes based on that.


Massively inflated bundle size with pages

Following the installation guide in this repo, my initial _worker.js output is 370KB.
If I then simply duplicate pages/index.ts to pages/index2.ts, and rebuild, I get over 750KB. And then if I do the same thing with index3.ts, I get over 1MiB. This is adding around 300KB for every single page.
Any real-world site loading some other dependencies, component libraries, etc. is going to rapidly exceed Workers limits, even with the increase to 5MiB. We've seen multiple people in Discord report hitting this limit with sites that had as little as 7 pages!
Here are some numbers for the generated _worker.js when using the experimental minify option, and when not:
using --experimental-minify
1 page site: 370KB output
2 page site: 750KB output
3 page site: 1MiB output
without --experimental-minify
1 page site: 333KB output
2 page site: 622KB output
3 page site: 911KB output

That's not a typo - the --experimental-minify option appears to make the output larger.

next-on-pages seems to copy large amounts of Next.js boilerplate for every page... I've noticed every page has it's own base-server

I just got hit by this error and not clear on what to do.

Same here. I have a really simple app, but the pages are 3-5MB. Why are the sizes so inflated?

Yup, same, we only have 2 pages, and over 1mb

Yup, same, we only have 2 pages, and over 1mb
Edit @dario-piotrowicz / @james-elicx , sorry for the ping, is there any solution to use Nextjs on Pages? Something is not adding up :/
Edit 2: This is the result from Nextjs build:

Route (pages)                              Size     First Load JS
┌ ℇ /                                      12.7 kB         190 kB
├   /_app                                  0 B             133 kB
├ ○ /404                                   194 B           134 kB
├ ℇ /api/hello                             0 B             133 kB
├ ℇ /me/profile                            43.5 kB         221 kB
├ ○ /sign-in/[[...index]]                  408 B           134 kB
└ ○ /sign-up/[[...index]]                  408 B           134 kB
+ First Load JS shared by all              134 kB
  ├ chunks/framework-4556c45dd113b893.js   45.2 kB
  ├ chunks/main-267015de6884ae13.js        30.1 kB
  ├ chunks/pages/_app-b0675639f806e8f3.js  57 kB
  ├ chunks/webpack-45c1d38871d29bef.js     1.03 kB
  └ css/0705bda694329cbb.css               306 B

ƒ Middleware                               333 kB

Yes. Use Vercel like they want you to do, or host it yourself on a VPS. It's extortion.

Hello @Richard87 @HenrijsS, are either of you able to share your applications so that we can see what is leading to such a large bundle size in them, and see if there is other deduping we can do for them?
It's possible that you may have rather beefy dependencies that are massively inflating the bundle size, but it's also possible that there could be another reason. Without seeing what's going on in your application, it's very hard for us to tell or help.
Please also make sure that you are using the latest version of @cloudflare/next-on-pages. For instance, @HenrijsS your reply was from before we made a release that included additional deduping, so you should try out the latest release and see how that affects things for you.

Hi @james-elicx ! I uploaded a copy of our app and wired it up to cloudflare and invited you to the repo (since it will be the copmany app I don't want to publish it :) )
Deploutlog of richard87/cloudflare-test

2023-07-21T16:53:38.626654603Z	Cloning repository...
2023-07-21T16:53:41.148151096Z	From https://github.com/Richard87/cloudflare-test
2023-07-21T16:53:41.148637753Z	 * branch            8cfa896640e5410df4592069239c2648ac5df701 -> FETCH_HEAD
2023-07-21T16:53:41.148791851Z
2023-07-21T16:53:41.233403805Z	HEAD is now at 8cfa896 init commit
2023-07-21T16:53:41.2338525Z
2023-07-21T16:53:41.366813974Z
2023-07-21T16:53:41.400962227Z	Success: Finished cloning repository files
2023-07-21T16:53:42.07414725Z	Detected the following tools from environment<EMAIL_ADDRESS><EMAIL_ADDRESS>2023-07-21T16:53:42.074180919Z	Installing project dependencies: npm clean-install --progress=false
2023-07-21T16:54:21.650151189Z
2023-07-21T16:54:21.650695839Z	added 1415 packages, and audited 1416 packages in 38s
2023-07-21T16:54:21.651118332Z
2023-07-21T16:54:21.651145139Z	274 packages are looking for funding
2023-07-21T16:54:21.651425951Z	  run `npm fund` for details
2023-07-21T16:54:21.656351241Z
2023-07-21T16:54:21.656487964Z	3 moderate severity vulnerabilities
2023-07-21T16:54:21.656765687Z
2023-07-21T16:54:21.656954245Z	To address all issues, run:
2023-07-21T16:54:21.65696677Z	  npm audit fix
2023-07-21T16:54:21.657164878Z
2023-07-21T16:54:21.657346901Z	Run `npm audit` for details.
2023-07-21T16:54:21.686642334Z	Executing user command: npx @cloudflare/next-on-pages@1
2023-07-21T16:54:24.700915475Z	npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>2023-07-21T16:54:40.037453285Z	npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
2023-07-21T16:54:40.361185222Z	npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
2023-07-21T16:54:40.84598049Z	npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
2023-07-21T16:54:42.164178772Z	npm WARN deprecated<EMAIL_ADDRESS>The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.
2023-07-21T16:54:48.00863165Z	⚡ @cloudflare/next-on-pages CLI v.1.3.1
2023-07-21T16:54:48.011437337Z	⚡ Detected Package Manager: npm
2023-07-21T16:54:48.012034955Z	⚡ Preparing project...
2023-07-21T16:54:48.013798207Z	⚡ Project is ready
2023-07-21T16:54:48.014069135Z	⚡ Building project...
2023-07-21T16:54:50.558416332Z	▲  npm
2023-07-21T16:54:50.559136467Z	▲  WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>2023-07-21T16:54:58.347673005Z	▲  npm WARN
2023-07-21T16:54:58.348152654Z	▲  deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
2023-07-21T16:54:59.405206307Z	▲  npm
2023-07-21T16:54:59.405848364Z	▲  WARN deprecated<EMAIL_ADDRESS>The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.
2023-07-21T16:55:03.422348021Z	▲  Vercel CLI 31.0.4
2023-07-21T16:55:03.59831724Z	▲  Warning: When using Next.js, it is recommended to place JavaScript Functions inside of the `pages/api` (provided by Next.js) directory instead of `api` (provided by Vercel). Other languages (Python, Go, etc) should still go in the `api` directory. Learn More: https://nextjs.org/docs/api-routes/introduction
2023-07-21T16:55:04.321952904Z	▲  Installing dependencies...
2023-07-21T16:55:07.964030658Z	▲  up to date in 3s
2023-07-21T16:55:07.964615676Z	▲  274 packages are looking for funding
2023-07-21T16:55:07.964951526Z	▲  run `npm fund` for details
2023-07-21T16:55:07.981107283Z	▲  Detected Next.js version: 13.4.2
2023-07-21T16:55:07.991945909Z	▲  Detected `package-lock.json` generated by npm 7+...
2023-07-21T16:55:07.992244156Z	▲  Running "npm run build"
2023-07-21T16:55:08.94719753Z	▲  ><EMAIL_ADDRESS>build
2023-07-21T16:55:08.947769433Z	▲  > next build
2023-07-21T16:55:09.403852784Z	▲  - info Loaded env from /opt/buildhome/repo/.env
2023-07-21T16:55:09.596616635Z	▲  Attention: Next.js now collects completely anonymous telemetry regarding usage.
2023-07-21T16:55:09.596846326Z	▲  This information is used to shape Next.js' roadmap and prioritize features.
2023-07-21T16:55:09.597186038Z	▲  You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
2023-07-21T16:55:09.597339409Z	▲  https://nextjs.org/telemetry
2023-07-21T16:55:09.731706951Z	▲  - info Linting and checking validity of types...
2023-07-21T16:55:16.827989619Z	▲  - info Creating an optimized production build...
2023-07-21T16:55:17.038772342Z	▲  - warn You are using an experimental edge runtime, the API might change.
2023-07-21T16:55:26.127426737Z	▲  Warning: For production Image Optimization with Next.js, the optional 'sharp' package is strongly recommended. Run 'yarn add sharp', and Next.js will use it automatically for Image Optimization.
2023-07-21T16:55:26.128354082Z	▲  Read more: https://nextjs.org/docs/messages/sharp-missing-in-production
2023-07-21T16:55:44.375913579Z	▲  <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (659kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
2023-07-21T16:55:55.027224993Z	▲  - warn Compiled with warnings
2023-07-21T16:55:55.028648203Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.028982607Z	▲  A Node.js API is used (MessageEvent at line: 1) which is not supported in the Edge Runtime.
2023-07-21T16:55:55.029601971Z	▲  Learn more: https://nextjs.org/docs/api-reference/edge-runtime
2023-07-21T16:55:55.029819824Z	▲
2023-07-21T16:55:55.03006954Z	▲  Import trace for requested module:
2023-07-21T16:55:55.030317557Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.030946778Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.031254602Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.031402673Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.032102485Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.032531438Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.0325396Z	▲
2023-07-21T16:55:55.032544004Z	▲  ./node_modules/next/dist/server/web/spec-extension/image-response.js
2023-07-21T16:55:55.032824463Z	▲  A Node.js API is used (process.turbopack at line: 14) which is not supported in the Edge Runtime.
2023-07-21T16:55:55.032893628Z	▲  Learn more: https://nextjs.org/docs/api-reference/edge-runtime
2023-07-21T16:55:55.03309037Z	▲
2023-07-21T16:55:55.033224775Z	▲  Import trace for requested module:
2023-07-21T16:55:55.033363912Z	▲  ./node_modules/next/dist/server/web/spec-extension/image-response.js
2023-07-21T16:55:55.033489192Z	▲  ./node_modules/next/server.js
2023-07-21T16:55:55.033634305Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.03378118Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.033917649Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.034097522Z	▲
2023-07-21T16:55:55.034239017Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.034379525Z	▲  A Node.js API is used (setImmediate at line: 11) which is not supported in the Edge Runtime.
2023-07-21T16:55:55.034524747Z	▲  Learn more: https://nextjs.org/docs/api-reference/edge-runtime
2023-07-21T16:55:55.034661151Z	▲
2023-07-21T16:55:55.034808552Z	▲  Import trace for requested module:
2023-07-21T16:55:55.034946445Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.035099482Z	▲  ./node_modules/scheduler/index.js
2023-07-21T16:55:55.035256229Z	▲  ./node_modules/react-dom/cjs/react-dom.production.min.js
2023-07-21T16:55:55.035391735Z	▲  ./node_modules/react-dom/index.js
2023-07-21T16:55:55.035527149Z	▲  ./node_modules/next/dist/esm/client/script.js
2023-07-21T16:55:55.03572141Z	▲  ./node_modules/next/dist/esm/shared/lib/router/router.js
2023-07-21T16:55:55.036527298Z	▲  ./node_modules/next/dist/esm/client/router.js
2023-07-21T16:55:55.036858642Z	▲  ./node_modules/next/router.js
2023-07-21T16:55:55.037438122Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.037609513Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.037798119Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.037933225Z	▲
2023-07-21T16:55:55.038132225Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.038701363Z	▲  A Node.js API is used (setImmediate at line: 11) which is not supported in the Edge Runtime.
2023-07-21T16:55:55.03889848Z	▲  Learn more: https://nextjs.org/docs/api-reference/edge-runtime
2023-07-21T16:55:55.039081442Z	▲
2023-07-21T16:55:55.039272187Z	▲  Import trace for requested module:
2023-07-21T16:55:55.039849981Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.04004834Z	▲  ./node_modules/scheduler/index.js
2023-07-21T16:55:55.040184575Z	▲  ./node_modules/react-dom/cjs/react-dom.production.min.js
2023-07-21T16:55:55.040482555Z	▲  ./node_modules/react-dom/index.js
2023-07-21T16:55:55.040493733Z	▲  ./node_modules/next/dist/esm/client/script.js
2023-07-21T16:55:55.040667313Z	▲  ./node_modules/next/dist/esm/shared/lib/router/router.js
2023-07-21T16:55:55.040733365Z	▲  ./node_modules/next/dist/esm/client/router.js
2023-07-21T16:55:55.040973188Z	▲  ./node_modules/next/router.js
2023-07-21T16:55:55.041575177Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.041848658Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.042306939Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.042499238Z	▲
2023-07-21T16:55:55.042669356Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.042865129Z	▲  A Node.js API is used (MessageChannel at line: 14) which is not supported in the Edge Runtime.
2023-07-21T16:55:55.043590451Z	▲  Learn more: https://nextjs.org/docs/api-reference/edge-runtime
2023-07-21T16:55:55.043726836Z	▲
2023-07-21T16:55:55.043905353Z	▲  Import trace for requested module:
2023-07-21T16:55:55.044207013Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.044590307Z	▲  ./node_modules/scheduler/index.js
2023-07-21T16:55:55.044599726Z	▲  ./node_modules/react-dom/cjs/react-dom.production.min.js
2023-07-21T16:55:55.044674866Z	▲  ./node_modules/react-dom/index.js
2023-07-21T16:55:55.044833954Z	▲  ./node_modules/next/dist/esm/client/script.js
2023-07-21T16:55:55.045047291Z	▲  ./node_modules/next/dist/esm/shared/lib/router/router.js
2023-07-21T16:55:55.045360167Z	▲  ./node_modules/next/dist/esm/client/router.js
2023-07-21T16:55:55.045390595Z	▲  ./node_modules/next/router.js
2023-07-21T16:55:55.045486268Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.045709348Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.046403266Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.046701912Z	▲
2023-07-21T16:55:55.046861185Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.04731886Z	▲  A Node.js API is used (MessageChannel at line: 14) which is not supported in the Edge Runtime.
2023-07-21T16:55:55.047525585Z	▲  Learn more: https://nextjs.org/docs/api-reference/edge-runtime
2023-07-21T16:55:55.047664445Z	▲
2023-07-21T16:55:55.047805643Z	▲  Import trace for requested module:
2023-07-21T16:55:55.047955333Z	▲  ./node_modules/scheduler/cjs/scheduler.production.min.js
2023-07-21T16:55:55.048141253Z	▲  ./node_modules/scheduler/index.js
2023-07-21T16:55:55.048576398Z	▲  ./node_modules/react-dom/cjs/react-dom.production.min.js
2023-07-21T16:55:55.048715468Z	▲  ./node_modules/react-dom/index.js
2023-07-21T16:55:55.048939179Z	▲  ./node_modules/next/dist/esm/client/script.js
2023-07-21T16:55:55.048986826Z	▲  ./node_modules/next/dist/esm/shared/lib/router/router.js
2023-07-21T16:55:55.049256358Z	▲  ./node_modules/next/dist/esm/client/router.js
2023-07-21T16:55:55.049765909Z	▲  ./node_modules/next/router.js
2023-07-21T16:55:55.049782233Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.049788278Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.049832963Z	▲<EMAIL_ADDRESS>2023-07-21T16:55:55.049858017Z	▲  - info Collecting page data...
2023-07-21T16:56:15.954379335Z	▲  - info Generating static pages (0/2)
2023-07-21T16:56:16.095091209Z	▲  - info Generating static pages (2/2)
2023-07-21T16:56:16.380771514Z	▲  - info Finalizing page optimization...
2023-07-21T16:56:16.386591788Z	▲
2023-07-21T16:56:16.561550516Z	▲  Route (pages)                              Size     First Load JS
2023-07-21T16:56:16.561697984Z	▲  ┌ ℇ /                                      12.7 kB         190 kB
2023-07-21T16:56:16.562103216Z	▲  ├   /_app                                  0 B             133 kB
2023-07-21T16:56:16.562118249Z	▲  ├ ○ /404                                   194 B           134 kB
2023-07-21T16:56:16.562323836Z	▲  ├ ℇ /api/hello                             0 B             133 kB
2023-07-21T16:56:16.562392774Z	▲  └ ℇ /me/profile                            43.5 kB         221 kB
2023-07-21T16:56:16.562498916Z	▲  + First Load JS shared by all              134 kB
2023-07-21T16:56:16.562600477Z	▲  ├ chunks/framework-4556c45dd113b893.js   45.2 kB
2023-07-21T16:56:16.562818685Z	▲  ├ chunks/main-267015de6884ae13.js        30.1 kB
2023-07-21T16:56:16.563006148Z	▲  ├ chunks/pages/_app-a7b791b1aca29c07.js  57 kB
2023-07-21T16:56:16.563114153Z	▲  ├ chunks/webpack-45c1d38871d29bef.js     1.03 kB
2023-07-21T16:56:16.563399324Z	▲  └ css/0705bda694329cbb.css               306 B
2023-07-21T16:56:16.56341111Z	▲
2023-07-21T16:56:16.563494322Z	▲  ƒ Middleware                               334 kB
2023-07-21T16:56:16.563612314Z	▲  ℇ  (Streaming)  server-side renders with streaming (uses React 18 SSR streaming or Server Components)
2023-07-21T16:56:16.563762039Z	▲  ○  (Static)     automatically rendered as static HTML (uses no initial props)
2023-07-21T16:56:18.048074806Z	▲  Collected static files (public/, static/, .next/static): 9.888ms
2023-07-21T16:56:18.390922957Z	▲  Using TypeScript 5.0.4 (local user-provided)
2023-07-21T16:56:25.180066807Z	▲  Build Completed in .vercel/output [1m]
2023-07-21T16:56:25.360110868Z	⚡ Completed `npx vercel build`.
2023-07-21T16:56:30.016605213Z
2023-07-21T16:56:30.017339188Z	⚡ Build Summary (@cloudflare/next-on-pages v1.3.1)
2023-07-21T16:56:30.017779638Z	⚡
2023-07-21T16:56:30.017799388Z	⚡ Middleware Functions (1)
2023-07-21T16:56:30.018047331Z	⚡   - middleware
2023-07-21T16:56:30.018217255Z	⚡
2023-07-21T16:56:30.01847914Z	⚡ Edge Function Routes (3)
2023-07-21T16:56:30.018561414Z	⚡   ┌ /
2023-07-21T16:56:30.018621603Z	⚡   ├ /api/hello
2023-07-21T16:56:30.018839723Z	⚡   └ /me/profile
2023-07-21T16:56:30.019098264Z	⚡
2023-07-21T16:56:30.019260691Z	⚡ Wasm Files (2)
2023-07-21T16:56:30.019451251Z	⚡   ┌ wasm_a7e702bc5ba9227243abda7977c8096f59478d3f
2023-07-21T16:56:30.019597496Z	⚡   └ wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020
2023-07-21T16:56:30.01976833Z	⚡
2023-07-21T16:56:30.019931382Z	⚡ Other Static Assets (30)
2023-07-21T16:56:30.020170535Z	⚡   ┌ /404.html
2023-07-21T16:56:30.020277888Z	⚡   ├ /500.html
2023-07-21T16:56:30.020529444Z	⚡   ├ /assets/nb-NO.ts
2023-07-21T16:56:30.020699166Z	⚡   ├ /favicon.ico
2023-07-21T16:56:30.021071008Z	⚡   └ ... 26 more
2023-07-21T16:56:30.021345122Z
2023-07-21T16:56:30.021561588Z	⚡ Build log saved to '.vercel/output/static/_worker.js/nop-build-log.json'
2023-07-21T16:56:30.058049382Z	⚡ Generated '.vercel/output/static/_worker.js/index.js'.
2023-07-21T16:56:30.142176647Z	Finished
2023-07-21T16:56:30.142831777Z	Found _worker.js in output directory. Uploading.
2023-07-21T16:56:31.212235678Z	Uploading additional modules:
2023-07-21T16:56:31.212983619Z	- __next-on-pages-dist__/chunks/1026.js (esm)
2023-07-21T16:56:31.213341534Z	- __next-on-pages-dist__/chunks/1032.js (esm)
2023-07-21T16:56:31.213714804Z	- __next-on-pages-dist__/chunks/1092.js (esm)
2023-07-21T16:56:31.21448196Z	- __next-on-pages-dist__/chunks/1154.js (esm)
2023-07-21T16:56:31.2145012Z	- __next-on-pages-dist__/chunks/1163.js (esm)
2023-07-21T16:56:31.214510287Z	- __next-on-pages-dist__/chunks/1164.js (esm)
2023-07-21T16:56:31.214514603Z	- __next-on-pages-dist__/chunks/1190.js (esm)
2023-07-21T16:56:31.214518576Z	- __next-on-pages-dist__/chunks/1216.js (esm)
2023-07-21T16:56:31.214526096Z	- __next-on-pages-dist__/chunks/1238.js (esm)
2023-07-21T16:56:31.21493019Z	- __next-on-pages-dist__/chunks/1265.js (esm)
2023-07-21T16:56:31.214940559Z	- __next-on-pages-dist__/chunks/1268.js (esm)
2023-07-21T16:56:31.214944896Z	- __next-on-pages-dist__/chunks/1289.js (esm)
2023-07-21T16:56:31.215085209Z	- __next-on-pages-dist__/chunks/136.js (esm)
2023-07-21T16:56:31.21516919Z	- __next-on-pages-dist__/chunks/1387.js (esm)
2023-07-21T16:56:31.21705595Z	- __next-on-pages-dist__/chunks/1490.js (esm)
2023-07-21T16:56:31.217070471Z	- __next-on-pages-dist__/chunks/1496.js (esm)
2023-07-21T16:56:31.217074716Z	- __next-on-pages-dist__/chunks/1549.js (esm)
2023-07-21T16:56:31.21707871Z	- __next-on-pages-dist__/chunks/1574.js (esm)
2023-07-21T16:56:31.217082509Z	- __next-on-pages-dist__/chunks/1587.js (esm)
2023-07-21T16:56:31.217086273Z	- __next-on-pages-dist__/chunks/1588.js (esm)
2023-07-21T16:56:31.217090223Z	- __next-on-pages-dist__/chunks/1616.js (esm)
2023-07-21T16:56:31.217094158Z	- __next-on-pages-dist__/chunks/1627.js (esm)
2023-07-21T16:56:31.217097886Z	- __next-on-pages-dist__/chunks/1629.js (esm)
2023-07-21T16:56:31.217101653Z	- __next-on-pages-dist__/chunks/1700.js (esm)
2023-07-21T16:56:31.217128796Z	- __next-on-pages-dist__/chunks/1705.js (esm)
2023-07-21T16:56:31.217133678Z	- __next-on-pages-dist__/chunks/1768.js (esm)
2023-07-21T16:56:31.217137856Z	- __next-on-pages-dist__/chunks/1796.js (esm)
2023-07-21T16:56:31.217141847Z	- __next-on-pages-dist__/chunks/1864.js (esm)
2023-07-21T16:56:31.217148729Z	- __next-on-pages-dist__/chunks/1890.js (esm)
2023-07-21T16:56:31.217318589Z	- __next-on-pages-dist__/chunks/1929.js (esm)
2023-07-21T16:56:31.217635323Z	- __next-on-pages-dist__/chunks/1974.js (esm)
2023-07-21T16:56:31.217654623Z	- __next-on-pages-dist__/chunks/1981.js (esm)
2023-07-21T16:56:31.217845973Z	- __next-on-pages-dist__/chunks/1987.js (esm)
2023-07-21T16:56:31.217856721Z	- __next-on-pages-dist__/chunks/211.js (esm)
2023-07-21T16:56:31.218036603Z	- __next-on-pages-dist__/chunks/2131.js (esm)
2023-07-21T16:56:31.21821671Z	- __next-on-pages-dist__/chunks/2159.js (esm)
2023-07-21T16:56:31.218226723Z	- __next-on-pages-dist__/chunks/2161.js (esm)
2023-07-21T16:56:31.218417776Z	- __next-on-pages-dist__/chunks/2190.js (esm)
2023-07-21T16:56:31.218593016Z	- __next-on-pages-dist__/chunks/220.js (esm)
2023-07-21T16:56:31.218620568Z	- __next-on-pages-dist__/chunks/2233.js (esm)
2023-07-21T16:56:31.218819834Z	- __next-on-pages-dist__/chunks/2350.js (esm)
2023-07-21T16:56:31.218909885Z	- __next-on-pages-dist__/chunks/2374.js (esm)
2023-07-21T16:56:31.21898125Z	- __next-on-pages-dist__/chunks/2379.js (esm)
2023-07-21T16:56:31.219195318Z	- __next-on-pages-dist__/chunks/2408.js (esm)
2023-07-21T16:56:31.219275803Z	- __next-on-pages-dist__/chunks/247.js (esm)
2023-07-21T16:56:31.219551502Z	- __next-on-pages-dist__/chunks/2542.js (esm)
2023-07-21T16:56:31.219563708Z	- __next-on-pages-dist__/chunks/255.js (esm)
2023-07-21T16:56:31.222147875Z	- __next-on-pages-dist__/chunks/2595.js (esm)
2023-07-21T16:56:31.222170066Z	- __next-on-pages-dist__/chunks/2627.js (esm)
2023-07-21T16:56:31.222174997Z	- __next-on-pages-dist__/chunks/2643.js (esm)
2023-07-21T16:56:31.222178819Z	- __next-on-pages-dist__/chunks/2734.js (esm)
2023-07-21T16:56:31.222182663Z	- __next-on-pages-dist__/chunks/2741.js (esm)
2023-07-21T16:56:31.222186445Z	- __next-on-pages-dist__/chunks/2812.js (esm)
2023-07-21T16:56:31.222194233Z	- __next-on-pages-dist__/chunks/2917.js (esm)
2023-07-21T16:56:31.22219851Z	- __next-on-pages-dist__/chunks/2956.js (esm)
2023-07-21T16:56:31.222202653Z	- __next-on-pages-dist__/chunks/2972.js (esm)
2023-07-21T16:56:31.22220652Z	- __next-on-pages-dist__/chunks/2998.js (esm)
2023-07-21T16:56:31.222210368Z	- __next-on-pages-dist__/chunks/3002.js (esm)
2023-07-21T16:56:31.222214206Z	- __next-on-pages-dist__/chunks/3013.js (esm)
2023-07-21T16:56:31.22221822Z	- __next-on-pages-dist__/chunks/3023.js (esm)
2023-07-21T16:56:31.222222112Z	- __next-on-pages-dist__/chunks/310.js (esm)
2023-07-21T16:56:31.222225915Z	- __next-on-pages-dist__/chunks/3284.js (esm)
2023-07-21T16:56:31.222229813Z	- __next-on-pages-dist__/chunks/3294.js (esm)
2023-07-21T16:56:31.222424155Z	- __next-on-pages-dist__/chunks/3321.js (esm)
2023-07-21T16:56:31.222431699Z	- __next-on-pages-dist__/chunks/3366.js (esm)
2023-07-21T16:56:31.22267688Z	- __next-on-pages-dist__/chunks/3370.js (esm)
2023-07-21T16:56:31.222837836Z	- __next-on-pages-dist__/chunks/3399.js (esm)
2023-07-21T16:56:31.222995501Z	- __next-on-pages-dist__/chunks/3433.js (esm)
2023-07-21T16:56:31.223162537Z	- __next-on-pages-dist__/chunks/3453.js (esm)
2023-07-21T16:56:31.223316781Z	- __next-on-pages-dist__/chunks/3475.js (esm)
2023-07-21T16:56:31.223462189Z	- __next-on-pages-dist__/chunks/351.js (esm)
2023-07-21T16:56:31.223626529Z	- __next-on-pages-dist__/chunks/3610.js (esm)
2023-07-21T16:56:31.223794445Z	- __next-on-pages-dist__/chunks/3616.js (esm)
2023-07-21T16:56:31.223948069Z	- __next-on-pages-dist__/chunks/3633.js (esm)
2023-07-21T16:56:31.224119339Z	- __next-on-pages-dist__/chunks/3769.js (esm)
2023-07-21T16:56:31.224277136Z	- __next-on-pages-dist__/chunks/377.js (esm)
2023-07-21T16:56:31.224423496Z	- __next-on-pages-dist__/chunks/3825.js (esm)
2023-07-21T16:56:31.224488276Z	- __next-on-pages-dist__/chunks/3826.js (esm)
2023-07-21T16:56:31.22490452Z	- __next-on-pages-dist__/chunks/3840.js (esm)
2023-07-21T16:56:31.224932311Z	- __next-on-pages-dist__/chunks/3841.js (esm)
2023-07-21T16:56:31.225161716Z	- __next-on-pages-dist__/chunks/3853.js (esm)
2023-07-21T16:56:31.225329799Z	- __next-on-pages-dist__/chunks/3935.js (esm)
2023-07-21T16:56:31.225424637Z	- __next-on-pages-dist__/chunks/3989.js (esm)
2023-07-21T16:56:31.225600219Z	- __next-on-pages-dist__/chunks/3997.js (esm)
2023-07-21T16:56:31.225664253Z	- __next-on-pages-dist__/chunks/4127.js (esm)
2023-07-21T16:56:31.225836631Z	- __next-on-pages-dist__/chunks/4137.js (esm)
2023-07-21T16:56:31.226002355Z	- __next-on-pages-dist__/chunks/4168.js (esm)
2023-07-21T16:56:31.226250326Z	- __next-on-pages-dist__/chunks/4204.js (esm)
2023-07-21T16:56:31.226363358Z	- __next-on-pages-dist__/chunks/4329.js (esm)
2023-07-21T16:56:31.226474988Z	- __next-on-pages-dist__/chunks/434.js (esm)
2023-07-21T16:56:31.226612702Z	- __next-on-pages-dist__/chunks/4371.js (esm)
2023-07-21T16:56:31.226758056Z	- __next-on-pages-dist__/chunks/4401.js (esm)
2023-07-21T16:56:31.226894826Z	- __next-on-pages-dist__/chunks/4404.js (esm)
2023-07-21T16:56:31.227044983Z	- __next-on-pages-dist__/chunks/4423.js (esm)
2023-07-21T16:56:31.227170498Z	- __next-on-pages-dist__/chunks/4437.js (esm)
2023-07-21T16:56:31.227320611Z	- __next-on-pages-dist__/chunks/4448.js (esm)
2023-07-21T16:56:31.227463573Z	- __next-on-pages-dist__/chunks/4474.js (esm)
2023-07-21T16:56:31.227590978Z	- __next-on-pages-dist__/chunks/4495.js (esm)
2023-07-21T16:56:31.227741979Z	- __next-on-pages-dist__/chunks/4529.js (esm)
2023-07-21T16:56:31.227873663Z	- __next-on-pages-dist__/chunks/4533.js (esm)
2023-07-21T16:56:31.227992042Z	- __next-on-pages-dist__/chunks/4536.js (esm)
2023-07-21T16:56:31.228145345Z	- __next-on-pages-dist__/chunks/4582.js (esm)
2023-07-21T16:56:31.228285468Z	- __next-on-pages-dist__/chunks/4639.js (esm)
2023-07-21T16:56:31.22840963Z	- __next-on-pages-dist__/chunks/4708.js (esm)
2023-07-21T16:56:31.228546928Z	- __next-on-pages-dist__/chunks/4748.js (esm)
2023-07-21T16:56:31.228688352Z	- __next-on-pages-dist__/chunks/476.js (esm)
2023-07-21T16:56:31.228834218Z	- __next-on-pages-dist__/chunks/4780.js (esm)
2023-07-21T16:56:31.228961381Z	- __next-on-pages-dist__/chunks/4793.js (esm)
2023-07-21T16:56:31.229144036Z	- __next-on-pages-dist__/chunks/4808.js (esm)
2023-07-21T16:56:31.229250229Z	- __next-on-pages-dist__/chunks/4842.js (esm)
2023-07-21T16:56:31.229395618Z	- __next-on-pages-dist__/chunks/4844.js (esm)
2023-07-21T16:56:31.229517719Z	- __next-on-pages-dist__/chunks/4855.js (esm)
2023-07-21T16:56:31.229609445Z	- __next-on-pages-dist__/chunks/4867.js (esm)
2023-07-21T16:56:31.229847321Z	- __next-on-pages-dist__/chunks/4920.js (esm)
2023-07-21T16:56:31.230183337Z	- __next-on-pages-dist__/chunks/4928.js (esm)
2023-07-21T16:56:31.230195262Z	- __next-on-pages-dist__/chunks/4929.js (esm)
2023-07-21T16:56:31.230199635Z	- __next-on-pages-dist__/chunks/4945.js (esm)
2023-07-21T16:56:31.230340993Z	- __next-on-pages-dist__/chunks/4949.js (esm)
2023-07-21T16:56:31.230414996Z	- __next-on-pages-dist__/chunks/4970.js (esm)
2023-07-21T16:56:31.230591508Z	- __next-on-pages-dist__/chunks/4993.js (esm)
2023-07-21T16:56:31.23067408Z	- __next-on-pages-dist__/chunks/5004.js (esm)
2023-07-21T16:56:31.230902905Z	- __next-on-pages-dist__/chunks/5042.js (esm)
2023-07-21T16:56:31.231196843Z	- __next-on-pages-dist__/chunks/5054.js (esm)
2023-07-21T16:56:31.231209086Z	- __next-on-pages-dist__/chunks/5068.js (esm)
2023-07-21T16:56:31.231297063Z	- __next-on-pages-dist__/chunks/5108.js (esm)
2023-07-21T16:56:31.231363261Z	- __next-on-pages-dist__/chunks/5130.js (esm)
2023-07-21T16:56:31.23154729Z	- __next-on-pages-dist__/chunks/5145.js (esm)
2023-07-21T16:56:31.231630893Z	- __next-on-pages-dist__/chunks/5149.js (esm)
2023-07-21T16:56:31.231865751Z	- __next-on-pages-dist__/chunks/5150.js (esm)
2023-07-21T16:56:31.232138433Z	- __next-on-pages-dist__/chunks/5190.js (esm)
2023-07-21T16:56:31.232149558Z	- __next-on-pages-dist__/chunks/5251.js (esm)
2023-07-21T16:56:31.232224586Z	- __next-on-pages-dist__/chunks/53.js (esm)
2023-07-21T16:56:31.232312722Z	- __next-on-pages-dist__/chunks/5373.js (esm)
2023-07-21T16:56:31.232551359Z	- __next-on-pages-dist__/chunks/539.js (esm)
2023-07-21T16:56:31.232786663Z	- __next-on-pages-dist__/chunks/5408.js (esm)
2023-07-21T16:56:31.232797744Z	- __next-on-pages-dist__/chunks/5430.js (esm)
2023-07-21T16:56:31.232870233Z	- __next-on-pages-dist__/chunks/5442.js (esm)
2023-07-21T16:56:31.233007343Z	- __next-on-pages-dist__/chunks/5462.js (esm)
2023-07-21T16:56:31.2331506Z	- __next-on-pages-dist__/chunks/5467.js (esm)
2023-07-21T16:56:31.233226278Z	- __next-on-pages-dist__/chunks/5498.js (esm)
2023-07-21T16:56:31.233613065Z	- __next-on-pages-dist__/chunks/5505.js (esm)
2023-07-21T16:56:31.233624431Z	- __next-on-pages-dist__/chunks/558.js (esm)
2023-07-21T16:56:31.233697076Z	- __next-on-pages-dist__/chunks/5590.js (esm)
2023-07-21T16:56:31.233778186Z	- __next-on-pages-dist__/chunks/5633.js (esm)
2023-07-21T16:56:31.233943306Z	- __next-on-pages-dist__/chunks/5641.js (esm)
2023-07-21T16:56:31.234038679Z	- __next-on-pages-dist__/chunks/5679.js (esm)
2023-07-21T16:56:31.234196707Z	- __next-on-pages-dist__/chunks/5704.js (esm)
2023-07-21T16:56:31.234449993Z	- __next-on-pages-dist__/chunks/5744.js (esm)
2023-07-21T16:56:31.234461599Z	- __next-on-pages-dist__/chunks/5761.js (esm)
2023-07-21T16:56:31.234542934Z	- __next-on-pages-dist__/chunks/585.js (esm)
2023-07-21T16:56:31.234690641Z	- __next-on-pages-dist__/chunks/5861.js (esm)
2023-07-21T16:56:31.234838758Z	- __next-on-pages-dist__/chunks/5881.js (esm)
2023-07-21T16:56:31.2349338Z	- __next-on-pages-dist__/chunks/5893.js (esm)
2023-07-21T16:56:31.235085076Z	- __next-on-pages-dist__/chunks/5945.js (esm)
2023-07-21T16:56:31.235372895Z	- __next-on-pages-dist__/chunks/6010.js (esm)
2023-07-21T16:56:31.235443016Z	- __next-on-pages-dist__/chunks/6021.js (esm)
2023-07-21T16:56:31.235532528Z	- __next-on-pages-dist__/chunks/606.js (esm)
2023-07-21T16:56:31.235682237Z	- __next-on-pages-dist__/chunks/619.js (esm)
2023-07-21T16:56:31.235772337Z	- __next-on-pages-dist__/chunks/623.js (esm)
2023-07-21T16:56:31.235937693Z	- __next-on-pages-dist__/chunks/627.js (esm)
2023-07-21T16:56:31.236197877Z	- __next-on-pages-dist__/chunks/6272.js (esm)
2023-07-21T16:56:31.236210037Z	- __next-on-pages-dist__/chunks/628.js (esm)
2023-07-21T16:56:31.236353349Z	- __next-on-pages-dist__/chunks/629.js (esm)
2023-07-21T16:56:31.236455124Z	- __next-on-pages-dist__/chunks/6346.js (esm)
2023-07-21T16:56:31.236615624Z	- __next-on-pages-dist__/chunks/6411.js (esm)
2023-07-21T16:56:31.236704663Z	- __next-on-pages-dist__/chunks/6447.js (esm)
2023-07-21T16:56:31.236866369Z	- __next-on-pages-dist__/chunks/6474.js (esm)
2023-07-21T16:56:31.237142531Z	- __next-on-pages-dist__/chunks/65.js (esm)
2023-07-21T16:56:31.237154216Z	- __next-on-pages-dist__/chunks/6500.js (esm)
2023-07-21T16:56:31.237302574Z	- __next-on-pages-dist__/chunks/6508.js (esm)
2023-07-21T16:56:31.237386429Z	- __next-on-pages-dist__/chunks/6513.js (esm)
2023-07-21T16:56:31.237553661Z	- __next-on-pages-dist__/chunks/6523.js (esm)
2023-07-21T16:56:31.237643739Z	- __next-on-pages-dist__/chunks/6526.js (esm)
2023-07-21T16:56:31.237875286Z	- __next-on-pages-dist__/chunks/655.js (esm)
2023-07-21T16:56:31.238155324Z	- __next-on-pages-dist__/chunks/656.js (esm)
2023-07-21T16:56:31.238167039Z	- __next-on-pages-dist__/chunks/6568.js (esm)
2023-07-21T16:56:31.238240398Z	- __next-on-pages-dist__/chunks/6600.js (esm)
2023-07-21T16:56:31.238316424Z	- __next-on-pages-dist__/chunks/6607.js (esm)
2023-07-21T16:56:31.238482184Z	- __next-on-pages-dist__/chunks/668.js (esm)
2023-07-21T16:56:31.238575548Z	- __next-on-pages-dist__/chunks/6682.js (esm)
2023-07-21T16:56:31.238728976Z	- __next-on-pages-dist__/chunks/6686.js (esm)
2023-07-21T16:56:31.238981846Z	- __next-on-pages-dist__/chunks/67.js (esm)
2023-07-21T16:56:31.238992844Z	- __next-on-pages-dist__/chunks/6735.js (esm)
2023-07-21T16:56:31.239109423Z	- __next-on-pages-dist__/chunks/6747.js (esm)
2023-07-21T16:56:31.239209539Z	- __next-on-pages-dist__/chunks/6764.js (esm)
2023-07-21T16:56:31.239459039Z	- __next-on-pages-dist__/chunks/6771.js (esm)
2023-07-21T16:56:31.239717224Z	- __next-on-pages-dist__/chunks/6774.js (esm)
2023-07-21T16:56:31.239728866Z	- __next-on-pages-dist__/chunks/6861.js (esm)
2023-07-21T16:56:31.239806686Z	- __next-on-pages-dist__/chunks/6886.js (esm)
2023-07-21T16:56:31.239965949Z	- __next-on-pages-dist__/chunks/6900.js (esm)
2023-07-21T16:56:31.240125679Z	- __next-on-pages-dist__/chunks/6934.js (esm)
2023-07-21T16:56:31.240274676Z	- __next-on-pages-dist__/chunks/6938.js (esm)
2023-07-21T16:56:31.240537191Z	- __next-on-pages-dist__/chunks/6943.js (esm)
2023-07-21T16:56:31.240548132Z	- __next-on-pages-dist__/chunks/6957.js (esm)
2023-07-21T16:56:31.240634982Z	- __next-on-pages-dist__/chunks/7039.js (esm)
2023-07-21T16:56:31.240869473Z	- __next-on-pages-dist__/chunks/7041.js (esm)
2023-07-21T16:56:31.241173803Z	- __next-on-pages-dist__/chunks/7076.js (esm)
2023-07-21T16:56:31.24131579Z	- __next-on-pages-dist__/chunks/7078.js (esm)
2023-07-21T16:56:31.241473947Z	- __next-on-pages-dist__/chunks/7097.js (esm)
2023-07-21T16:56:31.241587249Z	- __next-on-pages-dist__/chunks/7118.js (esm)
2023-07-21T16:56:31.241729737Z	- __next-on-pages-dist__/chunks/7167.js (esm)
2023-07-21T16:56:31.241874342Z	- __next-on-pages-dist__/chunks/7203.js (esm)
2023-07-21T16:56:31.242115782Z	- __next-on-pages-dist__/chunks/7218.js (esm)
2023-07-21T16:56:31.242244353Z	- __next-on-pages-dist__/chunks/7239.js (esm)
2023-07-21T16:56:31.242386376Z	- __next-on-pages-dist__/chunks/7294.js (esm)
2023-07-21T16:56:31.242571292Z	- __next-on-pages-dist__/chunks/7297.js (esm)
2023-07-21T16:56:31.242727777Z	- __next-on-pages-dist__/chunks/733.js (esm)
2023-07-21T16:56:31.242877464Z	- __next-on-pages-dist__/chunks/7334.js (esm)
2023-07-21T16:56:31.242971225Z	- __next-on-pages-dist__/chunks/738.js (esm)
2023-07-21T16:56:31.243185158Z	- __next-on-pages-dist__/chunks/7385.js (esm)
2023-07-21T16:56:31.243329955Z	- __next-on-pages-dist__/chunks/7462.js (esm)
2023-07-21T16:56:31.243478878Z	- __next-on-pages-dist__/chunks/7493.js (esm)
2023-07-21T16:56:31.243609594Z	- __next-on-pages-dist__/chunks/7532.js (esm)
2023-07-21T16:56:31.243764709Z	- __next-on-pages-dist__/chunks/7563.js (esm)
2023-07-21T16:56:31.243903833Z	- __next-on-pages-dist__/chunks/7650.js (esm)
2023-07-21T16:56:31.244048712Z	- __next-on-pages-dist__/chunks/7707.js (esm)
2023-07-21T16:56:31.244246692Z	- __next-on-pages-dist__/chunks/7730.js (esm)
2023-07-21T16:56:31.244307623Z	- __next-on-pages-dist__/chunks/7751.js (esm)
2023-07-21T16:56:31.244548501Z	- __next-on-pages-dist__/chunks/7762.js (esm)
2023-07-21T16:56:31.244676091Z	- __next-on-pages-dist__/chunks/7879.js (esm)
2023-07-21T16:56:31.244839909Z	- __next-on-pages-dist__/chunks/7925.js (esm)
2023-07-21T16:56:31.244988243Z	- __next-on-pages-dist__/chunks/7960.js (esm)
2023-07-21T16:56:31.245532534Z	- __next-on-pages-dist__/chunks/7995.js (esm)
2023-07-21T16:56:31.245822365Z	- __next-on-pages-dist__/chunks/801.js (esm)
2023-07-21T16:56:31.246095785Z	- __next-on-pages-dist__/chunks/8086.js (esm)
2023-07-21T16:56:31.246282498Z	- __next-on-pages-dist__/chunks/81.js (esm)
2023-07-21T16:56:31.246606304Z	- __next-on-pages-dist__/chunks/8141.js (esm)
2023-07-21T16:56:31.246863177Z	- __next-on-pages-dist__/chunks/8169.js (esm)
2023-07-21T16:56:31.247123793Z	- __next-on-pages-dist__/chunks/819.js (esm)
2023-07-21T16:56:31.247357589Z	- __next-on-pages-dist__/chunks/8216.js (esm)
2023-07-21T16:56:31.247629087Z	- __next-on-pages-dist__/chunks/8320.js (esm)
2023-07-21T16:56:31.247914707Z	- __next-on-pages-dist__/chunks/8335.js (esm)
2023-07-21T16:56:31.248177634Z	- __next-on-pages-dist__/chunks/835.js (esm)
2023-07-21T16:56:31.248452292Z	- __next-on-pages-dist__/chunks/8364.js (esm)
2023-07-21T16:56:31.249398636Z	- __next-on-pages-dist__/chunks/8407.js (esm)
2023-07-21T16:56:31.249645793Z	- __next-on-pages-dist__/chunks/844.js (esm)
2023-07-21T16:56:31.249830076Z	- __next-on-pages-dist__/chunks/8460.js (esm)
2023-07-21T16:56:31.25000773Z	- __next-on-pages-dist__/chunks/8478.js (esm)
2023-07-21T16:56:31.250194633Z	- __next-on-pages-dist__/chunks/8513.js (esm)
2023-07-21T16:56:31.250366882Z	- __next-on-pages-dist__/chunks/8546.js (esm)
2023-07-21T16:56:31.250529217Z	- __next-on-pages-dist__/chunks/8677.js (esm)
2023-07-21T16:56:31.250710544Z	- __next-on-pages-dist__/chunks/8679.js (esm)
2023-07-21T16:56:31.250870656Z	- __next-on-pages-dist__/chunks/8682.js (esm)
2023-07-21T16:56:31.251054584Z	- __next-on-pages-dist__/chunks/8698.js (esm)
2023-07-21T16:56:31.251181888Z	- __next-on-pages-dist__/chunks/8700.js (esm)
2023-07-21T16:56:31.25125403Z	- __next-on-pages-dist__/chunks/8736.js (esm)
2023-07-21T16:56:31.25145008Z	- __next-on-pages-dist__/chunks/8756.js (esm)
2023-07-21T16:56:31.25482869Z	- __next-on-pages-dist__/chunks/8791.js (esm)
2023-07-21T16:56:31.254854254Z	- __next-on-pages-dist__/chunks/8839.js (esm)
2023-07-21T16:56:31.254858958Z	- __next-on-pages-dist__/chunks/8849.js (esm)
2023-07-21T16:56:31.254862748Z	- __next-on-pages-dist__/chunks/8945.js (esm)
2023-07-21T16:56:31.254901984Z	- __next-on-pages-dist__/chunks/8951.js (esm)
2023-07-21T16:56:31.254906638Z	- __next-on-pages-dist__/chunks/8974.js (esm)
2023-07-21T16:56:31.254910584Z	- __next-on-pages-dist__/chunks/9079.js (esm)
2023-07-21T16:56:31.254914353Z	- __next-on-pages-dist__/chunks/9111.js (esm)
2023-07-21T16:56:31.254918088Z	- __next-on-pages-dist__/chunks/9129.js (esm)
2023-07-21T16:56:31.25492182Z	- __next-on-pages-dist__/chunks/913.js (esm)
2023-07-21T16:56:31.254925609Z	- __next-on-pages-dist__/chunks/9136.js (esm)
2023-07-21T16:56:31.254929953Z	- __next-on-pages-dist__/chunks/9320.js (esm)
2023-07-21T16:56:31.254933727Z	- __next-on-pages-dist__/chunks/9328.js (esm)
2023-07-21T16:56:31.254937956Z	- __next-on-pages-dist__/chunks/9329.js (esm)
2023-07-21T16:56:31.254941973Z	- __next-on-pages-dist__/chunks/9380.js (esm)
2023-07-21T16:56:31.254945889Z	- __next-on-pages-dist__/chunks/9395.js (esm)
2023-07-21T16:56:31.254949762Z	- __next-on-pages-dist__/chunks/9400.js (esm)
2023-07-21T16:56:31.254953565Z	- __next-on-pages-dist__/chunks/9477.js (esm)
2023-07-21T16:56:31.25495723Z	- __next-on-pages-dist__/chunks/9625.js (esm)
2023-07-21T16:56:31.254960979Z	- __next-on-pages-dist__/chunks/9643.js (esm)
2023-07-21T16:56:31.254968622Z	- __next-on-pages-dist__/chunks/9689.js (esm)
2023-07-21T16:56:31.254972612Z	- __next-on-pages-dist__/chunks/9707.js (esm)
2023-07-21T16:56:31.25497686Z	- __next-on-pages-dist__/chunks/9745.js (esm)
2023-07-21T16:56:31.254980911Z	- __next-on-pages-dist__/chunks/9766.js (esm)
2023-07-21T16:56:31.256165924Z	- __next-on-pages-dist__/chunks/9782.js (esm)
2023-07-21T16:56:31.256184433Z	- __next-on-pages-dist__/chunks/9864.js (esm)
2023-07-21T16:56:31.256189289Z	- __next-on-pages-dist__/chunks/9886.js (esm)
2023-07-21T16:56:31.256193317Z	- __next-on-pages-dist__/chunks/9921.js (esm)
2023-07-21T16:56:31.256197044Z	- __next-on-pages-dist__/chunks/9949.js (esm)
2023-07-21T16:56:31.256201162Z	- __next-on-pages-dist__/chunks/9968.js (esm)
2023-07-21T16:56:31.256205061Z	- __next-on-pages-dist__/chunks/9974.js (esm)
2023-07-21T16:56:31.256218178Z	- __next-on-pages-dist__/chunks/9978.js (esm)
2023-07-21T16:56:31.256222418Z	- __next-on-pages-dist__/chunks/9996.js (esm)
2023-07-21T16:56:31.258170954Z	- __next-on-pages-dist__/functions/api/hello.func.js (esm)
2023-07-21T16:56:31.25819351Z	- __next-on-pages-dist__/functions/index.func.js (esm)
2023-07-21T16:56:31.258198198Z	- __next-on-pages-dist__/functions/me/profile.func.js (esm)
2023-07-21T16:56:31.258202024Z	- __next-on-pages-dist__/functions/middleware.func.js (esm)
2023-07-21T16:56:31.258206247Z	- __next-on-pages-dist__/nextjs-manifests/__BUILD_MANIFEST.js (esm)
2023-07-21T16:56:31.258210951Z	- __next-on-pages-dist__/nextjs-manifests/__NEXT_FONT_MANIFEST.js (esm)
2023-07-21T16:56:31.258214859Z	- __next-on-pages-dist__/nextjs-manifests/__REACT_LOADABLE_MANIFEST.js (esm)
2023-07-21T16:56:31.258219057Z	- __next-on-pages-dist__/assets/noto-sans-v27-latin-regular.5dda3fca77107598.ttf.bin (buffer)
2023-07-21T16:56:31.258223067Z	- __next-on-pages-dist__/wasm/wasm_a7e702bc5ba9227243abda7977c8096f59478d3f.wasm (compiled-wasm)
2023-07-21T16:56:31.258226923Z	- __next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm (compiled-wasm)
2023-07-21T16:56:31.30371358Z	✨ Compiled Worker successfully
2023-07-21T16:56:31.451501214Z	Found _routes.json in output directory. Uploading.
2023-07-21T16:56:31.46868114Z	Validating asset output directory
2023-07-21T16:56:32.29122226Z	Deploying your site to Cloudflare's global network...
2023-07-21T16:56:35.042881565Z	Parsed 1 valid header rule.
2023-07-21T16:56:36.471434907Z	Uploading... (0/30)
2023-07-21T16:56:37.591076849Z	Uploading... (10/30)
2023-07-21T16:56:37.707447407Z	Uploading... (20/30)
2023-07-21T16:56:37.899371962Z	Uploading... (30/30)
2023-07-21T16:56:37.899654376Z	✨ Success! Uploaded 30 files (1.86 sec)
2023-07-21T16:56:37.899933338Z
2023-07-21T16:56:38.255036137Z	✨ Upload complete!
2023-07-21T16:56:40.660556Z	Success: Assets published!
2023-07-21T16:56:44.73812Z	Error: Failed to publish your Function. Got error: Your Functions script is over the 1 MiB size limit (workers.api.error.script_too_large)

Thank you @Richard87. Looking at this, I actually believe Clerk is causing your issues. It kind of explains something that I wasn't able to explain when I was looking at a reproduction for a Clerk issue the other day. I didn't understand why I was seeing wasm files in the reproduction, but I see the same ones in your project.
Without Clerk:

0 wasm files.
0 font files.
total unzipped size is 600kb.

With Clerk sign-out component, context provider, and middleware:

2 wasm files.
1 font file.
total unzipped size is 2.4mb.

To me, it seems like Clerk is using things that it has no need to, and, as such, it is resulting in big wasm files (1.4mb total) and webpack chunks that don't need to be there. In your repo for instance, the unzipped middleware function goes from 30kb -> 800kb after our deduping, just because it uses clerk - for some reason it has chunks that are of no relevance, like all of reactjs.
When I look at the chunks that use the Wasm files, and the font, they actually look like they're coming from @vercel/og somewhere, and the chunk that appears to be using the @vercel/og chunk relates to ImageResponse code in Next.js. And that chunk appears to be consumed in the next/server chunk (this code). And the next/server webpack chunk is used in the @clerk/nextjs webpack chunk.
So, to summarise, it appears that Clerk is adding all this unnecessary code that shouldn't be there and thereby is massively inflating your bundle size.

Thanks for doing looking into it! I'm opening an issue at Clerk side ASAP!

Yup, same, we only have 2 pages, and over 1mb
Edit @dario-piotrowicz / @james-elicx , sorry for the ping, is there any solution to use Nextjs on Pages? Something is not adding up :/
Edit 2: This is the result from Nextjs build:

Route (pages)                              Size     First Load JS
┌ ℇ /                                      12.7 kB         190 kB
├   /_app                                  0 B             133 kB
├ ○ /404                                   194 B           134 kB
├ ℇ /api/hello                             0 B             133 kB
├ ℇ /me/profile                            43.5 kB         221 kB
├ ○ /sign-in/[[...index]]                  408 B           134 kB
└ ○ /sign-up/[[...index]]                  408 B           134 kB
+ First Load JS shared by all              134 kB
  ├ chunks/framework-4556c45dd113b893.js   45.2 kB
  ├ chunks/main-267015de6884ae13.js        30.1 kB
  ├ chunks/pages/_app-b0675639f806e8f3.js  57 kB
  ├ chunks/webpack-45c1d38871d29bef.js     1.03 kB
  └ css/0705bda694329cbb.css               306 B

ƒ Middleware                               333 kB

@Richard87, I'd also like to point out that the numbers above are JS payload size for the client-side code and not for the server-side code. I suspect that if you were to look at the build output Vercel CLI provides you with, you'd find that the vercel output is actually several times the size of what @cloudflare/next-on-pages is pushing to Pages.

Yup, absolutley, but basically 2 wasm files, one small(less than 100kb), and one big(1mb+).
 By design next-on-pages aggressively dedupes and optimizes the output Vercel CLI produces to the extent it is safe to do so without breaking the app.


sveltekit: Protected Routes

Improve documentation
The code snippet in the guide describes how to protect routes.
Link
https://github.com/supabase/auth-helpers/blame/main/packages/sveltekit/README.md#L240
Describe the problem
However, wouldn't this

just protect the GET method
any subroutes are still accessible.

Describe the improvement
It would be great if a way is displayed that protects any HTTP method access, as well as blocking any sub path access.

There is no a clean way to solve auth for multiple routes currently, but that´s on sveltekit´s side since its missing some sort of middleware.
You can however create a handle hook to secure multiple pages in one place.
Here we check for POST requests that go to a url starting with /protected-route
// src/hooks.server.ts
export const handle = async ({ event, resolve }) => {
	if (event.url.pathname.startsWith('/protected-route' && event.request.method === 'POST') {
		const { session, supabaseClient } = await getSupabase(event);
		if (!session) {
			throw error(401);
		}
		// do your middleware stuff here
		// for example store the session in locals
		event.locals.session = session;
	}

	return resolve(event);
}

I think we can add this to the docs

Excellent, thanks David!
Just curious why add && event.request.method === 'POST'), without this, it would protect from any HTTP method, right?
Yes, please add this to the docs - it's a common scenario for many use cases.

Just curious: Without && event.request.method === 'POST'), it would protect from any HTTP method, right?

Yeah, i just added it as an example.

Also, this could as well work on hooks.client.ts ?

The handle hook only exists on the server. If you want client side authentication you need to use the layout and page load functions to restrict access to pages.


2FA

We  trying to config for 2FA on one login ? Do we configure Djongo on one login ?
or Do you have documentation how to do it with one login?

Are you asking if two factor login can be done in one request? No, not out of the box.
If you limit your users to one specific type of 2FA (e.g. TOTP devices) you might be able to make your own login view that handles the username, password, and 2nd factor all in one go.

No. I am not asking that.

Do this application using
SAML federation or  IDP Federation ?

I don't know what either of those are, but this package has nothing to do with federation.

i Just mailed you our product description. i hope is easy to understand. Please reply me back.

A quick Google search for "onelogin django" gave me this: https://github.com/onelogin/python-saml
I think that's probably what you want.


External Global functions in Table 11401

Hello,
We are using in page extension some global functions from TAB11401 "CBG Statement Line":

CreateGenJournalLine
ReadGenJournalLine

Could you please make those function "External" in order to be able to call them from AL ?
Used image: ..12.0.21229.0-nl
Thanks,
Andrei Lungu

Done :)


AttributeError: 'Nonetype '

I have set up Windows with Python 2.7.x, and have installed all of the dependencies. I believe I have everything configured properly at this time, but when I try to run the tool I keep getting a "NoneType" error. I have attached a screenshot of the error. Can you provide any insight as to what might be causing this?

It looks like an element is not visible that it's looking for. In the beginning steps when it first sets up credentials you many need to do a manual step with the browser.

Thanks. I noticed that I had not yet registered the device, and there was a problem with that. I have resolved it, but it has not cleared the error. The script seems to stop at the screen where it asks you to select a user account. I try selecting one of them, and I receive a redirect_uri_mismatch error. Attached is a screenshot of the error page. The url, in case that should be useful, is below:
https://accounts.google.com/o/oauth2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcloudprint+https%3A%2F%2Fspreadsheets.google.com%2Ffeeds%2F&response_type=code&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&client_id=873159778538-irju3u707ve8806gm1fctsduaim1jmlh.apps.googleusercontent.com&hl=en&from_login=1&as=7aecc6b32ae126a9&authuser=0

H'mmmm, it may be that you're using a browser that has multiple accounts associated with it. To resolve that, try going into Chrome's data directory and deleting it, so that no accounts are associated with the browser you are using to test with. For the Logo Cert Tool, it creates a directory in the directory where it runs, that is named identical to the user account (minus @gmail.com), so just delete that.

Ok, thanks. I've tried this, but unfortunately, it didn't work. Incidentally, there were two accounts associated with it, but only because the tool asks for a 2nd user account. I haven't gotten to a point where it's actually used, though.

It appears I either didn't have the configuration file correct (namely the gmail1, 2, and 3 links) or the client wasn't set up correctly. The first client I created was a Web Application. I created a new one as "Other". It's not explicitly stated in the README if this is correct.

Did your latest changes resolve the issue?

I seem to have gotten past this issue, yes. Still having some other ones. When I create credentials for a 0Auth client id, can you confirm whether this should be "Web Application" or "Other" for Native applications?

This issue is no longer occurring.


Avoid assertion failure when using Host Device

Passing a device ID of zero (Host device) to FSEventsCopyUUIDForDevice
causes the following assertion failure error to be printed to the logs:

(FSEvents.framework) FSEventsCopyUUIDForDevice(): failed assertion 'dev > 0'

Codecov Report

Merging #32 into master will decrease coverage by 0.43%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
- Coverage   43.03%   42.59%   -0.44%
==========================================
  Files           2        2
  Lines         165      162       -3
==========================================
- Hits           71       69       -2
  Misses         84       84
+ Partials       10        9       -1

Impacted Files
Coverage Δ

fsevents.go
43.58% <0%> (-1.15%)
:arrow_down:

wrap.go
42.27% <0%> (-0.25%)
:arrow_down:

Continue to review full report at Codecov.

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

@adriansr sorry nobody has looked at this. Can you please rebase on master and see if the tests pass?

This github conflict editor is nonsense. Please rebase this branch to get upgraded travis tests for 1.10.

@drewwells it's rebased now. Thanks for looking at this :)

@adriansr this PR does not fix the assertion message. Applying your patch and changing the test to use dev id 0 results in the same error message:
2018-07-17 22:04 fsevents.test[23666] (FSEvents.framework) FSEventsCopyUUIDForDevice(): failed assertion 'dev > 0'

@patsoffice I clearly have broken something.
It seems on May I sent a different fix and for some reason overwrote this branch. Let me see if I can find the original.

Closed in favor of @patsoffice PR which is more complete


Switch to OpenWeatherMap API

The old code uses the paid weather.com API. Switching to a more modern API allows for flexibility and better code style.

Open-Meteo will be used instead since it has a free API and is open source.


CompileGraph throw an instance of 'std::out_of_range'

Bug Description
The trtorch::CompileGraph throw an instance of 'std::out_of_range' during the Conversion Context and imminently terminate
To Reproduce
Steps to reproduce the behavior:

Extract the attached file - Input.zip

Place the file module.pt

Execute the following code
`
    const std::vector<std::vector<int64_t>> input_shapes = { { 4, 24, 64, 64 }, { 1, 24, 1, 1 } };
     std::string modelPath = "model.pt";
 auto lrs = at::randint(5, { 4, 24, 64, 64 }, { torch::kCUDA });
 auto alphas = at::randint(5, { 1, 24, 1, 1 }, { torch::kCUDA });

 std::vector<torch::jit::IValue> trt1_inputs_ivalues;
 trt1_inputs_ivalues.push_back(lrs.clone());
 trt1_inputs_ivalues.push_back(alphas.clone());

 std::cout << "TRTorch model compile graph:" << '\n';
 auto trt_mod = trtorch::CompileGraph(module, input_shapes);

 std::cout << "TRTorch model inference:" << '\n';
 auto out = trt_mod.forward(trt1_inputs_ivalues);

`

The following error reported:
DEBUG: [TRTorch Conversion Context] - Evaluating %48 : int = aten::size(%lrs.1, %29) # code/superResolutionGpu.py:91:36
WARNING: [TRTorch - Debug Build] - There may be undefined behavior using dynamic shape and aten::size
DEBUG: [TRTorch Conversion Context] - Found the value to be: 4
DEBUG: [TRTorch Conversion Context] - Evaluating %batch_size.1 : Tensor = prim::NumToTensor(%48) # code/superResolutionGpu.py:91:15
terminate called after throwing an instance of 'std::out_of_range'
what():  map::at
Aborted (core dumped)

Expected behavior
trt_mod returned object is valid and can be used to perform forward operation.
Environment

Build information about the TRTorch compiler can be found by turning on debug messages

PyTorch Version (e.g., 1.0): 1.6
CPU Architecture: Jetson Xavier AGX
OS (e.g., Linux): JetPack 4.4
How you installed PyTorch (conda, pip, libtorch, source): pip3
Build command you used (if compiling from source):
Are you using local sources or building from archives: local
Python version: 3.6.9
CUDA version:10.2
GPU models and configuration: Jetson Xavier AGX
Any other relevant information: JetPack 4.4

Additional context
The attached zip file contains the full execution report with all required reported error information
The same model but in *.onnx format (generated from the same torch model via torch.onnx.export) is processed successfully via the TRT C++ interface without any run time exception as described above.
If it can help I can share it too.

Hello,
Any help here will much appreciated please.
If any further material is required to analyze my problem please notify.
Thanks!

I have same problem.

@OronG13 Can you try with the latest release ? We've updated pytorch to 1.7.1. This is the error that I see now with the latest release
terminate called after throwing an instance of 'trtorch::Error'
  what():  [enforce fail at core/conversion/evaluators/NodeEvaluatorRegistry.cpp:62] Expected schema to be true but got false
Evaluator for aten::mulonly runs on certain schemas, but schema for node is not retrievable

@OronG13 Can you try with the latest release ? We've updated pytorch to 1.7.1. This is the error that I see now with the latest release
terminate called after throwing an instance of 'trtorch::Error'
  what():  [enforce fail at core/conversion/evaluators/NodeEvaluatorRegistry.cpp:62] Expected schema to be true but got false
Evaluator for aten::mulonly runs on certain schemas, but schema for node is not retrievable

a week ago, I test my model with pytorch 1.7.1, this problem remains.

Thanks @peri044 & @zccyman,
I'm little bit confused,
@peri044:
based on your response it seems that the original problem isn't reproduced but a new one was raised so it still not OK.
Please approve.
@zccyman:
Did you see the same old problem or the new one described by @peri044?
Additionally,
Please clarify your test environment in order to verify that we are using the same.
Do you have the same environment as described above by me?
Did you upgrade only PyTorch version to 1.7.1 instead of 1.6?
All the rest stay without changes?
In general,
Due to the fact that with the same model *.onnx format using the TRT C++ everything is working fine in the same environment described above, I don't think it is a matter of PyTorch but only TRTorch C++.
My assumption based on the fact that the *.onnx was generated from the same TorchScript *.pt tile that was unsuccessfully compiled by the TRTorch C++ but successfully parsered, optimized and inferenced by the TRT C++.
Thanks,

Thanks @peri044 & @zccyman,
I'm little bit confused,
@peri044:
based on your response it seems that the original problem isn't reproduced but a new one was raised so it still not OK.
Please approve.
@zccyman:
Did you see the same old problem or the new one described by @peri044?
Additionally,
Please clarify your test environment in order to verify that we are using the same.
Do you have the same environment as described above by me?
Did you upgrade only PyTorch version to 1.7.1 instead of 1.6?
All the rest stay without changes?
In general,
Due to the fact that with the same model *.onnx format using the TRT C++ everything is working fine in the same environment described above, I don't think it is a matter of PyTorch but only TRTorch C++.
My assumption based on the fact that the *.onnx was generated from the same TorchScript *.pt tile that was unsuccessfully compiled by the TRTorch C++ but successfully parsered, optimized and inferenced by the TRT C++.
Thanks,

@OronG13 Yes. I faced a different error. My environment is different. I'm using an x86 machine with 2080 Ti GPU. Since we have moved to Pytorch 1.7.1 in TRTorch, I recommend trying the latest release on your environment. Can you let me know if you see the old error or the new one posted in this comment  using your environment?
This can help narrow down the root cause for debugging.

@OronG13 Yes. I faced a different error. My environment is different. I'm using an x86 machine with 2080 Ti GPU. Since we have moved to Pytorch 1.7.1 in TRTorch, I recommend trying the latest release on your environment. Can you let me know if you see the old error or the new one posted in this comment  using your environment?
This can help narrow down the root cause for debugging.

Hello @peri044,
OK, I now understand,
Unfortunately, PyTorch version 1.7.1 pre built binaries are not available for Jetson aarch64, the newest available version is 1.7.0 as detailed here (Built from sources the PyTorch is not a friendly task):
https://forums.developer.nvidia.com/t/pytorch-for-jetson-version-1-7-0-now-available/72048
I will try to work with this latest version for aarch64 and update you.
Additional question:
Which TRTorch C++ version are you working with? 0.1.0? master? other tag\branch?
Thanks,

Hello @peri044,
OK, I now understand,
Unfortunately, PyTorch version 1.7.1 pre built binaries are not available for Jetson aarch64, the newest available version is 1.7.0 as detailed here (Built from sources the PyTorch is not a friendly task):
https://forums.developer.nvidia.com/t/pytorch-for-jetson-version-1-7-0-now-available/72048
I will try to work with this latest version for aarch64 and update you.
Additional question:
Which TRTorch C++ version are you working with? 0.1.0? master? other tag\branch?
Thanks,


Add support for dist-upgrade & autoremove action

It would be useful if the apt task could also be used for performing dist-upgrade and autoremove actions in batch. This PR adds support for these.

Hey @aboks,
We would like to thank you for taking the time to contribute to our supported module. Would it be possible for you to add some tests and I can work on getting this merged.
Many Thanks
The Modules Team.

Hi @pmcmaw, Ruby is not my 'native' language, but I've tried to add some tests.

That looks perfect! :-)
I am going to run it through the internal adhoc pipeline and hopefully get it merged.
Thanks for such a quick turnaround, really appreciated.

Your code has now been merged into master.
I would like to take the time to thank you for for your contribution.
Many Thanks
The Modules Team


add fixture 'chauvet-dj/corepar-uv-usb'

update manufacturers.json
add fixture 'chauvet-dj/corepar-uv-usb'
update register.json

Thank you @Fxedel!

Export files validity
(Output of test script tests/github/exports-valid.js.)
Test the exported files of selected fixtures against the plugins' export tests.
You can run a plugin's export tests by executing:
$ node cli/run-export-test.js -p <plugin name> <fixtures>
Fixture chauvet-dj/corepar-uv-usb changed in this PR

d-light

attributes-correctness

:white_check_mark: chauvet-dj/corepar-uv-usb-5ch.xml
:white_check_mark: chauvet-dj/corepar-uv-usb-1ch.xml

ecue
ofl
qlcplus

xsd-schema-conformity

:x: Chauvet-DJ-COREpar-UV-USB.qxf
Show errors

Element '{http://www.qlcplus.org/FixtureDefinition}Group': [facet 'enumeration'] The value 'Switching Channel' is not an element of the set {'Intensity', 'Colour', 'Gobo', 'Prism', 'Shutter', 'Beam', 'Speed', 'Effect', 'Pan', 'Tilt', 'Maintenance', 'Nothing'}.
Element '{http://www.qlcplus.org/FixtureDefinition}Group': 'Switching Channel' is not a valid value of the atomic type '{http://www.qlcplus.org/FixtureDefinition}groupEnumType'.

Broken links
(Output of test script tests/http-status.js.)
There were 0 internal and 4 external links failing.

http://www.adblighting.com/?page=getsupportfile&file=165
https://www.claypaky.it/en/home/
https://www.claypaky.it/media/documents/HR_Sharpy_Manual_05.2016_EN.pdf
http://www.coemar.com/media/file/Prospot_250_LX_E1.pdf

Export files validity
(Output of test script tests/github/exports-valid.js.)
Test the exported files of selected fixtures against the plugins' export tests.
You can run a plugin's export tests by executing:
$ node cli/run-export-test.js -p <plugin name> <fixtures>
Fixture chauvet-dj/corepar-uv-usb changed in this PR

d-light

attributes-correctness

:white_check_mark: chauvet-dj/corepar-uv-usb-5ch.xml
:white_check_mark: chauvet-dj/corepar-uv-usb-1ch.xml

ecue
ofl
qlcplus

xsd-schema-conformity

:white_check_mark: Chauvet-DJ-COREpar-UV-USB.qxf

Plugin export diff
(Output of test script tests/github/export-diff.js.)
You can run view your uncommited changes in plugin exports manually by executing:
$ node cli/diff-plugin-outputs.js -p <plugin name> <fixtures>
Fixture coemar/prospot-250-lx modified in this PR
Fixture output to all plugins is checked.
:information_source: Plugin d-light
Outputted files not changed.
:information_source: Plugin ecue
Outputted files not changed.
:information_source: Plugin qlcplus
Outputted files not changed.

Export files validity
(Output of test script tests/github/exports-valid.js.)
Test the exported files of selected fixtures against the plugins' export tests.
You can run a plugin's export tests by executing:
$ node cli/run-export-test.js -p <plugin name> <fixtures>
Fixture chauvet-dj/corepar-uv-usb changed in this PR

d-light

attributes-correctness

:white_check_mark: chauvet-dj/corepar-uv-usb-5ch.xml
:white_check_mark: chauvet-dj/corepar-uv-usb-1ch.xml

ecue
ofl
qlcplus

xsd-schema-conformity

:white_check_mark: Chauvet-DJ-COREpar-UV-USB.qxf

Fixture coemar/prospot-250-lx changed in this PR

d-light

attributes-correctness

:white_check_mark: coemar/prospot-250-lx-strd.xml
:white_check_mark: coemar/prospot-250-lx-emul.xml

ecue
ofl
qlcplus

xsd-schema-conformity

:white_check_mark: Coemar-ProSpot-250-LX.qxf

Broken links
(Output of test script tests/http-status.js.)
There were 0 internal and 3 external links failing.

http://www.adblighting.com/?page=getsupportfile&file=165
https://www.claypaky.it/en/home/
https://www.claypaky.it/media/documents/HR_Sharpy_Manual_05.2016_EN.pdf


Reaching the best trained model checkpoint

Hi,
In Ray Tune I can get the checkpoint value of the "best" trial like this:
result = tune.run(
        tune.with_parameters(train),
        resources_per_trial={"cpu": 12, "gpu": gpus_per_trial},
        config=config,
        num_samples=num_samples,
        search_alg=hyperopt_search,
        scheduler=scheduler)

best_trial = result.get_best_trial("accuracy", "max", "last")
best_checkpoint_dir = best_trial.checkpoint.value

Then, I can load the best checkpoint to my model like this:
model_state, optimizer_state = torch.load(os.path.join(best_checkpoint_dir, "checkpoint"))
my_model = Lenet5()
my_model.load_state_dict(model_state)

I couldn't understand how to do the exact same thing with Syne Tune. (I can not reach the best trained model)
Could you please help with this ?
Thank you so much :)

Hello,
Syne Tune is agnostic to how checkpointing is implemented, in the sense that your training script has to implement it (there are helper functions for PyTorch models). For this reason, we also do not have a simple way of accessing individual checkpoints and load corresponding models.
If we standardized the way in which training scripts write/load checkpoints more (as apparently Ray Tune is doing), we could offer this functionality. For example, for a user with PyTorch models, if they use our provided functions to save/load checkpoints (and not some home-made code), we could do it.
However, some training scripts may not include checkpointing (our schedulers still work then), some may checkpoint not after every epoch, and previous checkpoints for a trial are overwritten by newer ones. I am therefore not sure it is great practice to assume that certain checkpoints written during HPO (for the purpose of pause and resume) are available later on.
Also, I'd recommend to retrain your best model on all data, including the validation data, in which case the HPO checkpoint is of no use.

Hello, we have this request on our back-log, to write some docs on how to do what you like to do.
However, please note you will have to implement checkpointing (save to / load from local files) on your own in your training script. If you use PyTorch, we provide some helper functions, please check the docs. If you use Hugging Face, we have an example that includes checkpointing.

Okay, I understand. Thank yo soo much for your reply :)

Hi @ElifCerenGok, we added an example let us know if it solves your use-case! :-)


Support for db initialization scripts

Hello
it would be nice to have an out-of-the-box support for loading sql scripts during initialization of mariadb instance
afaik you could achieve this simply with configmaps, if scripts loaded is < 1Mb, or by implementing a container that clone a git repository and mounts the script in a volume, but it seems quite cumbersome
thank you

Hey there @fabioportieri !
I've been thinking about this but I don't think we should overload more the MariaDB  bootstrap process as it is could currently become very heavy by performing tasks like restoring a backup.
Alternatively we could define a new CRD SqlJob which can execute *.sql scripts in a MariaDB impersonating and user:
apiVersion: mariadb.mmontes.io/v1alpha1
kind: SqlJob
metadata:
  name: mariadb-create-table
spec:
     database: mariadb
     asUser: mariadb
     passwordSecretKeyRef:
        name: mariadb
        key: password
      mariaDbRef:
         name: mariadb
      sqlScript: |
           CREATE OR REPLACE TABLE foo (a int);

The user would be able to provide a Configmap key reference instead:
apiVersion: mariadb.mmontes.io/v1alpha1
kind: SqlJob
metadata:
name: mariadb-create-table
spec:
   database: mariadb
   asUser: mariadb
   passwordSecretKeyRef:
      name: mariadb
      key: password
    mariaDbRef:
       name: mariadb
    sqlScriptConfigmapKeyRef:
        name: mariadb-script
        key: 'init.sql'

and also orchestrate multiple SqlJob by providing a dependsOn:
apiVersion: mariadb.mmontes.io/v1alpha1
kind: SqlJob
metadata:
 name: mariadb-insert-table
spec:
    dependsOn:
       - name: mariadb-create-table
    database: mariadb
    asUser: mariadb
    passwordSecretKeyRef:
       name: mariadb
       key: password
     mariaDbRef:
        name: mariadb
     sqlScript: |
          INSERT INTO foo VALUES(1);

Does this cover your needs?

Hey @fabioportieri !
This has been implemented, take a look at the updated quickstart guide and examples:

https://github.com/mmontes11/mariadb-operator#quickstart
https://github.com/mmontes11/mariadb-operator/tree/main/config/samples/sqljobs

Closing!


Indicate units required in function summarys

Feature Request:
Can you change the summary comments on the functions to indicate what units are required for the parameters?
for example
locator.StartListeningAsync(minTime, minDistance);
I can tell minTime is milliseconds from your code (at least for Android), having it in the comments would of saved me confirming :-)

put in timespans


Slow and high cpu usage when adding big files (>14GB)

When I try to add 2 files of 7GB each, dat does not show any progress (see #544). However it eats around 70-80% of my CPU for more than 10 minutes until I see a completion of 21.6 GB/14.88 GB. Even after that, the process is not over as my cpu is still used.
Specs:

Intel Atom N2840 @2.16GHz
Archlinux

@mafintosh is it possible that his installation fell back to a js version of libsodium? Is there any way to quickly check which version is being used, js or native?

@G-Ray do you have any more info on this? I think this might be related to the memory leak that @mafintosh found. Could you update dat to the newest version and see if you could reproduce?
Also, using --debug at the end of the command will give us helpful output we can use! Thank you!

Closing this until we get more info


Fixes for using debugger

This fixes errors that occur when running with a Lua debugger.
Note: A full fix will also require an update to luassert, which fixes the same type of error (see Olivine-Labs/luassert#132).
This should fix issues #490 and #491.

thanks a lot!
@o-lim maybe enhance the documentation too? (saying that for the debugger to work, the coverage has to be deactivated?)

We also need to update the docs for this... @ajacksified ?


feat: redirect router

Fixes Issue #7929

closes #7929
Changes proposed

link: after successful save on add/edit, redirect back to manage link list page with successful message
event: after successful save on add/edit, redirect back to the manage event list page with a successful message
milestone: after successful save on add/edit, redirect back to the milestone link list page with the successful message

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Thank you for the contribution

I could not see the successful message code?

I might be wrong but I think with the current implementation we can't show the toast along with redirecting back to the list page
ex- the notification/toast component lies in the account/manage/link/64a4284da005543636769ca0 page when the notification appears we immediately push the router with a new URL(list page) since the notification box is part of the /manage/link/:id when the new route renders it renders a new page where no notification box is present.
To fix this  we can wrap our whole app to a toast/notification provider that way the notification box is present throughout the app and do not closes due to page transition

I might be wrong but I think with the current implementation we can't show the toast along with redirecting back to the list page
ex- the notification/toast component lies in the account/manage/link/[[..id]] page when the notification appears we immediately push the router with a new URL(list page) since the notification box is part of the /manage/link/:id when the new route renders it renders a new page where no notification box is present.
I mean it is visible but for a very short amount of time
To fix this we can wrap our whole app to a toast/notification provider that way the notification box is present throughout the app and does not close due to page transition

Yes the toast can't be used because of the direct, I think we will need to use the alert notification instad and remove the success part of the toast on the add/edit pages

Cool will make the changes

I checked the components/Alert.js component the problem

I might be wrong but I think with the current implementation we can't show the toast along with redirecting back to the list page
ex- the notification/toast component lies in the account/manage/link/[[..id]] page when the notification appears we immediately push the router with a new URL(list page) since the notification box is part of the /manage/link/:id when the new route renders it renders a new page where no notification box is present.
I mean it is visible but for a very short amount of time
To fix this we can wrap our whole app to a toast/notification provider that way the notification box is present throughout the app and does not close due to page transition

Yes the toast can't be used because of the direct, I think we will need to use the alert notification instead and remove the success part of the toast on the add/edit pages

This means there will be no notification for success right? And for errors, we will show an alert, let me know if I am correct

Please can you resolve conflicts then we can get it merged

Done :)

Please can you fix the failing build - I think there is a lint error

Done, this time for sure :(