pguardiario

pguardiario

Member Since 1 year ago

Experience Points
0
follower
Lessons Completed
0
follow
Lessons Completed
10
stars
Best Reply Awards
23
repos

43 contributions in the last year

Pinned
⚡ Solve captchas for Puppeteer / Selenium
⚡ Make http2 requests that look like the real thing
⚡ A simple trick to scrape html tables with selenium painlessly.
⚡ A shell for executing sqlite queries
⚡ convert csv file to xlsx
⚡ A tool for scraping websites
Activity
Oct
18
17 hours ago
Activity icon
issue

pguardiario issue comment ethereum/go-ethereum

pguardiario
pguardiario

CRIT Failed to persist storage slots

System information

Version: 1.10.10-stable Git Commit: bb74230f2a93057b92bf58aab09c9438ce435f95
Architecture: amd64 Go Version: go1.17.2 Operating System: linux GOPATH= GOROOT=go

Expected behaviour

Normal operation

Actual behaviour

geth crashes

Steps to reproduce the behaviour

geth --ws

Backtrace

CRIT [10-18|02:51:04.158] Failed to persist storage slots          err="write /root/.ethereum/geth/chaindata/000003.log: file too large"
pguardiario
pguardiario

Sorry, please close if this is a leveldb error, I will post the issue there if I can't resolve it.

On Mon, Oct 18, 2021 at 6:50 AM Martin Holst Swende < ***@wrote:

Well, the error is pretty plain: write /root/.ethereum/geth/chaindata/000003.log: file too large". This is an error which comes from go-leveldb, the database underlying go-ethereum. What is the size if that file? What flavour of linux, and what type of filesystem are you using?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ethereum/go-ethereum/issues/23759#issuecomment-945416687, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOASJVQ7DHEQVPBOFDIHSQDUHO7UZANCNFSM5GFSJIZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Activity icon
issue

pguardiario issue ethereum/go-ethereum

pguardiario
pguardiario

CRIT Failed to persist storage slots

System information

Version: 1.10.10-stable Git Commit: bb74230f2a93057b92bf58aab09c9438ce435f95
Architecture: amd64 Go Version: go1.17.2 Operating System: linux GOPATH= GOROOT=go

Expected behaviour

Normal operation

Actual behaviour

geth crashes

Steps to reproduce the behaviour

geth --ws

Backtrace

CRIT [10-18|02:51:04.158] Failed to persist storage slots err="write /root/.ethereum/geth/chaindata/000003.log: file too large"

Oct
7
1 week ago
Activity icon
fork

pguardiario forked ProjectOpenSea/opensea-whitelabel

⚡ Easily whitelabel an OpenSea marketplace for your own website
pguardiario Updated
fork time in 1 week ago
Activity icon
issue

pguardiario issue comment ProjectOpenSea/opensea-js

pguardiario
pguardiario

seaport.createBuyOrder is not working - returns 429 error every time.

Hi Team

I'm using code from the opensea-creatures project (sell.js) to create an OpenSeaPort instance and call seaport.createBuyOrder()

My Node & npm versions C:\Users\Owner>node -v v12.18.4

C:\Users\Owner>npm -v 6.14.6

Script const {OpenSeaPort,Network} = require('opensea-js') const RPCSubprovider = require('web3-provider-engine/subproviders/rpc') const Web3ProviderEngine = require('web3-provider-engine') const {MnemonicWalletSubprovider} = require('@0x/subproviders'); const accountAddress = "0x2c649A72529FfB801825a52136e0D5C8F171f6Bd" const API_KEY = ""; const NFT_CONTRACT_ADDRESS_SVS = "0x219b8ab790decc32444a6600971c7c3718252539"; const NFT_TOKEN_ID = "3400"; const NETWORK = "mainnet"; const NODE_API_KEY = "e1d6858ba67049bc934a9b764efb9c31"; const isInfura = true;//!!process.env.INFURA_KEY; const MNEMONIC = "My Metamask Mneumonic here"; const BASE_DERIVATION_PATH = 44'/60'/0'/0; const network = NETWORK === "mainnet" || NETWORK === "live" ? "mainnet" : "rinkeby";

const mnemonicWalletSubprovider = new MnemonicWalletSubprovider({ mnemonic: MNEMONIC, baseDerivationPath: BASE_DERIVATION_PATH, });

const infuraRpcSubprovider = new RPCSubprovider({ rpcUrl: isInfura ? "https://" + network + ".infura.io/v3/" + NODE_API_KEY : "https://eth-" + network + ".alchemyapi.io/v2/" + NODE_API_KEY, });

const providerEngine = new Web3ProviderEngine(); providerEngine.addProvider(mnemonicWalletSubprovider); providerEngine.addProvider(infuraRpcSubprovider); providerEngine.start();

const seaport = new OpenSeaPort( providerEngine, { networkName: NETWORK === "mainnet" || NETWORK === "live" ? Network.Main : Network.Rinkeby, apiKey: API_KEY, }, (arg) => console.log(arg) );

placeOffer(NFT_CONTRACT_ADDRESS_SVS, NFT_TOKEN_ID, 0.0000001, Math.round(Date.now() / 1000 + 60 * 3))

async function placeOffer(address, tokenId, price , expirationTime) {
const asset = { tokenId: tokenId, tokenAddress: address, } try{
const makeOffer = await seaport.createBuyOrder({ asset: asset, accountAddress,
startAmount: price, expirationTime })
console.log(Successfully created a offer! ${makeOffer.asset.openseaLink}); } catch(ex) { console.log(ex) }
}

packages.json

{ "name": "newscript", "version": "1.0.0", "description": "", "main": "test.js", "scripts": { "test": "echo "Error: no test specified" && exit 1" }, "author": "", "license": "ISC", "dependencies": { "@0x/subproviders": "^6.4.1", "opensea-js": "^1.1.5" }, "engines": { "node": "^12.18.x"
} }

When i run the script the sdk outputs the following log to console :- Already approved enough currency for trading Order hashes match

but then it always returns the 429 Error: API Error 429: Message: {"detail":"Request was throttled."}

I understand throttling. Why is it that I'm getting the 429 when I have never once called this function successfully. I've most certainly not called it multiple times a second or at any rate to induce throttling limits.. In fact even when I leave it for 24 hrs plus and try again it give me the 429.

I have the correct node version installed as specified in the engines section in the opensea-creatures package.json.

I also have the same node module dependencies as opensea-creatures

"@0x/subproviders": "^6.4.1", "opensea-js": "^1.1.5"

My code to create the OpenSeaPort client is identical to the opensea-creatures script file. Yet it still return 429.

I know all the the code is OK because when I run the same code from a react-app the buy order is placed successfully. But I cannot get it to run from script.

I know that I don't need an API key because the code runs successfully from my react-app.

please help ! I much appreciate the sdk but why the persistent 429?

Also what is the magic combination of latest node and opensea modules that I can use to place a buy order ??

pguardiario
pguardiario

This one should probably get closed since there's no solution other than to slow down.

Activity icon
issue

pguardiario issue comment ProjectOpenSea/opensea-js

pguardiario
pguardiario

seaport.createBuyOrder is not working - returns 429 error every time.

Hi Team

I'm using code from the opensea-creatures project (sell.js) to create an OpenSeaPort instance and call seaport.createBuyOrder()

My Node & npm versions C:\Users\Owner>node -v v12.18.4

C:\Users\Owner>npm -v 6.14.6

Script const {OpenSeaPort,Network} = require('opensea-js') const RPCSubprovider = require('web3-provider-engine/subproviders/rpc') const Web3ProviderEngine = require('web3-provider-engine') const {MnemonicWalletSubprovider} = require('@0x/subproviders'); const accountAddress = "0x2c649A72529FfB801825a52136e0D5C8F171f6Bd" const API_KEY = ""; const NFT_CONTRACT_ADDRESS_SVS = "0x219b8ab790decc32444a6600971c7c3718252539"; const NFT_TOKEN_ID = "3400"; const NETWORK = "mainnet"; const NODE_API_KEY = "e1d6858ba67049bc934a9b764efb9c31"; const isInfura = true;//!!process.env.INFURA_KEY; const MNEMONIC = "My Metamask Mneumonic here"; const BASE_DERIVATION_PATH = 44'/60'/0'/0; const network = NETWORK === "mainnet" || NETWORK === "live" ? "mainnet" : "rinkeby";

const mnemonicWalletSubprovider = new MnemonicWalletSubprovider({ mnemonic: MNEMONIC, baseDerivationPath: BASE_DERIVATION_PATH, });

const infuraRpcSubprovider = new RPCSubprovider({ rpcUrl: isInfura ? "https://" + network + ".infura.io/v3/" + NODE_API_KEY : "https://eth-" + network + ".alchemyapi.io/v2/" + NODE_API_KEY, });

const providerEngine = new Web3ProviderEngine(); providerEngine.addProvider(mnemonicWalletSubprovider); providerEngine.addProvider(infuraRpcSubprovider); providerEngine.start();

const seaport = new OpenSeaPort( providerEngine, { networkName: NETWORK === "mainnet" || NETWORK === "live" ? Network.Main : Network.Rinkeby, apiKey: API_KEY, }, (arg) => console.log(arg) );

placeOffer(NFT_CONTRACT_ADDRESS_SVS, NFT_TOKEN_ID, 0.0000001, Math.round(Date.now() / 1000 + 60 * 3))

async function placeOffer(address, tokenId, price , expirationTime) {
const asset = { tokenId: tokenId, tokenAddress: address, } try{
const makeOffer = await seaport.createBuyOrder({ asset: asset, accountAddress,
startAmount: price, expirationTime })
console.log(Successfully created a offer! ${makeOffer.asset.openseaLink}); } catch(ex) { console.log(ex) }
}

packages.json

{ "name": "newscript", "version": "1.0.0", "description": "", "main": "test.js", "scripts": { "test": "echo "Error: no test specified" && exit 1" }, "author": "", "license": "ISC", "dependencies": { "@0x/subproviders": "^6.4.1", "opensea-js": "^1.1.5" }, "engines": { "node": "^12.18.x"
} }

When i run the script the sdk outputs the following log to console :- Already approved enough currency for trading Order hashes match

but then it always returns the 429 Error: API Error 429: Message: {"detail":"Request was throttled."}

I understand throttling. Why is it that I'm getting the 429 when I have never once called this function successfully. I've most certainly not called it multiple times a second or at any rate to induce throttling limits.. In fact even when I leave it for 24 hrs plus and try again it give me the 429.

I have the correct node version installed as specified in the engines section in the opensea-creatures package.json.

I also have the same node module dependencies as opensea-creatures

"@0x/subproviders": "^6.4.1", "opensea-js": "^1.1.5"

My code to create the OpenSeaPort client is identical to the opensea-creatures script file. Yet it still return 429.

I know all the the code is OK because when I run the same code from a react-app the buy order is placed successfully. But I cannot get it to run from script.

I know that I don't need an API key because the code runs successfully from my react-app.

please help ! I much appreciate the sdk but why the persistent 429?

Also what is the magic combination of latest node and opensea modules that I can use to place a buy order ??

pguardiario
pguardiario

Maybe another device on your network is hitting opensea very fast.

Oct
4
2 weeks ago
Sep
21
3 weeks ago
Activity icon
fork

pguardiario forked ProjectOpenSea/ships-log

⚡ An example dapp listing recent auctions and bids on OpenSea, with the ability to buy items or accept offers right from the page.
pguardiario MIT License Updated
fork time in 3 weeks ago
Sep
20
4 weeks ago
Activity icon
fork

pguardiario forked Ishaan28malik/react-zip-download

⚡ A project to implement multi file zip downloader using Reactjs
pguardiario Updated
fork time in 4 weeks ago
Sep
18
1 month ago
Sep
17
1 month ago
Activity icon
issue

pguardiario issue comment HashLips/generative-art-node

pguardiario
pguardiario

10K editions

is it possible to create 10,000 without the program crashing?

pguardiario
pguardiario

This looks better but instead of

await layers.forEach(async (layer) => {
     await drawLayer(layer, i);
   });

I suggest:

for(let layer of layers){
  await drawLayer(layer, i);
}

That forEach is a HoF and I think there's some confusion about how those work.

Sep
12
1 month ago
started
started time in 1 month ago
started
started time in 1 month ago
started
started time in 1 month ago
Sep
7
1 month ago
Activity icon
issue

pguardiario issue comment HashLips/generative-art-node

pguardiario
pguardiario

10K editions

is it possible to create 10,000 without the program crashing?

pguardiario
pguardiario

The metadata for 10K would be less than 10M so that can't be it. It looks like it's just not waiting for things that are async, It probably needs a major rewrite.

Activity icon
issue

pguardiario issue comment HashLips/generative-art-node

pguardiario
pguardiario

The rarity does not work for me

Is the rarity actually working? Im not good at coding especially Js but if I look through the code I cant see where the superrare is used?

pguardiario
pguardiario

You just put _sr (super rare) or _r (rare) in the image filenames

This alone does not make anything more rare. If you have a layer directory with only one file, even if you label it _sr, every single output image will contain it.

Yes, it only affects the metadata property. To change the math you need to do something in the drawLayer function

Sep
6
1 month ago
Activity icon
issue

pguardiario issue comment HashLips/generative-art-node

pguardiario
pguardiario

The rarity does not work for me

Is the rarity actually working? Im not good at coding especially Js but if I look through the code I cant see where the superrare is used?

pguardiario
pguardiario

I am wondering the same. Is it just for metadata?

Right, the metadata shows up with the correct titles but it doesn't seem to actually make anything more rare. I'm trying to figure out how to code rarity into the program and I'll let you know when I figure it out.

You just put _sr (super rare) or _r (rare) in the image filenames

Jul
30
2 months ago
Activity icon
fork

pguardiario forked snail007/goproxy

⚡ 🔥 Proxy is a high performance HTTP(S) proxies, SOCKS5 proxies,WEBSOCKET, TCP, UDP proxy server implemented by golang. Now, it supports chain-style proxies,nat forwarding in different lan,TCP/UDP port forwarding, SSH forwarding.Proxy是golang实现的高性能http,https,websocket,tcp,socks5代理服务器,支持内网穿透,链式代理,通讯加密,智能HTTP,SOCKS5代理,黑白名单,限速,限流量,限连接数,跨平台,KCP支持,认证API。
pguardiario Updated
fork time in 2 months ago