Investigate performance regression

Since about two days ago, our nightly jobs went from taking about 30 minutes to about two hours. It seems that this is mostly being driven by int_clearinghouse__detector_agg_five_minutes_with_missing_rows, and the most likely culprit is something to do with #408
@kengodleskidot and @mmmiah, do you know what might be going on there?

Ah, great, thanks @JamesSLogan

When updating this model in #408, I believe the most time-consuming step is in the spine CTE where we join the 5-minute time intervals with the detector. If there is a way to limit this join to the same timeframe as the detector_agg CTE that would drastically reduce the time to process this model.


The --version flag is passed to nvim, so it is not a way to figure out version of neoray

Operating System or distro: Ubuntu
neoray version: master branch for today, hard to figure out :)

Describe the bug
--version flag is passed to nvim, it  probably prints version to stdout and exits, but neoray still tries to establish rpc session with it.
I would expect it to output version of nvim.
Steps to reproduce
Just start it with --version and observe error logs:
tbunyk@ZALANDO-33620:~/projects/neoray$ bin/neoray_debug --version
[DEBUG] [NVIM] Neovim started with command: nvim --embed --version
[ERROR] [NVIM] Failed to get api information: msgpack/rpc: session closed
[ERROR] [NVIM] Failed to set client information: msgpack/rpc: session closed
[ERROR] [NVIM] Failed to execute scripts.vim: msgpack/rpc: session closed
[FATAL] [NVIM] Attaching ui failed: msgpack/rpc: session closed

:+1:


PINT compatibility

So here is a first stab at PINT compatibility. I have re-factored pulsar.py to have a base BasePulsar class that has all of the standard properties that the user calls, then I have Tempo2Pulsar and PintPulsar that inherit BasePulsar and get the needed information from either a libstempo instance or from a TOA and TimingModel instance depending on whether or not you are using tempo2 or PINT.
From this I now have a function Pulsar that you initialize a Pulsar class from. It has the same API as the old Pulsar class except it now has an extra argument timing_code, which defaults to tempo2. You can also initialize this with the usual par and tim file, or you can initialize it with libstempo or PINT objects.
One reason for doing things this was is that the Tempo2Pulsar and PintPulsar classes act as a bridge between codes. Here we have a way for enterprise to call either code but now libstempo or PINT could call enterprise by initializing these classes internally.
I have to set up more tests but this is coming along. Also speaking of tests, I switched from using setUp to setUpClass in the unit tests since setUp is called every time a test function is called whereas setUpClass is called only at the beginning of each test case. This takes the test runtime down to a few minutes from what was about 20 minutes.

Ok I've been doing some comparisons of PINT and tempo2 just in terms of the data and the likelihood when using each code, respectively. I think the first two plots are known to the PINT team and it has something to do with the ephemeris or the earth barycentering method.
Different in SSB frequencies. I admit that I may be using the wrong frequencies from PINT (model.barycentric_radio_freq? sounds right...). This is a very small difference since the units are MHz but you can see the yearly trend.

Difference in Residuals. Again you see the yearly trend and if this is removed I think you end up with the difference see in this PINT issue.

log10 relative error in log-likelihood with parameters drawn randomly from prior. This uses the 9-year B1855+09 data set with a full noise model (efac, equad, ecorr, red noise). Overall these are pretty small but I'm a bit surprised they aren't closer. We definitely need to figure this out!

Maybe some PINT people will be interested in this @scottransom.

If it's reproducing what PINT does, I think you should merge this.  We inherit PINT's known issue.
It's really troubling that some likelihood calls have >1e-3 relative error.  That's way more than roundoff... At the IPTA meeting this came up and some people brushed it off as single v. double precision.  This looks worse than that.

It's really troubling that some likelihood calls have >1e-3 relative error. That's way more than roundoff... At the IPTA meeting this came up and some people brushed it off as single v. double precision. This looks worse than that.

Thats why I don't want to merge it yet. There isn't anything obvious but I think there may be a bug somewhere. All the tests only test self consistency, in other words, they assume that the data in Pulsar is correct.

The plots are really interesting.  I suspect (as you mention) that the first two are the known issue (which we don't understand) about the tiny ephemeris differences.  I agree that fractional error differences as large as 1e-3 is worrisome, though!

Ok I took a look at what parameters correspond to the large difference in log-likelihood and it was for very small values of efac ~0.1. I think this makes sense because it exacerbates the differences i the residuals. In reality we will never have efacs that low. I re-ran with the lower prior range of 0.8 and I get something much more reasonable.

I've also done a run using the tempo2 residuals with everything else PINT and get log likelihood differences never more that 1e-7 so I think this all boils down to the residuals, it just varies with noise because that can make the difference more or less pronounced.


Can't reexport shared configuration

Problem
I want to share my postcss config across packages, so I created one package which just holds the config:
my-postcss-config-pkg/index.js
var prefixer = require('autoprefixer')({
  browsers: ['Explorer >= 11'],
})

module.exports = {
  plugins: [
    prefixer
  ],
};

In my app package I want to use it, so I created a postcss config there which just reexports the shared config:
app-pkg/postcss.config.js
module.exports = require('my-postcss-config-pkg');

but this actually doesn't prefix anything. I also tested it with wrapping autoprefixer with a log statement and it does indeed only get called for one file which contains nothing to prefix anyway.
I found out that I need to use Object.assign:
const config = require('my-postcss-config-pkg');
module.exports = Object.assign({}, config);

which makes totally no sense to me. Is this a bug?
Environment
Please provide information about your environment.

OS
Node
npm
PostCSS

arch
6.3.1
3.10.3
postcss-loader 1.3.3

@hoschi Does the require() get resolved (Module Resolution)? Can you also post your webpack.config.js and where in your file tree you currently placed postcss.config.js? There is also {Object} notation for configs
postcss.config.js
const options = {
   autoprefixer: { browsers: ['Explorer >= 11'] }
}

module.exports = (ctx) => ({
   plugins: {
      "autoprefixer": options.autoprefixer
   }
})

where postcss-load-config loads the plugin(s), but tbh I have no idea if that works 😛
Could you also please use a CSS File where there would be definitely something to prefix or use another plugin ?
A small test repo with your current setup  for reproduction would be appreciated 🙃
This definitely needs to be supported by postcss-load-config and was intended to, but after the config file worked I got bit lazy 🤣 💯

Does the require() get resolved (Module Resolution)?

yep, I tried REPL and it looks good

Can you also post your webpack.config.js

See [1]

where in your file tree you currently place postcss.config.js?

app-pkg/postcss.config.js means app-pkg is the root folder of this NPM module

where postcss-load-config loads the plugin(s)

I had a lot of problems with other package which resolve stuff, so I try to use normal require as most as possible

Could you also please use a CSS File where there would be definitely something to prefix or use another plugin ?

I think you mean this sentence from me:
I also tested it with wrapping autoprefixer with a log statement and it does indeed only get called for one file which contains nothing to prefix anyway.
I have a bunch of SCSS files which some should be prefixed and some not. Using
module.exports = require('my-postcss-config-pkg');

then autoprefixer gets only called for one file (of say one hundred). This file doesn't contain anything to prefix, which is just a sidenote. But it should be called for each file, not only one. Using
const config = require('my-postcss-config-pkg');
module.exports = Object.assign({}, config);

calls autoprefixer for each file. If there is something to prefix or not is moot, so this is the expected behavior.

A small test repo with your current setup for reproduction would be appreciated

Do you have a starting repo with webpack and postcss already installed? I don't know how to start this.
[1]
'use strict';

// node core modules

// 3rd party modules
const webpack = require('webpack');
const HtmlWebpackPlugin = require('html-webpack-plugin');
const ExtractTextPlugin = require('extract-text-webpack-plugin');
const CustomizationResolverPlugin = require('customization-resolver-webpack-plugin');
const UglifyJsPlugin = require('uglifyjs-webpack-plugin');

// internal modules
const { DEVELOPMENT, PRODUCTION, FRONTEND_MODULE_NAME } = require('../constants');
const { makeBabelOptions, makeBabelInclude, makeBabelExclude } = require('./babel-config-utils');
const { stringToRegex } = require('../util');

const globalStylesRegex = /styles-global\/.*\.scss$/;

const entryHmr = [
  'webpack-hot-middleware/client',
  'react-hot-loader/patch',
];

const pluginsDev = [
  new webpack.DefinePlugin({
    'process.env': {
      NODE_ENV: JSON.stringify(DEVELOPMENT),
    },
    __BASENAME__: JSON.stringify(process.env.BASENAME || ''),
  }),
  new webpack.HotModuleReplacementPlugin(),
  new webpack.NoEmitOnErrorsPlugin(),
];

const pluginsProd = [
  // move common dependencies into entry chunk, when it reduces the feature chunk by more than 50%
  new webpack.optimize.AggressiveMergingPlugin(),
  // extract CSS into own file to load it in parrallel with JS.
  // Also prevents FOUC, which should only happen with SSR.
  // https://webpack.js.org/guides/code-splitting/#css-splitting
  new ExtractTextPlugin({
    filename: 'app.css',
    // extract CSS of main module into CSS file, other chunk embedd their CSS in JS files
    allChunks: false,
    // we use CSS Modules so we can ignore this
    ignoreOrder: true,
  }),
  // set production as current environment, needed by webpack itself to activate some optimizations
  new webpack.DefinePlugin({
    'process.env': {
      NODE_ENV: JSON.stringify(PRODUCTION),
    },
    __BASENAME__: JSON.stringify(process.env.BASENAME || ''),
  }),
  // needs to be there till webpack 3:
  // * https://webpack.js.org/guides/migrating/#uglifyjsplugin-minimize-loaders
  // * https://webpack.js.org/plugins/loader-options-plugin/
  new webpack.LoaderOptionsPlugin({
    // put loaders into minimze mode
    minimize: true,
    // remove debug stuff
    debug: false,
  }),
  // minification
  new UglifyJsPlugin(),
];

const sassLoader = {
  loader: 'sass-loader',
  options: {
    sourceMap: true,
    sourceMapContents: true,
  },
};

const rulesDev = [{
  test: /\.css$/,
  use: [
    'style-loader',
    {
      loader: 'css-loader',
      options: {
        modules: true,
        sourceMap: true,
        importLoaders: 1,
        localIdentName: '[name]__[local]__[hash:base64:5]',
      },
    },
    'postcss-loader',
  ],
}, {
  test: /\.scss$/,
  exclude: globalStylesRegex,
  use: [
    'style-loader?sourceMap',
    {
      loader: 'css-loader',
      options: {
        modules: true,
        sourceMap: true,
        importLoaders: 2,
        localIdentName: '[name]__[local]__[hash:base64:5]',
      },
    },
    'postcss-loader?sourceMap',
    sassLoader,
  ],
}, {
  test: globalStylesRegex,
  use: [
    'style-loader?sourceMap',
    'css-loader?sourceMap',
    'postcss-loader?sourceMap',
    sassLoader,
  ],
}];

const rulesProd = [{
  test: /\.css$/,
  use: ExtractTextPlugin.extract({
    fallback: 'style-loader',
    use: [
      'css-loader?modules&importLoaders=1&localIdentName=[name]__[local]__[hash:base64:5]',
      'postcss-loader',
    ],
  }),
}, {
  test: /\.scss$/,
  exclude: globalStylesRegex,
  use: ExtractTextPlugin.extract({
    fallback: 'style-loader',
    use: [
      'css-loader?modules&importLoaders=2&localIdentName=[name]__[local]__[hash:base64:5]',
      'postcss-loader',
      'sass-loader',
    ],
  }),
}, {
  test: globalStylesRegex,
  use: ExtractTextPlugin.extract({
    fallback: 'style-loader',
    use: [
      'css-loader',
      'postcss-loader',
      'sass-loader',
    ],
  }),
}];

function getLoaderQueryName(isDevelopment) {
  if (isDevelopment) {
    return '[path][name].[ext]?[hash]';
  }
  return '[hash].[ext]';
}

module.exports = function makeConfig(options) {
  const {
    isDevelopment,
    paths: {
      buildDir,
      customizationDir,
      customizationNodeModulesDir,
      file_frontendEntry,
      file_indexHtml,
      nodeModulesDir,
      srcDir,
    },
  } = options;

  const config = {
    entry: [
      // make babel-polyfill available for client code needed by
      // - runtime performance plugin transform-react-inline-elements
      // - redux-saga, because of the generators
      'babel-polyfill',
      // normal app entry point
      file_frontendEntry, // eslint-disable-line camelcase
    ],
    target: 'web',
    cache: isDevelopment,
    output: {
      path: buildDir,
      publicPath: '/',
    },
    module: {
      rules: [{
        test: /\.js?$/,
        include: makeBabelInclude(options.paths),
        exclude: makeBabelExclude(options.paths),
        use: {
          loader: 'babel-loader',
          options: makeBabelOptions(options),
        },
      }, {
        test: /\.txt$/,
        loader: 'raw-loader',
      }, {
        test: /\.(png|jpg|jpeg|gif|svg|woff|woff2)$/,
        use: {
          loader: 'url-loader',
          options: {
            name: getLoaderQueryName(isDevelopment),
            limit: 10000,
          },
        },
      }, {
        test: /\.(eot|ttf|wav|mp3)$/,
        use: {
          loader: 'file-loader',
          options: {
            name: getLoaderQueryName(isDevelopment),
          },
        },
      },
      ],
    },
    // NOTE:
    // - commons plugin is only needed when you have multiple entry points, which not using all of your main entry point.
    plugins: [
      // inject generated file names into HTML
      new HtmlWebpackPlugin({
        template: file_indexHtml,
        hash: false,
        // favicon: set favicon here,
        filename: 'index.html',
        inject: 'body',
        minify: {
          collapseWhitespace: false,
        },
      }),
    ],
    stats: {
      // Nice colored output
      colors: true,
    },
    // make absolute import statements possible, also for local modules
    resolve: {
      // json added because some NPM module try to load json files via "require('./package')" instead of "require('./package.json')"
      extensions: ['.js', '.json'],
      modules: [
        customizationDir,
        srcDir,
        nodeModulesDir,
        customizationNodeModulesDir,
      ],
      plugins: [
        new CustomizationResolverPlugin({
          customizationDir,
          sourceDir: srcDir,
          isCompleteFileName: /\.scss$/,
          // exclude node_modules but not frontend if it lies under this path
          excludePath: stringToRegex(`node_modules(?!/${FRONTEND_MODULE_NAME})`),
          excludeRequest: stringToRegex(`node_modules(?!/${FRONTEND_MODULE_NAME})`),
        }),
      ],
    },
  };

  if (isDevelopment) {
    // add entries for HMR, ORDER MATTERS
    config.entry = [].concat(entryHmr).concat(config.entry);

    config.plugins = pluginsDev.concat(config.plugins);
    config.module.rules = rulesDev.concat(config.module.rules);

    // no hashing for file names
    config.output.filename = '[name].js';
    // now, take your poison ......
    // enable source maps for chrome devtools, see
    // * https://github.com/webpack/webpack/issues/3165
    // * https://github.com/webpack/webpack/issues/2145
    // config.devtool = 'inline-source-map';
    // use 'eval' because of stacktraces in rebox only supported by this devtool, breaks HMR in most cases
    config.devtool = 'eval';
  } else {
    config.plugins = pluginsProd.concat(config.plugins);
    config.module.rules = rulesProd.concat(config.module.rules);
    config.output.filename = '[name].[chunkhash].js';
  }

  return config;
};

uhhh...😩 😛 This config is way to complex...I have a test enviroment for webpack yep 👍

Is your package on npm? (Link, Name)
Please narrow it down to just the CSS specific part (no "development/production", no plugins, ...), to make sure it's not related to your webpack setup :D
See below 😛

Package
package/package.json
{
   "name": "myPackage",
   "version": "1.0.0",
   "main": "index.js"
   "dependencies": {
       "postcss-plugin": "^1.0.0"
    }
}

package/index.js
module.exports = (ctx) => ({
   plugins: [
     require('postcss-plugin')(ctx.options.plugin)
   ]
})

Project
project/postcss.config.js
module.exports = (ctx) => require('myPackage')(ctx)

project/webpack.config.js
{
   test: /\.css$/
   use: [ 'style-loader', { loader: 'css-loader, options: { importLoaders: 1 } }, 'postcss-loader' ]
}

ok here you go:
git clone git@github.com:hoschi/postcss-load-config-issue-73-config.git config
git clone https://github.com/hoschi/postcss-load-config-issue-73-project project
cd project
npm install
npm install ../config
webpack

Gives me:
project > webpack
Hash: 0f7ed3ed8d2c7f7a0141
Version: webpack 2.3.1
Time: 405ms
    Asset     Size  Chunks             Chunk Names
bundle.js  15.9 kB       0  [emitted]  main
   [0] ./app/styles.css 1.05 kB {0} [built]
   [1] ./app/index.js 282 bytes {0} [built]
   [2] ./~/css-loader?{"importLoaders":1}!./~/postcss-loader!./app/styles.css 299 bytes {0} [built] [failed] [1 error]
   [3] ./~/style-loader/addStyles.js 8.51 kB {0} [built]
   [4] ./~/style-loader/fixUrls.js 3.01 kB {0} [built]

ERROR in ./~/css-loader?{"importLoaders":1}!./~/postcss-loader!./app/styles.css
Module build failed: TypeError: require(...) is not a function
    at module.exports (/home/hoschi/repos/postcss-load-config-issue-73/project/postcss.config.js:1:122)
    at /home/hoschi/repos/postcss-load-config-issue-73/project/node_modules/postcss-load-config/index.js:58:50
 @ ./app/styles.css 4:14-125
 @ ./app/index.js

Which I don't know why, have you an idea @michael-ciniawsky  ?

@hoschi #1

I changed the example repos to look like my setup from initial post and it works as expected in this minimal case:
project > webpack && cat dist/bundle.js  | grep block
Hash: c791c27d939007ea3ec1
Version: webpack 2.3.1
Time: 539ms
    Asset     Size  Chunks             Chunk Names
bundle.js  73.6 kB       0  [emitted]  main
   [0] ./app/styles.css 1.05 kB {0} [built]
   [1] ./app/index.js 282 bytes {0} [built]
   [2] ./~/base64-js/index.js 3.48 kB {0} [built]
   [3] ./~/buffer/index.js 48.6 kB {0} [built]
   [4] ./~/css-loader?{"importLoaders":1}!./~/postcss-loader!./app/styles.css 313 bytes {0} [built]
   [5] ./~/css-loader/lib/css-base.js 2.19 kB {0} [built]
   [6] ./~/ieee754/index.js 2.05 kB {0} [built]
   [7] ./~/isarray/index.js 132 bytes {0} [built]
   [8] ./~/style-loader/addStyles.js 8.51 kB {0} [built]
   [9] ./~/style-loader/fixUrls.js 3.01 kB {0} [built]
  [10] (webpack)/buildin/global.js 509 bytes {0} [built]
exports.push([module.i, ".foo {\n\tdisplay: block;\n\t-webkit-user-select: none;\n\t   -moz-user-select: none;\n\t    -ms-user-select: none;\n\t        user-select: none;\n}\n", ""]);

@hoschi If you have time and interest also try with {Object} Notation 😛 , I will do later when I have time 😄. Exporting an {Object}should also work but the the signature changes an you lose ctx
package/index.js
modules.exports = {
   plugins: [
      ...plugins
   ]
}

project/postcss.config.js
module.exports = require('package')

Can this be closed ? 🙃

the output from my last comment is already with object notation ;)
We can close this as it seems to be a problem of some combination in my setup. If I have more information on this I post it here.

Thanks for your help <3

We can close this as it seems to be a problem of some combination in my setup. If I have more information on this I post it here

@hoschi 👍 Any regression or idea to improve the UX highly welcome, post it here or feel free to simply open a new issue 😛


Detect list items in MS Word Documents

Currently, bulleted and enumerated lists are not detected in MS Word documents. They are currently detected as either Narrative Text or Titles. The goal of this issue is to update partition_docx so that these elements are detected. This may require a check of the element XML for the section of text in question.

Can you tell me more about this issue? Looking at the expected_elements fixture in test_docx.py, it seems like we are detecting bulleted lists. Is this issue specific to MS Word documents?

Here's an example document where the bullet points are identified as NarrativeText.

list-item-missing.docx

I also have this issue. I have downloaded a bunch of docs files from google drive (google exports them as docx files when downloading a directory on google drive. The documents have many normal and nested bullet points, but they're identified either as NarrativeText or Title when I use unstructured.

Thanks for the additional detail @saeedesmaili . @Coniferish is working on this issue now


Added some conditionals to the gitlab.rb template to allow for unauthenticated SMTP - 2

Hi,
Gitlab requires the smtp_authentication, smtp_user_name, and smtp_password variables in gitlab.rb to be unset in order to use unauthenticated SMTP. This adds jinja checks for these values and does not set them if they are empty.
In the case of the smtp_authentication = false, you have to remove the smtp_user_name and smtp_password, (well-known issue of Gitlab configuration).
Source : https://gitlab.com/gitlab-org/omnibus-gitlab/issues/325

This is a duplicate of the #87 without the prometheus part.


embassy task: cannot cfg away task arguments

#[embassy_executor::task]
pub async fn test(
    a: u32,
    b: u32,
    #[cfg(feature = "c")] c: u32,
) {

}

Fails with cannot find value c in this scope when the feature c is not enabled. It seems argument cfg's are not applied during the transformation.

I attempted to fix this, but it seems when the task macro runs, all the args have no attributes, i.e id.attrs.len() is always zero. Not sure where this info is being lost (or maybe I'm looking in the wrong place, proc macros are not my area of expertise).


[UI]: Changed class from warning to failure for confirm site name mes…

…sage.
Fixes #12232
When deleting a page that triggers the WAGTAILADMIN_UNSAFE_PAGE_DELETION_LIMIT, the orange warning text fails the contrast checks.
So I have changed the class of the message text from warning to failure which imrpoves the contrast.
Before

Now

I think we should probably keep this as warning but find a more suitable yellow/orange instead.
@thibaudcolas - thoughts?

I think we should probably keep this as warning but find a more suitable yellow/orange instead.
@thibaudcolas - thoughts?

Should it be changed globally or just in this page?

@sanjeevholla26 if you can suggest a better yellow/orange range of colours that's good (including for dark mode) I think we would want to update the colours globally yes.

My apologies @sanjeevholla26 - I just read the original issue and see that @thibaudcolas actually suggested the message type change originally.
https://github.com/wagtail/wagtail/issues/12232#issuecomment-2312208122
I'll try to take another look at this PR soon.


rdpgfx: Fix GFX v10.6 PDUs parsing and naming according to the spec

This PR fixes the new GFX 10.6 client and server PDUs parsing and naming according to the spec.
This change is taken out of our proxy PR as @akallabeth asked to do. The proxy's functionality depends on this one.

@freerdp-bot test


[New game]: Rubik's Cube Game

🎮 Game Request
The Cube Solver is a captivating puzzle game that challenges players to unravel the mysteries of a scrambled Rubik's Cube. Utilizing a seamless combination of HTML, CSS, and JavaScript, players can manipulate the virtual cube and strategically solve it, testing their spatial reasoning and problem-solving abilities.
Point down the features
Game points

Realistic cube simulation
User-Friendly controls
Time tracking

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @OMKAR-KALEPU !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @OMKAR-KALEPU ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


web3.py dependency issues

Error message
ImportError: cannot import name 'geth_poa_middleware' from 'web3.middleware' (/Users/daniel.adebimpe/testing-notebooks/zksync/.venv/lib/python3.11/site-packages/web3/middleware/__init__.py)
Description
I have followed the installation instructions on the zksync website here. And i'm getting errors attempting to run the following sample code that is provided (which are just imports):
from eth_account import Account
from eth_account.signers.local import LocalAccount
from web3 import Web3

from zksync2.account.wallet import Wallet
from zksync2.module.module_builder import ZkSyncBuilder

To which I get import error seen above.
Dependencies
python version - 3.11.9
web3 version - 7.4.0
zksync2 version - 1.2.0
Additional Context
I'm running this code inside a virtual env, on vscode.
Any help/support would be appreciated.

Current version only supports web3py v6. New release will come out with support for v7


[Feature request] Ask to import GPG key?

Just migrated my repo to another server and decided to rebuild all of my packages and I noticed it's quite a hassle, especially when building multiple packages. to import all of the GPG keys by hand. So, I'm asking you to add a feature that asks the user if they want to import the missing key.

You are probably looking for keyserver-options auto-key-retrieve option, add this to your ~/.gnupg/gpg.conf.

Aah did not know of this option, thanks!

No wonder: https://wiki.archlinux.org/index.php?title=Makepkg&diff=510044&oldid=510043

Is there any chance of reconsidering adding something like this? Maybe even an automated version? auto-key-retrieve unfortunately does not work (anymore) for some signatures in the AUR, most notable for me the Dropbox one, because they don't contain the fingerprint of the key, but only the key ID, which gpg doesn't use for lookup during auto-key-retrieve anymore.
See also this Q&A I have been grappling with the last couple of days. :sweat_smile:

Dear lord, I can stand GPG less every day.


2022 5 12 upgrade reanimated

WIP

Thanks

Sorry, wasn't ready to be merged yet! Will let you know when it is

Good

how are you?

@daxaxelrod


chore(github-transfer): transfer under swaggerexpert organization

:tada: This PR is included in version 1.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


WIP: Some changes

I've made some changes here and there. Still a lot to do, but please have a look.

Coverage increased (+13.0%) to 54.167% when pulling a30d83ece278c6001b2478eff884b0184336a51b on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+13.0%) to 54.167% when pulling a30d83ece278c6001b2478eff884b0184336a51b on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.4%) to 55.556% when pulling 0dc9675c2944791b8bfe5fe0088f799e11a9228d on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.4%) to 55.556% when pulling 00d6218d5c155d892296251020cc53148685e441 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.7%) to 55.862% when pulling f17c1997566b3c80efe54cf6a5674b3ff733d995 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.4%) to 55.556% when pulling 300f1d2079751426c7f6f5fdb17eb160a92bcfe1 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Wow! Thank you very much! Great work. :)

Coverage increased (+12.4%) to 53.623% when pulling a6f80af94106d76e83bbde180ad4ca5ca59fdddf on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+12.8%) to 53.957% when pulling 29b007c16198a26c96270a7b3f79c7539103d8f2 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+12.8%) to 53.957% when pulling 29b007c16198a26c96270a7b3f79c7539103d8f2 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+12.8%) to 53.957% when pulling 29b007c16198a26c96270a7b3f79c7539103d8f2 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling 7b17b5cd3612f073c8de64139d6957dea98570cf on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling c964f006940911edae797c5bb06a2faa0acb6075 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling 462dca97b174719fc70473a2a64cb4ccf4af9db5 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling 462dca97b174719fc70473a2a64cb4ccf4af9db5 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+21.0%) to 62.147% when pulling 41d5c77fc66103a0ca22f2d2ce6b07a9a8f62268 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling 481c32e6e8f0f5f3db1e6bdea521d52a0704a010 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling 481c32e6e8f0f5f3db1e6bdea521d52a0704a010 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+26.0%) to 67.164% when pulling 481c32e6e8f0f5f3db1e6bdea521d52a0704a010 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling 98e9367a3d3f196bead5bb5e36de03e622a16a7e on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling f36af39bbf0d9f1ea4e6e92beb59016c5ea6706d on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling f36af39bbf0d9f1ea4e6e92beb59016c5ea6706d on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+14.1%) to 55.319% when pulling f36af39bbf0d9f1ea4e6e92beb59016c5ea6706d on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Still work in progress. Please don't merge yet. 🙃

Coverage increased (+48.2%) to 89.404% when pulling 42728a83f21a4c51d9c9fff9d786ef87efc18de4 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+47.3%) to 88.489% when pulling 70bc23513061da806f85b05c00fd32265ee16225 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+50.9%) to 92.086% when pulling 14f39ae1514dbc2884a2c28526502c3343adcf47 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+51.6%) to 92.806% when pulling 0714453d907b8f45dd0ba8bee3cb19f277fbe8ba on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+53.0%) to 94.152% when pulling 9e425ff386ee150b1f3866083f93904331f26bcd on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+53.0%) to 94.152% when pulling ecdc8e43368d766f1532e520390499c988085db1 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+53.0%) to 94.152% when pulling bd53ebcb2d703ff527009beeda87b7d7b4f7b91f on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+53.0%) to 94.152% when pulling 3c2c8b5192b158742142d4a1003d09dbe8f25734 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.

Coverage increased (+53.08%) to 94.253% when pulling 1133f584958bf66dc63e095c9d82dbab7368ed71 on woylie:master into 602617e8d74b4a51666fc29549f7dc83fe549135 on rhazdon:master.


Sketch out districtwide admin page

What does this look like?

What's it all about?

Create a logical homepage for Uri to access all the administrator functions we're building out (like student services bulk upload)
Reduce unnecessary load on the app by avoiding extra trips to the School Overview Page which costs lots of memory
Clean up the navbar

Here's what the view looks like for educators with districtwide access but no ability to edit educator permissions:


added User.from_auth method for Ruby examples

as per Issue #571 by @aL3xa
You will need to have an Authorization model to accommodate it
create_table "authorizations", force: :cascade do |t|
t.string   "provider"
t.string   "uid"
t.string   "token"
t.integer  "user_id"
t.datetime "created_at"
t.datetime "updated_at"
t.string   "secret"
end

@elanperach Using your change, I hit an error "NoMethodError (undefined method `smash')" due to the line "params = params.smash.with_indifferent_access"

@ACPK Added another commit with the smash method we added to the Hash Class.
Let me know if that did the trick.

@elanperach could you clean up the PR and remove unnecessary User fields?

dear @elanperach what is the purpose of #smash method?

@aligit it is for flattening nested hashes.

thanks


Attachment serialization size

Q
A

Bug report?
yes

Feature request?
no

RFC?
no

How used?
Standalone

Swiftmailer version
6.1.3

PHP version
7.3

A serialized empty message object is 12677 bytes long, but a serialized empty attachment object is 48169 bytes long, ballooning any message object with an attachment in it. (Not to mention multiple)
This is because by default the entire list of 986 known mimetypes from /lib/mime_types.php is added to attachments as a private property, which is only used in setFile to determine the mimetype from the extension...
This seems similar to #103 and should be fixable the same way: By moving this into a static property. This lowers the size of a Swift_Attachment to 7959 bytes.
Example
<?php

include 'vendor/autoload.php';

echo strlen(serialize(new Swift_Message())).PHP_EOL;
echo strlen(serialize(new Swift_Attachment())).PHP_EOL;

We are well aware of the size of the serialized messages. Unfortunately, nothing we can do easily. I've tried several times. The good news is that I've taken that into account when designing Symfony Mailer, which is a replacement for Swiftmailer.


GotoLineAndCenter and code folding

GotoLineAndCenter does not seem to honor code folding, but seems to works in term of visible lines.
So if you folded lines above line 50, and GotoLineAndCenter(50), the caret won't end up on the line marked 50 in the margin.

Fixed.


Make authenticated API calls

Steps to reproduce
After authentication, I store the accessToken in my redux state (and after that redux-persist automatically stores it in localStorage).
What I want to achieve is: Make every feathers API call with the accessToken, if it's present in the redux state.
What I'm doing now:
export const app = feathers(); // + configure rest, hooks...

// Append accessToken in header if present.
// It would be better to take the accessToken from redux state,
// but for now we keep this solution (i.e. take directly from
// localStorage)
app.hooks({
  before: hook => {
    const item = window.localStorage.getItem('persist:myApp'); // This is where redux-persist saves the accessToken
    if (item) {
      const { auth } = JSON.parse(item);
      const { accessToken } = JSON.parse(auth);
      if (!accessToken) {
        return;
      }
      hook.params.headers = {
        Authorization: `Bearer ${accessToken}`,
        ...hook.params.headers
      };
      return hook;
    }
  }
});

So what I'm doing is, before each API request, retrieve the accessToken from the localStorage (and not from the in-memory store!).
Expected behavior
There should surely be a way to do this without retrieving localStorage and parsing JSON before each api request.
Actual behavior
Didn't find a clean way to pass state variables to the feathers app.
The only way I found is, on every api request, do
componentWillMount() {
  this.props.findUsers({ // findUsers dispatches feathersRedux.users.find
    headers: { Authorization: `Bearer ${this.props.auth.accessToken}` }
  })
}

But doing this on every method is not viable.
System configuration
Tell us about the applicable parts of your setup.
Module versions 2.1.0
NodeJS version: Not relevant
Operating System: Not relevant
Browser Version: Not relevant
React Native Version: Not relevant
Module Loader: Not relevant

I think that @feathersjs/authentication-client does this for you.
https://docs.feathersjs.com/api/authentication/client.html
https://github.com/feathersjs/authentication-client
My app.js:
export const app = feathers()
  .configure(feathers.socketio(socket))
  .configure(feathers.hooks())
  .configure(authentication({
    storage: window.localStorage, // store the token in localStorage and initially sign in with that
  }));

In my oauth callback page I end up calling authenticate() like so:
app.authenticate({strategy: 'jwt', accessToken: Cookies.get('feathers-jwt')});

I just double checked my project(s) and I am using @feathersjs/authentication-client for this.
https://docs.feathersjs.com/api/authentication/client.html
https://github.com/feathersjs/authentication-client
My app looks like:
...
import authentication from 'feathers-authentication-client';
...
export const app = feathers()
  .configure(feathers.socketio(socket))
  .configure(feathers.hooks())
  .configure(authentication({
    storage: window.localStorage, // store the token in localStorage and initially sign in with that
  }));

In my oauth callback page I end up calling:
app.authenticate({strategy: 'jwt', accessToken: Cookies.get('feathers-jwt')}));

at this point the client will exchange the cookie for an auth token and stuff it in local storge. After this all subsequent calls should be authenticated.

Hey @chris-garrett,
I'm a beginner and I'm trying to implement this for the past 6 hours or so, I am having difficulties because app.authenticate() is a promise and not sure how to wait it out.
I have tried something like this:
`import React from 'react';
import Dashboard from './dashboard';
import PropTypes from 'prop-types';
import feathers from '@feathersjs/feathers';
import auth from '@feathersjs/authentication-client';
import socketio from '@feathersjs/socketio-client';
import io from 'socket.io-client';
import { Provider } from 'react-redux';
import Realtime from 'feathers-offline-realtime';
import reduxifyServices, { getServicesStatus } from 'feathers-redux';
import configureStore from '../../store';
const socket = io();
const app = feathers().configure(socketio(socket)).configure(auth({
storage: window.localStorage
}));
class Layout extends React.Component {
async componentDidMount(){
await app.authenticate();
}
render() {
    const services = reduxifyServices(app, ['users', 'customers']);
    const store = configureStore(services);
    store.dispatch(services.customers.create({ text: 'message 1' }));

    return (
        <div>
          <Provider store={store}>
          <Dashboard services={services} getServicesStatus={getServicesStatus}>
            { this.props.children }
          </Dashboard>
          </Provider>
        </div>
        );
}

}
export { Layout };
`
But it does not seem to work, can you give me some advice? :)

First you can look at eddyystop/feathers-reduxify-authentication. Its a wrapper over app.authenticate() while maintaining an 'authorized' prop in the state.
Your will have to be in a wait state until the promise resolves using app.authenticate() or wait until the authication state is set using feathers-reduxify-authentication. That can be awkward. You can look at (the by now quite dated)
eddyystop/feathers-starter-react-redux-login-roles as a redux example.
You can always use a pollyfill for async/await in the client to make it sync, but your frontend will likely be 'hung' until auth is done.


Removed compiletime deprecations

Hi,
I have a go at removing a few deprecations that were present in the build with latest elixir version.
The following changes were done :

Update the mime_types count from 647 -> 648 to get the test passing (We added one at PR #60)
Add () on the method calls
Removed the unused variables

Most of these deprecations are present when using
Erlang/OTP 19 [erts-8.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Elixir 1.3.4

Here is the errors that were outputted during compilation :
warning: variable "get_mix_config" does not exist and is being expanded to "get_mix_config()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/context.ex:9

warning: variable "mix_test_config" does not exist and is being expanded to "mix_test_config()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/context.ex:30

warning: variable "pure_from" is unused
  lib/mailman/external_smtp_adapter.ex:31

warning: variable "mime_types" does not exist and is being expanded to "mime_types()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/attachment.ex:717

warning: variable "uri" is unused
  lib/mailman/attachment.ex:688

warning: variable "deliveries" does not exist and is being expanded to "deliveries()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/test_server.ex:18

warning: variable "self" does not exist and is being expanded to "self()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/test_server.ex:36

warning: variable "self" does not exist and is being expanded to "self()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/test_server.ex:41

warning: variable "self" does not exist and is being expanded to "self()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/test_server.ex:46

warning: variable "self" does not exist and is being expanded to "self()", please use parentheses to remove the ambiguity or change the variable name
  lib/mailman/test_server.ex:72

Thanks for looking into it !

Thanks and sorry for such a late merge!


Adding upstream-url in the resources settings

Summary
I'm confused about the architecture.
On the page https://gogatekeeper.github.io/gatekeeper/ the example architecture looks like the gatekeeper works as a gateway.
But in the gatekeeper settings only one host is possible - upstream-url.
In practice, this is not enough.
How about adding upstream-url in the resources setting?
Thanks in advance!
Why?
If we have a gateway that is at the entrance to a Kubernetes cluster and the cluster has modules located in different namespaces, we need the gateway to be able to route requests to different namespace domain names.
How
Solution options:

breaking backward compatibility - set FQDN in uri settings

resources:
- uri: ufr-product-catalog-ui.ufr-product-catalog-dev.svc.cluster.local/products*

preserving backward compatibility - set the relative path as before, but allow to override the upstream URL.
If upstream-url is specified in the resource, then it overrides the root upstream-url.

upstream-url: ufr-product-catalog-ui.ufr-product-catalog-dev.svc.cluster.local
resources:
- uri: /products*
   upstream-url: ufr-product-catalog-ui.ufr-product-catalog-dev.svc.cluster.local

@gt814 hi this is not possible this feature would need to be implemented e.g. as new softwate built above gogatekeeper, for sure there would be next requests to implement virtual host routing, sni matching etc...etc..., I don't have time to implement new project and maintain it but if there is somebody I would be happy to see it

@p53 Thanks for your answer!
Behind the gatekeeper we can use other components like envoy or nginx,
but I was confused by the number of components in the chain ))
In my case a sidecar was configured and this required a helm chart for deploying the gatekeeper, different from the helm chart for deploying microservices with business logic.
I understand your point of view and will close this issue.


Exclude binary files from git EOL settings

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[x] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description
Merge changes for images and font files were not possible to get rid of. git reset --hard HEAD would result in the files still showing with merge changes.
Solution from:
https://stackoverflow.com/a/52694438/25657391
Added/updated tests?
We are aiming for 100% statement coverage.

[ ] Yes
[x] No, and this is why: not a functional change
[ ] I need help with writing tests

Seems good. I was reading a little about line endings, and it seems LF is the Unix standard. Is there any issues with Windows computers using this? Or will the windows OS be able to convert the LF to CRLF

All the 3 major OSes support either EOL type. It's just VSCode uses the OS default, so we need to override that if we have some ppl using Windows and some using Unix based OSes.


feat(home): add specification authors section

fixes #113

@acidbunny21 Awesome, could you please resolve conflicts so we can get this one merged in?

@pavlenex conflicts resolved ✅


Home Assistant Update is Available

This issue is re-opened automagicly by Home Assistant.
It should be closed manually by commenting closes #14 when committing new  .HA_VERSION file

Test comment on issue

Upgrade Home Assistant from 0.114.3 to 0.114.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.114.4 to 0.115.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.0 to 0.115.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.1 to 0.115.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.1 to 0.115.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.2 to 0.115.3
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.3 to 0.115.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.4 to 0.115.5
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.5 to 0.115.6
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.115.6 to 0.116.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Travis build has passed

Upgrade Home Assistant from 0.116.1 to 0.116.2
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.116.2 to 0.116.3
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.116.2 to 0.116.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.116.4 to 0.117.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Travis build has passed

Upgrade Home Assistant from 0.117.0 to 0.117.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.117.1 to 0.117.2
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.117.1 to 0.117.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.117.4 to 0.117.5
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.117.5 to 0.117.6
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.117.6 to 0.118.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.118.0 to 0.118.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.118.2 to 0.118.3
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.118.3 to 0.118.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.118.4 to 0.118.5
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 0.118.5 to 2020.12.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2020.12.0 to 2020.12.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2020.12.1 to 2020.12.2
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2020.12.2 to 2021.1.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2020.12.2 to 2021.1.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.0 to 2021.1.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.0 to 2021.1.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.1 to 2021.1.2
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.1 to 2021.1.2
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.2 to 2021.1.3
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.2 to 2021.1.3
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.3 to 2021.1.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.3 to 2021.1.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.4 to 2021.1.5
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.4 to 2021.1.5
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.5 to 2021.2.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.1.5 to 2021.2.1
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.2.1 to 2021.2.2
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.2.1 to 2021.2.3
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.2.3 to 2021.3.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.2.3 to 2021.3.2
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.2.3 to 2021.3.3
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.2.3 to 2021.3.4
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.3.4 to 2021.4.0
Release notes available via https://www.home-assistant.io/latest-release-notes/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.4.0 to 2021.4.1
Release notes available via https://www.home-assistant.io/blog/2021/04/07/release-20214/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.4.1 to 2021.4.2
Release notes available via https://www.home-assistant.io/blog/2021/04/07/release-20214/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.4.3 to 2021.4.4
Release notes available via https://www.home-assistant.io/blog/2021/04/07/release-20214/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.4.4 to 2021.4.5
Release notes available via https://www.home-assistant.io/blog/2021/04/07/release-20214/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.4.5 to 2021.4.6
Release notes available via https://www.home-assistant.io/blog/2021/04/07/release-20214/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.4.6 to 2021.5.0
Release notes available via https://www.home-assistant.io/blog/2021/04/07/release-20214/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.5.2 to 2021.5.3
Release notes available via https://www.home-assistant.io/blog/2021/05/05/release-20215/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.5.3 to 2021.5.4
Release notes available via https://www.home-assistant.io/blog/2021/05/05/release-20215/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.5.4 to 2021.5.5
Release notes available via https://www.home-assistant.io/blog/2021/05/05/release-20215/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.5.5 to 2021.6.0
Release notes available via https://www.home-assistant.io/blog/2021/05/05/release-20215/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.6.0 to 2021.6.1
Release notes available via https://www.home-assistant.io/blog/2021/06/02/release-20216/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.6.2 to 2021.6.3
Release notes available via https://www.home-assistant.io/blog/2021/06/02/release-20216/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.6.3 to 2021.6.4
Release notes available via https://www.home-assistant.io/blog/2021/06/02/release-20216/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.6.4 to 2021.6.5
Release notes available via https://www.home-assistant.io/blog/2021/06/02/release-20216/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.6.5 to 2021.6.6
Release notes available via https://www.home-assistant.io/blog/2021/06/02/release-20216/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.6.6 to 2021.7.0
Release notes available via https://www.home-assistant.io/blog/2021/06/02/release-20216/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.7.0 to 2021.7.1
Release notes available via https://www.home-assistant.io/blog/2021/07/07/release-20217/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.7.1 to 2021.7.2
Release notes available via https://www.home-assistant.io/blog/2021/07/07/release-20217/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.7.2 to 2021.7.3
Release notes available via https://www.home-assistant.io/blog/2021/07/07/release-20217/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.7.3 to 2021.7.4
Release notes available via https://www.home-assistant.io/blog/2021/07/07/release-20217/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.7.4 to 2021.8.0
Release notes available via https://www.home-assistant.io/blog/2021/07/07/release-20217/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.8.0 to 2021.8.1
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.8.0 to 2021.8.1
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.8.0 to 2021.8.1
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.8.0 to 2021.8.1
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.8.0 to 2021.8.1
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

GitHub workflow has success

Upgrade Home Assistant from 2021.8.0 to 2021.8.2
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

GitHub workflow has success

Upgrade Home Assistant from 2021.8.2 to 2021.8.3
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.8.3 to 2021.8.4
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.8.4 to 2021.8.5
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.8.5 to 2021.8.6
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.8.6 to 2021.8.7
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.8.7 to 2021.8.8
Release notes available via https://www.home-assistant.io/blog/2021/08/04/release-20218/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.0 to 2021.8.8
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.0 to 2021.9.1
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.0 to 2021.9.2
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.2 to 2021.9.3
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.3 to 2021.9.4
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.4 to 2021.9.5
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.5 to 2021.9.6
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.6 to 2021.9.7
Release notes available via https://www.home-assistant.io/blog/2021/09/01/release-20219/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.9.6 to 2021.10.1
Release notes available via https://www.home-assistant.io/blog/2021/10/06/release-202110/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.10.4 to 2021.10.5
Release notes available via https://www.home-assistant.io/blog/2021/10/06/release-202110/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.10.5 to 2021.10.6
Release notes available via https://www.home-assistant.io/blog/2021/10/06/release-202110/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2021.10.6 to 2021.10.7
Release notes available via https://www.home-assistant.io/blog/2021/10/06/release-202110/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.10.7 to 2021.11.0
Release notes available via https://www.home-assistant.io/blog/2021/10/06/release-202110/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.11.0 to 2021.11.1
Release notes available via https://www.home-assistant.io/blog/2021/11/03/release-202111/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.11.1 to 2021.11.2
Release notes available via https://www.home-assistant.io/blog/2021/11/03/release-202111/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.11.2 to 2021.11.3
Release notes available via https://www.home-assistant.io/blog/2021/11/03/release-202111/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.11.3 to 2021.11.4
Release notes available via https://www.home-assistant.io/blog/2021/11/03/release-202111/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.11.4 to 2021.11.5
Release notes available via https://www.home-assistant.io/blog/2021/11/03/release-202111/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.11.5 to 2021.12.0
Release notes available via https://www.home-assistant.io/blog/2021/11/03/release-202111/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.0 to 2021.12.1
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.1 to 2021.12.2
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.1 to 2021.12.3
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.3 to 2021.12.4
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.4 to 2021.12.5
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.5 to 2021.12.6
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.6 to 2021.12.7
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.7 to 2021.12.8
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: failure

Upgrade Home Assistant from 2021.12.8 to 2021.12.9
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.9 to 2021.12.10
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2021.12.10 to 2022.2.0
Release notes available via https://www.home-assistant.io/blog/2021/12/11/release-202112/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from unknown to 2022.2.3
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.3 to unavailable
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.3 to 2022.2.4
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.3 to 2022.2.5
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.5 to 2022.2.6
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2022.2.6 to 2022.2.7
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.7 to 2022.2.8
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.8 to 2022.2.8
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.9 to unavailable
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.9 to unavailable
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.9 to 2022.2.9
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.9 to unavailable
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.9 to 2022.3.0
Release notes available via https://www.home-assistant.io/blog/2022/02/02/release-20222/.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.2.9 to unavailable
Release notes available via https://www.home-assistant.io/blog/2022/03/02/release-20223/.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2022.3.0 to 2022.3.1
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.0 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.1 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.1 to 2022.3.2
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.2 to 2022.3.3
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.3 to 2022.3.4
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.4 to 2022.3.4
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.4 to 2022.3.5
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.6 to 2022.3.7
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.7 to 2022.3.8
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.8 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.8 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.8 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.3.8 to 2022.4.0
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.0 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.0 to 2022.4.1
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.0 to 2022.4.1
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.0 to 2022.4.2
Release notes available via None.
This comment was generated by Jarvis.

Upgrade Home Assistant from 2022.4.2 to 2022.4.3
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.3 to 2022.4.4
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.4 to 2022.4.4
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.4 to 2022.4.5
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.5 to 2022.4.5
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.5 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.5 to 2022.4.6
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.6 to unavailable
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.6 to 2022.4.7
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.4.7 to 2022.4.7
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.5.0 to 2022.5.1
Release notes available via None.
This comment was generated by Jarvis.

GitHub workflow status: success

Upgrade Home Assistant from 2022.5.1 to 2022.5.2
Release notes available via https://www.home-assistant.io/blog/2022/05/04/release-20225/.
This comment was generated by Jarvis.

GitHub workflow status: success


Search results pages go over limit

Noticed this while working on the current patch release.

The highest page count should be 500 (i.e. 10.000 documents) - looks like it is now based on the total number of results.
The request for a page over 500 will fail, so this should be restored.

After some digging: this happens only when the user has a download limit over 10.000, as the download limit is also used to determine the maximum page count. Such requests are refused by elasticsearch, however.


Sui framework snapshot tool

I am going to revisit this tomorrow and see if I can set up a few simtests to help with upgrade testing

Closing this one and continue in https://github.com/MystenLabs/sui/pull/10490


Improve json->nwb conversion

Describe changes:

Add more data to nwb:

Time stamps: B_PhotometryFallingTimeHarp
Time stamps: B_PhotometryRisingTimeHarp
Time stamps: B_OptogeneticsTimeHarp
Trial-by-trial lickspout positions (x, y, z)
Trial-by-trial reward size (left, right)

Add more meta data, and put them to nwb.scratch

Replace all eval() with getattr())
Improve formatting
The GUI will not export to nwb immediately after a session

What issues or discussions does this update address?

https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/256
https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/197

Describe the expected change in behavior from the perspective of the experimenter
None.
Describe the outcome of testing this update on a rig in 447
N/A. Will only affect the downstream pipeline.

@XX-Yin please check whether I'm still missing some important fields. @hagikent @srecanatesi please also take a look. Thanks!


Adding NGC compiler support for AOT and Web pack compatibility.

@especializa-user  and @berardo  thank you so much for this wonderful Angular Directive. I've taken the liberty to upgrade the project to compile using Angular NGC compiler instead of typescripts compiler. This should be enough to allow webpack and AOT compatibility. However, I'm not familiar with your build scripts so it's quite possible I missed something.  This should help resolve these issues:
https://github.com/Especializa/nativescript-ng-shadow/issues/6

Hi Guys,
Any ideas when and if this will this be merged?
Regards,
Tarek

Please, this has been open for almost a month. Anyone care to merge?
The lacking webpack and aot support makes the plugin virtually impossible to use in production.

If you want to use this plugin in your project, you can actually copy and paste the directive file into your project.
https://github.com/Especializa/nativescript-ng-shadow/blob/master/src/angular/ng-shadow.directive.ts
then add it to the appropriate ngModule and use with bundling.

How do I get access to the latest changes in the master branch (including this merge)?
The latest package version in the npm registry is still 2.1.0 (from December 2017) and including the Github repo directly as a dependecy in my package.json (as suggested here) results in an error: Could not install from "Especializa\nativescript-ng-shadow" as it does not contain a package.json file.
"dependencies": {     ...     "nativescript-ng-shadow": "Especializa/nativescript-ng-shadow",     ...   },

@ManuelSch yes, I'm wondering the same.
@berardo would be cool if you could publish the latest version (including this PR) to npmjs.org - as mentioned by @ManuelSch the GitHub repository does not contain a package.json so we cannot just install from the master.

@lambourn If you need it real quick, just download the repo as a zip file, take the content of the src folder and use it to overwrite the files in your /node_modules/nativescript-ng-shadow folder.
Works as a short-term solution, but obviously these changes will be gone as soon as you run npm install the next time.

@ManuelSch sure. I cloned it locally outside node_modules and set my dependency to file:// location instead. Still, would be great if the maintainers could push a new package to npmjs.org

@especializa-user and @berardo - would be cool if you could publish the latest version including this PR to npmjs.org. Thanks a lot!

It works with --env.aot --env.uglify flags now but it doesn't without --env.aot for me? Is this expected behaviour?

Can please you Bump the version and update NPM ?

Hi @berardo - any chance you bump the version? :)

Please publish the version to npm.

Can please you Bump the version and update NPM ?

I've forked and repackage this directive in the standard Angular Package format and published it to NPM here: https://www.npmjs.com/package/nativescript-ngx-shadow. @especializa-user if wish just let me know and I can open a PR with the changes included.  I just wanted to get this out there since the directive is so amazing and lots for people are clamoring to use it.
github for the fork is here: https://github.com/TheOriginalJosh/nativescript-ngx-shadow


Issue with examples on linux

Hi,
Just wanted to say I love what you guys have been doing here. I've been following this project for a little bit and have even used pixi for a small personal project. The workflow was marvelous :).
This week I decided to see if how it would work on linux. Trying the examples I run into the following error...
 ~/pixi/examples/turtlesim
21:06 $ pixi run start
  × The current system has a mismatching virtual package. The project requires '__linux' to be at least version '5.10' but the system has version '3.10.0'

I confirmed the linux version.
21:06 $ uname -r
3.10.0-1062.4.2.el7.x86_64

This still leaves me a little bit of a loss. I don't see any explicit mention of a minimum linux version in the lock/toml file. What is the recommended workflow to resolve this?

Thankyou, this is awesome to hear!
To fix the issue you need to add:
[system-requirements]
linux= "3.10"

The default is a lot higher. This is still up for a debate. Why are you using such a old Linux kernel?

I was testing on a on premise node that is available to me. The cluster is not managed by me or my team so I am unsure of the exact reasoning, but we could probably do a better job of keeping things up to date.
That worked though. Thank you!

Good that it worked. Note that it might not always work as packages can depend on higher version of linux.
Upvote this reaction to see how much people walk into this problem :+1:

Maybe, you could add a help message to see this issue on github or to try
[system-requirements]
linux= "Your version of linux"  ex: "5.4.0"

@jelber2 we've noted this as an issue we still have to improve the workflow for. It is tracked in https://github.com/prefix-dev/pixi/issues/815


Create component for bottom text in Landing

issue-97
Tailor the landing page to each of the roles for the bottom half of the page:
-create component for the bottom right message
-create component for the bottom message, sign up should not show when logged in

Based on issue 28, assuming this would take a similar amount of time. Budgeting 2 hours based on issue 28. It could take shorter time since any photos are involved (which I'm less experienced and encounter issues with)


tools/test: Use local throughout

Shell variables are global by default.  Thankfully Bash has a feature
where you can at least make them local, if you remember to do so.
This fixes a bug since 1db6b89ed where running the lint suite would
clobber the files variable that remembered the --diff vs
--all-files vs default (since-branch-base) setting.  This meant that
later suites (jest, prettier, and deps, by default) would see an
invalid value for files.
For jest, this had the same effect as --all-files, making it
annoyingly slow for interactive use (but the same as we run in CI.)
For prettier, it would cause it not to run at all.
The other accidentally-global variables here didn't happen to collide
with anything, but best to do this consistently so they don't in the
future (and so we're more likely to remember to do it in future code,
and avoid this sort of bug.)
Reported-by: Chris Bobbe<EMAIL_ADDRESS>Debugged-by: Chris Bobbe<EMAIL_ADDRESS>

Thanks, LGTM! Merged.


WSO2 IS Kubernetes - Workflow doesn't work with 2 replicas of stateful sets

Description:
When there are 2 replicas of the IS Stateful Set, the workflow sometimes works and another doesn't. When the IS Stateful Set has a single replica it works perfectly until the Pod is restarted, when it restarts it stops working until you eliminate the Workflow Definition and add it again.
The error in all cases is the following:

Thanks in advance.
Affected Product Version: IS-5.10.0
OS, DB, other environment details and versions:

Kubernetes: v1.18.2
MySQL: 5.7.31

Steps to reproduce:

Deploy the Kubernetes Helm Chart[1].
Add the Workflow Definition and the Workflow Engagements. Test it.
Scale the IS Stateful Set to 1 and add a new Workflow Definition and Workflow Engagements if the other one doesn't work. Test it.
Then restart the pod or scale the IS Stateful Set to 0 and then to 1. Test it.

https://github.com/wso2/kubernetes-is/tree/master/advanced/is-pattern-1#helm-chart-for-a-clustered-deployment-of-wso2-identity-server

Moved to https://github.com/wso2/kubernetes-is/issues/269


docs: ClientBootstrap reuse is not important but permissible on the same thread/EL

Motivation:
The original ClientBootstrap documentation is sometimes misunderstood as stressing the importance to re-use.
Modifications:
Explain that reuse is not important but permissible on the same thread/EL.
Result:
Clearer docs.

it would be really great if we could suppress the DocC symbol link warnings, those cross-module/cross-package links work on Swiftinit!

it would be really great if we could suppress the DocC symbol link warnings, those cross-module/cross-package links work on Swiftinit!

@franklinsch is this an option? Or will this work in DocC soon too?

@weissi We're tracking cross-target link resolution with https://github.com/apple/swift-docc/issues/208. It's being worked on primarily by @d-ronnqvist

@weissi We're tracking cross-target link resolution with apple/swift-docc#208. It's being worked on primarily by @d-ronnqvist

The initial support for cross-target linking in DocC is available on main behind a feature flag but the overall feature of multi-target documentation is still in progress.
Note that the DocC syntax for linking to a symbol in another module is
``/OtherModuleName/SymbolName/functionName()``

stating with a leading / to indicate an external symbol link, followed by the absolute symbol path (including the name of the external module. For example:

/Swift/Sendable
/NIOCore/EventLoop

@weissi We're tracking cross-target link resolution with apple/swift-docc#208. It's being worked on primarily by @d-ronnqvist

The initial support for cross-target linking in DocC is available on main behind a feature flag but the overall feature of multi-target documentation is still in progress.
Note that the planned—and currently implemented—syntax for linking to a symbol in another module is
``/OtherModuleName/SymbolName/functionName()``

stating with a leading / to indicate an external symbol link, followed by the absolute symbol path (including the name of the external module). For example:

/Swift/Sendable
/NIOCore/EventLoop

@dnadoba I assume NIO isn't using feature flags for its docs right now so this has to stay as is, correct?

I'm not aware of any feature flags set for DocC in NIO. The two main way DocC is compiled is through the build system provided by https://swiftpackageindex.com/ and Xcodes "Product -> Build Documentation" action.  I'm not aware of a safe way to add flags to both of them.

do these links actually produce any build errors in Xcode?