text:
WSLGit works, does not work in VSCode

I have Ubuntu WSL installed from the store and WSLGit running as git.exe, with the git.path pointing to it correctly. I just switched my config to use an SSH key with no passphrase, and set WSLGIT_USE_INTERACTIVE to 0 in my environment settings.
Running the git.exe executable under bash works fine. The Output > Git menu in VSCode shows that it finds the right executable, and can run it (output below).
The issue is that every time I open or switch to a file under version control the SOURCE CONTROL pane flickers between showing the 'calculating changes' interfaces and displaying No source providers registered, which is what it settles on.
I'm aware this may be more a vscode issue than a wslgit one, but given the unusual setup I thought I'd try here first.
Any ideas?
Here's the Git Output:
Looking for git in: C:\Users\MarcelKornblum\Projects\git.exe
Using git 2.17.1 from C:\Users\MarcelKornblum\Projects\git.exe
> git rev-parse --show-toplevel
> git config --get commit.template
Open repository: \c\Users\MarcelKornblum\Projects\website
> git status -z -u
> git rev-parse --show-toplevel
> git config --get commit.template
Open repository: \c\Users\MarcelKornblum\Projects\netlify-cms-oauth-provider-python
> git status -z -u
> git rev-parse --show-toplevel
> git config --get commit.template
Open repository: \c\Users\MarcelKornblum\Projects\website
> git status -z -u
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git config --get commit.template
Open repository: \c\Users\MarcelKornblum\Projects\website
> git status -z -u
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git config --get commit.template
Open repository: \c\Users\MarcelKornblum\Projects\website
> git status -z -u
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git rev-parse --show-toplevel
> git config --get commit.template
...
Open repository: \c\Users\MarcelKornblum\Projects\website
> git status -z -u
> git rev-parse --show-toplevel
> git config --get commit.template

The paths in the "Open repository..." lines do not look right.
Can you please check the output of C:\Users\MarcelKornblum\Projects\git.exe rev-parse --show-toplevel by running it from a command prompt within a git repository? It should print a path like c:\Users\....
Do you have any special mount points setup inside WSL, or configured custom mounts in wsl.conf?

The output from that command (run from within a repo called website, navigated to via cmd is the same as the "Open repository" line:
/c/Users/MarcelKornblum/Projects/website

I don't think I've set up any custom mounts though this is my first Windows machine in a long time and it's possible I did something following a tutorial online while trying to set up. There's no files at /etc/wsl.conf in any case.

Hi there, Andy.
First of all, kudos to you for tackling the wls, git and vscode issue (which really MS should have solved by now).
Having said that, I'm running into the same issue as @marcelkornblum.
Are there any news on how to solve it?
Thank you in advance!

It turned out I had something in .bashrc from trying to run docker in wsl. I managed to get it running with trial and error by fiddling with settings and looking at the git output panel until it matched what Andy was expecting. Unfortunately I can't have docker mounting working at the same time as it seems it needs the exact opposite setting :(

Yes, exactly. Currently, wslgit only supports the default WSL mount points under /mnt, while Docker needs everything mounted directly under /.
I have some plans to support more general mounts, but no concrete implementation yet.

It feels as though both ought to be able to be working at the same time, but I tried symlinks and new mount points and all sorts of ideas without luck.
I guess really this issue should be closed, but do you know if there's something I can subscribe to for when you figure it out @andy-5 ?
If there's anything I can do to help of course please let me know, the work you've done to date is great...

You mentioned that you setup the mounts for docker in .bashrc - are you using something like sudo mount --bind /mnt/c /c there? Because there seems to be a workaround for that specific setup, see https://github.com/andy-5/wslgit/issues/33#issuecomment-412774712.
If you set the Windows environment variable WSLGIT_USE_INTERACTIVE_SHELL to 0, .bashrc should not be executed when running wslgit, so the default mount points are used and everything works fine. However, once you open a WSL shell, which executes .bashrc, the mount points are changed permanently (until the next reboot) to the way docker expects them.
The workaround is to open your project in VS Code before opening any WSL shell. wslgit should work correctly then, and VS Code internally remembers the correct path to the repository. Afterwards, you can open a WSL shell, which changes the mount points. From then on, wslgit will not correctly translate the paths anymore, but most commands should work fine from within VS Code (because it remembered the correct path to the repository).
For a proper fix, you can follow issues #12 and #42 (which describes the same problem, but with a different setup). As you suggested, I'm closing this issue now in favor of the others. Feel free to share any updates on your specific setup or possible workarounds you may find.


text:
New test instances aren't recognized

There are some new test instances, like Frankfurt_Ruxit, Falkenstein, Berlin, which haven't names like ec2-eu-central-1. On trying to add these instances like  Frankfurt_Ruxit:Chrome, after update scenarios they aren't recognized in the list of test instances.

The email that had your API WebPageTest API key lists the location that an API key can be used with - primarily the Akamai supported locations, Dulles & London
There was an WebPageTest bug that allowed other locations to be used and this got fixed at some point (it's not known what fixed the bug)
So first thing to check is whether you API key actually supports the locations you're trying to use

Sure, it does. I run successful tests with locations like
Frankfurt, Safari, Cable | eu-central-1:Safari
Frankfurt_EC2, Chrome, Cable | ec2-eu-central-1:Chrome

Hi @e-orlov,
If I'm not mistaken, the list of locations at https://www.webpagetest.org/getLocations.php?f=html includes locations that are not available through the API.
This is the list of locations available through the API, the ones that you mention are not available there:
https://www.webpagetest.org/getLocations.php?f=html&k=A

source: gharchive/issue

authors: andydavies e-orlov josebolos

repo: andydavies/WPT-Bulk-Tester

license: mit

license_type: permissive

license_source: bigquery


text:
Log Generation in Batch and Stream Mode to AWS S3

Backend file and dependencies added to the backend pom.xml.

Access Key not removed

source: gharchive/pull-request

repo: andymbwu/log-generator

license_source: github-api


text:
Fix PythonParser.on_disconnect not to close socket before Connection

Pull Request check-list

[x] Does $ python setup test pass with this change (including linting)?
[ ] Does travis tests pass with this change (enable it first in your forked repo and wait for the travis build to finish)?
[x] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

Description of change
Related to #1085
I have added failing tests to show inconsistencies between HiredisParser and PythonParser
on_disconnect implementations.
When hiredis is installed (and HiredisParser is used implicitly)
connection can not be securily shared between process forks because if it gets closed in
one of forks other processes can receive BrokenPipe errors because of operations on shutdown socket.

I tweaked your patch a bit and merged it. Thanks!

authors: andymccurdy popravich

repo: andymccurdy/redis-py

license: MIT


text:
showDetails toolbar button can be in wrong state after initialization

It seems that the showDetails button is always in the active state by default, even when json-viewer is initialized with show-data-types="false" and show-size="false". In that scenario the button then requires two clicks before it has the expected toggling effect.

Thank you for reporting this issue. I will check it and work on a fix.

authors: Toutouwai andypf

repo: andypf/json-viewer


text:
'rzModule' not available

I'm trying to integrate this with my project (angularjs - ionic framework - cordova), and when try do this:
angular.module('modulename', [
   ...
  'rzModule'
  ])

this is what I get:
0     008561   error    TypeError: undefined is not an object (evaluating 'angular.module'), http://192.168.0.100:8100/lib/angularjs-slider/dist/rzslider.js, Line: 26
1     008744   error    Error: [$injector:modulerr] Failed to instantiate module syndcate due to:
[$injector:modulerr] Failed to instantiate module rzModule due to:
[$injector:nomod] Module 'rzModule' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

False alarm! I included this before angular..

Why i am a ruler?

authors: jangholi oguzgelal

repo: angular-slider/angularjs-slider


text:
Demo missing for ng-repeat

Is there any demo for a translation of a dynamic translationId derived from a variable inside ng-repeat.

The value of element's attribute translate is a string (otherwise you would have to write  always). Maybe use AJS interpolation () or use a dedicate component (and calling the service).

Thank you very much! I am going to implement a dedicated component because I think that components are more clean and flexible.

But remember to use the events so you get translation language changes correctly.

authors: knalli leolux

repo: angular-translate/angular-translate


text:
Using canvas

From @iamsaint on February 16, 2015 11:0
Hi. Could you tell me how to use canvas to draw map layer with your directive?
Copied from original issue: tombatossals/angular-leaflet-directive#634

From @nCore on March 2, 2015 14:30
You have two possibilities:

Create your own canvas, above the map (via higher z-index) like this:

#map {
    display: block;
    width: 100%;
    height: 100%;
    position: relative;
    z-index: 1;
}

#canvas {
    display: block:
    width: 100%;
    height: 100%;
    position: absolute;
    z-index: 2;
    /* this will allow you to scroll the map and pass-through all the events */
    pointer-events: none;
}

and then just simply get it in javascript and draw anything on it:
var canvas = document.getElementById('canvas');
var context = canvas.getContext('2d');

// drawing logic

You can use this plugin for Leaflet: https://github.com/CartoDB/Leaflet.CanvasLayer and use with mapObject given by leafletData.getMap() promise.

From @simonpeters on May 13, 2015 11:59
Doesn't leaflet support canvas out of the box?

If the functionality is missing then see if you can add it.

Look at the code and the examples.
https://github.com/tombatossals/angular-leaflet-directive/blob/master/src/services/leafletLayerHelpers.js

repo: angular-ui/ui-leaflet


text:
API docs issues

The example for otherwise in the docs seems to be incorrect. I tried the following:
.config(function($urlRouterProvider) {
  $urlRouterProvider.otherwise((url, router) => {
    router.stateService.go('error', {error: 'page-not-found'});
  });
})

But this resulted in an error Cannot read property 'stateService' of undefined.
I then moved the logic to the run cycle instead:
.run(function($urlRouter) {
  $urlRouter.otherwise((url, router) => {
    router.stateService.go('error', {error: 'page-not-found'});
  });
})

This led to Cannot read property 'go' of undefined.
Upon analysis of parameters, I found that a boolean value is inserted as the first parameter to the function. Changing to:
.run(function($urlRouter) {
  $urlRouter.otherwise((bool, url, router) => {
    router.stateService.go('error', {error: 'page-not-found'});
  });
})

Finally did the trick.
So not sure what that first parameter is, but it's missing from the example. In addition, the return statement in the example is superfluous.
Further, the docs here should probably state:

Returns the state that the transition is going to

E.g. to instead of from.

$urlRouterProvider and $urlRouter are deprecated.
Try using $urlServiceProvider.rules.otherwise((matchValue, url, router) => {});.
All parameters are optional. See here https://ui-router.github.io/ng1/docs/latest/interfaces/url.urlrulehandlerfn.html

The docs for urlRouter service (injected as $urlRouter at runtime) are correct.  For $urlRouterProvider (injected at config time), follow this chain:
injectables -> $urlRouterProvider -> $urlRouterProvider.otherwise
The reason for this is:
In angular-ui-router, we've always used .config(function($urlRouterProvider) {}) to add rules like otherwise.  Those rules were passed the $injector, i.e.
$urlRouterProvider.otherwise(function ($injector, $location) {
    return '/a/valid/url';
  }));

In ui-router-core, we're dropping the $injector wherever possible, but the ng1 code still should support it for backwards compatibility.   Since $urlRouterProvider is only an ng1 concept, it keeps the OLD API for use in .config() blocks.

Thanks for the clarification, I'll review the doc changes and refactor my code accordingly

authors: adamreisnz aj-dev christopherthielen

repo: angular-ui/ui-router


text:
Error: no such method 'instance' for sortable widget instance

I don't know why i get that error twice one in line 79 and 226 (current version), with a dinamic loaded list. The weird thing is that the list is still sortable.
Thanks

What version of jquery-ui are you using?

The last one, that you point in the website
The first error goes in here:
        // When we add or remove elements, we need the sortable to 'refresh'
        // so it can find the new/removed elements.
        scope.$watch('ngModel.length', function() {
          // Timeout to let ng-repeat modify the DOM
          $timeout(function() {
            // ensure that the jquery-ui-sortable widget instance
            // is still bound to the directive's element
            if (!!element.sortable('instance')) {//////HHEEEEEEERREEEEE
              element.sortable('refresh');
            }
          }, 0, false);

and the second one in here:
        scope.$watch('uiSortable', function(newVal /*, oldVal*/) {
          // ensure that the jquery-ui-sortable widget instance
          // is still bound to the directive's element
          if (!!element.sortable('instance')) {///HEREEEEE

It looks like the links in the README are for v1.10.x instead of v1.11.x.
The test cases use the latest version (v1.11.x) fetched from bower and that's why I could spot this issue while developing.
I will push a hotfix in the weeken to restore support for jquery-ui v 1.9+ as advertised.
Thanks for your collaboration in this issue.

Fixed in v0.13.2, releasing now

authors: thgreasi yayolius

repo: angular-ui/ui-sortable


text:
edit-mode directive is only one way binding

Hi, I am creating a wizard for edition and creation. And depending of what the user is doing I should set if it is in edit mode or not.
The fact is the attribute edit-mode is only one way bound so if I first create an entity it starts with editMode set on false, but if after it I want to edit another entity, editMode can't change to true.
I've tried with edit-mode="{{editMode}}" but it doesn't work as I expected.
Thanks

Can you elaborate on this example or provide a code example.  I'm not sure I know what you are getting at.

@franciscopuyo I found a problem that only allowed edit mode to be toggle once, I corrected it and it will be in the next push.
<button ng-click="clickToggle()">Toggle Edit Mode</button>
<wizard on-finish="finishedWizard()" hide-indicators="false" edit-mode="editToggle">
...

$scope.clickToggle = function() {
    $scope.editToggle = !$scope.editToggle;
};

This will work

My use case is like so:

bind edit-mode to a variable in my component: edit-mode=$ctrl.wizardEditMode
initially wizardEditMode is false
a user selects an item from a list, wizardEditMode gets set to true.

Things work so far. Then when the user is done performing their task, they hit a save button and I "reset" the wizard. After resetting, changes to the wizardEditMode variable, aren't being picked up by the $watch on editMode in the angular-wizard source. I'd like the editMode logic to be in a function so I can invoke it.
I'll submit a pull request in a moment.

Pull request added: https://github.com/angular-wizard/angular-wizard/pull/236

authors: franciscopuyo jacobscarter mindscratch

repo: angular-wizard/angular-wizard


text:
file.ts is missing from TypeScript Compilation.

Versions
Windows 10 Enterprise

Angular CLI: 1.6.6
Node: 8.9.4
OS: Win32 x64
Angular: 5.2.9

I've been tasked to add a Test Framework to an Angular/TypeScript project, and I had never heard of it before I had started. Using Jasmine / Karma and have got the program to succeed a test for the condition (if 0 is equal to 0).
I'm trying to make use of the default code provided to a Spec file created by the compiler whenever a component is generated. Below is the code:
`
import { async, ComponentFixture, TestBed } from '@angular/core/testing';
import { CommonModule } from '@angular/common';
import { ShareModule } from '../../../share/share.module';
import { DashboardRoutingModule } from '../dashboard.routing.module';
import { DashboardComponent } from '../dashboard-main/dashboard.component';
import { ChartModule } from '../../../share/charts/chart.module';
describe('Module / Component : Dashboard', () => {
it('If 0 is 0, return true', () => {
expect(0).toEqual(0);
});
let component: DashboardComponent;
let fixture: ComponentFixture;
beforeEach(async(() => {
TestBed.configureTestingModule({
imports: [
CommonModule,
ShareModule,
DashboardRoutingModule,
ChartModule,
],
declarations: [
DashboardComponent
]
})
.compileComponents();
}));
beforeEach(() => {
fixture = TestBed.createComponent(DashboardComponent);
component = fixture.componentInstance;
fixture.detectChanges();
});
it('should create component', () => {
expect(component).toBeDefined();
});
});
`
The only differences between the copy code and the default code, is the additional Imports at the top as well as those same imports reflected within the configureTestingModule function.
If I do not have those imports in place, the compiler kicks up a fuss when I try to test it on the grounds that "<app-chart [data]="data">" is unrecognised (These tags are the only thing within my components html file, as they call another module / component that simply displays a graph. While data is me passing the data for the graph)
When I add in the imports, this Error goes away and is then replaced with
_ERROR in ./src/environments/environment.ts
Module build failed: Error: C:\Users\MYNAME\Project\PROJECTNAME\src\environments\environment.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
at AngularCompilerPlugin.getCompiledFile (C:\Users\MYNAME\Project\PROJECTNAME\node_modules@ngtools\webpack\src\angular_compiler_plugin.js:656:23)
at plugin.done.then (C:\Users\MYNAME\Project\PROJECTNAME\node_modules@ngtools\webpack\src\loader.js:467:39)
at
at process.tickCallback (internal/process/next_tick.js:188:7)
@ ./src/app/share/map/map.api.service.ts 26:20-64
@ ./src/app/share/map/map.module.ts
@ ./src/app/share/form/form.module.ts
@ ./src/app/share/share.module.ts
@ ./src/app/modules/dashboard/dashboard-main/dashboard.component.spec.ts
@ ./src .spec.ts$
@ ./src/test.ts
My file structure is:
src [Folder]
--app [Folder]
--/--modules [Folder]
--/--/--dashboard [Folder]
--/--/--/--dashboard.Module [Module]
--/--/--/--dashboard Main [Folder]
--/--/--/--/--component files [ts/css/html/spec]
--/--share [Folder]
--/--/--charts [Folder]
--/--/--/--chart.Module [Module]
--/--/--/-- chart Main [Folder]
--/--/--/--/--component files [ts/css/html/spec]
--environments [Folder]
--/--environment.ts
Below is my tsconfig file.
{   "compileOnSave": false,   "compilerOptions": {     "outDir": "./dist/out-tsc",     "sourceMap": true,     "declaration": false,     "moduleResolution": "node",     "emitDecoratorMetadata": true,     "experimentalDecorators": true,     "target": "es5",     "typeRoots": [       "node_modules/@types"     ],     "lib": [       "es2017",       "dom"     ]   } }
I have been looking for a solution all day, but I'm unable to find one.

Update;
Commented out the "return true if 0 is 0" bit at the top, forgot it was there when I was testing. Now the error has been replaced with the following:
"Error: Found the synthetic property @animationState. Please include either "BrowserAnimationsModule" or "NoopAnimationsModule" in your application."
adding these imports does not stop this error.

repo: angular/angular-cli


text:
Test hangs if a TSCompiler rule fails

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Area
- [x] devkit
- [ ] schematics

Versions
Angular CLI: 6.0.8
Node: 10.3.0
OS: win32 x64
Angular: 6.0.7
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        0.6.8
@angular/cli                      6.0.8
@ngtools/webpack                  6.0.8
@schematics/angular               0.6.8
@schematics/update                0.6.8
rxjs                              6.2.1
typescript                        2.7.2
webpack                           4.8.3

Repro steps

ng new TestTest gotta give it an awesome name since you're testing the test feature
Open tsconfig.json and add "noUnusedLocals": true, to the compiler options
Open app.component.ts and add Input to the import: import { Component, Input } from '@angular/core';
run ng test

The log given by the failure
C:\git\TestTest>ng test
 10% building modules 1/1 modules 0 active(node:26184) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
06 07 2018 12:06:29.736:WARN [karma]: No captured browser, open http://localhost:9876/
06 07 2018 12:06:29.749:INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:9876/
06 07 2018 12:06:29.750:INFO [launcher]: Launching browser Chrome with unlimited concurrency
06 07 2018 12:06:29.758:INFO [launcher]: Starting browser Chrome              × ｢wdm｣: Hash: a560bbf6f6cb4d2aebc7
Version: webpack 4.8.3
Time: 4663ms
Built at: 07/06/2018 12:06:29 PM
       Asset      Size     Chunks  Chunk Names
     main.js  6.21 KiB       main  main
polyfills.js  6.52 KiB  polyfills  polyfills
Entrypoint main = main.js
Entrypoint polyfills = polyfills.js
[./src/polyfills.ts] 0 bytes {polyfills} [built]
[0] multi ./src/polyfills.ts 28 bytes {polyfills} [built]
[./src/test.ts] 0 bytes {main} [built]

ERROR in src/app/app.component.ts(1,21): error TS6133: 'Input' is declared but its value is never read.

The test will hang here forever, until you correct the error.
Desired functionality
It should continue building and running the tests after the error. Or at least it should end the process if you're in --watch=false mode.
Mention any other details that might be useful
This is a big problem with my CI environment.  If you submit some code that has an unused variable suddenly my build server hangs for an hour until the CI system finally decides to murder the process.
If you run ng build it powers through the error and still builds.  This is what leads me to believe this is an error with the Angular CLI and not the TypeScript compiler.  I'm assuming ng build and ng test should trigger the same compilation from TypeScript, yet one works and one doesn't.

By default ng test is run in watch mode.   Thus, it hangs forever waiting for the user to fix the error.
In CI, you should be using ng test --watch=false


text:
Unable to do anything with ng

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [x] new
- [x] build
- [x] serve
- [x] test
- [x] e2e
- [x] generate
- [x] add
- [x] update
- [x] lint
- [x] xi18n
- [x] run
- [x] config
- [x] help
- [x] version
- [x] doc

Versions

lazar@lazar:/media/lazar/Elements$ npm list -g --depth 0
/home/lazar/.nvm/versions/node/v10.8.0/lib
├── @angular/cli@6.1.4
├── npm@6.3.0
├── terser@3.8.1
└── wane@0.0.7 -> /home/lazar/wane

npm ERR! peer dep missing: jasmine@^2.4.1, required by jasmine-pretty-html-reporter@0.2.5
lazar@lazar:/media/lazar/Elements$ ng -v
angular-cli[11689]: ../src/node_contextify.cc:637:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.
 1: 0x8b8210 node::Abort() [angular-cli]
 2: 0x8b82e5  [angular-cli]
 3: 0x8eb237 node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [angular-cli]
 4: 0xb4daa8  [angular-cli]
 5: 0xb4fa12 v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [angular-cli]
 6: 0x3d74905841bd
Aborted (core dumped)
lazar@lazar:/media/lazar/Elements$ node -v
v10.8.0
lazar@lazar:/media/lazar/Elements$ npm -v
6.3.0
lazar@lazar:/media/lazar/Elements$

I'm on Linux, Ubuntu 17.04.
Repro steps

Uh... Type a command? :thinking:
The log given by the failure

I'll repeat it here from the version output:
angular-cli[11689]: ../src/node_contextify.cc:637:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.
 1: 0x8b8210 node::Abort() [angular-cli]
 2: 0x8b82e5  [angular-cli]
 3: 0x8eb237 node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [angular-cli]
 4: 0xb4daa8  [angular-cli]
 5: 0xb4fa12 v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [angular-cli]
 6: 0x3d74905841bd

Desired functionality

Ha!
Mention any other details that might be useful

I'm pretty sure it used to work at some point. Haven't used Angular in a while and tried to create a new project now :thinking:

I have the same problem when using cli Version 6.2.0-beta.3
I get the error serve.json not found on Windows.
With every command i try.

@lazarljubenovic
This most likely is not a bug in the CLI, it most likely caused by how installed the cli.
The CLI has many dependencies and you don't have them installed.
They are listed on the @angular/cli page on the npmjs site.
https://www.npmjs.com/package/@angular/cli
Each of those packages has other dependencies that are not installed.    It's a huge tree and you need to let npm do its work to get those dependencies for you.

To resolve you need to uninstall the current version

npm uninstall -g @angular/cli

The verify you npm cache.

npm cache verify

Then reinstall allowing all the dependencies to download.

npm install -g @angular/cli

This seems like a problem with your node/npm and not with Angular CLI.
Please have a look at the fixing npm permissions page, common errors page, npm issue tracker, or open a new issue in that issue tracker if the problem you are experiencing isn't known.

authors: KevinGruber alan-agius4 lazarljubenovic rlove


text:
:host-context special selector fails build when used in Sass file

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

$ node --version
v8.11.4
$ npm --version
5.6.0
$ ng --version
 _                      _                 ____ _     ___
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|

/ △ \ | '_ \ /  | | | | |/ _ | '__|   | |   | |    | |
/ ___ | | | | (| | || | | (| | |      | || | | |
//   __| ||_, |_,||_,||       _|||
|___/
Angular CLI: 6.1.5
Node: 8.11.4
OS: darwin x64
Angular: 6.1.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package                           Version
@angular-devkit/architect         0.7.5
@angular-devkit/build-angular     0.7.5
@angular-devkit/build-optimizer   0.7.5
@angular-devkit/build-webpack     0.7.5
@angular-devkit/core              0.7.5
@angular-devkit/schematics        0.7.5
@angular/cli                      6.1.5
@ngtools/webpack                  6.1.5
@schematics/angular               0.7.5
@schematics/update                0.7.5
rxjs                              6.3.1
typescript                        2.7.2
webpack                           4.9.2
Repro steps

The :host-context Special Selector is documented here:
https://angular.io/guide/component-styles#host-context
It is as simple as this to demonstrate the problem:
$ ng new —style=sass mynewproj
$ cd mynewproj
$ echo ":host-context(.myclass1) .myclass2" >> src/app/app.component.sass
$ echo "  color: red" >> src/app/app.component.sass
$ cat src/app/app.component.sass
:host-context(.myclass1) .myclass2
color: red
$ ng serve
The log given by the failure

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
Date: 2018-09-03T18:11:36.109Z
Hash: fd8f7012853b1b62f00b
Time: 4270ms
chunk {main} main.js, main.js.map (main) 10.9 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 227 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 5.22 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 15.9 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 3.27 MB [initial] [rendered]
ERROR in ./src/app/app.component.sass
Module build failed:
:host-context(.myclass1) .myclass2
^
Invalid CSS after "h": expected 1 selector or at-rule, was "host-context(.mycla"
in /mynewproj/src/app/app.component.sass (line 1, column 1)
ℹ ｢wdm｣: Failed to compile.
Desired functionality

The :host-context selector works fine when using a CSS file, but when using SASS there is a build failure.
I'm working around it temporarily by using both Sass and CSS in the component.  Yuck.
@Component({
selector: 'app-login',
templateUrl: './login.component.html',
styleUrls: ['./login.component.sass', './login.component.css'],
})
Why does the :host-context special selector not work in a Sass file?
Mention any other details that might be useful

I'm sorry, but this issue is not caused by Angular CLI. Please contact the author(s) of the  libsass project or file an issue on their issue tracker.


text:
ng build consumes all memory & swap

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Unknown
Description

From time to time (maybe one in 8-10 times) the build seems to run away consuming memory infinitely and crashing my machine if I don't catch it and kill it quick enough. Below is a screen shot of system monitor for one such event (where I did catch it in time)

The build I am running is a slightly modified version of the output from ng new
🔬 Minimal Reproduction

Open System Monitor, to resources page, and be ready to kill what you are about to start.
clone git@github.com:nsoft/ns-login.git
checkout revision 198c3f677d77652f59c6e7b08e4ef1dcf273436d
cd into the /admin directory
run ng build several times (or ./gradlew build which in turn runs ng build)

I have seen this occur with ng build run on the command line, run via gradle, or run via intellij invoking gradle when deploying to tomcat. About 50% of the time when this happens the build fails after locking up the computer for a couple minutes. I suspect this the OS killing it (but haven't tried to verify. This survival seems more likely if the machine was not running low on memory to start with.
🔥 Exception or Error

No Error, just an unresponsive computer that remains unresponsive >30 min,
with all memory and swap consumed.

🌍 Your Environment

Angular CLI: 8.3.20
Node: 11.8.0
OS: linux x64
Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.803.20
@angular-devkit/core         8.3.20
@angular-devkit/schematics   8.3.20
@schematics/angular          8.3.20
@schematics/update           0.803.20
rxjs                         6.4.0

Anything else relevant?

No browser involved

I am developing on Ubuntu 18.0.4. The above specified revision represents a very slightly modified version of the output from ng new I am quite new to Angular, and so My normal assumption would be that I've messed something up, and I'd hesitate to file a report, but intermittent run-away memory like this has to be a bug, even if it resulted from some thing I did...
I searched, but the bugs I find talk about out of memory errors, and that's not my case.
Another interesting bit is that the process list in System Monitor will NOT show any  process consuming a corresponding hunk of memory, so you can't find and kill it that way.

This appears to be related to something you provide in your demo components that are generated by ng new.  The problem goes away once the placeholder stuff is removed. Yet this is a really ugly failure mode.

This is most likely due to the use of Node.js 11.  This version has reached its end of life and is no longer supported.  Please consider updating to a supported version.  Version 12 is recommended for optimal performance (currently 12.13.1).  Please see https://nodejs.org for more information.

@nsoft, have you tried Node 12?

Sorry not yet. haven't yet rolled back to this project, which was not paid work... $$ first unfortunately. Definately plan to get back to it.

Closing as no further communication was provided by the issue creator.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

authors: alan-agius4 clydin nsoft


text:
ng build  changes output of another project in the workspace

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
No
Description
When building a project in a workspace, the build output of other project are changed during build. Have a look at the reproduction below. After you followed the steps, inside the dist folder, you can see that my-lib is not built for production anymore, even though I previously built the library for production. It seems that the command ng build my-application --prod changes the output of my-lib. If I build my-application, the output of my-lib should not be changed in my opinion.
This is annoying, because what I need to do to prevent errors in the build pipeline, is to

build the library for production
build the application for production
build the library for production

The third step should not be necessary.
🔬 Minimal Reproduction
Create a workspace with a library and an application
ng new my-workspace --create-application=false
cd my-workspace
ng generate library my-lib
ng generate application my-application

Now build the library and the application with production configuration:
ng build my-lib --prod
# my-lib is now built for production
ng build my-application --prod
# my-lib is not anymore built for production

🔥 Exception or Error
Below is the output in the console. As you can see, one step of the application build is Compiling my-lib : es2015 as esm2015
> ng build my-lib --prod && ng build my-application --prod

Building Angular Package

------------------------------------------------------------------------------
Building entry point 'my-lib'
------------------------------------------------------------------------------
Compiling TypeScript sources through ngc
Bundling to FESM2015
Bundling to FESM5
Bundling to UMD
Minifying UMD bundle
Writing package metadata
Built my-lib

------------------------------------------------------------------------------
Built Angular Package
 - from: C:\Projects\example-library-workspace\projects\my-lib
 - to:   C:\Projects\example-library-workspace\dist\my-lib
------------------------------------------------------------------------------
Compiling my-lib : es2015 as esm2015
Generating ES5 bundles for differential loading...
ES5 bundle generation complete.

chunk {0} runtime-es2015.1eba213af0b233498d9d.js (runtime) 1.45 kB [entry] [rendered]
chunk {0} runtime-es5.1eba213af0b233498d9d.js (runtime) 1.45 kB [entry] [rendered]
chunk {2} polyfills-es2015.4265614f51b38bdc5abc.js (polyfills) 36.1 kB [initial] [rendered]
chunk {3} polyfills-es5.d7f438905a78995e41d5.js (polyfills-es5) 129 kB [initial] [rendered]
chunk {1} main-es2015.a8830bb6116aeecf10ff.js (main) 137 kB [initial] [rendered]
chunk {1} main-es5.a8830bb6116aeecf10ff.js (main) 160 kB [initial] [rendered]
chunk {4} styles.3ff695c00d717f2d2a11.css (styles) 0 bytes [initial] [rendered]
Date: 2020-05-13T14:18:05.269Z - Hash: b6f9baef21f8ce0ea869 - Time: 93640ms

🌍 Your Environment
     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 9.1.5
Node: 12.16.3
OS: win32 x64

Angular: 9.1.6
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.901.5
@angular-devkit/build-angular      0.901.5
@angular-devkit/build-ng-packagr   0.901.5
@angular-devkit/build-optimizer    0.901.5
@angular-devkit/build-webpack      0.901.5
@angular-devkit/core               9.1.5
@angular-devkit/schematics         9.1.5
@angular/cli                       9.1.5
@ngtools/webpack                   9.1.5
@schematics/angular                9.1.5
@schematics/update                 0.901.5
ng-packagr                         9.1.3
rxjs                               6.5.5
typescript                         3.8.3
webpack                            4.42.0

Hi @json-derulo,
This happens because when building a library in prod mode, the library is build using the old rendering engine VE. When this is consumed in an application, it needs to be transformed and compiled to be Ivy compatible, which is done by NGCC. NGCC, will write the transformed code in the library folder.
What I suspect is that you don't need to run the --prod flag for the library build. --prod flag is intended to be used only when you want to publish your library to NPM repository. If you are consuming the library solely in your Angular workspace, you don't need to build using --prod.
In case you do want to public your library to npm, there are a couple of thing you can do. See here: https://github.com/angular/angular/issues/36119#issuecomment-600511071 for more information.


text:
Error in config file :  Cannot find module 'angular-cli/plugins/karma'

Please provide us with the following information:

OS?

Windows 10 x64

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.18
node: 6.4.0
Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Created the app usin the CLI (updated yesterday to the latest version). The app works and loads in Chrome. For now there's just an input field.
I created a service using "ng g myservice"
Then I wrote some tests in myservice.service.ts
I ran "ng test"
The log given by the failure.

Normally this include a stack trace and some more information.

$ ng test --watch=false
22 10 2016 11:05:54.156:ERROR [config]: Error in config file!
{ Error: Cannot find module 'angular-cli/plugins/karma'
at Function.Module._resolveFilename (module.js:455:15)
at Function.Module._load (module.js:403:25)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at module.exports (D:\dev\wiki_a2\karma.conf.js:12:7)
at Object.parseConfig (D:\dev\wiki_a2\node_modules\karma\lib\config.js:377:5)
at new Server (D:\dev\wiki_a2\node_modules\karma\lib\server.js:56:20)
at C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\tasks\test.js:25:31
at Class.exports.default.Task.extend.run (C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\tasks\test.js:15:16)
at Class.TestCommand.extend.run (C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\commands\test.js:26:25)
at Class. (C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\node_modules\angular-cli\lib\models\command.js:152:17)
at tryCatch (C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\node_modules\rsvp\dist\lib\rsvp-internal.js:215:12)
at invokeCallback (C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\node_modules\rsvp\dist\lib\rsvp-internal.js:230:13)
at C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\node_modules\rsvp\dist\lib\rsvp\then.js:29:16
at flush (C:\Users\Elg\AppData\Roaming\npm\node_modules\angular-cli\node_modules\rsvp\dist\lib\rsvp\asap.js:85:5)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9) code: 'MODULE_NOT_FOUND' }

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

Hi,
I'm experiencing the same issue -> fresh node and angular-cli installation, everything works, just the ng test doesn't (same error message and no karma plugin found).
Cheers

Hi,
I'm experiencing the same issue.
angular-cli: 1.0.0-beta.16
node: 6.6.0
os: Linux x64

I found my error which was that I had not provider a service. This service is used in the component that I want to test.

In my particular case, this error don't happen.

Closing as inactive.

Check if angular-cli/plugins/karma exists in the node_modules directory.
In my case the problem was that I had migrated to @angular/cli package, but karma.conf.js was still referencing the angular-cli paths.  I updated my references by comparing to the karma.conf.js from this repo: https://github.com/angular/angular-cli/blob/master/packages/%40angular/cli/blueprints/ng2/files/karma.conf.js

@juhap  this work for me but in the karma.conf.js have issue
Error: No provider for "framework:angular-cli"! (Resolving: framework:angular-cli)

@ahelord check the answer provided by @juhap there are multiple locations that angular-cli needs to be changed to @angular/cli

@juhap It seems that your link is broken. Could you take a look and fix it please? I'm also having a similar issue.

@frank-productops  New link you can check out: https://github.com/angular/angular-cli/blob/b15d1f37b6c6d7e57d969359b8b7d8a916465362/packages/%40angular/cli/blueprints/ng/files/karma.conf.js

@frank-productops i modify proyect little bit https://github.com/ahelord/angular-cli-primeng-example

Hi,
When I updated from angular-cli to @angular/cli, i also faced the same issue:
Error: Cannot find module 'angular-cli/plugins/karma'
The solution worked for me is to update the karma.conf.js file present in root folder of the project.
frameworks: ['jasmine', '@angular/cli'],
...
plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-remap-istanbul'),
      require('@angular/cli/plugins/karma')
    ],
...
preprocessors: {
      './src/test.ts': ['@angular/cli']
    },
...

After this change, ng test should work.

Detailed guide on changes to karma.conf.js after upgrading to @angular/cli rc1: https://github.com/angular/angular-cli/wiki/stories-rc.0-update

Since Google highly prefers Github issues instead of StackOverflow when it comes to debugging Angular 2 applications, I figured I would chime in here.
The issue is that the Node package for Angular's CLI was changed from angular-cli to @angular/cli.  If you go through your karma.conf.js file and replace all instances of angular-cli you should be good to go.
Shout out to this StackOverflow post that got me to the correct answer.  Also shout out to @softgandhi  for answering the same thing.  Unfortunately for him I lack reading comprehension.

I had a project in angular2, primeng and angular-cli. I decided to migrate angular4 and @ angular-cli
  When with the own guide angular but I did not work out errors when finding the core module. Then I decided to create a new project with the new @ angular-cli and pass the source code, there were errors where we had to add the Angular animations module and update Primeng.

You may also need to update the environments section in angular-cli.json
Old version
"environments": {         "source": "environments/environment.ts",         "dev": "environments/environment.ts",         "prod": "environments/environment.prod.ts"       }
New version
"environmentSource": "environments/environment.ts",       "environments": {                 "dev": "environments/environment.ts",         "prod": "environments/environment.prod.ts"       }

authors: Abekonge BaronChen Caballerog MeltdownZA ahelord bothbears droppedoncaprica filipesilva frank-productops jeremythille juhap sjcetx softgandhi


text:
ng new -d   ->  Cannot read property 'replace' of undefined

Bug Report or Feature Request (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.1.2
node: 6.9.2
os: win32 x64
Windows 10, powershell
Repro steps.
run "ng new [name] --dry-run"
The log given by the failure.
PS W:\> ng new Something --dry-run
installing ng
You specified the dry-run flag, so no changes will be written.
Cannot read property 'replace' of undefined
TypeError: Cannot read property 'replace' of undefined
    at decamelize (%APPDATA%\Roaming\npm\node_modules\@angular\cli\node_modules\ember-cli-string-utils\index.js:25:13)
    at Object.dasherize (%APPDATA%\Roaming\npm\node_modules\@angular\cli\node_modules\ember-cli-string-utils\index.js:50:11)
    at Class.<anonymous> (%APPDATA%\Roaming\npm\node_modules\@angular\cli\ember-cli\lib\models\blueprint.js:869:42)
    at tryCatch (%APPDATA%\Roaming\npm\node_modules\@angular\cli\node_modules\rsvp\dist\rsvp.js:539:12)
    at invokeCallback (%APPDATA%\Roaming\npm\node_modules\@angular\cli\node_modules\rsvp\dist\rsvp.js:554:13)
    at %APPDATA%\Roaming\npm\node_modules\@angular\cli\node_modules\rsvp\dist\rsvp.js:629:16
    at flush (%APPDATA%\Roaming\npm\node_modules\@angular\cli\node_modules\rsvp\dist\rsvp.js:2414:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

###Additional Informations
I just reinstalled angular cli before

npm uninstall cli
npm clear cache
npm install cli

With @@angular/cli 1.2.6, I can run
ng new no-app-will-be-generated --dry-run

The output is:
installing ng
You specified the dry-run flag, so no changes will be written.
  create .editorconfig
  create README.md
  create src/app/app.component.css
  create src/app/app.component.html
  create src/app/app.component.spec.ts
  create src/app/app.component.ts
  create src/app/app.module.ts
  create src/assets/.gitkeep
  create src/environments/environment.prod.ts
  create src/environments/environment.ts
  create src/favicon.ico
  create src/index.html
  create src/main.ts
  create src/polyfills.ts
  create src/styles.css
  create src/test.ts
  create src/tsconfig.app.json
  create src/tsconfig.spec.json
  create src/typings.d.ts
  create .angular-cli.json
  create e2e/app.e2e-spec.ts
  create e2e/app.po.ts
  create e2e/tsconfig.e2e.json
  create karma.conf.js
  create package.json
  create protractor.conf.js
  create tsconfig.json
  create tslint.json
Project 'no-app-will-be-generated' successfully created.

No folder with that name is created anywhere.
Most importantly, I do not see any error of any kind.

Closing this per @catull response. If you can still reproduce this issue with the latest CLI (1.2.7) please create a new issue and fill the template. Thanks!

authors: LProemer catull hansl


text:
Counterintuitive output with ngIfEnd and ngIfStart on same element

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] other

Current behavior:

Case 1:

A

B

C

Output: AC

Case 2:

A

B

C

Output:   (empty)
Expected / new behavior:

Case 1: A (C shouldn't be rendered because its ngIfEnd matches ngIfStart=false on B)
Case 2: C (C should be rendered because its ngIfEnd matches ngIfStart=true on B)
Angular version: 1.6.4

Browser: all

Putting the ngIfStart/End attributes on an element, is the same as putting ngIf on it. By having both ngIfStart and ngIfEnd on the same element, is like using two ngIfs on it. This is not a supported usecase imo.

Then I suppose that my current workaround isn't supported either:

I want all
s to be governed by condition1 && condition2; and the last two
s to also depend on condition3 && condition4. But I understand that the above is currently working by chance and may break in the future.
The only currently supported alternative I can think of is:

Which forces me to repeat condition1 && condition2 on the last two
s; if another condition that should apply to all
s were to be added, I would need to remember to add it to both ng-if-starts.
I guess that what I really want is a way to add more conditions to some of the elements in a ng-if-start/ng-if-end group.
One more thing, do elements between ng-if-start and ng-if-end also get their own ng-if? If that is the case, I suppose this isn't supported either:

Thanks

I see what you are after. In your initial example, it seemed like you where trying to have two interleaved ngIf'd collections (e.g. [item1, item2] and [item2, item3]), which is definitely not supported.
The way this works now, it is possible to have nested multi-element directives, but you can't have the start or end attributes for more than one directive on the same element (because of how we scan for these -end directives).
So, what you want is this (which is currently not supported):

Item 1

Item 2

Item 3

Item 4

What does work, is having one extra element at the end to enclose the whole group. E.g. something like:

Item 1

                    Item 2

Item 3

          Item 4

Demo

This is obviously not ideal, but should be fine for most usecase. Considering that there are also other (less dry but more flexible) solutions, I don't think it is worth trying to somehow support multiplt -end attributes on the same element.
(Closing, but feel free to continue the discussion below.)

I solved my use case following your nested multi-element directives example. I agree that supporting the same attribute twice on the same element isn't worth it. Thanks for your help!

authors: gabrielmaldi gkalpak


text:
Facebook login authentication problem

I use this code in main.ts :
bootstrap(MyApp, [
  APP_ROUTER_PROVIDERS,
  HTTP_PROVIDERS,
  FIREBASE_PROVIDERS,
  defaultFirebase({
    apiKey: "",
    authDomain: "",
    databaseURL: "",
    storageBucket: "",
  }),
  firebaseAuthConfig({
    method: AuthMethods.Password
  })
]).catch(err => console.error(err));

and i have this methode for facebook login
loginFacebook(){
 this.af.auth.login({
      provider: AuthProviders.Facebook,
      method: AuthMethods.OAuthToken,
    });
    console.log(" facebook login  ");

  }

and the facebook authentification d'ont work
how i can see the erreurs logs ?

i get this error  :

you must include credentials to use this auth method.

@samirthebti Sorry for the delay on this issue. Can you create a plnkr?

Nevermind, I just reproduced this myself. This is a bug, we'll get it fixed in the next release.

@samirthebti with
method: AuthMethods.Popup
or
method: AuthMethods.Redirect
I have it working, but I do get same error with
method: AuthMethods.OAuthToken

@Ronsku is correct.
Using AuthMethods.OAuthToken is an incorrect option.

authors: Ronsku davideast samirthebti


text:
Use of unexported auth property

When trying to bundle with rollup angularfire2 (ionic 2 app) I got such error:
 Error: Module myproject/node_modules/angularfire2/node_modules/firebase/firebase-browser.js does not export auth (imported by myproject/node_modules/angularfire2/auth/firebase_sdk_auth_backend.js)
Seems it is because import {auth} from 'firebase' and auth is not exported. Using angularfire2 version 2.0.0-beta.5

Thnx to @ivoviz, @orangesoup found workaround:
open node_modules/@ionic/app-scripts/config/rollup-config.js and:

Add useScript: false into configuration
change commonjs() to:

commonjs(
	{
	    include: [
		'node_modules/rxjs/**',
		'node_modules/angularfire2/**',
		'node_modules/firebase/**'
	    ],
	    namedExports: {
		'node_modules/angularfire2/node_modules/firebase/firebase.js': ['initializeApp', 'auth', 'database'],
		'node_modules/angularfire2/node_modules/firebase/firebase-browser.js': ['initializeApp', 'auth', 'database']

	    }
	}
 )

Yep, namedExports is the solution for now.

Hi,
i did the same and now it works, thanks.
But i wouldn't change the original rollup-config, you can just use your own, like here:
https://github.com/angular/angularfire2/issues/565#issuecomment-250153841

@olostan , it should be useStrict: false, not useScript: false!


text:
MatLabel with dark theme has very low contrast ratio

Reproduction
https://stackblitz.com/edit/angular-material-dark-theme-selected-form-field-contrast
Steps to reproduce:

Inspect one of the focused form-fields' label and check the color css property

Expected Behavior
$label-color should be lighten up here
Actual Behavior
When a MatFormField is focused the label becomes small, and with dark theme really hard to read. When it is in .mat-typography it's even smaller, but that's another issue
Environment

Angular: 8.2.14
CDK/Material: 8.2.3
Browser(s): Chrome 78.0.3904.97
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Yeah, this is a great issue. I agree that this has never been a really good contrast. We are working on a form-field that is based on MDC. We should make sure that this is improved there, or at least double-check with the Material Design team whether this is intentional or not.
https://material-components-web.appspot.com/theme/index.html?theme=dark
At first I'd say that it looks better for the yellow label, but as soon as the field becomes invalid, the contrast is not very good.

Hello, any news on this issue? MDC is now implemented and the issue is still there. We need to have a very light primary palette to assure good contrast...

authors: BUONJG Totati devversion

repo: angular/components


text:
MatTable with MatTableDataSource scrolling problem on dataSource update

Hi,
I'm pretty new to Angular and I did a CRUD RESTful application using HttpService, Mat-Table and MatTableDataSource. Everything is working fine except that in Chrome my table scrollbar always scroll to bottom when I refresh my datasource. Do you know what could it be?
This is my code, as you can see when I close the dialog I call the getLinedevices() method that update the dataSource.
If, for example, I am deleting a record in the middle of the table after the datasource updates the scrollbar scrolls to the bottom.
This doesn't happen in firefox.
Any suggestions will be appretiated,
Thanks,
Luca
export class LinedeviceComponent implements OnInit {

  displayedColumns: string[] = [....];
  linedevices: Linedevice[];
  linedevice: Linedevice;
  dataSource = new MatTableDataSource(this.linedevices);
  lineId: number;
  deviceId: number;
  description: String;
`
  /**
   * HttpClientService
   */
  constructor(
    private httpClientService: HttpClientService,
    private location: Location,
    public dialog: MatDialog,
    public deleteDialog: MatDialog,
    public insertDialog: MatDialog
  ) { }

  ngOnInit() {
    this.getLinedevices();
  }

getLinedevices() {
    this.httpClientService.getLinedevices().subscribe(
      response => this.dataSource.data = response,
    );
  }
/*
   * Dialog di Delete
   */

  openDeleteDialog(): void {
    const dialogRef = this.deleteDialog.open(DialogDeleteComponent, {
      width: '500px',
      data: { lineId: this.lineId, deviceId: this.deviceId, description: this.description }
    });

    dialogRef.afterClosed().subscribe(result => {
      console.log('The delete dialog was closed');
      /*console.log(result);*/
      this.getLinedevices();
    });
  }

Unfortunately we are tight on resources and unable to do much troubleshooting right now. I recommend asking on Stackoverflow, but also providing a reproduction in StackBlitz

authors: LucaMurarolli andrewseguin


text:
Why so many Material Libraries?

I'm quite confused.
There is this one, which is the official Material for Angular.
There is also material-components-web which is a general verison that works everywhere and developed by Material team and then there is angular-mdc-web, same as material-components-web but for angular.
ARGH, What's going on at Google?
If I start a project with something and it gets abandoned then I'll need to switch everything and work twice. How can I make the right choice?
Also, do this follow material-components-web? I mean, if material-components-web release a feature or change something, this library should be updated, right?

Don't rely on Google's corporate design implementations for realising my very own corporate branding :rocket: :woman_cartwheeling:

Si which one did you pick to help you get started?

Closing as this is not regarding the Angular Material library.

@josephperrott Well, it is regarding Angular Material. I'm wondering what makes this one better that the 2 others. It's getting confusing :( Please help me :P

Just try this library out.. you'll see that it's well designed and crafted... I have worked with both this and the one for angularjs and the team are doing a great job!

Thanks for the input.

The @angular/material library is very good library, for sure! If the goal is to implement an app in material UI/UX, it's a good choice!

If I start a project with something and it gets abandoned then I'll need to switch everything and work twice.

Maybe, I have mistaken the question. It sounded like you were trying to implement a corporate branding with the material libraries. I would not choose material for that. When goal is to implement an app in material, then go for it!

authors: Extarys dherges josephperrott mackelito


text:
Failed to compile

Bug, feature request, or proposal:
The master branch was Failed to compile,when I use command gulp serve:devapp
What is the expected behavior?
What is the current behavior?
here are the Error Code Stack:
Error: Error: /Users/ydy/Code/WorkSpace/WebstormProjects/material2/src/lib/input/input.ts:48:1: Error encountered in metadata generated for exported symbol 'MatInput':
 /Users/ydy/Code/WorkSpace/WebstormProjects/material2/src/lib/input/input.ts:165:48: Metadata collected contains an error that will be reported at runtime: Expression form not supported.
  {"__symbolic":"error","message":"Expression form not supported","line":164,"character":47}
    at /Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/@angular/compiler-cli/src/metadata/collector.js:663:27
    at Array.forEach (<anonymous>)
    at validateMetadata (/Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/@angular/compiler-cli/src/metadata/collector.js:651:42)
    at MetadataCollector.getMetadata (/Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/@angular/compiler-cli/src/metadata/collector.js:508:17)
    at LowerMetadataCache.getMetadataAndRequests (/Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/@angular/compiler-cli/src/transformers/lower_expressions.js:263:39)
    at LowerMetadataCache.ensureMetadataAndRequests (/Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/@angular/compiler-cli/src/transformers/lower_expressions.js:209:27)
    at LowerMetadataCache.getRequests (/Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/@angular/compiler-cli/src/transformers/lower_expressions.js:204:21)
    at /Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/@angular/compiler-cli/src/transformers/lower_expressions.js:146:36
    at /Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/typescript/lib/typescript.js:2492:86
    at reduceLeft (/Users/ydy/Code/WorkSpace/WebstormProjects/material2/node_modules/typescript/lib/typescript.js:2188:30)

Failed to compile  using /Users/ydy/Code/WorkSpace/WebstormProjects/material2/src/lib/tsconfig-tests.json

adapter/moment-date-adapter.ts(10,44): error TS2307: Cannot find module '@angular/material'.
adapter/moment-date-adapter.ts(118,37): error TS2339: Property 'locale' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.ts(132,58): error TS2339: Property 'locale' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.ts(143,33): error TS2339: Property 'locale' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.ts(148,46): error TS2339: Property 'locale' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.ts(150,46): error TS2339: Property 'locale' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.ts(191,57): error TS2339: Property 'locale' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-formats.ts(9,30): error TS2307: Cannot find module '@angular/material'.
adapter/index.ts(15,8): error TS2307: Cannot find module '@angular/material'.
adapter/moment-date-adapter.spec.ts(11,64): error TS2307: Cannot find module '@angular/material/core'.
adapter/moment-date-adapter.spec.ts(168,20): error TS2339: Property 'sameDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(267,20): error TS2339: Property 'compareDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(268,20): error TS2339: Property 'compareDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(269,20): error TS2339: Property 'compareDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(270,20): error TS2339: Property 'compareDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(271,20): error TS2339: Property 'compareDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(272,20): error TS2339: Property 'compareDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(273,20): error TS2339: Property 'compareDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(277,20): error TS2339: Property 'clampDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(283,20): error TS2339: Property 'clampDate' does not exist on type 'MomentDateAdapter'.
adapter/moment-date-adapter.spec.ts(289,20): error TS2339: Property 'clampDate' does not exist on type 'MomentDateAdapter'.

What are the steps to reproduce?
Here are some commands I've used as follows:

git clone
npm install -g glup
cd material2
npm install
gulp serve:devapp

and then compiling failed
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Mac OS
Is there anything else we should know?
I was just beginning to learn about the Angular,maybe this is a easy question, I'll appreciate for any help

Closing as a duplicate of https://github.com/angular/material2/issues/8380.

authors: AlphaIX crisbeto


text:
Sidenav demos broken

The sidenav demos at your documentation are broken.

Duplicate of #8702. Please use the search before opening duplicate issues.

authors: donroyco mbeckenbach


text:
fix(grid-list): styles not cleared when switching to a different styling mode

Fixes the old styles not being cleared when switching between styling modes in the grid list (e.g. going for proportions to a fixed height).
Fixes #4047.

Presubmit passed
@crisbeto can you rebase?

authors: crisbeto jelbourn


text:
Element not visible even after using browser.wait()

I am using ng-hide and ng-show for my login page. While testing I get element not visible, I tried browser.wait() but it says mulitple elements found.
My code is available at
https://github.com/Leo-G/Flask-Scaffold/blob/develop/app/templates/login.html
Any help will much appreciated.

Please direct general support questions like this one to an appropriate support channel, see https://github.com/angular/protractor/blob/master/CONTRIBUTING.md#questions
Thank you!

authors: Leo-G juliemr

repo: angular/protractor


text:
WebElement.clear() Does Not Update Model

Calling WebElement.clear() on an input element does not appear to update the associated model.
View:
<input ng-model="foo">
<div>{{foo}}</div>

Spec:
it("should update the model", function(){
    var input = element(by.css("input"));
    input.sendKeys("bar");
    input.clear();
    expect(element(by.css("div")).getInnerHtml()).toBe(""); // Fails, because it's still "bar"
});

@wlingke  thank you you are genius

@wlingke thanks from 2017. I still have this issue on angular 2.

@EugeneSnihovsky Are you having problems with clear in a pure angular 2 application? I am having issues in a hybrid app with validation not triggering when using clear but wasn't sure if i have broken something or if it was related to hybrid application.

me too! on ng2

Still having this issue in 2017. On an input containing 'abc', .clear() followed by .sendKeys('d') on the empty input field and results in 'abcd' in angular's model using reactive forms.

@wlingke thanks from 2018, lol. Still having this problem on Angular 5 when I try doing:
field.clear() // works
field.sendKeys() //works
field.clear() // doesn't update my reactive form

backspace issue with clear throws a WebDriverError: java.net.SocketException: Connection reset by peer error

Ok I've had to resort to a more complex workaround, but it's a lot more reliable. I've had no false test failures with this.
const mapSerial = (fn: Function, list: any[]) => list.map(x => fn(x)).reduce((p, next) => p.then(next), Promise.resolve())

const clearInput = (name: string) => {
  const el = element(by.css('input[name=' + name + ']'))
  return visibilityOf(el)
   .then(() => el.getAttribute('value'))
   .then((text) => {
      const keysArray = text.replace(/ /g, '').split('')
      keysArray.push('')
      return mapSerial((key: string) => setTimeout(() => el.sendKeys(Key.BACK_SPACE), 0), keysArray)
    })
   .then(() => browser.wait(() => el.getAttribute('value').then(text => text.length === 0), 12000))
   .then(() => el)
}

I tried your solution @evanjmg and I'm still stuck with the focused input. Not cleared, no new content append.

I can confirm this is still an issue with Angular 7.2.3 and Protractor 5.4.0 on 73.0.3683.103.

@wlingke thanks much, your solution worked for me too.

Hi @juliemr I can confirm, that .clear() is still not working fine. I'm testing a form and the only way of making the test to work is doing this:
    it('should run validations', async function () {       await browser.get('/#/login');       await password.sendKeys('a');       await password.sendKeys(protractor.Key.BACK_SPACE);       await username.click()       expect(await passwordError.getText()).toMatch('Pedo');     });

I had a similar issue with a directive I was using and sendKeys not updating the model. This solution worked for me though I am not sure if it will work for you all:
field.sendKeys(protractor.Key.chord(protractor.Key.CONTROL, "a"));
field.sendKeys(protractor.Key.BACK_SPACE);
field.clear();

Thanks a lot! 2019 and this is still the way to go :)

I had a similar issue recently. The workaround is to select all the existing text, use backspace to clear the text

Guys.. If the above solutions does not work for you, then try below. It works..
send empty string with single space.
field.sendKeys(' ');

Noticed this problem when we tried to test some validation. It all works manually but using setKeys and clear doesn't seem to affect Angular to mark the input as touched or dirty.
I wonder if there validation component we are using is loaded too slowly and isn't actually loaded by the time the test has filled out the form, it's only 2 inputs in my case. I'll run a delay test tomorrow and see if that fixes it.

authors: BalaSudheer EugeneSnihovsky Kungfoowiz collectivecognition evanjmg guillermosnipe kenborge manialpha martinstark maximelafarie satieh sebastianhaas tiboprea vlio20 vsravuri


text:
Protractor Java port

Protractor Java port to be used with Webdriver Java client.

It's unlikely that we're going to tackle this anytime soon, so I'm going to close this issue for now.

authors: gurvinderd juliemr


text:
"systemjs.config.js" not loaded (HTTP-GET-ERROR 404)

The actual version of angular-quickstart has this in index.html:
<script src="systemjs.config.js"></script>
Starting the server (npm start) and looking in dev tools shows that this file cannot be loaded (because of its filename):

However, it works, if I change the filename:
If I rename the file to "config.js" and reference it,
then script can be loaded and angular quickstart works:
<script src="config.js"></script>
The strange thing is that renaming the file to something like the following will result in the same problem (GET-Error 404):

"systemjs-config.js"
"systemjs_config.js"
"systemjsconfig.js"

Maybe because of the word "systemjs" or "*js.js" ?
So, I guess, renaming the file to "config.js" or something else, solves the problem.

First time ever I see that. Are you running it with our provided local server?

Are you running it with our provided local server?

I am using lite-server
coming from angular-quickstarts "package.json"
and start the server with npm start:
{
  "name": "angular-quickstart",
  "version": "1.0.0",
  "scripts": {
    "start": "tsc && concurrently \"tsc -w\" \"lite-server\" ",
    "lite": "lite-server",
    "tsc": "tsc",
    "tsc:w": "tsc -w"
  },
..

What you show does not look like the package.json from this repo. You can clearly see that there is a systemjs.config.js here and there is not a config.js here.
I'm attributing this issue to an error on your part and closing it. If you can demonstrate otherwise, I'm happy to reopen.

What you show does not look like the package.json from this repo. You can clearly see that this repo has a What you show does not look like the package.json from this repo. You can clearly see that this repo has a systemjs.config.js and there is no config.js file. and there is no config.js file.

I have to rename "systemjs.config.js" to "config.js" to make it work. I mentioned the reason above. It does NOT work when I use the name "systemjs.config.js". I included the original quickstart before renaming to "config.js".
angular-quickstart.zip

I tried it again to verify the case:

I am using "angular-quickstart.zip" as it is.
make "npm install"
make "npm start"

Server started:

I opend Safari (it does not matter, google chrome or firefox shows the same error) and get the 404-Error for "systemjs.config.js":

I have cleared all my caches and tried again. The same error with 'systemjs.config.js', it's only working when renaming this file. Strange.

There is something exotic in your environment. We cannot repro. I'm sorry but we have to keep this closed until there is a repro.

authors: Foxandxss nimo23 wardbell

repo: angular/quickstart


text:
don't export Zone constructor

Since zone.js is such a delicate system, it is important that users can interact with it only in a safe manner using only the apis we intend them to be using.
I'm not sure what's the full scope of this work but here are some items we should definitely do:

[ ] don't export the Zone constructor, users should use only zone.fork api to create new zones
[ ] hide or at least prefix all of the private instance methods (e.g. bind, bindOnce)
[ ] consider setting the constructor property in the Zone constructor to null
[ ] if constructor can't be reset to null on all browsers (works in Chrome), the hide all the patching helper fn that are on Zone fn
[ ] protect global.zone from being reset by non-authorized code (maybe via a setter?)
[ ] review any other places for api leakage

We should do our best to make Zone constructor inaccessible since the only way to properly instantiate a new zone is via forking. Using the constructor can only result in abuse of the apis.

Some of the visibility issues are resolved in #82.

Hi folks, so this is a confirmed usage restriction? We are required to rely on global.zone as a kind of "current thread" equivalent singleton reference, right?
For Browserify users like myself, could that singleton accessor be exposed in the module exports still? Could just help consistently avoid using global for stylistic reasons...
Thanks!

authors: IgorMinar unframework vicb


text:
feat(custom-element): patch customElement v1 APIs

Patch the CustomElement V1 APIs.
connectedCallback
disconnectedCallback
adoptedCallback
attributeChangedCallback

Make them run in the zone when they were defined by customElements.define.
So the issue like https://github.com/angular/angular/pull/24185 may be resolved by this one.
@robwormald, @mhevery, please review, thank you!

This is cool!  Does it play nice with the document-register-element polyfill (specifically 1.8.1)?

@remackgeek, I believe before this PR, zone.js already support legacy document.registerElement. So document-register-element polyfill will also be supported.

Which version will this issue be fixed ?

authors: JiaLiPassion krishna217 remackgeek


text:
fixed animesuge

Closes #665

It's because of this I guess:

For Cloudflare scraping either cfscrape or selenium is used. Cfscrape depends on node-js and selenium utilizes an automated invisible instance of a browser (chrome/firefox). So, if you want to use Cloudflare enabled sites, make sure you have node-js and a webdriver installed.

authors: ArjixGamer queeup

repo: anime-dl/anime-downloader

license: Unlicense


text:
Feb development

A bunch of varied development :)

adds location + zoom to areas (to define centre/zoom for an area)
adds locations to resources (to define point on a map to show it) and editing via wagtail
multi step river create form
nice location + precision widget
fix jumping scrolling
button to close main menu inside the menu
disable rotating/panning of map
add zoom controls to map
add map filters
rename "remix" module to "map"
update maptiler style

Brilliant work @nicksellen !

authors: nektdev nicksellen

repo: animorphcoop/shared-futures-space


text:
Linking with glob strips leading '.' from link name

Enviornment
OS: Ubuntu Mate 20.04.1
Python version: 3.8.2
dotbot version: 1.17.1 (yaml: 5.3)
Setup
Given a repository with this structure:
home/.bashrc
home/.profile
home/.vim
install
install.conf.yaml

with this install.conf.yaml:
- defaults:
    link:
        create: true
        force: true
        relink: true

- link:
    ~/:
        path: home/.*
        glob: true

Execution
running ./install -v produces this output:
Globbing with path: home/.*
Globs from 'home/.*': ['home/.vimrc', 'home/.profile', 'home/.bashrc']
Creating link ~/vimrc -> /home/erik/.dotfiles/home/.vimrc
Creating link ~/profile -> /home/erik/.dotfiles/home/.profile
Creating link ~/bashrc -> /home/erik/.dotfiles/home/.bashrc
All links have been set up

==> All tasks executed successfully

Running ls -l ~ confirms that the link names do not have the leading '.'. I
would expect the link name to keep the leading '.' (e.g. ~/.vimrc). I realize
that I can specify the links for these files individually, but this approach
is more work to maintain.
Remarks
If I change path: home/.* to be path: home/* based on the example from the
documentation, python glob module ignores files that start with '.'. Looking
more at how link.py works, it seems the problem might behere,
specifically how glob_item is set. I haven't put the code through a debugger
yet to confirm, but I think adding a check if glob_base has trailing '.',
then remove trailing '.'. This would cause glob_item to have the leading '.'.
I'll have some time tomorrow to try this.

Fixed by #245

authors: anishathalye etkeys

repo: anishathalye/dotbot


text:
FMovies, Seez, AllMoviesForYou & UHD Movies extensions are showing error when it tried to play any video

Source information
FMovies 13.14 , Seez 13.5 , AllMoviesForYou 13.12 , UHD Movies 13.17
Source language
English
Steps to reproduce
It's exactly same for all 4 extensions mentioned above. Just open any of the extension & try to play anything.
Expected behavior
The extensions should've played the video when I clicked on it.
Actual behavior
FMovies : When I tried to play any video, it's showing
"JsonDecodingException: Expected start of the object '{', but had 'EOF' instead at path: $
JSON input: .Server at 9anime.eltik.net Port 80</ address>
" error message

Seez :  The actual behaviour is exactly the same that was mentioned above in FMovies but I'm still adding the error pic here as well

Allmoviesforyou : When I tried to play any video, it's showing
"Video list is empty" error message

UHD Movies : When I tried to play any video, it's showing
"No working links found" error message

Aniyomi version
App version: 0.14.6-6697 (standard, 2b8000b81, 106, 2023-11-14T22:48Z) Android version: 12 (SDK 31) Android build ID: SKQ1.210821.001.WW_Phone-31.0210.0210.303-0 release-keys Device brand: asus Device manufacturer: asus Device name: ASUS_I003_1 Device model: ASUS_I003DD Device product name: WW_I003D
Android version
Android 12
Other details
These extensions are pretty much the big 4 extensions for movies in Aniyomi. All of them going down together is a big set back for a movie fan like me so please try to fix them at your earliest convenience.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.12.3.10.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Please open one issue for each source, as it makes it easier to keep track of things.

repo: aniyomiorg/aniyomi-extensions


text:
Make pghero work with postgres 11/12

Currentyl pghero.sql is not working ootb with postgres 11 & 12. This PR fixes this.

Hey @tboeghk, thanks for this PR and #8! I haven't used this project in a long time (and it seems neither have others based on this issue), so going to archive it. In the last commit, I've removed the waiting column so it'll work with more recent versions of Postgres as well as past versions.
As you've seen, the concept is pretty simple, so you can always release your own version.

authors: ankane tboeghk


text:
Return slices

No need to expose the Vec

Hi @njaard, thanks for the PRs. Happy to switch to slices in 0.3.0.

authors: ankane njaard

repo: ankane/stl-rust


text:
Why does Stylebot not work on chrome:// addresses?

Not sure whether this has been asked before, but I am trying to customise some chrome:// addresses. Sometimes, Stylebot will open the CSS editor, and I am able to make changes easily, but in most cases the editor can't be opened to edit the page. Is there restrictions on this? Because if there are, the aren't working very well...
Any response is much appreciated!

I'm not sure Chrome extensions can access internal browser pages - probably for security reasons.

The chrome:// addresses are not actually real uri, they are shortcuts to settings in the browser itself, and as such are not possible to be accessed by extensions. The addresses serve as redirection to the settings options in other words.
It would be a huge security risk if an extension could alter the content of the DOM elements of the browser locally.
While it would probably be possible to write an extension to hack this, the extension would need to be downloaded and installed by the owner of the machine on which Chrome is installed. Such an extension would never meet the Chrome Store criteria for acceptance, and the only place one might find such a thing to download would in "the wild". Basically it would be like deliberately downloading a trojan, so if you want to do something like this for personal use, you would need to code it yourself.

yes, afaik, chrome doesn't allow running content scripts on chrome:// urls

authors: AlexJohn73 ankit geckoseo speeditor

repo: ankit/stylebot


text:
🛑 zabbix24 is down

In 1aabfd8, zabbix24 (https://zabbix24.duckdns.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: zabbix24 is back up in 42fdcf2.


text:
🛑 mikrotik24 is down

In 11d3cfb, mikrotik24 (https://mikrotik24.duckdns.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mikrotik24 is back up in 981a84a after 38 minutes.


text:
add social media icons on mentor page

Description
add the social media icons on the mentor page
Screenshots

Additional information
No response

assigned you an issue! You can get assigned this when you complete that one. Or you have the choice to choose one. Thank you keep contributing.

i would want to work on this. please assign me this issue as soon as i complete the other one.

sure! but as of guidelines i cannot assign two issue to single person at one time.

i have finished working on this. if you could assign this task to me then i would be able to make aPR @anmode .
Meanwhile i am working on the other issue as well.

i have raised a pr on this issue. if you could please review and merge it @anmode .

Hii, i reviewed and left you some comments.... making you PR a good contribution

Hii, i reviewed and left you some comments.... making you PR a good contribution

yes thanks

authors: anmode ePSA-eJya

repo: anmode/grabtern-frontend


text:
Mico Develop Branch updates

This pull requests

merges fixes in the develop branch to mico develop
deactivates doclint for javadoc generation

Hope the last update will fix the JDK 7 build


text:
🛑 Pedtalant is down

In ea1d5ec, Pedtalant (https://педталант.рф) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pedtalant is back up in 76cfd9d after 2 hours, 1 minute.

repo: ano-pedproject/repo


text:
Tags and courses stored in DB

Functionally new

Tags and courses can be stored in the database
Unified the displayed results for different subclasses

Refactoring and code changes

Tags and courses implemented as their own classes
Renamed AbstractBookmark to Bookmark
Moved more common functionality to the shared Bookmark class, e.g. toString and constructor functionality
Changed concrete implementations to interfaces, where possible (ArrayList -> List as a parameter, for instance)
Created new methods for shared code in TextUI
Updated the tests to reflect the current state of the code
Created a Utilities class for general purpose constants and static methods. Added a method for decosntructing the tag and course inputs (strings separated by commas)

To do in this branch (database management)

A new tag is created from user input, even if a tag with that name already exists
many-to-many relationships use eager fetching, but it's probably possible to use lazy fetching and avoid errors, with some changes
Tests for tag and course functionality

Codecov Report

Merging #15 into master will increase coverage by 1.43%.
The diff coverage is 78.6%.

@@             Coverage Diff              @@
##             master      #15      +/-   ##
============================================
+ Coverage     69.67%   71.11%   +1.43%
- Complexity       61       87      +26
============================================
  Files            10       13       +3
  Lines           310      315       +5
  Branches         16       18       +2
============================================
+ Hits            216      224       +8
- Misses           86       89       +3
+ Partials          8        2       -6

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/bookmarks/BlogBookmark.java
100% <100%> (ø)
3 <3> (ø)
:arrow_down:

src/main/java/app/App.java
59.37% <100%> (ø)
6 <0> (ø)
:arrow_down:

src/main/java/bookmarks/VideoBookmark.java
100% <100%> (ø)
3 <3> (ø)
:arrow_down:

src/main/java/bookmarks/BookBookmark.java
92.3% <100%> (+5.94%)
4 <2> (+1)
:arrow_up:

src/main/java/bookmarks/PodcastBookmark.java
100% <100%> (ø)
3 <3> (ø)
:arrow_down:

src/main/java/app/domain/Course.java
27.27% <27.27%> (ø)
3 <3> (?)

src/main/java/app/domain/Tag.java
27.77% <27.77%> (ø)
3 <3> (?)

src/main/java/app/dao/BookMarkDAO.java
41.86% <60%> (+15.38%)
5 <0> (+3)
:arrow_up:

src/main/java/app/utilities/Utilities.java
87.5% <87.5%> (ø)
4 <4> (?)

src/main/java/bookmarks/Bookmark.java
95.91% <95.91%> (ø)
22 <22> (?)

... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70ff0dd...eb55f80. Read the comment docs.

authors: anonOstrich codecov-io

repo: anonOstrich/ohtu-miniprojekti


text:
FIX : the base rabbitMQ link won't work witout the terminal slash.

Closes #70

PR pour info, merge immédiat.

repo: ansforge/psc-admin-portal


text:
fix/functionaltests

based on the repo @lod started I tried to fix conflicts.
zuul might not be happy, though.

@tbugfinder Ping me once green, I will have to do a squash but ideally once you have it in right shape you should split it in several pull-requests, I will bypass CI for those if you do, so we endup with a better change history.

@tbugfinder please rebase or close if it no longer applies.

In fact I will close it because the last changes made to create makes this patch irrelevant. Reopen if needed and ping me on irc to get it reviewed faster.

authors: ssbarnea tbugfinder


text:
Molecule won't start Docker container - fatal: [centos8]: UNREACHABLE! => {"changed": false, "msg": "Authentication or permission failure ...

When run molecule test, I got the following error:
fatal: [centos8]: UNREACHABLE! => {"changed": false, "msg": "Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in "/tmp". Failed command was: ( umask 77 && mkdir -p "echo ~/.ansible/tmp/ansible-tmp-1602159340.7644343-138649041382011" && echo ansible-tmp-1602159340.7644343-138649041382011="` echo ~/.ansible/tmp/ansible-tmp-1602159340 exited with result 1", "unreachable": true}
After this failure, "docker ps -a" return nothing, which means no docker containers were started.
My platform is wsl 2 on Window 10
coomand "docker run hello-world" indicates the docker is working properly
the versions of pip and python are:  Python 3.8.5 and pip 20.0.2 from /usr/lib/python3/dist-packages/pip (python 3.8)
the molecule.yml:
dependency:
name: galaxy
driver:
name: docker
platforms:

name: centos7
image: geerlingguy/docker-centos7-ansible
provisioner:
name: ansible
verifier:
name: ansible

...

Can you try doing molecule create to create a docker instance and then molecule list to display the instance? You could also try going through the step by step test sequence commands listed in the "Run test sequence commands" section of the Getting Started Guide.

@larmbuster, the issue was resolved. skipping step create was caused by the states in molecule cache. after reset, everything is working now. Thanks for your helps!

@shanxijie Glad to hear you were able to figure it out!

Hi, i'm getting the exact same error message using molecule version 2.20.2.
If I run, molecule converge, molecule verify, molecule destroy separately, it works fine. I only seem to get the UNREACHABLE error when I use the molecule test command. I have nothing within my ~/.cache/molecule directory either.

authors: larmbuster rcooper85 shanxijie

repo: ansible-community/molecule


text:
Run fails when ssh not installed

Describe the Issue
Does not work without ssh package, does not respect ubtu18stig_ssh_required: false
Expected Behavior
All tasks relating to ssh should be skipped.
Actual Behavior
TASK [/home/user/UBUNTU18-STIG : HIGH | UBTU-18-010412 | PATCH | The Ubuntu operating system must enforce SSHv2 for network access to all accounts.]
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Destination /etc/ssh/sshd_config does not exist !", "rc": 257}

Control(s) Affected
010412
010420
010424
010411
010414
010415
010416
010417
010418
010419
010512
and possibly more, I gave up here.
Environment (please complete the following information):

devel (==main)
Ansible Version: 2.9.27
Host Python Version: 2.7.17 (old, I know)
Ansible Server Python Version: 2.7.17
Additional Details:
Ubuntu Desktop 18.04.5 LTS
ssh package NOT installed

Additional Notes
Steps to reproduce:

git clone https://github.com/ansible-lockdown/UBUNTU18-STIG
sed -i 's/ubtu18stig_ssh_required: true/ubtu18stig_ssh_required: false/' UBUNTU18-STIG/defaults/main.yml
ansible-playbook -D UBUNTU18-STIG/site.yml -i localhost, --connection=local -e "ansible_become_password=[password]" | tee stig.txt

Possible Solution
I ran these to get past the 10 failing tasks.
sed -i '/ubtu_18_010412/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat1.yml
sed -i '/ubtu_18_010420/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat1.yml
sed -i '/ubtu_18_010424/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat1.yml
sed -i '/ubtu_18_010411/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat2.yml
sed -i '/ubtu_18_010414/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat2.yml
sed -i '/ubtu_18_010415/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat2.yml
sed -i '/ubtu_18_010416/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat2.yml
sed -i '/ubtu_18_010417/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat2.yml
sed -i '/ubtu_18_010418/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat2.yml
sed -i '/ubtu_18_010419/a\      - ubtu18stig_ssh_required' UBUNTU18-STIG/tasks/fix-cat2.yml

But after all of that I still get this
TASK [/home/user/UBUNTU18-STIG : MEDIUM | UBTU-18-010512 | PATCH | The Ubuntu operating system must configure the uncomplicated firewall to rate-limit impacted network interfaces. | limit on service] *********************************************************************************************
failed: [localhost] (item=OpenSSH) => {"ansible_loop_var": "item", "changed": false, "commands": ["/usr/sbin/ufw status verbose", "/bin/grep -h '^### tuple' /lib/ufw/user.rules /lib/ufw/user6.rules /etc/ufw/user.rules /etc/ufw/user6.rules /var/lib/ufw/user.rules /var/lib/ufw/user6.rules", "/usr/sbin/ufw --version", "/usr/sbin/ufw limit from any to any app 'OpenSSH'"], "item": "OpenSSH", "msg": "ERROR: Could not find a profile matching 'OpenSSH'\n"}

I gave up at that point and resolved it with
sudo apt-get install -y ssh

It seems that this is just not setup to run on a system without ssh.

Sorry for the delay in this taking a look at it today and will address it.

This will be fixed in the upcoming release for v2r10 and that option will be removed, this was artifact from a old release.  If you would like to run the playbook you can either shut off the controls in the default/main file, or run your playbook ansible-playbook example.yml --skip-tags "ssh"


text:
Use with Controller Credentials

SUMMARY

It's not clear how the role or module can utilize a Controller credential, other than a "Vault" credential to unlock an encrypted value from a file.  Is there any documentation / guidance on how to use Controller credentials with this collection?  Other collections, like ansible.controller also use environment variables to pull in Controller authentication secrets - which are provided by the Red Hat Ansible Automation Platform Credential (type).
ISSUE TYPE

Bug Report

ANSIBLE VERSION

N/A
COLLECTION VERSION

v1.2.1

STEPS TO REPRODUCE

NA
EXPECTED RESULTS

Expect a way to pass in secrets to the role/module, using certain Environment variables and/or known (local) configuration - like those found in the cloud.openstack modules - so that Controller Credentials can be associated with playbook to create an appropriate Job Template.
If there were a set of associated environment variables, or an expected (configuration) file - then an custom Credential Type could created/used/provided - to store an appropriate credential to associate with role when used in a playbook.
ACTUAL RESULTS

N/A

@dkolepp Thanks for the issue.
How does the following environment variables sound?

REDHAT_CSP_USERNAME
REDHAT_CSP_PASSWORD

As a side note - what are the release plans, so that it is visible in Red Hat AutomationHub ?

repo: ansible-middleware/redhat-csp-download


text:
#554 changing export process to not include nodes from a sourced resource

If a group or host in an inventory is from a source we do not want to export the object as part of the inventory.

Coverage decreased (-0.06%) to 63.891% when pulling 6e9ff13f90cdd37c625bd867c0b9a16b80a1aa49 on john-westcott-iv:554-no-dynamic-host-or-groups into c9b983e6919c8fcf3bf760bb278d967a7dfc1f12 on ansible:master.

This will need to go in the CHANGELOG for 3.3.1

authors: AlanCoding coveralls john-westcott-iv

repo: ansible/tower-cli


text:
fix: limit and spinning of search icon

make sure you are searching by adding spinner
https://github.com/ansys/ansys-sphinx-theme/assets/104772255/03661c50-56b4-4dbc-a640-ed6eac864a53

Loving it.

repo: ansys/ansys-sphinx-theme


text:
Create a section in the documentation about how to freeze code

Description of the feature
How to create an executable in PyAEDT
Steps for implementing the feature
No response
Useful links and references
No response

Not needed

repo: ansys/pyaedt


text:
DOC: Update documentation

[x] Simplify sphinx cards on landing page
[x] Conda documentation fix
[x] Simplify cards in getting started and userguide
[x] Remove requirement.txt precommit check
[x] Align cards

Hi @dipinknair ,
Is this still a draft? I am going to create a new release now, just in case you want me to wait.

Thanks @dipinknair for updating the PyAEDT documentation.

authors: MaxJPRey Samuelopez-ansys dipinknair


text:
PLOTTING: change opacity for lighter color

Seems like #727 didn't solve the color issues we mentioned. Opacity works fine whenever there is something behind. We should use a grey, lighter color rather than pure black so that it does not look that intense.

Closed by #741

authors: AlejandroFernandezLuces RobPasMue

repo: ansys/pyansys-geometry


text:
Result animations don't work with the new pyvista default backend (trame)

🤓 Before submitting the issue

[X] I have visited the Troubleshooting section.
[X] I have searched among the existing issues.
[X] I am using a Python virtual environment.
[X] I am using the latest version of PyMAPDL and its dependencies (fully updated virtual environment). You can update them using pip install --upgrade --upgrade-strategy eager ansys-mapdl-core.

🔍 Description of the bug
The results object animation method is not compatible with the current backend that PyVista has switched to (trame). When trying to animate a solution (for example, from a nodal analysis)  with mapdl.result.animate_nodal_solution(0) the trame window gets stuck loading until you stop the execution. Once you do, a static mesh is opened in the trame window.
Animations with the notebook=False option remain operative, but one thing I have noticed is that the mapping of the colorscale to the animation stopped working a few versions ago (so, for example, if you have something vibrating, it will always show the color for 0 deformation, even if it does animate the displacements). add_text=Truehas also become less functional, as the text is barely readable.
🕵 Steps To Reproduce
Steps:

Make any simple model and run a modal analysis.
Animate modal results from the results object.

💻 Which Operating System are you using?
Windows
🐍 Which Python version are you using?
3.11
📝 PyMAPDL Report
'
📝 Installed packages
'
📝 Logger output file
No response

Hi @CesarRodriguezPereira
For me (running Python 3.11 in MacOS + docker, PyMAPDL remote mode) both show an animation:
result.animate_nodal_solution(0, show_displacement=True, displacement_factor=10)

and
result.animate_nodal_solution(0, show_displacement=True, displacement_factor=10,notebook=False)

but it gets stuck when I close the window (I need to issue ctrl + C). But I believe this is an MacOS issue.
@clatapie can you confirm this behaviour on Windows?

Hi @germa89
Regarding the animation within the notebook, I haven't been able to get it to work within a notebook in vscode, as it gets stuck loading. When trying it on jupyter notebook or jupyterlab I get no output, as it seems to have issues with widget state (but that may be my juypter environment lacking in configuration due to my use of VScode by default). I'll try to get trame working in the default notebooks (jupyter rather than vscode), to see if I can get more info on the issue (maybe the infinite loading has to do with how vscode handles the widget).
The issue you show when closing the window isn't MacOS related, and has been present at least since I started using the library (around january 2021), I always thought it was a vtk issue and not a pymapdl one. To be a bit more detailed with the behaviour, closing the window manually will kill the kernel, although stopping the cell execution won't (the window becomes unresponsive, as expected, but the kernel is still usable). Trying to close any of the windows (even old inactive ones) will prompt the user with killing the process python.exe, killing the kernel in the process.
My usual solution when performing modal analyses has always been "kill the cell through KeyboardInterrupt" (available at the push of a button in vscode), then launch another animation. Stack until you have so many windows that it's unmanageable, close it all, and repeat.

I have identify your issue also in default jupyter notebook. I will keep investigating

This bug is due to pymapdl-reader.. transferring and assigning it to @AlejandroFernandezLuces

repo: ansys/pymapdl