Windows Server 2019 Essentials | ISO de 64 bits

[Enter feedback here]

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

ID: 38acb737-4d4d-97a3-1f8c-4c36f4429be9
Version Independent ID: 17a853fc-e6aa-108e-95eb-50753ef13ade
Content: What's New in Windows Server, version 1809
Content Source: WindowsServerDocs/get-started/whats-new-in-windows-server-1809.md
Product: windows-server-threshold
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

Not sure what the feedback is here?


@JStr84galaxy Was there any problem in the recent version of the dependency?

@JStr84galaxy Was there any problem in the recent version of the dependency?
Originally posted by @suztomo in https://github.com/GoogleCloudPlatform/java-docs-samples/issues/6168#issuecomment-940585523

I am not sure what this issue is about. Closing.


install-grub.pl fails when / is tmpfs

Issue description
I'm attempting to migrate my root onto a tmpfs. When rebuilding the system, the system errors when switching configurations and the grub boot menu doesn't get properly updated. The exact error is:
Failed to get blkid info (returned 512) for / on none at /nix/store/...-install-grub.pl line 189.

More information on your partition/filesystem layout is going to help us a bunch. Could you provide this?

Of course, my mistake, I wrote this in a hurry after an exhuasting day. Forgive my sloppiness. So I'm currently on NixOS 20.03. I need to use grub because I am using an encrypted boot parition. Here is my root file-system declaration:
  fileSystems."/" = {
    device = "none";
    fsType = "tmpfs";
    options = [ "defaults" "size=2G" "mode=755" ];
  };

The interesting thing is that the system built and deployed the first time it was run, but once I actually booted into the system and root was on the tmpfs, I couldn't rebuild any new configurations due to the mentioned error, nixos-rebuild failed every time. I was only able to revert thanks to a previous boot generation.

This is still an issue on 2.4pre20201201_5a6ddb3 with the following mount:
tmpfs on /mnt type tmpfs (rw,relatime)
fileSystems."/" =
    { device = "tmpfs";
      fsType = "tmpfs";
    };

@sheeldotme, for now, I was successfully able to workaround this using ZFS as explained by grahamc

Having the same issue in the latest unstable nixos.

Can someone provide a full test case for this? My machine runs tmpfs as root with grub and it works fine.

Related:  https://github.com/NixOS/nixpkgs/issues/130125

A properly configured tmpfs-as-root system will not run into this issue, so the problem is going to be based in the way the machine was configured. This issue sort of looks abandoned since it's been most of a year with no response, so I'm going to close it, but if you want to re-open and post the config that exhibits this issue, I can give it a look.

For anyone happening upon this via search engine, this error can happen when /boot is part of the tmpfs (e.g. because you used /boot/efi as ESP) and you go with the default config for grub2. As mentioned above, this is misconfiguration.


feat(@ciscospark/i-p-wdm): switch server when current server fails

add server error interceptor to switch server url when a REST request
fails

This PR should be closed, replaced by a nearly identical PR from jofuhrma


Base server

This migrates the most basic API functionality over to a standalone module. It only explicit route it is equipped with is the build-in status module.

👍

👍


[docs]Solve the problem of invalid document URL address in README.md file

https://github.com/apache/flink-cdc/issues/3105
Solve the problem of invalid document URL address in README.md file
Modify the URL in the file that points to the document address

@hnbian Thanks for the PR! We've refactored the entire README so the patch won't be valid anymore. Feel free to create issue and PRs if you find more


Undo migrations with down.sql?

Could not find in the docs whether or now using .down.sql scripts is supported to go back to an earlier db state.
Could you confirm whether or not that is the case?

Yes, you can check this example which has .down.sql migrations.


Diagnostic files not being archived as expected with test_output

There have been 2 reports of core files generated from openjdk test crashes not getting archived.  We believe this functionality should work when ARCHIVE_TEST_RESULTS is selected in a Grinder job (https://github.com/AdoptOpenJDK/openjdk-tests/pull/1073), but we should investigate why it is not.

We currently set jtreg tests as only retain files generated by test that fail or cause error. That is if test pass and no error all generated files will be deleted after each test completes executing.
Some special case is there are system dump generated by passing tests, which dump files will be deleted. In order to keep those file we can update to retain those files by using file name pattern.

Good catch, the 2 cases that were reported through Slack are when tests report as passed (but a crash is still seen).

Interesting, even if set with option to retain files that match a specific filename there is no those files under that specific folder described on console output 'tests/TestConfig/test_output_15613907978889/jdk_util_0/work/scratch/4/core.20190624.114421.14985.0001.dmp'

Actually scratch directory is a tmp directory for the running test, which is used to write any temporary files. Jtreg will ensure that the directory is always empty when the test begins. So we cannot expect dump or other files stay there.
The corresponding dmp files can actually be found per tests.

So two notes here

Will update code to make sure even if tests pass still retain those dmp files
Instead of finding the files under scratch please find them per tests


In colemak layout for the dvorak Kinesis mode, add right handed backslash

I found that there were two forward slashes accessible to the right pinky finger, so this makes one of them (top right) into a backslash.
This was an important change for me because the other backslash key in the Kinesis dvorak keycap set (bottom left of keyboard) is actually an international key, and seems to switch function between OSes.  In Windows it is indeed backslash, but in Linux it ends up with other mappings.  So I was without a backslash regularly, and two forward slashes for the right pinky didn't help much.  There are other ways to fix the international key mapping, but two forward slashes in close proximity seems suboptimal.

thanks!


⚠ Bofrost.be has degraded performance

In dcc97fb, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1079 ms

Resolved: Bofrost.be performance has improved in b43287a.


ReadMe ADD and Code changed

Description
This repository contains a simple implementation of the Binary Search Algorithm in Python. Binary search is an efficient algorithm used to find the position of a target value within a sorted list. The search works by repeatedly dividing the list in half, checking if the middle element is the target, and then narrowing down the search range accordingly.
Type of change

[ ] New Project
[X] New Feature
[ ] Bug fix

Issue number:
#17
Checklist:

[X] I have included a README.md file for my project clearly explaining its purpose, functionality, and usage instructions (applicable for new projects, not bug fixes).
[X] My code adheres to the style guidelines outlined by this project.
[X] I have thoroughly reviewed my code to identify and address any potential errors or inconsistencies.
[X] I have added clear and concise comments to my code, especially in sections that might be challenging to understand at first glance.
[X] I have reviewed and followed the project's Contributing Guidelines to ensure my contribution aligns with the project's requirements.

Thank you @Sayanjones


yolo of yolo of yolo

yolo could/should be smarter when modifying an image that has been yolo'd already
otherwise we are ending up with 5+ layers of yolo already

In @chigozienri 's usecase - I'm assuming she was using the same base/dest - which will result with this:

I am guessing we should have condensed it to a single yolo layer

working on this in #22


Update GitOpsSets docs

Closes #2373

Updated GitOpsSets docs with my editing suggestions.

@Callisto13  Great, thanks!


pass global leaks error on window.onerror in browser

in firefox < 9.0, window.hasOwnProperty('onerror') === true, so it will always emit an global leaks error on window.onerror

do we need the .navigator?

sorry, i didn't catch you
i use .navigator here to check the running environment -- node or browser
another solution is to use dom level 2 event handler in support/tail.js


Script won't start because it's trying to use dash environment

Hey, I tried to run the script for adding the application colors but I immedately get this error /usr/bin/env: ‘dash’: No such file or directory. There's a typo in the script, as I changed the /usr/bin/env from dash to bash and it worked

fixed, thanks!

Np! :D


Validate QCs

Current dependencies on/for this PR:

feature/pos-process-block

PR #727

PR #728

PR #729

PR #730

PR #732   👈

This comment was auto-generated by Graphite.

Merge activity

Oct 17, 7:42 PM: @lazynina started a stack merge that includes this pull request via Graphite.


align core service logs

Resolves #803

Thanks!

However, the log "Core service started..." is misleading from the _job_dispatcher.py.

yes, as issue #803 say that running the core service does more than just starting a job dispatcher, so just replace the words is misleading

Instead, I suggest changing the "Start job dispatcher" log to a debug log, and add the "Core service started..." log to the Core.run() method.

Also the Core service has been stopped. is add to the Core.stop() method, i think add  "Core service started..." log to the Core.run() method is a good way.
If set Start job dispatcher to a debug log , whether the stop job dispatcher also do that

You're right. We probably can remove both the ...


Increase connection timeout when using C* python driver

I don't know if it's related to the new C* python driver that got released yesterday (3.3.0), but as of today, I had problems successfully running the cstar_perf UI in a docker container.
I have been seeing that a client would run into a timeout when establishing a connection with C*:
WARNING:cassandra.cluster:[control connection] Error connecting to <IP_ADDRESS>:
Traceback (most recent call last):
  File "cassandra/cluster.py", line 2154, in cassandra.cluster.ControlConnection._reconnect_internal (cassandra/cluster.c:37797)
    return self._try_connect(host)
  File "cassandra/cluster.py", line 2176, in cassandra.cluster.ControlConnection._try_connect (cassandra/cluster.c:38315)
    connection = self._cluster.connection_factory(host.address, is_control_connection=True)
  File "cassandra/cluster.py", line 847, in cassandra.cluster.Cluster.connection_factory (cassandra/cluster.c:10142)
    return self.connection_class.factory(address, self.connect_timeout, *args, **kwargs)
  File "cassandra/connection.py", line 330, in cassandra.connection.Connection.factory (cassandra/connection.c:5749)
    raise OperationTimedOut("Timed out creating connection (%s seconds)" % timeout)
OperationTimedOut: errors=Timed out creating connection (5 seconds), last_host=None
```

After increasing the connection_timeout, things started to work as before.

Please note that the default connection_timeout is **5s**

Thanks!


Create DB based on a Diagram: 'clinic' database created from the diagram provided

Hello Dear Code Reviewers Team 👋,
Misal/Luis Team would like to ask for your kindly help to do the 🔍 Code Review 👀 for our project.
- 🎯 Project requirements

📌 Create a file named schema_based_on_diagram.sql where you implement the database from the diagram.

✅ The specified file was created.

📌 Join tables from many-to-many relationships might not appear in the diagram, but you still need them.

✅ Table treatments_histories was created.

📌 Remember to add the FK indexes.

✅ INDEXES for all FK were added.

We really thank you for your support. 🙏
Cheers and Happy Reviewing! 👀
Misal/Luis Team! 🙋♂

@misalazeem and @luigirazum, move the second author from contrinution section to author section


404 when regenerating oauth2 secret

Gitea version (or commit ref): Latest
Git version: Latest
Operating system: Arch Linux x64
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

Description
I am unable to regenerate the secret for an Oauth2 application.
Screenshots

after clicking regenerate secret:

Can you please provide your logs around the time of a 404?


add Env.clearAll function

Signed-off-by: Brian Downs<EMAIL_ADDRESS>

Well detailed description of the change :

Adds a function that clears all environment variables.

Resolves: #

Type of change:

[ ] Bug fix

[x] New feature

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Housekeeping

[ ] Tests have been updated to reflect the changes done within this PR (if applicable).

[ ] Documentation has been updated to reflect the changes done within this PR (if applicable).

Preview (Screenshots) :

I initially added it but couldn't get CI to pass. I don't have access to a Windows box to test. Frustration lead to *nix only.. :/ Added support back in.

I initially added it but couldn't get CI to pass. I don't have access to a Windows box to test. Frustration lead to *nix only.. :/ Added support back in.

Ahh okay no worries. I'll be able to test it out on windows and try get it working

This is an interesting one. Seems whenever I unset all env vars on windows the process just exits when running the tests. In the REPL it runs the first time then exits the second (with some changes to use strchr rather that strstr).
It's causing some headaches for me on windows so I'm unsure how I feel about this one :/

Happy to adjust this to be nix* only.

I think for now we can do that, will aim to revisit the windows implementation at some point

Cheers for this 🎉


[Feature request] negative y coord spawning

Is it possible to get support for the mobs to spawn below y 0?  I have a custom world with 1.18 caves, and mobs only spawn above y 0.
This plugin is amazing, brings so much fear and excitement into caving, and pairs so well with our server.

Probably resolved in latest build. Please, try it out.


The disabled option for useFetch ignored

Describe the bug
I was expecting to halt the query until the expression would evaluate true. Instead the fetch appears to always run, no matter what I pass to this param.
To Reproduce
const { data, error, loading } = useFetch(getSpeaker.setParams({ speaker: el.dataset.speaker }), {
    disabled: !showDrawer,
    refetchOnFocus: false,
});

Expected behavior
I was expecting this to behave similarly to react-query, where the fetch will only happen once disabled evaluates to true. Is that a fair assumption?
Desktop (please complete the following information):

OS: macOS
Browser: Chrome

Additional context
Add any other context about the problem here.

Apologies, I mixed up something on my codebase and this is indeed working as assumed. I was just looking at the wrong place.


Prometheus storage considered dirty on every startup

I'm using an upstart script to launch prometheus (prometheus is invoked by cronolog inside the script section, no real content other than that), and that works well for us (upstart commands perform as advertised).
However, every single time that prometheus starts up after being shutdown by an upstart command, storage is considered DIRTY:
prometheus, version 0.15.1 (branch: master, revision: 17eebbc)
  build user:       @19c92959409e
  build date:       20150729-21:28:47
  go version:       1.4.2
time="2015-08-13T17:32:32Z" level=info msg="Loading configuration file /etc/prometheus/prometheus.yaml" file=main.go line=173
time="2015-08-13T17:32:32Z" level=info msg="Loading series map and head chunks..." file=storage.go line=263
time="2015-08-13T17:32:49Z" level=warning msg="Persistence layer appears dirty." file=persistence.go line=689
time="2015-08-13T17:32:49Z" level=warning msg="Starting crash recovery. Prometheus is inoperational until complete." file=crashrecovery.go line=39
time="2015-08-13T17:32:49Z" level=info msg="Scanning files." file=crashrecovery.go line=51

Is this because of #591 was closed without actually implementing sync()? Or something else?

How are you shutting down prometheus? You should send a SIGTERM, and then wait for it to terminate.

Indeed. This is what upstart is doing. Upstart will wait some amount of time, then send SIGKILL, but I confirmed via upstart debug logs that prometheus is exiting by itself.

That's very odd, can you port the logs of Prometheus at shutdown?

time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:23:46Z" level=warning msg="Sample ingestion resumed." file=storage.go line=546
time="2015-08-14T20:24:56Z" level=info msg="Checkpointing in-memory metrics and chunks..." file=persistence.go line=541

Is it possible that some of this is due to interactions with opentsdb? I have a ridiculous number (>100s) of goroutines that have been pending for 300+ minutes waiting for remote storage.
The service also dies occasionally due to OOM, on a machine with 180G of ram. This server is ingesting node_exporter metrics from ~200 machines, plus metrics from three custom exporters of which at most one of each type is installed on each machine that runs a node_exporter.
One wrinkle is that I wrote one of the custom exporters stupidly wrong, which causes it to crash every so often on each machine, causing prometheus to consider that endpoint UNHEALTHY, which might also add load? Not sure.
Are there docs anywhere describing the storage system architecture?

What storage flags are you running your Prometheus with. With that load you likely have to do at least some basic tuning.
Scraping the unhealthy targets should reduce the load if anything as we don't have to ingest their samples.
There are no detailed docs about the storage architecture. (There are vague plans to write something up eventually.) If you are interested, I'm happy to do a video call to give you an overview. Just ping me at<EMAIL_ADDRESS>

I pass 4 flags: 'alertmanager.url', 'config.file', 'storage.local.path' and 'storage.remote.opentsdb-url', so yeah, I'm sure some tuning is needed. What do you suggest?
I'll ping you off-thread as well.

http://prometheus.io/docs/operating/storage/ provides some information about storage flags.
Look at the storage.local.memory-chunks and storage.local.max-chunks-to-persist. The latter one is likely the reason why you are seeing those warnings. They basically say that the storage is not ready for appending so the samples are piling up. Eventually, new samples are dropped.

The remote storage is isolated from the local, so that if the remote storage if full it shouldn't affect things (and you'd see lots of Remote storage queue full, discarding sample.).

The service also dies occasionally due to OOM, on a machine with 180G of ram. This server is ingesting node_exporter metrics from ~200 machines, plus metrics from three custom exporters of which at most one of each type is installed on each machine that runs a node_exporter.

That'll be ~80k time series from the node exporters and I'm going to guess similar from the customs. That shouldn't present a problem for prometheus on what I presume is a very beefy machine. What's your scrape interval, how many samples/s are you ingesting and are you on SSD or HDD? It might be worthwhile to look at the node exporter consoles and prometheus console for the prometheus machine.

@fabxc According to my /metrics, the prometheus_local_storage_memory_series was 500,000+, so this makes sense. I've seen vast improvement from tuning these flags, thanks for the pointer.
@brian-brazil I do indeed see many of those messages. My scrape interval is 15s, I'm not sure how to get to the built in consoles (/consoles/prometheus_overview{.html,} doesn't work on my install at least). However,  (rate(prometheus_local_storage_ingested_samples_total[5m]) == 39674.668288367975), and I'm unfortunately on an HDD because of the hardware I was given for testing.
I've copied my /metrics on the prometheus server below, just for reference:
# HELP go_gc_duration_seconds A summary of the GC invocation durations.
# TYPE go_gc_duration_seconds summary
go_gc_duration_seconds{quantile="0"} 0.00023809000000000002
go_gc_duration_seconds{quantile="0.25"} 0.203586453
go_gc_duration_seconds{quantile="0.5"} 22.265724745
go_gc_duration_seconds{quantile="0.75"} 73.957165681
go_gc_duration_seconds{quantile="1"}<PHONE_NUMBER>54
go_gc_duration_seconds_sum 2461.877243197
go_gc_duration_seconds_count 61
# HELP go_goroutines Number of goroutines that currently exist.
# TYPE go_goroutines gauge
go_goroutines 1.668616e+06
# HELP http_request_duration_microseconds The HTTP request latencies in microseconds.
# TYPE http_request_duration_microseconds summary
http_request_duration_microseconds{handler="alerts",quantile="0.5"} NaN
http_request_duration_microseconds{handler="alerts",quantile="0.9"} NaN
http_request_duration_microseconds{handler="alerts",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="alerts"} 0
http_request_duration_microseconds_count{handler="alerts"} 0
http_request_duration_microseconds{handler="consoles",quantile="0.5"} NaN
http_request_duration_microseconds{handler="consoles",quantile="0.9"} NaN
http_request_duration_microseconds{handler="consoles",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="consoles"} 0
http_request_duration_microseconds_count{handler="consoles"} 0
http_request_duration_microseconds{handler="drop_series",quantile="0.5"} NaN
http_request_duration_microseconds{handler="drop_series",quantile="0.9"} NaN
http_request_duration_microseconds{handler="drop_series",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="drop_series"} 0
http_request_duration_microseconds_count{handler="drop_series"} 0
http_request_duration_microseconds{handler="federate",quantile="0.5"} NaN
http_request_duration_microseconds{handler="federate",quantile="0.9"} NaN
http_request_duration_microseconds{handler="federate",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="federate"} 0
http_request_duration_microseconds_count{handler="federate"} 0
http_request_duration_microseconds{handler="graph",quantile="0.5"} NaN
http_request_duration_microseconds{handler="graph",quantile="0.9"} NaN
http_request_duration_microseconds{handler="graph",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="graph"} 0
http_request_duration_microseconds_count{handler="graph"} 0
http_request_duration_microseconds{handler="heap",quantile="0.5"} NaN
http_request_duration_microseconds{handler="heap",quantile="0.9"} NaN
http_request_duration_microseconds{handler="heap",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="heap"} 0
http_request_duration_microseconds_count{handler="heap"} 0
http_request_duration_microseconds{handler="label_values",quantile="0.5"} NaN
http_request_duration_microseconds{handler="label_values",quantile="0.9"} NaN
http_request_duration_microseconds{handler="label_values",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="label_values"} 0
http_request_duration_microseconds_count{handler="label_values"} 0
http_request_duration_microseconds{handler="metrics",quantile="0.5"} NaN
http_request_duration_microseconds{handler="metrics",quantile="0.9"} NaN
http_request_duration_microseconds{handler="metrics",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="metrics"} 0
http_request_duration_microseconds_count{handler="metrics"} 0
http_request_duration_microseconds{handler="prometheus",quantile="0.5"} 10179.848
http_request_duration_microseconds{handler="prometheus",quantile="0.9"} 23372.595
http_request_duration_microseconds{handler="prometheus",quantile="0.99"} 26023.137
http_request_duration_microseconds_sum{handler="prometheus"} 1.2615919335999992e+07
http_request_duration_microseconds_count{handler="prometheus"} 294
http_request_duration_microseconds{handler="query",quantile="0.5"} NaN
http_request_duration_microseconds{handler="query",quantile="0.9"} NaN
http_request_duration_microseconds{handler="query",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="query"} 0
http_request_duration_microseconds_count{handler="query"} 0
http_request_duration_microseconds{handler="query_range",quantile="0.5"} NaN
http_request_duration_microseconds{handler="query_range",quantile="0.9"} NaN
http_request_duration_microseconds{handler="query_range",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="query_range"} 0
http_request_duration_microseconds_count{handler="query_range"} 0
http_request_duration_microseconds{handler="series",quantile="0.5"} NaN
http_request_duration_microseconds{handler="series",quantile="0.9"} NaN
http_request_duration_microseconds{handler="series",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="series"} 0
http_request_duration_microseconds_count{handler="series"} 0
http_request_duration_microseconds{handler="static",quantile="0.5"} NaN
http_request_duration_microseconds{handler="static",quantile="0.9"} NaN
http_request_duration_microseconds{handler="static",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="static"} 0
http_request_duration_microseconds_count{handler="static"} 0
http_request_duration_microseconds{handler="status",quantile="0.5"} NaN
http_request_duration_microseconds{handler="status",quantile="0.9"} NaN
http_request_duration_microseconds{handler="status",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="status"} 4.277188049000001e+06
http_request_duration_microseconds_count{handler="status"} 2
http_request_duration_microseconds{handler="version",quantile="0.5"} NaN
http_request_duration_microseconds{handler="version",quantile="0.9"} NaN
http_request_duration_microseconds{handler="version",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="version"} 0
http_request_duration_microseconds_count{handler="version"} 0
# HELP http_request_size_bytes The HTTP request sizes in bytes.
# TYPE http_request_size_bytes summary
http_request_size_bytes{handler="alerts",quantile="0.5"} NaN
http_request_size_bytes{handler="alerts",quantile="0.9"} NaN
http_request_size_bytes{handler="alerts",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="alerts"} 0
http_request_size_bytes_count{handler="alerts"} 0
http_request_size_bytes{handler="consoles",quantile="0.5"} NaN
http_request_size_bytes{handler="consoles",quantile="0.9"} NaN
http_request_size_bytes{handler="consoles",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="consoles"} 0
http_request_size_bytes_count{handler="consoles"} 0
http_request_size_bytes{handler="drop_series",quantile="0.5"} NaN
http_request_size_bytes{handler="drop_series",quantile="0.9"} NaN
http_request_size_bytes{handler="drop_series",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="drop_series"} 0
http_request_size_bytes_count{handler="drop_series"} 0
http_request_size_bytes{handler="federate",quantile="0.5"} NaN
http_request_size_bytes{handler="federate",quantile="0.9"} NaN
http_request_size_bytes{handler="federate",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="federate"} 0
http_request_size_bytes_count{handler="federate"} 0
http_request_size_bytes{handler="graph",quantile="0.5"} NaN
http_request_size_bytes{handler="graph",quantile="0.9"} NaN
http_request_size_bytes{handler="graph",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="graph"} 0
http_request_size_bytes_count{handler="graph"} 0
http_request_size_bytes{handler="heap",quantile="0.5"} NaN
http_request_size_bytes{handler="heap",quantile="0.9"} NaN
http_request_size_bytes{handler="heap",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="heap"} 0
http_request_size_bytes_count{handler="heap"} 0
http_request_size_bytes{handler="label_values",quantile="0.5"} NaN
http_request_size_bytes{handler="label_values",quantile="0.9"} NaN
http_request_size_bytes{handler="label_values",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="label_values"} 0
http_request_size_bytes_count{handler="label_values"} 0
http_request_size_bytes{handler="metrics",quantile="0.5"} NaN
http_request_size_bytes{handler="metrics",quantile="0.9"} NaN
http_request_size_bytes{handler="metrics",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="metrics"} 0
http_request_size_bytes_count{handler="metrics"} 0
http_request_size_bytes{handler="prometheus",quantile="0.5"} 291
http_request_size_bytes{handler="prometheus",quantile="0.9"} 291
http_request_size_bytes{handler="prometheus",quantile="0.99"} 291
http_request_size_bytes_sum{handler="prometheus"} 85554
http_request_size_bytes_count{handler="prometheus"} 294
http_request_size_bytes{handler="query",quantile="0.5"} NaN
http_request_size_bytes{handler="query",quantile="0.9"} NaN
http_request_size_bytes{handler="query",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="query"} 0
http_request_size_bytes_count{handler="query"} 0
http_request_size_bytes{handler="query_range",quantile="0.5"} NaN
http_request_size_bytes{handler="query_range",quantile="0.9"} NaN
http_request_size_bytes{handler="query_range",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="query_range"} 0
http_request_size_bytes_count{handler="query_range"} 0
http_request_size_bytes{handler="series",quantile="0.5"} NaN
http_request_size_bytes{handler="series",quantile="0.9"} NaN
http_request_size_bytes{handler="series",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="series"} 0
http_request_size_bytes_count{handler="series"} 0
http_request_size_bytes{handler="static",quantile="0.5"} NaN
http_request_size_bytes{handler="static",quantile="0.9"} NaN
http_request_size_bytes{handler="static",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="static"} 0
http_request_size_bytes_count{handler="static"} 0
http_request_size_bytes{handler="status",quantile="0.5"} NaN
http_request_size_bytes{handler="status",quantile="0.9"} NaN
http_request_size_bytes{handler="status",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="status"} 1126
http_request_size_bytes_count{handler="status"} 2
http_request_size_bytes{handler="version",quantile="0.5"} NaN
http_request_size_bytes{handler="version",quantile="0.9"} NaN
http_request_size_bytes{handler="version",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="version"} 0
http_request_size_bytes_count{handler="version"} 0
# HELP http_requests_total Total number of HTTP requests made.
# TYPE http_requests_total counter
http_requests_total{code="200",handler="prometheus",method="get"} 294
http_requests_total{code="200",handler="status",method="get"} 2
# HELP http_response_size_bytes The HTTP response sizes in bytes.
# TYPE http_response_size_bytes summary
http_response_size_bytes{handler="alerts",quantile="0.5"} NaN
http_response_size_bytes{handler="alerts",quantile="0.9"} NaN
http_response_size_bytes{handler="alerts",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="alerts"} 0
http_response_size_bytes_count{handler="alerts"} 0
http_response_size_bytes{handler="consoles",quantile="0.5"} NaN
http_response_size_bytes{handler="consoles",quantile="0.9"} NaN
http_response_size_bytes{handler="consoles",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="consoles"} 0
http_response_size_bytes_count{handler="consoles"} 0
http_response_size_bytes{handler="drop_series",quantile="0.5"} NaN
http_response_size_bytes{handler="drop_series",quantile="0.9"} NaN
http_response_size_bytes{handler="drop_series",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="drop_series"} 0
http_response_size_bytes_count{handler="drop_series"} 0
http_response_size_bytes{handler="federate",quantile="0.5"} NaN
http_response_size_bytes{handler="federate",quantile="0.9"} NaN
http_response_size_bytes{handler="federate",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="federate"} 0
http_response_size_bytes_count{handler="federate"} 0
http_response_size_bytes{handler="graph",quantile="0.5"} NaN
http_response_size_bytes{handler="graph",quantile="0.9"} NaN
http_response_size_bytes{handler="graph",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="graph"} 0
http_response_size_bytes_count{handler="graph"} 0
http_response_size_bytes{handler="heap",quantile="0.5"} NaN
http_response_size_bytes{handler="heap",quantile="0.9"} NaN
http_response_size_bytes{handler="heap",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="heap"} 0
http_response_size_bytes_count{handler="heap"} 0
http_response_size_bytes{handler="label_values",quantile="0.5"} NaN
http_response_size_bytes{handler="label_values",quantile="0.9"} NaN
http_response_size_bytes{handler="label_values",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="label_values"} 0
http_response_size_bytes_count{handler="label_values"} 0
http_response_size_bytes{handler="metrics",quantile="0.5"} NaN
http_response_size_bytes{handler="metrics",quantile="0.9"} NaN
http_response_size_bytes{handler="metrics",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="metrics"} 0
http_response_size_bytes_count{handler="metrics"} 0
http_response_size_bytes{handler="prometheus",quantile="0.5"} 3057
http_response_size_bytes{handler="prometheus",quantile="0.9"} 3096
http_response_size_bytes{handler="prometheus",quantile="0.99"} 3102
http_response_size_bytes_sum{handler="prometheus"} 877660
http_response_size_bytes_count{handler="prometheus"} 294
http_response_size_bytes{handler="query",quantile="0.5"} NaN
http_response_size_bytes{handler="query",quantile="0.9"} NaN
http_response_size_bytes{handler="query",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="query"} 0
http_response_size_bytes_count{handler="query"} 0
http_response_size_bytes{handler="query_range",quantile="0.5"} NaN
http_response_size_bytes{handler="query_range",quantile="0.9"} NaN
http_response_size_bytes{handler="query_range",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="query_range"} 0
http_response_size_bytes_count{handler="query_range"} 0
http_response_size_bytes{handler="series",quantile="0.5"} NaN
http_response_size_bytes{handler="series",quantile="0.9"} NaN
http_response_size_bytes{handler="series",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="series"} 0
http_response_size_bytes_count{handler="series"} 0
http_response_size_bytes{handler="static",quantile="0.5"} NaN
http_response_size_bytes{handler="static",quantile="0.9"} NaN
http_response_size_bytes{handler="static",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="static"} 0
http_response_size_bytes_count{handler="static"} 0
http_response_size_bytes{handler="status",quantile="0.5"} NaN
http_response_size_bytes{handler="status",quantile="0.9"} NaN
http_response_size_bytes{handler="status",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="status"} 745415
http_response_size_bytes_count{handler="status"} 2
http_response_size_bytes{handler="version",quantile="0.5"} NaN
http_response_size_bytes{handler="version",quantile="0.9"} NaN
http_response_size_bytes{handler="version",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="version"} 0
http_response_size_bytes_count{handler="version"} 0
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 7151.74
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1024
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 153
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 1.05398337536e+11
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.4398246244e+09
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 1.06608111616e+11
# HELP prometheus_build_info A metric with a constant '1' value labeled by version, revision, and branch from which Prometheus was built.
# TYPE prometheus_build_info gauge
prometheus_build_info{branch="master",revision="7f9a8de",version="0.15.1"} 1
# HELP prometheus_configuration_attempts number of times a configuration reload was attempted, failed or succeeded.
# TYPE prometheus_configuration_attempts counter
prometheus_configuration_attempts{state="attempted"} 1
prometheus_configuration_attempts{state="succeeded"} 1
# HELP prometheus_dns_sd_lookup_failures_total The number of DNS-SD lookup failures.
# TYPE prometheus_dns_sd_lookup_failures_total counter
prometheus_dns_sd_lookup_failures_total 0
# HELP prometheus_dns_sd_lookups_total The number of DNS-SD lookups.
# TYPE prometheus_dns_sd_lookups_total counter
prometheus_dns_sd_lookups_total 0
# HELP prometheus_evaluator_duration_milliseconds The duration for all evaluations to execute.
# TYPE prometheus_evaluator_duration_milliseconds summary
prometheus_evaluator_duration_milliseconds{quantile="0.01"} 9860
prometheus_evaluator_duration_milliseconds{quantile="0.05"} 9860
prometheus_evaluator_duration_milliseconds{quantile="0.5"} 17521
prometheus_evaluator_duration_milliseconds{quantile="0.9"} 21991
prometheus_evaluator_duration_milliseconds{quantile="0.99"} 26634
prometheus_evaluator_duration_milliseconds_sum 6.509127e+06
prometheus_evaluator_duration_milliseconds_count 245
# HELP prometheus_local_storage_checkpoint_duration_milliseconds The duration (in milliseconds) it took to checkpoint in-memory metrics and head chunks.
# TYPE prometheus_local_storage_checkpoint_duration_milliseconds gauge
prometheus_local_storage_checkpoint_duration_milliseconds 1.011040272601e+06
# HELP prometheus_local_storage_chunk_ops_total The total number of chunk operations by their type.
# TYPE prometheus_local_storage_chunk_ops_total counter
prometheus_local_storage_chunk_ops_total{type="clone"} 725
prometheus_local_storage_chunk_ops_total{type="create"} 3.217324e+06
prometheus_local_storage_chunk_ops_total{type="load"} 138
prometheus_local_storage_chunk_ops_total{type="persist"} 637281
prometheus_local_storage_chunk_ops_total{type="pin"} 71882
prometheus_local_storage_chunk_ops_total{type="transcode"} 1.547023e+06
prometheus_local_storage_chunk_ops_total{type="unpin"} 71882
# HELP prometheus_local_storage_chunkdesc_ops_total The total number of chunk descriptor operations by their type.
# TYPE prometheus_local_storage_chunkdesc_ops_total counter
prometheus_local_storage_chunkdesc_ops_total{type="evict"} 841470
prometheus_local_storage_chunkdesc_ops_total{type="load"} 1.010165e+06
# HELP prometheus_local_storage_chunks_to_persist The current number of chunks waiting for persistence.
# TYPE prometheus_local_storage_chunks_to_persist gauge
prometheus_local_storage_chunks_to_persist 2.573101e+06
# HELP prometheus_local_storage_fingerprint_mappings_total The total number of fingerprints being mapped to avoid collisions.
# TYPE prometheus_local_storage_fingerprint_mappings_total counter
prometheus_local_storage_fingerprint_mappings_total 0
# HELP prometheus_local_storage_inconsistencies_total A counter incremented each time an inconsistency in the local storage is detected. If this is greater zero, restart the server as soon as possible.
# TYPE prometheus_local_storage_inconsistencies_total counter
prometheus_local_storage_inconsistencies_total 0
# HELP prometheus_local_storage_indexing_batch_duration_milliseconds Quantiles for batch indexing duration in milliseconds.
# TYPE prometheus_local_storage_indexing_batch_duration_milliseconds summary
prometheus_local_storage_indexing_batch_duration_milliseconds{quantile="0.5"} 16448.477141
prometheus_local_storage_indexing_batch_duration_milliseconds{quantile="0.9"} 17207.785174
prometheus_local_storage_indexing_batch_duration_milliseconds{quantile="0.99"} 17207.785174
prometheus_local_storage_indexing_batch_duration_milliseconds_sum 1.4983375939149999e+06
prometheus_local_storage_indexing_batch_duration_milliseconds_count 71
# HELP prometheus_local_storage_indexing_batch_sizes Quantiles for indexing batch sizes (number of metrics per batch).
# TYPE prometheus_local_storage_indexing_batch_sizes summary
prometheus_local_storage_indexing_batch_sizes{quantile="0.5"} 44
prometheus_local_storage_indexing_batch_sizes{quantile="0.9"} 70
prometheus_local_storage_indexing_batch_sizes{quantile="0.99"} 70
prometheus_local_storage_indexing_batch_sizes_sum 1.571379e+06
prometheus_local_storage_indexing_batch_sizes_count 71
# HELP prometheus_local_storage_indexing_queue_capacity The capacity of the indexing queue.
# TYPE prometheus_local_storage_indexing_queue_capacity gauge
prometheus_local_storage_indexing_queue_capacity 16384
# HELP prometheus_local_storage_indexing_queue_length The number of metrics waiting to be indexed.
# TYPE prometheus_local_storage_indexing_queue_length gauge
prometheus_local_storage_indexing_queue_length 55
# HELP prometheus_local_storage_ingested_samples_total The total number of samples ingested.
# TYPE prometheus_local_storage_ingested_samples_total counter
prometheus_local_storage_ingested_samples_total 1.78882882e+08
# HELP prometheus_local_storage_invalid_preload_requests_total The total number of preload requests referring to a non-existent series. This is an indication of outdated label indexes.
# TYPE prometheus_local_storage_invalid_preload_requests_total counter
prometheus_local_storage_invalid_preload_requests_total 0
# HELP prometheus_local_storage_maintain_series_duration_milliseconds The duration (in milliseconds) it took to perform maintenance on a series.
# TYPE prometheus_local_storage_maintain_series_duration_milliseconds summary
prometheus_local_storage_maintain_series_duration_milliseconds{location="memory",quantile="0.5"} NaN
prometheus_local_storage_maintain_series_duration_milliseconds{location="memory",quantile="0.9"} NaN
prometheus_local_storage_maintain_series_duration_milliseconds{location="memory",quantile="0.99"} NaN
prometheus_local_storage_maintain_series_duration_milliseconds_sum{location="memory"}<PHONE_NUMBER>960018
prometheus_local_storage_maintain_series_duration_milliseconds_count{location="memory"} 204810
# HELP prometheus_local_storage_max_chunks_to_persist The maximum number of chunks that can be waiting for persistence before sample ingestion will stop.
# TYPE prometheus_local_storage_max_chunks_to_persist gauge
prometheus_local_storage_max_chunks_to_persist 3.146466e+06
# HELP prometheus_local_storage_memory_chunkdescs The current number of chunk descriptors in memory.
# TYPE prometheus_local_storage_memory_chunkdescs gauge
prometheus_local_storage_memory_chunkdescs 1.9584554e+07
# HELP prometheus_local_storage_memory_chunks The current number of chunks in memory, excluding cloned chunks (i.e. chunks without a descriptor).
# TYPE prometheus_local_storage_memory_chunks gauge
prometheus_local_storage_memory_chunks 3.109625e+06
# HELP prometheus_local_storage_memory_series The current number of series in memory.
# TYPE prometheus_local_storage_memory_series gauge
prometheus_local_storage_memory_series 691046
# HELP prometheus_local_storage_out_of_order_samples_total The total number of samples that were discarded because their timestamps were at or before the last received sample for a series.
# TYPE prometheus_local_storage_out_of_order_samples_total counter
prometheus_local_storage_out_of_order_samples_total 0
# HELP prometheus_local_storage_persist_errors_total The total number of errors while persisting chunks.
# TYPE prometheus_local_storage_persist_errors_total counter
prometheus_local_storage_persist_errors_total 0
# HELP prometheus_local_storage_series_ops_total The total number of series operations by their type.
# TYPE prometheus_local_storage_series_ops_total counter
prometheus_local_storage_series_ops_total{type="archive"} 10
prometheus_local_storage_series_ops_total{type="create"} 4071
prometheus_local_storage_series_ops_total{type="maintenance_in_memory"} 204810
prometheus_local_storage_series_ops_total{type="unarchive"} 8
# HELP prometheus_notifications_latency_milliseconds Latency quantiles for sending alert notifications (not including dropped notifications).
# TYPE prometheus_notifications_latency_milliseconds summary
prometheus_notifications_latency_milliseconds{quantile="0.5"} 812
prometheus_notifications_latency_milliseconds{quantile="0.9"} 1201
prometheus_notifications_latency_milliseconds{quantile="0.99"} 1338
prometheus_notifications_latency_milliseconds_sum 246021
prometheus_notifications_latency_milliseconds_count 244
# HELP prometheus_notifications_queue_capacity The capacity of the alert notifications queue.
# TYPE prometheus_notifications_queue_capacity gauge
prometheus_notifications_queue_capacity 100
# HELP prometheus_notifications_queue_length The number of alert notifications in the queue.
# TYPE prometheus_notifications_queue_length gauge
prometheus_notifications_queue_length 0
# HELP prometheus_remote_storage_queue_capacity The capacity of the queue of samples to be sent to the remote storage.
# TYPE prometheus_remote_storage_queue_capacity gauge
prometheus_remote_storage_queue_capacity{type="opentsdb"} 102400
# HELP prometheus_remote_storage_queue_length The number of processed samples queued to be sent to the remote storage.
# TYPE prometheus_remote_storage_queue_length gauge
prometheus_remote_storage_queue_length{type="opentsdb"} 0
# HELP prometheus_remote_storage_sent_latency_milliseconds Latency quantiles for sending sample batches to the remote storage.
# TYPE prometheus_remote_storage_sent_latency_milliseconds summary
prometheus_remote_storage_sent_latency_milliseconds{type="opentsdb",quantile="0.5"} 738
prometheus_remote_storage_sent_latency_milliseconds{type="opentsdb",quantile="0.9"} 1326
prometheus_remote_storage_sent_latency_milliseconds{type="opentsdb",quantile="0.99"} 10252
prometheus_remote_storage_sent_latency_milliseconds_sum{type="opentsdb"} 6.8996348e+07
prometheus_remote_storage_sent_latency_milliseconds_count{type="opentsdb"} 50551
# HELP prometheus_remote_storage_sent_samples_total Total number of processed samples to be sent to remote storage.
# TYPE prometheus_remote_storage_sent_samples_total counter
prometheus_remote_storage_sent_samples_total{result="dropped",type="opentsdb"} 7.011685e+06
prometheus_remote_storage_sent_samples_total{result="failure",type="opentsdb"} 13200
prometheus_remote_storage_sent_samples_total{result="success",type="opentsdb"} 5.0419e+06
# HELP prometheus_rule_evaluation_duration_milliseconds The duration for a rule to execute.
# TYPE prometheus_rule_evaluation_duration_milliseconds summary
prometheus_rule_evaluation_duration_milliseconds{rule_type="alerting",quantile="0.5"} 13812
prometheus_rule_evaluation_duration_milliseconds{rule_type="alerting",quantile="0.9"} 18568
prometheus_rule_evaluation_duration_milliseconds{rule_type="alerting",quantile="0.99"} 19260
prometheus_rule_evaluation_duration_milliseconds_sum{rule_type="alerting"} 5.335308e+06
prometheus_rule_evaluation_duration_milliseconds_count{rule_type="alerting"} 245
# HELP prometheus_rule_evaluation_failures_total The total number of rule evaluation failures.
# TYPE prometheus_rule_evaluation_failures_total counter
prometheus_rule_evaluation_failures_total 0
# HELP prometheus_target_interval_length_seconds Actual intervals between scrapes.
# TYPE prometheus_target_interval_length_seconds summary
prometheus_target_interval_length_seconds{interval="15s",quantile="0.01"} 5.092907957
prometheus_target_interval_length_seconds{interval="15s",quantile="0.05"} 7.742574289
prometheus_target_interval_length_seconds{interval="15s",quantile="0.5"} 19.019487486
prometheus_target_interval_length_seconds{interval="15s",quantile="0.9"}<PHONE_NUMBER>5
prometheus_target_interval_length_seconds{interval="15s",quantile="0.99"}<PHONE_NUMBER>27
prometheus_target_interval_length_seconds_sum{interval="15s"} 1.9645108370758814e+06
prometheus_target_interval_length_seconds_count{interval="15s"} 80409

That's 10X the samples/s of the next biggest HDD prometheus we're aware of. What does disk i/o utilisation look like (iostat- x)?

Linux 3.19.5-145.el6REDACTED (REDACTED) 	08/17/2015 	_x86_64_	(24 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           3.96    0.00    0.71    0.07    0.00   95.26

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
sda               0.03    85.94    4.04   76.01    42.26  5907.25    74.32     1.84   22.94   0.28   2.23
dm-0              0.00     0.00    4.07  162.35    42.24  5907.25    35.75     7.89   47.42   0.13   2.23
dm-1              0.00     0.00    0.00    0.00     0.01     0.00     8.84     0.00    0.39   0.38   0.00

Also, that consoles link doesn't work (open consoles/prometheus.html: no such file or directory), I complied with just make, did I need to bundle the consoles directory alongside, or should it just work via embedding?

Disk seems fine, and you're using around one core. Have you set GOMAXPROCS?
Yes, you need to copy the consoles and console_libraries directories.

OMG, I entirely forgot about GOMAXPROCS.

I'm still getting the issue where storage is marked dirty every time, but since that seems to be more likely a problem with my specific setup, I'm closing this issue. Thanks for the help!


Game manager code rework

Something is wrong with this version. Sometimes Errors randomly popup and the error message is very difficult to read


ZoneAwareError is 15-20x slower than native, should lazy-evaluate "stack"

Getting a stack trace can be an expensive operation, and both Firefox and Chrome/V8 (haven't checked IE/Edge) optimize it by formatting the unstructured stack trace of an error on demand, the first time the stack property is accessed (https://github.com/v8/v8/wiki/Stack-Trace-API#customizing-stack-traces).
When building instrumentation tooling, I use this to minimize the overhead of capturing the stack trace using new Error() and then evaluate its stack property if and when needed. Unfortunately, ZoneAwareError does the trace evaluation and formatting in its constructor, so it ends up a lot slower, both from invoking the native error's formatting, and Zone.js's own overhead. I have also noticed it resulting in increased memory pressure, leading to more frequent GC pauses:

(The first half is running new NativeError(), the second is running new Error().)
Benchmark demonstrating the issue - https://jsperf.com/zoneawareerror.
Note that this runs the benchmark with an unrealistically shallow call stack. The real life impact in a complex application is likely to be more pronounced.
Is it possible to make it evaluate and rewrite the stack on demand?

@mleibman , so your requirement is

use native Error instead of zone patched one?
use zone patched one, but format stack on demand?

I can use the native error as a workaround, though there doesn't seem to be a formal way of getting it (api.symbol('Error') is private, and window['__zone_symbol__Error'] is hacky and not guaranteed to work).
Ideally, the zone patched one should not incur any additional overhead in the constructor, and do all its work on demand in the stack accessor. Using the zone patched error is preferable since it filters out the blacklisted zone frames and adds zone information for each one.

@mleibman ,

if you want to use native error, you can update to latest version of zone.js, and by default,
node_modules\dist\zone-error.js is not loaded, so you will get native Error automatically.
if you use some old version of zone.js, you can set __Zone_disable_Error = true; in index.html before loading zone.js.
if you want to use zone patched Error, the blacklisted zone frame filter can be attached on demand, but zone information on stack frame can't be attached on demand, because the zone also keep a stack frame which only hold correct information when Error is constructed.

1 & 2 aren't really an option for me.
But it seems that we can still have our cake and eat it too. I may be reading the code wrong, but there doesn't seem to be anything in the ZoneAwareError constructor that needs to actually access the stack property right away. The zone information for the current stack frame (as read in let zoneFrame = api.currentZoneFrame() can be captured in the constructor and used on-demand later. What do you think?
Also, is there a better way to access the native Error other than using window['__zone_symbol__Error']?

yes, we can keep the zoneFrame in Error constructor and build the stack on demand, but not only keep the zoneFrame itself, but also all it's ancestors.  I will try to create a patch.
to access native Error, you need to access window['__zone_symbol__Error'] or window[Zone.__symbol__('Error')], what is your suggestion?

@JiaLiPassion,
If you capture the currentZoneFrame, does that not give you access to all of its ancestors too via the currentZoneFrame.parent? It doesn't seem like you have to do anything special there, but again, I'm not familiar with the code, so this is all based on just reading through it.
The reason I'm asking about the proper way to access the native Error is that I'm concerned that it may stop working at some point. The api.symbol() (also referenced as Zone.__symbol__) looks like a shim for ES6 Symbol functionality that just prepends it with '__zone_symbol__' until ES6 symbols are universally supported. Right now, the shim is used regardless of whether the environment supports ES6 symbols, but if Zone switches to actually using native ES6 symbols at some point, window['__zone_symbol__Error'] will stop working. The other problem is that the '__zone_symbol__' prefix is an internal implementation detail, and Zone.js makes no guarantees that it won't change.

@mleibman , yes, the currentZoneFrame will include all it's ancestors information in Error constructor, but if we do so, it will keep all zone information in Error and may cause memory leak. I will think about it again.
And about the native Error access, I am not sure it will change or not. Maybe we should provide a getNative method.

Thanks!


Lag spikes using shift while crafting.

This error occurs one time after each server restart. If you shift click while crafting multiple blocks massive lag spike happens and you get an error in the console. It has to do something with CraftItemEvent.
Tested this without the plugin. it doesn't happen, it is caused by Jobs.

[11:55:25 ERROR]: (org.bukkit.craftbukkit.v1_17_R1.legacy.CraftLegacy:259) Initializing Legacy Material Support. Unless you have legacy plugins and/or data this is a bug!

https://prnt.sc/1arui28

Jobs version: <IP_ADDRESS>
Server Type:Purpur-1265
Server Version: 1.17.1

509ac682adef8ec64fde0912722bd688e430a9ff

still isn't fixed on latest version available
[22:17:45 ERROR]: (org.bukkit.craftbukkit.v1_17_R1.legacy.CraftLegacy:259) Initializing Legacy Material Support. Unless you have legacy plugins and/or data this is a bug!
[22:17:48 INFO]: [⚡] Tick #3915 lasted 3225.96 ms. (6351.87% increase from avg)

Jobs version: <IP_ADDRESS>
Server Type:Purpur-1267
Server Version: 1.17.1


Update org-mode snippets to use lowercase for blocks

It seems that org is transitioning to use lowercase on blocks, and that early last year, yasnippet adopted this in their org-mode templates.
Could you update so that Doom is providing these? Right now, there are a confusing mix.
https://github.com/AndreaCrotti/yasnippet-snippets/issues/303

Sorry for the tremendously late response. As of #51 this should be fixed. Thanks for bringing it to my attention!


Force gem platform to be something else

I have sys-proctable in my Gemfile. This works fine with MRI but causes issues with JRuby where it is looking for a "java" platform version which doesn't exist, but in the case of Windows the win-x86 one works just fine. Is there a way to force bundler to allow this gem to work?

If there is no JRuby version, I would expect Bundler to try to install the pure ruby version. It doesn't?

Bundler does. Unfortunately the versions of sys-proctable for the past 4 years have all been platform-specific, so when it tries to install a generic version it installs one from 4 years ago. See here: http://rubygems.org/gems/sys-proctable/versions
The x86-mswin32-60 version works fine with JRuby, so I want there to be a way for me to basically override what Bundler thinks is best for me. Even if the answer in this case is "sys-proctable should package a generic one too," I don't want to be forced to not use Bundler every time this happens. Quite annoying.
What I'm wondering is if there is a way or there could be a way to basically say "no, bundler, I am telling you to do this, I realize you think you're right"

Yup, the way to do that is fork the repo, edit the gemspec, and use :git. That way you get a gemspec that says the right thing.
On Nov 24, 2011, at 8:17 PM, Mitchell<EMAIL_ADDRESS>wrote:

Bundler does. Unfortunately the versions of sys-proctable for the past 4 years have all been platform-specific, so when it tries to install a generic version it installs one from 4 years ago. See here: http://rubygems.org/gems/sys-proctable/versions
The x86-mswin32-60 version works fine with JRuby, so I want there to be a way for me to basically override what Bundler thinks is best for me. Even if the answer in this case is "sys-proctable should package a generic one too," I don't want to be forced to not use Bundler every time this happens. Quite annoying.
What I'm wondering is if there is a way or there could be a way to basically say "no, bundler, I am telling you to do this, I realize you think you're right"

Reply to this email directly or view it on GitHub:
https://github.com/carlhuda/bundler/issues/1550#issuecomment-2871204

Ouch, fair enough :(


Update proj1-part2-README-zh_CN.md: add example about how to run single test

I think we need to add example about how to run single test in proj1-part2-README-zh_CN.md, because this is an important information to help beginners to debug tinysql on single test.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thx!


imperfectproduce.com

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

  Provide the following infos properly, which will help us to resolve your issue quickly.

Issue(s):
Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x]
You can select more than one category of issues if you need to!

[x] Whitelist
[ ] Blacklist
[ ] App Broken
[ ] Website Broken
[ ] Request
[ ] Other Issue

Pack(s):
Write the name of the pack(s) you are using.

Pack(s) Name: blu

Extension(s):
Also name the extension(s) if you are using any. If you don't then leave it blank.

Extension(s) Name:

Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.

Domain(s):

djnf6e5yyirys.cloudfront.net
friendbuy.com
pt.friendbuy.com
cdn1.friendbuy.com
cdn.friendbuy.com

Your Config:
Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list.
Make sure you are running Energized Protection Service only.

Client:

Version:

Details:
Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Your Issue Detail:
Breaks page
https://www.imperfectproduce.com/account/referrals
Need account

Thank you for making Energized Protection great with your kind help!

A project by Ador with ❤

@AdroitAdorKhan djnf6e5yyirys.cloudfront.net is still blocked and breaks the site. Please whitelist.


expose NodeView to JavaScript

Baby steps towards #142

Rebased onto master to pull in new FileSource changes
Backtracked the mbgl setView functionality to a branch off of v0.4.1

https://github.com/mapbox/mapbox-gl-native/tree/set-view-v0.4.1

Fixed up the OpenGL context was already current errors by retaining the current NodeView on a NodeMap as a v8::Persistent (the garbage collector was trying to destroy active views previously)

I'm still seeing Error: Request has already been responded to, or was canceled (actually indicating that nodeRequest->resource is empty) on occasion, although very rarely - I'd like to track this down here before moving further.
/cc @tmpsantos

Okay, I think I've tracked down the problem, but I don't quite know the right solution.
When NodeRequest::cancel is called, it resets the resource pointer, but I think it doesn't always kill the request or remove it from the pending request queue in time. When the request completes and attempts to call NodeRequest::Respond, it's missing a resource, and throws an error.
Could there be a race condition in NodeFileSource::cancel?

Naive debugging looks like this:
ok 922 actual matches expected
# raster-brightness function
REQUEST CREATE
REQUEST CREATE
REQUEST CREATE
mbgl::Request::cancel
REQUEST CREATE
mbgl::Request::destruct passed asserts
mbgl::Request::cancel
mbgl::Request::destruct passed asserts
mbgl::RequReEsQtU:E:ScTa nCcReElA
TEm
bgl::Request::destruct passed asserts
mbgl::Request::RcEaQnUcEeSlT
 CmRbEgAlT:E:
Request::destruct passed asserts
REQUEST CREATE
REQUEST CREATE
REQUEST CREATE
REQUEST CREATE
REQUEST CANCEL
REQUEST CANCEL
REQUEST CANCEL
REQUEST CANCEL

/Users/mikemorris/gyp/node-mapbox-gl-native/test/render.test.js:45
                req.respond(err, { data: data });
                    ^
Error: Request has already been responded to, or was canceled.
    at /Users/mikemorris/gyp/node-mapbox-gl-native/test/render.test.js:45:21
    at fs.js:208:20
    at Object.oncomplete (fs.js:108:15)
Process 7389 exited with status = 8 (0x00000008)

So it looks like the underlying mbgl::Request is canceled and destroyed, but the NodeRequest is still around and eventually attempts to respond even though it has been "canceled" (had its resource pointer reset).

Punting on this in favor of #147, may revisit later.


fix(pipe): package resolving error

name: pull request
about: submit changes to the project
title: "[pr] "
labels: ''
assignees: ''

description
fixed the package resolving error,
also when pipe downloading fails in some condition the temp directory remains in directory, fixed it!!
related issue: #919
/claim #919
how to test
add a few steps to test the pr in the most time efficient way.

if relevant add screenshots or screen captures to prove that this PR works to save us time.
if you think it can take more than 30 mins for us to review, we will pay between $20 and $200 for someone to review it for us, just ask in the pr.

nice !!
/approve


Error compiling: executing make deps

Have you read a contributing guide?

[X] I have read CONTRIBUTING.md
[X] I have searched the existing issues and didn't find any that were similar
[X] I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior
Showing the errors attached in logs.
Expected Behavior
Executing make deps install/compile the dependencies. It looks like there is a conflict with the roundupsize function.
Steps To Reproduce
clone the repository
make deps
Environment
- OS:Unbuntu
- Version: 22.04
- Golang version: 1.22

Anything else?
go mod download
go build -o deps github.com/ahmetb/govvv
runtime
/usr/local/go/src/runtime/msize_allocheaders.go:16:6: roundupsize redeclared in this block
/usr/local/go/src/runtime/msize.go:13:6: other declaration of roundupsize
/usr/local/go/src/runtime/map.go:357:25: too many arguments in call to roundupsize
have (uintptr, bool)
want (uintptr)
/usr/local/go/src/runtime/slice.go:191:41: too many arguments in call to roundupsize
have (uintptr, bool)
want (uintptr)
/usr/local/go/src/runtime/slice.go:197:56: too many arguments in call to roundupsize
have (uintptr, bool)
want (uintptr)
/usr/local/go/src/runtime/slice.go:210:48: too many arguments in call to roundupsize
have (uintptr, bool)
want (uintptr)
/usr/local/go/src/runtime/slice.go:218:32: too many arguments in call to roundupsize
have (uintptr, bool)
want (uintptr)
/usr/local/go/src/runtime/string.go:273:36: too many arguments in call to roundupsize
have (uintptr, bool)
want (uintptr)
/usr/local/go/src/runtime/string.go:288:38: too many arguments in call to roundupsize
have (uintptr, bool)
want (uintptr)
make: *** [Makefile:25: deps] Error 1

Noticed is an error of golang, closing


Docs missing fh-matplotlib dependency

Go to docs/apps
python main.py throws this error:

❯ python main.py
Traceback (most recent call last):
  File "/Users/drg/answer/fh-frankenui/docs/app/main.py", line 41, in <module>
    from dashboard import dashboard_homepage
  File "/Users/drg/answer/fh-frankenui/docs/app/dashboard.py", line 16, in <module>
    from fh_matplotlib import matplotlib2fasthtml
ModuleNotFoundError: No module named 'fh_matplotlib'

docs/app/requirements.txt isn't specified or documented anywhere.

I'm reworking how docs are done generally to try to make it more friendly to contributors.  I've simplified the docs to be a regular app with py files, and updated the contributing guide.  I think there's more I need to do here, but hopefully contributing will get easier and easier so please let me know all the stumbling blocks you see :)


Several improvement for mpirun.gpu script.

Add CUDA MPS enable option (-m)
Fixed bug

Thank you @yhirokawa san for contribution. I have confirmed this code works on the SYSTEM-B@ISSP.


Add more documentation

Documentation for the following subheadings:

enum
switch
while
for
if
goto
defer
Functions

Great!

I pushed this live. Thanks again! this is a huge amount of content.


Tabs fail: JSON value '(1,1,1, ...)' of type NSMutableArray cannot be converted to BOOL

Hi everyone.
I'm trying to use Animated.View in Tabs renderTabBar param and getting this error

and this is my code

"react-native": "0.63.2"
"native-base": "^2.13.8"
Everything is working on "react-native": "0.61.5"

Hi @iqorlobanov , can you provide minimal code reproduction on snack for the same?

I also experience this.

Also, by passing {...props} to ScrollableTab is causing the error if you're using <Animated.View>.
example:
<Tabs
  renderTabBar={props => (props &&
      <Animated.View>
        <ScrollableTab { ...props } />
      </Animated.View>
    )
  }
>
  <Tab heading="Tab 1">
    <View>
      <Text>Tab 1</Text>
    </View>
  </Tab>
  <Tab heading="Tab 2">
    <View>
      <Text>Tab 2</Text>
    </View>
  </Tab>
</Tabs>

I was facing the same issue with Animated.View
I wrapped it in <> </>  and it fixed the issue for me.

@iqorlobanov
I was facing the same issue with Animated.View
I wrapped it in <> </>  and it fixed the issue for me.

Thanks! It works :)


[packaging] add basic deb packaging

@vellamike the error above is coming from the make install command. looks like docs wasn't built, so install is failing since it's trying to copy an html folder. Let me fix that separately (doc generation shouldn't be required for installation)

@vellamike the error above is coming from the make install command. looks like docs wasn't built, so install is failing since it's trying to copy an html folder. Let me fix that separately (doc generation shouldn't be required for installation)

OK - let me know when it's fixed, I'd like to build the debs and test locally before merging since this is an important PR.

@vellamike Doc generation fixed in #125


[BUG] All SBOM_BLOB_URLs are fetched

When examining a attestation containing multiple SBOM_BLOB_URL Task results, for example an attestation of multi-arch image, in the evaluation of a single image all SBOM_BLOB_URL Task results are fetched and processed, not only those for that specific architecture.

I think we should handle this in ec-policies instead: https://github.com/enterprise-contract/ec-policies/pull/1202


BUG:  : label for the "Book title" given in Book Exchange Hub is in wrong style and written twice

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
when we go through the Book Exchange Hub the form is given for connecting to the readers, in that form the first field of book title label is writen twice and in wrong Style.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@anuragverma108 @huamanraj can you please this task to me, it will be very helpful for me.

can you please assign me this issue ? @anuragverma108

@Maheshwari-Love
Assigned!
Make sure to attach before & after screenshots in your PR. Also, star the repo before working on it. While creating your PR, ensure you pull all existing changes beforehand to avoid conflicts.
Happy open-source contributing!

@anuragverma108  I have fixed the issue and made a pull request, kindly review it and if any changes required please let me know.


Instances for com.twitter.concurrent.AsyncStream

Something like a year ago AsyncStream was added into twitter util. Up till now it was a mystery to me. Now that I've met it I'd like it to play nicely with the rest of cats and in order to do that it needs some instance magic.  This aims to provide that for those type classes I currently need. It bothers me that I had to Await for Eq to work but since that's what was done for Future I assume it's acceptable.
I hope.
It does in fact test out nicely.

Codecov Report

Merging #62 into master will decrease coverage by 3.89%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master      #62     +/-   ##
=========================================
- Coverage   52.84%   48.94%   -3.9%
=========================================
  Files           8        9      +1
  Lines         176      190     +14
  Branches        2        2
=========================================
  Hits           93       93
- Misses         83       97     +14

Impacted Files
Coverage Δ

...l/src/main/scala/io/catbird/util/asyncstream.scala
0% <0%> (ø)

Continue to review full report at Codecov.

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

Thanks! And yep, that's the only way to do Eq (and is why that method's not implicit).
Did you look into writing a stack-safe tailRecM?

I haven't yet, I just cribbed the current unsafe one from Var and called it good for now. I'm thinking monoid is also something worth creating an instance for but I wanted some feedback before continuing in case I had run something off the rails.

@travisbrown I switched Monad out for StackSafeMonad and changed the tests to assume stack safety and all seems well. I'm happy enough with this without Monoid at this point.

@travisbrown I'm at the point where I've gotten the code I want in and ready. Not sure why it's being reported as not tested, it should be fully covered by the law checks.

Sorry about the delay in review—this looks generally good to me, but I think we should be sure to create non-singleton arbitrary instances (which should improve test coverage as well).

I'm not sure what you mean by "non-singleton arbitrary instances"

Right now you have Arbitrary(A.arbitrary.map(AsyncStream.of)), which means that all the AsyncStream values generated for laws checking will consist of a single arbitrary element (i.e. no empty streams, no streams longer than one).

What about the following:
implicit def asyncStreamArbitrary[A](implicit A: Arbitrary[A]): Arbitrary[AsyncStream[A]] =
  Arbitrary(
    Arbitrary.arbitrary[Stream[A]].map(AsyncStream.fromSeq)
  )

The current version using AsyncStream(_) is essentially the same as of, since there will only ever be a single argument for the A*.

Thanks! Just restarted the build to see if that resolves the timeouts.

I'd be happy to see this merged with both AsyncStream and Var switched (back) to explicitly non-stack-safe tailRecM implementations and stackUnsafeMonad laws checking, and then we can handle stack safety for each of those individually in separate tickets / PRs.

Alright, I'll revert back to the explicit unsafe version of Var but I'd like to leave the stack safe version of AsyncStream in if I could. It's tested and working.

Looking at the codecov report and comparing it to what scoverage says makes me wonder if there's something missing in the integration. scoverage says the code coverage for the util module is 92% and that it's 100% for the rest of the modules. Aggregating the reports with scoverage then gives a coverage percentage as 94% which seems much closer to the truth than 49.46%. I'm not familiar with codecov or its API (which seems little more than upload the cobetura files) so I'm not sure what might be wrong.

@crispywalrus Yeah, I don't know what's up with the codecov reporting. I've seen something similar in other repos—e.g.: https://github.com/circe/circe-derivation/issues/4


bug: ngI18nClosureMode mode is not defined

Bug Report
production build shows white page and ngI18nClosureMode undefined error in logs
Ionic version:

[x] 4.x
Current behavior:

When I run ionic build --prod, Generate Cordova based Apk in Android Studio, then  the app shows white page, in the log I found an error with angular ngI18nClosureMode. The same behavior I got in electron serve.

Expected behavior:

N/A
Steps to reproduce:

Other information:

https://github.com/angular/angular/blob/master/packages/core/src/util/ng_i18n_closure_mode.ts
Ionic info:

ionic info

Ionic:

   Ionic CLI                     : 5.4.13 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.11.7
   @angular-devkit/build-angular : 0.803.22
   @angular-devkit/schematics    : 8.3.22
   @angular/cli                  : 8.3.21
   @ionic/angular-toolkit        : 2.1.1

Capacitor:

   Capacitor CLI   : 1.4.0
   @capacitor/core : 1.4.0

Cordova:

   Cordova CLI       : 9.0.0<EMAIL_ADDRESS>   Cordova Platforms : none
   Cordova Plugins   : no whitelisted plugins (0 plugins total)

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   ios-sim : 8.0.2
   NodeJS  : v10.16.3 (/usr/local/bin/node)
   npm     : 6.13.6
   OS      : macOS Catalina
   Xcode   : Xcode 11.1 Build version 11A1027

Thanks for the issue. Can you provide a repo with the code required to reproduce this issue?


Video ID xvideos

I'm trying your plugin, and enjoyed, however, I need to play videos from xvideos.com, the scheme is the same as that of youtube and vimeo, can you help me? And if it works out I want to buy your plugin, can I use it on two different projects as well?

You might have a look at some other libraries to get an idea of how to get the raw video URL out of the pages so you can pass it into the video player. A quick search on GitHub turned up this PHP snippet that uses regular expressions to extract the video URL from the web page. It is essentially the same thing I did for the YouTube video extension by getting the raw HTML of the page and then parsing it for the URL.
https://github.com/emeidi/extract-youtube-links-and-download/blob/master/youtube-dl/youtube_dl/extractor/xvideos.py

A single license grants you a set license keys to use for Android, iOS, Windows for a single app idea.


14 fix remote into container

Fix
env variables are adjusted per user input so that user can remote into container.
Enhancements
New Laravel project is created in adjacent folder
Switched node commands to be prefixed by docker:
Closes #14

Tested fine.


Why you don't use modelviewset or generics for API?

Hi Amir, How's Everything?
I just watched your project and see you are using APIView Instead of ModelViewSet for Listview CreateView and Detail View.
Do you have any reason to use these? you can do all of them with generics too but you create all of them from start.
If It's Okay I wanna to update your code to one the choices - ModelViewSet or Generics.

Hey dear Ali,
Just for code integrity. Using APIView makes it easier to understand everything that happens inside the codes. In real projects, you usually need to customize generic views, so it's better to start simple and customized from the beginning.
If a person has a little familiarity with Django, he can easily recognize at a glance what's happening in your project, while when using generic views, he's forced to study their mechanism.
And of course it's very important that your codes are written according to a specific structure and using different classes in different views is not very interesting.
thank you.

Hello again,
I said you can also use generics.
You can use ModelViewSet and actions for these kind of work you just said.
By the way, thank you for responding. ✌


kubicorn panics on apply for DigitalOcean

I installed kubicorn from master (7bcb550) with go get and exported my DIGITALOCEAN_ACCESS_TOKEN. When running kubicorn apply I am getting a panic for invalid memory address or nil pointer dereference.
deployments » kubicorn create kobol --profile do
2017-12-07T08:15:59-07:00 [ℹ]  Selected [fs] state store
2017-12-07T08:15:59-07:00 [✿]  The state [./_state/kobol/cluster.yaml] has been created. You can edit the file, then run `kubicorn apply kobol`

deployments » kubicorn apply kobo
2017-12-07T08:16:08-07:00 [ℹ]  Selected [fs] state store
2017-12-07T08:16:08-07:00 [ℹ]  Loaded cluster: kobol
2017-12-07T08:16:08-07:00 [ℹ]  Init Cluster
2017-12-07T08:16:08-07:00 [ℹ]  Query existing resources
2017-12-07T08:16:11-07:00 [ℹ]  Resolving expected resources
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x489222]

goroutine 1 [running]:
time.(*Timer).Stop(0x0, 0x11d8c40)
        /home/brady/.asdf/installs/golang/1.9.2/go/src/time/sleep.go:75 +0x22
github.com/kris-nova/kubicorn/cutil/signals.(*Handler).Reset(0xc420290a80)
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/cutil/signals/signals.go:73 +0x2f
github.com/kris-nova/kubicorn/cloud.teardown()
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/cloud/atomic_reconciler.go:202 +0x61
github.com/kris-nova/kubicorn/cloud.(*AtomicReconciler).Expected(0xc4202e74a0, 0xc420392820, 0xc4203f01a0, 0x0, 0x0)
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/cloud/atomic_reconciler.go:71 +0x33c
github.com/kris-nova/kubicorn/cmd.RunApply(0x19dd540, 0x11d97c0, 0xee5fe0)
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/cmd/apply.go:150 +0x6e2
github.com/kris-nova/kubicorn/cmd.ApplyCmd.func1(0xc420256240, 0xc4202790e0, 0x1, 0x1)
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/cmd/apply.go:60 +0x72
github.com/kris-nova/kubicorn/vendor/github.com/spf13/cobra.(*Command).execute(0xc420256240, 0xc4202790a0, 0x1, 0x1, 0xc420256240, 0xc4202790a0)
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/vendor/github.com/spf13/cobra/command.go:653 +0x2a2
github.com/kris-nova/kubicorn/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x19d6c60, 0xe01219, 0x119c5d9, 0x4)
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/vendor/github.com/spf13/cobra/command.go:728 +0x2fe
github.com/kris-nova/kubicorn/vendor/github.com/spf13/cobra.(*Command).Execute(0x19d6c60, 0x0, 0x9bb)
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/vendor/github.com/spf13/cobra/command.go:687 +0x2b
github.com/kris-nova/kubicorn/cmd.Execute()
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/cmd/root.go:85 +0x31
main.main()
        /home/brady/gocode/src/github.com/kris-nova/kubicorn/main.go:22 +0x20

Hi, thanks for reporting the issue.
This is a known issue and I already submitted PR fixing this (#493). However, I can't merge without @kris-nova, but she's out for Kubecon.
I believe it should be merged soon, but in the meanwhile, you can build of the signals-hotfix branch. I'll rebase it right now.

@bradylove The branch is re-based now, so you can use it in the meanwhile. Thanks once again.

@xmudrii thank you for you quick response.
I rebuilt master with the -race flag and tried again, it appeared to work this
time, however there were 6 data races detected. I pulled the signals-hotfix
branch and also built it with the -race flag. Apply worked again and the
data races still exist.
kobol apply <cluster name> from master (7bcb550) see here
kobol apply <cluster_name> from signals-hotfix see here
I am not too familiar with how the signals package is used but it would seem to me the fix in singals-hotfix does fix the panic from a nil pointer but could cause the timer to get out of sync. Example:

Register is called and starts a go routine.
Reset is called to stop the timer.
Go routine starts executing and initializes the timer.

@bradylove Thank you very much for analysis! This sounds strange.
I'll try to look into it as soon as I can, however I'm quite busy right now.
Signals are being handled from the cloud package; the relevant file is atomic_reconciler.go.
I believe the problem is that we're creating 4 signal handlers while reconciling, therefore race conditions. I think it would help to use some sort of global signal handler, but as I said, I can't test right now.
Once again, thank you very much for the help. I'll look into it as soon as I can.

Same happens when you apply cluster without internet connection -- see #503.


Française translation following CONTRIBUTING.md

Feature Request
Describe the solution you'd like
Following the CONTRIBUTING.md section on translations provide a Française translation.

[ ] README.md -> .github/lang/README.fr.md
[ ] CONTRIBUTING.md -> .github/lang/CONTRIBUTING.fr.md
[ ] lang/en.js -> lang/fr.js
[ ] content/en/index.md -> content/fr/index.md
[ ] content/en/details.md -> content/fr/details.md

Hey @Pandz18 did you want me to assign this to you?

Hey @Pandz18 did you want me to assign this to you?

Hi sure you can but I have to translate only the ReadMe file and the contributing file , if I'm not wrong ?

or all the files that have empty boxes next to them in your first comment

You can do just the docs if you like, but there is a chance to add French to the site translations too (all the files listed). I can explain how to do this and how to test it, if you like :)

You can do just the docs if you like, but there is a chance to add French to the site translations too (all the files listed). I can explain how to do this and how to test it, if you like :)

Hi , I did it for all of them , also my PR is showing an error. Can you tell me what I did wrong

@lukeocodes  Hi , I apologise for this but I've added a profile pic and was wondering if you could update it ? If it's not much of an issue .

@lukeocodes I apologise but this will be the last time I request you to update my photo, I'm so sorry but my mum told me to change my pfp . I'm so sorry Jaden for disturbing


Save time of death for satellites

Useful for logging in multiagent cases. Also maybe log satellite callbacks on death.

This is already a feature, oops!


Small fix about forcing wget to overwrite scripts when submitting a job.

@jerrychenhf Have renamed use_config_cache to no_config_cache, please help to merge.


Add events on month view options

I've added two more options to the :events-on-month-view attribute.
With the value medium the start time is prepended to the event title.
With the value long the start and end time is prepended to the event title.

Hi @bastianjoel, Thanks for your contribution!
I took some time to think it over and came to the conclusion I am not merging in despite the good quality of your work.
Sorry about that.
The reasons for that are:

The option Long is already in true
Adding an option medium makes it less intuitive what would be the straightforward result?
Prepending the time to the event title is not something that is done anywhere else, why would it reverse the order with a medium option
If you need to reverse the order of the event elements, there is a custom renderer for this purpose
We need to carefully select options that bring an outcome which is not already achievable through other options. If we don't vue-cal will end up with tons of options that will make the codebase harder to maintain and improve.

I hope you understand my point and I am sorry to close this PR.
If you still want to help on vue-cal, you can pick any "feature request" in the issues, and I will be happy to discuss the work to be done.
Cheers.


prettyping: init 1.0.1

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build prettyping

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: prettyping
Partial log (click to expand)
Cannot nix-instantiate `prettyping' because:
error: attribute 'prettyping' in selection path 'prettyping' not found

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: prettyping
Partial log (click to expand)
Cannot nix-instantiate `prettyping' because:
error: attribute 'prettyping' in selection path 'prettyping' not found

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: prettyping
Partial log (click to expand)
Cannot nix-instantiate `prettyping' because:
error: attribute 'prettyping' in selection path 'prettyping' not found

@xeji I've updated the PR. Thanks!

@GrahamcOfBorg build prettyping

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: prettyping
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: prettyping
Partial log (click to expand)
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/hybdncbvjw1z271ndfsp4qqysjzbzw3v-prettyping-1.0.1
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/hybdncbvjw1z271ndfsp4qqysjzbzw3v-prettyping-1.0.1/bin
patching script interpreter paths in /nix/store/hybdncbvjw1z271ndfsp4qqysjzbzw3v-prettyping-1.0.1
/nix/store/hybdncbvjw1z271ndfsp4qqysjzbzw3v-prettyping-1.0.1/bin/prettyping: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/fqm2x6kiay1q4vg7pqp4wp17bdijlyc3-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/hybdncbvjw1z271ndfsp4qqysjzbzw3v-prettyping-1.0.1...
/nix/store/hybdncbvjw1z271ndfsp4qqysjzbzw3v-prettyping-1.0.1

Success on x86_64-linux (full log)
Attempted: prettyping
Partial log (click to expand)
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/pfhnr8hhd0w3fwkyldg3sp7vahc6vqbc-prettyping-1.0.1
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/pfhnr8hhd0w3fwkyldg3sp7vahc6vqbc-prettyping-1.0.1/bin
patching script interpreter paths in /nix/store/pfhnr8hhd0w3fwkyldg3sp7vahc6vqbc-prettyping-1.0.1
/nix/store/pfhnr8hhd0w3fwkyldg3sp7vahc6vqbc-prettyping-1.0.1/bin/prettyping: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/czx8vkrb9jdgjyz8qfksh10vrnqa723l-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/pfhnr8hhd0w3fwkyldg3sp7vahc6vqbc-prettyping-1.0.1...
/nix/store/pfhnr8hhd0w3fwkyldg3sp7vahc6vqbc-prettyping-1.0.1


Validating URLs with an underscore in the subdomain.

Currently, the URL parsing fails for any URL that includes a subdomain with an underscore. For example:
my_domain.scott.com
This isn't a completely straightforward issue, because technically underscores in subdomains aren't standards compliant -- even if it's used and tends to work in every browser.
@yuyang041060120 Would you accept a pull request to allow for underscores in the subdomain?

The regex seems pretty restrictive in what it allows :(
http://localhost:11795/ for example is not considered a valid URL, neither would http://machinename/ be.
telnet://whatever.com/ wouldn't be considered a valid URL either since the regex seems to restrict the protocol to http/s and ftp.

localhost should be added. I'm running into a situation where I need this.