IDIBU / LINKEDIN ERROR - linkedin

I am trying to post jobs from Idibu onto Linkedin. It's been working for a long time but suddenly on Friday (02/02/2018), I get an error.
After contacting Idibu and Linkedin, they advised me to post a message on here.
Error Code:
job identifier: 1858414_
status: FAIL
1858414array (
0 => '3ab2bd03-1e32-482e-8965-a79a07997aab',
)
Using key TCzaHpd1TWgGvNVw6qxnC0Pp8N9OBHV3F1p0xW_spLODYKr1mIA0aSaPSdjB2WN9
token: 3ab2bd03-1e32-482e-8965-a79a07997aab
Job was added to the database but error occured during posting to linkedin:
Internal service error
array (
'status' => '500',
'timestamp' => '1517585944663',
'request-id' => 'UA9WGL98JP',
'error-code' => '0',
'message' => 'Internal service error',
)
<?xml version="1.0" encoding="UTF-8"?>
<share>
<comment><![CDATA[HR Assessor / Trainer, London, £29500 - £34000 per annum, Education & Training]]></comment>
<content>
<title><![CDATA[HR Assessor / Trainer, London, £29500 - £34000 per annum, Education & Training]]></title>
<submitted-url>http://idi.to/5iNV<;/submitted-url>
<submitted-image-url><! [CDATA[https://www.aptrack.co/uap/logos/linkedin_status.jpg]]>;</submitted-image-url>
<description><![CDATA[KM Recruitment is a specialist UK wide recruiter for the Work Based Learning and Welfare to Work sectors.
Job Title: HR Assessor / Trainer
Location: London -..]]></description>
</content>
<visibility>
<code>anyone</code>
</visibility>
</share>

We were experiencing 'Internal API server' errors for weeks in October during profile requests. Persistent questions to enterprise support resulted in a similar suggestion (look on stackoverflow), but I kept at it and was finally told that we had identified a "java bug".
No further explanation and a few weeks later I was notified that a fix would be released soon. After that, the issue seemed to stop, but we're now seeing a new spike in the same type of errors.
OAuth2 Error Occurred: : =0A{=0A "errorCode": 0,=0A "message": "Internal API server error",=0A "requestId": "(removed)",=0A "status": 500,=0A "timestamp": 1518103930225=0A}

Related

The API I'm testing sometimes respond with different error codes and questions, how can I used 'Examples' and match assertion to check one OR other? [duplicate]

Files for the scenario
All the files are on same directory.
title-update-request.json
{id: 12, name: 'Old Hello', config:[{username: 'qwe', password: 'tyu'},{username: 'abc', password: 'xyz'}]}
title-update-response.json
{id: 12, name: 'New Hello', config:[{username: 'qwe', password: 'tyu'},{username: 'abc', password: 'xyz'}]}
title-update-error-request.json
{id: 00, name: 'Old Hello', config:[{username: 'qwe', password: 'tyu'},{username: 'abc', password: 'xyz'}]}
title-update-error-response.json
{Error: 'not found', Message: 'The provided Book is not found.'}
book-record.feature
Feature: CRUD operation on the book records.
Background:
* def signIn = call read('classpath:login.feature')
* def accessToken = signIn.accessToken
* url baseUrl
Scenario: Change title of book in the single book-record.
* json ExpResObject = read('classpath:/book-records/title-update-response.json')
* json ReqObject = read('classpath:/book-records/title-update-request.json')
* call read('classpath:/book-records/update.feature') { Token: #(accessToken), ReqObj: #(ReqObject), ResObj: #(ExpResObject), StatusCode: 200 }
Scenario: Change title of book in the non-existing book-record.
* json ExpResObject = read('classpath:/book-records/title-update-error-request.json')
* json ReqObject = read('classpath:/book-records/title-update-error-response.json')
* call read('classpath:/book-records/update.feature') { Token: #(accessToken), ReqObj: #(ReqObject), ResObj: #(ExpResObject), StatusCode: 400 }
update.feature
Feature: Update the book record.
Scenario: Update single book-record.
Given path '/book-record'
And header Authorization = 'Bearer ' + __arg.Token
And header Content-Type = 'application/json'
And request __arg.ReqObj
When method put
Then status __arg.StatusCode
And response == __arg.ExpectedResponse
Actual API response for scenario: 1 is :
{name: 'New Hello', config:[{username: 'abc', password: 'xyz'},{username: 'qwe', password: 'tyu'}]}
Actual API response for scenario: 2 is :
{Error: 'not found', Message: 'The provided Book is not found.'}
Question: How should I validate the response in update.feature file since problem is if I make change s as using #^^config that will not works for scenario :2 and response == _arg.ExpectedResponse is not working for Scenario: 1?
This is classic over-engineering of tests. If someone has told you that "re-use" is needed for tests, please don't listen to that person.
You have two scenarios, one happy path and one negative path. I am providing how you should write the negative path here below, the rest is up to you.
Scenario: Change title of book in the non-existing book-record.
Given path 'book-record'
And header Authorization = 'Bearer ' + accessToken
And request {id: 00, name: 'Old Hello', config:[{username: 'qwe', password: 'tyu'},{username: 'abc', password: 'xyz'}]}
When method put
Then status 400
And response == {Error: 'not found', Message: 'The provided Book is not found.'}
See how clean it is ? There is no need for "extreme" re-use in tests. If you still insist that you want a super-generic re-usable feature file that will handle ALL your edge cases, you are just causing trouble for yourself. See how un-readable your existing tests have become !!
EDIT: Since I refer the question to others often as an example of how NOT to write tests, I wanted to make my point more clear and add a couple of links for reference.
Sometimes it is okay to "repeat yourself" in tests. Tests don't have to be DRY. Karate is a DSL that enables you to make HTTP calls or JSON manipulation in one or two lines. When you start attempting "re-use" like this, it actually leads to more harm than good. For example, you now need to look at multiple files to understand what your test is doing.
If you don't believe me, maybe you will believe the team at Google: https://testing.googleblog.com/2019/12/testing-on-toilet-tests-too-dry-make.html

The AWS Lambda returns "Error: connect ETIMEDOUT **.****.***.***:443"

I have to services, Admin Panel(Laravel) и Online Shop(Woocommerce). The relation between these to services was realized with AWS Lambda.
When I try to send an updating product request from my Admin panel to online shop, time to time the lambda couldn't connect to the Woocomerce API.
On time when the system is not updating the product, lambda returns the error "Error: connect ETIMEDOUT"
I originally thought that the Wordpress didn't have enought time for updating process. And decided to increase the lambda's timeout (60000 ms). But it didn't help. I still found the ETIMEDOUT errors in logs.
By the way, the time period between sending the updating request to woocommerce and showing an error is 2 min. If I right understand, the lambda had enough time for getting the answer from woocommerce.
Another strange thing. According the lambda's logs, on time when lambda got an error, the woocommerce API was available. It seems like something disconnects the internet on time when lambda is sending the request.
My question is, why lambda cannot send to Woocommerce API the request. Why it happens time to time?
P.S. Below I added the example of lambda's logs.
The log on starting sending the updating request.
2021-08-14T18:23:48.692Z b228455b-45a8-5cbf-8160-1cc INFO Inside edit Online List {
status: '1',
*********
is_delete: 0,
name: 'Omega Speedmaster Moonwatch Chronograph 42mm ',
price_on_request: 0,
on_sale: 0
}
The log with error.
2021-08-14T18:25:58.299Z b228455b-45a8-5cbf-8aae6 INFO WooCommerce editOnlineStock err::: { Error: connect ETIMEDOUT ***.****.***.***:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
address: '***.****.***.***',
port: 443,
config:
{ url:
'https://domain/wp-json/wc/v3/products/*****',
method: 'put',
params: {},
data:
'{"name":"Omega Speedmaster Moonwatch Chronograph 42mm ","type":"simple"***********',
headers:
{ Accept: 'application/json',
'Content-Type': 'application/json;charset=utf-8',
'User-Agent': 'WooCommerce REST API - JS Client/1.0.1',
'Content-Length': 681 },
auth:
{ username: 'ck_************',
password: 'cs_************' },
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 60000,
adapter: [Function: httpAdapter],
responseType: 'json',
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
****************************
Is your lambda associated with a VPC? If so, i) explore to see if the VPC has a route out to the internet with a NAT gateway/instance, ii) examine the VPC flow logs for errors.

Receiving a 429 error when trying to create a storage account during ARM deploy

Reciving this error when trying to deploy to a recently deleted resource group.
Have left this running for 40 minutes but it never clears.
When i use a completley newly named resource group this doesnt happen.
In my ARM template I create this storage account before i try and create the serverfarm associated with it.
Any help would be very grateful, i can also repeat this with the same resource group.
OPERATION ID90AB707C6611418B
TRACKING ID67c301c6-93a6-4372-98bf-5bfe60f7df5f
STATUS429
PROVISIONING STATERunning
TIMESTAMP29/08/2018, 12:16:59
DURATION37 seconds
TYPEMicrosoft.Web/serverfarms
RESOURCE ID/subscriptions/<removed>/resourceGroups/<removed>/providers/Microsoft.Web/serverfarms/<removed>
STATUSMESSAGE{
"Code": "Conflict",
"Message": "Cannot modify this web hosting plan because another operation is in progress. Details: Id: 39c36b85-ea54-4bc0-899f-7776e15f2511, OperationName: Create, CreatedTime: 8/29/2018 8:41:20 AM, RequestId: ce52f313-8193-4e09-bfab-28892d69adb4, EntityType: 9",
"Target": null,
"Details": [
{
"Message": "Cannot modify this web hosting plan because another operation is in progress. Details: Id: 39c36b85-ea54-4bc0-899f-7776e15f2511, OperationName: Create, CreatedTime: 8/29/2018 8:41:20 AM, RequestId: ce52f313-8193-4e09-bfab-28892d69adb4, EntityType: 9"
},
{
"Code": "Conflict"
},
{
"ErrorEntity": {
"ExtendedCode": "59205",
"MessageTemplate": "Cannot modify this web hosting plan because another operation is in progress. Details: {0}",
"Parameters": [
"Id: 39c36b85-ea54-4bc0-899f-7776e15f2511, OperationName: Create, CreatedTime: 8/29/2018 8:41:20 AM, RequestId: ce52f313-8193-4e09-bfab-28892d69adb4, EntityType: 9"
],
"Code": "Conflict",
"Message": "Cannot modify this web hosting plan because another operation is in progress. Details: Id: 39c36b85-ea54-4bc0-899f-7776e15f2511, OperationName: Create, CreatedTime: 8/29/2018 8:41:20 AM, RequestId: ce52f313-8193-4e09-bfab-28892d69adb4, EntityType: 9"
}
}
],
"Innererror": null
}
Storage accounts can be notoriously slow to delete. Your conflict is likely caused by that resource not having been removed yet.
You should be able to see the resource group in the portal to verify that the assets still exist, or you can query the status with Get-AzureRmResourceGroupDeployment -ResourceGroupName ResourceGroupName.
You can also check activity logs.

2Checkout Authorization Fails since June

From the beginning of this (June 2018) month most of my clients can not pay with 2Checkout by card, everything was OK before.
I begin collecting the responses, they are always the same:
"validationErrors":null,
"exception":{
"errorMsg":"Authorization Failed",
"httpStatus":"400",
"exception":false,
"errorCode":"600"
},"response":null
I have no idea what is going on, I tried to contact their support team, but everything they said, that everything should work, but actually it doesn't!
I use API to process payments. The website code haven't changed since that time.
The request to 2CO looks like this:
Array
(
[method] => POST
[timeout] => 45
[headers] => Array
(
[Accept] => application/json
[Content-Type] => application/json
)
[body] => {
"sellerId":"my seller id",
"privateKey":"my private key",
"merchantOrderId":just a random number,
"token":"token received from 2CO",
"currency":"USD",
"total":"130.00",
"billingAddr":{
"name":"name from debit/credit card here",
"addrLine1":"customer address here",
"addrLine2":"",
"city":"customer city here",
"state":"",
"zipCode":"",
"country":"MX",
"email":"customer email here"
},
"lineItems":[{
"name":"product name here",
"price":"130.00",
"type":"product",
"quantity":"1"
}]
}
)
Above is the example for a Mexico customer, so, addrLine2, state and zipCode are not required.
Thanks for help in advance!

preview is not working for actions-on-google, web & device

Having trouble getting my action to work in preview.
After installing the app on gcloud I ran....
./gactions preview -action_package=agent.json -invocation_name="my action"
... and I got...
Pushing action 'my action' for testing...
'my action' is now available for you until 2017-04-08 9:32AM CDT (29 minutes from now)
Try 'gactions simulate', then 'talk to my action', or use the Web Simulator at https://g.co/actionswebsim.
Then I ran...
./gactions simulate
.. and I got...
User TTS (CTRL-C to stop):
Than from the device I got...
Sorry I don't know how to help with that...
And from the web simulator I got....
{
"response": "Sorry, this action is not available in simulation",
"audioResponse": "//NExAASq..."content_copy,
"debugInfo": {
"sharedDebugInfo": [
{
"name": "GOOGLE_SYSTEM_ACTION",
"debugInfo": "Your query is handled by Google’s system actions"
}
]
}
}
Any ideas?
Thanks,
Don
In order for the simulator to invoke your intent, you have to begin with "talk to your invocation name" or "at your invocation name for deep link phrase"
More details here:
https://developers.google.com/actions/distribute/invocation-and-discovery
It works for me.
Just type excatly the following 'talk to my test app'

Resources