In the custom circuit class, no method to return the wavefunction

In the circuit class, there is a method to plot the wavefunction [Circuit.plot_wavefunction], but no method that returns the wavefunction itself. It would be very useful to be able to get the wavefunction data as a numpy array to be able to manipulate it on our own.

Ideally this method would allow the user to also specify the basis in which the wavefunction is returned (it is currently plotted in the phi basis, so choosing either this or the default basis would be helpful).

Hi @pdparakh108, the wavefunctions of the Circuit instance can be accessed in the same way as for any other qubit instance - which is Circuit.eigensys(), which returns a tuple of eigenenergies and the corresponding wavefunctions in the basis that is defined for the Circuit instance (If hierarchical diagonalization is used, the wavefunction will be in the product basis of the subsystems it comprises). If you would like to get the data for the wavefunctions that are being plotted, you can use the following method as well:
plot_data = circ.generate_wf_plot_data(
            which=1,
            var_indices=(1,2),
            eigensys=esys,
            change_discrete_charge_to_phi=True,
            grids_dict=circ.discretized_grids_dict_for_vars(),
        )

Where I am using a method which is not described in the documentation. But, this is the very method that is used internally to generate the date for plotting the wavefunction. Please let us know if that helps.

Hi,
Thank you so much! This is very helpful.
Best,
Pranav

On Apr 29, 2024, at 1:04 PM, saipavanc @.***> wrote:
Hi @pdparakh108 https://github.com/pdparakh108, the wavefunctions of the Circuit instance can be accessed in the same way as for any other qubit instance - which is Circuit.eigensys(), which returns a tuple of eigenenergies and the corresponding wavefunctions in the basis that is defined for the Circuit instance (If hierarchical diagonalization is used, the wavefunction will be in the product basis of the subsystems it comprises). If you would like to get the data for the wavefunctions that are being plotted, you can use the following method as well:
plot_data = circ.generate_wf_plot_data(
which=1,
var_indices=(1,2),
eigensys=esys,
change_discrete_charge_to_phi=True,
grids_dict=circ.discretized_grids_dict_for_vars(),
)
Where I am using a method which is not described in the documentation. But, this is the very method that is used internally to generate the date for plotting the wavefunction. Please let us know if that helps.
—
Reply to this email directly, view it on GitHub https://github.com/scqubits/scqubits/issues/217#issuecomment-2083231650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXPN4XIFF62CUZR6KR7VRKLY7Z4Q7AVCNFSM6AAAAABG6R5J7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTGIZTCNRVGA.
You are receiving this because you were mentioned.


Error: undefined is not an object evaluating 'react2.default.PropTypes.string'

Pls check the lib.
When i try run example is meet error

@Donhv yes, problem PropTypes not update,
try this
"react-native-flat-buttonreact-native-tag-select": "github:herarya/react-native-flat-button"

fixed in v1.0.6 @Donhv @herarya


The synchronous post request for copying returned before the file is actually copied.

Hi,
I wrote the below code for copying a file using synchronous post request.
`
final ItemReference parentReference = new ItemReference();
parentReference.path = getOneDrivePath(dst.getParentPath());
mClient.get().getDrive()
.getItems(src.getFileId())
.getCopy(dst.getFileName(), parentReference)
.buildRequest()
.post();
`
After the post returned, I request the item copied just now. But the item doesn't exist. So I tried to request the item in a loop (polling) then I can get the copied item through several times tries. I thinks post should be returned after the copied item is available.
Any idea?

The result of the copy is not the copied item, but an asynchronous monitor that can be polled for when a copy action has completed.
See the detailed copy documentation.  In the OneDrive Explorer for Android, there is also a full example of how the copy system works.

@peternied Thanks a lot. 👍

I'm going to close out this question since you have got the answers you need, if not please reopen.  If you happen to have any other questions/comments open up a new issue.


Insertion Sort.cpp

I have added code for insertion sort. Kindly merge my code.

Thanks for your contribution!

PR has been merged under hacktoberfest!

Happy contribution!


Nuproj.Common package for non-NuProj projects

Package that provides _NuProjProjectReferenceClosure target.

This LGTM. @terrajobst what do you think?
@kovalikp how does this new .nuproj get built? I don't see any change to wire it up to the overall build or add it to the solution.

Well, this is just quick and dirty solution for our problem.
With this, user will have to install NuProj as a solution package, and NuProj.Common to the .csproj dependencies (should probably mention this in docs).
To use build\NuProj.props and build\NuProj.targets for .nuproj projects as suggested earlier, we would have to add CPS;AssemblyReferences;DeclaredSourceItem;UserSourceItems capabilities.
At least according to this https://github.com/NuGet/NuGet.VisualStudioExtension/pull/30. But AssemblyReference capability is not applicable in our case.
Ideally NuGet would support atomic capabilities for AddFile, AddReference, AddFrameworkReference, AddImport and so on. Or even better, have a capability to somehow get implementation of IMSBuildNuGetProjectSystem from CPS project. Maybe I should put this into coherent proposal and raise an issue in NuGet project.

I'm in close contact with the NuGet folks to break up their bulk check for these several capabilities to allow for AssemblyReferences at least to be missing. I haven't heard a commitment to support for RTM yet, but they do want to add support for it to support other CPS-based projects too.
I agree we should not advertise such support in nuproj inappropriately.

@AArnott @terrajobst are you going to merge this?

I like it, yes. But my earlier question remains:

how does this new .nuproj get built? I don't see any change to wire it up to the overall build or add it to the solution.

I'd like to see this wired up so that it builds the new nupkg with the rest of the code so we can build and publish it altogether. Or do you have something else in mind?

Ah, sorry. I thought you were asking about how users' .nuproj files get build.
package.proj file picks up all .nuproj files from src\NuProj.Packages directory. See here: https://github.com/nuproj/nuproj/blob/master/tools/package.proj#L39

OK. I wasn't expecting a wildcard. cool.
I'll try out these changes locally and merge if all looks good.


⚠ Syncthing-KA-TM has degraded performance

In fac49e6, Syncthing-KA-TM ($URL_SYNCTHING_MERZ_NIMBUS_TM) experienced degraded performance:

HTTP code: 200
Response time: 8513 ms

Resolved: Syncthing-KA-TM performance has improved in 0c278c3 after 5 minutes.


Question about window resizing issue.

I'm using this plugin for a couple pages that I'm working on but have ran into a slight issue that I am hoping you could help me out with.
I have the animation working exactly the way I want, however, when I resize the browser a lot of the content sizes change as well. This means that all my starting and stopping points, and my transform amount all have to be different.
I see you have a refresh call, which looks like it calls the init again, but is there a way to update the data amounts before you refresh?
Thanks in advance.

Hey y'all,
I'm having a similar issue, but opposite. After resizing the window, skrollr stops affecting the opacity, though it seems to successfully affect the location.
Skrollr is a plug-in included in a Wordpress theme I'm working off of (https://wordpress.org/themes/cover/).
It seems to be affected by my function where I set the height of a feature article container to full window height:
    function featureSet(){
        var height = ($(window).height());
        height = height + "px";
        console.log(height);
        $('.owl-item > div').css('min-height', height).css('max-height', height);
    }

The only place I can find a solid mention of the skrollr function is &&jQuery(".cover").length>0&&skrollr.init({forceHeight:!1})
I've tried adding skrollr.get().refresh(); and skrollr.init(); inside a $(window).resize function which seems to have no effect.
Any new solutions?

$(function() {
skrollr.get().refresh();
});
Putting that after init did it for me.


Improvements for Jupyter intro

The first thing that should be taught is running code--that's why we're using it after all
By doing that first, Markdown will be naturally cut down, which it should be

This is how it is in the notebook we have, I just apparently did my own thing during the UW workshop. Just need to make sure to follow the notebook even thought I’m “live coding”


Set up rust

The link for the "set up rust" article leads to a page not found error, both from the homepage and from the article that precedes it. Don't know if this is a mistake or if it's just that it hasn't been written yet.

Cannot reproduce

Me neither.
@yarwelp Can you provide more information? Exact links for the affected pages would be best.

Well it works now but I swear it was saying that the page could not be found yesterday.
The URL in question was https://os.phil-opp.com/set-up-rust/ and the links that I followed to get to it were from the pages https://os.phil-opp.com/entering-longmode/ and then https://os.phil-opp.com/ and I tried both multiple times without success yesterday, but as I said now it works.
Heisenbug?

/shrug
The web works in mysterious ways.


Implement a high-level shadow document interface

This PR implements a high-level interface to the shadow document service.

Codecov Report

Merging #16 (b675841) into main (f68bb2c) will increase coverage by 5.15%.
The diff coverage is 95.12%.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
+ Coverage   79.53%   84.69%   +5.15%
==========================================
  Files           4        5       +1
  Lines         430      588     +158
==========================================
+ Hits          342      498     +156
- Misses         88       90       +2

Impacted Files
Coverage Δ

src/AWSCRT.jl
65.85% <ø> (+0.85%)
:arrow_up:

src/AWSMQTT.jl
86.33% <0.00%> (+0.19%)
:arrow_up:

src/ShadowFramework.jl
96.05% <96.05%> (ø)

src/IOTShadow.jl
100.00% <100.00%> (+25.00%)
:arrow_up:

... and 1 file with indirect coverage changes


[Feature] Create controller for GC(resource tracker) mechanism

Currently, we create resourceTracker for every revision, and blindly delete the old revision resource tracker to let the GC mechanism of K8s to do the real GC. This mechanism has some drawbacks:

It's not flexible enough for different GC strategies, we always rely on application controller to do GC
It could cause resources leak when the revision increase but the reconcile fail. For example, some of  resources in revision v1 created except one, and we change the resource so the new revision(v2) created but it still fails. And we create v3. Then we don't have any way to GC v1 resources.

In conclusion, we should just have one resource tracker to one app per environment(cluster). And we should create a resource tracker controller for it.
kind: ResourceTracker
metadata:
  generation: 1
  name: myapp-mynamespace
spec:
  resourcesType:  // resourceType record all resources kind related in ResourceTracker
  - apiVersion: xx
    kind: xx
  strategy:
    stopGC: false // rollout process should set it to true
    GCLoopDuration: 10m
  appName: myapp
  appNamespace: mynamespace
  revision: myapp-v2
  components:
  - name: mycomp
     resources:
    - apiVersion: xx2
       name: yy1
    - apiVersion: xx1
  - name: mycomp-2
     resources:
    - apiVersion: xx2
       name: yy1
    - apiVersion: xx1
status:
  observedAppRevision: myapp-v2
  lastGCTime: <rfc-time>
  components:
  - name: mycomp
     resources:
    - apiVersion: xx2
       name: yy1
    - apiVersion: xx1

update resourceTracker by component
after application reconcile success, remove unexisting component.

After an off-line discussion with @wonderflow, new ideas are recorded as below:

In an app upgrading scenario, “Create(new resources)” and “GarbageCollect(old resources)” must be coupled and synchronized.
Once new revision’s resources are created, it must garbage collect old revision’s resources immediately.
And further upgrading on this app must be blocked until previous garbage collection is done.
Otherwise, if “create” and “GC” become asynchronized, rapid upgrading will result in resource races, as GC mechanism
cannot determine which resources should be deleted and which should be retained.

Based on conclusion 1, we don’t need an extra ResourceTracker controller to do GC jobs.
The one who asks for creating resources is the one who is responsible for invoking GC.
Currently, dispatch module is in charge of this.

Each app revision has a paired ResourceTracker.
Comparing to the idea that each application has only one ResourceTracker, this brings us convenience on tracing
history resources of a specific app revision.
In some scenarios, we may need to retain resources of an app revision even newer revision is released.

Currently, we just fix below issue with minor changes:

It could cause resources leak when the revision increase but the reconcile fail. For example, some of resources in revision v1 created except one, and we change the resource so the new revision(v2) created but it still fails. And we create v3. Then we don't have any way to GC v1 resources.

We'll still keep the current way for GC, closing


Tensor Parallelism fix

[x] Tensor parallelism works
[x] Lazy loading system making TP usable with minimal code change

Current support for TP:

[x] LLama, full support: parallel embeddings, parallel self attention (the gate_proj can be handled better via merging), parallel mlp.
[x] GPTNeo
[x] BERT
[x] RoBERTa

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

1 - looking at other optimum backends, including the neuron inference backend, It seems that the general pattern/paradigm is to create mirror classes of the transformers classes implementing the same APIs: here you seem to be heading in a different direction, keeping the same classes but modifying their behaviour. Is this an implementation constraint or a design choice ?

The reason I do this instead of having seperate classes is because then I would need to do the same thing for all the AutoModel classes where what I want to change is not really dependent on them. Also we want to keep the example code change as minimal as possible.

2 - you make an heavy use of monkey patching. Again, is it a constraint or a design choice ? If it is a design choice, on what grounds did you take it ?

A bit of both. Basically, we want to be able to change the original Trainer behaviour without copy pasting big methods just to change one line of code. While this is not neat, this is the best approach we found.

Merging after discussing offline.


As a user, the app updater should give me the option not to download an update

When cancelling, it seems it still tries to validate the (cancelled) download.

Steps to reproduce:

downgraded package.json version to 1.2.0
yarn build
moved ./release/mac/Grid to /Applications
run Grid

Additionally, when I run yarn start:dev, I get another uncaught exception.

Initial issue (buttons) fixed.


plis support :(

Plis support Asus Zenfone 4 T00I

@zhuowei Is working on it.

How rough is @zhuowei working right now, I mean is he doing well?


[Terra-Tag] Update examples

Summary
Updated Example  for ensuring that the terra-tag has realistic examples.
What was changed: Updated the about page for terra-tag
Why it was changed: To update examples to be realistic.
Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[x] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-9334

---
Thank you for contributing to Terra.
@cerner/terra

+1 for the updated accessibility example.


Reference AUR package

I've created an AUR package to automate/structure installation for ArchLinux users here: https://aur.archlinux.org/packages/kak-lsp-git/ - this adds a reference to it in the README.
Regarding the package itself, happy to incorporate any suggestions / changes to the install process. You can see the PKGBUILD file here.

Thank you for contribution!
PKGBUILD looks fine to me, the only thing which might need to be fixed is install -Dt "${pkgdir}/etc/" kak-lsp.toml — unfortunately at the moment kak-lsp doesn't try to read from that location and after installation it will be not immediately usable. User need to copy config manually into ~/.config/kak-lsp/. I think it might be worth mention in package description and/or in installation message. I raised #44 to fix this problem (actually I will do it right now because it's easy to do and result should be quite beneficial)

Yeah, there's a post-install message about that (as well as activating the systemd unit) - https://aur.archlinux.org/cgit/aur.git/tree/kak-lsp-git.install?h=kak-lsp-git

Ah, I missed it, thanks for pointing out correct place. Anyway, with the latest master copying file should be required only for customization (which I guess virtually everyone does because default config is far from being complete or universal).

@GordStephen Yo! Thanks for the AUR submission.
A few things to point out in the PKGBUILD:

The v from the version should be parsed out.  Mentioned in the VCS package guidelines
The example you have put into /etc/kak-lsp.toml should be removed and placed into /usr/share/$pkgname/examples/kak-lsp.toml
I also think you should be using install -Dm644 and such when installing files.

Thanks for the feedback! I'll push a new release.

@Foxboron I incorporated those changes, if you have any other suggestions let me know.

They look great! Awesome work :)


add p2/index.qmd

add p2/index.qmd

Great job @yyuanxuan, looking good!
Can you add spData to the package with:
usethis::use_package("spData")

And any other packages not currently in the DESCRIPTION file?

Great job @yyuanxuan, looking good!
Can you add spData to the package with:
usethis::use_package("spData")

And any other packages not currently in the DESCRIPTION file?

Thanks for the advice, p2 (link) is now working ok. This gives me much more confidence to continue porting the other practicals and I am happy to do that.

Great job, good to see tests passing!


Usage with Ecto 2.0

monetized (version 0.4.0) requires ~> 1.1.1
phoenix_ecto (version 3.0.0) requires ~> 2.0.0-rc
Locked to 2.0.2 in your mix.lock

** (Mix) Hex dependency resolution failed, relax the version requirements of your dependencies or unlock them (by using mix deps.update or mix deps.unlock)

Thanks for letting me know.
I've gone ahead and updated to ecto 2 which should resolve this issue. 👍


Sidebar resize area overlapping scrollbar and color selector

The width of the vertical bar that allows to resize the sidebar is too big.  It overlaps both the scrollbar on the left and (among other things) the color selector on the right.  The result is that clicks in the scrollbar don't scroll the document but rather enable the sidebar resizing.  The same is true for clicking the color selector.  For the latter, the workaround is to click near the right edge of the colored box; this is interpreted correctly as a click on the selector.
I have reproduced the issue in Firefox 4, IE 8 and Safari 5.0.5 (WebKit 533.21.1) - haven't tested any other browsers - running EtherPad 1.1 on a Linux host.

I've the same problem, and it's really cumbersome when working with larger documents.


[backport] P2P decentralization improvements

This is a backport of #5329.
It also includes changes from #5287 to avoid conflicts and updates go-libp2p to a more recent version.

This PR requires https://github.com/spacemeshos/api/pull/293 to be merged first in the api repo, after which v1.21.1 release of the api repo needs to be tagged, and go.mod needs to be updated accordingly in this PR.

windows-latest test failure appears to be unrelated to the PR, rerunning failed jobs:
=== FAIL: node TestPeerInfoApi (4.69s)
2023-12-25T17:20:06.250Z	WARN	00000.defaultLogger	attempt to SetLevel of logger lower than parent level, this may result in log entries being dropped silently
    adminservice_api_test.go:61:
        	Error Trace:	D:/a/go-spacemesh/go-spacemesh/node/adminservice_api_test.go:61
        	Error:      	"0s" is not greater than "0s"
        	Test:       	TestPeerInfoApi
        	Messages:   	uptime should be set

bors merge

Same failure in the test run w/o d14n changes, so trying another time...
https://github.com/spacemeshos/go-spacemesh/actions/runs/7330671330/job/19962145193

bors merge

bors merge

MacOS test flake this time
=== FAIL: txs TestCache_Account_Add_UpdateHeader (0.01s)
    cache_test.go:644:
        	Error Trace:	/Users/runner/work/go-spacemesh/go-spacemesh/txs/cache_test.go:644
        	Error:      	Target error should be in err chain:
        	            	expected: "bad nonce"
        	            	in chain:
        	Test:       	TestCache_Account_Add_UpdateHeader

bors merge

bors merge

Systests:
=== NAME  TestPartition_30_70
    logger.go:130: 2023-12-29T17:42:14.927Z	ERROR	TestPartition_30_70	client state differs from ref state	***"client": "smesher-12", "ref_client": "boot-0", "layer": 18, "client_hash": "0x0000000000000000000000000000000000000000000000000000000000000000", "ref_hash": "0x50dfb24d60ad37f00b391da907af53ca47cde9d14f8280bce2fd89ae70e41a10"***
    partition_test.go:167:
        	Error Trace:	/build/systest/tests/partition_test.go:167
        	            				/build/systest/tests/partition_test.go:182
        	Error:      	Should be true
        	Test:       	TestPartition_30_70
    logger.go:130: 2023-12-29T17:42:14.949Z	INFO	TestPartition_30_70	namespace was deleted	***"namespace": "test-ihxo"***
--- FAIL: TestPartition_30_70 (922.95s)

IIRC this was not observed before, let's consider it a flake

bors merge


Go To Source Definition UX improvements

Following up on TypeScript’s new Go To Source Definition command (d851ea5d49b0ec89b98765d9e0084c25f2ff5031), I want to track some editor-side UX improvements:

Can we replace the error notification for “no source definitions found” with an inline message similar to Go To Definition?

Can we somehow indicate when a result is a guess? This is already returned in the protocol response via an unverified property, but it is never surfaced to the user. When multiple locations are returned, maybe we could add something to the peek locations UI:

(Note: the unverified flag is also sometimes set in normal Go To Definition responses, so this request is not specific to Go To Source Definition.)
When only one location is returned, maybe a notification would suffice, but I would love design input on this.

@jrieken Any thoughts on these? I think we'd have to implement these in core

Can we somehow indicate when a result is a guess? This is already returned in the protocol response via an unverified property, but it is never surfaced to the user.

There is currently no way to express that but it reminds me of https://github.com/microsoft/vscode/issues/74237 which is about adding a kind-property to references/locations. That would allow us to classify/filter/etc...

Can we replace the error notification for “no source definitions found” with an inline message similar to Go To Definition?

No sure how "go to source" is implemented but in case it is using the editor.action.goToLocations-command that a "no-results-message" can be passed


Adding Newgiza University , Egypt

@AhmedNaeim1 First stage of verification passed, official domain is ngu.edu.eg as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@AhmedNaeim1 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[Flutter GPU] Standardize a message error pattern.

Part of https://github.com/flutter/flutter/issues/130921
Right now, we have a mix of error handling that may be confusing to users.

Sometimes a success boolean is returned.
Sometimes an exception is thrown if there's a problem.
Sometimes Impeller validation will catch problems and rendering will fail.
Sometimes the Impeller backend will allow something invalid to happen and rendering will silently fail unless the user has Metal or Vulkan validations enabled.

Recommendation: Bias heavily towards exception throwing.

For dart-side parameter guards, use message asserts instead of exception branches.


Fix missing content style

fallback code is missing the content style in the &::before, &::after

Thanks for fixing this for me, much appreciated.


Add golangci-lint.yml

Fix #16

Help welcome. Currently stuck. Error below.
run golangci-lint
  Running [/home/runner/golangci-lint-1.53.3-linux-amd64/golangci-lint run --out-format=github-actions] in [] ...
  level=warning msg="Failed to discover go env: failed to run 'go env': exit status 2"
  level=error msg="Running error: context loading failed: failed to load packages: failed to load with go/packages: err: exit status 1: stderr: template: main:1: function \"context\" not defined\n"

  Error: golangci-lint exit with code 3

Help welcome :)

I'm happy to take over this one :+1:

@puerco, thank you!. I'll re-assign this to you!

@puerco, let me know if and when you want a review!

Thank you, @wey-chiang!

O wow, I had not noticed this. Thanks for handling it john speed, we can now enable golangci lint


Link Header case broke getV1BatchTokenFromHeaders

getV1BatchTokenFromHeaders fails to parse the batch token using headers returned from a V1TransactionsApi listPaymentsWithHttpInfo call since it looks for isset($http_headers['Link']) and headers are now returned lowercase.
To be clear, a one character workaround is isset($http_headers['link']) on line 289 in ApiClient (note lowercase "link").
Any suggestions?

Thanks for reporting! We'll take a look. To get around this, feel free to download the SDK repo locally and use it instead of via Composer etc, and make the change in your local SDK so it correctly retrieves the link header.
I'll update this once we actually resolve this or have more information, though.

Just heard back from internal teams, this should be resolved now. Please let me know if you're still experiencing it, though.

Thank you for the reply, but still coming through lowercase for me.

...try again! No, seriously, we realized we missed a spot, and this should now really be resolved 😄. Sorry for the confusion, but appreciate you letting us know. Definitely let us know if you have any further issues or questions in the future!


Can you please tell me that on which version of python the code was written?  I'm getting this error now after trying a lot.

Can you please tell me that on which version of python the code was written?  I'm getting this error now after trying a lot.
help me with this...
or please tell me step by step which version of python I have to use then which are the libraries I have to install.
I have followed all the instructions from the readme file in the project, still, I'm not able to run that.

Originally posted by @deepanshuparuthi in https://github.com/Karan-Malik/FaceMaskDetector/issues/8#issuecomment-827462755

The code was written on Python 3.7.
For the library versions used you can check the requirements.txt file in the repository.

i got this now

You haven't included the error in this image. Send the image of the last few lines of the error you receive.

Here it is

that error was solved using pillow library..help me solve this one

Resolved all the errors, Thanks!

Resolved all the errors, Thanks!

How was this issue resolved?


Improvements of the "Gettings started" guide

I tried to setup my first ResinOS installation on an Ordoid-C1. Since I have no easy means to install nodejs 6.x I could not use rdt and thus went for the manual configuration. I got stuck/confused in section https://resinos.io/docs/odroid-c1/gettingstarted/#configure-the-image.

And edit the ssid and psk values in the /boot/system-connections/resin-sample connection file

Since I have no WIFI but use an ethernet connection, I was not sure if I would get a working network connection in case I do not change the configuration shown in the manual. So I mounted the image on the loopback device and searched for alternative configuration examples for an ethernet card (with no luck).
Two sections below in "Boot the device" I got the answer about my WIFI/ethernet problem:

You will also need to ensure that the device can connect to the network, either via ethernet or wifi.

Yeah, yeah ... maybe i should have read on before trying to configure the ethernet settings manually. I propose to change "Configure the image" of manual configuration:  point out that an ethernet connection is configured by default and no settings have to be changed in case an ethernet connection is used.
Here the 2nd point:  a link or a description how to change the files manually would be fine. Creating loopback devices, mount it ...

Some minor improvements:
Section https://resinos.io/docs/odroid-c1/gettingstarted/#install-resin-device-toolbox:

node.js 6.x is listed as dependency - but node.js 4.8 works fine. The npm Package description of resin-device-toolbox also shows NodeJS >= 4.

Section https://resinos.io/docs/odroid-c1/gettingstarted/#get-a-container-running add

$ cd resinos-sample
$ rdt push resin.local -s .

Just rdt push resin -s . did not work. I had to add .local to the hostname to resolve it.

@agherzan ^

@mh182 sorry for the late reply. @shaunmulligan this sounds like a documentation problem / rdt. Can you confirm? Who should take a look on this?

@agherzan these are indeed documentation issues, some of them have already been addressed in updating the docs to use resin cli instead of rdt, but the ones haven't yet. I'm not sure who can pick this up at the moment, I might have some time later this week.

ping @shaunmulligan

maybe also ping @zwalchuk

I'll take ownership of this

Moving to resinos repo, https://github.com/resin-os/resinos/issues/354. Will address with other documentation changes


Filename of Unshared Projects

Should be the file name of the downloaded project if possible (you can extract it from within the <title> element of the normal project viewer page, and there might be an API method too.

Hmm... I'll work on this later. I don't have time until Thursday. If
anybody writes a pull request while I'm gone, I will merge it. Thanks for
reporting this bug.
On Friday, June 24, 2016, joker314<EMAIL_ADDRESS>wrote:

Should be the file name of the downloaded project if possible (you can
extract it from within the  element of the normal project viewer
page, and there might be an API method too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scratchyone/sb2edit/issues/3, or mute the thread
https://github.com/notifications/unsubscribe/AK8oJXzpvfcYsxKkId-yqdFhHOBSstgLks5qPCrbgaJpZM4I-Cn_
.

--


Email venues to request missing or unclear fire safety and evacuation information.

[ ] Sheffield - Learn create sell
[x] Manchester - DF Capital
[ ] Manchester - SeeSaw
[x] London - Holborn Office
[ ] Birmingham  - Aston University
[ ] Birmingham - iCentrum
[ ] Scotland - Strathclyde University
[ ] London - Brixton

Manchester - Information complete
London Holborn - Closed
Scotland - Strathclyde University: Sent email to Katie Bharaj

Lili has mentioned before that calling Zack from learn create sell works better than email.

Manchester DF Capital:

Holiday period opening confirmed.
Alarm is not working as they stated - Tony will send us the details when he heard back from Alarm company.
Challenge to find who has the missing fobs.

Scotland - Strathclyde University - to update with latest info

Birmingham - Aston Uni: All information sent by Tony is updated in Space Guidelines and Venue Management

London Brixton - to update


Unable to filter dimension in chart by double click - after update from Supserset 2.0.1 to 2.1.0

After update to 2.1.0 from 2.0.1 we are unable to filter one line on chart with multiple dimensions via double clicking on it. (Does not depends on chart type: for example, Time-series Area chart and time-series bar chart had been tested).
It was very useful feature and all of our charts were depended on it (on version 2.0.1) - our users would simply double click on a single line to explore certain tendency rather then disabling every other line via navigation bar on top-right of the chart.
Are there any options to turn this feature back on?
How to reproduce the bug

Go to any chart (for example, 'Time-series Area chart') with multiple dimensions
Double click on a single row

Expected results
Only chosen dimension left on a chart
Actual results
Nothing happens, there are still multiple dimensions on a chart.
Environment

browser type and version: Google Chrome 109.0.5414.120 (also tested on Firefox 111.0.1)
superset version: superset 2.1.0
python version: python 3.8.12
node.js version: node 10.24.0

Checklist

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Same issue here.

Well, I'm trying to find out the reason this feature isn't working.
I'm not a frontend developer and sorry for possible confusing, but here are some results:
Comparing 2.1.0 with 2.0.1 in debug mode will show that EchartInstance reference won't be got anymore, I guess the problem in the reference handler:
https://github.com/apache/superset/blob/357745f418d3eb42fececd6fd7d4a59337709a1d/superset-frontend/plugins/plugin-chart-echarts/src/Timeseries/EchartsTimeseries.tsx#L59
In 2.0.1 echartRef will be equal to ChartInstance object, but in 2.1.0 you will get undefined
@villebro I see some of your activities in this module. Do you have any ideas how to fix this bug? Could you share your thoughts, please?
As you can see, there are plenty of "DoubleClick feature" users :)

The current era ECharts (line, area, or otherwise) don't have a double-click feature. That sounds like what existed on the "legacy" (deprecated) line charts based on NVD3. Those still exist on 2.1.0, but will be migrated in 3.0.
What is NOT release in 2.1.0, but is available on master and will be available in 3.0 as well, are the ECharts equivalent, the All and Inverse buttons you see here.

ECharts does not and will not support double click actions like this (they're not discoverable to new users, arguably), so we're supporting the ECharts-native solution instead.
Hope this explains the situation... I'll close this for now, but if I'm misinterpreting the issue, let me know and we can re-open.

@rusackas thank you for reply! We are excited to try this  newfeature with 'All' and 'Invert' buttons!
But I still don't get it...
The double click feature is described in EchartsTimeseries module (the link in my previous comment), which one is NOT marked as deprecated and implemented in Echarts module. So, double click feature is in ECharts as well, isn't it?

@rusackas thank you for reply! We are excited to try this newfeature with 'All' and 'Invert' buttons!
But I still don't get it... The double click feature is described in EchartsTimeseries module (the link in my previous comment), which one is NOT marked as deprecated and implemented in Echarts module. So, double click feature is in ECharts as well, isn't it?
UPD: Here is the correct link to the function:
https://github.com/apache/superset/blob/357745f418d3eb42fececd6fd7d4a59337709a1d/superset-frontend/plugins/plugin-chart-echarts/src/Timeseries/EchartsTimeseries.tsx#L72

Yep, I see that in the code, and it looks like it ought to work, but I don't see it actually doing anything. That probably ought to be debugged or removed, one way or the other.

@rusackas yep, it ought to work and it was OK in 2.0.1, but not in 2.1.0:
I've tryed to debug this feature, but then I got stuck. You can debug this in the next steps:

Open any time-series Echart (for example, open 'Time-series Bar Chart v2') with at least 2 dimensions,
Set a breakpoint on this line:
https://github.com/apache/superset/blob/357745f418d3eb42fececd6fd7d4a59337709a1d/superset-frontend/plugins/plugin-chart-echarts/src/Timeseries/EchartsTimeseries.tsx#L75
(on the user side, the path is: webpack://superset/plugins/plugin-chart-echarts/src/Timeseries/EchartsTimeseries.tsx )
Double click on any bar (or on the name of dimention in annotation layer)
Ok, now you are paused on a breakpoint
Check out the echartInstance variable (which one is defined in the line above our debugging point).  In 2.1.0 it is undefined. I guess this is the problem, the reference handler is broken somewhere, but I don't know where and how to fix it.

This is how it was looking like in 2.0.1:

In 2.1.0 we have undefined. This is because the echartRef is null, which one is defined a little above.
If you have any ideas about this bug, please share :)
I guess we can re-open this issue, because it's not deprecated and it would be very helpful for us to use it until 3.0 release

Just for the record: this is where the feature is described and implemented previously:
https://github.com/apache/superset/issues/16354

@rusackas Can we re-open the issue, please?

This was fixed in https://github.com/apache/superset/pull/24477 and will be available in 3.0

@PrinceGallywix you can try to add ref={echartRef} to fix issue.
https://github.com/apache/superset/blob/357745f418d3eb42fececd6fd7d4a59337709a1d/superset-frontend/plugins/plugin-chart-echarts/src/Timeseries/EchartsTimeseries.tsx#L294
<Echart
  ref={echartRef}
  refs={refs}
  height={height - extraControlHeight}
  width={width}
  echartOptions={echartOptions}
  eventHandlers={eventHandlers}
  zrEventHandlers={zrEventHandlers}
  selectedValues={selectedValues}
/>


How can I disable a submit button until the form is in a valid state?

How can I disable a submit button until the form is in a valid state?

Short answer
There is no way to do that. Moreover, I would recommend you not to do so at the first place. See more detailed answer below.
Long answer
I see a problem with your requirement UX-wise.
In order to get the form's validity state you need to submit the form. Having "invalid" form with no errors displayed under the fields is a horrible thing to have. Having all fields marked in red when you render the form initially is equally devastating.
React Advanced Form takes a smart approach on this, and any field in a form is neither valid, nor invalid at initial render. This has a long backstory and has proven itself a sensible approach for any use case.
Sorry, at the moment there is no way to do that. This requirement is much more ambiguous conceptually, rather than technically. I don't plan to support this unless it's well thought through. If you have a suggestion of how to achieve your requirement while preserving a good UX, please post it here and we can come up with something.
Thanks.

I see what your saying and agree that all the fields in a form showing as invalid initially is a bad idea.
I was thinking that there could be an isValid property on the form that could be checked without triggering the UI to display everything as invalid.

If you perform form.submit() this will validate all fields in the form and mark them correspondingly.
This is not the recommended, however, as it is much more evident if you click on submit button, triggering the submit, rather than calling the method directly. But in some cases you may want to do that, I understand.
this.form.submit()

<Form ref={form => this.form = form}>
  {/* ... */}
</Form>

I think you misunderstood,  I don't want to initially submit() or call validate() or do anything that would make the UI light up like Christmas before the user has taken any action.   I was just looking for a property on the Form like "isValid" that I could use to toggle the disabled state of a button.  I'm not sure of the inner workings of the Form component to know if what I'm asking for is even possible.  If not then no big deal.
Thanks for your thorough answers they are very helpful.

@T-Roth Sorry, this is not possible now. As I explained, making this happen may have a somewhat ambiguous behavior. Internally, we solve this be having three values of what is a boolean flag for field's validity:

true - field is valid
false - field is invalid
null - explicitly, field is neither

But this is not suitable for API, since most of people will rely on !form.state.isValid, which will produce falsy result in case of explicit null (initial render).
I will keep this requirement in mind, but can't offer any solution at the moment.


Dynamics: Connecting CHARMM-GUI Forcefield to OpenMM Setup

Figure out how to accept the force field fields from the charmm-gui
Charmm-gui files for opsin 3ug9 are here https://drive.google.com/drive/folders/1Vx2iVaYiJ5TXwPIC27XoHBRujOd97s5U?usp=drive_link

We can add these kinds of file types to the force fields section in OpenMM (source):

.rtf, .top – Residue topology file
.par, .prm – Parameter file
.str – Stream file
.inp – Only if “par” is in the file name, it is a parameter file

We should probably use everything in the toppar folder except for the .crd file - "tip216.crd" (source. I don't think we should include "step5_assembly.str" and "step5_input_minimization.str" since they include information about the box rather than the force field itself. There is also a file called toppar.str in the main folder that we shouldn't include. It doesn't have the correct format for a .str file (it has a line containing "read" but never has a line containing "end" for the read to stop.)

I was able to run a simulation with the files above on the OpenMM GUI, but I changed some of the parameter of the simulation. I set "Non-Bonded Method" to "Cutoff, non-periodic" and "Statistical Ensemble" to "Constant Volume, temperature".


After build Node can't find @routes

I'm getting this error. It is because Typescript knows about this route, but Node doesn't know. This package is maybe the solution https://github.com/ilearnio/module-alias
Error: Cannot find module '@routes/LiftrRoutingModule'
grip_1  | Require stack:
grip_1  | - /home/node/dist/server.js
grip_1  |     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:980:15)
grip_1  |     at Function.Module._load (internal/modules/cjs/loader.js:862:27)
grip_1  |     at Module.require (internal/modules/cjs/loader.js:1040:19)
grip_1  |     at require (internal/modules/cjs/helpers.js:72:18)
grip_1  |     at Object.<anonymous> (/home/node/dist/server.js:17:30)
grip_1  |     at Module._compile (internal/modules/cjs/loader.js:1151:30)
grip_1  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
grip_1  |     at Module.load (internal/modules/cjs/loader.js:1000:32)
grip_1  |     at Function.Module._load (internal/modules/cjs/loader.js:899:14)
grip_1  |     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12) {
grip_1  |   code: 'MODULE_NOT_FOUND',
grip_1  |   requireStack: [ '/home/node/dist/server.js' ]
grip_1  | }
grip_1  | internal/modules/cjs/loader.js:983
grip_1  |   throw err;

the package tsconfig-paths resolves all the routes at run-time. It is included in the Liftr boilerplate. You can run node -r tsconfig-paths/register server.js within the dist folder and it should work.


The first window displayed center, second and subsequent displayed ca…

Change Initial position of uiWindow on macOS.

The First Window is displayed at center.
Second and subsequent are displayed cascaded.

Because (single)App and DocumentApp templates of SwiftUI do like this.

Because (single)App and DocumentApp templates of SwiftUI do like this.

Hi @junogura, yes that's a much better default. Looks good! Will need more testing with multiple window apps.

Replaces #100 ?


With multiple guides on a page, how do you close all but selected?

I've setup multiple guides on a page, but when I click each one's Page Guide tab it opens it - without closing the others.
What do I need to do to close the open one when I click on a new one?
Thanks

Hi @qwertydude, apologies for the late response. Version 1.3.2 (which was released yesterday) contains a fix for this. Opening a new pageguide now automatically closes all other open pageguides. Thanks for reporting and please let us know if you have further issues.

Excellent! Thanks!

This isnt working.
I have 2 Tours. Now one is open and i click on the other The message Box at the bottom is closed


x/net/context/ctxhttp: race condition preventing response from being closed

The ctxhttp.Do method contains a race condition when the context is cancelled before the client.Do performed in a go routine returns. The http.Response is discarded, leaving its Body opened and thus leading to sockets left in CLOSE_WAIT state.
To reproduce the issue, run this on Linux (can't reproduce on osx, I'm not sure why):
package main

import (
	"fmt"

	"golang.org/x/net/context"
	"golang.org/x/net/context/ctxhttp"
)

func main() {
	ctx, cancel := context.WithCancel(context.Background())
	cancel()
	resp, err := ctxhttp.Get(ctx, nil, "http://httpbin.org/get")
	fmt.Printf("%v, %v\n", resp, err)
	<-make(chan struct{})
}

The output is:
<nil>, context canceled

As the res is nil, I have no way for the caller to close the resp.Body.
Then look at netstat -lan | grep CLOSE_WAIT, you will see a new socket lying down forever.

Which version of Go? ctxhttp operated differently depending on the Go version.

Never mind, I see the problem.

I seem to recall seeing some workaround code for <=1.4. @jacobsa ?

@broady, @okdave, I'm sending a fix. Polishing a test now.

Dupe of #13293.

I'm not sure it is.

Sent https://go-review.googlesource.com/18802


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/caching d2f17bb...72ad795:
  > 72ad795 upgrade to latest dependencies (# 576)
bumping knative.dev/eventing 820db20...7fc053b:
  > 7fc053b upgrade to latest dependencies (# 5931)
bumping knative.dev/pkg 608fc87...438776b:
  > 438776b Drop unused test/cmd package (# 2366)
  > 754f332 Drop indirect dependencies from go.mod (# 2359)
  > 7f59158 Add ConfigMap parsing for int16 (# 2365)
bumping knative.dev/serving 215d013...a81da90:
  > a81da90 upgrade to latest dependencies (# 12363)
  > b150683 Bump golangci-lint timeout to prevent errors in actions (# 12362)
  > a7a9420 Don't run tests in parallel in kind (# 12361)
  > adc6d24 Update net-kourier nightly (# 12360)
  > 34c4c27 Update net-contour nightly (# 12359)
  > 9521ecb Update net-istio nightly (# 12358)

/lgtm
/approve


Incorrect data type for BreakoutAnalogOutput

The analog outputs on the breakout board requires unsigned 16-bit integer data that is interpreted by the hardware as offset binary:
https://open-ephys.github.io/onix-docs/Hardware Guide/Datasheets/fmc-analog-io.html#host-to-device-data-frames
However, signed data is used throughout the output node resulting in incorrect values being sent to the hardware:
https://github.com/open-ephys/onix-bonsai-onix1/blob/7ac700fb8a696d4d9f8d97c9d1b85765b9951ca6/OpenEphys.Onix1/BreakoutAnalogOutput.cs#L100
This issue applies to both Volts and S16 output options because they are both ultimately transformed to S16 before being sent.

Fixed in #213


Manage Backup

The manage backup screen should not have a grey cover.
The actions on the screen should be accessible.

-The grey cover of the Manage Backup screen( while loading ) is still visible.
-Tested on staging app version 1.4.0(184)

I haven't been able to reproduce this locally. Is there a recording or screenshot of this happening?

@cakesoft-swati are still able to see the grey screen? I am not.

Screen_Recording_20201221-105216.zip
This is the recordig frm Hexa live app version 1.4.0(188)

-Uable to reproduce this on live app v1.5.1(261)


Upgrade currency-formatter (less dependecies) + nbsp between amount a…

Thanks for the PR! It looks good, but the commit message mentions a non breakable space that I can't see. Any chance you forgot including it?

@bnjbvr The nbsp is directly included in the new version of the library. in the previous version, the space between amount and symbol was a simple space. It is now corrected.

Awesome! Cheers.


how to improve the memory of a windows 11 vm

Hello I just install a windows 11 vm on UTM but I want more memory so how is it possible to improve it or adding an hard disk or an usb on the vm please.
Configuration

UTM Version:
OS Version: 12.2.1
Intel or Apple Silicon? Apple

Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

After you right-click on the VM and choose edit, you go to system and what does your memory slider show? How much memory do you want to use?
Without knowing your version of UTM, I cannot help you with adding a drive.

hi thanks for reply. I actually use the last version of utm

but I can change the value of the memory and when i add a hard disk after 10 he is disconnected so I can't upload anything's on it because it is always disconnected during the upload and after a few seconds the vm crash

I add my disk whit this and I already check the USB sharing option

sorry for my English I don't speak very well

Oh, I'm sorry, I know nothing about USB sharing. I guess you meant memory as in storage. I thought you were asking for help with increasing RAM AND adding storage.

no problème if you can explain me how to increase the ram of the vm it can be cool please

Right click on the VM name
Choose edit
In the window that opens, choose system on the left
Move the slider to the right to increase RAM for the VM (or type in the amount desired in MB)
Once you click save it should change the available RAM in your VM the next time you start it.
NOTE: if any of the VMs are 32 bit instead of 64 bit, it will not see RAM above about 4GB no matter what you set the slider to.

ok thank and how I can adding storage because I only have 64gb and I want like 100gb

In the same settings window, instead of clicking system click the "new drive" button at the bottom. Then just type in the size you want and click create. You will need to format it in the VM, but it should show up as another hardware drive.

ok i see but how I format it in the vm because it did'n appear

in the vm

can you show me me with some picture maybe

I'm afraid I don't use windows much anymore. You would be better off using a search engine for "how to format new drive in windows 10"

ok thanks you very much for your time an advises


change autoprefixer-core to autoprefixer

You changed it already in the package.json but not yet here:
https://github.com/mxstbr/react-boilerplate/blob/master/makewebpackconfig.js#L90

Ah I missed that, thanks a lot!


AWS + Okta Saml

Platform or tool
AWS, Okta, AzureAD
Desired or expected behavior
Some organizations have switched to a purely federated access control for AWS. The access keys and sts tokens are auto-generated each session. It would be great if the AWS plugin can also include the ability to use SSO login.
If this is extremely out of scope, let me know. I might even try making this plugin addon
Current behavior
Currently, I am using saml2aws that would log into aws using okta as the sso backend. My organization hasnt migrated over to a single cross-account access (using source_profile in the ~/.aws/config).
saml2aws login -a [account] --force --skip-prompt --mfa=TOTP --password=$(op item get 'okta' --fields password) --mfa-token=$(op item get 'okta' --otp)

Relevant log output
No response
op CLI version
2.9.1

This definitely sounds like something that 1Password Shell Plugins should solve!
Current focus for right now though is on credentials that authenticate to their respective CLIs (e.g. Okta credentials to authenticate to the Okta CLI), but the plugin ecosystem is built with use cases like the one you're describing in mind, where plugins can authenticate with other platform's credentials as well. So it's very likely that we'll enable these types of use cases in the near future, so stay tuned!


Pull image failed

When playing with latest cri-o, image pull is always failed with errors:
[root@centos ~]# ocic image pull nginx
FATA[0000] pulling image failed: rpc error: code = 2 desc = Invalid image name "nginx", expected colon-separated transport:reference
[root@ centos ~]# ocic image pull nginx:latest
FATA[0000] pulling image failed: rpc error: code = 2 desc = Invalid image name "nginx:latest", unknown transport "nginx"

@runcom Is this a known issue?

Omit it, its my wrong usage of pull command. should pull it with prefix docker://.


Synthesis failed for Composer

Hello! Autosynth couldn't regenerate Composer. :broken_heart:
Here's the output from running synth.py:
2020-05-09 05:08:48 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-09 05:08:48,819 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-composer'
2020-05-09 05:08:50 [INFO] Running synthtool
2020-05-09 05:08:50,836 autosynth > Running synthtool
2020-05-09 05:08:50 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-09 05:08:50,836 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-09 05:08:51,047 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-composer
nothing to commit, working tree clean
2020-05-09 05:08:51,312 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-09 05:08:52,154 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Composer
2020-05-09 05:08:57,024 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/composer/synth.metadata'
2020-05-09 05:08:57 [ERROR] Synthesis failed
2020-05-09 05:08:57,055 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--', 'Composer']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Composer. :sob:
Here's the output from running synth.py:
2020-05-10 05:08:47 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-10 05:08:47,756 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-composer'
2020-05-10 05:08:49 [INFO] Running synthtool
2020-05-10 05:08:49,772 autosynth > Running synthtool
2020-05-10 05:08:49 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-10 05:08:49,772 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-10 05:08:49,993 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-composer
nothing to commit, working tree clean
2020-05-10 05:08:50,069 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-10 05:08:50,515 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Composer
2020-05-10 05:08:54,361 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/composer/synth.metadata'
2020-05-10 05:08:54 [ERROR] Synthesis failed
2020-05-10 05:08:54,386 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--', 'Composer']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Composer. :sob:
Here's the output from running synth.py:
2020-05-11 05:07:45 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-11 05:07:45,494 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-composer'
2020-05-11 05:07:47 [INFO] Running synthtool
2020-05-11 05:07:47,188 autosynth > Running synthtool
2020-05-11 05:07:47 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-11 05:07:47,189 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-11 05:07:47,372 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-composer
nothing to commit, working tree clean
2020-05-11 05:07:47,692 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-11 05:07:48,142 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Composer
2020-05-11 05:07:51,671 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/composer/synth.metadata'
2020-05-11 05:07:51 [ERROR] Synthesis failed
2020-05-11 05:07:51,695 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--', 'Composer']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Composer. :sob:
Here's the output from running synth.py:
2020-05-11 15:09:27 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-11 15:09:27,923 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-composer'
2020-05-11 15:09:29 [INFO] Running synthtool
2020-05-11 15:09:29,395 autosynth > Running synthtool
2020-05-11 15:09:29 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-11 15:09:29,395 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-11 15:09:29,604 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-composer
nothing to commit, working tree clean
2020-05-11 15:09:29,726 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-11 15:09:30,268 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Composer
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.0
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
A new Hex version is available (0.20.1 < 0.20.5), please update with `mix local.hex`
All dependencies are up to date
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.

22:09:32.941 [info]  FETCHING: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

22:09:33.301 [info]  FOUND: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200421, new=20200421, generating=true
Creating leading directories
Writing Empty to clients/composer/lib/google_api/composer/v1/model/empty.ex.
Writing Environment to clients/composer/lib/google_api/composer/v1/model/environment.ex.
Writing EnvironmentConfig to clients/composer/lib/google_api/composer/v1/model/environment_config.ex.
Writing IPAllocationPolicy to clients/composer/lib/google_api/composer/v1/model/ip_allocation_policy.ex.
Writing ImageVersion to clients/composer/lib/google_api/composer/v1/model/image_version.ex.
Writing ListEnvironmentsResponse to clients/composer/lib/google_api/composer/v1/model/list_environments_response.ex.
Writing ListImageVersionsResponse to clients/composer/lib/google_api/composer/v1/model/list_image_versions_response.ex.
Writing ListOperationsResponse to clients/composer/lib/google_api/composer/v1/model/list_operations_response.ex.
Writing NodeConfig to clients/composer/lib/google_api/composer/v1/model/node_config.ex.
Writing Operation to clients/composer/lib/google_api/composer/v1/model/operation.ex.
Writing OperationMetadata to clients/composer/lib/google_api/composer/v1/model/operation_metadata.ex.
Writing PrivateClusterConfig to clients/composer/lib/google_api/composer/v1/model/private_cluster_config.ex.
Writing PrivateEnvironmentConfig to clients/composer/lib/google_api/composer/v1/model/private_environment_config.ex.
Writing SoftwareConfig to clients/composer/lib/google_api/composer/v1/model/software_config.ex.
Writing Status to clients/composer/lib/google_api/composer/v1/model/status.ex.
Writing Projects to clients/composer/lib/google_api/composer/v1/api/projects.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

22:09:33.415 [info]  FETCHING: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1beta1

22:09:33.463 [info]  FOUND: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1beta1
Revision check: old=20200421, new=20200421, generating=true
Creating leading directories
Writing AllowedIpRange to clients/composer/lib/google_api/composer/v1beta1/model/allowed_ip_range.ex.
Writing Empty to clients/composer/lib/google_api/composer/v1beta1/model/empty.ex.
Writing Environment to clients/composer/lib/google_api/composer/v1beta1/model/environment.ex.
Writing EnvironmentConfig to clients/composer/lib/google_api/composer/v1beta1/model/environment_config.ex.
Writing IPAllocationPolicy to clients/composer/lib/google_api/composer/v1beta1/model/ip_allocation_policy.ex.
Writing ImageVersion to clients/composer/lib/google_api/composer/v1beta1/model/image_version.ex.
Writing ListEnvironmentsResponse to clients/composer/lib/google_api/composer/v1beta1/model/list_environments_response.ex.
Writing ListImageVersionsResponse to clients/composer/lib/google_api/composer/v1beta1/model/list_image_versions_response.ex.
Writing ListOperationsResponse to clients/composer/lib/google_api/composer/v1beta1/model/list_operations_response.ex.
Writing NodeConfig to clients/composer/lib/google_api/composer/v1beta1/model/node_config.ex.
Writing Operation to clients/composer/lib/google_api/composer/v1beta1/model/operation.ex.
Writing OperationMetadata to clients/composer/lib/google_api/composer/v1beta1/model/operation_metadata.ex.
Writing PrivateClusterConfig to clients/composer/lib/google_api/composer/v1beta1/model/private_cluster_config.ex.
Writing PrivateEnvironmentConfig to clients/composer/lib/google_api/composer/v1beta1/model/private_environment_config.ex.
Writing SoftwareConfig to clients/composer/lib/google_api/composer/v1beta1/model/software_config.ex.
Writing Status to clients/composer/lib/google_api/composer/v1beta1/model/status.ex.
Writing WebServerNetworkAccessControl to clients/composer/lib/google_api/composer/v1beta1/model/web_server_network_access_control.ex.
Writing Projects to clients/composer/lib/google_api/composer/v1beta1/api/projects.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs
fixing file permissions
2020-05-11 15:09:34,364 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/composer/synth.metadata'
2020-05-11 15:09:34 [ERROR] Synthesis failed
2020-05-11 15:09:34,395 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--', 'Composer']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Composer. :sob:
Here's the output from running synth.py:
2020-05-12 05:09:09 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-12 05:09:09,158 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-composer'
2020-05-12 05:09:10 [INFO] Running synthtool
2020-05-12 05:09:10,829 autosynth > Running synthtool
2020-05-12 05:09:10 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-12 05:09:10,830 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--']
2020-05-12 05:09:11,046 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-composer
nothing to commit, working tree clean
2020-05-12 05:09:11,291 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-12 05:09:11,742 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Composer
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.0
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
A new Hex version is available (0.20.1 < 0.20.5), please update with `mix local.hex`
All dependencies are up to date
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.

12:09:14.204 [info]  FETCHING: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:09:14.573 [info]  FOUND: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200421, new=20200421, generating=true
Creating leading directories
Writing Empty to clients/composer/lib/google_api/composer/v1/model/empty.ex.
Writing Environment to clients/composer/lib/google_api/composer/v1/model/environment.ex.
Writing EnvironmentConfig to clients/composer/lib/google_api/composer/v1/model/environment_config.ex.
Writing IPAllocationPolicy to clients/composer/lib/google_api/composer/v1/model/ip_allocation_policy.ex.
Writing ImageVersion to clients/composer/lib/google_api/composer/v1/model/image_version.ex.
Writing ListEnvironmentsResponse to clients/composer/lib/google_api/composer/v1/model/list_environments_response.ex.
Writing ListImageVersionsResponse to clients/composer/lib/google_api/composer/v1/model/list_image_versions_response.ex.
Writing ListOperationsResponse to clients/composer/lib/google_api/composer/v1/model/list_operations_response.ex.
Writing NodeConfig to clients/composer/lib/google_api/composer/v1/model/node_config.ex.
Writing Operation to clients/composer/lib/google_api/composer/v1/model/operation.ex.
Writing OperationMetadata to clients/composer/lib/google_api/composer/v1/model/operation_metadata.ex.
Writing PrivateClusterConfig to clients/composer/lib/google_api/composer/v1/model/private_cluster_config.ex.
Writing PrivateEnvironmentConfig to clients/composer/lib/google_api/composer/v1/model/private_environment_config.ex.
Writing SoftwareConfig to clients/composer/lib/google_api/composer/v1/model/software_config.ex.
Writing Status to clients/composer/lib/google_api/composer/v1/model/status.ex.
Writing Projects to clients/composer/lib/google_api/composer/v1/api/projects.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:09:14.694 [info]  FETCHING: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1beta1

12:09:14.740 [info]  FOUND: https://composer.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1beta1
Revision check: old=20200421, new=20200421, generating=true
Creating leading directories
Writing AllowedIpRange to clients/composer/lib/google_api/composer/v1beta1/model/allowed_ip_range.ex.
Writing Empty to clients/composer/lib/google_api/composer/v1beta1/model/empty.ex.
Writing Environment to clients/composer/lib/google_api/composer/v1beta1/model/environment.ex.
Writing EnvironmentConfig to clients/composer/lib/google_api/composer/v1beta1/model/environment_config.ex.
Writing IPAllocationPolicy to clients/composer/lib/google_api/composer/v1beta1/model/ip_allocation_policy.ex.
Writing ImageVersion to clients/composer/lib/google_api/composer/v1beta1/model/image_version.ex.
Writing ListEnvironmentsResponse to clients/composer/lib/google_api/composer/v1beta1/model/list_environments_response.ex.
Writing ListImageVersionsResponse to clients/composer/lib/google_api/composer/v1beta1/model/list_image_versions_response.ex.
Writing ListOperationsResponse to clients/composer/lib/google_api/composer/v1beta1/model/list_operations_response.ex.
Writing NodeConfig to clients/composer/lib/google_api/composer/v1beta1/model/node_config.ex.
Writing Operation to clients/composer/lib/google_api/composer/v1beta1/model/operation.ex.
Writing OperationMetadata to clients/composer/lib/google_api/composer/v1beta1/model/operation_metadata.ex.
Writing PrivateClusterConfig to clients/composer/lib/google_api/composer/v1beta1/model/private_cluster_config.ex.
Writing PrivateEnvironmentConfig to clients/composer/lib/google_api/composer/v1beta1/model/private_environment_config.ex.
Writing SoftwareConfig to clients/composer/lib/google_api/composer/v1beta1/model/software_config.ex.
Writing Status to clients/composer/lib/google_api/composer/v1beta1/model/status.ex.
Writing WebServerNetworkAccessControl to clients/composer/lib/google_api/composer/v1beta1/model/web_server_network_access_control.ex.
Writing Projects to clients/composer/lib/google_api/composer/v1beta1/api/projects.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs
fixing file permissions
2020-05-12 05:09:15,652 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/composer/synth.metadata'
2020-05-12 05:09:15 [ERROR] Synthesis failed
2020-05-12 05:09:15,682 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/composer/synth.metadata', 'synth.py', '--', 'Composer']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


newsflash: 3.1.1 -> 3.1.3

Description of changes
https://gitlab.com/news-flash/news_flash_gtk/-/releases/v.3.1.3
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

newsflash


kubecost Prometheus high memory usage

Hi! We have kubecost deployed with helm is our EKS cluster of around 50 nodes (c5.2xlarge). I'm giving 11Gi memory to prometheus-kubecost, 1vcpu, storing only 2h of data and still it's being killed by OOM. Any suggestion / tweak we can do?

Hi @jeanholidu, there are many different config changes available to reduce/manage Prometheus memory usage. Are you using your own Prometheus with the open source cost-model or something else? What version of Prometheus are you using?

We are using the one provided in the helm chart, in the opensource version of kubecost, with the following:
`prometheus:
nodeExporter:
enabled: false
serviceAccounts:
nodeExporter:
create: false
server:
retention: 2h
resources:
  requests:
    cpu: "1000m"
    memory: "11000Mi"
  limits:
    cpu: "1000m"
    memory: "11500Mi"`

Thanks! Would you be able to share a bug report with<EMAIL_ADDRESS>That should give us full context.

I will, thanks for the prompt help.


Setting Passive Touch Gestures in index.html does not work

Description
adding the following line to index.html before loading <my-app> does not set Polymer.passiveTouchGestures = true. Violation messages appear in console and Polymer.passiveTouchGestures === false;
Polymer.setPassiveTouchGestures(true);

Live Demo

http://jsbin.com/mehasat/edit?html,console,output
Steps to Reproduce

Generate PSK app
Add script tag in index.html with Polymer.setPassiveTouchGestures(true) to document.head, after or before webcomponents-loader.js
console.log(Polymer.passiveTouchGestures)

Expected Results
Polymer.passiveTouchGestures should be true, no scrolling violation messages should appear in chrome console.
Actual Results
Polymer.passiveTouchGestures is false, Scrolling violation messages appear in chrome console.
Browsers Affected

[x] Chrome

Versions

Polymer: v2.1.0
webcomponents: v1.0.2

@bennypowers You're trying to call a Polymer method before actually importing the library, it works fine if you just move the script down below the Polymer import.
http://jsbin.com/yubibedefu/1/edit?html,console,output

facepalm
Ok yeah that works, but i still get several passive scrolling violation messages.
As well, setting Polymer.passiveTouchGestures = true in head doesn't work, but I assume that's intentional

@azakus could you take a look at this report?


revert, emit and potentially others should be turned into library functions

This is just a quick brain dump and not actionable but I think once we are further along with our plans for a standard library then revert and emit should turn into library functions.
Motivation
The main motivation would be to not pollute the global namespace with special keywords or built-in functions too much.
Details
E.g. instead of:
type BookMsg = bytes[100]

contract GuestBook:
    pub guest_book: map<address, BookMsg>

    event Signed:
        idx book_msg: BookMsg

    pub def sign(book_msg: BookMsg):
        self.guest_book[msg.sender] = book_msg

        emit Signed(book_msg=book_msg)

    pub def get_msg(addr: address) -> BookMsg:
        return self.guest_book[addr]

We could have:
from std.evm import emit

type BookMsg = bytes[100]

contract GuestBook:
    pub guest_book: map<address, BookMsg>

    event Signed:
        idx book_msg: BookMsg

    pub def sign(book_msg: BookMsg):
        self.guest_book[msg.sender] = book_msg

        emit(Signed(book_msg=book_msg))

    pub def get_msg(addr: address) -> BookMsg:
        return self.guest_book[addr]

I think this would be a good place to start on the standard library.
We may want to consider adding an unsafe feature to Fe so that these functions can actually be implemented. I imagine this is part of the reason why Rust introduced it in the first place, because they wanted to prioritized library-features while also providing safety through limitation.

We may want to consider adding an unsafe feature to Fe so that these functions can actually be implemented.

Can you elaborate on the need for unsafe here?
The simplest way I can think of to implement that would be to just map the import of e.g revert to a YUL function revert that we would generate which would roughly look like:
function revert() {
    revert(0, 0)
}

Can you elaborate on the need for unsafe here?

Yeah, so I was thinking that we would try to implement revert and other std lib features in actual Fe modules. And if we were to do this, we would need to provide a bit more flexibility in the language. The problem with this, though, is that providing more flexibility can be at odds with safety. In the case of revert, implementing it in Fe would require us to use some sort of Yul code block:
pub def revert():
  yul:
    revert(0, 0)

The issue with allowing users to define Yul code blocks is that they can easily break their program, for example:
pub def revert():
  yul:
    mstore(26, 42) # overwrite some value stored in memory

In Rust, you would first need to enter unsafe mode to do this (see inline assembly). So we could have something like this:
pub def revert():
  unsafe:
    yul:
      revert(0, 0)

I realize the syntax given here doesn't look great
Of course, you can still write Yul in this unsafe block that breaks your program, but you're at least required to acknowledge that the code you're writing is unsafe and more scrutiny should be applied. I like this approach because it makes it easy for someone to write code with basic safety guarantees, while also allowing people to break the rules on occasions where it's required.

While I generally still agree that long term we should move certain things into a planned std library I have changed my view regarding revert and emit and think they might be better off staying keywords. I've put down a few more words on revert here. I'm closing this issue for now.


How to catch replicate errors without crashing?

I'm trying to call replicate from a node.js environment. If I have a malformed model input, the replicate SDK throws an error that crashes my server. I'm unable to catch the error and handle it. Here's my code:
 try {
        console.log("try")
        const output = await replicate.run(model, { modelInput })
  } catch (error) {
        console.log("catch")
  }
 console.log('after')

Here's my logs with the error:
  try
(node:15518) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
/Users/pseagren/Documents/TITLES/dev/backend/wallflower/api/wallflower-backend/node_modules/replicate/index.js:159
      throw new Error(`API request failed: ${response.statusText}`);
            ^

Error: API request failed: Unprocessable Entity
    at Replicate.request (/Users/pseagren/Documents/TITLES/dev/backend/wallflower/api/wallflower-backend/node_modules/replicate/index.js:159:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v18.7.0

Oddly, sometimes (but infrequently) my catch block actually catches the error, but usually it doesn't and the server crashes. Am I missing something?

Hi, @pqseags. Thanks for writing in. I'm sorry you're having trouble with this.
Here are two suggestions:

The run method is a shorthand for creating a prediction and waiting for its result. It throws an error if the prediction fails. However, the longer form predictions.create method doesn't throw, and instead populates its error property. So one option would be to migrate to that method instead.
The issue could be that your try-catch block isn't correctly catching promise rejections. If the run method returns a promise that rejects, and that promise rejection isn't caught inside an async function, it could be causing your catch block not to execute.

If the code you shared is part of an async function, it should catch the error properly. But if it's not, then you'll need to declare the enclosing function as async or handle the promise with .catch():
replicate.run(model, { modelInput })
  .then(output => {
    console.log('after');
  })
  .catch(error => {
    console.log("catch");
  });

Thanks for the response @mattt. Your first suggestion worked well, and we wanted to migrate to use webhooks anyway so that's perfect.
Regarding the second suggestion however, the code is in an async function, and I ran into the same issue with .catch(). Perhaps the error is being thrown incorrectly in replicate's run method? From my understanding it should be Promise.reject() rather than throw new Error

@pqseags Thanks for the update. I'm glad to hear that you found a solution.
My understanding is that when an error is thrown inside an async function, it's automatically wrapped into a rejected Promise.

@pqseags Oh wait, I see why this is happening. The original code you posted seems to be calling replicate.run without an await. I think adding that should fix your issue.

Hmm I'm not familiar enough to say for sure. Definitely odd that I was seeing inconsistent behavior as well. Either way I'm happy with the predictions.create solution - thanks for the help!


Sm2sm3testing

add some test cases for sm2 package
fix sm3 bug
upgrade ginkgo to v2

todo： rollback go mod changes for proto related.

改动是因为ginko（ut）框架升级而fabric没升级这个框架的依赖。upstream那边我已经提交了相关issue。我们这边确实应该考虑回滚。
|
Sam Yuan
@.***
|
Signature is customized by Netease Mail Master
On 01/27/2022 11:36, Xiao Hui wrote:
@xiaohui249 commented on this pull request.
依赖目录vendor也提交了，造成很多依赖文件变更，这个目录是否有必要提交？
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>


Update dependencies version

Hi, @kztao.
Any plan to PR to upstream?
(In my case:
https://github.com/Lemon73-Computing/maui-linux/pull/2/files#diff-bc1521ce26d824c8a081953577e2feb3ed93cd898009d33fa5466f8878674c68R39-R44
But, I don't know whether this runs well or not...)

o, it's not ready for merge.


Added a resource to walkthrough average calculation on Ring

Resource Addition
Category
Tutorial
Description
A short walkthrough on how to calculate the average value from nodes on a Ring computation
Checklist

[ ✓] I have followed the contribution guidelines
[ ✓] The resource is freely accessible (or marked if paid)
[ ✓] I have added it to the appropriate category
[ ✓] The link is functional
[ ✓] The description is clear and concise

Wonderful contribution @flow254!
Before approving, can I kindly ask to keep the average calculation ring doc you've added on a separate repo and just add the link to it in the main README file please?
In this way we will keep the structure of this repo consistent :)
Thanks so much!


Videos are cool but show me the text

This tutorial appears to be all videos. I don't want to sit through multiple videos while I'm looking to get an overall sense or even a specific bit of info. I can't cut and paste from a video. So, I suggest that text be the primary form of tutorials and you can have videos if they might help.

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

ID: 79e0a0b9-d316-fea3-f92d-db9535ea3400
Version Independent ID: 215ec001-4569-072c-01fb-32edba90db40
Content: MongoDB, React, and Node.js tutorial for Azure
Content Source: articles/cosmos-db/mongodb/tutorial-develop-mongodb-react.md
Service: cosmos-db
Sub-service: cosmosdb-mongo
GitHub Login: @johnpapa
Microsoft Alias: jopapa

@jeffmcaffer Thank you for the feedback. Before the start of the videos there is a GitHub repo link provided where the entire code sample is available. We can download it and then refer to the videos side by side to understand the code.

Please let us know if this helps.

@jeffmcaffer Awaiting your response on this.

@jeffmcaffer Due to lack of response, we will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Move docs/setup-tutorial.md to the github wiki.

Also, revise it to ensure everything still works.

Setup tutorial needs:
- Start here page
- Security holes
- HTTPS
- Default admin account
- Information about legal requirements of the developers using this template
- Privacy policy & data collection notices

Move "Gmail Email Settings" into the tutorials.

Rewrote the tutorial, left stubs for various other things. Good enough to close this issue for now.


make featured speakers centered like sponsor heading

@aayusharora @mariobehling please check and merge

Current coverage is 42.58% (diff: 100%)

Merging #710 into development will not change coverage

@@           development       #710   diff @@
=============================================
  Files                6          6
  Lines              688        688
  Methods             71         71
  Messages             0          0
  Branches           112        112
=============================================
  Hits               293        293
  Misses             395        395
  Partials             0          0

Powered by Codecov. Last update 7a9d8cf...ec528c1