Running Grover's algorithm fails with "aer_simulator_statevector" backend

Environment

Qiskit Terra version: 0.19.1
Python version: 3.8.5 (probably irrelevant)
Operating system: macOS 12.1

What is happening?
Running Grover's algorithm fails with the latest version of qiskit (with "aer_simulator_statevector" backend):
  File ".../python3.8/site-packages/qiskit/algorithms/amplitude_amplifiers/grover.py", line 242, in amplify
    max_amplitude_idx = np.where(circuit_results == max_amplitude)[0][0]
IndexError: index 0 is out of bounds for axis 0 with size 0

How can we reproduce the issue?
The following minimal example is adapted from:
https://github.com/Qiskit/qiskit-terra/blob/a2b9a9b13ab76974cd5509ff6f693c5dec9cc351/test/python/algorithms/test_grover.py#L258-L265
The main change is in setting the backend to "aer_simulator_statevector".
from qiskit import Aer
from qiskit.algorithms import AmplificationProblem, Grover
from qiskit.circuit.library import PhaseOracle

backend = Aer.get_backend("aer_simulator_statevector")

oracle = PhaseOracle("x1 & x2 & (not x3)")
problem = AmplificationProblem(oracle, is_good_state=oracle.evaluate_bitstring)
grover = Grover(quantum_instance=backend, iterations=2)
result = grover.amplify(problem)  # fails here
assert result.oracle_evaluation
assert "011" == result.top_measurement

What should happen?
The code should work as in the previous versions (qiskit 0.33.0, qiskit-terra 0.19.0).
Any suggestions?
The problem is in the Grover.amplify method:
https://github.com/Qiskit/qiskit-terra/blob/a2b9a9b13ab76974cd5509ff6f693c5dec9cc351/qiskit/algorithms/amplitude_amplifiers/grover.py#L228
circuit_results is sometimes a numpy.ndarray object (as in the tests) and sometimes a qiskit's Statevector object, but the code doesn't differentiate between these cases, and when it is a Statevector it fails here:
https://github.com/Qiskit/qiskit-terra/blob/a2b9a9b13ab76974cd5509ff6f693c5dec9cc351/qiskit/algorithms/amplitude_amplifiers/grover.py#L241-L242

I cannot reproduce this error with Terra 0.19.1 and Aer 0.9.0. What version of Qiskit Aer do you have installed?

My qiskit-aer version is 0.10.2 (the latest release)

It's caused by Aer 0.10 - that changed the type saved by save_statevector etc to the qiskit.quantum_info classes, with a compatibility layer that mostly should have meant that they behaved like Numpy arrays.  In this case, though, the Statevector.__eq__ method returns a single Boolean, rather than broadcasting like general Numpy arrays.  It's a simple fix - we just need to cast the output of get_statevector to a Numpy array if we want to use it with guaranteed Numpy semantics.

I believe #7560 sorted this. In any case QuantumInstance usage by Grover is now deprecated and soon to be removed in favor of using a Sampler primitive. Since I believe this is well outdated I am going to close it.

Seems I got distracted and ended up not closing this despite saying I was! 🤦♂


learning rate can't update in resuming training with hovorod

🐛 Bug
When I resumed training the model with LearningRateMonitor, the LR written in the log won't update anymore but just keep the same with original status of the ckpt file.
To Reproduce
import os
import torch
from torch import nn
import torch.nn.functional as F
from torchvision.datasets import MNIST
from torch.utils.data import DataLoader, random_split
from torchvision import transforms
import pytorch_lightning as pl
from pytorch_lightning.callbacks import LearningRateMonitor
import horovod.torch as hvd

class LitAutoEncoder(pl.LightningModule):
    def __init__(self):
        super().__init__()
        self.encoder = nn.Sequential(nn.Linear(28 * 28, 128), nn.ReLU(), nn.Linear(128, 3))
        self.decoder = nn.Sequential(nn.Linear(3, 128), nn.ReLU(), nn.Linear(128, 28 * 28))

    def forward(self, x):
        # in lightning, forward defines the prediction/inference actions
        embedding = self.encoder(x)
        return embedding

    def training_step(self, batch, batch_idx):
        # training_step defines the train loop. It is independent of forward
        x, y = batch
        x = x.view(x.size(0), -1)
        z = self.encoder(x)
        x_hat = self.decoder(z)
        loss = F.mse_loss(x_hat, x)
        self.log("train_loss", loss)
        self.log("lr", self.optimizer.param_groups[0]['lr'])
        return loss

    def configure_optimizers(self):
        self.optimizer = torch.optim.Adam(self.parameters(), lr=0.01)
        # self.optimizer = hvd.optimizer.DistributedOptimizer(self.optimizer)
        lr_scheduler = torch.optim.lr_scheduler.CosineAnnealingWarmRestarts(optimizer=self.optimizer, T_0=10, T_mult=2, eta_min=0)
        return [self.optimizer], [lr_scheduler]

def main():
    dataset = MNIST(os.getcwd(), download=True, transform=transforms.ToTensor())
    train, val = random_split(dataset, [55000, 5000])

    autoencoder = LitAutoEncoder()
    lr_monitor = LearningRateMonitor(logging_interval='step')
    trainer = pl.Trainer(
        gpus=1,
        max_epochs=64,
        strategy='horovod',
        callbacks=[lr_monitor],
        limit_train_batches=32
        )
    trainer.fit(autoencoder, DataLoader(train), DataLoader(val), ckpt_path='lightning_logs/version_14/checkpoints/epoch=4-step=63.ckpt')

if __name__ == "__main__":
    main()

Expected behavior
Use the MNIST as an example, train it from scratch and save a model in middle.
Then pass the model path to trainer to resume train the model.
Now check the log in tensorboard, you can see the lr-Adam won't update.
But for the 'lr' we write in log , it is normal.
And it will be normal when the strategy is 'ddp' or with the version 1.4.2 of pytorch_lightning.

If anyone has any suggestion, please kindly let me know! Thanks a lot!
Environment

PyTorch Lightning Version (e.g., 1.5.0):1.5.4
PyTorch Version (e.g., 1.10):1.10.0
Python version (e.g., 3.9):3.7.11
OS (e.g., Linux):Linux
Horovod version:0.23.0
MPI version:3.0.0
CUDA version:11.1
NCCL version:2.7.8

Additional context
but I found that if I use the old way to define the distributed optimizer by uncomment the line below, then it will update the learning rate normally.
def configure_optimizers(self):
        self.optimizer = torch.optim.Adam(self.parameters(), lr=0.01)
        # self.optimizer = hvd.optimizer.DistributedOptimizer(self.optimizer)

cc @awaelchli @rohitgr7

I am currently seeing a similar issue with my LightningModule w/ LearningRateCallback. Using torch.optim.Adam and any optimizer, I am unable to see my learning rate plotted or changed in any way during training.
def configure_optimizers(self):         """Called to configure the trainer's optimizer(s)."""         optimizer = Adam(self.parameters(), lr=self.lr, weight_decay=self.weight_decay)         scheduler = construct_scheduler(optimizer, self.scheduler_type, self.lr, self.warmup, self.num_epochs)         return {             'optimizer': optimizer,             'lr_scheduler': {                 'scheduler': scheduler,                 'monitor': self.metric_to_track,                 'frequency': self.trainer.check_val_every_n_epoch             }         }

I am currently seeing a similar issue with my LightningModule w/ LearningRateCallback. Using torch.optim.Adam and any learning rate scheduler, I am unable to see my learning rate plotted or changed in any way during training.

@amorehead with horovod?

@rohitgr7,
Actually, with DDP. I found that the issue only showed up when I returned a dictionary containing my optimizer and lr_scheduler keys.

Any progress here? same issue

here:
    def configure_optimizers(self):
        self.optimizer = torch.optim.Adam(self.parameters(), lr=0.01)
        # self.optimizer = hvd.optimizer.DistributedOptimizer(self.optimizer)
        lr_scheduler = torch.optim.lr_scheduler.CosineAnnealingWarmRestarts(optimizer=self.optimizer, T_0=10, T_mult=2, eta_min=0)
        return [self.optimizer], [lr_scheduler]

the scheduler is configured with interval='epoch' by default. ref: https://pytorch-lightning.readthedocs.io/en/latest/common/lightning_module.html#configure-optimizers
and learning rate monitor is by step.
lr_monitor = LearningRateMonitor(logging_interval='step')

Possibly that's why its not updating the lr and lr monitor just shows the same lr for that epoch in all the steps.
can anyone share a reproducible script using: https://colab.research.google.com/github/PyTorchLightning/pytorch-lightning/blob/master/pl_examples/bug_report/bug_report_model.ipynb
thank you!


Single Device prefetch_to_device

prefetch_to_device is great when doing distributed training, but can be a hassle for non-pmap use cases since you need to add then remove a dummy sharding dimension at the front. A convenience function to prefetch data onto the device in single GPU training would be helpful.
Also, prefetch_to_device returns ShardedDeviceArrays instead of DeviceArrays. Is there a difference, or are the two interchangeable? Thanks in advance!

Hi @n2cholas -- very sorry for the late reply! I'll rope in @jheek who has thought about this much more carefully.

@jheek is this something we are still planning on doing?

I'll close this for now, users can already "prefetch" something to a single device using jax.device_put. The use case seems somewhat niche and prefetching is mostly handled automatically or manually through JAX APIs these days.

Hi @n2cholas ,
Do you have any working code that can use prefetch_to_device with single GPU? My dataset comes from TFDS and I am struggling with how to add the dummy dimmension for prefetch_to_device.
I created a thread here. I'd be much appreciated if you can share some experiences over there.
Thanks!

@davidshen84 after profiling a bit, I found that prefetching would not help much for my use case. Have you tried calling .batch() twice on your TFDS (first time with the batch size, second time with batch_size=1 i.e. 1 device)? e.g. https://github.com/n2cholas/progan-flax/blob/main/src/main.py#L41-L43


Can't download the Service definition when clicking the Download button

Description:

When trying to download the service definition from the service catalog service, it shows an UI error alert.
Steps to reproduce:

Go to the services by clicking the services Icon in the left menu
Click Add sample and deploy the sample service.
Go to the overview of the service and click the download button.

Affected Product Version:

APIM 4.1.0 pre alpha
Environment details (with versions):

OS:
Client:
Env (Docker/K8s):

Optional Fields
Related Issues:

Suggested Labels:

Suggested Assignees:

Fixed with https://github.com/wso2/apim-apps/pull/179


feat: add clientConfig to from verb

- What I did

Send at_client version to server

- How I did it

Pass the client version via the clientConfig in AtLookupImpl in the RemoteSecondary.

- How to verify it
- Description for the changelog

@gkc: Updated the pubspec.yaml with a comment. and changed the e2e test atSign from ce2e4 to ce2e2 because ce2e4 runs on a prod version of at_secondary_server. So, the e2e tests are failing because the changes related to clientConfig are not yet released into Prod. I will a new PR with having tests guarded with version checking to support cross version testing.


FEATURE: Implement Local Storage for todo items

Description
Currently, the todo items are being stored in an array. Reloading the page clears this array.

New to do items should be pushed to the browser local storage so that closing the page does not clear the saved items

Screenshots
No response

I can solve this issue, could you please assign this to me?

Sure, go ahead
Tee
On Mon, Oct 3, 2022, 22:03 ROHIT RANJAN SINGH @.***>
wrote:

I can solve this issue, could you please assign this to me?
—
Reply to this email directly, view it on GitHub
https://github.com/slim-codes/todo/issues/11#issuecomment-1266046107,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARHI433RVB2JALX3XCVT5JDWBNC2PANCNFSM6AAAAAAQ36POUA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Allow phone numbers to contain country codes and limit the max length

I think it is fair to consider this as a bug since Phone only checks that the string provided is all numeric. Please let me know your thoughts on whether this is a bug.

I think it is reasonable to limit the max length of phone number, else the tester can enter a very long number and the display will be cut off in the app. As for country code, sorry for my bad english, are you saying that if it is a bug to allow the phone numbers to contain country codes or we should allow phone numbers to contain country code?

Yea I agree with @ryanlml that adding country codes counts as a feature. Limiting the length might be fine though.

Thanks for the inputs! I guess we can add the appropriate warnings in the user guide. What do the rest think about limiting the length of phone number?


How to use HashToG1 with frontend.Variable

Hello,
I'm a beginner with gnark and I am wondering how I can use hashToG1 with a frontend.Variable type. This functions seems to take bytes as input.
Thank you in advance.
Hamza

Can you post an example circuit what you are trying to do?
NB! It seems to be a question about gnark usage, I'm converting the issue to discussion.


Add rule in order to detect certificates (issue #572)

Description:
Solves the issue https://github.com/zricethezav/gitleaks/issues/572
Build a custom docker image and scanned a file and found it:
time="2021-10-08T08:02:55Z" level=warning msg="leaks found: 1"

Checklist:

[x] Does your PR pass tests?
[ ] Have you written new tests for your changes?
[x] Have you lint your code locally prior to submission?

This PR should not be merged as it would cause false positives. As a certificate is not a secret.

See related issue.


Add sql

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
Description
[Please include a brief description of the changes or features added]
Type of PR

[ ] Bug fix
[ ] Feature enhancement
[x] Documentation update
[ ] Security enhancement
[ ] Other (specify): _______________

Screenshots / Videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have followed the code style guidelines of this project.
[x] I have checked for any existing open issues that my pull request may address.
[x] I have ensured that my changes do not break any existing functionality.
[x] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[x] I have read the resources for guidance listed below.
[x] I have followed security best practices in my code changes.

Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Resources for Guidance
Please read the following resources before submitting your contribution:

[x] Code Harbor Hub Community Features
[x] Docusaurus Documentation
[ ] React.js Documentation
[x] Markdown Guide
[ ] MDX Documentation
[x] Mermaid Documentation

Resources for DSA Features on Our Site:

[x] Tabs: Switch Languages
[x] Line Numbering
[x] Math Equations

Contribution Guidelines
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
Issue Creation

Limit on Issues:

Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

Basic Contributions:

This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
For these tasks, issues will be assigned the level1 label.

Acknowledging Hard Work:

If a contributor puts in significant effort on a task, the issue will be upgraded to level2. This is our way of recognizing and appreciating extra effort.

Feature Additions and Component Work:

Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

Level1:

Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.

Level2:

Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.

Level3:

Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!
#1777 ADDED SQL Commands And Diving Deeper into SQL: Beyond the Basics with examples
Kindly comment if any changes needed
Fix https://github.com/CodeHarborHub/codeharborhub.github.io/issues/1777

Kindly comment if any changes needed
Fix https://github.com/CodeHarborHub/codeharborhub.github.io/issues/1777


Crash with minetest 5.3

Describe the bug
When I place a not empty 64k storage tablet, it crash.
When I dig a terminal, it crash, to.
After restarting, a part of the stuff contained in the tablet diseapeared.
Log
2021-01-03 16:02:48: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod 'microexpansion' in callback nodemeta_inventory_OnPut(): ...9/.minetest/mods/microexpansion/modules/network/init.lua:39: bad argument #1 to 'equals' (userdata expected, got nil)
2021-01-03 16:02:48: ERROR[Main]: stack traceback:
2021-01-03 16:02:48: ERROR[Main]: 	[C]: in function 'equals'
2021-01-03 16:02:48: ERROR[Main]: 	...9/.minetest/mods/microexpansion/modules/network/init.lua:39: in function 'insert_item'
2021-01-03 16:02:48: ERROR[Main]: 	.../.minetest/mods/microexpansion/modules/storage/drive.lua:338: in function <.../.minetest/mods/microexpansion/modules/storage/drive.lua:323>

Desktop (please complete the following information):

Minetest version: 5.3

@theFox6 Are you able to fix? It is really annoying, I cant use this mod on my private server.

Could you check if this is still a problem in the latest version and send me new log outputs?

ok no problem

I will be in vacation soon and I will got the time xD

It is strange, I cant reproduce with mt 5.4 on my main pc
I will retest on my server (5.4 now) and send you the log.

Can pipeworks cause the crash? On my server I had pipeworks but I tested without on my pc.

I may have fixed it at some point, I just wanted to know if you still have this problem. If not then you can close the issue.


go live

Docs Build status updates of commit 83e82b6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.gitignore
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

msteams-platform/.vs/ProjectSettings.json
:white_check_mark:Succeeded

msteams-platform/.vs/VSWorkspaceState.json
:white_check_mark:Succeeded

msteams-platform/.vs/msteams-platform/v16/.suo
:white_check_mark:Succeeded

msteams-platform/.vs/slnx.sqlite
:white_check_mark:Succeeded

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/cafe-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/flow-bot.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/flow-help.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/polly-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/tab-onenote-config.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/tab-planner-config.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/tab-sp-config.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/tab-sp.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/web-sp.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/faq/wideidea.png
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/calls-meetings-bots-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/apps-publish.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/apps-upload.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-manifest-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/resources/bot-v3/bots-create.md
:white_check_mark:Succeeded
View

msteams-platform/resources/dev-preview/developer-preview-features.md
:white_check_mark:Succeeded
View

msteams-platform/resources/schema/manifest-schema.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/create-tab-pages/content-page.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/native-device-permissions.md
:white_check_mark:Succeeded
View

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


Feature/GitHub actions

Can see the workflow in .github/workflows/

Can check that the DOCKER_TAG works in the Makefile, can try running:
make print-ver

After adding to the Makefile:
# build docker image
.PHONY: print-ver
print-ver:
	echo ${DOCKER_TAG}


Hardware: GPS module support

Hello,
does this package support only specific modules (chipsets) or it can be used with every common gps module for arduino and raspberry pi?
Thanks

Hardware localization such as GPS is out of scope for this project


follow new ink api

https://github.com/JunoLab/atom-ink/pull/127

The  Send to console button kinda breaks lazy results, will have to look into that. For now it might be better to get the stable changes in and leave that button for another PR.

Yup, seems sensible.

That code now lives in https://github.com/JunoLab/atom-julia-client/tree/sp/sendtoconsole.

This isn't really breaking (we didn't use the .julia class we set), so I'm going ahead and merge this.


[EVENT] CryoCloud upcoming small events

Summary

https://2i2c.freshdesk.com/a/tickets/993
Event Info
NSIDC User Working Group meeting:
Date for the event: Sept 26
Active times: 11am - 3 pm PT
How many people will attend the event: 13
Do you need to need hub infrastructure to be pre-initialized before the event? If possible, but not required
Any other information that will help us prepare for the extra usage during the event - This will be a small demo to show how NSIDC data is accessed from the cloud
Icesat-2 Science Team meeting workshop:
Date for the event: ** Oct 5
** The active times for the event (e.g., 9am to 5pm US/Pacific): ** 12 pm - 530 pm PT
How many people will attend the event: 13
** Do you need to need hub infrastructure to be pre-initialized before the event? Would be awesome, but not required
Hub info

Hub URL:
Hub decommisioned after event?:

Task List
Before the event

[ ] Dates confirmed with the community representative and added to Hub Events Calendar.
[ ] Quotas from the cloud provider are high-enough to handle expected usage.
[ ] One week before event Hub is running.
[ ] Confirm with Community Representative that their workflows function as expected.

👉Template message to send to community representative
Hey {{ COMMUNITY REPRESENTATIVE }}, the date of your event is getting close!

Could you please confirm that your hub environment is ready-to-go, and matches your hub's infrastructure setup, by ensuring the following things:
- [ ] Confirm that the "Event Info" above is correct
- [ ] On your hub: log-in and authentication works as-expected
- [ ] `nbgitpuller` links you intend to use resolve properly
- [ ] Your notebooks and content run as-expected

[ ] 1 day before event, either a separate nodegroup is provisioned for the event or the cluster is scaled up.

During and after event

[ ] Confirm event is finished.
[ ] Nodegroup created for the hub is decommissioned / cluster is scaled down.
[ ] Hub decommissioned (if needed).
[ ] Debrief with community representative.

👉Template debrief to send to community representative
Hey {{ COMMUNITY REPRESENTATIVE }}, your event appears to be over 🎉

We hope that your hub worked out well for you! We are trying to understand where we can improve our hub infrastructure and setup around events, and would love any feedback that you're willing to give. Would you mind answering the following questions? If not, just let us know and that is no problem!

- Did the infrastructure behave as expected?
- Anything that was confusing or could be improved?
- Any extra functionality you wish you would have had?
- Could you share a story about how you used the hub?

- Any other feedback that you'd like to share?

Given the nature of small events, I have assigned to @GeorgianaElena and @sgibson91 who are/are going to be involved with the support cycle during the time these events will run. I expect the first one to be handled (monitored, actually) by @GeorgianaElena and the second one to be handled (monitored) by @sgibson91.

The date of these events has passed. I am not aware of any tickets coming in during this period, so I believe things went ok. Closing.


flexget: 3.1.149 -> 3.1.150

Motivation for this change
Update to latest upstream release 3.1.150
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 145476 run on x86_64-linux 1

1 package built:

flexget


DEX-383 remove support for bulkUpload field

Pull Request Overview

bulkUpload field now replaced with uploadType as agreed with Ben
tests updated to reflect this

/rebase


{CI} Pin Jinja2 to 3.0.3

Description
CI failed:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=1459759&view=logs&j=715ff7e7-0433-5a80-bbc9-ca9609d2bc48&t=7f464a6b-d59f-566f-20bd-0d339d7433d8&l=831
2022-03-25T03:56:05.2026491Z Extension error:
2022-03-25T03:56:05.2028477Z Could not import extension sphinx.builders.latex (exception: cannot import name 'contextfunction' from 'jinja2' (/opt/hostedtoolcache/Python/3.10.2/x64/lib/python3.10/site-packages/jinja2/__init__.py))

This is because Jinja2 released a new version yesterday which introduced breaking changes, but sphinx doesn't have version limits on Jinja2, causing the latest Jinja2 being installed.
TODO
This PR is only a workaround, the final solution would be to update sphinx to newer versions.
References

https://github.com/readthedocs/readthedocs.org/issues/9037
https://github.com/pallets/jinja/issues/1631

CI


@dnd-kit/core upgrade can't drag

When I upgrade @dnd-kit/core from version 3.0.1 to 3.0.2 or 3.0.3, my component can't drag.
Then I back to version 3.0.1 and the problem solved.
Maybe something wrong in 3.0.2 or 3.0.3 ?

Kind of hard to help you without more details. Can you share the code?

I`ve faced the same issue after upgrade to 3.0.2 from 3.0.0.

Closing this issue, most likely due to having multiple versions of @dnd-kit/core installed locally. This should be less of an issue now that we have moved @dnd-kit/core to peerDependencies of @dnd-kit/sortable and @dnd-kit/modifiers in #294
Feel free to open with replication steps.


Flux Sequence Parallel Poor Scalability Issue

sp=4
FluxTransformerBlock forward took 0.0036454200744628906 seconds to run on GPU.
FluxSingleTransformerBlock forward took 0.0033855438232421875 seconds to run on GPU.
end-to-end epoch time: 6.30 sec, memory: 38.453348864 GB
sp=1
FluxTransformerBlock forward took 0.008208751678466797 seconds to run on GPU.
FluxSingleTransformerBlock forward took 0.0074808597564697266 seconds to run on GPU.
end-to-end  epoch time: 2.57 sec, memory: 36.300577792 GB
both the FluxTransformerBlock and FluxSingleTransformerBlock, which are the primary DiT Blocks, have shown acceleration when using SP.
However, the overall inference time has increased. We are currently investigating the issue of degraded scalability with the Flux extension.

The problem is solved. We should do some warmup step before time profiling.


Updating metadata schema

Setting "manufacturer" and "design" to Optional in BatteryDescription for the BatteryMetadata. Fixes #70.

@WardLT I am not familiar with pydantic, so would you mind double-checking?

Did something wrong. Will try again.


fix setting migrator bug

fix bug (where the old settingsObject was being passed through instead of the new one), and unit test (which is what caught the regression)
FYI @madajczyk  - i'll merge this once you have a chance to look at it and confirm this is the right fix. I hadn't yet deployed your PR, so fortunate timing there!

Oh man, terribly sorry for the problem here @wesmoncrief.  I thought I had the unit tests set up and running properly to avoid issues.  I'll take this is an item to add to workflow for any future PRs I get involved in (and possibly find a way to document that, too).
This fix looks good.  Thank you so much for identifying and resolving!

No worries at all! The real issue here is that I should have GitHub actions configures to automatically run tests before allowing merge 🙂


Contact the organization - the email is sent to the user

 Issue by zuzannawiler
Wednesday Feb 24, 2016 at 08:01 GMT
Originally opened as https://github.com/stxnext-csr/volontulo/issues/457

When  a user goes into organization info under e.g. http://volontuloapp.org/organizations/fundacja-taka-sytuacja/9 and contacts the organization, the email is not sent to the organization, but to the user.

 Comment by zuzannawiler
Thursday Feb 25, 2016 at 10:52 GMT

Needs to be done after #444 is completed

Remove user that fills contact form from email recevers list

End user is not receiving email, but mail is also sent to address: ddd.

Randomly created user<EMAIL_ADDRESS>was assigned to this Organization as well. Work as expected. SIgn-off.


apply_qirpass() of Pytket-qirpass generates QIR with inverted parameters

Hello @Roland-djee @cqc-alec,
I am using pytket's qirpass (https://pypi.org/project/pytket-qirpass) to optimise QIR.

How qirpass works: QIR --parse--> Circuit --transform--> Circuit --generate--> QIR

In the QIR code generation phase, parameters of the callable are inverted. For example:
define void @main() #0 {
entry:
  call void @__quantum__qis__h__body(%Qubit* inttoptr (i64 0 to %Qubit*))
  ret void
}

declare void @__quantum__qis__h__body(%Qubit*)

becomes
define void @main() #0 {
entry:
  call void @__quantum__qis__rz__body(double 0x3FF921FB54442D18, %Qubit* null)
  call void @__quantum__qis__rx__body(double 0x3FF921FB54442D18, %Qubit* null)
  call void @__quantum__qis__rz__body(double 0x3FF921FB54442D18, %Qubit* null)
  ret void
}

declare void @__quantum__qis__rx__body(double, %Qubit*) local_unnamed_addr

declare void @__quantum__qis__rz__body(double, %Qubit*) local_unnamed_addr

Where in the code this happens: the inner-loop of compile_basic_block_ll(). paramreps are listed before argreps:

        for cmd in circuit:
            op, args = cmd.op, cmd.args
            optype, params = op.type, op.params
            name, sig = tk_to_qir[optype]
            assert len(params) + len(args) == len(sig.split(", "))
            paramreps = [encode_double(param * pi) for param in params]
            argreps = [argrep(arg) for arg in args]
            bb_ll += f"  call void @{name}({', '.join(paramreps + argreps)})\n"  ## <--------
        # Write out the remaining instructions
        for instr in unknown_sub_block:
            bb_ll += str(instr) + "\n"

Q1: Shouldn't the parameters be the other way round as this inversion violates the QIR spec ?
Q2: If yes, can I expect a patch anytime soon ?

Best,

Hi @hamidelmaazouz ,
I'm not quite sure what the bug is here. Are you saying that the qubit pointer should come before the angle parameter in (e.g.) __quantum__qis__rz__body?
The order here was based on that given in this page. Do you have a reference to a specification where the order is different? (If so we should definitely try to make them consistent.)

Yes, the qubit pointer should come before the angle parameter.

Do you have a reference to a specification where the order is different?

I was referring to the new spec under development. Here's the link: https://github.com/qir-alliance/qir-spec/blob/spec_update/specification/under_development/Instruction_Set.md
But then again, qirpass seems to adhere to spec v0.1 which makes it also valid.
Are there any plans to get a jump on the new spec in the future ?

Yes, the qubit pointer should come before the angle parameter.

Do you have a reference to a specification where the order is different?

I was referring to the new spec under development. Here's the link: https://github.com/qir-alliance/qir-spec/blob/spec_update/specification/under_development/Instruction_Set.md
But then again, qirpass seems to adhere to spec v0.1 which makes it also valid.
Are there any plans to get a jump on the new spec in the future ?

I see, thanks. We won't change this immediately since doing so would break some existing pipelines, but if and when the new spec is approved we will presumably have to make that change.

Thank you @cqc-alec


Support upstream jdk sha

Support openjdk commitID as TAG for both release and non-release build
Close #3309
Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

Close in favour of https://github.com/adoptium/temurin-build/pull/3386


[CI] Fix Vitis-AI tests when USE_VITIS_AI flag set to OFF

Hi @leandron,
We have fixed the vitis-ai test failure issue when running with USE_VITIS_AI OFF flag. Could you please review and merge it?

Hi @anilmartha, thanks for the PR. It looks very promising in fixing https://github.com/apache/tvm/pull/10802.
Do you mind renaming it so that is it more clear for other people not involved in the original issue, what problem this PR is fixing? I would also recommend putting a [CI] tag, so that it looks more like other PRs.
cc @ashutosh-arm @driazati @lhutton1 for reviews

@leandron changed the title as per your suggestions.

Thanks @anilmartha! LGTM!

Thanks @anilmartha @ashutosh-arm @driazati !


[Dropdown Menu] The data-options documentation is obsolete

I checked.
At http://foundation.zurb.com/sites/docs/dropdown-menu.html#js-option (for v6.2.4), we can read:

data-click-open, default true
data-force-follow, default false

But in the code at https://github.com/zurb/foundation-sites/blob/v6.2.4/js/foundation.dropdownMenu.js#L362 (for v6.4.2 and currently in develop):

clickOpen: false,
forceFollow: true

I've checked the template, and SuperCollider is using the @example value to generate what is presented as the "default" value:
...
{{#each js.member}}

    {{formatJsOptionName this.name}}
    {{formatJsOptionValue this.examples}}
    {{this.description}}

{{/each}}
...

https://github.com/zurb/foundation-docs/blob/master/templates/partials/javascript-reference.hbs#L67
So for example when forceFollow was added in https://github.com/zurb/foundation-sites/pull/7344, the value of @example was set to be an example (obvious things are obvious), different from the variable value.
I'll make a PR.

Yeah I think this is definitely an issue we need to fix. I think we should have both an example and a default... short path will be having both in comments; I'd like SuperCollider to get the actual option value but this may take some time.  @gakimball do you have any thoughts on how we'd do that?

*JSDoc provide the actual option value.

I made some more tests. The following code ...
DropdownMenu.defaults = {
  ...
  /**
   * Boolean to force overide the clicking of links to perform default action, on second touch event for mobile.
   * @option
   * @default
   */
  forceFollow: true
};

... stop the compilations of docs. There is no error, but I think SuperCollider or JSDoc crashed. They do not handle the empty @default for an array value. (see http://usejsdoc.org/tags-default.html).

Given these are docs updates I think this can be accomplished after 6.3 is out the door.

There is also: https://github.com/spacedoc/spacedoc

@kball, So, what do we do for this issue ?

Improving the docs is going to be a big focus by @rafibomb and I in the first part of the new year.  @gakimball as the primary author on supercollider & spacedoc, how hard do you think it would be to get those libraries to read the actual value for these variables?

@kball It should be possible to get what you need (separate examples and defaults) without modifying Supercollider. I'll do some experimentation with tag parsing and see if we can't come up with something less brittle than the current system.
Having an example and a default in the table might make it too crowded, but needing them separate makes sense. An option might have, say, null as a default value and then something else like a function or string as an example.

@gakimball Thank you for your reply. But the main problem here is how to get the default value. It is not provided in the SuperCollider object, maybe because it is an array value and not a variable ?

@ncoden The Supercollider object comes straight from JSDoc and isn't modified in any way. According to the documentation for the @default JSDoc annotation, it only works with primitive values: string, number, boolean, and null. So if a plugin has an array or object as a default value, it won't be picked up.
I'm also wondering if the parser only plucks the default value for variable assignment (x = 'y') versus object property assignment ({ x: 'y', }), but that would be weird.

So, we will keep the current solution, but with @default instead of @example. :/

What's an example of where the default and the example are different enough that you'd need to show both? And how prevalent do you think such instances are?

I never talked about a single example value, but the expected type (keyword, number...) and/or all the possibles values when relevant.

@ncoden When you say "all possible values", I can think of a few scenarios:
One is that a plugin option can accept multiple types. I haven't been in the codebase in a while, but ideally there are as few of those as possible to begin with. If the explanation is too verbose, you might be better off moving that text out of the option table and into the documentation body. For example: "If a number is passed, x, if a string is passed, y".
Another is that a plugin option can accept one of a set number of values. JSDoc has @enum to handle this, but it might be overkill, when in most cases you can just type out the full list in the description of the property. For example:
DropdownMenu.DEFAULTS = {
  /**
    * Position of the menu relative to what direction the submenus should open. Can be `left` or `right`
    * @option
    */
  alignment: 'left',
};

Fixed: https://github.com/zurb/foundation-sites/pull/9562


More sophisticated gas metering for host calls

Right now, Athena does extremely simplistic gas metering: basically all instructions have a fixed gas cost of 4 (based on the word size in bytes). At the very least, we should attempt to properly meter host calls such as read/write storage, call, etc. Estimate how much these actually cost in terms of consumed resources (storage, bandwidth, compute), create a straightforward formula for each host call (e.g., based on the size of the call data), and implement more sophisticated, accurate gas pricing.

I was informed that host part is "free" of gas charging and only VM part should be counted (e.g. it can be the counter of executed instructions, or counter of clock cycles spent by program).
If we would like to go into charging also for syscalls imo we should consider 2 options:

hardcoded value cost per syscall (predictible)
each syscall could calculate/return cost itself (more elastic/functional, but may lead to different prices for the same work, in effect making everything less predictible).

Actually we already have one "paid" syscall - the ED25519 signature verification (it has a constant cost). If we want/need variable-cost syscalls, the cost would have to be predictable - how would the executors agree on the cost otherwise? I think the cost should be a function of the syscall arguments. The problem is that currently the syscall cost is hardcoded in the syscall number (it's inherited from SP1) and this would need to be changed.
impl SyscallCode {
  pub fn num_cycles(&self) -> u32 {
    (*self as u32).to_le_bytes()[2].into()
  }

If we want/need variable-cost syscalls, the cost would have to be predictable... the cost should be a function of the syscall arguments

💯
For reference we can study how this is done in EVM, for those opcodes that have a "dynamic" gas cost:

https://docs.google.com/spreadsheets/d/1n6mRqkBz3iWcOlRem_mO09GtSKEKrAsfO7Frgx18pNU/edit?gid=0#gid=0
https://www.evm.codes/

e.g.:


Does this provider support subaccounts?

We have connected subaccounts, but I don’t understand whether the terraform provider can use them?

@ilyavaiser unfortunately, the provider doesn't support subaccount API tokens yet.

@nabadger We aim to handle all our API features in the provider. Definitely, sub-account will also be implemented.


Fix instance name error in production environment

Fixes #

Hi this code should work correct
function Fn() {}
isJoditObject(new Jodit()) === true
isJoditObject(new Fn()) === false


--lineart unicode not working

Hi,
Thanks for a great package.
--lineart unicode when generating calw generates the following error (fancy and ascii work as required).
$ gcalcli  --lineart unicode calw
Traceback (most recent call last):
  File "/sbin/gcalcli", line 33, in <module>
    sys.exit(load_entry_point('gcalcli==4.3.0', 'console_scripts', 'gcalcli')())
  File "/usr/lib/python3.10/site-packages/gcalcli/cli.py", line 167, in main
    gcal.CalQuery(
  File "/usr/lib/python3.10/site-packages/gcalcli/gcal.py", line 1282, in CalQuery
    self._GraphEvents(cmd, start, count, event_list)
  File "/usr/lib/python3.10/site-packages/gcalcli/gcal.py", line 487, in _GraphEvents
    self.printer.msg(week_top + '\n', color_border)
TypeError: can't concat str to bytes

Exact same error in two diferent systems (OpenSuse Tumbleweed and Raspberry Pi OS).

Fixed via #582.


Kinesis Elasticsearch Sink: allow parametrized timeouts for jest client

I have implemented this on my end and it could be useful for other people, but I think it could be beneficial to configure the jest client directly from the hocon config file. Especially the connection and read timeout values (5 seconds was too small for my cluster in case of big load).
ElasticSenderHttp:
  private val factory: JestClientFactory = new JestClientFactory()
  factory.setHttpClientConfig(new HttpClientConfig
    .Builder("http://" + configuration.ELASTICSEARCH_ENDPOINT + ":" + configuration.ELASTICSEARCH_PORT)
    .multiThreaded(true)
    .discoveryEnabled(false)
    .maxConnectionIdleTime(30L, TimeUnit.SECONDS)
    .connTimeout(300000) # this line
    .readTimeout(300000) # this line
    .build()
  )

Agreed!  All of those should be available from the HOCON.


Common Install task does not remove Master Machine and Worker MachineSets Manifests

Per OCP 4.5 documentation for performing VMware UPI installation the Master Machine and Worker MachineSet manifests should be deleted prior to the creation of the Ignition files.
I have created PR #47 that resolves this issue.

This has been resolved with the merging of PR #47


Feature/basin connectivity

Initial Basin commit

These aren't ready for develop yet. Pull into a feature branch?

I'm good with the PR to develop. the idea is PR starts, we provided feed back, it gets updated over time, we merge in. Preferably we'd not leave feature branches laying around within the repository.


Error when compiling

I’m completely new to Rust so pardon me if this is an error on my end.
Anyway, when I run cargo build --release, I get this output:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS E:\configs-programs\chronos\chronos>

I would not be surprised if your git checked out the file as having \r\n line endings. This probably should be &[u8] to not hard code the size.

I'll have to fix this later

okay i meant to fix this a while ago but i did get around to fixing it today


Binaries

BGGfetch_2022-01-16_refactored-WebClients.zip

BGGfetch_v0-1-Alpha20020228-0.zip

BGGfetch_v0-1-Alpha20220303-0.zip

BGGfetch_v0-1-Alpha20020306-0.zip

BGGfetch_v0-1-Alpha20020309-0.zip


GH-4588 Update japicmp version for 5.0.0 and also enable japicmp for all modules by default

GitHub issue resolved: #4588
GitHub issue resolved: #4589
Briefly describe the changes proposed in this PR:

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

Exceptions to japicmp:

compliance
tools/runtime-osgi
tools/server
tools/workbench

These are all primarily disabled because japicmp complained that the jar file wasn't available. The compliance and workbench code I agree should not have strict backwards compatibility requirements, osgi should also be fine since it's just a wrapper to enable osgi. The server module, on the other hand, should probably be stricter wrt. backwards compatibility...but then we would need to figure out why japicmp is complaining about the missing jar file.


link authorization code to access tokens

we need to be able to detect authorization code replay, and have the ability to revoke access_tokens that were issued using this code on reuse.
Implement this by linking the authorization_code_key to the issued access_token(s).

done.


mosn支持熔断策略

Your question
mosn有以下功能吗？，可否集成？

Environment

MOSN Version 1.0.0

Logs

Paste the logs you see.

@ansiz Could you help to take a look at this issue? Thanks.

@ansiz Could you help to take a look at this issue? Thanks.

OK


Update link to IronPython

@huguesv,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Csv header delimiter

Description of Changes
Please check that the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Add a changelog entry (for non-trivial bug fixes / features)
[ ] CI passes

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.4482819
-0.03454733
128.95932
+1.8857727

1
5000
5.1897917
+0.13803434
137.16487
+0.30900574

1
10000
10.017402
-0.36215496
144.26118
-3.732483

1
50000
52.37042
+2.7083778
173.73276
+2.962555

1
100000
98.4989
-1.4585571
238.77963
+1.1095123

10
100
1.9999961
+0.068983555
132.54553
-1.4644318

10
500
6.241409
+0.069132805
139.13792
+0.3184204

10
1000
11.896813
-0.39660358
148.96552
+1.5358276

10
5000
56.224354
+0.13727188
177.35493
-5.5091553

10
10000
107.07256
+0.99131775
226.19289
-1.7254791


Fix chatkit issues

Resolves #448
Resolves https://github.com/source-academy/cadet-frontend/issues/750

Pull Request Test Coverage Report for Build 2582

11 of 18 (61.11%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.7%) to 94.883%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/cadet/chat/room.ex
11
18
61.11%

Totals

Change from base Build 2578:
-0.7%

Covered Lines:
853

Relevant Lines:
899

💛  - Coveralls

Could you briefly describe how your PR solves the issue thanks!

Due to Pusher's response on the user limit, we will send a request for every 10 users to add the users into the room.
But, in hindsight, I think the public chatroom solution might be better...

I will modify to use public chatrooms instead

Modified to use public instead of private chatrooms now


Bring back welcome menu item

Fixes https://github.com/microsoft/azuredatastudio/issues/18001
VS Code started replacing all the old legacy welcome page code with the newer Getting Started (walkthrough) experience and this was one of the things deleted. Bringing it back for now (the getting started stuff is all commented out for now).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.175%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
14516

Relevant Lines:
28627

💛  - Coveralls


Modified the dist/angular-selector.js file to fix issue #21 - Dropdow…

Modified the dist/angular-selector.js file to fix issue #21 - Dropdown closing on scroll click in IE and Edge

you need to make the changes in src. dist will be overridden on build


Issue with bot reporting result

[PennyDreadfulMTG/perf-reports] 500 error at /report/ (#12274)
Failed to execute INSERT INTO deck_match (deck_id, match_id, games) VALUES (%s, %s, %s) with ['8997', 15518, '0'] because of (1452, 'Cannot add or update a child row: a foreign key constraint fails (decksite.deck_match, CONSTRAINTdeck_match_ibfk_2FOREIGN KEY (deck_id) REFERENCESdeck(id))')
Reported on decksite by logged_out
Request Method: POST
Path: /report/?
Cookies: {}
Endpoint: add_report
View Args: {}
Person: logged_out
User-Agent: None
Referrer: None
Request Data: {'entry': '8998', 'opponent': '8997', 'result': '2–0', 'draws': '0', 'matchID': '195159795'}
DatabaseException
Stack Trace:
File "/home/discord/.local/lib/python3.6/site-packages/flask/app.py", line 1997, in call
return self.wsgi_app(environ, start_response)
File "/home/discord/.local/lib/python3.6/site-packages/flask/app.py", line 1985, in wsgi_app
response = self.handle_exception(e)
File "/home/discord/.local/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
response = self.full_dispatch_request()
File "/home/discord/.local/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/discord/.local/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/discord/.local/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
raise value
File "/home/discord/.local/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
rv = self.dispatch_request()
File "/home/discord/.local/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
return self.view_functionsrule.endpoint
File "./decksite/main.py", line 252, in add_report
if form.validate() and lg.report(form):
File "./decksite/league.py", line 196, in report
match.insert_match(dtutil.now(), form.entry, form.entry_games, form.opponent, form.opponent_games, None, None, mtgo_match_id)
File "./decksite/data/match.py", line 14, in insert_match
db().execute(sql, [right_id, match_id, right_games])
File "./shared/database_mysql.py", line 56, in execute
raise DatabaseException('Failed to execute {sql} with {args} because of {e}'.format(sql=sql, args=args, e=e))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Is this a race between manual reporting and bot reporting?

Not possible because of the explicit lock by deck_id, and anyway that would not be the error, it would be a 6th result. It could be a race condition between the report and something that deletes a deck: for instance, if I'm reporting while my opponent retires the deck if it was their first game. We could use the lock strategy also in the retire method, to avoid possible race conditions.

Closing this as has not reoccured and @jgabrielygalan tightened up some of this. Will reopen as necessary.


Fix travis

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

Codecov Report

Merging #13 into master will decrease coverage by 0.11%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
- Coverage    71.1%   70.99%   -0.12%
==========================================
  Files          33       33
  Lines        1270     1272       +2
  Branches      262      262
==========================================
  Hits          903      903
- Misses        367      369       +2

Impacted Files
Coverage Δ

src/deciders/TaskGraph.ts
85.49% <0%> (-1.33%)
:arrow_down:

Continue to review full report at Codecov.

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


a few ideas

change the README.md: I think you can remove the badges and the sections on Backers and Sponsors
change the current CHANGELOG.md to follow these changelog specs

What do you think?

I can make these changes and create a PR.

Amazing Yes, you are welcome.

Ok, almost a year later.... ;-)
I'm gonna look into this weekend.


merge development branch

enable LED
improvements to autostart of Bloch Demo
Add Qiskit 0.23
changes to readme.md


#1628 - Fixing HELM mojo, replacing template placeholders in ResourceMojo, Fixing NPE in UndeployMojo

Creating PR based on analysis in https://github.com/fabric8io/fabric8-maven-plugin/issues/1628

@djotanov : Have you tested it? Is it working for you?

Yes, everything works for me.

@djotanov : Great! Really Really appreciated :clap:

one minor thing, could you please add a line to changelog also?

Sure, done


bucket error causes failure

got this error this morning
run cross checker
State missing - aws_s3_bucket_versioning.<bucket_name> for aws_s3_bucket_versioning__<bucket_name>.tf not found - getting app-dev-serverlessdeploymentbucket-1qpneks1vfsz4
aws_s3_bucket_versioning <bucket_name>
listing in local state move
No <bucket_name> state files exiting ...
Found Error: ** Error: Zero state aws_s3_bucket_versioning <bucket_name> exiting.... exiting ....

the failure caused aws2tf to quit

committed a potential fix for this one

it has progressed beyond that point. closing


Update in the contributors.md #hacktoberfest

Add contributor name and clear some blankspaces founded.
First contribution.

Closed. Diff is unavailable.


Feature/travis unit test

First implementation for #16. Horribly ugly, but it does the job for now

It looks like your branch here has 3 commits, 2 of which were already merged, and for that reason there are conflicts. Can you rebase your branch, so that it's just the one commit? Also, is it possible to add windows to the matrix? Sorry I was slow responding to this.

I don't know what exactly I did, but I somehow managed to screw up my branching so much I had to start from scratch and cherry-pick the good stuff. Anyways, it should be fixed now.
Regarding windows: I did a quick skimming and apparently travis does support it by now, but I have absolutely no clue how it is set up or how to deal with potential OS differences in terms of shell commands for the install script.
That being said, AppVeyor seems to be more mature when it comes to OSS CI in Windows. I have no clue how to set it up properly though.
IMHO, matrix-testing gcc and clang (with 2 different standard lib implementations) on Linux should be sufficient, as far as it comes for those two compilers. If they did behave differently on Windows, I'd consider it a compiler/implementation bug.
I do agree that Visual Studio should be added to the compilers under test, but as stated before, I think that's a separate thing for AppVeyor.

Well, as it happens, the library currently doesn't compile for MSVC because macros are limited to only 127 arguments, which is actually conformant (if annoying). So I was hoping to get some CI for windows. However, this is a good start. One possibly-easier followup that would be nice to address would be to also add support for 11. Again, I made a small mistake and since I'm not compiling 11 locally these things tend to get through (Murphy's Law).
Thanks for your contribution!

Closes #16 .


Add sequel pro

Added Sequel Pro database client.
Made tiny whitespace change to line above.

Project URL
https://github.com/sequelpro/sequelpro
Category
Development/Other
Description
See bullets above
Why it should be included to Awesome macOS open source applications  (optional)
I was surprised it wasn't here already, it's such a slick app, love that it's open source too.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Appropriate language icon(s) added if applicable
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          2 Warnings

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

214
Dupe
https://github.com/sequelpro/sequelpro

  Generated by :no_entry_sign: Danger

@mattpotts Thank for your contribution! But this project already exists in this list. I'll close this PR.

I see it now, don't know how I missed it before!


RDC bug

When using remote desktop connection the bastard becomes unusable after the resolution changes to match phone resolution.

https://imgur.com/a/nCkL0NC

Calling such a piece of software "the bastard"... :D

Does this still happen in TaskbarX <IP_ADDRESS>?


Update README.md

Proposed Changes

Moves the subtitle to another line
Moves the project logo to the top right corner of the page
Changes the headers to follow title order

# Main title
## Section
### Subsection

Main title
Section
Subsection

@googlebot I signed it!


Fix mypy status check not working

Bump mypy version to 0.641
Fix check/mypy not forwarding mypy's exit code
Remove cirq.abc workaround because mypy sees right through it now
Add type: ignore to all extension casts involving an abstract type (there doesn't appear to be an equivalent of Type[T] that allows T to be abstract)
Use overloads to workaround TDefault not being inferred from the default value (instead causing an error like 'default value is not a TDefault')
Fix google_v2_supremacy_circuit.py importing cirq
Use cirq.type_workarounds.NotImplementedType (secretly Any) instead of type(NotImplemented) (which causes mypy to fail) or the built-in NotImplemented (which causes runtime exceptions) or the string 'NotImplemented' (also runtime failures) or the value types.NotImplementedType (which doesn't exist in python 3). Sigh
Add type annotations to a handful of places that needed them

This was broken for a long time without anyone noticing. Scary stuff.

Apparently even the string 'NotImplemented' isn't okay. Going back to the "say NotImplementedType but it really means Any" approach.

Automerge: started

Automerge cancelled: A status check is failing.

Automerge: started

Automerge cancelled: A status check is failing.

Automerge: started


feat: add Vector Search indexers and retrievers to Vertex AI plugin

This PR adds Vertex AI Vector Store to the Vertex AI plugin. There are some design decisions still to be made, as VVS works differently to other vector databases (in that it doesn't store metadata, only ids and the feature vectors)
I have included a samples for BigQuery, Firestore, and a Custom local document store (just in a JSON file)

[x] tests (unit, manual)
[x]  docs (in testapps)
[ ] changelog

Thanks @cabljac for adding out-of-the-box indexers/retrievers and test coverage :)
I left a few comments on you latest updates.


announcements md file - no longer by year

Lois is considering a single announcement file rather than new one each calendar year as currently indicated. Easy?

No change needed! Just needs to match 'Announcements' in filename.

I'm looping Lois in. I deleted the 2018 announcement and changed the name of the 2017 announcement to be universal. I think we are still in business. I'm waiting to see if anything brakes in the next commit.

Latest commit made/pushed and data imported, looks like we're good!


Document possible IndexedDB eviction with MDN ref

Platforms affected
All
Motivation and Context

I discovered the possible IndexedDB eviction through research to check the documented limits of IndexedDB data storage, triggered by a second look at PR #1011. I think this limitation really needs to be documented.
Possibly related to: PR #1042 (update IndexedDB platform support)
I think this kind of pitfall is extremely important to document whenever possible and should be treated like a bug.
Description

see title
Testing

visual inspection
Checklist

[ ] [TODO] I've run the tests to see all new and existing tests pass
I added automated test coverage as appropriate for this change
~~ Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))~~
If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords) (I did link to a couple related PRs in this issue)
[x] I've updated the documentation if necessary

FOLLOWUP TODO:

[ ] If merged, we may need to do a manual rebuild (see issue #1035)

@timbru31 can you confirm if this is OK after the last commit based on your previous discussion?

If there is no problem, I believe this PR can be merged in.
After this PR is merged in, #1042 should be rebased before merging.


Delete unnecessary first commits

After a long break, decided to do smth simple to test new configuration. Removed empty and unnecessary 7 commits at the beginning of the branch. I think almost everything works

View rendered LICENSE.md
View rendered README.md

You know there's no such thing as deleting commits, right?

Yep, I squashed 8 commits into 1. I forgot about the naming, sorry

Old commits will remain in the tree, though.

Okay


dflib-jupyter and echarts

trying to get echarts working with dflib: https://github.com/jupyter-java/jupyter-java-examples/blob/main/notebooks/java-dflib-echarts.ipynb
import org.dflib.echarts.*;

DataFrame df = DataFrame.foldByRow("name", "salary").of(
                "J. Cosin", 120000,
                "J. Walewski", 80000,
                "J. O'Hara", 95000)
        .sort($col("salary").desc());

var chart = ECharts
        .chart()
        .xAxis("name")
        .series(SeriesOpts.ofBar(), "salary")
        .plot(df);

        chart;

See that it does generates a html/text output cell with:

but i cant get that to render in vscode jupyter notebook nor in github notebook preview.

I am able to reproduce it partially. It is that "race condition" that I mentioned elsewhere. The first time the output is empty box. The second time I rerun the cell, it works ok (see below). That's in jupyter lab in Firefox. Let me try vscode jupyter

Yes, def some kind of race condition. Every now and then it renders in VSCode, but that's entirely unpredictable. We'll investigate

From a simple fix this turned into something much bigger. So...:

jupyter lab in the browser.  Charts work. Very rarely may require to re-execute a cell. We have a fix to make it more robust, but can't even reproduce the original issue as it is not that common.
GitHub doesn't allow even the simplest local JS from a notebook output to be executed.
VSCode can exec JS and can load external JS files. But the rendering doesn't work most of the time (it does sometimes).

The reason Kotlin Kandy works in cases 2 & 3 is that the rendering seems to be done server-side and there are embeded SVGs in the .ipynb. Our rendering is 100% client-side, so we need JS to work. So GitHub will continue to show an empty cell (actually a properly sized div, just without a chart  🙂 ) until we can switch to server-side rendering somehow. I am not giving up on VSCode just yet, but need to figure out how to debug JS execution within the notebook (e.g. how do I check the console logs)

Ok, getting somewhere with VSCode. There's a ["Jupyter Notebook Renderers"](Jupyter Notebook Renderers) extension from Microsoft. If I disable it and restart VSCode, the charts start rendering. I suspect it loads some conflicting JS libraries will need further investigation, but at least we know where to look

can confirm that disabling that notebook renderer extension makes it work for me.
that is unfortunate as it provides lots of other nice renderers.

whats weird though is that notebook renderer isn't supposed to affect text/html...

using developer tools I took a snapshot to spot the diff with and without the rendering.
With jupyter notebook rendering there are two iframes - one nested in another.

without its just one iframe and all is good.

Aha. I am not much of a VSCode user, so I was unsure how to even debug the HTML/JS involved. Thanks for the hint about developer tools. We'll see if we can do anything about it from our end.


Getting this issue: NetworkError: Socket operation failed, retrying...

Hi i'm using cache to serve user's request on rails project. It's working fine but sometimes getting following error:
#<Dalli::NetworkError: Socket operation failed, retrying...>
retrying request with new server
Dalli::Server#connect localhost:11211
It makes my application loses some requests. These are configuration.
config.cache_store = :dalli_store, 'localhost:11211', {:compress => true,  :value_max_bytes => 2048576 }
Is there any solutions to this. Or i did something wrong?

@sbatbayar As #440 has been fixed, I'm assuming this issue is resolved as well?  So I'm going to close.  If this is still a problem, please reopen.


Report incorrect startup times after seeks to Apple in iOS 18 / missing error log entries

Startup times reported in the access log after a seek, and displayed in the debugging overlay or with our metrics view, are wrong in iOS 18 beta (increasingly larger with each seek). This can be reproduced with our nightly demo when comparing behaviors on iOS 17 / 18. I guess tvOS is also affected.
We should report this issue to Apple. Probably the tvOS debugging overlay suffices (or we could mention the trick on iOS to display it, avoiding a complex demo).
Non-fatal error entries (e.g. warnings about excessive birates) also seem not correctly logged anymore in iOS 18.

iOS 18 beta 2 at the moment.

Issue iOS / tvOS 18 regression: Startup times from AVPlayerItemAccessLog are incorrect after seeks filed under FB14331591.

Fixed in iOS / tvOS 18 beta 5. I closed the FB accordingly.


Is it possible to override the html template?

Vue.js version: 1.0.28
consumed using: webpack

No. You can fork the repo and change it to your liking
On Oct 10, 2016 3:44 PM, "lavezzi1"<EMAIL_ADDRESS>wrote:

Vue.js version: 1.0.28
consumed using: webpack

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/matfish2/vue-pagination/issues/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcMPLO7bMAAWhXaL2lqUQ31RX39kVY6ks5qyjM4gaJpZM4KShnH
.


Sublime Text Auto-closing Tags

When using Sublime Text (dev 3102) and the vue-syntax-highlight library, auto-closing a tag with string interpolation causes Sublime Text to use the wrong closing tag.
Example:
<template>

{{ test }}
</template>

When adding </ after {{ test }}, the following occurs.
<template>

{{ test }}</{>
</template>

I would imagine this is a bug with ST3's auto-closing feature, but it's possible it's a bug with the syntax definition, so I'm posting this here.

Same problem here - I can reproduce it.

So I've determined that this issue is due to Lines 317 & 319 in the language definition.
I'm assuming that ST is looking for the most recent punctuation.definition.tag.* and seeing the { as the previous one, even though it's not in the same scope.
If those lines are changed to something like punctuation.definition.string.* then the issue is resolved and the auto-closed tag is
.
@yyx990803 I wonder what the best name for this would be.
The ST documentation seems to suggest any 'unspecific' scope should use punctuation.definition.generic.*
I'll submit a PR with this change in a bit.

This has been resolve in PR #69. The changes just need to be tagged in order to update Package Control.

Looks like the issue has been fixed, closing now.


a repo is listed as not a dataset but it is

https://github.com/maxadam2017/midtermproject
has https://github.com/maxadam2017/midtermproject/blob/master/.datalad/config (modified 12 months ago)

I wonder if it just wasn't returned in a search query for .datalad/config or may be some code logic needs a tuneup?

@yarikoptic It appears it just wasn't returned by GitHub's search.  Even if you just search for hits in that user's account, you get nothing.  (You do get a hit if you click on the "Repositories" option, but using the search API to search for repositories matching path:.datalad filename:config returns nothing, as those qualifiers are only supposed to be used for code searches.)

was likely addressed by #18 which is likely the only way to handle "not necessarily complete" search results


Fix the broken docs

The example code is not displaying on the index page, and the Azure Container Registry documentation is not working.

closed by https://github.com/astronomer/astronomer-cosmos/pull/1106


net/http: ListenAndServe is vulnerable to DNS rebinding attacks

What version of Go are you using (go version)?
go version go1.10 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/rob/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/rob/go/gopath"
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build916972665=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I wrote this small sample http listener code:
package main

import "net/http"

func main() {
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte("Hello World"))
	})
	http.ListenAndServe("localhost:8080", nil)
}

This, as expected, only listens for loopback connections, and it does not respond to requests coming from outside the machine.
I then tried, from the local host, to perform a request with an arbitrary Host header:
 curl localhost:8080 --verbose --header "Host: victim.com"

* Rebuilt URL to: localhost:8080/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> GET / HTTP/1.1
> Host: victim.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 21 Feb 2018 10:17:55 GMT
< Content-Length: 11
< Content-Type: text/plain; charset=utf-8
<
* Connection #0 to host localhost left intact
Hello World%

What did you expect to see?
Either the request to fail or the documentation for ListenAndServe or Handler to say that the local listener does not check for the Host header and is thus vulnerable to DNS rebinding attacks.
What did you see instead?
The request obtaining a response, without checks on the host header, and without any documentation on this issue.

Thank you for reporting this @empijei!
I'll page some of the folks on the net/http and security crews @bradfitz @agl @tombergan @FiloSottile.
Depending on the confirmation and severity of the issue after we evaluate it, perhaps in the future, please report security issues first to<EMAIL_ADDRESS>as detailed at https://golang.org/security, but either way, thank you for reporting it!

Check the documentation for ServeMux
In order to only serve your handle for a specific host, your pattern should read:
http.HandleFunc("example.com/", func(w http.ResponseWriter, r *http.Request) {
	w.Write([]byte("Hello World"))
})

Then a request for victim.com will return a 404.

Oh, I didn't know that, thanks.
Do you think it should be mentioned somewhere else? Or maybe this issue should be described in the documentation?

I suppose we could add some docs about the Host header somewhere.


TODO Issue: Do the whole Wiki thing again

TC-6
Jira Ticket: Current Status: TODO

TC-6 Jira Ticket: Current Status: TODO

Changed Jira Project layout. Now links to THREAT-4


Add Zulip version number to page_params.

This is a basic version of adding a user-readable version number to Zulip.
I put it in page_params (so you can access it via page_params.zulip_version since I don't have a clear idea for where in the visible UI it should go where it wouldn't be cluttery (maybe in an "about Zulip" help page that doesn't exist yet?) but this seems worth adding even in this develop-only form for now.
But thoughts are welcome!

Automated message from Dropbox CLA bot
@timabbott, it looks like you've already signed the Dropbox CLA. Thanks!

Is there a reason you didn't put an underscore in ZULIPVERSION?  Other than that, this looks fine to me.  We could stick it on the settings page for now, but I think we can also just wait for the re-design to make it easier to have an about page.

Yeah, agreed, this is better with an underscore.  Fixed and merged, thanks for the review!


Caching is seemingly broken by React v18's Strict Mode... or is it cancellation?

Discussed in https://github.com/arthurfiorette/axios-cache-interceptor/discussions/664

Originally posted by xml September  1, 2023
React 18 is a significant overhaul, and introduces new behavior in its  during development, causing many, many consequences such as this. It double-renders components, in an attempt to show you whether your renderers are idempotent and free of side-effects. Nice idea, although it's breaking lots of brains. I don't in any way believe a-c-i needs to be responsible for React's idiosyncracies, although at a minimum, it would be nice for people to be aware of the risks. That said...
Like many folks, I made all my heaviest/slowest axios requests cancellable to deal with StrictMode, so that when the component is quickly unmounted and remounted, any initial data calls are aborted. I use the ES spec abortController, as described in Axios docs. So far, so good. It cut down dramatically on duplicate API requests during dev.
Until... I added axios-cache-interceptor, and discovered that it refused to cache any of my most important data calls, no matter what I did. This was a brain-bender, until I randomly tried disabling StrictMode. Boom: caching suddenly worked. Here's an example of the debug messages from a-c-i, before and after. You can see that the request ID is the same, but the outcome is very different... AFTER (working normally, for comparison):
{id: '578315523', msg: 'Sending request, waiting for response', data: {…}}
{id: '578315523', msg: 'Useful response configuration found', data: {…}}
{id: '578315523', msg: 'Found waiting deferred(s) and resolved them'}
{id: '578315523', msg: 'Response cached', data: {…}}

BEFORE (failing, in StrictMode)
{id: '578315523', msg: 'Sending request, waiting for response', data: {…}}
{id: '578315523', msg: 'Waiting list had an deferred for this key, waiting for it to finish'}
{id: '578315523', msg: 'Detected concurrent request, waiting for it to finish'}
{id: '578315523', msg: 'Deferred rejected, requesting again', data: undefined}
{id: '578315523', msg: 'Caught an error in the request interceptor', data: {…}}
{id: '578315523', msg: "Response not cached and storage isn't loading", data: {…}}

So: conclusion thus far: a-c-i is perhaps not necessarily optimized for the unique circumstances of StrictMode during DEV, and it'll work fine in PROD, which is what I'm most worried about. So, OK.
But... what if it's not actually StrictMode causing the problem, but something else related to it? My other calls are caching just fine, even in StrictMode. So, what if the problem is cancellable requests?
To test that, I re-enabled StrictMode, went to my most important data calls, and stripped the abortController. Huh. Whaddya' know?! Suddenly, caching works the way I'd expect: with the first request fetching new data, and the second just reading cache! Results:
{id: '578315523', msg: 'Sending request, waiting for response', data: {…}}
{id: '578315523', msg: 'Waiting list had an deferred for this key, waiting for it to finish'}
{id: '578315523', msg: 'Detected concurrent request, waiting for it to finish'}
{id: '578315523', msg: 'Useful response configuration found', data: {…}}
{id: '578315523', msg: 'Found waiting deferred(s) and resolved them'}
{id: '578315523', msg: 'Returning cached response'}
{id: '578315523', msg: 'Response cached', data: {…}}
{id: '578315523', msg: 'Returned cached response'}

Implication: adding an abortController to the requests is causing the issue. But... what if I leave the abortController there... but simply don't invoke it in useEffect? Once again: works fine, with an identical stream of debug messages as above. So, the problem isn't the abortController being present, but invocation of it.
(To be exhaustive: I happen to have an axios interceptor which does some routine error-handling for me. That interceptor returns errors as rejected promises. Could that be the issue? I disabled it. After that, caching still fails, and with the same debug signature. There's nothing else in the interceptor pipeline between axios and a-c-i.)
My hypothesis:

we know that when axios cancels a request, it returns an error to the response interceptor pipeline, with a message of 'cancelled'.
I haven't read the a-c-i source, but I think what's maybe happening is that: if a-c-i receives duplicate requests and one of them fails with an error, a-c-i refuses to cache the response to the other, successful request. This makes sense.
However, does this make sense: a-c-i should filter out any errors related to a legitimate cancellation (those with a message of 'cancelled'), which would not only be more compatible with axios' expected behavior, but also have the side-effect of fixing the problem caused by StrictMode. ??
Or, at a minimum: use the docs to advise people not to combine a-c-i with cancellable requests, as that will break things. a-c-i by itself will do a great job of catching and suppressing the duplicates, so let a-c-i take care of all that for you. Downside to this: getting duplicate responses is still generally a Bad Thing, even if you avoid burdening your API server with the duplicate requests. It often results in writing duplicate data to state managers, and is pretty hard to avoid. So... I'd suggest it's actually important to support both cancellation and caching, together, as "defense in depth."

Thank you for a great library. This is an edge-case here, and hard to predict. I hope this documentation of the situation is helpful to... someone.

Hey @xml super thanks for this detailed bug report. Would you mind creating a reproducible example so that I can test it out?
If you are using cancellation to prevent doubling requests upon renders, axios cache Interceptor does it by default and no need to manually implement cancelation.
With this Interceptor, you may only want to use cancellation if you do not need that request anymore and will not request it again.
However, it should not behave like this. Happy to debug a reproducible example...

What's the error shown here?
// <before>
{id: '578315523', msg: 'Caught an error in the request interceptor', data: {…}}

The error shown is the expected Axios canceled error:
data: {
  error: CanceledError
  code: "ERR_CANCELED"
  config: {transitional: {…}, adapter: 'xhr', transformRequest: Array(1), transformResponse: Array(1), timeout: 0, …}
  message: "canceled"
  name: "CanceledError"
  stack: "CanceledError: canceled\n    at throwIfCancellationRequested (http://localhost:3001/static/js/bundle.js:43196:11)\n    at Axios.dispatchRequest (http://localhost:3001/static/js/bundle.js:43208:3)"
}

And yes, I fully understand that a-c-i can prevent duplicate requests from going out, thus saving latency and server load. What it cannot prevent (without aborting the second request) is the state manager receiving two copies of the same data. The fact that one copy came from cache doesn't help any...

Here's the link to a repo which shows the behavior: https://github.com/xml/a-c-i-issues
As it's C-R-A, all you need to do to run is npm install and then npm start. (Plus, I'm in the habit of using console.debug for all non-temporary console statements, so I apologize that requires setting the Log Level to "All Levels" in Chrome to see the debug messages from a-c-i.)
NOTE: I've noticed something super-weird which may be another issue? The second I augment this axios instance with a-c-i, it begins throwing CORS errors, but only in Chrome (Mac v116). Safari is fine...
So, to see the CORS error, open this repo in Chrome.
But, to just go straight to the error with cancelled requests preventing caching, use some other browser like Safari. If you then want to see caching behaving normally, simply comment out App.js line 18: return () => controller.abort();

NOTE: I've noticed something super-weird which may be another issue? The second I augment this axios instance with a-c-i, it begins throwing CORS errors, but only in Chrome (Mac v116). Safari is fine...
So, to see the CORS error, open this repo in Chrome. Note that I tried adding axios CORS-related overrides, but that didn't help at all.

Regarding the CORS error, this is a well known problem users may have when using a-c-i since #437. Searching CORS on this repository issues would've shown some examples of it. However I did not know that it wasn't showing anything on the documentation search. I just updated it, so now users may solve this easier.
.

Hey, after debugging, this problem is the exact one I described at https://github.com/arthurfiorette/axios-cache-interceptor/issues/612. I'll try to resolve it asap. Thanks for the detailed debugging information and reproducible example.

Released at v1.3.0


CRITICAL vulnerability: bump jackson from 2.6.7 to 2.9.10

Vulnerability Information
Bumps jackson-databind from 2.6.7 to 2.9.10.
Listed dependency com.fasterxml.jackson.core:jackson-databind contains vulnerable methods which are called from this project. This vulnerability appears to affect jackson-databind package versions lower than <IP_ADDRESS> (excluding). The vulnerability has been fixed in version <IP_ADDRESS>, as can be seen from the linked CVE or package release notes -
the micro-patch of <IP_ADDRESS> refers to the fix of this vulnerability.
The other jackson packages were also bumped in order to keep the version compatibility with the updated jackson-databind 2.9.10 package.

Property
Value

 Linked CVE
CVE-2019-14379

 Number of affected methods
1

Severity
CRITICAL

Current version
2.6.7

Updated version
2.9.10

Backwards Compatibility
True

Vulnerable method calls

Methods in this repository
Used package methods
Origin vulnerable method

org.embulk.util.guess/SchemaGuess.guessType(final Object value)
com.fasterxml.jackson.databind/ObjectMapper.readTree(String content)
com.fasterxml.jackson.databind.deser.std/EnumSetDeserializer(JavaType enumType, JsonDeserializer<?> deser)

org.embulk.util.guess/SchemaGuess.guessType(final Object value)
com.fasterxml.jackson.databind/ObjectMapper.readTree(String content)
com.fasterxml.jackson.databind.deser/BasicDeserializerFactory.createMapDeserializer(DeserializationContext ctxt, MapType type, BeanDescription beanDesc)

What do the columns represent?
The 1st column in the table indicates the method in this repository that was found to be affected by vulnerable methods from the jackson-databind package.
The 2nd column indicates the jackson-databind method that was directly called from this repository.
The 3rd column indicates the origin vulnerable method in the jackson-databind package. According to our dataset, this is one of the methods that produces the CVE-2019-14379 vulnerability. This method was found to be internally chain-called in the jackson-databind package by the method listed in column 2.
How were the results generated?
This vulnerability was analyzed specifically for usage in this project using the FASTEN Project. Statical method-level analysis was used to check for usage of vulnerable methods in the project.
Method calls between your project and jackson-databind have been mapped using a directed graph. From this graph, it could be then be seen whether any vulnerable jackson-databind methods are being called from within your project.
Research Scope
We are a team of 3 BSc Computer Science students at the TU Delft. Our goal is to conduct research on how developers react to method-level vulnerability information that affects their projects. We would highly appreciate if you could help us with our research and please tick statements which apply to you below.
First impression checklist

[ ] I have read this pull request description.
[ ] I was aware of this dependency vulnerability affecting my project before being informed by this Pull Request.
[ ] I was convinced by the provided method information that this vulnerability indeed affects my project.
[ ] After seeing the provided method-level information, I plan on fixing the vulnerability.

After fixing vulnerability checklist

[ ] I found that the provided method information has made my process of dealing with the vulnerable dependency easier.
[ ] I have given priority to the task of fixing the vulnerability over other project tasks that are yet to be completed.
[ ] I would like to receive this kind of method information in future vulnerable dependency Pull Request descriptions.

Hi, I am contacting you on behalf of the research team from the Technical University of Delft, The Netherlands. In our recent study, we have carefully selected a limited number of active and professional repositories from the open-source community to learn from. So every feedback counts! :)
We appreciate it if you could contribute to our research by answering just a few questions (either using the above checkboxes or the fully anonymous questionnaire from here: https://forms.gle/n6oXZUwYysMUnVDn6). This will take less than a minute.
Moreover, we will give credit to your repository in the upcoming paper.

Thanks for trying to contribute, but we are aware of it, and there is a reason for us that we still have to stay with 2.6.7 for a while. We'll work on updating it by ourselves after the blocker is resolved.


Text composables: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-text-composables?authuser=1#5
In which task and step of the codelab can this issue be found?
6. Add a new text element](https://developer.android.com/codelabs/basic-android-kotlin-compose-text-composables?authuser=1#5)
Describe the problem

No mention is made that in the Surface function, the modifier needs to be deletated, and only leaving the color.
at task 4, it mentions the following: "Before the BirthdayCardPreview() function, add a new function called BirthdayGreetingWithText(). Don't forget to add the @Composable annotation before the function because this will be a compose function emitting a Text composable." - Shouldn't the BirthdayGreetingWithText(). added before the @Preview(showBackground = true) line.
Task 6 introduces a Text() Composable, however, errors appear which can be corrected by updating the libraries.
Under Preview the function, under task 2 shouldn't the "@Preview(showBackground = false)" line be true, if not it could not update the Design view.

Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version: Electric Eel | 2022.2.2 Pathch 1
API version of the emulator: Pixel 6 Pro API 33
Additional information
Include screenshots if they would be useful in clarifying the problem.

Hi @Tllc
Thank you for writing in and bringing these issues to our attention.
The lesson has been updated to address the, and the revised lesson will be republished again in the near future.
Hope you are enjoying the course!
Regards.


Start of a contributing doc

Unsure where this PR should go and wanted to give you a chance to edit.

I think it would be good to be more specific, e.g. how Babel does it.

Can you please resubmit against master? I'm killing that branch.


feat: Add spinners to moon setup and moon teardown.

fixes: #12

@G3root Awesome stuff. Easier than expected.
For the PR to pass, can you run yarn version:bump:bin patch and push the changes.

@G3root Awesome stuff. Easier than expected.
For the PR to pass, can you run yarn version:bump:bin patch and push the changes.

Done

@G3root Ah, I wasn't expecting you to rebase against the develop branch. You'll need to fix the conflicts now :/

i'm new to these type of things . is it resolved ?

Thanks! I'll fix these minor issues in the development branch.


Cannot deploy to cloudflare

Environment

Operating System: Darwin
Node Version:     v18.16.1
Nuxt Version:     3.6.0
Nitro Version:    2.5.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      app, devtools, vite, build, vue, css, modules, postcss, components, strapi, image
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
I'm trying to deploy my site in SSR mode, but whenever I try either on pages or as a worker it fails. I think its because of google maps, whenever I add in @fawmi/vue-google-maps or vue3-google-map on a clean install the error happens, but this is my full package.json just in case its helpful.
Package.json:
"devDependencies": {
    "@nuxt/devtools": "latest",
    "@nuxt/image": "^1.0.0-rc.1",
    "@types/node": "^18",
    "autoprefixer": "^10.4.14",
    "nuxt": "^3.6.0",
    "postcss": "^8.4.24",
    "prisma": "^4.16.1",
    "sass": "^1.63.6",
    "sass-loader": "^13.3.2",
    "tailwindcss": "^3.3.2",
    "typescript": "latest",
  },
  "dependencies": {
    "@fawmi/vue-google-maps": "0.9.72",
    "@nuxtjs/strapi": "^1.9.3",
    "axios": "^1.4.0",
    "dayjs": "^1.11.8",
    "dotenv": "^16.3.1",
    "node-ical": "^0.16.1",
    "pinia": "^2.1.4",
    "postcode": "^5.1.0",
    "swiper": "^10.0.2",
    "v-calendar": "^2.4.1",
    "vite-svg-loader": "^4.0.0",
    "vue-imask": "^7.0.1",
    "vue-social-sharing": "^3.0.9",
    "vue3-tel-input": "^1.0.4"
  }

Wrangler.toml:
main = "./.output/server/index.mjs"
workers_dev = true
compatibility_date = "2022-09-01"
account_id = "***"
[site]
bucket = ".output/public"

Describe the bug
Build fails with error defineComponent is not defined. It fails during the deploy/publish to cloudflare stage, as below:

Additional context
I have followed https://nitro.unjs.io/deploy/providers/cloudflare but keep hitting this same error and I don't know where to even begin debugging this. Does anyone have any ideas?
Logs
No response

Which version of wrangler are you using? I remember that a few weeks ago I was checking wrangler version 3.x and I couldn't come to an agreement with it in terms of building and with 2.20.0 everything worked beautifully.

Would you provide a reproduction? 🙏
My guess is that perhaps you need to add the google map library to build.transpile.

@oritwoen I am using wrangler 3 but I have a basic test nuxt 3 app which can deploy using 3, so I'm not sure its that, but thank you for the suggestion!
@danielroe I just spent the morning ripping it apart more to determine where the issue lies, as today the google maps package seemed to work. I managed to route it down to the vue-imask package and its Mask component that I am using so I added that package to build.transpile and that seems to of worked! What does this actually do? How do I know when I need to add packages to this? Thank you so much for your help!
Another quick question about cloudflare if thats okay, is there a preference between using a worker or pages for a nuxt ssr site that utilises the server for apis too? I'm new to using cloudflare and don't understand the difference between the two for hosting nuxt. Thanks!

Great work debugging.
Using build.transpile ensures we process the source code of the dependency with nuxt/vite plugins. (For example, I think this likely would ensure that it imports the 'same' vue dependency as the rest of the Nuxt app.) Normally you shouldn't need to add packages to this, but it is a useful escape-hatch when you encounter bugs.
For Cloudflare, I would recommend Pages. It is just as good for APIs and is the direction CF will be developing their platform.

@danielroe ahh I see, thank you so much you've been really helpful!


the file X_train_256_v2.npy can't be build?

respected sir，I come from gregwchase/eyenet ---2018, I saw your message in the issue.May I ask how you solve the question that the file X_train_256_v2.npy can't be build?

Hi @YUN-XIAO-MO , the file X_train_256_v2.npy that you want to create is just the numpy array (i.e. .npy or .npz).

When I initially worked on the project, I tried to build the numpy array based on the this and this, but found that it is not the ideal way to do it. Because if you create a numpy array on training images(X_train) then I will be of size ~14GiB. And when training a model you have to load that ~14GiB of numpy array in the RAM. Which requires more RAM and computation.
So, I suggest if you can use the flow_from_directory then you can augment the images on fly, during model training. You can find more resources on Keras Website and its explanation of Medium

I'am glad that you responsed quickly.
I did get the warn that the RAM of the GPU is not enough.
So,I decrease the training set,I picked a little piece from the whole training set to try the model.
But my computer only have one GPU, I changed the code from gregwchase to fit my computer.
here is my code.
I use X_train to try the model, but i got a bug,I show you the traceback:
Splitting data into test/ train datasets Reshaping Data X_train Shape:  (2462, 256, 256, 3) X_test Shape:  (616, 256, 256, 3) Normalizing Data y_train Shape:  (2462, 2) y_test Shape:  (616, 2) Training Model 2022-01-25 14:05:22.483986: I tensorflow/core/platform/cpu_feature_guard.cc:151] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX AVX2 To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags. 2022-01-25 14:05:24.082647: I tensorflow/core/common_runtime/gpu/gpu_process_state.cc:214] Using CUDA malloc Async allocator for GPU: 0 2022-01-25 14:05:24.085044: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1525] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 1669 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 3050 Laptop GPU, pci bus id: 0000:01:00.0, compute capability: 8.6 Model flattened out to:  (None, 438048) 2022-01-25 14:05:24.516928: W tensorflow/core/framework/cpu_allocator_impl.cc:82] Allocation of<PHONE_NUMBER> exceeds 10% of free system memory. Traceback (most recent call last):   File "D:\Desktop\Python_WorkSpace\workspace\EYE\src\cnn_test.py", line 154, in <module>     model = cnn_model(X_train=X_train,   File "D:\Desktop\Python_WorkSpace\workspace\EYE\src\cnn_test.py", line 83, in cnn_model     model.fit(X_train, y_train, batch_size=batch_size, epochs=num_epoch,   File "D:\Anaconda3\envs\tensorflow\lib\site-packages\keras\utils\traceback_utils.py", line 67, in error_handler     raise e.with_traceback(filtered_tb) from None   File "D:\Anaconda3\envs\tensorflow\lib\site-packages\keras\engine\data_adapter.py", line 1420, in _make_class_weight_map_fn     class_ids = list(sorted(class_weight.keys())) AttributeError: 'str' object has no attribute 'keys'
Would you mind helping me with this problem.

Hi @YUN-XIAO-MO , I was not able to properly debug the code, would be mind providing detail about what changes you made in your script from the originals. Plus, what you wanted to achieve.
And if you can provide the full error logs to better understand the issue.

Thank you, honourable  sir. @Tirth27
I uploaded my details。
I just want to make the model work。

If you look at Keras Model APIs class_weight in the model.fit() takes dictionary, but you passed the string.
Direct quote from the website:

class_weight: Optional dictionary mapping class indices (integers) to a weight (float) value, used for weighting the loss function (during training only). This can be useful to tell the model to "pay more attention" to samples from an under-represented class.

Also, you might be interested in this discussion on StackOverflow