exec /entrypoint.sh: no such file or directory

Hi,
I've done the little steps from your website https://effective-programmer.com/quick-web-application-setup-using-php8-lumen-and-docker-eba310d1996a. But when I start the container "docker-lumen-app-web", the container stops and in the logfile I can find the message "exec /entrypoint.sh: no such file or directory".
Why does it happen?
Greetings,
Sandra

I was not able to repro this problem, as you can see this line should have copied the container/entrypoint.sh to /entrypoint:
https://github.com/naveed125/docker-lumen-app/blob/main/Dockerfile#L48
Can you try running the following commands:
docker compose down
docker compose up -d --force-recreate

I've run the listed commands but problem exists anymore.
Some details to my system:

Windows 10
WSL ist active
Hyper V ist deactivated

I tested the file with an other path. I moved it to the directory where the Dockerfile is. Of course I edited the path for the entrypoint.sh in Dockerfile but same problem.
Redis and mysql container are running.

I was able to repro the issue on windows. The issue was that vendor directory was missing due to the docker-compose volume directive. My fix should fix the issue. Let me know if it doesn't. Thanks for reporting it.

It doesn't work for me :-(
What I've done:

docker compose down
docker system prune -f
git pull
docker compose up -d --force-recreate
docker exec -it docker-lumen-app-web-1 composer install

And then I get the error
Error response from daemon: Container 3934b8adab8a26c6a2c46603d6be3bafd6fa0fcab2c85fe70fdd65eb0707b593 is restarting, wait until the container is running

Can you try docker compose build before step 4?

Nope same error.
Error response from daemon: Container 7eb25e16fc795cf054041f02edf3b30aeff66b737d0756c2e451c4980595a16e is restarting, wait until the container is running
Docker Desktop Log shows the error exec /entrypoint.sh: no such file or directory.

This is some kind of weird docker caching issue and I was able to reproduce it! To fix it, I made a small unimpactful change to entrypoint.sh script and then it worked. Here is my full log:
C:\Users\navee\projects>git clone https://github.com/naveed125/docker-lumen-app.git
Cloning into 'docker-lumen-app'...
remote: Enumerating objects: 146, done.
remote: Counting objects: 100% (146/146), done.
Receiving objects: 100% (146/146), 49.90 KiB | 4.54 MiB/s, done.
remote: Compressing objects:  80% (86/107)
remote: Compressing objects: 100% (107/107), done.
remote: Total 146 (delta 51), reused 108 (delta 23), pack-reused 0

C:\Users\navee\projects>cd docker-lumen-app

---- I CHANGED entrypoint.sh HERE, SEE DIFF BELOW -----

C:\Users\navee\projects\docker-lumen-app>git diff
warning: LF will be replaced by CRLF in container/entrypoint.sh.
The file will have its original line endings in your working directory
diff --git a/container/entrypoint.sh b/container/entrypoint.sh
index 4465dde..b75515f 100755
--- a/container/entrypoint.sh
+++ b/container/entrypoint.sh
@@ -1,5 +1,7 @@
 #!/bin/sh

+echo Starting container ...   <---- this is what i added in entrypoint.sh
+
 if [ ! -d ./vendor ]; then
   composer install
 fi

C:\Users\navee\projects\docker-lumen-app>docker compose build --no-cache
[+] Building 19.6s (17/17) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 1.53kB                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/alpine:3.14                                                                                1.3s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 297.22kB                                                                                0.0s
 => CACHED [ 1/12] FROM docker.io/library/alpine:3.14@sha256:0f2d5c38dd7a4f4f733e688e3a6733cb5ab1ac6e3cb4603a5dd564e5bfb80eed                                                                                0.0s
 => [ 2/12] RUN apk --no-cache add   curl   nginx   php8   php8-ctype   php8-curl   php8-dom   php8-fpm   php8-gd   php8-intl   php8-json   php8-mbstring   php8-mysqli   php8-opcache   php8-openssl   php8-phar    4.2s
 => [ 3/12] RUN ln -s /usr/bin/php8 /usr/bin/php                                                                                0.4s
 => [ 4/12] RUN curl -sS https://getcomposer.org/installer | php &&     chmod +x composer.phar &&     mv composer.phar /usr/local/bin/composer                                                                       3.0s
 => [ 5/12] COPY container/nginx.conf /etc/nginx/nginx.conf                                                                                0.0s
 => [ 6/12] COPY container/fpm-pool.conf /etc/php8/php-fpm.d/www.conf                                                                                0.0s
 => [ 7/12] COPY container/php.ini /etc/php8/conf.d/custom.ini                                                                                0.0s
 => [ 8/12] COPY container/supervisord.conf /etc/supervisor/conf.d/supervisord.conf                                                                                0.0s
 => [ 9/12] COPY container/entrypoint.sh /entrypoint.sh                                                                                0.0s
 => [10/12] WORKDIR /var/www                                                                                0.0s
 => [11/12] COPY src/ /var/www/                                                                                0.0s
 => [12/12] RUN composer install --prefer-dist --no-dev                                                                                9.6s
 => exporting to image                                                                                0.8s
 => => exporting layers                                                                                0.8s
 => => writing image sha256:525a295f6855f0336e63205f7bbfdb7377ef0169fbd50ef9563bd46e5dc02b8b                                                                                0.0s
 => => naming to docker.io/library/docker-lumen-app_web                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them

C:\Users\navee\projects\docker-lumen-app>docker compose up --force-recreate
[+] Running 4/4
 - Network docker-lumen-app_default    Created                                                                                0.0s
 - Container docker-lumen-app-redis-1  Created                                                                                0.8s
 - Container docker-lumen-app-db-1     Created                                                                                0.8s
 - Container docker-lumen-app-web-1    Created                                                                                0.1s
Attaching to docker-lumen-app-db-1, docker-lumen-app-redis-1, docker-lumen-app-web-1
docker-lumen-app-redis-1  | 1:C 02 Nov 2023 08:41:21.450 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
docker-lumen-app-redis-1  | 1:C 02 Nov 2023 08:41:21.450 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
docker-lumen-app-redis-1  | 1:C 02 Nov 2023 08:41:21.450 * Redis version=7.2.2, bits=64, commit=00000000, modified=0, pid=1, just started
docker-lumen-app-redis-1  | 1:C 02 Nov 2023 08:41:21.450 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
docker-lumen-app-redis-1  | 1:M 02 Nov 2023 08:41:21.451 * monotonic clock: POSIX clock_gettime
docker-lumen-app-redis-1  | 1:M 02 Nov 2023 08:41:21.451 * Running mode=standalone, port=6379.
docker-lumen-app-redis-1  | 1:M 02 Nov 2023 08:41:21.452 * Server initialized
docker-lumen-app-redis-1  | 1:M 02 Nov 2023 08:41:21.452 * Ready to accept connections tcp
docker-lumen-app-db-1     | 2023-11-02 08:41:21+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.2.0-1.el8 started.
docker-lumen-app-db-1     | 2023-11-02 08:41:21+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
docker-lumen-app-db-1     | 2023-11-02 08:41:21+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.2.0-1.el8 started.
docker-lumen-app-db-1     | 2023-11-02 08:41:22+00:00 [Note] [Entrypoint]: Initializing database files
docker-lumen-app-db-1     | 2023-11-02T08:41:22.184920Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
docker-lumen-app-db-1     | 2023-11-02T08:41:22.186604Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
docker-lumen-app-db-1     | 2023-11-02T08:41:22.186930Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
docker-lumen-app-db-1     | 2023-11-02T08:41:22.186956Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.2.0) initializing of server in progress as process 82
docker-lumen-app-db-1     | 2023-11-02T08:41:22.196429Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
docker-lumen-app-db-1     | 2023-11-02T08:41:22.204548Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
docker-lumen-app-web-1    | Starting container ...
docker-lumen-app-web-1    | Installing dependencies from lock file (including require-dev)
docker-lumen-app-web-1    | Verifying lock file contents can be installed on current platform.
docker-lumen-app-web-1    | Package operations: 107 installs, 0 updates, 0 removals
docker-lumen-app-web-1    |   - Downloading fakerphp/faker (v1.17.0)
docker-lumen-app-db-1     | 2023-11-02T08:41:23.128056Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
docker-lumen-app-web-1    |   - Downloading hamcrest/hamcrest-php (v2.0.1)
docker-lumen-app-web-1    |   - Downloading mockery/mockery (1.4.4)
docker-lumen-app-web-1    |   - Downloading phpdocumentor/reflection-common (2.2.0)
docker-lumen-app-web-1    |   - Downloading phpdocumentor/type-resolver (1.5.1)
docker-lumen-app-web-1    |   - Downloading phpdocumentor/reflection-docblock (5.3.0)
....

Now it's working!
I am so much thankful, that you helped me so detailed.

Issue will be closed now.


Feature/ba 167 clean up

This PR:

Clears out any unused component files
Removes any unnecessary markup from the remaining files

@Braedencraig not a ton to actually review. I was just clearing out the markup on the components we're keeping to make that process a bit smoother.


Change in scheduling strategy

Hi,
Started docker swarm manager using binpack strategy and then later I decided to change it to spread strategy on the same port, is this kind implementation is available in docker swarm?
docker run -d -p 32768:2375 swarm manage --strategy "binpack" token://da0d4fd2d37068a4cbf891dda0378d5e
//
Bhargava Tadi

Assuming you mean that you stopped the running manager and ran it again with the command you wrote -  The manager will schedule using the strategy you asked for from that point on. Notice that the formerly allocated containers will not be re-balanced or anything of that sort. Hope this helps.

If I want to change the strategy allocation of running manager, then is it possible?

Not that I am aware.

Thank you Doronp!
I would like to know if this feature is available in the Swarm or not, I would like to own the issue and try to solve it.

Any other inputs are welcome, is this valid question? I want to work on this item if this is not available.

@bhar19 we welcome your contribution! I suggest closing this issue and creating a proposal for the changes you are proposing.

Closing due to lack of activity. Please reopen if you wish to continue discussing it.


Added armeria-bucket4j to throttle based on token buckets

…#2394):

Implemented advanced throttling TokenBucketThrottlingStrategy based on Token-Bucket rate-limiting algorithm and Bucket4j library.
Added new "bucket4j" module to Armeria.
Provided solution for issue #2394 in an alternative way as per earlier review feedback by @trustin: "Provide a separate module armeria-bucket4j which provides an alternative ThrottlingStrategy implementation that exposes bucket4j classes in the public API."

@minwoox Approve or comment?

Thanks again, @max904-github ! :bowing_man:


xcmp misbehaves when pixel to point ratio is <0

When xcmp is used on a plot where the number of x-bins is less than the number of pixels, the plot is rendered incorrectly.

Fixed in #52


| causes error while typing.Union works

I just moved to python 3.10. The following code works when using typing.Union, but when replacing it with | it fails
from collections.abc import Callable
from typing import Union

from beartype import beartype

class Test:
    @beartype
    def __init__(
        self,
        test: Callable[[int, int], int] | str = ...,  # fails
        # test: Union[Callable[[int, int], int], str] = ..., # works
    ):
        ...

...
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_decor/main.py", line 149, in beartype
    func_wrapper_code = generate_code(func_data)
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_decor/_code/codemain.py", line 166, in generate_code
    code_check_params = _code_check_params(data)
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_decor/_code/codemain.py", line 373, in _code_check_params
    func_wrapper_code_param = pep_code_check_param(
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_decor/_code/_pep/pepcode.py", line 149, in pep_code_check_param
    reraise_exception_cached(
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_util/cache/utilcacheerror.py", line 200, in reraise_exception_cached
    raise exception.with_traceback(exception.__traceback__)
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_decor/_code/_pep/pepcode.py", line 132, in pep_code_check_param
    ) = pep_code_check_hint(hint)
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_util/cache/utilcachecall.py", line 351, in _callable_cached
    raise exception
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_util/cache/utilcachecall.py", line 343, in _callable_cached
    return_value = params_flat_to_return_value[params_flat] = func(
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_decor/_code/_pep/_pephint.py", line 908, in pep_code_check_hint
    cls=get_hint_pep_origin_type_isinstanceable(hint_curr),
  File "/pool01/home/twoertwe/.cache/pypoetry/virtualenvs/python-tools-sgDWaTGJ-py3.10/lib/python3.10/site-packages/beartype/_util/hint/pep/utilpepget.py", line 821, in get_hint_pep_origin_type_isinstanceable
    raise BeartypeDecorHintPepException(
beartype.roar.BeartypeDecorHintPepException: Type hint collections.abc.Callable[[int, int], int] | str not isinstanceable (i.e., does not originate from isinstanceable class).

sorry, was using an old version of beartype (0.9.1), it works with 0.10.2

Almost had me anxiously dripping sweat everywhere there. :sweat_smile:


Problems to deploy my first containerized app to a Standalone Service Fabric using Azure Container Registry

I already have a Service Fabric project in Visual Studio 2017 with the following projects:

Service Fabric Application
Gateway (ASP.NET Core with .Net Core and the API Gateway Ocelot)
ServiceA (That is a reliable service using ASP.NET Core WebAPI)
ServiceB (Containerized App using ASP.NET 4 with WebAPI 2)

Sample code in GitHub https://github.com/licjapodaca/service-fabric-sample-gateway

When I deploy without the ServiceB the Service Application, everything is OK, but when the project ServiceB was including with the option Add Container Orchestrator Support in Visual Studio 2017 when try to deploy the Service Fabric application again, appears me a message like the following:

The question here is, What are the steps to follow to create a Server Certificate and the installation process in the machine or machines that needs to deploy the Service Fabric application?

Thanks in advance for your help.

From the Azure portal, assuming you have the proper permissions, you can download the server cert from the KeyVault associated with your SF cluster. Go to the KeyVault in the resource group your cluster is in, click on Certificates on the left and then click on the Certificate. There is an option to download the cert as .pfx. Once you have the .pfx on your dev machine you can double click it to install it and the VS can use it.
BTW, the reason the server cert is needed in this scenario is because the service you containerized needs to have its Docker image pushed to your Azure Container Registry (ACR). To do this in a way that Service Fabric will have access to the image, we encrypt the ACR password using the server cert and them place that in the manifest.

Sorry @BigMorty , I forgot to tell you, my Service Fabric cluster is a Standalone installation (On-Premises), the steps to follow in this scenario is different?

There still must be a server cert, that is what you need to install on your dev machine for VS to connect. Adding @amanbha and @NCarlsonMSFT who might know how to extract the server cert from on-prem cluster.

@licjapodaca How did you create your standalone cluster? Is it insecure, secured by certificate, or secured by windows?
Assuming a cluster certificate has been installed you can get it's thumbprint by opening Service Fabric Explorer for the cluster (typically https://:19080/Explorer/index.html) and going to the manifest tab of the cluster node (add #/tab/manifest to the url). In the manifest look for the certifcates element underneath the nodetype element and that will have the thumbprint for the cluster certificate, if one has been configured.
Assuming it has been configured you should be able to get the certificate by remoting into the machine and exporting the certificate using the certificate manger or powershell (https://docs.microsoft.com/en-us/powershell/module/pkiclient/export-pfxcertificate?view=win10-ps); you can use the thumbprint form above to find the correct certificate in either tool.
Then transfer that pfx file to your client and import it.

Hi @NCarlsonMSFT , I create the standalone cluster of SF by Windows security, but I already found another way to deploy ASP.NET 4 MVC WebAPI apps in a container by using the Service Fabric Hosted Containers template with the help of an  Azure Container Registry like in the following image:

As you can see:
1 and 2. I create the instruction of a new Service Fabric Service using the Hosted Container template giving the complete name of the image plus the Azure Container Registry that I will use.
3. Then, it adds the ServiceManifest that represent my ServiceB project that is in ASP.NET MVC 4 WebAPI.
4. And Finally, I just add the Dockerfile that my service need to create the Image. This process will be done by TFS (On-Premises) with Continuous Integration, first it builds the .Net Project and then will create the Image and upload to Azure Container Registry, so when our Testers trigger the Continuous Delivery it downloads from ACR the image and store it in the Service Fabric Image Store to create the n instances of the service.
It would be ok with this scenario?

@licjapodaca you'll quickly run into the same issue here that you need to provide the credentials for connecting to ACR in your application manifest (example) and it is highly recommended that you encrypt the password (and if possible don't check it in). Our publish dialog and release task both will handle that step for you. But only if your cluster is configured with a cluster certificate.
Would it be possible for you to configure your cluster with windows authentication and a cluster certificate as in this example: https://github.com/Azure-Samples/service-fabric-dotnet-standalone-cluster-configuration/blob/master/Samples/ClusterConfig.Windows.X509.MultiMachine.json ?
@MikkelHegn is it possible to add a cluster certificate to a windows secured cluster after the fact?

Excellent @NCarlsonMSFT ... thanks for your help, I will made the changes with the information that you gave me in your last post.
Greetings


authentication issue

hi from the cortex i have already the hash authentication so another hash will get authentication issue :
Traceback (most recent call last):
  ...
  File "ib/python3.9/site-packages/cortex_xdr_client/api/xql_api.py", line 51, in start_xql_query
    response = self._call(call_name="start_xql_query", json_value=request_data)
  File "lib/python3.9/site-packages/cortex_xdr_client/api/base_api.py", line 46, in _call
    return self._execute_call(url=url,
  File "python3.9/site-packages/cortex_xdr_client/api/base_api.py", line 67, in _execute_call
    response.raise_for_status()
  File "python3.9/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url

is there a way to add flag to set hash api key that will put instead of "Authorization": api_key_hash "Authorization": self._api_key
in _get_headers() line 30 in base_api.py file? or how can i get the not hash api from the product ?

query still not ended but api crash :
Traceback (most recent call last):
...
  File "/cortex_xdr_client/api/xql_api.py", line 75, in get_query_results
    raise InvalidResponseException(response, ["number_of_results"])
cortex_xdr_client.api.models.exceptions.InvalidResponseException: Invalid response from server.
 Got: {'reply': {'status': 'PENDING'}}. Missing items: ['number_of_results']

this response is expected when api take some time to get answer but the api does not wait and throw exception

Hey @omer-an Sorry for the late reply here. Thank you for creating this issue, as I am an advanced auth user I did not implement standard auth. I pushed a PR to enable it

thank you so much, will it be possible to push this pr to the version in pypi?

Yes indeed, I just pushed 1.8.0 out. I am reopening this as it got closed automatially - but I still need to dig into the errors you faced on querying.

@omer-an Is this still an issue?


GH-314 Add virtual helm repo resource

Closes #314
Include use_namespaces attribute for Helm repo.

Changes looks fine for me.


Add missing GA events from react-native-google-analytics-bridge

Hi,
I'd like to add the following events to the redux-beacon RN GoogleAnalyticsTracker:

setUser()
trackSocialInteraction()
trackScreenViewWithCustomDimensionValues()
trackEventWithCustomDimensionValues()
trackEventWithCustomDimensionAndMetricValues()
trackPurchaseEvent()

I'd also like to add the ability to add 'customDimensionsFieldsIndexMap' to the GA tracker.
This is all functionality which I imagine a lot of GA users should need. If you're happy to accept a PR then we'll get it done. Thanks

@djw27 absolutely!

New release includes these changes :tada:
https://rangle.gitbook.io/redux-beacon/targets/react-native-googleanalytics


Support Ruby 2.4 in CI

Summary
Fixes #209
Update the ruby_on_rails action to re-add testing against Ruby 2.4.
To accomplish this, we need to run gem update --system, but we don't
want to do this on any version except 2.4.x to save build time.
This commit uses the context and expression syntax for GitHub actions to
check if the Ruby versions starts with 2.4, and update the system gems
in the event that we have a match.

Thanks @andrewmcodes! Mind adding a changelog entry and your name to the README?


add total table count checks to routeTableRanges option for apiserver

Description
Cherrypick from EE. Adds apiserver valdation to limit the maximum number of tables targeted by routeTableRanges  Felixconfig option. This validation is already present in Felix itself, so currently, adding an oversized routeTableRanges arg via kubectl or similar will succeed when patching FelixConfig, but then cause Felix to panic. This PR causes such a patch to fail immediately instead.

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Will do!

ok - UT's added, and git history tidied up. I think this is ready for merge - normal, non-squash merge I believe since this is primarily a cherry-pick

@caseydavenport I dont think this PR requires a docs PR, but does it require a release note, since I am now patching a bug, on-top of adding new validation? I don't have perms to change these labels also BTW so will need an admin to modify those
thanks


Adds Initial Gemini Design Documentation

Gemini is a cluster manager that simplifies deploying and
operating clustering systems. This is the initial set of
design documents that describe Gemini.
Signed-off-by: Daneyon Hansen<EMAIL_ADDRESS>

PR ready to go now. Had to rebase.


Update external-sharing-overview.md

#892
Guest user/External user adding license in Preview on do not show the show "more" or "Manage product licenses", even if you click on multiple guest user but if you click on a different user/contact user etc. it will show "Manage product licenses" then you can assign the license , but this is just a work around so you can assign the product to the guest user, you must be back to the Standard Preview in Admin Center to show the Manage Product License.
See screenshot below:
-When you click on a guest user in a Preview On
https://snag.gy/7Y3Whn.jpg
-Shows the manage product option after you click on a different user as long as it is not a guest user
https://snag.gy/RaB7oE.jpg
https://snag.gy/U6AVr1.jpg

@MikePlumleyMSFT Hi Mike, changes look correct. Could you please review and merge? Thanks!


payment from receive link shows up with claim icon

send a receive link to someone
pay via receive link
in feed the received payment has claim icon where normal receive icon should be

Checked on QA environment
Work as per requirements
https://www.screencast.com/t/4mVlg1qYp4i
https://www.screencast.com/t/OmCoX95Bj


Use new external chunked_transfer library

https://github.com/frewsxcv/rust-chunked-transfer
I extracted out the decoder/encoder and made a separate reusable library

(note that you don't necessarly have to r? me for all PRs)
(it's especially changes to the logic of the code that should be reviewed for correctness)


Add gen_typed_args

Codecov Report

Merging #146 (8a93fbd) into main (b4674ea) will decrease coverage by 3.55%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
- Coverage   73.23%   69.67%   -3.56%
==========================================
  Files          11       12       +1
  Lines         609      653      +44
==========================================
+ Hits          446      455       +9
- Misses        163      198      +35

Impacted Files
Coverage Δ

src/memory_segments.rs
69.56% <0.00%> (-27.41%)
:arrow_down:

src/vm_core.rs
85.43% <0.00%> (-2.20%)
:arrow_down:

src/lib.rs
0.00% <0.00%> (ø)

src/ecdsa.rs
14.28% <0.00%> (ø)

src/ids.rs
34.61% <0.00%> (+0.16%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


bump kotlin and use jdk7 instead of jre7 dependency

this fixes classpath issues downstream, when projects are using the correct org.jetbrains.kotlin:kotlin-stdlib-jdk7 artifact.

Yay for flaky android tests. W/e they pass on my machine so merging


Wizards (RPG Series) cause weapon not able to use right click abilities

Soul's Like version : <IP_ADDRESS> patch 2
Wizards version :  0.9.23
MC Ver : 1.20.1
using this mod in conjunction with Wizards (https://modrinth.com/mod/wizards) somehow disables any weapon from this mod to use its ability like the moonlight beams or the Whirligig Saw
no relevant log is outputted

You have to blacklist weapons from this mod in Wizards (RPG Series)'s config.


Load balancing in an Availability Set

This section https://docs.microsoft.com/en-ca/azure/architecture/checklist/resiliency speaks to multiple machines being used to ensure SLA uptime, but it does not say anything in regard to the network traffice when there is a outage of any of the VM's.  IMO - Availability Set shoud mean a Active-Standby arrangement, or with the addition of Load Balancing - balancing the load to all VMS under an Availabliity Set.  There are applicaiton requirements in that legacy applications that CANNOT be load balanced, as the VM in Active Mode is handling all the traffice in-bound, and will also generate traffic outbound.  Mutliple VMS doing the same traffice will break the application.  LIve Migration is the ticket here, in that before the VM shuts down, network is buffered, memory delta is manage between Active/Standby, and the failover to Standy Occurs... at least in my ideal scenario.

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

ID: 948b29e3-d488-0a0e-89c7-42849a93522d
Version Independent ID: 8c986086-9343-4b99-ae53-f4fd1159d4f8
Content: Manage the availability of Windows VMs in Azure
Content Source: articles/virtual-machines/windows/manage-availability.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! We are currently investigating and will update you shortly.

@codeputer thanks for reaching out and sharing your thoughts with us. We appreciate all feedback.
I am a bit confused though on what action you would like to see out of this issue.
The doc you commented on does go into information about adding a LB to VMs in an AV set to manage traffic
https://docs.microsoft.com/en-ca/azure/virtual-machines/windows/manage-availability#combine-a-load-balancer-with-availability-sets
As well as the resiliency doc as it talks about using a LB to distribute traffic.
What exactly are you looking for as an outcome of this issue? I am confused as to what is not clear but if we can make it more clear then that would be great.

I think the documentation should make a clear delineation between Failover technology and Load balancing.  I realize that in both there is a virtual endpoint that routes traffic to an appropriate node, however, in failover/standby  the primary gets all the traffic, and when it has an issue, the traffic is routed to the secondary.  In my definition of load balancing, the load is spread across a number of nodes, and if one falls out of the pool, the virtual endpoint takes that node our of the pool and the service continues.
So Availability Set in my mind = Failover.  Scale Out  = Load Balancing.
In my case, I'm looking at Availability set for an application that has a very high SLA.  However, it's a legacy polling application with an in-memory "real-time" database.  This means it MUST always be the ONLY service that polls and manages the assets that it's connecting with, however should it fail (which is more likely a maintenance event than anything elese in Azure), I need a "Live MIgration" over to another VM that is basically picking up where the other left off - in other words (and perhaps in my mind) its Available.
Or am I thinking of Availability Set incorrectly - and I should think of it more as a Load Balancing solution, but with the added check mark that all the nodes can't be on the same hardware.  In that case, it should be documented as a Load Balancing solution, with an additional benefit of hardware utilization.
Regards,
Richard

From: Micah<EMAIL_ADDRESS>Sent: February 14, 2019 1:24 PM
To: MicrosoftDocs/azure-docs
Cc: Richard Reukema; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Load balancing in an Availability Set (#24955)
@codeputerhttps://github.com/codeputer thanks for reaching out and sharing your thoughts with us. We appreciate all feedback.
I am a bit confused though on what action you would like to see out of this issue.
The doc you commented on does go into information about adding a LB to VMs in an AV set to manage traffic
https://docs.microsoft.com/en-ca/azure/virtual-machines/windows/manage-availability#combine-a-load-balancer-with-availability-sets
As well as the resiliency doc as it talks about using a LB to distribute traffic.
What exactly are you looking for as an outcome of this issue? I am confused as to what is not clear but if we can make it more clear then that would be great.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/24955#issuecomment-463780626, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAlU1fwd5VwRugGWHKij9zCgvRcCTVueks5vNcYJgaJpZM4a8GFY.

Availability sets in Azure is simply a separate of hardware.
As per the diagram in the docs

If you were to put VMs into the same availability set the platform will ensure that those VMs are never put on the same update domain and fault domain. This means that if a rack were to fail with one VM on it, it would not take down the other VMs in that AV set as they would be placed on different racks.
The same thing can be said for updates. We perform updates in the data centers by update domains. Placing multiple machines into the same AV set ensures that they are placed in different updates domains and when we perform updates this means you will not have multiple machines taken down at once.
You are able to deploy machines into an AV set without a load balancer. This could mean that you have two separate VMs that are not related to one another. But you still don't want them taken down at the same time. To do that you would put them in the same AV set.
If you do want to achieve full High Availability for VMs, then you would want to place VMs in the same AV set as well as pair with a load balancer. That way if one of the VMs goes down the LB would automatically route traffic to the available machine until they are both back online then distribute traffic to both.
So the idea that an AV set = fail over is incorrect. It is just a way to ensure hardware separation inside of the data center. And scaling out does not mean load balancing persay. In Azure you can scale vertically and horizontally. So you can add more machines such as with Scale Sets to handle more load. In this case there is also a Load balancer that handles the traffic. You could also scale up the resources of a specific VM instead to handle more load. This does not mean you are having anything to do with a load balancer.
We do have documentation on fail over scenarios as well which is a whole other scenario
https://azure.microsoft.com/en-us/services/site-recovery/
All in all, an availability set is not a load balancing solution.

The application I'm dealing with is basically a polling application that reaches out to devices to pickup data for each device. It's old school and needs to be updated, but it has as in memory data store that tracks which IOT devices it has polled when was it polled, and the next time it needs to be polled.
It has its own "service" that keeps a second computer current as to what it's last task was.  This goes back to physical hardware, and if server failed, the standby had to pick it up right away.  Hence my research of Availablity Set - but my incorrect assumption that it too also meant routing was included.  Like you said, it ONLY means different infrastructure services which is managed by different services - nothing network related in terms of traffic flow.
I would think however, an option to provide a "shadow" VM in an Availability set - where the shadow is ready to jump in would also be  a good feature for Azure - or am I missing a feature that is already there?
Thanks in anyways for your help in understanding the documentation - I hope you can use it as feedback and make these delination from a network perspective more clear or at least address it directly as you have done in the explanation that you gave me!
Regards,
Richard

From: Micah<EMAIL_ADDRESS>Sent: February 14, 2019 2:00 PM
To: MicrosoftDocs/azure-docs
Cc: Richard Reukema; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Load balancing in an Availability Set (#24955)
Availability sets in Azure is simply a separate of hardware.
As per the diagram in the docs
[image]https://user-images.githubusercontent.com/32313503/52817031-826d4d00-3057-11e9-9fde-d0f3c7b44eae.png
If you were to put VMs into the same availability set the platform will ensure that those VMs are never put on the same update domain and fault domain. This means that if a rack were to fail with one VM on it, it would not take down the other VMs in that AV set as they would be placed on different racks.
The same thing can be said for updates. We perform updates in the data centers by update domains. Placing multiple machines into the same AV set ensures that they are placed in different updates domains and when we perform updates this means you will not have multiple machines taken down at once.
You are able to deploy machines into an AV set without a load balancer. This could mean that you have two separate VMs that are not related to one another. But you still don't want them taken down at the same time. To do that you would put them in the same AV set.
If you do want to achieve full High Availability for VMs, then you would want to place VMs in the same AV set as well as pair with a load balancer. That way if one of the VMs goes down the LB would automatically route traffic to the available machine until they are both back online then distribute traffic to both.
So the idea that an AV set = fail over is incorrect. It is just a way to ensure hardware separation inside of the data center. And scaling out does not mean load balancing persay. In Azure you can scale vertically and horizontally. So you can add more machines such as with Scale Sets to handle more load. In this case there is also a Load balancer that handles the traffic. You could also scale up the resources of a specific VM instead to handle more load. This does not mean you are having anything to do with a load balancer.
We do have documentation on fail over scenarios as well which is a whole other scenario
https://azure.microsoft.com/en-us/services/site-recovery/
All in all, an availability set is not a load balancing solution.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/24955#issuecomment-463794284, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAlU1cRxKduFCKeknHFSG6qh64ev0opWks5vNc59gaJpZM4a8GFY.

Always happy to help explain stuff :) It can be difficult to grasp some of the concepts in Azure as somethings that mean one thing from an on prem perspective do not mean the same thing when talking about Azure.
This can be especially true when talking about networking architecture.
Per the shadow copy comment, Azure kind of has this. For example, say you have a standalone virtual machine running an web application. No AV set, No load balancer. Just a VM. To ensure data consistency in Azure we keep 3 copies of your VMs VHD. This means the chance of any data loss due to failure of a data center or corruption is minimized.
Now lets say that single VMs rack in the data center fails. This means your VM will fail. Azure will realize that their was a failure and initialize a recovery action. This recovery action is to actually spin up a new VM and associate your VHD with that VM. This new VM will be on a new rack without an issue. This can take a couple of mins but your VM will come back online and be moved to safety. So even if you do not have any High Availability setup your VM will not be lost or be down for long. There are fixes in place that Azure will automatically take care of in case of failure. That being said, since you would only have that single VM there would be a few mins of downtime while the VM is moved to a new host.
Another thing to note is that every time you shutdown a VM you release the resources associated with that machine. So when you start it back up you will be allocated to a new host and the VMs OS disk will be associated with that new VM. So the separation of resources in Azure really helps with recovery and resiliency.
From a cloud perspective we really try to limit the amount customers have to worry about hardware. So much redundancy is built into the platform to the point where you can pretty much just run an app and let Azure take care of the rest. Running in a VM does still provide you some control over OS and hardware but for example running in an App services takes all that way. All you do is upload your code and let the platform take care of the rest.

Yeah I totally get it in terms of the redundancy – something that I think AWS doesn’t even come close to touching.
The roadmap for the application is to always more to PaaS services, but I need to have a lot more fall in place before that can happen.
I understand and appreciate that the VM will come back, and likely that small outage doesn’t really matter to the business in an operational sense – I’m sure their hardware failover to their standby would likely take longer – however – its there SLA and we need to ensure that we are addressing business concerns.
So 1) Create an Availability Set, 2) have 2 VM’s created exactly the same, 3) start their own replication service from VM1 to VM2 to sync memory, and 3) test the failover and time it takes.
Then I might suggest one more test – leave one VM up and cause it to “fail” – and see how long that takes to “return the service”.  I’m thinking it won’t be much of a difference.
BTW – is there a way to simulate a “maintenance event” on a VM?
Thanks again for your help!
Regards,
Richard
From: Micah<EMAIL_ADDRESS>Sent: February 14, 2019 2:36 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Richard Reukema<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Load balancing in an Availability Set (#24955)
Always happy to help explain stuff :) It can be difficult to grasp some of the concepts in Azure as somethings that mean one thing from an on prem perspective do not mean the same thing when talking about Azure.
This can be especially true when talking about networking architecture.
Per the shadow copy comment, Azure kind of has this. For example, say you have a standalone virtual machine running an web application. No AV set, No load balancer. Just a VM. To ensure data consistency in Azure we keep 3 copies of your VMs VHD. This means the chance of any data loss due to failure of a data center or corruption is minimized.
Now lets say that single VMs rack in the data center fails. This means your VM will fail. Azure will realize that their was a failure and initialize a recovery action. This recovery action is to actually spin up a new VM and associate your VHD with that VM. This new VM will be on a new rack without an issue. This can take a couple of mins but your VM will come back online and be moved to safety. So even if you do not have any High Availability setup your VM will not be lost or be down for long. There are fixes in place that Azure will automatically take care of in case of failure. That being said, since you would only have that single VM there would be a few mins of downtime while the VM is moved to a new host.
Another thing to note is that every time you shutdown a VM you release the resources associated with that machine. So when you start it back up you will be allocated to a new host and the VMs OS disk will be associated with that new VM. So the separation of resources in Azure really helps with recovery and resiliency.
From a cloud perspective we really try to limit the amount customers have to worry about hardware. So much redundancy is built into the platform to the point where you can pretty much just run an app and let Azure take care of the rest. Running in a VM does still provide you some control over OS and hardware but for example running in an App services takes all that way. All you do is upload your code and let the platform take care of the rest.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/24955#issuecomment-463807619, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAlU1SvAAmbaZFoIRcsc7TgpqPkuFtdBks5vNdbNgaJpZM4a8GFY.

@codeputer you might consider looking into running your app on Scalesets as well
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
Might make the process a bit simpler for you and provide you with that high availablity you are looking for.
As per simulating a maintenance event, we have had that ask quite a few times before but there is not a great way to achieve this. You could of course shutdown one of the VMs to ensure traffic is still routed correctly to the available VM but that does not really simulate a maintenance event. There are a few feature requests open in Azure feedback to have some way to simulate it but there is nothing really as of now.

@codeputer I will close this for now as based on the current setup of the docs we don't believe we should add more information. That being said, we have shared your feedback with the correct teams and your comment will remain on the docs so if other users have the same confusion we can always consider reopening and digging deeper. Let me know if you have any other questions and I am happy to help :)


Release notes Action doesn't run when a PR is merged

After the change to the new Actions YAML grammar, the Post release notes Action no longer runs when a PR is merged.

While the Action runs on PR merge now, it fails due to a bug in actions/checkout.


dirOf should work with relative paths

Issue description
nix's built-in function dirOf only works for strings which are absolute paths, for some reason. This looks like a completely arbitrary (and quite unfortunate) restriction, and the documentation doesn't mention it.
The related function baseNameOf does work for all kinds of strings.
Steps to reproduce
nix-instantiate --eval --expr 'dirOf "dir/abc.txt"'                                                        ~
error: string 'dir/abc.txt' doesn't represent an absolute path, at (string):1:1

Technical details

system: "x86_64-linux"
host os: Linux 4.14.49, NixOS, 18.03.132687.14c248a4ab7 (Impala)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.0.4
channels(paul): ""
channels(root): "nixos-18.03.132687.14c248a4ab7"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

I think this belongs over at https://github.com/NixOS/nix/issues, it might receive more attention from the right people there.

This makes sense.
There is no way to transfer the issue to another repository, right?

Not that I'm aware of, at least not for ordinary repo members/contributors.


Script doesn't collect the drop

20:25:02: Traceback (most recent call last):
20:25:02:   File "utils.py", line 96, in wrapper
20:25:02:   File "twitch.py", line 1332, in process_drops
20:25:02:   File "inventory.py", line 202, in claim
20:25:02:   File "inventory.py", line 120, in claim
20:25:02:   File "inventory.py", line 136, in _claim
20:25:02:   File "twitch.py", line 1534, in gql_request
20:25:02: exceptions.MinerException: GQL error: [{'message': 'PersistedQueryNotFound'}]

This is a duplicate of #138.


feat: Migrating to new docker image (single container)

-- Document guides how to migrate data & configuration from Docker stack to new appsmith docker image (single container)

Note to self: Add instructions on how to get a superadmin in the instance, after migration is finished.


test bumpwq

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

It's probably time for another cobra release soon anyway but thank you for working on this. I'll review when CI passes.

Thanks @Midnighter .
I stumbled over this because we get ImportError: cannot import name 'print_dependencies' from 'depinfo' (/usr/local/lib/python3.9/site-packages/depinfo/__init__.py) for the rpbasicdesign package in a weekly Galaxy tool test.
Would this solve this?

The full Traceback of our test is:
  File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.9/site-packages/rpbasicdesign/cli.py", line 14, in <module>
    from rpbasicdesign.Designer import Designer
  File "/usr/local/lib/python3.9/site-packages/rpbasicdesign/Designer.py", line 23, in <module>
    from rptools.rplibs import rpSBML, rpPathway
  File "/usr/local/lib/python3.9/site-packages/rptools/rplibs/__init__.py", line 7, in <module>
    from rptools.rplibs.rpPathway import rpPathway
  File "/usr/local/lib/python3.9/site-packages/rptools/rplibs/rpPathway.py", line 46, in <module>
    from .rpSBML import rpSBML
  File "/usr/local/lib/python3.9/site-packages/rptools/rplibs/rpSBML.py", line 40, in <module>
    import cobra
  File "/usr/local/lib/python3.9/site-packages/cobra/__init__.py", line 5, in <module>
    from cobra.core import (
  File "/usr/local/lib/python3.9/site-packages/cobra/core/__init__.py", line 1, in <module>
    from cobra.core.configuration import Configuration
  File "/usr/local/lib/python3.9/site-packages/cobra/core/configuration.py", line 16, in <module>
    from cobra.util.solver import interface_to_str
  File "/usr/local/lib/python3.9/site-packages/cobra/util/__init__.py", line 4, in <module>
    from cobra.util.util import *
  File "/usr/local/lib/python3.9/site-packages/cobra/util/util.py", line 6, in <module>
    from depinfo import print_dependencies
ImportError: cannot import name 'print_dependencies' from 'depinfo' (/usr/local/lib/python3.9/site-packages/depinfo/__init__.py)


New version: mikf.gallery-dl version 1.25.0

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

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow

This package is expecting arguments:
usage: gallery-dl.exe [OPTION]... URL...
gallery-dl.exe: error: The following arguments are required: URL
Use 'gallery-dl --help' to get a list of all options.

@wingetbot waivers Add Validation-Executable-Error


Poor formatting of slice_patterns

#![feature(slice_patterns)]

fn main() {
    match b"123" {
        [0, ..] => {}
        _ => {}
    }
}

As of rustfmt 0.99.1-nightly (da17b68 2018-08-04), formatting produces the following diff which I believe is less readable than the original:
-         [0, ..] => {}
+         [0, _..] => {}

Why is _.. even accepted syntax? It is not allowed in normal pattern matching:
let (a, _..) = (1, 2 ,3);

does not even compile.


cog predict -i<EMAIL_ADDRESS>FAILS

cog.yaml
    build:
      gpu: true
      system_packages:
        - "libgl1-mesa-glx"
        - "libglib2.0-0"
      python_version: "3.8"
      python_packages:
        - "torch==1.8.1"
      run:
          - pip install typing-extensions --upgrade
    predict: "predict.py:Predictor"

Machine Info
Darwin sentient-22-MacBook-Pro.local 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar  6 21:01:02 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8112 arm64
Process  =
        Building Docker image from environment in cog.yaml...
        [+] Building 82.8s (12/19)
         => [internal] load .dockerignore                                                                                0.0s
         => => transferring context: 2B                                                                                0.0s
         => [internal] load build definition from Dockerfile                                                                  0.0s
         => => transferring dockerfile: 2.11kB                                                                                0.0s
         => resolve image config for docker.io/docker/dockerfile:1.2                                                          4.4s
         => CACHED docker-image://docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e  0.0s
         => [internal] load .dockerignore                                                                                0.0s
         => [internal] load build definition from Dockerfile                                                                  0.0s
         => [internal] load metadata for docker.io/nvidia/cuda:11.1.1-cudnn8-devel-ubuntu20.04                                1.8s
         => [stage-0  1/11] FROM docker.io/nvidia/cuda:11.1.1-cudnn8-devel-ubuntu20.04@sha256:bb8379ce06f114591a64031c31d4f0  0.0s
         => [internal] load build context                                                                                0.0s
         => => transferring context: 42.15kB                                                                                0.0s
         => CACHED [stage-0  2/11] RUN --mount=type=cache,target=/var/cache/apt set -eux; apt-get update -qq; apt-get instal  0.0s
         => CACHED [stage-0  3/11] RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy -  0.0s
         => ERROR [stage-0  4/11] RUN curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyen  76.5s
        ------
         > [stage-0  4/11] RUN curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer | bash &&  git clone https://github.com/momo-lab/pyenv-install-latest.git "$(pyenv root)"/plugins/pyenv-install-latest &&  pyenv install-latest "3.8" &&      pyenv global $(pyenv install-latest --print "3.8") &&   pip install "wheel<1":
        #0 75.27 curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused
        #0 75.31 /bin/sh: 1: pyenv: not found
        #0 75.34 Cloning into '/plugins/pyenv-install-latest'...
        #0 76.51 /bin/sh: 1: pyenv: not found
        ------
        Dockerfile:36
        --------------------
          35 |          && rm -rf /var/lib/apt/lists/*
          36 | >>> RUN curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer | bash && \
          37 | >>>      git clone https://github.com/momo-lab/pyenv-install-latest.git "$(pyenv root)"/plugins/pyenv-install-latest && \
          38 | >>>      pyenv install-latest "3.8" && \
          39 | >>>      pyenv global $(pyenv install-latest --print "3.8") && \
          40 | >>>      pip install "wheel<1"
          41 |     COPY .cog/tmp/build2771002050/cog-0.0.1.dev-py3-none-any.whl /tmp/cog-0.0.1.dev-py3-none-any.whl
        --------------------
        ERROR: failed to solve: process "/bin/sh -c curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer | bash && \tgit clone https://github.com/momo-lab/pyenv-install-latest.git \"$(pyenv root)\"/plugins/pyenv-install-latest && \tpyenv install-latest \"3.8\" && \tpyenv global $(pyenv install-latest --print \"3.8\") && \tpip install \"wheel<1\"" did not complete successfully: exit code: 127
        ⅹ Failed to build Docker image: exit status 1

What could be potential issue and solution ?

The error lies in this line:
curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused
Your network is unstable. Just retry it. Note that if you are in countries that block Github (e.g. China) you need to use some global proxy.

This is latest
    cog predict -i @input.jpg
    Building Docker image from environment in cog.yaml...
    [+] Building 705.2s (17/18)
     => [internal] load build definition from Dockerfile                                                                  0.0s
     => => transferring dockerfile: 2.06kB                                                                                0.0s
     => [internal] load .dockerignore                                                                                0.0s
     => => transferring context: 2B                                                                                0.0s
     => resolve image config for docker.io/docker/dockerfile:1.2                                                          4.0s
     => CACHED docker-image://docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e  0.0s
     => [internal] load build definition from Dockerfile                                                                  0.0s
     => [internal] load .dockerignore                                                                                0.0s
     => [internal] load metadata for docker.io/nvidia/cuda:11.1.1-cudnn8-devel-ubuntu20.04                                1.5s
     => [internal] load build context                                                                                0.0s
     => => transferring context: 78.20kB                                                                                0.0s
     => [stage-0  1/10] FROM docker.io/nvidia/cuda:11.1.1-cudnn8-devel-ubuntu20.04@sha256:bb8379ce06f114591a64031c31d4f0  0.0s
     => => resolve docker.io/nvidia/cuda:11.1.1-cudnn8-devel-ubuntu20.04@sha256:bb8379ce06f114591a64031c31d4f0a42a711b7f  0.0s
     => CACHED [stage-0  2/10] RUN --mount=type=cache,target=/var/cache/apt set -eux; apt-get update -qq; apt-get instal  0.0s
     => CACHED [stage-0  3/10] RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy -  0.0s
     => [stage-0  4/10] RUN curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-ins  609.2s
     => [stage-0  5/10] COPY .cog/tmp/build4168359138/cog-0.0.1.dev-py3-none-any.whl /tmp/cog-0.0.1.dev-py3-none-any.whl  0.0s
     => [stage-0  6/10] RUN --mount=type=cache,target=/root/.cache/pip pip install /tmp/cog-0.0.1.dev-py3-none-any.whl   20.2s
     => [stage-0  7/10] RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy libgl1-  43.5s
     => [stage-0  8/10] COPY .cog/tmp/build4168359138/requirements.txt /tmp/requirements.txt                              0.0s
     => ERROR [stage-0  9/10] RUN --mount=type=cache,target=/root/.cache/pip pip install -r /tmp/requirements.txt        26.4s
    ------
     > [stage-0  9/10] RUN --mount=type=cache,target=/root/.cache/pip pip install -r /tmp/requirements.txt:
    #0 3.273 Looking in links: https://download.pytorch.org/whl/torch_stable.html
    #0 9.462 Collecting torch==1.8.1+cu111
    #0 26.09 /root/.pyenv/pyenv.d/exec/pip-rehash/pip: line 20:   221 Killed                  "$PYENV_COMMAND_PATH" "$@"
    ------
    Dockerfile:45
    --------------------
      43 |     RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy libgl1-mesa-glx libglib2.0-0 && rm -rf /var/lib/apt/lists/*
      44 |     COPY .cog/tmp/build4168359138/requirements.txt /tmp/requirements.txt
      45 | >>> RUN --mount=type=cache,target=/root/.cache/pip pip install -r /tmp/requirements.txt
      46 |     WORKDIR /src
      47 |     EXPOSE 5000
    --------------------
    ERROR: failed to solve: process "/bin/sh -c pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 137
    ⅹ Failed to build Docker image: exit status 1

AFAIK there is no easy way to edit the dockerfile content.
We should probably add requirements.txt content in cog debug.
Can you describe how to reproduce this bug? Like provide a git repo for your code? Let me try to reproduce it and dig deeper.

Steps to simulate:

Macbook m1/m2 pro
Build cog
Open readme.md https://github.com/replicate/cog/blob/main/README.md
Follow the readme.md
You will meet the  issue of build in few minutes.

Can you tell  more how to add the requirements.txt content in cog debug ?
i know the old school which requires DOCKERFILE and requirement.txt atleast.

Hi @sentient-22

I tried your steps and it worked. Note that there are two changes based on existing readme:

You need to set env by export DOCKER_DEFAULT_PLATFORM=linux/amd64.
Set gpu: false in cog.yaml since there is no GPU on Mac

Q: Can you tell more how to add the requirements.txt content in cog debug?

I mean you change the source code: https://github.com/replicate/cog/blob/main/pkg/cli/debug.go . I don't represent the official maintainers. But I think you can create an feature request issue or submit a contribution PR for it :)

Thanks @hongchaodeng

Don't you think GPU =False  is not good thing;they do provide m2 tin box chip[gpu chip] for $2000 ; I wonder why apple tried to derive the linxu/amd64 to linux/arm64
set env by export DOCKER_DEFAULT_PLATFORM=linux/amd64
I will PR if find stable build for my m2 system right now it is bleeding ;

COG is beautiful design to extend the intelligence beyond the platform but its usage is occluded  by APPLE stupid ambition of looking smooth .

ty M

The error lies in this line:
curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused
Your network is unstable. Just retry it. Note that if you are in countries that block Github you need to use some global proxy.

how to set Global proxy with raw.githubusercontent.com in clash?i've run clash in ubuntu, i can visit github ,but can't cog run python,the same issue here


Style Guide font assets from cli

I'm using the cli interface to generate and run the style guide, but I can't figure out the proper way to add local font assets (.eot, .woff, .etc...).
/path/to/styleguide --kss-source "scss/**/*.scss" --style-source "css/*.css" --output styleguide --watch --server --overviewPath overview.md --port 3100

Anybody have any ideas?

Hi @carwin, you could add a css file containing font declarations via
--custom-colors "path/to/fonts.css"
Or you could use something like this:
--extra-head "<style>/* @font declarations */</style>".
Additionally, in your build process you have to copy the font assets to the styleguide, just like you would do with images.

Well the declarations are there as part of the globbed sass files, so it's just the asset copying. I suppose I can use bash to do it if there isn't some parameter I can pass.

Yeah, just like that, in your npm-scripts or whatever you use.


HIVE-25086: Create Ranger Deny Policy for replication db in all cases.

Create Ranger Deny Policy for replication db in all cases if hive.repl.ranger.target.deny.policy is set to true.

What happens if the config is first enabled and then disable? Do we support it?

Did you generate the thrift files using the maven command?

Yes

What happens if the config is first enabled and then disable? Do we support it?

Currently, user would have to manually disable the ranger deny policy for target db if config is disabled afterwards.


functionalitymodification

Issue:
#9
After change:

@parzival272000  I like the stop button :)
please don't remove any of the button work on some another feature

Ok I just changed it to toggle functionalities are same

Can you atleast give me hacktoberfest-accepted on my this PR or the other one if my efforts were good.

I made another PR this time i didn't change any buttons etc just added the functionality can you revie it plz


iOS App Crash for IRLinkage error after upgrading to 1.9.40-alpha04

Hello, I was having this issue with 1.9.20 so I updated to last alpha 1.9.40-alpha04 as suggested.
Now, at startup, I have the following linkage crash on iOS 18
Seems unrelated to the Webview instance itself, but it arises only with this library upgraded to latest alpha.
Any help?
Uncaught Kotlin exception: kotlin.native.internal.IrLinkageError: Function 'clickable' can not be called: No function found for symbol 'androidx.compose.foundation/clickable|clickable@androidx.compose.ui.Modifier(androidx.compose.foundation.interaction.MutableInteractionSource;androidx.compose.foundation.Indication?;kotlin.Boolean;kotlin.String?;androidx.compose.ui.semantics.Role?;kotlin.Function0<kotlin.Unit>){}[0]'
    at 0   <Redacted>.debug.dylib              0x10ca7e8bb        kfun:kotlin.Throwable#<init>(kotlin.String?){} + 119
    at 1   <Redacted>.debug.dylib              0x10ca77b97        kfun:kotlin.Error#<init>(kotlin.String?){} + 115
    at 2   <Redacted>debug.dylib              0x10cab4397        kfun:kotlin.native.internal.IrLinkageError#<init>(kotlin.String?){} + 115
    at 3   <Redacted>.debug.dylib              0x10cab445b        kfun:kotlin.native.internal#ThrowIrLinkageError(kotlin.String?){}kotlin.Nothing + 175
    at 4   <Redacted>.debug.dylib              0x10dd0186f        kfun:androidx.compose.material.Surface$lambda$4#internal +

Update: this was solved by updating compose multiplatform dependency version to 1.7.1
1.7.1 solves the following issue: https://github.com/JetBrains/compose-multiplatform-core/pull/1647
This solves also this linkage error.


[EI Analytics] Verify theme usage in each widget

Description:
Need to verify how each widget uses the passed theme from the dashboard viewer.
Affected Product Version:
WSO2SP 4.3.0

Fixed in latest carbon-dashboards


Add more tests

We still need tests for the following tools:

    ExplosiveCheck,

    ControlChemCheck,

    SafetySummary,

    LitSearch

ControlChemCheck solved in #18


The popup has no slider

Description
The popup has no slider
There are 20 entries in total, but there are no sliders, only 16 are displayed. You need to enlarge the window to display them completely
code:
        parametersTable = new Table(composite, SWT.SINGLE | SWT.FULL_SELECTION | SWT.BORDER | SWT.H_SCROLL | SWT.V_SCROLL);
        final GridData gd = new GridData(GridData.FILL_BOTH);

DBeaver Version
22.1.1 ce
Operating System
WINDOS 10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Hello @yangmeng66,
Thanks for the bug report.
You can submit a PR that will fix this issue.


Expose NewIndexReader() and cleanups

Signed-off-by: Goutham Veeramachaneni<EMAIL_ADDRESS>

This change is

👍


Contact

Hi! Sorry for the random issue but I can't find any email or any way to contact you on your profile. I saw your issue in keg - can I talk to you somehow? Email's on my profile

Sorry I've been busy this week and didn't notice the email. Do you want to talk in private?

Yeah :) Shoot me an email or some other form of contact: https://leclan.ch


Uncaught TypeError: Cannot read property 'getPropertyValue' of null

[Enter steps to reproduce below:]

I just installed atom-minimap on a clear atom installation
When I am starting atom appears this error

Atom Version: 0.165.0
System: linux 3.13.0-43-generic
Thrown From: minimap package, v3.4.9
Stack Trace
Uncaught TypeError: Cannot read property 'getPropertyValue' of null
At /home/bogdan/.atom/packages/minimap/lib/minimap-view.coffee:198

TypeError: Cannot read property 'getPropertyValue' of null
  at MinimapView.module.exports.MinimapView.getEditorLineHeight (/home/bogdan/.atom/packages/minimap/lib/minimap-view.coffee:198:87)
  at MinimapView.module.exports.MinimapView.computeScale (/home/bogdan/.atom/packages/minimap/lib/minimap-view.coffee:192:27)
  at /home/bogdan/.atom/packages/minimap/lib/minimap-view.coffee:170:8
  at Config.module.exports.Config.observeKeyPath (/usr/share/atom/resources/app/src/config.js:568:7)
  at Config.module.exports.Config.observe (/usr/share/atom/resources/app/src/config.js:134:21)
  at MinimapView.module.exports.MinimapView.initialize (/home/bogdan/.atom/packages/minimap/lib/minimap-view.coffee:169:36)
  at MinimapView.View (/home/bogdan/.atom/packages/linter/node_modules/space-pen/lib/space-pen.js:184:25)
  at new MinimapView (/home/bogdan/.atom/packages/minimap/lib/minimap-view.coffee:86:5)
  at Minimap.module.exports.ViewManagement.onEditorAdded (/home/bogdan/.atom/packages/minimap/lib/mixins/view-management.coffee:105:16)
  at /home/bogdan/.atom/packages/minimap/lib/mixins/view-management.coffee:85:37

Commands

Config
{
  "core": {
    "autoHideMenuBar": true,
    "themes": [
      "flat-simple-dark-ui",
      "monokai"
    ]
  }
}

Installed Packages
# User
color-picker, v1.2.6
flat-simple-dark-ui, v0.1.1
font-awesome-snippetset, v0.0.6
git-log, v0.2.0
javascript-snippets, v1.0.0
linter, v0.9.1
markdown-format, v2.5.0
minimap, v3.4.9
monokai, v0.9.0
open-last-project, v0.1.1
project-manager, v1.14.1

# Dev
No dev packages

/cc @atom/core

After updating to version 3.5.4 problem was gone. :)
just close it


502 error if apply reaction auto-mapping tool

Steps to Reproduce

Open the structure
reaction_2.zip
Select reaction-automapping tool
Select any from drop down field
Click OK

Expected behavior
reaction auto-mapping applied to the structure
Actual behavior
Error is shown
Screenshots

Desktop (please complete the following information):

OS: Chrome Version 93.0.4577.63, Firefox Version 92.0, Microsoft Edge Version 93.0.961.47

Related issue epam/Indigo/issues/529

While running manual tests, I've encountered another manifestation if this problem, so I'll leave it here too.
Steps

Checkout latest version of release/2.4 branch
yarn install, yarn build, yarn serve:standalone
Open the structure reaction_2.zip
Select reaction-automapping tool
Select any value from drop down field
Click OK

Expected behavior
reaction auto-mapping applied to the structure
Actual behavior
App crashes.
For a rich error report I've started a dev server, here's what the error is:

Fixed, tested v.2.4


Add icon checklist workflow

Description

Basis for this change discussed in  #2070
How the action works
When a PR is opened involving icons, github-actions will leave a comment. This comment can be found and edited in .github/icon_checklist.md
Here is an example of it running on a PR: https://github.com/Hamster45105/lawnicons/pull/4
Note
I removed the first_pr_interaction.yml file since it would not really be needed if this action was implemented.
Fixes #2070

Type of change

:x: Bug fix (non-breaking change which fixes an issue)
:white_check_mark: General change (non-breaking change that doesn't fit the above categories, such as copyediting)

are you happy for me to mark as ready for review now?

It's up to you. In any case, someone else will do the code review.

Great job, thanks!


undefined method 'assets'

Hey,
I'm trying to use combustion for testing my rails engine, but unfortunately upon running the specs I get the following error:
undefined method `assets' for #<Rails::Engine::Configuration:0x007f81708a4aa0> (NoMethodError)

When calling:
config.assets.precompile += %w( myscript.js )

I tried initialising :sprockets too and added it to the gemfile. Doesn't help, though.
Any ideas?
spec_helper.rb:
require 'rubygems'
require 'bundler/setup'

require 'rails'
require 'action_controller/railtie'
require 'action_view/railtie'
require 'sprockets/railtie'
require 'jquery/rails'

require 'combustion'
require 'capybara/rspec'

Combustion.initialize! :action_view, :action_controller, :sprockets

require 'rspec/rails'
require 'capybara/rails'

RSpec.configure do |config|
  config.use_transactional_fixtures = true
end

Hi Markus
Which version of Rails do you have bundled?

Hey, it's rails 3.2.21.

I don't suppose this engine is available on GitHub so I can use it to reproduce the issue locally? :)

Hey, the gem is not quite public yet. Nothing secret, really, just a formality. Have to check back with people before making it public. So for the time being I invited you to a team and gave you read access to my fork.
On the branch feature/specs I gave combustion a try and got stuck with the problem above.

Never mind, I made it public.

lobby_boy? I don't think you've pushed the feature/specs branch.

Yes, I pushed it to my fork.

Right, so the issue, from my local testing, is that config in the scope of the engine, is the engine's configuration, not the app's. You want to do this instead, within the engine definition:
initializer "lobby_boy.assets.precompile" do |app|
  app.config.assets.precompile += %w( jquery.js js.cookie-1.5.1.min.js )
end

To anyone who stumbles across this issue, I fixed it by adding sprockets-rails as a dependency:
# yourgem.gemspec
Gem::Specification.new do |s|
  # Rest of gemspec

  s.add_development_dependency "combustion"
  s.add_development_dependency "sprockets-rails"
end

Then include the sprockets railtie in Combustion:
Combustion.initialize! :active_record, :action_controller, :action_view, :sprockets

or:
Combustion.initialize! :all

Might be going about it the wrong way, but it got me onto the next roadblock.


[Suggestion] add how to develop milvus 2.0 on Mac os.

compile_milvus2_macos (1).pdf

PR #577

This is not about how to install milvus on mac. this doc is telling how to compile or develop milvus on mac os.
https://milvus.io/docs/v2.0.0/install_macos.md#vscode

This doc will be moved to the milvus repo instead.


Create cluster, stuck in provisioning

Rancher versions:
rancher/server: v2.0.0-beta1
rancher/agent: ??
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker version: (docker version,docker info preferred)
Containers: 4
Running: 1
Paused: 0
Stopped: 3
Images: 3
Server Version: 18.03.0-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-1052-aws
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.858GiB
Name: ip-172-35-0-22
ID: GGHN:DTMK:ZPFT:FJU6:STC6:OWUF:3K5V:O5UC:CVIS:KMIH:3O7D:NFJ5
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single Node
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Steps to Reproduce:
Results:
This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.
Waiting for etcd and controlplane nodes to be registered

+1

Docker versions 17.12.1 and up dont work (yet). Please try with a supported version of Docker. If this doesn't solve it, please provide the steps to reproduce.

I now tried to create a new VPC in AWS and then following theese steps:
https://rancher.com/docs/rancher/v2.0/en/quick-start-guide
Dokcer version:
Client:
Version:       17.12.0-ce
API version:   1.35
Go version:    go1.9.2
Git commit:    c97c6d6
Built: Wed Dec 27 20:11:19 2017
OS/Arch:       linux/amd64
Server:
Engine:
Version:      17.12.0-ce
API version:  1.35 (minimum version 1.12)
Go version:   go1.9.2
Git commit:   c97c6d6
Built:        Wed Dec 27 20:09:53 2017
OS/Arch:      linux/amd64
Experimental: false
Still the same problem!

Can you provide complete logging of the rancher/server container and the rancher/agent container?

Can't find the logs?
https://rancher.com/docs/rancher/latest/en/faqs/server/

The folder cattle is empty

I didn't get any more help?

Tried several times now :(

I just removed the installation, I will set up a new and try. If that doesn't work I send that.

Dosen't work for me 👎
What do you need to help me?

My cluster gets stuck in provisioning state too.
I use Docker 17.03.2 and Rancher v2.0.0-beta3-rc1.
These are the logs for an agent with roles "etcd" and "control":
+ grep -q cloud-provider=azure
+ '[' kube-apiserver == kubelet ']'
+ exec kube-apiserver --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --allow-privileged=true --admission-control=ServiceAccount,NamespaceLifecycle,LimitRanger,PersistentVolumeLabel,DefaultStorageClass,ResourceQuota,DefaultTolerationSeconds --cloud-provider= --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --authorization-mode=Node,RBAC --insecure-bind-address=<IP_ADDRESS> --insecure-port=0 --storage-backend=etcd3 --service-cluster-ip-range=<IP_ADDRESS>/16 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --bind-address=<IP_ADDRESS> --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --service-account-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --secure-port=6443 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --etcd-servers=https://HOST_IP:2379,https://AGENT_IP:2379 --etcd-prefix=/registry
I0412 06:31:46.518072       1 server.go:114] Version: v1.8.10-rancher1
I0412 06:31:46.519335       1 plugins.go:101] No cloud provider specified.
I0412 06:31:46.743317       1 logs.go:41] warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
I0412 06:31:46.743995       1 logs.go:41] warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
W0412 06:31:46.745857       1 admission.go:66] PersistentVolumeLabel admission controller is deprecated. Please remove this controller from your configuration files and scripts.

W0412 06:31:46.916185       1 genericapiserver.go:311] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no resources.
[restful] 2018/04/12 06:31:46 log.go:33: [restful/swagger] listing is available at https://AGENT_IP:6443/swaggerapi
[restful] 2018/04/12 06:31:46 log.go:33: [restful/swagger] https://AGENT_IP:6443/swaggerui/ is mapped to folder /swagger-ui/
[restful] 2018/04/12 06:31:47 log.go:33: [restful/swagger] listing is available at https://AGENT_IP:6443/swaggerapi
[restful] 2018/04/12 06:31:47 log.go:33: [restful/swagger] https://AGENT_IP:6443/swaggerui/ is mapped to folder /swagger-ui/
I0412 06:31:47.937693       1 logs.go:41] warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
I0412 06:31:51.449883       1 serve.go:85] Serving securely on <IP_ADDRESS>:6443
I0412 06:31:51.450474       1 controller.go:84] Starting OpenAPI AggregationController
I0412 06:31:51.450766       1 crd_finalizer.go:242] Starting CRDFinalizer
I0412 06:31:51.450810       1 customresource_discovery_controller.go:152] Starting DiscoveryController
I0412 06:31:51.450917       1 naming_controller.go:277] Starting NamingConditionController
I0412 06:31:51.451465       1 apiservice_controller.go:112] Starting APIServiceRegistrationController
I0412 06:31:51.451492       1 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
I0412 06:31:51.451516       1 available_controller.go:192] Starting AvailableConditionController
I0412 06:31:51.451532       1 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
I0412 06:31:51.451721       1 crdregistration_controller.go:112] Starting crd-autoregister controller
I0412 06:31:51.451738       1 controller_utils.go:1041] Waiting for caches to sync for crd-autoregister controller
I0412 06:32:21.079787       1 logs.go:41] http: TLS handshake error from HOST_IP:42378: remote error: tls: bad certificate
I0412 06:32:22.453184       1 trace.go:76] Trace[895493806]: "Create /api/v1/namespaces" (started: 2018-04-12 06:31:52.452438012 +0000 UTC) (total time: 30.000697914s):
Trace[895493806]: [30.000697914s] [30.000561401s] END
E0412 06:32:22.463668       1 client_ca_hook.go:78] Timeout: request did not complete within allowed duration
E0412 06:32:51.476725       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1.Namespace: the server was unable to return a response in the time allotted, but may still be processing the request (get namespaces)
E0412 06:32:51.478082       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *api.ResourceQuota: the server was unable to return a response in the time allotted, but may still be processing the request (get resourcequotas)
E0412 06:32:51.478190       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/kube-aggregator/pkg/client/informers/internalversion/factory.go:61: Failed to list *apiregistration.APIService: the server was unable to return a response in the time allotted, but may still be processing the request (get apiservices.apiregistration.k8s.io)
E0412 06:32:51.478281       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *rbac.ClusterRoleBinding: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterrolebindings.rbac.authorization.k8s.io)
E0412 06:32:51.478358       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1.Endpoints: the server was unable to return a response in the time allotted, but may still be processing the request (get endpoints)
E0412 06:32:51.478451       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *api.ServiceAccount: the server was unable to return a response in the time allotted, but may still be processing the request (get serviceaccounts)
E0412 06:32:51.478566       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1.Service: the server was unable to return a response in the time allotted, but may still be processing the request (get services)
E0412 06:32:51.479239       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *api.LimitRange: the server was unable to return a response in the time allotted, but may still be processing the request (get limitranges)
E0412 06:32:51.479364       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *api.Pod: the server was unable to return a response in the time allotted, but may still be processing the request (get pods)
E0412 06:32:51.479473       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *rbac.ClusterRole: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterroles.rbac.authorization.k8s.io)
E0412 06:32:51.479517       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *rbac.RoleBinding: the server was unable to return a response in the time allotted, but may still be processing the request (get rolebindings.rbac.authorization.k8s.io)
E0412 06:32:51.480421       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/apiextensions-apiserver/pkg/client/informers/internalversion/factory.go:61: Failed to list *apiextensions.CustomResourceDefinition: the server was unable to return a response in the time allotted, but may still be processing the request (get customresourcedefinitions.apiextensions.k8s.io)
E0412 06:32:51.481117       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *api.Secret: the server was unable to return a response in the time allotted, but may still be processing the request (get secrets)
E0412 06:32:51.482351       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *rbac.Role: the server was unable to return a response in the time allotted, but may still be processing the request (get roles.rbac.authorization.k8s.io)
E0412 06:32:51.483173       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *storage.StorageClass: the server was unable to return a response in the time allotted, but may still be processing the request (get storageclasses.storage.k8s.io)
E0412 06:32:51.483244       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:73: Failed to list *api.PersistentVolume: the server was unable to return a response in the time allotted, but may still be processing the request (get persistentvolumes)
E0412 06:32:52.453181       1 storage_rbac.go:172] unable to initialize clusterroles: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterroles.rbac.authorization.k8s.io)
I0412 06:32:52.466085       1 trace.go:76] Trace[758895242]: "Create /api/v1/namespaces" (started: 2018-04-12 06:32:22.46474509 +0000 UTC) (total time: 30.001301422s):
Trace[758895242]: [30.001301422s] [30.001213905s] END
E0412 06:32:52.467511       1 client_ca_hook.go:78] Timeout: request did not complete within allowed duration
F0412 06:32:52.467633       1 hooks.go:133] PostStartHook "ca-registration" failed: unable to initialize client CA configmap: timed out waiting for the condition

Interestingly it says + grep -q cloud-provider=azure although I use a custom cluster. Lots of CA / certificate errors.
I redeployed Rancher a couple of times by stopping all docker container, run docker system prune --all and pull the Rancher image again.

This must be a rather common problem? Anyone that can help?

The host in EC2 is unreachable according to the log, that's why it keeps re-creating.
NodeController cluster-87kgh/m-csv45 [node-controller] failed with : Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded

What did you configure when creating the machine, what AMI, what SSH user? And can you validate it is accessible from the host running rancher/server.

What did you configure when creating the machine, what AMI?
The one that the Cluster creation reffers to for EU-Central-1 (ami-28422647) https://github.com/rancher/os/blob/master/README.md/#user-content-amazon
what SSH user?
SSH user, never seen anything about a ssh user in the guide?
And can you validate it is accessible from the host running rancher/server.
What should be accessible? The node is created and then terminated?

It defaults to Ubuntu which uses ubuntu as SSH user. If you use the RancherOS AMI, this is stated on the section Amazon:
Amazon
SSH keys are added to the rancher user, so you must log in using the rancher user.

Great, now it works, thanks!

@MarcErdmann If re-using nodes, please clean them before re-using: https://gist.githubusercontent.com/superseb/2cf186726807a012af59a027cb41270d/raw/7cfbce916809e7b2474a73a3da367b1a7f4ac9cf/cleanup.sh
Then after, file a new issue with output of docker logs --tail=all etcd and docker logs --tail=all kube-apiserver. Thanks

Thanks! Now it works.


Screenshots in "Why use pump?" don't match actual output

The screenshot in "Why use pump?" shows neat output (no typical noisy stack traces) that indicate the error message, file, and line number:

...but it actually looks like the following.
Without pump:
/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/lib/create-error.js:6
  var perr = new GulpUglifyError(msg, cause);
             ^
GulpUglifyError: unable to minify JavaScript
    at createError (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/lib/create-error.js:6:14)
    at wrapper (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/lodash/_createHybrid.js:87:15)
    at trycatch (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/minifier.js:26:12)
    at DestroyableTransform.minify [as _transform] (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/minifier.js:76:19)
    at DestroyableTransform.Transform._read (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_transform.js:159:10)
    at DestroyableTransform.Transform._write (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_transform.js:147:83)
    at doWrite (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_writable.js:347:64)
    at writeOrBuffer (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_writable.js:336:5)
    at DestroyableTransform.Writable.write (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_writable.js:274:11)
    at DestroyableTransform.ondata (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_readable.js:546:20)

With pump:
GulpUglifyError: unable to minify JavaScript
Caused by: SyntaxError: Unexpected token: name (Foo) (line: 1, col: 6, pos: 6)

Error
    at new JS_Parse_Error (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:1547:18)
    at js_error (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:1555:11)
    at croak (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2094:9)
    at token_error (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2102:9)
    at unexpected (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2108:9)
    at semicolon (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2128:56)
    at simple_statement (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2319:73)
    at eval (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2188:19)
    at eval (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2141:24)
    at eval (eval at <anonymous> (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2909:23)

Line number is given but no source filename, which defeats the utility of the line number. Has the code changed since you made those screenshots? Was that intentionally removed? (And if so, why?) Or is it a pump-config issue?
Note the source that's piped through uglify is ES6 (to cause an error):
class Foo {
  constructor() {
    console.log('hello world');
  }
}

The gulp script for the task:
const gulp = require('gulp');
const pump = require('pump');
const $ = require('gulp-load-plugins')();

gulp.task('tony', (cb: Function) => {
  pump([
      gulp.src('src/**/*.js'),
      $.debug({title: 'tony'}),
      $.uglify(),
      gulp.dest('dist')
    ],
    cb
  );
});

Environment

gulp-uglify 2.0.1
gulp 3.9.1
macOS Sierra 10.12
node 7.5.0

I broke it in 2.0.0 by mistake when I refactored away from using the
gulp-utils. I'll fix tonight to get something similar to the old output.
On Feb 2, 2017 1:39 PM, "Tony Trinh"<EMAIL_ADDRESS>wrote:

The screenshot in "Why use pump?"
https://github.com/terinjokes/gulp-uglify/blob/ccdc482/docs/why-use-pump/README.md
shows neat output (no typical noisy stack traces) that indicate the error
message, file, and line number:
[image: pump error]
https://github.com/terinjokes/gulp-uglify/raw/ccdc482a2f9754005b9f1a0d229fa46de8ecceff/docs/why-use-pump/pump-error.png
...but in reality, it actually like the following.
Without pump:
/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/lib/create-error.js:6
var perr = new GulpUglifyError(msg, cause);
^
GulpUglifyError: unable to minify JavaScript
at createError (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/lib/create-error.js:6:14)
at wrapper (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/lodash/_createHybrid.js:87:15)
at trycatch (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/minifier.js:26:12)
at DestroyableTransform.minify [as _transform] (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/gulp-uglify/minifier.js:76:19)
at DestroyableTransform.Transform._read (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_transform.js:159:10)
at DestroyableTransform.Transform._write (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_transform.js:147:83)
at doWrite (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_writable.js:347:64)
at writeOrBuffer (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_writable.js:336:5)
at DestroyableTransform.Writable.write (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_writable.js:274:11)
at DestroyableTransform.ondata (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/readable-stream/lib/_stream_readable.js:546:20)
With pump:
GulpUglifyError: unable to minify JavaScript
Caused by: SyntaxError: Unexpected token: name (Foo) (line: 1, col: 6, pos: 6)
Error
at new JS_Parse_Error (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :1547:18)
at js_error (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :1555:11)
at croak (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2094:9)
at token_error (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2102:9)
at unexpected (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2108:9)
at semicolon (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2128:56)
at simple_statement (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2319:73)
at eval (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2188:19)
at eval (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2141:24)
at eval (eval at  (/Users/tony/src/polymer/polymer-typescript-starter-kit/node_modules/uglify-js/tools/node.js:28:1), :2909:23)
Line number is given but no source filename, which defeats the utility of
the line number. Has the code changed since you made those screenshots? Was
that intentionally removed? (And if so, why?) Or is it a pump-config issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/terinjokes/gulp-uglify/issues/264, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQsZXsiNa7mzi3Z_BVgc6ZR_-2gP9eTks5rYkzMgaJpZM4L1qxJ
.

@tony19 To clear up some confusion: the line and column information you had in your error message is embedded within UglifyJS's error string. UglifyJS doesn't really know about more than one file at a time, thus why it doesn't include the filename in the error.
I failed to correct the error string (to add our own file and line information) when we moved to a new error wrapper in v2.0.0. This has now been corrected in v2.1.1.
The screenshots still don't exactly match, but the same information is now contained.