Creation of apps indicadores, familias, becas

What's this PR do?
This pr creates the django apps described in the document django apps, required for the implementation of the database models and future development of the project.
Where should the reviewer start?
The reviewer should check that all the apps below number five in the document are properly named and documentes.
How should this be manually tested?
N/A
Any background context you want to provide?
N/A
This template was adapted ~stolen~ from Quickleft/Sprint.ly

Codecov Report

Merging #8 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop       #8   +/-   ##
========================================
  Coverage    61.34%   61.34%
========================================
  Files           20       20
  Lines          119      119
========================================
  Hits            73       73
  Misses          46       46

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 271b2bc...d76993f. Read the comment docs.


feat:[PIPE-20336]: Add info regarding repo, branch,PR message display in UI

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6697ed123d3ccff0ffe218f3--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6697ed27c61fe9f151cf8be9--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6697f1259336bf4bc817cfe0--harness-developer.netlify.app


Improve webhook response

Describe the bug
Not a bug, is a feature improvement
When debugging github webhook you can read the response from lagoon.  That response does not contain any information about the results of the webhook, i.e. build_triggered: true
To Reproduce
Steps to reproduce the behavior:

Misconfigure a project and fire the webook
The response does not contain information about the result

Expected behavior
Consider different http response status codes or add results info to the response body
Additional context
Our repo was misconfigured, however, when reviewing the webhook response it shows 200 status and the response body is just a json blob about the commit.

@jordotech
thanks very much for your report! Just a question, which webhook system did you use exactly? as the rest2tasks system will soon be deprecated and we will only support the GraphQL system.

@Schnitzel
Using https://hooks.lagoon.amazeeio.cloud in github as described in the docs (lagoon project: ipsum): https://lagoon.readthedocs.io/en/latest/using_lagoon/configure_webhooks/


Update sql project already exists error message

This PR fixes #11504

Coverage increased (+0.1%) to 37.815% when pulling 665d1fab8867d80ec6ff362f5deefbe28380f21a on kisantia/updateErrorMessage into 9c1168ba3bbe2c50b2e8899595c9d5a9d8deab8b on main.


Update s3.md

I am unsure if this problem is unique to trying to apply this policy to a bucket using Terraform, but I was unable to use the policy straight from the docs to configure my storage backend's bucket permissions. The error I would receive from Terraform is as follows;
Error putting S3 policy: MalformedPolicy: Missing required field Principal

I recreated the policy using the AWS policy generator and it added the principal section.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

/ping @dmcgowan for a review.

@mark-church PTAL. Thanks.


[Bug] Multiple Buttons Results in Wrong Button Being Run

It seems like if I have multiple buttons on one page it puts the wrong template on the new note and puts it in the wrong folder. I tried it both with and without templater scripts and got the same result.
Example:

I pressed the Day Journal button which should have input the Day template, but instead put the Code Diary template.
It also put it in the wrong folder, it should have gone to Journal but instead went to Workout Log.

First of all, excellent use of buttons I'm proud.
Secondly, ohhh noooo that's not good! I will try to recreate and fix.
Out of pure curiosity, if you add a button block-id below each of those buttons, does the problem get solved?

wow, this was a really dumb error on my part. I've fixed it and am cutting a release now!

@SlRvb did the 0.4.8 release fix this? If yes, wanna close the issue?

Finally had a chance to test it out and it works now, thanks!


finally

I can't understand what is the difference in the program behavior between finally block and just code without it. Isn't the code below the same as written with the finally block?
try
{
// Invalid conversion; obj contains a string, not a numeric type.
i = (int)obj;
        // The following statement is not run.
        Console.WriteLine("WriteLine at the end of the try block.");
    }
        // Report that the finally block is run, and show that the value of
        // i has not been changed.
        Console.WriteLine("\nIn the finally block in TryCast, i = {0}.\n", i);

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

Any code in the try block that follows the statement that throws the exception is not executed.


[Train SCNN-TensorFlow] : <class 'tensorflow.python.framework.errors_impl.CancelledError'>, Enqueue operation was cancelled.

When I train the SCNN-TensorFlow, the error trun out.
This is the error:

Epoch: 90094 loss_ins= 0.003494 (0.003464) loss_ext= 0.000006 (0.000006) accuracy= 0.988932 (0.989564) accuracy_back= 0.997696 (0.997700) mean_time= 0.401934s
Epoch: 90095 loss_ins= 0.003441 (0.003463) loss_ext= 0.000006 (0.000006) accuracy= 0.990375 (0.989573) accuracy_back= 0.997693 (0.997699) mean_time= 0.402190s
Epoch: 90096 loss_ins= 0.003497 (0.003464) loss_ext= 0.000006 (0.000006) accuracy= 0.990354 (0.989581) accuracy_back= 0.997650 (0.997699) mean_time= 0.402138s
Epoch: 90097 loss_ins= 0.003340 (0.003462) loss_ext= 0.000006 (0.000006) accuracy= 0.988602 (0.989571) accuracy_back= 0.997772 (0.997700) mean_time= 0.402131s
Epoch: 90098 loss_ins= 0.003446 (0.003462) loss_ext= 0.000006 (0.000006) accuracy= 0.989145 (0.989567) accuracy_back= 0.997752 (0.997700) mean_time= 0.402337s
Epoch: 90099 loss_ins= 0.003515 (0.003463) loss_ext= 0.000006 (0.000006) accuracy= 0.988700 (0.989558) accuracy_back= 0.997706 (0.997700) mean_time= 0.402565s
Epoch: 90100 loss_ins= 0.003551 (0.003464) loss_ext= 0.000006 (0.000006) accuracy= 0.988906 (0.989551) accuracy_back= 0.997696 (0.997700) mean_time= 0.402450s
2019-10-25 04:49:09.973449: W tensorflow/core/kernels/queue_base.cc:277] _1_data_augmentation_1/input_producer/input_producer: Skipping cancelled enqueue attempt with queue not closed
2019-10-25 04:49:09.973524: W tensorflow/core/kernels/queue_base.cc:285] _3_batch/fifo_queue: Skipping cancelled dequeue attempt with queue not closed
2019-10-25 04:49:09.973571: W tensorflow/core/kernels/queue_base.cc:277] _0_data_augmentation/input_producer/input_producer: Skipping cancelled enqueue attempt with queue not closed
2019-10-25 04:49:09.973608: W tensorflow/core/kernels/queue_base.cc:277] _4_prefetch_queue_1/fifo_queue: Skipping cancelled enqueue attempt with queue not closed
2019-10-25 04:49:09.973652: W tensorflow/core/kernels/queue_base.cc:277] _5_batch_1/fifo_queue: Skipping cancelled enqueue attempt with queue not closed
I1025 04:49:09.974268<PHONE_NUMBER>20416 coordinator.py:224] Error reported to Coordinator: <class 'tensorflow.python.framework.errors_impl.CancelledError'>, Enqueue operation was cancelled
[[{{node batch_1/fifo_queue_enqueue}}]]

I have googled this soultion:
coord = tf.train.Coordinator()
threads = tf.train.start_queue_runners(sess=sess, coord=coord)

but it not work.

I have not met this problem before. You need to debug by yourself.


Print pod info on error

Signed-off-by: Raul Sevilla<EMAIL_ADDRESS>Description
We're currently blind when a benchmark fails.


Fails on checking for recipes

Describe the bug
When either using a package/dmg or a URL it constantly fails when searching for existing recipes
To Reproduce
Steps to reproduce the behaviour:

Download file or paste download URL in the GUI
Run by clicking Do It

Expected behaviour
Recipe Robot to produce desired recipes
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

macOS: 10.15.7 and 11
Recipe Robot Version: 2.0.0
which python: My system says /usr/bin/python but recipe-robot should use /usr/local/autopkg/python
python --version: My Systems says Python 2.7.16 but it should use the Python bundled with AutoPkg 2.2

Additional context
Full output from a sample run via the GUI
[WARNING] I'm processing the input path as a GitHub repo URL, but you may have wanted me to treat it as a download URL.
[ERROR] I encountered this error while checking for existing recipes:
Processing: https://github.com/betaflight/betaflight-configurator/releases/download/10.7.0/betaflight-configurator_10.7.0_macOS.dmg
Input path looks like a GitHub URL.
Getting GitHub repo...
GitHub repo is: betaflight/betaflight-configurator
Getting app name...
App name is: betaflight-configurator
Getting GitHub description...
GitHub description is: Cross platform configuration tool for the Betaflight firmware
Getting information from latest GitHub release...
Multiple formats available.
GitHub release download format is: dmg
GitHub release download URL is: https://github.com/betaflight/betaflight-configurator/releases/download/10.7.0/betaflight-configurator_10.7.0_macOS.dmg
Download URL is: https://github.com/betaflight/betaflight-configurator/releases/download/10.7.0/betaflight-configurator_10.7.0_macOS.dmg
Downloading file for further inspection...
Downloaded to /Users/p.cossey1/Library/Caches/Recipe Robot/2020-10-23_12-19-44_377901/betaflight-configurator_10.7.0_macOS.dmg
Determining download format...
File extension is dmg
Opening downloaded file...
Successfully mounted disk image
Validating app...
This app seems valid
Getting bundle name...
Bundle name is: betaflight-configurator
Bundle name differs from the actual app filename.
Actual app filename: Betaflight Configurator.app
Getting bundle identifier...
Bundle identifier is: com.nw-builder.betaflight-configurator
Checking for a Sparkle feed...
No Sparkle feed
Looking for version key...
Version key is: CFBundleVersion (10.7.0)
Looking for icon...
Icon is: /Users/p.cossey1/Library/Caches/Recipe Robot/2020-10-23_12-19-44_377901/unpacked/Betaflight Configurator.app/Contents/Resources/app.icns
Gathering code signature information...
This app is not signed
Getting developer name from GitHub...
GitHub developer is: The Betaflight Open Source Flight Controller Firmware Project
Searching for existing AutoPkg recipes for betaflight-configurator...
                                _[]_
                                [xx]
                               q-||-p
                                 ||
                               _/  \_

Hi @paul-cossey - Thanks for finding this bug! I think I fixed it in RC2, available here. Could you try that out?

Thanks for fixing so quickly! I've created a couple of recipes with it:
https://github.com/paul-cossey/AutoPkg-Recipes/tree/master/Causality
https://github.com/paul-cossey/AutoPkg-Recipes/tree/master/betaflight-configurator
But they both fail when I try and run the .munki recipe though AutoPkgr (I'm not 100% sure the problem isn't me!).
local.munki.Causality.nua | Error in local.munki.Causality.nua: Processor: URLDownloader: Error: Command '['/usr/bin/curl', '--silent', '--show-error', '--no-buffer', '--dump-header', '-', '--speed-time', '30', '--location', '--url', 'Paul Cossey', '--fail', '--output', '/Users/Shared/AutoPkgr/Cache/local.munki.Causality.nua/downloads/tmpg73gc5it']' returned non-zero exit status 3.
local.munki.betaflight-configurator.nua | Error in local.munki.betaflight-configurator.nua: Processor: URLDownloader: Error: Command '['/usr/bin/curl', '--silent', '--show-error', '--no-buffer', '--dump-header', '-', '--speed-time', '30', '--location', '--url', 'https://github-production-release-asset-2e65be.s3.amazonaws.com/60735171/78d33f80-ae6d-11ea-8868-1dc4ddfd51d0?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201025%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201025T111945Z&X-Amz-Expires=300&X-Amz-Signature=f1e61b464aee8a46ccacb7f5850180aa2deef7e4eb0dffac7c6c56cb0861cc4a&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=60735171&response-content-disposition=attachment%3B%20filename%3Dbetaflight-configurator_10.7.0_macOS.dmg&response-content-type=application%2Foctet-stream', '--fail', '--output', '/Users/Shared/AutoPkgr/Cache/local.munki.betaflight-configurator.nua/downloads/tmp1agxht_w']' returned non-zero exit status 22.
A quick look at the download recipe for Causality has my name as the URL!
<dict> 			<key>Arguments</key> 			<dict> 				<key>filename</key> 				<string>%NAME%.dmg</string> 				<key>url</key> 				<string>Paul Cossey</string> 			</dict> 			<key>Processor</key> 			<string>URLDownloader</string> 		</dict> 		<dict>
I'll create a couple more (probably tomorrow now) for some additional testing

Very strange that your name would end up in the URL. I'm not sure how that would even happen, and I can't reproduce it.
I've been pushing forward fixing other bugs, so here's a new (possibly final) RC to try: https://github.com/homebysix/recipe-robot/releases/tag/v2.0.0-rc3

Super weird! RC3 does seem to resolve the issue with my name being added as the download URL for Causality
<key>filename</key> 				<string>%NAME%.dmg</string> 				<key>url</key> 				<string>https://releases.hollywoodcamerawork.com/cau/2.1.14-96ec39c7/Causality%202.1.14%20Installer.dmg</string>
Almost end of play for us today, but I'll have a further play about tomorrow all being well.

I've now recreated the Casualty and Betaflight-configurator recipes and also a brand new one. All download and import into Munki with RC3 with no issues. As an added bonus Recipe Robot seems to be much quicker creating the recipes now.
Thanks!

Great! I'd still love to know why your name was appearing in the URL, but willing to write that up as a one-off glitch since nobody else has reported it.


Use the default google_protobuf package name

Description
Remove all aliases for google/protobuf imports and use the default package name (google_protobuf) across the board in Fabric.
Motivation and Context

Fixes #1899
How Has This Been Tested?
This PR does not contain a new test case, as it's a compile time/import fix.

Checklist:

[x] I have added a Signed-off-by
[x] Either no new documentation is required by this change, OR I added new documentation
[x] Either no new tests are required by this change, OR I added new tests
[x] I have run goimports, go vet, and golint. I have cleaned up all valid errors and warnings in code I have added or modified. These tools may generate false positives.  The goal is clean, consistent, and readable code.

Signed-off-by: JonathanLevi

Thanks, LGTM


[console] Pass rake env variables on to remote process.

These are env variables defined as part of the arguments given to rake
For instance:
rake ow:console[production] MONGODB_SOCKET_TIMEOUT=30

…would invoke the remote process with:
env MONGODB_SOCKET_TIMEOUT=30 bundle exec rails console

:warning: This patch is made against the 0.0.13 release, because the current 0.1.0 release has a berkshelf version requirement that’s incompatible with Gravity’s current bundle (berkshelf v4.3.5 has a hard = 0.16.0 requirement). Thus this won’t apply to master.
Is it possible to upgrade the berkshelf dependency? Newer versions don’t have this dependency any longer. Alternatively we could make a 0.0.14 release so that this patch can at least be pulled into Gravity.

Would this take precedence over a from_env declaration? I would expect it to override any env pulled in via that manner, but it's not clear to me.

I’m unfamiliar with from_env specifically, but I would assume the answer is yes, unless from_env sets the env variables from within the app process?

So it looks like from_env is overriding the ENV array from within the process so I would expect it to override your arg.

Reading the source, isn’t from_env meant to copy remote env variables?

That's right, it copies vars over from our OpsWork stack settings.

Yeah according to the README that’s what it does: https://github.com/artsy/momentum#owconfigfrom_envtoaws_idaws_secret

So were you asking if specifying a remote env variable with rake … FOO=bar would override FOO locally that’s retrieved from a remote stack? If so, then the answer would be no, because from_env is ran after rake has set env variables from ARGV.

That's exactly what i was wondering... makes sense!

Also @alloy yes I don't see why we can't upgrade the Berkshelf dependency elsewhere.

As written, this only impacts the ow:console command that SSH-es to the remote server and runs the console there, so it shouldn't conflict with ow:config:from_env, which is focused on supplying ENV values to the following rake tasks locally.
There is potential for overlap between this and what's supplied by figaro and the config/application.yml file it reads from on the remote server. If a value is already supplied in that file (which is currently populated via Opsworks' stack JSON), it will still overwrite any value passed this new way, I think. Is that acceptable?

Do you think the latest version would be ok? I have no clue about berkshelf or how to vet its versions.

If a value is already supplied in that file (which is currently populated via Opsworks' stack JSON), it will still overwrite any value passed this new way, I think.

Correct. Whatever is set in the shell previously would be overridden for the duration of the command.

Is that acceptable?

I think so.
The idea is that explicitly set (short lived) values should override defaults so that you can override them when really necessary.

@alloy go for the latest version!

There is potential for overlap between this and what's supplied by figaro and the config/application.yml file it reads from on the remote server. If a value is already supplied in that file (which is currently populated via Opsworks' stack JSON), it will still overwrite any value passed this new way, I think. Is that acceptable?

After testing it appears that figaro does not set env variables if they have been provided by the parent process. i.e. this PR will allow you to override env variables otherwise set by figaro.

@izakp So… Trying to satisfy the berkshelf version requirements (and those of its transitive dependencies) turned out to be hard. Only < v6 will work on Ruby 2.2.2 (which is what Gravity runs on) and it seems like Berkshelf v5 just moved the celluloid dependency to be a transitive dependency, so this still leads to an unsolvable graph.
Does Gravity actually need berkshelf? I added a commit that removes the dependency from momentum, in favour of the requiring application to provide it. Please review this very hard.

Regarding overriding those config values provided in the application.yml... great! This will be very useful.
I'm not sure how to handle the Berkshelf incompatibility. Removing it is a big breaking change, since other projects use this utility and presumably don't already have Berkshelf in their bundle.

I'm not sure how to handle the Berkshelf incompatibility. Removing it is a big breaking change, since other projects use this utility and presumably don't already have Berkshelf in their bundle.

Yeah, me neither. Alternatively I revert to my original suggestion to back port this to a 0.0.14 release just for Gravity?

Ok, went ahead and did that instead https://github.com/artsy/momentum/pull/24

Ok, seeing as this PR no longer introduces breakage and was already approved, I’m going to merge this.


[AutoPR scheduler/resource-manager] chore: jsonfmt scheduler

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6239

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/5806


Upgrade Nexus from 3.45.0-01 to 3.52.0-01

Description of changes

Upgrade the nexus package from 3.45.0-01 to 3.52.0-01 (release notes)

Switch the URL to the one listed in the public documentation

Partially fix a bug with the postPatch behavior modifying bin/nexus.vmoptions (detailed in the specific commit and discussed further below)
Update the URL for the meta.homepage, since the old one no longer resolves

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)
[x] Tested, as applicable:

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

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

[ ] Fits CONTRIBUTING.md.

Discussion of the change to /var/lib/sonatype-work

Currently, the bin/nexus.vmoptions file contains several instances of ../sonatype-work. The intent of this appears to be to enable a user to download the tgz, unpack it, and run from that folder directly (documented here). This would already be a problem, as the nix store is not intended to contain writable data folders.
The existing package attempts to make relative paths absolute with the --replace =. =$out line. However, the result is that the <jvm_option>=../sonatype-work/<subfolder> paths end up something like <jvm_option>=/<nix>/<store>/<path>/./sonatype-work/<subfolder>, which does not exist.
The NixOS module avoids this problem by defining its own equivalent of nexus.vmoptions and overriding it through the VM_OPTS_FILE environment variable, so it is unaffected by this change.
Adding this change sets the data folder to be the same as the default for the NixOS module. This does not result in a working package by itself, but does enable the user to get it in a working state by creating that directory.
I attempted to research if there was an existing pattern for how NixOS prefers handling packages like this that expect to have a writable data folder. Since it is a server application that's likely to be run as a service, using the XDG folder specification didn't make sense to me. I found this forum thread, which seemed to be a second indicate that /var/lib/<folder>/ was an acceptable pattern. If there is a different approach that is preferred, let me know and I will make whatever changes that are appropriate.

Squashed the commits down to a single commit with that message. Thanks for your help!


remove stray yellow pixel

Before:

After:

Images are blurred because of resizing - the actual images are not

LGTM. Thank you!


Added Cloud Run Support

Added Cloud Run Support by creating a separate Workflow and documented the steps which need to be followed along with screen shorts
https://github.com/serverpod/serverpod_docs/pull/4
List which issues are fixed by this PR. You must list at least one issue.
Deployment Support to Cloud Run
Pre-launch Checklist

[x] I read the Contribute page and followed the process outlined there for submitting PRs.
[x] This update cointains only one single feature or bug fix and nothing else. (If you are submitting multiple fixes, please make multiple PRs.)
[x] I read and followed the Dart Style Guide and formatted the code with dart format.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///), and made sure that the documentation follows the same style as other Serverpod documentation. I checked spelling and grammar.
[ ] I added new tests to check the change I am making.
[x] All existing and new tests are passing.
[x] Any breaking changes are documented below.

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

For this to be approved, it need full support of all features in the AWS deployment.

Deployment of new versions through Github.
Support for autoscaling.
Separate instances for Postgres and Redis.
Support for file uploads.
Correct setup for certificates and domain names.

I think at the current state, this may be better off as a tutorial. I would be happy to link to it from the documentation.

Thanks for the suggestion.
As of now when we do a push to GitHub it will create a new revision of service and migrate the traffic to the new one. The old one will still exist if some problem occurs we can change the traffic from new revision to old revision.
Cloud run automatically supports scalling we can even spin up 100 of serverpod service running within seconds.
We are packing our serverpod server into a docker( size ~30mb ) so that we can easily deploy them to any cloud services or even physical servers
As Suggested I will work on that postgres , redis , domain and certification part. And will make it as a complete solution and will keep you posted. If possible can you create this as feature and assign to me

We will soon be starting work on GCP support, this may be a nice starting point!

Hi @vlidholt  that's good to hear. Please let me know how can I help you 😃

Thank you! I started working on this now. Looks like a great entry point. :)

I've been working on GCP deployment over the past weeks. There is a GCP module up for review here:
https://github.com/serverpod/google_cloud_serverpod_gce/pull/1
I'll use this code as a base for the deployment, so @ajay-k07 will get credited as co-author.

I wanted to use serverpod for production apps, is it possible to deploy or should we wait for some for time?

We have added full support for Cloud Run or Compute Engine. The guides for deploying your Serverpod are available here:
https://docs.serverpod.dev/deployments/deployment-strategy


Fix documentation for copy 'n paste of example

Wanted to be lazy and copy 'n pasted the example. Did not work. Fixed the README.md so that others can be more successful in being lazy ;-).

aha, perfect, thanks!


a little typo in event.py Line:521

report typo

For output =
'onset' or 'step', the second column contains the value of the stim
channel immediately before "the the" event/step.

you can fix this your self by editing the file on github
https://github.com/mne-tools/mne-python/edit/master/mne/event.py
can you give it a try?

My pleasure! PR has been sent!


Make x86 database changes be committed only after contract execution is successful

As a contract developer, I don't want my smart contract to commit invalid state whenever an execution of it results in an error.
Right now when a smart contract causes a state change, that change is made immediately. As a result, if the contract runs out of gas or encounters some error,  the state change will remain and the contract might have an unexpected or inconsistent state afterwards. For this story, all database state changes should be added to a buffer. When the contract execution is confirmed to be successful, the buffer of changes should be committed to the database. Of course, when a contract tries to read a state, this buffer should be checked for pending changes before reading from the database.

done


How to generate 5 - frame snippets from ground truth

I wanted to test the SFMLearner on other kitti sequences apart from the 9,10.
How do I generate 5 frame snippets from the KITTI poses.txt

You can refer to this script I wrote:
https://github.com/yzcjtr/GeoNet/blob/master/kitti_eval/generate_pose_snippets.py


Allow specification of X and Y dimensions for auto resizing (so thumb is no fewer than X pixels in width and Y pixels in height upon resize)

Often when creating a thumbnail you're not sure the aspect ratio content editors will provide. Rendering a thumb that is no less than X pixels wide or Y pixels tall is useful in these situations. Fortunately, it's also easy to implement, and I've already done it, just needs to be tested on my end. Expect a pull request in the next couple days.

Pull request #16

maybe one could use the getThumb method from System\Models\File


Import grafana dashboards and datasources from cluster

What this PR does / why we need it:
Offers the possibility to collect configmaps from within the cluster and add the there stored dashboards/datasources to grafana. Adds a new service account with the needed permissions.
Details: Depending on the values, up to two sidecars are deployed in the pod. Those containers access the kubernetes api and watch on config map changes. Those are filtered for configmaps with a defined value. The files in those configmaps are stored in a shared folder and imported by grafana. When a configmap is removed, the connected file is removed too (and grafana removes it too)
Which issue this PR fixes
fixes  #5368
Special notes for your reviewer:

@zanhsieh @rtluckie

/assign @lachie83

Thank you @zanhsieh and @timstoop for your input. I worked on your remarks and hope to have covered all best practices now.

/assign

Please follow our RBAC best practices:
https://github.com/kubernetes/helm/blob/master/docs/chart_best_practices/rbac.md

@unguiculus Thank you for your remark. I changed the the rbac setting to be enabled by default, as described by the best practices. Sorry for missing that point. Hope I covered it completely now.

@unguiculus I adapted the PR to the current state of the grafana chart. Hope you can give me feedback again. Thank you for your time and patience

Thank you @unguiculus for your remarks. I changed it according to your requests.

/lgtm


How to use with meteor

Are there any examples showing how to use this with meteor?  I'm not sure how to show the errors on the form in a "meteor" way.

{{don't I need something here}}

Thanks,
Mike

The plugin manages error state for you, so Meteor shouldn't need to get involved. I've never used Meteor so I can't tell you anything more than that. Maybe someone on stackoverflow could help you out.

Actually it is working.  I pulled the trigger too early on opening an issue.  You're correct, you don't need and handlebar stuff inside that div.
Thanks,
Mike


make QuadraticHamiltonian a subclass of PolynomialTensor

Summary
Fixes https://github.com/Qiskit/qiskit-nature/issues/865
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

18 of 18 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 85.709%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
17062

Relevant Lines:
19907

💛  - Coveralls


Changed an error to warning for failure to optimise parameters in curve fit

ENH: adjusted error conditions for too many iterations to optimise parameters in scipy optimise curve fit.
What does this implement/fix?
Often when the error "Optimal parameters not found: Number of calls to function has reached maxfev = ..." is given perfectly usable results have been produced so raising an error is unhelpful so I have changed it to message (I would have preferred to use the warnings module but it appears to just not be showing anything).
Additional information
This was also complained about here, here and others.

Okay it seems I've broken something although the tests that failed seem to be unrelated to my changes

Okay it seems I've broken something although the tests that failed seem to be unrelated to my changes

@jagoosw I resolved merge conflicts for you. If you're happy with what this does now, please send an email to the mailing list proposing the change, mentioning the possible concern that users might miss the warning and think that the returned solution is optimal, and asking for opinions about whether the benefits outweigh the risks.

Oops that push was accidental. In the future, it's best to create a new feature branch rather than working in master.

I haven't heard back, and I cannot champion this change, so I'll go ahead and close this one.
I would support making this change in conjunction with:

deprecating full_output,
always returning all output in a bunch object, and
adding a success attribute to indicate whether fitting was successful or not.

But that would be a more substantial PR.


initial version

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3f6d8d7). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             master        #1   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         2
  Lines             ?        15
  Branches          ?         0
==========================================
  Hits              ?        15
  Misses            ?         0
  Partials          ?         0

Impacted Files
Coverage Δ

src/scaffold.js
100.00% <100.00%> (ø)

src/testing.js
100.00% <100.00%> (ø)

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 3f6d8d7...dc982b8. Read the comment docs.


refactoring of html templates and javascript code

Discussed in https://github.com/justpy-org/justpy/discussions/471

Originally posted by WolfgangFahl August 30, 2022
Currently justpy creates a html page for startup that is 2405 lines long.
Unfortunately this verbosity leads to hiding the clean structure behind the code which is shown below:
<!DOCTYPE html>
<html>
  <!--This is a justpy application using the tailwind.html template-->
  <head>
     <script>...</script>
     <title>JustPy</title>
     <link ...>
     <link ...>
   </head>
    <body style="" class="">
       <div id="components">
       </div>
       <script>...</script>
  </body>
</html>

the core Vue component 'app1'
var app1 = new Vue({
        el: '#components',
        data: {
            justpyComponents: justpyComponents
        },
        render: function (h) {
            var comps = [];
            for (var i = 0; i < this.justpyComponents.length; i++) {
                if (this.justpyComponents[i].show) {
                    comps.push(h(this.justpyComponents[i].vue_type, {
                        props: {
                            jp_props: this.justpyComponents[i]
                        }
                    }))
                }
            }
            return h('div', {}, comps);
        }
    });

The html is a mixture of css and javascript imports and declarations. A separation of concern is not visible and would IMHO be the core task of refactoring making sure that only a few lines of clean html are left that are commented to show what the parts do.
To get this new clean result i suggest to get rid of the Jinja templates and instead write the generator for the code as a pure python code with an object oriented structure. The logic to be used for version handling and other configuration task can then be implemented much clean and be tested and debugged. Jinja templates are executed out of the standard python debugging context and are a nightmare for testing and debugging. The extra value the templates seem to bring at first look does IMHO evaporate as soon as maintainance work as we need to do is to be done.
First step - replace %include
The explosion of html lines in the code is mostly from the use of the %include% option of the Jinja templates:
 {% include 'js/event_handler.js' %}
    {% include 'js/html_component.js' %}
    {% include 'js/quasar_component.js' %}
    {% include 'js/chartjp.js' %}
    {% include 'js/aggrid.js' %}
    {% include 'js/iframejp.js' %}
    {% include 'js/deckgl.js' %}
    {% include 'js/altairjp.js' %}
    {% include 'js/plotlyjp.js' %}
    {% include 'js/bokehjp.js' %}
    {% include 'js/katexjp.js' %}
    {% include 'js/editorjp.js' %}

we need to be able to talk about issues and debugging in code with comments like - there is a problem in line xyz of somecode.js in function somefunction ...

let justpy_core=new JustpyCore(
      this, // window
      'JustPy', // title
      false, // page_ready
      false, // result_ready
      0, // reload_interval
      false   // debug
    );

is now generated by the template.py modules's Context class
{% if page_options.redirect %}
        location.href = '{{ page_options.redirect|safe }}';
    {%endif %}
    {% if page_options.display_url is not none %}
        window.history.pushState("", "", '{{ page_options.display_url }}');
    {%endif %}
    var page_id = {{ page_id | safe }};
    var websocket_id = '';
    var use_websockets = JSON.parse('{{ use_websockets }}');
    var justpyComponents = {{ justpy_dict.replace('</' + 'script>', '</" + "script>') | safe }};


[Bug] Update from 4.9.6 to 4.11.2 build error

Describe the bug
$ react-scripts build
Creating an optimized production build...
Failed to compile.

<EMAIL_ADDRESS>Attempted import error: 'createProsePlugin' is not exported from '@milkdown/utils'.

with milkdown v.4.9.6 buid succeeded
To Reproduce
Steps to reproduce the behavior:
"build": "react-scripts build"
Desktop (please complete the following information):
macOS

maybe the problem is in version 4.11.2 build I see that in github createProsePlugin exist in utils and its exported
https://github.com/Saul-Mirone/milkdown/blob/main/packages/utils/src/atom/base-prose-plugin.ts
https://github.com/Saul-Mirone/milkdown/blob/main/packages/utils/src/index.ts#L2

What's your local version of @milkdown/utils in node modules?

Its have extra "declare" in my<EMAIL_ADDRESS>export declare const createProsePlugin:

Can you paste your package.json here? I need to confirm which package you're using having this problem.

I update all dependencies versions into v4.11.2 in this code sand box and everything works fine, I think removing node_modules and yarn.lock then try yarn install agian maybe helpful.

my bad.. After update it I have not remove yarn.lock (maybe the issue is with yarn).
Its work now thanks!
https://github.com/tagspaces/tagspaces-extensions/commit/c1de072ba2eb4600484a292f4f1c384ab529ea56#diff-0854bac2ae3884effc67a6052d96ab4021f1ec28bbc4f696df2e5487f6306ff5R31