when send request to /userinfo with idtoken, it does not work

Describe the bug
I have got idtoken, and I sent request to /userinfo with idtoken, it does not work
To Reproduce
1、get id token

2、send request to /userinfo with idtoken

3、I traced the code, when it went to this line, it returned null and throwed exception

Expected behavior
what confuses me is why the type is OAuth2TokenType.ACCESS_TOKEN instand of IDToken ?

this version is 0.4.0

this authorizationService is InMemoryOAuth2AuthorizationService, but when i have a bean as following, it works normal
@Bean
    public OAuth2AuthorizationService authorizationService(JdbcTemplate jdbcTemplate,
                                                           RegisteredClientRepository registeredClientRepository) {
        return new JdbcOAuth2AuthorizationService(jdbcTemplate, registeredClientRepository);
    }

You should be using the access_token.

You should be using the access_token.

all right, then i have one more question, what is the use of IDToken?

You should be using the access_token.

all right, then i have one more question, what is the use of IDToken?

IDToken is used for sso,  it  likes to the Service Ticket in CAS

You should be using the access_token.

all right, then i have one more question, what is the use of IDToken?

You can find more details here https://oauth.net/id-tokens-vs-access-tokens/

You should be using the access_token.

all right, then i have one more question, what is the use of IDToken?

You can customize the IdToken and return the user info within that token and the client can decode token and retrieve the user info without needing to call the userinfo endpoint

You should be using the access_token.

all right, then i have one more question, what is the use of IDToken?

You can customize the IdToken and return the user info within that token and the client can decode token and retrieve the user info without needing to call the userinfo endpoint

great, your reply is very helpful to me, thank you very much !


Use CMAKE_CXX_VISIBILITY_PRESET instead of manually checking flags

The updates of fmt.tar.gz and molfiles.tar.gz are here to set CMake policy CMP0063 to NEW and silence a warning.

The changes in tar.gz files are https://github.com/chemfiles/molfiles/commit/532a22308aac8d24262ad6095a13462d47e44214 and https://github.com/chemfiles/fmt/commit/a1cef0ff2a0902ceaf4cf9f010e859c9e871ab01+https://github.com/chemfiles/fmt/commit/10838b63c37c9970e71f4fb0796b794bc4a34338

Travis is green (https://travis-ci.org/chemfiles/chemfiles/builds/448387488?utm_source=github_status&utm_medium=notification), the commit status did not get updated =/


Add comment toggling

Refers to #14626

Thanks. Can you add this:
	vim9script
	import autoload 'dist/comment.vim'
	nnoremap <silent> <expr> gc comment.Toggle()
	xnoremap <silent> <expr> gc comment.Toggle()
	nnoremap <silent> <expr> gcc comment.Toggle() .. '_'

into a new file pack/dist/opt/comment/plugin/comment.vim?
Then we can add the following to the documentation:
 Load the plugin with this command: >
    packadd comment
<
This way you can use the plugin with the default key bindings `gc` and similar for commenting (which is a well-established mapping established in the Vim community).

To have more control over the mappings used, add the following snippet to your .vimrc (assuming vim9 script): >
	vim9script
	import autoload 'dist/comment.vim'
	nnoremap <silent> <expr> gc comment.Toggle()
	xnoremap <silent> <expr> gc comment.Toggle()
	nnoremap <silent> <expr> gcc comment.Toggle() .. '_'

Something like this?
Can you please also add yourself in the header of the autoload script as upstream author? And please also as Codeowner. We may also need to update the Filelist

Would it make sense to move the autoload to pack/dist/opt/comment as well then?

It doesn't feel right to add help entry into filetype.txt though.

It doesn't feel right to add help entry into filetype.txt though.

We put it in various.txt: https://github.com/neovim/neovim/blob/a736e845a48c5ccdcfeb4ea485aa859a04b35d59/runtime/doc/various.txt#L560-L597

Thanks. I would move it to around here: https://github.com/vim/vim/blob/98b12ede31754071f36fb7a73324456c1ee7b89c/runtime/doc/usr_05.txt#L440 so it's close to the editorconfig and matchit install instructions.
We should also document the use of 'commentstring' option. Also that it won't do anything if this option isn't set for a particular filetype and how to set this to make gc work. The Neovim doc looks quite clear in this regard.
I am wondering, whether we should add help-tags for gc. That will certainly conflict with tpopes commentary plugin. So not sure if this is a particular good idea or not.

I am wondering, whether we should add help-tags for gc. That will certainly conflict with tpopes commentary plugin. So not sure if this is a particular good idea or not.

We did, because otherwise :h gc won't work because there are tags with a higher score. And conflicts (E154) are only triggered by duplicate tags in the same directory? @zeertzjq

Since this is an optional plugin, maybe mapping tags like gc should be added to pack/dist/opt/comment/doc/ instead, so that they are only found when the plugin is loaded.

I am wondering, whether we should add help-tags for gc. That will certainly conflict with tpopes commentary plugin. So not sure if this is a particular good idea or not.

please let the choice back to users, there lots wonderful vim plugins, it should be not possible to add them all within vim,
besides some users specifically may just like tpopes' commentary (e.g me), so that conflict may not be liked by amount of people.
--
shane.xb.qian

We should also document the use of 'commentstring' option. Also that it won't do anything if this option isn't set for a particular filetype and how to set this to make gc work. The Neovim doc looks quite clear in this regard.

If it would wait another week or so, or anyone else would be able to add this documentation.

please let the choice back to users, there lots wonderful vim plugins, it should be not possible to add them all within vim,
besides some users specifically may just like tpopes' commentary (e.g me), so that conflict may not be liked by amount of people.

It's completly optional. You will need to use packadd to use it. Or simply use your favorite other plugin. And it makes sense, to add the plugin specific documentation into the package itself.

yes, if really added this within vim, i think @zeertzjq 's suggestion should be acceptable; or leave it alone, this commentary plugin looked was not so essential, visual-selection operation can do it also.
--
shane.xb.qian

Thanks all. I have included it and adjusted the documentation.
@habamax I made a simple change to the plugin, so that it doesn't error out for non-modifiable buffers: https://github.com/vim/vim/blob/5400a5d4269874fe4f1c35dfdd3c039ea17dfd62/runtime/pack/dist/opt/comment/autoload/comment.vim#L18

Related: https://github.com/neovim/neovim/pull/28176

Thanks, @chrisbra!

Thank you, @habamax and @chrisbra :)


Add Kubernetes documentation to Jump

I have moved the environment variables to their own section as they apply to multiple installation methods
I have added documentation for installing Jump on Kubernetes with Helm

Thanks for this, must admit I've not got much experience with helm charts but it looks good to me.

Personally I've got mixed opinions on Helm, but nonetheless it seems to be the de facto standard for small deployments on Kubernetes. And getting my Helm chart indexed on ArtifactHub will hopefully give it some more exposure 🙂

Well thanks so much for your contribution, glad you're enjoying Jump 😃


KAFKA-17374: add bootstrap.controller to kafka-reassign-partitions.sh

Jira: issues.apache.org/jira/browse/KAFKA-17374
According to the KIP-919 kafka-reassign-partitions.sh should support the --bootstrap-controller argument.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@m1a2st Could you please rebase code to include #16644?

@m1a2st could you please sync code?


IngressGateway fails to start with unknown proxyComponentLogLevel flag

Bug description
IngressGateway component is failing with following error:
$kubectl log istio-ingressgateway-868fc8d7fd-9n4cv -n istio-ingress -p
2019-05-28T04:52:03.543645Z	error	unknown flag: --proxyComponentLogLevel
Error: unknown flag: --proxyComponentLogLevel

I suspect this PR, which provides proxyComponentLogLevel and proxyLogLevel as parameter for istio/proxyv2.
While pilot supports this parameter, it seems istio/proxy does not support this parameter yet.
Expected behavior
istio-ingressgateway pods to get to Ready state upon installation.
Steps to reproduce the bug
Simply try docker run -it istio/proxyv2:1.1.7 proxy router --proxyComponentLogLevel=misc:error or
follow installation step below and observe logs of ingressgateway pods.
Version (include the output of istioctl version --remote and kubectl version)
$ istioctl version --remote
client version: version.BuildInfo{Version:"1.1.6", GitRevision:"04850e14d38a69a38c16c800e237b1108056513e-dirty", User:"brew", Host:"Mojave-2.local", GolangVersion:"go1.12.5", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.6"}
citadel version: version.BuildInfo{Version:"1.1.7", GitRevision:"eec7a74473deee98cad0a996f41a32a47dd453c2-dirty", User:"root", Host:"341b3bf0-76ac-11e9-b644-0a580a2c0404", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.6-6-geec7a74"}
$
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-19T22:12:47Z", GoVersion:"go1.12.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.9", GitCommit:"16236ce91790d4c75b79f6ce96841db1c843e7d2", GitTreeState:"clean", BuildDate:"2019-03-25T06:30:48Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

I've tried this with both 1.1.4 and 1.1.7 versions.
How was Istio installed?

Clone istio/installer repository
Checkout current master
Run ./bin/install.sh install_all with all default values

Environment where bug was observed (cloud vendor, OS, etc)
cloud vendor=AWS
newly kubernetes cluster span up via KOPS
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.
My attempt to dump state failed :( with following error. let me know if you still need this I'll dive into the script to see what's wrong there.
sh: line 118: "0" + "1084782": syntax error: operand expected (error token is ""0" + "1084782"")

The flag is a part of pilot agent not envoy: https://github.com/istio/istio/blob/8476158e82721ec4929e7071eb85f26b85189241/pilot/cmd/pilot-agent/main.go#L78
It is not in release-1.1, which is why it doesn't work -- istio/installer can only install 1.2 (master), not 1.1. I don't think we have settings to make it install 1.1, did you maybe have TAG environment variable set? If not maybe a bug somewhere that sets it incorrectly

This will be fixed now. 1.2 has the flag, and in 1.1 we allowed unknown flags

Thank you @howardjohn


Interactive table

Make the table interactive:

Sort by clicking on a column
Show more than 50 rows
Search for a star/HD number
Link from star/HD number to Simbad

Except the links, all have been done with commit 2db94d9b234bf319409324ad032262bed2b03baf


【Feature】Support Add Node Programmatically Manually  Automatically

Thank all of you very much for sharing 👍
I tried many ways to build flow through meta nodes json, none of them worked very well. 😟😟😟
SO I developed a set of functions for automatic programmatically adding nodes implemented based on simulated drag and drop
, hoping to help someone.

First I would create a node json string

let NODE_RELATION = {
        root: [{
            "type": "gongwei",
            "name": "gongwei_1",
            "parent_id": -1,
            "children": [{
                "parent_id": 1,
                "type": "pipeline",
                "name": "pipeline_1",
                "children": [{
                    "type": "analyze",
                    "name": "analyze_1",
                    "parent_id": 3,
                    "children": []
                }]

            }]
        }, {
            "parent_id": -1,
            "type": "gongwei",
            "name": "gongwei_2",
            "children": []
        }]
    }

In the second part🚗🚗🚗, I will create a function that adds nodes. In this function, the mousedown function will be used,-
then the flowy.drag object will be dynamically modified (atrr left and top) to move the object's position to the middle of the screen.
finally, the mouseup function will be used to release drag object.
It should be noted that offset and px will change according to the screen size.

    function add_node(node_type, node_name, parent_node_id) {
        offset_y = 35
        offset_x = 200

        $(`#${node_type}`).click()

        let evt = new MouseEvent("mousedown", {
            bubbles: true,
            cancelable: true,
            view: window,
        });

        $(`input[value="${node_name}"]`).parent()[0].dispatchEvent(evt);
        console.log('flowy.drag()', flowy.drag())
        if (parent_node_id == -1) {
            flowy.drag().style.left = '900px'
            flowy.drag().style.top = '150px'
        } else {
            flowy.drag().style.left = flowy.blocks()[parent_node_id].x + offset_x + "px"
            flowy.drag().style.top = flowy.blocks()[parent_node_id].y + offset_y + "px"
        }

        let evt1 = new MouseEvent("mouseup", {
            bubbles: true,
            cancelable: true,
            view: window,
        });
        $('#canvas')[0].dispatchEvent(evt1);
    }

Finally, the final flowy can be constructed by the meta node NODE_RELATION data json according to the number of layers.

add_node('root', 'root', -1)
for (let level_1 of NODE_RELATION['root']) {
    add_node(level_1['type'], level_1['name'], level_1['parent_id'])
}

If you need all the codes you can contact me ❤❤❤

Originally posted by @wscjxky in https://github.com/alyssaxuu/flowy/issues/110#issuecomment-2046970507

Hi @wscjxky I'm using flowy for my fyp, I have a need of input flowy node manually Can you please share the full code?

Hi all!,
Thank you @wscjxky for the code it's very helpful. I found this library and it's a pity that is not updated with features, it's simple to use and does most of the functionality, but missing a few ones is a killer.
Could I use your code @wscjxky to have a node with two parents?.
In the flows I need, the user will create flows with parallel branches that merge. It seems that by fixing the parent in whatever position I need it would work, but I don't know if I will run into further issues.
Thank you very much!.

Thanks a lot for the quick reply and the link of other people working on
the same I appreciate it a lot. From what I saw this is something far from
trivial. Would reconsider my choice of going with this library then. Thanks
and greetings from Spain!.
On Fri, Apr 26, 2024, 11:45 Stanley @.***> wrote:

Hi all!,
Thank you @wscjxky https://github.com/wscjxky for the code it's very
helpful. I found this library and it's a pity that is not updated with
features, it's simple to use and does most of the functionality, but
missing a few ones is a killer.
Could I use your code @wscjxky https://github.com/wscjxky to have a
node with two parents?.
In the flows I need, the user will create flows with parallel branches
that merge. It seems that by fixing the parent in whatever position I need
it would work, but I don't know if I will run into further issues.
Thank you very much!.
I'm glad to help you. 👍
But I think @alyssaxuu https://github.com/alyssaxuu didn't support that
a node with multiple parent nodes.
Now only supports a node with one parent.
#102 https://github.com/alyssaxuu/flowy/issues/102
—
Reply to this email directly, view it on GitHub
https://github.com/alyssaxuu/flowy/issues/148#issuecomment-2079027244,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3KRUX62KEED2XKJFLQH5DY7IO4BAVCNFSM6AAAAABGABKWLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZGAZDOMRUGQ
.
You are receiving this because you commented.Message ID:
@.***>

Hi @wscjxky I'm using flowy for my fyp, I have a need of input flowy node manually Can you please share the full code?

https://github.com/wscjxky/flowy/tree/master/program_add_node_demo

It doesn't work?

@wscjxky  yer sorry I deleted my comment. This will be helpful. Thanks.

@wscjxky it's a great start, I have implemented code based on yours that pulls the schemas from a database, its not very intuitive clicking the tabs, loading the HTML, then clicking the first tab again to load back. I take it this is due to restrictions with underlying library?

The plugin is great and thanks to the creator.
Unfortunately, there are too many limitations, so I decided to create a React version for myself with branching and manual block links. I'm still working on it, and once it's complete, I will create an open-source version of it.

Looking forward to it Abhijit.
On Thu, Oct 31, 2024, 1:25 PM Abhijit Das @.***> wrote:

The plugin is great and thanks to the creator.
Unfortunately, there are too many limitations, so I decided to create a
React version for myself with branching and manual block links. I'm still
working on it, and once it's complete, I will create an open-source version
of it.
Screenshot.2024-10-31.at.11.52.02.PM.png (view on web)
https://github.com/user-attachments/assets/2f153af7-f367-4f51-9810-b83c948a2c73
—
Reply to this email directly, view it on GitHub
https://github.com/alyssaxuu/flowy/issues/148#issuecomment-2450555857,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISPRAT6Q5GE27ATPHVAD3Z6JYYNAVCNFSM6AAAAABGABKWLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJQGU2TKOBVG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi everyone!
I’m excited to announce that I’m now building this project in public: @madgeek_in/react-flow-builder
If you're interested in contributing or have ideas to improve the flow builder, I'd really appreciate some pull requests and any help you can offer. Let’s work together to make this tool as useful and flexible as possible for the community. Thank you for your support and contributions!

Looks interesting. I think if it’s based on Flowy you could (or should) give some credit to the original project in your documentation.


Searches coming up empty

@dmhacker Can you update this repository? The YouTube searches are coming up empty on Heroku.

I implemented thepauleh's changes.  I couldn't figure out how to get his commit applied to my fork so I copied the two files.  It's working and finds a result then asks if I want to download it.  Every time after it says "An error occurred.  Video unavailable".

Im seeing the same thing - my hunch is the file storage. Its my first time playing with Heroku, but it appears the local dyno storage is designed to be stateless / isnt distributed

Well at least I know I did the first part right. You are doing better than me.  I'm an old retired mainframe programmer so this is definitely beyond the scope of my experience.  I do good to figure out the tutorial for these things. ;)

Slightly different than thepauleh and the guy claims it works so trying it.  He updated some additional versions.
https://github.com/dmhacker/dmhacker-youtube/issues/17#issuecomment-656951127


Accessing HTTP(s) Keyword with Basic Auth

Is it a duplicate question?
No, didn't find anything similar
Attempting to access a URL using basic auth in the URL
https://user:password@HOSTNAME
It appears that the page is not loading.  This works in the browser.  Is it even possible to access a URL using basic auth in the URL or is there a different way to format the URL?
Info
Uptime Kuma Version: 1.7.3
Using Docker?: Yes
Docker Version:  20.10.7
Node.js Version (Without Docker only):
OS: Ubuntu 21.04
Browser: Chrome / Brave

Basic Auth is not supported.

@Abdulvoris-Urolov
#864 should include basic auth.
Could you open a help issue with the context what worked, what did not instead of necroposting on this issue?


Introduce facet-lib

In attempt to move all reusable components and related code to a library.
Homepage: https://github.com/mareklibra/facet-lib
To be done in follow-ups:

reexport selected components
setup CI on facet-lib
move facet-lib under same repo as the facet project (which is about to be moved too)
test reusability in OCM and OCP projects

Deprecated by #218, closing


Release updated quick start image

The quick start code has been updated, but a new docker image has not been pushed.

@bobbywatson3 Thanks for the reminder. I just pushed a new quickstart image 2.1.1 to docker hub and updated the chart again to use this image by default in https://github.com/bastionzero/charts/pull/15

Perfect, thanks!


Check added stack trace parts for filename match

Fixes https://github.com/substack/tape/issues/386. Also refactors regex checking code a little.
One thing I'm not sure about is how to test this. The issue is actually this line here:
https://github.com/fongandrew/tape/blob/2c242ca9715b6b0bfded23fccb522dd414d96612/lib/test.js#L219
Tape ignores stack trace lines that originate from files starting with that dir variable. Currently, it means ignoring all stack trace lines from within tape's own package directory. The problem is that tape's own tests also live within its package directory, so the at variable is never set on the result object.
We could try changing dir to point to just the lib directory inside the package. This would result in the at being set and we could check it. This should be fine to do, since the stack trace for an assertion error shouldn't run through any file outside of the lib directory, but I'm not sure if that could change in the future.
Also, this would result in 25 or so existing tests failing (since their test outputs don't include the at variable). It wouldn't be a big deal to update those tests (correct behavior should be including the at variable in those test results), but feedback welcome on that.

I think that tests kind of need to not ignore stack trace lines that originate within the tests directory, so I'd think updating those tests is the right path here (also totally fine to do that in a separate PR, and this can be rebased after that's merged)

Updated tests are in https://github.com/substack/tape/pull/388. This PR is rebased off of that one.

Please rebase this on latest master when you can :-D

Rebased!

Added test for a file name with a space in it. Rewrote the stack trace regex to handle that scenario. New approach also gets rid of the for ... in loop.

Comments addressed (amended old commit).


typegoose 4.0 broken

docs do not seem to be updated for 4.0 release unless they need no update
objects are being persisted to db
but without properties
any feedback appreciated

Can you provide a sample? My projects are working fine with 4.0.

private async create(ctx: Koa.Context) {
    const data = ctx.request.body;

    let u = await UserModel.create({
        _id: mongoose.Types.ObjectId(),
        emailAddress: data.emailAddress,
        password: data.password
    });

    this.renderCtx
        .renderSuccess(
            ctx,
            HttpStatus.CREATED,
            'users',
            u.toString());
}

response from REST client in webstorm
User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.
debugger console follows
"C:\Program Files\nodejs\node.exe" --inspect-brk=63640 C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\dist\server\server.js cross-env NODE_ENV=development nodemon --watch 'server/**/*' -e ts,tsx --exec 'ts-node' ./server/server.ts
Debugger listening on ws://<IP_ADDRESS>:63640/800ff62a-bd39-45a4-b49f-7797fbaa356c
For help see https://nodejs.org/en/docs/inspector
the server/replset/mongos options are deprecated, all their options are supported at the top level of the options object [poolSize,ssl,sslValidate,sslCA,sslCert,sslKey,sslPass,sslCRL,autoReconnect,noDelay,keepAlive,keepAliveInitialDelay,connectTimeoutMS,family,socketTimeoutMS,reconnectTries,reconnectInterval,ha,haInterval,replicaSet,secondaryAcceptableLatencyMS,acceptableLatencyMS,connectWithNoPrimary,authSource,w,wtimeout,j,forceServerObjectId,serializeFunctions,ignoreUndefined,raw,bufferMaxEntries,readPreference,pkFactory,promiseLibrary,readConcern,maxStalenessSeconds,loggerLevel,logger,promoteValues,promoteBuffers,promoteLongs,domainsEnabled,checkServerIdentity,validateOptions,appname,auth,user,password,authMechanism,compression,fsync,readPreferenceTags,numberOfRetries,auto_reconnect,minSize]
Server running on port 3000
MongoDB connection success Bluebird. MongoDB is running.
{"method":"POST","url":"/api/user","query":{},"remoteAddress":"::ffff:<IP_ADDRESS>","host":"localhost:3000","userAgent":"Apache-HttpClient/4.5.2 (Java/1.8.0_152-release)","errorMessage":"User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.","errorStack":"ValidationError: User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.\n    at new ValidationError (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\error\validation.js:27:11)\n    at model.Document.invalidate (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1725:32)\n    at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1597:17\n    at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\schematype.js:785:9\n    at process._tickCallback (internal/process/next_tick.js:150:11)","statusCode":500,"responseTime":56}
ValidationError: User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.
at new ValidationError (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\error\validation.js:27:11)
at model.Document.invalidate (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1725:32)
at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1597:17
at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\schematype.js:785:9
at process._tickCallback (internal/process/next_tick.js:150:11)
{"method":"POST","url":"/api/user","query":{},"remoteAddress":"::ffff:<IP_ADDRESS>","host":"localhost:3000","userAgent":"Apache-HttpClient/4.5.2 (Java/1.8.0_152-release)","errorMessage":"User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.","errorStack":"ValidationError: User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.\n    at new ValidationError (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\error\validation.js:27:11)\n    at model.Document.invalidate (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1725:32)\n    at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1597:17\n    at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\schematype.js:785:9\n    at process._tickCallback (internal/process/next_tick.js:150:11)","statusCode":500,"responseTime":5}
ValidationError: User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.
at new ValidationError (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\error\validation.js:27:11)
at model.Document.invalidate (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1725:32)
at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1597:17
at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\schematype.js:785:9
at process._tickCallback (internal/process/next_tick.js:150:11)
Debugger attached.
Debugger listening on ws://<IP_ADDRESS>:63640/800ff62a-bd39-45a4-b49f-7797fbaa356c
For help see https://nodejs.org/en/docs/inspector
Process finished with exit code 1

import {prop, Typegoose} from 'typegoose';
import * as mongoose from 'mongoose';
mongoose.connect('mongodb://localhost:27017/api');
export class User extends Typegoose {
@prop({ required: true })
emailAddress: string;
@prop({ required: true })
password: string;
}
export const UserModel = new User().getModelForClass(User);

the .create method on the model isnt taking
i saw in the debugger after await, undefined
but the data coming in from koa is fine I see the data in my data object

thank you for the help I will try to clean up troubleshooting better with a github project eventually
just trying to shake this out
I like it
does the create return an object to async off of ?

originally I saw objects being persisted to the database with ID and no properties
found out I need to get rid of new and use create
but now using create nothing gets persisted

my UserModel seems to be undefined when making the create call
so life cycle of the model is undefined for some reason

Please provide a sample repository, that makes it a lot easier

Its looking like timing of where the mongoose.connect (...) is placed
I could put it in the model
I could put it in my router at the top
I could put in my router constructor
QUES: where is the ideal place to put mongoose.connect(...)
does it get bootstrapped somehow into typegoose beforehand so proper binding takes place ?

I have searched github for a starter project using koa2 typescript for async/await
and found none
thats what I am working on now
but this typegoose package could use a descent starter project on github to accomodate

here is latest output
MongoDB connection success Bluebird. MongoDB is running.
{"method":"POST","url":"/api/user","query":{},"remoteAddress":"::ffff:<IP_ADDRESS>","host":"localhost:3000","userAgent":"Apache-HttpClient/4.5.2 (Java/1.8.0_152-release)","errorMessage":"User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.","errorStack":"ValidationError: User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.\n    at new ValidationError (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\error\validation.js:27:11)\n    at model.Document.invalidate (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1725:32)\n    at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1597:17\n    at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\schematype.js:785:9\n    at process._tickCallback (internal/process/next_tick.js:150:11)","statusCode":500,"responseTime":9}
ValidationError: User validation failed: emailAddress: Path emailAddress is required., password: Path password is required.
at new ValidationError (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\error\validation.js:27:11)
at model.Document.invalidate (C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1725:32)
at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\document.js:1597:17
at C:\apache-tomcat-9.0.0.M17\webapps\ROOT\api\node_modules\mongoose\lib\schematype.js:785:9
at process._tickCallback (internal/process/next_tick.js:150:11)
Debugger attached.
Debugger listening on ws://<IP_ADDRESS>:63927/03ed2772-078a-40ad-94ae-a7e5c2173ef4
For help see https://nodejs.org/en/docs/inspector

this is the router
import * as Koa from 'koa';
import IRouter from '../isomorphic/IRouter';
import * as Router from 'koa-router';
import RenderCtx from '../isomorphic/RenderCtx';
import * as HttpStatus from 'http-status-codes';
import * as mongoose from 'mongoose';
import {UserModel} from './model/User';
import * as Bluebird from 'bluebird';
class UserRouter implements IRouter {
private static connectString = process.env.MONGODB_URI || 'mongodb://localhost/api';
private Router = new Router({
    prefix: '/api',
});
private renderCtx = new RenderCtx();

constructor() {
    (<any>mongoose).Promise = Bluebird;
    mongoose.connect(UserRouter.connectString, {server: {poolSize: 15}})
        .then((): void => {
            console.log("MongoDB connection success Bluebird. MongoDB is running. ");
        })
        .catch((err): void => {
            console.log("MongoDB connection error. Please make sure MongoDB is running. " + err);
            process.exit();
        });
}

// We need use bind for transmission context
// https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/bind
public router(): Router {
    return this.Router
        .post('/user', this.create.bind(this));
}

private async create(ctx: Koa.Context) {
    const data = ctx.request.body;

    let u = await UserModel.create({
        _id: mongoose.Types.ObjectId(),
        emailAddress: data.emailAddress,
        password: data.password
    });

    this.renderCtx
        .renderSuccess(
            ctx,
            HttpStatus.CREATED,
            'users',
            u.toString());
}

}
export const userRouter: UserRouter = new UserRouter();

Hi Ben,
I pushed what I have so far
if you can take a look that would be terrific
I will continue to shake it out
https://github.com/nhhockeyplayer/api

cheers

KEN

to reproduce I am running server.ts as follows
webstorm IDE

launch server.js from dist dir within a node.js debug configuration
and debugging node in webstorm debugger breakpoints work great
REST Client to post user.json at root dir

so its looking like create call is not binding properties for my koa2 project
im signing off for now
will check back in next 12 hours
thanks for any feedback

I cloned your repo but I can't get it running. But I saw something in user.router.ts:
let u = await UserModel.create({
  _id: mongoose.Types.ObjectId(),
  emailAddress: data.emailAddress,
  password: data.password
});

You should remove the line _id: mongoose.Types.ObjectId(), because the _id field is filled automatically.

@Ben305  I know I am out of topic, but I just want to share this with you:
https://snyk.io/test/npm/typegoose
"Remediation: Upgrade to<EMAIL_ADDRESS>Thanks a lot for Typegoose: amazing!

Ok here is latest
I removed the required=true as follows
export class User extends Typegoose {
@prop()
emailAddress: string;
@prop()
password: string;
}
export const UserModel = new User().getModelForClass(User);
now objects are persisting but only have the id no properties are being persisted

db.users.find()
{ "_id" : ObjectId("5a972214faaf4926c8a6b312"), "__v" : 0 }

Ben
running my project is very simple
properties are not holding water
is this going to be patched?
If not I will have to pass on typegoose
I want to use it but right now its not holding water
I provided a repo
build normally
ng build
then use a commans prompt and go into src/server and execute tsc
that will compile the server and output the compilation to the dist folder
at this point use webstorm to launch a node.js debug configuration pointing to server.js
thats it
run...and debug...steps thru code beautifully
ignore the client stuff
webstorm has a REST Client tool to post ./api/user.json
you have to specify application.json for the contenttype in the REST Client tool
If you can help I would be greatful

Ben you said your projects are all running fine.
can you post one for access?
the tests for typegoose appear to work from their own private dir
nothing is holding up beyond that
even keyword model is conflicting
I cant import
or get any predictable runtime here

the promise coming back from model.create(...) has undefined properties for the model
the pre hooks did persist createdAt updatedAt properties though
User.ts
@pre('save', (next) => {
if (!this.createdAt) {
this.createdAt = this.updatedAt = new Date();
}
next();
})
export class User extends Typegoose {
@prop()
emailAddress: string;
@prop()
password: string;
@prop()
createdAt?: Date;
@prop()
updatedAt?: Date;
}
export const model = new User().getModelForClass(User);
user.router.ts
private async create(ctx: Koa.Context, next) {
const data = ctx.request.body;
    let u = await model.create([{
            emailAddress: data.emailAddress,
            password: data.password
        }])
        .then((result) => {
            this.renderCtx
                .renderSuccess(
                    ctx,
                    HttpStatus.CREATED,
                    'users',
                    result);
        })
        .catch((err) => {
            this.renderCtx
                .renderFaild(
                    ctx,
                    HttpStatus.CONFLICT,
                    'users',
                    err);
        });
}

I'll start pairing down the package.json something with mongoose maybe

koa body was coming in as array
I was treating it as object
therefore it was never making it into the model on create


winget tries to upgrade .NET 5 Runtime over and over

Brief description of your issue
I have two .NET runtimes installed side by side: 5 and 6

winget sees the 5.0.17 version and tries to upgrade it to 6.0.7, even though 6.0.7 is already installed on the machine.
Steps to reproduce

Install .NET Runtime 5.0.17
Install .NET Runtime 6.0.7
Run winget upgrade
You'll see the following:

Name                                               Id                                Version       Available     Source
-----------------------------------------------------------------------------------------------------------------------
Microsoft .NET Runtime 6.0                         Microsoft.DotNet.Runtime.6        <IP_ADDRESS>213  6.0.7         winget

Expected behavior
winget treats .NET Runtime 5 and 6 as two different applications and does not offer new .NET 6 versions for .NET 5.
Actual behavior
winget treats .NET Runtime 5 and 6 the same application, offering new .NET 6 versions as upgrades for .NET 5.
Environment
Windows Package Manager v1.2.11601
Windows: Windows.Desktop v10.0.19044.1766
Package: Microsoft.DesktopAppInstaller v1.17.11601.0

The issue with dotnet runtimes is due to there being multiple versions of the runtime installed side-by-side and is related to

#1413

We have enhancements in Windows Package Manager 1.3 support for "AppsAndFeatures" data that will help in this scenario.

For me, this situation is a little bit different... I have installed only one version 5.0.13

but winget list to install version 3.1.27

o course when I try install it

@dw72
Can you try with "--verbose-logs" and share the resulting logs? I'd also like to know which version of Windows Package Manager you're running.

WinGet-2022-07-25-14-18-12.581.log

@exchange12rocks? Is this still happening?

@denelon Yes:
Name                                        Id                           Version Available Source
-------------------------------------------------------------------------------------------------
Microsoft .NET Runtime - 5.0.17 (x64)       Microsoft.DotNet.Runtime.6   < 6.0.5 6.0.14    winget
1 upgrade available.

I am also having this issue with different versions of the .NET runtime and winget. I have .NET 6.0.23 installed and winget would like me to upgrade it to 6.0.25. However, I already have that version installed as well.
In any case, winget downloads and attempts to install 6.0.25 and then closes shortly after starting the install. If I try to upgrade with the the -id flag, I get the "No installed packages [...]" message. If I try to install with the id, the package is found, downloaded and tries to install.
I have also found and ran the .NET Fix Repair tool, and it found no issues with my installed packages.
Winget version v1.6.3421

Having similar issue:

To workaround this, set the architecture and install.

set the architecture and install.

@aaronliu0130 could you elaborate further?

e.g. winget install Microsoft.DotNet.SDK.5 -a x64


[release/1.7 backport] Add WithReadonlyTempMount to create readonly temporary mounts

Backport of https://github.com/containerd/containerd/pull/8259

Backporting since we'd like to use this in:

https://github.com/moby/moby/pull/44964
https://github.com/moby/buildkit/pull/1100

potential concerns
the changes do functionally change the code in diff/walking/differ.go - Compare() to make the temp mount readonly. I don't think that should introduce any issues (and addresses https://github.com/containerd/containerd/issues/6077) but I thought it worth mentioning.

/cc @thaJeztah

/cc @dmcgowan @AkihiroSuda

/ok-to-test

Failures look unrelated, but I can't rerun them afaict


sorting is always by id if no filtering

https://github.com/umesh-krishna/django_serverside_datatable/blob/0da2f9b5c6f1e5da2cc9aa1e521b1993533b7cb7/django_serverside_datatable/datatable.py#L58
I think this would be fixed with the removal of 'id',  in the order_by() method

Fixed


removed extra quotes on 55

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

#label:"aq-pr-triaged"

@kof-f the name of the product changed in June: https://azure.microsoft.com/en-us/blog/azure-virtual-desktop-the-desktop-and-app-virtualization-platform-for-the-hybrid-workplace/

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


Fix library attachments

Libraries in Drupal 7 are attached as an array:
$return['#attached']['library'][] = array(
  $library['module'], $library['name'],
);

Whereas in Drupal 10 they are attached as a string with a slash separating the module and library name:
$return['#attached']['library'][] = $library['module'] . '/' . $library['name'];

@darrenoh could you paste a snippet of sample code that this fixes? I'll write a unit test

Done.


feat: add table of contents section to README

This little project really grew up into needing a table of contents 😭


Add August by Intilligence

Song Name
August
Artist Name
Intilligence
Source
Youtube
Youtube Link
https://youtu.be/oe5WzVf1kq4?si=tAUpNNclFvHUFp8x
Direct File Link
No response
Song ID
48
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 107553957

reject
duplicate request, no worries, the song has been accepted


feat: Adding code for sending parameter "response_format" as request payload

Related Issues/PRs
For newer models, openai accepts response_format, which can be text or json_object. This PR adds the parameter for this. Additionally, when developer set postprocessingoptions, in OpenAIPrompt class, post processing field is reduncdant and can be made optional. We cannot infer post processing from response format because json as response format is not supported by many models including GPT-4 and GPT-3.5-Turbo. All changes made in this PR as backward compatible and will not break any existing code.
What changes are proposed in this pull request?
In this PR, we are adding:

Ability to add parameter for response_format in OpenAIPrompt class and OpenAIChatCompletion class.
Added unit tests to validate this
Added code to infer postprocessing from postprocessingoptions and hence making it optional.

How is this patch tested?
Unit tests and integration tests are added to validate this change
Does this PR change any dependencies?

[X] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[X] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

/azp run

Codecov Report
Attention: Patch coverage is 0% with 77 lines in your changes missing coverage. Please review.

Project coverage is 1.91%. Comparing base (08aab6a) to head (d014023).

Files with missing lines
Patch %
Lines

...apse/ml/services/openai/OpenAIChatCompletion.scala
0.00%
41 Missing :warning:

...zure/synapse/ml/services/openai/OpenAIPrompt.scala
0.00%
35 Missing :warning:

...soft/azure/synapse/ml/services/openai/OpenAI.scala
0.00%
1 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (08aab6a) and HEAD (d014023). Click for more details.
HEAD has 150 uploads less than BASE

Flag
BASE (08aab6a)
HEAD (d014023)

151
1

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #2317       +/-   ##
==========================================
- Coverage   84.50%   1.91%   -82.59%
==========================================
  Files         326     326
  Lines       16755   16826       +71
  Branches     1480    1511       +31
==========================================
- Hits        14158     322    -13836
- Misses       2597   16504    +13907

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles

/azp run

/azp run

/azp run

/azp run

/azp run


Add parenthesis to deps and package function calls

Without parenthesis a warning is printed with elixir 1.4.0-rc.1

Thankyou - merged! (will do a release shortly as well - ta)


Show what Vega validator/data node you are connected to

potentially in the footer or with the Vega wallet version number

duplicate #931


Remove the linting error code placed in beginning of the message #2815

For #2815

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[ ] Title summarizes what is changing
[ ] Has a news entry file (remember to thank yourself!)
[ ] Unit tests & system/integration tests are added/updated
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)

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

Made some tweaks. Just waiting for CI to be green before we merge.


Include existing height when calculating new one for KeyboardAvoidingView

Summary
Currently, height is sometimes the only valid option for pushing TextInput up in the layout on Android. The problem is when switching keyboards. For instance, switching from ABC to emojis. This will trigger keyboard show events and recalculate the height for the KeyboardAvoidingView. Since the keyboard is still showing, the view has the height that was previously calculated and thus frame represents that. This means the frame.height has adjustments for the keyboard calculated in it, but it is used the same way as if the keyboard was not showing. This results in wrong calculation and the input showing at the incorrect place in the layout (mostly hidden under the keyboard)
This fix simply uses the previous calculation to offset frame.height, resulting in the correct height and smooth switching between keyboards. It's also scoped only to height mode since that's where the problem shows.
Note: I mention android here, but it fixes it for both platforms. It's just that iOS usually works best with different behaviour so it's rarely used there.
Changelog
[General] [Added] - Include this.state.bottom when calculating new keyboard height to fix android keyboard switching
Test Plan
With simple code:
import { StatusBar } from "expo-status-bar";
import React from "react";
import {
  KeyboardAvoidingView,
  StyleSheet,
  Text,
  TextInput,
  View,
} from "react-native";

export default function App() {
  return (
    <KeyboardAvoidingView style={styles.container} behavior="height">
      <Text>Open up App.js to start working on your app!</Text>
      <StatusBar style="auto" />
      <TextInput style={{ backgroundColor: "red", width: "100%" }} />
    </KeyboardAvoidingView>
  );
}

const styles = StyleSheet.create({
  container: {
    padding: 32,
    flex: 1,
    backgroundColor: "#fff",
    alignItems: "center",
    justifyContent: "space-between",
  },
});

Notice the consistency of the TextInput after the changes, while before it would just move around more you switch the keyboards.

Before
After

I can confirm the bug is here again in RN 0.70.5 :warning:

@Orange9000 @dranitski Here, you can find the version that includes PR.

It's very important task, thank you.

I can see this bug happening again in 0.71.8


Document App Store guidelines for data storage

As a developer, I need to know that we are meeting Apple/Google's guidelines for storing user data like emails and analytics data. This will make the submission process less of a risk of rejection.
Acceptance Criteria

Consider encryption
Apple/Google app store guidelines for storing user data (like emails and analytics data) is thoroughly evaluated for our specific plans
Findings and especially actions required is left as comments in this Issue

Apple:
We must have a privacy policy that says what data it collects and what it does with that data. Explain data retention policies (this would be more for our analytics)
We must request permission for any data collection even if data is anonymous.
We should only request access to data we need
Technically if we do not have access to the data or it is not being sent off of the device we do not need to disclose it, but its better if we do.
Overall not much there on how we store it as long as we disclose it. We should keep best practices anyway (encryption etc)
Google:
We must be transparent on how we handle user data. Same as apple, privacy policy.
Data must be secure and there is a clear retention and deletion policy.
We will need to fill out a data safety form
Overall looks like Apple is more strict so we should follow that and it should cover what Google requires.


improvement(seek): return the data source error when seek error

Signed-off-by: pingkai<EMAIL_ADDRESS>

Codecov Report

Merging #350 into develop will decrease coverage by 0.00%.
The diff coverage is 75.00%.

@@             Coverage Diff             @@
##           develop     #350      +/-   ##
===========================================
- Coverage    68.89%   68.89%   -0.01%
===========================================
  Files          214      214
  Lines        11681    11683       +2
===========================================
+ Hits          8048     8049       +1
- Misses        3633     3634       +1

Impacted Files
Coverage Δ

mediaPlayer/SuperMediaPlayer.cpp
74.39% <66.66%> (+0.20%)
:arrow_up:

framework/data_source/curl/curl_data_source.cpp
84.64% <100.00%> (ø)

framework/demuxer/play_list/SegmentList.cpp
87.71% <0.00%> (-8.78%)
:arrow_down:

mediaPlayer/player_msg_control.cpp
76.98% <0.00%> (-0.80%)
:arrow_down:

framework/codec/ActiveDecoder.cpp
86.34% <0.00%> (+0.48%)
:arrow_up:

Continue to review full report at Codecov.

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


Revert "[WIP] Adaptor config in a new table"

Reverts ecmwf-projects/cads-broker#68

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


ActiveRecord::ConnectionNotEstablished in extranet/home#index

Error in Osuny
ActiveRecord::ConnectionNotEstablished in extranet/home#index
connection to server at "<IP_ADDRESS>", port 35951 failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
View on Bugsnag
Stacktrace
app/models/communication/extranet.rb:88 - with_host
app/controllers/application_controller/with_domain.rb:6 - current_extranet
app/controllers/application_controller/with_domain.rb:12 - current_university
app/controllers/application_controller.rb:27 - ensure_university
app/controllers/application_controller/with_locale.rb:19 - switch_locale

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
ActiveRecord::ConnectionNotEstablished in users/unlocks#new

An error linked to this issue has been reopened in Bugsnag
ActiveRecord::ConnectionFailed in extranet/home#index

An error linked to this issue has been marked as fixed in Bugsnag
ActiveRecord::ConnectionFailed in extranet/home#index


Remove filtered VCF variants for Lumpy, Manta, CNVkit and WHAM

Marghoob;
Following up on #63, I managed to improve precision quite a bit after realizing that filtered variants were being included as MetaSV inputs for all of the new callers. This fix avoids that, and greatly improves our precision:

Nice, I'll continue to tweak but this brings us more in line with expectations. Thanks again for all the merges and discussion.

This collaboration is great. Thanks again. In the meanwhile, we have also added support for inversion assembly. We have even more improvements coming in for MetaSV!


Mermaid graph diagram not rendering

In overview section, there is a mermaid graph which isn't being rendered on live book.

This should have rendered to something like this:
graph TD;
    esp-idf-hal --> esp-idf-sys & embedded-svc
    esp-idf-svc --> esp-idf-sys & esp-idf-hal & embedded-svc

If we run mdbook serve locally, the graph gets rendered correctly, this issue is only when it's live on website.

The diagram is visible for me at least using Firefox on macOS, even when clearing the cache and refreshing the page.
Out of curiosity, which browser/OS are you running?

It's weird as yesterday it was not working for me either but now it works fine. I've tried both Chrome and Brave on MacOs,

I tested on Chrome on Android and Brave on windows. And as you can see in screenshot, it wasn't working at the time of reporting it, but as of now it is working! 😄

It's weird as yesterday it was not working for me either but now it works fine. I've tried both Chrome and Brave on MacOs,

I wonder what's causing it and how it got fixed automatically 🤔. If it had something to do with mermaid.js, their live demo and playground was working just fine.

Yeah, not sure. Obviously something funky was going on 😁
The diagram is still visible for me so I'm going to close this issue, but if you have any other problems please feel free to reopen it.


Reduce token update frequency

This pull request changes how a token is updated in absence of events to be handled by that segment.
Normally, both the Tracking and Pooled Streaming processor would eagerly update the TrackingToken in all scenarios.
Thus, event-full batches (read: events that the segment is in charge of) would update the token, but also event-less batches (read: when the segment is in charge of no events), would incur an immediate token update.
This pull request changes that behavior for both Streaming Processor implementations.
For the Pooled Streaming Processor, the WorkPackage now uses the extensionClaimThreshold to wait before doing any token update in absence of events it should handle.
The Tracking Processor now also introduces such a deadline.
It uses the "batch processing start time" and adds the eventAvailabilityTimeout.
This value is validated, combined with the hasNextAvailable check, in a while-loop every time events are added to the batch.

The tests for the TrackingEventProcessor aren't taken into account since we don't aggregate the coverage reports over several modules.
Hence, I will ignore Sonar Cloud's warning.


ZEROS not defined

I think the MAGICL port had some fruit left.
; in: DEFUN CL-QUIL.CLIFFORD::CLIFFORD-TO-MATRIX
;     (CL-QUIL.CLIFFORD::ZEROS
;      (LIST (EXPT 2 CL-QUIL.CLIFFORD::N) (EXPT 2 CL-QUIL.CLIFFORD::N)))
;
; caught STYLE-WARNING:
;   undefined function: CL-QUIL.CLIFFORD::ZEROS
;
; compilation unit finished
;   Undefined function:
;     CL-QUIL.CLIFFORD::ZEROS
;   caught 18 STYLE-WARNING conditions
;   printed 19 notes

Does this come up with the tests?
Grepping through the code this seems to be the only place missing the package


Swift version

I begin convert code to swift but i have problem to convet this code
#define GENERATE_SETTER(PROPERTY, TYPE, SETTER, UPDATER) \
- (void)SETTER:(TYPE)PROPERTY { \
    if (_##PROPERTY != PROPERTY) { \
        _##PROPERTY = PROPERTY; \
        UPDATER \
        [self setNeedsLayout]; \
    } \
}

can you help me to convert it?
you can check my code in this forked repo in swift branch
https://github.com/dimohamdy/StepSlider

I do not understand why you wanna convert it to swift, where is profit? But if you want - do it.
This code is precompile macro and it converts to usual setter, when compile. I wrote it just for less code and DRY. So you can use willSet for all those properties in swift. So code for index will be looks like:
var index = 0 {
    willSet {
        guard newValue != index else { return }

        sendActionsForControlEvents(.ValueChanged)
        setNeedsLayout()
    }
}

thank you


runtime-benchmarks gives an error: ValidatorSet does not have the std feature enabled

i have this error out of box on development branch when i try to run benchmarks on pallet-tft-price
error: `ValidatorSet does not have the std feature enabled, this will cause the substrate_validator_set::GenesisConfig type to be undefined.
  --> pallets/pallet-tft-price/src/mock.rs:73:1`

not sure why the error didn't pop up in the CI
here is the command that triggers the error mentioned above:
cargo test --no-fail-fast --features runtime-benchmarks -p pallet-tft-price

I see the pallet not added to std section in runtime cargo file, adding it didn't solve the error.
Update:
@renauter suggested a fix, and I will push it soon.

fixed in https://github.com/threefoldtech/tfchain/pull/776


Evidence income form view

Despite what the branch name says, this is the Income form object.
It's to be used to validate the Income amount the user provides when assessing the evidence based check.

@colinbruce please have a look at this when you get a minute, thanks

@dotemacs is this PR active, or should we close it for now? It's to be merged to master, so that's why I'm asking.

I'll be merging this into evidence-controller branch as I'll be using the form object implemented here for the page 4. of the prototype.

:+1:

Closing and re-opening PR on another branch


Export data after Filtering it.

Is there any way to export the data after filtering the data in the client side.

Current export example does export the filtered out data only.
If you want to export it without hitting the back end, you can only export current page.

Ohh  Yes. I just figured it out. So to download all data after column filtering I need to remove the RowsPerPage. Am I right?

For all the data you need remove paging when constructing the grid for the export.

Ok. Thanks a lot. By the way a very nice product you have build.


Multiple view type is not working.

I Use this way to show multiple layout.
mAdapter = new GenericAdapterBuilder()
.addModel(
R.layout.contact_row,
YourViewHolder.class,
YourModel.class)
.addModel(
R.layout.second_row,
YourSecondViewHolder.class,
YourSecondModel.class)
.addModel(
R.layout.third_row,
YourThirdViewHolder.class,
YourThirdModel.class)
.execute();
where i put condition which layout inflate at what position?

Hi,
You have to pass one list to the adapter. For instance, you have lists like below;
List<YourModel> yourList
List<YourSecondModel> yourSecondList
List<YourThirdModel> yourThirdList

List<Object> yourObjectList

yourObjectList.addAll(yourList);
yourObjectList.addAll(yourSecondList);
yourObjectList.addAll(yourThirdList);

adapter now you can pass your objectList to the adapter. Positioning depends on the objectlists' positions.

Hi,
Its working as u said. Could you please tell me how to switch to alternate viewtype and highlight the selected row like single selected item.
Thanks

All of those things just like the recyclerview. For highlighting the selected row; you can make itemview selected in your viewholder.
If you want to add new features besides above to the GenericRecyclerAdapter class, you can extend it or you can add some feature to this library and create a pull request.


git didn't invent version control

You write
GitHub didn’t invent version control. It took a program called git
but even git wasn't the first version control system.
I used CVS for years and then Subversion for years before git came around. And there were others before CVS, I think something called rcs, for one…  the concept is actually really really old.  the big innovation is that github added a really easy, pretty web UI (at just the right time) and turned distributed collaborative coding into a big social network too.
https://en.wikipedia.org/wiki/Revision_control
Anyway - thanks for such a great article.

This was the one omission that caught my eye, too. Version control has been around for a long time - but Git democratized it, by meeting the workflow needs of one notably popular and democratic piece of software. It also followed on the heels of BitKeeper, which provided some of the same concepts, but is now remembered mainly for the licensing disputes that led to the development of Git and Mercurial.
Seems a bit unfair to SVN, which was hugely popular not so long ago (...Wait, what? It's really been 12 years?).


[inja] add inja

Add Inja Library. It's an header only library.
https://github.com/pantor/inja

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

LGTM, thanks for the PR!


I saw Flixel Got Problem for my compile

Describe your bug here.

Command Prompt/Terminal logs (if existing)
lime test windows -debug

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Flixel Got Problem to Compile

idk do
haxelib remove flixel
haxelib install flixel

Idk what you should do since I don't know if you've edited anything.

Did you edit anything in this build? If so, mention or summarize your changes.
Flixel got problem to compile
You need to say what you've edited here if you've edited anything.


Allow release mode builds to run on simulators

Current documentation (https://github.com/flutter/flutter/wiki/Flutter's-modes) states that Flutter release mode builds cannot be run on the Simulator. For many applications, the iOS Simulators are sufficiently high fidelity to do 99% of development work without going through the additional friction of deploying to devices regularly.

The release mode behaviours should be the same in debug and release mode, except for performance (for which the simulator doesn't give you an accurate understanding anyway).

@collinjackson mentions that you might want to test other things about release builds, e.g. crash reporting.
We don't plan to support this in the near term, but I'm leaving this bug open to track the topic.

This is also important to be able to capture screenshots with Fastlane in release mode on simulators.

I also don't see a reason to restrict release mode builds to physical devices. Developers may need to test release mode builds but not have immediate access to a physical device.

Especially for developers that are on Mac and may not have an Android Phone.
Rody Davis Jr.
Full Stack Mobile Developer
Github | Website | Appstore | LinkedIn
Twitter | Facebook | YouTube
On Apr 25, 2018, 10:47 AM -0400, Jason Rai<EMAIL_ADDRESS>wrote:

I also don't see a reason to restrict release mode builds to physical devices. Developers may need to test release mode builds but not have immediate access to a physical device.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

This bit me when I was trying to get iOS screenshots for devices I do not own (like the iPhone 8 Plus).

Is there any other cross platform framework that has this restriction? I know Xamarin does not.

I guess we could replace the outright ban with a prominent warning. If anyone wants to implement that, we would definitely consider a PR implementing it.

I second that this is needed for screenshots.  In the mean time is there any way to get rid of the debug banner?  Because I don't have all the devices I need screenshots for.

https://stackoverflow.com/questions/48893935/how-to-remove-debug-banner-in-flutter-on-android-emulator

The release mode behaviours should be the same in debug and release mode, except for performance (for which the simulator doesn't give you an accurate understanding anyway).

Behaviors for applications should be the same.  However, I think that the ability to run release builds in simulators would be a big help to testing changes to the Flutter engine because the engine does very different things in the different modes.

Sometimes it happens that for fast-prototyping I don't have an apple enrolled developer account on the machine.
Without the ability to test a release build on the simulator I can't even see how much space will take the release bundle.
I'm able to do this both on Xamarin.Forms and React Native, don't see why we can't do it in Flutter.
Please make this command flutter run --release -d <ios-simulator-id> work, thank you :)

+1

It's possible to remove the debug banner by setting the debugShowChekedModeBanner MaterialApp property to false, e.g.
return new MaterialApp(title: 'MyApp', debugShowCheckedModeBanner: false,...);

@Hixie Is there anyway to have flutter compiling in release mode for the Simulator arch? Thanks

What is your use case?

@Hixie
My use case is that I've to redistribute a part of our flutter app as a native SDK.
To do that, I've basically created a thin wrapper that implements the flutter app2app plumbing to avoid exposing the flutter APIs to our client and publish Flutter.framework and App.framework as private pods on our private repo. My SDK podspec declares App and Flutter as dependencies and all the plugins are compiled as static libraries.
However, for development purposes I need to create fat frameworks with device and simulator archs. Normally we would compile all of them in release. However, it seems that release mode was explicitly blocked on the xcode_backend.sh script.
Maybe you could clarify the limitations for such restriction or if it would be possible to compile it in release mode somehow.
Moreover, the i386 arch requires us to change flutter gn to allow it to be compiled in a x86_64 machine.
Thanks in advance,

Interesting use case, definitely not something we've considered before...
The reason we haven't allowed it so far is that people tend to use it to test performance, but then they get disappointed when the performance on a simulator really has no bearing on real device performance.

I see. But Apple also has the some problems and they basically make a good statement on the fact that performance must be measured on the device. Would you guys consider to remove this restriction ? Is there any patch on my side I could do to compile for release ? Thanks

@Hixie Sorry for pushing this. Is there a way to compile flutter locally for x86_64 and i386 in release ?

Any update here ? Glad to help if someone would provide some highlights.

This feature is also important for developers who work remotely and want to present their current version / work via ScreenSharing to their clients for example.

Interesting use case, definitely not something we've considered before...
The reason we haven't allowed it so far is that people tend to use it to test performance, but then they get disappointed when the performance on a simulator really has no bearing on real device performance.

For me the reason would be testing my Flutter app in release mode without owning a physical IOS device.

Now that bitcode support is out for testing this is the remaining feature to ship iOS native frameworks with flutter. Any idea if this could be a short term priority ? Thanks.

@xster @jonahwilliams  @eseidelGoogle Is this something that was scheduled for a near future ? Is there anything the community could help with ? Thanks.

The work needing done is mostly on the engine side I suspect.  Similar to what @jonahwilliams did recently for adding support for release x86.  See PRs linked from https://github.com/flutter/flutter/issues/9253.

Any updates?

We distribute a Flutter application as an iOS framework (to hide implementation details) and this is currently quite painful because the user must use both Debug and Release builds of the frameworks because we cannot simply distribute the Release build and tell the customer to only use a real device for development. Therefore, we really would like to have a Release version iOS framework build that runs on the Simulator.

The mainly reason of what i need it is to make a video screen record. The debug version is too slow. When i use the release version "flutter build apk" on android it's look pretty great! The app is so smoothly but on ios simulator by using the debug version is too poor.

It is also not just the banner. If you have code that branches on kDebugMode, kReleaseMode, or kProfileMode, you can not run on a simulator and have the correct experience.

The release mode behaviours should be the same in debug and release mode, except for performance (for which the simulator doesn't give you an accurate understanding anyway).

It should, but sometimes they are not. I would like to know when they are not the same fast, using the simulator.

I'd like to use the IOS simulator to record parts of my app to create App Previews for my App Store listing. I don't have access to a 6.5" Iphone so the closest alternative is the IOS simulator. I don't expect performance of the simulator to be representative of real world app performance but my assumption is that it'd be suitable enough to record a few videos for this purpose.

I use flutter build ios-framework build Release And Debug frameWork. I try use lipo -create Debug/app.framework Release/app.framework. I Can Run IOS simulator but I get error and blank "[VERBOSE-2:engine.cc(134)] Engine run configuration was invalid."

Is there a solution for this ? As there are quit a times developer needs to validate things for release configuration and  its bit frustrating to not able to run it on simulator.

Hello everybody.
The year is 2021 and we're now joining the other devs suffering from this limitation imposed by the release version of Flutter.
Here it is our use case:
We have a multi module - 100% native - app. All modules are integrated as a dependency of the main app, via Cocoapods (private pods). Until now, everything works just fine. And on our CI, among other validations, the app goes through the current Steps:

Download all dependencies (pod install)
build
unitTests
UI + Snapshot Tests
Archive
Deploy to Testflight

The situation:
If Steps 3 and 4 target iOS simulators, so we can get the DIFFs for different devices and check how our app is going to look on different screens. On the other hand, for the sake of performance, Steps 5 and 6 must target only the ARM architecture (generic iOS device).
The problem:
Ever since we added Flutter as a dependency, it totally broke the current pipeline.
The main issue is that to make Steps 3 and 4 run, we have to use the Debug versions of the .xcframework generated. But the Steps 5 and 6 must use the Release variant.
The solutions:
To make it all work, we have to re-run pod install between Steps 4 and 5 to change the reference of the files we are pointing at. Or manually edit the app project file. Either solutions, terrible, slow and error-prone.
What we believe it would be the most appropriate way: Run all Steps already referencing the Release version of the .xcframework
Anyone got any tips on how to proceed on this situation?

Hello everybody.
The year is 2021 and we're now joining the other devs suffering from this limitation imposed by the release version of Flutter.
Here it is our use case:
We have a multi module - 100% native - app. All modules are integrated as a dependency of the main app, via Cocoapods (private pods). Until now, everything works just fine. And on our CI, among other validations, the app goes through the current Steps:

Download all dependencies (pod install)
build
unitTests
UI + Snapshot Tests
Archive
Deploy to Testflight

The situation:
If Steps 3 and 4 target iOS simulators, so we can get the DIFFs for different devices and check how our app is going to look on different screens. On the other hand, for the sake of performance, Steps 5 and 6 must target only the ARM architecture (generic iOS device).
The problem:
Ever since we added Flutter as a dependency, it totally broke the current pipeline.
The main issue is that to make Steps 3 and 4 run, we have to use the Debug versions of the .xcframework generated. But the Steps 5 and 6 must use the Release variant.
The solutions:
To make it all work, we have to re-run pod install between Steps 4 and 5 to change the reference of the files we are pointing at. Or manually edit the app project file. Either solutions, terrible, slow and error-prone.
What we believe it would be the most appropriate way: Run all Steps already referencing the Release version of the .xcframework
Anyone got any tips on how to proceed on this situation?

Is there any interest in pursuing this and adding support?

Sure!

Is there any interest in pursuing this and adding support?

yes

Any update for running release build on iOS Simulators ?

Any update for running release build on iOS Simulators ?

Currently in the same situation as @sma. It makes it very difficult for our clients to integrate with a simple CocoaPod workflow.

Any updates?

Any updates or at least a way to hide layout overflow errors, I just have one which ruins the screenshot.

Any update please?? This is a basic feature which should be supported. How can we test if the release is working on an iPhone 15 without the physical device regardless of debug mode?

any news?

It's 2024 and this issue is still getting ignored, after 7 years. Any workaround?

Why keep ignoring everyone, this feature would help a lot, what is the meaning of not add this command to run on ios ? Android have this, why not on ios?

currently i ran into a bug that only happens in release mode, why not allow us to test  in release mode ?

@Hixie This limitation is quite cumbersome for embedding a flutter module in release mode in another app and test on the simulator/device on iOS. Could you reconsider ? How are is this change ? Any pointer for a workaround/PR ?

This is not something anyone who contributes to Flutter regularly has said is on their radar for 2024, but we welcome contributions from everyone, so if anyone is interested in implementing this, please do feel free to do so. The main thing is we would want a prominent warning that performance in a simulator is never representative, even in release builds. If you need help getting started, check our contributing guide, join the Discord (link in the guide) and ask for help in the #hackers-new channel.

Release aar works on the Android emulator without warning so I'm not sure iOS simulator needs additional warning for the embedding use case. I found a workaround for my use case by the way:

Build the framework using flutter build ios-framework
Replace the ios-arm64_x86_64-simulator part of the App.xcframework release build with the one from the debug build.
Use the Flutter.xcframework from the release build
Run on the iOS simulator and device.

Any update on this? Causing major issues.

Any progress?

This will require config change in xcode project

FYI, as of December 2024, this is still not something we plan to work on, but we welcome contributions if anyone is interested in implementing this.  See https://github.com/flutter/flutter/issues/11754#issuecomment-1960436803


feat: extension background storage

Closes #58
Context

add background extension storage configuration
define storage keys
sync background storage with popup context

Extension builds preview

Name
Link

Latest commit
ab9126080b84ead02056cd49325b75afabfc1dd1

Latest job logs
Run #7887550848

DownloadDownloadDownloadDownload


Fix for #1267 - Link inside text for content-type without blocks brea…

…ks the site

Fixes #1276
/cc @giuliaghisini @cekk @pnicolli

@giuliaghisini @cekk @pnicolli I think now we are safe, tell me if there are any other issue.

@giuliaghisini @cekk @pnicolli I think now we are safe, tell me if there are any other issue.

i think now it's ok!


introduce immutable tags

Perhaps this could be done from CI, but for the start we can simply create and extra tag with git rev in ./publish.

FYI @2opremio


refactor

@rultor merge

@rultor merge

@driver733 OK, I'll try to merge now. You can check the progress of the merge here

Coverage increased (+0.08%) to 10.594% when pulling 2ad80953cfc72b1a7dba5cddd010c703e96da5d4 on refactor into aa4c655f059eb6d2a25de301f03695edc6d1d33e on master.

@rultor merge

@driver733 Done! FYI, the full log is here (took me 4min)


Added support for Image hover

Adds support for Image hovering which will land in bokeh 0.12.16.

Just to reference the PR: https://github.com/bokeh/bokeh/pull/7651
Now to get it merged and into 0.12.16!

Should we just merge? Don't expect there to be any API changes in your PR do you?

Should we just merge? Don't expect there to be any API changes in your PR do you?

I guess so. I'll test again once the bokeh PR is merged and a new PR can be created then if necessary.
Merging.


SSL issue: The hyperlink in the README doesn't work

Hey guys! I just tried to open https://geoviz.fusiontables-archive.withgoogle.com/ but there is a problem with your SSL certificate, hence the browser refuses to take me to the page.

Whoops.  That link is incorrect.   I'll work on correcting that.
The README should tell you to look at the ft-archive-index Sheet in Drive
which links to your visualizations.

The incorrect link is still in the README.


Use "azure/core-http" to improve ECONNRESET handling

The azure sdks have a systemErrorRetryPolicy that's supposed to automatically retry a request for errors like "ECONNRESET". However, it had a bug where it never retried. I found a PR that fixed the bug in the "core-http" package a while ago, but not the "ms-rest-js" package we had been using. I filed a bug on "ms-rest-js" to get the fix ported over, but not sure when that'll happen and it sounds like "core-http" is the newer/better version of "ms-rest-js", anyways.
Only issue was some build errors around ServiceClientCredentials, but I mitigated that with AzExtServiceClientCredentials.
Related to https://github.com/microsoft/vscode-azurefunctions/issues/2390 and https://github.com/microsoft/vscode-azureappservice/issues/1932

ms-rest-js 2.2.1 has the fix we need for ECONNRESET, so we don't need to use core-http anymore (which only helped for genericClient anyways)
I decided to keep the changes for AzExtServiceClientCredentials because it lets us remove the explicit dependency on "ms-rest-nodeauth" and I have seen typescript errors related to the credentials before.


core: embedded front end examples

Summary
Create a demo app that shows how to embed two different component trees or apps can be used within the same host app sharing core as a external peer dep. Example App:
Host app built with Angular

Feature 1
vue component wrapped as custom element
Feature 2
svelte component wrapped as custom element

Both feature 1 and 2 use Clarity Core as a peer dependency. This example demonstrates that Core can be used cross framework and be shared as a peer dep between embedded apps. Each app should also extend a Core component with a aliased tag and style it to also demonstrate isolated styles between embeds.
<!-- host app (Angular) -->
<section>
  <feat1-embed></feat1-embed>
  <feat2-embed></feat2-embed>
</section>

<!-- feat 1 template (Vue) -->
<style>
  feat1-button {
    --background: green;
  }
</style>
<feat1-button>aliased cwc-button</feat1-button>

<!-- feat 2 template (Svelte) -->
<style>
  feat2-button {
    --background: orange;
  }
</style>
<feat2-button>aliased cwc-button</feat2-button>

implemented proof of concept for internal share/use


Refactor discovery registry

Describe what this PR does / why we need it
重构并优化部分代码
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.livk seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


GLTF: Add root node export options and GODOT_single_root extension

Solves https://github.com/godotengine/godot-proposals/discussions/6588
This PR adds root node export options and a new glTF extension called GODOT_single_root.
This was discussed with @lyuma about 2 months ago, but was on hold for most of that time due to me waiting for other PRs to be merged as prerequisites (and me not wanting to open draft PRs with a long dependency chain).

(with this PR by itself, there is no export settings dialog, but it can be set through GDScript code when exporting from script, and the goal is to make this available in the export settings once that's added)

Single Root: Treat the Godot scene's root node as the root node of the glTF file, and mark it as the single root node via the GODOT_single_root glTF extension. This will be parsed the same as Keep Root if the implementation does not support GODOT_single_root.
Keep Root: Treat the Godot scene's root node as the root node of the glTF file, but do not mark it as anything special. An extra root node will be generated when importing into Godot. This uses only vanilla glTF features. This is equivalent to the behavior in Godot 4.1 and earlier.
Multi Root: Treat the Godot scene's root node as the name of the glTF scene, and add all of its children as root nodes of the glTF file. This uses only vanilla glTF features. This avoids an extra root node, but only the name of the Godot scene's root node will be preserved, as it will not be saved as a node.

The last 2 options both use only vanilla glTF features. Keep Root is the same as 4.1. Multi Root is a new feature, which allows round-tripping a scene without an extra root node, but the downside is that the root node will only ever be a Node3D because the Godot scene's root node is only being saved as a name instead of a node.
The first option, Single Root, uses the GODOT_single_root extension. This extension has no data, it is only a flag with rules and restrictions. Single Root is identical to Keep Root except that it adds this one string to the "extensionsUsed" array to mark it as the single root node. Godot will read this flag and set the glTF root as the single root node of the generated Godot scene. This flag will do nothing in implementations that don't support it, so in those cases it behaves identically to exporting with Keep Root, and exporting in 4.1 and earlier.

@aaronfranke Said he will write a proposal at the review meeting we had today.

@fire @lyuma Proposal opened https://github.com/godotengine/godot-proposals/issues/7791

@aaronfranke Do you think it'll be doable to write a gltf spec for GODOT_single_root I can present / pull request?

@fire I have already done this: https://github.com/KhronosGroup/glTF/pull/2329


Add support for multi-level directories

Currently, you can organize your gist files into directories, but only a single-level. The notion of gist directories are meant to extend the value of gists, not to replace repos, and so I'm not too sure how valuable it would be to support multi-level directories. That said, I want to track this limitation in order to get feedback from folks, and help inform the prioritization of this work.

personally, I think this would be overengineering it for gists.
I'd rather see native gistpad tagging improvement instead ... https://github.com/vsls-contrib/gistpad/issues/7#issuecomment-590961547

I’m going to close this now that enough time has passed, and no one has requested it. As was mentioned, I actually don’t think I want to add support for this, particularly now that GistPad supports managing repos in addition to gists 👍


updated iterm2-nightly (2.9.20160129)

Closes #1612.

Merged as ddfe934d97fa2dcea56c818bcce8377311be297d.


ioBroker.tado produces exceptionally high CPU load

After installing ioBroker.tado I noticed the fan of my Pi PoE HAT starting to periodically cool the CPU (which it never did before). Based on the output of htop I noticed that ioBroker.tado is producing 40 - 50% CPU load with every refresh interval.
Based on the silly log output it seems that the adapter re-creates all objects with every refresh. My tado setup is quite complex with 14 rooms and ~20 devices.
This also increases the load of ioBroker.javascript at the same time as it seems its consuming the flood of events from ioBroker.tado. As soon as I disable my instance of ioBroker.tado the periodic CPU load increases stop (also for the ioBroker.javascript adapter) and the CPU cooling ends.
No other of my (50+) adapters is producing these high levels of load.
Expected behavior
The adapter should create less load on the CPU.
Versions:

Adapter version: 0.2.6
JS-Controller version: 3.2.16
Node version: 14.16.0
Operating system: Raspbian GNU/Linux 10 (buster)

(Frankly not sure if this is bug or an improvement request)

Hi! Which interval is configured?
I / we will have a look at the state update.

Hmm i See here we have a nasty extendObject at every refresh, that’s inefficient.
https://github.com/DrozmotiX/ioBroker.tado/blob/main/main.js#L1648
sorry old piece of code, already fixed in my other adapters will take care of this one during weekend

we could reuse the implemented function in json-explorer ;-)

@DutchmanNL  we could reuse the implemented function in json-explorer ;-)

That's the one I mean 😉

@DutchmanNL  we could reuse the implemented function in json-explorer ;-)

That's the fix I mean 😉

I did a quick hack and it seems to work very fine
https://github.com/DrozmotiX/ioBroker.tado/tree/192
It just produces a lot of warnings, because stateAttr.js does not cover all states. But this is just something that has to be done ;-)

@paulheimann
If you would like to do an experimental test you can install
DrozmotiX/ioBroker.tado#082a3ab2b8119a9eb2c1907ed6c40d0ee5f18c98
like

You will get a lot of warnings like
Sentry disabled, error catched : State attribute definition missing for 'Stage_04_Weather'
but this does not impact the functionality.
Would be interesting if CPU usage decreases.

@HGlab01 @DutchmanNL, thanks a lot for the rapid response! I'm impressed.

Hi! Which interval is configured?

30 seconds, I believe that's the default which I never changed.

If you would like to do an experimental test you can install
DrozmotiX/ioBroker.tado#8cba3f19afb5654f95501786de2eda4bc4307766

I tried. What I observed: Load on ioBroker.tado goes down to 20 - 25% CPU with each update interval. The simultaneous load spikes of ioBroker.javascript seem to have gone down more significantly (~5 - 10%).
After having run ioBroker for ~1 hr, ioBroker.tado is still the sub process with by far the highest CPU time. So, while this change definitely improved the situation it still seems that ioBroker.tado is more resource hungry than it should be.

@HGlab01 @DutchmanNL, thanks a lot for the rapid response! I'm impressed.

Hi! Which interval is configured?

30 seconds, I believe that's the default which I never changed.

If you would like to do an experimental test you can install
DrozmotiX/ioBroker.tado#8cba3f19afb5654f95501786de2eda4bc4307766

I tried. What I observed: Load on ioBroker.tado goes down to 20 - 25% CPU with each update interval. The simultaneous load spikes of ioBroker.javascript seem to have gone down more significantly (~5 - 10%).
After having run ioBroker for ~1 hr, ioBroker.tado is still the sub process with by far the highest CPU time. So, while this change definitely improved the situation it still seems that ioBroker.tado is more resource hungry than it probably should be.

i will take a further look at that when I change the oAuth handling. Basically we only get a JSON and write it to states should not be a high load

Just a quick update: Kept iobroker running for more than than 24hrs with the experimental version from @HGlab01. In terms of CPU time ioBroker.tado is still by far the most hungry adapter (roughly 10x compared to the second most resource hungry one).

My Tado-Install has 216 states. Therefore it is not surprising when 200+ Events are fired every polling interval.

I'm absolutely no expert so please forgive if this is an irrelevant thought: Shouldn't events only be fired for things that actually changed compared to the last poll?

My Tado-Install has 216 states. Therefore it is not surprising when 200+ Events are fired every polling interval.

I'm absolutely no expert so please forgive if this is an irrelevant thought: Shouldn't events only be fired for things that actually changed compared to the last poll?

Hmm yes and now, there are 2 ways to do it :

(as now) let the controller handle the state behavior
(possible to do) keep the values in memory and only write if the value changed

we can make a test what's more efficient, to be honest didn't compare it yet between the ioBroker controller logic or doing ut by ourself with memory logic

In my point of view this should not be done on adapter level but on framework (= iobroker js-controller) level. And I would say the current iobroker js-controller implementation is pretty fine.
I appreciate inputs and ways how to get it more efficient and we should proceed to think how to elaborate.

@HGlab01 i Will check with the Core team about backend and planner Roadmap on These items as the value are Updates (we cam See That) question is iFrame it only Updates the State Time stamp are anwatschle the valies amd ACK too
of the Last is the case, we have 2 unneeded write actions to the state DB
@paulheimann what kind of hardware is your ioBroker running on?

@paulheimann what kind of hardware is your ioBroker running on?

Running on Raspberry Pi 4 Model B 4GB RAM

@paulheimann what kind of hardware is your ioBroker running on?

Running on Raspberry Pi 4 Model B 4GB RAM

what kind of storage ? On an raspberry pi with an SD you should really think about using Redis instead of writing on the card

what kind of storage ? On an raspberry pi with an SD you should really think about using Redis instead of writing on the card

Yes, you are right. Unfortunately didn't find time yet to switch to redis yet.

Switched to redis in the meantime. iobroker.tado (running on the version  DrozmotiX/ioBroker.tado#8cba3f19afb5654f95501786de2eda4bc4307766 referenced by @HGlab01 above) is still the process with the highest CPU consumption on my entire system (monitoring it now for a couple of days). The CPU spikes with every update interval now go hand in hand with spikes of redis.

I compared the CPU-time to other adapters:
iobroker.javascript: 5-times
iobroker.shelly (also state intensiv): 2-times
iobroker.scene: ~equal
My assessment: CPU load is ok in comparison to other adapters For sure, if adapters do not handle many states the CPU consumption is less.
I will combine this improvement and issue 214 and launch a version for latest in the next few days

If you like you can check this version. This includes all possible improvements.
DrozmotiX/ioBroker.tado#d5e9999b562c02c63c16e24c5eeb22135a787992


Rename the inspec test attribute for clarity.

Thanks for spotting that @gavindidrichsen, updating.
Signed-off-by: Stuart Paterson<EMAIL_ADDRESS>

Was a sane enough name but slightly clearer now!


spglib fails to build because of a missing dependency which is not available in the Ubuntu Repositories

Crate name:
spglib
Build failure link:
https://docs.rs/crate/spglib/0.1.3
https://docs.rs/crate/spglib/0.1.3/builds/230972
Additional details:
I tried to follow the standard procedure of adding the package to the build environment, but the dependency I need is not a package in the Ubuntu Repositories.
The dependency comes from this repository.
Is it possible that I could still add this package or is there a workaround?

As an alternative you could add the C project to the Rust crate as a submodule and compile it in build.rs before building the Rust code.

@jyn514 What if the Rust bindings are already in a subdirectory of the main C repository?

I am not sure how to do it in that case, unfortunately. Maybe you could make a hard-link to the header file and use that if the header file doesn't already exist on the system?

Closing due to inactivity; feel free to reopen if you're still having trouble and have time to work on it.


Sidebar is not scrollable: I can't access menu items at the bottom

@yivo old issue already fixed, you can close it


Add sample backup config

This adds sample backup configurations for 2 of 3 and 3 of 5. Instead of giving step by step instructions, this just shows examples and talks about what the reader needs to consider.

@mflaxman I would like some input before I mark it as ready for merging

+1 i was surprised that this info wasnt included in the guide already
why do you recommend having copies of core and specter on a usb drive stored with the wallets?

Less chances of having incompatible versions. Also, if your heirs have to
find copies of the software they may get malware instead.
It's still not simple, but anything to lessen the complexity will help
On Tue, 22 Dec 2020, 13:42 mmikeww<EMAIL_ADDRESS>wrote:

+1 i was surprised that this info wasnt included in the guide already
why do you recommend having copies of core and specter on a usb drive
stored with the wallets?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/btcguide/btcguide.github.io/pull/48#issuecomment-749351633,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAGF5EAQPGMF2KCNXOGGB3SWAWTNANCNFSM4ULUQVMA
.

@mflaxman this is ready for review

@mflaxman this is ready for review

The cobo vault requires that you set up a password, and the Coldcard requires that you set up a PIN. So both of those should be backed up somewhere as well

The cobo vault requires that you set up a password, and the Coldcard requires that you set up a PIN. So both of those should be backed up somewhere as well

Thanks. I realized this should be talked about as well.
Generally speaking, the seed, PIN/password of the device should be with the corresponding device. However, where do you suggest the seed, PIN/password for the device/s that stay with you (in your house, or on your person if you're traveling) are stored?

Thanks. I realized this should be talked about as well.
Generally speaking, the seed, PIN/password of the device should be with the corresponding device. However, where do you suggest the seed, PIN/password for the device/s that stay with you (in your house, or on your person if you're traveling) are stored?

I don't have a good recommendation. This other guide suggests to spread that information out with other seeds, but also recommends keeping a digital copy somewhere, such as in an encrypted file in the cloud, or I guess in a password manager. He calls it a "digital note":
https://github.com/DriftwoodPalace/guides/blob/master/hodl-guide/hodl-guide_50_storage.md

I don't have a good recommendation. This other guide suggests to spread that information out with other seeds, but also recommends keeping a digital copy somewhere, such as in an encrypted file in the cloud, or I guess in a password manager. He calls it a "digital note":
https://github.com/DriftwoodPalace/guides/blob/master/hodl-guide/hodl-guide_50_storage.md