When you try to install a plugin you already have, exit code is 0

Is it normal?
Shouldn't it be something more appropriate (>=2) ?
This is causing me troubles when automating the installation but since it's new for me, I wasn't sure where the issue lied so I wasted several hours to find a workaround :D

Maybe I don't get your point, but if you already have a plugin then a return code of 0 means it was successful as it didn't have to do anything. Why would you expect it to be different?

This is causing me troubles when automating the installation but since it's new for me, I wasn't sure where the issue lied so I wasted several hours to find a workaround :D

Why do you need a workaround? Why can't you just move on to the next plugin? If it's already installed, then there isn't anything that needs to be done.

"Why would you expect it to be different?"
because it didn't install a plugin, it told me the plugin is already there, that's rather different to me but I don't know the convention on exit codes at all so I just asked ^^
At first I supposed that the error codes were meant to describe errors but also warnings

Think about what needs to happen after the command is done. You would expect the plugin to be there. If it is already installed then do nothing because after the command is done, it is in the state you expect it to be. IMO installing plugins should be idempotent. Like doing a PUT, I'd expect it to make the change and not complain if the change has already been made.

I don't know, are all exit code above 1 = a complaint/an error?

I looked at other package managers. pip and brew return 0 when the package is already installed. So I'd say it's safe to assume this is consistent behavior.

This concept of being able to install or do something repeatedly and have the same result as running it once is so prevalent in the computer software world that there's a term for it: idempotency. So, I'd say leaving the exit code as success is right call.


about liver dataset

Thanks for sharing your work in this field!
I have some questions about these words in the paper
"Raw scans are resampled  into 128 × 128 × 128 voxels after cropping unnecessary  area around the target object. For liver CT scans, a simple  threshold-based algorithm is applied to find a rough liver  bounding box for cropping."
1.What should I do to crop and resample？
Sorry I am not familar with image processing, what kind of tools should I use?
2.During training，how do I select two input image （fixed image and moving image）from dataset （e.g LiTs 130 CT scans，512x512x75）？
3.If I were to use a liver dataset, what preprocessing steps would I need to perform？

If you use our provided datasets, there is nothing else to do --- they are already preprocessed. If you want to make your own dataset, a complete preprocessing pipeline for liver can be found in demo.py, which takes as input two raw CT scans for a forward pass.

Thank you for your reply,i will check out demo.py.
I have another question.
How do I choose an image pair from mydataset for training，just random？

You can prepocess them into a .h5 file like our provided dataset, then the training script would choose random image pairs for training by default.

Thank you very much for your reply.


How does passwordless in Authenticator actually work?

There should be an explanation of how Authenticator's passwordless feature works on this page, or at least a link. Anyone reading this page won't come away knowing that Authenticator uses public key cryptography, similar to what WHFB or FIDO2 keys do. If you dig around looking for old Ignite presentations, the information is out there, but AFAIK it's nowhere in the actual docs.
https://channel9.msdn.com/Events/Ignite/Microsoft-Ignite-Orlando-2017/BRK2017

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

ID: ee6ac70d-5853-6a3a-0964-23b46910b4c4
Version Independent ID: a5beda87-9845-8807-6221-7fdc64079587
Content: Passwordless sign-in with the Microsoft Authenticator app - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-authentication-passwordless-phone.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@robmacf
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for the feedback, @robmacf
The intent of this article is to show how to enable passwordless sign-in. One of the linked docs from the article covers conceptual information around passwordless - https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-authentication-passwordless. There's more that could probably be included in that conceptual doc, but is that more what you'd expect to see?
#in-progress

Thanks, that article linked under "What is Passwordless?" is exactly what I was looking for. I didn't see the link until you pointed it out - I was looking for wording like "how it works" or" behind the scenes."
If I could make one small suggestion, better link text would be "Learn how passwordless authentication works"; this would also be more consistent with the wording of the other two links.

The doc link under 'Next steps' has now been updated to make it clearer. This update should publish in the next hour or so Thanks.


feat(app): Add Motivational Quote Easter Egg

Pre-Submission Checklist

[ ] Your pull request targets the staging branch of freeCodeCamp.
[ ] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[ ] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[ ] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #16382
Description

Added a feature where a motivational quote is randomly selected from a static list and displayed whenever the user closes all the panes on the page. Also added a quotes.js file with an array of quote objects and a function that returns a random quote object when called.
BREAKING CHANGE: None

Sorry, realized I forgot to start the branch name with the feature/ prefix. I'll close this and submit another PR with the a properly named branch.


Very high function call overhead

Steps to reproduce
function test {}
measure-command { foreach($i in 1..1000000) { test }}

Expected behavior
Function calls do not exhibit high overhead

Actual behavior
measure-command { foreach($i in 1..1000000) { test }}

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 23
Milliseconds      : 547
Ticks             : 235471577
TotalDays         : 0.000272536547453704
TotalHours        : 0.00654087713888889
TotalMinutes      : 0.392452628333333
TotalSeconds      : 23.5471577
TotalMilliseconds : 23547.1577

Function calls (even empty functions) exhibit very high overhead
Environment data

Name                           Value
----                           -----
PSVersion                      6.0.4
PSEdition                      Core
GitCommitId                    v6.0.4
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

This kind of overhead makes powershell unsuitable for code which requires hundreds of thousands or millions of simple function calls.
In-lining the function call shows the difference in overhead of function call vs inline in these scenarios:
measure-command { foreach($i in 1..1000000) { $i = 0; $i++ }}

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 1
Milliseconds      : 63
Ticks             : 10638564
TotalDays         : 1.23131527777778E-05
TotalHours        : 0.000295515666666667
TotalMinutes      : 0.01773094
TotalSeconds      : 1.0638564
TotalMilliseconds : 1063.8564

measure-command { foreach($i in 1..1000000) { test }}

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 24
Milliseconds      : 23
Ticks             : 240235646
TotalDays         : 0.000278050516203704
TotalHours        : 0.00667321238888889
TotalMinutes      : 0.400392743333333
TotalSeconds      : 24.0235646
TotalMilliseconds : 24023.5646

This is a scripting system (high latency), not a programming language that is compiled to native code (low latency).  I found better mileage if I can keep loops to small counts, by utilizing the cmdlets or operators to do all the work.  I had an instance where I needed to break a Base64String in to 80 character indented lines in to an XML document.  A typical programming loop construct took 20 seconds to break the blob in to approximately 40,000 lines.  A REGEX (-replace) pattern did it in under a second in a single command.

A similar test in python shows overhead of about 0.11s over 1 million calls so id argue that the overhead is significantly higher than comparable languages.
There are ways around it like inlining functions and using native C# calls

@msftrncs but PowerShell is JIT compiled, for loops which happen more than 16 times ( https://stackoverflow.com/a/34236617 )

Parameter set resolution is not part of that. It still happens at runtime.
We are looking into improving the performance of the parameter binder, but it's quite a complex piece of code.

I've stumbled on this Powershell performance bug two many times, and it's quite embarrassing. Calling a function within a large loop absolutely kills the performance of the script, and I'm forced to copy the contents of the function into the for loop to restore the performance.
Fixing embarrassing performance issues like this one (and the ProgressPreference on Invoke-WebRequest/RESTMethod) is necessary if you want to drive further adoption of Powershell

and the ProgressPreference on Invoke-WebRequest/RESTMethod

@eythort-mm It was fixed. If you still see in latest builds please open new issue with repo steps.

yeah it's probably fixed in the latest builds, but that was more of a side note, being an equally embarrassing performance issue


titleAlign doesn't work in any chart

It always display in center of the chart header

Cannot reproduce.
This works fine:
	slide.addChart(pptx.charts.PIE, dataChartPieLocs, {
		x: 9.8,
		y: 0.5,
		w: 3.2,
		h: 3.2,
		dataBorder: { pt: "1", color: "F1F1F1" },
		showLegend: true,
		legendPos: "t",
		legendFontSize: 14,
		showLeaderLines: true,
		showTitle: true,
		title: "Right Title & Large Legend",
		titleAlign: "right",
		titlePos: { x: 0, y: 0 },
	});

OK.I thought it means the title label position relative to chart.thanks

It sounds like you're looking for legendPos - where the legend is in reference to the chart itself.
Chart API


Include information about justInTimeInstall from this page: https://docs.microsoft.com/en-us/microsoftteams/platform/resources/messaging-extension-v3/create-extensions?tabs=typescript#request-to-install-your-conversational-bot

The documentation for JIT install is split up across 2 pages, one of which is "legacy v3". The info in this section
https://docs.microsoft.com/en-us/microsoftteams/platform/resources/messaging-extension-v3/create-extensions?tabs=typescript#request-to-install-your-conversational-bot
Needs to be copied to this page

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

ID: 8fb0c2d8-f880-c260-d0be-6b9467e47f8c
Version Independent ID: 7820ffc9-5260-c818-f5fb-672801a67d00
Content: Respond to the task module submit action - Teams
Content Source: msteams-platform/messaging-extensions/how-to/action-commands/respond-to-task-module-submit.md
Product: msteams
GitHub Login: @clearab
Microsoft Alias: anclear

Closing this issue as per confirmation received from @Wajeed-msft. This issue has been addressed through the PR #2664. The section has been added in Create a task module page.


Flutter web rendering anomaly

Some things look much better in mobile browsers.
At the same time, I noticed that sometimes the quality of icons in Flutter Web on a desktop browser can improve if some neighboring widgets are accidentally changed (for example, the size).
Desktop browser:

Mobile browser:

Hi @syfulin
Can you please provide your flutter doctor -v and a minimal complete reproducible code sample?
Thank you

@hamdikahloun, thanks for the answer.
I have reinstalled Flutter SDK and the "anomalous gray line" is gone 🤷🏻♂:

The icons could be prettier too, but no 😑.
I'll try to find out when changing which code the icons lose quality and write here
flutter doctor -v:

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Unable to install the ligature

Windows isn't able to recognize the "build" command which is supposed to create the OTF files. I am doing something wrong?

The "build" command is a batch file. It runs the node index.js command. Are you in the root directory of the project? What error are you getting?

I'm closing this issue. You can reopen if you're still having a problem. Thanks!


Per-type skip

As discussed in #2924 and "hinted" in #2555 and maybe others, a per-type skip would be nice. I don't have tens of use-case, in fact I have only one: the matrix. In our computer graphic application, we define a lot of matrices in several modules, thus making #[rustfmt::skip] uninteresting. What I (and probably many others) want is something like
// in lib.rs or mod.rs. Or top of a file?
#[rustfmt::skip(Matrix3, Matrix4)]

because I can't imagine a single case where I would want rustfmt to format my matrices. The only right way to format a 3x3 matrix is when it has 3 columns and 3 rows. All in one line or in one row is unreadable.
I don't know rustfmt code at all, nor what it could possibly do. Do you have access to the base type when parsing the files? I ask because I wonder if an alias type Affine = Matrix3<f64> would force the user too add all aliases in the skip, if such a feature existed.

It could be also another config option akin to ignore where the struct's name would be specified.
I don't think the type is available so the ignore wouldn't propagate to Affine in your example. @topecongiro is that the case ?

Since rustfmt acts on AST, which holds little or no type information, skipping based on type can only be done heuristically.

if an alias type Affine = Matrix3<f64> would force the user too add all aliases in the skip

This won't happen unless the user explicitly uses #[rustfmt::skip(Affine)]. Attributes inside external crates won't have effect.

In general I think columns of numerical data are an area where code formatters struggle. There is more semantic information when these are formatted correctly and it makes bugs and incorrect literals stand out, which is what good syntax should do. I can see the argument that having these special snowflake formattings messes up an otherwise orderly plan for formatting, but this is a case where the standard formatting really does make the code much harder to use. This might be a niche edge-case for Rust in general, but for people who want it, I'd argue it really matters.
Also it would be fantastic if Rust could actually generate clean matrix formatting for us :)

What about something like #[rustfmt::arrayNxM] where rustfmt will automatically arrange things matrix style, with configuration for horizontal alignment of the columns in .rustfmt.toml?  As a first pass this could be only for [T: {N*M}] but could be expanded for argument lists to functions and tuples/tuple structs

I think this is a more general issue. There are a lot of places where readability improves with column alignment,
Take this example:
let expanded = ConfigKeys {
    program_id: keys[0],
    group_id: keys[1],
    cache_id: keys[2],
    user_id: keys[3],
    user_meta: keys[4],
    user_ev: keys[5],
    user_queue: keys[6],
}

or
let expanded = ConfigKeys {
    program_id : keys[0],
    group_id   : keys[1],
    cache_id   : keys[2],
    user_id    : keys[3],
    user_meta  : keys[4],
    user_ev    : keys[5],
    user_queue : keys[6],
})

I'm not sure the decision of when to columnate is something that can be chosen automatically.
But perhaps a directive like #[rustfmt(align)] could exist to specify blocks that should be formatted this way.

Hey @nilgoyette, I don't know if it works in your use case but I've seen something like the following:
#[rustfmt::skip]
mod matrices {
    pub const ARR1: [ /* hand formatting */ ];
    pub const ARR2: [ /* hand formatting */ ];
}

use matrices::*;

It's a bit less elegant since you lose an indent and all items have to be contiguous, but at least you don't need to call out each individual array.


Add support for paths in tsconfig.json and jsconfig.json

Adds support for "paths" in both tsconfig.json or jsconfig.json.
Examples:
Single module alias
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "mytheme": ["components/mytheme.js"]
    }
  }
}

Wildcard alias
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@c/*": ["components/*"],
    }
  }
}

Fallback behavior
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@mytheme/*": ["themes/theme-a/*", "lib/theme-b/*"]
    }
  }
}

Temporarily behind an experimental feature flag:
// next.config.js
module.exports = {
  experimental: {
    jsconfigPaths: true, // enables it for both jsconfig.json and tsconfig.json
  }
}

Fixes #7779

Stats from current PR

Default Server Mode

General Overall increase ⚠

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

buildDuration
10.7s
10.5s
-186ms

nodeModulesSize
52.8 MB
52.8 MB
⚠ +14.6 kB

Client Bundles (main, webpack, commons)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.js gzip
6.24 kB
6.24 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..c6c1.js gzip
10.1 kB
10.1 kB
✓

framework.HASH.js gzip
39.1 kB
39.1 kB
✓

Overall change
56.2 kB
56.2 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.module.js gzip
4.78 kB
4.78 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.71 kB
6.71 kB
✓

framework.HA..dule.js gzip
39.1 kB
39.1 kB
✓

Overall change
51.4 kB
51.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

polyfills-HASH.js gzip
26.3 kB
26.3 kB
✓

Overall change
26.3 kB
26.3 kB
✓

Client Pages

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.js gzip
1.24 kB
1.24 kB
✓

_error.js gzip
3.15 kB
3.15 kB
✓

hooks.js gzip
664 B
664 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.03 kB
2.03 kB
✓

routerDirect.js gzip
279 B
279 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
7.86 kB
7.86 kB
✓

Client Pages Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.module.js gzip
594 B
594 B
✓

_error.module.js gzip
2.08 kB
2.08 kB
✓

hooks.module.js gzip
370 B
370 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js gzip
1.48 kB
1.48 kB
✓

routerDirect..dule.js gzip
271 B
271 B
✓

withRouter.m..dule.js gzip
270 B
270 B
✓

Overall change
5.28 kB
5.28 kB
✓

Client Build Manifests

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Rendered Page Sizes

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

index.html gzip
916 B
916 B
✓

link.html gzip
924 B
924 B
✓

withRouter.html gzip
913 B
913 B
✓

Overall change
2.75 kB
2.75 kB
✓

Serverless Mode (Decrease detected ✓)

General Overall increase ⚠

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

buildDuration
11.6s
11.3s
-324ms

nodeModulesSize
52.8 MB
52.8 MB
⚠ +14.6 kB

Client Bundles (main, webpack, commons)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.js gzip
6.24 kB
6.24 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..c6c1.js gzip
10.1 kB
10.1 kB
✓

framework.HASH.js gzip
39.1 kB
39.1 kB
✓

Overall change
56.2 kB
56.2 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.module.js gzip
4.78 kB
4.78 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.71 kB
6.71 kB
✓

framework.HA..dule.js gzip
39.1 kB
39.1 kB
✓

Overall change
51.4 kB
51.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

polyfills-HASH.js gzip
26.3 kB
26.3 kB
✓

Overall change
26.3 kB
26.3 kB
✓

Client Pages

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.js gzip
1.24 kB
1.24 kB
✓

_error.js gzip
3.15 kB
3.15 kB
✓

hooks.js gzip
664 B
664 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.03 kB
2.03 kB
✓

routerDirect.js gzip
279 B
279 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
7.86 kB
7.86 kB
✓

Client Pages Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.module.js gzip
594 B
594 B
✓

_error.module.js gzip
2.08 kB
2.08 kB
✓

hooks.module.js gzip
370 B
370 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js gzip
1.48 kB
1.48 kB
✓

routerDirect..dule.js gzip
271 B
271 B
✓

withRouter.m..dule.js gzip
270 B
270 B
✓

Overall change
5.28 kB
5.28 kB
✓

Client Build Manifests

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Serverless bundles Overall decrease ✓

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_error.js gzip
293 kB
293 kB
-111 B

404.html gzip
1.32 kB
1.32 kB
✓

hooks.html gzip
956 B
956 B
✓

index.js gzip
294 kB
294 kB
⚠ +7 B

link.js gzip
301 kB
301 kB
-34 B

routerDirect.js gzip
300 kB
300 kB
⚠ +149 B

withRouter.js gzip
300 kB
300 kB
-129 B

Overall change
1.49 MB
1.49 MB
-118 B

Stats from current PR

Default Server Mode

General Overall increase ⚠

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

buildDuration
9.5s
9.5s
⚠ +55ms

nodeModulesSize
52.8 MB
52.8 MB
⚠ +14.6 kB

Client Bundles (main, webpack, commons)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.js gzip
6.24 kB
6.24 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..c6c1.js gzip
10.1 kB
10.1 kB
✓

framework.HASH.js gzip
39.1 kB
39.1 kB
✓

Overall change
56.2 kB
56.2 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.module.js gzip
4.78 kB
4.78 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.71 kB
6.71 kB
✓

framework.HA..dule.js gzip
39.1 kB
39.1 kB
✓

Overall change
51.4 kB
51.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

polyfills-HASH.js gzip
26.3 kB
26.3 kB
✓

Overall change
26.3 kB
26.3 kB
✓

Client Pages

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.js gzip
1.24 kB
1.24 kB
✓

_error.js gzip
3.15 kB
3.15 kB
✓

hooks.js gzip
664 B
664 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.03 kB
2.03 kB
✓

routerDirect.js gzip
279 B
279 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
7.86 kB
7.86 kB
✓

Client Pages Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.module.js gzip
594 B
594 B
✓

_error.module.js gzip
2.08 kB
2.08 kB
✓

hooks.module.js gzip
370 B
370 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js gzip
1.48 kB
1.48 kB
✓

routerDirect..dule.js gzip
271 B
271 B
✓

withRouter.m..dule.js gzip
270 B
270 B
✓

Overall change
5.28 kB
5.28 kB
✓

Client Build Manifests

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Rendered Page Sizes

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

index.html gzip
916 B
916 B
✓

link.html gzip
924 B
924 B
✓

withRouter.html gzip
913 B
913 B
✓

Overall change
2.75 kB
2.75 kB
✓

Serverless Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

buildDuration
10.2s
10.5s
⚠ +249ms

nodeModulesSize
52.8 MB
52.8 MB
⚠ +14.6 kB

Client Bundles (main, webpack, commons)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.js gzip
6.24 kB
6.24 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..c6c1.js gzip
10.1 kB
10.1 kB
✓

framework.HASH.js gzip
39.1 kB
39.1 kB
✓

Overall change
56.2 kB
56.2 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

main-HASH.module.js gzip
4.78 kB
4.78 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.71 kB
6.71 kB
✓

framework.HA..dule.js gzip
39.1 kB
39.1 kB
✓

Overall change
51.4 kB
51.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

polyfills-HASH.js gzip
26.3 kB
26.3 kB
✓

Overall change
26.3 kB
26.3 kB
✓

Client Pages

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.js gzip
1.24 kB
1.24 kB
✓

_error.js gzip
3.15 kB
3.15 kB
✓

hooks.js gzip
664 B
664 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.03 kB
2.03 kB
✓

routerDirect.js gzip
279 B
279 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
7.86 kB
7.86 kB
✓

Client Pages Modern

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_app.module.js gzip
594 B
594 B
✓

_error.module.js gzip
2.08 kB
2.08 kB
✓

hooks.module.js gzip
370 B
370 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js gzip
1.48 kB
1.48 kB
✓

routerDirect..dule.js gzip
271 B
271 B
✓

withRouter.m..dule.js gzip
270 B
270 B
✓

Overall change
5.28 kB
5.28 kB
✓

Client Build Manifests

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Serverless bundles Overall increase ⚠

zeit/next.js canary
timneutkens/next.js add/jsconfig-paths
Change

_error.js gzip
293 kB
294 kB
⚠ +705 B

404.html gzip
1.32 kB
1.32 kB
✓

hooks.html gzip
956 B
956 B
✓

index.js gzip
293 kB
294 kB
⚠ +631 B

link.js gzip
301 kB
301 kB
-311 B

routerDirect.js gzip
300 kB
300 kB
-177 B

withRouter.js gzip
300 kB
300 kB
⚠ +114 B

Overall change
1.49 MB
1.49 MB
⚠ +962 B

@timneutkens Since paths is read from json files, the value is completely static. I'd be interested in being able to set these from next.config.js. That way they can also be populated from environment variables (so that they can be populated from e.g. ZEIT now buildEnv). Is that a use-case that could be considered for this PR as well?

That way they can also be populated from environment variables (so that they can be populated from e.g. ZEIT now buildEnv). Is that a use-case that could be considered for this PR as well?

That's not supported by most code editors while tsconfig and jsconfig are. What's the use case?

Allowing dynamic values also makes it significantly harder to do any type of caching in the future.

Wow, I was waiting for this feature! I like using ~/ alias for my src folder, and had to setup this in both next.config.js and tsconfig.json. Now one setting is enough. Thanks a lot!

That's not supported by most code editors while tsconfig and jsconfig are. What's the use case?

@timneutkens Use case is to create a localized next.js app, where each locale is an instance of the app on its own. locale data is made dynamic by configuring an alias to a locale folder. (This is just a POC, still trying to feel the water on where next.js is going to go feature-wise.)

Just a thought, but can this be (ab)used to enable "transpile node_modules"? as in
"paths": {
  "my-module/*": "node_modules/my-module/*"
}

I'm using tsconfig-paths-webpack-plugin for more then a year, and it just works.
Do you know what are differences between your implementation and this lib?

I'm using tsconfig-paths-webpack-plugin for more then a year, and it just works.
Do you know what are differences between your implementation and this lib?

Significantly more overhead as it uses another library that implements filesystem calls itself instead of relying on webpack.
Besides that it didn't seem to be based on the actual TypeScript source code, meaning there could be differences in how the output path is calculated.
It also maintained a lot of baggage, eg webpack 3 support and checks that are not needed as we know exactly how the plugin will execute in Next.js.

Is this supporting monorepo structures where paths are defined at repo root? i.e:
packages/
  nextApp/
     tsconfig.json
tsconfig.json

I added: jsconfigPaths: true to my config, installed 9.3.2-canary.3 and removed webpack alias I used to have, but am getting errors that can't resolve paths unless I add those webpack aliases back.

Didn't add resolving of extends currently

You probably considered this already but mentioning it to make sure. Another option is to build it on top of the typescript compiler API. It seems to provide a host.resolveModuleName.

@timneutkens I just upgraded my NextJS which includes this change and removed tsconfig-paths-webpack-plugin and tried building my code, but to no avail, webpack just errors out:
$ next build "src/app"
Creating an optimized production build

./pages/index.tsx
Module not found: Can't resolve '@Config/HomeProjectCardData' in 'E:\dev\website\src\app\pages'

> Build error occurred
Error: > Build failed because of webpack errors
    at build (E:\dev\website\node_modules\next\dist\build\index.js:13:900)

I've branched my code, could you have a look what's going wrong here? My app is based on the Firebase sample.
Branch (tsconfig specifically): https://github.com/favware/website/blob/pluginless-paths/src/app/tsconfig.json

You forgot to add the experimental flag in next.config.js

Ah I missed that yeah, thanks!

Hey @timneutkens it seems I can now use this without the experimental flag, do you confirm? If so, should we add documentation for it? Thanks!

Hey @timneutkens it seems I can now use this without the experimental flag, do you confirm? If so, should we add documentation for it? Thanks!

We don't document experimental flags as they are experimental and can be removed at any time in some cases (this one will land soon).

Hi everyone! My issue is that when I use a component first and then import it from Material UI, the component is imported from '<EMAIL_ADDRESS>Is there a way around it?

@4ortytwo can you provide a clear example? It's hard to follow what you're asking.

I have this in my tsconfig
 "baseUrl": ".",
    "paths": {
      "@r/*": ["./*"], // alias for root
      "@s/*": ["./src/*"] // alias for src
    }

And this in my next.config
experimental: {
    jsconfigPaths: true,
  },

Let's say I created a new tsx file and used Material-ui <Container></Container> in it without prior import. I see that it's not imported and use 'Add import statement' of WebStorm.
At the top, I see that it's imported from<EMAIL_ADDRESS>Anything imported from any other library also has a similarly looking path.
I wonder whether it could be related to the IDE. I'd like to be able to use aliases for my paths but I still want library imports to look concise. How can I achieve that?

@4ortytwo That's just how TypeScript resolves paths and in a way it is sort of related to your IDE but I doubt using something like VSCode is going to change it much. My own recommendation would be to not have a path alias for root dir and instead just keep files in a src dir (which you can then also set as the rootDir and baseDir in the tsconfig, which will somewhat improve TSServer since it doesn't have to traverse as many files).
Alternatively, paths are resolved bottom to top (with top taking higher priority I mean) so if you really need to keep the root path alias then add another alias, not sure if this exactly works, might need some tweaking. But I think it'll work:
{
    "paths": {
      "@material-ui/*": ["./node_modules/@material-ui/*"],
      "@r/*": ["./*"],
      "@s/*": ["./src/*"]
    }
}

By example in another project where I work we have our paths set up like this:
{
		"paths": {
			"@utils/*": ["lib/util/*"],
			"@lib/*": ["lib/*"],
			"@root/*": ["*"]
		}
}

And whenever a file is in lib/util it will suggest @utils/file.ts rather than @lib/util/file.ts.

Didn't add resolving of extends currently

@timneutkens do you plan to support this? If so, is there an issue I can follow? I would definitely be interested in this feature but cannot use jsconfigPaths as it stands.

@davecardwell it's on the roadmap, but there's no ETA. Feel free to send a pull request adding support!

Hi everyone ✋
I spend a loooottt of time on this issue and still can't get it work.
There is no problem if the alias concern a folder outside of src but if it's in src, it's not working... .
I have the Typescript error in dev mode.

I am trying to do import ExampleContainer from '@containers/ExampleContainer where ExempleContainer is located at src/containers/ExampleContainer
Here is my tsconfig.json:
{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "baseUrl": "./src",
    "paths": {
      "@containers/*": ["containers/*"],
      "@context/*": ["config/context/*"],
      "@components/*": ["components/*"],
      "@styles/*": ["styles/*"],
      "@contents/*": ["contents/*"],
      "@assets/*": ["assets/*"],
      "@utils/*": ["utils/*"],
      "@constants/*": ["config/constants/*"]
    }
  },
  "exclude": [
    "node_modules"
  ],
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx"
  ]
}

My next.config.js :
module.exports = {
  experimental: {
    jsconfigPaths: true,
  },
};

Thank you for your help 👍

Can you create a minimal repository?

Sure !
https://github.com/HeadFox/react-app-starter/tree/feature/migrate-to-typescript

Looks like it's related to yarn PnP because when you get rid of .yarn and yarnrc.yml it works fine

Okey thanks a lot👍
I will ask @arcanis if he can help me on this.

I think we might have to run our plugin before the pnp resolver plugin, though I'm not sure how to test this and it seems incredibly hard to debug installed modules when using PnP.

Hopefully this fixes it, as said I couldn't test it: https://github.com/zeit/next.js/pull/12104

Okey thanks I will test it as soon as I can !
I also send a message in the Yarn's discord

It's probably worth a separate issue, but generally speaking we don't recommend using paths or aliases (even though aliases work fine with Webpack last time I checked).
Instead, we strongly suggest to use the link: protocol, which is the idiomatic way to point a package name to a location in a way that all tools can understand without any configuration. More details here.

@arcanis worked great thanks

This is feature is working for me, but eslint is throwing a "unable to resolve path to module" errors whenever I try this. The build looks fine, but eslint is unhappy. Any insight on how to fix this? Will #11986 help?

module.exports = {
experimental: {
jsconfigPaths: true, // enables it for both jsconfig.json and tsconfig.json
}
}

Hi, Im new to webpack and next.js.
How do add the flag above if my next.config.js look like this
module.exports = withFonts(     withCSS(         withLess({             webpack(config) {                 config.module.rules.push({                     test: /\.svg(\?v=\d+\.\d+\.\d+)?$/,                     use: [                         {                             loader: 'babel-loader',                         },                         {                             loader: '@svgr/webpack',                             options: {                                 babel: false,                                 icon: true,                             },                         },                     ],                 });                 return config;             },         }),     ), );

Adds support for "paths" in both tsconfig.json or jsconfig.json.
Examples:
Single module alias
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "mytheme": ["components/mytheme.js"]
    }
  }
}

Wildcard alias
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@c/*": ["components/*"],
    }
  }
}

Fallback behavior
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@mytheme/*": ["themes/theme-a/*", "lib/theme-b/*"]
    }
  }
}

Temporarily behind an experimental feature flag:
// next.config.js
module.exports = {
  experimental: {
    jsconfigPaths: true, // enables it for both jsconfig.json and tsconfig.json
  }
}

Fixes #7779

Hi, I'm new to webpack and next.js.
How do I add the jsconfigPaths flag if my next.config.js looks like this:
module.exports = withLess({    withCSS({       webpack(config) {          return config       }    }) })

This feature does not require the flag, as it has been released as stable. It should work out of the box.

The aliasing works perfectly for me. Thx for the feature. However, I can't use "code peek" (i.e. command+click on the alias to get to the module) any longer, I am using visual studio code. Any idea why that might be?
Cheers

Hello, I am using Next 9.4.0 with TypeScript. Setting up the aliases seems to work fine, but Next fails to import the files specified unless the aliases have a slash after the @ symbol (e.g. import { bla } from @/components will work, but @components will fail).
Any ideas on why this might be? Could it be attempting to look for a node module with an @ in front, similar to @angular/core for instance?

@chris-tse I've seen that working in multiple projects, try this:
"paths": {
  "@/*": ["/*"]
}

@lfades I think I figured out the problem. I created a blank tsconfig.json, ran next dev to auto-populate the file, then added the paths to it. It wasn't recognizing the paths properly until I closed and restarted the dev server.


Add name to the background thread

This PR adds name to the background worker thread of the GlobalCollector. It will help us monitor the CPU usage of the thread.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 87.312%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

minitrace/src/collector/global_collector.rs
6
7
85.71%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
1569

Relevant Lines:
1797

💛  - Coveralls


feat:update dubbo to <IP_ADDRESS>,change alibaba to apache

Motivation:
update dubbo version
Modification:
update dubbo <IP_ADDRESS>
update zk version
fix some local test when use dubbo <IP_ADDRESS>
Result:
Fixes #https://github.com/sofastack/sofa-rpc/issues/1065
If there is no issue then describe the changes introduced by this PR.

already bump dubbo to 3.1.8 by https://github.com/sofastack/sofa-rpc/pull/1356


Add the ability to refresh the package list with a button

Discussed in https://github.com/stevenbenner/pacfinder/discussions/6

Originally posted by majestic53 March  3, 2022
I noticed that if I removed a package while pacfinder is open, the package will continue to be listed in the app. Would it be possible to add a refresh button and/or allow refresh through CTRL+R?

Added in commits:

1ec172c9ed46b7ef16e5d72aa7292a93b7488027
bddbb57e153aa146f9db8b7b55005335198187db
1172d03c516d262fb32232a992493011f05632ca
0e8c5406b1f007933ca0cbed21cb05b7da79fd9e

This will be included in the next release (version 1.2).


Pruning with restricted bits analysis

Also converts a bunch of existing tabs to spaces.

the tabs and spaces need to be in a separate pull req

is the usePartialEval flag really needed? default values for arguments make things a lot more confusing

LGTM thanks


Synthesis failed for java-kms

Hello! Autosynth couldn't regenerate java-kms. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmp4c5flwi8/googleapis'...
Cloning into '/tmpfs/tmp/tmp4c5flwi8/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '5cff5b7993329624debe15b28363457c8c07e7b1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Note: checking out 'd741cd976975c745d0199987aff0e908b8352992'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at d741cd97 chore: enable gapicv2 for firestore/v1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-05-05 21:32:00 [INFO] Running synthtool
2020-05-05 21:32:00 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:32:00,421 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-05 21:32:00,553 synthtool > Ensuring dependencies.
2020-05-05 21:32:00,564 synthtool > Cloning googleapis.
2020-05-05 21:32:00,565 synthtool > Using precloned repo /tmpfs/tmp/tmp4c5flwi8/googleapis
2020-05-05 21:32:00,570 synthtool > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-java.
2020-05-05 21:32:00,682 synthtool > Failed executing bazel build //google/cloud/kms/v1:google-cloud-kms-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/0848f48ca551a9bcb4a4401e8c6c892b/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmp4c5flwi8/googleapis/hs_err_pid23248.log

2020-05-05 21:32:00,683 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 269, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-java']' returned non-zero exit status 37.
2020-05-05 21:32:00 [ERROR] Synthesis failed
HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth-self'
Note: checking out '5cff5b7993329624debe15b28363457c8c07e7b1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Previous HEAD position was d741cd97 chore: enable gapicv2 for firestore/v1 API
HEAD is now at a3a0bf0f BREAKING_CHANGE: Removing TimeSeriesQueryLanguageCondition as an alert condition type. The condition type is unsupported and unused. It was originally added for the Monitoring Query Language Alpha feature. refactor!: Drop support for TimeSeriesQueryLanguageCondition as an alert condition type.
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at ab88356 fix: make .kokoro-autosynth executable (#522)
Switched to a new branch 'autosynth-103'
2020-05-05 21:32:00 [INFO] Running synthtool
2020-05-05 21:32:00 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:32:01,011 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-103
nothing to commit, working tree clean
2020-05-05 21:32:01,143 synthtool > Ensuring dependencies.
2020-05-05 21:32:01,154 synthtool > Cloning googleapis.
2020-05-05 21:32:01,155 synthtool > Using precloned repo /tmpfs/tmp/tmp4c5flwi8/googleapis
2020-05-05 21:32:01,159 synthtool > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-java.
2020-05-05 21:32:01,270 synthtool > Failed executing bazel build //google/cloud/kms/v1:google-cloud-kms-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/0848f48ca551a9bcb4a4401e8c6c892b/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmp4c5flwi8/googleapis/hs_err_pid23283.log

2020-05-05 21:32:01,271 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 269, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-java']' returned non-zero exit status 37.
2020-05-05 21:32:01 [ERROR] Synthesis failed
HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, 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', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-kms. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpg_wy7nud/googleapis'...
Cloning into '/tmpfs/tmp/tmpg_wy7nud/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '5cff5b7993329624debe15b28363457c8c07e7b1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Note: checking out 'd741cd976975c745d0199987aff0e908b8352992'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at d741cd97 chore: enable gapicv2 for firestore/v1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-05-07 07:01:18 [INFO] Running synthtool
2020-05-07 07:01:18 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:01:18,316 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-07 07:01:18,449 synthtool > Ensuring dependencies.
2020-05-07 07:01:18,460 synthtool > Cloning googleapis.
2020-05-07 07:01:18,461 synthtool > Using precloned repo /tmpfs/tmp/tmpg_wy7nud/googleapis
2020-05-07 07:01:18,465 synthtool > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-java.
2020-05-07 07:01:18,579 synthtool > Failed executing bazel build //google/cloud/kms/v1:google-cloud-kms-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/2e6270f19d90397ae95ce45075410b6a/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpg_wy7nud/googleapis/hs_err_pid16412.log

2020-05-07 07:01:18,580 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 269, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-java']' returned non-zero exit status 37.
2020-05-07 07:01:18 [ERROR] Synthesis failed
HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth-self'
Note: checking out '5cff5b7993329624debe15b28363457c8c07e7b1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Previous HEAD position was d741cd97 chore: enable gapicv2 for firestore/v1 API
HEAD is now at 2fc2caaa chore: enable gapic v2 and proto annotation for bigquery/storage/v1beta2 API.
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at be74d3e build: do not fail builds on codecov errors (#528)
Switched to a new branch 'autosynth-111'
2020-05-07 07:01:18 [INFO] Running synthtool
2020-05-07 07:01:18 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:01:18,901 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-111
nothing to commit, working tree clean
2020-05-07 07:01:19,031 synthtool > Ensuring dependencies.
2020-05-07 07:01:19,042 synthtool > Cloning googleapis.
2020-05-07 07:01:19,043 synthtool > Using precloned repo /tmpfs/tmp/tmpg_wy7nud/googleapis
2020-05-07 07:01:19,047 synthtool > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-java.
2020-05-07 07:01:19,158 synthtool > Failed executing bazel build //google/cloud/kms/v1:google-cloud-kms-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/2e6270f19d90397ae95ce45075410b6a/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpg_wy7nud/googleapis/hs_err_pid16447.log

2020-05-07 07:01:19,159 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 269, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-java']' returned non-zero exit status 37.
2020-05-07 07:01:19 [ERROR] Synthesis failed
HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, 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', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-kms. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpj3dhn1ja/googleapis'...
Cloning into '/tmpfs/tmp/tmpj3dhn1ja/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '5cff5b7993329624debe15b28363457c8c07e7b1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Note: checking out 'd741cd976975c745d0199987aff0e908b8352992'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at d741cd97 chore: enable gapicv2 for firestore/v1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-05-08 03:27:13 [INFO] Running synthtool
2020-05-08 03:27:13 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:27:13,882 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-08 03:27:14,020 synthtool > Ensuring dependencies.
2020-05-08 03:27:14,031 synthtool > Cloning googleapis.
2020-05-08 03:27:14,031 synthtool > Using precloned repo /tmpfs/tmp/tmpj3dhn1ja/googleapis
2020-05-08 03:27:14,035 synthtool > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-java.
2020-05-08 03:27:14,146 synthtool > Failed executing bazel build //google/cloud/kms/v1:google-cloud-kms-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/61f217ad1bfb53f5036eec272df30d07/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpj3dhn1ja/googleapis/hs_err_pid25922.log

2020-05-08 03:27:14,147 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 269, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-java']' returned non-zero exit status 37.
2020-05-08 03:27:14 [ERROR] Synthesis failed
HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth-self'
Note: checking out '5cff5b7993329624debe15b28363457c8c07e7b1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Previous HEAD position was d741cd97 chore: enable gapicv2 for firestore/v1 API
HEAD is now at 83816bb3 Add kokoro-specific .bazelrc file with arguments specific only for kokoro environments. This is to fix autosynth builds when it tries building older commits.
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 4674113 build: use Bazel 3.0.0 for autosynth builds (#529)
Switched to a new branch 'autosynth-116'
2020-05-08 03:27:14 [INFO] Running synthtool
2020-05-08 03:27:14 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:27:14,494 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-116
nothing to commit, working tree clean
2020-05-08 03:27:14,634 synthtool > Ensuring dependencies.
2020-05-08 03:27:14,645 synthtool > Cloning googleapis.
2020-05-08 03:27:14,646 synthtool > Using precloned repo /tmpfs/tmp/tmpj3dhn1ja/googleapis
2020-05-08 03:27:14,650 synthtool > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-java.
2020-05-08 03:27:14,761 synthtool > Failed executing bazel build //google/cloud/kms/v1:google-cloud-kms-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/61f217ad1bfb53f5036eec272df30d07/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpj3dhn1ja/googleapis/hs_err_pid25957.log

2020-05-08 03:27:14,761 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 269, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-java']' returned non-zero exit status 37.
2020-05-08 03:27:14 [ERROR] Synthesis failed
HEAD is now at 5cff5b7 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, 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', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.


Warn about invalid (often typoed) options.

Fixes GH-395.
I've added code that checks both options provided as arguments to the
JSHINT function and as command comments (/*jshint ... */). If JSHint
doesn't know about an option it produces a warning:
Bad option: ''.
Test plan: make test.

Why?


Bookmark should be available for guests

The current implementation only supports bookmarking talks if a user is signed in, and there is no way to know that until you actually sign in.
It would be nice if the bookmarking feature could be available for guest users too.
That may create conflicts (offline and online bookmarks), for those I suggest to keep it simple and give preference to the online ones.

See also https://github.com/joreilly/Confetti/issues/378

Prompt in https://github.com/joreilly/Confetti/pull/381, Let me know what you think!


Integration Test - Release - 2019/02/06 02:15:08

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest2 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


Translate to English

Hi
i love your great project but i have a problem
would you Please translate your comments in English
thanks alot

Did you mean to translate the README.md in English??

no for example
public static final int MPM_RANDOM_PLAY = 3; // 随即播放
and add English Language in Strings.xml
thanks a lot a we are waiting for new version
thankas agian

see #32 , thanks.

Thanks


[Improvement] Misisng @Override annotation

What would you like to be improved?
Missing override annotation for:
isImpersonationEnabled in KerberosConfig.java
toGravitinoTableChange in SparkTableChangeConverter34.java
toGravitinoType and toSparkType in SparkTypeConverter34.java
How should we improve?
add annotation

Hi, can I work on this?


Adjusted the core library, toolkit and the sample application to supp…

…ort logout from Shibboleth IdP3.
This is a pull request in response to comments in issue #169 .
Changes made:
- added NameID.java to com.onelogin.saml2.authn
- adjusted LogoutRequest to use NameID instances and generate corresponding NameId XML element
- adjusted Util.java to work with NameID
- adjusted acs.jsp to extract NameID from login response
- adjusted dologout.jsp to supply NameId and SessionIndex to Auth
- added a logout() method to Auth.java that accepts a NameID as argument
- adjusted LogoutRequestTest.java and AuthTest.java to work with the original methods (typecasts to resolve ambigous references)

Coverage decreased (-1.5%) to 93.738% when pulling 840d78c5387ed377ecb933e111f9277d2b6c6b15 on median1st:master into 1ebbb362fb6d7dd83474da8b7bbb9dac0ea8cdf9 on onelogin:master.

Coverage decreased (-1.5%) to 93.738% when pulling 840d78c5387ed377ecb933e111f9277d2b6c6b15 on median1st:master into 1ebbb362fb6d7dd83474da8b7bbb9dac0ea8cdf9 on onelogin:master.

Thanks for providing the PR, I will review it carefully and merge it or a solution inspired by that PR.

Sorry for the delay. I hope to have time next week and review & merge that PR.

No problem :)
Btw I tested and it is working well.
About the implementation, I am not sure if it is good or not to have a NameId class (I dont have much background about this library so I guess others will know better) but if it is, It could be good if the class was Serializable.
Let me know if I can help on something :)

@pitbulk
Sorry to come back to you. Did you have any update on it ?
I am willing to help you if you need.

See https://github.com/onelogin/java-saml/commit/ba141697df4bb1cd670c61307e1de7767670bf8c


[REVIEW] yellowberard

GitHub Profile Link
https://github.com/yellowberard

I like how you've got important contact links at the top. There's a lot of white space on the right, you could put all the languages, frameworks and tools all in one section. I'd definitely try and use all matching icons.

Thanks for the suggestion I will definitely work on it.

This is more-or-less the same as #1987 my only suggestion is

On the last line of the profile, the word "repositories" maybe hyperlink the repo page for that word?

Repo page: https://github.com/yellowberard?tab=repositories

I will make the changes.

I will make the changes.

Thanks!

Looks great, some thoughts...

join EddieHub 😜
double title at the top looks a bit strange
too many widgets, pick 1 or 2 (if 2, 1 single line)
try to do more issues and code reviews


streamalert - osquery prefix - plus outdated docs

to: @ryandeivert or @austinbyers or @chunyong-lin
Details

Prefix osquery logs with osquery:, as we did with CB
Fix outdated code comments in matchers/sample.py

Testing
StreamAlertCLI [INFO]: (17/17) Successful Tests
StreamAlertCLI [INFO]: (39/39) Alert Tests Passed

Coverage remained the same at 95.276% when pulling 95162b3fece09a336131193894fe880d480bcad6 on mimeframe-streamalert-osquery-prefix-upstream into 8942c7d8b1324ad7caa67ab791814b87cb35baf2 on master.


Uncaught TypeError: Cannot read properties of undefined (reading 'sourceId')

Hi, I use AdminLTE 3.2.0 and get that error.
 I took a stab at digging into the django_crispy_modal.zip you sent over, but honestly, without the models, it's been a bit of a puzzle.
Any chance you could shoot over some more code or a stripped-down version that I can fire up? It'll save me some trouble, and we might crack this nut faster together.
Appreciate your help in advance! 😊

@blasferna Thank you for responding. I'll send the models in the attachment. I tried it on empty project, it worked, but in my project I still get this error. I couldn't find a solution.
_model.zip

@ademkocamaz You found a bug, I've fixed this in the source code. Until the new version is released, you can install directly from the source:
pip install git+https://github.com/blasferna/django-crispy-formset-modal


Cleanup tox.ini

We don't need all of this configuration.
This makes it more succint.

Acceptance test failure fix: https://github.com/SUSE/skuba/pull/1066

Rebased.

https://github.com/SUSE/skuba/pull/1169

i'm not tox expert, but from what I understand this looks good. @tdaines42 could you look over this?
Thanks for cleaning this up!

Sorry forgot to respond I took a look but tox really isn't my thing. Seems like people who know better have gotten to it

@evrardjp  Do you have the issue number or bsc for this? If there is none, could you create one? We need it for planning the releases. Thanks.

There is none, this is not a bug, just an improvement

There is none, this is not a bug, just an improvement

Could you create one in avant-garde? We use Issues for planning the release work and this will help us. Otherwise they can escape our radar. Thanks in advance.

So much paperwork :)
Ok let's do it.

Done: SUSE/avant-garde#1931

Thanks. This helps.

upstream card was closed so I think this can be closed @chentex

Not sure many folks cared anyway, let's close.


[Misc] Upgrade to pytorch 2.5

Upgrade to pytorch 2.5
Requires changes to flash attn: https://github.com/vllm-project/flash-attention/pull/23

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

/ready

@bnellnm it loos like there are some cmake errors:
[2024-10-22T15:09:27Z] #25 15.41 CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
--
  | [2024-10-22T15:09:27Z] #25 15.41 Please set them or make sure they are set and tested correctly in the CMake files:
  | [2024-10-22T15:09:27Z] #25 15.41 CUDA_CUDA_LIBRARY (ADVANCED)
  | [2024-10-22T15:09:27Z] #25 15.41     linked by target "_moe_C" in directory /workspace
  | [2024-10-22T15:09:27Z] #25 15.41     linked by target "_C" in directory /workspace
  | [2024-10-22T15:09:27Z] #25 15.41     linked by target "vllm_flash_attn_c" in directory /workspace/.deps/vllm-flash-attn-src
  | [2024-10-22T15:09:27Z] #25 15.41

the cuda version should not matter that much. I think our current pipeline should still work even if pytorch itself is built against cuda 12.4 .

@bnellnm it loos like there are some cmake errors:
[2024-10-22T15:09:27Z] #25 15.41 CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
--
  | [2024-10-22T15:09:27Z] #25 15.41 Please set them or make sure they are set and tested correctly in the CMake files:
  | [2024-10-22T15:09:27Z] #25 15.41 CUDA_CUDA_LIBRARY (ADVANCED)
  | [2024-10-22T15:09:27Z] #25 15.41     linked by target "_moe_C" in directory /workspace
  | [2024-10-22T15:09:27Z] #25 15.41     linked by target "_C" in directory /workspace
  | [2024-10-22T15:09:27Z] #25 15.41     linked by target "vllm_flash_attn_c" in directory /workspace/.deps/vllm-flash-attn-src
  | [2024-10-22T15:09:27Z] #25 15.41

the cuda version should not matter that much. I think our current pipeline should still work even if pytorch itself is built against cuda 12.4 .

Looks related to https://github.com/vllm-project/vllm/pull/8609/

The PR looks good but we should quickly come to a consensus on what to do with the CUDA version that pytorch is built against

Im fine to remove the --extra-index-url if we decide to make 12.4 the default for vllm. But we should still ship 12.1 and 11.8 wheels IMO

Please merge from main to fix the CI failures for multi-modal models.

some errors are real:

cuDNN Frontend error: [cudnn_frontend] Error: No execution plans support the graph.

https://github.com/huggingface/diffusers/issues/9704
fixing by 0068133

pytorch 2.5 changes the output slightly:

[2024-10-27T04:21:27Z] hf:	‘vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs.\n\n- Advantages of using the LLM:\n  - High-fidelity and accurate predictions: The LLM can generate high-quality and context’
[2024-10-27T04:21:27Z] vllm:	‘vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs.\n\n- Advantages of using the LLM:\n  - High-efficiency and low-latency inference: The LLM provides fast and efficient’

The output is still sensible.
Therefore I changed it to logprobs check instead.
For future reference, we can also change to logprobs check if exact comparison is not feasible while it is not our fault (due to pytorch or huggingface numerical change).

Hi, looking forward to this new support, I wonder when will it be released? Thanks!

Hi, looking forward to this new support, I wonder when will it be released? Thanks!

you can install the wheel from main branch to use it directly. see https://docs.vllm.ai/en/latest/getting_started/installation.html#install-the-latest-code

@youkaichao thanks! but is it less stable than a stable version?


Android: Interactions/activies disappear on rotation

After loading your profile if you rotate your devices the interactions/activities disappear.
I assume the appropriate state isn't being saved/restored.

Yeah, it looks like the profile Activity circumvents the sync & storage system used by the rest of the app and directly invokes the API cilent for data that are pushed straight to the UI.  Not necessarily a bad low-overhead design for a lesser-used Activity, but we'll need to rely on other tricks to get persistence. Freezing/Thawing from a bundle might be sufficient?

fixed in #893


[BUG]: Certain titles not found but can be watched in normal browser's

Program version
5.1.4
Operating System
Windows
Type
GUI
Service
Crunchyroll
Command used
NIL
Show ID
G1QFP9G5E
Episode
ALL
Console Output
Nothing Found.

Series is empty!

Additional Information
Certain content/titles can be watched in normal browser's but doesn't show inside anidl search.
Searching for the title produces Nothing Found.
Using the Show ID, try to list episodes: Series is empty!

It seems to find the shows now.

Nope, if I had to guess, it was an issue on crunchy's end with a mismatch of season IDs, it wouldn't be the first time

Understand.
I will close the ticket in that case.


Adapt for GitBook 2.5.x

This should also work with previous versions of GitBook, but I enforced gitbook >= 2.5.0 in package.json, so that old versions of gitbook uses previous version of the plugin.
If you merge this PR, can you bump and publish a version? Thanks :beers:

Merged and published. Thanks @SamyPesse!

Awesome! Thanks :beers:


Move gradle wrapper scripts to gradle directory

I am proposing that you change the default location of Gradle Wrapper scripts (gradlew and gradlew.bat) generated by gradle wrapper task. Currently the default location is the working directory, which is usually the project root. Unfortunately that makes project root directory cluttered with gradle files.
Out of 8 files/folders in this example project root directory, 5 of them are Gradle specific:

I have too often seen people having disdain towards Gradle exactly because of this, especially newcomers, it gives them the impression Gradle suffers from "configuration hell" or something.
Wouldn't it be better to put those wrapper scripts in the gradle directory instead?
Executing Gradle tasks using the wrapper would now look like
eg. gradle/gradlew clean or eg.gradle/w clean, instead of ./gradlew clean (assuming working dir is project root dir).
In this example that would reduce the number of Gradle specific files in project root directory to 3.

Is there already a way to move the root directory gradle-related files to a different place?
Either by global or local settings/installations.


Update pluginSpectrumGraph_server.js

Graphical representation of the set scanner values (limit + sensitivity)

It's only active if receive the websocket commands from the scanner plugin

Wrong file. Applying manually.


Auto update fails on Samsung devices

I cannot get the auto update feature working on Samsung devices (2 smartphones and 1 tablet).

Samsung A52s with Android 14
Samsung A54 with Android 14
Samsung Tab S6 lite with Android 13

But it works perfectly on Google Pixel smartphones.

@Silther I recommend going through https://dontkillmyapp.com/samsung or something similar to disable Samsung's non-standard battery optimization settings and see whether that helps.

Maybe, but I'd need to know which exact settings are necessary to toggle, have Accrescent identify whether they're enabled (if that's possible), and if so, make Accrescent prompt the user in those cases.


"Such a creature"

https://docs.raku.org/language/list
ends with "Such a creature should never be passed back to unsuspecting users."
Should replace "creature" with something more directly descriptive, e.g. "object"

Or, perhaps "Arrays with bound slots should never be passed back to unsuspecting users."
"Passed back" could also be "returned" or "supplied".
Pm


Enhance service bus JMS starter

Switch the JMS starter to use following:
https://search.maven.org/artifact/com.microsoft.azure/azure-servicebus-jms
We should provide a snapshot version before June 1

Support sending messages to sessionenabled queues #21531
Support receivers for session enabled queues #21533
Support delayed operations on message #21532
Enable cache #21534
Support more connection properties.

Closing this issue for we have other issues tracking for these respectively.


WIREFRAME: User Profile Page

As a user of OS.io I want to be able to edit (public?) attributes/information that is listed in my profile, so that I understand what is viewed by the (public?).

Determine what attributes will be surfaced on this page and any requirements for them.
Understand where this page will sit in the product
Create UI and understand any navigation around this page.
Consider first use and repeated use scenarios.

VC's

Create wireframes
Review wireframes with UX + Stakeholders.
Post to InVision

GitHub Related:
https://github.com/fabric8io/fabric8-ui/issues/193
https://github.com/almighty/almighty-core/issues/761

@jryhanyc - According to @pmuir we now have the ability for the user to update their image by providing a new URL, but we can't implement image storage for now.  Can you think about how we present that experience in your Profile work?

@catrobson will do

Latest draft wireframes

Let's talk about this and the OAuth story in planning tomorrow briefly to figure out where we need this to head.

Jessica's latest wireframes can be found here:  https://redhat.invisionapp.com/share/KQB6LEHM8