doesn't work

Hi !
I follow the steps in the usage but some problems happened.
Your program seems don't work properly and I don't know the reason.
It just convert only one .md file.
if it is because of the Chinese characters ?

Initially, I guess that can be the reason. Unicode can't decode Chinese characters, thus giving an error.
Here is a possible solution on Stack Overflow.
If possible, please run the code manually i.e., by double clicking PubsidianConverter.py from this folder and paste the error code from the terminal. It will help to debug further.
Thank you.

Since, command line is windows default GBK code, all ' Chinese characters' .encode(‘gbk') When the output result is the same as the 'Chinese character' result.
To sum up, str of python is actually a kind of unicode, and python's default code is ascii. When non-ascii is converted to ascii, an error will be reported.


Python 3 support

Make changes necessary to be Python 3 compatible and test on Python 3.
Simplistically, changes are to (a) how some exceptions are handled, (b) to some utility scripts that may not be used, (c) to the test tile source, (d) to some tests.  Prior to this, the plugin was manually tested with Python 3 where it worked in common use cases.  Since this adds CI testing, it is more certain to stay working.

Could you make a note in the README (or maybe also in the requirements.txt) about the special version of pylibtiff necessary for python 3?

I've changed requirements.txt (and setup.py).  There isn't any harm in using the github version of pylibtiff, so I've made that the default with a comment in requirements.txt of when it isn't necessary.


Can we change "instant mode" to "quick fuck"?

I find it much more comical :) What's the community opinion?

👉👌? Even more concise :-))


[C++][Acero] Add the ability to merge already-sorted input nodes

Describe the enhancement requested
I have a use case wherein I want to asof join two datasets. However, each dataset on the left and right hand side is sharded across N files. Each file is individually sorted from top to bottom. Imagine a dataset composed of two files:
file A
ts,col
1,"foo"
3,"foo"
5,"foo"

file B
ts,col
2,"bar"
3,"bar"
6,"bar"

After merging
ts,col
1,"foo"
2,"bar"
3,"bar"
3,"foo"
5,"foo"
6,"bar"

Sorting using order_by isn't tenable for huge datasets. It'd be more efficient to stream each input table and emit batches in sorted order via a heap.
Merging N files this way is actually computationally similar to asof_join_node.cc in that you can efficiently do it by buffering data from all your input nodes and spawning a process thread that emits data in sorted fashion.
I propose refactoring some of the guts of asof_join_node.cc so that we can achieve the above computation. I think that this will unlock lots of potential that is hidden behind specialized databases like KDB.
I have a draft PR for the idea here: https://github.com/apache/arrow/pull/38380 and have locally tested it for O(100GB) files.
Would be curious to get opinions from @icexelloss, @bkietz, and @westonpace on this approach!
Component(s)
C++

I think this is a useful operation to have

PR is in a presentable state now--open to thoughts!

Issue resolved by pull request 38380
https://github.com/apache/arrow/pull/38380


Update dependencies to support svelte@4

Closes #109

Updated the types according to https://github.com/sveltejs/svelte/pull/8512
Updated the storybook dependencies to support svelte 4, see https://github.com/storybookjs/storybook/releases/tag/v7.0.27
Use svelte 4 internally, but allow svelte 3 as peer dependency
use Node 20 in the build pipeline
I had to remove the webpackFinal stuff in the storybook main.js for it to work and according to this comment it was not needed either

The included storybook run fine for me locally.
I am not familiar with the build process with github actions, so feel free to edit anything.

I do not know if the peer dependency version of storybook should also be ^7.0.27, or if it will be fine this way

:rocket: PR was released in v3.0.4 :rocket:

Thanks for the great job and for the time invested in this @RSWilli ! 👏🏽

Is it possible this should be using<EMAIL_ADDRESS>I see some extra commits supporting Svelte 4 done in that release:

https://github.com/storybookjs/storybook/releases/tag/v7.1.0-rc.2

Also, when running my project with v3.0.4 I get the following error which I'm not sure if it's related:
stacktrace

Failed to load preset: {"type":"presets","name":"/Users/XXX/dev/mainmatter/chouchou/node_modules/.pnpm/@storybook+addon-svelte-csf@3.0.4_@storybook+svelte@7.1.0_@storybook+theming@7.0.22_<EMAIL_ADDRESS>on level 1
ERR! /Users/XXX/dev/mainmatter/chouchou/node_modules/.pnpm/@storybook+addon-svelte-csf@3.0.4_@storybook+svelte@7.1.0_@storybook+theming@7.0.22_@sveltejs_h2rr5co6q2uverg6qodhdmucde/node_modules/@storybook/addon-svelte-csf/dist/cjs/preset/index.js:1
ERR! import { svelteIndexer } from './indexer.js';
ERR! ^^^^^^
ERR!
ERR! SyntaxError: Cannot use import statement outside a module
ERR!     at internalCompileFunction (node:internal/vm:73:18)
ERR!     at wrapSafe (node:internal/modules/cjs/loader:1178:20)
ERR!     at Module._compile (node:internal/modules/cjs/loader:1220:27)
ERR!     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
ERR!     at Object.newLoader (/Users/XXX/dev/mainmatter/chouchou/node_modules/.pnpm/esbuild-register@3.4.2_esbuild@0.18.11/node_modules/esbuild-register/dist/node.js:2262:9)
ERR!     at extensions..js (/Users/XXX/dev/mainmatter/chouchou/node_modules/.pnpm/esbuild-register@3.4.2_esbuild@0.18.11/node_modules/esbuild-register/dist/node.js:4807:24)
ERR!     at Module.load (node:internal/modules/cjs/loader:1119:32)
ERR!     at Module._load (node:internal/modules/cjs/loader:960:12)
ERR!     at Module.require (node:internal/modules/cjs/loader:1143:19)
ERR!     at require (node:internal/modules/cjs/helpers:110:18)
ERR!  /Users/XXX/dev/mainmatter/chouchou/node_modules/.pnpm/@storybook+addon-svelte-csf@3.0.4_@storybook+svelte@7.1.0_@storybook+theming@7.0.22_@sveltejs_h2rr5co6q2uverg6qodhdmucde/node_modules/@storybook/addon-svelte-csf/dist/cjs/preset/index.js:1
ERR! import { svelteIndexer } from './indexer.js';
ERR! ^^^^^^
ERR!
ERR! SyntaxError: Cannot use import statement outside a module
ERR!     at internalCompileFunction (node:internal/vm:73:18)
ERR!     at wrapSafe (node:internal/modules/cjs/loader:1178:20)
ERR!     at Module._compile (node:internal/modules/cjs/loader:1220:27)
ERR!     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
ERR!     at Object.newLoader (/Users/XXX/dev/mainmatter/chouchou/node_modules/.pnpm/esbuild-register@3.4.2_esbuild@0.18.11/node_modules/esbuild-register/dist/node.js:2262:9)
ERR!     at extensions..js (/Users/XXX/dev/mainmatter/chouchou/node_modules/.pnpm/esbuild-register@3.4.2_esbuild@0.18.11/node_modules/esbuild-register/dist/node.js:4807:24)
ERR!     at Module.load (node:internal/modules/cjs/loader:1119:32)
ERR!     at Module._load (node:internal/modules/cjs/loader:960:12)
ERR!     at Module.require (node:internal/modules/cjs/loader:1143:19)
ERR!     at require (node:internal/modules/cjs/helpers:110:18)

This is my list of dependencies

"devDependencies": {
   "@fontsource-variable/inter": "^5.0.3",
   "@playwright/test": "1.36.1",
   "@storybook/addon-essentials": "^7.1.0",
   "@storybook/addon-interactions": "^7.1.0",
   "@storybook/addon-links": "^7.1.0",
   "@storybook/addon-styling": "^1.3.4",
   "@storybook/addon-svelte-csf": "^3.0.4",
   "@storybook/blocks": "^7.1.0",
   "@storybook/jest": "^0.1.0",
   "@storybook/svelte": "^7.1.0",
   "@storybook/sveltekit": "^7.1.0",
   "@storybook/test-runner": "^0.11.0",
   "@storybook/testing-library": "^0.2.0",
   "@sveltejs/adapter-cloudflare": "^2.3.1",
   "@sveltejs/kit": "1.22.3",
   "@tailwindcss/forms": "^0.5.3",
   "@tailwindcss/typography": "^0.5.9",
   "@types/testing-library__jest-dom": "^5.14.8",
   "@typescript-eslint/eslint-plugin": "5.62.0",
   "@typescript-eslint/parser": "5.62.0",
   "autoprefixer": "10.4.14",
   "chromatic": "^6.19.8",
   "concurrently": "^8.2.0",
   "eslint": "8.45.0",
   "eslint-config-prettier": "8.8.0",
   "eslint-plugin-playwright": "^0.15.1",
   "eslint-plugin-promise": "^6.1.1",
   "eslint-plugin-storybook": "^0.6.12",
   "eslint-plugin-svelte": "2.32.2",
   "postcss": "8.4.26",
   "postcss-import": "^15.1.0",
   "postcss-load-config": "4.0.1",
   "prettier": "2.8.8",
   "prettier-plugin-jsdoc": "^0.4.2",
   "prettier-plugin-svelte": "2.10.1",
   "prettier-plugin-tailwindcss": "^0.4.0",
   "react": "^18.2.0",
   "react-dom": "^18.2.0",
   "storybook": "^7.1.0",
   "svelte": "4.0.5",
   "svelte-check": "3.4.6",
   "tailwindcss": "3.3.3",
   "tslib": "2.6.0",
   "typescript": "5.1.6",
   "vite": "4.4.4",
   "vitest": "0.33.0"
},

Let me know if this relates to this issue or if I need to open a new one with more information.
Again, thanks for the effort and giving back to the community ❤

@oscard0m I am getting the same error here, I think this happens because the types are now svelte 4 typings, which are incompatible with the svelte 3 typings in my project
I think this needs a new PR, if we want to support both svelte 3 and 4

@oscard0m I am getting the same error here, I think this happens because the types are now svelte 4 typings, which are incompatible with the svelte 3 typings in my project

Thanks for the quick answer and for giving some light here @RSWilli!

I think this needs a new PR, if we want to support both svelte 3 and 4

I'm not sure what are the steps to follow:

Do we want addon-svelte-csf to be retro-compatible with Svelte 3? In my mind, this should be a major release, and users can stay with in the previous version, which supports Svelte v3
Do you know What is the versioning criteria for this addon? @JReinhold

I think @joelmukuthu is correct, that what you're seeing @oscard0m is #111.

I think this happens because the types are now svelte 4 typings, which are incompatible with the svelte 3 typings in my project

@RSWilli I don't think the typings should be breaking, because we did the same changes in core without breaking anything. But if they indeed are, then we should revert this PR and release it as a major instead.

@benpaquier the error you're seeing is #111, which comes from Storybook v7.1. I suggest you try pinning your Storybook dependencies to version 7.0.27.
#113 should fix this when it's released.


Category filters should send as few ones as possible

Category filter should decide if sending accepted or rejected is better, so it can send the minimum subset of categories.
Having 100 categories:

If I accept 2, it should send those 2 as accepted.
If I accept 90 (or reject 10), it should send those 10 as rejected.

On it.

Working! If we find any issue, let's open a new one.


Can you elaborate the nginx.conf please?

I am trying to configure the nginx server to implement the nginx.conf. Can you please elaborate the steps in the Readme please?

@debanjanbasu did you find an answer? For me its saying page isn't working

nginx.conf does not seem to be working. Any of you find a solution to this ?

I have just simplified the rewrite rules for dummyimage.com to work. Now named image sizes like hd1080 and skyscraper are handled by the PHP code and not rewrite rules. For nginx to work You should just need to add these two rules somewhere in your site's server conf:
error_page 404 = @404;
location @404 {
   rewrite (.*) /code.php?x=$request_uri last;
}

rewrite (.*) /code.php?x=$request_uri last;

See https://github.com/kingkool68/dummyimage/blob/9ec16b9c728a1a63a10fc6004d96198c6350cd84/nginx.conf
See #38 and the PR #39 for more details.


Validate Log Schemas

Feature Request
Problem
When working with the log ingestion API I found it hard to contain issues when logs don't appear in the Log Analytics Workspace. Especially debugging the schema was error prone.
Proposal
Introduce a function to validate the send log against the schema.
Details
For example given the following source code, I've created a JSON log as an object instead of an array:
ctx := context.Background()
client, err := azlogs.NewClient(endpoint, creds, &azlogs.ClientOptions{})
if err != nil {
	log.Fatal(err)
}

// Created JSON as an object instead of an array.
exampleJSON := map[string]string{
	"cve":   "CVE-12345",
	"alert": "violated something in the api-server",
}

logs, err := json.Marshal(exampleJSON)
if err != nil {
	log.Fatal(err)
}

_, err = client.Upload(ctx, dataCollectionRuleId, streamNameTable, logs, &azlogs.UploadOptions{})
if err != nil {
	log.Fatal(err)
}

This code will return a success status code. In Azure I could not find the appropriate place to see error logs from the respective DCR (in this case there was no transformation query).
This can lead to long debug cycles because it takes approximately 1-3 minutes until logs show up, and longer to recognize my send data didn't matched the schema.

Hi @SimonBaeumer! There's currently no operation to do exactly what you described, but you can use the QueryWorkspace method in our query/azlogs module to programmatically get the schema for your custom table in your Log Analytics Workspace. This might help with debugging.
I would use the getschema Kusto query which returns the names and types of each column in the table.
Example:
package main

import (
	"context"
	"fmt"

	"github.com/Azure/azure-sdk-for-go/sdk/azcore/to"
	"github.com/Azure/azure-sdk-for-go/sdk/azidentity"
	"github.com/Azure/azure-sdk-for-go/sdk/monitor/query/azlogs"
)

func main() {
	cred, err := azidentity.NewDefaultAzureCredential(nil)
	if err != nil {
		//TODO: handle error
	}

	client, err := azlogs.NewClient(cred, nil)
	if err != nil {
		//TODO: handle error
	}

	res, err := client.QueryWorkspace(context.TODO(), "<WORKSPACE_ID>", azlogs.QueryBody{Query: to.Ptr("<TABLE_NAME> | getschema")}, nil)
	if err != nil {
		//TODO: handle error
	}
	if res.Error != nil {
		//TODO: handle partial error
	}

	// Print Rows
	for _, table := range res.Tables {
		for _, row := range table.Rows {
			fmt.Println(row)
		}
	}
}

Our troubleshooting guide has additional debugging information.


Project Reactor support

I would like to request a sample / feature of supporting Spring Project Reactor. If the ability exists right now, I would like an example for this.

Hi @lynch19,
please see the discussion in #239. We have test code in https://github.com/awslabs/aws-serverless-java-container/tree/master/aws-serverless-java-container-springboot2/src/test/java/com/amazonaws/serverless/proxy/spring/webfluxapp.
I'd appreciate if someone contributes a sample by adding it to https://github.com/awslabs/aws-serverless-java-container/tree/master/samples and creating a pull request.


skip another test to avoid flaps

This avoids a flap in travis. This test got more flappy
recently :S
r: @jcorbin @rf @kriskowal

:ok:


*: update docs-dm

First-time contributors' checklist

[x] I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added, or deleted? (Required)
add shortcuts to generate dm template
Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v3.0 changes)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Need modification after applied to another branch
[ ] Might cause conflicts after applied to another branch

/wip

Suggest changing the title to [WIP] *: add shortcuts to generate dm template. 😄

this PR is ready, plz cc @CharLotteiu

Do the changes in this PR need to be cherry picked to the release-2.0 branch? @Ehco1996

Do the changes in this PR need to be cherry picked to the release-2.0 branch? @Ehco1996

yes, i think so

/label needs-cherry-pick-2.0
/translation doing

/merge

/assign

/remove-translation doing
/translation done


Correction in yourls_die(): 'html_head' should be 'html_footer'

Now checking for html_footer action before the call to yourls_html_footer() (code was checking for html_head action instead, which is wrong).

Good catch! :mag:
Thanks a lot! :+1:

You're welcome - and thanks for YOURLS!


Add presets page update on release workflow

I removed the local javascript action and addressed Andrew's comments, but I found myself spending an important amount of time developing the action in bash, so I just created a python script for it. I don't think it is worth spending the time on implementing what the python script does directly in bash. Let me know if you think otherwise.


"google is undefined" error in Windows 10 UWP project

We slightly modified the simple example, with IMA plugin and videojs-contrib-ads plugin included, and we were able to get it work fine in a browser (we can see video playing with pre-roll and mid-rolls).
But once ported into a Windows 10 UWP project (Javascript-based), we're getting the following error:

Unhandled exception at line 1219, column 5 in ms-appx://e815aafe-3034-4f1f-b1de-fbf96af3e701/pages/playback/js/videojs.ima.js
0x800a1391 - JavaScript runtime error: 'google' is undefined

It seems to indicate that Google API script is not available, but we do have the following reference in place:
<script src="http://imasdk.googleapis.com/js/sdkloader/ima3.js"></script>
Any idea what could have caused this?

Hi there,
Unfortunately, the IMA SDK doesn't support JavaScript-in-an-app implementations - we only currently support browsers (Chrome, Firefox, etc.).
Thanks,
Shawn

Hi there,
Unfortunately the IMA SDK doesn't support JavaScript-in-an-app implementations - we currently only support web browsers (Chrome, Firefox, etc.). We've found JavaScript performance in these kind of apps to be unpredictable at best, so it's not surprising to me that the SDK isn't behaving as expected there.
Thanks,
Shawn


Ongoing problem from a closed issue.

          > You're talking about this message:

This is to be expected, and is due to the way Obsidian itself handles the frontmatter update. If you are typing into a note at the same time that Obsidian updates the frontmatter field, it will show that message. There is no "external" process modifying the file, it is Obsidian itself.
My plugin works by waiting for 10 seconds after you stop typing before updating the frontmatter. By doing it this way it reduces the chance of that message popping up. However, if you start typing again the exact instant Obsidian is updating the frontmatter field, you'll see that message. It won't affect anything, it's just annoying. Hopefully they resolve this at some point.
Please note that you do not need to have the file open for the frontmatter to update. The updates go into a queue and the file will update even after you close it.

I think there may be a bug with this still. You said the plugin waits for ten seconds after you stop typing before updating it. I regularly find I pause to think for a few seconds and carry on typing to  look up and see that this message has popped up and the middle of a couple of words is missing.
Originally posted by @creativefibro in https://github.com/alangrainger/obsidian-frontmatter-modified-date/issues/3#issuecomment-1879834985

@creativefibro as I mention, that's expected and the way that Obsidian itself handles the frontmatter update. There isn't anything that can be done to fix this, other than changing the timeout. You can edit that in the data.json file to increase it from 10 seconds to something that works better with your pausing-to-think timing. Change the value of the timeout field in data.json and then restart Obsidian.

First, let me say thank you for this wonderful plugin. It helped me a lot these past months :)
Now to the topic. I encounter this popup on a regular basis, and usually I won't think too much, but today I realized there are cases where this conflict of typing and front matter updating can cause data loss. I think maybe this is what @creativefibro is conveying in the previous comment.
Concretely, the text last inserted (in my case, 4 entire lines of text, because I was rapidly copying and pasting things) disappeared right after the conflict. And multiple undos (repeated Ctrl+Z's) do seem to confirm this by bringing back the text and rewinding the last modified time.
Personally I've already edited the timeout field in the jata.json file to 90 to try to avoid this, but I thought at least I should also report this phenomenon. Hope this helps.


fix: prune memtable/files range independently in each partition

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
https://github.com/GreptimeTeam/greptimedb/issues/4828
What's changed and what's your intention?
This PR removes the scanner level global lock for range builders. Each partition will create a range builder for a file to prune.
In UnorderedScan, each partition may prune the same file multiple times. But this usually doesn't increase the total query time.
The global lock may have potential issues while the query engine is doing something like streaming merge. Since partitions may wait for each other. If the top partition currently polling is waiting for a lock owned by another partition in the merge heap, then the top partition may never have a chance to get the lock.
Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

@coderabbitai summary


Add and require version_added lexer attribute

Next step for #2585 :)

MXML: Remove bogus mimetypes line

Savi: Fix indentation

Move versionadded data to a lexer attribute
That way, we can set it to "" for old lexers, and check that it's
present on new lexers. (In the future, we might also use it for better
presentation in the documentation.)

Make documentation use the new version_added lexer attribute

Require the version_added lexer attribute

Harmonize version_added format

Very nice!

Looks good to me, thanks! I assume finding the ones which are set to "" at the moment is a question of Git history analysis? After all, they must have been added at some point (not that I think it's worth fixing for now.)


Avoid panic if repository is not specified

Current coverage is 65.48% (diff: 100%)

Merging #79 into master will not change coverage

@@             master        #79   diff @@
==========================================
  Files            45         45
  Lines          2529       2529
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1656       1656
  Misses          698        698
  Partials        175        175

Powered by Codecov. Last update ada53ea...d4b2575

Thanks for the PRs, we are lunching soon the v4, and those example are being updated too.
Anyways, thanks!


Add feature that makes it easier to find scanlator in my language.

It's very unpleasant having to look for scanlator in my language because they are not identified in any way.  To solve this, I imagine that if the language was just written next to the scanlator it would solve everything.  Example: Mixscans (pt br).  Or if there was a feature in the extension options that had already been programmed to only open scanlators for a certain language, as already exists for subtitles in anime.

Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

That's a extension issue, not the main app's. Send a Feature request to your extension maintainer instead (also, don't forget to say the extension which you want this to be added!).

I don't want to add a new extension. I just want a feature that makes it
easier to find scanlators in my language to read manga that are in multiple
extensions.
Em sex., 2 de fev. de 2024 03:58, Claudemirovsky @.***>
escreveu:

That's a extension issue, not the main app's. Send a Feature request to
your extension maintainer instead (also, don't forget to say the extension
which you want this to be added!).
—
Reply to this email directly, view it on GitHub
https://github.com/aniyomiorg/aniyomi/issues/1389#issuecomment-1923090157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3NYHGFKKBVN7WB7656KBXDYRSFA3AVCNFSM6AAAAABCWDPBMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGA4TAMJVG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don't want to add a new extension. I just want a feature that makes it easier to find scanlators in my language to read manga that are in multiple extensions.

Such a feature would have to come from the extension, not the app.


Update dataframe.describe for pandas 1.1

In pandas 1.1, the default behavior of handling datetimes has been deprecated. Previously they were treated like categoricals (gave things like unique). In the future they'll be treated like numerics (will give things like quantiles).
In [15]: df = pd.DataFrame({"A": pd.date_range("2000", periods=2)})

In [16]: ddf = dd.from_pandas(df, npartitions=1)

In [17]: df.describe()
/Users/taugspurger/.virtualenvs/dask-dev/bin/ipython:1: FutureWarning: Treating datetime data as categorical rather than numeric in `.describe` is deprecated and will be removed in a future version of pandas. Specify `datetime_is_numeric=True` to silence this warning and adopt the future behavior now.
  #!/Users/taugspurger/Envs/dask-dev/bin/python
Out[17]:
                          A
count                     2
unique                    2
top     2000-01-01 00:00:00
freq                      1
first   2000-01-01 00:00:00
last    2000-01-02 00:00:00

In [18]: ddf.describe()
/Users/taugspurger/sandbox/dask/dask/dataframe/core.py:2230: FutureWarning: Treating datetime data as categorical rather than numeric in `.describe` is deprecated and will be removed in a future version of pandas. Specify `datetime_is_numeric=True` to silence this warning and adopt the future behavior now.
  meta = data._meta_nonempty.describe()
/Users/taugspurger/sandbox/dask/dask/dataframe/core.py:2128: FutureWarning: Treating datetime data as categorical rather than numeric in `.describe` is deprecated and will be removed in a future version of pandas. Specify `datetime_is_numeric=True` to silence this warning and adopt the future behavior now.
  meta = self._meta_nonempty.describe(include=include, exclude=exclude)
Out[18]:
Dask DataFrame Structure:
                    A
npartitions=1
               object
                  ...
Dask Name: describe, 19 tasks

In [19]: _.compute()
Out[19]:
                          A
unique                    2
count                     2
top     2000-01-02 00:00:00
freq                      1
first   2000-01-01 00:00:00
last    2000-01-02 00:00:00

To silence this warning, we'll need to use datetime_is_numeric
In [21]: df.describe(datetime_is_numeric=True)
Out[21]:
                         A
count                    2
mean   2000-01-01 12:00:00
min    2000-01-01 00:00:00
25%    2000-01-01 06:00:00
50%    2000-01-01 12:00:00
75%    2000-01-01 18:00:00
max    2000-01-02 00:00:00

I don't know if we'll want to add that to our API or not.

cc @shwina who might care about these changes as well

NO. This is not a problem. I like this behavior
# Good ^_^
df_in_date_range.describe()

date
file

1808
1808

66
1806

2021-06-08 21:25:35
aiml_file_0101b.mp4

67
2

2021-06-07 13:24:53
NaN

2021-06-11 20:31:42
NaN

VS
# BAD >:(
df_in_date_range.describe(datetime_is_numeric=True)

date

1808

2021-06-09 14:11:13.823561984

2021-06-07 13:24:53

2021-06-08 11:19:54

2021-06-09 13:43:42

2021-06-10 16:41:39

2021-06-11 20:31:42

I lose the file column in Jupyter Notebooks
... It took me hours upon hours to figure out how to get read the files from disk and parse them correctly in pandas and now I'm dealing with this damn warning:
FutureWarning: Treating datetime data as categorical rather than numeric in .describeis deprecated and will be removed in a future version of pandas. Specifydatetime_is_numeric=True to silence this warning and adopt the future behavior now.
We should have the freedom to use datetime data as a categorical. Do NOT force us to convert it to a numeric!


A/B testing for fuzzing engines

Let's keep the work-in-progress design of A/B testing tool at docs/ab-testing.md and use this bug to track the progress.

This information is mostly irrelevant for the user, but would fit well in the design doc.

That sounds useful to me; regarding docker functionality, the next PR which is close to complete, there is currently a premade image on gcontainer registry (gcr) with built clang and all dependencies (essentially from tutorial/install-deps.sh).
From there, this repo will container a Dockerfile which pulls from gcr, sets some environment variables/directories (as compatible with dispatcher.sh), and runs 1 script.
As I work on the runners, it may seem better for them to have their own Dockerfile; the gcr image should still work for both.

I've switched our project to fuzzer-test-suite, due to an issue with the project ID of fuzz-comparison

For reference, engine-comparison is currently hard-wired with certain specifications which our group will always use, but a general user will want to specify. The list of all such variables is:

$GCLOUD_ZONE
$SERVICE_ACCOUNT
$IMAGE_FAMILY
$GSUTIL_BUCKET

These all rest in common-harness.sh

I've been working on report generation, and I'm approaching a solution which mostly involves CSV generation in Golang. I should say this task could potentially be done without Golang, and just much more javascript sophistication, but there is a lot of array computation to be done in arranging multiple raw datasets (raw being just two columns, time and a single data column) into a complete graph.
To begin with, raw CSVs are located in a nest of directories, in general benchmark-X/fengine-Y/trial-Z/data.csv. So, at each level, CSVs from the lower level will be aggregated into a single CSV, and then this CSV will be fit for display in a static HTML page which just reads a CSV from its own directory (and which could be identical across all reports).
Accordingly, the first step is putting CSVs for each trial-A through trial-Z into a single CSV for the directory benchmark/fengine. This is just an aggregation of smaller datasets to the larger one.
The next step is then putting CSVs for each fengine into a single CSV for the benchmark/ folder. The data taken for each fengine could be all of the data, or it could be just the maximum trial from within each fengine CSV, or similarly the median trial.
The CSVs in each benchmark/ directory would directly compare fengines, and this is the most important comparison. The CSVs for each benchmark/fengine could be used to view variance among trials and etc.


KYLIN-3552 add doc and blog

Can one of the admins verify this patch?

Thank you, as the feature is not released yet, so this PR will be held.


add union of two linked list

union of two sorted linked list . both list should not have duplicates

Merged 🍺


PHP Compatibility issues

When upgrading to the latest trunk version, I got the following error:
Kanboard\\Core\\Security\\random_bytes() in /app/Core/Security/Token.php on line 24

I'm not running PHP7, so that's probably the problem :)

Possible solution is to use
http://php.net/manual/en/function.openssl-random-pseudo-bytes.php
Instead of random_bytes

There is a polyfill for older PHP, don't forget to do a composer install if you are using directly the repo.

Ah ofcourse, thanks for that! Then this issue can be closed :+1:


Misalignemnts in results header / data

i was doing a request with more columns than what fit in the screen and sqlectron gives me a weird alignment of the column names with the data ...

I have realized it before too. It occurs sometimes :cry:


map.invalidateSize() changes map center

How to reproduce

Leaflet version I'm using: 1.0.1
Browser (with version) I'm using: Chrome  51.0.2704.63 (64-bit)
OS/Platform (with version) I'm using: Ubuntu 16.04

Step 1
Create html file with this content:
<!DOCTYPE html>

    <title>Leaflet</title>
    <link rel="stylesheet"<EMAIL_ADDRESS>/>

Step 2
In browser console run map.setView(map.getCenter())
What behaviour I'm expecting and which behaviour I'm seeing
I expecting that center is not changed, but it changed.
This depends on the window size. If not repeat resize the browser window.
Problems in file Map.js:1482.
Maybe we can compare new center with current in function setView like this
if (this._loaded) {
			var currentCenter = this.getCenter();
			var newCenter = L.latLng(center);
			if (newCenter.lat === currentCenter.lat
				&& newCenter.lng === currentCenter.lng
				&& zoom === this.getZoom()) {
				this.fire('movestart');
				this.fire('moveend');
				return this;
			}
		}

But in events will be wrong center.

Cannot reproduce in master with playground at http://playground-leaflet.rhcloud.com/rofi/edit?html,output
Might be related to #3194 / #3197

@IvanSanchez

This depends on the size of the window is not always repeated. It is necessary to change the window size.

OK, I see what you mean now. New playground at http://playground-leaflet.rhcloud.com/wewo/1/edit?html,output

@IvanSanchez, yea. Now it reproduce in your example.The shift is very small. 1-2 pixel. In my example can be seen better.


For working with ripple effect

Jonathan,
This pull request is FYI, mainly.  I wanted to use DlxLib to solve Ripple Effect puzzles - DlxLib can't quite handle that since I need what Knuth calls secondary columns in a generalized cover problem (pg. 17 of his paper).
I started to modify DlxLib ... and got carried away.  In addition to adding primary/secondary columns I pretty much changed the entire O-O structure of the data matrix itself, adding special Root and Row objects to the Column and Data objects.  Yet at the end of the day your demos work unchanged (demo 3 - the one that shows pentominoes fitting the 8x8 board incrementally as the search progresses is especially nice).
So ... this pull is for your entertainment/information.  Though if you have suggestions for me, I'd be happy to hear them.

Hi - I'm am unfamiliar with the whole pull request process so I'll have to do some reading to get up to speed. I'm in the middle of starting a new job and also doing an online course (Principles of Reactive Programming) so I'm a bit busy at the moment. But I'll get back to you when I can. Thanks for your patience.

No rush at all!  Like I said, for your entertainment/amusement mainly.
Good luck on your new job. -- David
On Sat, May 16, 2015 at 4:29 AM, Jonathan Taylor<EMAIL_ADDRESS>wrote:

Hi - I'm am unfamiliar with the whole pull request process so I'll have to
do some reading to get up to speed. I'm in the middle of starting a new job
and also doing an online course (Principles of Reactive Programming) so I'm
a bit busy at the moment. But I'll get back to you when I can. Thanks for
your patience.
—
Reply to this email directly or view it on GitHub
https://github.com/taylorjg/DlxLib/pull/2#issuecomment-102613169.

BTW, do you have a working example of a Ripple Effect puzzle solver?

Nope - it's in progress though!  A day or two should do it.
On Sat, May 16, 2015 at 11:00 AM, Jonathan Taylor<EMAIL_ADDRESS>wrote:

BTW, do you have a working example of a Ripple Effect puzzle solver?
—
Reply to this email directly or view it on GitHub
https://github.com/taylorjg/DlxLib/pull/2#issuecomment-102660034.

Cool - I'd be interested to see it.
Cheers,
Jon

Hi David,
I have decided not to merge in this pull request because of the large size/scope of the changes. However, I'd like to thank you for making me aware of secondary columns. I have now added support for them to DlxLib in version 1.3 which I released last night. I added some more Solve overloads with an additional parameter, numPrimaryColumns. I then made a small internal tweak and it seems to work fine.
FYI, I have created a couple more demo programs that make use of secondary columns:

https://github.com/taylorjg/TetraSticks
https://github.com/taylorjg/RippleEffectDlx

Regards,
Jon.

thanks! I'll look at them
On Thu, Oct 1, 2015 at 11:15 AM, Jonathan Taylor<EMAIL_ADDRESS>wrote:

Hi David,
I have decided not to merge in this pull request because of the large
size/scope of the changes. However, I'd like to thank you for making me
aware of secondary columns. I have now added support for them to DlxLib in
version 1.3 which I released last night. I added some more Solve
overloads with an additional parameter, numPrimaryColumns. I then made
a small internal tweak and it seems to work fine.
FYI, I have created a couple more demo programs that make use of secondary
columns:

https://github.com/taylorjg/TetraSticks
https://github.com/taylorjg/RippleEffectDlx

Regards,
Jon.
—
Reply to this email directly or view it on GitHub
https://github.com/taylorjg/DlxLib/pull/2#issuecomment-144805218.


config dir

it's useful to have example config files but they clutter the topdir a little. @Jean-Baptiste-Camps should we move into a toplevel dir of their own?

We could cerrtainly have a config_examples dir, or something equivalent. Another question is: should we exclude (most of) them from the git repository ? For now, I have stopped to commit my various configurations (Chrestien, Montferrand, etc.), not to drown the repository in them. What do you think ?

I think we should gitignore *.txt file at root and have a config_example directory.
Alternatively, we also need to spawn git repository that demonstrate examples with config, built model as attached binary to release, and finally source data

Fixed by #66


Add new Rails/IndexNames cop

This cop enforces the standard index naming provided by Rails, allowing developers to enjoy a standardized schema.
A bonus impact of following this convention is that fully duplicated indexes are prevented by default.
Custom index names were once a required workaround for default names that were too long for various database implementations. That could happen because of long table names, long field names, or long lists of compound index keys.
However, that problem has been fully resolved. The current automated naming approach will deterministically abbreviate indexes that would have been too long before.
Background:

Article: https://www.shakacode.com/blog/rails-7-1-limits-max-length-of-auto-generated-index-names/
Feature PR: https://github.com/rails/rails/pull/47753

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[ ] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

Hi, thanks for the PR! I don't think I've ever bothered with manually naming my indicies but can you just generalise this?
Generally, I would say let users name their indicies as they wish. Indicies don't have to be only over a column, they can have query constraints, modify the column, use different index strategies (gin, gist, etc.). Per the PR you linked, it doesn't look like rails will respect any of these options in the index name.

I have some general feedback for your PR. I would wait until more feedback until adressing this:

This cop should not run over the whole codebase. Limit it only to migrations, same as ThreeStateBooleanColumn and similar cops.
If only in Rails 7.1 the index is safe to create, this should not run over migrations generated with older rails.
It might be a good idea to add config StartAfter. It's a bit awkward right now, there are a few PRs wanting to do this but none have been merged so there is no common module yet. https://github.com/rubocop/rubocop-rails/pull/335 https://github.com/rubocop/rubocop-rails/pull/277 https://github.com/rubocop/rubocop-rails/pull/335
You can also add indicies with add_index, these should be an offense as well.
adoc is automatically generated. Please drop these changes.

Thanks for the great comments @Earlopain with pointers as well!
All addressed, and I added specs to confirm no offenses both for earlier Rails versions and earlier Migrations versions.

That was quick, cool. One additional thing I forgot about: autocorrect will be unsafe since it changes index names which may be referenced later. (also remove_index).
In particular I'm aware of this pattern that good_job does, where it first checks if a index exists before creating it. I'm not entirely sure why, seems to only matter when a migraiton is run more than once in the same direction, but it's pobably valid in some way: https://github.com/bensheldon/good_job/blob/956e872d321df21738c599aa1a86a8514e05a7ef/demo/db/migrate/20240518175058_create_good_job_process_lock_indexes.rb
I'd also see this as one counter-argument for introducing such a cop. I would be pretty uncomfortable referecing the auto-generated index name without being explicit about it somewhere.

Okay, @Earlopain, much to my surprise it does seem rather possible to generalize and accommodate valid reasons for a custom name that could lead to duplication of indexes with the same column names but different handling or properties (e.g. fulltext  as another example where you may want both a fulltext and non fulltext index on the same columns).
I've added an allowlist, and enumerated in a comment the current keys that I think don't justify a custom name as well, for scrutiny.
Comments and improvements welcome!


Any plan for ios & android

Hi Croydon,
Thanks for the Great job! I've tried grpc on Macos and it can work well.
However, I see the mobile related code is commented out currently as below, so I'd like to ask if there's any plan to get the cross-comiple done?
# This doesn't work yet as one would expect, because the install target builds everything         # and we need the install target because of the generated CMake files         #         #   enable_mobile=False # Enables iOS and Android support

We would also love to see this happen. What would that entail?


FIX: WM mask selection from dseg before generating report

Following suit of poldracklab/fmriprep#2084 and inline with nipreps/niworkflows#500, this PR uses a more robust version of the extraction code.
Resolves: #99
Depends: nipreps/niworkflows#500

Does this have any impact on derivatives?

Nope, only on the reports. But we may want to downstream it to 1.1.x

sdcflows 1.1.x? I don't think anything depends on it.

fair enough - why bother 👍


If any MQTT publish message fails with the  Error -27648 while sending data,  it continuously fails, recovers only on reboot

Hi Team,
I am using AWS FreeRTOS version 202007 and ESP32.
ESP32 is connected to the corporate network Wi-Fi. Very High speed network. No chance of unstable network.
Also ESP does not loose wifi connectivity at all. wifi is very stable.
If any MQTT publish message fails with the following error, it will not recover and it continuously fails, recovers only on reboot.
[iot_thread] [ERROR][NET][117930] Error -27648 while sending data.
This occurs very randomly.
In my opinion this error is observed happening generally when two close publish or one publish and one subscribe happens almost together or close or back to back.
Can we do publish from multiple threads with out worrying about thread safety? I strongly suspect thread safety here.
How can we use this SDK or how can we trust this SDK, if this error keeps coming now and then and creates instability in the system.
Please let me know the fix for this as soon as possible.
Again this is the same issue from 2 years.
There is single MQTT connection for all the three threads, there is unique  client ID.
Thanks,
Kumar.

Hi Team,
Can you please help me on this as soon as possible. This is an issue faced in the site. This needs to be fixed immediately.
I am clueless with this.
I need your immediate assistance in this.
Thanks
Kumar.

Hello @kumarfirmware ,
If you are using coreMQTT APIs from multiple threads and sharing connection then thread safety must be handled in the application.
Alternatively you can use the coreMQTT Agent library that adds thread safety to the coreMQTT library. Please refer https://freertos.org/mqtt-agent/index.html

Hi  Pvyawaha,
Thanks for the message. I am using AWS FreeRTOS version 202007 and ESP32. There is no coreMQTT and coreMQTT Agent library in this version.
Please let me know how to proceed in detail. please give me clear detailed information with respect to version 202007.
Thanks
Kumar.

Hi @kumarfirmware,
From your logs, it looks like the publish completes successfully, and then on line 54 the timestamp jumps from 1659 to 4628, where it fails to send a PINGREQ packet as part of the keep alive job. Is the connection intended to be left inactive long enough for the keep alive job to kick in?
Also, there have been issues in the past with this version of the MQTT library where the network receive task fails and the application isn't notified until the keep alive job fails, resulting in similar log messages to what you are seeing. Can you enable debug logs to try to narrow down where the issue occurs between the send of the PUBLISH and the keep alive attempt?
Additionally, as the MQTT library that was part of 202007 was removed, we recommend that you upgrade to the latest release if you are able.

Hi Muneeb,
Thanks for the message. I do not close the MQTT connection and there is no need to close the MQTT connection.  MQTT PING is a continuous process, it will go on.
The worry is sometimes this Error -27648 does not go off hours together even after reboot, it continuously keep giving this Error -27648.
I am using AWS FreeRTOS version 202007 and ESP32. As you know it takes long time to move to AWS FreeRTOS version 202107.
Meanwhile production sites are struggling with this issue with AWS FreeRTOS version 202007.
How do I replace MQTT library seamlessly in the AWS FreeRTOS version 202007?
Please help me with this immediately with detailed steps.
Any immediate help in this is highly appreciated.
Thanks, Regards,
Kumar.

Hi @kumarfirmware,
Can you enable debug logging? As I mentioned earlier, it's possible the connection goes down even before the ping request attempt is made, and more logs could help narrow down when the error occurs.
If you aren't able to upgrade to the latest release due to the MQTT API changing, are you able to use the MQTT library from previous tags, like 202012.00 or 20210526_Archive, which was the last tag before the old MQTT API was removed? I ask since both of those tags contain the coreMQTT library, and also have a compatibility layer to interface with the old MQTT API that you are using in 202007.00. I think using coreMQTT along with the compatibility layer might help you since you would still be able to use the same API you currently are.

The MQTT library in 202007 and 202012 is not the same. 202012 uses coreMQTT, but only contains a compatibility layer to be able to use the APIs in 202007. Internally, it will still use coreMQTT, so you will need to include the coreMQTT library as well. If 202012 works for you, then I would recommend next using 20210526_Archive, since it contains bug fixes for memory leaks that were in 202012.
That tag would have had testing for demo builds and runs when each commit was merged, but it does not have extensive testing for every build combination as our release tags do.

Hi Muneeb,
Thanks for the message. I started using 20210526_Archive. Everything looks good, until now.
But I guess shadows are handled a bit differently here in this version compared to 202007, so I need to adopt my code here.
So I assume I should do device shadows also using normal MQTT Publish and subscribe to match the compatibility for MQTT API used in AWS V202007.
So I cannot use the shadow library here right?
Please confirm this as soon as possible, so that it will help me to move forward.
Thanks, Regards,
Kumar.

Hi,
I'm not sure why you wouldn't be able to use the Shadow library in that version. Looking at the commit history, there weren't that many changes to the old shadow files in that tag. Since that version of the shadow library used the old MQTT APIs, it will just be using the MQTT compatibility layer instead, so the APIs would be the same. Of course, the recommendation is to use the latest Device Shadow library but the old API is still present in the 20210526 tag.
I'm not sure what you mean by master/release for 20210526_Archive. 20210526_Archive is a git tag that points to the same commit that the main branch pointed to on 2021-05-26. The current main and release branches point to newer commits that do not have the MQTT compatibility layer.
Release branches are tested the most. Our recommendation is still to use the latest release version 202107.00, but if that is not possible then you can use 202012 or 20210526_Archive. It's up to you whether you are willing to use 20210526_Archive in production; if you only want to use release tags, then you should know that 20210526 contains bug fixes for memory leaks that were present in 202012, so you should copy over the changes that were made to the MQTT compatibility layer

Hi Muneeb,
Thanks for the message. Thanks for the clarification.
I am getting the following error when I am using old shadows in 20210526_Archive.
../vendors/espressif/boards/esp32/aws_demos/application_code/comms.c:40:10: fatal error: aws_iot_shadow.h: No such file or directory
#include "aws_iot_shadow.h"
     ^~~~~~~~~~~~~~~~~~

compilation terminated.
Can you please help me with this as soon as possible.
Thanks, Regards,
Kumar.

Hi Muneeb,
Can you please help me with the above error as soon as possible.
I guess shadow library is not building and I am not able to use it in my application code.
Thanks, Regards,
Kumar.

Hi Muneeb,
Can you please help me with the above error as soon as possible.
Thanks, Regards,
Kumar.

From the error, it looks like you need to include this file. You should add the directory that file is in to your include path before compiling.

Hi Muneeb,
In 202007 it works automatically. I am not sure how to add this to the make file in 20210526_Archive.
Can you please help me with this?
Thanks, Regards,
Kumar.

What build system/compiler are you using? For gcc compilers, you can add include paths by using the -I option

Hi Muneeb,
I am using gcc compiler.
See in the build folder under CMakeFiles I see the following files. Here it clearly shows shadow library is not compiled at all.
I am not using anything on my own. I am just using the existing make files.

Thanks, Regards,
Kumar.
Thanks, Regards,
Kumar.

If you are using that version of shadow and cmake, then you should add a dependency on AFR::shadow in your CMakeLists.txt. For example, this demo has a dependency on AFR::device_shadow since it uses the latest Shadow library. You would use AFR::shadow since you are using the older one.

Hi Muneeb,
I tried this, but still it is not solving the issue.
We should some how call this AFR::shadow in CMakeLists.txt in vendors\espressif\boards\esp32 , because we are using shadows in this folder vendors\espressif\boards\esp32\aws_demos\application_code.
If you can crack this some how it will really help. I guess we are very close.
Thanks, Regards,
Kumar.

Hi Muneeb,
Can you please help me with the above error as soon as possible.
Thanks, Regards,
Kumar.

Hi Muneeb,
I am able to build this successfully now.
I will test and see if I can reproduce the [iot_thread] [ERROR][NET][117930] Error -27648 while sending data.
I will let you know how the test goes.
Thanks,
Kumar.

Namaste @kumarfirmware,

[iot_thread] [ERROR][NET][117930] Error -27648 while sending data.

One of the many possible reasons for the above error is the possibility of the duplication of clientcredentialIOT_THING_NAME on multiple devices/ clients.
We had encountered this error wherein two clients - one being our ESP32 device and, the other being a client node running a Python script, were both using the same device identifier. As a consequence, whenever the Python script published a MQTT Topic, the ESP32 device would start showing the Error -27648 while sending data. on the console. This happens, even if the published MQTT topic is not subscribed by the ESP32 device.
Reason for such behavior: According to the MQTT spec, multiple connections to the same endpoint must have unique client IDs, otherwise it's likely that the first connection will suddenly be dropped by the server, without notification, after the second connection has been made.
Requesting you to go through this https://github.com/aws/amazon-freertos/issues/2916#issuecomment-761175166, which is part of the AFR & ESP32: NETWORK ERROR encountered, for aperiodic MQTT Publish operation issue, I had raised.
Additionally please note, the FreeRTOS version we are using for development is V202002.00, which is older than yours.
Hope this helps!
Thanks | Regards,
Dipen

Hi Dipen,
Thanks for the message.
I am pretty sure I am using unique clientcredentialIOT_THING_NAME.
I am not doing any multiple MQTT connections with same clientcredentialIOT_THING_NAME.
I am still facing the issue [iot_thread] [ERROR][NET][117930] Error -27648 while sending data. some times.
Thanks,
Kumar.

Hi Muneeb,
As you know I am using AWS 20210526_Archive, as this has a compatibility layer for MQTT API used in AWS V202007.
I do not see any problem with the publish.  But I have a problem with the subscribe.
Whenever the cloud is sending a message to ESP32, I am getting the following error.
Length of the message from the cloud is around 5,600 bytes.
Please help me with the following error as soon as possible.

Thanks,
Kumar.

Hi @kumarfirmware,
We apologize for taking this long to get back to you. The compatibility layer is thread safe. You can use it to publish from multiple tasks including OTA simultaneously.
Thanks

Hi @kumarfirmware,
Looking at some of your logs,
384 388558 [normal_operatio] TLS_Connect fail (0x7d3, NULL)
385 388558 [normal_operatio] [ERROR][NET][3885580] Failed to establish new connection. Socket status: -1.
386 388559 [normal_operatio] [ERROR][MQTT][3885590] Failed to establish new MQTT connection, error NETWORK ERROR.
387 388559 [normal_operatio] [ERROR][DEMO][3885590] MQTT CONNECT returned error NETWORK ERROR.
Start establishing MQTT connection
388 389569 [normal_operatio] [INFO ][MQTT][3895690] MQTT library successfully initialized.
abort() was called at PC 0x4016b883 on core 0

Some comments:

You should not attempt a new MQTT connection if the TLS connection fails
You should not call IotMqtt_Init() a second time without calling IotMqtt_Cleanup()

It looks like you are not yet able to reconnect. You should keep retrying the TLS connection before proceeding further with the MQTT connection.

Hello @kumarfirmware ,
Closing this issue now, please reopen if you have more questions on the same topic or create a new one for other topics.


Add --output option to dapr list

Note: marked as a draft until the corresponding change is committed to the Dapr CLI and I've sorted out which docs branch this should target.

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[x] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Adds documentation for the new --output option of the dapr list command.
Issue reference
dapr/cli#728

Change base to 1.3


feature: --force CLI flag for meltano add

Feature scope
CLI (options, error messages, logging, etc.)
Description
We currently support the --force CLI flag for meltano install. Since meltano add installs by default, it should also support this flag.

Still relevant.

@WillDaSilva Can I work on this?

@XshubhamX We'd gladly accept a contribution of this feature. I've assigned it to you. Feel free to reach out to us in the Meltano Slack if you run into any difficulties. Once your changes are working, tested, and documented, please open a PR, and we'll review it promptly.


HBASE-24371 Add more details when print CompactionConfiguration info

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 30s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 33s
the patch passed

+1 :green_heart:
compile
1m 10s
the patch passed

+1 :green_heart:
javac
1m 10s
the patch passed

+1 :green_heart:
shadedjars
6m 41s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 43s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
10m 54s
hbase-server in the patch failed.

39m  0s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 5ee5eba86e80 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 5e32e08782

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/1/testReport/

Max. process+thread count
606 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 29s
the patch passed

+1 :green_heart:
compile
1m  8s
the patch passed

+1 :green_heart:
javac
1m  8s
the patch passed

+1 :green_heart:
shadedjars
6m 20s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 41s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
9m 34s
hbase-server in the patch failed.

37m 44s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0aee925fdd69 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 5e32e08782

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/2/testReport/

Max. process+thread count
616 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 33s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 55s
the patch passed

+1 :green_heart:
compile
1m 20s
the patch passed

+1 :green_heart:
javac
1m 20s
the patch passed

+1 :green_heart:
shadedjars
7m 19s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
1m  0s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 29s
the patch passed

+1 :green_heart:
compile
1m  8s
the patch passed

+1 :green_heart:
javac
1m  8s
the patch passed

+1 :green_heart:
shadedjars
6m 16s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
180m 15s
hbase-server in the patch passed.

207m 33s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4b5ec385ed46 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 852150a23f

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/5/testReport/

Max. process+thread count
3441 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1711/5/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@anoopsjohn  any more comments?


error parse

{"Code":1,"Message":"用户登录成功","Data":{"Token":"146A307B82184AB5A00918CF9B612160","User":{"UserId":"3cd1cd06-3d77-4efb-a78d-ad9a9cea3d80","RealName":"admin","Department":"测试1"},"Settings":null},"PageIndex":null,"PageSize":null,"TotalCount":null,"TotalPageCount":null}
this json str can't parse through

with gbk, chinese

json throw   JSON_THROW(static_cast<const detail::out_of_range>(&ex));

The JSON above is indeed valid and the following program works:
#include "json.hpp"
#include <iostream>

using json = nlohmann::json;

int main() {
    json j = R"({"Code":1,"Message":"用户登录成功","Data":{"Token":"146A307B82184AB5A00918CF9B612160","User":{"UserId":"3cd1cd06-3d77-4efb-a78d-ad9a9cea3d80","RealName":"admin","Department":"测试1"},"Settings":null},"PageIndex":null,"PageSize":null,"TotalCount":null,"TotalPageCount":null})"_json;

    std::cout << j.dump(2) << std::endl;
}

The library does only support UTF-8 though. Other encodings are not supported. The error may come from a misinterpretation of GBK.

thank, but in my point, the gbk and utf8 or other codepage, the ascii part is same, the process of interpretation should not mistake.  just like tinyxml2, it work well with gbk or utf8.

But your value does not only contain ASCII values. For this library, it makes a difference whether 用户登录成功 is encoded as UTF-8 or GBK.

00-7F  0xxx xxxx  //ascii and gbk, utf8 same
07-FF 110x xxxx 10xx xxxx
...
what i want voice is that, if any char first bit is 1, you shoud process it as text, and do need to interpretate it, what we  interest is the char  and need to interpretate is the char value below 128(unsinged)

if a str is  abc , so it is  0xxx xxxx, 0xxx xxxx, 0xxx xxxx
if b str is a中c, so it is 0xxx xxxx, 1xxx xxxx, 1xxx, xxxx, 0xxx xxxx, whether in gbk or utf8

Could you please attach the above JSON as file, so I can check myself?

ok, wait half hours

git@github.com:ChinaCCF/TestJSON.git

the file commit here, and i recheck again, the same error

Thanks! Here is the error message I get:
libc++abi.dylib: terminating with uncaught exception of type nlohmann::detail::parse_error: [json.exception.parse_error.101] parse error at line 1, column 23: syntax error while parsing value - invalid string: ill-formed UTF-8 byte; last read: '"\323\303'

And indeed, the string 用户登录成功 begins at column 28. The parser complains about the byte sequence 0323 0303 (octal) which is 0xD3 0xC3 (hex). In UTF-8, D3 indicates the start of a 2-byte sequence. The next byte must be in the range 0x80..0xBF. Therefore, 0xC3 is unexpected here.
This library does not support any other encoding but UTF-8. The encoding of 用户登录成功 in GBK is invalid UTF-8, so it is rejected by the library.

i like your lib very much, it's Intuitive , and simple. but if it do not support gbk, i feel sad,  and use rapidjson(china tencent) insead of nlohmann. i think in the world (in win32) , there are many other program run in code page that is not utf8.

Sorry to hear that.


Proposal: Add fst and snd functions to access a tuple pair

I find myself using JS array with a length of 2 as if they were a tuple pair. For example, R.zip returns a list of pairs. But when working with pairs, fst and snd functions would be nice. The fst function can be emulated with R.head, but there's no snd function. There's also no way to emulate the !! operator from Haskell without writing your own function afaik?
I'd like to get rid of this kind of code:
R.map(function(v) { return v[1]; }, data)

Example usecase:
var combined = R.zip(list1, list2);
R.map(R.compose(R.toUpper, R.snd), combined);

I realize that if it were more complex than this, I would be better of using Lenses, but for usecases as simple as this, I think a new alias for the head function is easily created, and a snd function with the following definition is also easily created:
var fst = R.head;
var snd = R.curry(function(pair) {
  return pair[1];
});

As a small optimisation with might choose to throw an error when the array that represents the pair has a length which is not 2.
Thoughts?

could be:
var fst = R.nth(0);
var snd = R.nth(1);
// or this: R.map(function(v) { return v[1]; }, data) becomes simply:
R.map(R.nth(1), data)

Cool, thats quite simple. I didn't see the R.nth function yet, obviously ;)
I'd still love the addition of fst and snd functions tho, what do you think?

yeah, nth doesn't get the respect it deserves, it is very handy!

I'd still love the addition of fst and snd functions tho, what do you think?

fst may be a tough sell, since it essentially an alias for head and we have, at present, no aliases. and without fst, snd would be an oddball. Plus, it's easy enough to whip these up using nth.
I'm curious where other stand, though.

Ok, makes sense.
How much thought has gone into working with pairs (as in Haskell pairs, 2-length tuples) in Ramda? Are there other specific functions that make this more easy? Are you working with pairs personally? And does it make sense in JS at all? Or might a specific Pair functor make more sense?
The selling argument could be that Ramda would then enable working with pairs, whereas now it doesn't.

Plus, it's easy enough to whip these up using nth.

Well, if you want to do it the right way, I think fst and snd should throw an error when the given array doesn't have a length of 2, and thus isn't a valid pair. And that makes it a little less easy than just var snd = R.nth(1);

Or might a specific Pair functor make more sense?

interesting for sure, but maybe more in the scope of ramda-fantasy or sanctuary. A generic n-tuple might be even better, but maybe tough to do with JS loose typing. By which I mean it would be tough/costly to enforce that a given tuple, e.g. (String, Object, Number) is always typed that way.

But you know, if we can make these efficient enough, we can reimpement everything in terms of pair-based lists, and [scare the heck][co] out of some folks.  :smiling_imp:

In case it wasn't clear, this is a joke!
[co]: https://github.com/ramda/ramda/issues/1002#issuecomment-89425812

Well, since you asked @branneman, I think it'd be cool to see this in ramda-fantasy as a staple type with implementations of all the usual interfaces.
The functor/monoid/apply instances differ from Array which is, in my opinion, the raison d'etre, but there are other good uses.
One can define a nice Bifunctor which does what you might expect.
var neat = compose(map(reverse), bimap(replace('o', '')), split("-"))
neat("hello-world")
//=> Tuple("hell", "dlrw")

There's the whole Reader/Writer Monad/Comonad symmetry: http://stackoverflow.com/questions/11245183/importance-of-isomorphic-functions/11247408#11247408
There's some interesting laws and properties to be exploited with tuples used as categorical products and in the pair calculus.
One cool thing I've seen is this:
 var _Tuple = function(x, y) {
    this[0] = x;
    this[1] = y;
    this.length = 2;
  }

Which keeps it working with nth() and head()

would love to see a PR on ramda-fantasy

I'm gonna close this here, but I would like to continue this conversation on ramda-fantasy.
And it would be nice to have cons, car, cdr for working with Pair too ....

Cool, agreed! Let's make a new issue at ramda-fantasy then, with a reference to this issue/discussion.

:+1:


Android client stuck on Waiting on initial GNSS fix...

Android client stuck on Waiting on initial GNSS fix...
Android 9.0
MIUI Global <IP_ADDRESS>(PEDMIXM)
Model: MI MAX 3

This means that location services on your phone can't get a GPS fix. This can happen for various reasons, but is most common indoors. Can you check that you are in an area with good GPS reception? You can check if you get a GPS fix with e.g. GPS Test from Play Store. If your phone has a setting for location accuracy, try setting it to "High accuracy" instead of "Battery saving".

True, I just wander how uber, maps works so fast ?

I currently only use Android's "fine" location provider. That means it will try to rely on GPS only. However, there is also a "coarse" location provider that gets the location from the network instead. I can see if I can implement this as a fallback while the device is waiting for a more accurate GPS fix.

That would be significant improvement. Can you please consider this as feature request please?

I will actually consider it a bug, since when I made this feature, I thought just using "fine" was enough. If I understand the docs correctly, "coarse" is able to provide an immediate, albeit less accurate, location. So this was a mistake on my part; I really should be using both. :-)

Another suggestion for checking your own GPS-Status: SatStat - its open source and available on f-droid as well.

I implemented a fix for this in v1.1.1. It may take a couple of days for that version to be available on F-Droid. Hopefully, this fixes the issue for you. If it doesn't work for some reason, please reopen this issue and post any new behavior.


IndexError in multi-column groupby + sum

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 19.04
Modin version (modin.__version__): '0.7.3+52.g880545b'
Python version: Python 3.7.3
Code we can use to reproduce:

Describe the problem
Get IndexError when try multi-column groupby with pandas-on-ray engine
IndexError:  positional indexers are out-of-bounds

Source code / logs

import modin.pandas as mpd
df = mpd.DataFrame(
[[1, 11, 101], [1, 21, 201], [2, 12, 102], [2, 22, 202], [2, 32, 302]],
columns=list("abc"),
)
print(df.groupby(["a", "b"]).sum())

Closing this. Just tested this code, it has been fixed. Please re-open if this is still an issue.


write to transaction json

Fix for https://github.com/samelamin/spark-bigquery/issues/12

Tested on my side. Thank you.

@lnicalo you are most welcome! I really would appreciate it if you can rate the package when you get a chance

@lnicalo you are most welcome! I really would appreciate it if you can rate the package when you get a chance


Zipking readiness probe 503

Describe the Bug
The pod don't start beacuse readines probe with error 503. I have configured elasticsearch env variables to connect to a elastic 8.2 cluster. The log ends with
2022-05-23 10:12:49.392  INFO 1 --- [           main] c.l.a.c.Flags                            : Using OpenSSL: BoringSSL, 0x1010007f
2022-05-23 10:12:50.678  INFO 1 --- [           main] c.l.a.s.d.DocStringExtractor             : Using com.linecorp.armeria.thrift.jsonDir: META-INF/armeria/thrift
2022-05-23 10:12:50.720  INFO 1 --- [           main] c.l.a.c.u.SystemInfo                     : Hostname: zipkin-server-75d9b5b4f8-mshps (from /proc/sys/kernel/hostname)
2022-05-23 10:12:51.133  INFO 1 --- [oss-http-*:9411] c.l.a.s.Server                           : Serving HTTP at /<IP_ADDRESS>:9411 - http://<IP_ADDRESS>:9411/
2022-05-23 10:12:51.138  INFO 1 --- [           main] c.l.a.s.ArmeriaAutoConfiguration         : Armeria server started at ports: {/<IP_ADDRESS>:9411=ServerPort(/<IP_ADDRESS>:9411, [http])}
2022-05-23 10:12:51.210  INFO 1 --- [           main] z.s.ZipkinServer                         : Started ZipkinServer in 6.383 seconds (JVM running for 8.539)
2022-05-23 10:16:09.208  INFO 1 --- [orker-epoll-2-1] c.l.a.i.JavaVersionSpecific              : Using the APIs optimized for: Java 9+

So I guess it starts correct but I can't see more errors to fix the problem.
I use this image version:
openzipkin/zipkin:2.17.1

is this a problem with the helm chart? zipkin's docker healthcheck works or we would get broken CI.

At some point we had an issue like this because zipkin was accepting https but the health endpoint is hard coded to do http. I can't find the issue tho, maybe it was an gitter.


Add reboot homey instruction to manual

Installed Pushover and followed instructions, but only on forum I found that I need to reboot the Homey to get it work.
Please add the reboot instruction to the instructions on the page of apps.athom.com and on the first forum page.

I don’t see why you would need to reboot Homey to make the app work.
If you needed to do this, I suspect that it was environment specific.


ontology updates post-3.1.0

ced320a1-29f3-47c1-a735-513c7084d508, self_reported_ethnicity - update Indian [HANCESTRO:0487] to Singaporean Indian [HANCESTRO:0598] & update Malaysian [HANCESTRO:0496] to Singaporean Malay [HANCESTRO:0597]
661a402a-2a5a-4c71-9b05-b346c57bc451 donor_id:GSM4643738 - update to 5 day [MmusDv:0000115]
48d354f5-a5ca-4f35-a3bb-fa3687502252 var_time:P7 - update to 7 day [MmusDv:0000117]
d86517f0-fa7e-4266-b82e-a521350d6d36 Dataset:RomanovDev10x - update to 23 day [MmusDv:0000144]

Private Collection: Human Neck Adipose Tissue
Dataset: adipose from neck - all nuclei
donor_id:CREEK003 should be self_reported_ethnicity:HANCESTRO:0005,HANCESTRO:0013 (currently 'multiethnic')

Collection: 1ca90a2d-2943-483d-b678-b809bf464c30
All Datasets
donor_id:H20.33.018 should be self_reported_ethnicity: HANCESTRO:0013,HANCESTRO:0014
donor_id:H20.33.034 should be self_reported_ethnicity: HANCESTRO:0005
donor_id:H21.33.037 should be self_reported_ethnicity: HANCESTRO:0005
All are currently 'admixed ancestry'/'multiethnic'  (the latter two checked 'Other' in addition to 'White' but didn't offer further information)

Collection: 6f6d381a-7701-4781-935c-db10d30de293
Dataset: 9f222629-9e39-47d0-b83f-e08d610c7479
donor_id: homosapiens_None_2023_None_sikkemalisa_002_d10_1101_2022_03_10_4837472020-3173-NC004 should be self_reported_ethnicity: HANCESTRO:0005,HANCESTRO:0008
donor_id: homosapiens_None_2023_None_sikkemalisa_002_d10_1101_2022_03_10_483747290B should be self_reported_ethnicity: unknown (submitter has "mixed" and "south american")
donor_id: homosapiens_None_2023_None_sikkemalisa_002_d10_1101_2022_03_10_483747NP19 should be self_reported_ethnicity: unknown (submitter only has "mixed" with no further information)
Collection: 6f6d381a-7701-4781-935c-db10d30de293
Dataset: 066943a2-fdac-4b29-b348-40cede398e4e
donor_id: homosapiens_None_2023_None_sikkemalisa_001_d10_1101_2022_03_10_4837472020-3173-NC004 should be self_reported_ethnicity: HANCESTRO:0005,HANCESTRO:0008
donor_id: homosapiens_None_2023_None_sikkemalisa_001_d10_1101_2022_03_10_483747290B should be self_reported_ethnicity: unknown (submitter has "mixed" and "south american")

Collection: 7d7cabfd-1d1f-40af-96b7-26a0825a306d
Only 1 Dataset
donor_id in ['Rep_C_1012','Rep_C_1017','Rep_C_1033','Rep_C_1036','Rep_C_1037','Rep_C_1039','Rep_C_1050','Rep_C_1053','Rep_C_1055','Rep_C_1059','Rep_C_1060','Rep_C_1064','Rep_C_1076','Rep_C_1078','Rep_C_1094','Rep_C_1095','Rep_C_1107','Rep_C_1143','Rep_C_1151','Rep_C_1154','Rep_C_1161'] should be self_reported_ethnicity: HANCESTRO:0014 (submitter has "Other/Multiple Races" & "Hispanic/Latino")
donor_id in ['Rep_C_1002','Rep_C_1003','Rep_C_1021','Rep_C_1051','Rep_C_1066','Rep_C_1072'] should be self_reported_ethnicity: unknown (submitter has "Other/Multiple Races" & "Non Hispanic/Latino")

Collection: 4d74781b-8186-4c9a-b659-ff4dc4601d91
Dataset: b07fb54c-d7ad-4995-8bb0-8f3d8611cabe
cell_type_ontology_term_id: CL:0000234 (phagocyte) should be CL:0000113 (mononuclear phagocyte)

Private Collection: Neuron type-specific effects of human aging and sex on DNA methylation and transcription
Dataset: all (only one dataset)
author_cell_type: L4-5IT_RORB_TSHZ2 should be CL:4030062 (L4/5 intratelencephalic projecting glutamatergic neuron)
author_cell_type: L2-4IT_CUX2 should be CL:4030059 (L2/3 intratelencephalic projecting glutamatergic neuron)
author_cell_type: L4-5IT_RORB_LRRK1 should be CL:4030062 (L4/5 intratelencephalic projecting glutamatergic neuron)
author_cell_type: L4-5IT_RORB_ARHGAP15 should be CL:4030062 (L4/5 intratelencephalic projecting glutamatergic neuron)
author_cell_type: L6IT_THEMIS_LINC00343 should be CL:4030065 (L6 intratelencephalic projecting glutamatergic neuron)
author_cell_type: L6IT_THEMIS_CUX1 should be CL:4030065 (L6 intratelencephalic projecting glutamatergic neuron)
author_cell_type: L3-5IT_RORB_PLCH1 should be CL:4030061 (L3 intratelencephalic projecting glutamatergic neuron)

@jahilton - clarifying - were these addressed after the 3.1.0 migration? If so, can this be closed?

No, these are for the next migration (post-3.1.0 means whatever schema version is after 3.1.0, which we now know will be 4.0.0). I'll update the title

Migration is complete.
The updates that weren't made due because the terms weren't in the schema 4.0.0 ontologies have been migrated to the next ontology update issue #710
@Jchaffer787 your comment came after the migration had been set. FYI - CL:4033053 is accepted by current schema, but CL:4030066 is not. If you make the CL:4033053 revision, please update the comment in the new issue


Fix ReferenceError in Web NFC example

Currently, if there's an error while scanning for NFC, it triggers error handler which has no error argument. But inside error handler, error.message is accessed, which triggers ReferenceError (no message property on undefined).

@googlebot I signed it!


Move generate and push client logic to openapi workflow

Before, we had an openapi/workflow that triggered a digitalocean-python-client/workflow to 1) generate the clients 2) run the mocked tests. With this change, it will look more like this:

When a PR is created in openapi spec files it will run pydo's mocked tests.
When the openapi PR is pushed to main, it will generate the client and create PR for pydo repo.

This had to be done because the github action we were using could not trigger other workflows using GITHUB_TOKEN which was causing PR checks to choke on the digitalocena-python-client side:
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#triggering-further-workflow-runs

o.O These checks shouldn't even run because the changes aren't in specifications/

I've noticed workflows aren't honoring any paths of paths-ignore values lately.


batch insert

When I batch insert 10 million data into stand-alone clickhouse, The time spent avg 16min,why so slowly? @alexey-milovidov

How exactly (in what format, to what kind of table) do you insert your data?
By the way, when using Values format, there is slow path, when data contains expressions (example: now() for DateTime field) or requires type conversion (example: '123' in quotes for integer field). So, you should specify data in explicit form.

create table（id Int64,name String,open_time Date）MergeTree('open_time', ('id','name'))
when I use python client insert list to DB （for example: db.insert([p1,p2,p3...])）

Maybe it is an issue of Python client. Python clients are unofficial, we have not evaluated them.
By the way, there are few different Python clients.
Is problem persists, when you insert data with clickhouse-client from command line, as in tutorial?

I think so, the Python client lib is https://github.com/Infinidat/infi.clickhouse_orm  ,so when I change to use  clickhouse-client ,its so quickly! Thank for your answer.

Ok. I suggest you to create an issue in infi.clickhouse_orm repository.

Hi, infi.clickhouse_orm v0.7.1 includes several performance improvements that reduce the time it takes to insert large amounts of data. @fengyuncrawl - I would appreciate it if you could try it and report back whether it's working faster than before.


Correct sourcemap URLs if necessary

In each source file, we check for a sourcemap URL directive. If we find one, we replace its URL with the sourcemap's full path relative to the domain root (i.e. the new URL will start with /). If the original sourcemap URL is a data URI or begins with / already, we don't touch it.
This PR also adds sourcemap correction to the tests, with different levels of path nesting.
I added a few tiny dependencies in this PR, because that's a lesser evil than reinventing the wheel completely 😃
Oh, and a small bonus: I tweaked how we look up assets from compilation.assets. We now take into account compilation.outputOptions.publicPath, so we can figure out the exact asset name without having to retry different parts of the path/filename. 👍
This PR closes issue #6.

nice work :)


NativePlatform not detected in the C# project

In the SamplesWin8.1\MediaPlayerCS project, the ffmpeg DLLs are not found due to the fact that the platform is always AnyCPU, therefore, the path to libraries are not correct:
E.g:

Expected: ffmpeg\Build\Windows81\ARM\bin\avcodec-56.dll
Actual: ffmpeg\Build\Windows81\bin\avcodec-56.dll

This is available for both Windwos 8.1 and Windows Phone 8.1 projects, for all ffmpeg DLLs
The CPP and JS project detect the libraries correctly.

Did you build the project from the command line? The MediaPlayerCS project does not have 'AnyCPU' configuration defined. I never end up with this configuration selected when opening the solution or project file before. However, I pushed an update to set the default to x86 anyway. Please let me know if you still encounter any issue. Thanks :)

According to https://msdn.microsoft.com/en-us/library/c02as0cs.aspx, the name of the macro for "Current Project Platform" is $(Platform).
But the macro for "Currently Targeted Platform" is $(PlatformName) (according to https://msdn.microsoft.com/en-us/library/42x5kfw4.aspx).
So I believe that we need to consider PlatformName (for the entire solution) instead of Platform. I changed the code in .csproj (Windows and Windows Phone) and now the DLLs are correctly selected.


Attachments

Hello there:) This is more a question than an issue.
Is it possible to read the attachments of an email? Since IMAP protocol supports it I was wondering if this library can also handle that, otherwise I could try to contribute :)
Thank you rocket

Hey! You should be able to grab any part of the body (including attachments) through the use of Session::fetch and then inspecting the resulting Fetch responses. The attachments will generally be outlined in the "bodystructure" part of Fetch, which you can then fetch explicitly later on using BODY. This StackOverflow answer has some pointers that may prove useful :)


Gradients with np.linalg.inv

Hi,
I noticed that taking gradients involving the np.linalg.inv function gives an error. Take for example,
from jax import grad
import jax.numpy as np
import jax.random as random
key = random.PRNGKey(0)

W = random.uniform(key, (10, 10), minval=-1, maxval=1)

def some_func(W):
    return np.linalg.inv(W)[0][0]

grad(some_func)(W)

This gives the error (included the warnings just in case)
  warnings.warn('No GPU found, falling back to CPU.')
[...]/jax/numpy/linalg.py:114: UserWarning: numpy.linalg support is experimental and may cause silent failures or wrong outputs
  warnings.warn(_EXPERIMENTAL_WARNING)
[...]/jax/numpy/linalg.py:124: UserWarning: numpy.linalg support is experimental and may cause silent failures or wrong outputs
  warnings.warn(_EXPERIMENTAL_WARNING)
Traceback (most recent call last):
  File "[...]/interpreters/ad.py", line 149, in get_primitive_transpose
    return primitive_transposes[p]
KeyError: sub

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "error.py", line 11, in <module>
    grad(some_func)(W)
  File "[...]/jax/api.py", line 114, in grad_f
    ans, g = value_and_grad_f(*args, **kwargs)
  File "[...]/jax/api.py", line 151, in value_and_grad_f
    g = vjp_py(onp.ones((), onp.result_type(ans)))
  File "[...]/jax/api_util.py", line 55, in apply_jaxtree_fun
    ans = fun(*args)
  File "[...]/jax/api.py", line 366, in out_vjp_packed
    return out_vjp(cotangent_in)
  File "[...]/jax/interpreters/ad.py", line 78, in vjp_
    _, arg_cts = backward_pass(jaxpr, consts, (), dummy_primal_and_ct)
  File "[...]/jax/interpreters/ad.py", line 135, in backward_pass
    cts_out = get_primitive_transpose(eqn.primitive)(ct_in, *invals, **eqn.params)
  File "[...]/jax/interpreters/ad.py", line 152, in get_primitive_transpose
    "Reverse-mode differentiation rule for '{}' not implemented".format(p))
NotImplementedError: Reverse-mode differentiation rule for 'sub' not implemented

I'm assuming this is similar to #407 ?
Thanks

I think this is actually fixed already. Are you using an up to date jax? (It's possible we haven't pushed it into a release yet, so you might need to use jax but not jaxlib from Github rather than Pypi.)

Yes that was the case, apologies my bad


clone后发生报错

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM 0.9.1
Operating system/version
WIN11
Terminal name/version
Powershell
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue
在clone时会失败并报出Error detected while processing C:\Users\guangkun\AppData\Local\nvim\init.lua:
E5113: Error while calling lua chunk: C:\Users\guangkun\AppData\Local\nvim/lua/core/init.lua:
164: 错误

Expected behavior

Actual behavior
No response
Additional information
No response

U dont just clone and use this repo, read the doc first.

我使用的是doc的命令安装，安装结束之后就显示成这样

U dont just clone and use this repo, read the doc first.
And don't use self-compiled nvim.

我使用的是doc的命令安装，安装结束之后就显示成这样

Do some research in the closed issues, thanks for your cooperation.


Added a benchmark capability to the tearsheet.

Coverage decreased (-3.8%) to 68.182% when pulling aefcebe6c58f0eea816d3fd4cbffc3beec88bc1f on tearsheet-upgrades into 4af45151f2f973d21172042a8d4d1bd478d61aff on development.


Question:Is this compatible with optifine?

Title says it all.

Get Cosmetica capes working on Optifine
To add partial Cosmetica support to a bunch of clients.
https://www.arccapes.com/install.html
Using this method the capes you'll be displayed will not respect your cape settings. It uses default settings with the exception of Optifine capes which are shown. We're working on an alternative method to this that you'll be able to use and have more control over what cosmetics you see.
Eyezah on discord yesterday

So I think this is a good anwser (:

The Cosmetica mod itself is also compatible with Optifne! You'll just need to use OptiFabric seeing as we don't yet have a Forge mod.


Clean up deno example

This PR:

Remove unneeded permission from the README
deno fmt
fix warnings

Couple of questions:

Does this need better typing ? or the await is actually not needed

Is there a simple example where there is actual system read, just to showcase deno --allow-read working in synergy with the wasm permissions

Does this need better typing ? or the await is actually not needed

We still need the await. The package.json wasn't declaring a typings file before, so your editor would have struggled to resolve the return value. This should be resolved by https://github.com/wasmerio/wasmer-js/commit/07b61f25bed62609d91a3aa1ef06c6ebbdb7eb3e.

Is there a simple example where there is actual system read, just to showcase deno --allow-read working in synergy with the wasm permissions

I'm not sure. I guess you could try running one of the WASI executables from the wasmer/wabt package on WAPM (e.g. wasm2wat), but I haven't tried that with Deno before.
@sigmaSd, are you able to rebase onto the main branch to pick up the new CI file? If you get merge conflicts from the pkg/ directory, you should be able to resolve them by running npm run build and overwriting the files.

rebase done
Regarding the await, deno doesn't use package.json and the only file it uses is the typescript file
If I gotodefinition this is what I see

Hmm... That might be because the typings file is called lib.d.ts, while the JavaScript file is called Library.cjs.js or Library.esm.js or Library.umd.js depending on how the code is being imported (UMD vs CommonJS vs ES Modules).


Add __STORYBOOK_CLIENT_API__ for external tools

So tools like Chromatic and others that interact with the client API can work with storybooks that haven't injected any code.
I would love to refactor this code from preview into core but I will leave to a later PR.
How to test
Check that __STORYBOOK_CLIENT_API__ is defined in each example app.

cc @timhaines

Yes, interested to know if this helps Percy and if there is more that would be needed at your end @timhaines

Would it perhaps also be useful to expose the channel, perhaps on __STORYBOOK_CHANNEL__? That way scripts could also fire events to trigger things like stories rendering.

Feel free to add as long as you're going to use it =)

@Hypnosphi => https://github.com/storybooks/storybook/pull/3243