Tagger crashes upon trying to play a song

Whenever I doubleclick a song in the tagger program, it crashes. I have tried to make it work with both Spotify for Desktop as the web player, both on my desktop as on laptop, and in all these cases the program silently crashes.
Luckily I could still generate playlists for every single tag I assigned, because I'm doubtful if this program is still maintained... Though I am a big fan of the project, I will have to move to "tagging" using playlists within Spotify.

I unfortunately dont have the time to actively maintain the project.
It frequently occours that the Spotify API throws some new error that is not handled properly and after a few days they fix it and everything works again. So maybe this issue will resolve itself in a few days.

Thank you for the response and clarification! Okay, I will check some time later if it resolved itself.
Also, I completely understand not finding time to maintain side projects. Thank you for starting it, and making it open source!
On 07 Jan 2024 20:57, Benedikt Alkin @.***> wrote:
I unfortunately dont have the time to actively maintain the project.
It frequently occours that the Spotify API throws some new error that is not handled properly and after a few days they fix it and everything works again. So maybe this issue will resolve itself in a few days.
—
Reply to this email directly, view it on GitHubhttps://github.com/BenediktAlkin/SongTaggerForSpotify/issues/29#issuecomment-1880155685, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL2PKSLRSAELRTFNCLHUK53YNL4Y5AVCNFSM6AAAAABBQIUS56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGE2TKNRYGU.
You are receiving this because you authored the thread.Message ID: @.***>
[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/BenediktAlkin/SongTaggerForSpotify/issues/29#issuecomment-1880155685", "url": "https://github.com/BenediktAlkin/SongTaggerForSpotify/issues/29#issuecomment-1880155685", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Thanks @BenediktAlkin for the awesome program!  Was really bummed when it ceased working.  Just tried it again tonight and it is back to being operational, fyi @Spruce8913.

Yesss! Thank you for letting me know!
On 18 Jan 2024 05:15, bradzom @.***> wrote:
Thanks @BenediktAlkinhttps://github.com/BenediktAlkin for the awesome program! Was really bummed when it ceased working. Just tried it again tonight and it is back to being operational, fyi @Spruce8913https://github.com/Spruce8913.
—
Reply to this email directly, view it on GitHubhttps://github.com/BenediktAlkin/SongTaggerForSpotify/issues/29#issuecomment-1897764142, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL2PKSMC2LHXGSIXSIOIE33YPCOVHAVCNFSM6AAAAABBQIUS56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJXG43DIMJUGI.
You are receiving this because you were mentioned.Message ID: @.***>
[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/BenediktAlkin/SongTaggerForSpotify/issues/29#issuecomment-1897764142", "url": "https://github.com/BenediktAlkin/SongTaggerForSpotify/issues/29#issuecomment-1897764142", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Hello! :)
I have the same problem right now. Song doesn't need to play, just when app get information what song is in actual in player, it's crashing

Only way to use is to has spotify player closed, but its harder to tag, without listening :)
Thanks for app! If it would no crash, will be amazing! :)

Hi, great analysis and writeup! It's unfortunate how Spotify makes backward compatibility breaking changes.
I included your code and made a new release. It should be up shortly.


Implementing Ties

Implement tying 2 notes together. The method is stubbed already.

After talking to coworker who uses Git a lot, he said that this is the best way to do code reviews and how I should develop. This way, anyone can see my progress as I'm working on it and can comment.

[x ] Implement test for index translation method
[x ] Implement index translation method
[ ] Implement test for start tie method
[ ] Implement start tie method
[ ] Implement test for remove tie method
[ ] Implement remove tie method

Implemented startTieAtIndex method, but can't figure out why the test is failing.

I started out writing the API for adding and removing a Tie within Measure. However, I realized during development that you could have a case where a tie could start in one measure and end in another. Because we wouldn't want measures to know about each other, it makes sense to instead have this API in the Staff. Therefore, I now started implementing it in the Staff. I have not removed it from Measure yet, because I'm not sure if the Staff implementation will call into Measure or will just modify Measure itself yet.

Just had to make a decision about how repeats affect measure indexes. This is what I have decided at this point:
If you have a repeat of a count of measures, each measure should be able to be indexed, so even if a measure is a repeat of a previous measure, it will have its own index. For instance:
[ MeasureA, MeasureB, MeasureRepeat(2 measures, repeated once), MeasureC ]

MeasureA is index 0
MeasureB is index 1
Measure0 of repeat is index 2
Measure1 of repeat is index 3
Measure0 of repeat next count is index 4
Measure1 of repeat next count is index 5
MeasureC is index 6
I think this makes sense, because it will allow every measure to be accessed even if it is part of a repeat. However, for modifying measures, the code will need to ensure that you never try to modify a measure that is simply a repeat of an earlier measure. I can see a possibility of maybe using a flag in  Measure to indicate this for convenience possibly at some point.

Considering having a state for a Measure that says whether it can be mutated, because if a measure is just a repeat of another one, then you shouldn't be able to modify anything in it.

This branch is ready to merged and can be reviewed now. Every task is completed.
Take a look @migue48

Since this is a very large change, which I will avoid in the future, we should try to do a code walkthrough before you take a look. Contact me to schedule it @migue48


Minimum environment test

I add tests for minimum environments, which do not contain cv2, scikit-learn, and matplotlib.

Great PR!
Thanks!

I am sorry, but could you fix another point?
Pillow is included in the minimum requirements of ChainerCV, even though it is not in Chainer.

LGTM!


Sync all the things

[x] Synchronizer is almost complete rewritten
[x] Add Cleaner
[x] passa clean
[x] add and upgrade now automatically sync
[x] remove now automatically cleans
[x] passa install = passa lock (if needed) + passa sync
[x] Find a way to get exactly what needs to be synced in add/remove/upgrade and only sync/clean those
[x] Make sure hash-checking during installation works
[x] News fragments (plural!)

Squashed and merged in 42360ff05dd2.


Creates styles for the welcome section.

Styles all sections of the welcome section Heading and figure included.

closes #3 #4 #5 #6


Feature/improve test

Closing. This is included in https://github.com/blueinkhq/blueink-client-js/pull/22


How to add token api in swagger ui page?

I managed to setup Swashbuckle successfully in my .net project and it's able to generate Swagger document very well. But the token (login) api is missing. How to add it to the document too so that I can use it to get the access token?

If you're API authentication uses one of the supported security schemes (basic, apiKey or OAuth2) you should be able to get this working by enhancing the generated Swagger with security descriptions. The following tutorial describes the process for OAuth: http://knowyourtoolset.com/2015/08/secure-web-apis-with-swagger-swashbuckle-and-oauth2-part-2/

You may also want to checkout #707 for an alternative approach using an IDocumentFilter to add the token endpoint. This is a little more flexible as you could theoretically use it to include any token endpoint regardless of the scheme being used

closing due to inactivity


Adding 7220 IXR-D4 chassis type

Hi,
23.3.1 introduced 7220 IXR-D4 chassis, could you please add it to the list of platforms?
Thanks

done in #37


get module name from component.json

see webpack/webpack#337
Instead of infering the module name from the path name, it should be read from the component.json.

Read all component.jsons for all dependencies.
Use the component which component.jsons name field matches the request.

This is a bigger refactoring...

@lmartins, I was wondering what fix you used. I am having difficulty loading components with webpack. I think the plugin assumes the component.json file is a direct child of the component folder. While components folder structure seems to be more like:
component-name
   |_ v.x.y.z
        |_ component.json
        |_ index.js

Even though I pass an array of paths for the lookupPaths, the plugin can't resolve the module.
Thanks!

@aminmeyghani although I will possibly use again in the future, I am now using a different solution and to be honest can't quite recall what I did then.

Thanks @lmartins ! Just wondering, do you use another plugin to work with component and webpack ?

No, for the time being im using JSPM to build my JS projects.


Making Executables

How would you make a standalone executable from a Wren file? Would you have to embed it into a C application or what?

Well, you'd have to package it with some code that creates a Wren VM and then interprets the wren file.

OK.


Raise auto_merge script's ability to see an approving review

Specify a per_page argument of 100 (the maximum) (default was 30)

E.g. this made the difference in https://github.com/quantumlib/Cirq/pull/2308

It is


Update ODUE_discord.js (v1.2)

v1.2

Added Party and variables ussage commands inside the Text box
Added: Small Picture pluggin command
Added: Small Picture Text pluggin command

Thanks for this!
I made some small changes (like replace that stupidly long switch with a way more simple method) and updated the MV version with your added stuff.


[GH-593] Fixed name_update_tx

resolves #593

I will open new PR for this problem because I created this brunch not from the master.


With customize navigation bar and tool-bar

Hello~
Thanks very much for your great work of this plugin, which is just the Right one for my cordova app targeting Native IOS/Android when open an external link without jump out.
Just want these issues:
In IOS:

Navigation-bar title on top show targeting Html's title now the center shows the URL. Could it be possible to show the html's title?(Though I know Safari also shows the URL...)
Navigation-bar title on top with customize button's icons. I want to replace the text 'done' with an left arrow icon, and move Share button at bottom to the right of navigation-bar....could it be possible in your future update version?
No tool-bar at bottom this toolbar's style is not unified with my App, so I want to move all the functions (Share, Open in Browser) to the Top, and hide the toolbar at bottom.

In Android

Customize Color for Navigationbar on Top in current version it is gray, and can't be changed..
Navigation-bar title on top with customize button's icons.  Besides the feature request in IOS, In android, the location bar seems useless for me...could it be replaced by Html's title?

Again, thanks very much for your excellent work of this Plugin~

+1!

To customize color for NavigationBar use barColor for iOS, but toolbarColor for Android.
It's inconsistent across platforms:
toolbarColor: '#f7f7f9',	// for Android
barColor: '#f7f7f9',		// for iOS only
tintColor: '#1ca8dd',		// for iOS only
controlTintColor: '#1ca8dd'	// for iOS only


Remove accidental commit of git submodule

Added in #13470 (8b98b94)
cc @PanSpagetka @martinpovolny This was added accidentally.  Please avoid this in the future.

Note that this causes the Docker build to fail with the following error:
Building in Docker Cloud's infrastructure...
Cloning into '.'...

No submodule mapping found in .gitmodules for path 'providers/manageiq-providers-amazon'

please ensure the correct public key is added to the list of trusted keys for this repository and the remote branch exists. (1)


Orchard.DynamicForms - Check Box Field Uses "Mandatory" Instead Of "Required"

v1.9.1
In all other elements I've used so far the Validation tab has a "Required" checkbox.
The Check Box element uses the word "Mandatory" instead.

The checkbox uses a different client side validator ("mandatory") than the textfields ("required"), but I agree it would be better to keep the same name on the UI layer, since there's no functional difference as far as the user is concerned.


Update Composer dependencies (2023-02-14-00-09)

Visual regression test passed!
View the visual regression test report


Heap Sort

Add a solution program for heap sort in any programming language

I want to work on this issue..I can provide the solution in C/C++/Python

I want to work on this issue

@dcod3r please specify the language for the solution


monitoring via graphite

Hi,
I am trying to monitor vernemq, and I made the following settings:
graphite_enabled = on
graphite_host = carbon.hostedgraphite.com
graphite_port = 2003
graphite_interval = 20000
graphite_api_key = YOUR-GRAPHITE-API-KEY
is the graphite_api_key the output of  vmq-admin api-key create command?
but nothing shows at localhost:2003. how can i fix it?

Hi @elhamkazemi thanks for asking.
The graphite_api_key in not the vmq api key. The configs you find in vernemq.conf are just an example.
If you want to see graphite results on your localhost you have to run a graphite service on your localhost and then configure vernemq.conf accordingly.


Feat(BILL-CPC-247) : Add HTML Elements for Billing Service

Would like to merge into main to allow for the billing service to contain new UI elements. We should be able to have a history page documenting all the bills generated and a details page for a given id.
Design Documents:
History Page:

Details Page:

Without css and with mockup data:

Jira:

P.S. The reason some people are credited for making changes on the branch is likely due to rebasing from main

Are you planning to do pagination for this?

I would see the value in providing pagination given a scenario where we get all the bills generated say in an admin page yes. For the time being I wouldn't particularly say it would be of high priority given the small amounts of data being used right now.


[RFC] Write tests for existing components

Goals

improve quality of components
secure PRs and review with tests
avoid regression

Background
What we know

testing components with @testing-library

What Radix-UI does

writes "integration" tests for each of its components (ex)
check accessibility violations with axe-jest

What's possible with Storybook

integrating stories with testing-library
write interaction tests, they run testing library under the hood
write accessibility tests, they run axe under the hood

Storybook allows writing tests for stories instead of components.
Chromatic automates testing visual changes
https://www.chromatic.com/docs/
Proposals

Test components with testing-library
Add axe-jest to check for accessibility violations
Write integration tests for related components, when it makes sense
See if it's worth adding storybook integrations

We should test components not extending radix primitives
Testing accessibility is the most relevant part
Testing interactions with component
Avoid testing styles as it's redundant with stitches tests


WaveDrom - build digital wavefrom graphics

https://wavedrom.com/editor.html
https://wavedrom.com/
http://agilesoc.com/2018/08/20/turning-documentation-into-unit-testing-action/
It's more easier than I thought. Once we learn the basics we can draw the waveforms very easily and it's actually easier to modify the diagram and store it in version control systems to compare as what changed.

Some good examples to get comfortable


[staging] gnugrep: 3.7 -> 3.11

Also replace myself as a maintainer
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Draft for now because this breaks PCRE

Should work now, @trofi can you verify that I didn't break the bootstrap tools?

At least on linux (and I think on darwin as well) we will need to add pcre2 to allowed references (or substitute from pcre?). Otherwise stdenv fails to build as:
$ nix build --no-link -f. stdenv
error: output '/nix/store/jy1wr873b4ib5gplrg3118z8gjs2bpa1-stdenv-linux' is not allowed to refer to the following paths:
         /nix/store/grd3jawsc8xchi0zg92k91m1n5piasbj-pcre2-10.42

Do I need them in persistent as well?

I have successfully built stdenv from this branch now for x86_64-linux

Today's cutoff for "breaking changes" in 23.05, so I wonder if this is worth squeezing in.  (I don't feel confident enough to merge now.)

I personally wouldn't risk it, it's not like people have been anxiously waiting for this gnugrep update ;)

@Artturin applied suggestion
@trofi can you look at my latest commit? It enables more tests but adds a dependency on glibcLocales. Is this wise? stdenv still builds for me with this applied.

glibcLocales expands to null for musl and other non-glibc targes:
$ nix build --no-link github:NixOS/nixpkgs/pull/228714/merge#pkgsMusl.stdenv -L
error:
       … while calling the 'derivationStrict' builtin

         at //builtin/derivation.nix:9:12: (source not available)

       … while evaluating derivation 'stdenv-linux'
         whose name attribute is located at /nix/store/55sz8bdibv3qq6saialdkkiijvsrrx0s-source/pkgs/stdenv/generic/default.nix:93:14

       … while evaluating attribute 'allowedRequisites' of derivation 'stdenv-linux'

         at /nix/store/55sz8bdibv3qq6saialdkkiijvsrrx0s-source/pkgs/stdenv/generic/default.nix:84:7:

           83|     lib.optionalAttrs (allowedRequisites != null) {
           84|       allowedRequisites = allowedRequisites
             |       ^
           85|         ++ defaultNativeBuildInputs ++ defaultBuildInputs;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: value is null while a set was expected

The simplest would be to probably avoid use of .override() and pick default locale set.

Thanks for that input, this suggestion also adds chinese locales, bringing the skipped tests down to 9 (skipped by default because they are expensive).
The only things that could be worth fixing are:

pcre-ascii-digits: skipped test: PCRE 10.42 and older lack PCRE2_EXTRA_ASCII_BSD
sjis-mb: skipped test: SJIS locale not found

Bumped to 3.11, this means I dropped the 3.10 regression fix.

musl is in trouble, but fortunately only on aarch64:
https://hydra.nixos.org/build/221679820

This appears to break pkgsStatic.gnugrep for me on x86_64 linux, with 4 tests failing: test-nl_langinfo-mt, test-setlocale_null-mt-one, test-setlocale_null-mt-all, test-thread_create.

So, add !stdenv.hostPlatform.isMusl to doCheck?

Yes, I'd use that as the simplest workaround, in case nothing better is submitted.  It's surely better than to have no musl-based stdenv.  For example, we could conditionally drop just the tests failing now (a tiny minority).

I'm currently investigating

Hmm, on x86_64-darwin it always gets stuck during tests (four times at least now).  That's on Hydra: https://hydra.nixos.org/build/222612843#tabs-buildsteps
Locally it did pass for me on the first try – so maybe something about rosetta.  I don't know, but I expect we'd conditionally drop tests again?

so doCheck = !stdenv.hostPlatform.isDarwin?

IIRC, @reckenrode also mentioned the x86_64-darwin issue, albeit for sandbox builds.

I’ve also encountered it trying to work on the Darwin stdenv bump on x86_64-darwin. It always hangs on my Apple Silicon MBP, but it builds on our Intel iMac. The MBP is running 13.4 while the iMac is still on 13.3.1(a). I don’t know if OS version makes a difference, or if it’s a Rosetta 2 issue the test is triggering.

Apparently it succeeded in the end
nix build /nix/store/cprxh7g44qgvygmc2hv3l6xg3qkyl6sx-gnugrep-3.11 --dry-run

so I guess I'll let it be for now and reconsider doCheck = !stdenv.hostPlatform.isDarwin once it gets stuck again? (which I expect to happen in some future staging-next)

How long did it take to run? I left mine going for hours, and it never finished.

I don't know how to find that.  The log is easy to get, as the URL doesn't change on retries, but I can't see how to find which job built it (and see the time and machine).

I don't know how to find that. The log is easy to get, as the URL doesn't change on retries, but I can't see how to find which job built it (and see the time and machine).

checkPhase completed in 2 minutes 32 seconds

Are any of the builders actually x86_64-darwin hardware? It’s still stuck for me.
[1/158/203 built, 0.0 MiB DL] building gnugrep-3.11 (checkPhase): FAIL: test-c-stack.sh

It’s been stuck at that for hours. I even tried to rework my stdenv stuff to build gnugrep later (with clang 16), but it didn’t make a difference.

I believe all are aarch64-darwin currently.  @cole-h should have a better grasp on this.

ofborg has 3 x86 and 2 aarch64 macs, with the aarch64 macs enabling Rosetta and taking x86 builds whenever The Scheduler desires.

@cole-h: this was too big for OfBorg, I meant Hydra where it did succeed after several attempts (but I don't know on which machine).

According to https://hydra.nixos.org/machines, we only have 1 "real" x86_64-darwin machine (destined-gannet). (There's stirred-oryx too, but it's been dead basically since forever.)

Can anyone with Rosetta test this patch?
diff --git a/pkgs/tools/text/gnugrep/default.nix b/pkgs/tools/text/gnugrep/default.nix
index 75c6f695073..2494ed1e49b 100644
--- a/pkgs/tools/text/gnugrep/default.nix
+++ b/pkgs/tools/text/gnugrep/default.nix
@@ -17,7 +17,8 @@ stdenv.mkDerivation {
   };

   # Some gnulib tests fail on Musl: https://github.com/NixOS/nixpkgs/pull/228714
-  postPatch = if stdenv.hostPlatform.isMusl then ''
+  # They also seem to fail on Rosetta: https://github.com/NixOS/nixpkgs/pull/228714#issuecomment-1574300624
+  postPatch = if stdenv.hostPlatform.isMusl || stdenv.hostPlatform.system == "x86_64-darwin" then ''
     sed -i 's:gnulib-tests::g' Makefile.in
   '' else null;

Worked for me:
vin@catacendre nixpkgs % file result/bin/grep
result/bin/grep: Mach-O 64-bit executable x86_64
vin@catacendre nixpkgs % realpath ./result
/nix/store/vpcabk9qbxssqj3qcy9c3nag465mi3zw-gnugrep-3.11


bug(datepicker): w/ filter validate is not announcing the disabled state of the dates

Reproduction
Steps to reproduce:

Open the Datepicker Examples
Go to the "Datepicker with filter validation" demo
Open calendar and  focus on any disabled dates

Expected Behavior
It should provide the state of the disabled dates as "disabled"
Actual Behavior
It is not providing the state of disabled dates as "disabled"
Environment
ChromeOS | Google Chrome 91.0.4472.167 | ChromeVox
Additional Notes
This is copied from an internal bug report found during a11y testing.

I can no longer reproduce. I think this might have been fixed when we changed the calendar to use native button element inside the grid cells, rather than putting aria-disabled directly on the grid cell. The internal bug for this was also verified as fix by the reporter, so I'll go ahead and consider this "fixed".
Chrome/ChromeOS Version 104.0.5112.110 (Official Build) (64-bit)
Running locally on main branch at commit 29c4df53859aa42a04d404a6e4d2d3280ca705b9


delay issues when intrupting the key_receive function

how do you get the program to return commands at set intervals rather than as fast as possible. If I try to include a delay in the key_received function, it causes the commands to build up.  I need to read the commands at the same time as I am receiving images from a camera using opencv however, the camera feed has inevitble delay so the joystick commands do not match with each frame.
below is the a minimum working example of the problem. I tried messing around in the source code to include a delay in a while loop in the interface file but that didnt work at all.
any help is much appreciated.
'''
from pyjoystick.sdl2 import Key, Joystick, run_event_loop
import time
def print_add(joy):
    print('Added', joy)

def print_remove(joy):
    print('Removed', joy)

def key_received(key):
    print('Key:', round(key.value,2))

    if key == "Button 1":
        print("DISCONNECTING JOYSTICK")
        Joystick.close()

    time.sleep(25/1000)   #how do I get the program to read commands every 25 ms instead.

run_event_loop(print_add, print_remove, key_received)

'''
``

Make a buffer / list and read the commands on a timer or thread.

Ok

You need to keep the loop running to process events on the system.
from pyjoystick.sdl2 import Key, Joystick, run_event_loop
import time
import threading

events = []
alive = threading.Event()
alive.set()

def print_add(joy):
    print('Added', joy)

def print_remove(joy):
    print('Removed', joy)

def key_received(key):
    print('Key:', round(key.value,2))

    if key not in events:
        events.append(key)

    if key == "Button 1":
        print("DISCONNECTING JOYSTICK")
        Joystick.close()
        alive.clear()

def run_interval(interval=25/1000):
    while alive.is_set():
        evs = [e for e in events]
        events.clear()

        for key in evs:
            print(e)
        time.sleep(interval)

th = threading.Thread(target=run_interval)
th.start()

run_event_loop(print_add, print_remove, key_received)


Long time waiting without response

I've tested many APIs, (Channels_GetAllParticipants, Messages_GetAllChats, ...)  but they don't respond and waiting forever!
var chats = await client.Messages_GetAllChats(null);

WTelegramClient source running under .NET 6.0.0-rc.2.21480.5

please check https://github.com/wiz0u/WTelegramClient/blob/master/FAQ.md#troubleshoot


Webrtc frame skipping

Im seeing some weird behaviour using webrtc where I get frame skipping / stuttering every 2 seconds.
The issue isnt present when using mse whatsoever. Ive tried the default Frigate version of go2rtc and also updated to 1.8.4 with no change.
{
  "producers": [
    {
      "type": "RTSP active producer",
      "url": "rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1\u0026subtype=0/",
      "remote_addr": "<IP_ADDRESS>:554",
      "user_agent": "go2rtc/1.8.4",
      "sdp": "v=0\r\no=-<PHONE_NUMBER><PHONE_NUMBER> IN IP4 <IP_ADDRESS>\r\ns=Media Server\r\nc=IN IP4 <IP_ADDRESS>\r\nt=0 0\r\na=control:*\r\na=packetization-supported:DH\r\na=rtppayload-supported:DH\r\na=range:npt=now-\r\nm=video 0 RTP/AVP 96\r\na=control:trackID=0\r\na=framerate:25.000000\r\na=rtpmap:96 H264/90000\r\na=fmtp:96 packetization-mode=1;profile-level-id=4D0033;sprop-parameter-sets=Z00AM+kAeACH0IAAAfSAAGHBAgA=,aOqPIAA=\r\na=recvonly\r\nm=audio 0 RTP/AVP 8\r\na=control:trackID=5\r\na=rtpmap:8 PCMA/8000\r\na=sendonly\r\n",
      "medias": [
        "video, recvonly, H.264 Main 5.1",
        "audio, sendonly, PCMA/8000"
      ],
      "receivers": [
        "96 H264, bytes=165715478, senders=3"
      ],
      "recv": 167130230
    }
  ],
  "consumers": [
    {
      "type": "RTSP passive consumer",
      "url": "rtsp://<IP_ADDRESS>:8554/front",
      "remote_addr": "<IP_ADDRESS>:55208",
      "user_agent": "FFmpeg Frigate/0.12.1-367d724",
      "sdp": "v=0\r\no=- 1 1 IN IP4 <IP_ADDRESS>\r\ns=go2rtc/1.8.4\r\nc=IN IP4 <IP_ADDRESS>\r\nt=0 0\r\nm=video 0 RTP/AVP 96\r\na=rtpmap:96 H264/90000\r\na=fmtp:96 packetization-mode=1;profile-level-id=4D0033;sprop-parameter-sets=Z00AM+kAeACH0IAAAfSAAGHBAgA=,aOqPIAA=\r\na=control:trackID=0\r\n",
      "medias": [
        "video, sendonly, H264, H265",
        "audio, sendonly, MPEG4-GENERIC"
      ],
      "senders": [
        "96 H264, bytes=165715478, receivers=1"
      ],
      "send": 167591030
    },
    {
       "type": "WebRTC/WebSocket async passive consumer",
      "remote_addr": "tcp4 prflx <IP_ADDRESS>:54068 related :0",
      "user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36",
      "medias": [
        "video, sendonly, VP8, RTX, VP9, H264, AV1, RED, ULPFEC, FLEXFEC-03",
        "audio, sendonly, OPUS/48000/2, RED/48000/2, G722/8000, PCMU/8000, PCMA/8000, CN/8000, TELEPHONE-EVENT/48000, TELEPHONE-EVENT/8000, L16, PCML"
      ],
      "senders": [
        "102 H264, bytes=113648791, receivers=1"
      ],
      "send": 114843212
    },
    {
      "type": "RTSP passive consumer",
      "url": "rtsp://<IP_ADDRESS>:8554/front",
      "remote_addr": "<IP_ADDRESS>:57216",
      "user_agent": "Lavf59.27.100",
      "sdp": "v=0\r\no=- 1 1 IN IP4 <IP_ADDRESS>\r\ns=go2rtc/1.8.4\r\nc=IN IP4 <IP_ADDRESS>\r\nt=0 0\r\nm=video 0 RTP/AVP 96\r\na=rtpmap:96 H264/90000\r\na=fmtp:96 packetization-mode=1;profile-level-id=4D0033;sprop-parameter-sets=Z00AM+kAeACH0IAAAfSAAGHBAgA=,aOqPIAA=\r\na=control:trackID=0\r\n",
      "medias": [
        "video, sendonly, H264, H265",
        "audio, sendonly, MPEG4-GENERIC"
      ],
      "senders": [
        "96 H264, bytes=71272938, receivers=1"
      ],
      "send": 72074346
    }
  ]
}

Just and update there is nothing in the chrome logs outside of

You should try to use go2rtc addon. I can see that WebRTC works for you via TCP. This is strange because for LAN connection it should be UDP. Maybe problem related to port forwarding for Frigate docker container.

Its weird  using firefox it uses UDP
{
"producers": [
{
"type": "RTSP source",
"url": "rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1\u0026subtype=0/",
"remote_addr": "<IP_ADDRESS>:554",
"user_agent": "go2rtc/1.2.0",
"medias": [
"video, sendonly, 96 H264/90000",
"audio, recvonly, 8 PCMA/8000"
],
"tracks": [
"96 H264/90000, sinks=3"
],
"recv":<PHONE_NUMBER>
}
],
"consumers": [
{
"type": "RTSP client",
"url": "rtsp://<IP_ADDRESS>:8554/front",
"remote_addr": "<IP_ADDRESS>:59940",
"user_agent": "FFmpeg Frigate/0.12.1-367d724",
"medias": [
"video, recvonly, 96 H264/90000",
"audio, recvonly, 0 MPEG4-GENERIC/0"
],
"tracks": [
"96 H264/90000, sinks=3"
],
"send":<PHONE_NUMBER>
},
{
"type": "RTSP client",
"url": "rtsp://<IP_ADDRESS>:8554/front",
"remote_addr": "<IP_ADDRESS>:36750",
"user_agent": "Lavf59.27.100",
"medias": [
"video, recvonly, 96 H264/90000",
"audio, recvonly, 0 MPEG4-GENERIC/0"
],
"tracks": [
"96 H264/90000, sinks=3"
],
"send":<PHONE_NUMBER>
},
{
"type": "WebRTC client",      "remote_addr": "udp4 prflx
<IP_ADDRESS>:58247 related :0",
"user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64;
rv:120.0) Gecko/20100101 Firefox/120.0",
"send": 3073996
}
]
}
On Sat, Dec 2, 2023 at 6:50 PM Alex X @.***> wrote:

You should try to use go2rtc addon. I can see that WebRTC works for you
via TCP. This is strange because for LAN connection it should be UDP. Maybe
problem related to port forwarding for Frigate docker container.
—
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/go2rtc/issues/789#issuecomment-1837078466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU556KKYKXUG6HLMJFVMVPDYHLMV7AVCNFSM6AAAAABACDQVUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGA3TQNBWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

And also has problems? What's the bitrate of the stream?

When using version v1.8.4 I have UDP mapped yet it uses TCP? Why ?
On the default version it uses UDP no problem with the same docker settings
On Sat, Dec 2, 2023 at 8:05 PM Alex X @.***> wrote:

And also has problems? What's the bitrate of the stream?
—
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/go2rtc/issues/789#issuecomment-1837094974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU556KLP2LM66SRDG5XRSEDYHLVNLAVCNFSM6AAAAABACDQVUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGA4TIOJXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Bitrate is 8192 Kb/Sec @ 3840*2160
On Sat, Dec 2, 2023 at 8:05 PM Alex X @.***> wrote:

And also has problems? What's the bitrate of the stream?
—
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/go2rtc/issues/789#issuecomment-1837094974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU556KLP2LM66SRDG5XRSEDYHLVNLAVCNFSM6AAAAABACDQVUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGA4TIOJXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is hi bitrate and can be a problem real time streaming for WebRTC

I'm seeing similar behavior but on both MSE and WebRTC. I tried to disable audio transcoding as well but no change. My streams are transcoded to H264 (from H265 of camera) by go2rtc. To avoid any other posssibilities, I'm testing using go2rtc web interface on port 1984 using "stream" link to test.
All my 4K streams are stuttering like this, skipping frames on both MSE & RTC.  On the exact same device, ie a Chromebook or a PC, if I launch VLC and point it to the RTSP stream of go2rtc, like rtsp://go2rtc_ip:8554/Cameraname then it plays flawlessly.
This confuses me as it happens in Chrome, Edge and even Thorium, while RTSP stream on VLC works perfectly fine.


Create serialization strategy for non-body params

Follow-up for #564, meta issue #565

@fehguy I think the #564 should be #654 instead. (Feel free to delete this comment after fixing it in the initial comment.)

I just found that there currently is an Internet draft discussed in the HTTP working group. This basically defines a format to transport JSON arrays (while omitting the brackets) in HTTP headers.
I guess this could work for custom headers with OpenAPI schema definitions for them, as well as for future official HTTP headers following an RFC coming out of this internet draft.
Note that this defines a serialization scheme just for arrays, not for objects, because that way it works nicely with multiple occurences of a Header, which is equivalent to putting the values together in one, separated by commas.
It will not work for most existing headers using different syntax, for that we would need some different serialization scheme.
(originally posted at #652, but @fehguy pointed out it belongs here.)

I bet this was discussed before, but what about using something like http://api.jquery.com/jquery.param/ ?

Covered in #878


KONGA_SEED_KONG_NODE_DATA_SOURCE_FILE doesn't work

I use db less config.
I set KONGA_SEED_KONG_NODE_DATA_SOURCE_FILE.
It never worked. I need help, please ~~

I'm using the 0.14.7 version now, it doesn't work either.

@xiaolin8 , unfortunately I cannot reproduce the issue on Konga 0.14.7. It's working fine on my end and from what I get from your screenshots, it should be working for you as well.
Can you please run in dev mode with the same env vars and post Kongas logs? Maybe that will help me identify what I'm missing.

I have just submitted a PR where I solve this setting extravolumes and extravolumemounts (those were not available) in your custom values. Those should point to configmaps (secrets should work too) that define the files you need. It works with me.
module.exports = [
        {
            "name": "kong-admin",
            "type": "key_auth",
            "kong_admin_url": "http://your-kong-admin-svc:8444",
            "health_checks": false,
        }
    ]

I have the same issue:
# cat kong_seed_node_data.json
module.exports = [
    {
        "name": "Kong",
        "type": "default",
        "kong_admin_url": "http://kong:8001",
        "health_checks": false,
    }
]

# less docker-compose.yml
(...)
  konga-prepare:
    image: pantsel/konga:0.14.7
    command: "-c prepare -a postgres -u postgresql://kong:${KONG_PG_PASSWORD}@db:5432/konga"
    depends_on:
      - db
    networks:
      - kong-net
    restart: on-failure

  konga:
    image: pantsel/konga:0.14.7
    depends_on:
      - konga-prepare
    ## FIXME: we need always instead of on-failure because sometimes the database takes a little while to be
    ## ready after konga-prepare, and konga fails because it can't find the database but exists with error code 0
    restart: always
    ports:
      - "1337:1337"
    networks:
      - kong-net
    environment:
      TOKEN_SECRET: "${KONGA_TOKEN_SECRET}" #Created by Ansible in .env
      DB_ADAPTER: postgres
      DB_HOST: db
      DB_USER: kong
      DB_PASSWORD: "${KONG_PG_PASSWORD}"
      DB_DATABASE: konga
      NODE_ENV: production
      KONGA_SEED_KONG_NODE_DATA_SOURCE_FILE: /run/kong_seed_node_data.json
    volumes:
      - ./kong_seed_node_data.json:/run/kong_seed_node_data.json

The error in the console is:
konga_1               | SyntaxError: /run/kong_seed_node_data.json: Unexpected token m in JSON at position 0
konga_1               |     at JSON.parse (<anonymous>)
konga_1               |     at Object.Module._extensions..json (internal/modules/cjs/loader.js:797:27)
konga_1               |     at Module.load (internal/modules/cjs/loader.js:653:32)
konga_1               |     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
konga_1               |     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
konga_1               |     at Module.require (internal/modules/cjs/loader.js:692:17)
konga_1               |     at require (internal/modules/cjs/helpers.js:25:18)
konga_1               |     at getseedData (/app/config/default-seed-data.js:25:28)
konga_1               |     at Object.<anonymous> (/app/config/default-seed-data.js:49:21)
konga_1               |     at Module._compile (internal/modules/cjs/loader.js:778:30)
konga_1               |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
konga_1               |     at Module.load (internal/modules/cjs/loader.js:653:32)
konga_1               |     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
konga_1               |     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
konga_1               |     at Module.require (internal/modules/cjs/loader.js:692:17)
konga_1               |     at require (internal/modules/cjs/helpers.js:25:18)
konga_1               |     at /app/node_modules/sails/node_modules/include-all/lib/help-include-all-sync.js:271:33
konga_1               |     at Array.forEach (<anonymous>)
konga_1               |     at _recursivelyIncludeAll (/app/node_modules/sails/node_modules/include-all/lib/help-include-all-sync.js:174:11)
konga_1               |     at includeAll (/app/node_modules/sails/node_modules/include-all/lib/help-include-all-sync.js:292:5)
konga_1               |     at helpBuildDictionary (/app/node_modules/sails/node_modules/include-all/lib/help-build-dictionary.js:43:15)
konga_1               |     at Function.module.exports.aggregate (/app/node_modules/sails/node_modules/include-all/index.js:101:10)
konga_1               | Failed to load /run/kong_seed_node_data.json from KONGA_SEED_KONG_NODE_DATA_SOURCE_FILE
konga_1               | Reverting to default kong_node seed

@eburgueno , judging from your message, your json file is not valid

@pantsel do you see anything wrong with it? It's almost a line for line copy of the one in the docs:
module.exports = [
    {
        "name": "Kong",
        "type": "default",
        "kong_admin_url": "http://kong:8001",
        "health_checks": false,
    }
]

Try renaming your file to kong_seed_node_data.data instead of .json because the file is not a valid json file. (And it shouldnt be a json file also)

the file is not a valid json file.

Of course. Didn't think about that. Calling it .data did the trick. Thanks!

solved my problem:
volumeMounts: - mountPath: /users/ name: users env: - name: KONGA_SEED_USER_DATA_SOURCE_FILE value: /users/usersdb.data
kind: ConfigMap apiVersion: v1 metadata: name: kong-dashboard-users labels: app: kong-dashboard data: usersdb.data: "module.exports = [ { 'username': 'admin', 'email'<EMAIL_ADDRESS>
Hi @flowdopip i am also stuck on the same issue, Need your help. can you please share me the exact configuration which you have passed in the values.yaml and configmap.

solved my problem:
volumeMounts: - mountPath: /users/ name: users env: - name: KONGA_SEED_USER_DATA_SOURCE_FILE value: /users/usersdb.data
kind: ConfigMap apiVersion: v1 metadata: name: kong-dashboard-users labels: app: kong-dashboard data: usersdb.data: "module.exports = [ { 'username': 'admin', 'email'<EMAIL_ADDRESS>
Hi @flowdopip i am also stuck on the same issue, Need your help. can you please share me the exact configuration which you have passed in the values.yaml and configmap.

Here's what I have:
apiVersion: v1
kind: ConfigMap
data:
  usersdb.data: "module.exports = [ { \"username\": \"ADMIN\", \"email\"<EMAIL_ADDRESS>\"firstName\": \"Marmaduke\", \"lastName\": \"Wimblethorpe\", \"node_id\": \"http://kong.kong.svc.cluster.local:8001\", \"admin\": true, \"active\" : true, \"password\": \"password\" }]"
  kongconnection.data: "module.exports = [{\"name\": \"Kong\", \"type\": \"default\", \"kong_admin_url\": \"http://@KONG_IP@:8001\", \"health_checks\": false}]"
metadata:
  name: konga-data

Then on the deployment
     env:
...
            - name: KONGA_SEED_USER_DATA_SOURCE_FILE
              value: /base/config/usersdb.data
            - name: KONGA_SEED_KONG_NODE_DATA_SOURCE_FILE
              value: /base/config/kongconnection.data
          volumeMounts:
          - mountPath: /base/config/
            name: base-config
      volumes:
        - name: base-config
          configMap:
            name: konga-data


Concurrent authenticate_request calls result in signed-out status.

I have a flask, cross-origin backend which supports multi-threaded requests.
I notice that on a certain page in my frontend, where two requests are performed concurrently (and therefore both undergo authenticate_request validation) one of them fails, whilst the other succeeds - despite their headers and claims being the same.
Is this a known issue? Somehow I don't really see the same issue in the dev environment, only production.
Thanks & merry Christmas!

BTW, the exact error message I get is:
RequestState(status=<AuthStatus.SIGNED_OUT: 'signed-out'>, reason=<TokenVerificationErrorReason.TOKEN_INVALID_AUTHORIZED_PARTIES: ('token-invalid-authorized-parties', 'Authorized party claim (azp) does not match any of the authorized parties.')>, token=None, payload=None).
Whilst the other request succeeds with a signed-in status.
If I refresh the page, they might switch - but one always fails.

Resolved!
#54 this fixed the issue for me as well, i assume it's some sort of caching happening on clerk side.
Happy holidays!

OK, this is back for me, even with networkless authenticate_request. TBH the code I've got seems correct and the fact it works intermittently (literally differs on page refresh) makes me think this is a Clerk-side issue.


[DOCS] Include a direct link for CODE_OF_CONDUCT.md

Description
In the Code of Conduct 💚 section, I suggest adding a direct link to the guidelines on  CODE_OF_CONDUCT.md. This improvement would make it easier for contributors to find the documentation without having to search for it manually. By implementing this enhancement, it will greatly enhance productivity and improve the overall user experience for everyone.
Screenshots
Before:

Expected:

Additional information
Assign this issue to me under GSSOC23

assign this issue to me @panwar8279 Thank you!!

Hi @jfmartinz ,  I have assigned this task to you. Kindly complete your work within 2 days. Good luck!


Mention embeded analyzer configuration files in FxCop analyzer NuGet package starting 2.9.5 release

See https://github.com/dotnet/roslyn-analyzers/pull/2818
Starting 2.9.5 (not yet published), we will embed the analyzer configuration files in each analyzer NuGet package. This page can contain the set of available options in the latest packages. Users that are on older packages can use the embedded documentation file in the NuGet package to check the available options.

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

ID: 6b376237-1957-7b92-899d-0c816dac5412
Version Independent ID: 0a02458c-2f69-80c3-4215-436f2250ced0
Content: FxCop analyzer configuration options - Visual Studio
Content Source: docs/code-quality/fxcop-analyzer-options.md
Product: visual-studio-windows
Technology: vs-ide-code-analysis
GitHub Login: @gewarren
Microsoft Alias: gewarren

@mavasani Hi Manish. I see that 2.9.5 is released, but I'm not finding the embedded configuration file. Is it in the 'editorconfig' folder?

@gewarren it should be in .nuget\packages\microsoft.codeanalysis.fxcopanalyzers\2.9.5\documentation\Analyzer Configuration.md
As an aside, we should also document the embedded helper editorconfig files analogous to the helper rulesets inside \.nuget\packages\microsoft.codeanalysis.fxcopanalyzers\2.9.5\editorconfig. Do you want me to file a separate issue at https://docs.microsoft.com/en-us/visualstudio/code-quality/analyzer-rule-sets?view=vs-2019?


Helper refactor

As mentioned in https://github.com/geopm/geopm/pull/1382, pulling out the Helper pass by const ref. changes here.
And refactoring string_ends_with to use rfind.
Related to #1348

You should be able to debug the failing unit test more quickly by running the tests locally.  Let me know if you need any help getting that set up.

C++20 adds the starts_with() and ends_with() methods for std::string.  We may want our functions to reflect the APIs defined in the standard.


GridList missing in docs

Hey guys, just noticed that the GridList component seems to have disappeared from the docs, looks like commit 0f98495 was the culprit. Before I submit a PR, can someone let me know if this was intentional or not?

Good catch. Do you want to make a PR to add it back ?

done, see #1948


D/feature/bridge api

Coverage increased (+0.1%) to 85.857% when pulling a9a3112fec2ad2da1bf6f9cfdf1e40284e52bfb6 on d/feature/bridge-api into 5554fdcd85fb6ff6e6422e02319facfb6f47e91d on master.


Give user ability to customise buttons

Had a request to change the copy from Finish Wizard to OK.
Sideshow already has a dictionary and a language setting, but the user can't customise it without changing the source code.
I think we should allow providing a Sideshow.config.customDictionary property.

Also I think we should give the ability if the user wants to show the title of the next step or not.
I've had some buggy behaviour when the steps have autoskipping, where the title of the next step is shown, but when clicking it will bring me to the next step.
It might be useful to allow the user to customise this behaviour with something like Sideshow.config.hideNextTitle

Where close button will appear in the list of tutorials?


Why is python being added in the docker file

Quick one, why is Python being added in the Dockerfile ? I removed it on local and all seems to go well.

At one point docker-gc was using some inline Python to calculate elapsed times, but that was removed in 66260330a98584179dd69a1438c4816ecabedd87. Good catch @SamSaffron!


iframe integration into Confluence

Hi, I got a request to implement mattermost into confluence via iframe. The documentation states to change the "head.html" which seems to be gone since 2015 (https://docs.mattermost.com/integrations/embedding.html#embedding-mattermost-in-web-applications-using-an-iframe )
To this point I found no way to implement mattermost via iframe into confluence. What is the current correct way and why isn´t it documented?!
Also I found this thread which lead to nowhere aswell:
https://forum.mattermost.org/t/how-can-we-load-mattermost-in-iframe/165/8

The Issue was resolved by the MM support. Really bummed nobody cared about this.


IFF Elim doesn't take current node into account

In Natural Deduction
(A <-> B) A
------------------
B

However, the verification rule only checks to see if the structure above the line is correct. It doesn't check to see if the current node matches any of the parents.

Fixed in Commit 904f4e87baee51a0798f4b879b1bcf6aaedf344f


How to pass the -n argument (skip existing files)?

Is it possible to pass the -n argument in ffmpeg-python somehow? This quits immediately if the output file already exists.
I know I can get past the y/n questions with .overwrite_output(), but I'd rather not encode everything again for no reason.

I needed to confirm overwriting. And i made it this way:
ffmpeg.run(vid, overwrite_output=1)
I guess to cancel overwriting you need to replace 1 with 0 (or False):
ffmpeg.run(vid_1080, overwrite_output=0)

I guess to cancel overwriting you need to replace 1 with 0 (or False):
ffmpeg.run(vid_1080, overwrite_output=0)

Thanks for replying! I tried this but it doesn't work unfortunately. overwrite_output=1 means it overwrites files without asking. 0 means it asks for y/n. I'm looking for something that would skip overwriting without asking.

Hi! I am looking for any solution. Is there any update?

have you tried adding n=None in you output node?
it seems to kind of work:
try:
    ffmpeg.input("tmp/tmp.mp4").output("tmp/tmp.mp4", n=None).run(quiet=True)
except ffmpeg.Error as e:
    print(e.stdout.decode())
    print(e.stderr.decode())

[...]
File 'tmp/tmp.mp4' already exists. Exiting.

have you tried adding n=None in you output node? it seems to kind of work:

Thanks. adding n=None is working.... :relaxed:


question about make ./configure?

when i run ./configure, it occurs as following
checking for ocamlmklib... /usr/local/bin/ocamlmklib
checking for ocamldoc... /usr/local/bin/ocamldoc
checking for ocamlbuild... no
checking if OCaml version is >= 4.06.1... yes
checking for ocamlbuild... no
configure: error: ocamlbuild not found.
root@OptiPlex-390:/toolsrc/infer-master# ocaml --version
The OCaml toplevel, version 4.06.1
i think i have installed ocaml with version 4.06.1

Hopefully this is resolved, closing the issue optimistically. Feel free to reopen if you have more questions.


v1.3.0 no addon info

Have you upgrade the vela-core to v1.3.0? It seems the server lost the configuration of addon, you can apply this configmap and try again:
apiVersion: v1
kind: ConfigMap
metadata:
  name: vela-addon-registry
  namespace: vela-system
data:
  registries: '{
  "KubeVela":{
    "name": "KubeVela",
    "helm": {
      "url": "https://addons.kubevela.net"
    }
  }
}'

@clcc2019 Are there any more updates?

I'm closing this issue as there's no more info, feel free to reopen it if you still occur this issue in v1.3.3


IE 11 "Object expected" exception on form validation error

Prerequisites

[x] I have read the documentation.

Description
In IE 11 form validation errors are triggering "Object expected" exception. IE Edge works fine.
The exception is thrown only after babel transformations of function toErrorSchema https://github.com/mozilla-services/react-jsonschema-form/blob/770e5a4c7496824bff77bac14fb5a7749ada3bdf/src/validate.js#L24
It exists both in this github playground and npm dependencies, since the code there is already transformed by babel.
Here's validate.js from npm (playground uses same code, but obfuscated):
https://gist.github.com/alex-perfilov-reisys/d50d53bc2f15a1195ebf9a4d416d92f0#file-validate-js-original-bad-compilation-L86
So the problematic line is 86, in the toErrorSchema function.
I'm not sure which plugin is spoiling it, but I was able to fix it for myself [ugly way for now].
I took all the validate.js and compiled it using https://babeljs.io/repl/ website online, that's the result:
https://gist.github.com/alex-perfilov-reisys/c060b6509660fdb32f929872ee09e29e
And saved it in my node_modules. As I said, I know that's wrong. But it works.
Steps to Reproduce

Open IE 11
Go to playground https://mozilla-services.github.io/react-jsonschema-form/
Click "Errors" tab

Expected behavior
The form is shown with validation errors
Actual behavior
Form is not rendered at all, Exception thrown.

Version
any

I'm closing this. Feel free to reopen if you plan to work on a fix.

As of May 2017, the report of alex-perfilov-reisys is still vaild: RJSF seems to still have the issue reported here with IE11, even on the playground https://mozilla-services.github.io/react-jsonschema-form/
For all those looking for support of IE11 (and do not look for highest efficiency), use import "babel-polyfill" at the beginning of the app - and the error disappears... ;)

@oliver-bauer this is probably worth adding a note about that in the README; would you be willing to take care of this work?

@oliver-bauer babel-polyfill doesn't seem to do the trick for me. I get the exact same error. Neither is including polyfills with polyfill.io. Any idea what was the specific polyfill that fixed this for you?

Related also to #206.


Don't explode when we can't find version info

Notices may contain only partially-correct information about the amendments.
Rather than exploding when there's an inconsistency, log it. This fixes
current integration test failures.
Different solution, but resolves #357

👍


Ensure Inky content is unescaped.

Just adds .html_safe to the output of Inky::Core.re_inject_raws. Fixes #10

Awesome, thanks for the PR.


add language file for: de

oh yes - i should proof read twice if i write something in the night ;)

Thank you!

thanks @muescha @fregante


refactor: Remove non-batching event code path (v2 events endpoint)

Instructions

PR target branch should be against development
PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary
I had to rebase development into the approved PR from https://github.com/mParticle/mparticle-web-sdk/pull/494 due to the potential conflicts.  Fortunately there were no conflicts, but there were a few failing tests. The first commit has already been approved (its commit hash is just difference because of the rebase). The other changes I made can easily be reviewd in commit hash 43a3b20:

In order to reduce the flakiness of each test, and make each test module more silo'd, I decided to add beforeEach/afterEach clauses where I set and reset the fetchMock each time.  This reduces some of the need to go to test-main.js to figure out what is happening (although it is less DRY, I think it's an improvement).
The test should trigger beacon on page visibilitychange events was flakey and so I updated it to use lastCall instead of getCalls()[0] to always identify the correct call.
Replaced a string with url.events for DRY-ness.

Testing Plan

[x] Was this tested locally? If not, explain why.

Reference Issue (For mParticle employees only.  Ignore if you are an outside contributor)

Closes https://go.mparticle.com/work/SQDSDKS-5315

closing in favor of
https://github.com/mParticle/mparticle-web-sdk/pull/518
https://github.com/mParticle/mparticle-web-sdk/pull/519
https://github.com/mParticle/mparticle-web-sdk/pull/520
https://github.com/mParticle/mparticle-web-sdk/pull/522
https://github.com/mParticle/mparticle-web-sdk/pull/523
https://github.com/mParticle/mparticle-web-sdk/pull/525
https://github.com/mParticle/mparticle-web-sdk/pull/528


Add external TileSetAtlasSource to TileSet

The TileSet editor can create a TileSetAtlasSource when adding a Texture2D to the source list. But there is no way to add an external TileSetAtlasSource there.
This would be useful when importing TileSetAtlasSources from external formats like Aseprite or others.
The TileSet is too complex a structure to import entirely from these formats. But importing TileSetAtlasSource would be the best option. In this case, when updating the graphic file, the resource would be automatically reimported and the TileSet updated. This will add responsiveness to the editor.

I'm sorry, I didn't look closely: TileSetSource has a hard connection with one tileset, and therefore cannot be used in several tilesets at once.
It's a pity. This pull request will have to be closed.


RSL refresh

Summary of changes
Asana Ticket: RSL | Update page content and layout
Updated RSL to match mocks.
Generic location card html:  refactored PSL and RSL location cards a bit to use a generic component.
Fixed trip planner link:  the PSL trip planner link didn't direct to the correct "to".  Rewrote for the RSL and PSL.

Also checking the following:

[ ] Does frontend functionality render and work correctly in IE?
[ ] Are interactive elements accessible to screen readers?

Maybe a question for Yinka, but I noticed that the styling is different from before. As in, how many cards we're showing/how wide they are.
In prod:

In this PR:


Fix bug in remove_join_expressions

Which issue does this PR close?

Closes #11621.
Rationale for this change
Given an example query:
SELECT * FROM t1 JOIN t2 ON t1.v1 = t2.v1 WHERE (t1.v1 == t2.v1) OR t1.v1

When removing the join predicate t1.v1 = t2.v1 from the parent filter (t1.v1 == t2.v1) OR t1.v1,  this process can be considered as replacing the join predicate with true. The result should be TRUE OR t1.v1 and further simplified to empty, but currently, it is t1.v1. This will lead to incorrect join results.
What changes are included in this PR?

Are these changes tested?
Yes
Are there any user-facing changes?
No

The failure of clippy is unrelated to the current changes.

error: use of deprecated method arrow_schema::Schema::all_fields: Use flattened_fields instead

Thanks for the review @alamb


Cannot log into NewsBlur

Had this error since the alphas. Always the same: "Network error. Try again later."
Tried different networks etc. nothing fixes it.

Which version of NetNewsWire are you running (according to the About window)?

Do you have any special characters in your username or password?

yes there is a semicolon in my password. is that really it??

Which version of NetNewsWire are you running (according to the About window)?

6.0d5 (6005)

Do you have any special characters in your username or password?

Yes there is a semicolon in my password. is that really it??

It’s a good idea to get the latest beta: https://nnw.ranchero.com/2021/03/13/netnewswire-b-for.html

That is probably the problem. It is the same as #2886. I fixed this for all services and the fix is coming in the next Beta.

Oops, I linked the wrong issue. This was actually fixed in #2884.

I'm getting the same error with 6.0.2. No special characters in password, but am using a custom port and https (both defined in API URL).

The problem was an incorrect base_url in config.php affecting the API URL. My base_url is non-standard cause of running behind a reverse proxy + SSL. FreshRSS logs just mentioned password was incorrect.

It’s working for you now?


Support CocoaPods

@ahizzle Thank you.  I hope this gets merged soon.
This is badly needed since react native >= 0.60 is using pods for everything.
Without a podspec, I cannot figure out how to solve the following error since React is already included in my project's Podfile.
/node_modules/react-native-tcp/ios/TcpSockets.m:6:9: fatal error: 'React/RCTAssert.h' file not found
#import <React/RCTAssert.h>

@ahizzle @esutton I recently started helping to maintain this package, maintenance has moved to a fork. Mind repointing your PR to https://github.com/aprock/react-native-tcp? I have contributor permission there.

@phillbaker thanks for the tip.
I am using @ahizzle fork since I need pod support now.
    "react-native-tcp": "https://github.com/atvenu/react-native-tcp.git",

I've opened a PR for the aprock fork.


chore: Add machine types

Fixes #
Description

Adds v1alpha1/Machine types to the Karpenter Core repo

How was this change tested?
make presubmit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 115 (0.0%)  changed or added relevant lines in 3 files are covered.
18 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-1.2%) to 74.873%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1alpha1/register.go
0
8
0.0%

pkg/apis/v1alpha1/machine_status.go
0
14
0.0%

pkg/apis/v1alpha1/zz_generated.deepcopy.go
0
93
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/scheduling/requirements.go
2
98.45%

pkg/test/environment.go
6
73.91%

pkg/controllers/provisioning/scheduling/topology.go
10
84.71%

Totals

Change from base Build<PHONE_NUMBER>:
-1.2%

Covered Lines:
5307

Relevant Lines:
7088

💛  - Coveralls


TypeScript refactoring

Hi!
Here's my small contribution.

[x] Fully refactored using TypeScript (ES6)
[x] Deps are updated
[x] Node v12 support
[x] All tests are green

The README needs some updates to be compliant with the current changes but changes are minors for those who are using it actually.

@warner any chance to merge it?

@antoine-pous why did you close it?

@antoine-pous why did you close it?

It appears that they won't maintain/merge it, then i've closed it. You can still use it from my repo if needed by running:
Using Yarn: yarn add antoine-pous/node-srp-typescript
Using NPM: npm install git://github.com/antoine-pous/node-srp-typescript.git --save
Feel free to report any issue, the day they want merge it they can contact me back :)

It appears that they won't maintain/merge it, then i've closed it. You can still use it from my repo if needed by running:
Using Yarn: yarn add antoine-pous/node-srp-typescript
Using NPM: npm install git://github.com/antoine-pous/node-srp-typescript.git --save
Feel free to report any issue, the day they want merge it they can contact me back :)


Debug both javascript and c# in ASP.NET Core MVC using VS Code

Is there a way to set breakpoints and debug javascript and c# at the same time in VS Code (on macOS)?
I have installed the chrome debugger extension and then created a new MVC app using dotnet new mvc.
But when I launch the app breakpoint are only hit in the C# files, they stay grayed out in the js files (site.js) because no symbols have been loaded.
These are my launch settings (the only thing I have modified is osx command because chrome is not my default browser on macOS):
"version": "0.2.0",
   "configurations": [
        {
            "name": ".NET Core Launch (web)",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceRoot}/bin/Debug/netcoreapp1.1/Foo.PhotoSite.dll",
            "args": [],
            "cwd": "${workspaceRoot}",
            "stopAtEntry": false,
            "internalConsoleOptions": "openOnSessionStart",
            "launchBrowser": {
                "enabled": true,
                "args": "${auto-detect-url}",
                "windows": {
                    "command": "cmd.exe",
                    "args": "/C start ${auto-detect-url}"
                },
                "osx": {
                    "command": "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
                },
                "linux": {
                    "command": "xdg-open"
                }
            },
            "env": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "sourceFileMap": {
                "/Views": "${workspaceRoot}/Views"
            }

@bitbonk : No, there is no way to do that in VS Code. The best you can do is run two different instances of VS Code. In your first instance, remove the launchBrowser element. Start debugging that. Once debugging launches in that instance you could then F5 your chrome debugging instance.

@bitbonk i asked myself the same question. I asked here on Stackoverflow and gave myself the answer after some research. I don't know if this will work on mac, but give it a try.


Add boid wandering to cystoids

Description
It'd be really nice if cystoids wandered in a boid fasion, to ensure that when they attack something, they'll do it together. The hivemind could probably ensure they attack together, but they'd need to wander together for the hivemind to even matter.

Scratch that, instead they should follow the weaver that created them, like mind controlled pawns do with their telepath.


Hide sidebar on Firefox

The 8d9fb271523d70c6889a6ef831218e17dcf746fe commit doesn't work on Firefox. Works on Chrome.

Thank you for reporting it @bptrsn.
Fixed - 710b1911aff3ece37921d202661dda6f6fb65ed2


add doc for instructions on how to create draft plugins

closing in favour of #662 since that one contains more background context/thoughts on this :)


Mecvibes does not open in POP OS 22.04 with Nvidia Card

Mechvibes does not open both in .deb and in appimage and in the snap it opens, however, the screen is loading and does not load the sounds in POP OS 22.04 with Nvidia Card.

Dupe of #171


Use dependabot?

Got this after forking: https://github.com/plata/ublue-surface/pull/1

I think we're using dependabot, yeah, https://github.com/ublue-os/startingpoint/blob/main/.github/dependabot.yml.
Most of the time you can just go ahead and merge the PRs it generates, or close them and wait until this repo updates (whenever dependabot alerts us to)

Ah I see, the schedule is weekly. So that's likely the reason why I already got the PR.


Encrypted MP3's (MP3_160_ENC)

So I scraped the new Protobuf layout from Spotify's javascript file, and it seems that value '7' in AudioFormat is "MP3_160_ENC", which I am guessing is an encrypted MP3.
For some tracks, sending "sp/track_uri" with args ["mp3160", songid] sends a "Failed to send to backend" #116  or a "TrackError: Account subscription status not Spotify Premium" #111 .
Instead, you must send a "sp/track_uri2" command with args [songid, fileid]. This is what the web player currently does. Unfortunately though, there is no "MP3_160" file id for songs now, only a "MP3_160_ENC" file id, that then gives you a URL for an encoded MP3.
Has anyone else seen this or know of a way of decrypting the MP3's? I imagine it must be some flash applet that does the decrypting.

After some investigation I found out that the server replies an "album_art" message right after a "track_uri2" call. And it contains a javascript code which, when eval'd, returns what appears to be a key to the player.
The bad thing is that they don't use any conventional encryption system and they compiled the functions on the swf using flascc. We will have bad time in order to figure out how they do it.

Hi.
I've receiving the message "Failed to send to backend" too. Just a tip: amagus, maybe the trouble could be similar to the pingpong issue??

This is harder than the pingpong issue since the full decoding of the MP3 would be needed. And does not communicate back to the server, it simply play the file.
I still have no clue in how to do this rather than looking instruction by instruction on the flascc generated code.

I couldn't get that message (album_art). How did you found it?

It's a message sent by the server right after replying the track_uri2 request.
http://imgur.com/YEGaFuB

Hi, I'm debugging it now. How can I get the FileID? I don't find it in the track object.

So I managed to extract the actionscript bytecode from player.swf, then include my own main class that calls into the relevant bytecode functions ('pocus', 'evaluate' and 'hocus_pocus').
So this would work if you tried to decrypt one of the files, although it's clearly ugly because you still have to run an swf. I can't work out which actual algorithm it is using. There is a public and private key, but it is not RSA.
The public key is given in the "album_art" message, the private key is compiled with the swf.

Actually its symmetric RC4, SHA-1 HMACs and good ol' XOR. Got a few notes here. Should have something in a few days.

Nice work! I'll give an implementation a go as well.

wow. nice work guys!

Actually the guys from the Shigawire's fork of node-spotify-web figured out how to fix the issue

I've not been getting the 'album_art' message for about a week now so it just hangs. Is that happening (no happening) for anyone else?


make docker daemon on Minikube VM  use proxy

I am a fresh man from China,you must know about the terrible GWF.
When I use Minikube ,I faced the problem that how to configure Internet setting correctly to make everything work.
Due to the proxy on my PC,the Docker daemon in Minikube can't  access Internet.I have tried the way
on document as follows:
$ minikube start --docker-env HTTP_PROXY=http://$YOURPROXY:PORT
--docker-env HTTPS_PROXY=https://$YOURPROXY:PORT
However,seems it doesn't work,I checked the log on Minikube Virtual Machine which reveals that the Docker still connect network directly rather than use proxy.
The content I added into the document is the way that works on my computer.Docker daemon in Minikube works successfully base on these.
Hope it  helps.^_^

This change is

Hey,
It looks like this might be a bug in minikube itself, if you have to make the change this way. Would you mind opening an issue in the minikube repo and we can fix it there rather than have to make this documentation change?

@dlorenc  ok，thanks

@dlorenc  minikube repo:#1723

@dlorenc So, can I close this PR then?

Yeah you should be able to close this.


Delete an account from the service

As an administrator
I need a function to delete accounts
So that account list will be relevant
Details and Assumptions
* access to the database is available, credentials are verified

Acceptance Criteria
gherkin
Given a delete request is sent
When account id is provided
Then [account_id] is deleted


⚠ Bofrost.com has degraded performance

In d4d1506, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 723 ms

Resolved: Bofrost.com performance has improved in e2f63d4 after 6 minutes.


Datum data leakage

What happened?:
I have a pipeline where a temporary folder for some of the processing and found out that this may cause data leakage between datums. The datum data leakage then caused a whole slew of unexpected bugs such as repeated processing.
What you expected to happen?:
A datum should not be exposed to data from other datums.
How to reproduce it (as minimally and precisely as possible)?:

I input sample data into a repo. In this example i've used the images from the tutorial under the repo images.
Used the following code:

import os
import shutil

# reproduces the bug
def do_stuff(image):
    print("copying file to temp dir")
    shutil.copy(image, '/tmp/foo')
    print(os.listdir('/tmp/foo'))
    print("ALL DONE!")

# walk /pfs/images
print("started another datum!")
for dirpath, dirs, files in os.walk("/pfs/images"):
    os.makedirs('/tmp/foo', exist_ok=True) # create a temporary directory
    for file in files:
       do_stuff(os.path.join(dirpath, file))

And the following pipeline spec:
{
  "pipeline": {
    "name": "bugrepro"
  },
  "description": "A pipeline that reproduces the bug",
  "transform": {
    "cmd": [ "python3", "/main.py" ],
    "image": "foo"
  },
  "input": {
    "pfs": {
      "repo": "images",
      "glob": "/*"
    }
  }
}

The resulting output from the logs:
started another datum!
copying file to temp dir
['kitten.png']
ALL DONE!
started another datum!
copying file to temp dir
['AT-AT.png', 'kitten.png']
ALL DONE!
started another datum!
copying file to temp dir
['AT-AT.png', 'liberty.png', 'kitten.png']
ALL DONE!

Anything else we need to know?:
This was reproduced in Pachyderm Hub using the version as of today (1.10.3).

This is an expected behavior, but I can definitely see how that's crazy confusing and hard to debug. Really sorry you hit this!
Pachyderm only controls and wipes the /pfs directories between datums.  If scratch/temp space is used during execution, the user needs to be careful to clean that up.
I thought we had this documented but can't seem to find it. Will try to make that clearer. Just talked to eng about this further and there might be a few ways we can harden things to make it less likely for users to have this happen.

Thanks for the quick input @JoeyZwicker
Just to share my experience with this, the user will naturally start looking at whether a datum has retried but won't see any retry related logging messages from Pachyderm. I actually found out that this caused significant re-processing in the pipeline and that the longer the job, the more data written into the temp folder and the more processing taking place. We spent quite some time on figuring this one through as a user would originally think that data leakage between containers is extremely unlikely.
I've been using Pachyderm for quite some time and was totally surprised by this. As this creates possible security implications, I think at minimum this has to appear in the docs.

@jdoliner If you have some ideas based on our offline conversation, can you add some more details about various ways we can potentially protect things a little better?
We discussed a few ideas:

potentially making a /pfs/scratch dir for people to use explicitly.
Or explicitly wiping /tmp as a way to cover some common datum leakage
making the default that everything except pfs/out is read-only unless you set a pipeline flag. There are some challenging implications of this which is that many applications (I have no idea which ones or what percentage) may behind the scenes try to use tmp or scratch space and then will fail by default.

I think the overall notion is that:

datum leakage in general is not a use case we to support on purpose. The user has minimal control over datum and pod scheduling. We used to have incrementality as a fully-supported feature, but have not seen many common needs for bringing it back.
We don't want break libraries or user processes that need to write to other dirs. Many (definitely not all) libraries that do this behind the scenes, probably clean up after themselves. It's when users do it as scratch space in their code that they often forget.
This is, understandably, a very subtle and difficult thing for user to debug themselves, as @RaananHadar pointed out. Users grok that every datum is separate, but the fact that pachyderm only wipes /pfs is a minutia that, even through documentation, is hard for users to learn.  We can document it better, but may want to go further than that.

@svekars, in speaking with Raanan, we think that this might be the best place to make a "warning" or "note".
I would probably put it around this section: https://docs.pachyderm.com/latest/concepts/pipeline-concepts/datum/relationship-between-datums/. It discusses the relationship between datums, and how datums output relate to each other, for example, what happens if two datums write the same file in pfs/out. Clarifying which parts of the file system are cleaned up between independently run datums probably could fit somewhere in there.

I think the only thing that really makes sense to me as a product change is to add an option for a /pfs/scratch directory that gets cleared every time. I think that's the best we can do for official support. The other ideas either don't solve the problem or introduce risks of breaking other things.

clear /tmp should in theory be fine, although there's a risk that some apps and libraries at cache to /tmp now won't run as well in Pachyderm. And it only solves the problem if people know to use tmp, so because of those two things it doesn't seem worth it.
Making everything readonly has the potential to break a lot of things so I don't think it's worth doing it.

Ultimately I think most of the solution here is going to be in docs, turning anything on by default has too much potential to break things, so we're going to need to make users aware of the complications associated with persisting things during datum processing.

Hi,
I've created a PR, that addresses the docs for this.
I still feel strongly that to fully address this issue I wouldn't count on docs alone. Our current solution is for each pipeline to use a random string for a temporary directory. Giving this some thought, this is not a good solution as it would eventually lead to a storage leak and the pod size increasing over time. I am betting that this leak might be a prevalent issue with other users who aren't even aware of this subtlety...
There is an excellent lecture behind one of the maintainers of k8s here where he specifies that one of the core principles of k8s is "meet the user where they are" so basically a code written in k8s does not need to know that it was written in k8s. This has been largely implemented successfully in Pachyderm so far, but forcing the user to create their temp dir in a specific way and clean up introduces some quirks and caveats that a serious user needs to know in the long term.
I really think that a /pfs/scratch dir is the way to go. This way it, can be passed as an argument to the code and the user can use a different argument when not running in Pachyderm. And you are saving the warnings for the user for having to take special care with temporary files, which are a common scenario.


HDDS-8487. Recon Heatmap UI Changes and Size Normalization

What changes were proposed in this pull request?
HeatMap Changes

Size Normalization.
Color Change
Disabled Currentlt setting by flag.
Changed pnpm version to latest one

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8487
How was this patch tested?
Manually

@ivandika3
Can you review my UI heatmap PR?

@sumitagrawl  @dombizita @devmadhuu
Completed all changes suggested by Ivan you can merge PR.

Completed all changes suggested by Siyao.


Correct translation in 'Building' section of README

Fixes #73

Oops.. Thanks for your attention @barrymcgee


[dev.fuzz] do not instrument packages which are non-deterministic

During development I've noticed that reported coverage will often decrease after restarting fuzzing, indicating that counters are being incremented by functionality not triggered by the code being fuzzed.
Doing some manual testing while working on a encoding/json indicates that sync in particular is quite noisy and will cause new edges to be triggered for the first couple of seconds.
We probably can't automate this for third party code (although we should probably document that if you're fuzzing code that i.e. spawns background goroutines in an init it may be quite noisy) we may want to make an effort to find packages in the stdlib which have this problem. The simplest approach to this would be to run a fuzz target which does nothing (f.Fuzz(func(_ *testing.T, _b_ []byte) {})) and incrementally instrument packages. Anything that then increases counted edges can probably be considered noisy, and should be considered for exclusion (there will, likely, be packages we cannot exclude, despite being noisy).

When instrumenting for fuzzing, I wonder if we could make sync.Pool never reuse objects to work around this problem.
Some form of caching will always be possible - for example, encoding/json uses a global sync.Map to cache other stuff. But at least we could alleviate the problem for pools.

I wonder if we could make sync.Pool never reuse objects to work around this problem.

Object-reuse is a common source of sync.Pool bugs. If I understand the suggestion correctly, I think it would be a mistake to change this behavior when fuzzing.
One alternative might be to hook the scheduler to make it deterministic (based on some seed — #46221?) even for otherwise-nondeterministic code.
My question is, though: what's the harm in exercising nondeterminism? That might mean that the fuzzer explores some redundant parts of the input space, but if the behavior of the function is nondeterministic then it's good to explore some redundant parts of the input space in order to catch scheduling-sensitive bugs (compare #22569, #43794).

My question is, though: what's the harm in exercising nondeterminism? That might mean that the fuzzer explores some redundant parts of the input space, but if the behavior of the function is nondeterministic then it's good to explore some redundant parts of the input space in order to catch scheduling-sensitive bugs (compare #22569, #43794).

I think exercising non-deterministic behavior of the functions being fuzzed is definitely expected behavior, my concern is with non-deterministic behavior of code that isn't being fuzzed. Going back to my initial example, if I'm fuzzing a function which simply does _ = 1 + 1, but by importing a certain package I'm seeing edge coverage increase then we are getting noise that is not productive.
Perhaps that level of noise is acceptable though? It's somewhat hard to tell without a good set of targets to test against whether this will significantly impede the performance of the fuzzing engine.

I think when it comes to fuzzing, not all forms of non-determinism are equally helpful. Randomness or pseudo-randomness is important of course within the mutator, and randomness in how threads or goroutines are scheduled can be helpful, especially if running under a race detector, but it can be less helpful to have randomness in the coverage metrics or randomness in background code that is not under test that effectively drives randomness in the coverage.
FWIW, here is a slightly older snapshot of some of the instrumentation exclusions for dvyukov/go-fuzz:
https://github.com/dvyukov/go-fuzz/blob/fc9bdef631a7086b4708dae03a370f7294c1d335/go-fuzz-build/main.go#L310-L326
	ignore := map[string]bool{
		"runtime":                         true, // lots of non-determinism and irrelevant code paths (e.g. different paths in mallocgc, chans and maps)
		"runtime/internal/atomic":         true, // runtime depends on it
		"runtime/internal/sys":            true, // runtime depends on it
		"unsafe":                          true, // nothing to see here (also creates import cycle with go-fuzz-dep)
		"errors":                          true, // nothing to see here (also creates import cycle with go-fuzz-dep)
		"syscall":                         true, // creates import cycle with go-fuzz-dep (and probably nothing to see here)
		"internal/syscall/windows/sysdll": true, //syscall depends on it
		"sync":             true, // non-deterministic and not interesting (also creates import cycle with go-fuzz-dep)
		"sync/atomic":      true, // not interesting (also creates import cycle with go-fuzz-dep)
		"time":             true, // creates import cycle with go-fuzz-dep
		"internal/bytealg": true, // runtime depends on it
		"internal/cpu":     true, // runtime depends on it
		"internal/race":    true, // runtime depends on it
		"runtime/cgo":      true, // why would we instrument it?
		"runtime/pprof":    true, // why would we instrument it?
		"runtime/race":     true, // why would we instrument it?
	}

(You can of course also look at the current code, but it is more dynamic now, without the associated per-package comments).

@rolandshoemaker

my concern is with non-deterministic behavior of code that isn't being fuzzed.

If you're importing a package that does non-trivial init-time work, then perhaps one solution is for the fuzzer to distinguish between “transient” and “steady-state” runs: a program that has no pending timers and no runnable goroutines is in a steady state, whereas a program that does have pending timers or goroutines does not.
It still seems important to test the transient states, since (for example) a logical race between a background ticker and the API under test would not be diagnosed if we only tested steady states. But we could at least treat the coverage from transients different from the coverage for steady states, or try to run the program to a steady state before fuzzing to get a baseline for the “steady-state coverage”.

What packages are currently getting instrumented?
From the initial writeup of this issue, I was incorrectly interpreting that it was instrumenting the runtime and all of the stdlib, but it looks like that it currently avoids the runtime:
https://github.com/golang/go/blob/dev.fuzz/src/cmd/compile/internal/base/flag.go#L240-L241
For example, is it instrumenting syscall? If so, that's one example that was causing a crash in an earlier incarnation of the compiler instrumentation (via go114-fuzz-build) under OSS-Fuzz: https://github.com/google/oss-fuzz/issues/3639#issuecomment-613604967.
For a beta / early MVP, it might be better to start by notching out the "noisy" / non-deterministic packages that go-fuzz was notching out from the stdlib (e.g., sync), which is part of what I was trying to say above...


xcodebuild[9255:188990] [MT] DVTPlugInManager: Required plug-in compatibility UUID 42E1F17B-27B3-4DE8-92A8-DC76BA4F5921 for DVTCoreGlyphs.framework (com.apple.dt.DVTCoreGlyphs) not present

i was trying to run the demo app but some problem with flutter app on ios build android is working fine and normal xcode project with swift works fine
the error is

logs
Launching lib/main.dart on iPhone 12 Pro Max in debug mode...
Running Xcode build...
Xcode build done.                                           10.8s
Failed to build iOS app
Error output from Xcode build:
↳
    2021-06-17 01:56:14.273 xcodebuild[9255:188990] [MT] DVTPlugInManager: Required plug-in compatibility UUID 42E1F17B-27B3-4DE8-92A8-DC76BA4F5921 for DVTCoreGlyphs.framework (com.apple.dt.DVTCoreGlyphs) not present
    ** BUILD FAILED **

Xcode's output:
↳
    note: Using new build system
    note: Planning
    note: Build preparation complete
    warning: Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
    /Users/ajaylee/AndroidStudioProjects/eat/ios/Flutter/Debug.xcconfig:1:1: error: unable to open file (in target "Runner" in project "Runner")
    /Users/ajaylee/AndroidStudioProjects/eat/ios/Flutter/Debug.xcconfig:1:1: error: unable to open file (in target "Runner" in project "Runner")
    /Users/ajaylee/AndroidStudioProjects/eat/ios/Flutter/Debug.xcconfig:1:1: error: unable to open file (in target "Runner" in project "Runner")
    warning: ONLY_ACTIVE_ARCH=YES requested with multiple ARCHS and no run destination to provide an active architecture; building for all applicable architectures (in target 'Runner' from project 'Runner')
    warning: Capabilities for Signing & Capabilities may not function correctly because its entitlements use a placeholder team ID. To resolve this, select a development team in the Runner editor. (in target 'Runner' from project 'Runner')

Could not build the application for the simulator.
Error launching application on iPhone 12 Pro Max.

flutter doctor -v

flutter doctor -v
[✓] Flutter (Channel unknown, 2.2.0, on macOS 11.3.1 20E241 darwin-x64, locale
    en-GB)
    • Flutter version 2.2.0 at /Users/ajaylee/development/flutter
    • Framework revision b22742018b (5 weeks ago), 2021-05-14 19:12:57 -0700
    • Engine revision a9d88a4d18
    • Dart version 2.13.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/ajaylee/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode-beta.app/Contents/Developer
    • Xcode 13.0, Build version 13A5154h
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.57.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.23.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 11.3.1 20E241 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 91.0.4472.101

• No issues found!

what to do now i tried uninstalling and installing but nothing works for me

Hi @ajailee
Whenever you download someone's code sample, execute flutter clean and then run the app. See https://github.com/flutter/flutter/issues/18712
If the problem persists, please try with a new project
flutter create myapp
cd myapp
flutter run -v
If you're running on the physical device, be sure to add team ID in the Xcode
Thank you

I tried but I can't find so I uninstalled 13 beta and installed the 12.0.1


Update VS2013 template to VS2015

Kindly update VS2013 template to use in VS2015 and with the newest release of Arrayfire 3.4.

For the time being, we do not anticipate adding VS2015 example project to ArrayFire given the following reasons:

ArrayFire still has a minimum dependency of VS2013, hence to keep in touch with that, we will continue to ship VS2013 project files.
VS2013 project files can be upgraded to VS2015. However, VS2015 files cannot be downgraded.
Given that VS2013 can be upgraded, shipping additional VS2015 files is purely overhead.
CUDA 7.5 does not support VS2015.
VS2013 is still has a very high usage ratio.

If one or more of these reasons change in the future we might look to add it. So I will leave this issue open.

This has been added to master.

I tried to run HELLOWORD in VS2015 with CUDA8.0, having following errors:

These libraries are installed with CUDA installation, as I know.

ArrayFire v3.4.0 is still on CUDA 7.5. We completed this release with the v3.4.1 release in mind which will happen on Monday, Oct 17 2016.


ID namespace error when deploying almond-server via podman

/kind bug
Description

Steps to reproduce the issue:
podman run -p 3000:3000 --uidmap keep-id \
-v /dev/shm:/dev/shm \
-v $XDG_RUNTIME_DIR/pulse:/run/pulse \
-v ${XDG_CONFIG_HOME:-$HOME/.config}/almond-server:/var/lib/almond-server \
minnixtx/almond-server:arm64
Describe the results you received:
ERRO[0615] Error while applying layer: ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 192:192 for /run/systemd/netif): lchown /run/systemd/netif: invalid argument
  ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 192:192 for /run/systemd/netif): lchown /run/systemd/netif: invalid argument
Trying to pull quay.io/minnixtx/almond-server:arm64...
  unauthorized: access to the requested resource is not authorized
Error: unable to pull minnixtx/almond-server:arm64: 2 errors occurred:
	* Error committing the finished image: error adding layer with blob "sha256:dbad5a3d9e059ad673cb03431604f7d02d3d16a4f6bad97eab35b8db19259d0b": ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 192:192 for /run/systemd/netif): lchown /run/systemd/netif: invalid argument
	* Error initializing source docker://quay.io/minnixtx/almond-server:arm64: Error reading manifest arm64 in quay.io/minnixtx/almond-server: unauthorized: access to the requested resource is not authorized
Describe the results you expected:
I expected the Almond virtual assistant server to run and be accessible via port 3000
Additional information you deem important (e.g. issue happens only occasionally):
Happens every time.
Output of podman version:
Version:            1.8.2
RemoteAPI Version:  1
Go Version:         go1.11.6
OS/Arch:            linux/arm64
Output of podman info --debug:

debug info
$ podman info --debug
debug:
  compiler: gc
  git commit: ""
  go version: go1.11.6
  podman version: 1.8.2
host:
  BuildahVersion: 1.14.3
  CgroupVersion: v1
  Conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.14, commit: '
  Distribution:
    distribution: debian
    version: "10"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
  MemFree: 155422720
  MemTotal: 502472704
  OCIRuntime:
    name: runc
    package: 'containerd.io: /usr/bin/runc'
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10
      commit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
      spec: 1.0.1-dev
  SwapFree: 187531264
  SwapTotal: 251232256
  arch: arm64
  cpus: 4
  eventlogger: file
  hostname: orangepizeroplus2-h5
  kernel: 5.4.28-sunxi64
  os: linux
  rootless: true
  uptime: 15h 10m 23.08s (Approximately 0.62 days)
registries:
  search:
  - docker.io
  - quay.io
store:
  ConfigFile: /home/minnix/.config/containers/storage.conf
  ContainerStore:
    number: 0
  GraphDriverName: vfs
  GraphOptions: {}
  GraphRoot: /home/minnix/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 0
  RunRoot: /run/user/1000/containers
  VolumePath: /home/minnix/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
~$ apt list podman
Listing... Done
podman/unknown 1.8.2~140 amd64
podman/unknown,now 1.8.2~140 arm64 [installed]
podman/unknown 1.8.2~140 armhf
podman/unknown 1.8.2~140 ppc64el
Additional environment details (AWS, VirtualBox, physical, etc.):
For context, I have been working on building an arm64 container for the Stanford OVAL virtual assistant: Github page is here. After cloning their git repo, the image builds successfully using buildx and pushes to registry. My docker build command:
docker buildx build -t minnixtx/almond-server:arm64 --platform=linux/arm64 . --push
The podman command I used is the recommended one from the almond-server github page.

My Dockerfile
FROM docker.io/fedora:31

# Install all deps in the standard repos
RUN dnf -y module install nodejs:10 && \
    dnf -y install git curl pulseaudio-libs-devel unzip nodejs make gcc gcc-c++ libcanberra-devel atlas-devel blas-devel

# Install yarn
RUN curl -sL https://dl.yarnpkg.com/rpm/yarn.repo | tee /etc/yum.repos.d/yarn.repo
RUN dnf -y install python yarn

RUN mkdir /opt/almond
COPY . /opt/almond
WORKDIR /opt/almond

# snowboy doesn't like building in docker, due to overlayfs bugs...
RUN rm -rf /opt/almond/node_modules && \
    yarn --network-timeout 1000000 && \
    cp -Tr /usr/local/share/.cache/yarn/v6/npm-snowboy-1.3.1-220f23f026096fe5290d7919a9f0da93ccd253f2-integrity/node_modules/snowboy/ node_modules/snowboy/ && \
    (cd node_modules/snowboy/ && yarn install --ignore-scripts --no-lockfile && yarn run install) && \
    rm -fr /usr/local/share/.cache

EXPOSE 3000
ENV THINGENGINE_HOME=/var/lib/almond-server
ENV PULSE_SOCKET=unix:/run/pulse/native

ENTRYPOINT [ "yarn", "start"]

My repo: https://hub.docker.com/r/minnixtx/almond-server/tags
If any more info is needed please let me know. The device is an Orange Pi Zero Plus2 H5 running armbian.

Looks like your user may not have a valid mapping in /etc/subuid and /etc/subgid. Can you provide both of those files, plus the output of podman unshare cat /proc/self/uid_map

/etc/subuid:
minnix:100000:65536
/etc/subgid:
minnix:100000:65536
$ podman unshare cat /proc/self/uid_map
         0       1000          1

Can you try a podman system migrate and then see if things start working?

Ok will try it and post back

I'm going to reformat and reinstall and report back. I think I've kind of screwed things up with too much fiddling around.

Still more errors:
$ podman system migrate
$ podman run -p 3000:3000 --uidmap keep-id -v /dev/shm:/dev/shm -v $XDG_RUNTIME_DIR/pulse:/run/pulse -v ${XDG_CONFIG_HOME:-$HOME/.config}/almond-server:/var/lib/almond-server minnixtx/almond-server:arm64
Trying to pull docker.io/minnixtx/almond-server:arm64...
Getting image source signatures
Copying blob f77d8914c709 done
Copying blob 687c2f71b096 done
Copying blob f42516629c75 done
Copying blob dbad5a3d9e05 done
Copying blob 6fec01a34141 done
Copying blob bd1b6c7d8d9b done
Copying blob 436bdb7986f9 done
Copying blob 2046c413010f done
Copying config dbc3810e02 done
Writing manifest to image destination
Storing signatures
ERRO[0599] Error while applying layer: ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 192:192 for /run/systemd/netif): lchown /run/systemd/netif: invalid argument
  ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 192:192 for /run/systemd/netif): lchown /run/systemd/netif: invalid argument
Trying to pull quay.io/minnixtx/almond-server:arm64...
  unauthorized: access to the requested resource is not authorized
Error: unable to pull minnixtx/almond-server:arm64: 2 errors occurred:
	* Error committing the finished image: error adding layer with blob "sha256:dbad5a3d9e059ad673cb03431604f7d02d3d16a4f6bad97eab35b8db19259d0b": ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 192:192 for /run/systemd/netif): lchown /run/systemd/netif: invalid argument
	* Error initializing source docker://quay.io/minnixtx/almond-server:arm64: Error reading manifest arm64 in quay.io/minnixtx/almond-server: unauthorized: access to the requested resource is not authorized

Could you try this as root.  This might be something to do with the user namespace?
ERRO[0599] Error while applying layer: ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 192:192 for /run/systemd/netif): lchown /run/systemd/netif: invalid argument
Also what is the output of
$ podman unshare cat /proc/self/uid_map

Hello thanks for your help and sorry for the delay. I promise to get back to this ASAP. It is hectic here right now. Just want to say I am appreciative and haven't forgotten.

@minnixtx Any progress?

Since we have had 0 activity in a couple of months, I am going to close this. Reopen if we need to make progress.