Fix FieldExistsQuery on columns with index off or columnstore=false

Summary of the changes / Why this improves CrateDB
Follows https://github.com/crate/crate/pull/14527, managing it separately since this exposes bugs.
The first commit adds more variations of the test testWhereNotEqualAnyWithLargeArray combining index off and columnstore = false which exposes below two bugs:

FieldExistsQuery is counted as 1 more clause resulting in TooManyClauses exceptions. (In some cases, it does not due to rewriting)
When columnstore = false, FieldExistsQuery is used and raises exceptions:

select a from t where a != any([1,2]); -- where 'a' is an int column with (columnstore = false)
IllegalStateException[FieldExistsQuery requires that the field indexes doc values, norms or vectors, but field 'a' exists and indexes neither of these data structures]

The last two commits address the mentioned issues.
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

It would be good to expand it to cover other types too.

Hi @seut, could you have a look at this draft? The last two commits are for the two bugs described above.

Sorry but this doesn't look right at all.
Could you please give a high level description of the actual problem? How do users run into this? What is this fixing?

Since I allowed columns with index off and columnstore = false to be queryable (so far on fix-lucene-query-builder branch), I tried to expand on testWhereNotEqualAnyWithLargeArray to cover the variations which exposed two failures,

https://github.com/crate/crate/pull/14604#discussion_r1345796030
https://github.com/crate/crate/pull/14604#discussion_r1345798744

I think part of the confusion is due to the difference of FieldType and MappedFieldType.
E.g. in regards to doc-values:

FieldType indicates the type of doc-values that might be used
MappedFieldType and Reference indicate if doc-values are actually used

This means that the doc-values type from FieldType can't be used as indicator if doc-values are available. That's not a bug, that's a design choice.
See:

https://github.com/crate/crate/blob/f33cbc0ebecf42bc872c5eb2607eddd6c781155c/server/src/main/java/io/crate/execution/dml/IntIndexer.java#L71-L72
https://github.com/crate/crate/blob/f33cbc0ebecf42bc872c5eb2607eddd6c781155c/server/src/main/java/org/elasticsearch/index/mapper/NumberFieldMapper.java#L281-L289

Also please try to limit the scope of PRs. This is again addressing multiple aspects, which made it much more difficult to review.
I opened up https://github.com/crate/crate/pull/14847 to address the column-store aspect.

Thank you for taking over @mfussenegger and your explanation and commits make sense.


 Darwin 15.6.0
npm ERR! argv "node" "/usr/local/bin/npm" "i" "-D" "purify-css"
npm ERR! node v0.12.7
npm ERR! npm  v2.12.1
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package grunt does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jholtslander/Desktop/remove-unnecessary-css-with-purifycss-and-grunt-master/npm-debug.log

Trying to run purifycss after install results in:
$ purifycss
/usr/local/lib/node_modules/purify-css/node_modules/yargs/node_modules/camelcase/index.js:4
	let isLastCharLower = false;
	^^^
SyntaxError: Unexpected strict mode reserved word
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/purify-css/node_modules/yargs/lib/command.js:3:19)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)

Tried posting the log contents as requested but...

You need to have nodejs >= 5 installed
whats the output for node -v and/or nodejs -v

Helpful

Try using nvm for switching versions or nodenv. 0.12 is very old. Current versions are 8 and 9.


Close tmux window when complete?

Is it possible to have the "syntastic_daemon" tmux window close itself when syntax checking is complete? Tmux colors it red and it's slightly distracting :)

yes. you can add this in vimrc.
au RemoteReply * if expand('<afile>') =~# '^syntastic@@@@'
            \ | call remote_send(g:syntastic_async_servername, "<ESC>:qa!<CR>")
            \ | endif

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @


[Question] Do xcode groups need to be in a folder before you can create a template?

I had some trouble trying to create templates with interface builder files just like in the blog post. It wasn't until I put all the files into a folder and assigned the group to that folder that I had success. Is this the desired process in order to create template groups? If it is, I think it would be better if you could mention that in the blog post as well.
It would be great if it could function the same way without having to assign the group into a folder though.

That is intended functionality, but I'm gonna change it so that you can create from selected files, then there becomes no issue of groups or folders.
Sent from my iPhone

On 8 May 2015, at 16:41, mjjimenez<EMAIL_ADDRESS>wrote:
I had some trouble trying to create templates with interface builder files just like in the blog post. It wasn't until I put all the files into a folder and assigned the group to that folder that I had success. Is this the desired process in order to create template groups? If it is, I think it would be better if you could mention that in the blog post as well.
It would be great if it could function the same way without having to assign the group into a folder though.
—
Reply to this email directly or view it on GitHub.

latest update has modified functionality, you create template from selected files instead of from project group. please let me know how you get on :) https://twitter.com/dodsios


Localized the blog into Japanese Apr2020_2

Hi Hue Team,
As always, I localized the latest Hue blog into Japanese.
Please review it. :)
Thanks,
-- Tatsuo

Thanks a lot Tatsuo, it is live now! https://jp.gethue.com/blog/quick-task-sql-editor-for-apache-spark-sql-with-livy/


1.10 reconciler timeouts backport

workaround for TestKafkaSourceDeletedFromContractConfigMaps timeouts on cleanup
on 1.11 we backported reconciler-test https://github.com/openshift-knative/eventing-kafka-broker/commit/8feed0c277afd4a303ce52ade6d3420eb9c545e8 , but let's keep a simpler patch for 1.10

Should we backport that? or is that just something here, on older releases, @maschmid ?

we'll see, I am trying to fix the flakiness of lp-interop test with serverless 1.31, from  https://github.com/openshift/release/pull/46746  , we need the lp-interop jobs to be flake-free, so let's see if this helps. (we may need to skip it on release-v1.10 althogether is we can't fix the flakiness).


How to deprecate declarations in header files?

Deprecations in header files look like this:
DEPRECATEDIN_1_1_0(struct hostent *BIO_gethostbyname(const char *name))

This is not what doc/internal/man7/deprecated.pod says to do:
     # ifndef OPENSSL_NO_DEPRECATED_1_1_0
     /* ... */
     OSSL_DEPRECATEDIN_1_1_0 __owur int
     HMAC_Init(HMAC_CTX *ctx, const void *key, int len, const EVP_MD *md);
     /* ... */
     # endif

Are the old things going to be changed, will OpenSSL continue to have two ways to signal deprecation, or should the "new way" quoted above just be removed?

Ping @levitte and @paulidale who wrote/reviewed #13074.
I also question the utility of adding seven macros (the _FOR ones) that aren't used except internally.

And none of the new OSSL_DEPRECATEDIN_ macros are used anywhere except in the header file.

Ping @levitte and @paulidale who wrote/reviewed #13074.

  I want to see that stuff mature, and I expect the deprecation efforts to be the arena where this is tested out.  For example, I'm converting all the RSA deprecations to the new form in #13167.
(@mattcaswell, I'd like to encourage you to do the same in #13138)

I also question the utility of adding seven macros (the _FOR ones) that aren't used except internally.

I think we should use them more, and I admit I haven't really started yet, but the RSA deprecations in #13137 could absolutely be of this form (just picking an example out of many possible):
DECLARE_ASN1_ENCODE_FUNCTIONS_only_attr(OSSL_DEPRECATEDIN_3_0_FOR("please use OSSL_ENCODER instead"), RSA, RSA_PUBKEY)

For example, I'm converting all the RSA deprecations to the new form in #13167

Can you show me where?  I didn't find any in a quick review but maybe it's not there yet.
(Not surprisingly, having two ways to do the same thing is sub-optimal IMO.)

For example, I'm converting all the RSA deprecations to the new form in #13167

Can you show me where? I didn't find any in a quick review but maybe it's not there yet.

Argh, wrong PR number, should have said #13096!  In there, scroll down to include/openssl/rsa.h

(Not surprisingly, having two ways to do the same thing is sub-optimal IMO.)

Depends...  there are other factors, like nudging others in participating in the change, which also helps re-calibrating their muscle memory.  Or so I hope...

(@mattcaswell, I'd like to encourage you to do the same in #13138)

It's not clear to me....why do we need a new way of deprecating things?

It's not clear to me....why do we need a new way of deprecating things?

I've argued for it in #13074.  Keywords: "more like C", and "consistency"

It's also less annoying to add to functions :)

When adding a new way of doing things, the old way should have been converted. Unless someone takes this up, you'll be burdened with two ways of doing things for years :(

When adding a new way of doing things, the old way should have been converted. Unless someone takes this up, you'll be burdened with two ways of doing things for years :(

There's absolutely nothing stopping us from doing a conversion of what DEPRECATEDIN_x_y_z just before releasing beta 1.

Yup, there's nothing stopping anyone from doing the conversion. Let's see if it happens.

Closing this. I had a look but couldn't find any of these old style deprecations any more.


Firefly won't accept my PIN

Issue description
I have tried to log into my Firefly account to check my IOTA which I normally do most days but it won't accept my PIN. I have tried it several times but no joy. I will try again tomorrow.
Firefly version
1.2.0 IOTA Foundation
OS details
Windows10
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue

Clicked onto my profile
Entered my PIN
Keeps saying incorrect PIN
...

Expected behaviour
I expect to be logged into my IOTA account
Actual behaviour
Not being allowed to log in
Errors
No response

@Freyabelle have you recently changed your pincode or password?

Thanks, think this is possibly related to another issue. But as you are all sorted I will close this one.


Bower release 0.3.0 is missing

Won't be able to install latest legacy release 0.3.0.
Please add a new release:
https://github.com/angular-ui/angular-ui-router-bower/releases

Hey all, try now.  Just pushed 0.3.0 to bower.


[WIP] Replace rockylinux witf chainguard/wolfi-base

add wolfi-base-cpu image
debug: do not publish image

Summary

Test instructions

We don't need to install xz explicitly, since py3.11-pip installs it for us
#10 2.047 + apk add py3.11-pip mesa-gl glib cmake
#10 2.246 (1/41) Installing libattr1 (2.5.2-r1)
#10 2.456 (2/41) Installing libacl1 (2.3.2-r1)
#10 2.698 (3/41) Installing libbz2-1 (1.0.8-r7)
#10 2.748 (4/41) Installing libexpat1 (2.6.2-r1)
#10 2.799 (5/41) Installing liblz4-1 (1.9.4-r4)
#10 3.166 (6/41) Installing xz (5.4.6-r2)

https://github.com/Unstructured-IO/base-images/pull/20#issuecomment-2149487254


[🐞] useTask$ doesn't behave the same with Link navigation

Which component is affected?
Qwik Runtime
Describe the bug
AFAIK, useTask$ should run in the same deterministic way whether it's server rendered or client rendered.
But it doesn't run in the same order when it runs during client side rendering (using Link or "show/hide" logic)
Reproduction
https://stackblitz.com/edit/qwik-starter-hjsrfx?file=src/routes/page1/tabs.tsx
Steps to reproduce

Click on Page 1 - Go here first

Look at the right order of tabs index numbers -

Click on the link Page 2 - Click Here

Click on the only link on the page

Look at the wrong order of index numbers

The "problematic code" is located the page1/tabs.tsx file, just search for useTask$
(If I change it to useVisibleTask$, it works, but with a flicker, obviously)

System Info
(From Stackblitz)

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @builder.io/qwik: 1.0.0 => 1.0.0
    @builder.io/qwik-city: ^1.0.0 => 1.0.0
    undici: 5.22.0 => 5.22.0
    vite: 4.3.3 => 4.3.3

Additional Information
The "problematic code" is located the page1/tabs.tsx file, just search for useTask$
(If I change it to useVisibleTask$, it works, but with a flicker, obviously)

sibling run in parallel, in SSR is deterministic because there is not lazy loading

Thanks
This problem doesn't occur when using useVisibleTask$ by the way, but that comes with an annoying "flicker"
Do you have any suggestion of how we could solve the problem of syncing up sibling child components? (like in this case, tabs + their content)
Few options we thought of -

Having it not behave in parallel on the browser (make it the same as in SSR)

Adding a value prop (only in our library) where both components (tab + content) that point to the same unique value (which will work but wil make the API more verbose)

Having some kind of an API to query child components (like we discussed in the past, a hook that gives you like an observer of project child components), that way we'd know their actual index on the DOM.

using querySelector (but that will require useVisibleTask$ again)

it also executes in parallel in SSR, but there are no promises, no lazy loading. Looking into some code to make this more determinisitc in cases like this

OK thanks @manucorporat ! 🙏

Not sure this should be open - isn't this by design? You can't count on the rendering order, you should use the signal dependency graph instead.

I am having similar issues. Everything works fine whenever I load the page; however, when I go to the page through a Link, the loading order is all messed up and the page won't load correctly.

@Dindaleon depends, can you share some code

@Dindaleon That's not possible if a component stays mounted. The order of task execution is only in code-order the first render, after that it depends on tracked signals.
So unless you're seeing incorrect ordering in newly mounted components, it's expected behavior.
I'm closing this issue as it's behaving as expected, but if you do find a bug please open a new issue with a minimal reproduction.

BTW - the solution for the ordering of tabs in Qwik UI is using an Inline Component, which has access to the children, and providing them with index props before passing them to the Qwik Component.


Filtering fields with double '_' in Internet Exchange Peering Session List API

Hello,
hopefully I use the correct category of issue for this. Using the API to retrieve Internet Exchange peering lists I wanted to filter with the Internet Exchange ID. My code did not work as expected until I noticed that the field name that should be passed to the API is internet_exchange__id (notice the double underscore in the field name).
The same is true for other fields like autonomous_system__id or autonomous_system__asn
Proposed Changes
I think the filter field names should be changed to include single underscores to avoid bugs in the API usage.

This is actually not a bug but a feature. This is the way django-filters knows how to find which part is the model and which part is the field of the model. This behavior is internal to django-filters and cannot be altered or at least won't be because I don't intend to rewrite a filter mechanism on my own :D

Thanks for the info, I can consider that the API is steady as it is then :)


Aurora - BetterDocs - [Issue Report]

Changes all server icons and people in servers icon but leaves friend icons alone

april fools


Create SECURITY.md

No code changes, the purpose of this PR is just to introduce a very basic vulnerability disclosure policy / security policy to the repo.

@daveqnet, we should add the security team as CODEOWNERS of this file.


"Could not build the precompiled application for the device."

Been working in Flutter going on two years now. Love it.
Admittedly, however, I'm coming from the Android side and have never worked on the iOS side until today.
Ok, and so I tried running my app on a Macbook today and got the following results.
I haven't a clue what to do next. Any insight would be appreciated.
Going back to school on this one--took me a half-hour to work the Macbook's Finder.

[✓] Flutter (Channel stable, v1.17.3, on Mac OS X 10.15.5 19F101, locale en-CA)
    • Flutter version 1.17.3 at /Users/gregperry/Projects/flutter
    • Framework revision b041144f83 (10 days ago), 2020-06-04 09:26:11 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/gregperry/Library/Android/sdk
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2, Build version 11B52
    • CocoaPods version 1.8.4

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Community Edition (version 2019.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 34.0.4
    • Dart plugin version 191.6183.88

[✓] VS Code (version 1.32.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.25.0

[✓] Connected device (1 available)
    • Greg’s iPhone • 790231423ae297eb332cfbb9d02ec90f023e1588 • ios • iOS 13.1.2

• No issues found!

Hi @Andrious
This platform is not meant for assistance on personal code.
You may want to look at this docs
Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Update autorest.typescript to use @azure/core-http and @azure/core-arm

Updating autorest.typescript to use core-http, etc will enable us to regenerate ServiceClient code for all management and data plane libraries.

[x] Update generated dependency references for @azure/core-http and @azure/core-arm
[x] Update expected test output so that tests pass (find/replace in many generated files)
[x] Ensure generated examples in README.md are generated with the correct imports
[x] Ship major version bump due to breaking changes -- OR investigate smoothing over possible breaking changes for users

This was finished in Sprint 155 via https://github.com/azure/azure-sdk-for-js/issues/4223.


[QUESTION]:Upgrade or fresh install?

How can the Team help you today?
Decide what is best method for updating drivers.
Details:
Current csi-unity driver: v2.10
Desired csi-unity driver: v2.12
Our environment is disconnected.  We used the offline installer method originally.
Should we uninstall and install?  or Upgrade?

You can perform the upgrade using the instructions provided at this link: Dell CSM Offline Upgrade Guide .


The error of the Figure 7: Estimated geographic distribution of SA-1B images.

Taiwan is a territory of China. Please replace image 7 with the correct world map image！！！

They still used the misleading world map in SAM2. This is too provocative. This is a disrespect for China's sovereignty. The authors should correct all incorrectly used maps.


Add dependencies prop to FastField

🚀 Feature request
Current Behavior
Formik FastFields will block updates unless a change was made to the slice of Formik state that is related to that field.
Desired Behavior
Allow FastFields to specify additional slices of Formik state they depend on.
Suggested Solution
Add dependencies prop to FastField to specify other dependencies in the same form.  In shouldComponentUpdate, check for changes to the other listed slices of Formik state.
Consider an example where we have a form with two fields, for job title and specialization.  Upon selecting the job title, and the options for selecting a population are populated.  The implementation
of this example would look something like this using the proposed dependencies prop.
<Form>
  <FastField name="job-title">...</FastField />
  <FastField name="job-specialization" dependencies={["job-title"]} />
</Form>

Who does this impact? Who is this for?
Keeping large forms performant is a difficult problem to solve.  FastField can take us a large part of the way there, but it isn't usable in two scenarios:
a.) Form Field body depends on other formik values
b.) Form Field body depends on state external to formik
This change would effectively solve most common a.) scenarios because, in these cases, the dependency typically is consistent and known.
Describe alternatives you've considered
As far as I am aware, this is the only way to solve this problem at a library level.  Without this feature, one must write a wrapper component, put it directly within the Field component, and implement the shouldComponentUpdate method there.  This assumedly is less performant than the library solution because the Field render logic will still occur, but the difference may be negligible.
If there aren't any objections, and others agree this would be valuable, I would be happy to submit a PR adding this feature.

Any update on this? Sounds exactly like what we need!

I would love this

Still really needed


Update centos-7-from-iso.json

Old link doesn't exist anymore. Found a link that does.

Thank you @dylanmpeck!

Looks good! Thanks again @dylanmpeck.


Request: PLEASE make a repo wiki for all of the rules!

I've looked at the rules for Linter multiple times to try to figure out what the plugin can do, but its too damn long, it's easy to lose my place in it. Even though there are sections listed in the readme, that's long too and I'd rather not have to switch back and forth between tabs of windows. A wiki with a sidebar for contents and collapsible sections would be VERY helpful.

This is an interesting request. I am not the most familiar with how to set a wiki up for a git repo. There are several limitations to take into account with it:

How would the wiki be hosted?

If it is hosted via github, are there any limitations?

How to maintain the wiki (i.e. a simple script for markdown to html/JS or something else)?
This repo is maintained by non-owners of the repo, so does that pose a problem for creating a wiki?

Those are the main things that need sorting out before a wiki would be possible.

Looks like so long as I have the ability to update repo settings, I could host a static wiki with just html, css, and JS. I might be able to do something more complex, but that may also not be feasible.

Oh I thought you'd know that GitHub has a wiki feature to host wikis right on the repo. If you do so, a wiki tab will show up at the top between "projects" and "security." That should be much easier to maintain and collaborate on with contributors than other wiki solutions.
https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis
https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages

Oh I thought you'd know that GitHub has a wiki feature to host wikis right on the repo. If you do so, a wiki tab will show up at the top between "projects" and "security." That should be much easier to maintain and collaborate on with contributors than other wiki solutions.
https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages

The problem with a wiki like that is that you have to manually setup the pages and it is not as easy to maintain from my experience. I would rather host the wiki via Github and have the files exist in the repo itself since that allows for easier maintainability from a dev perspective.

Oh I thought that would be easier. I'm not familiar with GitHub wikis myself. Would you want to do research to get a best of both worlds, where you can have the wiki section, and have it hosted? However it shows here that a wiki would be its own git repo: https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.wiki.git, idk if that's a compromise you're okay with.
If that's not ideal, would you know if its possible with Docusaurus? That seems popular among Obsidian plugin projects. Have you thought of using documentation software like that?

I am looking into hosting the wiki via github. It would be like the one for obsidian dataview: https://blacksmithgu.github.io/obsidian-dataview/
Assuming I have the permissions to set that up on this repo.

I see, and Dataview hosts the docs right on their repo.

It looks like the problem with that is I do not own the repo, so I cannot actually do that at this time. I will need to reach out to the owner of the repo and see how he wants to proceed.

@platers , what do you think about hosting a wiki like dataview does: https://blacksmithgu.github.io/obsidian-dataview/
I believe that requires a change in the settings of the repo, but I am not entirely certain. I can see about asking the maintainer(s) of that repo to see what settings need to be changed to get it working if we are fine with going that route.

Sounds good to me, do you just need me to turn on github pages? Happy to do that when its ready

Sounds good to me, do you just need me to turn on github pages? Happy to do that when its ready

All that would need to be done would be to turn on github pages and set the branch to gh-pages if I am seeing things correctly. However it looks like I need to set a decent bit of things up first. It will probably not be something I can get to in less than 3 or so weeks, so I will let you know once things are ready for it to be turned on.

Ok sounds good!

Saw that the github wiki is actually a repo itself as well. This is something that may be better and take less work to create. It would not be indexed for search engines, but that should be fine. It would just require a CI change for when releases are created. I am still a bit hazy on how that works since it looks like it needs the github cli to do locally since I don't own this repo. But I will have to research the 2 approaches down the road.

I have not forgotten about this. I just have not made this a high enough priority yet. I would like to be able to get this done this release, but it may be a release or 2 yet since I am about to have a week or so with little time to work on the Linter.
I need to think more about how the doc site would be setup and then decide from there on how to move forward from there. So far I am not thinking of a very good way to do the layout unless the built in themes do a good job handling filtering down to the proper rule level on search.

Looks like you cannot easily search for things in the github wiki setup.

mkdocs makes the most sense from my perspective as the route to go for the documentation as it has a pretty good search setup and allows me to add the documentation quite nicely. I am still working on a format add adding info, but I hope to finish the setup for it in the next couple of releases barring it being a quick addition.

Here is a rough idea of what I plan doing:

The examples for rules can be expanded and closed as needed. By default they are hidden. This is something that can be changed. It may be better to do this at the examples level rather than doing so for each individual example.

I wanted to put the proof of concept out there in https://github.com/platers/obsidian-linter/pull/730 . It currently needs a decent bit of work which I cannot get to in time before I head out for over a week, but it should be a good start to the logic around the site.
The following are things that definitely still need to be done:

Add an icon for the site
More information for the overview page

Just so you know I will keep reading updates, it just looks like there's nothing else for me to do.

For an icon, look into creating or using an icon from https://www.svgrepo.com/vectors/curly-brackets/ and https://www.svgrepo.com/vectors/markdown/.

Here is a good online SVG editor: https://mediamodifier.com/svg-editor#

I pushed an update. I believe it is almost ready for merging with master. I just need to look at the new documentation again after I get back in like a week. After that, the value being merged the following would need to be done:

Update rule links in plugin to point to new documentation site
Add a CI workflow on releases for deploying documentation updates
Update README documentation
I am probably not thinking of something as well.

The documentation portion has been added along with a workflow to allow it to publish on release. It should be almost ready for use. I believe that after the next release we should be able to swap over to using it.
So far here are a couple of things we will want to have in place to allow the workflow to work @platers :

Set the permissions for github actions to allow read and write so publish can work

After the next release, we will need to go into the settings for this repo and go to the pages section. There we need to set the branch to use for the github pages to be gh-pages. The site name that we will want to use should be obsidian-linter.

Then once that is in place, I can swap over the in app links to the new site and then slim down the README to make it easier to digest.

Sounds good, looks like the repo already has those permissions set.

@platers , we should be good to go into the settings for this repo and go to the pages section. There we need to set the branch to use for the github pages to be gh-pages. The site name that we will want to use should be obsidian-linter.

 I really appreciate the time you guys took to ship this. Should I close the issue now?

Its now live at https://platers.github.io/obsidian-linter/

Thanks @platers!

 I really appreciate the time you guys took to ship this. Should I close the issue now?

This site still needs some work when it comes to integrating the app and the readme with the site. Once that is done, I believe that the answer is yes. But for now we should keep the issue open.

Here are the remaining things that need to be done to close this issue:

[ ] Update getURL on rules to link to the new wiki
[ ] Update the README to be slimmed down and reference the new wiki
[ ] Decide what to do about the contribution docs (likely just reference from the README to the new wiki)

This should be complete. We may want to add more info to the README in the future, but for now I cut it down. I believe the changes should take care of most of what remained. The wiki should be the main source of info for the plugin itself moving forward. The contributing file has been moved to the wiki and should be referenced there.


Switch from Differ to HTMLDiff gem for article update email

Differ wasn't behaving well when parsing html & many changes. HTMLDiff gem appears to work better.

https://www.pivotaltracker.com/story/show/113457159

@divoxx @brupm @jeyb hopefully the last one for this story :)

:+1:

ready for deployment


WFLY-3854 move to latest javassit and some cleanup

@ctomc Please identify the components that use javaassist and @ ping their component leads asking for review/approval. Thanks.

@scottmarlow can you sign off on this

Hibernate ORM 5.3 will default to ByteBuddy, however, Hibernate ORM 5.1 still uses the older Javassist version.

@scottmarlow are you saying Javassist 3.22.0 will not work with Hibernate 5.1.x? Why is this different from another minor upgrade?

Retest this please

we should at least run the Hibernate ORM 5.1 unit tests with the newer javassist version.  Perhaps someone has done this already but I will do it locally as well.

@kabir I tried running the Hibernate 5.1.x unit tests with Javassist 3.22.0 and they pass, which is encouraging (not surprised since Sanne did the same testing before).  In the past, Javassist minor upgrades have included  changes that caused Hibernate regressions, which is one reason why the Hibernate ORM team is cautious about upgrades like this.
@gbadner @sebersole @Sanne any feedback on Javassist 3.22.0-GA being used with Hibernate ORM 5.1.x in WF12?  We would like to decide today.  Thanks!  If problems occur, we will either fix them or bring back Javassist 3.20.0-GA

@scottmarlow aren't you the person maintaining Javassist?
I'll run the ORM 5.1 build with 3.22.0-GA once again, but it would be nice to also have a thourough changelist of Javassist.

@Sanne I don't currently have time to learn the javassist internals.  Chiba does the releases and I help push them to maven central.  Is https://github.com/jboss-javassist/javassist/compare/3.20...master what your looking for?

I don't currently have time to learn the javassist internals

I didn't ask you to learn it? I asked if you were the person maintaining it, as I thought you were.
Anyway, I just run the ORM 5.1 and the Hibernate Search testsuite using 3.22.0-GA and found no issues.
Let's wait for the opinion of @gbadner @sebersole as well though.
IF they agree with the upgrade, I'd like to upgrade the ORM 5.1 branch as well. It's not good that WildFly uses a different set of dependencies than the set we regularly test for.

It's FF today, shall we put it in? We still have 2 weeks till the final cut to pull it away.

Agreed, let's merge it. I don't see any problem with it, if I stand corrected by Gail or Steve we'll revert but I think that's a very unlikely case.

Since you already verified that it works.. fine with me
On Wed, Feb 14, 2018, 6:22 AM Sanne Grinovero<EMAIL_ADDRESS>wrote:

Agreed, let's merge it. I don't see any problem with it, if I stand
corrected by Gail or Steve we'll revert but I think that's a very unlikely
case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wildfly/wildfly/pull/10646#issuecomment-365591494,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOUE4mTiV79BQzBX9TSJ7uISY3z2AOYks5tUtAZgaJpZM4QWhjw
.

Sorry for being late to the game on this. I'm going to run japi-compliance-checker on the two versions and see if any changes affect Hibernate.

@gbadner Feel free to do that, but I'm not sure if that's useful? We already know that the APIs we use are compatible, as the project compiles when replacing the version.

Ah, OK. I won't bother then.


Add map-empty and map-null attributes to the Field tags

This would be great because sometimes we want to set field specific behaviour

may u provide a method in Mapper that can map not null fields global, Mapper.mapNotNull(),For the same bean ,sometimes need map null field,sometimes need map not null field. we have to config two  for each Bean


Add licence

hey, I just saw that this repository have no licence
I think it would be nice to add one, so that people can modify and run the scripts themselves if they need to.  Usually I use Apache 2.0 for all my repos, so will stick with it for this repo as well. Fixed in c21d6db - thank you for noticing!

Thanks ! :D


v0.16.0 is adding extra lines in long listing mode

Hi,
Since v0.16.0, when long listing, lsd is adding extra lines when a single line is wider that the console's width.
behavior of lsd v0.15.1

behavior of lsd v0.16.0

This has been fixed by https://github.com/Peltoche/lsd/pull/289
Will be available in the next release.


feat: support fetch headers and transactions

Changes

Add rpc methods

fetch_header
fetch_transaction
remove_headers
remove_transactions

Add SendTransactionsProofProcess handle SendTransactionsProof message
Add tests

Codecov Report
Base: 34.92% // Head: 32.81% // Decreases project coverage by -2.11% :warning:

Coverage data is based on head (ae98bba) compared to base (72d4c96).
Patch coverage: 12.57% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #70      +/-   ##
===========================================
- Coverage    34.92%   32.81%   -2.12%
===========================================
  Files           22       23       +1
  Lines         3545     3834     +289
  Branches       515      571      +56
===========================================
+ Hits          1238     1258      +20
- Misses        2188     2457     +269
  Partials       119      119

Flag
Coverage Δ

unittests
32.81% <12.57%> (-2.12%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ocols/light_client/components/send_blocks_proof.rs
0.00% <0.00%> (ø)

...rotocols/light_client/components/send_txs_proof.rs
0.00% <0.00%> (ø)

src/protocols/light_client/mod.rs
11.90% <0.00%> (-3.80%)
:arrow_down:

src/subcmds.rs
0.00% <0.00%> (ø)

src/service.rs
50.30% <4.44%> (-4.26%)
:arrow_down:

src/protocols/light_client/peers.rs
32.53% <20.83%> (-8.28%)
:arrow_down:

src/storage.rs
84.53% <33.33%> (-2.72%)
:arrow_down:

...otocols/filter/components/block_filters_process.rs
64.70% <50.00%> (ø)

src/verify.rs
52.63% <85.71%> (ø)

... and 2 more

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

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

The "always_success" binary in CKB is smaller than the one in this PR.


default.config cleanup

Dataverse upstream defaults to a site URL differently to our default.
Think about how to provide the correct site URL automatically for cases we use Ingress.
This should be working on demo, dev and production environments.
This doesn't seem to be possible right now within Kubernetes, only by using Helm templates.
(Most likely static setting them in a persona is the wrong way, as it might differ from what the user is using.)
This is relevant for sent mails, but also for things like integrations with external services, etc.

In the same go, we should think about removing $HOST_DNS_NAME and use $dataverse_fqdn instead. Less confusion, less moving parts.
Remove ADMIN_PASS from default.config. This is contraproductive when the docs tell people not to put password there - it should be avoided for a clearer message.

The dataverse.siteUrl setting is subject to change upstream, see IQSS/dataverse#6636.
We should not mess with this until it's sorted out upstream.


Blog section read button alignment not proper

button in blog section get overflow from the box

@akshitagupta15june  please assign me this issue under ggsoc. I want to work on this issue

@akshitagupta15june, I noticed a button in the blog section seems to be overflowing from its container. I think I can fix this by adjusting the button size or the container width. I'd be happy to take a look and improve the layout! Would you be open to assigning this to me under GSSoc'24?


Fix of model_dims inside model

There was bug when dims and model_dims were different which this fix should solve.
Also changed recon loss to be between decoder output and input (instead of input embedding).
Misc. change to get rid of mutable default argument, just to be safe.
P.S.: Training the model looks good and converges.

@jidno oh already! thank you Theo for testing it out so soon! 🙏

@jidno in the limitations section of the paper, they said that convergence is sensitive to the learning rate

@jidno in the limitations section of the paper, they said that convergence is sensitive to the learning rate

@lucidrains Just tested at three learning rates, 1e-3 which didn't converge, and at 1e-4 and 3e-4 which converged at similar loss values where 1e-4 got the better results.

@jidno what sort of data are you training on? is it something with a time component?

@lucidrains yep, 3D motion

@jidno nice! 🚀


Show author information on post

Show author information on post using people metadata

특정테마의 layouts 을 오버라이드. https://github.com/jekyll/minima#layouts


Trigger callback on read exceptions

Maybe I'm approaching this the wrong way, but I'm trying to stream NMEA data from a network device. For this I'm using a TcpClient whose GetStream() I feed to NmeaParser.StreamDevice. My problem is that since the StreamDevice is doing all the reading I have no way of knowing if the connection is dropped.
I think I can enable TCP keepalive and poll the TCP client for connectivity, but it would be neat if the library can propagate exceptions when reading data so we can have a bit more graceful error handling. Unless there's a better way to do this.

For this scenario what I've typically done is create a new custom Stream class that has your stream inside it and forwards the read calls but also monitors bytes getting through and after a set timeout restarts the stream.

@dotMorten That makes sense. Thanks!


Implement min_num / max_num on ListBlock

Includes both server-side and client-side validation.
Fixes #5300 and #2379; supersedes #3914.

Merged in f98bd6870d4d60803a91578b598cb704c490c3f5


Why does MCMC sampling take so much time here?

Even acquiring 50 samples can take ages for GPyOpt.
Why is that the case? Is sampling not parallelized?
Or does n_samples mean something like the number of repeated MCMC sampling sequences?

@javiergonzalezh Is GPyOpt using GPy's HMC or Metropolis-Hastings for MCMC sampling of GP hyperparameters?
btw, PyMC3 is using Theano as a backend to speed things up.

It is using HMC that and averaging the acquisitions with respect to the
samples. You can have a look to this
http://nbviewer.jupyter.org/github/SheffieldML/notebook/blob/master/GPy/sampling_hmc.ipynb
notebook to check the details.
Hope it helps!
On 25 April 2017 at 18:24, Reinier Maat<EMAIL_ADDRESS>wrote:

@javiergonzalezh https://github.com/javiergonzalezh Is GPyOpt using
GPy's HMC or Metropolis-Hastings for MCMC sampling of GP hyperparameters?
btw, PyMC3 is using Theano as a backend to speed things up.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SheffieldML/GPyOpt/issues/88#issuecomment-297104118,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGiS864SyhEMDkB4NxumpG8ynxCtkQRWks5rzixFgaJpZM4NFsyL
.

Okay thanks! Right now, on my fastest workstation default HMC on a GPRegression model takes over 10 minutes to complete for just 50 samples. Don't really understand why.
I might write some HMC code using PyMC3 for my own purposes. Perhaps I can file a pull request later if I have time.

Cool! I'd be great if you could use a pull request with that! Thanks for the interests!

This is because the default setting skips 100 samples for burn-in and takes 100 samples (10 samples for model with 10 interval), which are 200 HMC samples in total. With the default 20 leapfrog steps setting, the HMC sampling requires 4000 gradient steps. That's why it is slow.
Of course, you could always tune the HMC parameters to make it perform better for your problem.


async job example

Hi,
I tried adding the async example as a test case, see https://github.com/larshp/microjob/commit/5dd6c7b5bdf6110c59fe88cf476b15583906877e
It gives Error: __awaiter is not defined, am I doing something wrong, missing any black magic?

Good catch!
I think this bug has been introduced during the TS refactoring.

This problem is related to TS: the worker thread is run-time JS and it gets some JS-compiled from TS.
However, when you compile an async function via TS, you'll get the __awaiter wrapper that's not defined inside the worker thread.
I'm trying to figure out how to pass all the compiled TS and not just a little part of it.

After further investigation, I think I need to rewrite microjob back to JS, leaving just the typings definition.
Unfortunately, the function in charge of wrapping the async job is created at run-time and this does not fit with TS compilation.
As explained here: https://basarat.gitbooks.io/typescript/docs/async-await.html the compilation of async functions is done through generators and that just does not work with native await keyword.
Having a mix of run-time JS and compiled TS is basically bad.

Not really? __awaiter is made because TS async/await to be usable by versions of node that don't have it. In my experience setting target to es2017 works for this sort of thing.

Also this package requires an experimental part of node anyway. We might as well compile TS to the latest version of JS.

@ddwwcruz great suggestion!
Fixed in version v0.3.1 (just shipped) 🎉


Upgraded to work with Terraform >= 0.12

Removed duplicated usage of terraform_validates, as params for this
method changed.
Updated documentation to reflect working state for 0.12

Would be neat if this could be merged!

Thanks @krzyzakp !
v1.14.0 has been released.
PS: There is a support for Terraform 0.12 in terraform_docs hook now.


Speed up bubble resizing, zooming, panning (easier redraw function)

I am going to make a lighter function that would redraw bubbles using stashed data and without requesting data from the model if only scale range is changing
Resizing, zooming, panning, should get faster
@arthurcamara1  did you have any comments on it?

Ok, some improvement was achieved. However, the performance still does not seem to be the optimal.
Consideration: clearHighlighted is very expensive for some reason. It was taking 8ms of execution alone. Removed it from zoomer, which brought back bug #175 (we have now to fix it in some other way)
Result: execution time improved from 48-54ms down to 6-21ms on my browser.


upgraded to the latest SDK

Upgrading for Windows 10 19H1.
Also adding app.manifest as per
https://github.com/windows-toolkit/Microsoft.Toolkit.Win32/issues/76#issuecomment-473943028

 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: virzak sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Ask for adding switching theme support

The support for a white theme is lacking.

Wakapi is not gonna feature a light theme, sorry.


Refont of FAQ section

Description 📹
Loom: https://www.loom.com/share/ff249906156e4977b17c70e74f256325
We made various design-only adjustments to the FAQ section, but the functionality remains the same. We placed the title at the top and added a subtitle. We also adjusted the text size, changed the divider color, and reduced the padding.
Old section:

New section:
https://www.figma.com/design/S1UKYgWewNqNHZFAaBUilG/%F0%9F%8F%9D%EF%B8%8F-Starknet-ID?node-id=3555-6782&t=x8xvLBhT37BVQyXF-1

Proposed Actions 🛠
Here’s a checklist of actions to follow for resolving this issue:

Fork and Create Branch:
Fork the repository and create a new branch using the issue number:
git checkout -b fix-[issue-number]

Run Tests and Commit Changes:
Make sure your changes don't break existing functionality and commit with a clear message:
git commit -m "Fix: [Short description of the fix]"

Required 📋
To keep our workflow smooth, please make sure you follow these guidelines:

Assignment: Don't create a pull request if you weren’t assigned to this issue.
Timeframe: Complete the task within 3 business days.
Closing the Issue: In your PR description, close the issue by writing Close #[issue_id].
Review Process:

Once you've submitted your PR, change the label to "ready for review".
If changes are requested, address them and then update the label back to "ready for review" once done.

Testing: Test your PR locally before pushing, and verify that tests and build are working after pushing.

Thank you for your contribution 🙏
⚠ WARNING: Failure to follow the requirements above may result in being added to the OnlyDust blacklist, affecting your ability to receive future rewards.

Hey @Kevils can I hop on this one

Can I get this issue assigned?
MY workflow:
First will start inspecting the FAQ section on the codebase and understand its css properites and then making changes as per the requested changes and moreover its responsive on every devices and ten at last testing it and finally making a PR.
ETA=24hours

Can I try solving this issue?

Mind if I take this issue?


Fixes

Hello @anilahir thank you for this module! I have done some bug fixing here, as well as refactoring a little and adding a little bit more API coverage. Please review the individual commits to better understand what has been addressed, and let me know if you have any questions.

Hello @anilahir thank you for this module! I have done some bug fixing here, as well as refactoring a little and adding a little bit more API coverage. Please review the individual commits to better understand what has been addressed, and let me know if you have any questions.

Thank you @jonom :)

Thanks for the quick merge!

@anilahir thank you for tagging a release, it doesn't seem to have made it up to packagist yet though - would you be able to set up a github hook?

@jonom already added GitHub hook but It's deprecated
It's fixed now. Please check again & let me know if anything missed

Looks great, thanks again!


Pull log files to local machine for analysis

Pulls log files from remote drive to local drive using SFTP. Remote drive currently defaults to neurodoor, so same-day analysis would not be supported.
A modified version of this script would be needed when files are deleted from neurodoor for long-term storage, but it was felt that

(a) it's useful to have a way to get the files from neurodoor, since that sits in a sweet spot between recency and scope, and
(b) it would be good to get this checked in before something happens to my laptop.

Same comment as Brandon: why not use "scp sp1022@neurodoor.nmr.mgh.harvard.edu:/autofs/nas/neurobooth/data/*/system_resource.log ." for example to copy all system_resource files?
Also if I type my password as an argument it is now stored in my bash history, which I am not sure how I feel about.

Same comment as Brandon: why not use "scp [sp1022@neurodoor.nmr.mgh.harvard.edu](mailto:sp1022@neurodoor.nmr.mgh.harvard.edu):/autofs/nas/neurobooth/data/*/*system_resource*.log ." for example to copy all system_resource files?
Also if I type my password as an argument it is now stored in my bash history, which I am not sure how I feel about.

Good point about the bash history. Could use SSH key as opposed to password.

Same comment as Brandon: why not use "scp sp1022@neurodoor.nmr.mgh.harvard.edu:/autofs/nas/neurobooth/data/*/*system_resource*.log ." for example to copy all system_resource files?

Here is the rsync command I would use:
rsync -amP --include "*/" --include "*.log" --exclude "*" $MGH_USER@$NEURODOOR:/autofs/nas/neurobooth/data/* logs/

rsync is better, especially if you want to maintain the folder tree structure, but just a note, rsync is natively supported by cygwin but not by other shells in windows (powershell devs already said they won't support rsync). So depending on what you are willing to use, rsync may not be an option.

rsync is better, especially if you want to maintain the folder tree structure, but just a note, rsync is natively supported by cygwin but not by other shells in windows (powershell devs already said they won't support rsync). So depending on what you are willing to use, rsync may not be an option.

This a fair point regarding non-native tooling. I believe Git for Windows may also implement rsync though, so maybe dev machines can be expected to have access to it in some form or another? If we plan to run the analysis on the cluster then it makes sense.

These are valid points. I wrote this in python because I don't use cygwin and would prefer not to install it again, and my original plan was to extend this to do parsing of the logs into CSV files for further analysis. I hope to get back to that someday.
I will save it elsewhere for my personal use until it's more functional.

These are valid points. I wrote this in python because I don't use cygwin and would prefer not to install it again, and my original plan was to extend this to do parsing of the logs into CSV files for further analysis. I hope to get back to that someday.
I will save it elsewhere for my personal use until it's more functional.

Makes sense! Regarding extending the script, I would decouple the log analysis and file transfer. I.e., it would be nice if the log analysis could be run on any machine, whether it be our laptop or the cluster (which would not need file transfer).

yes. I wasn't planning on coupling them tightly. Just make it so you could
call one on the output of the other.
On Tue, Sep 19, 2023 at 10:55 AM Brandon Oubre @.***>
wrote:

These are valid points. I wrote this in python because I don't use cygwin
and would prefer not to install it again, and my original plan was to
extend this to do parsing of the logs into CSV files for further analysis.
I hope to get back to that someday.
I will save it elsewhere for my personal use until it's more functional.
Makes sense! Regarding extending the script, I would decouple the log
analysis and file transfer. I.e., it would be nice if the log analysis
could be run on any machine, whether it be our laptop or the cluster (which
would not need file transfer).
—
Reply to this email directly, view it on GitHub
https://github.com/neurobooth/neurobooth-os/pull/319#issuecomment-1725808311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2FPAQM7MIF3SH3CYXVNXDX3GW4NANCNFSM6AAAAAA45FODTQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Adding a Travis CI build using Ubuntu Focal

Follow up for #1659 to add a CI build using the Ubuntu Focal platform version of the gcc compiler and dependencies.
This pull request depends on compiler error fixes in #1659 being merged.
Open questions

should all CI builds be updated to use the latest platform/compiler versions? Or should one/most builds use the older platform version to verify that xrdp continutes to build on the older platform?

TODO:

add/upgrade a clang build to the latest version

Thanks for raising this.
At the moment the benefits of this PR can be seen here, as #1659 has not been merged:-
https://travis-ci.org/github/aquesnel/xrdp/builds/721903430
My own preference would be to turn this round and make all the builds focal apart from a single xenial build. However, when I tried this myself I discovered libfdk-aac-dev seems to be missing for i386.
So another approach might be to keep i386 at xenial (for 'legacy') and move everything else forward to focal.
I hope this helps - sorry if it raises more questions than it answers.

I've updated this pull request with @matt335672 's suggestion of using the latest Ubuntu for all 64-bit builds, and only using ubuntu xenial for the 32-bit builds.

I'm certainly happy with this. I just pulled the commits into a temp branch in my own repo and ran it through Travis. Results are here. Using the name: tags helps the readability I think.
What do you think @metalefty?

Totally agree.

note
This pull request depends on the pull request #1659 being merged in order to not break the build. Since #1659 has been merged, this pull request is now unblocked and can be safely merged once it has been approved.


feat(random/unstable): basic randomization functions

Closes https://github.com/denoland/std/issues/4848
Currently includes the following:

@std/random/between: randomBetween function
@std/random/integer-between: randomIntegerBetween function
@std/random/sample: enhanced version of (to-be-deprecated?) @std/collections/sample's sample function, with new weights and random options
@std/random/seeded: randomSeeded function implementing the PGC32 algorithm
@std/random/shuffle: shuffle function implementing Fisher–Yates shuffle

@std/random/pick: pick and pickWeighted functions

Note that we already have sample() in @std/collections. So if we introduced a weighted sample() function, it should be added to @std/collections or even as an option to the current sample, for example a weight option:
const numbers = [1, 2, 3, 4];
const random = sample(numbers, { weights: [1, 9999, 2, 8888] });

@std/random/seeded: SeededPrng class implementing the Wichman-Hill algorithm

Is there a particular reason why this algorithm is added?

@std/random/shuffle: shuffle function implementing Fisher–Yates shuffle

I think this would be a cool addition to @std/collections.

@timreichen

@std/random/seeded: SeededPrng class implementing the Wichman-Hill algorithm

Is there a particular reason why this algorithm is added?

Only that it was the algorithm suggested in the linked issue, it has a period high enough for any sensible use case, and it seems to give a good distribution of results. One other plus is that arbitrarily chosen positive integer seeds still seem to give good entropy, even if they're apparently "low entropy" numbers like 1 or 12 (i.e. they don't need to be primes or anything fancy). I don't have the requisite expertise to verify its randomness properties beyond "seems to give good results" though.

@std/random/pick: pick and pickWeighted functions

Note that we already have sample() in @std/collections. So if we introduced a weighted sample() function, it should be added to @std/collections or even as an option to the current sample() function:
const numbers = [1, 2, 3, 4];
const random = sample(numbers, { weights: [1, 9999, 2, 8888] });

I quite like the idea of making it an option. It does require "unzipping" the values from their weights, but it can still be pretty versatile in terms of usage:
const weighted = new Map([["a", 5], ["b", 3], ["c", 2]]);
const result = sample([...weighted.keys()], { weights: [...weighted.values()] });

I'll keep the collections stuff within the scope of this PR for now as some of it relies on the random stuff (e.g. I'll use SeededPrng for tests), but happy to split it out before merging if that's preferable.

@lionel-rowe Can you move shuffle and this version of sample to std/random (leaving the existing collections/sample untouched)?
Also I'd prefer to see SeededPrng exported from @std/random/seeded-prng, randomBetween from @std/random/between, randomIntegerBetween from @std/random/integer-between for consistency of the rest of std.

@lionel-rowe Can you move shuffle and this version of sample to std/random (leaving the existing collections/sample untouched)?

@kt3k Wouldn't that be confusing to have two sample() functions? Or do you mean to deprecate collections/sample in another PR?

Also I'd prefer to see SeededPrng exported from @std/random/seeded-prng, randomBetween from @std/random/between, randomIntegerBetween from @std/random/integer-between for consistency of the rest of std.

Prng looks weird to me. Maybe it should it be written out as SeededPseudoRandomNumberGenerator?

@kt3k Wouldn't that be confusing to have two sample() functions? Or do you mean to deprecate collections/sample in another PR?

I think we can deprecate collections/sample when we stabilize random/sample.

Also I'd prefer to see SeededPrng exported from @std/random/seeded-prng, randomBetween from @std/random/between, randomIntegerBetween from @std/random/integer-between for consistency of the rest of std.

Prng looks weird to me. Maybe it should it be written out as SeededPseudoRandomNumberGenerator?

Or how about the name like SeededRandom? There is a similarly named npm package https://www.npmjs.com/package/seedrandom

How best to represent SeededRandom's seed and state values is giving me a bit of a headache.

Type
Pros
Cons

BigInt
- A single scalar value can hold a 64-bit uint- Visually compact
- Can also hold negative values and values bigger than uint64, and validity can only be checked at runtime- JSON.stringify throws

BigUint64Array
- Probably the most semantically "correct"
- The fact that the seed represents a 64-bit uint is an implementation detail that's not relevant for typical consumers of the library- JSON.stringify throws- Subject to endianness issues e.g. if created directly from underlying binary data. That seems like a deal-breaker to me.

Uint8Array
- Still semantically OK - bytes are bytes are bytes- Easy to extract uint64 values without worrying about endiannness using DataView#getBigUint64
- Length can only be checked at runtime- JSON.stringify gives an object with numeric keys but no length property, i.e. it can't be ergonomically converted back to a Uint8Array- The bytes really represent 64-bit uints, not 8-bit uints

Hex string
- Ergonomic to write- Visually compact
- Strings give very weak compile-time type checking, and TS's template literal types can't represent more than a couple of hex digits before running out of space

Standard array of Bytes (union of number literals 0..255)
- Can be easily converted to and from Uint8Arrays- Hard-coded values can be fully type-checked at compile time! You can check both length and the values of elements, e.g. allowing [1, 1, 1, 1, 1, 1, 1, 1] but disallowing [1, 1, 1] or [1, 1, 1, 1, 1, 1, 1, 256].
- Not very "webby"- Requires as type assertions for values that aren't hard-coded or directly emitted from the library

One possible idea: accept both Uint8Array and standard arrays of numbers as inputs (maximum ergonomics for both hard-coded and non-hard-coded use), while emitting arrays of numbers in the output (maximum portability — easy JSON serialization etc). Proof of concept: https://github.com/lionel-rowe/deno_std/commit/11961938e305f2b32f6a22562bf9510ea94aacfa

One possible idea: accept both Uint8Array and standard arrays of Bytes as inputs (maximum ergonomics for both hard-coded and non-hard-coded use), while emitting arrays of Bytes in the output (maximum portability — easy JSON serialization etc)

This sounds good to me. Also this is going to be unstable package for a while. We can iterate later.

One last thing. Can you please go through all exceptions and ensure they following the contributing guidelines? See https://github.com/denoland/std/blob/main/archive/tar_stream.ts for an example.

@iuioiua I think they already do, with the exception that error messages beginning with a variable name don't capitalize the variable name:
throw new RangeError("max must be greater than or equal to min");

How should those be handled? `max`/`min` with backticks would be another option.


[Android] TypeError: NativeCameraModule.checkDeviceCameraAuthorizationStatus is not a function

Issue Description
I followed the installation instructions on README.md but I get the following error when checking Device Camera authorization status:
TypeError: NativeCameraModule.checkDeviceCameraAuthorizationStatus is not a function
Steps to Reproduce / Code Snippets / Screenshots
This is my code:

import { CameraKitCamera } from 'react-native-camera-kit'

{...}
  componentDidMount() {
    return this.cameraAuthorization()
  }

  cameraAuthorization = async () => {
    const isCameraAuthorized = await CameraKitCamera.checkDeviceCameraAuthorizationStatus()

    if (isCameraAuthorized) {
      this.onCameraReady()
    } else {
      const isUserAuthorizedCamera = await CameraKitCamera.requestDeviceCameraAuthorization()
      if (isUserAuthorizedCamera) {
        this.onCameraReady()
      }
    }
  }
{...}

settings.graddle:
include ':rncamerakit'
project(':rncamerakit').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-camera-kit/android/')

android/app/build.gradle:
dependencies {
    implementation project(":rncamerakit")
    {...}

MainApplication.java:
import com.wix.RNCameraKit.RNCameraKitPackage;

{...}
    @Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
        new MainReactPackage(),
        new RNCameraKitPackage(),
{...}

Environment

React Native Camera Kit version: "^6.3.0"
React Native version: "0.57.4"
Platform(s) (iOS, Android, or both?): Android
Device info (Simulator/Device? OS version? Debug/Release?): Real Device: OnePlus One - 6.0.1

Same Error for android, works on IOS. Any update?


Implement automatic colour updates with GitHub Actions

Sorry for the spam, anyone who's receiving it. Don't worry - I am too...

It now works! Is this ok, @ozh? Currently I just have to run a script whenever I remember to, which is not a great solution.

Never spend 6 minutes doing something by hand when you can spend 6 hours failing to automate it

Seems nice! I'm surprised there's no need for an action to setup ptyhon itself ?

Nope, the GitHub Actions runners have the most common development environments pre-installed.


Could not create framebuffer

I get these two warnings over and over hundreds of times in the output window
drivers/gles2/rasterizer_gles2.cpp:10314 - Could not create framebuffer!!
drivers/gles2/rasterizer_gles2.cpp:10350 - Could not create framebuffer!!
https://github.com/okamstudio/godot/blob/master/drivers/gles2/rasterizer_gles2.cpp
My video card is relatively new with current and non-custom drivers on win7 64
Card: NVIDIA GeForce GTX 760

do you have the latest drivers installed?
On Sun, May 17, 2015 at 5:15 PM, travisapple<EMAIL_ADDRESS>wrote:

I get these two warnings over and over hundreds of times in the output
window
drivers/gles2/rasterizer_gles2.cpp:10314 - Could not create framebuffer!!
drivers/gles2/rasterizer_gles2.cpp:10350 - Could not create framebuffer!!
https://github.com/okamstudio/godot/blob/master/drivers/gles2/rasterizer_gles2.cpp
My video card is relatively new with current and non-custom drivers on
win7 64
Card: NVIDIA GeForce GTX 760
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1930.

I do. I have the latest version from NVIDIA. Thanks for looking into this!

This is displayed with the above warnings in the command line window but not the output frame:
ERROR: _draw_viewport:  Condition ' desired_rect.width<=0 || desired_rect.height <=0 ' is true.
At:  servers/visual/visual_server_raster.cpp:6965
https://github.com/okamstudio/godot/blob/master/servers/visual/visual_server_raster.cpp

Do you have an example project where this happens?  I've got a 770, and Windows 7 64 bit.  I'm curious if I could reproduce it.

Ok after playing around with this I finally figured out a way to reproduce this.
1: Open Godot
2: Open Any project
3: On windows, there's a blue "Show Desktop" button in the tray (bottom right). Click that. It should minimize all windows.
4: Now click on the task bar to show the Godot window. There should be hundreds of these errors in the output window that showed up as the window was minimized.
I verified that this is also an issue on two other computers (all Win 7) for both 32bit and 64bit. All three computers have different video cards from different manufacturers.
The issue is the "Show Desktop" button on Win 7.

On Windows 8.1 too.
WARNING: RasterizerGLES2::_update_framebuffer:  Could not create framebuffer!!
At:  drivers\gles2\rasterizer_gles2.cpp:10314
WARNING: RasterizerGLES2::_update_framebuffer:  Could not create framebuffer!!
At:  drivers\gles2\rasterizer_gles2.cpp:10350
ERROR: VisualServerRaster::_draw_viewport:  Condition ' desired_rect.width<=0 || desired_rect.height<=0 ' is true.
At:  servers\visual\visual_server_raster.cpp:6965

I thought that this is normal ( Windows 7 x64 Pro ):
At:  servers/visual/visual_server_raster.cpp:6965
WARNING: _update_framebuffer:  Could not create framebuffer!!
At:  drivers/gles2/rasterizer_gles2.cpp:10314
WARNING: _update_framebuffer:  Could not create framebuffer!!
At:  drivers/gles2/rasterizer_gles2.cpp:10350
ERROR: _draw_viewport:  Condition ' desired_rect.width<=0 || desired_rect.height
<=0 ' is true.

This also happens when using the Win+D shortcut (obviously), just wanted to mention that I have that problem too. (Raden HD7850)
drivers\gles2\rasterizer_gles2.cpp:10467 - Could not create framebuffer!!, code: 36054


Avm updates

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Thanks @sonalika-roy !
I'll get back to you this week for the review

I tried deploying the updated infra today but it get stuck when provisioning the app service part. I tried eastus2 and northeurope, but same issue. Did you succeed deploying it?


Fixing Documentation Shortcomings

Context
Much of the documentation for developing Serenade is not clear, incomplete, or hard to find.  This is a meta ticket to outline the missing sections so we can fix them up.  User facing documentation on some features could be part of this issue or a separate one
Goals
Ease of contributing or working on Serenade
List of missing areas

[ ] Building and running Serenade
[ ] Adding new programming language support or updating existing support
[ ] Training language models

always happy to accept documentation improvements—thanks for creating this issue!
just to make sure you've seen what we currently have, from https://github.com/serenadeai/serenade#docs:

building and running serenade: https://github.com/serenadeai/serenade/blob/master/docs/building.md
language support: https://github.com/serenadeai/serenade/blob/master/docs/grammars.md
training models: https://github.com/serenadeai/serenade/blob/master/docs/training-models.md

@tmacwill good to have those links. Do they show up on the website? How would a user best be directed to those pages?

the main repo README links to the docs folder, but am also open adding some individual links to the README or linking to the docs folder from https://serenade.ai/docs/

@tmacwill Thanks, that's where I was looking!  This issue came out of some conversations on the serenade discord about developing/running locally, so I created an issue where we can track people's documentation improvements over time.  Personally I hit a bit of a problem with setting up on an M1 that I'm working through, and I'll update the build docs with anything I find :)

nice, makes sense! ah yeah, code-engine and speech-engine don't yet have arm64 support, so on an M1 Mac, you'll need to build them using Rosetta2: https://github.com/serenadeai/serenade/blob/master/docs/building.md#system


Dot-Matrix version?

Hi! Apparently there’s a new dotmatrix version of these little clocks, which would also make it really easy to display day of the week as well as have a true menu for the settings.
Here’s a link to the product on Amazon:
Amzn.com/B07T369S58
No idea where to track down the original code, but I’m wondering if yours can be modified to work with this. I would be more than happy to contribute to the cause and ship you one of these clocks if you wanted to take a stab at it. Heck… even if you can just get a simple hello world on the screen, I could probably take it from there. I’ve already soldered on the header on the circuitboard so I should be good to go with programming. I just have no idea where to start.

Hi MarquelV, I think it's very possible to code for these, if the one you are lookign at uses STC microcontroller.
Please email me directly at af5mi at yahoo dot com about contributing a hardware sample.
-Jens

hi @MarqueIV were you able to test out https://github.com/zerog2k/clock-3118AY/tree/testing ?

Crap! Completely forgot about this!  Lemme see if I can take a crack at this in the next week or so.  Sorry for the delay.


instance direction error

Hello, I used this tool to convert i3dm and generated 3d tiles to display in Cesium, but the instanced direction is incorrect.
The convert code is as follows:
var glb = File.ReadAllBytes(model);
var i3dm = new I3dm.Tile.I3dm(pos, glb);
i3dm.FeatureTable.IsEastNorthUp = true;
and the  transform of the i3dm in 3d tiles is computed:
var transform = GisUtil.Wgs84Transform(longitude, latitude, height).ToArray();
While the result is that all these instanced object is fall-placed.
This is orginal glb file:

This is instanced object display in Cesium:

I am confused, why the parameter "EastNorthUp" in i3dm not working, why the instanced object direction is not the same as the orginal glb file. Thank you!

Hi, so the position is ok but the rotation not in Cesium?
To get the rotations in Cesium right is quite complex is my experience (it's something with calculating i3dm.NormalUps and i3dm.NormalRights), in MapBox client things are much easier.

Hi, that's it. The positions are right but the directions are wrong.
I know the rotation calculation is complex. You have discussed in this link. https://community.cesium.com/t/instance-rotation/10163
But, I don't need to rotate the glb model. I want to keep the directions of instanced objects the same as orginal glb model.
In my opinion, when the parameter"EAST_NORTH_UP" is set true, and "NORMAL_UP" and  "NORMAL_RIGHT" are default in b3dm file, the instanced objects should not be rotated.
Do you think so? Why the instanced objects are rotated fall-placed?
Thank you!

Ok if you don't need the rotations it should be more easy. Can you compare https://bertt.github.io/cesium_3dtiles_samples/samples/instanced/index_north.html with your case? Tool https://github.com/bertt/i3dm.tooling can assist to inspect/unpack the i3dm tiles.

Thank you very much for your patient reply.

Hello, I have solved the intance position and rotation problem, but another problem arose.
https://user-images.githubusercontent.com/44218937/115649929-d8865b00-a35a-11eb-98c8-29ff73e56a81.mp4
When I zoom or rotate the 3d earth, the instanced objects sometimes disappear. The bounding volume is set to be the extent region of all the instanced objects.
Do you know why? Thank you!

What was the fix?
Disappearing features: I suspect something with geometricError in tileset.json


Remove Atlas and Nifi

This PR removes all references to Apache Atlas and Nifi since they were merely used as proof-of-concepts and we don't plan on maintaining them at the moment. Also, they make up for a major chunk of the integration test runtime.
This was done in an attempt to make the code more readable and less cluttered.

what is the planned alternative for those dependencies?

what is the planned alternative for those dependencies?

We're currently looking into different approaches to implement the catalogueing feature as well as options to make the out-of-band data transfer simpler. No definite answer at this time I'm afraid, as the project is still in its infancy and docs aren't always up-to-date.

how is it possible to follow the discussions around this topic? I am already on the eclipse project mailing list, but this does not seem to be the right place.

once we have something concrete we'll definitely create issues here. your best bet is to watch this repo and periodically check back.

ok, thx!

Does anyone object to me merging this? If not, I'll go ahead later today.
Jim


[BUG] File opening in browser when dropped on body.

Description
In the pic text generator, files open in browser when dropped outside of the file area. This may often happen unknowingly.
There needs to be a default preventer for that.
Screenshots
No response
Additional information
No response
🥦 Browser
Google Chrome
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

that is true, i think because the drag and drop feature wasn't implemented in the library used

:tada: This issue has been resolved in version 2.56.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Node3D not selectable in Godot 4 for AnimationTree Root Motion Track (but Spatial was in 3)

Godot version
4.0.2
System information
Arch Linux, Xorg, Gnome 43
Issue description
The root node in my character exported with Auto-Rig Pro inside Blender contains a "root" Spatial/Node3D node, which is the intended track for root motion. However, Godot 4 doesn't allow me to select it, only the deformation bones contained within Skeleton3D.
Godot 3 LTS

Godot 4
 ``
Steps to reproduce

Open minimal reproduction project in Godot 3 LTS
Open the "char" scene
Click AnimationTree, then in Inspector > Root Motion > Track, select the "root" Spatial node at the top of the hierarchy.
See that everything works as intended.
Now, open the project in Godot 4.
Try to repeat Step 3.

As you can see, it isn't possible. The only way to get around this is to use the project converter in 4's import dialog, and make sure to never touch the Track's setting again.
Minimal reproduction project
root_motion_3.zip

Your project is not working correctly in 3.x to begin with. If the root motion is working properly, the RootMotionView should scroll.
What you say you did in Godot 3.x by selecting the root node is in fact just disabling the SpatialNode's animation.
The root motion must be included in the bones of the Skeleton, whether 3.x or 4.0.

The root motion view does scroll if you carry out step 3, like I said in my instructions. I submitted the project to show in step 3 is not possible in Godot 4. Please don't dismiss this so quickly, I've dedicated months of my life to working in Godot and this completely breaks functionality in 4.

The root motion view does scroll if you carry out step 3, like I said in my instructions.

I tried your project with 3.5.2, but first of all this is not available.
I don't think it should be enabled in the first place, since from a retargeting standpoint it can't handle animations that are outside of the skeleton. You should probably rethink your AutoRig pro settings.
I don't think it should be enabled in the first place, since from a retargeting standpoint it can't handle animations that are outside of the skeleton. You should probably rethink your AutoRig pro settings.

Auto Rig Pro bakes the "c-traj" controller's animation into the root node as part of a "Root motion" check mark in the settings, which cannot be configured, and is at parity with expected workflows for both Unreal Engine and Unity. However, what it does allow is including the c-traj controller in the export, which is what I did and tried again, with the root motion check mark disabled.
This bone exports forward as Y, and therefore doesn't affect the RootMotionView until "Zero Y" is unchecked, upon which it moves a forward moving character upwards. I've attached the project with the updated model below, if you'd like to see for yourself.
root_motion_3_zeroY.zip
This person on StackOverflow is facing the same issue from 10 days ago, here:
https://gamedev.stackexchange.com/questions/204975/godot-root-motion-is-calculated-incorrectly
If the solution is as simple as adding the equivalent of a "+Y Up" to the c-traj bone for export, I'll contact the developer of Auto Rig Pro and ask that he add a special preset for Godot 4.

At least if you use retargeting, it will be converted to the axis on the appearance, but if you don't use retargeting, you need to care about the axis of the bone. See also https://github.com/godotengine/godot/issues/75228.

If the solution is as simple as adding the equivalent of a "+Y Forward" to the c-traj bone for export, I'll contact the developer of Auto Rig Pro and ask that he add a special preset for Godot 4.

Yes, I suggest that.

Okay, but that person isn't using Auto Rig Pro, and they have the same problem, and their issue is still open while this one was closed and archived, and most likely visible only to you and me from now on.
Over the months of trying use Blender's default exporter alongside Godot I would have to set all my animations to move upwards when I wanted them to go forwards, which makes the process of actually animating like this impossible!

This issue makes working with root motion challenging in Godot because many root motion tools and assets export it as an object animation.
It works at runtime if you set root_motion_track to the root node by code. The problem is that we can't preview any root motion feature on the editor because you can't select it on the inspector.
As other engines do, the scene importer could have options to post-process the skeleton and animations to what Godot expects. I managed to get AutoRig Pro exports working with this import script. It creates a root bone, parent it to the base bones, and set the root animation track to point to it.
@tool
extends EditorScenePostImport

func _post_import(scene):
   modify_skeleton(scene)
   modify_animation(scene)

   return scene

func modify_skeleton(scene:Node, add_root = true):
   var skeleton:Skeleton3D = scene.find_child("Skeleton3D") as Skeleton3D

   var new_skeleton = skeleton.duplicate() as Skeleton3D

   if add_root:
   	new_skeleton.clear_bones()
   	new_skeleton.add_bone("root")

   # Can't set a new bone as parent of previous bones
   # Need to rebuild whole skeleton so root is the first bone
   for idx in skeleton.get_bone_count():
   	var name = skeleton.get_bone_name(idx)
   	var enabled = skeleton.is_bone_enabled(idx)
   	var parent = skeleton.get_bone_parent(idx)
   	var pose = skeleton.get_bone_pose(idx)
   	var rest = skeleton.get_bone_rest(idx)
   	var pos = skeleton.get_bone_pose_position(idx)
   	var rot = skeleton.get_bone_pose_rotation(idx)
   	var scale = skeleton.get_bone_pose_scale(idx)

   	new_skeleton.add_bone(name)
   	var new_idx = new_skeleton.get_bone_count()-1
   	new_skeleton.set_bone_enabled(new_idx, enabled)
   	new_skeleton.set_bone_rest(new_idx, rest)
   	new_skeleton.set_bone_pose_position(new_idx, pos)
   	new_skeleton.set_bone_pose_rotation(new_idx, rot)
   	new_skeleton.set_bone_pose_scale(new_idx, scale)

   	new_skeleton.set_bone_parent(new_idx, parent+1)

   if add_root:
   	for idx in new_skeleton.get_parentless_bones():
   		new_skeleton.set_bone_parent(idx, 0)

   for idx in new_skeleton.get_bone_count():
   	new_skeleton.force_update_bone_child_transform(idx)

   skeleton.replace_by(new_skeleton)

   return scene

func modify_animation(scene:Node):
   var root:Node3D = scene.find_child("root")
   var animation_player:AnimationPlayer = scene.find_child("AnimationPlayer")

   for animation_name in animation_player.get_animation_list():
   	var animation:Animation = animation_player.get_animation(animation_name)
   	var root_track = animation.find_track("root", Animation.TYPE_POSITION_3D)
   	animation.track_set_path(root_track, "root/Skeleton3D:root")
   	animation.track_move_to(root_track, 0)

   return scene

Works great with these export options:


player.on('ended', event => window.location : Not working with 3.6.7

Hi.
I m using version 3.4.3 with this code :
``
It's work fine.
i update to 3.6.7 and the code is not working anymore.
Thanks

I just note there is two differents behaviour :
https://cdn.plyr.io/3.6.7/demo.js
https://cdn.plyr.io/3.6.7/demo.css
and
https://cdn.plyr.io/3.6.7/plyr.css
https://cdn.plyr.io/3.6.7/plyr.js
dont give same skin / have differents error ..
I m lost :(


Fixed an error where xcopy fails due to a space in $(SolutionDir)

This explains that error I had. I wonder why it didn't appear in the video? I just copied the files myself.

This explains that error I had. I wonder why it didn't appear in the video? I just copied the files myself.
His path to sparky has no spaces I guess

I wonder why it didn't appear in the video?

He has no spaces in his sparky path I guess. The problem is that as soon as you have a space in your path and you pass it without quotation marks xcopy will receive multiple args instead of the one path, because space is obviously the standard argument-seperator. The quotation marks tell the commandline-engine (or whatever it is called) to pass everything between them as one arg and not seperate it.

Yes, you are correct. If you have no spaces in the $(SolutionDir) path, then this doesn't result in an error. Thanks for your pull request; merging.


Preserve sticky item height fixes(3499)

This PR fixes #3499

Codecov Report

Merging #3500 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3500      +/-   ##
==========================================
+ Coverage   99.82%   99.82%   +<.01%
==========================================
  Files         172      172
  Lines        2804     2805       +1
==========================================
+ Hits         2799     2800       +1
  Misses          5        5

Impacted Files
Coverage Δ

src/modules/Sticky/Sticky.js
98.91% <100%> (+0.01%)
: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 d40dad2...7cfb6c0. Read the comment docs.

Any update regarding this PR?

@felixmosh sorry for delay, thank you ❤


Add compatibility with the Django 1.10 MIDDLEWARE setting.

This patch allows developers to use the new MIDDLEWARE setting in Django. Changes are as follows:

Wrap all of Mezzanine's middleware in django.utils.deprecation.MiddlewareMixin when it is available. This allows it to work as new-style middleware in Django 1.10.

Dynamically check which of MIDDLEWARE and MIDDLEWARE_CLASSES is defined before monkey-patching settings in mezzanine.conf.set_dynamic_settings.

Note that Mezzanine will still default to MIDDLEWARE_CLASSES when creating new projects etc. (I think we have to wait till Django 1.12 before changing that). The purpose of this patch is just to allow developers to switch to using the new setting (and new-style middleware) without it breaking.

Looks good!
Couple suggestions:

Rather than having a MIDDLEWARE_SETTING variable everywhere, why don't we just do something like if not settings.MIDDLEWARE and settings.MIDDLEWARE_CLASSES: settings.MIDDLEWARE = settings.MIDDLEWARE_CLASSES, and then we just reference settings.MIDDLEWARE everywhere which is the correct name moving forward.

Can probably put the dummy middleware mixin into (a new module) mezzanine.utils.deprecation and import from there rather than repeating it everywhere.

@stephenmcd thanks for the prompt feedback. To address your points:

This will not work because Django treats the two settings differently. Everything in MIDDLEWARE is processed as new-style middleware and it will fail if not written in the new form. Everything in MIDDLEWARE_CLASSES is treated as old-style middleware and Django wraps is before passing to the new middleware handler. We cannot unilaterally rewrite one to the other without breaking things.

I have moved the MiddlewareMixin into a separate module. Thanks.

Makes sense, thanks!


format-alt not working in correctly - pulseaudio

using waybar v0.9.2
If format-alt is active, pulseaudio-module don't update if signal is sent, it stays unmuted. Logically, it should change its icon to not muted/normal. You can test it by a leftclick to change to format alt, afterwards right-click on the module, it stays unchanged.
  "pulseaudio": {     "format": "{icon}",     "format-alt": "{icon} {volume}%",     "format-muted": "",     "format-icons": {       "headphone": "",       "hands-free": "",       "headset": "",       "phone": "",       "portable": "",       "car": "",       "default": ["", ""]     },     "on-click-right": "pactl set-sink-mute @DEFAULT_SINK@ toggle",     "smooth-scrolling-threshold": 5,     "tooltip": false   },

Will be fixed with #676


Update jq-version to 1.7 from 1.6

/run tests

Will need adjustments, latest version is failing due to:
src/jq_test.c:322:24: error: invalid operands to binary expression ('pthread_t' and 'int')
        if (threads[a] != 0) {
            ~~~~~~~~~~ ^  ~


Building ImageMagick fails on Windows 10

I guess this is an issue for ImaegMagick.
Documenting this should anyone else install Makie on Windows 10 with Julia 1.0.0
Error: Error building ImageMagick:
│ ┌ Warning: On Windows, creating file symlinks requires Administrator privileges
│ └ @ Base.Filesystem file.jl:789
│ ┌ Warning: platform_key() is deprecated, use platform_key_abi() from now on
…….
Extracting archive:
│ ERROR: Can not create symbolic link : A required privilege is not held by the client. : C:\Users\hearn.julia\packages\ImageMagick\d5KBL\deps\usr\bin\libpng-config
│ ERROR: Can not create symbolic link : A required privilege is not held by the client. : C:\Users\hearn.julia\packages\ImageMagick\d5KBL\deps\usr\lib\libpng.dll.a
│ ERROR: Can not create symbolic link : A required privilege is not held by the client. : C:\Users\hearn.julia\packages\ImageMagick\d5KBL\deps\usr\lib\pkgconfig\libpng.pc

Is a fix in the works for this? Changing a system setting doesn't sound like the answer.

Looks to be fixed on my end!


added starterframe function

fixes #3

Things have got busy at work.. I'll need till the weekend to look at this stuff!

Don't sweat it, this is not work! Burn out in open source happens more than we'd like to admit. Check it out whenever you feel like. In also quite busy with work. I think it's cool that we can collaborate over github without ever having met in real life and being in other continents!


Address BUILD_DOCUMENTATION sphinx warnings

@jhlegarreta I took quite a few passes at the AdaptiveHistogram issue, but we finally in a good place :-)
With the warnings cleaned up, it will be easier to prevent issues from slipping in.


Support for mobile apps?

Is MDL perform well on a mobile phone?

for question please head over to stackoverflow.
MDL is a responsive Framework so it should be usable for mobile apps written in HTML/CSS/JS.