text:
Geldanzeige wird nicht geupdated

Wenn ich eine Wohnung übernehme, wird die Strafe nicht gleich auf mein Kontostand angerechnet. Das mag bei uns Millionären niemanden auffallen, aber bei 5000€ Starkapital bleibt da bis zum nächsten login oder nächsten Tag immer das gleiche stehen.
Dazu muss aber eine balanceDiff in jede History Response mit rein. Und simsalabim, das haben wir eh schonmal überlegt um die Summe in der History eigen darzustellen
https://github.com/immopoly/appengine/issues/4
Dann können wir die Farbe in der History (rot grün) auch davon abhängig machen.
Ich kümmere mich gerne als Initiativstrafe

history hat jetzt nen amount und die history wird nach den add / release task an den userdatamanager.update übergeben, der updated dann history balance und co und macht fireuserdatachanged.... todos sind drann um das mit dem hinzufügen und nehmen von flats auch zu machen.
History ist unser globales answerobjekt,
wir müssen nur nochmal den fehlerfall mit exception abklären

Habe gerade bemerkt das wenn ich ne Wohnung hinzufüge der status sich updated, aber irgendwie ist die berechnung falsch, habe jetzt 57.047.483 €, aber in wirklichkeit habe ich nur 179.160,694667€
Kann das mal wer anders testen ?
SCREENSHOT
https://img.skitch.com/20111203-ep2c8khbk1sa5hcq4sjuts1nd4.jpg

authors: mrschtief tobibo

repo: immopoly/android


text:
add_comp_snfi issue

Hi,
Using the latest version of humind, we get an issue when we excute humind::add_comp_snfi() as :
Error in are_values_in_set(): ! All columns must be in the following set: 7_to_8, 4_to_6, 1_to_3, none, undefined ℹ The following columns have values out of the set Please check. snfi_shelter_issue_cat ✖ The values out of the set are: snfi_shelter_issue_cat: other
This error appears when we use the updated function add_shelter_issue_cat by recoding :
undefined = c("dnk", "pnta"),
other=c("other")

Additional note: the documentation for param "issue_cat_levels" still has "none" as the first option.

Additional note: the documentation for param "issue_cat_levels" still has "none" as the first option.

Thank you for the catch. Change commited.

Linking to https://github.com/impact-initiatives-hppu/humind/issues/548 since we will recode functions using separate parameters; no longer need for "_levels"

source: gharchive/issue

authors: Borisso2020 gnoblet sunheemoraes

repo: impact-initiatives-hppu/humind

license: MIT

license_type: permissive

license_source: github-api


text:
Clean up existing config.ini if required to remove obsolete entries.

Cleans up config.ini to remove old obsolete entries such as "es7_FW18-19" which can confuse the end-users.

please don't merge this. just use minini to remove entries. this can be reduced down to a couple lines of code.

please don't merge this. just use minini to remove entries. this can be reduced down to a couple lines of code.

Think of this as the step-father of your child disciplining it differently in your absence.
If you want it raised right, feel free to step up.

I am not sure what you mean by that comment, I'll choose to ignore it.
There's 2 ways to go about this.

delete the config after all entries are read, then simply write them back to file.
use ini_puts with null as the value to delete a key.

Personally I wouldn't do anything. If users are getting confused about old entries in the file then that's on them. It's not like the overlay displays them.

I am not sure what you mean by that comment, I'll choose to ignore it.

Take ownership of your former project, and make the changes the way you want it. Or watch from afar as it goes through a gradual process of perceived bloat/enshitification.
In an abstract symbolic way, if you don't like the way someone else is raising your child that you have disowned, then just step up, make amends and take responsibility.

I mean, everyone has done a great job of maintaining this. The overlapping buffer fix is mostly correct for example 😉
The changes in this commit are a bit too drastic and bug prone imo, especially for the problem it's trying to solve. I am simply suggesting an alternative way of solving said problem.
Merge it if you like, I just don't think it's a good proposed fix, no offence.

source: gharchive/pull-request

authors: ITotalJustice borntohonk

repo: impeeza/sys-patch


text:
如果我想在预览的img标签下添加 referrerpolicy="no-referrer"   的代码，我应该如何调整呢？

Describe the issue

Procedure version
1
Reproduction link
1

参考这个：https://imzbf.github.io/md-editor-v3/zh-CN/demo#🔏 修改 xss 配置

authors: beiming-org imzbf


text:
Importing problem in Swift

When I install via cocoa pods, as in your instruction, I cannot import the module, concretely, I get the message No such module 'EventSource’
Do you have any ideas?

Just to be sure @pavlem are you opening the workspace generated when pod install?

Yes of course I am, I already have several pods and they are all working fine. For example, I am having the main project ScanG.xcodeproj and the workspace project ScanG.xcworkspace which I am using.

I created a completely new project from scratch, so you can see the error.
Link: https://github.com/pavlem/SSEventsTest

As I see, you only have EventSource.h generated after pod install

I have the same issue. Any help ? Thx

Any news here? Any help will be greatly appreciated by me as well.

I'm taking a look right now, hopefully I can figure it out. In the meantime you can copy EventSource/Sources/EventSource.swift file into your project and that has to work.

@nikolaschou @spiridonkopicl @pavlem guys I just updated to Swift 5, merged some PRs and updated the pod. Everything should be working now.
Update the pod:
pod update IKEventSource

I tested with @pavlem's test project and after updating the pod the project compiled perfectly. I'll try to make some space to keep maintaining this. I haven't worked on a long time on this and checked the code and there is a lot of space for improvement.

@andresinaka thanks, the import now works, but it gives me weird feedback in Xcode.
2019-05-27 11:01:23.046348+0200 ScanAndGo[5597:253775] Task <28410D31-A8B9-44A7-A059-FD9BAE51C6DE>.<1> load failed with error Error Domain=NSURLErrorDomain Code=-999 "annulleret" UserInfo={NSErrorFailingURLStringKey=https://d-xxx.com/api/events?cs=userDevice, NSErrorFailingURLKey=https://d-xxx.com/api/events?cs=userDevice, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDataTask <28410D31-A8B9-44A7-A059-FD9BAE51C6DE>.<1>"
), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <28410D31-A8B9-44A7-A059-FD9BAE51C6DE>.<1>, NSLocalizedDescription=annulleret} [-999]
2019-05-27 11:01:23.046523+0200 ScanAndGo[5597:253777] Task <28410D31-A8B9-44A7-A059-FD9BAE51C6DE>.<1> finished with error - code: -999

Just to note, I tried in the meantime with some other library and it works although that one has some buffer issues, but I can see the events coming (https://github.com/banjun/ReactiveSSE). Also, it is working on android totally fine via https://github.com/heremaps/oksse, so the server is not the issue.

mmm that's a weird error, it looks like the eventSource instance is getting dealloc... I just tried with the url in your example and it seems to connect but the server is not even returning a 200... weird
import UIKit
import IKEventSource

class ViewController: UIViewController {

    var eventSource: EventSource?

    override func viewDidLoad() {
        super.viewDidLoad()

        eventSource = EventSource(url: "https://d-xxx.com/api/events?cs=userDevice")

        eventSource?.onOpen {
            print("OPEN")
        }
    }
}

Hello Adnre,
I sent you the correct URL to your email.

authors: andresinaka nikolaschou pavlem spiridonkopicl

repo: inaka/EventSource

license_source: bigquery


text:
Suggestion to rename the spatial_ directories in content/tutorials

I suggest to prefix the spatial_ directories in content/tutorials with r_, resulting in r_spatial_xxxx. They all relate to R, and we expect non-R spatial tutorials to come which could then use e.g. qgis_xxxx. (An alternative would be spatial_r_ and spatial_qgis_, but the suggested r_spatial_ is more in line with the existing r_ directories)
It's not that important, but it seems more streamlined that way. Feel free to comment.

I'll drop my idea, since it would turn existing links (in other places) non-functional, i.e. links to the affected tutorials. We'll better use spatial_qgis_ or something like that for non-R spatial tutorials.

repo: inbo/tutorials


text:
Support weakly typed data and search attributes

Basically skip the type checking for those cases to be more flexible. In some case that user want to implement an dynamic workflow that may need dynamic data or search attributes (especially with persistence locking)
Another idea is to let user define data/search attribute with type by prefix:
DataAttributeDef.createByPrefix("UserInteger-", Integer.class)

Also need https://github.com/indeedeng/iwf-java-sdk/issues/180

Data attributes should be easily supported.
But search attributes need to be registered into the namespace, how could it be dynamically created during running time?

To support the createByPrefix for data attributes, we could:

add a new filed isPrefix into DataAttributeDef.
in registry, add a new Map<String, Map<String, Class<?>>> dataAttributePrefixToTypeStore field to record the prefixes seperately, so that when validating the keys, the time complexity could be O(N), where N is the count of prefixes.

To support the createByPrefix for data attributes, we could:

add a new filed isPrefix into DataAttributeDef.
in registry, add a new Map<String, Map<String, Class<?>>> dataAttributePrefixToTypeStore field to record the prefixes seperately, so that when validating the keys, the time complexity could be O(N), where N is the count of prefixes.

@longquanzheng What do you think?

That looks good to me. I would probably do the same way as you described

Also I just realized that getAllDataObjects will be broken for now after this change. We may just add a comment for this behavior as edge case. (In fact, I think this API is not too important to have anyway)

Data attribute support in #189.

authors: longquanzheng zklgame

repo: indeedeng/iwf-java-sdk


text:
Support for passing custom file extensions to eslint / jshint

Note: I haven't tested the jshint part, only eslint

Published in fashion-show@3.2.0.

authors: indexzero jansel

repo: indexzero/fashion-show

license: mit


text:
Change event never fires

Assigning a function to change, the function is never called with the arguments promised.
controller.js
$scope.log=function(){
    console.log(arguments);
};

If change="log" it will never fire. If change="log()" it fires, but always with empty arguments.

Hi @swimmadude66, you're not passing through the data in your HTML. Because of how Angular evals functions you need to pass the parameters you're trying to get to your log function in the HTML, like this:
<select ... change="log(newValue, oldValue)" ..></select>
```

repo: indrimuska/angular-selector


text:
[ProteinSolvation] Add maxwarn flag to grompp command

The addition of the maxwarn flag to the grompp command prevents experiments to fail for this common errors:
 WARNING 1 [file energy_minimization.mdp]:
  The largest distance between excluded atoms is 1.208 nm, which is larger
  than the cut-off distance. This will lead to missing long-range
  corrections in the forces and energies. If you expect that minimization
  will bring such distances within the cut-off, you can ignore this warning.

According to this the user should take a look to check if the protein structure is correct, however, the problem can be overriden by setting the maxwarn flag to 1.
I also remove the ns_type variable, since it was already the default value.

@cristianacarpinteiro according to this (and following the structures of other simulators) it means that if more than one warning appears, then the simulation crashes. Is this correct?
Moreover, this error won't be passed to the user until the end of the simulation, so we won't be able to stop it if he did not want this happening. So the simulation can work, but users may still want to kill it for these warnings. No? If so, we need to start thinking about how to send this to the user.

@cristianacarpinteiro according to this (and following the structures of other simulators) it means that if more than one warning appears, then the simulation crashes. Is this correct?
Moreover, this error won't be passed to the user until the end of the simulation, so we won't be able to stop it if he did not want this happening. So the simulation can work, but users may still want to kill it for these warnings. No? If so, we need to start thinking about how to send this to the user.

Yes, you are correct! These warnings appear in a lot of RCSB files and are very specific to each protein to solve in a systematic way. Ignoring this warnings will produce a simulation with some minor inaccuracies according to the documentation, but I think it should be up to the user if he wants to ignore the warnings or not. What is your suggestion on how to pass this to the user?

Yes, you are correct! These warnings appear in a lot of RCSB files and are very specific to each protein to solve in a systematic way. Ignoring this warnings will produce a simulation with some minor inaccuracies according to the documentation, but I think it should be up to the user if he wants to ignore the warnings or not. What is your suggestion on how to pass this to the user?

I do not have a suggestion as of yet, but at least for warnings there should be a certain stream from the backend so that users can immediately address them if they want. Otherwise, they consume computation and only at the end they see their simulation was useless.

I think the best way of approaching this as of now is to pass a ignore_warnings in the simulate method. If the user sets it to True we add the maxwarn flag and if it sets to False the simulation will fail and then the user can see the warnings on the stdout. Streaming the warnings to the user directly seems a too complicated solution to implement quickly.

simulate method. If the user sets it to True we add the maxwarn flag and if it sets to False the simulation will fail and then the user can see the warnings on the stdout. Streaming the warnings to the user directly seems a too complicated solutio

Seems a reasonable solution. The user can check immediatly in the stdout if the simulation crashed due to warnings and pass the argument accordingly

I think the best way of approaching this as of now is to pass a ignore_warnings in the simulate method. If the user sets it to True we add the maxwarn flag and if it sets to False the simulation will fail and then the user can see the warnings on the stdout. Streaming the warnings to the user directly seems a too complicated solution to implement quickly.

I didn't mention to do it quickly :) Just to start thinking about it!
Okay, that seems like a reasonable solution! However, with -maxwarn 1 this will just ignore the first warning and crash on the second. What do you think you should provide? Ignore all? A few? Let the user decide?

I will put it as a value the user can change instead of a bool.

@david451lima @IvanPombo I am re-requesting your review because I changed the way I was doing this to address our concerns.

repo: inductiva/inductiva


text:
How to use laravel's Storage::download response?

How can I use Storage::download() with Inertia? Currently it just opens up a modal with the contents of the downloaded file..

You need to make a normal, non-Inertia request to download files. All Inertia requests must return a valid Inertia response, which a file download of course isn't. So, instead of using an <inertia-link>, just use a regular <a>. 👍

gular <a>.

Did you find a way around this?
I need to send a post request to download the file.

You should be able to just use a regular form. Optionally with the target set to _blank to ensure a new window/tab opens and your Inertia app will just keep running.
<form action={yourDownloadUrl} method="post" target="_blank">
    <button>Download</button>
</form>

You can do it with a form... but remember the csrf token.
First, send the token to the Inertia view where you are going to insert the form:
return inertia ( 'YourView', [ 'token' => csrf_token() ] );

Now, in the view, insert the csrf token in a hidden input.
For instance, in a React view:
<form action = { route ('your.named.route', your.param) } method = "post">
    <input type="hidden" name="_token" value={props.token}/>
    <button>Download</button>
</form>

You can use this in onClick
fetch(route('documents.download', { id: document.id }))
    .then((res) => res.blob())
    .then((blob) => {
      const file = window.URL.createObjectURL(blob)
      window.location.assign(file)
    })

Is there any new and convenient way to do this, just with inertiajs form ?

authors: Naoray boparaiamrit javdome nwaweru omidgfx reinink rojtjo

repo: inertiajs/inertia-laravel


text:
Update ServiceProvider@registerBladeDirective

Enables to change parent div id's, defaulted to app

Reasonable addition, thanks! 👍

authors: halilcakar reinink


text:
Flow queue states and related Errors

Currently I have empty() to support. #94
But what about the callback queue?

According to #95 I can reject invalid awaits/pulls or I can check the state whether it is possible to pull.
fileReader.on("pull", readNextChunk);
fileWriter.on("push", writeNextChunk);
(function pump(){
    fileReader.pull(function (chunk){
        if (fileReader.atEnd())
            fileWriter.close();
        else
            pump();
        fileWriter.push(chunk);
    });
})();

fileReader.on("pull", readNextChunk);
fileWriter.on("push", writeNextChunk);
fileReader.on("reject", function (){
    fileWriter.close();
});
(function pump(){
    fileReader.pull(function (chunk){
        fileWriter.push(chunk);
        pump();
    });
})();

I don't like the reject event in this scenario. I think it should throw an error just as by empty read.
fileReader.on("pull", readNextChunk);
fileWriter.on("push", writeNextChunk);
(function pump(){
    fileReader.pull(function (chunk){
        if (fileReader.isDrain())
            fileWriter.close();
        else
            pump();
        fileWriter.push(chunk);
    });
})();

var fileReader = new FileReader({path: "path1", open: true});
var fileWriter = new FileWriter({path: "path2", open: true});
(function pump(){
    try {
        fileReader.pull(function (chunk){
            fileWriter.push(chunk);
            pump();
        });
    } catch (error) {
        fileReader.close();
        fileWriter.close();
        if (!(error instanceof Flow.Drain))
            throw error;
    }
})();

I need to rename the states and the current error types.
Flow.Empty
Flow.Drain
flow.isEmpty() || flow.empty()
flow.isDrain() || flow.drain()

drain is a verb, I need an adjective. so we can call it dry instead.

Flow.Empty
Flow.Drain
flow.isEmpty()
flow.empty() // making the flow empty
flow.isDry()
flow.drain() // making the flow dry, rejecting all the callbacks

So what should happen when I drain an already pulled/awaited flow?
I don't know...

Let's assume we are reading a file:
reader.write(file.chunk);
if (file.atEnd) {
    reader.drain();
    breakTheLoop();
}

So a flow can be non-empty but dry.
I think dry is not the best term to describe this.

Exhausted, run dry, no better :S Stop might be the right term.
reader.write(file.chunk);
if (file.atEnd) {
    reader.stop();
    breakTheLoop();
}

That does not feel right either.
if (reader.exhausted)
    while(!reader.dry)
        writer.write(reader.read());

I am not sure. Exhausted means that we used up everything. What if we want to reuse the same flow again. So it is dry for a long term, but it can find a new source later and can be filled again.

We can add an exhaust() method to make the flow exhausted, and we can add a drain() method to make it dry. I think these are better terms than the previous ones. Ofc. we can use empty() instead of dry if we want to do. It does not really matter. Another possible adjective instead of exhausted can be consumed.

I don't like the dry, because it is part of the stream API. I need to check exactly what it means there.

What if we add a dry-await / dry-pull event, and the event handler could stop the error throwing mechanism? It would be just the same as the code suggested here: https://github.com/inf3rno/dataflower/issues/95

Okay, I'll add some examples about loop, and let's find out what to implement for breaking the loop.

By streams the drain event indicates when it is appropriate to resume writing. So to translate it is triggered when the queue gets empty/dry. Is there a way to do the same without defining an event?


text:
[Question]: How can I upload 1000 files at once

Describe your problem

我上传了一个文件夹，一共有869个文件，我设置了    client_max_body_size 999M，但是还是出现这个错误，请问，怎么能一次性上传1000个文件呢？

@fg2501我们打算创建一个国际社区，所以我们鼓励使用英语进行交流。

大佬，并不是我不想用英语交流，而是我不会啊！

@fg2501 We intend to create an international community, so we encourage using English for communication.

If I really have to communicate in English, can every sentence be translated into English through ChatGPT and sent here, just like I'm doing right now?

I don't think it is feasible to accomplish this through web UI.
Check HTTP API / Python SDK out.

I don't think it is feasible to accomplish this through web UI. Check HTTP API / Python SDK out.

大神，我是一个编程小白，能具体说一下，应该怎么做呢？

repo: infiniflow/ragflow


text:
[Feature Request]: Missing avatar in API: list-chat-assistants

Is there an existing issue for the same feature request?

[X] I have checked the existing issues.

Is your feature request related to a problem?
No response
Describe the feature you'd like
https://ragflow.io/docs/dev/http_api_reference#list-chat-assistants
Describe implementation you've considered
No response
Documentation, adoption, use case
No response
Additional information
No response

avatar does exist.

authors: Feiue KevinHuSh


text:
A trick to bypass words blocking patches

A trick to bypass words blocking patches https://github.com/Puliczek/CVE-2021-44228-PoC-log4j-bypass-words

Thx for the report. I can confirm, I have already seen some attacks using the lower/upper sets.

@realization does it work with https://github.com/infiniroot/nginx-mitigate-log4shell/blob/handle-bypass/mitigate-log4shell.conf ?
i'm sure lua allows a better input handling, but that's what I came up with as quickfix (first time working with lua here).

authors: Napsty realization


text:
ISPN-10500 Remove javassist 3.24.1-GA dependency

this version is no longer used by any Infinispan module, but 3.23.1-GA is still used by hibernate-search so that one is kept

https://issues.jboss.org/browse/ISPN-10500

I will also backport this to 9.4.x once I see CI is fine

I still see javassist module used here: https://github.com/infinispan/infinispan/blob/10.0.0.Beta5/feature-pack/client/src/main/resources/modules/io/netty/slot/module.xml#L20 but I suppose that module is already deployed other feturepack in wildfly, like it happens for "org.jboss.logging" or other modules we consume but do not provide ourselves. I think it's safe to go.

CI has 2 failures, but do not seem related.

integrated! thanks @anistor

authors: anistor pruivo

repo: infinispan/infinispan


text:
Document mapping type name can't start with '_'

When using put_document I received the following error:
** (MatchError) no match of right hand side value: {:error, %Elasticsearch.Exception{col: nil, line: nil, message: "Document mapping type name can't start with '_', found: [_doc]", query: nil, raw: %{"error" => %{"reason" => "Document mapping type name can't start with '_', found: [_doc]", "root_cause" => [%{"reason" => "Document mapping type name can't start with '_', found: [_doc]", "type" => "invalid_type_name_exception"}], "type" => "invalid_type_name_exception"}, "status" => 400}, status: 400, type: "invalid_type_name_exception"}}
My Elasticsearch version is 6.5.2.
I checked that by default document_url is using "_doc" and it seems that it will no longer be possible to start with "_" the type. Is there a way to solve without changing the code?
https://github.com/infinitered/elasticsearch-elixir/blob/5c7c2dd186217cb7d3c6252275e4ae47b193fe4b/lib/elasticsearch.ex#L127

@jhonathas Since Elasticsearch is removing mapping types in favor of _doc, this should be working in 6.5.2.  Elasticsearch merged a PR to support _doc over a year ago.
We're running tests here against 6.4.0, and the tests exercise put_document quite heavily. Everything seems to be working?
Can you share more details about how you're calling put_document? Also, double check to make sure you're not running an older version of Elasticsearch.

I just realized that even giving the command to install version 6.5.2 (mix elasticsearch.install vendor --version 6.5.2), he installed 5.1.1.
I'm testing other versions. That may have been it.

Now I ran the command again to install version 6.5.2 and it installed 6.5.1. I think the problem was really in the...
{   "name" : "k417ww3",   "cluster_name" : "elasticsearch",   "cluster_uuid" : "tnTNRrwKQnOiN57O40VK9Q",   "version" : {     "number" : "6.5.1",     "build_flavor" : "default",     "build_type" : "tar",     "build_hash" : "8c58350",     "build_date" : "2018-11-16T02:22:42.182257Z",     "build_snapshot" : false,     "lucene_version" : "7.5.0",     "minimum_wire_compatibility_version" : "5.6.0",     "minimum_index_compatibility_version" : "5.0.0"   },   "tagline" : "You Know, for Search" }

authors: danielberkompas jhonathas

repo: infinitered/elasticsearch-elixir


text:
@tensorflow/tfjs-node is depreciated?

It looks like tfjs-node has been archived.  Is it still ok to use?  Should this project switch to @tensorflow/tfjs?

I just pulled up the docs, and I don't see anything about archived.  Where are you looking?
https://github.com/tensorflow/tfjs/tree/master/tfjs-node

ah good!  Reopen if I can help.

authors: GantMan qozle

repo: infinitered/nsfwjs


text:
OSS Get started update (addresses #2124 )

Closes #2124
With notebooks moving to OSS GA soon, we'll be able to update the GS with a more tutorial-focused notebooks path (similar to https://docs.influxdata.com/influxdb/cloud/get-started/) soon.

Some suggestions, but also an overall critique of new get started content: Rather than link to all the different ways a user can collect/write/query/visualize data, we should walk them through a proven path that will allow them to do all of these things. I would suggest the following:

Use one of the sample data sets. Walk a user through writing the data set (CSV or LP upload). Or we could have them set up a scraper and use that data.
Walk through how to query that data in the UI.
Walk through creating a dashboard to visualize the data.
etc.

At the end of each section or at the end of the doc, we can provide links to other methods to accomplish each task, but a user should be able to go through the get started guide step by step and successfully complete each task.

Hey @sanderson , I do agree with that but as stated in the PR description, this content will be replaced with the much more comprehensive notebooks path as soon as notebooks are released for OSS, which should be in the next week or two. Because of that, I used the existing getting started content (it's not actually "new", just moved) for now rather than reinventing the wheel for something that will be up for just a couple weeks.

🤦🏻♂ My bad. I should've read the description. Looks tood.


text:
add info about OFFSET and WHERE in subqueries

Closes https://github.com/influxdata/DAR/issues/90
Hi @ayang64 @jsteenb2 I was curious whether we should remove this note--or does this note still apply for "main" queries...just not valid for subqueries?

moved to v2 repo


text:
Not able to add members in influx cloud UI

Not able to add members (invite users into this trial account)
https://us-west-2-1.aws.cloud2.influxdata.com/orgs/<org_id>/settings/members

How can I invite a new user into this trial account?

this is no longer relevant. we've updated the way we handle users in cloud.

repo: influxdata/influxdb


text:
Question: Collect docker metrics from remote docker host

Hello,
I would like to collect docker metrics on my local device from a docker engine which is running on a remote device.
Does anyone know how to use the [inputs.docker] plugin in telegraf with tcp endpoint?
What do I need to set up/configure on the docker daemon from the remote deivce and what do I need to set up/configure on the device from where I want to collect the data? Telegraf will be running in a docker container.
I have tried to set the ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:2375 in the docker.service file for systemd as described in https://docs.docker.com/engine/reference/commandline/dockerd/ it is not working.
Can someone help?

@dockerize8 thanks! The docker input for telegraf is documented here: https://github.com/influxdata/telegraf/tree/master/plugins/inputs/docker#docker-input-plugin
You might have more luck opening this in the https://github.com/influxdata/telegraf repo.


text:
Data loss in influxdb due to aggregators

I am pushing data from NATS to InfluxDB using Telegraf. The data is being generated continuously, which results in multiple entries having the same timestamp. My timestamps are in nanoseconds, but in InfluxDB, the data is being aggregated, causing a loss of data points in my Grafana dashboard.
Can any one suggest how to avoid data loss.
example data.
requestsRaw,ObjectType=requestsRaw,errorMessage=noData,errorResponseBody=noData,host=server-3,nodeName=Test-Node,requestName=WebSocket\ request-response\ Sampler,responseCode=200,result=pass,runId=R_20241015-1415,samplerType=transaction,subject=nats.subject.requestsraw,testName=Test time=1728981942717004500,count=1,errorCount=0,sentBytes=1467,timeStamp=1728981940732,receivedBytes=59275,latency=0,processingTime=0,connectTime=0,responseTime=3151 1728981942717004544
requestsRaw,ObjectType=requestsRaw,errorMessage=noData,errorResponseBody=noData,host=server-3,nodeName=Test-Node,requestName=WebSocket\ request-response\ Sampler,responseCode=200,result=pass,runId=R_20241015-1415,samplerType=transaction,subject=nats.subject.requestsraw,testName=Test latency=0,receivedBytes=59275,time=1728981942717004500,errorCount=0,responseTime=1276,count=1,processingTime=0,sentBytes=1467,timeStamp=1728981942619,connectTime=0 1728981942717004544
Below is my telegraf configuration
[[inputs.nats_consumer]]
servers = [“nats://localhost:4222”]
subjects = [“nats.subject.requestsraw”]
data_format = “xpath_json”
xpath_native_types = true
fieldexclude = [“subjects”, “runId”, “testName”, “nodeName”, “ObjectType”, “errorMessage”, “errorResponseBody”, “requestName”, “responseCode”, “result”, “samplerType”]
[[inputs.nats_consumer.xpath]]
metric_name = “‘requestsRaw’”
metric_selection = “/"
timestamp = “time”
timestamp_format = “unix_ns”
field_selection = "”
[inputs.nats_consumer.xpath.tags]
runId = “string(/runId)”
testName = “string(/testName)”
nodeName = “string(/nodeName)”
ObjectType = “string(/ObjectType)”
errorMessage = “string(/errorMessage)”
errorResponseBody = “string(/errorResponseBody)”
requestName = “string(/requestName)”
responseCode = “string(/responseCode)”
result = “string(/result)”
samplerType = “string(/samplerType)”

I'm not sure what you mean by aggregate (could you explain?) but I believe these docs address what I think is happening to you:
https://docs.influxdata.com/influxdb/v1/write_protocols/line_protocol_tutorial/#duplicate-points

authors: philjb thrinathadevops


text:
Keep Influx client in separate repository

When I execute go get "github.com/influxdata/influxdb/client/v2", I get:
# cd .; git clone https://github.com/influxdata/influxdb /home/emiliano/go/src/github.com/influxdata/influxdb
Cloning into '/home/emiliano/go/src/github.com/influxdata/influxdb'...
fatal: unable to access 'https://github.com/influxdata/influxdb/': GnuTLS recv error (-54): Error in the pull function.
package github.com/influxdata/influxdb/client/v2: exit status 128

OK, I've found part of the cause; the command to install the client pulls in the entire influxdb repo at 56MB of data rather than just the go client. Could the go client be split off to a separate repository?

@retorquere Hi, this has been considered in the past and may even arrive in the future. I'm converting this issue to a feature request as I can't find an existing issue that requests this.

We have plans to create a new client. Some of that work has already begun at https://github.com/influxdata/influxdb-client. If you have the opportunity, please leave any feedback or requests for that new client in that repository.
Thanks.

Is this client already usable? I'm open to use help test this.

It's experimental at the moment. If you're going to use it, you should vendor or version pin in some way because the API is likely going to change. It is usable for querying at the moment and I'm currently working on a write API.

The write API is what I'm most interested in. I don't mind the API changing, the tool I'm building is under heavy change itself, so this would just fold in. But without write, I can't start using this.

(BTW, I'm currently using raw line protocol for writes because the current v2 API was unusably slow for my use-case at least)

I have a PR up for an initial version of the write API for that new client in influxdata/influxdb-client#4. If you're interested, you can check out that PR and try using it. The API currently allows either writing directly with line protocol or having the protocol get encoded for you.
There's still more work to do to build convenience functions on top of it, but just having the PR gets a baseline to start the work at least.

I am curious as to why the client was moved into the influxdb repository in the first place as https://github.com/influxdata/influxdb-go shows, I am really not a big fan of the way go handles dependencies but in that case having to clone the full database repository to interface with it is totally silly, I would imagine you won't have to clone mariadb repository to request it, at least I hope xD

authors: e-dard jsternberg retorquere schmurfy


text:
Could not add uint64 value with Influxdb client for go

Hello, Influxdb team!
I just tried to add uint64 value with official InfluxDB's Go client and got very painful bug. My values was added as "string" (as consequence all math operation on this data become impossible).
My friend @mrqwer88 found reason of this behaviour and I could quote it here from InfluxDB's code https://github.com/influxdata/influxdb/blob/91ee34b111f2034ec9456a6ce391b470d69e3216/models/points.go#L2013:
// TODO: 'uint' should be considered just as "dangerous" as a uint64,
 // perhaps the value should be checked and capped at MaxInt64? We could
 // then include uint64 as an accepted value

Do you have any plans to implement uint64 values support? it's widely used type in different systems (linux, snmp, routers) and it's enough complicated to avoid usage of it.
Thank you!

See #7801

Oh, I see. Feel free to close my tix as duplicate.
On Sat, 28 Jan 2017 at 15:27, britcey notifications@github.com wrote:

See #7801 https://github.com/influxdata/influxdb/issues/7801
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/7901#issuecomment-275854433,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACnfZsVLpI9T-r-HFXGJjTtDtXmejM8Wks5rW15kgaJpZM4LwgxB
.

--
Sincerely yours, Pavel Odintsov

authors: britcey pavel-odintsov


text:
databases created in 1.2.2 cannot be backed up and restored in 1.5.2

Hi there
From influx 1.2.2 we do a complete backup of all our databases, first (all) the meta, then all the data.
On a fresh instance of 1.5.2 we do an 'offline' restore of all the meta/databases: everything appears to work fine, the data has been transferred and is available via queries etc.
On the 1.5.2 instance we now perform a "-portable" backup of a single database, and then drop the database. The files appear to be correctly written.
We then perform a restore of those files (again using -portable). The restore fails with:
$ influxd restore -portable -database sla_cvlili /root/sla_cvlili/
2018/04/26 15:38:15 error updating meta: updating metadata on influxd service failed: err=read tcp 127.0.0.1:39456->127.0.0.1:8088: read: connection reset by peer, n=16
restore: updating metadata on influxd service failed: err=read tcp 127.0.0.1:39456->127.0.0.1:8088: read: connection reset by peer, n=16
$

in the influx server logs we see one single line:
2018-04-26T15:39:58.932722Z	info	failed to decode meta: proto: meta.ShardGroupInfo: illegal tag 0 (wire type 0)	{"log_id": "07heI8BW000", "service": "snapshot"}

we are also now incapable of doing a -portable backup for new databases created in the 1.5.2 instance. the act of restoring the original 1.2.2 data appears to have broken the 1.52 instance.
If we start from scratch without performing the original restore of the 1.2.2 data the -portable backup/restore works as expected.
is there a way we can better understand the error:
failed to decode meta: proto: meta.ShardGroupInfo: illegal tag 0 (wire type 0)
?
thanks for any ideas
appendicies:
# backup procedure on 1.2.2:
influxd backup -database $database -retention forever -since $INCR_SINCE_DATE $INFLUX_BACKUP_DIR

# restore procedure on 1.5.2 (offline):
influxd restore -metadir $INFLUX_DATA_DIR/meta/ $INFLUX_BACKUP_DIR/metastore/
for database in $(cat $INFLUX_BACKUP_DIR/databases); do
    influxd restore -database $database -datadir  $INFLUX_DATA_DIR/data/ $INFLUX_BACKUP_DIR
done

Update:
to help reproduce this I attach a backup of a single-row database ("foo") from our 1.2.2 instance.
This database was created with the following commands:
create database foo
use foo
INSERT treasures,captain_id=pirate_king value=2
exit

backup was made using:
influxd backup -database foo foo

attempt to restore on influx 1.5.2:
$ influxd restore -online -db foo -newdb foo foo
2018/04/27 09:53:25 Using metastore snapshot: foo/meta.00
2018/04/27 09:53:25 error updating meta: updating metadata on influxd service failed: err=read tcp 127.0.0.1:39236->127.0.0.1:8088: read: connection reset by peer, n=16
restore: updating metadata on influxd service failed: err=read tcp 127.0.0.1:39236->127.0.0.1:8088: read: connection reset by peer, n=16
$

The log appears in influx:
failed to decode meta: proto: meta.ShardGroupInfo: illegal tag 0 (wire type 0)	{"log_id": "07ibSndG000", "service": "snapshot"}

This can be replayed easily using docker:
cd && unzip foo.zip

docker run -it -d -p 8086:8086  -e INFLUX_BACKUP_DIR=/var/lib/influxdb/backup -e INFLUX_DATA_DIR=/var/lib/influxdb -v `pwd`/foo:/var/lib/influxdb/backup --name=influxdb influxdb:1.5.2

docker exec -it influxdb bash
# once in docker execute:
influxd restore -online $INFLUX_BACKUP_DIR

Foo database backup is attached.
It appears that Influx 1.5.2 online mode restore is not compatible with backups made by Influx 1.2. I haven't tested backups made by 1.3/1.4. non-portable backups created in and exported from 1.5.2 can be restored using -online mode to the same 1.5.2 instance.
Any ideas on how to get more info regarding:
failed to decode meta: proto: meta.ShardGroupInfo: illegal tag 0 (wire type 0)	{"log_id": "07ibSndG000", "service": "snapshot"}
would be appreciated.
foo.zip

Hi, I used influxdb 1.2 to backup and influxdb 1.5.2 to restore.
But my restore order is influxd restore -metadir /influxdb/meta/  /backup/meta influxd restore -database mydatabase /influxdb/data/ backup/data/. Then I change influxdb conf [data] index='tsi1'and use influx_inspect to convert data structure from TSM to TSI influx_inspect -database mydatabase -datadir /influxdb/data/ -waldir /influxdb/wal/. It worked well. I think maybe restore portable was not worked because influxdb 1.2 backup didn't have portable option.

Hi Heath, thanks for your response.
That's interesting regarding the conversion of indexes, however this would also be an offline backup/restore, in the sense that you can't be collecting data during the process. It's very useful though thanks for that.
regarding the restore portable, it was influx 1.5.2 that did the portable backup so it should be able to restore a backup it made itself.  For me there is a bug with portable backups in 1.5.2 (as evidenced with the docker reproduce above), I wouldn't trust online backups in production in the current state for the open source version at least.
to summarise:
1.2.2  backup -> 1.5.2 (offline restore ('works')) -> 1.5.2 portable backup -> (new 1.5.2) portable restore fails
and
1.2.2  backup -> 1.5.2 (online restore) fails  (see docker example)

Having the same problem with 1.4 and 1.5.3. I upgraded influx to 1.5.3 prior to the -portable backup but this still didn't help.
ts=2018-06-11T09:56:46.298458Z lvl=info msg="failed to decode meta: proto: meta.DatabaseInfo: illegal tag 0 (wire type 0)" log_id=08c_5UU0000 service=snapshot

Same problem here. I'm making backups from 1.5.2 OSS to restore to 1.6.4 OSS.
Backup command:
influxd backup -host myhost_to_backup:8088 -portable /influxdb_prod_backup/

Restore command:
influxd restore -host myhost_to_restore -portable /influxdb_prod_backup/

Error:
ts=2018-11-02T15:18:58.265897Z lvl=info msg="failed to decode meta: proto: meta.ShardGroupInfo: illegal tag 0 (wire type 0)" log_id=0BXFl9yW000 service=snapshot

I've tested making backup from 1.6.4 to 1.6.4, using the same aforementioned commands for backup and restore and the problem persists

Guys, it seems to be something related to docker networking, not with influxdb itself. I've made a test running an influxdb 1.6.4 container sharing the volume that contains backup files made from influxdb 1.6.4. Withing it, I've executed the influxd restore command and it worked like a charm.

I had similar case but the error I got when running restore to remote influxdb docker instance was:
$ influxd restore -db foo -portable -host 192.168.12.13:8088 -newdb bar ~/backup/
error updating meta: DB metadata not changed. database may already exist
restore: DB metadata not changed. database may already exist

The -newdb bar did not exist on the remote influxdb instance and the logs only had:
lvl=info msg="failed to decode meta: proto: meta.ShardGroupInfo: illegal tag 0 (wire type 0)"
Found @galindro 's helpful comment. Moving the backup files to the remote and running locally worked like it should:
$ sudo docker exec -it container_id /bin/bash
# mkdir /tmp/backup; exit
$ sudo docker cp ~/tmp/portable_backup/. container_id:/tmp/backup
$ sudo docker exec -it container_id /bin/bash
# influxd restore -db foo -portable -newdb bar /tmp/backup/
Restoring shard 367 live from backup ***.tar.gz
...

authors: ErnoL HeathKang galindro ivanpricewaycom teu


text:
Fix config typo

@tehmaspc have you signed the CLA?
https://influxdata.com/community/cla/
Thanks!

@jsternberg - done; just signed. thanks!

Thanks!

authors: jsternberg tehmaspc


text:
Implement value-transform functions such as sin() and abs().

This adds 17 "value transforms" to InfluxQL, where these are defined as functions which operate on the value of one datapoint at a time, leaving the timestamp unaffected.
The full list of functions added is: abs, sin, cos, tan, asin, acos, atan, log, log10, exp, sqrt, rad2deg, deg2rad, pow, ceiling, floor, round.
All of these work for float and integer datatypes.  You get integer points back where possible (e.g. round(my_float) or abs(my_int)), otherwise you get float points.
Internally, they are called via the Auxiliary Value route rather than as standard Calls (which are basically for aggregators, selectors and other things which don't necessarily return a new value for each input point).  This means that they play nicely with multi-field queries, selectors, nesting and subqueries; the following queries on the standard dataset all produce the expected results:
SELECT water_level, 3 * abs(water_level - 100.4) AS fred FROM h2o_feet LIMIT 3

SELECT max(water_level), sqrt(abs(water_level)) FROM h2o_feet

SELECT -4 * abs(fred) FROM (SELECT mean(water_level) AS fred FROM h2o_feet)

SELECT mean(*) FROM (SELECT abs(water_level) FROM h2o_feet)

More unit tests are required, but implementing the tests seems to be harder than implementing the code, particularly for more complex queries like the ones above.  Any pointers or examples welcome.
Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated
[x] Provide example syntax
[x] [InfluxData Documentation] https://github.com/influxdata/docs.influxdata.com/pull/1097

Addresses parts of #5930 #659 #3691.

Anyone looked at this? @rbetts ?

We'll add this to the work queue for review. However, in the short term it needs to be rebased and it needs test cases for argument and type validation to the functions that are added.

Closing this in favor of #9424. @Tomcat-Engineering I'm sorry it took so long for this feature and for not properly looking at this PR, but we refactored the engine to make this kind of functionality much easier to validate and implement. #9424 implements only the basic trigonometry functions, but we would be very interested in adding more value transform functions if you have the time. Please refer to that PR to see the new method. Thanks.

#9499 is the PR. #9424 is the issue.

@jsternberg no worries, glad the feature made it in eventually, and good that you came up with a neater way of integrating with the engine.  I might have a look at adding some of the other value transforms if I have time... I assume that the mechanism for implementing value transforms is now considered stable enough to add more?

Yes. I would consider it stable enough.

authors: Tomcat-Engineering fdhex jsternberg rbetts


text:
Add more math functions to influxql

Basic trig functions were recently added by @jsternberg.  This PR adds a load more, using the same mechanisms.
New functions

abs(x)
asin(x), acos(x), atan(x), atan2(x, y)
exp(x), log(x), log10(x)
pow(x, y), sqrt(x)

Required for all non-trivial PRs

[x] Sign CLA (if not already signed)

Required only if applicable
You can erase any checkboxes below this note if they are not applicable to your Pull Request.

[x] [InfluxData Documentation] see existing ticket

I'm going to review this, but before I do, I just want to point out this: +120, -27.
🎉 🎉 🎉
I'm very happy. I hope this refactor made it much easier to implement these for you.

Also, can you add a test for each of the new functions? Just having one query that is valid in TestCompile_Success and one in the failures is good. It just ensures that the compiler is tested at least a little bit.

@Tomcat-Engineering for function names, we should just match the functions Prometheus has.
So exp() is fine, but we should have log10(x), log2(x), and ln(x) too. If we want a generic log function, we can do log(x, y) since that function isn't used in Prometheus. The primary reason is to avoid confusion between the two platforms.

@Tomcat-Engineering whenever you have the time, this PR is relevant to the NaN question: #9637.
This came about when a regression test caught stddev() acting weirdly because it previously returned null and started getting filled with the fill value after the regression. Likely, we're going to handle it by allowing NaN to propagate through the system, but have the cursor return a sentinel null value so NaN will get encoded as null in the JSON. I think this is likely relevant to what we should do with other NaN values.
That likely means you don't have to check for NaN. It'll be handled as a null value which is the equivalent of return nil, true anyway.

It would be nice to have some unit tests which actually check the values and datatypes returned from these functions... if you guys provide some for the trig functions that you implemented, I'm happy to extend the coverage to these new functions.  The scaffolding required (as seen in select_test.go) looks somewhat complicated so I'm going to let you do that bit!

I'll add a unit test for that. I've been meaning to do that anyway.
I'm thinking of changing the interface for call functions though. I thought the original interface would work well, but I've been finding the interface from the type mapper is much better and easier for construction. So here's the interface I'm thinking of changing it to:
type CallValuer interface {
    Call(name string, nargs int, args func() []interface{}) (interface{}, bool)
}

So similar to the current interface, but it passes the name of the function, the number of arguments, and a function that can be used to obtain the arguments. The purpose is to make it so that the call arguments aren't evaluated until the function knows it can handle them.
Thoughts?

I've now updated the current code to use the new interface: https://github.com/influxdata/influxdb/pull/9666

Hi @Tomcat-Engineering, do you have time to complete this? We are planning to do a release candidate probably early next week and I would like to get this included. I can help finish this up if you don't have the time.

Thanks @Tomcat-Engineering for your help in starting this. I did the work of adapting my comments and then squashing it. I'm going to merge it now.
Once again, thank you so much for your help in getting these additional functions in. We're going to get them into 1.6.

authors: Tomcat-Engineering jsternberg


text:
InfluxDB 0.9.4.2: What's the exact sql to query the last absolute hour data in InfluxDB?

For example,
Now is 2015-10-26 10:10:00
The expect period is from 2015-10-26 09:00:00 to 2015-10-26 10:00:00
Thanks,
Vincent

This is neither a bug nor a feature request. Please send questions to the mailing list, influxdb@googlegroups.com
The answer is that if you want an exact time range you must specify absolute time ranges. For example, SELECT * FROM foo WHERE time >= '2015-10-26 09:00:00' and time <= '2015-10-26 10:00:00'

authors: VincentAtC beckettsean

repo: influxdb/influxdb


text:
Account sequence mismatch error during a tx raw transactions

Crate
ibc-relayer
Summary of Bug
While trying to execute a tx raw conn-try transaction between cosmoshub-4 and irishub-1 got a couple of "acount sequence mismatch" errors (see below).
Version
Branch: master
Commit: commit 1adb18d3d4c70239115bc5d98abeb8d114cf9c15
Steps to Reproduce
When executing a conn-try connection, there was a timeout. When trying again a couple of times, got a account mismatch error.
hermes tx raw conn-try irishub-1 cosmoshub-4 07-tendermint-4 07-tendermint-157 -s connection-201
May 10 15:24:16.515  INFO ibc_relayer_cli::commands: Using default configuration from: '.hermes/config.toml'
May 10 15:24:16.571  INFO ibc_relayer::event::monitor: starting event monitor chain.id=cosmoshub-4
May 10 15:24:16.593  INFO ibc_relayer::event::monitor: starting event monitor chain.id=irishub-1
May 10 15:24:30.699  WARN ibc_relayer::event::rpc: error while building event send_packet.packet_data
Error: tx error: failed during a transaction submission step to chain id irishub-1 with underlying error: RPC error to endpoint http://iris.decentrox.com:26657/: RPC error to endpoint http://iris.decentrox.com:26657/: Internal error: timed out waiting for tx to be included in a block (code: -32603)
ubuntu@ip-172-31-36-51:~/relayer/ibc-rs$ hermes tx raw conn-try irishub-1 cosmoshub-4 07-tendermint-4 07-tendermint-157 -s connection-201
May 10 15:24:39.273  INFO ibc_relayer_cli::commands: Using default configuration from: '.hermes/config.toml'
May 10 15:24:39.283  INFO ibc_relayer::event::monitor: starting event monitor chain.id=cosmoshub-4
May 10 15:24:39.293  INFO ibc_relayer::event::monitor: starting event monitor chain.id=irishub-1
Error: tx error: failed with underlying cause: tx response error: check_tx reports error: log=Log("account sequence mismatch, expected 4, got 3: incorrect account sequence")
ubuntu@ip-172-31-36-51:~/relayer/ibc-rs$ hermes tx raw conn-try irishub-1 cosmoshub-4 07-tendermint-4 07-tendermint-157 -s connection-201
May 10 15:25:08.093  INFO ibc_relayer_cli::commands: Using default configuration from: '.hermes/config.toml'
May 10 15:25:08.103  INFO ibc_relayer::event::monitor: starting event monitor chain.id=cosmoshub-4
May 10 15:25:08.113  INFO ibc_relayer::event::monitor: starting event monitor chain.id=irishub-1
Error: tx error: failed with underlying cause: tx response error: check_tx reports error: log=Log("account sequence mismatch, expected 4, got 3: incorrect account sequence")
ubuntu@ip-172-31-36-51:~/relayer/ibc-rs$ hermes tx raw conn-try irishub-1 cosmoshub-4 07-tendermint-4 07-tendermint-157 -s connection-201
May 10 15:25:43.915  INFO ibc_relayer_cli::commands: Using default configuration from: '.hermes/config.toml'
May 10 15:25:43.949  INFO ibc_relayer::event::monitor: starting event monitor chain.id=cosmoshub-4
May 10 15:25:43.971  INFO ibc_relayer::event::monitor: starting event monitor chain.id=irishub-1
May 10 15:25:45.154  WARN ibc_relayer::event::rpc: error while building event send_packet.packet_data
May 10 15:25:52.767  WARN ibc_relayer::event::rpc: error while building event send_packet.packet_data
May 10 15:25:52.767  WARN ibc_relayer::event::rpc: error while building event send_packet.packet_data
Error: tx error: failed during a transaction submission step to chain id irishub-1 with underlying error: RPC error to endpoint http://iris.decentrox.com:26657/: RPC error to endpoint http://iris.decentrox.com:26657/: Internal error: timed out waiting for tx to be included in a block (code: -32603)

In theory the account sequence is retrieved before a transaction, so there might be some concurrency issue when getting the sequence and submitting the transaction ?
Acceptance Criteria
No account mismatch should appear.

For Admin Use

[X] Not duplicate issue
[X] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

If the conn-try was the only command you were doing there shouldn't be any concurrency.
One possible scenario  (as this is a checkTx error) is that the latest sequence number is queried from the full node before indexing is finished for the block that includes a previous Tx using the same sequence.
I am not sure we can do much for the tx raw commands other than adding retries to them which we don't want as these are exactly the kind of scenarios we want them to expose.
In the hermes create connection... command there are retries that should mitigate this problem.

authors: ancazamfir andynog

repo: informalsystems/ibc-rs


text:
add the work-in-progress example after Solidity's SimpleAuction

Adding an interesting example of how Quint could be used to model a Solidity contract called SimpleAuction (from the Solidity intro). This example requires another pass, when we implement a few missing features (e.g., constant substitution). However, it is already a valuable example, and it can help new users in faster onboarding.
Every smart contracts turns into an interesting case study. So I'd like to merge this one before running out of time budget, spent 6 hrs on this one.

[x] Tests added for any new code
[x] Entries added to the respective CHANGELOG.md for any new functionality

We should think more about this strategy of using records to define the state. It makes the lack of unchanged helpers less annoying, but also takes power away from the effects checker (i.e. there's no checking for multiple or unbalanced record updates). I feel like if we ever find a nice way to compose states/specs and embed it into the language, then we won't need to resort to this. Just something I've been keeping in mind.

Yep, we definitely have to understand the emerging idioms :)

repo: informalsystems/quint


text:
Inconsistent id used in record page

A while ago we changed the makeSafeIdAttr functionality to properly modify the schema/table/column names that we're attaching to different models.
But it seems like we're not doing this consistently. For example, in record.html we're not using this function for the row id.
We should

[x] make sure we're consistently using this function (makeSafeIdAttr) in all the places that we're creating id/class attributes.
[ ] decide whether we want to use name or displayname. I saw different places in the code using different attributes.
[ ] Add c_${name || displayname} to the <tr> entity rows in the main section

currently similarly used in recordset table on the <th> element
this will be the new format and keep old values support backwards compatibility

[ ] make sure test cases are stable based on changes to use name instead of displayname
[ ] modify the custom-css styles that are used in different deployments to be aligned with the new change.

so new and old styles can coexist to prevent a regression in deployments that may have used c_hash with a source key also defined

We previously discussed this when talking about custom styles for different projects. More notably in the case of RBK/Gudmap. When we had that discussion, it was pointed out that the "displayname" may not be unique whereas the name should be. https://github.com/informatics-isi-edu/chaise/issues/1525#issuecomment-392986536
Related PR to make sure we don't break functionality of using name instead for custom styles:
https://github.com/informatics-isi-edu/rbk-www/pull/3/files

displayname:

What you see so it's easier to understand what to use in class
clear rule for replacing special characters. - replace space and other characters
less model awareness
might have HTML

i.e. Title

name:

case sensitive
more "aware" of the model
name will remain constant while displayname may be updated at any time
unique

Add c_* and other information to top section of record app.
Apply this to recordedit as well.

ermrestJS decides column.name as:

sourcekey
default heuristic to generate hash based on path (current implementation)

chaise uses column.name

Update for playwright:

bullet 2 above

use name or displayname?

Accordion.Item uses #rt-heading-${displayname}
<tr> in RecordMainSection uses .entity-row-${displayname}

also has #row-${column.name}

entity value <td> in <tr> of RecordMainSection uses #entity-displayname

PR #2526 fixes the issue mentioned in the first bullet above.
Any further changes:

require more in depth discussion as to which of the options are "better"
changing any of the above id or classes might break backwards compatibility for deployments with custom CSS

includes prepending c_

source-key changes would not be a simple change

authors: RFSH jrchudy

repo: informatics-isi-edu/chaise


text:
Font Awesome scripts

We decided to move away from font awesome and use bootstraps glyphicons. I noticed that font awesome is still loading css rules that are overriding bootstrap css rules.

I think this is  fixed by @howdyjessie but hasn't been merged due to the font-file issue.
I have fixed the issue and pushed it to her branch. Changes can be seen here
https://dev.isrd.isi.edu/~chirag/chaise/recordset/#1/legacy:dataset@sort(accession,id)?limit=15

Yep @chiragsanghvi is correct. The branch in question is update-icons, and this issue is tracked by #789. Now that @chiragsanghvi fixed the font file warnings I had a problem with earlier, I've opened PR #804 for review, and I'll close this issue for now to avoid duplicating #789.

authors: chiragsanghvi howdyjessie jrchudy


text:
Run the command on the slack channel, only the information of the corresponding cluster is displayed.

This is very useful bot to operate kubernetes cluster.
Thanks for making it.
I suggest an improvement to make this bot better.
This is suggestions:
Running the botkube command on the slack channel, only the information of the corresponding cluster is displayed.

Hey @zodiac12k,
Thanks for using BotKube :). We have a couple of designs in mind for multiple cluster support. We will soon add the support once we finalize the design.

Fixed with https://github.com/infracloudio/botkube/pull/39

repo: infracloudio/botkube


text:
TLS configurations with self-hosted Cloud Pricing API

Self-hosted Cloud Pricing API users of GitHub Actions (or other CI/CD integrations), need a way to:

Use something like INFRACOST_TLS_VERIFY=false (similar to what docker supports) to disable TLS verification for testing. Given users went through the trouble of generating a cert, this option only seems useful for testing.
Have env variables or flags or configure keys for the following so users could provide the cert files (again, similar to what docker supports). On CI/CD, users would have to have a step in the GH Action that writes the cert files before Infracost runs.

      --tls-ca-cert string   Trust certs signed only by this CA (default "/Users/ali/.docker/ca.pem")
      --tls-cert string     Path to TLS certificate file (default "/Users/ali/.docker/cert.pem")
      --tls-key string      Path to TLS key file (default "/Users/ali/.docker/key.pem")

Note for community:
Please 👍 if you'd like to upvote this or receive updates.

Trying to hack through this one - https://github.com/njculver/infracost/tree/feat/tls-configuration

@aliscott any thoughts on the interface changes for this?

Sorry I dropped the ball on this one. Have been looking at other tools - here's the options they have:
Docker
--tls                Use TLS; implied by --tlsverify
--tlscacert string   Trust certs signed only by this CA (default "/Users/ali/.docker/ca.pem")
--tlscert string     Path to TLS certificate file (default "/Users/ali/.docker/cert.pem")
--tlskey string      Path to TLS key file (default "/Users/ali/.docker/key.pem")
--tlsverify          Use TLS and verify the remote

Redis
--tls              Establish a secure TLS connection.
--sni <host>       Server name indication for TLS.
--cacert <file>    CA Certificate file to verify with.
--cacertdir <dir>  Directory where trusted CA certificates are stored.
                    If neither cacert nor cacertdir are specified, the default
                    system-wide trusted root certs configuration will apply.
--insecure         Allow insecure TLS connection by skipping cert validation.
--cert <file>      Client certificate to authenticate with.
--key <file>       Private key file to authenticate with.
--tls-ciphers <list> Sets the list of prefered ciphers (TLSv1.2 and below)
                    in order of preference from highest to lowest separated by colon (":").
                    See the ciphers(1ssl) manpage for more information about the syntax of this string.
--tls-ciphersuites <list> Sets the list of prefered ciphersuites (TLSv1.3)
                    in order of preference from highest to lowest separated by colon (":").
                    See the ciphers(1ssl) manpage for more information about the syntax of this string,
                    and specifically for TLSv1.3 ciphersuites.
--raw              Use raw formatting for replies (default when STDOUT is

Helm
--ca-file string             verify certificates of HTTPS-enabled servers using this CA bundle
--cert-file string           identify HTTPS client using this SSL certificate file
--insecure-skip-tls-verify   skip tls certificate checks for the repository
--key-file string            identify HTTPS client using this SSL key file

For us I think it makes sense to make these infracost configure values initially instead of flags since that where we set the pricing_api_endpoint. Here's my idea for the names we should use:

tls_insecure_skip_verify
tls_ca_cert_file
tls_cert_file
tls_key_file

@njculver, @alikhajeh1 do we even need to support the client cert and key files initially or is it enough initially to skip the client verification and just allow specifying a CA cert file?

Nice one! infracost configure makes sense, I suppose it can also be used in CI/CD pipelines too.
I don't have an opinion if we can skip the client verification part - if @njculver doesn't need it and it's a lot more work then sure 🤷

@njculver I've opened a PR for adding tls_insecure_skip_verify, tls_ca_cert_file: https://github.com/infracost/infracost/pull/1187.
Let me know what you think and if this will help your use-case.

Sorry for letting this completely fall off my radar - I've been super busy with other things. Personally, I don't need the client certificate validation for my use case either. Skipping verification seems like it's fine for POC/dev usage, allowing a user to provide the CA cert works for self/internal signed certs. The additional client verification would probably be necessary in some more tightly controlled environments but this would be a good starting point from my perspective.

Great, thanks @wilkej and @njculver, we'll ship this in the next release (v0.9.15) which we'll look to release at the end of this week/early next week. I'll let you know when it's released if you'd be willing to try it out!

@wilkej, @njculver the support for tls_insecure_skip_verify and tls_ca_cert_file is now released in v0.9.15. Docs: https://www.infracost.io/docs/cloud_pricing_api/self_hosted/#using-a-self-signed-certificate. Please try it out and let me know if it works well for you 😄

authors: alikhajeh1 aliscott njculver

repo: infracost/infracost


text:
Feat/resolve upstream

syncs upstream changes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 13 committers have signed the CLA.:white_check_mark: dependabot[bot]:white_check_mark: hugorut:x: zackproser:x: iangrunt:x: denis256:x: smaftoul:x: untcha:x: eak12913:x: levkohimins:x: lantern-sam:x: maunzCache:x: MoonMoon1919:x: marinalimeiraYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant hugorut

repo: infracost/terragrunt


text:
🛑 Academusoft is down

In 1c440b1, Academusoft ($SECRET_ACADEMUSOFT) was down:

HTTP code: 503
Response time: 1385 ms

Resolved: Academusoft is back up in 7a71b98.

repo: infraestructuraidt/status


text:
Bing Maps Search

Hi there,
Do you have any sample with Bing Maps and the Search Manager  (Microsoft.Maps.Search) implemented ?
Thanks for your help!
-NC

@nlcano, no we currently do not have support for this in place as part of angular-maps. We do have support for loading modules etc. But you'd have to implement the payloads yourself and then bind the results to the various components.

@thor-schueler: Thanks, I am planning to add support for the Search Feature (and others).
The code listed below works when I use the published package.   I clone and link the package locally, and I am getting the issue below, any help will be appreciated.
Module
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
import { Routes, RouterModule } from '@angular/router';
import { MapModule, MapAPILoader, WindowRef, DocumentRef, BingMapAPILoaderConfig, BingMapAPILoader } from 'angular-maps';
import { environment } from 'environments/environment';
import { BMapDemoComponent } from './bmapdemo.component';
const routes: Routes = [{
path: '',
data: {
title: 'Maps Tests',
urls: [{ title: 'Test', url: '/' }, { title: 'Tests' }, { title: 'Bing Maps' }]
},
component: BMapDemoComponent
}];
@NgModule({
imports: [
CommonModule,
MapModule.forRootBing(),
RouterModule.forChild(routes)
],
declarations: [BMapDemoComponent],
providers: [
{
provide: MapAPILoader, deps: [], useFactory: BingMapServiceProviderFactory
}
],
})
export class BMapDemoModule { }
// Bing Maps
export function BingMapServiceProviderFactory() {
const bc: BingMapAPILoaderConfig = new BingMapAPILoaderConfig();
bc.apiKey = environment.Bing.Maps.Key;
bc.branch = 'experimental';
return new BingMapAPILoader(bc, new WindowRef(), new DocumentRef());
}
Error:
Error: Uncaught (in promise): Error: Unexpected value '[object Object]' imported by the module 'BMapDemoModule'. Please add a @NgModule annotation.
Error: Unexpected value '[object Object]' imported by the module 'BMapDemoModule'. Please add a @NgModule annotation.
at syntaxError (compiler.js:466)
at eval (compiler.js:15088)
at Array.forEach ()
at CompileMetadataResolver.getNgModuleMetadata (compiler.js:15071)
at JitCompiler._loadModules (compiler.js:33486)
at JitCompiler._compileModuleAndComponents (compiler.js:33447)
at JitCompiler.compileModuleAsync (compiler.js:33363)
at CompilerImpl.compileModuleAsync (platform-browser-dynamic.js:230)
at eval (core.js:6441)
at ZoneDelegate.invoke (zone.js:392)
at syntaxError (compiler.js:466)
at eval (compiler.js:15088)
at Array.forEach ()
at CompileMetadataResolver.getNgModuleMetadata (compiler.js:15071)
at JitCompiler._loadModules (compiler.js:33486)
at JitCompiler._compileModuleAndComponents (compiler.js:33447)
at JitCompiler.compileModuleAsync (compiler.js:33363)
at CompilerImpl.compileModuleAsync (platform-browser-dynamic.js:230)
at eval (core.js:6441)
at ZoneDelegate.invoke (zone.js:392)
at resolvePromise (zone.js:824)
at resolvePromise (zone.js:795)
at eval (zone.js:873)
at ZoneDelegate.invokeTask (zone.js:425)
at Object.onInvokeTask (core.js:4620)
at ZoneDelegate.invokeTask (zone.js:424)
at Zone.runTask (zone.js:192)
at drainMicroTaskQueue (zone.js:602)
at

@thor-schueler: Thanks, I am planning to add support for the Search Feature (and others).
I clone and link the package locally, and I am getting the issue _Uncaught (in promise): Error: Unexpected value '[object Object]', any help/guidance will be appreciated.

@nlcano: yeah, linking is tricky. When you link, the entire project gets linked into the node_modules folder of you local project, including the .ts files. So when you build, the ngc compiler will try to compile those file as well (depending on how your tsconfig in the local test project is setup). However, all the references will be screwed up, hence the errors (at least this is what I suspect).
You really have two options here:

build the package in your local clone (npm run prepublish) and then copy the contents of the dist folder into the appropriate place in the node_modules of your local test project (instead of using npm link).  That is what I usually do. Since the dist won't contain the ts files, you'll be in good shape.
adjust the tsconfig file in your local test project to exclude any .ts files in node_modules from the compile.

If you continue to have issues getting it setup, let me know and I'll setup a skype to look at it with you. Once you got a local version, adding the search capabilities will likely include:

Defining a search service contract. (see the abstracts in the services root as go-bys)
Implement the contract for bing (and preferably for google).
Create a component the renders the search box for inclusion in the map. You'd inject the service into the component and the results would probably be an observable that that map host can subscribe to to do appropriate things.

Hope that helps....

Looking for only search box without bing map like autocomplete. When we are trying write in the box will hit the bing api and get the results. If you can advice, how we can achieve it with angular map.

authors: abhishekgupta1991 nlcano thor-schueler

repo: infusion-code/angular-maps


text:
Include all Dockerfiles in the project

I am thinking that it may be practical to include as part of the project all Dockerfiles of images that are used in tests and additionally push all of them under a common namespace in Docker Hub (e.g., scruid/druid-docker, scruid/openresty and scruid/clusterf-chaos-proxy) or in GitHub Package Registry (beta) (tagged as docker.pkg.github.com/ing-bank/scruid/IMAGE_NAME:VERSION).
Dockerfiles will be part the project, will evolve with the project and publishing of the images can become a part of the CI process. Furthermore, when a new feature requires changes to some image (e.g., new version of Druid or some extension) the required change in the Dockerfile can be part of the corresponding PR.
A POC of such change can be found in https://github.com/anskarl/scruid/commit/1917a99df73d6bb7fbea525c0a408d5837093e38 in which:

There are Dockerfiles for Openresty, Druid and Chaos-proxy, along with their configuration files
A utility Makefile for building the required docker images (all together or individually)
Uses GitHub Package Registry (beta)
Just for demonstration purposes of this POC, all docker images are under docker.pkg.github.com/anskarl/scruid/ namespace (should change to docker.pkg.github.com/ing-bank/scruid/)
For space efficiency all images are Alpine-based
Images are highly configurable, for example can change the version of Druid
When running ./services.sh start and some image is not available, it will try to build the image locally

What is missing for the POC:

the preferred Docker registry (Docker Hub or GitHub Package Registry)
the CI instructions to push the images to the registry (should require authentication)

What do you think? Do you find any benefits of making such an addition to the project?

I think this is useful for the robustness of our build and control of our supply chain. On the downside, it makes it a bit more work to update our dependencies, but I think it's a net positive.
I would prefer to use the GitHub Package Registry because it's one fewer third-party.

In https://github.com/anskarl/scruid/commit/7566fe6f2098b31859f57f9ceb22273bb143371e I've added GitHub Actions workflow for building the project similar to the current implementation that uses CircleCI, but the main difference is that it can also build Docker images for all the required external services (e.g., Druid) and pushed to GitHub Package Registry.
As it is also included in the commit message, the changes are outlined below:

similar to the current CircleCI workflow:

workflow is triggered on push or pull request
.ivy2 directory is cached (hashed base on the checksum of build.sbt)
coverage report is being archived

adds docker image publishing to github packages:

credentials are managed by github
no need to have separate user/space on Docker Hub

use of common .env file for both docker-compose and Makefile. The versions of external services (e.g., Druid) are controlled here
the workflow is portable, since forked repos will automatically publish images on their owner space
simplifications on Makefile (no need for latest tag, automatically load the contents of .env file)

With GitHub Actions, the build flow can be handled without CircleCI and it is well integrated with GitHub Package Registry.
Please note that the images in docker-compose in https://github.com/anskarl/scruid/commit/7566fe6f2098b31859f57f9ceb22273bb143371e are  pointing to GitHub Package Registry, therefore the automated tests in CircleCI are failing.

authors: anskarl barend

repo: ing-bank/scruid


text:
Proof of concept for navigation component

Components that require updating:

Navigation

Tech to be used:

UIKit
HTML/SASS
Fontawesome Pro

What is the current behavior:
We currently don't have a navigation component.
What is the new behavior:
Create a proof of concept using HTML/CSS. Take the design PDF and convert it to code. You will be using UIKit as the CSS library along with Fontawesome PRO icons. Any comments you need to make, make them in the discussion of the issue or the implementation issue for this component.
The expected deliverable will be a component that is responsive and mobile ready.
Justification: Vital component

Currently blocked by #36

@saynegrojas once you're ready to pass this one on, let me know here. I think its almost across the finish line - thanks a ton!


text:
Review public interface

Review public interface and the use of pointers on it, deprecating old functions in favor of new ones.
Example:
Deprecate
func New(config *IncogniaClientConfig) (*Client, error)

In favor of
func NewClient(config IncogniaClientConfig) (*Client, error)

Reference: https://github.com/golang/go/wiki/CodeReviewComments#receiver-type

repo: inloco/incognia-go


text:
Build(deps-dev): Bump @babel/core from 7.16.10 to 7.16.12 (#2487)

Pull request opened by the merge tool on behalf of #2487

Merged in f9ddacf2ba2c53f5f03d5ca80135cc4fe11a1715

repo: inmanta/web-console


text:
Add support for resources that have no dryrun possible

Description
closes #2555
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches iso5, master in 0b717575c49f91252686807230d99a086561965c

authors: Stijnkool inmantaci


text:
Make cardano-crypto-class compatible with vector-0.13

Currently building fails with newest version of the vector package, likely due to RoleAnnotations. See discussion in this PR for more context: https://github.com/input-output-hk/cardano-base/pull/325#issuecomment-1290415545
Looks like NoThunks Instance needs to be fixed for SimpleKES and possibly others

Closing as duplicate of #327 (flaky internet caused creation of two identical tickets)

repo: input-output-hk/cardano-base


text:
Usage of asserts

There are a few places in KES implementation where Control.Exception.assert is being used. This has no affect since asserts will never get triggered, because they are removed by the compiler, unless compiled with either -O0 or -fno-ignore-asserts, which is never the case in this repo.
So, we need figure out whats the purpose of those asserts and either remove them in favor of some other mode of failure or make them count with a cabal flag or something. A good example on how latter can be achieved is in the consensus repo.

This is kind of how asserts are supposed to work, but IMO it's a good idea to just enable them (-fno-ignore-asserts) - at the very least for testing, but I think it won't hurt to turn them on in production, too.

authors: lehins tdammers


text:
Cardano db sync takes extremely long to revert a fork block

It takes db-sync more than 3 minutes to revert a fork block, here are db sync's logs:
[db-sync-node:Info:96] [2021-01-22 09:20:35.58 UTC] insertShelleyBlock(Allegra): epoch 243, slot 19740942, block 5242014, hash 649d3a63e41d94003b6d6a1d43325d99b2017042536b48a7dcdf3fb2e66d0f56
[db-sync-node:Info:96] [2021-01-22 09:21:15.68 UTC] insertShelleyBlock(Allegra): epoch 243, slot 19740984, block 5242015, hash 8b601c5e732ee1b0746f21503a4f4741ac072abd920dc2248404d2d5e772e81a
[db-sync-node:Info:96] [2021-01-22 09:21:19.89 UTC] Rolling back to slot 19740942, hash 649d3a63e41d94003b6d6a1d43325d99b2017042536b48a7dcdf3fb2e66d0f56
[db-sync-node:Info:96] [2021-01-22 09:21:19.89 UTC] Deleting slots numbered: [19740984]
[db-sync-node:Info:96] [2021-01-22 09:24:40.42 UTC] insertShelleyBlock(Allegra): epoch 243, slot 19740984, block 5242015, hash 95687df531f8098a0a6aa8d995cb10abcae8e03263157c7bf69298b142a9ff72

On the other hand, cardano node recovers almost instantly:
[af752952:cardano.node.ChainDB:Notice:310] [2021-01-22 09:21:15.36 UTC] Chain extended, new tip: 8b601c5e732ee1b0746f21503a4f4741ac072abd920dc2248404d2d5e772e81a at slot 19740984
[af752952:cardano.node.Mempool:Info:318] [2021-01-22 09:21:15.38 UTC] fromList [("kind",String "TraceMempoolRemoveTxs"),("mempoolSize",Object (fromList [("numTxs",Number 0.0),("bytes",Number 0.0)])),("txs",Array [Object (fromList [("txid",String "txid: TxId {_unTxId = \"bb954b78d19a76a30296275c91dca434b1e10dc6f5bde883ac30f7f85d0fe8d7\"}")]),Object (fromList [("txid",String "txid: TxId {_unTxId = \"ac27e19e84df3207be35ac40855f10b7b7189ba847fefe990e4d6fb16377f1e4\"}")]),Object (fromList [("txid",String "txid: TxId {_unTxId = \"b7068bc1ffcab956c1330cedb1cdc91d00d0ba7de8e800e3b27b2f889e33ebf9\"}")]),Object (fromList [("txid",String "txid: TxId {_unTxId = \"cd7afed7b8a800cdaf6021a151190338f01984570fcda7d4d99b0412a153366c\"}")]),Object (fromList [("txid",String "txid: TxId {_unTxId = \"657968defcc7407b1d39559cce6aecca6f7f33cff1c457519e8c3b8697c5a7f6\"}")]),Object (fromList [("txid",String "txid: TxId {_unTxId = \"844883270d7ab2da8b6cc3874584257567b254bdab03d3b7124199006f05bc5f\"}")])])]
[af752952:cardano.node.ChainDB:Info:310] [2021-01-22 09:21:15.38 UTC] Block fits onto some fork: 95687df531f8098a0a6aa8d995cb10abcae8e03263157c7bf69298b142a9ff72 at slot 19740984
[af752952:cardano.node.ChainDB:Info:310] [2021-01-22 09:21:15.38 UTC] Valid candidate 95687df531f8098a0a6aa8d995cb10abcae8e03263157c7bf69298b142a9ff72 at slot 19740984
[af752952:cardano.node.ChainDB:Notice:310] [2021-01-22 09:21:15.65 UTC] Switched to a fork, new tip: 95687df531f8098a0a6aa8d995cb10abcae8e03263157c7bf69298b142a9ff72 at slot 19740984
[af752952:cardano.node:Info:154672] [2021-01-22 09:21:19.33 UTC] fromList [("time(ps)",Number 3.629532492654353e18),("kind",String "MeasureTxsTimeStart"),("mempoolNumBytes",Number 288.0),("mempoolNumTxs",Number 1.0)]
[af752952:cardano.node.Mempool:Info:154672] [2021-01-22 09:21:19.33 UTC] fromList [("tx",Object (fromList [("txid",String "txid: TxId {_unTxId = \"8ca37de36f49b9d19955f5111827ec0ef7a4ca3f8259d27d95b7671415ce072e\"}")])),("kind",String "TraceMempoolAddedTx"),("mempoolSize",Object (fromList [("numTxs",Number 1.0),("bytes",Number 288.0)]))]
[af752952:cardano.node.Mempool:Info:333687] [2021-01-22 09:21:19.33 UTC] fromList [("tx",Object (fromList [("txid",String "txid: TxId {_unTxId = \"8ca37de36f49b9d19955f5111827ec0ef7a4ca3f8259d27d95b7671415ce072e\"}")])),("kind",String "TraceMempoolRejectedTx"),("mempoolSize",Object (fromList [("numTxs",Number 1.0),("bytes",Number 288.0)])),("err",Object (fromList [("kind",String "BadInputsUTxO"),("error",String "The transaction contains inputs that do not exist in the UTxO set."),("consumed",Number 0.0),("badInputs",Array [Array [String "657968defcc7407b1d39559cce6aecca6f7f33cff1c457519e8c3b8697c5a7f6",Number 23.0]]),("produced",Number 4.9999e10)]))]
[af752952:cardano.node.ChainDB:Notice:310] [2021-01-22 09:21:20.28 UTC] Chain extended, new tip: 930451bb268a5b6933494d8c97f11a32fbbe47d5bc419a58076243e61fb028f9 at slot 19740988
[af752952:cardano.node.ChainDB:Notice:310] [2021-01-22 09:21:24.71 UTC] Chain extended, new tip: 2635bbc5da85ca331437492d1a59d438818fb0b679d459964e46eb5a866df372 at slot 19740993
[af752952:cardano.node.Mempool:Info:318] [2021-01-22 09:21:24.71 UTC] fromList [("kind",String "TraceMempoolRemoveTxs"),("mempoolSize",Object (fromList [("numTxs",Number 0.0),("bytes",Number 0.0)])),("txs",Array [Object (fromList [("txid",String "txid: TxId {_unTxId = \"8ca37de36f49b9d19955f5111827ec0ef7a4ca3f8259d27d95b7671415ce072e\"}")])])]

This has been happening for around 2 weeks, increasing in intensity.

The upcoming 8.0.0 release (should be released early next week) has vastly improved rollbacks (rollbacks as done in PostgreSQL without any Haskell doing any processing). I have seen it roll back from chain tip, right back to the Byron era (over a year of blocks) in under 10 minutes.

The upcoming 8.0.0 release (should be released early next week) has vastly improved rollbacks (rollbacks as done in PostgreSQL without any Haskell doing any processing). I have seen it roll back from chain tip, right back to the Byron era (over a year of blocks) in under 10 minutes.

Here is a rollback with the current improved rolbacks:
[db-sync-node:Info:50] [2021-01-23 09:49:22.66 UTC] Rolling back to slot 19829014, hash 1369c36907c449da8232ee746da9a392feeb0ad114db8ff565981922e54735c9
[db-sync-node:Info:50] [2021-01-23 09:49:22.66 UTC] Deleting slots numbered: [19829066]
[db-sync-node:Info:50] [2021-01-23 09:49:22.68 UTC] Slots deleted

So according to the logs, the rollback happened in less than a second.

Here is a rollback with the current improved rolbacks:
[db-sync-node:Info:50] [2021-01-23 09:49:22.66 UTC] Rolling back to slot 19829014, hash 1369c36907c449da8232ee746da9a392feeb0ad114db8ff565981922e54735c9
[db-sync-node:Info:50] [2021-01-23 09:49:22.66 UTC] Deleting slots numbered: [19829066]
[db-sync-node:Info:50] [2021-01-23 09:49:22.68 UTC] Slots deleted

So according to the logs, the rollback happened in less than a second.

This is fixed in the 8.0.0 release (probably today).

This is fixed in the 8.0.0 release (probably today).

authors: erikd xdzurman

repo: input-output-hk/cardano-db-sync


text:
Switch to use separate hedgehog-extras repository

This would allow this project to cache better in cardano-node, and also allow for this hedgehog-extras to be used elsewhere, for example cardano-entropy.

bors merge

repo: input-output-hk/cardano-node


text:
[CSL-17] Compile CSL under Windows

@georgeee

@georgeee
@arodrigues tried, here is result:

cryptonite package requires eay32 and ssl32 C libs, which are not in Windows
I couldn't get those packages' binaries as doing so in Windows is a bit of a headache - I tried doing it in Cygwin, in MinGW and nothing worked

@georgeee
@me to contact Vincent

@georgeee
Sent mail to Vincent, waiting for reply

@gromak
cryptonite doesn't depend on openssl, but cryptonite-openssl does. eay32 and ssl32 are the name of the libraries on some versions of openssl. if the openssl version library is too recent, the name has changed to the usual crypto and ssl libraries. This is also the exact same building process as HsOpenSSL on Windows btw, which has the exact same .cabal dependency on windows.
You can find binaries version of the openssl dlls (don't use the latest one) here:
https://slproweb.com/products/Win32OpenSSL.html

@arodrigues
@gromak Ah, you are correct - it is {{cryptonine-openssl}}. I didn't catch the entire name of the package when the error message popped up.

@georgeee
It was reply from Vincent, not Ivan :)

@arodrigues
@georgeee is it here on YT?

repo: input-output-hk/cardano-sl


text:
Voting tools signature verification adjustment.

Included voting purpose in  verification process.
After integration tests we discovered that correct signature verification is incorrect. Adding voting purpose to signature verification process fixed the problem

Ahh, this was next on my list to check 😁 good spot. I'll review this as soon as I'm back in front of my PC

Apologies for stepping out and taking you prey :( . This bug was blocking integration tests with GVC, therefore we need a rapid dev and fix

repo: input-output-hk/catalyst-core


text:
Publish specs on github pages

This PR will create a static html file listing the pdf files generated in the build.
A current limitation is that the pdfs need to have unique names, otherwise only one of them is kept.
At the moment,  in master, this is what is happening, because both ledger and midnight pdfs are called PDF.pdf , however this PR  addresses this, so, after it is merged,  the page will show to different pdfs called "cardano-ledger.pdf" and "midnight-example.pdf".
An example of how this page looks like: https://bienpulenta.github.io/formal-ledger-specifications
In order for the github page to be created, we need to change the "Pages" Settings in this repo, and set the deploy-source to branch "gh-pages", like in this example screenshot:

Indeed, force-pushed to rebase


text:
Ml/plt 5384  mintburn dbsync compare

Status: figuring out redeemers is still in progress, but the rest passes the test.

PLT-5384: Main addition is this test here which:

gets a random slot from an existing Marconi mintburn.db
gets [TxMintRow] for that slot
gets [TxMintRow] from a preexisting dbsync postgres database for that slot as well. (The sql query to get these from postgres is this one, confirmed correctness of this on cardano-db-sync's slack channel)
compares them

Managed to find and fix a bug.
This test is meant to be run only manually as there are no pre-existing Marconi nor dbsync databases around in CI. Since the entire cabal component is set to "not buildable" with a flag. To build/run/repl it locally one needs to add --flag '-ci' to the cabal cli, so for example

cabal build marconi-chain-index-test-compare-cardano-db-sync --flag '-ci'
cabal repl marconi-chain-index-test-compare-cardano-db-sync --flag '-ci'
cabal run marconi-chain-index-test-compare-cardano-db-sync --flag '-ci'

will work.

Pre-submit checklist:

Branch

[X] Tests are provided (if possible)
[X] Commit sequence broadly makes sense and have useful messages
[ ] Important changes are reflected in changelog.d of the affected packages
[X] Relevant tickets are mentioned in commit messages

PR

[ ] (For external contributions) Corresponding issue exists and is linked in the description
[X] Targeting main unless this is a cherry-pick backport
[X] Self-reviewed the diff
[X] Useful pull request description
[X] If relevant, reference the ADR in the PR and reference the PR in the ADR
[X] Reviewer requested

@koslambrou @berewt So it looks like I won't be able to finish this ticket.
The issue that remains is that redeemer hash and data don't always match between marconi and dbsync (if you set it to Nothing on both marconi and dbsync results then the test succeeds). The funny part being that they sometimes don't match. Might be worth it to double-check the sql query with dbsync team and also and maybe ledger or plutus-core team on whether the redeemer we save is correct.
There are TODO items in the test which help to see where it goes wrong.
How to run the test:

sync mintburn indexer on preprod
sync dbsync on preprod
set env variables
(run the test as described in issue description)

repo: input-output-hk/marconi


text:
a place to see updated protocol cddl specs

The chain sync protocol find intersect is updated I guess which is not allowing me to find an intersect on 1.17.0 MC3. I wanted to have a look at the up to date chain sync protocol cddl specs.

There was no change in the protocol, maybe the wallet guys changed the implementation of their chain-sync server.

It is because of the hard fork combinator, closing this issue as it is not related to the chain sync protocol but the ledger spec.

authors: ashisherc coot

repo: input-output-hk/ouroboros-network


text:
TypeError _removeHandlerRef at each run due to impacket's logging error removal

Exception TypeError: "'NoneType' object is not callable" in function _removeHandlerRef at 0x014BDDB0 ignored
without options or with -h, thist error always its present
i work with windows 7 sp1

This issue appears to be resolved.

repo: inquisb/keimpx


text:
PENV-390: fix problem with duplicates

- What I did
fix the problem with duplicates in jet drop
- How I did it
if we achieved topSyncPulse and no data, we receive that we need to jump to the pulse
the main problem is the pulse is some with current, that why we need to check it
- How to verify it
with real platform
- Description for the changelog

Codecov Report

Merging #67 into master will decrease coverage by 0.04%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
- Coverage   73.68%   73.64%   -0.05%
==========================================
  Files          42       42
  Lines        2630     2633       +3
==========================================
+ Hits         1938     1939       +1
- Misses        560      562       +2
  Partials      132      132

Impacted Files
Coverage Δ

etl/extractor/platform_impl.go
76.15% <33.33%> (-1.02%)
:arrow_down:

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 7b5123d...a8b2628. Read the comment docs.

authors: Tsovak codecov-commenter

repo: insolar/block-explorer


text:
Schema in domain contract

insgocc generates domain contract with description of contract set

no need for now

authors: LinnikD Vany

repo: insolar/insolar


text:
Update AnimeCard.xaml

Reduced NextEpisodeIn font size.
Changed TextAlignment to left.

Just noticed in your screenshot, you don't have enough with to show the user rating

i'm merging your pr, but i might change the left padding later.

authors: Bamboozul insomniachi

repo: insomniachi/Totoro


text:
ig: Fix host.Init() workaround flags

Use ParseEarlyFlags() on main to be sure flags from the host package are parsed when host.Init() is called.
How to test
Deploy https://github.com/inspektor-gadget/inspektor-gadget/blob/main/docs/examples/pod-ig.yaml
(be sure the nodeName is removed or updated and the image used is the right one, main or compiled from this branch)
Before this commit
$ kubectl logs ig
error: filesystems tracefs not mounted (did you try --auto-mount-filesystems?)

After this commit
Tracer prints events as expected

I can't make the CI pass. It continues failing in some cases, I'm almost sure it's not related to this change but I don't want to merge it until the CI passes.

I can't make the CI pass. It continues failing in some cases, I'm almost sure it's not related to this change but I don't want to merge it until the CI passes.

It turns out that there was actually an issue https://github.com/inspektor-gadget/inspektor-gadget/pull/2195, it's not a good idea to rerun the tests until they past.

repo: inspektor-gadget/inspektor-gadget


text:
Enabling mntns filters on DNS trace gadget

Enabling the mount namespace filter on the trace/dns gadget
The DNS gadget needs to be filterable by mount namespace (container), otherwise some special containers like CoreDNS will overload the reader side.
This code enables the standard filtering method common with other tracers.

Hi,
Have you found more information why the CPU is overloaded on nodes with coredns?
Slack thead

authors: alban slashben


text:
A.02.07.federated.discovery.service

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
XPATH expression is missing
Proposed Change
Add XPATH reference

This has two pre-requisites that cannot be tested automatically:

the operator of the system under test (probably a Member State) has chosen to implement the federated search option for the Link Discovery Service operation
there are in fact other Discovery Services registered in the service under test (with the intention of federating the search to them)
Only then does Requirement 16 apply
The XPath at which one would then find the linked service advertised is as described in the TG text above the requirement (by reference to OGC CSW ISO AP 10.8..4.13):
/ows:OperationsMetadata/ows:Constraint[name="FederatedCatalogues"/ows:Value - and the service at that URL should pass all the tests!

Then the test type should be changed to "Manual".
Or a new conformance class needs to be introducted in the TG for the federated search option, but that requires an update to the TG first, so not an option for now.

Reading further in TG section 4.3.4.2, the service operator can publish the details in this way (in this section of the GetCapabilities response) even if he has adopted the 'discovery client approach' as an option, instead of 'federated search'. Arguable, this makes no difference to conformance testing.
AgreeL set to 'manual'

authors: PeterParslow cportele jensscheerlinck


text:
Write ATS for TG requirement 44

For each dataset available the OpenSearch description shall contain a "Query" element that has a "role" attribute with the value "example" and "spatial_dataset_identifier_code" and "spatial_dataset_identifier_namespace" attributes together containing unique spatial dataset identifier. The value of the "crs" and "language" attributes shall be set to the values considered as the default ones by the service provider.

Are the "crs" and "language" attributes mandatory? This is not specifically mandated in the requirement, but would make sense.

repo: inspire-eu-validation/ats-download-atom


text:
update the api of get node resoure information in Dashboard UI - [closed]

In GitLab by @sokril on Mar 31, 2020, 01:06
Merges node -> dev

In GitLab by @sokril on Mar 31, 2020, 07:23
closed

repo: inspursoft/board


text:
fix: base_test

What?
Test base trainer component
Why?
Comprehensive testing on JAX mava systems
Extra
The only thing to test in the base class seems to be the names of the components. The actual functions are tested in the other classes?
Closes #532

Thanks for this Siddarth. There's actually just nothing to test here, so that's my bad for creating an issue for it.
Would you mind please just resolving the issue with a comment akin to "Nothing to test" and moving on to another test instead?

repo: instadeepai/Mava


text:
Index trajectories at particular index from buffer

Can we get trajectories at particular index from the TrajectoryBuffer or ItemBuffer. Something like buffer.get_trajectory(state, trajectory_index), since buffer.sample(state, rng_key) returns a random slice from the buffer.

You would have to specify the batch index as well as the starting time index but this is pretty easy functionality to add.

authors: EdanToledo shariqfz

repo: instadeepai/flashbax