[BUG]:  ERROR | BaseChat | model response parase faild！can only concatenate str (not "NoneType") to str

Describe the bug
I use the chat excel ,after the "[Product_sample_30_change.csv] Analysis！" finished , when I ask a question such as  " 查看产品名称有哪些" or " 查看Bookeen Notea的产地" , all  answer  starts with a report  error " ERROR!can only concatenate str (not "NoneType") to str 很抱歉"  .
a complete answer such like  " ERROR!can only concatenate str (not "NoneType") to str 很抱歉，我没有足够的信息来回答您的问题。产品名称为“Bender CC613”的产地需要进一步调查和查询。建议您查阅相关产品的官方网站或联系生产厂家查询相关信息"
the log is " 2023-09-01 11:37:12 | INFO | webserver | illegal json processing:
我无法查询Bookeen Notea的产地，因为Bookeen是一家科技公司，而Notea是它的一款电子笔记本应用程序。Bookeen的总部位于中国，但Notea应用程序可能是在中国或其他地方开发的。如果您想了解更多信息，可以查询Bookeen公司的官方网站或联系他们的客户支持部门。
Traceback (most recent call last):
File "/home/zw/DB-GPT-Excel/DB-GPT/pilot/out_parser/base.py", line 137, in __extract_json
temp_json = self.__illegal_json_ends(temp_json)
File "/home/zw/DB-GPT-Excel/DB-GPT/pilot/out_parser/base.py", line 127, in __illegal_json_ends
temp_json = temp_json.replace(illegal_json_end, " }")
AttributeError: 'NoneType' object has no attribute 'replace'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/zw/DB-GPT-Excel/DB-GPT/pilot/scene/base_chat.py", line 197, in nostream_call
self.prompt_template.output_parser.parse_prompt_response(
File "/home/zw/DB-GPT-Excel/DB-GPT/pilot/scene/chat_data/chat_excel/excel_analyze/out_parser.py", line 28, in parse_prompt_response
clean_str = super().parse_prompt_response(model_out_text)
File "/home/zw/DB-GPT-Excel/DB-GPT/pilot/out_parser/base.py", line 195, in parse_prompt_response
cleaned_output = self.__extract_json(cleaned_output)
File "/home/zw/DB-GPT-Excel/DB-GPT/pilot/out_parser/base.py", line 140, in __extract_json
raise ValueError("Failed to find a valid json response！" + temp_json)
TypeError: can only concatenate str (not "NoneType") to str
"

have same question~~~~

我也是同样的错误：
ERROR!can only concatenate str (not "NoneType") to str This is a CSV file containing data for a basketball player. The file has 12 columns and the columns are separated by commas. The columns in this file are: 1. "PlayerID" - A unique identifier for each player. 2. "Name" - The name of the player. 3. "Position" - The position of the player (e.g., "SG", "SF", "PF", etc.). 4. "Height" - The height of the player in inches. 5. "Weight" - The weight of the player in pounds. 6. "TeamID" - The ID of the team the player belongs to. 7. "Score" - The points scored by the player in a game. 8. " rebounds" - The number of rebounds the player got in a game. 9. " assists" - The number of assists the player got in a game. 10. "Turnovers" - The number of turnovers the player got in a game. 11. "Blocks" - The number of blocks the player got in a game. 12. "Steals" - The number of steals the player got in a game. This file appears to be used to keep track of information about basketball players and their performances. The data in this file can be used for various analyses such as determining the most effective players for a team, analyzing player performance over time, and identifying patterns in player statistics.

同样的错误

同样的问题，已经拉取最新的代码

The primary cause of this issue is that the model's capability did not produce the correct JSON format as per the prompt; you can use the ChatGPT model.

@lin-xiaosheng @Sololololo

How to use?


Suggestion: Don't update DOM if setState doesn't notice change and encourage immutable

I know there are some guys changing the state's value directly in the state object, so setState cannot compare the difference.
But I think everybody should use something like seamless-immutable so that they don't directly modify the state, that is horrible and not a good practice in virtual DOM because we will need to update the DOM every time when running setState.
If we force not updating the DOM (or let say don't trigger render) if the state value is not changed in setState, I think people will start noticing this issue, plus it will improve the performance if nothing is actually need to be updated and we are able to know it because all the object and array is immutable.

I don't understand, in what situation you would call setState and don't want to update the DOM?

I set a function called setRootState as I would like to change the state directly in the child components without passing functions with setState
So, I cannot really check the current value of the root state. When I called setRootState, the state value may not be changed
Another situation is the state value is depended on function result, which is unexpected
setState({
  isSomething: getIsSomethingFromSomewhereDynamically()
})

It is annoying to save the result and compare to the current value

since seems no one is interested in it, I just close it


remove license headers and script

thanks @hugotiburtino
probably no need to deploy btw. since it's mostly dx stuff.


HDDS-11095. Generate fixed length string with Robot builtin

What changes were proposed in this pull request?
S3 Robot tests have some test cases using shell function printf to generate fixed length string.
hadoop-ozone/dist/src/main/smoketest/s3/objectcopy.robot
115:    ${custom_metadata_value} =  Execute                    printf 'v%.0s' {1..3000}

hadoop-ozone/dist/src/main/smoketest/s3/objectputget.robot
194:    ${custom_metadata_value} =  Execute                    printf 'v%.0s' {1..3000}
202:    ${long_tag_key} =           Execute                               printf 'v%.0s' {1..129}
205:    ${long_tag_value} =         Execute                               printf 'v%.0s' {1..257}

hadoop-ozone/dist/src/main/smoketest/s3/MultipartUpload.robot
161:    ${custom_metadata_value} =  Execute                               printf 'v%.0s' {1..3000}

This does not work on more recent bash and/or python versions, only a single v is printed.
The problem can be reproduced using the following simplified test script:
*** Settings ***
Library     OperatingSystem
Library     String

*** Test Cases ***
Test Printf 123
    ${rc}               ${output} =    Run And Return Rc And Output           printf 'v%.0s' 1 2 3
    Length Should Be    ${output}      3

Test Printf {}
    ${rc}               ${output} =    Run And Return Rc And Output           printf 'v%.0s' {1..5}
    Length Should Be    ${output}      5

and running:
$ docker run -it --rm \
  -v $(pwd)/test.robot:/test.robot
  python:3.6.8 \
  bash -c 'pip install robotframework==6.1.1 && bash --version && robot --version; robot test.robot'
...
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
...
Robot Framework 6.1.1 (Python 3.6.8 on linux)
...
==============================================================================
Test Printf 123                                                       | PASS |
------------------------------------------------------------------------------
Test Printf {}                                                        | FAIL |
Length of 'v' should be 5 but is 1.

I propose to replace with Generate Random String   N from Robot's String library.
https://issues.apache.org/jira/browse/HDDS-11095
How was this patch tested?
Existing tests:
https://github.com/adoroszlai/ozone/actions/runs/9749872256

Thanks @ivandika3 for the review.


Transform Pose to World frame

Transform the Pose from udfc to world frame

Read up on tf2 library. Need to find out what transforms are already being broadcast

Should be finished


Add minimal "Snapshot" UI affordances

UI for https://github.com/dockstore/dockstore/issues/2569
To implement in the UI, consider the following approach:

The existing "versions" table has edit and delete actions by version, add a "snapshot" or "build" action button that will start the snapshot wizard.
Implement a dialog that allows the Dockstore User to choose to issue a DOI (and change the version being snapshotted).
Display snapshots with a lock icon in the versions table or pulldown to denote a snapshotted version.

There are other features that snapshotting clears the way for, like including packing dependencies and digitally signing workflows and images.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.7
┆Issue Number: DOCK-787

Link the PR

https://github.com/dockstore/dockstore-ui2/pull/736 too

snapshot UI is completed and present on staging.dockstore.org
Found new issue that warrants a new ticket https://github.com/dockstore/dockstore/issues/2762


[bal-tabs] unable to center the tab items

Can you please add the option to center the tab items? For the time being, there is only the possibility to align them to the start or to the end.
where is needed: https://www.figma.com/file/TpLyniy71JAMZhps0qHhVU/Baloise-–-UI-Kit-(Team-Library)?node-id=4008%3A50604

@madaluca please align it to the left


Update to DoorBirdPy 2.0.2

Description:
Update to DoorBirdBy 2.0.2, which uses the new version (0.21) of the DoorBird LAN API.
Pull request in home-assistant.github.io with documentation: home-assistant/home-assistant.github.io#5487
Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

I have tested all of the code locally except the event bus because I can't open the logbook or settings tabs in the frontend. Every tab except home is just a blank page and Chrome logs GET http://<IP_ADDRESS>:8123/undefined 404 (Not Found) to the console. Is this a known issue with the dev branch or did I screw something up with my test instance?

@Klikini Thanks for your contribution! Are you aware of #13994? Could you support @oblogic7? No matter which PR gets merged first one of you has to port the changes unfortunately. :-(

I think their changes are more involved, so their PR should be merged first and then I will manually reapply my changes in a new PR to the new code handling each device.

I deliberately did not make any updates to API calls as part of my PR.  All of my devices are up-to-date on firmware and I did verify that the notification endpoint is still available.  The documentation states that notifications are automatically converted to the new schedule format so the existing approach still works well.  The API calls should be updated in case the notifications endpoint is deprecated in a future release.

@oblogic7 Yes, which is why your PR should merge first. I can reapply my changes to your new code easily once it merges because most of my changes were in the DoorBirdPy library itself.

Please rebase and re-apply your changes! :-)

Moved to #14933


GoRouter observer causes exception

while adding
observers: <NavigatorObserver>[NewRelicNavigationObserver()],
to the go_router in my project :
an exception while navigation to one of my screens
:
package:flutter/src/widgets/navigator.dart': Failed assertion: line 2993 pos 18: '!navigator._debugLocked': is not true.
any help with this issue
═══════ Exception caught by widgets library ═══════════════════════════════════
The following NoSuchMethodError was thrown building InheritedGoRouter(goRouter: Instance of 'GoRouter'):
Class 'RouteSettings' has no instance getter 'key'.
Receiver: Instance of 'RouteSettings'
Tried calling: key
The relevant error-causing widget was:
MaterialApp MaterialApp:file:///Users/mohammedadelalisorour/Documents/My%20%20Work/Flutter/sevenSquare/the_laundry_hub/lib/app.dart:30:30
When the exception was thrown, this was the stack:
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:38:5)
object_patch.dart:38
#1      NewRelicNavigationObserver._addGoRouterBreadcrumb (package:newrelic_mobile/newrelic_navigation_observer.dart:83:30)
newrelic_navigation_observer.dart:83
#2      NewRelicNavigationObserver.didPush (package:newrelic_mobile/newrelic_navigation_observer.dart:45:9)
newrelic_navigation_observer.dart:45
#3      _NavigatorPushObservation.notify (package:flutter/src/widgets/navigator.dart:3338:14)
navigator.dart:3338
#4      List.forEach (dart:core-patch/growable_array.dart:416:8)
growable_array.dart:416
#5      NavigatorState._flushObserverNotifications (package:flutter/src/widgets/navigator.dart:4333:27)
navigator.dart:4333
#6      NavigatorState._flushHistoryUpdates (package:flutter/src/widgets/navigator.dart:4295:5)
navigator.dart:4295
#7      NavigatorState._updatePages (package:flutter/src/widgets/navigator.dart:4161:5)
navigator.dart:4161
#8      NavigatorState.didUpdateWidget (package:flutter/src/widgets/navigator.dart:3803:7)
navigator.dart:3803
#9      StatefulElement.update (package:flutter/src/widgets/framework.dart:5643:55)
.....
..
..
════════ Exception caught by Flutter framework ═════════════════════════════════
'package:flutter/src/widgets/navigator.dart': Failed assertion: line 2993 pos 18: '!navigator._debugLocked': is not true.
════════════════════════════════════════════════════════════════════════════════
D/newrelic(23857): PayloadController: 0ms. waiting to submit payload [8d20ef85-ac51-4a28-b6aa-c8093ea521dd].
D/newrelic(23857): HarvestTimer: time since last tick: 59997
D/newrelic(23857): Harvest: tick
D/newrelic(23857): Harvester state: CONNECTED
I/newrelic(23857): Harvester: connected
I/newrelic(23857): Harvester: Sending [8] HTTP transactions.
I/newrelic(23857): Harvester: Sending [0] activity traces.
I/newrelic(23857): Harvester: Sending [0] session attributes.
I/newrelic(23857): Harvester: Sending [0] analytics events.

when i remove the observer everything is working fine

@mohadel92 are you still seeing this issue?

@mohadel92 can you check this https://github.com/flutter/flutter/issues/108544?

same problem

Not the OP, but we're seeing a similar issue with using go_router for a modal bottom sheet.
When you use showModalBottomSheet, it can potentially push a route to the Navigator where the settings do not have a route path or name. For us, we're using showModalBottomSheet to pop up a widget, then when the user presses a button on that widget, we navigate to another page.
I believe the difference between Navigator and go_router when NewRelicNavigationObserver intercepts the route is that the Navigator path expects RouteSettings while the go_router path expects a widget.

@duraz0rz that's good feedback, i will check it from our side.

To add a bit more to this, we figured out a workaround on our end.
The docs for showBottomModalSheet state that you can pass routeSettings for NavigationObservers:

The optional settings parameter sets the RouteSettings of the modal bottom sheet sheet. This is particularly useful in the case that a user wants to observe PopupRoutes within a NavigatorObserver.

We didn't have this set when we were using Navigator and NewRelicNavigationObserver was not crashing, while it was crashing until we set routeSettings for a bottom sheet modal when we switched to go_router.

@duraz0rz @bernardoveras @mohadel92  can you check this in our latest flutter release?

@eugenio-tesio-ueno can you share example app or code snippet for this issue?

Hello @ndesai-newrelic , I hope you are feeling well.
This actually works for me by changing the child and key parameter that by default it does not bring in the routesettings.

you know why you are looking for a child or key?.
It seems that the ModalBottomSheets use by default the RouteSettings class that has flutter with only the name, arguments property.

@MiguelBelotto00 you are right, we need to look for name instead of key, can you create PR for this?

Yes, for sure I prepare the pr of this

@eugenio-tesio-ueno can you share example app or code snippet for this issue?

Miguel will provide the error found https://github.com/newrelic/newrelic-flutter-agent/issues/68#issuecomment-2059466094

@MiguelBelotto00 that's right, you can remove the method, now we are reading it from the name so we dont need different method.

Hey @MiguelBelotto00, it seems like route.child is providing the same value as name when passed. If you have any alternative suggestions, feel free to open a PR, and we'll review it.

If you took _addGoRouterBreadcrumb and cast fromRoute and toRoute as RouteSettings, you'll get a syntax error, like this:

The workaround is to copy the NewRelicNavigationObserver and create your own observer. So I guess this issue isn't critical

@eugenio-tesio-ueno why are you casting this as route settings for from route and to route?

@eugenio-tesio-ueno why are you casting this as route settings for from route and to route?

To convert the dynamic fromRoute variable to RouteSettings, (previously validated by the if condition) and to show you that key property does not exists.


Publish stored messages using Enumerator

When using the MqttManagedClient, the function LoadQueuedMessagesAsync retrieves all data from the user, and when we have a large amount of data, we can issue a high memory consumption.
This PR removes adding loaded data into queue and sends it just before starting publishing new data.

@dotnet-policy-service agree

@dotnet-policy-service agree


[FLINK-1295][FLINK-883] Allow to deploy 'job only' YARN cluster. Add tests to YARN

users can now also deploy Flink on YARN for executing a single job.
the flink-yarn project has been moved out of the flink-addons module
the MiniYARNCluster is used for testing Flink on YARN
There is now a (undocumented) Java interface Flink's YARN client, allowing users to manually control the YARN session.
ALL ports used by Flink when running on YARN are automatically determined. In the past users reported problems with blocked ports (YARN is telling the client the RPC address of the application master)
The checks before deployment have been improved to give better error messages if the user is requesting too many resources for a YARN session

The change has been tested on google compute cloud ("click to deploy" with google cloud storage, not hdfs) and amazon emr (hdfs).

 I like that there is a much better test coverage for the Yarn cluster now.
@rmetzger Can you comment on a few open questions?

There are two projects for yarn: "flink-yarn" and "flink-yarn-tests". Can we combine them in one project? The reason why we put the tests in "flink-scala" into a different project was only beause the Scala macros uses in "flink-scala" caused problems otherwise. Since the Yarn project is not using macros, I see no reason for the separation.

The example for the YARN session should probably not refer to a local file ("file:///...")

There is a bit of a strange mechanism in computing the ports for the application master (base port plus attempt-id or so). Can this be simplified? Also, what happens if that port is already in use, per chance?

How hard would it be to make the client parameter that starts a yarn session for the job simpler? Something like -y rather than -m yarn-cluser?

Thank you for the feedback. I'll address the inline comments.
Regarding the questions:

The separation between flink-yarn and flink-yarn-tests exists because the flink-yarn-tests expect the flink-dist package to be build before the flink-yarn-tests package.
The tests are really starting a YARN cluster and deploying a flink fat-jar to it. Therefore, we need to run flink-dist first. I asked on the maven mailing list if there is a way of simplifying this and it seems to be possible to store the archetype descriptors (used to build the fat-jar) in a separate maven module which is then accessed by flink-dist and a prepare-tests phase of flink-yarn. But for that approach, we would need to create an additional maven module (something like flink-assemblies for making the assembly descriptor independent of the flink-dist package).

tl;dr maven is not flexible enough for a better solution.
2. Yep. That doesn't make much sense (I used a local yarn cluster for testing it .. thats why I didn't really stumble across it). I'll fix it.
3. This is true for the old YARN client (before this pull request). As you can see here: https://github.com/apache/flink/pull/292/files#diff-37b2363833862d636afea47fab39a694L269 I removed the code that was computing the port. This new YARN client is allocating ALL ports dynamically (web frontend, RPC). I'm using YARN to transfer the RPC port of the AM to the client.
4. Probably not hard. Its a matter of taste I guess. I think my approach is more flexible (imagine we want to have a -m mesos-cluster or a -m flink-local at some point). Also, we would need to throw an exception if a user is setting something like -j -m myCluster:6123. It would be good to get some more opinions here.

As far as I can tell without running tests on the cluster it looks good to me. Only some minor remarks as in-code comments.

Thank you for reviewing the code. I hope I have time tomorrow to address all remarks.

Thank you for reviewing the pull request. I'll merge it now.


Create a Schema Manager to avoid huge loading infering database information

WHY
BEFORE - What was wrong? What was happening before this PR?
All started in https://github.com/Laravel-Backpack/CRUD/issues/4618 when a user reported HUGE loading times for CRUDS.
At that time I was not able to reproduce the issue, but a few days ago that SAME issue starting hunting me.
I have a suspect that is dbal that introduced this since I didn't change nothing in the development environment apart from updating packages.
Testing around the stuff it seems that it's a problem in mysql 5.7 atleast, and affect MariaDB users too (since it was branched from mysql 5.x). Upgrading to mysql 8 solved the issue instantaneously.
AFTER - What is happening after this PR?
We hold the database schema on the SchemaManager and all subsquent calls are made to this object instead of the db directly.
mysql 5.7 without this branch

mysql 5.7 with this branch

mysql 8 with this branch

mysql 8 without this branch

Is it a breaking change?
I tried to make it non breakable ... in the next major all crud and model methods should be moved to the manager and probably create adapters for each db engine we would like to support.

@realtebo This is the solution me and @tabacitu came up after finding the problem for the huge loading times you reported in #4618
If you have time and don't mind, would you give this branch a test to see if it fixes the issues you reported ?
Cheers

Yup - @realtebo or anybody else who can test this. Let us know if everything works ok after doing:
composer require backpack/crud:"dev-hold-the-schema as 5.3.99"

If so, we'll merge and tag this, and then you can do composer require backpack/crud:"^5.3" again, to get the official, launched version.

I am actually away from home and from work. And so o am happily away from pc.. I will try you works in a week . Thanks in advance

I am actually away from home and from work. And so o am happily away from pc.. I will try you works in a week . Thanks in advance

I wish you an happy vacations.
We spend alot of time in computer, spending 1/2 weeks away is a bless! :pray:
I really wish we could work for 2 weeks and do what we like to do for the next two.
If you like to code, so be it, but it's what you like to do, not mandated, so watching birds is what you like ? Do it.
We shouldn't commit so much time from our lifes to work, it's counter "living"!
See you next week :tropical_drink:
Cheers

I only have one question for you here @pxpm
Other than that, I'm very VERY happy with this. If @jorgetwgroup gave it a test too and we have his thumbs up... I'm ready to merge it. I love it ❤ So clean!

(or maybe @munjaldevelopment is a better tester for this, since he was using MariaDB anyway? you decide please @pxpm 🙏)

@tabacitu all fixed.
Problem was that in testing we use the same connection to test regular tables and tables with prefix.
Since I didn't separate that tests when I wrote them, the schema for the testing connection was generated before the prefixed tables were created, and it would not regenerate (as expected).
I thought about moving the prefixed database tests to other testing environment, but decided to "fix" it in DatabaseSchema. Basically it now checks the connection as before, but if the connection already has a schema it tries to get only the specific table.
So even if you are creating tables during the app lifecycle (tenants or something like) we make sure we get the tables after the schema was generated.
Please allow the tests to run in this branch so we are sure everything is working fine!
2 beers can't hold me back! muhahahaha 🙃  !
Cheers

Sorry for VEEERY late reply.
I can confirm that upgrading mysql from 5.7 to 8 fix EVERY AND EACH slowness problem.

@tabacitu moved the files, applied your suggestions, let me know if was something like that you had in mind.
Cheers

Update: found a big bug - https://github.com/Laravel-Backpack/CRUD/issues/4704


[Bug]: Module not found: Can't resolve <entry_path> in Docker

System Info
System:
OS: macOS 15.1
CPU: (8) arm64 Apple M1 Pro
Memory: 262.28 MB / 32.00 GB
Shell: 5.9 - /opt/homebrew/opt/zsh/bin/zsh
Binaries:
Node: 20.11.0 - ~/.local/state/fnm_multishells/44569_1731538780778/bin/node
npm: 10.2.4 - ~/.local/state/fnm_multishells/44569_1731538780778/bin/npm
Browsers:
Chrome: 130.0.6723.117
Safari: 18.1
npmPackages:
@rspack/cli: 1.1.1 => 1.1.1
@rspack/core: 1.1.1 => 1.1.1
Details
As of v1.1.1, rspack does not successfully build in Docker containers. This bug is not present in rspack v1.1.0, or when installing directly on the host machine.
Reproduce link
https://github.com/mxmason/rspack-repro-docker
Reproduce Steps

Clone the example repo
Start a docker daemon
docker build . -f Dockerfile-rspack -t rspack-image
Observe the error below

ERROR in × Module not found: Can't resolve './src/index' in '/app'
help: Found module './src/index.js'. However, it's not possible to request this module without the extension
      if its extension was not listed in the `resolve.extensions`. Here're some possible solutions:

      1. add the extension `".js"` to `resolve.extensions` in your rspack configuration
      2. use './src/index.js' instead of './src/index'

ERROR in ×   Error: Child compilation failed:
│     × Module not found: Can't resolve '/app/node_modules/html-webpack-plugin/def  ault_index.ejs' in '/app'
│
│   - child-compiler.js:211
│     [app]/[html-webpack-plugin]/lib/child-compiler.js:211:18
│
│   - index.js:13364 finalCallback
│     [app]/[@rspack]/core/dist/index.js:13364:9
│
│   - index.js:13386
│     [app]/[@rspack]/core/dist/index.js:13386:14
│
│   - index.js:13488
│     [app]/[@rspack]/core/dist/index.js:13488:18
│
│   - index.js:473 done
│     [app]/[@rspack]/lite-tapable/dist/index.js:473:13
│
│   - index.js:480 AsyncSeriesHook.callAsyncStageRange
│     [app]/[@rspack]/lite-tapable/dist/index.js:480:20
│
│   - index.js:82 AsyncSeriesHook.callAsync
│     [app]/[@rspack]/lite-tapable/dist/index.js:82:21
│
│   - index.js:13484
│     [app]/[@rspack]/core/dist/index.js:13484:33
│
│   - index.js:13528
│     [app]/[@rspack]/core/dist/index.js:13528:37

Compare to building directly on the host machine, which works fine:
npm ci
npm run build:rspack

Builds in Docker also work in v1.1.0. To demonstrate, downgrade the rspack binaries and try to build the Docker image again:
npm i -DE<EMAIL_ADDRESS><EMAIL_ADDRESS>docker build . -f Dockerfile-rspack -t rspack-image

The same issue is occurring on Cloudflare Pages. Although I haven’t changed the code, after updating rspack from v1.1.0 to v1.1.1, a "module not found" error started appearing. Building locally works without any issues.

We have a similar issue with @rsbuild/core: 1.1.1 also, probably related?

Running into a similar problem with Docusaurus. However, Docusaurus is only dependent on<EMAIL_ADDRESS>Instead, I have to explicitly resolve<EMAIL_ADDRESS>

same for me  Rolling back to @rsbuild/core: 1.0.19 solve issue

Works for linux-x64-gnu, but fails for linux-x64-musl. That is, using an node:18-alpine image which uses musl fails, but if I use node:18-bullseye which uses gnu, it works fine.
If I may believe my yarn.lock, these are the possible different bindings:
  optionalDependencies:
    "@rspack/binding-darwin-arm64" "1.0.14"
    "@rspack/binding-darwin-x64" "1.0.14"
    "@rspack/binding-linux-arm64-gnu" "1.0.14"
    "@rspack/binding-linux-arm64-musl" "1.0.14"
    "@rspack/binding-linux-x64-gnu" "1.0.14"
    "@rspack/binding-linux-x64-musl" "1.0.14"
    "@rspack/binding-win32-arm64-msvc" "1.0.14"
    "@rspack/binding-win32-ia32-msvc" "1.0.14"
    "@rspack/binding-win32-x64-msvc" "1.0.14"

we are using node:20.11.1-alpine3.18 and its failing

Pin @rspack/core to 1.1.0 should fix this.
For example, use pnpm overrides:
// package.json
{
  "pnpm": {
    "overrides": {
      "@rspack/core": "1.1.0"
    }
  }
}

for us it's a problem with "tsconfig.json". Rspack do not see this file at all in docker with node:20.5.0-alpine to node:23.1.0-alpine. changing location of a file in docker container does not resolve the issue.

Fixed in Rspack v1.1.2


Still get fp32 wrapper error

Describe the bug
Steps:  33% 500/1500 [09:06<17:56,  1.08s/it, loss=0.286, lr=1e-6]Traceback (most recent call last):
  File "train_dreambooth.py", line 822, in <module>
    main(args)
  File "train_dreambooth.py", line 805, in main
    save_weights(global_step)
  File "train_dreambooth.py", line 682, in save_weights
    text_enc_model = accelerator.unwrap_model(text_encoder, keep_fp32_wrapper=True)

Reproduction
Train and save part way.
Logs
No response
System Info

diffusers version: 0.9.0
Platform: Linux-5.10.147+-x86_64-with-glibc2.27
Python version: 3.8.16
PyTorch version (GPU?): 1.13.0+cu116 (True)
Huggingface_hub version: 0.11.1
Transformers version: 4.25.1
Using GPU in script?:
Using distributed or parallel set-up in script?:

Can confirm that as per @ShivamShrirao's response in #180, you just need to update accelerate.
Change %pip install -q accelerate==0.12.0 transformers ftfy bitsandbytes gradio natsort
to %pip install -q accelerate transformers ftfy bitsandbytes gradio natsort

so what should it be ? bitsandbytes or bitsandbytes 35? im getting crap results still , half hour ago

Not sure if related but now get this error
RuntimeError: Detected that PyTorch and torchvision were compiled with different CUDA versions. PyTorch has CUDA Version=11.7 and torchvision has CUDA Version=11.6. Please reinstall the torchvision that matches your PyTorch install.

@G-force78 fixed in 8b1472ffd0c8e0144f9db797e545eb908a1831b9


feat: Add token auth to GitLab/GitHub hosting providers

Description
This PR adds an optional "token" argument to the gitlab() and github() code hosting provider. This allows for the usage of modules stored in private repositories.
QC

[x] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[x] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

Closes #1301

@johanneskoester seems like conda env files are still fetched without the token. I've tested hardcoding it in the conda deployment file [1] and it works. Any pointers on the best way to make the token available there?
[1] https://github.com/tdido/snakemake/blob/435913d63cc42ac7b9e0cf438673e339aa25d055/snakemake/deployment/conda.py#L843

A cli arg for the token is not an option IMHO, because then the token will be inside of the bash history, which is a security risk. Can you explain what exactly fails when just fetching the token from os.environ?

Right, yes, that makes sense. The failure I was referring to was the one when adding the argument to the gitlab() function, where it doesn't pass the token to the conda environments it fetches.
I'll change the cli arg to os.environ instead, should be straightforward.

@johanneskoester I've switched to using an env variable for the token and it seems to be working fine. Please let me know whether the implementation looks OK.

Can you please run black on your changes?


Springs.Filter.ByCategoryName also returns Tags

The Springs.Filter.ByCategoryName node returns both the Category passed and the Tags associated with that Category. It looks like the filter function acts as a wildcard, not as an exact match

Hi,
Yes, that's the intended use. I wanted to keep it more generic, so the node takes a list of strings and checks for partial matches. To get just the rooms, you have two options:

I did not know about the plural. Thanks for the tip!
Does that work with all categories?
Here's what I had done. But now that you mention it, that would not have excluded the RS lines


Marker title does not appear on hover

Hi.i am facing this issue where marker title is not being appearing on hover on the map when map gets generated. Following is my code
`df = pd.read_csv('file.csv')
gmap = gmplot.GoogleMapPlotter((df['lat'].min() + df['lat'].max()) / 2.0,
(df['lng'].min() + df['lng'].max()) / 2.0, 14,
apikey='xxxxxxx')
for index, row in df.iterrows():
gmap.marker(row['lat'], row['lng'], color='red', title=row['mnemonic'])`
Interestingly if my csv file contains row >=255,the title do gets appear on mouse hover.But on larger dataset the title does not appear.
thanks

@Abdur91 if you look at the raw HTML, do those markers that don't display a title actually have their title field set to some string?
You should see something like this for every marker:
new google.maps.Marker({
    title: ..., // <-- should have a string
    icon: ...,
    position: ...,
    map: map
});

(Note to self: Might be related to #117)

thanks for your reply .yes my title value is a string value,but still title appears only for 256 rows.greater than 256 rows it does not.
As you have referred issue 117.i am quite sure its related to that

i need a fix to this as early as possible
thanks

I was never able to reproduce this on my end with sample data - if it's not sensitive info, could you attach the .csv file (or something similar with fake data) here? And attaching your output HTML file (without your API key) here would help too.

As with #117, I'll be closing this for now since I still can't reproduce this.
If it happens again, feel free to post a code snippet or traceback and I can reopen this.


Configure image attributes using ImageLoaderSettings

Objective

Fixes #11200

Solution
I added some of the TextureDescriptor fields to the ImageLoaderSettings struct.
They are optional and can be used to overwrite the default values/values defined by the ImageFormat.
I did not add all fields (label, size, etc.). Also, the wgpu types are not serializable and deserialized, so I am skipping them.

Changelog
Added optional  sample_count, dimension, texture_format, and usage fields to the ImageLoaderSettings.

without breaking existing code

Unfortunately adding elements to struct without the #[non_exhaustive] tag is considered a breaking change.
I'm not sure how Bevy handles "temporary" pull requests and stuff, so I have no idea if this is a good idea.

Sure it's technically not none-breaking, but I expect for the most caeses, where ImageLoaderSettings is constructed, only some fields are set and the rest are overwritten with default anyway.

I think you should enable (de)serialization for the types, and not skip serde so that it would work directly with .meta files.
I would also prefer that you pass the values to Image::from_buffer, same as the other settings.

Maybe we should wait until .meta files are finished. Then we could add [insert what .meta files are parsed into here ] as a parameter to ImageLoaderSettings?

Not sure what you mean? .meta files are finished, and what they are parsing is ImageLoaderSettings.

I think you should enable (de)serialization for the types, and not skip serde so that it would work directly with .meta files.

IIRC this is a pretty big lever to pull / enables a lot of stuff on the wgpu side.

Not sure what you mean? .meta files are finished, and what they are parsing is ImageLoaderSettings.

Yup meta files "work" today and they are driven by serde. As a general rule, settings should be serializable.
The general strategy for ImageLoaderSettings has been to define a new backend-agnostic Image settings API that is serializable. See ImageSamplerDescriptor for an example of the pattern.

Thank you for your input.
So ideally, we can configure all of the attributes of an image using the ImageLoaderSettings, and by extension also in a .meta file.
To make this work, we would have to either implement and enable serde for all wgpu texture types, which is not desired, or we would have to copy them and maintain a mirrored version.
This encompasses the following types:
wgpu::Label => WgpuLabel (Option<&str> should be easy)
wgpu::Extent3d => ImageExtend3D (Image prefix or Wgpu prefix?)
wgpu::TextureDimension => ImageDimension (straight-forward only 3 enum variants)
wgpu::TextureFormat => ImageFormat (image format already exists and refers to the image encoding, so we would have to rename one of them, also this enum has very many variants, which makes mirroring them very verbose).
wgpu::TextureUsages => ImageUsages (how do we handle bitfield serialization? a simple u32? this would not be very readable)
Additionally, we might also like to mirror TextureViewDescriptor and TextureAspect.
If we were to mirror all of these types, it would be a logical next step, to flatten the Image type to look somewhat like this:
//old:
pub struct Image {
    pub data: Vec<u8>,
    // TODO: this nesting makes accessing Image metadata verbose. Either flatten out the descriptor or add accessors
    pub texture_descriptor: wgpu::TextureDescriptor<'static>,
    pub sampler: ImageSampler,
    pub texture_view_descriptor: Option<TextureViewDescriptor<'static>>,
    pub asset_usage: RenderAssetUsages,
}

//new:
pub struct Image {
    pub data: Vec<u8>,
    pub label: ImageLabel,
    pub size: ImageExtent3d,
    pub mip_level_count: u32,
    pub sample_count: u32,
    pub dimension: ImageDimension,
    pub format: ImageFormat,
    pub usage: ImageUsages,
    pub view_formats: Vec<ImageFormat>,
    pub sampler: ImageSampler,
    pub texture_view_descriptor: Option<TextureViewDescriptor<'static>>, // rework this as well
    pub asset_usage: RenderAssetUsages,
}

Since implementing (de)serialization for all texture types is not trivial, I would debate, that it might be beneficial to merge this PR as is, since this change already improves our API for loading images.
Additionally, I would create a new issue detailing how we can get this functionality to work with .meta files, as well as, how we can use these newly mirrored types, to improve/flatten our image abstraction.
What do you think? @mockersf @cart

If we were to mirror all of these types, it would be a logical next step, to flatten the Image type to look somewhat like this:

For now I think it probably makes sense to keep the TextureDescriptor model (aka ImageDescriptor):

It reduces boilerplate:

It allows us to share the type / its fields across both ImageLoaderSettings and Image
It allows us to implement a single From<ImageDescriptor> for TextureDescriptor<'static> and use it anywhere we need to use an ImageDescriptor

It makes it easier to conceptualize the Image / wgpu::Texture connection.

Since implementing (de)serialization for all texture types is not trivial, I would debate, that it might be beneficial to merge this PR as is, since this change already improves our API for loading images.

I would prefer to hold the line on "loader settings must be serializable". I don't think the mirroring has many unknowns / we should be able to merge it relatively quickly. And that way we don't break anyone by rolling out two versions of the api back-to-back across releases.

Additionally, I would create a new issue detailing how we can get this functionality to work with .meta files, as well as, how we can use these newly mirrored types, to improve/flatten our image abstraction.

I'm down for that.

Or alternatively we could embrace ImageLoaderSettings as the ImageDescriptor and store that on Image?

can we please have this

I agree that this is necessary, but its worth doing this in a new PR introducing mirrored configuration API.


setting relations using the relation_id generated by django in field_values

I noticed today that this doesn't work. Nasty, because my tests now failed randomly, which was hard to debug. Is this something that can be fixed?

Can you throw in a little example code as it's a little hard to guess what you mean by the subject :)

Sorry, was in a hurry ;-)
In the following snippet I used to have 'user_id': liduser.pk instead.
AutoFixture(Profiel, field_values={
    'voornaam': 'LID',
    'status': Profiel.STATUS.LID,
    'user': liduser,
}).create(1)

Which I expected to work because that's how django deals with relations usually.

Seems valid. What is the benefit for you to use user_id over user? What happens if you set an integer to the user field? Does that work?
I see the problem you have. But I probably won't get around to fix it soonish. Would you be interested in working on a fix for this?

Setting an integer to the user field is invalid in Django. The benefit is mostly that if you don't have a whole instance, you can still set the related value (without incurring extra costs for getting the instance).
The problem is not that I really want to use this feature though, it's more that it fails very silently and is thus hard to debug. Making it fail obviously by throwing some error would already be a big improvement.


Any non-ASCII characters comes with an extra space when typed

Describe the bug
Any non-ASCII characters comes with an extra space when typed
To Reproduce
Steps to reproduce the behavior:

Type an non-ASCII character, like ä.

Expected behavior
It's ä instead of ä .
Desktop (please complete the following information):

OS: Arch Linux

Yeah, that is a side effect of using the old user input system, I am in the process of porting all of the user input fields to the new system (used in the card description field for eg when viewing a card) + a little bit of rewrite so it's taking a little while. Should be out soon. Please let me know if that is happening in the card description as well. It does not happen for me


CodeFix for missing import should take into acount @types

I do not repro though on my machine:

Can you post a sample code? Thanks

Sure, here is the the sample: https://github.com/wallverb/test
Clone, npm install and I get this:

Looks like it might be related to "baseUrl": "." in tsconfig.json

I feel like you need to change this to
            "*": [
                "node_modules/@types/*"
                "node_modules/*"
            ]

or just omit the entire "*" field if you're using "moduleResolution": "node"

@DanielRosenwasser - Thanks - first suggestion does the trick
If I omit entire '*' field with "moduleResultion": "node" then I get this:

Looks like there's an issue when it comes to using path mapping. Thanks!


[libiconv] Update to 1.16

Signed-off-by: Steven Marshall<EMAIL_ADDRESS>

closing in vavor of #7


Resolve day-1 experience related bugs - Misc

[ ] Bug 7299679: Add guidance to "Deploy a Spring Boot JAR file Web App to Azure App Service on Linux" on 404 issue
[ ] Bug 7114479: Failed to instantiate [com.microsoft.azure.spring.cloud.autoconfigure.telemetry.TelemetrySender

Closing this one.


Edits to examples doc

Some minor but fairly widespread edits to the docs for the "simple" example. Please feel free to take or leave any of them.
A note on British vs. American spelling: I don't have a preference, but I chose "-ize" over "-ise" for the docs because it matches keywords in the code.

Not sure how this got duplicated; closing it.


Leptos 0.6.5

I updated the dependencies and it seems to just work with leptos 0.6.5 and axum 0.74
I also changed the example in the readme. The previous version did not work but this does. I do not know why.

Maybe better use the other pull request. Seems more complete.

Thanks @florianfelix ! I've merged https://github.com/tqwewe/leptos_server_signal/pull/13


All Your Haags Belong to Us

New Analytics

Windows Possible Credential Dumping

Resolving #1744 .

Updated Analytics

PowerShell - Connect To Internet With Hidden Window (renamed)

Resolving #1899.

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Windows Possible Credential Dumping :x:

diskUsage: 184320
runDuration: 4.704s
scanCount: 6441

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Windows Possible Credential Dumping :x:

diskUsage: 180224
runDuration: 26.393s
scanCount: 0


The all verification has been failed using zksolc 1.4.0

🐛 Bug Report for hardaht-zksync plugins
When I deploy some contracts with verification, the contract has been deployed successfully, but verification failed.
I never seen this error before I was using older zksolc versions.
@m-ikowit contracts % npx hardhat deploy-zksync --script deploy.ts --network zkSyncSepoliaTestnet

Starting deployment process of "TestERC20"...
Estimated deployment cost: 0.0001551017 ETH

"TestERC20" was successfully deployed:
 - Contract address: 0xe1eCC6FD2dfD612BE600d3b5258C1dCc8e681533
 - Contract source: src/zksync-deploy/TestERC20.sol:TestERC20
 - Encoded constructor arguments: 0x00000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000000954657374546f6b656e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000025454000000000000000000000000000000000000000000000000000000000000

Requesting contract verification...
Your verification ID is: 5132
Error in plugin @matterlabs/hardhat-zksync-verify: Backend verification error: Deployed bytecode is not equal to generated one from given source

Network configuration is here:
networks: {
    zkSyncSepoliaTestnet: {
      url: "https://zksync-era-sepolia.blockpi.network/v1/rpc/public",
      ethNetwork: "sepolia",
      zksync: true,
      verifyURL: "https://explorer.sepolia.era.zksync.dev/contract_verification",
    },
}

💥 Plugin name
@matterlabs/hardhat-zksync-verify
📝 Description
Provide a clear and concise description of the bug.
🔄 Reproduction Steps

Run npx hardhat deploy-zksync

🤔 Expected Behavior
Describe what you expected to happen.
😯 Current Behavior
Describe what actually happened.
🖥 Environment
zksolc: 1.4.0
📋 Additional Context
Add any other context about the problem here. If applicable, add screenshots to help explain.
📎 Log Output
Paste any relevant log output here.

We are in the process of fixing the issue. Issue appeared at verify BE. In the meantime, adjust your Hardhat configuration to support either Solidity version 0.8.19 or switch zksolc version to 1.3.23 as a temporary solution.

Apparently this is now fixed with 1.4.0 being available at backend


Eval is not the best practice and it may lead to errors

Hi!
I'm working on Electron application and it uses svg.js and svg.select.js libs. The Electron documentation advises to disable or override eval. So the app has content-security-policy metatag that disables eval. It lead to errors in svg.select.js lib, because it uses eval.
Do you have any plans to change it? Thanks!

I was about to say that this will not change but then I reviewed the code and I wonder why I didnt see that in the review of the PR. The code can be easily rewritten to:
this.pointCoord = function (setting, object) {
  return typeof setting !== 'string' ? setting : object[setting]
}

feel free to create a PR to fix it :)

@Fuzzyma the solution will be a bit harder, because there are such expressions as 'width / 2' that should be evaluated. I already have an idea and I will create a PR

True - jeah ok then there was a reason that was done as it is :D. But when you have a neat idea - go ahead :)


shasum doesn't match

echo -n ZapDesktop-darwin-v0.2.2-beta.dmg | openssl dgst -binary -sha512 | base64
F0sxZmk6c/sCq/FHvqh68lh1CJ6CDf9yzwPeMTMUQfSrj+kHYovrdNheYmieF7HcmD2aHznvF7qEvNYPD5tvHA==
should be 4SBbTGH78z1ml4ZAetI4VnSMlzUq/zijVeI8YvSbEI1cB0IodofdSJJzNVFaozFwW9aNvP+e/xdD7eUqh5QVOQ== according to latest-mac.yml

same problem with macbook dmg 0.2.2 version shasum doesn't match
I'm using shasum -sha256 filepath

@funontheride please see the previous comment for the correct command you must use in order to validate the checksum:
https://github.com/LN-Zap/zap-desktop/issues/826#issuecomment-425700555

Wow you are fast! sorry. I was missing the | 64base and it wouldn't work.
thank you! all this is difficult for me. I have no idea :)
cheers!


Instructions for HTTP application routing does not work for RBAC enabled clusters

Following the instructions for setting up HTTP application routing does not work for RBAC enabled clusters. The necessary RoleBindings and/or ServiceAccounts are missing for the ingress controller and external DNS to work properly.
I get that the functionality and instructions are just to get started quickly, not something fit for production. But enabling RBAC is just a single click in the cluster creation process, and I often want to have RBAC even during experiments to ensure I don't run into those roadblocks later.
Error from pod addon-http-application-routing-nginx-ingress-controller-66gt7h4:
W1013 13:26:28.815432       6 status.go:288] error updating ingress rule: ingresses.networking.k8s.io "aks-helloworld" is forbidden: User "system:serviceaccount:kube-system:addon-http-application-routing-nginx-ingress-serviceaccount" cannot update resource "ingresses/status" in API group "networking.k8s.io" in the namespace "default"

Error from pod addon-http-application-routing-external-dns-65fd9574c4-c6mmc:
time="2021-10-13T13:06:19Z" level=error msg="azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://management.azure.com/subscriptions/[...]/resourceGroups/MC_[...]/providers/Microsoft.Network/dnsZones?api-version=2018-05-01: StatusCode=400 -- Original Error: adal: Refresh request failed. Status Code = '400'. Response body: {\"error\":\"invalid_request\",\"error_description\":\"Identity not found\"}"

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

ID: 51a32f9e-c92f-412b-d460-567f3c542b98
Version Independent ID: fad073ab-a376-1535-7bc4-deaca1d98dd9
Content: HTTP application routing add-on on Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/http-application-routing.md
Service: container-service
GitHub Login: @lachie83
Microsoft Alias: laevenso

@lindhe Thank you for reaching out with your feedback, our team will review and get back to you at the earliest.

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@lindhe, Thanks for the feedback. HTTP application routing is being retired in favor of Web Application Routing, but your point on RBAC-enabled clusters being a common scenario, even in the initial testing stage, is valid. We'll keep this in mind as we consider what kind of scenario-based guidance to add to our Web App Routing content.
#please-close


ThinkPad x280

Model: ThinkPad x280
Patchset: xx70_xx80_patches_v7.txt with all patches (nothig commented out)
TPM: 4C 4E 56 42 42 53 45 43 FB -> 4C 4E 56 42 42 53 45 43 FF
Notes: Do not use fix_vendor_hashes.py, it damages patched bios file and machine becomes unbootable. Just patch and change sequence (above).
TPM stick in "MFG mode".

Thank you for your comment.
Same situation with x240.
I used https://github.com/thrimbor/thinkpad-uefi-sign and it made my laptop unbootable. It even looked like some short circuit or power failure because laptop switched off in a fraction of a second.
everything else works fine. I got whitelist removed.


Update shellcode_hash_search.py

Quick n Dirty Fix for IDA 7.x 64 bit
Issue:
https://github.com/fireeye/flare-ida/issues/76#issue-490390660
https://github.com/fireeye/flare-ida/issues/73#issue-461892003

lgtm
@jhsmith thoughts?

Thanks so much for your contribution, but I'd like to resolve this a little differently in #79. Please try this the new version and let us know if you encounter more issues.


S3 watcher noisy in new regions (like us-east-2)

The newer regions don't provide an ACL name.
We're currently getting null as the ACL name in these regions.
Worse yet, the changewatcher sees a change on every run for buckets in these regions.
To things need to happen:

CloudAux for S3 needs to be updated to stop asking for the ACL name.
Need to investigate why security_monkey is reporting a change when the config dictionary has not been modified.

@mikegrima ^

This should be addressed in https://github.com/Netflix-Skunkworks/cloudaux/pull/22. Further discussion is at: https://github.com/Netflix-Skunkworks/cloudaux/issues/21
Though, we will want to do a bit more to prevent this. My recommendation is to have Grants based entirely on ID's, and to maybe have an ephemeral path that contains a dict of canonical ID's to their corresponding display names.

My suspicion as to the cause of the flipping is based on the bug in CloudAux as such:
The data is stored as a JSON string in the SM database. CloudAux is returning a Python dict which has a Grants that looks like this:
"Grants": {
    None: [
        "FULL_CONTROL"
    ]
},

But, when it translates into a JSON string, it looks like this:
Grants": {
    "null": [
        "FULL_CONTROL"
    ]
},

As such, it will always be different and log the change to the DB.  The fix in https://github.com/Netflix-Skunkworks/cloudaux/pull/22 should resolve that issue for now.

PR #587 mostly addresses this issue. Will submit a new PR to create an ephemeral section with Grants featuring the friendly account names (only applicable for regions that have it).
This will require a slight modification to CloudAux and SM.

Hey @mikegrima  - Is this issue ready to be closed or do we want to keep it open for the next PR.  (Something about an ephemeral section and Grants)


Release new version

We're needing this as well. The current version depends on an old version of httparty that conflicts with other gems in our project. Right now we're pointed at master, which is not ideal.
What's the ETA on a new release?

Any update, @sabman / @kashif?

Any updates?

✅ release pushed 🎉
Thanks for all the work and promoting me


Keybinding request: execute request

Great work! Would it be possible to add a keybinding for executing a request, even when you are working in another file. I'm testing a post using a JSON file. Would really speed up the testing if I can simply edit the JSON file and with a simple key-stroke VSConnect can make the request.

Thanks for the feedback, and sorry for the long delay. I finally got around to adding a command for this. You can add something like this to your keybindings.json:
{"key": "ctrl+shift+/", "command": "vsConnectClient.sendCurrentRequest" }


parse format refs #33

add ability to return a format string.
Also fix a bug introduced with upstream library change.

Codecov Report

Merging #52 into master will decrease coverage by 0.3%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
- Coverage     100%   99.69%   -0.31%
==========================================
  Files           1        1
  Lines         618      650      +32
==========================================
+ Hits          618      648      +30
- Partials        0        2       +2

Impacted Files
Coverage Δ

parseany.go
99.69% <100%> (-0.31%)
:arrow_down:

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 f58c961...d433040. Read the comment docs.


Is R2DBC is going to support multiple hosts or multiple nodes

is R2DBC supporting for DB high availability, means R2DBC is supporting for multiple hosts or multiple nodes ?

Generally, this is subject to drivers as the pool cannot tell the connection mechanism for a driver.


Specifying the starting url path in npm start

I found out how to change the starting path in my app for the production build using the "homepage" setting in the package.json.
"homepage":"http//server-name/MyApp"
For this to work I also had to change my routes (using react-router) to include the subdirectory:
<Route path="/MyApp" components={App}>
This works great in prod but when I run npm start during development, I have to manually add "MyApp" to the url. Is there any way I can set this so it npm start runs the app as follows:
http://localhost:3000/MyApp
Thanks!

We might implement this—see https://github.com/facebookincubator/create-react-app/pull/1887 for work in progress on this.
But until this is done you have a workaround that will work in both development and production:
<Route path={process.env.PUBLIC_URL} components={App}>

The string will be empty in development, and the /MyApp path in production. You can also concatenation it with other routes.
With React Router 4 you can even make this simpler by specifying basename: https://github.com/facebookincubator/create-react-app/pull/2668.


⚠ Digital Ocean - https://status.digitalocean.com/ has degraded performance

In 57a18d5, Digital Ocean - https://status.digitalocean.com/ (https://status.digitalocean.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 151 ms

Resolved: Digital Ocean - https://status.digitalocean.com/ performance has improved in 21e24e7.


Update list of 3.0 features

Removed: property bags and ignore parts of the model
Added: interception

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

ID: 67b660a3-4b81-2f6e-fd19-a2c71e9f3b5b
Version Independent ID: 5552bf61-9cfb-5152-0bc1-903cd4bd417d
Content: New features in EF Core 3.0 - EF Core
Content Source: entity-framework/core/what-is-new/ef-core-3.0/features.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @divega
Microsoft Alias: divega

Closed in #1733.


Update Readme.md

Thanks for this!
It seems there is a typo in README.md . This should fix that!

@Reggino hm, looks like redux api was changed in some version. I'm looking at docs and looks like it should be createStore(reducer, null, storeCreator). I'll try to check older version and fix it. Thanks for PR!


Update LICENSE

@chenrui333 Just thought I'd CC you in to this to let you know that I've changed the license for this repo, following on from your suggestion. Thanks again.


minimal run for early termination policy to take effect?

Hi I notice that the early termination policy won't start stopping runs unless certain number of runs has been run, for example, if I queue a HyperDrive run with total 4 runs, those will all run till the end even if I specify eval_interval = 1 and delay = 0

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

ID: 82c2fcdc-a4d7-20b5-a53e-33a84b723989
Version Independent ID: 9811ee46-407f-553a-4e78-214d2fdd723a
Content: Tune hyperparameters for your model - Azure Machine Learning service
Content Source: articles/machine-learning/service/how-to-tune-hyperparameters.md
Service: machine-learning
Sub-service: core
GitHub Login: @swatig007
Microsoft Alias: swatig

Hi,
Can you please let me know how many Max concurrent runs you were using? The first set of concurrent runs will usually run through completion, because we wouldn't have a previous best run for comparison.
-Swati.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Kuan Lu<EMAIL_ADDRESS>Sent: Tuesday, April 16, 2019 10:33:39 AM
To: MicrosoftDocs/azure-docs
Cc: Swati Gharse; Mention
Subject: [MicrosoftDocs/azure-docs] minimal run for early termination policy to take effect? (#29518)
Hi I notice that the early termination policy won't start stopping runs unless certain number of runs has been run, for example, if I queue a HyperDrive run with total 4 runs, those will all run till the end even if I specify eval_interval = 1 and delay = 0

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

ID: 82c2fcdc-a4d7-20b5-a53e-33a84b723989
Version Independent ID: 9811ee46-407f-553a-4e78-214d2fdd723a
Content: Tune hyperparameters for your model - Azure Machine Learning servicehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fmachine-learning%2Fservice%2Fhow-to-tune-hyperparameters%23feedback&data=02|01|swatig%40microsoft.com|0b1f7575749746b994f008d6c291ab3f|72f988bf86f141af91ab2d7cd011db47|1|0|636910328236358290&sdata=pTORDd6VK0xmSE5qk898rc10xy%2Fd0rpTEQzLpGLRwCY%3D&reserved=0
Content Source: articles/machine-learning/service/how-to-tune-hyperparameters.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Fmachine-learning%2Fservice%2Fhow-to-tune-hyperparameters.md&data=02|01|swatig%40microsoft.com|0b1f7575749746b994f008d6c291ab3f|72f988bf86f141af91ab2d7cd011db47|1|0|636910328236358290&sdata=5y%2F09hF9ZCDYXBzluWOkLgJ8uiPCkky7Mo95WFneZaU%3D&reserved=0
Service: machine-learning
Sub-service: core
GitHub Login: @swatig007https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fswatig007&data=02|01|swatig%40microsoft.com|0b1f7575749746b994f008d6c291ab3f|72f988bf86f141af91ab2d7cd011db47|1|0|636910328236368284&sdata=VeXlwmpEYQJe79DNh8XfLZlYKUaqIumv%2FZYUV4JEc0U%3D&reserved=0
Microsoft Alias: swatig

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F29518&data=02|01|swatig%40microsoft.com|0b1f7575749746b994f008d6c291ab3f|72f988bf86f141af91ab2d7cd011db47|1|0|636910328236368284&sdata=ZBMtygJvPsRiRDdLXghA7duSFhvTY2mED5epIJ5BMT0%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAjCkNivku69PH5Jjk47pYT9DspQ1TOD7ks5vhglzgaJpZM4czVgc&data=02|01|swatig%40microsoft.com|0b1f7575749746b994f008d6c291ab3f|72f988bf86f141af91ab2d7cd011db47|1|0|636910328236378279&sdata=JmN8M03TUcHfrDJW4ONlDEbd7Mzy9396f1%2F3Z3nJdLg%3D&reserved=0.

@lucas95123 Hi Kuan, any update for this issue? Thank you.

Hi Yutong,
Yeah I saw the reply from Swati, the max-concurrent run I’m using is 4, so I guess if I only have 4 runs all of them will be queued in first-set of run which will all run till the end right? Does that mean after the first-set of concurrent runs the early termination will guarantee to happen? For example 8 runs in total, 4 max concurrent runs, the latter 4 will be determined for early stop based on the first 4 runs.
Thanks,
Kuan
From<EMAIL_ADDRESS>Sent: Wednesday, April 17, 2019 3:39 PM
To<EMAIL_ADDRESS>Cc: Kuan<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] minimal run for early termination policy to take effect? (#29518)
@lucas95123https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flucas95123&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493261817&sdata=rg4Jolw%2BOP1LZwjNcTFZkIHH0coi8bO%2Fy26PQr%2FEcVg%3D&reserved=0 Hi Kuan, any update for this issue? Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F29518%23issuecomment-484287518&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493281802&sdata=1m7WM%2BsKiRdSZbkY1hUPbGt%2FjgUvIVBu7YozYMuvj%2Fg%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADCMAIDLM5G7MOEPNMFQAQTPQ6RIXANCNFSM4HGNLAOA&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493291837&sdata=DHRL95PQEBwfikI%2FeUtq6l3Bm21sN2rX26ma5tUtp4Y%3D&reserved=0.

Hi Kuan,
For subsequent runs, early termination policy will be applied as defined and runs will be evaluated for early termination. The actual determination of whether a run will end up being terminated or not depends on the run metrics and the early termination criteria defined.
Hope this helps,
-Swati.
From: Kuan Lu<EMAIL_ADDRESS>Sent: Wednesday, April 17, 2019 3:45 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Swati Gharse<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] minimal run for early termination policy to take effect? (#29518)
Hi Yutong,
Yeah I saw the reply from Swati, the max-concurrent run I’m using is 4, so I guess if I only have 4 runs all of them will be queued in first-set of run which will all run till the end right? Does that mean after the first-set of concurrent runs the early termination will guarantee to happen? For example 8 runs in total, 4 max concurrent runs, the latter 4 will be determined for early stop based on the first 4 runs.
Thanks,
Kuan
From<EMAIL_ADDRESS>Sent: Wednesday, April 17, 2019 3:39 PM
To<EMAIL_ADDRESS>Cc: Kuan<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] minimal run for early termination policy to take effect? (#29518)
@lucas95123https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flucas95123&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493261817&sdata=rg4Jolw%2BOP1LZwjNcTFZkIHH0coi8bO%2Fy26PQr%2FEcVg%3D&reserved=0 Hi Kuan, any update for this issue? Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F29518%23issuecomment-484287518&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493281802&sdata=1m7WM%2BsKiRdSZbkY1hUPbGt%2FjgUvIVBu7YozYMuvj%2Fg%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADCMAIDLM5G7MOEPNMFQAQTPQ6RIXANCNFSM4HGNLAOA&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493291837&sdata=DHRL95PQEBwfikI%2FeUtq6l3Bm21sN2rX26ma5tUtp4Y%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F29518%23issuecomment-484289050&data=02|01|swatig%40microsoft.com|b11add0f7df5458cea2f08d6c386612d|72f988bf86f141af91ab2d7cd011db47|1|0|636911379257241066&sdata=hAkJSuAfYxHwcIStSa72KBSkQ2fmJ8JYxeGPg4LT3LE%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIYKINXWHOEMC2MWMQFAKJLPQ6SAJANCNFSM4HGNLAOA&data=02|01|swatig%40microsoft.com|b11add0f7df5458cea2f08d6c386612d|72f988bf86f141af91ab2d7cd011db47|1|0|636911379257251058&sdata=oAnrEx%2FNHePTbOoRR%2Fnlnz7%2B%2Ft6qcTQ6GoKlbQDSA%2Fw%3D&reserved=0.

Hi Swati
Thanks for the response, now I get how all these work. Another question by the way, do you guy now or in the near future have plans for C# SDK? would be very helpful for .Net applications.
Thanks,
Kuan

发件人: Swati Gharse<EMAIL_ADDRESS>发送时间: Wednesday, April 17, 2019 9:17:24 PM
收件人: MicrosoftDocs/azure-docs
抄送: Kuan Lu; Mention
主题: Re: [MicrosoftDocs/azure-docs] minimal run for early termination policy to take effect? (#29518)
Hi Kuan,
For subsequent runs, early termination policy will be applied as defined and runs will be evaluated for early termination. The actual determination of whether a run will end up being terminated or not depends on the run metrics and the early termination criteria defined.
Hope this helps,
-Swati.
From: Kuan Lu<EMAIL_ADDRESS>Sent: Wednesday, April 17, 2019 3:45 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Swati Gharse<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] minimal run for early termination policy to take effect? (#29518)
Hi Yutong,
Yeah I saw the reply from Swati, the max-concurrent run I’m using is 4, so I guess if I only have 4 runs all of them will be queued in first-set of run which will all run till the end right? Does that mean after the first-set of concurrent runs the early termination will guarantee to happen? For example 8 runs in total, 4 max concurrent runs, the latter 4 will be determined for early stop based on the first 4 runs.
Thanks,
Kuan
From<EMAIL_ADDRESS>Sent: Wednesday, April 17, 2019 3:39 PM
To<EMAIL_ADDRESS>Cc: Kuan<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] minimal run for early termination policy to take effect? (#29518)
@lucas95123https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flucas95123&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493261817&sdata=rg4Jolw%2BOP1LZwjNcTFZkIHH0coi8bO%2Fy26PQr%2FEcVg%3D&reserved=0 Hi Kuan, any update for this issue? Thank you.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F29518%23issuecomment-484287518&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493281802&sdata=1m7WM%2BsKiRdSZbkY1hUPbGt%2FjgUvIVBu7YozYMuvj%2Fg%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADCMAIDLM5G7MOEPNMFQAQTPQ6RIXANCNFSM4HGNLAOA&data=02|01||1c2debaed0a74db9720c08d6c385814b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911375493291837&sdata=DHRL95PQEBwfikI%2FeUtq6l3Bm21sN2rX26ma5tUtp4Y%3D&reserved=0.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F29518%23issuecomment-484289050&data=02|01|swatig%40microsoft.com|b11add0f7df5458cea2f08d6c386612d|72f988bf86f141af91ab2d7cd011db47|1|0|636911379257241066&sdata=hAkJSuAfYxHwcIStSa72KBSkQ2fmJ8JYxeGPg4LT3LE%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIYKINXWHOEMC2MWMQFAKJLPQ6SAJANCNFSM4HGNLAOA&data=02|01|swatig%40microsoft.com|b11add0f7df5458cea2f08d6c386612d|72f988bf86f141af91ab2d7cd011db47|1|0|636911379257251058&sdata=oAnrEx%2FNHePTbOoRR%2Fnlnz7%2B%2Ft6qcTQ6GoKlbQDSA%2Fw%3D&reserved=0.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F29518%23issuecomment-484349930&data=02|01||efe1c062ba014d041afe08d6c3b4c2be|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911578455258021&sdata=P0EHbYOiNBwwTsKs6IVVWVPiSmSIGU0KkAMaG5ueAGk%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADCMAIAZ2WV6MCND5M3SBVDPQ7Y5JANCNFSM4HGNLAOA&data=02|01||efe1c062ba014d041afe08d6c3b4c2be|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636911578455268032&sdata=m4WVTr%2BsRIDYhrRsQVmhseFMfajCUST5DGZpk1NFRt8%3D&reserved=0.

@lucas95123 Hi Kuan, I will close this issue since your original question has been answered. @swatig007 Hi Swati, do we have any plan for C# SDK?
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Renes gimmicks: initial upload

Added 4 working spells
May require balance changes or grafics update.

Hey! Awesome to see another mod in the works!  Ping me when you're totally finished with it and I'll merge it in and ship it with the next update


RC2 - Preview Tooling, .NET Core Library template.

Created a new ASP.NET Core Library, by default creates this project.json:
{
  "version": "1.0.0-*",

  "dependencies": {
    "NETStandard.Library": "1.5.0-rc2-24027"
  },

  "frameworks": {
    "netstandard1.5": {
      "imports": "dnxcore50"
    }
  }
}

That's great, but as soon as you try and multi target by adding another framework:
{
  "version": "1.0.0-*",

  "dependencies": {
    "NETStandard.Library": "1.5.0-rc2-24027"
  },

  "frameworks": {
    "net461" : { },
    "netstandard1.5": {
      "imports": "dnxcore50"
    }
  }
}

You get this - the NETStandard.Library cannot be resolved.

(The null ref exception I have raised as a seperate issue: #1547
Would it not make more sense to have the project.json file by default, list the NETStandard.Library dependency as a dependency of the netstandard1.5 framework, rather than list it as a common dependency  - because it seems to be incompatible with most other frameworks. Or is this compatibility issue something that will be fixed by the final release of the tooling?

Did you Restore Packages after making the change?  :(


Allow nested connect calls and overload rshift method to connect steps

Description
This PR adds the the functionality of making nested calls on Step.connect method and using the >> operator to connect steps, which can simplify writing long pipelines. An example can be seen with DEITA Pipeline:
from distilabel.llm.huggingface.transformers import TransformersLLM
from distilabel.llm.openai import OpenAILLM
from distilabel.pipeline.local import Pipeline
from distilabel.steps.conversation import ConversationTemplate
from distilabel.steps.deita import DeitaFiltering
from distilabel.steps.expand import ExpandColumns
from distilabel.steps.generators.huggingface import LoadHubDataset
from distilabel.steps.task.complexity_scorer import ComplexityScorer
from distilabel.steps.task.evol_instruct.base import EvolInstruct
from distilabel.steps.task.evol_quality.base import EvolQuality
from distilabel.steps.task.generate_embeddings import GenerateEmbeddings
from distilabel.steps.task.quality_scorer import QualityScorer

if __name__ == "__main__":

    with Pipeline(name="DEITA") as pipeline:
        load_data = LoadHubDataset(
            name="load_data", batch_size=100, output_mappings={"prompt": "instruction"}
        )

        evol_instruction_complexity = EvolInstruct(
            name="evol_instruction_complexity",
            llm=OpenAILLM(model="gpt-3.5-turbo"),
            num_evolutions=5,
            store_evolutions=True,
            generate_answers=True,
            include_original_instruction=True,
        )

        instruction_complexity_scorer = ComplexityScorer(
            name="instruction_complexity_scorer",
            llm=OpenAILLM(model="gpt-3.5-turbo"),
            input_mappings={"instructions": "evolved_instructions"},
        )

        expand_evolved_instructions = ExpandColumns(
            name="expand_evolved_instructions",
            columns=["evolved_instructions", "answers", "scores"],
            output_mappings={
                "evolved_instructions": "evolved_instruction",
                "answers": "answer",
                "scores": "evol_instruction_score",
            },
        )

        evol_response_quality = EvolQuality(
            name="evol_response_quality",
            llm=OpenAILLM(model="gpt-3.5-turbo"),
            num_evolutions=5,
            store_evolutions=True,
            include_original_response=True,
            input_mappings={
                "instruction": "evolved_instruction",
                "response": "answer",
            },
        )

        response_quality_scorer = QualityScorer(
            name="response_quality_scorer",
            llm=OpenAILLM(model="gpt-3.5-turbo"),
            input_mappings={
                "instruction": "evolved_instruction",
                "responses": "evolved_responses",
            },
        )

        expand_evolved_responses = ExpandColumns(
            name="expand_evolved_responses",
            columns=["evolved_responses", "scores"],
            output_mappings={
                "evolved_responses": "evolved_response",
                "scores": "evol_response_score",
            },
        )

        generate_conversation = ConversationTemplate(
            name="generate_conversation",
            input_mappings={
                "instruction": "evolved_instruction",
                "response": "evolved_response",
            },
        )

        generate_embeddings = GenerateEmbeddings(
            name="generate_embeddings",
            llm=TransformersLLM(
                model="TinyLlama/TinyLlama-1.1B-Chat-v1.0",
                device="cuda",
                torch_dtype="float16",
            ),
            input_mappings={"text": "conversation"},
            input_batch_size=5,
        )

        deita_filtering = DeitaFiltering(name="deita_filtering")

        # Current connect approach
        load_data.connect(evol_instruction_complexity)
        evol_instruction_complexity.connect(instruction_complexity_scorer)
        instruction_complexity_scorer.connect(expand_evolved_instructions)
        expand_evolved_instructions.connect(evol_response_quality)
        evol_response_quality.connect(response_quality_scorer)
        response_quality_scorer.connect(expand_evolved_responses)
        expand_evolved_responses.connect(generate_conversation)
        generate_conversation.connect(generate_embeddings)
        generate_embeddings.connect(deita_filtering)

We can chain them:
        # Chained connect approach
+        (
+            load_data
+            .connect(evol_instruction_complexity)
+            .connect(instruction_complexity_scorer)
+            .connect(expand_evolved_instructions)
+            .connect(evol_response_quality)
+            .connect(response_quality_scorer)
+            .connect(expand_evolved_responses)
+            .connect(generate_conversation)
+            .connect(generate_embeddings)
+            .connect(deita_filtering)
+        )

Or using the >> operator (by overloading the __rshift__ method):
        # Chained rshift approach
+        (
+            load_data
+            >> evol_instruction_complexity
+            >> instruction_complexity_scorer
+            >> expand_evolved_instructions
+            >> evol_response_quality
+            >> response_quality_scorer
+            >> expand_evolved_responses
+            >> generate_conversation
+            >> generate_embeddings
+            >> deita_filtering
+        )

Hey here! Won't the rshift cause issues when the steps are not sequential? Also the approach looks nice, but I'm afraid the non-sequential DAGs won't benefit from this and if that's the case, it may be confusing for users. I believe I briefly discussed this with @gabrielmbmb back in December and none of us was sure about this approach, but maybe now @gabrielmbmb thinks otherwise. Anyway, great work so far! 👍🏻

Hey here! Won't the rshift cause issues when the steps are not sequential? Also the approach looks nice, but I'm afraid the non-sequential DAGs won't benefit from this and if that's the case, it may be confusing for users. I believe I briefly discussed this with @gabrielmbmb back in December and none of us was sure about this approach, but maybe now @gabrielmbmb thinks otherwise. Anyway, great work so far! 👍🏻

What do you mean by sequential steps? If you mean pipelines like https://github.com/argilla-io/distilabel/pull/494 of PairRM, the calls to connect could be done like this:
- load_hub_dataset.connect(rename_columns)
+ load_hub_dataset >> rename_columns

- rename_columns.connect(evol_instruction_complexity_1)
- rename_columns.connect(evol_instruction_complexity_2)
+ rename_columns >> evol_instruction_complexity_1
+ rename_columns >> evol_instruction_complexity_2

- evol_instruction_complexity_1.connect(combine_columns)
- evol_instruction_complexity_2.connect(combine_columns)
+ evol_instruction_complexity_1 >> combine_columns
+ evol_instruction_complexity_2 >> combine_columns

- combine_columns.connect(rename_for_pairrm)
- rename_for_pairrm.connect(ranker)
+ combine_columns >> rename_for_pairrm >> ranker

Also, it's not included in this PR, but it could be updated to simplify cases like the one from rename_columns:
- rename_columns.connect(evol_instruction_complexity_1)
- rename_columns.connect(evol_instruction_complexity_2)
+ rename_columns >> [evol_instruction_complexity_1, evol_instruction_complexity_2]

I think it could improve readability (it's be syntatic sugar for the call to step.connect(other_step)), but if you think it can be confusing, we can remove remove it without a problem. Also, assuming we can draw the pipeline it should be easier to learn this syntax 😄

I think it could improve readability (it's be syntatic sugar for the call to step.connect(other_step)), but if you think it can be confusing, we can remove remove it without a problem. Also, assuming we can draw the pipeline it should be easier to learn this syntax 😄

Yes indeed it can improve it, but I believe I discussed this with @gabrielmbmb and he was not really a fan of rshift not sure if that was opinionated or had a strong reason to, but let's discuss with him when he jumps into the conversation 👍🏻

Hi here @plaguss I've tried this aiming to connect LoadDataFromDicts with a list of UltraFeedback tasks and it won't work, since it will raise the following exception: Operator ">>" not supported for types "LoadDataFromDicts" and "list[UltraFeedback]", could you please have a look at it? Thanks in advance!

I don't know that much about pyright, will take a look to see if there's any error in the typing info, but it should say it's correct in that case, the types are generic enough for those methods:
    def __rshift__(self, other: Union["_Step", List["_Step"]]) -> "_Step":
        ...
    def __rrshift__(self, other: List["_Step"]) -> "_Step":
        ...

Maybe upgrading pyright solves the issue? Not sure either


Add is_null and is_not_null to Expression

Documenting in case anyone out there happens to want to get involved, these should be easy to add. We need a trivial test case for this. "users"."hair_color" is nullable in our normal schema.

#27 added this


Add more Metrics to Quality Report

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Is your feature request related to a problem? Please describe.
Add more metrics to Quality Report or Grafana Dashboard:

Break Annotation Time per Label Type: It helps to identify the challenging Label Types or Shapes
Compare count of created and deleted labels in Annotation, Validation, and Acceptance stages: It helps to evaluate if for certain projects adding Validation or Acceptance stages to the process is valuable enough to spend extra time on them
Active vs Inactive Annotation time: It'd be helpful to identify where annotators need more training for complex tasks

Describe the solution you'd like
Data points to calculate above metrics are already collected by events endpoint and stored in ClickHouse. The proper Grafana dashboards needs to be created for them, or expose them in Quality Report page of Projects and Tasks.
Describe alternatives you've considered
Above metrics can be exposed through API's only, so the reports or dashboards will be built outside CVAT app.
Additional context
These metrics help to identify where annotation process and quality can be improved - when annotation tasks are complex and annotators need to be trained for the required domain knowledge to provide proper annotations.

Hi, thank you for the suggestions! But this is related to Analytics reports, not Quality reports.


Bug: Claudie doesn't allow nodes from two different AWS provider instances in the same region

Current Behaviour
Currently, Claudie doesn't allow the following configuration:
spec:
  providers:
    - name: aws-team1
      providerType: aws
...
    - name: aws-team2
      providerType: aws
...
  nodePools:
    dynamic:
      - name: control-aws
        providerSpec:
          name: aws-team1
          region: eu-west-1
      - name: compute-aws
        providerSpec:
          name: aws-team2
          region: eu-west-1

Expected Behaviour
Sometimes, the users might want to deploy nodepools in the same region, by two different providers (e.g. for billing, reporting or security issues).
Anything else to note
Currently, I see the options to set provider.alias to e.g.:

nodepool_{{ $provider.name }}_{{ $provider.region }}
nodepool_{{ substr(sha256($provider.name + $provider.region), 0, 4) }}
nodepool_{{ $random }}

References

https://github.com/berops/claudie/issues/1296
https://github.com/berops/claudie/blob/master/services/terraformer/templates/aws/provider.tpl

Depends on https://github.com/berops/claudie/issues/1296