-
Updated
Apr 27, 2022 - JavaScript
marketplace
Here are 875 public repositories matching this topic...
-
Updated
Jul 8, 2022 - PHP
-
Updated
Jul 7, 2022 - PHP
-
Updated
Jun 10, 2022 - Ruby
-
Updated
Jul 8, 2022 - TypeScript
It seems that the number of joining clients (not the num of computing clients) is fixed in fedml_api/data_preprocessing/**/data_loader and cannot be changed except CIFAR10 datasets.
Here I mean that it seems the total clients is decided by the datasets, rather the input from run_fedavg_distributed_pytorch.sh.
https://github.com/FedML-AI/FedML/blob/3d9fda8d149c95f25ec4898e31df76f035a33b5d/fed
-
Updated
Oct 19, 2021 - PHP
Most of our current tests mock away the DB because they're focused on the application logic and external API. We have seen changes breaking some DB queries without being caught by tests from time to time. We should improve the situation by adding tests that run the DB queries defined in our entity / DTO repositories and assert no DB error, just to ensure that the queries are consistent with the sc
-
Updated
May 4, 2022 - JavaScript
-
Updated
Apr 26, 2022 - Swift
-
Updated
Jul 4, 2022 - C#
-
Updated
Apr 4, 2022
-
Updated
Jun 20, 2022 - TypeScript
-
Updated
Jul 7, 2022 - JavaScript
-
Updated
Jun 22, 2022 - PHP
-
Updated
Nov 7, 2021 - JavaScript
-
Updated
Jul 5, 2022 - PHP
-
Updated
Jul 5, 2022 - PHP
-
Updated
Jan 16, 2019 - PHP
-
Updated
Jul 7, 2022 - C#
-
Updated
Jul 1, 2022 - TypeScript
-
Updated
Jul 5, 2022 - PHP
We need to sync the issues assigned to users from Github, so when someone is assigned to Github, the user assigned should be assigned on Gitpay as well. And we expect that the user is notified about this change by email.
We have two scenarios:
- User assigned on Github is registered on Gitpay
- User assigned on Github is not registered on Gitpay
The email should follow this template:
Add tests for price simulation, totals, taxes (net & gross)
-
Updated
Jun 13, 2022 - C++
-
Updated
Jul 6, 2022 - JavaScript
-
Updated
Mar 27, 2022 - Ruby
Improve this page
Add a description, image, and links to the marketplace topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the marketplace topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Improve the tier prices feature - add info like "Buy 2 in x.xx$ and save x%"