Show multi-job output variables for deployments

Show how to output variables from deployment jobs and how to later access them from another job.
Fixes #4946

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

I tried implementing this and it doesn't seem to work. See https://github.com/MicrosoftDocs/vsts-docs/issues/4946#issuecomment-543319731.

@Slooz Sorry for the deceiving explanation I gave initially. I got confused myself by the fact that my deployment job was also named deploy.

No worries! I tested this and am now confirming that this works for me. This method allows me to use a variable from one deployment job in another deployment job.

@Victor-Savu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Victor-Savu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


feat(default): introduce Default component

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

16 of 22 (72.73%)  changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 98.879%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Psl/OS/OperatingSystemFamily.php
0
1
0.0%

src/Psl/Password/Algorithm.php
2
3
66.67%

src/Psl/RandomSequence/SecureSequence.php
0
1
0.0%

src/Psl/Shell/ErrorOutputBehavior.php
0
1
0.0%

src/Psl/TCP/ConnectOptions.php
0
1
0.0%

src/Psl/TCP/ServerOptions.php
2
3
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
4233

Relevant Lines:
4281

💛  - Coveralls


u-boot-iot2050: Update upstream queue to v2021.04

This comes with a couple of changes:

based on stable release
folded defconfig patches into main one
added support for boot-selection via USER button
cleaned up recipes

Even Ethernet works again (must have been an upstream issue, no related
changes on the patches).

These patches are in line with what I'm planning to submit to u-boot upstream soon, at least regarding baseline and watchdog support (network depends on TI).


Create a symbolic link for /etc/mtab

When ganesha starts, it looks for volume mount data in /etc/mtab. However, this file does not pre-exist in the Ubuntu image and results in the created pod hanging at ganesha server error.
mount.nfs: mounting <IP_ADDRESS>:/pvc-3d9bd71e-e7ab-4420-bffa-b158e7de9186 failed, reason given by server: No such file or directory

Since mostly /etc/mtab is a copy of /proc/mounts hence it should be safe to have as a symbolic link.
https://github.com/longhorn/longhorn/issues/2111#issuecomment-786402108

@joshimoo PTAL.


Configure source for docker images

🚀 Feature Description
Docker image should have configured source. Than when we deploy image to ghcr.io (Github) registry, image is automatically link to correct repository.

If there is another way except manually mapping after image push, i would be glad for some direction

Github docs - Labelling container images
Github docs - Connecting a repository to a package
✔ Goals

[ ] Configure image owner from .csproj

🧰 Possible Solution
via CLI
docker build  --label "org.opencontainers.image.source=https://github.com/octocat/my-repo"

dockerfile
LABEL org.opencontainers.image.source=https://github.com/octocat/my-repo

As a source it can be fetched from .csproj. This way it is used via nuget packages i think
 <PropertyGroup>
   ...
    <RepositoryUrl>https://github.com/octocat/my-repo</RepositoryUrl>
   ...
 </PropertyGroup>

This is already implemented.
https://github.com/dotnet/sdk/blob/190723c80d85721cdc58fd906e645c4029b947bb/src/Containers/Microsoft.NET.Build.Containers/KnownStrings.cs#L13
See here in the .net 8 SDK source code, "ContainerRegistry" is deprecated in favor of ContainerRepository which aspir8 already supports.
You can either include ContainerRepository within your csproj, which is the recommended way, or you can specify on the command line with https://github.com/prom3theu5/aspirational-manifests/blob/main/src/Aspirate.Commands/Options/ContainerRepositoryPrefixOption.cs

In fact you also have
CurrentState.ContainerRegistry, which is set by https://github.com/prom3theu5/aspirational-manifests/blob/main/src/Aspirate.Commands/Options/ContainerRegistryOption.cs
The produced image by the builder will be
 /  / image : tag

I don't know if i understand that correctly but i think we are taking about different thinks.
You are talking about image name, I'm talking about image annotation of source.
But non the less thanks to you i have found this: sdk-container-builds docs
Configuring PrivateRepositoryUrl in .csproj will add annotation for image: org.opencontainers.image.source
    <PublishRepositoryUrl>true</PublishRepositoryUrl>
    <PrivateRepositoryUrl>https://github.com/octocat/my-repo</PrivateRepositoryUrl>

note: PrivateRepositoryUrl  is only written if PublishRepositoryUrl is true. Also relies on Sourcelink infrastructure being part of the build.

Alternative is to set annotation straight up:
  <ItemGroup>
    <ContainerLabel Include="org.opencontainers.image.source" Value="https://github.com/octocat/my-repo" />
  </ItemGroup>


Small update

... still based on LVGL v6.x

Removed need for Ticker (use the Arduino standard millis())
way faster screen update based on Bodmer suggestion
faster debugging output (removed the delay call)

Thank you Pablo!

You are welcome. I do have v7.x version prepared also (in my repo), but (when I see commits to the 7.0.1-dev) I'm waiting for 7.0.1 release to avoid -dev version missleading.


FreeBSD pip/virtualenv installations fail as py36-{pip,virtualenv} are no longer upstream

For now I've had to set pip to false and roll our own execs for pip and virtualenv.  I'll provide the code below that we use for ensuring pip (noting that we specify in heira data the python version to pass to this module, so 36 if we want python 3.6 to be installed)
  exec { 'ensurepip':
    command => "/usr/local/bin/python${version[0]}.${version[1]} -m ensurepip",
    creates => "/usr/local/bin/pip-${version[0]}.${version[1]}",
    require => Package["python${version}"],
  }

Thank you for the report.  Can you elaborate on why this change is required?  Does this come up because you are installing a different python version than the default?
For context, on my FreeBSD systems, I set DEFAULT_VERSIONS=python=3.6 in my ports builds, and then specify 36 in hiera as you do also, so that I have the py360{pip,virtualenv} packages available.

Hi Zack,
As far as I understand it, the default package manager in Puppet for FreeBSD is pkg(ng), so when puppet tries to interpret the following:
class { 'python' :
  version    => '36',
  pip        => true,
  dev        => true,
  virtualenv => true,
}

the module checks the valid versions in the FreeBSD.yaml and then gets:
  '36':
    virtualenv_package: 'py36-virtualenv'
    virtualenv_cmd: 'virtualenv-3.6'
    pip_package: 'py36-pip'
    pip_cmd: 'pip-3.6'

From here pkg will try to install py36-pip which doesn't exist using the ensure_pip function which doesn't override the pkg provider default.  As py36-pip doesn't exist upstream (and we've not yet built our poudriere infrastructure to provide our own ports built packages) the python module fails.

Ah yes, you are correct.  The only reason I'm able to install python 3.6 on my systems is due to the fact that I'm building my own ports with poudriere.  How have you gotten python3.6 installed?
To get poudriere going, there is a module that could help.
https://github.com/xaque208/puppet-poudriere
Maybe this module could support something like pyenv, which is like rbenv, but for python to get installed versions that are not available as packages.

Hi Zack,
Sorry for the delay in responding (I'm not getting the emails from github just for this issue for some reason.)  I rolled back from 3.6 to 3.5, but I was using this module to deploy to FreeBSD 11 client servers and it pulls down the python36  package just fine because it's available.
I'd really like, and we have the requirements for it, to get poudriere up and running in our infrastructure.  But in the mean time I've got something like the above exec working for both the require pip step and installing the virtualenv.
The pyenv approach sounds interesting; I've actually had a play about with this on Ubuntu.
Kind regards,
Richard

Hi Zack.  Let's close this.  We could use the module now, for python 3.6 for example, because the upstream has switch to providing py36 packages, but if we wanted to rebuild our older projects which have still only been tested as working with python 3.5 we couldn't because those packages no longer exist upstream.
This is a seemingly intractable problem that we will always face but for which we have an automated version of a manual solution as described in my first post explaining the issue.


Bugs i guess

i just compiled python factorial program that i write but terminal cant work and shuted down!~
help me plz

Please retest again with platformio-atom-ide-terminal 2.9.0


more programming environments; many failures

in execution of reframe
closes issure #304

Are these tests valid for dom/daint, because they also fail for me there.

added flag -Mnorpath ; now it is running on dom and daint

@teojgo I think this is expected, isn't it @ajocksch?

I tried myself on kesch and they fail


[Autocomplete]: Typescript error when using controlled Autocomplete with disableClearable

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
HI there,
I have the following code -
type Entity = {
  id: number;
  name: string;
};

const data: Entity[] = [
  { id: 1, name: "Org 1" },
  { id: 2, name: "Org 2" },
  { id: 3, name: "Org 3" }
];

const App = () =>
{
  const [organization, setOrganization] = useState<Entity | null>(null);

  return (
    <Autocomplete
        renderInput={(params) => <TextField {...params} label="Organization" />}
        options={data}
        getOptionLabel={({ name }) => name}
        onChange={(event, value) => {
          setOrganization(value);
        }}
        value={organization}
        disableClearable
      />
  );
}

This code causes typescript error for the value prop -
Type 'Entity | null' is not assignable to type 'Entity | undefined'.
  Type 'null' is not assignable to type 'Entity | undefined'.

I tried to use also undefined instead of null. But I get an error in that case, because we change uncontrolled state to controlled - MUI: A component is changing the uncontrolled value state of Autocomplete to be controlled.
How can I use controlled autocomplete element with empty default value?
Expected behavior 🤔
No response
Steps to reproduce 🕹
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
 System:
    OS: macOS 11.6.4
  Binaries:
    Node: 18.0.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.6.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Edge: Not Found
    Firefox: 92.0
    Safari: 15.3
  npmPackages:
    @emotion/react: ^11.9.0 => 11.9.3
    @emotion/styled: ^11.8.1 => 11.9.3
    @mui/base:  5.0.0-alpha.91
    @mui/icons-material: ^5.8.4 => 5.8.4
    @mui/lab: ~5.0.0-alpha.91 => 5.0.0-alpha.92
    @mui/material: ~5.9.1 => 5.9.2
    @mui/private-theming:  5.9.1
    @mui/styled-engine:  5.8.7
    @mui/system:  5.9.2
    @mui/types:  7.1.5
    @mui/utils:  5.9.1
    @types/react: ^18.0.9 => 18.0.15
    react: ^18.1.0 => 18.2.0
    react-dom: ^18.1.0 => 18.2.0
    typescript: ^4.7.3 => 4.7.4

Your solution works as expected with our example and null is the correct value to be used https://codesandbox.io/s/modest-stallman-ye4uye?file=/src/App.tsx

Hi @povilass,
it works in codesandbox, but in real compiler it doesn't.
I use the latest versions. Sorry, I've forgot to add env info. Thank you, it's fixed now.

Duplicate of #29046

Since the typings make sense, you can apply disableClearable when the value is set by doing:
disableClearable={!!organization}


Image under compass

Hello, i would like to know if it's possible to place an image under the compass in some way instead of having a blank background.
It could be usefull to help people to navigate in closed spaces.
Thank you for the time and , eventually, answer.

This is possible if you override the .pnlm-compass CSS class.

I followed your hints and now is working like intended.Thank you  for your time and your library :)


disconnect versioning of org.wso2.carbon.user.mgt.common from carbon-identity-framework

currently, custom password generators are dependent on org.wso2.carbon.user.mgt.common.  The codebase of this package has not changed in a year, but in that time it has had hundreds of unnecessary versions due to being tied to the versioning of carbon-identity-framework.  This creates extra overhead for maintainers of addons based on this package, such as customer password generators.
Splitting the codebase & lifecycle of these two packages would greatly improve the stability of such addons.

Unless there is a requirement to use some specific API being introduced in some latter version of the dependent component org.wso2.carbon.user.mgt.common, I don't think there is any necessity to change the dependent component version when building up the extension.
As in runtime, if the extension defines a major to minor, or major to major version range, it will get resolved to the version which is available in the runtime within its version range. We don't see any complications there.
Therefore, appreciate if you can elaborate more on the experience in maintaining the custom password generator extensions and limitations observed.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


added-device-independent-pixels-article

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Thank You so much!!! That was my pleasure to contribute :heart_eyes:


New command: spo group list

spo group list

Adds 'spo group list ' command. Closes #1691

Coverage remained the same at 100.0% when pulling a6904d069a287ceef2747fcfbf2e227344b6c5c6 on dips365:grouplist into 0d730dbdd2ddff7d90e039a9d8ab56a87de7a794 on pnp:master.

@VelinGeorgiev
Please review it and let me know if needs any change.

Thanks @dips365 We'll review it shortly 👍

@VelinGeorgiev Thanks For review and comments.
I will take care of it in upcoming work.


loss

Why do my output loss_G and loss_D are opposite to each other? In your code, loss_G and loss_D are just symbols different. And after this training is completed, the predictions are all nan. Why is this so?
I really hope to hear from you.

Because the denominator may be 0 in the calculate of iou and dice, you can replace the np.mean() with np.nanmean().

Because the denominator may be 0 in the calculate of iou and dice, you can replace the np.mean() with np.nanmean().

I am also have a problem with the loss_G and loss_D, actually, I changed the symbol of the loss_D,  but the results do not seem to differ.  Is anyone could explain it?

This shouldn't be happening, maybe you can try to train with the adversarial loss alone (i.e., w/o the dice loss, which was put there to help stabilize the adversarial training). In that case, changing the symbol should just make the whole training fail.


layers/meta-balena: Update to v2.53.8

Update meta-balena from 2.52.7 to 2.53.8
Changelog-entry: Update meta-balena from v2.52.7 to v2.53.8
Signed-off-by: Alexandru Costache<EMAIL_ADDRESS>

@balena-ci I self-certify!


Add all link buttons for results

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Ok, that is a good idea, users can link to the product detail page directly, and there is no need to copy and paste.

That's true!


[Minor] Standardize naming convention within modules (discussion)

Open discussion to standardize how we name and organize the contents of a module

Idea 1: For a module with many sub modules (partials)
@import './node_modules/@casper/nightshade-styles/modules/<module-name>bundle';

Idea 2: For a module with one file
@import './node_modules/@casper/nightshade-styles/modules/<modulename>/base';


Feature Request: Improvements to testing redirects in

Is there a possibility that the functionality of MemoryRouter could be extended with a method that allows a test to push changes to the history directly? That would greatly simplify the amount of code needed to do integration testing on flows that go from one page to another. The navigation testing example in the documentation shows a possible way for testing synchronous navigation, but seems like it would become awkward for async.
As an example: I'm trying to do integration testing on a form that submits a comment to an API, then redirects to another route that will fetch and show the comments. Most code examples I find online show it is easy to test that a redirect happened and where it redirected to. The ReactRouter documentation has the only example I could find that could actually test content on the redirected page. The code there is relatively complex.

You can make your own memory router with a separate history instance. Then you can push to it externally however you'd like. It's simple:
import { createMemoryHistory } from "history";
import { Router } from "react-router";

const history = createMemoryHistory();
const tree = mount(<Router history={history} />);

history.push('/foo');


pdns 4.1.3 install issues

I am new with pdns looking to manage it a little easier.
I was able to install pdns_server and the recursor on a ubuntu 16.04, imported all data from bind and it is responding to queries OK.
Try to follow the flask howto  and after a few hiccups I was able create a admin user, login and created an account,
unfortunately none of my domains show to be managed.
I try to add one manually but got error 400.
Is there a document that describe how this all is supposed to work? configure powerdns-admin to play with pdns latest release, how to create templates etc.
thanks
sc

Have you specified pdns version and its API key in the config.py file ?

yes,
I see this in the logfile:
2018-07-09 17:07:53,390 - app.models - ERROR - Config Option "api-config-dir" must be set
I did not find an entry in the config file for this, I added
API_CONFIG_DIR = "/var/www/powerdns-admin"
no more errors and nothing on domain list. still not able to add a domain error 400.
and ignorant on how to create a template.


Added the Igbo name Chizi

Added the igbo name chizi to \collections

Hey @cezennia,
Thanks, however, the tests are failing because your translations contain capital letters.
Also, the Hebrew translation should be spelled using the Hebrew alphabet.
Please make the changes and I'll merge your PR

That's not the correct Hebrew translation.
You can also remove the Hebrew translation and I'll merge it.

adjusted the hebrew translation and Capitalization issues

Cool, thanks!
merged #1


Synthesis failed for gax-nodejs

Hello! Autosynth couldn't regenerate gax-nodejs. :broken_heart:
Here's the output from running synth.py:
b'3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/live-server/node_modules/fsevents):\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\n\naudited 1393 packages in 19.229s\nfound 0 vulnerabilities\n\n2020-05-29 04:11:54,414 synthtool [DEBUG] > Running prelint...\nDEBUG:synthtool:Running prelint...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>prelint /home/kbuilder/.cache/synthtool/gax-nodejs\n> cd samples; npm link ../; npm install\n\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! path /home/kbuilder/.cache/synthtool/gax-nodejs\nnpm ERR! code EACCES\nnpm ERR! errno -13\nnpm ERR! syscall symlink\nnpm ERR! Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'\nnpm ERR!  [Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'] {\nnpm ERR!   errno: -13,\nnpm ERR!   code: \'EACCES\',\nnpm ERR!   syscall: \'symlink\',\nnpm ERR!   path: \'/home/kbuilder/.cache/synthtool/gax-nodejs\',\nnpm ERR!   dest: \'/usr/lib/node_modules/google-gax\'\nnpm ERR! }\nnpm ERR! \nnpm ERR! The operation was rejected by your operating system.\nnpm ERR! It is likely you do not have the permissions to access this file as the current user\nnpm ERR! \nnpm ERR! If you believe this might be a permissions issue, please double-check the\nnpm ERR! permissions of the file and its containing directories, or try running\nnpm ERR! the command again as root/Administrator (though this is not recommended).\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-29T11_11_54_854Z-debug.log\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! code ETARGET\nnpm ERR! notarget No matching version found for<EMAIL_ADDRESS>ERR! notarget In most cases you or one of your dependencies are requesting\nnpm ERR! notarget a package version that doesn\'t exist.\n\nnpm ERR!  Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>prelint script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-29T11_11_56_834Z-debug.log\n2020-05-29 04:11:56,842 synthtool [DEBUG] > Running fix...\nDEBUG:synthtool:Running fix...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>fix /home/kbuilder/.cache/synthtool/gax-nodejs\n> gts fix\n\nversion: 12\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/pagination.js\n  21:23  error  "google-gax" is not found  node/no-missing-require\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/quickstart.js\n  23:23  error  "google-gax" is not found  node/no-missing-require\n\n\xe2\x9c\x96 2 problems (2 errors, 0 warnings)\n\nError: Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\n    at makeError (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/lib/error.js:59:11)\n    at handlePromise (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/index.js:114:26)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)\n    at async run (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/gts/build/src/cli.js:120:17) {\n  shortMessage: \'Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  command: \'node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  exitCode: 1,\n  signal: undefined,\n  signalDescription: undefined,\n  stdout: undefined,\n  stderr: undefined,\n  failed: true,\n  timedOut: false,\n  isCanceled: false,\n  killed: false\n}\nnpm ERR! code ELIFECYCLE\nnpm ERR! errno 1\nnpm ERR<EMAIL_ADDRESS>fix: `gts fix`\nnpm ERR! Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>fix script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-29T11_12_04_541Z-debug.log\n2020-05-29 04:12:04,550 synthtool [ERROR] > Failed executing npm run fix:\n\nNone\nERROR:synthtool:Failed executing npm run fix:\n\nNone\n2020-05-29 04:12:04,551 synthtool [DEBUG] > Wrote metadata to synth.metadata.\nDEBUG:synthtool:Wrote metadata to synth.metadata.\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__\n    return self.main(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main\n    rv = self.invoke(ctx)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke\n    return callback(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main\n    spec.loader.exec_module(synth_module)  # type: ignore\n  File "<frozen importlib._bootstrap_external>", line 678, in exec_module\n  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed\n  File "/home/kbuilder/.cache/synthtool/gax-nodejs/synth.py", line 28, in <module>\n    node.fix()\n  File "/tmpfs/src/github/synthtool/synthtool/languages/node.py", line 179, in fix\n    shell.run(["npm", "run", "fix"], hide_output=hide_output)\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run\n    raise exc\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run\n    encoding="utf-8",\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run\n    output=stdout, stderr=stderr)\nsubprocess.CalledProcessError: Command \'[\'npm\', \'run\', \'fix\']\' returned non-zero exit status 1.\n2020-05-29 04:12:04,593 autosynth [ERROR] > Synthesis failed\n2020-05-29 04:12:04,593 autosynth [DEBUG] > Running: git reset --hard HEAD\nHEAD is now at d94c2dd chore: release 2.4.1 (#835)\n2020-05-29 04:12:04,600 autosynth [DEBUG] > Running: git checkout autosynth\nSwitched to branch \'autosynth\'\n2020-05-29 04:12:04,605 autosynth [DEBUG] > Running: git clean -fdx\nRemoving __pycache__/\nRemoving build/\nRemoving node_modules/\nRemoving package-lock.json\nRemoving protos/google/\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main\n    return _inner_main(temp_dir)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 595, in _inner_main\n    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 371, in synthesize_loop\n    synthesize_inner_loop(toolbox, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 381, in synthesize_inner_loop\n    synthesizer, len(toolbox.versions) - 1\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch\n    synthesizer.synthesize(synth_log_path, self.environ)\n  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 119, in synthesize\n    synth_proc.check_returncode()  # Raise an exception.\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode\n    self.stderr)\nsubprocess.CalledProcessError: Command \'[\'/tmpfs/src/github/synthtool/env/bin/python3\', \'-m\', \'synthtool\', \'--metadata\', \'synth.metadata\', \'synth.py\', \'--\']\' returned non-zero exit status 1.\n'

Google internal developers can see the full log here.

Autosynth is still having trouble generating gax-nodejs. :sob:
Here's the output from running synth.py:
b'3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/live-server/node_modules/fsevents):\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\n\naudited 1393 packages in 17.831s\nfound 0 vulnerabilities\n\n2020-05-30 04:11:37,356 synthtool [DEBUG] > Running prelint...\nDEBUG:synthtool:Running prelint...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>prelint /home/kbuilder/.cache/synthtool/gax-nodejs\n> cd samples; npm link ../; npm install\n\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! path /home/kbuilder/.cache/synthtool/gax-nodejs\nnpm ERR! code EACCES\nnpm ERR! errno -13\nnpm ERR! syscall symlink\nnpm ERR! Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'\nnpm ERR!  [Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'] {\nnpm ERR!   errno: -13,\nnpm ERR!   code: \'EACCES\',\nnpm ERR!   syscall: \'symlink\',\nnpm ERR!   path: \'/home/kbuilder/.cache/synthtool/gax-nodejs\',\nnpm ERR!   dest: \'/usr/lib/node_modules/google-gax\'\nnpm ERR! }\nnpm ERR! \nnpm ERR! The operation was rejected by your operating system.\nnpm ERR! It is likely you do not have the permissions to access this file as the current user\nnpm ERR! \nnpm ERR! If you believe this might be a permissions issue, please double-check the\nnpm ERR! permissions of the file and its containing directories, or try running\nnpm ERR! the command again as root/Administrator (though this is not recommended).\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-30T11_11_37_780Z-debug.log\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! code ETARGET\nnpm ERR! notarget No matching version found for<EMAIL_ADDRESS>ERR! notarget In most cases you or one of your dependencies are requesting\nnpm ERR! notarget a package version that doesn\'t exist.\n\nnpm ERR!  Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>prelint script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-30T11_11_39_738Z-debug.log\n2020-05-30 04:11:39,748 synthtool [DEBUG] > Running fix...\nDEBUG:synthtool:Running fix...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>fix /home/kbuilder/.cache/synthtool/gax-nodejs\n> gts fix\n\nversion: 12\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/pagination.js\n  21:23  error  "google-gax" is not found  node/no-missing-require\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/quickstart.js\n  23:23  error  "google-gax" is not found  node/no-missing-require\n\n\xe2\x9c\x96 2 problems (2 errors, 0 warnings)\n\nError: Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\n    at makeError (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/lib/error.js:59:11)\n    at handlePromise (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/index.js:114:26)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)\n    at async run (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/gts/build/src/cli.js:120:17) {\n  shortMessage: \'Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  command: \'node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  exitCode: 1,\n  signal: undefined,\n  signalDescription: undefined,\n  stdout: undefined,\n  stderr: undefined,\n  failed: true,\n  timedOut: false,\n  isCanceled: false,\n  killed: false\n}\nnpm ERR! code ELIFECYCLE\nnpm ERR! errno 1\nnpm ERR<EMAIL_ADDRESS>fix: `gts fix`\nnpm ERR! Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>fix script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-30T11_11_47_267Z-debug.log\n2020-05-30 04:11:47,277 synthtool [ERROR] > Failed executing npm run fix:\n\nNone\nERROR:synthtool:Failed executing npm run fix:\n\nNone\n2020-05-30 04:11:47,279 synthtool [DEBUG] > Wrote metadata to synth.metadata.\nDEBUG:synthtool:Wrote metadata to synth.metadata.\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__\n    return self.main(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main\n    rv = self.invoke(ctx)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke\n    return callback(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main\n    spec.loader.exec_module(synth_module)  # type: ignore\n  File "<frozen importlib._bootstrap_external>", line 678, in exec_module\n  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed\n  File "/home/kbuilder/.cache/synthtool/gax-nodejs/synth.py", line 28, in <module>\n    node.fix()\n  File "/tmpfs/src/github/synthtool/synthtool/languages/node.py", line 179, in fix\n    shell.run(["npm", "run", "fix"], hide_output=hide_output)\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run\n    raise exc\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run\n    encoding="utf-8",\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run\n    output=stdout, stderr=stderr)\nsubprocess.CalledProcessError: Command \'[\'npm\', \'run\', \'fix\']\' returned non-zero exit status 1.\n2020-05-30 04:11:47,341 autosynth [ERROR] > Synthesis failed\n2020-05-30 04:11:47,342 autosynth [DEBUG] > Running: git reset --hard HEAD\nHEAD is now at d94c2dd chore: release 2.4.1 (#835)\n2020-05-30 04:11:47,350 autosynth [DEBUG] > Running: git checkout autosynth\nSwitched to branch \'autosynth\'\n2020-05-30 04:11:47,356 autosynth [DEBUG] > Running: git clean -fdx\nRemoving __pycache__/\nRemoving build/\nRemoving node_modules/\nRemoving package-lock.json\nRemoving protos/google/\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main\n    return _inner_main(temp_dir)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 595, in _inner_main\n    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 371, in synthesize_loop\n    synthesize_inner_loop(toolbox, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 381, in synthesize_inner_loop\n    synthesizer, len(toolbox.versions) - 1\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch\n    synthesizer.synthesize(synth_log_path, self.environ)\n  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 119, in synthesize\n    synth_proc.check_returncode()  # Raise an exception.\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode\n    self.stderr)\nsubprocess.CalledProcessError: Command \'[\'/tmpfs/src/github/synthtool/env/bin/python3\', \'-m\', \'synthtool\', \'--metadata\', \'synth.metadata\', \'synth.py\', \'--\']\' returned non-zero exit status 1.\n'

Google internal developers can see the full log here.

Autosynth is still having trouble generating gax-nodejs. :sob:
Here's the output from running synth.py:
b'd {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\n\naudited 1393 packages in 17.365s\nfound 0 vulnerabilities\n\n2020-05-31 04:11:33,776 synthtool [DEBUG] > Running prelint...\nDEBUG:synthtool:Running prelint...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>prelint /home/kbuilder/.cache/synthtool/gax-nodejs\n> cd samples; npm link ../; npm install\n\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! path /home/kbuilder/.cache/synthtool/gax-nodejs\nnpm ERR! code EACCES\nnpm ERR! errno -13\nnpm ERR! syscall symlink\nnpm ERR! Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'\nnpm ERR!  [Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'] {\nnpm ERR!   errno: -13,\nnpm ERR!   code: \'EACCES\',\nnpm ERR!   syscall: \'symlink\',\nnpm ERR!   path: \'/home/kbuilder/.cache/synthtool/gax-nodejs\',\nnpm ERR!   dest: \'/usr/lib/node_modules/google-gax\'\nnpm ERR! }\nnpm ERR! \nnpm ERR! The operation was rejected by your operating system.\nnpm ERR! It is likely you do not have the permissions to access this file as the current user\nnpm ERR! \nnpm ERR! If you believe this might be a permissions issue, please double-check the\nnpm ERR! permissions of the file and its containing directories, or try running\nnpm ERR! the command again as root/Administrator (though this is not recommended).\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-31T11_11_34_188Z-debug.log\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! code ETARGET\nnpm ERR! notarget No matching version found for<EMAIL_ADDRESS>ERR! notarget In most cases you or one of your dependencies are requesting\nnpm ERR! notarget a package version that doesn\'t exist.\n\nnpm ERR!  Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>prelint script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-31T11_11_36_101Z-debug.log\n2020-05-31 04:11:36,110 synthtool [DEBUG] > Running fix...\nDEBUG:synthtool:Running fix...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>fix /home/kbuilder/.cache/synthtool/gax-nodejs\n> gts fix\n\nversion: 12\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/pagination.js\n  21:23  error  "google-gax" is not found  node/no-missing-require\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/quickstart.js\n  23:23  error  "google-gax" is not found  node/no-missing-require\n\n\xe2\x9c\x96 2 problems (2 errors, 0 warnings)\n\nError: Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\n    at makeError (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/lib/error.js:59:11)\n    at handlePromise (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/index.js:114:26)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)\n    at async run (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/gts/build/src/cli.js:120:17) {\n  shortMessage: \'Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  command: \'node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  exitCode: 1,\n  signal: undefined,\n  signalDescription: undefined,\n  stdout: undefined,\n  stderr: undefined,\n  failed: true,\n  timedOut: false,\n  isCanceled: false,\n  killed: false\n}\nnpm ERR! code ELIFECYCLE\nnpm ERR! errno 1\nnpm ERR<EMAIL_ADDRESS>fix: `gts fix`\nnpm ERR! Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>fix script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-05-31T11_11_43_400Z-debug.log\n2020-05-31 04:11:43,410 synthtool [ERROR] > Failed executing npm run fix:\n\nNone\nERROR:synthtool:Failed executing npm run fix:\n\nNone\n2020-05-31 04:11:43,411 synthtool [DEBUG] > Wrote metadata to synth.metadata.\nDEBUG:synthtool:Wrote metadata to synth.metadata.\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__\n    return self.main(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main\n    rv = self.invoke(ctx)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke\n    return callback(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main\n    spec.loader.exec_module(synth_module)  # type: ignore\n  File "<frozen importlib._bootstrap_external>", line 678, in exec_module\n  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed\n  File "/home/kbuilder/.cache/synthtool/gax-nodejs/synth.py", line 28, in <module>\n    node.fix()\n  File "/tmpfs/src/github/synthtool/synthtool/languages/node.py", line 179, in fix\n    shell.run(["npm", "run", "fix"], hide_output=hide_output)\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run\n    raise exc\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run\n    encoding="utf-8",\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run\n    output=stdout, stderr=stderr)\nsubprocess.CalledProcessError: Command \'[\'npm\', \'run\', \'fix\']\' returned non-zero exit status 1.\n2020-05-31 04:11:43,464 autosynth [ERROR] > Synthesis failed\n2020-05-31 04:11:43,464 autosynth [DEBUG] > Running: git reset --hard HEAD\nHEAD is now at d94c2dd chore: release 2.4.1 (#835)\n2020-05-31 04:11:43,475 autosynth [DEBUG] > Running: git checkout autosynth\nSwitched to branch \'autosynth\'\n2020-05-31 04:11:43,481 autosynth [DEBUG] > Running: git clean -fdx\nRemoving __pycache__/\nRemoving build/\nRemoving node_modules/\nRemoving package-lock.json\nRemoving protos/google/\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main\n    return _inner_main(temp_dir)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 595, in _inner_main\n    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 371, in synthesize_loop\n    synthesize_inner_loop(toolbox, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 381, in synthesize_inner_loop\n    synthesizer, len(toolbox.versions) - 1\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch\n    synthesizer.synthesize(synth_log_path, self.environ)\n  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 119, in synthesize\n    synth_proc.check_returncode()  # Raise an exception.\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode\n    self.stderr)\nsubprocess.CalledProcessError: Command \'[\'/tmpfs/src/github/synthtool/env/bin/python3\', \'-m\', \'synthtool\', \'--metadata\', \'synth.metadata\', \'synth.py\', \'--\']\' returned non-zero exit status 1.\n'

Google internal developers can see the full log here.

Autosynth is still having trouble generating gax-nodejs. :sob:
Here's the output from running synth.py:
b'ed {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})\n\naudited 1393 packages in 19.44s\nfound 0 vulnerabilities\n\n2020-06-01 04:11:52,240 synthtool [DEBUG] > Running prelint...\nDEBUG:synthtool:Running prelint...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>prelint /home/kbuilder/.cache/synthtool/gax-nodejs\n> cd samples; npm link ../; npm install\n\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! path /home/kbuilder/.cache/synthtool/gax-nodejs\nnpm ERR! code EACCES\nnpm ERR! errno -13\nnpm ERR! syscall symlink\nnpm ERR! Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'\nnpm ERR!  [Error: EACCES: permission denied, symlink \'/home/kbuilder/.cache/synthtool/gax-nodejs\' -> \'/usr/lib/node_modules/google-gax\'] {\nnpm ERR!   errno: -13,\nnpm ERR!   code: \'EACCES\',\nnpm ERR!   syscall: \'symlink\',\nnpm ERR!   path: \'/home/kbuilder/.cache/synthtool/gax-nodejs\',\nnpm ERR!   dest: \'/usr/lib/node_modules/google-gax\'\nnpm ERR! }\nnpm ERR! \nnpm ERR! The operation was rejected by your operating system.\nnpm ERR! It is likely you do not have the permissions to access this file as the current user\nnpm ERR! \nnpm ERR! If you believe this might be a permissions issue, please double-check the\nnpm ERR! permissions of the file and its containing directories, or try running\nnpm ERR! the command again as root/Administrator (though this is not recommended).\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-06-01T11_11_52_681Z-debug.log\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\nnpm ERR! code ETARGET\nnpm ERR! notarget No matching version found for<EMAIL_ADDRESS>ERR! notarget In most cases you or one of your dependencies are requesting\nnpm ERR! notarget a package version that doesn\'t exist.\n\nnpm ERR!  Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>prelint script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-06-01T11_11_54_675Z-debug.log\n2020-06-01 04:11:54,683 synthtool [DEBUG] > Running fix...\nDEBUG:synthtool:Running fix...\nnpm WARN npm npm does not support Node.js v12.17.0\nnpm WARN npm You should probably upgrade to a newer version of node as we\nnpm WARN npm can\'t make any promises that npm will work with this version.\nnpm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.\nnpm WARN npm You can find the latest version at https://nodejs.org/\n\n><EMAIL_ADDRESS>fix /home/kbuilder/.cache/synthtool/gax-nodejs\n> gts fix\n\nversion: 12\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/pagination.js\n  21:23  error  "google-gax" is not found  node/no-missing-require\n\n/home/kbuilder/.cache/synthtool/gax-nodejs/samples/quickstart.js\n  23:23  error  "google-gax" is not found  node/no-missing-require\n\n\xe2\x9c\x96 2 problems (2 errors, 0 warnings)\n\nError: Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\n    at makeError (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/lib/error.js:59:11)\n    at handlePromise (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/execa/index.js:114:26)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)\n    at async run (/home/kbuilder/.cache/synthtool/gax-nodejs/node_modules/gts/build/src/cli.js:120:17) {\n  shortMessage: \'Command failed with exit code 1: node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  command: \'node ./node_modules/eslint/bin/eslint --fix **/*.ts **/*.js **/*.tsx **/*.jsx --no-error-on-unmatched-pattern\',\n  exitCode: 1,\n  signal: undefined,\n  signalDescription: undefined,\n  stdout: undefined,\n  stderr: undefined,\n  failed: true,\n  timedOut: false,\n  isCanceled: false,\n  killed: false\n}\nnpm ERR! code ELIFECYCLE\nnpm ERR! errno 1\nnpm ERR<EMAIL_ADDRESS>fix: `gts fix`\nnpm ERR! Exit status 1\nnpm ERR! \nnpm ERR! Failed at the<EMAIL_ADDRESS>fix script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /home/kbuilder/.npm/_logs/2020-06-01T11_12_02_421Z-debug.log\n2020-06-01 04:12:02,430 synthtool [ERROR] > Failed executing npm run fix:\n\nNone\nERROR:synthtool:Failed executing npm run fix:\n\nNone\n2020-06-01 04:12:02,431 synthtool [DEBUG] > Wrote metadata to synth.metadata.\nDEBUG:synthtool:Wrote metadata to synth.metadata.\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__\n    return self.main(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main\n    rv = self.invoke(ctx)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke\n    return callback(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main\n    spec.loader.exec_module(synth_module)  # type: ignore\n  File "<frozen importlib._bootstrap_external>", line 678, in exec_module\n  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed\n  File "/home/kbuilder/.cache/synthtool/gax-nodejs/synth.py", line 28, in <module>\n    node.fix()\n  File "/tmpfs/src/github/synthtool/synthtool/languages/node.py", line 179, in fix\n    shell.run(["npm", "run", "fix"], hide_output=hide_output)\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run\n    raise exc\n  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run\n    encoding="utf-8",\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run\n    output=stdout, stderr=stderr)\nsubprocess.CalledProcessError: Command \'[\'npm\', \'run\', \'fix\']\' returned non-zero exit status 1.\n2020-06-01 04:12:02,471 autosynth [ERROR] > Synthesis failed\n2020-06-01 04:12:02,471 autosynth [DEBUG] > Running: git reset --hard HEAD\nHEAD is now at d94c2dd chore: release 2.4.1 (#835)\n2020-06-01 04:12:02,479 autosynth [DEBUG] > Running: git checkout autosynth\nSwitched to branch \'autosynth\'\n2020-06-01 04:12:02,484 autosynth [DEBUG] > Running: git clean -fdx\nRemoving __pycache__/\nRemoving build/\nRemoving node_modules/\nRemoving package-lock.json\nRemoving protos/google/\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main\n    return _inner_main(temp_dir)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 595, in _inner_main\n    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 371, in synthesize_loop\n    synthesize_inner_loop(toolbox, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 381, in synthesize_inner_loop\n    synthesizer, len(toolbox.versions) - 1\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch\n    synthesizer.synthesize(synth_log_path, self.environ)\n  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 119, in synthesize\n    synth_proc.check_returncode()  # Raise an exception.\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode\n    self.stderr)\nsubprocess.CalledProcessError: Command \'[\'/tmpfs/src/github/synthtool/env/bin/python3\', \'-m\', \'synthtool\', \'--metadata\', \'synth.metadata\', \'synth.py\', \'--\']\' returned non-zero exit status 1.\n'

Google internal developers can see the full log here.

@alexander-fenster or @xiaozhenliu-gg5, could you PTAL?

Looking

Release of v2.4.1 has failed which caused synth failures:
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

I released v2.4.1 manually.


[Bug]:  usage not working for GPTAssistantAgent?

Describe the bug
When calling get_actual_usage() on a GPTAssistantAgent I get
No usage summary. Please call "create" first.

even though on the OpenAI platform I can see the threads and associated token.
Steps to reproduce
call :
agent.get_actual_usage()

with agent being GPTAssistantAgent
Model Used
gpt-4o-2024-05-13
Expected Behavior
agent.get_actual_usage()
should return something like:
{'total_cost': 0.01265,
 'gpt-4o-2024-05-13': {'cost': 0.01265,
  'prompt_tokens': 1273,
  'completion_tokens': 419,
  'total_tokens': 1692}}

(Sorry if I am missing something!)

I found a way to retrieve the usage info, by modifying def _get_run_response(self, thread, run) in autogen/agentchat/contrib/gpt_assistant_agent.py
See https://github.com/CMBAgents/autogen/commit/5f360e551505bbe5ae2ba17eb204e3f92dd406cb


added 'view' attribute to zone_auth setter

Small change to add the 'view' parameter to the zone_auth resource.

Thanks!  This was released in version 1.0.1.


Allow file based configuration

Similar to https://github.com/google/trillian/pull/620
And (if not resolved by #578): frontend.go should read the actual PEM file (see https://github.com/google/keytransparency/pull/578#discussion_r120088973)
@gdbelvin proposed using https://github.com/namsral/flag

At the moment, we're not seeing a strong demand for this.  We can reopen at a later point if interest comes around.


Setup.py is supposedly deprecated

I used this to generate PKGBUILDs for two python modules, cs50 and submit50. However upon installing the packages, I get the below terminal output:

The package installations still seemed to complete anyway, but I thought maybe I should post this here just in case.

Actually, pip2pkgbuild does support generation of PEP517 (the pypa/build, pypa/installer staffs mentioned in your screenshot) based PKGBUILD by the --pep517 option. But, it will only generate such PKGBUILD if there's a pyproject.toml file provided by the Python module, according to the wiki.
However, after I tried, it seems pypa/build and pypa/installer can even deal with modules without the TOML file. So, I will release a new version to remove the verification logic of the --pep517 option.

looks like 0.3.4 still try to use setup.py.
A solution could be this in PKGBUILD:
in build():
if [ -e setup.py ]; then
python setup.py build
else
python -m build --wheel --no-isolation
fi
and in package():
if [ -e setup.py ]; then
python setup.py install --root="${pkgdir}" --optimize=1 --skip-build
else
python -m installer --destdir="${pkgdir}" dist/*.whl
fi


fix: use np.int64 and np.float64 instead of deprecated np.int and np.float

Fixing the following error:

AttributeError: module 'numpy' has no attribute 'int'.
np.int was a deprecated alias for the builtin int. To avoid this error in existing code, use int by itself. Doing this will not modify any behavior and is safe. When replacing np.int, you may wish to use e.g. np.int64 or np.int32 to specify the precision. If you wish to review your current use, check the release note link for additional information.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

@thakur-nandan, please take a look at this fix, without it, some models do not work with new versions of numpy (such as SPARTA).
I attached the error in the description.


how to input --cucumberOpts.tags with multiple tags with And relationship

Equivalent in conf.js file will look like:
cucumberOpts: {
tags: ['@dev', '~@ignore']
}
I am trying something like --cucumberOpts.tags="@dev&&~@ignore" or  --cucumberOpts.tags="['@dev','~@ignore']"
None of it seems to work.  Do we support multiple tags input from commandline?

I think this is now a grunt question, so I'm going to close. Please ask on stack overflow or a more appropriate grunt forum. Thanks!

just stumbled on this. The OP is encountering a grunt bug which is fixed in grunt 1.X , which was released a couple months ago. HTH

Since this is the first relevant google hit for the subject and I have a feeling myself or someone else might end up here in the future:
This is what I'm ended up using doing with an integration-test grunt registered task, where I'm setting a bunch of process.env and passing the values to the grunt-protractor-runner module with my CLI input as grunt integration-test -tags=@wip,@kian. Note that from what I can tell before diving further that the grunt-protractor-runner is using AND logic on the CLI passed in tags, so it works great if you want to AND NOT (@kian,~@wip), but as great for IN/LIKE logic.
//$ grunt integration-test -tags=@wip,@kian

//Collect tags from CLI or specify elsewise.
if(grunt.option('tags') != undefined) cukeTags = grunt.option('tags'); //Tags from CLI
//else cukeTags = ["~@cleanup","~@wip"]; //Just my local usecase if I don't want to run "all"
else cukeTags = false; //Run everything in the suite

//Throw tags into an array if they exist and aren't an array.
if (!Array(cukeTags) && cukeTags != false && cukeTags != undefined && cukeTags.includes(',')) cukeTags = cukeTags.split(',');

//Set tags for grunt-protractor-runner to consume
grunt.config.merge({protractor: {options: {args: {cucumberOpts: {tags: cukeTags} }}}});

//Run protractor based off standard grunt-protractor-runner task config.
grunt.task.run(['protractor:e2e']);


add JANet doc

remove some aliases' docs

@muuki88 Hello Nepomuk. COuld you please advise when we can expect this to be merged?

Thanks for the reminder 😊

@muuki88 Thank you


:sparkles: surgical mask relative to Covid-19 period

Close #1
Name: Surgical Mask
Category: Mouth

Any chance for this PR to be merged ?

Thanks for the PR


Fix add-action opts bug + test

So not all of the top level opts such as basePath per docs are getting merged into _opts in addAction. The following PR should fix it by missing both of them, also adding a test since addAction was missing coverage.
A few other things (maybe worth opening an issue for) - one thing I'm not a huge fan of is the large dynamic function definition in addAction, it may be nicer to have a static function and either bind, or store some of the default arguments to be passed to it.
Another is that addAction is a function in an extension that relies mapper / store introspection to be correct. Would a more general path-way to to allow action: {} definitions in the mapper which the applied / registered adapters be allowed to absorb into their own actions without requiring them to introspect the core framework?

Another point - should the action return an object if a mapper is specified in options? Currently it's hard for me to tell that there is much advantage to using addAction over declaring a function on the mapper manually e.g.
    login(username, password) {
      return adapter.POST('auth/token/', { username: username, password: password })
        .then((response) => {
          this.setupAuthToken(response.data.token)
        })
    },

I personally just add my own functions to mappers, but a lot of people clamored for this declarative HTTP action syntax.

Current coverage is 93.47% (diff: 100%)

Merging #56 into master will increase coverage by 0.14%

@@             master        #56   diff @@
==========================================
  Files             1          1
  Lines            45         46     +1
  Methods           7          7
  Messages          0          0
  Branches          6          6
==========================================
+ Hits             42         43     +1
  Misses            3          3
  Partials          0          0

Powered by Codecov. Last update 9d8ca3a...e85f722

More tests #56


Spring cleaning

+1

It's already winter, but anyway +1

@bmwiedemann @jdsn opinions?

:+1:  (assuming that it works)


fix: update intro_multimodal_rag_utils.py to support PDFs with blank pages

PDFs with blank pages generate errors. Fix the support to process PDFs with blank pages.
Description
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Follow the CONTRIBUTING Guide.
[ ] You are listed as the author in your notebook or README file.

[ ] Your account is listed in CODEOWNERS for the file(s).

[ ] Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
[ ] Ensure the tests and linter pass (Run nox -s format from the repository root to format).
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

imports making the lint failing are updated by owl-bot ... how can i fix it?

I need to disable the ISORT check. Don't worry about the other lint errors.


APP UI: APP Platform Settings should read "APP Settings"

[Version]
17.0 2017/05/15 (bugfix branch, including issue #677)
[How to reproduce]

go to http://estsdehn.intern.est.fujitsu.com:8880/oscm-app/

[Expected result]
The title of the section for updating the APP cfg settings is "APP Settings"
[Observed result]
The title is "APP Platform Settings"
[Details]
Since APP is the abbreviation for Asynchronous Provisioning Platform, the "Platform" in the title is superfluous.

This seems to have been changed already to APP Controller Configuration in the latest version. @gertipoppel Is this acceptable?

My bad. Comment made about previous version of APP. Will fix now.

Checked on Windows Server 2016, jdk1.8u121, build BES_MASTER_UNIT-1778 2017/06/29 (Official 17.2.0) in Saml mode. Now the title is "APP Settings".


Create LICENSE

Add Apache License to it

Thanks :) just though about the same.
Will add headers to the scripts later ....


Delete article

These are instructions for Service Panel and not relevant anymore

The build is failing, because there's a reference to this doc from docs/about-hypernode/billing/billing-faq-for-the-service-panel.md:49.


Tests and pypi

Hi,
This is the public standalone assembly uploade for review @Ge94 . I have edited the scripts and added two unit tests. Would appreciate your opinions. Couple of queries:

Unsure how to test the study registration as this requires webin credentials
I have added files to make this a python package. Will need some guidance on how to register this and then can change the installation from a condo env to a pip install hopefully.

@mberacochea

Overall the structure looks OK. Are there any specifics? I left you some small comments.

I had to import with the script location for the tests to work.
https://github.com/EBI-Metagenomics/assembly_uploader/blob/10e0d51bfb23ddc13116b99d7c801f6ac45b8ac4/assemblyuploader/study_xmls.py#L7
However I get this error after installing the python package now. That was the only bit I was not sure how to fix.
  File "/Users/vkale/miniconda3/envs/assemblyuploader/bin/study_xmls", line 5, in <module>
    from assemblyuploader.study_xmls import main
ImportError: cannot import name 'main' from 'assemblyuploader.study_xmls' (/Users/vkale/miniconda3/envs/assemblyuploader/lib/python3.8/site-packages/assemblyuploader/study_xmls.py)

The code looks good for me too. My only other doubt is about testing the study registration. If I understood correctly it's better not to test behaviours what we can't predict (e.g. ENA API failing) - could we skip the registration and use a mock registration output file to test subsequent steps? Does it make sense @mberacochea ?

The code looks good for me too. My only other doubt is about testing the study registration. If I understood correctly it's better not to test behaviours what we can't predict (e.g. ENA API failing) - could we skip the registration and use a mock registration output file to test subsequent steps? Does it make sense @mberacochea ?

Sorry, I didn't see this message. We should mock the ENA API, and create failure scenarios to test our code response to that. We should also create mocks for valid responses

OK. I've added Github Actions to this one.


librespot / spotify connect failing on FiiO USB DAC

I know librespot support is beta, so I don't expect a fix, but putting this here in case some else finds a way to fix this and can help me out.
RUST_BACKTRACE=1 /opt/librespot/librespot -n MusicBox -u snip -p snip  --onstart /usr/bin/mpc stop -v -b 320  --device plughw:1
[snip]
INFO:librespot::util: Exit status: exit code: 0
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', /checkout/src/libcore/option.rs:329
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
TRACE:librespot::audio_file: chunk 6 / 92 complete
TRACE:librespot::audio_file: requesting chunk 7
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:511
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:495
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:471
   8: core::panicking::panic_fmt
TRACE:librespot::audio_file: chunk 7 / 92 complete
TRACE:librespot::audio_file: requesting chunk 8
             at /checkout/src/libcore/panicking.rs:69
   9: core::panicking::panic
             at /checkout/src/libcore/panicking.rs:49
  10: <librespot::audio_backend::alsa::AlsaSink as librespot::audio_backend::Sink>::start
  11: librespot::player::PlayerInternal::run
  12: std::panicking::try::do_call
  13: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  14: <F as alloc::boxed::FnBox<A>>::call_box
  15: std::sys::imp::thread::Thread::new::thread_start
             at /checkout/src/liballoc/boxed.rs:650
             at /checkout/src/libstd/sys_common/thread.rs:21
             at /checkout/src/libstd/sys/unix/thread.rs:84
DEBUG:librespot::player: drop Player[0]

When I switch to --device plughw:0 it works on the default pi soundcard (which I guess I could connect up to my amp on different channel and use that awaiting a fix). (temp fix in /opt/musicbox/startup.sh for now).
I thinks it's something to do with librespot trying to talk S16_LE and my DAC only supporting (or only announcing) SE32_LE see https://github.com/plietar/librespot/issues/162
root@MusicBox:/cf# cat /proc/asound/DAC/pcm0p/sub0/hw_params
access: RW_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 44100 (44100/1)
period_size: 441
buffer_size: 8820
root@MusicBox:/cf# cat /proc/asound/DAC/stream0
SmartAction FiiO USB Audio Class 2.0 DAC at usb-3f980000.usb-1.2, high speed : USB Audio

Playback:
  Status: Stop
  Interface 1
    Altset 1
    Format: S32_LE
    Channels: 2
    Endpoint: 1 OUT (ASYNC)
    Rates: 32000, 44100, 48000, 88200, 96000, 176400, 192000
    Data packet interval: 125 us

maybe some sort of fix lies in https://github.com/rickyzhang82/bit_perfect but I don't get it (yet).

Are you sure it's the same issue? It doesn't have the same sample format error message and alsa's plughw should solve that anyway (as per the linked issue). The log looks more like it handled a few chunks ok and then something went wrong on the 8th one. My rust experience is in its infantcy (and only due to what I've tried to understand in librespot) so maybe I'm wrong. Unfortunately it's no longer actively maintained so we might have to work this out between us.

Try a recent kernel (4.14.x), looks like there had been a bug which was fixed. Pulseaudio went into D state every time as soon as I plugged in the DAC while working with ALSA just fine, now it all works as supposed.


Add checks for users, isolated logic

Could you rebase this on the current master and look at the failing tests? The former may fix the latter :)


reghdfe_store_alphas is unrecognized

When I run the sample code in Readme with option to save fixed effect, there's an error message saying the command reghdfe_store_alphas is unrecognized.
I've downloaded the latest version from Github, and the codes are below. Thank you!
. sysuse auto, clear
(1978 Automobile Data)

. ivreghdfe price weight, absorb(trunk, save)
(dropped 5 singleton observations)
(MWFE estimator converged in 1 iterations)
command reghdfe_store_alphas is unrecognized
r(199)

. which reghdfe
*! version 5.7.1 20mar2019

. which ivreghdfe
*! ivreghdfe 1.0.0  07jul2018
*! this just adds absorb() to this code:
*! ivreg2 4.1.10  9Feb2016
*! authors cfb & mes
*! see end of file for version comments

resolved?

Has there been an update? This error still occurs.
`
. which reghdfe
c:\ado\plus\r\reghdfe.ado
*! version 5.7.1 20mar2019
. which ivreghdfe
c:\ado\plus\i\ivreghdfe.ado
*! ivreghdfe 1.0.0  07jul2018
*! this just adds absorb() to this code:
*! ivreg2 4.1.10  9Feb2016
*! authors cfb & mes
*! see end of file for version comments
`

Can you try with the commit I just added? It works on my side.

Ah, sorry. Didn't see that there was another branch. I tried reinstalling from there and it looks like it works now!

I am sorry what must I do to get it working? sorry for the noob questions... but someone has gotta ask them ? :(

I just added a new version to github. So uninstalling and reinstalling from there should so the trick.

@pxv148 run the following in stata:
cap ado uninstall ivreghdfe
net install ivreghdfe, from(https://raw.githubusercontent.com/sergiocorreia/ivreghdfe/mead/src/)

Thank you!


build fails when using prerender

Trying out the prerender plugin with version 2.8.1, I cannot get the build to pass.
x Build failed in 407ms
error during build:
TypeError: [preact:prerender] d is not a function
    at i (file:///<repo>/node_modules/@preact/preset-vite/headless-prerender/prerender-DWVaPvWr.js:1:262)
    at Module.g (file:///<repo>/node_modules/@preact/preset-vite/headless-prerender/prerender-DWVaPvWr.js:1:437)
    at file:///<repo>/node_modules/@preact/preset-vite/headless-prerender/main-DSgznFuN.js:1:16171

See repro: https://stackblitz.com/edit/vitejs-vite-ybgooe?file=src%2Fmain.jsx,vite.config.js&terminal=build

Can you reproduce outside of stackblitz?

Sorry for the headache!


Chore: add analytics to sponsor links on home page

Small PR adding some Google Analytics events to the sponsor links on our home page. I'm not seeing the events fire locally (I'm actually not seeing any analytics requests going out), and I'm assuming that's due to it the requests not originating at eslint.org. Would love confirmation though!

Yes, I think that's because of the third attribute when initializing ga points to eslint.org domain. I think we can merge it, and I can check it in GA console, we can always change it if it doesn't work correctly.

There was a failure yesterday too that was fixed by a re-run. Will run the deploy-preview deploy once more.


Updating kube-capacity dependencies, bumping version to v0.4.0

This should fix #20, #24, and #27.

Looks like this diff was too big for Codacy, oh well...


[release/1.6] Prepare release notes for v1.6.21

Welcome to the v1.6.21 release of release tool!
The twenty-first patch release for containerd 1.6 contains various fixes and updates.
Notable Updates

**update runc binary to v1.1.7 (#8450)
**Remove entry for container from container store on error (#8456)
**oci: partially restore comment on read-only mounts for uid/gid uses (#8403)
**windows: Add ArgsEscaped support for CRI (#8247)
**oci: Use WithReadonlyTempMount when adding users/groups (#8357)
**update go to go1.19.9 (#8469 )
**archive: consistently respect value of WithSkipDockerManifest (#8345)

See the changelog for complete list of changes
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors

Sebastiaan van Stijn
Derek McGowan
Iceber Gu
Kirtana Ashok
Justin Chadwell
Phil Estes
Akihiro Suda
Djordje Lukic
Kazuyoshi Kato
Mike Brown
Wei Fu
kiashok

Changes
25 commits

da91c3b07 Add release notes for v1.6.21
[release/1.6] update go to go1.19.9 (#8469)

39566aade [release/1.6] update go to go1.19.9

[release/1.6] fix the task setting the runtime path (#8454)

e8840f688 skip TestContainerStartWithAbsRuntimePath if the runtime is v1
75ab094de integration: add container start test using abs runtime path
f49254f0b WithRuntimePath uses the TaskInfo.RuntimePath field

[release/1.6 backport] update runc binary to v1.1.7 (#8450)

ccb51ff26 update runc binary to v1.1.7

[release/1.6] Remove entry for container from container store on error (#8456)

95d31551d Remove entry for container from container store on error

[release/1.6 backport] oci: partially restore comment on read-only mounts for uid/gid uses (#8403)

c33eb574d oci: partially restore comment on read-only mounts for uid/gid uses

[release/1.6 ] Add ArgsEscaped support for CRI (#8247)

bc2e01303 Fix argsEscaped tests
8b81d5acc Add ArgsEscaped support for CRI

[release/1.6 backport] update runc binary to v1.1.6 (#8385)

57d953482 update runc binary to v1.1.6

[release/1.6 backport] oci: Use WithReadonlyTempMount when adding users/groups (#8357)

fb5e663d0 oci: Use WithReadonlyTempMount when adding users/groups

[release/1.6] update go to go1.19.8 (#8353)

26efb8fd5 [release/1.6] update go to go1.19.8

[release/1.6] archive: consistently respect value of WithSkipDockerManifest (#8345)

ec13b497e export: add test for WithSkipDockerManifest
d1f3771c4 archive: consistently respect value of WithSkipDockerManifest

Dependency Changes
This release has no dependency changes
Previous release can be found at v1.6.20

@dmcgowan @dcantah could you please take a look when you have some time? Thanks!

This needs a bump to 1.6.21 https://github.com/containerd/containerd/blob/release/1.6/version/version.go#L26

Might wanna wait for this actually https://github.com/containerd/containerd/pull/8454

Might wanna wait for this actually #8454

This PR has been checked in. Updated this PR to include this change and contributor

Still need to add this file to the commit with the version bump:

This needs a bump to 1.6.21 https://github.com/containerd/containerd/blob/release/1.6/version/version.go#L26

resolved this!

Did we update the Go version to latest? There was a release Yesterday

opened https://github.com/containerd/containerd/pull/8469

opened [release/1.6] update go to go1.19.9 #8469

Do we want to block this PR on go version update?

I would personally consider making sure not to do a release with a go version that has CVE's attached (even though the actual CVE's wouldn't affect containerd).
There's also some fixes for compiler issues in the go1.19.9 release. We just received reports of random panics in Docker, which could be related to a bug in go1.19.8; see https://github.com/moby/moby/issues/45454

I think we can probably merge the Go update in the next few hours; in that sense I don't think it is really holding up the release if we get it in today. I agree with @thaJeztah that it's easier to just make sure we are on the latest Go release that has CVE's associated with it to keep from complaints that we are using a runtime with known CVEs (even though we know containerd is unaffected)

I normally avoid putting mention of go updates into the release notes unless it has a relevant since it can be a bit of a moving target. Without, easy to just release with or without it merged and not worrying about updating this every time. Its easier to get these PRs merged quicker so it doesn't need a constant update. Think just remove the mention and we'll merge and do the release when the Go update is merged.

Ah, yes, that's fine with me; my comment was mostly "don't release before updating"; not specifically tied to including it in the changelog

I normally avoid putting mention of go updates into the release notes unless it has a relevant since it can be a bit of a moving target. Without, easy to just release with or without it merged and not worrying about updating this every time. Its easier to get these PRs merged quicker so it doesn't need a constant update. Think just remove the mention and we'll merge and do the release when the Go update is merged.

updated PR!

@estesp the test failures here don't seem to be related to the changes being made here and I remember they passed earlier. Could you please help restart these tests? Thanks!

One thing I forgot to mention (but should probably not be a blocker) is that go1.19.9 should resolve the issue where the soft-limit was discarded by Go, and set to the hard-limit;  https://github.com/containerd/containerd/pull/7566#discussion_r1150907094

do we need more sign offs for this PR to be merged? We are trying to get a new release out based on v1.6.21, so wanted to check :)

@dcantah if you have some time would you be able to take a look please? Thanks!


Link to repo in readme

Hey Phil - thanks for building this. :) Just an FYI - found the image on docker hub, which mentioned "The docker-compose.yml file in this repository" but no link. Might be helpful to folks to add a href...

Will do on my next update :)


error on load with RNW

I will added later a repoductible repo

Okay @lobor  I'd really need a repro to be able to approach this correctly, waiting on that

Same issue is happening here :/
expo: 50.0.13
react native: 0.73.5
Example:
export default function HistoryFilters() {
  const ref = useRef<BottomSheetMethods>(null);

  return (
    <View>
      <BottomSheet
          ref={ref}
          closeOnDragDown={true}
          animationType='slide'
          backdropMaskColor='#000000'
        >
          <Text>
            The smart 😎, tiny 📦, and flexible 🎗 bottom sheet your app craves 🚀
          </Text>
        </BottomSheet>
    </View>
  );
}

export default function HistoryPage() {
  return (
    <View>
      <Text>=)</Text>
      <HistoryFilters />
    </View>
  );
}

hi, how to config for react js webpack? i have equal error


Make gpr_timespec platform agnostic.

-- timespec.tv_sec to gpr_int64
-- timespec.tv_nsec to gpr_int32
Creating pull request for initial review and to run tests.

@ctiller  and @nicolasnoble  to take a look for general sanity & feasibility.

This is ready for review.
FYI @soltanmm, @murgatroid99, @jcanizales, @stanley-cheung

Not sure if h2_proxy_simple_request_test failure is related to this change or not.


Write failed queries to log and in the exception

Failed queries are shown with placement variables in the Exception:
Unable to execute UPDATE statement [UPDATE payment SET receiver_id=:p1, date_changed=:p2 WHERE payment.id=:p3]

That makes it often hard to see what went wrong.
To see the database error, you have to check the log:
Error: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'receiver_id' cannot be null

The query did not go to the log, but at least it is possible to puzzle together what went wrong.
However, there is a nice formatter available, which writes full queries to the log.
This PR does three things:

Show full query and SQL error in the exception
Write queries to log, even if they fail
Fix an error in PdoConnection::exec() (see below)

New Exception message looks like this:
Unable to execute statement [UPDATE payment SET receiver_id=NULL, date_changed='2021-04-28 22:15:55.450739' WHERE payment.id=1491]
Reason: [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'receiver_id' cannot be null]

And when going to the log, you see the offending query right above the error message.
Just looking at the changed lines of code, this rabbit hole was deeper than expected.
ALSO
I fixed an error in PdoConnection::exec(). This is likey not a big deal, since it only fixes something that was broken, but you might want to check because of backwards compatibility, hence the double highlighting.
The PdoConnection::exec() method wraps PDO::exec(), which, according to the manual "does not return results from a SELECT statement". Instead, it returns the number of affected rows.
However, in PdoConnection, that returned int was wrapped into a DataFetcher, which only works with result sets. So now you can call fetch() on an int and admire the exception. I think you can call DataFetcher::getDataObject() to get the int back, but it is an ordeal, let alone confusing.
So I removed the DataFetcher and have PdoConnection::exec() return the int from PDO::exec() directly. If someone went the extra mile to get to the return value using DataFetcher::getDataObject(), that does not work anymore.
I thought about putting this into its own PR, but it meant immediate merge conflicts with this one.

Ok, apparently so database systems return a prepared statement even when the query is faulty (MySQL) and others don't (SQLite, Postgres). However, a prepared statement is needed to get the full query for the exception message. This isn't a problem in itself, because if your query syntax is broken, you do not need to see the values. Those are only interesting when the execution failed, for example due to a constraint violation.
But I had to take apart the tests that checked if an exception is thrown, and that the exception contains the query. This is now done independently, so it can be checked independent of platform.
While trying out stuff to go around the issue, I refactored some lines in Criteria::doUpdate(). I left those changes in, even though they are not related to the objective of this PR, simply because it is an improvement. Hope that is alright.

@stereomon We would need to make sure that the additional (useful) data is only added in development mode, rather than production mode maybe.

Hey @stereomon, that's a good point, hadn't thought of that. I like @dereuromark's idea, to be careful in production mode, but helpful in development/debug mode.
So now the exception message in prod mode is the exact same as before, and in dev mode you get full query and SQL error message. Do you think this will work?

Codecov Report

Merging #1727 (52d6276) into master (cc16d3d) will decrease coverage by 14.58%.
The diff coverage is 6.66%.

@@              Coverage Diff              @@
##             master    #1727       +/-   ##
=============================================
- Coverage     88.27%   73.68%   -14.59%
- Complexity     7714     7717        +3
=============================================
  Files           262      262
  Lines         22131    21997      -134
=============================================
- Hits          19536    16209     -3327
- Misses         2595     5788     +3193

Flag
Coverage Δ
Complexity Δ

5-max
73.68% <6.66%> (-14.59%)
7717.00 <5.00> (+3.00)
:arrow_down:

7.4
73.68% <6.66%> (-14.59%)
7717.00 <5.00> (+3.00)
:arrow_down:

agnostic
73.68% <6.66%> (+<0.01%)
7717.00 <5.00> (+3.00)

mysql
?
?

pgsql
?
?

sqlite
?
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cc16d3d...52d6276. Read the comment docs.

I decided to split this into two PRs, to make it more manageable. This PR contains the changes to the exception output that we have been discussing.
Remote branch name doesn't make sense now, but I don't think I can change the branch name of a PR (can I?), and I don't want to lose the discussion.

I'm fine with the separation for dev and prod.
Thank you for your effort!


Add hardware STL files

I think there were 2 STL files: the arm and the cradle. We should add them both!
...would it be useful to put them in their own "STL" directory, rather than mixed in with the Python? I can go either way.

 How's this?


Union index is zig-zag long

The avro spec says that a Union value is encoded by first encoding the index of the Union entry as a long--meaning zig-zag encoded.  In decode.rs, it reads the index as a single byte, directly encoded as an integer.  I think this change needs to be made:
diff --git a/src/decode.rs b/src/decode.rs
index 28980c2..f43005d 100644
--- a/src/decode.rs
+++ b/src/decode.rs
@@ -112,12 +112,11 @@ pub fn decode<R: Read>(schema: &Schema, reader: &mut R) -> Result<Value, Error>
             Ok(Value::Map(items))
         },
         &Schema::Union(ref inner) => {
-            let mut buf = [0u8; 1];
-            reader.read_exact(&mut buf)?;
+            let index = zag_i64(reader)?;

-            match buf[0] {
-                0u8 => Ok(Value::Union(None)),
-                1u8 => decode(inner, reader),
+            match index {
+                0 => Ok(Value::Union(None)),
+                1 => decode(inner, reader),
                 _ => Err(DecodeError::new("union index out of bounds").into()),
             }
         },

I guess there's also a parallel change that needs to be made on the encode side...

Actually I think there's a second bug in the code above, I think the second case in match needs to be:
                1 => decode(inner, reader).map(|x| Value::Union(Some(Box::new(x)))),

Good catch!
Given you have it already almost all figured out, would you feel comfortable opening a PR to fix this? 🙂


[Bug]: @page reference doesn't seem to work

Plugin
@knodes/typedoc-plugin-code-blocks
Typedoc plugin(s) version(s)
@knodes/typedoc-plugin-pages": "^0.23.1
Typedoc version
typedoc": "^0.23.27
Describe the problem
Created a simple structure like this:
pages
    |--- test.md
    |----test2.md

In my typedoc.json, I specified "readme": "./pages/test.md"
My plugin config is just:
    "pluginPages": {
      "pages": [
        { "title": "test", "source": "test.md" }
      ]
    }

When I run typedoc, I get:
error [@knodes/typedoc-plugin-pages]: MarkdownPagesLinks ⇒ In "pages/test.md:3:1 (in expansion of @page)", could not resolve page "./test2.md[Test" from reflection test

All I am trying to do is that I have a set of existing MD files (about 30 of them) which have explanations of core topics for the package.  They live under ./docs but I changed that to ./pages b/c it seems like that's what this plugin wants?
Those markdown (before) just had regular md links like [Test](./test.md), but that style of link doesn't seem to work here.
Any ideas what I'm doing wrong?
What did you expected ?
I expect to be able to have my own existing markdown files, which reference other markdown files in the same folder.

AH, I figured it out.
It needs to be:
test.md
{@page ./test2.md Link to Test 2}
config in typedoc.json
"pages": [
        { "title": "Test 2", "source": "test2.md" }

But this means I need one entry in pages for EVERY markdown file I already have?  And EVERY markdown file's links need to be updated to use the @page format?
This also means when I add a new markdown, I have to update "page" config in typedoc.json?
This feels pretty cumbersome.  Is there no way to bulk include all my markdowns?  Or have it scan or something?

Sorry, one more comment:  Images referenced in markdown as in ` also do not seems to work in the generated documentation.
Is there some equivalent directive like @page but for images?  I tried @Img, @img, @Image, and @image, but all are unrecognized.  How to reference images then?

Yeah the declarative format of pages is boring. I got a full rework of this system somewhere so that there is no need to modify the config when adding new pages, but I don't have the time to finalize & release it.


Updating user avatar does not update the avatar on the settings page

While trying to update my user avatar, I noticed that as I uploaded a new avatar, the settings page still shows the old avatar. On closing it though, my avatar has been successfully changed, and on opening the settings page the new avatar is displayed.

Thanks for the report!  Seems like a likely regression in the recent work we've done on that page.
@rheaparekh @YJDave one of you want to work on this?

@timabbott can i take this issue?

@dgarvit I have already solved this issue, while debugging. Sorry for inconvenience.

Here is the PR #8688, though you can review and try it out :)


fix(cd): workflow variable usage

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.053%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3910

Relevant Lines:
5280

💛  - Coveralls


Could you deploy a sources jar to maven along with the executable jar?

Would it be possible to build and deploy a sources jar along with the execution jar when you deploy to the maven repository?  Having the source makes it easy to debug and follow the code during execution.
Its pretty easy, just add the sources plugin section (link below) to the pom file and it'll create the sources jar when you run package.
https://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html

Please, create a PR with the changes, and I will accept it ASAP.


Add a golang implementation.

Hi @brendanburns, Nic here from HashiCorp, this looks super interesting would love to help out in my spare time.


XCGlogger output truncated when app crashes right after

Hi,
Just before a point where the app will crash, I have a log.verbose() line, which gets truncated:
2014-11-21 09:19:58.095 [Verbose] [MyViewController.swift:121] listDataCallback(_:response(lldb)
To compare, I added a println() and that gets printed out fine.

I've now added a XCGNSLogDestination log destination class that uses NSLog and is thus thread safe (though not as customizable). You should now use that class in cases where you're chasing a crash like that. This won't be an issue in Swift 2.0, since print() now appears to be thread safe.