Improve documentation

This PR will add a table of contents, a section about the new feature bundled features files and rearrange the content.
Should only be merged after https://github.com/TheBrainFamily/cypress-cucumber-preprocessor/pull/219

This is fantastic! I'm sure this will help a lot of people starting with the project. Thank you so much. :)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Init Templates / Recipes / UI Framework Choice

We want to do our best to remove any barriers for someone trying out Tauri. We have seen new users look to the examples repo which we have maintained thus far as a core testing playground. It has been discussed primarily on discord that we provide a command that makes testing and creating toy apps a breeze.
We have been talking about "recipes" for a bit now. We are thinking we "curry" a command like create-react-app and then follow up with the necessary config to set up Tauri to work with it. Like an init command for a greenfield tauri project build with X framework.
An ideal implementation would pull from a list of "templates" which list the command necessary to run and the required config in Tauri that needs to be set. In this manner, we should be able to offload most of the heavy lifting. I think it is open for discussion if this should be part of the init command or it's own separate command. I am imagining something like tauri init --template and this enables one of the questions to prompt which framework you would like to use.
Prompts are important so a user isn't expected to type in a framework correctly. It seems pulling from a list of templates is also important as it will enable more easily expanding that if the only requirement is a .json file (or equivalent).
I would love input on what others imagine this should be and how we might avoid pitfalls. My expectation is this is scoped to tauri.js and js only libs, and we can add similar as other CLI and bindings are added.

I started working on this here
My goal for a first PR would be to allow a user to init a new project with a react dev server generated by create-react-app, so that it's clear how to add support for other dev frontend choices.
So far, the help and init procedure are:
⟩ yarn tauri init -h
yarn run v1.22.4
$ /home/projects/example/node_modules/.bin/tauri init -h
[tauri]: running init

  Description
    Inits the Tauri template. If Tauri cannot find the tauri.conf.json
    it will create one.
  Usage
    $ tauri init
  Options
    [......]
    --plugin, -p         Add UI framework. Supported: react-js

Done in 0.26s.

⟩ yarn tauri init
yarn run v1.22.4
$ /home/projects/example/node_modules/.bin/tauri init
[tauri]: running init
? What is your app name?
? What should the window title be? Tauri App
? Would you like to add a UI plugin? (Use arrow keys)
❯ None
  react-js

No plugin selected by default. Note also that the choice of dev server URI would be controlled by plugin setting. None => Prompt for dev server URI, any other selection would assume that the devPath would be set by the plugin settings.

This is cool, a nice start. But the word plugin means something else. Would you please consider using 'recipe'?

Next.js calls them examples. Boilerplate & recipe is also nice.

One thing that @zakpatterson and I were discussing is the folder structure. We don't hold any particular strong opinions regarding folder structure and tauri (init does use src-tauri which may be the only one?), but we will need an opinion for this. I have generally assumed my root held the main package.json, an src for the ui/web frontend and src-tauri. Most of these init scripts (like create-react-app for instance) will create a folder for you to my knowledge. To support this structure, we would likely need to run create-react-app first (which creates the folder for you), and then lay tauri on top.
The current iteration of #930 assumes multiple package.json. The user creates the folder, adds a package.json (because tauri requires it), inits tauri and then runs create-react-app. This gives us a folder structure like the following. I don't know that either structure is "wrong" per se, but one vs the other kind of dictates the order we run these and the tauri assumptions as to what exists when running init.

Thoughts? Are there any frameworks out there that init differently than create-react-app that we need to consider?
/cc @tauri-apps/core

Should this be a top level command? Along the lines of tauri recipe that then hooks into the init sequence after choosing create-react-app or whatever. I think tauri init feels moreso intended towards bootstrapping tauri into an existing project. Additionally, we could support tauri recipe which runs your UI init script and then layers on tauri config, and also have tauri init and choosing a "recipe" assuming you have already run create-react-app and only takes care of the tauri config. Essentially tauri recipe for a greenfield project, tauri init for a brownfield project (but use some of the effort from tauri recipe to preset config).

That's a great idea really @jbolda

Sure we could put the UI project source, configuration, and build output in the same root directory as the main project. If the UI project is in a "js" framework, then it could share the same package.json file as the root project.
But then if the UI project were written in something else, like Scala,js, then the root directory would get a build.sbt file. Scala also puts its build products into a folder called target, so something else would need to be done to avoid colliding with rust's target folder.
For the sake of generality, it makes more sense to me at least for the UI code, build conf, and build output to go into one subdirectory by default. I get that's not how the examples are done now.
Also I started on #930 without looking through the PRs and roadmap, and I never saw #851. Should I put more effort on advancing #851 first?

The more I think about it, the more I tend agree. It probably makes sense to keep it consistent across the board. The being said, it probably makes sense to push towards using yarn for the workspaces. We need a root package.json for tauri, but most of these starter CLIs also add their own package.json. We could normalize everything from the root then I imagine.
Regarding #851, I think that is kind of waiting on #850 to reconcile things around that. We expect to always have a js CLI, but plan to add CLIs for other languages as well. Moving some of the core logic into rust means that we can share that between all of the CLIs. I don't know how clear that divide is, but I imagine the "recipe" logic makes sense to be implemented generally in each language. Then each can deal with the specfic language nuances there.
/cc @lucasfernog @tensor-programming ^ make sense to you?

I'm not sure I understand the use case for init to just add Tauri to an existing project. Should I add another top level command for recipe that only modifies an existing build configuration and runs the ui init script?

First of all, I like the idea of the PR and how it can make it much easier to get started with Tauri. I do have a few suggestions though:
First, I think that the CRA app files should be at the root level, with the src-tauri folder inside of it. It's how all the examples and the Vue CLI plugin are structured. The issue with Scala using target for dist isn't really a problem since Tauri dist is in src-tauri/target (although I do see how it could cause some confusion). Having a different structure than an existing CRA app with Tauri added via tauri init seems like unnecessary fragmentation. I think 95-99% of users will be using a JS framework and have a package.json anyway and sharing it would be easier to manage. Lots of new developers may try to install deps for their JS app into the tauri package.json and would be confused when it doesn't work.
Second, maybe we could automatically set beforeDevCommand to start the CRA dev server so that yarn tauri dev just works, instead of making the user run multiple commands (same for build).
Third, I think there should be two separate commands for using a recipe and adding to an existing app (like @jbolda suggested). Maybe tauri create for creating a new app with a recipe, and tauri integrate (or tauri init) for adding to an existing app. I think this will make the process easier to understand for new developers trying to decide how to get started with Tauri.
Finally, I'm a little worried that this may be out of scope for the Tauri CLI. Creating a full list of recipes and keeping them updated isn't an easy task. We'd have to monitor for breaking changes in each CLI we use and then update Tauri CLI to support the latest version. What if a user wants to pass arguments to their framework CLI's init command? Do we have to create a passthrough for all the different config args for each framework? We also want to migrate the CLI to Rust at some point, and this would make that more difficult. A getting started doc page with instructions for each of the frameworks would be easier to maintain and give the user more control, although it would sacrifice some ease-of-use.

The scope concerns are totally understandable. But it seems people agree something must be done because it's a common speed-bump for beginners.
Maybe init/create doesn't even belong in this repository? Maybe we need  create-tauri-app as a separate tool.

I actually really like the idea of create-tauri-app. It will make the Rust CLI transition easier since it could stay as JS. It would still be really easy for the user as they could just run yarn create tauri-app and then they're good to go.

@zakpatterson the thought with init in an existing project, I think is the expectation that has a web app and wants to add desktop app. That is currently the only init, but I imagine it would see less use with a recipe option as I expect the majority are greenfield projects.
I don't think we expected to have a package.json in src-tauri, @nklayman. (At least I didn't.) The root could operate off of yarn workspace, but that is extra to document and gets away from the value of recipes. I think whichever structure we choose will set a precedent. I don't know that we need to lean heavily on historical context being <1.0. The bigger question is in the context of future languages and bindings I think.
I agree with the beforeDevCommand, but I don't know how that would work with yarn workspaces (haven't actually used it yet myself).
My understanding is that there will still be a thin wrapper of js that I think this would new fine to fit within. I mentioned this earlier, but I don't think it makes sense for js to handle every languages "recipes" nor Rust necessarily either. I think that leads to some precedent for create-tauri-app, but other languages don't really do that (but maybe it doesn't matter but consistency is also nice).
At the end of the day though, we say this works with any UI framework so we will need some indication or documentation for every one otherwise it will come across as an empty promise. If this implementation only concerns itself tauri config and pass-through another command, the effort required is really low and will make getting into tauri a breeze. This brings in more people trying it out and seeing the possibilities, but also makes it much easier to spin up and test different frameworks. Marketing is a lot harder then code and even docs.
Where we place it is probably more open ended in my mind. I don't think we ever decided what the Rust CLI core would actually include?

Ok, parsing the above, I suggest this:

[ ] No change to current tauri init.
[ ] New top level command tauri recipe, which is basically the same as tauri init except that it can use a recipe to build the UI framework. Just so we're clear I'm going to implement this by renaming the current init to recipe with the extra -r flag, and creating a new command init which is an alias to recipe -r none.
[ ] React recipes set beforeDevCommand and beforeBuildCommand
[ ] I still think the UI build configuration stuff should be separate from the tauri build, the beforeDevCommand and beforeBuildCommand settings make this much nicer.
The point about installing packages to the web ui only is a great one. But adding packages to the desktop app behaves the same way. The Cargo.toml file is inside of the src-tauri folder. It just seems more congruent to me if the UI side of the desktop app has a parallel directory structure to the rust side.


nested groups fails to parse

Language => Expr: (STRING (COMMA [d] STRING)*)?
Error => "unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting IDENTIFIER, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting DISCARD, unexpected "(" (LPAREN) at line 1, column 15.expecting RPAREN, "
when I change language to this: Expr: (STRING COMMA [d] STRING)?
no problem occurs
Am I doing something wrong or nested groups are not supported?

hi @MrMuMu, first glad to see that you looked at CSLY.
for now nested groups are supported. And I have no plan to support it any soon as I son't see any usefull use case.
for your specific case the best solution is I guess :
Expr : OptinnalExpr
OptionnalExpr: STRING (COMMA [d] STRING)*
May I ask you what you arelooking at in CSLY ?
Are you planning to use it for any special purpose ?

The repeated error annoy me so I will look at it more precisely.

for now nested groups are supported. And I have no plan to support it any soon as I son't see any usefull use case.

You mean are not supported I think.
Yes, I have solved it just like that:)
I was going to send an email to you actually, after I have finished the core of my project.
I am trying to implement XPath support for .net core. Right now, .net core only support XPath 1.0 but there is already XPath 3.1 recommendation on W3C. I'm trying to implement a lexer, parser for this grammar by using your project. There are other approaches but I would like to use the published grammar.
I have searched other lexer, parser approaches but your "embeddable" solution got me^^

Grenat project ! I am happy that thé "embeddedable" features if CSLY hot toi. It was my main concern when I started it. Glad to sée that I am not tottaly wrong.


Possible to analyze ASP.NET Web Forms Site project?

Is there a way to analyze the code for Web Forms Site project?

environment

Microsoft Visual Studio Professional 2019 Version 16.11.29
.NET Framework 4.8
ASP.NET Web Forms Site

My example project

It seems like a question for ASP.NET:
https://github.com/dotnet/aspnetcore


ARROW-10825: [Rust] Added support for NullArray to MutableArrayData

This is awaiting #8849 to build

Codecov Report

Merging #8851 (bda962c) into master (38cfdc3) will increase coverage by 1.70%.
The diff coverage is 0.00%.

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

The full set of Rust CI tests did not run on this PR :(
Can you please rebase this PR against apache/master to pick up the changes in https://github.com/apache/arrow/pull/9056 so that they do?
I apologize for the inconvenience.


#37: Fills progress bar on finish

Fixes #37 This attempts to fill the progress bar after the finish() method is called for the progress bar.

Thanks for the pull request!
Can you add a test to the test suite that covers this issue?

This has been fixed in the 0.4 version


Allow extractor to accept different attractor radii

I've been thinking a bit about how to represent non-geocentric orbits and I think simply scaling the trajectory is the cleanest and most straight-forward way.
Obviously deleting or hiding the main body and defining a new ellipse is not a great idea. There are ways to resize the main globe in Cesium, but they require extra javascript code and I think it's better to do most of the job here, rather than hiding half the code behind the js application -especially for something this simple-.
For now, you can't really change the imagery layers, but this is the next thing I'm planning to work on.

For the record, after discussing a bit, we decided not to "hack" the planet radius and use a more consistent approach instead, even if it's more complicated.


Feature/predictor frame

This pull request includes:

GTSAM integrator
Change that odometry and imu messages are not published in the same frame as rovio
Fix that the odom predictor stops publishing (and diverging) after maximum queue size of imu messages reached since last received odometry message

ah forgot about this: At the moment both integrators are running (for comparison). Before merging, I would add a rosparam to select the integrator and only run one.


[Question]: No raptor switch in v0.6.0 or dev image but in the demo website.

Describe your problem
Thanks for your work.
It's strange that I can see raptor configs in the demo site, but when I setup my local environment by docker-compose with image v0.6.0 or dev, I cannot see the raptor switch.
As we can see, the onnx models in your demo website are much better than the open-source models. Now I see the UI/config is a little bit different.
My questions is, can you point out what kind of images do you use or anything else you use in the demo website is different from the open-source one?

RAPTOR config should be in DEV docker image.

v0.6.0 doesn't have RAPTOR which dev version of image has.
Modify the RAGFLOW_VERSION in docker/.env to dev.

Thanks. I pull dev image 2 days ago, and no raptor in it. you mean I need pull it again?


Resize dialog form

Ho do I resize the dialog that allows me to add / update the data? Some of my entities have a couple of fields, and I have to scroll to enter all fields.

It is done with less, see tutorial.

Great, thanks


Add an interface for get_source_and_targets

It looks like MiqRequestWorkflow is missing a default get_source_and_targets implementation. This method is called internally, but is not currently defined, apparently relying on subclasses to define it.
Given that there are already several other empty method declarations within the MiqRequestWorkflow model, I suspect this one simply got missed. For my first pass I've decided to add a bit of strictness to it so that it will raise a more informative error. This is a very basic way to implement interface enforcement in Ruby, though there are other ways if the reviewers of this PR prefer.
Originally smoked out when I turned on strict partial double validation.

@miq-bot add_labels refactoring, hammer/no, ivanchuk/no


Low results on validation set

Hi, I test my model on all train images (without corner) and got 11.1 map on tiny 50. However, the same model I submitted to the challenge website on the test set can achieve 50 map on tiny 50. So, would you share you your config which test on the test  or train set without corner info (no need for merge file)

just remove MERGE_RESULTS  and MERGE_GT_FILE will be ok, the necessary setting is:
TEST:
COCO_EVALUATE_STANDARD: 'tiny'  # tiny need change
MERGE_RESULTS: true
MERGE_GT_FILE: '/home/hui/dataset/tiny_set/annotations/task/tiny_set_test_all.json'
IGNORE_UNCERTAIN: true
USE_IOD_FOR_IGNORE: true


Phantom don't fly

When I kill one and transform into it, I can't fly

When I kill one and transform into it, I can't fly
Can you shoot fireballs as a ghast?

yes, and fly when i morph into a bee

I should probably note that the phantom flight ability is different to any other flying morphs: You have to be in the air and then press the ability key, and then you enter a glide mode. If you press the ability key whilst being in the glide mode, you will either quickly fly up or quickly fly down.


Add async calls inside custom ExpandRow renderer

There's a way of making async calls inside custom expand row renderer?

Hi, try using this:
onExpand={this.handleOnExpand}
expandRenderer={this.expandRenderer}
handleOnExpand= (row, isExpand, rowIndex, e) => {
    if (
        isExpand &&
        this.state.expands.filter(a => a.id === row.id).length === 0
    ) {
        this.loadDetails(row.id);
    }
};

expandRenderer = row => {
    const hit = this.state.expands.filter(a => a.id === row.id);
    if (hit.length === 0) {
        return Loading
    }
   return hit.anything

}

Here?

@jendamozna good sharing

Hi ! There are other way? Because I use functional component, and I make a request for each row for get data, I tried with hook and figure out in a loop infinite, never finish and throw a request limit.

Hi ! There are other way? Because I use functional component, and I make a request for each row for get data, I tried with hook and figure out in a loop infinite, never finish and throw a request limit.

Did you manage to solve this problem?


Docker image of Rasa X not getting pulled which installing via One Line Deploy Script

Rasa version:
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant): 0.33.2
Python version:
Operating system (windows, osx, ...): ubuntu 18.04
Issue:
in ec2 instance, all pods except rasa-app pod get created successfully.
Error (including full traceback):
      on running command `kubectl describe pods rasa-app-pod-name`

All the pods seem to work fine when Rasa X is set or 0.33.0 in an environment variable.
Command or request that led to error:
`curl -s get-rasa-x.rasa.com | sudo bash`

Content of configuration file (config.yml) (if relevant):

Content of domain file (domain.yml) (if relevant):

Thanks for raising this issue, @JustinaPetr will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

@gaushh Please reopen this if you are still running into this issue in the latest version of Rasa X

@gaushh Please reopen this if you are still running into this issue in the latest version of Rasa X


Latest articles - Bandcamp Daily failed with error 503

Error message: The requested resource cannot be found! Please make sure your input parameters are correct! cUrl error:  (0) PHP error:
Query string: action=display&bridge=BandcampDaily&context=Latest+articles&format=Atom
Version: dev.2020-02-26
Hi @VerifiedJoseph I added your bridge to my rss-bridge, but it seems like there are some issues, like the Latest Articles not working (error above); I get the same error the 'Album of the Day' choice under Franchises.
Regards,
Jack

https://github.com/RSS-Bridge/rss-bridge/issues/1523#issuecomment-609407858
Fixed the issue.


Add Global Variables and Mixins

Added files for global variables and mixins as well as my personal mixins for testing.

Try not to get in the habit of merging your own PRs without a review from a team member.


How can I use Chinese to write description in _config.yml?

When I tried this, I got a build error.

Using encoding:utf-8 may help. But I can't use Chinese when writing a  post.

I think you can use utf-8 to write a post in Chinese.
MacBook-Pro:_posts yuancalvin$ file -I 2015-12-13-test.md
2015-12-13-test.md: text/plain; charset=utf-8
MacBook-Pro:_posts yuancalvin$ cat 2015-12-13-test.md
---
layout: post
title: test
---

这是一篇测试的文档

I can do it without any problem : )
Hope this will help.

Thank for help. I find that it was the encoding error that cause the issue.


update playground app to use SwiftPackage and resolve compiler warnings

This PR:

removes dependency on CocoaPods from the playground app and references the library Package.swift instead.
updates code where deprecations warnings were prompted by the compiler
adds support for async/await to the excellent RequestProtocol (includes README example and a working code example)

The first commit is constrained to the first two bullets above
The second commit adds async/await support

Is this support for async/await working as described in the example? We are trying to use it and getting a runtime problem that breaks the app without any log or error.


Highlight search terms

Any chance we can get the search terms highlighted? I'd imagine it'd be something like:
let @/="foo"

I thought about this, but I'm not sure it's gonna work out.
I'd have to emulate all the regexp engines that grep tools use and it would have to be configurable in case someone needs to add a new grep tool. Unless there's a better way, this would be extremely lot of work.

When you enter the query yourself at the prompt, grepper assumes some things, so there might be some false positives in some cases. It does simple transformations like these:
\bfoo\b  ->  \<foo\>
*?  ->  \{-}
+?  ->  \{-1,}

And with this, I consider this feature implemented!


[moe]: add flash attention

📌 Checklist before creating the PR

[ ] I have created an issue for this PR for traceability
[ ] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[ ] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234

📝 What does this PR do?

Summarize your work here.
if you have any plots/diagrams/screenshots/tables, please attach them here.

💥 Checklist before requesting a review

[ ] I have linked my PR to an issue (instruction)
[ ] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[ ] I have performed a self-review of my code
[ ] I have added thorough tests.
[ ] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[ ] 🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

need to fix import error in test

https://github.com/hpcaitech/ColossalAI/commit/e2c0e7f92abf6b93ccb331298880a41553df0cc7#diff-60052b0dcfac281a5cb4066eec7883fb118236af31fe84e240742c44dbe0c034 this pr may be helpful

need to fix import error in test


Change behavior (sensor.random)

#Description:
random.randrange(10, 20) will create an integer between from 10 and 19. From my point of view it would be more natural to include 20 as well. The test needed a fix too.
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: random
    name: Random
    min: 0
    max: 20

Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

ok to merge when comment addressed and merge conflict resolved.


Combining multiple savedmodels into one SavedModel

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version (use command below):
Python version: 3.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template

Describe the expected behavior
I was able to combine multiple tf estimator savedmodels (linear classifiers) into one and then serve that final model instead of serving multiple models. I assumed the same process would work for boosted trees saved models.
Describe the current behavior
But when it comes to boosted trees, i am experiencing the following error :
NotFoundError:  Resource localhost/boosted_trees/QuantileAccumulator/_load_2153_load_11463/N10tensorflow34BoostedTreesQuantileStreamResourceE does not exist.
[[node import/boosted_trees/BoostedTreesQuantileStreamResourceGetBucketBoundaries_1 (defined at :2) ]] [Op:__inference_pruned_12525]
Function call stack:
pruned
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Model1, Model2 are my two loaded linear classifer estimators on the same feature set but for different cities; replacing them with boosted trees estimators yields the error

class CombinedModel(tf.Module):
def init(self):
self.model1 = model1
self.model2 = model2
@tf.function(input_signature=[tf.TensorSpec(shape=[None], dtype=tf.float32),
tf.TensorSpec(shape=[None], dtype=tf.float32),
tf.TensorSpec(shape=[None], dtype=tf.string)])
def call(self, feature1, feature2, city):
input1 = {
"feature1" : feature1,
"feature2": feature2
}
print(type(allotment_eta))
city_chennai = tf.constant(["chennai"])
city_mumbai = tf.constant(["mumbai"])
    # IF CITY IS CHENNAI
    if tf.equal(city[0],city_chennai):
        inference_func = self.model1.signatures["predict"]
        predictions = inference_func(**({"feature1": feature1, "feature2": feature2}))
        return predictions['probabilities']
    # ELSE CITY IS MUMBAI
    else :
        inference_func = self.model2.signatures["predict"]
        predictions = inference_func(**({"feature1": feature1, "feature2": feature2}))
        return predictions['probabilities']

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

@yaswitag1
Please, let us which Tensorflow version you are using?. Request you to share colab link or simple standalone code with proper indentation and supporting files to reproduce the issue in our environment.It helps us in localizing the issue faster.Thanks!

Hey,
The notebook can be found in the link attached below.
https://drive.google.com/file/d/1LaLmnzHAeRdqw-2LDv8Ew_TD-CGB7jvI/view?usp=sharing

I have tried in colab with TF version 2.2 ,nightly versions and was able to reproduce the issue.Please, find the gist here.Thanks!

Hey,
Are there any updates on this ?

@yaswitag1 I tried to execute the code in TF 2.5 and facing different error. Please find the gist here.Thanks!


[Question] Weight Conversion of GPTJ Model

Question
During the process of converting model weights, I encountered some confusion. Why is it necessary to set the weight of ln2 equal to ln1 when extracting the weights of GPTJ? Upon reviewing the code of GPTJ, I noticed that they neither use ln2 nor do they apply ln1 twice.

TransformerLens fits many models into a single consistent architecture.
This assumes, for generality, that there's a separate Ln for attention and
for MLP. GPT-J has a single LN applied once, and this normed residual
stream is then used for both attention and MLP. Ensuring ln1 and ln2 have
the same weights achieves an identical effect in the TL architecture
On Sat, 30 Mar 2024, 8:35 am Xiangyu Zhang, @.***>
wrote:

Question
During the process of converting model weights, I encountered some
confusion. Why is it necessary to set the weight of ln2 equal to ln1 when
extracting the weights of GPTJ? Upon reviewing the code of GPTJ, I noticed
that they neither use ln2 nor do they apply ln1 twice.
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/issues/531, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKOJ3BFETUAXLLKX6XDY2Z2MHAVCNFSM6AAAAABFPMHXXKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTMMZTGIYDCOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for you reply!


Elasticsearch not active before searching for product

Categories in menu are not showing on first pageload.
It appears to me that elasticsearch is not active or it's being "activated" when you search for product "test" on https://techdrones.no.
After clicking on the product in search, and clicking on "go back button", you'll see the categories finally appearing in the menu.
On my other 2 projects https://logima.io and https://hoversport.no everything works fine and all projects have the same configuration and different indexes etc.
What could be the cause?

Do you find the solution?

Do you find the solution?

Yeah! Precisely use Elasticsearch 5.6.0.
curl -L -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.6.0.deb ; dpkg -i elasticsearch-5.6.0.deb ; /etc/init.d/elasticsearch start
Works on my ubuntu instance.


fix: added missing param validation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How adaptable is this to a completely different environment?

Can, I modify the code to a completely different environment, rewards, states, actions etc? Which file should I start looking at first?

Please look at https://github.com/muupan/async-rl/issues/8.


Adding support for Rotary Position Embeddings

Adding the support for Rotary Positional Embeddings(RoPE).
tl;dr: Advantages of RoPE: This embedding gets applied to the query and key matrices, and hence (unlike ALiBi embeddings), is agnostic to the attention implementation and works out-of-the box for any attention implementation. Recent works have also shown that some variants of RoPE are good at extrapolating beyond training length.
Design doc
Experiments: 125M model, 1B model.

@dakinggg will this merge cause any problems in merging mpt code into the Hugging Face github codebase?


Add Pop OS as an option for install?

I'm running Pop OS, which is based off of Ubuntu.
Would you accept a PR adding support for it?

Since there’re so many Ubuntu-derived distributions…
I think we’d better add a new environment variable to alias system name?

Would you accept a PR adding support for it?

I’m open for accepting PRs:)

Since there’re so many Ubuntu-derived distributions… I think we’d better add a new environment variable to alias system name?

Would the environment variable look like this:

export SYSTEM_NAME_FOR_SWIFT=`$NAME $VERSION`

Im not much of a bash user, but then you could check that variable based on a list of supported  OS types and install swift based on that variable.
What do think?


VM: ARM precompiler on Mac assumes iOS ABI

SIMARM chooses to use the iOS ABI or the EABI based on whether the host is a Mac or not respectively.  This prevents building an AOT snapshot on a Mac host for an Android target.

cc @fsc8000

We have similar problems with the code alignment and stack alignment values as well.

Partially addressed by 85cdc0eac20e823c827d65685da8b1a9e1d9c2fe

9f2668c9987f0a86cac9cd46c5e3418df22e9f38


pkg hash added (#18)

pkg hash added

build string modification

Co-authored-by: Ritu Dhoot<EMAIL_ADDRESS>Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

We need to create tag open-ce-v1.5.0 from r4.4.0, which doesn't have this commit from main.

Raised another PR#20


Show an end-to-end example of creating a DataLoader

I believe the notebook is nicely rendered under this link:
https://github.com/pzelasko/lhotse/blob/5bf1b85ee0f47798cac6c717e6d36ba55946468c/examples/mini_librispeech/dataloader_example.ipynb

Nice!!!

Codecov Report

Merging #73 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #73   +/-   ##
=======================================
  Coverage   92.83%   92.83%
=======================================
  Files          36       36
  Lines        2429     2430    +1
=======================================
+ Hits         2255     2256    +1
  Misses        174      174

Impacted Files
Coverage Δ

lhotse/audio.py
96.35% <100.00%> (+0.02%)
:arrow_up:

lhotse/cut.py
88.46% <100.00%> (ø)

test/cut/test_padding_cut.py
100.00% <100.00%> (ø)

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 2c7eef4...4c781ca. Read the comment docs.


[BUG]Dateset scale is not supported in k8s 1.15

What is your environment(Kubernetes version, Fluid version, etc.)
k8s version:1.15.1
fluid:0.5.0
Describe the bug
I exec kubectl scale alluxioruntime imagenet --replicas=2 and failed
The logs shows The alluxioruntimes "imagenet" is valid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update
What you expect to happen:
How to reproduce it
Additional Information

Known issue,change the version of version


Add RabbitMQ

Please add RabbitMQ container

@Vasary
I will need to know a few things in order to decide about how to add it and link it to the rest.

What is your use-case (can you give some examples)
Does it require access from the host?
Does it require access from within the php container?

@cytopia

In my project all of request are deferred via RabbitMQ
Yes, it use web ui for monitoring queue
Yes, it require access from php container

I think a very good idea opportunity use PSQL or MySQL or both

@Vasary
Could you give me a more technical example please. Such as: Does it speak with a remote sock on a specific port? Or do you simply need some php module to be loaded?

Should already be working in Release v0.13. Only thing that's missing is Intranet layout adaptions and Documentation.

@cytopia thanks for add rabbitmq, nowadays i'm using a custom devilbox setup for my projects, but i see that soon i could use devilbox out of the box.

@eortega @Vasary RabbitMQ will be available in a few days.

@Vasary @eortega RabbitMQ is finally making it into the Devilbox: https://github.com/cytopia/devilbox/pull/354

https://devilbox.readthedocs.io/en/latest/custom-container/enable-rabbitmq.html#custom-container-enable-rabbitmq

Hey @cytopia it's really good to hear that; thanks for your effort in this project !!
I'm gonna try to update devilbox to newest version this weekend.
Regards.


Create checkbox to select between Interop and Beizer curve

Would be better than a flag at startup.

Right now I made a command line flag. It is not pretty.


Fix concurrency problem when moving ACL rules with drag&drop

Description

There was a concurrency problem with the “moveNetworkAclItem” API method. If two users were changing the ACL rules order at the same time, this could lead to inconsistent actions.
To solve the problem we added a “consistency check ” parameter, which is used to hold the consistency hash. This hash is created using an MD5 hash function on a String that is created with all ACL rules UUIDs concatenated in their order, which is defined via the ‘number’ field.
We also lock the editing of the ACL while executing the upgrade. This allows us to handle race conditions nicely, and present a good feedback for the user.
We are not forcing users to send the consistency hash variable. Therefore, they can use the API call without the hash parameter. Therefore, they assume the risk of problems that may arise due to race conditions scenarios.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs

How Has This Been Tested?
Via unit tests and locally.

Checklist:

[X] I have read the CONTRIBUTING document.
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Testing
[X] I have added tests to cover my changes.
[X] All relevant new and existing integration tests have passed.
 I'll keep you posted as I make progress.

@blueorangutan package

@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✖centos7 ✔debian. JID-2160

let me retry @rafaelweingartner
@blueorangutan package

@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian.


Allow tolerance to be customisable

Description:
Tolerance should be customisable to allow for inaccurate sensors.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#soon
Example entry for configuration.yaml (if applicable):
climate:
  platform: generic_thermostat
  heater: switch.heater
  sensor: sensor.temp
  tolerance: 5

Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Good work making it customizable! But for being a real on/off  tolerance difference the code should be changed to something like this:
      if not is_heating:
           too_cold = self._target_temp - self._cur_temp > self._tolerance
           if too_cold:
                  _LOGGER.info('Turning on heater %s', self.heater_entity_id)
                  switch.turn_on(self.hass, self.heater_entity_id)
      elif is_heating:
            too_cold = self._cur_temp - self._target_temp > self._tolerance
            if not too_cold:
                  _LOGGER.info('Turning off heater %s', self.heater_entity_id)
                  switch.turn_off(self.hass, self.heater_entity_id)

Please, can someone change it? Thanks a lot!

@r-jordan to have the tolerance work both ways? I think the intention was to avoid overshooting and undershooting.

@lwis yes, it has to work in both ways. Otherwise having a tolerance vale is the same as decreasing the target temperature by that value and setting tolerance to 0. Now the thermostat is stopping too early. You can read about hysteresis at https://en.wikipedia.org/wiki/Hysteresis#Control_systems

@lwis @balloob Do you think I should open an Issue for making the tolerance work both ways?

@r-jordan could you open a PR?

@lwis I haven't opened a PR before and I have no development environment ready to do the tests. But I'll try to do that all!

@r-jordan Gitter is a good place if you get stuck 👍


fix(types): Include types folder in npm package

Fixes #167

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


pip install qiskit fails

Environment

LATEST == qiskit-0.39.2.tar.gz
Python version: Python 3.9.12
Operating system:  UBUNTU 18.02

pip install qiskit
Collecting qiskit
  Downloading qiskit-0.39.2.tar.gz (13 kB)
Collecting qiskit-terra==0.22.2
  Downloading qiskit_terra-0.22.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (4.8 MB)
     |████████████████████████████████| 4.8 MB 2.4 MB/s
Collecting qiskit-aer==0.11.1
  Downloading qiskit_aer-0.11.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (19.2 MB)
     |████████████████████████████████| 19.2 MB 6.9 MB/s
Collecting qiskit-ibmq-provider==0.19.2
  Downloading qiskit_ibmq_provider-0.19.2-py3-none-any.whl (240 kB)
     |████████████████████████████████| 240 kB 776 kB/s
Collecting scipy>=1.0
  Downloading scipy-1.9.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (33.8 MB)
     |████████████████████████████████| 33.8 MB 58 kB/s
ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    scipy>=1.0 from https://files.pythonhosted.org/packages/bb/b7/380c9e4cd71263f03d16f8a92c0e44c9bdef38777e1a7dde1f47ba996bac/scipy-1.9.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl#sha256=c68db6b290cbd4049012990d7fe71a2abd9ffbe82c0056ebe0f01df8be5436b0 (from qiskit-aer==0.11.1->qiskit):
        Expected sha256 c68db6b290cbd4049012990d7fe71a2abd9ffbe82c0056ebe0f01df8be5436b0
             Got        1d0e730a05d6b17f04d18033d6a6602d621ca2aeda1c02c437934487abd477c3

What is happening?
Call stack thrown
ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    scipy>=1.0 from https://files.pythonhosted.org/packages/bb/b7/380c9e4cd71263f03d16f8a92c0e44c9bdef38777e1a7dde1f47ba996bac/scipy-1.9.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl#sha256=c68db6b290cbd4049012990d7fe71a2abd9ffbe82c0056ebe0f01df8be5436b0 (from qiskit-aer==0.11.1->qiskit):
        Expected sha256 c68db6b290cbd4049012990d7fe71a2abd9ffbe82c0056ebe0f01df8be5436b0
             Got        1d0e730a05d6b17f04d18033d6a6602d621ca2aeda1c02c437934487abd477c3

How can we reproduce the issue?
run pip install qiskit on linux machine with python 3.9
What should happen?
Should be able to install it
Any suggestions?
No response

That specific error ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. and the other related output points to a local networking issue. What pip is reporting there is that it downloaded a package file for the package scipy (which is a dependency for qiskit) and the checksum of that file it downloaded from PyPI does not match the checksum the package recorded for itself. This points to something corrupting the file when it's being downloaded (a network issue, hardware fault, etc). I expect this is coming up on scipy because it's a larger package (33.8MB compared to the 4.8MB for terra and 19.2MB for aer). My only suggestion is to maybe try fetching the scipy package from https://pypi.org/project/scipy/#files directly and manually verifying the checksums to see if you can get it to download without any corruption. If you can download it and verify the contents with the checksum then you can manually install the package and try installing qiskit again (although it's likely you'll have similar issues on other packages too).
That being said there isn't really anything we can really do about it from the qiskit side as the failure is local to your specific environment and/or network. I'm going to close this issue accordingly, but please feel free to reopen this if I'm missing something or there is more to discuss on this.


Drag and Drop Taking More time for large set of data

Hello Obaid,
I am using this library from past 6 month and till now it's very good. But, as my application is growing with huge data sets then drag and drop is taking too much time. Lets say i have 2000 item in a list to drag any item from list and drop it to some area its taking 20-30 seconds, can you suggest what to do in this case?

@rrohitesh any chance you can reproduce this in Plunkr?

This is also an issue i have hit with it, i have done some investigation and found the source of the issue in my case, probably the same issue for rrohitesh.
Because angular uses zone.js for its change detection it will re run a full change detection cycle when any dom event fires, this becomes a problem with large amounts of draggables, in my case it was with a list of 200 draggables that use angular templates. I have updated my fork with a fix for the issue which consists of running the repeat firing dom events(drag, dragover, dragenter, dragleave) in the parent zone so they do not trigger a change detection run.
The only caveat to this is that if you do something with the onDrag, onDragOver, onDragEnter or onDragLeave event emitters that needs to cause a change detection run then with my change you would need to run something in the angular zone to trigger it. That can be done like this;
this.zone.run(() => {     console.log('Update now!'); });
I can issue a pull request if you think the change is worthwhile?

This Plunkr should show the issue;
http://plnkr.co/edit/bJG679H1G0pzf3PMvUuX?p=preview

I have created a pull request with my fix for this issue #94

Thanks, @Sypher1987, I'll take a look.

Thanks for the fix @Sypher1987 . Much appreciated.
Fixed in v2.9.1.


[Bug]: "defualt schema" is not displayed when creating a new ODP sharding mysql datasource

ODC version
4.2.3
OB version
odp sharding mysql
What happened?
"defualt schema" is not displayed when creating a new ODP sharding mysql datasource：

What did you expect to happen?
"defualt schema" is displayed when creating a new ODP sharding mysql datasource：
How can we reproduce it (as minimally and precisely as possible)?
creat a new ODP sharding mysql database
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit bdc5e71e82f649f2778e1eea6f680df10309126a
------
晓康
Mon Nov 13 17:14:07 2023 +0800


The battery_alert package has trouble with 0.170 HA release due to Groups changes

Check out breaking changes for 0.107 https://www.home-assistant.io/blog/2020/03/18/release-107/ and the note related to Groups. Because the battery_alert package uses group.set, it's having some issues with this new release because that service no longer exists - at least, not with that name.
Not sure how to fix, but wanted to report the issue.
Error returned by HA is "Unable to find service group/set."

I just corrected an issue in my groups configuration and now it seems the service call is working okay, but I think there are still other issues because on the battery page there are a number of unavailable battery group entities.

https://www.home-assistant.io/integrations/group/
Lines such as 'view' and 'control' are no longer valid:
battery_alert:
control: hidden
battery_view:
view: yes

Seems like there is a pull request already that fixes this:
https://github.com/notoriousbdg/Home-AssistantConfig/pull/23/files

I have the same problem

Same problem here. Can someone update script to work 0.107+?
It is good script. It should be nice to see it in HASS COMMUNITY STORE ;)

yeah, i made a merge request but think notorious is busy with other life stuff atm. you can just use an editor to find and delete the offending lines.

Not only does the group/view give issues but it also returns the following error for me when I toggle settings: Unable to find service input_number/turn_on
Home Assistant 0.110.3

Hi everyone,
I got this to work with my HassOS install.
I made a PR here and added a little documentation:
https://github.com/notoriousbdg/Home-AssistantConfig/pull/27
Feel free to test, the direct raw file is here:
https://raw.githubusercontent.com/notoriousbdg/Home-AssistantConfig/164d3d736abfed943c4a4a71ec769022dc3045aa/packages/battery_alert.yaml
I'm interested to know if this works for others.
Thanks.

https://github.com/notoriousbdg/Home-AssistantConfig/pull/27 has been merged.  Thanks @KptnKMan!


兼容spring boot1吗

Your question
describe your question clearly
Your scenes
describe your use scenes (why need this feature)
Your advice
describe the advice or solution you'd like
Environment

SOFATracer version:
JVM version (e.g. java -version):
OS version (e.g. uname -a):
Maven version:
IDE version:

Caused by: java.lang.ClassNotFoundException: org.springframework.boot.context.properties.bind.Binder

Caused by: java.lang.ClassNotFoundException: org.springframework.boot.context.properties.bind.Binder
你用的 tracer 版本是多少，如果是 springboot 1.x 的话可以使用 tracer 2.4 版本

Since there is no feedback for a long time, please close this issue here first. If you have any questions, you can open it again.


Cannot generate library with name app-routing

Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [X] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node --version = v8.11.3
npm --version = 5.6.0
Angular CLI: 6.1.5
Node: 8.11.3
OS: linux x64
Angular:
...
Package                      Version
@angular-devkit/architect    0.7.5
@angular-devkit/core         0.7.5
@angular-devkit/schematics   0.7.5
@schematics/angular          0.7.5
@schematics/update           0.7.5
rxjs                         6.2.2
typescript                   2.9.2
Repro steps

I created a new app so that I could generate a number of different libraries:

Create a new application: ng new libraries

from the libraries folder that just got created, I generated a library:
ng g library @companyname/authentication
The library is generated in the libraries/projects/companyname/authentication/ folder
I attempt to generate another library:
ng g library @companyname/app-routing
I receive an error: Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
This has to be a bug. Can anyone please confirm?
The log given by the failure

Desired functionality

It should not give an error when I want to create a library called @companyname/app-routing
Mention any other details that might be useful

Related to https://github.com/angular/angular-cli/issues/11961


create_oauth_request should support JSON payloads out of the box

Is your feature request related to a problem? Please describe.
The flask and Django helpers both take use_json in create_oauth_request, but this flag is never used in the integration code itself, causing developers to have to build the request object manually if the endpoint accepts JSON.
I'm porting over existing code that used Flask-OAuth2lib which seemed to do this.
Describe the solution you'd like
The helper code should look at the headers and determine if it should use JSON automatically.
use_json = request.headers.get('Content-Type').find('application/json') != -1

Describe alternatives you've considered
I've currently built my own helper that looks at the content type:
def create_oauth_request(request):
    """
    Ported function from flask_helpers.py (link below) to improve JSON support.
    https://github.com/lepture/authlib/blob/master/authlib/integrations/flask_helpers.py
    """
    from authlib.oauth2 import OAuth2Request
    from authlib.common.encoding import to_unicode
    body = None
    if request.method == 'POST':
        if request.headers.get('Content-Type').find('application/json') != -1:
            body = dict(request.json)
        else:
            body = request.form.to_dict(flat=True)

    url = request.base_url
    if request.query_string:
        url = url + '?' + to_unicode(request.query_string)

    return OAuth2Request(request.method, url, body, request.headers)

I'm happy to submit a PR with this built-in if it gets your support.

@mmattax Hi, this use_json is used in:
    def create_json_request(self, request):
        return create_oauth_request(request, HttpRequest, True)

@lepture I'm facing the same issue as @mmattax was here. I'm trying to allow JSON requests to my OAuth server and currently only urlencoded form requests are possible. Would it make sense to dynamically call create_oauth2_request or create_json_request based on the request headers? Currently I can't see how create_json_request would ever be callable during the authentication flow - it only seems to be called for protected calls with an OAuth Access token already in place.
Happy to submit a PR if you'd consider it!

@YPCrumble Authlib respects standard. As RFC6749 stated, the payload should be in application/x-www-form-urlencoded, you can't send JSON payload to token endpoint. In this case, I will not accept such a PR.
You can always rewrite the create_oauth2_request method on your AuthorizationServer so that your provider can accept JSON payload. But Authlib won't provide it by default.


update: expose recordedChunks api from record

Short description
Resolves #
Implementation details
How to test it
Screenshots
Checklist

[ ] This PR is covered by e2e tests
[x] It introduces no breaking API changes

Closed as a duplicate.


ERROR/warning when read pdb files

I want to know whether the following ERROR/warning matters when I mutate amino acids in pyrosetta:
core.import_pose.import_pose: File '/data2/rjli/test_dataset/1amk/1amk_protein.pdb' automatically determined to be of type PDB
core.io.pdb.HeaderInformation: [ WARNING ] Deposition day not in range [1, 31]: 0
core.io.pdb.HeaderInformation: [ WARNING ] Unrecognized month in HEADER deposition date
core.io.pdb.HeaderInformation: [ ERROR ] Malformed Compound record found: ' 1AMK_PROTEIN'
core.io.pose_from_sfr.PoseFromSFRBuilder: [ WARNING ] discarding 4 atoms at position 1 in file /data2/rjli/test_dataset/1amk/1amk_protein.pdb. Best match rsd_type:  SER:NtermProteinFull

THE PYTHON CODE :
import os
from pyrosetta import *
from pyrosetta.rosetta.protocols.simple_moves import MutateResidue
init()

source_folder = '/data2/rjli/test_dataset'

for id in os.listdir(source_folder):
    folder_path = os.path.join(source_folder, id)
    if os.path.isdir(folder_path):
        for file in os.listdir(folder_path):
            if file.endswith('protein.pdb'):
                protein_file = os.path.join(folder_path, file)
                pose = pose_from_pdb(protein_file)
                n_res = pose.total_residue()
                # loop over all residues
                for i in range(1, n_res + 1):
                    res = pose.residue(i)
                    if res.name() == "ASN":
                        # create a MutateResidue mover to mutate Asn to Leu
                        mut = MutateResidue(i, "LEU")
                        mut.apply(pose)
                    if res.name() == "GLN":
                        # create a MutateResidue mover to mutate GLN to Leu
                        mut = MutateResidue(i, "LEU")
                        mut.apply(pose)
                output_file = os.path.join(folder_path, f'{id}_mutate0_protein.pdb')
                pose.dump_pdb(output_file)

I don't see anything in the quoted warnings errors which immediately be suspect. I would suggest dumping the PDB after loading and checking if everything looks like you expect it to.


New version: qBittorrent.qBittorrent version 4.3.9

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Kind of weird considering VirusTotal says the files are ok
x64 x86
Would maybe be nice to know which one flagged, but nothing much I can do, unfortunately.


In temporary conversation mode, mobile users cannot use the three dots in the top right corner of the interface to reopen the Artifacts function that was closed during the conversation

Bug Report
Installation Method
Docker
Environment

Open WebUI Version: v0.3.32
Operating System: Ubuntu 22.04
Browser (if applicable): Android Edge 129.0.2792.65

Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[ ] I have included the Docker container logs.
[x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
When enabling temporary conversation mode on mobile, the three dots in the top right corner should allow reopening of Artifacts that were closed during the conversation.
Actual Behavior:
There are no three dots in the top right corner of the temporary conversation on mobile.
Description
Bug Summary:
In temporary conversation mode, mobile users cannot use the three dots in the top right corner of the interface to reopen the Artifacts function that was closed during the conversation.
Reproduction Details
Steps to Reproduce:

Open Open WebUI on a mobile browser and enable temporary conversation mode
Ask LLM to output some HTML code
Notice that there are no three dots at the top right corner, so Artifacts cannot be opened

Additional Information
Although what I'm about to say might not be a bug, I still think it should be improved: allow the three dots on the top right corner to be accessible even when a conversation has not started on mobile. After all, many times I need to add special system prompts rather than using my custom commands.
Thank you!

Added to dev!


Custom BBCode for RichTextLabel

I know there's _draw functions for characters similar to what i'm proposing which make it easier to make your own text rendering engine but I think being able to work with, tweak and extend the higher level tools the engine gives you to suit your needs is more efficient.
RichTextLabel for instance does a LOT of nice things for you which you would have to re set up in your own implementation. It being based in C++ also makes it faster and being an inbuilt note means it just generally plays nicer with everything else.
This also makes it easier to make custon "control codes" for game specific stuff.
(specifically, control_codes are bbcode that don't parse text and don't need an end tag. They're just there for stuff like shaking the textbox, adding pauses or changing the text speed. All mid sentance or as metadata.)
Everything within square braces could be automatically treated as a bbcode tag and hidden thus requiring escape characters to use square braces them normally (although square braces already cause strange rendering problems so not a big loss).
Here's my idea for a couple of functions and classes for or related to RichTextLabel as an implementation of this feature.
If you don't like the idea of implementing more classes for this most of these could easily just be dictionaries but I think it makes everything far less janky.
function evaluate_bbcode(string bbcode)
returns an array containing sets of RichTextString objects for the passed bbcode
class RichTextString
Member values:
Dictionary parameters: {"parameter":value} (Dictionary of the parameters passed in the bbcode)
Array characters: (Just an array of RichTextCharacters, the text between the tags)
class RichTextCharacter
Member values:
index: position in string (Read only or auto support insertion? Don't know if this would be inefficient and liable to mess things up :0)
offset: (The most "local" local positioning. Relative to where the character would normally be displayed. Auto updates whenever another position value is changed)
local_position: (The character's position relative to the textbox. Auto updates whenever another position value is changed)
globall_position: (The character's position relative to the screen. Auto updates whenever another position value is changed)
modulation: (Color and alpha transparency.)
font: (Controls the character's font. nuff said.)
function evaluate_control_code(string control_code)
Like evaluate_bbcode it returns an array. This time full of RichTextControlCode objects for that specific control code
I'm not sure whether it would be more efficient to make control codes their own thing but if they are I'd suggest using < and > to denote their specific tags
class RichTextControlCode
int index: (Position in overall bbcode string. Keep in mind that codes don’t take up any characters in the final string)
Array characters: (An array of RichTextCharacters)
Note that I'm not familiar with how bbcode and such is parsed "under the hood" so if anybody else knows a better implementation or something I'm missing please feel free to speak your mind below.
Also, if anyone's used textmesh in unity before and see they handle something better than this pitch, drop it below.

very well-written. thank you for inspiring yokai

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Make BgpkitParser Generic For Any Reader

These changes have the goal of allowing the BgpkitParser to use a generic reader including non-'static values as described in #74. The most important part of this is it allows the construction of BgpkitParser using mutable references to existing readers. This is helpful because it allows a BgpkitParser to be created without consuming ownership of the reader.
After making these changes, cargo test showed all tests passing on my machine.
On a somewhat related note, I have noticed a couple other areas where the performance could be improved with some simple changes. Are you open to additional pull requests?

Hey @jmeggitt, this looks good. I checked out the code and it seems to be working fine for me as well. Just to double check this gets what you originally wanted, I added a local test for muttable reference of a reader, and it works well too.
        let http_stream = ureq::get("http://archive.routeviews.org/route-views.ny/bgpdata/2023.02/UPDATES/updates.20230215.0630.bz2")
            .call().unwrap().into_reader();
        let mut reader = bzip2::read::BzDecoder::new(http_stream);
        assert_eq!(12683, BgpkitParser::from_reader(&mut reader).into_elem_iter().count());

        let mut reader = oneio::get_reader("http://archive.routeviews.org/route-views.ny/bgpdata/2023.02/UPDATES/updates.20230215.0630.bz2").unwrap();
        assert_eq!(12683, BgpkitParser::from_reader(&mut reader).into_elem_iter().count());

Thinking about performance improvements, one other obvious place to work on is the conversion from BGP message records to elements, i.e. spliting and duplicating record information into messages for individual prefixes. The main pain point was from the borrow checker, and the code is obviously not optimized at the moment (e.g. a lot of clonings).
https://github.com/bgpkit/bgpkit-parser/blob/remove-custom-databytes/bgpkit-parser/src/parser/mrt/mrt_elem.rs#L119

I thought it might be interesting to do a profile to see which parts actually have the largest impacts on performance.
The setup was fairly simple. I just wrote a simple test program which parsed the first 5 million entries from a table dump then exited. This was then compiled in release mode with debug symbols using bgpkit-parser 6055612. I used Intel VTune to perform the profile and it gave me the following results.
use std::hint::black_box;

fn main() {
    let start_time = Instant::now();
    let parser = BgpkitParser::new("C:\\Users\\Jasper\\Downloads\\bview.20220911.0800.gz").unwrap();
    let mut count = 0;
    for elem in parser {
        black_box(elem);
        count += 1;
        if count == 5000000 {
            break
        }
    }
    println!("Elapsed: {:?}", start_time.elapsed());
}

Here was the result of that run. I included the image for context, but much of it is unreadable without clicking the various segments.

Here are a couple of the parts I found interesting:

Elementor::record_to_elems took up 11.9% of the total CPU time, but the vast majority (67.7%) of that time was spent waiting on the system allocator. From a quick glance, all of these cases involved using Vec.
The function that took the most CPU time (42.0%) was ReadUtils::read_nlri_prefix. This is not that surprising given the type of file being parsed, but it looks like there are a number of ways that this could be improved.
26.1% of the entire application runtime was spent to allocate/free memory.

Because viewing a table dump leads to somewhat biased results, I also ran it again on one of the largest updates files I could find for rcc15 (updates.20230124.0750.gz, 31MB). The test code was exactly the same except for switching out the file path.

In this case, the majority (59.1%) of the CPU time was spent allocating and freeing memory using the system allocator. An additional 7.8% of the CPU time was spent using memcpy. It is a bit harder to tell if memcpy is being overused, but roughly a third of that seems to involve stuff being cloned in bgp_update_to_elems.
An easy way to get a sizable performance boost might be to use a crate like smallvec, tinyvec, or arrayvec. With some slight variations, they all provide vec-like data structures that reserve a certain amount of space on the stack before allocating space on the heap. This could have a massive impact on performance for cases where you need the flexibility of a Vec, but know than in most cases it will only hold a small number of elements. In fact, if you enable the union feature for smallvec it can use the space a Vec would normally use for the base pointer and capacity to start storing values instead. This means that if total number of items placed on the stack before moving to the heap totals to less than 2 machine words (16 bytes on x64) then it will be the exact same size as a Vec would be minus the heap.


fix: AtlasmapProvider should accept inspectionParameters for CSV

Fixes: #2265

One follow-on question on this after I +1'd it, would all usages besides Syndesis of the atlasmap component need to be updated, i.e. the app that holds atlasmap standalone, vscode extension, storybook?

No, that interface is for Syndesis only.

awesome, tx!


How about add a tree component？

Like this.

Not something we'll be building into Bootstrap anytime soon. You can get there with our collapse and accordion functionality, and I imagine others have built this as a plugin/extension.

Not something we'll be building into Bootstrap anytime soon. You can get there with our collapse and accordion functionality, and I imagine others have built this as a plugin/extension.

Thank you. I will try to achieve it.


SE-0210: improve documentation comments per @natecook1000's comments.

@natecook1000 here are the comment updates you requested in https://github.com/apple/swift/pull/15519. I'm going to go ahead and merge these so I can start my cherry-picks, but we can tweak further if needed.

Sure thing! I've got a branch with some other fixes, I'll rebase on this and do another pass there. Thanks!


updated texts (1.2)

Thank you for the contribution. It was merged directly as 53b06816e4c5600a8d81446cc15e02383f356361 to keep commit history cleaner.


createWebviewPanel to Return the Existing Panel of the Same viewType

Scenario:
An extension presents a webview in a command. This webview is maintained as a singleton in the extension code. A serializer is also implemented to restore the webview after reload.
When VS Code reloads, if the webview is not active before the reload, then VS Code keeps it inactive after reload. We can see the title of the webview but it is not actually rendered.
Now, when the user triggers the command again, a new webview panel is created by calling createWebviewPanel. So we see two webviews with the same title in VS Code.
Problems:

Is there a way to iterate the existing webviews? I didn't find a way to do so. If I can iterate and activate the existing webviews, then I can solve this problem.
Should createWebviewPanel create a new panel or return the existing instance?

Requests:

VS Code to provide APIs to iterate and activate existing webviews.
createWebviewPanel to reuse webview panel when the specified viewType already exists.

VS Code to provide APIs to iterate and activate existing webviews.

The API is designed so that web view objects aren't discoverable because extension A wouldn't know what to do with WebView of extension B...

VS Code to provide APIs to iterate and activate existing webviews.

The API is designed so that web view objects aren't discoverable because extension A wouldn't know what to do with WebView of extension B...

This looks like a security concern, to access webviews that were created by other extensions.
But the case here is to access what was created by myself. createWebviewPanel and the WebviewPanelSerializer should coordinate to avoid duplicating the webview panels of the same viewType. Does that make sense?

createWebviewPanel and the WebviewPanelSerializer should coordinate to avoid duplicating the webview panels

I think they do, the doc says 'The serializer should take ownership of this panel. The serializer must restore the webview's .html and hook up all webview events.' which makes me believe this should/could work.

This is a problem but I agree that querying webviews is not an api we want to add. We also don't want to move away from making webview restoration lazy. Giving webview some sort of unique id that we can de-duplicate by VS Code could work but needs some more thought.
You can also sort of work around this. Here's what the markdown preview does:

In your extension, track all the webviews that you create or are restored from serialization
When a webview is restored just check to see if there is already a "duplicate" view showing somewhere
If there is a duplicate, dispose of the duplicate and make the restored webview into the primary view.

With this, there may be multiple tabs for a webview singleton: some that are awaiting restoration and at most one active one. But once any pending webviews are restored, they will get de-duplicated by your extension so there is conceptually ever only one active one. No one's reported the duplicate tabs being problematic for markdown in the year+ since it was added (although now that I say that, I can already sense the incoming issue)

This is a problem but I agree that querying webviews is not an api we want to add. We also don't want to move away from making webview restoration lazy. Giving webview some sort of unique id that we can de-duplicate by VS Code could work but needs some more thought.
You can also sort of work around this. Here's what the markdown preview does:

In your extension, track all the webviews that you create or are restored from serialization
When a webview is restored just check to see if there is already a "duplicate" view showing somewhere
If there is a duplicate, dispose of the duplicate and make the restored webview into the primary view.

With this, there may be multiple tabs for a webview singleton: some that are awaiting restoration and at most one active one. But once any pending webviews are restored, they will get de-duplicated by your extension so there is conceptually ever only one active one. No one's reported the duplicate tabs being problematic for markdown in the year+ since it was added (although now that I say that, I can already sense the incoming issue)

Thanks for the info. First of all, it does not look good to have multiple tabs:

Second, it's not true when one tab is activated and then others can be disposed (see screenshot above). The deserializeWebviewPanel is only called when users click on one of the tabs (no objection regarding lazy restoration), and that's when we can check for duplicates and dispose. That means users need to click on each tab to get them disposed. And the behavior itself makes no sense.
The singleton to check for duplicates and dispose was already implemented and shipped, but the workaround is still problematic. So my goal here is to have only one tab and I'm open for options.

I think this is a good use case of the custom editor api proposal: #77131
To implement this, you'd:

Register a file system provider for your welcome page
Register a custom editor for some special file on that file extension.
Using the normal VS Code commands, invoke open for your welcome page resource in the target group

The custom editor api will ensure that only a single webview for a given resource exists in a group at a time


Any auth in your sceleton?

Hello!
Thank you for your articles!
I saw many old references that you used session authentication in Slim skeleton.
Now, in this repo I see no traces of ANY authentication in middleware or in somewhere else.
Did you remove that?
My goal is to learn how to use session auth using a middleware in Slim apps.
Maybe  your e-book have some practical examples for that?

Hi @palansher
Sessions has been removed from the Skeleton project, to make it more agnostic and API friendly. Sessions are mostly used for web-applications with a frontend. There is maybe one exception, for example when you implement a OAuth 2 Implicit Grant flow. But the implicit grant flow is no longer a suitable authentication method anyway.
There are plenty of options for auth available. The "best" solution depends on your project specific requirements,
e.g. Sessions (Cookie authentication), Basic Auth, API-Keys, Bearer (JWT), Oauth2 (authorization) etc.

https://odan.github.io/slim4-skeleton/security.html

In my eBooks (vol1 and vol2) you will find articles and examples covering all these topics.

Thanks! Got it.


The subdomain correctly redirects to the server and still the error message is displayed.

The entered domain does not resolve to the primary public IP of this server.
Please make an A record pointing to your server's IP. For example, if you make an A record called 'panel' pointing to your server's IP, your FQDN is panel.domain.tld
If you are using Cloudflare, please disable the orange cloud.
If you do not have a domain, you can get a free one at https://freenom.com
Please enter your FQDN (panel.domain.tld):
The subdomain correctly redirects to the server and still the error message is displayed.

I tried to install my server today and ran into the same issue.
dig +short myip.opendns.com @resolver1.opendns.com show the correct public IP and I can see the domain resolves to the same, correct IP.

I tried to install my server today and ran into the same issue.
dig +short myip.opendns.com @resolver1.opendns.com show the correct public IP and I can see the domain resolves to the same, correct IP.
Update: managed to get it to work by replacing this line in the script:
SERVER_IP=$(curl -s http://checkip.amazonaws.com)
with
SERVER_IP=$(dig +short myip.opendns.com @resolver1.opendns.com)
Not sure why amazonaws didn't resolve to the correct address.

 DNS may take time to propagate.

I tried to install my server today and ran into the same issue.
dig +short myip.opendns.com @resolver1.opendns.com show the correct public IP and I can see the domain resolves to the same, correct IP.
Update: managed to get it to work by replacing this line in the script:
SERVER_IP=$(curl -s http://checkip.amazonaws.com)
with
SERVER_IP=$(dig +short myip.opendns.com @resolver1.opendns.com)
Not sure why amazonaws didn't resolve to the correct address.

 DNS may take time to propagate.

Works fine now and thanks for the update to 1.0.3 !
I'm installing now. Fingers crossed ;-)

Okay, I am closing this issue since it's not really an issue with the script.


Global declaration of vars conflict with test cases.

Challenge Factorialize a Number has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.26.2840.71 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
var factor =1;
function factorialize(num) {
  for (var i=1; i<=num; i++){
    factor *=i;
  }
  return factor;
}

factorialize(10);

The issue tracker is for reporting bugs only. Please use the help chat room or try looking through the forum for help with a specific challenge.
Happy Coding.

i think the code is correct but it is showing wrong

Apologies, please have a proper title and description on the issue next time, screenshots are appreciated. I closed because this appeared like an issue seeking help with the challenge.
And yes your code is correct, but unfortunately is using the var factor =1; in global scope.
This conflicts with the test cases.
If you move the same inside the scope of the function, it should work fine.

Closing again as duplicate of https://github.com/FreeCodeCamp/FreeCodeCamp/issues/9199


Better SQL function help strings in query-builder UI

Better SQL function help strings in query-builder UI
Affected Version
Version: 0.21
Description
Consider the "stock" Wikipedia data source and stock Docker Druid cluster. We want to write a query that uses some of the time functions. To see what is described here, you'll want to follow along in the UI.
Start with the following:
SELECT
  __time,
  channel,
  page
FROM "wikiticker-2015-09-12-sampled"

Now, let's round the time to an hour. What function do we use? There is no UI to tell us the available functions, we just have to look at the documentation. Many products do have a list of functions so we can stay in the query builder. So, that's the first UI feature request: list of functions, preferably grouped as in the documentation.
Let's say we find the FLOOR function in the documentation. We start to type:
SELECT
  __time,
 FLOOR
 ...

We get a choice list that includes the FLOOR function, along with this "help":
FLOOR
Syntax:
FLOOR(expr)

Description:
Floor.

So, the second UI request is that the help actually be helpful: at least give the function signature and summary from the documentation:
FLOOR
Syntax:
FLOOR(timestamp_expr TO <unit>)

Description:
Rounds down a timestamp, returning it as a new timestamp. Unit can be SECOND, MINUTE, HOUR, DAY, WEEK, MONTH, QUARTER, or YEAR.

By contrast, if we'd typed TIME_CEIL, the help would have been filled in. So, it seems the help is spotty; sometimes you win, sometimes not.
Let's continue along. We type the opening paren, the UI fills in the closing one and places the caret in between, ready for us to type:
SELECT
  __time,
 FLOOR(|)
 ...

Now, what are the arguments? By now, the help (as weak as it was) is gone, we're left guessing. (Or, in reality, we flip back over to the documentation.)
Thus, the third UI request is to give guidance for the arguments. Three ways this is commonly done are:

Expression builder: separate dialog to build up the call. Rather old-school.
Phantom placeholders: when adding the close paren, show the function as FLOOR(<timestamp> TO <unit>) with the two <arg> elements as hints that get replaced as soon as the user starts typing. Great, but only works for new expressions.
Tool-tip hover hint: hover the cursor over the function to get the help text from earlier. This works well all the time: new expressions and looking at existing queries.

There is a dynamic function list giving you the candidate functions and corresponding docs when typing in the Web Console. The first 2 requests you mentioned are already met.

@FrankChen021, thanks much for the explanation. Yes, I agree that the pop-up list exists: it was noted in the description. The key is that I have to know the function name ahead of time. For example FLOOR is commonly a function for converting floats to ints, so us newbies wouldn't expect it to be the name of a date-time function. Thus, some kind of UI tool to show functions grouped by category would help when we don't know the name.
Note also that this pop-up disappears once I type the opening paren. But, that is exactly the time when the parameters are needed. Type "time_" pick TIME_CEIL, type "(". Pop-up is gone. What are the parameters again? That is one of the issues described here.
Yes, a workaround is to start a new expression with the same function, see the parameter list again, and go back and fill in the parameters for the first function. Highly awkward, but I agree that it technically works.
Of course, I find it easier to keep a tab open with the SQL documentation rather than fuss with the UI. This request is to modify the UI so I don't need to have that doc. tab open.


Fallout from latest nixpkgs updates

Broken packages:

[ ] chemps2
[ ] dirac
[ ] molden
[ ] qmcpack
[ ] cp2k
[ ] meep
[ ] octopus]

CP2K, meep, octopus and molden build without errors on nixpkgs/master. For those I think we can just wait some time? Or do they break by something we are doing here?

There is also some error with the optStdenv, which complains upon an update to a more recent nixpkgs version, that NIX_CFLAGS_COMPILE is set.
phillip@rlyeh:~/Dokumente/Git/NixOS-QChem$ nix build .#cp2k
warning: Git tree '/home/phillip/Dokumente/Git/NixOS-QChem' is dirty
warning: Using saved setting for 'extra-substituters = https://nix-qchem.cachix.org' from ~/.local/share/nix/trusted-settings.json.
error: The ‘env’ attribute set cannot contain any attributes passed to derivation. The following attributes are overlapping: NIX_CFLAGS_COMPILE
(use '--show-trace' to show detailed location information)

The HDF5 related bugs can be fixed with the following patch (need to open an upstream PR for this).
diff --git a/pkgs/tools/misc/hdf5/default.nix b/pkgs/tools/misc/hdf5/default.nix
index f32fba46d55..767a545e1ee 100644
--- a/pkgs/tools/misc/hdf5/default.nix
+++ b/pkgs/tools/misc/hdf5/default.nix
@@ -91,6 +91,15 @@ stdenv.mkDerivation rec {
     moveToOutput 'bin/h5pcc' "''${!outputDev}"
   '';

+  postFixup = ''
+    # Remove reference to /build, which get introduced
+    # into AM_CPPFLAGS since 1.14.0
+    for i in h5cc h5c++; do
+      substituteInPlace $dev/bin/$i --replace \
+        '-I/build/hdf5-${version}/src/H5FDsubfiling' ""
+    done
+  '';
+
   passthru.tests = {
     inherit (python3.pkgs) h5py;
   };

The NIX_CFLAGS_COMPILE problem is solved here: https://github.com/Nix-QChem/NixOS-QChem/pull/263

Unfortunately, it is not:
$ nix flake check
warning: Using saved setting for 'extra-substituters = https://nix-qchem.cachix.org' from ~/.local/share/nix/trusted-settings.json.
error: The ‘env’ attribute set cannot contain any attributes passed to derivation. The following attributes are overlapping: NIX_CFLAGS_COMPILE
(use '--show-trace' to show detailed location information)

$ nix build .#cp2k
warning: Using saved setting for 'extra-substituters = https://nix-qchem.cachix.org' from ~/.local/share/nix/trusted-settings.json.
error: The ‘env’ attribute set cannot contain any attributes passed to derivation. The following attributes are overlapping: NIX_CFLAGS_COMPILE
(use '--show-trace' to show detailed location information)

Unfortunately, it is not:

Now we have a strange divergence: nix-build release.nix -A qchem.cp2k works just fine.
Not sure what's going on here.

But can you reproduce with nix flake check? I can confirm that nix-build release.nix works. I would just be surprised if flakes mess with the stdenv :open_mouth:

But can you reproduce with nix flake check? I can confirm that nix-build release.nix works. I would just be surprised if flakes mess with the stdenv open_mouth

Yes, I can reproduce the failure with flakes, but I have no idea why it behaves differently. I will dig into it.

release.nix hides some failures away. https://github.com/Nix-QChem/NixOS-QChem/pull/264 solves the problem now. nix flake check proceeds, but now complains that allow-import-from-derivation is not activated (could be simply enabled in nixConfig).

Completed.


TypeScript declarations issues with v1.52.1

TS defs of the current version of the engine are noticeably worse and less accurate than of the previous version.
Major concern is type inaccuracy and great number of any types used all over. Here are some concrete problems:

ModelComponent asset property should accept Asset values.

/**
* The asset for the model (only applies to models of type 'asset') can also be an asset id.
*
* @type {Asset|number}
*/
set asset(arg: number);

ScriptType methods are defined as properties, causing issues when extending and overriding methods:

TS2425: Class 'ScriptType' defines instance member property 'update', but extended class defines it as instance member function.
TS2425: Class 'ScriptType' defines instance member property 'initialize', but extended class defines it as instance member function.

defs:
update: (dt: number) => any;
initialize: () => any;

also notice return types any where they should be void.

Classes have odd names and aliases:

type Asset$7 = Asset$6;
type AssetRegistry$a = AssetRegistry$c;
type Application$h = Application$7;
type ResourceHandler$g = ResourceHandler$h;

declare class Material$2
...

Material class clone() method is declared to return Material, causing type mismatch when called on subclass such as StandardMaterial. This was not previously an issue.

Most private properties are not declared as private, e.g. Entity class:

readonly sprite: SpriteComponent;
_batchHandle: any;
c: {};
_app: Application$7;
_guid: string;
_destroying: boolean;
_template: boolean;

ContainerHandler methods' attributes are all defined as any, previously defined with correct types.

_getUrlWithoutParams(url: any): any;
_getParser(url: any): any;
load(url: any, callback: any, asset: any): void;
open(url: any, data: any, asset: any): any;
patch(asset: any, assets: any): void;

Callbacks' types are not exported:

type resourceHandlerCallback$1 = (err: string | null, response?: any) => any;

ResourceHandler patch() method is not declared as optional.

TS2339: Property 'stop' does not exist on type 'SoundInstance$1'.

This is great. Thanks for compiling this list @pavle-goloskokovic. I'll be taking a look at fixing all this sometime during this week.

A little update:

The ModelComponent types have been improved: https://github.com/playcanvas/engine/pull/4002
Material#clone actually should return a Material and it's right that you should cast it as appropriate.
Classes have the $ suffixes because of Rollup. But they are aliased to the correct names at the bottom of the playcanvas.d.ts file. I'm considering also including the unbundled type declarations in the NPM package that will not have the aliasing.
The old process for generating playcanvas.d.ts relied on the code explicitly saying what you want included. The new process includes everything and we must explicitly say what's private. This is a pretty massive job and I suspect that we won't fully mark everything that is private on the final release of 1.52.x. But hopefully this won't cause major problems for people.
The SoundInstance and related types have now been improved: https://github.com/playcanvas/engine/pull/4008

TODO:

I'm aware of a problem with ScriptType. I'll investigate.
Yes, ResourceHandler needs fixing.
I'll look into the callbacks.

Material#clone actually should return a Material and it's right that you should cast it as appropriate.

I agree with the above, but consider this example:
const sm = new pc.StandardMaterial();
const clone = sm.clone();

What should be the type of clone constant?

You would do:
const sm = new pc.StandardMaterial();
const clone = sm.clone() as pc.StandardMaterial;

He is pointing at the change introduced here:
https://github.com/playcanvas/engine/commit/130dca17c71b006702662b20568b3e3ffef5ce2c#diff-3d28fa0b12934d0b6f4314eb2637fca0e13c4f2e191ddce393fc8d473c27a06e
StandardMaterial#clone used to return the type from the initial instance, but its "shadowed" by just relying on copy now (in Material#clone).

Yeah, I know. clone now lives on the Material base class. So this really doesn't have anything to do with the switch in how we generate the TS declarations. This is an API change that doesn't impact JS devs. But will require TS devs to update their code.

It still feels wrong to return the unextended type?
Its fixable with JSDoc @template:
const a  = new StandardMaterial();
const b  = a.clone();

Over class StandardMaterial:
@augments Material<StandardMaterial>

Over class Material:
@template T

Material#clone function JSDoc becomes:
    /**
     * Clone a material.
     *
     * @returns {T} A newly cloned material.
     */
    clone() {
        const clone = new this.constructor();
        return clone.copy(this);
    }

And then the typing is on par with what JS is doing here.

You can also consider this:
https://www.typescriptlang.org/docs/handbook/advanced-types.html#polymorphic-this-types

Some more improvements here: https://github.com/playcanvas/engine/pull/4019
That PR removes or makes private some Entity properties/functions. Definitely getting closer to a new, releasable set of types.

ScriptType functions as properties issue fixed: https://github.com/playcanvas/engine/pull/4023
I'm tentatively estimating a couple of days before we can publish 1.52.2.


chore(es-grammars) add fast-glob dep

hoo boy, thought I added this. Must have messed up somewhere.
Anyways, thanks!


Progress width is wrongly calculated when color escape codes are used

Originally from here https://github.com/piotrmurach/tty-progressbar/pull/31.
Currently it seems like color codes increase length further than it should be, which causes some unexpected behavior as described in the pr.
Opening this to track the solution

Released v0.16.0 that fixes this issue. :shipit:


Fix ROI

ROI is used in the status display
This brings back the ROI and fixes the glitch reference in #1258

Concerning ROI,  @glennfu and I submitted updates to darwin within a few minutes of each other.  My update utilized the ROI in the status display,  his removed it completely (valid from his point of view of the code).
this incorporates a fix in mine that takes into account executing the backtester with capital being 0, It no longer errors.


WIP: enable route support for websocket connections

link: #27766

Did we already implement websocket connections in backend? I thought that was still planned.


Fix the build target at Makefile

Hello @sdispater,
This PR fixes the following situation:
$ make build
Building poetry (1.0.0a4)
 - Building sdist
 - Built poetry-1.0.0a4.tar.gz

 - Building wheel
 - Built poetry-1.0.0a4-py2.py3-none-any.whl

[CannotResolveCommandException]
The command "make:release" is not defined.
make: *** [Makefile:30: build] Error 1

Thank you for the amazing tool and the hard work you do!

Thanks!


Fix/274 map issue

[中文版模板 / Chinese template]
🤔 This is a ...

[ ] New feature
[x] Bug fix
[ ] TypeScript definition update
[ ] Bundle size optimization
[ ] Performance optimization
[ ] Enhancement feature
[ ] Refactoring
[ ] Update dependency
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Release
[ ] Site / documentation update
[ ] Demo update
[ ] Workflow
[ ] Other (about what?)

🔗 Related issue link
close #274

🔗 Related PR link

🐞 Bugserver case id

💡 Background and solution

📝 Changelog

Language
Changelog

🇺🇸 English

🇨🇳 Chinese

☑ Self-Check before Merge
⚠ Please check all items below before requesting a reviewing. ⚠

[ ] Doc is updated/provided or not needed
[ ] Demo is updated/provided or not needed
[ ] TypeScript definition is updated/provided or not needed
[ ] Changelog is provided or not needed

🚀 Summary
copilot:summary
🔍 Walkthrough
copilot:walkthrough

Please check the Bug Server case