ZipDelpoy on azure web app linux fails during kudu sync

We are deploying a PHP Zip file to Azure App Service for Linux on a Premium (P1V2) Linux App Service Plan. It fails during the Kudu Sync step while processing files:
2019-05-08T04:06:36.2389539Z Command: "/home/site/deployments/tools/deploy.sh"
2019-05-08T04:06:36.2389838Z Handling Basic Web Site deployment.
2019-05-08T04:06:36.2390093Z Kudu sync from: '/tmp/zipdeploy/extracted' to: '/home/site/wwwroot’
…
….
2019-05-08T04:06:36.2403894Z Processed 11560 files...
2019-05-08T04:06:36.2404111Z Processed 14025 files...
2019-05-08T04:06:36.2404338Z An unknown error has occurred. Check the diagnostic log for details.
2019-05-08T04:06:36.2478968Z ##[error]Failed to deploy web package to App Service.
Note that we deploy this exact same Zip file to identical (Premium P1V2) Windows instances without issue. This problem is intermittent, and specific to App Service For Linux deployments. We have seen this occur in multiple Azure Regions - so this isn't a flaky instance or zone-specific issue. It seems like a bug in the Azure App Service Deploy task itself, which only occurs on App Service For Linux deployments. Azure Support staff have mentioned that it appears to be causing a Docker Container restart, which is killing the deployment process.

@rramachand21   can you assist this user?

Team,
We have got one more customer DTS on same scenario. Can you please take a look into this at priority
Snippet of  logs
2019-05-13T23:48:15.2050106Z Error: From directory doesn't exist
2019-05-13T23:48:15.2050349Z An error has occurred during web site deployment.
2019-05-13T23:48:15.2050418Z Kudu Sync failed
2019-05-13T23:48:15.2050481Z \n/opt/Kudu/bin/Scripts/starter.sh "/home/site/deployments/tools/deploy.sh"
2019-05-13T23:48:15.2050604Z App container will begin restart within 10 seconds.
2019-05-13T23:48:15.2107637Z ##[error]Failed to deploy web package to App Service.
2019-05-13T23:48:15.2116824Z ##[debug]Processed: ##vso[task.issue type=error;]Failed to deploy web package to App Service.
2019-05-13T23:48:15.2127512Z ##[debug]Deployment Failed with Error: Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
2019-05-13T23:48:15.2127716Z ##[debug]task result: Failed
2019-05-13T23:48:15.2128148Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
2019-05-13T23:48:15.2128563Z ##[debug]Processed: ##vso[task.issue type=error;]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
2019-05-13T23:48:15.2129561Z ##[debug]Processed: ##vso[task.complete result=Failed;]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
2019-05-13T23:48:15.2148489Z ##[debug][POST]https://management.azure.com/subscriptions/<subscription Id>/resourceGroups/spreevel/providers/Microsoft.Web/sites/Spreedix2/config/appsettings/list?api-version=2016-08-01

We are also having the same problem deploying to our Linux B1 app services. There are eight in separate app service plans, and have seen random failures across all of them. It is an intermittent issue and re-running the deployment eventually does succeed.
Example log:
2019-07-01T16:29:52.0074562Z Package deployment using ZIP Deploy initiated.
2019-07-01T16:30:07.7763815Z Fetching changes.
2019-07-01T16:30:08.1841003Z Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/7e26b992-ac80-4f1c-89ac-027684a25a66.zip (1.27 MB) to /tmp/zipdeploy/extracted
2019-07-01T16:30:08.1901108Z ##[error]Failed to deploy web package to App Service.
2019-07-01T16:30:08.1909376Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
2019-07-01T16:30:11.6780546Z Successfully added release annotation to the Application Insight : xxx-yyy-zzz
2019-07-01T16:30:12.2726654Z Successfully updated deployment History at https://xxx-yyy-zzz.scm.azurewebsites.net/api/deployments/111111111111
2019-07-01T16:30:12.6429723Z App Service Application URL: https://xxx-yyy-zzz.azurewebsites.net
2019-07-01T16:30:12.6633655Z ##[section]Finishing: Deploy Site

We are also facing Same Issue. Works well with Widows WebApp and failed with Linux WebApp.

Also having the same issue. Log snippet:
2019-10-07T17:52:10.6075020Z Processed 96267 files...
2019-10-07T17:52:10.6075086Z Processed 97524 files...
2019-10-07T17:52:10.6075200Z Processed 99527 files...
2019-10-07T17:52:10.6075282Z An unknown error has occurred. Check the diagnostic log for details.
2019-10-07T17:52:10.6160866Z ##[error]Failed to deploy web package to App Service.
2019-10-07T17:52:10.6171123Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
2019-10-07T17:52:13.3119324Z Successfully added release annotation to the Application Insight : tc-egis-b9eb
2019-10-07T17:52:14.0541850Z Successfully updated deployment History at https://tc-egis.scm.azurewebsites.net/api/deployments/1791570470733307
2019-10-07T17:52:14.2915923Z App Service Application URL: http://tc-egis.azurewebsites.net
2019-10-07T17:52:14.3153074Z ##[section]Finishing: Deploy Azure Function App

The same :(
2020-02-29T17:06:08.2983939Z Package deployment using ZIP Deploy initiated.
2020-02-29T17:26:43.0604255Z Updating submodules.
2020-02-29T17:26:43.0609942Z Preparing deployment for commit id '5990ad07ae'.
2020-02-29T17:26:43.0611103Z Repository path is /tmp/zipdeploy/extracted
2020-02-29T17:26:43.0611819Z Running oryx build...
2020-02-29T17:26:46.0687104Z Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 12 -i /tmp/8d7bd3a35c34740 -p compress_node_modules=tar-gz --log-file /tmp/build-debug.log
2020-02-29T17:26:46.0689704Z Build orchestrated by Microsoft Oryx, https://github.com/Microsoft/Oryx
2020-02-29T17:26:46.0690529Z You can report issues at https://github.com/Microsoft/Oryx/issues
2020-02-29T17:26:46.0691156Z
2020-02-29T17:26:46.0691731Z Oryx Version      : 0.2.20191105.2, Commit: 67e159d71419415435cb5d10c05a0f0758ee8809, ReleaseTagName: 20191105.2
2020-02-29T17:26:46.0692333Z Build Operation ID: |7ga48LrNSwY=.8449380c_
2020-02-29T17:26:46.0692830Z Repository Commit : 5990ad07ae024887ac6441fac1124b1e
2020-02-29T17:26:46.0693129Z
2020-02-29T17:26:46.0693782Z Using intermediate directory '/tmp/8d7bd3a35c34740'.
2020-02-29T17:26:46.0694106Z
2020-02-29T17:26:46.0694482Z Copying files to the intermediate directory...
2020-02-29T17:26:46.0694845Z Done in 8 sec(s).
2020-02-29T17:26:46.0695080Z
2020-02-29T17:26:46.0695375Z Source directory     : /tmp/8d7bd3a35c34740
2020-02-29T17:26:46.0695775Z Destination directory: /home/site/wwwroot
2020-02-29T17:26:46.0696060Z
2020-02-29T17:26:46.0696232Z
2020-02-29T17:26:46.0696537Z Using Node version:
2020-02-29T17:26:46.0696871Z v12.13.0
2020-02-29T17:26:46.0697002Z
2020-02-29T17:26:46.0697169Z Using Yarn version:
2020-02-29T17:26:46.0697370Z 1.17.3
2020-02-29T17:26:46.0697891Z
2020-02-29T17:26:46.0698086Z Configuring Yarn cache folder...
2020-02-29T17:26:46.0698336Z yarn config v1.17.3
2020-02-29T17:26:46.0698892Z success Set "cache-folder" to "/usr/local/share/yarn-cache".
2020-02-29T17:26:46.0699205Z Done in 0.62s.
2020-02-29T17:26:46.0699344Z
2020-02-29T17:26:46.0699740Z Running 'yarn install --prefer-offline'...
2020-02-29T17:26:46.0700059Z
2020-02-29T17:26:46.0700231Z yarn install v1.17.3
2020-02-29T17:26:46.0700451Z [1/4] Resolving packages...
2020-02-29T17:26:46.0700780Z [2/4] Fetching packages...
2020-02-29T17:26:46.0701440Z info There appears to be trouble with your network connection. Retrying...
2020-02-29T17:26:46.0701879Z info There appears to be trouble with your network connection. Retrying...
2020-02-29T17:26:46.0702293Z info There appears to be trouble with your network connection. Retrying...
2020-02-29T17:26:46.0703158Z info There appears to be trouble with your network connection. Retrying...
2020-02-29T17:26:46.0706927Z info There appears to be trouble with your network connection. Retrying...
2020-02-29T17:26:46.0746701Z info There appears to be trouble with your network connection. Retrying...
2020-02-29T17:26:46.0747312Z info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
2020-02-29T17:26:46.0754650Z info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
2020-02-29T17:26:46.0755529Z info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
2020-02-29T17:26:46.0756908Z info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
2020-02-29T17:26:46.0757538Z [3/4] Linking dependencies...
2020-02-29T17:26:46.0762029Z warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^7.0.0".
2020-02-29T17:26:46.0763157Z warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>2020-02-29T17:26:46.0767314Z warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>2020-02-29T17:26:46.0770416Z warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>2020-02-29T17:26:46.0771552Z warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>2020-02-29T17:26:46.0772491Z warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^16.0.0".
2020-02-29T17:26:46.0773470Z warning "react-pdf ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4.0.0-alpha.0 || ^4.0.0".
2020-02-29T17:26:46.0774618Z warning "react-pdf > pdfjs-dist ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4.0.0-alpha.0 || ^4.0.0".
2020-02-29T17:26:46.0777172Z warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>2020-02-29T17:26:46.0778250Z warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>2020-02-29T17:26:46.0779210Z warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>2020-02-29T17:26:46.0779952Z An unknown error has occurred. Check the diagnostic log for details.
2020-02-29T17:26:46.0815835Z ##[error]Failed to deploy web package to App Service.
2020-02-29T17:26:46.0827631Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.

Currently crippled by this issue

@sanchitmehta   please assist.

Facing the same issue.
I am amazed that just nobody gets any support.

We are also experiencing this occasionally.
Looking into the deployment logs in Kudu at the specified time, the suspicious entries are as follows:

--
  |
  |
  |

Running the deployment a second time was successful.

@suwatch since you've replied first once this was reported last year, can you give us an overview of the current state of investigation of this issue?
Or @rramachand21 did you take a look at this?
It seems to affect a notable number of customers and I can as well confirm that it's still an issue to this day.

@jamesfaceface We are actively working on fixing the above issue by next App Service release cycle which would be around end of September.
@Gerrit-K Can you paste the error trace ?
To give an idea of the issue: App Service uses an NFS based Volume to host the App's /home directory. Kudu on Linux uses this mounted NFS share to host locks used during deployment for various purposes (to ensure there is just on active deployment at a time, to lock the writes to the deployment status file). These locks don't work well when Kudu is hosted on multi-instances (mostly due to latency in NFS Based calls and our previous implementation of these locks being flock files). We are working on revamping the locking system and make it reliant.

@sanchitmehta Thanks for the prompt response! It's good to hear that this issue is being actively worked on.
Unfortunately due to several reasons I am not able to share the trace, but I've seen an error similar to the one reported by @jamesfaceface: Deployment Lock Failure. In our case, we're running multiple apps on one service plan and if we deploy everything, most deployments fail at more or less exactly the 20 minute mark (which, based on your explanation, is probably a lock timeout?).
I've tested WEBSITE_RUN_FROM_PACKAGE=1 for those apps that don't need a writable file system and it seems to improve the situation currently, but that might be a volatile observation as these failures weren't deterministic for us. Still, thanks for the hint!
Looking forward for any updates (and of course hopefully a fix) on this topic.

Moving each app to its own dedicated app service plan reduced the occurrence frequency of this issue, but didn't completely diminish it. Out of 8 parallel app deployments, there was still one that failed. This time I also retrieved the exception stack trace:

Click here to view
2020-08-19T12:51:12    Error occurred, type: error, text: Object reference not set to an instance of an object., stackTrace:    at Kudu.Contracts.Infrastructure.LockExtensions.LockOperationAsync(IOperationLock lockObj, Func`1 operation, String operationName, TimeSpan timeout) in /tmp/KuduLite/Kudu.Contracts/Infrastructure/LockExtensions.cs:line 76
   at Kudu.Services.Deployment.DeploymentController.Deploy(String id) in /tmp/KuduLite/Kudu.Services/Deployment/DeploymentController.cs:line 135
   at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync()
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter()
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync()
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync()
   at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapWhenMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Kudu.Services.Web.Tracing.TraceMiddleware.Invoke(HttpContext context) in /tmp/KuduLite/Kudu.Services.Web/Tracing/TraceMiddleware.cs:line 64
2020-08-19T12:51:13      Outgoing response, type: response, statusCode: 400, statusText: BadRequest

@sanchitmehta is this the issue you've described and does the trace help you in any way or were you already aware of it?

I'm confident that we have NFS locking issues during deployment. For example, files .python_packages are locked, even from rm:

WEBSITE_RUN_FROM_PACKAGE=1 is a poor option for us because we can't programatically rotate the function host keys with a read only file system or benefit from pycache/grpc files.

We are actively working on fixing the above issue by next App Service release cycle which would be around end of September.

@sanchitmehta
Any news on this? It's now October, but I didn't dare to revert back to our previous setup and test because this issue seems almost untouched since then :/

@sanchitmehta @SumiranAgg We are also facing the problem having a random error for Kudu sync for subsequent deployments for Linux Python Azure Function App. This issue seems to sit open since last year. It is adversely affecting our developments and deployments on Linux Python Azure Function Apps. Could you please updates on this or provide a workaround solution?
@Gerrit-K @SumiranAgg @mattmelton Have you found any workaround for this issue?
Attempt 1
2020-11-04T17:06:57.4362725Z ##[section]Starting: Deploy Azure Function App
2020-11-04T17:06:57.4374239Z ==============================================================================
2020-11-04T17:06:57.4374594Z Task         : Azure Functions
2020-11-04T17:06:57.4375018Z Description  : Update a function app with .NET, Python, JavaScript, PowerShell, Java based web applications
2020-11-04T17:06:57.4375400Z Version      : 1.163.7
2020-11-04T17:06:57.4375674Z Author       : Microsoft Corporation
2020-11-04T17:06:57.4375996Z Help         : https://aka.ms/azurefunctiontroubleshooting
2020-11-04T17:06:57.4376379Z ==============================================================================
2020-11-04T17:06:58.0771407Z Got service connection details for Azure App Service:'name of app'
2020-11-04T17:06:59.0305223Z Trying to update App Service Application settings. Data: {"WEBSITES_ENABLE_APP_SERVICE_STORAGE":"true","WEBSITE_RUN_FROM_PACKAGE":"true"}
2020-11-04T17:06:59.2751323Z App Service Application settings are already present.
2020-11-04T17:07:01.0818186Z Package deployment using ZIP Deploy initiated.
2020-11-04T17:09:45.9907407Z Updating submodules.
2020-11-04T17:09:45.9908306Z Preparing deployment for commit id 'commit id'.
2020-11-04T17:09:45.9909209Z Generating deployment script.
2020-11-04T17:09:48.8441340Z Using cached version of deployment script (command: 'azure -y --no-dot-deployment -r "/tmp/zipdeploy/extracted" -o "/home/site/deployments/tools" --basic --sitePath "/tmp/zipdeploy/extracted"').
2020-11-04T17:09:48.8442007Z Running deployment command...
2020-11-04T17:09:50.4397280Z Command: "/home/site/deployments/tools/deploy.sh"
2020-11-04T17:09:50.4397690Z Handling Basic Web Site deployment.
2020-11-04T17:09:50.4398324Z Kudu sync from: '/tmp/zipdeploy/extracted' to: '/home/site/wwwroot'
2020-11-04T17:09:50.4398860Z Copying file: 'azure-pipelines.yml'
2020-11-04T17:09:50.4401765Z Copying file: 'azure-pipelines2.yml'
2020-11-04T17:09:50.4402719Z Deleting file: 'host.json'
2020-11-04T17:09:50.4403761Z Deleting directory: 'worker_venv/lib/python3.6/site-packages/statsmodels/tsa/base/pycache'
2020-11-04T17:09:50.4405095Z Error: ENOENT: no such file or directory, rmdir '/home/site/wwwroot/worker_venv/lib/python3.6/site-packages/statsmodels/tsa/base/pycache'
2020-11-04T17:09:50.4405948Z An error has occurred during web site deployment.
2020-11-04T17:09:50.4406474Z Kudu Sync failed
2020-11-04T17:09:50.4407066Z \n/opt/Kudu/Scripts/starter.sh "/home/site/deployments/tools/deploy.sh"
2020-11-04T17:09:50.4452537Z ##[error]Failed to deploy web package to App Service.
2020-11-04T17:09:50.4476186Z ##[error]To debug further please check Kudu stack trace URL : https://'name of app'.scm.azurewebsites.net/api/vfs/LogFiles/kudu/trace
2020-11-04T17:09:50.4477867Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
2020-11-04T17:09:51.5189816Z Successfully added release annotation to the Application Insight : ddw-test-ana-idm-func-code
2020-11-04T17:09:54.5333501Z Successfully updated deployment History at https://'name of app'.scm.azurewebsites.net/api/deployments/'deployment id'
2020-11-04T17:09:54.8685348Z App Service Application URL: http://'name of app'.azurewebsites.net
2020-11-04T17:09:54.8845492Z ##[section]Finishing: Deploy Azure Function App

Attempt 2
2020-11-04T17:06:57.4362725Z ##[section]Starting: Deploy Azure Function App
2020-11-04T17:06:57.4374239Z ==============================================================================
2020-11-04T17:06:57.4374594Z Task         : Azure Functions
2020-11-04T17:06:57.4375018Z Description  : Update a function app with .NET, Python, JavaScript, PowerShell, Java based web applications
2020-11-04T17:06:57.4375400Z Version      : 1.163.7
2020-11-04T17:06:57.4375674Z Author       : Microsoft Corporation
2020-11-04T17:06:57.4375996Z Help         : https://aka.ms/azurefunctiontroubleshooting
2020-11-04T17:06:57.4376379Z ==============================================================================
2020-11-04T17:06:58.0771407Z Got service connection details for Azure App Service:'name of app'
2020-11-04T17:06:59.0305223Z Trying to update App Service Application settings. Data: {"WEBSITES_ENABLE_APP_SERVICE_STORAGE":"true","WEBSITE_RUN_FROM_PACKAGE":"true"}
2020-11-04T17:06:59.2751323Z App Service Application settings are already present.
2020-11-04T17:07:01.0818186Z Package deployment using ZIP Deploy initiated.
2020-11-04T17:09:45.9907407Z Updating submodules.
2020-11-04T17:09:45.9908306Z Preparing deployment for commit id 'commit id'.
2020-11-04T17:09:45.9909209Z Generating deployment script.
2020-11-04T17:09:48.8441340Z Using cached version of deployment script (command: 'azure -y --no-dot-deployment -r "/tmp/zipdeploy/extracted" -o "/home/site/deployments/tools" --basic --sitePath "/tmp/zipdeploy/extracted"').
2020-11-04T17:09:48.8442007Z Running deployment command...
2020-11-04T17:09:50.4397280Z Command: "/home/site/deployments/tools/deploy.sh"
2020-11-04T17:09:50.4397690Z Handling Basic Web Site deployment.
2020-11-04T17:09:50.4398324Z Kudu sync from: '/tmp/zipdeploy/extracted' to: '/home/site/wwwroot'
2020-11-04T17:09:50.4398860Z Copying file: 'azure-pipelines.yml'
2020-11-04T17:09:50.4401765Z Copying file: 'azure-pipelines2.yml'
2020-11-04T16:46:35.0746125Z Deleting file: 'worker_venv/lib/python3.6/site-packages/openpyxl/chart/surface_chart.py'
2020-11-04T16:46:35.0748217Z Error: ENOENT: no such file or directory, unlink '/home/site/wwwroot/worker_venv/lib/python3.6/site-packages/openpyxl/chart/surface_chart.py'
2020-11-04T16:46:35.0748713Z An error has occurred during web site deployment.
2020-11-04T16:46:35.0748960Z Kudu Sync failed
2020-11-04T17:09:50.4407066Z \n/opt/Kudu/Scripts/starter.sh "/home/site/deployments/tools/deploy.sh"
2020-11-04T17:09:50.4452537Z ##[error]Failed to deploy web package to App Service.
2020-11-04T17:09:50.4476186Z ##[error]To debug further please check Kudu stack trace URL : https://'name of app'.scm.azurewebsites.net/api/vfs/LogFiles/kudu/trace
2020-11-04T17:09:50.4477867Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.**
2020-11-04T17:09:51.5189816Z Successfully added release annotation to the Application Insight : ddw-test-ana-idm-func-code
2020-11-04T17:09:54.5333501Z Successfully updated deployment History at https://'name of app'.scm.azurewebsites.net/api/deployments/'deployment id'
2020-11-04T17:09:54.8685348Z App Service Application URL: http://'name of app'.azurewebsites.net
2020-11-04T17:09:54.8845492Z ##[section]Finishing: Deploy Azure Function App

@Gerrit-K @SumiranAgg @mattmelton Have you found any workaround for this issue?

@Anmol007 Unfortunately no. The only "workaround" was to use dedicated app service plans for each app service. Since then the locking errors drastically reduced in frequency (but still appear from time to time). But this of course comes means less flexibility and more costs, so it's not acceptable in the long run.

Have you found any workaround for this issue?

Environment independent ACR + Docker image deployment using the Python AppService base (
mcr.microsoft.com/azure-functions/python:3.0-python3.8-appservice).
We invested in vscode dev containers too. I'm confident I'll never go back to Oryx/Kudu deployments.

facing issue

I had absolutely the same issue. At the beginning I had it time to time and 1 day it started to appear constantly. I was not able to find the solution and had to migrate to App Service with windows and make all the settings for my NextJs app like in the following article - https://parveensingh.com/next-js-deployment-on-azure-app-service.

Does this mean we cant use linux azure web app for hosting next-js?

Check if you have an environment variable set on your web app, under key PROJECT. This seemed to cause this issue for me.
After removing the PROJECT environment variable (and restarting the app), I could confirm in the generated deploy.sh that the value was removed, and deployment was successful again.
I started seeing the problem upgrading from .Net 6 to .Net 7 on a Blazor WebAssembly application.

I've just been hit by a similar problem to this as well:
Error: ENOTDIR: not a directory, scandir '/home/site/wwwroot/node_modules/classnames'
An error has occurred during web site deployment.
Kudu Sync failed
\n/opt/Kudu/Scripts/starter.sh "/home/site/deployments/tools/deploy.sh"
Deployment Failed. deployer = GITHUB_ZIP_DEPLOY deploymentPath = ZipDeploy. Extract zip.
Error: Failed to deploy web package to App Service.
Error: Deployment Failed, Package deployment using ZIP Deploy failed. Refer logs for more details.

Not sure it is the same issue but I started to get strange error during web app startup. I use zip deployment with WEBSITE_RUN_FROM_PACKAGE = 1. The exact same package I deploy to azure works perfectly on the same node version locally and worked fine on azure a week ago. Now I am getting this error:
2023-09-26T09:05:13.182028937Z Starting OpenBSD Secure Shell server: sshd.
2023-09-26T09:05:13.393802701Z Starting periodic command scheduler: cron.
2023-09-26T09:05:13.471027445Z Could not find build manifest file at '/home/site/wwwroot/oryx-manifest.toml'
2023-09-26T09:05:13.471094746Z Could not find operation ID in manifest. Generating an operation id...
2023-09-26T09:05:13.471109446Z Build Operation ID: 29d27ec9-8757-4105-bd40-e747750d8bd8
2023-09-26T09:05:13.805856371Z Environment Variables for Application Insight's IPA Codeless Configuration exists..
2023-09-26T09:05:13.816235512Z Writing output script to '/opt/startup/startup.sh'
2023-09-26T09:05:13.936853343Z Running #!/bin/sh
2023-09-26T09:05:13.936885043Z
2023-09-26T09:05:13.936898443Z # Enter the source directory to make sure the script runs where the user expects
2023-09-26T09:05:13.936903543Z cd "/home/site/wwwroot"
2023-09-26T09:05:13.936908343Z
2023-09-26T09:05:13.936912743Z export NODE_PATH=/usr/local/lib/node_modules:$NODE_PATH
2023-09-26T09:05:13.936917443Z if [ -z "$PORT" ]; then
2023-09-26T09:05:13.936921943Z 		export PORT=8080
2023-09-26T09:05:13.936926844Z fi
2023-09-26T09:05:13.936931044Z
2023-09-26T09:05:13.936935444Z PATH="$PATH:/home/site/wwwroot" node --unhandled-rejections=strict ./packages/cosmos-webservice/dist/app.js
2023-09-26T09:05:38.000471984Z /home/site/wwwroot/node_modules/@graphql-tools/load/cjs/load-typedefs/load-file.js:83
2023-09-26T09:05:38.000605186Z                 throw errors[0];
2023-09-26T09:05:38.001275094Z                 ^
2023-09-26T09:05:38.001286695Z
2023-09-26T09:05:38.001291895Z Error: ENOTDIR: not a directory, scandir '/home/site/wwwroot/node_modules/yargs/yargs'
2023-09-26T09:05:38.001297795Z     at Object.readdirSync (node:fs:1527:3)
2023-09-26T09:05:38.001314495Z     at readdirWithFileTypes (/home/site/wwwroot/node_modules/@nodelib/fs.scandir/out/providers/sync.js:16:33)
2023-09-26T09:05:38.001320295Z     at Object.read (/home/site/wwwroot/node_modules/@nodelib/fs.scandir/out/providers/sync.js:10:16)
2023-09-26T09:05:38.001325795Z     at SyncReader.scandirSync [as _scandir] (/home/site/wwwroot/node_modules/@nodelib/fs.scandir/out/index.js:18:17)
2023-09-26T09:05:38.001331395Z     at SyncReader._handleDirectory (/home/site/wwwroot/node_modules/@nodelib/fs.walk/out/readers/sync.js:28:34)
2023-09-26T09:05:38.001337595Z     at SyncReader._handleQueue (/home/site/wwwroot/node_modules/@nodelib/fs.walk/out/readers/sync.js:23:18)
2023-09-26T09:05:38.001343195Z     at SyncReader.read (/home/site/wwwroot/node_modules/@nodelib/fs.walk/out/readers/sync.js:15:14)
2023-09-26T09:05:38.001348395Z     at SyncProvider.read (/home/site/wwwroot/node_modules/@nodelib/fs.walk/out/providers/sync.js:11:29)
2023-09-26T09:05:38.001353795Z     at ReaderSync.walkSync [as _walkSync] (/home/site/wwwroot/node_modules/@nodelib/fs.walk/out/index.js:20:21)
2023-09-26T09:05:38.001359295Z     at ReaderSync.dynamic (/home/site/wwwroot/node_modules/fast-glob/out/readers/sync.js:13:21) {
2023-09-26T09:05:38.001364896Z   errno: -20,
2023-09-26T09:05:38.001370196Z   syscall: 'scandir',
2023-09-26T09:05:38.001375496Z   code: 'ENOTDIR',
2023-09-26T09:05:38.001380896Z   path: '/home/site/wwwroot/node_modules/yargs/yargs'
2023-09-26T09:05:38.001385596Z }
2023-09-26T09:05:38.001404096Z
2023-09-26T09:05:38.001409796Z Node.js v18.17.1

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service

Check if you have an environment variable set on your web app, under key PROJECT. This seemed to cause this issue for me. After removing the PROJECT environment variable (and restarting the app), I could confirm in the generated deploy.sh that the value was removed, and deployment was successful again.
I started seeing the problem upgrading from .Net 6 to .Net 7 on a Blazor WebAssembly application.

9 months after this comment, its what fixed my issues. Thanks @PolygeneLubricants


[WIP] npm package

As discussed, let's merge this and I will create another PR with fixes and cleanups.


LXC migration failing

Hi, I have an issue similar to the one here: https://github.com/lxc/lxd/issues/2019
root@iZ6wefy8r9jd5wk9ee5va8Z:~# lxc move srv-dc-seafile awss:
error: Unable to connect to: <IP_ADDRESS>:8443
However I know it's not a firewall issue and can connect to both ends:
[Local]
root@iZ6wefy8r9jd5wk9ee5va8Z:~# nc -vz <IP_ADDRESS> 8443
Connection to <IP_ADDRESS> 8443 port [tcp/*] succeeded!
[Remote]
root@ip-172-31-14-246:~# nc -vz <IP_ADDRESS> 8443
Connection to <IP_ADDRESS> 8443 port [tcp/*] succeeded!
Any idea what could be happening here?

Is <IP_ADDRESS> maybe defined on both hosts as a local IP? In which case the target host can indeed connect to that IP, but it's talking to the wrong machine.


Seed Breaking Sound

MC 1.12.2
Genera 1.0.3
Forge 2512
The Breaking Stone of Burdock and Nightshade is the Stone breaking sound. Can you change it to the Grass/Wheat breaking sound?

Fixed. Will commit after testing.


Setting custom timeout not working

Hello,
I have found out that for OkHttp version 3.8.1 (I was also trying version 3.7.0 and result was the same) setting custom timeout is not working. I use it with retrofit version 2.3.0 and after changing timeout in OkHttpClient timeouts are thrown still after 10 seconds. I have asked question on stack overflow, but no answer was fixing my problem, so I assume that there is something going on here. Here is how I change timeouts:
OkHttpClient client = new OkHttpClient.Builder() .connectTimeout(20, TimeUnit.SECONDS) .writeTimeout(20, TimeUnit.SECONDS) .readTimeout(20, TimeUnit.SECONDS) .build()
and then I just attach it to retrofit builder like:
builder.client(client)
but it has no effect. Request throw SocketTimeoutException after 10 seconds. I was also trying to set 0 as timeout, but is was not working too.
Can you take a look at this?
Best regards,
Patryk

Can you confirm if you actually mean 3.8.1 and 3.7.0?

Yes I meant 3.8.1 and 3.7.0. Sorry

Can you create a failing test case, I just tested using a CLI against https://httpbin.org/delay/10 (annoyingly max of 10 seconds) and it worked perfectly.

I use OkHttp 3.8.0 at work，but timeout not working,  can you give me a some suggest? Thanks!

hi,@jablonskipj ,I met a similar problemI use okhttp to upload some imgs.I set like this " OkHttpClient.Builder builder = new OkHttpClient.Builder()                 .connectTimeout(5, TimeUnit.SECONDS)                 .writeTimeout(5, TimeUnit.SECONDS)                 .readTimeout(5, TimeUnit.SECONDS);         client = builder.build();",but it didnt work .it will spend long time more than 1min when the network have a low speed .i couldnt resolve it .do you have some ideas? thanks very mush

@wangzhen6039 in my case the problem was that I had an implementation of SSL and I was creating custom OkHttpClient that was overriding my further implementation. I was setting there timeout and I was not able to change it. I have forgot about it and spend a lot of time to find the problem which was simple. Take a look at your own code and check if you have no other implementation of OkHttpClient which is overriding your timeouts.

Hi,
I am using the below code. I am not using any custom OkHttpClient class object.
OkHttpClient client = new OkHttpClient.Builder()
.connectTimeout(5 , TimeUnit.SECONDS)
.writeTimeout(5 ,TimeUnit.SECONDS)
.readTimeout(5 ,TimeUnit.SECONDS)
.retryOnConnectionFailure(false)
.build();
But httpRequest never times out on 5 seconds.  Could anyone help. Thanks

@bhavyav8421 can you create a failing test case.  Alternatively post your problem and runnable example code to stackoverflow.  The issue tracker is not the preferred support route for trouble shooting.

Hi ,
In my case, I have connected to a wifi which doesn't have internet.
And in the retrofit configuration, I set the timeout as 10second.  the exception thrown is UnknownHostException after around 30 secons if I access any api.  As I have specified 10seconds timeout, I am expected to receive SocketTimeoutException after 10seconds. Let me know if I am wrong.
Even if I use HttpUrlConnection instead of retrofit, I am getting UnknownHostException after 30 seconds.

Any answer for @bhavyav8421 question?

I'm more and more disappointed in this product.
I cause a defect on the product and yet I have to write tests to you instead of the developer who blew this defect.
The code that provided @ bhavyav8421 completely reflects the problem and I confirm this defect, but instead of fixing you just closed the issue.

It's not a product. You didn't pay for it.
On Sat, Jun 23, 2018, 11:42 AM Shaburov Oleg<EMAIL_ADDRESS>wrote:

I'm more and more disappointed in this product.
I cause a defect on the product and yet I have to write tests to you
instead of the developer who blew this defect.
The code that provided @ bhavyav8421 completely reflects the problem and I
confirm this defect, but instead of fixing you just closed the issue.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/3553#issuecomment-399687358, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEETErOY7Ps66I_siy06VaxhodnBLPks5t_mHXgaJpZM4PG-4W
.

@shaburov I'm sorry you feel that way.  Ultimately I agree with @JakeWharton
If you see above I ran a test against https://httpbin.org/delay/10 and I confirmed the correct behaviour with the latest version.  At this point there is probably something else going on but none of the reports above help us diagnose the specific problem.  I interpret your response as valuing our time as near zero in doing the ground work to find the problem, which is why I push back a bit and ask for something concrete and runnable we can investigate.

@yschimke I may have been a little rash. I'm sorry.
Connection timeout must also extend to the expectation of resolving the host (DNS).

The original report is that failures are too fast. Faster than custom timeout.
I think you’ve identified a legit bug/improvement with handling DNS but it likely has a different cause/fix than this reported issue.
Would you care to file a specific issue for timing out DNS calls?
Our current timeouts are very low level (connect socket, read/write next byte), below the layer of abstraction we provide (request). So we may want to make a general request level timeout also.

For the retrofit users, good comment by @JakeWharton on a related issue that Retrofit gives you per request timeouts already
https://github.com/square/okhttp/issues/2840#issuecomment-245927547

This is not the best solution. But this code works just fine:
After setting retrofit request call timeOutRetrofitHandler(); method.
    private Handler handler;
    private Runnable runnable;

    private void timeOutRetrofitHandler() {

        if (null != handler && null != runnable) {
            handler.removeCallbacks(runnable);
        }

        handler = new Handler();
        runnable = () -> {
            dismissRetrofitProgress();
            Toast.makeText(context, getResources().getString(R.string.error_msg_timeout), Toast.LENGTH_SHORT).show();
        };
        handler.postDelayed(runnable, (DEFAULT_TIMEOUT_SEC + 1) * 1000);
    }

    private void dismissRetrofitProgress() {
        if (null != handler && null != runnable) {
            handler.removeCallbacks(runnable);
        }
        retrofitRequestCancel();
        dismissProgress();
    }

    private void retrofitRequestCancel() {
        if (null != call) {
            call.cancel();
        }
    }

I spent a couple of hours trying to figure out why my app would not throw an UnknownHostException for at least 40 seconds.
I launched it in an Android Pie emulator, turned off the internet on my laptop, click a button to do a network request (Retrofit 2.5.0) and am then forced to sit there for precisely 40 seconds until it throws the exception. In a KitKat emulator it was reliably taking 170 seconds. I then made a little unit test and it worked perfectly in the JVM.
So the answer for me was the emulators themselves do something very odd with network connectivity I can't explain when the connection is dropped. When I checked on a real device it would instantly throw the exception regardless of timeout settings. Hope this helps someone!

@wangzhen6039 in my case the problem was that I had an implementation of SSL and I was creating custom OkHttpClient that was overriding my further implementation. I was setting there timeout and I was not able to change it. I have forgot about it and spend a lot of time to find the problem which was simple. Take a look at your own code and check if you have no other implementation of OkHttpClient which is overriding your timeouts.

Thank for your answer! I just forgot I'm using custom OkHttpClient as well.

Thank you @dannyZhou
Works fine OkHttp 4.9.3

@wangzhen6039 try this : .retryOnConnectionFailure(false)
Full codes:
OkHttpClient client = new OkHttpClient.Builder()
            .connectTimeout(10, TimeUnit.SECONDS)
            .readTimeout(10, TimeUnit.SECONDS)
            .writeTimeout(10, TimeUnit.SECONDS)
            .retryOnConnectionFailure(false)
            .build();

OKHTTP version: 3.10.0


Uncaught TypeError: Cannot read property '0' of undefined

Only open file and after try to save or using VIM keys for navigation.
Atom: 1.21.1 x64
Electron: 1.6.15
OS: Mac OS X 10.13
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property '0' of undefined
At /Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/partial-keyup-matcher.js:57

TypeError: Cannot read property '0' of undefined
    at PartialKeyupMatcher.getMatches (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/partial-keyup-matcher.js:42:105)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/keymap-manager.js:375:91)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:100:42)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:3:65)

Commands
     -1:01.8.0 vim-mode-plus:activate-insert-mode (input.hidden-input)
     -1:00.0 vim-mode-plus:activate-normal-mode (input.hidden-input)
     -0:59.8.0 vim-mode-plus:reset-normal-mode (input.hidden-input)
  2x -0:59.5.0 vim-mode-plus:undo (input.hidden-input)
     -0:57.1.0 vim-mode-plus:activate-characterwise-visual-mode (input.hidden-input)
  4x -0:56.6.0 vim-mode-plus:move-right (input.hidden-input)
     -0:55.7.0 vim-mode-plus:delete (input.hidden-input)
     -0:54.7.0 vim-mode-plus:set-register-name (input.hidden-input)
     -0:54.5.0 vim-mode-plus:set-input-char-w (input.hidden-input)
     -0:54 vim-mode-plus:move-to-first-character-of-line-down (input.hidden-input)
     -0:51.6.0 vim-mode-plus-ex-mode:open (input.hidden-input)
     -0:50.5.0 core:confirm (input.hidden-input)
  2x -0:38.8.0 core:close (input.hidden-input)
     -0:35.1.0 vim-mode-plus-ex-mode:open (input.hidden-input)
     -0:34.2.0 core:confirm (input.hidden-input)
     -0:16.6.0 settings-view:open (input.hidden-input)

Non-Core Packages
atom-beautify 0.30.5
atom-django 0.3.2
atom-runner 2.7.1
busy-signal 1.4.3
color-picker 2.2.5
django-templates 0.5.0
emmet 2.4.3
file-icons 2.1.13
git-plus 7.10.0
intentions 1.1.5
linter 2.2.0
linter-flake8 2.2.1
linter-python-pep8 0.2.0
linter-ui-default 1.6.10
Remote-FTP 1.2.6
symbols-tree-view 0.14.0
sync-settings 0.8.3
terminal-fusion 2.4.4
todo-show 2.1.0
vim-mode-plus 1.11.6
vim-mode-plus-ex-mode 0.10.1
wakatime 7.0.3

Thanks for taking the time to contribute!
Though you don't have proton-mode installed, based on the stack trace I think this is a duplicate of https://github.com/atom/atom/issues/15851 (which was tagged as a dupe of https://github.com/dvcrn/proton/issues/286) and is fixed in Atom 1.22, currently in beta.  If you can reproduce in 1.22, please let us know.

We noticed that this is a duplicate of https://github.com/atom/atom/issues/15851. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Feature request : open Emoji keyboard

Hi @paras-28
I see there's an open issue addressing the case you described. https://github.com/flutter/flutter/issues/24153
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you

ok


Test case improvement

Reduces the number of test cases by using the parametrized decorator provided by pytest.
Tests are no longer part of the class TestAlgorithms() as this class is not used anywhere and pytest has no way to pass in the parameter.

Thanks for the PR @ThanosTsiamis!
Could you check why the CI is failing after your changes and address that?

Hey @kPsarakis !
Apologies for the oversight! Forgot to add the pytest package to the requirements.txt file. I hope it works now. If not I'll turn it into a WIP and develop it on my own

@ThanosTsiamis The CI passes now. Is this still WIP, or is it ok to merge?

Hi @kPsarakis.
Please review it at your earliest convenience!
Cheers!


Cannot keep the menu height when working with Bootstrap

$('#top-menu').prmenu({
"height": "50"
});
When working with Bootstrap 3.3.6 together, only the mobile view can keep the menu item height at 50px.

I can confirm that is happening.  I have added a fix in the latest commit.  This corrects the problem on my test pages using Bootstrap.  Let me know if the problem continues.

Yes, the problem fixed after replacing the script with new version.  Thanks a lot!


[CLI]: wandb sync doesn't update summaries

Describe the bug
When W&B crashes during a run and the dashboard stops populating with the run history, I use wandb sync <path> after the run finishes to upload the missing histories. This works, however, the summaries of the run are stuck on the last value that W&B received when the run was still online. This is annoying as I use the summaries (as exported to CSV) to plot the final accuracies of my runs.

wandb sync <path>

Example run with this issue: https://wandb.ai/tudcv/vit_position_embeddings/runs/3bszgqpa
Additional Files
No response
Environment
WandB version: 0.13.4
OS: Linux HPC
Python version: 3.9.12
Additional Context
No response

Hi @rjbruin , happy to help. Could you please expand on this post. What did you mean by the summaries of the run are stuck on the last value? Are you saying that in the run overview page, the Summary isn't updating correctly post sync?

Exactly. For example, the value of epoch gets stuck at something like 15 even though I ran for 200 epochs. Similarly, the value for val/acc in the table reports the value for the 15th epoch, instead of for the final epoch. In the graphs, I can see the values for all the epochs. When I do CSV export, it shows the value from the table (the stuck value) rather than the last value from the graph.

Hi @rjbruin , could you please provide me the entire run folder of a run that wasn't synching completely. I will attempt to reproduce this behavior on my end and review your logs.

Hi @MBakirWB, I've sent the requested info by email!

Hi @rjbruin, I appreciate your patience while we looked into this. I was able to reproduce this issue frequently and have flagged it as a bug. It's now on the engineering teams radar. Once there's been movement or any updates, I'll be sure to let you know.

Excellent! Thanks for following up on this so thoroughly. :)

I'm seeing a similar issue with my runs (I think) - we're running entirely offline, and then when we call wandb sync the summaries for the runs we've synced are empty. This makes it quite difficult to use the web ui to make bar charts, or other plots that rely on the summary metric rather than the logged metrics. Is there any update on this?

I am having similar problems. I run my jobs offline as well and later sync my runs (like the person above me). As a potential workaround, is there a way to add new (key, values) to a completed summary after syncing? If yes, I can at least add certain stats to my summary which will help in comparing runs with different hyperparameters.

Hi @wilrop , the issue is currently in the sdk teams backlog and will be revisited at a later time. You could update the summary metrics using the api, please visit this page in our docs for an example,


refactor: move to react router v7 and react v19 stable

Description
I wanted to move to react router because I have issues with tanstack router, and in the same vein move to react 19 as it is now stable.

[!WARNING]
Please do not delete the sections below

⚠ If you modify backend code, be sure to run these commands :
cd backend
pnpm run openapi # will generate OpenAPI schema at `/openapi/schema.yaml`
pnpm run freeze # will update the `requirements.txt` file if you added new packages

⚠ If you modify frontend code, be sure to run these commands :
pnpm install --frozen-lockfile # Install the packages at the exact version listed in the lockfile
pnpm run format # format the files using biome

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

NpProgress :

https://github.com/tanem/react-nprogress
https://codesandbox.io/p/sandbox/github/tanem/react-nprogress/tree/master/examples/reach-router?file=%2Fsrc%2Findex.tsx


Add missing projects and update some existing ones

cc @caniszczyk @castrojo

@castrojo build fails but I don't know why, I've fixed a few issues since 1st commit like extra : etc - but now it fails due to some strange errors that seem to be unrelated to my PR. Anyway, this needs a review, especially regarding categories/subcategories. Thanks!

@AndreyKozlov1984 can you figure out what's broken here?

I don't think the commented out logo snippets are going to work, the check is looking for actual logos afaict?

I'll check how to fix this

I can't add real logos because there are no logos for those projects.

@castrojo can you track down missing logos, they should be on github.com/cncf/artwork as part of project onboarding

Just an FYI - I added the missing projects here: https://github.com/cncf/landscape/pull/3373

Thanks, I saw & approved.

@caniszczyk @castrojo @AndreyKozlov1984 can you PTAL?
I've updated the PR - removed projects that were added in separate PRs since this PR was open - now it only contains changes needed on top of the current master branch.
Thanks!

Ping...

ok this looks fine to me but I'm still new so hoping for one more review!


Tests README: textual update

... to better reflect the current reality.

coverage: 96.408%. remained the same
when pulling 6db841ef145228c379b4928099131423e08aeb37 on feature/test-docs-minor-update
into 082531d8efec77dcc0fec312749ff87096c9c384 on 1.x.


[DNM] Source compat testing/toolchain building SwiftPM changes

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves #NNNNN, fix apple/llvm-project#MMMMM.

https://github.com/apple/swift-package-manager/pull/7593
@swift-ci please test source compatibility

https://github.com/apple/swift-package-manager/pull/7593
@swift-ci please build toolchain macOS platform

https://github.com/apple/sourcekit-lsp/pull/1361
https://github.com/apple/swift-package-manager/pull/7593
@swift-ci please build toolchain macOS platform

https://github.com/apple/sourcekit-lsp/pull/1361
https://github.com/apple/swift-package-manager/pull/7593
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7771
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7773
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7773
@swift-ci please build toolchain macOS platform

https://github.com/apple/swift-package-manager/pull/7773
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7773
@swift-ci please clean build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7773
@swift-ci please clean build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7773
@swift-ci please build toolchain macOS

https://github.com/swiftlang/swift-package-manager/pull/7773
@swift-ci please build toolchain macOS

https://github.com/swiftlang/swift-evolution/pull/2474
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7620
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7620
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7620
@swift-ci please build toolchain macOS platform

https://github.com/swiftlang/swift-package-manager/pull/7801
@swift-ci please build toolchain

https://github.com/swiftlang/swift-package-manager/pull/7801
@swift-ci please test source compatibility

https://github.com/swiftlang/swift-package-manager/pull/7854
@swift-ci please test source compatibility

https://github.com/swiftlang/swift-package-manager/pull/7854
@swift-ci please build toolchain

https://github.com/swiftlang/swift-package-manager/pull/7882
@swift-ci please test Linux platform

https://github.com/apple/swift-foundation/pull/855
https://github.com/swiftlang/swift-package-manager/pull/7883
@swift-ci please test Linux platform

https://github.com/apple/swift-foundation/pull/855
https://github.com/swiftlang/swift-package-manager/pull/7883
@swift-ci please test Windows platform

https://github.com/apple/swift-foundation/pull/855
https://github.com/swiftlang/swift-package-manager/pull/7883
@swift-ci please test Windows platform

https://github.com/apple/swift-foundation/pull/855
https://github.com/swiftlang/swift-package-manager/pull/7883
@swift-ci please test Windows platform

https://github.com/swiftlang/swift-package-manager/pull/7888
@swift-ci please test

https://github.com/swiftlang/swift-package-manager/pull/7888
@swift-ci please build toolchain

https://github.com/swiftlang/swift-package-manager/pull/7888
@swift-ci please test source compatibility

https://github.com/swiftlang/swift-package-manager/pull/7896
@swift-ci please test

https://github.com/swiftlang/swift-package-manager/pull/7896
@swift-ci please test source compatibility

https://github.com/swiftlang/swift-package-manager/pull/7896
@swift-ci please build toolchain

https://github.com/swiftlang/swift-package-manager/pull/7896
@swift-ci please build toolchain

https://github.com/swiftlang/swift-package-manager/pull/7896
@swift-ci please test

https://github.com/swiftlang/swift-package-manager/pull/7903
@swift-ci please build toolchain macOS platform


Split out Microsoft.Maker.Serial into its own repository

... and included it via git submodule
Created new repository https://github.com/ms-iot/serial-wiring to house Microsoft.Maker.Serial component

@turkycat Please review and test these changes.

I'm not sure this is the best time to extract this stuff, as I have outstanding changes on my fork which haven't been merged back into ms-iot\master yet

How many are we talking, and are you working on Serial? If not, then you can rebase without much, if any, impact. We need this for the VirtualShields work,

👍 Cloned the repo and then ran the git submodule commands to bring in the files. I then verified that I could build the project in Debug and Release mode for all 3 targets. Should we modify the README to mention the submodule with instructions on how to pull it in?

:gem:


OperationQueue addOperation() hangs

I've subclassed Operation class for my own simple operation (API request) and sometimes when adding that operation to OperationQueue it hangs on addOperation() for few seconds. I'm currently iterating thorough objects, for each object create operation and add it to operation queue via addOperation() method.

Hi @fgulan - can you share a bit more information, such as code, or explanation of the dependency graph or any conditions?
The addOperation method in the queue is a little bit involved, but most of it is just about adding some dependencies for conditions and dealing with mutual exclusive conditions. So, would be good to try to vary the scenario to remove any conditions and see if you still have issues. That will help narrow down what is going on.
You could also fire up the Time Profiler to see what is happening?

If you have a lot (and I mean a lot) of conditions, this could cause a slightly delay in adding operations to an OperationQueue. But, at least in all of my tests, this requires an absurdly large number of conditions.

Gonna close this, @fgulan if you are still having issues, please re-open. :)


Fix miio air quality sensor

Description:
Fix a bug in miio air quality sensor
Related issue (if applicable): fixes #28827
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

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

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

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

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @valkjsaaa,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Accepting suggestion part way through keyword doesn't replace rest of keyword

hey @M|ik
...accept suggestion with cursor after M
results in hey @Mikeik

Hi @maxhudson, thanks for your feedback!
Actually, that is expected behavior. The library supports mentions with spaces ("@Max Hudson"), so the most stable flow here is just to replace a string between trigger and cursor position. As result, it should be understandable for the end-user why a mention was added this way and he will take this into account for the future.

I'm actually a bit unclear why this would be expected still.
Say I type @M... then @Mik... then I place the cursor back between @M and ik - I'll get the suggestion for mike, but when I accept it, it only replaces the M, not the ik, so I end up with @Mikeik.
I see why a user might account for this behavior in the future and avoid it, but it's unclear to me how it's a feature.

I see your point. Maybe it will be more clear in your case to use the isInsertSpaceAfterMention property?
So then @M|ik will become @Mike ik.
Anyway, the main idea is always to replace the value between the trigger (@) and the cursor no matter if the cursor at the end of a string or inside.
This behavior is common to a number of messengers (Telegram, Skype).

You're right - appears to be standard behavior. Probably just impossible to detect reliably/causes other issues


Added tests for HealthSeriesBuilder

Tests include full branch coverage for underlying methods of SeriesBuilder and explicit boundary interior coverage for createSeriesPerBuild().

Ich habe jetzt die Tests von Florian Pirchmoser übernommen: https://github.com/jenkinsci/analysis-core-plugin/commit/d54eea4d8cb72f43848ba7424461a11204bfe6d9


fixing socket connection issues

@3rd-Eden any updates?

@ronkorving is this something you can merge and publish for us?


add aligned roi introduced in Detectron2

Description
(Brief description on what this PR is about)
add aligned ROIAlign introduced in https://github.com/pytorch/pytorch/pull/23706
improved MaskRCNN mask acc by 0.2~0.3 mAP. However when training with large batch size, warmup needs to be increased.

@Kh4L

LGTM. Thanks

Hi @Jerryzcn , could you please add an unittest? Thank you!


add keyboard/menu-bar zoom controls

It's a feature I need on my small laptop, where I often zoom in to make text more readable.
Tested on Linux (NixOS) running Electron 8.

Thanks for this! Works great, will land in 1.33.0.


Wrong HINTS of params of function declared with @callback

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.80.0
OS Version: Windows 10 Pro 22H2. OS build 19045.3208

Wrong hints of params of function declared with @callback

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.80.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


How to get parameters of Class Constructor

Is there any way to get the parameters or examples from the constructor of a class?
My jsdoc for the constructor looks as follow:
/**

Constructor for components
@class AmenitiesList
@memberOf comp.model
@param    {object} options overwrite defaults
*/

@wmontgomery this was not possible.  The analyzer was not including the params for the constructor.  This commit fixes this: https://github.com/sutoiku/jsdox/commit/e7477a2ebc6f33e20d823266f0eeb170e10a691a.
now, if you add something like this to class.mustache it will display the parameters.
{{#params}}
**{{name}}**: {{#typesString}}`{{typesString}}`{{/typesString}}{{#description}}, {{{description}}}{{/description}}
{{/params}}

Probably something that should be added to the default template.  @mrjoelkemp what do you think?

@psq Sounds good.


Allow using setServerNames on WebSocket

Currently, you have to use WebSocketFactory#setServerNames for SNI parameters. However, I want to use the factory for different connections to different domains. This requires doing synchronization on the factory only to set the server name:
synchronized (socketFactory) {
    String host = IOUtil.getHost(url);
    // null if the host is undefined, unlikely but we should handle it
    if (host != null)
        socketFactory.setServerName(host);
    else // practically should never happen
        socketFactory.setServerNames(null);
    socket = socketFactory.createSocket(url);
}

I have 3 solutions to this problem with decreasing complexity:

Allow setting the server names on the socket rather than only the factory, this would require a few changes to the handling of the raw socket creation
Allow passing the server names in createSocket to have an idempotent behavior
Add a way to copy the factory, this should be fairly trivial to implement. For instance new WebSocketFactory(otherFactory) or similar. I would be willing to PR this.

@MinnDevelopment Thank you. I'm interested in what your PR will look like 😀 . Please note that I'm a bit picky about beauty of source codes, so PRs that "just work" won't be merged 😅 . My programming style can be found in repositories in github.com/authlete and github.com/TakahikoKawasaki. Finally, I'm sorry I'm busy as a co-founder and programmer of Authlete, Inc., so it may take time for me to respond.

@TakahikoKawasaki I already have something but I haven't gotten around to testing it yet. I will try my best to adhere to the code style.


Use locale passed in arguments

This doesn't change anything since we have an attr_reader in the inherited Gateway class, but just for consistency...

LGTM


Copyedits

Type of PR: Documentation Fix
Description
Applies a number of capitalization and grammatical fixes.
Changes are in separate commits, so if there are any you'd prefer not to include, just let me know and I can quickly revert them.
Why should this be added
Smoother reading of the docs
Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing

Thank you so much! Where have you been my whole life?


fix(nuxt): resolve defu/h3 paths in type templates

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This should fix types when importing directly from #build/app.config and also the declared app config from types/app.config.d.ts.
Related: https://github.com/nuxt/nuxt/issues/23984
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have added tests (if possible).
[ ] I have updated the documentation accordingly.

/trigger release


TypeError: Cannot read property 'indexOf' of undefined

Version
4.0.2
Environment info
Environment Info:

  System:
    OS: macOS Mojave 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 10.16.0 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.11.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 77.0.3865.120
    Firefox: 68.0.1
    Safari: 13.0.2
  npmPackages:
    @vue/babel-preset-app:  3.1.1
    @vue/cli-overlay:  3.9.0
    @vue/cli-plugin-babel: ^3.1.0 => 3.1.1
    @vue/cli-plugin-eslint: ^3.1.0 => 3.11.0
    @vue/cli-service: ^3.8.0 => 3.9.2
    @vue/cli-shared-utils:  3.9.0 (3.11.0)
    @vue/component-compiler-utils:  2.6.0
    @vue/eslint-config-standard:  4.0.0
    @vue/eslint-config-typescript:  4.0.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    babel-helper-vue-jsx-merge-props:  2.0.3
    babel-plugin-transform-vue-jsx:  4.0.1
    eslint-plugin-vue:  5.0.0-beta.5 (4.7.1)
    typescript: ~3.2.4 => 3.2.4 (3.5.3, 3.6.3, 2.5.3)
    vue: ^2.5.17 => 2.6.10
    vue-amap: ^0.5.10 => 0.5.10
    vue-class-component: ^6.0.0 => 6.3.2
    vue-cli-plugin-typescript: ^0.0.1 => 0.0.1
    vue-eslint-parser:  3.3.0 (2.0.3)
    vue-gen-router: ^0.0.5 => 0.0.5
    vue-hot-reload-api:  2.3.1
    vue-loader:  15.7.0
    vue-property-decorator: ^7.0.0 => 7.3.0
    vue-router: ^3.0.1 => 3.0.2
    vue-simple-uploader: ^0.6.0 => 0.6.0
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.5.17 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
    vuedraggable: ^2.17.0 => 2.17.0
    vuex: ^3.0.1 => 3.0.1
  npmGlobalPackages:
    @vue/cli: 4.0.2

Steps to reproduce
npm install -g @vue/cli
vue ui
http://localhost:8000/project/create
Details => Project folder => vue-cli-4.0
Presets => vue-ts =>  TypeError: Cannot read property 'indexOf' of undefined
What is expected?
Normally generated project
What is actually happening?
Unable to generate, always stuck there

Installing CLI plugins. This might take a while...
🚀  Invoking generators...
📦  Installing additional dependencies...
at makeError (/usr/local/lib/node_modules/@vue/cli/node_modules/execa/index.js:174:9)
at Promise.all.then.arr (/usr/local/lib/node_modules/@vue/cli/node_modules/execa/index.js:278:16)
at process._tickCallback (internal/process/next_tick.js:68:7)

code: 1,
stdout:
'⚙  Installing CLI plugins. This might take a while...\n\n🚀  Invoking generators...\n📦  Installing additional dependencies...\n\n',
stderr: null,
failed: true,
signal: null,
cmd:
'vue create vue-cli-4.0 --skipGetStarted --packageManager yarn --inlinePreset {"useConfigFiles":false,"plugins":{"@vue/cli-plugin-babel":{},"@vue/cli-plugin-typescript":{"classComponent":true,"useTsWithBabel":true},"@vue/cli-plugin-eslint":{"config":"prettier","lintOn":["save","commit"]}},"router":true,"routerHistoryMode":false,"vuex":true}',
timedOut: false,
killed: false }
TypeError: Cannot read property 'indexOf' of undefined
at progress.wrap (/usr/local/lib/node_modules/@vue/cli/node_modules/@vue/cli-ui/apollo-server/connectors/projects.js:274:35)
at process._tickCallback (internal/process/next_tick.js:68:7)
TypeError: Cannot read property 'indexOf' of undefined
at progress.wrap (/usr/local/lib/node_modules/@vue/cli/node_modules/@vue/cli-ui/apollo-server/connectors/projects.js:274:35)
at process._tickCallback (internal/process/next_tick.js:68:7)

@yuexing0921 Hello!
I think that because of invalid project name. In some case vue ui doesn't validate the name right.
I've reporoduced this issue vith project name "!_VUE-start". vue ui passed this through, but vue cli said me that this project name is invalid.

use command line vue create myproject, no problem

use CamelCase name for the project and don't use - or _

i try CamelCase proje name but the error continue.
ProjectCreate.vue:659 Error: GraphQL error: Cannot return null for non-nullable field Mutation.projectCreate.
at new t (bundle.esm.js:63)
at Object.next (bundle.esm.js:1004)
at g (Observable.js:135)
at x (Observable.js:179)
at e.value (Observable.js:235)
at bundle.esm.js:866
at Set.forEach ()
at Object.next (bundle.esm.js:866)
at Object.handler (client.js:145)
at e.processReceivedData (client.js:512)

on windows computers caused by wrong prefix path. I changed prefix to "C:\Users\Administrator\AppData\Roaming\npm" and the error has been fixed.

I have  the same issue @Firat-Bayram  what do you mean by changing prefix path

In my case , I didn't install yarn, when I use 'vue create projectName' in command line and it will give me the specified error.

npm prefix -g =>my global path  C:\Users<your user name>\AppData\Roaming\npm
if your path is different , you can change it with the command below
npm config set prefix $value

Version
4.0.2
Environment info
Environment Info:

  System:
    OS: macOS Mojave 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 10.16.0 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.11.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 77.0.3865.120
    Firefox: 68.0.1
    Safari: 13.0.2
  npmPackages:
    @vue/babel-preset-app:  3.1.1
    @vue/cli-overlay:  3.9.0
    @vue/cli-plugin-babel: ^3.1.0 => 3.1.1
    @vue/cli-plugin-eslint: ^3.1.0 => 3.11.0
    @vue/cli-service: ^3.8.0 => 3.9.2
    @vue/cli-shared-utils:  3.9.0 (3.11.0)
    @vue/component-compiler-utils:  2.6.0
    @vue/eslint-config-standard:  4.0.0
    @vue/eslint-config-typescript:  4.0.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    babel-helper-vue-jsx-merge-props:  2.0.3
    babel-plugin-transform-vue-jsx:  4.0.1
    eslint-plugin-vue:  5.0.0-beta.5 (4.7.1)
    typescript: ~3.2.4 => 3.2.4 (3.5.3, 3.6.3, 2.5.3)
    vue: ^2.5.17 => 2.6.10
    vue-amap: ^0.5.10 => 0.5.10
    vue-class-component: ^6.0.0 => 6.3.2
    vue-cli-plugin-typescript: ^0.0.1 => 0.0.1
    vue-eslint-parser:  3.3.0 (2.0.3)
    vue-gen-router: ^0.0.5 => 0.0.5
    vue-hot-reload-api:  2.3.1
    vue-loader:  15.7.0
    vue-property-decorator: ^7.0.0 => 7.3.0
    vue-router: ^3.0.1 => 3.0.2
    vue-simple-uploader: ^0.6.0 => 0.6.0
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.5.17 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
    vuedraggable: ^2.17.0 => 2.17.0
    vuex: ^3.0.1 => 3.0.1
  npmGlobalPackages:
    @vue/cli: 4.0.2

Steps to reproduce
npm install -g @vue/cli
vue ui
http://localhost:8000/project/create
Details => Project folder => vue-cli-4.0
Presets => vue-ts => TypeError: Cannot read property 'indexOf' of undefined
What is expected?
Normally generated project
What is actually happening?
Unable to generate, always stuck there
Installing CLI plugins. This might take a while...
Invoking generators...
Installing additional dependencies...
at makeError (/usr/local/lib/node_modules/@vue/cli/node_modules/execa/index.js:174:9)
at Promise.all.then.arr (/usr/local/lib/node_modules/@vue/cli/node_modules/execa/index.js:278:16)
at process._tickCallback (internal/process/next_tick.js:68:7)

code: 1,
stdout:
' Installing CLI plugins. This might take a while...\n\n Invoking generators...\n Installing additional dependencies...\n\n',
stderr: null,
failed: true,
signal: null,
cmd:
'vue create vue-cli-4.0 --skipGetStarted --packageManager yarn --inlinePreset {"useConfigFiles":false,"plugins":{"@vue/cli-plugin-babel":{},"@vue/cli-plugin-typescript":{"classComponent":true,"useTsWithBabel":true},"@vue/cli-plugin-eslint":{"config":"prettier","lintOn":["save","commit"]}},"router":true,"routerHistoryMode":false,"vuex":true}',
timedOut: false,
killed: false }
TypeError: Cannot read property 'indexOf' of undefined
at progress.wrap (/usr/local/lib/node_modules/@vue/cli/node_modules/@vue/cli-ui/apollo-server/connectors/projects.js:274:35)
at process._tickCallback (internal/process/next_tick.js:68:7)
TypeError: Cannot read property 'indexOf' of undefined
at progress.wrap (/usr/local/lib/node_modules/@vue/cli/node_modules/@vue/cli-ui/apollo-server/connectors/projects.js:274:35)
at process._tickCallback (internal/process/next_tick.js:68:7)

this problem. i think is node version.  please change node version.

npm prefix -g =>my global path C:\Users\AppData\Roaming\npm
if your path is different , you can change it with the command below
npm config set prefix $value

npm prefix -g =>my global path C:\Users\AppData\Roaming\npm
if your path is different , you can change it with the command below
npm config set prefix $value

Tried every solution I found here or StackOverflow nothing worked for me. Found out that if I use Sass/SCSS (with node-sass) it will crush but if I use Sass/SCSS (with dart-sass) it will create a project as expected.

I have the same issue. On what page you can choose Sass/SCSS (with dart-sass) ?


Update to 7.0

@conda-forge-admin, please rerender

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.

@xantares do you still need this version? Because a newer version did succeed


ManagedClient - Args returning from DisconnectedHandler

Describe the feature request

Managed client does not return a useful error when bad password is used, it just return an error code 128
Which project is your feature request related to?

ManagedClient

Describe the solution you'd like
It would be nice to have a new error code with BadUsernameOrPassword which helps to identify this type of common error
Additional context
Add any other context or screenshots about the feature request here.

This is one possible reason:
https://github.com/chkr1011/MQTTnet/issues/1148


[Firefox] No chat replay when connected with account

The chat replay option doesn't work on firefox when I'm signed in, but works when I'm not. I've tried on a profile with no other extensions. and I was not banned from the channel. Everything works on chrome.
In the logs of the console, TypeError: messages.comments is undefined is looping
(I'm on linux I don't know if it's matter)

+1
Same problem, hope you'll can fix it please, your addon is amazing !!

Hi, the chat is fixed in version 0.6 for firefox

Great, you have fixed studio mode too ! Wow Perfect Addon now !! THANKS !


Catalog builds failing

due to https://github.com/crosscite/content-negotiation/issues/104

Fixed with URL workaround in https://github.com/manubot/catalog/commit/9fe185e313cd072ee1541567f5383d27c47b8019


Trouble Understanding Backend Configuration

I am having trouble getting the backend configured for download functionality.  What am I supposed to put for the host and port?

You don't need to change it, the defaults are just fine. In the Spotify app, enter <IP_ADDRESS>:23287 in the hostname field, as shown on the screenshot.

I get this error when trying to download.  I had figured I had the configuration incorrect...

Did you set the beat saber directory correctly?

Yes.  Just double-checked.

Well, then post the .env file here so I can see what's wrong. Also post a screenshot of the settings pop-up in Spotify. Most likely the authentication parameter is wrong.

Text version of .beatsaber.env
(file was renamed so that GitHub would accept it)
Sorry for the delay.

You don't need to change AUTH_USERNAME and AUTH_PASSWORD, leave the defaults. Otherwise it will fail with an authentication error if you don't configure it properly. The username and password are only used locally and don't mean anything.

I'm also getting this when the backend attempts to initialize:

Well, in this case you didn't put the .beatsaber.env file in the .spicetify directory. If the directory doesn't exist, create it and place the file there.

I did, but maybe it's not the correct one.  I have one in the
AppData/Local/spicetify and AppData/Roaming/spicetify directories.  Is
there another?
On Thu, Aug 3, 2023, 04:06 Kuba Szczodrzyński @.***>
wrote:

Well, in this case you didn't put the .beatsaber.env file in the
.spicetify directory. If the directory doesn't exist, create it and place
the file there.
—
Reply to this email directly, view it on GitHub
https://github.com/kuba2k2/spicetify-beat-saber/issues/4#issuecomment-1663484980,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKAHQODPBSKCFFAOCLF5ETXTNLXFANCNFSM6AAAAAA2IIRYUU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes, the directory is called .spicetify (note the dot in front) and is placed in your user folder (one level higher than AppData.

I've just released version 2.1.0, which doesn't require any configuration steps in .env files.
Uninstall the backend and install the new version (2.0.1) first.
Then update the Spicetify extension to 2.1.0.
Then open the settings popup, click the three dots icon and browse to your Beat Saber directory:

I've removed the old backend, and installed the new one.  I've also installed the new plugin version.
I'm setting the Hostname field in the in-app configuration as directed, but now it can't seem to connect to the backend.

It won't let me enter anything in the directory field, probably because of the backend error.

Thanks, this should be fixed in extension v2.1.1 and backend v2.0.2.

I was able to update both.
The UI now shows all is well, but when a download is attempted, the same "Error: Couldn't connect to backend" toast appears.

Is the backend running and showing as connected on the UI? Did you reboot your PC after installing backend?

You might not have enough permissions for the ProgramFiles folder. It's best to install BeatSaber in a different Steam library, such as on C:\ or somewhere else. Otherwise you can assign permissions to the BS directory using the windows "Properties" sheet.

Backend is confirmed (via Process Explorer) to be running, and the UI shows as "Connected: v2.0.2," as shown in the above screenshot.  Permissions shouldn't be an issue, but I tried setting "Everyone" to have Full Control access anyway, just to see if it would change anything.  Unfortunately, no dice.

Open your browser and go to http://localhost:23287/levels/download/1591e1210ddb60bfe5ad2434359246ee7e888c1f (the hash is the level ID, first one I had at hand). Post a screenshot of the output.

Sorry, it's been a busy week.
A text output is displayed, and nothing more:
{"levelDir":"b0b5 (Paranoid - ggdruber)","hash":"1591e1210ddb60bfe5ad2434359246ee7e888c1f","name":"Paranoid","subName":"","authorName":"Black Sabbath","mapperName":"ggdruber","characteristics":{"Standard":["Expert","ExpertPlus"]},"songFilename":"song.egg","coverFilename":"cover.jpg"}

I decided to try it again today.  I remembered that I had switched the queue block on for a while after troubleshooting with it, so I turned the block off and tried to download the next available track in my queue, which so happened to be Wintergatan's "Marble Machine."
Huh.  It downloaded the song with no errors.

Haha, I'm glad that worked. The JSON you posted today would indicate that no errors occur. Maybe it was just a temporary problem.


Fix local transactions in JMS and fix examples

Purpose

Fix local transactions in JMS

Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #17023 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #17023   +/-   ##
=======================================
  Coverage   68.85%   68.85%
=======================================
  Files           5        5
  Lines         122      122
  Branches       21       21
=======================================
  Hits           84       84
  Misses         38       38

Continue to review full report at Codecov.

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


Handle change metric type on-the-fly (without brubeck restart)

Hi
Looks like that current implementation does not handle change
metric type on-the-fly (without restarting brubeck).
This patchset fix this expanding hashtable key by adding space and metric type:
metric_name + ' ' + metric_type
If You may fix this more clearly - it will be perfect, thanks in advance!
More detailed description:

Start brubeck with config:

{
  "sharding" : false,
  "server_name" : "brubeck_debug",
  "dumpfile" : "./brubeck.dump",
  "capacity" : 15,
  "expire" : 10,
  "http" : ":8888",

  "backends" : [
    {
      "type" : "carbon",
      "address" : "localhost",
      "port" : 2003,
      "frequency" : 10
    }
  ],

  "samplers" : [
    {
      "type" : "statsd",
      "address" : "<IP_ADDRESS>",
      "port" : 8126,
      "workers" : 4,
      "multisock" : true,
      "multimsg" : 8
    },
    {
      "type" : "statsd-secure",
      "address" : "<IP_ADDRESS>",
      "port" : 9126,
	  "max_drift" : 3,
	  "hmac_key" : "750c783e6ab0b503eaa86e310a5db738",
	  "replay_len" : 8000
    }
  ]
}

Send metrics as counter type and see network traffic between brubeck
and graphite storage (I use go-carbon):

while true; do (echo "send counter" ; echo "deploy.test.myservice:1|c" \
| socat -t 0 - udp-sendto:<IP_ADDRESS>:8126; sleep 1); done
...
ngrep -d any -q "test" port 2003
...
T <IP_ADDRESS>:53600 -> <IP_ADDRESS>:2003 [AP]
  deploy.test.myservice 10<PHONE_NUMBER>. # valid, we collect sum = 1 * frequency = 10

Change metric type only (counter -> gauge), name stays same,
and see network traffic between brubeck and graphite storage (I use go-carbon),
brubeck continues handle this metric as counter, not as gauge:

while true; do (echo "send gauge" ; echo "deploy.test.myservice:1|g" \
| socat -t 0 - udp-sendto:<IP_ADDRESS>:8126; sleep 1); done
...
ngrep -d any -q "test" port 2003
...
T <IP_ADDRESS>:53600 -> <IP_ADDRESS>:2003 [AP]
  deploy.test.myservice 10<PHONE_NUMBER>. # invalid, must be '1', not '10'

bump


chore(single-spa-angular): add single-spa as dependency

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?
This PR removes single-spa as a peerDependency, and add as a regular dependency for the project.
Issue Number: #188
What is the new behavior?
Single-spa now is included as a dependency
Does this PR introduce a breaking change?
[ ] Yes
[X] No

Other information

The code looks fine to me, but the tests are failing. @arturovt can you comment here?

I have added a check for PopStateEvents that are caused by single-spa as Joel commented in my PR. Which does if (skipNextEvent && event.singleSpa).
We might consider setting >= 5.4 then? Since singleSpa property was added in 5.4.

@joeldenning, @arturovt, should we close this one and get on with #193?

Closing in favor of #193 - i think adding it via schematic is a better appraoch


auth-upgrade : login page do not display

Only LOGIN title is displayed.
[DOM] Found 2 elements with non-unique id #state: (More info: https://goo.gl/9p2vKq) <input type="hidden" name="state" id="state" value="d1b979c62fe54a28bd57f72de745a35b"> <input type="hidden" name="state" id="state" value="d1b979c62fe54a28bd57f72de745a35b">

@bourgeoa can you pls add to the context of the issue: when did this occur? On what actions?

The messages [DOM] Found 2 elements with non-unique id #state can be seen at every login.

Can't reproduce the login page do not display. May have been resolved with latest patch on logout.

The messages [DOM] Found 2 elements with non-unique id #state can be seen at every login.

This comes from the node-solid-server login page views (see https://github.com/solid/node-solid-server/blob/v5.1.6/default-views/auth/auth-hidden-fields.hbs) which might be removed. Depends on resolution of: https://github.com/solid/node-solid-server/issues/1619


Added Error Handling for AppBar & adjusted layout service to not dele…

…te stacks, previous algorithm found this unnecessary, new algorithm needs them.

Closing this PR, as we moved entities to the pbdl package and also changed the name of OrganizationalGroup to BaseGroup (see base_group.dart for more details).


[Editor] Don't create an observer for the stamp annotation after the viewer has been closed

When running tests in PR #18296, I noticed this error:
JavaScript error: http://<IP_ADDRESS>:59398/build/generic/build/pdf.mjs, line 18783: TypeError: can't access property "addEventListener", this._uiManager._signal is null

so this patch should fix it.

/botio integrationtest


feat: migrate to new calldata

Fixes <no issue>
What

implemented new calldata encoding

Why

first step for migration to new genvm

Testing done

python file is taken from genvm, untested here
ts parser is tested to some extent
some manual testing was done

Decisions made

Checks

[x] I have tested this code
[x] I have reviewed my own PR
[ ] I have created an issue for this PR
[x] I have set a descriptive PR title compliant with conventional commits

Reviewing tips

For now there is a problem with "json" input by user for obvious reasons. I can allocate some time to fix them, but I am not great in reactive ui's
User facing release notes
New calldata string representation is slightly different from json:

it has bytes type (encoded in text as b#<hex bytes>)
it has address type (encoded in text as addr#<64 hex digits>
keys can omit "

Changes in general look good. I'm super lost around the encoding part
I have checked this branch and I cannot use the simulator properly, when trying to run write methods I get
Uncaught (in promise) Error: Error writing to contract
    callWriteMethod useContractQueries.ts:220
    handleCallWriteMethod ContractMethodItem.vue:58
    callWithErrorHandling runtime-core.esm-bundler.js:199
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:206
    emit runtime-core.esm-bundler.js:6306
    createSetupContext/get emit/< runtime-core.esm-bundler.js:8016
    0 Btn.vue:46
    callWithErrorHandling runtime-core.esm-bundler.js:199
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:206
    invoker runtime-dom.esm-bundler.js:722

I think the UI it's also broken in some places
Extra
I also want to remark that this PR has big breaking changes that will impact:

GenLayerJS
users upgrading

@AgustinRamiroDiaz Can you please disclose the contract and the method that you are calling to get this error? I've tried different ones and they all succeed.

Actually I found out that probably what we mean by address is 20 bytes and not 32 as in this PR. It is sort of confusing:

account address is 20 bytes
word size (in eth) is 32 bytes, slot addresses in eth are also 32 bytes

Sorry I messed up this PR.... It won't reopen


Special characters

LoginSecurity will strip special characters like ěščřžýááíé from translations.
Applies only to console.

Applies only to console.

 This just sounds like LoginSecurity debug code for loading a different language file.

Yea that debug message seems like a bug.
No idea why it would say that.
it must be parsing messages incorrectly for sure...

This one deserves to be immortalized in history.... https://www.reddit.com/r/ProgrammerHumor/comments/4tc2ka/so_my_friend_accidentally_let_some_debug_messages/

this is brilliant

@Plazmaz thanks for the nice morning gift

@lenis0012 if you're planning on wontfixing, you should probably close the issue


Automated cherry pick of #5258

Cherry pick of #5258 on release-5.22.

#5258: Fix channel header popover for existing channels

/cc  @nevyangelova

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 280eeb589313f3c5773701e8ed3531503f852758


better icon

I am pretty happy with the general vibe of the little tomato snek boi but I threw it together in about 3 minutes in Affinity Designer, someone with more of an æsthetic sensibility could probably kick it up a half a dozen notches easily

When someone designs something new, we'll have to somehow go from an image to an Iconset and thereby to an ICNS, which this handy tiny script can accomplish: https://github.com/retifrav/python-scripts/blob/master/generate-iconset/generate-iconset.py

This is now available via pipx install generate-iconset.

The current icon is growing on me. Closing this until I can come up with some more specific criteria for what 'better' means, at which point there can be a PR or something.


place=square no longer renders

place=square is an unusual tag: it represents something that always has a relatively small, well-defined shape that needs to be connected to other built features like streets and buildings. So unlike most place=* values, it belongs on an area (or a point, as a last resort, if poorly defined).
We added place=square to the tiles and stylesheet for #153, but one of the fixes for #543 resulted in place=* areas getting dropped from the tile schema altogether, with the assumption that they’re redundant to place points (either manually mapped or automatically generated at the centroid). This assumption was only necessary because so many boundaries are incorrectly dual-tagged with place=*.
We need to make an exception for place=square, which never has a boundary or manually mapped centroid. As with other areas like parks, the tiles need to contain both a polygon and an automatically generated centroid point. For now, the priority would be to restore the polygon so that the stylesheet can fill and (suboptimally) label the square based on the polygon. As part of #543, the stylesheet would switch to labeling the square based on its automatically generated centroid, but the fill would remain based on the polygon.
This issue was originally filed as #831, but it seems to have been deleted by mistake.

@1ec5 , I have just enable  place_areas , where is going to show place=square .
https://vtiles.staging.openhistoricalmap.org/#17.05/48.111187/-1.680973

The place_areas could be polygon o relation:
https://www.openhistoricalmap.org/changeset/132406
https://vtiles.staging.openhistoricalmap.org/#16.16/69.985331/-42.348633

Okay if I am understanding this ticket correctly:

need place area labels, created via using the place area polygons (centroid labels don't exist yet)

This is now in map-styles repo, see demo:

https://openhistoricalmap.github.io/mbgl-timeslider/demo/#17.120/48.11178/-1.68019/1850,-4000-2023

place square labels (per above) are in the latest: https://www.openhistoricalmap.org/#map=18/48.11182/-1.68133&layers=O&date=2024-12-31&daterange=1824-01-01,2024-12-31


error in post feed with HTML decode

when the original video title is:
REEPS ONE & BABELI | British Humour

I can use a npm package for fix the title, but I don't know if affect to body content or url too.
any idea? @delgermurun

Ok is fixed with he.decode, I need to update to the last repository version :-)


Textual data represented in 3D

source: https://github.com/opentecture/mindmapping/issues/31

There's a multitude of static text data on the web - goodly portions of which offer greats insights when graphed in 2D or 3D

Story
As a PERSONA
I want to
So I can
Acceptance Criteria
Given
When
Then

@theo-armour - can you give an example? Does this represent work to be done?

no acceptance criteria. #wontfix


Error credservice.go - temporary ban detected

Hello, thank you for awesome tool.
Starting 14-Jul -21  - i got an error indicate banned by hola.
Log server below

Hi!
Is it working though? I see fallback mechanism was fired and endpoint was received.

Maybe we'd want to downgrade the level of the "temporary ban detected" to INFO so we don't confuse people.

Any request will fail with 407 Auth Failed suspicious:
PROXY   : 2021/07/15 10:47:23 handler.go:95: INFO     <IP_ADDRESS>:59105 GET http://2ip.ru/ 407 Auth Failed suspicious

@olikami I spammed the API to trigger a ban on my machine and I could confirm that fallback mechanism stopped working

$ ./hola-proxy -proxy-type lum
MAIN    : 2021/07/15 13:48:18 main.go:147: INFO     hola-proxy client version v1.5.2 is starting...
MAIN    : 2021/07/15 13:48:18 main.go:148: INFO     Constructing fallback DNS upstream...
MAIN    : 2021/07/15 13:48:18 main.go:155: INFO     Initializing configuration provider...
CRED    : 2021/07/15 13:48:18 credservice.go:30: ERROR    Configuration bootstrap error: temporary ban detected. Retrying with the fallback mechanism...
MAIN    : 2021/07/15 13:48:32 main.go:168: INFO     Endpoint: https://zagent1251.hola.org:22225
MAIN    : 2021/07/15 13:48:32 main.go:169: INFO     Starting proxy server...
MAIN    : 2021/07/15 13:48:32 main.go:171: INFO     Init complete.
PROXY   : 2021/07/15 13:48:33 handler.go:104: INFO     Request: <IP_ADDRESS>:40296 HTTP/1.1 GET http://ipinfo.io/
PROXY   : 2021/07/15 13:48:35 handler.go:95: INFO     <IP_ADDRESS>:40296 GET http://ipinfo.io/ 407 Auth Failed suspicious
PROXY   : 2021/07/15 13:48:37 handler.go:104: INFO     Request: <IP_ADDRESS>:40300 HTTP/1.1 GET http://ipinfo.io/
PROXY   : 2021/07/15 13:48:38 handler.go:95: INFO     <IP_ADDRESS>:40300 GET http://ipinfo.io/ 407 Auth Failed suspicious
PROXY   : 2021/07/15 13:48:41 handler.go:104: INFO     Request: <IP_ADDRESS>:40302 HTTP/1.1 CONNECT //ipinfo.io:443
PROXY   : 2021/07/15 13:48:46 handler.go:49: ERROR    Can't satisfy CONNECT request: dial tcp <IP_ADDRESS>:22225: operation was canceled
PROXY   : 2021/07/15 13:48:46 handler.go:104: INFO     Request: <IP_ADDRESS>:40306 HTTP/1.1 CONNECT //ipinfo.io:443
PROXY   : 2021/07/15 13:49:16 handler.go:49: ERROR    Can't satisfy CONNECT request: dial tcp <IP_ADDRESS>:22225: i/o timeout
PROXY   : 2021/07/15 13:50:01 handler.go:104: INFO     Request: <IP_ADDRESS>:40322 HTTP/1.1 CONNECT //ipinfo.io:443
PROXY   : 2021/07/15 13:50:08 handler.go:49: ERROR    Can't satisfy CONNECT request: dial tcp <IP_ADDRESS>:22225: operation was canceled
PROXY   : 2021/07/15 13:50:10 handler.go:104: INFO     Request: <IP_ADDRESS>:40326 HTTP/1.1 GET http://ipinfo.io/

Not much we can do with it. Once your IP got bad reputation, you've three options:

Try to change your home IP.
Use other solution: opera-proxy, windscribe-proxy
Use hola-proxy in conjunction with windscribe-proxy or opera-proxy via hola-proxy's  -proxy option to circumvent IP block. This may be useful if you still need residential IPs (-proxy-type lum) and opera-proxy or windscribe-proxy is not sufficient alone.

@Snawoot Would it be a good idea to disable the fallback mechanism now?

@rany2 I don't think so, it'll stop work in Egypt and other countries with censorship then. Basically fallback proxies introduced by hola exactly for censorship reasons. That fact it helped bypass Hola's per-IP limits for a while was just a nice side-effect.

@Snawoot I thought that the fallback proxies stopped working completely.

@rany2 Usually I've tested it with self-inflicted block adding
<IP_ADDRESS>         client.hola.org

to hosts file. I've tested it right now, it seem to work OK.
[15:19:25] dt1:~/src/hola-proxy> hola-proxy
MAIN    : 2021/07/15 15:19:27 main.go:147: INFO     hola-proxy client version v1.5.1 is starting...
MAIN    : 2021/07/15 15:19:27 main.go:148: INFO     Constructing fallback DNS upstream...
MAIN    : 2021/07/15 15:19:27 main.go:155: INFO     Initializing configuration provider...
CRED    : 2021/07/15 15:19:27 credservice.go:30: ERROR    Configuration bootstrap error: Post "https://client.hola.org/client_cgi/background_init?uuid=8273196d6a2447c5af65e07e30da1348": dial tcp <IP_ADDRESS>:443: connect: connection refused. Retrying with the fallback mechanism...
MAIN    : 2021/07/15 15:19:29 main.go:168: INFO     Endpoint: https://zagent1283.hola.org:22225
MAIN    : 2021/07/15 15:19:29 main.go:169: INFO     Starting proxy server...
MAIN    : 2021/07/15 15:19:29 main.go:171: INFO     Init complete.
PROXY   : 2021/07/15 15:19:37 handler.go:104: INFO     Request: <IP_ADDRESS>:36040 HTTP/1.1 GET http://api.ipify.org/
PROXY   : 2021/07/15 15:19:38 handler.go:95: INFO     <IP_ADDRESS>:36040 GET http://api.ipify.org/ 200 OK

That's surprising... so I guess they fixed their fallback mechanism to prevent block bypass.

Thank you so much for prompt response. I found closed issue about ban detection after open my.
Really appreciate it.
I have an issue too with opera-proxy and  windscribe-proxy - will open issue in their repo.


ConstantFolding: fix wrong constant folding for float-infinity compares

Only if the other operand of an comparison with Inf is a literal we can be sure that it's not Inf or NaN.
Fixes a miscompile
rdar://122605966

@swift-ci test

@swift-ci test

CC: @jkshtj    Looks like #69828 was somewhat over-eager.  It caused float + 0 < infinity to always evaluate true, among other problems.

CC: @jkshtj Looks like #69828 was somewhat over-eager. It caused float + 0 < infinity to always evaluate true, among other problems.

Sorry for the oversight on my part! Thank you for letting me know.


Remove command line option --hpx:run-agas-server

This options is obsolete, it should be removed.

This was fixed by merging #2547


Alt+D shortcut for selecting address bar in Windows

Operation System: Windows 7 Home Premium Service Pack 1
Beaker version: 0.7.11
Alt+D (shortcut) which works for selecting the address bar in most (if not all) browsers is not present in Beaker browser.

We use Cmd/Ctrl+L