chore: update formatting and linting

Description
Something to think about.
This PR bootstraps a new eslint config for the repo via npm init @eslint/config, selecting react + airbnb defaults. There were a bunch of specific rules specified in the previous config (mostly react stuff) don't cause any errors. That in itself doesn't negate their value (they could have been enforcing more strict rules than the plugin:react/recommended defaults), but unless we feel very strongly about any of those rules my preference is for less config and better defaults.
Just to clarify how eslint works:

Plugins defines a set of linting rules
extends allows you to opt-in to pre-configured sets of rules (recommended by plugins, etc) without manually needing to do so in rules
rules trumps all and allows configuration of individual rules for your project

What was changed in this pull request?

.eslintrc -> .eslintrc.js
Removed lots of react rules under rules in favor of those recommended by eslint-plugin-react

Why is it necessary?

More simple config.
Fixes #___
Checklist

[ ] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[ ] Unit tests added or updated
[ ] Documentation added or updated
[ ] Example(s) added or updated
[ ] Update schema.json if there are changes to the viewconf JSON structure format
[ ] Screenshot for visual changes (e.g. new tracks or UI changes)
[ ] Updated CHANGELOG.md

One other thing I realized is that the eslint-prettier-plugin does not actually run prettier. Instead it tells eslint to ignore specific rules since prettier will take care of them. Unfortunately, I don't think that prettier has been run in some time and lots of files need to be prettified.
Our CI should run:
prettier --check
eslint

and users should run
prettier --write
eslint --fix

I'm happy to run this and update the workflow accordingly.

I'm going to merge and open a separate PR to run prettier/eslint.


Bulgarian translation

Don't forget to add Bulgarian to the list of available languages in src/providers/settings-data/settings-data.ts 😄

@zillionn please see @ItsANameToo's comment. You will need to do this in order for the translation to work.

Done.

Bad news @zillionn, I just merged meaning there's now a conflict 😬

You happy now... Guthub?

I'm happy, thanks @zillionn! :+1:


Update .hlxignore

Update the ignore list for EDS

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.17%. Comparing base (31dee22) to head (602d753).

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #619      +/-   ##
==========================================
- Coverage   98.19%   98.17%   -0.03%
==========================================
  Files          34       34
  Lines        4099     4099
==========================================
- Hits         4025     4024       -1
- Misses         74       75       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Search term is incorrect?

Using OPDSBrowser on Android, I am entering a Search for 'Harold', the author of one of my pdf files. This finds no result. The reason is that the search term 'harold' doesn't get passed. In fact the Request looks badly formatted. (I would try with Aldiko but there the Search button doesn't appear :-( ) I am guessing that {searchTerm} should be part of the initial page sent to the client?
The command screen for DotOPDS shows:
6362165145178012834 - Response: GET http://<IP_ADDRESS>:8080/opds
Content-Type: application/atom+xml; charset=utf-8
<feed xmlns:os="http://a9.com/-/spec/opensearch/1.1/" xmlns:opds="http://opds-spec.org/2010/catalog" xmlns:dc="http://purl.org/dc/terms/" xmlns:dotopds="urn:dotopds:v1.0" xmlns="http://www.w3.org/2005/Atom">
  <updated>2017-02-02T21:57:31</updated>
  <id>tag:root:root</id>
  <title>DotOPDS Library</title>
  <link rel="search" type="application/atom+xml" href="/opds/search?q={searchTerms}" />
  <link rel="start" type="application/atom+xml;profile=opds-catalog;kind=navigation" href="/opds" />
  <link rel="self" type="application/atom+xml;profile=opds-catalog;kind=navigation" href="/opds" />
  <entry>
    <updated>2017-02-02T21:57:31</updated>
    <id>tag:root:genres</id>
    <title>Books by genres</title>
    <dc:issued>0</dc:issued>
    <content type="text">Browse books by genres</content>
    <link type="application/atom+xml;profile=opds-catalog;kind=acquisition" href="/opds/genres" />
  </entry>
</feed>
6362165150697394674 - Request: GET http://<IP_ADDRESS>:8080/opds/search?q={searchTerms}&q=harold
User-Agent: Dalvik/1.6.0 (Linux; U; Android 4.4.2; SM-T310 Build/KOT49H)
Host: <IP_ADDRESS>:8080
Connection: Keep-Alive
Accept-Encoding: gzip

Breakpointing in SearchController.cs in Feed Search I see q is {searchTerms}, not harold. The query of course finds nothing.

The readers are all @#$!@#$, the only one I found that works properly is Moon+Reader. I prefer Aldiko, will push them for fixes.


add dropdown demo in showcase

@Jinjiang   .   this demo is aim to show the dropdown on first push;  now I have added the filtering feature.

Awesome! +1 @luics

nice job!


feat: Markdown / custom processing support

Hi, great plugin!
It'd be nice if this plugin could wrap TS types in a markdown symbols, like:
Type

```ts
  {
    field: number
  }
```

Is not assignable to `number`

So other plugins like noice.nvim could highlight the diagnostic popup using treesitter for example
I think there're two ways to implement it:

Direct option like format = 'markdown', while the current behaviour is format = 'plain' or something
Two generic functions for formatting blocks and inlines, line:

format = {
  inline = function (text) return '`' .. text .. '`',
  block = function (text)
    return '```ts\n' .. text .. '\n```'
  return
}

Second approach is more difficult, because we'd need to choose what data to pass in function parameters (is text already prettified? How to handle nested indentation?)

updated with:
{
    "davidosomething/format-ts-errors.nvim",
    config = function()
      require("format-ts-errors").setup({
        add_markdown = true, -- wrap output with markdown ```ts ``` markers
        start_indent_level = 0, -- initial indent
      })
    end,
}

lmk if that works

It seems like the TS blocks are not indented now

Not entirely sure what's happening, i'll share a better screenshot when i found one

if you could share the file as well it would help

Here's the short example:
type Obj1 = { field: number }
type Obj2 = { field: string }
const x: Obj1 = {field: 123}
const y: Obj2 = x

Current output is:
Type

```ts
Obj1
```

is not assignable to type

```ts
Obj2
```

  Types of property 'field' are incompatible.
Type

```ts
number
```

is not assignable to type

```ts
string
```

 (2322)

are you using         start_indent_level = 0, -- initial indent ?
The default before this change was 1

are you using  start_indent_level = 0, -- initial indent ? The default before this change was 1

Yes, i'm using start_indent_level = 0

remove that line or change it to start_indent_level = 1 to bring back initial indent

remove that line or change it to start_indent_level = 1 to bring back initial indent

It produces the same result for the example i posted above

i am unable to replicate, can you post a minimal config?
here's what i see with start_indent_level = 1

Sorry, it turn's out that render-markdown plugin removes the indentation in code blocks
That's my output without the plugin:
Type

```ts
  Obj1
```

is not assignable to type

```ts
  Obj2
```

  Types of property 'field' are incompatible.
Type

```ts
  number
```

is not assignable to type

```ts
  string
```

@davidosomething
Is the Types of property 'field' are incompatible indented correctly? You can close the issue if that's intended

If anyone stumbles across this, you can turn off render-markdown's indent feature to keep the highlighting
Here's how i've configured neovim to render "Diagnostics" as markdown:
local builtin_open_float = vim.diagnostic.open_float

---@diagnostic disable-next-line: duplicate-set-field
vim.diagnostic.open_float = function(...)
	local bufnr, winid = builtin_open_float(...)

	vim.api.nvim_set_option_value('filetype', 'markdown', { buf = bufnr })

	return bufnr, winid
end

And here's how to tell neovim not to apply DiagnosticError highlight to the whole popup:
vim.diagnostic.config {
	signs = {
		-- text & numhl tables
	},

	float = {
		-- NOTE: format can't return the highlight, so we use prefix & suffix without it
		format = function() return '' end,

		prefix = function(report)
			local signs = vim.diagnostic.config().signs or {}
			local icon = signs.text[report.severity]
			return icon .. ' ', signs.numhl[report.severity]
		end,

		suffix = function(report)
			local hl = 'Normal'
			local message = vim.trim(report.user_data.lsp.message)

			if string.find(message, '\n') then
				return string.format('%s\n^ (%s)', message, report.code), hl
			end

			return string.format('%s (%s)', message, report.code), hl
		end,
	},
}

Is the Types of property 'field' are incompatible indented correctly? You can close the issue if that's intended

Yea, it comes newline+indented from typescript server.
It's possible to change the output of that as well using some regex to strip the extra indent, but the messaging changes between typescript versions so I'll leave it as an exercise to the user ;P
Thanks for using and following up on the issue!


Crash

Environment: Clearoom-0.2.2-alpha, java-21;
probeZS version: Release 1.18.5-20240623010409
modlist: modlist.txt
crash-report: crash-2024-06-25_00.00.09-client.txt
latest.log: latest.log
debug.log: debug.log

oh, I saw a sentence in Crafttweaker.log:
[POSTINITIALIZATION][CLIENT][INFO] [ProbeZS]: null import member in mods.ddd.Resistances
Maybe it has something to do with this mod: Distinct Damage Descriptions mod


pip install pyq fails

When I do a 'pip install pyq' from the Pycharm 2018 Community edition terminal, it fails with the following error:
File "C:\Users\bob\AppData\Local\Temp\pip-install-8zf3idem\pyq\setup.py", line 497, in build_extensions
        self.compiler.compile_options.remove('/MD')
    ValueError: list.remove(x): x not in list

[ ] Which operating system are you using (if Linux, please provide flavour of it, i.e RedHat, CentOS or Ubuntu), is it 32-bit, or 64-bit?

Windows 10 Home 64-bit

[ ] Which version of PyQ are you running? Please provide output of  pyq --versions, if PyQ isn't operational, please provide Python interpreter version and PyQ version python -V; python3 -V; pip list | grep pyq:

PyQ fails to install
Python 3.6.5 :: Anaconda, Inc.

[ ] Which version of kdb+ are you using, is it 32-bit or 64-bit?

KDB+ 3.6
64-bit

[ ] If on 64-bit, is your QLIC set? Please provide output env | grep QLIC on linux/macOS, or set|grep QLIC on Windows.

QLIC is not defined.
According to the kdb docs - "If QLIC is not defined, kdb+ falls back to QHOME (or its fallback)."

[ ] Did you use virtual environment to install PyQ? If not, why?

Not initially although I just tried in a venv and get the same error.

[ ] Where is your QHOME? Please provide output env | grep QHOME on linux/macOS, or set|grep QHOME on Windows.

C:\q\

[ ] Do you use Conda? If so, what version?

Python 3.6.5 :: Anaconda, Inc.

Could you please confirm that you have Microsoft Build Tools for Visual Studio 2017 installed. Then please use terminal app, not pycharm to install PyQ. Please provide full output of
/path/to/your/bin/python3.6 -mpip install pyq


Currently, the ledger command only takes int for ledger_index - update the logic to allow string as well.

Assume ledger_index is quoted int if it is not "current", "closed", or "validated".
FIXES #3533

Looks pretty good, but I'd like to request a couple of changes.

The DepositAuthorized unit tests are failing as a result of your change.  You can choose to fix them yourself, or you could cherry-pick this commit which has a fix: scottschurr@3461cd4
The commit messages need some work.  Here is generally good advice to follow: https://chris.beams.io/posts/git-commit/  But there are two specific changes I'd like to see

The first line of the first commit message is too long.  It should be 60 characters or less.  If there's more stuff coming then that first line should end with a colon followed by a blank line followed by the additional stuff.

RPC ledger_index argument accepts quoted numeric strings:
Some RPC commands return ledger_index as a quoted numeric string.
This change allows the returned value to be directly copied and
used for follow-on RPC commands.
FIXES 3533

Presumably the remaining commits will want to be squashed into the first commit when this pull request is merged.  Please start the commit message of any commits you want squashed with [FOLD].  The person assembling a release may not have been following the code review.  Including [FOLD] helps the person building the release to know whether they have additional work to do. So the second commit message might look like this...

[FOLD] Update unit-test

The additional bug-fix and tuning commits should all include [FOLD] at the front. So, for example, the commit message for the third commit might look like...

[FOLD] Simplify ledger_index parsing:
Change lexicalCastChecked() argument to std::unit32_t.
Update unit-test.

I'm sure you get the idea. Thanks.

Thank you. I fixed the unit test.
I'll update the commit message and squash per your recommendations once the PR is approved.


Structs that hold pointers to arrays of structs should have lifetime parameters

For example:
typedef struct D3D12_ROOT_DESCRIPTOR_TABLE
    {
    UINT NumDescriptorRanges;
    _Field_size_full_(NumDescriptorRanges)  const D3D12_DESCRIPTOR_RANGE *pDescriptorRanges;
    } 	D3D12_ROOT_DESCRIPTOR_TABLE;

pDescriptorRanges points to the start of an array of NumDescriptorRanges D3D12_DESCRIPTOR_RANGE instances.  The generated rust type should have an appropriate lifetime parameter indicate that this array must be valid for as long as the D3D12_ROOT_DESCRIPTOR table instance is valid.
This pattern exists across many D3D12 structs, and possibly in other Win32 ones as well.

Currently, win32metadata does not include anything associating these two fields together, so it is likely some work will be required there. I think we need to agree that including these lifetime parameters is the right thing to do, figure out what metadata is required and get the appropriate issue filed.  Once that's done we'll be able to do the windows-rs work to resolve this issue.

Sweet, thanks for opening the issue. I have other issues open for supporting arrays in general, which I currently only support minimally, but this will be useful to track this specific pattern.
We'll need another issue on the win32metadata repo for adding metadata to account for the _Field_size_full_(NumDescriptorRanges) SAL annotation. The metadata already parses SAL annotations so that shouldn't be a problem - we just need to get them to add this one somehow.

Other array-related issues: #212 #443 #479 #790
I hope to address all of these together when I get a moment.

Doesn't look like there's been any progress metadata issue. https://github.com/microsoft/win32metadata/issues/547
I'll close this issue for now but keep an eye on that metadata issue. If that is resolved, we can revisit this.


Leverage SNAPS-OO library to create post-install OpenStack objects

The post-install scripts use the openstack command line for creating the images and public network. As this is a SNAPS project, we may want to consider using SNAPS-OO to create these objects.
As SNAPS-OO currently has an incomplete magnum implementation, we will have to leave those post-install operations as-is for the time being.

Also the init-runonce adds security groups and flavors which are good candidates for SNAPS-OO to handle as well.

We may also want to make those values a bit more customizable.


Fix KUBERNETES_SERVICE_ACCOUNT_TOKEN auth

What changes were proposed in this pull request?
This PR fixes the KUBERNETES_SERVICE_ACCOUNT_TOKEN auth type, as it currently will never work.
The current problem is caused by a VERY bad assumption being made by Kubeflow itself. Inside the kfp.Client() initialization code, if a host is specified it will never enable ServiceAccount auth. (Relevant code in kfp.Client())
Because we require that api_endpoint is set and pass it to the kfp.Client() constructor, we always specify a host.
Luckily the solution is relatively simple, we can explicitly tell the kfp.Client() constructor that we want to use ServiceAccount auth, by passing a kfp.auth.ServiceAccountTokenVolumeCredentials() to the credentials argument of kfp.Client().
How was this pull request tested?

Running Elyra in a Kubeflow cluster with ServiceAcount auth

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@alexisc67 sounds like the problem you've brought up on gitter!

@ptitzler this PR should be ready to merge now.


Gridsome on Mac M1, upgrade sharp please

I'm trying to install node packages within existing Gridsome projects on my Mac M1 (they work on other machines).
It says
Failed at the<EMAIL_ADDRESS>install script

If I write in package.json:
"overrides": {
    "gridsome": {
      "sharp": "^0.30.7"
    }
 }

I get this error when Gridsome develop run
Gridsome v0.7.23

Initializing plugins...
Error:

Vue packages version mismatch:

-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>

I tried every solution suggested from previous issues, nothing helped

Hi, here is my DockerFile content that work with Docker on my Mac M1 using : docker-compose run --rm gridsome yarn install

`FROM node:16-bullseye-slim AS development
ARG DOCKER_UID=-1
ARG DOCKER_GID=-1
RUN set -eu;
if [ "$DOCKER_UID" -gt -1 ]; then
usermod -u "$DOCKER_UID" node;
groupmod -g "$DOCKER_GID" node;
mkdir -p /home/node/.npm;
chown -R node:node /home/node;
fi;
COPY --chown=node:node  . .
ENV PATH=$PATH:./node_modules/.bin
WORKDIR /app
USER node
RUN yarn global add @gridsome/cli<EMAIL_ADDRESS>RUN echo "export PATH=${PATH}:yarn global bin" >> /home/node/.bashrc
`

Following, the sharp version should be updated.

"overrides": {
    "gridsome": {
      "sharp": "^0.30.7"
    }
 }

Worked for me though

Thanks for your feedback!

Following, the sharp version should be updated.

"overrides": {
    "gridsome": {
      "sharp": "^0.30.7"
    }
 }

Worked for me though

I tried one more time, thought this should work for me also. And it worked after removing vips and reinstalling node:
brew remove vips
nvm uninstall 17
nvm install 17
nvm use 17
rm -rf node_modules
npm i

But still looking forward to the update with sharp version and Vue 3 also ))

@positivecrash glad it's fixed for you. However, I guess it'd be better to leave this ticket open until the sharp version is not updated. Basically, it's a low-hanging fruit to fix that, and before that's done Apple Silicon users will have hard times installing Gridsome.


sklearn is still a dependency in setup.py

Commit b508b1a intended to remove sklearn dependency, but actually removed scipy. You can check the commit's diff here.
scipy is still installed since it's a dependency of scikit-learn, but we also get the deprecated sklearn package.
This means that the problem from #29 still affects finch-clust==0.1.8. We can check it by doing the following (based on How to test whether a package will be affected by the sklearn deprecation):
SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=False \
    pip install finch-clust==0.1.8

Thanks a lot for letting me know, it is fixed now!


3 way overlaps drawn when there 3x2 way interactions

The data contains three sets that all interact with each other pairwise, but there is no three way interaction. This is inferred and results in a joint overlapping area that should not be there.
These exist:
{Drama,Romance}
{Comedy,Romance}
{Comedy,Drama}
This does not exist:
{Drama,Romance,Comedy}
What it looks like:

Where the issue is:

you are right. the problem is, this can not be solved with circles. this is: if you want to sick to relative correct size.

So - the results here are an approximation process. Like I said in the 3rd and 4th paragraph of my blog post introducing this project:

The problem is that even for only 3 sets, its not always possible to position everything so that everything is area proportional to the set sizes. Try changing A=B=C=8 , AB=AC=4 and BC=0 in the above example to see what I mean about impossible layouts. There is no way to exactly satisfy all those constraints. Even worse is trying to layout Euler diagrams with 4+ sets: if there are no disjoint sets, its actually impossible to use circles to represent these set relations exactly.
I still want the best possible approximation even if its not possible to be perfect all the time. So I did the sensible thing here: define a function that measures how well a layout matches the desired overlaps - and then minimize that function numerically.

In your case, It doesn't look like there is a better layout for that data.


Introduce a multi-stage Docker file

I want to see if this works with the buildah task in RHTAP.
Ref: EC-302.

This does produce a working RHTAP build. Still lots to do, but I'm thinking let's merge early and often.

I'll probably merge soon.


Add references section and tweaks badges order

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


contourf! ignores colors specified for extendhigh and extend low?

The following example in the documentation (https://makie.juliaplots.org/v0.15.2/examples/plotting_functions/contourf/) seems not to produce the desired output currently (this should cut off low and high peaks in the data and fill in with :cyan or :magenta)
using CairoMakie
xs = LinRange(0, 10, 100)
ys = LinRange(0, 10, 100)
zs = [cos(x) * sin(y) for x in xs, y in ys]

f = Figure()
Axis(f[1, 1])

co = contourf!(xs, ys, zs, levels = -0.75:0.25:0.5,
    extendlow = :cyan, extendhigh = :magenta)

Colorbar(f[1, 2], co)

f

while it does keep the color constant for values below -0.75 (dark blue) and above 0.5 (bright yellow), it does not display the specified :cyan and :magenta colors, respectively.
If this is not a bug, I am surprised how this option is different from setting extendhigh = :auto, which is the example provided below this one in the documentation. In fact, the output plots provided for the two examples in the documentation look identical to me (and they are identical when I run the examples in the REPL).

Oh that is a bug, must have regressed at some point and I guess the high low thing wasn't covered by visual tests.

Closing the issue, because this issue is resolved when I check on the newest versions.


Add "ATTRIBUTES" functionality

See https://senzing.atlassian.net/browse/GDEV-3917
Member of https://github.com/senzing-garage/garage-roadmap/issues/5

SZ_ENTITY_INCLUDE_RECORD_FEATURE_IDS → SZ_ENTITY_INCLUDE_RECORD_FEATURES

Flag was renamed.  Same old flag value (same bit).  Still only applies to “entity” retrieval calls (e.g.: getEntity() searchByAttributes(), exportJSON(), findPath(), findNetwork() and why()) even though it modifies the record section.  This creates references from the record section back to the entity features so you can tell which records contributed to which features.
NOTE: JSON format is likely still the same but it may change to be broken down by feature like the new flags (according to @Brian Macy )

SZ_ENTITY_INCLUDE_RECORD_FEATURE_DETAILS and SZ_ENTITY_INCLUDE_RECORD_FEATURE_STATS

These are new flags.  They apply to all “entity” retrieval calls as above, but ALSO apply to getRecord() calls.  These provide the FEATURES JSON segment at the RECORD level in the JSON that in the past has only existed at the ENTITY level of the JSON .  The feature details is illustrated in the Jira description, but the FEATURE_STATS will appear as it does for the SZ_ENTITY_INCLUDE_FEATURE_STATS – in each case we see the features in detail contributed by a record at the record level.
IMPORTANT NOTE 1: These flags modify the search criteria part of the JSON response on searchByAttribute() as well in that you will see feature details and/or statistics on the hypothetical search record that acts as the search criteria.
IMPORTANT NOTE 2: These flags interact with the SZ_ENTITY_INCLUDE_INTERNAL_FEATURES flag which was previously NOT APPLICABLE to getRecord() calls.  However, since these flags interact with SZ_ENTITY_INCLUDE_INTERNAL_FEATURES that flag is NOW APPLICABLE to getRecord() calls, changing the behavior of that flag.


MSVC and pointer arithmetic

Hey Peter. Thank you for this implementation! So far I encountered only one problem, not a big deal actually, but MSVC is not happy with pointer arithmetic and throws some errors during compilation:

vector.c(375): error C2036: void *
vector.c(380): error C2036: void *
vector.c(415): error C2036: void *
vector.c(435): error C2036: void *
vector.c(439): error C2036: void *const
vector.c(473): error C2036: void *
vector.c(488): error C2036: void *

I fixed this with an explicit cast and just want to let you know that such a problem occurs.

Thanks for reporting this! Do you think you could send a pull request with your fixes? I'd be happy to merge it.

2020 Sep 03 -- this is still a problem


Add options to Cassandra to control indexing

Add StoreIndexesOnly and StoreWithoutIndexing options to the cassandra
storage which controls whether indexes are written along with spans.

This allows us to deploy, scale, and prioritize  writers independently for
indexing and storage workloads.

Signed-off-by: Prithvi Raj<EMAIL_ADDRESS>

Coverage remained the same at 100.0% when pulling 7509d919e5e9da248faa423be77b10b7af430dee on add-cassandra-writer-options into 851b0dd202f1c0ab56271dc71ba5e03c73c0c88e on master.


Not working in Android Chrome

works in  android firefox
again Great addon for a-frame!

Just looking at this. I've been testing on my own Google Pixel and haven't encountered any issues. Can you describe what's happening or send me an example?

I experience the same issues in my app as well as your basic demo @mwbeene.
Android 9
Chrome 90.0.4430.210
Description:
Clicks on ground floor seem not to be registered and thus do not move the camera.
Clicks on objects work fine.
I can also confirm Firefox works perfectly on the same platform.

I just tested https://c-frame.github.io/aframe-cursor-teleport/examples/basic/index.html on Chrome Android, I have no issue.


Added grunt directory with js modules

For maintaining grunt tasks, I've moved all tasks to a grunt directory with .js modules. They're loaded in with the load-grunt-configs package.

Nice change, thanks @cameronjroe


Statistical assumptions?

Hi - I just have a very basic question on the statistical assumptions of the songbird approach. For example, do each covariate have to follow a normal distribution? Do the covariates have to be independent from each other? etc.  Thank you!

Not sure 100%, but this post might be helpful.

It looks like this question has been answered, feel free to reopen if this is not the case.


Move Create a poll documentation page into Sending messages section

Currently documentation for creating a poll is in the Tools & customization section.
We should move it to the Sending messages section, since it's one of the things you can do when sending a message. It can be directly beneath the Add GIFs in your message link (currently the last one in the section).

@zulipbot claim


chore: Attempt to enable Python 3.7

This is because Google Colab is still on Python 3.7, so it would enable this repo for Colab.

Python 3.7 support unfortunately is missing support for a range of type annotations that we use. It's probably not worth trying to backport them to support 3.7 at this stage.


Mgi quickfix

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
ANCHOR-284 Quickfix of requestedAccount not properly set
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]

Something went wrong with PR preview build please check


feat(core): validate inputs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (fb3d388) 97.12% compared to head (83f8802) 93.06%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
- Coverage   97.12%   93.06%   -4.06%
==========================================
  Files           6        7       +1
  Lines         174      202      +28
==========================================
+ Hits          169      188      +19
- Misses          5       14       +9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Bug] Inconsistent callout handling

I was testing how this works with my workflow and noticed inconsistent behaviors with callouts.
Here the code without trying to serialize it:
> [!Experiments]+
> - # In-Progress
>
> ```dataview
> LIST FROM "01 Research/Lab Notebook" AND #experiment WHERE contains(status, "in-progress")
> ```

Now with serialization that does not get recognized:
> [!Experiments]+
> - # In-Progress
>
><!-- QueryToSerialize: LIST FROM "01 Research/Lab Notebook" AND #experiment WHERE contains(status, "in-progress") -->

Then I tried it outside of the callout, and suddenly the part inside the callout gets recognized:
<!-- QueryToSerialize: LIST FROM "01 Research/Lab Notebook" AND #experiment WHERE contains(status, "in-progress") -->
<!-- SerializedQuery: LIST FROM "01 Research/Lab Notebook" AND #experiment WHERE contains(status, "in-progress") -->
- [[01 Research/Lab Notebook/2023-09-08 Camera calibration.md|2023-09-08 Camera calibration]]
- [[01 Research/Lab Notebook/2023-09-15 Reactions to conspecific and heterospecific bedding in Peromyscus.md|2023-09-15 Reactions to conspecific and heterospecific bedding in Peromyscus]]
<!-- SerializedQuery END -->

> [!Experiments]+
> - # In-Progress
>
><!-- QueryToSerialize: LIST FROM "01 Research/Lab Notebook" AND #experiment WHERE contains(status, "in-progress") -->
<!-- SerializedQuery: LIST FROM "01 Research/Lab Notebook" AND #experiment WHERE contains(status, "in-progress") -->
- [[01 Research/Lab Notebook/2023-09-08 Camera calibration.md|2023-09-08 Camera calibration]]
- [[01 Research/Lab Notebook/2023-09-15 Reactions to conspecific and heterospecific bedding in Peromyscus.md|2023-09-15 Reactions to conspecific and heterospecific bedding in Peromyscus]]
<!-- SerializedQuery END -->

It messes up the callout, but somehow it suddenly kinda works.

The replacement logic is a bit finicky, and I'm not a master of Regular expressions, unfortunately.
I will keep this ticket open because improvements would be very valuable to make this plugin more versatile


Update MVDR beamforming tutorial

Use download_asset to download audios.
Replace MVDR module with new-added SoudenMVDR and RTFMVDR modules.
Benchmark performances of F.rtf_evd and F.rtf_power for RTF computation.
Visualize the spectrograms and masks.

tutorial: https://output.circle-artifacts.com/output/job/de0ccc46-2998-42fe-a2fa-7ac1c24f4205/artifacts/0/docs/tutorials/mvdr_tutorial.html


Reduce I2of5 false positives

I2of5 was giving me a TON of false positives on higher resolution cameras with the WebRTC scanning.
Reducing the AVG_CODE_ERROR down to .25 (from .38) greatly reduced these without impacting any other lower resolution camera devices I tested on.

Thank-you for your Patch!
We have forked the project and are accepting Pull Requests here:
https://github.com/NeraiCorp/getUserBarcode


Plaster build script tasks for signing files

Hello,
I've been using some of the ideas from the Build.ps1 script in my psake build script and I added a few tasks to enable script signing that I use on some other projects.
I can create a PR to add/merge some of the work that I've done on the build script i use. It could probably use a bit of work but I wanted to know whether this was something that you thought plaster could provide functionality for.
Thanks,
Dave Green

The current build.ps1 psake script is by no means done.  I'd like to add a docs build task that perhaps uses platyPS.
So yeah, have a task to do script signing (perhaps based on existence of a CertificatePath/Name property) task would be nice to have.  Go ahead and submit a PR and we can work from there on how best to integrate it in.

Thank you for the feedback and help with this! It's been fun to contribute 😄


Navigation is broken on mobile with Doxygen 1.9.2

Doxygen 1.9.2 creates a "hamburger menu" on mobile that conflicts with the doxygen-awesome CSS. Here's how it looks with Doxygen 1.9.2 in collapsed state:

Here's how it looks in expanded state:

I think this commit in Doxygen is responsible: https://github.com/doxygen/doxygen/commit/74b8e42b85cda8927e14511fba8b83f85b6ff2c9

Experiencing the same issue on 1.9.2: https://teslabs.github.io/zephyr-doxygen-test/

Yesterday I discovered the problem with the button disappearing on resize as well... :( It seems like claiming that 1.6.0 is ready for doxygen 1.9.2 was a bit of an overstatement. I am experimenting on how to fix this, but it's difficult to find the correct spot in the DOM to mount the button... Ideas welcome and stay tuned!


GH-36345: [C++] Prefer TypeError over Invalid in IsIn and IndexIn kernels

Rationale for this change

Prefer TypeError over Invalid in IsIn and IndexIn kernels
What changes are included in this PR?
When casting fails, return TypeError instead of Invalid.

Are these changes tested?
Yes.

Are there any user-facing changes?
No.

Closes: #36345

cc @pitrou


[1.12.2] [B11] All Vis Crystals in the Thaumonomicon Look The Same

I'm guessing the items in the tasks don't respect NBT.

#511 for reference

I can confirm that this happens for me as well. The arcane bellows and essentia smelting both have this issue where I can't see which specific crystals are required. So far these are the only two. Unless one were to happen to know which ones were required, you can't progress past this point.


Make error

./kernel/get-deps
make: ./kernel/get-deps: No such file or directory
make: *** [GNUmakefile:67: kernel-deps] Error 127

Have you deleted that file? If not, it should work.
But more generally, a lot of context is lacking to know what is going on.

No, I placed the files from the repository in a separate folder and tried to run the build.

Then it should work, unless you misplaced relative to the rest of the repo, renamed, or removed kernel/get-deps.


Introduce a skip list

Some operators may not play nice if installed automatically. If any future operators exhibit bad behavior, they should be added to the list in vars/skip_list.yml.
Fixes #118

/lgtm


Drools 6 Simple example

I add submodule drools in examples with simple use case. Also I add feature "examples-drools-simple" with integrity test

test comment to test email notifications

Another test comment

@sobkowiak I fix README.txt. Please check my English


36 | Changes for publishing to test.pypi.org

Thanks Jon, duly added (I had to install them for your new tests to run too, coin didn't drop to add them to setup.cfg).


Issues with Eigen when building tf_tutorials_example_trainer on Windows 10

I'm attempting to build Tensorflow C++ on Windows 10 following the instructions of the cmake readme. However, I'm getting issues with compiling at the Eigen step.
Compiler:
Build flags:
Id flags:

The output was:
1

Microsoft Visual Studio 2015 Version 14.0.25420.1.
Copyright (C) Microsoft Corp. All rights reserved.

The license for Visual Studio has expired.

The evaluation period for this product has ended.

Performing C++ SOURCE FILE Test COMPILER_SUPPORT_FASTMATH failed with the following output:
Change Dir: C:/Users/Irene/Documents/tensorflow/tensorflow/contrib/cmake/build/eigen/src/eigen-build/CMakeFiles/CMakeTmp

Run Build Command:"C:/Program Files (x86)/MSBuild/14.0/bin/MSBuild.exe" "cmTC_70ffc.vcxproj" "/p:Configuration=Debug" "/p:VisualStudioVersion=14.0"
Microsoft (R) Build Engine version 14.0.25420.1

Copyright (C) Microsoft Corporation. All rights reserved.

Build started 9/02/2017 3:13:30 PM.

Project "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_70ffc.vcxproj" on node 1 (default targets).

PrepareForBuild:

  Creating directory "cmTC_70ffc.dir\Debug\".

  Creating directory "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\Debug\".

  Creating directory "cmTC_70ffc.dir\Debug\cmTC_70ffc.tlog\".

InitializeBuildStatus:

  Creating "cmTC_70ffc.dir\Debug\cmTC_70ffc.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.

ClCompile:

  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\CL.exe /c /Zi /W4 /WX- /Od /Ob0 /D WIN32 /D _WINDOWS /D _CRT_SECURE_NO_WARNINGS /D _SCL_SECURE_NO_WARNINGS /D COMPILER_SUPPORT_FASTMATH /D _DEBUG /D "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /GR /Fo"cmTC_70ffc.dir\Debug\\" /Fd"cmTC_70ffc.dir\Debug\vc140.pdb" /Gd /TP /wd4127 /wd4505 /wd4714 /errorReport:queue  -ffast-math "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\src.cxx"

  Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24215.1 for x64

  Copyright (C) Microsoft Corporation.  All rights reserved.

  cl /c /Zi /W4 /WX- /Od /Ob0 /D WIN32 /D _WINDOWS /D _CRT_SECURE_NO_WARNINGS /D _SCL_SECURE_NO_WARNINGS /D COMPILER_SUPPORT_FASTMATH /D _DEBUG /D "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /GR /Fo"cmTC_70ffc.dir\Debug\\" /Fd"cmTC_70ffc.dir\Debug\vc140.pdb" /Gd /TP /wd4127 /wd4505 /wd4714 /errorReport:queue  -ffast-math "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\src.cxx"

cl : Command line warning D9002: ignoring unknown option '-ffast-math' [C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_70ffc.vcxproj]

  src.cxx

Link:

  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\link.exe /ERRORREPORT:QUEUE /OUT:"C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\Debug\cmTC_70ffc.exe" /INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /manifest:embed /DEBUG /PDB:"C:/Users/8i/Documents/tensorflow/tensorflow/contrib/cmake/build/eigen/src/eigen-build/CMakeFiles/CMakeTmp/Debug/cmTC_70ffc.pdb" /SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:"C:/Users/8i/Documents/tensorflow/tensorflow/contrib/cmake/build/eigen/src/eigen-build/CMakeFiles/CMakeTmp/Debug/cmTC_70ffc.lib" /MACHINE:X64  /machine:x64 cmTC_70ffc.dir\Debug\src.obj

  cmTC_70ffc.vcxproj -> C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\Debug\cmTC_70ffc.exe

FinalizeBuildStatus:

  Deleting file "cmTC_70ffc.dir\Debug\cmTC_70ffc.tlog\unsuccessfulbuild".

  Touching "cmTC_70ffc.dir\Debug\cmTC_70ffc.tlog\cmTC_70ffc.lastbuildstate".

Done Building Project "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_70ffc.vcxproj" (default targets).

Build succeeded.

"C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_70ffc.vcxproj" (default target) (1) ->

(ClCompile target) ->

  cl : Command line warning D9002: ignoring unknown option '-ffast-math' [C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_70ffc.vcxproj]

    1 Warning(s)

    0 Error(s)

Time Elapsed 00:00:00.54

Source file was:
int main() { return 0; }
Determining if the include file pthread.h exists failed with the following output:
Change Dir: C:/Users/Irene/Documents/tensorflow/tensorflow/contrib/cmake/build/eigen/src/eigen-build/CMakeFiles/CMakeTmp

Run Build Command:"C:/Program Files (x86)/MSBuild/14.0/bin/MSBuild.exe" "cmTC_55681.vcxproj" "/p:Configuration=Debug" "/p:VisualStudioVersion=14.0"
Microsoft (R) Build Engine version 14.0.25420.1

Copyright (C) Microsoft Corporation. All rights reserved.

Build started 9/02/2017 3:13:37 PM.

Project "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_55681.vcxproj" on node 1 (default targets).

PrepareForBuild:

  Creating directory "cmTC_55681.dir\Debug\".

  Creating directory "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\Debug\".

  Creating directory "cmTC_55681.dir\Debug\cmTC_55681.tlog\".

InitializeBuildStatus:

  Creating "cmTC_55681.dir\Debug\cmTC_55681.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.

ClCompile:

  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\CL.exe /c /Zi /W3 /WX- /Od /Ob0 /D WIN32 /D _WINDOWS /D _DEBUG /D "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo"cmTC_55681.dir\Debug\\" /Fd"cmTC_55681.dir\Debug\vc140.pdb" /Gd /TC /errorReport:queue "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\CheckIncludeFile.c"

  Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24215.1 for x64

  Copyright (C) Microsoft Corporation.  All rights reserved.

  cl /c /Zi /W3 /WX- /Od /Ob0 /D WIN32 /D _WINDOWS /D _DEBUG /D "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo"cmTC_55681.dir\Debug\\" /Fd"cmTC_55681.dir\Debug\vc140.pdb" /Gd /TC /errorReport:queue "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\CheckIncludeFile.c"

  CheckIncludeFile.c

C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\CheckIncludeFile.c(1): fatal error C1083: Cannot open include file: 'pthread.h': No such file or directory [C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_55681.vcxproj]

Done Building Project "C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_55681.vcxproj" (default targets) -- FAILED.

Build FAILED.

"C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_55681.vcxproj" (default target) (1) ->

(ClCompile target) ->

  C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\CheckIncludeFile.c(1): fatal error C1083: Cannot open include file: 'pthread.h': No such file or directory [C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_55681.vcxproj]

    0 Warning(s)

    1 Error(s)

Time Elapsed 00:00:00.24

The line with the error is:
C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\CheckIncludeFile.c(1): fatal error C1083: Cannot open include file: 'pthread.h': No such file or directory [C:\Users\Irene\Documents\tensorflow\tensorflow\contrib\cmake\build\eigen\src\eigen-build\CMakeFiles\CMakeTmp\cmTC_55681.vcxproj]
So I guess the question is why is eigen trying to include pthread.h on Windows?
I was able to reproduce this on my box, when previously (Dec 2016, commit 2531ebc0fe7fc96) it worked fine. However even that previously good commit no longer functions now. This suggests Eigen upstream has changed something to break the tensorflow cmake build.

@mrry pthread.h on Windows does seem anomalous.

@Katuali and @ferrouswheel: What command are you using to start the build? Since Eigen is header-only, we shouldn't need to build anything for it, and our CI is currently green, so I suspect something is different in your configuration.
Also, @Katuali, I notice that MSBuild seems to be building in Debug configuration. For various reasons, we haven't been able to build on Windows in Debug, but you can instead try Release or RelWithDebInfo (if you need symbols).

I tried MSBuild /p:Configuration=Release tf_tutorials_example_trainer.vcxproj and MSBuild /p:Configuration=Release tf_python_build_pip_package.vcxproj. So definitely using Release configuration
Both result in the same issue. I've tried building master branch, tag v1.0.0, and an older commit. Which suggests this may be our environment somehow.
I've found the build log from the CI, so I'm going to try to track down where things diverge and report back here!

That's weird! I can confirm that it builds correctly for me, in a fresh checkout. It's possible that the CMake build leaves some droppings behind (sadly, it's not hermetic like the Bazel build) and this could be causing the build to fail. Looking forward to hear what you find out....

I've tracked this down to a Windows Boost distribution with a bad CMakeLists.txt. It would set BOOST_ROOT in the windows environment, and eigen would try and configure against it and then fail.
Sorry for the noise! Please feel free to close this.

@ferrouswheel That you for tracking it down!

@ferrouswheel Thanks for looking into this! I took a look at the Eigen CMakeLists, and it looks like we're doing more than we need to in the Eigen build—when in fact all we really need to do is copy some headers to the right location. The build testing is enabled by default, and attempts to pick up Boost. I'm not sure why it breaks, but we can at least avoid the problem in future by avoiding that part of the build.

@mrry Nice - I'm glad our Boost hiccup will help speed up the tensorflow build :-)


Request timeout

My gd-ocamlfuse is not sync with gdrive. Nautilus doesnt respond.
The output of -debug mode is:
[0.004943] TID=0: Setting up default filesystem...
[0.005005] TID=0: BEGIN: Saving configuration in /home/evandson/.gdfuse/default/config
[0.005413] TID=0: END: Saving configuration in /home/evandson/.gdfuse/default/config
[0.005594] TID=0: Loading application state from /home/evandson/.gdfuse/default/state...done
Current version: 0.7.21
Docs mode not changed!
Setting up cache db...done
Setting up CURL...done
Refresh token already present.
[0.012817] TID=0: Starting filesystem /home/evandson/gdrive
[0.020872] TID=1: init_filesystem
[0.021018] TID=1: Starting flush DB thread (TID=2, interval=30s)
[0.021519] TID=1: Starting async upload thread (TID=3)
[0.022197] TID=5: getattr /.Trash
[0.022257] TID=5: BEGIN: Loading metadata from db
[0.022282] TID=5: END: Getting metadata: Not found
[0.022301] TID=5: BEGIN: Refreshing metadata
[0.026683] TID=6: opendir / O_RDONLY,O_NONBLOCK
[5.079133] TID=5: Error during request: Code: 28, Description: CURLE_OPERATION_TIMEOUTED, ErrorBuffer: Resolving timed out after 800 milliseconds

[5.079165] TID=5: Retrying (1/8)
[11.807006] TID=5: Error during request: Code: 28, Description: CURLE_OPERATION_TIMEOUTED, ErrorBuffer: Resolving timed out after 801 milliseconds

[11.807040] TID=5: Retrying (2/8)
[19.303970] TID=5: Error during request: Code: 28, Description: CURLE_OPERATION_TIMEOUTED, ErrorBuffer: Resolving timed out after 800 milliseconds

[19.304002] TID=5: Retrying (3/8)
[24.435160] TID=5: BEGIN: Refreshing access token
[29.722456] TID=5: Retrying (1/8) refresh_token after exception: Failure("Code: 28, Description: CURLE_OPERATION_TIMEOUTED, ErrorBuffer: Resolving timed out after 800 milliseconds\n")
[36.360099] TID=5: Retrying (2/8) refresh_token after exception: Failure("Code: 28, Description: CURLE_OPERATION_TIMEOUTED, ErrorBuffer: Resolving timed out after 800 milliseconds\n")

Other info:
Debian 10 | DNS <IP_ADDRESS>
Tried reinstall all (include rm -rf ~/.gdfuse), but not success.

Found similar topic:
https://github.com/astrada/google-drive-ocamlfuse/issues/196
Sorry for that.
Problem solved by sudo apt-get upgrade; increase request time and google dns!


Parameterized Flow (Row/Column)

I've been looking in layout options for an upcoming product, and what you have so far is pretty slick.  I agree with issue #3 ... the ability to set/persist width & height on each split is key.
Beyond that, I'd like a hook to parameterize the flow option... meaning a way to toggle the split from a Row to Column, and visa-versa.  The link below takes you to an example showing how this could work.
http://plnkr.co/edit/igJXFGghO3eKHPQ23Jq2?p=preview
If you inspect the DOM, you'll see that the DOM elements are changing... but only the splitbar is updating.

is the parameterized flow option enabled? since this was closed?
unable to find a way to toggle between flow : column & row programatically.

Hello. Is there any update on toggle between row/column ??

+1 Bump.
This doesn't appear to work anymore. I'm sure a lot has changed since 0.0.0.


Prep release

Codecov Report

Merging #140 (be903b2) into main (b24191c) will decrease coverage by 0.06%.
The diff coverage is 22.22%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #140      +/-   ##
==========================================
- Coverage   48.37%   48.32%   -0.06%
==========================================
  Files         131      131
  Lines        4690     4699       +9
==========================================
+ Hits         2269     2271       +2
- Misses       2421     2428       +7

Impacted Files
Coverage Δ

src/fullctl/django/models/abstract/meta.py
42.06% <0.00%> (-0.68%)
:arrow_down:

src/fullctl/django/tasks/qualifiers.py
69.76% <ø> (ø)

src/fullctl/django/urls.py
80.00% <ø> (ø)

src/fullctl/django/views/__init__.py
42.59% <40.00%> (-0.27%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


tests: fixing the tests

Sorry, misclick, I was trying to make a PR to another place. It is still in development, sorry about the trouble.


0.16.0 release

Any plans for a 0.16.* release soon? Would be greatly appreciated.

@wilsonzlin Any updates?

We should maybe ask @wilsonzlin to transfer ownership of the repo


Ability to "abort" starting/attaching based on details of the buffer

Language server
N/A
Requested feature
In certain situations, I want to prevent a language server from starting or attaching to a buffer. I don't want to set autostart = false because I still do want autostart in most cases.
However, there are some specific situations (e.g. specific root dir, specific buffer name, or even specific file contents) when I do not want a language server attached to the buffer.
The request: I want to be able to "abort" the current LSP startup/attach process from inside one of the setup hook functions. Maybe I can do this by returning some specific sentinel value, or calling some specific function, in one of the setup hook functions.
Practical example: I want to autostart the YAML language server, except when the file appears to contain Jinja template syntax.
One workaround would be to set autostart = false and then write my own autocommand to call LspStart or LspAttach, with my own if/else checks. But then I lose the benefit of the Lspconfig magic root detection to choose between starting a new client and attaching an existing one.
Other clients which have this feature
Unknown

More features are out of scope for lspconfig, which is intended to be only a set of quickstart configs.
This might be worth raising at https://github.com/neovim/neovim


[enhancement] replace sub to checked_sub

Codecov Report
Base: 84.80% // Head: 84.90% // Increases project coverage by +0.09% :tada:

Coverage data is based on head (82a4fd2) compared to base (73f1aeb).
Patch coverage: 98.30% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #176      +/-   ##
==========================================
+ Coverage   84.80%   84.90%   +0.09%
==========================================
  Files          54       54
  Lines        5238     5272      +34
==========================================
+ Hits         4442     4476      +34
  Misses        796      796

Impacted Files
Coverage Δ

src/dft_basic/src/auto_scaling_storage/tests.rs
94.79% <0.00%> (ø)

src/dft_basic/src/service/basic_service.rs
93.86% <100.00%> (+0.09%)
:arrow_up:

src/dft_tx_storage/src/service.rs
94.11% <100.00%> (+0.11%)
:arrow_up:

src/dft_types/src/blockchain.rs
96.85% <100.00%> (+0.01%)
:arrow_up:

src/dft_types/src/token_allowances.rs
94.76% <100.00%> (ø)

src/dft_types/src/token_archive.rs
99.31% <100.00%> (+<0.01%)
:arrow_up:

src/dft_types/src/token_balances.rs
100.00% <100.00%> (ø)

src/dft_types/src/token_transaction_window.rs
96.72% <100.00%> (+0.19%)
:arrow_up:

src/dft_utils/src/range_utils.rs
100.00% <100.00%> (ø)

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.


Error in ResponsivePaddingCollection.xs

I believe there's a copy/paste error here in ResponsivePaddingCollection - should be ScaledSize xs(double width) => const ScaledPadding.xs() ?

@timbell Great catch!
Do you want to open a PR or should i fix it?

Happy to do a PR...


NIFI-10244 Add nifi-web-client-api and implementation

Summary
NIFI-10244 Adds a nifi-web-client-api module providing reusable interfaces to abstract HTTP communication.
The nifi-web-client-api module provides a WebClientService interface with a fluent design pattern similar to the Spring Framework WebClient. The WebClientService and associated components support composition and execution of HTTP requests using standard or custom HTTP methods. The WebClientService supports synchronous request execution.
The nifi-web-client-api module also provides an HttpUriBuilder interface to abstract composition of a java.net.URI based on component elements.
The nifi-web-client module provides a standard implementation of these interfaces using OkHttp. The StandardWebClientService class supports configuration of common settings, such as timeouts, TLS, and proxy access.
The nifi-web-client-api and nifi-web-client modules under nifi-commons provide the foundation for a new Controller Service interface named WebClientServiceProvider defined in nifi-web-client-provider-api. The StandardWebClientServiceProvider implementation in nifi-web-client-provider-service enables components to define a reusable service configuration for HTTP communication.
This approach follows the pattern of the Proxy Configuration Service, allowing Processors to abstract HTTP socket configuration. The nifi-web-client-api and nifi-web-client-provider-api also provide a layer of abstraction for components that require HTTP components. This narrows the scope of impact for dependency upgrades and allows components to implement HTTP communication without depending on a particular HTTP library.
The initial implementation is self-contained with a number of unit tests using OkHttp MockWebServer. Runtime integration can be tested with scripted components, and further improvements can be implemented in subsequent pull requests as necessary. The purpose of this pull request is to provide the foundational implementation for additional development efforts.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 8
[X] JDK 11
[X] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks for the feedback @ferencerdei! I pushed an update to address the comments.

Thanks for the feedback @ferencerdei! I pushed an update to address the comments.

Thanks for the answers and the fixes!

Thanks for the contribution @exceptionfactory. I went through the code and overall I like the clean design and the functionality. A few small comments:

I tested the UriBuilder, it's easy to use and functionally works well.
I prefer the builder pattern instead of the fixed interface order, but since http requests consist of 3 fixed parts and this will not be extended, and since it would require changing the whole design and is a matter of taste anyway, it's still perfectly usable.
I tried out the WebClientService. I created a custom processor that sends different HTTP requests to a HandleHttpRequest -> HandleHttpResponse NiFi flow. I have tested the service using TLS and a proxy server. The settings from the specified proxy service and SSLContextService are appropriately read by the processor.
LGTM+1

Thanks for the thorough testing and feedback @Lehel44!


Version 0.10.3 uses a full core on CPU

Version 0.10.3 uses up 100% cpu on my macbook pro.
Especially the Electron Helper

@q42jaap Can you please provide additional details.
Does this happen when opening a specific folder? Does this happen when opening VSCode without a folder (Cmd+Shift+N)? Anything you can add to help us reproduce

Im using the following line in .bash_profile:
code () { VSCODE_CWD="$PWD" open -n -b "com.microsoft.VSCode" --args $* ;}
I use that to code . in the directory. I leave the editor open voor a long time. And then I notice my Mac is running low on power. It's also getting hot, CPU is high on the Electron Helper subprocess.
It's difficult to say how to repro, I can't always get that to happen (fortunately).
tree | wc -l gives 25876 (406 of my own files/dirs, the rest are node_modules, I'm using npm 3)

@q42jaap what workspace do you open with code?

I'm opening a directory in which I've checked out our private git repo. Not a particularly big project.
We use nodejs 5 for backend and babel ES6 code for the frontend.
Are there steps (suchs as logs or dumps) I can take and submit (privately) to Microsoft?

@q42jaap well it would be interesting if this happen on a different folder too, maybe you could give it a try. Does the CPU go to 100% right after you open the folder?

It does not always happen, and it does not happen immediately. I'm currently in the process of reinstalling vscode, which is going to take a while due to slow connection.

I'm seeing the same on 0.10.5. Strangely, I didn't see this prior to 0.10.5 - any ideas?

Again, if there is a repository we could clone to reproduce the behaviour, please let us know.

Same her. As of 0.10.5 ElectronHelper misbehaves and eats up all of my cpu cycles. Happens on a small Ember project with a fairly big nodes_module directory. node_module and bower_components are already excluded from search. Is there a way to turn back to 0.10.3 without building it by yourself?

For those that see high CPU use, please identify the arguments for the proces (e.g. ps aux | grep ) so that we know which of the processes that Code spawns is the one in charge.

@bpasero
Started Code two minutes ago. Activity monitor reports already a memory usage of 1.25 GB... This is what ps says:
martin@mbp13 oi [master] $ ps aux | grep Electro
martin            987 115,7 13,1  4206388 1099208   ??  R    10:09am   2:16.77 /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=watcherService
martin            988   0,0  0,0  2464436   3184   ??  S    10:09am   0:00.01 /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Framework.framework/Resources/crashpad_handler --database=/tmp/VSCode Crashes --url=https://ticinocrashreporter.azurewebsites.net/crash --handshake-fd=59
martin            981   0,0  0,7  3203928  54996   ??  S    10:09am   0:00.60 /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=pluginHost
martin            980   0,0  1,7  4519136 145132   ??  S    10:09am   0:03.12 /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --enable-delegated-renderer --num-raster-threads=2 --gpu-rasterization-msaa-sample-count=8 --content-image-texture-target=3553 --video-image-texture-target=3553 --channel=974.1.633953805
martin            979   0,0  0,5  3194512  39524   ??  S    10:09am   0:00.30 /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=SharedProcess
martin            975   0,0  0,5  2711288  40136   ??  S    10:09am   0:00.25 /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper --type=gpu-process --channel=974.0.1109795083 --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=13,24,29,32,41,45,52,58 --gpu-vendor-id=0x8086 --gpu-device-id=0x0166 --gpu-driver-vendor --gpu-driver-version
martin            974   0,0  0,8  3395268  65068   ??  S    10:09am   0:01.38 /Applications/Visual Studio Code.app/Contents/MacOS/Electron
martin           1060   0,0  0,0  2432788    588 s001  R+   10:11am   0:00.00 grep Electro

@bpasero After start (with loading my Ember project automatically ), I've got six Electron Helper processes. One of them ist using approx 120% CPU to allocate memory. It stops eating CPU cycles after allocation aroun 1.28 GB RAM. I already excluded the usual suspects (node_modules, tmp, bower_components) with "files.exclude"...
Thx in advance, Martin

Here is the output formatted (according to http://superuser.com/a/117921):
USER    PID   %CPU   %MEM      VSZ      RSS TTY  STAT  START    TIME     COMMAND
martin  987  115,7   13,1  4206388  1099208 ??    R    10:09am  2:16.77  /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=watcherService
martin  988    0,0    0,0  2464436     3184 ??    S    10:09am  0:00.01  /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Framework.framework/Resources/crashpad_handler --database=/tmp/VSCode Crashes --url=https://ticinocrashreporter.azurewebsites.net/crash --handshake-fd=59
martin  981    0,0    0,7  3203928    54996 ??    S    10:09am  0:00.60  /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=pluginHost
martin  980    0,0    1,7  4519136   145132 ??    S    10:09am  0:03.12  /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --enable-delegated-renderer --num-raster-threads=2 --gpu-rasterization-msaa-sample-count=8 --content-image-texture-target=3553 --video-image-texture-target=3553 --channel=974.1.633953805
martin  979    0,0    0,5  3194512    39524 ??    S    10:09am  0:00.30  /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=SharedProcess
martin  975    0,0    0,5  2711288    40136 ??    S    10:09am  0:00.25  /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper --type=gpu-process --channel=974.0.1109795083 --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=13,24,29,32,41,45,52,58 --gpu-vendor-id=0x8086 --gpu-device-id=0x0166 --gpu-driver-vendor --gpu-driver-version
martin  974    0,0    0,8  3395268    65068 ??

Hi Benjamin, CPU goes down after allocation approx 1,25 GB of RAM. Takes around four minutes on my „101“ (MacBook Pro (13 Zoll, Mitte 2012), 2.9 GHz Core i7).
Regards,
Martin

Am 12.01.2016 um 10:56 schrieb Benjamin Pasero<EMAIL_ADDRESS>@planetexpress69 https://github.com/planetexpress69 does CPU ever go down, is it only initially?
—
Reply to this email directly or view it on GitHub https://github.com/Microsoft/vscode/issues/1009#issuecomment-170857183.

Can people seeing this issue with a JavaScript workspace please give our insiders build a try (https://code.visualstudio.com/insiders) and enable Salsa: https://github.com/Microsoft/vscode-docs/blob/master/release-notes/latest.md#javascript---salsa-preview

@bpasero: I am still experiencing the issue on the Insiders build with Salsa enabled.
OS X El Capitan Version 10.11.1 (15B42)

I'm seeing the same behaviour, Electron helper process constantly allocating more and more memory and then crushes at some point and start over. CPU consumptions is 350% around that time.
OS X Yosemite.

Closing as duplicate of #774. We believe the issue to be when having a large folder (gigabytes) and installing the file watcher on it.

@q42jaap @ragebiswas @Kane-Sendgrid @kevinkucharczyk @planetexpress69  is one of you able to do a little experiment? I am speculating that maybe our library for file watching is failing. The steps would be:

setup to run vscode out of our sources as described at https://github.com/Microsoft/vscode/wiki/How-to-Contribute
copy the contents of Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/chokidar into the sources at ./node_modules/chokidar (replace the entire folder)
open ./node_modules/chokidar/lib/fsevents-handler.js from the sources and insert console.log(fsevents) in line 9
run code out of sources with ./scripts/code.sh and send me the output

For me (since fsevents works ok), I get this:
~/Development/monaco/scripts> ./code.sh
[10:07:53] Using gulpfile ~/Development/monaco/gulpfile.js
[10:07:53] Starting 'electron'...
[10:07:53] Finished 'electron' after 1.28 ms
[9931:0308/100756:INFO:CONSOLE(199)] "%c[Extension Host] %cdebugger listening on port 5870", source: file:////Users/bpasero/Development/monaco/out/vs/workbench/services/thread/electron-browser/threadService.js (199)
[9931:0308/100802:INFO:CONSOLE(199)] "%c[Extension Host] %cdebugger listening on port 5870", source: file:////Users/bpasero/Development/monaco/out/vs/workbench/services/thread/electron-browser/threadService.js (199)
~/Development/monaco/scripts> ./code.sh
{ [Function: watch]
  getInfo: [Function: getInfo],
  FSEvents: [Function: FSEvents],
  Constants:
   { kFSEventStreamEventFlagNone: 0,
...

If something goes wrong, I would expect fsevents to print as undefined. In that case, can you put another console.log inside the try/catch block of line 7 to see what the error is loading that native module?
Thanks!

@bpasero fsevents is indeed undefined there.

thanks, we figured that it must be something else. is it possible to share the workspace with me go reproduce?

@bpasero looks like this issue is specific to a project, unfortunately I can't share it. Is there anything else I can help to debug it?

Hi there,
undefined as well.

martin@mbp13 scripts [master] $ ./code.sh
undefined
[08:52:23] Using gulpfile ~/Desktop/vscode/gulpfile.js
[08:52:23] Starting 'electron'...
[08:52:23] Finished 'electron' after 741 μs
[2333:0309/085225:INFO:CONSOLE(199)] "%c[Extension Host] %cdebugger listening on port 5870", source: file:////Users/martin/Desktop/vscode/out/vs/workbench/services/thread/electron-browser/threadService.js (199)

Am 08.03.2016 um 11:53 schrieb Benjamin Pasero<EMAIL_ADDRESS>@q42jaap https://github.com/q42jaap @ragebiswas https://github.com/ragebiswas @Kane-Sendgrid https://github.com/Kane-Sendgrid @kevinkucharczyk https://github.com/kevinkucharczyk @planetexpress69 https://github.com/planetexpress69 is one of you able to do a little experiment? I am speculating that maybe our library for file watching is failing. The steps would be:
setup to run vscode out of our sources as described at https://github.com/Microsoft/vscode/wiki/How-to-Contribute https://github.com/Microsoft/vscode/wiki/How-to-Contribute
copy the contents of Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/chokidar into the sources at ./node_modules/chokidar (replace the entire folder)
open ./node_modules/chokidar/lib/fsevents-handler.js from the sources and insert console.log(fsevents) in line 9
run code out of sources with ./scripts/code.sh and send me the output
For me (since fsevents works ok), I get this:
~/Development/monaco/scripts> ./code.sh
[10:07:53] Using gulpfile ~/Development/monaco/gulpfile.js
[10:07:53] Starting 'electron'...
[10:07:53] Finished 'electron' after 1.28 ms
[9931:0308/100756:INFO:CONSOLE(199)] "%c[Extension Host] %cdebugger listening on port 5870", source: file:////Users/bpasero/Development/monaco/out/vs/workbench/services/thread/electron-browser/threadService.js (199)
[9931:0308/100802:INFO:CONSOLE(199)] "%c[Extension Host] %cdebugger listening on port 5870", source: file:////Users/bpasero/Development/monaco/out/vs/workbench/services/thread/electron-browser/threadService.js (199)
~/Development/monaco/scripts> ./code.sh
{ [Function: watch]
getInfo: [Function: getInfo],
FSEvents: [Function: FSEvents],
Constants:
{ kFSEventStreamEventFlagNone: 0,
...
If something goes wrong, I would expect fsevents to print as undefined. In that case, can you put another console.log inside the try/catch block of line 7 to see what the error is loading that native module?
Thanks!
—
Reply to this email directly or view it on GitHub https://github.com/Microsoft/vscode/issues/1009#issuecomment-193724632.

Can’t share my workspace, but either 0.10.10 or my upgrade to ember 2.4 and rebuilding the whole node_modules („hairy fireball of death®“) fixed the problem for me.
M.

Am 08.03.2016 um 22:37 schrieb Benjamin Pasero<EMAIL_ADDRESS>thanks, we figured that it must be something else. is it possible to share the workspace with me go reproduce?
—
Reply to this email directly or view it on GitHub https://github.com/Microsoft/vscode/issues/1009#issuecomment-193978748.

I'll add a "me too" to this issue. I am using VSCode with Unity and the project size is small, yet it's still chomping at my CPU (MBP, Yosemite).

@trojanfoe able to share this workspace with me? what OSX are you on?

@Kane-Sendgrid @planetexpress69 very sorry, I realized my instructions were not good and I have updated them. the output we see on the console is coming from a different use of chokidar, not the one from VS Code. the new instructions are slightly different but not much and we can see if chokidar is running by looking at the developer console within Code. Can you retry please?

@bpasero for me it's only logging: debugger listening on port 5870 and nothing after that.

@bpasero There wasn't anything particularly special about the project.  I think if you created a new Unity project, set it up to use VS Code and then attempted to edit some scripts, you would see the same issue.
I am using OSX 10.11.3 on a fairly old MBP (Late 2010).

@Kane-Sendgrid thanks for trying, I guess when you changed the file you did not recompile, could that be true? We typically run gulp watch first, which will compile the project and listen for changes to incrementally compile.

@bpasero [Service Library: Watcher] Do we have fsevents?:  true

@Kane-Sendgrid thanks, so this means the native (and good) file watcher is active. it is interesting that you say your coworker is not seeing issues, maybe this could lead us to the actual problem. some questions:

does your co worker have similar hardware as you (mainly is the disk a SSD in both machines)?
are you seeing the CPU spike NEVER going down or after a moment going down?
is your co worker not seeing a CPU spike at all?

We have similar hardware (I have MacBook Pro 15, he has 13, same year model). I'm seeing Electron Helper process spiking in CPU and memory and then it dies and starts ramping up again. Let me wait and see how long it can go (it was going at least 5 cycles for me during ~10 minutes). My coworker doesn't see spike.

@Kane-Sendgrid interesting, so you say the process increases also in memory and then actually exits and starts this process over again?
Can you give me some numbers on the workspace: how many files and folders?
I realise that we always restart the watching process when it dies so it would never end for you.
I cannot believe that your co worker is not seeing an increase in memory and CPU when opening the same folder though, does he have other settings than you? is he really opening the same folder?

We found out about the issue and here is what happens:

user opens a large folder in VS Code
VS Code installs a watcher on the root of the folder from another process
watcher starts to walk the folder in a way that memory increases a lot
eventually the process dies with out of memory
VS Code detects this and starts the watcher again because we typically never want to loose the watching information
this goes on and on forever and simply results in constant and high CPU use

We also verified that chokidar was not falling back to polling.
The fixes for March are:

allow the user to configure excludes from the new files.watcherExclude setting
add node_modules to the excluded folders by default
do not restart chokidar after 5 failing attempts

For the future, we are looking into https://github.com/Microsoft/vscode/issues/3998

I'm seeing this issue on version 1.4.0 for OS X El Capitan.

I notice this only happens after I open my project's .gitignore, the file is pretty small in size (2.5K), so this might be a different issue with the same outcome.

@andradei can you check the full arguments of the process to see which of our processes are causing it?

@bpasero How do I do that?

I found out that an extension was causing this for me:
I'll leave the issue reference here in case it is helpful.
https://github.com/kantlove/vscode-todo-parser/issues/21

VSCode 1.4.0
I've also encountered this issue, I'm seeing one Code Helper instance eating 100% of one core power.
Full arguments to the process:
/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=watcherService

My settings.json:
{
      "editor.tabSize": 2,
      "compilerOptions": {
        "target": "ES6"
      },
      "files.exclude": {
            "**/.git": true,
            "**/.svn": true,
            "**/.hg": true,
            "**/.DS_Store": true,
            "node_modules": true
      }
}

Extensions I'm using:
beautify
jsx
Handlebars
ESLint (disabled for this project)
GIt History
Auto Close Tag
Color Highlight
vscode-icons
Bootstrap 3 Snippets
Javascript (ES6) code snippets
Reactjs code snippets

@RafalWilinski does it also reproduce when running without extensions loaded:
I am very sorry to hear you are having issues with VS Code. I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line, execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

I've just removed all extensions and reopened project - same thing happens.
Project I'm opening: https://github.com/RafalWilinski/ember-gmail
Let me know if you need more info.

@RafalWilinski so you say you have a single folder with lots of files within? what kind of folder is that? maybe we should consider adding it to the default watcher exclude setting.

Btw I just setup this project and do not see a 100% CPU core (Mac OS X).

In my project there was a tmp folder generated by babel. Inside, there are around 20000 subfolders and tree | wc -l = 522100 files & directories overall with total weight of 1.2GB(!), it took a couple of seconds to even rm -fr /tmp it.
I don't tmp folder should be ignored by default.
@bpasero Because repo does not have /tmp folder in it, it accumulates over the time.

ok thanks, for me the folder was much smaller. you can get the CPU down by adding this folder to the watcher exclude and it would also make sense to add it to search excludes.


clean up .stan file tests and dependencies

Most of the models being tested in src/test/unit/gm/parser do not have their dependencies included in make/tests.
It looks like this will be really painful to add and maintain across three directories, so it'd be ideal if this could be automated somehow.

This has been fixed.


compaction do not work with s3

Thanos, Prometheus and Golang version used
docker improbable/thanos:master-2018-09-21-1e1f9e5
What happened
Run compaction to downsample long retention s3 storage but there is now new block are created, and all operation took only few seconds it more looks like it do not try to do anything with the existing blocks that has size near 6GB
What you expected to happen
I expected that compaction create new blocks with downsampled data to query
How to reproduce it (as minimally and precisely as possible):
not sure i just use docs from the github, maybe i miss something
Full logs to relevant components
/ # thanos compact --objstore.config-file=/creds/s3-config --http-address="" --log.level=debug
level=info ts=2018-09-27T19:35:49.170523334Z caller=factory.go:47 msg="loading bucket configuration file" filename=/creds/s3-config
level=info ts=2018-09-27T19:35:49.171236275Z caller=compact.go:223 msg="starting compact node"
level=info ts=2018-09-27T19:35:49.171514704Z caller=compact.go:811 msg="start sync of metas"
level=info ts=2018-09-27T19:35:49.171585369Z caller=main.go:292 msg="Listening for metrics" address=
level=debug ts=2018-09-27T19:35:49.390452488Z caller=compact.go:174 msg="download meta" block=01CRDHPRJJ2EM8GKAYQ3PM3MEC
level=debug ts=2018-09-27T19:35:49.439990558Z caller=compact.go:174 msg="download meta" block=01CRDHTP7BY4Z4GCZY68S7A4GQ
level=debug ts=2018-09-27T19:35:49.470718626Z caller=compact.go:174 msg="download meta" block=01CRDRKP9AWZKNQB4CNVAKR3H5
level=debug ts=2018-09-27T19:35:49.502677747Z caller=compact.go:174 msg="download meta" block=01CRDRPDDKKGR3MKX93KPTS78G
level=debug ts=2018-09-27T19:35:49.540440283Z caller=compact.go:174 msg="download meta" block=01CRDZEG4NT340RQQ6GJ9P06JJ
level=debug ts=2018-09-27T19:35:49.560644244Z caller=compact.go:174 msg="download meta" block=01CRDZJ4NDTZ4XB8C8WKRT0N3K
level=debug ts=2018-09-27T19:35:49.587291398Z caller=compact.go:174 msg="download meta" block=01CRE6C1Z7ZPHF7350QGQF06VE
level=debug ts=2018-09-27T19:35:49.618160311Z caller=compact.go:174 msg="download meta" block=01CRE6DVXC0ZMHA5W87948BJCH
level=info ts=2018-09-27T19:35:49.65045978Z caller=compact.go:817 msg="start of GC"
level=info ts=2018-09-27T19:35:49.658204413Z caller=compact.go:149 msg="compaction iterations done"
level=info ts=2018-09-27T19:35:49.658279946Z caller=compact.go:156 msg="start first pass of downsampling"
level=info ts=2018-09-27T19:35:49.835052424Z caller=compact.go:162 msg="start second pass of downsampling"
level=info ts=2018-09-27T19:35:50.015181588Z caller=compact.go:167 msg="downsampling iterations done"
level=info ts=2018-09-27T19:35:50.015307227Z caller=retention.go:17 msg="start optional retention"
level=info ts=2018-09-27T19:35:50.201559202Z caller=retention.go:46 msg="optional retention apply done"
level=info ts=2018-09-27T19:35:50.202410485Z caller=main.go:168 msg=exiting

Anything else we need to know
Uncomment and fill if you use not casual environment or if it might be relevant.
Environment:

OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Others:
Version of prometheus with sidecar is 2.3.1

Sure, it will not compact anything if there is nothing to compact. It needs at least 3 source blocks of smaller compaction level, so it will take time.
Downsampling hits in only after longer time as well, as there is no need to downsample fresh data.
Let me know if I am missing something here I will reopen - otherwise, it it expected.

@bwplotka  thank you very much for answer i alredy see that it start to work. So i have only one more question, is there any information how downsampling trigger, i mean dows it will start only for data only than 1 day or something similar. And if there is a way i can configure what data i need to downsample, for example, i need to downsample all that older than 1 week

@bwplotka Update looks like i found what will trigger downsampling, need to wait https://github.com/improbable-eng/thanos/blob/984f42ea00f1e62d599709382408e6c1861212b2/cmd/thanos/downsample.go#L169
for 5 minutes downsampling
and
https://github.com/improbable-eng/thanos/blob/984f42ea00f1e62d599709382408e6c1861212b2/cmd/thanos/downsample.go#L190
for 1h downsampling
Does it possible to make this parameters configurable?
Dows it possible to configure downsampling resolution, for example not 5 minutes but 10 minutes.
Also notice one thing, if retention for row data is configured less than downsampling start to work it will delete all raw data before it will be downsampled, but maybe i miss some other parameter


feat: add tabs to edit dataset page

SUMMARY
This pr will begin the new flow for the edit dataset page once a user creates a new dataset. It also adds the tabs for the edit page.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/17326228/200560849-c9527159-7717-4600-bdf6-077e4bed7e6b.mov
TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

Looks good, but I am going to do some quick visual testing

visual testing looks great! Thanks


Example 04 is not runnable

$ python3 qwiic_alphanumeric_ex04_set_brightness.py

SparkFun Qwiic Alphanumeric - Example 5: Set Brightness

Qwiic Alphanumeric Ready!
Traceback (most recent call last):
  File "qwiic_alphanumeric_ex04_set_brightness.py", line 70, in <module>
    run_example()
  File "qwiic_alphanumeric_ex04_set_brightness.py", line 65, in run_example
    my_display.display_print("Milk")
AttributeError: 'QwiicAlphanumeric' object has no attribute 'display_print'

Looks like
https://github.com/sparkfun/Qwiic_Alphanumeric_Py/blob/594e4d99a8051d5af514cd74a15d2a9b8280dfb2/examples/qwiic_alphanumeric_ex04_set_brightness.py#L65
was incorrectly copy/pasted or something, should be updated to be my_display.print("Milk")


Doc migration updates

Description
Documentation is being moved to the doc portal.  So content is being removed from here and linked to the doc portal/CSM GitHub repository.
Issues
List the issues impacted by this PR:

Issue ID

Checklist

[x] I have performed a self-review of my own code
[ ] I have run 'make check' to ensure my code does not have any formatting, vetting, linting, or security issues
[ ] I have run 'make test' to ensure new and existing unit tests pass locally with my changes
[ ] I have not allowed coverage numbers to degrade
[ ] I have maintained at least 90% code coverage
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[x] Visual inspection of changes and manual testing of links.

e2e pass


ci: sporadic failures "Exit 127"

cos-toolkit version:
Not relevant
CPU architecture, OS, and Version:

Describe the bug
Sporadically CI fails with ERRO[0000] fatal error: exit status 127 or more generically with exit status 127 in different places. This is happening very frequently, and becomes more noticeable now
To Reproduce
Happened to me locally too (only once). My guess is a simple looping on the binaries generated with UPX will eventually fail with the above
Expected behavior
To not fail
Logs

Additional context
I suspect it's due to part of our binaries (luet and extensions) compressed with UPX. See also upstream issues about it: https://github.com/upx/upx/issues/385 https://github.com/upx/upx/issues/224 https://github.com/upx/upx/issues/225 .
I'll use this issue to track all the occurences

https://github.com/rancher-sandbox/cOS-toolkit/runs/2959979887

I suspect it's due to part of our binaries (luet and extensions) compressed with UPX. See also upstream issues about it:

If so I'd suggest to add a toggle to use UPX or not and then just give it a try for some time without. On CI this happens quite often, I mostly saw it on make deps step. If the issue disappears without it I'd say we have to forget about UPX until it gets fixed upstream.

I suspect it's due to part of our binaries (luet and extensions) compressed with UPX. See also upstream issues about it:

If so I'd suggest to add a toggle to use UPX or not and then just give it a try for some time without. On CI this happens quite often, I mostly saw it on make deps step. If the issue disappears without it I'd say we have to forget about UPX until it gets fixed upstream.

I do agree, but I would give a deeper look as we could also try to downgrade https://github.com/upx/upx/issues/225#issuecomment-428379251 or try to use a different upx option, I think --brute is causing issues

This is happening now everytime on master, see https://github.com/rancher-sandbox/cOS-toolkit/runs/2972359148, raising prio and moving it in Todo

I think we can close this for now and re-open it if needed, doesn't seems happening anymore after disabling upx


Application is "vidmanlive" instead of "liveorigin"

Hey all,
Can you successfully start a broadcast from for example ffmpeg?
As I can see when you create a broadcast the application in the response is "vidmanlive" (but not "liveorigin"). When I try to start streaming to it I go the following error in ffmpeg:
Parsed protocol: 4
Parsed host    : vidman-eu-central-1.periscope.tv
Parsed app     : vidmanlive?t=...
RTMP_Connect1, ... connected, handshaking
HandShake: Type Answer   : 03
HandShake: Server Uptime : 0
HandShake: FMS Version   : <IP_ADDRESS>
HandShake: Handshaking finished....
RTMP_Connect1, handshaked
Invoking connect
RTMP_ReadPacket, failed to read RTMP packet header
rtmps://vidman-eu-central-1.periscope.tv:443/vidmanlive?t=...: Unknown error occurred

Same for RTMP and RTMPS.
Do you get the same?

I got it. I used to specify User Agent as "Periscope/2699 (iPhone; iOS 8.1.2; Scale/2.00)" within a request and periscope returns vidmanlive. If I do not specify anything periscope returns liveorigin.

Probably the liveorigin is legacy now?

@DmT021 I always get vidman. Although i'm getting an I/O error from that now


Once quarkiverse extension upgrades google-cloud-storage to 1.113.8, remove exclusion in google-storage extension

Camel and quarkiverse google-storage are not aligned with google-cloud-storage library. (1.113.4 vs 1.113.8) Issue in quarkiverse is reported as https://github.com/quarkiverse/quarkus-google-cloud-services/issues/113
If quarkiverse extension is upgraded, remove exclusios in google-storage/runtime extension.

Out of date since we no longer use the quarkus-google-cloud-services extensions.


How to avoid CUDA_ERROR_OUT_OF_MEMORY: out of memory, when --phi = 1?

Dear all,
My environment: Windows 10, RAM 32, Python 3.7.4, CUDA 11.0, nvcc (Cuda compilation tools, release 10.0, V10.0.130), RTX2060, Driver Version: 445.75, tensorflow-gpu==1.15.0
I got CUDA_ERROR_OUT_OF_MEMORY: out of memory when using --phi = 1
How to solve this problem?
Thank you very much in advance.
Warmest regards,
Suryadi
`
python train.py --epochs 2 --snapshot imagenet --phi 1 --gpu 0 --random-transform --compute-val-loss --freeze-backbone --batch-size 8 --steps 2 pascal D:\learn\pascal\VOCtrainval_11-May-2012\VOCdevkit\VOC2012
(many lines are deleted here)
Total params: 7,225,352
Trainable params: 1,057,976
Non-trainable params: 6,167,376

None
Ada tensorboard_callback =  <tensorflow.python.keras.callbacks_v1.TensorBoard object at 0x000001FC8C43A308>
Epoch 1/2
2020-04-16 00:59:01.269505: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2020-04-16 00:59:02.332008: W tensorflow/stream_executor/cuda/redzone_allocator.cc:312] Internal: Invoking ptxas not supported on Windows
Relying on driver to perform ptx compilation. This message will be only logged once.
2020-04-16 00:59:02.431162: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cublas64_100.dll
2020-04-16 00:59:03.204061: W tensorflow/core/common_runtime/bfc_allocator.cc:305] Garbage collection: deallocate free memory regions (i.e., allocations) so that we can re-allocate a larger region to avoid OOM due to memory fragmentation. If you see this message frequently, you are running near the threshold of the available device memory and re-allocation may incur great performance overhead. You may try smaller batch sizes to observe the performance impact. Set TF_ENABLE_GPU_GARBAGE_COLLECTION=false if you'd like to disable this feature.
2020-04-16 00:59:03.263676: I tensorflow/stream_executor/cuda/cuda_driver.cc:831] failed to allocate 3.50G<PHONE_NUMBER> bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory
2020-04-16 00:59:06.194695: I tensorflow/core/profiler/lib/profiler_session.cc:205] Profiler session started.
2020-04-16 00:59:06.198217: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cupti64_100.dll
1/2 [==============>...............] - ETA: 11s - loss: 4.2019 - regression_loss: 2.8140 - classification_loss: 1.38802020-04-16 00:59:06.774271: I tensorflow/core/platform/default/device_tracer.cc:588] Collecting 2822 kernel records, 11 memcpy records.
Traceback (most recent call last):
File "train.py", line 388, in
main()
File "train.py", line 383, in main
validation_data=validation_generator
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\keras\engine\training.py", line 1296, in fit_generator
steps_name='steps_per_epoch')
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\keras\engine\training_generator.py", line 294, in model_iteration
callbacks._call_batch_hook(mode, 'end', step, batch_logs)
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\keras\callbacks.py", line 236, in _call_batch_hook
batch_hook(batch, logs)
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\keras\callbacks.py", line 519, in on_train_batch_end
self.on_batch_end(batch, logs=logs)
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\keras\callbacks_v1.py", line 362, in on_batch_end
profiler.save(self.log_dir, profiler.stop())
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\eager\profiler.py", line 140, in save
gfile.MakeDirs(plugin_dir)
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\lib\io\file_io.py", line 438, in recursive_create_dir
recursive_create_dir_v2(dirname)
File "C:\Users\ASUS\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\lib\io\file_io.py", line 453, in recursive_create_dir_v2
pywrap_tensorflow.RecursivelyCreateDir(compat.as_bytes(path))
tensorflow.python.framework.errors_impl.NotFoundError: Failed to create a directory: logs/2020-04-16\plugins\profile\2020-04-16_00-59-06; No such file or directory
`

The validation dataset usually fed in GPU in 1 batch, try to train without compute_val_loss, and  manually calculate the mAP if you have a large validation data

Try smaller batch size. But then you should probably add the -freeze-bn option. Because batch normalization does not work good with small batches. What puzzles me the RTX2060 should have enough RAM for batchsize=8 are other programs running on the GPU?


[REQUEST] make nanoVDB CUDA async allocation optional so it can be used on vGPU

Is your feature request related to a problem? Please describe.
Current nanoVDB implementation uses functions like cudaMallocAsync and cudaMemcpyAsync, for example in CudaDeviceBuffer when allocating or uploading data to the GPU. These functions are not available when using a vGPU that does not have unified memory enabled, which is common for example for GPU-enabled Azure VM's where the GPU is shared/sliced between multiple instances. Trying to run nanoVDB code on such a VM will result in CUDA 801 'not supported' exceptions.
Describe the solution you'd like
Projects such as PyTorch usually implement the async code paths using a switch to enable/disable them, plus a fallback path that uses synchronous functions. If nanoVDB had something similar, that would be the perfect solution, save for potential efficiency disadvantages the synchronous fallback paths could have.
Describe alternatives you've considered
For my situation there is not really an alternative, as I am not in a position to change hypervisor settings to enable unified memory support or use some other deployment target for the code I want to use with nanoVDB. The only option is to switch to a VM that uses passthrough GPU instead of vGPU, but again this is not something under my control.

Some more information/corrections:

This is only about cudaMallocAsync and cudaMallocFree, not cudaMcpyAsync etc.
Upon closer inspection of nanovdb/util/cuda/CudaUtils.h I found out there is already a fallback path when building with CUDA versions prior to 11.2 (the version that introduced async malloc functions)

Based on this, I created PR #1799 that introduces macros CUDA_MALLOC and CUDA_FREE, and a define NANOVDB_USE_SYNC_CUDA_MALLOC that can be set by the host build system to force synchronous CUDA allocations.


Fixes typos in the title bar article

Fixes #1570

@mijacobs : The PR passed the acceptance checklist. Please evaluate further and approve/complete the PR if appropriate. Thanks!


chore(Data/Finset/PiInduction): remove porting note about clear_value

This tactic now exists.

I'm not sure if this is the right fix; opinions welcome.

bors merge
Thanks!


Cannot set certificate transparency

This is autogenerated. Please review and update as needed.
Describe the bug
Trying to create certificate request with policy incl. certificate transparency fails with "Cannot set Certificate Transparency for a manual enrollment."
Command Name
az keyvault certificate create
Errors:
Cannot set Certificate Transparency for a manual enrollment.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az keyvault certificate create --vault-name {} -n {} -p {}

Policy JSON:
{
  "issuerParameters": {
    "certificateTransparency": true,
    "name": "Unknown"
  },
  "keyProperties": {
    "curve": null,
    "exportable": true,
    "keySize": 2048,
    "keyType": "RSA",
    "reuseKey": false
  },
  "secretProperties": {
    "contentType": "application/x-pkcs12"
  },
  "x509CertificateProperties": {
    "keyUsage": [
      "cRLSign",
      "dataEncipherment",
      "digitalSignature",
      "keyEncipherment",
      "keyAgreement",
      "keyCertSign"
    ],
    "subject": "CN=foobar.net",
    "validityInMonths": 24
  }
}

Expected Behavior
Certificate request is created
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Installer: MSI

azure-cli 2.5.1

Additional Context

@bim-msft please take a look

Apologies for the +1 but I'm also seeing this issue.

hi @fabicz the error is from Azure Keyvault service

@RandalliLama from key vault service team will be looking into it

ping @RandalliLama

@RandalliLama do we have internal ADO open to track?

@RandalliLama for triaging

@RandalliLama for triaging

This has been fixed and is no longer an issue.
#please-close