Run DANNCE on Rat7M

Hi,
I want to run DANNCE model on the Rat7M dataset as a baseline. To do that, I am preparing the *_dannce.mat file. Rat7M comes with the Camera parameters and the 3D groundtruth. But I don't know how to fill the field of labelData.data_2d for each of the six cameras.
Could you tell me how to get those values? ---- I thought DANNC does NOT need 2d labels but without these values the model ran into errors...
BTW, I am going to use the pretrained models (DANNCE and COM) you provided in the demo/markless_mouse_1/, please let me know if you suggest otherwise.
Thank you in advance.

The way it is currently written, all of our models (including ones that do not require 2D labels, such as DANNCE) share a common set of data loading functions and thus expect to find labelData.data_2d. It is not ideal behavior, and I hope that a contributor at some point improves this =) If you are just using a DANNCE model, you can just fill data_2d with zeroes.
Are you planning to train on Rat7M or just do prediction on Rat7M? For prediction, yes, the pretrained weights in demo/markerless_mouse_1/DANNCE/weights/weights.rat.AVG.6cam.hdf5 should be fine. Remember to set vol_size: 240 to use 3D volumes that are large enough to contain a rat and set new_n_channels_out: 22 (or scrub new_n_channels_out from the config entirely).

Thank you for your fast reply!
I changed the new_n_channels_out to 20 since there are 20 keypoints in the Rat7M MoCap data. I will change the vol_size to 240.
I can try to modify the data loading process for DANNCE. I can make a pull request if I get success.
Happy Danncing!

Thanks! We are preparing a new release soon, if you want to make any
changes I recommend branching off release_development.
But also -- you are just planning to do Rat7M prediction, right? If you are
planning to try training, there is more to discuss re: logistics.
On Mon, May 16, 2022 at 5:43 PM Even @.***> wrote:

Thank you for your fast reply!
I changed the new_n_channels_out to 20 since there are 20 keypoints in
the Rat7M MoCap data. I will change the vol_size to 240.
I can try to modify the data loading process for DANNCE. I can make a pull
request if I get success.
Happy Danncing!
—
Reply to this email directly, view it on GitHub
https://github.com/spoonsso/dannce/issues/109#issuecomment-1128167002,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW2P42W3VINI5WD4WNQ5XDVKK6OTANCNFSM5WCJWLLA
.
You are receiving this because you commented.Message ID:
@.***>

Hi, Dr. Dunn,
Yes that I plan to just do the Rat7M predictions. I first run the COM prediction using the weights.rat.COM.hdf5 in the demo/markerless_mouse_1/COM/weights/. I used the debug mode and output the COM overlays. Unfortunately, the overlay looks quite off ( I randomly picked Camera5.)  I realized that I cannot use the flag --com-fromlabels to do DANNCE predictions so I am training the COM from scratch, which gives me the error about memory loading, just as you expected.
May I ask how to pregenerate all of the volumes and save them to disk?

What downfac did you use for the COM prediction? It is quite sensitive to
using the same value that was used for training.
On Tue, May 17, 2022, 4:36 PM Even @.***> wrote:

Hi, Dr. Dunn,
Yes that I plan to just do the Rat7M predictions. I first run the COM
prediction using the weights.rat.COM.hdf5 in the
demo/markerless_mouse_1/COM/weights/. I used the debug mode and output
the COM overlays. Unfortunately, the overlay looks quite off ( I randomly
picked Camera5.) I realized that I cannot use the flag --com-fromlabels
to do DANNCE predictions so I am training the COM from scratch, which gives
me the error about memory loading, just as you expected.
May I ask how to pregenerate all of the volumes and save them to disk?
—
Reply to this email directly, view it on GitHub
https://github.com/spoonsso/dannce/issues/109#issuecomment-1129293939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW2P46C3ZUKCXHLMW37GHDVKP7LHANCNFSM5WCJWLLA
.
You are receiving this because you commented.Message ID:
@.***>

I used downfac: 4.  In the provided config files, the values are
in com_mouse_config.yaml  downfac=2 and
in dannce_rig_com_config.yaml downfac=8
What number should I use? 8? Can I set the downfac to 8 and then predict COM using the provided weights.rat.COM.hdf5  for Rat7M? Or do I need to train the COM first?

Try it with downfac 2
On Tue, May 17, 2022, 7:18 PM Even @.***> wrote:

I used downfac: 4. In the provided config files, the values are
in com_mouse_config.yaml downfac=2 and
in dannce_rig_com_config.yaml downfac=8
What number should I use? 8? Can I set the downfac to 8 and then
predict COM using the provided weights.rat.COM.hdf5 for Rat7M? Or do I
need to train the COM first?
—
Reply to this email directly, view it on GitHub
https://github.com/spoonsso/dannce/issues/109#issuecomment-1129409410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW2P43ZRPN3QNZBP4GHKYLVKQSMBANCNFSM5WCJWLLA
.
You are receiving this because you commented.Message ID:
@.***>

Prediction, that is. With the rat.com weights
On Tue, May 17, 2022, 7:20 PM Tim Dunn @.***> wrote:

Try it with downfac 2
On Tue, May 17, 2022, 7:18 PM Even @.***> wrote:

I used downfac: 4. In the provided config files, the values are
in com_mouse_config.yaml downfac=2 and
in dannce_rig_com_config.yaml downfac=8
What number should I use? 8? Can I set the downfac to 8 and then
predict COM using the provided weights.rat.COM.hdf5 for Rat7M? Or do I
need to train the COM first?
—
Reply to this email directly, view it on GitHub
https://github.com/spoonsso/dannce/issues/109#issuecomment-1129409410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW2P43ZRPN3QNZBP4GHKYLVKQSMBANCNFSM5WCJWLLA
.
You are receiving this because you commented.Message ID:
@.***>


Normal User login after to tips:no permission

runtime: docker
run shell:
rocketmqdashboard:
image: apacherocketmq/rocketmq-dashboard:1.0.0
container_name: rmq-dashboard
deploy:
resources:
limits:
memory: 512M
restart: always
links:
- rmqnameserver
environment:
- JAVA_OPTS=-Drocketmq.namesrv.addr=rmqnameserver:9876
- "rocketmq.config.loginRequired=true"
- "rocketmq.config.dataPath=/tmp/rocketmq-console/data"
volumes:
- ./env/rmq.properties:/tmp/rocketmq-console/data/users.properties
- ./env/role-permission.yml:/tmp/rocketmq-console/data/role-permission.yml
ports:
- "9875:9875"
BUG REPORT
users.properties file add Normal User
web login this Normal User,tips no permission

Normal users can only access URIs in the config  rolePerms.ordinary.
Could you provide more information for troubleshooting, for example, which URI has no permission?

After investigating, I found some of the read URIs is not default in the rolePerms.ordinary config, it is not a functionality Bug but it really makes user confused. I will create a new PR to improve it.
Thanks for your issue.

PR has been submitted.
If it is urgent for you, the workaround is to modify the role-permission.yml yourself.

PR has been submitted. If it is urgent for you, the workaround is to modify the yourself.role-permission.yml

thank you


build: bump ti plugins version

/assign @Mini256
PTAL~
Please test in test-dev after the merge, and if you need some label testing, you can submit pr to change the configuration.

/lgtm

/merge


Improve documentation

Would you mind improving the documentation?
I'm missing a full example. Particularly one explaining of how to merge an arbitrary number of streams into one. Does the constructor take an array of streams? How is merge-stream supposed to be used in the context of gulp?
Thanks for clarifying.

Does the constructor take an array of streams?

You can read the very small code to fully understand what it actually does. https://github.com/grncdr/merge-stream/blob/master/index.js

How is merge-stream supposed to be used in the context of gulp?

https://github.com/gulpjs/gulp/blob/36374495496b7893ce42116e10b878debd136b1f/docs/recipes/using-multiple-sources-in-one-task.md

Yes, you are right. I already did now. :checkered_flag: Yet I would have preferred to just read the .md.

Anyway, as @SetTrend suggested, API doc with argument types (like deep-extend-stream doc) is useful for users.

@SetTrend PR welcome to improve the docs


TorsionDrive Dataset Visualization

Description
Add visualization to the torsion drive dataset for 1D scans. In addition:

[x] Adds a count function to find the number of total optimization/gradient evaluations.
[x] Adds a status function to provide details on completed torsion scans.
[x] Allows the visualization to measure the actual angle of the final molecule rather than trusting the constraint.

@ChayaSt

Status

[ ] Changelog updated
[x] Ready to go

This pull request introduces 1 alert when merging fc8909553d7bb564418de34e877689bca19ce7bf into a1c257f512c7cb0d0fbef67895935353b1660eb6 - view on LGTM.com
new alerts:

1 for Unused local variable

Comment posted by LGTM.com


update word from currently to may

Test on iOS 14.5:
Image component support that four border radius properties now.

@Simek good suggestions. But if you view the Image style props document here: https://reactnative.dev/docs/image-style-props#image-border-radius. You can see that the four border radius props are supported on iOS platform.
Another thing I check the history of the document: https://github.com/facebook/react-native-website/commits/master/docs/images.md. The sentences about iOS Border Radius Styles never have changed since first commit.
thanks.
cc: @hramos

@robberfree I have in mind the React Native core repository PRs and commits, or official changelog entries, not the docs.
The code should be the source of truth in this case.


Bootstrap 4

To get text the correct size on the web page, set the html font-size to 1em - all text on the page is relative to this size. Don't ceil or floor font sizes - you'd do this for px units, but for rem units we want the decimals. Form input boxes add 2 (pixels) to the line height - Need to convert this 2 to ems. The Admin pages use the bootstrap folder directly (apps use rails_admin), so need to include the functions.scss file in bootstrap. the px_to_em function returns rem units not em siren rem units are used elsewhere and we'd get more "bootstrap can't combine units" errors

You're saying that your rails app(using RailsAdmin for admin backend) breaks when used with Bootstrap 4, assets failing to compile or showing wrong style - is that correct?
How can I reproduce the problem you're experiencing?

Bootstrap 4 doesn't allow measurement units to be mixed (you can define the width of, say, a text in terms of pixels or of ems or of rems, but you can't define one text in terms of pixels and then define another text in terms of the first text plus a number of ems. Or you can't say that a text is 3 ems high then say a button is the same height as the text plus 2 pixels - you always have to use the same units.
In Rails Admin, there is a file with a number of variables (variables.scss) that defines the sizes of text, and so on. This file needs to consistently use the same units. Rather than go through the file and change every pixel measurements to the corresponding number of rems, I added a new function that converts a number of pixels to the same number of rems (16 pixels = 1 rem) and I applied that function to all the pixel measurements. Now all sizes are defined in terms of rems. Also note that rems are often small decimal numbers (while pixels are almost always integers) so flooring and ceiling rems is not a good thing to do.
I found that just changing from Bootstrap 3 to Bootstrap 4 in my GemFile and then asset precompiling threw up a large number of errors all caused by mixed measurement units. I changed definitions one at a time until I resolved all the errors.

I should also say that my site (https://library.gordonknight.co.uk) uses Rails Admin, but only for administrators. Regular users see pages that are defined as rails views.

Hmm... I could not reproduce.
My attempt went like this:

Using dummy_app, added gem 'bootstrap', '~> 4.3.1' to Gemfile
Renamed app/assets/stylesheets/application.css to application.scss and added @import "bootstrap"; there.
Run rake assets:precompile, nothing broke and application-<hash>.css is generated containing styles from Bootstrap 4.

What's the difference with yours?

I'm going to close this pull request.
I'm now very confused. I have just reverted my gemfile back to using the standard rails admin gem (now at version 1.4.2). I clobbered and cleaned my assets and then pre-compiled and my assets precompile successfully. All I did was change my gemfile.
I can only think that I must have changed something else in the past few weeks - probably after I modified rails-admin and that negated the need for my rails-admin changes. It must be something in my own css files that was causing my problems. Going back over my changes, I can't see anything obvious that I have changed.
I'm very sorry for wasting your time on this.


az search service CLI doc missing some documentation

Describe the bug
This docs page: https://learn.microsoft.com/en-us/cli/azure/search/service?view=azure-cli-latest#az-search-service-update
has several arguments not documented, instead the doc page just shows "Some help" (which isn't).
Related command
az search service update etc.
Errors
The doc page does not document all arguments
Issue script & Debug output
The doc page does not document all arguments
Expected behavior
The doc page does document all arguments

Environment Summary
➜ az --version
azure-cli                         2.56.0
core                              2.56.0
telemetry                          1.1.0
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\v-paelazem.azure\cliextensions'
Python (Windows) 3.11.5 (tags/v3.11.5:cce6ba9, Aug 24 2023, 14:38:34) [MSC v.1936 64 bit (AMD64)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
No response

Thank you for opening this issue, we will look into it.


generic interface cannot be used as a generic argument

When an interface uses "__generic", the interface cannot be used as a part of the __generic argument.
It is easier to explain the problem with an example.
The following code gives us a compile error,
__generic<T:__BuiltinFloatingPointType> // <== This is the problem
interface IOperation
{
  static bool Equals(T lhs, T rhs);
};

__generic<T:__BuiltinFloatingPointType, OpType:IOperation<T>> // <= Not sure if this is a right way
bool Equals(T lhs, T rhs)
{
  return OpType::Equals(lhs, rhs);
}

The error message is following,
a.slang(8): note 99999: an internal error threw an exception while working on code near this location
bool Equals(T lhs, T rhs)
    ^~~~~~
(0): error 99999: Slang compilation aborted due to an exception of class Slang::InternalError: unexpected: Generic type/value shouldn't be handled here!

The following alternative approach didn't work either,
__generic<T:__BuiltinFloatingPointType>
interface IOperation
{
   bool Equals(T lhs, T rhs);
};

__generic<T:__BuiltinFloatingPointType>
struct JKWAK_test
{
    __generic<OpType:IOperation<T>>
    bool Equals(OpType op, T lhs, T rhs)
    {
       return op.Equals(lhs, rhs);
    }
}

The error message is identical to the first example.

This is due to some fundamental limitation we have in our IR. Supporting this is likely something we cannot afford in the short term. Let's try:
__generic<T:__BuiltinFloatingPointType>
struct JKWAK_test
{
    bool Equals(IOperation<T>op, T lhs, T rhs)
    {
       return op.Equals(lhs, rhs);
    }
}

If this doesn't work, we may be able to fix it.

Oh. I got it wrong.
The suggested workaround seems to be working.
Let me try it on UE.

This issue was closed as WNF due to the low bang for the buck.
But we should track it as an unfinished feature like https://github.com/shader-slang/slang/issues/4236


aws region-specific bug

When I set my ZAPPA_SETTINGS to be something like below
ZAPPA_SETTINGS = {
'dev': {
'aws_region': 'ap-northeast-1',
's3_bucket': 'MY_BUCKET_NAME,
'settings_file': 'PATH_TO_MY_SETTINGS/settings.py'
}
}
the standrad "python manage.py deploy dev" command doesn't work.
However, If I remove the "aws_region" parameter, things magically work. I believe this behaviour is easily reproduciable and might be non-us-region specific.

Are lambda and api gateway available in ap-northeast-1?
Either way, can you post the relevant part of the stack trace? It might be something somebody can help fix, or worst case it will help others search for it.

@collingreen thank you for your quick response. I tried to reproduce the issue so I can get some stack traces but am not able to at the moment.
The sequence of things I did was

Created a bucket to be used in my ZAPPA_SETTINGS beforehand, set my ZAPPA_SETTINGS accordingly, ran the deploy command, it failed.

Changed the ZAPPA_SETTINGS to use a new bucket name (without actually creating it), ran the deploy command, everything worked fine. Then noticed things are up and running in a us region.

Supplied the region parameter (ap-northeast-1) into my ZAPPA_SETTINGS, left the bucket name unchanged, ran the command, it failed.

Supplied the region parameter, changed the bucket name parameter to a new one (not yet created), ran the command, it failed.

Removed the region parameter, left the bucket name unchanged, ran the command, things worked.

^
Left me with a conclusion that something region-specific is messing things up. (which I have no clue about). But at the moment, I can't reproduce the behavior.
any guess? please give me some guidance on whether or not to keep this issue open in case I run into that behavior again. I am developing a micro service and need to have it up and running in the ap-north-east region and (hopefully not) might run into this issue again

I concur that this is a bug.
ZAPPA_SETTINGS = {
    'dev': {
        'aws_region': 'ap-southeast-1',
        's3_bucket': 'django.lambda',
        'settings_file': './project/settings.py',
    }
}

But my bucket was still created in US Standard that is why I get this error because they are not in the same region.
botocore.exceptions.ClientError: An error occurred (InvalidParameterValueException) when calling the CreateFunction operation: Error occurred while GetObject. S3 Error Code: PermanentRedirect. S3 Error Message: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.


add user_contract when invited

Codecov Report

Merging #67 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
+ Coverage   98.74%   98.77%   +0.03%
==========================================
  Files          22       22
  Lines         636      655      +19
==========================================
+ Hits          628      647      +19
  Misses          8        8


Missing GLIBC packages on RHEL5

I'm trying to run 0.8.1 of LightTable on RHEL5 and I get the following error:
lighttable: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by lighttable)
lighttable: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by lighttable)
lighttable: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /opt/LightTable/libnode.so)
lighttable: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /opt/LightTable/libnode.so)
lighttable: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /opt/LightTable/libgcrypt.so.11)
lighttable: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /opt/LightTable/libgcrypt.so.11)

I'm guessing it's because RHEL5 is too old, and contains older versions of GLIBC. Is there any possibility to package those binaries in with the release or to default to compiling with an older gcc?

I found similar issues to this one:

Can't run on CentOS 6.5 · Issue #1842 · LightTable/LightTable
Running on CentOS · Issue #1418 · LightTable/LightTable
GLIBC error on Debian · Issue #164 · LightTable/LightTable

My last comment on #1842:

Atom/Electron requires the specific version of libc. And it just doesn't seem to work on CentOS versions prior to 7; one issue among several:

atom-shell not available on CentOS? · Issue #1172 · atom/electron

There seem to be lots of people struggling to build it on CentOS 6.x, to no obvious avail.
I don't think I, or anyone else, will be able to help you. Light Table is nearly moribund as-is. Migrating from node-webkit to Atom was a significant project aimed to address major issues for a large number of users. Migrating to another alternative is just not realistic anytime soon – unless you are willing to spearhead that effort yourself.


update 1.20.2 ?

when will there be an update 1.20.2
because I can't play without it. This is a great mod

The 1.20 version is working for me in 1.20.2. Your mileage may vary however, depending on what other mods you have installed.

when will there be an update 1.20.2 because I can't play without it. This is a great mod
I made this mod for version 1.20.2 and above!
Here is the link: https://github.com/ShrikerChestTree/CITResewn/releases/tag/1.20.2
I'm sorry to post it here because I can't post it in Pull Reguest.

when will there be an update 1.20.2 because I can't play without it. This is a great mod

I made this mod for version 1.20.2 and above! Here is the link: https://github.com/ShrikerChestTree/CITResewn/releases/tag/1.20.2 I'm sorry to post it here because I can't post it in Pull Reguest.

So what did you change, because your fork seems to be just a fork with no changes?

Modifying fabric.mod file (>=1.20)

I made this mod for version 1.20.2 and above! Here is the link: https://github.com/ShrikerChestTree/CITResewn/releases/tag/1.20.2 I'm sorry to post it here because I can't post it in Pull Reguest.

unfortunately this does not work at all. even with just this file and the fabric api, it just tries to load, then crashes immediately

I made this mod for version 1.20.2 and above! Here is the link: https://github.com/ShrikerChestTree/CITResewn/releases/tag/1.20.2 I'm sorry to post it here because I can't post it in Pull Reguest.

unfortunately this does not work at all. even with just this file and the fabric api, it just tries to load, then crashes immediately

Bro has already released a new version of the mod (or not) for the new version -.-
Well, if not, then in the search in Modrinth write "CIT Resewn".


Usage examples

Hi,
I have the need to implement flink using the MongoDB sink, and I really liked this project! But it was not clear how to implement it in flink, is it possible to attach, or send me some examples of use?

Close this issue since the discussion is not active. Reopen it if needed.


[AutoPR managementgroups/resource-manager] typo: managementgroups/resource-manager/Microsoft.Management

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4709

Build output:

dist/com.microsoft.azuregroups.v2018_03_01_preview/azure-mgmt-management-1.0.0-beta-javadoc.jar
dist/com.microsoft.azuregroups.v2018_03_01_preview/azure-mgmt-management-1.0.0-beta.jar
dist/com.microsoft.azuregroups.v2018_03_01_preview/azure-mgmt-management-1.0.0-beta.pom
dist/com.microsoft.azuregroups.v2018_03_01_preview/azure-mgmt-management-1.0.0-beta-sources.jar

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2227


Typo in the tutorial in 'Firebase for Flutter'

In the 9th Chapter "Enable Data Syncing", it has a typo in the following code:
ChatMessage({this.snapshot, this.animation)};
main.dart
// Modify the following line of ChatMessage in main.dart.
class ChatMessage extends StatelessWidget {
  ChatMessage({this.snapshot, this.animation)};
  final DataSnapshot snapshot;
  final Animation animation;

  @override
  Widget build(BuildContext context) {
    return new SizeTransition(
      sizeFactor: new CurvedAnimation(
          parent: animation, curve: Curves.easeOut),            // modified

Remove the TickerProviderStateMixin widget and the List variable from the ChatScreenState class definition, as shown.

cc @Sfshaza

This bug refers to the deprecated (and removed) codelab. (It was replaced for Google I/O 2018.) Closing.

@AugustusLi
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/883. Any further collaboration will be done there.


docs: documents

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


设置了sock5的代理, 怎么不生效

Before feedback
Before you feedback, please search for the issues to see if there are similar problems that can solve your problem.
Please delete the above and the contents of this line, then fill in the feedback form in the following format, Thanks.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS & Version: [e.g. macOS, Windows, Linux]
Version: [e.g. macOS 10.14.2, Windows 10, Ubuntu 18.04]
Motrix Version: [e.g. v1.1.3, v1.1.0]
Installation package type: [e.g. dmg, AppImage]

Additional context
Add any other context about the problem here.

这个软件底层用的是开源 aria2 进行封装，arisa2 好像不支持 socket5 代理。

https://github.com/agalwood/Motrix/wiki/Proxy


Exception following VSCode startup after following Getting Started instructions

Reference issue #701, "Error: spawn ctest ENOENT", closed by the initiator.
Reference issue #522, "Stuck with 'Configuring project: Saving open files'", open.
I'm opening a new issue because #701 was closed by the initiator without a description for how it was mitigated. Issue #522 appears to be common to a number of situations.
I get the following exception after restarting VSCode when following instructions in the Getting Started document during initial setup. Everything configures and builds fine until VSCode is restarted.
[rollbar] Unhandled exception: Unhandled Promise rejection: Post-folder-open Error: spawn ctest ENOENT {"folder":{"uri":{"$mid":1,
"fsPath":"c:\Users\Me\Documents\Projects\Embedded\VSCode\MyProject","_sep":1,
"external":"file:///c%3A/Users/Me/Documents/Projects/Embedded/VSCode/MyProject",
"path":"/c:/Users/Me/Documents/Projects/Embedded/VSCode/MyProject","scheme":"file"},
"name":"MyProject","index":0}}
It seems to be having a problem with the definition of "external".

Same issue, have you worked out any approach to solve the problem? @itbgcthate

I have not.

Are you both using MinGW by chance? Make sure that CTest is on your system PATH, and then do a Scan for Kits.  There's a bug with MinGW kits that it saves off your PATH variable when you do a scan, so if CTest was not on the path at the time you first scanned, it will not find CTest subsequently when using that kit.  See #760.

Is this still an issue?  We made some fixes to MinGW scenarios recently and would ask that you try again.  If it is still an issue, can you please provide instructions for how to reproduce the problem? (e.g. a repository to clone, and which version of CMake and MinGW you are using.)
Thank you!


Triangular Prism

I would like to fix this. Please assign this to me.

Go ahead
Deadline 8 May,2021


[Feature Suggestion] IPinfo's free IP database - IP to Country ASN

Is there an existing issue for this?

[X] I have searched the existing issues.

Describe the solution you'd like
As Sniffnet uses country and ASN information of IP addresses, I think IPinfo's free IP database would be able to provide tremendous value.
The features of the free IP to Country ASN database:

Provides full accuracy with daily updates and no IP range aggregation. The accuracy of IP data is provided on a granular level.
Combines both country and ASN information in a single database.
Comes in MMDB file format.
The database structure is flat, tabular and consistent.
Released under a commercially permissible CC-BY-SA 4.0 license.

Schema: https://ipinfo.io/developers/ip-to-country-asn-database

FIELD NAME
EXAMPLE
DATA TYPE
DESCRIPTION

start_ip
<IP_ADDRESS>
TEXT
Starting IP address of an IP address range

end_ip
<IP_ADDRESS>
TEXT
Ending IP address of an IP address range

country
JP
TEXT
ISO 3166 country code of the location

country_name
Japan
TEXT
Name of the country

continent
AS
TEXT
Continent code of the country

continent_name
Asia
TEXT
Name of the continent

asn
AS2519
TEXT
Autonomous System Number

as_name
ARTERIA Networks Corporation
TEXT
Name of the AS (Autonomous System) organization

as_domain
arteria-net.com
TEXT
Official domain or website of the AS organization

As the IPinfo's IP to Country ASN database comes in .mmdb format, the rust MMDB reader library can still be used. The "free" in the free IP database is only related to the part that it is a reduced subset of the IP geolocation database and does not provide city-level data. There is no compromise with accuracy.
Please let me know what you think. If you need any assistance, I will be happy and glad to help.
Disclaimer: I am the DevRel of IPinfo. We also have a community dedicated to IP data usage in OSS projects.
Is your feature request related to a problem?
The existing IP database does not provide daily updates, and I believe it does aggregate IP ranges. Due to the database's lack of full accuracy, there are possibilities of IP location discrepancies.
Example (As of writing this):
IP Address: <IP_ADDRESS> (IPinfo.io/<IP_ADDRESS>)
Current Provider's free service: Argentina
Current Provider's paid service: United States
IPinfo's Free IP database: Canada
Evidence: The lowest ping time from 600+ probe servers is in  Montréal, Quebec, CA.
Independent evidence from Ping.sx

Hi @abdullahdevrel first of all thanks very much for the very detailed and precise report, I really appreciate that.
Some concerns I'm noticing:

the size of the DB is a bit high (if I'm not wrong it's around 47 MB) and this would negatively impact on the packed binary size. I know that probably the size overhead wrt the DB I'm currently using is due to the presence of more entries/major accuracy, but it still feels a bit too much.
Even if the DB is updated daily, I'm currently distributing the MMDBs embedded into the binary, so given a version of Sniffnet the MMDB file wouldn't be updated anyway.

I really appreciate you taking a look, @GyulyVGC
Would it be possible for us to write a PR for the project that implements a database download mechanism during the installation process?
This will be a great feature because:

It will enable you to ship smaller binaries without packaging a database in the project.
Users will get full accuracy and updated data routinely if they update the IP database themselves.
It will simplify code maintenance issues as the IP database will be downloaded from the client side and the update mechanism will be done by the user.

The plan I would suggest:

During the installation, the database from IPinfo gets downloaded.
During the installation process, we mention where the IP database is stored by mentioning the file path to the DB.
The user is provided some level of documentation so they can update the database routinely. The file path to the IP database should be transparent and it is just a file they can overwrite to keep the IP data fresh.

Downloading the IP database is as simple as making a curl/wget call (documentation):
curl -L https://ipinfo.io/data/free/country_asn.mmdb?token=<YOUR_TOKEN> -o country_asn.mmdb

Addressing your concerns

wrt the DB I'm currently using is due to the presence of more entries/major accuracy, but it still feels a bit too much.

The cost of high accuracy is that we are including more granular information, and thus, the size of the binary is relatively large.
The current two databases that you use account for a total of ~15 MB. While our database is significantly bigger.
The size discrepancy is due to IP range aggregation. IP range aggregation works by clustering IP ranges ( for example, /24) into one geolocation. So, even if IP addresses of an IP address range fall into multiple countries, by doing IP address range clustering, providers simply pick the majority location of each IP address and assign it to the entire range. That is an accuracy compromise. This creates a new dimension of the problem, as range clustering does not account for IP corrections on an individual level.
We do not do range clustering; the database is fully accurate even though it is free. IP range granularity goes to even one IP address level (/32 CIDR range).
Example:
SELECT *
FROM (
    SELECT *
    FROM ip_country_asn
    WHERE start_ip=end_ip
)
SAMPLE (5 ROWS)

START_IP
END_IP
COUNTRY
COUNTRY_NAME
CONTINENT
CONTINENT_NAME
ASN
AS_NAME
AS_DOMAIN

2620:0:1cff:dead:beef::7ca0
2620:0:1cff:dead:beef::7ca0
DE
Germany
EU
Europe
AS32934
Facebook, Inc.
facebook.com

2606:4700::6811:ffbf
2606:4700::6811:ffbf
US
United States
NA
North America
AS13335
Cloudflare, Inc.
cloudflare.com

2001:728:0:2000::8a
2001:728:0:2000::8a
GB
United Kingdom
EU
Europe
AS2914
NTT America, Inc.
ntt.com

<IP_ADDRESS>
<IP_ADDRESS>
US
United States
NA
North America
AS15133
Edgecast Inc.
edg.io

<IP_ADDRESS>
<IP_ADDRESS>
BR
Brazil
SA
South America
AS19551
Incapsula Inc
incapsula.com

Now, if we implement an IP database download feature, you can remove the database packaged with the binary, which accounts for 15 MB.
Then, when the user installs the program, they can download the database directly from us after installation. Moreover, if we keep the downloaded database path transparent, users can regularly download our database using their own free token to keep the database updated. They can write a cronjob of sort that overwrites the IP database on a regular schedule.

MMDBs embedded into the binary, so given a version of Sniffnet the MMDB file wouldn't be updated anyway.

I hope that you will consider implementing the download mechanism. The parent databases of the IP to Country ASN database are ASN database and IP to Geolocation database.

The ASN database has changed by 0.116% since yesterday.
The IP to Geolocation database changed by 0.004% since yesterday.

Considering the daily changes, these updates can add up. Sniffnet deals with sensitive information, so the project would greatly benefit from the increased accuracy provided by our database.

Please let me know what you think.

While I got your point and actually the solution could be beneficial under certain point of views, I still prefer bundling the DBs to keep things easy for the average user.
I think the normal user is not interested in having such a fine grained granularity and I don't want to leave the burden to create a token and install in a pre-defined path.
A better solution is an hybrid one: in #365 I'm already implementing the possibility to choose a custom MMDB file for users who have a commercial database or want more precision, otherwise the embedded one will be used.
In this way, the average user can enjoy the app without having to worry about further installations/configurations, while more advanced users can download the MMDB file they prefer and later set the path to it via the new Advanced settings.

I thank you again very much for your proposal and assistance in providing such a detailed ticket.
However, as anticipated I think that #365 is the best tradeoff between complexity and completeness.

@GyulyVGC Thank you very much again for considering us. I totally understand.
We will be cheering on from the sidelines :) Feel free to ping us anytime in the future, it will be an honor to help.

Hey @abdullahdevrel I was wondering if there could be a chance for a sort of collaboration between IPinfo and Sniffnet.
#365 was merged some days ago and I thought it can be nice to include in Sniffnet's settings a link  to the IPinfo website.
This would be beneficial for:

my users to know where to get MMDB resources
for IPinfo itself, since it'd be a sort of promoting chance to acquire new customers and to be highlighted as one of the leaders in this sector

Furthermore, if you are willing to start this collaboration, I'll be more than happy to highlight IPinfo as one of Sniffnet's sponsors in the README as well as the official website of the project.
I plan to release the next version of the app in a couple of months, so feel free to take your time to come to a decision 😃

Hey @GyulyVGC,
Apologies for the late response. That is a fantastic proposal. I have emailed you<EMAIL_ADDRESS>to discuss the suggestion further.
Thanks!

Hey @abdullahdevrel I'm super happy you find the proposal interesting!
I just answered your email.
I remain open for further discussion both here or via email.

@all-contributors please add @ipinfo for financial.


Add "Self" to Actor select

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Adds a new Self option to Actor Selector fields inside Actor Scripts

What is the current behavior? (You can also link to an open issue here)

When copy and pasting an Actor with scripts that reference itself all the Actor select fields need to be set to the new Actor again.

What is the new behavior (if this is a feature change)?

When selected, "Self" always references the current actor. So when the actor is copied it'll reference the newly created Actor rather than the previous one.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No

Other information:

Great idea! It looks like the UI was hooked up but the compile part was missing, I've just pushed a small update that appears to make this work.
I'm gathering a bunch of updates together at the moment and making sure they all work together so I think once I've tested this some more it will be merged as part of the 1.2.0 release candidate.
Thanks @pau-tomas!

Oh! Yes, I did a last minute refactor to not have to pass context all the way down the view hierarchy and then I forgot to add the compile part. Thank you!


fix: Prevent an infinate loop on Windows in build executables

Description
When running jaspr through dart .\lib\main.dart or through a built Jaspr executable the _findRootProjectDir (in lib/src/server/server_handler.dart) would enter an infinite loop because Platform.script.path returns the the path with a leading slash.
This changes requests for Platform.script.path to Platform.script.toFilePath() which is more correct.
Also fix melos format on Windows and the real server test on Windows.
This also updates modules/build to a valid commit.
Fixes #130
Type of Change

[ ] ❌ Breaking change
[ ] ✨ New feature or improvement
[x] 🛠 Bug fix
[ ] 🧹 Code refactor
[ ] 📝 Documentation
[ ] 🗑 Chore

Ready Checklist

[x] I've read the Contribution Guide.
[x] In case this PR changes one of the core packages, I've modified the respective CHANGELOG.md file using
the semantic_changelog format.
[x] I updated/added relevant documentation (doc comments with ///).

@fuzzybinary Feel free to open another PR and add yourself to the AUTHORS file.


feat(etcd): added etcd chart to helm charts

etcd chart for Kubernetes.
Tested etcd on Kubernetes deployed locally (AWS) using helm.

can you just keep only etcd commits here. You also have storm commits in this PR

Could you take a look at our contribution standards in https://github.com/helm/helm/blob/master/docs/awesome.md
Specifically you're missing some of the items in
https://github.com/helm/helm/blob/master/docs/awesome.md#labels

You need to edit your commit similar to #72 -- your email is incorrect. :)

Done.

This hasn't been updated in six weeks and there are a few outstanding comments. @chaitanyaenr is this still in progress or should we close it?


dfx 0.11.2 wasm optimization is not respecting the icp:* custom metadata namespace

So doing some testing with integrating an experimental version of the metadata schema proposed in #2607 into the ic-kit. I can correctly get things working by manually compiling the cargo project, and running ic-wasm shrink on it, which is the new tooling for shrinking wasm, in leu of ic-cdk-optimizer.
Doing the same build using the standard dfx build hello with 0.11.2 results in the custom linked sections to be stripped, regardless of the namespace

Just realized this is addressed in PR #2578 which has been merged :heavy_check_mark:


Validate Filters.json

We don't currently perform any validation on the filters.json file provided. We should check that all the regex as okay and give a warning if the file isn't okay.

Starting with #68 we gracefully handle a bad filter file, and debug output should indicate what we loaded for user debugging.


Add respondImmediately property to SinonFakeServer

server.respondImmediately = true;
If set, the server will respond to every request immediately and synchronously. This is ideal for faking the server from within a test without having to call server.respond() after each request made in that test. As this is synchronous and immediate, this is not suitable for simulating actual network latency in tests or mockups. To simulate network latency with automatic responses, see server.autoRespond and server.autoRespondAfter.
http://sinonjs.org/docs/

thanks mate!


build error:  rebar: Command not found

Environment

OS:  ubuntu
Max@gitlab:~/emq-relx$ uname -a
Linux gitlab 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Max@gitlab:~/emq-relx$ cat /etc/issue
Ubuntu 16.04.2 LTS \n \l

Erlang/OTP:
Erlang/OTP 21 [erts-10.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe]

EMQ:
git clone https://github.com/emqtt/emq-relx.git

Description
A description of the issue
Max@gitlab:~/emq-relx$ make
make[1]: Entering directory '/home/Max/emq-relx/deps/goldrush'
make[1]: rebar: Command not found
Makefile:13: recipe for target 'deps' failed
make[1]: *** [deps] Error 127
make[1]: Leaving directory '/home/Max/emq-relx/deps/goldrush'
erlang.mk:310: recipe for target 'deps' failed
make: *** [deps] Error 2

Checkout V2.3.11 tag and use erlang/otp 20 as erlang runtime. The problem could be solved.

thank you.


MM-43306 : Support graphQL for channels, channel members

Summary

Ticket Link
https://mattermost.atlassian.net/browse/MM-43306
Related Pull Requests
n/a
Screenshots
n/a
Release Note

Add graphQL support for fetching channels, channel members and sidebar categories in team controller component.

/update-branch

/update-branch

Error trying to update the PR.
Please do it manually.

/update-branch

Nice work! Testing this out locally and loading the app and doing a few basic tasks worked.
I see a few small things to change before approving. It looks like there's imports that had been renamed to channel_actions2 (maybe while doing some temporary refactoring), and a missing Channel type import. I also see one unit test failing locally:
 FAIL  components/team_controller/actions/index.test.ts
  ● components/team_controller/actions › initializeTeam › should fire off success of getChannelsMembersCategories when fetch call passes

Fixed the wrong import and the test.

/update-branch

E2E tests not automatically triggered, because the PR is not in a mergeable state. Please update the branch with the base branch and resolve outstanding conflicts.

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/248458

/update-branch

/e2e-test MM_ENV="MM_FEATUREFLAGS_GRAPHQL=true"

Triggering e2e testing with options:
&map[MM_ENV:MM_FEATUREFLAGS_GRAPHQL=true]

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/249431

/update-branch

/e2e-test MM_ENV="MM_FEATUREFLAGS_GRAPHQL=true"

Triggering e2e testing with options:
&map[MM_ENV:MM_FEATUREFLAGS_GRAPHQL=true]

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/249806

/update-branch

/e2e-test MM_ENV="MM_FEATUREFLAGS_GRAPHQL=true"

Triggering e2e testing with options:
&map[MM_ENV:MM_FEATUREFLAGS_GRAPHQL=true]

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/251809

@jgilliam17 trigger both with and without gQL flag

@M-ZubairAhmed graphQL one has a lot of failures
with graphQL https://mattermost-cypress-report.s3.amazonaws.com/251808-6267462-onprem-ent-webapp-pr-11113-mm-ee-test:6267462/mochawesome.html
without graphQL https://mattermost-cypress-report.s3.amazonaws.com/251809-6267462-onprem-ent-webapp-pr-11113-mm-ee-test:6267462/mochawesome.html

@M-ZubairAhmed graphQL one has a lot of failures with graphQL https://mattermost-cypress-report.s3.amazonaws.com/251808-6267462-onprem-ent-webapp-pr-11113-mm-ee-test:6267462/mochawesome.html without graphQL https://mattermost-cypress-report.s3.amazonaws.com/251809-6267462-onprem-ent-webapp-pr-11113-mm-ee-test:6267462/mochawesome.html edited: post textbox appears disabled for most failures, making the channels "read-only"

pushed the fix

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/252067

/e2e-test MM_ENV="MM_FEATUREFLAGS_GRAPHQL=true"

Triggering e2e testing with options:
&map[MM_ENV:MM_FEATUREFLAGS_GRAPHQL=true]

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/252068


versionCode not increased?

Though there are multiple releases available and a versionName of 1.2.0 indicating that, versionCode is still on 1. As Android uses versionCode to tell versions apart (and to decide whether a given APK is an update to an already installed app), it's important to always increase that right before tagging a new release. Could you please do that for future releases? Thanks in advance!

Hi @IzzySoft, thanks a lot for pointing this out! I now had a look at it.
I wasn't super familiar with Android app versioning, and it seems that I introduced this bug here by specifying the cz.yaml config to update the version line in the pubspec.yaml file to the specified semantic version (e.g. 1.1.0) upon running cz bump.
However, this strips the part after the + symbol in the version line, which represents the build number in Flutter and is used to generate the versionCode. This got first manifested here after updating to version 1.0.0. Hence the versionCode got out of sync and has stayed like that up until now. Just as you say about the versionCode (and also android docs):

The value is a positive integer so that other apps can programmatically evaluate it, for example to check an upgrade or downgrade relationship. You can set the value to any positive integer you want, however you should make sure that each successive release of your app uses a greater value. You cannot upload an APK to the Play Store with a versionCode you have already used for a previous version.

So we need to fix this to be updated (incremented by +1?) when bumping versions. I could have a look if this can be done by some quick change to cz.yaml, but since it seems that @fpervaiz is working on some release bump+build CI in #53, @fpervaiz lmk if you want to have a look at it yourself 😊.

So we need to fix this to be updated (incremented by +1?)

By 1 is fine (would then serve as "release counter"). By definition it just has to be larger than anything previously defined, so there are different practices around. Just don't increase it too much as you never could go back then. With +1 you're totally on the safe side.
Never heard this causing issues with an app; for Flutter apps it usually suffices defining it properly in pubspec.yaml. But then, I'm no Flutter dev (not even an Android dev) – so I'm totally with you being cautious and asking a team member :smile:

@adam-sroka thank you for triaging the issue. I'm happy to pick this up!


Force helper class cards-cols-value to reduce card size

When I use the css helper class cards-cols-1 it works as expected, reducing the number of columns to 1.
However, when entering a value larger than the number of cards in the table, it does nothing.
In tables with 2-6 cards the cards are huge.
I would love to be able to use e.g. cards-cols-8 in a table with 3 cards to reduce the size of the cards.
I don't mind that they won't fill the whole page-width. They could just be left-aligned.

Can you share screenshots?
Have you tried changing the card width in Style Settings?

The variables can be found here:
https://github.com/kepano/obsidian-minimal/blob/master/src/scss/features/cards.scss#L5-L13
You should be able to accomplish what you're trying to do just by using the cards class alone and setting the --cards-min-width

With --cards-min-width:40px;
It seems like everything above cards-cols-3 gives me as many columns as can fit within the frame.
cards-cols-3

cards-cols-4

cards-cols-5

etc...

In the latest commit you can also define the max-width of cards globally by using this snippet
body {
  --cards-max-width:200px;
}

Awesome, thanks! Looks much cleaner now :)


chore: 🤖 smaller docker image

JIRA Link
N/A
Changelog / Description
removes dev dependency + use alpine as base to create significantly smaller docker images.
Previous images were 2.4GB images, this change brings them to a more reasonable 367 MB.
Checklist -

[ ] New Feature ?
[ ] Updated swagger annotation (if API structure is changed) ?
[ ] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

closing this, made it a separate commit in the dual SDK #202 PR instead


Feature request: AdminOnly comands

Should they be executed as well by bots in natural language?
Should we add an extra measure for that?

https://github.com/ephemeraHQ/message-kit/pulls


Keybindings and Settings Hotkeys Do Not Work in Other MainWindows

Open a new BN window
Open settings (via hotkey or menu)
Open a new window
Hotkey and menu are both non-functional for settings

This is not a new bug, has existed since at least 3.4, and the fix for https://github.com/Vector35/binaryninja-api/issues/4818 didn't resolve this particular issue.

Discovered here from the project window:
https://github.com/Vector35/binaryninja-api/issues/5002

Fixed in 4.0.4849-dev.

So one source of this behavior is fixed which fixes the initial repro steps shown above.
There is a separate issue and the repro is:

Open Binary Ninja
File....New Window
Close the first window
Only the Hotkey is non-functional. The menu action and the command palette actions work without issue.

Simply clicking on the Binary Ninja application menu, then clicking back to the Binary Ninja window allows the hotkey to work once again.

Fixed in 4.0.4874


setup.py should end with a new line.

it's now resolved, fix should be available soon

Fixed and will be included in next release


Problem with creating coords by dict

IMO there's a problem with using dicts as coords definition for DataArrays.
E.g. an array defined by
import xarray as xr
arr = xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]})
will lead to an exception when tried to be indexed like
arr[0, 0, 0]
The error message is
ValueError: conflicting sizes for dimension 'z': length 2 on <this-array> and length 3 on 'z'
As far as I can imagine this is because dicts don't preserve order in python.
At least printing the coords shows a different order than used in the definition of arr:
arr.coords
Coordinates:
  * x        (x) int32 1
  * z        (z) int32 1 2 3
  * y        (y) int32 1 2
Using an ordered dict turns out to work:
import collections
od = collections.OrderedDict([('x', [1]), ('y', [1, 2]), ('z', [1, 2, 3])])
arr = xr.DataArray(np.zeros([1, 2, 3]), od)
And so does using a list of tuples:
arr = xr.DataArray(np.zeros([1, 2, 3]), [('x', [1]), ('y', [1, 2]), ('z', [1, 2, 3])])
Both lead to
arr[0, 0, 0]
<xarray.DataArray ()>
array(0.0)
Coordinates:
    x        int32 1
    y        int32 1
    z        int32 1
as expected.
Detected in WinPython-64bit-<IP_ADDRESS>Qt5 with xarray version 0.7.0

You shouldn't be able to make a DataArray like this -- you have three dimensions on coordinates, but only one dimension on the array itself.
With xarray 0.8.2, you get an error message with your example:
import xarray as xr
arr = xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]})

ValueError: conflicting sizes for dimension 'z': length 1 on the data but length 3 on coordinate 'z'

However, this error message is not quite accurate. You need to explicitly provide dims to get a sensible error:
arr = xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]}, dims=['x'])

ValueError: coordinate z has dimensions ('z',), but these are not a subset of the DataArray dimensions ['x']

I still need to test this on the dev version, but for now I will make this as an error reporting bug.

Hello, thanks for the immediate reply - and to seize the opportunity: thanks for this really great library, which I think will be the enabler for me to - finally - use netCDF4 for my measurement facility like I wished for years now.
However, I have to disagree in your point regarding the not fitting dimensions in the DataArray definition. np.zeros() will for sure return an n-dimensional array when called with a length-n list as argument, which I did with n=3 and the list [1,2,3].
I.e. calling np.zeros([1, 2, 3])
will return array([ [ [ 0.,  0.,  0.], [ 0.,  0.,  0.] ] ])
Besides, the working alternatives with tuples or the OrderedDict use the very same dummy array for initializing in the example above.
Further I estimate the 0.8.2-error-message completely consistent: it (silently) acknowledges that there are three dimensions in both the zeros-array and the coords by reporting a problem about not fitting lengths of the third one of each, 'z'.
Though by adding a one-dimensional dims-definition, you turn the following error messages away from the original problem, now indeed introducing an inconsistency in dimensions between dims and data.

Note that the recommended to build data arrays is to specify the dimensions names explicitly:
In [11]: xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]}, dims=['x', 'y', 'z'])
Out[11]:
<xarray.DataArray (x: 1, y: 2, z: 3)>
array([[[ 0.,  0.,  0.],
        [ 0.,  0.,  0.]]])
Coordinates:
  * y        (y) int64 1 2
  * z        (z) int64 1 2 3
  * x        (x) int64 1

on master, failing to do so results in a FutureWarning (which is the important message, but gets lost in the traceback) and then in a ValueError (which might be confusing):
In [12]: xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]})
/home/mowglie/.pyvirtualenvs/py3/bin/ipython:1: FutureWarning: inferring DataArray dimensions from dictionary like ``coords`` has been deprecated. Use an explicit list of ``dims`` instead.
  #!/home/mowglie/.pyvirtualenvs/py3/bin/python3
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-12-501c20b8b785> in <module>()
----> 1 xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]})

/home/mowglie/Documents/git/xarray/xarray/core/dataarray.py in __init__(self, data, coords, dims, name, attrs, encoding, fastpath)
    219
    220             data = as_compatible_data(data)
--> 221             coords, dims = _infer_coords_and_dims(data.shape, coords, dims)
    222             variable = Variable(dims, data, attrs, encoding, fastpath=True)
    223

/home/mowglie/Documents/git/xarray/xarray/core/dataarray.py in _infer_coords_and_dims(shape, coords, dims)
     83                 raise ValueError('conflicting sizes for dimension %r: '
     84                                  'length %s on the data but length %s on '
---> 85                                  'coordinate %r' % (d, sizes[d], s, k))
     86
     87     assert_unique_multiindex_level_names(new_coords)

ValueError: conflicting sizes for dimension 'y': length 1 on the data but length 2 on coordinate 'y'

@shoyer maybe changing the warning into an error would be the way to go now?

@SpghttCd Yes, I was confused. I missed that you were writing np.zeros, so reply doesn't make much sense!
On master (and in the next release of xarray), we do indeed issue a warning here as @fmaussion points out. Unfortunately, we did support this behavior in prior releases of xarray (especially with an OrderedDict), so I think we should keep the deprecation warning around for a while before making this behavior an error (probably in v0.10).

o I think we should keep the deprecation warning around for a while before making this behavior an error (probably in v0.10)

@shoyer - Do we still want to deprecate this behavior in v0.10?

Do we still want to deprecate this behavior in v0.10?

Sure, that seems reasonable to me.


Ingress Gateway can't access HTTPS backend service

Followed this link - https://github.com/istio/istio/issues/8029, but couldn't make it work.
Same issue as mentioned in the above post, I'm able to make it work with PASSTHROUGH but we have requirement for TLS termination so trying nginx sample & also we need to use our custom certs mounted on ingress gateway (can't use ISTIO_MUTUAL)
ISSUE - I tried to set up a gateway and virtual service for an https service (nginx server). But the gateway can only send clear http request to the https service. And the https service return 400 Bad Request - The plain HTTP request was sent to HTTPS port.
I'm using istio 1.6.3, and running on my kind cluster locally.
`curl https://client-1.clients.alice.com:31308 -vvv --cacert ca.crt --cert client.crt --key client.key
* Rebuilt URL to: https://client-1.clients.alice.com:31308/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to client-1.clients.alice.com (<IP_ADDRESS>) port 31308 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: ca.crt
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Request CERT (13):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS handshake, CERT verify (15):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=client-1.clients.alice.com
*  start date: Aug 17 09:42:23 2020 GMT
*  expire date: Aug 18 09:42:52 2020 GMT
*  issuer: C=GB; ST=England; O=Alice Ltd; OU=Alice Ltd Certificate Authority; CN=Alice Ltd Intermediate CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fb82080a400)
> GET / HTTP/2
> Host: client-1.clients.alice.com:31308
> User-Agent: curl/7.54.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
*< HTTP/2 400
*< server: istio-envoy
*< date: Mon, 17 Aug 2020 11:55:28 GMT
*< content-type: text/html
*< content-length: 255
*< x-envoy-upstream-service-time: 3
*<
*
*<title>400 The plain HTTP request was sent to HTTPS port</title>
*
*400 Bad Request
*The plain HTTP request was sent to HTTPS port
*nginx/1.19.2`

### LOGS in ingress gateway pod -
[2020-08-17T11:56:41.422Z] "GET / HTTP/2" 400 - "-" "-" 0 255 4 3 "<IP_ADDRESS>" "curl/7.54.0" "2b515097-1a44-901c-9da9-36095f523cea" "client-1.clients.alice.com:31308" "<IP_ADDRESS>:443" outbound|443||nginx-service.development.svc.cluster.local <IP_ADDRESS>:38048 <IP_ADDRESS>:8443 <IP_ADDRESS>:40514 client-1.clients.alice.com -
### Below are yamls

apiVersion: v1
kind: Service
metadata:
  name: nginx-service
  namespace: development
spec:
 selector:
  app: nginx-container
 ports:
 - name: https
   protocol: TCP
   port: 443
   targetPort: 443

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  namespace: istio-system
  name: nginx-gateway
spec:
  selector:
    istio: ingressgateway # use istio default controller
  servers:
  - port:
      number: 443
      name: https
      protocol: https
    tls:
      mode: MUTUAL
      serverCertificate: /etc/istio/ingressgateway-certs/tls.crt
      privateKey: /etc/istio/ingressgateway-certs/tls.key
      caCertificates: /etc/istio/ingressgateway-ca-certs/ca-chain.crt
    hosts:
    - "*"

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: nginx-virtual-service
  namespace: development
spec:
  hosts:
  - "*"
  gateways:
  - nginx-gateway.istio-system.svc.cluster.local
  http:
  - match:
    - uri:
        prefix: "/"
    route:
    - destination:
        host: nginx-service.development.svc.cluster.local
        port:
          number: 443

apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: nginx-mtls
  namespace: development
spec:
  host: nginx-service.development.svc.cluster.local
  trafficPolicy:
    tls:
      mode: MUTUAL
      clientCertificate: /etc/istio/ingressgateway-certs/tls.crt
      privateKey: /etc/istio/ingressgateway-certs/tls.key
      caCertificates: /etc/istio/ingressgateway-ca-certs/ca-chain.crt
    portLevelSettings:
    - port:
        number: 443
      loadBalancer:
        simple: ROUND_ROBIN

And I'm successfully able to curl from ingress-gateway using same tls.crt and tls.key
kubectl -n istio-system exec -it $(kubectl -n istio-system get pod -l app=istio-ingressgateway -o jsonpath={.items..metadata.name}) -c istio-proxy -- curl -vvv https://nginx-service.development.svc.cluster.local:443 --cacert /etc/istio/ingressgateway-certs/ca-chain.crt --cert /etc/istio/ingressgateway-certs/tls.crt --key /etc/istio/ingressgateway-certs/tls.key
* Rebuilt URL to: https://nginx-service.development.svc.cluster.local:443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to nginx-service.development.svc.cluster.local (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/istio/ingressgateway-certs/ca-chain.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Request CERT (13):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS handshake, CERT verify (15):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=nginx-service.development.svc.cluster.local
*  start date: Aug 17 12:46:39 2020 GMT
*  expire date: Aug 18 12:47:09 2020 GMT
*  subjectAltName: host "nginx-service.development.svc.cluster.local" matched cert's "nginx-service.development.svc.cluster.local"
*  issuer: C=GB; ST=England; O=Alice Ltd; OU=Alice Ltd Certificate Authority; CN=Alice Ltd Intermediate CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55dc5c077580)
> GET / HTTP/2
> Host: nginx-service.development.svc.cluster.local
> User-Agent: curl/7.58.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200
< server: nginx/1.19.2
< date: Mon, 17 Aug 2020 12:51:25 GMT
< content-type: text/html
< content-length: 8626
< last-modified: Mon, 17 Aug 2020 12:47:25 GMT
< etag: "5f3a7c5d-21b2"
< accept-ranges: bytes
<

Some secrets:

NOTE- As per the link I also tried changing port name of my nginx service from https to http2-myport but it started giving 503, and also my curl from ingress gateway to nginx svc started failing with below error
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* error:1408F10B:SSL routines:ssl3_get_record:wrong version number
* stopped the pause stream!
* Closing connection 0
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
command terminated with exit code 35

curl https://client-1.clients.alice.com:31308 -vvv --cacert ca.crt --cert client.crt --key client.key
* Rebuilt URL to: https://client-1.clients.alice.com:31308/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to client-1.clients.alice.com (<IP_ADDRESS>) port 31308 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: ca.crt
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Request CERT (13):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS handshake, CERT verify (15):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=client-1.clients.alice.com
*  start date: Aug 17 09:42:23 2020 GMT
*  expire date: Aug 18 09:42:52 2020 GMT
*  subjectAltName: host "client-1.clients.alice.com" matched cert's "client-1.clients.alice.com"
*  issuer: C=GB; ST=England; O=Alice Ltd; OU=Alice Ltd Certificate Authority; CN=Alice Ltd Intermediate CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f96ef009800)
> GET / HTTP/2
> Host: client-1.clients.alice.com:31308
> User-Agent: curl/7.54.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 503
< content-length: 95
< content-type: text/plain
< date: Mon, 17 Aug 2020 14:24:03 GMT
< server: istio-envoy
< x-envoy-upstream-service-time: 44
<
* Connection #0 to host client-1.clients.alice.com left intact
upstream connect error or disconnect/reset before headers. reset reason: connection termination

cc @vadimeisenbergibm

@lubinson - Hi please let me know if you are able to solve this ?

can you post the config dump from ingress pod? https://github.com/istio/istio/wiki/Troubleshooting-Istio

I faced this case and I could not figure it out.
@lubinson
@howardjohn


Browser Compatibility: Microsoft Edge Fails

Navigating to your demo in the Microsoft Edge browser completely fails:

Hi @oneezy ,
I've already fix this issue in my last commit.

Great!
What was the problem if you don't mind me asking?

I was treating the result of the querySelectorAll()  method as an iterable array, and it only works in Chrome. I have to change it querySelectorAll(). forEach(callback)  to [].forEach.call(querySelectorAll(), callback)

ahhh, i see. Awesome.
I need to update to your new version.
I've been hacking away on the first theme, though it's mainly UI type stuff. Should be an easy transfer.

Check it out!
http://waifufightdangostyle.com/

Wow, it looks awesome! GJ

hahA.. thanks @trofrigo
I haven't even began to utilize wordpress yet, though I suppose that's a good thing in the beginning stages.  Save that for phase 2.


express.static not loading a customized folder name

app.use(express.static(__dirname + '/public',{
    etag: false
}));

My file tree

My css loads as expected
<link rel="stylesheet" href="/css/styles.css">

My . js in my footejs folder doesn't load
<script src="/footerjs/themeScript.js"></script>

But if I add /public to the path or change the footerjs to js then it loads, not sure why... It's not a virtual path, i can still access the js file with localhost:3000/footerjs/themeScript.js "version": "4.13.4" btw
<script src="/public/footerjs/themeScript.js"></script>
or
<script src="/js/themeScript.js"></script>

Hm, that is really weird. We can use some debugging output to see what is going on, though. Can you set the environment variable DEBUG to send,express:*? If you are launching your app as node app, then you just add it to the beginning like DEBUG=send,express:* node app. Then you should see a bunch of express: logs printed. Make the request to <script src="/footerjs/themeScript.js"></script> and then paste the debug output here are we can see what may be going on.

Here is what i get... weird ... I don't see the public...
  express:application set "x-powered-by" to true +0ms
  express:application set "etag" to 'weak' +3ms
  express:application set "etag fn" to [Function: wetag] +2ms
  express:application set "env" to 'development' +0ms
  express:application set "query parser" to 'extended' +0ms
  express:application set "query parser fn" to [Function: parseExtendedQueryString] +0ms
  express:application set "subdomain offset" to 2 +0ms
  express:application set "trust proxy" to false +1ms
  express:application set "trust proxy fn" to [Function: trustNone] +0ms
  express:application booting in development mode +0ms
  express:application set "view" to [Function: View] +0ms
  express:application set "views" to '/Users/myname/Sites/bitbucket/myApp/views' +0ms
  express:application set "jsonp callback name" to 'callback' +0ms
  express:router use / query +3ms
  express:router:layer new / +0ms
  express:router use / expressInit +1ms
  express:router:layer new / +0ms
  express:router use / serveStatic +0ms
  express:router:layer new / +0ms
  express:router use / serveStatic +0ms
  express:router:layer new / +0ms
  express:router:route new / +0ms
  express:router:layer new / +1ms
  express:router:route get / +0ms
  express:router:layer new / +0ms
running server on port 33333

Hi @nicolag that logs looks correct; it is what prints before you make any requests to your server. Did you try and make the request that was not working? It should print additional logs that should help.

Hi @dougwilson, I use <script src="/footerjs/themeScript.js"></script> and below is what I got with debug mode when I make the request to index.html
Last login: Wed Feb  8 21:29:27 on console.txt

Hi @nicolag that is weird indeed, because the trace is showing that your request GET /footerjs/themeScript.js is being served from the file /Users/nguo/Sites/bitbucket/nicolaDojoTheme/public/footerjs/themeScript.js which seems like the correct file you're trying to get.

Hey @dougwilson thanks for looking into it... I've tried to made a new app to test it, the same file structure but minimal content and less dependencies, everything works as expected...
It's just doesn't work over there, honestly I've spent tons of time in trying to figure out this weirdness ... I guess I will have to table it for now, lol... But thanks for the help.

@dougwilson guess what, I moved some of the themeScript.js 's required modules around and rename them, but didn't aware a path inside it was changed by web storm's auto reference refractor,  now it makes perfect sense why i have to use <script src="/public/footerjs/themeScript.js"></script> to load, just the <script src="/js/themeScript.js"></script> is still ridiculous. I will close this one, thanks @dougwilson.

No problem, @nicolag I'm glad you were able to track it down :D

Thank you @dougwilson  :)


Update C++ code sample.

The previous code sample did not compile. Updated it so that it does and reduced it to a MRE.

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


use getTargetClass in function checkTargetAttributeExistence

This interesting change, to be able to change getTargetClass when necessary when extending this class.

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Tests pass?
✔

Fixed issues

While this is a good change since we don't repeat code and use existing method, I'm a bit confused because the description you provided states that you would like to change visibility of getTargetClass()?

While this is a good change since we don't repeat code and use existing method, I'm a bit confused because the description you provided states that you would like to change visibility of getTargetClass()

That would be another point, besides decreasing the repeated code.
when think its facilitates to control a extend of the class, and you don't need to repeat function checkTargetAttributeExistence, to want modify just only getTargetClass  (I made some modifications).
will change the issue description.

While this is a good change since we don't repeat code and use existing method, I'm a bit confused because the description you provided states that you would like to change visibility of getTargetClass()?

I did correction of my explanation.

Thank you!


Where can I find the reference papers you've implemented in your code. I want to make a citation in my paper.

Where can I find the reference papers you've implemented in your code or how can I make a citation of your code. You have done a great stuff and I'm using your code in my paper. Thank you!

Please go to https://zenodo.org/record/4014775 for citation.
The DOI is 10.5281/zenodo.4014775


[Utility] Introduce an unbonding period after an actor unstakes

Objective
Design & implement a framework of how to handle on-chain Unbonding after an actor submits a valid Unstake transaction.
Origin Documents

Cosmos SDK documentation on unbonding
Cosmos explanation of unbonding in the context of validators
Morse (pocket-core) has a parameter called UnstakingTime which can be found here
Unstaking has been discussed on the Pocket Forums as can be found here

Goals

Unbonding definition: a state during which an actor operates normally, after unstaking, before their escrowed stake is returned and they are removed as active actors
At a minimum, have parity with unbonding periods from Morse
Evaluate options for how on-chain actor unbonding could be implemented
Design, document and implement unbonding of Applications, Suppliers & Gateways
Create a pattern reusable for all actors

Deliverables
IMPORTANT NOTE TO THE OWNER: The deliverables below are not a complete list of everything that needs to be done, but rather a starting point to help. The research, which is part of the deliverables, should drive most of the design decisions.

Research

[ ]  Put together a reference doc with bullet points, links, highlights, learnings capturing the research below(< 1 page total
Other Projects

[ ]  Investigate how actor (e.g. validator) unbonding is designed and implemented in the Cosmos SDK
[ ]  Investigate how at least one other project does (non-validator) actor unbonding in the Cosmos ecosystem

Morse

[ ]  Investigate how actor unbonding currently works in Morse

Before implementation

[ ]  Prepare a 1-pager “mini spec” notion / docs / markdown and get feedback & review before kicking off the implementation

Implementation requirements

[ ]  Unbonding should finish  automatically N blocks from the moment the actor submits the unstaking transaction
[ ]  N should have a unique governance parameter for every actor: Application, Supplier, Gateway
[ ]  Escrowed funds are returned to the actor only AFTER the unbonding process is complete

During implementation

[ ]  Separate PRs per actor after the foundation is in place
[ ]  Add unit / integration tests
[ ]  Add at least 1 E2E test (per actor)
[ ]  Make target to trigger the E2E test

After implementation

[ ]  Add a new page in docusaurus that explains how the implemented mechanism works

Estimated Days of Work
5 days
Disclaimer: This is the total projected number of estimated hours to completion & merge. The owner of this tickets is expected to use this GitHub issue to communicate with the core protocol team along the way, with update & feedback for each deliverable throughout the duration of this work._

Creator: @olshansk
Co-Owners: @moatus

@moatus Could you review the requirements for unstaking here. I'm thinking of mounting out the engineering work for it.

With some guidance from @facundomedica, here is the way to go

In that case I don't think we have a solution that would work "out of the box". You could achieve something like that with endblock or x/epochs, both solutions being pretty similar, main difference being that with x/epochs you can "schedule" the process to happen every certain amount of time.
Most likely you'll have an unbonding queue so on endblock/epochEnd you iterate through them and release any that its unbonding time has expired. You might also want to add some limits to this kind of processing, so you process up to X unbonds per epoch/endblock. Otherwise you might get timeouts.

After looking through [1], this is EXACTLY what we should be using for this.
[1] https://docs.cosmos.network/v0.46/modules/epoching/

Please note that the documentation is outdated on their website right now: https://github.com/cosmos/cosmos-sdk/issues/20651

@red-0ne Please make sure to take a look at the notes & comments. We should tackle this in the next iteration.

Cross-referencing this comment: https://github.com/cosmos/cosmos-sdk/issues/20651#issuecomment-2179515541

Implemented in #666 and #704.


Key Board Type Button is not working?

Key board type "Next", "Search", "Done" are not working?

this repo is out of date, check the new https://github.com/mopsicus/UnityMobileInput


remove line filename from the  pool section

Remove the filename config single line as it  breaks the conditional dhcp config for pxe;

[x] Redmine Issue: https://redmine.pfsense.org/issues/12986
[x] Ready for review

There is already a fix on that Redmine issue that should prevent that line from being a problem when it isn't needed. Is the current fix incomplete or not functional? If so, comment that on the Redmine. If you haven't tested the fix on the Redmine yet, please do so before suggesting additional changes.

I've tested the suggested fix and it does not work; this PR is running in production and solved the issue;
Looking in the history of the file I realize that the cause of the problem was a change in the logic;

Looking in the history of the file I realize that the cause of the problem was a change in the logic;

Is a different change needed? There's likely a reason why the line was included in that case - some additional clarification here would be helpful


Interpolated booleans inferred as boolean | null (nullability)

Describe the bug
TypeScript boolean types in template string interpolation are not correctly inferred as boolean, but instead as boolean | null
To Reproduce
Steps to reproduce the behavior:

// 💥 Query has incorrect type annotation.
//	Expected: { has_private_url: boolean; }
//	Actual: { has_private_url: boolean | null; }[]
await sql<{ has_private_url: boolean }[]>`
  SELECT
    ${true as boolean} AS has_private_url
  FROM
    users
`;

Also same problem with no TS type assertion:
// 💥 Query has incorrect type annotation.
//	Expected: { has_private_url: boolean; }
//	Actual: { has_private_url: boolean | null; }[]
await sql<{ has_private_url: boolean }[]>`
  SELECT
    ${true} AS has_private_url
  FROM
    users
`;

Expected behavior
Inference as boolean
Screenshots
--
Desktop (please complete the following information):

OS: macOS Sequoia 15.0 (24A335)
PostgreSQL version 14
Version 3.4.4

Additional context
I was thinking that this may relate to the isColumnNonNullable() function, but since I cannot see anything in the AST related to interpolated values (also not sure what keywords to search for), I'm thinking that maybe the interpolation happens at an earlier step, before the parsing, eg somewhere related to this code:
https://github.com/ts-safeql/safeql/blob/86f5cd6396a11001944d31e8a1ad99ca49497acb/packages/eslint-plugin/src/utils/ts-pg.utils.ts#L61-L98
With a few hints as to how the system works, I would love to open a PR fixing this.

Workaround
Wrap the interpolation in coalesce():
await sql<{ has_private_url: boolean }[]>`
  SELECT
    coalesce(${true as boolean}) AS has_private_url
  FROM
    users
`;


Support for Battery status?

Hey - , I love this code, and I have it running on my Merlot.
Would it be possible to see the battery status?

See here:
https://github.com/paperdink/paperd_ink_test/pull/4


ImageBox unable pan with keep selection rectangle selected

May be pan image with Shift keyboard modifier or start Selection with Control keyboard modifier key both independent...

Hello,
Thanks for the issues you've raised, and I do apologise for not noticing these earlier.
It's an interesting puzzle given how panning and selection behaviours contradict each other, which is why currently panning is disabled if selection is enabled. I'm not really sure there is a good solution - they are separate tools really.
One idea that did occur to me as I started replying to this would be some form of delay - so if you pressed the mouse and started moving it, this would be interpreted as defining a selection region. If you clicked and held for a moment, then started moving the mouse, this would be interpreted as "grab and pan".
Thanks again for the feedback!
Regards;
Richard Moss


add is_acknowledged, acknowledged_by, acknowledged_reason, acknowledg…

…ed_date to action item's fields
Proposed Changes

Request to to add is_acknowledged, acknowledged_by, acknowledged_reason, acknowledged_date to Cyberpion's action item fields.

Hi, can someone please take a look and approve or comment on the code. We really want to merge it, it's effecting our customers.


universal-lock: non-conflicting requirements with non-overlapping marker expressions provoke a fork

Consider these requirements:
a >= 1 ; sys_platform == 'linux'
a < 2 ; sys_platform == 'darwin'

with a==1.0.0 and a==2.0.0 available in the registry.
(These are captured in this packse test.)
Even though the version constraints are non-conflicting, because the marker expressions are non-overlapping, this will actually provoke a fork in the universal resolver. The fork means that the a >= 1 requirement is free to choose, say, a==2.0.0 if it's available because the fork exists in isolation from the a < 2 requirement. However, if no fork were to happen, then both the a >= 1 and a < 2 requirements would be active simultaneously such that a==2.0.0 couldn't be chosen. So in this case, there exists a resolution without forking, but it is distinct from the resolution we get if we fork.
I think we could detect this case by looking at whether the version constraints themselves are conflicting. That is, if there exists an overlap in the version constraints, then we don't fork even if the marker expressions are non-overlapping. I think a decision like that would be predicated on the idea that it could be possible to find one resolution that works across multiple platforms. But it might not be possible. It feels like forking in this case, even if it isn't always necessary, results in more freedom for the resolver to find a resolution. But... maybe it's surprising to users in real cases.
I'm overall not quite sure what the right behavior is here. My sense of things right now is that this shouldn't block shipping, but I'm happy to have my mind changed on that!
Original discussion: https://github.com/astral-sh/uv/pull/4339#discussion_r1642814360

For reference, if we run the corresponding packse scenario with uv, we get this lock file (current main is e264637b63b29b5e9a99ef9ac64594a8b827b611):
version = 1
requires-python = ">=3.12"

[[distribution]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies"
version = "0.0.0"
source = "registry+http://localhost:3141/"
sdist = { url = "http://localhost:3141/packages/fork-allows-non-conflicting-non-overlapping-dependencies/fork_allows_non_conflicting_non_overlapping_dependencies-0.0.0.tar.gz#sha256=a715415043cafef783fd4d6d3adcbfb0e823663f9af3e2a6e73810da9269e472", hash = "sha256:a715415043cafef783fd4d6d3adcbfb0e823663f9af3e2a6e73810da9269e472" }

[[distribution.dependencies]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies-a"
version = "1.0.0"
source = "registry+http://localhost:3141/"
marker = "sys_platform == 'darwin'"

[[distribution.dependencies]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies-a"
version = "2.0.0"
source = "registry+http://localhost:3141/"
marker = "sys_platform == 'linux'"

[[distribution]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies-a"
version = "1.0.0"
source = "registry+http://localhost:3141/"
sdist = { url = "http://localhost:3141/packages/fork-allows-non-conflicting-non-overlapping-dependencies/fork_allows_non_conflicting_non_overlapping_dependencies_a-1.0.0.tar.gz#sha256=dd40a6bd59fbeefbf9f4936aec3df6fb6017e57d334f85f482ae5dd03ae353b9", hash = "sha256:dd40a6bd59fbeefbf9f4936aec3df6fb6017e57d334f85f482ae5dd03ae353b9" }
wheels = [{ url = "http://localhost:3141/packages/fork-allows-non-conflicting-non-overlapping-dependencies/fork_allows_non_conflicting_non_overlapping_dependencies_a-1.0.0-py3-none-any.whl#sha256=37c13aa13cca009990929df08bed3d9de26e1d405a5ebd16ec0c3baef6899b23", hash = "sha256:37c13aa13cca009990929df08bed3d9de26e1d405a5ebd16ec0c3baef6899b23" }]

[[distribution]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies-a"
version = "2.0.0"
source = "registry+http://localhost:3141/"
sdist = { url = "http://localhost:3141/packages/fork-allows-non-conflicting-non-overlapping-dependencies/fork_allows_non_conflicting_non_overlapping_dependencies_a-2.0.0.tar.gz#sha256=0b4ca63d060f4daa2269c08b7083f594e096b94e1bcbde53d212c65b52378358", hash = "sha256:0b4ca63d060f4daa2269c08b7083f594e096b94e1bcbde53d212c65b52378358" }
wheels = [{ url = "http://localhost:3141/packages/fork-allows-non-conflicting-non-overlapping-dependencies/fork_allows_non_conflicting_non_overlapping_dependencies_a-2.0.0-py3-none-any.whl#sha256=35168196ad80d0f2822191a47e3a805b4ad527280c8b84e7eed77b7fee505497", hash = "sha256:35168196ad80d0f2822191a47e3a805b4ad527280c8b84e7eed77b7fee505497" }]

[[distribution]]
name = "project"
version = "0.1.0"
source = "editable+."
sdist = { path = "." }

[[distribution.dependencies]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies"
version = "0.0.0"
source = "registry+http://localhost:3141/"

And if we run it with poetry 1.8.2, we get this lock file:
# This file is automatically @generated by Poetry 1.8.2 and should not be changed by hand.

[[package]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies"
version = "0.0.0"
description = "This test ensures that multiple non-conflicting but also non-overlapping dependency specifications with the same package name are allowed and supported.  At time of writing, this provokes a fork in the resolver, but it arguably shouldn't since the requirements themselves do not conflict with one another. However, this does impact resolution. Namely, it leaves the `a>=1` fork free to choose `a==2.0.0` since it behaves as if the `a<2` constraint doesn't exist."
optional = false
python-versions = ">=3.8"
files = [
    {file = "fork_allows_non_conflicting_non_overlapping_dependencies-0.0.0.tar.gz", hash = "sha256:a715415043cafef783fd4d6d3adcbfb0e823663f9af3e2a6e73810da9269e472"},
]

[package.dependencies]
fork-allows-non-conflicting-non-overlapping-dependencies-a = [
    {version = "<2", markers = "sys_platform == \"darwin\""},
    {version = ">=1", markers = "sys_platform == \"linux\""},
]

[package.source]
type = "legacy"
url = "http://localhost:3141"
reference = "packse"

[[package]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies-a"
version = "1.0.0"
description = ""
optional = false
python-versions = ">=3.8"
files = [
    {file = "fork_allows_non_conflicting_non_overlapping_dependencies_a-1.0.0-py3-none-any.whl", hash = "sha256:37c13aa13cca009990929df08bed3d9de26e1d405a5ebd16ec0c3baef6899b23"},
    {file = "fork_allows_non_conflicting_non_overlapping_dependencies_a-1.0.0.tar.gz", hash = "sha256:dd40a6bd59fbeefbf9f4936aec3df6fb6017e57d334f85f482ae5dd03ae353b9"},
]

[package.source]
type = "legacy"
url = "http://localhost:3141"
reference = "packse"

[[package]]
name = "fork-allows-non-conflicting-non-overlapping-dependencies-a"
version = "2.0.0"
description = ""
optional = false
python-versions = ">=3.8"
files = [
    {file = "fork_allows_non_conflicting_non_overlapping_dependencies_a-2.0.0-py3-none-any.whl", hash = "sha256:35168196ad80d0f2822191a47e3a805b4ad527280c8b84e7eed77b7fee505497"},
    {file = "fork_allows_non_conflicting_non_overlapping_dependencies_a-2.0.0.tar.gz", hash = "sha256:0b4ca63d060f4daa2269c08b7083f594e096b94e1bcbde53d212c65b52378358"},
]

[package.source]
type = "legacy"
url = "http://localhost:3141"
reference = "packse"

[metadata]
lock-version = "2.0"
python-versions = "^3.11"
content-hash = "fa3f7ba6b95fa7787a5a362f6373095804b9e6ab1ce0a4608ebd5adb23d36999"

So here, it seems like both poetry and uv are forking since both a==1.0.0 and a==2.0.0 show up in the lock file.
But notice what happens if we try the packse test fork-allows-non-conflicting-repeated-dependencies. It looks a lot like the one above, but both requirements are unconditional so no forking happens:
a >= 1
a < 2

So locking with uv gets us:
version = 1
requires-python = ">=3.12"

[[distribution]]
name = "fork-allows-non-conflicting-repeated-dependencies"
version = "0.0.0"
source = "registry+http://localhost:3141/"
sdist = { url = "http://localhost:3141/packages/fork-allows-non-conflicting-repeated-dependencies/fork_allows_non_conflicting_repeated_dependencies-0.0.0.tar.gz#sha256=f71a547328d8616fddcc6ac173a242690d754e0d42427edd7d1f4df34b41d073", hash = "sha256:f71a547328d8616fddcc6ac173a242690d754e0d42427edd7d1f4df34b41d073" }

[[distribution.dependencies]]
name = "fork-allows-non-conflicting-repeated-dependencies-a"
version = "1.0.0"
source = "registry+http://localhost:3141/"

[[distribution]]
name = "fork-allows-non-conflicting-repeated-dependencies-a"
version = "1.0.0"
source = "registry+http://localhost:3141/"
sdist = { url = "http://localhost:3141/packages/fork-allows-non-conflicting-repeated-dependencies/fork_allows_non_conflicting_repeated_dependencies_a-1.0.0.tar.gz#sha256=45ca30f1f66eaf6790198fad279b6448719092f2128f23b99f2ede0d6dde613b", hash = "sha256:45ca30f1f66eaf6790198fad279b6448719092f2128f23b99f2ede0d6dde613b" }
wheels = [{ url = "http://localhost:3141/packages/fork-allows-non-conflicting-repeated-dependencies/fork_allows_non_conflicting_repeated_dependencies_a-1.0.0-py3-none-any.whl#sha256=b08be7896afa7402a2650dd9ebf38e32cf65d5bf86956dc23cf793c5f1f21af2", hash = "sha256:b08be7896afa7402a2650dd9ebf38e32cf65d5bf86956dc23cf793c5f1f21af2" }]

[[distribution]]
name = "project"
version = "0.1.0"
source = "editable+."
sdist = { path = "." }

[[distribution.dependencies]]
name = "fork-allows-non-conflicting-repeated-dependencies"
version = "0.0.0"
source = "registry+http://localhost:3141/"

And locking with poetry gets us:
# This file is automatically @generated by Poetry 1.8.2 and should not be changed by hand.

[[package]]
name = "fork-allows-non-conflicting-repeated-dependencies"
version = "0.0.0"
description = "This test ensures that multiple non-conflicting dependency specifications with the same package name are allowed and supported.  This test exists because the universal resolver forks itself based on duplicate dependency specifications by looking at package name. So at first glance, a case like this could perhaps cause an errant fork. While it's difficult to test for \"does not create a fork\" (at time of writing, the implementation does not fork), we can at least check that this case is handled correctly without issue. Namely, forking should only occur when there are duplicate dependency specifications with disjoint marker expressions."
optional = false
python-versions = ">=3.8"
files = [
    {file = "fork_allows_non_conflicting_repeated_dependencies-0.0.0.tar.gz", hash = "sha256:f71a547328d8616fddcc6ac173a242690d754e0d42427edd7d1f4df34b41d073"},
]

[package.dependencies]
fork-allows-non-conflicting-repeated-dependencies-a = ">=1,<2"

[package.source]
type = "legacy"
url = "http://localhost:3141"
reference = "packse"

[[package]]
name = "fork-allows-non-conflicting-repeated-dependencies-a"
version = "1.0.0"
description = ""
optional = false
python-versions = ">=3.8"
files = [
    {file = "fork_allows_non_conflicting_repeated_dependencies_a-1.0.0-py3-none-any.whl", hash = "sha256:b08be7896afa7402a2650dd9ebf38e32cf65d5bf86956dc23cf793c5f1f21af2"},
    {file = "fork_allows_non_conflicting_repeated_dependencies_a-1.0.0.tar.gz", hash = "sha256:45ca30f1f66eaf6790198fad279b6448719092f2128f23b99f2ede0d6dde613b"},
]

[package.source]
type = "legacy"
url = "http://localhost:3141"
reference = "packse"

[metadata]
lock-version = "2.0"
python-versions = "^3.11"
content-hash = "8b88e3e9187c6b396033abe10456761aceb0847dcdb391fd7a2cf091ab6a5bfb"

So both tools behave the same on this example too. No forking happens, and as a result, a==2.0.0 is completely excluded from the lock file.

This has been fixed by https://github.com/astral-sh/uv/pull/4662: We fork, but since we use the resolution of the first fork as preference for the next fork, we end up with only a==1.0.0


Add user documentation

Resolves https://github.com/silverstripe/silverstripe-session-manager/issues/15

@clarkepaul can you have a look at these userdocs?

@clarkepaul Are you satisfied with the doc?

Cool checked the last couple of changes of changing 'remember me' to 'keep me signed in' and looks good.


CF metadata for instrument variables

[x] variable names and attributes
[x] deployment details

Built in now... but no current way to track netcdf cf library used (other than in explicit meta documentation) which requires user to be well versed in updating config files


Docker build speedup

Small change to Dockerfile layer ordering. Layers which are expected to change infrequently appear earlier in the Dockerfile, reducing the time to make archive for code changes. A make cleandocker target has been added to the Makefile to explicitly delete the docker image when seeking to build from scratch.
The original ordering may have been intentional (as a way of forcing fresh docker images on every code change), this is just intended to make development quicker. Feel free to close without verbose commentary if so.

 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.Tim Sogard seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Grouped folder datasource and added searchbar

Added searchbar on folders

Grabbed pieces of it in various PRs. Closing this one. :pray: :pray:


Instancing crashes if instancing added before model component

Release Type: Github
Describe the bug
Adding an instancing component and then a model component crashes the instancing processor.
To Reproduce
Steps to reproduce the behavior:

Add instancing component to an entity,
Add model component to the same entity
Exception time

Expected behavior
It should not crash.
Screenshots
If applicable, add screenshots to help explain your problem (use GitHub drag & drop)

Log and callstacks
stacktrace.txt

I cannot reproduce this.
No crash after adding instancing, followed by model component to an entity:

This is a subtle bug.
It crashes on this line:
https://github.com/stride3d/stride/blob/f7494f8be926b42a7e882c4a085331672ae97af3/sources/engine/Stride.Engine/Engine/Processors/InstancingProcessor.cs#L173
because modelRenderProcessor can be null in a subtle case due to how it's stored by this line:
https://github.com/stride3d/stride/blob/f7494f8be926b42a7e882c4a085331672ae97af3/sources/engine/Stride.Engine/Engine/Processors/InstancingProcessor.cs#L210
The issue is if you start with a completely empty scene (technically a scene without any entities with a ModelComponent), then ModelRenderProcessor does not exist yet, so adding InstancingComponent will create InstancingProcessor without ModelRenderProcessor existing.
Not sure what's the correct way of solving processor dependency, two ways I can think of to solve this:

Add modelRenderProcessor ??= EntityManager.GetProcessor<ModelRenderProcessor>(); in OnEntityComponentAdding
new ModelRenderProcessor() and EntityManager.Processors.Add(...)  in OnSystemAdd if the first retrieval is null.

@tebjan Any other solutions or input?


freedv: fix build on darwin

Description of changes
Closes #165422.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

This still doesn't fix the issue on x86_64 darwin.

@knl authorizationStatusForMediaType is on macOS 10.14+. Maybe we just need to bump the SDK version?