gradle – ERROR: Method android () for arguments could not be found

Este es el error que me da android studio

El buildGradle:

 android {
        compileSdkVersion 23
        buildToolsVersion '23.0.1'

        defaultConfig {
            applicationId 'com.MyApp'
            minSdkVersion 9
            targetSdkVersion 21
            versionCode 1
            versionName "1.0"
        }

        lintOptions {
            abortOnError false
        }

        buildscript {
            repositories {
                google() // For Gradle 4.0+
                maven { url 'https://maven.google.com' }
            }
            dependencies {
                classpath 'com.android.tools.build:gradle:3.5.0'

                // NOTE: Do not place your application dependencies here; they belong
                // in the individual module build.gradle files
            }
        }

        allprojects {
            repositories {
                jcenter()
                maven
            }
        }

        dependencies {
            compile fileTree(dir: 'libs', include: ('*.jar'))
        }
    }

y el gradle-wrapper.properties:

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-2.6-all.zip

El error:

ERROR: Method android () for arguments could not be found
(build_szu6u1qudhn719nxb58vfd0f $ _run_closure1 @ 1fcc37a7) on root
Project # prueva2 #.

Alguna solution?

Ease of Use – What is the best screen navigation method for invalid user input?

Consider an Angular app with lots of user input through screens A, B, and C. Screen C requires valid inputs from A and B; B only from A; and A is independent. For example, suppose the user enters invalid inputs on screen B.

Question: Which navigation should I support for B in this case?

I currently think that I will not allow navigation to C due to data validation issues. But what about the return to B? On the one hand, there are no validity issues, and the user may want to look up screen A to help screen B enter. On the other hand, this would complicate the status management of the app. An alternative is to disable such navigation, possibly with the option to restore the last valid inputs to B.
Since I lack experience in UX, I would be glad about answers that help me with this compromise.

Defining the shipping method per shipment with partial shipments

We currently use the "Edit Orders" extension of Mageplaza to set "Best Way" as a shipping method when we initially create orders and finish shipping once the order is created and ready to ship. Is there a way to set the shipping method / shipping price per part delivery either through this extension or another order processing option?

Since we are a manufacturer, there may be a sufficiently long lead time between entering an order and picking up an appointment so that we can determine these prices later.

windows – Are there any disadvantages to the Hash Analysis File Comparison method?

I've just read a bit about signature file analysis to see if any files were modified or deleted by an attacker. I noticed that when hiding a file, an attacker could change the first few bytes of a file, damaging the file signature, making it harder for an analyst to see.

Does the hash analysis have similar weaknesses?

sharepoint enterprise – "The specified method is not supported." Error trying to log in with ADFS

I am trying to configure a web application in a SharePoint environment to use ADFS as the login provider.

I followed the steps in this TechNet blog post, and everything seemed to work well until I actually signed up with ADFS.

When I navigate to the web application, a drop-down menu for selecting the credential type appears. I select ADFS and will be redirected to the ADFS login page. I enter the correct credentials and will be sent to https: // WEB_APPLICATION_HOSTNAME / _trust. This page displays a yellow ASP.NET death screen with the following information:

Specified method is not supported.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ServiceModel.FaultException`1((System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)): Specified method is not supported.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


(FaultException`1: Specified method is not supported.)
   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response) +249
   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) +83
   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst) +33
   Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) +1103
   Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) +72
   Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments) +1859
   Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.OnSessionSecurityTokenCreated(SessionSecurityTokenCreatedEventArgs eventArgs) +590
   Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SetPrincipalAndWriteSessionToken(SessionSecurityToken sessionToken, Boolean isSession) +90
   Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request) +701
   Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) +323
   Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs eventArgs) +138
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +215
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +97

For example, SharePoint internally sends a request to the security token service. He responds that an invalid SOAP method is used, but this is just a guess.

I have tried the steps in this Fiddler blog to try to forward these requests through Fiddler, but Fiddler does not capture anything.

Google searches for this situation are not results that are remotely similar to my situation. How can I start troubleshooting?

Below are the ULS logs listed by the request to the _trust endpoint. Remarkably, the first line worries me a lot. The Uri here is the URN I added in step 7 of the TechNet blog post, but it does seem to be a kind of bug.

SharePoint Foundation   General                 adyrv   High        Cannot find site lookup info for request Uri urn:*******.
SharePoint Foundation   Claims Authentication   amb82   Unexpected  Couldn't find a proper match for user email. User: '********************'.
SharePoint Foundation   Claims Authentication   8307    Critical    An exception occurred in ADFS claim provider when calling SPClaimProvider.FillUserKeyForEntity(): Specified method is not supported..
SharePoint Foundation   Monitoring              b4ly    High        Leaving Monitored Scope (SPClaimProvider.FillUserKeyForEntity()). Execution Time=120.4741
SharePoint Foundation   Claims Authentication   af3zp   Unexpected  STS Call Claims Saml: Problem getting output claims identity. Exception: 'System.NotSupportedException: Specified method is not supported.     at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime tokenLifeTime)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.CreateTokenCacheReferenceFromUserId(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentTokenCacheReferenceClaim(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentOutputIdentityForRequest(SPRequestInfo requestInfo, IClaimsIdentity outputIdentity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity(IClaimsPrincipal principal, RequestSecurityToken request, Scope scope)'.
SharePoint Foundation   Monitoring              b4ly    High        Leaving Monitored Scope (SPSecurityTokenService.GetOutputClaimsIdentity()). Execution Time=121.9425
SharePoint Foundation   Claims Authentication   fo1t    Monitorable STS Call: Failed to issue new security token. Exception: System.NotSupportedException: Specified method is not supported.     at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime tokenLifeTime)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.CreateTokenCacheReferenceFromUserId(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentTokenCacheReferenceClaim(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentOutputIdentityForRequest(SPRequestInfo requestInfo, IClaimsIdentity outputIdentity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity(IClaimsPrincipal principal, RequestSecurityToken request, Scope scope)     at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request)
SharePoint Foundation   Monitoring              b4ly    High        Leaving Monitored Scope (SPSecurityTokenService.Issue). Execution Time=125.8951
SharePoint Foundation   Topology                aeayc   High        (Forced due to logging gap, cached @ 11/14/2019 01:19:26.79, Original Level: Verbose) The SecurityTokenServiceHeaderInfo including the correlation ID was added.
SharePoint Foundation   Monitoring              b4ly    High        Leaving Monitored Scope (ExecuteSecurityTokenServiceOperationCaller:http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue). Execution Time=141.6527
SharePoint Foundation   Claims Authentication   fsq7    High        SPSecurityContext: Request for security token failed with exception: System.ServiceModel.FaultException`1(System.ServiceModel.ExceptionDetail): Specified method is not supported. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.NotSupportedException: Specified method is not supported.    at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime token...).
SharePoint Foundation   Claims Authentication   8306    Critical    An exception occurred when trying to issue security token: Specified method is not supported..
SharePoint Foundation   Claims Authentication   af3xx   Unexpected  Claims Saml Sign-In: Could not get local token for trusted third party token. FaultException: 'System.ServiceModel.FaultException`1(System.ServiceModel.ExceptionDetail): Specified method is not supported. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.NotSupportedException: Specified method is not supported.    at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime token...).'. Stack: '   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf)     at Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments)'.
SharePoint Foundation   Monitoring              b4ly    High        Leaving Monitored Scope (SPFederationAuthenticationModule.OnSessionSecurityTokenCreated). Execution Time=143.4391
SharePoint Foundation   Monitoring              b4ly    High        Leaving Monitored Scope (SPFederationAuthenticationModule.OnAuthenticateRequest::WifCodeCall). Execution Time=161.2515
SharePoint Foundation   Micro Trace             uls4    High        Micro Trace Tags: 0 adyrv,143 b4ly,0 fsq7,0 af3xx,0 b4ly,0 b4ly

vue.js – Laravel + Vuejs: The POST method is not supported for this route: Import in table with Laravel Excel

Greetings I have a problem with Laravel. I would like to send an Excel file from my component created in Vuejs. I want to import this file into a spreadsheet with about 5Mb and 36 records. I'm using the LaravelExcel V.3 library, I'm using multipart / form data on my form and my route is POST type with the axios library. I appreciate your answers and contributions.

My component – FrontEnd


My component – Vuejs


My post route in Laravel

//Medicamentos (Catalogo)
Route::post('/actualizacatalogo','MedicamentoController@importarexcel');

My controller

public function importarexcel(Request $request)
    {

            Excel::import(new MedicamentoImport(),$request->file('file'));
            return back();

    }

Enter image description hereEnter image description here

PHP – Error generating PDF send data using the GET method

I'm trying to create a PDF report that collects information from a table of data. This table contains a field called PIN. The situation is that I have an administration window in which I have records from another table, and these records also have a field named PIN corresponding to my data table from which I extract the information to generate the PDF ,

The problem is that when trying to generate PDF, the PIN selected by the GET method is sent to the URL of the file that generated the PDF DO NOT GENERATE However, if you send the PIN via URL, the page will be empty.
Thanks for your help.

Button code that sends the PIN from which you want to generate the PDF.

  ";?>

PDF generated code:

 set_charset("utf8"); 
$sql = "SELECT * FROM datos WHERE pin ='{$_GET('pin')}' ORDER BY pin ASC";   
$result = mysqli_query($conn, $sql); 

while($row = mysqli_fetch_array($result))  
{      
$output .= 'TODO EL CONTENIDO HTML DEL PDF CONSULTADO CON EL DATO "PIN"';  
}  
return $output; 
}  
if(isset($_POST("generate_pdf")))  
{  
require_once('TCPDF-master/tcpdf.php');
//PROPIEDADES DEL PDF
}