Display each services routes in open api

--project-name
-services
---composer
---user-service1
---user-service2
---user-service3
-package.json
-platformatic.json

As you can check here i'm getting two routes only which belongs to user-service1, because i have added added user-service1 to as a entrypoint in platformatic.json,
if i'm changing entrypoint in platformatic.json with user-service3, i'll get routes of it,
Now, can i show all my services routes in above image, instead of only one service routes,
And this should be beneficial for me if i want to separate it with different tabs, ex (expand, collapse) of each services , like platformatic/db feature
Thank you

entry point should be composer,
and to group it there is one flag available in routes, can use it


No compatible version found<EMAIL_ADDRESS>

Not sure why I get this or how to solve it
  "devDependencies": {
    "casper": "^1.1.1",
    "casper-chai": "^0.2.1",
    "casperjs": "^1.1.0-beta5",
    "mocha-casperjs": "^0.5.5"
}

 npm install
npm ERR! Darwin 15.4.0
npm ERR! argv "/usr/local/Cellar/node/5.0.0/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.0.0
npm ERR! npm  v3.3.9

npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! 1.1.0-beta5, 1.1.0-beta4, 1.1.0-beta3, 1.1.0-beta2
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

Because the new npm is not released. Hold on, this will follow tonight (CEST).

I published the new version right now. Installing CasperJS by means of npm works for me, both locally and globally.
@dschinkel Please note, however, that you only need to include casperjs and that the release is 1.1.0. So you might want to try with something like
  "devDependencies": {
    "casperjs": "^1.1.0",
    "casper-chai": "^0.2.1",
    "mocha-casperjs": "^0.5.5"
}

looks like your push did it...thanks!


VirtualList - Allow template7 syntax in 'emptyTemplate' method

This is a (multiple allowed):

[ ] bug

[x] enhancement

[x] feature-discussion (RFC)

Framework7 Version: 1.6.5

Platform and Target: All

What you did
I used a virtual list with an emptyTemplate, that includes template7 variables
Expected Behavior
The template7 syntax should have been parsed
Actual Behavior
I can see the '{{emptyList}}' template
It would be great if you could use template7 in the emptyTemplate method of the virtualList

Any sense in this? Empty template doesn't receive any items or whatever because there is no items. Just use plain JS there, otherwise do it manually:
emptyTemplate: Template7.compile('....')()

Thank you for the example of how to do it manually.
I am using it for localization. I made a template7 helper method, that displays a translation for a file


[Feature] sc-28513 Show progress when loading large CSV or parquet file

Signed-off-by: Kent Huang<EMAIL_ADDRESS>
PR checklist

[x] Ensure you have added or ran the appropriate tests for your PR.
[x] DCO signed

What type of PR is this?
Enhance
What this PR does / why we need it:
Enable duckdb enable_progress_bar flag to show progress bar when importing large files into in-memory db
Which issue(s) this PR fixes:
sc-28513
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Based on the design of DuckDB, the progress bar will only be displayed when executing a long query.


Does globalHistogram for a category field work on a sample?

Some doubts have arisen about the internals of this expression, when using a category (string) field

It doesn't although the expression is currently limited to a maximum number of 32768 categories (what should fit most cases)

Have a look at this example for more details:

Using this viz with vancouver_trees

This is the underlying request to Maps API for metadata which reads as

https://cartovl.carto.com/api/v1/map?api_key=default_public&client=vl-1.2.6&config={"buffersize":{"mvt":1},"layers":[{"type":"mapnik","options":{"sql":"SELECT \"genus_name\",\"cartodb_id\",\"the_geom_webmercator\" FROM vancouver_trees ","aggregation":{"columns":{},"dimensions":{"genus_name":{"column":"genus_name"}},"placement":"centroid","resolution":1,"threshold":1},"vector_extent":2048,"vector_simplify_extent":2048,"dates_as_numbers":true,"metadata":{"geometryType":true,"columnStats":{"topCategories":32768,"includeNulls":true},"dimensions":true,"sample":{"num_rows":1000,"include_columns":["genus_name","cartodb_id"]}}}}]}

That executes this code in Maps API which in this particular case is:

 SELECT genus_name AS category, COUNT(*) AS frequency
   FROM (SELECT genus_name, cartodb_id, the_geom_webmercator FROM vancouver_trees) AS __cdb_query
 GROUP BY genus_name ORDER BY 2 DESC
 LIMIT 32768

So there is a limit in the number of categories, with LIMIT, but not the records that feed them (the __cdb_query itself).

The frequencies for the first 32768 categories are good to rely on.

So I'm understanding that globalHistogram will return all categories, with their frequency,  while they are less than 32768, right ? Yes, this works for most cases.


provide default props

It seemed like providing default props would make some of the current validations more useful. Trying out the component, I was exploring the bare minimum needed to render, and I was not able to trigger the console.info call in componentDidMount because those property values did not exist:
this.props.config.postUrl and this.props.eventHandlers.drop triggered fatal errors because config and eventHandlers were not defined.
Providing default props triggered the info call, and Dropzone.js gave a useful error message of
Uncaught Error: No URL provided

Thanks for the component!

Oh hey, great change - thanks a lot :clap: ! I'll push an update to npm with the change right after merging, too.


NeoForge: Invalid Mod File

Modloader version: 20.5.5
Minecraft Version: 1.20.5
Don't know if this is just because neoforge beta but preferred reporting it
invalid mod file net.neoforged.fml.loading.moddiscovery.ModFileInfo@71a3a190 net.neoforged.fml.loading.moddiscovery.InvalidModFileException: Illegal version number specified version (highlight-neoforge-1.20.5-2.5.0.jar)

Fixed in 2.5.1


feat: Updates Aries version

Closes https://github.com/trustbloc/vct/issues/41
Signed-off-by: Andrii Soluk<EMAIL_ADDRESS>

Codecov Report

Merging #42 (7099447) into main (fc0f010) will decrease coverage by 0.57%.
The diff coverage is 40.90%.

@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
- Coverage   85.11%   84.53%   -0.58%
==========================================
  Files          13       13
  Lines        1693     1701       +8
==========================================
- Hits         1441     1438       -3
- Misses        147      157      +10
- Partials      105      106       +1

Impacted Files
Coverage Δ

pkg/client/vct/client.go
85.95% <0.00%> (-5.28%)
:arrow_down:

pkg/controller/command/handler.go
100.00% <ø> (ø)

pkg/controller/rest/operation.go
85.71% <50.00%> (-0.70%)
:arrow_down:

pkg/controller/command/command.go
82.45% <54.54%> (-1.12%)
:arrow_down:

cmd/vct/startcmd/start.go
84.42% <100.00%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


allow configurable strict_slashes in router

Looks like sanic automatically add both with and without trailing slash routes to every route declaration since 0.4.0 207ec1e0322776cd795739a8ce1acf390e8b6888.
I think it would be configurable, maybe by adding strict_slashes parameter to Route constructor. And let the user to pass it manually to the app.
Or maybe also allow adding to any individual route just like Flask does.

I could see adding this knob, but I'm curious why? When would you want http://route.com/get but not http://route.com/get/, or vice-versa?

They could have difference meaning sometimes.
Eg. distinction between file and directory while serving file/directory resource metadata.

Closing with: https://github.com/channelcat/sanic/pull/559


Azure msdeploy Python App Service Issue

I'm trying to deploy an Azure App Service running Flask on Python 3.4.  When I deploy from within Visual Studio (2015) via Web Deploy, everything works nicely.  But, when I attempt to deploy from my CI/CD server (TeamCity 10.0.3 on Windows Server 2012 R2) using an MSBuild step, the deployment succeeds without errors, but my app is apparently missing some crucial components and just throws HTTP errors on every request (my logging isn't able to capture the actual errors because the app is apparently totally hosed at this point).  My build has the following steps and executes against the .pyproj file.  I'm deploying numerous C# applications from this TeamCity instance using Web Deploy without fail:

Command Line Runner - Copy publish profile (because msdeploy looks for it at ~/__profiles for some unknown reason and I can't find a flag or configuration setting to change):
mkdir __profiles   copy *.pubxml __profiles

Command Line Runner - Create venv at top level folder:
c:\python34\python.exe -m venv env

Command Line Runner - Install from requirements.txt:
env\scripts\pip install -r requirements.txt

Powershell Runner - Stop Azure App Service

MSBuild Runner - Deploy (Build file path points to the .pyproj file):
/p:DeployOnBuild=true   /p:PublishProfile="My Publish Profile"  /p:Configuration=Release  /p:AllowUntrustedCertificate=True   /p:UserName=%WebDeployUserName%  /p:Password=%WebDeployPassword%

Powershell Runner - Start Azure App Service

Related question on SO

You could use the Console in the Azure portal to check for differences in the file system on working vs non-working and also run some Python code to check that your virtual environment and packages are working fine.  Interactivity in the console is limited, but it's can still be useful.

One thing to note is that PTVS on VS 2015 will deploy the virtual environment as part of your application code.  Your custom script is creating a virtual env, and the msbuild deploy probably also copies the virtual env.  I don't know what kind of mixed-up deployment that might create.
The basic logging done by Azure can be useful. It's enabled via the portal:

You should look at the contents of web.config on the live site with Web Deploy and MSBuild.  If I recall correctly, some % variables are getting replaced somewhere in the pipeline when using Web Deploy.  If that's not happening, that could be the problem. Ex: %INTERPRETERPATH%

By the way, just so you're aware, things are changing significantly with VS 2017.
The current situation (on VS 2017 Preview) is that we no longer publish a virtual environment.  We also no longer auto-generate web.config files.  The Python interpreter is selected by installing a site extension.  There's no automatic installation of Python packages, you have to log in to the console and issue pip install -r requirements.txt.
Read more at: https://blogs.msdn.microsoft.com/pythonengineering/2016/08/04/upgrading-python-on-azure-app-service/
Other team members are currently working on a CLI that will simplify all these steps, but that's not in yet.

Thanks @huguesv, the web.config variables were in fact the issue.  The following % variables are replaced dynamically by the publish process in VS 2015 (even if I hard code the actual values, they are replaced with these placeholders when running msdeploy from TeamCity);
<appSettings>
    <add key="WSGI_ALT_VIRTUALENV_HANDLER" value="app.wsgi_app" />
    <add key="WSGI_ALT_VIRTUALENV_ACTIVATE_THIS" value="%ROOTDIR%\env\Scripts\python.exe" />
    <add key="WSGI_HANDLER" value="ptvs_virtualenv_proxy.get_venv_handler()" />
    <add key="PYTHONPATH" value="%ROOTDIR%" />
  </appSettings>

<handlers>
      <add name="Python FastCGI" path="handler.fcgi" verb="*" modules="FastCgiModule" scriptProcessor="%INTERPRETERPATH%|%WFASTCGIPATH%" resourceType="Unspecified" requireAccess="Script" />
    </handlers>

I hope PTVS for 2017 allows us to support a CD workflow without having to manually run a publish from VS.  For now, I'm looking at options for automating CD of this app using Docker.

Since all we do in publish now is copy files, you can use any approach to publishing that you like (FTP, DropBox, etc.) after the initial site configuration. The trick is in creating a static web.config that is correct so that you don't rely on the transform step.
For VS 2017 we've added new templates to help create a static one, but the link above (also https://aka.ms/PythonOnAppService) shows what the entries should look like.


Extraction of internal features from the tower representation

We should investigate the internal features of the tower representation. Doing this should provide several benefits:

It should help us identify good features that we can compute directly, and feed into the neural network.
It should help us improve the neural network architecture.

The default network architecture (ResNet) seems to have an odd bias towards a strong activation close to the edge of the board. As can be observed in the diagram below:

This behavior makes sense, consider a set of weights W that are normally distributed, and a positive input x:
y = W [ x₀ x₁ x₂ x₃ x₄ x₅ x₆ x₇ x₈ x₉ ]

If W ∈ N(μ, σ) and μ < 0 then along the edge x₇, x₈, and x₉ are zero:
W [ x₀ x₁ x₂ x₃ x₄ x₅ x₆ x₇ x₈ x₉ ] ≤ W [ x₀ x₁ x₂ x₃ x₄ x₅ x₆ 0 0 0 ]

This hypothesis can be confirmed by investigating the final weights, and checking the mean of the convolution layers:
{
    "01_upsample/conv_1": {
        "mean": -0.0003626140533015132,
        "std": 0.00519569544121623
    },
    "02_residual/conv_1": {
        "mean": -0.00011233328405069187,
        "std": 0.002601742511615157
    },
    "02_residual/conv_2": {
        "mean": -0.00011419910879340023,
        "std": 0.0026016614865511656
    },
    "03_residual/conv_1": {
        "mean": -0.00010304508032277226,
        "std": 0.0026021271478384733
    },
    "03_residual/conv_2": {
        "mean": -6.648160342592746e-05,
        "std": 0.002603317843750119
    },
    "04_residual/conv_1": {
        "mean": -0.0003849344211630523,
        "std": 0.0025755600072443485
    },
    "04_residual/conv_2": {
        "mean": 0.00016120942018460482,
        "std": 0.002599172294139862
    },
    "05_residual/conv_1": {
        "mean": 0.00021969537192489952,
        "std": 0.002594882855191827
    },
    "05_residual/conv_2": {
        "mean": 0.00045546123874373734,
        "std": 0.002564028138294816
    },
    "06_residual/conv_1": {
        "mean": -0.00022857918520458043,
        "std": 0.0025941154453903437
    },
    "06_residual/conv_2": {
        "mean": 0.00020613202650565654,
        "std": 0.0025959957856684923
    },
    "07_residual/conv_1": {
        "mean": -0.0020295707508921623,
        "std": 0.001631724531762302
    },
    "07_residual/conv_2": {
        "mean": -2.099659468512982e-05,
        "std": 0.002604082226753235
    },
    "08_residual/conv_1": {
        "mean": -0.0021902318112552166,
        "std": 0.001408747280947864
    },
    "08_residual/conv_2": {
        "mean": 7.066841476444097e-07,
        "std": 0.002604166977107525
    },
    "09_residual/conv_1": {
        "mean": -0.0021506529301404953,
        "std": 0.0014684603083878756
    },
    "09_residual/conv_2": {
        "mean": -2.3711704670859035e-06,
        "std": 0.002604165580123663
    },
    "10_residual/conv_1": {
        "mean": -0.0015733279287815094,
        "std": 0.002075168304145336
    },
    "10_residual/conv_2": {
        "mean": -0.00012044789764331654,
        "std": 0.0026013797614723444
    },
    "11p_policy/conv_1": {
        "mean": -0.007533475290983915,
        "std": 0.06204431504011154
    },
    "11p_policy/linear_1": {
        "mean": -0.01642797514796257,
        "std": 0.038641564548015594
    },
    "11v_value/conv_1": {
        "mean": -0.0014275580178946257,
        "std": 0.08837682008743286
    },
    "11v_value/linear_1": {
        "mean": 0.00015922913735266775,
        "std": 0.0526527501642704
    },
    "11v_value/linear_2": {
        "mean": -0.010312804952263832,
        "std": 0.06787863373756409
    },
}

As can be seen most of the convolution layers has a negative mean.
edge_tower_representation.zip
Conclusion
The current neural network architecture has a systematic bias towards the edge of the board. This problem is presumably exaggerated by the fact that we clip activations to the range [0, 6].

Some approaches to solving the problem above immediately springs to mind:

Padding with a different constant instead of zero (we could pad with the median of the input distribution, a truncated normal distribution).
Use a per-activation, instead of per-channel, bias after each convolution layer.

Neither of these approaches are supported by cuDNN when running with layout NCHWVECTC and INT8x4.

Even if it might turn out to be tricky to implement said algorithms in cuDNN, we can still train the architectures in Tensorflow and verify whether they result in a lower loss:

Green is per-activation offset
Gray is per-channel offset

As one can observe they are effectively equivalent, with the difference being well within the margin for error.

An alternative attack vector is to try and prevent the non-zero mean for the weights, at which point the zero-padding does not matter anymore.
The most likely culprit for the negative weights mean is the residual connection, which in the AlphaZero architecture looks like this, where Rₖ is the output of a residual block, and Lₖ₋₁ is the output of the previous residual connector:
Lₖ = Lₖ₋₁ + Rₖ

Rₖ ∈ N(0, 1)

Note that if Lₖ₋₁ has a non-zero variance then the variance of Lₖ will increase with k. This would normally not be a huge problem, however since we clip our activations to six the optimizer must continuously decrease the mean of Lₖ to maintain expressiveness of the network.
A solution to this is to instead interpolate between Lₖ₋₁ and Rₖ when computing the residual connector, i.e. Lₖ = α Lₖ₋₁ + (1 - α) Rₖ. A few interpretations for different value of α:

α = 0.5 - This is the current architecture without the exploding activations.
α ≠ 0.5 - This is what is called a highway network, a common value is α = 0.9.

We could also make α a trainable parameter.

When looking at the activations after introducing the α interpolation, the border problem seems to have been largely resolved. But an un-intended side-effect of making sure that Lₖ ∈ N(0, 1), is that the quantization resolution became worse, which has negative effects on the playing strength.
If we want to preserve 99.9% of all values, assuming the values are a normal distribution with a mean of 0 and a variance of 1, then we should clip the activations at 3.09023. This is a far cry from 6.0, and shows that we are effectively just wasting half of the quantized range.
This in-efficient use of the quantized range presumably also had negative effects before introducing α, since the initial parts of the architecture were not using the entire range, resulting in a low resolution during the initial parts of the inference.


Allow verbatim pragma

Issue #, if available: N/A
Description of changes:
Verbatim pragma no longer causes failure

interpreter handles verbatim case
remove default fall-through bug to improve the error message in case this happens again
update grammar

Testing done:
Unit testing, local notebook execution
Discovered the issue with:
from braket.circuits import Circuit
from braket.devices import LocalSimulator

prog = Circuit()
prog = prog.cnot(0, 1)
prog = prog.cnot(0, 1)
prog = prog.rx(0, 3.14/2)
prog = Circuit().add_verbatim_box(prog)

verbatim = sim.run(prog(theta=3.14/2), shots=100)

Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

It may make sense to add verbatim to "supported pragmas" in device capabilities now, but since it's a noop, it might be ok to just list it in neither supported or forbidden


Help

How to Connect MongoDB??

https://github.com/xHyroM/Uptimo/tree/mongodb and change values in .env

can admin more than 1?

You need edit code

How, Can u help?


babel + rlt langs like persian ;)

Add babel and lazytext for multi-language
Add dir for right-to-left language like Persian (Farsi)
Add free Persian font

@RaminNietzsche can you please update the branch?


The experimental results could not be reproduced

I wonder why the CIFAR100 result I reproduced was only 57%, but the experimental result of the paper was 75%. I haven't found out why.

Hi @JJJTF, thanks for your interest! Could you please be more specific on from which model that you cannot reproduce the results? And also your experiment settings, e.g. number of GPUs, hyperparameters like learning rate and batch size. If you follow the default hyperparameter settings in this repo, you should get the similar results.

my experiment settings is hvt-s-1.json file and cuda:0,1, others is default.

Hi @JJJTF, I just trained this model on 2 V100 GPUs.  My python environment has PyTorch 1.7.1 and CUDA 10.1. Without modifying any code in this repo, I got the final accuracy of 73.68% by using the following commands for training,
python -m torch.distributed.launch --nproc_per_node=2 --use_env main.py --config config/hvt-s-1.json --data-set CIFAR --data-path [path/to/cifar100]

Note that your final result could be slightly different based on your environment, but ideally it should not be significantly lower, i.e. 57% is not normal. It would be better if you can double-check your code.
Here is the training log for your reference: all_logs.txt

Thank you very much for your timely answer to each question. I will run again according to your all_logs.txt parameter.


Test against three last doctrine common versions

2.6 is 5.5+. what do we do?

@docteurklein you mean with the build or with 5.4 support drop?

@akovalyov I meant with 5.4.

@docteurklein PHP 5.3 has reached its EOL 3 months ago. So, I suggest to tag the last minor release for 5.4 and to add 5.5 as a minimum.

Totally. we'll just tag a last release for the lost people still using 5.3/5.4 (like me :))
next release is a minor change with php version drop!

@docteurklein so, is it time now for this PR?


Signature and Certificate Files Overwritten During signing when recursive option chosen

When specifying --output-signature or --output-certificate as part of cosign sign, contents are overwritten when specifying -r/--recursive for signing mutiarch images
Separate files would need to be created for each image being signed

Putting some thoughts on how this might want to be implemented.

For non recursive signatures, use parameters provided by the user
For recursive signatures

manifest list image uses the parameters provided by the user
Each resulting image appends the architecture and platform as follows
`<user_provided_input>--

thoughts?

That sounds good to me!


fix(integration-test): Handle missing revision in git url params

Fixes
https://issues.redhat.com/browse/RHTAPBUGS-884

Description

avoid showing params where value is not defined
use master as default branch when revision param is not provided (GH automatically redirects to a valid default branch in this case)

Type of change

[ ] Feature
[x] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?
Create an integration test without specifying git revision.

Browser conformance:

[ ] Chrome
[x] Firefox
[ ] Safari
[ ] Edge

/lgtm
/approve


Updating events

whoops this was to the wrong place

Woaaaah! Awesome.

@mileszim are you going to reopen this PR?

@binhums I have a lot of improvements/updates for this coming your way over the next week including this, so I'll open a PR when that's ready.

@mileszim sweet, when you do make sure you check out the comment on this issue
https://github.com/binhums/ember-cli-mapbox/issues/24#issuecomment-178197841
I think it would be good to start sending up the map / marker instance when we trigger the action.

@mileszim any updates here? If you want to pair up on it I'd be happy to.


Persistent shock model is now general income process model

This PR addresses issue #124 concerning ConsPersistentShockModel.py.  It replaces that module with ConsGenIncProcessModel.py, and extends the changes to ConsMedModel.py (the original module is preserved in ConsMedModelOLD).  Both the "explicit permanent income" and "persistent shock" models now use the exact same solver, with an input called pLvlNextFunc that gives next period's expected persistent income (or productivity) as a function of this period's.  In ExplicitPermInc, that's just a linear function (constant permanent income growth factor); in PersistentShock, it's an AR1-style function (which now has its own class).  This change adds the capability to have oddball pLvlNextFuncs, with the most obvious use being an approximation to the Social Security benefit structure.
These models still can't handle cycles>1 for the same reason as before: it's not clear how to construct the pLvlGrid for a particular period when it should have different values on each cycle.  It would also create a problem in the persistent shock model, as the AR1 would want to regress back to a different mean level for each cycle.  To get around this, users will have to explicitly list out the repeating cycle of periods in the inputs they pass to the constructor (which is trivial in Python) and use cycles=1.  Long run permanent income growth also won't work in the persistent shock model with cycles=0.
I wrote in #124 that we should redo the representations of policy and value functions to use normalized levels, and convert when called.  I realized this won't work because of pLvl=0, which would make undefined cNrms (etc).
Before approving and merging to master, we should delete ConsMedModelOLD.py and ConsPersistentShockModel.py, and remove a few obsoleted lines from ConsumerParameters.py.  I'm leaving these in for now for testing and comparison purposes.

After discussing with CDC and making some additions, this PR should be ready to merge.

Right, $P_{0}$ is nonzero.  So $P_{t}$ will be nonzero so long as $P_{t-1}$ is nonzero.
I think @mnwhite was just trying to use the fact that we rule out $P_{0}=0$ as a way to illustrate clearly the structure of what we are doing.  Maybe it is obvious, but it helps make the obvious crystal clear.

Sort of. Let me try to unpack my original comment more.
In ConsGenIncProcessModel, the consumption function is a
LinearInterpOnInterp1D (actually a VariableLowerBoundFunc2D on that, but
let's stick to the important part). It's composed of a list of
pLvL-specific 1D interpolators over mLvl. At some point, I made a
comment-to-self to rewrite that as 1D interpolators on mNrm, and then have
an extra "conversion" step when it's evaluated at (mLvl,pLvl).
In the top post of this thread, I noted that this won't work, because the
pLvlGrid might include pLvl=0, either because there actually is some
way in some specification to end up with pLvl=0, or to have a proper
bounding cFunc for when pLvl approaches but does not reach 0, through a
terrible series of shocks. You can't "convert to normalized market
resources" when pLvl=0, so it can't work.
Random thought I had the other day: at some point I had a demo for
TractableBufferStock that shows it being solved "the slow way" using
ConsMarkovModel vs the "the fast" way. We can actually use ConsIndShock and
have the "zero" permanent income shock be arbitrarily close to 0, but still
positive.
On Sat, Feb 24, 2024, 10:18 PM Christopher Llorracc Carroll <
@.***> wrote:

Right, $P_{0}$ is nonzero. So $P_{t}$ will be nonzero so long as $P_{t-1}$
is nonzero.
I think @mnwhite https://github.com/mnwhite was just trying to use the
fact that we rule out $P_{0}=0$ as a way to illustrate clearly the
structure of what we are doing. Maybe it is obvious, but it helps make the
obvious crystal clear.
—
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/pull/128#issuecomment-1962798640, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFPJGPF74WK7RVQXZDDYVKUQDAVCNFSM4DXWC5AKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJWGI3TSOBWGQYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mnwhite Thanks for the explanation. One additional follow up: the model nests the unit root case, which is solved in ConsIndShock. In that special case, even though we can normalize, implicitly, is pLvl=0 or close to zero possible? And if so, why isn't it a problem in the unit root case?

In ConsIndShock, pLvl=0 would be a problem, as it would make mNrm infinite
and thus break the code. For ExplicitPermInc (the unit root example for
ConsGenIncProcess that solves the ConsIndShockModel without normalization),
pLvl=0 is allowed to be in the grid, and it's allowed to actually happen
during both solution and simulation. No normalization is ever performed (as
far as I know), so there will never be a division by zero.
It might be that there's a very small adjustment to the pLvlNextFunc that
needs to happen to account for pLvl=0 (e.g. if it's taking log(pLvl) as
part of its math), but that's like 2 lines.
On Mon, Feb 26, 2024 at 3:31 PM nomadj1s @.***> wrote:

@mnwhite https://github.com/mnwhite Thanks for the explanation. One
additional follow up: the model nests the unit root case, which is solved
in ConsIndShock. In that special case, even though we can normalize,
implicitly, is pLvl=0 or close to zero possible? And if so, why isn't it a
problem in the unit root case?
—
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/pull/128#issuecomment-1965214270, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFP6VXGLHKGLREYB6YDYVTWKZAVCNFSM4DXWC5AKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJWGUZDCNBSG4YA
.
You are receiving this because you were mentioned.Message ID:
@.***>


A single failed component may stop further deployment

Currently, if a component fails to deploy, the instance deployment is considered failed. Although whether we should continue to deploy is debatable (especially when there aren't dependencies constrains stopping a component to be deployed), this does lead to a bug, where some components (that are ordered after the failed component) are not removed when the instance is removed.

Assign to @RemindD to evaluate.


Added Opensource Tailwind Components

https://github.com/besoeasy/tailwind-components

I feel like it's too new to be featured on the list. It was just recently created, and both the website and the readme are quite empty. Feel free to PR again when the project has grown and when its presentation is friendlier.


Incorrect behavior when aborting download in v0.8

Problem
libcurl provides a WRITEFUNCTION option to process response chunks. Its behavior is to abort the download if returned integer is not equal to the length of passed chunk.

Your callback should return the number of bytes actually taken care of. If that amount differs from the amount passed to your callback function, it signals an error condition to the library. This causes the transfer to get aborted and the libcurl function used returns CURLE_WRITE_ERROR.

It looks like instead of E_WRITE_ERROR, latest libcurl-impersonate is returning E_RECV_ERROR which breaks the abort functionality and makes it impossible to differentiate between server side receive errors/timeouts and on-purpose aborts.
Test Case
Following is the minimal test case with pycurl that can be used to reproduce this:
import pycurl

print(pycurl.version)

url = 'https://bit.ly/4874LxR'

def abort_write(_):
    '''
    Abort writing response body.
    '''
    return -1

curl = pycurl.Curl()
curl.setopt(pycurl.URL, url.encode('utf-8'))
curl.setopt(pycurl.FOLLOWLOCATION, 1)
curl.setopt(pycurl.WRITEFUNCTION, abort_write)
curl.perform()
curl.close()

Results
Use LD_PRELOAD to load libcurl-impersonate 0.8.0 and run the test. Error 56 (E_RECV_ERROR) will return:
$ LD_PRELOAD=/local/lib/libcurl-0.8.0.so CURL_IMPERSONATE=chrome124 python pycurl_test.py

PycURL/7.45.3 libcurl/8.7.0-DEV BoringSSL zlib/1.3 brotli/1.1.0 zstd/1.5.6 nghttp2/1.63.0

Traceback (most recent call last):
  File "/home/ubuntu/pycurl_test.py", line 22, in <module>
    curl.perform()

pycurl.error: (56, 'Failure writing output to destination, passed 1369 returned -1')

I tried the same test case with libcurl-impersonate 0.7.0b1 built with older libcurl v8.5 and it passed:
$ LD_PRELOAD=/local/lib/libcurl-0.7.0b1.so CURL_IMPERSONATE=chrome124 python pycurl_test.py

PycURL/7.45.3 libcurl/8.5.0 BoringSSL zlib/1.3 brotli/1.0.9 zstd/1.5.6 nghttp2/1.56.0

Traceback (most recent call last):
  File "/home/ubuntu/pycurl_test.py", line 22, in <module>
    curl.perform()

pycurl.error: (23, 'Failure writing output to destination')

Error 23 (E_WRITE_ERROR) is the expected code, which allows client to handle on-purpose aborts and process the result. Something got broken in latest impersonation patch or maybe in libcurl v8.7.1 itself. Strangely though, version API returns 8.7.1 as 8.7.0-DEV implying that it is not stable.

Thanks for the detailed report. I'll verify the behavior later.
As for the version API, I noticed it a while ago. I did use the v8.7.1 tag from curl repository, you can take a look at the Makefiles, however, the compiled binary does not show this version. There might be something wrong with the build arguments or something like that.


Cached token expired within a day

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Incase of token cache between Webapp and Background console application service for the scenario mentioned in https://github.com/Azure-Samples/ms-identity-dotnet-advanced-token-cache/tree/master/1-Integrated-Cache/1-1-WebApp-BgWorker, the application allows to configure the expiration time of the token being cached in the database.
In the webapp application of startup.cs file, I changed the code below to store the token for at least 30 days.
               //Once expired, the cache entry is automatically deleted by Microsoft.Extensions.Caching.SqlServer library                 options.DefaultSlidingExpiration = TimeSpan.FromDays(30);
And in the database too, I used SQL server, it correctly added the expiration time of after a month as shown in the screenshot below:

However, after a couple of hours, this database entry got changed to

Any log messages given by the failure

No

Expected/desired behavior

Now the expiration time of the token was changed to 30 days, it should have cached in the DB for this time but it got expired within sometime.
Can't the token be cached/stored for 30 days?

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

Versions

Mention any other details that might be useful
The background application worked well for a day with the stored token but the next day when the background process executed it failed to retrieve the cached token. Table entries of MSALAccountActivities --> FailedToAcquireToken changed to True from False and Token Cache entry also changed to 1-day expiration from 30 days.

Thanks! We'll be in touch soon.

could you (or would you) be able to check if the offline_access scope is being used. The sample needs both the Refresh tokens (granted only of offline_access is sent as a scope) to work correctly

documentation did not mention anywhere to pass it but as per your recommendation now, I have passed the scope of offline_access and testing it now. I will share the results asap.

@kalyankrishna1 even after passing the scope of "offline_access", the issue remains the same. Are you able to replicate the scenario at your end?

Any update on this would be helpful.

These are the fresh debug logs, Is the issue reproduced at your end?
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] MSAL MSAL.NetCore with assembly version '<IP_ADDRESS>'. CorrelationId(20cc83ac-50eb-4065-8dc9-3a985c3f9164)
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] === AcquireTokenSilent Parameters ===
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] LoginHint provided: False
Info (True) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Account provided: BackgroundWorker.MsalAccount
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] ForceRefresh: False
Info (True) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164]
=== Request Data ===
Authority Provided? - True
Client Id - 37b71744-81ba-4762-b071-18da96bf008e
Scopes - Mail.Read User.Read
Redirect Uri - https://replyUrlNotSet
Extra Query Params Keys (space separated) -
ClaimsAndClientCapabilities -
Authority - https://login.microsoftonline.com/4a95f16f-35ba-4a52-9cb3-7f300cdc0c60/
ApiId - AcquireTokenSilent
IsConfidentialClient - True
SendX5C - False
LoginHint -
IsBrokerConfigured - False
HomeAccountId -

Info (True) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] === Token Acquisition (SilentRequest) started:
        Authority: https://login.microsoftonline.com/4a95f16f-35ba-4a52-9cb3-7f300cdc0c60/
        Scope: Mail.Read User.Read
        ClientId: 37b71744-81ba-4762-b071-18da96bf008e

Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Attempting to acquire token using using local cache...
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Looking up access token in the cache.
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Filtering by tenant id item count before 0 after 0
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Filtering by home account id item count before 0 after 0
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Filtering by token type item count before 0 after 0
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] No matching entry found for user or assertion
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [Instance Discovery] Tried to use network cache provider for login.microsoftonline.com. Success? False
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [Instance Discovery] Tried to use known metadata provider for login.microsoftonline.com. Success? True
Warning (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] No app metadata found. Returning unknown
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [FOCI] App is part of the family or unknown, looking for FRT
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [Instance Discovery] Tried to use network cache provider for login.microsoftonline.com. Success? False
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:12 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [Instance Discovery] Tried to use known metadata provider for login.microsoftonline.com. Success? True
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Refresh token found in the cache? - False
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Checking ADAL cache for matching RT
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [FOCI] FRT found? False
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [Instance Discovery] Tried to use network cache provider for login.microsoftonline.com. Success? False
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] [Instance Discovery] Tried to use known metadata provider for login.microsoftonline.com. Success? True
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Refresh token found in the cache? - False
Info (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Checking ADAL cache for matching RT
Verbose (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] No Refresh Token was found in the cache
Warning (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Refreshing the RT failed. Is AAD down? False. Is there an AT in the cache that is usable? False
Warning (False) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:13 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] Failed to refresh the RT and cannot use existing AT (expired or missing).
Error (True) MSAL <IP_ADDRESS> MSAL.NetCore Microsoft Windows 10.0.18363 [05/18/2021 07:24:14 - 20cc83ac-50eb-4065-8dc9-3a985c3f9164] MSAL.NetCore.<IP_ADDRESS>.MsalUiRequiredException:
        ErrorCode: no_tokens_found
Microsoft.Identity.Client.MsalUiRequiredException: No Refresh Token found in the cache
   at Microsoft.Identity.Client.Internal.Requests.Silent.SilentClientAuthStretegy.FindRefreshTokenOrFailAsync()
   at Microsoft.Identity.Client.Internal.Requests.Silent.SilentClientAuthStretegy.RefreshRtOrFailAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.Silent.SilentClientAuthStretegy.ExecuteAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.Silent.SilentClientAuthStretegy.ExecuteAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.Silent.SilentRequest.ExecuteAsync(CancellationToken cancellationToken)   at Microsoft.Identity.Client.Internal.Requests.Silent.SilentRequest.ExecuteAsync(CancellationToken cancellationToken)   at Microsoft.Identity.Client.Internal.Requests.RequestBase.RunAsync(CancellationToken cancellationToken)
        StatusCode: 0
        ResponseBody:
        Headers:
Could not acquire token for account<EMAIL_ADDRESS>Error: No Refresh Token found in the cache
  <------------------------>

Hi, I have replicated the scenario by changing to TimeSpan.FromDays(30); and I am not able to reproduce the issue. It's working as expected and no change in expiration time after 2 hours in sql db is observed. Can you please let us know if you have followed the sample exactly as is or if you have made some other customizations as well? @architect-tarun-narang

It worked fine for me until two hours or so, till the time access token is not expired. However, in my case after 8-10 hours, I started facing this issue for which I shared the debug logs as well. Request you to please give it a try after 10 hours.
In addition to this, do the logs provided above confirms any issue? Thanks

I just tried after almost 24 hours and it still works. Can you please confirm if you have used the sample as is? Did you use the automated scripts to create the app reg and configurations? If not can you please do it that way and see if working fine?

I did not use the automated script to create the app and give it a try as per your suggestions.
Yes, we used the same sample program, even this issue was raised with the Microsoft team and they were able to reproduce this problem at their end.
By looking at the logs above, do you see any problem, why the refresh token was not found in the cache? In the meanwhile, I will try this with an automated script. Thanks

@architect-tarun-narang Please let us know which Microsoft team was able to reproduce this issue. Can you please loop me in on the thread?

Sure, I will drop an email to the Microsoft team requesting them to loop you in. I don't have your email address.

@architect-tarun-narang did you try running the sample with the automated scripts? Is it still failing?

@architect-tarun-narang  Hi, after more than 24 hours the issue has now happened in my setup. Thank you for your patience with this. We are looking into this on priority

@architect-tarun-narang can you please add the following line to the background worker's program.cs file (line 45)  also?
options.DefaultSlidingExpiration = TimeSpan.FromDays(30);
Basically the issue happened because you updated the time from 2 hours to 30 days only in the webapp and background worked used the default value of 20 mins for the DefaultSlidingExpiration property hence the refresh token became shortlived and then removed from the db post 20 mins leading to the refresh token not found error.

@architect-tarun-narang  did it help?

Thanks @jeevanbalanmanoj , it worked, the issue is resolved now.

Fix deployed


Fix redirect_uri issue with tornado reversed url

When reversing URLs, tornado doesn't interpret the regex optional symbol '?'. This causes the redirect_uri to be https://example.com/complete/mybackend/? with the question mark appended. Some providers will simply append to this uri, causing URLs like https://example.com/complete/mybackend/??code=.... with two question marks. This makes the interpretation of the query string fail.
The provider in this case is django-oidc-provider. Arguably that library should be smarter in constructing the redirection, but removing the question mark from the uri solves these kind of issues.
Alternatively we could strip the question mark from the uri in the tornado strategy in here, but this seemed simpler.

Thanks!


panicked at invalid range 0..21 for a fixedbitset of size 12

Describe the bug
--- START
-- Failing SQL setup code:
CREATE TABLE supplier (     s_suppkey INTEGER,     s_name VARCHAR,     s_address VARCHAR,     s_nationkey INTEGER,     s_phone VARCHAR,     s_acctbal NUMERIC,     s_comment VARCHAR,     PRIMARY KEY (s_suppkey) ); CREATE TABLE part (     p_partkey INTEGER,     p_name VARCHAR,     p_mfgr VARCHAR,     p_brand VARCHAR,     p_type VARCHAR,     p_size INTEGER,     p_container VARCHAR,     p_retailprice NUMERIC,     p_comment VARCHAR,     PRIMARY KEY (p_partkey) ); CREATE TABLE partsupp (     ps_partkey INTEGER,     ps_suppkey INTEGER,     ps_availqty INTEGER,     ps_supplycost NUMERIC,     ps_comment VARCHAR,     PRIMARY KEY (ps_partkey, ps_suppkey) ); CREATE TABLE customer (     c_custkey INTEGER,     c_name VARCHAR,     c_address VARCHAR,     c_nationkey INTEGER,     c_phone VARCHAR,     c_acctbal NUMERIC,     c_mktsegment VARCHAR,     c_comment VARCHAR,     PRIMARY KEY (c_custkey) ); CREATE TABLE orders (     o_orderkey BIGINT,     o_custkey INTEGER,     o_orderstatus VARCHAR,     o_totalprice NUMERIC,     o_orderdate DATE,     o_orderpriority VARCHAR,     o_clerk VARCHAR,     o_shippriority INTEGER,     o_comment VARCHAR,     PRIMARY KEY (o_orderkey) ); CREATE TABLE lineitem (     l_orderkey BIGINT,     l_partkey INTEGER,     l_suppkey INTEGER,     l_linenumber INTEGER,     l_quantity NUMERIC,     l_extendedprice NUMERIC,     l_discount NUMERIC,     l_tax NUMERIC,     l_returnflag VARCHAR,     l_linestatus VARCHAR,     l_shipdate DATE,     l_commitdate DATE,     l_receiptdate DATE,     l_shipinstruct VARCHAR,     l_shipmode VARCHAR,     l_comment VARCHAR,     PRIMARY KEY (l_orderkey, l_linenumber) ); CREATE TABLE nation (     n_nationkey INTEGER,     n_name VARCHAR,     n_regionkey INTEGER,     n_comment VARCHAR,     PRIMARY KEY (n_nationkey) ); CREATE TABLE region (     r_regionkey INTEGER,     r_name VARCHAR,     r_comment VARCHAR,     PRIMARY KEY (r_regionkey) ); CREATE TABLE person (     id BIGINT,     name VARCHAR,     email_address VARCHAR,     credit_card VARCHAR,     city VARCHAR,     state VARCHAR,     date_time TIMESTAMP,     extra VARCHAR,     PRIMARY KEY (id) ); CREATE TABLE auction (     id BIGINT,     item_name VARCHAR,     description VARCHAR,     initial_bid BIGINT,     reserve BIGINT,     date_time TIMESTAMP,     expires TIMESTAMP,     seller BIGINT,     category BIGINT,     extra VARCHAR,     PRIMARY KEY (id) ); CREATE TABLE bid (     auction BIGINT,     bidder BIGINT,     price BIGINT,     channel VARCHAR,     url VARCHAR,     date_time TIMESTAMP,     extra VARCHAR ); CREATE TABLE alltypes1 (     c1 boolean,     c2 smallint,     c3 integer,     c4 bigint,     c5 real,     c6 double precision,     c7 numeric,     c8 date,     c9 varchar,     c10 time without time zone,     c11 timestamp without time zone,     -- TODO(Noel): Many timestamptz expressions are unsupported in RW, leave this out for now.     -- c12 timestamp with time zone,     c13 interval,     c14 struct < a integer >,     c15 integer [],     c16 varchar [] ); CREATE TABLE alltypes2 (     c1 boolean,     c2 smallint,     c3 integer,     c4 bigint,     c5 real,     c6 double precision,     c7 numeric,     c8 date,     c9 varchar,     c10 time without time zone,     c11 timestamp without time zone,     -- TODO(Noel): Many timestamptz expressions are unsupported in RW, leave this out for now.     -- c12 timestamp with time zone,     c13 interval,     c14 struct < a integer >,     c15 integer [],     c16 varchar [] );CREATE MATERIALIZED VIEW m0 AS SELECT tumble_0.c1 AS col_0, hop_2.c13 AS col_1, DATE '2023-07-03' AS col_2 FROM (tumble(alltypes1, alltypes1.c11, INTERVAL '6') AS tumble_0 JOIN hop(alltypes1, alltypes1.c11, INTERVAL '153575', INTERVAL '5989425') AS hop_1 ON tumble_0.c5 = hop_1.c5 AND true) JOIN hop(alltypes1, alltypes1.c11, INTERVAL '261201', INTERVAL '20373678') AS hop_2 ON hop_1.c11 = hop_2.c11 AND hop_2.c1 GROUP BY tumble_0.c14, hop_2.c13, tumble_0.c15, tumble_0.c1, hop_1.c13, hop_2.c15, tumble_0.c11, hop_2.c10, hop_1.c3, hop_2.c2, hop_2.c14, hop_2.c5, tumble_0.c6, tumble_0.c9, hop_1.c7, hop_2.c9;CREATE MATERIALIZED VIEW m1 AS SELECT CAST(true AS INT) AS col_0 FROM lineitem AS t_0 FULL JOIN orders AS t_1 ON t_0.l_comment = t_1.o_orderpriority AND true AND t_0.l_linenumber = t_1.o_custkey AND t_0.l_linenumber = t_1.o_shippriority AND t_0.l_linestatus = t_1.o_clerk AND t_0.l_shipmode = t_1.o_orderpriority AND t_0.l_returnflag = t_1.o_orderpriority AND t_0.l_shipmode = t_1.o_clerk AND t_0.l_shipdate = t_1.o_orderdate AND t_0.l_shipinstruct = t_1.o_orderstatus AND t_0.l_suppkey = t_1.o_custkey AND t_0.l_linestatus = t_1.o_comment AND t_0.l_shipinstruct = t_1.o_comment AND t_0.l_linestatus = t_1.o_orderpriority AND t_0.l_commitdate = t_1.o_orderdate AND t_0.l_comment = t_1.o_comment AND t_0.l_comment = t_1.o_clerk AND t_0.l_comment = t_1.o_orderstatus AND t_0.l_partkey = t_1.o_shippriority AND t_0.l_returnflag = t_1.o_clerk AND t_0.l_discount = t_1.o_totalprice AND t_0.l_receiptdate = t_1.o_orderdate AND t_0.l_shipmode = t_1.o_comment AND t_0.l_shipmode = t_1.o_orderstatus AND t_0.l_quantity = t_1.o_totalprice AND t_0.l_linestatus = t_1.o_orderstatus AND t_0.l_tax = t_1.o_totalprice AND t_0.l_partkey = t_1.o_custkey AND t_0.l_shipinstruct = t_1.o_orderpriority AND t_0.l_orderkey = t_1.o_orderkey AND t_0.l_extendedprice = t_1.o_totalprice GROUP BY t_0.l_tax, t_0.l_shipdate, t_0.l_extendedprice, t_0.l_orderkey, t_1.o_custkey, t_1.o_orderpriority, t_0.l_shipinstruct, t_0.l_partkey, t_0.l_shipmode, t_0.l_linenumber, t_0.l_discount HAVING true;CREATE MATERIALIZED VIEW m2 AS SELECT (t_4.c8 + (INT '224625786')) AS col_0, t_4.c7 AS col_1, sum((FLOAT '299')) FILTER(WHERE true) AS col_2 FROM ((WITH with_0 AS (WITH with_1 AS (SELECT t_2.ps_comment AS col_0, string_agg(t_2.ps_comment, ('W0IpillyUK')) AS col_1 FROM partsupp AS t_2 WHERE true GROUP BY t_2.ps_availqty, t_2.ps_comment HAVING true) SELECT (REAL '968') AS col_0, (INTERVAL '3600') AS col_1 FROM with_1) SELECT (BIGINT '808') AS col_0, (BIGINT '130') AS col_1 FROM with_0 WHERE false) AS sq_3 RIGHT JOIN alltypes2 AS t_4 ON sq_3.col_1 = t_4.c4 AND true) LEFT JOIN nation AS t_5 ON t_4.c3 = t_5.n_regionkey GROUP BY t_4.c8, t_4.c7, t_4.c13, t_4.c4, t_5.n_name, t_4.c6, t_4.c10 HAVING false;CREATE MATERIALIZED VIEW m3 AS WITH with_0 AS (SELECT t_1.s_phone AS col_0, tumble_2.c4 AS col_1 FROM supplier AS t_1 RIGHT JOIN tumble(alltypes1, alltypes1.c11, INTERVAL '6') AS tumble_2 ON t_1.s_name = tumble_2.c9 AND true AND t_1.s_address = tumble_2.c9 AND t_1.s_acctbal = tumble_2.c7 WHERE (tumble_2.c6 < tumble_2.c6) GROUP BY t_1.s_phone, tumble_2.c9, tumble_2.c4, tumble_2.c3, t_1.s_name, t_1.s_address) SELECT (167) AS col_0, false AS col_1, (INT '106') AS col_2, DATE '2023-06-26' AS col_3 FROM with_0 WHERE ((BIGINT '173') <= ((BIGINT '803') - (INT '1')));CREATE MATERIALIZED VIEW m4 AS SELECT hop_0.c8 AS col_0, hop_0.c2 AS col_1 FROM hop(alltypes1, alltypes1.c11, INTERVAL '604800', INTERVAL '19958400') AS hop_0 GROUP BY hop_0.c8, hop_0.c7, hop_0.c16, hop_0.c2, hop_0.c11;CREATE MATERIALIZED VIEW m5 AS WITH with_0 AS (SELECT t_2.c8 AS col_0, (BIGINT '0') AS col_1, (SMALLINT '82') AS col_2 FROM m3 AS t_1 FULL JOIN alltypes2 AS t_2 ON t_1.col_1 = t_2.c1 AND true WHERE t_1.col_1 GROUP BY t_2.c13, t_2.c11, t_2.c8) SELECT DATE '2023-07-03' AS col_0, (50) AS col_1 FROM with_0 WHERE false;CREATE MATERIALIZED VIEW m6 AS SELECT tumble_0.c9 AS col_0 FROM tumble(alltypes2, alltypes2.c11, INTERVAL '22') AS tumble_0 GROUP BY tumble_0.c9;CREATE MATERIALIZED VIEW m7 AS SELECT t_0.col_2 AS col_0 FROM m3 AS t_0 RIGHT JOIN m4 AS t_1 ON t_0.col_3 = t_1.col_0 AND t_0.col_1 WHERE t_0.col_1 GROUP BY t_0.col_0, t_0.col_3, t_0.col_2 HAVING true;CREATE MATERIALIZED VIEW m8 AS SELECT tumble_0.c2 AS col_0 FROM tumble(alltypes2, alltypes2.c11, INTERVAL '94') AS tumble_0 FULL JOIN customer AS t_1 ON tumble_0.c3 = t_1.c_nationkey AND true GROUP BY tumble_0.c2 HAVING false;CREATE MATERIALIZED VIEW m9 AS SELECT t_0.bidder AS col_0, t_0.bidder AS col_1, ARRAY[(BIGINT '68'), (BIGINT '9223372036854775807')] AS col_2, t_0.bidder AS col_3 FROM bid AS t_0 GROUP BY t_0.bidder;CREATE MATERIALIZED VIEW m10 AS SELECT (FLOAT '0') AS col_0, (DATE '2023-06-26') AS col_1 FROM m4 AS t_0 GROUP BY t_0.col_0 HAVING true;CREATE MATERIALIZED VIEW m11 AS WITH with_0 AS (SELECT TIMESTAMP '2023-07-03 01:14:21' AS col_0, '9ycQJ34Es1' AS col_1, tumble_1.item_name AS col_2, (FLOAT '518') AS col_3 FROM tumble(auction, auction.expires, INTERVAL '33') AS tumble_1 JOIN auction AS t_2 ON tumble_1.expires = t_2.date_time AND true GROUP BY t_2.id, tumble_1.extra, t_2.description, tumble_1.category, t_2.expires, t_2.item_name, tumble_1.item_name) SELECT (FLOAT '344') AS col_0, (REAL '550') AS col_1, (REAL '625') AS col_2 FROM with_0;CREATE MATERIALIZED VIEW m12 AS SELECT sq_3.col_2 AS col_0, CAST(NULL AS STRUCT<a CHARACTER VARYING, b CHARACTER VARYING>) AS col_1 FROM (SELECT t_2.r_name AS col_0, t_2.r_comment AS col_1, t_2.r_name AS col_2, (INTERVAL '-38') AS col_3 FROM region AS t_2 WHERE true GROUP BY t_2.r_comment, t_2.r_name HAVING false) AS sq_3 JOIN partsupp AS t_4 ON sq_3.col_1 = t_4.ps_comment AND true WHERE false GROUP BY sq_3.col_2;CREATE MATERIALIZED VIEW m13 AS SELECT t_2.ps_comment AS col_0 FROM (supplier AS t_0 FULL JOIN m3 AS t_1 ON t_0.s_suppkey = t_1.col_2 AND true) JOIN partsupp AS t_2 ON t_1.col_0 = t_2.ps_supplycost AND true AND t_0.s_nationkey = t_2.ps_partkey GROUP BY t_1.col_3, t_0.s_name, t_1.col_0, t_2.ps_comment HAVING max(true) FILTER(WHERE true);CREATE MATERIALIZED VIEW m14 AS SELECT 'nHeW0VinSR' AS col_0, true AS col_1, sq_5.col_2 AS col_2, DATE '2023-07-03' AS col_3 FROM (SELECT t_4.col_0 AS col_0, (INTERVAL '-1') AS col_1, t_4.col_0 AS col_2, 'bVsJQcdHQW' AS col_3 FROM m13 AS t_4 WHERE true GROUP BY t_4.col_0 HAVING true) AS sq_5 LEFT JOIN tumble(bid, bid.date_time, INTERVAL '12') AS tumble_6 ON sq_5.col_2 = tumble_6.extra AND (true) WHERE true GROUP BY tumble_6.url, tumble_6.price, sq_5.col_2, sq_5.col_0, sq_5.col_1 HAVING false;CREATE MATERIALIZED VIEW m15 AS WITH with_0 AS (SELECT tumble_1.id AS col_0 FROM tumble(auction, auction.date_time, INTERVAL '87') AS tumble_1 FULL JOIN tumble(bid, bid.date_time, INTERVAL '79') AS tumble_2 ON tumble_1.id = tumble_2.price AND true WHERE true GROUP BY tumble_2.extra, tumble_1.reserve, tumble_2.date_time, tumble_1.description, tumble_2.url, tumble_1.initial_bid, tumble_2.auction, tumble_1.id) SELECT CAST(NULL AS STRUCT<a BOOLEAN, b INTERVAL>) AS col_0 FROM with_0 WHERE false;CREATE MATERIALIZED VIEW m16 AS SELECT DATE '2023-07-03' AS col_0, max(t_1.date_time) AS col_1 FROM bid AS t_0 FULL JOIN person AS t_1 ON t_0.bidder = t_1.id AND true GROUP BY t_0.extra, t_1.city, t_0.price, t_1.date_time HAVING false;

-- Failing SQL query:
CREATE MATERIALIZED VIEW m17 AS SELECT tumble_0.initial_bid AS col_0 FROM tumble(auction, auction.expires, INTERVAL '72') AS tumble_0 JOIN alltypes1 AS t_1 ON tumble_0.id = t_1.c4 AND true WHERE EXISTS (SELECT ARRAY[(INT '184')] AS col_0 FROM (SELECT tumble_7.col_0 AS col_0 FROM (m10 AS t_6 LEFT JOIN tumble(m16, m16.col_1, INTERVAL '66') AS tumble_7 ON t_6.col_1 = tumble_7.col_0) LEFT JOIN tumble(m16, m16.col_1, INTERVAL '48') AS tumble_8 ON tumble_7.col_0 = tumble_8.col_0 AND true GROUP BY t_6.col_1, tumble_7.col_0) AS sq_9 WHERE t_1.c1 GROUP BY t_1.c15, t_1.c16, t_1.c8, t_1.c2, tumble_0.reserve, t_1.c14, tumble_0.initial_bid, t_1.c3, tumble_0.item_name) GROUP BY tumble_0.seller, tumble_0.initial_bid, tumble_0.description, t_1.c6;
---- END

thread 'main' panicked at 'invalid range 0..21 for a fixedbitset of size 12', /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fixedbitset-0.4.2/src/lib.rs:610:9 stack backtrace:    0: rust_begin_unwind              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/std/src/panicking.rs:593:5    1: core::panicking::panic_fmt              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/panicking.rs:67:14    2: fixedbitset::Masks::new              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fixedbitset-0.4.2/src/lib.rs:610:9    3: fixedbitset::FixedBitSet::set_range              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fixedbitset-0.4.2/src/lib.rs:320:30    4: risingwave_frontend::optimizer::rule::apply_join_transpose_rule::ApplyJoinTransposeRule::push_apply_both_side              at /risingwave/src/frontend/src/optimizer/rule/apply_join_transpose_rule.rs:469:17    5: <risingwave_frontend::optimizer::rule::apply_join_transpose_rule::ApplyJoinTransposeRule as risingwave_frontend::optimizer::rule::Rule>::apply              at /risingwave/src/frontend/src/optimizer/rule/apply_join_transpose_rule.rs:159:13    6: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_node              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:53:36    7: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:76:24    8: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29    9: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   10: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   11: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   12: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:26:32   13: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   14: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   15: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   16: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   17: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   18: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   19: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29   20: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   21: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   22: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   23: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:26:32   24: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   25: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   26: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   27: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   28: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   29: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   30: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29   31: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   32: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   33: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   34: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:26:32   35: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   36: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   37: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   38: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   39: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   40: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   41: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29   42: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   43: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   44: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   45: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:26:32   46: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   47: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   48: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   49: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   50: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   51: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   52: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29   53: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   54: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   55: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   56: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:26:32   57: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   58: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   59: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   60: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   61: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   62: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   63: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29   64: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   65: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   66: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   67: alloc::vec::Vec<T,A>::extend_desugared              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2811:35   68: <alloc::vec::Vec<T,A> as alloc::vec::spec_extend::SpecExtend<T,I>>::spec_extend              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_extend.rs:17:9   69: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:43:9   70: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   71: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   72: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   73: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   74: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   75: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   76: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29   77: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   78: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   79: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   80: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:26:32   81: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   82: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   83: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   84: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   85: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   86: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   87: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs::{{closure}}              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:68:29   88: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/ops/function.rs:305:13   89: core::option::Option<T>::map              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/option.rs:1075:29   90: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/adapters/map.rs:103:26   91: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter_nested.rs:26:32   92: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/spec_from_iter.rs:33:9   93: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/alloc/src/vec/mod.rs:2711:9   94: core::iter::traits::iterator::Iterator::collect              at /rustc/f0411ffcebcd7f75ac02ed45feb53ffd07b75398/library/core/src/iter/traits/iterator.rs:1895:9   95: itertools::Itertools::collect_vec              at /risingwave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/itertools-0.10.5/src/lib.rs:1985:9   96: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize_inputs              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:65:22   97: risingwave_frontend::optimizer::heuristic_optimizer::HeuristicOptimizer::optimize              at /risingwave/src/frontend/src/optimizer/heuristic_optimizer.rs:77:17   98: risingwave_frontend::optimizer::logical_optimization::<impl risingwave_frontend::optimizer::plan_node::PlanRef>::optimize_by_rules_until_fix_point              at /risingwave/src/frontend/src/optimizer/logical_optimization.rs:64:27   99: risingwave_frontend::optimizer::logical_optimization::LogicalOptimizer::subquery_unnesting              at /risingwave/src/frontend/src/optimizer/logical_optimization.rs:373:16

https://buildkite.com/risingwavelabs/pull-request/builds/26608#0189194a-412e-4895-b54f-74f1f13e0055
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

looks same as #10662 and should have been fixed by #10716


bug：start failed under windows environment

Description
While i start pareto project under windows environment  and access http://localhost:4000/ the app broken.
Why the error
I have checked the code. I found the path writing to the file will be like,
D:\test

Yes, nodejs have rightly parsed the path 'D:\test'  when output it to the console or file. But the comiler read path from files will be  broken. Because the slash will escape the character 't'. The \t will be explained to 'tab'.
Solution
i have tried fixed it by writing a function to transform the path with double '\\' under window environment.
const os = require("os");
/**
 * Transform the OS path separator in the content based on the platform, while writing to files.
 * in windows the path should be replaced with \\ in files, for example, "D:\\test"
 *
 * @param {string} content - The content with OS path separators.
 * @return {string} Transformed content with updated path separators.
 */
function transformSepOfPath(content) {
  switch (os.platform()) {
    case "win32":
      return content.replace(/\\/g, "\\\\");
    default:
      return content;
  }
}

module.exports = {
  transformSepOfPath,
};

Others questions

I wonder  how you develope or test the framework. What I do is just replace the @pareto/core: "latest" to @pareto/core:"workspace:*" in projects of examples.

pnpm  --filter="./pacakges/core" run dev.  # to generate dist files.
pnpm install  # to install the dependencies
pnpm  --filter="./examples/tailwind" run dev

I wonder why you develope in mix in js and ts. why not develope fully in typescript?

fix: star app failed while in windows env #6

I apologize for the late response. Thank you for the changes related to Windows. Regarding the first question, if I were to publish the code in 'examples' as a template, I would have to use "@paretojs/core": "latest", because in my pnpm monorepo, 'latest' and 'workspace:*' have the same effect.

Secondly, why mix js and ts? Undoubtedly I prefer to use ts, initially I used js for the development of the bin program because many of the initial examples of rspack used js. I will migrate to ts later if possible

I'm currently working on adding i18n examples. Once this is complete, I plan to adjust the tooling to include typescript, eslint, prettier, and commitlint.

feel free to feedback!

I apologize for the late response. Thank you for the changes related to Windows. Regarding the first question, if I were to publish the code in 'examples' as a template, I would have to use "@paretojs/core": "latest", because in my pnpm monorepo, 'latest' and 'workspace:*' have the same effect.

I restored "workspace:*" to "latest",  deleted node_modules and pnpm install again. It worked!

feel free to feedback!

Thanks for your reply! I like your project pareto. It' s so coooool~


Couldn't find package "react-component-scroll" on the "npm" registry

Can' t try this package, not found on npm registry.

Read.md need update. change npm install react-component-scrollload


Improve to_schema in PandasUtils

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.06 :warning:

Comparison is base (40db808) 100.00% compared to head (1f9f9e5) 99.94%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##            master     #101      +/-   ##
===========================================
- Coverage   100.00%   99.94%   -0.06%
===========================================
  Files           23       23
  Lines         1878     1878
===========================================
- Hits          1878     1877       -1
- Misses           0        1       +1

Impacted Files
Coverage Δ

triad/utils/pandas_like.py
99.09% <100.00%> (-0.91%)
:arrow_down:

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

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


Make core dumps location configurable and default to /var/contiv/dumps

Coverage decreased (-0.07%) to 77.172% when pulling d29aebf87956343247b5940a293948cb58fa9836 on rastislavszabo:master into 1e891c079a830a99fa8db364dcb0b0961d5bf261 on contiv:master.


What's the source code licence terms?

Hi,
there's no license terms in your whole source code.
example, what I'm saying is MIT or Apache or GPL or LGPL or ...
Or, Your company internal license term.
It may be freely studying use now.
Source code has opened but, Licenses are still live.
So you can describe exact source code license terms in your souce code.
Good study materials.
thanks.

The license is right there, in the source code.  Take a look.

@rmtew  where's exact license terms? there's only source code owner's term only.
/*

Description:

History<EMAIL_ADDRESS>2016/04/19, create

*/
So, If some one , some company use this source , then he will claim?
or freely modify of this code then author no concern?
that is not clear.

Look in the top level! There's a file called LICENSE.
On Thu, Oct 5, 2017 at 4:41 PM, Trustfarm-heart<EMAIL_ADDRESS>wrote:

@rmtew https://github.com/rmtew where's exact license terms? there's
only source code owner's term only.
/*

Description:

History<EMAIL_ADDRESS>2016/04/19, create
*/
So, If some one , some company use this source , then he will claim?
or freely modify of this code then author no concern?
that is not clear.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/viabtc/viabtc_exchange_server/issues/14#issuecomment-334350376,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAjZn3_mkK8zvNaBd2bykHmL-gJCJHzks5spE_ZgaJpZM4PucMM
.

@rmtew Great!.
It is sad story to you closing the ViaBTC, But, Open your technology is great works.
Good Luck!

Maybe look a bit harder there too :-)  Repository owner is @haipome, I have
nothing to do with Viabtc.
On Thu, Oct 5, 2017 at 5:01 PM, Trustfarm-heart<EMAIL_ADDRESS>wrote:

@rmtew https://github.com/rmtew Great!.
It is sad story to you closing the ViaBTC, But, Open your technology is
great works.
Good Luck!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/viabtc/viabtc_exchange_server/issues/14#issuecomment-334352588,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAjZhG7PmClNWyqHBpZ2Cok-1CcIUGzks5spFSUgaJpZM4PucMM
.

@rmtew  It's not important thing I think. because source code and this repo's owner is @haipome , very clear.
You instruct me to where's licence term file. your instruction helps I finding the term file easily and in a short time. that's your thanks.
And Cheering the technology Contribution to owner. it is also very clear, even though I've wrote another thread.
Anyway thanks and good luck to all.


No Reports for Nested Suites

I just upgraded to 3.0.0 and I am no longer seeing the report information for nested suites.  I ran ASCIISuite taken from http://doc.scalatest.org/3.0.0/#org.scalatest.Suite and here is the result:
> test-only *.ASCIISuite
[info] Run completed in 767 milliseconds.
[info] Total number of tests run: 6
[info] Suites: completed 4, aborted 0
[info] Tests: succeeded 6, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.

Version 2.2.6 has the expected result:
> test-only *.ASCIISuite
[info] ASuite:
[info] - A should have ASCII value 41 hex
[info] - a should have ASCII value 61 hex
[info] BSuite:
[info] - B should have ASCII value 42 hex
[info] - b should have ASCII value 62 hex
[info] CSuite:
[info] - C should have ASCII value 43 hex
[info] - c should have ASCII value 63 hex
[info] Run completed in 685 milliseconds.
[info] Total number of tests run: 6
[info] Suites: completed 4, aborted 0
[info] Tests: succeeded 6, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.

Same issue at my side.

This should be fixed in 3.0.1. Not sure why the ticket did not get closed. Can you try 3.0.1 and let us know here whether that solves your issue?

Indeed, 3.0.1 does solve this issue. Thank you, Bill.

This issue could probably be marked closed now that 3.0.1 is released?

As told above, you are free to close this issue. I am not authorized to do it for you. am I?