[Bug] recursion limit exceeded when deserialization

Component
network, json-rpc
What version of Alloy are you on?
alloy v0.2.1
Operating System
Linux
Describe the bug
The function try_deserialize_ok will return a deserialization error when recursion limit exceeded.
Reproduce Example
Using debug_trace_block_by_number with CallTracer option to trace Block 15413811
Code
let block_number = 15413811;
let geth_trace_options = GethDebugTracingOptions::default().with_tracer(
    GethDebugTracerType::BuiltInTracer(GethDebugBuiltInTracerType::CallTracer),
);
let geth_trace_results = provider
    .debug_trace_block_by_number(block_number.into(), geth_trace_options)
    .await?;
println!("{}", geth_trace_results.len());

Result
Error: deserialization error: recursion limit exceeded at line 1 column 200590

Caused by:
    recursion limit exceeded at line 1 column 200590

Reason
The recursion limit is not large enough to handle call traces of these two transactions tx1 and tx2 inside.
let hash = b256!("aceacb7bbe075e5701638860e33de3dd60b480e4d0cfd7ce672ea0ab77412ba3");
let geth_trace_options = GethDebugTracingOptions::default().with_tracer(
    GethDebugTracerType::BuiltInTracer(GethDebugBuiltInTracerType::CallTracer),
);
let geth_trace_results = provider
    .debug_trace_transaction(hash, geth_trace_options)
    .await;
println!("{}", geth_trace_results.is_err());  // true

This might be related and helpful: ethereum/go-ethereum#22857

If you want to deserialize that kind of heavily nested structure, enable the serde_json "disable_recursion_limit" feature yourself. This is not suitable to enable in Alloy itself.

If you want to deserialize that kind of heavily nested structure, enable the serde_json "disable_recursion_limit" feature yourself. This is not suitable to enable in Alloy itself.

Could you please explain a bit more and give some suggestions about deserializing heavily nested structures? 🙏

I ran into the same issue not too long ago. The problem with using the disable_recursion_limit feature of serde is that it needs to be enabled on the Deserializer itself, which is buried deep inside alloy (the try_deserialize_ok function that @ZzPoLariszZ has identified).
It would be good if alloy could somehow at least expose the option to the outside without the need of forking the project. After all this effectively currently disables the ability to work with certain transactions on the blockchain.

There is nothing that we need to expose, you have to add erde_json as a dependency and enable the feature.

The unbounded_depth feature on serde_json only exposes the disable_recursion_limit function that needs to be called on the deserializer itself.
    let mut deserializer = serde_json::Deserializer::from_str(&json);
    deserializer.disable_recursion_limit();

Since the deserializer is instantiated inside the try_deserialize_ok, it is not possible to enable this right now.

The possible modification of try_deserialize_ok
/// Attempt to deserialize the `Ok(_)` variant of an [`RpcResult`].
pub fn try_deserialize_ok<'a, J, T, E, ErrResp>(
    result: RpcResult<J, E, ErrResp>,
) -> RpcResult<T, E, ErrResp>
where
    J: Borrow<RawValue> + 'a,
    T: RpcReturn,
    ErrResp: RpcReturn,
{
    let json = result?;
    let json = json.borrow().get();
    trace!(ty=%std::any::type_name::<T>(), json, "deserializing response");
    let mut deserializer = serde_json::Deserializer::from_str(&json);
    deserializer.disable_recursion_limit();
    let deserializer = serde_stacker::Deserializer::new(&mut deserializer);
    T::deserialize(deserializer)
        .inspect(|response| trace!(?response, "deserialized response"))
        .inspect_err(|err| trace!(?err, "failed to deserialize response"))
        .map_err(|err| RpcError::deser_err(err, json))
}

Ah I see, I thought it would be removed by enabling the feature alone


Now i'm going to write an issue

header
nothing can i do for this questions.
level 3
12345678iop
http://<IP_ADDRESS>:6080/jsdsp/pages/index.html#mode_detail.html?&modeId=23

435


Extends setup.py with build_doc command

Tested no Sphinx env

python setup.py build_doc - failed with correct exception message

Tested Sphinx env

python setup.py build_doc - completed HTML doc build

Tested no Sphinx env

python setup.py install - no import Sphinx error message

Hello @samaid! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file docs/source/buildscripts/sdc_build_doc.py:

Line 95:1: E265 block comment should start with '# '
Line 103:1: W391 blank line at end of file

This PR requires install sdc with pip install . or pip install sdc.
Installing with pip install -e . (for development) will not work because cwd is removed from sys.path. For developers it is more convenient to use pip install -e . and run cd docs && make html.

I will continue work on this PR


Subtype HSL/RGB and expect certain outputs

Who is this for?
Us and better typing
What is it doing for them?
Based on this comment
It seems that types that are too nested aren't coming up as errors when of the wrong type, so we're being a lot more specific!
If there's a better way to do this please let me know, still learning on types 🤓

I think you need to unpack the heavily nested object for the type checker to tell you these are wrong – happy to discuss more tomorrow – but this looks fine as-is.

Let's chat tomorrow and I'll make changes!


Operationalize all Cold stunning models

Cron file manually adjusted to add the models int he correct order

All models on a single cron string is over the 999 character limit for a cron job, thus I split them into to jobs
One job starts 5 minuets after the other to reduce server load
Logging is sort of broken by doing it like this, due to our logging relying on pulling the standard out from specific jobs

DI Ingestion wasn't saving to DB due to bug but now it is


Azure File Copy Task: (400) Bad Request - Not able to fetch token for tenant Id

Hello,
we are using the latest Azure File Copy task (version 1.0.84), and we are getting the following error:
2017-02-13T09:50:58.7898956Z ##[debug][Azure Call]Retrieving storage key for the storage account: ebsazstorageesbdbesbdxxx in resource group:
2017-02-13T09:50:58.7908966Z ##[debug]Fetching Access Token
2017-02-13T09:50:58.8308958Z ##[debug]No proxy settings
2017-02-13T09:50:58.9878968Z ##[debug]POST https://login.windows.net/********/oauth2/token with -1-byte payload
2017-02-13T09:50:59.3108999Z ##[debug]ExceptionMessage: The remote server returned an error: (400) Bad Request. (in function: Get-SpnAccessToken)
2017-02-13T09:50:59.3459070Z ##[debug]Processed: ##vso[task.logissue type=error;code={"Task_Internal_Error":ExceptionMessage: Not able to fetch token for tenant Id ********. (in function: Get-AzRMStorageKeys)};]
We are using a Service Principal in VSTS which has Contributor Role on the Resource Group.
I was not able to reproduce the error on another subscription with exactly the same setup.

We solved the problem. After deleting the endpoint in VSTS we recreated the principal and the endpoint and everything works fine.


Add possibility to delete/move/rename files

There already is a command doc:rename that provides the move/rename functionality, and doc:delete that allows you to delete the current doc.

doc:delete does not work

Hmm, right. I never used it before, but after a small test I can confirm that indeed it does not delete the file.

doc:delete isn't performing as you expected it to be - instead it deletes the selection (from what I can get from the code). You might need to find another way.
One way might be making a plugin that calls os.remove. But beware, os.remove works on files and empty directories, so you might run into issues if you use it like rm -r.

The command doc:delete isn't work so this is something we need to fix.
Otherwise, for the delete/more/rename functionality it is delicate to figure out how to integrate with lite-xl especially because currently we don't have contextual menus. On the other side this is something definitely useful but we need to figure out a good way to integrate this functionality.
Note that I have implemented a very small part of this: if you control-click in a directory in treeview you will be prompted to create a new directory. The only problem of this approach is that it is not discoverable by the user, you really have to know this or otherwise you may never know!

this is not a bug. doc:delete is used to delete the selection, not to delete files. I suggest a new command is created for this, preferably doc:delete-file or soemthing.

Dang, I didn't realize that doc:delete was an actual editing action. Thanks for letting me know!

As @takase1121 pointed out, doc:delete is for forward deleting (delete key on the keyboard). I suggest the following addition to the "commands/core.lua" file.

The code to close the window is copied from "commands/root.lua". I wasn't sure how to reference root:close


Limited selection of robot test files with 'Run' button of VS Codium

The execution of robot test files in VS Codium can be configured by launch files and can be executed with the 'Run' button.
But with "target"   : "${file}", this feature is limited to files selected in VS Codium explorer and therefore opened in editor.
There is no corresponding functionality available to select a folder to let the Robot Framework execute all robot files
inside this folder automatically.
It would be useful to have an extension here to execute entire folders also (because Robot Framework supports folder as input).

Hi Cuong,
please look into this.
Thank you,
Thomas

Hi Cuong,
can you give me a status for this issue?
Thank you,
Thomas


Add University of Reading

official university website: https://www.reading.ac.uk/
long-term IT related course: https://www.reading.ac.uk/ready-to-study/study/2022/computer-science-ug/bsc-computer-science
university recognising the domain: https://www.reading.ac.uk/digital-technology-services/service-catalogue/office-365

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

Thanks for looking into this. I have attached some links above which should help with verification. Student emails will be in the form<EMAIL_ADDRESS>

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


HTTP 流量授权: practice/http-traffic-authorization.md

This article is waiting to be claimed. practice/http-traffic-authorization.md

/accept

/delay-reset 写作中，近期完成

/pushed

目录调整，该章节合并，详情见 #251


Drag & drop support for desktop clients

Should reference System.Window.Forms only at a desktop level, and consume what is required to make it work.

Completed in #430 and https://github.com/ppy/osu/pull/313 👍


Error when trying to initialize Spin temperature in a 3TM calculation

Hey,
sim.changeInit(3,temp_init) gives an error and it is associated to a typo in line 290 of NTMpy.py version 0.1.1. It says:
self.temp_data_Spin = function
when I believe it should say:
self.temp_data_Spin.init = function
which makes the code run without any issues.
Thanks,
Alberto

Hi Alberto,
Thank you very much for the hint.
Can you make a pull request?

Ciao Alberto, thanks for notifying us this bug. I am currently working on an update and I will correct this error I did not notice.


propan.cli.docs.serve missing from distribution

Describe the bug
In the latest version <IP_ADDRESS> there is an import for propan.cli.docs.serve, but the module is not included in the distribution.
Maybe that is because it is ignored here: https://github.com/Lancetnik/Propan/blob/main/propan/cli/docs/init.py#L3 ?
Curiously the gen.py exists:
$ ls […]/lib/python3.11/site-packages/propan/cli/docs/
app.py  gen.py  __init__.py

$ grep "version" […]/lib/python3.11/site-packages/propan/__about__.py
__version__ = "<IP_ADDRESS>"

Relevant traceback:
    from propan.brokers.rabbit import RabbitBroker, RabbitQueue
/opt/pipx/home/venvs/poetry/lib/python3.11/site-packages/propan/__init__.py:3: in <module>
    from propan.cli.app import *  # noqa: F403
/opt/pipx/home/venvs/poetry/lib/python3.11/site-packages/propan/cli/__init__.py:1: in <module>
    from propan.cli.main import cli
/opt/pipx/home/venvs/poetry/lib/python3.11/site-packages/propan/cli/main.py:10: in <module>
    from propan.cli.docs import docs_app
/opt/pipx/home/venvs/poetry/lib/python3.11/site-packages/propan/cli/docs/__init__.py:1: in <module>
    from propan.cli.docs.app import docs_app
/opt/pipx/home/venvs/poetry/lib/python3.11/site-packages/propan/cli/docs/app.py:12: in <module>
    from propan.cli.docs.serve import serve_docs
E   ModuleNotFoundError: No module named 'propan.cli.docs.serve'

@bodograumann  I suppose it is connected with .gitignore cuz this file reallu doesn't exists at disturbed package

And it's fixed with <IP_ADDRESS>


tracking score

🚀 What is the feature?
For now, we are displaying quiz questions correctly on the screen. But we are not tracking the total score of the session yet.
Provide a way to display the current score to the user. You can think about something cool yourself, but I would suggest that we need something like "[3/5]" (e.g. 3 correct out of 5) as a minimum requirement.
Have fun!

ℹ Additional info
Add a screenshot of your changes - if helpful.
Make sure the app works, otherwise the PR cannot be approved.

@benbenben147147147 please assign this issue to me

Sure!

@benbenben147147147 please see the pr https://github.com/benbenben147147147/Quiz-to-Contribute-OSS/pull/90


JSS Not Minified in Production Build

Hello, I tried searching for a solution to this for several hours but couldn't find one.
In my production build, the JSS generated by Material UI is not minified and the class names are not turned into jss123. They stay as MuiButtonBase, MuiInputBase, etc.
This is happening on both server side render and client side render.
I am setting NODE_ENV=production explicitly during build and runtime. And when building with webpack I am specifying production mode.
I'm pretty sure this is a webpack issue but I'm at the end of my ropes on this one :(

[x ] The issue is present in the latest release.
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
JSS is rendered in dev mode
Expected Behavior 🤔
JSS is rendered in production mode
Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.9.8

React
v16.13.1

Browser
Chrome

Webpack
v4.42.1

etc.

Here are my webpack configs:
webpack.base.js:
// branch
const branch = process.env.BRANCH || 'development';

// path
const path = require('path');

// webpack
const webpack = require('webpack');

// webpack plugins
const MiniCssExtractPlugin = require('mini-css-extract-plugin');

module.exports = {
	module: {
		rules: [
			{
				test: /\.(js|jsx)?$/,
				exclude: /node_modules/,
				loader: 'babel-loader'
			},
			// {
			// 	test: /\.(js|jsx)?$/,
			// 	include: [path.resolve(__dirname)],
			// 	use: {
			// 		loader: 'babel-loader',
			// 		options: {
			// 			presets: ['@babel/preset-env']
			// 		}
			// 	}
			// },
			{
				test: /\.(less)$/,
				exclude: /node_modules/,
				use: [
					MiniCssExtractPlugin.loader,
					{ loader: 'css-loader' },
					{
						loader: 'less-loader'
					}
				]
			},
			{
				test: /\.(svg|woff|woff2|eot|ttf|otf)$/,
				include: /paymentfont/,
				use: ['file-loader']
			}
		]
	},
	resolve: {
		modules: [
			path.resolve(__dirname),
			'node_modules'
		],
		extensions: ['.js', '.jsx', '.worker.js']
	},
	plugins: [
		new webpack.DefinePlugin({
			'__BRANCH__': JSON.stringify(branch)
		}),
		new MiniCssExtractPlugin({
			filename: 'styles.[contenthash].css',
			chunkFilename: 'styles.[contenthash].css'
		})
	]
};

webpack.client.base.js:
// branch
const branch = process.env.BRANCH || 'development';

// path
const path = require('path');

// webpack
const webpack = require('webpack');

// webpack plugins
const LoadablePlugin = require('@loadable/webpack-plugin');
const { CleanWebpackPlugin } = require('clean-webpack-plugin');
const CopyWebpackPlugin = require('copy-webpack-plugin');
const MomentTimezoneDataPlugin = require('moment-timezone-data-webpack-plugin');

// settings
const OUTPUT_PATH = 'dist';

module.exports = {
	target: 'web',
	entry: {
		main: './client.js'
	},
	output: {
		path: path.resolve(__dirname, OUTPUT_PATH),
		publicPath: '/',
		filename: '[name].[contenthash].js',
		chunkFilename: 'chunk-[name].[contenthash].js'
	},
	optimization: {
		runtimeChunk: true,
		splitChunks: {
			chunks: 'all',
			maxAsyncRequests: Infinity,
			maxInitialRequests: Infinity,
			minChunks: 2,
			minSize: 10000
		}
	},
	plugins: [
		new webpack.DefinePlugin({
			'__SSR__': JSON.stringify(false)
		}),
		new LoadablePlugin({
			writeToDisk: {
				filename: path.resolve(__dirname, 'bin')
			}
		}),
		new webpack.IgnorePlugin({
			resourceRegExp: /^\.\/locale$/,
			contextRegExp: /moment$/
		}),
		new MomentTimezoneDataPlugin({
			matchZones: /^America\/.+$/
		}),
		new CopyWebpackPlugin([
			{
				from: path.resolve(__dirname, 'assets')
			},
			{
				from: path.resolve(__dirname, `assets.${branch}`)
			}
		]),
		new CleanWebpackPlugin({
			cleanStaleWebpackAssets: false,
			protectWebpackAssets: false,
			cleanOnceBeforeBuildPatterns: ['*']
		})
	]
};

webpack.client.production.js:
// webpack
const merge = require('webpack-merge');

// webpack plugins
const TerserPlugin = require('terser-webpack-plugin');
const OptimizeCssAssetsPlugin = require('optimize-css-assets-webpack-plugin');
const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;

// base config
const baseConfig = require('./webpack.base.js');
const clientBaseConfig = require('./webpack.client.base.js');

const config = {
	mode: 'production',
	devtool: false,
	optimization: {
		minimizer: [
			new TerserPlugin({
				terserOptions: {
					ecma: 5,
					warnings: false,
					compress: {
						drop_console: true,
						drop_debugger: true
					},
					mangle: true,
					module: true,
					output: {
						comments: false
					},
					toplevel: true,
					ie8: false,
					safari10: false
				}
			}),
			new OptimizeCssAssetsPlugin({
				cssProcessorPluginOptions: {
					preset: ['default', { discardComments: { removeAll: true } }],
					region: 'us-west-2'
				}
			})
		]
	},
	plugins: [
		// uncomment this to analyze what is taking up space in webpack compilation
		// new BundleAnalyzerPlugin()
	]
};

module.exports = merge(baseConfig, clientBaseConfig, config);

webpack.server.base.js:
// path
const path = require('path');

// webpack
const webpack = require('webpack');

// webpack plugins
const NodeExternals = require('webpack-node-externals');
const LoadablePlugin = require('@loadable/webpack-plugin');
const { CleanWebpackPlugin } = require('clean-webpack-plugin');

// settings
const OUTPUT_PATH = 'bin';

module.exports = {
	target: 'node',
	entry: './server.js',
	output: {
		path: path.resolve(__dirname, OUTPUT_PATH),
		filename: 'server.js',
		chunkFilename: '[name].js'
	},
	externals: [NodeExternals()],
	plugins: [
		new webpack.DefinePlugin({
			'__SSR__': JSON.stringify(true)
		}),
		new LoadablePlugin({
			outputAsset: false,
			writeToDisk: false
		}),
		new CleanWebpackPlugin({
			cleanStaleWebpackAssets: false,
			protectWebpackAssets: false,
			cleanOnceBeforeBuildPatterns: ['*']
		})
	]
};

webpack.server.production.js:
// webpack
const webpack = require('webpack');
const merge = require('webpack-merge');

// base config
const baseConfig = require('./webpack.base.js');
const serverBaseConfig = require('./webpack.server.base.js');

const config = {
	mode: 'production',
	plugins: [
		new webpack.DefinePlugin({
			'__BUILD__': JSON.stringify('production')
		})
	]
};

module.exports = merge(baseConfig, serverBaseConfig, config);

Duplicate of #10068

i see. i used the gatsby material ui plugin before and thought the minification was built in.


Topic/marklogic

Current coverage is 74.72% (diff: 0.00%)

Merging #1329 into master will decrease coverage by 0.56%

@@             master      #1329   diff @@
==========================================
  Files           192        195     +3
  Lines         11469      11555    +86
  Methods       11202      11286    +84
  Messages          0          0
  Branches        124        126     +2
==========================================
  Hits           8634       8634
- Misses         2835       2921    +86
  Partials          0          0

Powered by Codecov. Last update e15fd41...fe39e9f

@jedesah Given our discussion yesterday, should probably close this and we can submit another with the other read/write approach.


VS Code's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VS Code.

Issue Type: Bug
getting this issue, tried reinstalling vscode insiders a several times but doesnt help.

VS Code version: Code - Insiders 1.37.0-insider (34e0ed575230b5c8168289995d59edf274539631, 2019-07-05T08:57:32.211Z)
OS version: Windows_NT x64 10.0.17134
Remote OS version: Linux x64 4.15.0-54-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz (4 x 2394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.88GB (2.98GB free)

Process Argv

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: angular_serve

OS
Linux x64 4.15.0-54-generic

CPUs
Intel Xeon E312xx (Sandy Bridge, IBRS update) (4 x 2399)

Memory (System)
7.79GB (2.39GB free)

VM
0%

Extensions (21)

Extension
Author (truncated)
Version

ng-template
Ang
0.800.0

jshint
dba
0.10.20

vscode-eslint
dba
1.9.0

gitlens
eam
9.8.2

EditorConfig
Edi
0.13.0

prettier-vscode
esb
1.9.0

python
ms-
2019.6.22090

typescript-javascript-grammar
ms-
0.0.50

vscode-typescript-tslint-plugin
ms-
1.2.1

vsliveshare
ms-
1.0.488

vsliveshare-audio
ms-
0.1.56

fabric8-analytics
red
0.0.12

vscodeintellicode
Vis
1.1.7

remote-containers
ms-
0.66.0

remote-ssh
ms-
0.44.0

remote-ssh-edit
ms-
0.44.0

remote-ssh-explorer
ms-
0.44.0

remote-wsl
ms-
0.38.7

vscode-remote-extensionpack
ms-
0.15.0

debugger-for-chrome
msj
4.11.6

scala
sca
0.3.4

Is it reproducible without extensions?
To try this you can open Command Palette (F1 or Ctrl + Shift + P) and pick Developer: Reload Window With Extensions Disabled

Does this happen in the latest insiders too?
/cc @joaomoreno

@mjbvz this happened for a brief time period when version 1.37 was released initially, within an hour of release the rollback to 1.36 was released (with 1.36 this issue was not reproducible).
With newer release 1.37 this issue is not reproducible.


package conflicts

Hi,
I have been trying to install rosella through conda. Conda is updated and I created a python 3.9 environment. However, I get package conflicts such as:
Package zlib conflicts for:
rosella -> zlib[version='>=1.2.11,<1.3.0a0']
python=3.9 -> zlib[version='>=1.2.11,<1.3.0a0|>=1.2.12,<1.3.0a0|>=1.2.13,<1.3.0a0']
...and many more. Sorry, maybe this is not a rosella issue, but maybe you have an idea what it could be. Edit: This also occurred in python 3.8
Thanks!

Hello!
Thanks for checking out Rosella. This kind of seems like your conda channels might be out of order. Would you please be able to post the contents of your ~/.condarc file? It should look something like this:
channels:
  - bioconda
  - conda-forge
  - defaults

Hello, thanks for the fast reply.
Yes, I really could have thought of that myself, conda-forge was missing.
It worked now, thanks a lot!


dracut: remove systemd-tmpfiles-setup from initramfs

Although no unit depends on systemd-tmpfiles-setup.service explicitly, it gets sometimes pulled in automatically for some reasons. As a result, the initramfs has both systemd-tmpfiles-setup-dev.service and systemd-tmpfiles-setup.service, so units like systemd-resolved.service cannot start because of an ordering cycle issue. That's the case especially for ARM64 architecture.
To fix that, let's remove systemd-tmpfile-setup.service from the initramfs.

I wonder why there is a circle and both do not coexist well in the initramfs.
The change looks ok as it is not enabled currently.
I checked the output of systemd-tmpfiles --cat-config inside the initramfs to see if there is anything that we might need (excluding the /dev entries which are created) and some files were created by the tools itself other are missing and may not cause problems now because we don't make use of them. It is good to keep in mind that we forcefully disabled it if something breaks later because it depends on it.


❤ New Ownership requested

It's time! I believe I'm going to do this for all my addons, but it's definitely time to set them free. I don't really have much of a vision of going forward on this, and am mostly maintaining. I think this makes the most sense to be owned by the larger ember community (because of its generality), but I don't think that really exists.
Anyhoo, thanks for everyone who's contributed- y'all are great!

My company uses this addon in production. I'm willing to take it over and keep it maintained and updated. Thanks for all the hard work! Let's chat on Discord. I'm @Alon on there.

@tim-evans I am still up for taking over control of this :)

Hi, yes, I was waiting for @melsumner to respond to my cross post here https://discuss.emberjs.com/t/new-maintainers-owners-requested/15768/3

@tim-evans sounds good. You want to move the repo to the adopted ember addons repo. And then I would apply there?

@Alonski I think that may be best ❤, since I don't want to have an ad-hoc process for each of my addons.

Ok sounds great. Good luck and thanks for everything @tim-evans !

@Alonski I've invited you to the org :+1:

@MelSumner so can I just start "owning" this repo/library? Do we have an org on NPM as well that we have publish rights to?

@tim-evans Thanks for everything! This is a great addon and your work is really appreciated!


Model catalog importing and sorting

Is your enhancement related to a problem? Please describe
Models are typically sorted alphabetically by source namespace, except when you import a model:

When you import a model, you have to give it a name to be sorted by:

This can lead to models being harder to find.
Describe the solution you'd like
Have the import form updated to default to naming the entry local-import/<model name> instead of just <model-name> (or something similar) or perhaps have it be a separate field to provide the import namespace.
Describe alternatives you've considered
Users can do this themselves, but there is no default or prompted namespace and they probably won't realized the need until after running into sorting issues.
Additional context
No response

We updated the way we sort models by default, with the following rules:

At the top, the models in use (inference servers)
Then the models downloaded
Finally models available

See https://github.com/containers/podman-desktop-extension-ai-lab/pull/851 for ref


Disabled Account Detection won't fire

Describe the bug
For this detection: https://github.com/Azure/Azure-Sentinel/blob/master/Detections/SigninLogs/DisabledAccountSigninsAcrossManyApplications.yaml
I think line 31 should be
| where count_ >= threshold
Screenshots
No results:

Success with modified code:

@aew-takeahike - Thanks for the feedback.  We have set the threshold related to the number of distinct applications where the disabled account attempted to sign into.  Because this is an Alert, we don't want to fire unless we have a higher confidence level.  You are welcome to modify the alert with your own parameters, I would suggest modifying the let statement for the threshold to something lower.  If you set it to 1, then you would also receive the alert.  We will keep an eye on the feedback for this one and can certainly change the default threshold if that is what is desired by the community.  Thanks, Shain


Set document conditionally

Description
// Definition
#let authors = context document.author.len()

// Output
Authors: #authors

// Error A (no error and nothing in about dialog)
#set document(author: "test") if authors == 0

// Error B (no error and nothing in about dialog)
#if (authors == 0) { set document(author: "test"); [Done] }

Reproduction URL
No response
Operating system
Windows
Typst version

[X] I am using the latest version of Typst

In your example, authors is of type content, not int so all the comparisons return false. Everything that depends on the contextual information needs to be inside of the context expression.
That said, before https://github.com/typst/typst/pull/4768 was merged (which I coincidentally was just working on as you opened the issue) this still wouldn't have worked due to other bugs.
However, with it now merged, you can do it like this:
#set document(author: "Normal")
#context {
  set document(author: "Changed") if "Normal" in document.author
}

Note that document set rules are a special case here. Usually having a set rule without any following content in the same block is pointless because the set rule is scoped to the code block. However, because the document is a singleton, scoping does not make sense. So for document set rules, the last one just wins.
For other kinds of set rules, you'd usually have a setup like this, with an "everything show rule":
#set document(author: "Normal")
#show: body => context {
  set text(red) if "Normal" in document.author
  body
}
Hi there!


Update codeql-analysis.yml

Upgrade codeQL action to v2 as per https://github.blog/changelog/2022-04-27-code-scanning-deprecation-of-codeql-action-v1/

@sullivanmatt another one for you 👍

Thanks again!


The reward value did not decrease.

When I run the demo ( step3_rlhf_finetuning/training_scripts/opt/single_node/run_1.3b.sh) without any change , the reward dose not increase.  Is it normal? I would appreciate it if anyone can provide a normal reward curve .

this is my reward curve

this is my critic_loss


Completed todos and bugfixes,  also migrated from Ivy on Gradle

Vaadin Page.Styles has not ability to remove added css, i fixed remove methods in this plugin, and replace Ivy with Gradle. Compiled and tests with vaadin 7.4.3.

Hi!
I’m terribly sorry for not reacting to this right away, and then forgetting all about it for this long!
Unfortunately I do not want to accept this patch as-is. I really appreciate the added removeStyleSheet functionality, but I don’t wish to switch from Ivy to Gradle. Not in the same pull request at least.
So if you wish, you can submit a new pull request with just the removeStyleSheet additions, and if you really want to, another pull request with the changes to move from Ivy to Gradle (and some compelling reasons why it would be a great thing ;)).
Thanks!

As #9 already implements the removeStyleSheet functionality and converts the project from Ivy to Maven, I’m closing this PR. Thanks anyway!


Itent for interaction with external application

Design of Intents for interaction with Tasker and Automate (as well as other automation application for Android) has started, details here (https://github.com/souliss/souliss/wiki/SoulissApp-Intents).

+1 Good!
2015-10-27 22:01 GMT+01:00 Dario Di Maio<EMAIL_ADDRESS>
Design of Intents for interaction with Tasker and Automate (as well as
other automation application for Android) has started, details here (
https://github.com/souliss/souliss/wiki/SoulissApp-Intents).
—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/96.

https://github.com/souliss/souliss/wiki/SoulissApp-API

Ok Automate its installed, waiting your apk update =)
Regards
2015-10-28 0:51 GMT+01:00 Alessandro Del Pex<EMAIL_ADDRESS>
https://github.com/souliss/souliss/wiki/SoulissApp-API
—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/96#issuecomment-151677781.

Juan you're always up to date :)

I try! :P I not seen yet the "it.angelic.receivers.AutomateReceiver" on
Receiver Class :(
Regards
2015-10-28 11:30 GMT+01:00 Alessandro Del Pex<EMAIL_ADDRESS>
Juan you're always up to date :)
—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/96#issuecomment-151794593.

Yes, it will be in next version
Ale
Il 28/ott/2015 16:15, "juanpintom"<EMAIL_ADDRESS>ha scritto:

I try! :P I not seen yet the "it.angelic.receivers.AutomateReceiver" on
Receiver Class :(
Regards
2015-10-28 11:30 GMT+01:00 Alessandro Del Pex<EMAIL_ADDRESS>
Juan you're always up to date :)
—
Reply to this email directly or view it on GitHub
<https://github.com/souliss/soulissapp/issues/96#issuecomment-151794593
.

—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/96#issuecomment-151877846.


feat: GcpNfsVolumeRestore

Description
Changes proposed in this pull request:

GCP NFSVolume Restore

Related issue(s)
https://jira.tools.sap/browse/PHX-91

/retest


Add BindingSets util for quick convenience processing of tuple query results

For example to quickly get all values for one particular variable out of a query result.

Hi,
We (Me and @shubhi0108) would like to work on this issue. Can you please elaborate more on the issue. We know that when the query is evaluated, the result goes in TupleQueryResult, and then in order to get the values we can iterate over the result to get BindingSets for each row. Now, how do we want to processes the tuples further?

Sure thing! The idea for this issue was to have a new convenience function for working with tuple query results. I originally thought a separate BindingSets class, but thinking about it a bit more, I think adding a function to the QueryResults util makes more sense.
For example, I'd like to be able to do something like this:
 String query = "SELECT ?x ?y ?z { ?x ?y ?y }";
TupleQueryResult result = conn.prepareTupleQuery(query).evaluate();

 List<Value> valuesOfX = QueryResults.getAllValues(result, "x");

so that valuesOfX would contain all values for variable ?x produced by the query.
Of course you can do this kind of thing already using a stream and a lambda:
  List<Value> valuesOfX = result.stream().map(bs -> bs.getValue("x")).collect(Collectors.toList());

I'll be honest by the way that when I first wrote this issue I hadn't considered that it's already pretty easy to what I wanted using lambdas and streams, so there is less urgency for this. But a util function makes it a little bit easier, so it's still a useful addition.

Great that you want to contribute by the way. Before you get started, please have a look at the contributor guidelines, in particular the points on how to sign the Eclipse ECA, and how to do commits and pull requests. Let me know if you need any help with any of it.

Hi,
We have added the asked function and a test for the same. According to our implementation, the function getAllValues() returns null when the user enters the binding element that does not exist in the result. Should there be some exception thrown or returning null is fine?

We have added the asked function and a test for the same. According to our implementation, the function getAllValues() returns null when the user enters the binding element that does not exist in the result. Should there be some exception thrown or returning null is fine?

I wouldn't throw an exception, but perhaps you can return an empty list instead of null?

Hi,
Please let me know whether some work in left regarding this issue.
Thanks

All good, thanks. Normally issues close automatically when the PR is merged, not sure why this one didn't. Closing now to mark resolved.


unit64 is a typo still in the spec

unit64 was a typo introduced really early in the code, and should have been uint64. Most uses have been fixed but the spec is still wrong. This has not been caught before cause decoding actually has a catch all so you can write anything and it will be handled as a uint64 in a varint anyway.
This branch fixes the last typo.

Thank you @cjkjellander


Kernel support of ipset is missing

Kernel support of ipset is missing.
$ sudo apt-get update
$ sudo apt-get install ipset
$ sudo ipset create blacklist hash:ip hashsize 4096
ipset v6.23: Kernel error received: Invalid argument

I’ve created a Debian Jessie server and an Ubuntu (default choice) server on Scaleway and I’m getting this problem right now.

any update on this issue ?


Accordion: enable nested accordions

This pull request addresses #266.
Now accordion items are correctly associated with their accordion container element. Thus, inner children do not trigger an outer-accordion toggle anymore.

Hey @jneuendorf,
Thanks for the PR! Awesome job.
Can you please add an example of a nested accordion (we can style it afterwards) to showcase it?
You can add it here inside an example block: https://github.com/themesberg/flowbite/blob/main/content/components/accordion.md
Then I will check the PR again and most likely merge it.
Cheers,
Zoltan

I added the docs.
However, I couldn't check if the new code is working because the local docs after yarn build load the remote JS of the latest public version instead of new sources.

Thanks @jneuendorf for the contribution <3
Merged and will be added + tagged in the next release notes.

@zoltanszogyenyi  Hi, this fix available for yarn? I updated to<EMAIL_ADDRESS>using yarn and still see this bug.
On https://yarnpkg.com/package/flowbite it says that latest version 1.6.5
Thanks!

Sorry I'm wrong, on https://yarnpkg.com/package/flowbite  it says latest version is 1.6.4
It would be great if someone can upload it to yarn so I can use it :)

One more addition, I maybe wrong somewhere, but I checked node_modules folder, it says I have:
"name": "flowbite",
"version": "1.6.5",
In blog/node_modules/flowbite/package.json
But I still have problem described in https://github.com/themesberg/flowbite/issues/266

Another update.
I changed data-accordion="collapse" to data-accordion="open" in all places, and now I can open child accordions and parent not closing. In my case it's what I was looking for.
Just in case if someone will be looking for it. Template looks like this:

    <button type="button" class="flex items-center justify-between w-full p-5 font-medium text-left text-gray-500 border border-b-0 border-gray-200 rounded-t-xl focus:ring-4 focus:ring-gray-200 dark:focus:ring-gray-800 dark:border-gray-700 dark:text-gray-400 hover:bg-gray-100 dark:hover:bg-gray-800" data-accordion-target="#accordion-collapse-body-1" aria-expanded="true" aria-controls="accordion-collapse-body-1">
      What is Flowbite?
      <svg data-accordion-icon class="w-6 h-6 rotate-180 shrink-0" fill="currentColor" viewBox="0 0 20 20" xmlns="http://www.w3.org/2000/svg"><path fill-rule="evenodd" d="M5.293 7.293a1 1 0 011.414 0L10 10.586l3.293-3.293a1 1 0 111.414 1.414l-4 4a1 1 0 01-1.414 0l-4-4a1 1 0 010-1.414z" clip-rule="evenodd"></path></svg>
    </button>

Flowbite is an open-source library of interactive components built on top of Tailwind CSS including buttons, dropdowns, modals, navbars, and more.

Check out this guide to learn how to get started and start developing websites even faster with components on top of Tailwind CSS.

What are the differences between Flowbite and Tailwind UI?

          <button type="button" class="flex items-center justify-between w-full p-5 rounded-t-xl font-medium text-left text-gray-500 border border-b-0 border-gray-200 focus:ring-4 focus:ring-gray-200 dark:focus:ring-gray-800 dark:border-gray-700 dark:text-gray-400 hover:bg-gray-100 dark:hover:bg-gray-800" data-accordion-target="#accordion-nested-collapse-body-1" aria-expanded="false" aria-controls="accordion-nested-collapse-body-1">
            Open source
            <svg data-accordion-icon class="w-6 h-6 shrink-0" fill="currentColor" viewBox="0 0 20 20" xmlns="http://www.w3.org/2000/svg"><path fill-rule="evenodd" d="M5.293 7.293a1 1 0 011.414 0L10 10.586l3.293-3.293a1 1 0 111.414 1.414l-4 4a1 1 0 01-1.414 0l-4-4a1 1 0 010-1.414z" clip-rule="evenodd"></path></svg>
          </button>

The main difference is that the core components from Flowbite are open source under the MIT license, whereas Tailwind UI is a paid product.

          <button type="button" class="flex items-center justify-between w-full p-5 font-medium text-left text-gray-500 border border-b-0 border-gray-200 focus:ring-4 focus:ring-gray-200 dark:focus:ring-gray-800 dark:border-gray-700 dark:text-gray-400 hover:bg-gray-100 dark:hover:bg-gray-800" data-accordion-target="#accordion-nested-collapse-body-2" aria-expanded="false" aria-controls="accordion-nested-collapse-body-2">
            Architecture
            <svg data-accordion-icon class="w-6 h-6 shrink-0" fill="currentColor" viewBox="0 0 20 20" xmlns="http://www.w3.org/2000/svg"><path fill-rule="evenodd" d="M5.293 7.293a1 1 0 011.414 0L10 10.586l3.293-3.293a1 1 0 111.414 1.414l-4 4a1 1 0 01-1.414 0l-4-4a1 1 0 010-1.414z" clip-rule="evenodd"></path></svg>
          </button>

Another difference is that Flowbite relies on smaller and standalone components, whereas Tailwind UI offers sections of pages.

          <button type="button" class="flex items-center justify-between w-full p-5 font-medium text-left text-gray-500 border border-gray-200 focus:ring-4 focus:ring-gray-200 dark:focus:ring-gray-800 dark:border-gray-700 dark:text-gray-400 hover:bg-gray-100 dark:hover:bg-gray-800" data-accordion-target="#accordion-nested-collapse-body-3" aria-expanded="false" aria-controls="accordion-nested-collapse-body-3">
            Can I use both?
            <svg data-accordion-icon class="w-6 h-6 shrink-0" fill="currentColor" viewBox="0 0 20 20" xmlns="http://www.w3.org/2000/svg"><path fill-rule="evenodd" d="M5.293 7.293a1 1 0 011.414 0L10 10.586l3.293-3.293a1 1 0 111.414 1.414l-4 4a1 1 0 01-1.414 0l-4-4a1 1 0 010-1.414z" clip-rule="evenodd"></path></svg>
          </button>

We actually recommend using both Flowbite, Flowbite Pro, and even Tailwind UI as there is no technical reason stopping you from using the best of two worlds.

Learn more about these technologies:

Flowbite Pro

Tailwind UI

    <button type="button" class="flex items-center justify-between w-full p-5 font-medium text-left text-gray-500 border border-gray-200 focus:ring-4 focus:ring-gray-200 dark:focus:ring-gray-800 dark:border-gray-700 dark:text-gray-400 hover:bg-gray-100 dark:hover:bg-gray-800" data-accordion-target="#accordion-collapse-body-2" aria-expanded="false" aria-controls="accordion-collapse-body-2">
      Is there a Figma file available?
      <svg data-accordion-icon class="w-6 h-6 shrink-0" fill="currentColor" viewBox="0 0 20 20" xmlns="http://www.w3.org/2000/svg"><path fill-rule="evenodd" d="M5.293 7.293a1 1 0 011.414 0L10 10.586l3.293-3.293a1 1 0 111.414 1.414l-4 4a1 1 0 01-1.414 0l-4-4a1 1 0 010-1.414z" clip-rule="evenodd"></path></svg>
    </button>

Flowbite is first conceptualized and designed using the Figma software so everything you see in the library has a design equivalent in our Figma file.

Check out the Figma design system based on the utility classes from Tailwind CSS and components from Flowbite.

@alex223125 I think, the fix has just net yet been released. Looking at

https://github.com/themesberg/flowbite/releases/tag/v1.6.5 and
https://github.com/themesberg/flowbite/compare/v1.6.5...main

the changes of this PR will probably be contained in v1.6.6


rofi: fix default path

use configured value instead of assuming XDG default

Looks good to me, merged into master: https://github.com/rycee/home-manager/commit/782d2fab83fe1964e220f5b343d68659b9dd9cf2.


Run and Debug is not working as expected

Issue Type: Bug
After the update today, Run and Debug is not working as expected
I have a pytorch checkout and I'm just trying to debug test_boolean_tensor for example. Its impossible to enter the prepare_fx step into the prepare_fx function. It even gives bogus error messages that don't show up normally. Earlier this wasn't a problem.
I generally just put
if name == "main":
a = TestQuantizeFxOps()
a.test_boolean_tensor()
(its converting the underscores to bold)
to the bottom of the test file, add a breakpoint in prepare_fx (another file), and then click Run and Debug but as of the recent update, its just not hitting that breakpoint. It WILL hit it if I put the breakpoint in the test file, but then I still can't step into prepare_fx
expected: step into prepare_fx
actual: it steps over prepare_fx
This was working earlier today and I can't get it to work at all now, was worried something was wrong with my checkout but the bug stays even on master and after rebuilding pytorch
Version: 1.58.1
Commit: 2aeda6b18e13c4f4f9edf6667158a6b8d408874b
Date: 2021-07-13T06:22:33.013Z (17 hrs ago)
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.5.0
VS Code version: Code 1.58.1 (2aeda6b18e13c4f4f9edf6667158a6b8d408874b, 2021-07-13T06:22:33.013Z)
OS version: Darwin x64 20.5.0
Restricted Mode: No
Remote OS version: Linux x64 5.2.9-229_fbk15_hardened_4185_g357f49b36602

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 3, 3

Memory (System)
32.00GB (0.19GB free)

Process Argv
--crash-reporter-id b5c82189-01d2-4e8f-b09c-a17b7c537d71

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: devgpu108.ash6.facebook.com

OS
Linux x64 5.2.9-229_fbk15_hardened_4185_g357f49b36602

CPUs
Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz (56 x 2457)

Memory (System)
251.71GB (11.11GB free)

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

vscode-cudacpp
kri
0.1.1

remote-containers
ms-
0.187.0

remote-ssh
ms-
0.65.7

remote-ssh-edit
ms-
0.65.7

remote-wsl
ms-
0.58.2

vscode-remote-extensionpack
ms-
0.21.0

rainbow-brackets
2gu
0.0.6

git-tree-compare
let
1.10.2

python
ms-
2021.6.944021595

vscode-pylance
ms-
2021.7.2

jupyter
ms-
2021.8.1013163132

cpptools
ms-
1.5.1

rainbow-brackets-2
tej
1.1.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspyt653:30270858
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30311712
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30335481
vscod805:30301674
pythonvspyt200:30331937
vscextlangct:30333562
binariesv615:30325510
vsccppwt:30329788
bridge0708:30335490

/extPython


feat: make tensor_ordering utilities more configurable

Summary
This makes the tensor_ordering utilities a bit easier to use and enables us to get rid of some private method usage in other parts of the stack.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

23 of 23 (100.0%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 85.696%

Files with Coverage Reduction
New Missed Lines
%

qiskit_nature/second_q/operators/electronic_integrals.py
1
89.82%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
17050

Relevant Lines:
19896

💛  - Coveralls

@Mergifyio requeue

@Mergifyio refresh


feat(input): DLT-1808 icon scoped slot

Add icon scoped slot to input
Obligatory GIF (super important!)

:hammer_and_wrench: Type Of Change
These types will increment the version number on release:

[x] Feature

:book: Jira Ticket
https://dialpad.atlassian.net/browse/DLT-1808
:book: Description

Added iconSize scope to icon slot to be able to keep the icon size in sync with the input.
General CSS cleanup of input.less

:bulb: Context

A while ago when we changed the way we were handling icons, forgot to update input accordingly, so the icon sizes where not being handled correctly.

:pencil: Checklist
For all PRs:

[x] I have ensured no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] I have reviewed my changes.
[x] I have added all relevant documentation.
[x] I have considered the performance impact of my change.

For all Vue changes:

[x] I have made my changes in Vue 2 and Vue 3. Note: you may sync your changes from Vue 2 to Vue 3 (or vice versa) using the ./scripts/dialtone-vue-sync.sh script. Read docs here: Dialtone Vue Sync Script

For all CSS changes:

[x] I have used design tokens whenever possible.

:camera: Screenshots / GIFs

Size
Before
After

XS

SM

MD

LG

XL

Links

Input component - Dialtone docs
DtInput - Dialtone Vue 2
DtInput - Dialtone Vue 3

huh, seems like sth change here
Actual:

Previous:

https://dialtone.dialpad.com/components/input.html#icon-sizes
Not sure if it is intendeed, I was looking that it was missaligned and thats probably because a missing line-height:1 in textarea.
Without line-height:

With line-height:

There is padding issues probably also because the icons size is updated.
Previous:

Current:

IIRC the icon was intentionally aligned to the vertical center when it was a textarea

There is padding issues probably also because the icons size is updated.
Previous:

Previous actually looks incorrect here, it is not reflecting what the labels are saying.

Previous actually looks incorrect here (at least for icon size). it is not reflecting what the labels are saying.

Yes, thats ok, I mean the margin between the icon and the text.

I see ok this update, also love the cleaning here.
Cool to see this is working properly now.
If my comments about the change on marging are ok from design perspective, I will approve it, lets wait a little bit

IIRC the icon was intentionally aligned to the vertical center when it was a textarea

Doesn't work that way, at least on storybook. I have a vague memory about wanted it vertically centered too, but not really sure.
https://dialtone.dialpad.com/vue/index.html?path=/story/components-input--with-both-icons&args=type:textarea

There is padding issues probably also because the icons size is updated.
Previous:
Current:
Previous:
Current:
Previous:
Current:

All of those icons are aligned to the left, as the icon size is different seems like the spacing is different but it isn't.
Certainly we need the design perspective here.
@francisrupert @fede-dp

Doesn't work that way, at least on storybook. I have a vague memory about wanted it vertically centered too, but not really sure.

hmm alright maybe we changed it..

We should be a bit careful about updating this in product due to the removal of classes. Could possibly break something that was still referencing those old classes.

Sure thing, would be cool to heads up this in the Dialtone update ticket.

Alright, will merge this and put a note on next weeks Dialtone update ticket.


Omnisharp support for .NET Core localized Intellisense

Can Omnisharp team help confirm if it supports the new localized Intellisense for .NET Core in VS Code that was released earlier this month or there needs to be a fix taken to make the localized Intellisense work?
Guidance: https://docs.microsoft.com/en-us/dotnet/core/install/localized-intellisense
Related Issue: https://github.com/dotnet/core/issues/4032#issuecomment-568908920
The localized XMLs are located in the following subdirectory (as per language code) for say .NET Core 3.0:
...\dotnet\packs\Microsoft.NETCore.App.Ref\3.0.0\ref\netcoreapp3.0<lang code>

@vivmishra I downloaded the .NET Core 3.1 French language pack and installed it according to the guidance. Opening a netcoreapp3.1 project in VS Code I do not see localized intellisense. I can see from the OmniSharp log that it is running with the French culture.

OmniSharp Log
Starting OmniSharp server at 07/01/2020 à 12:28:04
    Target: c:\Users\jorobich\source\repos\test1
OmniSharp server started.
Path: C:\Users\jorobich.vscode-insiders\extensions\ms-vscode.csharp-1.21.9.omnisharp\1.34.9\OmniSharp.exe
PID: 3924
    Starting OmniSharp on Windows 6.2.9200.0 (x64)

    DotNetPath set to dotnet

    Located 5 MSBuild instance(s)
        1: Visual Studio Enterprise 2019 16.5.29521.150 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin"
        2: Visual Studio Enterprise 2017 15.9.28307.960 - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin"
        3: Visual Studio Enterprise 2019 16.5.29703.146 - "C:\Program Files (x86)\Microsoft Visual Studio\Preview16\Enterprise\MSBuild\Current\Bin"
        4: Visual Studio Enterprise 2019 16.4.29613.14 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin"
        5: StandAlone 16.3 - "C:\Users\jorobich\.vscode-insiders\extensions\ms-vscode.csharp-1.21.9\.omnisharp\1.34.9\.msbuild\Current\Bin"

    Registered MSBuild instance: Visual Studio Enterprise 2019 16.5.29521.150 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin"

    Detecting Cake files in 'c:\Users\jorobich\source\repos\test1'.

    Could not find any Cake files

    No solution files found in 'c:\Users\jorobich\source\repos\test1'

    Queue project update for 'c:\Users\jorobich\source\repos\test1\test1.csproj'

    Detecting CSX files in 'c:\Users\jorobich\source\repos\test1'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Loading project: c:\Users\jorobich\source\repos\test1\test1.csproj

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.EditorConfigWorkspaceOptionsProvider, Order: 200

    Configuration finished.

    Omnisharp server running using Stdio at location 'c:\Users\jorobich\source\repos\test1' on host 11356.

    Successfully loaded project file 'c:\Users\jorobich\source\repos\test1\test1.csproj'.

    Adding project 'c:\Users\jorobich\source\repos\test1\test1.csproj'

    Update project: test1

    Solution initialized -> queue all documents for code analysis. Initial document count: 3.

Thanks for the follow-up. Maybe we can then keep this issue open for tracking the work to get this working.


Make pyyaml a requirement

Ruby i18n lib supports YAML by default. For this lib pyyaml is an extra requirement. I suggest to make it a requirement. With this, issues like #7, #9, #19 and #26 could be avoided.
In addition, I will suggest to load .yaml and .yml by default, instead of using i18n.set('filename_format'...), since Ruby lib also does that by default.

Seems this package is no longer maintained by the author, check out this library https://github.com/sectasy0/pyi18n

@sectasy0 Unfortunately this package does not support namespaces :/


add_new_observations has no apparent effect

Using your example code, but printing the results of predictions before and after adding new observations, I see no difference in the predictions:
>>> import pmdarima as pm
>>> from pmdarima.datasets import load_wineind

>>> y = load_wineind()
>>> train, test = y[:125], y[125:]
>>> arima = pm.ARIMA(order=(1, 1, 2), seasonal_order=(0, 1, 1, 12))
>>> arima.fit(y)
>>> predictions_before_new_observations = arima.predict(n_periods=100)
>>> print(predictions_before_new_observations)
[ 21966.69719064  25983.70920537  30225.30979849  35417.12497605
  13011.36189384  19639.41029275  21506.58177734  23674.34000129
  21685.76396121  23669.77820915  26955.35258274  22755.25064259
  19808.16136752  23578.78187736  27845.86723277  32923.89430476
  10475.68782067  17024.74537797  18831.64801826  20929.54676213
  18876.02419507  20792.575179    24011.97552646  19745.03912793
  16731.45371123  20435.40477139  24635.90945687  29647.31038012
   7132.50104453  13614.94381595  15355.23778394  17386.52472372
  15266.39195688  17116.3319192   20269.12166605  15935.57445125
  12855.37832874  16492.7186265   20626.61257859  25571.40275359
   2989.98267735   9405.81470422  11079.49792966  13044.17412588
  10857.43061599  12640.759835    15726.93883867  11326.78088062
   8179.97401491  11750.70356944  15817.9867783   20696.16621008
  -1951.86460938   4397.35667427   6004.42915649   7902.49460948
   5649.14035637   7365.85883215  10385.4270926    5918.65839133
   2705.24078239   6209.3595937   10210.03205935  15021.6007479
  -7693.04081479  -1410.43027436<PHONE_NUMBER>4   1961.4861744
   -358.47882193   1291.62891063   4244.58642786   -288.79301663
  -3568.82136879   -131.3133007    3802.74842171   8547.70636704
 -14233.54593886  -8017.54614165  -6543.69514588  -4778.85117934
  -7165.42691889  -5581.92992956  -2695.58315555  -7295.57334327
 -10642.21243865  -7271.31511379  -3403.86413459   1274.48306752
 -21573.37998161 -15423.99092763 -14016.75067508 -12318.51745176
 -14771.70393453 -13254.81768842 -10435.08165764 -15101.68258858
 -18514.93242718 -15210.64584554 -11409.80560957  -6798.06915068]

>>> arima.add_new_observations(test)  # pretend these are the new ones
>>> predictions_after_new_observations  = arima.predict(n_periods=100)
>>> print(predictions_after_new_observations)
[ 21966.69719064  25983.70920537  30225.30979849  35417.12497605
  13011.36189384  19639.41029275  21506.58177734  23674.34000129
  21685.76396121  23669.77820915  26955.35258274  22755.25064259
  19808.16136752  23578.78187736  27845.86723277  32923.89430476
  10475.68782067  17024.74537797  18831.64801826  20929.54676213
  18876.02419507  20792.575179    24011.97552646  19745.03912793
  16731.45371123  20435.40477139  24635.90945687  29647.31038012
   7132.50104453  13614.94381595  15355.23778394  17386.52472372
  15266.39195688  17116.3319192   20269.12166605  15935.57445125
  12855.37832874  16492.7186265   20626.61257859  25571.40275359
   2989.98267735   9405.81470422  11079.49792966  13044.17412588
  10857.43061599  12640.759835    15726.93883867  11326.78088062
   8179.97401491  11750.70356944  15817.9867783   20696.16621008
  -1951.86460938   4397.35667427   6004.42915649   7902.49460948
   5649.14035637   7365.85883215  10385.4270926    5918.65839133
   2705.24078239   6209.3595937   10210.03205935  15021.6007479
  -7693.04081479  -1410.43027436<PHONE_NUMBER>4   1961.4861744
   -358.47882193   1291.62891063   4244.58642786   -288.79301663
  -3568.82136879   -131.3133007    3802.74842171   8547.70636704
 -14233.54593886  -8017.54614165  -6543.69514588  -4778.85117934
  -7165.42691889  -5581.92992956  -2695.58315555  -7295.57334327
 -10642.21243865  -7271.31511379  -3403.86413459   1274.48306752
 -21573.37998161 -15423.99092763 -14016.75067508 -12318.51745176
 -14771.70393453 -13254.81768842 -10435.08165764 -15101.68258858
 -18514.93242718 -15210.64584554 -11409.80560957  -6798.06915068]

Am I missing something about how add_new_observations works?
Windows-10-10.0.17763-SP0
Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:04:45) [MSC v.1900 32 bit (Intel)]
pmdarima 1.1.0
NumPy 1.15.4
SciPy 1.2.1
Scikit-Learn 0.20.3
Statsmodels 0.9.0

Hrmm... you appear you be correct. I'll dig into this and see if I can figure out what may be going on. If you're right, this is a big problem especially for out_of_sample usage

Thanks. Glad it's not just me! I noticed that the model's endog does not get updated (which, from a quick glance at the code, it appears it should), so perhaps this is a good place to start looking.

You're right, it definitely appears that it should be working, but I suspect there is some statsmodels intricacy in the way we're updating the data that is not working as expected. This is the line in question, for any would-be watchers.
Thanks again for raising this issue!

Thanks. Glad it's not just me! I noticed that the model's endog does not get updated (which, from a quick glance at the code, it appears it should), so perhaps this is a good place to start looking.

I just spent 3 hours or so trying to figure this out. Super glad I ran into this.

It's only on seasonal Arimas. I've found where in the statsmodels code this is affected; still working on a fix.

Take a look at #109 if you want to see what the proposed fix looks like... this ended up being a mess of dealing with statsmodels internals, so the actual behavior of this method has changed to allow us to support it.

Solved in #109. Will be releasing v1.1.1 patch shortly.


Update netty version to address CVE

Updated the version of netty to address this CVE https://nvd.nist.gov/vuln/detail/CVE-2019-20444.
Since it is a patch update, existing unit tests should cover the update.
Let me know if you'd like me to create an issue to go along with this PR

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9151/
Test PASSed.

Hi @patrickofriel-wk, thanks for this change. Unfortunately, our netty dependency version is directly tied to gRPC and must match what gRPC uses under the hood, so we would need to update gRPC as well.
We may be open to bumping grpc again, but I am not sure. @ggezer WDY think?

Looks like gRPC 1.28.1 has netty 4.1.45.Final which I believe should fix the CVE as well. Let me know if you'd like me to attempt to update that as well in this pr.

We definitely can't accept the PR in the current state. You can bump the gRPC dependency up to 1.28.1 and match the Netty version for now

Updated the gRPC version to match the version of netty without the CVE

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9152/
Test PASSed.

@patrickofriel-wk did you sign the CLA from the first comment by the alluxio-bot? If not could you do so? If you did the bot may be bugged and I'll manually remove it if I find your signature in the DB.

Just signed, thanks @ZacBlanco

alluxio-bot, merge this please

Thanks @ZacBlanco and @ggezer !


About v0.6.0

Hi,
first of all, thanks for this great and useful project :)
I'm trying to update the asm-lsp nix package to the latest version, but I realized the v0.6.0 tag does not match the Cargo.toml version attribute. Do you plan in the near future to release a new version? Because I'm not sure whether to use this tag or just the latest master commit.
Also, when running cargo tests (either on master or v0.6.0), it panics with the following stack
---- x86_parser::tests::test_populate_instructions stdout ----
thread 'x86_parser::tests::test_populate_instructions' panicked at src/x86_parser.rs:276:50:
called `Result::unwrap()` on an `Err` value: Permission denied (os error 13)
stack backtrace:
   0:     0x555555961e37 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h83d3e31f1809523c
   1:     0x555555998720 - core::fmt::write::h76573a5842288faa
   2:     0x55555597b0e5 - std::io::Write::write_fmt::h03c7f344cad83924
   3:     0x555555961c04 - std::sys_common::backtrace::print::h73765b495122298a
   4:     0x555555962ac7 - std::panicking::default_hook::{{closure}}::hfad133b7877f7d1a
   5:     0x55555596285a - std::panicking::default_hook::hb7ccbed45ddd154f
   6:     0x5555556b4147 - test::test_main::{{closure}}::hf40cc5116b9e0d00
   7:     0x5555559631bc - std::panicking::rust_panic_with_hook::h03308f3977d70e82
   8:     0x555555962f1a - std::panicking::begin_panic_handler::{{closure}}::h6543c8dd74f459e9
   9:     0x555555962066 - std::sys_common::backtrace::__rust_end_short_backtrace::h68617e661e847078
  10:     0x555555962c64 - rust_begin_unwind
  11:     0x55555560e925 - core::panicking::panic_fmt::hf7f647d933c4266a
  12:     0x55555560ee53 - core::result::unwrap_failed::hea2b65c1fd5e91f1
  13:     0x55555562244d - asm_lsp::x86_parser::tests::test_populate_instructions::hdeaefc124e47f77e
  14:     0x5555556250e9 - core::ops::function::FnOnce::call_once::h594ca467f03d54cd
  15:     0x5555556ba32f - test::__rust_begin_short_backtrace::hebeab2082d02321e
  16:     0x5555556b39ce - test::types::RunnableTest::run::h5fdfad28f3276824
  17:     0x5555556ba49e - test::run_test_in_process::h99cb0c08e49cd7df
  18:     0x5555556e1feb - std::sys_common::backtrace::__rust_begin_short_backtrace::hdc599a0a67a37f33
  19:     0x5555556b054a - core::ops::function::FnOnce::call_once{{vtable.shim}}::h281a5c3954151894
  20:     0x555555952475 - std::sys::pal::unix::thread::Thread::new::thread_start::h0838e25cb6831d7f
  21:     0x7ffff77be272 - start_thread
  22:     0x7ffff7839dcc - __GI___clone3
  23:                0x0 - <unknown>

I know it's a Nix-related issue since running the same outside the Nix build process works, but maybe you have a clue about the error.
Thanks

Hi, really glad to hear you're enjoying the project!

Do you plan in the near future to release a new version? Because I'm not sure whether to use this tag or just the latest master commit.

I was planning on giving the owner time to review the last couple pending PRs before pushing another release. I could look into pushing a an 0.6.1 release in the meantime if that would be helpful :). Otherwise, I would recommend pulling off of the master branch for now.

Also, when running cargo tests (either on master or v0.6.0), it panics with the following stack

Interesting, thanks for the report! I'm not super familiar with Nix so I can't try to recreate the issue myself now. However, looking at the code it appears to be the call to fs::create_dir_all inside get_cache_dir: https://github.com/bergercookie/asm-lsp/blob/0a274567e908c1ae293300c177c0b62ccd454720/src/x86_parser.rs#L529-L549
It looks like the test tried to create the missing pieces along the path ~/.cache/asm-lsp and ran into a permissions error. Is there something in your config that's restricting writes along this path?

Thanks for the prompt response!
After setting up the environment variable and pointing it to a writable location, the test works
Regarding the version, as you wish: creating a v0.6.1 is fine; otherwise, I can wait until the next planned version.


feat(api): improve error message on conflict error

What this PR changes/adds
Changes the message in the response when the error on service layer is Conflict
Why it does that
The prev implementation sends a generic message Object exists on conflict error which is confusing
in request like delete.
Further notes
The ObjectExistsException has been renamed to ObjectConflictException  and instead of generic message
Object of type {} already exists with  it forward the error messages coming from the ServiceFailure`
Linked Issue(s)
Closes #2344
Checklist

[ ] added appropriate tests?
[x] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

Codecov Report
Base: 64.64% // Head: 64.62% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (a19da63) compared to base (fffdeb4).
Patch coverage: 54.54% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2348      +/-   ##
==========================================
- Coverage   64.64%   64.62%   -0.02%
==========================================
  Files         830      830
  Lines       17413    17411       -2
  Branches     1086     1085       -1
==========================================
- Hits        11256    11252       -4
- Misses       5708     5710       +2
  Partials      449      449

Impacted Files
Coverage Δ

...e/edc/web/jersey/mapper/EdcApiExceptionMapper.java
100.00% <ø> (ø)

...edc/web/spi/exception/ObjectConflictException.java
0.00% <0.00%> (ø)

...se/edc/web/spi/exception/ServiceResultHandler.java
0.00% <0.00%> (ø)

...actdefinition/ContractDefinitionApiController.java
100.00% <100.00%> (ø)

...protocol/ids/serialization/IdsTypeManagerUtil.java
75.00% <0.00%> (-0.61%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update the networkState RPC with the latest networking change

First of all, we can now have multiple active connections to the same node, so the RPC query should be updated to show multiple addresses when that happens.
Additionally, we should also add a lot of things to this query: the list of notification streams open, the ongoing requests, and so on.
Tackling this issue consists in figuring out exactly what can be added, knowing that the point of this query is to show to humans what the current networking state is.

Wasn't the idea to deprecate this RPC endpoint? Or was this a different one?

Yeah, rename it: #5541
Gav mentioned that he was looking at it from time to time, and it might indeed not be a bad idea to leave an RPC query for people to look at what their node is doing (as long as we're pretty clean on the fact that what is returned is unstable).

Issue still relevant and important.


[Event Request] Codeunit 10750 "SII XML Creator" - FillThirdPartyId

Describe the request
Please add the IsIntraCommunity within the OnFillThirdPartyIdOnBeforeAssignValues Event
    local procedure FillThirdPartyId(var XMLNode: DotNet XmlNode; CountryCode: Code[20]; Name: Text; VatNo: Code[20]; BackupVatId: Code[20]; NeedNombreRazon: Boolean; IsIntraCommunity: Boolean; IsNotInAEAT: Boolean; IDTypeInt: Enum "SII ID Type"; SIIDocUploadState: Record "SII Doc. Upload State")
    var
        TempXMLNode: DotNet XmlNode;
        IDType: Text[30];
    begin
        OnFillThirdPartyIdOnBeforeAssignValues(SIIDocUploadState, CountryCode, Name, VatNo);

New Integration Event with added Boolean:
   [IntegrationEvent(false, false)]
    local procedure OnFillThirdPartyIdOnBeforeAssignValues(SIIDocUploadState: Record "SII Doc. Upload State"; var CountryCode: Code[20]; var Name: Text; var VatNo: Code[20];IsIntraCommunity: Boolean)
    begin
    end;

Additional context
As we use the Vat Registration No., County Code which could differ from the "Buy-to Vendor" we need to inject the correct data including the IsIntraCommunity before writing the Information.
Internal work item: AB#536600

Availability update: We will publish a fix for this issue in the next update for release 24.
Build ID to track: 20594.


Is there a way to access the underlying schema rules?

I've recently been considering switching to this library for our app's validation. In certain parts of the UI there is a need to display the input rules for the user (i.e: the maximum allowed text length in an input field). Is there a way to access rules (i.e: max length, min length) of a schema after creating it?

We are working on that in #211

Perfect. You have created one of the best validation libraries out there, with this feature added i would put it on top of the list. Thank you!

I will try to ship this feature next weekend

This should now be possible due our new reflection API.


Delete .validation file for baidu devtool

Deleting this .validation file to empty out the baidu directory.
Microsoft Reviewers: Open in CodeFlow

Duplicate.  Closing.


RingBuffer.getCursor()

Up to 64-bit, more than supposed，and Now use slow to cover the consumption, the problem how should we do？

I'm sorry I don't understand the issue that you have raised.  Do you think that you could clarify the issue.

Closing due to lack of information.


pull request for e2e test at 12/03/2016 20:45:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Specify MVP and release date

As a project owner,
I'd like to collect all the required functionality for the MVP release
so that we could line up the work needed and create the stories to capture them in GitHub.
A/C

List of minimal valuable functionalities are gathered.
With all the stories determined the MVP release date is agreed upon.

MVP due date has been agreed on to be 16th Oct 2017.


Patch 7

These edits are from my PM and are good to publish.

#sign-off

Will these edits go live this morning? OR do I need to do something else to get them published?

Do not merge.


Enable access to camera and microphone

...if possible in System WebView.
At least with the option to revoke/disable access.
Check on https://test.webrtc.org/

This opens up some concerns:

when a user installs the app, they see that the app wants access to camera and microphone - immediate red flags for a "privacy oriented" app!
how can the user be absolutely sure that web apps can't sneakily access camera/mic while running? In future, when Service Workers are implemented in WebView, they could in theory do this even when the app isn't running!

One solution for permissions would be a plugin (or plugins), just as Automate does this, and here you can find instructions about how to do this. I hope they help. Another, simpler, would be an explanation in the app description at Play Store / f-droid repo.
I don't know how this would work when using WebView, but Chrome (which the WebView is based on) asks a user when a site requests camera and microphone for the first time and there's the notification while they are being accessed. If a user doesn't trust a web site, they simply won't allow it the access.

I agree. Privacy is important but the users should be able to decide if the website can access the camera and microphone.

Yeah, for instance, I was hoping to use this app as a way to sandbox a Google login and spoof a desktop UA to use Google Meet (because of course mobile UAs are blocked to download the app) for a work-related call. That sounds like a pretty privacy-oriented way to go about certain things like how I use container tabs in Firefox on desktop.

One solution is to have a separate fork of WebApps that makes a few concessions, like requesting location, camera, mic, etc. Then your critical apps can run in WebApps, but your media and navigation, etc. can run in the other.
Turns out, I already have such a fork: WebMediaShare https://github.com/tobykurien/WebMediaShare - it does not currently request those additional permissions, but that could be added. It behaves a bit differently to WebApps, hence the fork, but it still sandboxes the web apps and blocks 3rd party cookies and referrers.
Would that work?

Sure, but doesn't each web app independently request access to location, camera, etc. anyways? Wouldn't you just be giving permissions for individual apps to ask permissions?

Once WebApps is given permission to camera/microphone/location, then the system WebView will have access to these, regardless of which site is loaded. There isn't an API to enable/disable camera or microphone per site loaded in the WebView, as far as I can see. Also for most users, the WebView is updated as a binary blob from Google Play, so it can't really be trusted.

Ah, I'm using Bromite's webview which is a bit better, but I was assuming webviews would work like a browser -- which you sadly can't containerize like Firefox's multi-account containers.

Turns out, I already have such a fork: WebMediaShare https://github.com/tobykurien/WebMediaShare - it does not currently request those additional permissions, but that could be added.

This user would appreciate such an addition with great gratitude and humility.

+1 but only if it possible to disable it in the options.
Alternative you could emulate them for apps which require them like anbox is trying: https://github.com/anbox/anbox/issues/727

I noticed something interesting, if you go on translate.yandex.com and click 'visual translation', the site through Webapp is able to open the camera and take a photo, however then the result is an empty page not the translated image, and viewing the original image is impossible as well.
Is it because camera is not implemented yet?

I think that's an image upload, e.g. you can compose a tweet on twitter and click to add an image, and you get the option to take a picture with the camera. However, as stated in #56 the actual upload from camera doesn't work, and I never figured out why (I wasn't sure if it was just my device, Lightning browser also had the same issue on my device at the time).


Inconsistent APIs for.create() and .update() in regards to hasMany relationships

It seems that .create() expects hasMany relationships to be defined as an array of related model instances, e.g:
let post1 = server.create('post', {...}),
    post2 = server.create('post', {...});

server.create('user', {
    posts: [post1, post2]
})

Whereas .update() expects hasMany relationships to be passed in as Collection objects, e.g:
let post1 = server.create('post', {...}),
    post2 = server.create('post', {...}),
    user = server.create('user', {...});

user.update({
    posts: new Collection('post', [post1, post2])
})

This is by the way not documented anywhere. The documentation conveniently only discusses of the more straightforward belongsTo relationship.

Actually it seems like .update() doesn't work at all with hasMany relationships...

Actually it seems like .create() doesn't work properly either with hasMany relationships: If I have:
let post1 = server.create('post', {...}),
    post2 = server.create('post', {...});

let user1 = server.create('user', {
    posts: [post1, post2]
}),

let user2 = server.create('user', {}),

user1 and user2 are now both serialized with:
"relationships": {
    "posts": {
        "data": [{"type": "posts", id: "1"}, {"type": "posts", id: "2"}]
    },
}

instead of just user1.
Alright this is probably enough reasons for me to abandon ember-mirage at this point 😣

I can see why this is frustrating. Which version of Mirage are you on? There were some improvements made in the 0-3 beta series. You can read more and see some examples in this blog post.
The ORM in 0-2 was incomplete - turned out to be hard to get all of these cases working correctly. I think we're closer.
You can look at the one-to-many example from the post to see how I normally create relationships.
The reason for the inconsistency in the array versus Collection is that, server.create actually goes through the Factory layer, whereas model.update is the "lower-level" ORM layer.

@samselikoff I was indeed on 0.2 but I just gave a shot to the beta version you mentioned. It is much much more stable, which brought back my faith in ember-mirage, so thank you for pointing this out.
I initially ran into additional issues, as I had several one-way reflexive hasMany associations, where I'd essentially either get duplicate entries or a plain and simple crash after several .update(), but all these problems went away after I declared {inverse: null} on these associations. It would have been nice to get a warning about this.

Interesting. Glad you're finding 0-3 useful.
I believe the behavior matches Ember Data - if you user: belongsTo('user') on a user model, by default that sets up an implicit inverse.

@samselikoff There are no belongsTo associations involved here. Essentially just:
// mirage/models/post.js
export default Model.extend({
    parents: hasMany('post'),
    siblings: hasMany('post'),
    related: hasMany('post')
})

If I do this with Ember Data, at least it will warn me that the inverse could not be determined as this is an ambiguous definition, whereas Mirage just silently ignores the problem.

Ah yes - thank you. You're right that I need to add warnings for ambiguous schema definitions.
In Ember Data you need to specify null inverse in this case though, right?

Yes correct, either null inverse for one way, or explicit inverse for two way.

Great, added a new issue to track this: https://github.com/samselikoff/ember-cli-mirage/issues/1065


⚠ Bofrost.lu has degraded performance

In f909ab0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2371 ms

Resolved: Bofrost.lu performance has improved in ecd951c after 29 minutes.


chore(StakeManagerProcessAccount.spec): add specs for processAccount

Checklist
Ensure you completed all of the steps below before submitting your pull request:

[ ] Added natspec comments?
[ ] Ran forge snapshot?
[x] Ran pnpm lint?
[ ] Ran forge test?
[x] Ran pnpm verify?

This has been sitting here for almost a week since a re-review was requested.
Since the corresponding job ( https://github.com/logos-co/staking/actions/runs/8264004339) is green, I"m going to merge this one.


Invalid public key input

          throw new Error(`Invalid public key input`);

It seems it from this line:
https://github.com/SoilLabs/Solana-Foam/blob/c94e8a8cf9c2d266e4812416ccfbf9fdb8ef9709/index.mjs#L33-L33
, the Fdt.metadata.address is empty

I have also encountered this problem. Can you provide a more detailed template

Yes really confused here. I tried to put in the public address for my solana address in the ftd.json's metadata->address field, but it gave me the error like: invalid transaction: Transaction failed to sanitize accounts offsets correctly

same issue.


Added animal-sniffer plugin for checking Android compatibility

Description
The animal-sniffer plugin has been added to the parent pom.xml file, which can be used to check dependencies for specific Android API level compliance. The Android API level 26 signature is from the gummy-bears library, which supports signatures from API level 19 and above.
In order to run the Animal Sniffer plugin, the command mvn animal-sniffer:check can be used.

Thanks @IanZYYap. For others looking at this PR - this is the first contribution from our Massey capstone project team working on improved Android support in our client libraries.

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

/azp run java - core - ci

/check-enforcer evaluate


ReadMe: Add history with short description on changes for each version.

Add history table to README, to give users visibility on the changes from one version to another.

Realistically, a changelog like this will only get updated if it is generated

Realistically, a changelog like this will only get updated if it is generated

Yeah! I know we use git cliff for Fluvio repo, what do you think about doing the same here?
Thinking out loud, Im not sure if we could have a PR open via CI which generates the change log and replaces the previous?


fisher: does not work with a samtools index file

Hello
unlike flank, shuffle,slop... fisher doesn't want to work with a genome file created using samtools faidx

Error: The genome file xxxx.fasta.fai has no valid entries. Exiting.

is it possible to change this ?
It's really a pity that we have to modify our existing genome files, and only for fisher.

Tool:    bedtools fisher (aka fisher)
Version: v2.26.0-45-g57b7f2c

thank you

the map tool acts like fisher, it does not want to work with a genome file created using samtools faidx.
is it possible to change this, too ?
thank you

Thanks - I will look into fixing this. Should be straightforward.

Nice, thank you.

This is fixed in master


Changed example to full path

https://github.com/MicrosoftDocs/office-docs-powershell/pull/3580

Docs Build status updates of commit be74b62:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit ce1f4bf:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit ce1f4bf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Export-SPWeb.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit f1680ab:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit f1680ab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Export-SPWeb.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Getting Error for the CLI commands to install the FHIR Loader project. (For Azure API for FHIR with FHIR-Proxy)

Hello Team,
I'm getting an error when I try to execute the script ./deployFhirBulk.bash.
I'm creating different resource group for the loader. I have different resource group for Azure API for FHIR.
I have different resource group for the FHIR-Proxy.
Getting the below error

I will really appreciate your help on this issue.
Regards,
Kedarnath Shinde

I made it work but still have this issue.
https://github.com/microsoft/fhir-loader/issues/63#issue-2272682925


Npm V1 task does not write proper output to logs

In my build pipeline I use Npm v1 task to run npm test and npm install commands. In the log output from the task I can see only a single line like:
 [command]C:\Windows\system32\cmd.exe /D /S /C "C:\BuildAgents\A\_work\_tool\node\8.11.1\x64\npm.cmd install --no-optional"

This is not sufficient for my needs I would like to see detiled logs - just exactly the logs that I can see when I start npm via cmd.exe on my local machine. I use VSTS with the "new" visual theme.

Which version of the task are you running, and what sort of build agent? I've just checked our suite of validation builds for the Npm V1 task, and they all contain the full npm logs as expected.

We use a self-hosted agent:
Agent.OS | Windows_NT
Agent.OSVersion | 10.0.14393
Agent.Version | 2.120.2

Task version 1.* (dropdown in VSTS), command Custom, exact command line:
run test -- --env=$(env) $(customOptions)

Before this command we use Use Node 8.x block (Node Tool Installer) - version speck 8.x.
Where can I check VSTS version itself? I will try to provide all necessary information so please ask if something is missing.

OK I double checked (in meanwhile we have an update to VSTS) and now we indeed get log output on completed builds. But still output is missing on ongoing builds. Now I must wait 10 minutes until command is finished and only then I can see log output - no immediate results.

Please see attached screenshot - I entered the build log after command run for 4 minutes still without any output.

I consult with my teammates and indeed on completed builds logs were always present, here we are concerned only about logs that we can see during ongoing builds. Sorry for misunderstanding.

is only the npm test not showing live console output?  or are all tasks not showing live console?
are your tests buffering output?

In the build @marcin-chwedczuk-meow describes we use mainly node steps. All of them behave like buffered on the agent. Get Sources is too quick to say if it's buffered or not.
Node commands, when run manually in cmd.exe, generate output just fine, line by line.
We use mainly: npm install --no-optional, npm test, and some custom scripts too. All output it presented only after the command finishes fully. For short tasks it's ok. But npm test (which uses TestCafe and custom reporter, not buffered) takes a lot of time, and especially for that one we'd like to see the output live. Previously (in the old VSTS UI) it worked just fine.

some things to narrow:
trying cmdline task (and run npm test) to see if that's buffering - trying to see if task or whether you're having a general signal R issue
Do F12 / devtools in the browser and see if you're getting an errors
If you "queue with diagnostics" the logs will have trace output from the agent and that will help us see if the task or the agent is buffering.

Task Utility: Command line v2 – does indeed not buffer npm output. Chrome console does not show any errors (some warning for getCodeCoverageSummary promise returning null only, not important here I think).
Diagnostic log contains some data we'd like not to share publicly. Is there something specific we should extract from the diagnostic log, anonymize our sensitive data and share with you?
What I see by comparing the two tasks (npm and command line) is that npm task first show that npm test failed, and then shows the command output.

The NPM task synchronously runs your command, buffers the output, and prints it at the end of the task.  We will be switching to async (i.e. streaming STDOUT/STDERR) but there should be no change in total duration of your step.  The only difference will be that you observe STDOUT/STDERR sooner.

Okay, thanks for clarification. Any ETA on the async?

@keithrob - thanks for confirming.  I think it should be as simple as switching a line to await tl.exec (instead of tf.execSync)?  Let me know if that's correct.  In the early days it was harder but await makes it awesome :) Regarding the task model async is a big deal as buffering gives the impression of a hang or non responsive.

@keithrob, @bryanmacfarlane: The current behavior of the npm task buffering output is also a problem for us.  We need to enable realtime output from long-running tests.  For now, we will workaround this by using a script task instead of npm.

Hello! I'm a PM over on the Azure Artifacts team. I wanted to drop in here and address some of these issues with the news that we're currently reevaluating the types of tasks we offer in Azure Pipelines, and looking to focus more on lighter-weight tasks that cover authentication and setup. In lieu of the task redesign, we're going to forego making changes to the current tasks (with a few exceptions). We hope the new tasks we spin up in the next quarter or so are easier and more helpful, be on the lookout!
An addition to my copied/pasted blurb above: The issue seen here is one of the reasons we're switching - to remove some of our unwanted/unexpected behavior in favor of simply using the scripts/command line tools from the actual protocols.

@elbatk, is there any estimate or issue that can be tracked for this redesign?

@elangelo can we have an update on this issue?

@elangelo Any update on this? I'm struggling with timeouts on long-running npm test task and cannot see the culprit due to missing logs

@kepikoi

elangelo Any update on this? I'm struggling with timeouts on long-running npm test task and cannot see the culprit due to missing logs

Try use a different task type instead, we do something like the following and it then shows output:
- task: CmdLine@2
  condition: succeeded()
  inputs:
    script: npm test
    workingDirectory: $(workingDirectory)