mirror of https://github.com/ByConity/ByConity
fix some typo
This commit is contained in:
yaojun
parent
a7dff2ef35
commit
20435acf85
|
|
@ -13,13 +13,13 @@ Please give us any feedback if you need any help with anything including(and bey
|
|||
|
||||
If anything doesn't make sense, or doesn't work when you run it, please open a bug report and let us know!
|
||||
|
||||
> And if you like ByConity, but just don’t have time to contribute, that’s fine. There are other easy ways to support ByConity and show your appreciation, which we would also be very happy about:
|
||||
> And if you like ByConity, but just don't have time to contribute, that's fine. There are other easy ways to support ByConity and show your appreciation, which we would also be very happy about:
|
||||
|
||||
> - Star the repository ⭐️
|
||||
|
||||
> - Tweet about ByConity 🐦
|
||||
|
||||
> - Refer to ByConity in your project’s readme 🤝
|
||||
> - Refer to ByConity in your project's readme 🤝
|
||||
|
||||
> - Mention ByConity at local meetups, conferences, events and tell your friends/colleagues 🗣️
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ Before you ask a question, it is best to search for existing [Issues](https://gi
|
|||
If you then still feel the need to ask a question and need clarification, we recommend the following:
|
||||
|
||||
- Open an [Issue](https://github.com/ByConity/ByConity/issues/new).
|
||||
- Provide as much context as you can about what you’re running into.
|
||||
- Provide as much context as you can about what you're running into.
|
||||
- Provide project and platform versions, depending on what seems relevant.
|
||||
- Use our [Discord](https://discord.gg/V4BvTWGEQJ) server to reach the community
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ Not everything happens through a GitHub pull request. Please join the community
|
|||
|
||||
#### Before Submitting a Bug Report
|
||||
|
||||
A good bug report shouldn’t leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information, and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
|
||||
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information, and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
|
||||
|
||||
- Make sure that you are using the latest version.
|
||||
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://byconity.github.io/docs/introduction/main-principle-concepts). If you are looking for support, you might want to join our [Discord Server](https://discord.gg/V4BvTWGEQJ) and ask the community.
|
||||
|
|
@ -96,12 +96,12 @@ A good bug report shouldn’t leave others needing to chase you up for more info
|
|||
|
||||
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
|
||||
|
||||
- Open an [Issue](https://github.com/ByConity/ByConity/issues/new). (Since we can’t be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
|
||||
- Open an [Issue](https://github.com/ByConity/ByConity/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
|
||||
- Explain the behavior you would expect and the actual behavior.
|
||||
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports, you should isolate the problem and create a reduced test case.
|
||||
- Provide the information you collected in the previous section.
|
||||
|
||||
Once it’s filed:
|
||||
Once it's filed:
|
||||
|
||||
- The project team will label the issue accordingly.
|
||||
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
|
||||
|
|
@ -116,7 +116,7 @@ This section guides you through submitting an enhancement suggestion for ByConit
|
|||
- Make sure that you are using the latest version.
|
||||
- Read the [documentation](https://byconity.github.io/docs/introduction/main-principle-concepts) carefully and find out if the functionality is already covered, maybe by an individual configuration.
|
||||
- Perform a [search](https://github.com/ByConity/ByConity/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
|
||||
- Find out whether your idea fits with the scope and aims of the project. It’s up to you to make a strong case to convince the project’s developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you’re just targeting a minority of users, consider writing an add-on/plugin library.
|
||||
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
|
||||
|
||||
#### How Do I Submit a Good Enhancement Suggestion?
|
||||
|
||||
|
|
|
|||
|
|
@ -225,7 +225,7 @@ namespace pdqsort_detail {
|
|||
}
|
||||
|
||||
// The following branchless partitioning is derived from "BlockQuicksort: How Branch
|
||||
// Mispredictions don’t affect Quicksort" by Stefan Edelkamp and Armin Weiss.
|
||||
// Mispredictions don't affect Quicksort" by Stefan Edelkamp and Armin Weiss.
|
||||
unsigned char offsets_l_storage[block_size + cacheline_size];
|
||||
unsigned char offsets_r_storage[block_size + cacheline_size];
|
||||
unsigned char* offsets_l = align_cacheline(offsets_l_storage);
|
||||
|
|
|
|||
|
|
@ -277,7 +277,7 @@ endif()
|
|||
|
||||
set (DBMS_COMMON_LIBRARIES)
|
||||
# libgcc_s does not provide an implementation of an atomics library. Instead,
|
||||
# GCC’s libatomic library can be used to supply these when using libgcc_s.
|
||||
# GCC's libatomic library can be used to supply these when using libgcc_s.
|
||||
if ((NOT USE_LIBCXX) AND COMPILER_CLANG AND OS_LINUX)
|
||||
list (APPEND DBMS_COMMON_LIBRARIES atomic)
|
||||
endif()
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ struct LeastBaseImpl
|
|||
{
|
||||
if (!left->getType()->isIntegerTy())
|
||||
{
|
||||
/// Follows the IEEE-754 semantics for minNum, except for handling of signaling NaNs. This match’s the behavior of libc fmin.
|
||||
/// Follows the IEEE-754 semantics for minNum, except for handling of signaling NaNs. This match's the behavior of libc fmin.
|
||||
return b.CreateMinNum(left, right);
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -3489,7 +3489,7 @@ Any `ALTER TABLE ... MODIFY SETTING setting` statements SHALL
|
|||
return an error, unless the user has the **alter settings** privilege for
|
||||
the destination table either because of the explicit grant or through one of
|
||||
the roles assigned to the user. The **alter settings** privilege allows
|
||||
modifying table engine settings. It doesn’t affect settings or server configuration parameters.
|
||||
modifying table engine settings. It doesn't affect settings or server configuration parameters.
|
||||
|
||||
##### RQ.SRS-006.RBAC.Privileges.AlterSettings.Grant
|
||||
version: 1.0
|
||||
|
|
|
|||
|
|
@ -6466,7 +6466,7 @@ RQ_SRS_006_RBAC_Privileges_AlterSettings = Requirement(
|
|||
'return an error, unless the user has the **alter settings** privilege for\n'
|
||||
'the destination table either because of the explicit grant or through one of\n'
|
||||
'the roles assigned to the user. The **alter settings** privilege allows\n'
|
||||
'modifying table engine settings. It doesn’t affect settings or server configuration parameters.\n'
|
||||
'modifying table engine settings. It doesn't affect settings or server configuration parameters.\n'
|
||||
'\n'
|
||||
),
|
||||
link=None,
|
||||
|
|
@ -13469,7 +13469,7 @@ Any `ALTER TABLE ... MODIFY SETTING setting` statements SHALL
|
|||
return an error, unless the user has the **alter settings** privilege for
|
||||
the destination table either because of the explicit grant or through one of
|
||||
the roles assigned to the user. The **alter settings** privilege allows
|
||||
modifying table engine settings. It doesn’t affect settings or server configuration parameters.
|
||||
modifying table engine settings. It doesn't affect settings or server configuration parameters.
|
||||
|
||||
##### RQ.SRS-006.RBAC.Privileges.AlterSettings.Grant
|
||||
version: 1.0
|
||||
|
|
|
|||
Loading…
Reference in New Issue