Error when opening an untracked file with base = "HEAD"

Description
I am getting the following error when opening a file with the same name as a file that has previously been moved and staged. See repro instructions.
Error executing vim.schedule lua callback: ...cal/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/async.lua:76: The coroutine failed with this message: ...cal/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/hunks.lua:172: Invalid hunk with untracked
=true hunk="@@ -1,15 +1,6 @@"
stack traceback:
        [C]: in function 'assert'
        ...cal/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/hunks.lua:172: in function 'calc_signs'
        ...l/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/manager.lua:49: in function 'apply_win_signs0'
        ...l/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/manager.lua:72: in function 'apply_win_signs'
        ...l/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/manager.lua:466: in function 'fn'
        .../share/nvim/lazy/gitsigns.nvim/lua/gitsigns/debounce.lua:68: in function 'update'
        ...al/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/attach.lua:365: in function 'fn'
        .../share/nvim/lazy/gitsigns.nvim/lua/gitsigns/debounce.lua:68: in function 'attach_throttled'
        ...al/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/attach.lua:426: in function <...al/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/attach.lua:425>
stack traceback:
        [C]: in function 'error'
        ...cal/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/async.lua:76: in function 'cb'
        ...cal/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/async.lua:113: in function 'cb'
        ...l/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/manager.lua:416: in function <...l/share/nvim/lazy/gitsigns.nvim/lua/gitsigns/manager.lua:401>

Neovim version
NVIM v0.9.2 Build type: RelWithDebInfo LuaJIT 2.1.0-beta3 Compilation: /usr/bin/gcc -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wvla -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -fno-common -Wno-unused-result -Wimplicit-fallthrough -fdiagnostics-color=auto -fstack-protector-strong -DUNIT_TESTING -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -I/usr/include/luajit-2.1 -I/usr/include -I/usr/include/luv -I/builddir/build/BUILD/neovim-0.9.2/redhat-linux-build/src/nvim/auto -I/builddir/build/BUILD/neovim-0.9.2/redhat-linux-build/include -I/builddir/build/BUILD/neovim-0.9.2/redhat-linux-build/cmake.config -I/builddir/build/BUILD/neovim-0.9.2/src -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include     system vimrc file: "$VIM/sysinit.vim"   fall-back for $VIM: "/usr/share/nvim"  Run :checkhealth for more info
Operating system and version
Fedora 38
Expected behavior
Operation as usual
Actual behavior
The error above
Minimal config
for name, url in pairs{
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
} do
  local install_path = vim.fn.fnamemodify('gitsigns_issue/'..name, ':p')
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.opt.runtimepath:append(install_path)
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
  -- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
  base = "HEAD",
}

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE

Steps to reproduce

be inside a git repository
create a file with some text in it echo "some text" > Cargo.toml
git add Cargo.toml
git commit -m "message"
mv Cargo.toml into a directory for example subdir
git add .
nvim --clean -u minimal.lua Cargo.toml
add some text and save the file
now the error should appear constantly

Gitsigns debug messages
No response

I got that exact same stack too now. I'm not sure what I did, multiple branch switching...

I could only get it to work with this inside my .gitconfig:
[init]
    defaultBranch = main

Maybe there are some assumptions made about the default branch somewhere?

Most of my repo's use main so I doubt that.

Maybe it's a bug within git itself, since it's not too long ago that they added the config option to change the default branch.

I'm not sure why the default init branch has anything to do with this.

I have to mention that I got this issue too, and I'm using fedora 38 exactly like @Saecki which seems like a big coincidence.
I have the default fedora git: git version 2.41.0.

If you can make the repro steps precise and in a script then that will probably allow me to repro this.
Ideally this could be added as a testcase in the current suit.

Ok so it seems I don't even need to change the .gitconfig this script does the trick for me. If you can reproduce the error I can create a proper test case.
#!/bin/sh

# init git repo
REPRO_DIR="untracked_file_madness"
rm -f "$REPRO_DIR"
mkdir "$REPRO_DIR"
cd "$REPRO_DIR"
git init --initial-branch=main

# first commit
echo "some text" > Cargo.toml
git add Cargo.toml
git commit -m "message"

# move Cargo.toml and stage move
mkdir subdir
mv Cargo.toml subdir
git add Cargo.toml subdir

# open file in neovim with minimal config
MINIMAL_CONFIG="for name, url in pairs{
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
} do
  local install_path = vim.fn.fnamemodify('gitsigns_issue/'..name, ':p')
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.opt.runtimepath:append(install_path)
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
  -- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
  base = \"HEAD\",
}

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
vim.defer_fn(function() vim.cmd(\"w\") end, 1000)
"
echo "$MINIMAL_CONFIG" > minimal.lua
nvim -u minimal.lua Cargo.toml

I think the cause of this is just a faulty assertion in hunks.lua:172:
assert(
    not untracked or hunk.type == 'add',
    string.format('Invalid hunk with untracked=%s hunk="%s"', untracked, hunk.head)
)

Since git status returns this
❯ git status
On branch master
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        renamed:    Cargo.toml -> subdir/Cargo.toml

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        Cargo.toml
        gitsigns_issue/
        minimal.lua

Removing the assertion seems to work just fine. Do you know why it was there in the first place? Otherwise could we just remove it?

Repro'd it!
Thanks for scripting this.


Add a generic file-storage to modules.

As #89 mentioned, We should add a generic file-storage service.

As we turned to spring-boot and made the FileOrchestratorStorage packed into the DefaultOrchestratorStorageBean.
So Bean is generic enough.


Function not found when linking two components together

I have two wasm components gcd2.wasm and gcd4.wasm.

The first one implements and exports a function gcd2: func(a: s64, b: s64) -> s64 which calculates the greatest common divisor of two integers.
The second one imports the gcd2 function, whose signature is the same as described above, and exports a function gcd4: func(a: s64, b: s64, c: s64, d: s64) -> s64, which uses the imported gcd2 function to calculate the greatest common divisor of four integers (i.e gcd(a,b,c,d)=gcd(gcd(gcd(a,b),c),d)).

I'm using wasmtime::component to load the two components, link them together, and invoke the gcd4 function, but Linker::instantiate returned an error, indicating that gcd2 is not defined.
My code is here:
use wasmtime::{
    component::{Component, Linker},
    Store,
};
struct MyState {}
fn main() {
    let mut config = wasmtime::Config::new();
    config.wasm_component_model(true);
    let engine = wasmtime::Engine::new(&config).unwrap();

    let gcd2 = Component::from_file(&engine, "gcd2.wasm").unwrap();
    let gcd4 = Component::from_file(&engine, "gcd4.wasm").unwrap();

    let mut store = Store::new(&engine, MyState {});
    let linker = Linker::new(&engine);
    // linker.instance("ss").unwrap().
    linker.instantiate(&mut store, &gcd2).unwrap();
    linker.instantiate(&mut store, &gcd4).unwrap();
}

Test Case
The two wasm components are in the following zip file:
linker-demo.zip
Steps to Reproduce

Create a new rust project using cargo new
Modify main.rs like mentioned above
Put the two wasm component files in the root directory of the project
cargo run

Expected Results
No panics happened
Actual Results
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: import `gcd2` has the
wrong type

Caused by:
    expected func found nothing', src\main.rs:18:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Versions and Environment
Wasmtime version or commit: rev 255fd6b, with feature component-model
Operating system: Windows 10, 21H1 19044.2486
Architecture: x64
Extra Info
Cargo.toml:
[package]
name = "linker-demo"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
wasmtime = { git = "https://github.com/bytecodealliance/wasmtime", rev = "255fd6b", features = ["component-model"] }

Instantiating a component does not modify the Linker, you'd have to re-insert items into the linker. Additionally unlike core wasm components cannot have their functions directly hooked up via the embedder API at this time, so you'd need to have the host interpose between the two components.
Linking components together at this time is planned to be left to tooling like wasm-tools compose where it's linked together at the component model level before something reaches Wasmtime.

Instantiating a component does not modify the Linker, you'd have to re-insert items into the linker. Additionally unlike core wasm components cannot have their functions directly hooked up via the embedder API at this time, so you'd need to have the host interpose between the two components.
Linking components together at this time is planned to be left to tooling like wasm-tools compose where it's linked together at the component model level before something reaches Wasmtime.

Thanks! I'll look into wasm-tools


/kick & /ban are broken

They appear to load and discord shows them as loaded but they don't show up when trying to run them.

This is due to bugs in the current discord system.


Add Deep Evidential Regression

This PR fixes #32. The main changes are:

[x] Add Deep Evidential Regression's loss.
[x] Change the dist_estimation parameter of the regression routine from a boolean to an integer in order to specify the number of parameters to estimate.
[x] Add tests.
[x] Add a tutorial to explain how to use DER.
[x] Add the reference to the documentation.
[x] Add a synthetic toy dataset.

Bonjour @o-laurent!
Thank you for your kind feedback. I will certainly be checking your reviews and addressing any suggested changes as soon as possible. I'd like to let you know that I'm planning to make another pull request by the end of this week to add Monte-Carlo Dropout (#40).
On another note, I recently read your paper on Packed-Ensembles and find it very interesting. I noticed that the library currently has an implementation of the Conv2d layer. If it's okay with you, I will open an issue and adjust my schedule for next week to work on adding Conv1d and Conv3d layers.
I'm genuinely interested in contributing to this project, so if there are any other issues to resolve or papers to implement, please feel free to let me know. I'm more than willing to work on them.
Best,

On another note, I recently read your paper on Packed-Ensembles and find it very interesting. I noticed that the library currently has an implementation of the Conv2d layer. If it's okay with you, I will open an issue and adjust my schedule for next week to work on adding Conv1d and Conv3d layers.

Thank you so much for your interest :). We already have an implementation of Conv1d in another project (@alafage), so it may be easier for us to deploy it in this library, but thanks for the proposal.

I'm genuinely interested in contributing to this project, so if there are any other issues to resolve or papers to implement, please feel free to let me know. I'm more than willing to work on them.

If you are interested in the project, I can invite you to join the GitHub team as a developer if you would like to. We have a lot of ideas to improve and extend the library, and I could detail some of them by starting a GitHub project. Do you have a specific interest in the field of uncertainty? If so, we could try to think about new ideas that match your own projects!

The PR now seems ready for merge. I'll do it tonight if there is no opposition.

Yes, I believe this PR is ready to be merged. Thank you, @o-laurent and @alafage, for your assistance. I truly appreciate it.

I'm definitely interested in this project and would love to join.
During my recent internship at Michelin, I worked on combining uncertainty quantification with deep generative models to help address the problem of generating high-quality and synthesizable molecules. I tested various models, including DER, and MC Dropout.
I have several papers in mind that I'd like to contribute to this library. These include this paper, Wasserstein Dropout, MC-DropConnect, and MC-SoftDropConnect.

Wow, it is a very nice project!
They would all make excellent additions to the library, and I'd be happy to look into these methods with you!
I've sent you an invite to join the team.


Adjust batch mode partition count calculation

Cherry-pick of #28972 into swift-5.2-branch. Reviewed by @davidungar.

git cherry-pick -m 1 ... produced a squashed commit. Should this cherry-pick mirror the commits on the original PR instead?

Please cherry pick the original PR structure. It makes the history a big easier to reason about across branches.

@CodaFi I cherry-picked over the commits.

@swift-ci please test

@swift-ci please test


Update the specifics/ets lesson

PR #782 fixed a small shortcoming. The existing translations have to be checked whether they are affected by it.
Translation
Translation progress:

[x] en
[x]  ru /cc @nscyclone #786
[x]  ko /cc @devleoper
[ ]  jp /cc @3100
[ ]  pl /cc @Koziolek
[ ]  es /cc @aleandros / @jonahoffline / @eze1981
[ ]  pt /cc @pragmaticivan
[ ]  vi /cc @joneslee85
[ ]  id /cc @rezaprima
[ ]  gr /cc @gemantzu

#795 for greek language


IHostingEnvironment object gets a difference in path

In the Linux system, the dotnet is started in different paths. The WebRootPath attribute of the IHostingEnvironment object is different from the ContentRootPath attribute. The dotnet startup path is obtained. Shouldn't it always be the path of the site directory?
CentOS7
dotnet --version 2.2.103
Code
https://github.com/netnr/test/blob/master/src/Netnr.Test/Controllers/PathController.cs

This behavior is by design and we have no plans to change it.


Feature Request: Limit access to collections on image choose

I'm working on a large sporting site with regional team based editing, and looking to set up regional collections, and while I can limit upload to certain collections, I'm trying to restrict regional editors choosing images uploaded by other regions.
I would love the ability to have a 'choose' permission to collections, as even though you can restrict user groups to specific collections in terms of adding and editing, when choosing images on a page, they can still browse all collections, even if they don't have permission to add/edit them.
My initial thought was to just used named collections, not the Root one, but it turns out all of these named collections are still visible when choosing. I appreciate the default need for access to all, but given you can restrict people to a certain subtree of the site using page permissions, why not have a similar choose permission for collections?
E.g. If not specified, can see all in chooser, and if choose permission specified on certain collections, can only select from these.
Have seen it referenced in SO and referenced by @gasman in a comment.
Would love to put this forward for a feature request for multi-site & document/image collections - Thanks!

Hi @alpower - thanks for the suggestion.
This sounds the same as what's being proposed in #4488, so I suggest we keep the conversation on there.


feat(modal): adds basic modal

Introduces a modal-box component and implements a plain modal demo.
Notes:
Ghost/link button is not yet available.
Right alignment is not yet available.
Adds the option to add an id to a title because it is needed to correlate the title ID with the aria-describedby attribute.
How to handle scrolling content is TBD.

Hi @srambach It seems that icon "X" is not centered horizontally and vertically.

It appears that the following sentence is not encoded correctly.

@dabeng Thanks for the review! The X is to be an icon within "ghost" button which I'll update when that becomes available (ghost button is in PR; icons are coming soon).
And thanks for the nice way of saying I missed filling in the Overview section for Modal. :-) I'll update it.

@srambach One question. In your demo you are placing the modal in the center of the page, but I don't believe that is correct. I'm looking at the designs and what we do for PF 3 and see that the modal is positioned towards the top of the browser window.
@kybaker @mceledonia can you comment?

@mcarrano @srambach Yes it is horizontally centered but a bit off-center vertically going towards the top of the page as Matt said. I am not sure how best to translate this to CSS - is it just an offset that pushes the whole thing up by a certain amount?

No one has commented on the accessibility information being in both the modal and modal-box. Is that ok with everyone? It's duplicate info but important to know in both places I think. Also, does the usage section on a demo make sense?


Refactoring/support screen

Description

https://github.com/getferdi/ferdi/issues/651
Motivation and Context

https://github.com/getferdi/ferdi/issues/651
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the code style of this project (run $ yarn lint).

I'm playing around to see how I could improve Ferdi Support Screen, see #651. That is where I am at locally:

That's pretty rough but I wanted to share where I am before I move forward.
I created three components:

SupportManisfesto rendering all the text;
GitHubStarEmbed rendering GitHub star counter;
OpenCollectiveEmbed rendering Open Collective's donation button.

I nested GitHubStarEmbed and OpenCollectiveEmbed in SupportManisfesto.
I nested SupportManisfesto in the existing component SupportFerdiDashboard.
I have a  question, maybe you have pointers:

I understand that writing a plain message in English in a component is not the way to go (because of translations).  I can see messages are hosted this way:

const messages = defineMessages({
  headline: {
    id: 'settings.supportFerdi.headline',
    defaultMessage: '!!!Support Ferdi',
  },
});

however, my message is pretty long and has multiple paragraphs (see screenshot.) Where/how shall I host this message?
cc @kytwb

This is an update following our pairing session with @kytwb. Current look:

Next steps:

translate hardcoded strings;
update and finalize copy;
add pop-up customize window for surveys.

Thank you for the update!

I update the title, header, and copy.
Re title and header -- I found the term "support" confusing since in most applications the support section is where users seek help. Here we want to share information about Ferdi; the story of what Ferdi is. I find the term "About" more appropriate. Let me know what you think.
(We could indeed have a "Support" section in navigation where users seek help. I would be happy to carry on this discussion in an issue.)
That is what the title, header, and copy look like:

Feedback welcome.
Next steps:

translate hardcoded strings;
add pop-up customize window for surveys.

@yourcontact Great progress! Thank you for posting updates with screenshots for visibility! Happy to pair to help wrap up the last steps you identified! 🙏

This is an update following our pairing session with @kytwb. Current look:

Next step is to translate hardcoded strings.

Next step is to translate hardcoded strings.

I used this StackOverflow answer as a guide to implement React Intl.
Let me know if there any simpler ways to implement this. I will refactor https://github.com/getferdi/ferdi/pull/722/commits/490f277118d87f8b54ddc1f44398cac5e72b158a.

@kytwb @vantezzen, the message above says this branch the has conflicts that must be resolved. However the button "Resolve conflicts" is disable.
The messages say "Only those with write access to this repository can merge pull requests." can you help me with this?

You'll need to resolve those conflicts by merging develop into your branch first, something like:
git checkout develop
git
pull origin
git checkout refactoring/support-screen
git merge --no-ff develop

Well that took a really long time for us to merge this in 😅
Well anyway, I now finally merged this in by circumventing GitHub's resolve conflict system a bit - I now merged it via 74daa50 but GitHub doesn't really detect that.
So thank you for your contribution!

That is great! Thank you, @vantezzen.
And thank you @kytwb for the mentoring sessionS.


Create Add Two Numbers.cpp

According to hacktoberfest 2022 rules you can only make one valid PR in any specific repository, so request you to please not make a lot of contribution in a single repository otherwise it will get marked as spam. Hope you can understand it and will keep in mind from ahead.

okay thank you


Doc tests

Description

Addresses part of #205, specifically getting pytest --doctest-modules to pass

I was able to get most of the doc tests to pass without affecting the readability (I think) of the examples. I haven't turned on pytest --doctest-modules because we still having failing tests that have to do with get_segment_from_frame. One example error looks like this
075     This is called by `transform`, don't call `_wrap_class` directly, always use `transform`.
076
077     Example:
078     >>> @transform
079     ... class MyClass:
080     ...     def __init__(self, x):
081     ...         self.x = x
082     ...     def __call__(self, args):
083     ...         return self.x + args
084     >>> myobj = MyClass('hello')
UNEXPECTED EXCEPTION: FileNotFoundError(2, 'No such file or directory')
Traceback (most recent call last):
  File "/Users/sebastianlee/Aleph-One-Gmbh/padl/padl/dumptools/inspector.py", line 295, in get_segment_from_frame
    full_source = caller_frame.f_globals['_pd_source']
KeyError: '_pd_source'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/doctest.py", line 1329, in __run
    exec(compile(example.source, filename, "single",
  File "<doctest padl.wrap._wrap_class[1]>", line 1, in <module>
  File "/Users/sebastianlee/Aleph-One-Gmbh/padl/padl/wrap.py", line 108, in __init__
    trans_class.__init__(self, ignore_scope=ignore_scope, arguments=args)
  File "/Users/sebastianlee/Aleph-One-Gmbh/padl/padl/transforms.py", line 1003, in __init__
    call = inspector.get_segment_from_frame(caller_frameinfo.frame, 'call')
  File "/Users/sebastianlee/Aleph-One-Gmbh/padl/padl/dumptools/inspector.py", line 297, in get_segment_from_frame
    full_source = get_source(caller_frame.f_code.co_filename)
  File "/Users/sebastianlee/Aleph-One-Gmbh/padl/padl/dumptools/sourceget.py", line 37, in get_source
    with open(filename) as f:
FileNotFoundError: [Errno 2] No such file or directory: '<doctest padl.wrap._wrap_class[1]>'

I would say this is not a priority to fix since I'm sure it has to do with the special situation of a pytest. However, @wuhu if you think this would be a good opportunity to learn about how dumptools works, I would appreciate working on resolving this issue with your help.

nice! looks good.
i wonder if the imports can be avoided.
Also for all the definition within the file like from padl import identity

Very nice!


Avoid dropping events across properties

This PR is one approach to addressing the issue mentioned in https://github.com/pyviz/panel/pull/529#issuecomment-514299433.  The symptom in that case was that occasionally a selection event would be dropped, and not synchronized from JavaScript to Python.  And this problem only happened when hover data events were being synchronized around the same time.
Here's an overview of my understanding of what's currently happening between Panel and pyviz_comms.
When working in the notebook, Panel builds a JavaScript fragment for each synchronized property of a model.  This JavaScript fragment is used to create a Bokeh CustomJS object which is passed to Bokeh for execution whenever the given property changes.  This fragment is built in the get_comm_customjs function
https://github.com/pyviz/panel/blob/74efb05f8ef0178bff07f3af8d2cb4a5fe890a40/panel/io/notebook.py#L62
The bulk of the logic for this fragment is pulled from the JS_CALLBACK string from pyviz_comms.
https://github.com/pyviz/pyviz_comms/blob/master/pyviz_comms/__init__.py#L118
This JS_CALLBACK fragment has some debouncing logic, where events that occur in rapid succession are batched up and processed together.  This "batch" of events is stored in an array as the event_buffer property of the comm_status object.
https://github.com/pyviz/pyviz_comms/blob/e9f50e031f993f732e9c89035cabca4740c65244/pyviz_comms/__init__.py#L177-L181
Note that there is one buffer per comm, which for Panel means one buffer per model (across all synchronized properties in the model).
Before the events in the event_buffer array are processed, the unique_events function is run on the buffer to "Processes the event queue ignoring duplicate events of the same type".
https://github.com/pyviz/pyviz_comms/blob/e9f50e031f993f732e9c89035cabca4740c65244/pyviz_comms/__init__.py#L119-L122
This "event type" is pulled from the event_name property of the callback object
https://github.com/pyviz/pyviz_comms/blob/e9f50e031f993f732e9c89035cabca4740c65244/pyviz_comms/__init__.py#L184
The issue is that this event_name property is not defined for Panel models (at least the ones I looked at).  So, whenever events occur rapidly enough to build up in the event_buffer, all of the events except for the last one are dropped.
If all of these events are updates to the same property, then this is probably fine. But when the event buffer contains events that update multiple properties, this is a problem.
This PR makes the simple update of setting the event_name property of the callback object to the property name before the pyviz_comms logic processes it.  With this change, the logic for "ignoring duplicate events" will occur for each property individually.
With this change, I no longer have the problem with the Plotly pane of selected_data events being dropped occasionally when they are accompanied by rapid hover_data updates.

Thanks for the detailed investigation here and sorry for having to dig so deeply into things. The fix makes sense to me so I'll merge.


Managing code compatibility in a TypeScript ecosystem with multiple compiler versions

We're looking for recommendations from the TypeScript team on the best way (with today's tools) to mitigate the organization-level developer pain of a large internal ecosystem with multiple TS versions, and whether you know of any existing approaches. I'm especially interested to hear stories of how other teams have concretely mitigated it (I link to one such below, from Google).
This isn't a TypeScript bug; I'm aware of https://github.com/Microsoft/TypeScript/issues/14116 and am not pushing for a fix from within TypeScript.
The pain
We have a growing number of TypeScript services that depend on a growing number of internal TypeScript libraries, and developers commonly hit against compilation failures caused by a mismatch in compiler versions between a consuming service or library and one of its (potentially transitive) dependency libraries.
While these pains are equally true for public and internal libraries, we're primarily interested in what we can do with the packages we have direct control over (i.e., we can mostly guarantee semver is followed).
We use npm (and yarn) for dependency management, we generally follow semver internally, and we haven't realized a perfect way to apply these tools towards the problem.
Problematic scenarios:
1. Consumer's compiler is older than dependency's compiler
This is the natural case where the dependency's compiler produced .d.ts code with language features that the consumer's compiler doesn't understaned.
Usually, the resolution has been to upgrade the consumer's compiler.
2. Consumer's compiler is newer than dependency's compiler
Less obviously, this can also cause failure. Example: TypeScript 2.9 widened the type of the keyof operator, rendering some .d.ts declaration code emitted by TypeScript 2.8 unimportable by a 2.9 compiler.
Usually, the resolution has been to downgrade the consumer's compiler.
Solutions considered
In both scenarios above, the common resolution (upgrade/downgrade) is often complicated by the graph of mismatched compiler versions among all of the consumer's transitive dependencies -- a problem we anticipate to get worse as more libraries are built.
a. Enforce a single TypeScript X.Y version across the organization
Using an npm postinstall script (or other), assert that every service and library builds with a single blessed X.Y version of TypeScript.
Google does this (video), and they have some advantages that makes this realistic (a monorepo; centralized dev resources to grind out compiler upgrades).
Pros

Guarantees .d.ts compatibility, between internal packages.

Cons

The cost of upgrading the blessed version organization-wide could be prohibitively high. We may never upgrade TS again (or undo enforcement to do so), because the cost scales linearly with the number of libraries we use.

b. Bump library major versions for TypeScript upgrades
When a library upgrades the version of TypeScript used to build, also bump its major version. This doesn't fully solve the problem, but it reduces the chance that a consumer will break from a minor version update of a dependency. Breakage can still happen if the consumer/dependency are on different TS versions which are compatible for the subset of language features used in the dependency's old .d.ts files, but incompatible for language features in an interface added by a minor version update.
Pros

Cheap guard rail that will usually prevent package minor version upgrades from breaking consumers.

Cons

Doesn't improve the story for upgrading compiler versions of consumer packages.

This also doesn't provide developers with any guidance on how to navigate major version upgrades for their dependencies -- other than "update the package; run tsc; hope nothing explodes".
c. Libraries declare compatible consuming TypeScript compiler versions
Using a package.json key, have each library declare what TS versions it believes its emitted .d.ts files can be imported by. A postinstall script throws if consumers are running an unsupported version (problem: without a yarn/npm lockfile, postinstall script can't be sure which TS compiler is actually in play)
At its simplest (package.json key manually updated by developers) it's error-prone, but over time converges on useful guidance.
Pros

Gives "fast fail" feedback for developers adding or upgrading libraries with known compiler version incompatibility.

Cons

If declarations are manual: error-prone; will miss incompatibilities until after first breakage.
If declarations are automatic: involves some fairly complex scripting.
Doesn't improve the story for upgrading consumer package compiler versions (i.e., how to discover and )

Both (b) and (c) still leave service developers with the challenge of detecting the highest safe version of TS for their service, and library developers with the risk that they'll need support multiple branches for consumers with (very) different TS versions.

you might find the proposal in https://github.com/Microsoft/TypeScript/issues/22605 sufficient for your needs.
the assumption in https://github.com/Microsoft/TypeScript/issues/22605, that you have a "tool" that can emit a .d.ts compatible with different versions of the compiler.

Thanks @mhegazy. Yes, I should have clarified that I'm interested in recommendations that are possible with today's tools.
Adapting #22605 into such a thing, I believe it looks like this?

Library builds .d.ts with<EMAIL_ADDRESS>For each build, developer hand-modifies output .d.ts into multiple backwards-compatible flavors index-2.8.d.ts, etc.
a. Alternatively: enhance tsc to be able to emit downlevel'd .d.ts.
b. Alternatively: build a tool that will downlevel source .ts, which input into older tsc versions, "handling" modern language features with no downlevel equivalent.
Library has a postinstall script that detects the consumer's tsc version, picks the right flavor, and swaps out (overwrites) ./index.d.ts.

We have not had explicit guidance on this regard. what we have seen ppl do are either one of two approaches, 1. option a above, where the whole org moves their TS version all at once. 2. for libraries to test against older versions, and try to isolate the breaks from their users. Most of the breaks do not escape to the .d.ts files (with few exceptions).

Backward/Forward .d.ts compatibility system #31907

@igrayson what’s your final solution now?
Btw, thanks for all the detail.


Broken Swift project with plugins

Cocoapods has bug https://github.com/CocoaPods/CocoaPods/issues/7463
If pod uses :path with symlink, spec.public_header_files doesn't work.
It causes that Swift projects couldn't register plugins. E.g.  I met it in my plugin https://github.com/mogol/flutter_secure_storage/issues/3
The same issue exists for firebase storage plugin.
Steps to reproduce:

Create new Flutter project with Swift in IDEA.
Add package firebase_database: 0.3.6
Run on iOS Simulator

Could be caused by
https://github.com/flutter/flutter/pull/14748
Logs
Running "flutter packages get" in demo_security...
Launching lib/main.dart on iPhone X in debug mode...
Running pod install...
Running Xcode clean...
Starting Xcode build...
Xcode build done
Could not build the application for the simulator.
Failed to build iOS app
Error launching application on iPhone X.
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    The use of Swift 3 @objc inference in Swift 4 mode is deprecated. Please address deprecated @objc inference warnings, test your code with “Use of deprecated Swift 3 @objc inference” logging enabled, and then disable inference by changing the "Swift 3 @objc Inference" build setting to "Default" for the "Runner" target.
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    /Users/german/Projects/nomads/test/demo_security/ios/Runner/GeneratedPluginRegistrant.m:6:9: fatal error: 'flutter_secure_storage/FlutterSecureStoragePlugin.h' file not found
    #import <flutter_secure_storage/FlutterSecureStoragePlugin.h>
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 error generated.

Launching lib/main.dart on iPhone X in debug mode...
Running Xcode clean...
Starting Xcode build...
Xcode build done
Failed to build iOS app
Could not build the application for the simulator.
Error output from Xcode build:
↳
Error launching application on iPhone X.
    ** BUILD FAILED **

Xcode's output:
↳
    === BUILD TARGET firebase_database OF PROJECT Pods WITH CONFIGURATION Debug ===
    ld: warning: -undefined dynamic_lookup is deprecated on iOS
    === BUILD TARGET firebase_database OF PROJECT Pods WITH CONFIGURATION Debug ===
    ld: warning: -undefined dynamic_lookup is deprecated on iOS
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    The use of Swift 3 @objc inference in Swift 4 mode is deprecated. Please address deprecated @objc inference warnings, test your code with “Use of deprecated Swift 3 @objc inference” logging enabled, and then disable inference by changing the "Swift 3 @objc Inference" build setting to "Default" for the "Runner" target.
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    /Users/german/Projects/nomads/test/demo_security/ios/Runner/GeneratedPluginRegistrant.m:6:9: fatal error: 'firebase_core/FirebaseCorePlugin.h' file not found
    #import <firebase_core/FirebaseCorePlugin.h>
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 error generated.

Flutter Doctor
[✓] Flutter (Channel beta, v0.1.5, on Mac OS X 10.13.3 17D102, locale en-SG)
• Flutter version 0.1.5 at /Users/german/Projects/github/flutter
• Framework revision 3ea4d06340 (9 days ago), 2018-02-22 11:12:39 -0800
• Engine revision ead227f118
• Dart version 2.0.0-dev.28.0.flutter-0b4f01f759
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
• Android SDK at /Users/german/Library/Android/sdk
• Android NDK at /Users/german/Library/Android/sdk/ndk-bundle
• Platform android-27, build-tools 27.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.2, Build version 9C40b
• ios-deploy 1.9.2
• CocoaPods version 1.4.0
[✓] Android Studio (version 3.0)
• Android Studio at /Applications/Android Studio.app/Contents
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)
[✓] IntelliJ IDEA Community Edition (version 2017.3.4)
• Flutter plugin version 22.2.2
• Dart plugin version 173.4548.30
[✓] Connected devices (1 available)
• iPhone X • 47F7777A-ED9B-4761-89F0-BEAC583DD438 • ios • iOS 11.2 (simulator)
• No issues found!

Duplicate of #15099


Use UUID as conversation ID

Description
Use UUID as conversation ID
Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

My concerns were addressed here.
/lgtm


fix escape path for special chars

Added extra regex to handle special chars

Thanks for the contribution :shipit:


Storage version migrator v1beta1 -> v1

When we eventually remove v1beta1, users will need to migrate their stored CRDs to use v1 before upgrading to a version of Tekton Pipelines that removes v1beta1. This issue tracks implementation of a storage version migrator as described in the k8s docs.

Example k8s upstream tool that handles this : kubernetes-sigs/kube-storage-version-migrator
knative/pkg also has some "helpers" for this : apiextensions/storageversion/cmd/migrate
from @dibyom: this could also be a post-install job like https://github.com/knative/serving/blob/main/config/post-install/storage-version-migration.yaml

/assign


Configurations for LevelDB, RocksDB and their collections

Such configurations should control the exact behavior of separate collections and will differ depending on modality:

document collections may constrain types of JSON members under given JSON Pointers.
graph collections may enable or disable multi-graph support, directedness, and graph-specific compression.
vector collections may tune hyper-parameters affecting tradeoffs between search quality and speed.
binary collections may hint expected blob sizes that may affect the underlying compaction policy of LSM trees.

Aside from those, the more obvious modality-agnostic configurations would include:

manually set memory budgets for caching in persistent variants.
custom directory paths to support better tiering between SSDs and HDDs connected to the same node.

Most DBMS engines don't provide any space to store collection-specific metadata, so this will need a separate persisting mechanism. The simplest solution would be to use JSON files, as we already include two JSON parsers in our builds.

:tada: This issue has been resolved in version 0.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


spring @Aspect can not work with swagger2

pom.xml version info:

springfox-swagger2: 2.5.0
swagger-core: 1.5.10
springfox-swagger-ui: 2.6.1
springboot: 1.5.3

I has a project with swagger2 and springboot.
The project code without @Aspect works very well.The code reads as follows.
public interface TestApi {
    WfExecution test(Long temp);
}

@Api(value = "TestAPI")
@RequestMapping(value = "/test")
@RestController
public class TestApiImpl implements TestApi {

    @Override
    @RequestMapping(value = "/test")
    @ApiOperation(value = "", notes = "", produces = MediaType.APPLICATION_JSON)
    public WfExecution test(@ApiParam(value = "", required = true) @RequestParam(required = true, value = "temp")
                                        Long temp) {
        return new WfExecution();
    }
}

the right result:

But when I add the follow code, the swagger-ui doesn't show the test-api-impl.
@Aspect
@Component
public class LoggerAop {
    @Before("execution(* com.XXX.controller.impl.TestApiImpl.*(..))")
    public void doBeforeAdvice(JoinPoint joinPoint){
            System.out.println("XXX");
    }
}

the error result:

Is there a conflict between swagger and spring AOP?

Please upgrade to 2.7.0

I upgrade to 2.7.0. But It not works.
And I find that there is one proxy class in webUi. Its method is the same as that of the TestApi class.

When I add the @EnableAspectJAutoProxy(proxyTargetClass=true) , swagger and aop work well.

Hi,
I am using openapi3 and spring boot 2.3.1.
I am facing the similar kind of issue.
@Aspect
@Configuration
@EnableAspectJAutoProxy(proxyTargetClass = true)
public class UserAccessAspect {}


CloudWatch log group class

Hello, team can you add cloudwatch "log_group_class" variable

This issue has been resolved in version 2.8.0 :tada:


Fix cut off dashboard header image

https://openedx.atlassian.net/browse/MA-947
@hanningni please review

:+1:


Add statistics for runv Pod

Add statistics for runv Pod, only libvirt driver is supported now.

LGTM


user-profile: Add mobile-responsive styling.

This changes the styling of the user profile popup to be responsive
to mobile devices. In this case it is converted to a modal form using
flex to center it on devices with screen sizes under 768px in width.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

Looks great, merged, after adding the missing "Fixes: #4669" tag to the commit message.  Thanks @brockwhittaker!


Groq Llama 3.1

Added new Llama 3.1 model via Groq.
But getting this error message when trying to chat. Does this mean it's not yet available via API or something?

Early API access to Llama 3.1 405B is currently only available to paying customers - stay tuned for general availability. During preview launch, we are limiting all 3.1 models to max_tokens of 8k and 405b to 16k input tokens: https://console.groq.com/docs/models


Implement multi-slide macros

Hi!
Since I wanted to use the macros to stagger lists into slides and needed to generate multiple slides with macros as suggested in #488, I implemented the feature.
The behavior is now: When a macro is used inline and emits multiple slides, the first slide emitted is appended to the currently active slide, which is then pushed. The following slides are all pushed except the last one, which becomes the new active slide on the stack.
My reasoning for this behavior is the following scenario:
...
---

![:stagger](
# headline

%%%
- list element
  - sub element
  - sub element
%%%
- list element
%%%
- list element
%%%
- list element
%%%
- list element
%%%
- list element
)

---
...

With this macro implementation:
remark.macros.stagger = function () {
  return this.split('%%%\n').reduce(({ output, current }, part) => {
    const next = current + part
    return {
      output: output + next + '---\n',
      current: next
    }
  }, { output: '', current: '' }).output;
}

Looking forward to any feedback and with kind regards,
yeldiR

What does this do that the standard way does not?
---
## header of slide

* topic 1
--
  * sub topic 1a
--
  * sub topic 1b
--
* topic 2
--
* topic 3

Your example creates multiple slides with one part of the list each, right? Or am I missing a feature?
I want to create multiple pages with an incrementally larger part of the list showing. As I see it that is currently not possible with or without macros.

Huh. I wasn't aware of that. In that case, no macro is needed.
Thank you!


crowd dc added in product list

Pull request description
Provide description for the PR
Checklist

[ ] I have successful end to end tests run (with & without domain)
[ ] I have added unit tests (if applicable)
[ ] I have user documentation (if applicable)

Closing in favor of https://github.com/atlassian-labs/data-center-terraform/pull/315


Resuming from hibernation crashes the application (Windows)

On a laptop waking back up, the application reports the following error:

This was the JSON port of the language server:
[org.enso.languageserver.boot.LanguageServerComponent] Started server at json:<IP_ADDRESS>:60829,

I will test it as well on some old WIndows machine

I can confirm. From the logs it looks like something requests a shutdown. Will investigate.

This has been fixed a while ago, at least the backend part, in

#7470
#7729

So it appears to be a regression.

Tested polyglot version of NodeJS

That obviously meant polyglot version of Ydoc

Closed via #11712 and #11739


⚠ Bofrost.lu has degraded performance

In 34fcd70, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1215 ms

Resolved: Bofrost.lu performance has improved in e42b233 after 9 minutes.


Signals are not restarting on pause

What Happened?
Signals created with NH are not playing from start after pause
What was supposed to happen?
Travellers signals are restearting after the pause and playing from beginning.
Platform
None
Mods
No response
Logs
No response

I'm not sure what this means

im testing christmas mod now, and signals are indeed playing from the start after pausing and unpausing. so im counting this as fixed


[ROCKETMQ-160]SendHeartBeat may not be logged in the expected period

JIRA:https://issues.apache.org/jira/browse/ROCKETMQ-160

Coverage decreased (-0.004%) to 31.879% when pulling fab38018a89ace83a079f0f39c233dff91735e14 on Jaskey:ROCKETMQ-160-heartbeat-log into 45a64fd6a8ab66a8b0eb30cbe2dffd59b19274f9 on apache:develop.

Coverage decreased (-0.004%) to 31.879% when pulling fab38018a89ace83a079f0f39c233dff91735e14 on Jaskey:ROCKETMQ-160-heartbeat-log into 45a64fd6a8ab66a8b0eb30cbe2dffd59b19274f9 on apache:develop.

@lizhanhui @zhouxinyu
Any guys come to review this trival changes?

@shroman
For your first point, I would like to remain the existing flow? Because the heart beat sent may be failed and if we only mark the success one, we maybe miss the log for long turn when send heartbeat is failed for many times and then become success.  But anyway this is a minor issue , I will follow your advice if you guys think it is better.
For your second point, I agree and I will proceed.

IMO, log SendHeartBeat records of all brokers every 20 times is reasonable.

@zhouxinyu , hmm, it depends on what we need.
The issue I post is that , the log is not doing as expected when the addr table is empty. Even though log for all broker is reasonable, a empty check will be needed.
I will follow your advice after more guys review.

@Jaskey Incrementing and logging heartbeats on success seems reasonable to me. All failures are logged in catch clause.

@lizhanhui  yes it seems reasonable to send heartbeat for all broker as one time.
Please review the updated pr which only

check if the beartbeat table is empty, only log and calculate times when it is not empty
rename the heartbeat times variable

Coverage increased (+0.04%) to 37.891% when pulling d86e994c68d8373895c554d543168ef4b5e5d426 on Jaskey:ROCKETMQ-160-heartbeat-log into 6a9628b3c3e6835e37baf7b58ad9300364d4d384 on apache:develop.

Coverage increased (+0.04%) to 37.891% when pulling d86e994c68d8373895c554d543168ef4b5e5d426 on Jaskey:ROCKETMQ-160-heartbeat-log into 6a9628b3c3e6835e37baf7b58ad9300364d4d384 on apache:develop.

IMO, it's good and reasonable that counter should record the heartbeat's real request.

@dongeforever
hiw does this pr go, is it been merged？

@Jaskey Yeah. it has been merged


Start Error

Why i recive thies error ?
root@vps-zap59814x-4:~/SnapchatBot-master/examples# python reflectorbot.py -u noxxxxx -p 19wr#%xxxxxxxxx
[1] 21608
-bash: FeFOZyU9T@T2YRyUR%SxPz%Sg7vOCrdg5: command not found
root@vps-zap59814-4:~/SnapchatBot-master/examples# [2018-12-05 11:02:36,165] Starting new HTTPS connection (1): feelinsonice-hrd.appspot.com:443
[2018-12-05 11:02:36,536] https://feelinsonice-hrd.appspot.com:443 "POST /loq/login HTTP/1.1" 400 None
Traceback (most recent call last):
File "reflectorbot.py", line 22, in
bot = ReflectorBot(args.username, args.password)
File "build/bdist.linux-x86_64/egg/snapchat_bots/bot.py", line 26, in init
File "/usr/local/lib/python2.7/dist-packages/requests-2.20.1-py2.7.egg/requests/models.py", line 897, in json
return complexjson.loads(self.text, **kwargs)
File "/usr/lib/python2.7/json/init.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

I have the same error and without any idea how to fix it. Did anybody got a fix?

First line in the readme
"This repo is deprecated due to changes in Snapchat's unofficial API."

So there is no way to send snaps again ?


_call.py - environment variables are being override in the subprocess.check_output method

Recently, as part of the change in commit  'Always set PIP_YES to avoid prompts' (a21d85) a dictionary was added as an env argument into the subprocess.check_output method.
When setting the env argument, the called sub-process can't access the environment variable of the base process.
The impact is that i'm getting an error (attached below) when i try to import the last version of  pip-api (0.0.19)
The following code change solved the problem on my host :

i would recommend to add the PIP_YES variable upon the existing system variable.
More Information
Error message:

Subprocess module note about env variable :

I forgot to mention that i'm using pip-download library  - which actually call the pip-api import on line 12.

Thanks for raising! Looks like we should be merging PIP_YES into os.environ and passing that as env instead.

Fixed in https://pypi.org/project/pip-api/0.0.20/

Tested on Windows 10; no issues!


Setup with eclipse ee oxygen on tomcat

Versions.

I have set up eclipse ee oxygen with jsf/cxf libraries,tomcat server and mysql database. Problem is I want to integrate Angular 4 as the default front-end. This means, I need the dynamic web project to display the Angular 4 html and css on tomcat's server.

I'm sorry, I have no idea how to setup all those things together. A better place to ask would be Stack Overflow.


Content update

What

remove header links to Get started, roadmap and features
remove get an account section
remove references to trial accounts and upgrades to billable
move some of "before you start" content to responsibility model" and delete page

How to review
Describe the steps required to test the changes.

Preview the content locally (see README) and check that it renders as expected.
Manually check that any removed or renamed anchor tags are not in use (linkchecker doesn't do this).
…

Who can review
not @kr8n3r
Preview

changes accepted

on the home page it says: "GOV.UK PaaS is a live service."
this is true however I think it should be qualified with a statement to the effect that the plan it to decommission the platform by 22nd December 2023.
in the section at the bottom it says "GOV.UK PaaS uses the open source Cloud Foundry project, and runs on Amazon Web Services. Read our blog post on why we chose Cloud Foundry for more information." this dates back to the original alpha and should be replaced with updated content to reflect the current situation. i.e. that the platform is being decomissioned.
maybe

GOV.UK PaaS uses the open source Cloud Foundry project, and runs on Amazon Web Services. The platform is being decommissioned by Dec 22nd 2023. Read our blog post on why we chose to decommission our platform

updated


feat: add npm badge to readme

PR Checklist

[X] Addresses an existing open issue: fixes #730
[X] That issue was marked as status: accepting prs
[X] Steps in CONTRIBUTING.md were taken

Overview
Added npm version badge to readme file. Also added it to the template that creates the file: src/steps/writeReadme/generateTopContent.ts

Yikes. I think I failed to include one updated file. How about now?
All test are passing locally


bridged network and qemu-agent

Just wanted to call out that if you want to use a bridged network, whatever cloud image you end up using seems to require that the qemu-guest-agent package be built into the image.  If the upstream vendor does not do this (Ubuntu), you need to customize the image yourself.  In my case, simply switching from Ubuntu vendor image to CentOS vendor image (vendor includes qemu-guest-agent by default in their cloud image) just made everything work.   Not sure if you want to call this out in your README or not, just wanted to share.
Also, thank you for building this, very, very cool.

Hi, I'm glad you like the project.
Thanks for pointing out this issue. That's very interesting, because cloud_init should make sure that qemu-guest-agent is installed and running.
Take a look at this code snippet from templates/cloud_init/cloud_init.tpl:
...

packages:
  - qemu-guest-agent

runcmd:
  - [ systemctl, enable, qemu-guest-agent.service ]
  - [ systemctl, start, qemu-guest-agent.service ]

So, could it be that other cloud images (besides the CentOS image) are not missing the 'qemu-guest-agent' package, but the 'cloud_init' package? Could you please provide the URLs of the images that do not work?
For Ubuntu, for example, I use images from this site https://cloud-images.ubuntu.com/ and they seem to work just fine.

Are you using static IPs or DHCP leases?
If you are using static IPs, the problem could have been the DNS.
When VM with static IP was created, no default DNS was specified (this was not the case when using DHCP because DHCP server passes nameservers to the client). That probably resulted in qemu-guest-agent not being installed on boot.
I fixed that in cab0d3cc0cfc3dd941e9bb9981692e75d6bc577b commit. Now gateway is added as a primary DNS server, and Google's well known <IP_ADDRESS> DNS as a secondary.
I would appreciate, if you could verify that was the case.


ES1-631 - TTS thunder interface change

Reason for change: TTS plugin to support callsign based registeration
Test Procedure: Mentioned in ticket
Risks: Low

This looks like redundant functionality as by default, the IShell interface (part of every plugin) allows for QueryInterfaceByCallsign, so I think it is superfluous and unnecessary but as I am not the component owner of the implementation of this plugin I will approve. @karuna2git  to validate the usefulness of this method!


Add SetBasisState and SetState to lightning.kokkos

Context: In order for the StatePrep and BasisState optimizations be implemented, the kokkos device needs to be modified. Since the kokkos device is migrating to the pennylane-lightning repo, it is necessary that these changes are also in the pennylane-lightning repo.
Description of the Change: Copies over changes from Catalyst regarding kokkos into the pennylane-lightning repo.
Related GitHub Issues: https://github.com/PennyLaneAI/catalyst/pull/955
Notes: The tests won't pass until the PR  https://github.com/PennyLaneAI/catalyst/pull/955 is merged, since it updates the Catalyst Quantum Device API.

Closed in favour of: https://github.com/PennyLaneAI/pennylane-lightning/pull/843


A plan without periodicity, the Free plan

The Free plan should be unlimited, so is it possible to just create a plan without providing periodicity_type and periodicity ? everything will keeps working ?

I think the maintainer of this package does not want to engage in billing functionalities which is pretty understandable considering the unlimited scope. but you can achieve this functionality through manually overriding the expiration date and setting it to a pretty far date in the future. or I think it's nullable so you can try setting it to null and the subscription will never expire. although the way I handled free plans on my app is different. I have a command that automatically resumes subscriptions. and what I do regarding the free plan is to automatically resume it when it expires without asking for an invoice payment. and the way to check if it's a free plan depending on your implementation. either it's an extra column such as "is_free "or "price". in your plans table
So you have many ways to deal with the Free plan but it's outside of this package scope. Good Luck

Hey! I've wondered how to address this issue and decided to make the periodicity-related columns nullable, so it will be possible to create plans with no expiration set. I'm working on this right now.
Besides that, @omaressaouaf is right about billing: we are going to keep it out of the scope of this package. 😅

Hi! Version 4.1 introduces the ability to create plans without periodicity (which can be used to create "free plans"). Sorry for taking so long to release it! 😅

This is what we get when trying to consume a free plan
"LucasDotVin\\Soulbscription\\Enums\\PeriodicityType::getDateDifference(): Argument #3 ($unit) must be of type string, null given, called in /var/www/html/vendor/lucasdotvin/laravel-soulbscription/src/Models/Concerns/HandlesRecurrence.php on line 20"

to

is there any fix for this? thank you
This happened to me for this 2 plan
$basic = Plan::create([
"name"             => "basic",
'periodicity_type' => null,
'periodicity'      => null,
]);
    $monthly = Plan::create([
        'name'             => 'monthly',
        'periodicity_type' => PeriodicityType::Month,
        'periodicity'      => 1,
    ]);


fix null when parsing allOf with no properties

Coverage decreased (-0.3%) to 96.471% when pulling 8c67517268c574608a7b3951cfa62c8d16167503 on null-with-allOf-no-properties into 79fb160abf748d6b1728036bf893e666ec346139 on master.


tatweel_test

@stweil I am running into errors while building tatweel_test, these are related to tensorflow.
I have installed  tensorflow and protobuf by
sudo pip3 install --upgrade https://powerci.osuosl.org/job/TensorFlow_PPC64LE_CPU_Nightly_Artifact/lastSuccessfulBuild/artifact/tensorflow_pkg/tf_nightly-2.0.0.dev20190707-cp36-cp36m-linux_ppc64le.whl

I made the following symbolic links so that the include files would be found.
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/tensorflow /usr/local/include/tensorflow
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/tensorflow/core/protobuf  /usr/local/include/protobuf
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/google /usr/local/lib/google

Now I am getting the following error regarding missing file google/protobuf/util/message_differencer.h. As shown later via ls, the file exists. I don't know how to resolve this. Probably needs some change to include path to find the files.
depbase=`echo tatweel_test.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
g++ -DHAVE_CONFIG_H -I. -I../../unittest -I..  -DNDEBUG -DTESSBIN_DIR="\"/home/ubuntu/tesseract/bin\"" -DLANGDATA_DIR="\"/home/ubuntu/langdata_lstm\"" -DTESSDATA_DIR="\"/home/ubuntu/tessdata\"" -DTESSDATA_BEST_DIR="\"/home/ubuntu/tessdata_best\"" -DTESTING_DIR="\"/home/ubuntu/tesseract/test/testing\"" -DTESTDATA_DIR="\"/home/ubuntu/tesseract/test/testdata\"" -DPANGO_ENABLE_ENGINE  -I../src/api -I../../src/api -I../../src/arch -I../../src/ccmain -I../../src/ccstruct -I../../src/ccutil -I../../src/classify -I../../src/cutil -I../../src/dict -I../../src/display -I../../src/lstm -I../../src/textord -I../../unittest/base -I../../unittest/util -I../../src/training -I../../src/viewer -I../../src/wordrec -I../../abseil  -isystem ../../googletest/googletest/include -isystem ../../googletest/googlemock/include -I/usr/include/leptonica   -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16  -g -O2 -Wall -Wextra -Wpedantic -std=c++17 -MT tatweel_test.o -MD -MP -MF $depbase.Tpo -c -o tatweel_test.o ../../unittest/tatweel_test.cc &&\
mv -f $depbase.Tpo $depbase.Po
In file included from ../../unittest/util/utf8/unicodetext.h:25:0,
                 from ../../unittest/tatweel_test.cc:22:
../../unittest/syntaxnet/base.h:25:10: fatal error: google/protobuf/util/message_differencer.h: No such file or directory
 #include "google/protobuf/util/message_differencer.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:1861: recipe for target 'tatweel_test.o' failed
make[2]: *** [tatweel_test.o] Error 1
make[2]: Leaving directory '/home/ubuntu/tesseract/bin/unittest'
Makefile:2592: recipe for target 'check-am' failed
make[1]: *** [check-am] Error 2
make[1]: Leaving directory '/home/ubuntu/tesseract/bin/unittest'
Makefile:502: recipe for target 'check-recursive' failed
make: *** [check-recursive] Error 1

ls  /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/google/protobuf/util/message_differencer.h -l

-rw-r--r-- 1 root staff 44587 Jul  8 09:42 /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/google/protobuf/util/message_differencer.h

It is part of libprotobuf-dev on Debian. That package is installed automatically with libtensorflow-dev:
libprotobuf-dev:amd64: /usr/include/google/protobuf/util/message_differencer.h

Ah, I see, your third symbolic link should link to include instead of lib.

I had tried getting the debian package but couldn't install it.
ubuntu@tesseract-ocr:~$ wget http://ftp.mx.debian.org/debian/pool/main/t/tensorflow/libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb
--2019-07-08 13:28:37--  http://ftp.mx.debian.org/debian/pool/main/t/tensorflow/libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb
Resolving ftp.mx.debian.org (ftp.mx.debian.org)... <IP_ADDRESS>
Connecting to ftp.mx.debian.org (ftp.mx.debian.org)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2296976 (2.2M) [application/x-debian-package]
Saving to: ‘libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb’

libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb      100%[==========================================================================================================>]   2.19M   935KB/s    in 2.4s

2019-07-08 13:28:41 (935 KB/s) - ‘libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb’ saved [2296976/2296976]

ubuntu@tesseract-ocr:~$ sudo dpkg -i libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb
Selecting previously unselected package libtensorflow-dev:ppc64el.
(Reading database ... 243965 files and directories currently installed.)
Preparing to unpack libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb ...
Unpacking libtensorflow-dev:ppc64el (1.10.1+dfsg-A1) ...
dpkg: dependency problems prevent configuration of libtensorflow-dev:ppc64el:
 libtensorflow-dev:ppc64el depends on libtensorflow-framework1.10 (= 1.10.1+dfsg-A1); however:
  Package libtensorflow-framework1.10 is not installed.
 libtensorflow-dev:ppc64el depends on libtensorflow1.10 (= 1.10.1+dfsg-A1); however:
  Package libtensorflow1.10 is not installed.
 libtensorflow-dev:ppc64el depends on libtensorflow-cc1.10 (= 1.10.1+dfsg-A1); however:
  Package libtensorflow-cc1.10 is not installed.
 libtensorflow-dev:ppc64el depends on libprotobuf-dev (>= 3.6.0~); however:
  Package libprotobuf-dev is not installed.
 libtensorflow-dev:ppc64el depends on libgrpc++-dev (>= 1.14.1~); however:
  Package libgrpc++-dev is not installed.
 libtensorflow-dev:ppc64el depends on llvm-7-dev (>= 1:7~+rc2-1~exp1~); however:
  Package llvm-7-dev is not installed.

dpkg: error processing package libtensorflow-dev:ppc64el (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libtensorflow-dev:ppc64el
ubuntu@tesseract-ocr:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libllvm7 libprotobuf-lite10 linux-headers-4.15.0-51 linux-headers-4.15.0-51-generic linux-image-4.15.0-51-generic linux-modules-4.15.0-51-generic linux-modules-extra-4.15.0-51-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  libtensorflow-dev
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 21.6 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 245957 files and directories currently installed.)
Removing libtensorflow-dev:ppc64el (1.10.1+dfsg-A1) ...

Fixing the symbolic link would be easier.

libprotobuf-dev is available for Ubuntu.

libprotobuf-dev is available for Ubuntu.

That is an older version which gives errors with tensorflow.

Fixing the symbolic link would be easier.

Thanks for noticing that error.
I am trying with the correct symbolic link. It is giving some other errors. I need to test with a clean install.

error is related to use of LOG in /unittest/util/utf8/unicodetext.cc

I now got this linker error on a different build machine, too. It is fixed in Git master. Thanks to @jbreiden, I could add the missing ara.* files to the test submodule. So tatweel_test now runs all subtests successfully.

Thanks.
I removed the nightly build of tensorflow and manually installed the required packages and dependencies from debian experimental and unstable. I also updated the repo with the latest code.
 git log -1
commit e94392ef10618b7fc155dab25e5814bf70b4fe79 (HEAD -> master, origin/master, origin/HEAD)
Author: Stefan Weil<EMAIL_ADDRESS>Date:   Tue Jul 9 11:48:56 2019 +0200

    Update test submodule and fix pagesegmode_test
``

I am now getting an error for a different program.

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/lstm -I../.. -DNDEBUG -I../../../src/ccutil -I../../../src/cutil -I../../../src/ccstruct -I../../../src/arch -I../../../src/viewer -I../../../src/classify -I../../../src/dict -I../../../src/lstm -DINCLUDE_TENSORFLOW -I/usr/include/tensorflow -I/usr/include/leptonica -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -fopenmp -DTESSDATA_PREFIX=/usr/local/share -g -O2 -std=c++17 -MT recodebeam.lo -MD -MP -MF .deps/recodebeam.Tpo -c ../../../src/lstm/recodebeam.cpp  -fPIC -DPIC -o .libs/recodebeam.o
In file included from /usr/include/tensorflow/core/framework/tensor.h:19:0,
from /usr/include/tensorflow/core/public/session.h:24,
from ../../../src/lstm/tfnetwork.h:32,
from ../../../src/lstm/network.cpp:42:
/usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor:1:10: fatal error: unsupported/Eigen/CXX11/Tensor: No such file or directory
#include "unsupported/Eigen/CXX11/Tensor"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from /usr/include/tensorflow/core/framework/tensor.h:19:0,
from /usr/include/tensorflow/core/public/session.h:24,
from ../../../src/lstm/tfnetwork.h:32,
from ../../../src/lstm/network.cpp:42:
/usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor:1:10: fatal error: unsupported/Eigen/CXX11/Tensor: No such file or directory
#include "unsupported/Eigen/CXX11/Tensor"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:511: recipe for target 'network.lo' failed
make[1]: *** [network.lo] Error 1
make[1]: Leaving directory '/home/ubuntu/tesseract/bin/src/lstm'

The file in error seems to be there...

ls -l /usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor
-rw-r--r-- 1 root root 420 Aug 23  2018 /usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor

The missing file is part for libtensorflow-dev:
debian@development:~/src/github/tesseract-ocr/tesseract$ ls -l /usr/include/tensorflow/unsupported/Eigen/CXX11/Tensor
-rw-r--r-- 1 root root 4400 Jun 23  2018 /usr/include/tensorflow/unsupported/Eigen/CXX11/Tensor
debian@development:~/src/github/tesseract-ocr/tesseract$ dpkg -S /usr/include/tensorflow/unsupported/Eigen/CXX11/Tensor
libtensorflow-dev:amd64: /usr/include/tensorflow/unsupported/Eigen/CXX11/Tensor

On my system, the file is there, but it is installed in a different subfolder.
dpkg -S /usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor
libtensorflow-dev:ppc64el: /usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor

The path mentioned by you is not found:
 dpkg -S /usr/include/tensorflow/unsupported/Eigen/CXX11/Tensor
dpkg-query: no path found matching pattern /usr/include/tensorflow/unsupported/Eigen/CXX11/Tensor

That's the wrong one. The package for x86_64 includes both files:
$ ls -ld $(dpkg -L libtensorflow-dev | grep 'Tensor$')
-rw-r--r-- 1 root root  420 Aug 23  2018 /usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor
drwxr-xr-x 2 root root 4096 Mai 24 19:41 /usr/include/tensorflow/unsupported/Eigen/CXX11/src/Tensor
-rw-r--r-- 1 root root 4400 Jun 23  2018 /usr/include/tensorflow/unsupported/Eigen/CXX11/Tensor

These are the files from libtensorflow-dev_1.10.1+dfsg-A1_ppc64el.deb
$ ls -ld $(dpkg -L libtensorflow-dev | grep 'Tensor$')
drwxr-xr-x 2 root root 4096 Jul 10 03:37 /usr/include/tensorflow/eigen3/unsupported/Eigen/CXX11/src/Tensor
-rw-r--r-- 1 root root 4400 Jun 22  2018 /usr/include/tensorflow/eigen3/unsupported/Eigen/CXX11/Tensor
-rw-r--r-- 1 root root  420 Aug 23  2018 /usr/include/tensorflow/third_party/eigen3/unsupported/Eigen/CXX11/Tensor

@stweil  I tried the following, however tesseract is failing to build.
sudo pip3 install --upgrade https://powerci.osuosl.org/job/TensorFlow_PPC64LE_CPU_Nightly_Artifact/lastSuccessfulBuild/artifact/tensorflow_pkg/tf_nightly-2.0.0.dev20190707-cp36-cp36m-linux_ppc64le.whl

sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/google /usr/local/include
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/tensorflow /usr/local/include
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/tensorflow/core/protobuf  /usr/local/include
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/third_party  /usr/local/include
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/unsupported  /usr/local/include
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/absl  /usr/local/include
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/include/Eigen /usr/local/include

Since tf-nightly is built with protobuf 3.8.0, it was getting an error from https://github.com/tesseract-ocr/tesseract/blob/master/src/lstm/tfnetwork.pb.h about version.
download protobuf-all-3.8.0.zip
build protobuf
protoc --version
libprotoc 3.8.0

git clone tensorflow repo

protoc --cpp_out=$PWD --proto_path=../tensorflow \
                       --proto_path=$PWD src/lstm/tfnetwork.proto

Change tfnetwork.pb.cc to use #include "tfnetwork.pb.h"

However, tesseract still doesn't build.
Making all in src/api
make[2]: Entering directory '/home/ubuntu/tesseract/bin/src/api'
/bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 -std=c++17   -o tesseract tesseract-tesseractmain.o libtesseract.la -llept -fopenmp -lprotobuf -ltensorflow_cc   -lrt -lpthread
libtool: link: g++ -g -O2 -std=c++17 -o .libs/tesseract tesseract-tesseractmain.o -fopenmp  ./.libs/libtesseract.so -llept -lprotobuf -ltensorflow_cc -lrt -lpthread -fopenmp
/usr/bin/ld: cannot find -ltensorflow_cc
collect2: error: ld returned 1 exit status
Makefile:594: recipe for target 'tesseract' failed

tf nightly only had libtensorflow_framework.so.2 but that doesn't work either.
sudo ln -s /usr/local/lib/python3.6/dist-packages/tensorflow_core/libtensorflow_framework.so.2 /usr/local/lib/libtensorflow_framework.so

/bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 -std=c++17   -o tesseract tesseract-tesseractmain.o libtesseract.la -llept -fopenmp -lprotobuf -ltensorflow_framework   -lrt -lpthread

ubuntu@tesseract-ocr:~/tesseract/bin$ cd src/api
ubuntu@tesseract-ocr:~/tesseract/bin/src/api$ /bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 -std=c++17   -o tesseract tesseract-tesseractmain.o libtesseract.la -llept -fopenmp -lprotobuf -ltensorflow_framework   -lrt -lpthread
libtool: link: g++ -g -O2 -std=c++17 -o .libs/tesseract tesseract-tesseractmain.o -fopenmp  ./.libs/libtesseract.so -llept -lprotobuf -ltensorflow_framework -lrt -lpthread -fopenmp
./.libs/libtesseract.so: undefined reference to `tensorflow::internal::CheckOpMessageBuilder::NewString[abi:cxx11]()'
collect2: error: ld returned 1 exit status

Is there a way that I can disable tensorflow while building tesseract?

Yes: PATH/configure --with-tensorflow=no ....

Will also need a change to makefile for tatweel_test
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2 -std=c++17   -o
tfile_test tfile_test.o libgtest.la libgtest_main.la -lpthread ../src/api/
libtesseract.la   -lpthread
libtool: link: g++ -g -O2 -std=c++17 -o .libs/tatweel_test tatweel_test.o
third_party/utf/rune.o util/utf8/unicodetext.o util/utf8/unilib.o
./.libs/libgtest.a ./.libs/libgtest_main.a
../src/api/.libs/libtesseract.so -ltensorflow_cc -lpthread -fopenmp
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2 -std=c++17   -o
commandlineflags_test commandlineflags_test.o libgtest.la libgtest_main.la
-lpthread ../src/training/libtesseract_training.la ../src/training/
libtesseract_tessopt.la ../src/api/libtesseract.la   -licuuc -licudata
-lpthread
/usr/bin/ld: cannot find -ltensorflow_cc
collect2: error: ld returned 1 exit status
Makefile:1671: recipe for target 'tatweel_test' failed
On Wed, Jul 10, 2019 at 7:04 PM Stefan Weil<EMAIL_ADDRESS>wrote:

Yes: PATH/configure --with-tensorflow=no ....
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/2550?email_source=notifications&email_token=ABG37I3Z52CKLMO6CXTRKD3P6XQPDA5CNFSM4H62OND2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZTPDDI#issuecomment-510062989,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG37IZ6NAF23RBTAGBBKZ3P6XQPDANCNFSM4H62ONDQ
.

--

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com

Yes, you are right, thank you. Fixed now in master.

Can issue be closed?

@zdenop The workaround was to build with --with-tensorflow=no .
I tried to build without that just now with latest code and still get the errors.
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/lstm -I../.. -O2 -DNDEBUG -I../../../src/ccutil -I../../../src/cutil -I../../../src/ccstruct -I../../../src/arch -I../../../src/viewer -I../../../src/classify -I../../../src/dict -I../../../src/lstm -DINCLUDE_TENSORFLOW -I/usr/include/tensorflow -I/usr/include/leptonica -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -fopenmp -DTESSDATA_PREFIX=/usr/local/share -g -O2 -std=c++17 -MT recodebeam.lo -MD -MP -MF .deps/recodebeam.Tpo -c ../../../src/lstm/recodebeam.cpp -o recodebeam.o
In file included from ../../../src/lstm/tfnetwork.h:29:0,
                 from ../../../src/lstm/network.cpp:42:
../../../src/lstm/tfnetwork.pb.h:17:2: error: #error This file was generated by an older version of protoc which is
 #error This file was generated by an older version of protoc which is
  ^~~~~
../../../src/lstm/tfnetwork.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please
 #error incompatible with your Protocol Buffer headers.  Please
  ^~~~~
../../../src/lstm/tfnetwork.pb.h:19:2: error: #error regenerate this file with a newer version of protoc.
 #error regenerate this file with a newer version of protoc.
  ^~~~~
In file included from /usr/local/include/tensorflow/core/framework/tensor.h:22:0,
                 from /usr/local/include/tensorflow/core/public/session.h:24,
                 from ../../../src/lstm/tfnetwork.h:31,
                 from ../../../src/lstm/network.cpp:42:
/usr/local/include/tensorflow/core/framework/allocator.h:24:10: fatal error: absl/strings/string_view.h: No such file or directory
 #include "absl/strings/string_view.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:515: recipe for target 'network.lo' failed

That's strange. I just tested with configure --with-tensorflow=no, and it does not set the macro INCLUDE_TENSORFLOW. So tfnetwork.h should not be included.

I meant that I rebuilt just now without configure --with-tensorflow=no  and got the error.
When I use configure --with-tensorflow=no it builds ok.

I rebuilt the files using
protoc --cpp_out=$PWD --proto_path=../tensorflow \
                       --proto_path=$PWD src/lstm/tfnetwork.proto

Now the error is:
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/lstm -I../.. -O2 -DNDEBUG -I../../../src/ccutil -I../../../src/cutil -I../../../src/ccstruct -I../../../src/arch -I../../../src/viewer -I../../../src/classify -I../../../src/dict -I../../../src/lstm -DINCLUDE_TENSORFLOW -I/usr/include/tensorflow -I/usr/include/leptonica -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -fopenmp -DTESSDATA_PREFIX=/usr/local/share -g -O2 -std=c++17 -MT network.lo -MD -MP -MF .deps/network.Tpo -c ../../../src/lstm/network.cpp -o network.o
In file included from /usr/local/include/tensorflow/core/framework/tensor.h:22:0,
                 from /usr/local/include/tensorflow/core/public/session.h:24,
                 from ../../../src/lstm/tfnetwork.h:31,
                 from ../../../src/lstm/network.cpp:42:
/usr/local/include/tensorflow/core/framework/allocator.h:24:10: fatal error: absl/strings/string_view.h: No such file or directory
 #include "absl/strings/string_view.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:515: recipe for target 'network.lo' failed

Back again to the following error:
libtool: link: ( cd ".libs" && rm -f "libtesseract.la" && ln -s "../libtesseract.la" "libtesseract.la" )
/bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 -std=c++17   -o tesseract tesseract-tesseractmain.o libtesseract.la -llept -fopenmp -lprotobuf -ltensorflow_cc    -lrt -lpthread
libtool: link: g++ -g -O2 -std=c++17 -o tesseract tesseract-tesseractmain.o -fopenmp  ./.libs/libtesseract.a -llept -lprotobuf -ltensorflow_cc -lrt -lpthread -fopenmp
/usr/bin/ld: cannot find -ltensorflow_cc
collect2: error: ld returned 1 exit status
Makefile:600: recipe for target 'tesseract' failed

So, build issues with tensorflow on PPC64LE are still there.

As long as we don't have a TensorFlow model which works with Tesseract, the TensorFlow code in Tesseract is rather useless. I'd compile without it (unless you have such models).

Yes, I do compile without it.
This is not a problem with Tesseract. I will close the issue.
Thanks!


OpenGLEx.ConstructFor sometimes produces a paper airplane instead of anything useful

Expected Behavior:
A full screen rectangle generated with OpenGLEx.ConstructFor, which internally uses vertex array objects for speed, should be a rectangle spanning the entire screen.

Actual Behavior:
The full screen rectangle is actually drawn is weird and wonderful shapes, none of which resemble a full screen rectangle.

API: OpenGL

Current Workaround: Use ConstructUnoptimisedFor instead of ConstructFor when this issue is encountered.


[AIRFLOW-1265] Fix celery executor parsing CELERY_SSL_ACTIVE

Dear Airflow maintainers,
Fix celery executor config parsing of celery/celery_ssl_active key
Changed retrieval of celery/celery_ssl_active to use configuration.getboolean()
Add correct except block and log warning if celery/celery_ssl_active key is left undefined
@orezahc made this PR pull/2340 but it doesn't address the exception masking.
Which causes the celery executor to fail if celery/celery_ssl_active is left undefined.
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1265

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
This is a bug fix, i.e. the current behaviour is broken so must be missing tests as is.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@868bfe4). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #2341   +/-   ##
=========================================
  Coverage          ?   69.44%
=========================================
  Files             ?      144
  Lines             ?    11043
  Branches          ?        0
=========================================
  Hits              ?     7669
  Misses            ?     3374
  Partials          ?        0

Impacted Files
Coverage Δ

airflow/executors/celery_executor.py
0% <0%> (ø)

Continue to review full report at Codecov.

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

Please fix your commit according to the guidelines (Jira, subject line etc)

Fixed PR info and squashed commits

Woot. @bolkedebruin Can this be merged please? Master is currently broken for using Celery executor on SQS with the otherwise default config.

Please fix the commit message. There's a typo and the subject line looks too long

@saguziel done

The commit message should still start with [AIRFLOW-xxxx]

@holygits  can you rebase this


Chrome tries to load .../gitea/gitea/img/logo.png, Firefox loads .../gitea/img/logo.png

Gitea version (or commit ref): 1.14.0+dev-575-g1c230f69d
Git version: 2.25.1
Operating system: ubuntu-20.04
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No

I'm using the context /gitea for my instance

Description
After clicking on the upper left logo, chrome tries to load several urls. There are two logo urls:

logo.svg ... this is ok - https://hetzner-de.daemons-point.com/gitea/img/logo.svg
logo.png ... this is KO, it contains the context "/gitea" twice - https://hetzner-de.daemons-point.com/gitea/gitea/img/logo.png

For firefox the error doesn't happen. Firefox does not try to load the PNG logo.
Screenshots
Chrome:

Firefox:

The only place where we still use the PNG should be the meta tag <meta property="og:image" content="/img/logo.png" />. What does that tag's URL look like in your case?

The only place where we still use the PNG should be the meta tag <meta property="og:image" content="/img/logo.png" />. What does that tag's URL look like in your case?

I see these two pngs
$ curl -s https://hetzner-de.daemons-point.com/gitea|grep png
	<link rel="alternate icon" href="/gitea/img/favicon.png" type="image/png">
	<meta property="og:image" content="/gitea/img/logo.png" />

The SVG looks similar:
       <link rel="icon" href="/gitea/img/logo.svg" type="image/svg+xml">

Maybe for the PNG, og:url and og:image are contatenated somewhere somehow?
        <meta property="og:image" content="/gitea/img/logo.png" />
        <meta property="og:url" content="https://hetzner-de.daemons-point.com/gitea/" />

I see these two pngs
$ curl -s https://hetzner-de.daemons-point.com/gitea|grep png
	<link rel="alternate icon" href="/gitea/img/favicon.png" type="image/png">
	<meta property="og:image" content="/gitea/img/logo.png" />

The SVG looks similar:
       <link rel="icon" href="/gitea/img/logo.svg" type="image/svg+xml">

Maybe for the PNG, og:url and og:image are contatenated somewhere somehow?
        <meta property="og:image" content="/gitea/img/logo.png" />
        <meta property="og:url" content="https://hetzner-de.daemons-point.com/gitea/" />

The manifest looks like this:
       <link rel="manifest" href="data:application/json;base64,eyJuYW1lIjoiR2l0ZWE6IEdpdCB3aXRoIGEgY3VwIG9mIHRlYSIsInNob3J0X25hbWUiOiJHaXRlYTogR2l0IHdpdGggYSBjdXAgb2YgdGVhIiwic3RhcnRfdXJsIjoiaHR0cHM6Ly9oZXR6b
mVyLWRlLmRhZW1vbnMtcG9pbnQuY29tL2dpdGVhLyIsImljb25zIjpbeyJzcmMiOiJodHRwczovL2hldHpuZXItZGUuZGFlbW9ucy1wb2ludC5jb20vZ2l0ZWEvZ2l0ZWEvaW1nL2xvZ28ucG5nIiwidHlwZSI6ImltYWdlL3BuZyIsInNpemVzIjoiNTEyeDUxMiJ9LHsic3JjIj
oiaHR0cHM6Ly9oZXR6bmVyLWRlLmRhZW1vbnMtcG9pbnQuY29tL2dpdGVhL2dpdGVhL2ltZy9sb2dvLnN2ZyIsInR5cGUiOiJpbWFnZS9zdmcreG1sIiwic2l6ZXMiOiI1MTJ4NTEyIn1dfQ=="/>

or:
{
    "icons": [
        {
            "sizes": "512x512",
            "src": "https://hetzner-de.daemons-point.com/gitea/gitea/img/logo.png",
            "type": "image/png"
        },
        {
            "sizes": "512x512",
            "src": "https://hetzner-de.daemons-point.com/gitea/gitea/img/logo.svg",
            "type": "image/svg+xml"
        }
    ],
    "name": "Gitea: Git with a cup of tea",
    "short_name": "Gitea: Git with a cup of tea",
    "start_url": "https://hetzner-de.daemons-point.com/gitea/"
}

The manifest looks like this:
       <link rel="manifest" href="data:application/json;base64,eyJuYW1lIjoiR2l0ZWE6IEdpdCB3aXRoIGEgY3VwIG9mIHRlYSIsInNob3J0X25hbWUiOiJHaXRlYTogR2l0IHdpdGggYSBjdXAgb2YgdGVhIiwic3RhcnRfdXJsIjoiaHR0cHM6Ly9oZXR6b
mVyLWRlLmRhZW1vbnMtcG9pbnQuY29tL2dpdGVhLyIsImljb25zIjpbeyJzcmMiOiJodHRwczovL2hldHpuZXItZGUuZGFlbW9ucy1wb2ludC5jb20vZ2l0ZWEvZ2l0ZWEvaW1nL2xvZ28ucG5nIiwidHlwZSI6ImltYWdlL3BuZyIsInNpemVzIjoiNTEyeDUxMiJ9LHsic3JjIj
oiaHR0cHM6Ly9oZXR6bmVyLWRlLmRhZW1vbnMtcG9pbnQuY29tL2dpdGVhL2dpdGVhL2ltZy9sb2dvLnN2ZyIsInR5cGUiOiJpbWFnZS9zdmcreG1sIiwic2l6ZXMiOiI1MTJ4NTEyIn1dfQ=="/>

or:
{
    "icons": [
        {
            "sizes": "512x512",
            "src": "https://hetzner-de.daemons-point.com/gitea/gitea/img/logo.png",
            "type": "image/png"
        },
        {
            "sizes": "512x512",
            "src": "https://hetzner-de.daemons-point.com/gitea/gitea/img/logo.svg",
            "type": "image/svg+xml"
        }
    ],
    "name": "Gitea: Git with a cup of tea",
    "short_name": "Gitea: Git with a cup of tea",
    "start_url": "https://hetzner-de.daemons-point.com/gitea/"
}

Thanks. pretty certain it's a bug in the manifest generation.

Thanks. pretty certain it's a bug in the manifest generation.

I looked at modules/setting/setting.go and it seems that MakeAbsoluteAssetURL is called with
appURL: https://hetzner-de.daemons-point.com/gitea/, staticURLPrefix: /gitea
and it returns the concatenation of these...

I looked at modules/setting/setting.go and it seems that MakeAbsoluteAssetURL is called with
appURL: https://hetzner-de.daemons-point.com/gitea/, staticURLPrefix: /gitea
and it returns the concatenation of these...

@uli-heller Could you try this patch
diff --git a/modules/setting/setting.go b/modules/setting/setting.go
index be7ec16e1..1f05bd7b6 100644
--- a/modules/setting/setting.go
+++ b/modules/setting/setting.go
@@ -1070,12 +1070,7 @@ func MakeAbsoluteAssetURL(appURL string, staticURLPrefix string) string {
        }

        if err == nil && parsedPrefix.Hostname() == "" {
-               if staticURLPrefix == "" {
-                       return strings.TrimSuffix(appURL, "/")
-               }
-
-               // StaticURLPrefix is just a path
-               return strings.TrimSuffix(appURL, "/") + strings.TrimSuffix(staticURLPrefix, "/")
+               return strings.TrimSuffix(appURL, "/")
        }

        return strings.TrimSuffix(staticURLPrefix, "/")

@lunny Your patch looks good!

Checked out master
Applied your patch - https://github.com/uli-heller/gitea/tree/logo.png-2
Built
Run and tested: OK


Pin win32-taskscheduler to 1.0.2 and bump inspec-core/mixlib-shellout to latest

Pull in the latest deps, but pin win32-taskscheduler  to 1.0.2 as 1.0.9 broke tests and the scheduled task resource.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

Superseded by #7504


add support for linked images

Supports image references (filename instead of base64 encoded data)

Ok, I will update that.

We have a new version now (1.2) which includes this update.
It is also an interface change: removed option --maxlaserpower, changed option --cuttingpower (to be an int, instead of a fraction).
Also, bbox reporting (within the gcode files) has a different format (instead of ' to ', I use ':').


Why do almost everytime pokemon catch returns Catch Flee

I guess 90% time whenever I encounter any wild pokemon and try to catch it, I get response as Catch Flee.
pokeObject.CatchPokemon(currentPokemon, 1, 1.950, 0.850, 1, function(xsuc, xdat) {});
Is anyone else facing the same issue?

Can't even get Catch to work properly. Are you Encountering the Pokemon first?

same problem probably soft ban

Yep looks like a soft ban, tried another account and worked ok.

I don't think it is a soft ban issue. I was able to get a Pokémon on my device but not via the bot.  Got a data issue :-(

@filharvey my repo works for catching perfectly fine - I got 4k star dust in an hour

What is your code for encounter and capture. This has worked before but now is just not working.

Pull my repo and try it. ExamplePromises.js is the file you want

Will do thanks

If you keep getting "catch flee" try to play with the official client, try to catch 2 pokemons, if both escape after the first poke ball, you are softbanned

@d-pollard hi sir how can i put your repo into my bot system?


Error when Angular component defined in separate Bazel package from the NgModule

In discussion on https://github.com/alexeagle/angular-bazel-example/issues/87, I outlined an example project structure that might make sense for some Bazel Angular projects. But when I tried to implement it, I got a build error about Unexpected value 'ComponentA[...]' declared by the module 'FooModule[...]'. Please add a @Pipe/@Directive/@Component annotation. As you can see in the repro at https://github.com/alexeagle/angular-bazel-example/compare/master...pshields:example-project-layout , the components do have Component annotations. I think they must be getting stripped when the ts_library is built. Is this a bug? I would think the decorator should be preserved so that a component defined in a ts_library can be used in a separately-defined ng_module.

ts_library doesn't produce Angular metadata outputs, so we lose any information about the decorators. The only outputs are .js and .d.ts and these are both lossy with respect to the analysis needed by the angular compiler.
At google, we just mechanically change any ts_library that depends on Angular into an ng_module. That's easy for us to do, because Angular has to appear in the deps. In open-source, you can depend on anything in node_modules without listing it in deps but we could still have a check that fails compilation of a ts_library if it sees an import {} from '@angular/*'

Thanks Alex. There's a problem with turning the ts_library into an ng_binary; if we do that, we get e.g. Cannot determine the module for class ComponentA errors on the child ng_module targets (example repro), since the components aren't declared by an Angular module at that point. In that example, the //src/foo_module/component_a:component_a ng_module contains only the component declaration for ComponentA. FooModule, which declares ComponentA, is declared in the parent directory foo_module's ng_module. This mirrors the original issue @webdevelopland ran into in #87. So is that a bug? Or is it impossible to define a component in one ng_module target and declare it as part of an Angular module in a separate ng_module target? That would seem to make it impossible to define per-component Bazel packages / BUILD rules, unless you give each component a corresponding NgModule that declares it.

Briefly, it's the last thing: any component must be compiled with it's
declaring ngmodule because it's the compilation context. So any Bazel
package with components must have an NgModule.
On Mon, Feb 19, 2018, 4:07 PM Patrick Shields<EMAIL_ADDRESS>wrote:

Thanks Alex. There's a problem with turning the ts_library into an
ng_binary; if we do that, we get e.g. Cannot determine the module for
class ComponentA errors on the child ng_module targets (example repro
https://github.com/alexeagle/angular-bazel-example/compare/master...pshields:ngmodule-test),
since the components aren't declared by an Angular module at that point. In
that example, the //src/foo_module/component_a:component_a ng_module
contains only the component declaration for ComponentA. FooModule, which
declares ComponentA, is declared in the parent directory foo_module's
ng_module. This mirrors the original issue @webdevelopland
https://github.com/webdevelopland ran into in #87
https://github.com/alexeagle/angular-bazel-example/issues/87. So is
that a bug? Or is it impossible to define a component in one ng_module
target and declare it as part of an Angular module in a separate ng_module
target? That would seem to make it impossible to define per-component Bazel
packages / BUILD rules, unless you give each component a corresponding
NgModule that declares it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alexeagle/angular-bazel-example/issues/93#issuecomment-366831234,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC5I9FDNcl_i28zJ00kgX0kE9_U4aEFks5tWgylgaJpZM4SLHxf
.

We should do two things to close this:

give an error when a ts_library uses an Angular decorator, it should have been an ng_module
an ng_module rule without an @NgModule should error explaining that you can only compile one or more @NgModules, and need to re-organize your code so that every Bazel package has one

Thanks Alex. I agree with those two AIs to make it easier for developers to catch this class of problem and learn how to fix it.
Longer-term, is there any chance of, say, an ng_component rule that could allow for independent compilation of a component without knowing its module? Or would it be possible for ts_library to leave the decorators in place?
The developer experience of not being able to have per-component build packages seems suboptimal. Defining "leaf node" component packages, and hooking them up in a parent ng_module, is a pattern I'd often want to use---especially while there is a need for other per-component build rules such as sass_binary.

@pshields At the moment, the Module is the unit of compilation with Angular. The first party stuff that packages a bunch of components (Material) gathers small handfuls of closely related components into modules; this also seems to match the way components are most built and used in large apps, typically not one at a time but in small groups.
I can't speak for the future, whether some later re-factoring might make these ideas obsolete, but for the moment I don't think the design of Angular is aimed at the notion of having a bunch of free-floating components that you package up into modules at the point of use.

Currently the NgModule holds some of the context the compiler needs to resolve things like selectors in the component it compiles.
One of the goals with Ivy is that compilation of a component is local - this would mean NgModule becomes optional and the constraint we're discussing will go away. Targetted for Angular v7.


Mention Model Explainability

Mention the definition of Model Explainability here since feature importance with PFI is part of it.

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

ID: 1b1fb0dd-648b-26e9-7e4e-48824ab94160
Version Independent ID: 689b6488-dadc-fd39-c432-ebf095a0299a
Content: Explain model predictions using Permutation Feature Importance - ML.NET
Content Source: docs/machine-learning/how-to-guides/explain-machine-learning-model-permutation-feature-importance-ml-net.md
Product: dotnet-ml
GitHub Login: @luisquintanilla
Microsoft Alias: luquinta

AB#1599455