DEV Community: Jason

Release0.4 - Release

Jason — Sat, 11 Dec 2021 01:59:35 +0000

The issues 2519 has completed, and it closed by PR 2556. The issue 2542 has completed, and it is being reviewed by PR 2562. I also reviewed two PR 2543 and 2582.

Issue 2519

At the beginning, I edit the windows size.

const width = window.innerWidth;
const height = window.innerHeight;

It is work, but it duplicates what we already have with https://www.npmjs.com/package/xterm-addon-fit. The right way to do this is to have the parent element that holds the terminal fill the available width and height, and then it will automatically use that. So I , I will try to fix CSS. I used the following code, and the windows size looks good, but The terminal shouldn't display the text on many lines, and it has glitchy text instead.

.xterm {
  padding: 0.5rem;
  position: fixed;
  width: 100%;
  height: 89%;
}

I use vh instead of % and the issue fixed.

.xterm {
  padding: 0.5rem;
  position: relative;
  width: 100vh;
  height: 89vh;
}

However there are two lines doesn't seem to be necessary. It is optimized to solve this problem with only one line of code. Please refer to the PR 2556.

Issue 2542

This issue has almost done a part of it is being fixed some issue.
We can check the code of PR 2562.
I add the following code in the src/api/status/src/views/builds.hbs file. If the build done, hide loading and error and show success. if it is loading hide error, success, and show loading. If it has error, hide loading, success, and show error.

<div class="container-fluid py-2">
    <div class="table-responsive">
      <div class="row mb-2">
        <div class="col col-md-1 text-xs">status</div>
        <div class="col col-md-2 text-xs">Build in progress</div>
      </div>
      <div class="row">
        <div class="col text-sm">
          <div class="align-center">
            <span hidden id="build-loading" class="material-icons fa-spin fa-9x " style="font-size: 24px; color:rgb(255, 196, 0) !important" >motion_photos_on</span>
            <span  hidden id="build-success" class="material-icons"  style="font-size: 22px; color:green">check_circle</span>
            <span hidden id="build-fail" class="material-icons" style="font-size: 23px; color:red">cancel</span>
            <span id="calculatorData" style="float: center; color:blue" ></span>
          </div>
        </div>   
      </div>
    </div>
  </div>

The following code is datetime-calculator, and it decide which icon will be hidden.

const buildDateCaltulator = document.getElementById('calculatorData');
const buildLoading = document.getElementById('build-loading');
const buildSuccess = document.getElementById('build-success');
const buildFail = document.getElementById('build-fail');

export default function calculatorBuildInfo(data) {
  const startedAtValue = data.startedAt;
  const stoppedAtValue = data.stoppedAt;
  const resultValue = data.result;

  if (startedAtValue !== 'null' && stoppedAtValue === 'null') {
    const date = Math.abs((new Date(startedAtValue).getTime() / 1000).toFixed(0));
    const currentDate = Math.abs((new Date().getTime() / 1000).toFixed(0));
    const diff = currentDate - date;
    const hours = Math.floor(diff / 3600) % 24;
    const minutes = Math.floor(diff / 60) % 60;
    const seconds = diff % 60;
    buildDateCaltulator.innerText = `${hours} h ${minutes} m ${seconds} s`;
    buildFail.hidden = true;
    buildSuccess.hidden = true;
    buildLoading.hidden = false;
  } else if (resultValue === 0 && stoppedAtValue !== 'null') {
    const date = Math.abs((new Date(startedAtValue).getTime() / 1000).toFixed(0));
    const currentDate = Math.abs((new Date(stoppedAtValue).getTime() / 1000).toFixed(0));
    const diff = currentDate - date;
    const hours = Math.floor(diff / 3600) % 24;
    const minutes = Math.floor(diff / 60) % 60;
    const seconds = diff % 60;
    buildDateCaltulator.innerText = `${hours} h ${minutes} m ${seconds} s`;
    buildLoading.hidden = true;
    buildFail.hidden = true;
    buildSuccess.hidden = false;
  } else if (resultValue !== 0 && stoppedAtValue !== 'null') {
    const date = Math.abs((new Date(startedAtValue).getTime() / 1000).toFixed(0));
    const currentDate = Math.abs((new Date(stoppedAtValue).getTime() / 1000).toFixed(0));
    const diff = currentDate - date;
    const hours = Math.floor(diff / 3600) % 24;
    const minutes = Math.floor(diff / 60) % 60;
    const seconds = diff % 60;
    buildDateCaltulator.innerText = `${hours} h ${minutes} m ${seconds} s`;
    buildLoading.hidden = true;
    buildSuccess.hidden = true;
    buildFail.hidden = false;
  }
}

The following code can connect the above two documents:

Review PR 2543 and 2582.

I retest the PR 2543 and provide my suggestion.

I also retest the PR 2582, and the provide the following review comment:

What did I learn from OSD600

I improved my soft skill of networking and collaborating with community members. I mastered Slack, Dev and Discord.
I learned lots of knowledge about GitHub including forking, cloning, creating branch, creating pull request and so on. I also mastered some command, for instance, checkout, rebase, remote, merge, pull, push, fetch and so on.
I handed on the Markdown language.
I learned some feature about Docusaurus, and I have saved some skill which I noted using Docusaurus.
I learned how to apply Black to format Python code; how to apply a linter - Flake8, how to integrate my project.
I learned how to use Pytest to create test case and test my SSG.
I learned how to use PyPI to package and release SSG.
I learned lots of skills about Python, JS, CSS and other languages.

Release 0.4 Progress

Jason — Mon, 06 Dec 2021 02:07:07 +0000

The two issues 2519, and 2542 were both partially completed this week.

Issue 2519

I think the terminal port can't auto fit the height because the Browser can't get the size of the container. So I edit the terminal.js file and get the window's width and height, then calculate the row height and column width based on these data.
If the user has more than one screen, just refresh the screen, the terminal window will fit the new screen. The issue solved and I pull the request 2556.

However, the professor thinks it duplicates what we already have with https://www.npmjs.com/package/xterm-addon-fit. The right way to do this is to have the parent element that holds the terminal fill the available width and height, and then it will automatically use that. So I will fix my CSS for the page so that it does this.

Issue 2542

I want to do this issue by four steps.

1.An animated indication shows a build is happening.
2.The animated indicator shows the percentage being built.
3.The indicator shows how long it's been going for.
4.When it's done, the yellow animated circle becomes a green checkmark or a red ' X'.
I have done the first two steps, and the result video looks good. I edited two files and added the following code:

* {
  margin: 0;
  padding: 0;
  font-family: sans-serif;
}
.box {
  position: relative;
  height: 50px;
  width: 250px;
  background: transparent;
  border-radius: 5px;
}
.box svg {
  position: absolute;
  height: 160px;
  width: 160px;
  left: 25%;
  top: 50%;
  transform: translate(-50%, -50%) rotate(-90deg);
}
.box svg circle {
  fill: transparent;
  stroke: #ff0;
  stroke-width: 3;
  stroke-dasharray: 500;
  stroke-dashoffset: 500;
  stroke-linecap: round;
  animation: stroke 28s steps(500) forwards;
}
.box .counter {
  position: absolute;
  top: 60%;
  left: 25%;
  transform: translate(-50%, -50%);
  width: 70%;
  height: 30px;
  color: #e6b800;
  text-align: center;
  overflow: hidden;
}
.box .counter span {
  font-size: 10px;
  line-height: 25px;
  font-weight: bold;
  /* text-align: center; */
}
.box .counter span:after {
  content: '0%\A 1%\A 2%\A 3%\A 4%\A 5%\A 6%\A 7%\A 8%\A 9%\A 10%\A 11%\A 12%\A 13%\A 14%\A 15%\A 16%\A 17%\A 18%\A 19%\A 20%\A 21%\A 22%\A 23%\A 24%\A 25%\A 26%\A 27%\A 28%\A 29%\A 30%\A 31%\A 32%\A 33%\A 34%\A 35%\A 36%\A 37%\A 38%\A 39%\A 40%\A 41%\A 42%\A 43%\A 44%\A 45%\A 46%\A 47%\A 48%\A 49%\A 50%\A 51%\A 52%\A 53%\A 54%\A 55%\A 56%\A 57%\A 58%\A 59%\A 60%\A 61%\A 62%\A 63%\A 64%\A 65%\A 66%\A 67%\A 68%\A 69%\A 70%\A 71%\A 72%\A 73%\A 74%\A 75%\A 76%\A 77%\A 78%\A 79%\A 80%\A 81%\A 82%\A 83%\A 84%\A 85%\A 86%\A 87%\A 88%\A 89%\A 90%\A 91%\A 92%\A 93%\A 94%\A 95%\A 96%\A 97%\A 98%\A 99%\A 100% ';
  position: absolute;
  white-space: pre;
  left: 50%;
  transform: translateX(-50%);
  animation: animate 10s steps(100) forwards;
}
h8 {
  color: #000;
  position: absolute;
  width: 100%;
  text-align: center;
  top: 25%;
  right: 2%;
  letter-spacing: 1px;
}
@keyframes animate {
  0% {
    top: 0%;
  }
  100% {
    top: -5000px;
  }
}
@keyframes stroke {
  100% {
    stroke-dashoffset: 0;
  }
}

The professor's opinion is that we can't use a % since we don't have any concept of where we are in a build, and we know when a build started (Datetime) and therefore can calculate how long it's been running, so we could do something like 1m 15s, yes.
I will modify the code according to the professor's suggestion.

Release 0.4 Planning

Jason — Mon, 06 Dec 2021 01:13:22 +0000

I plan to work on Seneca-CDOT/telescope.Thare are some issues that inside my comfort zone and the difficulty also meets the requirements. In addition, I intend to continue to contribute to this project after this semester. I chose two issues, one the issue 2519, and another is 2542.

Issue 2519

The issue is about "Extend build terminal in dashboard to full height of viewport". The build terminal is only occupying the top portion of the page and the owner wish it extend to fill the available space vertically.

Issue 2542

The issue is about "Indicate a build is in progress in Dashboard build page". When go to a build in GitHub Actions, the user can see an animated indication that a build is happening, and how long its been going for:

When it's done, the yellow animated circle becomes a green check mark or a red "X".

Release 0.3 code review

Jason — Tue, 30 Nov 2021 21:29:03 +0000

1. I reviewed the IPC144 Issue 124 - Build PDF in deployment and include when we publish to GH-Pages.
I checked the docusaurus-config optional fields, it seems no field support downloading the document directly if you use the links: [ {items:}]. I suggest that create a new file, e.g. the name is Seneca-IPC144-download.md. Then, fill in a back-end interface for downloading files on this page, e.g. https://codeload.github.com/douban/douban-client/legacy.zip/master.

var $btn = $("#btn");

//A back-end interface for downloading files is known:
https://codeload.github.com/douban/douban-client/legacy.zip/master

$btn.click(function(){
    window.open("https://codeload.github.com/douban/douban-client/legacy.zip/master");
});

After that, in the docusaurus.config.js file, use the following code that can navigate to the download page.

items: [
        {
            label: 'Download',
            to: '/Seneca-IPC144-download',
         },
          ],

2. I reviewed another issue-ASCII Collating Sequence image converted into Table

I have two suggestions, the first is that at the end of line 47, the table should display " | ", but it is blank.
The second is the page didn't display a subtitle compared with the IPC144 old version.

Release0.3 Seneca-ICTOER/IPC144 -Audit & fix Information.md

Jason — Tue, 30 Nov 2021 03:21:05 +0000

I'm responsible for fixing the Information.md page, and the following six issues were fixed:

1. Fixed images work in dark modes. The memory model image's downward arrows and the letter in the bottom right corner are not clear in dark modes. I wrapping them in a tag and adding class "mdImg" to it.
2. The images can't display in all models. Change all the image path from "/img/.jpg" to "../../static/img/.jpg". The issue is fixed.
3. Fix Frontmatter for the page to include id, title, slug, and description.
4. Replace blockquote with Admonitions for clarity.
5. Added alt text for diagram images.
6. Some of " * "will get converted into _ after being formatted with Prettier. I use "\ *" replace them.

How to fix the code

Tips about merging commits

The challenge of this project is about how to merge all commits to one. I failed many times and I have to close the PR and recreate a new one. There are some tips about the issue.

Don’t use git add . because it will often add files you don’t intend, and then you get into a mess when you have to remove them and don’t know how. Instead, use: git add file1 file2 dir1 dir2 Specify the files/folders by name. It will save you making mistakes.
If you’re going to rebase onto main, you need to do this first:

git checkout main git pull upstream main git checkout issue-44 git rebase -i main
There’s no reason to pull from my origin/issue-44 because I made all these commits. Unless I merged something into my fork, which is unlikely.
Don’t do this: git pull origin main, then merge it to issue-44. First, I need to checkout main and pull from the upstream, not my origin.
Use git reflog, check here for more information. Revert your squashed commit by using git reset — hard , make changes, rebase and push it to issue-44 again. Before doing this, you can checkout a new branch to be extra safe.
If the added files are still in staging. For example, .gitignore and yarn.lock staged in git. Use restore --staged to unstage them, use git checkout issue044 to rollback their content. Then use git add for files that you are meant to change, in this case only docs/A-Introduction/information.md and maybe files in static/img. Rebase it and force push.

Release0.3 Using PyParing lib in mindsdb

Jason — Tue, 30 Nov 2021 02:32:20 +0000

MindsDB is a predictive platform that makes databases intelligent and machine learning easy to use. It allows data analysts to build and visualize forecasts in BI dashboards without going through the complexity of ML pipelines, all through SQL. It also helps data scientists to streamline MLOps by providing advanced instruments for in-database machine learning and optimize ML workflows through a declarative JSON-AI syntax.
I did 3 issues of this project, 1773 and 1771 have merged, and 1777 had approved.

PR 1773 and PR1771 review

These two issues are easy to fix, but it can help me understand the program as soon as possible and let me establish good communication with the project owner.
The first issue need to find the integrations table file, and remove the supported integrations table.

The second issue is that rename two sections from the left navigation menu.

PR1777 review

The issue is that if the user adds the space in the integration name, the app isn't able to parse that for e.g My SQL

mysql> CREATE PREDICTOR home_rentals_model FROM `My SQL`(SELECT * from test_data.home_rentals)  PREDICT rental_price;
ERROR 1149 (HY000): Expected "PREDICT" (at char 45), (line:1, col:46)
mysql>

At the beginning, I think the issue is from the interface, and I just need to remove the white space. Then I used the following code to deal with the issue.

After communicating with the project owner, I know that the interface changes affect only 'integration', ie when you work with MindsDB from your database (not via direct connection to MindsDB). In original issue error had raise in 'create predictor' query, which cant be used with such connection. The issue is parser error, probably it does not understand back quote symbols.
I searched for some information about pyparser and the pyparser can't understand backquotes as you said. Then I checked some methods about how to identify backquotes, probably two methods. One is to use backslash + backquote, and the other is to use repr (). I use the backslash +backquote method in this PR.

What I learned

The pyparsing module is an alternative approach to creating and executing simple grammars, vs. the traditional lex/yacc approach, or the use of regular expressions. The pyparsing module provides a library of classes that client code uses to construct the grammar directly in Python code. There are lots of functions, and I am learning them.

Lab10 Packaging and Releasing SSG

Jason — Sat, 27 Nov 2021 20:36:37 +0000

Lab10 will focus on packaging and releasing my own SSG project and getting our code into the hands of users. I use the PyPI to do it.

How to set up

I followed the instruction to finish all the steps.
First, I need to change the directory structure before I package SSG. I create a new directory named src/. When importing the package, Python searches through the directories on sys.path looking for the package subdirectory. I also need to update import information of all files.
Second, I creat a new file named _init_.py. The _init_.py files is required to import the directory as a package, and should be empty.

Third, edit the exist pyproject.toml file which tells build tools (like pip and build) what is required to build your project.

[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"

Forth, configuring metadata. There are two types of metadata: static and dynamic. I use the static metadata because it is simpler, easier to read, and avoids many common errors. setup.cfg is the configuration file for setuptools. It tells setuptools about your package (such as the name and version) as well as which code files to include. Eventually much of this configuration may be able to move to pyproject.toml.

[metadata]
name = magic-ssg
version = 0.9.1
author = Tengzhen Zhao
author_email = tzhao16@myseneca.com
description = A simple Static Site Generator tool, and it can help you to generate .html from .txt and .md files. 
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/Yoda-Canada/Magic-SSG
project_urls =
    Bug Tracker = https://github.com/Yoda-Canada/Magic-SSG/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.8.5

[options.packages.find]
where = src

Fifth, Now run this command from the same directory where pyproject.toml is located. Then register an account using this register page

py -m pip install --upgrade build
py -m build

py -m pip install --upgrade twine
py -m twine upload --repository testpypi dist/*

Sixth, after registered, I use twine to upload the distribution packages and install Twine. Once installed, run Twine to upload all of the archives under dist.

py -m pip install --upgrade twine
py -m twine upload --repository testpypi dist/*

The magic-ssg 1.0.0 upload to the PyPI successfully.

Testing

Former students of OSD600 helped me to test the installation of this software. The installation went smoothly and there was no problem running.

Reflection

I learned how to control the version and how to package and publish the program. I know how the version number is constantly updated, which is helpful for my future to develop a project.

Lab9 Continuous Integration Pipelines and Test Automation

Jason — Sat, 20 Nov 2021 02:30:49 +0000

This week I focused on managing project complexity through the use of Continuous Integration Pipelines and Test Automation. CI is a method whereby we build and run our tests automatically whenever anything is pushed to the repo, or a new pull request is made.

How to create a GitHub Actions Workflow

The video Running Tests through CI is very help and I followed the steps to create my first GitHub Actions Workflow. GitHub provides its own CL service called GitHub Action and we just need to click "Actions" tab. I choose the Python - Anacondas template into my project. Then I follow the instruction to configure the python-package-conda.yml file. Most of items are auto generated, only apart of them need to edit. For example, add the push and pull request action, and also edit the install dependencies.

Create a Pull Request to Test my CI

I create a new branch named lab9, and add a new file named test_md_txt_title.py. After all function passed, I push the branch to the remote and pull a new PR. After GitHub Action passed the PR, I merged it.

Add Tests to Partner Project

According to my parter's issue, I create a new test file named. I pull a new PR, the partner's Actions passed it.

Before that, I found that many projects have the function of automatic error checking. I wonder how to do it. After lab9, I also created my own GitHub actions. I'm very excited.

Lab8 Manage project complexity through the use of Automated Testing

Jason — Sat, 13 Nov 2021 23:11:45 +0000

The Lab8 are focused on managing project complexity through the use of Automated Testing. There are three frequently used framework for Python: Unittest, Nose and Pytest. Unittest has an associated module unittest2, but unittest2 is only applicable to Python 2.4-2.6. Nose has entered the maintenance mode. It can be seen from GitHub nose that the latest code submission of nose was on May 4, 2016. Nose2 inherits nose, but it should be noted that nose2 does not support all the functions of nose. Pytest's purpose is to make unit testing easier, and it can also be extended to support complex functional testing at the application level. Unlike unittest / nose, pytest can be used not only for unit testing, but also for higher-level, application-oriented functional testing. Therefore, if a higher level of testing is required, pytest is suitable. So I choose Pytest to test my project.

How to install

Run the following command in your command line:

pip install -U pytest

Check that you installed the correct version:

pytest --version

How to build directory tree

To get started writing tests, I need to simply create a folder named tests, which will contain test cases. Create an empty file called __init__.py in both tests folder and it's subfolder. Creating the __init__.py file means that the tests folder can be imported as a module from the parent directory. So my directory tree will look something like this:

How to write test case

In the assiLib.py has a function named get_txt_title. The function will specify if the article has title. If the first three lines have 2 blank lines and one non comment line, the function will take the non comment line as the title. I want to test it and separate it to 5 test cases. the first case is the title in the first line; the second is the title in the second line and it is centered; the third is the title in the Third line; the forth is the first line is the comment line; the fifth is the first line is the first sentence of the first paragraph.

When I run the test file, there are four passed and one failed. The failed case isn't a bug, it is an function need to be enhanced.

How to install Pytest-watch

What if you are working on a particular file/function, and want to run a single test over and over again while you fix a bug? There is a zero-config CLI tool that runs pytest, and re-runs it when a file in your project changes. It beeps on failures and can run arbitrary commands on each passing and failing test run. You can install it using the following command.

$ pip install pytest-watch You can run it using the every simple command in under the root directory.
$ ptw

How to install Pytest-cov

This plugin produces coverage reports. Compared to just using coverage run this plugin does some extras:

Subprocess support: you can fork or run stuff in a subprocess and will get covered without any fuss.
Xdist support: you can use all of pytest-xdist's features and still get coverage.
Consistent pytest behavior. If you run coverage run -m pytest you will have slightly different sys.path (CWD will be in it, unlike when running pytest).

Install it with pip:

pip install pytest-cov Usage:
pytest --cov=MAGIC-SSG tests/

Conclusion

I am looking for a job of automation tester. The lab8 is very helpful for me to interview the automation tester position.

Lab 7 Use Static Analysis tooling to manage project

Jason — Fri, 05 Nov 2021 21:31:10 +0000

Lab 7 focused on managing project complexity through the use of Static Analysis tooling. My project use Python, so I run with Python Black and Flake8.

How to apply Black to format Python code

      Black is the uncompromising Python code formatter and it is easy to install and to use. So I can save time and mental energy for more important matters.
      Black can be installed by running: pip install black
      Easy to run with: black {source_file_or_directory} or python -m black {source_file_or_directory}

Black supports configurations and will look for configuration starting from the current working directory. By default Black looks for pyproject.toml starting from the common base directory of all files and directories passed on the command line. The pyproject.toml contains separate sections for different tools and Black is using the [tool.black] section.
After run Black, there are 2 files reformateed. One is to use double quotation marks instead of single quotation marks, and another is formatted multiple parameters in a row into multiple rows. After formatting, my code is really easier to read

How to apply a linter - Flake8

      Flake8 is a tool officially released by Python to help detect whether Python code is standardized. Compared with pylin, which is popular at present, flake8 has flexible inspection rules, supports the integration of additional plug-ins and has strong expansibility.
      Flake 8 can be installed by running: python -m pip install flake8
      Easy to run with: flake8 path/to/code/to/check.py or flake8 path/to/code/
      After run Flake8, there are W605, E501, E541 issues.
       1. Issue W605 is about invalid escape sequence. I solved this issue by adding "r" at the beginning of the regular expression.
       2. Issue W501 is about line too long(80>79 characters). I create a ".flake8" file, and add a command max-line-length = 90, then the issue solved.
       3. Issue F541 is about f-string is missing placeholders. I solved this issue by add ad placeholder {args.config}.

Intergration

How to create one-step solution

I create a new file named check.sh to provide one-step solution that use a shell script to execute the Black and flake8.

How to integrate the 2 extensions into .vscode

Create User and Workspace settings, and add "black" to the .vscode/settings.json.
Repeat step 1 and integrate all extensions into the json file.

Pre-commit hook

Git hook scripts are useful for identifying simple issues before submission to code review.

Before you can run hooks, you need to have the pre-commit package manager installed: pip install pre-commit
Add a pre-commit configuration. I create a file named .pre-commit-config.yaml and generate a very basic configuration using pre-commit sample-config.
Install the git hook scripts. I run pre-commit install to set up the git hook scripts. Now pre-commit will run automatically on git commit!
Add Black and Flake8 into the pre-commit file.

Reflection

I used to read the project on GitHub. There are many files that I don't understand what their purpose is. After I complete the lab7, I understand most of them， for instance .vscode, .pre-commit-config.yaml, contributting.md, pyproject.toml and so on.

Release0.2 week four

Jason — Fri, 29 Oct 2021 03:06:08 +0000

The difficulty of this project is to be fast. The owner don't assign the issue to anyone and he only accept and merge the first PR that fixes correctly and well implements the issue following our contributing guidelines. So I must understand the project and the issue ASAP. At the same time, I have to upload the PR fist.

About the project

MeiliSearch is a powerful, fast, open-source, easy to use and deploy search engine. Both searching and indexing are highly customizable. Features such as typo-tolerance, filters, and synonyms are provided out-of-the-box.

About the issue

In the API Reference, the examples for the distinct attributes are introduced with movie_id which is the primary key of the index. The MeiliSearch hits are always distinct according to the unique identifier: so the primary key is the only attribute you will never put as a distinct attribute. It does not help to understand the purpose of a distinct attribute. The issue would like to apply some changes in the .code-samples.meilisearch.yaml file at the root of the repository

How to do

First, Look for the get_distinct_attribute_1, update_distinct_attribute_1 and reset_distinct_attribute_1 in the .code-samples.meilisearch.yaml file, then change the index parameter from 'movies' to 'shoes'.

Second, Find the update_distinct_attribute_1 in the in the .code-samples.meilisearch.yaml file, then change the from "movie_id" to 'skuid'

Reflection

The ability to read and understand code structures and issue is very important because the owner only accept and merge the first PR that fixes correctly and well implements the issue following our contributing guidelines. In the future, I must improve my reading comprehension speed.

Release0.2 week three

Jason — Fri, 29 Oct 2021 01:52:19 +0000

This project is very challenging because I need to know some knowledge about Algorithms. The project named Fliscopt, and it is a simple optimization library for flight scheduling and related problems in the discrete domain. The library supports plotting, asynchronous multiprocessing, and unimodal optimization benchmarks.

The issue

The issue need to add error message for failed unittests. A message indicating a failure for each unit-test, should give the user a small idea of what went wrong in the test. ex:self.assertEqual ( f(values), 0, msg ='HEURISTIC MESSAGE INDICATING WHY TEST CASE FAILED')

How to do

First, understand the testing structure and find the files which need to add error messages. I learned some automation testing knowledge and all test files saved in the tests folder. The run_pypy-tests.sh and run_tests.sh files implement automated testing! The test_algorithms.py, test_chaining.py and test_fitness.py need to add error messages.
Second, learned the algorithms and decided how to write the error message. This project has about a dozen algorithms, and they have different dimensions, input domain and global minimum. Here are three-dimensional images of several functions.

Three, according to different dimensions, input domain， global minimum and the different positions of the matrix, try to write a draft of the wrong information. Complete the task after repeated discussion and confirmation with the owner.

Reflection

I learned some methods to write automation test code. I can try to do the automation testing work in the future.
Learned some knowledge about some functions of the algorithm. Although the task was difficult, I was successfully completed through communication with the owner.