migrate from Appveyor to GitHub Actions

[StrikerRUS]

Fixed #122.
Appveyor suggests only 1 parallel job at free tier, GitHub Actions - 20.

Should be considered as a continuation of #328. Same changes as for *nix OSes: latest R version; stop producing 32bit artifacts.

[StrikerRUS]

@fukatani Could you please give a second review for this PR?

[fukatani]

LGTM

[StrikerRUS]

Thank you guys for reviews!

@fukatani
Could you please help with new release on PyPI?

@mlampros
Could you please help with new release on CRAN?

[mlampros]

Yes. Can you please point me to what was changed in the code base so that I can adjust the R code? Thanks for the notification.

[StrikerRUS]

I think the only change in R-package was in Python version requirements:
9e558f9#diff-99c1b03acafa469ec3315aee841d2b64f122907ff1ebef7e7be5c793faf5bf0d
cd99ce8#diff-99c1b03acafa469ec3315aee841d2b64f122907ff1ebef7e7be5c793faf5bf0d

I don't think any code adjustments are needed because all R tests are passed in the latest master branch.

If you think that requirements in Python version is too minor to have new release on CRAN, feel free to skip it.

[mlampros]

I think the drop of support for Python 2.7 (version) has to be added in the DESCRIPTION file of the CRAN package. I'll submit the updated version tomorrow to CRAN and I'll notify you once I received the approval.

[StrikerRUS]

Hey @mlampros !
Are there any problems with CRAN acceptance? Now I'm familiar a little bit with CRAN and can help you in case of any additional requests from CRAN administration.

[mlampros]

Hi, @StrikerRUS thanks for asking.

I had indeed a bunch of problems when submitting the package:

The problems were related with a namespace error as is also discussed in this issue and appeared mainly in the Windows version (I received 2 NOTES compared to the last submission of the package). It took me a while (I think 5 or 6 submissions) to figure out that it was related with the package.R file only and not with the tests, however it seems that it might be a good practice to not run the tests on CRAN . Finally, I ended up removing the initialization of Python from the .onload() function.

Anyway, now it works for all operating systems, however CRAN included lately tests also for M1mac (Checks on a M1 (arm64) Mac). I think I fixed the error by adjusting a lot of code in the tests and examples section but currently it's not a requirement for a successful submission to CRAN (probably it's in a testing phase).

I had to reply that I fixed the errors and now I'm awaiting for a response from the CRAN personnel. Once I receive the confirmation I'll make a pull request by uploading the new version.

[StrikerRUS]

@mlampros Thank you very much for the detailed report!

Anyway, now it works for all operating systems

Great! Thank you!

however CRAN included lately tests also for M1mac (Checks on a M1 (arm64) Mac). I think I fixed the error by adjusting a lot of code in the tests and examples section but currently it's not a requirement for a successful submission to CRAN (probably it's in a testing phase).

Yeah, I think this is beta test when CRAN picks up projects randomly and runs tests for them. For example, there is no M1mac point in the results for LightGBM: https://cran.r-project.org/web/checks/check_results_lightgbm.html.
I see the error is in scipy.sparse-related tests

  ══ Failed tests ════════════════════════════════════════════════════════════════
  ── Error (test-RGF_package.R:265:3): the 'mat_2scipy_sparse' returns a scipy sparse matrix ──
  Error: attempt to apply non-function
  Backtrace:
      █
   1. └─RGF::mat_2scipy_sparse(x_rgf, format = "sparse_row_matrix") test-RGF_package.R:265:2

I remember you told that there are some problems with reticulate integration with scipy.sparse on macOS. Maybe it is enough just to adjust the following condition?

rgf/R-package/tests/testthat/test-RGF_package.R

Lines 303 to 308 in f740790

	if (Sys.info()["sysname"] != 'Darwin') {
	# conversion of an R 'dgCMatrix' and 'dgRMatrix' to a scipy sparse matrices
	#--------------------------------------------------------------------------
	testthat::test_that("the 'TO_scipy_sparse' returns an error in case that the input object is not of type 'dgCMatrix' or 'dgRMatrix'", {

[StrikerRUS]

Kindly ping @fukatani for a new PyPI release.

[StrikerRUS]

@fukatani CRAN release has been published recently: #340 (comment). Please help with PyPI one to sync packages (Python 3.9 support, removed Python 2.7 support, compatibility with new scikit-learn, etc.).

[StrikerRUS]

@fukatani If you'd like, I can take the responsibility to make releases on PyPI. My nickname there is the same as on GitHub.

[fukatani]

@StrikerRUS
Sorry for late response.
Unfortunately, my OSS contribution is inactive in current.
I am grateful for the contributions of you and mlampros.

I'm investigating how to transfer PyPI authority.

[StrikerRUS]

@fukatani

Unfortunately, my OSS contribution is inactive in current.

Totally undestand!

I'm investigating how to transfer PyPI authority.

No need to transfer, you can simply invite me to collaborate and I'll be able to upload new releases.

Go to "Your projects" at PyPI site: https://pypi.org/manage/projects/.

Click "Manage" button for the rgf-python project.

Select "Collaborators" tab at the left side of the page.

Scroll down to the "Invite collaborator" section.

My "Username" there is the same as at GitHub.

[fukatani]

@StrikerRUS
Thx!
I invited you as maintainer.
Could you confirm it?

[StrikerRUS]

@fukatani Thank you so so much! Just accented your invite. Will try to upload new release in a few days.

[StrikerRUS]

New release is out!