Implement Email Validation

When registering an email automaticly send a verification email

Added APIS:
GET /api/users/{username}/emailaddresses
POST /api/users/{username}/emailaddresses/{label}/validate
Make sure we remove validated email and phonenumber when removing email
or phonenumber

@grimpy I'd like to keep the confirmation page for sms seperate since it is used on a mobile phone and optimized as such. For the email, I think a different confirmation page can be used that redirects you to the login after showing a nice message for a few seconds first.

@robvanmieghem required changes where made. Altough I would argue that all pages should be mobile friendly.


use giantswarm/cluster to render control plane resources

This pr: ..

is a nightmare

NOTE for reviewers: this PR is currently untested (and cannot be tested by the e2e tests yet). I'll be testing it manually and updating this PR with the results.

:point_up: this commit is worth viewing in isolation as it explains why the vspheremachinetemplate resources have been reworked quite heavily.

/run cluster-test-suites


Integration Test : Default ListenPort assignment in sever template

Add integration test to verify the default ListenPort ( plain text and SSL) when the ListenPort attribute is not set explicitly in WLST offline script or WDT model file
The PR covers 3 usecases
(a) No explicit port for Listen/SSL Port  in model/py script
(ItIntrospectVersion.java  and ItMiiCustomSslStore.java, ItT3Channel.java,ItTwoDomainsLoadBalancers.java )
(b) Explicit port with on-prem  default Listen (7001)  and  SSL (7002 ) port  (ProductionModeSecure.java)
(c) Explicit non on-prem default port such as  eg. 8001/8002 (already covered)
In case (a)  The runtime will be 7100/8100   (b) runtime will be 7001/7002. (c) runtime will be 8001/8002
Ref :  https://confluence.oraclecorp.com/confluence/display/ASDevWLS/Operator+and+WebLogic+network+ports+resolution
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/4761/ (parallel)
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/4762/ (sequential)

LG


Add dux command, rename dedux to undux

dux should do what the indexer does, in a blocking, synchronous manner. This would be useful for:

testing, when you want to ensure the indexer has finished before exercising the UI
immutable deployments of read-only datasettes, where you'd like the (eventual) power-user search to work w/o a background indexer running

As part of this, we'll fix up the names of the prepare/index functions, and create a cleaner boundary between the bits that expect Datasette's Database module and the bits that expect a sqlite3.Connection.


Requirements cannot be added to newly added NTs

After adding a NT to a Service Template Requirements that are added using the Pop-up are not stored.
This also happens after the Service Template is saved.
Only after a reload of the Service Template the Requirements can be added without any problems.

fixed in 64140c3d812c70a


Kinect v2 not found

I was trying libusb with the new usbdk backend on Windows 8.1. But usbdkcontroller.exe was unable to find the Kinect. usbdkcontroller.exe -n found two devices of the Kinect adapter (Hub devices), but the Kinect sensor was not found. I could see the Kinect sensor device in the Windows device manager, and a Microsoft driver is installed for it.
What can I do?

Hi,
Please collect binary UsbDk trace for kinect connection as described here: https://github.com/daynix/UsbDk/blob/master/Documentation/Tracing.txt#L52
Scenario should be:

Unplug your kinect
Run tracing
Plug the kinect back

Also please provide your USB topology (with kinect connected) as described here: https://github.com/daynix/UsbDk/blob/master/Documentation/UsbInfo.txt
Thanks,
Dmitry

usbdkcontroller-n.txt
MyUsbTree.txt
MyUsbTree.xml.txt
UsbDkTrace.etl.txt
(Remove .txt suffix from the .xml and .etl files)

Thanks for the logs. We will do the investigation.

Fixed in v1.00-12 by 6b21ddc78cb53e6885b67ca6ee68975a1db645aa

I confirm the Kinect is now detected.


fix soap encoding error

This has worked before. Has the standard always been soap-env etc? Is this a change that is compatible with most legacy devices? Has it been tested against easycwmp just for a start?

The build error is Just a docker secret issue.

This has worked before. Has the standard always been soap-env etc? Is this a change that is compatible with most legacy devices? Has it been tested against easycwmp just for a start?

I remember the initial code does not work with my Huawei 820 cpe device which does not accept the soap envelop so I did some fix.  for which xmlns attribute I think it is not important but we should keep it consistent everyone in the code. And the effective fix I think is this one:

` tr069/src/main/java/com/github/freeacs/tr069/xml/Response.java

sb.append("\n");
`

@yrong sorry about not answering for ages. About the encoding part, does it work for more than one type of device? I am not interested in merging this if I am not confident that most devices will handle this change. yes its a simple namespace change, but yey there are lot of badly implemented tr069 clients out there ...

I don't have to time to evaluate this for now. I can't just merge it without knowing why I should


Fix option argument passing

Commit 412909f is a bug fix. Commit 5899085 is a feature request. The editable data attribute when set to false makes the rating widget "read-only" useful for when one only wants to show the rating. The container allows to specify a span instead of the default div for when we want to display the rating inline. The class allows to style the container (like color and font-size). The id can be useful.
Note: when editable is set to false, the data-clearable is ignored.

Hello @iyedb, thank you very much for sharing your code and submitting this PR. The readonly feature is a recurrent feature request (#7) and making the plugin more and more configurable is definitely the way to go, but your interface implementation slightly differs from what I'd expect, let me make some points:

This plugin intent is to "replace" the placeholder input with the rating input, so I'm more inclined to just "copy" the id and classes from the placeholder input instead of explicitly passing them through a data-<parameter> attribute.
I think we don't really need to configure the wrapping element beyond span or div elements to allow an inline render option. May be a simpler approach would be to have a data-inline option, which, if present, would configure the plugin to be inline, being the block option a sensible default.
As "editable" is the default behaviour, I'd replace the data-editable=false option by a more semantic data-read-only flag, which, if present, would render a static rating display.

I'll gently decline this PR to have the opportunity to apply those changes, but your commits could definitely be merged in future releases as I think that, with a few adjustments, they can perfectly meet my "requirements" :-)
Thanks again for sharing and happy coding!

Hello @javiertoledo. Thanks for the detailed reply. No problem at all with not merging this PR as is. I agree with the data interface you described. Please consider fixing the args passing though (see 412909f).
Regards.


Grant Stream Analytics job permissions Synapse sample code

Feedback.
Grant Stream Analytics job permissions Synapse sample code.

No "ON" is written before OBJECT.
The GRANT statement will cause an error if you write server permissions and object permissions together. In the case of objects, you can specifically specify the Table name, View name, etc. In the case of server privileges, the object unit cannot be specified.

It should be written as follows
GRANT CONNECT,CONTROL,ADMINISTER DATABASE BULK OPERATIONS TO [AAD User].
GO
GRANT SELECT, INSERT ON OBJECT::dbo.TableName TO [AAD User].
GO

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

ID: daca22cc-4265-c99d-f0df-00c7dda3aefd
Version Independent ID: f83514e0-bbaa-239a-0077-98939721c220
Content: Use managed identities to access Azure SQL Database or Azure Synapse Analytics - Azure Stream Analytics
Content Source: articles/stream-analytics/sql-database-output-managed-identity.md
Service: stream-analytics
GitHub Login: @enkrumah
Microsoft Alias: ebnkruma

Thank you for your detailed feedback.  We are looking into the issue, and we will respond when we have more information.

@MartinJaffer-MSFT
Thanks for the reply.
I am a CSA on the Japanese side.
The SQL as is will result in an error, so please investigate.
The server Grant and object Grant should be written separately.
And you should write ON before the Object syntax.

Thanks for the feedback!
The fix is in a PR.

PR is completed, the doc should be updated shortly.
Thanks again @yang-jiayi, highly appreciated!
#please-close

Hi @Fleid ,
I have reviewed the reflected SQL code. The problem is still there.
The Azure SQL Database tag is fine.
GRANT CONNECT TO ASA_JOB_NAME;
GRANT SELECT, INSERT ON OBJECT::TABLE_NAME TO ASA_JOB_NAME;

That's correct.
Azure Synapse Analytics, on the other hand, has a problem.
GRANT CONNECT, CONTROL, ADMINISTER DATABASE BULK OPERATIONS TO ASA_JOB_NAME;
GRANT SELECT, INSERT, CONTROL, ADMINISTER DATABASE BULK OPERATIONS ON OBJECT::TABLE_NAME TO ASA_JOB_NAME;

Why do I have to write ADMINISTER DATABASE BULK OPERATIONS twice?
I think the following is correct, what do you think?
GRANT CONNECT, CONTROL, ADMINISTER DATABASE BULK OPERATIONS TO ASA_JOB_NAME;
GRANT SELECT, INSERT ON OBJECT::TABLE_NAME TO ASA_JOB_NAME;

Please check again.


Explanatory context

The parser should have some explanatory words and links to secondary literature.
Kokos will provide this.

(From our correspondence with Kokos):
References (you can extract bib entries from the webpages):

https://www.lotpublications.nl/dependency-as-modality-parsing-as-permutation
https://aclanthology.org/2023.eacl-demo.15/
https://aclanthology.org/2020.conll-1.3/
https://aclanthology.org/2020.lrec-1.647/
https://aclanthology.org/2023.clasp-1.13/

If you need software links as well:
https://github.com/konstantinosKokos/spindle
https://github.com//konstantinosKokos/aethel


Add big raster (.Jpg) to my vb.net project

hello,
i need to load some raster data in my application, but it returns an error at "system.drawing.image.fromstream"
i'm using gdal extention but it can't do the job.
thanks for help

Post your code.


Using CI_COMMIT_TAG in include:rules seems to have no effect

Minimal .gitlab-ci.yml illustrating the issue
I made a minimal test case here, but I'll replicate it below:
https://github.com/peterbbeu/gitlab-ci-local-testcase/tree/9bd6877
The output of gitlab-ci-local can be seen here:
https://github.com/peterbbeu/gitlab-ci-local-testcase/actions/runs/3639775229/jobs/6143584731
.gitlab-ci.yml
variables:
  IMAGE_TAG: $CI_COMMIT_REF_SLUG

include:
  - local: ci/version-tag.yml
    rules:
      - if: $CI_COMMIT_TAG

hello-world:
  stage: build
  script:
    - echo $IMAGE_TAG

ci/version-tag.yml
variables:
  IMAGE_TAG: $CI_COMMIT_TAG

hello-world2:
  stage: build
  script:
    - echo hello world

Expected behavior
See these two pipelines:
Branch: https://gitlab.com/petervv/gitlab-ci-test/-/pipelines/715969962
Tag: https://gitlab.com/petervv/gitlab-ci-test/-/pipelines/715970789
I expect the hello-world2 job to show up in the pipeline list when there's a CI_COMMIT_TAG, like happens on gitlab itself. Perhaps the include rule is not being correctly handled in this case?
Host information
Ubuntu 20.04
gitlab-ci-local 4.36.1
Additional context
Perhaps I'm using the wrong way of providing a tag?

I don't see --file ci/.gitlab-ci.yml being passed to your gitlab-ci-local command.

It's supposed to pickup .gitlab-ci.yml and through an include, the version-tag.yml. The end result should be a merged version of the two, like on Gitlab itself.
Do I need to specify all includes manually via an argument?

Oh, I didn't see that include 😁

Very nice, thanks!


doesnt work for chrome

Please refer to https://github.com/ehids/ecapture/blob/master/.github/ISSUE_TEMPLATE/bug_report.md for more information,thanks.


Modal is not closing itself after click

Describe the bug
Modal is not closing
To Reproduce
Method in my Vue component I call:
deleteConfirm() {
  this.$confirm({
    auth: true,
    message: 'foo',
    button: {
      yes: 'Yes',
      no: 'Cancel'
    },
    callback: (confirm, password) => {
      if (confirm && password === 'danger') {
        console.log('BOOOOM!');
      } else {
        console.log('relax');
      }
    }
  });
}

Expected behavior
After clicking on Cancel or Yes I expect the modal to close.
Additional context
When clicking outside the modal-messagebox (the modal-layer with background-color) the modal gets
more and more transparent - so after maaany clicks its unvisible but I thought it should close itself
directly after a button click.
The console.log spits out the clicks correctly.

Hello @Luckyfella73.  I have same issue. Do you manage to solve it? I implement Laravel Vue Datatable package and one of my columns is confirm delete action/button.

@DenisTsenov Unfortunately I didn't solve this issue. But if you are going to solve it I would appreciate if you post the solution here :)

Hi @Luckyfella73. Unfortunately i was unable to solve it, but i found few 'workarounds'. The first one is to redirect on the same page right after click on some of the ok/cancel buttons of the modal, which is kind of annoying.
The other one is to move the coresponding modal in separate page(which i already have). And if you chose the second one you have to be careful where you put the button/link which invoke the modal, because if it is in a form, the modal will dissapear kind of flash within less than a second. If it is outside of a form tag the modal work fine.
First workaround:
confirmRemove() {
this.$confirm({
                title: `Remove team`,
                message: `Are you sure you want to continue ?`,
                button: {
                    no: 'Cancel',
                    yes: 'Ok'
                },
                /**
                 * Callback Function
                 * @param {Boolean} confirm
                 */
                callback: confirm => {
                    if (confirm) {
                        axios.post(this.destroyRoute)
                             .then(response => {
                               window.location = response.data.route;
                             }).catch(error => {
                          alert('Something went wrong! Please try again later');
                        });
                    }

                  window.location = you_app_url;
                }
            });
}

Second one is without   window.location = you_app_url;, but ouside of a form tag and in a separate page.


Enhance the Kabanero CR operator to support a pipeline yaml file in addition to zips.

As part of the stack-hub design change, we moved pipeline specifications to the Kabanero CR.  The Kabanero CR expects the pipelines to be released and therefore zipped up.   An alternative method for aggregating the pipelines is to stack the pipeline-related CRs in the same file, using the Kubernetes method for concatenating different yamls (each CR separated by ---).
The Kabanero operator will tolerate either a .yaml or .tar.gz suffix on the URL specified for pipeline specifications in its CRs.   The Kabanero operator should support either https or github syntax as well.
Of note, the concatenation is just an alternative way to package the pipelines -- which allows the pipeline engineers to rapidly iterate through development scenarios.   Also of note, the Kabanero pipelines include symbolic processing (e.g. collection-ID) and that same substitution would happen whether the pipeline came from a zip or a concatenated yaml file.

The stack validating webhook currently enforces that a pipeline zip has a sha256 set in the Stack CR instance.  @stephenkinder outlines a "rapid development" model above... and computing and setting the sha256 into the Stack CR on each iteration probably doesn't fall into the "rapid development" category.
We need the SHA to be there so that when we activate the pipelines, the stack controller can use the digest to figure out if the pipelines/etc have changed, and re-apply them.
One approach we could use is to have the stack mutating webhook check to see if the pipelines are in a yaml file (.yaml extension instead of .tar.gz).  If it is, and if there is no sha256, then retrieve the file, compute it, and add it to the Stack CR.  Then the validating webhook can remain unchanged, and can enforce that there is a sha256 set.
Another alternative is to relax the validating webhook, such that it only enforces that a sha256 is present if the file ends in a .tar.gz extension.  The stack controller then needs to retrieve the yaml file and compute the sha256 before it tries to substitute any of the fill-ins in the pipeline yaml (such as StackId or Digest).  The template context needs to have the computed sha256 added before the templates are rendered.

When we activate a stack, the status section contains each version of the stack, and for each version we list the individual assets in the pipeline zip (the individual kubernetes objects).  When we add the support for reading the pipelines out of a .yaml file, we'll need to change how this works slightly.
*There will no longer be a manifest.yaml to use to check the sha256 of the individual assets.  The sha256 will be omitted from the status, and we'll need to make sure that no code depends on this information being there.  More specifically, each asset will be missing assetDigest.

I had originally been concerned that part of the status contained the file name within the .tar.gz where the asset yaml was found, but this appears not to be the case.  the individual asset status yaml just contains the name of the object:

      - assetDigest: 19afa906601d3a763ac1bd9ab9d0644de86646db33ed6f4e99be30059df2c69b
        assetName: java-microprofile-image-retag-task
        group: tekton.dev
        kind: Task
        namespace: kabanero
        status: active
        version: v1alpha1

@dacleyra I think the development work on this is done - please close this issue if that's true.


Always use gofmt in gofmt linter

Goimports is doing weird things according to some coworkers, and
rewriting import order is a weird thing to do as part of a linter.
Changing this to be simpler.

Said weirdness
+ is goimports
- is gofmt
diff --git a/net/discovery/server/streaming_client_test.go b/net/discovery/server/streaming_client_test.go
index f52c5f3c..21481e5a 100644
--- a/net/discovery/server/streaming_client_test.go
+++ b/net/discovery/server/streaming_client_test.go
@@ -191,19 +191,19 @@ func TestStreamClientWatch(t *testing.T) {

         args.registrar.EXPECT().Register(dtestutils.NameKey1, args.client).
             Do(func(name common.NameKey, receiver watch.Receiver) {
-                // Test an add for a name that doesn't exist.
-                receiver.OnReceiverAdd(dtestutils.NameKey2, mockWatch)
+            // Test an add for a name that doesn't exist.
+            receiver.OnReceiverAdd(dtestutils.NameKey2, mockWatch)

-                // Reply with an add for the requested name.
-                receiver.OnReceiverAdd(name, mockWatch)
-            })
+            // Reply with an add for the requested name.
+            receiver.OnReceiverAdd(name, mockWatch)
+        })

         cancelBlock := make(chan struct{})
         mockWatch.EXPECT().RemoveReceiver(args.client).
             Do(func(receiver watch.Receiver) {
-                receiver.OnReceiverRemove(dtestutils.NameKey1)
-                close(cancelBlock)
-            })
+            receiver.OnReceiverRemove(dtestutils.NameKey1)
+            close(cancelBlock)
+        })

This gets a 👍 from me


[sandboxes] devbox ls: print versions

Summary
For packages without an explicit version, this PR will print the version for
the user in devbox ls.
Fixes #2274
How was it tested?
% devbox ls
* go@latest - 1.23.0
* runx:golangci/golangci-lint@latest - 1.60.2
* runx:mvdan/gofumpt@latest - 0.7.0
*<EMAIL_ADDRESS>
Notice that versions are printed for go@latest and the runx packages, but
not for cowsay since it was added via devbox add<EMAIL_ADDRESS>Also, devbox ls -c examples/flakes/php and devbox ls -c examples/flakes/remote
% devbox ls -c examples/flakes/remote
* github:nixos/nixpkgs/5233fd2ba76a3accb5aaa999c00509a11fd0793c#hello
* github:nixos/nixpkgs/5233fd2ba76a3accb5aaa999c00509a11fd0793c#cowsay
* github:F1bonacc1/process-compose/v0.43.1

@savil Is this ready to be merged?


[DO NOT MERGE] Track next futures-preview release

Sweet, thanks for spearheading this! What are the major changes? Looks like Sink is now generic over the item rather than it being an associated type.

@tikue futures-preview now has its own sink compat shims. I had to resort to extremely fragile transmute to expose a private method though. Also CloneSpawn is broken and has been replaced by a mutex in SEED_SPAWN.
On a side note, do we really need tarpc::init()? Is it not better to use the executor upon which tarpc client/server future is spawned?

Regarding tarpc::init(), I'd prefer to track that in a dedicated bug, but briefly, I'm not opposed to having a config option in client::Config and server::Config to set the executor, but I think it's nice to have a default specified by init().

Is it not better to use the executor upon which tarpc client/server future is spawned?

I'm pretty sure this is possible! init() just takes something Spawn + Clone, e.g. DefaultExecutor::current().compat(). Nothing stops the user from using this same executor elsewhere. In fact doesn't tokio::run() use the current executor too?

@vorot93 I can't remember how I ended up looking at this PR, but if you want to open an issue about the missing method on Compat01As03Sink I'm sure it could get added easily (by the looks of it you just need fn as_ref(&self) -> &S?)

@Nemo157 that's a great suggestion! @vorot93 do you want to make that PR?

@Nemo157 @tikue rust-lang-nursery/futures-rs#1524

@tikue transmute is no longer there

r? @tikue


DatePicker renderInput is called twice

Hi
Looks like renderInput handler is called twice, but with different props in arguments? Is it expected behavior? It causes some problems in our client code
"@material-ui/pickers": "^4.0.0-alpha.12"
here is demo: https://codesandbox.io/s/sharp-smoke-txxmr

Which problem does it create for you? The double rendering shouldn't be an issue on its own.

Hello, can I get some explanation for this issue? I can't understand why double rendering shouldn't be an issue.

The double rendering might be coming from the need of the component to resolve the desktop vs mobile mode.


Update writing_single_node_hpx_applications.rst

Fix typo
Fixes #
Proposed Changes

Any background context you want to provide?

Replaced by #3974.


Request: Compatibility with PCA 9634

Hi Rob Tillaart,
Thank you for such a wonderful library. Unfortunatly, I'm working with the smaller brother (8 LEDs, 8 bit) of the same chip. It is called PCA9634 and I'm not sure if your library can be adapted for that chip. Since I'm an absolute noob, I was wondering if you would find the time and take a look at it, if this would be feasible.
I have the datasheet to this chip attached: Datasheet PCA9634.pdf
Thank you in advance!
Lux

Hi,
I will have a quick look at the datasheet

Check paragraph 7.3 of both datasheets, the register mapping differs, so this library cannot be used for the PCA9634
PCA9635.pdf
What is possible is to create a library with the same interface and adjusted register mapping.
As I have no hardware you should do the testing.

A quick search
There already exist

https://github.com/mmojana/pca9634-arduino-library
https://github.com/NickvanTholen/pca9634-lib/

Don't know if these would fit your needs.
Note the Nick van Tholen library has examples and has a more elaborated readme. I would check that one first.

If you want a library that is has similar API as mine, I need to write it (takes time estimate 10-15 hours )
And as I do not have the HW I cannot test it, could you do that?

I'm happy to test.
I have tried to use the mmojana lib, however it does not work with my breakout board. I have checked my hardware multiple times and I'm pretty sure it works. To make sure I designed a new board this morning and I'm now waiting for the arrival from china.
I suggest, that I test the lib from Nick van Tholen first (somehow I must have missed that one). Therefore, you don't have to spend too much work reinventing the wheel. I'll get back with the results (bad or good), as soon as I have them.
Thank you VERY much, for replying to my request and keeping your library up to date.  None of the samples work. I have a few more chips and empty boards, I'll go and solder a bit :-D

As it seems I must have killed my chip somehow. None of the samples work. I

that hurts ...
FYI I started with a library here - https://github.com/RobTillaart/PCA9634
stripped a copy of the pca9635, just to give it a try.
It is not functional yet as I have to patch registermapping.

A few hours of focus ==> https://github.com/RobTillaart/PCA9634
If you have time please verify if it works and /or errors you encounter.

I "answered" with a few comments (nothing special) your new repository.
You did an amazing job!


Do not use site.BaseURL in your templates

There is never a great reason to call .Site.BaseURL from a template. Hopefully we will deprecate that method at some point. Use the absURL and absLangURL functions instead.

https://discourse.gohugo.io/t/site-baseurl-appears-in-a-js-template-literal/46692/4

As long as it works an is supported, there is no need to change it.

Your call...


Add funding goal to side panel on profiles

Right now the funding goal is obscured by being placed toward the bottom of the
page.  It's related to receiving amount, so it seems to want to have the number
there.

+1

That's a simplistic solution, you've only duplicated the information.

@Changaco What's wrong with that?


Add compression and encoding type check for FastCompactionPerformer

Description
In FastCompactionPerformer, there is no logic to judge whether the CompressionType or TsEncodingType are same or not between two candidate chunk, which will lead to a false case that there are two pages whose compression type are different in one Chunk.
This PR is used to fix this issue. (DRAFT version)

coverage: 47.944% (-0.06%) from 48.006% when pulling 9a79177325eb4847559263d87bca270002f1783e on fast_performer_force_decoding into 1be3e0d5a53b478111ab2f5cce157f38febc78b3 on master.


SAPT-D!

Description

Adds additive dispersion correction to SAPT (pub upcoming from CDS group) to engine, and enables return of atomic pairwise dispersion from DFTD3.
Changelog description

Adds SAPT-D & pairwise DFTD3 analysis.
Status

[x] Code base linted
[x] Ready to go

superseded by #282


Help with what to put in a main function for a cxx interface program

Hello, I'm currently making a program in rust that exposes a function to c++ using the cxx crate.
here is the program : https://gist.github.com/rust-play/0997aff926802eb98998273330d48a43
but I'm not sure what to put in the main function to make it callable from c++

From what you wrote in the Gist, I would expect the C++ main to look similar to this:
#include "playground/playground.rs.h"

int main() {
  rust::Str token = "…";
  int64_t timestamp = …;
  rust::String jwt = rust_jwt::make_jwt(token, timestamp);
  (void)jwt;
}


Switch to leader latch WIP

I switched from LeaderSelector to LeaderLatch in order to avoid all of the exception logging. I am not completely finished with this, but just got a full build to run.  I am creating a PR to see how it does on travis.

@keith-turner Everything builds here without any errors, nice work!

I am finished working on this PR.   Based on the spelunking I have done in the Curator code, I think we may still see some occasional spurious exceptions from Curator.  This is caused by some Curator recipes scheduling background operations that may throw exceptions if things are closed.  At this point there is not much we can do about these other than fix curator.

I have opened CURATOR-467 and CURATOR-469 to document the problems I found while trying to avoid spurious error logging from Curator.


Popup creation of a new offline project the OK button is missing

Fixed with label "OK"

Closes #2243

its not merged yet, reopening


[BUG] [Functional] Routes - transit gateway route association failure in phase 3 with multi region.

Accelerator Version:  1.5.0
Install Type: Clean
Upgrade from version: N/A
Which State did the Main State Machine Fail in: Phase 3.

I am trying to setup multi region asea with transit gateway peering model.
I have used multi-region deployment with transit gateway peering. config i kept as similar to what is given in example.  Installation stops at phase 3. stating as below.
Error: There is already a Construct with name 'tgw_associate_core' in AccountStack [SharedNetworkPhase3]
65 | at Node.addChild (/app/node_modules/.pnpm/constructs@3.3.71/node_modules/constructs/src/construct.ts:534:13)
66 | at new Node (/app/node_modules/.pnpm/constructs@3.3.71/node_modules/constructs/src/construct.ts:75:22)
67 | at new ConstructNode (/app/node_modules/.pnpm/@aws-cdk+core@1.113.0/node_modules/@aws-cdk/core/lib/construct-compat.ts:184:24)
68 | at Object.createNode (/app/node_modules/.pnpm/@aws-cdk+core@1.113.0/node_modules/@aws-cdk/core/lib/construct-compat.ts:55:11)
69 | at new Construct (/app/node_modules/.pnpm/constructs@3.3.71/node_modules/constructs/src/construct.ts:575:26)
70 | at new Construct (/app/node_modules/.pnpm/@aws-cdk+core@1.113.0/node_modules/@aws-cdk/core/lib/construct-compat.ts:52:5)
71 | at new CfnElement (/app/node_modules/.pnpm/@aws-cdk+core@1.113.0/node_modules/@aws-cdk/core/lib/cfn-element.ts:31:5)
72 | at new CfnRefElement (/app/node_modules/.pnpm/@aws-cdk+core@1.113.0/node_modules/@aws-cdk/core/lib/cfn-element.ts:106:1)
73 | at new CfnResource (/app/node_modules/.pnpm/@aws-cdk+core@1.113.0/node_modules/@aws-cdk/core/lib/cfn-resource.ts:68:5)
74 | at new CfnTransitGatewayRouteTableAssociation (/app/node_modules/.pnpm/@aws-cdk+aws-ec2@1.113.0/node_modules/@aws-cdk/aws-ec2/lib/ec2.generated.ts:15750:9)
I attaching the mandatory accounts json where we have transitgateway config in shared network. and phase3 build logs.
files are sanitized already
madatoryaccounts.txt
phase3-build.txt
is there anything that I can try to fix this issue.?

Hi,  I see the same route table names used on each TGW, can you rename the route tables to be unique and retry? (i.e. core-Main, core-USW, core-APSE1 instead of all using core)  May only be an issue for the connected RTs, but they all may need to be unique (i.e. "core", "segregated", "shared", and "standalone").  You'll need to also fixup all associated references.  Let us know!

@Brian969,
Thanks for the suggestion and it works. Here is how i resolved this.
I went through the below code file couple of times, I was able to figure out that the code is failing when we are trying to associate the transit gateway remote with the same route table name.
while i was running this second round, i had to remove the route <IP_ADDRESS>/0 pointing to Main Transit gateway in tgw-routes[] in peered transit gateways. this route is already added by default when we do peering attachment between transit gateways, no need of adding this route block in new transit gateway deployments, unless we have specific routes to main transit gateway apart from <IP_ADDRESS>/0.
--
"deployments": {       "tgw": [         {           "name": "Main",           "asn": 65521,           "region": "${HOME_REGION}",           "features": {             "DNS-support": true,             "VPN-ECMP-support": true,             "Default-route-table-association": false,             "Default-route-table-propagation": false,             "Auto-accept-sharing-attachments": true           },           "route-tables": ["core", "segregated", "shared", "standalone", "west", "southeast"],           "tgw-routes": [             {               "name": "{TGW_ALL}",               "routes": [                 {                   "destination": "<IP_ADDRESS>/0",                   "target-vpc": "Perimeter",                   "target-account": "perimeter"                 }               ]             },             {               "name": "west",               "routes": [                 {                   "destination": "<IP_ADDRESS>/13",                   "target-tgw": "USWest"                 }               ]             },             {               "name": "southeast",               "routes": [                 {                   "destination": "<IP_ADDRESS>/13",                   "target-tgw": "APSE1"                 }               ]             }           ]         },         {           "name": "USWest",           "asn": 64526,           "region": "us-west-2",           "features": {             "DNS-support": true,             "VPN-ECMP-support": true,             "Default-route-table-association": false,             "Default-route-table-propagation": false,             "Auto-accept-sharing-attachments": true           },           "route-tables": ["core", "segregated", "shared", "standalone"],           "tgw-attach": {             "associate-to-tgw": "Main",             "account": "shared-network",             "region": "${HOME_REGION}",             "tgw-rt-associate-local": ["core"],             "tgw-rt-associate-remote": ["west"]           },           "tgw-routes": []         },         {           "name": "APSE1",           "asn": 64530,           "region": "ap-southeast-1",           "features": {             "DNS-support": true,             "VPN-ECMP-support": true,             "Default-route-table-association": false,             "Default-route-table-propagation": false,             "Auto-accept-sharing-attachments": true           },           "route-tables": ["core", "segregated", "shared", "standalone"],           "tgw-attach": {             "associate-to-tgw": "Main",             "account": "shared-network",             "region": "${HOME_REGION}",             "tgw-rt-associate-local": ["core"],             "tgw-rt-associate-remote": ["southeast"]           },           "tgw-routes": []         }       ]
https://github.com/aws-samples/aws-secure-environment-accelerator/blob/release/v1.5.0/src/deployments/cdk/src/deployments/transit-gateway/step-3.ts
we might have to correct mult-region example to help this issue not being raised again.
Thanks for your guidance, feel free to close this ticket.

Glad you were able to get your environment running and very much appreciate the feedback/follow-up.  I still consider this a bug - multiple TGW's should be able to associate to the same route table.
Issue:

Naming of the TGW association to a RT construct only includes the RT name, and not the name of the remote TGW
results in duplicate construct names
Fix:
Keep naming for currently deployed (1st instance) TGW to TGW associate constructs (to not break existing deploys) - see code for other similar RT fixes
add the remote TG name to the construct name for new/additional associations

Fixed here : https://github.com/aws-samples/aws-secure-environment-accelerator/pull/878
As mentioned in the PR, I did not use the remote TGW name since it might lead to collision : name would be tgw_associate_Main_core and tgw_associate_Main_core if 2 TGWs want to target Main TGW for the save core route.
With the TGW local name, it works : tgw_associate_TGW2_core and tgw_associate_TGW3_core

PR sent back for rework.


Switch from [U]INT# to [u]int#_t

As we discussed over various pull requests, using the [u]int#_t types from the stdint header can be a nice readability enhancement for the bsf framework codebase.
Since that switch is a very mechanical, but very large, change, I figured I'd forego opening a PR and instead provide a bash-script that'll take care of the grunt work automatically.
So here's how you can rip off the band-aide, if you decide you want to.
find . -name "*[cpp|h]" -exec sed -i 's/INT8/int8_t/g; s/INT16/int16_t/g; s/INT32/int32_t/g; s/INT64/int64_t/g; s/Uint/uint/g' "{}" \;

Of course, that might have some unintentional side effects, e.g. false positive matches and that kind of thing. So take with grain of salt.

Thanks, I'll make use of it when the time comes. (Although since I'm on Windows I might just do regex replace in VS)

+1 for this enhancement. This is one of the main readability issue I have with this (awesome) framework.


Rename column on empty dataset leaves the column field hanging

Same steps as in #5515, but only do the "add new column"
Expected result:

Focus on the new column field, and if clicking/doing something else cancels the edit-inline-field (leave the column with the default-generated name

Actual result:

Field is left "open" for editing when interacting with anything else on the page, seems like the column/name is not persisted either.

Since edit left hanging, it has the negative side-effect that any rename won't work, because it tries to use the column_1235345555 as new_name in the PUT request to rename column, regardless of what is typed in the rename input field.

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


[REVIEW] consider adding automated testing

Automated testing is a best practice for open source projects, reducing the risk of software regression through breaking changes. stemflow includes a mini_test module that appears to test many parts of the software, but this is run manually. I recommend adding automated tests in CI to verify (and to provide verification to users) that the software continues to function as expected.

Thank you for the suggestion! I agree that the test should be automatic.
I have made the mini_test automatic at each PR and push, testing on Python 3.8, 3.9, and 3.10.
I still kept the stemflow.manually_testing module and mini_test notebook in case any user is interested in it.
Besides, I add pre-commit for code trimming and auto-checking, as well as codecov statistics.
Related PRs: #9, #11 , #12

Closing this.


Tips are not found in different screen from currentTip during TipTour

Thank you for sharing this library. Very insightful.
I think there is a limitation in TipTour implementation. It fails to find nextTips when they are present in a different screen which is not loaded (Tip is not registered) until we navigate to that screen.
I think we should call nextAction/prevAction before finding the tip by id in the registry. So that once nextAction is called,

we navigate to the screen,
the tip is registered
then we can find it after some predefined delay (depending time for navigation animation + set layout)

Totally agree. I am facing this problem too.

Thanks for let me know! I will take a look on that.


Missing base URL in tag and category links

In the loop for tags and categories in layouts/partials/header.html the base URL is missing when the URL is generated.
Example:

base URL is: domain.tld/web/

post URL is: domain.tld/web/posts/new-post

Tag link generated is: domain.tld/tags/tag01 -- it should be domain.tld/web/tags/tag01

Cat link generated is: domain.tld/categories/cat01 -- it should be domain.tld/web/categories/cat01

I tried adding relLangURL, relURL, absLangURL, and absURL but I'm doing something wrong ^^:;
Thank you

Should be fixed in e695204.

Should be fixed in e695204.

Ahh, so that's how it's done. I was definitely doing it wrong. 🤣
Thank you very much!!

Ahh, so that's how it's done. I was definitely doing it wrong. 🤣
Thank you very much!!


chore: improve profile page

Small idea on improving the profile page.
IMHO the repository list is a duplicate of the pinned repository, which makes me end-up reading the same info twice:

Maybe adding a nice banner like https://github.com/github will make it look better too:

This removes the rust and js sections. Some of the docs dont link to them so would be good to have them somehow

Updated, the rust side does not have very much documentation tho.


Modifying Label to Var in min_label and max_label

Hi, this is Sai Rugveth Vankayala. Please check the modifying files and see if it fits your requirements.
This is resolution for the issue : closes https://github.com/SSoelvsten/adiar/issues/417

I'll fix the following myself on the rugveth-fixes branch:

Improve the wording in the commit message to conform to Git practices.
Add min_label and max_label to the set of deprecated functions.


Project path env

Summary

Adds support for setting a custom project path via $BP_DOTNET_PROJECT_PATH
Resolves #151
Use Cases

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.

Paketo doc changes - https://github.com/paketo-buildpacks/paketo-website/pull/128

@thitch97 @emmjohnson is this ready for review? What is it blocked on?

Besides that last small comment, this looks good to me. Since @fg-j has been looking at this PR I'll let her take a look as well before we approve!


Fix for Issue #2 and Reworked travis.yml for easier maintenance

The widget decompress method needed to coerce the value for the number input. While I was there, I changed to spaces. Hope that's not a problem.
Also, I switched up the .travis.yml file. This will be easier for you to maintain as new versions of Django or Python get added, as this config automatically does all the combinations for every listed version of Python and Django.
Additionally, coverage is now configured to run.

Changes Unknown when pulling 00022bf8225b464ff82fd2a8dd30568ab57cc224 on worthwhile:master into ** on bharling:master**.


Migration from Graphene to Strawberry

I use graphene==3.0.0b6 (it uses graphql-core v3 under the hood). Could you, please, provide some migration guide?

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

@Sergei-Rudenkov at the moment unfortunately we don't have a migration guide other than rewriting your application 😢
I am however experimenting with something that might allow you migrate from Graphene incrementally. If you're willing to give it a try follow the instructions here: https://github.com/jkimbo/strawberry-graphene
Let me know how it goes! I haven't actually tried this on a large schema so it's quite likely that things won't work but I'll try and fix them as soon as possible.

We tried to use https://github.com/jkimbo/strawberry-graphene, but found that it only worked up until version strawberry-graphql==0.68.0.
We made a few modifications and have it mostly working on strawberry-graphql==0.85.1. Most of our schema is still graphene-based (and we're still running into issues around enums and interfaces), but our root Schema object is strawberry-based. Here it is in gist-form: https://gist.github.com/AlecRosenbaum/d23541cbcd35290f675a207d0b7f95a3

@AlecRosenbaum this is awesome thanks for sharing! Do you mind if I update the repo with your changes?
Also what issues are you finding with enums and interfaces? Would be happy to help you debug them.

Credit for that goes to @tsx 🙂 I just stumbled across this issue and posted it.

Do you mind if I update the repo with your changes?

Sure!

Also what issues are you finding with enums and interfaces?

For interfaces we're running into issues around type resolution of non-strawberry types (https://github.com/strawberry-graphql/strawberry/issues/1405). I proposed https://github.com/strawberry-graphql/strawberry/pull/1406 to address it.
For enums we were also having issues updating to the latest graphene version (b2 -> b6 IIRC?) so that might be on us for how we're using it. We have a few pieces of custom functionality we implemented that we have yet to reimplement:

Automatically converting the exposed enum values to SCREAMING_SNAKE_CASE (since many of our python enums do not conform to that pattern)
Exposing an option to choose between usen the python enum's name/value for the graphql values
Generating "Enum Unions", to expose the equivalent of Union[Enum1, Enum2] where the enums don't have overlapping values. Since graphql doesn't support unions on enum fields, we have it generating a new combined enum.

@jkimbo @AlecRosenbaum Hi there! Looking to make this move as well.

Do you mind if I update the repo with your changes?

Did this happen? Or is the best route to still to use the gist @AlecRosenbaum provided?
@AlecRosenbaum Any more rough spots you've encountered?

I can't remember exactly what has changed since the last time we shared, but I know for sure we've updated some stuff.
Not exhaustive, but two larger issues we've faced and resolved in the schema converter were around interfaces and scalars. There's a DateTime scalar graphene provides which will conflict with strawberry's DateTime scalar if not explicitly handled. The other one had to do with how we use the Node interface. We wanted to gradually convert types over, and so we effectively had it allow duplicate interfaces (one interface on each graphene / strawberry) and just use the same underlying definition if trying to parse it again. Not a great solution, but works enough that we can be careful in the interim.
We also did some other stuff around enums so we didn't have to make schema changes when converting graphene enums over.
Having unions with both strawberry and graphene types seems to sometimes work if it's a graphene.Union, but I haven't yet had it work when defining the union with strawberry.
Also note that we're currently on strawberry-graphql==0.93.10, which is a little behind latest. So haven't yet tested with the latest release.
Hopefully this is more helpful than not 🙂. Here's the code:

Expand
import datetime
import inspect
from decimal import Decimal
from enum import Enum
from functools import partial
from graphene.utils.str_converters import to_snake_case
from typing import Any, Dict, Optional, Sequence, Type, Union

import graphene
import strawberry
from graphene.types.base import BaseType as BaseGrapheneType
from graphene.types.definitions import GrapheneUnionType
from graphene.types.schema import TypeMap as BaseGrapheneTypeMap
from graphql import (
    ExecutionContext as GraphQLExecutionContext,
    GraphQLList,
    GraphQLNonNull,
    GraphQLObjectType,
    GraphQLSchema,
    GraphQLType,
    validate_schema,
)
from graphql.type.directives import specified_directives
from strawberry.custom_scalar import ScalarDefinition, ScalarWrapper
from strawberry.directive import StrawberryDirective
from strawberry.enum import EnumDefinition
from strawberry.extensions import Extension
from strawberry.field import StrawberryField
from strawberry.schema import schema_converter
from strawberry.schema.config import StrawberryConfig
from strawberry.schema.schema_converter import CustomGraphQLEnumType
from strawberry.schema.types import ConcreteType
from strawberry.schema.types.scalar import DEFAULT_SCALAR_REGISTRY
from strawberry.types.types import TypeDefinition
from strawberry.union import StrawberryUnion
from strawberry.utils.str_converters import to_camel_case

def to_enum_name(s: str) -> str:
    return to_snake_case(s.replace('.', '_').replace('-', '_')).upper()

class OurCustomGraphQLEnumType(CustomGraphQLEnumType):
    def serialize(self, output_value: Any) -> str:
        if isinstance(output_value, Enum):
            return to_enum_name(output_value.value)
        return super().serialize(output_value)

class GraphQLCoreConverter(schema_converter.GraphQLCoreConverter):
    def __init__(self, *args, **kwargs):
        self.graphene_type_map = GrapheneTypeMap(self)
        super().__init__(*args, **kwargs)

    def add_graphene_type(self, type_: Any) -> GraphQLObjectType:
        return self.graphene_type_map.add_type(type_)

    def from_object_type(self, object_type: Type) -> GraphQLObjectType:
        # Check if it's a Graphene type
        if issubclass(object_type, graphene.ObjectType):
            return self.add_graphene_type(object_type)

        return self.from_object(object_type._type_definition)

    def from_type(self, type_: Any) -> GraphQLType:
        if inspect.isclass(type_) and issubclass(type_, BaseGrapheneType):
            return self.add_graphene_type(type_)
        return super().from_type(type_)

    def from_enum(self, enum: EnumDefinition) -> CustomGraphQLEnumType:
        enum_name = self.config.name_converter.from_type(enum)

        assert enum_name is not None

        # Don't reevaluate known types
        if enum_name in self.type_map:
            graphql_enum = self.type_map[enum_name].implementation
            assert isinstance(
                graphql_enum, OurCustomGraphQLEnumType
            )  # For mypy
            return graphql_enum

        graphql_enum = OurCustomGraphQLEnumType(
            name=enum_name,
            values={
                to_enum_name(item.value): self.from_enum_value(item)
                for item in enum.values
            },
            description=enum.description,
        )

        self.type_map[enum_name] = ConcreteType(
            definition=enum, implementation=graphql_enum
        )

        return graphql_enum

class GrapheneTypeMap(BaseGrapheneTypeMap):
    def __init__(self, strawberry_convertor, *args, **kwargs):
        self.strawberry_convertor = strawberry_convertor
        super().__init__(*args, **kwargs)

    def construct_union(self, graphene_type):
        create_graphql_type = self.add_type

        def types():
            union_types = []
            for graphene_objecttype in graphene_type._meta.types:
                object_type = create_graphql_type(graphene_objecttype)
                union_types.append(object_type)
            return union_types

        resolve_type = (
            partial(
                self.resolve_type,
                graphene_type.resolve_type,
                graphene_type._meta.name,
            )
            if graphene_type.resolve_type
            else None
        )

        return GrapheneUnionType(
            graphene_type=graphene_type,
            name=graphene_type._meta.name,
            description=graphene_type._meta.description,
            types=types,
            resolve_type=resolve_type,
        )

    def add_type(self, graphene_type):
        if hasattr(graphene_type, "_type_definition") or hasattr(
            graphene_type, "_enum_definition"
        ):
            try:
                return self.strawberry_convertor.from_type(graphene_type)
            except RecursionError as e:
                raise RuntimeError(
                    f'You probably have @strawberry.type decorator on a class that inherits from graphene. Please remove the graphene base class from {graphene_type}.'
                ) from e

        # Special case decimal
        if isinstance(graphene_type, type) and issubclass(
            graphene_type, graphene.Decimal
        ):
            return self.strawberry_convertor.from_scalar(Decimal)
        if isinstance(graphene_type, type) and issubclass(
            graphene_type, graphene.DateTime
        ):
            return self.strawberry_convertor.from_scalar(datetime.datetime)

        if inspect.isfunction(graphene_type):
            graphene_type = graphene_type()
        if isinstance(graphene_type, graphene.List):
            return GraphQLList(self.add_type(graphene_type.of_type))
        if isinstance(graphene_type, graphene.NonNull):
            return GraphQLNonNull(self.add_type(graphene_type.of_type))
        try:
            name = graphene_type._meta.name
        except AttributeError as e:
            raise TypeError(
                f"Expected Graphene type, but received: {graphene_type}."
            ) from e
        graphql_type = self.get(name)
        if graphql_type:
            return graphql_type
        if issubclass(graphene_type, graphene.ObjectType):
            graphql_type = self.create_objecttype(graphene_type)

            # Calling vars(graphene_type).items() on some graphene objects
            # causes later infinite recursion.. Quick hack to get moving for
            # now.
            if hasattr(graphene_type, 'has_strawberry_field'):
                # Create gql fields for all strawberry fields/mutations,
                # because create_objecttype(graphene_type) creates only
                # graphene fields.
                # This attr must be set on all graphene classes that
                # reference strawberry field or mutation.
                for name, field in vars(graphene_type).items():
                    if isinstance(field, StrawberryField):
                        gql_field = self.strawberry_convertor.from_field(field)
                        camel_case_name = to_camel_case(name)
                        graphql_type.fields[camel_case_name] = gql_field

        elif issubclass(graphene_type, graphene.InputObjectType):
            graphql_type = self.create_inputobjecttype(graphene_type)
        elif issubclass(graphene_type, graphene.Interface):
            # allows us to prefer the strawberry implementation of an interface
            # (mostly useful for Node)
            if graphene_type._meta.name in self.strawberry_convertor.type_map:
                graphql_type = self.strawberry_convertor.type_map[
                    graphene_type._meta.name
                ].implementation
                graphql_type.graphene_type = graphene_type
            else:
                graphql_type = self.create_interface(graphene_type)
        elif issubclass(graphene_type, graphene.Scalar):
            graphql_type = self.create_scalar(graphene_type)
        elif issubclass(graphene_type, graphene.Enum):
            graphql_type = self.create_enum(graphene_type)
        elif issubclass(graphene_type, graphene.Union):
            graphql_type = self.construct_union(graphene_type)
        else:
            raise TypeError(
                f"Expected Graphene type, but received: {graphene_type}."
            )
        self[name] = graphql_type
        if not issubclass(graphene_type, graphene.Scalar):
            self.strawberry_convertor.type_map[name] = ConcreteType(
                definition=None, implementation=graphql_type
            )
        return graphql_type

class Schema(strawberry.Schema):
    def __init__(
        self,
        # TODO: can we make sure we only allow to pass something that has been decorated?
        query: Type,
        mutation: Optional[Type] = None,
        subscription: Optional[Type] = None,
        directives: Sequence[StrawberryDirective] = (),
        types=(),
        extensions: Sequence[Union[Type[Extension], Extension]] = (),
        execution_context_class: Optional[
            Type[GraphQLExecutionContext]
        ] = None,
        config: Optional[StrawberryConfig] = None,
        scalar_overrides: Optional[
            Dict[object, Union[ScalarWrapper, ScalarDefinition]]
        ] = None,
    ):
        self.extensions = extensions
        self.execution_context_class = execution_context_class
        self.config = config or StrawberryConfig()

        scalar_registry: Dict[
            object, Union[ScalarWrapper, ScalarDefinition]
        ] = {**DEFAULT_SCALAR_REGISTRY}
        if scalar_overrides:
            scalar_registry.update(scalar_overrides)

        self.schema_converter = GraphQLCoreConverter(
            self.config, scalar_registry
        )
        self.directives = directives

        query_type = self.schema_converter.from_object_type(query)
        mutation_type = (
            self.schema_converter.from_object_type(mutation)
            if mutation
            else None
        )
        subscription_type = (
            self.schema_converter.from_object_type(subscription)
            if subscription
            else None
        )

        graphql_directives = [
            self.schema_converter.from_directive(directive)
            for directive in directives
        ]

        graphql_types = []
        for type_ in types:
            graphql_type = self.schema_converter.from_object_type(type_)
            graphql_types.append(graphql_type)

        self._schema = GraphQLSchema(
            query=query_type,
            mutation=mutation_type,
            subscription=subscription_type if subscription else None,
            directives=specified_directives + graphql_directives,
            types=graphql_types,
        )

        # attach our schema to the GraphQL schema instance
        self._schema._strawberry_schema = self  # type: ignore

        # Validate schema early because we want developers to know about
        # possible issues as soon as possible
        errors = validate_schema(self._schema)
        if errors:
            formatted_errors = "\n\n".join(
                f"❌ {error.message}" for error in errors
            )
            raise ValueError(f"Invalid Schema. Errors:\n\n{formatted_errors}")

        self.query = self.schema_converter.type_map[query_type.name]

    def get_type_by_name(
        self, name: str
    ) -> Optional[
        Union[
            TypeDefinition, ScalarDefinition, EnumDefinition, StrawberryUnion
        ]
    ]:
        if name in self.schema_converter.type_map:
            return getattr(
                self.schema_converter.type_map[name], "definition", None
            )

        return None

This is a wealth of info. Thanks a ton for writing it out. <3

Hey @patrick91, thanks for Strawberry, I wonder why this issue was closed, is there's a better way to do this nowadays or was it just stale?
I'm trying to do the same, I managed to get @AlecRosenbaum's version into a reasonably working state with some minor issues, but the problem is that I naturally can't merge Graphene's ObjectType with Strawberry's type. My base Query object has a little over 100 queries created from the merge (by subclassing) of 30 different query types, so it would be a big effort to try to convert all of those queries at once instead of over time.
What I started to try as an alternative is to convert the Graphene objects to GraphQL-core objects and then to StrawberryTypes, possibly by just adding a __strawberry_definition__, this way they would be interchangeable and mergeable:
# QueryA is a Graphene ObjectType while QueryB implements `WithStrawberryObjectDefinition`

# Now QueryA also implements `WithStrawberryObjectDefinition`
add_strawberry_to_graphene(QueryA)

ComboQuery = merge_types("ComboQuery", (QueryB, QueryA))


[Blog] Request for Post: Extending Meshery Models

Current State:
Measure that I owe doesn't have a blog post discussing the extensibility of a mesh remodel and how to either create a new model or extend existing models.
Desired State:

A short explanation and link to other meshery.io blog post for an explanation of models.
Use of the quick start guide.
Instructions on how to contribute a new model once completed. (https://meshery.io/catalog/models)
Call to action to create and contribute new models.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

@shivaylamba for your consideration. This issue was created with you in mind.

Hi @shivaylamba
Any update on this?


Set up content migration from V1 IoGT database

Copies sections and articles from a v1 IoGT database. Does not include images at this stage.
Assuming there is a database available with the v1 data. If not, I have added some docker compose config for this purpose. Just place the database backup SQL scripts in a directory called initdb.d in the project root, and run docker-compose start db.

Start with a brand new SQLite database. Remove or rename any existing.
Run the database schema migrations: manage.py migrate
Run the content migration (options are available, run with --help to see them): manage.py load_v1_db

Optionally, create a super user to log into the admin panel.

@istride - I just saw this closed, is it still helpful for me to look at the wip/v1-data-migration branch or is there an updated version somewhere else?

@isedwards  Sorry for late reply. I decided to merge this into develop so that it's obvious that it exists and make it easier to work on. The Merix team are currently working on content migration for surveys and polls.


how to generate YOLO_small.ckpt file by runing train.py?

it won't generator .ckpt file in new tensorflow version. just load the .meta and .date.

it won't generator .ckpt file in new tensorflow version. just load the .meta and .date.
@hainingbaby hi, hainingbaby. I trained the model with my own dataset, and generated 3 files named "yolo-10.data-00000-of-00001", "yolo-10.index" and 'yolo-10.meta'. How can i load the .meta and .data file? The code below can only open one weight file. Please help, tank you!
parser.add_argument('--weights', default="yolo-10.data-00000-of-00001", type=str)

@Youpretty
you can test it by "python test.py --weight_dir pascal_voc/output/your_outputdir --weights yolo-10"

The new tensorflow generate three files(.meta; .index; .data-XXX-of-XXX) instead of .ckpt file. And you can use these files like before. Put them in weights:
yolo.meta
yolo.index
yolo.data-0000-of-0001
Now run: python test.py --weights yolo

I'm new.I had this problem while running "train.py."Has anyone ever encountered this BUG? How to solve this problem？

I'm new. I had this problem while running "train.py."Has anyone ever encountered this BUG? How to solve this problem？
File "E:/CODEs/Nerual_Net_work_model/yolo_tensorflow-master/train.py", line 90, in train
train_timer.remain(step, self.max_iter))
ValueError: Unknown format code 'f' for object of type 'str'

I'm new. I had this problem while running "train.py."Has anyone ever encountered this BUG? How to solve this problem？
File "E:/CODEs/Nerual_Net_work_model/yolo_tensorflow-master/train.py", line 90, in train
train_timer.remain(step, self.max_iter))
ValueError: Unknown format code 'f' for object of type 'str'

I changed the code<<
log_str = '''{} Epoch: {}, Step: {}, Learning rate: {},'''
''' Loss: {:5.3f}\nSpeed: {:.3f}s/iter,'''
'''' Load: {:.3f}s/iter, Remain: {}'''.format(
datetime.datetime.now().strftime('%m-%d %H:%M:%S'),
self.data.epoch,
int(step),
round(self.learning_rate.eval(session=self.sess), 6),
loss,
train_timer.average_time,
load_timer.average_time,
train_timer.remain(step, self.max_iter))

to<<

log_str = '''{} Epoch: {}, Step: {}, Learning rate: {},Loss: {:5.3f}\n
Speed: {:.3f}s/iter,Load: {:.3f}s/iter, Remain: {}'''.format(
datetime.datetime.now().strftime('%m-%d %H:%M:%S'),
self.data.epoch,
int(step),
round(self.learning_rate.eval(session=self.sess), 6),
float(loss),
float(train_timer.average_time),
float(load_timer.average_time),
train_timer.remain(step, self.max_iter))


pd-worker: fix get_members_opt blocking

Signed-off-by: linning<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: #7124
Problem Summary:
When pd-server got killed, pd-worker will try to reconnect pd and issue get_members_opt request but this may never return even timeout reached , and pd worker can not handle any new task.
What's Changed:
Use get_members_async_opt and add external timeout mechanism.
Related changes
No
Check List
Tests

Manual test (add detailed scripts or steps below)

So the second time it reconnects succeeds?

request but this may never return even timeout reached

why never return?

request but this may never return even timeout reached

why never return?

This pr is a workaround for now, the root cause still need more investigating.

So the second time it reconnects succeeds?

When the pd restart and the underlying grpc connect established, it will reconnect succeed, this pr is aims to prevent pd worker from blocking and can retry later when new task arrived or  reconnect interval elapsed.

Close this pr since #7253 fixed issue #7124 .


zend-console not working as documented

The Docs say:

When a zend-mvc application is run from a console window (a shell window or Windows command prompt), it will recognize this fact and prepare zend-mvc components to handle the request. Console support is enabled by default, but to function properly it requires at least one console route and one action controller to handle the request. [...]

That seems not to be true and i can't find any code in zend-mvc (v3) that handles console-requests.
This doc should be replaced by working examples.
May be, this is an version issue. So zend-console should require zend-mvc v2 or documentation should point out that this only works with zend-mvc v2. ... and generally provide only documentation for its on functionality and usage.

May be, this is an version issue.

Right! See: https://docs.zendframework.com/zend-mvc-console/

@finalxcode 3.0.4 is from 20 Dec 2016. My Post is from 25 Jan 2017.
So i tried 3.0.4. and there is definitely no Console-Support in zend-mvc ^3.

Tive o mesmo problema e só consegui resolver instalando o modulo zendframework/zend-mvc-console

@FalkHe You need to install zend-mvc-console, as @froschdesign noted above. That package provides the zend-console integration for zend-mvc for versions 3 and up. (That said: we recommend migrating your console tooling to zfcampus/zf-console or symfony/console; zf-mvc-console will not receive long-term maintenance.)
@db9tecnologia Please use english in the github issue trackers for the ZF components and modules, to ensure everyone can understand your responses.


Launch-with documentation for Seven Bridges

Feature Request
Desired behaviour
Should look akin to https://beta.docs.dockstore.org/en/develop/end-user-topics/terra-launch-with.html
Check in  with Seven Bridges to see if we can update the homepage footer to include them as well as a "works with"
Don't forget the https://beta.docs.dockstore.org/en/develop/end-user-topics/language-support.html
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.7
┆Sprint: Seabright Sprint 18 Skipjack
┆Issue Number: DOCK-946
┆Epic: Launch-with Support

Launch-with doc looks good to Seven Bridges

Language support table still needs update

Language support table still needs update

Still true


No module named 'ldm.models.diffusion.ksampler'

How to fix it? (Windows)

Initializing, be patient...
Traceback (most recent call last):
File "scripts\dream.py", line 376, in
main()
File "scripts\dream.py", line 42, in main
from ldm.simplet2i import T2I
File ".\ldm\simplet2i.py", line 68, in
from ldm.models.diffusion.ksampler import KSampler
ModuleNotFoundError: No module named 'ldm.models.diffusion.ksampler'

Probably: either pip did not properly install 'k-diffusion', or pip didn't run at all for some reason.
I guess if it were me, I'd try removing the existing Python environment and rebuilding from scratch.

blessedcoolant's solution should do the trick for you. Please reopen the issue if it doesn't.
If the script continues to complain of missing modules, tildebyte's comment about removing the environment and rebuilding might be your safest course.

I'm having a similar issue, also on Windows (10), although the traceback has changed a bit.
Doing the additional pip install does not seem to add anything, nor solve the issue.
(ldm) G:\Production\invoke-ai\InvokeAI>python scripts\dream.py
* Initializing, be patient...

Traceback (most recent call last):
  File "scripts\dream.py", line 685, in <module>
    main()
  File "scripts\dream.py", line 49, in main
    from ldm.generate import Generate
  File "g:\production\invoke-ai\invokeai\ldm\generate.py", line 25, in <module>
    from ldm.models.diffusion.ksampler import KSampler
ModuleNotFoundError: No module named 'ldm.models.diffusion.ksampler'

(ldm) G:\Production\invoke-ai\InvokeAI>pip install -e git+https://github.com/lstein/k-diffusion.git@master#egg=k-diffusion
Obtaining k-diffusion from git+https://github.com/lstein/k-diffusion.git@master#egg=k-diffusion
  Updating g:\production\invoke-ai\invokeai\src\k-diffusion clone (to revision master)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
    Preparing wheel metadata ... done
Requirement already satisfied: resize-right in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.0.2)
Requirement already satisfied: kornia in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.6.0)
Requirement already satisfied: tqdm in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (4.64.1)
Requirement already satisfied: Pillow in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (9.2.0)
Requirement already satisfied: clip==1.0 in g:\production\invoke-ai\invokeai\src\clip (from k-diffusion) (1.0)
Requirement already satisfied: wandb in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.13.3)
Requirement already satisfied: scipy in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (1.9.1)
Requirement already satisfied: torchvision in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.12.0)
Requirement already satisfied: jsonmerge in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (1.8.0)
Requirement already satisfied: einops in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.3.0)
Requirement already satisfied: torchdiffeq in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.2.3)
Requirement already satisfied: clean-fid in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.1.31)
Requirement already satisfied: torch in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (1.11.0)
Requirement already satisfied: accelerate in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.12.0)
Requirement already satisfied: scikit-image in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.19.3)
Requirement already satisfied: ftfy in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from clip==1.0->k-diffusion) (6.1.1)
Requirement already satisfied: regex in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from clip==1.0->k-diffusion) (2022.9.13)
Requirement already satisfied: psutil in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (5.9.2)
Requirement already satisfied: pyyaml in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (6.0)
Requirement already satisfied: numpy>=1.17 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (1.23.3)
Requirement already satisfied: packaging>=20.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (21.3)
Requirement already satisfied: pyparsing!=3.0.5,>=2.0.2 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from packaging>=20.0->accelerate->k-diffusion) (3.0.9)
Requirement already satisfied: typing_extensions in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from torch->k-diffusion) (4.3.0)
Requirement already satisfied: requests==2.25.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from clean-fid->k-diffusion) (2.25.1)
Requirement already satisfied: idna<3,>=2.5 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (2.10)
Requirement already satisfied: chardet<5,>=3.0.2 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (4.0.0)
Requirement already satisfied: certifi>=2017.4.17 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (2022.9.14)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (1.26.11)
Requirement already satisfied: colorama in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from tqdm->k-diffusion) (0.4.5)
Requirement already satisfied: wcwidth>=0.2.5 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from ftfy->clip==1.0->k-diffusion) (0.2.5)
Requirement already satisfied: jsonschema in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonmerge->k-diffusion) (4.16.0)
Requirement already satisfied: pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (0.18.1)
Requirement already satisfied: importlib-resources>=1.4.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (5.9.0)
Requirement already satisfied: attrs>=17.4.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (22.1.0)
Requirement already satisfied: pkgutil-resolve-name>=1.3.10 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (1.3.10)
Requirement already satisfied: zipp>=3.1.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from importlib-resources>=1.4.0->jsonschema->jsonmerge->k-diffusion) (3.8.1)
Requirement already satisfied: imageio>=2.4.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (2.9.0)
Requirement already satisfied: networkx>=2.2 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (2.8.6)
Requirement already satisfied: tifffile>=2019.7.26 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (2022.8.12)
Requirement already satisfied: PyWavelets>=1.1.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (1.4.1)
Requirement already satisfied: docker-pycreds>=0.4.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (0.4.0)
Requirement already satisfied: Click!=8.0.0,>=7.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (8.1.3)
Requirement already satisfied: GitPython>=1.0.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (3.1.27)
Requirement already satisfied: setuptools in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (59.8.0)
Requirement already satisfied: shortuuid>=0.5.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.0.9)
Requirement already satisfied: setproctitle in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.3.2)
Requirement already satisfied: promise<3,>=2.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (2.3)
Requirement already satisfied: pathtools in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (0.1.2)
Requirement already satisfied: protobuf<4.0dev,>=3.12.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (3.19.5)
Requirement already satisfied: sentry-sdk>=1.0.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.9.8)
Requirement already satisfied: six>=1.13.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.16.0)
Requirement already satisfied: gitdb<5,>=4.0.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from GitPython>=1.0.0->wandb->k-diffusion) (4.0.9)
Requirement already satisfied: smmap<6,>=3.0.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from gitdb<5,>=4.0.1->GitPython>=1.0.0->wandb->k-diffusion) (5.0.0)
Installing collected packages: k-diffusion
  Attempting uninstall: k-diffusion
    Found existing installation: k-diffusion 0.0.1
    Uninstalling k-diffusion-0.0.1:
      Successfully uninstalled k-diffusion-0.0.1
  Running setup.py develop for k-diffusion
Successfully installed k-diffusion

(ldm) G:\Production\invoke-ai\InvokeAI>python scripts\dream.py
* Initializing, be patient...

Traceback (most recent call last):
  File "scripts\dream.py", line 685, in <module>
    main()
  File "scripts\dream.py", line 49, in main
    from ldm.generate import Generate
  File "g:\production\invoke-ai\invokeai\ldm\generate.py", line 25, in <module>
    from ldm.models.diffusion.ksampler import KSampler
ModuleNotFoundError: No module named 'ldm.models.diffusion.ksampler'

Try removing or moving the src directory and then do a conda env update -f
environment.yaml
On Fri, Sep 23, 2022 at 5:25 PM Jean-Sylvain Boige @.***>
wrote:

I'm having a similar issue, also on Windows (10), although the traceback
has changed a bit.
Doing the additional pip install does not seem to add anything, nor solve
the issue.
(ldm) G:\Production\invoke-ai\InvokeAI>python scripts\dream.py

Initializing, be patient...

Traceback (most recent call last):
File "scripts\dream.py", line 685, in
main()
File "scripts\dream.py", line 49, in main
from ldm.generate import Generate
File "g:\production\invoke-ai\invokeai\ldm\generate.py", line 25, in
from ldm.models.diffusion.ksampler import KSampler
ModuleNotFoundError: No module named 'ldm.models.diffusion.ksampler'
(ldm) G:\Production\invoke-ai\InvokeAI>pip install -e @.#egg=k-diffusion
Obtaining k-diffusion from @.#egg=k-diffusion
Updating g:\production\invoke-ai\invokeai\src\k-diffusion clone (to revision master)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing wheel metadata ... done
Requirement already satisfied: resize-right in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.0.2)
Requirement already satisfied: kornia in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.6.0)
Requirement already satisfied: tqdm in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (4.64.1)
Requirement already satisfied: Pillow in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (9.2.0)
Requirement already satisfied: clip==1.0 in g:\production\invoke-ai\invokeai\src\clip (from k-diffusion) (1.0)
Requirement already satisfied: wandb in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.13.3)
Requirement already satisfied: scipy in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (1.9.1)
Requirement already satisfied: torchvision in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.12.0)
Requirement already satisfied: jsonmerge in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (1.8.0)
Requirement already satisfied: einops in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.3.0)
Requirement already satisfied: torchdiffeq in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.2.3)
Requirement already satisfied: clean-fid in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.1.31)
Requirement already satisfied: torch in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (1.11.0)
Requirement already satisfied: accelerate in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.12.0)
Requirement already satisfied: scikit-image in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from k-diffusion) (0.19.3)
Requirement already satisfied: ftfy in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from clip==1.0->k-diffusion) (6.1.1)
Requirement already satisfied: regex in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from clip==1.0->k-diffusion) (2022.9.13)
Requirement already satisfied: psutil in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (5.9.2)
Requirement already satisfied: pyyaml in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (6.0)
Requirement already satisfied: numpy>=1.17 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (1.23.3)
Requirement already satisfied: packaging>=20.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from accelerate->k-diffusion) (21.3)
Requirement already satisfied: pyparsing!=3.0.5,>=2.0.2 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from packaging>=20.0->accelerate->k-diffusion) (3.0.9)
Requirement already satisfied: typing_extensions in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from torch->k-diffusion) (4.3.0)
Requirement already satisfied: requests==2.25.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from clean-fid->k-diffusion) (2.25.1)
Requirement already satisfied: idna<3,>=2.5 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (2.10)
Requirement already satisfied: chardet<5,>=3.0.2 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (4.0.0)
Requirement already satisfied: certifi>=2017.4.17 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (2022.9.14)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from requests==2.25.1->clean-fid->k-diffusion) (1.26.11)
Requirement already satisfied: colorama in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from tqdm->k-diffusion) (0.4.5)
Requirement already satisfied: wcwidth>=0.2.5 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from ftfy->clip==1.0->k-diffusion) (0.2.5)
Requirement already satisfied: jsonschema in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonmerge->k-diffusion) (4.16.0)
Requirement already satisfied: pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (0.18.1)
Requirement already satisfied: importlib-resources>=1.4.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (5.9.0)
Requirement already satisfied: attrs>=17.4.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (22.1.0)
Requirement already satisfied: pkgutil-resolve-name>=1.3.10 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from jsonschema->jsonmerge->k-diffusion) (1.3.10)
Requirement already satisfied: zipp>=3.1.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from importlib-resources>=1.4.0->jsonschema->jsonmerge->k-diffusion) (3.8.1)
Requirement already satisfied: imageio>=2.4.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (2.9.0)
Requirement already satisfied: networkx>=2.2 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (2.8.6)
Requirement already satisfied: tifffile>=2019.7.26 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (2022.8.12)
Requirement already satisfied: PyWavelets>=1.1.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from scikit-image->k-diffusion) (1.4.1)
Requirement already satisfied: docker-pycreds>=0.4.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (0.4.0)
Requirement already satisfied: Click!=8.0.0,>=7.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (8.1.3)
Requirement already satisfied: GitPython>=1.0.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (3.1.27)
Requirement already satisfied: setuptools in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (59.8.0)
Requirement already satisfied: shortuuid>=0.5.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.0.9)
Requirement already satisfied: setproctitle in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.3.2)
Requirement already satisfied: promise<3,>=2.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (2.3)
Requirement already satisfied: pathtools in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (0.1.2)
Requirement already satisfied: protobuf<4.0dev,>=3.12.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (3.19.5)
Requirement already satisfied: sentry-sdk>=1.0.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.9.8)
Requirement already satisfied: six>=1.13.0 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from wandb->k-diffusion) (1.16.0)
Requirement already satisfied: gitdb<5,>=4.0.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from GitPython>=1.0.0->wandb->k-diffusion) (4.0.9)
Requirement already satisfied: smmap<6,>=3.0.1 in c:\programdata\miniconda3\envs\ldm\lib\site-packages (from gitdb<5,>=4.0.1->GitPython>=1.0.0->wandb->k-diffusion) (5.0.0)
Installing collected packages: k-diffusion
Attempting uninstall: k-diffusion
Found existing installation: k-diffusion 0.0.1
Uninstalling k-diffusion-0.0.1:
Successfully uninstalled k-diffusion-0.0.1
Running setup.py develop for k-diffusion
Successfully installed k-diffusion
(ldm) G:\Production\invoke-ai\InvokeAI>python scripts\dream.py

Initializing, be patient...

Traceback (most recent call last):
File "scripts\dream.py", line 685, in
main()
File "scripts\dream.py", line 49, in main
from ldm.generate import Generate
File "g:\production\invoke-ai\invokeai\ldm\generate.py", line 25, in
from ldm.models.diffusion.ksampler import KSampler
ModuleNotFoundError: No module named 'ldm.models.diffusion.ksampler'
—
Reply to this email directly, view it on GitHub
https://github.com/invoke-ai/InvokeAI/issues/64#issuecomment-1256358163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3EVNW4BPOPAXU26ZHS5LV7XDXXANCNFSM57PAXDSA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

--
Written on my cell phone. Anything that seems odd is the fault of
auto-correct.

Try removing or moving the src directory and then do a conda env update -f environment.yaml

That seemed to do the trick, thanks

Encountering this on development branch on window. neither solution works


Set colors with JBColor and use label font

JBColor will adapt to IDE color theme
using UIUtils.getLabelFont() such that font is consistent with other "labels"

I took a look at it. I downloaded also different themes to check how it looks. If I understood it correctly than if you install other themes the base theme is always the intellij dark or white theme. When it is white then I think red and green is a bit too bright. And for the dark theme the percentage that is written on the bar cannot be seen sometimes (maybe the text on the progress bar should be black). If its possbile to fix that whould be good. Otherwise it looks fine to me!

I took a look at it. I downloaded also different themes to check how it looks. If I understood it correctly than if you install other themes the base theme is always the intellij dark or white theme. When it is white then I think red and green is a bit too bright. And for the dark theme the percentage that is written on the bar cannot be seen sometimes (maybe the text on the progress bar should be black). If its possbile to fix that whould be good. Otherwise it looks fine to me!

What do you mean by the light mode colors being too bright? How would you want the colors to be instead? I should be able to modify the color based on if the theme is light or not, but what should the color be then? If we want it more "pastel" looking then this would probably be a similar color to the one used in the dark theme. In which case this wouldn't be changing much according to the theme. I would in that case just use a fixed color for the color bars.

Yeah I would prefer the pastel looking colors like it is in the dark mode. But I see the problem then you have to check whether the IDE is in dark or light mode or find a color that fits both. If you have time for it you can change it but this wouldn't be important for me.
The only thing which would be nice if you can change it is that the percentage on the color bars is always black. Because in dark mode for some themes it is not readable anymore. After that you can merge the branch.


AzurePowershellV5: Suppress output from Az-functions

Task name: AzurePowershellV5, Common/VstsAzureHelpers_
Description:

Suppress output from Connect-AzAccount & Set-AzContext
Fix output display for hashtable used in write-host (helper function)

Documentation changes required: (Y/N) No
Added unit tests: (Y/N) No
Attached related issue: (Y/N) #19672
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

/azp run

Hello @mortenlerudjordet, thank you so much for this contribution.
The PR looks good, but before it can be merged, please bump the task version to 5.237.8 the patch version 7 is reserved.
Also, you need to do the next steps:
Install node.js v10.
Clone the repository and call the next commands from your CLI:
npm i
node make.js build --task AzurePowerShellV5

You would see a bunch of generated files in the git status.
Please, add them to this PR - they are required.

@v-mohithgc or @LeftTwixWand, please run the pipeline again with the new changes added to the PR.

@LeftTwixWand ; I have merged in the changes done on master,
Do I need to bump the patch number to 9 before this can be merged in as 8 now is taken?

@vincentdass : as code owner for Common/VstsAzureHelpers_ can you review the change I have proposed?

Hi @mortenlerudjordet , the PR checks are expected to fail as the task version isnt bumped.
please increase the minor version of this task to 238 and patch to 0, in task.json file and then run the build command (node make.js build --task AzurePowerShellV5) and then commit the changes.

/azp run

@v-mohithgc : Will I have to bump version on all these other tasks also?
Tried to run build on all in the error msg from the pipeline, but not all task in the list gets files under _generated after build complete.
Only see files generated for:
AzureFileCopyV2
AzureFileCopyV3
AzureFileCopyV4
AzureFileCopyV5
AzureFileCopyV6
AzurePowerShellV4
For the other tasks seems like the reason from the build logs is this:
Unable to find package.json file for AzureCloudPowerShellDeploymentV2 in _generated folder or Tasks folder, using default node 10.
See pipelines are failing on:
The following tasks should have their versions bumped due to changes in common: AzureCloudPowerShellDeploymentV1,AzureCloudPowerShellDeploymentV2,AzureFileCopyV1,AzureFileCopyV2,AzureFileCopyV3,AzureFileCopyV4,AzureFileCopyV5,AzureFileCopyV6,AzurePowerShellV2,AzurePowerShellV3,AzurePowerShellV4,SqlAzureDacpacDeploymentV1

I will remove the change to Common/VstsAzureHelpers_ and create a new PR without to make it simpler to approve


Documentation comments + Doxygen support

Hello! Sorry for disappearing for the last few weeks, work was tough.
I have documented the code I wrote and added Doxygen support! It looks really nice.
In order to generate the documentation, firstly install Doxygen and Graphviz:
# Ubuntu 22.04
sudo apt-add-repository universe
sudo apt-get update
sudo apt-get install doxygen
sudo apt-get install graphviz

Then run Doxygen:
doxygen doxygen.conf

Two folders named html and latex should appear.

Hi again @andrewlod
No problem.  I have been a bit busy here too with my work.  I will go ahead and test and review this.


Detector spec refactor

Following a discussion with @OStevan about https://github.com/informalsystems/tendermint-rs/pull/446, I am going to refactor the supervisor and detector spec in #479 so that the supervisor maintains a lightstore that only contains lightblocks that have been cross-checked, (or the once that have been verified with the primary that resulted in a cross-checked state).
To do so, we need to

pass  auxPrimaryLightStore into VerifyToTarget
pass a trusted and the latest verified into the detector
update the supervisor lightstore once we finished cross checking (insert the auxPrimaryLightStore)

This will allow us to ignore the state of lightblocks in the supervisor lightstore, as they all have been cross checked. This defines a cleaner interface: All lightblocks in the supervisor lightstore can be used by the user. All lightblocks in the supervisor lightstore are on a chain that lead to a cross-checked (trusted) lightblock.

This will allow us to ignore the state of lightblocks in the supervisor lightstore, as they all have been cross checked. This defines a cleaner interface: All lightblocks in the supervisor lightstore can be used by the user. All lightblocks in the supervisor lightstore are on a chain that lead to a cross-checked (trusted) lightblock.

I agree with being able to ignore "state" of headers and having a store that only has headers that can be used by the user. But I also think we're going to need a more nuanced view of what can be "trusted" / put into the supervisors light store / used by the user, and our thinking about the problem on the full node side is I think a bit muddled by having a static set of peers. The problem right now is that with a static set of peers and assuming at least one is correct, we don't even need to do verification, we could just be comparing headers (until there's a conflict).
I think we want to move towards a model that functions more like the on-chain IBC light client, where we assume that eventually, within the trusting period, we will hear from a correct node (relayer in the IBC case). The basic version is to always trust (ie. "expose to the user") the first thing that gets verified, but to still be on the lookout for potential conflicts, that you might only discover later.
Even if we start with a static set in the implementation, we should probably be formulating the problem as if there were a dynamic set, and with more alignment with how the on-chain ibc client operates.
This may mean that we expose a new time parameter to the users which is effectively "how long after verifying a header do you want to trust it". For the light node, this would give it time to talk to more nodes, find new peers, look for conflicts, etc., while for the on-chain IBC client, it would give other relayers a chance to submit conflicts before anyone can use the latest verified state. Of course this will make relayer logic even more complicated because they'll have to wait these timeouts before they can submit proofs based on them (unless we support more optimistic execution on chain)
Of course users could set this timeout to 0, which means they trust the header right away, but are always open to finding out later that it was wrong as fork detection continues.
It might also be practical to have some hybrid between time and number of full nodes to cross-check with.
There's been some prior discussion on Stores that I would flag as likely related as well, #428, #420. And I thought @OStevan raised an issue about making some functions less store based and more functional but I can't find that now.

I should have read the latest #479 before writing the above comment :) But I guess the important addition is the idea of a new time parameter. I actually had this sketched out in Rust last September, the following comment:
This module builds up a map from peers to chains.
After the same header has been seen across some number of peers
and over some amount of time, it can be trusted.

This might more naturally capture the concurrent structure of a light client, ie. running the light client independently for each node, but presumably not re-verifying common headers (ie. we could cache signature validation so the same signature is never verified twice), and waiting some amount of time to detect conflicts.

https://github.com/tendermint/spec/pull/164 closes this one.


Drawer menu always opened in Android Stock Browser

Hello.
I use a fixed header and the drawer menu is always open in the Android Stock browser I'm testing. I tried it with the installed Chrome version in the Android device and it works fine any other browser and device tested is also working fine.
This is the user agent of the browser in a LG G2 updated to Lollipop 5.0.2 "Mozilla/5.0 (Linux; Android 5.0.2; LG-D802 Build/LRX22G) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/34.0.1847.118 Mobile Safari/537.36"
It's a bit worrying because it should be a widely used browser and the side drawer menu uses more than half screen when is opened.

Ok. It was my fault.
I'm including material-design-lite.scss in my scss source and the resulting css is not including the WebKit prefix to make the css3 transforms work in the android stock browser.
Answer:Does Android's Stock Browser support CSS3 transforms

@jmtalarn Good to hear you worked it out. Yes, we are running gulp-autoprefixer on the compiled CSS rather than the SASS.

@surma: Could you mention the required use of autoprefixer in the docs for people using the scss files? I spent some time finding the error in my html code until reading this post...
@jmtalarn: Thanks a heap.


Can not vote

I voted for Masternode "Earth" 2 times, 10 TOMO each time. My balance was deducted but the "Total Voted" and "Candidates" remain blank.

I saw you voted 2 times (30 TOMO, 10 TOMO), https://scan.testnet.tomochain.com/address/0x8f940e07a7e229a8224f88f349f6801ad68265a4
The votes was recorded in smart contract, but there is use with display the data it TomoMaster. We will fix it.
I have to convert your address from image to text so that i can test your case. So it is better for me if you paste your address in the description.
Thank you for the contribution

I deployed a hotfix, it should for now, please check it again @anhntv2012

It works perfectly now. Much appreciated.


ClockTokens: Accommodated multi-GM games and games where the creator is not a GM.

ClockTokens v1.1: Changed logic to accommodate multi-GM games or games where the creator is not a GM.

@NicholasR77 I believe I've made the changes you mentioned. Let me know if anything else needs updating.


Prevent running view.remove() in the cleanup function or add note in docs

I did not realize that the cleanup function runs during view.remove(). I added a view.remove() call within the cleanup function returned by render() and then this caused an infinite loop in my widget by accident.
It might be possible to prevent users from getting in this situation in some way, but I am not sure. Maybe instead of passing this to render, a different object could be passed without a remove property or with remove() somehow overridden as a no-op?
https://github.com/manzt/anywidget/blob/8e589912f7a60989b90a5683a5a35a8a67456c08/packages/anywidget/src/widget.js#L174
If preventing it is not possible, the docs about the cleanup function could note that view.remove() should not be called inside the returned function, or could clarify that the cleanup function is run during DOMWidgetView.remove

Thanks for reporting! Do you think we could use a Proxy? Maybe patch .remove() as a no-op with a console.error to warning.