text:
100 integration testing with testcontainers

The changes in this PR provide abasis for running integration tests against different versions of Mastodon. I have provided setups for Mastodon 3.0.0, 4.0.2 and 4.1.0. More could be added if needed. Setups are based on Docker Compose. For more information on the setup or on how to run these tests, please check out https://github.com/andregasser/bigbone/wiki/Testing
This PR closes https://github.com/andregasser/bigbone/issues/100

@bocops Would be great if you could have a look at these changes. More details about how to test our code can be found here: https://github.com/andregasser/bigbone/wiki/Testing.

I couldn't immediately get Docker and the integration tests to run, but that might be a problem on my end. I got a "FATAL: database 'mastodon' does not exist" and then an exit with code 1 " container for service 'web' is unhealthy shortly thereafter. Looking into it.
Other than that, most of this looks good, I only have some small questions about the test constants and the scheme/port configuration changes to MastodonClient.Builder.

Sounds a bit like the 'db' container is not running correctly. When 'db' container is created, a user with DB-creation rights is created, but the database itself is created in the 'web' container using db:setup call.
you can send me your docker compose logs if you want then I'll have a look too.

Regarding the following methods:

withTrustAllCerts()
withPort()
withHttpsDisabled()

Clearly, withTrustAllCerts() and withHttpsDisabled should never be used in production setups (because they have a security impact). Ideally, a Mastodon instance always runs on the default SSL port 443, but I honestly have no clue whether this is always the case (certainly it would be good practice).
Maybe these methods still could be handy / useful for people who want to test out stuff.
So would it be ok for you, if we add a clear KDoc reminder to not use these methods in production setups?
Also, we could add a log.WARN in the code to advice against using this on prod.
Additional note for 'withPort(): At the moment, the local Mastodon instance running on Docker Compose is reachable via port 443, so in your browser you can just enter https://localhost` and you end up on the login screen of the Mastodon instance. While this is comfortable, I am not sure, if it is clever to occupy the 443 port locally, There are probably quite some devs that use this port to run some other web based services locally, That would cause port conflicts. So, if we switch to another port (e.g. 5000, we required this method).
Do you have any preference on how to proceed?

Sounds good - clear KDoc warnings should be good enough. :)

authors: andregasser bocops

repo: andregasser/bigbone


text:
Switch to po3's CommonLibSSE so it works for >1130

Switch Port over the build system to use cmake and vcpkg. Switch the easy dependencies over to vcpkg (Detours, CommonLibSSE's deps, SimpleIni, etc). This should allow it to work on the newer AE versions (works for me on 1130). Still need to scan the headers for correctness with later versions of CommonLibSSE, but a cursory glance of the addresses looks fine.
The reason I did this is that it appears that the CommonLibSSE-NG branch doesn't include many of the recent changes required for >1130, and would not start up.
This is the branch I pinned it to: https://github.com/powerof3/CommonLibSSE/tree/dev

Crashes on SE
Crash_2024_2_4_13-26-6.txt

source: gharchive/pull-request

authors: crajjjj tellett

license: MIT

license_type: permissive

license_source: github-api


text:
Please add support to select an item in a combo box

Hi. This is how I can select an item in a combo box using Xebium:
| ensure | do | select | on | id=status | with | label=Inconsistente |

How can I do the same with your fixture?

This is the mark-up we are trying to test against:

<select class="form-control ng-pristine ng-valid" id="status" ng-model="filtros.status" ng-options="opt.label | translate for opt in status">
<option class="ng-binding" value="">Todos</option>
<option value="0">Agendado</option>
<option value="1">Devolvido</option>
<option value="2">Enviado para pagamento</option>
<option value="3">Inconsistente</option>
<option value="4">Liquidado</option>
<option value="5">Parcial</option>
<option value="6">Pendente</option>
<option value="7">Vencido</option>
</select>

source: gharchive/issue

repo: andreptb/fitnesse-selenium-slim

license: mit

license_source: bigquery


text:
🛑 letr.app is down

In 93fb0f7, letr.app (https://letr.app) was down:

HTTP code: 0
Response time: 0 ms

Resolved: letr.app is back up in a47aa3a.

repo: andreruffert/up


text:
DAG fixes

Will need to change how 2D cals are done for chip specification. Right now it is just globbing.

yeah the glob has a comment above it that we will definitely need to switch that to a read + construct from the runlist.

authors: andrew-saydjari andycasey


text:
🛑 nhcam is down

In d0f0f05, nhcam ($NHIPCAM) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nhcam is back up in 83f42bf.

repo: andrewdavies-net/upptime


text:
🛑 nhcam is down

In 7c276ad, nhcam ($NHIPCAM) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nhcam is back up in 75c8c25.


text:
🛑 nhcam is down

In d9255ff, nhcam ($NHIPCAM) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nhcam is back up in 4ae632c.


text:
add keyword which refers to thing in most immediate scope

Proposed keyword: this
It refers to whatever thing is in most immediate scope.
Example:
const module = this;

fn factorial(x: i32) {
    if (x == 1) x else x * this(x)
}

const Node = struct {
    item: i32,
    next: &this,
};

struct MersenneTwister(
    int: type, n: usize, m: usize, r: int,
    a: int,
    u: int, d: int,
    s: int, b: int,
    t: int, c: int,
    l: int, f: int)
{
    const Self = this;

    array: [n]int,
    index: usize,

    pub fn init(self: &Self, seed: int) {
        module.factorial(seed);
        // ...
    }
}

Only having one way to do things is one of Zig's goals.

fn factorial(x: i32) {
    if (x == 1) x else x * this(x)
}

can already be done like
fn factorial(x: i32) {
    if (x == 1) x else x * factorial(x)
}

so there's no need to make another option. Structs could use the name of the type instead of declaring a variable.
struct MersenneTwister {
    // ...
    pub fn init(self: &MersenneTwister, seed: int) {
        module.factorial(seed);
        // ...
    }
}

The important example here is the anonymous struct:
const Node = struct {
    item: i32,
    next: &this,
};

We need this feature for #160 to work.
The other examples above I don't think would be idiomatic, just examples of the semantics of this feature.
Another example is https://github.com/andrewrk/zig/blob/0ae9023832584e256aa3b6df0f0829026141d21a/std/cstr.zig#L7
This const strlen = len;. Inside CBuf, len refers to a method, so you can't call the global len. If we did earlier const module = this; then you could do module.len.

Another use case for this is to make the language smaller and make annotations more powerful. For example, if we allow a block at the top level scope, we could do function annotations like this:
{@markAsTest(functionName)}
fn functionName() {
    // do the test...
}

With this you could potentially do this annotation inside the function:
fn functionName() {
    @markAsTest(this);
    // do the test
}

More importantly though we could have block-level attributes like this:
fn someFunction() {
    // some normal code...
    {
        @setDebugSafety(this, false);
        // some fast unsafe code
    }
    // some more normal code...
}

Here, this refers to a block, and setDebugSafety builtin function disables debug safety mechanisms only for the block that it is in.
With this strategy we could get rid of the compiler directive syntax and make the language smaller.

what would @typeOf({this}) be? a block scope metatatype instantiation? what would be the members of {this}? perhaps .parent? perhaps .declarations which contains a member for each var/const/ect declared in that scope? if all this sounds good, then the factorial example above is inconsistent. this in a function should not refer to the function, but the main block scope in the function body. this means you can't this(x - 1), so that resolves the rule of orthogonality violation.
but also, what the hell is the point of the features i just described? do we really need all this? if all that is the cost of removing annotations, i think the goal of making the language smaller fails. what's really the problem we're trying to solve with this issue?
for the MersenneTwister example (the original one) the benefit is not having to repeat all the template parameters if you want to refer to your own type. this is a good thing imo, because I'm still shuddering from the horrors of function signature duplication between .c and .h files. but a competing proposal for this usecase is to simply define Self in every struct declaration implicitly. (i don't believe that proposal has an issue number yet.)
another usecase is the const strlen = len; example. I've been arguing all along that the problem there is with the names, not with the language. i think the so-called len function should either be called strlen, a reference to c, or how about findNullTerminator. the second example follows the pattern (which i don't know if I've seen explicitly spelled out) that functions should be verbs unless they're O(1) getters, in which case they can be nouns.
in short, what (possibly) compelling usecases do we really have for this issue?

but also, what the hell is the point of the features i just described? do we really need all this?

I don't think we want all the features you described. I think @typeOf({this}) would be (block) and doing pretty much anything with that type other than calling a few builtin functions on it would be a compile error.

what's really the problem we're trying to solve with this issue?
in short, what (possibly) compelling usecases do we really have for this issue?

Get reference to container type inside it without it having to explicitly name it so that anonymous types can work. In this regard this is like the Self proposal but more general purpose, so that the additional following use cases are solved.
Annotations can work with existing builtin function syntax instead of #attribute(...) special syntax.
Annotations can target blocks of code instead of only functions and declarations, and participate in logic constructs such as an if-then statement with a condition on a compile time variable.
Ability to refer to module-level declarations when shadowed by local declarations. (strlen is a bad example since the validity of the name is in question, but I claim that the issue still stands)

Your point seems to be that this drags in all this other meta programming baggage, but I don't see why that has to be the case.

ok, good points. I'm probably doing a little too much exploration, but you brought up another point that i missed: safety and other annotations having conditional logic. here goes some more exploration!
is it possible to refer to a block while outside it? i believe the syntax as proposed makes that only possible if the block is the return value from the block (const block = {foo(); this};), which means you'd probably want to always annotate your blocks inside the block, instead of after the block, and therefore we might want to make this a restriction to have more orthogonality. this restriction would come in the form of forbidding a block value to escape it's block scope.
naming a block value into a const is still useful if you're conditional logic wants to be written with more blocks; for example:
fn foo() {
  var x: u32 = 100;
  while (x != 0) {
    const block = this;
    if (gotta_go_fast) {
      @annotate(block, "unsafe");
      if (is_posix) {
        disableInterrupts();
      }
    }
    print(x);
    x -= 1;
  }
}

More exploration!
fn foo() {
    const block_result = {
        const outer_block = this;
        if (blah) {
            while (true) {
                const outer_while = this;
                while (true) {
                    if (something) {
                        break outer_while;
                    } else {
                        @returnFromBlock(outer_block, 1234);
                    }
                }
            }
        } else {
            5678
        }
    };
}

authors: andrewrk phase thejoshwolfe

repo: andrewrk/zig


text:
Parsing error: Unexpected character '@'

Hi, I'm using webpack, babel-loader and the following webpack.config.js
...
module: {
        preLoaders: [{
            test: /\.js$/,
            loader: "eslint?fix=true&configFile=.eslintrc.webpack.json",
            exclude: /(node_modules|bower_components)/
        }],
        loaders: [{
            test: /\.jsx?$/,
            exclude: /(node_modules|bower_components)/,
            loader: 'babel', // 'babel-loader' is also a legal name to reference
            query: {
                presets: [
                    'es2015',
                    'react',
                    'stage-0'
                ],
                plugins: [
                    'lodash',
                    'transform-decorators-legacy',
                    'export-default-module-exports',
                    ['transform-es2015-modules-commonjs-simple', {
                        noMangle: true
                    }]
                ],
                compact: false,
                sourceMaps: true
            }
        },
...

I have no .babelrc.
However, when I run webpack, it complains about the @ syntax.
Reproducable with the following file:

// Vendors
const React = require('react');
import autobind from 'autobind-decorator'

@autobind
class AccountSettingsInputContainer extends React.Component {

}
export default AccountSettingsInputContainer;

Package.json includes:
"autobind-decorator": "^1.3.3",
    "autoprefixer": "^6.3.6",
    "babel-cli": "^6.10.1",
    "babel-core": "^6.9.0",
    "babel-loader": "^6.2.4",
    "babel-plugin-autobind-class-methods": "^1.0.4",
    "babel-plugin-export-default-module-exports": "^0.0.4",
    "babel-plugin-lodash": "^3.2.0",
    "babel-plugin-transform-decorators-legacy": "^1.3.4",
    "babel-plugin-transform-es2015-modules-commonjs-simple": "^6.7.4",
    "babel-polyfill": "^6.9.0",
    "babel-preset-es2015": "^6.9.0",
    "babel-preset-react": "^6.5.0",
    "babel-preset-stage-0": "^6.5.0",

I thought stage-0 was supposed to give me the ability to write:
class ClassName extends Other {
    boundMethod = () => {
        // ...
    }
}

But I can't do that, either. Wondering if it just isn't something in my config. Anyone notice anything odd?

Hello, run npm install babel-eslint --save-dev and add this setting to your package.json
 "standard": {     "parser": "babel-eslint"   },
reference: http://standardjs.com/#can-i-use-a-custom-js-parser-for-bleeding-edge-es6-or-es7-support

what the hell, this is so random
but it works. Thank you so much @lehcosta

authors: ThaJay jfeldstein lehcosta

repo: andreypopp/autobind-decorator


text:
Sending multipart with custom boundary string

how can i sending multi part form data with custom boundary string?

Boundary string is set within library/src/main/java/com/loopj/android/http/SimpleMultipartEntity.java without option to change it, so the only way is to use custom HttpEntity and send that, instead of using built-in one

authors: devflow smarek

repo: android-async-http/android-async-http


text:
[问答]我的手机刷的CM，想刷入个推送框架

谁家的推送可以通过recovery刷入手机？不用这帮国产应用天天启动一堆service，占用几百兆的内存，耗死手机。

感觉你应该不太明白这个，推送的SDK是APP选择集成的。其实小米华为的系统都做过这工作，假如你要使用的APP在小米华为的Rom上没有用小米华为的推送，那他们必然相互唤醒，或者一睡不醒。

@JingleDingDang 我是问有没有山寨版的google services framework

试试 http://opengapps.org/

authors: BBBOND JingleDingDang lbp0200

repo: android-cn/android-discuss


text:
🛑 Yourls Link-Shortener - cs.ugoe.de is down

In 48c5665, Yourls Link-Shortener - cs.ugoe.de (http://cs.ugoe.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Yourls Link-Shortener - cs.ugoe.de is back up in d4975ca.

repo: androtelema/upptime


text:
moquette.bat has an invalid character on line 85 causing it to fail to startup.

Description:
On Windows 10, attempting to run .\moquette.bat causes the following failure message and does not start:
Console Output:
F:\Applications\moquette\distribution-0.10-bundle-tar\bin>.\moquette.bat
"                                                                         "
"  ___  ___                       _   _        ___  ________ _____ _____  "
"  |  /  |                      | | | |       |  /  |  _  |_   | | "
"  | .  . | ___   __ _ _   _  | || | ___  | .  . | | | | | |   | |   "
"  | |/| |/ _ \ / \ | | | |/ _ \ __| __/ _ \ | |/| | | | | | |   | |   "
"  | |  | | () | (| | || |  / || ||  __/ | |  | \ /' / | |   | |   "
"  _|  |/_/ _, |_,|___|_|____| _|  |/_/_\ _/   _/   "
"                   | |                                                   "
"                   |_|                                                   "
"                                                                         "
Using JAVA_HOME:       "C:\Program Files\Java\jdk1.8.0_144"
Using MOQUETTE_HOME:   "F:\Applications\moquette\distribution-0.10-bundle-tar"
Improperly specified VM option 'GCLogFileSize=10M -XX:+HeapDumpOnOutOfMemoryError -Djava.awt.headless=true -Dlog4j.configuration=file:F:\Applications\moquette\distribution-0.10-bundle-tar\config\moquette-log.properties -Dmoquette.path=F:\Applications\moquette\distribution-0.10-bundle-tar -cp F:\Applications\moquette\distribution-0.10-bundle-tar\lib* io.moquette.server.Server'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Version  Info
Moquette Version: 0.10
Java Version 1.8.0_144
NOTE: Also incorporated changes committed with the fix for Issue #331
This fixed the warnings about the invalid '#' chars - but did not fix the underlying issue with the JVM Option being invalid.
Cause:
There is a trailing double-quote (") character on line 85 of moquette.bat.
Removing this double-quote from the file allows Moquette to start perfectly.

moquette的副本.txt
this bat shell should be ok

download this file
rename to moquette.bat
run it on windows os

Fixed with b1aa0019b25c3a84de921f34b05318777edaefe7

authors: andsel justinmtilley rongwei84n

repo: andsel/moquette


text:
Upstream Connection Rebalancing

Say you have a cluster with 3 nodes, where each node has 1000 upstream connections. If those nodes are becoming overloaded you may increase the number of replicas (either manually or with autoscaling).
Currently, if you add 3 more nodes, you'll end up with 3 nodes having 1000 upstream connections and 3 nodes with 0 upstream connections. Therefore Piko should rebalance upstream connections.
As Piko is designed to be hosted behind a load balancer, if a node drops the connection to an upstream service, that service will reconnect to a random node. Therefore when nodes find they have far more connections than the average for the cluster, then can gradually shed connections to upstreams which will then reconnect to a random node, rebalancing the cluster.
Such as in the above example, the average number of connections across the 6 nodes is 500, but the first three nodes all have 1000 connections each. The threshold and rate of shed connections can be configurable, such as shedding if you have 20% more connections than the cluster average, and shedding 0.5% of connections every second.

So this can include server configuration:

--rebalance.threshold: Threshold to start rebalancing, where each node will rebalance if it's number of upstream connections exceeds the cluster average by the threshold (probably with a default of 0 to disable rebalancing)

This should also avoid shedding if a node has very few connections (such if theres only 5 connections in the cluster don't rebalance)

--rebalance.shed-rate: Rate each node should shed connections if it exceeds the threshold (default 0.005?)

repo: andydunstall/piko


text:
Update sbt-scoverage to 1.7.1

Updates org.scoverage:sbt-scoverage from 1.7.0 to 1.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-patch

Superseded by #89.

repo: andyglow/websocket-scala-client


text:
DefaultTraverse doesn't pass all Traverse laws

It's possible that I'm doing something silly here, but I thought that I would report in case that's not what's happening. Either way, it would probably be good for droste to be doing more law-checking in tests.
Consider the following simple data type:
import cats.implicits._
import qq.droste.util.DefaultTraverse
import cats.{Applicative, Eq, Traverse}
import org.scalacheck.Arbitrary

final case class Pair[A](l: A, r: A)

object Pair {

  implicit val traversePair: Traverse[Pair] = new DefaultTraverse[Pair] {
    def traverse[G[_], A, B](fa: Pair[A])(f: A => G[B])(implicit G: Applicative[G]): G[Pair[B]] =
      G.map2(f(fa.l), f(fa.r))(Pair(_, _))
  }

  implicit def eqPair[A](implicit eqA: Eq[A]): Eq[Pair[A]] = Eq.instance((p1, p2) =>
    p1.l === p2.l && p1.r === p2.r
  )
}

Now run the following test:
import cats.tests.CatsSuite
import cats.laws.discipline.TraverseTests

class DefaultTraverseTests extends CatsSuite {
  implicit def arbPair[A](implicit arbA: Arbitrary[A]): Arbitrary[Pair[A]] = Arbitrary(
    arbA.arbitrary.flatMap(a1 => arbA.arbitrary.map(a2 => Pair(a1, a2))))

  checkAll("Pair", TraverseTests[Pair].traverse[Int, Int, Int, Set[Int], Option, Option])
}

The collectFirstSome and foldM identity laws consistently fail. Here is some example output:
- Pair.traverse.collectFirstSome reference *** FAILED ***
  GeneratorDrivenPropertyCheckFailedException was thrown during property evaluation.
   (Discipline.scala:14)
    Falsified after 10 successful property evaluations.
    Location: (Discipline.scala:14)
    Occurred when passed generated values (
      arg0 = Pair(1,1284725810),
      arg1 = org.scalacheck.GenArities$$Lambda$11995/1290092155@1195eb5b
    )
    Label of failing property:
      Expected: Some(Set())
  Received: Some(Set(-1))
- Pair.traverse.foldM identity *** FAILED ***
  GeneratorDrivenPropertyCheckFailedException was thrown during property evaluation.
   (Discipline.scala:14)
    Falsified after 5 successful property evaluations.
    Location: (Discipline.scala:14)
    Occurred when passed generated values (
      arg0 = Pair(0,2147483647),
      arg1 = Set(2061683075),
      arg2 = org.scalacheck.GenArities$$Lambda$12122/454406410@5b35771c
    )
    Label of failing property:
      Expected: Set()
  Received: Set(-225533737)

Both of these are ultimately implemented in terms of foldRight, so I suspect that there is an issue with the DefaultTraverse.foldRight implementation.

I believe this issue was resolved in #81, as the test has been ported over and is now passing. Happy to reopen this issue if we need to.

authors: andyscott ceedubs

repo: andyscott/droste


text:
extract vdex-010 got error

it is android 8 (api 27)
vdexExtractor -i services.vdex -o vdex -v 4
[INFO] Processing 1 file(s) from services.vdex
[DEBUG] [39536] 2024/01/23 12:07:29 (vdexExtractor.c:224 main) Processing 'services.vdex'
[DEBUG] [39536] 2024/01/23 12:07:29 (vdex_api.c:43 vdexApi_initEnv) Initializing environment for Vdex version '010'
------ Vdex Header Info ------
magic header & version      : vdex-010
number of dex files         : 1 (1)
dex size (overall)          : 86686c (8808556)
verifier dependencies size  : 126c4 (75460)
verifier dependencies offset: 866888 (8808584)
quickening info size        : 9da (2522)
quickening info offset      : 878f4c (8884044)
dex files info              :
  [0] location checksum : 3546dbe1 (893836257)
---- EOF Vdex Header Info ----
[DEBUG] [39536] 2024/01/23 12:07:29 (vdex/vdex_010.c:76 vdex_010_GetNextDexFileData) Processing first Dex file at offset:0x1c
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:622 dex_dumpHeaderInfo) ------ Dex Header Info ------
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:624 dex_dumpHeaderInfo) magic        : dex-038
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:629 dex_dumpHeaderInfo) checksum     : d2ad2477 (3534562423)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:630 dex_dumpHeaderInfo) signature    : f91d1d44709e25730f2a5966e61b5d3dbaffac2c
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:632 dex_dumpHeaderInfo) fileSize     : 86686c (8808556)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:634 dex_dumpHeaderInfo) headerSize   : 70 (112)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:636 dex_dumpHeaderInfo) endianTag    : 12345678 (305419896)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:638 dex_dumpHeaderInfo) linkSize     : 0 (0)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:640 dex_dumpHeaderInfo) linkOff      : 0 (0)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:642 dex_dumpHeaderInfo) mapOff       : 86679c (8808348)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:644 dex_dumpHeaderInfo) stringIdsSize: 139d9 (80345)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:646 dex_dumpHeaderInfo) stringIdsOff : 70 (112)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:648 dex_dumpHeaderInfo) typeIdsSize  : 17b3 (6067)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:650 dex_dumpHeaderInfo) typeIdsOff   : 4e7d4 (321492)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:652 dex_dumpHeaderInfo) protoIdsSize : 2fab (12203)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:654 dex_dumpHeaderInfo) protoIdsOff  : 546a0 (345760)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:656 dex_dumpHeaderInfo) fieldIdsSize : 5f9d (24477)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:658 dex_dumpHeaderInfo) fieldIdsOff  : 782a4 (492196)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:660 dex_dumpHeaderInfo) methodIdsSize: b058 (45144)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:662 dex_dumpHeaderInfo) methodIdsOff : a7f8c (688012)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:664 dex_dumpHeaderInfo) classDefsSize: e9d (3741)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:666 dex_dumpHeaderInfo) classDefsOff : 10024c (1049164)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:668 dex_dumpHeaderInfo) dataSize     : 7494e0 (7640288)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:670 dex_dumpHeaderInfo) dataOff      : 11d5ec (1168876)
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:687 dex_dumpHeaderInfo) -----------------------------
[DEBUG] [39536] 2024/01/23 12:07:29 (dex.c:373 dex_isValidDex) Dex version '038' detected
[FATAL] [39536] 2024/01/23 12:07:29 (dex.c:836 dex_getStringId) ((idx)) < ((dex_getStringIdsSize(dexFileBuf)))

here is the file
services.zip
please help, thanks

Are you sure this is a correct vdex file and can be executed?

Are you sure this is a correct vdex file and can be executed?

这是一个从一个车机系统(Android 8.1)上导出的文件，不确定是否可执行。导出路径为/system/oat/arm64/services.vdex

我昨天调试了一下，发现dex里面的字符串的idx会有负数的情况，很奇怪，要么就是这不是一个正常的文件，要么就是被混淆了，现在无法确认属于那种清晰

我昨天调试了一下，发现dex里面的字符串的idx会有负数的情况，很奇怪，要么就是这不是一个正常的文件，要么就是被混淆了，现在无法确认属于那种情形

方便留个联系方式吗  我重新导出发给你看一下

我的id，gmail邮箱

authors: hongwanli ohyeah521 swearl

repo: anestisb/vdexExtractor


text:
group middleware not working in angel_framework 2.1.1

group middleware not working in angel_framework 2.1.1
middleware is not being called
  app.group(
      AppConfig.basePath, (Router router) {
        router.get('/notifications/latest', NotificationController.getLatest);
      },
      middleware: [
        (RequestContext req, ResponseContext res) async {
          res.json({'message': 'access not authorised'});
          return false;
        }
      ],
    );

Use app.chain().group(...)

Thank you for indicating a solution.
I was going to suggest modifying line 164 of the router.dart file with that.
/// Creates a route, and allows you to add child routes to it
  /// via a [Router] instance.
  ///
  /// Returns the created route.
  /// You can also register middleware within the router.
  SymlinkRoute<T> group(String path, void Function(Router<T> router) callback, {Iterable<T> middleware, String name}) {
    //from this
    // middleware ??= <T>[];
    // final router = Router<T>().._middleware.addAll(middleware);
    //Isaque changed it here
    //to this
    final router = Router<T>();
    callback(router);
    if (middleware != null) {
      router._routes.forEach((element) {
        element.handlers.insertAll(0, middleware);
      });
    }
    return mount(path, router)..name = name;
  }

I will follow up with your solution

authors: insinfo thosakwe

repo: angel-dart/angel


text:
Persistent issues with prefs:root=Tweaks&path=x URLs

I know you're already aware of this issue, but do you think something similar to this (but not so atrocious) would work?

-(void) preferenceOrganizerOpenTweakPane:(NSString *)name {
    for (PSSpecifier *specifier in TweakSpecifiers) {
        if ( [[specifier name] caseInsensitiveCompare:[name stringByRemovingPercentEncoding]] == NSOrderedSame ) {
            [[[self rootController] navigationController] pushViewController:[[specifier target] controllerForSpecifier:specifier] animated:NO];
            break;
        }
    }
}

Crap, posted with wrong GitHub account.

I opened this issue under the wrong account, but if you consider looping the specifiers viable, I will go ahead and clean this up, write an iOS 6 compatible NSString extension method for stringByRemovingPercentEncoding, and follow the iOS call sequence when launching a nested panel via a URL to make the logic consistent with iOS' behavior, and issue a pull request.

Anyway, this much simpler approach works fine on iOS 9.  Have not tested anywhere else yet.

Merged #24, though I haven't tested functionality yet, so not closing this issue (or pushing a binary release to the repo) yet.

Yeah, of course.  I'd like to see if I can prevent the need for a sharedInstance on the TweakSpecifiersController, but in any case, I'll see if I can refine it in the next couple of days.  I'm hosting a fork on my repo, because I'm in beta on a tweak that basically depends on it, so I should have some feedback and testing hours shortly.

Just figured out the way to really do this with InspectiveC.  Much less readable to my eye, but it actually functions the way that the Preferences app does for nested specifiers.  Doesn't require a sharedInstance of the TweakSpecifiersController or manipulating the nav stack.  Will issue another pull request in the next day or so.

After receiving feedback from users, the general perception was that doing it the more efficient way produced an undesirable visual animation.  Happy with where things stand at this point.

authors: angelXwind billybooth fecaleagle


text:
🛑 SANDBOX is down

In cd0b4a8, SANDBOX (https://sandbox.moneybox.business) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SANDBOX is back up in 71b0d56.


text:
Is there a way to detect if someones in preview mode?

I'm thinking of displaying warning messages which a user doesn't add an ALT tag to images (think red border around the images etc) but I want this to only appear when a website is in preview 'mode' so that real users can't see the glaring red box when live.
Is there a variable, hook or anything which tell me in in a preview state?

Hey @jodiedoubleday, that's a good idea. Right now, the withPreview HOC does not pass a isPreview prop down to the page. This will be provided in the next version of the plugin exactly for cases like you described.
In the mean time, you should be able to use the usePreviewStore hook in your component to read into the root-level state. Something like the following should work:
import { usePrismicStore } from 'gatsby-source-prismic'

const MyPage = ({ data }) => {
  const [prismicPreviewState] = usePrismicStore()
  const isPreview = prismicPreviewState.enabled

  return (

  )
}

export default withPreview(MyPage, {
  // your options
})

Hey @jodiedoubleday, that's a good idea. Right now, the withPreview HOC does not pass a isPreview prop down to the page. This will be provided in the next version of the plugin exactly for cases like you described.
In the mean time, you should be able to use the usePreviewStore hook in your component to read into the root-level state. Something like the following should work:
import { usePrismicStore } from 'gatsby-source-prismic'

const MyPage = ({ data }) => {
  const [prismicPreviewState] = usePrismicStore()
  const isPreview = prismicPreviewState.enabled

  return (

  )
}

export default withPreview(MyPage, {
  // your options
})

Thanks @angeloashmore this looks great. and looking forward to V4 the roadmap looks great!

Thanks @angeloashmore this looks great. and looking forward to V4 the roadmap looks great!

authors: angeloashmore jodiedoubleday

repo: angeloashmore/gatsby-source-prismic


text:
feat:  Adicionar suporte a multi-idioma

Team Debuguers
777-  Teve problemas de conflitos com a Pull Request passada, que resolvia a issue feat: Adicionar suporte a novos idiomas #8,  e acabou por ser fechada, quando ignorou-se os commit para resolver o confiltos.
Com isso criou-se essa nova Pull Request,  para resolver a issue #8
@aosccode

777- @antonio-pedro99  feito...

@antonio-pedro99
@Danguya

E para finalizar, o i18n, podiam ter criado um hook, ou criado um state manager global para evitar imports do i18n por todo lado, ficaria responsabilidade do hook ou do state manager.
Mas gostei, estão de parabéns. 💯

777- Mesmo se o state Manage global fosse criado,  ele deveria ser chamado em toda parte da aplicação  que precisasse ser traduzida, é semelhante ao Provider e o Context, importas o provider uma vez, mas chamas o context em toda parte que vai lhe utilizar.
Quanto mais legível o código estar melhor,  acredito que se estivesses para adicionar por exemplo Mandarim, farias bwe rápido até beber água seria difícil 😁😁

E para finalizar, o i18n, podiam ter criado um hook, ou criado um state manager global para evitar imports do i18n por todo lado, ficaria responsabilidade do hook ou do state manager.
Mas gostei, estão de parabéns. 💯

777- Mesmo se o state Manage global fosse criado, ele deveria ser chamado em toda parte da aplicação que precisasse ser traduzida, é semelhante ao Provider e o Context, importas o provider uma vez, mas chamas o context em toda parte que vai lhe utilizar.
Quanto mais legível o código estar melhor, acredito que se estivesses para adicionar por exemplo Mandarim, farias bwe rápido até beber água seria difícil 😁😁
Obrigado pelo feedback 🤝🤝

Sim, mas é diferente, porque o Context por exemplo é nativo e global, o i18n aí não é, é uma dependencia, imagina que um dia mudas de i18n para uma cena qualquer, vais ter que mudar em várias páginas e lugares, mas se usares um Contexto por exemplo, terias de mudar apenas no contexto que importa isso, e é sobre isso. Manutenção e pensar no futuro.

authors: Afranioalves sombo20 trupakufi


text:
demo does not work on FF

FF displays Error: $event.srcElement is undefined when trying to drag any item

I'm getting different errors while trying the demo on firefox.

SyntaxError: missing } after function bodydraganddrop.js:1:4161
Error: No module: ngDragDrop
angular.js:1148:17
SyntaxError: missing } in compound statementdraganddrop.js:1:4870
Error: No module: ngDragDrop

In plunker, everything works as expected.
I'm using firefox version 49.0.2
@akurg: Could you try the demo on plunker and update what happens then?

authors: Roshanjossey akurg

repo: angular-dragdrop/angular-dragdrop


text:
Redux batch middleware not working correctly

Hey, i was trying to use @manaflair/redux-batch enhancer with store, and its not working as expected.
The problem is that store selectors are called every actions, for example if 5 actions are batched selectors are called 5 times. Its only happening when using select, when using subscribe exposed by store it works fine. Redux allows to manage when listeners are called, but using select takes away this flexibility, which is a problem.
Since in application im working on it was causing performance issue we had to implement a way around this, we really did not want to give up select since its used all over, we modified it a little:
const overrideSelect = (ngRedux: NgRedux) => {
const result$ = new BehaviorSubject(undefined);
ngRedux.subscribe(() => result$.next(undefined));
ngRedux['_store$'] = ngRedux['_store$'].sample(result$)
};
this way the subscribe dictates when selectors are called.

So each call to select generates a new subscription? When to those get cleaned up?

I'd have to dig into the implementation of redux-batch to see if it handles using redux as an observable or if it just patches the regular subscription mechanism.
One alternative in your case might be to call select with one of RxJS's buffering operators?

about solution i shared its done only on bootstrap.
Middleware i reported not working correctly is using subscription mechanism. Lets say you want to dispatch 5 actions, you would like your selectors to be called only once, after final state change. This is build in into redux-batch middleware, there are many implementation of that so ill share the example one : https://github.com/manaflair/redux-batch

OK yeah I reproduced the issue here https://github.com/SethDavenport/redux-batch-example and finally found time to dig into it a little more.
The problem is that redux-batch works by overriding the way redux manages subscribe and listeners. In particular, redux-batch appears to keep its own list of listeners from its own version of subscribe. However, patching store.subscribe is in my opinion insufficient as an abstraction, because since Redux 3.5 there's an observable-based mechanism than needs to be patched as well.
Your solution is interesting; however I don't think angular-redux is the right place for this since subscribe(() => result$.next()) effectively duplicates a mechanism already provided internally to redux.
Let me see if I can come up with a PR to redux-batch.

On second though - redux Store.observable() isn't a fully-fledged RxJS observable, which is resulting in some interop problems.  I can bake the non-sample portion of your solution into how we observablify the store - see #397.
@olaf89 give @angular-redux/store@6.3.0-alpha.0 and let me know.

I confirm it is solving the problem. Thanks!

repo: angular-redux/store


text:
Promise returned $translate.refresh() never gets rejected in case of XHR failure

https://github.com/angular-translate/angular-translate/blob/1aaab980760f8863551598ed748d200f1f03d9c6/src/service/translate.js#L1805 does not handle the case when $q.all() gets rejected.
I'm loading translation files lazily in the UI Router, so any missing unavailable / translation files will freeze the UI as the promise never gets rejected and the dependency does not get resolved in any way.
Would be great if refresh() would correctly reject the promise in case $.all() fails, this way one could at least implement a error message or implement other fallback logic.

It looks like this code was broken in this commit https://github.com/angular-translate/angular-translate/commit/aa5f5c979410f22bc821f88cfd3ec4a7938475f6. So we, probably, have to add tests for this case.

We should do something - maybe a pluggable solution / handler is indeed the best solution as the handling will differ from case to case (esp. with fallbacks missing...).
But I'm wondering, that it will freeze on missing files? (404 case)

@tspaeth $translate itself doesn't freeze, but anything that expects $translate.refresh() to eventually get resolved / rejected will (in this case it's ui-router where the state change will never finish and the App gets hung up after clicking on a link etc.).
I initially ran into the 404 problem when I was trying to both give $translate a list of known language and then let it figure out the preferred language of the user. It ended up adding two languages to the internal fallback list, trying to request both and since one of them didn't exist, it never resolved $translate.refresh(), again freezing ui-router.
While $translate will use one of known

Right, a catch case is missing here.

There was an event emitting in the old version of the code. Do we have to restore it as well?

Missing reject  applied in  5a85a64

authors: BonsaiDen DWand knalli tspaeth

repo: angular-translate/angular-translate


text:
[ui.bootstrap.pagination] Make first page index at 0 rather than 1

As documented, pagination settings takes a ng-model with a 1-based index , what's really confusing for a code-based approach.
I think it will be better to make it 0-based, as when your looking for the first page in a pages[n] Array, your not taking it at pages[1] but pages[0]

It should be noted that this request is a breaking change, and would depart from the typical use case with paginated api.
I am not sure if I agree that this is desired given that. Thoguhts?

I agree with wesleycho.  Pagination typically uses a 1-based approach.  A 1-based approach also matches the view behaviour, which imho is appropriate for view controls.  A 0-based approach may, and in most cases would, match the model, but on balance I would prefer 1-based here.

Closing as this does not appear to be a change that is desired in this project.

Is it better to make it configurable? default value is 1 based but can be configured as 0 based

authors: F2X stuart-harris wesleycho xiaolei

repo: angular-ui/bootstrap


text:
(Request): expose itemsPerPage inside uibPaging

Hello,
would it be possible to add itemsPerPage to the scope, so that it can be used inside a pager template?
My use case is I need to be able to display the pager as follows: "Previous 30 of 100 Next"
Thanks!

It is already available on the controller - wouldn't that be enough, since the pager component is using controllerAs?

Looks like this is already possible - see here

Sorry I missed your previous comment. You are absolutely correct, it is already supported. Thanks!


text:
feat(accordion): support events from collapse in accordion

Enable usage of collapse events of collapsed, collapsing, expanded, and expanding in accordion

Closes #5776

This technically is a breaking change, so I will slot this for 3.0.0

This needs documentation updates as well. Does this behave well if the attributes are not specified?

Added documentation. When the attribute is not there it behaves fine.

@wesleycho why is this change a breaking change ?
There is only some attributes added. When they not set (what they can't be currently) they will be ignored.
So this change is fully compatible.
We also

authors: bys92 theurere wesleycho


text:
Update i18n nl.js for grouping feature

avoid crash on  title: i18nService.get().grouping.group,       when language is set to dutch

Thanks,

repo: angular-ui/ng-grid


text:
fix(clearThisRowInvisible) not using parameter reason

Not sure if intended but clearThisRowInvisible is not using the parameter "reason" when deleting the "invisible reason" but it always deletes the hardcoded parameter "user".
This shouldn't change any other behavior since ui-grid internal functions call this function only with the parameter "user" but it will fix any unexpected behavior when using this function with a custom invisible reason
Haven't put a check if the value exists since "delete" fails silently in that case

Thanks


text:
Wrong separator from import in app.module.ts when generate component

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10

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.11-webpack.8
node: 6.5.0
os: win32 x64

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

ng generate component shared/toolbar

The log given by the failure. Normally this include a stack trace and some
more information.
Not work when  running, and see  in app.module.ts :
import { ToolbarComponent } from './shared\toolbar/toolbar.component';

Mention any other details that might be useful.
Minor bug

Thanks! We'll be in touch soon.

They are already aware of this bug: https://github.com/angular/angular-cli/issues/1719

Ok ! I made a search but not with the good word.
Thank you !

authors: niklas-dahl rlouissidney

repo: angular/angular-cli


text:
Bug: "link.prev?.setAttribute is not a function" - CSP and

Command
build
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
ng build breaks when we combine ngCspNonce with a hard-coded style-sheet link in index.html.
We can replicate this in a new angular app. However, this problem first appeared for us in an Angular Universal app, with the following setup:

We add ngCspNonce to the app-root as explained in: https://angular.io/guide/security#content-security-policy
We also add some external style-sheets as links in index.html.

We believe this is where the bug occurs
https://github.com/angular/angular-cli/blob/main/packages/angular_devkit/build_angular/src/utils/index-file/inline-critical-css.ts#L149
Minimal Reproduction
How to reproduce:

Run ng new
Add ngCspNonce to index.html (nonce is hardcoded for testability)
Add a stylesheet link to head: <link rel="stylesheet" href="..." />
Run ng build, and see error

Repo with minimal reproduction: https://github.com/majoer/angular-csp-link-bug
Exception or Error
Index html generation failed.
link.prev?.setAttribute is not a function

Your Environment
Angular CLI: 16.1.5
Node: 16.17.0
Package Manager: npm 8.15.0
OS: linux x64

Angular: 16.1.6
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1601.5
@angular-devkit/build-angular   16.1.5
@angular-devkit/core            16.1.5
@angular-devkit/schematics      16.1.5
@angular/cli                    16.1.5
@schematics/angular             16.1.5
rxjs                            7.8.1
typescript                      5.1.6
zone.js                         0.13.1

Anything else relevant?
No response

Duplicate of https://github.com/angular/angular-cli/issues/25419


text:
Routing not working

Command
add, new
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Routing not working inside project folder applications
localhost:4200/admin/dashboard
Minimal Reproduction
Create New Project
ng new <somename>
Create new application under projects
ng g application admin
Add route in main app ( file name: app.routes.ts)
import { Routes } from '@angular/router';
import { AppComponent as AdminAppComponent } from '../../projects/admin/src/app/app.component';
export const routes: Routes = [
  {
    path: 'voice',
    component: AdminAppComponent,
  },
];

Create component under
ng g c dashboard
Create route under Admin app
import { Routes } from '@angular/router';
import { AppComponent } from './app.component';
import { DashboardComponent } from './dashboard/dashboard.component';

export const routes: Routes = [
  {
    path: '',
    component: AppComponent,
    children: [
      { path: 'dashboard, component: DashboardComponent },
      { path: '**', redirectTo: 'dashboard' },
    ],
  },
];

Exception or Error
No response
Your Environment
ng version

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

Angular CLI: 17.3.8
Node: 20.12.0
Package Manager: npm 10.5.0
OS: win32 x64

Angular: 17.3.10
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.8
@angular-devkit/build-angular   17.3.8
@angular-devkit/core            17.3.8
@angular-devkit/schematics      17.3.8
@angular/cli                    17.3.8
@schematics/angular             17.3.8
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.6

Anything else relevant?
No response

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


text:
Template HMR broken running on Windows Dev Server

Which @angular/* package(s) are the source of the bug?
core, compiler
Is this a regression?
No
Description
Appears to be some issue with Template HMR on a Windows where even though the message "Component update sent to client(s)" is seen. Most of the code responsible for template HMR in core is not being served to the client via the core.mjs script. not sure about this anymore.
With this problem any changes to the template even after a manual page reload won't show the changes.
The @ng/component?import GET calls also don't have a response body either.
I have tested the same repo served from Linux (WSL) and it works just fine. And tested with brand new ng new projects on Windows.
There are no errors in the console.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 19.0.4
Node: 20.18.1
Package Manager: npm 10.8.2
OS: win32 x64

Angular: 19.0.2
... compiler, compiler-cli, core

Package                             Version
-------------------------------------------------------------
@angular-devkit/architect           0.1900.4
@angular-devkit/build-angular       19.0.4
@angular-devkit/core                19.0.4
@angular-devkit/schematics          19.0.4
@angular/animations                 19.0.1
@angular/cli                        19.0.4
@angular/common                     19.0.1
@angular/forms                      19.0.1
@angular/material                   19.0.1
@angular/platform-browser           19.0.1
@angular/platform-browser-dynamic   19.0.1
@schematics/angular                 19.0.4
rxjs                                7.8.1
typescript                          5.6.3
zone.js                             0.15.0

Anything else?
No response

Duplicate of https://github.com/angular/angular-cli/issues/29049

authors: hakimio jmerro


text:
can't load lazy module with eject

Output from: ng --version.

@angular/cli: 1.0.0 (e)
node: 6.9.5
os: win32 x64
@angular/common: 4.0.0
@angular/compiler: 4.0.0
@angular/core: 4.0.0
@angular/forms: 4.0.0
@angular/http: 4.0.0
@angular/platform-browser: 4.0.0
@angular/platform-browser-dynamic: 4.0.0
@angular/router: 4.0.0
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.0

when using eject, we can't make lazy module work; access the route,just get something like
 Cannot GET /here_is_the_lazy_module_route
but "npm start" without error;
other routes binding on main module work right.
and "ng server" also works right ,if disable eject  (in .angular-cli.json file  “”ejected:false“”)

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.

authors: filipesilva guzuomuse


text:
Getting error while installation of Agular/Cli

2017-09-24T06_32_06_337Z-debug.log
I am installing Angular/Cli npm on Windows 10 I have downloaded latested Nodejs & intalled then I am trying to install Angular/Cli but after some time it is show error message :
Unexpected end of input at 1:17100 "eslint-plugin-codecs":"^1.0.3","istanbul":"~",mocha":*","uglifyjs
Here is screen shot :

Please let me know how can I install & create my first Project. Attached log file as well.
Thanks,
Gaurav

Hi Gaurav
Execute npm config get prefix on bash, go to that directory find npm folder and add Authenticated User privilege to the folder and execute npm install again.

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

authors: filipesilva gauravgoyal5 smashraid


text:
Error when build and run server

Versions
Angular CLI: 1.6.2
Node: 6.11.3
OS: darwin x64
Angular: 5.1.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker
@angular/cli: 1.6.2
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.2
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.6.2
webpack: 3.10.0
i followed the steps to build server side rendering from this doc:
https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/universal-rendering.md
but when i run: npm run build:ssr && npm run serve:ssr it's build fine but the server not working below the error appear in terminal:
`> widget-angular@0.0.0 serve:ssr /Users/apple/Desktop/xxx/widget-revamp

node dist/server.js

/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:176964
__metadata("design:paramtypes", [Event]),
^
ReferenceError: Event is not defined
at Object.c (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:176964:38)
at webpack_require (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:20:30)
at Object.defineProperty.value (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:159189:10)
at webpack_require (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:20:30)
at Object.p4j/ (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:153978:572407)
at e (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:153978:149)
at Object.9lYv (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:153978:108048)
at e (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:153978:149)
at Object.bJO+ (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:153978:397422)
at e (/Users/apple/Desktop/xxx/widget-revamp/dist/server.js:153978:149)
npm ERR! Darwin 17.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "serve:ssr"
npm ERR! node v6.11.3
npm ERR! npm  v5.5.1
npm ERR! code ELIFECYCLE
npm ERR! widget-angular@0.0.0 serve:ssr: node dist/server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the widget-angular@0.0.0 serve:ssr script 'node dist/server.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the widget-angular package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node dist/server.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs widget-angular
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls widget-angular
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/apple/Desktop/xxx/widget-revamp/npm-debug.log`

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
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.


text:
[Feature Request] Create components with module flag inside that module folder

Versions

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

Angular CLI: 1.7.1
Node: 8.9.4
OS: win32 x64
Angular: 5.2.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.7.1
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.1
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.5.3
webpack: 3.11.0

Repro steps

Create a new module

ng g module feature

Create a new component for that module

ng g component some-component -m feature

Observed behavior
The component is created in the app folder.
Desired behavior
The component should be created in the module (feature) folder.
Mention any other details that might be useful (optional)
Currently you can do
ng g component feature/some-component -m feature

But you are repeating yourself when specify the module route and the module name. Ideally, Angular should now where this module is located, and create the component there.

Alternatively, you could do the following:
ng g module feature
cd feature
ng g component some-component
ng g component other-component
ng g component third-component

@clydin Thanks. I did not knew that. However, you usually work with ng in the root of the application, so your change directory would be like cd src/app/feature. Other than that, you suggestion works.
I still believe it should generate the component inside the module specified by the flag, but thanks for the workaround.

The most of the CLI commands take the current working directory into account and many of the generate commands were optimized (i.e., simplified command option usage) for use in this manner.
The module option is intended to be a helper option to affect the module rather than the component itself.  And the option is generally only needed when the standard file structure of a component within a module directory is not used.
Also, the standard module discovery logic will walk the directory hierarchy and use the closest module found so components can be nested several levels deep within a module directory and still be automatically added to the module.

Hi @michaeljota, thanks for this feature request. However, currently this is not part of the Angular CLI roadmap.
Let's close it for now, and revisit in the future if we see that this is needed.

authors: alan-agius4 clydin michaeljota


text:
chore(test): simplify test file

There is no need to have System typings or asynchronously load
the testing modules.

Okay, as long as you say that the error was not inside a test but in the file itself. LGTM.

I'll let you merge this.

authors: filipesilva hansl


text:
fix(@angular/build): add animate to valid self-closing elements

The <animate> tag, used for SVG animations, was incorrectly treated as a non-self-closing tag by the Angular build process. This resulted in errors during the build, as the parser expected a closing </animate> tag even when unnecessary.
Closes #28502

The changes were merged into the following branches: main, 18.2.x

Hi @alan-agius4, I still get error for "fe..." elements like feFlood etc. I commented in the issue also but it is closed. There are many other SVG tags which are valid self-closing and can be used in index.html
https://developer.mozilla.org/en-US/docs/Web/SVG/Element
I guess all of these need to be in the file?


text:
高级文档—WEBPACK 简介

用中文版的【WEBPACK 简介】package.json运行npm install后再运行npm start会报错。
用英文版的不会：https://angular.io/docs/ts/latest/guide/webpack.html
好像是包的问题。
希望你们能更新下中文版的【WEBPACK 简介】包实例。

错误是：cannot read property exclude of undefined.
来自node_modules\awesome-typescript-loader\src\instance.ts [266行]
code: compilerConfig.typingOptions.exclude = compilerConfig.typingOptions.exclude || [];

已经更新到了最新版，请测试。

authors: asnowwolf cn-fanfare

repo: angular/angular-cn


text:
git clone with project name and depth=1

On the readme there's a standar clone. Maybe it can be improved a little bit (git beginners might not be aware of this and can be useful for them):
git clone --depth=1 https://github.com/angular/angular-seed.git <your-project-name>

Btw, sorry to include this in an issue, but forking and PRing just for this seemed like a waste of time.

I liked the idea of this and tried it; but I couldn't figure out how to push to a new repository on github.com with a depth of 1; e.g. my flow with angular-seed is to do:
git clone https://github.com/angular/angular-seed mynewproject
cd mynewproject
git remote set-url origin https://myname/mynewproject
git push origin master

But this fails if the clone is done with level=1 on the push back to github.  Perhaps there is a workaround, but I'm not enough of a git wizard to make work.

If you only want to have a copy of the repository without the history then just delete the .git folder after cloning and then re-initialize the repository:
git clone --depth=1 https://github.com/angular/angular-seed mynewproject
cd mynewproject
rm -rf .git
git init
git remote add origin https://github.com/myname/mynewproject

repo: angular/angular-seed


text:
Double slash for bundles path

This slash before the bundles path is generating a double slash for the scripts path, e.g. http://localhost:3000/node_modules/@angular/common//bundles/common.umd.js. Some server are not happy with this double slash and redirect to 404 pages like Firebase Hosting.

I signed it!

Weird, I think I tried that way in the past and it didn't work. But it certainly does.
Can you change the systemjs.config.plunker.js as well?

I suppose it can be changed too. I'm having some errors trying to run "npm start" inside public/docs/_examples folder to test this.

You can't do that there.
Just run gulp build-plunkers and then go to any example, inside their ts folder, there is a plunker.no-link.html. Open that file in your browser and you will go to plunker.

I had a problem with that too.
`gulpfile.js:515
spawnInfo = spawnExt('npm', ['install', ...sources], {cwd: EXAMPLES_PATH});
^^^
SyntaxError: Unexpected token ...`

You need node 5.

Plunkr works according, regardless of how the bundles path is setted at systemjs.config.plunker.js

That is weird. I will check.

Sounds good. Merging

authors: Foxandxss wardbell ziglee


text:
Svg Pattern Tag Removed using ngSanitize

On the documentation in $sanitize code there is no mention as to why <pattern> is removed when sanitizing svg elements. Something similar happens when using <clipPath>. Is this indented? I believe it should be mentioned in the docs that they are not on the list if it's for some purpose.
https://developer.mozilla.org/en-US/docs/Web/SVG/Element/pattern
https://developer.mozilla.org/en-US/docs/Web/SVG/Element/clipPath

I assume this is just an oversight, although I don't know if it can be a security issue.

The sanitize svg whitelist seems to be based on the feedparser whitelist (https://pythonhosted.org/feedparser/html-sanitization.html#svg-sanitization), which doesn't contain these elements. I can't say why though.

As pointed out by @Narretz, you can manually work around this with #13282.

authors: Narretz gkalpak samy100


text:
Let $swipe ignore mouse movement

Hey everyone,
I have a usecase where the swipeable area also contains some text which the user might want to select. But when I now have the $swipe directive in place. When ever I select text the directive triggers the swipe event.
So please give me the choice to deactivate it
:heart: :heart: :heart:
P.S. Only the bravest heros are going to implement this :dancers:

:thumbsup: Just on time.

+1

Hi everybody,
I'm really new, can you please give me an example on how use the ngSwipeDisableMouse? Thanks

@spietra Like the documentation states you just need to

add ng-swipe-disable-mouse to the ng-swipe-left or ng-swipe-right DOM Element.

Hi all, I use ng-swipe-disable-mouse and it's really works great for ng-swipe-left & ng-swipe-right
but what can I do with ng-swipe-up or ng-swipe-down?

@tmhpfnr its funny because that doc statement technically doesn't make any sense. ng-swipe-left/ng-swipe-right is not a DOM element..

authors: JonathonWei RoberMac SubZero-0 TimHoepfner juanvillegas nesQuick spietra


text:
docs($httpBackend): compare $httpBackend API to $http API

Documentation states $httpBackend has the same API as $httpBackend, it compares the API to itself. This change compares the API to $http instead.

I don't think it is correct. What is compared here is the API of the mock $httpBackend vs. $httpBackend which should be identical. So we are talking about 2 services with the same name, but from the different modules.

Okay, I think I understand. This can be closed.

authors: ciwchris pkozlowski-opensource


text:
feat($cacheFactory): add expiration option to $cacheFactory

Adds an option to $cacheFactory to define the expiration of a key after a given amount of elapsed milliseconds.
The change additionally alters the defaultCache for $http so that it can be configured during the run phase.

I'd like to discuss about this feature being implemented into the AngularJS core. I know there are more powerful cache factories out there and the cache factory of AngularJS should be simple and lightweight. However, for requests to a REST API it should be possible to automatically invalidate the results after a given amount of time, while everything is still simple and lightweight. So I added this small amount of code to the $cacheFactory.
Tests for the change in src/ng/http.js are missing since I don't know how to test this properly. Hopefully someone can tell me how this could be achieved or point me to the right direction and I'll add a test for that, too.  The change has been implemented so one can configure the defaultCache with a maxAge as follows:
'use strict';

angular.module('app', [
    'ngResource'
])
.run(["$cacheFactory", function($cacheFactory) {
    $cacheFactory('$http', { maxAge: 10000 });
}]);

Additionally I want to mention that the time for adding this change and pull request (as well as the upcoming test for the $http change) has been payed by PAYMILL GmbH, Munich. I have been asked whether this could be mentioned somewhere once the code gets approved but wouldn't be an obstacle. I and PAYMILL would like to see this code in AngularJS and is the primary goal of this PR.
P.S.: CLA already signed. Anything else missing?

See https://github.com/angular/angular.js/pull/5494#issuecomment-226191144 why we are not gonna add this.

authors: Narretz rainboxx


text:
Spread types may only be created from object types

I am not sure if this is a bug, but after upgrading to angularfire2@5.0.0-rc.9 I get this strange error on our spread operators. I created a small stackblitz that illustrates how we use the snapshotChanges() in our project. If you install angularfire2@5.0.0-rc.8 there are no errors.
Version info
Angular: 6
Firebase: 5.0.2
AngularFire: 5.0.0-rc.9
How to reproduce these conditions
https://stackblitz.com/edit/spread-operator-error
Open stackblitz
Debug output

Expected behavior

No error
Actual behavior

Typescript gives error
ERROR in <path-to-file>: error TS2698: Spread types may only be created from object types.

This was a breaking change in RC 9, we fixed the typings :P
Your data object is now a Shirt. Odd that it's not spreading for you, you might want to look at your Shirt interface... I'll play around with this in my test project.
In the meantime you could do ...(data as {})

Thanks for the quick response.
Am also playing around, and the suggested bug fix work.
I think it boils down to my (limited) understanding of functions that handle types dynamically. Like the queryCollection function should probably have a return signature, of a different type than, say, Observable<any[]> 😃
But thanks anyway!

Ah, so yeah you're losing the type information when you pass the reference + the default is any
I forked your StackBlitz and altered it to achieve what I think you're looking for https://stackblitz.com/edit/spread-operator-error-j5r6nm?file=src/app/app.component.ts

authors: dauledk jamesdaniels


text:
WIP AngularFireMessaging

AngularFireMessaging
This is a WIP, but here is the current API surface.
class AngularFireMessaging {
  messaging: FirebaseMessaging;
  requestPermission: Observable<void>;
  getToken: Observable<string>;
  tokenChanges: Observable<string>;
  messages: Observable<{}>;
  requestToken: Observable<string>;
  deleteToken: (token: string) => Observable<any>;
}

Closed for #1749


text:
feat(paginator): Add option to allow reset pageIndex to 0 on pageSize changes

Feature Description
Add config option that allows to control the value of pageIndex on pageSize changes. For example with a directive input  like [resetPageIndexOnPageSizeChange]="false | true"
Use Case
While the current implementation (ensure first element is still shown when page size changes) makes perfect sense from a logical and technical point of view it is a constant point of misunderstanding with our customers as well as their users.
In every project this topic comes up multiple times. Every customer so far has reported this as a bug, even after
we explained the behavior prior.
In addition we have A / B tested the default behavior vs resetting to first page and in 100% of cases when feedback was given it was in regards to the default behavior. We have tried to add in app explanations but it didn't really help. Users just complained less but they still didn't understand the behavior.
It saddens us that the less logical and technically correct option is the one of choice, but customers want what customers want :)

You should already be able to do something like this:
<mat-paginator [pageIndex]="index" (page)="handlePage($event)"></mat-paginator>

handlePage(event: PageEvent) {
  if (event.pageIndex === event.previousPageIndex) {
    this.index = 0;
  }
}

In general we try to avoid having multiple ways of doing the same thing. Does the above not work for your case?

Closing this issue due to no recent activity, if this is still an issue please create a new issue.

authors: amysorto crisbeto ntziolis

repo: angular/components


text:
Select: placeholder label jumps on first trigger click after reset

To repro:

Select an option by hand by clicking on an option.
Reset the form control on a select programmatically
Click on trigger to open select.

The placeholder label should animate, but instead it jumps to the top without animating. This is a bug being fixed right now in angular/angular. Tracking it here as well so we know when this is fixed.

PR in place!  https://github.com/angular/angular/pull/13334

The fix was merged into master. Updating to angular/angular master or the next released version of Angular should resolve.


text:
make expansion panel height configurable

Bug, feature request, or proposal:
Proposal
What is the expected behavior?
Height of the mat-expansion-panel-header should be configurable.
What is the current behavior?
Repeating issue 5641, which was closed with a PR that didn't address the issue. PR 6643 addressed expansion-panel-header but not expansion-panel height
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on @master): https://goo.gl/uDmqyY
StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

I don't know whether I get your proposal right, but couldn't you simply wrap the expansion's content in a <div> and control the height of the <div>? I believe the panel will correctly follow the height of this <div>. Then you can enable scrollbars or anything else you want by customizing this <div>.

Good point. I just went back and reread the original issue. I misread it to begin with and thought it pertained to the panel itself, not the header. My bad.

authors: charlie-elverson julianobrasil


text:
fix(select,autocomplete): unable to set custom id on mat-option

Fixes consumers not being allowed to set their own id on a mat-option.
Fixes #11572.

@crisbeto could you rebase?

Rebased.

@crisbeto It looks like this one has some CI failures

The compilation error is sorted out now.

authors: crisbeto jelbourn josephperrott


text:
Note: jasmine2 does not yet support per-spec timeouts

In Jasmine 1.3, you can do:
it('does stuff', function() {
  ...
}, 100);

To specify a timeout of 100 ms.
Jasmine2 has added this feature in master (https://github.com/jasmine/jasmine/commit/a4faa80be464b1054293ac3179eb21b2ccc8c472) but it is NOT YET released in version 2.1.1.
This causes npm test to fail for Protractor's own test because our timeout suite (expected to fail) instead passes.
TODO - close this issue when a new version of Jasmine is released.

Done, now that we've upgraded to Jasmine 2.3.

@juliemr
Im using
"jasmine": "2.3.1"
"Protractor: Version 2.1.0"
it('does stuff', function() {
...
}, 1000);
I tried this and I got this error.
Jasmine spec timed out. Resetting the WebDriver Control Flow.
" Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL."
But the same spec used to work before updating protractor and Jasmine.

I have problems with jasmine.DEFAULT_TIMEOUT_INTERVAL, too. No matter how I write my code... I can't get rid of it.

authors: donaldpipowitch juliemr prabhu-telsiz

repo: angular/protractor


text:
Missing information

Hi!
I'm getting this error:
2) xxxxxxxxxxxxxxxxxx
Message:
InvalidSelectorError: invalid selector: An invalid or illegal selector was specified
(Session info: chrome=41.0.2272.118)
(Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Windows NT 6.3 x86_64)
Please, could you add more information about WHICH is the invalid selector?
Thanks!

These errors come directly from the WebDriver browser driver. Hopefully the stack trace was helpful in finding which line triggered that error - other than that, I don't think we want to get into the business of parsing webdriver errors and adding more information. (Note that the error returned from webdriver could be different text for different browsers). You could bring this up as a feature request with https://github.com/SeleniumHQ/selenium

authors: BrodaNoel juliemr


text:
es6 and lite-server errors

[1] Did not detect a bs-config.json or bs-config.js override file. Using lite-server defaults...
[1] ** browser-sync options **
[1] { injectChanges: false,
[1]   files: [ './**/*.{html,htm,css,js}' ],
[1]   server: { baseDir: './', middleware: [ [Function], [Function] ] } }
[1] [BS] Access URLs:
[1]  ------------------------------------
[1]        Local: http://localhost:3000
[1]     External: http://192.168.1.3:3000
[1]  ------------------------------------
[1]           UI: http://localhost:3001
[1]  UI External: http://192.168.1.3:3001
[1]  ------------------------------------
[1] [BS] Serving files from: ./
[1] [BS] Watching files...
[1] 16.03.19 17:59:33 200 GET /index.html
[1] 16.03.19 17:59:33 404 GET /styles.css
[1] 16.03.19 17:59:33 304 GET /node_modules/es6-shim/es6-shim.min.js
[1] 16.03.19 17:59:33 304 GET /node_modules/systemjs/dist/system-polyfills.js
[1] 16.03.19 17:59:33 304 GET /node_modules/angular2/bundles/angular2-polyfills.js
[1] 16.03.19 17:59:33 304 GET /node_modules/systemjs/dist/system.src.js
[1] 16.03.19 17:59:33 304 GET /node_modules/angular2/es6/dev/src/testing/shims_for_IE.js
[1] 16.03.19 17:59:33 304 GET /node_modules/rxjs/bundles/Rx.js
[1] 16.03.19 17:59:33 304 GET /node_modules/angular2/bundles/angular2.dev.js
[0] node_modules/angular2/typings/browser.d.ts(6,14): error TS2300: Duplicate identifier 'PromiseConstructor'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(22,5): error TS2300: Duplicate identifier 'done'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(23,5): error TS2300: Duplicate identifier 'value'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(46,5): error TS2300: Duplicate identifier 'size'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(52,5): error TS2300: Duplicate identifier 'prototype'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(66,5): error TS2300: Duplicate identifier 'size'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(72,5): error TS2300: Duplicate identifier 'prototype'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(88,5): error TS2300: Duplicate identifier 'prototype'.
[0] node_modules/angular2/typings/es6-collections/es6-collections.d.ts(103,5): error TS2300: Duplicate identifier 'prototype'.
[0] node_modules/angular2/typings/es6-promise/es6-promise.d.ts(11,15): error TS2300: Duplicate identifier 'Promise'.
[0] node_modules/angular2/typings/es6-promise/es6-promise.d.ts(42,16): error TS2300: Duplicate identifier 'Promise'.
[0] typings/browser/ambient/es6-shim/index.d.ts(11,5): error TS2300: Duplicate identifier 'done'.
[0] typings/browser/ambient/es6-shim/index.d.ts(12,5): error TS2300: Duplicate identifier 'value'.
[0] typings/browser/ambient/es6-shim/index.d.ts(477,11): error TS2300: Duplicate identifier 'Promise'.
[0] typings/browser/ambient/es6-shim/index.d.ts(496,11): error TS2300: Duplicate identifier 'PromiseConstructor'.
[0] typings/browser/ambient/es6-shim/index.d.ts(554,13): error TS2300: Duplicate identifier 'Promise'.
[0] typings/browser/ambient/es6-shim/index.d.ts(563,5): error TS2300: Duplicate identifier 'size'.
[0] typings/browser/ambient/es6-shim/index.d.ts(572,5): error TS2300: Duplicate identifier 'prototype'.
[0] typings/browser/ambient/es6-shim/index.d.ts(583,5): error TS2300: Duplicate identifier 'size'.
[0] typings/browser/ambient/es6-shim/index.d.ts(592,5): error TS2300: Duplicate identifier 'prototype'.
[0] typings/browser/ambient/es6-shim/index.d.ts(607,5): error TS2300: Duplicate identifier 'prototype'.
[0] typings/browser/ambient/es6-shim/index.d.ts(621,5): error TS2300: Duplicate identifier 'prototype'.
[0] 5:59:33 PM - Compilation complete. Watching for file changes.
[1] [BS] File changed: app/app.component.js
[1] [BS] File changed: app/main.js
[1] [BS] File changed: app/sayHello.js
[1] 16.03.19 17:59:33 200 GET /app/main.js
[1] 16.03.19 17:59:33 200 GET /app/app.component.js
[1] events.js:154
[1]       throw er; // Unhandled 'error' event
[1]       ^
[1]
[1] Error: watch node_modules/browser-sync/node_modules/lodash/lang/isNumber.js ENOSPC
[1]     at exports._errnoException (util.js:890:11)
[1]     at FSWatcher.start (fs.js:1313:19)
[1]     at Object.fs.watch (fs.js:1341:11)
[1]     at createFsWatchInstance (/run/media/habib/New Volume/projects/angular2/learn-from-doc/node_modules/chokidar/lib/nodefs-handler.js:37:15)
[1]     at setFsWatchListener (/run/media/habib/New Volume/projects/angular2/learn-from-doc/node_modules/chokidar/lib/nodefs-handler.js:80:15)
[1]     at FSWatcher.NodeFsHandler._watchWithNodeFs (/run/media/habib/New Volume/projects/angular2/learn-from-doc/node_modules/chokidar/lib/nodefs-handler.js:228:14)
[1]     at FSWatcher.NodeFsHandler._handleFile (/run/media/habib/New Volume/projects/angular2/learn-from-doc/node_modules/chokidar/lib/nodefs-handler.js:255:21)
[1]     at FSWatcher. (/run/media/habib/New Volume/projects/angular2/learn-from-doc/node_modules/chokidar/lib/nodefs-handler.js:473:21)
[1]     at FSReqWrap.oncomplete (fs.js:82:15)
[1]
[1] npm
[1]
[1] ERR! Linux 4.4.5-1-MANJARO
[1] npm ERR!
[1] argv "/usr/bin/node" "/usr/bin/npm" "run" "lite"
[1] npm ERR! node v5.8.0
[1] npm
[1] ERR! npm  v3.8.2
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! angular2-quickstart@1.0.0 lite: lite-server
[1] npm ERR! Exit status 1
[1] npm ERR!
[1] npm ERR! Failed at the angular2-quickstart@1.0.0 lite script 'lite-server'.
[1] npm ERR! Make sure you have the latest version of node.js and npm installed.
[1] npm
[1]  ERR! If you do, this is most likely a problem with the angular2-quickstart package,
[1] npm ERR! not with npm itself.
[1] npm ERR! Tell the author that this fails on your system:
[1] npm ERR!     lite-server
[1] npm ERR! You can get information on how to open an issue for this project with:
[1] npm ERR!     npm bugs angular2-quickstart
[1] npm ERR! Or if that isn't available, you can get their info via:
[1] npm ERR!     npm owner ls angular2-quickstart
[1] npm ERR! There is likely additional logging output above.
[1]
[1] npm
[1] ERR! Please include the following file with any support request:
[1] npm ERR!     /run/media/habib/New Volume/projects/angular2/learn-from-doc/npm-debug.log
[1] npm run lite exited with code 1
npm-debug.log.tar.gz

I'm sorry but I cannot duplicate.
Works fine for me. What is your environment? What node version? What did you clone?
Are you updating or starting from scratch? If updating, is it possible that you have multiple shim versions for the same shim library in your typings folder? If so, the easiest thing is to discard the repo and clone again.
My Console Log
On Windows, node v.5.6, npm v.3.6.0 ... after the following ...

clone the repo for beta.11, (commit 0fb8db4de578b41300dfde84f7fbb06a3f563b11)
npm install
npm start

... I see this (and the app displays in the browser) ...
> npm start

> angular2-quickstart@1.0.0 start C:\github\_angular-quickstart
> concurrently "npm run tsc:w" "npm run lite"

[1]
[1] > angular2-quickstart@1.0.0 lite C:\github\_angular-quickstart
[1] > lite-server
[1]
[0]
[0] > angular2-quickstart@1.0.0 tsc:w C:\github\_angular-quickstart
[0] > tsc -w
[0]
[1] Did not detect a `bs-config.json` or `bs-config.js` override file. Using lite-server defaults...
[1] ** browser-sync options **
[1] { injectChanges: false,
[1]   files: [ './**/*.{html,htm,css,js}' ],
[1]   server: { baseDir: './', middleware: [ [Function], [Function] ] } }
[0] 4:30:33 PM - Compilation complete. Watching for file changes.
[1] [BS] Access URLs:
[1]  -------------------------------------
[1]        Local: http://localhost:3000
[1]     External: http://192.168.1.80:3000
[1]  -------------------------------------
[1]           UI: http://localhost:3001
[1]  UI External: http://192.168.1.80:3001
[1]  -------------------------------------
[1] [BS] Serving files from: ./
[1] [BS] Watching files...
[1] 16.03.19 16:30:35 200 GET /index.html
[1] 16.03.19 16:30:36 200 GET /styles.css
[1] 16.03.19 16:30:36 200 GET /node_modules/es6-shim/es6-shim.min.js
[1] 16.03.19 16:30:36 200 GET /node_modules/angular2/es6/dev/src/testing/shims_for_IE.js
[1] 16.03.19 16:30:36 200 GET /node_modules/systemjs/dist/system-polyfills.js
[1] 16.03.19 16:30:36 200 GET /node_modules/angular2/bundles/angular2-polyfills.js
[1] 16.03.19 16:30:37 200 GET /node_modules/systemjs/dist/system.src.js
[1] 16.03.19 16:30:37 200 GET /node_modules/rxjs/bundles/Rx.js
[1] 16.03.19 16:30:38 200 GET /node_modules/angular2/bundles/angular2.dev.js
[1] 16.03.19 16:30:39 200 GET /app/main.js
[1] 16.03.19 16:30:39 200 GET /app/app.component.js

I cannot duplicate it either. Node 5.5.0, npm 3.7.2 and OSX.

I tried cloning https://github.com/angular/quickstart and I tried do it with copy the files in  https://angular.io/docs/ts/latest/tutorial/ and do npm install   in both windows and linux.
I also updated the npm and node to latest version.
It can detect the changes and transpile TypeScript to JavaScript but it can not refresh browser and sometimes server terminates with exit code 1

Using xubuntu 14.04, node 4.4.0, npm 2.14.20.
The following opens index.html in a new browser tab, but fails to live-update it and even locks the app's files against editing.
$ npm start

> angular2-quickstart@1.0.0 start /home/jonathan/workspace/angular2-quickstart
> concurrently "npm run tsc:w" "npm run lite"

[1]
[1] > angular2-quickstart@1.0.0 lite /home/jonathan/workspace/angular2-quickstart
[1] > lite-server
[1]
[0]
[0] > angular2-quickstart@1.0.0 tsc:w /home/jonathan/workspace/angular2-quickstart
[0] > tsc -w
[0]
[1] Did not detect a `bs-config.json` or `bs-config.js` override file. Using lite-server defaults...
[1] ** browser-sync options **
[1] { injectChanges: false,
[1]   files: [ './**/*.{html,htm,css,js}' ],
[1]   server: { baseDir: './', middleware: [ [Function], [Function] ] } }
[1] [BS] Access URLs:
[1]  ------------------------------------
[1]        Local: http://localhost:3000
[1]     External: http://192.168.1.2:3000
[1]  ------------------------------------
[1]           UI: http://localhost:3001
[1]  UI External: http://192.168.1.2:3001
[1]  ------------------------------------
[1] [BS] Serving files from: ./
[1] [BS] Watching files...
[1] 16.03.21 10:14:30 304 GET /index.html
[0] 10:14:33 AM - Compilation complete. Watching for file changes.
[1] 16.03.21 10:14:34 304 GET /styles.css
[1] 16.03.21 10:14:34 304 GET /node_modules/es6-shim/es6-shim.min.js
[1] 16.03.21 10:14:34 304 GET /node_modules/systemjs/dist/system-polyfills.js
[1] 16.03.21 10:14:34 304 GET /node_modules/angular2/es6/dev/src/testing/shims_for_IE.js
[1] 16.03.21 10:14:34 304 GET /node_modules/angular2/bundles/angular2-polyfills.js
[1] 16.03.21 10:14:34 304 GET /node_modules/systemjs/dist/system.src.js
[1] [BS] File changed: app/app.component.js
[1] [BS] File changed: app/main.js
[1] 16.03.21 10:14:34 304 GET /node_modules/rxjs/bundles/Rx.js
[1] 16.03.21 10:14:34 304 GET /node_modules/angular2/bundles/angular2.dev.js
[1] 16.03.21 10:14:36 200 GET /app/main.js
[1] 16.03.21 10:14:37 200 GET /app/app.component.js
[1] events.js:141
[1]       throw er; // Unhandled 'error' event
[1]       ^
[1]
[1] Error: watch node_modules/typings/node_modules/update-notifier/node_modules/latest-version/node_modules/package-json/node_modules/got/node_modules/readable-stream/lib/_stream_passthrough.js ENOSPC
[1]     at exports._errnoException (util.js:870:11)
[1]     at FSWatcher.start (fs.js:1234:19)
[1]     at Object.fs.watch (fs.js:1262:11)
[1]     at createFsWatchInstance (/home/jonathan/workspace/angular2-quickstart/node_modules/lite-server/node_modules/browser-sync/node_modules/chokidar/lib/nodefs-handler.js:37:15)
[1]     at setFsWatchListener (/home/jonathan/workspace/angular2-quickstart/node_modules/lite-server/node_modules/browser-sync/node_modules/chokidar/lib/nodefs-handler.js:80:15)
[1]     at FSWatcher.NodeFsHandler._watchWithNodeFs (/home/jonathan/workspace/angular2-quickstart/node_modules/lite-server/node_modules/browser-sync/node_modules/chokidar/lib/nodefs-handler.js:228:14)
[1]     at FSWatcher.NodeFsHandler._handleFile (/home/jonathan/workspace/angular2-quickstart/node_modules/lite-server/node_modules/browser-sync/node_modules/chokidar/lib/nodefs-handler.js:255:21)
[1]     at FSWatcher.<anonymous> (/home/jonathan/workspace/angular2-quickstart/node_modules/lite-server/node_modules/browser-sync/node_modules/chokidar/lib/nodefs-handler.js:473:21)
[1]     at FSReqWrap.oncomplete (fs.js:82:15)
[1]
[1] npm
[1]
[1] ERR!
[1]  Linux 3.19.0-51-generic
[1] npm
[1]
[1] ERR!
[1]
[1] argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "lite"
[1] npm ERR! node v4.4.0
[1] npm ERR!
[1] npm  v2.14.20
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! angular2-quickstart@1.0.0 lite: `lite-server`
[1] npm ERR! Exit status 1
[1] npm ERR!
[1] npm ERR! Failed at the angular2-quickstart@1.0.0 lite script 'lite-server'.
[1] npm ERR! This is most likely a problem with the angular2-quickstart package,
[1] npm ERR! not with npm itself.
[1] npm ERR! Tell the author that this fails on your system:
[1] npm ERR!     lite-server
[1] npm ERR! You can get information on how to open an issue for this project with:
[1] npm ERR!     npm bugs angular2-quickstart
[1] npm ERR! Or if that isn't available, you can get their info via:
[1] npm ERR!
[1] npm ERR!     npm owner ls angular2-quickstart
[1] npm ERR! There is likely additional logging output above.
[1]
[1] npm
[1]
[1] ERR!
[1]  Please include the following file with any support request:
[1] npm ERR!     /home/jonathan/workspace/angular2-quickstart/npm-debug.log
[1] npm run lite exited with code 1

Related: https://github.com/johnpapa/lite-server/issues/54

Had the same problem on Fedora 23, using various node and npm versions.   I found this solution that worked for me:
Related: angular/angular#6097
Another reference that contains some interesting links in the comments:
http://stackoverflow.com/questions/34399445/angular-2-quickstart-live-server-error

We updated the quickstart to all the latest versions.
Could we confirm if this is still a problem?
Thank you.

I also had the same issue (fs.inotify.max_user_watches was too low) but it works now. I think the problem is that lite-server watches all files, including node_modules, which totals in about 10600 files. This may be fixed by this pull request.

Closing as this is not a QS issue

authors: Foxandxss bengy jc275 kazemihabib rassiesmit wardbell

repo: angular/quickstart


text:
tsd running in preinstall still breaking angular

My PR is broken
https://travis-ci.org/angular/angular/jobs/60612378
because the travis cache was missed, and now it can't find tsd at the time ts2dart wants to preinstall.
I somewhat broke this with
https://github.com/angular/ts2dart/commit/5af57c39cfaa46f2f89305310ce5c65628c139a6
but that was needed for angular shrinkwrap
https://github.com/npm/npm/issues/3059#issuecomment-12282746
says we may as well use a separate release script (would also have the benefit of adding the git tag)
another option is to try having npm install tsd in the preinstall and also have tsd in the devDependencies, which I don't think we've tried - however this risks having a different version between those two things, and also, it's not actually a devDependency once the typings are on your machine, if anything, you just need to global install it.
Going to try a release script.

Still broken while trying to shrinkwrap angular again.


text:
adds a chapter on how to rock the gem with roda

let me know, if there's anything I could do to have Roda out in the sun 😅
great work and thank you for the effort 🗺 👍

Hey @simonneutert, thanks for the PR. Roda isn't officially supported, so don't want to include it in the readme, but this should be a good resource for anyone searching for it.

authors: ankane simonneutert

repo: ankane/mapkick


text:
Where does stylebot store custom stylesheets?

I don't want to use the HTML editor but can't seem to find the custom stylesheet path anywhere
Will update this issue if I find a solution

Update:
It is located in /Default/Local Extension Storage
However, it is not so easy to edit, because it is stored in a "log" file (e.g. "000003.log")
I am guessing this is something Chrome forces extensions to do since it seems my other extensions have this structure too.
I can get the results I want by opening the log file in a text editor with a utf-8 encoding and editing the last line (which seems to store the current settings) directly, however I am guessing this is also a bad idea if you care about losing your stylesheets since chrome might try to sync this log file or do stuff like file verification on it, so use at your own risk

BTW I have written a quick script to compile a CSS file and inject it into this log file, overwriting the current settings
If anyone is interested comment here and I can share

repo: ankit/stylebot


text:
Add a Docker Compose File

I see a Docker File here, I would like to add on Docker-Compose file , then it would be more convenient to start this application in container, with just one command. Should I go for it, If you want?

It's a valid issue, that's why I am assigning you cause participants can't create issues.So please consider discussing issues on discord first then we will create them for u.
1.Add docker.yml properly.
2.Add a screenshot of the image this project running on docker in the PR

you are participating through swoc right ?

No, I came to Know about this project while searching and sorry for not discussing this on Discord First, I will remember this for next time.

It's ok , actually, these issues are under swoc , so as of now I am unassigning you ,later you can work on this project

Ok, one thing i would like to ask, Is registeration still open for swoc and can i work on this issue after getting registered? Just asking

Ok, one thing i would like to ask, Is registeration still open for swoc and can i work on this issue after getting registered? Just asking

no its currently closed

It's closed ...there will be one more open source in Jan named JGOC or Jwoc
so u can participate
On Sun, 26 Dec, 2021, 10:17 pm Ankita Puri, @.***>
wrote:

Ok, one thing i would like to ask, Is registeration still open for swoc
and can i work on this issue after getting registered? Just asking
no its currently closed
—
Reply to this email directly, view it on GitHub
https://github.com/ankitapuri/pixelvibe/issues/416#issuecomment-1001211429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APRU7F2DCNRIUNVNXI2NTY3US5BLZANCNFSM5KXNH23Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

authors: 7saikat7 RishiKumarRay ankitapuri

repo: ankitapuri/pixelvibe


text:
I met some mistake when I generated some vertical text

hello, When I generated some vertical text , I modified the code at render_multiline function as you@ankush-me told in older issue, but some word was missed when it's line was vertical, could you help me?

the crop picture like this ,thank you!

the code I modified only here

I have tried it and modified the code I showed which got a good result, thank you very  @ankush-me

repo: ankush-me/SynthText


text:
📚 [Documentation / WorkFlow] - Adding auto_comment.yml file

Description ✍
We need to add an auto-comment.yml that will automatically welcome, greet and provide necessary information to the contributors when they create new issues, PR, and when these will get assigned or merged respectively. This will promote motivation and performance
@anmode Please assign me this issue under gssoc'23
Are you contributing for a program ?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

Not needed thanks @Anshika-Jain02

repo: anmode/grabtern-frontend


text:
Fixed the confirmpassword visibility

Related Issue

Closes: #[614]
Description of Changes
Checklist:

[✔ ] My code adheres to the established style guidelines of this project.
[✔ ] I have conducted a self-review of my code.
[✔ ] I have included comments in areas that may be difficult to understand.
[ ✔] I have made corresponding updates to the project documentation.
[✔ ] My changes have not introduced any new warnings.

Screenshots

Original
Updated

![Updated screenshot](lin

https://github.com/anmode/grabtern-frontend/assets/109091515/68fecb5e-7af2-4b40-b7e5-ddf0d58acaae
k) |
Please provide any necessary screenshots to illustrate the changes made.

Can you fix UI of this icon too? Looks so small
And make it work if I enter password without entring conf password and try to view , i can see..
As of now it didn't do like.. you can see.

yeah, i can fix the UI but what you mention later it looks fine that when anyone enter the password without entering the conf password the password is view by clicking on the button.

hey @anmode , fixed the UI icon please review it and merge this PR.

authors: anmode rishiofficial


text:
🛑 Педакадемия.РФ is down

In 7e30039, Педакадемия.РФ (https://педакадемия.рф) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Педакадемия.РФ is back up in 04e873a after 11 minutes.

repo: ano-pedproject/repo


text:
Update package.json

Mixing nodemon and concurrently are also missing

Well, I've saw the the readme defines install them. Closing.

repo: anorudes/redux-easy-boilerplate


text:
Update index.js

For me to merge this it will need to do something more then just add a comment for a shirt. Please choose an issue, there are several testing related issues that would require pretty tiny testing improvements for instance. :-) Thanks!

Closing since I am not seeing any motion towards something productive... feel free to submit a new PR per notes above.

repo: ansble/monument


text:
ANS-006-98 - MAJ PDF spec fonc + suppression PDF et images outdated

Mise à jour du pdf de la spécifications fonctionnelles
Suppression des pdf et images outfated
issues #68 , #70 , #86

@SEBELIN , review attendue pour pouvoir merger