text:
How to remove right space?

my options...
<LineChart
  data={{
    labels: ['January', 'February', 'March', 'April', 'May', 'June'],
    datasets: [
      {
        data: [
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
        ],
      },
      {
        data: [
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
          Math.random() * 100,
        ],
      },
    ],
  }}
  width={Dimensions.get('screen').width}
  height={300}
  chartConfig={{
    backgroundGradientFrom: 'white',
    backgroundGradientTo: 'white',
    backgroundGradientFromOpacity: 0,
    backgroundGradientToOpacity: 0,
    decimalPlaces: 2,
    color: () => 'black',
    labelColor: () => 'black',
    propsForLabels: {
      fontSize: '11',
    },
  }}
  withHorizontalLabels={false}
  withInnerLines={false}
  withOuterLines={false}
  bezier
  style={{
    paddingRight: 0,
  }}
/>

Did you solved the issue ? I am facing the same issue

Same issue

repo: indiespirit/react-native-chart-kit


text:
Bookmarklets not working

When I like or repost a tweet, specifically this one:
https://twitter.com/modacitylife/status/1025045893660078080
The bookmarklet posts to my site, but this is happening:

post kind is note
response properties are invisible in post editor (but appear empty when you change post kind)
bridgy does nothing

Expected:

proper post kind
response properties filled
bridgy did its magic

Additionally, I don't know if this is by design, the text from the original tweet is entered to the post title (I want it to be empty). The post body has an [embed] shortcode. But if you use the Semantic Linkback plugin, this is not required. Then the tweet will show twice.

Possibly related?
https://github.com/dshanske/indieweb-post-kinds/issues/198

source: gharchive/issue

repo: indieweb/wordpress-indieweb-press-this

license_type: permissive

license_source: github-api


text:
Improve testing the new implementation of console authorization & plans

Created by: @bayegan Nov 23 2021 at 15:17 CET
Last updated: Jul 18 2022 at 11:52 CET
ClickUp ID: IK-1850
To ensure that we support authorization in the console, implement the console authorization model as established in previous sprints.
Acceptance criteria:
Define and document requirements for a service account/authorized user
Implement ability to delegate access to authorized user/service account

Commented by: @bayegan Nov 15 2021 at 01:16 CET
@yetizer : this feature is pretty urgent, if not already resolved. if possible, i'd like to be assigned or use such a user to test and setup in our staging area, before we can do it in production. cc @marvinkite

Commented by: @bayegan Nov 23 2021 at 15:17 CET
Need input on how to automate testing for the new plans

Commented by: @bayegan Nov 23 2021 at 15:18 CET
Unit tests are currently taking too long to run

Commented by: @bayegan Dec 06 2021 at 14:11 CET
Pavel har verified that new permissions are working in local setup. No longer applies.


text:
How can I update Laravel session data using Inertia Vue?

I have recently migrated from Laravel Livewire to Laravel Inertia Vue. During the course while using Livewire, I created a trait called WithPerPagePagination then created a public variable of perPage with the default value of 10 and mounted the value to the session $this->perPage = session()->get('perPage', $this->perPage);. Then with the help of lifecycle hook, created a function method updatedPerPage($value) now when ever the perPage variable is updated the value will be passed into the session using session()->put('perPage', $value); and then finally applying the pagination to the query return $query->paginate($this->perPage);. The perPage variable is wire modeled to the select input in the blade frontend.
WithPerPagePagination Trait
trait WithPerPagePagination
{
    use WithPagination;

    public $perPage = 10;

    public function mountWithPerPagePagination()
    {
        $this->perPage = session()->get('perPage', $this->perPage);
    }

    public function updatedPerPage($value)
    {
        session()->put('perPage', $value);
    }

    public function applyPagination($query)
    {
        return $query->paginate($this->perPage);
    }
}

Now in the case of Inertia Vue, how can I put the updated value of per_page into the session, from the frontend and get the above behavior. Now for the Inertia Vue application, I have defined a per_page variable within the index method, $request->has('per_page') ? $request->per_page : 5; and using it within the query as in paginate($per_page) and passing it as a prop, to the frontend. Later in the frontend, initializing the prop per_page with the type Number, and creating and returning data, paginate: { per_page: this.per_page }, then creating a method initPerPage() returning this.$inertia.replace(route('users.index', { per_page: this.paginate.per_page })). And finally, v-modeling to paginate.per_page and if whenever there is a change, run initPerPage. This method replaces the url of the route with the desired per_page value selected.
User Controller
public function index(Request $request)
{
    $per_page = $request->has('per_page') ? $request->per_page : 5;
    $users =  User::query()
                ->select('id', 'name', 'email', 'role_id', 'created_at')
                ->when($request->search, fn($query, $search) => $query->where('name', 'like', '%'.$search.'%'))
                ->paginate($per_page)
                ->withQueryString();

    return Inertia::render('Backend/Management/AudienceManagement/Users/Index', [
        'per_page' => $per_page,
        'users' => $users
    ]);
}

User Index Vue
<template>
    <input-group inline>
        <input-select v-model="paginate.per_page" @change="initPerPage" placeholder="Per Page">
            <option value="5">5</option>
            <option value="10">10</option>
        </input-select>
    </input-group>
</template>

<script>
    import InputGroup from '@/Components/Custom/Input/Group'
    import InputSelect from '@/Components/Custom/Input/Select'

    export default {
        components: {
            InputGroup,
            InputSelect
        },
        props : {
            per_page: {
                type: Number
            }
        },
        data() {
            return {
                paginate: {
                    per_page: this.per_page
                }
            }
        },
        methods: {
            initPerPage() {
                this.$inertia.replace(route('users.index', { per_page: this.paginate.per_page }))
            }
        }
    }
</script>

Now with my current Inertia Vue approach, as soon as the user changes the per_page select input, the selected value will be added with the parameter per_page=value to the url, which makes it work, but as the per_page value is not stored into the session, whenever I refresh the page, or redirect back to the page, the per_page value is back to default. Please help me here to create the same behavior as in Livewire. Thank you for your time.

Same problem here.
Did u find a solution?

@toxifiedmatrix is this still needed? You can just do this from the UserController, where you render the Inertia component -- just put the value in session and resolve it from there if no value is specified.
Please close the issue if this has been resolved to help maintainers.

Hey there,
We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

authors: MrEko crnkovic jessarcher toxifiedmatrix

repo: inertiajs/inertia-laravel

license: MIT


text:
Pagination, i.default is not a function

Hi, I'm getting a strange error when attempting to implement pagination in a Laravel/Interia setup. The key difference between the pingcrm demo and my app is that I'm using "@inertiajs/inertia-vue3": "^0.3.5". It works fine if I use standard links but the following
<template v-for="link in links">
 				 				<inertia-link v-else 		              class="mr-1 mb-1 px-4 py-3 text-sm leading-4 border rounded hover:bg-white focus:border-indigo-500 focus:text-indigo-500" 		              :class="{ 'bg-white': link.active }" :href="link.url" v-html="link.label" /> 			</template>
Is throwing a Uncaught (in promise) TypeError: i.default is not a function error.
The controller I'm using for reference:
` $categories = DB::table('categories')->latest()->paginate(5);
    return Inertia::render('Admin/Categories/Index', [
        'categories' => $categories
    ]);`

I believe I found my answer in the vue3 hacking branch. Fingers crossed.

Had the same issue just now, fixed it by removing v-html and using the closing tag
<inertia-link v-else class="mr-1 mb-1 px-4 py-3 text-sm leading-4 border rounded hover:bg-white focus:border-indigo-500 focus:text-indigo-500"                               :href="link.url">                     {{ link.label }}                 </inertia-link>

Had the same issue just now, fixed it by removing v-html and using the closing tag
<inertia-link v-else class="mr-1 mb-1 px-4 py-3 text-sm leading-4 border rounded hover:bg-white focus:border-indigo-500 focus:text-indigo-500" :href="link.url"> {{ link.label }} </inertia-link>

Thanks! I'll try it tonight.

The {{ link.label }} escapes your characters, so for the << prev and next >> buttons, I had to put that in a span inside the inetia-link

Yo di con esta solución (  v-html="link.label" ), ya que mostraba: » «

authors: ed-mor meatjasenmp peckanthony

repo: inertiajs/pingcrm


text:
The best way to use the TextInput Component methods?

What's the best way in calling the methods in the TextInput Component?
methods: {
    focus() {
      this.$refs.input.focus()
    },
    select() {
      this.$refs.input.select()
    },
    setSelectionRange(start, end) {
      this.$refs.input.setSelectionRange(start, end)
    },
  },

Right now I'm calling it in the component mounted, while adding $attrs like so
<text-input v-model="form.email" :error="form.errors.email" label="Email" type="email" isFocused="focus"/>

  mounted() {
    if (this.$attrs.isFocused) {
      this.focus()
    }
  },

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


text:
Design a logo for Inexor flex

Inexor flex is a keyword that stands for NodeJS integration in Inexor.
We need a cool logo in corporate design.

How about this one?

Need feedback from @a-teammate  @Fohlen @aschaeffer @Croydon.

inexor flex is not more a brand than inexor core, imo btw

Looks nice. What font did you use there?

It's not a font I created this using geometric approximations in Inkscape.

Can you add it to https://github.com/inexorgame/artwork/tree/master/logo please?

authors: Croydon IAmNotHanni a-teammate

repo: inexorgame/inexor-core

license: Zlib


text:
[Question]: What is the YOUR_ACCESS_TOKEN of API

Describe your problem
部分API接口使用API里面创建的token 可以，但是这个接口/api/v1/dataset/{dataset_id}/retrieval，使用API里面创建的token或者user表里面的access_token里面都不行。示例：(ragflow) ubuntu@ubuntu-Super-Server:/data/ht/ragflow/python_api$ curl --request POST
--url http://10.0.169.144:9380/api/v1/chat
--header 'Content-Type: application/json'
--header 'Authorization: Bearer ragflow-QzYmQzOTdjOGEwMDExZWZhOTI0MDI0Mm'
{"data":null,"retcode":100,"retmsg":"<MethodNotAllowed '405: Method Not Allowed'>"}

I suppose you are talking about this document: https://github.com/infiniflow/ragflow/blob/main/api/http_api.md. These API is under development now. When it's available, we will announce and let you know.

By the way, we intend to create an international community, so we encourage using English for communication. Thank you very much.

authors: JinHai-CN changqingla

repo: infiniflow/ragflow


text:
[Bug]: Infinity Txn conflict

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

RAGFlow workspace code commit ID
n/a
RAGFlow image version
nightly（v0.15.0-17-g35580af8 full）
Other environment information
1.Ubuntu 24
2.Ragflow (config with Infinity engine)

Actual behavior
1.Once upon a local docment is selected (I still havn't press 'confirm' button), Ragserver raised the 3022 error list below. There no any error displayed in the frontend page.
ragflow-infinity  | [13:54:18.257] [28] [error] Table ragflow_dd78793cbfa211efaa260242ac150006_eb856922bfa211ef97d60242ac150006 doesn't exist
ragflow-infinity  | [13:54:18.257] [28] [error] Table ragflow_dd78793cbfa211efaa260242ac150006_eb856922bfa211ef97d60242ac150006 doesn't exist@src/main/query_context.cpp:225
ragflow-infinity  | [13:54:18.257] [28] [error] [THRIFT ERROR]: Table ragflow_dd78793cbfa211efaa260242ac150006_eb856922bfa211ef97d60242ac150006 doesn't exist@src/main/query_context.cpp:225
ragflow-server    | 2024-12-21 21:54:18,257 ERROR    17 (3022, "Table ragflow_dd78793cbfa211efaa260242ac150006_eb856922bfa211ef97d60242ac150006 doesn't exist@src/main/query_context.cpp:225")
ragflow-server    | Traceback (most recent call last):
ragflow-server    |   File "/ragflow/api/apps/kb_app.py", line 107, in update
ragflow-server    |     settings.docStoreConn.update({"kb_id": kb.id}, {"pagerank_fea": req["pagerank"]},
ragflow-server    |   File "/ragflow/rag/utils/infinity_conn.py", line 430, in update
ragflow-server    |     table_instance = db_instance.get_table(table_name)
ragflow-server    |   File "/ragflow/.venv/lib/python3.10/site-packages/infinity/remote_thrift/utils.py", line 403, in wrapper
ragflow-server    |     return func(*args, **kwargs)
ragflow-server    |   File "/ragflow/.venv/lib/python3.10/site-packages/infinity/remote_thrift/db.py", line 113, in get_table
ragflow-server    |     raise InfinityException(res.error_code, res.error_msg)
ragflow-server    | infinity.common.InfinityException: (3022, "Table ragflow_dd78793cbfa211efaa260242ac150006_eb856922bfa211ef97d60242ac150006 doesn't exist@src/main/query_context.cpp:225")

When I start to parse the documentation, the proccess is stop in the stage 'task has been received' over 30 mins without any issues rasied in backend and frontend before the actual parsing process started.  There is no any loading over CPU/MEM/DISK IO.
p.s. I have 20 CPUs and 64G mem, which is running the previous version RAGFLOW perfectly and the dataset was successfuly parsed by previous realsed RAGFLOW.

After chunk has been produced (still havn't finish the whole parsing process), Infinity error 4002 was raised when I try to drop this knowlegebase.

4.During the parsing process, there is a long time waiting（still waiting after 1 hour when I capture the log ） between each stage (from OCR started to Embedding the chunks) without any loading on CPU/MEM/DISK IO.  It seems everything is GOOD but everything is HANGING UP without doing anything. I use the RAGFLOW  nomic-text @ FastEmbeded and SILICONFLOW's chat model in system wide.
ragflow-server    | 2024-12-21 22:38:27,787 INFO     19 task_consumer_0 reported heartbeat: {"name": "task_consumer_0", "now": "2024-12-21T22:38:27.786730", "boot_at": "2024-12-21T21:51:55.278526", "pending": 1, "lag": 37, "done": 1, "failed": 0, "current": {"id": "f605ad3ebfa311efbf9d0242ac150006", "doc_id": "59bb2120bfa311efb8850242ac150006", "from_page": 12, "to_page": 24, "retry_count": 0, "kb_id": "eb856922bfa211ef97d60242ac150006", "parser_id": "book", "parser_config": {"auto_keywords": 3, "auto_questions": 1, "raptor": {"use_raptor": true, "prompt": "\u8bf7\u603b\u7ed3\u4ee5\u4e0b\u6bb5\u843d\u3002 \u5c0f\u5fc3\u6570\u5b57\uff0c\u4e0d\u8981\u7f16\u9020\u3002 \u6bb5\u843d\u5982\u4e0b\uff1a\n      {cluster_content}\n\u4ee5\u4e0a\u5c31\u662f\u4f60\u9700\u8981\u603b\u7ed3\u7684\u5185\u5bb9\u3002", "max_token": 512, "threshold": 0.1, "max_cluster": 64, "random_seed": 0}}, "name": "2023\u5e74\u7248GMP\u6307\u5357-\u8d28\u91cf\u7ba1\u7406\u4f53\u7cfb.pdf", "type": "pdf", "location": "2023\u5e74\u7248GMP\u6307\u5357-\u8d28\u91cf\u7ba1\u7406\u4f53\u7cfb.pdf", "size": 7081164, "tenant_id": "dd78793cbfa211efaa260242ac150006", "language": "Chinese", "embd_id": "nomic-ai/nomic-embed-text-v1.5@FastEmbed", "pagerank": 10, "img2txt_id": "", "asr_id": "paraformer-realtime-8k-v1@Tongyi-Qianwen", "llm_id": "THUDM/glm-4-9b-chat@SILICONFLOW", "update_time": 1734789640003}}

Expected behavior
No response
Steps to reproduce
upload a document and start parsing process.

Additional information
No response

#4207 fixed this.


text:
ISPN-4797 Use getAll for retrieving query results

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

Updated to use ArrayList in the result.

Pulling..

Unfortunately CI didn't get to run on this one, so just running tests manually.

Integrated into master, thanks @gustavonalle !

source: gharchive/pull-request

authors: gustavonalle wburns

repo: infinispan/infinispan


text:
ISPN-13382 Register JMX for Single Port Transport

https://issues.redhat.com/browse/ISPN-13382

@tristantarrant ISPN-11385 Remove remote-command-executor from schema I think you have the wrong JIRA number in this commit.

@tristantarrant but https://issues.redhat.com/browse/ISPN-13385 is related to the REST API: Retrieve a payload with mutable attributes and the value of each

authors: pruivo tristantarrant


text:
🛑 Client Portal is down

In 1009bbf, Client Portal (https://accounts.infinite8.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Client Portal is back up in 37c8ebe.


text:
Cleanup

[x] lint errors clean up (see before/after below)
[x] renaming example/ folder to examples/

Before
After

YOU DID IT!

authors: GantMan mazenchami

repo: infinitered/nsfwjs


text:
Remove tools/ alias from api-guide/client-libraries

I don't think this alias is necessary. I don't think we've ever had client libraries under the tools section.
Originally posted by @sanderson in https://github.com/influxdata/docs-v2/pull/2860#discussion_r671465783

Closed with b39bf036e04c35399c302888bbddec891f9a1136


text:
write() issues

Can someone give me a basic example of how to format the dictionary data?

Look at the README or at the docs: https://influxdb-python.readthedocs.io/en/latest/

There is no example in the README!

Oh.
Are you sure you don't mean to use write_points?

The function that: 'writes data to InfluxDB is write(data, params=None, expected_response_code=204)
My only question was how to I format the data dictionary.
Would it look like: data : { 'measurement,tag=A': value#}?

If you want to write points, use write_points.

authors: aviau dantespe

repo: influxdata/influxdb-python

license: mit

license_source: bigquery


text:
Unpin setuptools to fix travis

Signed-off-by: Matthew McGinn mamcgi@gmail.com

Any ETA on this one?

ETA 25 seconds

authors: aviau clslgrnc xginn8


text:
Bucket list should not display deleted buckets.

Bucket list should not display deleted buckets.

Not able to reproduce this on master

authors: OfTheDelmer mavarius

repo: influxdata/influxdb


text:
About Dashboard Zoom in

How to achieve the expected behavior on influxDB 2.0?
*Expected Behavior
That when one cell is zoomed, then all related cells in the Dashboard will also be zoomed.
*Examples of failure are as follows
Before zoom in

After zoom in

I would confirm that.
It would be a very helpful feature when examining real-time events if all graphs would follow when zooming.
https://community.influxdata.com/t/dashboards-all-graphs-should-follow-the-same-zoom-range/18631

@Franky1 Did you find something that can be configured to achieve this behaviour?

I would wager that in most cases when people look at dashboards they are looking to visually cross correlate graphed data to spot patterns. If the graphs are not aligned that becomes extremely challenging. I would almost say that shared zoom issue is even more important than Shared cursors.
Grafana does not have shared cursors and most of the time I don't notice it too much, but coming back to influxdb occasionally it is super jarring that zoom level is not synchronised.

Lack of shared zoom is a killer issue for me.  I can't think of a time I have ever been looking at time series (mainly large battery systems) data where I didn't want all panels to zoom (and pan) together.

+1 Nudge for this, can't believe it's 4 years and still nothing...

authors: Franky1 IGW84 NonLogicalDev Yu-Hui-Shen fredlemieux yorch


text:
where clause with or doesn't work when both a time and a non-time filter is used

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

insert test,fooTag=0 value=0
insert test,fooTag=0 value=1
select * from test where time=1605046096208082180 or "value"=0 (replace 1605046096208082180 with the time of the second insertion)

Expected behavior:
I should get the same result as select * from test where "value"=0. It's a OR operator so if either filter is true then I should get results.
> select * from test where "value"=0
name: test
time                fooTag value
----                ------ -----
1605046002738391427 0      0

Actual behavior:
No results
Environment info:

System info: Ubuntu 18
InfluxDB version: InfluxDB v1.8.3 (git: 1.8 563e6c3d1a7a2790763c6289501095dbec19244e)

Config:
Copy any non-default config values here or attach the full config as a gist or file.
[meta]
  dir = "/var/lib/influxdb/meta"

[data]
  dir = "/var/lib/influxdb/data"
  wal-dir = "/var/lib/influxdb/wal"

[[collectd]]
  enabled = true
  bind-address = "0.0.0.0:25826"

Another person has ran into the same issue: https://stackoverflow.com/questions/62812878/influxdb-returns-no-results-when-adding-logical-or-condition
A interesting behavior I found is that if both or clauses are true then the query works correctly:
> select * from test where time=1605046002738391427 or "value"='0'
name: test
time                fooTag value
----                ------ -----
1605046002738391427 0      0

The query fails only when the time clause doesn't return any results
> select * from test where time=1605046002738391428 or "value"='0'

Reversing the order doesn't help:
> select * from test where "value"='0' or time=1605046002738391428

Neither does using a tag:
select * from test where "fooTag"='0' or time=1605046002738391428

related issue: https://github.com/influxdata/influxdb/issues/15298


text:
[documentation] Unclear what RESAMLE does for continuous queries

While i can understand what GROUP BY(time) means, I didn't understand what RESAMPLE means, and what is its purpose (both EVERY and FOR).
You might want to write a section in the documentation clarifying that.

And also what does this mean
The time ranges of the CQ results have round-number boundaries that are set internally by the database.

@halt-hammerzeit please file this against the documentation repo. When you do, please describe what is unclear or inadequate about the current CQ docs, as they do discuss RESAMPLE EVERY...FOR...

Done
https://github.com/influxdata/docs.influxdata.com/issues/568

authors: beckettsean halt-hammerzeit


text:
Non-admin users receive forbidden response when making subqueries

I can't make subqueries on any non-admin users. I don't see anything in the documentation about privilege requirements in order to make subqueries. Getting back a forbidden authorization response with the status of "invalid measurement". I attempted with a user that even has ALL privileges for the particular database, but same error. Only after a user is made admin will the subquery work.
System info:
Ubuntu 16.04.1
InfluxDB 1.2.0-1 (from repos.influxdata.com)
HTTP Auth and HTTPS are enabled in influxdb.conf. No other special settings.
Reproduce bug

Setup a test db and user

CREATE DATABASE "testSubQuery"
USE "testSubQuery"
INSERT test,name=tag1 things=30
INSERT test,name=tag1 things=12
INSERT test,name=tag2 things=4
INSERT test,name=tag2 things=9
CREATE USER "testSubUser" WITH PASSWORD 'test'

Note all our users and their admin status

> SHOW USERS
user         admin
----         -----
__admin      true
testSubUser  false

Note our test users privileges (currently none)

> SHOW GRANTS FOR "testSubUser"
database privilege
-------- ---------

Attempt querying data with testSubUser

> SELECT * FROM test
ERR: error authorizing query: testSubUser not authorized to execute statement 'SELECT * FROM test', requires READ on testSubQuery

Makes total sense, user has no privileges.

Give testSubUser READ privileges

> GRANT READ ON "testSubQuery" TO "testSubUser"
> SHOW GRANTS FOR "testSubUser"
database     privilege
--------     ---------
testSubQuery READ

Repeat query with testSubUser

> SELECT * FROM test
name: test
time                name things
----                ---- ------
1486168403498343817 tag1 30
1486168403580866258 tag1 12
1486168403625002589 tag2 4
1486168403775352570 tag2 9

Query works as expected, now a simple GROUP BY test
> SELECT * FROM test GROUP BY "name"
name: test
tags: name=tag1
time                things
----                ------
1486168403498343817 30
1486168403580866258 12

name: test
tags: name=tag2
time                things
----                ------
1486168403625002589 4
1486168403775352570 9

Again as expected. Now simply take this last GROUP BY query and use it in a subquery. This query should be syntactically sound, and is only here for showing the permissions problem. As this query could be easily simplified into 1 query.
> SELECT SUM(things) FROM (SELECT * FROM test GROUP BY "name")
ERR: error authorizing query: invalid measurement: (SELECT * FROM test GROUP BY "name")

Getting authorization problems now. Invalid measurement?

Give testSubUser ALL privileges on DB

> GRANT ALL ON "testSubQuery" TO "testSubUser"
> SHOW GRANTS FOR "testSubUser"
database     privilege
--------     ---------
testSubQuery ALL PRIVILEGES

Repeat query, same error.

> SELECT SUM(things) FROM (SELECT * FROM test GROUP BY "name")
ERR: error authorizing query: invalid measurement: (SELECT * FROM test GROUP BY "name")

Give testSubUser ADMIN privileges

> GRANT ALL PRIVILEGES TO "testSubUser"
> SHOW USERS
user         admin
----         -----
__admin      true
testSubUser  true

Repeat query, now works.

> SELECT SUM(things) FROM (SELECT * FROM test GROUP BY "name")

name: test
time sum
---- ---
0    55

Fixed via #7952

authors: Nicholi jwilder


text:
feat(flux): enable group > min/max pushdown

Backports #21255 and #20994 to keep 1.x and 2.x in sync

Backported in #21285

authors: danxmoran lesam


text:
Update meta service, meta client, and httpd handler

Improve the ping endpoint so that it can optionally check for leader agreement across all meta servers
Add Ping method to the meta client
Fix ClusterID tests
Remove WaitForLeader from meta client and remove unnecessary references to it

cc @corylanou @dgnorton

+1

+1

@pauldix what's the new syntax, if any, for the /ping endpoint? We may need to update docs.
@rkuchan where do we have ping documented?

@beckettsean  This is an endpoint in the new meta service, which probably won't be used by anything outside of InfluxDB.

@beckettsean yeah, this is for the meta service only. However, it will be useful in monitoring/troubleshooting scenarios. If you hit the metaservice HTTP endpoint (which is a new thing)  and get /ping, then you'll get a response from that server with the HTTP bind address that the server thinks is the leader.
If you hit /ping?all=true then the server will hit all the other meta servers in the cluster and verify that they all agree about who the leader is. If there is a discrepancy an error is returned.
@rossmcdonald see above for the new way to monitor raft health. That new ping endpoint is what you'd hit during testing to ensure that the metaservice nodes all agree.

On a side note:  I don't think we should make any backward compatibility guarantees about the meta service HTTP API.

oh no, it's not a published API. Just for internal use. However, if we want
people to be able to do rolling upgrades after 0.10.0, we'll have to make
it backwards compatible. Which I think we should do.
On Fri, Jan 8, 2016 at 7:20 PM, David Norton notifications@github.com
wrote:

On a side note: I don't think we should make any backward compatibility
guarantees about the meta service HTTP API.
—
Reply to this email directly or view it on GitHub
https://github.com/influxdata/influxdb/pull/5319#issuecomment-170166450.

@beckettsean, the only place I've come across it in the docs is on the FEI page.

authors: beckettsean corylanou dgnorton pauldix rkuchan


text:
Fix index inconsistency after deletes

Required for all non-trivial PRs

[ ] Rebased/mergable
[ ] Tests pass
[ ] CHANGELOG.md updated
[ ] Sign CLA (if not already signed)

This fixes an issue where the inmem index would be inconsistent with the data stored on disk.  It also fixes a bug where deletes do not write tombstones for data that should be deleted.
The inconsistency can occur under write load to a measurement and concurrently dropping the measurement.  There is a race where the incoming writes create index entries, but the writes have not hit the cache/wal yet.  The delete completes and removes them series from the index and then the write completes and stores the data on disk.  The end result is that the data is on disk, but the index is inconsistent and is not aware that it exists within the shard.  Restarting the server causes the index to be reloaded and the data appears again.
There wasn't a good way to fix this without significantly reworking how the index and engine work together or introducing a lot of lock contention mainly to handle this cases of deletes.  I went with an approach that refreshes the index from the newly compacted files as well as what is remaining in the cache when the files are installed for use.  This resolves the issue, but there can be a brief period of time between when the the delete removes the series from the index and before the index is refreshed where series can appear missing.

@e-dard All fixed.


text:
if metrics is too many, how to disign db?

if many server metrices , how to design db？
for instance  1000 server   ，each server have 20 metrices ，total 2000个metrics ，how to design db?

I presume you mean how should the metrics be named? Check out the link
below for some advice for the 0.8 release:
http://influxdb.com/docs/v0.8/advanced_topics/schema_design.html
http://influxdb.com/docs/v0.8/api/reading_and_writing_data.html
On Fri, Jan 30, 2015 at 5:39 PM, fengyun.rui notifications@github.com
wrote:

if many server metrices , how to design db？
for instance 1000 server ，each server have 20 metrices ，total 2000个metrics
，how to design db?
—
Reply to this email directly or view it on GitHub
https://github.com/influxdb/influxdb/issues/1462.

Also, this question should be asked on the Google Group here: https://groups.google.com/forum/#!forum/influxdb

authors: otoolep pauldix rfyiamcool

repo: influxdb/influxdb


text:
Fix hostname defaults

This fixes the issue with hostnames being set incorrectly and not being able to attach to the cluster.
We also added explicit defaults for hostname and bind address.  These where already set to this, but by explicitly setting them, they will show up in the default config if you print it via influxd config.

+1

authors: corylanou toddboom


text:
Fixed some Python3 and Django 1.8 warnings

Fix a problem with print.
Fix get_model warning.
Fix urllib2 uninstalled package: replace with urlib3.

@SalahAdDin thanks for your pull request!

repo: infoportugal/wagtail-embedvideos


text:
Enabling Hermes to support more diverse relaying use-cases

Background
Hermes' user base is shifting away from relayer operators towards relayer developers. This is in large part because more non-Cosmos chains are onboarding into the Interchain ecosystem: all these different chains have different relaying use-cases.
In order to cater to these users, Hermes' architecture needs to be opened up such that it can be extended in a flexible and modular fashion to fit different use-cases and relaying strategies. To that end, the Hermes architecture is evolving from a relayer binary into a relay framework in order to enable this. In addition to flexibility and composability, the relayer framework will also expose presets to cater towards common relaying use-cases. This way, users will have a batteries-included option if their relaying use-case is not unique or does not require bespoke features/components.
Q1 Tasks
These are the concrete tasks that we aim to complete by Q1 in order to meet the objectives promised to the ICF:

[ ] #2926

Ongoing Tasks
The following are ongoing tasks that we're making progress on in Q1 but that will also carry over into Q2 and beyond:

[ ] #2952
[ ] #2956

Closing this issue as we'll be keeping track of OKRs directly in the Hermes project board instead of in issues.

repo: informalsystems/hermes


text:
Documentation update for v0.3

[x] [#758]: n/a
[x] New section for start-multi under the commands, right now it's only mentioned in tutorials: @romac
[ ] [#784] ~@adizere~ @romac
[ ] [#862]: partial update
[ ] [#786]: @ancazamfir
[x] [#785]
[ ] [#794]: @ancazamfir
[x] [#811]: n/a
[x] [#840]
[x] [#851]: n/a
[x] [#854]: n/a
[x] [#863]: n/a
[x] [#869]: n/a
[x] [#871]: n/a
[x] [#873]: @ancazamfir
[x] [#878]: n/a
[x] [#909]: n/a
[x] clarify optimistic sends and handshake are not supported @adizere (handled in the feature matrix)
[x] update feature matrix @adizere
[ ] add minimum SDK version
[x] update Hermes version to 0.3.0

For contributor use:

[ ] Updated the Unreleased section of CHANGELOG.md with the issue.
[ ] If applicable: Unit tests written, added test to CI.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

The version in the title of the guide should be updated to v0.3.0

The version in the title of the guide should be updated to v0.3.0

Yes, good point. This was handled in https://github.com/informalsystems/ibc-rs/pull/904/commits/3e52c31f787c1886855438bc18a1ffb567773a41. Is that incomplete?

The version in the title of the guide should be updated to v0.3.0

Yes, good point. This was handled in 3e52c31. Is that incomplete?

Ah cool, so it was updated while I was reading the guide.

authors: adizere ancazamfir soareschen

repo: informalsystems/ibc-rs


text:
Do download feature and minor fixes

do_download feature is currently broken on master but fixed in forest_74_zoom
Small task to merge aws.py and other refactorings into master to open Forest up for general development

Branch created forest_82_do_download

repo: informatics-lab/forest


text:
Data Format Specficaition

From james.ma...@gmail.com on July 04, 2014 08:21:07
The current definition is:
A data format specification is the information content borne by the document published defining the specification. Example: The ISO document specifying what encompasses an XML document; The instructions in a XSD file.
I would like to have this changed to something more understandable to none ontologists. I'm an ontologist and I struggle to understand this English. I propose:
The syntax by which data is specified which renders it valid for a given format.
Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=172

From alanruttenberg@gmail.com on July 05, 2014 11:33:59
See thread at https://groups.google.com/d/msg/information-ontology/v3vB3bIvQ3o/_INdeBMdL80J

From alanruttenberg@gmail.com on July 05, 2014 11:41:34
We quite deliberately chose to represent the specification document - ideally the standard - for file formats rather than get into what are quite difficult issues about, e.g, what syntax means, what the actual structure of the documents were or the formalisms used to define the format, the difference between the formalisms and what the formalisms specify, etc.
We did this knowing that
a) in the use cases we were interested in, it could repeatably be assessed whether we had an instance of the entity in question (e.g. a W3C published specification) and
b) That any queries that used file format as a specification could be just as easily done using the current (document) term
As James aludes to, efforts this far to capture the semantics of , e.g. encoding, haven't been quite right.
I do have some new ideas for elements of IAO that might address these issues, but they aren't ready for prime time.
-Alan
p.s It would be great if comments could be added to the ticket directly.

From james.ma...@gmail.com on July 05, 2014 12:44:35
Hi Alan,
I understand the reason now, though it has taken me this long to get there - which is a problem I think as there is quite some thinking behind this textual definition that is not apparent. The more fundamental problem is that IAO is just dodging the issue that people talk about data formats not documents that legally and formally define it. People don't annotate their data to ISO/IEC 10918-1 they say my image is a jpg format. I accept this is a shorthand for the longer statement about documents and authors etc but this is what people refer to. Is IAO saying that these formats can't be represented in an ontology or they are just out of scope for IAO or more simply that the word syntax is too restrictive?
Concerning the latter, I guess you're right about using the word syntax in my definition, perhaps there is a better word but for the sake of all the edge cases in the world you might not ever get a single word or you'll end up with 50 'syntax or this or that or this' clauses. We chose syntax as people generally understand what we meant. Adding examples will clarify we mean more widely the things you think are outside this.
James
PS Sorry about thread thing, I thought by replying it was all going in the ticket thread and not on a mailing list.

From alanruttenberg@gmail.com on July 07, 2014 21:29:26
"Is IAO saying that these formats can't be represented in an ontology or they are just out of scope for IAO or more simply that the word syntax is too restrictive?"
Neither. It's just that we haven't figured out how to do that yet, in a way that doesn't have easily exposed shortcomings.
You could try.
How would you define the tiff format?

From james.ma...@gmail.com on July 08, 2014 01:58:08
So textually no problem and that is actually all I'm asking for. Axiomatising it, I presume your problem is with the fact you can use it as a container for jpg, for example, as well as 'native' tiff? TIFF itself is clearly a format specification - it may well allow you to wrap up other images too by containing them in TIFF but that's fine. I don't need to add the axioms for TIFF to JPG but presumably such a thing can be added, not sure what that relationship is but some sort of contained in (whatever BFO would permit). I have no use case for this though.

From alanruttenberg@gmail.com on July 08, 2014 10:17:29
Axiomatizing and textually describing involve the same problems. Saying what you mean. As you pointed out with syntax, it isn't so easy to do. Its not clear where something like syntax even goes, ontologically speaking. Anyways, that's the background. As I said, I may have a proposal on how to handle this better in not too long. For that matter it isn't clear to what one would annotate the file format. In some cases it seems that the same content can be formatted in different but entirely equivalent forms. There is also an outstanding issue on what exactly the identity criteria are for ICEs. In some cases it seems that the form can vary (e.g. a book/ebook) in some cases not (a file?). There are consequences to choosing one or the other criterion universally.
For example, if the ICE is independent of format, then it would seem that the format applies to some subset of concretizations of it. If it the ICE is dependent on the format then we need a way to relate the differently formatted ICEs to each other.
Bill Duncan writes:
--
O discussed the issue of how data relate to data specifications in my
dissertation. In it, I used the term 'complies with' to denote the
relation between the two. For example, the string "(setf x 1)"
complies with some LIPSP programming language specification. This
means that the string "(setf x 1)" is specified by, adheres to,
conforms with, abides by etc. (choose your favorite synonym here) the
rules used to generate valid LISP strings.
Is the semantics of 'complies with' loose? I'd say yes. But, so is the
semantics of 'is about' (and its subproperties).
--
And then even if we tried using Bill's relation, having figuring out what the subject is, the object of the relation  would seem to, still be the specification document, or something one step away. So we land up adding more structure rather than less in expressing what we want.
It's for these reasons that we've pushed off adding the (what appears to be) simple relation you proposed. I suppose we could add it now and fix it later when we know how to say what we are talking about. I haven't felt the cost was worth the benefit given that we have a principled way to talk about the specification document.

From wddun...@gmail.com on July 08, 2014 10:53:21
How is my suggestion for a relation any "loser" than the relation 'is about'? Just as a particular ICE can be about multiple entities, so too can a give file conform to multiple formats.
Moreover, this notion of conformance/compliance/specification (or however you wish to phrase it) is implicit in our understanding of format specifications to begin with. Something counts as an XML file b/c it has a certain agreed upon grammatical structure. I'm just trying to make the implicit explicit.

From james.ma...@gmail.com on July 16, 2014 05:01:32
it sounds as though IAO is not able/willing to make changes to textual definition on data format at the moment so I will continue to use our own in SWO for now until something better is agreed upon. I'll keep abreast of this ticket should it change in the future.
JM

From alanruttenberg@gmail.com on July 16, 2014 22:29:48
Bill, what are the proposed relata for the conforms-to relation in this case?
James, IAO is you. Recall you have commit privs.
I discuss but don't rule.

From wddun...@gmail.com on July 19, 2014 11:15:09
James already has the relation 'has format specification' in SWO. It relates an information content entity to a data format specification. The relation's definition may need some more detail, and perhaps the name might be changed to 'has data format specification'. But, I think it (as a first step) works fine.
As for the "too broad" objection: 'has format specification' is a subproperty of 'is about', and thus inherits a number of problems from 'is about' regarding the lack of specificity. However, this "too broad" criticism can be applied to other subproperties of 'is about', such as 'denotes'. If the string "George Washington" denotes the first president of the United States, does it also denote his height, weight, and number of teeth? The answer to this is unclear, but the 'denotes' relation is still useful. The same may be said of 'has format specification'. A document may have a number of different of formats (e.g., ASCII, PDF, etc.), but that does not necessarily mean that the 'has format specification' relation is without merit.

Bill

From cmung...@gmail.com on February 19, 2015 14:15:28
Any progress on this? I agree with James' point about unintelligibility. The examples just confuse me more. "The instructions in a XSD file."??
Current individuals include things such as 'OWL' http://purl.obolibrary.org/obo/OBI_0000332 "OWL is a format standard of a digital entity that is conformant with the W3C Web Ontology Language specification.( http://www.w3.org/2004/OWL/ )"
There are numerous issues with this. OWL is a language with many concrete formats. The URL doesn't point to a single specification.
I get that top-down perfect axiomatization within the IAO framework is hard, so maybe it's time for a different approach?
Here is one suggestion. Define some ICEs according to how they are intended to be used. This frees up a need to axiomatize in depth the subtle structural properties of an ICE. A data format is an ICE intended to allow exchange of data between information systems; data is serialized according to the format and parsed by the receiver.
We still be would be free to record specific axioms on each individual format. This would provide material for bottom-up creation of more specific classes (in which membership can be inferred).

There are two issues, as I see it.

How to improve the documentation for this term
Whether and how to define a term with more granularity.

Towards the first, I propose, in language that I hope would be generally understood
definition: A data format specification is an authoritative document written for the purpose of describing how pieces of data should be ordered in relation to each other in a document of which the data are part.
example of usage: The XML specification, a copy(concretization) of which is at https://www.w3.org/TR/REC-xml/
Chris: I would say that the definition of OWL should be fixed to use https://www.w3.org/TR/owl2-syntax/ at least. OWL, as you point out, isn't a data format, but rather a standard which includes a number of format specifications. The syntax document specifies the functional syntax. A separate document specifies the RDF/XML, another the XML format. If a general term for an OWL format is need some disjunction of those documents would seem appropriate.
I would defend the utility of the current term as (at least in intent) defining a coherent set of entities. If used in simple annotation of files, it means we have one less set of terms to define, since the specification documents already exist and should be relatively easy to identify (easier than writing some new description of the format).
I think that data format specification documents differ. Some offer conformance criteria, some offer instructions more like a recipe for production, some more like a recipe for parsing. I would consider doing something with a file that is format related (such as the examples I give) to be different types of realizations of a concretization of the specification. See #174, #184 and so a directive information entity.
Shortcut relations may be in order. conforms with, in terms we already have, is something like: specified output of realization of concretization of data format specification

On the issue of whether we should have other terms, I think that other sorts of entities exist in this area, and that if an application has a need, for example, to define specific kinds of parts of data format specifications, that should be done. If that's the case I would ask that a separate ticket be opened for that, and that it include some examples of use of proposed terms and some competency questions.

I would also add, in an editor note, a pointer to this issue.

repo: information-artifact-ontology/IAO


text:
Enable or disable auto loading of projects on start

Add a checkbox to projects and categories which enables or disables that projects are loaded on start, so large configurations can still startup quickly.

Done for projects, need to add for categories as well.

Done

repo: infosupport/FMStudio


text:
Add support for AWS Cloudtrail.

Add support for AWS Cloudtrail in both the product and also into the usage file.
https://aws.amazon.com/cloudtrail/pricing/
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudtrail
aws_cloudtrail
Cost components:

Management events (additional copies) - unit is events. Monthly quantity is defined in usage parameter monthly_additional_management_events. This cost component is only shown if the resource has an event selector with include_management_events = true or the usage parameter is set.
Data events - unit is events. Monthly quantity is defined in usage parameter monthly_data_events.
Insight events - unit is events. Monthly quantity is defined in usage parameter monthly_insight_events. This cost component is only shown if an insight_selector is specified on the resource.

There are no free resources for CloudTrail.

I've updated the description of this issue with the details discussed.

@robh007 this is live in v0.9.16.

authors: aliscott robh007 vdmgolub

repo: infracost/infracost


text:
🛑 Uvirtual is down

In b6be8fb, Uvirtual (https://uvirtual.unimonserrate.edu.co/) was down:

HTTP code: 503
Response time: 452 ms

Resolved: Uvirtual is back up in 57bd480.

repo: infraestructuraidt/status


text:
🛑 Aulas virtuales is down

In b85c967, Aulas virtuales (https://aulasvirtuales.unimonserrate.edu.co/) was down:

HTTP code: 503
Response time: 1323 ms

Resolved: Aulas virtuales is back up in 282eb43.


text:
🛑 Biblioteca Digital is down

In b296b78, Biblioteca Digital (https://unimonserrate-library.ohelit.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Biblioteca Digital is back up in 0c40855.


text:
Please invite me to the community

Name
George Fred
Additional Context
I'd like to join this community. Maybe, this will help to improve my skills.

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is a remarkable open-source solution tailored for serverless platforms, aimed at empowering creators to craft their infrastructure solutions. 💻 We're thrilled to welcome you into our vibrant community! ✨ We eagerly anticipate your valuable contributions! 🤓 Don't forget to explore our community on Github and connect with us on LinkedIn 💜 Feel free to spread the word about our community to like-minded individuals interested in development, DevOps, technology, and collaborative contributions. 👉💜👈

repo: infraform/contribute


text:
Protocol compat

Added on to the compatibility checks based on #EXT-X-VERSION.
In addition, I added the functionality that the {Key|Map} struct is copied and appended to every segment that it applies to. Therefore, I added the detection on encoding to only print when the previous segment was different.

Note, internally we found a device (I know, we can't hack around shitty devices and I think it was an obscure STB), that couldn't handle reusing keys between segments without being explicitly told to.
We ended up dealing with it by creating a concept for output filters that we could chain on demand.
I'm not sure how this manifest package handles things right now, but introducing this concept if it's not already there may help separating RFC compliant behaviour from other formatting possibilities.
For the record, we also had filters to add http headers, limiting live stream segments (forcing clients to start a live stream at an exact position as well as forcing delays if needed), standardising KeyFormatVersions, stripping SCTE tags, ConsistentKeys (what I just mentioned) and forcing NONE encryption (when switching between playlists with and without encryption).

@bradleyfalzon the filter concept seems useful and easy to compose manipulation. I'll add an issue to design the interface for this package.
I'm concerned but not surprised that you found a device that required the key be provided for every segment.

authors: bradleyfalzon itsjamie

repo: ingest/manifest


text:
[FEAT]: goldilocks poseidon hash for BN254

Description
plonky2's Goldilocks filed is the most efficient field in ZKP system ( by far as i know). to make plonky2 verifiable on chain, the poseidon hash has to be implemented for BN254. a cpu implementation is here https://github.com/iden3/go-iden3-crypto/blob/master/poseidon/poseidon.go. possible to port that into icicle also?

Thank you for the suggestion!
We actually have goldilocks support in our upcoming roadmap, so stay tuned

thanks for your reply. however, i am not requesting for goldilocks support, rather it is poseidon implementation over foreign BN128 field on native Goldilocks field. Currently, ethereum only has precompile for BN128 and no Goldilocks field. To make my proof verifiable on chain, i need to implement BN128 on Goldilocks of plonky2

@cliff0412 not exactly sure what you meant, but here are three facts that might help:

BN128 ==BN254 (afaik). We have poseidon implemented for bn254
We are planning to add support for goldilocks poseidon in the future.
ICICLE is a general-purpose library, so unfortunately we are not planning to implement very specific cases

Closing the issue for now. Feel free to re-open or reach out in our Discord if you have any questions

authors: ChickenLover LeonHibnik cliff0412

repo: ingonyama-zk/icicle


text:
about SIBR_viewers

Thank you for your great achievements, when can we combine SIBR_viewers?

Hi, thanks for your interest.
We will have a try to integrate the SIBR_viewers once upon our paper is accepted.


text:
Add cmp-array function

My usecase is: comparing the output of several commands to a list of expected lines.
I would like to get a detailed output if I got more or less lines, and which line is different.
For perl, there's is_deeply, but in bash I called it cmp-array:
expected=( line1 line2 )

command_output=( $(ls) )
cmp-array "command output" ${command_output[@]}

Since I cannot pass two arrays to a bash function, the expected variable needs to be declared before.

Also, when adding this, I noticed a problem with note/diag when passing an array. It would be nice if they could output array elements line by line instead of a long line. Maybe I'll find out if I can fix that.

repo: ingydotnet/test-more-bash


text:
Fix y2k (Y2K-120)

Updated with today's date

Well... yeah.


text:
Fix y2k (Y2K-425)

Updated with today's date

Well... yeah.


text:
Change visibility of config file constant

https://github.com/ink8bit/deby/blob/9fd51eae37fd4987b78bd0c660855a7ef19b62cf/src/config/mod.rs#L28
pub(crate) const CONFIG_FILE_NAME: &str = ".debyrc";

should be private


text:
Wrong sequence Destructor / Constructor and task is not processed

Hi there,
I'm trying to use this thread-pool "LIB" and before using it, I wanted to make some stress tests on it to identify its limit, its hardening and reliability.
I wrote a really short main function and set a small amount of thread (1) with also a small file queue size (2). The behavior I can see is really strange : Some destructor  may be called before constructor :huh: and the same input may be treated by several tasks
Here is the small main.cpp :
#include <iostream>
#include <regex>

#include <vector>
#include <signal.h>
#include <unistd.h>
// #include "logger.h"

#include <future>
#include <utility>

#include "thread_pool.hpp"

static volatile bool         g_theEnd = false ;

#define DEBUG(...)   { printf(__VA_ARGS__) ; printf("\n") ; }
#define INFO(...)    { printf(__VA_ARGS__) ; printf("\n") ; }
#define WARNING(...) { printf(__VA_ARGS__) ; printf("\n") ; }
#define ERROR(...)   { printf(__VA_ARGS__) ; printf("\n") ; }

#define LOG_INIT(a)
#define SET_LOG_LEVEL(a)
#define LOG_END()

//
//
//
void cleanup(void)
{
    // Ask the threads to give up
    g_theEnd = true ;

    INFO("Stop test-thread-pool") ;
    LOG_END() ;
}

//
//
//
class NgapMessageDecode
{
public:
    NgapMessageDecode(int fd) : m_fd(fd)
    {
        DEBUG("Constructor %.8ld, fd=%.2d", this, fd) ;
    }

    virtual ~NgapMessageDecode()
    {
        DEBUG("Destructor  %.8ld, fd=%.2d", this, m_fd) ;
    }

    void operator()()
    {
        DEBUG("Decode %.2d, this=%ld, thread=%.8ld", m_fd, this, pthread_self()) ;
        // sleep(1) ;
    }

private:
    // std::promise<void> *    m_waiter ;
    int                     m_fd ;
};

int main(int argc, char * argv[])
{
    LOG_INIT("test-thread-pool") ;
    SET_LOG_LEVEL(_LOG_DEBUG) ;

    INFO("%s", "") ;
    INFO("Start test-thread-pool") ;

    tp::ThreadPoolOptions   threadPoolOption ;

    threadPoolOption.setThreadCount(1) ;
    threadPoolOption.setQueueSize(2) ;

    tp::ThreadPool  threadPool(threadPoolOption);

    for(int i=0; i<100; i++)
    {
        try
        {
            threadPool.post(NgapMessageDecode(i)) ;
        }
        catch(std::runtime_error & e)
        {
            std::cout << e.what() << std::endl ;
        }
    }
    sleep(1) ;
    cleanup() ;
    return 0 ;
}

The output is :
Start test-thread-pool
Constructor 140734462742560, fd=00
Destructor  140734462742176, fd=00
Destructor  140734462742560, fd=00
Constructor 140734462742560, fd=01
Destructor  140734462742176, fd=01
Destructor  140734462742560, fd=01
Constructor 140734462742560, fd=02
Destructor  140734462742560, fd=02
thread pool queue is full
Constructor 140734462742560, fd=03
Destructor  140734462742560, fd=03
thread pool queue is full
Constructor 140734462742560, fd=04
Destructor  140734462742560, fd=04
thread pool queue is full

How can the Destructor  140734462742176, fd=00 (line2) can be called before the constructor ?
More over, this same Destructor refers to the object where fd==00 whereas the corresponding constructor below refers to fd==01
Thus, how can I got the sequence described in the 3 first lines : Constructor / Destructor / Destructor with the same FD==00
So, I probably missed something or at least misunderstood how I'm supposed to use this "LIB" but I can't find out what's the good practice :/
Branch used : master
I can't use the branch round-robin-stealing 'cause it refers to std::exchange that is defined in C++14 and I must stay in C++11
Command to build the main application listed above, to facilitate :
g++ -c   -DLOG -I<path_to_thread-pool-cpp>/include/thread_pool -Wall -Wextra -g -std=c++11 -o main.o main.cpp

g++ -g   -o test-thread-pool main.o -lpthread

All kind of help would be appreciated :+1:

Based on my experience, the idea to conduct stress tests with a short queue is very bad (which is demonstrated your test - "thread pool queue is full"). At least, use default size (1024).
Start with this point. Your pool configuration too small to run any load. Ever empty function calls.

Thanks for your answer.
If I let the default queue size, OK it seems working but I also got an unexpected behavior :
Start test-thread-pool
Constructor 140731659953008, fd=00
Destructor  140731659952624, fd=00
Destructor  140731659953008, fd=00
Constructor 140731659953008, fd=01
Destructor  140731659952624, fd=01
Destructor  140731659953008, fd=01
Constructor 140731659953008, fd=02
Destructor  140731659952624, fd=02
Destructor  140731659953008, fd=02
...
etc

More over the below count is also strange :
(stdout.txt contains the ouput of the application)
$cat stdout.txt | grep Decode | wc -l
100
$ cat stdout.txt | grep Constructor | wc -l
100
$ cat stdout.txt | grep Destructor | wc -l
400

Why did I got 400 call to Destructor ? O_O
This make me confused

Not sure this is UB :) UB is slightly different thing.
Guess, till logic correct and no crash occurs - this can't be named UB.

I think there are additional move-ctor calls that you don't log.

I think there are additional move-ctor calls that you don't log.

I think you are probably right because I wrote the almost exact code using boost::asio::post and boost thread_pool (boost 1.70) and I got the same "unexpected" sequence of Destructor / Constructor o_O
I need to understand why (?)
Additional : how can I wait for end of current thread jobs ? If I leave the application and LOG "End of application", there are lots of threads that still execute code. I would like to wait for them before leave.

Ok I found it and when I think about it, this was obvious :blush:
@inkooboo You put me on the right way when you said

I think there are additional move-ctor calls that you don't log.

Indeed, the constructor that I omitted is the copy constructor. So, now I got as much constructors than destructors and this will make me sleep like a baby the next night :sleeping_bed:

authors: CyrilleBenard inkooboo yvoinov

repo: inkooboo/thread-pool-cpp


text:
fix broken link (#3063)

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

Merged into branches iso4 in 5be35d7990d23ffe6ac3baaf04c6bbc32bcd5175

repo: inmanta/inmanta-core


text:
Run the tests using python3.9 (#225)

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

Merged into branches iso5 in bf51f0c877064ae4ce918b68a5d25c0e2f3d8b86

repo: inmanta/inmanta-ui


text:
Link presentation

Link ContainerDays 2019 Presentation and make some small clean ups in the markdown.

@maal @maxbischoff someone ?

repo: inovex/illuminatio


text:
Firefox Tabbing

The problem
When using the keyboard, tabulator doesn't work as expected when using the columns menu or the note reactions menu.
Browser
Firefox
Steps to reproduce the behavior
Open the columns menu or note reactions menu using tabulator. Both menus cannot be accessed properly, unlike Chrome, for example.
Screenshots
No response
Additional context
No response

Hello,
#4562


text:
[BUG] - Possible to create an operational certificate with a negative value for kes-period

Internal/External
Internal
Area
Operational certificate
Summary
At the moment it's possible to create an operational certificate with a negative value for the kes-period parameter.
Steps to reproduce
./cardano-cli node issue-op-cert \
    --kes-verification-key-file .../pool_kes.vkey \
    --cold-signing-key-file .../pool_cold.skey \
    --operational-certificate-issue-counter ../pool_cold.counter \
    --kes-period -100 \
    --out-file pool/pool_operational.cert

Expected behavior
When trying to create the operational certificate with a negative kes-period should return an error

Closing this. If this is still relevant please reopen.

This issue is still present on master.

repo: input-output-hk/cardano-node


text:
Execute the cardano-cli at the process level

New execCardanoCLI function which uses one of:

$CARDANO_CLI if it is defined
cabal exec -- cardano-cli otherwise

New workspace function which creates a temporary directory and cleans it up.  The clean up is signalled by writing a done file.
The Genesis.Create test is modified to use execCardanoCLI and workspace.
New dependency on process library.

Thanks!

bors merge


text:
Scripts to setup a cluster that can go through Byron->Shelley->Allegra

Run the script scripts/shelley-allegra/mkfiles.sh and follow the
instructions it prints out.

bors merge

bors merge


text:
CAD-391 eliding messages

prints first and last message of range of equivalent 'TraceLedgerReplayEvent'.
[nixos19:cardano.node.ChainDB:Info:64] [2019-12-24 23:26:57.00 UTC] {"event":{"kind":"TraceOpenEvent.OpenedVolDB"},"kind":"TraceEvent","tip":"genesis(origin)"}
[nixos19:cardano.node.ChainDB:Info:64] [2019-12-24 23:26:57.31 UTC] {"event":{"snapshot":{"snapshot":"DiskSnapshot 9","kind":"snapshot"},"kind":"TraceLedgerReplayEvent.ReplayFromSnapshot","tip":"Tip (At (Block {blockPointSlot = SlotNo {unSlotNo = 3549092}, blockPointHash = ByronHash {unByronHash = AbstractHash 2cfa35fe9617a9c41ef5ec19bed50742e587ab10d18ce6ac80c09bf71308fc3e}}))"},"kind":"TraceEvent","tip":"genesis(origin)"}
[nixos19:cardano.node.ChainDB:Info:64] [2019-12-24 23:26:57.39 UTC] {"event":{"snapshot":{"snapshot":"DiskSnapshot 9","kind":"snapshot"},"kind":"TraceLedgerReplayEvent.ReplayFromSnapshot","tip":"Tip (At (Block {blockPointSlot = SlotNo {unSlotNo = 3549092}, blockPointHash = ByronHash {unByronHash = AbstractHash 2cfa35fe9617a9c41ef5ec19bed50742e587ab10d18ce6ac80c09bf71308fc3e}}))"},"kind":"TraceEvent","tip":"genesis(origin)"}
[nixos19:cardano.node.ChainDB:Info:64] [2019-12-24 23:26:57.39 UTC] messages elided in total = 70
[nixos19:cardano.node.ChainDB:Info:64] [2019-12-24 23:26:57.39 UTC] {"event":{"kind":"TraceOpenEvent.OpenedLgrDB"},"kind":"TraceEvent","tip":"genesis(origin)"}

depends on PR https://github.com/input-output-hk/iohk-monitoring-framework/pull/495

eliding TraceLedgerReplayEvent:
[nixos19:cardano.node.ChainDB:Info:63] [2019-12-30 13:06:34.52 UTC] {"event":{"snapshot":{"snapshot":"DiskSnapshot 19","kind":"snapshot"},"kind":
"TraceLedgerReplayEvent.ReplayFromSnapshot","tip":"Tip (At (Block {blockPointSlot = SlotNo {unSlotNo = 3560492}, blockPointHash = ByronHash {unBy
ronHash = AbstractHash 3ac09146dbc3c75e298543a22223ac3aeeab387d9ddecedac5cbe6465db34dc0}}))"},"kind":"TraceEvent","tip":"genesis(origin)"}
[nixos19:cardano.node.ChainDB:Info:63] [2019-12-30 13:06:34.78 UTC] before next, messages elided = 1432
[nixos19:cardano.node.ChainDB:Info:63] [2019-12-30 13:06:34.78 UTC] {"event":{"kind":"TraceLedgerReplayEvent.ReplayedBlock","slot":"3542400","epoch":"164"},"kind":"TraceEvent","tip":"genesis(origin)"}

eliding TraceGCEvent:
[nixos19:cardano.node.ChainDB:Debug:79] [2019-12-30 13:07:09.88 UTC] {"event":{"kind":"TraceGCEvent.PerformedGC","slot":{"kind":"SlotNo","slot":3562021}},"kind":"TraceEvent","tip":"4cac1a8@3567746"}
[nixos19:cardano.node.ChainDB:Debug:81] [2019-12-30 13:07:09.88 UTC] before next, messages elided = 2
[nixos19:cardano.node.ChainDB:Debug:81] [2019-12-30 13:07:09.88 UTC] {"event":{"kind":"TraceGCEvent.PerformedGC","slot":{"kind":"SlotNo","slot":3562025}},"kind":"TraceEvent","tip":"4cac1a8@3567746"}

depends on PR input-output-hk/iohk-monitoring-framework#495

upstream PR has been merged. now ready.

bors r+

bors r+


text:
Build Error: cardano-sl.sh shell script fails

When I try to build the project with the following command ./scripts/build/cardano-sl.sh, I get the following error message:
cardano-sl-db-1.0.1: build
Preprocessing library cardano-sl-db-1.0.1...
[ 5 of 13] Pos.DB.Pure
ERROR: flag 'help' was defined more than once (in files '/tmp/nix-build-google-gflags-2.2.0.drv-0/gflags-v2.2.0-src/src/gflags_reporting.cc' and '/tmp/gflags-20170711-34557-1a3xxyr/gflags-2.2.1/src/gflags_reporting.cc').

--  While building package cardano-sl-db-1.0.1 using:
      /Users/omefire/.stack/setup-exe-cache/x86_64-osx-nix/setup-Simple-Cabal-1.24.2.0-ghc-8.0.2 --builddir=.stack-work/dist/x86_64-osx-nix/Cabal-1.24.2.0 build lib:cardano-sl-db --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure 1

What branch are you using?

@omefire please reopen with exact steps you followed and based on which docs. We have revised building docs in past week and verified they work.

authors: domenkozar omefire

repo: input-output-hk/cardano-sl


text:
[DDW-1006] Integrate Delete Pending Transaction V2 API Endpoint

This PR integrates the delete pending transaction V2 API endpoint which allows a users to "forget" about a pending transaction that will not transition into an "inserted/confirmed" state so that the UTXO associated with the pending transaction can be spent again in a new transaction.
Testing Checklist

Slack QA thread
[ ] Test

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

@MarcusHurney please merge latest v2-integration branch. There are many conflicts due to the changes @tomothespian introduced in this PR: https://github.com/input-output-hk/daedalus/pull/1641

Closing this PR unmerged as it's changes are included in this PR https://github.com/input-output-hk/daedalus/pull/1651
cc @MarcusHurney @DeeJayElly @DmitriiGaico

authors: MarcusHurney nikolaglumac

repo: input-output-hk/daedalus


text:
Add windows ini support

fix the stack size setting on Linux, it was not being picked up
allow the client to run from the command line on windows, it could not get at the settings file (application.ini) it's apparently called 'etc_client_config.txt' on windows.
allow the client to use SecureRandom() by default on all platforms. The use may still override this value.

Tried it on a Windows 10 machine and it worked perfectly

authors: AlanVerbner mcsherrylabs

repo: input-output-hk/etc-client


text:
Added the "Write your first indexer" tutorial page in the RTD.

Added the complete CI-compiled example

Refer to the example in the RTD page.

Created a separate page for querying the indexer with an JSON-RPC HTTP server

Pre-submit checklist:

Branch

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

PR

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

@ana-pantilie You still have the query tutorial to review.

repo: input-output-hk/marconi


text:
byron-proxy: DB can trace writes

Requested so that the chain length can go into EKG

@disassembler I switched on EKG in the logger config and then let it write some blocks, but the gauge does not appear. @CodiePP am I doing it wrong?

@disassembler I switched on EKG in the logger config and then let it write some blocks, but the gauge does not appear. @CodiePP am I doing it wrong?

No that is correct.
For some reason we are not able to see this gauge in EKG. Alex and I were about to investigate it.
BUT we are convince that the variable is inserted EKG store since we can see it via Prometheus (http://localhost:12799/metrics) in the first line.

You can see slot numder under int:byron-proxy.db.block count in EKG

rebased on master

bors r+

repo: input-output-hk/ouroboros-network


text:
Simplification pass assumes laziness, resulting in miscompilation

Summary
While UPLC/PLC/PIR are strict, a simplification pass assumes the code is to be interpreted lazily, thus resulting in the following behaviour:
let c x _ = x in c True (error ()) will not err. If you however set it to const, it will err, because it's not simplified (for some arcane reason).
Concrete example in fork of Plutus: https://github.com/mlabs-haskell/plutus/commits/las/miscompilation
Do you have a proposed solution for this issue?
It's not clear to me whether it's GHC doing this or a Plutus library. In the former case, disable the optimisation pass, however this would lead to decreased efficiency, in the latter case, keep track of whether it's possible for the term to err.
System info
No response

Sorry, can you be more specific? Is this a PIR program? A Haskell program?
Unfortunately we can't stop GHC from touching the program entirely, so if this is Haskell it may indeed be something that GHC is doing.

I've posted a link to a fork in the summary where I've added goldens for the test.
Another link: https://github.com/mlabs-haskell/plutus/commit/eee1404aae86594fae0b604a058bbac7e79c295a#diff-1eec071a1e24882fcf29911ff286bec003f983927819ae99ad431fdf75867799
It's a Haskell program.

That's helpful, thanks.

This was brought into the sprint, but hasn't been worked on yet. Chances are, it'll take a bit more time for us to get to this issue, I will keep you updated.

PR #5280 shows that with the noinline pragma the evaluation results for the two examples are now the same. I.e., it IS GHC's inliner that causes the inconsistency.
For now, users will have to turn off the GHC inliner by hand with the noinline pragma for each of their functions. The team will be discussing and exploring better solutions. We welcome your input as well.

More discussion in this ADR.
@zliu41 do you have an idea on what we should do with this issue?

Strict is the only option. The other option (nonstrict) requires a way to prevent GHC from inlining things but that isn't currently possible.

@zliu41 should we keep this issue open or advertise using Strict and close the issue or something else? I'm just not sure how proceed with this specific GitHub issue.

Let's keep it open until we merge #5292 and start telling people to use Strict.

Let's keep it open until we merge https://github.com/input-output-hk/plutus/pull/5292 and start telling people to use Strict.

@zliu41 we aren't telling people to use Strict quite yet, right?

@zliu41 we aren't telling people to use Strict quite yet, right?

Right. The internal ticket tracking this is PLT-5830.

The internal ticket tracking this is PLT-5830.

It's merged now (has been for a while) and hence we can close this issue with the following general advice: use Strict, otherwise GHC will misbehave.

authors: L-as effectfully michaelpj thealmarty zliu41

repo: input-output-hk/plutus


text:
ledger: redeemer and data values are Data, remove Sealed

This is phases 3 and 4 of https://github.com/input-output-hk/plutus/issues/1465.
There's quite a lot in here. On the plus side, I got rid of the "unlifting" stuff in the book and a lot of Sealed juggling.
I'd appreciate feedback on a one thing in particular.
Wrapping validators
The real type of validators is now Data -> Data -> PendingTx -> Bool. However, we don't want people to write that, and ideally we don't even want to really expose the idea that the arguments are Data. To that end I've written wrapValidator :: (IsData a, IsData b) => (a -> b -> PendingTx -> Bool) -> (Data -> Data -> PendingTx -> Bool).
Now, you can call this on your validator when you write it, but then you end up with a top-level signature with the ugly Data things in it. Plus, if you're doing the typed script instance stuff, we want to have a validator with the "real" types in it.
So it's nice to just call it when you actually compile the validator, something like $$(compile [|| wrapValidator validator ||]). This works fine, except:

It's a bit clunky if you're also parameterizing the validator, you need to eta-expand (or use a fancy composition operator).
Because we're in a splice, TH won't let us use typeclass instances defined in the same file!

The latter is quite annoying, since we're not "really" using them, and the error is bad. There is a workaround: let wrap = wrapValidator @DataType @RedeemerType in $$(compile [|| wrap validator ||]). This is pretty ugly, but I don't have a better solution, so it's what I'm doing at the moment.
(The typed script instance stuff therefore also has to carry around a wrapper with it!)
You might think: can't we just do this generically in the library? No: we need to see the concrete typeclass instances, which means this needs to be done in the user's source code. We could maybe write some TH to do it.
On the plus side, we could also move the bit that turns validators returning Bool into validators returning () or throwing into the wrapping process, which would be good.
Known stuff I will follow up on
Will make issues for these:

Generating IsData instances.
Move check into wrapValidator.
Now validators all have the same type, we can require that type when converting to ValidatorScript, which will catch people who fail to wrap their validators.
Rename DataScript and RedeemerScript since they aren't scripts any more.

What should we call "data scripts" now?

Teach the state machine library to not rely on you knowing the state.

Hm, is it not possible do something similar to Ledger.Typed.Tx for wrapping validators?
Something like data Location = OnChain | OffChain and a type family Validator (l :: Location) a b where instance Validator OnChain a b = Data -> Data -> PendingTx -> Bool. Although that doesn't give you any more than wrapValidator does already... so I don't know!

What should we call "data scripts" now?

Maybe just call them state and input values, or state and input data

Although that doesn't give you any more than wrapValidator does already... so I don't know!

Yeah. To have another go at stating the constraints:

I want people to write their validators with the "deserialized" types, so that we can e.g. assert type coherence between their validators and redeemers etc.
We can't generically compile toData - we need a concrete type. So this has to happen in user code.

I could shove this into ScriptType, I guess, i.e.
class ScriptType a where
    ...
    redeemerToData :: CompiledCode (RedeemerType a -> Data)
    dataToData :: CompiledCode (DataType a -> Data)

which is a bit like having IsData superclass constraints except "precompiled". I guess that's slightly nicer than the current version for things using ScriptType at least.

Maybe just call them state and input values, or state and input data

I think "redeemer" is pretty established, we should probably stick with it. It also works without "script", so that's fine.
"Data value" sounds okay. I don't like "state value" because they're not always state.

I could shove this into ScriptType, I guess

This doesn't actually work: this stuff has to be passed at the last possible moment, e.g. we can't do this abstractly for StateMachine. Aggravating.

Okay, here's my best suggestion: instead of defining a specialised wrap function outside the quote, we just get people to put the whole expression for the validator in there, e.g.
$$(compile [|| validator ||]) where validator = wrapValidator mkValidator
This avoids the need for the type applications at least, which is nice. Plus we can give a generic piece of help: "If GHC complains about the stage restriction, just lift the whole thing out."

However, we don't want people to write that, and ideally we don't even want to really expose the idea that the arguments are Data.

I'm not sure I agree with this. It's a very explicit way of aligning things and being explicit is good. I'd probably just tell the users about Data rather than rely on TH or explain that instance resolution doesn't work in certain cases in a splice. Running some code inside compile and some code outside of it feels cryptic to me.

I'd probably just tell the users about Data rather than rely on TH or explain that instance resolution doesn't work in certain cases in a splice.

I tend to agree with this.  In many cases (he said optimistically) the data will be quite simple and it might be more straightforward if users could just write it explicitly rather than having some opaque translation applied in the background.  If they do that, then they might lose Haskell's type-safety guarantees and get the members of a pair the wrong way round or something, but then that would be their own fault.  Giving them the choice of whether to use Data explicitly or implicitly doesn't seem too bad.
There might also be a question of interoperability.  If someone uses another language for writing off-chain code and it has to produce outputs with datascripts which are compatible with ones produced by Haskell code then they'll have to know how the Haskell version is encoded, and that might not be too obvious if the encoding's been done automatically by some typeclass behind the scenes.

Running some code inside compile and some code outside of it feels cryptic to me.

To be clear, it's not running outside, it's just that the definition needs to be there. You can also make it work by putting the instance in another file!

I tend to agree with this. In many cases (he said optimistically) the data will be quite simple and it might be more straightforward if users could just write it explicitly rather than having some opaque translation applied in the background.

Well, you can look at what was here before this PR for an example of that. It's just lots of noise IMO.
You can still do it that way after this PR if you like, I just don't think it should be encouraged.
And it's not really opaque: you can look at the definition of wrapValidator, it's a very trivial function.

There might also be a question of interoperability. If someone uses another language for writing off-chain code and it has to produce outputs with datascripts which are compatible with ones produced by Haskell code then they'll have to know how the Haskell version is encoded, and that might not be too obvious if the encoding's been done automatically by some typeclass behind the scenes.

Yes, as with all such serialization things, if you do this you probably want to hand-write your instances, but that's fine I think.

I think the more important thing is that in the long run we want people to be using the more type interfaces, and those can't work without having a function that takes the "deserialized" types so it can check that they're right.

To expand a little: people are going to know about Data (otherwise these IsData instances won't make much sense), I just don't expect them to deal with it in their validators.

I tend to agree with this. In many cases (he said optimistically) the data will be quite simple and it might be more straightforward if users could just write it explicitly rather than having some opaque translation applied in the background.

Sorry, I didn't mean that people should manipulate Data directly, that would quite cumbersome I think. Just that asking to apply wrapValidator directly and provide the type signature that mentions Data seems better than the other options to me.

To be clear, it's not running outside, it's just that the definition needs to be there.

Sure, I should have said "writing" rather than "running".

You can also make it work by putting the instance in another file!

Yes, but this is the kind of thing that I'd prefer to avoid explaining.

Just that asking to apply wrapValidator directly and provide the type signature that mentions Data seems better than the other options to me.

To be clear, the alternative I'm envisaging is something like:
validator :: Data -> Data -> PendingTx -> Bool
validator = wrapValidator $ \d r p -> ...

vs
validator :: DataType -> RedeemerType -> PendingTx -> Bool
validator d r p =

The downsides of 1 as compared to 2 are:

Where do the types of the inner validator come from? Either rely more on type inference, or ugly annotating of lambda arguments, or a new top-level binding (in which case we're back with 2).
No typed validator binding to use in typed interfaces.

I guess I just really want people to live/think in the typed world as much as possible, and leave the "wrapping/parsing" business to the point where they package up their nice function for the library to use.

Anyway, I think I'm going to merge this as is in a bit. We can change that particular bit of the library fairly easily, and there's a bunch of uncontroversial stuff I want to do on top of this. Let's discuss this more at a meeting.

or a new top-level binding (in which case we're back with 2).

That's what I propose. Require the user to write two top-level bindings. Yes, this is slightly repetitive, but it's a small constant overhead per contract and zero magic while other solutions (generate the "untyped" validator via TH or apply it outside of a splice) are either magical or weird.

That's what I propose. Require the user to write two top-level bindings. Yes, this is slightly repetitive, but it's a small constant overhead per contract and zero magic while other solutions (generate the "untyped" validator via TH or apply it outside of a splice) are either magical or weird.

Well, that's what this PR does. Except they're local bindings, not top-level bindings. No magic, really. I don't think making it a top-level binding significantly changes anything...

authors: effectfully j-mueller kwxm michaelpj


text:
Restore type definitions to @inrupt/vocab-common-rdf

Describe the bug
The package has lost its type definitions in its v1.0.0 release. Thus TypeScript started complaining.
To Reproduce
mkdir reprod && cd reprod
npm init -y
npm i @inrupt/vocab-common-rdf@0
cat ./node_modules/@inrupt/vocab-common-rdf/package.json

Notice how the output includes "types": "./dist/index.d.ts",. Now run:
npm i @inrupt/vocab-common-rdf@1
cat ./node_modules/@inrupt/vocab-common-rdf/package.json

Notice that "types" are missing now.
Expected behavior
Type definitions to keep being included.

Yeah, thanks for reporting @riovir. We'll look into this ASAP.

Hi @riovir,
Thanks so much again for reporting - it actually kicked off a big internal update (that I'll describe below), but in fact the issue you noticed was due to something else entirely.
Basically we switched the 'default form' of our generated artifacts (by default I just mean the artifacts named without a suffix that explicitly describes whether they build on top of RDF/JS, or on top of rdflib, or which implementation of RDF/JS, or whether they use String Literals, etc.).
Previously the default form (in your case the artifact named @inrupt/vocab-common-rdf) relied on IRI-typed constants for vocab terms, and so it depended on @types/rdf-js. But with v1 we've switched that to just using String-typed constants instead, and with that switch we also generated just pure JavaScript artifacts, so with no type information or any TypeScript configuration at all. That was why you noticed the now missing "types".
So one of the changes I've now made is to update this so that we now default to generating string literal-based artifacts that support TypeScript out-of-the-box.
We always also published the other forms of our artifacts, we just name them more explicitly now. So the new name for the Common RDF artifact that uses RDF/JS types for the vocab term constants (and that uses Ruben Taelman's rdf-data-factory implementation of the RDF/JS Data Factory interface) is now named:
@inrupt/vocab-common-rdf-rdfjs-rdfdatafactory

If you try that dependency you should see the correct "types" field when you:
cat ./node_modules/@inrupt/vocab-common-rdf-rdfjs-rdfdatafactory/package.json

But now to describe the internal change sparked by your issue. It turns out that the RDF/JS community recently released the official TypeScript types, specifically @rdfjs/types. So we've now updated our Artifact Generator templates to use those types (as opposed to the DefinitelyTyped types that we were depending on before). But then it turned out that Ruben Taelman's implementation was still depending on the old types too. We raised an issue there, and Ruben quickly updated his library, allowing us to update our dependency on it, thereby tidying up all usage of RDF/JS types now.
So we'll be releasing new v1.0.1 versions for the Artifact Generator, and our published artifacts very soon (and I've updated the README documentation around all this too). It would be great if you could let us know if all that makes sense before we release the updated v1.0.1 versions of everything.

It would be great if you could let us know if all that makes sense before we release the updated v1.0.1 versions of everything.

It does, it's much appreciated, and also thank you for responding so quickly!

and I've updated the README documentation around all this too

Is that why currently I'm getting 404s (as in not yet released?) for the following links in the README?

Generated directory structure
Multiple forms of generated artifact
Generated source-code documentation
The relationship between generated source-code artifacts and RDF vocabularies

Hi @riovir,
Whoops! No, those broken links you found were actually broken - but fixed now (and the text improved a wee bit while I was at it).
I hope to get the next release of the Artifact Generator and the generated artifacts published tomorrow, so I'll leave this issue open until we get those released and verify that all is well again.
Again, thanks for the great feedback - it's been really invaluable, and thanks for your patience in dealing with these teething issues before we officially announce the open-sourcing of the Artifact Generator.

Hi @riovir,
Just the latest update - version v1.0.1 of the Artifact Generator and all the generated artifacts have been released to npmjs.org now (with a nice number of tidy ups and enhancements thrown in too for good measure (like really detailed JSDoc/JavaDoc comments for vocab terms that provide multi-lingual rdfs:label and rdfs:comment meta-data)).
If you get a chance it would be great if you could re-try and see if your expectations are met this time around.
Cheers,
Pat.

Ahoy @pmcb55! Yup, works as advertised. Thanks again! :)

repo: inrupt/artifact-generator


text:
Enable gcalcli to handle non-Google CalDav providers

I'm wondering if it would take a big effort for gcalcli to integrate with other providers, most notably standard CaldDav sources/providers. I realize the import of ics and vcal is already possible but I'm specifically asking about being able to interact directly with a CalDav online calendar.

We aren't using CalDav.  We are using the Google APIs directly.  At this time this simply isn't possible.

I'm wanting this as well, so I'm reopening this issue and adding it to the 4.1 milestone.
One of the outcomes of the modularization project I've been working on is that we should be able to support multiple backends.  I can't promise this will get done soon, but I'm officially putting on my wish list and i"ll start poking around in the near future.

Somehow, I did not know gcalcli existed and I wrote reticuldated some time ago. It is not as robust, and is really a scratch-my-own-itch project, but together with calendar-cli it works for me. This pair allows display of caldav and input/manipulation of existing caldav events.
If gcalcli ever begins to play nicely with caldav, I will likely completely abandon reticuldated.

authors: Adocentyn fauxmight jcrowgey tresni

repo: insanum/gcalcli


text:
Memory limits for local executor

I have noticed that redun seems to reserve memory even in local executors. Is there a way to tune that? or I am wrong on this assumption?

Hi @jshleap! Thanks for the question. I don't believe we set memory limits on local executors. Are you getting some behavior that suggests otherwise?

reserve memory even in local executors

Unless by "reserve" you mean preallocating memory. redun isn't doing anything unusual in that regard more than what multiprocessing thread and process pools typically do (FWIW, that is how redun implements the local executors). Let me know if that helps, or if I misunderstood the question.

max_workers will work to limit parallelism across all tasks. If its just one task that should have parallelism limits, check out the limits config option: https://insitro.github.io/redun/config.html?highlight=limit#limits

authors: jshleap mattrasmus

repo: insitro/redun


text:
snapshot_process: Sleep before starting the gadget

This makes sure that our test container has already spawned and is running the command we want to see in the snapshot
We have many flaky CI failures on snapshot_process. This should fix it

Unfortunately I don't think it fixes the issue:

https://github.com/inspektor-gadget/inspektor-gadget/actions/runs/10386743239/attempts/1#summary-28759182888
https://github.com/inspektor-gadget/inspektor-gadget/actions/runs/10380957419/attempts/1#summary-28742131702
https://github.com/inspektor-gadget/inspektor-gadget/actions/runs/10393961200/attempts/1#summary-28783086720

authors: burak-ok mauriciovasquezbernal

repo: inspektor-gadget/inspektor-gadget


text:
cli: disable invenio index command

INSPIR-3432

Actually I just checked the changes, this solution will not work. It is an entry point  ordering issue, if we don't resolve the  entrypoint in the right order the invenio_indexer.cli will never be overriden by inspirehep.indexer.cli. By solving the loading order then we just override invenio_indexer as @michamos suggesting. We'll probably need to override the loader and make sure our entrypoints are loaded after the invenio https://github.com/inveniosoftware/invenio-base/blob/master/invenio_base/app.py#L169

As it was mentioned in refinement already, when we are overwriting index group in inspirehep.cli it's already AFTER app is initialized so loading order doesn't matter here anymore.

authors: drjova pazembrz

repo: inspirehep/inspirehep


text:
Modifies json_utils.pull_neptune_data to now download files concurrently

What?

Neptune logs are now downloaded concurrently, yielding increased download speed.
We now only fetch the sys/id column when initialising the project instead of downloading the full table.
The downloaded JSON files are extracted directly into the store_directory, creating a flat file structure. i.e. No more nested folders.
Downloaded files are also named according to their run_id.

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

authors: CLAassistant liamclarkza

repo: instadeepai/marl-eval


text:
Get the list of blocked

I want to get the list of those who are blocked
How about?

I dont think there is a request for that in here. If it is in app, I'd appreciate a request and response written for that.
here is guide on intercepting and writing requests for this library.

yes it is possible, I made the pr to add it #593

authors: bardiademon jvogit unldenis


text:
Fix the model name for UI display

UI use "." as separator in metricIds, but the model name could include "." as the part of modelId between vendor and model name, such as "authropic.claude-v2", so we have to replace "." to "/", and also add ai system before the model.

LGTM

authors: jinsongo morningspace

repo: instana/otel-dc


text:
Fix for multiple $not with references

Two issues that are fixed:

We were comparing :value in the or conditions when we should have been comparing :value-blob.

We wern't handling the symbol-map datastructure properly. With ands and ors nested in just the right way, we would stop traversing the tree early.

🫡 🫡 🫡

authors: dwwoelfel stopachka

repo: instantdb/instant


text:
ilab serve doesn't warn that model name doesn't have expected model family name

Describe the bug

When ilab serve is used with custom model file, it should warn that model family name cannot be extracted and correct template cannot be selected.
To Reproduce
Steps to reproduce the behavior:
cp models/merlinite-7b-lab-Q4_K_M.gguf models/my-little-model.gguf
ilab serve --model-path models/my-little-model.gguf
ilab chat --model models/my-little-model.gguf -qq "hello" -gm

Expected behavior
Warning that no template would be applied as model family name cannot be extracted
Screenshots
Output:
<|system|>_type = {
    '1': '单人',
    '2': '双人',
    '3': '三人',
    '4': '

Device Info (please complete the following information):

Hardware Specs: Lenovo T14s
OS Version: Fedora Linux 40
Python Version: Python 3.12.3
InstructLab Version: ilab, version 0.16.0

Additional context

Fixed by https://github.com/instructlab/instructlab/pull/1297

repo: instructlab/instructlab


text:
Supports pull request comment event

Changes

Pick https://github.com/int128/docker-build-cache-config-action/pull/579
Fix lint

Thank you for your contribution! @neilime


text:
🛑 Shopintake is down

In 4a910d8, Shopintake (https://www.shopintake.com) was down:

HTTP code: 403
Response time: 256 ms

Resolved: Shopintake is back up in f01cdbc after 41 minutes.


text:
Re-enable (and fix) test_toggled_outlet_does_not_trigger_fencing_update in ssi test suite

test_toggled_outlet_does_not_trigger_fencing_update (tests.integration.shared_storage_configuration.test_power_control.TestHostFencingConfig) disabled/skipped in ssi test suite in order to get #244 landed. Investigate this failure and find a fix so it can be re-enabled.

Is there a ticket opened on the actual failure that was being seen with this test?

http://jenkins.lotus.hpdd.lab.intel.com/job/integration-tests-shared-storage-configuration/1877/arch=x86_64,distro=el7/testReport/tests.integration.shared_storage_configuration.test_power_control/TestHostFencingConfig/test_toggled_outlet_does_not_trigger_fencing_update/

Covered in #315

Reopening to track the fixing of #315 and reverting of #341.

#341 has been reverted. At this point this issue is a dup of #315 I think.

authors: brianjmurrell jgrund tanabarr

repo: intel-hpdd/intel-manager-for-lustre


text:
gpio fixes

switch to dynamic allocation of gpio contexts

clean up the code (formatting/readability).  No functional changes.

Merged

authors: arfoll jontrulson

repo: intel-iot-devkit/zmraa


text:
BigMPI compatibility

BigMPI support for very large jobs
See https://github.com/jeffhammond/BigMPI for details of BigMPI implementation

Tests are required.

authors: vamironov yurialexeev

repo: intel/Intel-QS