primordic/IssueDupesLite huggingface dataset:
Repository: Azure/bicep

Issue #8403: Linting Error BCP270 - Behaviour breaks conditional scopes
Created: 2022-09-14T06:49:37Z
Bicep version
v0.10.61
Describe the bug
bicep cli v0.10.61 introduces BCP270 as a default error rule.

Error BCP270: The scope used for this declaration is ambiguous.

This then breaks the bicep we have here;
resource existing_vnet_cont 'Microsoft.Authorization/roleAssignments@2020-04-01-preview' = {
  name:  guid(user_identity_principalId, networkContributorRole, rbacAssignmentScope=='subnet' ? existingAksSubnetName : existingAksVnetName)
  scope: rbacAssignmentScope=='subnet' ? existingAksSubnet : existingvnet
  properties: {
    roleDefinitionId: networkContributorRole
    principalId: uai.properties.principalId
    principalType: 'ServicePrincipal'
  }
}
To Reproduce
Use a boolean condition in the scope.
Additional context
I'd have much preferred if this linting rule was introduced as Warning instead of Error. Our conditional scope has been set this way for some time, and works fine with ARM.
I'm not sure if I want to table the "lets support conditional scopes" discussion, as I can always turn the linting rule off.... However it's much better suited as a Warning than an Error IMO.

Duplicate issue #8432: 'A resource of module must only reference a single scope' when using ternary operator for scope selection
Created: 2022-09-20T18:21:13Z
Bicep version
Bicep CLI version 0.10.61 (8f44805)
Describe the bug
I would like to have the same template for all subscription scopes and swap in values based on flags in the build. When specifying a scope for a resource, I'd thus like to use a ternary operator to use one subscription scope or another based on another flag.
Given the following sample:
param devSubscriptionId string
param prodSubscriptionId string

param devKeyVaultName string
param prodKeyVaultName string

resource DeploymentKeyVault 'Microsoft.KeyVault/vaults@2021-11-01-preview' existing = {
  name: IsDevTest ? devKeyVaultName : prodKeyVaultName // Works fine, no errors
  scope: IsDevTest ? subscription(devSubscriptionId) : subscription(prodSubscriptionId) // Throws ambiguity error
}
When I do so, however, I receive an error during build (and reflected in the IDE at design time) indicating The scope used for this declaration is ambiguous. A resource or module must only reference a single scope. bicep(BCP270).
Given this is a ternary operator and both results point to a subscription(), there logically would be only a single scope and there's thus nothing ambiguous about this at all.
To Reproduce
See code snippet above.
Additional context
N/A

Closing comment (2022-09-20T23:58:50Z): This looks like a duplicate of #8403. Closing for now, but let me know if I am mistaken.
Repository: Azure/bicep

Issue #498: Support separating array and object items with a comma instead of a newline
Created: 2020-09-16T15:55:03Z
In a lot of languages array items are separated by a comma.
It feels weird to not use comma's for array items.
Current
param sku string {
    default: 'Basic'
    allowed: [
        'Basic'
        'Standard'
        'Premium'
    ] 
}

Proposal
Allow the array items to be split using a comma as it feels more natural.
param sku string {
    default: 'Basic'
    allowed: [
        'Basic',
        'Standard',
        'Premium',
    ] 
}

Duplicate issue #224: line terminating comma error is ambiguous/misleading
Created: 2020-08-14T21:15:46Z
Creating an array and still put commas between array elements (see picture)... the error we throw isn't very accurate.

Closing comment (2020-09-17T00:08:30Z): Related to #498
Repository: Azure/bicep

Issue #4023: Check if resource exists
Created: 2021-08-13T05:40:42Z
feature request
currently creating AKS cluster using Microsoft.MachineLearningServices/workspaces/computes is not idempotent and will error if the link already exists. Currently there is no convenient way to check if the resource already exists and would like to understand the best way to handle this scenario in Bicep
Docs Link: https://docs.microsoft.com/en-us/azure/machine-learning/how-to-create-attach-kubernetes?tabs=python#limitations
Describe the solution you'd like
Convenient way to check if the resource exists and skip certain action ( in this case dont try to establish link) . This could be achieved using a deployment script az cli to see if the resource exists, but looks heavy for a simple check

Duplicate issue #11969: Check for existing
Created: 2023-09-28T06:55:46Z
Hi
When deploying a subscription I need the abillity to check if a subscription with the same name already exists.
Using the existing keyword does not provide the solution right now.
It would be nice, either having existing keyword returning null if resource is not existing or adding the NotFound to the return value.
So something like this:
resource exists 'Microsoft.Subscription/aliases@2021-10-01' existing = {
  name: 'test'
  scope: tenant()
}

// Then either
var resourceNotExists = (exists == null)
// or
var resourceNotExists = (exists.provisionState == 'NotFound')

resource subscriptionAlias 'Microsoft.Subscription/aliases@2021-10-01' = if(resourceNotExists ) {
  scope: tenant()
  name: subscriptionAliasName
  properties: {
    additionalProperties: {
      tags: tags
    }
    workload: workload
    displayName: subscriptionAliasName
    billingScope: billingScope
  }
}
A third option of cource is it to allow for some sort of try catch
/Claus

Closing comment (2023-10-03T07:48:17Z): Duplicates #4023
Repository: Azure/bicep

Issue #3569: Completions not working in an un-terminated object
Created: 2021-07-12T21:19:49Z
Created from this sample: #3510 (comment)
In the following example, we have an unmatched set of closing } braces, which causes a syntax error. Because this causes a syntax error, Bicep is unable to correctly offer property completions (cursor represented by |), and syntax highlighting also shows up incorrectly:
resource test 'Microsoft.Authorization/policyAssignments@2018-05-01' = {
  name: 'asdfsd'
  properties: {
    policyDefinitionId: policy.|
}
Tested with Bicep v0.4.63

Duplicate issue #4558: Misleading error squiggle when missing closing parenthesis
Created: 2021-09-23T10:44:44Z
Bicep version
VS Code 0.4.613
Describe the bug
In the below example, a closing brace is missing at the end of the file, however the error squiggles suggest the problem is with accountName.  There is no problem with accountName - just the file is incomplete.
To Reproduce
param accountName string
resource x 'Microsoft.Storage/storageAccounts@2021-04-01' = {
  name: accountName

Closing comment (2021-09-29T18:44:33Z): Also related to #3569
Repository: Azure/bicep

Issue #2573: Decompiler removes leading underscores from param names 
Created: 2021-05-07T13:09:48Z
Bicep version
1.23.0
Describe the bug
ARM templates associated with Visual Studio deployment projects (*.deployproj) have a couple of variables that point to the artefacts.  These are typically defined like this
 "_artifactsLocation": {
      "type": "string"
    },
    "_artifactsLocationSasToken": {
      "type": "securestring"
    },

When decompiled the leading underscore is removed...
param artifactsLocation string

@secure()
param artifactsLocationSasToken string

This breaks the standard Deploy-AzureResourceGroup.ps1 script.

Duplicate issue #7332: decompile should not remove underscores from parameter names
Created: 2022-06-22T22:50:27Z
decompile this:

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "_artifactsLocation": {
            "type": "string"
        },
        "_artifactsLocationSasToken": {
            "type": "securestring"
        }
    },
    "resources": [
    ],
    "outputs": {
    }
}

you get:

param artifactsLocation string
@secure()
param artifactsLocationSasToken string
EXPECTED:
param _artifactsLocation string
@secure()
param _artifactsLocationSasToken string
Those exact parameter names are expected by some tools including Deploy-AzTemplate.ps1 (which I think is still valid in the bicep world, waiting on @bmoore-msft for verification)

Closing comment (2022-06-23T03:51:00Z): Duplicate of #2573
Repository: Azure/bicep

Issue #1895: Provide Azure Built-In role constants
Created: 2021-03-16T12:25:43Z
Is your feature request related to a problem? Please describe.
Currently, to deploy a azure role assignment, the UUID of the role definition must be hard coded and/or provided as a parameter. This is a pain.
See https://github.com/Azure/bicep/blob/main/docs/examples/101/create-managedidentity-rbac/main.bicep for an example.
Describe the solution you'd like
Bicep is in a position to provide access to well-known constant values.
Syntax proposal 1: Introduce a new global variable that is loaded by default. Then you could access the roleDefinitionId like:
subscriptionResourceId('Microsoft.Authorization/roleDefinitions', WellKnownConstants.BuiltinRoles.StorageBlobDataContributor)

This has the advantage of (presumably) being easier to implement and has the advantage of only being one value in the namespace if there are other well-known constants that might be added in the future. Technically I suppose this would be a breaking change though.
Syntax proposal 2: The other option would be a new function for this specific case:
builtiInRoleDefinitionId('Storage Blob Data Contributor')

This is also a breaking change but is slightly simpler easier to use. It could also have an optional argument for targeting other scopes.
Downsides
Providing this information means that bicep must have some source of truth which would need to be vended with it (in which case it could become stale) or added as a new dependency. Also, it is not clear to me if the well known role definition ids are constant between different Azure clouds.
Regardless of the ergonomics this would essentially be adding resource-specific support into the bicep language, which as far as I can tell so far is relatively resource agnostic (or at least as much as ARM templates themselves are). Adding stuff like this starts to get into the "standard library" territory, which bicep might be trying to avoid.
This seems bite sized enough that if it's a desirable feature I'm actually considering implementing it myself and sending a PR, but I wanted to start a discussion first.

Duplicate issue #13427: Extend environment() function to expose Azure RBAC roles
Created: 2024-02-23T12:08:10Z
Is your feature request related to a problem? Please describe.
Feature reaquest.
Describe the solution you'd like
I would like to be able to fetch rbac role Ids using a function. Example usage:
Instead of:
@description('List of all Azure RBAC roles')
import {
  Roles
} from 'roletypes.bicep'

...

roleDefinitionIds: [
  Roles.Owner
]
I would like to:
roleDefinitionIds: [
  environment().roles.Owner
]

Closing comment (2024-02-26T14:59:32Z): Closing as duplicate of #1895
Repository: AzureAD/microsoft-authentication-library-for-dotnet

Issue #2181: Release WAM on .NET classic
Created: 2020-11-12T11:13:38Z
https://aka.ms/msal-net-wam
Known issues:
WAM with console apps #2196
WAM with MSA-passthrough #2126

Duplicate issue #2125: [Feature Request] WAM support on .NET Core for console WinForms WPF etc.
Created: 2020-10-20T18:00:42Z
This requires taking a dependecy on Windows Runtime, which is undesirable for Confidential Client

Closing comment (2020-11-17T15:07:39Z): Duplicate of #2181
Repository: AzureAD/microsoft-authentication-library-for-dotnet

Issue #2607: [Bug] Authorization code is truncated causing error AADB2C90090: The provided JWE is not a valid 5 segment token.
Created: 2021-05-06T14:07:34Z
Which Version of MSAL are you using ?
4.30.1
Platform
.NET Framework 4.7.2
What authentication flow has the issue?
Desktop / Mobile
Interactive
Is this a new or existing app?
An existing app with a new implementation of B2C.
Repro

Create a custom B2C policy that enriches the JWT with application-specific claims.
Acquire a token via AcquireTokenInteractive with the nativeclient redirect uri.
The redirect uri + authorization code exceed 2084 characters.
The code at WindowsFormsWebAuthenticationDialogBase can only read the truncated code instead of the full authorization code.
When exchanging the authorization code for a token the application throws the titular exception.

Expected behavior
A large set of claims should not cause an exception to occur.
Actual behavior
The authorization code gets truncated whenever the claims cause the authorization code to exceed a certain size.
Additional context/ Logs / Screenshots
AAD90090_Logging.txt
This issue is very similar to #2515 so it could be that this is a duplicate.

Duplicate issue #2749: B2C login with federated identity is broken in 4.33
Created: 2021-07-07T09:08:31Z
Logs and network traces
Since version 4.33.0 I can not login anymore with federated identity in B2C. Login with username password is still working. The following errors occurs:
AADB2C90090: The provided JWE is not a valid 5 segment token. Correlation ID: b0e306ce-96f0-4c1f-a9a8-2dc0fc5b6dc2
or
AADB2C90090: The provided JWE contains a field that is not base64 compliant.
Correlation ID: 41e39615-4c52-4dea-939c-0e5e308fd24e
or
AADB2C90085: The service has encountered an internal error. Please reauthenticate and try again.
Correlation ID: e4251fe0-c946-4d68-b008-fd3e5a74748b
Which version of MSAL.NET are you using?
MSAL.NET 4.33.0, it works in 4.32.1
Platform
.net framework 4.7 windows forms application
What authentication flow has the issue?

Desktop / Mobile

 Interactive
 Integrated Windows Authentication
 Username Password
 Device code flow (browserless)


Web app

 Authorization code
 On-Behalf-Of


Daemon app

 Service to Service calls



Is this a new or existing app?
The app is in production, I haven't upgraded MSAL, but started seeing this issue.
Repro
  app = PublicClientApplicationBuilder.Create(ClientId).WithParentActivityOrWindow(() => owner).WithB2CAuthority(SignInAuthority).WithDefaultRedirectUri().Build();

await app.AcquireTokenInteractive(scopes).ExecuteAsync();
Expected behavior
Can login with username/password and federated identities
Actual behavior
It throws MsalException in case of login with federated id.

Closing comment (2021-07-07T09:58:12Z): Probably a duplicate of #2607
cc: @jennyf19 FYI
Interestingly this would be a regression
Repository: AzureAD/microsoft-authentication-library-for-dotnet

Issue #2696: RemoveAsync(Account) doesn't remove account from cache
Created: 2021-06-10T22:20:14Z
I am using WAM with msal.net cache
The authority is https://login.windows.net
The GetAccountsAsync call returns the single operating system account. After that no matter how many times, the removeAsync(account) method is called, I am unable to remove OS account from cache.

Duplicate issue #3566: [Bug] RemoveAsync doesn't always work if PublicClientApplicationBuilder is using broker
Created: 2022-08-05T17:46:18Z
Which version of MSAL.NET are you using?
MSAL.NET 4.46.0
Platform
.NET 6
What authentication flow has the issue?

Desktop / Mobile

 Interactive
 Integrated Windows Authentication
 Username Password
 Device code flow (browserless)


Web app

 Authorization code
 On-Behalf-Of


Daemon app

 Service to Service calls



Is this a new or existing app?
This is a new app or experiment.
Repro
Trying to use the method described here:
https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-net-clear-token-cache
results in an infinite loop if there is an account the PublicClientApplicationBuilder was created using the WithBroker() method.
            _app = PublicClientApplicationBuilder
                .Create(ClientId)
                .WithBroker()
...
            authenticationResult = await _app.AcquireTokenInteractive(scopes).ExecuteAsync();
...

            accounts = (await _app.GetAccountsAsync()).ToList();

            // clear the cache
            while (accounts.Any())
            {
                await _app.RemoveAsync(accounts.First());
                accounts = (await _app.GetAccountsAsync()).ToList();
            }
Expected behavior
No infinite loop, and cache is actually cleared, or at least a workaround for the broker scenario that actually clears the cache.
Actual behavior
Infinite loop or cache is not properly cleared.
Possible solution
No idea. I've tried creating another PublicClientApplicationBuilder without the broker and then looping through the accounts to delete them, but using the broker will keep that account as if was not deleted, so the cache is not really cleared.

Closing comment (2022-08-05T18:20:39Z): I did have ListWindowsWorkAndSchoolAccounts set to on, but I've tried to turn it off and it still doesn't work, and yes, the specific account that won't go away is a "*.onmicrosoft.com" (work account) account, which is on the "Accounts by other apps" settings, so yes, this seems similar to #2696.
Wouldn't it make sense for the broker not force those accounts if I want to specifically remove them? It should have a copy of those accounts in the cache that I've specified.
The problem I'm facing is that this behavior is keeping me from being able to completely sign the user of my app. The documentation for GetAccountsAsync says: "Returns all the available accounts in the user token cache for the application.", so I was assuming that this cache was specifically for my app, not the cache of all the users in the OS. Even if I delete my MsalCacheHelper file, the user is still there.
Repository: AzureAD/microsoft-authentication-library-for-dotnet

Issue #1361: [Feature Request] Android shared_prefs should not be used with plain text.
Created: 2019-08-28T06:39:22Z
Is your feature request related to a problem? Please describe.
Android app security is compromised by storing access and refresh token in SharedPreferences as plain text documents.
Describe the solution you'd like
Tokens should be encrypted like in example github Secure Preferences
Describe alternatives you've considered
Tokens should not be stored in SharedPreferences, instead there could be used more secure place such as AccountManager.
Additional context
Tokens are now stored in:
/data/data/<package_name>/shared_prefs
com.microsoft.identity.client.accessToken.xml
com.microsoft.identity.client.refreshToken.xml

Duplicate issue #1544: [Feature Request] Encrypt token cache in shared preferences on Xamarin.Android when the OS enables it
Created: 2019-12-13T17:09:09Z
Is your feature request related to a problem? Please describe.
Enable encryption at rest for the token cache to make more difficult for an adversary to use the data stored in the cache for malicious purposes.
Note: MSAL.Android native encrypts the token cache when possible on Android devices.
Notes on the security aspect:

Adding encryption at rest is categorized as Defense in depth.
Shared preferences on Android are meant to be only visible to the application (or application group) that creates them, however in practice on rooted devices, these values are easy to read.

Closing comment (2024-05-20T16:20:33Z): Duplicate of #1361
Repository: AzureAD/microsoft-authentication-library-for-dotnet

Issue #3301: [Bug] WAM broker does not honor LoginHint 
Created: 2022-05-04T00:21:28Z
MSAL 4.46

Use WAM preview
Declare that the app is MSA-PT, i.e. only AAD plugin should handle auth
AcquireTokenInteractive using a login_hint

Actual: the full account picker pops up every time

Expected - a better interactive login experience, at the very least the Account Picker should not be invoked and instead the AAD plugin's browser should accelerate the authentication, e.g. Note that if account is part of the OS, the AAD plugin seems to be able to give back token silently.

Tracking ADO issue: https://identitydivision.visualstudio.com/Engineering/_workitems/edit/2040431
Note: when implementing a fix, please see #3520 as well for internal API details

Duplicate issue #3709: [Bug] Suppress account control when login_hint is present
Created: 2022-09-27T21:19:07Z
Related Bug Bug 2040431: Even with login_hint specified, MsalRuntime always shows the account picker
The related bug is tracking a fix on MSALruntime, this issue is to adopt to the fix when msalruntime fixes the related issue.

Closing comment (2022-09-29T12:34:36Z): Duplicate of #3301
Repository: AzureAD/microsoft-authentication-library-for-dotnet

Issue #670: CI tool warns about breaking changes in the public API
Created: 2018-11-02T17:53:02Z
Is your feature request related to a problem? Please describe.
We want to know when there are API breaking changes
Describe the solution you'd like
Identity Model Extensions for .NET have a tool to do that

CI tool breaks the CI build when the PR proposes a breaking change in the public API
CI tool issues a warning when the PR proposes a (non-breaking) change in the public API

Duplicate issue #1003: Fundamentals: Add API compat to build definitions
Created: 2019-03-22T23:52:54Z
Add api compat task to build definitions to unintended catch api changes

Closing comment (2020-01-30T19:22:47Z): duplicate of #670
Repository: AzureAD/microsoft-authentication-library-for-dotnet

Issue #4091: [Bug] Build failure. Invalid iOS version
Created: 2023-04-18T07:40:56Z
Logs and network traces
Without logs or traces, it is unlikely that the team can investigate your issue. Capturing logs and network traces is described in Logging wiki.
Which version of MSAL.NET are you using?

4.53.0
Platform

net7.0-ios
Repro
https://github.com/VladislavAntonyuk/MauiSamples/tree/main/Auth/MauiAuth
Expected behavior
No build issue.
Actual behavior
Error	CS1705	Assembly 'Microsoft.Identity.Client' with identity 'Microsoft.Identity.Client, Version=4.53.0.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae' uses 'Microsoft.iOS, Version=16.4.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065' which has a higher version than referenced assembly 'Microsoft.iOS' with identity 'Microsoft.iOS, Version=16.2.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065'
Possible solution
Downgrade to 4.52.0
Additional context / logs / screenshots / links to code
The latest available version of iOS Sdk is 16.2: https://github.com/xamarin/xamarin-macios/blob/main/DOWNLOADS.md

Duplicate issue #4120: Latest MSAL version is not compatible with current maui SDK 
Created: 2023-05-07T14:57:56Z
When using the current version of MSAL I get the following error when building:
CSC : error CS1705: Assembly 'Microsoft.Identity.Client' with identity 'Microsoft.Identity.Client, Version=4.53.0.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae' uses 'Microsoft.iOS, Version=16.4.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065' which has a higher version than referenced assembly 'Microsoft.iOS' with identity 'Microsoft.iOS, Version=16.2.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065
This is true for both the current VS production version 17.5.5 and the pre-release version 17.6.0 preview 6

Closing comment (2023-05-09T05:46:45Z): This is tracked in #4091. Fix is merged and will come in the next release; aiming for the end of the week.
Repository: Benjamin-Dobell/Heimdall

Issue #413: ERROR: Protocol initialisation failed!
Created: 2017-08-23T16:53:36Z
Have been trying for 3 hours to flash TWRP to a SMA500FU, and I don't know if it's a problem with the fact it's an A5, or if it's the build I'm using or what?
Here's the output of detect, and download-pit.
aliensonneptune@tinfoilhats:/$ sudo heimdall detect
Device detected
aliensonneptune@tinfoilhats:/$ sudo heimdall download-pit --output pit.pit
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
ERROR: Protocol initialisation failed!

Releasing device interface...

aliensonneptune@tinfoilhats:/$ 
Can anyone help me?
PS, I'm an android noob, only been using it for 4 weeks.
PPS, I'm on a USB3, and the phone is on the 6.0.1 UD.

Duplicate issue #529: Samsung SM-A736B/DS - ERROR: Failed to send handshake!
Created: 2023-07-26T16:37:59Z
Hello,
I am using heimdall v.1.42 and still getting this error.  I used the code from github to build it but it still doesn't work

Closing comment (2024-05-25T20:57:19Z): Duplicate of #413? I just added some help there.
Repository: Benjamin-Dobell/Heimdall

Issue #413: ERROR: Protocol initialisation failed!
Created: 2017-08-23T16:53:36Z
Have been trying for 3 hours to flash TWRP to a SMA500FU, and I don't know if it's a problem with the fact it's an A5, or if it's the build I'm using or what?
Here's the output of detect, and download-pit.
aliensonneptune@tinfoilhats:/$ sudo heimdall detect
Device detected
aliensonneptune@tinfoilhats:/$ sudo heimdall download-pit --output pit.pit
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
ERROR: Protocol initialisation failed!

Releasing device interface...

aliensonneptune@tinfoilhats:/$ 
Can anyone help me?
PS, I'm an android noob, only been using it for 4 weeks.
PPS, I'm on a USB3, and the phone is on the 6.0.1 UD.

Duplicate issue #541: Error initializing protocol
Created: 2024-05-11T01:45:15Z
Attempting to setup an old galaxy s9 with lineage. Heimdall doesn't explicitly support it, but Lineage has a dedicated guide, so I assume it does work. Receiving this error when running heimdall print-pit, still plugged in, all drivers installed, everything. Zadig even says it installs successfully, but the phone never leaves download mode. Any help appreciated, first time installing a custom android distro.
`PS C:\Users\baylo> heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
libusb: error [init_device] device '\.\USB#VID_0C45&PID_636B&MI_02#7&315A9F63&0&0002' is no longer connected!
libusb: error [init_device] device '\.\USB#VID_046D&PID_C08B&MI_01#7&5A22FA0&0&0001' is no longer connected!
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Unexpected handshake response!
ERROR: Protocol initialisation failed!
Releasing device interface...`
Edit: idk why it refuses to acknowledge that section as code despite the syntax, but I think it's pretty clear where the response is.

Closing comment (2024-05-25T20:57:28Z): Duplicate of #413? I just added some help there.
Repository: Benjamin-Dobell/Heimdall

Issue #291: Installation fails on OS X 10.11 (El Capitan)
Created: 2015-09-26T13:27:40Z
Edit by @Benjamin-Dobell:

TLDR: Use https://bitbucket.org/benjamin_dobell/heimdall/downloads/Heimdall-1.4.1-Unofficial-Signed.dmg

...
First i got this warning message when i tried to install it.

But i continue anyway, which got me this:

Let me know if you need more info.

Duplicate issue #317: OSX El Capitan Unsupported
Created: 2015-12-10T00:04:13Z
Please expand the .dmg / .pkg to function on OSX 10.11.1 -- El Capitan. Thanks

Closing comment (2015-12-13T02:25:25Z): Duplicate of #291?
Repository: Benjamin-Dobell/Heimdall

Issue #23: make install should not touch the udev service
Created: 2011-10-03T03:44:04Z
It's not usual for 'make install' to touch system services. Could you please change this to just print that the user should run 'udevadm trigger reload-rules' as root? The only way for your build system to work is to be run as root, and that's not safe practice anyhow. It's also a headache for anyone trying package this.

Duplicate issue #24: Errors whilst compiling heimdall
Created: 2011-10-03T08:49:43Z
I just tried compiling heimdall on openSUSE 11.4 and got the following errors.
sudo make install
make[1]: Entering directory /Galaxy_S2_Flashing/Heimdall/Heimdall-1.3.1/heimdall' test -z "/usr/local/bin" || /bin/mkdir -p "/usr/local/bin" /bin/sh ./libtool   --mode=install /usr/bin/install -c heimdall '/usr/local/bin' libtool: install: /usr/bin/install -c heimdall /usr/local/bin/heimdall test -z "/lib/udev/rules.d" || /bin/mkdir -p "/lib/udev/rules.d" /usr/bin/install -c -m 644 60-heimdall-galaxy-s.rules '/lib/udev/rules.d' make  install-data-hook make[2]: Entering directory/Galaxy_S2_Flashing/Heimdall/Heimdall-1.3.1/heimdall'
sudo service udev restart
service: no such service udev
make[2]: *** [install-data-hook] Error 1
make[2]: Leaving directory /Galaxy_S2_Flashing/Heimdall/Heimdall-1.3.1/heimdall' make[1]: *** [install-data-am] Error 2 make[1]: Leaving directory/Galaxy_S2_Flashing/Heimdall/Heimdall-1.3.1/heimdall'
make: *** [install-am] Error 2
Any clue why this is happening? I previously managed to install heimdall 1.3.0 but wanted to update to 1.3.1.

Closing comment (2012-07-03T17:52:56Z): This bug is closely related to #23 and would be solved when the other one is appropriately closed.
Repository: Benjamin-Dobell/Heimdall

Issue #413: ERROR: Protocol initialisation failed!
Created: 2017-08-23T16:53:36Z
Have been trying for 3 hours to flash TWRP to a SMA500FU, and I don't know if it's a problem with the fact it's an A5, or if it's the build I'm using or what?
Here's the output of detect, and download-pit.
aliensonneptune@tinfoilhats:/$ sudo heimdall detect
Device detected
aliensonneptune@tinfoilhats:/$ sudo heimdall download-pit --output pit.pit
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
ERROR: Protocol initialisation failed!

Releasing device interface...

aliensonneptune@tinfoilhats:/$ 
Can anyone help me?
PS, I'm an android noob, only been using it for 4 weeks.
PPS, I'm on a USB3, and the phone is on the 6.0.1 UD.

Duplicate issue #491: Samsung SM-G998B - ERROR: Failed to send handshake!
Created: 2021-08-25T08:22:43Z
So I cannot even print-pit currently on this device, is it even supported?
Currently output is:
`sudo heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
`

Closing comment (2024-05-25T20:33:33Z): Duplicate of #413? I just added some help there.
Repository: BlackArch/blackarch

Issue #1618: Failed to start Login Service -> boot after install
Created: 2017-04-27T12:32:29Z
systemctl status systems-logind.service for details
this is after new install off ISO
how do I access systemctl for more info to rectify?
I had the same issue w. Failed to start logon service when I created a virtual machine.

Duplicate issue #1818: Stuck while installing
Created: 2017-11-22T14:30:36Z
I was installing blackarch using vmware work station but when i reached Dumping data from Live ISO ,
It was stuck at Installing /usr, please wait....
Waited for more than 30min .. but it still there .

Closing comment (2018-03-06T13:43:38Z): Closing this as duplicate of #1618.
Repository: BlackArch/blackarch

Issue #2465: Gobuster not receiving update to v3
Created: 2019-09-09T08:36:32Z
I have searched open and closed issues for duplicates
 I am submitting a bug report for existing functionality that does not work as intended


Bug description
Gobuster package still getting version v2.0.1 instead of v3 as gobuster repo update.
Steps to reproduce

pacman -Syu
pacman -S gobuster

Actual result: Describe here what happens after you run the steps above (i.e. the buggy behaviour)
↳ pacman -Q --info gobuster
Name            : gobuster
Version         : 1:281.f7ed22d-1
Description     : Directory/file & DNS busting tool written in Go.
Architecture    : x86_64
URL             : https://github.com/OJ/gobuster
Licenses        : APACHE
Groups          : blackarch  blackarch-webapp  blackarch-scanner
Provides        : None
Depends On      : glibc
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 5.28 MiB
Packager        : Levon Kayan <noptrix@nullsecurity.net>
Build Date      : Thu 25 Jul 2019 05:59:49 PM WIB
Install Date    : Mon 09 Sep 2019 03:27:54 PM WIB
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

↳ gobuster -w directory-list-2.3-medium.txt -u http://example.com/ -x php -fw

=====================================================
Gobuster v2.0.1              OJ Reeves (@TheColonial)

Expected result: Describe here what should happen after you run the steps above (i.e. what would be the correct behaviour)
gobuster dir -u https://buffered.io -w ~/wordlists/shortlist.txt -l

===============================================================
Gobuster v3.0.1
by OJ Reeves (@TheColonial) & Christian Mehlmauer (@_FireFart_)
===============================================================

Screenshots

Info for developers

Device: Manufacturer Model XVI (Only if you consideer needed, for example, network cards)
GNU/Linux distribution: Archlinux with BlackArch Repo
Tool version: 2.0.1

Duplicate issue #2456: Chisel not displaying its version
Created: 2019-09-03T16:14:51Z
@noptrix go expert, for chisel you simply build it like that

  
    
      blackarch/packages/chisel/PKGBUILD
    
    
         Line 34
      in
      d8c997b
    
  
  
    

        
          
           go build 
        
    
  


For example in the docker it is built like that
https://github.com/jpillora/chisel/blob/f3a8df20e389ce41cd49101408231c67c093f5af/Dockerfile#L9-L12
I think a flag is missing and so the version is displayed as 0.0.0-src.

Closing comment (2019-10-02T23:10:39Z): seems to be related to #2465
That's happening with all go tools
Repository: BlackArch/blackarch

Issue #4018: Error signature during a BlackArch update.
Created: 2023-12-02T23:53:53Z
I encountered an error during a BlackArch update, and I can't find the solution:
sudo pacman -Syu
error: blackarch: signature from 'Levon 'noptrix' Kayan (BlackArch Developer) noptrix@nullsecurity.net' is unknown trust
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
blackarch                               4.0 MiB  1228 KiB/s 00:03 [####################################] 100%
error: blackarch: signature from 'Levon 'noptrix' Kayan (BlackArch Developer) noptrix@nullsecurity.net' is unknown trust
error: failed to synchronize all databases (invalid or corrupted database
If someone can help me, thank you.

Duplicate issue #4027: error: blackarch: signature from "Levon 'noptrix' Kayan (BlackArch Developer) <noptrix@mullsecurity.net>" is unknown trust
Created: 2023-12-07T16:49:07Z
error: blackarch: signature from "Levon 'noptrix' Kayan (BlackArch Developer) noptrix@mullsecurity.net" is unknown trust error: database 'blackarch' is not valid (invalid or corrupted database (PGP signature))
I've been trying to fix it since yesterday and I don't know how to do it, I've followed all the other solutions and it still doesn't work (I'm installing arch linux from 0 for the first time :)).

Closing comment (2023-12-07T19:11:07Z): You are required to make sure you are not submitting a duplicate issue. Before you opened this issue, you would have noticed the 3rd open issue is the same as this.
I have posted a temporary solution in it, please follow it, I am closing this issue.
Duplicate of #4018
Repository: BlackArch/blackarch

Issue #2835: Login issues
Created: 2020-08-23T17:50:29Z
Type: Discussion
Discussion
On 22 Aug 2020
i had a problem (im not sure if it was my faults or a bug).
Just after update (pacman -Syu) and reboot, i cant login back.
lxdm (is it lxdm or else? The default that came with it) will just react as i type the wrong password.
enter user => enter pass => ask for username again
On tty, theres a "login incorrect" messages after key in the password and before it refresh to ask for username again.
I tried to troubleshoot it by using a live arch and change the password but no different.
ssh also react as if i give it a wrong password.
Tried reinstall the kernel(pacman -Sy linux linux-firmware linux-headers) (maybe it'll help) with no luck.
have tried reinstall pam and pambase too.
Oh and this is the second time happened to me.
The first one is on a different machine with headless setup.
And i just reinstall everything as i thought i did something wrong.
just a morning after, this happened to my main laptop.
If someone knows the solution to this or someone facing the same problem, please let me know.
So that i dont have to blame myself. :D
Edit: Solution is here.

Duplicate issue #2837: I have blackarch install on my laptop after booting today morning I am having problem login. Whenever I enter the credentials it goes to login loop. i have an extra user other than root. I have tried with every WMs and every credentials. I updated my system yesterday. Need Help ASAP!!!!!!!!!!!!!!
Created: 2020-08-26T09:46:37Z
I have blackarch install on my laptop after booting today morning I am having problem login. Whenever I enter the credentials it goes to login loop. i have an extra user other than root. I have tried with every WMs and every credentials. I updated my system yesterday. Need Help ASAP!!!!!!!!!!!!!!
Originally posted by @samspei0l in #1820 (comment)

Closing comment (2020-08-26T10:21:47Z): As I said before, this is most likely related to #2835. Did you try the things recommended there?
I am going to close this for now as duplicate. If it is not related to the issue, feel free to reopen this issue.
Repository: BlackArch/blackarch

Issue #36: Add [bully].
Created: 2013-08-12T23:39:57Z
This tool was suggested by a BlackArch user.

Duplicate issue #137: Add [bully].
Created: 2013-08-19T01:40:06Z
This tool was suggested by a BlackArch user.

Closing comment (2013-08-19T01:43:11Z): Duplicate of #36.
Repository: BlackArch/blackarch

Issue #2562: [Tool request] Osmedeus
Created: 2019-12-12T17:14:58Z
Tool that allows you to automate reconnaissance and vulnerability scanning against targets.
https://github.com/j3ssie/Osmedeus

Duplicate issue #3626: Osmedeus | https://github.com/j3ssie/osmedeus.git | Osmedeus Workflow Engine for Offensive Security.
Created: 2022-12-08T11:34:45Z
**⠀⠀⠀⠀⢀⠠⢂⣍⣡⠒⣄⠢⢅⡂⢀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⣀⠵⠞⠛⢻⣿⣿⣷⣯⣒⡌⣒⠱⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠐⠁⠀⠀⠀⠀⠛⠿⣿⣿⣿⡷⣌⢣⠖⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⣰⣿⣿⣿⣿⡜⢦⣛⠀⠀⢀⡠⢄⡰⣆⢤⡄⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⢻⣿⣿⣿⠷⣝⠶⣩⠡⣌⡗⢮⣧⣿⣾⣷⣾⣿⣧⢄⠀
⠀⠀⠀⠀⠀⠀⠀⢀⣤⣿⣿⣿⢯⡟⣼⢫⣿⡹⣎⣻⣿⣿⡿⣿⠿⠃⠀⠈⠙⢧
⠀⠀⠀⠀⠀⠀⠀⣿⣿⣿⣿⡿⣏⡾⣵⢛⡶⣻⣍⣿⣿⣿⣿⠀⠀⠀⠀⠀⠀⠈
⠀⠀⠀⠀⠀⠀⢠⣿⣿⣿⡿⣝⣞⡳⠀⢸⣽⣳⢧⣿⣿⣿⡛⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⣠⣶⣿⣿⣿⣿⣻⡽⡾⠁⠀⠀⢷⣯⢿⣽⣿⣿⣿⣷⡄⠀⠀⠀⠀⠀
⠀⠀⠀⠀⣿⣿⣿⣿⣿⢷⣻⡝⠁⠀⠀⠀⠈⢫⣿⢾⣿⣿⣿⣿⣟⠀⠀⠀⠀⠀
⠀⠀⠀⣰⣿⣿⣿⣿⣟⣿⡟⠀⠀⠀⠀⠀⠀⠀⢻⣿⣾⣿⣿⣿⣿⣆⠀⠀⠀⠀
⠀⢠⣿⣿⣿⣿⣿⣿⣯⠏⠀⢀⣤⣶⣶⣦⣤⡀⠀⢻⣿⣿⣿⣿⣿⣿⣷⡄⠀⠀
⠀⢹⣿⣿⣿⣿⣿⢿⣽⠁⣰⣿⣿⣿⣷⣯⣷⣿⡆⠈⣿⣿⣿⣿⣿⣿⣿⡏⠀⠀
⠀⣾⣿⣿⣿⣿⡿⣿⡇⠀⢿⣿⡿⣿⣿⣿⣿⣿⡗⠀⢸⣿⣿⣿⣿⣿⣿⣷⠀⠀
⣴⣿⣿⣿⣿⣿⣿⣿⣧⠀⠘⢯⣿⢿⣻⣿⣿⠿⠁⠀⣼⣿⣿⣿⣿⣿⣿⣿⣧⠀
⣿⣿⣿⣿⣿⣿⢿⣿⣿⣦⡀⠀⠉⠙⠛⠋⠉⠀⢀⣴⣿⣿⣿⣿⣿⣿⣿⣽⣿⠀
⠈⣿⣿⣿⣿⣽⣿⣻⣿⢿⣿⣶⣤⣄⣀⣠⣤⣶⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠃⠀
⠀⢻⣿⣿⣿⣿⣽⣳⢿⣻⣿⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣻⣿⣿⣿⣿⡟⠀⠀
⠀⢸⣿⡿⣽⣿⣿⣿⣝⡷⣯⢿⣻⢿⣿⣿⣿⣿⣿⢿⣯⣿⣿⣿⣿⣽⣿⡇⠀⠀
⠀⠀⠙⠿⣿⣿⣿⣿⣿⣿⣷⣯⣽⣿⣾⣿⣯⣽⣾⣿⣿⣿⣿⣿⣿⠟⠋⠀⠀⠀
⠀⠀⠀⠀⠈⠛⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡿⠟⠁⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠉⠛⠿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠿⠛⠉⠀⠀⠀⠀⠀⠀⠀⠀
Osmedeus | https://github.com/j3ssie/osmedeus.git | Osmedeus Workflow Engine for Offensive Security.
Please add / install this superb Workflow Engine for Offensive Security.
🔥 What is Osmedeus?
Osmedeus is a Workflow Engine for Offensive Security. It was designed to build a foundation with the capability and flexibility that allows you to build your own reconnaissance system and run it on a large number of targets.
Thanks**

Closing comment (2022-12-08T19:55:04Z): Duplicate #2562
Repository: BlackArch/blackarch

Issue #219: Add [dnmap].
Created: 2013-08-19T21:55:03Z
This tool was suggested by a BlackArch user.

Duplicate issue #49: Add [dnmap-server].
Created: 2013-08-12T23:40:02Z
This tool was suggested by a BlackArch user.

Closing comment (2013-10-20T18:59:11Z): Duplicate of #219.
Repository: BlackArch/blackarch

Issue #36: Add [bully].
Created: 2013-08-12T23:39:57Z
This tool was suggested by a BlackArch user.

Duplicate issue #146: Add [bully].
Created: 2013-08-19T03:30:06Z
This tool was suggested by a BlackArch user.

Closing comment (2013-10-08T10:19:44Z): Duplicate of #36.
Repository: BlackArch/blackarch

Issue #2759: Broken package monitoring
Created: 2020-05-06T20:06:29Z
broken packages reason

 aimage: configure: error: OpenSSL library 'libssl-dev' not installed; cannot continue.
 amoco: #2760
 autopwn: upstream nccgroup/autopwn#14
 malcom broken #2857
 cmsscanner #3519
 xplico #3661
 aws-extender-cli & python-boto #4141

Duplicate issue #2201: [dirsearch] log permission error
Created: 2019-01-23T10:50:21Z
By default dirsearch save logs in the install dir causing permission error :

 _|. _ _  _  _  _ _|_    v0.3.8
(_||| _) (/_(_|| (_| )

Extensions: php | Threads: 4 | Wordlist size: 5979
Traceback (most recent call last):
  File "/usr/share/dirsearch/dirsearch.py", line 40, in <module>
    main = Program()
  File "/usr/share/dirsearch/dirsearch.py", line 36, in __init__
    self.controller = Controller(self.script_path, self.arguments, self.output)
  File "/usr/share/dirsearch/lib/controller/Controller.py", line 102, in __init__
    self.setupErrorLogs()
  File "/usr/share/dirsearch/lib/controller/Controller.py", line 226, in setupErrorLogs
    self.errorLog = open(self.errorLogPath, "w")
PermissionError: [Errno 13] Permission denied: '/usr/share/dirsearch/logs/errors-19-01-23_11-42-34.log'


But I found on their issue tracker there is a way to change the configuration: maurosoria/dirsearch#92
So we should change https://github.com/BlackArch/blackarch/blob/master/packages/dirsearch/PKGBUILD and uncomment save-logs-home = True in /usr/share/dirsearch/default.conf.

Closing comment (2020-09-26T17:51:42Z): @Edu4rdSHL Not exactly the same but anyway it's related to save-logs-home, ok it's not permission this time.
I wanted to quickly log that so I can fix it later myself.
As it is tracked in #2759, is doesn't matter if it doesn't show up in recent issues.
Repository: BlackArch/blackarch

Issue #413: Add [vfeed].
Created: 2013-11-18T19:47:29Z
URL: https://github.com/toolswatch/vFeed
Description: Open Source Cross Linked and Aggregated Local Vulnerability Database main repository

Duplicate issue #467: Add [vfeed].
Created: 2013-12-04T01:48:28Z
Homepage: http://www.toolswatch.org/2013/09/vfeed-open-source-aggregated-vulnerability-database-v0-4-5-released-support-of-cwe-2-5-and-snort-rules/

Closing comment (2013-12-04T01:56:38Z): Duplicate of #413.
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #105: 今天api好像使用不了了
Created: 2020-05-03T02:39:38Z
api今天调用不了，昨天还能用

Duplicate issue #106: api目前好像还是不能用
Created: 2020-05-04T02:18:25Z
作者你好，目前好像还是不能用

Closing comment (2020-05-04T02:21:03Z): Duplicate of #105
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #122: 出现接口反应时间过长、超时504的问题
Created: 2020-11-07T06:05:34Z

Duplicate issue #123: Internal Server Error!
Created: 2020-12-08T06:54:16Z
是接口都不维护了 好像都是超时

Closing comment (2020-12-09T00:49:08Z): Duplicate of #122
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #124: 你好，今天发现服务器连不上
Created: 2020-12-14T09:53:05Z
你好，今天发现服务器连不上

Duplicate issue #126: 浏览器和postman能调通api但是Alamofire不能正常获取接口的数据
Created: 2020-12-15T09:34:13Z
2020-12-15 17:30:56.380663+0800 iYDa[6904:40645799] Task <3E23D370-21AC-40AA-B5B2-D68262C4FE27>.<2> finished with error [-1001] Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x600002e48f60 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <3E23D370-21AC-40AA-B5B2-D68262C4FE27>.<2>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask <3E23D370-21AC-40AA-B5B2-D68262C4FE27>.<2>"
), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://lab.isaaclin.cn/nCoV/api/area?latest=1&province=%E6%B1%9F%E9%97%A8, NSErrorFailingURLKey=https://lab.isaaclin.cn/nCoV/api/area?latest=1&province=%E6%B1%9F%E9%97%A8, _kCFStreamErrorDomainKey=4}
2020-12-15 17:31:09.853527+0800 iYDa[6904:40644417] Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service

Closing comment (2020-12-16T17:23:29Z): Duplicate of #124
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #12: suspectedCount出现异常
Created: 2020-01-28T03:17:23Z
如题，目前数据不对应

Duplicate issue #59: province_suspectedCount的问题
Created: 2020-02-13T22:42:32Z
province_suspectedCount是疑似病例吗？为什么最近的数据province_suspectedCount都是0诶？
provinceName,cityName,province_confirmedCount,province_suspectedCount,province_curedCount,province_deadCount,city_confirmedCount,city_suspectedCount,city_curedCount,city_deadCount,updateTime
甘肃省,兰州,90,0,39,2,35,0,14,2,2020-02-13 23:51:34.768
甘肃省,平凉,90,0,39,2,9,0,1,0,2020-02-13 23:51:34.768
甘肃省,甘南,90,0,39,2,8,0,1,0,2020-02-13 23:51:34.768
甘肃省,天水,90,0,39,2,12,0,6,0,2020-02-13 23:51:34.768
甘肃省,定西,90,0,39,2,9,0,3,0,2020-02-13 23:51:34.768

Closing comment (2020-02-14T09:18:45Z): Duplicate of #12
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #116: api接口无法访问
Created: 2020-07-07T08:30:49Z
您好，今天不知道什么原因，无法访问您提供的api接口

Duplicate issue #117: 504 Gateway Time-out
Created: 2020-07-07T08:35:48Z
#116

Closing comment (2020-07-07T15:13:09Z): Duplicate of #116
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #12: suspectedCount出现异常
Created: 2020-01-28T03:17:23Z
如题，目前数据不对应

Duplicate issue #21: 爬取的山东省数据里，各个城市的疑似人数都是0。
Created: 2020-01-29T04:45:53Z
确诊人数没问题。
疑似人数和死亡人数都是0

Closing comment (2020-01-29T06:56:19Z): Duplicate of #12
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #12: suspectedCount出现异常
Created: 2020-01-28T03:17:23Z
如题，目前数据不对应

Duplicate issue #35: 部分关键数据错乱（死亡和治愈人数互换了）！！！
Created: 2020-02-02T09:04:42Z
如广东的数据：
汇总（正确）：

该省各市数据错乱：

Closing comment (2020-02-02T11:27:37Z): 另，通过API得到的疑似数据大部分为0。请帮忙看看，感谢提供数据。


Duplicate of #12
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #135: 接口无法访问
Created: 2022-04-11T16:19:21Z

Duplicate issue #136: 接口无法访问
Created: 2022-04-11T16:19:49Z

Closing comment (2022-04-19T09:41:41Z): Duplicate of #135
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #124: 你好，今天发现服务器连不上
Created: 2020-12-14T09:53:05Z
你好，今天发现服务器连不上

Duplicate issue #125: 这几天一直获取不到数据
Created: 2020-12-15T02:16:29Z

Closing comment (2020-12-16T17:24:20Z): Duplicate of #124
Repository: BlankerL/DXY-COVID-19-Crawler

Issue #28: /api/area的latest=1选项好像返回了以前的数据?
Created: 2020-01-31T01:52:47Z
一觉醒来一看还以为一夜治愈千人2333

Duplicate issue #29: 数据似乎不是最新的？
Created: 2020-01-31T02:16:42Z
https://lab.isaaclin.cn/nCoV/api/area?latest=1返回的似乎是以前的数据

Closing comment (2020-01-31T05:39:08Z): Duplicate of #28
Repository: Blueforcer/awtrix3

Issue #165: MQTT Boot Loop
Created: 2023-06-05T15:16:42Z
version: 0.67
MQTT via IOBroker
If I connect the clock via MQTT, it is in a boot loop.
with home assistant there are no problems.

Duplicate issue #190: [solved] Bootloop after reboot[BUG]
Created: 2023-06-12T19:37:25Z
First time boot after Flashing works fine. If the ESP is rebootet, doesn't matter if done by button of the firmware or by pressing the two hardware buttons causes an bootloop. It starts up says "check" and after this it reboots and says "check" again
Additional information

Devices involved:

Model: Ulanzi Awtrix Smart Pixel Clock 2882 (TC001)
AWTRIX-LIGHT version: v0.69

Closing comment (2023-06-12T20:06:35Z): If youre using iobroker:
duplicate of #165