Service can start app after startup

@patrickxb @maxtaco
This change makes it so the service starts the app. Adding an AppStartMode config so it can be disabled.
This gives us more control over app startup.

Just so I understand what this does:
Unless one sets app_start_mode="disabled" (or anything but service) in config.json, when the service starts up on OS X it will try to launch the desktop app?
So if an OS X user reboots, the desktop app will be started by the service?
Is that why we need this?
Sorry for all the questions, just trying to understand the context.

yeah... this has a bunch of benefits in that it gives us more control over the app starting and we can do on demand app starting too
Also fixes an issue: https://keybase.atlassian.net/browse/DESKTOP-513

LGTM


feat(contract-standards): Adding near-contract-standards library and more tools

near-contract-standards is a library with implementations of contract standards.
Additional tools include testing and implementation tools that reduce contract code and tests size by 2x.
Also added env::storage_byte_code() which right now returns a constant but in the future will be switched to return current storage cost from environment.
Fixes #254

It looks like we should lock our inter-connected crate versions by using =3.0.0-pre.1, otherwise the higher version overwrites the dependency. This usually doesn't happen, but may break some stuff if someone relies on near-sdk = =3.0.0 and we public near-sdk-core with 3.1.0, then their near-sdk create will depend on near-sdk-core = 3.1.0, which it shouldn't
But because the previous version was published under 3.0.0-pre-release, it overwrites 3.0.0-pre.1 for some alphabetical reason.
Just published near-contract-standards v0.1.0-pre.1 and near-sdk v3.0.0-pre.2

For instance, when I try to use the macro in a public function, it'll break:
#[near_bindgen]
impl Contract {
    …

    pub fn add_metadata_symbol(&mut self, symbol: String) { //} -> FungibleTokenMetadata {
        near_contract_standards::impl_fungible_token_metadata!(
            Contract,
            String::from("1.0.0"),
            String::from("Example NEAR fungible token"),
            symbol,
            String::from("https://github.com/near/near-sdk-rs/tree/master/examples/fungible-token"),
            24
        );
    }
}

near_contract_standards::impl_fungible_token_core!(
    Contract,
    token
);

I get:
error[E0434]: can't capture dynamic environment in a fn item
  --> /Users/mike/near/near-sdk-rs/near-contract-standards/src/fungible_token/macros.rs:61:9
   |
61 |         #[near_bindgen]
   |         ^^^^^^^^^^^^^^^
   |
   = help: use the `|| { ... }` closure form instead

@mfornet and @djsatok for your info, this is where we're at. An example of a mint function looks like this after some cursory testing:
#[near_bindgen]
impl Contract {

    …

    #[payable]
    pub fn mint(&mut self, account_id: ValidAccountId, amount: U128) {
        let deposit = env::attached_deposit();
        if let Some(account_balance) = self.token.accounts.get(&account_id.as_ref()) {
            // Add balance to the account, return deposit
            Promise::new(env::predecessor_account_id()).transfer(deposit);
            let new_balance = account_balance.saturating_add(amount.0);
            self.token.accounts.insert(&account_id.as_ref(), &new_balance);
        } else {
            // Insert the account, use the deposit for storage
            self.token.storage_deposit(Option::from(account_id.clone()));
            self.token.accounts.insert(&account_id.as_ref(), &amount.0);
        }
    }
}

Hm.... How does one put the hash of the contract (code) into the contract itself?

@ilblackdragon I think you need it to be part of the initialization.

Hm.... How does one put the hash of the contract (code) into the contract itself?

The reference_hash is the hash of the external JSON file that contains additional, free-form details.
https://nomicon-pr-158.onrender.com/Standards/Tokens/FungibleTokenMetadata.html#reference-level-explanation

Let's merge it and iterate


fixing import errors for lumina music + lumina mini t2i

While trying to use the repo as a pip package, I ran into some errors for inference usage w/ the package imports

Thank you for fixing the typo.


Made toDictionary method failsafe

Just a small change to be able to not send optional values

Coverage increased (+0.1%) to 80.636% when pulling dbfde21c96bcd674c8adaf31609972dfb123d679 on lrrrs:master into eae08cf136017e728ebab9b46080d3a2658cbeb4 on xing:master.

Coverage increased (+0.1%) to 80.636% when pulling 8f1a588615caefdb583a5023504841edc4160843 on lrrrs:master into eae08cf136017e728ebab9b46080d3a2658cbeb4 on xing:master.


Fix flake8

Can one of the admins verify this patch?

Current coverage is 94.77% (diff: 100%)

Merging #49 into master will decrease coverage by <.01%

@@             master        #49   diff @@
==========================================
  Files            28         28
  Lines           958        957     -1
  Methods           0          0
  Messages          0          0
  Branches         39         39
==========================================
- Hits            908        907     -1
  Misses           42         42
  Partials          8          8

Powered by Codecov. Last update 4386301...aed4c70


Make SerDe Optional

Make the serde dependency optional and add all the cfg flags. See #51

There is a problem with the CI configuration, but I ran tests in my fork and they worked fine: https://app.circleci.com/pipelines/github/morenol/smartcore?branch=lmm%2Fserde
@VolodymyrOrlov I think that we should modify  .circleci/config.yml to run the tests with --all-features

There is a problem with the CI configuration, but I ran tests in my fork and they worked fine: https://app.circleci.com/pipelines/github/morenol/smartcore?branch=lmm%2Fserde
@VolodymyrOrlov I think that we should modify  .circleci/config.yml to run the tests with --all-features

Hi @ssorc3! Thank you for taking care of #51! Me and @morenol are trying to figure out why Circle CI build was not triggered for your PR and one possible explanation is that you are following the project fork with your personal account rather than the project itself on CircleCI.
Could you please go by this link https://app.circleci.com/settings/project/github/ssorc3/smartcore
and unfollow the Smartcore project in Circle CI?

Hi @ssorc3! Thank you for taking care of #51! Me and @morenol are trying to figure out why Circle CI build was not triggered for your PR and one possible explanation is that you are following the project fork with your personal account rather than the project itself on CircleCI.
Could you please go by this link https://app.circleci.com/settings/project/github/ssorc3/smartcore
and unfollow the Smartcore project in Circle CI?

Codecov Report

Merging #67 (f1cf8a6) into development (eb76949) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development      #67      +/-   ##
===============================================
- Coverage        83.82%   83.80%   -0.02%
===============================================
  Files               75       75
  Lines             7800     7800
===============================================
- Hits              6538     6537       -1
- Misses            1262     1263       +1

Impacted Files
Coverage Δ

src/algorithm/neighbour/cover_tree.rs
85.06% <ø> (ø)

src/algorithm/neighbour/linear_search.rs
85.52% <ø> (ø)

src/algorithm/neighbour/mod.rs
85.71% <ø> (ø)

src/cluster/dbscan.rs
84.84% <ø> (ø)

src/cluster/kmeans.rs
86.61% <ø> (ø)

src/decomposition/pca.rs
86.25% <ø> (ø)

src/decomposition/svd.rs
64.44% <ø> (ø)

src/ensemble/random_forest_classifier.rs
72.11% <ø> (ø)

src/ensemble/random_forest_regressor.rs
68.91% <ø> (ø)

src/error/mod.rs
32.00% <ø> (ø)

... and 34 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eb76949...f1cf8a6. Read the comment docs.

Codecov Report

Merging #67 (f1cf8a6) into development (eb76949) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development      #67      +/-   ##
===============================================
- Coverage        83.82%   83.80%   -0.02%
===============================================
  Files               75       75
  Lines             7800     7800
===============================================
- Hits              6538     6537       -1
- Misses            1262     1263       +1

Impacted Files
Coverage Δ

src/algorithm/neighbour/cover_tree.rs
85.06% <ø> (ø)

src/algorithm/neighbour/linear_search.rs
85.52% <ø> (ø)

src/algorithm/neighbour/mod.rs
85.71% <ø> (ø)

src/cluster/dbscan.rs
84.84% <ø> (ø)

src/cluster/kmeans.rs
86.61% <ø> (ø)

src/decomposition/pca.rs
86.25% <ø> (ø)

src/decomposition/svd.rs
64.44% <ø> (ø)

src/ensemble/random_forest_classifier.rs
72.11% <ø> (ø)

src/ensemble/random_forest_regressor.rs
68.91% <ø> (ø)

src/error/mod.rs
32.00% <ø> (ø)

... and 34 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eb76949...f1cf8a6. Read the comment docs.

There is a problem with the CI configuration, but I ran tests in my fork and they worked fine: https://app.circleci.com/pipelines/github/morenol/smartcore?branch=lmm%2Fserde
@VolodymyrOrlov I think that we should modify .circleci/config.yml to run the tests with --all-features

I agree, @ssorc3 could you please replace
--features "nalgebra-bindings ndarray-bindings"

with
--all-features

in these 2 lines of config.yml:
https://github.com/smartcorelib/smartcore/blob/development/.circleci/config.yml#L26
https://github.com/smartcorelib/smartcore/blob/development/.circleci/config.yml#L29

There is a problem with the CI configuration, but I ran tests in my fork and they worked fine: https://app.circleci.com/pipelines/github/morenol/smartcore?branch=lmm%2Fserde
@VolodymyrOrlov I think that we should modify .circleci/config.yml to run the tests with --all-features

I agree, @ssorc3 could you please replace
--features "nalgebra-bindings ndarray-bindings"

with
--all-features

in these 2 lines of config.yml:
https://github.com/smartcorelib/smartcore/blob/development/.circleci/config.yml#L26
https://github.com/smartcorelib/smartcore/blob/development/.circleci/config.yml#L29

Hi. Just made that change to the circleCI config. I'm not following the project so I don't think that's the issue. Let me know if there's anything else I can do to help with it.

Hi. Just made that change to the circleCI config. I'm not following the project so I don't think that's the issue. Let me know if there's anything else I can do to help with it.


Migrate transifex

:heart: Thank you for your contribution!
Description
Migrates transifex workflows to use the new client and actions, as the old one is deprecated (ref https://github.com/inveniosoftware/invenio-i18n/issues/114)
Also adds i18n tests
Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

[x] I'm aware of the code of conduct.
[x] I've created logical separate commits and followed the commit message format.
[ ] I've added relevant test cases.
[ ] I've added relevant documentation.
[ ] I've marked translation strings (for relevant code).
[ ] I've followed the CSS/JS and React guidelines (for relevant code).
[ ] I've followed the web accessibility guidelines (for relevant code).
[ ] I've followed the user interface guidelines (for relevant code).
[ ] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
[x] I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code
If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

You license your contribution under the same terms as the current repository’s license.
You agree that you have the right to license your contribution under the current repository’s license.

As noted here, we shall remove the workflows from the packages and move them to the organization


[Bug] Server hang after requesting folder for file-related /vault/{filename} endpoints

Consider the following folder structure:
.
├── a
│   └── a.md
└── b

Request /vault/{filename} related endpoints with filename = a (a is a folder, not a valid file).
What I get from the server response: It's completely hung.

Similar results can get from GET, PUT, POST, DELETE endpoints.
What I expected to get from the server response:
It should return some errors instead of hanging (maybe 405 Bad Request?)
OS: MacOS Monterey 12.2.1 (M1)
Obsidian version: 0.14.6
Obsidian local rest API version: 1.3.5

I notice a related issue, for the PUT /vault/{filename} endpoint, if the specified folder in the path doesn't exist, the server is hung forever. (e.g. filename = c/d.md and folder c doesn't exist)

What I expected to get from the server response:
It should return 405 Bad Request or create the nested folder structure before creating the new file (maybe an optional parameter for this functionality?).

I notice a related issue, for the PUT /vault/{filename} endpoint, if the specified folder in the path doesn't exist, the server will hang forever. (e.g. filename = c/d.md and folder c doesn't exist)

What I expected to get from the server response:
It should return 405 Bad Request or create the nested folder structure before creating the new file (maybe an optional parameter for this functionality?).

For this issue -^ I've created #24.

Thanks for another very thorough bug report; I've fixed this in c9bc41e.


[BUG] How to remove Time Dimension?

In order to build a report which is reflecting the number of visitors grouped by 'Landing Page + query string', I would like to use only one dimension 'Landing Page + query string' with the timeframe that I can set in the time panel in the top right corner.
But in the current configuration, Time Dimension choosing is mandatory. So I'm getting date rows and columns with Landing Pages, please check out the following screenshot:

I suggest getting the table as we see on Google Analytics. Rows are dimensions, columns are metrics. With options to get rid of Time Dimension.

Please, let me know if it is possible to implement or fix it in the upcoming days.

We need to test it, but it seems possible to implement it.
Previously, time dimensions were required because it was based on the use of grafana graphs.

I would really appreciate it if you could do it soon. Again, my goal is to get the table with 'Landing Page + query string' dimension as the first column and metrics such as Active Users, Sessions and etc in the following columns the same as you can see on the screenshot from GA below:

Let me know if you have any questions.

Nice to see this in your TODO list!

@lcc3108 hi, dude! Would you tell me the estimated time when you will be able to make this work?
Thanks in advance!

@Shebelev
It is difficult to answer the estimated time.
Even if the development is finished now, i don't know how long it will take until the grafana plugin update process.
One thing I can say is that I just started working on it.

I think the backend work is pretty much done.
However, the data verification part and front-end work are left.
We are planning to create a separate UI because we can only scope it by date when looking up data in GA. (Maybe...)

Hi, awesome! It looks just like we needed. I'm excited when you finalize this update. Thanks!

@lcc3108 is the plugin available now? or can this issue be on our end? Thanks for what you do!

@Shebelev
0.2.1 has a bug, so I fixed it as 0.2.2.
Can you tell me the version information?

@Shebelev
We updated Grafana, and all works but I see the same. It still requires me to choose the period of time. When I do it, I receive divided data by the second dimension

@Shebelev
The feature of the current issue is released in 0.2.3.
Plug-in updates have been submitted and will be released after a grafana review.


How to copy text from vim to system clipboard?

I want to copy the text from vim to my windows apps(such as browser), I try to use "+y but it does not work. If there are some command can solve my problem? I know I can quit vim then cat file.txt and use mouse to do it, but I want to copy the text without mouse.

@fcbruce not in an easy and obvious way.  You need to set up a pair of programs on both sides of the divide, one attached to the Windows clipboard, and one attached to the vim clipboard

@fpqc Note that "+y connects to the X11 clipboard, not to the Vim one, making this easier to handle. Indeed this already works in MSYS2, and without an X-server — install Git for Windows, start Git Bash, use vim inside. (Not sure how much magic is required for that though).

there ya go, fcbruce!  You have your answer, use an X11 terminal.

@fpqc @Blaisorblade Yes, it works. I installed Xming X Server for Windows and input the command export DISPLAY=:0 in the bash of linux subsystem. Thank you very much! ^_^

For those who want to go the X server route, let me leave my notes here.

Install VcXsrv (I found that Xming is outdated on sourceforge and the new version is donationware)
If it starts after installing, stop it
Start it using XLaunch (search in the start menu), go with all the defaults (ensure the clipboard options are checked)
At the end, save the configuration to a file (use that to start it from now on)
Put DISPLAY=localhost:0.0 in your .bashrc in bash for Windows (and run the command in any open bash windows). The reason I explicitly say localhost is that this makes SSH X forwarding work, see below.
Ensure vim is installed using clipboard support. vim --version | grep clipboard should say +clipboard, not -clipboard. Also if you run the ex command :echo has('clipboard') in vim and it says 0 it does not have clipboard support compiled in. If you don't have clipboard support, install the vim-gtk package (apt-get install vim-gtk).
It should now work

As a bonus you should now be able to copy from and to your Windows clipboard from a remote machine by using SSH X forwarding (ssh -X ... ). You can use xclip on the remote machine or if you use vim there you will again need to make sure the clipboard option is compiled into vim (e.g. install vim-gtk). You can probably also configure PuTTY to use your local X server in case you prefer using that for remote connections.

@robbiev Thank you for this! You are a lifesaver :)

steps 1-5 worked for sublime as well (not obvious to everyone)

those using the VcXsrv approach by @robbiev, I was trying to find a way to start VcXsrv without having to start it manually by the XLaunch GUI.
Adding a line like this to ~/.bashrc works for me:
# start Xserver for shared clipboard
"/mnt/c/Program Files/VcXsrv/xlaunch.exe" -run config.xlaunch

It requires a config file, which can be generated from the last screen of the XLaunch GUI, just save it in the same folder as the xlaunch executable

@lemongrassnginger Wouldn't this start a new server process for each shell you start? Why not just copy config.xlaunch to %USERPROFILE%AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup so that Windows launches an instance at startup?

So it does! Thanks for pointing that out. Will move to my Windows startup folder

For people sitll looking for a solution I found a way that works without having to use X server. Thanks to bravekarma on reddit.
Simply paste the following into your .vimrc or init.vim:
" WSL yank support
let s:clip = '/mnt/c/Windows/System32/clip.exe'  " change this path according to your mount point
if executable(s:clip)
    augroup WSLYank
        autocmd!
        autocmd TextYankPost * if v:event.operator ==# 'y' | call system(s:clip, @0) | endif
    augroup END
endif

Ok I found a better way with both copy and paste working. I tested for neovim but with some modification will sort of work for vim also.
You can see the original solution over this stackoverflow answer.
Basically involves downloading win32yank.exe. It gets used by default with neovim, for vim you will have to edit your .vimrc. For details on vim modifications please see the original answer over stackoverflow as he gives out better details than what I can. Proceed below when those are done.
In init.vim or .vimrc put set clipboard=unnamedplus.
Execute the following commands:
curl -sLo /tmp/win32yank.zip https://github.com/equalsraf/win32yank/releases/download/v0.0.4/win32yank-x64.zip
unzip -p /tmp/win32yank.zip win32yank.exe > /tmp/win32yank.exe
chmod +x /tmp/win32yank.exe
sudo mv /tmp/win32yank.exe ~/bin

For people sitll looking for a solution I found a way that works without having to use X server. Thanks to bravekarma on reddit.
Simply paste the following into your .vimrc or init.vim:
" WSL yank support
let s:clip = '/mnt/c/Windows/System32/clip.exe'  " change this path according to your mount point
if executable(s:clip)
    augroup WSLYank
        autocmd!
        autocmd TextYankPost * if v:event.operator ==# 'y' | call system(s:clip, @0) | endif
    augroup END
endif

thank you. this is by far the best solution.

Ok I found a better way with both copy and paste working. I tested for neovim but with some modification will sort of work for vim also.
You can see the original solution over this stackoverflow answer.
Basically involves downloading win32yank.exe. It gets used by default with neovim, for vim you will have to edit your .vimrc. For details on vim modifications please see the original answer over stackoverflow as he gives out better details than what I can. Proceed below when those are done.
In init.vim or .vimrc put set clipboard=unnamedplus.
Execute the following commands:
curl -sLo /tmp/win32yank.zip https://github.com/equalsraf/win32yank/releases/download/v0.0.4/win32yank-x64.zip
unzip -p /tmp/win32yank.zip win32yank.exe > /tmp/win32yank.exe
chmod +x /tmp/win32yank.exe
sudo mv /tmp/win32yank.exe ~/bin

The answer is based on this Neovim wiki page.
You have to ensure that you're placing win32yank.exe in your path (the command assumes that ~/bin is in your path)

If the solution with VcXsrv described by @robbiev stopped working when upgrading from WSL1 to WSL2, do the following:
- In XLaunch settings check "Disable any access control"
- Put in .bashrc
export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2>/dev/null):0
export LIBGL_ALWAYS_INDIRECT=0
Found here.

If the solution with VcXsrv described by @robbiev stopped working when upgrading from WSL1 to WSL2, do the following:
- In XLaunch settings check "Disable access control"
- Put in .bashrc
export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2>/dev/null):0
export LIBGL_ALWAYS_INDIRECT=0
Found here.

For people sitll looking for a solution I found a way that works without having to use X server. Thanks to bravekarma on reddit.
Simply paste the following into your .vimrc or init.vim:
" WSL yank support
let s:clip = '/mnt/c/Windows/System32/clip.exe'  " change this path according to your mount point
if executable(s:clip)
    augroup WSLYank
        autocmd!
        autocmd TextYankPost * if v:event.operator ==# 'y' | call system(s:clip, @0) | endif
    augroup END
endif

This is a brilliant answer, I think this works on my machine. However, if I ssh into a machine and try to yank those files to the clipboard, it no longer works? How to overcome this issue?

These are nice workarounds, but considering who makes WSL. it is a wonder that "* and "+ do not work at all out of the box, that there is no underlying mechanism between it and the system clipboard. if you type :registers they don't even show. "*dd and "+dd function as though successful, but aren't. If you do "*10yy and "+10yy you get the 10 lines yanked message, but it will yank into unnamed register and the yank register. "a10yy yanks into the "a register properly.
I think @fcbruce and @alexcoca are still more correct than not that is should be an enhancement request or a bug report of some kind

For those who want to go the X server route, let me leave my notes here.
...

If you're on Windows 11, WSL has an X server configured out of the box.
The steps required for copy-paste are reduced simply to:

sudo apt install vim-gtk

This switches the installed options from -clipboard to +clipboard, and "+y will work immediately.
"*y still doesn't work, I'm not sure why.

For people sitll looking for a solution I found a way that works without having to use X server. Thanks to bravekarma on reddit.
Simply paste the following into your .vimrc or init.vim:
" WSL yank support
let s:clip = '/mnt/c/Windows/System32/clip.exe'  " change this path according to your mount point
if executable(s:clip)
    augroup WSLYank
        autocmd!
        autocmd TextYankPost * if v:event.operator ==# 'y' | call system(s:clip, @0) | endif
    augroup END
endif

Here's a translation into Lua for any Neovim users that come across this issue:
-- WSL clipboard support
do local clip, opts = '/mnt/c/Windows/System32/clip.exe', {}
  function opts.callback()
    if vim.v.event.operator ~= 'y' then return end
    vim.fn.system(clip, vim.fn.getreg(0))
  end
  if vim.fn.executable(clip) then
    opts.group = vim.api.nvim_create_augroup("WSLYank", {clear = true})
    vim.api.nvim_create_autocmd("TextYankPost", opts)
  end
end


Fixes for questa

Merge from Questa branch

@svenka3

Could you run OT with Questasim? I tried your branch which supports Questa but it did not work?
I use Questa 10.7c and it seems that the build phase passed, however when running to the simulation phase, it raises errors as below. Any help is appreciated!

Please try recent Questa version, I saw same error and it vanished in 2019.* Version if I recall
Good luck


[Feature Suggestion] Titled Wildcard Entries

Hello and good day to anyone reading this post. I'd like to recommend a feature that I feel could be very useful for the wildcard. Namely that of the ability to title wildcard entries. In most standard uses of wildcards people utilize one word per entry so it's easy enough for browsing. But if you're utilizing wildcards to store entire complex prompts or nested wildcard sequences it can quickly become a daunting task differentiating them all.
I propose a feature to be able to name the wildcard entries so that instead of showing the actual wildcard, it'd show the title instead. How I imagine it could work is that if you put a comment at the end of a wildcard entry or perhaps a double comment so it's specified as a title it'd instead show up when activating the wildcard from the prompt.
For example the following prompt 'character sitting on a beach enjoying a drink of water while a wave crashes in the background' could then have the comment at the end ## Beach Relaxation. And thus show up as just 'Beach Relaxation' in the list.
Thank you for your time in reading this and I hope that my idea may be picked up as a new feature for wildcards. As well I apologize if this has already been suggested, I looked through the other posts and don't think I saw anyone suggesting anything similar.

Thanks for the suggestion - it's a nice idea but we still need a way to differentiate regular words from wildcards. Dynamic Prompts doesn't have control of the prompt box. It receives whatever you wrote in there, looks for the wildcards and then replaces them with random values. "Beach Relaxation" is impossible to differentiate from regular text. Wouldn't naming the file achieve more or less the same purpose, i.e. Beach Relaxation.txt will become __Beach Relaxation

I was worried I wasn't properly clear in my explanation. What I'm proposing is a visual change for usage of wildcard look up in the prompt. Currently when typing in a wildcard it then populates a list of the wildcard entries so that you can choose one if you so desire. What I'm proposing is the ability to change how a wildcard entry shows up in that list with a title comment at the end of the entry. We'd only be seeing the title in that popped up list while typing, when clicking on it it'd spit out the actual entry. The way I'd have it syntax wise would be a doubt comment at the end to show wildcards what is defined as the title.
Having a bunch of nested single entry wildcards could achieve a similar effect but it could quickly snowball if you have a long enough list of entries.

I was worried I wasn't properly clear in my explanation. What I'm proposing is a visual change for usage of wildcard look up in the prompt. Currently when typing in a wildcard it then populates a list of the wildcard entries so that you can choose one if you so desire. What I'm proposing is the ability to change how a wildcard entry shows up in that list with a title comment at the end of the entry. We'd only be seeing the title in that popped up list while typing, when clicking on it it'd spit out the actual entry. The way I'd have it syntax wise would be a doubt comment at the end to show wildcards what is defined as the title.
Having a bunch of nested single entry wildcards could achieve a similar effect but it could quickly snowball if you have a long enough list of entries.

As a quick and dirty fix you could look at my pull request that adds search functionality as a new entry in the txt2img tab :)
#546


⚠ Bofrost.es has degraded performance

In 630fa89, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1437 ms

Resolved: Bofrost.es performance has improved in 1c717cf after 6 minutes.


Add aria data

https://www.w3.org/wiki/SVG_Accessibility/ARIA_roles_for_charts

Closed by a8c1b7699cd8e2d4a3a5544ba8405da3540feaea


Upgraded examples/webgl to use WebGL2 instead of WebGL1

Since all recent major browser releases (With the possible exception of Safari iOS) now support WebGL2, I thought it may help others if the example was upgraded to support WebGL2.
Although, I completely understand if you would like to keep it at webgl 1 to support the widest range of browsers / devices.

Thanks!


[BUG] - compoundVariants is not working when extendVariants

Describe the bug
I want to add more color variants for the button and I tried to replicate the same behavior that button is using for adding the classes. So when I use the extendVariants function to add a new color and compoundVariants, it is not applied.
Your Example Website or App
https://codesandbox.io/p/sandbox/issue-compoundvariants-jktcks?file=%2FApp.jsx%3A4%2C22-4%2C36
Steps to Reproduce the Bug or Issue

Go to https://codesandbox.io/p/sandbox/issue-compoundvariants-jktcks?file=%2FApp.jsx%3A4%2C22-4%2C36
You can check the button is not red

Expected behavior
As a user, I expected the button change their color classes when compoundVariants is being extended.
Screenshots or Videos
No response
Operating System Version
Windows
Browser
Edge

Hey @maxigs7 extendVariants doesn't include the default variants/compoundVariants, only the passed ones, so you need to create the solid variant in your extendVariants function, as follows:

const NextUIButton = extendVariants(Button, {
  variants: {
    variant: {
      solid: "", // <- add the solid variant
    },
    color: {
      accent: "",
    },
  },
  compoundVariants: [
    {
      variant: "solid",
      color: "accent",
      class: "bg-red-500 text-red-900",
    },
  ],
});

https://codesandbox.io/p/sandbox/issue-compoundvariants-forked-m9w82g?file=%2FApp.jsx%3A3%2C1-20%2C4
Inherit the default variants/compoundVariants etc is way more complicated

Thanks, @jrgarciadev!
That worked. I think would be nice to add some notes in the docs about that, it's kinda confusing.

I agree with you @maxigs7 Will make this clear on the docs, thank you!

import { button, extendVariants, Button as NextUIButton } from "@nextui-org/react";

const Button = extendVariants(NextUIButton, {
  variants: {
    ...button.variants, // 🟢 extend original variants
    variant: {
      ...button.variants.variant, // 🟢 extend original variants.variant
      outlined: "border-medium bg-transparent", // then add your variant
    },
  },

  compoundVariants: [ // now you're free to compose with every variants' keys
    {
      variant: "outlined",
      color: "default",
      class: "text-default border-default-50",
    },
    {
      variant: "outlined",
      color: "primary",
      class: "text-primary border-primary-50",
    },
// ...
  ],
});


enhancement throw exception instead of core during insert_range_from method

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


change transpose to adjoint (#27)

To close #32

@archanarw Thanks for this.
Looks like MultivariateStats needs to tag a new release. I've pinged them.

Update: The change at MultivariateStats is not live, but in a new minor version 0.10. So now we should wait for #49 or it's equivalent.

Closed in favour of https://github.com/JuliaAI/MLJMultivariateStatsInterface.jl/pull/51


docker build parcel error for socket.io

When building the docker container for app either through docker build or docker-compose build I am getting the following error during npm install.

Steps to recreate error:

clone repository
cd postgis-geologic-map
update submodules
run docker-compose build or docker build -t geologic-map .

It looks like the actual issue is coming from the mapboard-server package.

I believe it's referring to this /socket.io/socket.io.js on line 30.


Update links to assets.holoviews.org to use https

Since holoviews.org and assets.holoviews.org now have their own SSL certificates http based links are now causing certain pages on the website to be marked untrusted. All links to assets.holoviews.org should therefore be updated to explicitly use https.

Addressed in the merged PR referenced above. Closing.


Automatically hash status to determine screen refreshes

Right now, the administrator has to manually update a field to get the screen to refresh. Generate this automatically by hashing the status of all fields, including stop contents, column locations, etc.

Done and committed.


2021-01-07 06:31:39,370 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3f67ceece7e797a5736a25488aae35405649b90b
2021-01-07 06:31:39,373 autosynth [DEBUG] > Running: git log -1 --pretty=%at aa255b15d52b6d8950cca48cfdf58f7d27a60c8a
2021-01-07 06:31:39,377 autosynth [DEBUG] > Running: git log -1 --pretty=%at d73e8dea90af1b463a7f9d4a33244cf4612ada7c
2021-01-07 06:31:39,380 autosynth [DEBUG] > Running: git log -1 --pretty=%at 41e998d5afdc2c2143a23c9b044b9931936f7318
2021-01-07 06:31:39,383 autosynth [DEBUG] > Running: git log -1 --pretty=%at b670a77a454f415d247907908e8ee7943e06d718
2021-01-07 06:31:39,386 autosynth [DEBUG] > Running: git log -1 --pretty=%at 363fe305e9ce34a6cd53951c6ee5f997094b54ee
2021-01-07 06:31:39,390 autosynth [DEBUG] > Running: git log -1 --pretty=%at<PHONE_NUMBER>48b5fe5e0ac4f8a38b32d639ee93e4
2021-01-07 06:31:39,393 autosynth [DEBUG] > Running: git log -1 --pretty=%at 407613a1ac6a8a0a951a50dfbccb1be38ef6c5a0
2021-01-07 06:31:39,396 autosynth [DEBUG] > Running: git log -1 --pretty=%at 6b026e1443948dcfc0b9e3289c85e940eb70f694
2021-01-07 06:31:39,399 autosynth [DEBUG] > Running: git log -1 --pretty=%at 6133907dbb3ddab204a17a15d5c53ec0aae9b033
2021-01-07 06:31:39,402 autosynth [DEBUG] > Running: git log -1 --pretty=%at 759bdfc5272d9977324d7cfdae46771e23890f91
2021-01-07 06:31:39,405 autosynth [DEBUG] > Running: git log -1 --pretty=%at c992f7a0096ea35b331210c51050befd2499b98e
2021-01-07 06:31:39,409 autosynth [DEBUG] > Running: git log -1 --pretty=%at 40d76d547573fc273220bc0c8291fd942cb4502b
2021-01-07 06:31:39,412 autosynth [DEBUG] > Running: git log -1 --pretty=%at a3e990f3545dc8ccd384a75d20ce9cb185ca6a28
2021-01-07 06:31:39,418 autosynth [DEBUG] > Running: git checkout 5921e62fc9b1e78ec502052e2ba4e98856dc9b86
Note: checking out '5921e62fc9b1e78ec502052e2ba4e98856dc9b86'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5921e62 chore: update templates; use bazel gen (#25)
2021-01-07 06:31:39,424 autosynth [DEBUG] > Running: git checkout a3e990f3545dc8ccd384a75d20ce9cb185ca6a28
Note: checking out 'a3e990f3545dc8ccd384a75d20ce9cb185ca6a28'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at a3e990f fix: Listing apiary libraries correctly parses versions with dots (#896)
2021-01-07 06:31:39,430 autosynth [DEBUG] > Running: git checkout 5a3edc8b272dcd714fd0f16d2c788b2f95183729
Note: checking out '5a3edc8b272dcd714fd0f16d2c788b2f95183729'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5a3edc8b chore: update gapic-generator-go to v0.17.0
2021-01-07 06:31:39,446 autosynth [DEBUG] > Running: git branch -f autosynth-1000
2021-01-07 06:31:39,450 autosynth [DEBUG] > Running: git checkout autosynth-1000
Switched to branch 'autosynth-1000'
2021-01-07 06:31:39,454 autosynth [INFO] > Running synthtool
2021-01-07 06:31:39,455 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-01-07 06:31:39,455 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/python-recaptcha-enterprise/1000/sponge_log.log
2021-01-07 06:31:39,457 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-01-07 06:31:39,695 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/python-recaptcha-enterprise/synth.py.
On branch autosynth-1000
nothing to commit, working tree clean
2021-01-07 06:31:39,839 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
2021-01-07 06:31:39,845 synthtool [DEBUG] > Ensuring dependencies.
2021-01-07 06:31:39,857 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/python-recaptcha-enterprise/synth.py", line 31, in <module>
    bazel_target=f"//google/cloud/recaptchaenterprise/{version}:recaptchaenterprise-{version}-py",
NameError: name 'version' is not defined
2021-01-07 06:31:39,925 autosynth [ERROR] > Synthesis failed
2021-01-07 06:31:39,926 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 5921e62 chore: update templates; use bazel gen (#25)
2021-01-07 06:31:39,931 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2021-01-07 06:31:39,936 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating python-recaptcha-enterprise. :sob:
Here's the output from running synth.py:
fbb7045c34c9d3d22c1ff766eeae51f04c9
2021-01-07 06:31:39,315 autosynth [DEBUG] > Running: git log -1 --pretty=%at 39b7149da4026765385403632db3c6f63db96b2c
2021-01-07 06:31:39,319 autosynth [DEBUG] > Running: git log -1 --pretty=%at a073c873f3928c561bdf87fdfbf1d081d1998984
2021-01-07 06:31:39,322 autosynth [DEBUG] > Running: git log -1 --pretty=%at 68742c6016bf0d16948a572633d17955a8737414
2021-01-07 06:31:39,325 autosynth [DEBUG] > Running: git log -1 --pretty=%at 91b34d7ffc37581e03eec8b16d08b84e46b82bbe
2021-01-07 06:31:39,329 autosynth [DEBUG] > Running: git log -1 --pretty=%at 943bb78606d035001123030067dffcc34f4645f2
2021-01-07 06:31:39,332 autosynth [DEBUG] > Running: git log -1 --pretty=%at 15013eff642a7e7e855aed5a29e6e83c39beba2a
2021-01-07 06:31:39,335 autosynth [DEBUG] > Running: git log -1 --pretty=%at c2de32114ec484aa708d32012d1fa8d75232daf5
2021-01-07 06:31:39,339 autosynth [DEBUG] > Running: git log -1 --pretty=%at 32af6da519a6b042e3da62008e2a75e991efb6b4
2021-01-07 06:31:39,342 autosynth [DEBUG] > Running: git log -1 --pretty=%at 69629b64b83c6421d616be2b8e11795738ec8a6c
2021-01-07 06:31:39,346 autosynth [DEBUG] > Running: git log -1 --pretty=%at f94318521f63085b9ccb43d42af89f153fb39f15
2021-01-07 06:31:39,349 autosynth [DEBUG] > Running: git log -1 --pretty=%at 18c5dbdb4ac8cf75d4d8174e7b4558f48e76f8a1
2021-01-07 06:31:39,353 autosynth [DEBUG] > Running: git log -1 --pretty=%at 5d11bd2888c38ce1fb6fa6bf25494a4219a73928
2021-01-07 06:31:39,356 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3559dd8cb634347737632776ef4089443eacdb4f
2021-01-07 06:31:39,359 autosynth [DEBUG] > Running: git log -1 --pretty=%at 7d1ee3207371ef72a1ca931a0964c4007e687280
2021-01-07 06:31:39,363 autosynth [DEBUG] > Running: git log -1 --pretty=%at 352f25621c28d2fa0784984ea0ed5ea697aa1525
2021-01-07 06:31:39,367 autosynth [DEBUG] > Running: git log -1 --pretty=%at 996775eca5fd934edac3c2ae34b80ff0395b1717
2021-01-07 06:31:39,370 autosynth [DEBUG] > Running: git log -1 --pretty=%at 3f67ceece7e797a5736a25488aae35405649b90b
2021-01-07 06:31:39,373 autosynth [DEBUG] > Running: git log -1 --pretty=%at aa255b15d52b6d8950cca48cfdf58f7d27a60c8a
2021-01-07 06:31:39,377 autosynth [DEBUG] > Running: git log -1 --pretty=%at d73e8dea90af1b463a7f9d4a33244cf4612ada7c
2021-01-07 06:31:39,380 autosynth [DEBUG] > Running: git log -1 --pretty=%at 41e998d5afdc2c2143a23c9b044b9931936f7318
2021-01-07 06:31:39,383 autosynth [DEBUG] > Running: git log -1 --pretty=%at b670a77a454f415d247907908e8ee7943e06d718
2021-01-07 06:31:39,386 autosynth [DEBUG] > Running: git log -1 --pretty=%at 363fe305e9ce34a6cd53951c6ee5f997094b54ee
2021-01-07 06:31:39,390 autosynth [DEBUG] > Running: git log -1 --pretty=%at<PHONE_NUMBER>48b5fe5e0ac4f8a38b32d639ee93e4
2021-01-07 06:31:39,393 autosynth [DEBUG] > Running: git log -1 --pretty=%at 407613a1ac6a8a0a951a50dfbccb1be38ef6c5a0
2021-01-07 06:31:39,396 autosynth [DEBUG] > Running: git log -1 --pretty=%at 6b026e1443948dcfc0b9e3289c85e940eb70f694
2021-01-07 06:31:39,399 autosynth [DEBUG] > Running: git log -1 --pretty=%at 6133907dbb3ddab204a17a15d5c53ec0aae9b033
2021-01-07 06:31:39,402 autosynth [DEBUG] > Running: git log -1 --pretty=%at 759bdfc5272d9977324d7cfdae46771e23890f91
2021-01-07 06:31:39,405 autosynth [DEBUG] > Running: git log -1 --pretty=%at c992f7a0096ea35b331210c51050befd2499b98e
2021-01-07 06:31:39,409 autosynth [DEBUG] > Running: git log -1 --pretty=%at 40d76d547573fc273220bc0c8291fd942cb4502b
2021-01-07 06:31:39,412 autosynth [DEBUG] > Running: git log -1 --pretty=%at a3e990f3545dc8ccd384a75d20ce9cb185ca6a28
2021-01-07 06:31:39,418 autosynth [DEBUG] > Running: git checkout 5921e62fc9b1e78ec502052e2ba4e98856dc9b86
Note: checking out '5921e62fc9b1e78ec502052e2ba4e98856dc9b86'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5921e62 chore: update templates; use bazel gen (#25)
2021-01-07 06:31:39,424 autosynth [DEBUG] > Running: git checkout a3e990f3545dc8ccd384a75d20ce9cb185ca6a28
Note: checking out 'a3e990f3545dc8ccd384a75d20ce9cb185ca6a28'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at a3e990f fix: Listing apiary libraries correctly parses versions with dots (#896)
2021-01-07 06:31:39,430 autosynth [DEBUG] > Running: git checkout 5a3edc8b272dcd714fd0f16d2c788b2f95183729
Note: checking out '5a3edc8b272dcd714fd0f16d2c788b2f95183729'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5a3edc8b chore: update gapic-generator-go to v0.17.0
2021-01-07 06:31:39,446 autosynth [DEBUG] > Running: git branch -f autosynth-1000
2021-01-07 06:31:39,450 autosynth [DEBUG] > Running: git checkout autosynth-1000
Switched to branch 'autosynth-1000'
2021-01-07 06:31:39,454 autosynth [INFO] > Running synthtool
2021-01-07 06:31:39,455 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-01-07 06:31:39,455 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/python-recaptcha-enterprise/1000/sponge_log.log
2021-01-07 06:31:39,457 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-01-07 06:31:39,695 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/python-recaptcha-enterprise/synth.py.
On branch autosynth-1000
nothing to commit, working tree clean
2021-01-07 06:31:39,839 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
2021-01-07 06:31:39,845 synthtool [DEBUG] > Ensuring dependencies.
2021-01-07 06:31:39,857 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/python-recaptcha-enterprise/synth.py", line 31, in <module>
    bazel_target=f"//google/cloud/recaptchaenterprise/{version}:recaptchaenterprise-{version}-py",
NameError: name 'version' is not defined
2021-01-07 06:31:39,925 autosynth [ERROR] > Synthesis failed
2021-01-07 06:31:39,926 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 5921e62 chore: update templates; use bazel gen (#25)
2021-01-07 06:31:39,931 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2021-01-07 06:31:39,936 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.


Travis CI build takes 4 hours to complete, and randomly* fails.

All of the following builds should have passed, but either didn't due to negative codecov (of less than a percentage) or the CI (travis) failing:
FAIL transperancy: Make the user aware that DEBUG mode is enabled. #1446 opened 21 hours ago by Zarthus   1
PASS debugging: Add Filter method to hide filter sensitive data #1445 opened 22 hours ago by Zarthus   1
PASS Tidy up README #1444 opened 2 days ago by Zarthus   2
FAIL route_replies: rizon: [MODE] Add 403, 442 expectations #1443 opened 2 days ago by Zarthus   1
FAIL Remove unused AUTHORS symlink opened 5 days ago by Zarthus   1

Codecov accepts configuration in yaml, feel free to send pull request
Or do you propose to remove CI?

I wrote an issue so it's not forgotten. I don't care what the solution looks like, closing this issue because "someone can submit a PR instead" seems a bit counter-intuitive, we might as well close all issues then.


Charlesite Article lead doesn't load

Add: http://playlist.wiki/playlist/minerals-named-for-geologists

This article doesn't have an 'extract' which is used as the article description. The only thing I'm able to get for this article is the very short summary. Articles now fall back to using this if an extract is not available.


Distinguish missing and undefined

Typescript should distinguish missing and undefined at the type level in order to distinguish the following two statements:
// @strictNullChecks: true
type A = { x?: string }
let x: A = {}
let y: A = { x: undefined } // should not be allowed, but currently is

I believe this is a dupe of #13195

you are right. closing.


feat: dataset REST API for distinct values

SUMMARY
Creates a new generic endpoint to query distinct values from a ModelRestApi useful for filter dropdowns
This endpoint behaves in a very similar way then /api/v1/<resource>/related/<column_name> on this case /api/v1/<resource>/distinct/<column_name>
Accepts also the same JSON/Rison query parameters:
{
  "filter": "string",
  "page": 0,
  "page_size": 0
}

To enable this generic endpoint on a ModelRestApi child class we need to:
include_route_methods = { ..., RouteMethod.DISTINCT, }

Enable the fields that we allow to be queried:
allowed_distinct_fields = {"schema"}

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

🏷 API

🗑 🏷 api


ffi issue when bundle install

When running bundle install on MacOS 10.15.7 and Xcode 12.4
Function.c:852:17: error: implicit declaration of function 'ffi_prep_closure_loc' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
    ffiStatus = ffi_prep_closure_loc(code, &fnInfo->ffi_cif, callback_invoke, closure, code);
                ^
Function.c:852:17: note: did you mean 'ffi_prep_closure'?
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/ffi/ffi.h:269:1: note: 'ffi_prep_closure' declared here
ffi_prep_closure(
^
1 error generated.
make: *** [Function.o] Error 1
Function.c:852:17: error: implicit declaration of function 'ffi_prep_closure_loc' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
    ffiStatus = ffi_prep_closure_loc(code, &fnInfo->ffi_cif, callback_invoke, closure, code);
                ^
Function.c:852:17: note: did you mean 'ffi_prep_closure'?
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/ffi/ffi.h:269:1: note: 'ffi_prep_closure' declared here
ffi_prep_closure(
^
1 error generated.
make: *** [Function.o] Error 1

make failed, exit code 2

How can I fix this issue ?
Thanks in advance.

I got the solutions
/amazon-ivs-player-ios-sample/vendor/bundle/ruby/2.6.0/gems/ffi-1.13.1]$ bundle config build.ffi --disable-system-libffi
/amazon-ivs-player-ios-sample/vendor/bundle/ruby/2.6.0/gems/ffi-1.13.1]$ bundle install

It works.

Thanks for the report and following up with the solution.  Closing this issue.


Feature request: Search Bar

Is there any way (or any plans) to implement a search bar? It would be nice to search for keywords throughout the textbook.

it is relatively easy to have a search bar, but when I played around with the default Jekyll search bar it was very slow - I agree this would be a great feature to have as long as it doesn't hurt performance too much!

http://prob140.org/textbook/chapters/Search
Definitely room for improvement but still functional!


app is running but return nothing.

Version
Tell us which versions you are using ( you can see the versions in your package.json ):
react-native-audio :  3.5.1
react-native :0.52.2
react :  16.2.0
using react-native-sound ? Yes/No
1.2.6
yes
Expected behaviour :
What were you trying to do and what did you expect to happen ?
import React, { Component } from 'react';
import {Alert} from 'react-native';
//import Record from 'react-native-record-sound';
import {AudioRecorder, AudioUtils} from 'react-native-audio';
let audioPath = AudioUtils.DocumentDirectoryPath + '/test.aac';
let isRecording = false;
import {
/* Platform,*/
StyleSheet,
Text,
View,
Button
} from 'react-native';
/const instructions = Platform.select({
ios: 'Press Cmd+R to reload,\n' +
'Cmd+D or shake for dev menu',
android: 'Double tap R on your keyboard to reload,\n' +
'Shake or press menu button for dev menu',
});/
export default class App extends Component<{}> {
render() {
return

This is audio demo

;
}
static recordSound() {
if (isRecording === false) {
       AudioRecorder.prepareRecordingAtPath(audioPath, {
              SampleRate: 22050,
              Channels: 1,
              AudioQuality: "Low",
              AudioEncoding: "aac"
          });

        // Record.startRecord( audioPath + 'sound.aac' );
         // this.recordSound(audioPath);
          Alert.alert('recording_start:'+ audioPath);

      }
      else
      {
          Alert.alert('recording stop');
        // Record.stopRecord();
   //  isRecording = !isRecording;
  }}

}
const styles = StyleSheet.create({
container: {
flex: 1,
justifyContent: 'center',
alignItems: 'center',
backgroundColor: '#F5FCFF',
},
welcome: {
fontSize: 20,
textAlign: 'center',
margin: 10,
},
instructions: {
textAlign: 'center',
color: '#333333',
marginBottom: 5,
},
});
What happened when your issue occurred ? The more details you provide here the better the odds are that someone will help you resolve your issue
app is working well but not recording start and return nothing.
Please provide us with some code that we can run to reproduce your error.
above i already provided.
If you put a GitHub repo that reproduces your issue then you significantly increase your chances of getting help !

its working fine when i giving music directory path instead of Document directory path.


write rest_api.js

Closing due to one PR made for multiple stories [ Added the PR and summarized all stories in 1 ]


Mypy: Fully migrate to py3 function annotations in 3 more core files

This reduces the list of files which are excluded from linting for python2 annotations:

models.py: using approach already taken elsewhere in the file (QuerySet without subscript, or Sequence[T]);
stream_subscription.py: same approach as above, except only the former option is possible;
descriptors.py: use quotes for types, presumably bypassing a circular dependency.

Passes test-all on droplet.

This is a follow-up to my work in #8662.

Merged, thanks @neiljp!


added -o for mercurial

jest -o will now correctly detect changed files in mercurial projects

@facebook-github-bot import

This is great!

@facebook-github-bot shipit


Switch tests to use Helvetica Neue

Currently, the tests use the system font, and have hard-coded metrics, which means they fail on iOS 8. Switch to explicitly using Helvetica Neue or some other font that is also on iOS 8, so that the tests can run on any simulator running iOS 8 and higher.

systemFont was used in 2 places, replaced with Avenir


GH-2496: Reuse retry topic for maxInterval delay

Resolves spring-projects#2496
Created SameIntervalTopicReuseStrategy, used to keep retrying in the same retry topic when the delays of the last retries are the same.

@jgslima Thanks for the PR; it might take a bit of time to get it reviewed; with the upcoming holidays (and after recently getting out major releases) we are beginning to wind down a little. After today, I will not be working until the 19th and then, only for a few days before breaking again until the New Year.
I just wanted to let you know, in case you thought we were ignoring you; your work is definitely appreciated.
Thanks.

@jgslima Thanks for the PR; it might take a bit of time to get it reviewed; with the upcoming holidays (and after recently getting out major releases) we are beginning to wind down a little. After today, I will not be working until the 19th and then, only for a few days before breaking again until the New Year.
I just wanted to let you know, in case you thought we were ignoring you; your work is definitely appreciated.
Thanks.

Ok, good to know, have a nice vacation.

@jgslima Sorry for the delay - I hope to get to this next week.

Thank you for the reviews, I will be able to work on the changes on the weekend.

Besides marking FixedDelayStrategy and its related methods as deprecated, I tried to clean some classes, to make them work with just SameIntervalTopicReuseStrategy as much as possible.
So, I tried to change RetryTopicConfigurationBuilder and DestinationTopicPropertiesFactory, removing their FixedDelayStrategy attributes.
But after struggling for a while, it seems to me that it is best to leave the code as it is, and to clean it only when the actual remove is done in 3.1.
One of the issues is with RetryTopicConfigurationBuilder. We might make the methods useSingleTopicForFixedDelays() to define the value of the new attribute SameIntervalTopicReuseStrategy. However, the builder would have 2 pairs of methods that would act on the same attribute, and therefore, the SameIntervalTopicReuseStrategy attribute would end up having the value of the method called last (which would override the previous call), which might have misleading results.
Since today nobody uses the new methods dedicated to SameIntervalTopicReuseStrategy (like the new one useSingleTopicForSameIntervals()), we could make the builder to throw an error if both kinds of methods were called, requiring the user to call just one of them.
But the problem is with RetryableTopicAnnotationProcessor. Since both annotation attributes have default values, and are never null, RetryableTopicAnnotationProcessor needs to call both kinds of methods in the builder. I thought about having RetryableTopicAnnotationProcessor to check if both annotation attributes values are "compatible", throwing an error if not, so that only the method builder.sameIntervalTopicReuseStrategy() would be called. But this would break existing code that just declares fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC, since this would be incompatible with SameIntervalTopicReuseStrategy.MULTIPLE_TOPICS, which must be the default value.
It might be possible to work around this, by making the attribute sameIntervalTopicReuseStrategy() in the annotation with default as null, but I think this is not good for the annotation itself.
So for now, only the class DefaultDestinationTopicResolver would already be "cleaned".

In order to deprecate FixedDelayStrategy, I struggled a lot and was not able to find a proper approach for the @RetryableTopic annotation.
Its new SameIntervalTopicReuseStrategy attribute must have a default value (not just to simplify the annotation use, but also, to avoid breaking all existing declarations).
For the 2 cases below, I think we can assume SINGLE, because, we can tell that the user actually declared something for sameIntervalTopicReuseStrategy (since it is different from its default value of MULTIPLE):
@RetryableTopic(
     sameIntervalTopicReuseStrategy = SameIntervalTopicReuseStrategy.SINGLE_TOPIC
)

@RetryableTopic(
     sameIntervalTopicReuseStrategy = SameIntervalTopicReuseStrategy.SINGLE_TOPIC,
     fixedDelayTopicStrategy = FixedDelayStrategy.MULTIPLE_TOPICS
)

But the problem occurs in these 2 cases:
// below, SameIntervalTopicReuseStrategy.MULTIPLE_TOPICS is assumed since it is the default value.
@RetryableTopic(
     fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC
)

@RetryableTopic(
     fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC
     sameIntervalTopicReuseStrategy = SameIntervalTopicReuseStrategy.MULTIPLE_TOPICS
)

For them,  we cannot actually give some form of precedence for the configuration of SameIntervalTopicReuseStrategy, because we cannot tell whether the user actually configured it (I do not know means in the Java reflection API to tell whether an annotation attribute was actually declared).
If we could tell whether the user actually declared the attribute, we could assume SINGLE in the first case, and assume MULTIPLE in the second case (or even throw an error, requiring the user to configure just one of them).
We cannot assume MULTIPLE, because this would change the behaviour of existing codes like the first case.
We cannot also give precedence for the configuration of fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC because in the second case, it would not make sense to give precedence to a deprecated property.
I am really calling it... need help here.

In order to deprecate FixedDelayStrategy, new code that calls only the new methods in RetryTopicConfigurationBuilder should work fine. So the new methods like sameIntervalTopicReuseStrategy() should work also when using a single fixed delay topic.
However, by keeping the existing methods (like useSingleTopicForFixedDelays()) the builder would have 2 pairs of methods that would act on the same configuration, and therefore, the configuration would end up having the value of the method called last (which would override the previous call), which might have misleading results.
Since today nobody uses the new methods dedicated to SameIntervalTopicReuseStrategy (like the new one useSingleTopicForSameIntervals()), we could make the builder to throw an error if both kinds of methods were called, requiring the user to call just one of them.
But the problem is with RetryableTopicAnnotationProcessor. The new SameIntervalTopicReuseStrategy attribute of @RetryableTopic must have a default value (not just to simplify the annotation use, but also, to avoid breaking all existing declarations). Since both annotation attributes have default values, and are never null, for RetryableTopicAnnotationProcessor it is hard to know how to interact with the builder.
For the 2 cases below, I think we could give precedence for the sameIntervalTopicReuseStrategy and assume SINGLE, because, we can tell that the user actually declared something for sameIntervalTopicReuseStrategy (since it is different from its default value of MULTIPLE):
@RetryableTopic(
     sameIntervalTopicReuseStrategy = SameIntervalTopicReuseStrategy.SINGLE_TOPIC
)

@RetryableTopic(
     sameIntervalTopicReuseStrategy = SameIntervalTopicReuseStrategy.SINGLE_TOPIC,
     fixedDelayTopicStrategy = FixedDelayStrategy.MULTIPLE_TOPICS
)

But the problem occurs in these 2 cases:
// below, SameIntervalTopicReuseStrategy.MULTIPLE_TOPICS is assumed since it is the default value.
@RetryableTopic(
     fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC
)

@RetryableTopic(
     fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC
     sameIntervalTopicReuseStrategy = SameIntervalTopicReuseStrategy.MULTIPLE_TOPICS
)

For them,  we cannot actually give some form of precedence for the configuration of SameIntervalTopicReuseStrategy, because we cannot tell whether the user actually configured it (I do not know means in the Java reflection API to tell whether an annotation attribute was actually declared).
If we could tell whether the user actually declared the attribute, we could assume SINGLE in the first case, and assume MULTIPLE in the second case (or even throw an error, requiring the user to configure just one of them).
We cannot assume MULTIPLE, because this would change the behaviour of existing codes like the first case.
We cannot also give precedence for the configuration of fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC because in the second case, it would not make sense to give precedence to a deprecated property.
So I am not being capable of thinking about a way to make RetryableTopicAnnotationProcessor to work fine with the new behaviour of RetryTopicConfigurationBuilder.  :(

I thought about having RetryableTopicAnnotationProcessor to check if both annotation attributes values are "compatible", throwing an error if not, so that only the method  builder.sameIntervalTopicReuseStrategy() would be called. But this would break existing code that just declares fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC, since this would be incompatible with SameIntervalTopicReuseStrategy.MULTIPLE_TOPICS, which must be the default value.

Hi @jgslima, thanks for looking into this.
I might be missing something, but what's on my mind seems a bit simpler:

Both enums default to MULTIPLE_TOPICS
For the new logic, only SameIntervalTopicReuseStrategy is looked up, so no problems there.
For existing logic, we can look at both enum values - if any of them is SINGLE_TOPIC, single topic it is.

My reasoning for the last one is:

Existing logic with SINGLE_TOPIC for fixedDelayTopicStrategy would work as expected;
Existing logic with default values / MULTIPLE_TOPICS would work as expected;
New user logic using SameIntervalTopicReuseStrategy#SINGLE_TOPIC for fixed delays would work as expected
New user logic using SameIntervalTopicReuseStrategy#MULTIPLE_TOPICS for fixed delays would work as expected.

What am I missing?
Thanks.

Tonight I may be able to take a deep dive into your thoughts. At first, one case I can think of is existing code like where the developer declared FixedDelayStrategy.SINGLE_TOPIC, but is in fact using an exponential backoff:
@RetryableTopic(
  backoff = xxx,  // here, a backoff that actually results in exponential.
  fixedDelayTopicStrategy = FixedDelayStrategy.SINGLE_TOPIC
)

For instance, @Backoff may be configured with a delayExpression that sometimes may result in exponential, other times in fixed. Or it is always exponential, and fixedDelayTopicStrategy is there without need.
These cases, currently, result in multiple topics for the maxDelay. By making RetryableTopicAnnotationProcessor to assume single, would change the behaviour.
Later I will try to think about all combinations to see if we can make RetryableTopicAnnotationProcessor to assume the strategy based also on the actual backoff type (it can inspect the actual instance created for the backoff policy).

These cases, currently, result in multiple topics for the maxDelay. By making RetryableTopicAnnotationProcessor to assume single, would change the behaviour.

I don't think RetryableTopicAnnotationProcessor should really assume anything - it's role is to simply create the RetryTopicConfiguration with what's on the annotation. So, if it's FixedDelayStrategy.SINGLE_TOPIC, we just forward it. Same with the new configuration. Both configurations will need to cohexist in the RetryTopicConfiguration class, one being deprecated.
When we get to the point where we check for the strategy, we just check if all backoff values are the same, so if it's an exponential backoff we should simply ignore that configuration.
The fixedDelayTopicStrategy shouldn't have any interference in how the exponential backoff behaves, with old or new logic.
Hope this helps :)
Thanks.

Ok then.
I thought that, if a method is deprecated, ideally the framework should provide a recommended, non-deprecated alternative.
That's why I thought that the new methods in the builder should work to configure for fixed delay as well. Which in turn means a single configuration inside.
Anyway, I will proceed with the simple approach for the deprecation. Existing code that refers to FDS will have to be changed in 3.1.

I believe I have made all the requested changes. Please review. Thanks.

Hello guys. Any news on this? Thank you.

Sorry for the delay; it's on my TODO list, will try to get to it soon.

Pushed requested changes

Correction DestinationTopic.Type is not a public API (not visible).


[release-1.14] Fix backwards incompatible change: include a prometheus service by default

Manual backport of #6699
Kind
/kind bug
Release Note
NONE

/approve
/lgtm

/test pull-cert-manager-release-1.14-e2e-v1-29


MockPipe

Hi!
First of all, many thanks for your library.
When I was creating tests for my angular app, it appeared there was no proper way to mock pipes. Therefore I've created an MockPipe function based on your MockComponent code.
Is this maybe you can use/add in your ng-mock-component code? See below the code:
import {Pipe, PipeTransform} from '@angular/core';

/**
 * Examples:
 * MockPipe('mypipe');
 */
export function MockPipe(name: string): any {
  @Pipe({ name })
  class MockPipe implements PipeTransform {
    transform (input: any): any {
      return input;
    }
  }
  return MockPipe;
}

@cnunciato  Any comment?


Memory management question

In porting my phone app to template10, I have to deal with the user not being required to use the back button to navigate the app. The user can just jump back using the hamburger menu without using the back button, which causes the NavigationMode to be set to "New" instead of "Back". My phone app often does memory management (unhooking event handlers, etc.) when navigating back. Do you have any suggestions on how to do this in template10?

My answer is this. If you are unsure of the nav path the user will take, then you need to unwire events every time OnNavigatedFrom is called in your view-mode and re-wire events every time OnNavigatedTo is called. Again, this is only true if you are using navigation cache, which is an edge case.


OpenTelemetry Traces for Server

Support for OTEL Traces would be nice for running in production setting.
https://github.com/open-telemetry/opentelemetry-rust

if nobody takes this, I will add this myself in coming days.

Would also love to see this implemented 👀


Issue with line breaking

Describe the bug
When there is multiple rows in a cell, then delete the last row, then the words aligment is wrong, especially under "horizontal center" style.
To Reproduce
Steps to reproduce the behavior:

Input multipe rows in the same cell with "alt+enter".
Delete the last row, and the count of ramining rows is more than one.
See the style error.

Screenshots

There is still a small error when the words has DBC case punctuation and SBC case punctuation at the same cell. This lead the last charater showing only half. If we look carefully at the cell, we found in the cell there is a bit larger blank in front of the cell's words.
Screeshot as follow:

Thanks for your report, I'm working on it now

Has been fixed, see #83

Some issues complement:

Alignment is correct, but there is a extra blank row below the last row, so it can not be stay in center when style is vertical centralized.

And when editing the cell, if needing to add new breaking row, input a "alt+enter" there will be two row generated. This support the above issue, though the original issue fixed, but extra blank row staying.

Sorry for that, its our negligence, see #87

Take it easy. You have done a nice job.

Sorry, one more thing.
The style has been fixed, but there is a minor falt with the RC cell value still have a extra "\r\n" in the end of value.
For example, we have a cell with value "test", we input "alt + enter" to add a new row then delete it, the value is expected still be "test", but the value is actually "test\r\n" in the data object. It will be impact other relation styles, such as export to excel, the cell is still with a extra blank row and the cell style is something wrong with this.

You are right, have updated it.

You are right, have updated it.

Thanks, got the fixed.


Increased number of crashes being reported

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
I noticed a significant increase of crashes coming from Alamofire.Session after updating from version 5.1 to version 5.4.
The crash logs point to the method updateStatesForTask(_ task: URLSessionTask, request: Request) and indicate a heap corruption.
Crashed: org.alamofire.session.rootQueue
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000dc52e2890

Alamofire Environment
Alamofire version: 5.4
Xcode version: 12.1
Swift version: 5
Platform(s) running Alamofire: iOS 12/13/14
macOS version running Xcode: 10.15.7

+1

This is likely a duplicate of #3326. It's caused by Firebase Performance or another network performance analytics framework. You'll need to remove or upgrade those frameworks.


Using xcodecoverage for the real device?

Hi,
I'm able to export a nice report for test running on simulator.
But when trying with the actual device, I always get the following errors:
"Reading tracefile Coverage.info
lcov: ERROR: no valid records found in tracefile Coverage.info"
Any suggestion? Thank you

I'm afraid I only run tests on simulator, and never on device. My scripts are designed around this approach.
Take a look at envcov.sh, lines 8-14. Maybe modifying line 11 will help?


No more PR's to main branch

Github Action, to verify if any prs directed to main branch, automatically failing.
Maybe this way, everyone will be able to understand that when you pr to main, you failed.

Isn't it prefered now exept if you want to add applications?
bc according to chris & the changes in the contribute-code you actually should commit a pr into main in some cases.

according to the changes in the contribute-code made by chris it is prefered now exept if you want to add applications.

"prefered", would not be the right word. No need to get salty man, peace.


Implement a tree view for course management

Implement a tree view for course management. Progress of this feature is on the branch feature-tree.
Features

View the complete structure of all courses (including subjects and videos) owned by a single teacher
Drag and drop subjects and videos between courses and re-ordering
Create/Edit/Delete new nodes directly from the tree view
Change status of nodes

Tasks

Front-end for the view
Back-end API
Drag and drop
Create

Course [Note: Needs a suitable UI element to anchor the create button]
Video
Subject

Edit

Course
Video
Subject

Status of nodes

Course
Video
Subject

Re-ordering of nodes

Video
Subject

Moving nodes [Note: Requires #77 to be resolved]

Subjects between courses
Videos between subjects

Copy nodes [Note: Requies #77 to be resolved]

Subjects from course to course
Videos from subject to subject

Progress

Partially live. Moving and copying of nodes still not implemented

Need to be able to copy elements from one course to an other course.


Identify and merge reusable code for the load generators

Maybe we could make use of the Aries Test Harness

Not applicable anymore


remove complete line if becomes empty after removal

replaces https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3604
This add a method to the Tokens class to remove a token and if that causes that the line on which the token was to become completely empty remove that line as well.
Adding this method is in the first commit, the naming is terrible IMHO but lets discuss if the naming is the issue or maybe we want some traits to bring this kind of functionality and not add it to the tokens class.
The other commits show some fixers that benefit from this new method.
There are a bunch of other candidate fixers that could use this new method (from the top of my head);
- useless elseif
- empty comment (blocked by transformer issue)
- header comment (when removing the header comment/PHPDoc)
- ReturnAssignmentFixer
I left those out because of other issues or just because I'm running out of time.

This add a method to the Tokens class to remove a token and if that causes that the line on which the token was to become completely empty remove that line as well.
Adding this method is in the first commit, the naming is terrible IMHO but lets discuss if the naming is the issue or maybe we want some traits to bring this kind of functionality and not add it to the tokens class.

the introduced method is almost 150 lines and it's hard to read/understand/change
We have BC promise under Tokens. We shall not add this method there.
IMHO, similar as we have Analyzers, we can have sth like Manipulators
Let set up the plan for this PR. What about having:

extract new logic from Tokens into separated class
apply to other rules, as well
?

also, it may happen that clearTokenAndMergeSurroundingWhitespace would no longer be needed...

(IMHO, not a prio PR, i was just checking what was it, to know shall I merge it now - let's focus on other PRs first and come back to this one, this one looks more complicated, let's close simpler ones first)

anything left todo here?

@SpacePossum can you take a look at failing test from here: https://github.com/kubawerlos/php-cs-fixer-custom-fixers/pull/218 ?

Could you please add an integration test with single_blank_line_at_eof and one or more other rules proving that the empty line at end of file is not removed?

not sure if I understand, that fixer is not touched in this PR

@SpacePossum Indeed, the new method has to be called si nothing to do, please forget my comment :)

I've put the thing in a class in the Manipulators NS as suggested by @keradus
I don't see much overhead to make the method more easy, it is just dealing with PHP code so....
I also still see a use for clearTokenAndMergeSurroundingWhitespace so not sure why we would want to remove it.
Also removed all the usages and other changes that were in this PR in the hope this can be reviewed and done with first. After that we can start using this to clean up a lot of duplicate code in the various fixers and let even more fixers remove tokens and lines in a better fashion.

@SpacePossum what's the status of this PR? Will we be able to include this in 2.15.6?

Not sure, I'm rewriting this PR for over a year towards the liking of reviewers, but no agreement has been reached this should be added to the code base.

I'd say after changing Manipulators to Manipulator and fix for that failing test I'm for merging this.

:+1: I moved it to the other namespace

@SpacePossum please add this test case:
        [
            '<?php
/* other comment
 */
',
            '<?php
/* other comment
 *//* to remove */
',
        ],

thanks @kubawerlos  ! test and fix added, please review again when you've the time :)

There are still at least 2 problems.
Code like:
<?php
/* remove me */

without any whitespace after the comment is changed to <?php  when should be to <?php\n.
Other is that empty token is added somehow: https://github.com/kubawerlos/php-cs-fixer-custom-fixers/pull/218/checks?check_run_id=811898353 - I'm not sure it's worth investigating and creating test or simple condition before creating token is enough.

without any whitespace after the comment is changed to <?php when should be to <?php\n.

I'm not sure if I agree, shouldn't the complete line be removed by this method?
Second thing is worth looking into, thanks! :)


Can't get user positions

augur-node console log:
{"id":21,"jsonrpc":"2.0","method":"getTradingHistory","params":{"sortBy":"timestamp","isSortDescending":true,"marketId":"0xffba90565a6420d0c4c1fe172dc111fbd10a4cd8"}}
{"id":22,"jsonrpc":"2.0","method":"getSyncData","params":null}
{"id":50,"jsonrpc":"2.0","method":"getCategories","params":{"universe":"0x3d777ea1541a7dec004972b283d53af3633b7531"}}
getter error:  TypeError: Cannot read property 'abs' of undefined
at _.filter (/Users/bthaile/gitrepos/augur-node.git/src/server/getters/get-user-trading-positions.ts:116:46)
at /Users/bthaile/gitrepos/augur-node.git/node_modules/lodash/lodash.js:2935:13
at /Users/bthaile/gitrepos/augur-node.git/node_modules/lodash/lodash.js:4925:15
at baseForOwn (/Users/bthaile/gitrepos/augur-node.git/node_modules/lodash/lodash.js:3010:24)
at /Users/bthaile/gitrepos/augur-node.git/node_modules/lodash/lodash.js:4894:18
at baseFilter (/Users/bthaile/gitrepos/augur-node.git/node_modules/lodash/lodash.js:2934:7)
at Function.filter (/Users/bthaile/gitrepos/augur-node.git/node_modules/lodash/lodash.js:9173:14)
at /Users/bthaile/gitrepos/augur-node.git/src/server/getters/get-user-trading-positions.ts:114:35
at Generator.next ()
at fulfilled (/Users/bthaile/gitrepos/augur-node.git/src/server/getters/get-user-trading-positions.ts:4:58)
{"id":51,"jsonrpc":"2.0","method":"getMarketsInfo","params":{"marketIds":["0x3998d099283e91235b736d75f9d2b64675f2663e","0x9b090fa8fd0b65987d9ae59ea522080636ace896","0x9d3a5181fa79573d5ec7413ffddb49235664a4e2","0x137d755072e1fe35f6c75dc0cd68a6b1544a43fe","0xb6d1a1e0297b26eec8a38d16b73887720eaa4526","0x8e7205e3ad32bcb482dae0e07101921fc9738a3e","0x4208a8a28638b0903ba928d0bc2669c0afd6077f","0xd79eb8739b493058762c3823416b17a7775ea156","0x5caaced8df40e090e1d8d31edda244f7bdcb290d"]}}
{"id":52,"jsonrpc":"2.0","method":"getTradingHistory","params":{"sortBy":"timestamp","isSortDescending":true,"marketId":"0x3998d099283e91235b736d75f9d2b64675f2663e"}}
this occurs when getUserTradingPositions is called from UI, looks like a simple null check is needed but there might be more to it. Not sure if it's a local issue.
options used to call are
{
earliestCreationTime: undefined
latestCreationTime: undefined
orderState: "ALL"
transactionType: "all"
account: '0xbd355a7e5a7adb23b51f54027e624bfe0e238df6'
universe: '0x3d777ea1541a7dec004972b283d53af3633b7531'
}
I'm on pop docker fake time.

looks to be an issue in my local env. I'll keep an eye out.


feature:check json value

What's the purpose of this PR
feature:check json value
Which issue(s) this PR fixes:
Fixes #4142
Brief changelog
to be more specific, I made a short video for it, It works like that.
https://user-images.githubusercontent.com/50099513/184520175-3b8f79d0-335a-44a5-9302-73f1be4d276c.mov
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Read the Contributing Guide before making this pull request.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit tests to verify the code.
[ ] Run mvn clean test to make sure this pull request doesn't break anything.
[ ] Update the CHANGES log.

I have read the CLA Document and I hereby sign the CLA

This feature looks great!
However, I'm wondering is it possible to display the json check button only for potential json values? As I could imagine there will be many check in the future, e.g. yaml check, XML check, etc. The edit modal will look very complicated if there are a lot of checks.

Codecov Report

Merging #4519 (fc3b0b9) into master (4ca9739) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4519      +/-   ##
============================================
- Coverage     53.46%   53.45%   -0.01%
- Complexity     2703     2705       +2
============================================
  Files           490      491       +1
  Lines         15347    15399      +52
  Branches       1598     1596       -2
============================================
+ Hits           8205     8232      +27
- Misses         6585     6607      +22
- Partials        557      560       +3

Impacted Files
Coverage Δ

...ervice/service/ReleaseMessageServiceWithCache.java
84.70% <0.00%> (-1.18%)
:arrow_down:

...p/framework/apollo/biz/service/ItemSetService.java
8.95% <0.00%> (-0.89%)
:arrow_down:

.../apollo/portal/controller/NamespaceController.java
11.82% <0.00%> (-0.40%)
:arrow_down:

...k/apollo/biz/utils/ConfigChangeContentBuilder.java
100.00% <0.00%> (ø)

...ork/apollo/portal/service/AppNamespaceService.java
66.00% <0.00%> (ø)

...mework/apollo/portal/entity/vo/NamespaceUsage.java
51.72% <0.00%> (ø)

...apollo/adminservice/controller/ItemController.java
7.29% <0.00%> (+0.14%)
:arrow_up:

...mework/apollo/portal/service/NamespaceService.java
72.39% <0.00%> (+0.80%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This feature looks great! However, I'm wondering is it possible to display the json check button only for potential json values? As I could imagine there will be many check in the future, e.g. yaml check, XML check, etc. The edit modal will look very complicated if there are a lot of checks.

yeah, you are right, that will be terrible if there were so many check button.   but it is hard to show the check button if the value is not in JSON format, unless the value is in [] or {}, then I can show the check button. What do you think?

@nobodyiam  I have done this feature,  it works like that.
https://user-images.githubusercontent.com/50099513/184789712-94f680e1-5bbc-4972-9d23-a8628ddca026.mov

I have update CHANGES.md and add  json check when modal shown.  @nobodyiam


when parse content '-{ test = test' will show console error

Describe the bug

Version

Browser

[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

Fixed in this PR https://github.com/microsoft/botframework-cli/pull/763. Wait for it's merged into next BF-CLI RC


Added Into{Vec, Rc, Arc}

Thanks.
impl Into<Vec<AsciiChar>> for AsciiString  is so obvious I'm surprised it wasn't there.
I'll switch it to impl From<AsciiString> for Vec<AsciiChar> in a new PR.


(need help)failed to train model with mmdetection

No issue template in General questions. I use the Error report issue Template as follow
Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
if i use V100-16G machine, everything is ok, but A100 machine will report errors after running few steps.(sorry for bad english...)
Reproduction

What command or script did you run?

python tools/train.py configs/coco/coco_config.py

Did you make any modifications on the code or config? Did you understand what you have modified?
here is the coco_config.py

_base_ = '../fcos/fcos_center-normbbox-centeronreg-giou_r50_caffe_fpn_gn-head_1x_coco.py'
model = dict(
    backbone=dict(
        init_cfg=dict(
            type='Pretrained',
            checkpoint='./checkpoints/resnet50_caffe-788b5fa3.pth')))

# Modify dataset related settings
dataset_type = 'CocoDataset'
data_root = '/workdir/wepleo/data/open_datasets/coco/'
data = dict(
    train=dict(
        type=dataset_type,
        ann_file=data_root + 'Annotations/instances_train2017.json',
        img_prefix=data_root + 'images/train'),
    val=dict(
        type=dataset_type,
        ann_file=data_root + 'Annotations/instances_val2017.json',
        img_prefix=data_root + 'images/val'),
    test=dict(
        type=dataset_type,
        ann_file=data_root + 'Annotations/instances_val2017.json',
        img_prefix=data_root + 'images/val'))

optimizer_config = dict(_delete_=True, grad_clip=dict(max_norm=35, norm_type=2))

# We can use the pre-trained model to obtain higher performance
load_from = 'checkpoints/fcos_center-normbbox-centeronreg-giou_r50_caffe_fpn_gn-head_1x_coco-0a0d75a8.pth'

What dataset did you use?
coco

Environment
sys.platform: linux
Python: 3.7.9 (default, Aug 31 2020, 12:42:55) [GCC 7.3.0]
CUDA available: True
GPU 0,1: A100-SXM4-40GB
CUDA_HOME: /usr/local/cuda
NVCC: Build cuda_11.0_bu.TC445_37.28845127_0
GCC: gcc (GCC) 5.4.0
PyTorch: 1.7.0
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2021.3-Product Build 20210617 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v1.6.0 (Git Hash 5ef631a030a6f73131c77892041042805a06064f)
OpenMP 201511 (a.k.a. OpenMP 4.5)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 11.0
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_37,code=compute_37
CuDNN 8.0.3
Magma 2.5.2
Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_VULKAN_WRAPPER -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.8.0
OpenCV: 4.5.4-dev
MMCV: 1.3.15
MMCV Compiler: GCC 5.4
MMCV CUDA Compiler: 11.0
MMDetection: 2.17.0+a5054bd
install pytorch method:
conda install pytorch==1.7.0 torchvision==0.8.0 torchaudio==0.7.0 cudatoolkit=11.0

Error traceback
If applicable, paste the error trackback here.

2021-10-29 11:32:21,262 - mmdet - INFO - Epoch [1][70/58633]	lr: 4.253e-03, eta: 2 days, 14:19:30, time: 0.273, data_time: 0.045, memory: 3046, loss_cls: 0.8306, loss_bbox: 0.5608, loss_centerness: 0.6810, loss: 2.0725
Traceback (most recent call last):
  File "tools/train.py", line 189, in <module>
    main()
  File "tools/train.py", line 185, in main
    meta=meta)
  File "/home/wepleo/code/mmdetection/mmdetection-2.17.0/mmdet/apis/train.py", line 174, in train_detector
    runner.run(data_loaders, cfg.workflow)
  File "/home/wepleo/code/mmdetection/mmcv-1.3.15/mmcv/runner/epoch_based_runner.py", line 127, in run
    epoch_runner(data_loaders[i], **kwargs)
  File "/home/wepleo/code/mmdetection/mmcv-1.3.15/mmcv/runner/epoch_based_runner.py", line 51, in train
    self.call_hook('after_train_iter')
  File "/home/wepleo/code/mmdetection/mmcv-1.3.15/mmcv/runner/base_runner.py", line 307, in call_hook
    getattr(hook, fn_name)(self)
  File "/home/wepleo/code/mmdetection/mmcv-1.3.15/mmcv/runner/hooks/optimizer.py", line 35, in after_train_iter
    runner.outputs['loss'].backward()
  File "/workdir/anaconda3/envs/mmlab/lib/python3.7/site-packages/torch/tensor.py", line 221, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/workdir/anaconda3/envs/mmlab/lib/python3.7/site-packages/torch/autograd/__init__.py", line 132, in backward
    allow_unreachable=True)  # allow_unreachable flag
RuntimeError: CUDA error: an illegal memory access was encountered

Describe the bug if i use V100-16G machine, everything is ok, but A100 machine will report errors after running few steps.(sorry for bad English...)

There are many potential reasons, maybe because of the cuda and Nvidia driver versions. Some versions may have some compatibility issues on A100. Try to upgrade your GPU diver and cuda. Or maybe the GPU has broken.

Describe the bug if i use V100-16G machine, everything is ok, but A100 machine will report errors after running few steps.(sorry for bad English...)

There are many potential reasons, maybe because of the cuda and Nvidia driver versions. Some versions may have some compatibility issues on A100. Try to upgrade your GPU diver and cuda. Or maybe the GPU has broken.

GPU driver version: 460.27.04. The machine and the system worked well when training yolov5.  And I tried to compile mmcv in local, but a compiler version error has occurred. Is there a  version limit of mmcv in A100?

Describe the bug if i use V100-16G machine, everything is ok, but A100 machine will report errors after running few steps.(sorry for bad English...)

There are many potential reasons, maybe because of the cuda and Nvidia driver versions. Some versions may have some compatibility issues on A100. Try to upgrade your GPU diver and cuda. Or maybe the GPU has broken.

GPU driver version: 460.27.04. The machine and the system worked well when training yolov5. And I tried to compile mmcv in local, but a compiler version error has occurred. Is there a version limit of mmcv in A100?

So, the same code works fine on V100 but failed on A100. However, yolov5 is runnable in the same environment. High probability is because of the cuda version. Try to use cuda11.1 or a higher version. But I can not be sure because I do not have an A100 to reproduce this error. Just have a try.

pytorch 1.10
cudatoolkit=11.3
MMCV: 1.3.15
MMCV Compiler: GCC 5.4
MMCV CUDA Compiler: 11.0
MMDetection: 2.17.0+a5054bd
build and install MMCV and MMDetection from source follow the guide, everything is ok now. thank you ~


Repository name

It would be beneficial to give this repository a name other than paper. Maybe something like ShinySSD, that would make it a lot easier for people to find.

done


Document cupyx.errstate()

Currently this function is semi-public in the sense that all linalg routines refer to it for opt-in error checking, but the entry itself is undocumented. We should add it to the Sphinx API list, and also a short snippet to demo how to use it (like this).

We should also note the downside (that led to the current design) of using it: It'd cause synchronization.


MC 1.17 3D Biomes

Seems to work correctly to me, though I'd like to test it with corgi's world gen fork PR before a merge

After testing with corgi's branch this works properly. Ready for merge