i am trying to name my token with metadata but i get this error always.
C:\Users\efeka\Desktop\img\node_modules#solana\web3.js\src\connection.ts:4546
throw new SendTransactionError(
^
SendTransactionError: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: custom program error: 0x7
at Connection.sendEncodedTransaction
(C:\Users\efeka\Desktop\img\node_modules#solana\web3.js\src\connection.ts:4546:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Connection.sendRawTransaction
(C:\Users\efeka\Desktop\img\node_modules#solana\web3.js\src\connection.ts:4505:20)
at async Connection.sendTransaction
(C:\Users\efeka\Desktop\img\node_modules#solana\web3.js\src\connection.ts:4493:12)
at async Object.sendAndConfirmTransaction
(C:\Users\efeka\Desktop\img\node_modules#solana\web3.js\src\util\send-and-confirm-transaction.ts:31:21)
at async main (C:\Users\efeka\Desktop\img\name.ts:62:18) {
logs: [
'Program metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s invoke [1]',
'Program log: Instruction: Update Metadata Accounts v2',
'Program log: Update Authority given does not match',
'Program metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s consumed 5855 of 200000 compute units',
'Program metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s failed: custom program error: 0x7'
]
}
I didnt create token now, i created my token before 1 year. I think i didnt authorize my token or wallet.
Related
I'm using the Solana package with Jupiter swap token. After getting the swap result. I'm executing a transaction synchronously with the Solana package sendTransaction method at that time. I'm getting the below error code.
Jupiter Swagger collection.
{accounts: null, err: {InstructionError: [0, {Custom: 3012}]}, logs: [Program JUP3c2Uh3WA4Ng34tw6kPd2G4C5BB21Xo36Je1s32Ph invoke [1], Program log: Instruction: SetTokenLedger, Program log: AnchorError caused by account: token_account. Error Code: AccountNotInitialized. Error Number: 3012. Error Message: The program expected this account to be already initialized., Program JUP3c2Uh3WA4Ng34tw6kPd2G4C5BB21Xo36Je1s32Ph consumed 5139 of 600000 compute units, Program JUP3c2Uh3WA4Ng34tw6kPd2G4C5BB21Xo36Je1s32Ph failed: custom program error: 0xbc4], unitsConsumed: 0}
Jupiter can create up to 3 transactions (setupTransaction, swapTransaction, cleanupTransaction). Make sure that you execute all of them (if they are not null) in this order.
Followed steps from below link:
https://dataplatform.cloud.ibm.com/docs/content/wsj/manage-data/conn-box.html
When trying to configure box to Cloudpak from the above information, getting below error
The test was not successful
The assets request failed: CDICO0100E: Connection failed: Null pointer error
I'm trying to deploy my release on a azure web App. It's not working and I don't know what to do. Maybe I'm missing something in the configuration in my app service or in my release pipeline. I've got the following error
Failed to fetch App Service 'myAppServiceName' publishing credentials. Error: Could not fetch access token for Managed Service Principal.
And here is a block of my debug :
2019-04-11T08:25:35.4761242Z ##[debug]Predeployment Step Started
2019-04-11T08:25:35.4776374Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data subscriptionid = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
2019-04-11T08:25:35.4776793Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data subscriptionname = Paiement à l’utilisation
2019-04-11T08:25:35.4777798Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e auth param serviceprincipalid = null
2019-04-11T08:25:35.4778094Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data environmentAuthorityUrl = https://login.windows.net/
2019-04-11T08:25:35.4781237Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e auth param tenantid = ***
2019-04-11T08:25:35.4782509Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e=https://management.azure.com/
2019-04-11T08:25:35.4782769Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data environment = AzureCloud
2019-04-11T08:25:35.4785012Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e auth scheme = ManagedServiceIdentity
2019-04-11T08:25:35.4785626Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data msiclientId = undefined
2019-04-11T08:25:35.4785882Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data activeDirectoryServiceEndpointResourceId = https://management.core.windows.net/
2019-04-11T08:25:35.4786107Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data AzureKeyVaultServiceEndpointResourceId = https://vault.azure.net
2019-04-11T08:25:35.4786348Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data AzureKeyVaultDnsSuffix = vault.azure.net
2019-04-11T08:25:35.4786525Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e auth param authenticationType = null
2019-04-11T08:25:35.4786735Z ##[debug]33ddf4aa-03c4-4031-95fa-e2083d49cc9e data EnableAdfsAuthentication = false
2019-04-11T08:25:35.4792324Z ##[debug]{"subscriptionID":"mysubscriptionID","subscriptionName":"Paiement à l’utilisation","servicePrincipalClientID":null,"environmentAuthorityUrl":"https://login.windows.net/","tenantID":"***","url":"https://management.azure.com/","environment":"AzureCloud","scheme":"ManagedServiceIdentity","activeDirectoryResourceID":"https://management.azure.com/","azureKeyVaultServiceEndpointResourceId":"https://vault.azure.net","azureKeyVaultDnsSuffix":"vault.azure.net","authenticationType":null,"isADFSEnabled":false,"applicationTokenCredentials":{"clientId":null,"domain":"***","baseUrl":"https://management.azure.com/","authorityUrl":"https://login.windows.net/","activeDirectoryResourceId":"https://management.azure.com/","isAzureStackEnvironment":false,"scheme":0,"isADFSEnabled":false}}
2019-04-11T08:25:35.4809400Z Got service connection details for Azure App Service:'myAppServiceName'
2019-04-11T08:25:35.4846967Z ##[debug][GET]http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/
2019-04-11T08:25:35.5443632Z ##[debug]Deployment Failed with Error: Error: Failed to fetch App Service 'myAppServiceName' publishing credentials. Error: Could not fetch access token for Managed Service Principal. Please configure Managed Service Identity (MSI) for virtual machine 'https://aka.ms/azure-msi-docs'. Status code: 400, status message: Bad Request
2019-04-11T08:25:35.5444488Z ##[debug]task result: Failed
2019-04-11T08:25:35.5501745Z ##[error]Error: Failed to fetch App Service 'myAppServiceName' publishing credentials. Error: Could not fetch access token for Managed Service Principal. Please configure Managed Service Identity (MSI) for virtual machine 'https://aka.ms/azure-msi-docs'. Status code: 400, status message: Bad Request
2019-04-11T08:25:35.5511780Z ##[debug]Processed: ##vso[task.issue type=error;]Error: Failed to fetch App Service 'myAppServiceName' publishing credentials. Error: Could not fetch access token for Managed Service Principal. Please configure Managed Service Identity (MSI) for virtual machine 'https://aka.ms/azure-msi-docs'. Status code: 400, status message: Bad Request
2019-04-11T08:25:35.5512729Z ##[debug]Processed: ##vso[task.complete result=Failed;]Error: Failed to fetch App Service 'myAppServiceName' publishing credentials. Error: Could not fetch access token for Managed Service Principal. Please configure Managed Service Identity (MSI) for virtual machine 'https://aka.ms/azure-msi-docs'. Status code: 400, status message: Bad Request
2019-04-11T08:25:35.5512828Z Failed to add release annotation. Error: Failed to get App service 'myAppServiceName' application settings. Error: Could not fetch access token for Managed Service Principal. Please configure Managed Service Identity (MSI) for virtual machine 'https://aka.ms/azure-msi-docs'. Status code: 400, status message: Bad Request
2019-04-11T08:25:35.5645194Z (node:5004) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Failed to fetch App Service 'myAppServiceName' publishing profile. Error: Could not fetch access token for Managed Service Principal. Please configure Managed Service Identity (MSI) for virtual machine 'https://aka.ms/azure-msi-docs'. Status code: 400, status message: Bad Request
2019-04-11T08:25:35.5759915Z ##[section]Finishing: Deploy Azure App Service
And some screenshot of
azure missing configuration ?
release pipeline config 1
release pipeline config 2
release pipeline config 3
Let me know if you need more informations.. I'm new in this so maybe missing simple things... Best regards
do you have setting identity Status On ?
like below
In my case, we had just moved our app service to a new resource group, but the pipeline was still referencing the old resource group. Correcting the resource group fixed the issue
A simple typo can also be the reason for this error message.
You will get this error message even though if it's just a typo or wrong value in your "slotName".
Please do ensure that the "slotName" you've given is the actual slotname (the default is 'production'). So if you've added a slot that's called 'stage' then inside the portal it will have your '/stage' or '-stage', but it's still just called 'stage'.
I know several have had this error message shown and none of the above helped them out (I faced the same issue the first time).
My research indicated this to be an intermittent problem.
I redeployed 2 times and it worked.
The first redeploy - just seemed to wait for ages to connect to an available agent, so I cancelled that too, and redeployed - which worked without any issue.
If this is still an issue or if someone had this issue, all I did was just to rerun the release and it well went well. Hopefully someone has saved time by just re-releasing, if this wont work then probably try something else.
From my react native application, I am trying to authenticate against FB. Instead of directly using fbsdk, I was planning to use a wrapper around it.
I tried two wrappers.
https://github.com/xxsnakerxx/react-native-social-auth
https://github.com/magus/react-native-facebook-login
In both cases, I end up with a WebView which won't callback the app.
I have raised two issues
https://github.com/magus/react-native-facebook-login/issues/187
https://github.com/xxsnakerxx/react-native-social-auth/issues/6
XCode logs has below entries which I am not able to decipher
2016-12-09 06:13:29.757 XXXX[61829:8555589] -canOpenURL: failed for URL: "fbauth2:/" - error: "The operation couldn’t be completed. (OSStatus error -10814.)"
2016-12-09 06:13:29.759 XXXX[61829:8555589] -canOpenURL: failed for URL: "fbauth2:/" - error: "The operation couldn’t be completed. (OSStatus error -10814.)"
and..
__nw_socket_service_writes_block_invoke sendmsg(fd 9, 31 bytes): socket has been closed
2016-12-09 06:13:36.670958 XXXX[61829:8574160] [] nw_endpoint_flow_protocol_error [15.1 157.240.7.20:443 cancelled socket-flow (null)] Socket protocol sent error: [32] Broken pipe
2016-12-09 06:13:36.671154 XXXX[61829:8574160] [] nw_endpoint_flow_protocol_disconnected [15.1 157.240.7.20:443 cancelled socket-flow (null)] Output protocol disconnected
And the WebView post all the authentication looks like
Eventually successful with react-native-social-auth. Missed a few configurations.
I am using Mocha to test a Sails application. I have 2 test files. Both test files do the standard Before/After Sails.lift and Sails.lower.
When I run mocha test/TestDataEntry.js and mocha test/TestEventEntry separately, they execute properly. If I run just mocha, test/TestDataEntry executes properly but test/TestEventEntry fails. It seems as if the Sails server is not cycling down and up properly. Any suggestions for handling this issue would be appreciated. The terminal output is as follows:
larry#larry-Aspire-M3985 ~/Projects/web-backend $ mocha
Data Entry testing:
sails lifted
✓ bad url
✓ bad device (91ms)
✓ expired token (61ms)
✓ bad packet: missing Data field (59ms)
✓ bad packet: Data is not an array (62ms)
✓ bad packet: Data is empty (60ms)
✓ bad packet: missing data field D2 (60ms)
✓ bad packet: missing data field D1 (62ms)
✓ bad packet: missing data field TS (61ms)
✓ bad packet: bad timestamp field (64ms)
✓ good packet (60ms)
sails down
Event Entry testing:
sails lifted
✓ bad url
1) bad device
double callback!
2) expired token
double callback!
3) bad packet: missing Data field
double callback!
4) bad packet: Data is not an array
double callback!
5) bad packet: Data is empty
double callback!
6) bad packet: missing data field ED
double callback!
7) bad packet: missing data field ET
double callback!
8) bad packet: missing data field TS
double callback!
9) bad packet: bad timestamp field
double callback!
10) good packet
double callback!
sails down
12 passing (2s)
10 failing
1) Event Entry testing: bad device:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
2) Event Entry testing: expired token:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
3) Event Entry testing: bad packet: missing Data field:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
4) Event Entry testing: bad packet: Data is not an array:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
5) Event Entry testing: bad packet: Data is empty:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
6) Event Entry testing: bad packet: missing data field ED:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
7) Event Entry testing: bad packet: missing data field ET:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
8) Event Entry testing: bad packet: missing data field TS:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
9) Event Entry testing: bad packet: bad timestamp field:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
10) Event Entry testing: good packet:
Uncaught AssertionError: expected [Error: connect ECONNREFUSED] to be null
The following is the Before/After code:
before(function (done) {
// Lift Sails and start the server
Sails.lift({
log: {
level: 'error'
}
}, function (err, sails) {
console.log("sails lifted");
done();
});
});
after(function (done) {
console.log('sails down');
Sails.lower(done);
});
OK, it turns out that there is an anonymous parent describe block that is the parent of all of the test file describe blocks. So if a before/after hook is introduced at the anonymous parent level, then it covers all of the test files as a group.
Mocha executes the test files in alphabetical order by default. So I have constructed a test file 'aaaa.js' that only contains the before/after lifting and lowering of Sails. This introduces the before/after hooks at the parent level.
Now, 'mocha' executes all of the test files in test/* without a problem. The only drawback to this approach is that I no longer have the before/after hooks in the individual test files and therefore must use: 'mocha test/aaaa.js test/TestDataEntry.js' to ensure that Sails is lifted and lowered properly.
An approach to run multiple mocha tests with sails is to spawn a new sails instance for each mocha test
var SailsApp = require('sails').Sails;
describe('MochaTest',function() {
var sails = new SailsApp();
before(function(done) {
sails.lift({},
function(err,server) {
if(err) {
done(err);
} else {
done(err,sails);
}
});
});
after(function(done) {
sails.lower(done);
});
});