OVDB-62: Rename VDB SOPs

I still think that the suffix renaming is more trouble than it's worth - I don't think users really need to know from the label whether the SOP comes from the ASWF repository or not.
With OpenVDB->VDB, I'm fairly indifferent on the interlacing of the SOPs, though if both SE and ASWF SOPs are visible I personally prefer them to be entirely separate - it makes it much easier to see and select the desired tab item when typing something generic like "vdb". Also, can I just double check that someone has tested this does interlace the SOPs? My Houdini config is setup to show SOPs in different tab menu categories completely separately, so I'm wondering if this renaming would actually interlace them. Otherwise we'd also need to add them to the VDB menu.
We discussed implementing policies for hiding SE/ASWF nodes, so the interlacing point becomes less relevant anyway? This seems like something which could be implemented before this and may make this change redundant.
This being said... Instead of a blanket renaming, I'm wondering if there's a way we can leverage Houdini's node versioning system to allow users to switch between the native and ASWF SOPs. Something like prefix all aswf nodes with a ::aswf version. Ideally only one copy of each node should ever exist in the tab menu (which one gets prioritised should be decided at load) but then users could change the version of the node being loaded using the asset bar instead of the policy/ophide stuff.

Chiming in as I've just caught wind of this and I agree with @Idclip however I'm less indifferent about the interlaced entries as I think that would be confusing/frustrating and easy to misclick and I think should be avoided even as an interim solution.

@idclip @dnegmw - if you haven't seen it already, there's an open discussion from about two weeks ago between @jmlait and myself about different approaches we could take here for a bit more context (namespacing is briefly considered there):
https://lists.aswf.io/g/openvdb-dev/topic/proposal_unifying_vdb_and/29915127
Adding the (ASWF) suffix I don't particularly have strong opinions about, but it is perhaps still somewhat useful to be able to easily distinguish where this node came from just in terms of being able to report issues.
I have been testing the interlacing of nodes for the last few days and it's great, so much clearer and easier to use. I'll give you a very specific example - you have a mixture of native and open-source nodes deployed and you're looking for a node that does some kind of culling or pruning, but you can't exactly remember the name. You either tab and type some example phrases "cull", "prune", etc and hope you've got it close enough to find it or you just type "VDB" and scan through the list to find it visually. In the second scenario, rather than going through the list one-by-one until you find it, you probably still look for the names that you have in your head first and only resort to an exhaustive search if you don't find it. There's no doubt in my mind that having one consolidated, alphabetical list is better than two disjoint, alphabetical lists. For most users, the least likely piece of information they'll retain is whether the node is native or open-source (that's probably not the case for you Nick!). The interlacing and the scenario I've outlined is still very relevant when talking about hiding nodes through policy.
I also want to highlight that we're only deciding on a default naming scheme for ASWF nodes. For a company that is installing the open-source nodes for the very first time, what should happen? If you have already been installing these nodes for many years and your users have become used to how things are named and organised, this is more a discussion about whether to go through the potential disruption of changing the names or not. In this case, there's always the option to provide your own company policy, it's as simple as adding this to SOP_NodeVDB.cc:
class MyCompanyOpenVDBOpPolicy: public ASWFOpenVDBOpPolicy
{
public:
    std::string getLabelName(const houdini_utils::OpFactory& factory) override
    {
        return "Open" + factory.english();
    }
};

using OpenVDBOpPolicy = MyCompanyOpenVDBOpPolicy;


Fix form layout on export page

Looks good. Did you learn from my mistake and leave in .control-group for any particular javascript reason? Ref: #2188

I noticed that control-group was used elsewhere in the CSS and Javascript, so I decided to play it safe.

Thanks!


Extension causes high cpu load [auto report]

Issue Type: Performance
Extension Name: azure-pipelines
Extension Version: 1.183.0
OS Version: Windows_NT x64 10.0.18363
VSCode version: 1.52.1

ms-azure-devops.azure-pipelines-unresponsive.cpuprofile.txt
`
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

duplicate of #215

duplicate of #215

Yeah. There's been a number of improvements around this area, some released, some still in development. I'm going to close this as handled by #365 but until that lands you should also be able to see much faster activation time by setting azure-pipelines.configure to false.

Yeah. There's been a number of improvements around this area, some released, some still in development. I'm going to close this as handled by #365 but until that lands you should also be able to see much faster activation time by setting azure-pipelines.configure to false.


fix: New LKE clusters get stuck provisioning when HA price is undefined

Description 📝
This fixes an issue where creating an LKE Cluster in environments where REACT_APP_LKE_HIGH_AVAILABILITY_PRICE is undefined results in a cluster with nodes stuck in "provisioning" state, and the only way to get them un-stuck is to enable high availability, which is irreversible. The issue is fixed by passing false for control_plane.high_availability in cases where the environment variable is undefined.
I don't think this is strictly a Cloud Manager issue because the API does not respond with a 400, and the API docs state that control_plane.high_availability is treated as false by default. Regardless, explicitly passing false results in clusters that provision successfully, and leaving it absent seems to result in clusters that get stuck.
Major Changes 🔄

Pass false to control_plane.high_availability explicitly when the HA control plane prompt is not present

How to test 🧪
To Reproduce the Issue

Check out develop, remove the REACT_APP_LKE_HIGH_AVAILABILITY_PRICE environment variable from your .env file if necessary, and build Cloud Manager
Create an LKE cluster, observe that you're redirected to the cluster's details page
Wait ~20 minutes and confirm that the Cluster's nodes are still in "provisioning" state

To Verify These Changes

Check out this branch, remove the REACT_APP_LKE_HIGH_AVAILABILITY_PRICE environment variable from your .env file if necessary, and build Cloud Manager
Create an LKE cluster, observe that you're redirected to the cluster's details page
Confirm that the cluster finishes provisioning after a few minutes
Re-add the REACT_APP_LKE_HIGH_AVAILABILITY_PRICE environment variable, create an LKE cluster with HA enabled and an LKE cluster with HA disabled, and confirm that both clusters finish provisioning after a few minutes

I don't think we need to worry about fitting this into the 1.100 release since this issue does not impact cloud.linode.com.

It's still taking me <10min for the provisioning an HA cluster and its not done yet. It might be on my end but not too sure.


Add a new SDK OpenVR

Games using OpenVR:

VirtualCast - Windows
Operation Armstrong - Windows
Beat Saber - Windows
Hot Dogs, Horseshoes & Hand Grenades - Windows
Half-Life: Alyx - Windows, Linux
VAR: Exterminate - Windows
Tabletop Simulator - Windows, Linux, MacOS

I added a rule which detects OpenVR SDK for Windows & Linux & MacOS. I didn't name it Valve OpenVR because Valve itself names it OpenVR, on Steamworks wiki page as on OpenVR GH Wiki it's named OpenVR, let me know if I should name it Valve OpenVR instead.

fwiw, Steam specifies openvr support in a key: https://steamdb.info/search/?a=app_keynames&type=-1&keyname=379&operator=1&keyvalue=

It's still worth presenting on the tech list, as it's a technology. But alternatively, it would be detected by the key.


Fcs 149

[x] Support for cliPattern instead of cliDir

[x] Support for dependencies as dictionary

[x] Support for loading config folder and config.json files

:tada: This PR is included in version 2.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Useid 578/widget tracking

Calls are fired and you can check the events on Matomo Live and Matomo Events. Widget also tracks Button Pressed event and calls backend route /app-openend.

Implementing the service and the matomo events, I'v realized that we are not having the WidgetController Routes in Reactive Style. Should I rework these routes to be reactive?
I would vote for yes. (but I'd do this directly on main. PRs suck)
Please let me know @mpanne @code28
Also I am unsure about how much testing the tracking needs... Please share your thoughts about it!

Thanks for your feedback, peeps!


Geometry support

I often need to record screencasts with Atom, and need it in a specific position and size on screen.
Most X11 based application allow for a -geometry switch.
I realize Atom is Electron-based, and not X11. However, is it possible to support this switch?
Perhaps as follows:
atom --geometry 1280x720-37+50
where the value is [{WIDTH}][x{HEIGHT}][{+-}{XOFF}[{+-}{YOFF}]]

I don't think this is really necessary. Simply add a command like
atom.commands.add 'atom-workspace',
    'custom:prepare-for-screencast': ->
        atom.setSize(1280, 720)
        atom.setPosition(37, 50)

to your init.coffee. You can call Prepare for screencast from the Command palette.

This worked perfectly! Thanks.


Test/end 2 end test

Description
end to end testing for futures page
Related issue
https://github.com/Kwenta/kwenta/issues/234
Motivation and Context
How Has This Been Tested?

Screenshots (if appropriate):

@avclarke can you review this one and make sure it meets all expected test cases
we'll also need to write a CI workflow to automate this test in the future (new ticket cc @platschi)


Removed several smells across several files

This was school project work using Designite software to produce smell reports and and then squash them

Please review the Code Conventions. Brace placement is always on the next line.


Errors when attempting to add Rustler to new project (OTP20, Elixir 1.6.1)

Yesterday I attempted to add Rustler to an existing Phoenix project. After following the instructions for version 0.16.0, I obtained the following error, however.
Today I tried to add Rustler to a completely fresh Elixir project, to see if I had misconfigured something, or if there was a conflict happening with other things I was doing.
But on this self-contained Elixir project,whose source can be found here on GitHub for reference, exactly the same error occured:
(This is what you see after running iex -S mix:)
Erlang/OTP 20 [erts-9.1] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false]

==> rustler
Compiling 6 files (.ex)
Generated rustler app
==> elixir_rust_test
Compiling NIF crate :niftest (native/niftest)...
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
Compiling 2 files (.ex)

21:54:55.649 [error] Process #PID<0.188.0> raised an exception
** (Protocol.UndefinedError) protocol String.Chars not implemented for {:error, :bad_name}
    (elixir) lib/string/chars.ex:3: String.Chars.impl_for!/1
    (elixir) lib/string/chars.ex:22: String.Chars.to_string/1
    lib/rustler.ex:75: Rustler.compile_config/2
    lib/nif_test.ex:2: NifTest.__init__/0
    (kernel) code_server.erl:1333: anonymous fn/1 in :code_server.handle_on_load/5

21:54:55.655 [warn]  The on_load function for module Elixir.NifTest returned:
{%Protocol.UndefinedError{description: "", protocol: String.Chars, value: {:error, :bad_name}}, [{String.Chars, :impl_for!, 1, [file: 'lib/string/chars.ex', line: 3]}, {String.Chars, :to_string, 1, [file: 'lib/string/chars.ex', line: 22]}, {Rustler, :compile_config, 2, [file: 'lib/rustler.ex', ...]}, {NifTest, :__init__, 0, [...]}, {:code_server, :"-handle_on_load/5-fun-0-", 1, ...}]}

Generated elixir_rust_test app
Interactive Elixir (1.6.1) - press Ctrl+C to exit (type h() ENTER for help)

Steps to get here:

I started the new elixir project mix new elixir_rust_test
I added  {:rustler, "~> 0.16.0"} to the mix.exs dependencies.
I ran mix deps.get.
I ran mix rustler.new with as module name NifTest.
I added a compiler line to the configuration settings of mix.exs (line 10): `compilers: [:rustler] ++ Mix.compilers,
I added the rustler_crates private function to mix.exs and refer to it from the rustler_crates: setting in the configuration settings function, following the syntax mentioned here, which is the page that the rustler.new task refers to once done.
`
I created a new module lib/nif_test.ex and added the example code that the rustler.new task returned in there:

defmodule NifTest do
  use Rustler, otp_app: [:elixir_rust_test], crate: "niftest"

  # When your NIF is loaded, it will override this function.
  def add(_a, _b), do: :erlang.nif_error(:nif_not_loaded)
end

I ran iex -S mix, which returns in above erroreous output.

What is going on here? Am I following the setting-up instructions improperly, or is something broken inside Rustler?

Turns out the mistake was that I wrote use Rustler, otp_app: [:elixir_rust_test], crate: "niftest" rather than use Rustler, otp_app: :elixir_rust_test, crate: "niftest".
The reason for this mistake, is that Rustler's example code snippet (shown when the rustler.new task is run) returns:
defmodule NifTest do
    use Rustler, otp_app: [otp app], crate: "niftest"

    # When your NIF is loaded, it will override this function.
    def add(_a, _b), do: :erlang.nif_error(:nif_not_loaded)
end

In hindsight, [otp app] was meant to be a placeholder, but I interpreted it to be a list of names. I think that just writing :your_project_name or something there might be more clear :-).
In any case, I would have never guessed that this was the problem based on the weird errors that were raised, so there probably is something that can be improved in that regard as well. Let me know if you agree; I might be able to contribute with a PR.
Thanks! <3

Good spot! If you had this problem, another person may as well.
On Sun, Feb 11, 2018, 3:58 AM Qqwy<EMAIL_ADDRESS>wrote:

Turns out the mistake was that I wrote use Rustler, otp_app:
[:elixir_rust_test], crate: "niftest" rather than use Rustler, otp_app:
:elixir_rust_test, crate: "niftest".
The reason for this mistake, is that Rustler's example code snippet (shown
when the rustler.new task is run) returns:
defmodule NifTest do
use Rustler, otp_app: [otp app], crate: "niftest"
# When your NIF is loaded, it will override this function.
def add(_a, _b), do: :erlang.nif_error(:nif_not_loaded)end
In hindsight, [otp app] was meant to be a placeholder, but I interpreted
it to be a list of names. I think that just writing :your_project_name or
something there might be more clear :-).
In any case, I would have never guessed that this was the problem based on
the weird errors that were raised, so there probably is something that can
be improved in that regard as well. Let me know if you agree; I might be
able to contribute with a PR.
Thanks! <3
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hansihe/rustler/issues/130#issuecomment-364738821,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACyjU73bHgfZGVELtlHgqj5PqMyYMuHmks5tTrnJgaJpZM4SBE-E
.

I did actually have this same problem and it also took me a little time to figure it out.

@Qqwy thanks for pointing out the confusion...we'll make sure to fix that up. :+1:


Mail innovations

CI failed with a missing constant error:
/home/ubuntu/jenkins/workspace/active_shipping-pr/lib/active_shipping/shipping/response.rb:5:in `<module:Shipping>': uninitialized constant ActiveMerchant::ActiveMerchantError (NameError)

jenkins, retest this please

Not sure why but this doesn't pass on CI but does run locally. Pretty sure that's the current state of our active shipping fork and will be until we get the merge upstream stuff done.

@jedprentice I don't think it's worth fussing with CI until we get the merge upstream in. Can you look this over and if it looks okay we'll merge.

@psujohn Looks good to me. Bummer about CI.


Shell integration: Ensure it works on reconnected terminals

As part of this we should review that the shell integration related code is minimal on the pty host

/duplicate https://github.com/microsoft/vscode/issues/140246


Migrating IDIR usernames after BCeID/BCSC integration

After BCeID/BCSC integration, IDIR users will be recognized as new users and no longer have access to their submitted submissions and drafts.
ACs:

[x] Migrate all the IDIR users' submissions and drafts on the TOOL to the new usernames after BCeID/BCSC integration.
[x] Migrate all the IDIR users'  Camunda submissions to the new usernames after BCeID/BCSC integration.
[x] Write and store the migration script in the repo.

Migration progress in different environments (check when is done):

[x] DEV
[x] TEST
[ ] PROD

Will do this after the BCeID and BCSC integration.

Iman will need to do this ticket right after the first deployment related to BCeID/BSC

After PR Imam will run migration for Test and then send to teamfor testing

@Stella-Archer
This is ready to be tested on the TEST environment. For testing simply log in to TEST and verify you have all your previous drafts, applications, and tasks. All the previous submissions prior to the BCSC+BCeID integration for the IDIR user should be restored.

Only thing left to do is deploy to prod

woohoo everything is there good to go!

Great!
Moving it to Deploy to PROD

Deployed to PROD.


[Question] How to get img alt?

At first, to get img alt text, I just get 3rd argument of Tag::Image like below:
#[allow(dead_code)]
fn example2(markdown_input: &str) -> Vec<String> {
    // Set up options and parser. Strikethroughs are not part of the CommonMark standard
    // and we therefore must enable it explicitly.
    let mut opts = Options::empty();
    opts.insert(Options::ENABLE_TABLES);
    opts.insert(Options::ENABLE_FOOTNOTES);
    opts.insert(Options::ENABLE_STRIKETHROUGH);
    opts.insert(Options::ENABLE_TASKLISTS);
    let parser = Parser::new_ext(markdown_input, opts);
    let mut re: Vec<String> = Vec::new();
    for event in parser.clone() {
        match event {
            Event::End(Tag::Image(link_type, url, alt)) => {
                println!("{:?}, {:?}, {:?}", link_type, url, alt);
                re.push(alt.into_string());
            }
            _ => ()
        }
    }
    re
}
#[cfg(test)]
mod tests {

    #[test]
    fn example2() {
        let markdown_input = r"# arikitari

![1](1.png)

![cpp](D3T3cG6U0AAd0Zn.jpg)

![atgtheiwa1](D5iuwp0W4AEm1bi.jpg)

![atgtheiwa2](D5jwkn7XsAABJvV.jpg)

![IR](IR.jpg)
```markdown
![2][2.png]
```
";
        let re = super::example2(markdown_input);
        print!("{:?}", re);
        let test = re.iter().eq(&["1", "cpp", "atgtheiwa1", "atgtheiwa2", "IR"]) ;
        assert!(test);
    }
}

However, that returns empty string.
test tests::example2 ... FAILED

failures:

---- tests::example2 stdout ----
Inline, Borrowed("1.png"), Borrowed("")
Inline, Borrowed("D3T3cG6U0AAd0Zn.jpg"), Borrowed("")
Inline, Borrowed("D5iuwp0W4AEm1bi.jpg"), Borrowed("")
Inline, Borrowed("D5jwkn7XsAABJvV.jpg"), Borrowed("")
Inline, Borrowed("IR.jpg"), Borrowed("")
["", "", "", "", ""]thread 'tests::example2' panicked at 'assertion failed: test', src\lib.rs:179:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

failures:
    tests::example2

How should I do to get that?
I suspect around scan_inline_link...
https://github.com/raphlinus/pulldown-cmark/blob/d46259206d2d1129c8ac85c56a0de22b0aef6234/src/scanners.rs#L915-L945

So this is a bit weird, but images are tags in pulldown_cmark, which means that they contain other events. This is understably confusing, as this isn't true for html images.
The alt text you are looking for is contained in the image tag. For example, the snippet ![*a*](b "c") will produce the following events:
0: Start(Paragraph)
0: Start(Image(Inline, Borrowed("b"), Inlined(InlineStr { inner: [99, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1] })))
2: Start(Emphasis)
3: Text(Borrowed("a"))
4: End(Emphasis)
5: End(Image(Inline, Borrowed("b"), Inlined(InlineStr { inner: [99, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1] })))
13: End(Paragraph)

The value you were expecting to be the alt is actually the image's title!
Hope this clears things up. We may want to reconsider this design at some point at make images atoms to prevent such confusion.

We may want to reconsider this design at some point and make images atoms to prevent such confusion.

The problem is the contents of the Markdown image can contain nested inline Markdown elements. It's true that the CommonMark specs recommends to ignore them them for HTML output but other kinds of renderers might need/want to use them.

Thanks for the excellent considerations as always @mity. I suppose the current design is actually sensible. Closing this issue as the main question should be answered. If not, feel free to reopen!

Thank you for your answers. As a result, based on CommonMark0.29 Spec example 572, to get img alt, I need to concat all Text event strings, isn't it?

Hope this clears things up. We may want to reconsider this design at some point and make images atoms to prevent such confusion.

I want more documentation around below:

https://docs.rs/pulldown-cmark/0.5.3/pulldown_cmark/enum.Tag.html#variant.Image

the third is a title

I want example to tell users what is titile

https://docs.rs/pulldown-cmark/0.5.3/pulldown_cmark/enum.Event.html#variant.Start
Also I want example like https://github.com/raphlinus/pulldown-cmark/issues/394#issuecomment-527197423 to tell the deferences between Start and End event.


[Android] Add test cases for loadAppFromManifest().

This patch is to add test cases for loadAppFromManifest().
It contains several URL schemes like 'http:', 'https:', 'file:'
and others.

what is up with this?


capture and apply

Firstly, great work on this, has proved extremely useful for my project
Can I ask if you have any plans to add the DISM functionality offered by Apply-Image and Capture-Image, so I can then use this API for my imaging program as well
Thanks

You'll want to use my other library for applying and capturing images, Wimgapi.  DISM only manages existing images.
Here's an example on applying an image:
https://github.com/josemesona/ManagedWimgApi/wiki/Apply-an-Image

Okay thanks, hadn’t seen that one – will take a further look
But DISM command line certainly does more than just manage existing images? As I use it daily to roll out images to client machines e.g.
dism /Apply-Image /ImageFile:E:\Imaging10\1-Image\Win10081117r6.wim /Index:1 /ApplyDir:W:\
Darren Rose
PC Assist @ Home
01508 471459
darren.rose<EMAIL_ADDRESS>www.pcassistonline.co.ukhttp://www.pcassistonline.co.uk
From: josemesona<EMAIL_ADDRESS>Sent: 24 December 2017 00:11
To: josemesona/ManagedDism<EMAIL_ADDRESS>Cc: Darren Rose<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [josemesona/ManagedDism] capture and apply (#35)
You'll want to use my other library for applying and capturing images, Wimgapihttps://github.com/josemesona/ManagedWimgApi. DISM only manages existing images.
Here's an example on applying an image:
https://github.com/josemesona/ManagedWimgApi/wiki/Apply-an-Image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/josemesona/ManagedDism/issues/35#issuecomment-353755719, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKXn30I8FwNWjkCaeF0NsNFa7SZIqrwhks5tDZaHgaJpZM4RLx2i.

Yeah I know its confusing.  Dism.exe uses WIMGAPI to create and apply images.  This is because WIMGAPI just creates images in a generic way that can contain anything.  To modify images specific to Windows (like add drivers or features) you use DISMAPI.  Dism.exe and the Dism PowerShell CmdLets both use WIMGAPI under the covers depending on what operation you're performing.
So I made both libraries because I needed both.

Excellent – thank you for the full explanation – I really appreciate it
Darren Rose
PC Assist @ Home
01508 471459
darren.rose<EMAIL_ADDRESS>www.pcassistonline.co.ukhttp://www.pcassistonline.co.uk
From: josemesona<EMAIL_ADDRESS>Sent: 24 December 2017 00:26
To: josemesona/ManagedDism<EMAIL_ADDRESS>Cc: Darren Rose<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [josemesona/ManagedDism] capture and apply (#35)
Yeah I know its confusing. Dism.exe uses WIMGAPI to create and apply images. This is because WIMGAPI just creates images in a generic way that can contain anything. To modify images specific to Windows (like add drivers or features) you use DISMAPI. Dism.exe and the Dism PowerShell CmdLets both use WIMGAPI under the covers depending on what operation you're performing.
So I made both libraries because I needed both.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/josemesona/ManagedDism/issues/35#issuecomment-353756654, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKXn39BHV_js6ggxoNI8VJskQkYx8uKFks5tDZn-gaJpZM4RLx2i.


Code coverage change is not accurate on PRs

Codecov shows an improvement in coverage despite no code changes.
Originally noted by @alunturner in https://github.com/matrix-org/matrix-rich-text-editor/issues/701#issuecomment-1572024521

Codecov docs mention that this could cause the problem

Reasons for unexpected changes
Missing coverage reports or failed builds.

So I think this happens because we're not running all the tests on PRs (Android and iOS are only run when the label is applied) but we are running all of them on the main branch, hence there is nearly always a mismatch and the coverage is reported to have changed.
@jmartinesp @langleyd do you have any background on the current system of adding Android/iOS labels? Did we hit some usage limits in the past? I'm wondering if we could try running the tests on all PRs.

I'm not sure, to be honest. It might have been to make Rust/JS only PRs faster to merge, since the Android job takes ~15min per RAM and for iOS it's something between 20-25min. Maybe we could enable merge queues for this so when merging every job will be run, and thus have proper coverage reports?

Ooh, I just found out about 'carryforward flags' in Codecov which might do what we need!

Carryforward Flags are designed for projects that do not upload total coverage for every commit (e.g., monorepos with multiple applications/languages, iterative/partial/delta testing setups, etc).

If I understood correctly, we could carry forward the base branch's Android and iOS coverage so that PRs do not need to report them.

Maybe we could enable merge queues for this so when merging every job will be run, and thus have proper coverage reports?

Not to say we should not also use merge queues to ensure all the tests run before merging. That could still be nice to have as a safety net. Rust changes, for example, should run all the tests but it's easy to forget to add the labels.


The overwrite warning TOO SUBTLE

Does this issue occur when all extensions are disabled?: Yes/No
Yes

VS Code Version: 1.67.1
OS Version: macOS 12.0.1

Steps to Reproduce:

open the file try.txt, and add a line new line HELLO
either use any automatic method, or use emacs, vim, and edit that file try.txt by adding a line HI HI and save it.
Now go back to VSC and save that file.  A VERY SUBTLE: it will overwrite the file. Do you want to overwrite or not? message appear.  9 times out of 10, I cannot catch that box, because it is way too subtle. If may even appear to be "We have a survey. Do you want to participate?"  If it is a simple file like this, the warning may be more apparent, but if the file is like a complicated, 2000 lines long JSON file or XML file, the box appeared a lot less obvious.  Many times, I just thought it is saved and went away, only to find out hours later that it wasn't saved.

How to fix:  There are some warnings that are way more important than a subtle hint.  Make it prominent so the user cannot miss.
The user asked to save and it did not save and it belongs to the warning that pops up right in the center of the window.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Yeah agreed, maybe it should be modal if the save action is explicit.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Remove longview setup for servo-master Linode exodus

Longview is Linode's proprietary monitoring service.
We are moving the servo-master machine from Linode to EC2, so
we can and will no longer use Longview, so this commit removes it.
Refs #281

This change is

@bors-servo r+

:pushpin: Commit b979215 has been approved by edunham

:hourglass: Testing commit b979215 with merge c47b288...

:sunny: Test successful - travis


tests(ticdc): support for canal-json test and add basic case

What problem does this PR solve?

Issue Number: close https://github.com/pingcap/tiflow/issues/4189
What is changed and how it works?

support for canal-json test
add basic case

Check List
Tests

Integration test

Code changes
None
Side effects
None
Related changes
None
Release note
None

Codecov Report

Merging #4190 (8813172) into master (08da001) will increase coverage by 0.1384%.
The diff coverage is 66.1840%.

Flag
Coverage Δ

cdc
58.8273% <67.8571%> (+0.1825%)
:arrow_up:

dm
52.3067% <60.1895%> (+0.0521%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4190        +/-   ##
================================================
+ Coverage   55.1722%   55.3106%   +0.1384%
================================================
  Files           485        489         +4
  Lines         59829      60529       +700
================================================
+ Hits          33009      33479       +470
- Misses        23484      23683       +199
- Partials       3336       3367        +31

/run-copy

/run-copy

/run-copy

/run-copy

/run-kafka-integration-test

/run-kafka-integration-test

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/run-copy

/hold
Waiting for https://github.com/PingCAP-QE/ci/pull/550 landed.

/run-copy

Test result: https://ci2.pingcap.net/blue/organizations/jenkins/cdc_ghpr_kafka_integration_test_copy/detail/cdc_ghpr_kafka_integration_test_copy/11/pipeline/134/

/unhold
https://github.com/PingCAP-QE/ci/pull/550 landed.

/merge

/run-dm-integration-test
/run-verify


2023.10.0b3 [Bug]

The problem
Stop Working Integration
Your device model

Firmware type
Stock
Firmware version

Integration version with the issue

Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
2023.10.0b3
Is there anything useful in the logs?
No response
Diagnostics information
No response
Additional information
No response

Hello. Can you please provide a bit more info on the issue?
I have tested the mentioned version of HA, but did not notice any new issue with the current version of the integration


Catalog App Wordpress does not work on Rancher 2.0.8

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

started the rancher server v2.0.8
added a cluster (I tested for both DO and custom cluster)
launched the catalog app  Wordpress with all default settings

Result:
Wordpress runs up, but the container Containers never run up.
error message: Containers with unready status: [mariadb-test]

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.0.8
Installation option (single install/HA): Single Install

The wordpress-mariadb-test is only a test container and it will not get deployed if the user is using rancher v2.1 or above, this is because we only bring the tiller back since Rancher v2.1.
So user can either delete this test container or using the old version of WordPress.
Relevant feature request of catalog version filtering: https://github.com/rancher/rancher/issues/15014


We have a way to notify all users of significant news

(This is about being able to notify users of changes in the service on a routine basis, with users able to opt in and out, default being in)

This would include some lightweight user research (very short interviews) to learn how people want to get notified about various kinds of cloud.gov news (breaking changes, feature updates / new features, etc.), ideally including people at 18F, people at EPA, and a few prospective users from other agencies. (Do they read their email? Do they want an RSS feed? Would they reeeally just want a little notice in the CF CLI when they log in? Something else?)

This would also likely include:

Fix the RSS feed for the updates posts (https://github.com/18F/cg-landing/issues/88)
Make a mailing list happen

Newsletter:
Schedule: Quarterly - roughly the week following PI Inspect and Adapt
Length: one pager-ish
Audience: goes out to our mailing list via mailchimp
Author: Skyporter (James Hupp and others)
Technical updates (“Platform release notes”):
Roughly bi-weekly technical updates to cloud.gov/updates. These will focus on updates related to the functionality of the product and other items relevant to users. It will not focus on our team activity.
Schedule: bi-weekly / as appropriate
Length: bullets
Audience: technical audience
Author: Bernd
Blog posts (major announcements / things with opinions and editorializing)
Schedule: occasional
Length: long-ish
Audience: 18F blog (with summary and link at /updates)
Author: Anyone, with review/oversight via the 18F blog process
See rubric by @brittag for more details

Are there any other types of important notifications that aren't covered above?
@mogul @diego?

This seems like it'll cover stuff for now.

Nikki and Bret groomed the initial post and title of this issue to focus specifically on the case of technical updates. We will write similar issues in future for quarterly updates, outages, and pointers to blog posts.

PI8 75% assessment:
SHOULD: Currently we are releasing bi-weekly technical updates but we don't give users notice of them.  Setting the notifications up as per the checklist above seems in line with PI8 if we can fit it in. I'm assuming it should be a light lift but need to check with @berndverst.

Let's make separate stories for newsletter, blog posts, and technical updates.

We should investigate what kind of things MailChimp can do in response to feed updates to get a sense whether that automation is viable.

Do we need to worry about this feed containing users from east while that's still active?

I'd suggest we should keep feeding data to Mailchimp from East while it's still active - for example, we may send notices about migration for East people, so all East people should get those (for example, if any new people have been added by teammates on a project that hasn't migrated yet).

These Skyporter AC presuppose access to Mailchimp, which we might no longer be able to use? If we can't use mailchimp, another AC will be choosing a new tool/method to interact with customers for these purposes. I'll add that AC above.

Oh hm, I'd suggest rewriting this story to be not-tool-specific - for example, replacing "Mailchimp" with "our email tool" and reframing the description to include something like "a prerequisite for working on this story is having access to an email tool that we can use on an ongoing basis", since we may want to work on that choice in a different story.

Definitely, we don't want this story to blow up since finding a replacement tool is an endeavor in and of itself!

I moved this down the Atlas backlog a bit until we know more about whether we're writing this for MailChimp or for GovDelivery or some other solution.


请问训练部分会开源吗

请问该端到端语音模型的训练技术会公开吗，感谢团队的工作！

I tried to run the training after preparing the appropriate json data and yaml configuration file, but my attempt failed, can I ask for the missing configuration yaml file?

I tried to run the training after preparing the appropriate json data and yaml configuration file, but my attempt failed, can I ask for the missing configuration yaml file?

There is no published configuration yaml file yet.

请问该端到端语音模型的训练技术会公开吗，感谢团队的工作！

https://arxiv.org/abs/2412.02612

请问该端到端语音模型的训练技术会公开吗，感谢团队的工作！

https://arxiv.org/abs/2412.02612

您好，请问微调的代码后续会更新吗


Crash in SetUserData() if Id fields are nil anywhere in the Connectivity Template Tree

https://github.com/Juniper/apstra-go-sdk/blob/2c259185f0cac13e61824e0a22fa4eb62808a15d/apstra/two_stage_l3_clos_connectivity_template.go#L225

Consider detecting this problem in ConnectivityTemplate.SetUserData(). Doing so will require SetUserData() to return an error.


feat(ci): use content hash in build system

Benefits:

merges and squashes in your branch don't cause rebuilds
O(1) tag lookup, no need for tag renaming

Should at least reduce the number of builds by half (stuff that passed will revalidate quickly on master etc)

Somewhat tackling https://github.com/AztecProtocol/aztec-packages/issues/1957 but restricting to *.ts and *.cpp

Somewhat tackling https://github.com/AztecProtocol/aztec-packages/issues/1957 but restricting to *.ts and *.cpp

Thanks for updating that. I should've done it that way in the first place


RTSP Frame Grab of H264 Example

I've been unsuccessful in capturing individual rawframes to images when the stream is H264, like the example that uses MJPEG. I know the FFMpeg library is capable of doing it because I've been able to use the executable to pipe the results to individual files.
In examining the SimpleRTSPClient, I can see how the client is providing the rawframe into the event handler.
From there - I see in the example SimpleRtspPlayer, the RealTimeVideoSource.cs class handles the raw frame, the leans on ImageUtils to construct a buffer.
This is where I get confused. In the MJpeg Snapshot maker example, it simply grabs the FrameSegment.
Handling of other codes in the snapshot maker example would be helpful to understand how to process streams.
I've tried taking the raw stream and saving it, but the resulting files are not image files.
I would like to suggest an example snapshot maker that supports the other codecs.
If I can make mine work, I'll contribute it as an example.

Hello,
May be I dont understand the source of your problem, but you cant save h264 stream as individual decodable frames. You must decode all frames and then encode them for example in jpeg format (transcoding)

Take a look at SimpleRtspPlayer, here you could see how to decode H264 frames to bitmaps. You could use standard jpeg encoder in .net to get jpeg from bitmap.

Thank you for the tips- this is what I'm trying to learn more about. I do apologize for my naive questions, but I'm learning about this - Thank you for creating project, too, by the way. I'm learning a lot.
In the SimpleRtsPlayer - The RealtimeVideoSource.cs class seems to do the lifting of frames, am I correct in that?  It looks like it creates an FFmpegVideoDecoder for a frame (held in the Decoders map dictionary), and when a frame arrives, it then gets the parameters of the frame (width and size) by calling the TryDecode.
Then, it looks to setup a parameters to match the resolution of the stream, creates a memory buffer that will match a "full frame" (I am understanding this correctly?), then finally, it goes back to the decoder to get a decoded frame.
At this point - is the decodedFrame a complete frame that is then used on the GUI? In other words, is that a bitmap at that point that could then be saved in BMP format or converted to an image?
Is your strategy here to create the FFmpeg decoder object for the stream, and then have it process the data received from the RTSP source, and then keep the decoder object alive so it can then assemble the frames into an image?
This is super fun to learn about, so thank you again.

I sent you a small donation for your efforts and kind support.

Thank you for the tips- this is what I'm trying to learn more about. I do apologize for my naive questions, but I'm learning about this - Thank you for creating project, too, by the way. I'm learning a lot.

It's ok, you are welcome.

In the SimpleRtsPlayer - The RealtimeVideoSource.cs class seems to do the lifting of frames, am I correct in that? It looks like it creates an FFmpegVideoDecoder for a frame (held in the Decoders map dictionary), and when a frame arrives, it then gets the parameters of the frame (width and size) by calling the TryDecode.

Yeah, that's it!

Then, it looks to setup a parameters to match the resolution of the stream, creates a memory buffer that will match a "full frame" (I am understanding this correctly?), then finally, it goes back to the decoder to get a decoded frame.

The main idea here is that we have display area (window) of a certain size where we want to draw video stream. In general frame size is not equal to display area size, that's why we must use scaling when decoding process is finished. For you it means that you could get for example full hd h264 video from RTSP server and then rescale it to 720p or something else.

At this point - is the decodedFrame a complete frame that is then used on the GUI? In other words, is that a bitmap at that point that could then be saved in BMP format or converted to an image?

Yes, decoded frame is equal to complete bitmap and you could easily create .net bitmap. See here: https://stackoverflow.com/questions/6782489/create-bitmap-from-a-byte-array-of-pixel-data

Is your strategy here to create the FFmpeg decoder object for the stream, and then have it process the data received from the RTSP source, and then keep the decoder object alive so it can then assemble the frames into an image?

Yes you are right. We should keep decoder alive for several reasons: 1) it has state which is taken into account in the decoding process of H.264 2) performance

This is super fun to learn about, so thank you again.

Great, thank you too.

I sent you a small donation for your efforts and kind support.

Thank you very much for your support!

At the weekend I can help you to get bitmaps from decoded frames effectively

Hey, thank you! I'll try and create a project that mimics the MjpegSnapshotsMaker based on the project - It might prove useful to someone else.
I'll update here on my progress.

I've created a project - I am still trying to get it to work - but thoughts on this so far?
I've added you as a collaborator.
My thinking was to create a class that this handed the frame off to, that would then convert to an image and save it asynchronously, allowing the processing not to block the next incoming frame.
This class would work with a dictionary of transcoders to output the file.
Thoughts?

BTW - I'm trying to make this work in Core - I think that'd be cool.

@inzi
Tomorrow I will help you to make it

Thanks! I think I've made some progress

I'm learning so much about c# from this project - I just wanted to say thanks again.  This is teaching me a lot about threading, overloads, and event handling.

I don't think this works with core - I'm going to try another project. I am working towards converting the ReatTime video class that will simply save the file.
Before I do that, I'm going to try and modify the simple player to save each frame - so understand where to do that.

I don't think this works with core - I'm going to try another project. I am working towards converting the ReatTime video class that will simply save the file.

No, it works on net core. But you should understand that it depends on ffmpeg libraries which are unmanaged and should be compiled appropriately for every platform

Before I do that, I'm going to try and modify the simple player to save each frame - so understand where to do that.

I need push access to your repository, I will give you an out of the box example.

Check here:
https://github.com/inzi/rtspcapture/commit/bdfaea3eff8cd286082814e9f1e820a93e98aa41

I was able to do it yesterday! The github crash didn’t let me post. I’ll post the other project so you can look at it.
I’ll investigate building FFMPEG into unmanaged DLLs to make it work with core.

So - maybe you would know  - I tried using the x86 dlls in your project with core but it doesn't like them.
I tried disabling managed code check. Like this:
    [DllImport(LibraryName, EntryPoint = "create_video_decoder", CallingConvention = CallingConvention.Cdecl), SuppressUnmanagedCodeSecurity]

but still doesn't work.
It throws:
RtspClientSharp.Rtsp.RtspClientException: Receive error ---> System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
I'm trying to run the core app under Windows 10 in Visual Studio.
Any ideas?
I'm going to try the tool media-autobuild_suite-master to build FFMPEG and use the DLLs, but I am not sure what I'm doing! haha. :)

I'd make this branch yesterday ("working") - https://github.com/inzi/rtspcapture/tree/Working
It's similar to your code - maybe it looks better for someone like me learning the process?
That branch is greatly cleaned up. If you think it's worthy anything for someone else to look at, I'll put it into it's own repo .

Looks good. I will give link to your repo if somebody do something similar.

You need to compile libffmpeghelper under x64 platform. You don't need to compile FFmpeg by yourself, just get it here: https://ffmpeg.zeranoe.com/builds/ (Dev)

Also I want to add that you could download x86 net core runtime from official site and start your program in console. Make sure that you call x86 version of dotnet executable.

I will merge Working into master so the code is cleaner

Can libffmpeghelper be compiled for linux-arm so it can be used on a linux machine?

Can libffmpeghelper be compiled for linux-arm so it can be used on a linux machine?

Sure. But you should have powerful enough ARM CPU to decode H264 stream. Perhaps you should find SDK for your processor to do hardware decoding.

Hello, any news ?

HI Inzi and BogdanovKirill,
Hi Team,
I was following your conversation and it seems you have done a great piece of work for frame capturing from RTSP streams. I see that you created the project in the link below for this purpose.
https://github.com/inzi/rtspcapture
Within this, I see that the code for RTSP frame capture is different in master and Working branches. Can you confirm if the final piece of code for frame capturing is the one in working branch:
https://github.com/inzi/rtspcapture/blob/Working/RTSPSnapshotMaker/Program.cs
Regards,
Nouman

I definitely learn a lot from your discussion. I am not sure my question will be of your interest. How do we extract meta data information from RTSP frame?


Remove unused codes and temp files, update docs

Remove wordcutpy from pythainlp.tokentize
Remove unused imports in requirements.txt (conllu)
Remove docs/_build/ and .gitignore them (temp files from doc generator)
Update docs/api docs

Coverage increased (+4.5%) to 65.296% when pulling eb2f7e14c316816b4fac8f0435e9f05ef4f7a90b on bact:dev into 10583534f94722c4557924bc171ec03b990773e3 on PyThaiNLP:dev.

Coverage increased (+4.5%) to 65.296% when pulling eb2f7e14c316816b4fac8f0435e9f05ef4f7a90b on bact:dev into 10583534f94722c4557924bc171ec03b990773e3 on PyThaiNLP:dev.


'My portfolio' card has no file attached

I think the card named 'My portfolio' should be removed.

@Mandeep-009 ,
Thanks for finding the issue.
If you want to add the files for this project, then you can create a PR
You have to add the files for a portfolio, not delete the card.
Someone added the files but it got deleted.
I am assignning this issue to you.

Pls assign me this issue

or can I add another portfolio page there?

or can I add another portfolio page there?

@Sha1kh4 ,
This issue has closed,
You can create a new PR related to any frontend Projects 👍🏽


Export default for ES6 build

Currently only this works:
import * as pc from "./playcanvas.mjs";

But usually people expect this to work:
import pc from "./playcanvas.mjs";

This is adding all export statements again, but as export default:

So the file size grows, but a HTTP server with gzip is compressing/zipping that all away (because it is equal to the previous string)
I confirm I have signed the Contributor License Agreement.

I'm not sure I see the problem here. The module build is new, so the examples and docs haven't been updated yet to talk about it. But every example and doc will have:
import * as pc from "./playcanvas.mjs";

(...or whatever we choose to call the module which still hasn't really been decided). If this was a trivial change (e.g. a flag in Rollup, say, and it didn't really add much to the module file), I'd be more into the idea of doing this. But it just looks weird from a code point of view and sure, gzip will minimize the bloat, but it just looks wasteful still. Sorry not to sound more positive. For now, I'd rather focus on getting the module properly named and exposed in the repo, properly documented and integrated into the examples. Is that OK? I don't want to sound ungrateful because I get what you're trying to do here. Happy to revisit this down the road.

Closing for now - but let's remember to pick this back up in a few weeks.

Closing for now - but let's remember to pick this back up in a few weeks.


Update Textbox.json

I found this the easiest way to set a default font, size and color for textbox text. Other people looking for this functionality have linked to your file. This would answer their questions.

Thanks for contributing!


Sync master/root README.md and provide a script to do this

What this PR does / why we need it:
The README for the master version of the docs and in the root
of the repo (used by Github) should always be in sync but
require minor changes due to different relative locations of
resources and links.
Also added this script as part of our CI to ensure that the two
files don't drift.
Which issue(s) this PR fixes
Fixes #772
Special notes for your reviewer:
Also found that there was drift; the master docs had a link to the page about wait functionality, but the root readme did not. The link wasn't actually used/needed so I removed it.
Release note:
NONE

Codecov Report

Merging #831 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #831   +/-   ##
=======================================
  Coverage   44.55%   44.55%
=======================================
  Files          76       76
  Lines        4624     4624
=======================================
  Hits         2060     2060
  Misses       2431     2431
  Partials      133      133

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 838ea5a...61bdb8d. Read the comment docs.


Add support for Wolfssl550

More work is required to support wolfSSL 5.5.0.
This is because the used hooks work differently in 5.4.0 and 5.5.0.

Closing for now, issue is open


Improve parsing of Hessian units in vasprun.xml

Based on the discussion in #263, I have created a pull request that should improve the parsing of the vasprun.xml file for newer versions of VASP. Instead of using the version number, I use an additional XML tag on the <dynmat> node with the name unit to determine the units of the Hessian matrix in the XML. This should be more robust.
In addition, I have changed two things in the code:

Improve the clarity of the code by using XPath Syntax
Allow for an early exit from parsing after the information has been acquired

I hope that this is ok. Otherwise I can provide a more specialized merge request that only changes the absolute minimum required.

At some versions of VASP6, hessian unit may not be written in vasprun.xml, e.g., VASP-6.1.0. Does this PR work for it?

Yes, I checked the git log on the file where the Hessian and the units are written. The change to THz coincides with the new unit tag, so it should always work this way.

Thanks!


License mentioned in README is different from LICENSE file

The license mentioned in README is the Creative Commons 4.0 while the LICENSE file is for Apache License 2.0

Good catch!
For example, this fork https://github.com/mmumshad/kubernetes-the-hard-way doesn't mention CC-BY-NC-SA, probably because they replaced the whole README.


Build failure on 64-bit macOS

Perhaps unsurprising since APEX tooling is so different:
~/Development ❯❯❯ cd Mso
~/D/Mso ❯❯❯ mkdir build
~/D/Mso ❯❯❯ cd build
~/D/M/build ❯❯❯ cmake ..
-- The CXX compiler identification is AppleClang <IP_ADDRESS>30032
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Liblet platform: WIN32
-- Liblet test runner: GTEST
-- Enable testing: ON
-- Enable includes checks: ON
-- The C compiler identification is AppleClang <IP_ADDRESS>30032
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PythonInterp: /usr/bin/python (found version "2.7.16")
-- Defining liblet Mso::compilerAdapters
-- Defining liblet Mso::comUtil
-- Defining liblet Mso::cppExtensions
-- Defining liblet Mso::cppType
-- Defining liblet Mso::crash
-- Defining liblet Mso::debugAssertApi
-- Defining liblet Mso::eventWaitHandle
-- Defining liblet Mso::functional
-- Defining liblet Mso::memoryApi
-- Defining liblet Mso::motifCpp
-- Defining liblet Mso::oacr
-- Defining liblet Mso::oacr_posix
-- Defining liblet Mso::object
-- Defining liblet Mso::platformAdapters
-- Defining liblet Mso::platform_posix
-- Defining liblet Mso::smartPtr
-- Defining liblet Mso::tagUtils
All targets: compilerAdapters;comUtil;cppExtensions;cppType;crash;debugAssertApi;eventWaitHandle;functional;memoryApi;motifCpp;oacr;oacr_posix;object;platformAdapters;platform_posix;smartPtr;tagUtils;compilerAdapters_verify_includes;compilerAdapters_verify_includes_custom;compilerAdapters_verify_includes;compilerAdapters_verify_includes_custom;comUtil_verify_includes;comUtil_verify_includes_custom;comUtil_verify_includes;comUtil_verify_includes_custom;cppExtensions_verify_includes;cppExtensions_verify_includes_custom;cppExtensions_verify_includes;cppExtensions_verify_includes_custom;cppType_verify_includes;cppType_verify_includes_custom;cppType_verify_includes;cppType_verify_includes_custom;crash_verify_includes;crash_verify_includes_custom;crash_verify_includes;crash_verify_includes_custom;debugAssertApi_verify_includes;debugAssertApi_verify_includes_custom;debugAssertApi_verify_includes;debugAssertApi_verify_includes_custom;eventWaitHandle_verify_includes;eventWaitHandle_verify_includes_custom;eventWaitHandle_verify_includes;eventWaitHandle_verify_includes_custom;eventWaitHandle_tests;functional_verify_includes;functional_verify_includes_custom;functional_verify_includes;functional_verify_includes_custom;functional_tests;memoryApi_verify_includes;memoryApi_verify_includes_custom;memoryApi_verify_includes;memoryApi_verify_includes_custom;motifCpp_verify_includes;motifCpp_verify_includes_custom;motifCpp_verify_includes;motifCpp_verify_includes_custom;oacr_verify_includes;oacr_verify_includes_custom;oacr_verify_includes;oacr_verify_includes_custom;object_verify_includes;object_verify_includes_custom;object_verify_includes;object_verify_includes_custom;object_tests;platformAdapters_verify_includes;platformAdapters_verify_includes_custom;platformAdapters_verify_includes;platformAdapters_verify_includes_custom;smartPtr_verify_includes;smartPtr_verify_includes_custom;smartPtr_verify_includes;smartPtr_verify_includes_custom;tagUtils_verify_includes;tagUtils_verify_includes_custom;tagUtils_verify_includes;tagUtils_verify_includes_custom;gmock;gmock_main;gmock;gmock_main;gtest;gtest_main;gtest;gtest_main
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/benbader/Development/Mso/build
~/D/M/build ❯❯❯ make
make[1]: Entering directory '/Users/benbader/Development/Mso/build'
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
Scanning dependencies of target gtest
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
[  1%] Building CXX object _deps/googletest-build/googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o
[  1%] Linking CXX static library ../../../lib/libgtest.a
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
[  1%] Built target gtest
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
Scanning dependencies of target gmock
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
[  1%] Building CXX object _deps/googletest-build/googlemock/CMakeFiles/gmock.dir/src/gmock-all.cc.o
[  2%] Linking CXX static library ../../../lib/libgmock.a
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
[  2%] Built target gmock
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
Scanning dependencies of target gmock_main
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
[  3%] Building CXX object _deps/googletest-build/googlemock/CMakeFiles/gmock_main.dir/src/gmock_main.cc.o
[  4%] Linking CXX static library ../../../lib/libgmock_main.a
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
[  4%] Built target gmock_main
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
Scanning dependencies of target gtest_main
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
[  5%] Building CXX object _deps/googletest-build/googletest/CMakeFiles/gtest_main.dir/src/gtest_main.cc.o
[  6%] Linking CXX static library ../../../lib/libgtest_main.a
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
[  6%] Built target gtest_main
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
Scanning dependencies of target compilerAdapters
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
[  7%] Building CXX object libs/compilerAdapters/CMakeFiles/compilerAdapters.dir/__/__/tools/cmake/empty.cpp.o
[  7%] Linking CXX static library libcompilerAdapters.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libcompilerAdapters.a(empty.cpp.o) has no symbols
warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: warning for library: libcompilerAdapters.a the table of contents is empty (no object file members in the library define global symbols)
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
[  7%] Built target compilerAdapters
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
Scanning dependencies of target compilerAdapters_verify_includes
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
make[2]: Entering directory '/Users/benbader/Development/Mso/build'
[  8%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/compilerFeatures.h.cpp.o
[  9%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/compilerWarnings.h.cpp.o
[ 10%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/compilerWarnings_impl.h.cpp.o
[ 11%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/cppMacros.h.cpp.o
[ 12%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/cppMacrosDebug.h.cpp.o
[ 12%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/declspecDefinitions.h.cpp.o
[ 13%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/functionDecorations.h.cpp.o
[ 14%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/intrinsics.h.cpp.o
[ 15%] Building CXX object libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/linker.h.cpp.o
In file included from /Users/benbader/Development/Mso/build/libs/compilerAdapters/include/verify/linker.h.cpp:1:
/Users/benbader/Development/Mso/libs/compilerAdapters/include/compilerAdapters/linker.h:36:2: error: Unknown Platform!
#error Unknown Platform!
 ^
/Users/benbader/Development/Mso/libs/compilerAdapters/include/compilerAdapters/linker.h:59:2: error: Unknown Platform!
#error Unknown Platform!
 ^
2 errors generated.
make[2]: *** [libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/build.make:167: libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/verify/linker.h.cpp.o] Error 1
make[2]: Leaving directory '/Users/benbader/Development/Mso/build'
make[1]: *** [CMakeFiles/Makefile2:1269: libs/compilerAdapters/include/CMakeFiles/compilerAdapters_verify_includes.dir/all] Error 2
make[1]: Leaving directory '/Users/benbader/Development/Mso/build'
make: *** [Makefile:141: all] Error 2

Something about an undefined platform.  It's been long enough since I've been inside of MSFT that I don't feel confident trying to guess what needs to happen.  Possibly just defining _M_X64?
...also, kudos on getting some of this stuff out into the open!  I was just waxing lyrical about RefCountedObject tonight when I learned about this repo.  It makes me happy to see it again.

Figured it out.  To build from the command line, cmake needs to be told what the platform is:
cmake .. -DMSO_LIBLET_PLATFORM=MAC


Fixed broken test set up and sqllite valuewrapper bug

Fixes #265 Added missing init py to pypika.test.dialects and fixed bug where wrapper class was not being used correctly

Coverage increased (+0.09%) to 98.028% when pulling e573364e9c0a85355b4a2a432b83d68c2195d289 on fix_sqllite_valuewrapper into 285b1eeb8db853beefed46323108930ccdda21d5 on master.


Template: Add answer for legal aspects data owner and modify verbiage

Description

Add to the templates the answer to the question List who will have the rights to control access to which dataset(s) and update the wording in the templates for the Intellectual Property Rights section.

https://github.com/tuwien-csd/damap-frontend/issues/268
What does this PR do?

Update the wording in the Intellectual Property section, add to the templates the answer to the question List who will have the rights to control access to which dataset(s).
Breaking changes

Code review focus

Dependencies

Checks

[ ] Tested with Oracle/PostgreSQL
[ ] Export updated
[ ] Documentation added
[ ] Tests added
[ ] E2e tests created
[ ] Successfully ran e2e tests before merge

closes GH-268

FWFTemplate_review.docx
horizonEuropeTemplate_review.docx
scienceEuropeTemplate__review.docx


Build empty constructor when none specified

Hey!
This changes the derive implementation to always include an empty constructor, even if none is available in the ABI specification.
This makes it easier to use a uniform deploy implementation, even when there are no constructors specified in the solidity contract.

thanks!


fix(cf_worker): Don’t use return await in async functions

This adds a slight performance optimisation to the Cloudlfare Worker script.
External links:

https://eslint.org/docs/rules/no-return-await
https://developer.mozilla.org/docs/Web/JavaScript/Reference/Statements/async_function

Also adds JSDoc to the handleRequest(…) function to add intellisense in IDEs.

Awesome, thanks! 👍


Cannot use PyAudio in MacOS M1.

Hi, I have been trying to use SpeechRecognition module. Here is my code
`
import speech_recognition as sr
def real_time_speech_recognition():
recognizer = sr.Recognizer()
with sr.Microphone() as source:
    print("Say something or press 'q' to end.")

`
However, it keep on outputting the same error :
Traceback (most recent call last):   File "/Users/nuntea/Documents/Vasundhara Geo technology/Voice recognition and NER/Real Time Speech recogntiion/RTSR.py", line 11, in <module>     real_time_speech_recognition()   File "/Users/nuntea/Documents/Vasundhara Geo technology/Voice recognition and NER/Real Time Speech recogntiion/RTSR.py", line 7, in real_time_speech_recognition     with sr.Microphone() as source:   File "/Users/nuntea/Documents/Vasundhara Geo technology/Voice recognition and NER/Real Time Speech recogntiion/myenv/lib/python3.9/site-packages/speech_recognition/__init__.py", line 80, in __init__     self.pyaudio_module = self.get_pyaudio()   File "/Users/nuntea/Documents/Vasundhara Geo technology/Voice recognition and NER/Real Time Speech recogntiion/myenv/lib/python3.9/site-packages/speech_recognition/__init__.py", line 110, in get_pyaudio     raise AttributeError("Could not find PyAudio; check installation") AttributeError: Could not find PyAudio; check installation
However, I have already install PyAudio.
`(myenv) nuntea@Zonunmawias-MacBook-Air Real Time Speech recogntiion % pip list
Package                                           Version

certifi                                           2023.11.17
charset-normalizer                                3.3.2
idna                                              3.4
keyboard                                          0.13.5
pip                                               23.3.1
PyAudio                                           0.2.14
requests                                          2.31.0
setuptools                                        69.0.0
SpeechRecognition                                 3.10.0
urllib3                                           2.1.0
wheel                                             0.41.3`
I have tried different method mention in stackoverflow and other resources but couldn't fixed it :
(myenv) nuntea@Zonunmawias-MacBook-Air Real Time Speech recogntiion % xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" in System Settings to install updates
(myenv) nuntea@Zonunmawias-MacBook-Air Real Time Speech recogntiion % brew install portaudio Warning: portaudio 19.7.0 is already installed and up-to-date. To reinstall 19.7.0, run:   brew reinstall portaudio
(myenv) nuntea@Zonunmawias-MacBook-Air Real Time Speech recogntiion % pip3 install pyaudio Requirement already satisfied: pyaudio in ./myenv/lib/python3.9/site-packages (0.2.14)
Please help.

Hi @Nuna7, I came across the same issue when I first used this library on my M1 Mac too, although I install PyAudio the way it is described int he docs. Below is the part in the docs I did to fix it, let me know if the issue still continues:

On OS X, install PortAudio using Homebrew <http://brew.sh/>: brew install portaudio. Then, install PyAudio using Pip <https://pip.readthedocs.org/>: pip install pyaudio.

Works just fine for me on my M1 Mac after brew install portaudio


'React/RCTBridgeModule.h' file not found

Expected behavior
I used Cocoapods to add React native to my existing iOS app.
Observed behavior

Xcode can't seem to link React library files with Bugsnag.
Solutions on the Internet suggest unchecking "parallelize build" under the main project scheme, and adding React. I did these steps, but this still didn't fix it. Here's my scheme:

I've also tried changing the header imports manually, and that stops the errors one by one but it's not a sustainable solution.
E.g., '#import <React/RCTBridgeModule.h>' => '#import "RCTBridgeModule.h"
I also tried adding React to the header search paths, but that had no effect. Here are my settings under Project Settings => Build Settings => Header Search Paths:

Version
Bugsnag-react-native v. 2.5.0
react-native v. 0.48.3
XCode v. 9.0
Additional information
In RN 0.40.0 the library files were reorganized into the React namespace: '#import <React/RCTBridgeModule.h>' => '#import "RCTBridgeModule.h"... yet somehow Xcode didn't catch on to this.

Thanks for the report, @danbenn. I have a working example with cocoapods in https://github.com/bugsnag/bugsnag-react-native/pull/167, can you try running that branch project or comparing the configuration to see if there's something missing?
Is React Native also installed via CocoaPods?

Awesome, thanks! I didn't realize I could install with Cocoapods as opposed to react-native link.
Adding this line to my Podfile fixed it:
pod 'BugsnagReactNative', path: './node_modules/bugsnag-react-native'

My issue had nothing to do with bugsnag but with the fact that i was using react-native 0.57.8  but forgot to update react to 16.6.3 which is absolutely necessary.


Error while connecting MongoDb

post  = %MyApp.Post{title: "dfsd", body: "dfdsf"}
 MyApp.Repo.insert!(weather)

Following above error throws error as
(UndefinedFunctionError) function Mongo.Ecto.insert/6 is undefined or private
help us in fixing it.
mix.exs
  defp deps do
    [{:phoenix, "~> 1.2.1"},
      {:ecto, "~> 2.0", override: true},
     {:phoenix_pubsub, "~> 1.0"},
     {:phoenix_ecto, "~> 3.0"},
     {:postgrex, ">= 0.0.0"},
     {:phoenix_html, "~> 2.6"},
     {:phoenix_live_reload, "~> 1.0", only: :dev},
     {:gettext, "~> 0.11"},
     {:mongodb_ecto, github: "michalmuskala/mongodb_ecto", branch: "ecto-2"},
     {:cowboy, "~> 1.0"}]
  end

 def application do
    [mod: {MyApp, []},
     applications: [:phoenix, :phoenix_pubsub, :phoenix_html, :cowboy, :logger, :gettext,
                    :phoenix_ecto, :postgrex, :mongodb_ecto, :ecto]]
  end

lib/my_app/repo.ex
use Ecto.Repo, otp_app: :mongo_ecto, adapter: Mongo.Ecto
lib/my_app.ex
supervisor(MyApp.Repo, [])

This doesn't make sense for the dependencies you have listed. Based on the error, you have Ecto 2.1 loaded.

Closing for lack of activity.


deleting of repo does not work

removing labels from checked-in images or removing repo's does not work.. gui seems to hang.

I wasn't able to reproduce it.

I was able to remove tag separately (checking a tag and clicking on delete tag button) and also the repo at once (clicking on delete repository button).
To delete a comment you need to hover the comment and a link will appear on the top right of the comment. I was also able to delete it.
Any error on console or devtools?

No errors but let me dig in to it a bit... did see that Vue is running in development mode. that you might want to change later as well :)

did see that Vue is running in development mode.

How are you running your instance?

Right now I just done a git pull, build and compose up... did not change anything
Met vriendelijke groet,
Sven v Hamelsveld

Warning: I either dictated this to my mobile device, or I typed it clumsily. Expect typos, auto corrections and weirdness.

On 27 Jul 2018, at 15:53, Vítor Avelino<EMAIL_ADDRESS>wrote:
did see that Vue is running in development mode.
How are you running your instance?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Right now I just done a git pull, build and compose up... did not change anything

This is development mode. That's why you are getting that message.

What do I need to do to change that? Make the release :latest?

On 27 Jul 2018, at 16:18, Vítor Avelino<EMAIL_ADDRESS>wrote:
Right now I just done a git pull, build and compose up... did not change anything
This is development mode. That's why you are getting that message.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SUSE/Portus/issues/1913#issuecomment-408432471, or mute the thread https://github.com/notifications/unsubscribe-auth/APY-AL6zFB7ygz2oQn31vtos_rsdOMF7ks5uKyFDgaJpZM4VjdD2.

It depends on your deployment strategy. There are some content at http://port.us.org/docs/deploy.html that might help you.

when I create a new repo and try to delete the repo nothing happens. However when I then press delete tags it deletes the tags and the repo "Repository removed with all its tags."
now I've still 3 repo's left with no images in there and no tags ... those are non deletable .. :)

You are saying that when you go to /repositories you see 3 entries and all of them displays 0 on the tags column?

yes

Well... that's weird. I never faced that kind of issue.

the "latest" tag dont count in Portus

okay I've rebuild a few time with he latest release and can't recreate the issue anymore so think we can close this one.


add optional coffeescript support

Id rather not add the CoffeeScript support.  Not really part of what we are trying to demonstrate with this.

totally valid response. =)


"Yikes!" internal Serverpod error when running in debugger (path not normalized)

Describe the bug
If I run Serverpod in the VS Code debugger using (in launch.json), with the git main version of serverpod_cli:
{
    "version": "0.2.0",
    "configurations": [
       {
            "name": "serverpod generate",
            "request": "launch",
            "type": "dart",
            "console": "debugConsole",
            "program": "../vendor/serverpod/tools/serverpod_cli/bin/serverpod_cli.dart",
            "args": ["generate"]
        }
    ]
}

then I get the following error:
Yikes! It is possible that this error is caused by an internal issue with the Serverpod tooling. We would appreciate if you filed an issue over at Github. Please include the stack trace below and describe any steps you did to trigger the error.
https://github.com/serverpod/serverpod/issues
Invalid argument(s): Path must be normalized : /home/luke/Work/myproj/myproj_server/../myproj_client/lib/src/protocol/account.dart
#0      PhysicalResourceProvider._ensureAbsoluteAndNormalized.<anonymous closure>
physical_file_system.dart:89
#1      PhysicalResourceProvider._ensureAbsoluteAndNormalized
physical_file_system.dart:92
#2      PhysicalResourceProvider.getFile
physical_file_system.dart:51
#3      AbstractDartSdk.pathToUri
sdk.dart:151
#4      DartUriResolver.pathToUri
source.dart:54
#5      SourceFactoryImpl.pathToUri
source.dart:106
#6      FileSystemState.hasUri
file_state.dart:1388
#7      AnalysisDriver.changeFile
driver.dart:568
#8      DriverBasedAnalysisContext.changeFile
driver_based_analysis_context.dart:56
#9      EndpointsAnalyzer.analyze
endpoints_analyzer.dart:76
#10     performGenerate
generator.dart:46
<asynchronous suspension>
#11     _main
serverpod_cli.dart:282
<asynchronous suspension>
#12     main.<anonymous closure>
serverpod_cli.dart:44
<asynchronous suspension>
#13     main
serverpod_cli.dart:41
<asynchronous suspension>

Weirdly the path that is supposed to be passed from serverpod_cli to analyzer is supposed to be using the absolute path: endpoints_analyzer.dart:76 is:
          context.changeFile(file.absolute.path);

so I don't even know how this error is possible, since the path /home/luke/Work/myproj/myproj_server/../myproj_client/lib/src/protocol/account.dart should have been normalized.
Serverpod versions

CLI Version: git main
Library version: git main

Platform information
Linux

Thank you! Fix pending.


WIP: Adding tests for benchmark.py

Trying to revive the benchmark testing.
Comments from the old PR
https://github.com/devitocodes/devito/pull/957

why is this a PR already?

why is this a PR already?

No it is not ready. Do you mind if I keep it open for short-term? Like 24 hours?

sure np....but out of curiosity, why?

sure np....but out of curiosity, why?

Because I am thinking of pushing my changes to see how they react on travis.
I can run pytest locally but can I do something similar for travis?

travis always runs even w/o PRs
it's azure pipelines that runs only when a PR is open

travis always runs even w/o PRs
it's azure pipelines that runs only when a PR is open

Correct. You have told me that again in the past but I forgot.
I will close temporarily.


Folder API doesn't allow for internal iteration optimisation of filter-like adapters

In #631 it was found that the filter and filter_map parallel iterator adaptors can't have their Folder's changed to maximally benefit from any optimisations that their base folder has for consuming a whole iterator via consume_iter. These adaptors may consume an arbitrary number of elements before yielding anything, and so need to regularly manually check whether their base is full, or else they may get stuck unnecessarily consuming a whole split.
The Problem: filter shouldn't use naive serial adaptors
For instance, consider this potential version of filter's Folder that naively just uses (serial) iterator adaptors:
struct FilterFolder<'p, C, P: 'p> {
    base: C,
    filter_op: &'p P,
}

impl<'p, C, P, T> Folder<T> for FilterFolder<'p, C, P>
where
    C: Folder<T>,
    P: Fn(&T) -> bool + 'p,
{
    type Result = C::Result;

    fn consume(self, item: T) -> Self {
        let filter_op = self.filter_op;
        if filter_op(&item) {
            let base = self.base.consume(item);
            FilterFolder {
                base: base,
                filter_op: filter_op,
            }
        } else {
            self
        }
    }

    fn consume_iter<I>(mut self, iter: I) -> Self
    where
        I: IntoIterator<Item = T>
    {
        self.base = self.base.consume_iter(iter.into_iter().filter(self.filter_op));
        self
    }

    fn complete(self) -> Self::Result {
        self.base.complete()
    }

    fn full(&self) -> bool {
        self.base.full()
    }
}

This benefits from both any optimisations self.base has for handling whole iterators, and from internal-iteration optimisations that iter (and item.filter(_)) has, and can be significantly faster.
However, while consume_itering, self.base.full() will only get checked for each element that the filter adaptor actually yields (that is, self.base will handle short-circuiting when it is itself full). If filter doesn't yield anything for an extended period, it may be seconds/minutes/hours between checks, which can incorrectly miss when other parallel threads have finished a task. Consider:
#[test]
fn filter_octillion() {
    let x = octillion().filter(|&x| x > OCTILLION / 2).find_any(|_| true);
    assert!(x.is_some());
}

The first split is huge and filter won't yield anything, but later splits will very quickly find an element. Using the consume_iter above, the first split won't realise that find_any has finished, and will continue to process the whole split rather than short circuiting.
Failed Fix: take_while
One way to fix this would be to limit item using self.base.full(), so that it stops attempting to process items once another thread has finished:
self.base = self.base.consume_iter(iter.into_iter().take_while(|_| !self.base.full()).filter(self.filter_op));

But this doesn't and can't work: consume_iter consumes self.base. I don't think there's any variation along these lines that can work.
Proposal: Split full into an independent object
A possible thing that would address this is allowing breaking a "is full" object out of a folder, that can be handled independently from the original object, something like:
/// A type that can check whether a Folder is full.
trait FullChecker {
    fn full(&self) -> bool;
}

trait Folder<F> {
    // no change:
    type Result;
    fn consume(...)
    fn consume_iter(...)
    fn complete(...)

    // new:
    type Full: FullChecker;
    fn full_checker(&self) -> Self::Full;
    fn full(&self) -> bool { self.full_checker().full() }
}

There could be convenience types covering the common cases (i.e. most things other than find_first/find_last):
struct NeverFull;
impl FullChecker for NeverFull { fn full(&self) -> bool { false } }

struct BoolFull<'a>(&'a AtomicBool);
impl<'a> FullChecker for BoolFull<'a> {
    fn full(&self) -> bool { self.0.load(Ordering::Relaxed) }
}

For instance:

FilterFolder::consume_iter then becomes:
let base_full = self.base.full_checker();
self.base = self.base.consume_iter(iter.into_iter().take_while(|_| !base_full.full()).filter(self.filter_op));

MapFolder (and FilterFolder) becomes something like:
impl<...> Folder<T> for MapFolder<...> {
    // ...

    type Full = C::Full;
    fn full_checker(&self) -> C::Full { self.base.full_checker() }
}

FindFolder becomes something like
impl<...> Folder<T> for FindFolder<...> {
    // ...

    type Full = BoolFull;
    fn full_checker(&self) -> BoolFull { BoolFull(self.found) }
}

ReduceFolder becomes something like:
impl<...> Folder<T> for ReduceFolder<...> {
    // ...

    type Full = NeverFull;
    fn full_checker(&self) -> NeverFull { NeverFull }
}

Thanks for the nice write-up!


Overridden call type not always consulted when doing dead store elimination for registers

Relevant disassembly:

Notably x1 is set to sp + 0x48 at 10b0, and is the second argument to printf. At this point, printf type at 10c0 is uint64_t  printf@2da0(char* arg1, ...).
This turns into expected LLIL:

MLIL initially is as expected, as printfs type signature is wrong for this call site:

Now, while the string in the screenshots is truncated, it has a single positional paramter of char * from a %s. If I override the call site's type to account for this, the MLIL turns into this:

For some reason it is pulling x1 from the previous call, not the initialization that happens immediately prior.
If I remove the override and globally change printf's call type to const char *fmt, char * I get the expected result:

Happy to provide binaries or bndb's if needed.

Fixed last week in 2.2.2649-dev.


created_at field missing from products

The mage2vuestorefront is importing the created_at field for products, but the indexer is not. Is there a reason for this?
My colleague created a feature that adds a "New product" badge to products added in the last n days. I couldn't understand how she had been able to get the field to elasticsearch, until I realized she was using mage2vuestorefront and I was using the indexer.

No, it was just not used in VSF core, so that's why it is omitted.

@juho-jaakkola you are welcome to make a PR with requested changes.

I ended up using two custom attributes (new_from_date and new_to_date) instead. So can be closed, and reopened if someone else runs into the same need.


Enabled sample pipeline in DSPA samples

The issue resolved by this Pull Request:
Resolves https://issues.redhat.com/browse/RHOAIENG-6580
Description of your changes:

This PR enables the sample pipeline in DSPA samples.
Testing instructions

Deploy a DSPA sample and the sample pipeline must be present.
Checklist

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-668
An OCP cluster where you are logged in as cluster admin is required.
To use this image run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/668/head
git checkout -b pullrequest 89921c5e11c2d1faa22549ac5758e45e88518666
oc new-project opendatahub
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-668"

More instructions here on how to deploy and test a Data Science Pipelines Application.

/approve


report: make it possible to specify port

This makes it possible to run multiple runs in parallel both with report generation.

/gcbrun exp -n dk-test-infra12310 -m vertex_ai_gemini-1-5 -b minor-for-ci -i


ESM1.5 ssp585 15-24

resolution_complete type_ScenarioMIP   |    by<EMAIL_ADDRESS>
10 additional ensemble members for SSP585
exp name: SSP-585-15.. 24
branched from: HI-15..24
cmip6 exp name: ssp585

Issue migrated from trac:412 at 2024-01-31 18:39:29 +1100

<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>set resolution to complete


Fix docs side-nav background.

This allows the side-nav background color to extend
to the bottom of the screen.
Before:

After:

LGTM. FWIW we've had #1704 and #1028 for this but both were closed since we will be ditching this template once the generic gcloud-common template is in use.

Ah, I should have searched. Thanks @dhermes!
Should I merge or you? I'm in practice of not merging my own code for peer reviewing.

When it is amongst @tseaver and myself, the author does the merge. (In causes where a contributor can't merge, then the reviewer does.)


Added namespace field and reverse the resources

Signed-off-by: viveksahu26<EMAIL_ADDRESS>Related Issue(s)
https://github.com/kyverno/policies/issues/344

Description
Added [ ]results.namespace in the test.yaml file

Checklist

[X] I have read the policy contribution guidelines.
[X] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.

Hey @vyankyGH , I have added namespace. Could you review this.

@viveksahu26 thanks for this PR, but you have once again not linked it back to the issue which it is intended to close.

You either need to use closing keywords in front of the issue number or manually link it to the issue on the right side of the screen.

@viveksahu26 thanks for this PR, but you have once again not linked it back to the issue which it is intended to close.

You either need to use closing keywords in front of the issue number or manually link it to the issue on the right side of the screen.

Hey @viveksahu26 You mean to say that, to add issue in the Development section of the PR.

If you use closing keywords, it will automatically link it to the issue and show up in the Development section.


360 photo and video support

Basic integration of Valiant360 webGL library to view 360-degree photos and videos within sigal gallery. Modification of galleria theme, click VR icon or on the active image to open modal.

Hi,
Thanks for the PR, this seems to be a nice feature. However I'm not sure to want this in the core galleria theme, because this means more dependencies, and for each release it is a lot of work to update all the dependencies to their latest versions and check that everything still works.
What would think about putting this in another repository, like the 153957-theme (which can be pip-installed, which is great but not strictly necessary) ? The theme could then be referenced in https://github.com/saimn/sigal/wiki with other community efforts.


Compiler complains about table "Media Set" and "Media"

An error occurs in VS Code, when you define a variable of Record "Media Set" or "Media":
"The type or method 'Media' cannot be used for 'Extension' development."
"The type or method 'Media Set' cannot be used for 'Extension' development."
Is there a reason for it?

In multi-tenant installations, Media and Media Set tables may contain cross-tenant data, therefore extensions cannot read from them.
Could you please share more details about your scenario? Would you be able to use Tenant Media and Tenant Media Set tables instead?
P.S. You can always change the "target" property in the app.json to "Internal" to get access to Media and Media Set. But please remember that you will not be able to submit such extensions to AppSource, should you have an intention to do so.

Thanks for the quick answer. Tenant Media Set and Tenant Media works for us.

Thanks, closing then.


missing the action of "Staging a selection of code"

VSCode Version: 1.11.1
OS Version: win7-pro

Steps to Reproduce:

open VCS diff dialog
missing the action of "Staging a selection of code"

PS: it worked in the previous version

Duplicate of #24052, related to #21513