Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added workflow to update current-version-tag in README.md #1083

Closed
wants to merge 8 commits into from

Conversation

thebadcoder96
Copy link

Will fix #972

As discussed earlier, I have reopened this as a new PR so it can be CLA complaint.

menglinw and others added 7 commits December 12, 2023 08:59
* parquet sampling function developed in data_utils.py; Added sample_nrows argument in ParquetData class; Added test_len_sampled_data in test_parquet_data.py

* resolved conflict with dev, added more tests

* fixed sample empty column bug

* fixed comments in data_utils.py, including:
1. added type of return in sample_parquet function;
2. changed variable names in sample_parquet function to more descriptive names (select -> sample_index, out -> sample_df);
3. created convert_unicode_col_to_utf8 function to reduce repeating code in sample_parquet and read_parquet_df functions

* 1. renamed variable names in covert_unicode_col_to_utf8 function (data_utils.py) to be more descriptive (types -> input_column_types, col -> iter_column), other part unchanged

2. test_parquet_data.py, move import statement to the top of file

3. test_parquet_data.py, merged all tests about parquet sample feature to their original tests

* checked the datatype and input file path before and after reload with sampling option enabled

* test

* delete test edit in avro_data.py, updated fastavro version in  requirment.txt

* remove fastavro.reader type

* change fastavro version back to original

* 1. sample_parquet function description
2. test_len_data method keep one sample length test
3. remove sampling test in test_specifying_data_type
4. remove sampling test in test_reload_data
* bump tag matplotlib

* bumpt to most recent

* 3.9.0 update
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v4...v5)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Taylor Turner <taylorfturner@gmail.com>
Co-authored-by: Taylor Turner <taylorfturner@gmail.com>
@thebadcoder96 thebadcoder96 requested a review from a team as a code owner January 11, 2024 16:29
@taylorfturner taylorfturner changed the base branch from old-old-old-dev to dev January 11, 2024 18:17
Comment on lines +24 to +27
git config --local user.email "mishalksa@hotmail.com"
git config --local user.name "GitHub Action"
git commit -am "Update README with latest version tag"
git push
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm -- nifty what you did here but this creates a situation where each commit that fixes this is tagged to your account, which potentially isn't very robust long-term

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not something that is production-ready per se

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could create a dummy account and sign the cla. Do you have any ideas on how to make it more robust?

@taylorfturner
Copy link
Contributor

@thebadcoder96 any more thoughts on potential fix here?

@taylorfturner taylorfturner changed the base branch from old-old-dev to dev March 7, 2024 13:03
@taylorfturner
Copy link
Contributor

Closing after no activity for over a month. Can re-open.

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

Successfully merging this pull request may close these issues.

4 participants