Limit the TOC level depth in extensions/toc

Use case
Take a document, such as an API description, or a document converted from Org mode, with lots of deep-level headers and very short texts under each of them.
A TOC of such a document becomes excessively long and detailed. (My particular case is what mkdocs generates.)
A fix

Add a config parameter that optionally limits the maximum level of headers included in the TOC.
Filter the levels where they are generated according to that parameter.

I'll gladly make a PR, but would appreciate any advice on the best way to add a config parameter.

I'm sure this is a duplicate, but I can't seem to find it, In any event, we have traditionally been resistant to adding more config options. That certainly has been the stated reason for not yet adding this feature in previous discussions (which I can't find now).
Regardless, the TOC level depth is completely controlled by themes from within the templates. Our position has been that you should be able to override this with theme customization. However, it also occurs to me that as themes can now create their own settings (as of version 0.17), this could be user configurable as a theme setting. I would be willing to consider a PR which added a theme setting to both of the built-in themes.

@waylan Did you realize that this issue is for Python-Markdown, not for mkdocs?

Oh whoops. Thanks for the headsup @mitya57.

Interestingly, the OP made this statement:

(My particular case is what mkdocs generates.)

So, in the end, I did point to the correct way to address this in MkDocs. Although, by default, the builtin MkDocs themes limit the depth to 2 so I'm not sure why you're having a problem with excessively deep TOC. If you are using a third-party theme, then take that up with the devs of that theme. Otherwise, you are free to submit a PR to MkDocs as stated above.
I'm not so sure I want to add that option to the Markdown extension.

It's quite common to use markdown headings for structure and viewability, including deeper level headings however in the TOC you may not want to call them all out.  I have a document that has H1-H6, but I only want to show the higher level headings in the TOC, h1-h4.

@bpaduch ,
I would go even farther.
I would like to set the range of headers (Namely also the minimum).
As H1 is usually dedicated to the document title there is no sense of having it in the Table of Content.
So I'd like option to choose H2-H5 for instance.

@RoyiAvital that can be set with the extension options. In your config file do:
markdown_extensions:
    - toc:
        baselevel: 2

@waylan - I found the baselevel option doesn't actually limit headings but adjusts the headings, and essentially bumps them up so there is heading for that baselevel (just like in their example, a heading 1 and 2 becomes heading 3 and 4).
The same happens if I apply to my docs.  For example, in markdown I have:
## Heading 2
### Heading 3
#### Heading 4
##### Heading 5

What comes out is that the parser reformats the heading level and bumps them up a level, so that the desired baselevel isn't rendered.

Heading 2 -> becomes heading 3

 Heading 3  -> becomes heading 4

Heading 4 -> becomes heading 5

 Heading 5 -> becomes heading 6

TBH, this is strange because now you have different heading levels from the actual markdown, and the contents for heading 2 still display, but now as an h3.
Maybe I'm interpreting incorrectly but that's the results that occur when I apply it.

@bpaduch my last comment was responding to @RoyiAvital's request which is different that yours. As I explained in previous comments, what you are requesting is not currently supported and I'm not inclined to add such a feature to the extension myself.

@waylan ,
I asked to be able to set a range of Headers (Say H2-H5) which will be shown in the Table of Content.
I don't understand how what you wrote does it.

@RoyiAvital you are asking for something different that the matter being discussed in this issue. If the comment I made doesn't address your issue, then please continue the discussion elsewhere.

The issue asks to have limit on the order of the header to be included in the generated Table of Content.
You can think as limiting it on one side.
All I asked is if someone puts effort in that he should have the option to limit form both sides.
Namely only put in the Table of Content headers with number minHeader to maxHeader.
For instance if minHeaderLevel = 2 and maxHeaderLevel = 4 then:
# Header Level 1 % Will be ignored
## Header Level 2 % Will be shown
### Header Level 3 % Will be shown
#### Header Level 4 % Will be shown
#### Another Header Level 4 % Will be shown
##### Header Level 5 % Will be ignored

Sorry @RoyiAvital I misunderstood your request. To me this whole request is not something I would ever want so when I saw your request I assumed you meant you wanted the baselevel feature.

I actually doesn't understand what's baselevel is.
What I want is not to include Level 1 Header (Single #) as use it for the document title.
From that I need to be able not to include too high levels (Like 5 # -> ##### Five Level Header).

This appears to have been addressed with #686.

@waylan , could you explain what was done there?

@RoyiAvital a new config option was added: toc_depth which is documented here.

@waylan , What about the option to set the first level to be included?
To make it more clear, I want the TOC to include only
 to
 (Where
 is the highest level).

@RoyiAvital that was not part of the original request, nor is it anything I have any use for, or am interested in having. Of course, if a PR is submitted I'll consider it.

@waylan ,
Are you OK with the case that you use
 for the Title of the Document yet it appears in the TOC?
Most TOC generators (See Word, Libre Office, Apple Write) exclude the document title from the TOC.
We can't do that in Python Markdown.

I use the meta extension and include the title of the document in the meta-data. My templates then insert that Title into the HTML separate from the body of my document which comes from the Markdown. Therefore, I never get the document title included in my TOC.
I work on Python-Markdown as a volunteer in my spare time and I don't have any reason to use up my spare time on features I have no use for. Therefore, if this is something you care about, you need to do the work. If someone submits a PR, I'll take the time to review it, and if it passes my review, I'll merge it. Other than that, I have more important things (to me) to work on.


Release of version <IP_ADDRESS> of xFailOverCluster

Releasing version <IP_ADDRESS>

Hi @kwirkykat, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Katie Keim). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Propose Meltfile as the single source of truth file name

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/117
Originally created by @mbergeron on 2018-10-05 16:54:23

We don't any name for what we refer as the Single Source Of Truth for the Meltano CLI, and no complete definition of what it should represent.
In my perspective I think this file should have all the data to:

Describe all the entities and attributes
Hold metadata about each entities and attributes:

PII Status (I like the RED, GREEN, YELLOW analogy here)
Transformations (lower, truncate, ...)
Validations
Mocking strategy (to create fake data with)

Configurations of the pipeline components:

Singer tap/target files (config.json, properties.json)
DBT model location (and DBT profile)
Data warehouse access control

Debugging settings

Keep track of intermediary formats (Singer tap output, for example)

There are probably other things that should go there, so this list is not exhaustive but I think we should name this file sooner than later.
I propose Meltfile.

View 17 previous comments from the original issue on GitLab


Make the logo on the home page clickable

Is your feature request related to a problem? Please describe.
GSSOC 23
The logos on the homepage aren’t clickable. Related to a user experience problem. Most users expects that the logo takes them back to the homepage or reloads the homepage.
Describe the solution you'd like
When a user clicks on the logo, it should navigate back to the homepage.
Describe alternatives you've considered
I’ll like to add the website link to the logos to make them clickable
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello @abansal15 I’m also a contributor that raised the issue so I’ll work on it
You can visit the live site and see if there’s any modifications you’ll like to make

@AshutoshDash1999
is it the main website - https://bookingjini.com/
or the icons website- https://icons.bookingjini.tech/

The main company website is:
https://bookingjini.com/

is it the main website - https://bookingjini.com/

yes

Hello @MutiatBash, I am GSSoc contrbutor. I would like to work on the issue pls assign it to me


Game freezes/crashes when using SOS Female Pubic Hairs colored with IC-PR3 installed

This issue is very specific and esoteric so feel free not to respond if you're not comfortable.
There is an issue when using IC-PR3 and SOS Female Pubic colored for NPCs, more specifically the auto-color changing of pubic hairs
To reproduce this, a few mods are required:

Racemenu SE- https://www.nexusmods.com/skyrimspecialedition/mods/19080
Schlongs of Skyrim SE - https://www.loverslab.com/files/file/5355-schlongs-of-skyrim-se/
PapyrusUtil SE - https://www.nexusmods.com/skyrimspecialedition/mods/13048?tab=description
SOS Female Pubic Hairs colored for NPCs 2.0.4 - https://www.loverslab.com/files/file/10318-sos-female-pubic-hairs-colored-for-npcs/
Any nude body replacer

Process for reproducing:

In game, spawn any female NPC
Ensure that in the SOS mod menu they have pubic hair equipped (should be automatically equipped already)
remove all their equipment, the game should freeze
The game also freezes to a black screen when loading savegames with any NPCs that are naked with the pubic hair equipped

I did a lot of testing and discovered that:

Removing PHFPubicHairs.xml from SKSE\Plugins\NiOverride\TintData\Armor fixes the issue but the auto-color changing function is disabled
Removing the pubic hair mesh fixes the issue
Removing skee.dll from RaceMenu fixes the issue
Disabling IC-PR3 fixes the issue

There seems to be some conflict between the auto-color changing fuction of Pubic Hairs and your mod.
Anyway this issue happens only after I've installed IC-PR3. Super strange that it conflicts with a pubic hair mod of all things lol

Wth that is a weird bug!!!

Unable to reproduce the hair is changing as should with no freezing/crashing issues. (Although this is the about to be released PR4!)
Since your on SE maybe you don't have installed RaceMenu 0.4.16 Memory Leak Hotfix (SE)?

Thanks for troubleshooting, guess I'll have to test it out again with the new release then!


"Ability to add whole libraries in one click" is missing

This issue exists in 0.0.61 (Winx64) which introduced "Ability to add whole libraries in one click.":
MoRBiD MaNGLeRToday at 6:06 AM
@vexorian For the "Ability to add whole libraries in one click" Improvement, where does this ability appear?  I don't see it:

vexorianToday at 6:07 AM
Hmnn there should be a plus button
MoRBiD MaNGLeRToday at 6:08 AM
I only see + for individual movies.

Clearing Chrome's browser data and retrying fixed the issue:
chrome://settings/clearBrowserData


Improve working-with-prometheus.md

Signed-off-by: windsonsea<EMAIL_ADDRESS>What type of PR is this?
/kind documentation
What this PR does / why we need it:
Improve docs

/approve


[http] Initial codec splitting with test parametrization

This just introduces some plumbing and legacy versions of codecs. There is no changes to the codecs at this point (the files are just duplicated and the namespace Legacy is used).
Integration tests that are relevant are parameterized to run over combinations of upstream/downstream legacy and new versions of the codecs.
No-op for behavior.

Some questions:

Defaults should still be the existing codecs, which makes me think I should flip LEGACY_HTTP[12] to NOEXCEPT_HTTP[12] or something that would make it harder for users to choose the WIP/new codecs.
The grpc parametrized integration tests require more plumbing to get to work with the codecs. It makes me think I should just make a LegacyHttpIntegrationTest class.

@asraa very quick comment: I don't think we should use config for picking between legacy/exception. It's an implementation detail. Can we just use runtime like we typically do for this? I think the default should be the new code.

@asraa very quick comment: I don't think we should use config for picking between legacy/exception. It's an implementation detail. Can we just use runtime like we typically do for this? I think the default should be the new code.

Yeah will do -- I'll remove it from config and add a runtime switch with default Legacy. Should upstream/downstream be separate switch? If there's just one "use_legacy" switch, I'd run tests with legacy on/off, not with different combos of upstream/downstream legacy choices. I'm happier doing that. Much easier to plumb

If there's just one "use_legacy" switch, I'd run tests with legacy on/off, not with different combos of upstream/downstream legacy choices. I'm happier doing that. Much easier to plumb

Yes +1, let's just keep it simple. Also, FWIW, I think the default should be new/exceptions vs. legacy. I don't really think these changes are scary enough to warrant default legacy, but I don't feel super strongly about it if you and @alyssawilk feel otherwise.

I think as long as people can opt out and we warn there's a series of high risk changes (stick in the release notes as we add the runtime flag) coming we can default on.  We can get more conservative if the tests prove to not be sufficient for this sort of refactor change.

Gotcha! Will plumb that through and push again with the runtime flip.

+1 on runtime vs. config.

Before I start -- instead of TEST_P'ing over a bool to setLegacyCodec() in each integration test (and also codec_client_test/conn_pool_test), should I just create duplicate bazel targets that would define a macro that conditionally calls setLegacyCodec() ?

@asraa how many tests files vs. individual TEST_F are we talking about?

In test/integration: 504 tests individual tests, 49 integration test classes that would need to be parametrized, 42 test files

Hmmm.  Brainstorming simpler options, what if we had the default option set
in a #define, and ran all the tests is non-default mode in one of the
builds (maybe the one that runs with deprecated options fatal), and then
only do a few tests in both A and B modes?
It would mean we didn't have comprehensive coverage (asan and tsan) for all
integration tests, but they'd all run in both modes.
On Tue, Mar 31, 2020 at 2:40 PM asraa<EMAIL_ADDRESS>wrote:

In test/integration: 504 tests individual tests, 49 integration test
classes that would need to be parametrized, 42 test files
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/pull/10591#issuecomment-606802254,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AELALPIUCOAYRO6VNHYMVV3RKI2LBANCNFSM4LXWE3RA
.

It would mean we didn't have comprehensive coverage (asan and tsan) for all integration tests, but they'd all run in both modes.

I like the idea of a running them with a separate build that runs with a --define use_legacy=true, but am worried about not having any asan coverage. Maybe we can run just //test/integration/... with asan here? https://github.com/envoyproxy/envoy/blob/016e92d60c5de0a3789b2c4b2da17a9dec78c0cd/ci/do_ci.sh#L232
I can parametrize over the other two tests since they're one and done things (codec_client_test)

SGTM, though @lizan or @htuch might have opinions on how to best do build / CI workarounds.  I think ASAN and debug builds are most important (catch assertion failures and any memory issues) so I think if we do unit and integration tests for legacy for those we're good.

Merged master, fixed clang-tidy, and will check the diff in CI time with this commit.
Quick question: I just wrangled with an integration test error for an hour or two before I realized it was happening because of a merged change in the new codecs that wasn't back ported to the legacies. To stop this from happening all the time, is there an easy way to write a fix_format rule that does the diff of the codec_impl's and codec_impl_legacy's? There's an expected diff (in namespaces), but the line numbers would change with code additions

@asraa good idea; we could just maintain a golden diff for each codec and force anyone making codec changes to update it. That will force anyone making a codec change to confront the need to synchronize. It's a bit of extra work for anyone playing with codecs, but I like it (or something along those lines).

@alyssawilk I agree, we can turn down the runtime guard earlier than usual if we want as we aren't deprecating something. I think we need to see significant burn time on the new path; probably the closest example we've had is the migration of buffer implementations.
@asraa WDYT of differentially fuzzing the two implementations in codec_impl_fuzz_test? It probably won't be a ton of work to add support for both. We used this kind of differential fuzzing in the buffer migration to get high confidence in behavioral equivalence.

OK I think the codec_impl diffs in fix_format work reasonably well (at least well enough to alert you have an issue with syncing), I had another patch to do this morning, and the fix_format caught it. I added a print out of the expected diff too to the error message to update it easily.
Fuzzers: Yes i think so! I don't think I want to tackle it in this PR, but I think it's worth doing on a change.
Policy for staying around: @yanavlasov @mattklein123 As soon as this PR and the statusor one are merged, yan and I are splitting up the H/1 and H/2 removals. I think at that point we'll need some time to canary the change to make sure we've caught places where exceptions were thrown outside dispatching context. I don't know how long that'd take, should we aim for a release date?

Policy for staying around: @yanavlasov @mattklein123 As soon as this PR and the statusor one are merged, yan and I are splitting up the H/1 and H/2 removals. I think at that point we'll need some time to canary the change to make sure we've caught places where exceptions were thrown outside dispatching context. I don't know how long that'd take, should we aim for a release date?

My personal feeling is that we should stage this change and the first actual code change and land them mostly together, with default enabled. Given the extra pain of maintaining both versions it would be good to not merge this until we are ready to go IMO. After we do that, I think we should aim for removal in ~4 weeks or so? WDYT?

My personal feeling is that we should stage this change and the first actual code change and land them mostly together, with default enabled. Given the extra pain of maintaining both versions it would be good to not merge this until we are ready to go IMO. After we do that, I think we should aim for removal in ~4 weeks or so? WDYT?

Hm, yes. This is a pain to maintain (as you can see I yet again had to patch). You're right, this is best to merge when the codec changes are ready. If so the timeline would probably look like this:

Merge Yan's Status/StatusOr
Update POC to use Status/StatusOr, make sure there's consensus in the poc
Stage this Splitting, Asra H/1 change, Yan's H/2 change and merge when ready

I added a more verbose release message, and changed the copts to only define the macro in the target it was used in. At this point, should I leave this PR with a nostalebot until we're ready to revisit?

This is ready for re-review. I updated the PR description with a summarization of the changes in the PR.

@mattklein123 When you have a chance, could you please take a look? Or any other non-googler maintainer :)
Summary of updates:

integration tests parametrized and run in legacy mode in compile_time_options
h/1 codec_impl_test is parametrized on codec type
h/2 codec_impl_test is also parametrized, but the target is duplicated and built with a test flag for runtime override
no-op everywhere else, codec implementations are cloned, default new codecs
format still enforces the devs change or make updates to the golden diffs, but that may be unncessary now that the tests are parametrized
clang_tidy fails on existing issue #11691

Clang tidy seems to be off, flagging gtest macros with invalid casing.


Dockerfile: stay on 20.04/LTS for python3.8

Description
Docker building failing with ubuntu:latest (jammy) as no python3.8 is available.
Type of change
force LTS/20.04 version

This is an alternative to #4568 (where ubuntu is bumped to 22.04). Could you enable container steep to check if everything passes?

the singularity step requires napari to allow public pull from the artefacts at https://github.com/orgs/napari/packages?repo_name=napari


ImportError: cannot import name 'BertModelLayer'

Describe the bug
A clear and concise description of what the bug is.
hanlp2.0安装使用错误
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
import hanlp

Describe the current behavior
A clear and concise description of what happened.
ImportError: cannot import name 'BertModelLayer'
Expected behavior
A clear and concise description of what you expected to happen.
正常导入
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Linux Ubuntu 16.04
Python version:3.6.9
HanLP version:hanlp-2.0.0a46

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.6/dist-packages/hanlp/init.py", line 17, in
import hanlp.components
File "/usr/local/lib/python3.6/dist-packages/hanlp/components/init.py", line 5, in
from . import tok
File "/usr/local/lib/python3.6/dist-packages/hanlp/components/tok.py", line 12, in
from hanlp.components.taggers.transformers.transformer_tagger import TransformerTagger
File "/usr/local/lib/python3.6/dist-packages/hanlp/components/taggers/transformers/transformer_tagger.py", line 13, in
from hanlp.layers.transformers.loader import build_transformer
File "/usr/local/lib/python3.6/dist-packages/hanlp/layers/transformers/loader.py", line 9, in
from bert import BertModelLayer, albert_models_tfhub, fetch_tfhub_albert_model

[x] I've completed this form and searched the web for solutions.
yes

Did you install the required versions of thirdparty packages?
https://github.com/hankcs/HanLP/blob/master/setup.py#L37


feat: Implement Avail validium data attestation contracts

What ❔
This PR adds data attestation support for validiums using Avail's bridge.
Why ❔
This adds verification and storage of data attestations onchain allowing for provable data availability on the settlement layer.
Checklist

[X] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[X] Documentation comments have been added / updated.

Closing this one because these changes were already added to sync-layer-stable

era beqaraj


Add a 'lookup'-page, to instantly retrieve information on topics

Using knowledge databases such as MIT search or Wikipedia, implement a search page that grabs data from either of these sites. Using word weighting and other techniques, a quick summary will be provided in realtime to the user.

Usage: "I want to learn about.... user input"

http://stackoverflow.com/questions/18065526/pulling-data-from-a-webpage-parsing-it-for-specific-pieces-and-displaying-it


fix: validation custom error with asterisk field

Description
Fixes #6245
Reopen PR #6340
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

I would like to ask you to change the declaration of methods according to PSR-12 (there is an example here: https://www.php-fig.org/psr/psr-12/#45-method-and-function-arguments). Because the string is longer than 120 characters.

@kenjis @MGatner What do you think if the three arguments ($field, $label, $originalField) are replaced with an array or a DTO?

What do you think if the three arguments ($field, $label, $originalField) are replaced with an array or a DTO?

It seems this fix needs BC break, so I'm fine with the change.

These methods have way too many parameters. I don't know that adding a new one is worse than a breaking change though. Definitely we should break this up somehow in version 5. If anyone can think of a way to handle this now as backwards-compatible I'm open to it.

@iRedds @kenjis  I have been changed declaration of methods to follow PSR-12 and added the comment out of originalField parameter.

@ping-yee Add a description to the changelog.

v4.2.3 has been released. See https://github.com/codeigniter4/CodeIgniter4/releases
This change will be included in v4.2.4.
Please rebase and add changelog v4.2.4.
See https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/workflow.md#updating-your-branch

@kenjis Is this normal? Or I do the wrong thing when I rebase my branch...
If I do the wrong thing, please tell me how can I fix it :(

@ping-yee This is not normal. You did something wrong.
What commands did you run?
And please don't use git merge.

@kenjis I use sourcetree to manage my git flow.
I syncing your repository first, and run rebase onto devlop branch.
After I resolve the conflicts, run rebase onto devlop branch again(Maybe there is a problem with this step).
Then I push the commit fa442b4 and get the results.
Should I re-open the new PR or do something to fix this?
Sorry, this is my first time to contribute :(

I syncing your repository first, and run rebase onto devlop branch.

My repository? Do you mean https://github.com/kenjis/Codeigniter4 ?
If so, my repository has nothing to do with you.

After I resolve the conflicts, run rebase onto devlop branch again(Maybe there is a problem with this step).

You did rebase onto develop twice.
I don't know why your branch is like this.

Should I re-open the new PR or do something to fix this?

If you drop the commits other than you did for this PR (the commits marked below) with git rebase -i,
you can revert the branch state. Then rebase again correctly.

But you don't use git command, I can't support you.
If you can re-open the new PR, that is also fine.

I syncing your repository first, and run rebase onto devlop branch.
@kenjis I say the wrong word. Not your repository, my repository is right word.
Thanks for your help and I'll use command to rebase my git flow!

Okay, if syncing your repository means this https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/workflow.md#syncing-your-repository , you just did rebase twice.
In my understanding, if you did rebase twice, the result is the same. The second rebase does nothing.
So I still have no clue for the status of your mess branch.

Would it be to I don't syncing my repo before I commit my change?
I try to fix the git flow later.

Would it be that I don't syncing my repo before I commit my change?

Sorry, I don't get your situation.
I thought you synced your repository, and did rebase twice.
But you say you did not sync?
After all, the current your branch is abnormal state.
There are two commits that are the same content.
git rebase never creates a new commit. It just change the existing commits.
Either you did something I couldn't anticipate, or Sourcetree ran strange commands that I couldn't anticipate.
In any case, I do not know of any way to get the branch into this state.

I think my git flow is too mess to fixed, so I decide to re-open the PR.
Thanks for your help and teach again! @kenjis


How to reduce pitch shift artifacts

This has been brought up before (2 years ago) in issue #383, was wondering if there is any way to reduce the artifacts? Also, with using Tone.GrainPlayer there isn't any clear example on how to connect these and modify pitch.
Was hoping that there be a workaround for reducing the artifacts while using PitchShift or GrainPlayer, any example code would be helpful.
Audio file is provided as either .wav or .mp3

@tambien thanks a lot for labelling this for docs! But apart from the example code, I am wondering if there is any way to reduce noise/artifacts when using Pitch Shift or GrainPlayer?

The parameters you choose really depend on amount of pitch shifting you do and also your source audio (i.e. percussive, drone, noisy). I would say there is no magic values, it's just about finding what sounds right for you given your source. In general the more of the pitch shifting you apply, the greater your artifacts are going to be. In the case of GrainPlayer you can adjust the grainSize and overlap to try to reduce artifacts. PitchShift does not have as many controls, you can adjust the windowSize to something that sounds right to you.

This question was very helpful to me


Remove dependency on custom Prometheus fork

Sorry for the huge PR - I think this wasn't really feasible to split up into multiple, still compiling and working PRs. When changing the origin repo of the Prometheus vendoring to point to prometheus/prometheus vs. tomwilkie/prometheus, that requires basically touching and fixing up everything at once.
Things in this PR:

Changes the vendoring of Prometheus to use the official upstream master.
The static web (graph UI) assets were partially in our custom fork, partially in upstream (but not in a reusable fashion). I copied the necessary assets, as well as added build steps to build the compiled-in static assets in bindata.go.
The web API copy is now deleted. Instead, we use the new context support in the upstream WebUI->PromQL->Storage stack. Instead of building a new MergeQuerier for every request, creating a PromQL engine from that, and handing it to the web UI, we can now simply add the user info to the request context at the very beginning and let the web UI and PromQL hand the context all the way down to our custom storage, which extracts that info from the storage again.
Use the opened-up upstream chunk interfaces from the ingester.
Since there was no agreement upstream to open up the fingerprint mapper, fingerprint locker, and memory series code to outside users, I had to copy over the code for them. I simplified them as far as I could: removed persistence support and deleted all unused methods. Further simplifications are possible in the future.
A number of other adjustments that were necessary.

I added three TODO(juliusv) markers that need further upstream support to be fixed again:

The upstream chunks currently don't have a utilization method and there's no way to get to this info anymore, so I disabled the instrumentation for it for now - high priority to enable this again, as this histogram also functions as a counter of stored chunks:

// TODO(juliusv): Re-enable upstream support for this.
// i.chunkUtilization.Observe(chunk.C.utilization())

When decoding a chunk in the querier, we can't get the number of samples in the chunk before decoding it anymore, leading to a probably negligible performance overhead:

// TODO(juliusv): Pre-allocate this with the right length again once we
// add a method upstream to get the number of samples in a chunk.
var samples []model.SamplePair

The upstream web API expects a local.Storage as the second constructor argument. I extended our MergeQuerier to satisfy this interface, although most of the methods are not actually called. Plan: make the expected interface in the upstream web API narrower to only ask for the methods the web API is actually using.

Vendoring commit also looks ok.

@jml Thank you!
Indeed, some comments to look at there in the ingester, but they all concern code that was just copied as is. So I'd prefer addressing them in a followup.

Great. I don't think I've found anything here that needs to be addressed here, so please merge when ready.


Garbage collection

Hi,
I have a question regarding the behavior of the extension.
When I was using Web Audio Inspector I noticed that the nodes in my app were piling up.
I was implementing a fix to make sure to disconnect the unused nodes properly but then Audion was introduced.
Using Audion, I check on the version my code where the nodes were piling up and the ones that are unused seems to be discarded now.
Can anybody confirm that garbage collection is actually at work here ?
I have issues monitoring the memory and the theory on the nodes's garbage collection is quite nebulous.
So I can't really make up my mind if Web Audio Inspector had issues displaying the nodes that were garbage collected or if it is Audion that's discarding the AudioBufferSourceNode that already played but are still connected.
If it is the case, then I don't necessarily need to disconnect the used nodes.
Thanks

Maybe @hoch can give more authoritative answers here, but I assume that letting a non-looping AudioBufferSourceNode  complete it's playback or calling stop and removing any reference to it should trigger garbage collection - calling disconnect manually should not be needed. Be aware that the timing of garbage collection is explicitly unspecified - the exact point in time when GC kicks in and what is collected is not specified and can change with future browser versions.
IIRC, older versions of the Web Audio Chrome Extension were prone to keeping references to AudioNodes which might result in prevention of garbage collection. The current audion version never accesses your AudioNodes - it receives the metadata through special Chrome Debugging APIs.

A great explanation, @max-vogler! I don't have anything to add here. :)

This clear things up.
Thank you for your answer @max-vogler

You can manually trigger a GC in memory tab of the devtool. If your nodes disappear after that, the GC is working on your nodes.

Closing per https://github.com/GoogleChrome/audion/issues/113#issuecomment-968673333.


Issues with clustering markers and pinch zoom on mobile

Hi,
We have noticed a problem with clustering markers in our app. But we saw that the same problem happens with the example map at:
https://developers.google.com/maps/documentation/javascript/marker-clustering
First issue:
If you put one finger on one clustering marker and another finger on another clustering marker and then pinch to zom in. After a short while the zoom will stop and all the clustering markers will dissapear. They show up again if you pan or adjust the zoom.
Second issue:
Sometimes when we try to pinch to zoom and happen to put one finger on a clustering marker the map will zoom out completly to the world map. We haven't figured out completly what triggers it. If it's certain spot on the clustering marker. But it will happen maybee 1 time in 10 tries...
Both issues can happen on both iOS and Android.
In our application we have a lot of clustering markers so the problem happens more frequently.

We are experiencing this exact same issue and are currently going to investigate whether there is a workaround / solution.

Findings from my investigation:
Map has touch listeners applied to know when to zoom, so touches.length > 1 ? doZoom : doNotZoom. Cluster has event propagation so it bubbles the event up to the map, but the touch event is registered on the cluster. When you zoom the cluster is removed, so consequently the event is removed, because that is good practice. This removes the touchmove listener and because the touchmove has been removed, the `maps.event.addListener(Map, ‘idle’, ...) event is never triggered because the map thinks it’s still being interacted with.
Thing is, the cluster should not be removed until the idle event has been triggered, as this triggers a redraw.
Things that trigger a cluster redraw:

Adding markers
Adding a single marker
Removing a single marker
Removing markers
When the map becomes ‘idle’
A repaint (which we never trigger as we don’t have draggable markers)

Things I did to debug:

We are not triggering a cluster redraw mid-move.
I logged every instance of the cluster redraw, and the clusters are not being redrawn
Neither then MarkerClusterer or the Clusterer classes is not being reinitialised at any point

I thought it could be something that we were doing that could trigger the markers to be removed, but it's not. It's also apparently nothing that the library is doing (that I can see). The markers are just removed from the DOM when zooming.
The cause of the issue:
All of the clusters are removed and re-added on zoom_changed with not throttling of the event. This is the problem. The markers should not be re-drawn until the user has finished interacting with the map. The zoom_changed event should be throttled or debounced.

@flojon We have a workaround if you're interested!

Remove the zoom_changed listener starting line 163.
Change the idle listener to the following:

  google.maps.event.addListener(this.map_, 'idle', function() {
    that.resetViewport();
    that.redraw();
  });

@alexmccabe Thank you for your help! I finally tried your workaround. I noticed we actually use MarkerClusterPlus so I changed the idle listener to this:
        google.maps.event.addListener(this.getMap(), "idle", function () {
            cMarkerClusterer.resetViewport_();
            cMarkerClusterer.redraw_();
        })

There is one issue with this workaround. If I put my fingers on two cluster marker or two fingers on the same cluster marker and zoom it will "zoom" into the cluster marker, ie, make it bigger, instead of zoom into the map... To reset it I have to double touch on a cluster marker.

I've replaced that code inside googles code, but by the sounds of it you're trying to overload their listener with yours, which I don't think will work and will probably result in the issue you are having.
I cloned the google maps library and we now maintain our own version of it, with my previous workaround.

I replaced the code inside markercluster.js here: https://github.com/googlemaps/v3-utility-library/blob/66d4921aba3c0d5aa24d5998e485f46c34a6db27/markerclustererplus/src/markerclusterer.js#L754-L770
We have a copy of that file in our repository.
I removed the zoom_changed listener and modified the idle listener.
Is your clone public?

https://gist.github.com/alexmccabe/510dc73e27c7c04be669dff96f0acbd9
Here you go buddy

Could this be made into a PR?
I don't find any downside of the @alexmccabe version

I believe the issue still exists: on mobile, trying to zoom or pan with a finger on a cluster fails.

Sorry I didn't get around to opening a PR for this, and now I'm totally out of the loop in what the original problem was (I've switched jobs multiple times since then, pandemic for you). @jeanmatthieud It's not ideal, but the workaround I posted seems to have worked for at least one other person. Maybe you could check the gist I posted? It seems there hasn't been any changes to the core lib so you could replace the package version in it's entirety with the version I posted. You could look into patch package to make it easier?

Hi!
I'm having this same issue with the latest version too with the https://github.com/googlemaps/js-markerclustererplus Everything works fine on desktop. In the mobile, if you pinch zoom by not touching the cluster-icons, it works, but if you pinch zoom over marker icon, depending on the meta viewport settings, it either zooms the whole viewport or does not zoom at all.
I had implemented the latest version of markerclustererplus with hiding/showing markers inside cluster and it worked fine (except pinch zoom on mobile),  and when I tried @alexmccabe version (https://gist.github.com/alexmccabe/510dc73e27c7c04be669dff96f0acbd9) pinch zooming started working but marker hiding/showing did not work.
I'm kinda stuck now between these two versions. I need to either try to get "old" version working with my marker hiding/showing code, or hopefully get the latest version working with pinch zoom.
I'm happy to help if needed.
Br,
Jukka


Unexpected/random behavior when using jasmine.clock() (install/tick/uninstall)

When using jasmine.clock feature to wait for some action to take place, the results of my tests are unexpected.

Sometimes it just never runs
The test fails, but when I try in the browser it works.
If I use javascript setTimeout, sometimes the tests pass, but sanjo:jasmine throws an error on the console the says: Uncaught Error: 'expect' was used when there was no current spec, this could be because an asynchronous test timed out. (this is expected, I believe).

Specs
describe('AdminDistributorForm', function () {

	describe("when filling up address", function () {

		var $div, $zipCodeField, $stateField, $numberField, zipCode, fakeAddressFromZipCode;

		beforeEach(function () {
			var div = document.createElement("DIV");
			Blaze.render(Template.AdminDistributorForm, div);
			$div = $(div);
			$zipCodeField = $div.find('[name=addressZipCode]');
			$stateField = $div.find('[name=addressState]');
			$numberField = $div.find(['name=addressNumber']);
			zipCode = '05050150';

			jasmine.clock().install();
		});

		afterEach(function() {
			jasmine.clock().uninstall();
		});

		it('should fetch address when zipcode is provided.', function () {
			spyOn(utils, 'addressFromZipCode');
			$zipCodeField.val(zipCode);
			$zipCodeField.trigger('blur');
			expect(utils.addressFromZipCode).toHaveBeenCalledWith(zipCode);
		});

		it('should autocomplete address fields if valid address is returned, and focus on the address number field.', function () {
			spyOn($.fn, 'focus');

			$zipCodeField.val(zipCode);
			$zipCodeField.trigger('blur');

			jasmine.clock().tick(10);

			expect($stateField.val()).toEqual('SP');
			expect($.fn.focus).toHaveBeenCalled(Jasmine.any);

		});
	});

});

Implementation
Template.AdminDistributorForm.events({
	'blur [name=addressZipCode]': function(e) {
		var zipCode = $(e.target).val();
		var address = utils.addressFromZipCode(zipCode);

		$('[name=addressState]').val("SP");
	}
});

Template

        CEP
        <input type="text" name="addressZipCode" id="addressZipCode" class="form-control" />

        Estado
        <input type="text" name="addressState" id="addressState" class="form-control" />

Where do you use setTimeout? Do you just want to wait for a condition?
I think you need to make the test async. Then you can use setTimeout.
it('should autocomplete address fields if valid address is returned, and focus on the address number field.', function (done) { // Make the test async by having an argument
            spyOn($.fn, 'focus');

            $zipCodeField.val(zipCode);
            $zipCodeField.trigger('blur');

            setTimeout(function () {
                expect($stateField.val()).toEqual('SP');
                expect($.fn.focus).toHaveBeenCalled(Jasmine.any);
                done(); // Tell Jasmine that we are done
            }, 10); // It is milliseconds by the way ;-)
        });

You can find out more about this feature in the documentation of Jasmine: http://jasmine.github.io/2.1/introduction.html#section-Asynchronous_Support

Thanks for the quick response Sanjo!
Calling done in the setTimeout removes the Uncaught Error: 'expect' was used when there was no current spec, this could be because an asynchronous test timed out console error, but throws another one Uncaught ReferenceError: Jasmine is not defined.
Also, I appreciate your help in regards to my implementation, but what worries my is that I can't use jasmine.clock feature, which from the jasmine documentation, I suppose is the preferred way to wait for actions before asserting things, instead of using setTimeout (which feels like a hack that I did).

In my understanding jasmine.clock is used to test code that uses setTimeout or setInterval. You can also manipulate the time with it for Date usage.
The line expect($.fn.focus).toHaveBeenCalled(Jasmine.any); must be expect($.fn.focus).toHaveBeenCalled(); or `expect($.fn.focus).toHaveBeenCalled(jasmine.any); (lowercase jasmine).

That solved the problem Sanjo. Thanks for catch the typo issue!
The other thing that I was doing wrong is that I was checking the value of a field I autocompleted:
expect($stateField.val()).toEqual('SP');

When I should be doing the following:
spyOn('$.fn', 'val');
expect($.fn.val).toHaveBeenCalled();


[BUG] Errors in documentation

Describe the bug

Grammar mistake in the main page

The doc for browsers.Chromium says "Google Chrome"

(Not an error or a bug) the quick start could demonstrate the use of browser_history.get_history from #15.

To Reproduce
Steps to reproduce the behavior:

Go to the documentation
Read
Scroll?
See error

Expected behavior
The errors need to be fixed and an example usage of get_history() must be included in the quick start.
Additional context
If you find any more errors, add them to the thread here.

I'll work on this.

Sure.


how do I stop the training of RASA

No description in here but I think you can press Ctrl + C from ur command line

thanks @hungph-dev-ict  , can the same procedure be applied for disconnecting the ngrok server ,i am not able to disconnect the ngorok server

I think when you press Ctrl C, your model has not been trained and old models wil still be reused

thaanks @hungph-dev-ict


proposal: x/net/html: Allow getting raw HTML attribute values on Tokenizer

Related to https://github.com/golang/go/issues/17667
The current Tokenizer API does not provide a way to get the raw tag attribute values when parsing, as it always unescapes the value.
My proposal is to configure such behavior by providing a new API method UnescapeAttr which allows us to do it while keeping consistency across the package. There is also the option of implementing Raw... API methods that replicate the logic of the existing ones while maintaining the original parsed value.
A tentative PR can be found at https://go-review.googlesource.com/c/net/+/405034

CC @neild @bradfitz

CC @nigeltao

What's the use case? I see that https://go-review.googlesource.com/c/net/+/405034 says it fixes https://github.com/golang/go/issues/17667 but that issue notes that "Escaping again the unescaped attribute values can be a solution" that doesn't require new x/net/html code or API changes.

@nigeltao I'm not the author of the original issue, but the statement of Escaping again the unescaped attribute values can be a solution isn't true. Two situations where that doesn't work are:

when the value is unescaped to begin with, so you're escaping something that wasn't before
when the value contains both escaped and unescaped characters

The goal here is to get the 'raw* value, not an escaped/unescaped version of it. In addition, as per the docs: UnescapeString(EscapeString(s)) == s always holds, but the converse isn't always true.

The goal here is to get the raw value

This sounds like an XY Problem, where "get the raw value" is a solution but it's not clear (1) what the underlying problem is and (2) whether "get the raw value" is the best solution to that.
What's the actual problem?

For context, I'm working on a tool that:

parses html
possibly does some transformation on the content depending on a set of conditions. None of those conditions are "unescape the value of the tag attributes if X", so those values should stay the same as the original input.
outputs said transformed html

This sounds like an XY Problem

I guess I could argue the same for the current implementation. Why are the values of the current implementation unescaped, considering the lib provides a method to do so if needed.

possibly does some transformation on the content depending on a set of conditions. None of those conditions are "unescape the value of the tag attributes if X", so those values should stay the same as the original input.

Why do the attribute values have to stay the same bytes? Would it work if your tool outputs equivalent attributes (in that both before and after's unescaped forms are equal) instead of identical attributes?
In other words, what breaks if passing
 to your tool produces <div bar="<">?

Why are the values of the current implementation unescaped, considering the lib provides a method to do so if needed.

Unescaping for text nodes is unfortunately different from unescaping for attributes. Go's Unescape function's documentation could admittedly be better, but it is only for text nodes' raw bytes and it would be incorrect to apply the Unescape function to attributes' raw bytes.
Specifically, look for "pound=" in https://github.com/WebKit/WebKit/blob/6b07b8bc6e0e5aaac87b1c8373d52e8fe1f942c1/LayoutTests/html5lib/resources/entities02.dat
Focus on lines 195, 204, 263 and 272:
195:

204: |       bar="ZZ&pound=23"

263:
ZZ&pound=23

272: |       "ZZ£=23"

For "&pound=", which does not contain a semi-colon, this is not unescaped when in an attribute context but is unescaped (to become "£=") when in a text node context.
Yes, it's maddeningly inconsistent. There's different escaping rules again for


Mouse cursor is not visible on the bright background

We may try to make the cursor transparent but with inverted colors filter or something


Single binary distribution concept

Hi Mike,
Firstly, congrats on a creating a great package.
I seen a couple of mentions about bundling thrust with the go executable within the closed issues.
I've created a proof of concept on Linux, which should be easy to replicate on Windows.
Basically, you append the thrust zip to the go binary, then adjust the offset.
go build basic_webserver_app.go
cat thrust-v0.7.6-linux-x64.zip >> basic_webserver_app
zip -A basic_webserver_app

In helper_linux.go i've imported github.com/kardianos/osext to get the path of the running exe, then simply unzipped that.
func prepareExecutable() error {
	exe, err := osext.Executable()
	if err != nil {
		return err
	}
        // if exe contains archive
	       return unzip(exe, GetThrustDirectory())
        // else
              // downloadFromUrl()
}

I think this concept maybe a good idea to implementing properly, but I appreciated that there would be a few issues to consider first. Let me know your views.

Awesome concept, unfortunately my ability to type and code is severely hindered by an injury.
If you would like to submit a PR that works, and examples, i would love to merge it.

Oh no, @miketheprogrammer! Did you try not getting hurt? :D
@everclear I've bundled assets like this with go applications before, simply to have a purely standalone application in a single file. It's a pretty big hassle on Windows, though. The biggest drawback I really see to it is that you can't go run the application without additional checking (or build constraints).
What I ended up doing with my application internally was defaulting to the XDG Base Directory spec, with no special case for Windows.
So, in pseudo-code (as I'm totally being naughty and githubbing from work):
assetDir := filepath.Join(xdg.CacheDir(), "go-thrust")

if !dirExists(assetDir) {
  // Make directory
  // Download release
  // Validate, extract, carry on
} else if !fileExists(filepath.Join(assetDir, "thrust", "thrust_shell") {
  // Zip file there? Looks like the version we want? Extract it and carry on
  // No zip file? Bah! Download release, extract, carry on
} else {
  // If you're super paranoid you can do some checking here
  // Or maybe check for a newer release in the background while... carrying on
}

Since the thrust shell is essentially a runtime component that's decoupled from your app, there's really no harm in having that as part of the first run logic. Or on-startup checks. Etc. Github for Desktop, Chrome, a lot of applications work this way nowadays. This also provides the ability to test across different releases without creating a new build for each, either by setting the XDG environment variables, or using version flags. Whatevs.
Thoughts? Personally, I like having a small app that's all mine. And releasing updates regularly. If you mash all the bits and bytes together you're going to have to download the entire thrust runtime to get updates to your application, even when thrust itself has nothing new.

@everclear's solution also work in Windows.

Let's look into it then. Can someone submit a pr
@everclear https://github.com/everclear's solution also work in Windows.
—
Reply to this email directly or view it on GitHub
https://github.com/miketheprogrammer/go-thrust/issues/60#issuecomment-148985183
.

It would be awesome to have this built in. I essentially did that with go-bindata in my app:
func extractAssets(provisioner *appProvisioner) error {
	assetList := provisioner.AssetList()
	for i := range assetList {

		// root is the install root that the assets get unpacked to.
		var root string

		// assetName is the name of the asset bound by go-bindata.
		assetName := assetList[i]

		// check whether its going to the binary dir for thrust or general asset
		// directory.
		if strings.Contains(assetName, "thrust/") {
			root = provisioner.ThrustBinDir
			assetName = strings.Replace(assetName, "thrust/", "", 1)
		} else {
			root = provisioner.AssetRoot
		}

		outputFileName := filepath.Join(root, assetName)

		// decompress the asset into memory
		asset, err := provisioner.GetAsset(assetList[i])
		if nil != err {
			return err
		}

		// make sure the folder is created.
		outputPath, _ := filepath.Split(outputFileName)
		err = os.MkdirAll(outputPath, os.ModeDir)
		if nil != err {
			return err
		}

		// write the asset out.
		err = ioutil.WriteFile(outputFileName, asset, os.ModePerm)
		if nil != err {
			return err
		}
	}
	return nil
}

Any closer on this?  :D

AFIAK Thrust is halted until further notice. :'(
I made something similar using electron that I have go bindings for.  https://github.com/rrohrer/electronshell and https://github.com/rrohrer/go-electronshell.
It's not as complete as Thrust, but it works with the default build of electron + it's at least robust enough to ship the app that my company made with it. (basic desktop app doing nothing too fancy).
There are currently some Windows specific hacks in go-electronshell but it's actually easier to do it the 'right' cross-platform way.  Windows just... isn't the best.

I have just gotten back into golang at work. I am too injured to work on
this at home but will try to work some cycles in at work
On Feb 7, 2016 4:42 AM, "Ryan Rohrer"<EMAIL_ADDRESS>wrote:

AFIAK Thrust is halted until further notice. :'(
I made something similar using electron that I have go bindings for.
https://github.com/rrohrer/electronshell and
https://github.com/rrohrer/go-electronshell.
It's not as complete as Thrust, but it works with the default build of
electron + it's at least robust enough to ship the app that my company made
with it. (basic desktop app doing nothing too fancy).
There are currently some Windows specific hacks in go-electronshell but
it's actually easier to do it the 'right' cross-platform way. Windows
just... isn't the best.
—
Reply to this email directly or view it on GitHub
https://github.com/miketheprogrammer/go-thrust/issues/60#issuecomment-180984155
.

Awesome!

omg ... i freakin did it. after a year away from GoLang.
I did the go-bindata you suggested. It was incredibly easy.
type SingleBinaryThrustProvisioner struct{}

/*
NewSingleBinaryThrustProvisioner instantiates an SingleBinaryThrustProvisioner
*/
//go:generate go-bindata -pkg $GOPACKAGE -o vendor.go vendor/
func NewSingleBinaryThrustProvisioner() SingleBinaryThrustProvisioner {
	return SingleBinaryThrustProvisioner{}
}

/*
Provisions a thrust environment based on settings.
*/
func (sbtp SingleBinaryThrustProvisioner) Provision() error {
	err := sbtp.extractToPath(base+"/$V", thrustVersion)
	if err != nil {
		return err
	}
	return Bootstrap()
}

func (sbtp SingleBinaryThrustProvisioner) extractToPath(filepath, version string) error {
	fileName := strings.Replace(filepath, "$V", version, 1)
	data, err := Asset("vendor/thrust-v0.7.6-darwin-x64.zip")
	if err != nil {
		fmt.Println("Error accessing thrust bindata")
		return err
	}
	fmt.Println("No error accessing thrust bindata")
	fmt.Println("Writing to", fileName)
	err = ioutil.WriteFile(fileName, data, os.ModePerm)
	if nil != err {
		return err
	}
	return unzipExecutable(fileName)
}

I will test later and publish soon

Looks promising!!  :D

Resolved #67


ISSUE: zwave platform (old OZW) still supported?

Describe the bug
A clear and concise description of what the bug is.
I'm trying to install this using the old zwave platform (old OZW) and config flow fails with the following error in logs:
Logger: homeassistant.config_entries
Source: config_entries.py:575
First occurred: 8:53:44 PM (2 occurrences)
Last logged: 8:54:16 PM

Error occurred loading configuration flow for integration keymaster: No module named 'zwave_js_server'

Environment (please complete the following information):

OS: [e.g. HassOS/Raspbian/CentOS]  Ubuntu 20.04
Type of device: [e.g. RPi3/NUC/Synology] Server
Home Assistant version: [e.g. 0.105.5] 2021.4.4
Hassio/Docker/Core? Core
Component version: [e.g. 0.1.2] 0.0.31

Logs
Paste your error logs here.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Please add emails in plain/text format if possible and applicable.

Closing this as this just moved to zwavejs and working fine now (and won't be able to test any fixes).

hmm can't explain this by looking at the code. Will have to keep an eye out for the next report, thanks anyway!

This is happening to me as well and I'm not ready to move to zwavejs just yet. Any way I can help figure out the issue?


split BN plugin to a submodule?

Is it possible to split the BN plugin to a submodule? Currently subfolders aren't supported with the existing plugin manager and I'd be nice to have the plugin available for easy discovery in the plugin manager.

Very good point, thanks, we will do so shortly!

Awesome! That plus creating a release is all we need to add it to the plugin manager. 👍

Done, you can find it at https://github.com/fgsect/JMPscare-binja :)
I've created an issue in the community-plugins repo.
Please let us know if there's anything else for us to do and thanks for the heads-up again!


./collab-vm-server: error while loading shared libraries: libturbojpeg.so.0: cannot open shared object file: No such file or directory

Hi, Anyone know how to fix this?
log:
root@gunawan092w:~# mkdir collabvm-server
root@gunawan092w:~# cd ./collabvm-server/
root@gunawan092w:~/collabvm-server# cd ..
root@gunawan092w:~# cd ./collabvm-server/
root@gunawan092w:~/collabvm-server# wget https://github.com/computernewb/collab3/releases/download/1.2.11/collab-vm-server-debian-amd64.tar.gz
--2022-12-30 06:01:33--  https://github.com/computernewb/collab3/releases/download/1.2.11/collab-vm-server-debian-amd64.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/77417867/8d96c8a4-0594-491b-a425-e4ea8cc86e8b?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20221230%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20221230T060133Z&X-Amz-Expires=300&X-Amz-Signature=f7c378f73cf1af7faf54f5d5500e145a91ecd2a86ea3a2c9d27731328612f5e0&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=77417867&response-content-disposition=attachment%3B%20filename%3Dcollab-vm-server-debian-amd64.tar.gz&response-content-type=application%2Foctet-stream [following]
--2022-12-30 06:01:33--  https://objects.githubusercontent.com/github-production-release-asset-2e65be/77417867/8d96c8a4-0594-491b-a425-e4ea8cc86e8b?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20221230%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20221230T060133Z&X-Amz-Expires=300&X-Amz-Signature=f7c378f73cf1af7faf54f5d5500e145a91ecd2a86ea3a2c9d27731328612f5e0&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=77417867&response-content-disposition=attachment%3B%20filename%3Dcollab-vm-server-debian-amd64.tar.gz&response-content-type=application%2Foctet-stream
Resolving objects.githubusercontent.com (objects.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 761283 (743K) [application/octet-stream]
Saving to: 'collab-vm-server-debian-amd64.tar.gz'

collab-vm-server-debian-amd64 100%[=================================================>] 743.44K   982KB/s    in 0.8s

2022-12-30 06:01:34 (982 KB/s) - 'collab-vm-server-debian-amd64.tar.gz' saved [761283/761283]

root@gunawan092w:~/collabvm-server# tar
tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options
Try 'tar --help' or 'tar --usage' for more information.
root@gunawan092w:~/collabvm-server# tar -xf collab-vm-server-debian-amd64.tar.gz
root@gunawan092w:~/collabvm-server# ls
collab-vm-server  collab-vm-server-debian-amd64.tar.gz  http
root@gunawan092w:~/collabvm-server# chmod 700 ./collab-vm-server
root@gunawan092w:~/collabvm-server# sudo ./collab-vm-server
./collab-vm-server: error while loading shared libraries: libturbojpeg.so.0: cannot open shared object file: No such file or directory
root@gunawan092w:~/collabvm-server#

Compile the server yourself, as the released binaries are from an older revision of 1.2.11 from early stages of development.
Details should be in the BUILDING.md in the root directory of the repository.


fix name for OpenShift service

With OCP 3.10 the service is now called atomic-openshift-node. This change will instruct to restart the correct service.

Closing as this is not the correct way of restarting master to pick up the changes on OCP 3.10.


register v0.1.1

@JuliaRegistrator register
Release notes:
Updated documentation and examples

Registration pull request created: JuliaRegistries/General/102143
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" 5ea542926b5d544a374fb0bc5b8fcab8be434796
git push origin v0.1.1


Chart endpoint not correctly downloading

Default options
aapl = iex("AAPL")
aapl.get_chart()

Returns

[]

Non-default options
aapl2 = iex("AAPL", chartRange='1d')

Returns

Traceback (most recent call last):
File "test.py", line 3, in
aapl = iex("AAPL", chartRange='1d')
File "/home/addison/Documents/iex/iexenv/lib/python3.5/site-packages/iexfinance/init.py", line 14, in IexFinance
inst = Share(symbol, **kwargs)
File "/home/addison/Documents/iex/iexenv/lib/python3.5/site-packages/iexfinance/init.py", line 39, in init
self.data_set = self.refresh()
File "/home/addison/Documents/iex/iexenv/lib/python3.5/site-packages/iexfinance/init.py", line 43, in refresh
data = super(Share, self)._fetch()
File "/home/addison/Documents/iex/iexenv/lib/python3.5/site-packages/iexfinance/iexretriever.py", line 215, in _fetch
raise ValueError("Not all endpoints downloaded")
ValueError: Not all endpoints downloaded

Thanks to Alessandro Visintin for pointing out this issue

Seems that there is an issue with the IEX API, where it does not download the chart endpoint in batch requests when chart is specified following other endpoints. See iexg/IEX-API#156  for further info (awaiting response from IEX at the moment)


[FLINK-20309][tests] Make source split assignment in UnalignedCheckpointITCase stable. [1.12]

Unchanged backport of #14655.

No changes and green AZP -> merging.

No changes and green AZP -> merging.


[SPARK-34544][PYTHON][FOLLOW-UP] Add pandas-stubs in dev/requirement.txt

What changes were proposed in this pull request?
This PR is a minor followup of https://github.com/apache/spark/pull/34927 that adds pandas-stubs dependency into dev/requirements.txt.
Why are the changes needed?
For easier development setup.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
Manually tested as below:
pip install -r dev/requirements.txt

cc @zero323 FYI

LGTM

Let me merge this one since this file is not actually tested and used anywhere in CI :-).

Merged to master.


change https to http in Faker Image to better performance

was changed https to http in Faker Image to better performance. See the examples in lorempixel.com

I don't see a reason why to do this. There is not that much performance overhead where the full web goes over ssl

yep, i did tests in my personal projects, some load in droplets and local, and without https, images load more faster. i'm not sure if servers are over ssl, 'cause the links examples are over http only.. but it's only my suggestion


refactor(ast_tools): one function to add header to generated files

Centralize logic for adding header to generated files.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6971  👈
#6970
#6957
#6956
#6954
#6953
#6952
#6951
#6950
#6949
#6948
#6947
#6946
#6945
#6944
#6943
#6942
#6941
#6940
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Merge activity

Oct 27, 8:26 PM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


python version

Hi there,
Can you verify that this buildpack only works with 2.x ?

The build pack installs the Agent package, which has self-contained
versions of software used.
This means that it should work with any Python version.
Are you having an issue?
On Monday, May 16, 2016, Scott McWhirter<EMAIL_ADDRESS>wrote:

Hi there,
Can you verify that this buildpack only works with 2.x ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/miketheman/heroku-buildpack-datadog/issues/16

Yes, I get
~/.apt/opt/datadog-agent $ exec /app/.apt/opt/datadog-agent/embedded/bin/python /app/.apt/opt/datadog-agent/agent/dogstatsd.py start
ImportError: No module named site

With ConnectionRefusedError: [Errno 111] Connection refused when attempting to connect to statsd.
This is with python-3.5.1 as the python version.

Can you show what version of the Agent package is installed? Also, what
other buildpacks are you running?
On Mon, May 16, 2016, 18:15 Scott McWhirter<EMAIL_ADDRESS>wrote:

Yes, I get
~/.apt/opt/datadog-agent $ exec /app/.apt/opt/datadog-agent/embedded/bin/python /app/.apt/opt/datadog-agent/agent/dogstatsd.py start
ImportError: No module named site
With ConnectionRefusedError: [Errno 111] Connection refused when
attempting to connect to statsd.
This is with python-3.5.1 as the python version.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/miketheman/heroku-buildpack-datadog/issues/16#issuecomment-219565049

just heroku/python and agent version datadog-agent 5.7.4

Can you paste the output of heroku buildpacks ?
On Mon, May 16, 2016, 18:24 Scott McWhirter<EMAIL_ADDRESS>wrote:

just heroku/python and agent version datadog-agent 5.7.4
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/miketheman/heroku-buildpack-datadog/issues/16#issuecomment-219566684

1. https://github.com/miketheman/heroku-buildpack-datadog.git
2. heroku/python

I can confirm and reproduce this behavior with a runtime.txt value of "python-3.5.1", and will continue to see what can be done.

It appears that this failure is being induced by the Python buildpack, which sets some environment variables in the startup profile that conflict with path loading.
$ cat .profile.d/python.sh
export PATH=$HOME/.heroku/python/bin:$PATH
export PYTHONUNBUFFERED=true
export PYTHONHOME=/app/.heroku/python
export LIBRARY_PATH=/app/.heroku/vendor/lib:/app/.heroku/python/lib:$LIBRARY_PATH
export LD_LIBRARY_PATH=/app/.heroku/vendor/lib:/app/.heroku/python/lib:$LD_LIBRARY_PATH
export LANG=${LANG:-en_US.UTF-8}
export PYTHONHASHSEED=${PYTHONHASHSEED:-random}
export PYTHONPATH=${PYTHONPATH:-/app/}

$ unset PYTHONHOME
$ .profile.d/run-dogstatsd.sh
2016-05-17 12:37:57,462 | INFO | dd.dogstatsd | utils.pidfile(pidfile.py:31) | Pid file is: /app/.apt/opt/datadog-agent/run/dogstatsd.pid
2016-05-17 12:37:57,463 | INFO | dd.dogstatsd | daemon(daemon.py:157) | Starting
2016-05-17 12:37:57,463 | INFO | dd.dogstatsd | daemon(daemon.py:171) | Pidfile: /app/.apt/opt/datadog-agent/run/dogstatsd.pid

The reason this works with the Python 2.x runtime is that the PYTHONHOME variable is telling the dogstatsd runner to use the buildpack's Python interpreter (2.7.x), and the Agent is using Python 2.7 - so the app and Agent can both can find the site.py module on startup.

@konobi I forgot to mention here that the fix for Python 3.x is in, please let me know if you have any issues with that now.


[Support Request] for anime-on-demand.de

Example URl: https://www.anime-on-demand.de/anime/161 (This link is the Mainpage of the Anime. Not the link to the Video)
It is necessary to register

Post an example URL.

There is no direct play link . But I have even copied the HTML INPUT tag .

geo-restricted?

You also have to provide account credentials if it requires paid subscription.

Can i send you the data via pm?

./youtube-dl https://www.anime-on-demand.de/anime/161 -u --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'https://www.anime-on-demand.de/anime/161', u'-u', u'--verbose']
Type account password and press [Return]:
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.02.13
[debug] Python version 2.7.3 - Linux-3.2.0-4-amd64-x86_64-with-debian-7.8
[debug] exe versions: none
[debug] Proxy map: {}
[AnimeOnDemand] Downloading login page
[AnimeOnDemand] Logging in as
[AnimeOnDemand] 161: Downloading webpage
[AnimeOnDemand] episode-1: Downloading playlist JSON
[AnimeOnDemand] episode-1: Downloading m3u8 information
ERROR: Failed to download m3u8 information: '' (caused by BadStatusLine("''",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "./youtube-dl/youtube_dl/extractor/common.py", line 354, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "./youtube-dl/youtube_dl/YoutubeDL.py", line 1905, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 401, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 419, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 379, in _call_chain
result = func(*args)
File "./youtube-dl/youtube_dl/utils.py", line 830, in https_open
req, **kwargs)
File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open
r = h.getresponse(buffering=True)
File "/usr/lib/python2.7/httplib.py", line 1034, in getresponse
response.begin()
File "/usr/lib/python2.7/httplib.py", line 407, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.7/httplib.py", line 371, in _read_status
raise BadStatusLine(line)

Currently they are switching from RTMP streams to HTML5 (beta). As kitokirisaki said an account is neccessary, but you can create a free one. The series following this link is completly free, so testing is possible: https://www.anime-on-demand.de/anime/162

It is possible to download episodes from AoD with youtube-dl. They are using .m3u8-playlists in the new HTML5-version, which are supported by youtube-dl.
You'll need to monitor the traffic, for example with Firefox. After starting the video, you'll get something like "playlist.m3u8?aodSecure_starttime" in the monitor, which can be used for some things, but is basically unusable for download. Under this entry, you'll get something like
"chunklist_w1601181907_b13568000_", this is a playlist on 56b60eb28ccee.streamlock.net:1936 (the streaming-server of AoD) which serves the Episode in "1080p+", which is a high-bitrate FHD-video in Blu-Ray-quality. Under that, you'll get other chunklists, the next should be "chunklist_w1601181907_b6400000_", which is the playlist for "normal" Full-HD. Under this, you'll get other chunklists with lower quality. Now copy the chunklist with your preferred resolution and open a terminal for youtube-dl. Enter "youtube-dl", then paste the chunklist-URL and set an output name with "-o [Filename]". The last step is required, because youtube-dl may be unable to set a short filename; so replace [Filename] with you preferred name (need to be without space in the title).
Then press enter, and youtube-dl will download the file. This may take some time, and a 20-minute episode will need between 1.2 and 1.9 GB of space in the highest resolution.
However, this is only possible with the HTML5-version. For more information, look at my screenshot.

Regards,
CTG

Currently they are switching from RTMP streams to HTML5

While the latest version (2016.04.13) of youtube-dl works fine for series with html5, I can't download any video which is streamed the classic way (without html5).
As far as I understand the code correctly (I'm not good with python) the animeondemand extractor looks for an input with "streamstarter_html5" in its class tag. The "classic" version however does not have this tag. It would be just "streamstarter" instead.
Here are two sites to verify:
HTML5 (works just fine for all episodes): https://www.anime-on-demand.de/anime/162
classic (just downloads the teasers): https://www.anime-on-demand.de/anime/137
I suggest a similar approach as there is for downloading the teasers: If no playlist item for html5 was found, then retry looking for the classic way.

Hi, the extractor for AnimeOnDemand  is still working great for HTML5-able episodes, though they changed the streaming format for desktop browsers recently.
Unfortunately, he isn't able to recognize movies like https://www.anime-on-demand.de/anime/175 or https://www.anime-on-demand.de/anime/178 , as they aren't listed like episodes.


Fix arrays over multiple lines (CR/LF issue)

Since STRING_LITERAL didn't exclude \r, if an \r followed it, it was getting picked up into the literal. Fixes #489

It included test additions, auto-generated files, plus some debugging improvements that were unintentionally from another PR. Thanks.


Fix unwanted side effect in FutureUtils.timeoutTo (#695)

Fix for #695
To eliminate the possibility of race condition I moved fallback evaluation after promise resolving. It will lead to some overhead (extra Either allocation and flatMap on future), but I didn't find any better way to guarantee to fix the problem.
I added 2 test cases. First is pretty simple - just check that side-effect is not evaluated when future finished earlier than timeout. I placed it in the shared tests.
The second one is a lot more interesting. I placed it on the JVM tests because this issue is reproducible only in environments with the real multithreading. This test runs on a real thread pool and tries to adjust timeout to find race condition. And when this race condition is found, it checks that the number of errors and side-effect evaluations is the same. This test is non-deterministic and takes some time to find race condition, but with this test, I was able to reproduce issue from #695 before this fix.

No, looks good.


Many different connections for a single worker

Running a single worker causes many different sessions inside ActiveMQ

Experiencing this when a --timeout is supplied, but without timeout this is not the case and the session keeps the same. However, there is only once a connection established (the isConnected() returns correctly true when the timeout loop is passed). Apparently somewhere else in the queue process loop there is a consumer added for every single iteration in the loop. When the worker exists, all consumers on this connection are immediately closed.


constexpr & __shfl errors

Cuda 8.0
Cudnn 5.1
Tensorflow
My Makefile has been modified to what @Iamanorange suggested in  issue #28
I get the following errors when running "make all" in the flownet2-tf folder:
nvcc --expt-relaxed-constexpr -g -std=c++11 -I python -c "import tensorflow; print(tensorflow.sysconfig.get_include())" -I"/usr/local/cuda/.." -DGOOGLE_CUDA=1 -D_MWAITXINTRIN_H_INCLUDED -D_FORCE_INLINES -D__STRICT_ANSI__ -D_GLIBCXX_USE_CXX11_ABI=0 -c  src/ops/preprocessing/kernels/data_augmentation.cu.cc -x cu -Xcompiler -fPIC  -o src/ops/build/data_augmentation.o
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
/usr/local/lib/python2.7/dist-packages/tensorflow/include/absl/strings/string_view.h(496): error: constexpr function return is non-constant
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(55): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(309): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(310): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(138): error: identifier "__shfl" is undefined
/usr/local/lib/python2.7/dist-packages/tensorflow/include/absl/strings/str_cat.h(259): error: expression must have a constant value
/usr/local/lib/python2.7/dist-packages/tensorflow/include/absl/strings/str_cat.h(259): error: expression must have a constant value
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(651): warning: missing return statement at end of non-void function "Eigen::internal::igammac_cf_impl<Scalar, mode>::run [with Scalar=float, mode=Eigen::internal::VALUE]"
detected during:
instantiation of "Scalar Eigen::internal::igammac_cf_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::VALUE]"
(855): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::VALUE]"
(2096): here
instantiation of "Eigen::internal::igamma_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma(const Scalar &, const Scalar &) [with Scalar=float]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsHalf.h(34): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(712): warning: missing return statement at end of non-void function "Eigen::internal::igamma_series_impl<Scalar, mode>::run [with Scalar=float, mode=Eigen::internal::VALUE]"
detected during:
instantiation of "Scalar Eigen::internal::igamma_series_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::VALUE]"
(863): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::VALUE]"
(2096): here
instantiation of "Eigen::internal::igamma_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma(const Scalar &, const Scalar &) [with Scalar=float]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsHalf.h(34): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(651): warning: missing return statement at end of non-void function "Eigen::internal::igammac_cf_impl<Scalar, mode>::run [with Scalar=float, mode=Eigen::internal::DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igammac_cf_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::DERIVATIVE]"
(855): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::DERIVATIVE]"
(2102): here
instantiation of "Eigen::internal::igamma_der_a_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma_der_a(const Scalar &, const Scalar &) [with Scalar=float]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsHalf.h(38): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(712): warning: missing return statement at end of non-void function "Eigen::internal::igamma_series_impl<Scalar, mode>::run [with Scalar=float, mode=Eigen::internal::DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igamma_series_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::DERIVATIVE]"
(863): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::DERIVATIVE]"
(2102): here
instantiation of "Eigen::internal::igamma_der_a_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma_der_a(const Scalar &, const Scalar &) [with Scalar=float]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsHalf.h(38): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(651): warning: missing return statement at end of non-void function "Eigen::internal::igammac_cf_impl<Scalar, mode>::run [with Scalar=float, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igammac_cf_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(855): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(2108): here
instantiation of "Eigen::internal::gamma_sample_der_alpha_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::gamma_sample_der_alpha(const Scalar &, const Scalar &) [with Scalar=float]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsHalf.h(42): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(712): warning: missing return statement at end of non-void function "Eigen::internal::igamma_series_impl<Scalar, mode>::run [with Scalar=float, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igamma_series_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(863): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=float, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(2108): here
instantiation of "Eigen::internal::gamma_sample_der_alpha_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::gamma_sample_der_alpha(const Scalar &, const Scalar &) [with Scalar=float]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsHalf.h(42): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(651): warning: missing return statement at end of non-void function "Eigen::internal::igammac_cf_impl<Scalar, mode>::run [with Scalar=double, mode=Eigen::internal::VALUE]"
detected during:
instantiation of "Scalar Eigen::internal::igammac_cf_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::VALUE]"
(855): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::VALUE]"
(2096): here
instantiation of "Eigen::internal::igamma_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma(const Scalar &, const Scalar &) [with Scalar=double]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/arch/CUDA/CudaSpecialFunctions.h(120): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(712): warning: missing return statement at end of non-void function "Eigen::internal::igamma_series_impl<Scalar, mode>::run [with Scalar=double, mode=Eigen::internal::VALUE]"
detected during:
instantiation of "Scalar Eigen::internal::igamma_series_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::VALUE]"
(863): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::VALUE]"
(2096): here
instantiation of "Eigen::internal::igamma_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma(const Scalar &, const Scalar &) [with Scalar=double]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/arch/CUDA/CudaSpecialFunctions.h(120): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(651): warning: missing return statement at end of non-void function "Eigen::internal::igammac_cf_impl<Scalar, mode>::run [with Scalar=double, mode=Eigen::internal::DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igammac_cf_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::DERIVATIVE]"
(855): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::DERIVATIVE]"
(2102): here
instantiation of "Eigen::internal::igamma_der_a_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma_der_a(const Scalar &, const Scalar &) [with Scalar=double]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/arch/CUDA/CudaSpecialFunctions.h(135): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(712): warning: missing return statement at end of non-void function "Eigen::internal::igamma_series_impl<Scalar, mode>::run [with Scalar=double, mode=Eigen::internal::DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igamma_series_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::DERIVATIVE]"
(863): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::DERIVATIVE]"
(2102): here
instantiation of "Eigen::internal::igamma_der_a_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::igamma_der_a(const Scalar &, const Scalar &) [with Scalar=double]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/arch/CUDA/CudaSpecialFunctions.h(135): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(651): warning: missing return statement at end of non-void function "Eigen::internal::igammac_cf_impl<Scalar, mode>::run [with Scalar=double, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igammac_cf_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(855): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(2108): here
instantiation of "Eigen::internal::gamma_sample_der_alpha_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::gamma_sample_der_alpha(const Scalar &, const Scalar &) [with Scalar=double]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/arch/CUDA/CudaSpecialFunctions.h(154): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/SpecialFunctionsImpl.h(712): warning: missing return statement at end of non-void function "Eigen::internal::igamma_series_impl<Scalar, mode>::run [with Scalar=double, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
detected during:
instantiation of "Scalar Eigen::internal::igamma_series_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(863): here
instantiation of "Scalar Eigen::internal::igamma_generic_impl<Scalar, mode>::run(Scalar, Scalar) [with Scalar=double, mode=Eigen::internal::SAMPLE_DERIVATIVE]"
(2108): here
instantiation of "Eigen::internal::gamma_sample_der_alpha_retval<Eigen::internal::global_math_functions_filtering_base<Scalar, void>::type>::type Eigen::numext::gamma_sample_der_alpha(const Scalar &, const Scalar &) [with Scalar=double]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/unsupported/Eigen/CXX11/../src/SpecialFunctions/arch/CUDA/CudaSpecialFunctions.h(154): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(242): error: identifier "__shfl" is undefined
detected during instantiation of "T tensorflow::CudaShuffleSync(unsigned int, T, int, int) [with T=unsigned int]"
(253): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(270): error: identifier "__shfl_up" is undefined
detected during instantiation of "T tensorflow::CudaShuffleUpSync(unsigned int, T, unsigned int, int) [with T=unsigned int]"
(282): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(299): error: identifier "__shfl_down" is undefined
detected during instantiation of "T tensorflow::CudaShuffleDownSync(unsigned int, T, unsigned int, int) [with T=unsigned int]"
(311): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(328): error: identifier "__shfl_xor" is undefined
detected during instantiation of "T tensorflow::CudaShuffleXorSync(unsigned int, T, int, int) [with T=unsigned int]"
(340): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(242): error: identifier "__shfl" is undefined
detected during instantiation of "T tensorflow::CudaShuffleSync(unsigned int, T, int, int) [with T=tensorflow::uint16]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(74): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(270): error: identifier "__shfl_up" is undefined
detected during instantiation of "T tensorflow::CudaShuffleUpSync(unsigned int, T, unsigned int, int) [with T=tensorflow::uint16]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(80): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(299): error: identifier "__shfl_down" is undefined
detected during instantiation of "T tensorflow::CudaShuffleDownSync(unsigned int, T, unsigned int, int) [with T=tensorflow::uint16]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(86): here
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(328): error: identifier "__shfl_xor" is undefined
detected during instantiation of "T tensorflow::CudaShuffleXorSync(unsigned int, T, int, int) [with T=tensorflow::uint16]"
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(92): here
12 errors detected in the compilation of "/tmp/tmpxft_00001547_00000000-7_data_augmentation.cu.cpp1.ii".
Makefile:63: recipe for target 'preprocessing' failed
make: *** [preprocessing] Error 2
Any help is appreciated.

Add -DNDEBUG to CFLAGS.
 Consider update them.

Added -DNDEBUG to CFLAGS. However this only rids one of the 12 errors. I still get the:
error: identifier "__shfl" is undefined

Try to build with CUDA 9.x

Upgrading to Cuda 9.2 did the trick. Thank you very much for the help.