Skip to content
This repository has been archived by the owner on Mar 23, 2021. It is now read-only.

Error in rbind(deparse.level, ...) : numbers of columns of arguments do not match #37

Open
veskoaleksandrov opened this issue Jul 6, 2016 · 3 comments
Labels

Comments

@veskoaleksandrov
Copy link

Hi Artem,

First and foremost allow me to express my gratitude for all the hard work you put in RGA package - I use it on a daily basis and I am very happy.

Recently upgraded from version 0.3.x to 0.4.2. As part of the upgrade I've changed my code to accommodate for the changes in RGA. Unfortunately I am hitting the wall with following code:

list_experiments(accountId = "aaaaaaaa", webPropertyId = "UA-bbbbbbbb-cc", profileId = "dddddddd")

It returns following error message:

Error in rbind(deparse.level, ...) :
numbers of columns of arguments do not match

Searching for the above error online did not yield helpful results and so I've created a GIT account to report this bug directly.

I am attaching the output of:
httr::with_verbose(list_profiles())
traceback()
sessionInfo()
for your reference.

list_profiles.txt
sessionInfo.txt
traceback.txt

Should you need additional details, please do not hesitate to let me know.

Best,
Vesko

P.S. I followed your advice to test after installing the DEV version but the same issue seems to be present there as well.

@artemklevtsov
Copy link
Owner

artemklevtsov commented Jul 6, 2016

Thank you for the detailed report. Seems I found a reason.
Please post the following output:

token <- RGA::authorize()
path <- sprintf("management/accounts/%s/webproperties/%s/profiles/%s/experiments",
                accountId, webPropertyId, profileId) # paste your IDs
query <- list(start.index = 1, max.results = 10)
url <- RGA:::get_url(path, query)
res <- RGA:::api_request(url, token)
dput(res)

@veskoaleksandrov
Copy link
Author

Here it is: dput.txt

@veskoaleksandrov
Copy link
Author

Hi @artemklevtsov ,

It has been a while since I checked back. I was wondering if you can share any thoughts on whether this bug is going to be resolved in foreseeable future?

Please let me know!

Thanks a bunch,
Vesko

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants