Typescript definition for vex.dialogs

Please add the TypeScript "*d.ts" file to define Vex. Without them the compiler notice error and won't compile the .ts
On DefinitelyTyped github page there's only a partial define, which does not include any reference for vex.dialogs class/file

As far as I know this project hasn't used TypeScript in its history. Is this file something that we should be concerned about, or can you add it to your project because you're using TypeScript?

Yes, I'm using typescript and it needs definitions for classes/libraries I used in the project.
As far as I know, the Definetly Typed github project is an open project to define those libraries which are not written in typescript (and so they don't have the .ts file to get definitions).
They just create a .d.ts file which define the structure of the library classes and methods.
Here there's the define for Vex:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/36d40a63a05b5cb3413737fbdf7c9a2a26f211fd/vex-js/vex-js.d.ts

Oh, thank you, I hadn't heard of Definitely Typed. Should I submit a PR over there to update the vex .d.ts for version 3?

I opened this issue in the meantime: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/12951
Thanks for the heads up!

I think so, but I don't know very well how those file are manteined.
Due it's a github project I think you can add some changes and add missing fields if you want.
I tried to map the Vex '.js' files to extract the definition file, but I have not fully understand how library works. Unfortunately by now I have commented out my code where Vex is called, because Visual Studio does not compile a .NET project if there're TypeScript errors on the client side.

Can I BUMP this please?
Having a great deal of trouble trying to incorporate vex-js and vex-dialog together in a dotnet core/typescript project.
I have the 'vex-js' part coming in ok, along with a .d.ts file for typing, but there is nothing in that file describing the 'vex-dialog' side of things, and looking at the demos, thats what is mostly used?
Reading the quickstart, it states using webpack/etc prohibits you from using the combined minified js file, so I added NPM entries for 'vex-js', 'vex-dialog', and '@types/vex-js'
I assumed I would do something like:
import * as vex from 'vex-js';
import 'vex-dialog';

vex.defaultOptions.className = 'vex-theme-os'; //this is fine
vex.dialog.confirm({...                     //this is not fine (nothing in the .d.ts for it)

NOTE: I apologise in advance; This is NOT really a vex issue, it is a webpack/d.ts issue,
but after MUCH googling, I'm honestly at a loss as to the appropriate webpack/typescript (yet vex-js aware) place to post this.

https://github.com/tivnet/DefinitelyTyped/blob/master/types/vex-js/index.d.ts - this one? I think we need a PR over there for vex-dialog, then.
Is it possible/does it make sense to add a new types directory, e.g. types/vex-dialog/index.d.ts?

Yes, that appears to be the .d.ts I have.
I'm afraid I have been away from web-dev for a little while so I'm not 100% on the current VS+TS+NPM tooling chain, but the .d.ts was obtained from a separate npm package "@types/vex-js": "^2.3.29"
I'm not aware how original products package their index.d.ts for npm deployment, sorry.

Can I bump this again, it is possible to include your own type definitions in your NPM Package, you just need to add the .d.ts file to your codebase and reference it in your package.json.
More on that here: http://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html
Once that is done you can request to have the definitions removed from DefinitelyTyped to avoid confusion.


Added support for 'any' type of dictionary to be 'serialized' into javascriptcontext.

Needed this to support a dictionary that inherited the generic dictionary.

Cool


13146 fss tooling add support for search batch attributes endpoint

This PR contains FSS Tooling - add support for search batch attributes endpoint in dot net client implementation changes

Thanks Chris for review. I have updated the value of the UKHOAssemblyVersionPrefix variable to 1.2 (from 1.1) in azure-pipelines.yml.


Updated tag_version

fixed #2703

I believe switching to use test.properties file hasn't been done yet. Probably need to update the line https://github.com/adoptium/aqa-tests/blob/master/external/common_functions.sh#L465 too.

I believe switching to use test.properties file hasn't been done yet. Probably need to update the line https://github.com/adoptium/aqa-tests/blob/master/external/common_functions.sh#L465 too.

Updated


Configurator can't open files

Any help would be much appreciated.
Got a RPI 3 with Hass.io (Home Assistant 0.102.0, Configurator 3,6) and are trying to open files in the configurator, but I'm getting a stage error, in the window for showing the yaml code.
"'utf-8' codec can't decode byte 0xb0 in position 37: invalid start byte".
I think i got something to do with the file names every file got "._" in the beginning of the file name, but i don't know.

Here are the logs from the Hass.io add-on page:
Log
[18:37:31] INFO: Add-on running
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
no field package.preload['resty.core']
no file './resty/core.lua'
no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/5.1/resty/core.lua'
no file '/usr/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/common/resty/core.lua'
no file '/usr/share/lua/common/resty/core/init.lua'
no file './resty/core.so'
no file '/usr/local/lib/lua/5.1/resty/core.so'
no file '/usr/lib/lua/5.1/resty/core.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file './resty.so'
no file '/usr/local/lib/lua/5.1/resty.so'
no file '/usr/lib/lua/5.1/resty.so'
no file '/usr/local/lib/lua/5.1/loadall.so')
2019/11/22 18:37:31 [notice] 24#24: using the "epoll" event method
2019/11/22 18:37:31 [notice] 24#24: nginx/1.16.1
2019/11/22 18:37:31 [notice] 24#24: OS: Linux 4.14.98-v7
2019/11/22 18:37:31 [notice] 24#24: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2019/11/22 18:37:31 [notice] 24#24: start worker processes
2019/11/22 18:37:31 [notice] 24#24: start worker process 31
INFO:2019-11-22 18:37:32,155:hass_configurator.configurator:Starting server
INFO:2019-11-22 18:37:32,157:hass_configurator.configurator:Listening on: http://<IP_ADDRESS>:80
INFO:2019-11-22 18:38:03,861:hass_configurator.configurator:<IP_ADDRESS> - "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [22/Nov/2019:18:38:04 +0100] "GET / HTTP/1.1" 200 52056 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Safari/605.1.15"
INFO:2019-11-22 18:38:04,521:hass_configurator.configurator:<IP_ADDRESS> - "GET /api/file?filename=/config/._configuration.yaml HTTP/1.1" 200 -
WARNING:2019-11-22 18:38:04,523:hass_configurator.configurator:'utf-8' codec can't decode byte 0xb0 in position 37: invalid start byte
<IP_ADDRESS> - - [22/Nov/2019:18:38:04 +0100] "GET /api/file?filename=/config/._configuration.yaml HTTP/1.1" 200 82 "http://192.168.xx.xxx:8123/api/hassio_ingress/6cTLZ2etaibEbwYxscQkbWZldbtP32XqhShY717Ghyk/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Safari/605.1.15"
INFO:2019-11-22 18:38:04,626:hass_configurator.configurator:<IP_ADDRESS> - "GET /api/listdir?path=. HTTP/1.1" 200 -
<IP_ADDRESS> - - [22/Nov/2019:18:38:04 +0100] "GET /api/listdir?path=. HTTP/1.1" 200 16250 "http://192.168.xx.xxx:8123/api/hassio_ingress/6cTLZ2etaibEbwYxscQkbWZldbtP32XqhShY717Ghyk/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Safari/605.1.15"

This is related to your file or Configurator itself.
Please report this upstream on the Configurator repository: https://github.com/danielperna84/hass-configurator
Thanks! 👍


Is this code be able to operate on different version of Pytorch??

Is this code able to operate on different version of Pytorch??

Currently, we only support the environment provided in the docker image.


Add Deploy config advanced flags ui

Fixes #1743

that looks cool!

What are valid values for the compile encoding?   Can we make it a
combobox?  What about the jar_splitting_excludes what is the value in there
supposed to look like?
On Thu, Feb 1, 2018 at 2:40 PM, Etan Shaul<EMAIL_ADDRESS>wrote:

@etanshaul commented on this pull request.
In google-cloud-tools-plugin/src/com/google/cloud/tools/
intellij/appengine/cloud/AppEngineDeploymentConfigurationPanel.java
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1865#discussion_r165466007
:

@@ -52,6 +54,18 @@
private HyperlinkLabel appEngineCostWarningLabel;
private JLabel serviceLabel;
private JCheckBox hiddenValidationTrigger;

private JTextField compileEncodingTextField;

you could have the tabbed panel field live in the common panel, but then
all of the inner components of the "advanced" tab live in
AppEngineStandardDeploymentEditor
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1865#discussion_r165466007,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HVwAAb0q45syhDov1Sv_rBWSRjbLks5tQhNAgaJpZM4Ryzu6
.

@patflynn I don't know all the valid values for compile_encoding and jar_splitting_excludes. The only documentation I found on them was this https://github.com/GoogleCloudPlatform/gcloud-maven-plugin#application-deployment-goal, and it doesn't mention the valid values.

Nice design! Are we sure we won't have more boolean properties in the future? They are sitting nicely in a grid now but if we keep adding them then it might grow beyond being beautiful.
Also, it feels good they use the same property name one'd use with SDK itself, but slightly strange for UI - maybe we should add small question mark which brings us to the description page? I don't know about the amount of work, but adding a tooltip for each property with short description of the property would be even more cool.

I wouldn't worry. I don't think we'll be adding any more staging params.
On Fri, Feb 2, 2018 at 2:34 PM, Ivan Portyankin<EMAIL_ADDRESS>wrote:

Nice design! Are we sure we won't have more boolean properties in the
future? They are sitting nicely in a grid now but if we keep adding them
then it might grow beyond being beautiful.
Also, it feels good they use the same property name one'd use with SDK
itself, but slightly strange for UI - maybe we should add small question
mark which brings us to the description page? I don't know about the amount
of work, but adding a tooltip for each property with short description of
the property would be even more cool.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1865#issuecomment-362683992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HdsjdbsRmxbv6mSzeKg6s6a8Wl-4ks5tQ2MqgaJpZM4Ryzu6
.

@nbashirbello
it sounds like the excludes are only applicable when enable jar splitting is enabled.
Perhaps we should only show it when enable jar splitting is enabled, and have some documentation to indicate that it should be a comma separated lists of file suffixes to exclude with an example?

@nbashirbello thanks for the refactoring. Just some minor comments from me.
to follow up on @patflynn's comment: if the excludes field is only available if "jar splitting" is checked, then perhaps we can make this even clearer in the UI by having it be a child component (i.e. visually nested underneath it)?

on second though, if we have some helper wording around this, then there is no need really to visually nest it like I suggested above

@nbashirbello we discussed in the meeting today updating the labels of the advanced staging properties to something more human readable. E.g.:
enable_jar_classes -> Enable JAR Classes

Added a help icon in the staging tab that currently links to  https://github.com/GoogleCloudPlatform/gcloud-maven-plugin#application-deployment-goal. Would update later to show a file with the tablized version of the flags with their description

Looks nice, maybe we can think of placing the help icon to the right bottom corner? Now it kind of creates a large margin between the tab and the entire flags UI.

When "Enable JAR Splitting" is disabled and there are no existing values for "JAR Splitting excludes"

When "Enable JAR Splitting" is disabled and there is a value for "JAR Splitting excludes"

My 2¢: it seems odd to have a text field that's controlled by what appears to be a sub-button.

@briandealwis that can probably be solved by making the text field a child (visually indented) of the checkbox. wdyt? I'm open to other suggestions.

Makes sense to me!

Does it make sense for the user to enable the up-to-date check?

The staging flags will soon be configurable from the appengine-web.xml so UI support is no longer need.


Replace sand blocks with actors

Replace sand blocks with robots and zombies.

revert zombies's and robots's images for left and right movement

Also create a model for the enemies (zombies/robots)


Issue53

#53 on top of #76

This change is

@onecloud-sean could look at matrix statuses?

nice!

POlling log action is under question, matrixproject shows latest, but it should be available for run that is MatrixConfiguration that doesn't show expected Actions....

I'm a little unclear on what you'd like me to look at. I can try running this change against a matrix project and see what happens. Is there something in particular I should be looking for though?

I want avoid mess of logic between different job types. The question on how statuses would look for matrix runs, they are kind of parallel runs in workflow.
Matrix-plugin structure: MatrixProject (config, root polling log, pr state "storage"), MatrixConfiguration (ItemGroup that is "build" of MatrixProject, that produces MatrixRuns), MatrixRun - "build" where real build/checkout really happens.
:atm: preStatus works with MatrixProject.getActiveConfigurations() that produces many long context statuses (at least for test case). If MatrixRun would set other context (new logic that you made for workflow), then it wouldn't match preStatus contexts.
I have feeling that preStatus for matrix project should set only 1 context status and then final status should be set with some Aggregateable Publisher  (afair matrix-project has special publisher that could be run in MatrixConfiguration).

I might not be understanding the whole picture here but trying to manage a per-run status of a matrix build seems like trouble. It might work OK for a 1-dimensional matrix but, IMHO, anything beyond that will start getting cluttered. I think the per-run information of a matrix build is best left to the details. For example a single status representing the whole matrix that had a detail message such as "19 of 21 matrix runs passed".
So basically, I think I agree with you.

pollinglogaction vs BuildAction is crazy but i seems found how it logs and attaches clickable action on matrix builds pages.

didn't found how to do aggregatable status, maybe better not to use prestatus for matrix jobs until...

ps i hate matrix-project 😠

polling logs reworked...

Made more fixes.

Trigger extraction for runs (publishers/build steps) requires custom extractor.
Polling log action requires custom extractor to get log file path.
Repository storage seems works fine with plain Job.
prestatus works somehow when it matches to default publishers/builders. I think they can be improved in future.

CHange become huge, any other changes/fixes should go separately.


cursor: default for disabled  in pagination

Looks like I made too many changes and pushed origin out of date for this pull request. I've manually resolved this though—sorry for the confusion, and thanks for the addition :).


allow sl-chart options to be set after render

There are cases when the highcharts options need to be updated after render, such as when the options depend on the data of the chart.
Specific use case: I'm using plotbands to show an uptime meter in the background while graphing data at the same time.

@alxyuu Please add this as a proposal to https://github.com/softlayer/sl-ember-components/issues/1254

@notmessenger is it not possible to work this myself? I already have the changes ready


Update PerfForesightConsumerType

Made some fixes in the language and description of the model and the code. One mistake left to be clarified.
Paragraph in the subsection Example parameter values to construct an instance of PerfForesightConsumerType that elaborates, "In contrast, we could specify a life-cycle model...", which states that the parameter T_cycle could be set to $1$. However, it is already set to $1$ and this would not allow room for age-varying parameters of income growth and survival probability.
Ready to merge in all other aspects.
CC: @alanlujan91

Ah, that should say "cycles", not "T_cycle". I'll look at that comment; we
don't want misleading or false information in docstrings.
On Fri, Nov 10, 2023 at 1:35 PM Siddarth Venkatesh @.***>
wrote:

Made some fixes in the language and description of the model and the code.
One mistake left to be clarified.
Paragraph in the subsection Example parameter values to construct an
instance of PerfForesightConsumerType that elaborates, "In contrast, we
could specify a life-cycle model...", which states that the parameter
T_cycle could be set to $1$. However, it is already set to $1$ and this
would not allow room for age-varying parameters of income growth and
survival probability.
Ready to merge in all other aspects.
You can view, comment on, or merge this pull request online at:
https://github.com/econ-ark/HARK/pull/1358
Commit Summary

c70ebc9
https://github.com/econ-ark/HARK/pull/1358/commits/c70ebc9afaaa1f1c6c75b24826084d8b6c8add2e
Update PerfForesightConsumerType.ipynb

File Changes
(1 file https://github.com/econ-ark/HARK/pull/1358/files)

M examples/ConsIndShockModel/PerfForesightConsumerType.ipynb
https://github.com/econ-ark/HARK/pull/1358/files#diff-9d66369772ee85955dcef8ed98feb176516db8bfab21a53cddd62060909394c1
(128)

Patch Links:

https://github.com/econ-ark/HARK/pull/1358.patch
https://github.com/econ-ark/HARK/pull/1358.diff

—
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/pull/1358, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFOS3PHILJDCJHEE6XDYDZXV7AVCNFSM6AAAAAA7GR3OYKVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DQMJVG44DOMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@mnwhite The thing I pointed out, and you were looking into, is still pending to be resolved. Will open a new PR to resolve that once these stylistic issues have been decided upon. Thanks.


abs -> fabs

Because warnings suck.
Also by the way Examples/PMTweenExamples/Classes/AdditiveVC.m gives a static analyser warning because a line of code is never used, why is it there anyways 😛

Thanks for taking care of those warnings; apologies for taking so long to merge, been rather busy lately!


Unify proxy modes, introduce UDP protocol detection.

Description
This is work in progress on #5535.
What's has been done so far (and why):

Removed transparent mode in UDP. The way transparent mode for UDP is implemented is far from ideal: It's only supported on Linux, requires sudo for the whole process, prevents full coverage of udp.py and is not even used/enabled.
Together with #5543, I'll plan to do re-add transparent UDP mode later in a similar fashion, i.e. a separate process, asking for sudo if necessary, setting everything up for the user. In the meantime, udp.py has now full coverage.
Updated AsyncioServerInstance and ProxyMode to support both protocols for one ProxyMode. In the process, the need for additional ServerInstances disappeared, so ProxyModes now fully describe proto, port and layer.
Removed make_connection_id. Since we don't know on what layer we'll detect what protocol, we can't use the DNS-ID in ServerManager connection-ID trick anymore - same as goes for QUIC, if we don't want to alter SendData and DataReceived (see https://github.com/mitmproxy/mitmproxy/pull/5435#pullrequestreview-1075694658).
Changed the proxy mode syntax to what was discussed in #5535. Also DNS has now --mode reverse:dns://<IP_ADDRESS> if used with an upstream, --mode dns will launch a local-resolve server.
Adjusted DNS layer to match packets by their ID. As mentioned above, this was previously done through ServerManager connection-IDs, but if we detect DNS higher up, or in the future use some transparent mode, this can't be done this way anymore.
Copied and adjusted TCP layer decisions for UDP.

@mhils: Before I'm adjusting and (re-)adding tests, could you maybe have a quick look as to whether the way the "new" modes are implemented is something you'd sign off on? Thanks :)

Looks fantastic now! 🍰 😃

@mhils This should be ready now :) I've updated the docs as well, that's why I didn't want to merge before you've had the chance to look over the wording. Once we support QUIC and HTTP3, I think it's time to add a table as in #5535.


change task worker node to list; add target worker node to cache

Signed-off-by: Yaliang Wu<EMAIL_ADDRESS>Description

ML task may run on multiple nodes. We save all worker nodes as String in ML task doc which is not easy to use. This PR changed worker nodes in MLTask as List
Add target worker node to cache

Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #656 (b68034b) into 2.x (6fb7970) will decrease coverage by 0.79%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##                2.x     #656      +/-   ##
============================================
- Coverage     84.58%   83.79%   -0.80%
+ Complexity      998      985      -13
============================================
  Files            93       93
  Lines          3582     3597      +15
  Branches        325      327       +2
============================================
- Hits           3030     3014      -16
- Misses          417      443      +26
- Partials        135      140       +5

Flag
Coverage Δ

ml-commons
83.79% <75.00%> (-0.80%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...java/org/opensearch/ml/profile/MLModelProfile.java
46.29% <40.00%> (-0.65%)
:arrow_down:

...ain/java/org/opensearch/ml/model/MLModelCache.java
86.36% <71.42%> (-1.78%)
:arrow_down:

...va/org/opensearch/ml/model/MLModelCacheHelper.java
95.08% <75.00%> (-0.69%)
:arrow_down:

...earch/ml/action/load/TransportLoadModelAction.java
90.09% <100.00%> (-0.10%)
:arrow_down:

...h/ml/action/upload/TransportUploadModelAction.java
98.63% <100.00%> (ø)

...n/java/org/opensearch/ml/model/MLModelManager.java
78.77% <100.00%> (ø)

...va/org/opensearch/ml/task/MLPredictTaskRunner.java
82.14% <100.00%> (ø)

...pensearch/ml/task/MLTrainAndPredictTaskRunner.java
78.26% <100.00%> (ø)

...a/org/opensearch/ml/task/MLTrainingTaskRunner.java
74.76% <100.00%> (ø)

.../cluster/MLCommonsClusterManagerEventListener.java
65.62% <0.00%> (-12.50%)
:arrow_down:

... and 4 more

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


Use svn switch instead of svn update for cached_copy

If using the cached_copy, capistrano issues a svn update command, if a cached copy is available. But if you switch the branch or tag, that command won't do anything useful. If you use svn switch, it'll switch to the new repo location (if necessary) AND update to the given revision. So there is no downside in using svn switch instead svn update.

This fix breaks deployment of projects that use svn externals. svn switch with a revision number concerns itself only with the main project and does not implicitly 'svn update' any svn externals. Our projects rely heavily on svn externals, so this fix broke them thoroughly.
Is there a maintainable way to roll this back or add an explicit 'svn update' to the process following the svn switch command in my local project?

@boutell - do you know if there's a way to make svnswitch work for projects
using externals. (also word to the wise, lock Capistrano in your Gemfile,
when your production server is at the hands of a Gem, you'd better test
well before upgrading Cap, it's a mistake that many people make)

Update: I patched the gem on my local copy to do the update command that was removed - after the switch command that was added, so that we also get the benefits this change was originally intended to achieve.
Yes, this updates the main project twice, but I see no simple way to avoid that and not break updates of projects that use svn:externals.
Hopefully this change can be made upstream so that we can stay current without re-breaking our deploys (:

leehambley: thanks for the advice. How would I lock Capistrano? I'm googling but seem to be looking for the wrong things. As you might guess I'm not really a Ruby guy. Not yet anyway.
svn switch does not appear to have any love for externals at all. Which makes sense because externals are really separate checkouts anyway.
But on reflection there is no real penalty for fixing it as I suggest. Since the main project is already at the desired revision after the switch command, determing that will take almost no time, and then it'll move on to updating the externals.

Bump - any hope of this simple and correct fix to a pretty serious regression for those of us who use externals? (The fix is to do both - do your svn switch command and then the svn update. The latter will add very little overhead for those not using externals because it will just determine it is on the correct revision, and it's correct for everyone.)

Ok, I was waiting for the time to get into the SVN docs… You can expect
this to be pulled today, and pushed as a prerelease if what you say is
accurate I don't see anything standing in the way.

Thanks, I really appreciate it!

Pre-release gem pushed 2.10.0.pre. Please be aware that the feature version is bumped because also deploy:symlink is renamed for Rake 0.9.x compatibility, is has now become deploy:create_symlink.
I literally havent tried this version, but the tests look good - please feedback any problems you run into.

I see that in 2.12.0, 2.14.2 this issue still exists. Is that correct? All those use just svn switch bot not svn update, resulting in a small headache trying to figure out what was bundler talking about, when it said that my gemspecs changed :)

I'd just like to draw your attention to our announcement on 23-10-2017 -

https://github.com/capistrano/capistrano/blob/master/CHANGELOG.md#3100-2017-10-23

As of this release, version 2.x of Capistrano is officially End of Life. No further releases of 2.x series are planned, and pull requests against 2.x are no longer accepted. The maintainers encourage you to upgrade to 3.x if possible.

This issue you're commenting on is nearly 7 years old! We'd be glad to help you upgrade to a none-EOL version of Capistrano, catch us on the mailing list, and/or our guides/etc!

@leehambley thank you for your quick reply, I just wanted to know / to let others know if this is indeed fixed in versions mentioned here :-)
I just have some old projects (tons of them) which each use some old version of Capistrano and these legacy projects are not actively maintained anymore and I had to just redeploy two of them. I moved some of these projects to git, which solved this issue. I use Capistrano 3 in newer projects, but don't have resources to migrate all those projects to newer one. That's my fault though...


Usage of useDataChannelMessage

Describe the problem
In order to use useDataChannelMessage we have to specify channelId twice. First when we initialize the hook, second when we send message with payload like this:
const { send } = useDataChannelMessages({ channelId: 'say_hello' });

const sentRegards = async () => {
    await send({
      channelId: 'say_hello',
      payload: 'Hi mate',
   });
 };

I know that this is not important and has no impact of our usage of this beautiful library but i think adding channelId twice feels weird to me. :D
Describe the proposed solution
Either after initializing hook with channelId, i think send shouldn't require me channelId anymore and should only accept payload or we should add channelId within send method.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

yeah, that's a fair point.
The idea behind it was that we wanted to make it possible to use multiple channelIds within the same hook, so that you could say
const { send } = useDataChannelMessages({ channelId: ['say_hello', 'say_goodbye'] });

const sentRegards = async () => {
    await send({
      channelId: 'say_hello',
      payload: 'Hi mate',
   });
 };

but maybe that's actually not needed.
If we were to restrict the hook to a single channelId we could let the send method only take the payload type of course.
cc @Ocupe and @keepingitneil for discussing this

Oh, i understand now! Thank you for your quick response. :)

Though about it some more, I think it's more user friendly when the send method is simplified.
It's maybe even nicer to reason about different channel handlers if each of them has their "own" hook

Thank you so much for quick response and result! :)


removing IP from previous scan

I am testing Goscan, which I really like so far.  I loaded one IP and ran through the process.  But I can’t load another IP or remove the previous IP, it shows the first IP.  I can’t clear either. Is there a way to remove an IP once you have completed the goscan for that IP? Because of this issue, I am only able to use goscan once.

Hi @Shotokanman, what happens if you try to load target ... again?

Marco when I tried to load another IP, nothing happens. When I show targets, it contains the old ipaddress. I can't change it or load any new endpoints to scan.

I see, adding the ability to remove targets is an enhancement already requested in #14.
But we should definitely add the ability to add new targets as well.
If someone has some bandwidth to work on this it would be really helpful!

Hello!
I have some bandwidth available and I'd love to give it a try if that's ok
A few question about the feature:

Which name would be better? "unload" / "delete" / "remove" ?
What kind of arguments should be accepted? Only the IP ?
What is the expected behaviour when you delete the target? does it also delete all the linked objects ( ports / hosts / services ) ?

Hi @PouuleT, thank you for volunteering to help! 🙏
Regarding your questions:

Which name would be better? "unload" / "delete" / "remove" ?

What about unload?

What kind of arguments should be accepted? Only the IP ?

It would be good to mirror the behaviour of the load command, starting with the ability to remove only one single target.
Something like: unload target SINGLE <IP/32>

What is the expected behaviour when you delete the target? does it also delete all the linked objects ( ports / hosts / services ) ?

I think it would be easier to take an incremental approach, starting by removing just the target and then, in a future iteration, we could try to remove also all the linked objects. What do you think?

I like the incremental approach! I'll go with unload target SINGLE <IP/32> which will only remove the target.
I'll try to make the PR before the end of the week


Python version for environment on Apple Silicon

Getting the error ... "ERROR: Could not find a version that satisfies the requirement tensorflow (from versions: none)" .  What version python was this tested with?

If you are using Homebrew, the default python is now 3.12, which is not yet support by many of the deep learning platforms. Install python 3.11 (brew install<EMAIL_ADDRESS>and either make it the default, or create an environment with python 3.11: (python3.11 -m venv py311env && cd py311env && source bin/activate).
In short, python 3.11 (or older) is required.

That works ... thanks!

Tested on Apple M3 Max w/64 GB RAM.. works well


Add Czech translation

I'd love to contribute and add Czech translation. I am native Czech speaker and I want to use my client in my language.

Thanks for your contribution! I'll add this whenever I update the mod next :)


use sass-loader errors

Versions

nuxt: ^2.15.3
node: v14.15.0
yarn: 1.22.5

Reproduction

Additional Details

Steps to reproduce

create nuxt + ts project
yarn add sass/node-sass sass-loader -D
yarn dev
Failed to compile with 1 errors

What is Expected?
use sass-loader@11 OK
What is actually happening?
ERROR  Failed to compile with 1 errors
ERROR  in ./assets/css/main.scss
Module build failed (from ./node_modules/sass-lo
ader/dist/cjs.js):
TypeError: this.getOptions is not a function
at Object.loader

use sass-loader@10,it's OK，the @11 failed to compile.

use sass-loader@10,it's OK，the 11 failed to compile.


Autoconfiguration of private network interface

Would it be possible to add auto-configuration of private interface in VPS when --vultr-private-networking is enabled?
I'm thinking abount establishing docker swarm using vultr private network only.
Thanks for advance.

I'm testing with -vultr-os-id=160 (buntu 14.04 x64) and --vultr-private-networking=true.

one more test:
docker-machine create --driver vultr --vultr-api-key=myAPIKey --vultr-region-id=7 --vultr-plan-id=29 --vultr-ipv6=1 --vultr-private-networking=1 --engine-env DEV=1 testowa5
Running pre-create checks...
(testowa5) Validating Vultr VPS parameters...
(testowa5) getting client
(testowa5) getting client
(testowa5) getting client
Creating machine...
(testowa5) getting client
(testowa5) Creating Vultr VPS...
(testowa5) Using PXE boot
(testowa5) Provisioning RancherOS (stable)
(testowa5) getting client
(testowa5) getting client
(testowa5) Waiting for IP address to become available...
(testowa5) Created Vultr VPS ID: 3323436, Public IP: <IP_ADDRESS>, Private IP: <IP_ADDRESS>
Waiting for machine to be running, this may take a few minutes...
(testowa5) getting client
(testowa5) getting client
(testowa5) getting client
(testowa5) getting client
(testowa5) getting client
(testowa5) getting client
(testowa5) getting client
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Detecting the provisioner...
Provisioning with rancheros...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
(testowa5) getting client
Docker is up and running!
To see how to connect Docker to this machine, run: docker-machine env testowa5
[root@vultr ~]# docker-machine ssh testowa5
(testowa5) getting client
[rancher@testowa5 ~]$ ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 5A:00:00:1E:4E:C6
          inet6 addr: fe80::5800:ff:fe1e:4ec6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:396 (396.0 B)  TX bytes:1439 (1.4 KiB)

[rancher@testowa5 ~]$ hostname
testowa5
[rancher@testowa5 ~]$ cat /opt/rancher/bin/start.sh
cat: can't open '/opt/rancher/bin/start.sh': No such file or directory

Auto-configuration of private network interface eth1 is already implemented. But only for machines that are created with the default RancherOS. For Ubuntu machines you can actually pass a Cloud-init user data file with the --vultr-userdata parameter.
See here for a template: https://github.com/janeczku/docker-machine-vultr/blob/master/vultr.go#L481-L499
Pozdro :smile:

there is still some issue with autoconfiguration of rancheros. See my second test with default os.
pozdro.

This has been fixed in https://github.com/janeczku/docker-machine-vultr/releases/tag/v1.0.3.
Auto-configuration of private network interface eth1 is fully working again with RancherOS.


[feature request] Interface and type names EMOJI Support!!

Since all type declarations and infos will be omitted when compiled to JS, it would be safe and great to have interface and type names with emoji support !!!
Just like this:

And codes will be like:

I'm a little 🐑 ish on this

Looking at the unicode character data, emoji chars seems to be marked as symbols; which makes them invalid identifier characters (neither ID_Start  nor ID_Continue) names as per the ECMAScript spec; and since these names exist at runtime, we have no way of naming them in the resulting JS code.

@mhegazy Type & declarations infos will be omitted and will not show up in the resulting JS code, is there any possibility or future plans on this? This is gonna be a really cool feature, just like Swift.

This feature is a really bad idea IMO. Makes it more difficult to both write and read code (use it a few times and it becomes annoying to read the code). Just my two cents on this.

This is gonna be a really cool feature, just like Swift.

I know :(. but we are committed to be a super-set of JS, and part of that is not diverging from the ES spec on issues that may cause conflicts, like identifier names. I would recommend making this an ECMAScript proposal instead. if TC39 approves it, we will do it.


Fix build

small typescript error slipped in w/my big change

ya I think its narrowing doesn't work across closures in all cases


Dynamically switching mask in same input box not functioning as expected

I have a select box I'm using to determine the proper mask for a text input. What happens is that the direction (ltr/rtl) property of the mask seems to inherit the state of the initially selected mask if you switch/change between the 2. I have created a test case in jsFiddle with specific steps to recreate the issue. A big thank you in advance to anyone who could provide some valuable input!
Test Case: http://jsfiddle.net/csoseman/c6eLfcqp/

@csoseman ,
Sorry for the late reply, it seems that when you select local first, then it behaves correctly, but when you select the standard option first it behaves wrong.
I will have a look at it this week.
best regards,
Robin

@csoseman ,
Just upgrade to the latest version.
Have a look http://jsfiddle.net/c6eLfcqp/14/

Hi, I'm trying to add/remove a % suffix depending on some criteria but updating with the "option" method does not work.
http://jsfiddle.net/23sm7err/7/
Seems the only way for now is to recreate the mask.
Cheers

@gkostov ,
The option method is intented for adding extra options like callbacks, etc at a later time to the mask.  Changing the mask itself or options which are used to generate the mask will not change the mask behavior.

Oh, that explains it then. Thank you for the very quick response.
Not a great deal, but was wondering what the reason could be for this decision? It feels like a glitch there because the method does actually update the internal options hash. I use this like:
var inputMask = Inputmask({alias:'decimal', suffix:''}).mask(someElement);

// ... then later when I need to add the suffix
inputMask.option({suffix:'%'});  // only update "suffix" in the internal options hash
inputMask.mask(inputMask.el);  // rebuild the mask

which feels a bit hacky but does the job well :-)
Cheers

@gkostov ,
I did have a quick look at the option method and actually I did implement remasking, , I shall see why the above does not work without calling the remasking.

@gkostov ,
Have a try with the latest greatest  ;-)

Works just fine now :-)
Great work, thanks!


Render LaTeX to image

This feature would require significant dependencies on the host machine depending on the solution. Using SymPy requires LaTeX to be installed.
This might also require the use of temporary files.

This would probably be better done with matplotlib, but I'm going to use tex2png and subprocess instead.


hyundai: fix carState.stockAeb/carState.stockFcw

The current logic isn't correct
https://github.com/commaai/openpilot/blob/0c95493dc0cbc5d3dec59a50ac5476573041942d/selfdrive/car/hyundai/carstate.py#L112-L117
stock seems to use CF_VSM_Warn == 1 for warning the driver and higher values for braking, although it is possible to command braking even when CF_VSM_Warn == 1
stock definitely uses CF_VSM_Warn == 2 with CF_VSM_DecCmdAct = 1 as well as CF_VSM_Warn == 3 with FCA_CmdAct = 1 to command braking (and in both cases uses CR_VSM_DecCmd for the amount of braking requested)
Here is my best guess but there still may be edge cases where it doesn't brake until you start pressing the brake pedal or something

stockFcw = CF_VSM_Warn != 0 and CF_VSM_DecCmdAct == 0 and FCA_CmdAct == 0
stockAeb = CF_VSM_Warn != 0 and (CF_VSM_DecCmdAct == 0 or FCA_CmdAct == 0)

Example routes:
02c45f73a2e5c6e9|2020-06-24--12-20-18
c7d0d7dde77d49ce|2022-06-24--19-02-59

This is what I have noticed on the 2021 Hyundai Sonata as well.

CF_VSM_DecCmdAct != 0 or FCA_CmdAct != 0 you mean?

This user also got a FCW: 6111bd7df5043394|2022-08-08--09-48-29--15


why did you add the testset to the training data?

why did you add the testset to the training data?
This is different from what we did before.
Is this reasonable?

Please take a look here, it's incorrect to put the test set into the train set, there's no reason for this, and I don't know why the code is doing it this way. I checked the repository, and it's not there.

 Please take a look here, it's incorrect to put the test set into the train set, there's no reason for this, and I don't know why the code is doing it this way. I checked the repository, and it's not there.

https://github.com/pengfeiliHEU/M2I2/issues/10#issuecomment-1834061712
OK，that is in the last version really.


Update README.md

Some stuff I noticed in the README that needed updating.

should we get the merge?


Enum values that are defined in OpenAPI spec don't appear to be set properly in generated types

As part of my OpenAPI spec, I have an enum mapping continents to their abbreviations. In the spec this looks as follows:
    ContinentEnum:
      enum:
      - AF
      - AN
      - AS
      - EU
      - NA
      - OC
      - SA
      type: string
      description: |-
        * `AF` - Africa
        * `AN` - Antarctica
        * `AS` - Asia
        * `EU` - Europe
        * `NA` - North America
        * `OC` - Oceania
        * `SA` - South America

The openapi-generator code generated for that definition looks as follows:
        /// * `AF` - Africa
        /// * `AN` - Antarctica
        /// * `AS` - Asia
        /// * `EU` - Europe
        /// * `NA` - North America
        /// * `OC` - Oceania
        /// * `SA` - South America
        ///
        /// - Remark: Generated from `#/components/schemas/ContinentEnum`.
        @frozen internal enum ContinentEnum: String, Codable, Hashable, Sendable {
            case AF = "AF"
            case AN = "AN"
            case AS = "AS"
            case EU = "EU"
            case NA = "NA"
            case OC = "OC"
            case SA = "SA"
        }

It thus appears that instead of using the values provided in the spec for each enum case, the generator assigns the key of each case as also being the value.
Given the above, I'd personally prefer to see these enum cases defined with the values from the OpenApi document, e.g.
            case AF = "Africa"
            case AN = "Antarctica"
            case AS = "Asia"
            case EU = `"Europe"

I'm also not sure if this behavior is expected, or perhaps an issue with my OpenAPI spec.

The OpenAPI specification doesn't assign any special meaning to description, it's just freeform text. There's no place in the OpenAPI document to provide the "name" for a case that's distinct from its raw value.
So unfortunately this is a limitation of the OpenAPI 3.1.0 specification itself, not of this generator.

Now, technically, this generator could try to somehow parse patterns from the description, but since those patterns are completely freeform, it's unlikely to work reliably, and would result in the generator having to support various heuristics that aren't required by the OpenAPI specification.

To summarize, your OpenAPI document is correct, and is the best you can do with OpenAPI 3.1.0. If this is an issue for you, you could try engaging with the OpenAPI specification community and pitch an improvement for a future revision of the OpenAPI specification.

Thank you so much for the clarification, it's super greatly appreciated and really helped me to better understand why this is how it is.
Surprised to hear there's no official specification for that as enums are quite common IMO. Not a huge deal to me personally as I can just solve this by rolling a wrapper of my own to have the proper values assigned, but I sure will look at their process for making proposals when I find the time.
Thanks again for the wonderful help!

One (possibly not very pretty) alternative idea would be to use a oneOf of string enums, each with one case.
So instead of:
type: string
enum:
  - A
  - B
  - C

You could use:
oneOf:
  - type: string
    description: My custom A description
    enum: [A]
  - type: string
    description: My custom B description
    enum: [B]
  - type: string
    description: My custom C description
    enum: [C]

Although it'll generate a bit more verbose code, and will likely be less performant. But just thought I'd mention it.

Ohhh, that does seem like a super smart suggestion considering the current limitations with enums, thanks for putting that in my head! :-)
Since I developed the server for this in Python using the Django framework, I'm using drf-spectacular for OpenAPI schema generation.
It's a quite modular package, so I'll just play with this a little and see if I can hack something together that changes how these enums are defined in the spec file. 👍

Ah, gotcha. It was looking alright from the example you provided, but I absolutely agree that having value1, value2 etc as case names wouldn't be desirable, and in fact would be harder to reason about than what we have right now.
Another thought, is this something which could be addressed by a generator plugin at a future point, similar to what is described in #112?
Not necessarily saying a plugin for this should be provided as part of this package, but maybe a way for adopters to override certain schema generation logic if desired.

For sure open to ideas for other plugin types. If you have a specific idea of the function kind you'd want to implement in a plugin (e.g., for the example in #112 it's something like func swiftSafeName(name: String, kind: ...) -> String), please add a comment to #112.


Revert "Doc-3268 sei"

Reverts harness/developer-hub#2385

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Error when trying to use getBreakpointFromWidth

I'm trying to use getBreakpointFromWidth from this recipe, but I get "Unexpected token (5:12)" error:

(^ a reference to the responsiveUtils file)
This is essentially what's going on in my related code:
import { getBreakpointFromWidth } from 'react-grid-layout/lib/responsiveUtils.js'

type BreakpointsType = {
    readonly lg: number;
    readonly md: number;
    readonly sm: number;
    readonly xs: number;
    readonly xxs: number;
}
const BREAKPOINTS: BreakpointsType = {
  lg: 1200,
  md: 1024,
  sm: 768,
  xs: 480,
  xxs: 0
};

const myFunction = (screenWidth: number): String => {
// ... stuff
console.log(
    "current breakpoint:",
    getBreakpointFromWidth(BREAKPOINTS, screenWidth)
  );
// ... other stuff
}

I tried upgrading from  "react-grid-layout": "^0.18.2" to "react-grid-layout": "^1.2.0," upgrading typescript, npm installing, but none of it seemed to resolve the issue... Am I doing something wrong? Please help?
Thanks!

RGL uses flow  so you cannot import raw code directly from lib without also enabling flow in your own build chain.
You must import from the distribution. From the index file (https://github.com/react-grid-layout/react-grid-layout/blob/master/index.js) it looks like you could:
import { Responsive } from 'react-grid-layout';

Responsive.utils.getBreakpointFromWidth( ... )


CATS on Eirini failure: apps/rolling_deploy.go:27

Following CATS test fails:
[Fail] [apps] Rolling deploys [BeforeEach] deploys the app with zero downtime
/home/vic/suse/cf-acceptance-tests/apps/rolling_deploy.go:27

https://github.com/suse/cf-acceptance-tests/blob/master/apps/rolling_deploy.go#L68
To reproduce in cats apply following patch: (as silly as it looks)
diff --git a/apps/rolling_deploy.go b/apps/rolling_deploy.go
index a153292e..5dd854d7 100644
--- a/apps/rolling_deploy.go
+++ b/apps/rolling_deploy.go
@@ -67,7 +67,7 @@ var _ = AppsDescribe("Rolling deploys", func() {
    Expect(cf.Cf(
      "push", appName,
      "-p", assets.NewAssets().Dora,
-     "--strategy=rolling",
+     "--strategy", "rolling",
    ).Wait(Config.CfPushTimeoutDuration())).To(Exit(0))
  })
 })

To reproduce manually:

Deploy an app:

$ cf push -p cf-acceptance-tests/assets/dora dora

$ cf a
Getting apps in org system / space tmp as admin...

name   requested state   processes             routes
dora   started           web:1/1, worker:0/0   dora.vic-cap.ci.kubecf.charmedquarks.me

$ while true; sleep 1; do curl -k -H Expect: -s https://dora.vic-cap.ci.kubecf.charmedquarks.me/; done

Update the app with strategy rolling:

$ cf push dora -p cf-acceptance-tests/assets/dora/ --strategy rolling

Problem:
This second cf push gets stuck and timeouts. It does start 2 pods for the same app (so, 1 new):
$ cf a
Getting apps in org system / space tmp as admin...

name   requested state   processes             routes
dora   started           web:1/1, web:1/1, worker:0/0   dora.vic-cap.ci.kubecf.charmedquarks.me

And there's no downtime (checked with curl).  But the old pod never goes away and the push timeouts. I don't see errors on scheduler-0/logs, but I see a bunch of errors on eirini: desirer.get-instance.failed-to-get-statefulset, handler.get-app-instances.bifrost-failed

@jimmykarily this seems like a bug in Eirini - old pods don't get deleted when performing a rolling deployment. Is the Eirini team looking into this?

I don't think so, we never created an issue on the Eirini backlog for this. Just did: https://www.pivotaltracker.com/story/show/175610610

I still can't tell what the exact problem is but I have same data points. I run the steps both in kubecf and cf-for-k8s (where it works). The process in kubecf is as follows:
These are the logs of the eirini (opi) pod when following the reproduce steps. First the CC tries to delete the process guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2926","version":"8e8aa685-b998-4968-819b-50a75b2a2190"}} but it doesn't exist (this is also true for cf-for-k8s). Then (in kubecf only) staging happens. When it's done there is a desire request for an app with the same guid but this time the version field has changed. While this was happening, I was watching the records on the processes table in the cloud controller database and I saw before my own eyes the version column of that process record changing a value.
I couldn't connect to the cf-for-k8s database to watch for such a change there but by looking at the cf-for-k8s logs, the version of the desired process stays the same from beginning to the end.
Maybe the staging process that happens in between (in kubecf) sends back the staging result with the wrong version field and CC writes that in the database with no validation whatsoever? If that's true, then it could explain why after the second push, the first process doesn't get cleanedup (it tries to cleanup with the first and no longer valid version?).
eirini pod logs in kubecf:
{"timestamp":"2020-11-10T12:40:36.153248366Z","level":"debug","source":"handler","message":"handler.stop-app.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2908","version":""}}
{"timestamp":"2020-11-10T12:40:36.164029265Z","level":"debug","source":"desirer","message":"desirer.stop.statefulset-does-not-exist","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2926","version":"8e8aa685-b998-4968-819b-50a75b2a2190"}}
{"timestamp":"2020-11-10T12:40:42.023541228Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2909"}}
{"timestamp":"2020-11-10T12:40:43.638159063Z","level":"debug","source":"convert","message":"convert.convert-staging","data":{"app-id":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","staging-guid":"f8a9a412-c08d-423a-b6b4-d6db327bcdd1"}}
{"timestamp":"2020-11-10T12:41:12.040336036Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2910"}}
{"timestamp":"2020-11-10T12:41:24.338952683Z","level":"debug","source":"buildpack-staging-bifrost","message":"buildpack-staging-bifrost.complete-staging.Complete staging","data":{"session":"29","task-guid":"f8a9a412-c08d-423a-b6b4-d6db327bcdd1"}}
2020/11/10 12:41:24 [DEBUG] POST https://internal_user:4E7H3zKuRN9lYcItKjUbCb3752tvhISaxKlvra2xQkFrzP7H81oDd4nxZPLXiDGY@api.kubecf.svc:9023/internal/v3/staging/f8a9a412-c08d-423a-b6b4-d6db327bcdd1/build_completed?start=false
{"timestamp":"2020-11-10T12:41:24.423848126Z","level":"info","source":"handler","message":"handler.staging-handler.staging-complete.posted-staging-complete","data":{"session":"1.30","staging-guid":"f8a9a412-c08d-423a-b6b4-d6db327bcdd1"}}
{"timestamp":"2020-11-10T12:41:26.719504897Z","level":"debug","source":"handler","message":"handler.get-app.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2911","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:26.727798644Z","level":"error","source":"desirer","message":"desirer.get.failed-to-get-statefulset","data":{"error":"not found","guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2929","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:26.727892652Z","level":"error","source":"handler","message":"handler.get-app.failed-to-get-lrp","data":{"error":"failed to get app: not found","guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2911","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:26.745778751Z","level":"debug","source":"handler","message":"handler.desire-app.requested","data":{"app_guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682-149f9ea9-ed9f-424a-94ce-7aec23894d2e","session":"2912","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:26.836485898Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2913","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:29.910235985Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2914","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:32.988124306Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2915","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:36.074679648Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2916","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:36.224863008Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","session":"2917","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:41:42.023115801Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2918"}}
{"timestamp":"2020-11-10T12:41:42.050911304Z","level":"debug","source":"handler","message":"handler.update-app.requested","data":{"guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682-149f9ea9-ed9f-424a-94ce-7aec23894d2e","session":"2919","version":"149f9ea9-ed9f-424a-94ce-7aec23894d2e"}}
{"timestamp":"2020-11-10T12:42:12.030522073Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2920"}}
{"timestamp":"2020-11-10T12:42:42.023819005Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2921"}}
{"timestamp":"2020-11-10T12:43:12.030291817Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2922"}}
{"timestamp":"2020-11-10T12:43:42.046120821Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2923"}}
{"timestamp":"2020-11-10T12:44:12.031187032Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2924"}}
{"timestamp":"2020-11-10T12:44:42.025267140Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2925"}}
{"timestamp":"2020-11-10T12:45:03.689272434Z","level":"debug","source":"convert","message":"convert.convert-staging","data":{"app-id":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","staging-guid":"7826aaaa-03e2-4bb9-9f59-79a367cf7e21"}}
{"timestamp":"2020-11-10T12:45:12.041838824Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2926"}}
{"timestamp":"2020-11-10T12:45:41.534470070Z","level":"debug","source":"buildpack-staging-bifrost","message":"buildpack-staging-bifrost.complete-staging.Complete staging","data":{"session":"31","task-guid":"7826aaaa-03e2-4bb9-9f59-79a367cf7e21"}}
2020/11/10 12:45:41 [DEBUG] POST https://internal_user:4E7H3zKuRN9lYcItKjUbCb3752tvhISaxKlvra2xQkFrzP7H81oDd4nxZPLXiDGY@api.kubecf.svc:9023/internal/v3/staging/7826aaaa-03e2-4bb9-9f59-79a367cf7e21/build_completed?start=false
{"timestamp":"2020-11-10T12:45:41.606378164Z","level":"info","source":"handler","message":"handler.staging-handler.staging-complete.posted-staging-complete","data":{"session":"1.32","staging-guid":"7826aaaa-03e2-4bb9-9f59-79a367cf7e21"}}
{"timestamp":"2020-11-10T12:45:42.035548843Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2927"}}
{"timestamp":"2020-11-10T12:45:43.423147155Z","level":"debug","source":"handler","message":"handler.get-app.requested","data":{"guid":"0229c797-98c5-4e7c-9947-00fe7904758c","session":"2928","version":"bab175be-239c-4e0f-a19c-a7be311d0086"}}
{"timestamp":"2020-11-10T12:45:43.432345956Z","level":"error","source":"desirer","message":"desirer.get.failed-to-get-statefulset","data":{"error":"not found","guid":"0229c797-98c5-4e7c-9947-00fe7904758c","session":"2947","version":"bab175be-239c-4e0f-a19c-a7be311d0086"}}
{"timestamp":"2020-11-10T12:45:43.432446193Z","level":"error","source":"handler","message":"handler.get-app.failed-to-get-lrp","data":{"error":"failed to get app: not found","guid":"0229c797-98c5-4e7c-9947-00fe7904758c","session":"2928","version":"bab175be-239c-4e0f-a19c-a7be311d0086"}}
{"timestamp":"2020-11-10T12:45:43.452631071Z","level":"debug","source":"handler","message":"handler.desire-app.requested","data":{"app_guid":"ff38e73a-1029-4c7b-a87a-cd20c83e1682","guid":"0229c797-98c5-4e7c-9947-00fe7904758c-bab175be-239c-4e0f-a19c-a7be311d0086","session":"2929","version":"bab175be-239c-4e0f-a19c-a7be311d0086"}}
{"timestamp":"2020-11-10T12:45:43.466190029Z","level":"debug","source":"handler","message":"handler.get-app.requested","data":{"guid":"0229c797-98c5-4e7c-9947-00fe7904758c","session":"2930","version":"bab175be-239c-4e0f-a19c-a7be311d0086"}}
{"timestamp":"2020-11-10T12:45:43.480523414Z","level":"debug","source":"handler","message":"handler.update-app.requested","data":{"guid":"0229c797-98c5-4e7c-9947-00fe7904758c-bab175be-239c-4e0f-a19c-a7be311d0086","session":"2931","version":"bab175be-239c-4e0f-a19c-a7be311d0086"}}
{"timestamp":"2020-11-10T12:46:12.028013981Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2932"}}
{"timestamp":"2020-11-10T12:46:12.064843398Z","level":"debug","source":"handler","message":"handler.update-app.requested","data":{"guid":"0229c797-98c5-4e7c-9947-00fe7904758c-bab175be-239c-4e0f-a19c-a7be311d0086","session":"2933","version":"bab175be-239c-4e0f-a19c-a7be311d0086"}}
{"timestamp":"2020-11-10T12:46:42.024725522Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"2934"}}

eirini pod logs in cf-for-k8s:
{"timestamp":"2020-11-10T13:01:34.334011286Z","level":"debug","source":"handler","message":"handler.get-app.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3143","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:34.338613919Z","level":"error","source":"desirer","message":"desirer.get.failed-to-get-statefulset","data":{"error":"not found","guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3148","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:34.338985001Z","level":"info","source":"handler","message":"handler.get-app.app-not-found","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3143","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:34.363620428Z","level":"debug","source":"handler","message":"handler.desire-app.requested","data":{"app_guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838-741aea05-01d1-41db-bad3-4f0cf853ca67","session":"3144","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:34.769661906Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3145","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:37.820973750Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3146","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:40.903369647Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3147","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:43.967512086Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3148","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:46.038915751Z","level":"debug","source":"handler","message":"handler.list-apps.requested","data":{"session":"3149"}}
{"timestamp":"2020-11-10T13:01:46.084490587Z","level":"debug","source":"handler","message":"handler.update-app.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838-741aea05-01d1-41db-bad3-4f0cf853ca67","session":"3150","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:47.038572318Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3151","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:50.111202708Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3152","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}
{"timestamp":"2020-11-10T13:01:50.293728339Z","level":"debug","source":"handler","message":"handler.get-app-instances.requested","data":{"guid":"c86c6569-dde0-47bb-88fa-777c3f7a7838","session":"3153","version":"741aea05-01d1-41db-bad3-4f0cf853ca67"}}

Opened an issue here: https://github.com/cloudfoundry/cloud_controller_ng/issues/1952

Based on the answer on the above issue, the problem seems to be that we are completely missing the deployment_updater:

https://github.com/cloudfoundry/cloud_controller_ng/blob/master/docs/v3/zero_downtime_deployments.md#enabling-deployments
https://github.com/cloudfoundry/cloud_controller_ng/blob/master/Procfile#L5


[Select] Remaining tasks

Add chromatic stories
Add tests
Improve mobile experience

pointer handling works well when using slowly, but it has the tendency to close from under you when going quickly, need to check what's going on here
on mobile, there's an issue with positioning when the page is pinch-zoomed. I think it might be due to visual viewport vs. layout viewport and the fact we position: fixed.

Investigate to see if we can add support for animation (opening/closing)
see if we can improve this scenario: if I press down on the ScrollUpButton or ScrollDownButton and hold while it scrolls, when I release, it will select the first or last item because the scroll button disappears and mouse is now released on an item
test is it can work with native label and not just our Label

@benoitgrelard Can you also look at the option of supplying a max-height to the content / viewport? Currently when setting the max-height for the content and attempting to scroll, the container sticks to the bottom of the window.

Also, when using the select with groups of items, the separator is being announced as a group.
In the example you have with food, the screen reader says there's 5 groups when there are only 3 (plus 2 separators)

Hey @Kinbaum, someone is keen! haha
How have been playing with it given it's not even out yet 😀
Guessing you're following the PRs/npm, etc? 😀
In any case:

Also, when using the select with groups of items, the separator is being announced as a group.
In the example you have with food, the screen reader says there's 5 groups when there are only 3 (plus 2 separators)

I've handled that one and made the separators visual only for now.

Can you also look at the option of supplying a max-height to the content / viewport? Currently when setting the max-height for the content and attempting to scroll, the container sticks to the bottom of the window.

I don't think I understand what you mean here.

Ah I see the issue here...

@Kinbaum it would be good to understand your use-case? why do you need to set a max-height?

This version of Select is designed to function like the MacOS select in terms of UX. So the heuristics are basically to present as many options as possible on the screen whilst maintaining alignment with the trigger as close as possible.
So setting a maxHeight wouldn't be desirable here.
If we provide later a "simpler" version of a select which just displays the items in a dropdown underneath the trigger without alignment then you'd be able to do it and it might make "some" sense to do it in this case as it would all drop down underneath.

Sorry, but I've also been testing the Select without you releasing it officially yet 😅
https://codesandbox.io/s/clever-edison-nbsy3o?file=/App.js
If you have a Select within a Dialog, and if you then tab to the Select and press enter you are not able to use arrow keys to navigate the items, while outside of the Dialog it works fine.

Sorry, but I've also been testing the Select without you releasing it officially yet 😅
https://codesandbox.io/s/clever-edison-nbsy3o?file=/App.js
If you have a Select within a Dialog, and if you then tab to the Select and press enter you are not able to use arrow keys to navigate the items, while outside of the Dialog it works fine.

I don't see that issue, what you are describing seems to work fine in the sandbox.

Sorry, but I've also been testing the Select without you releasing it officially yet 😅
https://codesandbox.io/s/clever-edison-nbsy3o?file=/App.js
If you have a Select within a Dialog, and if you then tab to the Select and press enter you are not able to use arrow keys to navigate the items, while outside of the Dialog it works fine.

I don't see that issue, what you are describing seems to work fine in the sandbox.

If you hover the Select it works again, I am using Chrome on Windows 11.
Precise steps to reproduce: (make sure mouse does not end up hovering the Select viewport)

Left click "Edit profile"
Press "Enter" on keyboard (Select should open at this point)
Use up and down arrow keys (nothing should happen)
Hover any Select item with your mouse
Use up and down arrow keys (should work now)

I can also click anywhere in the modal, then click the Select, and as long as the mouse is not hovering any item the arrow keys do nothing.

I can't replicate on Chrome MacOS, I will try it on Windows see if it makes a difference.

Sorry I can't see it here either, that's Chrome 91 on Windows 11:
https://user-images.githubusercontent.com/1539897/155707031-8a943f76-a399-42aa-a3e4-7ebb8bdbd75b.mov

Just asked two people on mac to try and reproduce. They were able to reproduce, but the funny part is that the problem only exists when the entire options list is viewable on screen, so e.g. if the window is short enough that the scroll buttons appear, then it works 🤷♂

Ah thanks I can see it now.
I'll take a look at what's going on.

Ah I see the issue here... @Kinbaum it would be good to understand your use-case? why do you need to set a max-height?

@jjenzz i think this is just a matter of visual preference, especially for a really long list of items. Since radix components are just primitives (not opinionated with the css), I would expect to have control over this and have things continue to behave the same (within reason), just like all the other primitives.

Ah I see the issue here... @Kinbaum it would be good to understand your use-case? why do you need to set a max-height?

@benoitgrelard @jjenzz i think this is just a matter of visual preference, especially for a really long list of items. Since radix components are just primitives (not opinionated with the css), I would expect to have control over this and have things continue to behave the same (within reason), just like all the other primitives.

I understand, this is somewhat less true and more difficult for this one because of how complex the positioning is though. That said we'll see if we can accommodate and worse case I'm sure we'll provide a simpler dropdown version soon.

@Fumler addressed in #1200

Facing this issue #1205 with select, hoping you can address it in your remaining tasks.

Using the official example https://fbwlh5.csb.app/ on mobile iOS Safari I get a weird behaviour where I need to click focus away from the trigger to activate the select content again.
Reproduce

load https://fbwlh5.csb.app/ on mobile
click select
options are shown
select value
options are hidden and select is focused
click select (you can see the black focus border dissapears but no options are shown)
click select again
Options are shown

https://user-images.githubusercontent.com/24416970/156182631-2006e70d-919c-41c5-9765-65244cfb5f68.mp4
The normal expected behaviour

select value
select is focused
click select and the options are showed again

works in all other dekstop browsers that I have tested.

I see:

test is it can work with native label and not just our Label

does that mean it already works with radix Label? If so, can you provide an example? My attempt did not work.

I see:

test is it can work with native label and not just our Label

does that mean it already works with radix Label? If so, can you provide an example? My attempt did not work.

@acc-nicholas Yes it does:
<Label>
  What is your age?
  <Select.Root defaultValue="18-40">
    <Select.Trigger className={triggerClass}>
      …
    </Select.Trigger>
    …
  </Select.Root>
</Label>

// or

<Label htmlFor="age-label">What is your age?</Label>
<Select.Root defaultValue="18-40">
  <Select.Trigger className={triggerClass} id="age-label">
    …
  </Select.Trigger>
  …
</Select.Root>

Is there a way for us to allow scroll outside while the select is open? If not, this feels rather opinionated (the forced focus lock)

@UTkzhang, at the moment it isn't possible. That being said, if we offered the possibility to go non-modal like other components, this one will have to close on scroll anyway because of the complexity of alignment so not sure how much you'd gain from that being a possibility.

Close on scroll to me seems like a better solution than a force lock

It's not really about it being a better solution, they are for different concerns.
I think there might be a valid point to offer modality support like we do for other primitives, ability to scroll (and scroll on close) is just a part of non-modal mode.

Understood, I am for it

Select search: allows to use an input as a trigger and type some text to filter or select an item
Select multi: allows to select multiple elements and display them as tags
Select creatable: allows to type text in an input even if not available in the items list and commit it

These three specifically would be very important for us.

Having a simpler select would be nice. I have a State select that has 50 options and without a max-height it uses the entire window height... feels odd.

Hi! Thanks for your work, we are supper happy using Radix since a couple months ago.
Can you please include the multiple attr to this component?  :)

Hi,
I would like to ask if you plan to add support for async infinite loading, something like what Adobe React Spectrum Picker has.
https://react-spectrum.adobe.com/react-spectrum/Picker.html#asynchronous-loading
Their onLoadMore prop is a game changer.
Select components are often used with async lists. Having an option to trigger some action when the scroll position is close to the end allows using infinite loading instead of loading all the options at once.


fix: Change "Open In" Images to inline SVG

No longer needed, GitHub fixed the issue.
https://support.github.com/ticket/personal/0/2524584


Add when conditions to commonly used processors

Description
This change adds "when" conditional support to the following processors

grok (grok_when)
parse_json (parse_when)
add_entries (add_when on each entry)
convert_entry_type (convert_when)
copy_value (copy_when on each entry)
delete_entries (delete_when)
list_to_map (list_to_map_when)
rename_keys (rename_when on each entry)
split_string (split_when on each entry)
substitute_string (substitute_when on each entry)

This PR also fixes a bug that occurred when the parse_json processor is used on a key that does not exist in the Event, resulting in an an exception that results in Events being dropped
Issues Resolved
closes #2613
Check List

[x] New functionality includes testing.
[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks great! One comment below. Also, can we update the doc as a follow-up?

Good call will update the docs in a follow up PR

@graytaylor0 , More important that the documentation in this repository is the user documentation on opensearch.org. Please create an issue in https://github.com/opensearch-project/documentation-website requesting documentation updates for this feature.


Invisible notification window gets enumerated

Some times dwm-win32 grabs an invisible notification window on Windows 10 and then it is enumerated when moving between windows, even though it is invisible

This has been irritating me. I haven't bothered to fix it yet since hadn't had time. I added a special writelog key binding. If you try v0.0.15 release and you hit this please try mod+control+l and it should write a file called dwm-win32.log which should contain the state of the windows. Feel free to paste it here on the one that you think shouldn't be shown. I will do the same if I see it. I need to figure out what the client is so that I can ignore it.

Thanks :) I am gonna try working as well on a more general solution as well, because there might be more cases like this with other invisible windows and it's definitely a bug

It is a bug, I'm not sure where since I haven't debuged much. It could be due to race conditions.
Sometime I quite dwm-win32 and start again and it no longer considers it visible which means I could add a hotkey to recompute or automatically do it when windows get rearranged. I want to look at logs before I add the hack.

@prabirshrestha Yah I do that as well XD, it is interesting it is caught since I am pretty sure there are checks for visibility of windows before catching them, looking into this RN :)

#33 Merged.


Bots stay at a low amount

I'm using 200 private proxies the bot amount stays low like at 10 there are no errors.

Are you looking at the Bot Alive count that was just added? I found a bug in it that I'm fixing that is displaying the wrong number.

No i'm looking at a custom bot counter that shows how many were connected not alive

I see what you're talking about, I'll look into it. Out of the 200, about how many connect?

About 10-12

Really? I'm testing with 120 and get about 100. Are you running it on your local pc?

I tested it with my pc and on c9.io and with a vps.

Can you paste your custom counter here? And it could also be that your network can't handle it

@dahquan yeah it might be my network. Give me a second i'm going to check my usage when ever I run the bots

it's working perfect with vps but how you did to set up on c9 bro? i tried but i failed i mooved to koding vm

@Wartoz make the c9.io workspace public because if its not it cannot access the link/inject or whatever.

Ehh I fixed it by adding like 7k public proxies still only get like 250 out of 7.3k proxies but what ever i'm getting 250

How to run the bots on a vps???


Enable authless services

Description
Enable services that have no authentication. This can be useful for OAuth flows or hosting Streamlit dashboard.
Fixes: https://github.com/orchest/orchest/issues/487
Checklist

[x] The documentation reflects the changes.
[x] I have manually tested the application to make sure the changes don’t cause any downstream issues, which includes making sure ./orchest status --ext is not reporting failures when Orchest is running.

Apart from some beauty changes, the overall (high-level) structure looks good to me. Only question I have here is: https://github.com/orchest/orchest/pull/486#discussion_r715598558
Nice work! :muscle: