Ghost Build Error

I got an error attempting to build NodeOS. This error doesn't give any information I can recognize and infact, I don't see a warning or error at all... it just fails. Now, it could be because I'm tired but I did run "npm install" and this error occured with "npm run build". Here's the npm-debug.log
0 info it worked if it ends with ok 1 verbose cli [ '/root/.nvm/versions/node/v6.3.1/bin/node', 1 verbose cli   '/root/.nvm/versions/node/v6.3.1/bin/npm', 1 verbose cli   'run', 1 verbose cli   'build' ] 2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] 5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prebuild, continuing 7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true 9 verbose lifecycle<EMAIL_ADDRESS>PATH: /root/.nvm/versions/node/v6.3.1/lib/node_modules/npm/bin/node-gyp-bin:/root/nodeos/node_modules/.bin:/root/.nvm/versions/node/v6.3.1/bin:/root/.nvm/versions/node/v6.3.1/bin:/root/bin:/root/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin 10 verbose lifecycle<EMAIL_ADDRESS>CWD: /root/nodeos 11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'scripts/build' ] 12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null 13 info lifecycle<EMAIL_ADDRESS>Failed to exec build script 14 verbose stack Error<EMAIL_ADDRESS>build:scripts/build 14 verbose stack Exit status 1 14 verbose stack     at EventEmitter.<anonymous> (/root/.nvm/versions/node/v6.3.1/lib/node_modules/npm/lib/utils/lifecycle.js:242:16) 14 verbose stack     at emitTwo (events.js:106:13) 14 verbose stack     at EventEmitter.emit (events.js:191:7) 14 verbose stack     at ChildProcess.<anonymous> (/root/.nvm/versions/node/v6.3.1/lib/node_modules/npm/lib/utils/spawn.js:40:14) 14 verbose stack     at emitTwo (events.js:106:13) 14 verbose stack     at ChildProcess.emit (events.js:191:7) 14 verbose stack     at maybeClose (internal/child_process.js:852:16) 14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5) 15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /root/nodeos 17 error Linux 4.4.0-31-generic 18 error argv "/root/.nvm/versions/node/v6.3.1/bin/node" "/root/.nvm/versions/node/v6.3.1/bin/npm" "run" "build" 19 error node v6.3.1 20 error npm  v3.10.3 21 error code ELIFECYCLE 22 error<EMAIL_ADDRESS>build:scripts/build22 error Exit status 1 23 error Failed at the<EMAIL_ADDRESS>build script 'scripts/build'. 23 error Make sure you have the latest version of node.js and npm installed. 23 error If you do, this is most likely a problem with the NodeOS package, 23 error not with npm itself. 23 error Tell the author that this fails on your system: 23 error     scripts/build 23 error You can get information on how to open an issue for this project with: 23 error     npm bugs NodeOS 23 error Or if that isn't available, you can get their info via: 23 error     npm owner ls NodeOS 23 error There is likely additional logging output above. 24 verbose exit [ 1, true ]

It's strange, seems that scripts/build fails just when it start to exec...
El 13/9/2016 6:09, "Lite McFish"<EMAIL_ADDRESS>escribió:
I got an error attempting to build NodeOS. This error doesn't give any
information I can recognize and infact, I don't see a warning or error at
all... it just fails. Now, it could be because I'm tired but I did run "npm
install" and this error occured with "npm run build". Here's the
npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/root/.nvm/versions/node/v6.3.1/bin/node',
1 verbose cli '/root/.nvm/versions/node/v6.3.1/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prebuild,
continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH:
/root/.nvm/versions/node/v6.3.1/lib/node_modules/npm/bin/
node-gyp-bin:/root/nodeos/node_modules/.bin:/root/.nvm/
versions/node/v6.3.1/bin:/root/.nvm/versions/node/v6.3.
1/bin:/root/bin:/root/.local/bin:/usr/local/sbin:/usr/
local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/
local/games:/snap/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /root/nodeos
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'scripts/build' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1 signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
14 verbose stack Error<EMAIL_ADDRESS>build:scripts/build
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/root/.nvm/versions/node/v6.
3.1/lib/node_modules/npm/lib/utils/lifecycle.js:242:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/root/.nvm/versions/node/v6.
3.1/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:852:16)
14 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:215:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /root/nodeos
17 error Linux 4.4.0-31-generic
18 error argv "/root/.nvm/versions/node/v6.3.1/bin/node"
"/root/.nvm/versions/node/v6.3.1/bin/npm" "run" "build"
19 error node v6.3.1
20 error npm v3.10.3
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>build:scripts/build
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>build script 'scripts/build'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the NodeOS package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error scripts/build
23 error You can get information on how to open an issue for this project
with:
23 error npm bugs NodeOS
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls NodeOS
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/305, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgfvi_2mM-1nE8q_cMbEENBjPjZH6dEks5qpiICgaJpZM4J7Reb
.

What could cause a crash that quick? Will you need more of my device specs?
On Tue, Sep 13, 2016, 12:55 AM Jesús Leganés Combarro <
<EMAIL_ADDRESS>wrote:

It's strange, seems that scripts/build fails just when it start to exec...
El 13/9/2016 6:09, "Lite McFish"<EMAIL_ADDRESS>escribió:
I got an error attempting to build NodeOS. This error doesn't give any
information I can recognize and infact, I don't see a warning or error at
all... it just fails. Now, it could be because I'm tired but I did run "npm
install" and this error occured with "npm run build". Here's the
npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/root/.nvm/versions/node/v6.3.1/bin/node',
1 verbose cli '/root/.nvm/versions/node/v6.3.1/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prebuild,
continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH:
/root/.nvm/versions/node/v6.3.1/lib/node_modules/npm/bin/
node-gyp-bin:/root/nodeos/node_modules/.bin:/root/.nvm/
versions/node/v6.3.1/bin:/root/.nvm/versions/node/v6.3.
1/bin:/root/bin:/root/.local/bin:/usr/local/sbin:/usr/
local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/
local/games:/snap/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /root/nodeos
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'scripts/build' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1 signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
14 verbose stack Error<EMAIL_ADDRESS>build:scripts/build
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/root/.nvm/versions/node/v6.
3.1/lib/node_modules/npm/lib/utils/lifecycle.js:242:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/root/.nvm/versions/node/v6.
3.1/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:852:16)
14 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:215:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /root/nodeos
17 error Linux 4.4.0-31-generic
18 error argv "/root/.nvm/versions/node/v6.3.1/bin/node"
"/root/.nvm/versions/node/v6.3.1/bin/npm" "run" "build"
19 error node v6.3.1
20 error npm v3.10.3
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>build:scripts/build
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>build script 'scripts/build'.
23 error Make sure you have the latest version of node.js and npm
installed.
23 error If you do, this is most likely a problem with the NodeOS package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error scripts/build
23 error You can get information on how to open an issue for this project
with:
23 error npm bugs NodeOS
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls NodeOS
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/305, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAgfvi_2mM-1nE8q_cMbEENBjPjZH6dEks5qpiICgaJpZM4J7Reb

.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/305#issuecomment-246592031, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIHz3xDH1Im64FcdRpL4iUkTrezOI0h1ks5qpkj2gaJpZM4J7Reb
.

Look what's generating the exit 1 on scripts/build.
El 15/9/2016 4:07, "Lite McFish"<EMAIL_ADDRESS>escribió:

What could cause a crash that quick? Will you need more of my device specs?
On Tue, Sep 13, 2016, 12:55 AM Jesús Leganés Combarro <
<EMAIL_ADDRESS>wrote:

It's strange, seems that scripts/build fails just when it start to
exec...
El 13/9/2016 6:09, "Lite McFish"<EMAIL_ADDRESS>escribió:
I got an error attempting to build NodeOS. This error doesn't give any
information I can recognize and infact, I don't see a warning or error at
all... it just fails. Now, it could be because I'm tired but I did run
"npm
install" and this error occured with "npm run build". Here's the
npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/root/.nvm/versions/node/v6.3.1/bin/node',
1 verbose cli '/root/.nvm/versions/node/v6.3.1/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prebuild,
continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle
true
9 verbose lifecycle<EMAIL_ADDRESS>PATH:
/root/.nvm/versions/node/v6.3.1/lib/node_modules/npm/bin/
node-gyp-bin:/root/nodeos/node_modules/.bin:/root/.nvm/
versions/node/v6.3.1/bin:/root/.nvm/versions/node/v6.3.
1/bin:/root/bin:/root/.local/bin:/usr/local/sbin:/usr/
local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/
local/games:/snap/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /root/nodeos
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c',
'scripts/build' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1 signal:
null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
14 verbose stack Error<EMAIL_ADDRESS>build:scripts/build
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.
(/root/.nvm/versions/node/v6.
3.1/lib/node_modules/npm/lib/utils/lifecycle.js:242:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.
(/root/.nvm/versions/node/v6.
3.1/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:852:16)
14 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:215:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /root/nodeos
17 error Linux 4.4.0-31-generic
18 error argv "/root/.nvm/versions/node/v6.3.1/bin/node"
"/root/.nvm/versions/node/v6.3.1/bin/npm" "run" "build"
19 error node v6.3.1
20 error npm v3.10.3
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>build:scripts/build
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>build script 'scripts/build'.
23 error Make sure you have the latest version of node.js and npm
installed.
23 error If you do, this is most likely a problem with the NodeOS
package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error scripts/build
23 error You can get information on how to open an issue for this project
with:
23 error npm bugs NodeOS
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls NodeOS
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/305, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAgfvi_2mM-1nE8q_
cMbEENBjPjZH6dEks5qpiICgaJpZM4J7Reb

.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/305#issuecomment-246592031,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/
AIHz3xDH1Im64FcdRpL4iUkTrezOI0h1ks5qpkj2gaJpZM4J7Reb>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/305#issuecomment-247213247, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfviOdadgOYK0P7d_gK38HTyP40DHcks5qqKhxgaJpZM4J7Reb
.

closing due to inactivity.


New-TablePercentageBar - Conditional BarColor?

With New-TablePercentageBar it doesn't seem possible to create a condition for things like BarColor?
Ideally, being able to say something like the following would be great:

If Value > 70 BarColor eq Yellow
If Value > 80 BarColoer eq Orage
If Value > 90 BarColor eq Red

Love this addition, not sure when it popped in, just needs this one tweak to be super useful!

hi,
Not sure it's natively possible:

https://datatables.net/plug-ins/dataRender/percentageBars

The JS code is here:

https://cdn.datatables.net/plug-ins/1.13.4/dataRender/percentageBars.js

Source codes (to commit back to DataTables after fixes)

https://github.com/DataTables/Plugins/blob/master/dataRender/percentageBars.js

This would require some modification to support conditions, but doable.
Some links to consider:
-https://datatables.net/examples/basic_init/data_rendering.html

I actually just hardcoded this and it seems to work, so I'll work on it to make it nice and fancy

Gotcha, I didn't assume it was tied directly to DataTables - thanks!
My current workaround is to use manual HTML with -InvokeHTMLTags:
$tmp1 | % { $.'% Used' = "$($.'% Used')" + '%  <meter value="' + "$($_.'% Used')" + '" optimum="25" low="70" high="85" max="100">' }
Very ugly but works...my biggest issue was trying to make it 'pretty' as I am not familiar with CSS, etc...

The change is pretty trivial

Just before returning style, you can hardcode cBar to some value. I am now checking on how you can pass hashtable of sorts so it would work

I've created PR for this change in datatables. Lets see how that works out. I'll probably release my own version until they process it properly on their own side.

From a PowerShell perspective:
$DataTable = @(
    [PSCustomObject] @{ Test = 'Name'; Test2 = 'Name2'; Test3 = 'Name3'; Test4 = 1.42; Percents = 50 }
    [PSCustomObject] @{ Test = 'Name'; Test2 = 'Name2'; Test3 = 'Name3'; Test4 = 5.72; Percents = 5 }
    [PSCustomObject] @{ Test = 'Name'; Test2 = 'Name2'; Test3 = 'Name3'; Test4 = 16.22; Percents = 17 }
    [PSCustomObject] @{ Test = 'Name'; Test2 = 'Name2'; Test3 = 'Name3'; Test4 = 23.73; Percents = 99 }
    [PSCustomObject] @{ Test = 'Name'; Test2 = 'Name2'; Test3 = 'Name3'; Test4 = 50.73; Percents = 105 } # will be trimmed to 100%
    [PSCustomObject] @{ Test = 'Name'; Test2 = 'Name2'; Test3 = 'Name3'; Test4 = 90; Percents = 105 } # will be trimmed to 100%
)

New-HTML {
    New-HTMLTable -DataTable $DataTable -AlphabetSearch {
        New-TablePercentageBar -ColumnID 4 # runs on defaults
        New-TablePercentageBar -ColumnID 3 -BackgroundColor Blue -TextColor White -BorderColor Grey -BarColor gold -BorderStyle ridge -Type round {
            New-TablePercentageBarCondition -Minimum 0 -Maximum 10 -BackgroundColor Blue -TextColor White -BarColor Red
            New-TablePercentageBarCondition -Minimum 11 -Maximum 20 -BackgroundColor Blue -TextColor White -BarColor Green
            New-TablePercentageBarCondition -Minimum 21 -Maximum 25 -BackgroundColor Blue -TextColor White -BarColor AppleBlossom
            New-TablePercentageBarCondition -Minimum 26 -Maximum 85 -BackgroundColor Grey -TextColor Black -BarColor Cyan
            New-TablePercentageBarCondition -Minimum 86 -Maximum 100 -BackgroundColor Blue -TextColor White -BarColor Yellow
        }
    } -ImmediatelyShowHiddenDetails
} -ShowHTML -FilePath $PSScriptRoot\Example7_PercentageBar.html -Online

Love it, as usual! Thanks!

Is this working in 1.9.0?
The example does not appear to be working for me...no errors

It is, but was working without -Online. I forgot to change version number in configuration url. Republished 1.10.0 which should work in both cases.

Thanks!


JMS support for Spring wolf.

Many organization use JMS protocol to interface with message queues brokers like IBM WMB, Apache ActiveMQ or Artemis, Tibco etc.

RabbitMQ supports AMQP protocol.
There is another protocol JMS https://www.oracle.com/java/technologies/java-message-service.html
It is used heavily in the Java world. Spring has a listener annotation for it called as JMSListener on the lines of RabbitListener or KafkaListener

I see. You are interested in the auto-detection of methods annotated with the JmsListener annotation.
Springwolf uses plugins (more details here) to scan for protocol specific annotations.
Although Jms is not a protocol, but rather an API, I can imagine it to be an own springwolf plugin.
In case anyone wants to get started on it (plugin + example project), feel free to. We are happy to assist.
To provide details about the protocol in use (anypointmq, ibmmq, jms are documented/mentioned in the asyncapi spec) via an custom annotation, a look at
KafkaAsyncOperationBinding might be helpful.

Thank you for the report, the issue has been addressed in the new release with the jms plugin.
Feel free to reopen this issue if there is still something missing.


Use graphql apis instead of db direct access

Right now we are accessing the database directly which complicates the setup and adds tons of logic for the views that could have been made querying the graphql instead. The problem was originating from the fact that we couldn't run graphql in production mode, and any substantial amount of requests caused the server to crash, however there has been many improvements in the graphql repo and the indexer too. Let's give it another shot.

closed by #77


Added check for hotspot enabled

Covers a scenario where the phone is connected to the PC running the adb client through the phones hotspot feature by adding a check to verify that the hotspot is enabled.

Lookin great! Merging

Lookin great! Merging


(maint) Adjust travis osx cacert paths as admin

Attempt to fix recently appearing failures like this by manipulating
the cert file as root:
+old_cacert_path=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre/lib/security/cacerts
+rm /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre/lib/security/cacerts
override rw-r--r--  root/wheel for /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre/lib/security/cacerts?
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

Test PASSed

CLA signed by all contributors.


If I use blacken-docs, does that mean I don't need to use black anymore

I see  pre-committ-config.yaml is the configuration file where you can set the category of files that use blacken-docs
For example, the following file instructs blacken-docs to format files with the suffixes RST, md, py, markdown, Tex
repos:
  - repo: https://github.com/psf/black
    rev: stable
    hooks:
      - id: black
        language_version: python3.7
  - repo: https://github.com/asottile/blacken-docs
    rev: master
    hooks:
    -   id: blacken-docs
        language: python
        files: '\.(rst|md|markdown|py|tex)$'

Does that mean I can remove black and just keep blacken-docs?
just like this:
repos:
  - repo: https://github.com/asottile/blacken-docs
    rev: master
    hooks:
    -   id: blacken-docs
        language: python
        files: '\.(rst|md|markdown|py|tex)$'

nope you still need black, and this is pretty easy to verify if you try it out:
$ pre-commit  run --all-files
[INFO] Installing environment for https://github.com/asottile/blacken-docs.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
blacken-docs.............................................................Passed
$ cat t.py
print(   "VERY UGLY"    )
$ cat .pre-commit-config.yaml
repos:
-   repo: https://github.com/asottile/blacken-docs
    rev: v1.6.0
    hooks:
    -   id: blacken-docs

the reason it covers py files is to rewrite docstrings:
$ cat t.py
def f():
    """

    ```python
    print(   "very ugly"   )
    ```
    """
$ pre-commit  run --all-files --show-diff-on-failure
blacken-docs.............................................................Failed
- hook id: blacken-docs
- exit code: 1
- files were modified by this hook

t.py: Rewriting...

pre-commit hook(s) made changes.
If you are seeing this message in CI, reproduce locally with: `pre-commit run --all-files`.
To run `pre-commit` as part of git workflow, use `pre-commit install`.
All changes made by hooks:
diff --git a/t.py b/t.py
index 2ae1412..050422c 100644
--- a/t.py
+++ b/t.py
@@ -2,6 +2,6 @@ def f():
     """

     ```python
-    print(   "very ugly"   )
+    print("very ugly")
     ```
     """

Ok, I see. Thank you.


BuilderInfo.CreateHandlerBuilderFn vs ValidateConfig

One function pointer field has an Fn suffix, one doesn't. We should be consistent. Let's check the Go conventions to see if there's a preference and stick to it consistently.

Done


Complete API documentation

We build API documentation for the babelizer, but some of the babelizer modules were missing docstrings. This PR updates all the babelizer modules with descriptive docstrings. Also included sphinx-click as a dependency to build docs for a click-based application.
This fixes #52.

This looks good! I think this is sufficient for the JOSS review. One suggestion that is based on my preferences: it might be nice to consider breaking up this single page into multiple, with each module having its own page. There is a lot of information here, so that might help make it a bit more digestible. But up to you all on how you would like to present the info

Thanks, @lheagy! I took your suggestion to break up the API docs into one module / page (and by doing so, I think it helped me catch some errors). I'll merge this PR and close the referring issue.


Remove claim on possible optional bindings in repeat-while conditions

The claim is immediatly disproved on the grammer rule description below that states that the while condition is an expression. An expression in turn does not comprise an optional binding. The grammar rule seems to be correct since it matches with the bahavior of the Swift compiler and the SwiftSyntax library.

This is all about repeat-while statements which only allow expressions in their while-condition as the grammar states and the compiler expects. An example from a Swift playground:

Thanks for that context — looking at the diff, I found the wrong part of the book.  This looks good to me!
@swift-ci Please test.


[#3883] OpenSSL SSLSession returns incorrect peer principal

Motivation:
According to the javadocs of SSLSession.getPeerPrincipal should be returning the identity of the peer, while we return the identity of the issuer.
Modifications:
Return the correct indentity.
Result:
Behavior match the documentation.

Cherry-picked into 4.0 (303cb535239a6f07cbe24a033ef965e2f55758eb) , 4.1 (29ac2ae3c255fb2fa1c1660f8e35d45c212430aa) and master (1644d733ecd388b0b3ee6403118f0f84e1102fe9)


Fixes to previous unknown issues

Fixed:

Players data not being synced automatticlly

A while ago we had an issue with some players loosing their starting money. This was due to the fact that they would.. Join Server > load in & get starting cash > Alt + f4 or something similar bypassing any other abort syncing features... they would then join back and have 0 because the script no longer thinks they are a _newplayer due to them having a database entry. (I think this is what caused it) and because no data was synced they are now on the default 0 cash. Correct me if I'm wrong please my head is hurting.

LGTM; merging...


Replicator giving issue , with jobs getting into crashed type

Hi team,
i have a 3 node couch cluster deployed on kubernetes, replication is set in a way like A-B, B-A, B-C, C-B, A-C, C-A using replicator, with continuous replication enabled.
From UI, i can see no issues with replication and everything is replicated properly but when i see the logs, i am seeing following logs,
Replicator GET ******  failed due to error sel_conn_closed

Can someone please help, with this issue? can this logs be ignored?

Also, one more thing would like to share is with scheduler/docs api, i do not see anything in the error count, its 0

It means the _changes feed connection is closed unexpectedly. If the error count is 0, it happens rarely enough that the error count is reset. So it's probably more rare than once a minute or so.
A few things to try:

Check if you're using a restrictive replication filter.
Increase the replicator connection timeout configuration to say 90000(msec).
Check if your load balancer (if you have one), has an idle connection timer then bump that too and then, check that it's not set to buffer connection data.

In general replicator will retry the replications on failure and continue where it left off. It's pretty resilient like that. So, if you don't want to track down the connection issues, and it seems your data replicates as intended you probably don't have to worry about it.

Hi @nickva
Thank you for the quick reply, i would need a further help as i am pretty new to couch

Where do i check this?
restrictive replication filter.

Also can i put this connection timeout under local.d directory in any ini file?

Thanks
Pallavi C

If your replication document doesn't have a filter specified then it's not a concern.
You can put the timeout in any local..d or local.ini file
https://docs.couchdb.org/en/stable/config/replicator.html#replicator/connection_timeout

Closing as there has been no activity in a while. Hopefully the suggested reply helped.


chore: refactor client code for cleanliness

Description
This cleans up some type-safety and style things in the front-end code:

Replaces a lot of foo && foo.method() calls with foo?.method() (and similarly for arrays).
Replaces "reduce" calls with slightly more efficient maps and flatMaps when possible (note: Node 11 and recent browsers have flatMap as a built-in array method, but the code wouldn't compile with it that way, leading to me just using the Lodash one)
Replaces a lot of 'any' type annotations with more specific ones.

There should be no changes to any functionality; this is meant to be purely a refactoring change for cleanup purposes.
Task Item
#minor

Coverage increased (+0.07%) to 54.596% when pulling 185a0756285baed24ed51ba7d2d2fd3d30060759 on beyackle/typeSafety_frontend into 34631bfcee2e3172cc2a9fc1759f1bbd176dbf65 on main.


Incompatible git command

Hi,
when trying to follow the installation instructions for the master branch on Ubuntu 16.04 I encountered the following error:
$ python Scripts/UpdateCommon.py
Cloning common-lib-amd-ADL into /home/jstephan/build/Common/Lib/AMD/ADL
error: unknown option `no-tags'
usage: git clone [<options>] [--] <repo> [<dir>]

    -v, --verbose         be more verbose
    -q, --quiet           be more quiet
    --progress            force progress reporting
    -n, --no-checkout     don't create a checkout
    --bare                create a bare repository
    --mirror              create a mirror repository (implies bare)
    -l, --local           to clone from a local repository
    --no-hardlinks        don't use local hardlinks, always copy
    -s, --shared          setup as shared repository
    --recursive           initialize submodules in the clone
    --recurse-submodules  initialize submodules in the clone
    --template <template-directory>
                          directory from which templates will be used
    --reference <repo>    reference repository
    --dissociate          use --reference only while cloning
    -o, --origin <name>   use <name> instead of 'origin' to track upstream
    -b, --branch <branch>
                          checkout <branch> instead of the remote's HEAD
    -u, --upload-pack <path>
                          path to git-upload-pack on the remote
    --depth <depth>       create a shallow clone of that depth
    --single-branch       clone only one branch, HEAD or --branch
    --separate-git-dir <gitdir>
                          separate git dir from working tree
    -c, --config <key=value>
                          set config inside the new repository

'git clone' failed with return code 129

Using python2 or python3 doesn't make a difference as this is a git error. I'm using the default git version in the Ubuntu repository:
$ git --version
git version 2.7.4

Removing the "no-tags" flag from the script worked for me but I don't know if this will cause issues at some point.

Removing the "--no-tags" from the script will not cause any issues, but may increase the time it takes to clone projects.  I don't recall what version of git introduced the "--no-tags" option, but it is available in git v2.11.


Fix Editor crash on Windows when cs script doesn't compile

and minor windows related tweaks
I didn't make an Issue. Lemme know if it is needed :)

I fixed what was commented on and added back the C# physics bindings

Physics changes are completely unrelated and should not be in this PR. Also just uncommenting those lines is not enough, as i already clarified in physics bindings issue :)

gotcha

This looks nice and clean! There is one more tiny style violation though :p Path checking is done in about perfect way it seems 👍 I'll verify and merge tomorrow, thank you for being patient with me :)

np
we're all better off with the nitpicked version than my original PR

This Uri bit is great. Thanks a lot!


Document WatchingStatefulWidget and WatchingStatefulWidgetMixin

I noticed in the docs that there is no use of StatefulWidgets, which makes sense. So without access to initState, how do I run code only once on first build?
More broadly, are there any plans to support lifecycle hooks, like initState, dispose, etc.?
Side note: I usually use flutter_hooks for this, with an empty dependency array passed to useEffect but seems watch_it is not compatible with HookWidget
Edit: I see that there are widgets and mixins for StatefulWidget as well. Maybe this should be documented. While this solves my issue, I think I'll keep this issue open for discussion on docs. Thanks

Indeed, there is a mixin for StatefulWidgets and a WatchingStatefulWidget see https://github.com/escamoteur/watch_it#the-watchingwidgets but I agree that I could add a sentence of using the WatchItStatefulWidget

Btw I'm thinking ob adding an executeOnce function

executeOnce would be really good. It would help with eliminating the need for StatefulWidgets altogether

after looking at the document, i'm needing help still with how i would make class MyApp extends WatchingStatefulWidget {. what would below look like to be able to use watchValue in _MyAppState ?
class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  late AppLinks _appLinks;
  StreamSubscription<Uri>? _linkSubscription;

  @override
  void initState() {
    super.initState();

    _initDeepLinks();
  }

  @override
  void dispose() {
    _linkSubscription?.cancel();

    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
   //needing to use watchValue
  }
}


Search

Is your feature request related to a problem? Please describe.
Sometimes it is hard to implement a search with nested folders
Describe the solution you'd like
It would be cool to implement a search option from the box

@aslanalyiev I'm not sure what the UI image is for filtering a tree view by search, do you have a specific image?
Or do you have any references?

I meant to provide a prop where a user can put a string and TreeComponent will automatically filter data(nested as well)
const treeDataWithALotOfNestedChildren = [....];

const searchText = 'name of some element from the tree data'; //some string that a user provided to find needed the tree elements

<Tree
   tree={treeDataWithALotOfNestedChildren}
   ...requiredProps
   searchQuery={searchText}
/>

result:
New filtered tree with the preservation of the structure(e.g. if a deeply nested child has a lot of parents that don't meet searchText they also should be rendered).
initialTree:

titleR
title2
title3
titleR2

searchText = title3
result:

titleR
title2
title3

smth like that :)

any update👀


[AMSDK-10268]Handle Analytics response identity events

Listen for Analytics response identity event
Dispatch Avid sync event
Add unit tests

Description

-Handle Analytics response identity events
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Got it, will fix it soon.


How to get *interface{} of field in struct.

What version of Go are you using (go version)?

$ go version 1.11.4

Does this issue reproduce with the latest release?
Not an issue, just a question.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/shihaonan/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/shihaonan/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.11.4/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.11.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/5y/tg5wtlx9255g3mfhp8g0fzn80000gn/T/go-build386392868=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

https://play.golang.org/p/3GtnyYYrjlM
Run code will Throw a panic:
"panic: reflect: reflect.Value.Set using unaddressable value"
I know change the type of i from interface{} to *interface{} could be right, but how to get *interface{} of field in struct?


Add an explicit comment to .env.example advising to make a copy of that file

Describe the bug
Its very easy to miss the step of making a copy of .env.example into .env.  Users end up putting their credentials into .env.example, never making a copy if it and then being confused why the app is making invalid tokens.
Additional context
Can we just add a comment to .env.example that tells users to make a copy of that file?

Sure thing @devinrader! That's a good idea.


Fix env variable setting for doc build

What does this PR do?
This PR fixes a problem for setting the env variable for the doc version - hopefully the last fix needed :)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

OK to merge this @regisss ?


Weighted RNA support score for variant sequences

The current supporting read count drops any read which only partially spans a variant sequence. This causes counts to fall very sharply with increasing variant sequence length. A smoother measure of RNA supporting for a variant sequence would give partially spanning reads weights less than 0 (proportional to how many bases they overlap and how many sequences contain that subsequence).

It might be interesting to explore weighting based on the "sequence uncertainty" around a variant. For example, if the all of the reads spanning the i th positions upstream of a given variant all agree on the bases at those positions then perhaps partially spanning reads can be given full weight (e.g. equivalent to fully spanning reads). Conversely, if there is a significant amount of uncertainty about the bases at positions surrounding a variant, then the weight given partially overlapping reads can decrease more sharply. In this way read scoring takes into account not only support for a variant, but also the degree of support for positions surrounding a variant. This also may have the added benefit of relaxing the requirement for fully-spanning reads in regions in which we're fairly certain of the sequence surrounding a variant, and emphasize spanning reads for variants in regions of highly uncertain sequence context.


Repository Name

Description
If this repository is only going to contain the maintainer dashboard, it would probably be good to rename the repo to something like openff-maintainers or openff-status to avoid confusion.
cc @mattwthompson @j-wags @dotsdl

openff-status

I'd suggest plain openforcefield/status

Agreed. If there are no objections in the next three hours, I'll change it.

Jumping the gun on this since we seem to have consensus

Just reviewing my notifications -- I approve this change.


Requiring translation files generates CSRF related error.

When i add

//= require pickadate/translations/es_ES

to application.js I get this error:
Can't verify CSRF token authenticity
Completed 401 Unauthorized in 1ms (ActiveRecord: 0.0ms)

If i remove that line it works fine.

I haven't got much to add as to why this happens, but I can confirm that this happens for me as well. Seems like a really weird bug.

:+1: Please fix this.

Here's a fix:
jQuery.extend( jQuery.fn.pickadate.defaults, {
    hiddenName: true
});

Explanation
When using translations the value being displayed are different from the the value being submitted by using different values for the options format and formatSubmit. This works by adding an hidden input with the same name + suffix to the end of the form like post[created_at]_hidden. Input names like these apparently cause errors like these in ruby servers and rails (see: https://github.com/amsul/pickadate.js/issues/208)
By setting hiddenName: true this is fixed by just using adding an hidden input with the same name instead of adding the suffix. This is the best solution imo. If you want you can also fix this by removing the suffix with hiddenSuffix: "" and optionally set an hidden prefix with hiddenPrefix: "".

I would argue setting hiddenName to true by default, but i could imagine this would break things for users that like to upgrade and already rely on parsing values with the suffix/prefix.


[FEATURE REQUEST 2.0] Support null textures for ISpriteBatch

Description
ISpriteBatch in it's current state doesn't support passing a null to it's texture parameter in the Draw method.
The Why
This feature should implemented because what if the user doesn't want to draw a quad with a texture and instead would like to draw a colored quad?
The How
I propose we do one of the following:

Make the index (0) of u_textures in the fragment shader represent a white texture that is preloaded.
Or even better, just offset each index by 1 in the texture binder and don't multiply the color output of the fragment shader by the texture bound to zero, as nothing is likely to be bound, like so:

case 1: color *= texture(u_textures[1], in_texCoord); break;
case 2: color *= texture(u_textures[2], in_texCoord); break;
case 3: color *= texture(u_textures[3], in_texCoord); break;
case 4: color *= texture(u_textures[4], in_texCoord); break;
default: break; // If zero, just break and draw the color the user specified.

Perhaps just have overload methods would be a better idea.


Some questions about code details and abnormal phenomenon

Hi, it's very kind of you for releasing the code of the paper, and there are some questions about code details and abnormal phenomenon:

As is shown in the first image, I am bit confused of the codes in 140-144 lines of ./data/dtu.py. The reference should be the first element of "view_ids", the in codes in 140-144 lines you have put in the last position. Is something wrong with my understanding?

And again in the codes in 233-234 lines of ./train_mvs_nerf_pl.py, here appears two notions, tgt and ref. So may I ask what exactly src, ref, and tgt stands for?

Is the "with_depth" option means that we have got the depth map of dataset and we should not activate it if we do not get the depth map?

Last qusetion, when I train with my own dataset, nan appears after a few iterations. Have you ever met with the same problem?
Looking forward to your answers. Thanks for your work again.

Hi, thanks, 1. we define the 'reference view' (mostly used in other papers) to be target view, so we put it at the last, and randomly select 3 views to the source views. 2. please refer to the figure of our pipeline, 3. that's right, 4. oh, I didn't train this model with other datasets, so I don't have much sense on this issue. I think you can try to overfitting on a single scene, I believe this can help you for debugging.

Hi, thanks, 1. we define the 'reference view' (mostly used in other papers) to be target view, so we put it at the last, and randomly select 3 views to the source views. 2. please refer to the figure of our pipeline, 3. that's right, 4. oh, I didn't train this model with other datasets, so I don't have much sense on this issue. I think you can try to overfitting on a single scene, I believe this can help you for debugging.

Thanks for your reply quite a lot!


problems when dealing with svg FeImage Links

It's seems like a bug on usvg.
This is my test svg
<svg width="1080" height="1440" viewBox="0 0 1080 1440" version="1.1" xmlns="http://www.w3.org/2000/svg"
     xmlns:xlink="http://www.w3.org/1999/xlink">
    <defs>
        <rect fill="#b77d21" opacity="0.3" id="feImageSource" width="1080" height="1440">
        </rect>
        <filter id="filter01">
            <feImage xlink:href="#feImageSource" x="0%" y="0%" width="100%" height="100%">
            </feImage>
        </filter>
    </defs>
    <rect x="0" y="0" width="1800" height="1440" filter="url(#filter01)" />
</svg>

and usvg out miss rect#feImageSource tag. like this:
<svg width="1080" height="1440" viewBox="0 0 1080 1440" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:usvg="https://github.com/RazrFalcon/resvg" usvg:version="0.11.0">
    <defs>
        <filter id="filter01" x="-0.1" y="-0.1" width="1.2" height="1.2">
            <feImage x="0" y="0" width="1080" height="1440" color-interpolation-filters="linearRGB" preserveAspectRatio="xMidYMid" image-rendering="optimizeQuality" xlink:href="#feImageSource" result="result1"/>
        </filter>
    </defs>
    <g filter="url(#filter01)">
        <path fill="#000000" stroke="none" d="M 0 0 L 1800 0 L 1800 1440 L 0 1440 Z"/>
    </g>
</svg>

when usvg convert the svg element (convert_element), it will create a 'g' tag some time. but, the id has not set on 'g' tag.
the <g opacity="0.3"><rect id="#id0"></rect></g> is not equal to <rect id="#id0" opacity="0.3"></rect>
and then. due to it has no id. it has been removed in remove_unused_defs

I try to move element id to the group node, but test thread has overflowed its stack.
I make all group which usvg created neet copy the element id if have. code, and seems like is there make it stack overflow.
I want to find the reason, and may need help.

Yes, I can confirm the bug. Will fix it on weekends.

Could i know when to fix this bug?

No time frame, sadly.


Expired token causes all CLI commands to fail

This may have been addressed in this commit, but I wanted to call it out in case it goes deeper.
If I have an expired token in .aptible/tokens.json, all commands fail (including login and even version) with the error "An error occurred: Expired Token". I do see in this commit that the message will change, but it's not clear that the error won't still occur. I have to rimraf .aptible in order to login again.

0.16.9 fixed the problem! Thanks for catching that.


peer-to-peer code reviews/day3

you did a great job in implementing the requirements of the project.
to highlight some:
-no linter error
-Professional README file
-good use of git flow
Required Changes
when I click the comment button the popup window is not according to the wire frame. please update it according to the wireframe provided.
the close button is not clearly visible. kindly make it clear.
Optional suggestions
when I click all the links in your nav bar all are not working except the Home. kindly implement them.

Hi @haftamudesta , all required changed was dued
Thank you


Install Spacy and Spacy model package as a part of the Pebblo install

Description:
Install the Spacy and Spacy model package as a part of the Pebblo install.

Spacy model package(en_core_web_lg-3.7.1)
Spacy(>=3.7.2, <3.8.0) Source: en_core_web_lg-3.7.1 release docs
Presidio version(2.2.351 ) support for spacy versions (spacy <4.0.0,>=3.4.4).  Source: Presidio code

Source of GitHub link:
The GitHub link used for installing is taken from the Spacy package that is installed with the Pebblo using the following command:
spacy info en_core_web_lg --url

Reference: Spacy Docs
Testing:
Tried building & installing Pebblo on my local. It shows the download step.

@srics
We tried to publish this on the test PyPI and encountered the following error.
Upon research, I found that URL requirements are not permitted on PyPI.
Error:
Invalid value for requires_dist. Error: Can't have direct dependency: 'en-core-web-lg @ https://github.com/explosion/spacy-models/releases/download/en_core_web_lg-3.7.1/en_core_web_lg-3.7.1-py3-none-any.whl
Issue links:

Allow PEP 508 URL requirements in requires_dist
Cannot upload with external dependency due to "Invalid value for requires_dist"


MSB4064 : "TargetFramework" not available in task "GenerateBuildSessionId" loaded  from Xamarin.iOS.Tasks

I have this message in french so the translation may not be as accurate as it should.
Any Clue ?
I used that target list. It happens when adding Xamarin.iOS10.
<Project Sdk="Xamarin.Legacy.Sdk/0.2.0-alpha4">
  <PropertyGroup>
    <TargetFrameworks>Xamarin.iOS10;netstandard2.1;net7.0-android;net7.0-ios</TargetFrameworks>
    <SupportedOSPlatformVersion Condition="'$(TargetFramework)' == 'net7.0-ios'">15.0</SupportedOSPlatformVersion>

Can you share a diagnostic MSBuild log?

I switched from rider to VS and that fixed it.


0.118.0 - Bad Gateway

Nach einem Update von 0.116.4 auf 0118.0 meldet EVCC leider immer 502 Bad Gateway.
An der evcc.yaml wird nichts geändert. HomeAssistant ebenfalls nicht.
  Seite.
Hier noch ein Auszug vom Log (Debug mode)
Neustart HomeAssistant, Elli Wallbox, Neukopplung brachten keine Abhilfe.
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/06/11 13:18:10 evcc 0.118.0
[main  ] INFO 2023/06/11 13:18:10 using config file: /config/evcc.yaml
[main  ] INFO 2023/06/11 13:18:10 starting ui and api at :7070
[db    ] INFO 2023/06/11 13:18:10 using sqlite database: /data/evcc.db
[mqtt  ] INFO 2023/06/11 13:18:10 connecting evcc-660423155 at tcp://<IP_ADDRESS>:1883
[mqtt  ] DEBUG 2023/06/11 13:18:10 tcp://<IP_ADDRESS>:1883 connected
[eebus ] INFO 2023/06/11 13:18:10 Local SKI:  54e07c6b293baf90c3c2a6c0ef18ac641c9aa5b9
[eebus ] DEBUG 2023/06/11 13:18:10 mdns: announce
[eebus ] DEBUG 2023/06/11 13:18:10 mdns: using zeroconf
[eebus ] DEBUG 2023/06/11 13:18:10 starting websocket server on :4712
[eebus ] DEBUG 2023/06/11 13:18:10 mdns: start search
[eebus ] DEBUG 2023/06/11 13:18:10 ski: bb661a4fc1650c04c34f53c1154259651ddab929 name: Elli-Wallbox-2223A2K669 brand: Elli model: Wallbox typ: Wallbox identifier: Elli-Wallbox-2223A2K669 register: false host: wallbox-2223A2K669.local. port: 4712 addresses: [<IP_ADDRESS>]
[eebus ] DEBUG 2023/06/11 13:18:10 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 1.565s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:18:11 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>
[eebus ] DEBUG 2023/06/11 13:18:11 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>:4712
[eebus ] DEBUG 2023/06/11 13:18:12 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error:  websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:18:12 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:18:12 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 7.799s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:18:19 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>
[eebus ] DEBUG 2023/06/11 13:18:19 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>:4712
[eebus ] DEBUG 2023/06/11 13:18:20 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error:  websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:18:20 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:18:20 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 26.428s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:18:46 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>
[eebus ] DEBUG 2023/06/11 13:18:46 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>:4712
[eebus ] DEBUG 2023/06/11 13:18:46 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error:  websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:18:46 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:18:46 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 42.695s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:19:29 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>
[eebus ] DEBUG 2023/06/11 13:19:29 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>:4712
[eebus ] DEBUG 2023/06/11 13:19:29 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error:  websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:19:29 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:19:29 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 2m39.879s to minimize double connection probability
[main  ] FATAL 2023/06/11 13:19:40 cannot create charger 'wallbox': cannot create charger 'template': cannot create charger 'eebus': i/o timeout
[main  ] FATAL 2023/06/11 13:19:40 will attempt restart in: 5m0s
[eebus ] DEBUG 2023/06/11 13:22:09 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>
[eebus ] DEBUG 2023/06/11 13:22:09 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at <IP_ADDRESS>:4712
[eebus ] DEBUG 2023/06/11 13:22:10 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error:  websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:22:10 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:22:10 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 5m29.943s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:24:40 mdns: stop announcement
Die URL direkt (über Port 7070) aufzurufen ist leider ebenfalls erfolglos - solange nicht die "finale" Fehlermeldung kommt.  :(
"Firefox kann keine Verbindung zu dem Server unter ws://homeassistant.local:7070/ws aufbauen."
Viele Grüße

Short Update - on a native Installation (same evcc.yaml with modified IP) 0.118.0 works well. Maybe problem with the docker container?

Topic solved. Don’t know how but I also cannot provide further traces

Hallo chrdal,
was hast du gemacht, dass es wieder funktioniert?
Meine Logdatei sieht genauso aus wie deine:
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/06/21 18:20:19 evcc 0.118.1
[main  ] INFO 2023/06/21 18:20:19 using config file: /config/evcc.yaml
[main  ] INFO 2023/06/21 18:20:19 starting ui and api at :7070
[db    ] INFO 2023/06/21 18:20:19 using sqlite database: /data/evcc.db
[eebus ] INFO 2023/06/21 18:20:19 Local SKI:  063efa776ce229de53d73a37138b2cccb5c2a18e
[eebus ] DEBUG 2023/06/21 18:20:19 mdns: announce
[eebus ] DEBUG 2023/06/21 18:20:19 mdns: using zeroconf
[eebus ] DEBUG 2023/06/21 18:20:19 starting websocket server on :4712
[eebus ] DEBUG 2023/06/21 18:20:19 mdns: start search
[eebus ] DEBUG 2023/06/21 18:20:24 ski: b847b94b1655feb88055cfb94086e09dbd48065b name: Elli-Wallbox-2137A1MJ50 brand: Elli model: Wallbox typ: Wallbox identifier: Elli-Wallbox-2137A1MJ50 register: false host: wallbox-2137A1MJ50.local. port: 4712 addresses: [<IP_ADDRESS>]
[eebus ] DEBUG 2023/06/21 18:20:24 delaying connection to b847b94b1655feb88055cfb94086e09dbd48065b by 612ms to minimize double connection probability
[eebus ] DEBUG 2023/06/21 18:20:24 trying to connect to b847b94b1655feb88055cfb94086e09dbd48065b at <IP_ADDRESS>
[eebus ] DEBUG 2023/06/21 18:20:24 initiating connection to b847b94b1655feb88055cfb94086e09dbd48065b at <IP_ADDRESS>:4712
[eebus ] DEBUG 2023/06/21 18:20:29 connection to b847b94b1655feb88055cfb94086e09dbd48065b failed:  dial tcp <IP_ADDRESS>:4712: i/o timeout
[eebus ] DEBUG 2023/06/21 18:20:29 trying to connect to b847b94b1655feb88055cfb94086e09dbd48065b at wallbox-2137A1MJ50.local.
[eebus ] DEBUG 2023/06/21 18:20:29 initiating connection to b847b94b1655feb88055cfb94086e09dbd48065b at wallbox-2137A1MJ50.local.:4712
[eebus ] DEBUG 2023/06/21 18:20:34 connection to b847b94b1655feb88055cfb94086e09dbd48065b failed: dial tcp <IP_ADDRESS>:4712: i/o timeout
[eebus ] DEBUG 2023/06/21 18:20:34 restarting mdns search
[eebus ] DEBUG 2023/06/21 18:20:34 delaying connection to b847b94b1655feb88055cfb94086e09dbd48065b by 6.151s to minimize double connection probability
[eebus ] DEBUG 2023/06/21 18:20:40 trying to connect to b847b94b1655feb88055cfb94086e09dbd48065b at <IP_ADDRESS>
[eebus ] DEBUG 2023/06/21 18:20:40 initiating connection to b847b94b1655feb88055cfb94086e09dbd48065b at <IP_ADDRESS>:4712

Your evcc config is wrong, it is not able to start. So you get bad gateway, since there is no evcc running.

Hey! I haven't modified my evcc.yaml file and after 3 days it was working. I have not glue why it is working now again. I thought that the docker container maybe have network problems but I couldn't solve them. Sorry.

Hi thecem, thanks for the hint. But why has it worked over several months and now it doesn't?
When it helps I can also attach my config here. EVCC is/was running over home assistant on a rasperry pi 4.
BR


permission declaration inside the application tag does not send any notification as that does not allow app to request the required permissions.

Expected behaviour
There should be a notification when the permission is declared inside application tag in the manifest file or the docs should be updated to ensure that users of the library do not forget to declare the permissions outside the application tag in the manifest file.
Actual behaviour
The request for the permission simply does not show up and the permission is not granted.
Steps to reproduce
Version of the library

Hi @RbkGh, thanks for your request but Dexter's purpose is to handle all the boiler plate related to the permission handling so you can focus in your app business logic.
If you declare your permissions outside the application tag, Dexter will behave as the system, so that's not an issue.
Once said that, if you have a PR that solves the problem you've described, I encourage you to submit it so we can review it and discuss about it.

#196 this pull request should enhance this


Add mewlzebub by vivivivivi

Song Name
mewlzebub
Artist Name
vivivivivi
Source
Youtube
Youtube Link
hgsRUh65ec4
Direct File Link
No response
Song ID
63082
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 27122654
Downloaded: No

accept


Added InputStream and OutputStream for FileClient upload and download

@alzimmermsft @jaschrep-msft @rickle-msft

For now use a similar code pattern to what blobs has for its InputStream and OutputStream methods.


fairseq fails with RuntimeError: _Map_base::at

Trying to run fairseq using the following command results in error
$ python train.py data-bin/iwslt14.tokenized.de-en   --lr 0.25 --clip-norm 0.1 --dropout 0.2 --max-tokens 4000   -       -arch fconv_iwslt_de_en --save-dir checkpoints/fconv
| distributed init (rank 1): tcp://localhost:11807
| distributed init (rank 4): tcp://localhost:11807
Exception ignored in: <module 'threading' from '/opt/conda/envs/pytorch-py35/lib/python3.5/threading.py'>
Traceback (most recent call last):
File "/opt/conda/envs/pytorch-py35/lib/python3.5/threading.py", line 1286, in _shutdown
Traceback (most recent call last):
Traceback (most recent call last):
File "", line 1, in
File "", line 1, in
Traceback (most recent call last):
File "train.py", line 29, in
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 106, in spawn_main
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 106, in spawn_main
Traceback (most recent call last):
File "", line 1, in
exitcode = _main(fd)
exitcode = _main(fd)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 116, in _main
main(args)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 116, in _main
File "train.py", line 21, in main
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 106, in spawn_main
multiprocessing_main(args)
File "/home/nimbix/fairseq/multiprocessing_train.py", line 40, in main
self = pickle.load(from_parent)
self = pickle.load(from_parent)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/synchronize.py", line 112, in setstate
File "", line 969, in _find_and_load
Traceback (most recent call last):
File "", line 1, in
p.join()
exitcode = _main(fd)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/process.py", line 121, in join
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 115, in _main
Traceback (most recent call last):
File "", line 1, in
File "", line 958, in _find_and_load_unlocked
Traceback (most recent call last):
File "", line 1, in
prepare(preparation_data)
res = self._popen.wait(timeout)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 106, in spawn_main
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 226, in prepare
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/popen_fork.py", line 51, in wait
File "", line 673, in _load_unlocked
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 106, in spawn_main
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 106, in spawn_main
File "", line 661, in exec_module
return self.poll(os.WNOHANG if timeout == 0.0 else 0)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/popen_fork.py", line 29, in poll
_fixup_main_from_path(data['init_main_from_path'])
File "", line 750, in get_code
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 278, in _fixup_main_from_path
pid, sts = os.waitpid(self.pid, flag)
exitcode = _main(fd)
File "/home/nimbix/fairseq/multiprocessing_train.py", line 82, in signal_handler
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 116, in _main
exitcode = _main(fd)
exitcode = _main(fd)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 116, in _main
File "", line 819, in get_data
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/spawn.py", line 116, in _main
raise Exception(msg)
KeyboardInterrupt
Exception:
-- Tracebacks above this line can probably be ignored --
Traceback (most recent call last):
File "/home/nimbix/fairseq/multiprocessing_train.py", line 45, in run
args.distributed_rank = distributed_utils.distributed_init(args)
File "/home/nimbix/fairseq/fairseq/distributed_utils.py", line 29, in distributed_init
world_size=args.distributed_world_size, rank=args.distributed_rank)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/site-packages/torch/distributed/init.py", line 46, in init_process_group
group_name, rank)
RuntimeError: _Map_base::at
self = pickle.load(from_parent)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/queues.py", line 24, in
run_name="mp_main")
self = pickle.load(from_parent)
self = pickle.load(from_parent)
File "/opt/conda/envs/pytorch-py35/lib/python3.5/runpy.py", line 254, in run_path
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/queues.py", line 24, in
File "/opt/conda/envs/pytorch-py35/lib/python3.5/multiprocessing/queues.py", line 24, in

What version of pytorch and fairseq are you using?

pytorch 0.2 and fairseq (latest checkout)

We require pytorch >= 0.4.0, please update your pytorch installation and try again. Reopen the issue if it's still not working.

I updated to latest pytorch  and fairseq

print(torch.version)
0.5.0a0+7ca8e2f

and the fairseq code does run. However, when I monitor the GPU utilization (using nvidia-smi), I dont see any process running on the GPU. Any idea why this could happen ?
$ CUDA_VISIBLE_DEVICES="0" python3 train.py data-bin/wmt14_en_de   --lr 0.5 --clip-norm 0.1 --dropout 0.2 --max-tokens 4000   --criterion label_smoothed_cross_entropy --label-smoothing 0.1   --lr-scheduler fixed --force-anneal 50   --arch fconv_wmt_en_de --no-save --no-progress-bar --log-interval 10 --max-epoch 1 --max-update 10
Namespace(arch='fconv_wmt_en_de', clip_norm=0.1, criterion='label_smoothed_cross_entropy', curriculum=0, data='data-bin/wmt14_en_de', decoder_attention='True', decoder_embed_dim=768, decoder_embed_path=None, decoder_layers='[(512, 3)] * 9 + [(1024, 3)] * 4 + [(2048, 1)] * 2', decoder_out_embed_dim=512, device_id=0, distributed_backend='nccl', distributed_init_method=None, distributed_port=-1, distributed_rank=0, distributed_world_size=1, dropout=0.2, encoder_embed_dim=768, encoder_embed_path=None, encoder_layers='[(512, 3)] * 9 + [(1024, 3)] * 4 + [(2048, 1)] * 2', force_anneal=50, label_smoothing=0.1, log_format=None, log_interval=10, lr=[0.5], lr_scheduler='fixed', lr_shrink=0.1, max_epoch=1, max_sentences=None, max_sentences_valid=None, max_source_positions=1024, max_target_positions=1024, max_tokens=4000, max_update=10, min_lr=1e-05, momentum=0.99, no_epoch_checkpoints=False, no_progress_bar=True, no_save=True, optimizer='nag', restore_file='checkpoint_last.pt', sample_without_replacement=0, save_dir='checkpoints', save_interval=-1, seed=1, sentence_avg=False, share_input_output_embed=False, skip_invalid_size_inputs_valid_test=False, source_lang=None, target_lang=None, train_subset='train', valid_subset='valid', validate_interval=1, weight_decay=0.0)
| [en] dictionary: 40471 types
| [de] dictionary: 42715 types
| data-bin/wmt14_en_de train 3900144 examples
| data-bin/wmt14_en_de valid 39412 examples
| model fconv_wmt_en_de, criterion LabelSmoothedCrossEntropyCriterion
| num. model params: 213412278
| training on 1 GPUs
| max tokens per GPU = 4000 and max sentences per GPU = None
/usr/local/lib/python3.5/dist-packages/torch/autograd/function.py:41: UserWarning: mark_shared_storage is deprecated. Tensors with shared storages are automatically tracked. Note that calls to set_() are not tracked
'mark_shared_storage is deprecated. '
/home/nimbix/fairseq/fairseq/trainer.py:193: UserWarning: torch.nn.utils.clip_grad_norm is now deprecated in favor of torch.nn.utils.clip_grad_norm_.
grad_norm = utils.item(torch.nn.utils.clip_grad_norm(self.model.parameters(), self.args.clip_norm))
| epoch 001 | loss 15.266 | nll_loss 15.176 | ppl 37023.27 | wps 10149 | ups 2.4 | wpb 3936 | bsz 121 | num_updates 10 | lr 0.5 | gnorm 3.668 | clip 100% | oom 0 | sample_size 3936.1

fairseq only supports GPU training, so it's definitely using GPUs... note that fairseq only appears in nvidia-smi after training has begun (e.g., it is not resident during data loading). Please test with a small pytorch script and confirm that your setup is correct. If not then please open an issue with pytorch.


Formatting

Spacing between groups of text and images are too large. Some of the images themselves are also too large. This is a common issue throughout the LEARN ABOUT FLUIDS and LEARN ABOUT PIV part of the app.
Another issue of formatting is the scroll bar; it's covering some of the text and it needs to be moved out of the way and further off to the side.

Pull request #12 fixes this

Pull request #12 fixes this


Show MessageBox on error (PropertiesPanel) and remove Panel class (not that useful)

Removed the Panel class as it doesn't seem to do anything and generates errors (not critical for compilation but why not ?). Changed the way the properties file exception is thrown (see the comment in the relevant code part).

Hey by the way, would you mind working on more error handling? I know there are a lot of try/catches, but I am going to work on the White List for now. If you wouldn't mind, it would be really helpful if you worked on handling errors!

No problem ! I'll work on error handling. Actually, I haven't tested it yet with a server, that is how I discovered the properties thing I guess. See you in a couple hours with some new commits ;)

@Frazew I just committed the changes I've made. Since it's harder to mess with the whitelist directly, it will tell them how to use the commands to do it. This has the added advantage of working while they are in game, which is more convenient :smile:


Don't display progress notifications when uploading blobs

An alternative to this approach would be to suppress notifications if suppressLogs is true. But this implementation seemed cleaner and returns us to the old functionality before the SDK update.
Fixes #536

Can you give examples of what the logs looked like before and what they look like now?

Here's the old logs:

And new logs:

Blob deletion logs were removed in #513, do we want those back?

Blob deletion logs were removed in #513, do we want those back?

Yeah I think so


Adaptive X-Lab

Project Lead: Thomas Fiorelli

Mentor: @nohorse @emilyclyde

Welcome to OL2! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training :tada:.

Before Week 1 (Sept 23): Your first mentorship call

[ ] Complete the OLF self-assessment (online, printable).  This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
[ ] Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Sept 30): First Cohort Call (Open by Design)

[ ] Complete Assignment 'Write Your Vision or Mission Statement'. Leave a comment on this issue with your draft vision statement & be ready to share this on the call.
[ ] Watch 'Mozilla & Working Open'.
[ ] Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Oct 7): Mentorship call

[ ] Look up two other projects and comment on their issues with feedback on their vision statement.
[ ] Complete your Open Canvas (instructions, canvas). Comment on this issue with a link to your canvas.
[ ] Start your Roadmap. Comment on this issue with your draft Roadmap.

Before Week 4 (Oct 14): Cohort Call (Build for Understanding)

[ ] Look up two other projects and comment on their issues with feedback on their open canvas.
[ ] Pick an open license for the work you're doing during the program.
[ ] Use your canvas to start writing a README, or landing page, for your project. Link to your README in a comment on this issue.

This issue is here to help you keep track of work during the first month of the program. Please refer to the OL2 Syllabus for more detailed weekly notes and assignments past week 4.

@emilyclyde I sat down with Will and Audry today!

as you work on your Open Canvas share a link to your copy here!


New domestic address javascript autocomplete component using google classes #72 #75 [TGER-140]

#72 #75
I remade the component using Google provided classes.
Google Class 'Autocomplete' handles session tokens automatically.  We still need to test this as charges can rack up quickly if not handled properly.

the Package addresses config is modified to include a "Google Places API Key" reference to a Project's .env file

Frontend example
https://play.tailwindcss.com/t8e1AuhUos
When the User searches in the 1st search bar, a dropdown of 'autocomplete' results will show up.
When the User clicks a dropdown result, the result is parsed into the address fields in the 2nd input bar.
These fields cannot be altered, except Address Line 2.  That is data Google does not have.
I chose to make these fields read-only, so we can verify that these addresses are real (according to Google).

Thank you. per our discussions on Slack, I would like to make some modifications to it, but I'm excited to see it in use.


Azure DevOps Server 2019 does not show Pipelines Settings, Pipelines Release Retention and Test Retention in project settings page

I want to configure yaml build pipelines Symbol Store retention as stated in https://learn.microsoft.com/en-us/azure/devops/pipelines/policies/retention?view=azure-devops-2019&tabs=yaml but 'Pipelines' sections 'Settings' and 'Release Retention' items do not show up in UI. Likewise in section 'Test' the item 'Retention' is missing.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 2931f833-b378-efa9-2c43-0d2afea22bd7
Version Independent ID: ba3138ef-dc42-16c9-fcb3-1af441be7eb8
Content: Retention policies for builds, releases, and test - Azure Pipelines
Content Source: docs/pipelines/policies/retention.md
Product: devops
Technology: devops-cicd-policies
GitHub Login: @juliakm
Microsoft Alias: rabououn

@kkluwehkg -- thank you for your feedback.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@juliakm -- please look into this issue.

@kkluwehkg Thanks for flagging this. For DevOps 2019, there isn't a Pipeline > Settings section. I do see the other two. Here's a screenshot. To get here, I went to Project settings for an individual project. I'll update the article.


[communication] Migrate @azure-rest/communication-job-router to ESM/vitest

Packages impacted by this PR

@azure-rest/communication-job-router

Issues associated with this PR

https://github.com/Azure/azure-sdk-for-js/issues/31338

Describe the problem that is addressed by this PR
Migrates the @azure-rest/communication-job-router package to ESM and vitest.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

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

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


Remove Microsoft-related logos

Removing Mircosoft-related logos from the badge due to:

https://github.com/simple-icons/simple-icons/issues/11236

Before
After

As the Simple Icons project maintainer, I still hope Microsoft will allow us to use it. So I created this PR to attract your attention.

@LitoMore Thanks for the PR. I see we publish the logos at https://code.visualstudio.com/brand. Would these work for you?

Thanks @chrmarti - though the comms we've had from Legal have suggested we:

Can only use icons from the below sources, and
Only include the icons in the format they're presented

Power Platform
Dynamics 365
Microsoft 365
Azure

As the Simple Icons project is a monochrome icon library, we would be breaking terms on point 2 straight away - and looking at the source you've shared above, we would have to adapt the icons published there to include too.

Thanks for the continued discussion and feedback here. We've removed the use of the logo and will provide any updates in the future if something changes in this space.


Option for disabling the snippets functionality

Hello,
Have you thought that, in the future, you can disable the snippets functionality? I think that this will be good if you have installed another extension that it's focused only in snippets. In this moment, for example with this extension C# Snippets, when you are going to insert and snippet you have a duplicated entry for every snippet. What is your opinion about this? Thanks and congratulations for your extension!

Unfortunately, we currently don't control how snippets appear in the completion list. This is controlled by the VS Code setting, "editor.snippetSuggestions", which has a default value of inline.

Thank you for your quick response, I know that it's not a definitive solution but the author of the mentioned extension has writed a post telling how to disable manually some snippets, regardless from who are (sadly in his case it's yours, but it's a solution for any snippet extension) How to disable the C# snippets for the C# extension of Visual Studio Code/ Thank you so much, I will close this question, thank you again.


Apply the mousemove listener to the handlers only

It is overkill to add it to the whole document.

Ha, it is needed so the movement continues even when the mouse leaves the handler.


Add option to sort json by keys

Hi @North101, thanks for the pull request. I will merge it lately today. Thanks!

You're welcome. Thanks for the great extension!

Until the end of the week I'll release a version with your pull request, thanks again.

0.10.0 is rolling out with your contributions, thanks!


Metadata should allow for more than just strings

Metadata field should allow for any object to be passed to and from the API.
We should find a way to allow this to happen.

Strings can contain JSON data, therefore can be serialized/deserialized manually by end-programmers to any kind of object - even more than our Tapglue objects ;) This is my solution, but if you find any other we can try it.

I've created the following program and it seems to work ok:
import com.google.gson.Gson;
import com.google.gson.annotations.Expose;
import com.google.gson.annotations.SerializedName;

import java.util.HashMap;

class Main {
    public static void main(String[] args) {
        case1();
        case2();
        case3();
    }

    private static void case1() {
        MyClassTwo y = new MyClassTwo();
        y.FieldIsh = "yey";

        MyClass cls = new MyClass();
        cls.Field = "Hello";
        cls.Field2 = y;

        String serializedObj = serializeToJson(cls);
        System.out.printf("ehlo: %s\n", serializedObj);

        MyClass x = deserializeFromJson(serializedObj);
        System.out.printf("aloha: %s\n", x.Field);
        System.out.printf("aloha: %s\n", x.Field2);

        if (x.Field2 instanceof MyClassTwo) {
            System.out.printf("yup\n");
        }
    }

    private static void case2() {

        MyClass cls = new MyClass();
        cls.Field = "Hello";
        cls.Field2 = "ehlo";

        String serializedObj = serializeToJson(cls);
        System.out.printf("ehlo: %s\n", serializedObj);

        MyClass x = deserializeFromJson(serializedObj);
        System.out.printf("aloha: %s\n", x.Field);
        System.out.printf("aloha: %s\n", x.Field2);

        if (x.Field2 instanceof String) {
            System.out.printf("yup\n");
        }
    }

    private static void case3() {
        HashMap<String, String> map = new HashMap<>(2);
        map.put("demo", "demo");
        map.put("demo2", "demo2");

        MyClass cls = new MyClass();
        cls.Field = "Hello";
        cls.Field2 = map;

        String serializedObj = serializeToJson(cls);
        System.out.printf("ehlo: %s\n", serializedObj);

        MyClass x = deserializeFromJson(serializedObj);
        System.out.printf("aloha: %s\n", x.Field);
        System.out.printf("aloha: %s\n", x.Field2);

        if (x.Field2 instanceof HashMap) {
            System.out.printf("yup\n");
        }
    }

    public static class MyClass {
        @Expose
        @SerializedName("field")
        String Field;

        @Expose
        @SerializedName("field2")
        Object Field2;
    }

    public static class MyClassTwo {
        @Expose
        @SerializedName("fieldIsh")
        String FieldIsh;
    }

    private static String serializeToJson(MyClass myClass) {
        Gson gson = new Gson();
        return gson.toJson(myClass);
    }

    private static MyClass deserializeFromJson(String jsonString) {
        Gson gson = new Gson();
        return gson.fromJson(jsonString, MyClass.class);
    }
}

As such, I'll propose to revert our metadata to have a type Object and allow the users to send anything they want there. We'll just have to ensure they know, from the documentation, that they have to send a type that's compatible with gson.

Sample code to show what's the problem:
SchemaClass myObject = new SchemaClass<>();
SchemaClass myObject2 = new SchemaClass<>();
myObject.field = new CustomClassA();
myObject2.field = new CustomClassB();
myObject.field.fieldA = 10;
myObject2.field.fieldB = "testField";
// we cant guess what class is used as "T" so we create saving and loading token with type of object
Type type = new TypeToken<SchemaClass>() {
}.getType();
String jsonOfMyObject = new Gson().toJson(myObject, type);
String jsonOfMyObject2 = new Gson().toJson(myObject2, type);
// now deserialize it
SchemaClass myObjectAfterDeserialization = new Gson().fromJson(jsonOfMyObject, type);
SchemaClass myObject2AfterDeserialization = new Gson().fromJson(jsonOfMyObject2, type);
assertEquals(myObject2.field.fieldB, ((CustomClassB) myObject2AfterDeserialization.field).fieldB);
assertEquals(myObject.field.fieldA, ((CustomClassA) myObjectAfterDeserialization.field).fieldA);
GSON deserializes "field" as linkedMap, so to get fieldA we would need to do:
myObjectAfterDeserialization.field.get("fieldA") - if it would be a bigger object instead of primitive variable, we would receive another linkedMap with its parameters. So I think It's easier to access when we use it as string and then developers can parse it however they want


typescript is not supported anymore?

orm.d.ts looks old and when trying to use it in the project with a code from your samples - its not working. Is typescript not supported anymore?

applied some fixes locally, though it looks old to me too

The person who added & maintained typescript support has disappeared. New contributors are welcome.


TargetRid default needs to be updated

Currently source-build determines the non-portable rid of the target platform by calling RuntimeInformation.RuntimeIdentifier:
<TargetRid Condition="'$(TargetRid)' == ''">$([System.Runtime.InteropServices.RuntimeInformation]::RuntimeIdentifier)</TargetRid>

The changes in https://github.com/dotnet/runtime/pull/89598 mean this property will no longer return the rid based on Linux's /etc/os-release, but instead it will return the rid the .NET runtime was built for.
So when source-building .NET with a portable Microsoft SDK, the RuntimeIdentifier will be the portable rid of that SDK, and not the non-portable rid of the platform the build is running on.
The TargetRid should continue to default to the non-portable rid of the platform so we can identify portable from non-portable assets.
cc @MichaelSimons @elinor-fung @dsplaisted @omajid

Linking this to the change where this occurred: https://github.com/dotnet/runtime/pull/89598


Concatenate multiple variables into one variable with a multi-index (categories)

I often have to deal with datasets in this form (multiple variables of different sizes, each representing different categories, on the same physical dimension but using different names as they have different labels),
<xarray.Dataset>
Dimensions:     (wn_band1: 4, wn_band2: 6, wn_band3: 8)
Coordinates:
  * wn_band1    (wn_band1) float64 200.0 266.7 333.3 400.0
  * wn_band2    (wn_band2) float64 500.0 560.0 620.0 680.0 740.0 800.0
  * wn_band3    (wn_band3) float64 1.5e+03 1.643e+03 1.786e+03 1.929e+03 ...
Data variables:
    data_band3  (wn_band3) float64 0.7515 0.5302 0.6697 0.9621 0.01815 ...
    data_band1  (wn_band1) float64 0.3801 0.6649 0.01884 0.9407
    data_band2  (wn_band2) float64 0.8813 0.4481 0.2353 0.9681 0.1085 0.0835

where it would be more convenient to have the data re-arranged into the following form (concatenate the variables into a single variable with a multi-index with the labels of both the  categories and the physical coordinate):
<xarray.Dataset>
Dimensions:   (spectrum: 18)
Coordinates:
  * spectrum  (spectrum) MultiIndex
  - band      (spectrum) int64 1 1 1 1 2 2 2 2 2 2 3 3 3 3 3 3 3 3
  - wn        (spectrum) float64 200.0 266.7 333.3 400.0 500.0 560.0 620.0 ...
Data variables:
    data      (spectrum) float64 0.3801 0.6649 0.01884 0.9407 0.8813 0.4481 ...

The latter would allow using xarray's nice features like ds.groupby('band').mean().
Currently, the best way that I've found to transform the data is something like:
data = np.concatenate([ds.data_band1, ds.data_band2, ds.data_band3])
wn = np.concatenate([ds.wn_band1, ds.wn_band2, ds.wn_band3])
band = np.concatenate([np.repeat(1, 4), np.repeat(2, 6), np.repeat(3, 8)])

midx = pd.MultiIndex.from_arrays([band, wn], names=('band', 'wn'))
ds2 = xr.Dataset({'data': ('spectrum', data)}, coords={'spectrum': midx})

Maybe I miss a better way to do this? If I don't, it would be nice to have a convenience method for this, unless this use case is too rare to be worth it. Also not sure at all on what would be a good API such a method.

One option that gets you part way there:
arrays = [ds['data_band%d' % i].rename({'wn_band%d' % i: 'wn'}).assign_coords(band=i)
          for i in range(1, 4)]
combined = xr.concat(arrays, dim='wn')

This would still need some work (e.g., with set_index #1028) to set the MultiIndex. Ideally, maybe you could write something like combined.set_index(spectrum=['band', 'wn']) to create the new dimension and MultiIndex all at once.
It does seem like something like the key argument to pandas.concat would make sense here:
http://pandas.pydata.org/pandas-docs/stable/merging.html#more-concatenating-with-group-keys
The API is not so obvious for us, though, because we need to supply the new dimension name and levels all at once. Maybe something like xr.concat(arrays, dim={'spectrum': ['band', 'wn']} would work.

Using something like combined.set_index(spectrum=['band', 'wn']) or  xr.concat(arrays, dim={'spectrum': ['band', 'wn']}) would be nice, although it may be a bit weird to use the key spectrum to rename the wn dimension here.
For now, I'm fine with setting the MultIndex with the more explicit - though more verbose - combined.set_index(wn=['band', 'wn']).rename({'wn': 'spectrum', 'data_band1': 'data'})


Add custom kryo serializer for GrailsFlashScope

From martin.grotzke on August 05, 2011 09:41:37
This need has been identified on the mailing list:
http://groups.google.com/group/memcached-session-manager/browse_thread/thread/8a81e7b1fb1c2230

There's now an additional custom kryo serializer that can be configured as customConverter: de.javakaffee.web.msm.serializer/kryo.GrailsFlashScopeRegistration
Original issue: http://code.google.com/p/memcached-session-manager/issues/detail?id=107

From martin.grotzke on December 26, 2011 15:42:37
(No comment was entered for this change.)
Labels: -Milestone-1.5.2 Milestone-1.6.0


[cosmos] The new Bulk API does not retry when Cosmos DB throttles

Package Name:
azure/cosmos

Package Version:
3.9.0

Operating system:
macos

[ ] nodejs

version: 14.4.0

[ ] typescript

version: 3.9.7

Describe the bug
When using the new Bulk API and in case the database throttle, there are no retries and the error is bubbled up to the user code immediately.
Given that the purpose of the Bulk API is to do many operations, the throttling might be a common case and it would be very useful if the API would respect the retry policy similar to how the other SDK APIs does.
To Reproduce
Steps to reproduce the behavior:

Clone the test app from https://github.com/vjrantal/cosmos-typescript-bulk-import-throughput-optimizer/tree/wip (notice the wip branch)
Setup according to the instructions at https://github.com/vjrantal/cosmos-typescript-bulk-import-throughput-optimizer/tree/wip#setup
Observe the output that may look something like below:

BulkOperations importing 1000 items with Upsert took 7.21 seconds
Average throughput 138.73 per second
Consumed Request Units 3325.33
Item count in Cosmos DB is 6599
Failed to import 398 items

The test app prints how many failures occur and in above case 398 / 1000 failed. If you further observe the output, it is likely that all failures were due to 429 returned from the server.
Expected behavior
The Bulk API respect the retry policy as defined by the SDK user.

@zfoster Will be looking into this issue. As of now this is by design. We intentionally kept bulk simple for the initial release.

Hi,
are there any plans to implement retry also for bulk operations?

@kushagraThapar If this is a valid feature request, please add the feature-request label, remove the question label and move it to the Backlog milestone. Otherwise, please consider closing it.

@ramya-rao-a - Done. Thanks for notifying!

Hey @vjrantal ,
We currently offer retrials for bulk requests. Would you consider migrating to the latest version as a potential option?

@topshot99 If the latest version of the SDK solves this issue, then I think it is valid to close.
Could you add here a link to the documentation (or source code) of the new retry behavior as reference?

@vjrantal sure but there is one more answer which i want form you :
Additionally, I've observed that you're considering non-201 status codes as errors. Could this be a potential factor contributing to the issue?
Can you answer this?

Additionally, I've observed that you're considering non-201 status codes as errors. Could this be a potential factor contributing to the issue?

At Aug 20, 2020 when I opened this issue, the behavior was that if the Cosmos DB server throttles, there are no retries and the error is immediately returned to the SDK user. What I would expect to happen is that the SDK internally retries according to a policy with pre-defined (but configurable) defaults so that retry is handled "inside" the SDK before returning any error to the user of the SDK.
I think it is correct for me as SDK user to consider non-201 status codes as errors, because those are the ones that the SDK "bubbles up" to the user of the SDK and needs to be handled at that level.


prevent assertion TypeError in tensorflow 0.7

In tensorflow 0.7, cannot treat tf.Tensor as bool. See: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/framework/ops.py#L444

The issue is that asserting output_tensors[0] when it is type tf.Tensor (tensorflow backend) will raise
TypeError("Using a `tf.Tensor` as a Python `bool` is not allowed. Use `if t is not None:` instead of `if t:` to test if a tensor is defined, and use the logical TensorFlow ops to test the value of a tensor.")

I've updated the code upstream, which might remove the need for this PR. Please either update the PR to fix the merge conflicts, or close it.


testing factory issue

I forked forem and run commands above but I receive error with factory_girl:
```/home/rege/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.1.0/lib/active_support/dependencies.rb:240:in `require': no such file to load -- factory_girl (LoadError)
http://pastie.org/3150900

What was the exact command you used to run this?

and
```bundle exec rspec spec

What version of factory_girl_rails do you have installed? Mine's at 1.2.0.

gem list gives me factory_girl (2.3.2, 2.1.0) factory_girl_rails (1.4.0, 1.2.0)

ok I removed factory_girl 2.3.2 and factory_girl_rails 1.4.0 and 130 examples pass. :)

Ok, looks like this could be because of the factory girl bump. I'll investigate a little later today.
On 09/01/2012, at 9:33<EMAIL_ADDRESS>wrote:

ok I removed factory_girl 2.3.2 and factory_girl_rails 1.4.0 and 130 examples pass. :)

Reply to this email directly or view it on GitHub:
https://github.com/radar/forem/issues/123#issuecomment-3405248


Replace type with isinstance

Object type comparisons should always use isinstance() instead of comparing types directly:

# Correct:
if isinstance(obj, int):

# Wrong:
if type(obj) is type(1):

https://peps.python.org/pep-0008/#programming-recommendations
https://wemake-python-styleguide.readthedocs.io/en/latest/pages/usage/violations/refactoring.html#wemake_python_styleguide.violations.refactoring.TypeCompareViolation

@yegor256 take a look please

@blablatdinov thanks!


[ZEPPELIN-2821] Fix Missing import

What is this PR for?
The python interpreter has a bug when trying to render matplotlib images from the z.show() function.  Line 139 of python/src/main/resources/python/zeppelin_python.py references un-imported package base64.  import base64 was added to the file to prevent this error in the future.
What type of PR is it?
Bug Fix
Todos

[x] - Add missing base64 module to python/src/main/resources/python/zeppelin_python.py

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2821

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]

How should this be tested?
Display a matplotlib image with zeppelin:
import matplotlib.pyplot as plt
plt.plot([1,2,3,4])
z.show(plt)

Questions:

Does the licenses files need update?
no
Is there breaking changes for older versions?
no
Does this needs documentation?
no

could you please setup travis CI to run tests
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration

Thanks @Sdedelbrock for the fix!

yes, let's get CI to run though :)

I've force pushed the PR twice to re-trigger the build, and one of the jobs consistently times out.  I have disabled test concurrency to no avail.  I have manually re-run the (failed) test with success, however Jenkins still shows a failure.
Please let me know how you would like me to proceed.

You can close/open this PR to trigger Jenkins. Then Jenkins will check last build result and update this PR build status. Or just leaving message would be okay too, like you just did.
I checked the build result manually https://travis-ci.org/Sdedelbrock/zeppelin/builds/261941334.
LGTM and merge to master and branch-0.7 if no further comments.

it.....
finally......
happened!
😄

awesome!


Improve link autodetection

Currently for a link to be detected as such it has to start with http(s):// or www., this is too simplistic. Please add TLDs to the link detection function.

The full list of TLDs is here: https://data.iana.org/TLD/tlds-alpha-by-domain.txt
It contains lots of really obscure ones, so I'm not sure that including all of them is a good idea (it's 10K of text). I can provide a shorter one, if you want.

@Leonya Can you provide examples of autolinks you'd like to parse? I think I tried to reverse-engineer the github markdown autolinks behaviour at the time.

Sure:
t.co/foo
jetbrains.team/abc
yandex.ru

Basically anything that is a hostname.known-tld should be turned into a link.

Doesn't it bother you that github does not linkininze such strings? I can surely do such change, but I suppose it's incorrect to call that GFM anymore

No, I believe it's fine. It's not the kind of extension that goes against the spirit of GFM.

I've introduced SFM (space flavoured markdown) with proposed changes. A couple of coutry codes were still removed (e.g. .sh) because bash files occur in text quite frequently.
Will update MPP branch a little bit later.

These two commits also need to be synced with the kotlin-js-clean branch: f4c743257f242efdca2bfc5559f8327cd73a02ec, 31647e1ae9cfb469dbb78f050643ee73a81f5530

Force pushed kotlin-js-clean


Hovering over the text, shows the entire text.

With the default size, if you copy something with long text. It would be cut-off. User has to increase the size of the window to see the entire text. It would be nice if the user is able to see the entire text by just hovering over it.

That could be useful, agreed.


[admin][broker] Fix force delete subscription not working

Fixes https://github.com/apache/pulsar/issues/22404
Motivation
Fix force delete subscription not working on persistent topics.
Modifications

Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

I still have the same issue on pulsar 3.3.1 on apachepulsar/pulsar-all:3.3.1


Implement core::fmt::Step for UInt

Closes #29.

This looks great, thanks a lot for the contribution.

We should have tests to ensure both the arbitrary int overflowing as well as the underlying type overflowing. I wrote them up (and they pass just fine):

#[cfg(feature = "step_trait")]
#[test]
fn forward_out_of_range() {
    // In range
    assert_eq!(Some(u7::new(121)), Step::forward_checked(u7::new(120), 1));
    assert_eq!(Some(u7::new(127)), Step::forward_checked(u7::new(120), 7));

    // Out of range
    assert_eq!(None, Step::forward_checked(u7::new(120), 8));

    // Out of range for the underlying type
    assert_eq!(None, Step::forward_checked(u7::new(120), 140));
}

#[cfg(feature = "step_trait")]
#[test]
fn backward_out_of_range() {
    // In range
    assert_eq!(Some(u7::new(1)), Step::backward_checked(u7::new(10), 9));
    assert_eq!(Some(u7::new(0)), Step::backward_checked(u7::new(10), 10));

    // Out of range
    assert_eq!(None, Step::backward_checked(u7::new(10), 11));
}

Github's test runner won't currently test this, as the feature needs to be enabled. We can add that:

In .github/workflows, make a copy of test-const.yml and swap out the feature.
Once that is added and uploaded, Github should automatically run the test suite with this feature enabled.

Oh! And:

Add the new feature to the CHANGELOG.md, putting it under a new section 1.2.7

thanks for the guidance! please let me know if there's anything else I'm missing

Thanks a lot for your contribution!


SCST  strategies

Can you tell us about training different SCST strategies? I don't know how to operate it

The problem has been solved, it was my mistake, thank you very much


⚠ Bofrost.es has degraded performance

In a5a310c, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1531 ms

Resolved: Bofrost.es performance has improved in 712943a after 15 minutes.


dependency_mode option not visible

The --dependency_mode option is not displayed when running java -jar compiler.jar --help.
See https://github.com/google/closure-compiler/blob/v20160315/src/com/google/javascript/jscomp/CommandLineRunner.java#L615

Yeah - I didn't find out about that change until much later as well. Caught me off guard. The flag is still there, just not documented from the command line. I'm going to audit those flags and make sure the appropriate ones are still documented.

And the --define option is also not visible.

There are a lot of flags not visible. I'm going to audit them all.

thanks

Closed by #1695