How to decrease the minimum throughput

If the current minimum throughput is 30000 in the Unlimited storage capacity. Would be the minimum throughput decreased automatically if volume of data (actual throughput) is decreased? How can we decrease the current minimum throughput (20000 for example) in case of we know volume of data (actual throughput) is decreased. Thanks.

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

ID: 0f2b93a5-28b8-db4a-ab64-6342d3aafc63
Version Independent ID: 245586f2-63e1-1e78-a5dd-21e8fa2cc5d3
Content: Provision throughput on Azure Cosmos containers and databases
Content Source: articles/cosmos-db/set-throughput.md
Service: cosmos-db
GitHub Login: @aliuy
Microsoft Alias: andrl

@kazshi Thank you for your interest in Azure products and services. We are investigating and will get back to you soon.

@kazshi The throughput isn't automatically decreased if your data size reduces. You have to change the throughput limit to the value that you need, you can update the throughput by using Azure portal or  programmatically by using one of the supported SDK. You can billed for the provisioned throughput and not based on the usage.
If using portal, you can change the throughput limit under the scale and settings blade.

@SnehaGunda Thanks for your comment. Sorry for my lack of explanation. Actually the original question is from my customer and their current throughput value is 31900 and it's lower limit. They cannot reduce the throughput value from the Portal or using program because of a large number of partitions, and they're trying to reduce data size to decrease the current throughput value (change the lower limit). Would the number of partitions be decreased by reducing the data size? How can they change lower limit of the throughput value in this case? Thanks.

Hi @SnehaGunda , do you have any information of how to change the lower limit for the case? Thanks.

Yes I'm seeing this same issue on the SQL API side. If you scale up your database above a certain threshold, usually 10k RU/s), you can no longer come back down to 400 and get locked into a higher tier of some sort. This is very frustrating since I wanted to create an auto-scaler function that scales up the collection every day for a big bulk import, and then scales back down after the import is finished.

Also, there is no info on why the minimum RU/s limit is set to what it is, which is the crux of this issue. According to this article, you should have a minimum of 400 RU/s limit with up to 4 collections, 100 RU/s additional minimum per collection over 4, and 40 RU/s additional minimum per GB of storage. Using that math, since I have 5 collections and 43GB of data, my minimum should be 2,220 RU/s, but my minimum is 3,200 which seems totally arbitrary!

@kazshi @ijabit I have reached out to the product group to get an accurate answer. Apologies for the delay. Thank you!

@kazshi and @ijabit Sorry about the delay in getting back on this.
We will be providing a new header "x-ms-cosmos-min-throughput", it will be available soon. It represents the minimum throughput value an offer can be scaled down to. Once you have this header, you should be able to scale the RU limit to not lower than that value. The minimum throughput value is based on the following three properties:
o	Max throughput that you ever increase on the container or the database.
o	Data stored in the container or the database.
o	If you are using database-level/shared throughput, this value depends on the number of containers within the database.
@ijabit Due to above factors you can't always scale down thr RU value to 400. Your calculation should include the above three properties, I think there will be a formula that is used to calculate the minimum value which will give a better idea.
@kazshi Would the number of partitions be decreased by reducing the data size? - The number of partitions vary based on the data size and throughput. You don't have to worry about the number of partitions when you choose the right value. The right partition key should consider these factors: https://docs.microsoft.com/en-us/azure/cosmos-db/partitioning-overview#choose-partitionkey
@Mike-Ubezzi-MSFT in case you have any other update from the product team please share it as well.

@SnehaGunda Thank you for the info. Do you have any ETA of when the new header will be implemented?

o	Max throughput that you ever increase on the container or the database.
That is the really frustrating thing, it makes it impossible to scale up for a large load without getting locked in to a higher rate. I thought that was one of the big selling points, that you can scale up and down as demand requires! Nothing in the docs says that once you scale up you get locked in. Very disappointing...

@SnehaGunda Thanks for your valuable inputs. I have assigned this issue to you for further clarifications.

@kazshi I don't know of any ETAs as of now we will notify you with blog posts and doc updates. Yes we are working on documentation for this feature, we will be updating the main conceptual and REST API docs. We will notify you when the docs are available.
@ijabit There might be a different way to solve your problem, which I may not be aware. Can you please send an email to<EMAIL_ADDRESS>alias, a broader audience can look at your questions, our team can guide you in the right direction.

I also dropped an email to our product group, @kirillg will respond to this issue soon.

@SnehaGunda were you able to get a response?

@ijabit no, I sent a followup email to Kirill, can you also please reach out the<EMAIL_ADDRESS>alias, its monitored by a broader audience and easy to get faster response.

@SnehaGunda I've sent a message to that Email. Thanks!

@ijabit Unfortunately I can't find your email to askcosmosdb alias, I am sure you sent it because other PM saw the email. I may have deleted it by mistake. Did you get your questions addressed?

@snehagunda the subject contains I110793756 if that helps. Karthik Raman asked me for clarification which I replied to. I haven't heard back form anyone since then. Thanks.

@ijabit I pinged Karthik to look into this issue, please send a followup email from your end too :-) . We will track with the alias and close the issue here.
#please-close

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion but, the specific issue will be addressed via the email communication that is in-progress.

@SnehaGunda Was "x-ms-cosmos-min-throughput" implemented?  Thanks.

@Mike-Ubezzi-MSFT @SnehaGunda Could please reopen this thread so that I can track about the "x-ms-cosmos-min-throughput" implementation?  I'll need to provide info of it to my customer. Thanks.

@kazshi Best course of action is to reach out to askcosmosdb at microsoft.com where you will be issued a tracking ID, as previously advised.

@Mike-Ubezzi-MSFT I've not heard anything back in over a month. Not sure if that is the "best course of action".

@Mike-Ubezzi-MSFT I've not heard anything back in over a month. Not sure if that is the "best course of action".

Please send your Subscription ID to AzCommunity and I will send you instructions to have a support request filed. If you do have an Azure support plan, please go ahead and open a ticket with support. It is the best way to get this escalated. Thank you.

@Mike-Ubezzi-MSFT Actually the original issue was from support request, and I provided information (according to the following page - confirmed to Ask Azure Cosmos DB) of there's no way to decrease the minimum RU to the customer, the SR case has been already closed. Thanks for your support.
Provision throughput on Azure Cosmos containers and databases | Microsoft Docs
https://docs.microsoft.com/en-us/azure/cosmos-db/set-throughput#update-throughput-on-a-database-or-a-container

It doesn't make sense that you can scale a container up with unlimited maximum throughput, but can't scale it back down to the original minimum.  There should at very least be a warning about this in the documentation (and in the portal for that matter) and clear details on what thresholds will end up changing the minimum possible throughput.

This is joke - Isn't it?
I have run some performance tests against CosmosDb app and now I can't scale down and I will pay 60dollars per month for not using instance? Great job!

are there any updates regarding the header x-ms-cosmos-min-throughput. Is it already available?

Why is it that even my database with 0 items once I scale up I can't scale back down unless its at least 10% of what I scaled up to? What's the reason for this?

Any updates on this? Scaled my database up temporarily to handle some initial load. Now I can't scale down, saying 'Requested throughput 1000 is less than required minimum throughput 2000'. Do I really have to recreate the database??


Link to generated documentation is missing for script reports.py

Link to generated documentation is missing for script reports.py

Fixed in https://github.com/RedHatInsights/insights-results-aggregator-utils/pull/134


BugFix when ID is a UUID

I had a JSON Encode Serialize error when I use a Model with ID as UUID.
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type UUID is not JSON serializable

I'll create a test to don't decrease the coverage

Hi @rhenter, this LGTM, can you please add an example to the test_app using the UUID, it would help a lot to test your changes.

Hi @rhenter, this LGTM, can you please add an example to the test_app using the UUID, it would help a lot to test your changes.


enhance: Only import from packages in package.json

Motivation

For PNP, yarn 2 compatibility as well as not having issues with other package managers.
Solution

Only import from packages referenced in package.json

Codecov Report

Merging #1785 (91d7ede) into master (d14673e) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1785   +/-   ##
=======================================
  Coverage   98.63%   98.63%
=======================================
  Files         103      103
  Lines        1901     1901
  Branches      383      383
=======================================
  Hits         1875     1875
  Misses         14       14
  Partials       12       12

Impacted Files
Coverage Δ

packages/legacy/src/shapeToEndpoint.ts
80.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Connection spinner is off center in <IP_ADDRESS>10715.1

Describe the bug
Not sure if this should be classified as a bug or enhancement. The latest version of Lens contains a spinner that is not quite aligned with the 'Connecting...' text.
To Reproduce
Steps to reproduce the behavior:

Start Lens
Connect to cluster (i.e. through the hotbar)
See a spinner that is off center

Expected behavior
The spinner should be centered above the 'Connecting...' text.
Should look more like: (paint edit of screenshot found below)

Screenshots

Environment (please complete the following information):

Lens Version: <IP_ADDRESS>10715.1
OS: Windows 21H1
Installation method (e.g. snap or AppImage in Linux): .exe from https://k8slens.dev/

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Your logs go here...

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
your kubeconfig here

Additional context
Add any other context about the problem here.

Interesting fix, but looks great again! Thanks for fixing 👍


NPM is not installed with Node in NVM v1.1.6

If this is a question about how to use NVM4W, please use stackoverflow instead.
If this is an issue regarding antivirus, make sure you search the existing issues first.
My Environment

[ ] Windows 7 or below (not truly supported due to EOL - see wiki for details)

[ ] Windows 8

[ ] Windows 8.1

[X] Windows 10

[ ] Windows 10 IoT Core

[ ] Windows Server 2012

[ ] Windows Server 2012 R2

[ ] Windows Server 2016

[ ] My Windows installation is non-English.

I'm using NVM4W version:

[ ] 1.1.7
[X] 1.1.6
[ ] 1.1.5
[ ] 1.1.4
[ ] 1.1.3
[ ] 1.1.2
[ ] 1.1.1
[ ] Older
[ ] OTHER (Please Specify)

I have already...

[X] read the README to be aware of npm gotchas & antivirus issues.
[] reviewed the wiki to make sure my issue hasn't already been resolved.
[X] verified I'm using an account with administrative privileges.
[ ] searched the issues (open and closed) to make sure this isn't a duplicate.
[X] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

[ ] settings.txt
[ ] proxy support (Have you tried version 1.1.0+?)
[ ] 32 or 64 bit support (Have you tried version 1.1.3+?)
[ ] Character escaping (Have you tried version 1.1.6+?)
[ ] A standard shell environment (terminal/powershell)
[ ] A non-standard shell environment (Cmder, Hyper, Cygwin, git)

Expected Behavior
Typing in nvm install 10.14.1 installs both node and npm at the same time.
Actual Behavior
Typing in nvm install 10.14.1 installs both node but throws an error on the npm install hence not working.

Steps to reproduce the problem:

Installed v 1.1.6 of nvm on my machine
Checked to make sure nvm is installed with admin rights
Install node using nvm install 10.14.1 and nvm install latest
The message saying it cannot install npm
Install npm as the message says in the screenshot, however, it still does not work

I also encountered the same problem.

npm changed the address of their repo. Upgrade to NVM 1.1.7.


Release <IP_ADDRESS>

The following samples have been added:

• Features > Toggle between feature request modes
• Layers > Export vector tiles
• Layers > Select ENC features
• Maps > Display a map SwiftUI

The following samples have been updated:

• Display information > Sketch on the map
• Geometry > Nearest vertex
• Layers > OpenStreetMap layer

The following samples have been removed:

• Features > Service feature table (cache)
• Features > Service feature table (manual cache)
• Features > Service feature table (no cache)
• Layers > ArcGIS vector tiled layer (URL)

In addition, this release includes the following changes:

• Updated app info page
• Updated main README with instructions for installing SDK manually
• Fixed various bugs in the following samples: Identify raster cell, Map reference scale, and Show legend
• Updated READMEs
• Updated Display KML network links service

The changes look good, but the release notes are not correct - they seem to overlap a lot with the 12.0.2 notes. Did you paste the wrong notes?

Mike stated that the U13 release notes should include <IP_ADDRESS>:

Probably unnecessary, but to be as explicit as possible in writing:
Release notes pattern
<IP_ADDRESS> = Update 12 release notes
<IP_ADDRESS> + <IP_ADDRESS> = U13 notes
<IP_ADDRESS> + <IP_ADDRESS> = U14 notes
etc.

Ohh that makes sense. Let me make some slight adjustments to the notes before approval.


[Modal]: add z-index prop to modal

Interested to work on this one. Can you give more context, please?

Hey @SebastianLF, Great to hear that you are interested to work on this 🤩
Context:
The modal component has hardcoded z-index right now. I was thinking of adding a new prop to the component called -> zIndex . And based on this value the modal will get a z-index. Also whatever value is used right now should be the default value. so that there are no breaking changes 😄
I will assign you this issue. Let me know if you want any help, btw you can join moralis discord channel and ask for any help in web3uikit channel 🙌🏻

Thanks for this clear explanation. Let's try it!

Hey @SebastianLF 👋🏻
How is this task going?
Let me know if you are facing any issues 🙌🏻

Sorry, will work today on it :)

Nice work @SebastianLF 🥳
Closed as completed by #981


How to represent all versions

Is there a way to pass a range that represents all versions of a package?
I tough * would do it but it fails to parse. What should be the correct way?

You can do something like
irb(main):001:0> SemanticRange.satisfies('1.0.0', '>0.0.0')
=> true

@katzj thanks. Just one detail: wouldn't >=0.0.0 be more correct?

Yes :)


jetson xavier nx support

I am working on Jetson Xavier nx so is this repo support on Jetson Xavier nx ?

Yes, it will work on the Xavier.


XA transactions fail using SQLServer 2017-latest

When following documentation here:
https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-configure-msdtc-docker?view=sql-server-2017
Attempts to enable distributed transactions on SQL Server 2017.  The following error is thrown:
com.microsoft.sqlserver.jdbc.SQLServerException:
Failed to create the XA control connection.
Error: "Procedure expects parameter '@errormegssage' of type 'nchar'."

Note: This issue is not seen when using SQL Server 2019 preview.  But being a beta/preview image it should not be considered production ready.

@KyleAure , We have been made aware of this issue in SQL 2017 CU16. This is also mentioned in following thread.
https://github.com/microsoft/mssql-docker/issues/28#issuecomment-526278308
We are working on fixing this in upcoming CU. If you are blocked from making progress until then, please reach out to the SQL support team.

Thanks for the reply.  Yeah I had saw that after I posted this issue.  But figured that thread was more general and a specific issue should be raised for what we are seeing in SQL Server 2017.  If you want to close this issue you can but I think it may be better for tracking.


Fix incorrect parameters processing for JOIN subquery

Fixes #117
Parameters are processed incorrectly for JOIN subquery:

when queryCache is enabled - ON statement should be included in query cache, otherwise parameters are missing;
when queryCache is disabled - JOIN statement should be parsed only once, otherwise parameters are duplicated.

During the fix of failing test for SQLServer, I've spotted another issue - joins part must be executed exactly when it's added to the statement, otherwise an order of parameters parsed from JOIN tokens is broken.
So, I've reverted this part and only parse names and register aliases, but with a temporary QueryParameters container to avoid parameters duplication. This allows to resolve all names and aliases without affecting the result statement.

Thanks!


Azure Devops

Issue Type: Feature Request
There should be an option to use Azure DEVOPS for source control!
Azure Data Studio version: azuredatastudio 1.10.0 (5fdb967ffcea41df0335ec17cfa396a694bb174e, 2019-08-14T18:28:10.311Z)
OS version: Windows_NT x64 10.0.16299

Closing as duplicate of https://github.com/microsoft/azuredatastudio/issues/16001.  Thanks for opening this suggestion!


Torus social login visual improvements

I watched my mother-in-law click Google, and then act very confused when the torus modal popped up and she was prompted to click Google a second time. She asked "did I do something wrong?"

Let's update the visual style of these buttons so that it is clear they are one button to trigger the torus modal.
Stretch goals: On that button, or in the overline text there, can we indicate that the social logins are powered by torus, or show the torus logo, or something?
I also just noticed the icon color is broken. We can fix that in this ticket as well

@Atmosfearful isn't the plan to move away from this custom modal? There is an issue (#917) to investigate using the web3auth modal as-is.

This is resolved with updated design pattern implemented for Carbonmark.


[WIP] Introduce new sub command

Implement #111

[x] Introduce new sub command
[ ] Add tumugi new project NAME sub command

Coverage decreased (-0.4%) to 94.788% when pulling ba493d2c94b49692db5b2716b158ca3f30489c69 on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-0.4%) to 94.788% when pulling ba493d2c94b49692db5b2716b158ca3f30489c69 on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-0.4%) to 94.788% when pulling ba493d2c94b49692db5b2716b158ca3f30489c69 on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-0.4%) to 94.788% when pulling ba493d2c94b49692db5b2716b158ca3f30489c69 on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-0.4%) to 94.788% when pulling ba493d2c94b49692db5b2716b158ca3f30489c69 on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-0.4%) to 94.788% when pulling ba493d2c94b49692db5b2716b158ca3f30489c69 on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-0.5%) to 94.67% when pulling 26f6f67226a788541ff62e4c610548c03c21f8eb on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-0.5%) to 94.67% when pulling 26f6f67226a788541ff62e4c610548c03c21f8eb on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-1.3%) to 93.887% when pulling 6a09e0e7c0d1f25e7a333d8c49863210dcbd85db on change-new-subcommand into ecb53fe53e3f8bf55af95a3e93d4f3165fa1a3bc on master.

Coverage decreased (-1.2%) to 90.088% when pulling 76ee34986414cf33234b14f4077ccb0b5d55c534 on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage decreased (-1.2%) to 90.088% when pulling 76ee34986414cf33234b14f4077ccb0b5d55c534 on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.744% when pulling 32e839f9f910a59e64f55b6ed81c5472d78db9e3 on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.4%) to 93.683% when pulling 1decff329b404f9a03b1be0eec3174c7f111afd7 on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.778% when pulling f7d5b84c5c6b5d8560c39a3f7cd5fc54a979e83c on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.778% when pulling f7d5b84c5c6b5d8560c39a3f7cd5fc54a979e83c on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.778% when pulling f7d5b84c5c6b5d8560c39a3f7cd5fc54a979e83c on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.778% when pulling f7d5b84c5c6b5d8560c39a3f7cd5fc54a979e83c on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.778% when pulling f7d5b84c5c6b5d8560c39a3f7cd5fc54a979e83c on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.778% when pulling f7d5b84c5c6b5d8560c39a3f7cd5fc54a979e83c on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.

Coverage increased (+2.5%) to 93.778% when pulling f7d5b84c5c6b5d8560c39a3f7cd5fc54a979e83c on change-new-subcommand into 69d24e0d16725e7b85ac04bd5c2e8fef5c035bf6 on master.


Integrate Multi-Environment Testing for Playwright (Web/App/In-Cluster)

Dependent on issue #2332
Description
After migrating Playwright tests to the default structure, the next step is to enable running tests across different environments: web, app, and in-cluster. The goal is to create a unified setup so developers can easily run tests in any environment without needing reconfiguration, ensuring consistent test coverage across all modes.

I think this can be done in another step. It's more important now to get at least one minimal app test running.

Working on this https://github.com/headlamp-k8s/headlamp/pull/2344


The image is not resizing

So I followed all the steps and the image is loaded but with original dimensions.
All my images are in the public folder and from what I can see using a debugger in the GlideServiceProvider, the router is not working. Maybe because my images are not in the storage folder?

Hi,
Could you show me your config-file, and how you load the images?

This is how I load the images

And for the config file
'source' => [
'path' => public_path('media'),
],
'cache' => [
'path' => storage_path('glide/cache'),
],
'baseURL' => 'media',
'maxSize' => 2000 * 2000,
'useSecureURLs' => true

This is how I load the images
     <img src="{{ GlideImage::load($user->profileImage['url'], ['w'=> 30]) }}" alt="{{$user->username}}"/>

And for the config file
'source' => [
        'path' => public_path('media'),
    ],
    'cache' => [
        'path' => storage_path('glide/cache'),
    ],
    'baseURL' => 'media',
    'maxSize' => 2000 * 2000,
    'useSecureURLs' => true

Is the value of $user->profileImage['url'] a path relative to public_path('media')?

Yes the path is something like photos/user/name of the image

Ok.
Can you send me the generated url for an image?
Are you using Laravel 4 or 5?

I'm using Laravel 5 and this is how a url looks
/media/photos/james/03-04-2015_14-39-47_9qBTh.jpg?w=300&s=087846c0c6839575fe7f422ba829fc68

The image is showing.

Never mind, the problem was on my side. I didn't configure my server correctly. Thanks for your help anyway.

i have same issue while generating image on my website http://www.aircraftsmuseum.com/


just CLA test

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report

:exclamation: No coverage uploaded for pull request base (seatago@5ae2253). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             seatago     #437   +/-   ##
==========================================
  Coverage           ?   40.58%
==========================================
  Files              ?      139
  Lines              ?     8751
  Branches           ?        0
==========================================
  Hits               ?     3552
  Misses             ?     4910
  Partials           ?      289

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


Document git submodule commands

LGTM

Why did remove the comments in the README?
They seemed helpful.

The commands are safe to always run, so there's no need to include Git 101 documentation.


Can you make a easy turtorial?

Hi the information of flow is too little。can you make a turtorial that a blog or a website? i think is very useful for  some people who is new beginner of flow.

@taigacute
Thank you for your interest in flow.  Sure, I shall prepare a tutorial.

@js-ojus  that's good, A good tutorial will attract more people to interest flow

@3xxx
👍 Glad to see more progress!

the pic seems like a docment not a turtorial?

@taigacute That example is just a step by step test.

@taigacute @3xxx
I am finishing up a few urgent pieces of work in my consulting engagements.  Kindly bear with me.  I shall return to this.
Also, there is an overhaul being made to flow.  Please keep watching the 0.9 branch for more details.  Thank you all!

Thank for the flow lib and i glade to find the workflow lib in golang.
i test the lib last week and , maybe  i am a newer to sql and golang ,  i found that when  new  a child document , the data is query in mysql but is error  at parse the ctime , i am not sure
pdoc, err := Documents.Get(nil, input.ParentType, input.ParentID)->
err := row.Scan(&elem.Path, &elem.AccCtx.ID, &elem.Group.ID, &elem.Group.Name, &elem.Ctime, &elem.Title, &elem.Data, &elem.State.ID, &elem.State.Name)->
err := r.rows.Scan(dest...)
the error :
err : sql :  Scan  errors on colum  index 4, name "ctime": unsupported Scan ,  storing  driver.value  type []uint8
and return err


BREAKING CHANGE: Fix openapi validation errors

alertSource -> alert_source in notifications

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Don't require targetversion to be latest for Class Libraries

Describe the bug
When building a class library, the target version should not matter, as long as it's at least minversion. That check should only apply to app projects.
This check is done here and should have a condition for class libraries to ignore it (or check that target is at least minversion):
https://github.com/microsoft/microsoft-ui-xaml/blob/8f8cd0fe32754cfcd83dafb2fc8539703b6aec26/build/NuSpecs/MUXControls-Nuget-Common.targets#L16-L18
Steps to reproduce the bug

Create a .NET Class Library and set target version to 17134.
Add WinUI nuget package.
Build

Expected behavior
Build succeeds
Actual behavior
Build error:
C:\Users\username\.nuget\packages\microsoft.ui.xaml\2.3.191211002\buildTransitive\Common.targets(16,5): error : Microsoft.UI.
Xaml nuget package requires TargetPlatformVersion >= 10.0.18362.0 (current project is 17134) [E:\src\myclasslibrary.csproj]

Version Info
2.3.191211002

@jevansaks @llongley any ideas why 19H1 is required ?

Agree that the check for class libraries could be different. This check is serving two purposes:

For apps, it makes sure that you are running against a version high enough that we won't get "quirked" behavior from OS XAML.
For apps and class libraries, it's trying to avoid a confusing error message down the line because the WinUI WinMDs reference types in the Windows SDK that weren't introduced until later versions of Windows.

Now for class libraries the #2 check still needs to be there, but perhaps the Windows SDK we require can be lowered?
I think if someone can suggest a fix here that covers all the various project types we would be happy to accept it.
@dotMorten is there a challenge in having your class library target the 18362 SDK?

is there a challenge in having your class library target the 18362 SDK?

I prefer keeping min and max version the same. This to avoid having to ensure we don't call APIs that aren't supported on that platform. If I don't need the latest features, why enable them?
I don't really get your second point. Why is it confusing to not see APIs that you can't call on the version you're targeting?

The problem is that the WinUI metadata has types it references that weren't introduced until a later version of the Windows SDK. You will get a bizarre compiler error about not being able to resolve types if you disable the check and target too old of a Windows SDK.

I’m ok with closing this


feat: Add env to the tasks to specify tasks specific environment variables

This adds the ability to set additional environment variables for a specific task. E.g.:
[tasks]
bla = { cmd = "echo $ABC", env = { ABC = "DEF" } }
path_mod = { cmd = "echo $PATH", env = { PATH="/tmp/path:$PATH" }}

This results in:
$ pixi run bla
DEF

$ ABC=hoi pixi run bla
hoi

$ pixi run path_mod
/tmp/path:/bin:/.local/bin .....

We might also want this for a feature / environment (as a lightweight way of adding an 'activation script').
TODO:

[x] Add tests, preferrably in unit and an example where it is tested on their test task.
[x] Add documentation
[x] Add to schema.json

@wolfv  Do you want to continue on this pr? other wise making an issue out of it and closing it would be nice.

I like this, a lot actually.
A few questions:

xxx = { cmd = "echo $ABC", env = { "ABC" = "asdsad" }} if i run this with ABC="hoi" pixi run xxx Should it say "hoi" or "asdsad"? I could imagine a nice use-case where it is used as a default but could be overwritten. This is also what task does: GREETING=hoi task greet uses hoi for GREETING instead of the value defined in taskfile.
Should the env transfer in a depends_on graph?

If I could, I would approve the PR (since I opened it I can't review!) :)


Anyway to 'Avoid' a format (make last choice?)

Hello am using -f 'best[width<=1280]/[height<=?1080]/best' and it works well most of the time, but my player is not hot for WebM (more and more common). Is there a way to mod the above to prefer like every other format before WebM??
Thanks!!

Read FAQ.

My question is NOT covered in the FAQ.

It does. You just don't bother reading as well as searching the bug tracker. Needless to say you didn't even filled the new issue template.

Also filtering work for comparisons = (equals), != (not equals), ^= (begins with), $= (ends with), *= (contains) and following string meta fields:

ext: File extension

...

!= (not equals)

ext: File extension

Forgive me, but NOBODY would ever see the connection you just mentioned (or that it could work in this case), without better clarification.  Thanks for the bloody-nose, as always.

There is even an example for this but sure who will bother reading.


fix attributes/role for dataproc

minor fix to key for dataproc role.

Merged https://github.com/GoogleCloudPlatform/dataproc-initialization-actions/commit/241ad75a6edd4b8ff4f5308470df957e6c1d1b9f Thanks for catching and fixing this!


This is not your app!!!

https://www.youtube.com/playlist?list=PL0dzCUj1L5JGKdVUtA5xds1zcyzsz7HLj

@mihailsalari it was coded by me. However these tutorials helped me lot and I mentioned his name, so people can check other tutorials made by him. Is it an issue to submit codes that someone helped me write?

Really? You lie man!

@mihailsalari Again those tutorials are the reason why I coded this, however I coded in a totally different way, with storyboard, with swift 3, with video player VC etc. I don't seek any profit by uploading codes to github, anyone can watch these tutorials and make this. And I mention author's name and twitter profile so everyone can follow him.  So next time choose words carefully. If there is no other arguments I will close this conversation.

https://www.youtube.com/playlist?list=PL0dzCUj1L5JGKdVUtA5xds1zcyzsz7HLj


Remove baseline images

@Holmgren825 I've been a bit quick in merging haha
I really appreciate the effort to use baseline images for the tests, but I'd rather not have them. They are a real pain to maintain, and one day you will be gone and it will fall back to me ;-)
Furthermore, it will make many things painful to change, since each change to the plot will also change the tests, etc.
Tests are good, but here I really think we should keep tests as slick and simple as possible.

Ok, understand! Will fix.


Is Tutorial Material still useful in the current version？

Thanks for the amazing work!
I am trying to run inference in my own datasets.
I found some tutorials in ./demo and ./docs, are these materials still useful in the current version?

No, these files are from mmsegmentation without modification.
It is recommended that you first convert the dataset to COCO or Cityscape format, and then use inference_coco.sh or inference.sh for inference.

No, these files are from mmsegmentation without modification.
It is recommended that you first convert the dataset to COCO or Cityscape format, and then use inference_coco.sh or inference.sh for inference.

Got it. Thank you!


 Can you share a copy of your settings file?

Windows terminal.txt

This is #8910, I think.

yeah seems so


Python packageOverrides improvements

Between these two changes, complex uses of packageOverrides become a lot more tolerable (even if they’re still not pleasant). Explanations in commit messages.

For python3.pkgs: apply packageOverrides recursively, this is why it is typically also needed to pass self = python; if I recall correctly.
Regarding python3: expose packageOverrides in passthru , see also https://github.com/NixOS/nixpkgs/pull/67422. Another idea was to offer the contents of python-packages.nix as a top-level "overlay" so what you want to do here could apply also to the other Python sets.

For python3.pkgs: apply packageOverrides recursively, this is why it
is typically also needed to pass self = python; if I recall
correctly.

Does my change then remove the need to do that?

Regarding python3: expose packageOverrides in passthru , see also
https://github.com/NixOS/nixpkgs/pull/67422. Another idea was to offer
the contents of python-packages.nix as a top-level "overlay" so what
you want to do here could apply also to the other Python sets.

Exposing packageOverrides is a nice simple change that makes multiple
overrides possible, if not pretty.  It doesn't stop us doing it better
later, but I don't have the capacity to do that now.

Does my change then remove the need to do that?

I don't think so. Consider you override both the interpreter build, and a package in the package set. In that case you really still need to pass self = python; to make it use that Python. Thus, your change should not be needed then.
https://github.com/NixOS/nixpkgs/blob/a68a408a7ff80ef8e573d6b922ee824f68122292/pkgs/development/interpreters/python/default.nix#L20-L23
This is why I regret introducing the passthru to Python instead of just adding everything to pythonPackages like it's done for Haskell. It's ugly but way more practical.

Exposing packageOverrides is a nice simple change that makes multiple
overrides possible, if not pretty.  It doesn't stop us doing it better
later, but I don't have the capacity to do that now.

I've said before this probably should go via an RFC but frankly I don't see that happening. This change is simple and very useful so IMO its good.

Alternative at https://github.com/NixOS/nixpkgs/pull/91850.

Still very interested into this PR, composing packageOverrides is still not obvious to me without the passthru solution.

Still very interested into this PR, composing packageOverrides is still not obvious to me without the passthru solution.

This is a super valuable quick fix for the problem of not being able to compose Python overrides.
@FRidh @jonringer Anything in the way of merging this except for the conflict? @alyssais Could you please rebase?

personally, I'm of the opinion that we should use the lib.makeScope helper.
cc @FRidh

Hello again, I would like to call on a decision for this.
AFAIK, composing packageOverrides is still a hard thing, see #223268 for latest issue with it.
If the makeScope helper is the way to go, could we document it and opt to close this PR (and document the idea of not going for this solution or explain why this is not necessarily a good thing)?

@RaitoBezarius strongly in favor of documenting the result. @NixOS/documentation-team can assist with making it nice. Who else should we involve in making the technical decision? @DavHau opinions?


[WB-7410] Set user_settings to an empty dict in offline mode in _WandbSetup__WandbSetup._load_user_settings

https://wandb.atlassian.net/browse/WB-7410
Description
Fix a minor bug in _WandbSetup__WandbSetup._load_user_settings where _server might be accessed before it is initialized.
Testing
N/A
Release Notes
Below, please enter user-facing release notes as one or more bullet points.
If your change is not user-visible, write NO RELEASE NOTES instead, with no bullet points.
------------- BEGIN RELEASE NOTES ------------------
NO RELEASE NOTES
------------- END RELEASE NOTES --------------------

Converted this PR to a draft to fix settings propagation in the wandb.init method.

This is addressed in https://github.com/wandb/client/pull/3083, closing.


Unable to connect to Actual Server

I feel like a bit of a moron right now, I can't figure out what's going on.   I've set up a vanilla install of actual with this package as part of the same docker-compose.  No reverse proxies are involved.
name: Actual Stack
services:
  actual_server:
    image: docker.io/actualbudget/actual-server:latest
    container_name: actualserver
    ports:
      - '5006:5006'
    environment:
      - ACTUAL_HTTPS_KEY=/data/selfhost.key
      - ACTUAL_HTTPS_CERT=/data/selfhost.crt
    volumes:
      - ./actual-data:/data
    restart: unless-stopped

  actual-http-api:
    image: jhonderson/actual-http-api:latest
    container_name: actualhttpapi
    volumes:
      - ./data:/data:rw
    ports:
      - 5007:5007
    environment:
      - ACTUAL_SERVER_URL=${ACTUAL_SERVER_URL}
      - ACTUAL_SERVER_PASSWORD=${ACTUAL_SERVER_PASSWORD}
      - API_KEY=${API_KEY}
    restart: on-failure

ACTUAL_SERVER_URL=https://localhost:5006
ACTUAL_SERVER_PASSWORD=XXXX000X
API_KEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Version 24.10.1, latest for actual-http-api
0 issues with Actual itself.  But I can't get get it to talk to actual.  I've tried:

by docker container name (http and https)
by localhost  (http and https)
by IP  (http and https)

And consistently get:
{"error":"Error accessing Actual Server, check Actual Server password"}

I know I must be missing something, can someone help me out?

are you using a custom cert?

are you using a custom or self-signed cert?

I am, but I didn't even think a cert was required.  I tried with no cert and a self signed cert.  I can try a signed cert if that will make a difference.

Hey there, about ACTUAL_SERVER_URL, if both containers are in the same docker network, you don’t need to use https; this is not by default though, you either have to create a docker network and have both containers use it, or make both containers use bridge network.
If actual server is exposed to the public, you can directly use the actual server custom domain, instead of localhost.

I’m not exposing it to the public, and my understanding was that by default
docker would create a bridge network for both these containers to be on.
I’ll try explicitly having a bridge, and a signed certificate later tonight
to test.
On Mon, Oct 21, 2024 at 16:49 Jhon Cardenas @.***>
wrote:

Hey there, about ACTUAL_SERVER_URL, if both containers are in the same
docker network, you don’t need to use https; this is not by default though,
you either have to create a docker network and have both containers use it,
or make both containers use bridge network.
If actual server is exposed to the public, you can directly use the actual
server custom domain, instead of localhost.
—
Reply to this email directly, view it on GitHub
https://github.com/jhonderson/actual-http-api/issues/25#issuecomment-2427937469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDYM2MK6VBN46LJR7TTGSLZ4WHH3AVCNFSM6AAAAABQJSDY3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXHEZTONBWHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

If someone might be willing to test the stack, I posted that would be greatly appreciated.  Even hearing it works for other people would keep me from tilting at windmills.

From: Robert McLellan @.>
Sent: Monday, October 21, 2024 5:48:00 PM
To: jhonderson/actual-http-api @.>
Cc: jhonderson/actual-http-api @.>; Rob @.>; Author @.***>
Subject: Re: [jhonderson/actual-http-api] Unable to connect to Actual Server (Issue #25)
I’m not exposing it to the public, and my understanding was that by default docker would create a bridge network for both these containers to be on. I’ll try explicitly having a bridge, and a signed certificate later tonight to test.
On Mon, Oct 21, 2024 at 16:49 Jhon Cardenas<EMAIL_ADDRESS>wrote:
Hey there, about ACTUAL_SERVER_URL, if both containers are in the same docker network, you don’t need to use https; this is not by default though, you either have to create a docker network and have both containers use it, or make both containers use bridge network.
If actual server is exposed to the public, you can directly use the actual server custom domain, instead of localhost.
—
Reply to this email directly, view it on GitHubhttps://github.com/jhonderson/actual-http-api/issues/25#issuecomment-2427937469, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACDYM2MK6VBN46LJR7TTGSLZ4WHH3AVCNFSM6AAAAABQJSDY3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXHEZTONBWHE.
You are receiving this because you authored the thread.Message ID: @.***>

You are right, both containers run in bridge network by default, but then you cannot use localhost within a container. You have 2 options, either to use the name of the container, I.e http://actualserver:5006.
Or keep using localhost, but adding the option network_mode: host
See this related post: https://stackoverflow.com/a/56883398

OK, still not clear why the IP or container name didn’t work but I’ll try again with a signed cert.

From: Jhon Cardenas @.>
Sent: Monday, October 21, 2024 7:23:10 PM
To: jhonderson/actual-http-api @.>
Cc: Rob @.>; Author @.>
Subject: Re: [jhonderson/actual-http-api] Unable to connect to Actual Server (Issue #25)
You are right, both containers run in bridge network by default, but then you cannot use localhost within a container. You have 2 options, either to use the name of the container, I.e http://actualserver:5006.
Or keep using localhost, but adding the option network_mode: host
See this related post: https://stackoverflow.com/a/56883398
—
Reply to this email directly, view it on GitHubhttps://github.com/jhonderson/actual-http-api/issues/25#issuecomment-2428077200, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACDYM2N3V3IHFJYZAOQCXPTZ4WZI5AVCNFSM6AAAAABQJSDY3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYGA3TOMRQGA.
You are receiving this because you authored the thread.Message ID: @.***>

I am going to try your setup locally. In the mean time, feel free to share the actual http api container logs to see if there are more details of the failure, I am guessing it’s an http timeout

I got it to work locally, here my setup:
name: test
services:
  actual_server:
    image: docker.io/actualbudget/actual-server:latest
    container_name: actualserver
    ports:
      - '5006:5006'
    volumes:
      - ./actual-data:/data
    restart: unless-stopped

  actual-http-api:
    image: jhonderson/actual-http-api:latest
    container_name: actualhttpapi
    volumes:
      - ./data:/data:rw
    ports:
      - 5007:5007
    environment:
      - ACTUAL_SERVER_URL=http://actualserver:5006
      - ACTUAL_SERVER_PASSWORD=test
      - API_KEY=test
    restart: on-failure

Here is the things you can double check:

Enter the actual web ui and setup a password. This may be obvious but if you don't have a budget created, nor a password for it, actual http api won't work
If you password has characters docker compose doesn't like, escape it like - 'ACTUAL_SERVER_PASSWORD=problematic-password'

See my comment above, I am assuming your budget is not encrypted. If it is you need to pass the encryption password through the header -H 'budget-encryption-password: test'

I'm not sure what the issue was exactly but I'm good now.  Originally I had a self-signed cert for actual.  Once I removed that, and had the http/api instance access it directly I didn't have any luck directly.  But using a reverse proxy to access the http/api instance did seem to do the trick.
Http api (HTTP) -> Actual (HTTPS) didn't work
Http api(HTTPS) -> Actual (HTTPS / self signed) didn't work
Http api (HTTP) -> Actual (HTTP) didn't work
Http api (HTTP) -> Actual (HTTPS / reverse proxy) didn't work
HTTP api (HTTPS reverse proxy) -> Actual (HTTPS / reverse proxy)  Finally successful.


Fix CodeQL alert SM03926: Security sensitive JsonWebTokenHandler validations are disabled

Fixes #6513 #6507 #6505 #6504 #6503 #6502 #6501
Description
This PR suppresses the CodeQL SM03926 alerts related to disabled ValidateAudience properties in TokenValidationParameters class.
The alerts can't be fixed because the validations take place manually in the code.
Specific Changes

Added comment to suppress SM03926 alerts in the following classes:

ChannelValidation
EmulatorValidation
EnterpriseChannelValidation
GovernmentChannelValidation
ParameterizedBotFrameworkAuthentication
SkillValidation

Testing
The unit tests passed after the changes.

Pull Request Test Coverage Report for Build 329256

0 of 0   changed or added relevant lines in 0 files are covered.
127 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-0.05%) to 79.009%

Files with Coverage Reduction
New Missed Lines
%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetNextViableTime.cs
1
90.91%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetPreviousViableTime.cs
1
90.91%

/libraries/Microsoft.Bot.Connector.Streaming/TaskExtensions.cs
1
82.61%

/libraries/Microsoft.Bot.Connector.Streaming/Transport/TransportHandler.cs
2
96.39%

/libraries/Microsoft.Bot.Connector/Authentication/SkillValidation.cs
7
47.3%

/libraries/Microsoft.Bot.Connector.Streaming/Session/StreamingSession.cs
8
89.62%

/libraries/Microsoft.Bot.Connector/Authentication/EmulatorValidation.cs
35
32.35%

/libraries/Microsoft.Bot.Connector/Authentication/ParameterizedBotFrameworkAuthentication.cs
72
0%

Totals

Change from base Build 328982:
-0.05%

Covered Lines:
25603

Relevant Lines:
32405

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll


Fnv hasher with default capacity

This PR goes on top of https://github.com/mre/hyperjson/pull/43
Changes:

Initialize entites with default capacity > 0.

This may safe some extra memory allocations.
Benchmarks are again slightly contradictional.
Please consider this PR only like an idea. Feel free to reject it if it does not bring any useful improvement

So I ran the benchmarks on my machine and the values of this branch are very close to the master branch, well within the standard deviation. That means I can't make any conclusive judgement as to what is the faster version. Maybe others can try to reproduce on their machine?
main.txt
fnv-bench.txt

Here are my benchmarks for Python 3.5, done on my laptop (debian).
master.txt
fnv-hasher.txt
fnv-hasher-with-default-capacity.txt
Here the result aggregated in one spreadsheet: https://docs.google.com/spreadsheets/d/1vrERpk-QLZYLQOHu8nh6fIAeTdEbNxp5bJEIPc-N-MM/edit?usp=sharing
However, if I run the benchmark multiple times I get different results, so yea, based on this it's hard to judge if this is a real improvement.
Would it make sense to increase number of iterations in the benchmarks?

Pretty similar to what I saw in my benchmarks.
You can control the number of iterations and rounds with the following parameters:
pipenv run pytest benchmarks --benchmark-min-rounds=BENCHMARK_MIN_ROUNDS --benchmark-warmup-iterations=NUM

The docs are here.
I haven't tried that myself, though. 😉

Ok, running the following command:
time pipenv run pytest benchmarks  --benchmark-warmup-iterations=100000 --benchmark-min-rounds=100000

Shows to me a more or less reproducible result (I've tried 2 times).
fnv-hasher branch slightly faster than master, and fnv-hasher-with-default-capacity is slightly faster than fnv-hasher. In particular (total time):
master: 	                  2m40.388s
fnv-hasher:                       2m38.193s
fnv-hasher-with-default-capacity: 2m37.594s

I'm in the process of setting up a machine for profiling. Have a dedicated Linux box now for that purpose. If anybody has time to profile the code before me, feel free to do that and add some data here.


fix(connection manager): not sleeping if failed to connect

Thanks to the fix in #62, connection errors can now be correctly caught. The library also automatically re-tries the connection, which is awesome :)
The current implementation however only sleeps on a successful connection, which means if discord isn't running the socket and error log both get spammed.
This moves the sleep outside of the match block so it runs regardless of connection outcome, meaning the library will now wait 500ms between connection retries.

Could you show the relevant logs? It only re-tries errors that happened due to a timeout, and thus does not necessarily mean a connection failure, and could just mean that Discord is being a bit slow.
On Windows, the timeout is 1 second, so waiting an extra 500 milliseconds is a bit pointless, but if you're not on Windows, there might be no waiting involved currently so I can add some delay there so it doesn't spam quite so much.

The logged error is:
2023-08-23T08:35:07.616225Z ERROR discord_presence::connection::manager: Failed to connect: IoError(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })

This currently gets logged at a rate of more than once per ms, pinning a CPU thread to 100%. I have only tested this on Linux.
The windows read/write timeouts are part of its socket, but I don't think those come into play at this stage, since the lack of timeout is on failure to connect to the socket.
This doesn't add a timeout, but rather moves the existing connection sleep to ensure it captures the new error handling code in https://github.com/jewlexx/discord-presence/commit/d0c6016c91eb5bae718e5422b67eb8cb9107bf23, since previously this just broke from the loop.

I just double-checked the original implementation, and it seems that at some point the ConnectionRefused error was changed from breaking the loop, to not. This is probably better behaviour for an error like that, and will also fix the log spamming and whatnot.
I'll keep this open for now, because there definitely is a benefit for slowing down the send/receive loop, but I'd rather not have it time out every time, and only when it needs to, because some errors, such as the Windows Pipe Timeout error, should just retry immediately. If you have any thoughts on that please don't hesitate to let me know.

I've not had time to test, but from looking at the code I believe the current issue with breaking is that it does not 'stop' the client, and there is currently no API to restart it (nor can you create a new one since the started state is static.
I can see why you'd not want the retry logic, but if it's not there the client will need to cleanly shutdown on connection error, and consumers will need a way to restart.

I believe that until it actually connects it does not ready the client, and the code does set the STARTED variable to false, as well as ending the thread. So the intended way to restart this would be to wait for the thread.join method to finish, and then call client.start again if you want to try again.

Hey, sorry for the delay but finally got a chance to sit down and test this today. You're correct, you can just re-call start and it works fine.
It's a little bit clunky right now, but with on_ready and on_error, you can use channels to detect connection success/error events in one go:
        let mut drpc = DiscordClient::new(config.id);

        drpc.on_ready(move |_| {
            event_tx
                .try_send(ServiceEvent::Ready)
                .expect("channel to be open")
        });

        drpc.on_error(move |err| {
            if err
                .event
                .get("error_message")
                .and_then(|v| v.as_str())
                .map(|str| str == "Io Error")
                .unwrap_or_default()
            {
                event_tx2
                    .try_send(ServiceEvent::Error(err.event.to_string()))
                    .expect("channel to be open");
            }
        });

I think if the connection errors can be raised as their own error type, so that the string checking isn't required, that would clean it up enough.

Yeah I'm looking into implementing that (#70), and a better way of handling the actual client variable, that works better within the event handlers.
It might be a while though, I have exams coming up so I don't have much time to work on this at the moment.

Closed in favour of #102, which is more up-to-date.


Remote file and folder delete

adds ability to delete remote files and folders
adds a configuration option to allow for an automatic local deletion after the remote deletion is done

Please note that unlike the "Delete" function from the FileTree package that sends files to Trash, this delete is permanent. Let me know if you would like it to behave more like the function in the Tree package.

Please note I wasn't able to test this PR extensively on a SFTP server as I do not have a convenient access to one. Testing of the SFTP part is especially appreciated.

Nice work, Thanks

Best FTP package now.


Choose bzt version

Codecov Report

Merging #113 into master will increase coverage by <.01%.
The diff coverage is 57.14%.

@@            Coverage Diff            @@
##           master    #113      +/-   ##
=========================================
+ Coverage    64.6%   64.6%   +<.01%
=========================================
  Files          44      44
  Lines        3602    3608       +6
  Branches      611     613       +2
=========================================
+ Hits         2327    2331       +4
- Misses       1104    1106       +2
  Partials      171     171

Impacted Files
Coverage Δ

...lugins/performance/build/PerformanceTestBuild.java
60.86% <57.14%> (+0.26%)
:arrow_up:

Continue to review full report at Codecov.

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


Python x64 and SCons Windows build support.

Dear Boost.NumPy team,
we are using Boost.NumPy and the ndarray project in a big data context at our lab. So I made the effort and made both projects x64 Python compatible, as well as the ndarrays 64bit indexed (similar to eigen3). I was mainly working on Windows and had to test the projects, so at the same time I extended the SCons build system to work with Windows.
After all changes, both projects build without any internal warnings (the numpy interface deprecation warning left aside) and are working flawlessly. I'll send pull requests for both, starting with Boost.NumPy.
Here, there wasn't much to do concerning x64 compatibility. The only related change is in boost/numpy/ndarray.hpp: the shape and stride of x64 numpy arrays are larger than int, and this can be adressed in general by using size_t.
The rest of the changes concerns building on Windows with SCons. I integrated the SConsChecks project (https://github.com/ChrislS/SConsChecks) and greatly simplified the SConscript. Apart from that, extension finding was simplified over tests and library files.
Best,
Christoph

I've finally merged the build system changes from this PR (after rebasing to separate these commits from the integer type changes).  The integer type changes are up next.

That's great to hear (also for ndarray)!

Merged to master.


ui router reload only some directives

hi guys
as I seen the documentation ... by right $state.reload can help me to reload something when executed and it will reload entire controller which had that code
but I want to made only some directives. not entire controller , is there any way to do it? thanks before also much appreciated for helping :smile:

You need to implement a custom action to reload the directives. You can ask for help about doing that on stackoverflow.


Use stable bundler release 2.2.0

bundler 2.2.0  has been released.
ref. https://rubygems.org/gems/bundler/versions/2.2.0

Windows & Yum CI fails.

Windows & Yum CI fails.

They should be fixed in other pull requests.


ListItem styles.titleContainer

there's a property i'd like know how to override in <ListItem /> there's a style called styles.titleContainer
how would I override that? I'd like to essentially float the subtitle to the right.

Thanks @charlespeters, good idea. Just added this!


Unet modelstore details

hi
Do you know where I could get more info on the unet implementation ?
for example it says 'We expect 572 x 572 x 1'
it would be great to know why, and also what was the best accuracy, which hyper parameters, etc.
thanks

Hi, the input for UNet are images with resolution 572 by 572. This is with respect to the original paper for UNet.
For the best accuracy... it really varies. I believe the pretrained model used Adam with exponential decreasing training rate at 0.98 decay over 300 epochs or something, but that is because the dataset is small.
To find the best hyper parameters, it really is a trial and error problem.
@IsaacYangSLA Any comments on this?

thanks @ethantang95
So it seems that the number of classes are hard coded to be 2 in this implementation.
any simple way to make it multi-class unet? I see in the classification examples of digits+TF, the number of classes are automatically inferred from the data, which is great!

you can always change the unet network definition itself when you download the pretrained model. This implementation was done with respect to the paper but you are definitely free to experiment with it.

when i download a pretrained unet model from model store and create model with my datasets gives error " : Message type "caffe.NetParameter" has no field named "from".".please gives me suggestion. Thank you.