[web-pubsub-client] Add a browser sample and fix some bugs

Packages impacted by this PR
web-pubsub-client
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Layout.clear doesn't remove all child controls in Maya 2018

I'm dynamically generating controls under a VerticalForm.  I've been trying to use the form's clear() method when I need to refresh the UI, but some of the controls aren't removed.  I tried poking around in the code, and it looks to me like the culprit is the generator expression in mgui/core/init.py line 350.  It looks like it's removing controls from the list as it's reading from the list, and some controls get skipped as a result.
Replacing the generator expression with a list seems to work.  I'll create a pull request with that change.

Good catch.
Yeah the generator expression is just relying on the underlying list, which we are rather wrongfully mutating during iteration.

hey @bob-white  do we have test coverage for that behavior? it not it would be a good addition

Good call.
Do we have a a decent way of representing the controls and the control hierarchy in unit tests?
Or would we need to mock up some of the ui cmds to not return False?

Generally I have been relying on mocks by replacing the cmds call with a dummy object that does what we need.

reclosing


bug: Unable to update lazyvim

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.0
Operating system/version
Endeavour OS
Describe the bug
Hello,
I am unable to update lazyvim from the UI.
There are no additional config I have made or any changes that will prevent the OS from having an internet connection.
In fact the only plugin I have installed is Venn but the issue existed before I installed this plugin.
A point of interest is that this installation (machine, OS , et all ) is less than a week old as I received a laptop from RMA recently. My other machine which runs a similar setup is working perfectly fine and I can update lazyvim from within the UI.. No problems there.
I see the message "Could not resolve host : github.com". But I am able to access github from within the browser as is evident from me opening this issue on the same machine.
Further, I can also see from my ad blocker running on my DNS server that all the requests going to github are processed and not filtered / blocked in any manner.
I was wondering if anyone else is facing this issue or if I m missing some rather obvious steps.
Please find screenshots of lazyvim and my ad blocker

Steps To Reproduce

Open neovim
Press Leader + l
Press U

Expected Behavior
I expect to see that lazyvim updates the plugins
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Sorry, but there's literally nothing I can do about this. Lazy just spawns a git process that doesn't seem to be able to connect to github. You'll have to figure this out yourself.

I understand.. Its much less of a bug and more of a troubleshooting request..
If it is not too much trouble, can you suggest how I can go about troubleshooting it further.
I can ping github from the command line and I can access it in the browser..
I can clone and push and pull from the command line just fine - with or without credentials.
I m unable to see what could be the underlying issue just on nvim..

no idea. this is clearly a networking issue on your computer. maybe check your firewall?

Thanks.. I ll check..
Its as good as a starting point anyway.. :-)
Thanks again for the help!

Fixed it... For anyone else running into the same issue.
It was the DNS server. The homelab's ad guard DNS server was causing the issue..
A combination of the actual upstream DNS server and rate limiting was causing the issue.

Had the same problem, increasing the rate limit worked

Wow @krish2487 I had exact same issue - turned out I had a rate-limit set to 20/sec per client.. Curious if AdGuard does this by default, but setting it to 0 helped instantly!


Cannot find a way to catch Error: Another hypercore is stored here error

When creating a new database, if you erroneously try to create a new database over an existing one, you get Error: Another hypercore is stored here. However, I can find no way of catching this error so that I can handle it gracefully when using hyperdb.

Just fs.stat the DB folder before attempting to create the new db.
On Sat, Feb 16, 2019, 10:23 Aral Balkan<EMAIL_ADDRESS>wrote:

When creating a new database, if you erroneously try to create a new
database over an existing one, you get the Error: Another hypercore is
stored here. However, I can find no way of catching this error so that I
can handle it gracefully.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mafintosh/hyperdb/issues/164, or mute the thread
https://github.com/notifications/unsubscribe-auth/ANY6RmmcFPhd3IL-iA-o3NP67V4dcGBcks5vN9wngaJpZM4a-6hr
.

@m-onz Sorry, I should’ve been more precise: this is with random-access-idb in the browser and, afaics, there doesn’t seem to be a reliable way to see if an IndexDB database exists or not (!!!)

I've used hyperdb in the browser... Using substacks lib. The DB name
creates a key from your DB name.. Surely you can check that exists. I think
supplying the DB key as the second argument of the constructor each time
might work too.
On Sat, Feb 16, 2019, 17:01 Aral Balkan<EMAIL_ADDRESS>wrote:

@m-onz https://github.com/m-onz Sorry, I should’ve been more precise:
this is with random-access-idb in the browser and, afaics, there doesn’t
seem to be a reliable way to see if an IndexDB database exists or not (!!!)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mafintosh/hyperdb/issues/164#issuecomment-464362876,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANY6Rtr6KH6-dEgWsqpTRC_X4Cr3Jpb7ks5vODlPgaJpZM4a-6hr
.

Regarding my previous point: https://stackoverflow.com/a/23767548

I was running into this too and decided to use the discovery key so you can store multiple dats:
var crypto = require('hypercore-crypto')
var db = require('random-access-idb')

var key = 'dat://somedatkey'

var discoveryKey = crypto.discoveryKey(key)
var archive = hyperdrive(db(discoveryKey.toString('hex')), key)

Also, you could store your DB name in local storage or as a cookie.
Bit crude but its a work around.


Close non-persistent HTTPS connections

For instance, connections with the "Connection: close" header. Currently, if the client uses this header to signal a non-persistent connection and waits for the connection to be closed, it will hang indefinitely. This change closes these connections after processing the first HTTP request.

Thanks, look right.
Care to add a small test?

I ran into a little trouble testing this and haven't had time revisit it. Happy for someone else to pick this up, or I can close out the pull request for now.
Let me know which you'd prefer.

Superseded by https://github.com/elazarl/goproxy/pull/514 which added the requested test case.

@hmarr / @elazarl I think this PR should be closed based on https://github.com/elazarl/goproxy/pull/514#issuecomment-1874561092

Thanks @jeffwidman!


Errors reported in async mode trigger error overlays in v5

Current behavior
Starting from the v5 this plugin seems to add all reported issues to the compilation.errors list when webpack-dev-server is used, apparently to resolve #180.
However this change has an (unintended?) side effect - it makes error overlay plugins consider reported issues as build errors and block the app view. This behavior can be observed with devServer.overlay, error-overlay-webpack-plugin, react-refresh-webpack-plugin, and I think it might be the case with create-react-app's builtin overlay once it upgrades this plugin to v5.
Expected behavior
Personally I find the new behavior problematic. I'd like error overlay to show errors that actually break the application, for the same reason why TypeScript's noEmitOnError option is false by default.
Option 1
Add an option to enable (or disable?) the new behavior. This would be easy to implement and to configure, however it might be a little hacky (these issues are valid errors, so it makes sense for them to be included in compilation.errors?).
Option 2
Add an option to override severity of all issues reported by the plugin. This also would be easy to implement, however it removes the visual distinction between errors and warnings.
Option 3
Don't change anything in the plugin, but document this behavior and document way to ignore these errors on overlay level. It sounds like the best solution conceptually, however AFAIK none of the overlays have an option to ignore certain errors, and that might make configuration more complex.
Steps to reproduce the issue
// webpack.config.js
const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');

module.exports = {
  resolve: { extensions: ['.ts', '.js'] },
  module: {
    rules: [
      {
        test: /\.ts$/,
        use: [{ loader: 'ts-loader', options: { transpileOnly: true } }],
      },
    ],
  },

  devServer: {
    hot: true,
    // Reproduction 1:
    // overlay: true,
  },

  plugins: [
    new ForkTsCheckerWebpackPlugin(),

    // Reproduction 2:
    // new (require('error-overlay-webpack-plugin'))(),

    // Reproduction 3:
    // new (require('@pmmmwh/react-refresh-webpack-plugin'))(),
  ],
};

// src/index.ts
const test: string = 0;

Environment

fork-ts-checker-webpack-plugin: 5.0.13
typescript: 3.9.7
webpack: 4.44.1
webpack-dev-server: 3.11.0
error-overlay-webpack-plugin: 0.4.1
@pmmmwh/react-refresh-webpack-plugin: 0.4.1

I would go with option 1 - I think it should be enabled by default :) It should be easy to implement - one if in https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/blob/master/src/hooks/interceptDoneToGetWebpackDevServerTap.ts + configuration. Would you like to create PR?

I'm also keen to see this added as an option. @piotr-oles Is #496 along the lines of what you were thinking?

Would love to see this option! Type errors breaking compile can be very distracting =)

Was resolved in #496, thanks @edhollinghurst!


Refactor the Heading button section, in order to put a chat button in there

There is a problem here, @edsaperia I need your help:

Each heading contains two buttons right now:
1/ # for copying the id of the heading into the clipboard.
2/ A toggle button, which is for folding and unfolding the section
Where should I add a new button for the chat? How should these three buttons be arranged?

1/ Heading id should go into the address bar when you click on the heading in the table of contents. No need for a button to copy onto clipboard.
2/ Toggle button stays as it is, but should only be visible on hover (see https://github.com/docs-plus/docs.plus/issues/39)
3/ Chat icon should be to the right of the heading in the margin of the document. If there are no unread chats, it should be a chat bubble, if there are unread chats it should be a number in a circle.

Unread chats should also be shown in the table of contents in circles, similar to slack:

note that the designs of the icons are approximate - the images above just indicate the locations of the buttons.


BUG: fix issues with wheel tags, and add more tests to cover tags

Closes gh-141

Also, CI seems to be unhappy.

More Mypy buggy-ness:
mesonpy/__init__.py:839: error: Returning Any from function declared to return "bool"  [no-any-return]
``
This works fine locally on both Linux and macOS, and the code is correct - just a little complicated with property decorators:(

More Mypy buggy-ness:

It depends on the exact Mypy version and the minor version of Python ... sigh. On Python 3.9 this error disappears, and another one appears. Guess we have to live with it, Mypy isn't going to mature any time soon.

This was all green modulo the mypy issue, the last commit should fix that.

This is happy, in it goes. Thanks @FFY00!

Thanks for all the work on getting this PR ready for merging. For next time, I'd prefer PRs that do multiple things to be rebase-merged, instead of squashed, the rule I try to abide by is one commit per logical change. In case you are not used to this kind of workflow, I recommend using fixup commits if you need to modify commits, as explained in https://openinput.readthedocs.io/en/latest/contributing/index.html#workflow. Thanks :blush:

Sure, that is a good idea in most cases. I am familiar with it, will aim to rebase-merge where possible.
In cases where it would break git bisect it may be a bit questionable though, then it's more of a judgement call and squash-merge or a merge commit may be more helpful.

Thanks! All commits being self-contained is also something I strive to achieve, so in this workflow you would apply the fixes needed to the PR to each respective commit.


Read-only raspberry filesystem

Study how to do it in a simple way. There are some recipes in internet:
http://hallard.me/raspberry-pi-read-only/

It has been done almost as the guide says. I have put all logfiles into /tmp but the system stills with write flag on, so you can write things easily. It is important to note that any new software which needs to write togs should be redirected to /var/tmplog in order to put them into /tmp. This way any log will be written to memory instead of SD card. The same should be done with databases and similar software.


Issue #8195: Set FocusColor on Text Input Elements and selected ListItem

Description
Issue #8195: Added new Property "FocusColor" to set the Color of the MudAutocomplete, MudNumericField, MudSelect and MudText when Focused. The Color was always "Color.Primary" so it wouldn't fit in with other Components in a Form - like MudSlider - that have a different Color.
The Change is concluded by adding new CSS classes and setting the Property in different Components. The Border Color is changed as well as the MudInputLabel Text Color. For MudSelect the new Property is "SelectedColor". In MudItem the new Property is "Color", corresponding to the TextColor.
For MudItem and MudSelect the Color is set with MudText with the existing Property.
How Has This Been Tested?
UnitTest: Test all Color CSS Classes with MudText. Check if the classes are set by altering the FocusColor Property.
Visually: New TextInputFocusColorTest.razor Page in Unittests.Viewer. Test all four Elements with different Variants. Also tested, that the selected Item in MudSelect and Autocomplete have the correct Color.
Types of changes

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

Before:

After:

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Hi @ScarletKuro, thanks for the Review.
I will try to find another Solution and move FocusColor Property out of MudComponentbase.

@ScarletKuro, i moved the FocusColor out of MudComponentBase - Autocomplete, Select, Numeric and Textfield now have it. For MudItem the Property is "Color" for the Text. In MudSelectItem the new Property is "SelectedColor", to define what color it will have, if selected.

@ArkEcho Thanks for the contribution but we decided not to add this.
Mainly because its not a feature sought-after enough and have high impact of components changed.
The color can still be changed by changing the themes primary and in special cases where another color is needed apart from the themes primary color you can write a custom a custom css class that takes care of it for you.

@Garderoben
The Idea was that Blazor/C# developers that weren't that familiar with custom CSS (like me) could change it simply by setting a Property. Finding the right property to overwrite was especially difficult for the FocusColor, because it is a pseudo css class. Only by looking at the scss class in the Sources I could find it.

I just do not understand why this was not brought in if someone has done all the work for it @Garderoben .  I would say it is definitely needed to be able to control the theme in the app, so is the logic here that we should be controlling this with the theme overrides?

@justcoder1 I believe that in Material Design inputs should always follow the primary color except red for a form error.

Hi @danielchalmers I think you are suggesting as I asked, that you should control the input colors with the theme palate i.e. if you want you primary color to be "yellow" then you should adjust this in your overrides and then your inputs will match your primary colour? thanks

Hi @danielchalmers I think you are suggesting as I asked, that you should control the input colors with the theme palate i.e. if you want you primary color to be "yellow" then you should adjust this in your overrides and then your inputs will match your primary colour? thanks

@justcoder1 You can change your theme colors in the theme provider, see here: https://mudblazor.com/customization/overview#custom-themes.
<MudThemeProvider Theme="MyCustomTheme" />
@code{
    MudTheme MyCustomTheme = new MudTheme()
    {
        PaletteLight = new PaletteLight()
        {
            Primary = Colors.Yellow.Default,
        },
        PaletteDark = new PaletteDark()
        {
            Primary = Colors.Yellow.Lighten1
        }
    };
}

Please let me know if that helps or not!

Thanks @danielchalmers and this does help and clarifies things, thanks


:bug: fix(inject): load local resource

not allowed to load local resource.
the URL should be started by 'vscode-file://vscode-app/'
I have not tested this and it may not work.

Thanks for the contribution, will test this and merge if there are no issues.

well, I got an error when I test it.
ERR XHR failed: Download: XHR failed

well, it does not worked when I test it.

I was wrong, it was working.
The thing to note is that there must be only one space between vscode-app and the path, and it must be the / symbol and not the \ symbol.
vscode-file://vscode-app/path/to/file

I’ve actually tried using your solution while I was trying to fix this bug, and it did work, but there was still a CSP rule preventing loading JS/CSS files from outside of the app’s folders. I went for a different solution instead, where Vibrancy will read the JS/CSS contents directly and embed them in style/script tags, which seems to work just as well.


Improving the design of long proposals when collapsed

Now a "Show more" link is displayed
Avoid to collapse proposals only a few pixels longer

Fixes #167

I made some rebase, but is now done!

There is a way to collapse a proposal that was expanded?

@tarsisazevedo, there is no way to collapse again, only by refreshing!
I think would be ugly a explicit "Hide text" link in the end of each proposal. I gave other reasons in my comments on #167.

@tarsisazevedo i asked him to not do the collapse back action.

Hello, this PR will get approval?

@wagnerluis1982 there are a pending review on the https://github.com/luanfonceca/speakerfight/pull/181/files

Curiosity: why the review came as a screenshot? This is normal on GitHub?

@luanfonceca, I tried to put JS gettext as
self.after("
" + gettext('Show more') + "
");

but when I call makemessages -l pt_BR, the string is not added to .po file. It was due to this that I opted to use {% trans ...}.
I'm not sure why the string isn't considered but I guess that's because it is in a template file, not in a static javascript file.

I just remembered that you need to run a different command:
python manage.py makemessages -d djangojs --all
It will look up on the djangojs domain and create all the translations messages, after that you will open the djangojs.po in the poedit like you did with the django.po.

@luanfonceca I discovered that makemessages doesn't take in consideration calls to JS gettext inside templates. If I add an entry manually to the djangojs.po, the translation works, but in the next call to makemessages the entry will be removed.
Then, it seems the only way is to move the code to an external JS file. May I do?


[Proposal] Road to first class ES6 Modules support

I am aware of ember-appkit-rails https://github.com/dockyard/ember-appkit-rails but want to tease out some of the essential differences and see how ember-rails should/could move forward. And gauge what the current thinking is for everyone.
It may be that there should be a middle project between ember-appkit-rails and ember-rails to address some of the thinking below. But want to explore the viability of doing some of this work in ember-rails.
Below are some thoughts on what that might be. What the features and use cases might need to be.
Generate Ember App Kit stye ES6 syntax out of the box.

bootstrap generator includes loader, jj-abrams resolver and es6 transpiler in project source
generators produce es6 style code (export to default, etc)

This behavior should probably sit behind configuration flag  to avoid breaking compatibility with existing projects that use Global variables for ember app.
Double MVC problem
Many existing rails apps are not greenfield, and therefore would like to ease gently into ember development. I think for many this means easily being able to have rails views and ember views live in harmony. Eschew some of the SPA bias. Provide some documentation and sensible configuration options that help with this.

provide for bootstrap generator that enables the judicious use of rootElement option in Ember.Application.create()
potentially get ember bootstrapping out of application.js and optionally configure for ember_application.js that can be selectively included on some subset of pages.
Should we be working to bridge the divide between "document centric" page development and SPA application development? Fighting two concepts of routing can be a bit of a struggle for people new to ember.

Portability of Ember Code and Code Generation
One of the great things about ES6 Modules is the way that they lend themselves to highly modular and portable code patterns. Easy to move bits of code around add a require import and boom ready to go.
I could image a common division of labor where pure client side work is done outside of a rails project (ember app kit and api stubs) and then easily included into rails project.
How might ember rails facilitate this work flow? Maybe a rake task that can analyze an EAK project and import code into rails project?
Integrate with future ember cli and ability to shell out to external tools for generation.
A more abstract concept of ember generators that work across tooling environments and workflows (node, rails, etc).
Multiple Ember Applications
Large preexisting rails apps might not easily be able to embrace the SPA concept.
A potential way to ameliorate this effort would be to have multiple "mini" ember applications within a larger rails project. Common backend models and rails generated json but multiple frontend modules that cover discrete areas of functionality within a large rails app space.

Support for multiple "project" folders within the asset pipeline, each conforming to an EAK style project hierarchy

app/javascripts/
  ember-app-one/
  .../models
 .../templates
 .../routes
 .../controllers
 ... etc...

  ember-app-two/
  .../models
 .../templates
 .../routes
 .../controllers
 ... etc...

and so on

Maybe through configuration the generators can be project aware and an extra flag added that "just works" and puts the generated ember code in the right place.
Perhaps the up coming "pods" concept will help with this process.
For common functionality shared across projects (stuff like components) it seems like the ES6 modules approach will allow things to be very DRY when they need to be.
Thoughts? If this is way outside the scope of ember rails feel free to close issue.

This is finished by https://github.com/emberjs/ember-rails/pull/416


fastlane pilot upload error when trying to uploading the IPA file to the App Store

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I was using Azure DevOps's Apple App Store Release pipeline to upload IPA file to the App Store, and running into the following error when executing "fastlane pilot upload" command.
2020-04-27T15:44:59.2852120Z /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:175:in ensure in require': CRITICAL: RUBYGEMS_ACTIVATION_MONITOR.owned?: before false -> after true (RuntimeError) 2020-04-27T15:44:59.2855050Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:175:in require'
2020-04-27T15:44:59.2856870Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:230:in finish_resolve' 2020-04-27T15:44:59.2858720Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:297:in block in activate_bin_path'
2020-04-27T15:44:59.2860400Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:295:in synchronize' 2020-04-27T15:44:59.2862020Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:295:in activate_bin_path'
2020-04-27T15:44:59.2863480Z 	from /usr/local/bin/fastlane:23:in `'
2020-04-27T15:44:59.3050400Z ##[error]Error: fastlane failed with return code: 1
Command executed
fastlane pilot upload -u *** -i /Users/user/Downloads/vsts-agent-osx-x64-2.165.2/_work/r2/a/TestApp iOS/drop/TestApp/TestAppiOS.ipa -a com.ipathsystem.TestApp
Complete output when running fastlane, including the stack trace and command used
2020-04-27T15:44:14.0182700Z ##[section]Starting: Publish TestApp to the App Store TestFlight track
2020-04-27T15:44:14.0195280Z ==============================================================================
2020-04-27T15:44:14.0195710Z Task         : Apple App Store Release
2020-04-27T15:44:14.0196090Z Description  : Release an app to TestFlight or the Apple App Store
2020-04-27T15:44:14.0196440Z Version      : 1.158.0
2020-04-27T15:44:14.0196730Z Author       : Microsoft Corporation
2020-04-27T15:44:14.0198110Z Help         : More Information
2020-04-27T15:44:14.0198670Z ==============================================================================
2020-04-27T15:44:14.6885030Z c01c02bc-af94-408f-ac90-e6c3c5a5d22b exists true
2020-04-27T15:44:14.7074530Z [command]/usr/local/opt/ruby/bin/gem install fastlane
2020-04-27T15:44:14.7565140Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7566920Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7570030Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7572420Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7574910Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7577280Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7579440Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7582310Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7585000Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7590110Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7593670Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7596080Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7599540Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7600910Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7602020Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7603190Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7604410Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7605710Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7685300Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7688110Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7689700Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7691020Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7692370Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7693690Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7694920Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7696070Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7697210Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7698370Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:14.7699420Z (node:8951) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-27T15:44:22.0417070Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:22.0419330Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/rouge-2.0.7.gemspec:17.
2020-04-27T15:44:28.8162880Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:28.8166540Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/excon-0.59.0.gemspec:19.
2020-04-27T15:44:29.2221030Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:29.2222410Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/highline-1.7.8.gemspec:20.
2020-04-27T15:44:29.2242570Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:29.2243850Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:29.2247960Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:29.2249230Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:39.4912580Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:39.4913890Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/excon-0.59.0.gemspec:19.
2020-04-27T15:44:39.4915120Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:39.4916230Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/highline-1.7.8.gemspec:20.
2020-04-27T15:44:40.2797780Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:40.2799210Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/rouge-2.0.7.gemspec:17.
2020-04-27T15:44:41.6613120Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6615090Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:41.6616710Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6617860Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:41.6620990Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6622450Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:41.6624590Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6625810Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:41.6630490Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6631930Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:41.6639840Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6642520Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:41.6644760Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6647020Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:41.6653220Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6657390Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:41.6690800Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6692280Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:41.6694400Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6696530Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:41.6702880Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6704180Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:41.6707780Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6709030Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:41.6713600Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:41.6714940Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:42.1998960Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:42.2000320Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/multipart-post-2.0.0.gemspec:17.
2020-04-27T15:44:44.9321840Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:44.9323150Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/rouge-2.0.7.gemspec:17.
2020-04-27T15:44:53.9013200Z Successfully installed fastlane-2.146.1
2020-04-27T15:44:53.9014650Z Parsing documentation for fastlane-2.146.1
2020-04-27T15:44:53.9015370Z Done installing documentation for fastlane after 9 seconds
2020-04-27T15:44:53.9015940Z 1 gem installed
2020-04-27T15:44:54.0372200Z [command]/usr/local/opt/ruby/bin/gem update fastlane -i /Users/user/.gem-cache
2020-04-27T15:44:54.3568410Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:54.3570000Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/rouge-2.0.7.gemspec:17.
2020-04-27T15:44:54.4235150Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:54.4236510Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/excon-0.59.0.gemspec:19.
2020-04-27T15:44:54.4730110Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:54.4732300Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/highline-1.7.8.gemspec:20.
2020-04-27T15:44:54.4753830Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:54.4755370Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:54.4759350Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:54.4761260Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:54.9982490Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:54.9983810Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/rouge-2.0.7.gemspec:17.
2020-04-27T15:44:55.0731160Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:55.0733440Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/excon-0.59.0.gemspec:19.
2020-04-27T15:44:55.1290040Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:55.1291390Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/highline-1.7.8.gemspec:20.
2020-04-27T15:44:55.1310670Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:55.1311900Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/little-plugger-1.1.4.gemspec:18.
2020-04-27T15:44:55.1314800Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:55.1315960Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/logging-2.2.2.gemspec:18.
2020-04-27T15:44:58.5394070Z Updating installed gems
2020-04-27T15:44:58.5394500Z Nothing to update
2020-04-27T15:44:58.5728930Z [command]fastlane pilot upload -u *** -i /Users/user/Downloads/vsts-agent-osx-x64-2.165.2/_work/r2/a/TestApp iOS/drop/TestApp/TestAppiOS.ipa -a com.ipathsystem.TestApp
2020-04-27T15:44:58.7945160Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:58.7946770Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/rouge-2.0.7.gemspec:17.
2020-04-27T15:44:58.8204740Z NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
2020-04-27T15:44:58.8207900Z Gem::Specification#rubyforge_project= called from /Users/user/.gem-cache/specifications/highline-1.7.8.gemspec:20.
2020-04-27T15:44:59.2852120Z /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:175:in ensure in require': CRITICAL: RUBYGEMS_ACTIVATION_MONITOR.owned?: before false -> after true (RuntimeError) 2020-04-27T15:44:59.2855050Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:175:in require'
2020-04-27T15:44:59.2856870Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:230:in finish_resolve' 2020-04-27T15:44:59.2858720Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:297:in block in activate_bin_path'
2020-04-27T15:44:59.2860400Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:295:in synchronize' 2020-04-27T15:44:59.2862020Z 	from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems.rb:295:in activate_bin_path'
2020-04-27T15:44:59.2863480Z 	from /usr/local/bin/fastlane:23:in `'
2020-04-27T15:44:59.3050400Z ##[error]Error: fastlane failed with return code: 1
2020-04-27T15:44:59.3112910Z ##[section]Finishing: Publish TestApp to the App Store TestFlight track
Environment
MacMini2014:vsts-agent-osx-x64-2.133.3 user$ fastlane env
[✔] 🚀
[08:32:33]: fastlane detected a Gemfile in the current directory
[08:32:33]: However, it seems like you didn't use bundle exec
[08:32:33]: To launch fastlane faster, please use
[08:32:33]:
[08:32:33]: $ bundle exec fastlane env
[08:32:33]:
[08:32:33]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[08:35:13]: Generating fastlane environment output, this might take a few seconds...
✅ fastlane environment ✅
Stack
| Key                         | Value                                       |
| --------------------------- | ------------------------------------------- |
| OS                          | 10.15.4                                     |
| Ruby                        | 2.6.5                                       |
| Bundler?                    | false                                       |
| Git                         | git version 2.24.2 (Apple Git-127)          |
| Installation Source         | /usr/local/bin/fastlane                     |
| Host                        | Mac OS X 10.15.4 (19E266)                   |
| Ruby Lib Dir                | /usr/local/Cellar/ruby/2.6.5/lib            |
| OpenSSL Version             | OpenSSL 1.1.1d  10 Sep 2019                 |
| Is contained                | false                                       |
| Is homebrew                 | false                                       |
| Is installed via Fabric.app | false                                       |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/ |
| Xcode Version               | 11.4.1                                      |
System Locale
| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_US.UTF-8 | ✅ |
| LC_ALL   |             |   |
| LANGUAGE |             |   |
fastlane files:
No Fastfile found
No Appfile found
fastlane gems
| Gem      | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.146.1 | ✅ Up-To-Date  |
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
| Gem                       | Version      |
| ------------------------- | ------------ |
| did_you_mean              | 1.3.0        |
| slack-notifier            | 2.3.2        |
| atomos                    | 0.1.3        |
| CFPropertyList            | 3.0.2        |
| claide                    | 1.0.3        |
| colored2                  | 3.1.2        |
| nanaimo                   | 0.2.6        |
| xcodeproj                 | 1.16.0       |
| rouge                     | 2.0.7        |
| xcpretty                  | 0.3.0        |
| terminal-notifier         | 2.0.0        |
| unicode-display_width     | 1.7.0        |
| terminal-table            | 1.8.0        |
| plist                     | 3.5.0        |
| public_suffix             | 2.0.5        |
| addressable               | 2.7.0        |
| multipart-post            | 2.0.0        |
| word_wrap                 | 1.0.0        |
| tty-screen                | 0.7.1        |
| tty-cursor                | 0.7.1        |
| tty-spinner               | 0.9.3        |
| babosa                    | 1.0.3        |
| colored                   | 1.2          |
| highline                  | 1.7.10       |
| commander-fastlane        | 4.4.6        |
| excon                     | 0.73.0       |
| faraday                   | 0.17.3       |
| unf_ext                   | <IP_ADDRESS>      |
| unf                       | 0.1.4        |
| domain_name               | 0.5.20190701 |
| http-cookie               | 1.0.3        |
| faraday-cookie_jar        | 0.0.6        |
| faraday_middleware        | 0.13.1       |
| fastimage                 | 2.1.7        |
| gh_inspector              | 1.1.3        |
| json                      | 2.3.0        |
| mini_magick               | 4.10.1       |
| multi_xml                 | 0.6.0        |
| rubyzip                   | 1.3.0        |
| security                  | 0.1.3        |
| xcpretty-travis-formatter | 1.0.0        |
| dotenv                    | 2.7.5        |
| naturally                 | 2.2.0        |
| simctl                    | 1.6.8        |
| jwt                       | 2.1.0        |
| uber                      | 0.1.0        |
| declarative               | 0.0.10       |
| declarative-option        | 0.1.0        |
| representable             | 3.0.4        |
| retriable                 | 3.1.2        |
| mini_mime                 | 1.0.2        |
| multi_json                | 1.14.1       |
| signet                    | 0.14.0       |
| memoist                   | 0.16.2       |
| os                        | 1.1.0        |
| googleauth                | 0.12.0       |
| httpclient                | 2.8.3        |
| google-api-client         | 0.36.4       |
| google-cloud-env          | 1.3.1        |
| google-cloud-errors       | 1.0.0        |
| google-cloud-core         | 1.5.0        |
| digest-crc                | 0.5.1        |
| google-cloud-storage      | 1.26.0       |
| emoji_regex               | 1.0.1        |
| jmespath                  | 1.4.0        |
| aws-partitions            | 1.303.0      |
| aws-eventstream           | 1.1.0        |
| aws-sigv4                 | 1.1.2        |
| aws-sdk-core              | 3.94.0       |
| aws-sdk-kms               | 1.30.0       |
| aws-sdk-s3                | 1.63.0       |
| bundler                   | 2.1.4        |

generated on: 2020-04-27

[08:35:22]: Take notice that this output may contain sensitive information, or simply information that you don't want to make public.
[08:35:22]: 🙄  Wow, that's a lot of markdown text... should fastlane put it into
your clipboard, so you can easily paste it on GitHub? (y/n)
y
[08:37:52]: Successfully copied markdown into your clipboard 🎨
[08:37:52]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅

Hi @xplatform
Were you ever able to find a solution to this issue?


Icons broken on iOS

Some icons are broken on iOS. Specifically this seems to affect some outline icons. I'm using iOS 10.1.1
Attaching screenshots of the ones I've spotted

Yeah, there are some issues with some icons on iOS only. Will redraw broken icons

I can confirm this issue on iOS. I was looking for a bug in my own code first...
Thanks for fixing it soon.

I can confirm this issue on iOS. I was looking for a bug in my own code first...
Thanks for fixing it soon.

Fixed now in 0.8.9 release


Fold not loading after custom compilation

I have succesfully compiled tensorflow r1.1 and fold in my linux machine with gcc-4.9 but python is not able to load tensorflow:
>>> import tensorflow_fold as fd
2017-05-29 11:40:45.075279: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:901] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2017-05-29 11:40:45.075584: I tensorflow/core/common_runtime/gpu/gpu_device.cc:887] Found device 0 with properties:
name: GeForce GTX 1060 6GB
major: 6 minor: 1 memoryClockRate (GHz) 1.759
pciBusID 0000:01:00.0
Total memory: 5.92GiB
Free memory: 5.33GiB
2017-05-29 11:40:45.075597: I tensorflow/core/common_runtime/gpu/gpu_device.cc:908] DMA: 0
2017-05-29 11:40:45.075601: I tensorflow/core/common_runtime/gpu/gpu_device.cc:918] 0:   Y
2017-05-29 11:40:45.075606: I tensorflow/core/common_runtime/gpu/gpu_device.cc:977] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX 1060 6GB, pci bus id: 0000:01:00.0)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/__init__.py", line 22, in <module>
    from tensorflow_fold.blocks.block_compiler import *
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/blocks/block_compiler.py", line 28, in <module>
    from tensorflow_fold.blocks import loom_ops
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/blocks/loom_ops.py", line 19, in <module>
    import tensorflow_fold.blocks.result_types as tdt
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/blocks/result_types.py", line 27, in <module>
    from tensorflow_fold.public import loom
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/public/loom.py", line 17, in <module>
    from tensorflow_fold.loom.loom import *
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/loom/__init__.py", line 17, in <module>
    from tensorflow_fold.loom.loom import *
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/loom/loom.py", line 36, in <module>
    from tensorflow_fold.loom import deserializing_weaver_op
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/loom/deserializing_weaver_op.py", line 34, in <module>
    tf.resource_loader.get_data_files_path(), '_deserializing_weaver_op.so'))
  File "/home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow/python/framework/load_library.py", line 64, in load_op_library
    None, None, error_msg, error_code)
tensorflow.python.framework.errors_impl.NotFoundError: /home/rcilla/code/foldenv/local/lib/python2.7/site-packages/tensorflow_fold/loom/_deserializing_weaver_op.so: undefined symbol: _ZN10tensorflow7strings6StrCatB5cxx11ERKNS0_8AlphaNumE

Note the symbol not found is different from the one reported in #57

I just found that when compiling tensorflow with gcc 6.3.0 - without cuda support - the error is not produced.   It only appears when compiling wiht gcc-4.9 and cuda support

_ZN10tensorflow7strings6StrCatB5cxx11ERKNS0_8AlphaNumE

Looks like tensorflow::strings::StrCat is missing. This error seems to come from the string interface change in GCC from GCC 4.x to 5.x.
https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/


Zaibe

closes #issueNumber
Checklist for profile addition

[ ] Name the PR fix: add <shahzaib512>.
[ ] You've added file named your-username.json in the profiles directory.
[ ] You've linked the PR to the correct issue.

Other additions/changes

[ ] Changes made in this PR are mentioned below
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.
[ ] I've read the contributing guidelines

This PR adds/fixes

Notes

0k


User should be able to disable features pre install

It takes a while for everything to start up.  There are times where a user might not want letsencrypt or rdns. The user should be able to disable features prior to installation.

Available in quickstarts https://github.com/rancher/rio#quick-start. rio install --disable-features

This feature is added in v0.2.0