enable use of global underscore/lodash

This PR enables you to use a global underscore/lodash library instead of requiring it in to the bundle.
This is useful if loading underscore/lodash from a CDN or a separate bundle that exposes the library as a global as it prevents duplicating the dependency.

Makes sense but I don't like the idea of referencing global. How about if the global option omitted the var all together?

Yeah that is a better solution. I have updated the pull request.

Thanks! Can you squash the commits?

Commits are now squashed. I have also mentioned the new option in the readme as I thought that would be useful.

Thanks!

Published as<EMAIL_ADDRESS>

Awesome! Thanks for accepting the PR :)


Investigate Leveraging Jackson AfterBurner/Blackbird

Investigate adding the Jackson AfterBurner or Blackbird dependencies to offer potentially better deserialization performance.

com.azure:azure-cosmosdb already depends on afterburner... unfortunatelly, afterburner is not compatible with java11. Currently throws warning. Please, consider a forward compatibility for newer versions of java...
NOTE: when cosmos sdk wrapped in com.azure:azure-spring-data-cosmos, then spring data dependency boms brings their own (managed version) of afterburner.
NOTE: There are voices on internet ... which saying that afterburner / blackbird are not neccessary any more...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.fasterxml.jackson.module.afterburner.util.MyClassLoader (file:/xxx/.m2/repository/com/fasterxml/jackson/module/jackson-module-afterburner/2.12.2/jackson-module-afterburner-2.12.2.jar) to method java.lang.ClassLoader.findLoadedClass(java.lang.String)
WARNING: Please consider reporting this to the maintainers of com.fasterxml.jackson.module.afterburner.util.MyClassLoader
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Closing as won't be done


Deregister definitions from factory

Hi, I'm using Typhoon for almost two years already and I'm still very happy with it. We use the default component factory to register all our modules, but I also would like to deregister definition based on a protocol. Is this possible? I couldn't find anything in the API.

Hi @NielsKoole! Happy to hear from you.
We don't have such a feature. It sounds easy to implement, except that Typhoon usually validates assemblies and fails early on startup. . . we'd have to accept that removing an underlying definition (used by others) would create a runtime error.


Unable to open Spyder with Ubuntu

I installed Spyder into a virtualenv on Ubuntu using:
Steps to get Problem

source venv/bin/activate
sudo pip3 install spyder (which you are apparently never supposed to use sudo pip together ever)
spyder3

I get the following errors each time:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-quit'
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
shared memfd open() failed: Function not implemented
Trace/breakpoint trap (core dumped)
I have read that the libGL error is often associated with an Nvidia graphics card which I read here, but I ran the following to check for the problematic driver which would be caused by Nvidia:
sudo ldconfig -p | grep -i gl.so
which outputs:
libwayland-egl.so.1 (libc6,x86-64) => /lib/x86_64-linux-gnu/libwayland-egl.so.1
libcogl.so.20 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcogl.so.20
libQt5OpenGL.so.5 (libc6,x86-64) => /lib/x86_64-linux-gnu/libQt5OpenGL.so.5
libGL.so.1 (libc6,x86-64) => /lib/x86_64-linux-gnu/libGL.so.1
libEGL.so.1 (libc6,x86-64) => /lib/x86_64-linux-gnu/libEGL.so.1

I did not find the nvidia driver amongst these.
Maybe it's the case that one of these libs listed is the problematic one, or I do not have the lib that it wants to run Spyder?

Hi @w142236 seems like some sort of issue related with the driver of you graphics card and maybe is related with using sudo in the installation with pip, could you try to install Spyder in an env without using sudo? What happens if you run the spyder3 command with sudo (sudo spyder3)?
In this kind of cases there is not much we can do but hopefully some of the info above helps :)

Thank you for getting back to me! I am tied up today. I will give that a try and get back to you on Friday afternoon on whether or not that worked.

Without sudo, Spyder works well in an active venv environment:
spyder                        4.1.5
spyder-kernels                1.9.4
My environment: Xubuntu 20.10-beta.

Without sudo, Spyder works well in an active venv environment:
spyder 4.1.5
spyder-kernels 1.9.4
My environment: Xubuntu 20.10-beta.

What do you mean "without sudo"? Using sudo to install spyder or running sudo spyder3 to open it?

I did not use sudo to install spyder.
This command was used:
pip install spyder

I went ahead installed spyder in a new virtualenv using what you suggested.
virtualenv venvspyder
source venvspyder/bin/activate
pip install spyder
spyder3
I still get the same issue:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-quit'
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
shared memfd open() failed: Function not implemented
Trace/breakpoint trap (core dumped)
Maybe how it was installed, whether using sudo or pip, wasn't the issue?

I installed venv this way:
sudo apt install venv
How did you install venv?

dpkg -L python3-venv
/.
/usr
/usr/bin
/usr/share
/usr/share/doc
/usr/share/man
/usr/share/man/man1
/usr/bin/pyvenv
/usr/share/doc/python3-venv
/usr/share/man/man1/pyvenv.1.gz

Previously, I explained how I installed spyder in a venv environment in a piecemeal fashion.  So, I repeated what I did in its entirety in the interest of clarity:
# Start fresh:
sudo apt purge python3-venv
sudo apt autoclean
sudo apt autorermove

# Ground up install of venv:
sudo apt install python3-venv
cd; cd Downloads
python3 -m venv venvspyder
cd venvspyder
source bin/activate

# Install Spyder using pip3
pip install spyder # pip=pip3
which spyder3
     #>>> $HOME/Downloads/venvspyder/bin/spyder3
spyder3 # successfully launches Spyder

I do not know what "virtualenv" is that you used but it has nothing to do with venv.  Maybe you mixed 2 different tools?

Thank you for getting back to me.
I decided to do a fresh uninstall and reinstall of ubuntu to clean everything out and ran the following:
sudo apt-get -y upgrade
sudo apt-get -y update
sudo apt install python3-venv
python3 -m venv venvspyder
cd venvspyder
source bin/activate
pip install spyder
Then I got errors involving building wheels so I control-C'd out of the install and ran:
pip install wheel
pip install spyder
Got an error for psutil and control-C'd out of install again and ran:
sudo apt-get install python3.8-dev -y
pip install psutil
pip install spyder
And it installed without any errors.
I then ran: spyder3
And got the following:
Update LANGUAGE_CODES (inside config/base.py) if a new translation has been added to Spyder
Traceback (most recent call last):
File "/home/quit/venvspyder/lib/python3.8/site-packages/qtpy/QtWebEngineWidgets.py", line 22, in
from PyQt5.QtWebEngineWidgets import QWebEnginePage
ImportError: libsmime3.so: cannot open shared object file: No such file or directory
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/quit/venvspyder/bin/spyder3", line 8, in
sys.exit(main())
File "/home/quit/venvspyder/lib/python3.8/site-packages/spyder/app/start.py", line 200, in main
from spyder.app import mainwindow
File "/home/quit/venvspyder/lib/python3.8/site-packages/spyder/app/mainwindow.py", line 84, in
from qtpy import QtWebEngineWidgets  # analysis:ignore
File "/home/quit/venvspyder/lib/python3.8/site-packages/qtpy/QtWebEngineWidgets.py", line 26, in
from PyQt5.QtWebKitWidgets import QWebPage as QWebEnginePage
ModuleNotFoundError: No module named 'PyQt5.QtWebKitWidgets'
Do I simply install the missing module while inside the venv, or does this issue require additional steps to solve?

@w142236, are you trying to install Spyder in a Docker instance or something? I mention it because it doesn't seem you have the minimal deb packages to run it.

@w142236, are you trying to install Spyder in a Docker instance or something? I mention it because it doesn't seem you have the minimal deb packages to run it.

I don't understand what that means. I installed it as an app off the Microsoft Store if that helps to answer your question. Otherwise I'm not sure. Sorry!

I installed it as an app off the Microsoft Store if that helps to answer your question

@w142236, you should have clarified that from the start. Running Ubuntu through the WSL is very different from a regular installation. That seems to give you a version runs in the command line, not one that can run graphical applications.
Unfortunately, we don't have any experience doing that. So we can offer you further support for your use case, sorry.

I installed it as an app off the Microsoft Store if that helps to answer your question

@w142236, you should have clarified that from the start. Running Ubuntu through the WSL is very different from a regular installation. That seems to give you a version that runs in the command line, not one that can run graphical applications (such as Spyder).
Unfortunately, we don't have any experience doing that. So we can't offer you further support for your use case, sorry.

So is the OS the issue? Would this only work on a Linux computer?

@w142236 maybe this could be useful for your use case: https://techcommunity.microsoft.com/t5/windows-dev-appconsult/running-wsl-gui-apps-on-windows-10/ba-p/1493242 (not totally sure if something there will help to launch Spyder without issue in your WSL Ubuntu instance but let us know if something there helps :) )

Sorry @w142236, what I meant is that we don't know how to install Spyder in WSL. So we can't help you with that.

Hello @w142236 , not sure if this is too late, but I had similar issues recently when installing Spyder on WSL Ubuntu. The only way I got it to work was through anaconda3. So install anaconda 3 for linux and Spyder will be installed automatically as a package. Then you only type spyder as a command, or you can create environments as well.

Also, just in case fro wsl/wsl2, we have some docs regarding the usage of Spyder with wsl2 instances here: https://docs.spyder-ide.org/current/faq.html?highlight=run cell#install-wsl2 (not installing Spyder itself in the wsl2 instance but connecting to a remote kernel started there from you host on Windows)

Xubuntu (ubuntu base + XFCE) 21.10
python3 -m pip install spyder works fine.  No need for anaconda or miniconda.

Also, just in case fro wsl/wsl2, we have some docs regarding the usage of Spyder with wsl2 instances here: https://docs.spyder-ide.org/current/faq.html?highlight=run cell#install-wsl2 (not installing Spyder itself in the wsl2 instance but connecting to a remote kernel started there from you host on Windows)

Can verify this works on WSL1 Ubuntu 20.04 with
spyder 5.3.3
spyder-kernels  2.3.3


Tag commits here with the version of rustc they were released with?

I was trying to make absolutely sure that the registry replacement capability was in beta to resolve this comment, and I had a really hard time figuring out which commit of cargo was released with which version of rustc, as I detailed over in rust-lang/rust-packaging#59.
I got excited for a minute when I saw that there were tags in this repo, but those are cargo versions, not rustc versions.
Could we tag commits in this repo when a rustc release goes out pretty pretty please? 🍨🌸
I don't think github's made a way to send a PR for tags yet, so instead I made commands for someone with push access to copy and paste!! (or alter then copy and paste)
I don't have the SHA for rustc-1.0.0 because buildbot doesn't go back that far, as i mentioned on rust-lang/rust-packaging#59, and I didn't include a tag for rustc-1.12.0 since it hasn't been released yet.
git tag rustc-1.1.0 a48358155c90467ed9c897930dd0da4614605dac
git tag rustc-1.2.0 15b497b10c8261f09f15130595f696fcf29c3619
git tag rustc-1.3.0 553b363bcfcf444c5bd4713e30382a6ffa2a52dd
git tag rustc-1.4.0 833b947016f4fb5269ef4bc5448e4d79eb3b475b
git tag rustc-1.5.0 e1ed9956e079a563796fb380871f4b67619f58ee
git tag rustc-1.6.0 1af03beaffe9be40ae81ca39431c1f1651ef6b02
git tag rustc-1.7.0 9ebfb9b6d2bad7f9640ae012fae686ceeab7b084
git tag rustc-1.8.0 8fc3fd8df3857f3e77454c992458cd7baeeb622b
git tag rustc-1.9.0 10ddd7d5b3080fb0fa6c720cedca64407d4ca2f9
git tag rustc-1.10.0 259324cd8f9bb6e1068a3a2b77685e90fda3e3b6
git tag rustc-1.11.0 6b98d1f8abf5b33c1ca2771d3f5f3bafc3407b93

There should be a Cargo version tag for each release, but is that not enough?

(there's also a direct mapping from a rustc version to a Cargo version)

(there's also a direct mapping from a rustc version to a Cargo version)

Ooooooh. That's what I was missing :( Can I add a note about that to the README?
I checked the SHAs I have above with the SHAs that the cargo repo has tagged and I found some mismatches. For the mismatches, I rustup installed to see which one was actually shipped. One is my mistake; a few others didn't match the tags' SHAs:

rustc version
rustc SHA
cargo SHA
cargo version
match?

1.11.0
6b98d1f
6b98d1f
0.12.0
✅

1.10.0
259324c
259324c
0.11.0
✅

1.9.0
10ddd7d
10ddd7d
0.10.0
✅

1.8.0
8fc3fd8
8fc3fd8
0.9.0
✅

1.7.0
9ebfb9b
28a0cbb
0.8.0
❌ - cargo tag is correct

1.6.0
1af03be
1af03be
0.7.0
✅

❓
❓
c7c4137
0.6.1
❓

1.5.0
e1ed995
e1ed995
0.6.0
✅

1.4.0
833b947
8d21fd2
0.5.0
❌ cargo tag is incorrect

1.3.0
553b363
553b363
0.4.0
✅

1.2.0
15b497b
a2dd2ac
0.3.0
❌ cargo tag is incorrect

1.1.0
a483581
83a6d0e
0.2.0
❌ cargo tag is incorrect

1.0.0
unknown
efb482d
❓
❌ cargo tag is missing

❓
❓
d6dbce7
0.0.1-pre
❓

When I installed rustc 1.4.0, I got cargo --version = cargo 0.5.0-nightly (833b947 2015-09-13), which is the SHA I found from buildbot but not the SHA that is tagged with 0.5.0 here.
Same with rustc 1.2.0: cargo --version = cargo 0.4.0-nightly (15b497b 2015-07-08) (built 2015-07-09), rustc 1.1.0: cargo --version = cargo 0.2.0-nightly (a483581 2015-05-14) (built 2015-05-15) and rustc 1.0.0, which gave me a version that said 0.2.0 when I expected 0.1.0: cargo --version = cargo 0.2.0-nightly (efb482d 2015-04-30) (built 2015-04-29)
Also, what was cargo v0.6.1 for? I was going to guess that it was bumped between beta and stable, but if that was the case I would have expected the released version of rustc 1.5.0 to ship with cargo 0.6.1 but it came with the SHA that the cargo 0.6.0 tag has. Same question with v0.0.1-pre, that didn't seem to go with a rustc release.
Once we get everything matching up, I think a table in cargo's README that has the rustc version and cargo version associations would be helpful-- may I add that?

Hm what's the "rustc SHA" vs "cargo SHA" column? Is that comparing the cargo --version with the tag itself?
For 1.7.0 I get 28a0cbb for both
I think 0.6.1 was only published to crates.io, although I forget why :(. I think was fixing build breakage caused by a breaking change in the compiler?
I suspect I made the wrong tag for rustc 1.4.0 and cargo 0.5.0, can probably change that to 833b947
The cargo 0.3.0 (rustc 1.2.0) tag seems way off, no idea why it's saying it's cargo 0.4.0. Dunno what's going on there :(
Similarly the 0.2.0 tag is way out of sync with rustc 1.1.0's cargo. Also no idea what happened here.
Maybe I was just terrible at tagging in the early days? I vaguely remember we tagged things too early sometimes. I think this happened when I tagged a release when it went to beta, and then during that cycle we fast-forwarded Cargo to pick up bug fixes (but I didn't update the tag). In these cases I should probably update the tag to what we actually shipped.

Oh and as for 0.0.1-pre, I... actually have no idea what that is.

Hm what's the "rustc SHA" vs "cargo SHA" column? Is that comparing the cargo --version with the tag itself?

The rustc SHA in the table is the SHA that I got from looking at buildbot on the date that the rust-packaging/cargo-revs.txt file said it was using; the cargo SHA is the SHA that goes with each cargo tag itself.
I was trying to avoid installing every rustc version, so I didn't bother when the buildbot SHA matched the cargo tag SHA, but I did install the rustc version and then run cargo --version when there was a mismatch to see what was ACTUALLY shipped.

For 1.7.0 I get 28a0cbb for both

Yup, 1.7.0 was my mistake somehow; the SHA I got from buildbot was incorrect.
Wdyt about including the table mapping rustc version to cargo tagged version somewhere? If you're into that, let me know when you've fixed the tags and I'll be happy to make a table :) Thank you!!!!

Sounds good to me! Could you collect an updated list of tags for me to update?

This is what I think should happen, definitely check me:
git tag -f 0.5.0 833b947
git tag -f 0.3.0 15b497b
git tag -f 0.2.0 a483581
git tag 0.1.0 efb482d

I'm assuming we're not going to worry about the version number that cargo --version reports, since that'd be a pain in the butt to update the old releases and it doesn't really matter if the SHAs are the source of truth.

Ok, fixed!


Normalize bookmark url metadata

I understand that you may be totally uninterested in this change. If that is the case, feel free to close this PR.
This PR consists of three commits

First, adding the Link model, and adding the foreign key to bookmark.
Second, migrate the data over to the Link model.
Third, we remove the old fields in Bookmark change the code to only use data from the Link model.

If you have many users on the instance, it's a lot nicer to have normalized data as that data can then be re-used across those users, as it's not user specific.

Thanks for you effort, but I think I'd prefer not going ahead with this and keep the data model simpler. I can't see a lot of benefits to this, presumably there won't be a lot of overlap between user's bookmarks, so the reuse is marginal. On the downside this opens up a lot of potential for new bugs, and makes it harder to maintain in general.


How to change highlighting of folded lines?

I would like to gray out folded lines in my Org files.
I've moved to the treesitter based highlighting and figured out that I can override highlights using:
<EMAIL_ADDRESS>= { fg = colors.blue },
<EMAIL_ADDRESS>= { fg = colors.teal },
<EMAIL_ADDRESS>= { fg = colors.mauve },
<EMAIL_ADDRESS>= { fg = colors.sapphire },
<EMAIL_ADDRESS>= { fg = colors.pink },

However I can't seem to setup the folded line highlighting. What are the highlight groups used for the folded lines?

What Neovim version are you using? Only versions >= 0.10 support highlighting folded lines.

I updated to 0.10.
If I do:
    hi! folded gui=italic guifg=#E78284 guibg=#E78284

it does get the folded lines italic but the coloring is as if they're unfolded (i.e. TODO highlighted and headline highlighted as normal)

it does get the folded lines italic but the coloring is as if they're unfolded (i.e. TODO highlighted and headline highlighted as normal)

And you would like to have it old way?

Currently it's colored:

I'd like to gray out the folded lines like so:

Ah, ok. Nvim 0.10 added support for colored folds, so I added it as a default, since it's the same in Emacs.
I just pushed an option for this, so get the latest master.
You can add it to your orgmode setup to make it the old way:
require('orgmode').setup({
  ui = {
    folds = {
      colored = false
    }
  }
})

Docs: https://github.com/nvim-orgmode/orgmode/blob/master/DOCS.md#folds

Perfect! Hvala puno :pray:


Error: GH action super-linter failed on groovy linter with warnings not real error

GH action linter check start to fail during this weekend.
Have not identify if it is a change made recently in codenarc or the npm-groovy-lint or by  super-linter
which does more changes than before.
so the file not been touched start to show up warnings
and the result seems not only count "error" but also "warnings" so we get failed GH action runs
e.g
2022-10-03 02:24:59 [INFO]   File:[/github/workspace/pipelines/build/common/build_base_file.groovy]
2022-10-03 02:25:11 [ERROR]   Found errors in [npm-groovy-lint] linter!
2022-10-03 02:25:11 [ERROR]   Error code: 1. Command output:
....
npm-groovy-lint results in 1 linted files:
┌─────────┬───────────┬─────────────┐
│ (index) │ Severity  │ Total found │
├─────────┼───────────┼─────────────┤
│    0    │  'Error'  │      0      │
│    1    │ 'Warning' │     60      │
│    2    │  'Info'   │     197     │
└─────────┴───────────┴─────────────┘
Failure: 0 error(s) have been found
 60 warning(s) have been found

2022-10-03 02:25:14 [ERROR]   ERRORS FOUND in GROOVY:[1]

should have "https://github.com/nvuillam/npm-groovy-lint" to set--failon errorso we can ignore warning.
unless we decide to fix all warning

report issue in https://github.com/github/super-linter/issues/3391

For tractability:
so to summarize a bit for what happened for the linter incident (follow the timeline):

10 months ago super-linter enabled "--failon warning" by default for all groovy checks,

on 25th July super-linter released v4.9.5 and a new docker image ghcr.io/github/super-linter:v4.9.5

on 2nd Aug super-linter release a new docker image ghcr.io/github/super-linter:v4.9.6 (https://github.com/github/super-linter/actions/runs/2783363071) ghcr.io/github/super-linter:v4.9.6@sha256:65320e0da6fc983fccdca70cb74cb30bc55797300384ecc82458b42bb8d30828 not really sure if this is a mistake or a different release process?

on 9 Agu: our GH action started to use v4.9.6 image (SHA1: 65320e0da6fc983fccdca70cb74cb30bc55797300384ecc82458b42bb8d30828)

on 15th Aug: npm-groovy-lint add the support for more codenarc rules and also update megalint for the release v10.0.0

on 30th Sep: super-linter released v4.9.6 which bumped version of npm-groovy-lint to v10.0.0 also made another v4.9.6 image (https://github.com/github/super-linter/actions/runs/3161263459/jobs/5146653515) as ghcr.io/github/super-linter:v4.9.6: digest: sha256:251e96e712bb704493e15f1598c0461098445b6eec7454d8bd75bad79e82e93a

on 2nd Oct: we start to see failure on our GH action checks even we use the same v4.9.6 of super-lint but SHA1 has been changed from 65320e0da6fc983fccdca70cb74cb30bc55797300384ecc82458b42bb8d30828  to 251e96e712bb704493e15f1598c0461098445b6eec7454d8bd75bad79e82e93a

My PR linter job got similar output but failed and reported one error. https://github.com/adoptium/ci-jenkins-pipelines/actions/runs/3177396948/jobs/5177786644 . Is that the same issue?

I don't errors now, I think we've fixed all these?


using dotnet ef on published projects

I am working on an asp.net core website on linux. I'd like to be able to use the dotnet ef command on a node where I published the site. The published location just has the site dlls and dotnet ef seems to demand the project.json file be present.
Is this possible or must I use dotnet ef from the original source directory? Is there another tool/script I can leverage to accomplish dotnet ef database update without needing the project.json and incurring a dotnet restore and build?

This is currently not possible. We have https://github.com/aspnet/EntityFramework/issues/646 tracking the ability to have a CLI for compiled applications.


Change the order of DNS servers

The information provided in this article about how to modify the order of the DNS servers is not entirely true.
Reorder DNS server addresses: It's important to verify that you list your DNS servers in the correct order for your environment. DNS servers are used in the order that they're specified in the list. They don't work as a round-robin setup. If the first DNS server in the list can be reached, the client uses that DNS server, regardless of whether the DNS server is functioning properly. Remove all the DNS servers that are listed, and then add them back in the order that you want.
Just removing and adding them in the order you want will not make any changes in the list. The solution is to perform the following:

Remove the DNS servers that are listed, add the 1st DNS server from the new list you want to configure.

Save the configuration ----> Without this step there won't be any changes made

Then add the remaining DNS servers from your list

Save the configuration

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b9cc98dc-ed9e-1759-c5f7-e18722420b69
Version Independent ID: 217f2e7b-80d3-c2ec-3728-fd2264bbb5aa
Content: Create, change, or delete an Azure virtual network
Content Source: articles/virtual-network/manage-virtual-network.md
Service: virtual-network
GitHub Login: @asudbring
Microsoft Alias: allensu

Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We will create an internal tracking work item to address this issue. For now, we are closing this issue. If you have any additional information you would like to provide, please respond to this issue with any additional details.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Screen Text Extractor Seeing 'Y's as 'U's

Microsoft PowerToys version
0.82.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
TextExtractor
Steps to reproduce
Any time I use Text Extractor
✔ Expected Behavior
To copy text as it appears on screen
❌ Actual Behavior
Reading Ys as Us
Other Software
No response

This issue is with the underlying OCR Engine and fixing it is beyond the scope of this project. For more accurate OCR results use the Windows 11 Snipping Tool.


Making it explicit that opacity is only supported in macOS

PR is ready to be merged.
Makes it more explicit that background colour opacity is not supported in windows/linux.
Related to #2451

Thank you @AndreFCruz for this first contribution! 🙏 ❤


Linking (phone, email, geo)

It's is possible to use Linking interface with this tool?
In the documentation https://facebook.github.io/react-native/docs/linking.html there is an advice

NOTE: On iOS you'll need to link RCTLinking to your project by following the steps described here. In case you also want to listen to incoming app links during your app's execution you'll need to add the following lines to you *AppDelegate.m:

NOTE: As of iOS 9, your app needs to provide the LSApplicationQueriesSchemes key inside Info.plist or canOpenURL will always return false

it's possible to implement Linking using create-react-app/Expo ?

It should work without making any of the native-side changes, but we don't officially support it yet. The docs should be clearer in the near future and we'll have a guide on the Expo site at some point soon.

indeed it will just work out of the box without adding any of those things on the native side


State machine two-state transitions.

Currently, in the state machines (transfer manager, contract negotiation managers) there are two ways of handling state transitions in processing:
2-states
e.g. https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/fb222eb159110ac03e6c616c8556c3cf0311ca32/core/contract/src/main/java/org/eclipse/dataspaceconnector/contract/negotiation/ConsumerContractNegotiationManagerImpl.java#L329-L335
the negotiations in CONSUMER_OFFERING state are fetched from the nextForState method and leased, then they are sent to the provider and the state will transfer to another one only on the completion of the async operation.
3-states
e.g. https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/fb222eb159110ac03e6c616c8556c3cf0311ca32/core/contract/src/main/java/org/eclipse/dataspaceconnector/contract/negotiation/ConsumerContractNegotiationManagerImpl.java#L311-L318
the negotiations in INITIAL state are fetched from the nextForState method and leased, then immediately updated to PROCESSING and unleased and then sent to the provider. On async operation completion the state will change again
Choice
We decided to migrate all the state transition to the first case (2-states) because the 3-state has this point of failure: if the edc breaks after moving the state to PROCESSING, the entity will remain there undefinitely.
Using the 2-states transition we would avoid staling entities, because every state will have its process method that fetches the unleased entities in that state and process them.
To permit this pattern we have to ensure that all the async service calls are idempotent. This is already an EDC requirement.

As a pattern there must be an -ING state and an -ED state, e.g. PROCESSING and PROCESSED. Issue #818 relates here too.

See also https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/336#issuecomment-1060026575 which can build on this.


-iree-vm-bytecode-module-strip-symbols=true causes execution failure

Add -iree-vm-bytecode-module-strip-symbols=true in iree-translate causes execution failure
In iree/samples/simple_embedding/simple_embedded_dylib
$ ./simple_embedding_dylib
/usr/local/google/home/hcindyl/Projects/iree-dev/iree/iree/vm/bytecode_module.c:166: INVALID_ARGUMENT; mismatched internal_functions/function_descriptors vectors (0 != 2)

Darn, the reflection info is currently embedded on internal function defs - it should be on exports (ended up there due to weird reasons) - I'll work on fixing that so we can drop the table.


Set up Travis CI?

And make it test for last 3 GHC versions (7.6, 7.8, and 7.10, though 7.10 isn't actually out yet...).

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9201478-set-up-travis-ci?utm_campaign=plugin&utm_content=tracker%2F332399&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F332399&utm_medium=issues&utm_source=github).

Base it on build.sh and https://github.com/hvr/multi-ghc-travis ?

Based on my cursory glance here, it seems like it supports several versions at once, but I'm not sure.

Here is a .travis.yml that I use for the Ebnf package I maintain and test for three versions of GHC: https://github.com/FranklinChen/Ebnf2ps/blob/master/.travis.yml

Embarrassingly, my .travis.yml is actually out of date and fails on 7.8.4 :-). I'm in the middle of fixing it.

I got my project's .travis.yml working for 7.8.x and lower, but not yet for 7.10.x because of the big Prelude change it seems (since I don't use 7.10.x yet). But the updated template seems to work well otherwise.


[RMP] Session based recommenders

Merlin-models(Data Scientist)
update merlin-models to leverage transformers4rec
NVTabular(Data Scientist)
Session based ops for feature engineering.
Merlin-systems(Product Engineer)
Merlin-orchestration(Infra Engineer)
Examples and Docs(Everyone)
Aha! Link: https://nvaiinfa.aha.io/features/MERLIN-827

There is another ticket for Session based.


Create 1.3.3 release

[x] Prepare istio/cni.

[x] Check whether the same istio/api commit is used in istio/istio and istio/proxy.git clone git@github.com:istio/istio.git
pushd istio
git checkout release-1.3
export ISTIO_API_SHA_ISTIO=$(sed -n 's,^.*istio\.io/api v0.0.0-[^-]*-,,p' go.mod)
export ISTIO_PROXY_SHA_ISTIO=$(jq -r '.[] | select(.repoName == "proxy") | .lastStableSHA' < istio.deps)
export GO_CONTROL_PLANE_SHA=$(sed -n 's,^.*github.com/envoyproxy/go-control-plane [^-]*-[^-]*-,,p' go.mod)
popd

git clone git@github.com:istio/proxy.git
pushd proxy
git checkout $ISTIO_PROXY_SHA_ISTIO
export ISTIO_API_SHA_PROXY=$(git rev-parse --short=12 $(sed -n 's,^ISTIO_API = "\([^"]*\)".*$,\1,p' < repositories.bzl))
export ENVOY_SHA_PROXY=$(sed -n 's,^ENVOY_SHA = "\([^"]*\)".*$,\1,p' < WORKSPACE)
popd

test "$ISTIO_API_SHA_ISTIO" != "$ISTIO_API_SHA_PROXY" && echo "different istio/api commits in istio/istio and istio/proxy"

[x] Check whether the version of Envoy from which the go-control-plane's API has been extracted from is no more than a few days older to the version of Envoy used in istio/proxy.git clone git@github.com:envoyproxy/go-control-plane.git
pushd go-control-plane
git checkout $GO_CONTROL_PLANE_SHA
export DATA_PLANE_API_SHA=$(git submodule | sed -n 's,^-\([^ ]*\) data-plane-api.*$,\1,p')
popd

git clone git@github.com:envoyproxy/data-plane-api.git
pushd data-plane-api
git checkout $DATA_PLANE_API_SHA
export ENVOY_SHA_DATA_PLANE_API=$(git log -1 | sed -n 's,^.*Mirrored from.*envoy @ ,,p')
popd

echo "Envoy SHA used in istio/proxy: https://github.com/istio/envoy/commit/$ENVOY_SHA_PROXY"
echo "Envoy SHA used in envoyproxy/go-control-plane: https://github.com/envoyproxy/envoy/commit/$ENVOY_SHA_DATA_PLANE_API"

If the versions are different, you'll have to update the version used in istio/istio or istio/proxy to use the most recent version in both repos.
[x] Check whether the API commit SHA is the same in both repositories.bzl and istio.deps in istio/proxy.pushd proxy
git checkout $ISTIO_PROXY_SHA
export API_COMMIT_IN_REPOSITORIES=$(sed -n 's,^ISTIO_API = "\([^"]*\)".*$,\1,p' < repositories.bzl)
export API_COMMIT_IN_DEPS=$(jq -r '.[] | select(.repoName == "api") | .lastStableSHA' < istio.deps)
test "$API_COMMIT_IN_REPOSITORIES" != "$API_COMMIT_IN_DEPS" && echo "different API commits"
popd

[x] Update the SHAs in istio/proxy. All SHAs should ideally be updated in a single PR since it takes ~1.5 hours to build an image after it is merged.

[x] If necessary, update the version of Envoy used in istio/proxy. Update WORKSPACE and istio.deps with the same SHA. The SHA must exist in the istio/envoy:release-1.3 branch. WORKSPACE
[x] If the istio/api SHAs are different within istio/proxy between repositories.bzl and istio.deps, fix it in istio.deps.
[x] If the istio/api SHA is behind the one used in istio/istio, replace the SHA in both repositories.bzl and istio.deps to use the same as in istio/istio.

[x] Update the SHAs in istio/istio. All SHAs should ideally be updated in a single PR to ensure consistency.

[x] If the version of API used in the go-control-plane version is too far behind the Envoy version used in istio/proxy:

[x] If necessary, first create a new release of go-control-plane that uses the same API version as the Envoy version used in istio/proxy.
[x] Update the go-control-plane version in istio/istio in go.mod.

[x] If necessary, update the istio/proxy SHA in istio/istio in istio.deps. istio.deps
[x] Update the istio/cni SHA in istio/istio in istio.deps. This SHA must be the HEAD of the release-1.3 branch. The release script pulls the HEAD of the branch, not this specific SHA, but the SHA is printed out in the release manifest, so it's better to keep it consistent.

[x] Build the release by updating the monthly/release_params.sh parameters to use the SHA of the HEAD of istio.istio:release-1.3, and the 1.3.3 version. https://github.com/istio-releases/pipeline/pull/1316git clone git@github.com:istio/istio.git
pushd istio
git checkout release-1.3
export ISTIO_SHA=$(git rev-parse HEAD)
popd

git clone git@github.com:istio-releases/pipeline.git
pushd pipeline
git checkout release-1.3
git checkout -b create-1.3.3-release
sed -e 's/CB_BRANCH=.*$/CB_BRANCH=release-1.3/' \
    -e 's/CB_COMMIT=.*$/CB_COMMIT='$ISTIO_SHA'/' \
    -e 's/CB_VERSION=.*$/CB_VERSION=1.3.3/' \
    -i monthly/release_params.sh
git add monthly/release_params.sh
git commit -m 'Build release 1.3.3'
git push --set-upstream origin create-1.3.3-release
popd

Wait until the build finishes and is available in https://gcsweb.istio.io/gcs/istio-prerelease/prerelease/1.3.3/ and in draft state in https://github.com/istio/istio/releases.
[x] Run the long-running tests on the build. (owners: @mandarjog, @howardjohn, @JimmyCYJ, @Stono)
[x] Publish the release in the GitHub UI. Use the edit button on the draft release in https://github.com/istio/istio/releases. Make sure the pre-release box is unchecked.
[x] Update the documentation in istio/istio.io.

[x] Create a release note in the master branch, then cherry-pick to the release-1.3 branch. PR is here: https://github.com/istio/istio.io/pull/5122
[x] Update the full_version number in data/args.yaml in the release-1.3 branch.

[x] Update the release in GitHub to point the RELEASE NOTES link to the right release note page.
[x] Publish announcements about the release. (owner: @oaktowner)

1.3.3 has been released and announced: https://istio.io/news/2019/announcing-1.3.3/.


perf: in-memory public files check

Description
Around 4% of the time when running https://github.com/yyx990803/vite-dev-server-perf is spent on the serve public middleware.
This middleware will check every request before getting into the transform pipeline. Internally, it uses sirv, which does a fs.existsSync check for both filePath and filePath + '/index'. It seems that we can't configure it to avoid the /index suffix check, which I don't think we should be serving from the public dir. Even if this is fixed, there will still be a toll for every request because of the public dir feature.
This PR reads the public dir recursively on server start and keeps an in-memory set of all public files so we can avoid going through sirv.
The drawback is that a server restart is needed if new files are added to the public directory. If we want to move forward with this PR, we could decide to watch the public dir and add new files.
We are currently patching sirv to add a shouldServe option, so we can do a case check in case-insensitive platforms. If we merge this PR, we can also remove this patch and the check because the in-memory map will already filter these out.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

@ArnaudBarre is telling me he implemented the same (+the watcher) in rds: https://github.com/ArnaudBarre/rds/blob/main/src/server/public.ts, we should check rds more often :)

For ideas only, most of my implementations where never tested on Windows 👀
But that's from there I also bring the idea of using one big file watcher, having used multiple dedicated watcher (public, config, src) worked well and allowed to keep things independent (even if the entry point is a complicated merge of all, it really misses the plugin architecture of Vite)

The watcher is now used to delete/add publicFiles to the in-memory cache, and the cache is also used in checkPublicFile when available (in dev, but later on we could add it to build time too if we'd like).
The publicFiles don't have the publicDir prefixed in the set, so we avoid path.join calls to do the checks.

We can't remove the shouldServe patch because it is used during preview too (at least in this PR, but it is removed now from the serve public middleware)

/ecosystem-ci run

Here's the results of https://github.com/yyx990803/vite-dev-server-perf on my Windows machine. It's around 3%.

before
1000 TS modules (50x20) loaded in: 1167ms (runs: [1387,1181,1167,1166,1160])
1000 TS modules (20x50) loaded in: 1086ms (runs: [1161,1086,1078,1082,1099])
2000 TS modules (100x20) loaded in: 2530ms (runs: [2632,2530,2523,2504,2543])
5000 TS modules (250x20) loaded in: 6675ms (runs: [7346,6790,6630,6598,6675])
10000 TS modules (400x25) loaded in: 13616ms (runs: [15038,13693,13616,13447,13249])

after
1000 TS modules (50x20) loaded in: 1150ms (runs: [1521,1162,1131,1132,1150])
1000 TS modules (20x50) loaded in: 1025ms (runs: [1069,1025,1058,997,1013])
2000 TS modules (100x20) loaded in: 2424ms (runs: [2562,2426,2424,2403,2400])
5000 TS modules (250x20) loaded in: 6524ms (runs: [6957,6547,6524,6462,6517])
10000 TS modules (400x25) loaded in: 13286ms (runs: [14343,13192,13206,13290,13286])

Here's the results of yyx990803/vite-dev-server-perf on my Windows machine. It's around 3%.

Thanks for benchmarking! That isn't bad 🙌🏼

It depends on when we start 5.1 beta for me. If we are starting in a week, then I'd say let's wait for that.

It depends on when we start 5.1 beta for me. If we are starting in a week, then I'd say let's wait for that.

I don't think we have enough minor-only PRs yet to justify starting work on 5.1, so let's go with this one in a patch then.

The drawback is that a server restart is needed if new files are added to the public directory. If we want to move forward with this PR, we could decide to watch the public dir and add new files.

This seems like a user-hostile change that feels like a regression given that it comes as a patch release. It does not match expectations that people have about Vite, considering that it doesn't work like that for source code. If you are sticking with this approach, how about integrating the behavior of vite-plugin-restart for the public/ folder?

@cpojer I implemented watching of public files before this PR was merged, see https://github.com/vitejs/vite/pull/15195#issuecomment-1834551595
Are you seeing a regression? The public dir should work in the same way as before.
We're probably going to remove this approach once we merge https://github.com/vitejs/vite/pull/15279, as we can use that same cache for the checks (that is more performant when there are symlinks)

Oh fantastic, sorry I missed that change was part of this PR already 🤦♂


& in user names causes mentions to miss text property

Versions
SDK 4.8
nodejs v10.20.1
Describe the bug
Teams allows the & character in user names. When a user sends a message to a bot and mentions a user with the & character, the entities mention object is missing the 'text' property (<at>username</at>) causing functions like TurnContext.removeMentionText to fail.
To Reproduce
Create a user in Teams called "Test ($~&)"
Send a message to your bot while @ mentioning the user above
The message received by the bot contains the mention in entities but the 'text' property is missing:
{ mentioned:
     { id:
        '29:16xB25CaNg2TuYGVNbiEyHpb5T5N9-5al1bghslxHEhlc8FE-2EizBGV9a-YI9Z8V4JtgLbQmFp1VCJG92UDFRw',
       name: 'Test ($~&)' },
    type: 'mention' }

Expected behavior
text property should be <at>Test ($~&)</at>
{ mentioned:
     { id:
        '29:16xB25CaNg2TuYGVNbiEyHpb5T5N9-5al1bghslxHEhlc8FE-2EizBGV9a-YI9Z8V4JtgLbQmFp1VCJG92UDFRw',
       name: 'Test ($~&)' },
    type: 'mention',
    text: '<at>Test ($~&)</at>' }

@EricDahlvang can you please take a look at this?

Hi @matthiasdilger
Thank you for reporting this.  It appears to be an issue on the Teams side.  I've printed the entire incoming post's body to the output window and my user's mentioned entity has no < or >
{
  "text": "<at>Bot Health Test</at> <at>Eric Dahlvang (Murphy & Associates)</at>test3\n",
  "textFormat": "plain",
  "attachments": [
    {
      "contentType": "text/html",
      "content": "

Bot Health Test Eric Dahlvang (Murphy & Associates)test3
\n
"
    }
  ],
  "type": "message",
  "timestamp": "2020-04-23T19:50:47.719696Z",
  "localTimestamp": "2020-04-23T19:50:47.719696Z",
  "id": "1587671447694",
  "channelId": "msteams",
  "serviceUrl": "https://smba.trafficmanager.net/amer/",
  "from": {
    "id": "29:xxx",
    "name": "Michael Richardson (TEKsystems)",
    "aadObjectId": "xxx"
  },
  "conversation": {
    "isGroup": true,
    "conversationType": "channel",
    "tenantId": "xxx",
    "id": "19:xxx@thread.skype;messageid=1587670878861"
  },
  "recipient": {
    "id": "28:3851a47b-53ed-4d29-b878-6e941da61e98",
    "name": "Bot Health Test"
  },
  "entities": [
    {
      "mentioned": {
        "id": "28:3851a47b-53ed-4d29-b878-6e941da61e98",
        "name": "Bot Health Test"
      },
      "text": "<at>Bot Health Test</at>",
      "type": "mention"
    },
    {
      "mentioned": {
        "id": "29:xxx",
        "name": "Eric Dahlvang (Murphy & Associates)"
      },
      "type": "mention"
    },
    {
      "locale": "en-US",
      "country": "US",
      "platform": "Windows",
      "type": "clientInfo"
    }
  ],
  "channelData": {
    "teamsChannelId"<EMAIL_ADDRESS>    "teamsTeamId"<EMAIL_ADDRESS>    "channel": {
      "id"<EMAIL_ADDRESS>    },
    "team": {
      "id"<EMAIL_ADDRESS>    },
    "tenant": {
      "id": "xxx"
    }
  },
  "locale": "en-US"
}

Moving this to the BotFramework-Services repository.  I'll raise this internally with the Teams team.


Dense disparity ground truth map

Hi, I interestingly read your impressive paper!
While I was reading your paper and seeing the results, I happened to be curious how you obtain the dense disparity ground truth. The paper only describes you also train and test your method using the entire ground truth, taking into account all locations, including those without events.
I ask you for explaining the process more in detail. In addition, are there any lines of code describing the process?
Thank you for your answer in advance!

Correct me if I am wrong --- I think you are looking for this line.
Disclaimer: I am not the author. I am another reader interested in this project. Please take it with a grain of salt.


Copy Command vs. Polybase: DIUs

My understanding is that the copy command is just shorthand code for polybase...nothing different under the hood, however I've noticed that when copying 1 file to Synapse the copy command always uses 4 DIUs whereas polybase always uses 2 DIUs. They seem to take the same amount of time...so why does the company command use 2x DIUs?
All this says to me is that I should use Polybase because the copy command will cost me twice as much at the same performance (at least in ADF).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5f8f06db-58d4-75b9-f150-9a1b4767cf75
Version Independent ID: 54c26e53-460a-2f6e-b4f2-86f1e8581435
Content: Copy activity in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/copy-activity-overview.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@mwc360 Thank you for your query. We will investigate and update this thread further.

@linda33wj Can you please take a look at this?

@mwc360 Good catch and thanks for your feedback! We are making a change to by default use 2 DIUs instead of 4 for copy into Synapse via COPY cmd, which will behave the same as using PolyBase. Expect it taking effect in a week or so.
Related tip, if the default effective DIU number doesn't meet your requirement or expectation, you can always explicitly set it on Copy activity settings. Refer to https://docs.microsoft.com/en-us/azure/data-factory/copy-activity-performance#data-integration-units
#please-close


[gardening] Put white spaces in between if/while clauses and braces where it is missing.

What's in this pull request?
[gardening] Put white spaces in between if/while clauses and braces where it is missing.
For instance:
'if (foo){' => 'if (foo) {'
Sans any of those 80+ line violations.

Good gardening idea!
@swift-ci Please test and merge :-)

Thanks @wxxsw!


Homepage is broken

http://swimlane.github.io/angular-data-table/
TypeError: Cannot read property 'internal' of undefined
at HeaderController.styles (dataTable.helpers.js:1298)
at angular.min.js:198
at Object. (angular.min.js:109)
at l.$digest (angular.min.js:123)
at l.$apply (angular.min.js:126)
at l (angular.min.js:81)
at S (angular.min.js:85)
at XMLHttpRequest.D.onload (angular.min.js:86)

Does this happen when u run it locally?

No, this is what happens when I go to the above mentioned website. =)

I thought this was a known issue. None of the samples have worked on Chrome for several days. They work fine on IE 11.

Is it site only? The codepen didn't work either.

Same here. Demo on this page doesn't work on Chrome or Safari on Mac. Doesn't work on codepen either. Can someone confirm that things work for them locally on all browsers? FYI on Chrome, I see this error:
Uncaught ReferenceError: babelHelpers is not defined

+1

Why is this closed? Are you really planning not to support Chrome? Actually currently the home page for the demo doesn't work on Chrome 46.x, Firefox 40.0.3 and ie 11. Some of the demos work on some of the browsers, but all Browsers seem to have issues with at least a few of the demos.

@f1tech  This isn't closed. #88 is, which is a duplicate of this.

+1

Demos should be working again.

I am also getting Uncaught ReferenceError: babelHelpers is not defined and I am on version
@version v0.4.8

Getting this too

shuld be fixed now

+1, trying to use with Angular 1.4.2 without any luck.


Allow publishing of CSS images via HTML Design build

Following http://tridion.stackexchange.com/questions/13049/how-to-display-design-images-that-are-not-published-as-part-of-a-component the HTML design build currently discards any images (to prevent the example images, which are content, to be published), but it would be very useful to allow images that are part of the design (like sprites).

TSI-862 (internal issue ID for tracking purposes)


Infinite activation while training on 64x64 CelebA

Using python 3.6.9 and packages as advised in README, I tried to train from scratch with:
python ./scripts/compute_tfrecord.py --dataset celeba --resolution 64
python ./fid_utils/precalc_fid_stats.py --dataset celeba --data_path "./data/CelebA/*" --resolution=64
python main.py --config="./configs/CelebA_64x64_N2M2S32.yaml"

I didn't set up the number of epochs as advised in the yaml.
The training started and continued for quite some time, the tensorboard looks fine I think?

However, after exactly 130000 steps there was an error, the traceback of which I post below. Any idea why this happened?
[CelebA_64x64_N2M2S32] [Epoch: 54; 1261/2384; global_step:129997] elapsed: 64138.1083, d: -1490.8943, g: -139648.8750, q: 0.0000
[CelebA_64x64_N2M2S32] [Epoch: 54; 1262/2384; global_step:129998] elapsed: 64138.4170, d: 151.7455, g: -136700.0781, q: 0.0000
[CelebA_64x64_N2M2S32] [Epoch: 54; 1263/2384; global_step:129999] elapsed: 64138.7237, d: 741.5792, g: -140252.2188, q: 0.0000
[CelebA_64x64_N2M2S32] [Epoch: 54; 1264/2384; global_step:130000] elapsed: 64139.0329, d: -1249.9255, g: -138572.9062, q: 0.0000
 62%|█████████████████████████████████████████████████████████████████▉                                         | 482/782 [09:07<05:41,  1.14s/it]2020-07-27 08:41:02.094112: E tensorflow/core/kernels/check_numerics_op.cc:185] abnormal_detected_host @0x7f19ed960100 = {1, 0} activation input is not finite.
 62%|█████████████████████████████████████████████████████████████████▉                                         | 482/782 [09:08<05:41,  1.14s/it]
2020-07-27 08:41:02.107534: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.107596: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.107654: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.107891: W tensorflow/core/kernels/queue_base.cc:277] _0_input_producer: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108087: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108192: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108304: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108340: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108361: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108384: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108420: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108443: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108464: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108487: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108511: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108532: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
2020-07-27 08:41:02.108555: W tensorflow/core/kernels/queue_base.cc:277] _1_shuffle_batch/random_shuffle_queue: Skipping cancelled enqueue attempt with queue not closed
Traceback (most recent call last):
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1334, in _do_call
    return fn(*args)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1319, in _run_fn
    options, feed_dict, fetch_list, target_list, run_metadata)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1407, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: activation input is not finite. : Tensor had NaN values
	 [[{{node FID_Inception_Net/mixed_4/tower/conv_2/CheckNumerics}}]]
	 [[{{node FID_Inception_Net/pool_3}}]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 131, in <module>
    trainer.train(logger, evaluator, global_step)
  File "/home/janek/Documents/COCO-GAN/trainer.py", line 419, in train
    z_iter, z_fixed, feed_dict_iter, feed_dict_fixed)
  File "/home/janek/Documents/COCO-GAN/logger.py", line 207, in log_iter
    cur_fid = evaluator.evaluate(trainer)
  File "/home/janek/Documents/COCO-GAN/evaluator.py", line 71, in evaluate
    batch_features = fid.get_activations(gen_full_images, self.sess, self.batch_size)
  File "/home/janek/Documents/COCO-GAN/fid_utils/fid.py", line 125, in get_activations
    pred = sess.run(inception_layer, {'FID_Inception_Net/ExpandDims:0': batch})
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 929, in run
    run_metadata_ptr)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1152, in _run
    feed_dict_tensor, options, run_metadata)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1328, in _do_run
    run_metadata)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1348, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: activation input is not finite. : Tensor had NaN values
	 [[node FID_Inception_Net/mixed_4/tower/conv_2/CheckNumerics (defined at /home/janek/Documents/COCO-GAN/fid_utils/fid.py:45) ]]
	 [[node FID_Inception_Net/pool_3 (defined at /home/janek/Documents/COCO-GAN/fid_utils/fid.py:45) ]]

Caused by op 'FID_Inception_Net/mixed_4/tower/conv_2/CheckNumerics', defined at:
  File "main.py", line 115, in <module>
    evaluator.build_graph()
  File "/home/janek/Documents/COCO-GAN/evaluator.py", line 45, in build_graph
    fid.create_inception_graph(inception_path)
  File "/home/janek/Documents/COCO-GAN/fid_utils/fid.py", line 45, in create_inception_graph
    _ = tf.import_graph_def( graph_def, name='FID_Inception_Net')
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/framework/importer.py", line 442, in import_graph_def
    _ProcessNewOps(graph)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/framework/importer.py", line 235, in _ProcessNewOps
    for new_op in graph._add_new_tf_operations(compute_devices=False):  # pylint: disable=protected-access
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3433, in _add_new_tf_operations
    for c_op in c_api_util.new_tf_operations(self)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3433, in <listcomp>
    for c_op in c_api_util.new_tf_operations(self)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3325, in _create_op_from_tf_operation
    ret = Operation(c_op, self)
  File "/home/janek/Documents/COCO-GAN/coco_venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1801, in __init__
    self._traceback = tf_stack.extract_stack()

InvalidArgumentError (see above for traceback): activation input is not finite. : Tensor had NaN values
	 [[node FID_Inception_Net/mixed_4/tower/conv_2/CheckNumerics (defined at /home/janek/Documents/COCO-GAN/fid_utils/fid.py:45) ]]
	 [[node FID_Inception_Net/pool_3 (defined at /home/janek/Documents/COCO-GAN/fid_utils/fid.py:45) ]]

I've never see this before, and seems awkward to me.
The error is raised while computing the FID score.
Especially the generator loss is finite, which indicates the problem is neither caused by gradient explosion nor numerical problems during training.
Could you run the experiment again to see if it happens again?
Note that our codes should be able to automatically recover from the latest checkpoint of your experiment.

Thank you for your answer, how can I enable running from checkpoint? Or is
it done automatically?
On Mon, 27 Jul 2020 at 12:09, HubertLin<EMAIL_ADDRESS>wrote:

I've never see this before, and seems awkward to me.
The error is raised while computing the FID score.
Especially the generator loss is finite, which indicates the problem is
neither caused by gradient explosion nor numerical problems during training.
Could you run the experiment again to see if it happens again?
Note that our codes should be able to automatically recover from the
latest checkpoint of your experiment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hubert0527/COCO-GAN/issues/13#issuecomment-664257803,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA5UZRP4VUIWONYE754NWLR5VG6XANCNFSM4PIQNLQA
.

Automatically, just run the same training command. The messages on the console will tell you if it finds and recovers from a checkpoint.

Seems to have worked, I'm on epoch 55 and >132000 global step. Guess it was
a kind of anomaly.
On Mon, 27 Jul 2020 at 12:17, HubertLin<EMAIL_ADDRESS>wrote:

Automatically, just run the same training command. The messages on the
console will tell you if it finds and recovers from a checkpoint.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hubert0527/COCO-GAN/issues/13#issuecomment-664266882,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA5UZRWAXDVO75F67VI3GDR5VH3BANCNFSM4PIQNLQA
.


Ptz motions repeated twice

Hey I have a few v380 ptz cameras and things are working good but it seems like after some recent update all pan actions are repeated twice when i use the overlay of this component to move them. Other integrations still move normally. I can tell the motion is sent twice because the camera moves twice as far as it used to and also it discretely moves in two bursts

You need to log problem somehow. You can check browser developer console

I think the problem same #312


Installing RethinkDB as Windows service

We just merged support for running RethinkDB as a Windows service (https://github.com/rethinkdb/rethinkdb/issues/5810).
We should explain this in https://rethinkdb.com/docs/start-on-startup/ and maybe mention it on the Windows install page as well.
The process for setting up RethinkDB as a service is as follows:

Create a configuration file for the RethinkDB server. A template can be downloaded from https://github.com/rethinkdb/rethinkdb/blob/next/packaging/assets/config/default.conf.sample . At least the directory line should be specified. All other settings are optional. If directory is not specified, RethinkDB will put its data in c:\Windows\System32\rethinkdb_data, which is probably not what users want. To test a configuration file before using it as a service, you can run rethinkdb.exe --config-file <path to config file> manually.
Open a command line, go to the location of the rethinkdb.exe executable, and run:
rethinkdb.exe install-service --config-file <path to config file>
RethinkDB will install a service under the name rethinkdb_default and start it. You can use Windows' service manager to Monitor the status of the RethinkDB service, or to stop and/or restart it later. By default, the RethinkDB service will automatically start when the system starts.

Some relevant notes:

The service created by rethinkdb.exe install-service relies on rethinkdb.exe and on the config files to remain in the locations where they were when rethinkdb.exe install-service were called. If one of these files gets moved, the service must be re-installed (run rethinkdb.exe remove-service first).
Changes in the configuration file after the initial install will take effect when the service is restarted.
By default, the service is installed to run with System user privileges. For improved security, the service can be installed with a different user account. This can be done as follows:
rethinkdb.exe install-service --config-file <path to config file> --runuser <domain>\<user name> --runuser-password <password of the user>
(the <domain> is the Windows domain in which the user can be found. For a local user, this is the name of the server itself. If the user is from an Active Directory or Windows Domain, it must be the name of the directory)

To remove a service:
rethinkdb.exe remove-service

Both install-service and remove-service also accept the --instance-name <name> option. This can be used if you want to run multiple instances of RethinkDB on the same server. Each instance will get its own entry in the Windows Service manager, and can be configured and started/stopped separately.

Screenshot of what the service looks like in Windows' service manager after being installed by rethinkdb.exe install-service:

Hi @danielmewes
When I try to run rethinkdb.exe install-service I get following error:
ERROR: Unrecognized subcommand 'install-service'. Try 'rethinkdb help'.
Is this not supported in version 2.3.5-windows (MSC 190023506) ?

@JollyBrackets Is is not unfortunately. This feature will only be supported in the next RethinkDB release (2.4).

@danielmewes, ok thanks, looking forward to the release then! Is there another way to achieve this until then?

+1

Hi, I can not start the RethinkDB as Windows service (returning 1053 timeout error), how could I do this, or is not possible (or maybe wait for the 2.4.0 version)?

When is the rethink Db 2.4.0 version is going to release?

While your interest is awesome, appending questions to a long-closed documentation issue is probably not the best way to get solid answers. :)
For information about open-rethinkdb timelines and projects, I'd suggest keeping up with the community Slack:
http://slack.rethinkdb.com
Also, there's a Google Docs file which talks about planning meetings:
https://docs.google.com/document/d/1cTqKt1_EBanGoVmYyahdLyDD8dhCa0SdD0CbjbP67f8/preview

This is still not working v2.3.6
C:\rethinkdb-2.3.6>rethinkdb.exe install-service --config-file default.config
ERROR: Unrecognized subcommand 'install-service'. Try 'rethinkdb help'.


Tests failing on Windows

While looking into #219 I notice several tests fail on Windows:

@lukepmccombs

I'll pick this up.

The first couple errors I have are for the island model scripts. Matplotlib is expecting an integer for nrows and doesn't automatically cast true_rows from the viz_plots function. Easily fixed by a conversion (although it should probably round up).
Relevant tests: test_script_execution on:
island_model.py (viz_plots func)
multitask_island_model.py (viz_plots func)
Looks like several of the issues are caused by the recent changes to gym. env.reset() now returns two values, where a lot of the problem code where that is used simply forwards the whole return. Adding , _ to wherever that is used would fix it.
Relevant tests: test_script_execution on:
neural_network_cartpole.py (executable_rep/problems.py)
pitt_rules_cartpole.py (executable_rep/problems.py)
The last problems I had, and am surprised hadn't come up before, involve distributed. I had two errors when collecting tests and 2 scripts fail because module 'os' has no attribute 'WNOHANG', which is indicative of a Windows incompatibility.
Relevant tests: distributed doctests, test_script_execution on:
simple_async_distributed.py
simple_sync_distributed.py
Session details:
platform win32 -- Python 3.10.9, pytest-7.2.1, pluggy-1.0.0
rootdir: C:\Users\luke\LEAP, configfile: pytest.ini
plugins: anyio-3.6.2, c

Side note as a part of resolving this issue, I have setup github actions on my fork to replace Travis-CI.
The last issue was resolved in develop previously, I have largely fixed the others.
The gym issue is trickier to solve because the convention change hasn't been propagated back to python 3.7 on the version matrix. To support 3.7, we'll have to check versions and swap if need be.

Hopefully will confirm tomorrow that this issue can be closed with the associated merge request resolved.


Feature/overlay warnings

Not 100% on the revised conditional logic, but tested everything locally and it behaves as expected. The overlay will display on warnings only if overlayWarnings option is set to true. Warnings always still display in the console.

Coverage decreased (-0.4%) to 80.402% when pulling 8d54ae828a2417ded3a79d5b7902f704edb877e4 on benjarwar:feature/overlay-warnings into 3591ea8a351364815ea459b060d865c044fed955 on glenjamin:master.

Coverage decreased (-0.4%) to 80.402% when pulling 8d54ae828a2417ded3a79d5b7902f704edb877e4 on benjarwar:feature/overlay-warnings into 3591ea8a351364815ea459b060d865c044fed955 on glenjamin:master.

Hey @benjarwar! It's almost done, could you please fix up the two notes so @glenjamin can merge? Thank you 😄

If anyone else has time and can submit another PR based on this one, that’ll work too

On 14 Mar 2018, at 22:02, Jim Blue<EMAIL_ADDRESS>wrote:
Hey @benjarwar! It's almost done, could you please fix up the two notes so @glenjamin can merge? Thank you 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@glenjamin @jimblue sorry for the delay; this totally fell off my radar. Fixed up those two issues.
@glenjamin I opted to strengthen the check for overrides.overlayWarnings similar to how you did it here for autoConnect. So the setting is only passed along if the param is set to true.


update readme and ci scripts to use new pull methods

The ci files are now pulled from https://www.github.com/jeking3/boost-ci during the build process.  This allows them to be updated "en masse".
This PR updates the readme badges and I have enabled both Appveyor and Travis CI build jobs, so they should kick in normally on the PR.

Yep, so, merging was a bad thing.  The builds failed.  In the future, let's wait for the builds to pass.

Good news - all the builds are working again:
Appveyor: https://ci.appveyor.com/project/jeking3/signals2-db91c/build/1.0.7-develop
Travis: https://travis-ci.org/boostorg/signals2/builds/387260353

So should it be merged to master now?

It is stable and passes all builds successfully.  I've added a once-monthly develop branch cron job as well to get a Coverity Scan analysis (it is supposed to happen on any push to develop, but a squash or rebase in the GitHub UI may not trigger it - not sure yet).

I'm working with Travis support to figure out why the Coverity Scan job isn't running, if an additional change is needed (like in .travis.yml) there I will submit another PR.


How to change the language at runtime

Hey, I'm doing a bit research and I want to change the language of my project at runtime. I've tried the following code of the readme:
{
provide: TRANSLATIONS,
   useFactory: (locale) => {
   locale = locale || 'de-DE';
      return require(`raw-loader!../assets/i18n/messages.${locale}.xlf`);
   },
   deps: [LOCALE_ID]
},

In my translate service is a function, to change the language, but without an effect.
setEnLanguage() {
    registerLocaleData(localeEn);
}

I'm thankful for any help!

Have a look at what I did:
https://github.com/angular/angular/issues/24549#issuecomment-402013622
It works, only issue I have is the the require doesn't survive the build process when I use --prod in the CLI. Havent found a solution yet.

Thanks for your answer!
The solution looks a bit hackish, I think for now, I have to wait for Angular 7.x.

@ThomasCybulski It is not that hackish mate. It loads the XLF before it bootstraps your angular app.
I asked the Angular team and they said that for now this is the best way to move forward.
Up to you.


:truck: Move training parameters 1 level down

What this PR does / why we need it:
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

@gkumbhat is this handled by #434 ?

closing in favor of #434


Cleanup defaults focusing on font sizes

pre-req to sizing (width, padding, font-size) for #1024
closes #1123
closes #1101
closes #989

sets html font size to 10px, so that other px/rem values can be defined based in 10 (for example font-size(1.4)

new body default is 14px, 1.4 rem, @eatonphil take a look at this and let me know if you're still liking it from the other day. If not I'll just keep at 16px.

all font sizes should now render in whole pixel values ( as opposed to many sub-pixel results we have in master )

redefines base font vars as classes which use a mixin.

applying a default font class:
@extends .font-normal;

applying a custom font using the mixin:
@include font-size(1.5);

redefines (and fixes problems) where padding/margin were defined using rem values
fixes h4, h5, h6 heading tags, updates others with whole pixel values as compared to master
creates new scss files:

defaults.scss ( our defaults for base elements )
utilities.scss ( shared classes )
layout.scss ( layout specific things that were in manager.scss )

Coverage increased (+0.007%) to 84.211% when pulling 0a68792b963b0f5607d9b15b6fb317eb99fcd349 on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

Coverage increased (+0.007%) to 84.211% when pulling 2ca495e0bc3d2a43052ef14dcc3404fdc0e839bb on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

Fixes based on feedback:

[ ] sidebar list item padding reduction
[ ] linode dashboard input width + button reflow
[ ] tab > sub tab padding + alignment slightly off
[ ] header padding slightly off ( too large )
[ ] dashboard TODO (stats) top margin too large
[ ] advanced tab missing padding
[ ] top level tab padding too large, s/b 5px 15px 15px 15px
[ ] move layout styles to scss/layout/Layout.scss

@eatonphil

Coverage increased (+0.007%) to 84.211% when pulling 6553f65ee9cb30ea1a2df014357e2004e4b20869 on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

Coverage increased (+0.007%) to 84.211% when pulling 7d5eeb0491fc1979a702bdea4c89fda8d7b933c9 on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

Coverage increased (+0.007%) to 84.211% when pulling 125326a945dd414a24aeba69df8f9ccb744f9ff8 on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

@eatonphil  tell me if this alignment looks right to you

Coverage increased (+0.007%) to 84.211% when pulling 8fd11b56fe062634c0b2e1fc86b22c40b9e7e8b0 on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

Coverage increased (+0.007%) to 84.211% when pulling 8fd11b56fe062634c0b2e1fc86b22c40b9e7e8b0 on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

Just a heads up, since several of these margins were going slightly smaller ( 15px ), I updated $grid-gutter-width-base: 30px; (was previously 40px).
There are places where this var is divided, and may result in sub-pixel values, but I think it's a trade off for now, and can be addressed later.

Coverage increased (+0.007%) to 84.211% when pulling afc2971552da28a67682815bd73a2e1fa2c993a4 on mparke:defaults-cleanup into 82c88ba49c4c634ac0bde35ed4479e0a0f90a54e on linode:master.

I think you missed legends in a label-col change:

See initrd, virtualization mode, run level vs every other label.

Missing padding below subtab in edit config page?

Fixed issues and rebased

Coverage increased (+0.007%) to 84.437% when pulling 61482f6894ba2c778e046d7108be6a7497f888be on mparke:defaults-cleanup into 7257de6a62495b3696364ec4d938800368c4e155 on linode:master.


Drop wishlists

Drop wishlist models.
Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Just trying to understand, why the support was dropped for Wishlists. That sounds like a reasonable feature.
Was it dropped as a replacement for another feature? Can someone share some context here?
Appreciate your response.

@awaisdar001 we believe whishlist functionality can be built using Apps and User metadata. We are aiming to keep our core lean by adding only APIs that are essential or not trivial to extend. Such approach allows us maintaining healthier code base.

Thanks for the quick feedback @timuric
Amazing, thanks for the context. I understand the logic and behavior of Metadata models, but I don't exactly understand how this can be achieved using Apps? Is there some docs explaining that?
Secondly, In the lastest version of saleor, have we implemented the such things as "Favourites" or "ShoppingLists" if yes, can you refer me to that code?


[DDW-231] log expected errors as debug messages only

This PR improves our error handling by logging expected error cases only as debug messages instead of spamming our dev console.
Review Checklist:
Basics

[ ] PR is updated to the most recent version of target branch (and there are no conflicts)
[ ] PR has good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance tests are passing (npm run test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (npm run dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (npm run package / CI builds)
[ ] There are no flow errors or warnings (npm run flow-test)
[ ] There are no lint errors or warnings (npm run lint)
[ ] Text changes are proofread and approved (Jane Wild)
[ ] There are no missing translations (running npm run manage-translations produces no changes)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (npm run storybook)
[ ] In case of npm dependency changes both package-lock.json and yarn.lock files are updated

Code Quality

[ ] Important parts of the code are properly documented and commented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-rendering
[ ] Any code that only works in Electron is neatly separated from components

Testing

[ ] New feature / change is covered by acceptance tests
[ ] All existing acceptance tests are still up-to-date
[ ] New feature / change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review:

[ ] Merge PR
[ ] Delete source branch
[ ] Move ticket to done on the Youtrack board

@nikolaglumac i agree that it would be "better" … unfortunately it's not easily possible without a lot of duplicated logging statements or boilerplate around it. Basically I would have to duplicate the error logging into any if statement or set a flag like isHandledError for each case.

@DominikGuzei roger that!
Let's leave 1). for later. What about 2). and 3).? :)

working on those now @nikolaglumac 👍

@nikolaglumac changelog and ETC updates are added!


Core: RBAC add FF and document scope proposal

Action Item
Add a new FF to our helm charts RBAC.enabled with a boolean value, which defaults to false.
Furthermore, enhance the current swagger documentation with the proposed model based on OAuth scopes, see swagger doc.

Duplicate of https://github.com/keptn/keptn/issues/7352


issue with installing magic rock

Mac os , lua 5.4
image.nvim: magick rock not found, please install it and restart your editor
luarocks install magick: To check if it is available for other Lua versions, use --check-lua-versions.
it seems that magic rock only support lua 5.1
How to solve it?
Can I run neovim without magic rock?
thank you. This plugin is amazing ,its a game changer!

Hey, I'm not sure how things work on macOS, does this help you?
https://github.com/3rd/image.nvim/issues/18#issuecomment-1826976752

Hey, I'm not sure how things work on macOS, does this help you? #18 (comment)

this I tried. still not working

Neovim is supposed to come with LuaJIT, and it should works in its context, your external Lua version doesn't matter.
Check if nvim --version says it has LuaJIT, and preferably Neovim itslef is v0.10

I had the same problem, and this did the trick:
brew install lua51
luarocks --lua-version=5.1 install magick

I have tried this but it didn't work.  Which chip you are using? M or intel?

I followed @Gabz-Araujo and it worked. But, nvim --clean -c ":luafile minimal-setup.lua" for minimal-setup.lua does NOT show the image. I use Apple M1.

@spring-haru  you will likely have to follow some instructions in the pinned issue if you're on macos

I had the same problem, and this did the trick: brew install lua51 luarocks --lua-version=5.1 install magick

This no longer seems to be an option.

Error<EMAIL_ADDRESS>has been disabled because it is deprecated upstream!

Plugin just doesn't seem to be able to find magick/init.lua???

Updated it so it shows the loading error for the rock, it might point you in the right direction.

I tried this on my M2 chip Macbook and it worked, see https://github.com/3rd/image.nvim/issues/9#issuecomment-1637153929
change the magick/wand/lib.lua try_to_load as, for example:
lib = try_to_load("/opt/homebrew/lib/libMagickWand-7.Q16HDRI.dylib", function()
  -- local lname = get_flags():match("-l(MagickWand[^%s]*)")
  -- local suffix
  -- if ffi.os == "OSX" then
  --   suffix = ".dylib"
  -- elseif ffi.os == "Windows" then
  --   suffix = ".dll"
  -- else
  --   suffix = ".so"
  -- end
  -- return lname and "lib" .. lname .. suffix
end)

If you want to use luarocks.nvim you have to tell it to install the magick rock. Image.nvim doesn't do it automatically like some other plugins do.

If you want to use luarocks.nvim you have to tell it to install the magick rock. Image.nvim doesn't do it automatically like some other plugins do.
Take a look at the image.nvim readme for an example

Sorry, you're right. I somehow forgot to add options.
Here's my updated rocks.lua file:
return {
  "vhyrro/luarocks.nvim",
  priority = 1000, -- Very high priority is required, luarocks.nvim should run as the first plugin in your config.
  config = true,
  opts = {
    rocks = { "magick" },
  },
}

The issue is still happening. I did restart the terminal.

Probably need to run :Lazy build luarocks.nvim to install the rock

Yeah, I also thought so. Didn't help 🤔 .
How can I check if the build command worked? Because when I run it, it pops-up the Lazy panel.

Did you follow the other steps for Mac os from the readme? The installing magic part in particular? There's a note about brew installing something in a place that nvim doesn't check and how to fix it

Did you follow the other steps for Mac os from the readme? The installing magic part in particular? There's a note about brew installing something in a place that nvim doesn't check and how to fix it

Yep. I did that:
export DYLD_LIBRARY_PATH="/opt/homebrew/lib/"

and if I check with echo $DYLD_LIBRARY_PATH it shows the correct path.

What's your exact error? You should get something more than just image.nvim: magick rock not found I think. and if you don't, make sure you're up to date with the latest version of image.nvim.

@FunnyGhost solved it like https://github.com/3rd/image.nvim/issues/91#issuecomment-2025287226

@mesa123123
About this: image.nvim: magick rock not found, please install it and restart your editor
I listened to @Gabz-Araujo's suggestion:
luarocks --lua-version=5.1 install magick

The solution I found was the following:
modify the excerpt from the file '.luarocks/share/lua/5.1/magick/wand/lib.lua':
lib = try_to_load(
"/opt/homebrew/Cellar/imagemagick/7.1.1-30/lib/libMagickWand-7.Q16HDRI.dylib",
<EMAIL_ADDRESS>"/opt/homebrew/bin/imagemagick/7.1.1-25/lib/libMagickWand-7.Q16HDRI.dylib"
)

In my case, in the first line:
"/opt/homebrew/Cellar/imagemagick/7.1.1-30/lib/libMagickWand-7.Q16HDRI.dylib", read 7.1.1-29.

Checking the path I realized it should be 7.1.1-30
It worked

after a while try reinstalling lua/luajit and install pkg-config using brew, mine finally works in MacAir M1

Unfortunately this is still an issue. You cannot install Lua 5.1 with homebrew anymore
❯ brew install lua51
luarocks --lua-version=5.1 install magick

Warning: Formula lua51 was renamed to<EMAIL_ADDRESS>Error<EMAIL_ADDRESS>has been disabled because it is deprecated upstream! It will be disabled on 2024-02-16.
zsh: command not found: luarocks

Unfortunately this is still an issue. You cannot install Lua 5.1 with homebrew anymore
❯ brew install lua51
luarocks --lua-version=5.1 install magick

Warning: Formula lua51 was renamed to<EMAIL_ADDRESS>Error<EMAIL_ADDRESS>has been disabled because it is deprecated upstream! It will be disabled on 2024-02-16.
zsh: command not found: luarocks

Hey @t18n, for lua 5.1 you can install luajit.
brew install luajit
luarocks --local --lua-version=5.1 install magick

Unfortunately this is still an issue. You cannot install Lua 5.1 with homebrew anymore
❯ brew install lua51
luarocks --lua-version=5.1 install magick

Warning: Formula lua51 was renamed to<EMAIL_ADDRESS>Error<EMAIL_ADDRESS>has been disabled because it is deprecated upstream! It will be disabled on 2024-02-16.
zsh: command not found: luarocks

Hey @t18n, for lua 5.1 you can install luajit.
brew install luajit
luarocks --local --lua-version=5.1 install magick

This worked for me, thank you!
I'm on Macbook Air M2, Nvim 0.10.1 and Lua 5.4.7

I've re-packaged the luarocks package for neovim, and modified it slightly so that it will locate the local installation of magick as well.
Instead of using luarocks, you can just install this plugin.
https://github.com/kiyoon/magick.nvim

https://github.com/3rd/image.nvim/issues/91#issuecomment-2025287226 worked for me.
Instead of .dylib, I had to replace it with .so file on linux.
Here is the command I used to get the library path:
 fd 'libmagickwand.*\.(so|dylib|dll)$' / --hidden

I beat my head against the wall for bit with this, but I had to install pkgconfig to get this to work:
brew install pkgconfig

Then it magically worked

+1 to @dreilly1982 's suggestion. I'm currently using MacOS and was originally able to resolve the issue with this workaround mentioned above.
Happy to say this workaround is no longer necessary after running brew install pkgconfig.

I ran into a similar issue when trying to run the minimal config on a fresh installation of Arch Linux. I noticed that for the tiniest amount of time a message from presumably the shell (?) flashed on the screen which mentioned that pkg-config is not available as a command. On Arch, pkg-config is provided by the pkgconfig package and installing this package resolved the issue. So pkg-config seems to be a dependency of some sort? In that case perhaps it should be mentioned in the README.
I also noticed that the mode of failure seems to be the same as when magick is not available. In both cases :lua require("magick") produces the same error.

@burbschat do you have an otherwise working ImageMagick installation? (convert and identify commands available and working)
If you do you can switch to the magick_cli processor instead of using the Lua rock.

@3rd Yes indeed I do have a working ImageMagick installation. Switching to magick_cli does seem to work and thank you for documenting this option. However, if pgk-config is not available, first I still see sh: line 1: pkg-config: command not found and the same error message as when I use magick_rock (with pkg-config not available) appears (see screenshot below). If I just ignore the message and advance by pressing ENTER, images are displayed without problems. So it seems like the error message is accidentally triggered? I mean it is complaining that the magick rock is not found, even though it is not needed.

A similar error is triggered when I try to :lua require("magick") (without having pgk-config available), so perhaps magick is required (by which I mean loaded with require) somewhere even if the processor is set to magick_cli.
I've been testing this using the minimal config to which I added one line to set the processor to magick_rock or magick_cli. I also cleared the directory where lazy seems to install (?) the magick rock to (on my system that is ~/.local/share/nvim) after setting magick_cli in the minimal config, to ensure installation from scratch, but this did not appear to help.
Looking at the lazy-rocks directory, it seems like the magick rock is installed even if the processor is set to magick_cli. Not sure if this is relevant though. Just for the record, here is a tree ~/.local/share/nvim/lazy-rocks -L 5 showing the directories after a fresh initizalization with the minimal config:
~/.local/share/nvim/lazy-rocks
└── image.nvim
    ├── lib
    │   └── luarocks
    │       └── rocks-5.1
    │           ├── image.nvim
    │           ├── magick
    │           └── manifest
    └── share
        └── lua
            └── 5.1
                ├── image
                ├── magick
                └── types.lua

Hey, it was an extra check that ran all the time, fixed now.
@sankantsu Is there any way to avoid doing the build and installing the rock when using "magick_cli"?

@3rd , @burbschat
It seems that lazy.nvim has option to skip the build for plugin.
It might be helpful to document this option in README, for magick_cli processor users.
c.f. https://lazy.folke.io/spec#spec-setup
    {
        "3rd/image.nvim",
        opts = { ... },
        build = false,  -- This option disables build.
    },

I locally tested setting like above, and confirmed that it skips luarocks build steps.
It seems that opts.rocks.enabled = false also works, completely disables luarocks for all plugins (I didn't tried).
c.f. https://github.com/folke/lazy.nvim/issues/1576
I'm not sure about #240.

Thank you @sankantsu! Rewriting the README now with the help of Claude, who has a beautiful personality today :joy:

Hi, sorry, is this resolved? What's the answer? On MacOS how do I get the minimal example to work?
I tried one of the suggestions:
test_image_nvim % brew install luajit
luarocks --local --lua-version=5.1 install magick
which doesn't work (even after I brew install luarocks)

@varung Ive also done all the above and am not getting it to work on M1 mac. Would love someone to post a cohesive way to get this to work.

Hey, if you have a regular working imagemagick installation you can use the magick_cli backend instead of the rock.

@3rd I couldnt get magick_cli to work either. I tried everything in this thread as well as other threads and simply couldnt giet it figured out on M1 MacOS. Maybe its just me though. Thats why I'd like to see a "full solution" to try.

It's just my opinion, but given that it's so hard to install dev version of magick and more complicated steps involving luarocks, I believe the CLI interface should be the default mode and leave FFI bindings for the the advanced users.

@aogposton for cli mode the plugin uses only the identify and convert utilities from ImageMagick, can you confirm that those exist in your path and that they work?
try converting an image by using convert directly in your shell please.


docs: update prerequisites section

run ci

I stopped android-runtime job since this is only a change in  documentation and we don't need those tests.

run ci


Preprocessor? Regenerate source code

I am building extensions to an existing language as a preprocessor. I was unable to figure out if there is a way to get pegjs to regenerate the source code. Basically I want it to parse the source, I want to modify the AST then regenerate the source. Anyway this is possible?

@mattkanwisher sorry, I dont quite understand what you mean by "regenerate" the source.
Could you please clarify a bit? If you mean produce code based on the AST - you would have to write that logic yourself, either directly in the grammar or as a separate module.

Yeah produce code based on the AST, so I have to generate a compiler back to original source if I want to preprocess using this?

@YemSalat is right, PEG.js is just a parser generator.

Build a parser using PEG.js (ensure actions return AST)
Parse your language with the generated parser to build an AST
Modify the AST using transform pass's
Regenerate the source code

As you can see, PEG.js is only involved in the first step, so if you want to regenerate the source, you have to build a compiler yourself, or if a compiler or generator (toolchain) already exist's for the language, I suggest you either return AST compatible with the toolchain or add a transform that alters's the AST to be more compatible with the toolchain.
Closing, as this is not actually an issue with PEG.js but your welcome to continue the discussion.

So I figured it out. For anyone that lands on this bug post in the future. Just read the source code to "The super tiny compiler". After that I was able to use pegjs to build my preprocessor in a few hours
https://github.com/thejameskyle/the-super-tiny-compiler


ntdb: remove

Description of changes
ntdb is no longer used by samba and was last updated 8+ years ago. It also depends on python2.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

It hasn't been abandoned by upstream, scroll down and you'll see they've made a release this year
So the throw should be changed
This hasn't been updated in nixpkgs in many years so I think it's safe to assume no one is using this

That is tdb, not ntdb. ntdb only has one release on that page at the top.

Ah


run error actions (if any) when recaptcha fails

Is your feature request related to a problem? Please describe.
Currently we don't fire error actions when recaptcha fails
Describe the solution you'd like
fire error actions when recaptcha fails

@Pralish while you're looking into this, can you address this issue? Its related to how we are handling errors. https://github.com/restarone/violet_rails/issues/1071


[NVIDIA] Support vmap usage of jax.nn.dot_product_attention

To address this request: https://github.com/google/jax/discussions/22760, this PR support no-batch inputs.

Gentle ping @superbobry


Add syntax highlighting to API Basics documentation

This can be done to quite a few more documents. Should I do separate PRs for each or can I group as one larger syntax highlighting addition PR?

Thanks! We can do it all as 1 PR.

Okay @zpao. I will make changes, rebase and squash it.

Should be good to go now!

Thanks! I'll merge this now and if you have any others, feel free to open another PR.


Assignment with a Returned Value - Improve Challenge Seed

Challenge Assignment with a Returned Value has an issue.
Here is the current challenge code:
// Setup
var processed = 0;

function process(num) {
  return (num + 3) / 5;
}

// Only change code below this line

We need to better organize the example to show how the code is actually used.
// Example
var changed = 0;

function change(num) {
  return (num + 5) / 3;
}

changed = change(10);

// Setup
var processed = 0;

function process(num) {
  return (num + 3) / 5;
}

// Only change code below this line

I'm open to discussion on the specifics of this.  I don't know if this ends up being too long.
As per comments on #6062

var changed = 0;
function change(num) {
return (num + 5) / 3;
}
changed = change(10);
i don't understand that. how does it add up to 10? I've been stuck on this challenge for awhile


How should I mount network disk?

Hi All,
I would like to ask, is there any way to mount network disk? In the window system to do, I tried for a long time:(
Very thanks all

Hey @llovvoll!
I'm not sure if it works. But try to set the scope to the path as you'd normally do in File Explorer.

Hi hacdias,
Very thanks your respond, it's work, Does not meet the practical application method :(

Sorry, I can't understand you said 😞


Admin: Add mailing list sign up

We need a solution for mailing list.

We are using Mailchimp. @Yoonie458 sent me the login info so I'll close out this issue. Thanks Yoonie!