drumkv1: 0.9.2 -> 0.9.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/drumkv1/versions.
meta.description for drumkv1 is: '"An old-school drum-kit sampler synthesizer with stereo fx"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/bin/drumkv1_jack had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.9.3 with grep in /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3
directory tree listing: https://gist.github.com/21a4acb65d49b59e27d62df75991b0c1
du listing: https://gist.github.com/45145481fbcf06d8917738d6b444cc0e

Rebuild report (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
drumkv1

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A drumkv1 https://github.com/r-ryantm/nixpkgs/archive/7c4c370078a8fcd02680380e7c8bc1c467ca0431.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3
ls -la /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/bin

cc @cillianderoiste for testing.

Success on aarch64-linux (full log)
Attempted: drumkv1
Partial log (click to expand)
shrinking /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3/lib/lv2/drumkv1.lv2/drumkv1.so
shrinking /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3/lib/libdrumkv1_ui.so.0.9.3
shrinking /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3/lib/libdrumkv1.so.0.9.3
gzipping man pages under /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3/lib  /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3/bin
patching script interpreter paths in /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3
checking for references to /build in /nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3...
postPatchMkspecs
/nix/store/39ha6sj7wcf37binp2fp6v0jf163fyam-drumkv1-0.9.3

Success on x86_64-linux (full log)
Attempted: drumkv1
Partial log (click to expand)
shrinking /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/lib/lv2/drumkv1.lv2/drumkv1_ui.so
shrinking /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/lib/lv2/drumkv1.lv2/drumkv1.so
shrinking /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/bin/drumkv1_jack
gzipping man pages under /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/lib  /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3/bin
patching script interpreter paths in /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3
checking for references to /build in /nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3...
postPatchMkspecs
/nix/store/48kmm94xldc0f5a3llz8v1sgxnip2yrw-drumkv1-0.9.3


Fix build with fmt 8.1.0

Stop using fmt::formatter<std::tm> implementation details
Add tests for the waybar_time formatter

Tests might be a bit fragile as the date::format output depends on an underlying STL locale implementation. Any difference there is a bug though, and things are working on two stdlib implementations I tested.
Alpine build fails as the tests require timezone data. Dockerfile change in the top commit should address that.
Fixes #1368, #1379

Thank you, @alebastr . This seems much better than my quick hotfix. 👍🏽
I had to skip patches 8c41aaa and 766c8a1 for it to compile, since it was complaining about "can't find file to patch" on those.
I figured my upstream didn't include tests, so it should be safe. Right?

@mazunki yes, tests were added after 0.9.8 so it's safe to skip these patches. You can even skip a couple more and take only https://github.com/Alexays/Waybar/pull/1380/commits/c0d84853ea2f3f8b016abf92458ba15378de6c91 and https://github.com/Alexays/Waybar/pull/1380/commits/7f6bef20496ca23e83692801f6ff2957d28dde76.
@Alexays thanks for merging. Can you please update the alpine image?


Moves downloadHandler into server

Regional IO tables and Regional employment tables were not being updated in the downloadHandler if a user changed which region they were interested in.


OAuth Proxy not accepting external traffic

Hi,
I apologise for this as I'm sure I must be doing something wrong, but here we go.
I downloaded and setup the oauth proxy to use with a Google account. After following the various instructions, I ran a command roughly like:
./oauth2_proxy -upstream="http://localhost:9000" --client-id="my-client-id.apps.googleusercontent.com" --client-secret="my-secret" --cookie-secret="this is a cookie secret for this server".
I then executed curl localhost:4180/ping and got a 200 response as expected.
I ensured that I opened up the security groups on my instance and tried to access it from my local machine. But I only got connection refused.
Skipping a long story, I ended up compiling the simple Go server which is currently here: https://golang.org/doc/articles/wiki/#tmp_3, with a minor modification to use port 4180 instead of 8080.
And everything worked. I could access my Simple Go Server from both localhost (same machine) and from my own dev machine. Which, I think, rules out any firewalls, security groups etc. But possibly doesn't rule out issues with the Amazon AMI I'm using.
I began digging around in the code for the server, and found that the primary difference is this one:
In http.go, the current code executes:
listener, err := net.Listen(networkType, listenAddr), which translated to: listener, err := net.Listen("tcp", "<IP_ADDRESS>:4180")
Whereas the Simple Go Server executes something equivalent to net.Listen("tcp", ":4180").
Changing the code in http.go to:
listener, err := net.Listen(networkType, ":4180") fixed the problem.
And equally, changing my Simple Go Server to net.Listen("tcp", "<IP_ADDRESS>:4180") breaks it. I'm running Go v1.4.2 if that's relevant.
So it's something about how that listener gets setup.
So, I think the bug is either:

You can't set -http-address=":4180", which I think would solve my problem.
Some documentation about what issue I've run into and how to resolve it.

I'm assuming it's some configuration issue around networking I'm not familiar with and therefore the solution is 2. If someone can point me in the right direction that'd be fantastic!
Thanks!
 That's why oauth2_proxy by default only listens on <IP_ADDRESS> which only allows connections from processes on the same server (for example, nginx running on the same server and listening for https connections). see https://github.com/bitly/oauth2_proxy#ssl-configuration
I expect that if you specify --http-address=<IP_ADDRESS>:4180 you can force oauth2_proxy to accept http connections on any interface.

The docs could probably be clearer here. As @ploxiln beat me to, you want <IP_ADDRESS>:4180 The <IP_ADDRESS> denoting to listen on any ip.
The form for listening is a little finicky because it expects a protocol so it can pivot and listen on a socket. That means http://:4180 will also work.
please confirm back here that those details solve your issue.

Ah, it's so obvious!
Yes, that is exactly what I needed. I'm using Amazon ELB as my termination point, hence the problem. Let me update the docs.


Can you add a way to calculate the max heap used?

At the moment you provide heap.used() but i need something like heap.maxUsed() to validate some of the code that we are working with can work on certain device types

This could be done in this crate, but it would make more sense to add them in the underlying alloc crates.

Hello, I would like to discuss your laser hair removal project.


typo: resources/resource-manager/Microsoft.Authorization

assigment -> assignment
reponse -> response

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Can one of the admins verify this patch?


Review Code Coverage

General review of code coverage

[x] Excluding items that shouldn't be counted
[x] Create issues to add tests anywhere that it is warranted (aka not just 100% coverage, but actually should have a test)

Looking much better: https://app.codecov.io/gh/LibertyDSNP/frequency?search=&displayType=list


pageserver: fix secondary progress stats when layers are 404

Problem
Noticed this issue in staging.
When a tenant is under somewhat heavy timeline creation/deletion thrashing, it becomes quite common for secondary downloads to encounter 404s downloading layers.  This is tolerated by design, because heatmaps are not guaranteed to be up to date with what layers/timelines actually exist.
However, we were not updating the SecondaryProgress structure in this case, so after such a download pass, we would leave a SecondaryProgress state with lower "downloaded" stats than "total" stats.  This causes the storage controller to consider this secondary location inelegible for optimization actions such as we do after shard splits
This issue has relative low impact because a typical tenant will eventually upload a heatmap where we do download all the layers and thereby enable the controller to progress with migrations -- the heavy thrashing of timeline creation/deletion is an artifact of our nightly stress tests.
Summary of changes

In the layer 404 case, subtract the skipped layer's stats from the totals, so that at the end of this download pass we should still end up in a complete state.
When updating last_downloaded, do a sanity check that our progress is complete.  In debug builds, assert out if this is not the case.  In prod builds, correct the stats and log a warning.

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

It seems test_upgrade_generationless_local_file_paths needs an allow for the drift log message (we could even expect it, that way we have a test for this situation).

It seems test_upgrade_generationless_local_file_paths needs an allow for the drift log message (we could even expect it, that way we have a test for this situation).

It turns out that was actually a real bug (that test was exercising downloads after a restart, and failing because the progress stats weren't being updated properly after we called init_timeline_state) - pushed a fix.


Empty inline tables fail parse

This:
a = { }

fails with
Error at line 1 column 8:
Expected "=" or any character but end of input found.

(tested on http://binarymuse.github.io/toml-node/)

Fixed in 2.2.3.


[Fix][UI Next][V1.0.0-Alpha]Fix default display of node name in sub p…

Purpose of the pull request
This pull request fixs default display of node name in sub process node.
Releated issues
close #9071

Codecov Report

Merging #9075 (a43a68a) into dev (bf1f959) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #9075   +/-   ##
=========================================
  Coverage     39.80%   39.80%
- Complexity     4264     4265    +1
=========================================
  Files           808      808
  Lines         32545    32545
  Branches       3646     3646
=========================================
+ Hits          12953    12954    +1
  Misses        18365    18365
+ Partials       1227     1226    -1

Impacted Files
Coverage Δ

...er/master/dispatch/host/assign/RandomSelector.java
83.33% <0.00%> (+5.55%)
: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 bf1f959...a43a68a. Read the comment docs.


Implement BeginScope for the GoogleLogger

Set this to P1 as it looks like a pretty important missing feature...


UI: Left Panel Search Box unknown dispatch SET_STORY_FILTER "A Title"

Something appears to be dispatching SET_STORY_FILTER with a payload of {storyFilter: "A Title"}. I was unable to find a cause in my codebase and after looking through a few of the storybook related repositories I've been unable to locate the string. I did manage to successfully reproduce the issue with the AirBnB Dates example locally.
Local

Production

That's pretty weird.
I cannot re-produce this.
Searched for the "A Title" text and found nothing.

@arunoda Turns out a browser extension was the culprit and that I shouldn't be writing code at midnight.


Tables i and j have wrong values for catch in row m

Need to run calc_risk(), append to base_model  and save RDS again

The base_model RDS file is corrected


Fix to #2074 - allow users to opt-out from using null comparison expansion

Added UseDatabaseNullSemanticsQueryAnnotation that can be used to annotate the query with information that it should not expand null comparisons.

@anpete @mikary

updated the pull request

@anpete  - updated the pull request

There is a bunch of thing to follow up on but I am fine with pushing this if @anpete finished reviewing.

:shipit: pending comments


Connection Issues Through Desktop Client

User is experiencing issues and is receiving errors when trying to connect and use the Toggl desktop client.
Desk case/588883 includes all information and error notes.

The user asked me to bump this. They are really anxious to get their desktop app working again.

Having the same issue.  Are you online?

Using Arch Linux, encountering the issue with toggldesktop & toggldesktop-bin packages. Worked fine until a few weeks ago.

Same issue here, also on Arch Linux. Got the problem after upgrading from 7.4.61.

case/612731

Same issue with Arch.

Same here with Arch.
This bug may be not upstream fault, but related to packaging or openssl.
Some interesting posts can be found in Arch AUR discussion: https://aur.archlinux.org/packages/toggldesktop/

This seems like an issue with a third-party package, so I'm closing it but please feel free to reopen in case there is an issue like this with our official packages.


Fix convertFeetToInches method

There is currently a method called convertFeetToInches that lives in /lib/convertFeetToInches.js.
It is incomplete and needs to be fixed!

Acceptance Criteria:

Running yarn test convertFeetToInches results in tests passing.
You have written a skeleton method for someone else to work on.
You have written tests surrounding your skeleton method.
Running yarn lint does not print any errors to the console!
Optional: write one or two more tests surrounding the method you are solving to account for potential edge cases.

Please include the skeleton of a new method + an accompanying test for someone else to work on at the time of creating a pull request! A pull request will most likely be denied if it does not contain a skeleton method for someone else to work on! For more information, please read the Contributing Guide.
Thank you so much for your contribution!

Sounds cool, I'll work on this!

Pull request #394 introduces the convertFeetToInches functionality and introduces a convert function.
The scope was expanded beyond the issue in two manners:

I added .idea to the gitignore files for anyone who prefers developing with a Jet Brain product.
I removed a test which expected a throw on non-numeric types which utilizes a negative number for its argument.


Bugfix/angular 1.5 support

closes #8

Current coverage is 100.00%

Merging #9 into master will not affect coverage as of ac2e4f4

@@            master      #9   diff @@
======================================
  Files            3       3
  Stmts           30      30
  Branches         0       0
  Methods          0       0
======================================
  Hit             30      30
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of ac2e4f4

Powered by Codecov. Updated on successful CI builds.


Add support to :max_heap_size in websocket handler

See https://github.com/phoenixframework/websock_adapter/pull/15 for the reasoning.
Felt like this was necessary here as well, but maybe bandit/thousand_island architecture wouldn't require it, I didn't really look deeply into it.

Thanks! This looks great!


[#127449817] Increase timeout for tag_release tests to 30s

What?
Similar to #388 and #435
This script sometimes takes more than Eventually's default timeout of 1sec to
return when running in travis. Probably git operations are too heavy for
the container based travis build.
This happened in travis several times[1]. Dan was able to reproduce it
by running ginkgo --untilItFails, but I couldn't.
I set the timeout to 30. Even with 3 seconds it timeouts sometimes, and it is
not really important to add more time if it eventually timeouts in a reasonable
time.
The failure looked like this:
  • Failure in Spec Setup (BeforeEach) [3.847 seconds]
  TagRelease
  /home/travis/build/alphagov/paas-cf/concourse/scripts/tag_release_test.go:147
    when there are multiple 'previous-*' tags to be promoted
    /home/travis/build/alphagov/paas-cf/concourse/scripts/tag_release_test.go:146
      and the before last tag of 'previous-*' is promoted [BeforeEach]
      /home/travis/build/alphagov/paas-cf/concourse/scripts/tag_release_test.go:115
        should promote the same tag version for 'next-*'
        /home/travis/build/alphagov/paas-cf/concourse/scripts/tag_release_test.go:89
        Timed out after 3.000s.
        Expected process to exit.  It did not.
        /home/travis/build/alphagov/paas-cf/concourse/scripts/tag_release_test.go:161

[1] https://travis-ci.org/alphagov/paas-cf/builds/153593309
How to test?
Travis should pass, or see #426
Who?
Anyone but me

This test is local and should never take a lot of time. There can be some overhead for initialisation but if the command takes more than 10-15s I would be worried. Could you set it to 15s at most?

The only reason why there is a timeout at all is because we are forced to use Eventually in conjunction with gexec.Exit(0) as in https://github.com/alphagov/paas-cf/pull/539/files#diff-fe3bf3708b13219c511839e8e7834c17L36
The reason is that the exit code is not ready until the command finished, so you cannot check it in the test, you need to run a script that checks the execution in a given interval, like Eventually does.
We do not check the timeout of any other command, instead all of them they have an unlimited time to run.
This command is timing out because it is taking whatever time to run due some circumstances in travis which are out of our reach.
I will happily change from 30s to 15s if there is a good answer for: What do we win with 15s instead of 30s? if it timeouts, what will we do apart of rerun the run in travis, complain and maybe eventually increase it? Why set it to 15s and not 150s instead?

Neither for you or me, I will agree to change the number to any value to the result of this: echo $((RANDOM % (30-15) + 15))


[ERROR  ] [ffpyplayer  ] C:\Users\Furkan\Desktop\music_project\data\arp.wav: Protocol not found

Software Versions

Python: 3.6.7
OS: Windows 8.1
Kivy: 1.11.0
Kivy installation method: pip

Describe the bug
I cannot play my arp.wav file with ffpyplayer. I have installed ffpyplayer with pip (pip install ffpyplayer) but I couldn't compiled it (https://matham.github.io/ffpyplayer/installation.html) and I guess thats why it gives an error. I need a simple instruction of installing ffpyplayer because I am new to Kivy :(.
By the way I have tried SDL2 but it does not have get_pos() and seek() methods available (I need them). Gstplayer starts songs with noticable delay so I have to use ffpyplayer guys...
Expected behavior
I expect to play my audio file when I click the button with ffpyplayer.
Code and Logs and screenshots
// import os
os.environ['KIVY_AUDIO'] = 'ffpyplayer'

from kivymd.app import MDApp
from kivymd.uix.screen import Screen
from kivy.uix.togglebutton import ToggleButton
from kivymd.uix.gridlayout import MDGridLayout
from kivy.core.audio import Sound,SoundLoader
from kivy.clock import Clock
from kivy.lang import Builder

kv = """
<MyScreen>:
    MDGridLayout:
        cols:2
        id: mdgridlayout
        ToggleButton
            id:button_arp
            text:"arp"
            on_state:root.play_or_stop(self.state,root.arp)
"""

class MyScreen(Screen):

    def __init__(self, **kw):
        super().__init__(**kw)

        self.arp = SoundLoader.load("data\\arp.wav")
        self.a = 0

    def play_or_stop(self,state,song):
        if state == "down":
            song.play()
            song.seek(self.a)
            song.loop = True
        else:
            song.stop()

    def show_song_pos(self,*args):

        self.a = self.arp.get_pos()
        self.ids.button_arp.text = "Arp" + str(self.a)

class DemoApp(MDApp):
    def build(self):
        root = MyScreen()
        Clock.schedule_interval(root.show_song_pos,0.1)
        return root

if __name__ == "__main__":
    Builder.load_string(kv)
    DemoApp().run()

Also encountered this issue on windows and reverted back to SDL2

There's no log so there's no way to debug.

@matham Sorry I have forgot the logs. Here they are.

[INFO   ] [deps        ] Successfully imported "kivy_deps.gstreamer" 0.1.18
[INFO   ] [deps        ] Successfully imported "kivy_deps.glew" 0.1.12
[INFO   ] [deps        ] Successfully imported "kivy_deps.sdl2" 0.1.23
[INFO   ] [Kivy        ] v1.11.1
[INFO   ] [Kivy        ] Installed at "c:\Users\Furkan\Desktop\music_project\kivy_venv\lib\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 13:35:33) [MSC v.1900 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "c:\Users\Furkan\Desktop\music_project\kivy_venv\Scripts\python.exe"
[INFO   ] [KivyMD      ] v0.104.1
[INFO   ] [Factory     ] 184 symbols loaded
[INFO   ] [ImageLoaderFFPy] Using ffpyplayer 4.3.1
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_ffpyplayer, img_gif
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [GL          ] Using the "OpenGL" graphics system
[INFO   ] [GL          ] GLEW initialization succeeded
[INFO   ] [GL          ] Backend used <glew>
[INFO   ] [GL          ] OpenGL version <b'4.4.0 - Build <IP_ADDRESS>35'>
[INFO   ] [GL          ] OpenGL vendor <b'Intel'>
[INFO   ] [GL          ] OpenGL renderer <b'Intel(R) HD Graphics 5500'>
[INFO   ] [GL          ] OpenGL parsed version: 4, 4
[INFO   ] [GL          ] Shading version <b'4.40 - Build <IP_ADDRESS>35'>
[INFO   ] [GL          ] Texture max size <16384>
[INFO   ] [GL          ] Texture max units <32>
[INFO   ] [Window      ] auto add sdl2 input provider
[INFO   ] [Window      ] virtual keyboard not allowed, single mode, not docked
[INFO   ] [Text        ] Provider: sdl2
[INFO   ] [GL          ] NPOT texture support is available
[INFO   ] [SoundFFPy   ] Using ffpyplayer 4.3.1
[INFO   ] [Audio       ] Providers: audio_ffpyplayer (audio_gstplayer, audio_sdl2 ignored)
[ERROR  ] [ffpyplayer  ] C:\Users\Furkan\Desktop\music_project\data\arp.wav: Protocol not found
[ERROR  ] [ffpyplayer  ] C:\Users\Furkan\Desktop\music_project\data\bass.wav: Protocol not found
[ERROR  ] [ffpyplayer  ] C:\Users\Furkan\Desktop\music_project\data\clap.wav: Protocol not found
[ERROR  ] [ffpyplayer  ] C:\Users\Furkan\Desktop\music_project\data\hihat.wav: Protocol not found
[ERROR  ] [ffpyplayer  ] C:\Users\Furkan\Desktop\music_project\data\kick.wav: Protocol not found
[ERROR  ] [ffpyplayer  ] C:\Users\Furkan\Desktop\music_project\data\lead.wav: Protocol not found
[INFO   ] [Base        ] Start application main loop

Example non-working file (windows, .wav)
countdownbeep.zip

Hmm I'm unable to reproduce using the latest ffpyplayer on py3.7 x64.
I suspect this is an issue with your environment (dll hell) where somehow it's pulling another ffmpeg dll from a different package.
Could you try the following in a empty script without importing anything else:
from ffpyplayer.player import MediaPlayer
ff_opts = {'vn': True, 'sn': True}
ffplayer = MediaPlayer(filename)

and see if it plays the audio? If it doesn't, look in the folder join(sys.prefix, 'share', 'ffpyplayer', 'ffmpeg', 'bin'), you'll find ffplay.exe. try playing the file using ffplay filename and see if it has an issue.

That works, except for some weird looping at the end.
This reproduces the protocol not found:
import os
os.environ["KIVY_AUDIO"] = "ffpyplayer"
import time
from kivy.core.audio import SoundLoader

beep = SoundLoader.load("sounds/countdownbeep.wav")
beep.play()
time.sleep(10)

That works for me, still.
I installed master (python -m pip install kivy[base] --pre --extra-index-url  https://kivy.org/downloads/simple/) and ffpyplayer (pip install ffpyplayer) in a clean virtualenv and ran the code and it worked fine.

interestingly creating a new conda env on windows (which now defaults to 3.7.7) and installing those results in working audio.

Also when using 2.0.0rc2.
Upgrading kivy deps on the original env did not help.
Installing every package from the original env  (from list explicit/install --file) in the new env did not break it.
Creating a new environment with py3.7.3 like the original and installing packages (from list explicit/install --file) and then kivy+ffpyplayer -> back to non working audio.
Creating a new environment with py3.7.3 and just installing kivy --pre and ffpyplayer from pypi -> working audio.
Started a binary search of the package list, but both the top half and the bottom half result in working audio.

I'm very puzzled!

You entered dll hell!!. This used to be very common for kivy gstreamer until we switched to using msvc gstreamer builds and started pushing users to only install into a clean virtualenv.

I had the same problem. News on how to fixed? [ERROR ] [ffpyplayer ]video.mp4: Protocol not found

I had the same problem. News on how to fixed? [ERROR ] [ffpyplayer ]video.mp4: Protocol not found

I have stop continuing to my project, because python's execution speed did not satisfy for my case. So the answer is unfortunately no :( .

I'm going to close this because there's nothing for us to do here. Either something is wrong with the environment and you need to test it from a clean virtual environment, or the ffpyplayer binaries used just don't support the type of media in this file. In which case I'd convert the file to a different format. Either way we can't do anything about this.

my objective was simply to drag the control bar of the VideoPlayer and see  changes in the video, with no stop of 5 seconds. Is it possible to do that in whatever way in kivy? thank you

I answer to your message here because I've seen you marked the other post as duplicate. Your question was:
"Do you have a colon in the filename? What is the exact full filename of the video?". My answer is simply "video" with mp4 extension, thank you

Unfortunately, as I explained, there's nothing we can do about this as it's not a Kivy problem but with the underlying video decoder. And it's either because your environment has conflicts and you need to try this in a clean virtual environment, or the player doesn't support whatever data is in your file so you may want to try converting the video file to a different format. Otherwise, there isn't anything for us to do.

thank you very much @matham . Regarding my objective of simply to drag the control bar of the VideoPlayer and see changes in the video, with no stop of 5 seconds... Do you think is it possible to do that in whatever way in kivy? PS: If you think that would be better post this as a new topic please let me know, I don't want mess this thread, please let me know which is the best way for me to receive support for this question, I can also delete my comments in this page if you find it more reasonable, please let me know your thoughts about that, thank you in advance

About seeking to a more precise frame, that issue is already open here, but no one has worked on it so it hasn't been resolved. The cause of that is explained there.
About the other stuff, for support, we use discord.

thank you @matham

About the ffpyplayer error "Protocol not found", try to remove kivy_deps.gstreamer dependancy (if you use PyCharm for your project this is very simple) or reinstall kivy[base] only. And it shoul work.


Show Code Feature Doesn't Work

https://github.com/user-attachments/assets/5b311585-7897-4abd-bdf6-2145747157a4
CC @AnasSarkiz
/bounty $10

@seveibar, it works !!


When should a trace be considered as failed?

If a trace is sent for a match that will never happen (or a flow entry that never got installed for some reason) or a switch that's not connected it'll stay as type: starting indefinitely. For instance:
{
    "trace": {
        "switch": {
            "dpid": "00:00:00:00:00:00:00:01",
            "in_port": 1
        }
    }
}

{
    "result": [
        {
            "dpid": "00:00:00:00:00:00:00:01",
            "port": 1,
            "time": "2022-02-01 18:08:31.970954",
            "type": "starting"
        }
    ]
}

❯  ovs-ofctl -O OpenFlow13 dump-flows s1
 cookie=0x0, duration=60.673s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=50000,dl_src=ee:ee:ee:ee:ee:02 actions=CONTROLLER:65535
 cookie=0xab00000000000001, duration=62.625s, table=0, n_packets=21, n_bytes=882, send_flow_rem priority=1000,dl_vlan=3799,dl_type=0x88cc actions=CONTROLLER:65535

Originally how was it envisioned to report trace failures? Maybe fail fast calls would be easier to maintain and delegate the retries for callers to pace accordingly, assuming the API will continue to work synchronously?

sdntrace_cp or sdntrace?
On Tue, Feb 1, 2022 at 4:24 PM Vinicius Arcanjo @.***>
wrote:

If a trace is sent for a match that will never happen (or a flow entry
that never got installed for some reason) or a switch that's not connected
it'll stay as type: starting indefinitely. For instance:
{
"trace": {

    "switch": {

        "dpid": "00:00:00:00:00:00:00:01",

        "in_port": 1

    }

}

}
{
"result": [

    {

        "dpid": "00:00:00:00:00:00:00:01",

        "port": 1,

        "time": "2022-02-01 18:08:31.970954",

        "type": "starting"

    }

]

}
❯  ovs-ofctl -O OpenFlow13 dump-flows s1
cookie=0x0, duration=60.673s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=50000,dl_src=ee:ee:ee:ee:ee:02 actions=CONTROLLER:65535
cookie=0xab00000000000001, duration=62.625s, table=0, n_packets=21, n_bytes=882, send_flow_rem priority=1000,dl_vlan=3799,dl_type=0x88cc actions=CONTROLLER:65535
Originally how did it was envision to report the failure? Maybe fail fast
calls would be easier to maintain and delegate the retries for callers to
pace accordingly, assuming the API will continue to work synchronously?
—
Reply to this email directly, view it on GitHub
https://github.com/amlight/sdntrace_cp/issues/19, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADC4AM6RMK7RABZTAKOCX2LUZBFRTANCNFSM5NKJYBLA
.
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.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

sdntrace_cp or sdntrace?
…
On Tue, Feb 1, 2022 at 4:24 PM Vinicius Arcanjo @.> wrote: If a trace is sent for a match that will never happen (or a flow entry that never got installed for some reason) or a switch that's not connected it'll stay as type: starting indefinitely. For instance: { "trace": { "switch": { "dpid": "00:00:00:00:00:00:00:01", "in_port": 1 } } } { "result": [ { "dpid": "00:00:00:00:00:00:00:01", "port": 1, "time": "2022-02-01 18:08:31.970954", "type": "starting" } ] } ❯ ovs-ofctl -O OpenFlow13 dump-flows s1 cookie=0x0, duration=60.673s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=50000,dl_src=ee:ee:ee:ee:ee:02 actions=CONTROLLER:65535 cookie=0xab00000000000001, duration=62.625s, table=0, n_packets=21, n_bytes=882, send_flow_rem priority=1000,dl_vlan=3799,dl_type=0x88cc actions=CONTROLLER:65535 Originally how did it was envision to report the failure? Maybe fail fast calls would be easier to maintain and delegate the retries for callers to pace accordingly, assuming the API will continue to work synchronously? — Reply to this email directly, view it on GitHub <#19>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADC4AM6RMK7RABZTAKOCX2LUZBFRTANCNFSM5NKJYBLA . 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. You are receiving this because you are subscribed to this thread.Message ID: @.>

@jab1982 sdntrace_cp

@gretelliz, can we close this issue? Based on how things have evolved/implemented, the type property in the response when it's "incomplete" or "loop" now clearly represents a failure. I've noticed though that the type last hasn't been documented, since it's been used for representing a successful trace we should do it.


Test with Alectryon 1.4 and Coq 8.14.

For warnings that can be unconditionally disabled, we could use Global Set Warnings "-…". in a core file.  I'm don't think that SerAPI has a way to customize warnings from the command line otherwise, but maybe there's a [protocol command that we could use for that if the Set Warnings route is not desirable.

Global Set Warnings is frowned upon because of the transitive reach (beyond project boundaries). That's why command line arguments are usually preferred for that kind of stuff. That being said, in this precise case, I can also fix the warning by adding #[ global ] annotations everywhere they are missing.


Add half-width support + full-width space conversion

A lot of the extant corpus uses half-width katakana and full-width spaces. I added them for conversion to latin.

Thanks!
This implementation very good for convenience, but i think correctness should also be considered. Error endurance to some extend is important, but to support a whole system of half-width Katakana need a thorough consideration. I'm considering to add it as a feature? Anyway, I will check this later.

No problem! I'm using your program as a baseline for a paper about my ByT5-based transliteration tool, and it seemed unfair to compare it as-is when half or more of my corpus uses half-width characters. I've augmented the tool for the baseline comparison at least


Class attributes can be mutated from Python code

The guide states:

Note that unlike class variables defined in Python code, class attributes defined in Rust cannot be mutated at all

But this is in fact possible:
use pyo3::prelude::*;

#[pyclass]
struct MyClass {}

#[pymethods]
impl MyClass {
    #[classattr]
    fn my_attribute() -> String {
        "hello".to_string()
    }
}
fn main() {
    Python::with_gil(|py| {
        let my_class = py.get_type::<MyClass>();

        // All good...
        pyo3::py_run!(py, my_class, "assert my_class.my_attribute == 'hello'");

        // OK
        pyo3::py_run!(py, my_class, "my_class.my_attribute = 'foo'");

        // Also OK
        pyo3::py_run!(py, my_class, "assert my_class.my_attribute == 'foo'");
    });
}

Hmm interesting. I suspect this is a behavioural change we missed when we switched to "heap types" to support abi3 - see https://pyo3.rs/v0.16.4/migration.html#runtime-changes-to-support-the-cpython-limited-api

Type objects are now mutable - Python code can set attributes on them.

I'm unsure if this is something we should aim to fix, or just accept that it's been this way for a year and a half and update documentation?

I'm unsure if this is something we should aim to fix

I think so yes. I would be really surprised if I wrote:
#[pymethods]
impl MyClass {
    #[classattr]
    fn my_attribute() -> String {
        "hello".to_string()
    }
}

and python code was able to change it. IMO that kind of behaviour should be an opt-in. Maybe something like (to be bikeshedded) #[pyo3(changeable_from_python].

Can you overwrite methods from pymethods by reassigning them on the class? If yes, I don't see why class attrs are different.

For what it's worth, a quick search suggests the type flag we'd want to use to implement this is only present in python 3.10: https://docs.python.org/3/c-api/typeobj.html#Py_TPFLAGS_IMMUTABLETYPE
I think for older versions than 3.10 the only way to protect would be a custom metaclass?

Can you overwrite methods from pymethods by reassigning them on the class? If yes, I don't see why class attrs are different.

Yes

We could set tp_setattro on the type object to point to a function that just returns an error.

I think not on the type but on the type's type, right? i.e. metaclass 😊

Right. So this means we effectively have to support metaclasses?

On Python < 3.10, we can set this inside create_type_object_impl:
unsafe extern "C" fn error_setattrofunc(_slf: *mut ffi::PyObject, _attr: *mut ffi::PyObject, _value: *mut ffi::PyObject) -> c_int {
    let py = Python::assume_gil_acquired();

   PyTypeError::new_err("cannot set '...' attribute of immutable type '...'").restore(py);
    -1
}

(*(*type_object).ob_type).tp_setattro = Some(error_setattrofunc);

I've always thought of native classes being immutable as a natural default and an advantage. I would like to restore this behaviour, if you all agree.

I've always thought of native classes being immutable as a natural default and an advantage. I would like to restore this behaviour, if you all agree.

I agree it would be nice to restore this behaviour, but I think it's potentially hard - AFAIK we can't achieve it for the older Pythons without writing a custom metaclass.
I think writing a custom metaclass isn't fun even in pure-Python. There's also a question of where our custom metaclass would live - would it be global data shared amongst all PyO3 objects? How would it interact if multiple packages with different versions of PyO3 are all in use?
If you're feeling brave, please do stab at this! It might take a few attempts for us to figure out what works nicely.

Edit: Or is this mutating type?

Precisely :). If we had out own metaclass, *(*type_object).ob_type) would be our metaclass instead of type.

I agree it would be nice to restore this behaviour, but I think it's potentially hard - AFAIK we can't achieve it for the older Pythons without writing a custom metaclass.

That, and I also think it's unnecessary. "C extension" classes behaving different from normal classes was always an artifact of the non-heaptype implementation. Monkey-patching methods and attributes is a fact of life in Python, and oftentimes even helpful.

Monkey-patching methods and attributes is a fact of life in Python, and oftentimes even helpful.

I think that largely depends on perspective. It's certainly nice when you, as a user, just want to make something work in a dirty way. As a library author it's terrifying that people can just reach into your implementation details and change stuff. When cpython did the static-> heap type conversion, the new mutability was considered a problem.
Anyway: I don't think we can do this with limited api. As we wouldn't be able to do it consistently we might as well ditch the metaclass idea and only do it on 3.10+ with the Py_TPFLAGS_IMMUTABLETYPE flag. I still think that is preferable over current, but I'm not a fan of the inconsistency.
Also: this gave a me an idea for a new crate :)

Perhaps we should have a #[pyclass(immutable_type_object)] opt-in? We could then document that It only works properly on 3.10+?

Coming back to this, I think we should just add the opt in and leave the default unchanged. I think doing so is a relatively small macro addition to set the flag, so I'll mark this as a good first issue.

Perhaps we should have a #[pyclass(immutable_type_object)] opt-in? We could then document that It only works properly on 3.10+?

I looked into implementing this flag, but ran into a problem. If we mark the type object as immutable on creation, we can't add class attributes to it anymore, because they are set with PyObject_SetAttrString on the finished type object (which fails, because it's immutable). I'm not sure if there is (currently) a way to either ignore the immutable flag while setting these, or set the flag only after we're finished mutating. It looks like Python 3.14 will add PyType_Freeze for this purpose, so it probably makes sense to wait for that.


Pagespeed On as a variable?

Is it possible to have Pagespeed on as a variable?
We are using lua and openresty to set a list variables and was wondering if its possible with the pagespeed main on/off variable? We have got EnableFilters working.
pagespeed on; #on/off
pagespeed EnableFilters "$pagespeed_vars";

We have tried
set $pagespeed_on "on";
pagespeed $pagespeed_on; #on/off
pagespeed EnableFilters "$pagespeed_vars";

set $pagespeed_on on;
pagespeed "$pagespeed_on"; #on/off
pagespeed EnableFilters "$pagespeed_vars";

but have had no success and cant see anything in the docs. Is this possible?
We have pagespeed ProcessScriptVariables all; enabled

I had a look, and unfortunately supporting scripting of pagespeed on|off would need some additional handling to get it to work.
You maybe able to get close to what you want by conditionally disabling filters plus toggling InPlaceResourceOptimization?

@oschaaf will give this ago, and let you guys know how I get on. Thank you!

@oschaaf I managed to fix this by simply setting the PageSpeed=off header


:bulb: Switching Build to poetry :grey_question:

Why?

Why?

Why not ;-p
More seriously because it may be easier to maintain and produce wheel and other cool stuf without any effort.
It was just an idea. I gave it a try (as a Python noob) and could build/release package very easily.

Thanks for the suggestion!
Hatchling is also easy to maintain, and I have automation to:

Draft releases from merged PRs using labels matching https://keepachangelog.com
Automatically select the next version number based on SemVer changes
Part of this is due to the hatch_vcs plugin that takes the version number from the Git tag
Create source distribution and wheel files on the CI, and upload them directly to PyPI
Two-click release process: edit the draft, click "Publish". Means I can release using my phone :)

For a long time there was really only option for Python (setuptools), but now things have improved and there's lots of choices (if you don't have C/C++ extensions). That means choosing which to use is the difficult thing :)  Many are excellent, so it doesn't really matter which you use. I like hatchling because it's following standards, the maintainer is very helpful, and because of the hatch_vcs plugin.

I had never heard of pypa/hatch : thanks a lot for the tip :pray:

See also https://packaging.python.org/en/latest/tutorials/packaging-projects/ and https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html for some more options.

:ok_hand:


DS-3154 : Disable 'doclint' checks by default when building with Java 8 or above

See https://jira.duraspace.org/browse/DS-3154
Because of the number of javadocs errors in DSpace code, we've decided to disable the doclint checks by default. This PR adds a Profile which disables doclint if you are running Java 8 or above.

Reviewed and approved in today's DevMtg. Merging


Prettify the JSON and YAML views

We should highlight the JSON and YAML data in the several views that show it. E.g. https://www.prettifier.net/json/
Acceptance Criteria:

[ ] The JSON data is highlighted
[ ] The YAML data is highlighted

fixes #38

@joaquimrocha this can be closed now

We can close it. But we should assign the dark theme everywhere because of that issues with the singleton editor theme.


Request for Preprocessed WHO General Debates Dataset

Thank you for the fantastic repository! I would like to request the preprocessed WHO General Debates dataset for a dynamic topic modeling project I’m working on.
I appreciate your help!

WHO dataset has been uploaded.
Thank you for your interest in our work. It would be great if you can leave us a star!

Dear @BobXWu,
Thank you for uploading the Preprocessed WHO dataset!
I appreciate your hard work and dedication to making this valuable resource available.
I will definitely leave a star as a token of my appreciation!
Best regards,
Manh Do.


Unable to build label_image example, master branch

I am on OSX 10.11.12 (El Capitan)
Installed from source, on master branch
git rev-parse HEAD: a566a7701381a5cf7f70fce397759483764e482
bazel version: 0.3.2-homebrew
I am getting a series of errors when trying to build the label_image example from a freshly downloaded and configured (all default options, no CUDA, GPU, or Hadoop support) tensorflow source.
bazel build tensorflow/examples/label_image ...
output:
ERROR: /Users/corey/Documents/school/hpc/tensorflow/tensorflow/core/BUILD:353:1: C++ compilation of rule '//tensorflow/core:string_ops_op_lib' failed: cc_wrapper.sh failed: error executing command external/local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wthread-safety -Wself-assign -fcolor-diagnostics -fno-omit-frame-pointer '-std=c++0x' -MD -MF ... (remaining 92 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
tensorflow/core/ops/string_ops.cc:186:11: error: return type 'const ::tensorflow::Status' must match previous return type 'tensorflow::Status' when lambda expression has unspecified explicit return type
TF_RETURN_IF_ERROR(c->Merge(out, c->input(i), &out));
^
./tensorflow/core/lib/core/errors.h:43:42: note: expanded from macro 'TF_RETURN_IF_ERROR'
if (TF_PREDICT_FALSE(!_status.ok())) return _status;
^
tensorflow/core/ops/string_ops.cc:216:7: error: return type 'tensorflow::Status' must match previous return type 'const ::tensorflow::Status' when lambda expression has unspecified explicit return type
return Status::OK();
^
tensorflow/core/ops/string_ops.cc:208:17: error: no viable conversion from 'tensorflow::(lambda at tensorflow/core/ops/string_ops.cc:208:17)' to 'tensorflow::Status (*)(shape_inference::InferenceContext )'
.SetShapeFn([](InferenceContext c) {
^~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/ops/string_ops.cc:208:17: note: candidate function
./tensorflow/core/framework/op.h:247:16: note: passing argument to parameter 'fn' here
Status (fn)(shape_inference::InferenceContext)) {
^
3 errors generated.
Thanks for any advice or help!

Try updating your xcode. See also: tensorflow/models#130

@ctames Just in case it helps, your command works with the current master:
f794cd393b1e7821fcc3cdcee9b6a4400f2540bf refs/remotes/origin/HEAD

One thing, though, is that I am still on Bazel 0.3.1. No upgrade to Xcode at all (still 7.3).


Fix for posting video stories

Currently you're setting media_type to 0 which makes it impossible to use the method to add a video to your story. The pull request makes media_type an optional argument.

Thanks!


Add ai-git-assistant extension

Description
The primary function of this extension is to generate Git commit messages using Raycast's AI and to feed from the diff and status outputs of your repository.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @Popalay 👋
I like the idea a lot - what about instead rely on getSelectedFinderItems (and taking the files current directory)?

Hi @Popalay 👋
I like the idea a lot - what about instead rely on getSelectedFinderItems (and taking the files current directory)?

Hey @pernielsentikaer
This is a good idea, but in this case the usage of the extension changes a bit. With your proposal, choosing the git repo folder is required each time to generate a commit message. I want to make this experience more smooth w/o any required step expect the initial configuration. Do you have something in mind to make it possible? Thanks!

I think I can utilize the getSelectedDir method and if it returns something, presave the output for the next calls. In this case it will be possible to generate messages for the same repo w/o selecting the same repo twice. What do you think? @pernielsentikaer

@pernielsentikaer Broke down my branch history by trying to push changes instead of using the publish command. Opened a new PR. Please take a look.


Audio track title truncation

Description

Currently audio track titles can be any length, which can really alter the appearance of the UI. We should constrain these to one or two lines:

one line

two lines

@panchovm which of these do you think is better?
Resolution

[ ] 🙋 I would be interested in resolving this bug.

I vote for a third one, the Row L component. It seems better to use it for breakpoints where we see the viewport space reduced. The only component version where titles look good is on mobile is in Row S.
Notice that Row L also truncates audio title, but the remaining space is safer than Row M.
Row L

@panchovm Currently, L is used when the filters are open, and M is used when they are closed. Are you suggesting we use L all of the time on desktop?

No. I meant to use Row L in breakpoint md (from 768px to 1023px), and when filters are open, keeping the L version but with the wave and audio info area smaller.
Here is a screenshot with viewport as 900px width.


Update OnHelpMeChooseAccountStorage uri

Update OnHelpMeChooseAccountStorage uri

Thanks for reporting, I will merge this.

Bump

Released in v1.5.0


BUG about shape_infer()

I think nodes like or can be used without shape_infer?
File "/home/xxxx/anaconda3/envs/onnx/lib/python3.8/site-packages/onnx_tool/node.py", line 158, in value_infer
  raise NotImplementedError(f'this Node {self.op_type}-{self.name} has no value_infer')
NotImplementedError: this Node Or-/Or has no value_infer

Do you mean without value_infer?

I think the real problem here is your model with Or operator is not supported.

Thanks for your answer.
I guess that or operator is not supported. Could you teach me how to manually support or skip the or operator?
I tried to skip this operator in the code,
https://github.com/ThanatosShinji/onnx-tool/blob/f06228c4edce44bc33025db9b1bbcbd018173d9f/onnx_tool/graph.py#L823C37
but this will affect the shape infer of subsequent operators. I am confused about this and don't know how to solve it.

I've added this operator to the main branch. you can check out this branch to use.

Thanks for your quick reply!


open source data files for registerLocalNameConstants

registerLocalNameConstants needs a bunch of data files that give the names of each locale written in the other locales. See here:
https://github.com/google/closure-library/blob/5769370ad747affd84b4df37d39f4f2b50371ed0/closure/goog/locale/countrylanguagenames_test.js#L37
 // Test data from //googledata/i18n/js_locale_data/LocaleNameConstants__de.js

would it be possible to open source these data files? i'm pretty sure they're generated from cldr.

Hi Nick, for the moment we are not planning to make this data publicly available. We are planning to reimplement the NativeNames and LocalizedNames APIs which will require new locale data files which we are going to make available.

cool! do you have any idea when that might happen?


No longer extract ancillary layers by default through ariaTSsetup

Following convo with @mgovorcin and @dbekaert , adjust behavior of ariaTSsetup.py to no longer extract ancillary layers (i.e. 'solidEarthTide,ionosphere,troposphereTotal') by default. They now have to be explicitly specified in the commandline.
To test out these changes, refer to the following minimum working example:

Download a subset of version 3 products over southern California: ariaDownload.py --num_threads 16 -b '33.4 34.5 -119.0 -117.4'  -s 20190101  -e 20190216 -t 64 --version 3_0_1 -o Download

Test out default behavior of ariaTSsetup.py (i.e. layers 'solidEarthTide,ionosphere,troposphereTotal' should be missing from the specified output directory -w ts_default): ariaTSsetup.py -f "products/*.nc" -b '33.6 34.3 -118.5 -117.5' -mo 5800 --verbose -of ENVI -w ts_output --log-level debug

Explicitly specify extraction of ancillary layers (i.e. layers 'solidEarthTide,ionosphere,troposphereTotal' should be found in specified output directory -w ts_output_ancillarylyrs): ariaTSsetup.py -f "products/*.nc" -b '33.6 34.3 -118.5 -117.5' -mo 5800 --verbose -l 'solidEarthTide,ionosphere,troposphereTotal' -tm HRRR -of ENVI -w ts_output_ancillarylyrs --log-level debug

Note the -mo 5800 should be specified here to reject short IFGs that do not meet the defined spatial threshold of coverage (i.e. 5800 km^2) WRT to the specified bbox. See a relevant discussion on this here.

Given the logic changes i would suggest a few additional tests @sssangha:

Test this for a mixed set of products forcing it not to extract layers.
Test this for mixed set of product and forcing to extract the layers (even though they dont exist..).

@alexfore thanks for your input and helping me track down an issue.
Looks like the logic I had in the code did not appropriately account for NISAR GUNW products when trying to extract tropo layers (which don't have denoted model names in their paths like their S1 GUNW counterparts do). I made a tweak to account for this, let me know if you advise I adjust it for clarity.
And yes, this PR would lead to changes in the golden outputs as the expected behavior changes. Let me please regenerate them, adjust the coordination doc to reflect these changes, + LFT the products to you

Given the logic changes i would suggest a few additional tests @sssangha:
1. Test this for a mixed set of products forcing it not to extract layers.

2. Test this for mixed set of product and forcing to extract the layers (even though they dont exist..).

Let me add this to the golden

Given the logic changes i would suggest a few additional tests @sssangha:
1. Test this for a mixed set of products forcing it not to extract layers.

2. Test this for mixed set of product and forcing to extract the layers (even though they dont exist..).

Ok, @dbekaert I have a test that addresses this.
Download a mix of v2 and v3 products:
ariaDownload.py -t 137 --bbox '40.8 42.3 -122 -120' -i 20210330_20200329 -o Download
ariaDownload.py -t 137 --bbox '40.8 42.3 -122 -120' -i 20220331_20220319 -o Download
ariaDownload.py -t 137 --bbox '40.8 42.3 -122 -120' -i 20230829_20230724 -o Download
ariaDownload.py -t 137 --bbox '40.8 42.3 -122 -120' -i 20230829_20230817 -o Download

Test this for a mixed set of products forcing it not to extract layers:
ariaTSsetup.py -f "products/*.nc" --verbose -of ENVI -w ts_output --log-level debug

As expected, no ancillary layers are extracted by default (even when present for the v3 products:
ls ts_output
azimuthAngle  bPerpendicular  coherence  connectedComponents  DEM  export_workers  full_product_dict.json  incidenceAngle  lookAngle  productBoundingBox  stack  unwrappedPhase  user_bbox.json

Test this for mixed set of product and forcing to extract the layers (even though they dont exist..):
ariaTSsetup.py -f "products/*.nc" --verbose -of ENVI -l 'solidEarthTide,ionosphere,troposphereTotal' -tm HRRR -w ts_output_ancillarylyrs --log-level debug

Here is a list of all of the output layers:
ls ts_output_ancillarylyrs
azimuthAngle  bPerpendicular  coherence  connectedComponents  DEM  export_workers  full_product_dict.json  incidenceAngle  ionosphere  lookAngle  productBoundingBox  solidEarthTide  stack  troposphereTotal  unwrappedPhase  user_bbox.json

The ancillary layers are extracted ONLY for the v3 pairs.
Compare the unw phase vs tropo outputs:
ls ts_output_ancillarylyrs/unwrappedPhase/
20210330_20200329          20210330_20200329.hdr  20220331_20220319          20220331_20220319.hdr  20230829_20230724          20230829_20230724.hdr  20230829_20230817          20230829_20230817.hdr
20210330_20200329.aux.xml  20210330_20200329.vrt  20220331_20220319.aux.xml  20220331_20220319.vrt  20230829_20230724.aux.xml  20230829_20230724.vrt  20230829_20230817.aux.xml  20230829_20230817.vrt

ls ts_output_ancillarylyrs/troposphereTotal/HRRR/
20220331_20220319          20220331_20220319.hdr  20230829_20230724          20230829_20230724.hdr  20230829_20230817          20230829_20230817.hdr  dates
20220331_20220319.aux.xml  20220331_20220319.vrt  20230829_20230724.aux.xml  20230829_20230724.vrt  20230829_20230817.aux.xml  20230829_20230817.vrt

And not for the v2 pair (*20210330_20200329*):
ls products/*20210330_20200329*
products/S1-GUNW-A-R-137-tops-20210330_20200329-015957-41895N_400275N-PP-1ce2-v2_0_4.nc  products/S1-GUNW-A-R-137-tops-20210330_20200329-020019-43055N_41517N-PP-8010-v2_0_4.nc

Using that code change then I modified the tests/regression/run_tssetup_test.py tssetup run script to extract those layers again. Now all of the tests pass so these code changes could be merged. However, the next issue seems to be that you guys want to add more test cases / or replace the current tssetup test case?

Regarding the golden test data which was sent via LFT:

The products in this are not the same as those which are obtained if I use the four ariaDownload.py commands above. Is this intentional or an oversight? (13 versus 2 netcdf files). Both of the products which were included in the golden test data via LFT are v3_0_0 files.

Can we replace the previous tssetup case with one of these cases?

Using that code change then I modified the tests/regression/run_tssetup_test.py tssetup run script to extract those layers again. Now all of the tests pass so these code changes could be merged. However, the next issue seems to be that you guys want to add more test cases / or replace the current tssetup test case?

What you did to the run_tssetup_test.py suffices. I don't think we should add another test case. Apologies for the confusion.

Regarding the golden test data which was sent via LFT:
* The products in this are not the same as those which are obtained if I use the four ariaDownload.py commands above. Is this intentional or an oversight? (13 versus 2 netcdf files). Both of the products which were included in the golden test data via LFT are v3_0_0 files.

* Can we replace the previous tssetup case with one of these cases?

No, those 4 ariaDownload cases are unrelated to the golden outputs and shouldn't be reflected in the golden outputs. Whatever I shared in that comment was meant to address the questions @dbekaert raised. I think we could proceed as is. Thanks again @alexfore !


Authentic domain being blocked

Hello,
HOSTS file block click.discord.com which is an authentic domain that verifies the geolocation of the user and validate their IP address to be able to login to the Discord app.
Please whitelist this domain, it's not ad, malware, annoyance or anything else.
Domian: https://click.discord.com
Kind regards

click.discord.com is also used to verify email address for discord

This issue has been discussed before.
click.discord.com is primarily used for tracking links in emails, and as such StevenBlack has decided to blocklist it.
Unless new information has come to light, I doubt they will reconsider.
In the future, please check for existing issues before opening a new one.
Thank you

This issue has been discussed before.
click.discord.com is primarily used for tracking links in emails, and as such StevenBlack has decided to blocklist it.
Unless new information has come to light, I doubt they will reconsider.
In the future, please check for existing issues before opening a new one.
Thank you

If it's been discussed then it should be unblocked. The link also has legitimate use besides tracking - you cannot confirm the creation of discord account unless you go through that link, which they provide only though click.discord.com and theres no other way. Blocking this makes discord unusable.

click.discord.com is primarily used for tracking links in emails

and the policy of this list is to block any website which is primary used for tracking.
If you disagree with that policy, you may allowlist the domain yourself.
Additionally, you can contact Discord and request they stop tracking their users. Ultimately, it is their fault for using a tracking domain in account creation emails. Obviously they probably won't care, but it's worth a try.
In any case, I am not the maintainer of this list; this is not my decision to make. I am just trying to provide information.
Thank you.

@m-klecka and @wealstarrr this issue should be raised with Discord. Tell them, mixing scummy into their core workflows is a choice. Discord gets no free pass here.
Thank you for the assist @iam-py-test.


Add Dynamic for DynamicArray's count

It would be great to add Dynamic for DynamicArray's count, so we could write something like:
viewModel.categories.dynCount.map { "($0)" } ->> cell.countLabel

Good idea :)


Add MS IP Exclusion Flag to policy settings

This Change requires https://github.com/cloudflare/cloudflare-go/pull/1205 to be released in order for tests to pass.

TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareDeviceSettingsPolicy_" -count 1 -parallel 1 -timeout 120m -parallel 1
=== RUN   TestAccCloudflareDeviceSettingsPolicy_Create
--- PASS: TestAccCloudflareDeviceSettingsPolicy_Create (24.57s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	25.120s


Hundreds of "SyntaxWarning: invalid escape sequence"

Same issue as https://github.com/Azure/azure-cli/issues/28829. ruff check ./src --select W605 --ignore-noqa finds 1113 errors.
@bebound you might want to know

Thank you for opening this issue, we will look into it.

@ extension developers' attention, you can find the guide to fix this in https://github.com/Azure/azure-cli/issues/28829
Find developer based on latest commit
These extensions have not been updated for a long time: dms, resource-graph, swiftlet
aosm @jordlay @Cyclam
arcgateway @yaotongms
astronomer @necusjz
attestation @kairu-ms
billing_benefits @gaoyp830
communication @v-vprasannak
confluent @DeepikaNMS
connectedmachine @yaotongms
databox @Jing-song
datamigration @ashutoshsuman99 @gansach
dataprotection @zubairabid
devcenter @am-lim
eventgrid @Jing-song
hdinsightonaks @yuc-Li
image_gallery @Jing-song
k8s_runtime @ddadaal
keyvault_preview @evelyn-ys
mcc @dcwell
mixed_reality @calvinhzy
mobile_network @Jing-song
monitor-control @AllyW
new_relic @dipeshbhakat-microsoft
providerhub,quota @gaurimadhok
reservation @gaoyp830
site-recovery @calvinhzy
spring-cloud @AllyW
spring @sophiaso
stream-analytics @jsntcy
support @RudraSharma93Microsoft
timeseriesinsights @calvinhzy
vmware @jonathanhe-msft
workloads @jaskisin


Use ros2 contol test assets

All controllers use ros2_control_test_assets package added in ros-controls/ros2_control#289.
Related to ros-controls/ros2_control#208

@destogl I've rebased this branch to get an up-to-date CI run

Codecov Report

Merging #138 (d48dcdb) into master (59cf934) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #138     +/-   ##
=========================================
  Coverage   35.52%   35.52%
=========================================
  Files          48       24     -24
  Lines        4492     2246   -2246
  Branches     2896     1448   -1448
=========================================
- Hits         1596      798    -798
+ Misses        264      132    -132
+ Partials     2632     1316   -1316

Flag
Coverage Δ

unittests
35.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...include/joint_trajectory_controller/trajectory.hpp

...ler/test/test_load_joint_trajectory_controller.cpp

...ectory_controller/test/test_trajectory_actions.cpp

...ory_controller/test/test_trajectory_controller.cpp

...int_trajectory_controller/test/test_trajectory.cpp

...ory_controller/test/test_trajectory_controller.cpp

...int_trajectory_controller/test/test_trajectory.cpp

...ntroller/test/test_load_joint_state_controller.cpp

...ntroller/test/test_trajectory_controller_utils.hpp

...ollers/test/test_joint_group_effort_controller.cpp

... and 62 more


Ship manuals and tests with package

Thanks for the pull request. What's the rationale behind these changes?
Manual pages could be included in the package but pip won't install them in the proper location.
What's the use of having test cases in the package?

So one could run the tests and install the manual pages, specifically as part of building a distro package:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=termtosvg
Eg. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=xandikos

I see! Thanks for working on the AUR package.
I've included all tests in the package and I've also set up a test suite so that all tests can be run with python -m unittest termtosvg.tests.suite.
Does that look good?

Even better! Wish more projects utilized the test suite feature.

Merged, thanks again! Let me know if you're facing problem with packaging.

Would you be willing to do a patch release for this?

Generally speaking, one is supposed to have the testsuite run in the source tree, not install it as end-user code.

>>> print(os.getcwd())
/home/user/.vim/plugged/vim-rst-sections/ftplugin/vim_bridge
>>> import vim_bridge.registry
>>>


add Mina protocol and Celestia to trsut wallet

https://github.com/MinaProtocol/mina
https://github.com/celestiaorg

Hi @kubektl, Celestia has been added to WalletCore and WalletKit already. I cannot tell if it will be added to TrustWallet app soon or not.
Mina protocol is not in our roadmap at the moment


README.md: improve install instructions

This PR updates the readme's installation instructions to reference the queries directory nested under the topiary-queries crate. This is consistent with the example export TOPIARY_LANGUAGE_DIR command that appears soon after.

Sorry it took so long, this change is obviously correct!


Add 1-Layer and 2-Layer LCA Implementations for CPU Backend

Issue Number:

Objective of pull request:
Add 1-Layer and 2-Layer LCA Implementations for CPU Backend
Pull request checklist
Your PR fulfills the following requirements:

[ ] Issue created that explains the change and why it's needed
[X] Tests are part of the PR (for bug fixes / features)
[ ] Docs reviewed and added / updated if needed (for bug fixes / features)
[X] PR conforms to Coding Conventions
[ ] PR applys BSD 3-clause or LGPL2.1+ Licenses to all code files
[X] Lint (pyb) passes locally
[X] Build tests (pyb -E unit) or (python -m unittest) passes locally

Pull request type

Please check your PR type:

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation changes
[ ] Other (please describe):

What is the new behavior?

1 and 2 Layer LCA models are added

Does this introduce a breaking change?

[ ] Yes
[X] No

Supplemental information

Thanks for taking a look over the code! I should be able to make edits next week.
I'm conflicted on whether the LCA neuron and Accumulator neuron should be their own processes or LIF processes. Initially I had them as LIF processes, but I implemented them in microcode as well which led me towards the current design. My main concern is I don't think process models should differ in behavior for the same process.
The Accumulator neuron is the most reasonable to be a LIF process, it just would be a non-leaky, graded TernaryLIF. None of the lava LIF process models support graded spikes right now so it would be a separate process model.
The LCA neuron is graded with a soft-threshold activation, doesn't reset the voltage, and has a self-reinforcement term for the two-layer model. So while it has similar parameters to a LIF neuron, the behavior is quite different.
In both cases there would be new process models with a "LCA" tag which would need to be used in the run configuration. Also, if the models inherit most of the dynamics from an existing fixed and floating point LIF, this likely requires the separate subprocess models for since the fixed and floating point models define du differently: (4095 vs 1 - a perfect example of what I want to avoid with having everything as a LIF).

As a reference, here's the version with LIF models (I used exception_proc_model_map instead of tags to select these in the run config):
#  Copyright (C) 2023 Battelle Memorial Institute
#  SPDX-License-Identifier: BSD-2-Clause
#  See: https://spdx.org/licenses/

import numpy as np

from lava.magma.core.model.sub.model import AbstractSubProcessModel
from lava.magma.core.model.py.ports import PyOutPort
from lava.magma.core.process.process import AbstractProcess
from lava.magma.core.model.py.type import LavaPyType
from lava.magma.core.resources import CPU
from lava.magma.core.sync.protocols.loihi_protocol import LoihiProtocol
from lava.magma.core.decorator import implements, requires, tag
from lava.proc.lif.process import TernaryLIF, LIF
from lava.proc.dense.process import Dense
from lava.proc.lif.models import AbstractPyLifModelFloat, PyLifModelBitAcc, PyTernLifModelFixed

from lca.processes import LCA2Layer

@implements(proc=LIF, protocol=LoihiProtocol)
@requires(CPU)
@tag('floating_pt')
class PySoftThresholdFloat(AbstractPyLifModelFloat):
    # This model might spike too frequently. Implement an accumulator if so.
    s_out: PyOutPort = LavaPyType(PyOutPort.VEC_DENSE, float)
    vth: float = LavaPyType(float, float)

    def subthr_dynamics(self, activation_in: np.ndarray):
        # Its easier to add the self-reinforcement term here than to have a recurrent connection.
        super().subthr_dynamics(activation_in + self.spiking_activation() * self.dv)

    def reset_voltage(self, spike_vector: np.ndarray):
        # Don't reset voltage
        return

    def spiking_activation(self):
        return np.sign(self.v) * np.maximum(np.abs(self.v) - self.vth, 0)

@implements(proc=LIF, protocol=LoihiProtocol)
@requires(CPU)
@tag('fixed_pt')
class PySoftThresholdFixed(PyLifModelBitAcc):
    def subthr_dynamics(self, activation_in: np.ndarray):
        prev_spike_vector = self.spiking_activation()
        super().subthr_dynamics(activation_in)

        decay_const_v = self.dv + self.dm_offset

        neg_voltage_limit = -np.int32(self.max_uv_val) + 1
        pos_voltage_limit = np.int32(self.max_uv_val) - 1
        spike_feedback = np.int64(prev_spike_vector) * decay_const_v
        spike_feedback = np.sign(spike_feedback) * np.right_shift(np.abs(spike_feedback), self.decay_shift)
        spike_feedback = np.int32(spike_feedback)
        self.v[:] = np.clip(self.v + spike_feedback, neg_voltage_limit, pos_voltage_limit)

    def reset_voltage(self, spike_vector: np.ndarray):
        # Dont reset voltage
        return

    def spiking_activation(self):
        return np.sign(self.v) * np.maximum(np.abs(self.v) - self.effective_vth, 0)

@implements(proc=TernaryLIF, protocol=LoihiProtocol)
@requires(CPU)
@tag('floating_pt')
class PyAccumulatorFloat(AbstractPyLifModelFloat):
    # The graded spike LIF neuron was removed in Lava 0.4 so this reimplements the functionality
    s_out: PyOutPort = LavaPyType(PyOutPort.VEC_DENSE, float)
    vth_hi: float = LavaPyType(float, float)
    vth_lo: float = LavaPyType(float, float)

    def reset_voltage(self, spike_vector: np.ndarray):
        self.v[spike_vector != 0] = 0

    def spiking_activation(self):
        return self.v * np.logical_or(self.v > self.vth_hi, self.v < self.vth_lo)

@implements(proc=TernaryLIF, protocol=LoihiProtocol)
@requires(CPU)
@tag('fixed_pt')
class PyAccumulatorFixed(PyTernLifModelFixed):
    def spiking_activation(self):
        return self.v * np.logical_or(self.v > self.vth_hi, self.v < self.vth_lo)

@implements(proc=LCA2Layer, protocol=LoihiProtocol)
@tag('floating_pt')
class LCA2LayerModelFloat(AbstractSubProcessModel):
    def __init__(self, proc: AbstractProcess):

        threshold = proc.threshold.get()
        dt = proc.dt.get()
        tau_rc = proc.tau_rc.get()
        T = dt / tau_rc
        weights = proc.weights.get()
        input_val = proc.input.get()

        self.v1 = LIF(shape=(weights.shape[0],), du=1, vth=threshold, dv=T, v=0, u=0, bias_mant=0)
        self.weights_T = Dense(weights=-weights.T, num_message_bits=24)

        # LIF in place of Accumulator
        self.res = TernaryLIF(shape=(weights.shape[1],), du=1, dv=0, vth_hi=0, vth_lo=0, bias_mant=input_val)
        self.weights = Dense(weights=(weights * T), num_message_bits=24)

        self.weights.a_out.connect(self.v1.a_in)
        self.res.s_out.connect(self.weights.s_in)

        self.weights_T.a_out.connect(self.res.a_in)
        self.v1.s_out.connect(self.weights_T.s_in)

        # Expose output and voltage
        self.v1.s_out.connect(proc.out_ports.v1)
        self.res.s_out.connect(proc.out_ports.res)
        proc.vars.voltage.alias(self.v1.vars.v)

@implements(proc=LCA2Layer, protocol=LoihiProtocol)
@tag('fixed_pt')
class LCA2LayerModelFixed(AbstractSubProcessModel):
    def __init__(self, proc: AbstractProcess):

        threshold = proc.threshold.get()
        dt = proc.dt.get()
        tau_rc = proc.tau_rc.get()
        T = dt / tau_rc
        T_int = int(T * 4096)
        weights = proc.weights.get() * 2**8
        input_val = proc.input.get()
        input_exp = proc.input_exp.get()

        self.v1 = LIF(shape=(weights.shape[0],), du=4095, dv=T_int, vth=threshold, v=0, u=0, bias_mant=0)
        # weight_exp shifted 8 bits for the weights, 6 for the v1 output.
        self.weights_T = Dense(weights=-weights.T, num_message_bits=24, weight_exp=-14)

        # LIF in place of Accumulator
        self.res = TernaryLIF(shape=(weights.shape[1],), du=4095, dv=0, vth_hi=0, vth_lo=0,
                              bias_mant=input_val, bias_exp=input_exp)

        self.weights = Dense(weights=(weights * T), num_message_bits=24, weight_exp=-14)

        self.weights.a_out.connect(self.v1.a_in)
        self.res.s_out.connect(self.weights.s_in)

        self.weights_T.a_out.connect(self.res.a_in)
        self.v1.s_out.connect(self.weights_T.s_in)

        # Expose output and voltage
        self.v1.s_out.connect(proc.out_ports.v1)
        self.res.s_out.connect(proc.out_ports.res)
        proc.vars.voltage.alias(self.v1.vars.v)

Hello,
I have been attempting to get this pull request working on my end, and am fairly certain I have exhausted most options so decided to reach out. When attempting to run test_fixed.py, I am receiving import errors on lava.lib.optimization.process. However, when I attempt to import just lava.lib.optimization, I have no errors. I ended up grabbing this PR using Github CLI and am certain that I am working with the same files that are most up-to-date. Would love some advice on how to get the test_fixed.py to execute.
Thanks in advance.

Unfortunately I can't reproduce the issue on Mac OS when cloning a fresh copy and installing as described in README.md. You could try manually adding the /src directory to your PYTHONPATH environment variable to see if that helps.

I want to confirm that my setup procedure is correct:

I am going to lava-nc and following the instructions to setup an environment to install lava-nc to (using poetry to finish the env installation).
I remain inside of this newly created and activated environment and following the appropriate instructions listed on the site to do another poetry installation for lava-optimization. I do NOT create a new environment for lava-optimization.
Upon successful installation, I go a "gh pr checkout 200" to grab this pull request's changed files/data.

Would this be the appropriate set of steps in order to get this PR up and running?

I don't know the exact details of the lava-nc setup but it might not be installing lava-optimization in a way that is updated when you checkout the pr. The easiest option is to install directly from the lava-optimization fork (this will automatically install lava-nc as a requirement):
git clone https://github.com/Gavinator98/lava-optimization.git
cd lava-optimization
poetry config virtualenvs.in-project true
poetry install
source .venv/bin/activate
python ./tests/lava/lib/optimization/solvers/lca/test_fixed_pt.py

Additionally there is now a tutorial lava-optimization/tutorials/tutorial_04_lca.ipynb which may be a better starting point than the unit tests.


Remove DecodedType typealias (associatedtype) from Decodable protocol

Addresses #97.
/cc @tarunon

The build failed on Linux with the following error:
$ swift test
Compiling Swift Module 'Himotokitest' (6 sources)
/home/travis/build/ikesyo/Himotoki/Tests/Himotoki/DecodeErrorTest.swift:25:21: error: constructing an object of class type 'Self' with a metatype value must use a 'required' initializer
        return self.init(string: value)!
               ~~~~ ^
Foundation.NSURL:15:24: note: selected non-required initializer 'init(string:)'
    public convenience init?(string URLString: String)
                       ^
<unknown>:0: error: build had 1 command failures
error: exit(1): swift-build-tool -f /home/travis/build/ikesyo/Himotoki/.build/debug.yaml test

@tarunon Do you have any solution or workaround for this?

Yes, self.init(string: value)! is NSURL, not a Self.
I think we should cast NSURL to Self, but we cannot use Self in implement.
I have one idea, I'll make new pr. :3

Yes, self.init(string: value)! is NSURL, not a Self.
I think we should cast NSURL to Self, but we cannot use Self in implement.

I'm not sure why this succeeds on OS X with SwiftPM, but fails on Linux. 🤔

I don't know why... I think Linux is correct.
Because if make NSURL subclass, cannot use self.init(string: String) without override.
It may be swift compiler bug.

Auk,

Yes, self.init(string: value)! is NSURL, not a Self.
I misunderstood this problem, sorry.
It is not necessary that Self has init(string: String) implement.

Okay, this should be good to go now.
@tarunon Do you have further thoughts on this?

Merging this :ship:


(GH-6)(theme) Add theme styling and mobile search usability

In this PR:

Updates usability of search on mobile
Adds styling for added left navigation depth
Adds styling for forms, including custom checkboxes
Updates a page title "Chocolatey Community Repository (CCR)

@designxsteph thank you!


Could io.swagger.parser.v3:swagger-parser-v2-converter:2.0.27-SNAPSHOT drop off redundant dependencies to loose weight?

Hi, I am a user of project io.swagger.parser.v3:swagger-parser-v2-converter:2.0.27-SNAPSHOT. I found that its pom file introduced 53 dependencies. However, among them, 7 libraries (13%) have not been used by your project (the redundant dependencies are listed below). Reduce these useless dependencies can help prevent conflicts between library versions. MeanWhile, it can minimize the total added size to projects. It can also help enable advanced scenarios for this project.
This PR helps io.swagger.parser.v3:swagger-parser-v2-converter:2.0.27-SNAPSHOT lose weight :) I have tested the revised configuration in my local environment. It is safe to remove the unused libraries.
Best regards

Thanks!


Allow optional workingDir for ctx.RunCommand

Hello,
Specifying a working directory when using ctx.RunCommand would be nice.
Would you be open to this idea?

Good idea, thanks


Coerce plugin output key to a string

This line will fail when a plugin specifies its output as an array map of symbols to descriptions. What I usually see are plugins mapping string-to-strings, but since those are constants elsewhere, why not use them there too?
In other words, let the developer say
module SharedValues
  SOME_VAR = :SOME_VAR
end

def self.output
  [
    [SharedValues::SOME_VAR, 'Some output variasble']
  ]
end

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
I had a plugin, and it wouldn't work when I did a bundle exec fastlane action my_action, because of this:
https://github.com/fastlane/fastlane/issues/new
Run `fastlane env` to append the fastlane environment to your issue
bundler: failed to load command: fastlane (/Users/phil_busby/vendor/bundle/ruby/2.3.0/bin/fastlane)
NoMethodError: [!] undefined method `yellow' for :FOO:Symbol
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/documentation/actions_list.rb:149:in `block in print_output_variables'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/documentation/actions_list.rb:149:in `map'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/documentation/actions_list.rb:149:in `print_output_variables'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/documentation/actions_list.rb:61:in `show_details'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/documentation/actions_list.rb:6:in `run'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/commands_generator.rb:234:in `block (2 levels) in run'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:75:in `run!'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/fastlane/lib/fastlane/cli_tools_distributor.rb:98:in `take_off'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/gems/fastlane-2.85.0/bin/fastlane:20:in `<top (required)>'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/bin/fastlane:23:in `load'
  /Users/phil_busby/vendor/bundle/ruby/2.3.0/bin/fastlane:23:in `<top (required)>'

Description

@philihp Hey, thanks for the contribution! This is a small PR but I want to make sure this would be getting merged in for the correct reasons 😊 Is there a specific reason it won't work to define your output with strings as keys? This is method is for documentation purposes (to be read) so it makes sense for everything to be a string already.
The custom action template shows it as a string as well.
      def self.output
        # Define the shared values you are going to provide
        # Example
        [
          ['[[NAME_UP]]_CUSTOM_VALUE', 'A description of what this value contains']
        ]
      end

Forcing these keys to be strings is best for quality as we know exactly what will be outputted otherwise if its a key it will be determined at runtime - which could be a it more fragile 😇

@joshdholtz Of course. It seems to me that if a constant is defined, then we should use it... otherwise what's the point? Lemme take for example gradle.rb. It sets an output lane_context variable using the constant determined at runtime.
Actions.lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH] = File.expand_path(last_apk_path) if last_apk_path

So it should report
def self.output
  [
    ['GRADLE_APK_OUTPUT_PATH', 'The path to the newly generated apk file. Undefined in a multi-variant assemble scenario']
  ]
end

should be
def self.output
  [
    [SharedValues::GRADLE_APK_OUTPUT_PATH, 'The path to the newly generated apk file. Undefined in a multi-variant assemble scenario']
  ]
end

As far as I could see, every SharedValues::FOO defined to :FOO, so I don't think this adds much more cognitive load, but would also protect against the case where the reported string here actually falls out of sync with what the actual defined value is.
Additionally, someone reading the source would see this and know hey, if i want to use this value, i need to do lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH], rather than lane_context['GRADLE_APK_OUTPUT_PATH'].

Also, I'm down to go through all the actions and make that change... because consistency is also a good thing.

@philihp Thanks for taking the time to explain that! You really put up a good viewpoint 😊 However, I think we would really like to keep the keys of the hash a string as that field is meant to be static - since its for static documentation.
Our documentation for fastlane (docs.fastlane.tools) gets generated off of these static metadata action/plugin fields like 'output, return_value, authors, etc). So for consistency and quality sake, I think we would really prefer to keep the output` keys as a static string as well so we know exacly what will be generated for documentation 🙃
Your proposed changed isn't something super dynamic but its dynamic enough where we might need to do some sort of validation when documentation gets generated to make sure that all keys generated to their proper string version.
Also, running fastlane action gradle shows out to use the output variable names already so stringing the key would add a little redundancy 😇

I understand where you're coming from. Could I ask how the documentation is generated? Can I run that locally? I'd like to see how this method is used aside from printing to the console.

@philihp Turns out... it the docs don't actually look at output yet but I will be adding that tonight 😬 - https://github.com/fastlane/fastlane/blob/master/fastlane/lib/assets/ActionDetails.md.erb

Created issue #12061 to show that cause it really should


Content Structure

I had a quick read through the V2 website in Vienna and think that we could maybe improve the content structure. Since I haven't had the time to discuss this on the meetup, I will just post it here as reminder.

Get Started

Setup
Create State (define model)
Render State (define view and pull state)
Update State (add action chains to controller)

Concepts

Single state
Data flow
Actions
Chains
Signals

Advanced (is this really advanced?)

Routing
Choosing a model layer (immutable or not)
Serivces
Computed
Modules
Context Providers

Best Practices

Folder structure
Naming conventions
Storing module state
…

API

…

Yes! Rename Advanced to Getting Real™???
In all seriousness, it's not "Advanced" its stuff you absolutely need to make an app.

BAM and there it is!! We should also make it a sticker and a tshirt :)

Hmm, I really like @maxfrigge variant.

Wow... I never saw this! Haha, yeah, lets take this in for Cerebral2 :)
Yeah, I agree @Guria. In the setup, let the user clone a repo that is basically empty. Just has some imports ready for the tutorial.

Get started

Setup (Clone a tutorial with webpack-dev-server)
Add state
Render
Signal
Challenge

Then the tutorial repo will have a solution branch that shows an approach to solving the challenge. Anyways... will review items in structure, but like it :)


how to use the compare update operation?

I chose a compare update, but I couldn't find the action button for the merge a line.

Why is there no way to provide a merge code when comparing changes?

I'm not exactly sure what you are asking for here, but VS Code doesn't offer much control/extensibility of its diff view (the image you posted above). There a requests opened for VS Code to offer buttons/actions to move/copy lines between each side, etc. Is that what you are asking about?

@eamodio
This is a comparison of git conflicts. The left side is the remote resource and the right side is the local resource.
As you said, I hope to be able to offer buttons/actions to move/copy lines between each side, the purpose is to compare conflicts and then selectively merge conflicting content.

Duplicate of https://github.com/eamodio/vscode-gitlens/issues/647


Consistency check at blaze-server startup.

Make yaml file default to None -- expectation is that if user doesn't
specify a yaml file explicitly, will use dynamic addition.
Adds consistency check at server startup.

@necaris This is a small tweak / fix to blaze server -- could you take a look?

@kwmsmith Looks good! 👍


Elapsed Duration functionality for the Decoder/LoopedDecoder

The commits add a member to the Decoders, which contains the required information for the elapsed duration.
The functionality is implemented in the impl<R> Iterator for Decoder<R>/LoopedDecoder<R> and ticks an AtomicUsize up each read sample. With the channel count and sample rate the effective elapsed duration of a Decoder can be calculated.

This could maybe be a solution to #474
The total duration can be gotten beforehand from the decoder and be cached for later use.

sorry, but ping?

This might fit better as a new method on Source with a default implementation returning None (just like try_seek). Will be a little more work since now all the adapters need to be adjusted. Though one can easily follow what try_seek does for most cases.
The bigger question is what to do about Sink. Since that is what most media player like uses for rodio will use.

Really nice! Am using rodio for a small music app, and would be very helpful to have this feature.

Note for myself in the future:
Implement this through adding a new source wrapping whatever is beneath.

The new source keeps track of the position (number of samples * sample rate for each frame).
Will work universally on any source.
The new source tracking position will also get a try_seek implementation that updates the position on success.
Using a relaxed atomic might enable easy access. Something like get_pos() -> &AtomicU32 (u32 fits 49.71027 days of milliseconds, is that enough and precise enough?).

Anyone should feel free to try something like this, I do not have the time atm. I do need this feature for a hobby project so I will implement it eventually, tho that could be in a few months.

@dvdsk Ah, should have read more carefully, I assumed the current state of the PR is mergeable, since the most recent comment was just a few weeks old.
I could try to make a new PR based on the design you just outlined, but am afraid the architectural design decisions are a bit out of my comfort zone as I'm quite unfamiliar with the library.
With a slightly more detailed set of instrucitons can definitely attempt to do this.

I haven't looked at this in a while, but I can also later this week take a look at the requirements and see how the features could be implemented.
I also only did this because I needed the feature myself and I put it here, because it seemed like somebody else could also be interested.

am afraid the architectural design decisions are a bit out of my comfort zone as I'm quite unfamiliar with the library.

I recommend taking a look at the text here: https://docs.rs/rodio/latest/rodio/source/trait.Source.html, browse a few of the structs implementing Source and take a look at the sink here: https://github.com/RustAudio/rodio/blob/ee73f6d97d9ffca450f497f5ac0eff266dfb9fc7/src/sink.rs#L120
That should give you a feel for the relevant part of the code base. Then you or @BastianHentschel can give it a try. Let me know if its still unclear after reading up, then ill write up some pseudo code.

Hi, I've gone ahead and implemented what was described in https://github.com/RustAudio/rodio/pull/510#issuecomment-2135872850 over at #585

Hi, I've gone ahead and implemented what was described in #510 (comment) over at #585

Ill have a look tomorrow :+1: thanks for the work!


text size issue on older iPhones with smaller screens during enrollment

Admin is migrating devices from another MDM solution to Jamf pro and using Jamf Migrate app - V3.3.6
When a user has their text size set to large on their iPhone, the migrate app prevents them from scrolling down to click on "Enroll" after hitting "begin".
They attempted to minimize the text on the phone itself to facilitate the migration, but it appears to persist in an enlarged state within the JAMF Migrate app.
Because of this, they get a "Web API Error" when they wait too long on the enroll page.
Affects older iPhones - on SE editions impacts even with font size set to the smallest: iPhones (8) and (2nd gen) SE or smaller screens
workaround on larger screen models it to reset font size and/or reinstall the app

Sorry to say you've got the wrong project, Jamf Migrator and Jamf Migrate serve two different functions.  The team working on Jamf Migrate have been notified of the issue.


Do you do any filtering on the raw detection boxes from CenterPoint, such as filtering out low score objects and nms?

Or you just feed everything into the network? Thanks.

Detection boxes are not filtered, false detections are filtered implicitly when they do not get assigned a track and are not reported . I experimented with adding minimum thresholds, but the tradeoff with recall was negative


feat(compiler-sfc): transform asset url

The reason I left them as TODO is because we probably want to redo this to use import instead.
For example, currently
<img src="./logo.png" srcset="./logo.png"/>

is compiled to:
createVNode('img', {
  src: require("./logo.png")
})

But inline require is somewhat a legacy thing in webpack now. The more ideal output would be:
import logoPng from './logo.png'

createVNode('img', {
  src: logoPng
})

So, instead of generating an inline require call, we need to inject an import statement at the top of the generated code. To do this we need to add a method to TransformContext and handle it accordingly in codegen.

👍


label and animation overlaping each other

I am first time using the chartjs, got a stuck at one point, I have tried multiple option with labels and animation. I have shown bar, multiple line in one chart, the issue is lables and animation i.e custom label for each data point is overlapping each other , it is not readable.  I am using animation.OnComplete to show the lable
see the below image for reference. Please let me know if I am missing something.

The keyword is: custom. We can't accept your code as a bug of Chart.js.
For labels that do not overlap, see the datalabels plugin (you'll need the 2.x version for Chart.js v3)


Fix formatting issues in UG and DG

Describe your changes
Fix formatting issues in UG and DG
Issue ticket number and link
closes #211, relates to #154
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Files with missing lines
Coverage Δ
Complexity Δ

...java/seedu/address/logic/commands/SortCommand.java
100.00% <ø> (ø)
1.00 <0.00> (ø)


References to CF Version support by netCDF loaders

📚 Documentation
#3925 updates documentation to reflect the CF version now used when saving netCDF files. While checking that I'd not missed any other locations in the documentation where this was referenced I found that the CF version used by the loader was mentioned in two docstrings:

The module level docstring at the top of lib/iris/fileformats/netcdf.py (Version 1.4, 27 February 2009)

The module level docstring in lib/iris/fileformats/cf.py (Version 1.5, October, 2010)

I don't know how the netCDF loader works. Are these two docstrings correct? If they need updating then I can easily add this to #3925. The reference for CF1.7 will be: Version 1.7, 10 August 2017.

Thanks for this @jonseddon !
The docstrings you mention are both out of date as we now handle loading CF 1.7 netCDF files. I'd be tempted to just remove the specific version altogether, so for example just have
[CF]  NetCDF Climate and Forecast (CF) Metadata conventions.
[NUG] NetCDF User's Guide, https://www.unidata.ucar.edu/software/netcdf/docs/

After all we haven't pinned down the netcdf version. And I want to avoid having multiple places to update, everytime we update to a new CF version

Not sure why this didn't close automatically despite the two being linked, but #3925 was merged so this can now be closed


Update Travis to Xcode 9.1 #trivial

Issue fixed: #1009

@rnystrom if any of these fail, i've figured out the magic numbers here:
https://github.com/jessesquires/JSQCoreDataKit/blob/develop/.travis.yml

@rnystrom the full matrix is getting pretty big (once we re-add iOS 8), but i guess it is "fool proof".
we'd probably be ok just using the earliest major version though. (8.1, 9.0, 10.0 only, etc) what do you think?

Dead links found:
https://travis-ci.org/Instagram/IGListKit/jobs/318289838
https://github.com/Instagram/IGListKit/blob/master/Source/IGListSectionType.h#L43-L54

Lots of build warnings and legit test failures here:
https://travis-ci.org/Instagram/IGListKit/jobs/318289839
@rnystrom does this need to be rebased?

pushed a fix for one of the errors

Other fixes at #1038.
We should merge that, then rebased this PR.

dead link issue fixed at #1041
we should also merge that, then rebase this. then i think we'll be green 💚

some day this will work again