Version of .mat file when saving

Hi. great project! Really useful.
I want to use this project to help me save data to a .mat file, then read .mat in MATLAB. But my data could be larger than 2 GB. Sometimes it may come to 100+ GB. ignore the limit of my memory, does matio-cpp support this?
.mat has several version. The latest is v7.3, or above. When I loaded a  mat file created using matio-cpp, size > 2GB, then MATLAB failed to read it. So I guess matio-cpp only support v7 .mat?
Best,
Zheng

Hello @zhengliuer, you can select the version of the saved .mat file from the code, see https://github.com/ami-iit/matio-cpp/issues/52#issuecomment-994914920 .

Thanks @traversaro ! I just noticed that parameter. But when I did like
matioCpp::File matFile = matioCpp::File::Create("test.mat", matioCpp::FileVersion::MAT7_3);

it caused
[ERROR][matioCpp::File::Create] Failed to open the file named test.mat.
[ERROR][matioCpp::File::write] The file is not open.

Not quite sure why. When I removed the vetsion, it works fine.
Best,
Zheng

Are you sure that the matio compiled by vcpkg is compiled with hdf5 support?

I am not familiar with vpckg's manifest mode (I typically use it in classic mode), but at first glance it does not seems that you enabled the hdf5 feature of matio, can you try with something like (I did not double checked if this is the correct syntax):
{
    "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg/master/scripts/vcpkg.schema.json",
    "name": "kit",
    "version": "1.0.0",
    "dependencies": [
        "zlib",
        "hdf5",
        {
            "name": "matio",
            "features": ["hdf5"]
        },
        "visit-struct"
    ]
}

Actually hdf5 should be in the default features (see https://github.com/microsoft/vcpkg/blob/5d66a8994296bd141b9bf870edb2b4663975acf9/ports/matio/vcpkg.json#L14), so hdf5 should be already be available, however it may be try to enable it explicitly. If you want to debug more deeply, the relevant part of the code is https://github.com/ami-iit/matio-cpp/blob/f30bce77cd214f0fa8a2c8fc75799957d85eaa9f/src/File.cpp#L221C28-L221C41 and https://github.com/tbeu/matio/blob/9e26c65fc31de240a051c8921119391f2c14f249/src/mat.c#L442-L466, it seems that if the call works with 4/5 and fails with 7.3 probably there is something wrong going either in passing the parameter, or indeed hdf5 support somehow is not enabled (some bug in the vcpkg port?).

hdf5 support somehow is not enabled (some bug in the vcpkg port?).

To double check this, we can try to read a v7.3 mat file. If there is no hdf5 support, you should not be able to read it.

I am not familiar with vpckg's manifest mode (I typically use it in classic mode), but at first glance it does not seems that you enabled the hdf5 feature of matio, can you try with something like (I did not double checked if this is the correct syntax):
{
"$schema": "https://raw.githubusercontent.com/microsoft/vcpkg/master/scripts/vcpkg.schema.json",
"name": "kit",
"version": "1.0.0",
"dependencies": [
"zlib",
"hdf5",
{
"name": "matio",
"features": ["hdf5"]
},
"visit-struct"
]
}

Actually reading better https://github.com/microsoft/vcpkg/blob/5d66a8994296bd141b9bf870edb2b4663975acf9/ports/matio/vcpkg.json#L37C6-L37C11 it seems that hdf5 is in default features, but mat73 no. So I guess you can try with something like:
{
    "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg/master/scripts/vcpkg.schema.json",
    "name": "kit",
    "version": "1.0.0",
    "dependencies": [
        "zlib",
        "hdf5",
        {
            "name": "matio",
            "features": ["mat73"]
        },
        "visit-struct"
    ]
}

Wonderful!  Adding "mat73" feature does work fine to me! Thanks a lot!
Best，
Zheng

Thanks for opening the issue, I think the default settings of matio vcpkg port may be confusing, I opened https://github.com/microsoft/vcpkg/pull/42103 upstream to discuss this.


fix: support CLIs with single top level command

Support CLIs with a single top level command (i.e. the executable is the only command).
With this fix, users will need to do two things:

Place their command at the top level of the commands dir, e.g. src/commands/index.ts
Supply the default in their oclif config, for example

oclif: {
  default: ".",
  commands: "./dist/commands"
}

Fixes #425

Please let me know if the below migration would be correct then:

Add to package.json:

{
  "oclif": {
    "default": ".",
    "commands": "./lib" // as my "index.ts" is at "src/index.ts" and my tsc builds to "lib"
  }
}

Please let me know if the below migration would be correct then:

Add to package.json:

{
  "oclif": {
    "default": ".",
    "commands": "./lib" // as my "index.ts" is at "src/index.ts" and my tsc builds to "lib"
  }
}

That should also work

It works, but the --help now displays two sections (while it should only display the first):
❯ bin/dev --help
Downloads and extracts binaries from compressed packages using a config file

USAGE
  $ bindl . [--version] [--help] [-c <value>]

FLAGS
  -c, --config=<value>  Path to the config file
  --help                Show CLI help.
  --version             Show CLI version.

DESCRIPTION
  Downloads and extracts binaries from compressed packages using a config file

  The config will be read from any valid config file in the current directory. The configuration file can be defined
  using all the extensions and names accepted by cosmiconfig, such as bindl.config.js

Downloads and extracts binaries from compressed packages using a config file

VERSION
  bindl/2.0.0 wsl-x64 node-v16.15.1

USAGE
  $ bindl [COMMAND]

COMMANDS
  .  Downloads and extracts binaries from compressed packages using a config file

Another issue:
bindl . triggers the command too (while it should actually pass . as argument to the main command.

@felipecrs I push a commit last night that should resolve the issues you're seeing - let me know if that works better for you


NIFI-5826 Fix to escaped backslash

Fixing escaped backslash by unescaping it in java just before compiling regex.
For a consistency with expression language regex-based evaluators, all record path operators will follow the same escape sequence for regex. Single backslash should be defined as double backslash.
Examples:

replaceRegex(/col1, '\s', "_") - will replace all whitespaces (spaces, tabs) with underscore.
replaceRegex(/col1, '\.', ",") - will replace all a period with
replaceRegex(/col1, '\\', "/") - will replace backslash with forward slash

EL References: StringLiteralEvaluator. Special characters (backslash sequences) will be handled for any string literal value, and will affect the way regex and escaped chars must be defined. Same logic has been added to RecordPathUtils.unescapeBackslash.

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

+1, LGTM


Repeating Cycle

Before jumping into Pr first comment for assign.
Problem statement: Below is an example of a repeating cycle.
isRepeatingCycle([1, 2, 3, 1, 2], 3) => true
// Since the first two elements of [1, 2, 3] equals [1, 2]

Check Link for Full Question
Probelm Link: https://edabit.com/challenge/q8aKKcukixHhcH7n4

Before submitting a PR please Check some details.

[ ] fileName formet should be in camelcase
example- returnTheNextNumber.py
[ ]  Choose label for Problem , example- "good first issue", "easy"
[ ]  In file there should be problem statement and link to problem

/* Problem-Task : This program will add two numbers
 * Problem Link : https://edabit.com/challenge/SFzHtm63XT6EYNHWY
*/
int main() {
    int bla;
    return 0;
}

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

Can I work on this?

@vamsireddy22 assigned,
Best of Luck,


Cannot replicate the result in the multimodal_tutorials

Hi,
We tried to replicate the results in the multimodal_tutorials, but the spatial clustering result was not as good as the one in the tutorial. Would you provide some suggestions? Please find the model evaluation below. Thanks!
The clustering results from our end,

Result from the tutorial,

Training outputs,
Stopping early: metric has not improved more than 0.0 in the last 8 epochs.
If the early stopping criterion is too strong, please instantiate it with different parameters in the train method.
Model training finished after 96 min 38 sec.
Using best model state, which was in epoch 38.
--- MODEL EVALUATION ---
val AUROC score: 0.9870
val AUPRC score: 0.9787
val best accuracy score: 0.9578
val best F1 score: 0.9589
val target rna MSE score: 6.1840
val source rna MSE score: 1.6078
val target atac MSE score: 0.3834
val source atac MSE score: 0.1222

Hi @dyxmvp,
Did you use the same hyperparameters as in the tutorial? Looking at your evaluation, it looks to me that the model finished quite early (38 epochs) and the MSE scores seem quite high for this dataset. Maybe the model ran into an unlucky optimization.

This was related to a bug in the random seed configuration. We fixed it now.


Fix the API queries for certain things

In particular, the WikiaPage class' summary attribute checks for something that is not present in Wikia's API. However, the summary function does the correct functionality (searches for the page then returns a portion of it), so that needs to be incorporated into the class property as well

Pretty much fixed for the most part by now, there might be a few bugs lying around for malformed queries that I haven't quite fixed yet, but they are no longer so numerous that I need this abstract issue.


Convert Appsec deployment into daemonset for high availability

Thanks @he2ss for implementing Appsec into the Crowdsec helmchart. This PR builds upon #189 and turns the Appsec deployment into a daemonset for high availibility.
Other changes:

RegistrationToken generation is moved into _helpers.tpl. It can now also be passed through values.yaml
appsec-daemonSet.yaml is structured more like agent-daemonSet.yaml
Added the appsec auto_registration config into values.yaml

/kind enhancement
/area configuration

Hi @srkoster,
Thanks for this contribution. Isn't it better to let it on deployment, as it suits better if you want to configure HA?
If you have many nodes and don't want to deploy an appsec per node, you will have to play with annotations. Instead, having a deployment with replicas can be better, IMO.

@he2ss sounds reasonable.
I decided to implement the daemonset as the agent was also deployed as a daemonset. I see that the newest chart version allows the user to make a choice between deployment and daemonset. Does it make sense to bake the same choice into appsec?

Closing this PR in favor of #208


Publish source: Warn if publishing source and there are module references that don't use aliases

... unless they're to the public bicep registry

ISSUE: Need to have a way to disable this warning?


[driver/s3] Use aws/aws-sdk-go instead of goamz for s3 driver and cloudfront

I didn't change any of the s3 driver logic, only the s3 client calls to use this other library.
Caveats: V2 auth not supported, EC2 file credentials untested, cloudfront untested.
Some very unscientific tests show a 45% time reduction for running the s3 driver tests on my local computer as compared to master, and a 40% time reduction as compared to #1381 (connection pooling enabled).

@BrianBland Great looking numbers.
Would it be a good idea to adopt this as a separate, experimental driver (say, aws-s3) so we don't force people over immediately?

Definitely +1 on not forcing the new code on people.
Either a new, differently named driver, or a flag/config value in the existing driver (legacyCode: true) that would toggle it, and that we can default to false in the future.

Definitely +1 on not forcing the new code on people.

Not initially. We just don't know how stable this is. Long term, I don't want us to maintain two copies. :smile_cat:

Long term, I don't want us to maintain two copies.

Surely not :) - as soon as the "new" one would be stable enough, the other one would instantly become "unmaintained, use as-is".

After fixing the connection pooling in docker/goamz, the performance wins in this client change are no longer statistically significant in my testing. Whereas this does seem to have a much better v4 auth implementation, I'd rather stick with the known functional s3 client (goamz) over the auto-generated aws-sdk-go for now.

Updated to keep both s3 drivers, registers new one as "s3" and "s3aws", registers old driver as "s3goamz"

Current coverage is 51.08%

Merging #1385 into master will decrease coverage by -6.17% as of b678b3f

@@            master   #1385   diff @@
======================================
  Files          123     124     +1
  Stmts        11338   11739   +401
  Branches       798     711    -87
  Methods          0       0
======================================
- Hit           6492    5997   -495
+ Partial        798     711    -87
- Missed        4048    5031   +983

Review entire Coverage Diff as of b678b3f

Uncovered Suggestions

+0.27% via ...ge/driver/gcs/gcs.go#182...213
+0.23% via ...ge/driver/gcs/gcs.go#85...111
+0.22% via .../driver/s3-aws/s3.go#695...720
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Looks like hundreds of the files being added in this PR are from the corpus of the fuzz test for go-jmespath. Is there any sane way to have godeps exclude these test fixtures? If not, maybe this is a good opportunity to switch to native Go 1.5+ vendoring (vendor subdir).

@aaronlehmann In the meantime I'm willing to manually strip out these fixtures, given that godeps ignores *_test.go files anyway

Godep does not copy:
files from source repositories that are not tracked in version control.
*_test.go files.
testdata directories.

Maybe we can make a PR to go-jmespath to move the test data into a testdata directory?

@aaronlehmann vendoring fix upstreamed through go-jmespath -> aws-sdk-go via aws/aws-sdk-go#538

Nice, that was fast.

Yeah, this really helps boost confidence in using this library instead of goamz

rebase please :credit_card:

Rebased

This will need another rebase to pick up the build fix.  :crying_cat_face:

Added support for custom UA strings, storage classes (reduced redundancy)

LGTM
This PR also uses aws-sdk-go for cloudfront URL generation for which we don't test.   It might be a good idea to have a fallback somehow or verify the URLs are the same as before.  I'll leave that up to you.

Good call, still working on testing the cloudfront signer now

@RichardScothern confirmed cloudfront middleware is working, also added a bit of extra code for handling incomplete "baseurl" fields (adding the scheme and trailing slash)

registry/storage/driver/s3-aws/s3.go:4

// This package leverages the AdRoll/goamz client library for interfacing with
// s3.

LGTM after comment fix

@dmcgowan updated package comments for both S3 drivers

LGTM


Multiple Accept headers are pulled out as 1 item causing Contains to fail

When a client sends in multiple values in Accept header doing a check on that header fails the Contains method.
Looking at the Accept header it is a StringValues type which implements the many ICollection,IList,IEnumerable etc interfaces and the value of the Accept header is 1 entry with a string separated by comma.  Therefore a IList.Contains will fail because there isn't an entry that matches application/json when the entry is application/json, text/plain, */*
I would have expected 3 entries in the result of calling context.Request.Headers["Accept"] which would have made the check pass.  For now I will have to use context.Request.Headers["Accept"].Any(h => h.Contains("application/json")) or context.Request.Headers["Accept"].ToString().Contains("application/json"))
Attached is a screenshot of my debug window which shows what I saw.

The indexer returns the raw values as received by the server. If you want a specific format you need to ask for it. E.g. context.Request.Headers.GetCommaSeparatedValues(HeaderNames.Accept);
https://github.com/aspnet/HttpAbstractions/blob/1.0.0/src/Microsoft.AspNetCore.Http.Abstractions/Extensions/HeaderDictionaryExtensions.cs#L40

Why isn't there a context.Request.Headers.Accept that returns an array for example?
I'm also not sure why the decision was made to return it as a string as the indexer returns a type that implements numerous array interfaces so surely the expectation would be to expect multiple entries

@jchannon I'm assuming the multiple values are supported because there may actually be more than one Accept header "line" in the request message.  The System.Net.Http libraries took care of merging multiple header lines into a single array of media type ranges.
@Tratcher It is unfortunate that we require the end user to know how to standardized headers like Accept are delimited.  How would someone split user agent products and comment tokens as they are space delimited but comments also allow spaces within them?

See https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Extensions/HeaderDictionaryTypeExtensions.cs#L16
https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Extensions/RequestHeaders.cs#L24

Would using those extensions return multiple items in the array?

I think, once again, this problem boils down to "pay to play". If you don't want/need parsing of header values, the framework will allow you to get the raw values. The question is; should the defaults be the other way around, i.e. the framework optimizes for the 90%* that need separated values, but gives the other 10%* an API that allows you to "drop down" to raw values?

numbers pulled out of my ass

I think the default should return them as an array and merge them if the client sends multiple Accept headers.  The API of the headers collection returns StringValues which is an array. If it was string then it would be understandable why I got them all as one string value but its not so therefore if the API is an array I expect multiple entries in the array

I see at least two problems with that expectation.
First, you're using the lowest level API and expecting it to have knowledge of every possible header format. If you were accessing an Accept property then yes it would make sense that it would know the format. The comments above about the user agent header underscore this well, and then there are custom headers. Making broad assumptions at the lowest level makes those assumeptions impossible to work around when they go wrong.
Second, comma splitting is only the first level of structure.  Not to mention other issues like case normalization, wildcards, etc..
Even if we did this one thing for you here, you would still need a much deeper API to correctly evaluate the headers.

@Tratcher Because StringValues can represent zero, one or many string values, it's hard to know whether StringValues.Contains has string.Contains or string[].Contains semantics. Today, it's the latter, i.e. "any value is equal to", but if it has only one value, like text/html, application/json, application/xml, you'd expect Contains("application.json") to return true.

The current solution seems like an ideal approach to me.  The StringValues primitive is a bit weird, but it solves the problem of duplicate headers.  It also allows a proxy to maintain arbitrary duplicate headers if it wants to.
Parsing the headers into semantically meaningful things should be a secondary and optional thing.  This is one of the major advantages of these HttpAbstractions over the System.Net.Http stuff where you couldn't avoid paying the price of doing the semantic parsing of everything.

One other thing I see as a bit odd is requiring a higher level package to do the behaviour I'd expect at the lowest level but it is what it is I guess

@khellang I see the StringValues that comes from  request.Headers dictionary as being equivalent to this https://tools.ietf.org/html/rfc7230#section-3.2  where field-content may be zero, one or many values.
@jchannon The semantic parsing is still in the HttpAbstractions package.  The typed headers effectively provide the interpretation as per RFC 7321-5.  I think the distinction between the raw header value and the parsed content is a valuable one.

@darrelmiller Exactly, but if you call request.Headers["Accept"].Contains("application/json") and the Accept header is text/html, application/json, application/xml, what would you expect it to return? true or false?

@darrelmiller the typed headers are available in another package Microsoft.AspNetCore.Http.Extensions I believe

@khellang Doing simple string matching on HTTP headers is asking to introduce subtle bugs. I'm not sure how you convince people not to do that though.  If the Accept header was just application/json then the Contains() would work!  I think having access to the unfolded headers is worth the extra parsing step.  Especially because this is a the HttpAbstractions layer.  Frameworks can do pretty stuff on top of this stuff if they like.
@jchannon My bad, I saw package and thought repo, not Nuget.

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


setup-env: update yarn command line

using yarn install --offline --pure-lockfile --check-files
instead of
yarn install --offline --pure-lockfile
yarn check

as suggested by @fitiskin  in https://github.com/oVirt/cockpit-ovirt/issues/23
for solving build issues on CentOS Stream 9.
Signed-off-by: Sandro Bonazzola<EMAIL_ADDRESS>

/build rpm


New-AtwsAttachment adds timezone difference twice

New-AtwsAttachment adds timezone difference twice.

A fix is in the Development branch

Fixed from version <IP_ADDRESS>


Ingest all the uncatalogued accessions through Archivematica

[x] Fix downloads in the "Archival storage" tab
[x] Kick ClamAV off the shared instance
[x] Look at using bulk Elasticsearch index APIs

Waiting for a decision from the archivists about whether we want to use disk images for everything or just the big packages.

Sticking some progress on this ticket:

We're going to use disk images for really big accessions (>5000 files), but for other things Archivematica is coping okay, if quite slow.

We've had to make a bunch of changes to Archivematica along the way, including:

tweaking timeouts
updating/reverting stuff that was changed when we did the rebase; in particular a bunch of async code got removed that we were relying on
tweaking CPU/memory limits to make it more robust

I still don't fully understand all the issues we've had, but it's good enough for our use.

I have a spreadsheet of all the 37 existing accessions we need to migrate (at least, when we started this project). It gives you an idea of where things currently stand:

Archivematica is fairly stable at this point, so I'm going to close this ticket and create individual tickets for the remaining accessions, which are moving more slowly.


JVM implementation frontends code is slow and used up loads of memory and result in stack / memory overflow

After the recent update of the JVM frontends code, the execution time and memory usage is increased significantly, which sometimes result in out of memory and stack overflow. Double check of the logic and settings are needed to ensure the code run in acceptable time and resources.

Concrete example of this:
[Callgraph] Analysing method: mayThrow
[Callgraph] Analysing method: isSuper
[Callgraph] Analysing method: replace
Exception in thread "main" java.lang.StackOverflowError
        at ossf.fuzz.introspector.soot.CustomSenceTransformer.calculateDepth(CallGraphGenerator.java:410)
        at ossf.fuzz.introspector.soot.CustomSenceTransformer.calculateDepth(CallGraphGenerator.java:412)
        at ossf.fuzz.introspector.soot.CustomSenceTransformer.calculateDepth(CallGraphGenerator.java:412)
        at ossf.fuzz.introspector.soot.CustomSenceTransformer.calculateDepth(CallGraphGenerator.java:412)

Is this solved @arthurscchan ?

Merged two recursive functions to one in #837.


[QA] 1.1 QA Phase

QA for ETT is officially kicked off!
Current linked issues:

#30

I think QA is clear. Beginning release prep!


e.isLid is not a function

Error thrown when trying to check if a number is WhatsApp user or not. This may be caused by whatsapp web upgrade.
Error: Evaluation failed: TypeError: e.isLid is not a function on getNumberId

Related PR in whatsapp-web.js: https://github.com/pedroslopez/whatsapp-web.js/pull/1571


Build both MKL and BLAS variants

Build both MKL and BLAS variants.

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:37: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:37: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found


BEV's evaluation encoutered error on AGORA dataset.

Hi, Doc. Sun. It's me again. :-). This time when I run BEV's test on AGORA, the BEV's module somehow encountered 'no attribute' error. More specificly, the setting of module BEV had no attribute called show_items. Detailed infomation shows as below when I run eval_AGORA.py.
Using BEV. Threshold for positive center detection: 0.15 Traceback (most recent call last):   File "/home/gpu/content/ROMP/simple_romp/evaluation/eval_AGORA.py", line 125, in <module>     get_results_on_AGORA(set_name)   File "/home/gpu/.local/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 28, in decorate_context     return func(*args, **kwargs)   File "/home/gpu/content/ROMP/simple_romp/evaluation/eval_AGORA.py", line 110, in get_results_on_AGORA     model = BEV(default_eval_settings)   File "/usr/local/anaconda3/lib/python3.8/site-packages/bev/main.py", line 94, in __init__     self._initilization_()   File "/usr/local/anaconda3/lib/python3.8/site-packages/bev/main.py", line 111, in _initilization_     self.visualize_items = self.settings.show_items.split(',') AttributeError: 'Namespace' object has no attribute 'show_items'
Hope for your answer. 👍

Hi, @Rabbit314271,
Thanks for reporting the bug again.
I have submited a commit to fix this bug.
Check this:
https://github.com/Arthur151/ROMP/commit/376baf788fdb67f36d6b11dde1dcbdd388c11072
Please update the code.

Thank you very much for fixing the problem so quickly.
By the way, in the function save_agora_predictions_v6(line 79) of eval_AGORA.py, the input dict outputs should contain keys like body_pose(to be used in line 94& line 97) or 'global_orient' (to be used in line 96). However, when I print all the keys of the input dict outputs, it only contains :
params_pred, pred_batch_ids, center_confs, cam, smpl_thetas, smpl_betas, cam_trans, verts, joints, pj2d_org,
As a result, it will report a keyerror :
Traceback (most recent call last):   File "/home/gpu/content/ROMP1/simple_romp/evaluation/eval_AGORA.py", line 128, in <module>     get_results_on_AGORA(set_name)   File "/home/gpu/.local/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 28, in decorate_context     return func(*args, **kwargs)   File "/home/gpu/content/ROMP1/simple_romp/evaluation/eval_AGORA.py", line 124, in get_results_on_AGORA     save_agora_predictions_v6(image_path, outputs, prediction_save_dir)   File "/home/gpu/content/ROMP1/simple_romp/evaluation/eval_AGORA.py", line 96, in save_agora_predictions_v6     for ind in range(len(outputs['body_pose'])): KeyError: 'body_pose'
Hoping for your answer. :-)

Thanks for the bug reporting.
Sorry I don't have the resource to test the code now. The bug is supposed to be fixed in last commit:
https://github.com/Arthur151/ROMP/commit/a316fc475877677f3506b24628b8690ff21307be

OK! Now, everything functions well! Thank you very much for all these effort!

@Rabbit314271
Thank you for reporting these bugs.
Have a nice day.
Best


Show error message when datavault server is not connected

Currently, the UI just doesn't render if you go to a /grapher/ link and the datavault server is not connected.

@maffoo I'm closing this issue. I'd recommend you create a new one regarding auto-reconnect features to be more explicit with the request and we'll mark it v2.1 or similar.


Tweak test commands

Describe your changes
Split jest configs into standard and next.js specific files. This allows me to run yarn test --watch or yarn test:next --watch locally.
Checklist before requesting a review

[X] I have performed a self-review of my code
[X] If it is a core feature, I have added thorough tests.

I'll help with the conflicts 😉


Move athena and redshift MakeDatasourceFactory into grafana-aws-sdk

The athena and redshift plugins got the same fix (https://github.com/grafana/athena-datasource/issues/314) for a shared credentials caching issue but this introduced some duplicated code and of course won't help any new datasources based on the sdk. The duplicated function should be refactored to work generically and moved into the sdk, then athena and redshift should be updated to use it.

Moving this back to the back burner in favor of mulitenancy work.


back2source: Run pipeline for Ruby source and gem packages

For Ruby, the .gem file is the deployed binary. Our focus is on the files within the data.tar.gz archive in the .gem file. These files are a subset of the development codebase, and by checking the checksums between them, we can confirm the mapping. Since the "map_deploy_to_develop" pipeline already handles extract_archives and map_checksum, I believe the current pipeline manages Ruby's back-to-source process well.
I tried with https://rubygems.org/gems/devise and it's working fine.
@pombredanne any comment?

@chinyeungli I still would want to have a specific option for Ruby. There are some cases where ruby gems have native code and the d2d will not work just off checksums. See for instance https://tristanpenman.com/blog/posts/2018/08/29/writing-a-gem-with-native-extensions/

Created a packages list that can be used for testing
ruby_projects_list.xlsx

I tried 10+ projects and most of them have exact sha1 match between deploy and devel.
There is one exception, that I found so far, nokogiri-1.17.2.gem
In this gem file, it contains the following 2 libraries which don't exist in the development codebase:
gems/nokogiri-1.17.2.gem-extract/data.tar.gz-extract/ports/archives/libxml2-2.13.5.tar.xz
gems/nokogiri-1.17.2.gem-extract/data.tar.gz-extract/ports/archives/libxslt-1.1.42.tar.xz

In addition, there is no references for these 2 libraries anywhere in the output (the "DEPENDENCIES" worksheet is empty).
I guess we need to do something about this?
The nokogiri-1.17.2.gem has some .c and .h files and those also exist in the development codebase (with sha1match).
Is this the native code that you mentioned about?

I guess we need to do something about this?
...
Is this the native code that you mentioned about?
This is an issue indeed and something to handle as a problem for upstream!
@chinyeungli Excellent find

This is the kind of ghost embedded 3rd-party packages that matter a lot!

these could be vulnerable though luckily here https://public.vulnerablecode.io/packages/search?search=libxml2%402.1 and there https://public.vulnerablecode.io/packages/search?search=libxslt%401.1 , other versions are affected.
the license may be different. Can you check the high level licenses differences between the gems and nokogiri (though this may be documented at https://github.com/sparklemotion/nokogiri/blob/main/LICENSE-DEPENDENCIES.md and well known then?)

the license may be different. Can you check the high level licenses differences between the gems and nokogiri (though this may be documented at https://github.com/sparklemotion/nokogiri/blob/main/LICENSE-DEPENDENCIES.md and well known then?)

both are under mit as same as nokogiri


Add support for identity functions

I've added identity function support, screenshot below

You can also undo from a ["get", "property_name"] expression back to a identity function.
Demo https://2490-84182601-gh.circle-artifacts.com/0/artifacts/build/index.html
Fixes #640

Works great @orangemug :+1:
Should we also add Fx to the "Convert to expression" button to have consistency with all the other fields?

@pathmapper do you mean something like this?

I also add a 'add row' icon to the 'add stop', thoughts?

Yes, that is exactly what I had in mind @orangemug
The 'add stop' looks also nice :tada:

Yay merging!


net/udpbroadcastrelay plugin - Initial commit

udpbroadcastrelay - a plugin to control the daemon of the same name. The original daemon was called udp-broadcast-relay-redux, that daemon has been modified to better suit our purposes and is ready to be uploaded to wherever I am told to send it.
This plugin handles all the configurations required for multiple instances and displays those instances status in the services status UIs.
Usage is simple, port, Instance ID - which is also used as part of the pid, multicast address if used and drop down select of the interfaces to use. Source address is also an option for the likes of Chromecast.
The daemon is included in this commit for testing purposes only.

Added multiple multicast address options and use original TTL as Identifier for echoed packets if needed. Now default uses new DSCP to identify the packets and leaves TTL untouched.

@mimugmail do we have any timelines as to when this may make production. Really useful plugin for those of us using vlans.

@nivek1612 there are some things in this PR still unclear (ts, double back space, binary blob, copyrights)
@marjohn56 I'm sure I already asked in IRC but cant find it. Where on github is the source you are using in the ports PR? Adding code to ports tree directly is not allowed, only patches. I can try to build a correct makefile and maybe also upstream to FreeBSD itself

https://github.com/marjohn56/ports/tree/udpbroadcastrelay

@marjohn56 can you create a new own repo and upload the code?
There should be no relation to the whole ports tree.

https://github.com/marjohn56/UDPBroadcastRelay

I don't want to be picky or offend, but:

can you please make it lowercase only
tag a release number
check if the previous license was bsdclause-2 and if not, get a permission to change
add this to your makefile

all:
        $(CC) $(CFLAGS) -g main.c -o udpbroadcastrelay
        cp udpbroadcastrelay /usr/local/bin/
        chmod 755 /usr/local/bin/udpbroadcastrelay

OK, done...
https://github.com/marjohn56/udpbroadcastrelay
Just one thing, the scripts call sbin/udpbroadcastrelay not /bin, so it needs changing here or there... I care not which.
Cheers...

Can you recheck? I can't find the repo. If sbin is ok then just place it in the Makefile, it was just a guess from mine. Please keep this PR open and only remove the binary :)

It's there. I've deleted the original repo and the mixed case one and created a new one at this link:
https://github.com/marjohn56/udpbroadcastrelay
I posted it above.

There's a 404 when I click the link and it's not listed in your repo's list.

Try a cache flush. ;)
Alternatively, go here
https://github.com/marjohn56/udpbroadcastrelay/commit/5e07941f44872282b20b792f72417d83e6a339b6

Try it now, for some reason it got set to Private.
https://github.com/marjohn56/udpbroadcastrelay
From: Michael<EMAIL_ADDRESS>Sent: 01 March 2020 05:53
To: opnsense/plugins<EMAIL_ADDRESS>Cc: Martin Wasley<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [opnsense/plugins] net/udpbroadcastrelay plugin - Initial commit (#1677)
There's a 404 when I click the link and it's not listed in your repo's list.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/opnsense/plugins/pull/1677?email_source=notifications&email_token=AEJBPJSDENGUUNH22RWESQ3RFHZ2DA5CNFSM4KLZREQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENMV3KQ#issuecomment-593059242, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEJBPJQEMGVQHQLBWGYI2YTRFHZ2DANCNFSM4KLZREQQ.

Thanks, looks better now.
Can you please tag a release?

Not sure what you mean, I could of course just be being thick. You want a version in the source itself?
From: Michael<EMAIL_ADDRESS>Sent: 03 March 2020 08:07
To: opnsense/plugins<EMAIL_ADDRESS>Cc: Martin Wasley<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [opnsense/plugins] net/udpbroadcastrelay plugin - Initial commit (#1677)
Thanks, looks better now.
Can you please tag a release?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/opnsense/plugins/pull/1677?email_source=notifications&email_token=AEJBPJTWNLU5W5VTY6FQOALRFS3ATA5CNFSM4KLZREQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENSPSDA#issuecomment-593819916, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEJBPJVS5FMJM5732MH7MP3RFS3ATANCNFSM4KLZREQQ.

In Github you can tag a release, this will be the source for FreeBSD ports system to manage the rest:
https://github.com/opnsense/core/releases
Just tag version 1.0 and I'll do the rest :)

Well you learn something new every day…
Have done so.
From: Michael<EMAIL_ADDRESS>Sent: 03 March 2020 09:22
To: opnsense/plugins<EMAIL_ADDRESS>Cc: Martin Wasley<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [opnsense/plugins] net/udpbroadcastrelay plugin - Initial commit (#1677)
In Github you can tag a release, this will be the source for FreeBSD ports system to manage the rest:
https://github.com/opnsense/core/releases
Just tag version 1.0 and I'll do the rest :)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/opnsense/plugins/pull/1677?email_source=notifications&email_token=AEJBPJRVUM4TGJNV7SCQ2BTRFTD4ZA5CNFSM4KLZREQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENSWXLY#issuecomment-593849263, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEJBPJSK3JAUPJCN5XY75H3RFTD4ZANCNFSM4KLZREQQ.

Thx, can you merge my PR in your repo so I can go on? :)

😊 Is done.
From: Michael<EMAIL_ADDRESS>Sent: 03 March 2020 13:35
To: opnsense/plugins<EMAIL_ADDRESS>Cc: Martin Wasley<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [opnsense/plugins] net/udpbroadcastrelay plugin - Initial commit (#1677)
Thx, can you merge my PR in your repo so I can go on? :)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/opnsense/plugins/pull/1677?email_source=notifications&email_token=AEJBPJUAZNCJ7ASYZNNE4VDRFUBPTA5CNFSM4KLZREQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENTP6HA#issuecomment-593952540, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEJBPJXC57J3QGMUX3DWWRTRFUBPTANCNFSM4KLZREQQ.

@marjohn56 @mimugmail udpbroadcastrelay is in packages come 20.1.3 so do we want this in as well or is it still WIP?

No, it's working nicely. Run it up and try it.

It would be nice to have a devel pkg .. so, please merge.
It needs cleanup for sure ... but easier to work on when in master.

I'd love to know what this cleanup is... pray tell. :)

Makefile needs a PLUGIN_DEPENDS with udpbroadcastrelay (before merge), rc file doesn't really look like a rc file but not really important, Model name "ts" and double back ticks in ServiceController, ItemController seems unused, Copyright in Model, Model mount differs from ACL, volt has stuff from FTP Proxy. The first is a show stopper, rest can be done after merge

I merged some of your stuff last week, the only thing I did not merge was the params, which are needed.

Just tested the source on Github and it no longer works, reverted to my pkg source that's on the forum, works fine. I'll take a look later and see what's causing the problem.

It might be the missing setup.sh which sets the chmod, but this will be done by @fichtner since you can set these chmods in git directly

(and of course the removed binary)

I'll check later, off to do some proper work for a few hours.

What happens on your end when you remove ItemController.php? Does everything still work? I quite sure it's not needed.

My router just exploded!!
Nah.. nothing at all, we'll remove it.

Removed.

Where in the volt do you handle the restart action when changing anything? May I'm blind? Does the daemon restart if you change things?

Yes it does restart, if you have multiple instances they will restart or stop too. Fire it up and add a couple of relays is they way to see whats happening, if you only have one LAN then create a a VLAN or two and add a couple of instances on different ports or multicast addresses.

Think it may be time to close this PR and issue a new clean one, far too much traffic here I think.

I don‘t mind, will squash at the end.

On 10. Mar 2020, at 17:19, Martin Wasley<EMAIL_ADDRESS>wrote:

Think it may be time to close this PR and issue a new clean one, far too much traffic here I think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

OK.. I was doing it to make it easier to see what was going on, but if you are happy to leave it be then so am I. :)

What's the current status here? The binary is already available with 20.1.3.
If we merge we could have a devel pkg in 20.1.4 to go out for testing :)

bump... anything happening with this or shall I just squash it to make it quicker to pull?

I installed your branch locally here. After adding one instance I got this in configd.log:
Apr 15 14:11:58 OPNsense configd.py: [692e0c30-c724-46a4-b960-aeee1105d1f2] get udpbroadcastrelay instance status
Apr 15 14:11:58 OPNsense configd.py: [692e0c30-c724-46a4-b960-aeee1105d1f2] returned exit status 126

Then I set chmod 755 to rc sciript (which @fichtner will take care of after merge) and then I got:
Apr 15 14:12:49 OPNsense configd.py: [107f3740-9299-448a-89e7-1a84777c681a] get udpbroadcastrelay instance status
Apr 15 14:12:49 OPNsense configd.py: [107f3740-9299-448a-89e7-1a84777c681a] returned exit status 1

I could only start it via dashboard -> services -> UDP Broadcast Relay (which needs description).
Then everything seems to work.
Volt looks a bit different than the ususal plugins but it works :)
@fichtner for devel pkg for me it's ok :)

Merged, thanks. Some cleanups follow.

Yes. it needs the kick from the services start for the first time. There is a doc for it, I think it's already been PR'd


Fix #272. Blob types should be accessible via byte[]

This should fix the regression in #272
ping @singingbush let me know if this is suitable for your project, or if we need more types to be included.
I haven't tested this yet, so will wait for CI to see if I made any mistakes!

ping again @singingbush, any comments? If I don't hear from you for a few days, I'll just merge this and close the issue.

Sorry been hectic recently. I'll try it out tonight and get back to you

I've looked through the PR and it seems reasonable but I've not run locally. I noticed that there are now tests for byte[] and ubyte[] so that seems fine.
I was also trying to get it to work with std.datetime.systime.SysTime as an alternative to std.datetime.date.DateTime. SysTime includes timezone which makes it useful if using the timestamp type in MySQL.
According to MySQL docs:

MySQL converts TIMESTAMP values from the current time zone to UTC for storage, and back from UTC to the current time zone for retrieval. (This does not occur for other types such as DATETIME.) By default, the current time zone for each connection is the server's time.

So being able to retrieve columns as SysTime would be handy

SysTime includes timezone which makes it useful if using the timestamp type in MySQL.

If this is a new feature, and not an already-existing feature, can you open a new issue on it? I want to focus and making sure existing code doesn't break for this release. I agree, returning a SysTime might be useful. We do have a custom mysql Timestamp type, but I admit I never used it.
If it does work in 3.1.0, can you give me an example?

@SingingBush let me know if there are other problems that need addressing. Will push a new release.


Compiler errors from Boost.Asio and Boost.Beast -- Help needed

Version of Beast
Version 189 for the one in Boost distribution, and 228 for the one cloned from the GitHub repository (I'm using the former one, but I needed the latter as well for boost::beast::ssl.hpp).
Steps necessary to reproduce the problem
As the title says, I have errors that keep it from compiling and that's my problem.  The code is here and my server_certificate.hpp file is here.
I got the certificate from Let's Encrypt using the TXT record method, and it's a domain-specific certificate.  I was told by the guys at Let's Encrypt forums that it doesn't require DH parameters, but I'd like to confirm here if it's true or not.  I didn't get DH parameters.  It's a certificate issued via acme.sh.  The domain name is a subdomain I got for free from dynu.com; the .cer files I have are ca.cer, {DOMAIN}.cer, and fullchain.cer.  I was told that I'd need fullchain.cer so I put that in as the value for the cert string (it consists of two certificates and I used both).  The private key I have is in a .key file rather than a .pem file and I'm wondering if that's a problem.  I also need to ask what I need to do with the ctx.set_options and ctx.set_password_callback methods.
All relevant compiler information
This Gist includes the entire compiler output I got.  I'm using Visual Studio Community 2017 with the latest update and I have the MSBuild diagnostics level set to "classic" which gives you information about the whole development environment in addition to errors, warnings and line numbers.  So it took more time to complete the build attempt and the resulting output message is also a lot longer.  Sorry about that.
Thanks in advance for any replies and/or help.

You can't use Boost 1.69 with Beast 228 - you have to use the same version of boost and beast.

Thanks for the reply.  There were still errors and I can't choose to include only Asio from the Boost 1.69.0 (in the project's include directory setting in the IDE), so I had to completely give up on HTTPS (again).  I wanted to do it this time because I needed both my portfolio website (hosted with HTTPS on GitHub Pages) and the web server app to both be on HTTPS to avoid conflicts.  Otherwise I couldn't make a request to the web server app from my portfolio site to see if the web server app is running.  I'll just have to manually change the note for the web server app in my work.html page to say if it's running or not, now.
Anyway, right now it's running and you can find it at this URL: http://dragonosman.dynu.net:5501/ .  It uses a Google Map GUI with geolocation to open an info window with a currency conversion form at the user's location with the "to" currency in the form set to the one used at that place.  If geolocation isn't working, like if either the user didn't give permission or the browser doesn't support geolocation to begin with, the user will see an error but could just click anywhere on the map to get the info window with the HTML form on it and the "to" currency dropdown will be set to the one used at that location.  There are exceptions, though, since there are places that don't work--note on info window tells you which ones they are (the note doesn't come up when the error about geolocation not working is displayed--I should probably change that).
Sorry about the shameless advertising.  I wanted to say it since the app uses Beast server and client code.

I've decided to use the latest version, each, of the Boost.Asio and Boost.Beast from their respective GitHub repositories.  That way there should be problems aside from SSL certificates.
I'll ask back if I still have problems regarding the SSL certificates.

@vinniefalco I got it to build successfully.  But I still can't connect securely to the web app in my browser (it doesn't give me the warning that I might be being fooled about the site using HTTPS--it's a different message and it appears on the webpage itself).  You can see my .cpp file here; the server_certificate.hpp file is the same as before (from when I linked to it here).
Also, when I tried to visit the app in my browser, I got these messages in the console window:
handshake: The file handle supplied is not valid
handshake: The file handle supplied is not valid
handshake: An operation was attempted on something that is not a socket
handshake: The file handle supplied is not valid
handshake: The file handle supplied is not valid
handshake: An operation was attempted on something that is not a socket

What did I do wrong?  And is this something I should be asking at the Boost.Asio repository or is here fine too?
By the way, there were some linker errors I was getting because of OpenSSL libs that I was able to solve by adding this:
#ifdef WIN32
#pragma comment (lib, "crypt32.lib")
#endif

Just adding it here for reference.

Okay, I've opened the issue here and also sent an email about the problem to the Boost Users mailing list (just in case), so I'm closing this issue.  Sorry about this and also for bothering you.


how to set http proxy and socks proxy

my network is not directly allow  Binance API,how to set proxy in HummingBot

Hi @jiangxch please be advised that the foundation team does not support using any sort of vpn or equivalent to private networks. However we would suggest to ask our community discord for possible workaround. Thank you


Kotlin Multiplatform example + multiproject

Currently, I think it hasn't multiplatform support:
Extension of type 'SourceSetContainer' does not exist. Currently registered extension types: [ExtraPropertiesExtension, LibrariesForLibs, VersionCatalogsExtension, RootProjectAccessor, CoverallsJacocoPluginExtension, Grgit, ReckonExtension, ChangelogPluginExtension, ReportingExtension, DetektExtension, ApiValidationExtension, JacocoPluginExtension, NexusPublishExtension, DefaultArtifactPublicationSet, NodeJsRootExten
sion, YarnRootExtension]


Next Button on Add Members screen will not do anything

Description
After clicking the button (btnNextAddMembers.) on the Add Members screen (scrnBuildNew) after I added both owners, nothing happens. If I go to My Requests screen (scrnMyRequests) and go to that draft and click edit, I am able to add owners and click on the Submit Updates button (btnSubmitUpdates_EditRequest) and submit it successfully that way.
Steps to reproduce

Open App
Build New
Enter Private for visibility
Next
Enter Team name and check availability. No team name conflicts
Enter description and business reason
Next
Add myself and another admin to owners.
Next
Nothing Happens.

Expected results
I expect to move onto the final screen after Add Members screen to submit the team creation but next button doesn't do anything on the Add Members screen
Actual Results
After clicking Next on the add members screen, nothing happens.
Solution component
Power App
Operating system (environment)
Windows
Additional Info
**btnSubmitUpdates_EditRequest code is at bottom**

btnNextAddMembers code:

If(
    ('cmbOwners._1'.Selected.Email = 'cmbOwners._2'.Selected.Email) && (CountRows('cmbOwners._1'.SelectedItems) > 0),
    Set(
        Varowandmemnotclash,
        false
    ),
    Set(
        Varowandmemnotclash,
        true
    )
);
If(
    (CountRows('cmbMembers.'.SelectedItems) > 0) && (CountRows('cmbOwners._1'.SelectedItems) > 0) && (CountRows('cmbOwners._2'.SelectedItems) > 0),
    If(
        'cmbOwners._1'.Selected.Email = First('cmbMembers.'.SelectedItems).Email || 'cmbOwners._1'.Selected.Email = Last('cmbMembers.'.SelectedItems).Email || 'cmbOwners._2'.Selected.Email = First('cmbMembers.'.SelectedItems).Email || 'cmbOwners._2'.Selected.Email = Last('cmbMembers.'.SelectedItems).Email,
        Set(
            Varowandmemnotclash,
            false
        ),
        Set(
            Varowandmemnotclash,
            true
        )
    )
);
If(
    CountRows('cmbOwners.'.SelectedItems) <> 2 || (CountRows('cmbOwners._1'.SelectedItems) < 1) || (CountRows('cmbOwners._2'.SelectedItems) < 1),
    Set(
        BNReviewAndSubmit,
        false
    ) && Set(
        BNMembership,
        true
    ),
    If(
        CountRows('cmbOwners.'.SelectedItems) = 2 && Varowandmemnotclash,
        UpdateContext({ScratchlocalStep: ScratchlocalStep + 1}) && Set(
            BNReviewAndSubmit,
            true
        ) && Set(
            BNMembership,
            false
        )
    )
);
If(
    CountRows('cmbOwners.'.SelectedItems) = 2 && (CountRows('cmbOwners._1'.SelectedItems) > 0) && (CountRows('cmbOwners._2'.SelectedItems) > 0) && Varowandmemnotclash,
    Patch(
        'Teams Requests',
        LookUp(
            'Teams Requests',
            RowKey = srowkey
        ),
        {Owners: 'cmbOwners.'.SelectedItems},
        {Members: 'cmbMembers.'.SelectedItems},
        {
            Stage: {
<EMAIL_ADDRESS>"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
                Value: "Requirements"
            }
        }
    )
);
--------------------------------------------------------------------------------------------------------------------------------
btnSubmitUpdates_EditRequest code

If(
    (dcvOwners_EditRequest_1.Selected.Email = dcvOwners_EditRequest_2.Selected.Email) && (CountRows(dcvOwners_EditRequest_1.SelectedItems) > 0),
    Set(
        Vareditowandmemnotclash,
        false
    ),
    Set(
        Vareditowandmemnotclash,
        true
    )
);
If(
    (CountRows(dcvMembers_EditRequest.SelectedItems) > 0) && (CountRows(dcvOwners_EditRequest_1.SelectedItems) > 0) && (CountRows(dcvOwners_EditRequest_2.SelectedItems) > 0),
    If(
        dcvOwners_EditRequest_1.Selected.Email = First(dcvMembers_EditRequest.SelectedItems).Email || dcvOwners_EditRequest_1.Selected.Email = Last(dcvMembers_EditRequest.SelectedItems).Email || dcvOwners_EditRequest_2.Selected.Email = First(dcvMembers_EditRequest.SelectedItems).Email || dcvOwners_EditRequest_2.Selected.Email = Last(dcvMembers_EditRequest.SelectedItems).Email,
        Set(
            Vareditowandmemnotclash,
            false
        ),
        Set(
            Vareditowandmemnotclash,
            true
        )
    )
);
If(
    CountRows(dcvOwners_EditRequest.SelectedItems) <> 2 || CountRows(dcvMembers_EditRequest.SelectedItems) >= 2 || (dcvVisibility_EditRequest.Selected.Value = "Select" || CountRows(dcvVisibility_EditRequest.SelectedItems) < 1) || (IsBlank(Trim(dcvTeamDescription_EditRequest.Text))) || (IsBlank(Trim(dcvBusinessJustification_EditRequest.Text))),
    Set(
        EditRequest,
        true
    ) && Set(
        EJustificationValidation,
        "Business reason can't be empy"
    ) && Set(
        EditRequest,
        true
    ) && Set(
        EDescription,
        "Description can't be empty"
    ) && Set(
        EVisibilityValidation,
        "Select a Visibility option"
    )
);
If(
    CountRows(dcvOwners_EditRequest.SelectedItems) = 2 && (!IsBlank(Trim(dcvBusinessJustification_EditRequest.Text))) && (!IsBlank(Trim(dcvTeamDescription_EditRequest.Text))) && (dcvVisibility_EditRequest.Selected.Value <> "Select" && CountRows(dcvVisibility_EditRequest.SelectedItems) > 0) && Vareditowandmemnotclash && (CountRows(dcvOwners_EditRequest_1.SelectedItems) > 0) && (CountRows(dcvOwners_EditRequest_2.SelectedItems) > 0),
    Set(
        changetosubmit,
        true
    ) && SubmitForm(frmEditRequest) && Notify(
        "Success! Request submitted.",
        NotificationType.Success
    ) && Set(
        EditRequest,
        false
    )
);
If(
    (!IsBlank(Trim(dcvBusinessJustification_EditRequest.Text))) && (!IsBlank(Trim(dcvTeamDescription_EditRequest.Text))) && (dcvVisibility_EditRequest.Selected.Value <> "Select" && CountRows(dcvVisibility_EditRequest.SelectedItems) > 0 && CountRows(dcvOwners_EditRequest.SelectedItems) = 2 && Vareditowandmemnotclash && (CountRows(dcvOwners_EditRequest_1.SelectedItems) > 0) && (CountRows(dcvOwners_EditRequest_2.SelectedItems) > 0)),
    ClearCollect(
        TeamsReqTable,
        Filter(
            'Teams Requests',
            'Created By'.Email = gblUserProfile.mail
        )
    )
);

Hello,
Anyone that can help me on this?

@Luxosity Did you remove and re-add the data sources after you imported the app? Thanks


Arcane Missiles on clearcast

Is it reasonable/possible to add a feature that adds a toggle for using AM when a CC is triggered? Perhaps an additional toggle for second AM to double dip CC proc?
Thanks for the work put in btw.

Done


[BUG] Bad encoded character on connecting HFSQL database

Hi Mark,
Before everything, I want to thank you for all the hard-work you do on creating this useful project.
By the way, we've got an issue on connecting an HFSQL database from Windev by ODBC.
Actually, it runs good on most situations but we've a '�' character replacing every special characters with accent like éêàçèï
In the same time, it is well-displayed with RazorSQL by connecting on the same ODBC connector with the same driver.
Same for another projet on Visual Studio C# with the OdbcConnection class which run properly on connecting to the same ODBC connector with the same driver.
Is there a way to fix that by compiling your code differently ?
Or is that a question of deeper encoding that is not caught in the code ?
I'm running your code under Node v16.15.0.
ODBC Driver is available here : https://pcsoft.fr/st/telec/modules-communs-26/wx26_75p.htm
Best Regards,
Fybo

Another user found this issue as well and figured out a workaround: https://github.com/markdirish/node-odbc/issues/284#issuecomment-1234379530

Thank you buddy, you saved my day ! @kadler


Rig remote should set a mode while doing a frequency scan

when I want to scan a frequency range I may want to set a mode on the rig

fixed in ec8268df34d7bf70903e25fa1be765ddfab878b0 now in devel


connect could be used with a custom store.subscribe method provided as option

Context
Today there was some discussions about the new redux tree view example and this SO question:
http://stackoverflow.com/questions/34981924/performance-issues-with-a-tree-structure-and-shouldcomponentupdate-in-react-re
As I pointed out the solution of Redux examples is fine enough for most usecases but does not scale it the number of nodes is very big. We agree that it's not a good idea in the first place to render a huge list or a huge tree, but it seems the author of the question is still interested in a solution. I don't know if the usecase is valid or an antipattern but I guess it's worth giving the opportunity to render a huge number of items in an efficient way
Solution
As described in my answer if the number of connected items grows too big, then every state change triggers all connected HOC's subscriptions so it does not scale well.
If we want to make it scale better, the HOC subscriptions should only be called when necessary.
If the state slice of node with id=1 is updated, it produces overhead to actually trigger the subscription of the HOC that connects data to node with id=2, because obviously the connected component is not interested at all in this change.
Redux store has a store.subscribe(listener) method, and it is called inside connect
One can easily create a store enhancer that exposes a method like store.subscribeNode(nodeId,listener), which is only triggered when that node, with the provided, id is called. There are multiple ways of triggering this listener efficiently.
The problem is that once we have built this custom optimized subscription system, there's no way to reuse connect to listen to it because the call to store.subscribe is hardcoded here:
    trySubscribe() {
        if (shouldSubscribe && !this.unsubscribe) {
          this.unsubscribe = this.store.subscribe(::this.handleChange)
          this.handleChange()
        }
      }

A flexible solution would be to let the user control hw to subscribe to the store himself, by using connect options for example:
const mapStateToProps = (state,props) => {node: selectNodeById(state,props.nodeId)}

const connectOptions = {
   doSubscribe: (store,props) => store.subscribeNode(props.nodeId)
}

connect(mapStateToProps, undefined,connectOptions)(ComponentToConnect)

The default doSubscribe implementation would be: doSubscribe: (store,props) => store.subscribe() which keeps the current behavior unchanged.
There's one corner case I don't know yet how to solve is when the nodeId props changes over time. It would mean the HOC should then unsubscribe and then resubscribe for the new nodeId. In practice this seems farfetched to do so and I'm not sure it's really worth trying to solve this but if anyone has an idea...
I can make a PR for that, just tell me if it would be accepted or if it seems to much indirection and is not an usecase you want to support in redux.

Let's also consider redux-batched-subscribe of @tappleby
It exposes 2 methods:

store.subscribe is batched (because it's wrapped)
store.subscribeImmediate is not batched

If you use this store enhancer in your project, then all your connect HOC's become batched by default. This proposal would permit the user to connect components in both batched and immediate mode. I don't really have a real usecase for this but maybe it could permit to give some control over the priority the components should render themselves.

If props was an argument we'd have to resubscribe on every componentWillReceiveProps for consistency which would give bad perf.

That's right but I guess it's a very specific corner case as most of us would probably never want to update the subscription without unmounting/remounting.
There's still a solution to this problem:
const mapStateToProps = (state,props) => {node: selectNodeById(state,props.nodeId)}

const connectOptions = {
   doSubscribePropsSelector: props => props.nodeId,
   doSubscribe: (store,nodeId) => store.subscribeNode(nodeId)
}

connect(mapStateToProps, undefined,connectOptions)(ComponentToConnect)

If we use a selector to pick the data we need for the subscription, it gives the opportunity to componentWillReceiveProps to unsubscribe/resubscribe with the new nodeId only when it changes.
However the API becomes harder to use...

There are some other extension points people desire:

https://github.com/rackt/react-redux/pull/194
https://github.com/rackt/react-redux/pull/208

I wonder if there is a way to address these together without complicating the API. This might mean extracting the “core” of connect into an independent low-level function but I'm not sure about the API.

Basically, what if we separated the component in connect from the caching and invalidation logic.

@gaearon a usecase for https://github.com/rackt/react-redux/pull/208 would be to build a React.Perf middleware so that we can take measures for every dispatched action.
If subscription returned a promise resolved on setState callback, then the redux Middleware could be able to know when rendering has ended and measure wasted time that is relative to a given action.
See also this issue that can make it more complicated to build: https://github.com/facebook/react/issues/3611
There's already a not-really advanced middleware that does not take account that renderings can happen in an async way: https://github.com/AvraamMavridis/redux-perf-middleware

Also for my initial custom connect proposal I think another usecase is when we want to bind dom inputs to redux state. It might work well with events on a small app but I guess once the app becomes big, on a mobile device typing in an input triggering hundreds of HOC may be a problem?

@gaearon yes that would be great to provide full flexibility so that we can compose code in the way we want to use it without rewritting/forking the lib.
Also it can be nice to have an experimental API so that you can eventually change your mind later.
I  don't have an API in mind I'll have to digg deeper in the implementation details of connect :)

@gaearon @slorber I have a PR that attempts to address this here: #285. Would be interested in your thoughts. Not ready to merge, but want to know if it is directionally interesting.

@gaearon also it seems there is a community need to run multiple redux stores (https://github.com/reactjs/redux/issues/1385)
It could be nice if we could also pass to the provider a map of stores and if the connect method was flexible enough to permit to select the appropriate store from context

@gaearon @slorber @mhodgson
Was playing around with one attempt at splitting the core connect features into two different HOC: connector and cacher.
https://github.com/jtadmor/react-redux/commit/b829ece0688f71b0b5acb2ed73233f075487d8d6
The basic idea is that cacher should not know at all about the store or where state comes from. It receives all of the old connect() arguments, but doesn't actually hook up to a store. Instead, it requires the following props:
      ownProps: PropTypes.object.isRequired,
      storeState: PropTypes.object.isRequired,
      dispatch: PropTypes.func.isRequired,
    }

Instead of a handleChange method, it will now attempt to calculate mapStateFromProps only when storeState changes or if mapStateFromProps depends on props and ownProps changes. Ditto for mapDispatchToProps.
The connector accepts a wide variety of options:
const {
    store,
    subscribe = true,
    subscribeFromStore,
    subscribeFromStoreAndProps,
    resubscribeIf,
    dispatchFromStore,
    dispatchFromStoreAndProps,
    recalcDispatchIf,
    handleChange,
    pure = true
  } = options

These are designed to give consumers ability to customize the behavior, while falling back to sane default behavior, e.g. store falls back to context.store, dispatchFromStore falls back to (store) => store.dispatch and so forth.
You could call connector()(Component) and it would work just fine.
Regarding updating the subscription on componentWillReceiveProps, I've tried to solve that by allowing the options to specify either subscribeFromStore or subscribeFromStoreAndProps, and optionally allow a resubscribeIf that would look like (props) => props.node_id. This forces consumers to be explicit about whether resubscriptions should ever happen while the component is mounted but also provide fine-grained control.
I based this on suggestions here.
What I'm not sure on is the best API for each. Right now they are separate functions, but still very coupled in that Connector passes down storeState, ownProps, dispatch, and Cacher consumes those. One possibly way to make them more re-usable is to allow, e.g. Cacher options argument to let the consumer specify something like getOwnPropsFromProps = (props) => {} and getDispatchFromProps, getStoreStateFromProps likewise.
The other downside, perf wise, is that we now have two wrapper components instead of one to provide the same basic functionality as before. (This could be mitigated by keeping connect as is, but export the two more modular HOC as well, although that leaves future development a pain).
Let me know if this seems like a fruitful avenue.

At first glance I like the extensibility and decomposition of the problem but I'm not sure it would be nice for performances to have 2 wrappers instead of one, when we already focus on optimizing the single one we currently have.
I don't know what @gaearon exactly had in mind when saying

Basically, what if we separated the component in connect from the caching and invalidation logic.

But I guess the idea is that the caching logic would be an utility function instead of a new wrapper, to avoid degrading performances
See also work being done here: https://github.com/reactjs/react-redux/issues/368

Yes, after having quickly made these changes I'm realizing that some coupling is necessary because if you just subscribe without any filter, you already make way too many setState calls before you even get to the Cacher component.
Perhaps I'll try to organize something like this:
import { cacheMe } from 'react-redux'

// Render function of a HOC
render() {
  cacheMe.apply(this)

  return this.renderedElement
}

But we still have the major problem, I think, that the handleChange method is deeply tied to the implementation details both of the "caching" and the "get new state from store" parts of this component.
So while I could easily see just shuffling a few things around and using a custom method instead of store.connect, something like returning a Promise instead of just calling setState isn't going to be nearly as easy to let the consumer control.

If you look at #405, I've re-implemented connect in such a way that splits caching and connection. It's still a single component, but all the cache maintenance is handled by reselect.

This is now solved via #416 and what's currently published on npm as react-redux@next


Add configuration to the ClusterExtension API for disabling CRD Upgrade Safety validations

A new, optional, field should be introduced to the ClusterExtension API spec for enabling/disabling the CRD Upgrade Safety preflight checks. The default state should be enabled.

PR created in rukpak: https://github.com/operator-framework/rukpak/pull/902

https://github.com/operator-framework/rukpak/pull/902 merged. This added the CRD upgrade safety preflight configuration API into rukpak.
Work to transplant this logic into operator controller is currently blocked by https://github.com/operator-framework/operator-controller/pull/846 and will be tracked by https://github.com/operator-framework/operator-controller/issues/877


Cannot show text in Ubuntu20.04

Text cannot show anything.

Code:
the directory is like
.
├── code.py
└── custom_config.yml

then I ran manimgl code.py which shown below

class OpeningManimExample(Scene):
    def construct(self):
        intro_words = Text("""
            The original motivation for manim was to
            better illustrate mathematical functions
            as transformations.
        """)
        intro_words.to_edge(UP)

        self.play(Write(intro_words))
        self.wait(2)

        # Linear transform
        grid = NumberPlane((-10, 10), (-5, 5))
        matrix = [[1, 1], [0, 1]]
        linear_transform_words = VGroup(
            Text("This is what the matrix"),
            IntegerMatrix(matrix, include_background_rectangle=True),
            Text("looks like")
        )
        linear_transform_words.arrange(RIGHT)
        linear_transform_words.to_edge(UP)
        linear_transform_words.set_stroke(BLACK, 10, background=True)

        self.play(
            ShowCreation(grid),
            FadeTransform(intro_words, linear_transform_words)
        )
        self.wait()
        self.play(grid.animate.apply_matrix(matrix), run_time=3)
        self.wait()

        # Complex map
        c_grid = ComplexPlane()
        moving_c_grid = c_grid.copy()
        moving_c_grid.prepare_for_nonlinear_transform()
        c_grid.set_stroke(BLUE_E, 1)
        c_grid.add_coordinate_labels(font_size=24)
        complex_map_words = TexText("""
            Or thinking of the plane as $\\mathds{C}$,\\\\
            this is the map $z \\rightarrow z^2$
        """)
        complex_map_words.to_corner(UR)
        complex_map_words.set_stroke(BLACK, 5, background=True)

        self.play(
            FadeOut(grid),
            Write(c_grid, run_time=3),
            FadeIn(moving_c_grid),
            FadeTransform(linear_transform_words, complex_map_words),
        )
        self.wait()
        self.play(
            moving_c_grid.animate.apply_complex_function(lambda z: z**2),
            run_time=6,
        )
        self.wait(2)

Error:

ManimGL v1.6.1
[23:55:05] INFO     Using the default configuration file, which you can  config.py:265
                    modify in `~/anaconda3/envs/manim/lib/pyt
                    hon3.8/site-packages/manimlib/default_config.yml`
           INFO     If you want to create a local configuration file,    config.py:266
                    you can create a file named `custom_config.yml`, or
                    run `manimgl --config`

(process:11928): Pango-WARNING **: 23:55:05.548: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 2 char 1

(process:11928): Pango-WARNING **: 23:55:08.591: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 137

(process:11928): Pango-WARNING **: 23:55:08.593: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:08.596: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:09.121: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 137

(process:11928): Pango-WARNING **: 23:55:15.356: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:15.365: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:15.368: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:15.371: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:15.373: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:15.375: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:15.378: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136

(process:11928): Pango-WARNING **: 23:55:15.390: pango_layout_set_markup_with_accel: Attribute 'line_height' is not allowed on the <span> tag on line 1 char 136
~/anaconda3/envs/manim/lib/python3.8/site-packages/manimlib/utils/space_ops.py:155: RuntimeWarning: invalid value encountered in double_scalars
  cos_angle = np.dot(v1, v2) / np.float64(n1 * n2)
[23:55:28] INFO     Tips: You are now in the interactive mode. Now you    scene.py:119
                    can use the keyboard and the mouse to interact with
                    the scene. Just press `q` if you want to quit.

TexText is correct but Text cannot show anything.
Seemingly, line_height exists in pango >1.5. I am not sure if it is the pango version that makes this problem.
So, is there an answer? Thanks.
Environment
OS System: Ubuntu20.04.4LTS
manim version: 1.6.1
python version: python3.8

(this was first reported here: https://github.com/ManimCommunity/ManimPango/issues/88)

This is my bad. Currently Text is using a markup tag including a line_height attribute to control the line spacing, which requires a higher version of Pango. You may comment out the following 3 lines of code for temporary usage:
"line_height": (
    (self.lsh or DEFAULT_LINE_SPACING_SCALE) + 1
) * 0.6,

At here

This is my bad. Currently Text is using a markup tag including a line_height attribute to control the line spacing, which requires a higher version of Pango. You may comment out the following 3 lines of code for temporary usage:
"line_height": (
    (self.lsh or DEFAULT_LINE_SPACING_SCALE) + 1
) * 0.6,

At here

Thanks so much, it works! Now I could use manimgl on ubuntu20.04 perfectly.


UnixSocket Client/Server

Ember's Parser/Encoder logic on top of the Unix Socket Implementation introduced in fs2.
I wanted to make sure we had an issue since this got mentioned recently, and its a fairly straight encoding.

Without taking a look, does this actually need anything special? IIRC fs2's unix sockets also extends SocketGroup so can't you just pass it directly to the ember builders?

I didn't realize that. I'll try that out first.

Woops, I think I put my foot in my mouth. The unix sockets are not a socket group, but an instance of a unix socket is just a socket.

https://github.com/typelevel/fs2/blob/main/io/shared/src/main/scala/fs2/io/net/unixsocket/UnixSockets.scala#L33 - Yeah, I am going to PR it. Its fairly straightforward, but needs a different builder.


Error Base64QRCode in version 1.4.3

After update to version 1.4.3. i have error in:
var base64QrCode = new Base64QRCode(qrCodeData);
The type or namespace name 'Base64QRCode' could not be found

Hi @Sanyasims ,
this "issue" was already discussed in #361. Please read the discussion and my answer over there. If you then still have questions, let me know.


[Enter feedback here]
This:
compare( (void *) & elem1, (void *) & elem2 );
Is very misleading.  It should be this:
int compare( const void *elem1, const void *elem2 );

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 135f5795-2d27-fded-f416-2f5723b85b14
Version Independent ID: 245a2a7a-b1b4-dcc3-9581-9d6101ed0292
Content: qsort
Content Source: docs/c-runtime-library/reference/qsort.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Yeah, that's messed up. I have fixed it and it'll be live tomorrow by mid-afternoon.


pkg/pprof: add CODEOWNER

The package is currently owned by tophat. Let's give it to the last team that touched it.

@aditighag can you please review this PR?


igvm_defs: build error without "unstable" feature

cargo build of igvm_defs fails:
error[E0599]: no associated item named `SEV` found for struct `IgvmPlatformType` in the current scope
   --> src/lib.rs:383:5
    |
368 | #[open_enum]
    | ------------ associated item `SEV` not found for this struct
...
383 |     SEV = 0x04,
    |     ^^^ associated item not found in `IgvmPlatformType`

error[E0599]: no associated item named `SEV_ES` found for struct `IgvmPlatformType` in the current scope
   --> src/lib.rs:387:5
    |
368 | #[open_enum]
    | ------------ associated item `SEV_ES` not found for this struct
...
387 |     SEV_ES = 0x05,
    |     ^^^^^^ associated item not found in `IgvmPlatformType`

For more information about this error, try `rustc --explain E0599`.

If works, if the unstable feature is set: cargo build -F unstable

Interesting... let me take a look. What's curious is CI didn't catch this, so we probably need another update there to test building without this feature.

Aha it's because of how open_enum handles expansion... Let me see if i can device a fix, i think it needs to propagate the corresponding cfgs to the debug impl...
// Recursive expansion of open_enum macro
// =======================================

#[allow(clippy::exhaustive_structs)]
#[doc = " Enum describing different isolation platforms for"]
#[doc = " [`IGVM_VHS_SUPPORTED_PLATFORM`] structures."]
#[doc = " cbindgen:prefix-with-name=true"]
#[doc = " cbindgen:rename-all=ScreamingSnakeCase"]
#[repr(transparent)]
#[derive(
    ::core::cmp::PartialEq, ::core::cmp::Eq, AsBytes, FromBytes, FromZeroes, Clone, Copy, Hash,
)]
pub struct IgvmPlatformType(pub u8);

#[allow(non_upper_case_globals)]
impl IgvmPlatformType {
    #[doc = " Native platform type without isolation."]
    pub const NATIVE: IgvmPlatformType = IgvmPlatformType(0);
    #[doc = " Platform type of Hyper-V\'s which supports VSM isolation."]
    pub const VSM_ISOLATION: IgvmPlatformType = IgvmPlatformType(1);
    #[doc = " AMD SEV-SNP."]
    pub const SEV_SNP: IgvmPlatformType = IgvmPlatformType(2);
    #[doc = " Intel TDX."]
    pub const TDX: IgvmPlatformType = IgvmPlatformType(3);
    #[doc = " AMD SEV."]
    #[cfg(feature = "unstable")]
    #[cfg_attr(docsrs, doc(cfg(feature = "unstable")))]
    pub const SEV: IgvmPlatformType = IgvmPlatformType(4);
    #[doc = " AMD SEV-ES"]
    #[cfg(feature = "unstable")]
    #[cfg_attr(docsrs, doc(cfg(feature = "unstable")))]
    pub const SEV_ES: IgvmPlatformType = IgvmPlatformType(5);
}
impl ::core::fmt::Debug for IgvmPlatformType {
    fn fmt(&self, fmt: &mut ::core::fmt::Formatter) -> ::core::fmt::Result {
        #![allow(unreachable_patterns)]
        let s = match *self {
            Self::NATIVE => "NATIVE",
            Self::VSM_ISOLATION => "VSM_ISOLATION",
            Self::SEV_SNP => "SEV_SNP",
            Self::TDX => "TDX",
            Self::SEV => "SEV",
            Self::SEV_ES => "SEV_ES",
            _ => {
                return fmt.debug_tuple("IgvmPlatformType").field(&self.0).finish();
            }
        };
        fmt.pad(s)
    }
}

I have a PR out in that repo for a fix, so once we have that merged we should be able to take it. Let me see also about fixing CI to test this as well.

upstream PR is merged, will find some time tomorrow to close this out and publish a new release, sorry about that!

Thanks for fixing it!
We would need a new release with the fix to finish the packaging of this crate for Fedora, do you have an estimation for a new release?

I can spin one up tomorrow, was out last week on holiday.

@chris-oo great!

I just published a new release with 0.3.3.


Add info about order of rules in README.md

The current README does not tell in which order the generated text will appear in the output file. Since the order of rules is important in CSS, we should add a note on this. It is also important that this behavior is currently based implicitly on the way webpack is ordering the modules.

Lgtm

Merge? 😁


test: add jest integration test

part of #7

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #18   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines          62     62
  Branches       13     13
=====================================
  Hits           62     62

Continue to review full report at Codecov.

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

TODO use Jest with --json?
TODO ava
other runners can be done in separate PRs afterwards

see #21


(Bug) Dragn and drop columns in grouped columns

Describe the bug
I need to drag the title column "Test" but he won't let me do it
Your minimal, reproducible example
https://codesandbox.io/p/devbox/elastic-sound-3yv8lz?embed=1&file=%2Fsrc%2Fmain.tsx%3A90%2C20
Steps to reproduce
Start moving the column 'Test"
Expected behavior
Column "Test" should be dragged
How often does this bug happen?
Only once
Screenshots or Videos
https://recordit.co/fsafqWvR1M
Platform
Windows Google chrome
react-table version
8.10.7
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Another example
https://recordit.co/rD049mXt3k
I noticed that columnOrder updates correctly but by itself useReactTable doesn't update columns

Local code example

I met the same problem
https://codesandbox.io/p/devbox/competent-star-zwlj23?embed=1&file=%2Fsrc%2Fmain.tsx%3A32%2C42
I'm trying to move lastName, but it does't work. Column order updates but the table does't change the position of the columns

I think the main problem you guys are running into here is trying to use React 18 with react-dnd, which doesn't really work. All tanstack table dnd examples have moved on to dnd-kit instead.

I have the same issue, Did you guys resolve it? @KevinVandy  @GlebKodrik


cytoplasmic located TFs that translocate to nucleus on activation?

Hi Pascale
I think last week we were talking about the issue of whether new terms were required for TFs such as SMADs that, like nuclear receptors, remain in the cytoplasm until activated and then move to the nucleus.
The SMADs have:
GO:0005072 transforming growth factor beta receptor, cytoplasmic mediator activity
| is_a GO:0030618                transforming growth factor beta receptor, pathway-specific cytoplasmic mediator activity
| is_a GO:0030616                transforming growth factor beta receptor, common-partner cytoplasmic mediator activity
| is_a GO:0030617                transforming growth factor beta receptor, inhibitory cytoplasmic mediator activity
But maybe is a term for similar but non-SMAD proteins needed?
I'm not sure if there should be a new term to describe these types of proteins, maybe these family specific terms are sufficient?
But the other issue is should there be a MF term for the proteins that sequester TFs in the cytoplasm? Or can we just call these TF repressors. GO has the Cellular Component term:
GO:0090569 cytoplasmic transcriptional repressor complex
A protein complex, located in the cytoplasm, that possesses activity that prevents or downregulates transcription.
Do you think it would be helpful to have a MF term to describe this activity other than protein binding?
I haven't looked at this in any detail, it just came up in our discussion but I think it would be good to resolve this as part of the TF project
Thanks
Ruth

Hello @RLovering
Coming back to this - the solution we had agreed on was to use the term 'protein sequestering activity', and I propose that for SMADs you would annotate this to 'occurs in' cytoplasm.
Does that work ?
If that's the case I could either obsolete the 4 SMAD terms, or merge them into 'protein sequestering activity'. I am leaning towards obsoletion because I find those MFs very unclear, they would look odd as synonyms. What do you think?
Thanks, Pascale
TERMS IMPACTED:
GO:0005072 transforming growth factor beta receptor, cytoplasmic mediator activity
| is_a GO:0030618 transforming growth factor beta receptor, pathway-specific cytoplasmic mediator activity
| is_a GO:0030616 transforming growth factor beta receptor, common-partner cytoplasmic mediator activity
| is_a GO:0030617 transforming growth factor beta receptor, inhibitory cytoplasmic mediator activity

Discussing with @RLovering

The I-SMADs should be annotated to 'DNA-binding transcription factor inhibitor activity' (GO:0140416), occurs_in cytoplasm.
Others need to be looked at, they are possibly DNA-binding transcription factors (GO:0000981)

and obsolete the 4 terms above.
Thanks, Pascale

Dear all,
The proposal has been made to obsolete
GO:0005072 transforming growth factor beta receptor, cytoplasmic mediator activity
and children: GO:0030618 transforming growth factor beta receptor, pathway-specific cytoplasmic mediator activity
GO:0030616 transforming growth factor beta receptor, common-partner cytoplasmic mediator activity
GO:0030617 transforming growth factor beta receptor, inhibitory cytoplasmic mediator activity
The reason for obsoletion is that there are other terms that represent the same functions; for example:

GO:0030617 transforming growth factor beta receptor, inhibitory cytoplasmic mediator activity
should be annotated as 'GO:0140416 DNA-binding transcription factor inhibitor activity', occurs_in cytosol
others may be GO:0000981 DNA-binding transcription factor activity, RNA polymerase II-specific, or GO:0003712 transcription coregulator activity.

16 annotations need to be reviewed, see
https://github.com/geneontology/go-annotation/issues/2858

Group
Number of annotations

BHF-UCL
11

ComplexPortal
1

FlyBase
2

WB
1

PINC
1

mappings to those terms. Those terms are not present in any subsets.
There are no mappings to those term. Those terms are not present in any subsets.
You can add any comments to the ticket:
https://github.com/geneontology/go-ontology/issues/16202
We are opening a comment period for this proposed obsoletion. We’d like to proceed and obsolete this term on March 19th, 2020. Unless objections are received by March 19th, 2020, we will assume that you agree to this change.
Thanks, Pascale

@ukemi I dont think this is in the right project ??

? Feel free to move it then?


csharp/src/Drivers/Apache: data types should be returned as-is instead of being converted

What happened?
I expect structured types and intervals to be returned as their Arrow representation instead of being converted to string.
How can we reproduce the bug?
No response
Environment/Setup
No response

@CurtHagenlocher - So initially, this option was set. Unfortunately, the server did not return enough metadata for us to reconstruct the data structure to dereference the buffer.
How/who do we work with to get the server to return the necessary metadata?

I think what would need to happen to make this work is not to return until we've read the first Arrow batch and to take the schema from that instead of the Thrift-based metadata. I'm not sure yet how worthwhile this is. I'm pretty convinced that "Spark Connect" is the right path forward for Spark in the future and AFAIK Arrow results aren't supported from Impala or non-Spark implementations of HiveServer2. What I don't know is how quickly Spark users adopt newer versions: Spark Connect requires 3.4 which is barely a year old.


InvalidDimensions encountered while trying to read file

Library versions:

django-import-export 1.0.0
django 1.10.1

About data file and ORM:

django model with extra fields not show up in csv data file. (remove these fields also get same exception)
csv data file do not include id field

Exception after importing in admin:
InvalidDimensions encountered while trying to read file: data.csv

I found my data has some issue in format. I tried a small csv and added id in csv, then works.


Poor lfs_file_relocate() performance when a bad block is detected.

See also #535.
TLDR
lfs_file_relocate() copies data from a bad block to a new block one byte at a time. This is causing unpredictable lag (sometimes over 1500ms) when a block error is encountered while writing to a file.
Please consider:

Change lfs_file_relocate() to use a dat[] array for bulk transfers similar to what lfs_bd_cmp() now does. The array size for these bulk transfers should be configurable by the user as either a #define in lfs.h or a parameter in lfs_config.

Full Background
I have been investigating unstable lfs_file_write() performance on a Cortex-M4 processor when streaming data in a background thread from a buffer into an lfs file on flash. Our flash chip is 1Gbit with 128k byte blocks composed of 64 2k byte pages.
Our process needs to reliably write out approximately ~4kbytes of data to flash every 500ms. Most of the time this takes 5-10ms to write out, but once in a while the buffer overflows because lfs takes more than 1000ms to write out the data.  Profiling shows that flash page read and write operations reliably take 2ms or less to complete for this hardware and were not contributing to the problem.
It was discovered that whenever a bad block was found during lfs_file_write(), lfs_file_relocate() was called to copy the contents of the old block into a newly allocated block. On our hardware this operation takes as much as 1500ms to copy about 100kbytes of data. lfs_relocate_file() appears to be copying only one byte at a time between the read and write caches, causing a significant amount of overhead for this flash configuration.
After changing lfs_file_relocate() to use an array similar to what lfs_bd_cmp() now does, and setting that array to 32 bytes, lfs_file_relocate() now completes in 200-300ms after a block error.
I understand that lfs is trying to keep its stack footprint as low as possible and 128k blocks are a bit large, but I think the tradeoff between stack space and throughput in cases like this should be user configurable.
I can post a PR if that will help the discussion. Am I missing anything important here?

Edit: Actually a 256 byte buffer appears to be way overkill. Testing the same code with a 32 byte buffer yields nearly the same performance increase, so I have updated my description above.

If you have a PR with this change, I'd love to see it - I'd probably use it in my own version of littlefs where I'm seeing this same bottleneck come up occasionally

in lfs.c, in function lfs_bd_cmp(...) Change the line:
uint8_t dat[8];
to
uint8_t dat[64];
or larger.

You will need to balance the size of dat vs the larger max stack overhead (which lfs tries to minimize).

Thanks, I just applied your changes to my branch. I haven't had a chance to gather hard numbers, but anecdotally it does seem to help.
I'd happily give up some stack space if it means I can reduce my buffer size (which currently has to be very large to account for the periodic spikes in littlefs latency)

@ryangardner Unit tests are not passing for my PR. We did detect a lesser performance issue in lfs_bd_cmp() but when we increase its buffer size larger than 8 bytes it causes unit tests to fail. I'll get review feedback, but for now its working in you want to try it in your own fork.


feat: CDN Setup

Description
This PR sets up the public/index.html to inject the CDN_ URL via ngnix
Also, set the webpack_public_path to window.CDN_URL for webpack to handle lazyly loaded chunks
PR fixes following issue(s)
Fixes #23875
Type of change
Performance imporvement
Testing
Manual
Test Plan

Test if everything is working fine without setting the APPSMITH_CDN_URL env variable.
Test if static files are loaded from CDN after setting up APPSMITH_CDN_URL

Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

@hetunandu @sharat87 @somangshu  Please do not merge this PR. This is supposed to be a BE only feature.


Vegetarian Icon

The icon I want is:

Name: Vegetarian Symbol -  Ⓥ

Note: NOT https://www.v-label.eu/

Hmmm. Doesn't render in monospace in the browser. Weird!

can you please add it as an image i can't find it

@tonyraoul It's https://raw.githubusercontent.com/edent/SuperTinyIcons/master/images/svg/vegetarian.svg?sanitize=true
I think the layout may be browser dependent.


error api key is required!

error api key is required!

Sorry, where are you getting this error? A bit more information would be useful.

when i try to run gekko i get throw new error: api key is required.
the error has somthing to do with pushbullet!

Pushbullet pushes messages to your computer and/or phone if set up, so that you can follow price movements and act on it manually. You have to first register at https://www.pushbullet.com/ and get an authentication token that you must then enter in your config file on line 238. (by default pushbullet is enabled)
Alternatively try disabling pushbullet, set variable on line 235 to false.

thank you xD


Clarification about license

Hello, I would like to confirm that this project is under the MIT license ? I am interested in studying it very carefully so I can learn about writing my own MMO -style server backend for my own indie. project. This project seems quite amazing. I just want to clarify if I can use this repo. as source code to learn from towards my own closed source, commercial MMO -style server. Thank-you.

Yes: https://github.com/PerpetuumOnline/PerpetuumServer/blob/master/LICENSE

Thank-you so very much.


Time stamp not recognised

Hi, I followed the instruction for the message payload. The problem is that the timestamp is not being recognised. Any advice? The time stamp is in the past as data is loaded from a file.
{
"device": {
"deviceId": "log1"
},
"measurements": {
"lbs": 0,
"Weight_lbs": 4420,
"Value": 195961
},
"timestamp": "2020-09-17T09:50:02.052Z"
}

By not recognized do you mean you're receiving a validation error from the bridge while trying to send it or that it's not behaving as expected in the IoT Central application?
In IoT Central this timestamp will be used for features like the chart visualization and will also be included when you export your data. In the "Raw data" view, however, the timestamp displayed is the time the message arrived in IoT Central.

Thanks @peolivei2 it was indeed the raw data view that confused me. this is fine now.

issue closed