Gitignore template for Beef programming language

Reasons for making this change:
The Beef programming language is already included in the linguist repo, and a default
gitignore template for it would be useful.
Explanation:

BeefSpace_User.toml includes settings specific to the user, such as window position and open tabs.
recovery is the directory where data is saved, should the ide chrash. Sharing this isnt necessary.
build includes the compiled projects and should not be in the repo.

If this is a new template:

Repository
Website

Thanks for the contribution, however per the contribution guidelines this file should be placed in the community folder. Please edit the location of the file.
https://github.com/github/gitignore#specialized-templates

The location of the file should be moved to /community/Beef.gitignore now


connection handler is sending the breakdown twice for the SDX LC

Hi,
I believe this error was introduced by PR #226 , which ended up sending the breakdown connections twice for the SDX LC:
https://github.com/atlanticwave-sdx/sdx-controller/blob/main/sdx_controller/handlers/connection_handler.py#L159-L160

@congwang09 would you please take a look on this and #229 when you get a chance.
That PR for refactoring probably created the bug.


 How difficult would it be to generalize it to address #23? I think that one easy way is to pass a regex: exclude paths that match the regex.
I support checking out other tools and see how paths are included/excluded on a command line tool (e.g. coverage for Python).


Feature: Supported boolean flag in API

:grey_question: About
Is your feature request related to a problem? Please describe.
Actually, /api/postgresql.json :
[
  {
    "cycle": "15",
    "eol": "2027-11-11",
    "latest": "15.1",
    "latestReleaseDate": "2022-11-07",
    "releaseDate": "2022-10-10",
    "lts": false
  },
  {
    "cycle": "14",
    "eol": "2026-09-30",
    "latest": "14.6",
    "latestReleaseDate": "2022-11-07",
    "releaseDate": "2021-09-27",
    "lts": false
  },
  {
    "cycle": "13",
    "eol": "2025-11-13",
    "latest": "13.9",
    "latestReleaseDate": "2022-11-07",
    "releaseDate": "2020-09-21",
    "lts": false
  },
  {
    "cycle": "12",
    "eol": "2024-11-14",
    "latest": "12.13",
    "latestReleaseDate": "2022-11-07",
    "releaseDate": "2019-09-30",
    "lts": false
  },
  {
    "cycle": "11",
    "eol": "2023-11-09",
    "latest": "11.18",
    "latestReleaseDate": "2022-11-07",
    "releaseDate": "2018-10-15",
    "lts": false
  },
  {
    "cycle": "10",
    "eol": "2022-11-10",
    "latest": "10.23",
    "latestReleaseDate": "2022-11-07",
    "releaseDate": "2017-10-02",
    "lts": false
  },
...
]

does not give as much information as the official page, especially the Supported boolean column :

:bulb:  The solution you'd like
I would like to get a ready to use boolean attribute that would tell me is the version is supported or not... I mean without any client side computation.
Alternatives you've considered

Client side compuation

I think such a flag might make sense for actual versions (15.1, 14.5), but not for release cycles - this is what the badge API will do, and we can perhaps expand it from there.
The long-planned supported-versions field in the planned spec for releases.json fulfills a similar purpose - make it easy to check whether the version you're running is supported or not.
However, given that most clients will need to do some more computation to check for support, this isn't necessarily a good idea. (postgres 10 is still supported under Ubuntu 18.04 for eg), so clients are expected to do more work.
Could you provide some details as to why your client is so constrained?

this is what the badge API will do, and we can perhaps expand it from there.

:zap:

The long-planned supported-versions field in the https://github.com/endoflife-date/releases.json/pull/1 fulfills a similar purpose - make it easy to check whether the version you're running is supported or not.

Great news :clap:
Hmmm, here is the context :
:heavy_check_mark: We run psql on rhel
:heavy_check_mark: I strongly rely on psql Versioning policies for our maintenance process : therefore I need a matching (so I don't have to explain...tec...)

Could you provide some details as to why your client is so constrained?

:point_up: The main concern for me would to not have to make additional compuatations : I guess
:thought_balloon: Hopefully it did answer your questions @captn3m0 :crossed_fingers:

Most clients will anyway have to check:

What version of RHEL are you running
What is the latest version of postgres for that release of RHEL
In specific cases, lookup RedHat ELS lists to check if the package is included (https://access.redhat.com/articles/4997301)
If you are running the latest version as per RedHat
Grab the release cycle from the API
Check the latest version and match it. This is unlikely to match, because RHEL doesn't really track latest. RHEL 7 still has 9.2.24 for eg.
Finally, check the EOL date for the release cycle and see if it is crossed.

If you want to rely on just the postgres versioning policy, then you should just match the version, and the eol date.

Going to close this, will create a separate issue for listing supported versions in the API.

Sure, thanks a lot :pray:


blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Access to script at<EMAIL_ADDRESS>from origin 'https://my-website.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
🤔

just fixed, the hostname cdn.esm.sh will redirect to esm.sh now (this issue is caused by missed cors headers of the redirect response), better use esm.sh instead

Amazing! It didn't block me; I patched the issue on my side and more recent code won't face this, but an old deployment stumbled upon this and thought it would be good to share!
Thanks!

thanks for sharing!


Fix for buildling

Update the Gojiraw tree to compile. I built locally after updating glfw and functionality would appear not
to have regressed.

lgtm.


Jest HelloWorld test fails

Trying to setup testing with Jest and wanted to use HelloWorld.spec.js as an example, however it is failing with:
  FAIL  test/unit/specs/HelloWorld.spec.js
  HelloWorld.vue
    ✕ should render correct contents (12ms)

  ● HelloWorld.vue › should render correct contents

    TypeError: Cannot read property 'querySelector' of undefined

       6 |     const Constructor = Vue.extend(HelloWorld)
       7 |     const vm = new Constructor().$mount()
    >  8 |     expect(vm.$el.querySelector('.hello h1').textContent)
       9 |       .toEqual('Welcome to Your Vue.js App')
      10 |   })
      11 | })

      at Object.<anonymous> (test/unit/specs/HelloWorld.spec.js:8:19)

Having this issue today too.  Not sure whether it is relevant but querySelector has no definition in index.d.ts at path<EMAIL_ADDRESS>

got the same problem, according to the vue documentation, i make some change:
describe('HelloWorld.vue', () => {
 it('should render correct contents', () => {
   const Constructor = Vue.extend(HelloWorld)
   const vm = new Constructor().$mount()
   Vue.nextTick(() => {
   	expect(vm.$el.querySelector('.hello h1').textContent)
   	  .toEqual('Welcome to Your Vue.js App')
   })
 })
})

then the case is passed, but still got some error:
  console.error node_modules\vue\dist\vue.runtime.common.js:589
    [Vue warn]: Error in nextTick: "TypeError: Cannot read property 'querySelector' of undefined"


nova-filters: use sconsPackages.scons_latest; sconsPackages.scons_3_0_1: drop

Description of changes

See https://github.com/NixOS/nixpkgs/pull/201859.
Also removing sconsPackages.scons_3_0_1 since there are no more packages that depends on it in nixpkgs (nova-filters is the last one).
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

CC @magnetophon.


update develop branch

toggle rotation
delete annotation
edit annotation
screen capture
upgraded font awesome
Grid position
Zoom Control
Toolbar
Save
JSTS
adjust camera to avoid clipping
single objects

Zephyr


drawpile: 2.1.4 -> 2.1.6

Motivation for this change
https://drawpile.net/news/release-2.1.6/
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

The change seems fine, currently building/testing locally...

@fgaz thanks!


tidy/tidy-fix in cpt.config causes tidy call on compile

You set $aTidyFlags/$aTidyFixFlags from cpt and later set WorkloadType based on loaded from cpt values
  [WorkloadType] $workloadType = [WorkloadType]::Compile

  if (![string]::IsNullOrEmpty($aTidyFlags))
  {
     $workloadType = [WorkloadType]::Tidy
  }

  if (![string]::IsNullOrEmpty($aTidyFixFlags))
  {
     $workloadType = [WorkloadType]::TidyFix
  }

Need for example to store somewhere values after params and use that stores values for setting workloadType
..     , [alias("vs-sku")]
..       [Parameter(Mandatory=$false, HelpMessage="Edition of Visual Studio toolset to use for loading project")]
..       [string]   $aVisualStudioSku
..     )
if (![string]::IsNullOrEmpty($aTidyFixFlags))
{
	Set-Variable -name aTidyFixFlagsOnStart -value "1" -option Constant
}

if (![string]::IsNullOrEmpty($aTidyFlags))
{
	Set-Variable -name aTidyFlagsOnStart -value "1" -option Constant
}

```.....

[WorkloadType] $workloadType = [WorkloadType]::Compile
if (![string]::IsNullOrEmpty($aTidyFlagsOnStart))
{
$workloadType = [WorkloadType]::Tidy
}
if (![string]::IsNullOrEmpty($aTidyFixFlagsOnStart))
{
$workloadType = [WorkloadType]::TidyFix
}

The cpt.config file is overriding the script parameter values by design. We introduced this mechanism a few releases ago as a way of enabling teams to share and reuse Clang Power Tools settings easily, using source version control.
The Clang Power Tools user interface in the Visual Studio extension is not yet aware of this configuration file and leads to the behavior you are experiencing. We will address this in a future update.
Regards,
Gabriel.

It's ok, that cpt.config overrides script parameters. The problem is that it also overrides type of call from outside of script, not only from extension (compile/tidy/tidy-fix). You call compile (from VS or from command line) and get tidy-fix instead of it, and that's pretty nasty.


refactor: query and modeling as child-namespaces of modeling and engine

Codecov Report
Patch coverage: 76.56% and project coverage change: -0.92% :warning:

Comparison is base (bd1fa51) 86.04% compared to head (ccb77b8) 85.13%.

:exclamation: Current head ccb77b8 differs from pull request most recent head ee03d66. Consider uploading reports for the commit ee03d66 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #91      +/-   ##
==========================================
- Coverage   86.04%   85.13%   -0.92%
==========================================
  Files         113      115       +2
  Lines         939      942       +3
  Branches       69       73       +4
==========================================
- Hits          808      802       -6
- Misses        111      116       +5
- Partials       20       24       +4

Files Changed
Coverage Δ

Tseesecake/Arrangers/BucketAnonymousTimestamp.cs
62.50% <0.00%> (-12.50%)
:arrow_down:

Tseesecake/Engine/Mounting/DmlEngine.cs
0.00% <0.00%> (ø)

...atements/DuckDB/DuckdbArrangerCollectionFactory.cs
0.00% <ø> (ø)

.../Postgresql/PostgresqlArrangerCollectionFactory.cs
100.00% <ø> (ø)

Tseesecake/Modeling/Catalog/Facet.cs
100.00% <ø> (ø)

Tseesecake/Modeling/Catalog/Measurement.cs
100.00% <ø> (ø)

Tseesecake/Modeling/Catalog/TimestampTz.cs
0.00% <0.00%> (ø)

Tseesecake/Modeling/Catalog/VirtualMeasurement.cs
100.00% <ø> (ø)

Tseesecake/Modeling/GlobalEngine.cs
0.00% <0.00%> (ø)

Tseesecake/Modeling/Mounting/FileSource.cs
100.00% <ø> (ø)

... and 98 more

... and 1 file with indirect coverage changes

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


Adding image path, Fixes #328

Looks good, you just need to add the 'image_path' as one of the asserted columns to make sure all tests pass. Here:
https://github.com/dassaniansh/DeepForest/blob/872364a40d392d1d67bd46b3cbcfbe2bb713c078/tests/test_main.py#L129
https://github.com/dassaniansh/DeepForest/blob/872364a40d392d1d67bd46b3cbcfbe2bb713c078/tests/test_main.py#L142
I can then merge. Thanks for contributing.

@dassaniansh - just wanted to check if you'd seen the feedback from @bw4sz. Once you've made that small change to the tests we should be able to get this in.

Added to #353


Condense org.codehaus.groovy.runtime.ArrayUtil

use varargs instead of manual 250-length Array construction

Hi @Nektro thanks for the PR. The purpose of that ArrayUtils class is to ease bytecode generation and avoid needing to write bytecodes to generate an array as is needed for the varargs. The class comments show an example and explains why the individual methods are needed and they are statically linked to in generated bytecode by the CallsiteWriter.

@jwagenleitner sorry about that didn't see that it wasn't used in your actual program. Interesting JIT quirk you all found. Feel free to close :)


fix fix MetricRepo.THRIFT_COUNTER_RPC_ALL NullPointException

Proposed changes
Issue Number: close #17550
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.46 seconds
stream load tsv:          460 seconds loaded<PHONE_NUMBER>9 Bytes, about 155 MB/s
stream load json:         23 seconds loaded<PHONE_NUMBER> Bytes, about 97 MB/s
stream load orc:          73 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230319033007_clickbench_pr_116552.html


relates to gh-600 Add Predicate and Filter validation to Route Creation Actuator Endpoint

Relates to issue 600:
I have added some basic logic to the route creation actuator endpoint to at least check whether the specified Filter and Predicate Factories are available in the Gateway in order to avoid crashes when accessing this route or when refreshing the RouteLocators. I appreciate any suggestions to optimize the implementation!
Note: Already incorporated changes from https://github.com/spring-cloud/spring-cloud-gateway/pull/1190/ because it already implemented DI of the RoutePredicates List to the actuator classes.

Did I miss something?


Terminal

VSCode Version:
OS Version:

Steps to Reproduce:

Open terminal
Highlight text doesn't work

Reproduces without extensions: Yes/No

Please fill out the OS version, VS Code version and provide more details. How are you trying to highlight exactly?

It's working in version 1.17.0

Great 😃


RequestLogger 'requests' array always has only one element

Are you requesting a feature or reporting a bug?
Bug report
What is the current behavior?
When using a RequestLogger for multiple calls, the 'requests' array property has always only one element, which is the first request logged.
This, combined with the RequestLogger 'clear' bug #2688 makes it hard to implement assertions on the lastest request logged.
What is the expected behavior?
logger.requests[logger.requests.length-1] should always return the latest logged request
How would you reproduce the current behavior (if this is a bug)?
implement a test which fires multiple logged request, then try to get the latest request element from the requests array
Provide the test code and the tested page URL (if applicable)
Test code
test.only('Transactions Base Filters', async (t) => {
  await t.typeText(filters.grossAmountMin, '10')
    .expect(filters.activeFilter.count).eql(1)
    .expect(logger.contains(r => (
      r.response.statusCode === 200
      && requestParser.getParams(r.request.url).grossAmount === '10__value'
    ))).ok()
    .typeText(filters.grossAmountMax, '5')
    .expect(filters.grossAmountMin.getReact(({ props: { error } }) => error)).ok()
    .expect(filters.grossAmountMax.getReact(({ props: { error } }) => error)).ok()
    // check invalid input does not fire a request
    .expect(logger.count(r => (r.request.url.indexOf('grossAmount=10__value__5') > 0))).eql(0)
    .typeText(filters.grossAmountMax, '00')
    .expect(filters.grossAmountMin.getReact(({ props: { error } }) => error)).notOk()
    .expect(filters.grossAmountMax.getReact(({ props: { error } }) => error)).notOk()
    .expect(logger.contains(r => (
      r.response.statusCode === 200
      && requestParser.getParams(r.request.url).grossAmount === '10__value__500'
    ))).ok();

   // in this test there are two requests logged
    console.log('request :', logger.requests[1].request.url); // error
});

Specify your

operating system: windows 10 / chrome 67
testcafe version: 0.20.4<EMAIL_ADDRESS><EMAIL_ADDRESS>node.js version: 8.9.2

Hi @ricovitch
It is difficult to understand a cause of the problem without a direct access to the tested app.
Could you please share a link to the tested app or provide a simple example to reproduce?
In this case, I can fix the problem very fast and provide you a build with fix ASAP.

Basically, what i observe is that the RequestLogger instance 'requests' array does not allow to access a particular logged request by it's index if there are multiple logged requests.
In the case of multiple logged requests, i thought i could make assertions on the last logged one by getting it from this array, but that does not work like it should.
I think any test with multiple logged request should allow to reproduce this problem.
Just try to access the latest logged request at the end of the test by getting it from the array.

Basically, what i observe is that the RequestLogger instance 'requests' array does not allow to access a particular logged request by it's index if there are multiple logged requests.

I don't observer this behavior.
See an example:
import { RequestLogger, Selector } from 'testcafe';

const DEMOS_PAGE_URL = 'https://www.devexpress.com/support/demos/';
const PAGE_URL       = 'https://www.devexpress.com/';

const logger = new RequestLogger(new RegExp(PAGE_URL));

fixture `Fixture`
    .page(PAGE_URL)
    .requestHooks(logger);

test('test', async t => {
    await t.expect(logger.contains(r => r.response.statusCode === 200 && r.request.url == PAGE_URL)).ok();

    console.log(logger.requests.length);
    console.log(logger.requests[logger.requests.length - 1]);

    const demosLinkSelector = Selector('a').withAttribute('href', DEMOS_PAGE_URL);

    await t.click(demosLinkSelector)
        .expect(logger.contains(r => r.response.statusCode === 200 && r.request.url == DEMOS_PAGE_URL)).ok();

    console.log(logger.requests.length);
    console.log(logger.requests[logger.requests.length - 1]);
});

Sorry i can not give access to our apps/apis.

Could you please provide us a simple example to reproduce.

Sorry for the delay. Back from holidays we had a fresh look at this on our side.
It seems this relates to a misunderstanding of us about "Smart Assertion Query Mechanism".
We where not waiting for logger.count() assertion to update before asserting on logger.requests property.
So for future understanding, this does not work
await t.click(filters.resetButton);
const lastRequest = logger.requests[1];

And this work
await t.click(filters.resetButton)
  .expect(logger.count(() => true)).eql(2);
const lastRequest = logger.requests[1];


changed docker to point to forked repo

Proposed change

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality to the supervisor)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:
Link to cli pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] The code has been formatted using Ruff (ruff format supervisor tests)
[ ] Tests have been added to verify that the new code works.

If API endpoints of add-on configuration are added/changed:

[ ] Documentation added/updated for developers.home-assistant.io

webhook test

webhook test 2


Can not load pre-trained DETR model.

Hi,
it is a nice work! :)  But i can not load pre-trained DETR model.  Can you share a new pre-trained DETR model?
Thanks!

Prepare Faster-RCNN Detector

You can download the pretrained DETR on ResNet-101 we used in the paper:
    [VG](https://shanghaitecheducn-my.sharepoint.com/:u:/g/personal/lirj2_shanghaitech_edu_cn/EfJK_InTsk9Hq9RgXEui4gsBsk3pekuzPYk4gTR8coBYAA?e=fAo647),
    [OIv6](https://shanghaitecheducn-my.sharepoint.com/:u:/g/personal/lirj2_shanghaitech_edu_cn/Edrab9pd0O1NuVoz9RPmZtoBwxnSyl-NVIFCjxf6yUZ7FA?e=uPQZ1A),

Unzip the checkpoint into the folder

Then, you need to modify the pre-trained weight parameter MODEL.WEIGHTS in config.py playground/experiment/path/config_xx.py to the path of corresponding pre-trained detector weight to make sure you load the detection weight parameter correctly.

Error details:

Traceback (most recent call last):
File "/home/zztao/anaconda3/envs/sgtr/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 59, in _wrap
fn(i, *args)
File "/home/zztao/dev/SGTR/cvpods/engine/launch.py", line 118, in _distributed_worker
main_func(*args)
File "/home/zztao/dev/SGTR/tools/train_net.py", line 230, in main
stage_main(args, config, build_model)
File "/home/zztao/dev/SGTR/tools/train_net.py", line 155, in stage_main
trainer.resume_or_load(resume=args.resume, load_mapping=cfg.MODEL.WEIGHTS_LOAD_MAPPING)
File "/home/zztao/dev/SGTR/cvpods/engine/trainer.py", line 436, in resume_or_load
self.start_iter = (self.checkpointer.resume_or_load(self.cfg.MODEL.WEIGHTS,
File "/home/zztao/dev/SGTR/cvpods/checkpoint/checkpoint.py", line 170, in resume_or_load
return self.load(path, load_mapping)
File "/home/zztao/dev/SGTR/cvpods/checkpoint/checkpoint.py", line 107, in load
checkpoint = self._load_file(path)
File "/home/zztao/dev/SGTR/cvpods/checkpoint/detection_checkpoint.py", line 65, in _load_file
loaded = super()._load_file(filename)  # load native pth checkpoint
File "/home/zztao/dev/SGTR/cvpods/checkpoint/checkpoint.py", line 194, in _load_file
return torch.load(f, map_location=torch.device("cpu"))
File "/home/zztao/anaconda3/envs/sgtr/lib/python3.8/site-packages/torch/serialization.py", line 600, in load
with _open_zipfile_reader(opened_file) as opened_zipfile:
File "/home/zztao/anaconda3/envs/sgtr/lib/python3.8/site-packages/torch/serialization.py", line 242, in init
super(_open_zipfile_reader, self).init(torch._C.PyTorchFileReader(name_or_buffer))
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory

It seems like the torch  load can not load the checkpoints.
It may be caused by a mismatched PyTorch version or trying to load a broken file.
https://discuss.pytorch.org/t/error-on-torch-load-pytorchstreamreader-failed/95103
May try to re-download the ckpt or check the version of pytorch.


Improvement of custom charts docs

Description

short PR to improve docs on custom charts - increased emphasis that they can be used with FIlter and Parameter
especially the emphasis on Parameter hopefully guides people towards the great flexibility that this offers

Now added:

change the docs on custom components to have a shorter example - they now make use of super instead of copying the entire build method

Screenshot
Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
I have not referenced individuals, products or companies in any commits, directly or indirectly.
I have not added data or restricted code in any commits, directly or indirectly.

Thanks for addressing this so immediately. 🚀 The flexibility of the custom charts feature is much cleaner now.
Do you think we should change the order of custom charts with Filters and Parameters and list them in the order:

custom chart with Filter and then
custom chart with Parameter

Also, do you think we should add following comments below def scatter_with_line(...) and def waterfall(...):

"data_frame" is filtered.

"hline" is parametrised.
or something like that?

I implemented the above suggestions as clickable code annotations. Also improved the title of the examples, but I did not swap the order. Actually I prefer having the parameter on top, as its more important to get across.

Probably he has lots of other valuable feedback too so we should quiz him in the new year 🙂

Happy to help<EMAIL_ADDRESS>


fix(euclid_wasm): include payouts feature in default features

Type of Change

[x] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[ ] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Testcase - Need to verify wise connector from the dashboard


Is there a way to restrict the acces to the bot savely?

I want to be able to share inforamtion to certain users.
Is it safe enough to do something like:
Telegram::Bot::Client.run(token) do |bot|
  bot.listen do |message|

    case message.text
      if message.from.id == "My super secret id"
    when '/start'
      puts message.from.inspect
      bot.api.sendMessage(chat_id: message.chat.id, text: "Hello, #{message.from.first_name}")
    when '/stop'
      bot.api.sendMessage(chat_id: message.chat.id, text: "Bye, #{message.from.first_name}")
    end
    else
      bot.api.sendMessage(chat_id: message.chat.id, text: "Not authorized")
    end
  end
end

Any better/safer way?

I don't see any issues with your approach.


Primes and subscripts interfere with each other

Unlike in TeX, primes and super/subscripts are treated differently from each other in Typst, and they interfere.
$
y_3' quad y'_3
$

The 3 and the prime in both cases should be vertically aligned.
In TeX, the prime symbol is giant sized, and is then shrunk to make an actual superscript when used as a decorator.  Unicode math doesn't follow this approach: the prime is U+2032 and is small and already at the correct height to be a subscript for letters; double and triple primes are their own glyphs as well.  I think that Typst is simply inserting a U+2032 in all single prime circumstances, and hence a following subscript modifies the prime and not the thing the prime was modifying.
XeLaTeX with unicode-math enabled seems to use U+2023 and friends where it can, but also gets the interaction with subscripts correct.  It also has correct placement of a prime with a non-letter.  Compare:
Typst (note the low position of the prime with respect to the sum symbol)
$sum' x' A'$

XeLaTeX w/unicode-math (note the raised prime in proper superscript position with respect to the sum symbol)
$\sum' x' A'$

Sorry, I'm not very knowledgeable, but can't you do $y^prime_3$ $sum^prime_3$? In LaTeX, another way of doing what you did is $sum^{\prime}$.

Obviously there's still a lot left to be desired in terms of the size of the prime and how close it's placed to the symbol. But for me the code above seems okay-ish.

Alas, the size of the prime is wrong with $y^prime_3$; this is a workaround, but is not the finely crafted typesetting that Typst should be capable of.
It turns out that for well-formed OTF math fonts, the ssty feature encodes script and script-script variations of glyphs for the different optical sizes.  For a prime in New Computer Modern Math, the base glyph is /minute and the alternates are /minute.st and /minute.sts.  The optical size variants are, in fact, full sized jumbo primes à la the original TeX approach.
The upshot is that prime should not insert a raw U+2032 but instead in insert a superscript where the content is U+2032 with a variant taking into account the level of scripting.  I looked at the output from XeLaTeX + unicode-math and this seems to be exactly the approach taken there.
I guess Typst doesn't currently use the ssty feature to take advantage of optical size info in the math font already.  I tried to turn it on manually for a single prime character but wasn't successful.  At any rate, a proper fix for the prime situation would probably involve also upgrading the math engine to (optionally) use ssty info automatically.

This works fairly decently as a workaround for now
$y#box(width:0pt)[#text(top-edge: "ascender",bottom-edge: "descender")[$prime$]]_n$

Here's a workaround that works for now
#let prime = move(dx: 0.1em, dy: 0.35em, scale("\u{2032}", x:150%,y : 150%))
default: $sum', x', A', y_3'$
workaround: $sum^prime, x^prime, A^prime, y_3^prime$


Scheduled scan's Config page does not show the values of the scheduled scan created

On 2.5-head - commit id: 7e386ebab3f

Deploy CIS v2
Create a scheduled scan

Click on the scan to go to the Scan CR's details page, on the top right, click on Config.

Selected values while creating the scheduled scan are NOT available

On 2.5-head - commit id: b2953cbc

Scan state for "warn" results and Scheduling values (Radio button selections) are NOT available

Reopening the issue

On 2.5-head - commit id: baf4867cb
Scan detail page --> Config has the values for "Warn" and Schedule config


Copying from Gen2 to Gen2: A valid source-destination combination could not automatically be found

Which version of the AzCopy was used?
azcopy version 10.10.0
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy cp
What problem was encountered?
It gave error, when it is not supposed to.
It says:
Source: 'blah blah' of type BlobFS, and Destination: 'blah blah' of type BlobFS
and then in next breath:
INFO: Based on the parameters supplied, a valid source-destination combination could not automatically be found.
Tried various combinations, with/without / at end, --from-to option, wild card * in source path.

azcopy cp "$base_url/incoming/table1/2021-05-20/03/00/?$tok" "$base_url/incoming/table1/2021-05-21/20/20/?$tok" --recursive=true
azcopy cp "$base_url/incoming/table1/2021-05-20/03/00?$tok" "$base_url/incoming/table1/2021-05-21/20/20?$tok" --recursive=true
azcopy cp "$base_url/incoming/table1/2021-05-20/03/00/?$tok" "$base_url/incoming/table1/2021-05-21/20/20/?$tok" --from-to "BlobFSBlobFS" --recursive=true
azcopy cp "$base_url/incoming/table1/2021-05-20/03/00?$tok" "$base_url/incoming/table1/2021-05-21/20/20?$tok" --from-to "BlobFSBlobFS" --recursive=true
azcopy cp "$base_url/incoming/table1/2021-05-20/03/00/*?$tok" "$base_url/incoming/table1/2021-05-21/20/20?$tok" --recursive=true

How can we reproduce the problem in the simplest way?
$ tok="<a valid sas token>"
$ base_url='https://lanarpccalbdev01.dfs.core.windows.net/streaming-sync/rpccalb'
$ # --------------------- it's valid info
$ azcopy ls "$base_url/incoming/table1/2021-05-20/03/00?$tok" | head
INFO: /;  Content Length: 0.00 B
INFO: table1_001_20210520075314.csv.gz;  Content Length: 120.00 B
INFO: table1_002_20210520075314.csv.gz;  Content Length: 122.00 B
INFO: table1_003_20210520075314.csv.gz;  Content Length: 122.00 B
INFO: table1_004_20210520075314.csv.gz;  Content Length: 121.00 B
INFO: table1_005_20210520075314.csv.gz;  Content Length: 121.00 B
INFO: table1_006_20210520075314.csv.gz;  Content Length: 122.00 B
INFO: table1_007_20210520075314.csv.gz;  Content Length: 120.00 B
INFO: table1_008_20210520075314.csv.gz;  Content Length: 122.00 B
INFO: table1_009_20210520075314.csv.gz;  Content Length: 122.00 B
$
$
$ azcopy cp "$base_url/incoming/table1/2021-05-20/03/00/?$tok" "$base_url/incoming/table1/2021-05-21/20/20/?$tok" --recursive=true
INFO: The parameters you supplied were Source: 'https://lanarpccalbdev01.dfs.core.windows.net/streaming-sync/rpccalb/incoming/table1/2021-05-20/03/00/?my_valid_token' of type BlobFS, and Destination: 'https://lanarpccalbdev01.dfs.core.windows.net/streaming-sync/rpccalb/incoming/table1/2021-05-21/20/20/?my_valid_token' of type BlobFS
INFO: Based on the parameters supplied, a valid source-destination combination could not automatically be found. Please check the parameters you supplied.  If they are correct, please specify an exact source and destination type using the --from-to switch. Valid values are two-word phases of the form BlobLocal, LocalBlob etc.  Use the word 'Blob' for Blob Storage, 'Local' for the local file system, 'File' for Azure Files, and 'BlobFS' for ADLS Gen2. If you need a combination that is not supported yet, please log an issue on the AzCopy GitHub issues list.

failed to parse user input due to error: the inferred source/destination combination could not be identified, or is currently not supported
$
$
$ azcopy cp "$base_url/incoming/table1/2021-05-20/03/00/?$tok" "$base_url/incoming/table1/2021-05-21/20/20/?$tok" --from-to "BlobFSBlobFS" --recursive=true

failed to parse user input due to error: invalid --from-to value specified: "BlobFSBlobFS". Valid values are two-word phases of the form BlobLocal, LocalBlob etc.  Use the word 'Blob' for Blob Storage, 'Local' for the local file system, 'File' for Azure Files, and 'BlobFS' for ADLS Gen2. If you need a combination that is not supported yet, please log an issue on the AzCopy GitHub issues list.
$
$
$ azcopy cp "$base_url/incoming/table1/2021-05-20/03/00?$tok" "$base_url/incoming/table1/2021-05-21/20/20?$tok" --from-to "BlobFSBlobFS" --recursive=true

failed to parse user input due to error: invalid --from-to value specified: "BlobFSBlobFS". Valid values are two-word phases of the form BlobLocal, LocalBlob etc.  Use the word 'Blob' for Blob Storage, 'Local' for the local file system, 'File' for Azure Files, and 'BlobFS' for ADLS Gen2. If you need a combination that is not supported yet, please log an issue on the AzCopy GitHub issues list.
$
$
$ azcopy cp "$base_url/incoming/table1/2021-05-20/03/00?$tok" "$base_url/incoming/table1/2021-05-21/20/20?$tok" --recursive=true
INFO: The parameters you supplied were Source: 'https://lanarpccalbdev01.dfs.core.windows.net/streaming-sync/rpccalb/incoming/table1/2021-05-20/03/00?my_valid_token' of type BlobFS, and Destination: 'https://lanarpccalbdev01.dfs.core.windows.net/streaming-sync/rpccalb/incoming/table1/2021-05-21/20/20?my_valid_token' of type BlobFS
INFO: Based on the parameters supplied, a valid source-destination combination could not automatically be found. Please check the parameters you supplied.  If they are correct, please specify an exact source and destination type using the --from-to switch. Valid values are two-word phases of the form BlobLocal, LocalBlob etc.  Use the word 'Blob' for Blob Storage, 'Local' for the local file system, 'File' for Azure Files, and 'BlobFS' for ADLS Gen2. If you need a combination that is not supported yet, please log an issue on the AzCopy GitHub issues list.

failed to parse user input due to error: the inferred source/destination combination could not be identified, or is currently not supported
$
$
$ ls -1tr ~/.azcopy/*.log | tail -1 | xargs cat
2021/05/21 20:21:51 AzcopyVersion  10.10.0
2021/05/21 20:21:51 OS-Environment  linux
2021/05/21 20:21:51 OS-Architecture  amd64
2021/05/21 20:21:51 Log times are in UTC. Local time is 21 May 2021 20:21:51
2021/05/21 20:21:51 Closing Log
$

Have you found a mitigation/solution?
No.

@kashyap-bhatt-by  DFS endpoints on both source and destination are not supported.  Use .blob.core.windows.net endpoints on these accounts to perform copy.

@nakulkar-msft , error message says:

....If you need a combination that is not supported yet, please log an issue on the AzCopy GitHub issues list.
So why close this issue?


Chef14:  knife-windows tests broke

Failures:
  1) Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same long-name
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:125
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:55:in `block (3 levels) in <top (required)>'
  2) Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same short-name
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:125
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:59:in `block (3 levels) in <top (required)>'
  3) Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same description
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:125
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:63:in `block (3 levels) in <top (required)>'
  4) Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same default value
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:125
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:67:in `block (3 levels) in <top (required)>'
  5) Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same long-name
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:159
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:55:in `block (3 levels) in <top (required)>'
  6) Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same short-name
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:159
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:59:in `block (3 levels) in <top (required)>'
  7) Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same description
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:159
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:63:in `block (3 levels) in <top (required)>'
  8) Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same default value
     Failure/Error: expected = bootstrap.options[win_key][sym]
     NoMethodError:
       undefined method `[]' for nil:NilClass
     Shared Example Group: "compare_options" called from ./spec/unit/knife/bootstrap_options_spec.rb:159
     # ./spec/unit/knife/bootstrap_options_spec.rb:36:in `block in compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `each'
     # ./spec/unit/knife/bootstrap_options_spec.rb:33:in `compare_property'
     # ./spec/unit/knife/bootstrap_options_spec.rb:67:in `block (3 levels) in <top (required)>'
Finished in 0.78692 seconds (files took 0.69463 seconds to load)
135 examples, 8 failures
Failed examples:
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:1:2] # Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same long-name
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:1:3] # Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same short-name
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:1:4] # Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same description
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:1:5] # Chef::Knife::Bootstrap when compared to BootstrapWindowsWinrm uses the same default value
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:2:2] # Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same long-name
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:2:3] # Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same short-name
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:2:4] # Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same description
rspec ./spec/unit/knife/bootstrap_options_spec.rb[1:2:5] # Chef::Knife::Bootstrap when compared to BootstrapWindowsSsh uses the same default value

adding regression tag since my guess from the output is that knife-windows is actually busted on chef-14 and this isn't just test breakage.

Hi @lamont-granquist  and @btm: `knife bootstrap windows' is working fine, and it's just the tests that is failing. Will fix the specs.


Allow multiple widgets

Allow multiple widgets with different options per page by using id instead of class attribute selector.

thanks


Update enable-tlsecccurve.md

Added missing information and examples to the document.

@msbemba nice one!


MFCMAPI x86 Crash on "Export store contents to text"

I tried to export my store with a handful of mails via "Right Click on store - Export store contents to text" but MFCMAPI always crashes after creating some files with:
Exception thrown at 0x011B5399 in MFCMapi.exe: 0xC0000005: Access violation writing location 0xDDDDDDDD.
If there is a handler for this exception, the program may be safely continued.
MFCMAPI_Crash_CallStack.txt

I did a little investigation on the exception.
It happens in MapiProcessor.cpp - CMAPIProcessor::AddFolderToFolderList - Line 650:
lpNewNode->szFolderOffsetPath = szFolderOffsetPath;
Where lpNewNode->szFolderOffsetPath is not initialized as std::wstring because lpNewNode got allocated with MAPIAllocateBuffer in line 636.
I know nothing about MAPIAllocateBuffer but should it really instantiate structs containing complex data types like std::wstring?

After reading the docu about MAPIAllocateBuffer and fellow APIs I suggest the pull request #99 to fix this issue.

Thanks for finding and investigating this. I see the fix in #99 but I have a different approach in mind that'll keep the wstring.


Add SQL2 Functions — AKA Parameterized Views (DRAFT)

Currently, views may contain holes (variables), but these must be fully specified at creation time. Any attempt to update the values in the holes results in updating the view. This usage workflow is good for some purposes but wholly inadequate for interactive dashboards designed to be used by lots of users.
To address these problems, we need to introduce parameterized views, which are views that contain holes whose values are not specified until the result set is read from Quasar. This will allow front-end applications such as SlamData to store the parameterized views only, and then on a per-user basis, specify values for holes.
In addition, this opens the door to more advanced forms of caching, such as cubing.
SQL2 Syntax
A parameterized view, AKA a process, is a function from a one or more named values to a result set.
CREATE FUNCTION FLOOR(:num)
BEGIN
  :num - (:num % 1)
END;

CREATE FUNCTION ROUND(:num)
BEGIN
  FLOOR(:num + 0.5)
END;

An ordinary view emerges as a special case of an immediately applied function:
CREATE FUNCTION ANON123(:source)
BEGIN
  SELECT first_name, last_name FROM :source
END;

ANON123(`/foo/bar/baz`)

There are two top-level grammers we will need to support:

Mixing let bindings with function declarations followed by a terminal expression, which allows users to define and use their own functions inside their own queries;
A pure module that consists only of function declarations and possibly let bindings.

File System: Module Nodes / Mounts
Parameterized views could piggyback off view mounts or new type of node in the file system (module nodes, which contain SQL2 functions that accept input and return output). As with mounts, reading from module and editing their configuration are separate, until the two have been unified via metadata or other mechanism.
A module is akin to a directory of named executables (each defined by a SQL2), whereas a data node is akin to a data file, and a directory node is the same across the Quasar file system and ordinary file systems.
If the SQL2 defining a module defines multiple functions, then the module node contains multiple named executables. In this sense, a module groups together a bunch of functions under a common namespace.
Process API
Module may need a new API to retrieve results from, such as /process/fs/<location>/<name> (alternatively, the existing GET API can be returned but variables can be required to have valued specified in the request). A POST should be required to run a process inside a module, and the body of the post must be JSON / EJSON which specifies values for all named parameters. For example:
{"num": 2.3}

Metadata API
Retrieving metadata on a module should specify the names of all functions (in the directory listing of the mount?) and the number and types of parameters required by all the functions. This will enable front-ends built on top the API to prompt for appropriate inputs to each of the functions.
Imports
No doubt, one of the first things users will want (after they can create functions) is to be able to import them across different queries. We should think about whether to define that here or defer to later. At least for the initial bare bones implementation, users could copy/paste definitions in each SQL file, which seems like a reasonable if painful workaround.
import `/foo/bar/baz/`;

Caching
Notes on Caching: Not intended to be implemented in 4.2.
Caching a parameterized view is equivalent to computing all possible values for all parameters, and running the query for each value. In practice, using GROUP BY, the process can be collapsed into a single query.
Caching requires the determination of the possible values for all parameters (which can yield a non-empty result set). This is an algebraic problem that may or may not have a solution depending on the query.
For example, the following function may not be cached:
CREATE FUNCTION ARRAY_LENGTH(:foo)
BEGIN
  COUNT(:foo[_])
END

The reason the function may not be cached is because the number of solutions for :foo which produce a non-empty result set is infinite.
However, the following function may be cached:
CREATE FUNCTION USER_DATA(:user_id)
BEGIN
  SELECT * FROM `/root/path/data/` WHERE user_id = :user_id
END

In this case, the number of solutions for :user_id which produce a non-empty result set is finite, and can be determined by distincting the user_id field in the source data set.
Such a function may be cached efficiently through generation, execution, and indexed storage of the following query:
SELECT{"variables": {"user_id": user_id}, "result_set": [* ...]}
  FROM `/root/path/data/`
  GROUP BY user_id

If such a result set has an index on variables.user_id, or if the result set is stored as a map from variables to results, then lookups / evaluation of the function become O(1).
Note that even partial solutions for a parameterized view can accelerate results. But if no part of a parameterized view can be cached, then acceleration is going to require more traditional techniques (storage in memory, indexing on relevant fields, incremental computation, etc.).
Subtasks

[x] Extend SQL AST and enhance compiler to apply SQL functions
[x] Extend SQL parser to support user-defined functions and imports
[x] Extend SQL parser to parse modules (i.e. lets+functions without terminal expressions)
[x] Introduce module (mount?) in file system
[x] Support file system operations (metadata, etc.) for module type
[x] Enhance metadata API for module (mount?) & functions in module
[ ] Introduce evaluation API for functions in module (or reuse GET API but require params)
[ ] Update permission system for module (if necessary)
[ ] Implement support for imported modules (final task)

@beckyconning Please review.

Technical review & final specification by @sellout

My estimate (in 8 hour days) for the sub-tasks:

4 days
2 days
1 days
3 days
2 days (if necessary)
4 days
3 days
2 days
4 days

Didn't see this @. I'm reviewing now.

Is the intention that the following would work?
Access the folder /
Create a new MongoDB mount named test-mount with the database testDb
Access the folder /test-mount/testDb
Create a folder named processes
Access the folder /test-mount/testDb/processes
Create a new SQL² mount named userData with the query
CREATE FUNCTION USER_DATA(:user_id)
BEGIN
  SELECT * FROM `/root/path/data/` WHERE user_id = :user_id
END

Access the folder /test-mount/testDb
Create a new workspace named User
Rename the unnamed deck to User Id
In the deck named User Id
Insert a Build Variables Card
Add number variable user_id with default value 0
Insert a Show Variables Card
Wrap the deck named User Id
Rename the unnamed deck to User
Mirror the deck named User Id
Rename the unnamed deck to User Table
In the deck named User Table
Insert a Query Card
Provide the query
import `/test-mount/testDb/processes/userData`;
userData(:user_id)

Insert a Preview Table Card

@beckyconning This is basically correct, except it would be a SQL2 module mount, not a query mount. However, the main use of this will not initially be in user-imported modules, but rather in the front-end translating queries that use variables into modules, and then supplying values for those variables at query time. In this way, variable values can be separated from anything in the file system (including module mounts, etc.), which means they can be stored in user-storage and updated independently by many concurrent users. The one detail we should try to hammer out ASAP is how scoping will work in the presence of modules, maybe pull in Nathan into that conversation.

Cool. The primary intention for this to be used via the API by SlamData to allow for read only deck consuming is clear. I wasn't sure about this secondary use case but this clarifies it. So to support this secondary use we would need to add a mount type for SQL2 Modules.
This all seems to make sense.
If I understand correctly the way this would be used in the front end is that module(s) would be created which contain processes which represent views during deck authoring. All views will be represented as processes.
Cards can be chained by creating processes expressed in terms of another process which take all the arguments required for the subexpression.
Then during deck evaluation rather than using IMPORT each process will be called via the HTTP API.

Following the spec above an example of this may be
-- /mount/db/workspace/processes/aa8sdf798a7 created by the authoring of a Query Card
CREATE FUNCTION aa8sdf798a7(:country, :event)
BEGIN
    SELECT * FROM `/mount/db/olympics` WHERE country = :country AND event = :event
END;

-- /mount/db/workspace/processes/akljsd8a92 created by the authoring of a Query Card which follows the prior query card
IMPORT `/mount/db/workspace/processes/aa8sdf798a7`;
CREATE FUNCTION akljsd8a92(:name, :country, :event)
BEGIN
  aa8sdf798a7(:country, :event) WHERE name = :name
END;

Then during evaluation the following HTTP request would be made using the variables provided
GET /test/workspace/result/akljsd8a92?name=Mo Farah&country=UK&event=100 Metres Sprint
This would allow for evaluation with only “View” permissions and therefore deck consuming with only “View” permissions as well as the provision of locally stored values for these variables.
Would there be one module per workspace, one module per deck or one module per process?
Perhaps processes will be named after the card they were created to serve.

@jdegoes is there a separate issue for enhancing compile to be able to provide information about a query's dependencies on processes, or is that a subtask that should belong in here too?

@garyb We need to make a separate task.
I assume you want compile to report on whatever module imports are in the query? Or something else?

I would only use modules for views with variables. For views without variables, I think better interaction will be achieved with ordinary view mounts.

I assume you want compile to report on whatever module imports are in the query? Or something else?

If we could get both imported modules and the functions used that'd be ideal I think.

I would only use modules for views with variables. For views without variables, I think better interaction will be achieved with ordinary view mounts.

Yeah, our intention was to do that - although as soon as a parameterized view is introduced in a chain of cards every view after that will also have to be a paramtereized view I think, since we'll need to propagate variables backwards from the "end".

@garyb See here and please add or clarify depending on your needs.

@jedesah hi! would you be up for talking me through where you're up to and what you've got left at some point today or on monday?

@beckyconning Happy to do so! How about we do that on Monday. In case you didn't notice already, I've been check marking the subtasks that are done. Although, unfortunately, a few of the ones marked as done have not yet been merged to master (we're still are pretty bad about review times)

Everything is done and in master except for imports. Will move this whole issue to May iteration to track work on imports though instead of creating a new issue for them.


importsNotUsedAsValues in JS files elides imports incorrectly

TypeScript Version:  4.0.0-dev.20200508

Search Terms:
importsNotUsedAsValues
import eliding
Code
In TypeScript 3.8, a new importsNotUsedAsValues feature/compilerOption was added. This, however is producing different output based on if the file is .ts or .js.
tsconfig.json
{
  "compilerOptions": {
    "allowJs": true,
    "noResolve": true,
    "importsNotUsedAsValues": "preserve",
    "target": "ES2015",
    "outDir": "./out",
    "types": []
  }
}

test.js
// @ts-nocheck
import * as moment from 'moment';
import rollupMoment__default from 'moment';
export const moment = rollupMoment__default || moment;

Output
// @ts-nocheck
import * as moment from 'moment';
import 'moment';
export const moment = rollupMoment__default || moment;

Removing the importsNotUsedAsValues option, which is equivalent of having the value of remove will produce:
// @ts-nocheck
import * as moment from 'moment';
export const moment = rollupMoment__default || moment;

Changing the file extension from .js to .ts will produce the correct output for both cases
// @ts-nocheck
import * as moment from 'moment';
import rollupMoment__default from 'moment';
export const moment = rollupMoment__default || moment;

Expected behavior:

Used imports are not elided.
Given the same input it should produce the same output, irrespective of the file extension.

Actual behavior:

Given a JS input the import is elided incorrectly.

Playground Link: Playground doesn't have the importsNotUsedAsValues options.
Related Issues:  None that I can find.

Note: this bug is also present in 3.8 & 3.9.

Playground Link: Playground doesn't have the importsNotUsedAsValues options.

https://codesandbox.io/s/typescript-importsnotusedasvalues-preserve-bug-demo-qm23x
still an issue, multiple issues actually:

ts.transpileModule call
let result = ts.transpileModule(source, {
  fileName: "test.ts",
  compilerOptions: {
    target: "es2015",
    importsNotUsedAsValues: "preserve", // TS>=3.8 (we have TS=4.2) // -> import "./types"; import "./types.ts"; import "./types.d.ts";
    onlyRemoveTypeImports: true // no help
    //isolatedModules: true, // always true in ts.transpileModule
  }
});

1. unused value imports are removed
import { NotUsedAsValue } from "./mixed"

// ... is transpiled to ...

import "./mixed";

2. all comments before "import type" are removed
// also removed
// comment is removed
import type { SomeType_type } from "./types"
//
// SomeType

// ... is transpiled to ...

//
// SomeType

3. type imports are not fully removed
import { SomeType } from "./types"

// ... is transpiled to ...

import "./types";

@milahu would you mind opening a new issue?

#43693 (sorry for the noise)


Implement exit game on in-game screens

US: Exit the game #34
PREREQUISITES:

UI Prompt confirmation must exists

GODOT:

Implement the logic behind the press of Escape button

pause the current state of the game
pause possible sound effects (only clickable hexagon)
emit a signal notifying the game to spawn the confirmation prompt

BOUNDARIES:

What this task handles is the implementation, by emitting a signal, of the logic of the Escape button pressure

OUTCOMES:

Emit exit the game signal

Missing tests and disabling hover on hexagons


Add REST Data Connector

Add REST Data Connector to the community portal.

Coverage remained the same at 98.913% when pulling fa5689b017727b6d57aaf47107edb54ef33249d8 on niranjan94:patch-1 into 26a1f61c93110dba2f9b303ca06e8f093d4e8c31 on tableau:master.


Investigate inline-editing with core data

Ideally it'll be possible to support it.
Demonstrate in the TablerCoreDemo app.
It may be tricky to determine when to save the view context.

Done. See example in TablerCoreDemo.


Update minimum required azdata engine version - Arc

Pull Request Test Coverage Report for Build 723298357

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 43.527%

Totals

Change from base Build 723285344:
-0.002%

Covered Lines:
26107

Relevant Lines:
54819

💛  - Coveralls


Edit message module

Can you please add a module to edit the thread in a 5 minute range after posting it as it is possible in the app.
Thank you

I can look into that this weekend, thanks for the suggestion!


failed to connect data database

Please answer these questions before submitting your issue. Thanks!
Gorse version
install by docker
version "3"
image: zhenghaoz/gorse-in-one
Describe the bug
{"level":"fatal","ts":1690717078.0727994,"msg":"failed to connect data database","error":"dial tcp <IP_ADDRESS>:3099: connect: connection refused","errorVerbose":"dial tcp <IP_ADDRESS>:3099: connect: connection refused\ngithub.com/zhenghaoz/gorse/storage.ProbeMySQLIsolationVariableName:83: \ngithub.com/zhenghaoz/gorse/storage/data.Open:154: ","database":"mysql://xxxxx:xxxxxxxxxx@tcp(mysql:3099)/gorse?parseTime=true"}
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

mysql problem


Remove CAST in example in sys-fn-xe-file-target-read-file-transact-sql.md

Remove CAST on timestamp_utc on the last example. The column is already a datetime2(7), so the CAST is not required, and could be seen to imply that the column is a different data type.

Thank you! We'll incorporate this into an internal PR that refreshes the underlying article, and you will retain credit.

housekeeping ...
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Clean refactor pre-2fa

Moves some methods required by 2fa out of app.js and into

utils/sms.js
utils/email.js
utils/near.js

In the second commit, these functions are removes from app.js and imported instead.
The is a require refactor pre-2fa since 2fa depends on these utils as well.

Looks like checks have passed. Is there anything else blocking?
This is the minimum refactor of shared methods needed to be broken out before I can add more 2fa PRs.

Closing to trigger a new build on Render with a new PR for the same branch.

New PR here to trigger Render build: https://github.com/near/near-contract-helper/pull/188


Homework 2 Problem 2

Need to evaluate model on multiple hyper parameters:

different learning rates
different optimizers – Adam and SGD

We need two different plots for costs/epoch iterations, one for Adam and one for SGD.

Need to complete Problem 2, recommendation system and comparison between optimizers.

Thank you Isaac, I will take this part. -- Ahreum


Docs: Update ADRs

Update existing ADRs:

[x] Minor updates to reword "OARS" as "Aspects": https://github.com/openedx/openedx-aspects/pull/104
[x] Supersede 6. Areas of responsibility with a single tutor plugin repo instead: https://github.com/openedx/openedx-aspects/pull/105

Add new ADRs for:

[x] Protections for PII: https://github.com/openedx/openedx-aspects/pull/106
[x] Internationalization/localization/translations: https://github.com/openedx/openedx-aspects/pull/107, https://github.com/openedx/openedx-aspects/pull/110
[x] Course tree data https://github.com/openedx/openedx-aspects/pull/109
[x] Division of responsibilities between clickhouse and dbt: https://github.com/openedx/openedx-aspects/pull/112
[x] Don't use JSON field in clickhouse -- all useful data should be pulled out into MV fields. https://github.com/openedx/openedx-aspects/pull/113

@bmtcril I've reviewed the existing ADRs and found most of them to still be accurate, but these updates are worth doing:

Most need minor updates to reword "OARS" as "Aspects".
6. Areas of responsibility references multiple tutor plugins (tutor-contrib-clickhouse, tutor-contrib-ralph, tutor-contrib-superset).
This ADR should reflect the consolidated structure chosen for https://github.com/openedx/tutor-contrib-aspects

I think ADRs for these topics could be added:

Protections for PII
Internationalization/localization/translations
Course tree data
Materialized views stored in dbt: https://github.com/openedx/tutor-contrib-aspects/issues/533)
Don't use JSON field in clickhouse -- all useful data should be pulled out

Do you agree? Are there any other decisions you'd like me to write up?

I think these are great, there are probably more but I'll add them as their own tasks if need be. Thanks for tackling this!

Huge thanks to you, @Ian2012 and @bmtcril , for your guidance and reviews on these PRs!
Closing this issue.


runme: 3.0.2 -> 3.7.1

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

hi @momeemt @wegank - I managed to fix up these tests

Result of nixpkgs-review pr 342152 run on x86_64-linux 1

1 package built:

runme

Result of nixpkgs-review pr 342152 run on aarch64-darwin 1

1 package built:

runme

This package is now succeeded to build on aarch64-darwin and x86_64-linux. Looks good to me :)

test timeout on aarch64-linux
@ofborg build runme

3.8.3 https://github.com/NixOS/nixpkgs/pull/346800


FRONTEND WITH FRAMEWORK: VueJS-2.4 => Watchers in Vue.js

Description
Contributors are required to explain about Watchers in Vue.js, which should cover questions like:-
What are Watchers in Vue.js?
Why there is a need for watchers as we already have computed properties?
When do we have to use this?
How does this work?
How to implement Watchers with code (also give theory explanation of code)?
You can take 2-3 examples with codes of different types to explain this.
etc....
Note:
Plagiarism is strictly prohibited.
Changes should be made inside the Frontend_Web_Development_React_Angular_Vue/ dir inside Frontend_Web_Development_React_Angular_Vue branch.
Files need to be added into the Week2 folder only.
Domain
Frontend Dev React/Angular/Vue
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

If you don't know this framework. Don't worry still, you can contribute.
Here I am attaching some references for you.
https://vuejs.org/v2/guide/
https://www.tutorialspoint.com/vuejs/vuejs_overview.htm
https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Client-side_JavaScript_frameworks/Vue_getting_started
You can also study from any other source to learn.
Note -> These references contents are not to copy/paste. Avoid copy/paste, We will be checking.

/assign

Hey @Dhruvsinghjadon, any updates?
It's being too long, we are not getting any updates from your side.
If you are facing any problems while working on this issue. Let us know. We will help you out.

@Hritik157 Its assigned to you now,Please try to make pr faster


feat($IncludedByStateFilter): add parameters to $IncludedByStateFilter

Add parameters to the $IncludedByStateFilter:

params
options

This allows to use more parameters on this filter and not only the fullOrPartialStatename parameter.
Thanks to this improvement, the following now works (takes in account the id param):

It works

Closes #1735

Any news about this PR? :wave:

Sorry for the wait.

No problem.
Thanks! :sparkles:


Use a variable for resources path

Would it be possible that you use an "overridable" variable in the less source code in order to define resources path (actually, the path to images files)?
I'm trying to import the less source file in my app from the node_modules folder, but the path to images turns to be wrong when importing the less file from another location.
As an example, Twitter Bootstrap as an @icon-font-path variable which you can set yourself to solve the same issue :)
Or if you have any other/better idea to make usage of this cool colorpicker with npm easier, please do.

+1, I'm having the same issue.

@ClementParis016 having a separated variable in the less file will work?
@imgPath: "../img/bootstrap-colorpicker/";

.bgImg(@imgFilename){
    background-image: url("@{imgPath}@{imgFilename}");
}

Yes @mjolnic, this is the idea.
Then you can use it like this to override it on purpose:
@import "../node_modules/bootstrap-colorpicker/src/less/colorpicker"; // import first
@imgPath: "../img/smthg/"; // override after

Also, it would be a good idea to document it since people could be using the same variable name without knowing it which could lead to conflicts (or at least confusion) ;)

Thanks @ClementParis016 it has been changed since version 2.3


Add orthogonal polynomial schema

To support serialization of Legendre, Chebyshev, and Hermite polynomials

Fixed and pushed.

fixed the version error in the examples.


ELIFECYCLE for npm install<EMAIL_ADDRESS>

Creating an empty directory and running npm install<EMAIL_ADDRESS>inside returns the ELIFECYCLE error whereas the latest-0.19.1 has no issue.
I'm using archlinux and node 12.9.1 installed via fish-nvm.
Here is the npm log
2180 verbose stack Error<EMAIL_ADDRESS>install: `npx binwrap-install`
2180 verbose stack Exit status 1
2180 verbose stack     at EventEmitter.<anonymous> (/home/matthieu/.config/nvm/12.9.1/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:326:16)
2180 verbose stack     at EventEmitter.emit (events.js:209:13)
2180 verbose stack     at ChildProcess.<anonymous> (/home/matthieu/.config/nvm/12.9.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
2180 verbose stack     at ChildProcess.emit (events.js:209:13)
2180 verbose stack     at maybeClose (internal/child_process.js:1021:16)
2180 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
2181 verbose pkgid<EMAIL_ADDRESS>2182 verbose cwd /home/matthieu/temp/elm/npm
2183 verbose Linux 5.4.45-1-lts
2184 verbose argv "/home/matthieu/.config/nvm/12.9.1/bin/node" "/home/matthieu/.config/nvm/12.9.1/bin/npm" "install"<EMAIL_ADDRESS>2185 verbose node v12.9.1
2186 verbose npm  v6.10.2
2187 error code ELIFECYCLE
2188 error errno 1
2189 error<EMAIL_ADDRESS>install: `npx binwrap-install`
2189 error Exit status 1
2190 error Failed at the<EMAIL_ADDRESS>install script.
2190 error This is probably not a problem with npm. There is likely additional logging output above.
2191 verbose exit [ 1, true ]

I recently tried a couple of things out with Elm 0.18 and needed to use Node.js 10 in order to install it from npm.

Indeed this seems to be working with node 10 but not with 12 or 14. Thanks for the tips!


Online docs for main

What problem does this solve or what need does it fill?
docs.rs doesn't provide documentation for main; which can lag behind the latest release.
This also makes it hard to show off new merged documentation improvements.
What solution would you like?
Host the latest nightly docs on bevyengine.org, rebuilt after every merged PR.
What alternative(s) have you considered?
Clone the bevy repo and use cargo doc. This can't be linked, goes stale, takes a while to build and is harder for beginners.
Additional context
Discussed in #1721 and on Discord.

Why not host on GitHub pages for this repo ? That would be the simplest

Why not host on GitHub pages for this repo ? That would be the simplest

I like this actually. It also makes it less discoverable for beginners, which is a benefit in this case.

Seems like this is resolved by #3535 and followup PRs. Closing this.


Fix bloat check workflow concurrency

Problem
We have not had a completed bloat check in 13 hours; new ones keep canceling old ones.
Change overview
Make new bloat checks not cancel old ones, at least if the old ones are running already.
Testing
Will see if it helps when it merges... Hard to test otherwise.

Doesn't this mean we can

Can which?
I'm still concerned that a newly scheduled bloat check might cancel a previously-pending one and hence lose its place in the queue...  Not sure how that works, exactly.

Doesn't this mean we can

Can which?
I'm still concerned that a newly scheduled bloat check might cancel a previously-pending one and hence lose its place in the queue... Not sure how that works, exactly.

Sorry, this was an inadvertent comment.  I was typing while looking at the github docs.
But yes, by my reading new jobs will cancel previously-pending jobs.  But these will no longer cancel the running job.  This seems like it is what we want.  We still have the maximum queue depth of 1, but ensure that the running job always completes.


Unknown prop date on  tag

hi, I get this warning when use the library.
Unknown prop date on <div> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
I use this component as a component inside redux-form
MyForm.tsx
<Field name="DOB" component={DatePickerGroup} />
DatePickerGroup.tsx
import * as React from 'react';
import { findDOMNode } from 'react-dom';
import { DatePicker } from 'material-ui-pickers';
import * as moment from 'moment';
import { WrappedFieldProps } from 'redux-form';

export namespace DatePickerGroup {
    export interface AllProps extends OwnProps, WrappedFieldProps {

    }
    export interface OwnProps {
        id?: string,
        label?: string,
        className?: string,
        shrink?: boolean,
        fullWidth?: boolean,
        margin?: string,
        disabled?: boolean,
        readOnly?: boolean
    }
    export interface State {

    }
}

class DatePickerGroup extends React.Component<DatePickerGroup.AllProps, DatePickerGroup.State> {
    constructor(props) {
        super(props);
    }

    private inputControl: HTMLInputElement;

    handleDateChange = (date: moment.Moment) => {
        this.props.input.onChange(date.format("YYYY-MM-DD"));
    }

    render() {
        const {
            input, id, label, className, shrink, fullWidth, margin, disabled, readOnly,
            meta: { touched, error }
        } = this.props
        const selectedDate = moment(input.value, "YYYY-MM-DD").isValid() ? moment(input.value, "YYYY-MM-DD") : moment(new Date());

        return (
            <div>
                <DatePicker
                    format="DD/MM/YYYY"
                    value={selectedDate}
                    onChange={this.handleDateChange}
                />
            </div>
        )
    }
}

export default DatePickerGroup;

I use:
react: 15.6.2
typescript: 2.5.3,
material-ui: 1.0.0-beta.18
redux-form: 7.0.4

Can you please provide example of code

hi, I have updated the question, it was included the example.

But it works fine, isnt it?

yes, it works fine.. but usually we don't like a warning / error.
here is the screenshot of the warning

Yeah, Im sorry, Ill fix it in the next release, probably today.
Its really strange that I dont have such warning in my demo project.

do you use the same react version / material-ui?
anyway, another input for this library, when we had choose the year value, it is better the selection redirect back to the date selection.
Current, I have manually click on header of "date".
Thank you.

Should be fixed in v1.0.0-alpha.8


Write the "Graphic screen library"

rvc_fwrite(int *ptr, int size, int *memOffset) //write to display a char array
rvc_printf ( const char * format, ... );
clearScreen()
drawPixel(int x, int y)
drawLine(int x1, int y1, int x2, int y2)
drawHLine(int x1, int x2, int y)
drawVLine(int x, int y1, int y2)
drawRectangle(int x1, int y1, int x2, int y2)
drawCircle(int cx, int cy, int r)

Make sure the lib is loadable - this way, it's not HW implementation-specific. (no need to add a new CR)
Simple Access to display as a memory-mapped IO device (MMIO).
You may have "ROM"/"DATA," part of the Graphic lib.

@gilyaakov  - I looks at the API you wrote,
I see the declaration of the functions (draw_char) but not the functions itself

Also in the "graphic_screen_test.c" you have all the definitions there-
don't you need to "include" the API file?

All the API's files resides in library folder (in apps). The header files under inc folder and the implementations under src folder. The code that checks the API's is under examples. There is a Makefile for this.
run it by:
./buildl.sh -lib graphic_screen_api_test.c

Ok..
So why dos the "graphic_screen_test.c" have functions?
don't we need to "include" in the header?

It's just a sketch of the library, it's helps to check everything is ok. The library was build from this code. The code that linkage with libraries is in apps/library/examples


Lutron triggers and button #7

I modified a keypad in Essentials > Design to configure the keypad for 7 buttons. When I create the devices from the repeater with the Lutron plug-in, there is a new device, keypad button 7, modeled after the raise (or lower?) button '.18.
When creating a new trigger, I don't believe the new button 7 is listed in the available buttons; the '.18 and '.19 are listed, but in at least one of my keypads, indigo does not respond to either one.

Not sure what you mean by "modeled after the raise (or lower?) button '.18."  When I change one of my keypads to a W7B (instead of a W6RL), I just get a button 7, similar to buttons 1-6.  But no matching LED device.
If you didn't delete the raise and lower buttons (18 and 19), then they'll still be in the popup.  The plugin does not delete devices that no longer exist.   Those buttons no longer exist on the Lutron side, so you'll never get a notification for them.
Button 7 was certainly listed for me:

I do not have any W7B keypads, so I can't test whether they actually send out a status that the plugin can act on.  You can test that yourself by enabling debug logging (not detailed debugging), and see if you get a sequence like this when you press the button:
   Lutron RRA2/Caséta Debug        Received a keypad button/LED status message: ~DEVICE,11,5,3
   Lutron RRA2/Caséta Debug        buttonTriggerCheck: deviceID: 11, componentID: 5, gatewayID: 4452640
   Lutron RRA2/Caséta Debug        Received a keypad button/LED status message: ~DEVICE,11,5,4
   Lutron RRA2/Caséta Debug        buttonMultiPressCheck: Timeout reached for keypadid = 4452640:11.5, presses = 1

The componentID should be 7.

Joe - Sorry to be so slow replying - I've had some medical issues.
I just performed the debug test you suggested: For a 6 button keypad, I get
the same event log messages you quoted; for a keypad I configured in
Essentials to W7B (and transferred), neither the up nor the down buttons
are recognized with an entry in the event log. - also true for a
simultaneous press of both buttons.
Please let me know if the 7th button can't be used - I'm laying out my
keypads now, and need to know before I order engraving.
Thanks,
Bob
On Tue, Sep 6, 2022 at 7:00 PM Joe Keenan @.***> wrote:

Not sure what you mean by "modeled after the raise (or lower?) button
'.18." When I change one of my keypads to a W7B (instead of a W6RL), I just
get a button 7, similar to buttons 1-6. But no matching LED device.
If you didn't delete the raise and lower buttons (18 and 19), then they'll
still be in the popup. The plugin does not delete devices that no longer
exist. Those buttons no longer exist on the Lutron side, so you'll never
get a notification for them.
Button 7 was certainly listed for me:
[image: Screen Shot 2022-09-06 at 9 44 19 PM]
https://user-images.githubusercontent.com/72976/188771803-dc2f8b1a-b85c-4139-8c36-e1ba46bf1a84.png
I do not have any W7B keypads, so I can't test whether they actually send
out a status that the plugin can act on. You can test that yourself by
enabling debug logging (not detailed debugging), and see if you get a
sequence like this when you press the button:
Lutron RRA2/Caséta Debug        Received a keypad button/LED status message: ~DEVICE,11,5,3
Lutron RRA2/Caséta Debug        buttonTriggerCheck: deviceID: 11, componentID: 5, gatewayID: 4452640
Lutron RRA2/Caséta Debug        Received a keypad button/LED status message: ~DEVICE,11,5,4
Lutron RRA2/Caséta Debug        buttonMultiPressCheck: Timeout reached for keypadid = 4452640:11.5, presses = 1
The componentID should be 7.
—
Reply to this email directly, view it on GitHub
https://github.com/FlyingDiver/Indigo-radiora2/issues/55#issuecomment-1238822305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH5RS3ECHN5UXGPO2AKXI33V47ZMZANCNFSM6AAAAAAQETKN6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

If there's nothing in the log then the plugin isn't being notified and there's nothing I can do about it.

That doesn't make sense. Other than no LED, the seventh button is the same. Why would there be a 7 button keypad if it doesn't send a signal. In Essentials, I specified a W7B button kit on the Design page. Perhaps when installing the physical 7B keypad, it enables the 7th button? I was just reminded of another possibility: my Lutron Repeater regularly loses connection after a transfer, which requires power cycling and a long wait.
I haven't given up on button 7.


Follow API Guidelines

What
Changed APIs to follow the swift API guidelines.
How
See issue #96 for full list of transformations.
Testing
No new tests, no longer applicable tests have been removed.
Issues
Part of #96.
Notes
CouchDBClient methods haven't been touched in this PR, I'm still unsure about the names that I proposed in the issue.
The code base will need another look through to make sure that the operations are consistent with naming and parameter ordering etc. before #96 can be resolved.

A few things outstanding from #96 and review:

revID to revision
Create*QueryIndexOperation

indexName to name
designDoc to designDocumentID

GetDocumentOperation

revs to includeRevisions

QueryViewOperation & ViewOperation

updateSeqto includeLastUpdateSequenceNumber

HTTPInterceptor

ctx: to in context:

I'm not sure how much of that you wanted to defer to a later PR, but I think point 1 probably makes sense to do here given the extent of the doc/comment update changes for documentID anyway.

and the CouchDBOperation changes, but you explicitly called them out as not part of this PR.

@ricellis Done all the ones you pointed out, and CouchDBOperations? I remember about the CouchClient.add(operation:) methods not going in here.

+1


API for tools (get_psl__toolId__json) not working

When I try the example: https://training.galaxyproject.org/api/#/tools/get_psl__toolId__json
with toolshed.g2.bx.psu.edu/repos/iuc/abricate/maaslin2 I get an empy json.

The most likely cause then is that we haven't observed it on any of the servers that we check. Is it installed somewhere?

We can only collect this information from running galaxies with that tool installed.

sorry I meant the default example toolshed.g2.bx.psu.edu/repos/iuc/abricate/abricate which is on EU ...

You are missing the .json on the end...
https://training.galaxyproject.org/training-material/api/psl/toolshed.g2.bx.psu.edu%2Frepos/iuc/abricate/abricate.json

/psl/{toolId}.json
Get the GTN's public server tool listing for a specific tool ID. It lists all known public servers that are reachable at the time of the GTN's deployment, and which versions of this tool are available. It's very important that you strip the version component!

not sure why that's not being added by swagger since it's in the path provided, but it's at least documented :sweat_smile:


Fix AD Claim Mapping to User Extended model

Fix for reported issue: https://github.com/snok/django-auth-adfs/issues/241

Thank you for the great feedback ! I implemented all the requested changes.
However, not really sure what you require for the Documentation and Testing (very first PR on a public repo), could you help me out?
Thanks in advance !

@tim-schilling Added commit https://github.com/snok/django-auth-adfs/pull/242/commits/ac6d4984f4cf66bfddfcef87194cbd122e4d5c5b which holds documentation of the PR

Regarding the test here's one way to solve it:
You'll need to create a models file in the tests/ directory that creates a user extension model. You could name it profile, and set it to have a OneToOneField to User. Give it some random property.
Then the actual test should be similar to test_boolean_claim_mapping, but using the CLAIM_MAPPING setting that will try to update the Profile model for the user.

Ah, shoot. There's a problem here. Django doesn't automatically create related fields. So in the case of the User instance being created, you would need to wire up a post_safe signal receiver or something equivalent to create the profile when the user is created. That would guarantee that the profile instance would exist when we hit the update_user_attribute flow.

@WCONFR alright this should be good. If any of the build actions fail besides the coverage case, they need to be resolved.

Ok, fully understood. Thanks for your work on this, I will be patiently waiting for the second review.

This looks good to me.

Ideally we'd have better coverage of the exception flows in update_user_attributes

Yeah, ideally 😁 I'm happy with merging this as it is, though. 😊

@JonasKs Done, thanks for completing the merge

Thank you so much for the contribution, and to @tim-schilling for helping out like a champ! 😊

@JonasKs Do I need to do something to merge the PR since it has been approved ? Don't want to rush you, just want to be sure that you're not waiting on action from my end.

No, you're good, thank you. I've just been packed with work so haven't got around to it. I'll do it later 😊

Sorry for the delay! This has been released in 1.10.0. Thank you!
https://github.com/snok/django-auth-adfs/releases/tag/1.10.0


PL Release Notes 788xx

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://hdh.pr.harness.io/pr-1078

Preview environment: https://hdh.pr.harness.io/pr-1078

Preview environment: https://hdh.pr.harness.io/pr-1078


Nether

This is The best shader ngl, It also work on my low device, But It's too dark in nether

@Mcbamboo

lighting for nether and endworld will be added in the next version (wip)
thanks for trying!


fix: Further fix on #800

Fixes some add-calls to work properly with @skey

This PR is going to be replaced by another.


Set Dynamic tabBarStyle

Version
Tell us which versions you are using:

react-native-router-flux v3.36.0
react-native v0.37.0

Expected behaviour
I expected the tabBar to re-render as I pass it a new tabBarStyle
Actual behaviour
tabBar remained the same
Steps to reproduce

Create a tabBar scene:

<Scene key="NAV" tabs={true} tabBarStyle={[view.background_secondary, {backgroundColor: color(this.props.bootstrap).secondary}]} type={ActionConst.RESET}>

Pass in new props through the color function.
Expect a change.

For those who are curious, you can pass in a custom tabBar as a component={} in the tab={true} scene.

@Rayji96 how did you do this? I'm trying to create a custom tabbar, but the component won't receive the computedProps from the parent (hideNavBar, hideTabBar, isActive)


Update AWS Credentials lookup to use AWS default provider chain.

This PR replaces #3790.
Fixes #3748
Fixes #533
This change adds support for automatic configuration of AWS credentials from Instance Roles when running docker-machine from an EC2 server or ECS container. It replaces the original credential lookup code with an Amazon ChainProvider that retrieves credentials from the first valid source in this list:

Static credentials from the --amazonec2-access-key, --amazonec2-secret-key, and --amazonec2-session-tokencommand line options
Amazon's default credential chain: (at time of submission)
a.  Environment Variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY)
b.  Default profile in ~/.aws/credentials
b.  IAM Role (on supported AWS infrastructure)

Let's take all the ECS-related information out of the docs changes.  While it might incidentally be the case that supporting the upstream's updated authentication mechanism enables this, I don't want folks to conflate Machine and ECS.  They are two separate offerings from separate companies and folks will get very confused if we reference ECS from our documentation.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "aws-iam-roles" git@github.com:mrburrito/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~4
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "aws-iam-roles" git@github.com:mrburrito/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~4
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Removed reference to ECS (which was purely my motivation in implementing this!). It definitely has the possibility of confusing things.

Instance roles in general are a nice pickup and have been asked for before.
Looks pretty good -- @londoncalling any chance you take a quick look at these docs and tell me what you think?

@nathanleclaire @mrburrito docs changes look good but we are moving to a new consolidated docs repo: https://github.com/docker/docker.github.io
Let's merge your changes here, and I will attempt to cherry-pick these in :-)
After this, please make docs PR requests to https://github.com/docker/docker.github.io. If they accompany code changes, link the code change PR / issue to the docs PR. Nathan and I are going to chat further about this in the next couple of days, so we will settle on a process and let everyone know.

@londoncalling made the docs changes for you and submitted a PR. will do the same for my other open PR

👍 thanks @londoncalling @mrburrito

Code looks pretty good.
All docs over on migrated repo now so you should rebase this to not have them any more and follow up there to get those changes merged in.
Thanks!

Rebase complete. PR should already be on the docs repo (https://github.com/docker/docker.github.io/issues/36)

@nathanleclaire new docs PR submitted for the vnext_machine branch

Thanks @mrburrito

LGTM

Does anyone know what happened to this feature? Latest AWS driver doesn't seem to have IAM role support?


feat: [M3-7538] - Cloud Manager Docs with Vitepress

Description 📝
This is the latest iteration of a docsite generation for the Cloud Manager docs.
It iterates over the two previous POCs:

https://github.com/linode/manager/pull/9960
https://github.com/linode/manager/pull/10002

This version addresses the concerns of added dependencies to build the docs and utilizes the much better looking vitepress version. Instead of adding dev dependencies to the monorepo we utilize npx (more specifically its bun equivalent bunx) to get those on the fly during build time.
As a result there's 0 dependencies added to generate our docs 🎉
The same process is used to develop locally.
The pages will eventually live at https://linode.github.io/manager/ but until then the PR has been merged we can see the result at:
👉 https://abailly-akamai.github.io/manager/
Thanks @bnussman-akamai for the vitepress suggestion, GH action and @mjac0bs for the inspiration!
Note: We will need to also link to this documentation from the README and in other knowledge sources, tasks that will be done separately (we also need to clean/update the docs themselves)
Changes  🔄

Configure vitepress to build our docs automatically

Preview 📷

How to test 🧪

verify build steps: https://github.com/abailly-akamai/manager/actions/runs/7400941878
verify documentation quality: https://abailly-akamai.github.io/manager
locally, pull code and run yarn docs to get the local version

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[x] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[x] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[x] 📱 Providing mobile support
[x] ♿  Providing accessibility support

@jdamore-linode I generally agree that npx would be nice to not introduce additional dependency. The only reason I'm okay with (and encouraged) bunx here is because I'm really hoping and betting on Bun replacing node for us in over the next few months/years. I figured this would be a low friction way to start integrating Bun into our workflow.
If we want to keep is simple, I'm fine with reverting to npx for this, I just really want Bun to work in the long run!

Thanks @bnussman-akamai, that makes sense to me! I'm happy (and excited) to give Bun a shot. Also just noticed the addition to CONTRIBUTING.md that mentions the Bun installation, so feel free to disregard what I said about GETTING_STARTED.md.

I just really want Bun to work in the long run!

Hear, hear!


Added C++ version

Thanks a lot!
Can you comment on the following error message?
error: 'invalid_argument' is not a member of 'std'

Apart from that, can you make the two methods static, as in the implementations for the other languages?
Thanks!

Sorry for the exception - Missed the header library.
Made the functions static. Please let me know if you need any other change.

No problem, and thanks a lot for fixing these two issues!
There's one new thing now I'd like to see changed: Could you cache the result of alphabet.length() in a (static) constant again, just as you did before? It doesn't need to be executed every single time.

done

Thanks a lot!
Merged in https://github.com/delight-im/ShortURL/commit/86aa12d26e598d6964111b67eb31256bfc6a754e


[BEAM-11089] Fix DataflowRunner view override outputs

This fixes the failure demonstrated in #13121 where the DataflowRunner overrides corrupt the graph and adds a checkState that prevents it from recurring.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

run dataflow validatesrunner

run dataflow validatesrunner

R: @lukecwik if you are interested and have time but tagged @boyuanzz also
This is a fix towards #13053, part of portable job submission.