Exported animation is 1 frame short.

While working on https://mrdoob.github.io/rome-gltf/ I realised animations were not looping correctly.
You can see the issue by loading quadruped_wolf.gltf in http://gltf-viewer.donmccurdy.com and setting the animation speed to 0.25.

You'll see that the last morphtarget doesn't crossfade with the first morphtarget. By changing the animation end to from 14 to 15 (quadruped_wolf_fix.gltf), the resulting gltf loops properly in the viewer, but the loop glitch then appears in blender because now the last frame and first frame are the same.
This is how the curves look like:

After talking about this with a few people during Siggraph and considering all the possible levels (Blender, Exporter, Loader, Engine) my believe is that the issue is simply that the exporter should export one more frame.
My rational is that... Right now the exporter is not taking in consideration that blender frames have a length. It's treating the beginning of the last frame as the end of the animation. So in the case of quadruped_wolf.gltf the engine is not able to reproduce frame 14, because the exporter skipped it.
I think the exporter should treat the end of the last frame as the end of the animation. Exporting one more frame should virtually be the same.
With this change exported animations should then look exactly as they look in Blender.
quadruped_wolf.zip

Having said all that, I just created a simple test of a spinning cube and my suggestion would break it.
cube_rotating.zip
So it may be an issue of how Blender treats Shape Keys... 🤔

Currently also looking at it.

Just learnt to do time remapping in Blender and then it behaves like in the engine.
I have spent way too long on this and at this point I would be happy to just modify the animations so they have one more frame even if they are slightly glitchy when reproducing in Blender.
Feel free to close this if you don't see anything wrong 😣

The last frame (15) has no influence in Blender: Delete it or give it some extreme value. The animation does not change.
Hmmm ...

Probably we need to ask someone from Blender, what exactly is happening here.
I have attached a sample Blender file, which lets you start thinking: "I have done my animations always wrong" :-)
magic_blender.zip
Open and play the animation and check the values!


Fails to load /ClientResources/Scripts/contentediting/CreateContent.js on DXP Linux (Kestrel)

Kestrel may treat URLs case-sensitive. Therefore, naming the folder as below causes issue in CMS when deploying to Linux while CMS expects the path to be all lowercase "contentediting": https://github.com/episerver/foundation-mvc-cms/tree/net5/src/Foundation/wwwroot/ClientResources/Scripts/ContentEditing.

Confirmed. There are a few similar issues that we'll need to clean up. I think I've identified most of them in the following commit on my fork, but haven't merged back here yet -- https://github.com/daniel-isaacs/foundation-mvc-cms/commit/07065ba558358b6e958d98475fe08061b95437e9

should be fixed

Should be fixed with https://github.com/episerver/foundation-mvc-cms/pull/124


feature request: python style contex manager for style pushing, window management, etc

good to prevent wrong stacks
e.g.
import imgui

class Window:
    def __init__(self, *args, **kwargs):
        self.args = args
        self.kwargs = kwargs

    def __enter__(self):
        return imgui.begin(*self.args, **self.kwargs)

    def __exit__(self, exc_type, exc_value, traceback):
        imgui.end()

class StyleColor:
    def __init__(self, *args, **kwargs):
        self.args = args
        self.kwargs = kwargs

    def __enter__(self):
        imgui.push_style_color(*self.args, **self.kwargs)

    def __exit__(self, exc_type, exc_value, traceback):
        imgui.pop_style_color()

class ImguiId:
    def __init__(self, *args, **kwargs):
        self.args = args
        self.kwargs = kwargs

    def __enter__(self):
        imgui.push_id(*self.args, **self.kwargs)

    def __exit__(self, exc_type, exc_value, traceback):
        imgui.pop_id()

class Font:
    def __init__(self, font):
        self.font = font

    def __enter__(self):
        imgui.push_font(self.font)

    def __exit__(self, exc_type, exc_value, traceback):
        imgui.pop_font()

This is an interesting suggestion. I agree that it could be a good thing to have this functionality for all push/pop pairs.
It however raises a couple of question that should be addressed before going into it.
How would this look like if we push several commands onto the stack?
with imgui.style_color(xxx):
    with imgui.font(yyy):
        # ...

Would it be possible to somehow merge those in a single with statement? (And would it be a good thing?)
Should we add new names (like style_color, etc) or should we keep the current set of objects and make them compatible with current calls. As we did for the begin/end pairs? In my opinion, having a new set of objects to manage the with statement without altering existing push_* calls sounds better. It wouldn't add overhead on those. But for consistency with begin/end way of doing thing it may be better to have something like:
with imgui.push_style_color(xxx):
    # ...

For reference and discussion, I link here #264, #271, and #272


arm64: lift sxtl, sxtl2, sshll, sshll2

Partially fixes #5417
Also superficial re-ordering of the tests to make it easier to add new tests.
With both PRs targeting #5417 we get this LLIL:
  41 @ 100003ea0  s1 = [x29 - 8 {var_18}].d
  42 @ 100003ea4  s0 = s1
  43 @ 100003ea8  v0.d[0] = sx.q(v0.s[0] u>> 0 << 0)
  44 @ 100003ea8  v0.d[1] = sx.q(v0.s[1] u>> 0 << 0)
  45 @ 100003eac  d1 = int.q(d0)
  46 @ 100003eb0  d0 = 10.0
  47 @ 100003eb4  d0 = d0 f+ d1
  48 @ 100003eb8  s0 = fconvert.s(d0)
  49 @ 100003ebc  x8 = sx.q([x29 - 8 {var_18}].d)
  50 @ 100003ec0  x9 = 0x2c
  51 @ 100003ec4  x9 = x8 * x9
  52 @ 100003ec8  x8 = &main::x
  53 @ 100003ecc  x8 = x8
  54 @ 100003ed0  x8 = x8 + x9
  55 @ 100003ed4  [x8 + 0x28].d = s0
  56 @ 100003ed8  [x29 - 0xc {var_1c_1}].d = 0
  57 @ 100003edc  goto 58 @ 0x100003ee0

and this HLIL:
  10 @ 100003ea0  int64_t v1
  11 @ 100003ea0  v1.d = var_18
  12 @ 100003ea4  v0.d = v1.d
  13 @ 100003eb8  v0.d = fconvert.s(10.0 f+ int.q((v0.d u>> 0 << 0):4.d u>> 0 << 0))
  14 @ 100003ed4  *(sx.q(var_18) * 0x2c + 0x100008028) = v0.d
  15 @ 100003ed8  int32_t var_1c_1 = 0

Finally, it looks like there are some other unlifted SHL variants that would probably follow the same template. Let me know if you've come across any of these and I can take a look.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing PR because superseded by e3b91f9e65646a6b9cc69d2a353ad268ee20767b


Only define rendering of LambdaInfo on versions of Julia where it is defined to avoid breaking the package on Julia 0.6-.

Just realized that the REPL is broken with this so I'll close and wait for a real fix (hopefully with some test.)

nope, you get a less accurate fix. 0e9ad8c0b54c6481417e48dc32e825e12a4a5598


Snippit maintenance / automatic doc generation

For intro comments, see https://github.com/dthree/wat/commit/419654cfa180e321f2ac1a0d031ff195ec26d2f9

@Qix- I'm getting really close on fully working auto-doc generation, and I'd like to have someone to run these things by. Are you up to that? :fire:

Sure :)

Sweet :) I'll ping you some instructions tomorrow!

@Qix- if you could, I would love if you test out some things for me: I'm trying to see how long some things take on different systems. If you can:

Note how many seconds this takes:

npm install -g wat

Tabbing a few times on a library that hasn't been built will now auto-build the library, so that after it's built, you can carry on with your autocompletion without re-typing anything:

$ wat
? node [tab] [tab] [tab] [tab]

  Building, please wait...

  Done.

? node [try tabbing again, it should show all the node API]

Could you time how long the node build takes and if it works properly?

Try:

delete node

This should just take a second, and next time you tab, node should be grey again.

Thanks!

@sindresorhus you originally brought up this point. After over a month of work on it, I think I've got this problem pretty well wrapped up.
I'd love to get your present feedback / advice on it. If you have a second, could you try this out:
$ npm install -g wat
$ wat tour

This will walk you through what wat can do now.
@wooorm @Qix- @anko feedback from you guys as well would be awesome!

It looked neat, then I got to generating the chalk docs, which exited with 1 and errored:
fs.js:549
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                                                  ^

Error: EACCES: permission denied, open '/usr/lib/node_modules/wat/dist/clerk/../../config/index.json'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.writeFileSync (fs.js:1161:15)
    at Object.write (/usr/lib/node_modules/wat/dist/clerk/indexer.js:377:8)
    at /usr/lib/node_modules/wat/dist/autodocs/autodocs.js:78:38
    at checker (/usr/lib/node_modules/wat/dist/clerk/indexer.js:103:9)
    at /usr/lib/node_modules/wat/dist/clerk/indexer.js:112:7
    at Walker.<anonymous> (/usr/lib/node_modules/wat/dist/clerk/indexer.js:220:7)
    at emitNone (events.js:67:13)
    at Walker.emit (events.js:166:7)

I installed wat as root but am using it as my own user. Does wat try to cache in its install location? (If so, requesting $XDG_CACHE_HOME/wat|| ~/.cache/wat instead.)

@dthree First of all, very nice work! From what I tried, wat was really useful and I plan to use it in my flow in the future :+1:
I found some funky things going on with mdast. I probably have some weird documentation preferences, so I can imagine that having to do with it. Let me know if you have suggestions regarding that!

@anko aah I see what happened. 99% of the writes go to a temp dir - that write that errored there is something I was going to fix, didn't realize it would create that problem. Should be handled today! Anyway, if you run it as root for now, you should be able to make it through the rest of the tour :)

@wooorm thanks!!
On mdast, yeah I saw that. I just added like 10 more libs yesterday, so I have to go through and tune the autodoc generator to hit more edge cases.  The main sit is recognizing what is and isn't an API syntax declaration.
I'll probably end up fine-tuning about 30 or 40 libs before I release it.
Happy you find it useful though, and suggestions are accepted!

:+1:

@anko just did a mongo refactor that migrates all writes to the temp directories. I think I got everything. Would you mind re-installing and trying the tour again?

@wooorm I managed to clean up the autodoc response of mdast a bit. Still a few challenging quirks, I think though. Would you mind checking it out and telling me what you see wrong with the generated docs?

Looks better, but still some problems, I listed some points I found in GH-23.

@dthree Aaa, now I get
$ wat tour

  ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  |                                                                                |
  |  Welcome to Wat. Let's look up how to use Javascript's "array.slice()" method.                                                                                |
  |                                                                                |
  |  Type "js array slice" and press [enter].                                                                                |
  |                                                                                |
  └──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

? js array slice

  Sorry, there's no command like that.

  ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  |                                                                                |
  |  This pulled up a rapid description of the ".slice" command, and a usage example.                                                                                |
  |  This is the hallmark of wat - just the data you need, and nothing more.                                                                                |
  |                                                                                |
  └──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

  ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  |                                                                                |
  |  Now, let's see what content wat has. Press [tab] twice.                                                                                |
  |                                                                                |
  └──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

?

Anything I enter says "there's no command like that".
Is there perhaps a cache I haven't deleted that's giving me a dirty install?
$ jq '.version' < /lib/node_modules/wat/package.json
"0.1.31"

Did you just do a fresh install? Try:
? index"
This should re-index you.

@wooorm @anko @tomByrer @octalmage @defel @Qix- just finished the Wiki docs for added auto doc content to Wat. Adding a library should be incredibly easy and take 10 minutes or less, so I want to make sure my docs are intuitive and reflect that.
If you guys are able to, would you mind reading this Wiki and seeing if you can successfully do a PR on a new doc set? You can just pick any library you love. If anything's confusing, I'd like to know now, now when I release it :)
https://github.com/dthree/wat/wiki/Docs-|-101
Thanks!!


Add ability to adjust screen timing

This pull request adds three variables to the config.py.sample, and amends weather.py to accept these variables. It was written to be backward compatible with what current users are accustomed to seeing.
config.py.sample additions:
# Number of seconds to pause on the Daily and Hourly weather screens.
DH_PAUSE = 60 # 1 minute

# Number of seconds to pause on the Info screen.
INFO_SCREEN_PAUSE = 300 # 5 minutes

# Number of seconds between showing the info screen.
INFO_SCREEN_DELAY = 900 # 15 minutes

weather.py amendments (line 867+):
    # Automatically switch back to weather display after a couple minutes.
    if MODE not in ('d', 'h'):
        PERIODIC_INFO_ACTIVATION = 0
        NON_WEATHER_TIMEOUT += 1
        # Default in config.py.sample: pause for 5 minutes on info screen
        if NON_WEATHER_TIMEOUT > (config.INFO_SCREEN_PAUSE * 10):
            MODE = 'd'
            syslog.syslog("Switched to weather mode")
    else:
        NON_WEATHER_TIMEOUT = 0
        PERIODIC_INFO_ACTIVATION += 1
        # Default in config.py.sample: flip between 2 weather screens
        # for 15 minutes before showing info screen.
        if PERIODIC_INFO_ACTIVATION > (config.INFO_SCREEN_DELAY * 10):
            MODE = 'i'
            syslog.syslog("Switched to info mode")
        elif (PERIODIC_INFO_ACTIVATION % (config.DH_PAUSE * 10)) == 0 and
              MODE == 'd'):
            MODE = 'h'
        elif (PERIODIC_INFO_ACTIVATION % (config.DH_PAUSE * 10)) == 0 and
              MODE == 'h'):
            MODE = 'd'

Relevant: https://github.com/genebean/PiWeatherRock/issues/28

Thank you very much for this! The code looks good. I want to test it locally today but will merge it after that so long as it behaves as expected.

Thank you very much for this! The code looks good. I want to test it locally today but will merge it after that so long as it behaves as expected.

No problem. After reading Issue https://github.com/genebean/PiWeatherRock/issues/28 I think I'm going to amend this further, so that the end user can choose different screen times for daily and hourly, as well. I'll push the changes later today.

update to config.py.sample additions:
# Number of seconds to pause on the Daily weather screen.
DAILY_PAUSE = 60 # 1 minute

# Number of seconds to pause on the Hourly weather screen.
HOURLY_PAUSE = 60 # 1 minute

# Number of seconds to pause on the Info screen.
INFO_SCREEN_PAUSE = 300 # 5 minutes

# Number of seconds between showing the info screen.
INFO_SCREEN_DELAY = 900 # 15 minutes

update to weather.py (line 869+)
    # Automatically switch back to weather display after a couple minutes.
    if MODE not in ('d', 'h'):
        PERIODIC_INFO_ACTIVATION = 0
        NON_WEATHER_TIMEOUT += 1
        D_COUNT = 0
        H_COUNT = 0
        # Default in config.py.sample: pause for 5 minutes on info screen.
        if NON_WEATHER_TIMEOUT > (config.INFO_SCREEN_PAUSE * 10):
            MODE = 'd'
            D_COUNT = 1
            syslog.syslog("Switching to weather mode")
    else:
        NON_WEATHER_TIMEOUT = 0
        PERIODIC_INFO_ACTIVATION += 1
        # Default in config.py.sample: flip between 2 weather screens
        # for 15 minutes before showing info screen.
        if PERIODIC_INFO_ACTIVATION > (config.INFO_SCREEN_DELAY * 10):
            MODE = 'i'
            syslog.syslog("Switching to info mode")
        elif (PERIODIC_INFO_ACTIVATION % (((config.DAILY_PAUSE * D_COUNT) +
              (config.HOURLY_PAUSE * H_COUNT)) * 10)) == 0:
            if MODE == 'd':
                syslog.syslog("Switching to HOURLY")
                MODE = 'h'
                H_COUNT += 1
            else:
                syslog.syslog("Switching to DAILY")
                MODE = 'd'
                D_COUNT += 1

additions to global variable ( lines 61-62)
D_COUNT = 1
H_COUNT = 0

This is working good for me, thanks!
Feb 27 20:55:43 tart python3[3863]: pygame 1.9.6
Feb 27 20:55:43 tart python3[3863]: Hello from the pygame community. https://www.pygame.org/contribute.html
Feb 27 20:55:43 tart python3[3863]: X Display = :0
Feb 27 20:55:43 tart python3[3863]: Framebuffer Size: 1824 x 984
Feb 27 20:55:44 tart systemd[1]: PiWeatherRock.service: Succeeded.
Feb 27 20:55:44 tart systemd[1]: Stopped PiWeatherRock Service.
Feb 27 20:55:44 tart systemd[1]: Started PiWeatherRock Service.
Feb 27 20:55:44 tart sudo[3894]: pam_unix(sudo:session): session closed for user root
Feb 27 20:55:48 tart /weather.py[3901]: X Display = :0
Feb 27 20:55:48 tart /weather.py[3901]: Framebuffer Size: 1824 x 984
Feb 27 20:57:27 tart /weather.py[3901]: Switching to HOURLY
Feb 27 20:59:00 tart /weather.py[3901]: Switching to DAILY
Feb 27 21:00:33 tart /weather.py[3901]: Switching to HOURLY
Feb 27 21:00:34 tart /weather.py[3901]: Switching to info mode
Feb 27 21:02:57 tart /weather.py[3901]: Switching to weather mode


ScrollTo() Method

First question:
I would like to replace the traditional listview with ListViewZero. As an ItemSource I have connected a StringList that is filled dynamically. With every new entry in the string list, I would like to make it visible in the list and scroll the list accordingly in the backend to the new entry. But I'm missing the ScrollTo() method that the standard ListView has. Is there a workaround?
Second-Question
I would also like to use the list view without a fixed height within a scroll view. This worked fine in Xamarin. After the Maui migration, the default list view adjusts the height of the control incorrectly. Can the ListViewZero handle a parent scrollview?

Hi @SE250880
First answer:
There isn't a ScrollTo but you have much finer control because you can TwoWay bind to ScrollOffset
giving you pixel control of the scroll position.
If your ViewModel has this:
private double _listViewScrollOffset;
public double ListViewScrollOffset
{
    get => _listViewScrollOffset;
    set => SetProperty(ref _listViewScrollOffset, value);
}

and your xaml looks like this:
<cz:ListViewZero
    ItemsSource="{Binding SampleListData}"
    ScrollOffset="{Binding ListViewScrollOffset, Mode=TwoWay}"
    ItemHeight="40"
    ...
>

You can then do something like this when you add an item or items to your collection:
// Get the item index from somewhere, e.g. 'SampleListData.Count-1' if it's the end item.
ScrollOffset = 40 * itemIndex;

The next update will have a way of determining more information about the state of the ScrollViewZero, including the number of visible items, the index of the first visible item, the number of 'remaining items' before you run out of items to display, etc.
This will help you position things within the render area, e.g. to scroll so an item is centred or at the top or bottom of the view, as well as allowing lazy-loading for infinite scroll.
Second answer:
I'm not entirely sure I understand the question, so please correct me if I've misunderstood ...
The ListViewZero derives from a ContentView and has the HorizontalOptions and VerticalOptions set to FillAndExpand. You can override the default values yourself to any of the LayoutOptions so hopefully you can get it to size itself as any other control would.
E.g.
<cz:ListViewZero
    VerticalOptions="Start"
    ...
>

If you're trying to get the ListViewZero to behave when inside a vertical ScrollView, that's not going to work because ListViewZero uses a ScrollView and the MAUI documentation says we cannot nest a ScrollView inside a ScrollView.
Having said that, it ought to size itself like any other control, so you may be running into this MAUI bug.

First
Ok, that's a workaround for the moment, but I'm eagerly awaiting the next update that will make setting the scroll position easier.  :-)
Secondly
That doesn't help in my case and the Maui bug seems to be the problem here. I want to position the listview in a scrollview with the height of *. This looks fine until the list content gets to the end of the list. Then the whole control is enlarged to the content of the list. I don't want that, but the size should remain and the list should scroll. This worked fine in Xamarin, but not anymore with MAUI.  :-(


subsys: zbus: publish_stats: message_bus.zbus.publish_stats fails

Describe the bug
The test tests/subsys/zbus/publish_stats/message_bus.zbus.publish_stats fails
Observed for:

nrf52840dk/nrf52840
nrf52dk/nrf52832
nrf54l15dk/nrf54l15/cpuapp
nrf54l15dk/nrf54l15/cpuflpr
nrf5340dk/nrf5340/cpunet
nrf5340dk/nrf5340/cpuapp
nrf5340dk/nrf5340/cpuapp/ns
nrf9160dk/nrf9160
nrf9160dk/nrf9160/ns
nrf54h20dk/nrf54h20/cpuapp
nrf54h20dk/nrf54h20/cpurad
nrf54h20dk/nrf54h20/cpuppr

To Reproduce
Steps to reproduce the behavior:

have nrf9160dk/nrf9160 connected
go to your zephyr dir
call ./scripts/twister -T tests/subsys/zbus/publish_stats -p nrf9160dk/nrf9160 --device-testing --device-serial /dev/ttyACM0 -v --inline-logs  --west-flash="--erase"
See console output with error

Expected behavior
Valid console output
Impact
Not clear
Logs and console output
*** Booting Zephyr OS build v3.7.0-4232-g9b5260de9a31 ***
Running TESTSUITE publish_stats
===================================================================
START - test_channel_metadata

    Assertion failed at zephyr/tests/subsys/zbus/publish_stats/src/main.c:37: publish_stats_test_channel_metadata: 1000 not within zbus_chan_pub_stats_avg_period(&chan) +/- 50

 FAIL - test_channel_metadata in 1.018 seconds
===================================================================
TESTSUITE publish_stats failed.

------ TESTSUITE SUMMARY START ------

SUITE FAIL -   0.00% [publish_stats]: pass = 0, fail = 1, skip = 0, total = 1 duration = 1.018 seconds
 - FAIL - [publish_stats.test_channel_metadata] duration = 1.018 seconds

------ TESTSUITE SUMMARY END ------

===================================================================
RunID: e101656a64ea052518fadcb02f598410
PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Ubuntu 20.04.1 LTS
Toolchain Zephyr SDK 0.16.8
Commit SHA or Version used: v3.7.0-4232-g9b5260de9a31

Additional context
Probably introduced by 865f88c8038d062c5facd7c86152de7b81bc5f77

reproduction also on:

it8xxx2_evb
frdm_k64f
intel_adsp/ace15_mtpm
intel_adsp/ace20_lnl
up_squared
npcx9m6f_evb
intel_ish_5_4_1
mec15xxevb_assy6853
mec172xevb_assy6906

Can you check if this PR fixes the issue? #79962

Can you check if this PR fixes the issue? #79962

LGTM and works for nrf platforms

tests/subsys/zbus/publish_stats/message_bus.zbus.publish_stats

I checked this fix on up_squared and it8xxx2_evb.
Test pass


Inference time issue

Thanks for quick reply!
I tried to change compiler which supports std:regex such as gcc-4.9 or clang-3.5 & libcxx.
But the polly.py seems not to support gcc-4.9.
(I cannot find gcc-4-9 in the list when I type polly.py --help)
In the case of libcxx toolchain, I failed to build with some error messages. Here is log file.
Anyway, my first goal is to compare running time to piotr's matlab implementation.
I commented cxxopts things in acf.cpp and measure inference time using gettimeofday function.
Even though the inference time of the classifier heavily depends on the image content and casc thershold, somthings are wrong.
It takes 54ms for lena512color.png using drishti_face_gray_80x80.cpb.
(As you know, ~100ms in piotr's MATLAB code for 640x480 image)
I expect <1ms with my GPU (Titan X Pascal).
I think, I turn on the flag to use GPU.
https://github.com/elucideye/acf/blob/17c26894c8d597bb5a33f816167f16d5abe4fe67/CMakeLists.txt#L91
How about the inference time on your machine?

But the polly.py seems not to support gcc-4.9.

In the case of libcxx toolchain, I failed to build with some error messages. Here is log file.

I will try adding libcxx to the CI tests: https://github.com/elucideye/acf/pull/14

It takes 54ms for lena512color.png using drishti_face_gray_80x80.cpb. (As you know, ~100ms in piotr's MATLAB code for 640x480 image).  I expect <1ms with my GPU (Titan X Pascal).

The console app doesn't currently use the OpenGL ES 2.0 shader acceleration, so I'm sure you are running a CPU only benchmark.  I recently migrated this stuff from drishti for general purpose use and improvements, and it will be added to the Hunter package manger once it is cleaned up a little more.  I originally needed this for mobile platforms, so OpenGL ES 2.0 was the lowest common denominator that could support both iOS and Android platforms.  The main drawback with this approach is the 8 bit channel output limitation (it can be improved with 4x8 -> 32 bit packing).  Caveat: Due the the above mentioned limitation, the GLSL output is currently only an approximation of the CPU floating point output, and it needs to be improved (there will be a measurable performance hit).  For desktop use, it is probably better to write it in OpenCL or something higher level that doesn't have these limitations.  (I recently came across Halide, which seems like an excellent path for cross platform optimization, but I currently have no experience with it.)
The GLSL code is all in this file https://github.com/elucideye/acf/blob/master/src/lib/acf/GPUACF.h, which is currently separate from the ACF detection class.  To use that class, you will need to manage your own OpenGL context.  It uses https://github.com/hunter-packages/ogles_gpgpu to manage a shader pipeline that computes the features.  The expensive part on mobile platforms is the GPU->CPU transfer, so one frame of latency is added to the pipeline, such that ACF pyramids can be computed on the GPU for frame N ("for free"), and they are available for processing at time N+1 with no added CPU cost.   In this workflow, the precomputed ACF pyramid is passed in for detection in place of the RGB image.  The face detection/search on the precomputed pyramids then runs in a few milliseconds on an iPhone 7.  For pedestrian detection the extra frame of latency might not be suitable.  The SDK call is shown here:
https://github.com/elucideye/acf/blob/17c26894c8d597bb5a33f816167f16d5abe4fe67/src/lib/acf/ACF.h#L392
There is a small unit test that illustrates what the basic process would look like: 1) compute acf::Detector::Pyramid objects on the GPU and then; 2) feed them to acf::Detector:
https://github.com/elucideye/acf/blob/17c26894c8d597bb5a33f816167f16d5abe4fe67/src/lib/acf/ut/test-acf.cpp#L444-L464
The above test uses the Hunter aglet package to manage the OpenGL context (just glfw for PC builds).
That test could be used for some initial benchmarks, and perhaps it could be added to the console application for additional testing.  I'll try to take a look in the next few days, unless you want to try it sooner.

As a temporary GPU benchmark, I've added a timer class that can be enabled w/ an option in the unit test.  The is currently sitting in this PR: https://github.com/elucideye/acf/pull/16
See define ACF_LOG_GPU_TIME 1 here: https://github.com/elucideye/acf/pull/16/commits/0b95cb712648ea92a0958dfb82927d503d549429#r144582514
That will print the GPGPU pyramid compute (shaders, read and "fill")
ACF::fill(): 512 0.00225127

As well as the detection time
 acf::Detector::operator():0.00207684

On my desktop these each take about 2 milliseconds (2+2=4 ms) with a GEFORCE GTX TITAN X.   The detection time is comparable on my 2013 MacBook, but the fill operation is more like 20 ms (nearly all of that is spent in the texture read).  Actually if we use the PBO reads in ogles_gpgpu in the OpenGL ES 3.0 compatibility mode (or desktop) that should be faster.  I'll add an option for it.
This isn't a proper benchmark, but it can provide some info in the short term.
1: Test timeout computed to be: 9.99988e+06
1: [==========] Running 7 tests from 1 test case.
1: [----------] Global test environment set-up.
1: [----------] 7 tests from ACFTest
1: [ RUN      ] ACFTest.ACFSerializeCereal
1: [       OK ] ACFTest.ACFSerializeCereal (334 ms)
1: [ RUN      ] ACFTest.ACFDetectionCPUMat
1: [       OK ] ACFTest.ACFDetectionCPUMat (106 ms)
1: [ RUN      ] ACFTest.ACFDetectionCPUMatP
1: [       OK ] ACFTest.ACFDetectionCPUMatP (84 ms)
1: [ RUN      ] ACFTest.ACFChannelsCPU
1: [       OK ] ACFTest.ACFChannelsCPU (89 ms)
1: [ RUN      ] ACFTest.ACFPyramidCPU
1: [       OK ] ACFTest.ACFPyramidCPU (101 ms)
1: [ RUN      ] ACFTest.ACFPyramidGPU10
1: ACF::fill(): 512 0.00246045
1: [       OK ] ACFTest.ACFPyramidGPU10 (305 ms)
1: [ RUN      ] ACFTest.ACFDetectionGPU10
1: ACF::fill(): 512 0.00225127
1: acf::Detector::operator():0.00207684
1: [       OK ] ACFTest.ACFDetectionGPU10 (153 ms)
1: [----------] 7 tests from ACFTest (1173 ms total)
1:
1: [----------] Global test environment tear-down
1: [==========] 7 tests from 1 test case ran. (1173 ms total)
1: [  PASSED  ] 7 tests.
1/1 Test #1: ACFTest ..........................   Passed    1.19 sec

@SoonminHwang : I hope this answers your question.  I'm going to close this for now.  Since one of the strong advantages of this packages is size + speed, it might make sense to add some targeted google benchmarks.


There are 10 critical vulnerabilities from old dependencies

mooch@basement2:~/p/electronWebGCS$ npm audit
# npm audit report

minimatch  <3.0.5
Severity: high
minimatch ReDoS vulnerability - https://github.com/advisories/GHSA-f8q6-p94x-37v3
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/dir-compare/node_modules/minimatch
  dir-compare  <=2.4.0
  Depends on vulnerable versions of minimatch
  node_modules/dir-compare
    @electron/universal  1.0.1 - 1.3.3
    Depends on vulnerable versions of dir-compare
    node_modules/@electron/universal
      app-builder-lib  22.10.4 - 24.0.0-alpha.13
      Depends on vulnerable versions of @electron/universal
      node_modules/app-builder-lib
        dmg-builder  22.10.4 - 24.0.0-alpha.13
        Depends on vulnerable versions of app-builder-lib
        node_modules/dmg-builder
          electron-builder  19.25.0 || >=22.10.4
          Depends on vulnerable versions of app-builder-lib
          Depends on vulnerable versions of dmg-builder
          Depends on vulnerable versions of simple-update-notifier
          node_modules/electron-builder

minimist  <=0.2.3 || 1.0.0 - 1.2.5
Severity: critical
Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h
Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h
Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m
Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/@mapbox/togeojson/node_modules/minimist
node_modules/optimist/node_modules/minimist
node_modules/static-module/node_modules/minimist
node_modules/togeojson/node_modules/minimist
node_modules/wellknown/node_modules/minimist
  @mapbox/togeojson  *
  Depends on vulnerable versions of minimist
  Depends on vulnerable versions of xmldom
  node_modules/@mapbox/togeojson
  optimist  >=0.6.0
  Depends on vulnerable versions of minimist
  node_modules/optimist
    csv2geojson  3.8.0 - 5.1.1
    Depends on vulnerable versions of optimist
    node_modules/csv2geojson
  quote-stream  <=1.0.0
  Depends on vulnerable versions of minimist
  node_modules/static-module/node_modules/quote-stream
  togeojson  >=0.4.0
  Depends on vulnerable versions of minimist
  Depends on vulnerable versions of xmldom
  node_modules/togeojson
    leaflet-omnivore  >=0.3.1
    Depends on vulnerable versions of brfs
    Depends on vulnerable versions of csv2geojson
    Depends on vulnerable versions of togeojson
    Depends on vulnerable versions of wellknown
    node_modules/leaflet-omnivore
  wellknown  0.3.2 - 0.4.2
  Depends on vulnerable versions of minimist
  node_modules/wellknown

protobufjs  6.10.0 - 7.2.3
Severity: high
protobufjs Prototype Pollution vulnerability - https://github.com/advisories/GHSA-h755-8qp9-cq85
fix available via `npm audit fix`
node_modules/protobufjs

semver  <=5.7.1 || 6.0.0 - 6.3.0 || 7.0.0 - 7.5.1
Severity: moderate
semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw
semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw
semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/@babel/core/node_modules/semver
node_modules/@babel/helper-compilation-targets/node_modules/semver
node_modules/@babel/helper-define-polyfill-provider/node_modules/semver
node_modules/@babel/preset-env/node_modules/semver
node_modules/@electron/get/node_modules/semver
node_modules/babel-plugin-polyfill-corejs2/node_modules/semver
node_modules/eslint-config-airbnb-base/node_modules/semver
node_modules/eslint-import-resolver-webpack/node_modules/semver
node_modules/eslint-plugin-import/node_modules/semver
node_modules/eslint-plugin-jsx-a11y/node_modules/semver
node_modules/eslint-plugin-react/node_modules/semver
node_modules/istanbul-lib-instrument/node_modules/semver
node_modules/make-dir/node_modules/semver
node_modules/semver
node_modules/simple-update-notifier/node_modules/semver
  eslint-plugin-compat  >=3.6.0-0
  Depends on vulnerable versions of semver
  node_modules/eslint-plugin-compat
    eslint-config-erb  >=1.0.0-0
    Depends on vulnerable versions of eslint-plugin-compat
    node_modules/eslint-config-erb
  simple-update-notifier  1.0.7 - 1.1.0
  Depends on vulnerable versions of semver
  node_modules/simple-update-notifier

static-eval  <=2.0.1
Severity: high
Sandbox Breakout / Arbitrary Code Execution in static-eval - https://github.com/advisories/GHSA-x9hc-rw35-f44h
Sandbox Breakout / Arbitrary Code Execution in static-eval - https://github.com/advisories/GHSA-5mjw-6jrh-hvfq
fix available via `npm audit fix`
node_modules/static-eval
  static-module  <=1.5.0
  Depends on vulnerable versions of quote-stream
  Depends on vulnerable versions of static-eval
  node_modules/static-module
    brfs  1.1.0 - 1.4.3
    Depends on vulnerable versions of static-module
    node_modules/brfs

tough-cookie  <4.1.3
Severity: moderate
tough-cookie Prototype Pollution vulnerability - https://github.com/advisories/GHSA-72xf-g2v4-qvf3
fix available via `npm audit fix`
node_modules/tough-cookie

word-wrap  *
Severity: moderate
word-wrap vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-j8xg-fqg3-53r7
fix available via `npm audit fix`
node_modules/word-wrap
  optionator  0.8.3 - 0.9.1
  Depends on vulnerable versions of word-wrap
  node_modules/escodegen/node_modules/optionator
  node_modules/optionator

xmldom  *
Severity: critical
Misinterpretation of malicious XML input - https://github.com/advisories/GHSA-5fg8-2547-mr8q
Misinterpretation of malicious XML input - https://github.com/advisories/GHSA-h6q6-9hqw-rwfv
xmldom allows multiple root nodes in a DOM - https://github.com/advisories/GHSA-crh6-fp67-6883
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/xmldom

26 vulnerabilities (8 moderate, 8 high, 10 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

too many vulnerabilities

Are these fixed with the latest PR?

I don't believe so. It seems like upgrading electron deps will fix a good amount of these. Been pretty busy at $dayjob last couple of weeks but i will probably tackle this soon


vim-airline Not showing fancy status bar

In the screenshots the status bars look like this:

But i have:

Archlinux, vim 7.4.663

@OscarOrSomething, which colorscheme do you use?

Desert.

same issue

@idvoretskyi
fixed.
just 'set t_Co=256' in vim

Please, close this issue.

Sorry.


Omit build number from version in changelog

In flutter projects, it is usual to increase the build number when increasing the version.
This is necessary because the google playstore will only recognize build number versioning and regards everything else as flavour.
Build numbers are therefore basically a count of how many versions have been released, but arent very useful to include with the actual version number.
My pubspec therefore does have a build number, but it is completely irrelevant to the changelog and its readers.
When I use
cider release

my build number is also included in the Changelog, which I see as undesirable.
I am not sure what the best course of action would be to acommodate for this usecase in the package.
But I would be delighted if it would be possible to resolve this in some way.
Maybe the command could provide an option for not including the build number when transfering the version.
Perhaps it would be useful in general to be able to specify the behaviour for how build numbers are treated by default in the config file, as right now I will always have to use --bump-build together with cider bump.

closing this as I realized I need the build number to automatically generate android changelogs and therefore omitting it wouldnt be useful to me anymore.


[CMake] macOS: Find DebugSymbols.framework inside the SDK

It's always going to be at / on disk, but that's not what we should be linking against!

@swift-ci Please test

Do you know why this change was required now.  There haven't been headers for DebugSymbols in /System for ages now, and lldb has always linked against this...

@dcci: Oh, right, of course. I'll do it there.
@jimingham: It actually isn't required; like I was saying on Apple-internal chat (before chat went down) I had a bad Xcode install. But it's more correct regardless.

https://reviews.llvm.org/D59831


Remove unnecessary Flush

When the body has been written to the headers are flushed so it doesn't need a second flush at end; so set _requestProcessingStatus = RequestProcessingStatus.HeadersFlushed
Currently handled for _autoChunk but not for ContentLength

/cc @jkotalik @davidfowl

Probably can use the same BufferWriter for first write and headers https://github.com/aspnet/AspNetCore/issues/7429


time to deprecate zcl_excel_aunit?

Hi,
I think its time to deprecate https://github.com/sapmentors/abap2xlsx/blob/master/src/zcl_excel_aunit.clas.abap
I guess it was needed on 700, to differ between CL_AUNIT_ASSERT and CL_ABAP_UNIT_ASSERT
CL_AUNIT_ASSERT is long time obsolete and CL_ABAP_UNIT_ASSERT exits on all(?) versions 702 and above
        new  type tv_clsname value 'CL_ABAP_UNIT_ASSERT',
        old  type tv_clsname value 'CL_AUNIT_ASSERT',

Do we simply replace all references to zcl_excel_aunit with cl_abap_unit_assert? If so, I can do that.

in my opinion, yes

Please check if this PR is sufficient. Thanks.


Folder for 'collecting logs' documents

Signed-off-by: Jorma Virkkunen<EMAIL_ADDRESS>

I would prefer having the "moving files around" and "changing contents of the files" type of changes in separate commits. It would make reviewing easier. Now git doesn't realize that one of the files was moved, and shows instead that one file was deleted and another was added. If the commits were separated it would most likely show the actual differences.

This PR was reset. This improved one contains just the changes needed for the new folder structure: the new parent folder "Collecting Logs" and its README.md, and the two child subfolders Collecting_Logs_with_Logcat & Collecting_oFono_Logs. The headers of the READMEs of those subfolders were updated, of course. No other changes in them, yet.

This PR was reset. This improved one contains just the changes needed for the new folder structure: the new parent folder "Collecting Logs" and its README.md, and the two child subfolders Collecting_Logs_with_Logcat & Collecting_oFono_Logs. The headers of the READMEs of those subfolders were updated, of course. No other changes in them, yet.

These look fine to me. Are you planning on reintroducing the other changes as a separate commit in this PR, or should I just merge this and wait for another PR for the other changes?

This PR was reset. This improved one contains just the changes needed for the new folder structure: the new parent folder "Collecting Logs" and its README.md, and the two child subfolders Collecting_Logs_with_Logcat & Collecting_oFono_Logs. The headers of the READMEs of those subfolders were updated, of course. No other changes in them, yet.

These look fine to me. Are you planning on reintroducing the other changes as a separate commit in this PR, or should I just merge this and wait for another PR for the other changes?

I would like to make one more commit for this PR to get the two existing READMEs fixed. The other log collection work (more documents) I would deliver in other PRs.


Added macro support, compatibility

Added extension_types support
Added compat table generation
Changed Chromium acknowledgements
Added calls to xref macro "wexref"
Added tags to JSON metadata
Added calls to insert sidebar using WebExtensionSidebar macro

The columns in the compat table don't seem like the right ones to me. Can we just include Firefox, Chrome, and Edge? Those are the only ones likely to support this API in the future.
Also, I think we're supposed to have more tags. https://developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Write_an_API_reference#Tagging

The columns in the compat table don't seem like the right ones to me.
Can we just include Firefox, Chrome, and Edge? Those are the only
ones likely to support this API in the future.

I just copied the table from https://developer.mozilla.org/en-US/docs/MDN/Contribute/Structures/Compatibility_tables, but I agree, there's no point in including browsers that will never support this.
Which mobile browsers do we care about?

Also, I think we're supposed to have more tags.
https://developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Write_an_API_reference#Tagging

OK, I'll add those.


Added model parameter

Added the model parameter to the streaming sample.
Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

There is an ongoing discussion about whether this change should be introduced or not. Once that discussion is resolved, we will either try to merge this branch, or just delete it.

@happyhuman any updates here?

Stale. Closing.


[Question]: How do Pipe Pressurizers technically work?

I am building a large chests network to be able to have a "global" storage center that retrieves items from all my diverse farms/generators across the map and lets me access my global storage from terminals in connected locations.
To make this, you would naturally want to use pipe pressurizers to speed up the transport process. However, I have a doubt about how they work.
Do they work like vanilla powered rails (only speeding up some adjacent pipes) or do they increase the speed of the whole network?
Are they stackable? What is the speed multiplier? Is there any sort of effectiveness decay when using multiple pressurizers? Is there a travelling speed limit for items?
If they speed up the whole pipe network, I could simply build a "pressurizing plant" with all the pressurizers connected there, which would also make it easier to supply power to them.

Pipe pressurizers increase the speed for all items in the attached pipe network.
They are not stackable, but their effect stacks with speed modules. This means the maximum speed for a pipe item is a pressurized network, plus being extracted by a pipe with a tier three speed module.


Combination of either and delay causes RangeError: Maximum call stack size exceeded

test('do not make infinite loop with combination of delay', async () => {
  const $isMobile = createStore(true);

  const clickChooseDateButton = createEvent();
  const forceDepartDateChoice = createEvent();

  delay({
    source: clickChooseDateButton,
    timeout: either({ filter: $isMobile, then: 250, other: 0 }),
    target: forceDepartDateChoice,
  });

  const scope = fork();

  await allSettled(clickChooseDateButton, { scope });
});

I was wrong, without delay it is same same 🤗
test('do not make infinite loop', async () => {
  const $isMobile = createStore(true);

  either({ filter: $isMobile, then: 250, other: 0 });

  const scope = fork();

  await allSettled($isMobile, { scope, params: false });
});


UI Silently Logs Users Out

anselr
https://jira.jpl.nasa.gov/browse/AERIEQS-386
Moderate
Often while working on plans in the Aerie UI, a user will be logged out due to inactivity. When this happens, it is not reflected until the user refreshes the page, which can lead to confusing errors. For example, if a user tries to upload a model jar after such a timeout, the upload fails with an error message in the UI about an int being received as null or something implicit like that.
Given how long it takes to run simulations, it would be good to extend the timeout period by quite a lot (or perhaps indefinitely), so as to avoid the situation where a user leaves a long-running sim going in the background, only to return to it later to find that while the simulation has finished they can no longer interact with the UI and if they refresh, they lose the sim results.
Additionally, it would be preferable to have this logout be made much more obvious in the UI and not require the user to refresh.

This should be fixed via https://github.com/NASA-AMMOS/aerie-ui/pull/729


Vevo: attempting download a specific video a playlist, always downloads the first video of the list

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.06.12. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.06.12

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl --ignore-config -v https://www.vevo.com/watch/playlist/d1aa61ff-1f40-466f-b527-8277de057768?index=4
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--ignore-config', '-v', 'https://www.vevo.com/watch/playlist/d1aa61ff-1f40-466f-b527-8277de057768?index=4']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] youtube-dl version 2017.06.12
[debug] Python version 3.6.1 - Windows-10-10.0.15063-SP0
[debug] exe versions: ffmpeg N-83454-g3aae1ef, ffprobe N-83454-g3aae1ef
[debug] Proxy map: {}
[VevoPlaylist] d1aa61ff-1f40-466f-b527-8277de057768: Downloading webpage
[Vevo] Retrieving oauth token
[Vevo] USLV49400152: Downloading api video info
[Vevo] USLV49400152: Downloading video versions info
[Vevo] USLV49400152: Downloading amazon MPD information
[Vevo] USLV49400152: Downloading akamai MPD information
[Vevo] USLV49400152: Downloading amazon m3u8 information
[Vevo] USLV49400152: Downloading akamai m3u8 information
[debug] Invoking downloader on 'http://mpd-aws.vevo.com/v4/mpd/2015/12/USLV49400152/50199210-1804-47c6-9eab-b969e0b91a7e/uslv49400152_5200k_1920x1080_h264_5200_aac_128_track1_dashinit.mp4'
[download] Resuming download at byte 17335634
[download] Destination: TLC - Waterfalls-USLV49400152.fdash-amazon-8.mp4
[download] 100% of 164.98MiB in 04:40
[debug] Invoking downloader on 'http://mpd-aws.vevo.com/v4/mpd/2015/12/USLV49400152/50199210-1804-47c6-9eab-b969e0b91a7e/uslv49400152_128k_0x0__0_aac_128_dashinit.mp4'
[download] Destination: TLC - Waterfalls-USLV49400152.fdash-amazon-11.m4a
[download] 100% of 4.86MiB in 00:09
[ffmpeg] Merging formats into "TLC - Waterfalls-USLV49400152.mp4"
[debug] ffmpeg command line: ffmpeg -y -i 'file:TLC - Waterfalls-USLV49400152.fdash-amazon-8.mp4' -i 'file:TLC - Waterfalls-USLV49400152.fdash-amazon-11.m4a' -c copy -map 0:v:0 -map 1:a:0 'file:TLC - Waterfalls-USLV49400152.temp.mp4'
Deleting original file TLC - Waterfalls-USLV49400152.fdash-amazon-8.mp4 (pass -k to keep)
Deleting original file TLC - Waterfalls-USLV49400152.fdash-amazon-11.m4a (pass -k to keep)

Description of your issue, suggested solution and other information
On Vevo, individual videos within a playlist can be accessed by index number.
For Playlist: https://www.vevo.com/watch/playlist/d1aa61ff-1f40-466f-b527-8277de057768
3rd Video of playlist: https://www.vevo.com/watch/playlist/d1aa61ff-1f40-466f-b527-8277de057768?index=2
The youtube-dl, any attempt to download a video with index > 0, results in the downloading the first (index=0) video of the playlist.
In the example pasted above, the fourth video should have been download, instead "Waterfalls" (index=0) is downloaded.

I filed previously filed another issue #13394 regarding failure to download a Vevo playlist.
I am noting this in case it is same root cause - that the playlist is not processed correctly, so the first video is always downloaded


Bug using font-family with number

Describe the bug
I imported fonts from the Google Fonts API and some of them have numbers in their names, such as: Exo 2, Source Sans 3, Slabo 27px, etc. In this case, when selecting one of these fonts it is not applied.
To Reproduce
You can use the custom fonts option to add the above mentioned fonts

The fonts appears in the font menu, but when I click on one of them nothing happens.

But if I add a font without a number and click in it, it is applied normally

Version 2.46.1 has been deploied.
Thank you.

Wow, it was fast!
Thank you.


Minio GCS Fix - Added extra options to pass in service account json

Addresses issue https://github.com/helm/charts/issues/5911

@SubatomicHero is there any possibility to get these modifications done ? I can push it to the repo if you don't have the time


Interchain wallet

Hi,
Does this now support interchain wallet ?
If yes can somebody provide how to add chains, select/switch chains ?
Thank you

Go to the official page to initiate a chat with live support agent on the chat button to report this for review and for assistance via LIVE CHAT

@vinodhum visit the official page to start a chat with an agent on a live chat support to report this for review and for further assessment via Support


[Bug] Go back in browser not work even specifying the pushIn property

update several params using onChangeUrlQueryParams the pushIn property doesn't work any more

@Hearen did you manage to fix this somehow?


Create a CONTRIBUTING.MD doc

We need a version of our previous CONTRIBUTING.md file for each UpWiSE project.

i would like to take this one, assign me this issue

Hi @Naumantamboli, I have assigned this issue to you.
As a reference, this is the previous document that we had in an earlier group: https://github.com/klmansel/WWCodeGreenville/blob/master/CONTRIBUTING.md
I would like to see a Getting Started section and a link to the UpWiSE Community Policies.  Any other ideas or additions that you have would be welcome.

Hello @Naumantamboli, please note that if you are working on this issue as part of Hacktoberfest 2024, we will be wrapping up PR reviews in this repository in the next 24 hours.  You're welcome to work on this after then, but it won't be eligible to be counted as part of Hacktoberfest.


When opening a file, the application should start in a paused state

If not by default, then optionally.
I want this because some of my shaders take around ¼ to ½ second to generate a frame, which is OK for my intended use case.
Even if I tell SHADERed to render the preview at 1FPS, this still causes my PC to struggle.

@ctrlcctrlv added!
I've also made some changes on how the "paused" state works. Now the preview window will be updated when user recompiles a shader or resizes preview window even if the preview is paused. In my opinion this is how it should work. This way user can modify the shader when paused on a specific frame to see the result, avoid unnecessary rendering (only render on a change), etc...


HADOOP-18935. coalesce AWS S3 client proxy settings

coalesce proxy settings between the two clients
only set async proxy settings if non-empty

How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
47m 28s

trunk passed

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
0m 34s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 31s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 27s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 35s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 12s

trunk passed

+1 :green_heart:
shadedclient
36m 49s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 23s
/patch-mvninstall-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch failed.

-1 :x:
compile
0m 25s
/patch-compile-hadoop-tools_hadoop-aws-jdkUbuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.txt
hadoop-aws in the patch failed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.

-1 :x:
javac
0m 25s
/patch-compile-hadoop-tools_hadoop-aws-jdkUbuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.txt
hadoop-aws in the patch failed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.

-1 :x:
compile
0m 21s
/patch-compile-hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-aws in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

-1 :x:
javac
0m 21s
/patch-compile-hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-aws in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 21s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 5 new + 1 unchanged - 0 fixed = 6 total (was 1)

-1 :x:
mvnsite
0m 26s
/patch-mvnsite-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch failed.

+1 :green_heart:
javadoc
0m 17s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch failed.

+1 :green_heart:
shadedclient
38m  5s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 28s
/patch-unit-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch failed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

134m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6177/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6177

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux cafaf1f7ad92 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8e181fb30084aeb312b791d834669d3be47424eb

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6177/1/testReport/

Max. process+thread count
744 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6177/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Binderator improvements metadata files and dependency reporting

Added

metadata downloads

javadoc downloads

MavenNet javadoc support

PR https://github.com/Redth/MavenNet/pull/6

formatted output for missing artifacts

summary (number of exceptions - missing artifacts)

details about missing artifacts with suggestion code snippet to be added to config.json
Dependency errors : 1
1
    System.Exception:
No matching artifact config found for:
		    com.google.firebase.firebase-appcheck-interop:16.0.0-beta01
to satisfy dependency of:
		    com.google.firebase.firebase-database:20.0.0

    Please add following json snippet to config.json:

      {
        "groupId": "com.google.firebase",
        "artifactId": "firebase-appcheck-interop",
        "version": "16.0.0-beta01",
        "nugetVersion": "CHECK THIS",
        "nugetId": "CHECK THIS",
        "dependencyOnly": true/false
      }

NOTE: stable artifact depending on prerelease

NOTE: MavenNet 2.3.0 not published yet


Add kube version flag

Add --kube-version flag into helmfile template.
It overrides kubeVersion in helmfile.yaml.
resolve #722

@FeLvi-zzz did only template subcommand need this flag?

yes, I suppose that other subcommands do not need --kube-version flag because they connect a k8s cluster and be able to get its version.

Hey @FeLvi-zzz, you made a good point!
It's true most of helmfile and helm commands don't take --kube-version due to the reason you mentioned.
However, not only helm template but also helm-diff takes another similar flag --api-versions that can potentially be obtained from the target cluster. I think that's why we already call appendApiVersionsFlags in the helmfile-diff code.
HOWEVER, I realized that helm-diff lacks support for --kube-version! So it turns out there's an existing bug that when you set kubeVersion in helmfile.yaml, helm-diff run via helmfile-diff would fail due to an invalid flag error. We need to enhance helm-diff for that later.
Until then, the way you did it in the helmfile-diff code, flags = st.appendApiVersionsFlags(flags, release, ""), looks correct!

Hey @FeLvi-zzz, you made a good point!
It's true most of helmfile and helm commands don't take --kube-version due to the reason you mentioned.
However, not only helm template but also helm-diff takes another similar flag --api-versions where corresponding values can potentially be obtained from the target cluster. I think that's why we already call appendApiVersionsFlags in the helmfile-diff code.
HOWEVER, I realized that helm-diff lacks support for --kube-version! So it turns out there's an existing bug that when you set kubeVersion in helmfile.yaml, helm-diff run via helmfile-diff would fail due to an invalid flag error. We need to enhance helm-diff for that later.
Until then, the way you did it in the helmfile-diff code, flags = st.appendApiVersionsFlags(flags, release, ""), looks correct!

@FeLvi-zzz @mumoshu  I think that we can add some TODO comments for flags = st.appendApiVersionsFlags(flags, release, "").

@FeLvi-zzz please add required comments for flags = st.appendApiVersionsFlags(flags, release, "").

@yxxhero
added the comment!


qa_crowbarsetup.sh: Create /etc/crowbar/repos.yml for Cloud 6

For Cloud 6 (after M6), we don't specify custom repositories in the
provisioner barclamp, but in /etc/crowbar/repos.yml.
This is needed for the changes in https://github.com/crowbar/crowbar-core/pull/102

cc @MaximilianMeister

haven't tested but code looks good
:+1:

code looks good. My only concern is that we might want to add some nicer way for this for users and rather test that.

@bmwiedemann at the moment, there's no nicer way except for yast (see https://github.com/yast/yast-crowbar/pull/35). But I agree that if/once we add some API for this, we should use the API.

:+1:  lgtm

Just checked in the current gate job: file was created correctly, and provisioner proposal didn't have the autoyast repo. It also deploys openstack, so I think we're good.


Iteration Path of Sub-task in not moving to azure

Hi,
Whenever I try to export data from Jira-export I am always getting the iteration path as null only for the Sub-task workitem even though data is present in my Jira account I am searching whole code But not able to get it please help me as soon as possible.
Here I am putting Json file for one Sub-task workitem for your reference
{
"Type": "Task",
"OriginId": "PROJ-15",
"WiId": -1,
"Revisions": [
{
"Author"<EMAIL_ADDRESS>"Time": "2021-03-03T12:24:27.944+05:30",
"Index": 0,
"Fields": [
{
"ReferenceName": "System.Title",
"Value": "Task in task"
},
{
"ReferenceName": "System.IterationPath",
"Value": null
},
{
"ReferenceName": "Microsoft.VSTS.Common.Priority",
"Value": "3"
},
{
"ReferenceName": "System.State",
"Value": "To Do"
}
],
"Links": [
{
"Change": 0,
"TargetOriginId": "PROJ-14",
"TargetWiId": 0,
"WiType": "System.LinkTypes.Hierarchy-Reverse"
}
],
"Attachments": [],
"AttachmentReferences": false
},
{
"Author"<EMAIL_ADDRESS>"Time": "2021-03-03T12:24:28.358+05:30",
"Index": 1,
"Fields": [],
"Links": [
{
"Change": 1,
"TargetOriginId": "PROJ-14",
"TargetWiId": 0,
"WiType": "System.LinkTypes.Hierarchy-Reverse"
},
{
"Change": 0,
"TargetOriginId": "PROJ-14",
"TargetWiId": 0,
"WiType": "System.LinkTypes.Hierarchy-Reverse"
}
],
"Attachments": [],
"AttachmentReferences": false
},
{
"Author"<EMAIL_ADDRESS>"Time": "2021-03-03T12:26:41.346+05:30",
"Index": 2,
"Fields": [
{
"ReferenceName": "System.AssignedTo",
"Value"<EMAIL_ADDRESS>}
],
"Links": [],
"Attachments": [],
"AttachmentReferences": false
}
]
}
AB#5935

Hi Ayush!
Paste your config file here and I will try and help you.
Since this is an old issue, I will close it due to inactivity. Feel free to open again if you require further help.

Thankyou so much but i am able to complete that task.
On Mon, 6 Dec, 2021, 6:08 pm Alexander Hjelm, @.***>
wrote:

Hi Ayush!
Paste your config file here and I will try and help you.
Since this is an old issue, I will close it due to inactivity. Feel free
to open again if you require further help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/solidify/jira-azuredevops-migrator/issues/335#issuecomment-986737892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMOVDDVZQC5M5OQTOVKJCLUPSVELANCNFSM4YZAESHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Ok, no worries!
And apologies for the long inactivity. We have had a change of staff, during which no one was monitoring issues.

Hi Ayush. Could you please tell on how you were able to fix this issue. i am facing the same problem.


Error: invalid json response body at https://disease.sh/v2/historical/Brazil reason: Unexpected token < in JSON at position 0

Same error using the node-api HERE
Belgium is going well:
_https://disease.sh/v2/historical/Belgium_
Response header: content-type: application/json; charset=utf-8
Brazil is throwing this error:
_https://disease.sh/v2/historical/Brazil_
Response header: content-type: text/html; charset=utf-8

Error: invalid json response body at https://disease.sh/v2/historical/Brazil reason: Unexpected token < in JSON at position 0

https://github.com/NovelCOVID/API/issues/575#issuecomment-617827167


Fix publish release use of internal package

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>

🇬🇷 lol


⚠ Cioos National CKAN Sitemap has degraded performance

In 4fe9a4b, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 10164 ms

Resolved: Cioos National CKAN Sitemap performance has improved in 87986e5 after 5 minutes.


WooCommerce Cart Not Emptying

Hi, came across this issue on my Timber site, and managed to reproduce it in a clean setup. Can supply a repo if it would assist. Haven't been able to investigate further yet what the conflict is (suspecting some filter priority issue possibly), but this only happens on Timber themes and not default WP themes.
Expected behavior
The item is removed from the cart after checking out a $0 product, or product with 100% discount applied.
Actual behavior
The item is not removed from the cart after checking out a $0 product or product with 100% discount applied.
Steps to reproduce behavior

Add item to the cart
Apply coupon of 100% discount
Checkout
Check cart to see if product is still there

What version of WordPress, PHP and Timber are you using?
Wordpress 4.9.8
Timber 1.8.3
WooCommerce 3.5.1
Timber Starter Theme (https://github.com/timber/starter-theme)
PHP 7.1.23
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
Upgraded to latest version via Wordpress Dashboard

Stale issue, closing


rc2nix doesn't see sections with colons

My kdeglobals contains
[Colors:View]
BackgroundNormal=#000000

rc2nix skips that section.

The reason I made rc2nix skip colors and theme-related sections was because I use different themes on my different computers.  I also wanted to provide a different way to deal with theme settings (but I haven't gotten around to that yet).
That said, this should probably be controlled with a flag to rc2nix.
I'm happy to accept patches to that effect.

This is a bit of bikeshedding, but imho rc2nix should not ignore any section (tho it can for now until the highlevel things are done).
Primary reasoning for me is here that i expect rc2nix to create a complete snapshot of the current configuration, that can then be stuffed into the low level config to replicate the state (almost) exactly.

@HeapUnderfl0w I agree with you.
The biggest challenge right now is that KDE stores a lot of state information in configuration files, which I believe they are addressing in a future release.
As an example, if you poke around, you'll see window locations, monitor IDs, and all sorts of stuff that won't work on another computer with a different resolution.  You'd end up with windows appearing off screen and whatnot.
The rc2nix script is really stupid right now and I don't currently have any free time to work on it.  If anyone wants to help out that would be great.


Fix/small files refactor a

To this point all of the components files, and the following pages have had the final refactor done
About
CoverCropExplorer
CropSelector
CropSidebar
Feedback
Footer
GoalSelector
Header

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.


Tag created AMIs

possibly have a 'createdby' tag but certainly allow users to define tags via config
CLI example (but guessing I'll use the SDK)
aws ec2 create-tags --resources ami-78a54011 --tags Key=Stack,Value=BaseNodeJsServer

See Tag Example
https://www.packer.io/docs/builders/amazon-ebs.html

Also Tag an AMI's associated snapshot


Stripe.PaymentMethod.Card.brand not typescript exported

Hi there,
I am looking to typesafe a dictionary and would like to find a way to import the possible brand names of cards from stripe-js.
Can you help me with this?
Thank you,
Teo

Hi @teo029 👋 ,
You can find the list of the possible brand values returned for the Card object in the Stripe API docs:

Card brand. Can be American Express, Diners Club, Discover, JCB, MasterCard, UnionPay, Visa, or Unknown.

Other resources on this topic include Card brand choice and Supported card brands. Hope that helps!
Closing out for now.


C_CPP : Double Threaded Binary Tree

Description
Documentation on double threaded binary tree
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


Introduce guide to testing in Go

Newcomer-friendly introduction to testing in Go.

Some of the things covered here are Sia specific, for example our Makefile is pretty much only going to be found in the Sia repo.
I think I would rather see this titled something more directive, like 'How to Write Tests for Sia', given that the end goal of this document is to get people to start making pull requests, whether to add test coverage or help some other way.

I'm also not sure that we intend on keeping the test-unit and test-integration distinctions, they probably don't need to appear in this guide

Latest commit addresses code review comments, reorganizes layout, and adds more sections (e.g. 'A few guidelines', 'Basic test format', and 'Questions?'.

Need to name the file 'Running and Writing Tests for Sia.md' so that github knows render the markdown.

Fixed formatting issues (code wraps at 80 characters, added .md extension to filename).  Sorry about that.

Addressed Luke's code review comments (changed testing function examples and fixed section on testing particular packages)

Other than the things mentioned, it looks pretty good at this point

Latest changes address code review comments:

add cover tool screenshot and sample make test-long output

doc/Guide to Contributing to Sia.md has new updates; should be ready to merge that soon, which will fix the dead link

git branching instructions have been changed to reflect changes to git configuration instructions in doc/Guide to Contributing to Sia.md

Screenshot link is fixed (changed it to raw url; the relative link wouldn't have worked until the image had been merged).

Link to screenshot doc/assets/covertool.png is fixed.


1508 Delete archived version in UI

Only the admin could perform this action.
It won't be possible to delete the latest version - only the archived versions.

@sylmorin-gbif - thank you!
@MattBlissett - this looks correct to me, but given that it permanently deletes data (and we're rusty on IPT code) can you please review as well?

This looks fine to me, thanks Sylvain.


gh-149 Add flag to ParseDate to handle microsecond accuracy input.

Added an implementation which enables the ParseDate to handle input epoch timestamps specified to microsecond accuracy. The default handling is set to expect epoch timestamps to be provided with millisecond accuracy.

Codecov Report

Merging #218 (67dbfee) into develop (f91f89d) will increase coverage by 0.01%.
The diff coverage is 90.47%.

@@              Coverage Diff              @@
##             develop     #218      +/-   ##
=============================================
+ Coverage      81.13%   81.14%   +0.01%
- Complexity      1534     1538       +4
=============================================
  Files            185      185
  Lines           4268     4281      +13
  Branches         430      431       +1
=============================================
+ Hits            3463     3474      +11
- Misses           627      629       +2
  Partials         178      178

Impacted Files
Coverage Δ

.../gchq/koryphe/iterable/EmptyCloseableIterator.java
0.00% <ø> (ø)

...a/uk/gov/gchq/koryphe/iterable/StreamIterable.java
57.14% <ø> (ø)

...a/uk/gov/gchq/koryphe/iterable/StreamIterator.java
47.05% <ø> (ø)

...in/java/uk/gov/gchq/koryphe/util/IterableUtil.java
71.52% <ø> (ø)

...a/uk/gov/gchq/koryphe/impl/function/ParseDate.java
80.76% <75.00%> (-1.46%)
:arrow_down:

...c/main/java/uk/gov/gchq/koryphe/util/DateUtil.java
85.00% <100.00%> (+2.64%)
:arrow_up:

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 c65ef95...67dbfee. Read the comment docs.

Superseded by https://github.com/gchq/koryphe/pull/230 so more people can contribute to the branch


Mutex for coroutines

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

91 of 97 (93.81%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 99.514%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

include/yaclib/async/detail/base_core.hpp
0
2
0.0%

include/yaclib/coroutine/async_mutex.hpp
89
91
97.8%

include/yaclib/coroutine/detail/promise_type.hpp
2
4
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
1229

Relevant Lines:
1235

💛  - Coveralls


Issue with joining lobbies.

It's probably been mentioned here already, but I just think it's appropriate to mention it.
While using GorillaCosmetics, you can only join 1 lobby per session of Gorilla Tag. As soon as you leave a lobby and try to join a new one, the game will instantly crash. While not being the biggest problem ever, it's just pretty annoying to have to restart the game every time you try to join a new lobby.
quick edit: this happens on quest, but I don't know about PC, this might be in the wrong thing.

on pc the mod straight doesn't load the cosmetics


Invalid Semantic Links for Inferred Type Arguments

Tested in 3.5.0-dev.20190424.
Given this code (playground):
class Main<TData> {
	test1(obj: TData): void {}
	test2(obj: Partial<TData>): void {}
	test3<T extends TData>(obj: T): void {}
	test4<T extends Partial<TData>>(obj: T): void {}
}

interface Bla {
	foo: number;
	bar: number;
}

const m = new Main<Bla>();
m.test1({ bar: 1, foo: 1 });
m.test1({ bar: true, foo: 1 });

m.test2({ bar: 1 });
m.test2({ bar: true });

m.test3({ bar: 1, foo: 1 });
m.test3({ bar: true, foo: 1 });

m.test4({ bar: 1 });
m.test4({ bar: true });

The references are not resolved correctly:

bar in line 20 and 23 is not linked to Bla.bar. It however is in line 21 and 24 where the types don't match.
This affects rename, go to definition and all other semantic actions.
This might be linked to #30507.

Repros in non-generic case as well
class Main {
	test1(obj: Bla): void {}
	test2(obj: Partial<Bla>): void {}
	test3<T extends Bla>(obj: T): void {}
	test4<T extends Partial<Bla>>(obj: T): void {}
}

interface Bla {
	foo: number;
	bar: number;
}

const m = new Main();
m.test1({ bar: 1, foo: 1 });
m.test1({ bar: true, foo: 1 });

m.test2({ bar: 1 });
m.test2({ bar: true });

m.test3({ bar: 1, foo: 1 });
m.test3({ bar: true, foo: 1 });

m.test4({ bar: 1 });
m.test4({ bar: true });

I found another case where the semantic link is not fully established, but I'm not sure if it's a duplicate of this or not. The symptoms are slightly different.
type FooOf<T extends { getFoo(): any }> =
  T extends { getFoo(): infer U; } ? U : never;

Renaming or finding references on the infer U declaration does not affect/find the other usage of U.
Where this case differs is that operations on the latter U function as though they were taken on the infer U. For instance:

"Go to Definition" on the latter U does focus the declaration
Renaming the latter U renames only the declaration
"Find All References" on the latter U finds only the declaration

Btw. this is still broken in v3.8.3.


docs: whitepaper terminology

Is your feature request related to a problem? Please describe.
The terminology employed at the whitepaper is ad-hoc, and creates semantic barriers not only on the whitepaper, but also on its materialization (i.e., code)
Describe the solution you'd like
A clear and concise description of the terminology, for example, following NIST 8202's terminology section.
Describe alternatives you've considered
Leave the current terminology as is.

Related: #249

Being discussed in the academic paper efforts. Closing for now.


K8SSAND-1882 ⁃ Update cass-config-builder to newer 1.0 release

What happened?
cass-config-builder 1.0.5 is a rebuild of the base image (with some smaller changes). Update to it.
Did you expect to see something different?
How to reproduce it (as minimally and precisely as possible):
Environment

Cass Operator version:
Insert image tag or Git SHA here

Kubernetes version information:
kubectl version

Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, etc.

Manifests:

insert manifests relevant to the issue

Cass Operator Logs:

insert Cass Operator logs relevant to the issue here

Anything else we need to know?:
┆Issue is synchronized with this Jira Task by Unito
┆Issue Number: K8SSAND-1882
┆Priority: Medium
┆Link To Issue: https://k8ssandra.atlassian.net/browse/K8SSAND-1882

Fixed in https://github.com/k8ssandra/cass-operator/pull/439


cassandra 3.11.3 -> 3.11.4

Motivation for this change
update cassandra
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test cassandra

Looks like the cassandra test may have been removed from nixos/tests/all-tests.nix at some point? @contrun do you mind adding the cassandra test back to this file so we can run tests here?

@aanderse Looks like the only file in the nixos/tests directory contains cassandra is nixos/tests/cassandra.nix. I tried to search cassandra with git grep cassandra $(git rev-list --all -- nixos/tests/) -- nixos/tests/ | awk -F: '{print $2}' | sort | uniq.

@contrun pardon my poor choice of wording. The actual test remains, but the test is not actually executed by the bot because a reference to the test was removed (or never existed?) in all-tests.nix.
Can you please create an additional commit adding the test back into all-tests.nix?

@aanderse Added that. But I am not familiar with the testing process. Not sure if it will work.

I've been running the test from the master branch locally for ~10 minutes now and no success.
@cransom as the listed maintainer of the cassandra package do you have any information which could help us?

@GrahamcOfBorg test cassandra

@JohnAZoidberg as someone interested in cassandra do you have any insight into why the test is not succeeding?

Seems like you can't have a node as its own seed when it's listening on an interface instead of an IP.
At least the way it's done in the current test doesn't work and I can't figure out any other way.
I'll push a fix to my PR from yesterday that improves the config file: #59179

@contrun Any chance I can get you to leave a review and approval on https://github.com/NixOS/nixpkgs/pull/59179 if everything looks good to you? Bonus points if you test out the changes in your own configuration and mention results. Once https://github.com/NixOS/nixpkgs/pull/59179 is merged it seems like you could rebase this PR on master and we could quickly and confidently merge this. Sorry for the hold up so far.

And if you want you can upgrade the other supported versions we have to their new point release that came out on the same day: https://github.com/apache/cassandra/releases

This PR can be merged now as there is no blocker anymore, right? 100% relying on you @JohnAZoidberg to tell me whether to push the merge button.
@contrun Are you able to rebase on master and possibly update other versions as requested by @JohnAZoidberg?

@GrahamcOfBorg test cassandra

@GrahamcOfBorg build cassandra

Merging solely based on the good word of @JohnAZoidberg.


How to change files stored by cycle.serve

I need to apply some changes to files saved locally using cycle.serve. I see that serve creates a provisional request in the check method:
    let provReq = new ProvisionableRequest({
      protocol: req.protocol,
      proxy: upstreamProxy,
      method: 'GET',
      hostname: req.hostname,
      port: req.port,
      path: req.url,
    })
    provReq.send()
    let mirrResp = yield provReq.receive()

And later on mirrResp is written to the FS:
    let writeToFile = fs.createWriteStream(file)
    // ...
    yield new Promise((resolve, reject) => {
      mirrResp.pipe(writeToFile)
      // ...

It seems to me that changes should be applied to the mirrResp. Is my assumption correct?

Mirroring only downloads once, so to change a file locally, you can just edit the saved file in your text editor.


Resources should be added

Hello!
Resources block should be added to deployment and values file.

Thank you @brycahta

Thanks for the suggestion! Should be merged and released by end of the week


Wrong remote folder with windows host

What happened?
On windows under msys2 I am running :
devspace sync -n namespace --upload-only --pod=podname --local-path=/c/Users/user/work/ --container-path=/app

In the container I can't find /app/, however I can find a C:/Users/Users/scoop/apps/msys2/2021-07-25/app/ containing my files (which is odd to see in Linux..)
What did you expect to happen instead?
I expect to see my files under the remote path of  /app/
How can we reproduce the bug? (as minimally and precisely as possible)
see "What happened?"
Local Environment:

DevSpace Version: [use devspace --version]
devspace version 5.15.0
Operating System: windows | linux | mac
Deployment method: helm | kubectl apply

Kubernetes Cluster:

Cloud Provider: rancher-desktop
Kubernetes Version: [use kubectl version]

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T21:04:39Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4+k3s1", GitCommit:"3e250fdbab72d88f7e6aae57446023a0567ffc97", GitTreeState:"clean", BuildDate:"2021-08-19T19:09:53Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}

Anything else we need to know?
I found that using --container-path=app instead of --container-path=/app (as per documentation) works okay.

/kind bug

@jpambrun thanks for reporting this issue! Does the same problem occur if you use
devspace sync -n namespace --upload-only --pod=podname --local-path=C:\Users\user\work--container-path=/app

?

Sorry for the late response.
I found the reason for this issue. It has nothing to do with devspace. I am using the windows devspace.exe and when invoking windows executable from msys bash it will convert / to the root for msys' installation. So notepad.exe /etc/hosts will become notepad.exe C:/Users/<user>/scoop/apps/msys2/2021-07-25/etc/hosts and "just work". However devspace --container-path=/app becomes devspace --container-path=C:/Users/<user>/scoop/apps/msys2/2021-07-25/etc/hosts which makes no sense .. This was very unexpected to me and I still don't know how to work around it.. Apology for the false positive.

Five more minutes of googling and the right keywords is all I needed to find the solution.
Setting MSYS_NO_PATHCONV=1 or prepending an extra slash (e.g. --container-path=//app) should solve it, but I didn't get a chance to test yet.


MySQL 8.0.23 Support

I have tried the package with MySQL 8.0.23 and its not working properly, like not showing the detailed events as its supposed or not showing the events at all even if returned a successfull message saying that its connected.
¿Any thoughts regarding of this mysql version?

I think the cause of this problem is the incompatibility in the underlying zonji package with MySQL 8. Maybe @rodrigogs update the underlying zonji dependency with this fork the issue might be fixed!
Refer this issue from the original zonji repository here #135

That seems good. If you have some time to spend on it, I would be glad to review a PR.
I'm going to try my best to find some time to implement it if you cant.

Any update on this error? I think that this problem and mysql-events #44 may be related.


require('fzf-lua').live_grep({ cmd = "echo " }) does not work

require('fzf-lua').live_grep({ cmd = "echo " })

With the above Lua code, I expect the fzf window to show up and the item list only contains 1 item -- xxx where xxx is whatever I am typing.
However, it doesn't work like that.

As you can see from the image, I typed something but the item list only show --.
Are you aware of this issue?

I expect the above code should work the same as the code below:
local fzf = require("fzf")

coroutine.wrap(function()
  local result = fzf.fzf(
        {},
        "--bind 'change:reload:echo {q} || true'"
    )
  -- result is a list of lines that fzf returns, if the user has chosen
  if result then
    print(result[1])
  end
end)()

Fixed by removing the -- from the command, if required we can just add it to the cmd string.


GELU hard coded

Hi,
It seems that the activation func has been hard coded in TimeMixer.py as nn.GELU. I cannot set it by --activation parameter.
Thanks

Hi,
It seems that the activation func has been hard coded in TimeMixer.py as nn.GELU. I cannot set it by --activation parameter.
Thanks

We indeed use GELU as the default activation function, about the design of the TSLib.  Thanks for your suggestion, we will consider making this more flexible in future iterations.


Update stable version in repo from 1.4.2 to 1.5.3

Think about update stable version to 1.5.3
Version: stable=1.4.2 (48 days old) => latest=1.5.3 (15 days old)
Installs: stable=95 (58.64%), latest=18 (11.11%), total=162
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.5.3 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.5.3 but the current stable version is already 1.5.3.
So this issue should be closed.
@mcm1957 for evidence


Merge consecutive events in the truth en Germline Evaluation tool.

Currently if the truth (GenomeSTRiP vcf variants) are contiguous in target space we do not merge them thus they would count as several independent truth events when there is no way that an exome based tool would ever see them that way.
This issue is about adding an option so that these event can be merged.
This cannot be iniciated until the evaluation code has been merged into master.

Issue moved to broadinstitute/gatk #2852 via ZenHub


Controls in viewport with stretch-shrink positioned wrong

Godot version
v4.0.alpha2.official [79077e6c1]
System information
Windows 10
Issue description
After creating a SubViewportContainer and a SubViewport and setting stretch-scale to 2 and adding a child control and centering it looks like it is in the wrong position in editor but right when running.  This works in 3. Thanks.

Steps to reproduce

open TestGenerate .tscn, or generate a scene like gif, notice part off screen
run and fine

Minimal reproduction project
https://github.com/rakkarage/GenerateTexture

I feel like this is a situation where we want the SubViewport to work like a Control. Unfortunately it isn't, so the passing of update calls between parent and child is broken. So maybe there are nodes that are not updated.

I had a look at the MRP and it doesn't contain any SubViewport-node. So it doesn't fit to the bug-description.

Seems still valid, here's some repro
Repro.zip
The only problem here is that it looks different in game than in editor.


Add OAuth Readme.

Add readme for the sample OAuth project.

Content looks good, though it some of it seems like it'd be a better fit for the documentation than a readme, it's kind of general how to set up oauth and less about this specific sample. If the oauth documentation ends up duplicating some of this readme, it may be better to just link that documentation in the readme so there's only one place we need to keep track of.
Also, can you address the comments in #692 in this PR? Just to keep the discussion in one place as much as possible.
Thanks for taking this on!

Yeah I agree it's a bit more verbose I'll change that.
Oh the code as of right now already has addressed the comments for removing the logs in connectionBuilder.js and mask secrets in oAuthConfig.xml.

Content looks good, though it some of it seems like it'd be a better fit for the documentation than a readme, it's kind of general how to set up oauth and less about this specific sample. If the oauth documentation ends up duplicating some of this readme, it may be better to just link that documentation in the readme so there's only one place we need to keep track of.
Also, can you address the comments in #692 in this PR? Just to keep the discussion in one place as much as possible.
Thanks for taking this on!

Yeah I agree it's a bit more verbose I'll change that.
Oh the code as of right now already has addressed the comments for removing the logs in connectionBuilder.js and mask secrets in oAuthConfig.xml.

The snowflake_oauth changes should have gone in as a PR.  It looks like the direct merge caused some noise.  I think its ok to keep since there wasn't any overlap in the files.

The snowflake_oauth changes should have gone in as a PR.  It looks like the direct merge caused some noise.  I think its ok to keep since there wasn't any overlap in the files.

The snowflake_oauth changes should have gone in as a PR. It looks like the direct merge caused some noise. I think its ok to keep since there wasn't any overlap in the files.

Yep I accidentally delete the dev-2021.1 branch yesterday and restore that, I've worked with Patrick to make sure it contains all changes needed. My bad for using the wrong git command that direct push changes in.

The snowflake_oauth changes should have gone in as a PR. It looks like the direct merge caused some noise. I think its ok to keep since there wasn't any overlap in the files.

Yep I accidentally delete the dev-2021.1 branch yesterday and restore that, I've worked with Patrick to make sure it contains all changes needed. My bad for using the wrong git command that direct push changes in.

The snowflake_oauth changes should have gone in as a PR. It looks like the direct merge caused some noise. I think its ok to keep since there wasn't any overlap in the files.

Yep I accidentally delete the dev-2021.1 branch yesterday and restore that, I've worked with Patrick to make sure it contains all changes needed. My bad for using the wrong git command that direct push changes in.

I've made sure the dev-2021.1 branch is protected, to guard against stuff like that in the future.

The snowflake_oauth changes should have gone in as a PR. It looks like the direct merge caused some noise. I think its ok to keep since there wasn't any overlap in the files.

Yep I accidentally delete the dev-2021.1 branch yesterday and restore that, I've worked with Patrick to make sure it contains all changes needed. My bad for using the wrong git command that direct push changes in.

I've made sure the dev-2021.1 branch is protected, to guard against stuff like that in the future.


Removed MongoDB, replaced with LevelDB

These changes remove dependency on MongoDB and replace it with LevelDB.

:tada: This PR is included in version 5.0.2 :tada:
Your semantic-release bot :package::rocket:


Update hdinsight-hadoop-customize-cluster-bootstrap.md

Fixed invalid parameters causing the script to fail and also updated version from 3.6 to 4.0 since 3.6 will be deprecated soon.

@sreekzz
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Computer doesn't sleep

I set all durations to 1-minute but the computer never sleeps when the bclm is running. It was sleeping before I installed blcm. I'm running Sonoma 14.4 on an Apple M1 Max

+1

What method are you using to determine if it is sleeping or not? Have you checked Activity Monitor to see if any apps are preventing sleep? Are you streaming the log on Console before, during and after and checking the timestamps?

Not seeing this behavior on my hardware. The problem seems unrelated to bclm, if you have evidence to the contrary, please let me know.


"getInitialNotification" always return "null" .

getInitialNotification method always return 'null' for  local notification. I have tried in both scenarios while the app in background and while the app is closed and open from local notification .

Duplicate of https://github.com/react-native-push-notification-ios/push-notification-ios/issues/24


Minor UI cleanup + '...NameFromRoute' renaming refactor

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1159
Originally created by @derek-knox on 2019-10-18 21:28:51

[x] SQL button out of the 'group' for Analyze "Run" + "Sync" toggle
[x] Fix model highlight in main nav when Analyze is in focus
[x] drop ...NameFromRoute akin to EntitiesSelectorModal update https://gitlab.com/meltano/meltano/merge_requests/1045/diffs#e5989cb94ba25c7b35beb025bcf8d11714e2c4c8_99_92

View 5 previous comments from the original issue on GitLab


Update azure_ad_* tables to no longer return results and suggest using the matching tables in the azuread plugin. Closes #440

Example query results

Results
> select * from azure_ad_group

Error: Table deprecated and remove, please use table azuread_group instead. (SQLSTATE HV000)
> select * from azure_ad_service_principal
Error: Table deprecated and remove, please use table azuread_service_principal instead. (SQLSTATE HV000)
> select * from azure_ad_user
Error: Table deprecated and remove, please use table azuread_user instead. (SQLSTATE HV000)
> .quit

https://github.com/turbot/steampipe-plugin-azure/commit/071a8bbe7aebd9f1c3218786a07eb993cfd95856 includes changes to remove functionality from these tables, closing this PR.