Filter out EventEx by default to avoid event storm damage.

Though I don't necessarily agree with blocking EventEx wholesale as
there may be important events lost, the opposing argument is that, in
practice, when there is an event storm, they are usually EventEx events,
and the event storm brings down the entire system.  We have experienced
this many times at customer sites, and the downside is not worth the
upside.
Users can remove this value from the filtering if needed, and put in
more specific filtering of events.  Additionally, we still cut a log
message when we filter out the event, so its presence is still available
in the log.
https://bugzilla.redhat.com/show_bug.cgi?id=1079489

We should definitely put this in the ChangeLog in case anyone is reacting to this event.
Does it make sense to implement a throttling mechanism to prevent event storms from killing the system while also allowing useful events to come through?  I'm wondering if that would be a longer term solution instead of filtering events.
What do you think?

We should definitely put this in the ChangeLog in case anyone is reacting to this event.

Yes it will go in the changelog at sprint end

Does it make sense to implement a throttling mechanism

I agree, but I think this tactical solution should still go in for now.  @bzwei had started something like this, but I think it was put on the backburner?  See #25 for the DuplicateBlocker class he implemented as a class to use for doing short-circuit style throttling.  cc @gmcculloug

Agree. Merging now since throttling is not ready for this specific issue.


securefs 0.6.0

Created with brew bump-formula-pr.
Closes #98

Thanks for your contribution to Homebrew!  You rock!


[reggen] Add bitfield.h-style constants to reggen's output

This PR adds new constants to reggen's output. For a non-bit-sized register field, in addition to FIELD_MASK and FIELD_OFFSET, we now generate
#define FIELD ((bitfield_field32_t) { .mask = FIELD_MASK, .index = FIELD_OFFSET })

These defines can be used to make quite a bit of C code more concise; migrating existing code is a trivial ctrl-replace, though I kind of want to do them in batches to minimize merge conflicts. This PR includes a change to I2C as a PoC. I went ahead and did all the easy ones in this PR; some others will come as we remove the nonatomic MMIO functions.
They are currently not (easily) usable in tests, and that will require a somewhat more invasive approach to mock_mmio.h, but it shouldn't be an onerous change.

I think it would be good to suffix these with _FIELD, does anyone have thoughts for/against? My instinct is that this is better for forwards compatibility, where we don't want to just have <REGISTER>_<FIELD> because there are different aspects to things associated with that field of that register. I'm not sure what exactly the suffix should be to keep it short (proposal: _FIELD), but I can say I highly dislike that sometimes you need suffixes and sometimes you don't, depending on how wide the field is, and also that a non-suffixed definition might just be an offset, or might be a wider field, depending on how wide the field is. IMO it'd be better to be clearer about those, so if a register changes widths, we don't get weird type errors that are hard to diagnose.

Could you please in the PR description copy/paste a snippet from one of the _regs.h that has OFFSET, MASK and the new FIELD defines?

My instinct is that this is better for forwards compatibility, where we don't want to just have _ because there are different aspects to things associated with that field of that register.

While I agree with you in principle, there is the issue that we already emit _ for fields that are a single bit wide. I don't think it's unreasonable to say that if we want _FIELD, we should probably also do _BIT or similar?

My instinct is that this is better for forwards compatibility, where we don't want to just have _ because there are different aspects to things associated with that field of that register.

While I agree with you in principle, there is the issue that we already emit _ for fields that are a single bit wide. I don't think it's unreasonable to say that if we want _FIELD, we should probably also do _BIT or similar?

Yes, I would like to also see us move towards using _BIT - though that should be in a future PR, because that seems out of scope for this PR.

@lenary updated to use the _FIELD suffix.


Upgrade electron and other dependencies to fix security vulnerabilities

Summary
The main aim was to upgrade electron to fix a high security vulnerability found in Simorgh https://github.com/bbc/simorgh/network/alert/package-lock.json/electron/open
All other security vulnerabilities were fixed using npm audit. In total there were 234 vulnerabilities (170 low, 11 moderate, 53 high).
The upgrade of electron from 2.0.8 to 7.2.4 meant some breaking changes had to be fixed:

in electron/bbc-a11y.js in webPreferences, nodeIntegration: true had to be set to allow a script in the app's index.html to run https://github.com/bbc/bbc-a11y/blob/master/electron/index.html#L13 as it is defaulted to false in the newer versions of electron. However this throws 3 security warnings we should look into:

security-warnings.ts:161 Electron Security Warning (Disabled webSecurity) This renderer process has "webSecurity" disabled. This
exposes users of this app to severe security risks.

For more information and help, consult
https://electronjs.org/docs/tutorial/security.

security-warnings.ts:196 Electron Security Warning (allowRunningInsecureContent) This renderer process has "allowRunningInsecureContent"
enabled. This exposes users of this app to severe security risks.

For more information and help, consult
https://electronjs.org/docs/tutorial/security.

security-warnings.ts:179 Electron Security Warning (Insecure Content-Security-Policy) This renderer process has either no Content Security
Policy set or a policy with "unsafe-eval" enabled. This exposes users of
this app to unnecessary security risks.

For more information and help, consult
https://electronjs.org/docs/tutorial/security.

onHeadersReceived can no longer accept an empty object as options. If options are provided then it must have an urls property with an array of urls to filter against. The options object is optional so removing the empty object fixes the problem.
in lib/electron/storage.js the session.clearStorageData() is now a promise and not a callback API. Updating to return the promise fixes this issue.
in electron/bbc-a11y.js we now have to add app.commandLine.appendSwitch('disable-site-isolation-trials'); to allow accessing content in a cross-origin iframe. More info here https://stackoverflow.com/questions/55898000/blocked-a-frame-with-origin-file-from-accessing-a-cross-origin-frame

Details

Motivation and Context
A high security vulnerability found in Simorgh.
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I've added tests for my code
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Few failing tests to fix

The tests are failing because the iframe onload event is never called when electron-mocha runs the tests - https://github.com/bbc/bbc-a11y/blob/master/lib/runner.js#L85
I'm not sure why this event doesn't fire anymore.


DeppySource Framework Documentation

User Story
As a user I would like to have all the information I need to create my own DeppySource
Summary / Background
DeppySource is a framework for creating online EntitySources for querying by the Deppy API
Acceptance Criteria

APIs documented
example(s) given

Scenarios
Assumptions
Links (docs, drawings, designs, etc)
Deppy-as-a-Framework
Dependencies
Definition of Done

Readme with a quick start guide
reviewed and merged

Obsolete, closing


Augmented filter on the OXP domain leveraging the full identifier

Fixes #108
Heads-up: this PR sits on top of PR #110
Description of the change

This PR will extend/augment the filter on the OXP domain to also match against the full identifier

With the recent changes on PR  #114 this change here does not seems necessary anymore.


merge package template from arlac77/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template
chore(scripts): update prepare@rollup -c from template

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: add retry test inject failure midway in gRPC ReadObject

Add Retry Test API support for injecting failure midway in gRPC ReadObject

Testbench will fail with UNAVAILABLE after a few downloaded data with retry instructions return-broken-stream
Testbench will fail with UNAVAILABLE after YKiB of downloaded data with retry instructions return-broken-stream-after-YK

Update README

Enable methods that have Retry Test support in gRPC

  "storage.buckets.get",
  "storage.buckets.getIamPolicy",
  "storage.buckets.list",
  "storage.hmacKey.get",
  "storage.hmacKey.list",
  "storage.notifications.get",
  "storage.notifications.list",
  "storage.objects.list",
  "storage.objects.get",
  "storage.serviceaccount.get",

[x] Tests pass

[x] Appropriate changes to README are included in PR

As discussed offline, I updated Retry Test API Forced Failures Support description by transport and clarified how retry instructions result in the gRPC context. @tritone PTAL, thank you!

@coryan Wanted to check with you for future planning if there is any need to support x-goog-emulator-instructions force failures (e.g. return-503-after-256K) in the grpc server?
This PR adds support to the Retry Test API. Planning to merge today if no issues, thanks!

@coryan Wanted to check with you for future planning if there is any need to support x-goog-emulator-instructions force failures (e.g. return-503-after-256K) in the grpc server?

No, and we can always add the support if it becomes needed.


Run "Code/Demos/RDKit/GettingStarted/sample.cpp" got error

Run
g++ -o sample.exe sample.cpp -I$RDBASE/Code -I$RDBASE/Extern \
//       -L$RDBASE/lib -lChemReactions -lFileParsers -lSmilesParse -lDepictor \
//       -lSubstructMatch -lGraphMol -lDataStructs -lRDGeometryLib -lRDGeneral

Got
In file included from /root/RDKit_git/Code/RDGeneral/types.h:28,
                 from /root/RDKit_git/Code/GraphMol/Atom.h:25,
                 from /root/RDKit_git/Code/GraphMol/RDKitBase.h:23,
                 from sample.cpp:17:
/root/RDKit_git/Code/RDGeneral/Dict.h: In member function ‘void RDKit::Dict::setVal(const string&, T&)’:
/root/RDKit_git/Code/RDGeneral/Dict.h:260:25: error: ‘is_same_v’ is not a member of ‘std’
     static_assert(!std::is_same_v<T, std::string_view>,
                         ^~~~~~~~~
/root/RDKit_git/Code/RDGeneral/Dict.h:260:25: note: suggested alternative: ‘is_same’
     static_assert(!std::is_same_v<T, std::string_view>,
                         ^~~~~~~~~
                         is_same
/root/RDKit_git/Code/RDGeneral/Dict.h:260:36: error: expected primary-expression before ‘,’ token
     static_assert(!std::is_same_v<T, std::string_view>,
                                    ^
/root/RDKit_git/Code/RDGeneral/Dict.h:260:38: error: expected string-literal before ‘std’
     static_assert(!std::is_same_v<T, std::string_view>,
                                      ^~~
/root/RDKit_git/Code/RDGeneral/Dict.h:260:37: error: expected ‘)’ before ‘std’
     static_assert(!std::is_same_v<T, std::string_view>,
                  ~                  ^~~~
                                     )
/root/RDKit_git/Code/RDGeneral/Dict.h: In member function ‘void RDKit::Dict::setPODVal(const string&, T)’:
/root/RDKit_git/Code/RDGeneral/Dict.h:275:25: error: ‘is_same_v’ is not a member of ‘std’
     static_assert(!std::is_same_v<T, std::string_view>,
                         ^~~~~~~~~
/root/RDKit_git/Code/RDGeneral/Dict.h:275:25: note: suggested alternative: ‘is_same’
     static_assert(!std::is_same_v<T, std::string_view>,
                         ^~~~~~~~~
                         is_same
/root/RDKit_git/Code/RDGeneral/Dict.h:275:36: error: expected primary-expression before ‘,’ token
     static_assert(!std::is_same_v<T, std::string_view>,
                                    ^
/root/RDKit_git/Code/RDGeneral/Dict.h:275:38: error: expected string-literal before ‘std’
     static_assert(!std::is_same_v<T, std::string_view>,
                                      ^~~
/root/RDKit_git/Code/RDGeneral/Dict.h:275:37: error: expected ‘)’ before ‘std’
     static_assert(!std::is_same_v<T, std::string_view>,
                  ~                  ^~~~
                                     )

You probably need to add  -std=c++14 or -std=c++17 to the compilation.  It could be the docs are wrong.

You probably need to add -std=c++14 or -std=c++17 to the compilation. It could be the docs are wrong.

Tried， but it did not help


Make git comment prompt configurable

Pull the git comment prompt from settings similar to other prompts.

Hi @tcpaddock
Thanks for requesting the feature. I've added the SCM prompt to the editable prompts

The you can simply update the prompt here:

available in version 1.5.8


The mixed type can be replaced with array

in this method I think you can change the mix type to an array
https://github.com/yiisoft/form-model/blob/daa51d3791c662acbe52e71258a068e801a2fbfc/src/FormHydrator.php#L41-L51

In most cases data for form model popalting:

used once and not need after populating;
come from the user, and can be any type (for example, ServerRequestInterface::getParsedBody() returns array|object|null).

Goal of this method — for incorrect data returns false, not throw exception or error.


Setup Guide with visuals

The bot works for me I have this screen:

I assume, it should now be active in that 1 channel.
But, when a Pokemon spawns there, the bot does nothing (same screen). Not even p!catch Uv2624239weg27e. Log is also same.
So there is maybe 1 part missing in "How to make the bot work".
This all sadly cannot help now anymore if it cannot catch anyway because the changed Pokecord.
I'm still curious about that. And wanna help you that next time you can give 1-2 sentence more in description. Because you put so much work into it that nobody could use it, everyone open new issues, just because there is not 1 picture of for example your cmd window and how it looks if all works + if you catch something with it how it looks.
Very nice anyway :)

Thank you for the descriptive feedback, I appreciate it. The documentation, aka., a help command for all the other commands is in the roadmap. But I see your point about visuals for basic setup. I'll add it to my ToDo list.
Now, as for your problem, the solution is simple. Your autocatcher is Off by default. To enable it, you need to use a command P^autocatcher on.
If you don't want to turn it on everytime you restart the bot, simply change the line 41:
self.auto_catcher = False

to
self.auto_catcher = True

Ty, I could have read the code. But I read it with editor and there was no lines, just 1 big block. Good info, because I didn't know what to type in discord to change settings.

oh btw, if you are using an editor, I suggest Visual Studio Code. It is a must have for any coder.
It has many built-in plugins ranging from syntax highlighting to built-in compilers.

I have Visual Studio, but also I have only a slow Laptop and don't want to open Visual Studio, if it works quick in editor too :D

I don't know why, but the commands get no reaction.
I change in pokeball catcher in line 41 to true. It doesnt catch or write anything.

What I do is close + run setup.bat as admin.
The commands in discord doesn't work. Now I copied everything into System32 and started it as Admin, it still doesn't work.
And although auto_catcher is "true" (I changed the file and did restart etc) it does nothing.
In console it shows me all till whitelist and there is no change after everything (spawn, command).
How I use it: With my account spamming chat with Pokecord. Pokemon spawns. I wait but my Account dont write from the bot. Should I log out? Dumb questions maybe, but I would like to make it work.

Now I copied everything into System32 and started it as Admin, it still doesn't work.

Not necessary.

I wait but my Account dont write from the bot

I didn't get you. You need to use the commands from the same account as your selfbot.
The multi-user mode is available in Premium version.

I do, same account. But bot does nothing. Idk why :(

And I copied into System32 because it gave me error, that he can't find launcher, ect when I start as admin. If I start normal it not neccassary

Do not run it as Admin. You don't have to. Run it from the same folder
where all the files are there.
Try sending P^echo test in the chat and see if the bot replies test.
On Tue, May 22, 2018 at 11:35 PM, Stranger94<EMAIL_ADDRESS>wrote:

And I copied into System32 because it gave me error, that he can't find
launcher, ect when I start as admin. If I start normal it not neccassary
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Hyperclaw79/PokeBall-SelfBot/issues/25#issuecomment-391086574,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab8O6-qh24d42SwPYi-LQ6CZR1vbTTPyks5t1FN9gaJpZM4UI61l
.

Looks like the commands itself are not running. That is why, launch it normally from the directory where the original file is, and in normal mode. No need of admin.
The fact that even echo command is not working means the bot isn't able to communicate with Discord after it logs in.
Add python as exception to your firewall.

Python always opens in C:\Windows\System32
uff
I give up.
I disabled firewall whole day today.
And I started it whole day except 1 time without admin. If I don't know what to do I test all 100 ways.
You want to know what for me is the hardest part about programming or using cmd?  Really I wasted 1 day on this and it still doent work because now I have everywhere .py and discord files. Again jump 4 hours back reinstall phyton the 5th time? Or should I reinstall the bot files 5th time after deleting all files?
Ty for the help but I will try it maybe next week, since it looks like you cant catch pokemon now anyways.

I think that's the fatal problem, which also appears for other self-bots.

Hmm, looks like that PR was a bad move.
I can fix this pip issue, not a problem.
As for the folder location, just download the zip file and extract it to Desktop, go into the folder, run setup.bat and then run run.bat.
Try adding this line
print(message.content)

at line 116 to see if the bot is atleast reading the messages.
async def on_message(self, message):
    def pokecord_reply(msg):
        return msg.author.id ==<PHONE_NUMBER>08745985
    print(message.content)
    if not self.ready:
        return

Make sure you follow proper indentation while adding that line.

Okay I will try that as soon as possible, thank you for the help :) I will stay here I can learn something and you can fix stuff.

maybe a bad question :-P where i can find line 41 for autostart. i looked at all files. there is no line 41 or autostart :/

Thought i deleted my post, because i found the file a few seconds lauter :-p
Ty for answer and helping

Closing this as it feels excessive with all the provided details in the Readme and as preparation for a future major change.


Ask: Best Frontal Face Detection

Is there a way to identify which picture has the best frontal face? Eg. If there is an array of pictures of a same person, looking up, down, left, right, slight left, slight right, up right, down right, up left, down left and front, it should identify front face as the "best or close enough" frontal picture?
Not sure how to calculate this but It can be achieved with Face Landmark. For face looking left vs face looking right vs front face, a function that can calculate distance of the outer edge (jaw outline) of the eyes to the edge of the face and see if both (left side and right side) measurements are close enough.
Not sure how, to identify up looking face vs down looking face vs front face.
From bbt_face_similarity demo, if you see Penny's 5 pictures, it should identify no. 5 as best frontal picture.
EDIT: Found this interesting link https://github.com/1adrianb/face-alignment

Now I need to find if face is turned to left or right and straight looking faces .
Can you support?

Now I need to find if face is turned to left or right and straight looking faces .
Can you support?


Enable io_uring builds with newer liburing

Motivation:
Newer copies of liburing have changed header imports, making some
of our implicit includes fail, and have also changed the types
of some methods in a way that would only produce warnings in C but
which produces errors in Swift. Additionally, liburing broke when
we did the module split, but we didn't notice.
Modifications:

Import NIOCore for the Uring Swift code.
Import poll.h in CNIOLinux
Support arguments that are either pointers or UInt64s.

Results:
liburing code compiles again

cc @hassila

Thanks @Lukasa - been busy times unfortunately, but hope we can pick up discussions about how to move io_uring forward to the next level (including memory ownership discussions and in light of support for Concurrency in NIO) if you / the team have bandwidth early next year perhaps?

@hassila For sure, we're happy to sync up whenever. I mostly wanted to let you review this given that you wrote the original code! :grin:

@hassila For sure, we're happy to sync up whenever. I mostly wanted to let you review this given that you wrote the original code! 😁

Thanks, LGTM!


[rtloader/aggregator] Parse optional flush_first_value boolean with |b

What does this PR do?
Changes the aggregator.submit_metric method's argument parsing from OsisdOs|i to OsisdOs|b, converting into an unsigned char instead of an int (see https://docs.python.org/3/c-api/arg.html).
Motivation
#6663 added a new optional boolean parameter, flush_first_value, to the aggregator.submit_metric method. However, either the Python argument parsing or the argument sizes are different on arm64 than on amd64.
The core problem comes from the optional flush_first_value boolean being parsed as a 4-byte integer. On amd64, this isn't a problem, but it seems like the way the args are parsed on arm64 made it so that only the first 8 bits of the metric type integer (out of 32) were taken into account (the remaining 24 bits are seemingly all set to 0). This became obvious when I tried passing arbitrary values for metric types:

1000000000<PHONE_NUMBER>0110101100101000000000) became 989855744<PHONE_NUMBER>0000000000000000000000)
989855743<PHONE_NUMBER>1111111111111111111111) became 973078528<PHONE_NUMBER>0000000000000000000000)
16777216 (= 2^24) remained the same, while 16777215 became 0.

This resulted in all current metric types (which are mapped from 0 to 6) being sent as metric type 0 (ie. gauge) since Agent 6/7.24.0.
Describe your test plan
Tested with Python 2 and Python 3, on an Ubuntu 20.04 arm64 host and an Ubuntu 20.04 amd64 host. Both the metric type and the flush_first_value seem to be passed correctly with the new parsing format.

Also, I guess a test running the tests on arm64 would've caught this? (or are we missing a test?)

I ran the test suites on an arm64 Ubuntu 20.04 host, on the master branch, and neither inv rtloader.test nor inv test had any failure, thus I guess this is a blind spot.

Also, I guess a test running the tests on arm64 would've caught this? (or are we missing a test?)

I ran the test suites on an arm64 Ubuntu 20.04 host, on the master branch, and neither inv rtloader.test nor inv test had any failure, thus I guess this is a blind spot.

I'm going to merge this PR as-is and backport it for 7.25.1. We can prepare a follow-up PR for 7.26.0 to test whether defining and parsing flush_first_value as int works.

I'm going to merge this PR as-is and backport it for 7.25.1. We can prepare a follow-up PR for 7.26.0 to test whether defining and parsing flush_first_value as int works.


ENYO-5070 - Enact Picker: Text Unexpectedly Continues to Marquee

Issue Resolved / Feature Added
Enact Picker would still marquee even when you 5way off picker if the picker was previously hovered.
Resolution
Added some TV specific code to check for when the pointer hides.
Links
ENYO-5070

@ryanjduffy Updated! Should be good now.


Add cachier

https://github.com/fgrehm/vagrant-cachier

@viglesiasce, is there a reason this was against master instead of brown-bag branch? Just asking because I was planning on doing all the cleanup in that branch then submitting to master once everything was done.

Nope i biffed it.


[WIP] Add resize support to box when changing font-face on display/edit mode

Close #1008

Looks like Travis is failing, re-running the failing job to see if it gets fixed.
From testing: works very well!

@miina See Slack discussion and #1356 regarding Travis CI.

@obetomuniz Heya 👋  Looks like merging #1273 caused some merge conflicts here 😬  Let me know if you need some help with those or otherwise want to sync regarding that change.

Sure! Thank you for advanced heads up @swissspidy. I already pushed the merge.

@obetomuniz Could you confirm is this PR is addressing https://github.com/google/web-stories-wp/issues/923 as well (loading fonts based on the content, including different font weights, etc.)?

@miina Partially. We have decided to not cover content stuff on this PR since there is some related stuff on Morten's #1323 PR that we should consider before support content here. So only font-style/font-weight is being addressed. Do you think that we should consider an issue desc change on #923? Or that desc will be useful as requirement for any follow-up work?

Merging the recent changes from #1323 required several conflicts adjustments, so I am moving this PR back to WIP once I still want to ensure that everything is working as before the merge.

Partially. We have decided to not cover content stuff on this PR since there is some related stuff on Morten's #1323 PR that we should consider before support content here. So only font-style/font-weight is being addressed. Do you think that we should consider an issue desc change on #923? Or that desc will be useful as requirement for any follow-up work?

It just seemed that with #1323 getting merged this PR might need to address #923 anyway for working as expected. Dima mentioned that this PR will address the fonts properly loading in the front-end as well, that's where the question came from -- to confirm if that's so.

@miina 100% agreed, now that we have #1323, I can tackle content here too, no only font-style and font-weight. Thanks for bringing this here again. @dvoytenko do you have some additional insight related?

@miina 100% agreed, now that we have #1323 merged on this PR, I can tackle content here too, no only font-style and font-weight. Thanks for bringing this here again. @dvoytenko do you have some additional insight related?

Sure. @barklund has even more insight. But element{fontStyle, fontWeight, etc} are all gone. Instead, you will need to extract all styles from the content (there's a util for that, start with the getHTMLInfo unless Morten gives you a better advice). From that point it should be more or less all the same - you will have an array of fontStyle and fontWeight tuples.

@dvoytenko What about this PR? Is there some plan to get it merged or even re-reviewed?

@barklund could you approve or dismiss your review when your requested changes have been addressed? Would be great to finally get this merged.

@googlebot I consent.


[IMPROVEMENT] Docs: Clarify API and python client support

Is your improvement request related to a feature? Please describe
The docs page for the Longhorn Python client https://longhorn.io/docs/1.3.0/references/longhorn-client-python/.
Describe the solution you'd like
The page should clearly state that neither the Longhorn API or the client are officially supported and may change without warning or backwards compatibility considerations at any time.

ref: https://github.com/longhorn/longhorn/issues/4356


Test PR

Test for CLA stuff

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


Improve PlatformException.stacktrace documentation

Use case
I want to know in which cases and on what platforms the PlatformException.stacktrace is set without having to look up the implementation for each platform in the engine.

Proposal
Improve documentation for PlatformException.stacktrace.

@ueman, how to pass the exception stack trace to dart channel using result.error method (PlatformException) on Android? And on iOS?

@rafaelsetragni currently the stacktrace is only set, if there's an exception during serialization of data for method channels. For your use case you should probably create a new issue.


Update form links

Change googleform links to microsoft form links

 Recreate current feedback form and UR recruitment form in MS

 Recreate current feedback form and UR recruitment form in MS


Enabling Fast Refresh through craco?

create-react-app most recently added the experimental functionality of Fast Refresh through the .env variable FAST_REFRESH=true (which didn't work)
What modifications are required in the craco config to enable this?

Hi @AK-101111
You can set the env variable as specified in CRA docs, it should work. You could also submit a PR to add support for fast refresh to CRACO.
Similar features are supported by this code: https://github.com/gsoft-inc/craco/blob/master/packages/craco/lib/features/dev-server/set-environment-variables.js

Thank u for your response @patricklafrance
Regardless of setting the environment variable I could not get it Fast Refresh to play.
On the other hand I imported @pmmmwh/react-refresh-webpack-plugin
and simply added it to the webpack plugins through CRACO and ... it worked!

That's odd, does fast refresh work with a fresh CRA app?

Sorry for the late reply.
Based on the docs, they support it.
https://github.com/facebook/create-react-app/blob/master/docusaurus/docs/advanced-configuration.md

@AK-101111 Can you share your craco settings? I can't get the Fast Refresh to work

Apparently not in the released create-react-app yet: https://github.com/facebook/create-react-app/issues/8678#issuecomment-636839360

craco doesn't support yet cra@next (v4) but you can have fast refresh using a plugin


[RTE Phase 1] Rich text editor updates in Metafield

Epic: #374898
Renders react components in hydrogen when passed to the Metafield component. This will require recursively traversing the AST, and performantly rendering React components according to the AST.
How does the serializer support current and new plugins?
From the first take, we would have to support updating the serializer for every new plugin.
Link to demo: https://screenshot.click/01-13-f2vi9-ho4dn.mp4

hey @TirmanSidhu @joe-szczepaniak - Can you please provide more context on this? Are there any specific requirements you need from the  Hydrogen Metafield component?


Uniques with multiple fields

Motivation
https://dev.untill.com/projects/#!663686
need to have an unique on a fields combination From and Till varchar fields of wdoc.air.UPPayout
Problems:

old uniques engine is not suitable because From and Till are both varchar fields. Only one varchar field in one unique is allowed
sql: UNIQUE (fld1, fld2): https://github.com/voedger/voedger/blob/0f6794ba83c822a7105b293b00e20abb74150ad8/pkg/parser/sql_example_app/pmain/package.sql#L78
new uniques are exist on declaration level only. Would be good to implement new uniques using existsing old implementation
view value size? Is it actual to make it more compact?

Context

#151

null==0==""
insert null, then insert 0 -> error
no case when the unique field value is set for the first time on update
discuss with Yougin: what to do if DisplayName is unkonown on insert
unique fileds must be required

VIEW Uniques (
	QName qname NOT NULL, -- QName of the doc the values are from.
	ValuesHash int64 NOT NULL,
	Values bytes(32768) NOT NULL,
	ID ref,
	PRIMARY KEY ((QName, ValuesHash) Values)
) AS RESULT OF ApplyUniques;

byte(0) is added at the beginning of each varchar or bytes field value

need to handle empty strings and bytes


Merging our Repos

Hey @Nilesh220
I would like to merge our project repos. I would add you to the contributor's list and tag you.
Also, feel free to use my project in your repo.
Let me know what you think

OK DONE

Thanks again


Clicking download under an ebook

Where does the download go? If to my pc then under what name. If not to my pc where to and what can I do with it?

I assume you mean from an OPDS feed? The downloaded publication goes into your local bookshelf. Using the menu, you can export the downloaded EPUB from Thorium Reader.


Short solution needed: "Tuple usage example" (clickhouse)

Please help us write most modern and shortest code solution for this issue:
Tuple usage example (technology: clickhouse)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to create Tuple column


Fixed broken tabs on docs site

The history.isActive function was checking for route paths without the leading "/". Fixing that pretty much clears up all currently known broken things with the docs site

Addresses issues mentioned in #1884


Pull request for python-dbg

For travis-ci/travis-ci#4240.
Ran tests and found no setuid bits.
See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/72046076

Sorry, but this test will have to be re-run. Will open a new one later.


Webpack - InfiniteScroll is not a constructor

When installing with webpack, I get the following console error:
Uncaught TypeError: infinite_scroll__WEBPACK_IMPORTED_MODULE_0__.InfiniteScroll is not a constructor
    at eval (index.js:6)
    at Module../index.js (bundle.js:97)
    at __webpack_require__ (bundle.js:20)
    at bundle.js:84
    at bundle.js:87

Code listing....
package.json
{
  "main": "index.js",
  "scripts": {
    "build": "webpack --config webpack.config.js --mode=development"
  },
  "dependencies": {
    "infinite-scroll": "^3.0.6"
  },
  "devDependencies": {
    "webpack": "^4.41.0",
    "webpack-cli": "^3.3.9"
  }
}

webpack.config.js
path = require('path');

module.exports = {
  entry: './index.js',
  resolve: {
    extensions: ['*', '.js']
  },
  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: 'bundle.js'
  }
};

index.js
import { InfiniteScroll } from 'infinite-scroll';

var infScroll = new InfiniteScroll('#container', {
  // options...
});

index.html
<!doctype html5>

Closing due to PEBKAC

Where are you, @mafrosis ?
What did you see?
https://xkcd.com/979/


Bug: White-Screen on electron app at page load

Expected Behavior
Should run application in the electron app window
Current Behavior

Environment

Node version : v20.5.1
OS: MacOS, Windows, Linux (Ubuntu,Arch)

fixed with #34


Updated pdf.js to 1.0.907

Ok (tested).

Can you please rebase on top of stable branch?

ok

Rebase done.


fedpkg: remove unneeded patch

Motivation for this change
This patch is no longer used
Things done

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

[X] NixOS
[X] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build python3.pkgs.fedpkg python2.pkgs.fedpkg

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: python3.pkgs.fedpkg, python2.pkgs.fedpkg
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: python2.pkgs.fedpkg
The following builds were skipped because they don't evaluate on x86_64-linux: python3.pkgs.fedpkg
Partial log (click to expand)
/build/fedpkg-1.29
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29
strip is /nix/store/n4hb93w6j076xcjw5pm09rdmc09s075b-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29/lib  /nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29/bin
patching script interpreter paths in /nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29
checking for references to /build in /nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29...
wrapping `/nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29/bin/fedpkg'...
wrapping `/nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29/bin/fedpkg-stage'...
/nix/store/cyphpr9xrrzij259jb12s8as6bsi0h5r-python2.7-fedpkg-1.29

Success on aarch64-linux (full log)
Attempted: python2.pkgs.fedpkg
The following builds were skipped because they don't evaluate on aarch64-linux: python3.pkgs.fedpkg
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29
strip is /nix/store/qjrnv0qw44bw1hc23zhfh26xd1c25dfs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29/lib  /nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29/bin
patching script interpreter paths in /nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29
checking for references to /build in /nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29...
wrapping `/nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29/bin/fedpkg'...
wrapping `/nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29/bin/fedpkg-stage'...
warning: SQLite database '/nix/var/nix/db/db.sqlite' is busy
/nix/store/sy1gpmjq3apymrvraz42a29rpy9n46hm-python2.7-fedpkg-1.29

@marsam Can you remove name = "${pname}-${version}";?
We don't need that in python packages anymore.

The patch might still be needed:
$ exa -T result/
result
├── bin
│  ├── fedpkg
│  └── fedpkg-stage
├── lib
│  └── python2.7
│     └── site-packages
│        ├── etc
│        │  ├── bash_completion.d
│        │  │  └── fedpkg.bash
│        │  └── rpkg
│        │     ├── fedpkg-stage.conf
│        │     └── fedpkg.conf
│        ├── fedpkg
│        │  ├── __init__.py
│        │  ├── __init__.pyc
│        │  ├── __main__.py
│        │  ├── __main__.pyc
│        │  ├── cli.py
│        │  ├── cli.pyc
│        │  ├── lookaside.py
│        │  └── lookaside.pyc
│        ├── fedpkg-1.29.dist-info
│        │  ├── COPYING
│        │  ├── INSTALLER
│        │  ├── METADATA
│        │  ├── RECORD
│        │  ├── top_level.txt
│        │  └── WHEEL
│        └── usr
│           └── share
│              └── zsh
│                 └── site-functions
│                    └── _fedpkg
└── nix-support
   └── propagated-build-inputs

Perhaps an update and a slightly different patch would be preferable https://pagure.io/fedpkg/blob/master/f/setup.py#_51

@marsam Would you mind doing other cleanups for this?

sure, do you have anything in mind?

sure, do you have anything in mind?

Yep, just wanted to ask before I started reviewing again.

Also, all that cleanup I think an update would be cool.

I've updated fedpkg with buildPythonApplication, and checked the binaries are working

:+1:

Also, I did try to update it, but that it's going to take a bit of time: 3c1823c, because they don't quite follow the standard python packaging. I think that can go in another PR.

I agree that a separate pr for that would be appropriate.


Development

For the moment, the ci pipeline will be ignored, while I don't fix the CI/CD pipeline.


How to run jshint.js with node.exe and get output?

I'm the developer of CSE HTML Validator for Windows. CSE HTML Validator currently uses JSLint and runs JSLint with something like
node.exe wrapper.js test.js
The wrapper.js uses jslint.js (in the same folder as wrapper.js) to generate the results and output them to the console. The setup program for CSE HTML Validator only has to install node.exe, wrapper.js, and jslint.js on a user's system to get it to work.
I want to be able to support jshint in a similar manner.
I see there is a large “jshint.js” file in the dist folder here:
https://github.com/jshint/jshint/tree/master/dist
I’m hoping I can simply distribute just that file (jshint.js) with CSE HTML Validator (similar to JSLint), and call jshint.js with node.exe and the name of the file to check. I am already installing node.exe on the user’s system to support JSLint.
So basically what I would like to know is what files I need (the minimum number) to install on the user’s system (when they install my application) and how to call JSHint (I am already installing node.exe for JSLint). I hope to find a way to only install jshint.js and maybe a support file (like wrapper.js which I use for JSLint), and be able to execute something like “node.exe jshint.js test.js” and get the results in a similar way to JSLint.
Hopefully I won’t have to install all the JSHint files in the “src” folder or any modules folder or npm or a bunch of other files.
Perhaps I only need an appropriate wrapper.js file for jshint? However, I'm not totally sure and would like some help from someone who knows a lot about jshint.
Can someone help me get this working this way? I would really appreciate any help. I want to make jshint the default JavaScript linter instead of jslint because I think it's more practical and better overall.

jshint was forked from jslint and I believe it follows a similiar API. You should be able to do what you want, I used to use jshint in this way for the jslint for visual studio plugin, but I haven't tried the api in a while.

That's what I was hoping for but it's not working.
For example, this is what I get when I run "node.exe wrapper.js test.js":
T:\JSHint>node.exe wrapper.js test.js
evalmachine.:2194
var arrayProto = Array.prototype,
^
TypeError: Cannot read property 'prototype' of undefined
at runInContext (evalmachine.:2194:27)
at Object. (evalmachine.:13258:11)
at Object. (evalmachine.:13289:3)
at Object.require (evalmachine.:13291:4)
at s (evalmachine.:6:262)
at evalmachine.:6:313
at Object.require.jshint../lex.js (evalmachine.:17432:16)
at s (evalmachine.:6:262)
at evalmachine.:23042:10
at evalmachine.:23044:2
If someone who knows more about this can help, I'd much appreciate it. If you extract the files here into a 'JSHint' folder, then you will probably be able to reproduce this if node.exe is in your path:
https://www.htmlvalidator.com/private/JSHint.zip
Perhaps this is a bug in jshint.js?

See
https://github.com/lodash/lodash/issues/223
Somone has the same issue,  seems caused by lodash ran using runincontext (jshint bundles lodash).
I would try 1. Updating node 2. Comtinue searchimg google (with runincontext and the error you are getting connected with lodash or browserify 3. Ask on that issue i linked

Thanks. I'm using the latest version of node (v0.12.4). I'll have to do the research you suggest when I have time... maybe by then the issue will be resolved. :)


fix ds inference with user prompt for text-generation

What does this PR do?
as title

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

@ZhaiFeiyue I pushed a commit to handle the case where args are already given in the right format after gaudi_spawn.py: '"..."'. It's necessary because there are a few places in READMEs where the example command line contains such args (see here for instance).

@ZhaiFeiyue I pushed a commit to handle the case where args are already given in the right format after gaudi_spawn.py: '"..."'. It's necessary because there are a few places in READMEs where the example command line contains such args (see here for instance).

it always is '"..."' and won't be "'...'" right?

"

Yep


Persist etcd by default

Coverage increased (+0.07%) to 77.65% when pulling c901fd74b13fb7c9c4d6f52d8efdbbd8aa4e98a4 on lukasmacko:master into 3cefb3f48336564233979322f6dc55c3ce7dd62c on contiv:master.


Settings breaking conversions

I have been having issues with videos converting and after hours I have finally figured out the issue is with the settings
video-bitrate =
video-max-width =
I set
video-bitrate =3000
video-max-width =1280
and when I do and run manual.py -i video I get the error
Starting conversion.
Error converting file, FFMPEG error.
Traceback (most recent call last):
File "/opt/Automator/mkvtomp4.py", line 593, in convert
for timecode in conv:
File "/opt/Automator/converter/init.py", line 243, in convert
timeout=timeout, preopts=preopts, postopts=postopts):
File "/opt/Automator/converter/ffmpeg.py", line 553, in convert
total_output, pid=p.pid)
FFMpegConvertError: <FFMpegConvertError error="Exited with code 1", pid=6215, cmd="/root/bin/ffmpeg -fix_sub_duration -i /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E03 - The Dog Bluray-1080p.mkv -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc UTF-8 -metadata:s:s:0 language=eng -f mp4 -threads auto -y /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E03 - The Dog Bluray-1080p.mp4">
But then I removed the video-bitrate and its been converting just fine.

Processing Fear the Walking Dead Season 01 Episode 06 - The Good Man
Reading video stream.
Video codec detected: h264.
Pix Fmt: yuv420p.
Reading audio streams.
Audio detected for stream #1: ac3 [eng].
Creating audio stream 0 from source audio stream 1 [iOS-audio].
Creating audio stream 1 from source stream 1.
Reading subtitle streams.
Subtitle detected for stream #2: srt [eng].
Creating subtitle stream 0 from source stream 2.
No valid subtitle language specified, cannot download subtitles.
{
    "preopts": [
        "-fix_sub_duration"
    ],
    "subtitle": {
        "0": {
            "map": 2,
            "codec": "mov_text",
            "language": "eng",
            "encoding": "UTF-8"
        }
    },
    "format": "mp4",
    "postopts": [
        "-threads",
        "auto"
    ],
    "video": {
        "map": 0,
        "codec": "h264",
        "bitrate": 3000,
        "width": 1280,
        "level": 4.1
    },
    "audio": {
        "0": {
            "channels": 2,
            "map": 1,
            "codec": "aac",
            "bitrate": 256,
            "language": "eng"
        },
        "1": {
            "channels": 2,
            "map": 1,
            "codec": "aac",
            "bitrate": 512,
            "language": "eng"
        }
    }
}
Starting conversion.
Error converting file, FFMPEG error.
Traceback (most recent call last):
  File "/opt/Automator/mkvtomp4.py", line 593, in convert
    for timecode in conv:
  File "/opt/Automator/converter/__init__.py", line 243, in convert
    timeout=timeout, preopts=preopts, postopts=postopts):
  File "/opt/Automator/converter/ffmpeg.py", line 553, in convert
    total_output, pid=p.pid)
FFMpegConvertError: <FFMpegConvertError error="Exited with code 1", pid=5435, cmd="/root/bin/ffmpeg -fix_sub_duration -i /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E06 - The Good Man WEBDL-1080p.mkv -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf scale=1280:trunc(ow/a/2)*2 -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc UTF-8 -metadata:s:s:0 language=eng -f mp4 -threads auto -y /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E06 - The Good Man WEBDL-1080p.mp4">

This is with both settings removed
Processing Fear the Walking Dead Season 01 Episode 03 - The Dog Reading video stream. Video codec detected: h264. Pix Fmt: yuv420p. Reading audio streams. Audio detected for stream #1: dca [eng]. Creating audio stream 0 from source audio stream 1 [iOS-audio]. Creating audio stream 1 from source stream 1. Reading subtitle streams. Subtitle detected for stream #2: srt [eng]. Creating subtitle stream 0 from source stream 2. No valid subtitle language specified, cannot download subtitles. {     "preopts": [         "-fix_sub_duration"     ],      "subtitle": {         "0": {             "map": 2,              "codec": "mov_text",              "language": "eng",              "encoding": "UTF-8"         }     },      "format": "mp4",      "postopts": [         "-threads",          "auto"     ],      "video": {         "map": 0,          "codec": "copy",          "bitrate": 7715.657749999999,          "level": 4.1     },      "audio": {         "0": {             "channels": 2,              "map": 1,              "codec": "aac",              "bitrate": 256,              "language": "eng"         },          "1": {             "channels": 2,              "map": 1,              "codec": "aac",              "bitrate": 512,              "language": "eng"         }     } } Starting conversion. /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E03 - The Dog Bluray-1080p.mp4 created. Tagging file: /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E03 - The Dog Bluray-1080p.mp4. Trying to write tags. Tags written successfully. Relocating MOOV atom to start of file.

If you run the command from the failure manually, can you post the full FFMPEG output?
/root/bin/ffmpeg -fix_sub_duration -i /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E06 - The Good Man WEBDL-1080p.mkv -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf scale=1280:trunc(ow/a/2)*2 -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc UTF-8 -metadata:s:s:0 language=eng -f mp4 -threads auto -y /home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E06 - The Good Man WEBDL-1080p.mp4

I had to redownload a mkv and change its location but I can this command
/root/bin/ffmpeg -fix_sub_duration -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv"  -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf scale=1280:trunc(ow/a/2)*2 -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc UTF-8 -metadata:s:s:0 language=eng -f mp4 -threads auto -y "/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4"
And I got this output
-bash: syntax error near unexpected token ('`

Looks like you have an invalid character you accidentally copy/pasted into your command prompt somewhere

I've tried it 2 times over I even moved the file to your location with the same filename so that I can copy and paste and still getting that error

/root/bin/ffmpeg -fix_sub_duration -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv" -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf "scale=1280:trunc(ow/a/2)*2" -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc UTF-8 -metadata:s:s:0 language=eng -f mp4 -threads auto -y "/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4"

root@server1:~# /root/bin/ffmpeg -fix_sub_duration -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv" -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf "scale=1280:trunc(ow/a/2)*2" -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc UTF-8 -metadata:s:s:0 language=eng -f mp4 -threads auto -y "/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4"
ffmpeg version N-79087-gefa98cd Copyright (c) 2000-2016 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
  configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  libavutil      55. 19.100 / 55. 19.100
  libavcodec     57. 28.103 / 57. 28.103
  libavformat    57. 28.102 / 57. 28.102
  libavdevice    57.  0.101 / 57.  0.101
  libavfilter     6. 39.102 /  6. 39.102
  libswscale      4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc    54.  0.100 / 54.  0.100
Input #0, matroska,webm, from '/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv':
  Metadata:
    encoder         : libebml v1.3.0 + libmatroska v1.4.1
    creation_time   : 2015-11-14 08:53:18
  Duration: 00:45:08.72, start: 0.000000, bitrate: 10376 kb/s
    Chapter #0:0: start 0.000000, end 472.680000
    Metadata:
      title           : 00:00:00.000
    Chapter #0:1: start 472.680000, end 993.158000
    Metadata:
      title           : 00:07:52.680
    Chapter #0:2: start 993.158000, end 1589.879000
    Metadata:
      title           : 00:16:33.158
    Chapter #0:3: start 1589.879000, end 2144.142000
    Metadata:
      title           : 00:26:29.879
    Chapter #0:4: start 2144.142000, end 2674.463000
    Metadata:
      title           : 00:35:44.142
    Chapter #0:5: start 2674.463000, end 2708.715000
    Metadata:
      title           : 00:44:34.463
    Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
    Metadata:
      BPS             : 8865254
      BPS-eng         : 8865254
      DURATION        : 00:45:08.706000000
      DURATION-eng    : 00:45:08.706000000
      NUMBER_OF_FRAMES: 64944
      NUMBER_OF_FRAMES-eng: 64944
      NUMBER_OF_BYTES :<PHONE_NUMBER>
      NUMBER_OF_BYTES-eng:<PHONE_NUMBER>
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:1(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), fltp, 1536 kb/s (default)
    Metadata:
      BPS             : 1509000
      BPS-eng         : 1509000
      DURATION        : 00:45:08.715000000
      DURATION-eng    : 00:45:08.715000000
      NUMBER_OF_FRAMES: 253942
      NUMBER_OF_FRAMES-eng: 253942
      NUMBER_OF_BYTES : 510931392
      NUMBER_OF_BYTES-eng: 510931392
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:2(eng): Subtitle: subrip (default) (forced)
    Metadata:
      title           : Forced
      BPS             : 61
      BPS-eng         : 61
      DURATION        : 00:01:19.496000000
      DURATION-eng    : 00:01:19.496000000
      NUMBER_OF_FRAMES: 24
      NUMBER_OF_FRAMES-eng: 24
      NUMBER_OF_BYTES : 608
      NUMBER_OF_BYTES-eng: 608
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Codec AVOption sub_charenc (set input text subtitles character encoding) specified for output file #0 (/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4) is not an encoding option.

Hmm looks like its struggling with the sub_charenc option for some reason
Try this
/root/bin/ffmpeg -fix_sub_duration -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv" -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf "scale=1280:trunc(ow/a/2)*2" -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc "UTF-8" -metadata:s:s:0 language=eng -f mp4 -threads auto -y "/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4"

/root/bin/ffmpeg -fix_sub_duration -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv" -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf "scale=1280:trunc(ow/a/2)*2" -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -sub_charenc "UTF-8" -metadata:s:s:0 language=eng -f mp4 -threads auto -y "/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4"
ffmpeg version N-79087-gefa98cd Copyright (c) 2000-2016 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
  configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  libavutil      55. 19.100 / 55. 19.100
  libavcodec     57. 28.103 / 57. 28.103
  libavformat    57. 28.102 / 57. 28.102
  libavdevice    57.  0.101 / 57.  0.101
  libavfilter     6. 39.102 /  6. 39.102
  libswscale      4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc    54.  0.100 / 54.  0.100
Input #0, matroska,webm, from '/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv':
  Metadata:
    encoder         : libebml v1.3.0 + libmatroska v1.4.1
    creation_time   : 2015-11-14 08:53:18
  Duration: 00:45:08.72, start: 0.000000, bitrate: 10376 kb/s
    Chapter #0:0: start 0.000000, end 472.680000
    Metadata:
      title           : 00:00:00.000
    Chapter #0:1: start 472.680000, end 993.158000
    Metadata:
      title           : 00:07:52.680
    Chapter #0:2: start 993.158000, end 1589.879000
    Metadata:
      title           : 00:16:33.158
    Chapter #0:3: start 1589.879000, end 2144.142000
    Metadata:
      title           : 00:26:29.879
    Chapter #0:4: start 2144.142000, end 2674.463000
    Metadata:
      title           : 00:35:44.142
    Chapter #0:5: start 2674.463000, end 2708.715000
    Metadata:
      title           : 00:44:34.463
    Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
    Metadata:
      BPS             : 8865254
      BPS-eng         : 8865254
      DURATION        : 00:45:08.706000000
      DURATION-eng    : 00:45:08.706000000
      NUMBER_OF_FRAMES: 64944
      NUMBER_OF_FRAMES-eng: 64944
      NUMBER_OF_BYTES :<PHONE_NUMBER>
      NUMBER_OF_BYTES-eng:<PHONE_NUMBER>
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:1(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), fltp, 1536 kb/s (default)
    Metadata:
      BPS             : 1509000
      BPS-eng         : 1509000
      DURATION        : 00:45:08.715000000
      DURATION-eng    : 00:45:08.715000000
      NUMBER_OF_FRAMES: 253942
      NUMBER_OF_FRAMES-eng: 253942
      NUMBER_OF_BYTES : 510931392
      NUMBER_OF_BYTES-eng: 510931392
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:2(eng): Subtitle: subrip (default) (forced)
    Metadata:
      title           : Forced
      BPS             : 61
      BPS-eng         : 61
      DURATION        : 00:01:19.496000000
      DURATION-eng    : 00:01:19.496000000
      NUMBER_OF_FRAMES: 24
      NUMBER_OF_FRAMES-eng: 24
      NUMBER_OF_BYTES : 608
      NUMBER_OF_BYTES-eng: 608
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Codec AVOption sub_charenc (set input text subtitles character encoding) specified for output file #0 (/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4) is not an encoding option.

Hm same thing, lets try just taking that component out, no idea why it would cause problems though
/root/bin/ffmpeg -fix_sub_duration -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv" -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf "scale=1280:trunc(ow/a/2)*2" -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -metadata:s:s:0 language=eng -f mp4 -threads auto -y "/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4"

The last one seemed to work
/root/bin/ffmpeg -fix_sub_duration -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv" -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf "scale=1280:trunc(ow/a/2)*2" -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -c:s:0 mov_text -map 0:2 -metadata:s:s:0 language=eng -f mp4 -threads auto -y "/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4"
ffmpeg version N-79087-gefa98cd Copyright (c) 2000-2016 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
  configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  libavutil      55. 19.100 / 55. 19.100
  libavcodec     57. 28.103 / 57. 28.103
  libavformat    57. 28.102 / 57. 28.102
  libavdevice    57.  0.101 / 57.  0.101
  libavfilter     6. 39.102 /  6. 39.102
  libswscale      4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc    54.  0.100 / 54.  0.100
Input #0, matroska,webm, from '/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv':
  Metadata:
    encoder         : libebml v1.3.0 + libmatroska v1.4.1
    creation_time   : 2015-11-14 08:53:18
  Duration: 00:45:08.72, start: 0.000000, bitrate: 10376 kb/s
    Chapter #0:0: start 0.000000, end 472.680000
    Metadata:
      title           : 00:00:00.000
    Chapter #0:1: start 472.680000, end 993.158000
    Metadata:
      title           : 00:07:52.680
    Chapter #0:2: start 993.158000, end 1589.879000
    Metadata:
      title           : 00:16:33.158
    Chapter #0:3: start 1589.879000, end 2144.142000
    Metadata:
      title           : 00:26:29.879
    Chapter #0:4: start 2144.142000, end 2674.463000
    Metadata:
      title           : 00:35:44.142
    Chapter #0:5: start 2674.463000, end 2708.715000
    Metadata:
      title           : 00:44:34.463
    Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
    Metadata:
      BPS             : 8865254
      BPS-eng         : 8865254
      DURATION        : 00:45:08.706000000
      DURATION-eng    : 00:45:08.706000000
      NUMBER_OF_FRAMES: 64944
      NUMBER_OF_FRAMES-eng: 64944
      NUMBER_OF_BYTES :<PHONE_NUMBER>
      NUMBER_OF_BYTES-eng:<PHONE_NUMBER>
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:1(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), fltp, 1536 kb/s (default)
    Metadata:
      BPS             : 1509000
      BPS-eng         : 1509000
      DURATION        : 00:45:08.715000000
      DURATION-eng    : 00:45:08.715000000
      NUMBER_OF_FRAMES: 253942
      NUMBER_OF_FRAMES-eng: 253942
      NUMBER_OF_BYTES : 510931392
      NUMBER_OF_BYTES-eng: 510931392
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:2(eng): Subtitle: subrip (default) (forced)
    Metadata:
      title           : Forced
      BPS             : 61
      BPS-eng         : 61
      DURATION        : 00:01:19.496000000
      DURATION-eng    : 00:01:19.496000000
      NUMBER_OF_FRAMES: 24
      NUMBER_OF_FRAMES-eng: 24
      NUMBER_OF_BYTES : 608
      NUMBER_OF_BYTES-eng: 608
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
[AVFilterGraph @ 0x2ab49c0] [Eval @ 0x7ffdb0e6ce00] Undefined constant or missing '(' in 'auto'
[AVFilterGraph @ 0x2ab49c0] Unable to parse option value "auto"
[AVFilterGraph @ 0x2ab3d00] [Eval @ 0x7ffdb0e6ce00] Undefined constant or missing '(' in 'auto'
[AVFilterGraph @ 0x2ab3d00] Unable to parse option value "auto"
[AVFilterGraph @ 0x2a8af00] [Eval @ 0x7ffdb0e6ce00] Undefined constant or missing '(' in 'auto'
[AVFilterGraph @ 0x2a8af00] Unable to parse option value "auto"
[libx264 @ 0x2ab2a20] using SAR=1/1
[libx264 @ 0x2ab2a20] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
[libx264 @ 0x2ab2a20] profile High, level 4.1
[libx264 @ 0x2ab2a20] 264 - core 148 - H.264/MPEG-4 AVC codec - Copyleft 2003-2016 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=23 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=3000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to '/home/Videos/TV/Fear the Walking Dead/Season 1/Fear the Walking Dead - S01E05 - Cobalt -1080p.mp4':
  Metadata:
    encoder         : Lavf57.28.102
    Chapter #0:0: start 0.000000, end 472.680000
    Metadata:
      title           : 00:00:00.000
    Chapter #0:1: start 472.680000, end 993.158000
    Metadata:
      title           : 00:07:52.680
    Chapter #0:2: start 993.158000, end 1589.879000
    Metadata:
      title           : 00:16:33.158
    Chapter #0:3: start 1589.879000, end 2144.142000
    Metadata:
      title           : 00:26:29.879
    Chapter #0:4: start 2144.142000, end 2674.463000
    Metadata:
      title           : 00:35:44.142
    Chapter #0:5: start 2674.463000, end 2708.715000
    Metadata:
      title           : 00:44:34.463
    Stream #0:0(eng): Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 3000 kb/s, 23.98 fps, 24k tbn, 23.98 tbc (default)
    Metadata:
      BPS             : 8865254
      BPS-eng         : 8865254
      DURATION        : 00:45:08.706000000
      DURATION-eng    : 00:45:08.706000000
      NUMBER_OF_FRAMES: 64944
      NUMBER_OF_FRAMES-eng: 64944
      NUMBER_OF_BYTES :<PHONE_NUMBER>
      NUMBER_OF_BYTES-eng:<PHONE_NUMBER>
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc57.28.103 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/3000000 buffer size: 0 vbv_delay: -1
    Stream #0:1(eng): Audio: aac (LC) ([64][0][0][0] / 0x0040), 48000 Hz, stereo, fltp, 256 kb/s (default)
    Metadata:
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      BPS             : 1509000
      BPS-eng         : 1509000
      DURATION        : 00:45:08.715000000
      DURATION-eng    : 00:45:08.715000000
      NUMBER_OF_FRAMES: 253942
      NUMBER_OF_FRAMES-eng: 253942
      NUMBER_OF_BYTES : 510931392
      NUMBER_OF_BYTES-eng: 510931392
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc57.28.103 aac
    Stream #0:2(eng): Audio: aac (LC) ([64][0][0][0] / 0x0040), 48000 Hz, stereo, fltp, 512 kb/s (default)
    Metadata:
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      BPS             : 1509000
      BPS-eng         : 1509000
      DURATION        : 00:45:08.715000000
      DURATION-eng    : 00:45:08.715000000
      NUMBER_OF_FRAMES: 253942
      NUMBER_OF_FRAMES-eng: 253942
      NUMBER_OF_BYTES : 510931392
      NUMBER_OF_BYTES-eng: 510931392
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc57.28.103 aac
    Stream #0:3(eng): Subtitle: mov_text ([8][0][0][0] / 0x0008) (default) (forced)
    Metadata:
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      title           : Forced
      BPS             : 61
      BPS-eng         : 61
      DURATION        : 00:01:19.496000000
      DURATION-eng    : 00:01:19.496000000
      NUMBER_OF_FRAMES: 24
      NUMBER_OF_FRAMES-eng: 24
      NUMBER_OF_BYTES : 608
      NUMBER_OF_BYTES-eng: 608
      _STATISTICS_WRITING_APP: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_APP-eng: mkvmerge v7.0.0 ('Where We Going') 64bit built on Jun  9 2014 15:16:27
      _STATISTICS_WRITING_DATE_UTC: 2015-11-14 08:53:18
      _STATISTICS_WRITING_DATE_UTC-eng: 2015-11-14 08:53:18
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc57.28.103 mov_text
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (dts (dca) -> aac (native))
  Stream #0:1 -> #0:2 (dts (dca) -> aac (native))
  Stream #0:2 -> #0:3 (subrip (srt) -> mov_text (native))
Press [q] to stop, [?] for help
frame=  100 fps=0.0 q=2.0 size=       0kB time=00:00:04.56 bitrate=   0.4kbits/s

And now its just continuing with
frame= 5123 fps= 49 q=21.0 size=   88542kB time=00:03:34.01 bitrate=3389.2kbits/frame= 5152 fps= 49 q=21.0 size=   88932kB time=00:03:35.38 bitrate=3382.5kbits/

This part is colored as well
[AVFilterGraph @ 0x2ab49c0] [Eval @ 0x7ffdb0e6ce00] Undefined constant or missing '(' in 'auto'
[AVFilterGraph @ 0x2ab49c0] Unable to parse option value "auto"
[AVFilterGraph @ 0x2ab3d00] [Eval @ 0x7ffdb0e6ce00] Undefined constant or missing '(' in 'auto'
[AVFilterGraph @ 0x2ab3d00] Unable to parse option value "auto"
[AVFilterGraph @ 0x2a8af00] [Eval @ 0x7ffdb0e6ce00] Undefined constant or missing '(' in 'auto'
[AVFilterGraph @ 0x2a8af00] Unable to parse option value "auto"
[libx264 @ 0x2ab2a20] using SAR=1/1
[libx264 @ 0x2ab2a20] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
[libx264 @ 0x2ab2a20] profile High, level 4.1
[libx264 @ 0x2ab2a20] 264 - core 148 - H.264/MPEG-4 AVC codec - Copyleft 2003-2016 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=23 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=3000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00

Just pushed an update out to the script to made the sub_charenc option optional in autoProcess.ini instead of hard-coded
I also shuffled around the order of some of the commands. So now I would try the following things:

Update and rerun the script and see if your error persists with both video-bitrate and vide-max-width set
If that fails, find the new option subtitle-encoding in autoPrcoess.ini and set to nothing and try again

Let me know how that goes

Got this running manual.py with video bitrate and video max width set.

python /opt/Automator/manual.py -i "fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv"
Manual processor started.
Audio bitrate was invalid, defaulting to 256 per channel.
64bit Python.
Matched TV episode as fear the walking dead (TVDB ID:290853) S01E05
Proceed using guessed identification from filename?
# [y/n]: y
Processing Fear the Walking Dead Season 01 Episode 05 - Cobalt
Reading video stream.
Video codec detected: h264.
Pix Fmt: yuv420p.
Reading audio streams.
Traceback (most recent call last):
  File "/opt/Automator/manual.py", line 356, in <module>
    main()
  File "/opt/Automator/manual.py", line 347, in main
    processFile(path, tagdata)
  File "/opt/Automator/manual.py", line 204, in processFile
    output = converter.process(inputfile, True)
  File "/opt/Automator/mkvtomp4.py", line 147, in process
    options = self.generateOptions(inputfile, original=original)
  File "/opt/Automator/mkvtomp4.py", line 306, in generateOptions
    if (a.metadata['language'] == 'und' and self.adl) or a.metadata['language'].lower() in self.awl:
TypeError: argument of type 'NoneType' is not iterable

Same error with changing
subtitle-encoding

Whoops that error is unrelated to your problem and has to do with another change I made earlier tonight (you caught me when I had some free time to make changes to the script so I've been doing updates). Just patched that so you should be able to proceed now testing your specific issue. Update and try again.

Got this error now
Starting conversion.
Error converting file, FFMPEG error.
Traceback (most recent call last):
  File "/opt/Automator/mkvtomp4.py", line 612, in convert
    for timecode in conv:
  File "/opt/Automator/converter/__init__.py", line 243, in convert
    timeout=timeout, preopts=preopts, postopts=postopts):
  File "/opt/Automator/converter/ffmpeg.py", line 553, in convert
    total_output, pid=p.pid)
FFMpegConvertError: <FFMpegConvertError error="Exited with code 1", pid=11603, cmd="/root/bin/ffmpeg -fix_sub_duration -i /home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf scale=1280:trunc(ow/a/2)*2 -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -sub_charenc None -c:s:0 mov_text -map 0:2 -metadata:s:s:0 language=eng -f mp4 -threads auto -y /home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mp4">

Hmm very strange, I'm guessing that's with the subtitle-encoding option set to blank. Part of the way things are supposed to work is that the -sub_charenc option shouldn't be showing up in the command when that's blank or None but it looks like it still is for some reason.
I just pushed another update (sorry) to try and prevent that. I'm at work right now and unable to test this as well as I'd like so you'll have to keep doing it for now lol
But try this update and let me know

Nope getting the exact same error

sub_charenc still in the command?

Yeah its still there with None next to it
FFMpegConvertError: <FFMpegConvertError error="Exited with code 1", pid=12307, cmd="/root/bin/ffmpeg -fix_sub_duration -i /home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf scale=1280:trunc(ow/a/2)*2 -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -sub_charenc None -c:s:0 mov_text -map 0:2 -metadata:s:s:0 language=eng -f mp4 -threads auto -y /home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mp4">

Before I go too crazy, lemme just clarify you left the subtitle-encoding option blank in autoProcess.ini correct? You didn't type 'None' next to it?

haha yes I left it blank
[MP4]
ffmpeg = /root/bin/ffmpeg
ffprobe = /root/bin/ffprobe
output_directory =
copy_to =
move_to =
output_extension = mp4
output_format = mp4
delete_original = True
relocate_moov = True
video-codec = h264,x264
video-bitrate = 3000
video-max-width = 1280
h264-max-level = 4.1
ios-audio = True
ios-first-track-only = False
max-audio-channels = 2
audio-codec = aac
audio-language =
audio-default-language =
audio-channel-bitrate =
subtitle-codec = mov_text
subtitle-language =
subtitle-default-language =
fullpathguess = True
convert-mp4 = True
tagfile = True
tag-language = en
download-artwork = Poster
download-subs = False
embed-subs = True
sub-providers = addic7ed,podnapisi,thesubdb,opensubtitles
permissions = 0777
post-process = False
pix-fmt =
threads = auto
subtitle-encoding =

Think I may have found why its including none, but I need a video file with some subs to test it
Just pushed an update though, give it a try

Nope same problem
Traceback (most recent call last):
  File "/opt/Automator/mkvtomp4.py", line 612, in convert
    for timecode in conv:
  File "/opt/Automator/converter/__init__.py", line 243, in convert
    timeout=timeout, preopts=preopts, postopts=postopts):
  File "/opt/Automator/converter/ffmpeg.py", line 553, in convert
    total_output, pid=p.pid)
FFMpegConvertError: <FFMpegConvertError error="Exited with code 1", pid=13307, cmd="/root/bin/ffmpeg -fix_sub_duration -i /home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mkv -vcodec libx264 -map 0:0 -vb 3000k -level 4.1 -vf scale=1280:trunc(ow/a/2)*2 -c:a:0 aac -map 0:1 -ac:a:0 2 -b:a:0 256k -metadata:s:a:0 language=eng -strict experimental -c:a:1 aac -map 0:1 -ac:a:1 2 -b:a:1 512k -metadata:s:a:1 language=eng -strict experimental -sub_charenc None -c:s:0 mov_text -map 0:2 -metadata:s:s:0 language=eng -f mp4 -threads auto -y /home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.mp4">

Did the update and still showing
-sub_charenc None

Any chance you could upload a test file for me somewhere that's giving you this issue that I can download

Also pushed another attempt to directly block the -sub_charenc = None haha
I'm tired and losing my mind

Just sent you an email with test file link

Okay that last one worked and it is now converting the file

python /opt/Automator/manual.py -i "/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.sample.mkv"
Manual processor started.
Audio bitrate was invalid, defaulting to 256 per channel.
64bit Python.
Matched TV episode as Fear the Walking Dead (TVDB ID:290853) S01E05
Proceed using guessed identification from filename?
# [y/n]: y
Processing Fear the Walking Dead Season 01 Episode 05 - Cobalt
Reading video stream.
Video codec detected: h264.
Pix Fmt: yuv420p.
Reading audio streams.
No audio streams detected in any appropriate language, relaxing restrictions so there will be some audio stream present.
Audio detected for stream #1: dca [eng].
Creating audio stream 0 from source audio stream 1 [iOS-audio].
Creating audio stream 1 from source stream 1.
Reading subtitle streams.
Subtitle detected for stream #2: srt [eng].
Creating subtitle stream 0 from source stream 2.
No valid subtitle language specified, cannot download subtitles.
{
    "preopts": [
        "-fix_sub_duration"
    ],
    "subtitle": {
        "0": {
            "map": 2,
            "codec": "mov_text",
            "language": "eng",
            "encoding": null
        }
    },
    "format": "mp4",
    "postopts": [
        "-threads",
        "auto"
    ],
    "video": {
        "map": 0,
        "codec": "h264",
        "bitrate": 3000,
        "width": 1280,
        "level": 4.1
    },
    "audio": {
        "0": {
            "channels": 2,
            "map": 1,
            "codec": "aac",
            "bitrate": 256,
            "language": "eng"
        },
        "1": {
            "channels": 2,
            "map": 1,
            "codec": "aac",
            "bitrate": 512,
            "language": "eng"
        }
    }
}
Starting conversion.
/home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.sample.mp4 created.
Tagging file: /home/temp/sabnzbdplus/finished/Fear.the.Walking.Dead.S01E05.REPACK.1080p.BluRay.x264-BRAVERY/fear.the.walking.dead.s01e05.repack.1080p.bluray.x264-bravery.sample.mp4.
Trying to write tags.
Tags written successfully.
Relocating MOOV atom to start of file.

Glad its working
Went ahead and clean up some of the code and testing it on my end works. If you'd be so kind as to pull down the latest version and make sure everything is still working I'd appreciate it. If so feel free to close this issue, thanks for your patience

Just updated and tested it with another mkv and it seems to be working great thanks for your hard work!

Using the latest verion but occur the same error "for timecode in conv:". the environment is router with the openwrt system


Filter on a single value hides the value

When I have a filter on a single dimension, the thing that shows up in the Filter portion of the view just shows me dimension_name (#).  Which makes sense if I don't have enough screen real-estate to show the value.  If I do have enough screen real-estate, I'd really like to be able to see the value.

+1 I have trouble with this one as well

Changed how single value work.


Change phrasing "peak" to "Historical maximum"

Motivation
Updating phrasing on certain components: #797
Changes

Testing Instructions

Yes, also looks good to me. I was looking at it though, and saw that we were still using "Peak" on the descriptions of the landing page charts. So I wanted to rework those a bit, which I'm currently working on.  Will push a PR for that shortly and we can merge these together

Got it, let me know when you're ready @PatrickCleary


error in creating customize icon with fontello

Im having an error when I use my custom icons from fontello. I generate a new react native app just to test if my fonts config.json is the problem or not but in my new generated app the fonts are working  correctly without a problem. In my main app when I setup the config for my custom fonts I received this error:
undefined is not an object(evaluating 'children.props.name')

What makes you think the error is related to RNVI (I can't find anything in the code using children.props.name)? Any steps to reproduce?

Closing as invalid and lacking responses.


Encoding in greek

In some cases I think there is a problem with encoding in greek. E.g.: in the graph of the "Opinion interaction" a popup with "Δρ&alpha...etc." appears and in the output of the "Results Page" when we put "Download PDF File" characters are not recognized. For more details, see the attachments.

Hi @kiolalis & @ingedonke
Do you have a test LO that you can share here that demonstrates this and then I can play around with the encoding? I suspect that the PDF just needs to be told what encoding to use to solve this...
John

Hi John,
Here a link to an example, also a download link.
https://dev.tor.nl/~tom/xotdev/play.php?template_id=795
https://dev.tor.nl/~tom/xotdev/website_code/php/scorm/export.php?template_id=795&scorm=false
Bye,
Inge

Hi @ingedonke & @kiolalis
So i've nearly ironed out all the issues. Firstly, in the Canvas, the labels were showing the full HTML entity reference (γ λ etc) instead of the symbol - canvas apparently cannot process them so I first rendered them in a div tag and then captured the text representation using a simple function:
function htmlToChar(h){
return $("").html(
x_currentPageXML.getAttribute("name")
).text();
};

Secondly, the PDF needed to have a Unicode font embedded  but in order to do that I had to upgrade to the latest version of jsPDF. Sadly a lot of the api had been rewritten or deprecated and therefore I have had to re-write much of the table rendering code. I also took the opportunity to update the images to use the same as the results page:

I need to fix some of the formatting of the tables and positions of the images etc but I will get them done sometime this week and get the files uploaded.
John

Hi @ingedonke  & @kiolalis
I've now uploaded the files. I had to pretty much rewrite the results page to use the latest jsPDF since the version that we were using didn't properly support importing of unicode fonts - this also meant that I had to upgrade AutoTable and rewrite those parts to use the new API...
Since I now had to include 4 files (jsPDF, AutoTable, + normal/bold fonts) I also rewrote the loader and aggregated the files into a jsPDF folder...
There has been so much changed in this that it's probably going to have some bugs so it will need extensive testing and unfortunately @torinfo I haven't made any changes to the export or offline code tto include the extra or relocated files so that will definitely need looked at..
Lastly, there seems to be a wee bit of a bug with the opinion page and possibly the results page - if you duplicate that opinion page so you have this structure:
Opinion
Opinon
Wordsearch
Results
And you start at page 1 but DON'T submit the opinion page and move to page 2 and DO submit (with the default options) then you don't get the correct chart but instead it is tiny (below). Also, when you get to results page it shows two solid blue circles but there is an option for a solid blue and hollow blue in the code which I can't seem to have on screen at the same time...

I'm not sure if this issue is just the same as the problem that we have with many pages, in that you can't have two of the same page in the same LO without them interoperating somewhat... Perhaps some testing will help identify the issue...
John

@JohnSmith-LT @kiolalis I will test it this week and let you know. Thanks for all your work :)

Hi @ingedonke
Did you ever get around to testing this and can this issue be closed now?

Thanks @ingedonke


Updated HA proxy and changed default Stats URI

@stevendborrelli Please merge :)

Closed since another closed PR was merged with more or less same content.


Fan spins at max when 0%

With the latest update of FanControl my GPU is no longer supported, so I downloaded this Addon. Sadly the Fan spins up to 100% when it should be 0%. Is anyone able to reproduce this issue?
GPU: Radeon RX 580
Software:
FanControl.ADLX ver. 1.0.67 from https://ci.appveyor.com/project/Rem0o/fancontrol-adlx/build/artifacts
AMD Software: PRO Edition
Please let me know how I can send you more relevant information about the issue. Thank you very much for writing this addon :)

Show how you got it configured in FanControl ( screenshot ).
Also run this and show what's printed out in the console.
Test ADLX.zip

It seems to be happening after around 10 minutes or so.
The ADLXWrapper.exe runs through to 1000 and then closes automatically

Update: Now it seems to be happening every few minutes (around 5). The fan will speed up to what seems to be max speed for around 15 seconds and then returns to 0 RPM again

@LennardPlay  as far as Adrenaline is concerned, if you close FanControl, can you get your fan to behave using Adrenaline?

I have to reset the fan profile to return to normal operation again.
When updating FanControl to V191 my GPU was detected again, so I don't need to rely on the ADLX plugin anymore. Thank you for updating :) Everything works fine again.
PS: I wanna donate 5€ to this great project. What's the best way to do this? (The one with the least percentage of fees)

Don't worry about the fees, just use whatever is convenient to you. Thanks for the support!


Added MANIFEST.in.

Needed for R forecast

Job PR-145/1 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-145/1/index.html