Deprecate --watch

@boneskull commented on Jan 30

IMO "watch" should be killed. There are other tools which do this sort of thing much better.

@dasilvacontin commented on Jan 31

+1 to kill watch. I don't see the point of replicating the functionality of a watcher inside the project, when any watcher tool will do the job.

Creating a separate issue for this, so we can close the unrelated #871

yes please

Agreed. I'd really like see Mocha v3 broken down into smaller modules with a lean core.

It'd be nice to see some suggestions on an alternative, then; all of the :+1:'ers obviously know of a better replacement, but I, personally, do not. (I suspect the same is true of plenty of users. :P)

It'd be nice to see some suggestions on an alternative

https://github.com/gruntjs/grunt-contrib-watch
https://github.com/floatdrop/gulp-watch
I definitely still use --watch for some projects, as not all need a task runner. But its absence from the core wouldn't be missed if a plugin system exists. Or if everyone just uses a task runner.

Not everyone use grunt/gulp tasks for that sort of thing, some ppl are like to use npm scripts for some of the tasks.
This is also pretty useful with compilers flag. Yeah, you can use something like:
forever start -c "mocha" /path. But it seems much more complicated then it should be.

"do one thing and do it well"
It runs tests well.  It doesn't watch files well.  There are better solutions.  I understand it is handy for some people, but it's out of scope.

What is the alternative?

read above

Would you mind reading my comment too please?

I did.  But whether or not you use a task runner, forever, fswatch or whatever is your choice.

I'm not sure if forever start -c "mocha /path" /path would work, didn't start for me, not sure even if it should.
If you removing this feature, would you mind providing the other clear path to do it?

gaze is probably going to be your best bet

if you don't need something node-based, gaze is a wrapper around the excellent fswatch

many IDEs and text editors also have this functionality built-in

fswatch couldn't be added as node dependency, gaze doesn't have a CLI api. Including prerequisite for projects to use some IDE seems...
Okay, in other words, i either need to switch my projects on some task manager or i can still use mocha but only through programmatic API with some watcher.
That is a bad move in my opinion.

re: fswatch "if you don't need something node-based" ... it's not a node package.  apt-get install fswatch or brew install fswatch or whathaveyou.
I'm not sure why I need to do this for you, but here's a CLI for gaze.

re: fswatch "if you don't need something node-based" ... it's not a node package. apt-get install fswatch or brew install fswatch or whathaveyou.

Yes, that is why i said "fswatch couldn't be added as node dependency", it is like asking people to install debian package to run mocha.

here's a CLI for gaze.

That is the same thing as forever start -c "mocha /path" /path, see above as they say :-), this is less cool and you couldn't put it in mocha.opts, if you use compiler flag, things get even worse. But okay, that would do.

I'm not sure why I need to do this for you

Usually, when maintainers of some package, remove pre-existing functionality, they provide an explanation of why they do it and provide an alternative way to achieve the goal.
Explanation is the necessity, alternative way, is a common courtesy, sign of mutual respect, not a favor.
In other words you don't "need" to do anything and i'm sorry i "need" to write this.

Yes, that is why i said "fswatch couldn't be added as node dependency", it is like asking people to install debian package to run mocha.

Yes.  Though, gaze is a wrapper around fswatch.  When you install it, it compiles fswatch for you.  There are many, many NodeJS wrappers around non-NodeJS projects.  And some that just expect the executable to be there.  For instance, how would you run npm without git installed?  So, in my mind, not a huge deal, and a viable alternative.

Explanation is the necessity, alternative way, is a common courtesy, sign of mutual respect, not a favor.

When support is dropped the responsible thing would be to explain a viable alternative--and we will!
My comment was out of frustration; obviously there are viable alternatives, and I know you know that.  I felt I had to "google it" for you.  This was not meant to be disrespectful and I apologize if it came across that way.
I use grunt-contrib-watch if I need a watcher in all of my projects.  Most of the time I don't, because my IDE does it for me.  This solution works for me.
We'll provide well-documented alternatives when the time comes, so thank you for reminding me.  In fact, it may be worthwhile to add a "pending deprecation" notice when --watch is used.

It wouldn't be necessary to ‘google it’ for us, except that's precisely what I asked you to do. @markelog was just clarifying my request, I believe.
As for why I asked: I'm not curious about what the solutions are (I'm not a beginner. I do, in fact, know how to use a search engine.); I'm asking what Mocha's response to that question will be, when this is deprecated. I'm sorry I didn't word that better.
If gaze-cli will be the suggested go-to for confused users (read again, because apparently I need to specify this: not me.), I still think @markelog has a valid concern, although it's a rather small one in the grand scheme of things: mocha --watch widget is substantially D.R.Y.'er and more approachable than gaze "mocha widget" widget, or so on and so forth.
Personally, I don't think that's a blocking problem re: deprecating this. I'm all for doing so. ¯_(ツ)_/¯

@ELLIOTTCABLE @markelog Maybe this.

Since gaze is now apparently abandonware, and most of the large projects (Gulp, browserify, Karma) have switched over to Chokidar, may I suggest chokidar-cli?
In addition to the wider support, it solves the one concern I had above, by providing {path} substitution, letting us D.R.Y. up the Mocha command:
chokidar 'tests/*.js' -c 'mocha "{path}"'

I use testem for this.

@ELLIOTTCABLE Yes, chokidar is the way to go

When using mocha --watch, the first test run takes ~20 seconds, I presume while everything compiles and loads up.  After that, file changes trigger test reruns in <1 sec, which is great.
However, mocha --watch gets my CPUs spiking.  Does it do that for anyone else?  It's a bummer to leave that going overnight.
Chokidar doesn't do that, but it also requires the full 20 second compile time upon every file change :(
Is there a best-of-both-worlds solution?

@sosaucily Presumably, writing a JavaScript file that watches files with the Chokidar API and invokes Mocha programmatically, instead of using the CLI invocation, would be faster.

Would be awsome if we could diagnose the CPU spikes.  Any help would be appreciated!

At any rate, chokidar > gaze

-1 for this. I like every bit of the --watch how easy it is to setup and how it fits within my package.json/scripts section. Please don't kill it!!!

@padcom Mocha's main responsibility isn't watching files.  We frequently get many issues around the watch functionality, because it doesn't work how people think it will, or has bugs in edge cases, or isn't working cross-platform.  To that end, it should be removed from "core".  The functionality is helpful, but it's better handled by a third-party tool.
That said, there are certain use cases that likely won't work "out-of-the-box" with a third-party tool.  A separate module which would wrap something like chokidar is in order.  mowatch is/was an experimental tool to provide this outside of Mocha's core.  It doesn't use chokidar, but it should.

Moreover, I find chokidar to be annoying (generates npm warnings on every npm install due to npm not supporting multiple platforms). So I would always prefer watcher to be a separate platform-specific tool rather than integrated into a test runner.

All the proposed alternatives here seem to ignore the main point: Mocha's --watch is so useful because the Node process running the tests is kept alive.
If you have a very small project with very few dependencies and you're not doing transpilation, then you don't even need a Node tool to watch files and run a shell command. That's already invented and works well: http://entrproject.org.
Those of us who have somewhat bigger projects, using Babel transpilation, will need to find an alternative. A real one. That is, one that keeps Mocha running and doesn't have to respawn a Node process with everything that entails.

+1 on keeping --watch for the earlier mentioned reasons. Preferably, options like compilers and watch should become part of the Mocha library itself, as it now introduces unnecessary complexity on wrapper tools that want to support these same features. See this thread.

I do agree with @padcom (that argument is super important)

-1 for this. I like every bit of the --watch how easy it is to setup and how it fits within my package.json/scripts section. Please don't kill it!!!

Couldn't agree more with @ScottFreeCode as well. Until we find an good solution allowing to run mocha more than once especially with transpiler, we should keep --watch
I am repeating myself but consider this.
watch-run -i -p 'src/**/*' npm test:mocha

It works just fine, however it takes more and more time to execute as the code base grows. Reason? Using transpiler.
 "test:mocha": "mocha ./internals/test.setup.js ./src/**/*.spec.js* --require babel-core/register",

Every time file changes mocha requires babel-register. That means eating away time to transpile everything, whereas re-running mocha tests with mocha --watch take a bit of initial time to kick in but once up and running it is super fast.

Interesting bit of trivia (or, perhaps, an example of prioritization and things that go slow): in researching another issue, I discovered that --watch has been unpreferred since back in 2013: https://github.com/mochajs/mocha/issues/909#issuecomment-20311034

I've read /bin/_mocha.js and got wondered a little about --watch.
var watchFiles = utils.files(cwd, [ 'js' ].concat(program.watchExtensions));
When we execute mocha-cli with --watch at workspace, the watchFiles contains whole files under workspace.  So I tried edit _mocha.js manually like this and "Test-Runs-Twice Problem" seemed to be suppressed.
for example…
_mocha.js:

  //var watchFiles = utils.files(cwd, [ 'js' ].concat(program.watchExtensions));
  var ext = ['js'].concat(program.watchExtensions);
  var watchFiles = [];
  watchFiles = program.args.map(function(t) {
    return utils.files(resolve(t), ext)[0];
  });
  watchFiles = watchFiles.concat(utils.files(resolve('my/source/code/directory/'), ext));

command line:
 mocha -S -w  ./test/**/*

It might be a clue to resolve some problems about --watch.

I'm going to close this since it's clear that enough people use --watch that it'll be extremely disruptive.
It really needs an overhaul though.


Explore bringing GitLens "Git Commands" into built-in Git

Git Commands

Provides guided (step-by-step) access to common Git commands and their flags

This feature IMO should be moved into VS Code as there is duplication with VS Code commands and it provides a nice unified way of dealing with the growing list of Git commands, of which are hard to discover and deal with different options for. By moving this into VS Code directly, the UX of this feature could be improved as well, to provide a more seamless experience for navigating commands. For example, it would be great if this experience was shown immediately upon typing git  (with the space) in the Command Palette. Also many of the hoops and hacks that are needed to provide this experience should be largely eliminated as well (although many could be addressed through an expanded quick pick api).
Including this feature would also eliminate many duplicate git commands between GitLens and VS Code. And also since this feature is on-demand, there is no perf overhead for VS Code to provide this.

@eamodio Let's talk early June on how to advance this.


Syntax highlighting breaks in messages pan after error occurs.

SQL Operations Studio Version: sqlops 0.25.4 (8095643ed4421fbe5d713883b06bdac07a0dd01d, 2018-01-13T00:10:17.197Z)
OS Version: Windows_NT x64 10.0.15063

We have a stored procedure that is used to drive a data synchronisation process. It executes a certain stored procedure with different parameters. The procedure being called, could be called 10-80 times depending on the data to synchronise.
Both procedures print progress messages using RAISERROR with severity 10.
SET @msg = CONVERT(varchar(20),GETDATE(),120) + '' Captured update/insert data'';
RAISERROR(@msg, 10, 1) WITH NOWAIT;

In SQL Management Studio, this produces a list of progress messages. If there are any errors, the errors are highlighted red, but all other messages have the standard black on white formatting.
In SQL Operation Studio, when an error occurs, the error and each subsequent progress message is highlighted as an error (see attached)
Steps to Reproduce:

Execute long running procedure that issues messages via RAISERROR('msg',10,1) WITH NOWAIT
Introduce error that interrupts processing

Cheers
Phil

Closing out older issues.  I know we did some updates to the message window a while back (after this bug was filed).  It is possible the bug is resolved on the latest build.  Please let us know if this issue is still impacting you.  Thanks!


Solve Firecracker reboot issues

Problem: If the frontend or a user send the request to reboot a Firecracker instance, it stops but doesn't start again.
Solution: Change method to restart it just stopping the process, cleaning the firecracker run files and starting it again.

The lifecyle of the Execution in the different use case are not clear to me. Is the tear down ever called for Firecracker VM when it's running inside systemd?

The lifecyle of the Execution in the different use case are not clear to me. Is the tear down ever called for Firecracker VM when it's running inside systemd?

Yes, previously to the PR, the Firecracker VM was removed completely on a service stop or restart. Now is only stopping the process and running it again. Only in the case that the instance is removed completely from the system should do the teardown process.


Delete Item / Remove Item from assortment

The Website Status of an Item is somehow confusing for me.
Available / not available is clear.
But does deleted mean it will be deleted or removed from assortment (aus Sortiment genommen)?
In my opinion 4 Statuses would be better

available
not available
defective (so users know it will be repaired or they can donate a "new" one)
deleted (not visible on Website anymore)

At the moment deleted means that it does not exist on the website anymore. We need another status for defective, thats right. I think we should do:

Items marked as deleted should not be editable (since they do not exist on the website)
The state deleted should not be selectable when editing an item (since this can be achieved by pressing the delete button)
Add a new status for defective and sync that with the correct status on the website


Add command to svcat to abandon instances

Sometimes a service instance can become "stuck", and we want to just give up on it and make it go away in Kubernetes so that we don't see it anymore.
There are a couple ways this could happen, and I'm happy to go into more detail if whoever picks up this issue needs it. The short answer is that it can happen due to bugs, misbehaved brokers, messed up developer environments, or cases where you want to disconnect k8s from a service provisioned by the broker, even though it's still being used elsewhere (so the broker isn't letting you delete it).
This feature is to add the --abandon boolean flag to the svcat unbind and svcat deprovision commands. When that flag is present, before deleting the instance, the cli will first confirm the action and then remove ALL finalizers from the service instance so that it is deleted immediately, without giving service catalog a chance to try to delete it with the broker.
It also adds an optional -y flag that skips the interactive prompt/confirmation.
$ svcat unbind --abandon INSTANCE_NAME
This action is not reversible and may cause you to be charged for the broker resources that are abandoned.
Are you sure? [y|N]

deleted BINDING_NAME(S)
deleted INSTANCE_NAME

$ svcat deprovision --abandon INSTANCE_NAME
This action is not reversible and may cause you to be charged for the broker resources that are abandoned.
Are you sure? [y|N]

deleted INSTANCE_NAME

$ svcat help deprovision
Deletes an instance of a service

Usage:
  svcat deprovision NAME [flags]

Examples:

  svcat deprovision wordpress-mysql-instance

Flags:
      --abandon bool    Forcefully and immediately delete the resource from Service Catalog ONLY, potentially abandoning any broker resources that you may continue to be charged for.
      --yes,-y bool         Automatic yes to prompts. Assume "yes" as answer to all prompts and run non-interactively.

See the original issue for context and the discussion that lead up to this issue, #1723
I wrote an example plugin that does this for pods that you can use as a reference.
Add documentation for the feature to the cli page on our website

the cli will first confirm the action and then remove ALL finalizers from the service instance so that it is deleted immediately, without giving service catalog a chance to try to delete it with the broker.

AFAIK DELETE request doesn't have a request body. If you DELETE first, and then send PUT/PATCH, then in between those two requests Service Catalog will get a chance to deprovision (especially given the queue/cache)? So the correct order would probably be to remove finalizer first, and only after that send a DELETE?
Also, removing ALL finalizers sounds wrong to me - svcat should only remove kubernetes/service-catalog finalizer, other custom finalizers should be managed by appropriate controllers, since we don't know their purpose and side effects.

Similar to the notion of exporting an instance here https://github.com/kubernetes-incubator/service-catalog/issues/2250 just a different use case.

Similar to the notion of exporting an instance here https://github.com/kubernetes-incubator/service-catalog/issues/2250 just a different use case for "don't actually attempt deprovisioning".

The abandon should probably also support Bindings and Brokers.  See issue https://github.com/kubernetes-incubator/service-catalog/issues/2466

@carolynvs I'd like to work on this issue
/assign


error in building hand_tracking in windows

C:/users/loay sharaky/_bazel_loay sharaky/hr7sucjp/external/org_tensorflow/tensorflow/lite/kernels/BUILD:634:11: C++ compilation of rule '@org_tensorflow//tensorflow/lite/kernels:builtin_op_kernels' failed (Exit 2): cl.exe failed: error executing command C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.16.27023/bin/HostX64/x64/cl.exe /nologo /DCOMPILER_MSVC /DNOMINMAX /D_WIN32_WINNT=0x0601 /D_CRT_SECURE_NO_DEPRECATE ... (remaining 66 argument(s) skipped)
cl : Command line warning D9002 : ignoring unknown option '-O3'
external/org_tensorflow/tensorflow/lite/kernels/elementwise.cc(82): fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'msc1.cpp', line 1518)
To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
Internal Compiler Error in C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\cl.exe.  You will be prompted to send an error report to Microsoft later.
INTERNAL COMPILER ERROR in 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\cl.exe'
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
Target //mediapipe/examples/desktop/hand_tracking:hand_tracking_cpu failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 6.958s, Critical Path: 5.56s
INFO: 28 processes: 28 internal.
FAILED: Build did NOT complete successfully

https://docs.microsoft.com/en-us/cpp/error-messages/compiler-errors-1/fatal-error-c1001?view=msvc-160 suggests that you can often fix an optimization problem by removing one or more optimization options.
You may remove -c opt from the bazel build command to remove the optimization.

Tensorflow requires Visual C++ 2019  and Build Tools 2019:https://www.tensorflow.org/install/source_windows. My guess is "ensorflow/lite/kernels:builtin_op_kernels" also requires this.


Details on 8th death

Source is: https://www.cbc.ca/news/canada/saskatchewan/nelda-maurice-northern-sask-covid-1.5583540

Thank you for your contribution! From what I know so far, this fatality would be considered the 9th and isn't officially reported yet (as the 8th is reported as in the 50s, and this is 64) - I have a preliminary entry on the Google Sheets spreadsheet, but I will adapt some of the formatting to match yours (primarily using '/' to separate symptoms) to push as soon as it's officially announced. Thank you again - it's much appreciated.


Profile with/out attn_pdrop in gpt2, send to jax devs

I observe a massive speed hit when using dropout on TPU:
gpt2-small throughput (v3-32)

no attention dropout: 0.3654
threefry_partitionable dropout: 0.5499
with unsafe_rbg, no tpu initflag: 3.92 (!!!)

Jax devs have asked for a repro and/or profile.

[ ] profile
[ ] repro (ideally)

Here's the configuration that I use for profiling:

gpt2_small_fast.yaml, including changes of:

attn_pdrop=0.1
use_biases=False

FLAG=unsafe_rbg (here)

What is repro? Giving them a branch to reproduce the result?

well ideally it would be a minimized repro, which is kind of a bunch of work. let's see if they'll settle for the profile? (They indicated they might?)

Maybe I misunderstood, but the impact of unsafe_rbg seems to be against with the hypothesis. I observed that, after enabling unsafe_rbg, the training throughput gets a massive hit and the maximum batch size I could set also decreased to below 4096. I thought unsafe_rbg is supposed to help "reduce the size of the Tensorflow graph and compilation time".
I captured the observation here: https://github.com/stanford-crfm/levanter/issues/226

I do observe the hit on training throughput when tuning attn_pdrop from 0.1 to 0:

(the earlier comment was stated wrongly and has been removed)
The results are aligned with the observation stated at the beginning of this issue: after adding attention dropout, the training throughput decreases from 770K tokens per second to 500K.

I made a writeup with my experiment results and profiling data: https://docs.google.com/document/d/1C6M8IJmOFFtG_KmAv2yxkVmSuryFbPUmfFccth1LUo4/edit
@dlwh If this looks good to you, we can share it with Jax people.

lgtm, yeah, let's send it over. Hopefully they can figure it out without us having to minimize


[0.9.5]: High Memory consumption

Hi we have upgraded Influx to 0.9.5 but this behavior can be seen in 0.9.3/0.9.4
We have a database of 8GB size on a server with 4 CPUs and 12GB of memory
After 5 minutes, InfluxDB take 11GB of memory.
After 7 minutes server is swapping and oom killer start doing it's job.
After 9 minutes server is down.
I would like to know if there are some parameters that tweak how InfluxDB should consume memory ?

How many tag values do you have? I've seen 100Gb memory consumption before oom on a smaller database, where tag value contained hash or timestamp.

Hi
I have same situation, upgraded influx 0.9.4 to <IP_ADDRESS>-1, and use same data, wal, ... data files. Works, comes up but consumes high volumes of RAM (RES and VIRT). I have a server with 8CPUs and 6GB used exclusively for InfluxDB, don't use cluster configuration.
Using tsm1 engine, when startup influx appers this lines into log:
2015/11/27 12:20:36 InfluxDB starting, version <IP_ADDRESS>, branch 0.9.5, commit 9eab56311373ee6f788ae5dfc87e2240038f0eb4, built 2015-11-25T23:01:58+0000
2015/11/27 12:20:36 Go version go1.4.2, GOMAXPROCS set to 8
2015/11/27 12:20:36 Using configuration at: /etc/influxdb/influxdb.conf
[metastore] 2015/11/27 12:20:36 Using data dir: /var/opt/influxdb/meta
[metastore] 2015/11/27 12:20:36 Skipping cluster join: already member of cluster: nodeId=1 raftEnabled=true peers=[bebd8tse01.ods:8088]
[metastore] 2015/11/27 12:20:36 Node at bebd8tse01.ods:8088 [Follower]
[metastore] 2015/11/27 12:20:37 Node at bebd8tse01.ods:8088 [Leader]. peers=[bebd8tse01.ods:8088]
[metastore] 2015/11/27 12:20:37 spun up monitoring for 1
[store] 2015/11/27 12:20:37 Using data dir: /var/opt/influxdb/data
[metastore] 2015/11/27 12:20:37 Updated node id=1 hostname=bebd8tse01.ods:8088
[wal] 2015/11/27 12:20:37 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 52428800 partition size threshold
[wal] 2015/11/27 12:20:37 WAL writing to /var/opt/influxdb/wal/internal_metrics/internal/100
[wal] 2015/11/27 12:20:38 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 52428800 partition size threshold
[wal] 2015/11/27 12:20:38 WAL writing to /var/opt/influxdb/wal/internal_metrics/internal/105
[wal] 2015/11/27 12:20:38 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 52428800 partition size threshold
[wal] 2015/11/27 12:20:38 WAL writing to /var/opt/influxdb/wal/internal_metrics/internal/111
[wal] 2015/11/27 12:20:38 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 52428800 partition size threshold

Hi again
I have a tags for environment, hostname and servicename. Is a problem?
Thanks

We have about 6 TAG values
a piece of what is sent to the Influx
access_log,IPADDR=<IP_ADDRESS>,SITE=paris1.speedtest.orange.fr,FAMILYSITE=orange.fr,proxyname=routeur.touzeau.biz SIZE=4700,ZDATE=1438722000,RQS=10<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,SITE=speedtest.neotelecoms.com,FAMILYSITE=neotelecoms.com,proxyname=routeur.touzeau.biz SIZE=4600,ZDATE=1438722000,RQS=10<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:47:80:24,SITE=speedtest.net,FAMILYSITE=speedtest.net,proxyname=routeur.touzeau.biz SIZE=1103,ZDATE=1438722000,RQS=2<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:47:80:24,SITE=www.speedtest.net,FAMILYSITE=speedtest.net,proxyname=routeur.touzeau.biz SIZE=134669,ZDATE=1438722000,RQS=2<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:47:80:24,SITE=speedtest.proceau.net,FAMILYSITE=proceau.net,proxyname=routeur.touzeau.biz SIZE=10967892,ZDATE=1438722000,RQS=24<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:47:80:24,SITE=massy.testdebit.info,FAMILYSITE=testdebit.info,proxyname=routeur.touzeau.biz SIZE=4900,ZDATE=1438722000,RQS=10<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:47:80:24,SITE=paris1.speedtest.orange.fr,FAMILYSITE=orange.fr,proxyname=routeur.touzeau.biz SIZE=4700,ZDATE=1438722000,RQS=10<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:47:80:24,SITE=speedtest.neotelecoms.com,FAMILYSITE=neotelecoms.com,proxyname=routeur.touzeau.biz SIZE=4600,ZDATE=1438722000,RQS=10<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:5b:40:37,SITE=www.artica.fr,FAMILYSITE=artica.fr,proxyname=routeur.touzeau.biz SIZE=1324,ZDATE=1438722000,RQS=4<PHONE_NUMBER>
access_log,USERID=iphone-david,IPADDR=<IP_ADDRESS>,MAC=60:03:08:7b:7c:fd,SITE=ui.skype.com,FAMILYSITE=skype.com,proxyname=routeur.touzeau.biz SIZE=757,ZDATE=1438722000,RQS=1<PHONE_NUMBER>
access_log,USERID=iphone-david,IPADDR=<IP_ADDRESS>,MAC=60:03:08:7b:7c:fd,SITE=<IP_ADDRESS>,FAMILYSITE=<IP_ADDRESS>,proxyname=routeur.touzeau.biz SIZE=3903,ZDATE=1438722000,RQS=1<PHONE_NUMBER>
access_log,USERID=iphone-david,IPADDR=<IP_ADDRESS>,MAC=60:03:08:7b:7c:fd,SITE=<IP_ADDRESS>,FAMILYSITE=<IP_ADDRESS>,proxyname=routeur.touzeau.biz SIZE=9939,ZDATE=1438722000,RQS=1<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:bd:88:3b,SITE=<IP_ADDRESS>,FAMILYSITE=<IP_ADDRESS>,proxyname=routeur.touzeau.biz SIZE=3112,ZDATE=1438722000,RQS=1<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,SITE=localhost.company.tld,FAMILYSITE=company.tld,proxyname=articaad2.company.tld SIZE=37800,ZDATE=1438722000,RQS=3<PHONE_NUMBER>
access_log,IPADDR=<IP_ADDRESS>,MAC=00:0c:29:3d:7f:36,SITE=articatech.net,FAMILYSITE=articatech.net,proxyname=routeur.touzeau.biz SIZE=30828,ZDATE=1438722000,RQS=3<PHONE_NUMBER>
access_log,USERID=iphonealex,IPADDR=<IP_ADDRESS>,MAC=d8:9e:3f:34:2d:8d,SITE=captive.apple.com,FAMILYSITE=apple.com,proxyname=routeur.touzeau.biz SIZE=1300,ZDATE=1438722000,RQS=4<PHONE_NUMBER>
access_log,USERID=iphone-david,IPADDR=<IP_ADDRESS>,MAC=60:03:08:7b:7c:fd,SITE=<IP_ADDRESS>,FAMILYSITE=<IP_ADDRESS>,proxyname=routeur.touzeau.biz SIZE=23754,ZDATE=1438722000,RQS=6<PHONE_NUMBER>
access_log,USERID=ipadalex,IPADDR=<IP_ADDRESS>,MAC=28:6a:ba:59:f3:f9,SITE=<IP_ADDRESS>,FAMILYSITE=<IP_ADDRESS>,proxyname=routeur.touzeau.biz SIZE=3305,ZDATE=1438722000,RQS=1<PHONE_NUMBER>
access_log,USERID=ipadalex,IPADDR=<IP_ADDRESS>,MAC=28:6a:ba:59:f3:f9,SITE=<IP_ADDRESS>,FAMILYSITE=<IP_ADDRESS>,proxyname=routeur.touzeau.biz SIZE=9069,ZDATE=1438722000,RQS=2<PHONE_NUMBER>
access_log,USERID=ipadalex,IPADDR=<IP_ADDRESS>,MAC=28:6a:ba:59:f3:f9,SITE=<IP_ADDRESS>,FAMILYSITE=<IP_ADDRESS>,proxyname=routeur.touzeau.biz SIZE=4464,ZDATE=1438722000,RQS=1<PHONE_NUMBER>

@dtouzeau Series cardinality is the primary driver of RAM usage for InfluxDB. You have six tags, but each tag has many possible values. Tag cardinality is the unique combinations of all tag keys AND values. Your write sample contains 20 points that belong to 20 different series. Your series cardinality is likely very very high.
What are the results of the following command line query?
influx -database <db_name> -execute 'show tag values with key in (IPADDR, SITE, FAMILYSITE, MAC, USERID, proxyname)' | wc -l

Result is 36 929 on a 3GB database and influx take about 1.8GB memory.
Did you think that some points can be optimized ?
According sent rows, is influx is the appropriate database engine. ?
This piece of log are sent by a proxy service.
Average is around 4 000 000 rows per day for 365 days = 1 460 000 000 rows

Result is 36 929 on a 3GB database and influx take about 1.8GB memory.

Please give the results for the database that is causing the OOM errors. You mention "We have a database of 8GB size on a server with 4 CPUs and 12GB of memory" as the machine with the issue. Please give replies regarding only that machine, since that's the one with the OOM errors.

Did you think that some points can be optimized ?

Optimized how? There's no way to reduce RAM usage except to have fewer series. That would mean removing some tags or tag values, or inserting them as fields instead.

According sent rows, is influx is the appropriate database engine. ?

That's not enough data to say yes, but there's nothing about your use case that says InfluxDB is a poor choice.

.... That would mean removing some tags or tag values, or inserting them as fields instead ...
In this case, no aggregate function can be used like GROUP BY.
Installed PostgreSQL, injecting all datas, database size divided per 3, ( from 3GB to 1.2GB) memory used 540MB instead 1.8GB, same query time to get results...
Major changes, server still running and UP....
I think InfluxDB should be good to inject/query numeric values and extract rows with best performance if no aggregation made...
For us, definitively InfluxDB is not the right answer to store events/logs from proxies or FireWall...


Error during install: "File unchanged! The supplied flag value not found!  app/javascript/packs/application.js"

Hi,
Getting this:
15:21:49 henrik@devbox remit  master*$ bundle exec rails stimulus_reflex:install
/home/henrik/.devbox/code/remit/gems/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/stack.rb:37: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/home/henrik/.devbox/code/remit/gems/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/static.rb:110: warning: The called method `initialize' is defined here
/home/henrik/.devbox/code/remit/gems/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/stack.rb:37: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/home/henrik/.devbox/code/remit/gems/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/static.rb:110: warning: The called method `initialize' is defined here
Appending Stimulus setup code to /Users/henrik/Projects/barsoom/remit/app/javascript/packs/application.js
File unchanged! The supplied flag value not found!  app/javascript/packs/application.js
Creating controllers directory
       exist  app/javascript/controllers

This is a freshly generated Rails 6.0.2 app on Ruby 2.7.0 (thus the warnings…).
Running on an Ubuntu VM inside macOS.
I may have run the install command more than once if that has any relevance.

I removed SR and re-installed it. The next time, I got
15:51:06 henrik@devbox remit  master$ bundle exec rails stimulus_reflex:install
warning Integrity check: Top level patterns don't match
error Integrity check failed
error Found 1 errors.

========================================
  Your Yarn packages are out of date!
  Please run `yarn install --check-files` to update.
========================================

To disable this check, please change `check_yarn_integrity`
to `false` in your webpacker config file (config/webpacker.yml).

yarn check v1.19.1
info Visit https://yarnpkg.com/en/docs/cli/check for documentation about this command.

I made sure to explicitly start bin/webpack-dev-server, then ran yarn install --check-files, and then ran bundle exec rails stimulus_reflex:install again. This time I didn't get that error.

Paging @andrewmcodes, our resident rake expert.

Cheers! Not blocked by this anymore but could help others :)

@henrik super glad that you got this wrapped up.
Could you please close the issue if it's no longer unsolved?

Closing! 👍

try installing node js 16 using nvm


Error while parsing JSON

Hello.
Could you help me with this simple question. All of my projects locate in /home/azat/git/. For example if my project name is project it is in /home/azat/git/project folder.
In the project folder there are gulpfile.js, package.json files and node_modules folder with npm packages.
Here is a part of my gulfile.js:
var babel = require('gulp-babel');
var gulp = require('gulp');
var rename = require("gulp-rename");

gulp.task('jsx', function () {
  return gulp.src('src/jsx/*.jsx')
    .pipe(rename(function (path) {
      path.extname = ".js"
      }))
    .pipe(babel())
    .pipe(gulp.dest('src/js/'));
});

But if I put command gulp jsx, terminal gives an error:
azat@pc:~/git/project$ gulp jsx
[11:12:36] Using gulpfile ~/git/project/gulpfile.js
[11:12:36] Starting 'jsx'...

events.js:141
      throw er; // Unhandled 'error' event
      ^
SyntaxError: /home/azat/git/package.json: Error while parsing JSON - Unexpected end of input
    at Object.parse (native)
    at OptionManager.addConfig (/home/azat/git/project/node_modules/babel-core/lib/transformation/file/options/option-manager.js:100:62)
    at OptionManager.findConfigs (/home/azat/git/project/node_modules/babel-core/lib/transformation/file/options/option-manager.js:171:32)
    at OptionManager.init (/home/azat/git/project/node_modules/babel-core/lib/transformation/file/options/option-manager.js:229:12)
    at File.initOptions (/home/azat/git/project/node_modules/babel-core/lib/transformation/file/index.js:147:75)
    at new File (/home/azat/git/project/node_modules/babel-core/lib/transformation/file/index.js:137:22)
    at Pipeline.transform (/home/azat/git/project/node_modules/babel-core/lib/transformation/pipeline.js:164:16)
    at DestroyableTransform._transform (/home/azat/git/project/node_modules/gulp-babel/index.js:30:20)
    at DestroyableTransform.Transform._read (/home/azat/git/project/node_modules/gulp-babel/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:172:10)
    at DestroyableTransform.Transform._write (/home/azat/git/project/node_modules/gulp-babel/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:160:12)

So, why gulp-babel search my package.json file in the /home/azat/git/ folder? And how can I solve this problem?

I found the solution of the problem. It was package.json in the /home/azat/git/ folder, which is not my project folder. So, this is strange mistake.


Unhandled "error" event

Please describe the problem you are having in as much detail as possible:
After my bot has been running for around 30 minutes, it stops with this error:

I'm fairly certain it isn't my code because I have never touched events.js
I included lines 182-185 below
Include a reproducible code sample here, if possible:
/**
 * Expose
 */

Further details:

discord.js version: 11.2.1
node.js version: 8.8.1
Operating system: Windows 10
Priority this issue should have – please be realistic and elaborate if possible: low, this is a fairly minor error that seems to be confined to me

[ ] I found this issue while running code on a user account
[ ] I have also tested the issue on latest master, commit hash:

looks like your pc lost internet, nothing really to do about that

@devsnek probably was. I live in an area with Comcast lines from the 80's. You can imagine how stable that is.


Dev

PR Checklist

[ ] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] Documentation in docs is updated

Description of changes

Sorry, didn't mean to PR into fpgmass: main. I'm working on a fork.


My wishes.

This is not generally asking @majestrate but anyone who can do the following:

A professional looking theme (like Bootstrap - that doesn't look like it came from the shithole that is chan*.
Easier way to configure feeds (also easier docs)
Better configuration panel
Better configuration file (with comments)
Remove the old NNTP (2nd server) from the config file.

bootstrap theme
yes that would be nice

easier feed configuration
agree, needs more detail

better config panel
agree, also needs more detail, better in what way?

better config files (with comments)
agree

remove old nntp option
agree

"agree, also needs more detail, better in what way?" Rename the parameter names, they could be way better. Don't abbreviate and if you need to then use a comment to explain what that parameter does and it's states (0or 1)

@psgs Could you help with a Bootstrapped or your own professional looking theme for this project?

Hello :smiley:
Although this seems like an awesome project, and I would love to help, I'm a bit too busy with exams at the moment. Sorry :confused:

Don't wory man. :)
Also busy with exams. :)
On 05 June 2016 3:21:09 AM SAST, Francois<EMAIL_ADDRESS>wrote:

Hello :smiley:
Although this seems like an awesome project, and I would love to help,
I'm a bit too busy with exams at the moment. Sorry :confused:

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/majestrate/nntpchan/issues/72#issuecomment-223787489

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

I'm going to see if I can some how imporve the current mod panel with some h1 etc. tags

Assuming to amke a title such as
Mod pannel
 I would do

{{#i18n.Translations}}{{mod_pannel_page_heading}}{{/i18n.Translations}}

I wanted to know. About the whole thing of the NNTP server and that clients can spam. Should there maybe be a limit on how many posts can be made from an NNTP client.
This would probably mean that two NNTP servers should run.
The first NNTP server for the actual message propagation. (The one that talks to other Chan's)
And the second NNTP server for clients to connect to.

Should there maybe be a limit on how many posts can be made from an NNTP client.

possibly but it's always possible to "fake" a few things with the current sync stuff. you could always pretend to be another nntp server instead of a newsreader that posts.
I am of the opinion that IP based limits are futile in the long run.


Fix client-outputhost fd leak on consumer.close()

When consumer.close() is called and an outputhostconnection has some messages waiting to be read on the stream/socket, the readMessagesPump() go-routine might block forever, resulting in a go-routine / fd leak. This is because readMessgesPump() blocks on the deliveryCh (which is inturn read by the application using the library). This patch does the following:

Fixes the leak (by detecing close signal and draining the read pipe)
Removes the streamConnection member from consumerImpl, which is no longer used
Removes the closeConnection() helper on the consumerImpl and moves that logic within ouputhostconnection.close()

Coverage remained the same at 80.903% when pulling a71ba591ef0b89e18d09e3f8aa9e5dcd56137024 on fd-leak-fix into dcf9c0f081fc1e0506d43a3469b53c01e7377969 on master.


Price multiplier

Increase the maximum merchant buy/sell multiplier. Like, for example, 300% or 400% instead of the current maximum of 200%.

Already done. You can set it in settings of the merchant.

Oh I'm sorry I didn't find it and I searched a lot. I will look again.

It is in the newest version of the module on v9


caching HTTPS request on localhost crashes browser

On caching HTTPS request, browser crashes in development environment(i.e localhost). While it works fine in production since my application is on HTTPS.

There shouldn't be anything inherent in sw-toolbox that could crash a browser.
If there's a bug in a browser's service worker implementation that causes a crash, and sw-toolbox happens to trigger that browser bug, the best approach is to follow up with the browser's official issue tracker with a full set of steps to reproduce the crash:

Chrome bug tracker
Firefox bug tracker


--test-regex not working in Windows

In the repo eemeli/yaml-types I'm using TS sources in src/, but transpiling them to JS in dist/ with tsc before running tests. To make this work, I'm using this invocation, with no .taprc file:
tap --test-regex '\.test\.js$'

In Linux & MacOS this works fine, but my CI tests are failing in Windows with this error:
not ok 1 - no tests specified

Is tap supported on Windows?

It is, but quotes are weird on the windows command line. I recommend using just tap as the command, and adding "tap": { "test-regex": "\\.test\\.ts" } in package.json, or put the config in a yaml .taprc file.
Coverage with ts and esm is also somewhat broken in the current release of tap (which will be addressed in the next major, that's been my motivation to get onto yaml 2). You can see the setup I've been using here to get coverage with c8.

Thank you! By moving the config to "tap" in package.json I was able to make it work: eemeli/yaml-types#2.


 Basically, upon receiving first message for tcp address that we aren’t connected to, tcp router will initiate connection and requeue everything that is directed to this address until connection is established. Obviously, requeing messages can break ordering. Calling TcpTransport::connect before sending messages (as we were doing before) will guarantee ordering.
https://github.com/ockam-network/ockam/blob/develop/implementations/rust/ockam/ockam_transport_tcp/src/router/router.rs#L88

Possible fix is to delegate actual tcp connect from WorkerPair to TcpSendWorker::initialize or TcpRecvProcessor::initialize, and make connect call register new worker within tcp router immediately. This way since TcpSendWorker is already started and its address is known to tcp router, we can forward messages to it immediately (therefore, preserve ordering), even though actual tcp connection will be created after TcpSendWorker::initialize or TcpRecvProcessor::initialize is called.

Hi @SanjoDeundiak,
Where can I find in the documentation the description of the Ockam transport TCP connection and message transmission?


Selection formatting toolbar

Pull Request Description
In the documentation panel, add a toolbar for setting formatting properties of the selected text; it floats next to the selection, and initially supports bold/italic/strikethrough.
Cf. #9969
Important Notes

The icons are placeholders at the moment, but the code is otherwise ready for review.

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[ ] Unit tests have been written where possible.

icons incoming here https://github.com/enso-org/enso/pull/10030


cram index not recognized

I'm trying to use cram files to circumvent the htslib  >64k CIGAR operations problem for ultra-long reads.  As commented on commit 6918f6590ec66748b346063e4ff820ddb661866d, nanopolish doesn't handle/recognise the .crai index well. Something missing in the htslib/sam.c::sam_index_load2() arguments?
FYI I'm using samtools v1.6.
N.B. attempting to run it with a .bai generated from the .crai with cramtools-3.0.jar segfaults.
samtools index read.minimap2.cram && nanopolish eventalign -r ./read.fastq -b read.minimap2.cram -g hg38_UCSC.fa -t 2 --progress  Error: could not load the .bai index file for read.minimap2.cram  Please run 'samtools index read.minimap2.cram' before nanopolish

Hi,
Most nanopolish modules support cram but I missed adding support to eventalign. I'll fix this soon.
Jared

I've implemented cram support in eventalign, could you try the latest code and let me know if it works for you?

Thanks Jared! I'm getting this error now:
[cram_itr_query] tid=-3 not implemented for CRAM files -- Exiting Aborted

That's a new one to me - maybe try giving a defined reference region to compute the eventalign over:
nanopolish eventalign [...] chr1:10,000,000-20,000,000

Will do. Have a play if you want:
http://pwbc.garvan.org.au/~marsmi/ripper/fastq_runid_f84ad9e2bf813f3cf633e35d4a7bf531d021e5f3_0.fastq.bz2
http://pwbc.garvan.org.au/~marsmi/ripper/ripper.minimap2noL.cram

I've reported this to the htslib developers, hopefully they will implement it:
https://github.com/samtools/htslib/issues/625

Defining the reference region works, but eventalign fails to produce an alignment for this read (alignment should be respectable given the mean q-score of 12.445 with albacore-2.0.4).
[bam process] iterating over region: chr19:55900000-57030000 [post-run summary] total reads: 1 unparseable: 0 qc fail: 0 could not calibrate: 0 no alignment: 1

no alignment: 1 means that nanopolish couldn't infer the event-to-kmer mapping it relies on to realign the events to the reference genome. It could be due to the long read length, I haven't run many very long reads through it yet. If you don't mind experimenting, you could increase the bandwidth parameter here   to see if you can make it work:
https://github.com/jts/nanopolish/blob/master/src/nanopolish_raw_loader.cpp#L89

bandwidth = 200 worked!
What anticipated effect does a higher bandwidth parameter value have on computation?

Well, partially worked... will play around some more.


[INLONG-9831][Agent] Increase configuration acquisition capability

[INLONG-9831][Agent] Increase configuration acquisition capability

Fixes #9831

Motivation
Increase configuration acquisition capability
Modifications
Increase configuration acquisition capability
Verifying this change
(Please pick either of the following options)

[ ] This change is a trivial rework/code cleanup without any test coverage.

[ ] This change is already covered by existing tests, such as:
(please describe tests)

[ ] 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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

Left some comments, PTAL.


check bundle size with bundlesize

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.007%) to 99.488%

Totals

Change from base Build<PHONE_NUMBER>:
-0.007%

Covered Lines:
10064

Relevant Lines:
10066

💛  - Coveralls


[FEATURE] Search events based on cities

Detailed description
Create some tags for cities and if the user clicks on a city it will show the list of upcoming events going to happen in that city.
Context
As events can be based on multiple cities, so creating some tags for the cities and showing all the events going to happen in that city will give users a much better experience.
I would like to work on it for gssoc23
Possible implementation
No response
Additional information
No response
Code of Conduct

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

assign this to me, can contribute to this under GSSOC'23

Detailed description
Create some tags for cities and if the user clicks on a city it will show the list of upcoming events going to happen in that city.
Context
As events can be based on multiple cities, so creating some tags for the cities and showing all the events going to happen in that city will give users a much better experience.
I would like to work on it for gssoc23
Possible implementation
No response
Additional information
No response
Code of Conduct

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

Hey, I have created this issue and already mentioned that I want to work on it

@suzy-g38 do you want to work on this issue?

yes

I would like to work on this issue under GSSOC'23. I would appreciate if the issue is assigned to me.

@suzy-g38 you can start working on this issue

Hey @suzy-g38 ping me or @Deepu178 and let's have a discussion around the issue and your ideas


Bug/#979 - new LinearRing.getCenter method

... to be used in Polygon.setDefaultInfoWindowLocation
New class:

LinearRingTest: unit test class for LinearRing, only testing method getCenter for the moment

Impacted class:

LinearRing: added method getCenter

this PR looks like it has lots of unrelated commits.

@spyhunter99 Definitely. Only the last commit is related.
Sorry about that - everytime I tried something bold with git (like working on 2 separate branches) it failed. One day I'll learn how to properly use git.


HTTP 301 redirection exposes Azure internal URL for http requests

HTTP requests to our http://www.example.com are redirected (HTTP/1.1 301 Moved Permanently) to an azure URL eg https://lb-xxx.xxx.cloudapp.azure.com/ this cause a problem on browsers as the provided cert is issued for www.example.com.
HTTPS requests are resolved ok (HTTP/2 200).
The server_name on the nginx server configuration was changed from https://lb-xxx.xxx.cloudapp.azure.com to https://www.example.com. Also the moodle/config.php $CFG->wwwroot   = 'https://www.example.com';
Nameservers have A-records to domain example.com and subdomain www.example.com.
is there anyway the http redirection to not expose the internal azure URL?

I managed to resolve the issue by directly login in the VMSS and editing the service_name in the nginx site configuration file. Somehow the initial template deployment parameters were not setup correctly and that made it difficult to check and apply changes.


Typo fix "handhsake"

Pull Request Checklist

[ ] All changes are Go version 1.15 compliant
[ ] Your PR passes all CI checks. If a check cannot be passed for a justifiable reason, that reason must be stated in the commit message and PR description.
[ ] If this is your first time contributing, we recommend you read the Code Contribution Guidelines

[ ] The code being submitted is commented according to Code Documentation and Commenting
[ ] Commits have a logical structure according to Ideal Git Commit Structure

[ ] For new code: Code is accompanied by tests which exercise both the positive and negative (error paths) conditions (if applicable)
[ ] For bug fixes: If possible, code is accompanied by new tests which trigger the bug being fixed to prevent regressions
[ ] Any new logging statements use an appropriate subsystem and logging level
[ ] For code and documentation: lines are wrapped at 80 characters (the tab character should be counted as 8 characters, not 4, as some IDEs do per default)
[ ] A description of your changes should be added to running the release notes for the milestone your change will land in.

Thanks for the fix. However the git message is a bit off. Please refer to Ideal Git Commit Structure for acceptable git messages.

At the moment I don't have time to deal with CI & procedures for something this small, so feel free to close or take over. Thanks so much


Build with current nightly

With this, nadeko builds successfully for me on rustc 1.5.0-nightly (f93ab64d4 2015-09-21)

Ah, I always forget to add proper license.. I'm now considering MIT. Do you agree with it?

I have no problems with MIT

Thanks!


[#616] Restrict manager container security context

Drop all cpabilities and set seccomp profile to RuntimeDefault to avoid the warning: would violate PodSecurity "restricted:v1.24"

I executed make test-mk-v and make test-mk-do-v without failures.


Add gift code to give player cat hologram

code could be NOMEOWINGINGENERALCHAT
or just MEOW

Originally written by chomp

https://github.com/sp-tarkov/server/commit/7f0d740a1775559e3549fdd900475d03fab0b245

Originally written by chomp


Add HTTP client

I've made a client base that to make asynchronous HTTP requests. It follows the same principle as the ROS subscriber client, where a callback function is made available to client behaviours and is assigned to receive the HTTP response for processing. Only HTTP GET and POST requests are included right now, but its trivial to add others.
Note that the client base is dependent on the CPR library (C++ Requests, a high-level wrapper around libcurl). I've added an example which showcases the functionality and how the dependency can be resolved (sm_atomic_http). The CPR devs enabled CMake's FetchContent API so its quite portable and easy to integrate.
I understand this opens up the question of which dependencies to include in the SMACC library and how they should be handled. Using raw CURL will be more portable, but I found it quite hard to work with. CPR presented me a good balance of usability and portability. However, I'm open to suggestions for alternative approaches.
┆Issue is synchronized with this Jira Task by Unito
┆Link To Issue: https://robosoft-ai.atlassian.net/browse/SMACC1-5

I have to analyze this in detail but I think it would be nice to add this functionality.

This PR cannot be accepted in the state it is right now, one main reason (among others):

CPR is not and should not be a dependency of the "smacc" core package. We only should depend in ros standard packages and c++ std pkgs or boost.

I guess we could integrate this concept if it was part of one of the client_packages.

@pabloinigoblasco That's a fair point and its bothered me as well tbh.
I've been thinking of rewriting this client using the Boost.Beast module instead, which should be available on your repos if you can install ROS Noetic. The reason I didn't use it from the start is that we're using Ubuntu 18.04, which is stuck on Boost v1.65 and I think the Beast module was only added the Boost libraries in v1.68 and is available on Ubuntu 20.04, and will therefore only be available for Noetic. We were working on Melodic and are migrating to Noetic now, hence me only recently coming across Beast.
Would this be a better way forward? I do think a web client would be useful in SMACC to allow communication with remote machines through standard web requests or sockets, I guess the question is just how that should be implemented

using Boost.Beast sounds good.
It is available in Ubuntu 20.04 and also in Ubuntu 22.04.
Besides that refactoring to Boot.Beast
I still would introduce the following changes:

Using a new "client library package" instead of using the core "smacc package"
I would move the code to a cpp file always it is possible (excluding template methods)

From my side, we can go forward with this work.

I agree that this would be a valuable addition to the client library, with numerous use cases. I also like the idea of developing it in noetic. We plan on making noetic the master branch quite soon (currently melodic).

@pabloinigoblasco Fair points. I'll start porting it over as soon as I have some spare time and we've fully completed our migration to Noetic

Are there any complications with...

Moving the client https://github.com/yassiezar/SMACC2/blob/http-client/smacc2/include/smacc2/client_bases/smacc_http_client.hpp, to it's own folder in the smacc_client_library folder?
Moving the code to a cpp file?
Let's chat offline about this.


wish-list icon spacing issue on compare product's page #6793

Issue Reference
#6793

@papnoisanjeev
Please resolve the conflicts

@Sanjaybhattwebkul
Recompiled,  please check.

@papnoisanjeev
Please resolve the conflicts.

@Sanjaybhattwebkul
Recompiled, Please check.

@papnoisanjeev
Still showing conflicts.

@Sanjaybhattwebkul
Resolved please check.

@papnoisanjeev
Not fixed. the cross icon should be in center in the Arabic locale.Please find the screenshot Here

@papnoisanjeev
Please resolve the conflicts.

@Sanjaybhattwebkul
done.

@papnoisanjeev
The size of the cross icon should be the same  for all locales

@papnoisanjeev
The delete all button should be on the top-left corner. in Arabic locale. Please find the screenshot Here

@Sanjaybhattwebkul
All updates done here for Arabic locale please check.

@papnoisanjeev
Now this is working fine, please find the screenshot Here


Adjust UI

Description
Fixed UI related things listed in https://wiki.corp.adobe.com/display/AdobeDesign/Search+optimization+requirements
Url for testing

https://adjust-ui--helix-assets-ui--adobe.hlx3.page/#sidebar

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] 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:

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

@pkoch73 There are lots of linting errors, see either of

build log: https://github.com/adobe/helix-assets-ui/runs/6412235390?check_suite_focus=true
automatic inline comments: https://github.com/adobe/helix-assets-ui/pull/8/files

The helix linting rules are very strict and opinionated and doesn't allow many JS features :-) You can run npm run lint locally to see them or better yet use VS Code with eslint enabled, which will highlight them as errors while you type and offers automatic fixes for most.


"make test_gui" causes segfault with motif GUI

"make test_gui" causes segfault with the motif GUI.
Steps to reproduce
$ ./configure --with-features=huge --enable-gui=motif
$ make -j8
$ cd testdir
$ make test_gui
rm -f test_gui.res test.log messages
make -f Makefile test_gui.res
make[1]: Entering directory '/home/pel/sb/vim/src/testdir'
VIMRUNTIME=../../runtime; export VIMRUNTIME;  ../vim -f  -u unix.vim -u NONE -U NONE --noplugin --not-a-term -S runtest.vim test_gui.vim
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)
Makefile:168: recipe for target 'test_gui.res' failed
make[1]: *** [test_gui.res] Error 139
make[1]: Leaving directory '/home/pel/sb/vim/src/testdir'
Makefile:75: recipe for target 'test_gui' failed
make: *** [test_gui] Error 2

(gdb) bt
#0  0x00007faf43b12187 in kill () at ../sysdeps/unix/syscall-template.S:78
#1  0x0000560c74610ff4 in may_core_dump () at os_unix.c:3371
#2  0x0000560c74610f98 in mch_exit (r=1) at os_unix.c:3337
#3  0x0000560c7474e3c2 in getout (exitval=1) at main.c:1552
#4  0x0000560c745c4e09 in preserve_exit () at misc1.c:3161
#5  0x0000560c7460e8e0 in deathtrap (sigarg=11) at os_unix.c:1095
#6  <signal handler called>
#7  0x00007faf44f0bf65 in XrmStringToQuark () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#8  0x00007faf4587dff8 in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#9  0x00007faf4587e318 in XtSetValues () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#10 0x0000560c7470c195 in submenu_change (menu=0x560c766810d0, colors=1) at gui_motif.c:1543
#11 0x0000560c7470c313 in submenu_change (menu=0x560c7667fda0, colors=1) at gui_motif.c:1592
#12 0x0000560c7470c0b4 in gui_mch_new_tooltip_colors () at gui_motif.c:1515
#13 0x0000560c746b2efb in do_highlight (line=0x560c7664e3c8 "", forceit=0, init=0) at syntax.c:7507
#14 0x0000560c7454f3d0 in ex_highlight (eap=0x7fff5b698520) at ex_docmd.c:5692
#15 0x0000560c7454892f in do_one_cmd (cmdlinep=0x7fff5b698760, sourcing=1, cstack=0x7fff5b698850, fgetline=0x560c74543bc1 <getsourceline>, cookie=0x7fff5b698de0) at ex_docmd.c:2500
#16 0x0000560c74545d0b in do_cmdline (cmdline=0x560c76648250 "\" Vim color file", fgetline=0x560c74543bc1 <getsourceline>, cookie=0x7fff5b698de0, flags=7) at ex_docmd.c:995
#17 0x0000560c74543690 in do_source (fname=0x560c767ec600 "../../runtime/colors/torte.vim", check_other=0, is_vimrc=0) at ex_cmds2.c:3633
#18 0x0000560c74541802 in source_callback (fname=0x560c767ec600 "../../runtime/colors/torte.vim", cookie=0x0) at ex_cmds2.c:2454
#19 0x0000560c74541ad9 in do_in_path (path=0x560c76647590 "../../vimfiles,../../runtime,../../vimfiles/after", name=0x560c767eda20 "colors/torte.vim", flags=24, callback=0x560c745417dc <source_callback>, cookie=0x0) at ex_cmds2.c:2559
#20 0x0000560c74541ca3 in do_in_path_and_pp (path=0x560c76647590 "../../vimfiles,../../runtime,../../vimfiles/after", name=0x560c767eda20 "colors/torte.vim", flags=24, callback=0x560c745417dc <source_callback>, cookie=0x0) at ex_cmds2.c:2619
#21 0x0000560c74541ea8 in source_in_path (path=0x560c76647590 "../../vimfiles,../../runtime,../../vimfiles/after", name=0x560c767eda20 "colors/torte.vim", flags=24) at ex_cmds2.c:2678
#22 0x0000560c74541e73 in source_runtime (name=0x560c767eda20 "colors/torte.vim", flags=24) at ex_cmds2.c:2669
#23 0x0000560c746b2504 in load_colors (name=0x560c767ed88e "torte") at syntax.c:7176
#24 0x0000560c7454f343 in ex_colorscheme (eap=0x7fff5b699170) at ex_docmd.c:5674
#25 0x0000560c7454892f in do_one_cmd (cmdlinep=0x7fff5b6993b0, sourcing=1, cstack=0x7fff5b6994a0, fgetline=0x560c746f2a38 <get_func_line>, cookie=0x560c767ebdb0) at ex_docmd.c:2500
#26 0x0000560c74545d0b in do_cmdline (cmdline=0x0, fgetline=0x560c746f2a38 <get_func_line>, cookie=0x560c767ebdb0, flags=7) at ex_docmd.c:995
#27 0x0000560c746ed070 in call_user_func (fp=0x560c766294b0, argcount=0, argvars=0x7fff5b69a040, rettv=0x7fff5b69a220, firstline=1, lastline=1, selfdict=0x0) at userfunc.c:1063
#28 0x0000560c746ee128 in call_func (funcname=0x560c767db0f0 "Test_colorscheme", len=-1, rettv=0x7fff5b69a220, argcount_in=0, argvars_in=0x7fff5b69a040, argv_func=0x0, firstline=1, lastline=1, doesrange=0x7fff5b69a1e8, evaluate=1, partial=0x0, selfdict_in=0x0) at
userfunc.c:1621
#29 0x0000560c746ebaf3 in get_func_tv (name=0x560c767db0f0 "Test_colorscheme", len=-1, rettv=0x7fff5b69a220, arg=0x7fff5b69a1f0, firstline=1, lastline=1, doesrange=0x7fff5b69a1e8, evaluate=1, partial=0x0, selfdict=0x0) at userfunc.c:490
#30 0x0000560c746f25e8 in ex_call (eap=0x7fff5b69a2f0) at userfunc.c:3338
#31 0x0000560c7454892f in do_one_cmd (cmdlinep=0x7fff5b69a530, sourcing=1, cstack=0x7fff5b69a620, fgetline=0x560c746f2a38 <get_func_line>, cookie=0x560c767eacf0) at ex_docmd.c:2500
#32 0x0000560c74545d0b in do_cmdline (cmdline=0x560c7669e7d0 "call Test_colorscheme()", fgetline=0x560c746f2a38 <get_func_line>, cookie=0x560c767eacf0, flags=3) at ex_docmd.c:995
#33 0x0000560c7450d0fb in ex_execute (eap=0x7fff5b69ac30) at eval.c:8872
#34 0x0000560c7454892f in do_one_cmd (cmdlinep=0x7fff5b69ae70, sourcing=1, cstack=0x7fff5b69af60, fgetline=0x560c746f2a38 <get_func_line>, cookie=0x560c767eacf0) at ex_docmd.c:2500
#35 0x0000560c74545d0b in do_cmdline (cmdline=0x0, fgetline=0x560c746f2a38 <get_func_line>, cookie=0x560c767eacf0, flags=7) at ex_docmd.c:995
#36 0x0000560c746ed070 in call_user_func (fp=0x560c7658f810, argcount=1, argvars=0x7fff5b69bb00, rettv=0x7fff5b69bce0, firstline=1, lastline=1, selfdict=0x0) at userfunc.c:1063
#37 0x0000560c746ee128 in call_func (funcname=0x560c7663e360 "RunTheTest", len=-1, rettv=0x7fff5b69bce0, argcount_in=1, argvars_in=0x7fff5b69bb00, argv_func=0x0, firstline=1, lastline=1, doesrange=0x7fff5b69bca8, evaluate=1, partial=0x0, selfdict_in=0x0) at userfu
nc.c:1621
#38 0x0000560c746ebaf3 in get_func_tv (name=0x560c7663e360 "RunTheTest", len=-1, rettv=0x7fff5b69bce0, arg=0x7fff5b69bcb0, firstline=1, lastline=1, doesrange=0x7fff5b69bca8, evaluate=1, partial=0x0, selfdict=0x0) at userfunc.c:490
#39 0x0000560c746f25e8 in ex_call (eap=0x7fff5b69bdb0) at userfunc.c:3338
#40 0x0000560c7454892f in do_one_cmd (cmdlinep=0x7fff5b69bff0, sourcing=1, cstack=0x7fff5b69c0e0, fgetline=0x560c74546909 <get_loop_line>, cookie=0x7fff5b69c080) at ex_docmd.c:2500
#41 0x0000560c74545d0b in do_cmdline (cmdline=0x560c7660c680 "\" This script is sourced while editing the .vim file with the tests.", fgetline=0x560c74543bc1 <getsourceline>, cookie=0x7fff5b69c670, flags=7) at ex_docmd.c:995
#42 0x0000560c74543690 in do_source (fname=0x560c7660b843 "runtest.vim", check_other=0, is_vimrc=0) at ex_cmds2.c:3633
#43 0x0000560c74542bd1 in cmd_source (fname=0x560c7660b843 "runtest.vim", eap=0x7fff5b69c860) at ex_cmds2.c:3253
#44 0x0000560c74542b19 in ex_source (eap=0x7fff5b69c860) at ex_cmds2.c:3228
#45 0x0000560c7454892f in do_one_cmd (cmdlinep=0x7fff5b69caa0, sourcing=1, cstack=0x7fff5b69cb90, fgetline=0x0, cookie=0x0) at ex_docmd.c:2500
#46 0x0000560c74545d0b in do_cmdline (cmdline=0x560c76591c50 "so runtest.vim", fgetline=0x0, cookie=0x0, flags=11) at ex_docmd.c:995
#47 0x0000560c74545309 in do_cmdline_cmd (cmd=0x560c76591c50 "so runtest.vim") at ex_docmd.c:596
#48 0x0000560c74750673 in exe_commands (parmp=0x560c74a03e20 <params>) at main.c:2975
#49 0x0000560c7474d486 in vim_main2 () at main.c:797
#50 0x0000560c7474cd47 in main (argc=13, argv=0x7fff5b69d208) at main.c:444

I'll try when I find time to bissect in case it is a recent regression.
Environment

vim-8.1.1875, motif GUI
xubuntu-18.04.2 , x86_64

Dominique wrote:

"make test_gui" causes segfault with the motif GUI.

I've been having problems with Motif for a longer time.
What I have guessed is that the problem is in the Motif library.
Which library are you using?
It is possible that Vim uses the library incorrectly, in that case we
could fix it.
--
"Marriage is the process of finding out what kind of man your wife
would have preferred"
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

@brammool  wrote:

I've been having problems with Motif for a longer time.
What I have guessed is that the problem is in the Motif library.
Which library are you using?

Here are the name of the Ubuntu-18.04 packages:
$ dpkg -l | grep -i libmotif
ii  libmotif-common                       2.3.8-2build1                          all          Motif - common files
ii  libmotif-dev:amd64                    2.3.8-2build1                          amd64        Motif - development files

In /usr/include/Xm/Xm.h, I see:
#define XmVERSION_STRING "@(#)Motif Version 2.3.8"

I don't know what happened but I can't reproduce this bug anymore.
I tried various version of vim and none of them crashed when running test test_gui.
Closing.


GPSU Invalid Timestamp information

I am trying to parse data stream from HERO7 Black.
However, in the data stream there appears to be a corrupt data item:
GPSU type 'U' size 16 data: "2225525525425525",
It seems unlikely that this is due to storage device data corruption, as the rest of the stream is totally fine. I guess I'm asking if there is a known issue with GPSU timestamps being emitted incorrectly from the device, or if this is a known value to indicate some kind of error condition.
I do know that in some cases the first GPS5 with a GPSF of 2 or 3 is actually invalid - seems that if the lock is acquired part way through a packet, the entrie packet is marked with a lock, but some samples correspond to a non-locked period, but here the GPSF is 0
The previous and subsequent timestamps in the data stream are just fine, however the previous GPS5 sample looks odd:
    STRM nest size 264
      EMPT type 'L' size 4 data: 4,
      TSMP type 'L' size 4 data: 58,
      STNM type 'c' size 44 data: "GPS (Lat., Long., Alt., 2D speed, 3D speed)"
      GPSF type 'L' size 4 data: 3,
      GPSU type 'U' size 16 data: "220617220042.050",
      GPSP type 'S' size 2 data: 128,
      UNIT type 'c' samplesize 3 repeat 5 data: "deg", "deg", "m", ...

      SCAL type 'l' samplesize 4 repeat 5 data: 10000000, 10000000, 1000, 1000, 100,
      GPS5 type 'l' samplesize 20 repeat 3 data: 13,17788664,629855,-134217724,81, (redacted valid looking data)

    STRM nest size 284
      EMPT type 'L' size 4 data: 5,
      TSMP type 'L' size 4 data: 66,
      STNM type 'c' size 44 data: "GPS (Lat., Long., Alt., 2D speed, 3D speed)"
      GPSF type 'L' size 4 data: 3,
      GPSU type 'U' size 16 data: "220617220044.415",
      GPSP type 'S' size 2 data: 125,
      UNIT type 'c' samplesize 3 repeat 5 data: "deg", "deg", "m", ...
      SCAL type 'l' samplesize 4 repeat 5 data: 10000000, 10000000, 1000, 1000, 100,
      GPS5 type 'l' samplesize 20 repeat 5 data:  (redacted valid looking data)

Really appreciate any insights! - Thank you!

Is there any significance that the string (spacing for clarity) is "22 255 255 254 255 25" - looks like some kind of uninitialised buffer write?

I have never seen this error.  I expect you are correct in that there was some invalid data delivered from the GPS chip, or empty payload. We do have any error signalling for this, as we didn't know it could happen.  Have you seen this error more than once?

Hiya - Yes - this is the second time that it has been reported to me (although it is a defect reported against my parsing software, its not my actual device) - The end user  has supplied the MP4 file in the linked issue above if you'd like the whole thing.
Interestingly, the invalid GPSU data was the same in both cases.

Yes please to the sample clip.

Sure. The MP4 is in the linked issue above, along with a bit of narrative, but I'll duplicate it here: https://s3.amazonaws.com/s3.voneicken.com/GH010359.MP4

This seems to happen when I use my Hero 7 black without having the date set, i.e., it's set to some date in 2016. This in turn happens 'cause I run the camera with a USB-C power source and no internal battery: it looses the date after some hours without having any power when I remove the USB-C power to recharge the power pack.
Basically: remove battery from Hero 7 black, wait long enough for it to loose date&time (a few hours?), plug in USB-C power, switch to prefs and see that date is in 2016, start recording, observe the issue described here.

That is surprising as that time and date field is not from real time clock, it is the value reported from GPS.

It's not unbelievable though. This capture is from right at the start of the trace. It could be that after a few packets with a GPS time after a hard boot with loss of RTC, the firmware decides to do some extra work, which misses a deadline, so the output isn't captured for that timeslice. I have no idea how the gopro firmware is written, so this is pure conjecture!!

In the look at the number of samples per payload of GPS5, the GPS chip is behaving eratically.  Instead of 17-19 samples per payload (averaging around 18.1Hz), the stream (linked above) has payloads of 13, 9, 0, 4, 5, 0, 3.., averaging 4.6Hz.  The GPS chip is not behaving ideally.  This camera likely needs a factory reset.

I'm not sure the problem is reproducible. I just took a look at the recordings I have since the first one without date&time set:

2022/4/16 - date&time not set, GPS track is fine
2022/6/17 - date&time not set, GPS track messed-up, sample linked 4 comments up
2022/6/18 - date&time sync'd before recording, GPS track is fine
2022/6/23 - date&time not set, GPS track is fine
2022/6/24 - date&time not set, GPS track has issues with data points out of order (by <1sec)
2022/6/25 - date&time sync'd, GPS track is fine

I'm concluding that if the date&time are lost there is a chance that the GPS track ends up messed-up, but it's not systematic. Presumably some race condition. I'm not sure this can be pursued productively at this point.

We also don't have any firmware releases planned for HERO7.  This should not come up on more recent cameras.

Hi @dnewman-gpsw  - Just FYI -  I had another user report of invalid data in GPSU. https://github.com/time4tea/gopro-dashboard-overlay/issues/141

I look forward to knowing the camera model this was.

Hi - The Camera was Hero 9 Black - HD<IP_ADDRESS>.00
I can see the same sort of behaviour as before, where the number of samples from the GPS chip is erratic for the whole file.
Here is some debug from my software (the GPS5 values are redacted)
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 31 35 37 2e 37 32 39] [b'230625112157.729']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 1, Length Bytes=28/20
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 31 35 37 2e 37 32 39] [b'230625112157.729']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 4, Length Bytes=88/80
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 30 2e 35 33 34] [b'230625112200.534']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 30 2e 35 33 34] [b'230625112200.534']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 5, Length Bytes=108/100
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 31 2e 36 33 34] [b'230625112201.634']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 32 2e 35 36 39] [b'230625112202.569']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 3, Length Bytes=68/60
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 32 2e 35 36 39] [b'230625112202.569']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 3, Length Bytes=68/60
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 34 2e 30 35 34] [b'230625112204.054']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 34 2e 30 35 34] [b'230625112204.054']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 2, Length Bytes=48/40
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 34 2e 30 35 34] [b'230625112204.054']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 37 2e 30 32 34] [b'230625112207.024']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 37 2e 37 33 39] [b'230625112207.739']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 1, Length Bytes=28/20
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 30 38 2e 35 36 34] [b'230625112208.564']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 2, Length Bytes=48/40
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 30 2e 33 37 39] [b'230625112210.379']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 9, Length Bytes=188/180
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 30 2e 33 37 39] [b'230625112210.379']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 3, Length Bytes=68/60
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 31 2e 38 30 39] [b'230625112211.809']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 31 2e 38 30 39] [b'230625112211.809']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 9, Length Bytes=188/180
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 33 2e 37 33 34] [b'230625112213.734']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 33 2e 37 33 34] [b'230625112213.734']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 3, Length Bytes=68/60
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 36 2e 31 35 34] [b'230625112216.154']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 37 2e 37 34 39] [b'230625112217.749']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 1, Length Bytes=28/20
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 37 2e 37 34 39] [b'230625112217.749']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 8, Length Bytes=168/160
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 39 2e 38 33 39] [b'230625112219.839']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 31 39 2e 38 33 39] [b'230625112219.839']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 1, Length Bytes=28/20
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 32 2e 32 35 39] [b'230625112222.259']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 32 2e 32 35 39] [b'230625112222.259']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 3, Length Bytes=68/60
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 34 2e 31 38 35] [b'230625112224.185']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 2, Length Bytes=48/40
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 34 2e 31 38 35] [b'230625112224.185']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 6, Length Bytes=128/120
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 35 2e 33 39 35] [b'230625112225.395']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [35 35 30 39 31 30 30 30 38 32 32 34 30 34 30 30] [b'5509100082240400']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [35 35 30 39 31 30 30 30 38 32 32 34 30 34 30 30] [b'5509100082240400']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 1, Length Bytes=28/20
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 39 2e 30 32 35] [b'230625112229.025']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 10, Length Bytes=208/200
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 39 2e 30 32 35] [b'230625112229.025']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 6, Length Bytes=128/120
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 39 2e 36 38 35] [b'230625112229.685']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 32 39 2e 36 38 35] [b'230625112229.685']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 4, Length Bytes=88/80
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 31 2e 36 36 35] [b'230625112231.665']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 33 2e 37 30 30] [b'230625112233.700']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 3, Length Bytes=68/60
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 33 2e 37 30 30] [b'230625112233.700']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 6, Length Bytes=128/120
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 35 2e 36 38 30] [b'230625112235.680']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 36 2e 35 30 35] [b'230625112236.505']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 3, Length Bytes=68/60
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 36 2e 35 30 35] [b'230625112236.505']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 6, Length Bytes=128/120
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 38 2e 37 30 35] [b'230625112238.705']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 33 38 2e 37 30 35] [b'230625112238.705']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 2, Length Bytes=48/40
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 34 30 2e 32 34 35] [b'230625112240.245']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 34 31 2e 35 36 35] [b'230625112241.565']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 2, Length Bytes=48/40
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [32 33 30 36 32 35 31 31 32 32 34 31 2e 35 36 35] [b'230625112241.565']

As you can see, the GPSU values are incorrect for a few samples:
GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [35 35 30 39 31 30 30 30 38 32 32 34 30 34 30 30] [b'5509100082240400']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 0, Length Bytes=8/0
  GPMDItem: GPSU, Type=U, Size=16, Repeat: 1, Length Bytes=24/16 [35 35 30 39 31 30 30 30 38 32 32 34 30 34 30 30] [b'5509100082240400']
  GPMDItem: GPS5, Type=l, Size=20, Repeat: 1, Length Bytes=28/20

I don't have permission to share the file - is there any more information that would be useful for you? I'm guessing that this is probably happening quite a lot, as my software doesn't have that many users, and we have seen a couple of incidences now.
Thanks!

I hadn't previously noticed, but the timings of the samples are also very erratic, sometimes multiple packets at exact same time (hence 0 size, i guess)

Filtering is likely the only solution for these older camera sources.  HERO11 deprecated GPS5 and GSPU, adding GSP9 as cleaner way to sync time and location.

I can filter the invalid GPSU, but incorrect values are correlated with loss of sync with GPS chip or something, as can be seen by the erratic readings.
I take it that no further firmware will be created for these devices, so it is what it is...

Correct, new firmware is not likely.


Error: Problems reading data from Binary store in /tmp/gradle

I am getting the Error as follows, when I try to run the flutter app.
What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
Could not resolve all dependencies for configuration ':app:debugCompileClasspath'.
Problems reading data from Binary store in /tmp/gradle4420452894670361188.bin offset 455548 exists? true

I have set this in build.gradle
classpath 'com.google.gms:google-services:4.3.3'
I have this dependency in app/build.gradle
apply plugin: 'com.google.gms.google-services'
When I remove app/build.gradle google-services plugin, app worked fine. Since I need google-services plugin, I want to know how to solve this problem. Thanks!
This is the flutter doctor -v output.
[✓] Flutter (Channel stable, 2.2.3, on Linux, locale en_US.UTF-8)
    • Flutter version 2.2.3 at /opt/flutter
    • Framework revision f4abaa0735 (6 days ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/**/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.
[✓] Chrome - develop for the web
    • Chrome at google-chrome
[✓] Android Studio (version 4.1)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 57.0.1
    • Dart plugin version 201.9380
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] IntelliJ IDEA Community Edition (version 2019.3)
    • IntelliJ at /home/**/Office Works/Softwares/idea-IC-193.6494.35
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
[✓] IntelliJ IDEA Community Edition (version 2018.2)
    • IntelliJ at /opt/idea
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
[✓] VS Code (version 1.50.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.17.0

I am getting similar error for last 2 days with my react-native app. Still looking for soultion

This is most likely caused by a corner case in the dependency resolution engine. Unfortunately without a reproducer it is quite impossible to track down.
Can one of you share such a reproducer?
An alternative is to tweak dependency declarations as the order in which the graph is walked is sometimes a way to work around the bug. Tweak means: adding versions where you expect it from a platform, re-ordering declarations, etc ...

I could solve the issue by upgrading the gradle to gradle-6.7.

distributionUrl=https://services.gradle.org/distributions/gradle-6.0-all.zip

Indeed, I should have asked about the Gradle version. A number of fixes in this area were made during the 6.x line. I would encourage you to upgrade to Gradle 6.9 or even 7.x.
I'll close this issue for now. A new issue with a recent Gradle version and a reproducer can be opened if needed.


Delete duplicated warning

Docs Build status updates of commit 00d5602:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerapps-docs/developer/data-platform/org-service/metadata-option-sets.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit eeeb1d9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerapps-docs/developer/data-platform/org-service/metadata-option-sets.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@filcole
Thanks for finding and fixing this.


Can't browse docs for 2.2 version.

It seems that all docs are being updated to 3.0, but I am still using 2.2. How can I browse the 2.2 docs?

youre going to have to go back to the last commit in master to find previous release docs. Unfortunately I did not tag releases pre 3.0 in the repo.


build: upgrade kubernetes dependency

Issue link

What changes have been made

Verification steps

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

/retest


chore: address porting note in Archive/Imo/Imo1994Q1 -- linarith works now

According to git bisect, #7905 is what made the single linarith call work here.

Thanks!
bors merge


chore!: refactor testnode to expose appcreator

Overview
This refactor is mainly targeting #1990, but doing so in a way that uses common patters to avoid continuing to blow up the api
closes #1990
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

Codecov Report

Merging #1991 (6babf4c) into main (b2fc98c) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1991      +/-   ##
==========================================
- Coverage   21.49%   21.42%   -0.07%
==========================================
  Files         122      123       +1
  Lines       13817    13861      +44
==========================================
  Hits         2970     2970
- Misses      10558    10602      +44
  Partials      289      289

Impacted Files
Coverage Δ

test/util/testnode/config.go
0.00% <0.00%> (ø)

test/util/testnode/full_node.go
0.00% <0.00%> (ø)

test/util/testnode/node_interaction_api.go
0.00% <0.00%> (ø)


Support for Mijia Wireless Switch WXKG01LM

Hello,
Is support for the Wireless Switch WXKG01LM planned ?
Related question : iIs moving from DGNWG02LM to ZNDMWG03LM too early ?
Regards.
Dorian

I used DGNWG02LM and ZNDMWG03LM both,
Gateway 3 works well in ZHA mode to connect ZigBee 3.0 devices and also can link the BLE devices to ha,
In the current situation, using two gateways at the same time can achieve better results, It provide more connectable devices.

Supported

Supported


[Support] Site-to-Site VPN with OpenVPN

In raising this issue, I confirm the following:

[X] I have read and understood the contributors guide.
[X] The issue I am reporting can be replicated.
[X] The issue I am reporting can be is directly related to the pivpn installer script.
[X] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Question:
I have two networks:
Network A: <IP_ADDRESS>/24
Network B: <IP_ADDRESS>/24
In both networks I have a PIVPN Raspberry. Client to Server connection is working on both. I can connect with the OpenVPN Client to both PIVPNs and the corresponding Subnet.
Now I want to setup a Site-2-Site VPN to enable access from all Clients in Network A to Network B.
I am searching now a couple of days but I didnt got it running nor didnt I find any proper How-TO.
Br,
Johannes

Hi! thanks for opening an issue on our github page, please consider that when opening issues you should follow the template accordingly .. currently you are opening a support request using a bug report template.
We provide templates so you can provide us the details we need to be able to help you out, checking all the boxes doesn't make it any better or any faster to get help, quite the opposite will only take out our attention from what is really important.
Please take that in consideration next time, or whenever you ask for help in this or any other open source project.
Regardless, the subject is not pivpn related, is rather a custom setup, also I seen you have posted on reddit https://www.reddit.com/r/pivpn/comments/kaaaw1/pivpn_site_to_site_vpn_config/
also please take into consideration that you are asking for help with a very specific type of setup that not everyone has experience (me included) with, so it might take a while until someone has the chance or notices it and helps you with it.
thanks for your understanding and for using pivpn.
kind regards.
Closing this topic.


Wrong Height on items & statics

Height is not always taken from tiledata. The item from the picture got 5 height in tiledata and 20 ingame.
It affect to statics from map as well.
I believe it is cos height of duped items are taken from original item.
Causes many walls to be bigger than they really are.  Or maybe even to be windows.
Did not test if it happens with during canseelos() but I believe it does.

Until I see, duped item are not CItemBase but CItemBaseDupe. So duped items take height from the original one. I imagine this is to prevent memory usage or something like that.
Low, mid and high walls use to be dupes from the same item. so all have same height.
But Im not sure of one thing. Citembase looks for height into the tiledata eachtime? or height is preloaded from tiledata?

We have similar bug with range with bow. https://github.com/Sphereserver/Source-X/issues/710. Do not take range of the baseId

We have similar bug with range with bow. #710. Do not take range of the baseId

Looks similar but are not related I think.

I think this issue should be fixed by scriptpack cos by source it would increase memory usage I think.

Is this still happening?


[1358] Authenticate in ApplicationController by default

This reduces the error of 'authenticate' being forgotten in a new controller.

Closing in favour of #222


Wrong address in stack for the msys2-20200517-i686.tar.xz package

The stack tool requests the path:
/commercialhaskell/stackage-content/releases/download/msys2-20200517/msys2-20200517-i686.tar.xz
while the correct path from the website seems to be:
/commercialhaskell/stackage-content/releases/download/20200517/msys2-20200517-i686.tar.xz

Can you send a PR to update it?


Fix MyPy Typing for GeometryCollection

I believe this has been fixed with #60 can re-open if not.


when using wget in a dockerfile the /etc/hosts of the server is not used only dns

run wget in Dockerfile with host in /etc/hosts and not in dns fail
if i do
cat Dockerfile
from oraclelinux
RUN yum clean all && yum update -y && yum install -y wget
ADD infloop /usr/local/bin/infloop
RUN wget http://termix:/soft/java/jdk-7u99-linux-x64.rpm
CMD infloop
the build fail
despite host termix is in /etc/hosts and not in corporate dns
and /etc/nsswitch.conf has
hosts:      files dns myhostname
if i do
cat Dockerfile.ip
from oraclelinux
RUN yum clean all && yum update -y && yum install -y wget
ADD infloop /usr/local/bin/infloop
RUN wget http://<IP_ADDRESS>:/soft/java/jdk-7u99-linux-x64.rpm
CMD infloop
it works
Steps to reproduce the issue:
see above
Describe the results you received:
Step 4/5 : RUN wget http://termix:/soft/java/jdk-7u99-linux-x64.rpm
---> Running in f70f8ba313d4
--2017-02-10 12:55:11--  http://termix/soft/java/jdk-7u99-linux-x64.rpm
Resolving termix (termix)... failed: Name or service not known.
Describe the results you expected:
build succeeds
Output of docker version:
docker version
Client:
Version:      1.13.1
API version:  1.26
Go version:   go1.7.5
Git commit:   092cba3
Built:        Wed Feb  8 06:38:28 2017
OS/Arch:      linux/amd64
Server:
Version:      1.13.1
API version:  1.26 (minimum version 1.12)
Go version:   go1.7.5
Git commit:   092cba3
Built:        Wed Feb  8 06:38:28 2017
OS/Arch:      linux/amd64
Experimental: false
Output of docker info:
docker info
Containers: 14
Running: 0
Paused: 0
Stopped: 14
Images: 108
Server Version: 1.13.1
Storage Driver: btrfs
Build Version: Btrfs v4.4.1
Library Version: 101
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-514.2.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.51 GiB
Name: fondation.eservglobal.fr
ID: T62N:NMNV:SXYD:X7EB:YC27:HJIA:UQ3Z:I3EQ:AQAK:DCN2:R5SG:LMLQ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
environment:
physical on centos 7.3

Are you referring to /etc/hosts on the host machine or within the container itself?

from oraclelinux
RUN yum clean all && yum update -y && yum install -y wget
ADD infloop /usr/local/bin/infloop
RUN wget http://termix:/soft/java/jdk-7u99-linux-x64.rpm //here this cmd will run in container
CMD infloop

i am referring to the /etc/hosts on the host machine
Le Vendredi 10 février 2017 15h55, Joseph McCullough<EMAIL_ADDRESS>a écrit :

Are you referring to /etc/hosts on the host machine or within the container itself?—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This is expected behavior
The container gets its own /etc/hosts.
See #30383 for adding the --add-host functionality from run to build.
Thanks!

Thank you!
Le Lundi 13 février 2017 17h09, Brian Goff<EMAIL_ADDRESS>a écrit :

Closed #30913.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Two scripts for data exploration

Explore and present CTCH dataset.
Explore and present El. vestnik dataset.

It looks good.

It looks good.