inputType="email" not supported

Hi,
I've noticed that inputType="email" not working correct the input accept a none valid email if required ={true}.
Any suggestions how can I fix this?
Thanks

When I added
<SweetAlert input inputType="email" validationMsg="Please enter your email address" ... />
I got the validation message if I didn't enter anything, but if I enter a non valid email the SweetAlert accept the value.
I suggest to add new property something like this  validationEmailMsg="You must provide a valid email"
Thanks

Im publishing version 4.4 with support for this.  I'm also exposing a new prop validationRegex if anyone needs to override the regex used.
<SweetAlert
	 input
         inputType="email"
         validationMsg="Must be a valid email!"
	 title="Enter your email!"
	 onConfirm={this.hideAlert}
>
 	Email is required
 </SweetAlert>

I just published 4.4.1 and changed the default validationMsg to 'Please enter a valid email!' for inputType of 'email'

It works thank you very much 👍


Add Fabric Gateway to peers doc

Fabric Gateway doc adds to "peer" topic
Type of change

New feature

Description
Fabric Gateway is enabled / disabled on peer nodes
https://github.com/hyperledger/fabric/issues/2807
Additional details
Somewhat minimal; we can iterate.
Related issues
https://github.com/hyperledger/fabric/issues/2807
"Key Concepts - Josh peers" section

missing the latest gateway.md file. closing for re-do.


Pull the lastest if_warden changes

New xUnit verison
Receive working directory and environment for executing commands in the container host.
Restrict the directories the WardenUsers group can read/write.

These changes look good, pending test confirmation.  Once we've confirmed, I'll merge this in.


Add support for aws client vpn

This is pretty new (released last month, I think), but it's useful:
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/OperationList-query-cvpn.html

Thanks for the request! This should be covered when we upgrade to the latest version of botocore which is scheduled for Rusoto 0.38.0.

Looks like this is now a part of rusoto_ec2 0.37.0! 🎉


Replace post_install.sh with script to handle symlinks

see also:

https://github.com/aegershman/yugabyte-boshrelease/issues/36
https://github.com/aegershman/yugabyte-boshrelease/issues/18

Replace post_install.sh script with a fix which allows for accounting for symlinks in the install directory
linking to https://github.com/yugabyte/yugabyte-db/issues/3732#issuecomment-653261887

Going to merge to master and will validate more in https://github.com/aegershman/yugabyte-boshrelease/issues/217
ooooooooohhhh bby we're close.

Congrats 🎉🎉🎉


Patched SAT Resources download package to replace incomplete Application Insights configuration

Description / Motivation

Updated description of the Sitecore Azure Toolkit Resources package on the SXP 10.4 download page, to identify that it has been patched and republished.
Updated this on both the SXP 10.4 download page, and its Release Notes page.
This accompanies a PR committed to Main just yesterday, which addressed accompanying Azure App Service packages.

How Has This Been Tested?

tested on localhost:3000

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation update (non-breaking change; modified files are limited to the /data directory or other markdown files)

Checklist:

[X] I have read the Contributing guide.
[X] My code/comments/docs fully adhere to the Code of Conduct.
[ ] My change is a code change.
[X] My change is a documentation change and there are NO other updates required.
[ ] My change has new or updated images which are stored in the /public/images folder that need to be migrated to Sitecore DAM

Tested this PR again on the Vercel preview. All good. Ready to commit to Main please.


I got errors when training the code

Hi, Minkai, I use your data generation code to generate datasets with a new version of pyg, however, I got the following error when training, do you have any idea?
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [1479, 128]], which is output 0 of ReluBackward0, is at version 1; expected version 0 instead. Hint: the backtrace further above shows the operation that failed to compute its gradient. The variable in question was changed in there or anywhere later. Good luck!

By the data generation code, you refer to the ConfGF repo? (https://github.com/DeepGraphLearning/ConfGF#prepare-your-own-geom-dataset-from-scratch-optional)

yes, I followed your code and generate the dataset, but still find error in training

umm, wired. would you mind providing the full error, like the error occurs at which line?

File "train.py", line 170, in
train(it)
File "train.py", line 104, in train
return_unreduced_loss=True
File "/home//protein/GeoDiff/models/epsnet/dualenc.py", line 244, in get_loss
anneal_power, return_unreduced_loss, return_unreduced_edge_loss, extend_order, extend_radius, is_sidechain)
File "/home//protein/GeoDiff/models/epsnet/dualenc.py", line 279, in get_loss_diffusion
is_sidechain = is_sidechain
File "/shared_space//anaconda3/envs/deepdock/lib/python3.6/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(input, kwargs)
File "/home//protein/GeoDiff/models/epsnet/dualenc.py", line 220, in forward
edge_attr=edge_attr_local[local_edge_mask],
File "/shared_space//anaconda3/envs/deepdock/lib/python3.6/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(input, kwargs)
File "/home//protein/GeoDiff/models/encoder/gin.py", line 109, in forward
hidden = self.activation(hidden)
File "/shared_space//anaconda3/envs/deepdock/lib/python3.6/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(input, kwargs)
File "/shared_space//anaconda3/envs/deepdock/lib/python3.6/site-packages/torch/nn/modules/activation.py", line 98, in forward
return F.relu(input, inplace=self.inplace)
File "/shared_space//anaconda3/envs/deepdock/lib/python3.6/site-packages/torch/nn/functional.py", line 1299, in relu
result = torch.relu(input)
(function _print_stack)
Traceback (most recent call last):
File "train.py", line 170, in
train(it)
File "train.py", line 107, in train
loss.backward()
File "/shared_space//anaconda3/envs/deepdock/lib/python3.6/site-packages/torch/_tensor.py", line 307, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
File "/shared_space//anaconda3/envs/deepdock/lib/python3.6/site-packages/torch/autograd/init.py", line 156, in backward
allow_unreachable=True, accumulate_grad=True)  # allow_unreachable flag
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [1479, 128]], which is output 0 of ReluBackward0, is at version 1; expected version 0 instead. Hint: the backtrace further above shows the operation that failed to compute its gradient. The variable in question was changed in there or anywhere later. Good luck!

Try modifying this part? Change from self.edge_encoder_global to self.edge_encoder_local. This is a known small issue for the current code, where the parameters are shared.
https://github.com/MinkaiXu/GeoDiff/blob/d76991dd2edfda98631f001e542ecb933d310803/models/epsnet/dualenc.py#L209-L213

All these errors happen when I try with a new version of pyg and torch. I also try with an older version of packages similar to yours, it can run successfully.
after I fix the above global problem, error occurs in the following code:
node_attr_local = self.encoder_local(
z=atom_type,
edge_index=edge_index[:, local_edge_mask],
edge_attr=edge_attr_global[local_edge_mask],##global
)
I change the global to local, then it occurs to next:
File "/home/---/GeoDiff/models/epsnet/dualenc.py", line 250, in get_loss
anneal_power, return_unreduced_loss, return_unreduced_edge_loss, extend_order, extend_radius, is_sidechain)
File "/home/----/GeoDiff/models/epsnet/dualenc.py", line 285, in get_loss_diffusion
is_sidechain = is_sidechain
And if you are trying to move your code to a new version of pyg, I think you will also meet these? If you will try recently, I can wait for you.

Oh, yes. Another user recently also reported the same issue with a new PyG version. It seems this is caused by the PyG.

Hi,
Some other things in my mind is this part, where maybe you can change to one optimizer:
https://github.com/MinkaiXu/GeoDiff/blob/main/train.py#L70-L73
you can change to something like:
optimizer = get_optimizer(config.train.optimizer, nn.ModuleList([model.model_global, model.model_local]))
scheduler = get_scheduler(config.train.scheduler, optimizer)

And then, also change to only use one optimizer in the following training process, e.g.:
https://github.com/MinkaiXu/GeoDiff/blob/main/train.py#L83-L86
https://github.com/MinkaiXu/GeoDiff/blob/main/train.py#L90-L91
https://github.com/MinkaiXu/GeoDiff/blob/main/train.py#L107-L108
https://github.com/MinkaiXu/GeoDiff/blob/main/train.py#L116-L117
https://github.com/MinkaiXu/GeoDiff/blob/main/train.py#L175-L178
In my experiment, the single-optimizer actually can work pretty well. I'm not sure whether it is this two-optimizer scheme that causes this problem with newer package versions.

请问我也遇到了这个问题one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [1208, 128]], which is output 0 of ReluBackward0, is at version 1; expected version 0 instead。在新的环境该如何解决

Hi Zhuzhu@jinzhuwei, thanks for your interest! Is it possible for you to use the provided env? Pytorch and PyG have been significantly updated recently, so I suppose moving to a new env will require many engineering details...

Thank you for your reply，however，when I use the environment you provided,
an error occurs: NVIDIA GeForce RTX 3090 with CUDA capability sm_86 is not
compatible with the current PyTorch installation. The current PyTorch
install supports CUDA capabilities sm_37 sm_50 sm_60 sm_61 sm_70 sm_75
compute_37. If you want to use the NVIDIA GeForce RTX 3090 GPU with
PyTorch, please check the instructions at
https://pytorch.org/get-started/locally/
warnings.warn(incompatible_device_warn.format(device_name, capability, "
".join(arch_list), device_name))。
Does this error require reinstalling CUDA?
Minkai Xu @.***> 于2023年6月22日周四 12:21写道：

Hi @.***, thanks for your interest! Is it possible for you to
use the provided env? Pytorch and PyG have been significantly updated
recently, so I suppose moving to a new env will require many engineering
details...
—
Reply to this email directly, view it on GitHub
https://github.com/MinkaiXu/GeoDiff/issues/4#issuecomment-1601990641,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAOE47SH5TRCHMMNDOHFSALXMPB43ANCNFSM5S3TVN2Q
.
You are receiving this because you commented.Message ID:
@.***>

oh, I see. it seems like older cuda is required, but I know this might be too annoying...
Have you tried the things mentioned in this thread, about how to modify the code?

I'm very sorry, I'm a novice, I don't know much about this content yet,
except to reinstall CUDA, how can I make relevant code changes, I hope to
get your help.
Minkai Xu @.***> 于2023年6月22日周四 13:51写道：

oh, I see. it seems like older cuda is required, but I know this might be
too annoying...
Have you tried the things mentioned in this thread, about how to modify
the code?
—
Reply to this email directly, view it on GitHub
https://github.com/MinkaiXu/GeoDiff/issues/4#issuecomment-1602047032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAOE47R2SJMDWWBADN2COVLXMPMNHANCNFSM5S3TVN2Q
.
You are receiving this because you commented.Message ID:
@.***>

When I run the code in my own new environment when I do not use the
environment you provided, the following error occurs：
[image: image.png]
I searched the Internet for many ways to try to solve this problem, and I
couldn't avoid this error.
zhuzhu wei @.***> 于2023年6月22日周四 13:56写道：

I'm very sorry, I'm a novice, I don't know much about this content yet,
except to reinstall CUDA, how can I make relevant code changes, I hope to
get your help.
Minkai Xu @.***> 于2023年6月22日周四 13:51写道：

oh, I see. it seems like older cuda is required, but I know this might be
too annoying...
Have you tried the things mentioned in this thread, about how to modify
the code?
—
Reply to this email directly, view it on GitHub
https://github.com/MinkaiXu/GeoDiff/issues/4#issuecomment-1602047032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAOE47R2SJMDWWBADN2COVLXMPMNHANCNFSM5S3TVN2Q
.
You are receiving this because you commented.Message ID:
@.***>

When I reinstalled CUDA, I found that the program could not run normally,
and I queried that I knew that I was using the RTX3090 graphics card, and
it seemed that I could only choose CUDA 11.0 or above, so I would like to
consult you on the running code and what the graphics card used is the
configuration. Looking forward to your response.
zhuzhu wei @.***> 于2023年6月22日周四 14:11写道：

When I run the code in my own new environment when I do not use the
environment you provided, the following error occurs：
[image: image.png]
I searched the Internet for many ways to try to solve this problem, and I
couldn't avoid this error.
zhuzhu wei @.***> 于2023年6月22日周四 13:56写道：

I'm very sorry, I'm a novice, I don't know much about this content yet,
except to reinstall CUDA, how can I make relevant code changes, I hope to
get your help.
Minkai Xu @.***> 于2023年6月22日周四 13:51写道：

oh, I see. it seems like older cuda is required, but I know this might
be too annoying...
Have you tried the things mentioned in this thread, about how to modify
the code?
—
Reply to this email directly, view it on GitHub
https://github.com/MinkaiXu/GeoDiff/issues/4#issuecomment-1602047032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAOE47R2SJMDWWBADN2COVLXMPMNHANCNFSM5S3TVN2Q
.
You are receiving this because you commented.Message ID:
@.***>


"Download .NET 5.0" docs page miss info about .NET 5.0 SDK version 5.0.411

On Download .NET 5.0 docs page latest described .NET 5.0 SDK vesion for Visual Studio 2019 16.11.x is 5.0.408.
I'm using latest Visual Studio 2019 16.11.18 and is has .NET 5.0 SDK 5.0.411.
Add all necessary missing info on that docs page please: when .NET 5.0 SDK 5.0.411 was released, which Visual Studio 2019 version it is included in, which .NET 5.0 Runtimes it has insude, etc.
Thank you.

@dcwhittaker can you check if we’re missing releases on the json files?

.NET 5.0.408 was the last public SDK. The corresponding values are correct on the website.

So the behavior is by design, so closing the issue,


Topics

Thanks for adding topics to your package!
Due to a bug, we were not validating the names on package upload. This has been fixed and will be enforced when publishing new versions.
The guidelines for choosing topic names is https://dart.dev/tools/pub/pubspec#topics. Concretely we do not allow underscores.
Could you please update your topics names in the pubspec?
Thanks in advance and sorry for the inconvenience.

Sure I'll fix that right away!

Fixed in v0.4.1


Add queue and queues(_:) helpers to QueueContext.

This allows for jobs to be dispatched from other jobs in the same way they're dispatched from a Request.

I think this is good but since we're introducing a new public protocol I want to get @tanner0101's input on it

@tanner0101 Yep sounds good. Updated.

@ileitch while we're at it and have an open PR, could you snag this log issue? https://github.com/vapor/queues/blob/master/Sources/Queues/QueueWorker.swift#L34 (notice the extraneous space + ':')

@ileitch while we're at it and have an open PR, could you snag this log issue? https://github.com/vapor/queues/blob/master/Sources/Queues/QueueWorker.swift#L34 (notice the extraneous space + ':')

Done. I also lowercased Job to match this log line: https://github.com/vapor/queues/blob/302a29b2b3410aac240908bc7995e20fead18459/Sources/Queues/Queue.swift#L85

Thank you! LGTM

@ileitch could you update the PR title and body to be formatted as release notes? Release bot will automatically tag a new release once merged. You can see examples here: https://github.com/vapor/queues/releases.

@ileitch could you update the PR title and body to be formatted as release notes? Release bot will automatically tag a new release once merged. You can see examples here: https://github.com/vapor/queues/releases.

Sure, updated.

Thanks!

These changes are now available in 1.1.0


Initial changes for LLVM 18 compatibility on macOS

I've made some minimal changes to get Nyxstone to build with LLVM 18 on macOS:

Adjusted find_package call to not specify the LLVM version. I think it's probably best to not force a specific LLVM version considering a new major release of LLVM is available roughly every 6 months.
Removed a similar version check from the Python bindings build script.
Pruned the results of llvm-config --ldflags, which returns multiple flags on my system, only the first of which is the needed '-L' flag.
Removed link arguments that are unknown on macOS.

Notable TODOs include:

Updating Rust bindings build script.
Probably other stuff?

If these changes look good and support for LLVM 18 is desired, I can go ahead and clean these up and test on other platforms; otherwise, I'll just use my fork for now.

Another notable TODO I just realized: updating the README.

I've merged this branch into #55, so that LLVM 18 will land for c++, rust, and python at the same time. Thank you for your work!


Arm64 macos binary

See https://github.com/cado-security/cloudgrep/issues/16

Looks like the performance difference is mostly the one-off cost for pyinstaller extracting to /tmp
python3 cloudgrep.py -b bucket -q error --debug  2.71s user 0.62s system 37% cpu 8.802 total
./cloudgrep -b bucket -q error --debug  2.50s user 1.01s system 29% cpu 11.877 total


Replaced webview with Live Preview extension

Previewing the coverage summary was lacking the CSS image files due to issues with webview security sandbox settings.  Removed all the webview code and used the Microsoft Live Preview extension to render the coverage summary file.  Code became much simpler, but introduced dependency on a 3rd party extension.
This PR should fix #250, #298, and many other closed PR's with CSS/image/javascript issues.
PR is loosely based on:

"How to call one extension from another"
Microsoft's Live Preview extension for VS Code, where the livePreview.start.internalPreview.atFile command is defined.

Apologies for not meeting all the contribution requirements.  This is my very first PR.
I've no idea how to run tests with node, nor how to use containers.  I've been learning JS/TS for about a week; it was just enough to make this work.
TODO:  package.json probably needs to be updated to show a dependency on the ms-vscode.live-server extension.
Anyway, the attached animated shows me press ctrl-shift-7 to enable gutter colorization, followed by ctrl-shift-6 to preview the coverage summary in a Live Preview window.

@ryanluker, the PR doesn't pass the builds.  The MacOS and Windows builds looks like they were cancelled.  The Ubuntu build is failing tests; I'm not the best person to write javascript test due to zero experience with javascript testing and a week's worth of javascript/typescript experience.

@vxdguy I took a bit of a look last weekend but forgot to post here that I almost had something working for the tests. I will tinker a bit more today and see where I get to around getting those cleaned up.

@vxdguy Should be all fixed now with these 3 commits, after you take a look I can approve, and we will get this merged in!
https://github.com/ryanluker/vscode-coverage-gutters/pull/363/commits/a4736fae52b893e13e06c6f59abb5ce15812ab36 https://github.com/ryanluker/vscode-coverage-gutters/pull/363/commits/46df75d002cb7342423ec3fd5ce545db36ccf39c https://github.com/ryanluker/vscode-coverage-gutters/pull/363/commits/51fa3e8c46b9a7c89929b1e193e6eb69c7fdebe0
One question around the live preview, I tried it out locally, and I assume this what the in IDE browser should look like?

@mattseddon Do you by chance know how to programmatically interact with the live preview editor, https://github.com/microsoft/vscode-livepreview?
I wasn't able to see it listed anywhere when I debugged locally (usually when you access the vscode.window you can see the text documents and make assertions. I was looking to add better assertions than just checking if the extension is active or not 🤔.
https://github.com/ryanluker/vscode-coverage-gutters/pull/363/files#diff-e11f5552a6417cfc03e85116d67d338dd473153531dcd834d80fa2a0a19bd72bL22-L24

https://github.com/microsoft/vscode-livepreview

👋🏻 . Webviews are a PITA to test and that's if you have access to the WebviewPanel that they are created inside. At least then you can easily test "Whether the panel is visible." and "Whether the panel is active (focused by the user).". It seems like there is no API exposed by ms-vscode.live-server so IMO you have two options for this assertion: // Look to see if the webview is open and showing preview coverage

Head down this rabbit hole: https://github.com/webdriverio-community/wdio-vscode-service
Close all of the editors at the start of the test with await commands.executeCommand('workbench.action.closeAllEditors') and then check window.visibleTextEditors and window.activeTextEditor after you've opened the preview. The inside of the webview will still be a black box though.

Hope this helps. LMK if you need any clarification or further details.
👍🏻

https://github.com/microsoft/vscode-livepreview

👋🏻 . Webviews are a PITA to test and that's if you have access to the WebviewPanel that they are created inside. At least then you can easily test "Whether the panel is visible." and "Whether the panel is active (focused by the user).". It seems like there is no API exposed by ms-vscode.live-server so IMO you have two options for this assertion: // Look to see if the webview is open and showing preview coverage

Head down this rabbit hole: https://github.com/webdriverio-community/wdio-vscode-service
Close all of the editors at the start of the test with await commands.executeCommand('workbench.action.closeAllEditors') and then check window.visibleTextEditors and window.activeTextEditor after you've opened the preview. The inside of the webview will still be a black box though.

Hope this helps. LMK if you need any clarification or further details.
👍🏻

Yeah I assumed it was PITA when I could find no way to interact with it programmically via the vscode.window or the getExtension helper 😢. Thanks as always @mattseddon 👋🏻!


error: attribute 'vscodeExtPublisher' missing

When trying to add extensions using this flake I'm seeing the error attribute 'vscodeExtPublisher' missing. I ran nix flake update last Friday, where I could build my configuration successfully. I tried using the example with the nix repl found here and the error is present there as seen below:
$ nix repl
Welcome to Nix 2.11.1. Type :? for help.

nix-repl> :lf .
Added 18 variables.

nix-repl> inputs.nix-vscode-extensions.extensions.x86_64-linux.vscode-marketplace.golang.go
error: attribute 'vscodeExtPublisher' missing

       at /nix/store/z8z0bjp8y8ah0qy1kwhgzhiklp0cqibq-source/flake.nix:42:52:

           41|                 }))
           42|                 (builtins.groupBy ({ value, ... }: value.vscodeExtPublisher))
             |                                                    ^
           43|                 (builtins.mapAttrs (_: lib.listToAttrs))

nix-repl> inputs.nix-vscode-extensions.extensions.x86_64-linux.open-vsx.golang.go
error: attribute 'vscodeExtPublisher' missing

       at /nix/store/z8z0bjp8y8ah0qy1kwhgzhiklp0cqibq-source/flake.nix:42:52:

           41|                 }))
           42|                 (builtins.groupBy ({ value, ... }: value.vscodeExtPublisher))
             |                                                    ^
           43|                 (builtins.mapAttrs (_: lib.listToAttrs))

nix-repl>

Looking through the commit history, it seems to be caused by the changes in https://github.com/nix-community/nix-vscode-extensions/commit/46be1e77328c79878e698dd075842c7552546007, since the line that is referenced in the error message was added in this commit.
I've unfortunately not had time to look into what could resolve this issue.
Please let me know if you need any additional information or I can help out in any other way. This flake is great and it's made it much easier for me to maintain my configuration, so I'll be happy to help out if I can.

I couldn't reproduce the error. I created this minimal flake:
{
  inputs = {
    nix-vscode-extensions.url = "github:nix-community/nix-vscode-extensions";
  };

  outputs = { ... }: {
    # None
  };
}

Then ran the same thing with nix repl and didn't get any error:
$ nix repl
Welcome to Nix 2.13.2. Type :? for help.

nix-repl> :lf .
Added 8 variables.

nix-repl> inputs.nix-vscode-extensions.extensions.x86_64-linux.vscode-marketplace.golang.go
«derivation /nix/store/0b2w4ak4xz8fm7zgxci7l2hsv765h7zb-vscode-extension-golang-go-0.37.1.drv»

nix-repl> inputs.nix-vscode-extensions.extensions.x86_64-linux.open-vsx.golang.go
«derivation /nix/store/plannn5mbpip1qzwc6bmgwmwr9xzxkaq-vscode-extension-golang-go-0.37.1.drv»

Can you please provide a minimal flake to reproduce the issue?

The issue occurs when you'll import the flake as an overlay. Please do not use REPL for debugging because it doesn't evaluate the outputs.overlays.default

The issue occurs when you'll import the flake as an overlay. Please do not use REPL for debugging because it doesn't evaluate the outputs.overlays.default
And obviously you can't reproduce the error if you're not touching the right code. Nix is a functional lazily evaluated language, that means it only launches the code only and only if it's concerned with execution by higher-level functions. It's probable that the @Scandiravian has overlay import in his dotfile, which is not accounted for in the report :D

@bppdddqqqq You're right - I'm using it as an overlay. I used the repl to reproduce the error, since it was difficult to create a concise description of the issue using my dotfiles.
Here's how to reproduce the issue using configuration files and home-manager
# flake.nix
{
  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-22.11";

    nix-vscode-extensions = {
      url = "github:nix-community/nix-vscode-extensions";
      inputs.nixpkgs.follows = "nixpkgs";
    };

    home-manager = {
      url = "github:nix-community/home-manager";
      inputs.nixpkgs.follows = "nixpkgs";
    };
  };

  outputs = { nix-vscode-extensions, nixpkgs, home-manager, ... }:
    {
      homeConfigurations = {
        "test-home" = home-manager.lib.homeManagerConfiguration {
          pkgs = nixpkgs.legacyPackages.x86_64-linux; # Home-manager requires 'pkgs' instance
          extraSpecialArgs = { };
          modules = [
            ./home.nix
            {
              nixpkgs.overlays = [
                nix-vscode-extensions.overlays.default
              ];
            }
          ];
        };
      };
    };
}

# home.nix
{ pkgs, ... }: {
  programs.vscode = {
    enable = true;
    package = pkgs.unstable.vscode;
    extensions = with pkgs.vscode-marketplace; [
      eamodio.gitlens
    ];
  };

  home.username = "test-user";
  home.homeDirectory = "/home/test-user";

  home.stateVersion = "22.11";
}

When running home-manager build --flake .#test-home it produces the error:
error: attribute 'vscodeExtPublisher' missing

       at /nix/store/z8z0bjp8y8ah0qy1kwhgzhiklp0cqibq-source/flake.nix:42:52:

           41|                 }))
           42|                 (builtins.groupBy ({ value, ... }: value.vscodeExtPublisher))
             |                                                    ^
           43|                 (builtins.mapAttrs (_: lib.listToAttrs))
(use '--show-trace' to show detailed location information)

Thanks @bppdddqqqq and @Scandiravian. Now I can reproduce the error. Will take a look.

I found the issue.
This flake uses nixpkgs/dbc68fa4bb132d990945d39801b0d7f2ba15b08f, which is a fairly recent version.
In this version, vscode-utils.buildVscodeExtension is defined as:
buildVscodeExtension = a@{
    name,
    src,
    # Same as "Unique Identifier" on the extension's web page.
    # For the moment, only serve as unique extension dir.
    vscodeExtPublisher,
    vscodeExtName,
    vscodeExtUniqueId,
    configurePhase ? ''
      runHook preConfigure
      runHook postConfigure
    '',
    buildPhase ?''
      runHook preBuild
      runHook postBuild
    '',
    dontPatchELF ? true,
    dontStrip ? true,
    nativeBuildInputs ? [],
    ...
  }:
  stdenv.mkDerivation ((removeAttrs a [ "vscodeExtUniqueId" ]) // {

    name = "vscode-extension-${name}";

    passthru = {
      inherit vscodeExtPublisher vscodeExtName vscodeExtUniqueId;
    };

    inherit configurePhase buildPhase dontPatchELF dontStrip;

    installPrefix = "share/vscode/extensions/${vscodeExtUniqueId}";

    nativeBuildInputs = [ unzip ] ++ nativeBuildInputs;

    installPhase = ''
      runHook preInstall
      mkdir -p "$out/$installPrefix"
      find . -mindepth 1 -maxdepth 1 | xargs -d'\n' mv -t "$out/$installPrefix/"
      runHook postInstall
    '';

  });

In your flake, you use the older nixpkgs/nixos-22.11.
In this version, vscode-utils.buildVscodeExtension is defined as:
  buildVscodeExtension = a@{
    name,
    src,
    # Same as "Unique Identifier" on the extension's web page.
    # For the moment, only serve as unique extension dir.
    vscodeExtUniqueId,
    configurePhase ? ''
      runHook preConfigure
      runHook postConfigure
    '',
    buildPhase ?''
      runHook preBuild
      runHook postBuild
    '',
    dontPatchELF ? true,
    dontStrip ? true,
    nativeBuildInputs ? [],
    ...
  }:
  stdenv.mkDerivation ((removeAttrs a [ "vscodeExtUniqueId" ]) // {

    name = "vscode-extension-${name}";

    inherit vscodeExtUniqueId;
    inherit configurePhase buildPhase dontPatchELF dontStrip;

    installPrefix = "share/vscode/extensions/${vscodeExtUniqueId}";

    nativeBuildInputs = [ unzip ] ++ nativeBuildInputs;

    installPhase = ''
      runHook preInstall
      mkdir -p "$out/$installPrefix"
      find . -mindepth 1 -maxdepth 1 | xargs -d'\n' mv -t "$out/$installPrefix/"
      runHook postInstall
    '';

  });

The difference is that passthru is not used in nixpkgs/nixos-22.11, so vscodeExtPublisher does not get passed.
But why does the overlay use vscode-utils from nixpkgs/nixos-22.11, and not nixpkgs/dbc68fa4bb132d990945d39801b0d7f2ba15b08f? Line 25:
utils = prev.vscode-utils;

The issue would be resolve by replacing this line with something like:
utils = nixpkgs.legacyPackages.x86_64-linux.vscode-utils;

Basically, using the nixpkgs input instead of prev. But for this to work, you also shouldn't do:
nix-vscode-extensions.inputs.nixpkgs.follows = "nixpkgs";

However, the problem with this approach is that I have thrown x86_64-linux in the mix. This should be ${system} but I don't know how to get ${system} in that context.
Any help on how to approach this would be appreciated.

@AmeerTaweel Thanks for taking a look at this, I really appreciate it!
https://github.com/NixOS/nixpkgs/commit/dbc68fa4bb132d990945d39801b0d7f2ba15b08f is a commit to the nixpkg master branch, so I'm curious if there's a reason for the flake using a commit from the master branch instead of either the stable or unstable branch (nixos-22.11 or nixos-unstable)?
I think that the nixos-22.11 that is referenced by my flake.lock is actually newer than https://github.com/NixOS/nixpkgs/commit/dbc68fa4bb132d990945d39801b0d7f2ba15b08f (that commit is from December, while my flake.lock points to a commit from this Monday in the nixos-22.11 branch)
Since the issue is caused by the nixpkg version of this flake pointing to a commit instead of a branch, I tried removing inputs.nixpkgs.follows = "nixpkgs"; from the nix-vscode-extensions in my configuration inputs
This throws a different error:
error: attribute 'toExtensionJson' missing

       at /nix/store/df977wnmxn0iv0nx0wngbplllix1zkvk-source/modules/programs/vscode.nix:38:19:

           37|
           38|   extensionJson = pkgs.vscode-utils.toExtensionJson cfg.extensions;
             |                   ^
           39|   extensionJsonFile = pkgs.writeTextFile {
(use '--show-trace' to show detailed location information)

Which I think is due to toExtensionJson only being in the master branch and not in stable branch yet.
I think most users will be using either stable or unstable nixpkg inputs, so to avoid others running into the same issue, would it be possible to change the input in this flake to either nixos-22.11 or nixos-unstable and then use nix flake update to keep it up to date in flake.lock?
I wrote this pretty hastily, as I have to go to a meeting in two minutes. If anything is unclear or non-sense, please let me know. I'll read through my post again later and try to fix it up :sweat_smile:

However, the problem with this approach is that I have thrown x86_64-linux in the mix. This should be ${system} but I don't know how to get ${system} in that context.

@AmeerTaweel If this is done in an overlay, ${system}, should be available like this
final: prev: {
    utils = nixpkgs.legacyPackages.${final.system}.vscode-utils;
}

Though I would still suggest changing to a stable branch as input for the flake as mentioned in my comment above :smile:

@Scandiravian Yeah I think we have to do both things.

Update the overlay:

nixpkgs.legacyPackages.${final.system}.vscode-utils;

Use nixos-unstable.

The first part is easy, but the second part I just want to check why it is the way it is right now.
@deemp is there any specific reason for:
nixpkgs.url = "github:NixOS/nixpkgs/dbc68fa4bb132d990945d39801b0d7f2ba15b08f";

I don't want to change it carelessly.

@AmeerTaweel , nope, that specific rev isn't required. Could you please apply the fixes that you've suggested?

@smkuehnhold I don't understand the issue. Even if our flake uses unstable this does not affect your main flake, it will still be on nixos-21.11. Can you elaborate?

@smkuehnhold I don't understand the issue. Even if our flake uses unstable this does not affect your main flake, it will still be on nixos-21.11. Can you elaborate?

Ah, I get it now. There is one thing I neglected to mention: I've specified nix-vscode-extensions.follows=system-nixpkgs basically (where system-nixpkgs is some version of nixos-21.11 that my system uses). I guess it was my mistake to assume the original poster had done the same? 🤔
As for why I do this, it's really just hygiene. It is my preference to not depend on more than one version of nixpkgs unless otherwise necessary. My guess now is that this flake falls into the latter case? If so, that's a little annoying (to me) but understandable.
Thanks for the clarification @AmeerTaweel 👍

@smkuehnhold I actually do use "follows", but as I use a mix of packages from nixos-22-11 and nixos-unstable, I configured the extensions flake to follow the unstable one instead.


Cannot implement in angular 10

ERROR in node_modules/ng-stripe-checkout/src/stripe-checkout.module.d.ts:1:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.
This likely means that the library (ng-stripe-checkout) which declares StripeCheckoutModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

Hi,
Have you seen this issue? It is related. Thank you.
https://github.com/westphalen/ng-stripe-checkout/issues/8


Static rendering all the routes, even the parameterized ones

This is my exploration into the idea of static rendering all the routes such that they can be served in a totally language agnostic way. This is of course easy to do already for routes with no route params, but not so simple for the parameterized routes.
Why would I want to pre-render a parameterized route, where all the data comes from the clientside XHR call? Aren't I just prerendering a blank page? Not at all my friend, you prerender as much as you can which would typically include at least the global nav bar. Having that appear instantly instead of merely quickly upon hydration makes all the difference in giving your site an app-like feel.
And in my case it's especially important since I'm not using client-side routing, so each page load needs to be as fast-feeling as possible. Why no client-side routing? Imagine a large site with 1000 pages, an in-house project spanning many years and having many separate teams. Building this as a single app is bound to result in slow build times, so you can split it up into 10 Svelte projects where each has 100 pages (all behind a reverse proxy). But as long as you're splitting it at all it makes sense to just split it completely with full page reloads on every transition. Now you can reproportion ownership fluidly as you see fit, and most importantly, you can iteratively migrate page by page to some new framework. Perhaps whatever the hot framework of 2025 is. This a whole separate topic I could say a lot about but let's leave it at that.
So anyway, the '*' you pass to kit.prerender.pages only does the parameterless routes. A first attempt at this might be to add another route in there that has garbage for the param since it won't even be looked at from the serverside, and updating your code that runs onMount to only look at window.location instead of the page store.
I put together a repo to try out some ideas, at https://github.com/johnnysprinkles/static-all-the-things
Setup
The first commit is just setting things up with a small constellation of services to make a more realistic prod-like setup. There's SvelteKit, there's a simple API server, and there's a web server that serves the adapter-static compiled assets off of disk. Just to ensure we have a complete break between build time and runtime the web server is written in Python. Could be anything (for me it'll probably be Java or Kotlin), but all the matters is it's not Node.
On the SvelteKit side I added two routes related to airplanes, one is a parameterless List page, and one is a detail page that has an [id] in its route.

https://github.com/johnnysprinkles/static-all-the-things/commit/b06f612a31b4009e5a44a4b05b97f7c7cffd37f1
This example just gives you a 404 for the parameterized routes.
First pass
https://github.com/johnnysprinkles/static-all-the-things/commit/3be17a2a84147cdc516f83c756fd72ebe021ce65
  pages: [
    '*',
    '/airplane/XXX',
  ],

This manually adds preprender paths with garbage for the parameters, and it does work. I can run it and my dynamic pages function. It's all hacked up and manual though, we can do better.
First attempt at interpolating
We'd really like to keep using the store, which should be a source of truth for route params and other request-specific data, instead of going around it to inspect the window.location. So instead of passing garbage for the params when server-side rendering, what about if we pass something meaningful? Such as just the param name in square brackets? (I know, this is kind of overloading the meaning of square brackets, but it's just a start).
If we do that, we can just have the web server replace e.g. [id] with the actual ID. A hacked up and manual version of this is in:
https://github.com/johnnysprinkles/static-all-the-things/commit/5ed2e708ec1a355788b8bfb9deb24ff70d51b8e2
  pages: [
    '*',
    '/airplane/[id]',
  ],

More automated way of interpolating
We can tidy things up a bit by taking advantage of the manifest.js file, which knows both the names of all the route params (in JS comments) and the regexes that match, e.g.
export const routes = [
    // src/routes/index.svelte
    [/^\/$/, [c[0], c[2]], [c[1]]],

    // src/routes/networking/addresses/list.svelte
    [/^\/networking\/addresses\/list\/?$/, [c[0], c[3]], [c[1]]],
    ...

So the next version of this reads and parses that:
https://github.com/johnnysprinkles/static-all-the-things/commit/22e3e98149876364d8a4317e9557f727e2287021
It would be nice if we had routes presented in a language agnostic way, such as a routes.json file that lives next to the manifest. A possible feature request.
Once we have that we can fill in the page store via regex slice and dice. This would be a little easier if the page store data was pulled out of that structure (and also perhaps surrounded by special comment tokens). So for example we currently get this:
<script type="module">
  import { start } from "/./_app/start-aec04e6a.js";
  start({
    target: document.querySelector("#svelte"),
    paths: {"base":"","assets":"/."},
    session: {},
    host: location.host,
    route: false,
    spa: false,
    trailing_slash: "never",
    hydrate: {
      status: 200,
      error: null,
      nodes: [
        import("/./_app/pages/__layout.svelte-1240a5ff.js"),
        import("/./_app/pages/airplane/[id].svelte-a58c7efe.js")
      ],
      page: {
        host: location.host, // TODO this is redundant
        path: "/airplane/[id]",
        query: new URLSearchParams(""),
        params: {"id":"[id]"}
      }
    }
  });
</script>

But if it were more like this it would be easier for any language that can emit JSON to fill it in:
<script type="module">
  let pageStoreData = /** PAGE_STORE_START **/ {
    host: location.host,
    path: "/airplane/[id]",
    queryString: "",
    params: {"id":"[id]"}
  }/** PAGE_STORE_END **/;

  import { start } from "/./_app/start-aec04e6a.js";
  start({
    target: document.querySelector("#svelte"),
    paths: {"base":"","assets":"/."},
    session: {},
    host: location.host,
    route: false,
    spa: false,
    trailing_slash: "never",
    hydrate: {
      status: 200,
      error: null,
      nodes: [
        import("/./_app/pages/__layout.svelte-1240a5ff.js"),
        import("/./_app/pages/airplane/[id].svelte-a58c7efe.js")
      ],
      page: {
        host: pageStoreData.host,
        path: pageStoreData.path,
        query: new URLSearchParams(pageStoreData.queryString),
        params: pageStoreData.params
      }
    }
  });
</script>

So that's where things are at now, this will be an ongoing exploration.

It's not clear to me what you're requesting. Do you have a concise way of stating it? Parameterized routes are currently prerendered, but must be either linked to or specified as an option

Yes, parameterized routes are pre-rendered but that works best for a set of known values. Pre-rendering routes that have wildcard values where the values aren't known until request time isn't that well supported at the moment. It can be done but requires some fairly ugly parsing of the HTML artifacts. I think there might ultimately be 3 feature requests to make it smoother:

Exposing the routes from manifest.js as a JSON file
Factoring the page store data from the start() call out to make it easier to replace at runtime, and/or inherit from a global variable
Some new special syntax for the kit.prerender.pages array, something similar to the '*' but to specify to prerender all parameterized routes with placeholders.

It may be the case that what I'm trying to do is so uncommon that it doesn't belong in SvelteKit but in some other framework built on Svelte. Wanted to see if there's any interest.

Also this server-side interpolation into the HTML file, that is only one way to approach it. It could just include a copy of the route parsing logic in there. Then you could still serve your HTML files off a CDN and enjoy routes with placeholders. So in your start() call instead of:
  page: {
    host: location.host, // TODO this is redundant
    path: "/airplane/[id]",
    query: new URLSearchParams(""),
    params: {"id":"[id]"}
  }

You might have essentially a slice of the manifest that relates to that particular route, i.e. the regex with capture groups, and list of positional route param names. So like:
  page: {
    host: location.host, // TODO this is redundant
    path: location.pathname,
    query: new URLSearchParams(location.search),
    params: parseFrom(location.pathname),
  }

I need to make a branch on my demo repository and explore this.
I don't want to add to your open bug count, you can resolve this if you want, people can still find it in the history.

This seems over-complicated. You just need to create a directory page which generates a link for each parameter value

The values are infinite though.

Or I should say arbitrarily large, and constantly changing.

Basically I've got this pretty sweet prototype I'm building, it's way way faster than our extra-large Angular app even though it's doing full page reloads on every transition. I'm currently just serving it with npm run preview, but thinking about how I'm going to actually productionize it.

I'm on discord as "jpsimons" just FYI.

You can't prerender an infinite number of pages because the pretenders process would never end. You can prerender arbitrary / changing pages though by generating the links in the directory page accordingly

I'm trying to pre-render one page, but one page that's parameterized, where the parameter is filled in at runtime from the path.

If you can provide a list of all possible values of the parameter from a database or some other source you can prerender that page. If there are an infinite / arbitrarily large number of possible values and you cannot provide a list then you can't prerender now and never will be able to with any software because that's impossible.

Sorry I think I'm explaining more but not explaining better... these are pages that have no load() function, all data is fetched from the client-side. But all the surrounding bits of the page that aren't data fed can be pre-rendered so they pop in immediately, as fast as the browser can deserialize HTML and turn it into DOM, which is effectively instantly. I might have a global nav, some kind of subnav, a left nav bar, maybe a footer, and definitely the spinner. The spinner will reset itself upon hydration, but hopefully that will be resolved after a roll forward discussed in https://github.com/sveltejs/svelte/issues/4308

Ok. So just prerender that page then. I don't understand what the problem is. This whole thread is indecipherable to me. You might try asking for help on Discord instead

Ohhh, I think I finally figured out what you're trying to say. You want to prerender a page where the route parameter is not used in load but only client-side?

Exactly, my write-up was too wordy! Pre-rendering with [TODO] deferred values, deferred until runtime.

So I made up a scheme for it, and wanted to share, but it could be more streamlined and more integrated into SvelteKit if we wanted. The one thing that makes me nervous is the svelte file path in the manifest.js is just in comments, I need those and hope they don't go away.

This thread is really long and confusing. I'm going to close it and file a new issue referencing this one with a clearer

Hey guys, I came across a similar problem. For me routing on production does not even work, if I refresh the page. However, on dev it works.
Here is the setup (sliced)
filestructure
.
├── __error.svelte
├── index.svelte
├── __layout.svelte
├── shop
│   ├── [accessory].svelte
│   └── index.svelte
├── [...slug].svelte

As you can see, I am using a wildcard route [...slug] on the first directory level. It might conflict with shop sometimes, but thats just a side note for now.
[...slug] takes the "path" of a page and queries its content from a headless cms. When building with adapter-static build/_app/pages/[...slug].svelte-*.js was generated. This way the routing does not work.
When creating the routes manually (slug1, slug2...), they get properly generated in build folder and routing works on production
Here you can check the behavior

Goto https://ari-motors-v2.vercel.app/
Click on "ARI Personenfahrzeuge"
->  url changes to https://ari-motors-v2.vercel.app/ari-personenfahrzeuge and content loads
Refresh the browser
-> url stays the same, but content of / was loaded

Is there a way to work around this, somehow specifying the routes somewhere?
I really can't add all the routes as files manually, which the content creators create and they a changing constantly.
Even if I did, one change in these files would cause me to do the work on all  page files.
My two cents on the topic
Did you think about crawling the site for links you could possibly prerender? Like

Fetch and prerender /
Which links can I find here? -> Found /en
Let's try to prerender /en -> 200 ok, nice
Which links are on /en? Man, that will take some time, luckily I am a computer.

To be fair with you, build time will drastically increase. However that's not a big deal for me personally.

What does your kit.prerender.pages look like? If your slugs are constantly changing, keep mind that you can still pre-render of course but any parts of the page that are data-fed by request specific information will have to be client-rendered. If the page in its entirety is data-fed by request specific params, probably no point in static pre-rendering at all.
I'm a little unclear on your ultimate hosting solution. If it's Vercel, why not use adapter-vercel instead of adapter-static? adapter-static would be for a simple static file server, or as I'm pushing forward, a completely custom server runtime (the latter of which would allow query string, path params, rest params, etc).

Hi, thanks for your reply.
As you already hinted, adding the routes to kit.prerender.pages solved the prerender/routing problem.
svelte.config.js
    prerender: {
      crawl: true,
      enabled: true,
      force: false,
      pages: [
        "*",
        "/ari-personenfahrzeuge",
        "/elektrotransporter-ari-901/kofferaufbau",
        // other routes generated in [...slug]
      ],
    }

To answer you questions:
I am using a headless cms, where some content creators create pages/posts. These are the routes that constantly change.
As there is no data that changes at runtime adapter-static should get me the best results. Furthermore, I only want to publish new posts, when the site builds.
adapter-vercel seems to SSR at runtime on vercel functions.
Personally, I am a fan of using the things as they are meant to be, so I would prefer not to build a custom server runtime.
Just out of curiosity, the the config states crawl: true, so why wasn't /ari-personenfahrzeuge prerendered? The link is in the menu load()ed at build in __layout.svelte.
Nonetheless the config works absolutely fine. I'd love a function in future, which crawls links from pages and prerenders them.
However, I don't want to complain for svelte kit already is the best SSG and svelte is the fe framework so far. :)

I think I understand... new pages come into existence constantly, but you only them to be published on the next build/deploy? And you don't want to have to list them all out in the pages array, you want them to be found by crawling? I suspect you found a bug, and that the use of rest params in the path is confusing the system?

I'd try this just to test: Add a parameterized route without rest params, such as /elektrotransporter-ari-901/[name].svelte and update your code to look at 'elektrotransporter-ari-901/' + page.params.name instead of just page.params.slug, and see if that is crawlable, just to compare with the rest params case.

Maybe crawling stops at routes with params in them, by design, to avoid pre-rendering your entire database. Maybe you also aready mentioned such in your description, I should read more carefully. Sounds like we might want a new option for crawlAllowDynamicRoutes or something.

I think I understand...

Yes, that's right. The bug I found was in regards to routing, when loading the page first. I assume you differentiate routing on first page load and when clicking a relative link on the site. So refreshing the page in the browser did load the wrong page content, even when the url stayed correct.

I'd try this just to test:

I did. Seems like only rest params cause the problem.

Maybe crawling stops at routes with params

In my case, I really want to prerender to entire database :D, or lets say all the pages/posts.
I'd like crawlAllowDynamicRoutes.

To be honest, I expected crawl: true in the config to behave, as crawlAllowDynamicRoutes. Since it crawls in order to build the static site, it is to be expected that all links that are encountered are rendered.
If someone doesn't want to pre-render the entire database, one should set the pages to be rendered in the config.prerender.entries. It's simpler to config a couple of pages that need to be rebuilt (or need to be built for the first time), than to list the whole content of a database (which may be thousands of pages).
These are my two cents from reading the documentation, as I can't find this problem mentioned anywhere in the docs.

To be honest, I expected crawl: true in the config to behave, as crawlAllowDynamicRoutes. Since it crawls in order to build the static site, it is to be expected that all links that are encountered are rendered.

This! In my case I'm trying to set up a simple blog that renders pages based on markdown files.
I really expected crawl to pre-render all  linked pages, which it doesn't. I agree sometimes it would not be a good idea to render a whole database of entities, but there are cases where this would be greatly beneficial (I could have a completely static blog with a fantastic build process!).

So I was actually thinking more about rendering a generic version of a dynamic route, and actually this literally just came up again at my current employer... I want to use adapter static to spit out some html files and an _app folder that I can drop in an existing web server setup (in my case it's Java/Dropwizard/Maven). You can actually pull this off just fine by adding a prototypical example for each parameterized route in pages, i.e.
pages: [
  '*',
  '[id]'
]

Then do a little URL rewriting in your web server, something like:
<rewrite>
  <from>^\d+$</from>
  <to>/[id]/index.html</to>
</rewrite>

The downside here is the realtime path params won't come through in the page store params, but you can simply inspect location.pathname yourself. However... if you're navigate from say /123 to /456 it won't tear down and reconstruct your view, so really do need to do everything in the just recently added afterNavigate instead of onMount. I'd actually like to write a guide about all this stuff sometime.

so this is still a thing to be done?
i am new to svelte/svelteKit, did a little research on other frameworks (gatsbyjs for example) and seek for the ability to create static pages from dynamic routes.
i too thought the crawl option would unfold all those dynamic routes [page].svelte to static html pages based on the result of an api result.
is there any solution to that?
a different adapter?
other settings/options on kit.prerender?
any help is appreciated

You need to either link to each page somewhere within your app so that it will be crawled or you need to list each page in the prerender.entries option: https://kit.svelte.dev/docs#configuration-prerender

@benmccann
i have an api route to fetch users (using faker.js - older version; not 6.6.6)
the result of that list is used by module load() in my index.svelte route and links each entry as a detail page using a dynamic route [user].svelte
the second api [user].js fakes additional data for that user.
this data is again used by module load() in my [user].svelte route
npm run dev works perfectly fine, prefetching does its thing and data is shown on the list and user page. all fine.
but npm run build only renders my list page.
including the correct links to the detail pages for each user -> so crawling should do its thing, but no detail page is statically created)
you mentioned to add prerender.entries
which entries?

my user list route? - that one is created
my dynamic route for the detail page? - how?
each user page (i don't know as this is dynamically built)?

maybe i have a missconception of what adapter static and prerender does...
i wanted to test the capabilities of sveltekit to do SSG.

You would need to file an issue and provide a code repository that reproduces the issue. I'm not sure why crawling wouldn't work for you

Why is this closed? Now it is impossible to create a static page with dynamic params. I think it is not uncommon that you don't know your data on build time.

If I get it correctly and the problem is the same as mine:
You have a route users/ that is supposed to be static, and a database of users that is dynamic and is fetched on the frontend, and you want to be able to able to navigate to uses like users?user_id=80085, but you dont want to prebuild the users endpoints. But the build fails because you cannot use the url.searchParams for prerendered routes.
After very much research, I came to the solution to catch the error and return empty userId instead:
  export async function load({ url }) {
    try {
      return { props: { userId : url.searchParams.get('user_id } };
    } catch (e) {
      return { props: { userId: '' } };
    }
  }

That way the path is properly build and can be visited properly in both user\ and user\42
What else I tried and failed or didn't work for me:

use path params like user/[id].svelte and then query like user/313. Hydration works fine but you cannot go directly to user/313 since it doesn't exist
use hash params. You have to do add an event listener for the onhashchange and handle the reactivity yourself, also the history was kind of broken, it would push two states instead of one upon navigation.

I'm not quite sure I understand... users in your example is pre-rendered so it's an HTML file sitting in your /build folder? In that case you'd need to do any "infiinitely broad aka parameterized" loading client-side i.e. onMount. You could actually have a mix of data that's fetch at pre-render time, such data wouldn't change very often since it only updates when you redeploy static assets, and dynamic data fetch that's done client-side.
I think your first bullet point is on the right track... although in my case at my current employer, our build/deploy system chokes on square brackets, maybe having something to do with bash escaping, so I used underscores instead. As far as going directly to users/313 that's up to your web server to figure out, adapter-static lets you "bring your own server".

@johnnysprinkles If you have a completely static site and no power over the server then you would just get a 404 on users/313 because it won't exist in the file system, users?user_id=313 would work though because the users/index.html would be there. As for the users/ url, it is up to you how you handle the page without a user_id.
I created a PR that should work on your example: https://github.com/johnnysprinkles/static-all-the-things/pull/1
I didn't run it but I trust it should work.
But anyway, I think that using the searchParams shouldn't be forbidden, it should be handled as if the params are empty and give a warning to the developer, or at least the option to give a default value.

Oh I see, your web server is just a simple CDN so yeah, path params aren't an option. But your CDN will probably wildcard route all query-string suffixed URLs to the same filename. In that case, why use load() at all? Why not simply examine window.location.search from onMount?

Oh maybe I see what you're saying, url passed to load() is clientside runtime dynamic unlike the page store? Let me investigate.

You cannot access searchParams onMount, it throws an error on prerender. You can though ( I found out later ) condition if the code is running on the browser or on prerender: https://kit.svelte.dev/docs/modules#$app-env and do the same thing I did with the try/catch but with an if(prerendering)
import {  prerendering } from '$app/env';
 export async function load({ url }) {
    if(!prerendering) {
      return { props: { itemId : url.searchParams.get('id') } };
    } else {
      return { props: { itemId: '' } };
    }
  }

And then render a placeholder page if there are no params.
And as you already said, the pages are indeed in a CDN so it should be just dump static html pages.

I have read through all of the answers. Is there any update on this one? I have a folder structure like this:
─ src
── blog
─── +page.svelte
─── [blog_post]
──── +page.svelte
The thing is I have 0 references to blog_post page in blog page because in the blog page I get active blog posts from an API.  I create links through slugs of the blogposts. Like "example.com/blog/blog-about-something". The problem I am having is when I run static generation it has 0 references to blog posts page because blogs page is generated dynamically on client side as well.
I want to generate my navbar, footer and other elements statically and use my custom js fetch function to fill the blog post data. When I run the build it says crawling was unable to find references to blog_post page. If I add a reference like "" it finds the page but when I change the test post slug I get 404, which is expected. What I need is something like "blog/*" so I can serve same page all the time for anything that comes after "blog/". I can use "window.location" to complete my fetch function and if it is not found I can show my own 404. Only thing I want is to get my navbar, footer and other elements to be prerendered.
Sorry if this diverges from the main post of this thread but I think we have same problem.


Is it possible to invoke AAD auth/Oauth secured Azure function from Dynamics CRM plugin using webhook?

Looking for inputs or confirmation about the possibility on this topic.
No problem with public Azure function (open HTTP trigger) or accessing using function key. Whereas AAD secured is throwing 401-forbidden response. https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/357955/how-to-connect-to-azure-function-which-is-configured-for-azure-active-directory-authentication-from-dynamics-crm/940630
It is becoming repeat ask in community. https://stackoverflow.com/q/64179051/7920473

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

ID: 42dbdb06-f634-7af2-8054-eef3c9ae49db
Version Independent ID: dea28d93-ba3b-1020-77ca-f03b2a4773ef
Content: Register a webhook (Common Data Service) - Power Apps
Content Source: powerapps-docs/developer/common-data-service/register-web-hook.md
Service: powerapps
GitHub Login: @JimDaly
Microsoft Alias: jdaly

This is a known challenge which Web Hooks doesn't even attempt to address. Your options are limited.
So this is a feature request rather than a documentation issue.
If you attempt to call such an authenticated service using an HttpClient in a plug-in, you have more options. But none of them today represent best practices that we would recommend specifically at this time, although I see people making them work in community posts. Setting a certificate or secret value within the secure configuration of the plug-in seems to be the best solution I've seen. But we are looking to provide something better.


Generalize assertion for crypto unit tests [1.2.x]

Purpose
This is to make sure the tests are passing in both Travis and GitHub actions. Suspect the issue is due to the JDK version mismatch. The objective of the test cases are still valid.
This is a duplicate of PR https://github.com/ballerina-platform/ballerina-lang/pull/23155 which is sent to master branch.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #24042 into ballerina-1.2.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.2.x   #24042   +/-   ##
================================================
  Coverage            14.59%   14.59%
================================================
  Files                   51       51
  Lines                 1411     1411
  Branches               219      219
================================================
  Hits                   206      206
  Misses                1189     1189
  Partials                16       16

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 fc808fa...a0514bd. Read the comment docs.


Add changelog for the v0.11.1 release and update docs

What this PR does / why we need it:

Add changelog for the v0.11.1 release
Update recommended KubeOne version to v0.11.1
Update recommended Terraform version for AWS to v0.12.10

Tentatively, the plan is to release today (April 7th).
Special notes for your reviewer:
Docs PR: https://github.com/loodse/docs/pull/295
Does this PR introduce a user-facing change?:
NONE

/assign @kron4eg
/hold

/retest

/hold cancel

/cherrypick release/v0.11


[Task] Documentation for git sync related flows

SubTasks (TODO)

[ ] #8898

@Pranay105 can we close this now?


Tracing WG Meeting 2015-11-19

Date/Time: Thu Nov 19, 1:00PM eastern world time
Availablity in doodle: http://doodle.com/poll/vhfikus96esxyhhw
Agenda and minutes can be collected in here and copied into this repo later:
https://docs.google.com/document/d/1pudpZjdQ9onVKrjmlJzkxhBzkhjqOVxkX82i9biZtFY/edit?usp=sharing
Previous minutes: https://github.com/nodejs/tracing-wg/blob/master/wg-meetings/2015-10-07.md
Hangout on air for active participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYfuw8P_UiXnDp2gvtQ43RsOD5Ou2NxbFwb3uhUAEFzBdX2RBA?hl=en
YouTube movie for observers and saved recording: http://www.youtube.com/watch?v=vxY_OLHF66A
Hangout on air event for more details: https://plus.google.com/events/cso6u3m03mcqr0nan52d4epbcfc
Agenda discussion can happen in this thread.
(format loosely copied from https://github.com/nodejs/LTS/issues/38)
(instructions for creating Hangouts On Air on the nodejs/node wiki)

@nodejs/tracing - I've created this issue to track stuff for the next meeting in November.  A doodle is available to indicate your availability.
I'll post another reminder about the next meeting, in about two weeks.

Added

AsyncWrap

Open question: is error recovery of relevance and what are the use cases
see Trevors comment in nodejs/node#669

to the agenda.

@nodejs/tracing - the doodle has 6 names on it - Patrick Mueller, Thomas Watson, Matthew Loring, Ali Sheikh, Sam Roberts, Sanjeev Koranga - and the following date winners so far:

Tue, Nov 10, 1PM eastern
Wed, Nov 18, 1PM eastern

The first date - and a bunch of other dates on the doodle - I can't make, but I'm not critical, except for my mad HoA skillz.  I can teach someone though. :-)
Rest of you peeps, please doodle!

I've thrown my name and times in there, but all I'm interested in joining for is to get some feedback for this issue, which could probably be sorted in the comments: https://github.com/nodejs/tracing-wg/issues/34
Thanks :-)

The Wednesday time doesn't work great for me, but I can change some plans, if need be. I'd rather do that than miss out on the excellent facilitation of @pmuellr. :smile_cat:

@nodejs/tracing -
Looks like Thu Nov 19, 1:00PM eastern - world time - is the winner with 9, with only @skoranga (Sanjeev Koranga) not able to make it.
Unless I hear otherwise, will update all the things tomorrow, create the hangout, etc.

@nodejs/tracing -
I've updated the first comment with the details for the meeting. I believe you can get a GCal invite by visiting the "Hangout on air event" link above, but it's difficult for me to test that myself.  If anyone has problems, please comment here.  Maybe I hit a button wrong.
I'll be away from keyboard for most of the next two weeks, back in time for the hangout.  Until then, carry on!

@nodejs/tracing - reminder of the WG call tomorrow - see the first comment of this issue for call info

I've posted the meeting minutes in a PR - https://github.com/nodejs/tracing-wg/pull/35 - could someone review, and if ok, merge?  Happy to add material ...

Finally got the minutes from the last minutes posted - sorry for the delay.
https://github.com/nodejs/tracing-wg/blob/master/wg-meetings/2015-11-19.md


Subnets demo app documentation

Repo: https://github.com/hirosystems/subnet-demo-app
New How-to guide:

[] Add a How-to guide to use the Subnet demo app.
[] Add a link to the demo video: https://www.youtube.com/watch?v=FHKf-9C0LoI.
[] Add a screenshot of the Clarinet integrate command output for block 9.
[] Add prerequisites "clarinet latest version is required".

Update the existing readme:

[] Add the following lines to the top of the readme.
The project demonstrates some of the capabilities of subnets through a simple hypothetical NFT marketplace where minting, listing and offers happen on L2. This demo app showcases how to mint NFTs, list, transfer, and withdraw them from the subnet back to the mainchain. This is a demo application made to illustrate how wallets, exchanges and developer teams can leverage subnets in their applications.
[] Add a link to the demo video: https://www.youtube.com/watch?v=FHKf-9C0LoI

Perhaps add this demo under https://docs.hiro.so/example-apps instead of the Subnets product page.

https://github.com/hirosystems/subnet-demo-app/pull/1

Closing this issue as the readme is updated in the PR:https://github.com/hirosystems/subnet-demo-app/pull/1.


GADRewardedAd's userDidEarnRewardHandler never called.

I have discovered a bug using version 9.9.0
GADRewardedAd's userDidEarnRewardHandler is never called, despite user watching ad to completion.
Ad loading snippet 👇
let request = GADRequest()
GADRewardedAd.load(withAdUnitID: testAdUnit, request: request, completionHandler: { [weak self] (ad, error) in
    if let error = error {
        print("❌ Failed to load rewarded ad with error: \(error.localizedDescription)")
    } else if let ad = ad {
        self?.rewardedAds.append(ad)
        print("✅ Rewarded ad loaded.")
    }
})

Ad presentation snippet 👇
let ad = rewardedAds.removeFirst()
ad.fullScreenContentDelegate = self
ad.present(fromRootViewController: vc) {
    print("✅ Did watch ad!")
    didWatchAd()
}

Proof reward callback should have fired 👇

Result is that ✅ Did watch ad! is never printed to the console.
Let me know if there is any other information that may be helpful!

I was able to resolve the issue myself, perhaps this is the intended behavior.
My issue was that I did not hold a reference to the GADRewardedAd object as it was playing.


I don't know if it is a boug but if it is a boug i don't know if it is really is

Hello dear mister Luk-f,
I'am really insteresting in playing your game "10-mille" so i have installed python in my computer to test this wondérfoul program.
Ahém .. I launched the program by typping "python main.py" in my favorite terminal (S) stop me now if i am wrong.
It seems that there is no dice module at line 1 column 8 of your file dix_mille.py in folder 10-mille-main situed in _C:\Users\zebest\Downloads_ on my computer.
Hummmmm it is really really strange because i've never heard soemeone playing "10-mille" with no dice "module" right ? Stop me now if i am rond.
Anyway, sorry for being such a trompette, can't wait to play this wondérfoul (wondérfoulon if i can say, muahahah)
game.
I wish you zebest

If i can say even if my username is qbouchon i am not quentin bouchon from nautibus, this is just a coïncidence ofcourse

If i can say even if my username is qbouchon i am not quentin bouchon from nautibus, this is just a coïncidence ofcourse

You didn't answer to the post i did 4 minutes ago and i rélly want to play now ...

Well well well  if i can say

If i can say even if my username is qbouchon i am not quentin bouchon from nautibus, this is just a coïncidence ofcourse

Oh okay fortunately you clarified it bikoz I had a doubt until then...

You didn't answer to the post i did 4 minutes ago and i rélly want to play now ...

Okay my crew of canniballs developers takes care of hôle
XOXO

Have u try this branch : https://github.com/luk-f/10-mille/tree/test_pygame ?
Maybe better...

Why You Do This To ME ?
I forgot about this game and now you remind me i rélly rélly want to play it EXCEPT that there is NO dice module even on branch https://github.com/luk-f/10-mille/tree/test_pygame . Why the dices would be on  a tree anyway ?

Dou u have check requirements file ?

YES YES YES ! You are very right !
It WASN'T a Boug ! It was ze REQUIRIMENTE Files !!!
I am so Happy i can play this wonderfoul game !! And i am very good if i can say

Oh what a pleasure Doude !!
Do you want collaborate with me to dziss projekt ?? I am searching a new binome since the last one left to do drougs.
Thk a lot & garonne, XOXO


[BUG] Transparency not handeled correctly

Describe the bug
System setup:

Wallpanel used to display Grafana Dashboard.

Grafana dashboard (black background by default) contains an iframe for weather forecast.

Weather forecast widget is provided by https://www.meteoblue.com/de/wetter/widget/setupthree/obergrossegg_schweiz_11579273

Bug:
Since the last update of wallpaper the transparency-setting ist not handeled properly. The background remains white. Although everything else on the site is dark.
To Reproduce
Use an iframe in Grafana and set it to transparency.
Theory to occurring bug
I think a dark mode of the wallpanel itself (not just settings UI) would solve the problem. The recent upgrade to Grafana 8 may brought changes to CSS-handling which may have an influence on this issue.
Smartphone (please complete the following information):

Device: Samsung Galaxy Tab A7
OS: Android 11
Applicaiton version 0.9.5 build 6

But WallPanel does nothing with the webpage CSS or code.  WallPanel has it's own dark mode, not sure if this is changing the default background of WebView component, but I think its' up to your webpage to handle background color.


[bug] cannot get the balance through the method "getBalance"

Use the method "importAddress" to import the address as a watch wallet, but cannot get the balance through the method "getBalance"
Dogecoin Core version
v1.14.5/dogecoin-1.14.5-x86_64-linux-gnu.tar.gz
Machine specs

OS:  Linux version 4.14.123-111.109.amzn2.x86_64
CPU: 8
RAM:
Disk size: 500G
Disk Type (HD/SDD): SSD

Hi!
Did you specify the rescan (3rd) parameter when you did importaddress?
dogecoin-cli importaddress "<script>" "<label>" <rescan> <p2sh>

If you set it to false then you would need to do a manual rescan.
PS: I'm marking this as bug while we triage this because @chromatic is anyway working on the "import" RPC endpoints in #2942, so we can give some extra love & care to this one :-)

Hi!
Did you specify the rescan (3rd) parameter when you did importaddress?
dogecoin-cli importaddress "<script>" "<label>" <rescan> <p2sh>

If you set it to false then you would need to do a manual rescan.
PS: I'm marking this as bug while we triage this because @chromatic is anyway working on the "import" RPC endpoints in #2942, so we can give some extra love & care to this one :-)

Thanks for the reply.
Yes, I set rescan=false because if rescan=true it will take a long time and block other requests. My business scenario is that any address can return the balance, is there any rpc API that can meet my business requirements? Even indirect implementation is possible

So currently, you would want to add this address before you publish it for your business rather than after. In that case, you don't need to rescan. This is the cheapest option. Is it possible to implement this? Another option would be to just rescan a small number of blocks, which is what mentioned PR #2942 will enable for you.
Indirectly, you can use one of the overlay block exploring softwares out there (i.e. something like https://github.com/trezor/blockbook) that index the blocks processed by Dogecoin Core.
In the future, I'm looking to bring back the functionality from 1.10.0's experimental Dogeparty release, that allowed you to index every transaction for every address on the chain. I have the feature ported in concept but I do not think this is cost-efficient to introduce on 1.14 at this time, so I'm looking at post-1.21 for this.

Hi!!! i have wallet id and password https://dogechain.info/wallet but i dont have email. I did not connect 2FA. How do i go to the site? thanks for the answer

Kindly follow the step on this link to talk to the customer service directly on your issues
https://direct.lc.chat/14201793/

Use the method "importAddress" to import the address as a watch wallet, but cannot get the balance through the method "getBalance"
Dogecoin Core version v1.14.5/dogecoin-1.14.5-x86_64-linux-gnu.tar.gz
Machine specs

OS:  Linux version 4.14.123-111.109.amzn2.x86_64
CPU: 8
RAM:
Disk size: 500G
Disk Type (HD/SDD): SSD

Same issue I have but my address is of same default wallet, when I do [ dogecoin-cli getbalance "*" 0 true ]  I get total balance of wallet but When we do getbalance or (dogecoin-cli listtransactions “address” )  of specific address then we are getting zero. If we check same address on explorer then it shows there on explorer.
here is output when we do getbalance of specific address
( ubuntu@ip-172-31-14-216:~/dogecoin$ dogecoin-cli getbalance nZKufSPqXztZkeaoNouDknGrqg4tLwsbvV
0.00000000 )


[DEFECT]

Thank you for the defect report

[X] I am using the latest version of RAVEN.
[X] I have read the Wiki.
[X] I have created a minimum, reproducible example
that demonstrates the defect.

Defect Description
SamplePlot produce plots with overlapping x-labels and misaligned y-labels
Steps to Reproduce
Any example with:

SOURCENAME
VARIABLENAME

Expected Behavior
Expected xlabel to not be covered and ylabels to be aligned
Screenshots and Input Files

OS
Windows
OS Version
No response
Dependency Manager
CONDA
For Change Control Board: Issue Review

[ ] Is it tagged with a type: defect or task?
[ ] Is it tagged with a priority: critical, normal or minor?
[ ] If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

[x] If the issue is a defect, is the defect fixed?
[x] If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Change is exclusively visual. Approved to close via #1759.

Might be good to edit a working title for this issue as well for future reference.


ssh keys

Need to deal with ssh keys for deployments. Right now you have to copy them in by hand.  There should be a more elegant way.

Next version uses deployment keys. For now just copy you pk into your instance
docker copy ~/.ssh /home/developer/


[11.x] Fix normalizedNameCache

The wrong attribute was referenced in the PR https://github.com/laravel/framework/pull/51158
https://github.com/laravel/framework/blob/5d4b26edcd1e9ac91c8452fa93de77502bec4b78/src/Illuminate/View/Factory.php#L100-L105

Thanks!

Thanks @Jubeki


[BUG] v2.1.4 Cannot override variables

Describe the bug
Cannot override variables, whatever security enabled or not.
To Reproduce
Steps to reproduce the behavior:

Import flow from old version
Enable override for the variable
Make request

Expected behavior
Override success
Screenshots
If applicable, add screenshots to help explain your problem.

Flow
If applicable, add exported flow in order to help replicating the problem.
Setup

Installation docker
Flowise Version: 2.1.4
OS: Linux
Browser chrome

Additional context
Add any other context about the problem here.

Do you have a simple flow for me to test? are the variables used in custom tool or other places? chatflow or agentflow

ExportData.json
docker run -it --rm --name flowise -p 3000:3000 flowiseai/flowise

# Import data

curl http://localhost:3000/api/v1/prediction/479d9db3-9606-40e6-b78c-bd4405a87931 \
     -X POST \
     -d '{"question": "Hey, how are you?", "overrideConfig": {"vars":{"test":"overrided"}}}' \
     -H "Content-Type: application/json"

Fixed now in main branch, will update to new Docker version soon!


Migrate k3s.io website to CNCF owned neutral organization

My understanding as per the website guidelines is that this is migration is not strictly required. However, we still want this to happen. The website is an important part to K3s and should get migrated. CNCF already owns the domain, we just haven't moved the project yet :)
While the k3s.io website is open and can be updated today, and while there doesn't appear to be any requirement to move the website itself to a CNCF owned neutral organization, I would still like to transfer the project over to k3s-io so its in a more logical place and thus easier for the community to make any necessary updates.
This will involve transferring the https://github.com/rancherlabs/k3s-website project over to https://github.com/k3s-io/k3s-website

Linking as related to https://github.com/rancher/k3s/issues/2189 effort.

Per @cjellick follow the pattern for website that other OSS projects are using

We've done this on our end, just waiting on DNS now


[PE-D][Tester B] Scroll bar is invisible in dark mode

The timetable interface has a scroll pane, but it's not visible. Which can be problematic in the following scenario:
(small window size):

(large window size):

The schedule in 15:00-18:00 was hidden to the user. The indication of a scroll pane is not clear in dark mode. This is not an issue in light mode, see:

Labels: severity.Low type.FunctionalityBug
original: Berted/ped#10

Fixed


API store allows registering applications with case insensitive duplicate names

Description:
In API store, users are allowed to register applications with case insensitive duplicate names.
Suggested Labels:
product-scenarios

This was fixed in the latest versions


Peercoin, Waiting for daemon to come online

Description
[ppc1] Waiting for daemons to come online ...
Steps to Reproduce
ppcoin.conf
server=1
rpcuser=peercoinrpc
rpcpassword=
port=9902
config.json
{             // DON'T change the id after a production pool has begun collecting shares!             "id": "ppc1",             "enabled": true,             "coin": "peercoin",             // Address to where block rewards are given (pool wallet)             "address": "PX4irVmJah2tkr3j2LBNPiPB8EsYvRDQbN",             // Block rewards go to the configured pool wallet address to later be paid out             // to miners, except for a percentage that can go to, for examples,             // pool operator(s) as pool fees or or to donations address. Addresses or hashed             // public keys can be used. Here is an example of rewards going to the main pool             // "op"             "rewardRecipients": [                 {                     // Pool wallet                     "address": "PX4irVmJah2tkr3j2LBNPiPB8EsYvRDQbN",                     "percentage": 1.5                 }             ],             // How often to poll RPC daemons for new blocks, in milliseconds             "blockRefreshInterval": 400,             // Some miner apps will consider the pool dead/offline if it doesn't receive             // anything new jobs for around a minute, so every time we broadcast jobs,             // set a timeout to rebroadcast in this many seconds unless we find a new job.             // Set to zero to disable. (Default: 0)             "jobRebroadcastTimeout": 10,             // Remove workers that haven't been in contact for this many seconds.             // Some attackers will create thousands of workers that use up all available             // socket connections, usually the workers are zombies and don't submit shares             // after connecting. This features detects those and disconnects them.             "clientConnectionTimeout": 600,             // If a worker is submitting a high threshold of invalid shares, we can             // temporarily ban their IP to reduce system/network load.             "banning": {                 "enabled": true,                 // How many seconds to ban worker for                 "time": 600,                 // What percent of invalid shares triggers ban                 "invalidPercent": 50,                 // Check invalid percent when this many shares have been submitted                 "checkThreshold": 50             },             // Each pool can have as many ports for your miners to connect to as you wish.             // Each port can be configured to use its own pool difficulty and variable             // difficulty settings. 'varDiff' is optional and will only be used for the ports             // you configure it for.             "ports": {                 // Binding port for your miners to connect to                 "3053": {                     // Binding address (Default: <IP_ADDRESS>)                     "listenAddress": "<IP_ADDRESS>",                     // Pool difficulty                     "difficulty": 0.02,                     // TLS/SSL configuration                     "tls": false,                     "tlsPfxFile": "/var/lib/certs/mycert.pfx",                     // Variable difficulty is a feature that will automatically adjust difficulty                     // for individual miners based on their hash rate in order to lower                     // networking overhead                     "varDiff": {                         // Minimum difficulty                         "minDiff": 0.01,                         // Maximum difficulty. Network difficulty will be used if it is lower than                         // this. Set to null to disable.                         "maxDiff": null,                         // Try to get 1 share per this many seconds                         "targetTime": 15,                         // Check to see if we should retarget every this many seconds                         "retargetTime": 90,                         // Allow time to very this % from target without retargeting                         "variancePercent": 30,                         // Do not alter difficulty by more than this during a single retarget in                         // either direction                         "maxDelta": 500                     }                 }             },             // Recommended to have at least two daemon instances running in case one drops             // out-of-sync or offline. For redundancy, all instances will be polled for             // block/transaction updates and be used for submitting blocks. Creating a backup             // daemon involves spawning a daemon using the "-datadir=/backup" argument which             // creates a new daemon instance with it's own RPC config. For more info on this,             // visit: https:// en.bitcoin.it/wiki/Data_directory and             // https:// en.bitcoin.it/wiki/Running_bitcoind             "daemons": [                 {                     "host": "<IP_ADDRESS>",                     "port": 9902,                     "user": "peercoinrpc",                     "password": "<hidden>",                     // Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin                     // Family daemons. Using this is highly recommended. The value of this option                     // is a string that should match the value of the -zmqpubhashblock parameter                     // passed to the coin daemon. If you enable this, you should lower                     // 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.                     //"zmqBlockNotifySocket": "tcp://<IP_ADDRESS>:15101",                     // Enable streaming Block Notifications via WebSocket messaging from Ethereum                     // family Parity daemons. Using this is highly recommended. The value of this                     // option is a string that should  match the value of the --ws-port parameter                     // passed to the parity coin daemon. When using --ws-port, you should also                     // specify --ws-interface all and                     // --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"                     // If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0                     // to disable polling entirely.                     "portWs": 18545,                 }             ],             // Generate payouts for recorded shares             "paymentProcessing": {                 "enabled": true,                 // Minimum payment in pool-base-currency (ie. Bitcoin, NOT Satoshis)                 "minimumPayment": 0.01,                 "payoutScheme": "PPLNS",                 "payoutSchemeConfig": {                     "factor": 2.0                 }             }         }
Expected behavior
[ppc1] All daemons synched with blockchain
Actual behavior
[ppc1] Waiting for daemons to come online ...

I was able to fix the issue by restart vps and re-run donet Miningcore.dll -c nuconfig.json

hasLegacyDaemon:true


Feature: Integrate to work with Prometheus and Grafana

Describe the solution you'd like
If Prometheus or Grafana is already deployed and used in the users' environment, it will be helpful if we can export the security data to the central place as metrics, so that it won't be necessary to make users switch between multiple portals.

Close this due to duplicate


Nickname does not work for 2 conditions

Expected Behavior
      "nickname_above_iv": 0.8,
      "nickname_above_cp": 1500,

Expecting all pokemon above 1500 cp OR above 0.8 iv to be nicknamed
Actual Behavior
Only pokemon above 0.8 iv nicknamed. Regardless of CP. (below 1500 also nicknamed if iv>0.8
{
"type": "NicknamePokemon",
"config": {
"enabled": true,
"nickname_above_iv": 0.8,
"nickname_above_cp": 1500,
"nickname_template": "{iv_pct}-{attack_code}-{name}",
"nickname_wait_min": 3,
"nickname_wait_max": 5
}
},

nickname_above_cp is not supported by NicknamePokemon task.

In that case, this please reopen as feature request

Please resubmit as feature request.


docs(root): Expand testing guidance including stackblitz project

Summary of the changes
The pull request aims to expand the testing guidance documentation, including a StackBlitz project for practical testing.
Key Changes:
Added testing documentation: Includes a testing component demonstrating how to test components using Jest, React Testing Library, and Cypress.
CodePreview Component: Added to show code examples.
StackBlitz Button: Added to the testing documentation for users to test the code in a StackBlitz environment.
Related issue
Design system 1008

The lack of PR description is making it difficult for me to review this. I can see that there's 'showStackblitzBtn' in the new ComponentTesting component, but it's not set to true and i'm not sure when it's planned.
Even looking at the ticket (https://github.com/mi6/ic-design-system/issues/1008) i'm not sure if the button should be active.

The lack of PR description is making it difficult for me to review this. I can see that there's 'showStackblitzBtn' in the new ComponentTesting component, but it's not set to true and i'm not sure when it's planned.
Even looking at the ticket (#1008) i'm not sure if the button should be active.

The SB button in the Cypress guidance is currently disabled as it requires a new window/port to run the tests, which the SB sandbox does not currently support. If this changes we can, without much hassle, set it to true to allow the running of tests in the new window.


Not working with iPython/Jupyter

Python 3.5.0 |Anaconda 2.4.0 (x86_64)| (default, Oct 20 2015, 14:39:26)
[GCC 4.2.1 (Apple Inc. build 5577)]
I tried the first code example in a Jupyter/iPython notebook cell:
import matplotlib.pyplot as plt
import numpy as np
from mpldatacursor import datacursor

data = np.outer(range(10), range(1, 5))

fig, ax = plt.subplots()
lines = ax.plot(data)
ax.set_title('Click somewhere on a line')

datacursor(lines)

plt.show()

I've run pip install mpldatacursor and done kernel -> restart from Jupyter notebook.
Executing the cell, the plot displays correctly but it is noninteractive. Clicking a line does not do anything.
EDIT: just found https://github.com/joferkington/mpldatacursor/issues/12
Adding %matplotlib nbagg does produce something working, although it gives the error:
/Users/pi/anaconda/lib/python3.5/site-packages/IPython/kernel/init.py:13: ShimWarning: The IPython.kernel package has been deprecated. You should import from ipykernel or jupyter_client instead.

"You should import from ipykernel or jupyter_client instead.", ShimWarning)*

What backend are you using?
You'll have to use %matplotlib nbagg to have interactive figures in an IPython notebook.
Otherwise, the inline backend generates static .png's.  There's no way for any interaction to happen with the the inline backned.

Sorry, I just found the relevant issue. I've updated the above report.

To maintain compatibility with older versions of IPython, matplotlib's nbagg backend has to use mechanisms that are depreciated in the latest versions of IPython.  Therefore, you're seeing a warning related to that.
It's unavoidable, but can be safely ignored.

PS Could this %matplotlib nbagg information be provided in the main readme, under the setup section? A lot of iPython/Jupyter users out there now...

@p-i-: That's a good point! I'll add it to the readme tonight.
I'm going to re-open this issue as a reminder to myself.

Not sure whether to open a new issue for this.
For my imshow I'm getting x,y readout. But not the value. And the readout is to the bottom right outside of the image. It doesn't look at all similar to the images in the readme.

I like the readout to be here, but how to get the value? That's what I really need!

The readout you're seeing is the standard matplotlib readout, not
mpldatacursor's.
Did you click on the plot and not get an annotation popping up?  If so, I'm
a bit stumped. Try removing the display='single', maybe...
On Tue, Nov 10, 2015 at 5:10 PM, Pi<EMAIL_ADDRESS>wrote:

Not sure whether to open a new issue for this.
For my imshow I'm getting x,y readout. But not the value. And the readout
is to the bottom right outside of the image. It doesn't look at all similar
to the images in the readme.
[image: pi- 2015-11-10 at 23 08 29]
https://cloud.githubusercontent.com/assets/693495/11078825/195d5718-8800-11e5-8537-1d4810dea8bd.jpg
I like the readout to be here, but how to get the value? That's what I
really need!
—
Reply to this email directly or view it on GitHub
https://github.com/joferkington/mpldatacursor/issues/48#issuecomment-155597120
.

What version of mpl are you using?  There is a strange mix of the new color map and old styling of the nbagg close button.

1.4.3 -- I manually copied across Viridis from https://github.com/BIDS/colormap/blob/master/colormaps.py

You really should not copy code around ad-hoc like that, it leads to a reproducibility nightmare.

@tacaswell, I haven't yet got round to supplying a reproducible problem.  But maybe now is the right time.

%matplotlib nbagg

import matplotlib.pyplot as plt
import numpy as np
from mpldatacursor import datacursor

data = np.array([1,2,3])

fig, ax = plt.subplots()
im_ax = ax.imshow( np.array([ data ]) )
datacursor(im_ax)
plt.show()

That exact example works fine for me on mpl 1.5.0 and IPython 4.0.0, at least on Linux.  I can't try it on Windows or OSX, at the moment.
Maybe there's an OSX-specific problem?

I am on:
Python 3.5.0
Anaconda 2.4.0 (x86_64)| (default, Oct 20 2015, 14:39:26)
IPython 4.0.0

OSX 10.11.1 (15B42)

My setup could probably be replicated by using a fresh Anaconda installation (I only installed anaconda under a week ago)

I just submitted matplotlib/matplotlib#6030 which fixes an issue with the datacursor for me in matplotlib 1.5.1 with mpldatacursor 0.6.2

I have rendering issues using the nbagg backend. However I have thought of making a html image map and use plain javascript to add/render divs. I would actually like to interact between two charts, meaning clicking on one changes the other. This could be done by using the notebook kernel as demonstrated in this gist. Here one could either render a tooltip (or anything using plain javascript) or execute any arbitrary python code i.e. like interactive ipywidgets are doing.
Since I am working heavily on my own open source module I have priorities and can't promise anything. But if I have some time I would appreciate a hint if I could produce such an image map using existing functionality of mpldatacursor and where I should start looking at / hooking into.

%matplotlib nbagg did not work with jupyter-lab for me, I had to use %matplotlib widget (requires installing it and nodejs)

@p-i-  Not sure if you have resolved the problem. I am using mplcursors instead and it works for me on OSX.


Feature/atrayano/wildcard

Description

This is a beta version of a new feature (requested by Harvard) to enable wildcard expansion in History
Related Issue

Motivation and Context

Simplifies syntax in History by allowing regex expressions
How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)

Checklist:

[x] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

Made a mistake. Should NOT merge to master