Speed up SpanReader::findTraceIDs() for Elasticsearch

We have a service that generates two spans per trace, around 4K spans per second. It's very slow to query for the latest traces in this service.
This is the default query that is currently generated:
{
  "aggregations": {
    "traceIDs": {
      "aggregations": {
        "startTime": {
          "max": {
            "field": "startTime"
          }
        }
      },
      "terms": {
        "field": "traceID",
        "order": [
          {
            "startTime": "desc"
          }
        ],
        "size": 20
      }
    }
  },
  "query": {
    "bool": {
      "must": [
        {
          "range": {
            "startTime": {
              "from":<PHONE_NUMBER>000000,
              "include_lower": true,
              "include_upper": true,
              "to":<PHONE_NUMBER>000000
            }
          }
        },
        {
          "match": {
            "process.serviceName": {
              "query": "nginx-ssl"
            }
          }
        }
      ]
    }
  },
  "size": 0
}

This takes pretty much forever if there are many spans to aggregate:
{
  "took": 38372,
  "timed_out": false,
  "_shards": {
    "total": 5,
    "successful": 5,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": 331761,
    "max_score": 0,
    "hits": []
  },
  "other": "stuff"
}

Presumably, because ES takes full window, then sorts as many buckets
as there are traces.
Instead, we can pull the last X spans, and find unique traceIDs there:
{
  "query": {
    "bool": {
      "must": [
        {
          "range": {
            "startTime": {
              "from":<PHONE_NUMBER>000000,
              "include_lower": true,
              "include_upper": true,
              "to":<PHONE_NUMBER>000000
            }
          }
        },
        {
          "match": {
            "process.serviceName": {
              "query": "nginx-ssl"
            }
          }
        }
      ]
    }
  },
  "size": 100,
  "sort": [
    {
      "startTime": "desc"
    }
  ]
}

This is a whole lot faster:
{
  "took": 26,
  "timed_out": false,
  "_shards": {
    "total": 5,
    "successful": 5,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": 331761,
    "max_score": null,
    "hits": [
      "100 hits here"
    ]
  },
  "other": "stuff"
}

So this is 38372 / 26 = 1475x faster, which is pretty nice. Generally speedup is under 1000x, though.

Ha, this issue is #1475 just like speedup is 1475x 😦

Thanks for looking into this! It could be pretty sweet!
I'm curious about what would happen if there are only few traces with a large number of spans per service.
For e.g., let's assume that there are 10 unique traces with 10k spans all for the same service - if the new query is executed with a size of 10, would it retrieve all 10 traceIDs?

It will only return 10 unique traceIDs across the latest 1000 (value of es.max-num-spans) spans that match the query, which may as well be just one traceID. I'd personally take this tradeoff against waiting for tens of seconds for the query to finish.
I'm looking into test failures.

I understand your use case, but I'm not a fan of trading completeness for speed.
I'm wondering whether we can trigger the strategy of searching by spans and looking at traceIDs only for certain search patterns. For instance, only applying it if the search interval is less than a minute.
Or even better, are there strategies for search that are both complete and quick?

I understand your use case, but I'm not a fan of trading completeness for speed.

The tradeoff is "working ui" vs "not working ui" for me, unfortunately.

I'm wondering whether we can trigger the strategy of searching by spans and looking at traceIDs only for certain search patterns. For instance, only applying it if the search interval is less than a minute.

The larger the window, the cheaper it is to search by spans. Aggregation looks at all matched docs, while search only looks at the latest ones.

Or even better, are there strategies for search that are both complete and quick?

I created a topic in elasticsearch forum to see if there's a proper way to do this:

https://discuss.elastic.co/t/fast-way-to-find-recent-unique-fields/177351

@bobrik I tried to replicate that slow query in our environment but it ran pretty fast:
{
    "took": 177,
    "timed_out": false,
    "_shards": {
        "total": 5,
        "successful": 5,
        "skipped": 0,
        "failed": 0
    },
    "hits": {
        "total": 1087815,
        "max_score": 0,
        "hits": []
    },
    "aggregations": {
        "traceIDs": {
            "doc_count_error_upper_bound": -1,
            "sum_other_doc_count": 1087569,
            "buckets": [.....]
        }
    }
}

I tried to pick something that would match the hits.total value in your issue (331 761) but ended finding something that is 3x what is mentioned (1 087 815).
Obviously, this is not a perfect comparison, but I still wanted to try to replicate it and report back 👍

@bobrik I tried to replicate that slow query in our environment but it ran pretty fast:
{
    "took": 177,
    "timed_out": false,
    "_shards": {
        "total": 5,
        "successful": 5,
        "skipped": 0,
        "failed": 0
    },
    "hits": {
        "total": 1087815,
        "max_score": 0,
        "hits": []
    },
    "aggregations": {
        "traceIDs": {
            "doc_count_error_upper_bound": -1,
            "sum_other_doc_count": 1087569,
            "buckets": [.....]
        }
    }
}

I tried to pick something that would match the hits.total value in your issue (331 761) but ended finding something that is 3x what is mentioned (1 087 815).
Obviously, this is not a perfect comparison, but I still wanted to try to replicate it and report back 👍

May I know something detail  about the config of your environment?

@NijiadeIX I've shared number in a talk. You can get the slides from that page: https://kccnceu19.sched.com/event/MPbm/deploy-scale-and-extend-jaeger-louis-etienne-dorval-ticketmaster
Look at slide 14 and 37

@NijiadeIX this is how much data we have on daily basis (33B spans / 2TB of data per replica):
$ curl 'https://foo.bar/_cat/indices/jaeger-span-*?v&s=index&h=index,pri,docs.count,store.size'
index                  pri  docs.count store.size
jaeger-span-2019-09-11  38<PHONE_NUMBER>4      3.2tb
jaeger-span-2019-09-12  38<PHONE_NUMBER>0        4tb
jaeger-span-2019-09-13  38<PHONE_NUMBER>6        4tb
jaeger-span-2019-09-14  38<PHONE_NUMBER>0      3.8tb
jaeger-span-2019-09-15  38<PHONE_NUMBER>6      3.7tb
jaeger-span-2019-09-16  38<PHONE_NUMBER>4      3.9tb
jaeger-span-2019-09-17  38<PHONE_NUMBER>6      3.9tb
jaeger-span-2019-09-18  38<PHONE_NUMBER>2      3.5tb

We have also experienced very slow query performance, we altered the index setting, added
"eager_global_ordinals": true, to  traceID field, it looks like below
 "traceID": {           "type": "keyword",           "eager_global_ordinals": true,           "ignore_above": 256         }

@wqtty how much data do you ingest? What is your data retention?
With that setting do you experience increased disk, CPU overhead at ingestion time?

Note: this will, however, be shifting the cost of building global ordinals from search-time to refresh-time. For many use cases, this is a price that’s acceptable to pay for the improvements at search time.
https://medium.com/driven-by-code/elasticsearch-global-ordinals-31df2806391f

@wqtty how much data do you ingest? What is your data retention?
With that setting do you experience increased disk, CPU overhead at ingestion time?

Note: this will, however, be shifting the cost of building global ordinals from search-time to refresh-time. For many use cases, this is a price that’s acceptable to pay for the improvements at search time.
https://medium.com/driven-by-code/elasticsearch-global-ordinals-31df2806391f

we are having about 14k spans per second, and keep them in es for only 2 days, meaning we are having a jaeger-span index about 2.3T every day.

With that setting do you experience increased disk, CPU overhead at ingestion time?
Sorry, I didn't catch you.

If you experience increased CPU load or increased disk space allocation after you applied that setting.

If you experience increased CPU load or increased disk space allocation after you applied that setting.

not very obvious

Our elasticsearch/jaeger setup grinds to a halt as the day goes on!  Being able to control the max number of spans in the query result as a config option feels like something many folks (including me) would opt into.

I query the data of today can be very slow:
{
  "took" : 6864,
  "timed_out" : false,
  "_shards" : {
    "total" : 5,
    "successful" : 5,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : 95482,
    "max_score" : 0.0,
    "hits" : [ ]
  },
  "aggregations" : {
    "traceIDs" : {
      "doc_count_error_upper_bound" : -1,
      "sum_other_doc_count" : 95342,
      "buckets" : [...]
    }
  }
}

But I query the data of the yesterday can be very fast:
{
  "took" : 40,
  "timed_out" : false,
  "_shards" : {
    "total" : 5,
    "successful" : 5,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : 98014,
    "max_score" : 0.0,
    "hits" : [ ]
  },
  "aggregations" : {
    "traceIDs" : {
      "doc_count_error_upper_bound" : -1,
      "sum_other_doc_count" : 97875,
      "buckets" : [...]
    }
  }
}

Could somebody submit a new PR or rebase this one?

FYI re my previous comment, we've pretty much solved our performance problems by adding "eager_global_ordinals": true to the tradeId field, we currently ingest about 3.3billion spans a day and find performance pretty good

I suppose we rely on aggregations to get unique traceIds. Is there any way to distinguish the root span alone so that we could filter based on certain field to get all root spans and their traceIDs? I saw references will be empty array for  root spans. But again, it is a nested field. We could rely on parentSpanId field. But, It saw it is deprecated. Is there any possibility that we could add a new field or leverage existing field to find out root spans alone so that we can avoid this aggregation totally?

@pavolloffay, I can rebase, but it will still fail a test for reading past 10k spans and I don't really have much time on my hands to work around that.
Internally we've moved on from this a bit further, which complicates things.
Our index is sorted, so that queries can read data in order and terminate early. This required us to get rid of indexing for nested docs, which means no searching for tags in logs.
Overall there's a massive improvement in terms of docs (we used to run out of docs per segment because of nested docs!), and memory footprint:
index                  pri  docs.count store.size segments.memory segments.fixed_bitset_memory fielddata.memory_size memory.total
# Before (cluster one)
jaeger-span-2020-05-20  38<PHONE_NUMBER>3      8.9tb          17.1gb                         38gb                    0b       17.3gb
# After (cluster two)
jaeger-span-2020-05-20  38<PHONE_NUMBER>      4.8tb         192.1mb                           0b                    0b      192.1mb

Plus we're looking into Clickhouse as the backend #1438.

@RashmiRam, the aggregation is looking for traceIDs that match the tags. You can't look only at root spans, since they don't have tags of children.

Aah. I somehow missed it. Thanks @bobrik

@Stono Can I know what is your refresh interval and jvm size. I have tried using eager_global_ordinals but found no improvement after that, And our rate is very less when compared to yours.

@pavolloffay @wqtty @bobrik
I wanted to share big improvements we saw after adding "eager_global_ordinals": true to traceID field as mentioned in this comment.
https://github.com/jaegertracing/jaeger/pull/1475#issuecomment-566479808
Along with this change we also modified refresh_interval for the indices to 60s (default is 1 s for Elasticsearch).
Improvements we saw were following:

For non search endpoints (all endpoints except "/api/traces" that jaeger query makes using jaeger_rpc_request_latency_bucket metric) we saw 65-75% improvement for 90th percentile of latencies.
Same metric value for search endpoint (/api/traces) we saw 85% improvement for average latencies. (since highest bucket for this metric is 10s, earlier we could not even plot 90th percentile as it would flat line at 10s value. Hence we used average's 😄 )

Since setting eager_global_ordinals to true moves the cost of building global ordinals to refresh phase from search refresh interval helped with overall stability i believe.
We saw heap usage increase by 7-9% after this change.
Our daily index's primary store size is 200-300GB (with default settings of 5 primary shards and 1 replica). We retain data for 7 days and on average we keep 1.5-2TB of data in elasticsearch.
Let me know if you all have any questions.

@pavolloffay @wqtty @bobrik
I wanted to share big improvements we saw after adding "eager_global_ordinals": true to traceID field as mentioned in this comment.
#1475 (comment)
Along with this change we also modified refresh_interval for the indices to 60s (default is 1 s for Elasticsearch).
Improvements we saw were following:

For non search endpoints (all endpoints except "/api/traces" that jaeger query makes using jaeger_rpc_request_latency_bucket metric) we saw 65-75% improvement for 90th percentile of latencies.
Same metric value for search endpoint (/api/traces) we saw 85% improvement for average latencies. (since highest bucket for this metric is 10s, earlier we could not even plot 90th percentile as it would flat line at 10s value. Hence we used average's 😄 )

Since setting eager_global_ordinals to true moves the cost of building global ordinals to refresh phase from search refresh interval helped with overall stability i believe.
We saw heap usage increase by 7-9% after this change.
Our daily index's primary store size is 200-300GB (with default settings of 5 primary shards and 1 replica). We retain data for 7 days and on average we keep 1.5-2TB of data in elasticsearch.
Let me know if you all have any questions.

@mehta-ankit can we know your cardinality of traceID field, and what is the value of latency you have observed. For us setting the global_ordinals to true didn't help . Our refresh interval is also around 60s.

@sivatarunp I don't have the value for cardinality of traceID field. I am assuming i ll have to use cardinality aggregation to figure this out.
Avg Latencies for /api/traces endpoint have been around 500ms-1s in last 1 hour (its still early for us to hit high enough traffic on search right now). Of course it is dependent on params passed around from jaeger query (results limit, lookback value etc).
Question,

how did you set this value ? Did you set it on all your daily indices ?
We use a cronjob to set this value on each daily index when its created. Otherwise values like refresh interval and this one can be overwritten(https://github.com/jaegertracing/jaeger-operator/issues/1077#issuecomment-639488747)

@mehta-ankit  you can have a rough estimation of cardinality by traces/s metric as well. For us for lookback value of 1hr and results_limit to 20, Its taking huge time around 25-30s. Hence the worry
This is on an index which has around 40million queryable docs in the time range.
As far as to answer your question. We use es-aliases. We have the setting update in the jaeger-span-template. So each rollover will have the index created with this setting enabled

@sivatarunp ~I don't have the value for cardinality of traceID field. I am assuming i ll have to use cardinality aggregation to figure this out.~
Looks like i figured out the cardinality. It seems to be 105 million for a single day's index.
"aggregations" : {
    "traceid_count" : {
      "value" : 105056553
    }
  }

Used the following query
curl -H "Content-Type: application/json" -X GET "http://localhost:9200/<index_name>/_search?size=0&pretty" -d'{
   "aggs": {
         "traceid_count": {
             "cardinality": {
                 "field": "traceID"
             }
         }
     }
}'

Avg Latencies for /api/traces endpoint have been around 500ms-1s in last 1 hour (its still early for us to hit high enough traffic on search right now). Of course it is dependent on params passed around from jaeger query (results limit, lookback value etc).
Question,

how did you set this value ? Did you set it on all your daily indices ?
We use a cronjob to set this value on each daily index when its created. Otherwise values like refresh interval and this one can be overwritten(jaegertracing/jaeger-operator#1077 (comment))
Thanks for the info @mehta-ankit 👍 🙏
Our cardinality is around 130million per day. We have observed the high response times (25-30s) in cases where the querying service has high docs (40m)per shard. This was our test setup, where we ingested more docs of a single service to observe the pattern.  We observed better response times as the no:of docs/shard is reduced. Would you mind sharing few details like the AWS instance types which you were in use for the current setup

Closing due to inactivity.

Hey for other people coming to this thread, i've summarised all the things I changed to make jaeger -> elasticsearch super performant for our use case.  Hope it might be of use to others. https://karlstoney.com/speeding-up-jaeger-on-elasticsearch

@Stono great post! You didn't always mention the downsides of enabling various settings, so it's a bit hard to judge, but wouldn't some of these changes make sense permanently in the default index template created by Jaeger? Or do you feel that it's hardly ever a good idea to rely on the default template?

That's a really good point to be fair, I'll update it with the negatives tomorrow (which tbh are negligible for us, slightly more CPU during ingest).
I think it's hard for jaeger offer a best for all template our the box.  The default one is pretty good tbh, but I was pushing the scale.  When you start doing that sort of volume really I think you'll end up bespoke tweaking to your use case, and hardware.


Local package with a relative path in KudoOperatorTask, should be relative to its operator.yaml

What would you like to be added:
Let's say we have two operators: top-level parent and a dependency child located in a structure like this:
.
├── components
│   └── child
│       ├── operator.yaml
│       ├── params.yaml
│       └── templates
│           └── ...
│
└── parent
    ├── operator.yaml
    ├── params.yaml
    └── templates
        └── ...

then, following KudoOperatorTask definition will install the child operator:
  - name: child-app
    kind: KudoOperator
    spec:
      package: "../components/child"

however, the relative path "../components/child" is relative to the caller working directory. In other words, for this definition to work, kudo install call should be done inside the parent/ directory. This makes the operator installation a brittle process, where the user/makefile has to change/set the right directory prior to installation.
Suggestion:
A relative path inside a KudoOperatorTask definition should be relative to the operator.yaml holding that said definition. This way the above definition is always valid, no matter where the caller working directory is.
Note: should the child operator have another dependency in a sub-folder, then the path to it should be relative to the components/child/operator.yaml location.
Why is this needed:
To simplify/solidify installing operators with dependencies.

kudo package verify should do the same as the resolver: resolve the child operator relative to the operator.yaml referencing it.
kudo package create can be simple as long as child operators share the same base path as the operator.yaml (meaning the same level as templates or deeper). Otherwise, we should probably throw an error.


Sync Payment Terms Update/Automatically

This seems to highlight that the only way to update Payment Terms from BC to the integration table is via a custom extension.
Can you sync payment terms automatically, if so, how? Is the full extent of how Common Data Services and Dynamics 365 Sale Sync documented cohesively?
Regards

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

ID: 642b847f-299f-3489-0db9-44f49b46a8bc
Version Independent ID: 7eaf5cc4-ce22-026c-4bc6-23ef0e17b2f9
Content: Handling Missing Option Values - Business Central
Content Source: business-central/admin-cds-missing-option-values.md
Service: dynamics365-business-central
GitHub Login: @bholtorf
Microsoft Alias: bholtorf

Hello,
The short answer is no, there is no standard table mapping for payment terms. The lists of the standard table mappings are complete. Here are a couple of links to the topics that describe them.

For Dataverse (formerly Common Data Service), see Standard Table Mapping for Synchronization.

For Sales, see Standard Sales Entity Mapping for Synchronization.


RuntimeException: Cannot execute an Effect versioned 3.5.6 with a Runtime of version 3.4.7

What version of Effect is running?
3.5.6
What steps can reproduce the bug?
I have a Next.js deployment at https://github.com/cschroeter/park-ui/tree/main/website using the following dependencies:
{
  "dependencies": {
    "@effect/platform": "0.59.2",
    "@effect/schema": "0.68.26",
    "effect": "3.5.6"
  }
}

The error only appears on Vercel.
What is the expected behavior?
Not to see any RuntimeException
What do you see instead?
⨯ (FiberFailure) RuntimeException: Cannot execute an Effect versioned 3.5.6 with a Runtime of version 3.4.7
    at /var/task/website/.next/server/chunks/76767.js:3:111012

Additional information
Example code:
await Effect.runPromise(
    pipe(
      Effect.fromNullable(searchParams.get('order_id')),
      Effect.flatMap((orderId) =>
        pipe(
          HttpClientRequest.get(`https://api.lemonsqueezy.com/v1/orders/${orderId}`, {
            headers: {
              Accept: 'application/vnd.api+json',
              'Content-Type': 'application/vnd.api+json',
              Authorization: `Bearer ${LEMON_SQUEEZY_API_KEY}`,
            },
          }),
          HttpClient.fetchOk,
          HttpClientResponse.schemaBodyJsonScoped(Order),
          Effect.timeout('1 seconds'),
          Effect.retry(Schedule.exponential(200).pipe(Schedule.compose(Schedule.recurs(3)))),
        ),
      ),
      Effect.map((data) => !data.data?.attributes.refunded),
      Effect.catchAll(() => Effect.succeed(false)),
    ),
  )

@cschroeter - this error occurs when you have duplicate versions of effect in your program, usually as a result of out-of-sync dependencies. Strange that it only occurs on Vercel and not locally as well.
Can you run the equivalent of pnpm why effect with whatever package manager you have and see if you can see multiple versions of effect?

@IMax153
Thanks for the quick response. Unfortunately, there isn't a bun why command available right now. However I searched through node_modules and couldn't find anything with 3.4.7.

@IMax153
I could solve it by purging the cache and force a re-deploy

@cschroeter - That sounds reasonable. Let us know if it solves your issue.


[3pt]  - Add tests for comments counter - Student B

Make sure that the function for the comments counter is covered with unit tests using Jest.
Make sure that you have tests for all edge cases.

test file for comment counter has been added: Pull Request


MSOutputProducer crashing with UnboundLocalError

Impact of the bug
ReqMgr2MS (MSOutputProducer)
Describe the bug
It looks like MSOutputProducer fails to create the campaign/output map for very old workflows, which in general is Okay because we do not have very old/test workflows in the production system (if we do, we can get them archived).
However, we should change the code such that it doesn't crash if it finds a very old workflow without the ChainParentageMap attribute.
How to reproduce it
The ChainParentageMap was inserted into the requests around 2018, so any workflows before that will be able to reproduce this error.
Expected behavior
For such workflows, we can use the top level 'Campaign' attribute and map all of the output datasets to it. It won't be completely correct, but that information will not be used anyways for data insertion.
Additional context and error message
Fresh traceback from the logs:
2020-06-06 04:34:43,698:INFO:MSOutput: Running the msOutputProducer ...
2020-06-06 04:34:43,698:INFO:MSOutputStreamer: Could not open bufferFile: None. Exception coercing to Unicode: need string or buffer, NoneType foundFalling back to dictionary buffer.
2020-06-06 04:34:43,713:ERROR:MSOutput: ERR: Unable to create MSOutputTemplate for document {u'AcquisitionEra': {u'DigiFullPU_2017PU': u'CMSSW_9_0_2',
...
 u'RequestName': u'amaltaro_RVCMSSW_9_0_2TTbarLepton_13_PU25ns__HS_2017_resub_Converted_170602_105551_3888',
...
 u'_id': u'amaltaro_RVCMSSW_9_0_2TTbarLepton_13_PU25ns__HS_2017_resub_Converted_170602_105551_3888'}ERR: 'ChainParentageMap'
2020-06-06 04:34:43,713:ERROR:MSOutput: MSOutputProducer PipelineNonRelVal General Error from pipeline. Err: local variable 'msOutDoc' referenced before assignment. Giving up Now.
2020-06-06 04:34:43,713:ERROR:MSOutput: local variable 'msOutDoc' referenced before assignment
Traceback (most recent call last):
  File "/data/srv/beHG2006h/sw/slc7_amd64_gcc630/cms/reqmgr2ms/0.2.5.pre5/lib/python2.7/site-packages/WMCore/MicroService/Unified/MSOutput.py", line 588, in msOutputProducer
    pipeLine.run(request)
  File "/data/srv/beHG2006h/sw/slc7_amd64_gcc630/cms/reqmgr2ms/0.2.5.pre5/lib/python2.7/site-packages/Utils/Pipeline.py", line 139, in run
    return reduce(lambda obj, functor: functor(obj), self.funcLine, obj)
  File "/data/srv/beHG2006h/sw/slc7_amd64_gcc630/cms/reqmgr2ms/0.2.5.pre5/lib/python2.7/site-packages/Utils/Pipeline.py", line 139, in <lambda>
    return reduce(lambda obj, functor: functor(obj), self.funcLine, obj)
  File "/data/srv/beHG2006h/sw/slc7_amd64_gcc630/cms/reqmgr2ms/0.2.5.pre5/lib/python2.7/site-packages/Utils/Pipeline.py", line 71, in __call__
    return self.run(obj)
  File "/data/srv/beHG2006h/sw/slc7_amd64_gcc630/cms/reqmgr2ms/0.2.5.pre5/lib/python2.7/site-packages/Utils/Pipeline.py", line 74, in run
    return self.func(obj, *self.args, **self.kwargs)
  File "/data/srv/beHG2006h/sw/slc7_amd64_gcc630/cms/reqmgr2ms/0.2.5.pre5/lib/python2.7/site-packages/WMCore/MicroService/Unified/MSOutput.py", line 625, in docTransformer
    return msOutDoc
UnboundLocalError: local variable 'msOutDoc' referenced before assignment
2020-06-06 04:34:43,714:INFO:MSOutput<EMAIL_ADDRESS>Total 14 requests processed from the streamer.
2020-06-06 04:34:44,042:INFO:MSManager: Total outputProducer execution time: 18 secs

@todor-ivanov I think you were already aware of this bug, but I could not find any GH issues made for it, so here it is.


Cant Log On

I just downloaded Procurement 1.9.9 and after i run the program it ask me to log in using my email and password.  After i enter my info it Autenticates, fetches account name, load characters, then it says Done! Right after that i get an error message ( Error getting items for league , are you sure your league settings are correct?) and it crashes telling me to submit a ticket.  I don't know how to check my league settings when i haven't even been able to log onto procurement yet to change the settings.  I found this thru a youtube video guide and this will be my first time using the program.  Thank you

Are you a steam user? Have you tried logging in using sessionID?


Error adding Azure CMS

Issue Type: Bug
Getting an error after adding an Azure server as a CMS and trying to expand

Note that Azure DBs are not supported as CMS so an error is expected, but it should be giving a better error.
Azure Data Studio version: azuredatastudio 1.8.0 (763080aea044accfd9a44b8676f6a6cd8da2841a, 2019-06-03T22:08:37.910Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz (2 x 2200)

GPU Status
2d_canvas: disabled_softwarechecker_imaging: disabled_offflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: disabled_offnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwaresurface_synchronization: disabled_offvideo_decode: disabled_softwarewebgl: disabled_offwebgl2: disabled_off

Load (avg)
undefined

Memory (System)
7.00GB (3.73GB free)

Process Argv

Screen Reader
no

VM
0%

Being tracked here - https://github.com/microsoft/azuredatastudio/issues/5858
Investigating and will have a fix by tonight.

Reopening. Note that while the error message is the same this specifically is more about displaying a useful error when attempting to add an Azure server to CMS (which I don't believe it does currently).

Fixed by https://github.com/microsoft/azuredatastudio/commit/6197279e83d0cbb4e974c774854bd84b38498548


deprecation warnings...

...for Base.String  -- use AbstractString
...for Base.Nothing -- use Void
This is on Julia 0.4.1.  So many warnings--dozens--I am surprised no one else has reported.
Do I have some config problem?  On OS X 10.11

I see someone has a pull request to fix already, so as soon as it's integrated, good to go.


switch css processing to postcss from sass

Hello I created this fork because I wanted to contribute on tweaking the css for Prose but couldn't install the old node-sass dependencies on my new M1 Mac laptop, so I decided to switch the css build system to something more modern, faster and easy to install.
Feel free to close this without comment if you want but I think it is a small change that can benefit in contributing to this project for many people. Features of Sass used in the project (decoupling CSS in various files) stay the sime, but now they use the standard CSS https://github.com/import rule with .css files.

You can check my fork at github.com/juandjara/prose if you like, I have added some more things like some tweaks to responsive CSS for small screens, faster initial loading of repos, better handling of initial loading states. Its deployed at prosecms.netlify.app and the gatekeeper service is also deployed as a netlify function there. Because of that the handling of oauth credentials is a bit different

Thanks for this contribution! I don't have the capacity to run this code, but reading it over looks good to me.


php refresh_db.php Fatal error

PHP Fatal error:  Class 'mysqli' not found in /volume2/web/konnichiwa-master/scripts/add.php on line 5

php version 7.0

I think you just need to install mysqli. You can try this. I shoul probably add this as one of the requirements.

If you're on ubuntu, you can try this askubuntu answer. Check the comments on that answer and the chat as well if it doesn't fix your problem.

@dezhaoma If you are able to fix your issue, please do let me know, or if you need more help.

@dezhaoma If you are able to fix your issue, please do let me know, or if you need more help.

thanks , actually i've installed it on my synology nas , which do not contain mysqli , i've also installed appache 2.4 、php7.0 、phpadmin 、web station 、mariadb5 on my nas ; synology package center does not contain mysqli , there is mariadb only ,maybe i should build a docker image for my nas , and it works well on my ubuntu server .


Update get-started.md

Just a small edit to metadata

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

File
Status
Preview URL
Details

docs/skills/get-started.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Face Mesh - no z coordinate

Hello,
I got the javascript example for the face mesh to work, but inside of the landmarks are only x and y coordinates (and a visibility that is always "undefined")
How can i get the z coordinate for the landmarks?

Hello, Same problem here.
"multiFaceLandmarks" contains 2D coordinates array. There is no z coordinate value from onResults callback in FaceMesh javascript.
@mediapipe/face_mesh
0: {x: 0.6552373170852661, y: 0.7516689300537109, visibility: undefined}
1: {x: 0.6646785140037537, y: 0.6616325974464417, visibility: undefined}
2: {x: 0.6567336916923523, y: 0.698333203792572, visibility: undefined}
But<EMAIL_ADDRESS>landmarks contains z coordinates.
How can I get z coordinate from mediapipe-facemesh?

I think this is a problem with the javascript version as mediapipe hands has the same problem. https://github.com/google/mediapipe/issues/1429.  The python version does produce the z axis.

I think this is a problem with the javascript version as mediapipe hands has the same problem. https://github.com/google/mediapipe/issues/1429.  The python version does produce the z axis.

Any updates on the coordinate availability yet ?

Hi @LucaJunge,
You are right, Z coordinate is predicted by the model but need to be propagated to the API.
@mhays-google Could you please provide an estimation on that?

hey there, just saw v0.8.6 added 3D landmarks for Pose and Holistic -- any updates for this issue?

This should be a thing now.  I demo the 3d landmarks in Pose, but there are
some issues making the demo work well for holistic (namely, the face and
hands landmarks aren't real 3d coordinates).  But in both solutions, the
landmarks are there and are exposed in the results as poseWorldLandmarks.
On Tue, Jul 6, 2021 at 2:10 AM s @.***> wrote:

hey there, just saw v0.8.6
https://github.com/google/mediapipe/releases/tag/v0.8.6 added 3D
landmarks for Pose and Holistic -- any updates for this issue?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/google/mediapipe/issues/1422#issuecomment-874595605,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKQBFJA5BCQPAEBQXPYVKLTWLCAZANCNFSM4VF66AOQ
.

Hi @LucaJunge, Did you get a chance to go through the above comment. Thanks!


Ridge and error

Would be nice that in the model you directly return as well the error
Which error should be calculated ? Currently in the iamage project there is this:
var Y = predict(Xs, model);
var err = 0;
for (let i = 0; i < Xs.length; i++) {
    err += Math.abs(Y[i][0] - Ys[i][0]);
}

It has to be the Root Mean Squared Error. It is the function minimised by the method.


DotNet API Browser: Namespace descriptions missing information

Description
On the 'https://docs.microsoft.com/en-us/dotnet/api/?view=...' page, there is missing information for some of the namespace descriptions. The missing information seems to be related to the process of scraping the information from the individual namespace pages where there are links to any urls at 'https://docs.microsoft.com/en-us/dotnet/api' but does not seem to be affected by urls at 'docs.microsoft.com/visualstudio/msbuild/'.
To Reproduce
Steps to reproduce the behavior:

Go to .NET API Browser
Scroll down to 'Microsoft.Build.Framework Namespace'
Open the Microsoft.Build.Framework Namespace page in a separate window or tab
Compare the description on the API browser page to the summary on the Namespace page.
See error

Expected behavior
Each description should include the same information that the linked page summary has.
(e.g. The description for the Microsoft.Build.Framework Namespace description should read:
"The Microsoft.Build.Framework namespace contains the types that define how tasks and loggers interact with the MSBuild engine. For information, see MSBuild."
as opposed to:
"The namespace contains the types that define how tasks and loggers interact with the MSBuild engine. For information, see MSBuild."
Screenshots

Desktop (please complete the following information):

OS: Windows 7 with Service Pack 1 (Build 7601)
Browser Chrome 78.0.3904.97 (64-bit)

@chezzwizz Thanks for taking the time to report this issue.
I've flagged the issue for a member of the .NET experience team to ensure they are aware of it, and see if and how they can help.
Appreciate your contribution to our community.

@chezzwizz @mlottner We are aware of this issue, and tracking it internally. Thanks!

Duplicate of: https://github.com/MicrosoftDocs/feedback/issues/637

@chezzwizz Thanks again for your feedback.
I'm closing this issue here as the relevant team is aware of it and tracking it internally. Feel free to open additional site feedback cases if/as needed.


add the -lts and -sts aliases to dotnet

add the -lts and -sts aliases to the dotnet packages
Related Issue: https://github.com/NixOS/nixpkgs/issues/260915
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

This is my very first PR, please if I forgot something or I did something wrong feel free to tell me, I am here to fix it!

I see, that is entirely my mistake, I should have followed these information!
Time to learn how to amend old commits and fix them for me!

Is there a general agreement that -sts is meaningful?
Please see https://github.com/NixOS/nixpkgs/issues/260915#issuecomment-1831385042.


allow to change page limit

currently the page limit is limited to max 50 pages. but i want to see more. it was unlimited previously. could you add option to edit it when creating a bullboard? (parameter)

Hi, there is no change to the lib regarding to the number of pages.
Pagination is based on the params that bull / bullmq returns.
Can we debug that somehow?

There is no such limit...

Closing, feel free to re-open when you have more info

sorry i meant 50 jobs PER page. not 50 pages
@felixmosh

You have a setting for this, no?

yes, but i cannot change it to value greater than 50. can do 50 or less

Make a PR for this?
https://github.com/felixmosh/bull-board/blob/master/packages/ui/src/components/SettingsModal/SettingsModal.tsx#L82


Nate/feature/LOOP-1293/display mock cgm status progress

https://tidepool.atlassian.net/browse/LOOP-1293
displaying the mock cgm status progress

Updates include suggested updates from the PR along with updates requested from the design review.


Think through data prop feedback

Gather feedback on whether devs think that using a singular data prop is better or worse than individual props with primitives when using Hydrogen-UI/storefront-kit and the Storefront API.
Context:

Hydrogen-UI (soon to be renamed to storefront-kit) is a collection of React components that are built specifically for the Storefront API and its objects.
It is not a goal of Hydrogen-UI to be a general-purpose component library; in other words, an <Image/> component is intended to only work with Storefront API Image, a <ProductProvider/> component only works with a Storefront API Product, etc.
The majority of these components are "leaf nodes"; in other words, they are often the last rendered component in a React tree and do not have children.

Considerations:

Which is the best DX?
Are there performance implications by choosing one over the other?
Do either create patterns in developer's code that we want to encourage or discourage?
Could we enable both patterns, and if so, are there downsides?

Examples
data prop:
const product = getProductFromStorefrontApi();

return (
  <Image data={product.image}/>
)

Individual props:
const product = getProductFromStorefrontApi();
const {src, width, height, altText} = product.image;

return (
  <Image src={src} width={width} height={height} alt={altText}/>
)

(Feel free to add your thoughts to this issue)

I posted this question internally and there is a significantly larger portion of devs that prefer individual props to a singular data prop so far.

If you add the data prop, is it possible to override certain values?
Say we use imgix to get the images because of its performance improvements, does that mean we shouldn't use the <Image> component?
Does the <Image> component generate a srcset for images?

Also, how does getting product data from sources like Algolia mean for this? The data structure could be different. I fear that the data prop assumes that all data always and only comes from Storefront API.
Headless sites will often have a mix of data sources.

I created an internal poll, and the overwhelming majority of devs there preferred individual props. As of time of writing:

59 votes for individual props
4 votes for a data prop
4 votes for "both!"

Based on the feedback received, it seems that we should move forward with individual props. It's something that I would like to have done for the 2023-01 release.

#116 is a first pass at this.

I was going to say that my knee-jerk reaction is to prefer individual props without really thinking about why. I understand the reasoning with the Image component and that the ProductProvider needs the data to match what Shopify has.
I think it's easier for devs to reshape the product data (if it comes from another source) with individual props rather than a single data prop. I also wonder if the single data prop would encourage a dump pattern where devs overfetch data and just dump it all in the data prop, including excessive data that's not used but now passed along to every page where the component is used, causing a double bottleneck of first slowing down the initial server fetch and second slowing down the response to the client.
Curious to hear if there were any arguments for or against data props in your internal poll, or if it was just a simple cast your ballot without any debate?

I think it's easier for devs to reshape the product data (if it comes from another source) with individual props rather than a single data prop.

That's a good point.
And I think the flip-side is also true - it's easier for a developer to get an object from the Storefront API and pass it as a single data prop then it is to have to spread them out.
So I guess it comes down to which experience we're optimizing for.

I also wonder if the single data prop would encourage a dump pattern where devs overfetch data and just dump it all in the data prop, including excessive data that's not used but now passed along to every page where the component is used, causing a double bottleneck of first slowing down the initial server fetch and second slowing down the response to the client.

Yeah, that's a good concern to have. I'm not entirely sure that the component itself is going to help dictate how efficient the query is, though - it seems like the component may be the wrong layer for that (e.g. someone can still just pull out an Image's src prop and pass that, while still querying for all the other fields). I would love for the Storefront API to get some query cost fields added to responses like the Admin API has, and then help optimize at that layer instead. One day, maybe.

Curious to hear if there were any arguments for or against data props in your internal poll, or if it was just a simple cast your ballot without any debate?

Some hightlights:

One good argument for individual props was that the TypeScript DX is better for that, compared to the current situation where we use PartialDeep<Image> for `data.
Individual props could lead to devs using the spread pattern <Image {...product.image}/> which could both be good and bad; good in the sense that for a simple thing, like Image, that works fine, but for a Product, we probably don't want to encourage spreading all those potential props to the component when we probably only need a few props. (prop collision, or props eventually getting rendered to the DOM as HTML attributes, as many of these components do pass-through props so you can control the native HTML element as you desire)
The data prop can be good if the explicit goal of Hydrogen-UI (storefront-kit) is to be a set of components purpose-built for the Storefront API and not for any other APIs or data. It provides for a simpler DX than having to extract properties from those objects just to get the components to work.

My gut reaction is to prefer individual props as it’s more explicit about what you’re passing (less magic ✨). But, to your last point, I see the value of a singular data prop given that the components are purposefully built for the Storefront API.

Discussed this with @elisenyang — we'd like to proceed with the plan to support both. We will keep the simple mental model of CSS classes vs. inline styles …
In other words,data is the only prop you need. Sensible defaults are set where data lacks appropriate information. Individual props override data when set, and where appropriate.
This is a better solution than the spread pattern, as certain components may not want to have the value from data provided as the actual prop value … for example, product.featuredImage.width would be the original width … e.g. 4000px … that would be an inappropriate value for the width prop in virtually every use case.
As an example of how the above proposal would play out, I've updated the Image component PR to follow this behaviour. https://github.com/Shopify/hydrogen-react/pull/114


Example appears to contain a syntax error

USE AdventureWorks2012;
GO
EXEC sp_procoption @ProcName = '<procedure name>'
, @OptionName = ] 'startup'  /* <-- Syntax error? */
, @OptionValue = 'on';

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

ID: a260067f-c0fc-2a45-82c2-795ae1bb8dc6
Version Independent ID: e06f1f7e-1c5f-a494-7038-241053d5298a
Content: Execute a Stored Procedure - SQL Server
Content Source: docs/relational-databases/stored-procedures/execute-a-stored-procedure.md
Product: sql
Technology: stored-procedures
GitHub Login: @stevestein
Microsoft Alias: sstein

@pcleckler -- Philip, thank you for your feedback.  I am looking into this document.


pico_audio_i2s incompatible with USB stdio

It seems that the pico_audio_i2s library intermittently breaks the standard USB stdio implementation, resulting in no communication either way between the pico and the USB host after a short time (a few seconds to a minute or so).
The host still reports the USB CDC connection (e.g. /dev/ttyACM0 continues to exist) but communication ceases.
For example, the pico-playground sine_wave example exhibits this problem, if USB communication is enabled through adding pico_enable_stdio_usb(sine_wave_i2s 1) to the i2s section of CMakeLists.txt.  (In that example, the problem is evident as the terminal user interface initially works, then ceases to function).
Is this a known issue  -- and is there a known workaround?

I'm afraid this is just a "random guess", but the USB protocol is timing-sensitive, so if the Pico doesn't respond to USB requests from the host "quickly enough", the USB channel might go awry. Do you see any USB-related errors in the dmesg log?
In an entirely-separate project I was working on recently, I was able to solve this problem by running the USB-related code (in my case I was using tinyusb to emulate a HID mouse) on core1, with the rest of my application running on core0. (and then using https://www.raspberrypi.com/documentation/pico-sdk/group__multicore__fifo.html to communicate between the two cores)

I've just checked dmesg and this doesn't reveal anything.
I've also tried the suggested use of core1 in sine_wave_i2s, and am seeing same problems --- when commenting out the stdio use in the main thread, and adding multicore_launch_core1(other_thread); with the function
void other_thread()
{
	static int count=0;

	while (1)
	{
		busy_wait_ms(100);
		printf("%d\n",count++);
	}
}

Debug probe is arriving tomorrow, which should at least let me see if UART stdio suffers from the same problem.

yeah UART is likely much better; the stdio_usb stuff has a bunch of IRQ stuff to deal with running TinyUSB in the background, which is likely the source of issues.
Note you are much better off running your code on core 1, as all the stdio_usb stuff has already been initialized on core 0


Add Chip_seq_genomic_ranges_tutorial

Added a tutorial for aligning ensembl db annotations and chip-seq data from ENCODE. Also includes bio frame capabilities and genome features filtering example.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.96%. Comparing base (ef33d87) to head (5927226).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #65      +/-   ##
==========================================
- Coverage   93.09%   92.96%   -0.14%
==========================================
  Files           6        6
  Lines         333      341       +8
==========================================
+ Hits          310      317       +7
- Misses         23       24       +1

I've pushed a commit that should make the docs render

@ivirshup This should now be ready for review/merging!

Thanks a lot for the great contribution! I left a few comments!

Thank you both for reviewing @ivirshup @lauradmartens ! I hope I addressed all of your comments, please let me know if there's anything else that should be changed or if anything remains unclear.


Show Graph/Group theoretic properties

The idea comes from here. Interesting might be growth of groups and some other things.
https://www.reddit.com/r/math/comments/1aimjq8/understanding_groups_and_drawing_pretty_pictures/

This might be done with GAP #78


Headers are prefixed with HTTP_ in Rack.

It was passing before because the previous #headers in Formatter was wrong, this is the correct behavior.

Thanks. I merged this and the previous change to frontier as well.


add i18n boilerplate

https://phrase.com/blog/posts/internationalization-i18n-go/

go get -u github.com/nicksnyder/go-i18n/v2/goi18n

This is very confusing. The best way forward is not to try and implment this in Arcadia. Try it out in Cobrass first, perhaps have multiple branches reflecting different approaches, eg using the message printer or using Nick Snyder's go-i18n


Remove Stride integration

The Stride service was shutdown on February 15th, 2019.

@Qmando can you review?


fix bugs

Please don't alter the indentation of the project as it makes it impossible to focus on the actual code changes in a PR, just look at the "Files changed" tab of this PR to see the effect.
If you put the indentation back I'll happily review this PR again as right now I can't see what bugs you've fixed.

I am sorry for that I put the indentation changes to the PR. I will close this and create another one


IDVA6-1211: Determine isActive if before invitation date + 7 days

Short description outlining key changes/additions
Added functionality to correctly determine the isActive status for each invitation based on their individual expiry dates.
JIRA Ticket Number
https://companieshouse.atlassian.net/browse/IDVA6-1211
Type of change

[x] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: No security warnings found

CI: No security warnings found


Running ./create_build_env.ps1 to create windows package ends with error: invalid command 'install-pywin32-windows'

When creating the build environment to create the window's package the build ends/ fails with error: invalid command 'install-pywin32-windows' and prompts for a Repository and Full URL.
Exact Message -
Command "c:\python27\python.exe -c "import setuptools, tokenize;__file__='C:\\temp\\salt\\setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps" failed with error code 1 in C:\temp\salt\
Enter a Repository (full URL only):

I'm building on a 64Bit system and scrolling back up to the begining it seems the install script recognizes this. Any help much appreciated.

Tried installing separately through pip and it seems to already be satisfied, looks to genuinely be a bad command inside the script. Was able to complete creating the build environment.

I have talked to the guys at SaltStack, and they recognize this as a big in their code.  until they fix it I have found that instead of running line 64 "pip install -e .", you replace that with "python ./setup.py --quiet install --force;" and it seems to finish fine.  I will update this in the code

https://jira.corp.adobe.com/browse/CSTTEAM-44033


Support weapon and armor automation on NPC sheets.

In GitLab by @jonbonazza on Apr 1, 2022, 19:32
Unlike with Player Characters, if you create an NPC and give it weapons and armors in their inventory, there's no way to automate them.

This has been implemented for weapons now, armor isn't really feasible to implement. Closing as completed / won't fix.


python2.7-nevow: 0.11.1 -> 0.14.2

Motivation for this change
Tahoe-LAFS can't do deep checks of files without this update; a dependent code path is broken.
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Nevow has one user, Tahoe-LAFS, and that one user has broken functionality with old Nevow, so I'm bumping.

does this also affect stable?

@Mic92 I didn't push to stable, if that's what you mean.

My question was if Tahoe-LAFS on stable has the same incompatibility.


MDX support and user documentation infrastructure

Enable MDX in the Solid-Vite toolchain (this was a big pain since it's basically undocumented)
Stub landing page for help/user documentation
Toolbar button to access the help landing page
Additional page with project credits

The help content is mostly a stub so far but merging now so that we can work in parallel on this and other UI tasks.


Sign Up button on homepage goes to old signup page

Not sure how to enter the correct link

found the right code for the link
https://github.com/BCDevExchange/devex/commit/0a68ccd97ba5dd8d3efbc874d4a4862ec3de7e69


Fix epochs in mnist example (plots showing half correct value)

Codecov Report

Merging #176 (d229451) into dev (a40bdfd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #176   +/-   ##
=======================================
  Coverage   90.74%   90.74%
=======================================
  Files           8        8
  Lines         216      216
=======================================
  Hits          196      196
  Misses         20       20

Continue to review full report at Codecov.

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


Better handling of prototype properties in compile time or runtime

Low priority bug
When using properties name e.g toString from object prototype in jsx, babel plugin can't compile them due to Aliases,  PropAliases being objects will resolve the value from prototype Aliases['toString'] and throw. also on runtime and compile time for svg, the values from prototype will be used as prop or attribute resulting in e.g template(`<svg [object Object]="a"></svg>`, 2), or $el['function toString() { [native code] }'] = value.
SVGNamespace is similar as any propertie from prototype is considered to be a valid namespace.
The fix is to make the objects null prototype using Object.assign(Object.create(null), {}) or Object.setPrototypeOf({}, null). Or would Map be better, we already use Set but with Map  more changes are required.

Cna you give me an example of the code you write to achieve this?

https://playground.solidjs.com/?hash=1699428709&version=1.5.5


Create Mentorship Meeting Artifact

Use https://github.com/nodejs/create-node-meeting-artifacts to automatically Create Google Docs for Meeting Notes for Mentorship

Use GActions To Create the Issue Weekly: https://github.com/pkgjs/meet
Use The Create Node Meetign Artifacts for Generating the Google Docs

We need to integrate both, so each time an issue is created, the gdocs is created also and linked together.


Increase default HTTP timeout

Problem

Currently, httpx.ReadTimeout errors can be encountered easily (#197).
Suggested solution

We should increase the default timeout, however I do not know by how much.
We should look into how Prisma handles this.

30 seconds is the default timeout used by undici which is what Prisma uses and does not change: https://github.com/prisma/prisma/blob/6beab132e9f47216d7b968a5f1e0956f2a895a0b/packages/engine-core/src/binary/Connection.ts#L56


Where could I find the filter list of aistplusplus

Hi，thanks for sharing such a great dataset. I have downloaded the dataset but failed to find the ignore_list.txt which is mentioned in AIST++ websites ?

It's included in the annotation.

Thanks a lot！


Camera is ready

Camera has been added to both Android and Arduino side.

Nice work, just change the final strings 'FAIL' and 'SUCCESS' so they say "Connection to TANK established" and not GeoBot, and as Lucas mentioned no need to take away the Ultrasonic sensor logging. Other than looks fine.

Thanks! I've changed the Client file.


Add uptime alerts for Raspi, Jetsons, and cameras

Mostly completed using healthchecks.io and direct pushes from the respective devices. Still need to add Jetson KoeyeFu and the cameras.


Not really a Issue

I had a quick question I wondering if you have any of the Scripts you had from armaholic before it died?
I'm looking for the data download script.

Hey, sorry for the late response.
the data download script is contained in the SME.Gen Missions, see:
https://github.com/T-800a/SME.Gen/tree/development/_SMEGen_.Altis/scripts


Segmentation tool

Hi,
Could you please provide a link to the off-the-shelf segmentation tool (for "Depixelizing Pixel Art") that you have used for generating  your clustered samples,  so that we can cluster our dataset before using it to train im2vec? Will im2vec work without these clustered samples?
thanks

Hi,
Based on the paper, my understanding was that im2vec can work on image datasets that do not  have a vector counterpart. But based on your response it seems like during preprocessing we either need the SVG counterpart or use an algorithm to perform segmentation/clustering. I looked though your codebase but could not find the segmentation code or preprocessing code you are referring to (in experiment.py, there is a train_dataloader() but it does some standard image transformations on the already preprocessed dataset).
I am interested in training/evaluating im2vec on 2 public icon datasets for reconstruction as well as generating variations.  One of the datasets has both the image and svg files, while the other has only the image files. Some of these icons are colored while the others are just black and white.

Could you please provide some guidance on the preprocessing steps involved for the dataset that has only the image files?

Also, could you please provide some guidance on the preprocessing steps involved for the dataset that has both the image and svg counterpart?

Alternatively, if  you already have the preprocessing code for each case,  is it possible to share that?
Thanks for your help.

Hey,
Yes, you are right we do not need the vector counterparts for im2vec however the input images need to be preprocessed to get the best results. Yes, you are also right that the codebase doesn't contain any preprocessing code.
In my case I used this bit of code to generate colored images of the font https://gist.github.com/preddy5/c626189cbf548d915d0079b9a40cdb08 this code takes ttf(this is often how font are stored) files as the input and saves a colored png file, you could do something similar with SVG files.
For icons and emojis examples shown in the paper, I colored some of them manually using photoshop. Depending on the size of your dataset you could maybe try doing it manually or automate it using segmentation algorithms either like the one, I mentioned earlier or opensource implementations like this one https://github.com/vvanirudh/Pixel-Art/tree/e929ef1bdd9b1c46f063f309a3309bd362e51097
Hope that helps

Hi,
For font datasets, some recent methods like DeepVecFont generate the drawing commands from images/ttf, which are then used for reconstruction and variations.   For a large dataset of generic icons with complex topologies, I am not sure how feasible it is to automate the clustering process based on colors, but thanks for the links, I will check it out.


Build Solution fails

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Upon invoking "Build IoT Edge Solution" command from VS Code

Any log messages given by the failure

Sending build context to Docker daemon  12.08MB
Step 1/12 : FROM mohaseeb/raspberrypi3-python-opencv:latest
Get https://registry-1.docker.io/v2/mohaseeb/raspberrypi3-python-opencv/manifests/latest: unauthorized: incorrect username or password
Expected/desired behavior

Build should succeed

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10, VSCode 1.25.1, Docker for Windows Community Edition Version 18.06.0-ce-win72 (19098)
Channel: stable

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Hi, any updates on this?

Closing since the docker logout command should have fixed it. Let me know if this is not the case.


How can i change the label color of FormBuilderSearchableDropdown?

How can i change the label color of FormBuilderSearchableDropdown?
Any Sample please

Due to lack of response, I will close this issue.
If the bug still exists, feel free to open a new issue


docs: CRD example specs

Add example specs.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 55.25%. Comparing base (37f1f10) to head (2175830).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
+ Coverage   54.98%   55.25%   +0.26%
==========================================
  Files          10       10
  Lines        1133     1133
==========================================
+ Hits          623      626       +3
+ Misses        434      432       -2
+ Partials       76       75       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


flake init

Description

I know the nushell maintainers aren't super familiar with nix and while I am
completely unqualified to explain nix to anyone, I can at least provide a tl;dr
about flakes and what the files do.
flake.nix
flake.nix is a (purish) function that describes how to build and package
applications. The inputs to this function are typically buildtime/runtime
dependencies (rustc, cargo, nushell, etc.), and developer tooling
(clippy, rust-analyzer, etc.).
The function outputs can contain multiple things including runnable
applications, developer environments, nix modules, etc.
flake.lock
flake.lock version-pins the inputs to the function. This means you get extremely
consistent reproducibility to the build function outputs. This is one of the
main reasons people love flakes so much.
result/
nix build will symlink the built derivation to the result directory.
This should be included as an entry into .gitignore.
I also left a some comments in flake.nix to help explain a few things.

I've packaged this so that one could use nupm-lib to import nupm as a module and/or use nupm-test as a runnable application to test a local repository:

We recently started a repository to store various integrations: https://github.com/nushell/integrations. If possible, flake.nix would be better stored there to avoid spreading too many files around unrelated to the project.
That being said, I think it's still too early to distribute nupm. We even released any version of it yet.

Thanks for your feedback!

We recently started a repository to store various integrations: https://github.com/nushell/integrations. If possible, flake.nix would be better stored there to avoid spreading too many files around unrelated to the project.

I don't think so. That would need a much larger flake.nix that would encompass more than nupm.
I also don't agree that the files are 'unrelated to the project', they are very specific to nupm in that they package nupm and provide a developer shell for nupm (it's worth noting that the devshell doesn't have nushell-nightly yet so it's a work-in-progress).
Just to be clear. I've made sure this is as non-invasive as possible. The use of this flake is 100% optional and should have no effect on anything outside of the nix-ecosystem.
I'm also happy to maintain these files and be pinged for any problems/questions/help.

That being said, I think it's still too early to distribute nupm. We even released any version of it yet.

This isn't actually distributing anything, it's just packackaging nupm so that users don't have to write the nix expressions themselves. This isn't the same as being in nixpkgs.
I would also like to point out that nufmt has a flake: https://github.com/nushell/nufmt/pull/41

I mean, yes, it's related to the project, but we could quickly get our repository cluttered with all the different package manager files that would ultimately be our responsibility to maintain. @MangoIV made an external flake for Nushell here: https://git.sr.ht/~mangoiv/nu-shell.nix, so I guess it's possible to have a flake outside the project. Couldn't the flake pull from https://github.com/nushell/nupm instead of requiring local files? The advantage of https://github.com/nushell/integrations is that we can add some CI checks to test the packaging, and it is meant to be community-maintained, to avoid having the core team to maintain package manager and distro files in our core repositories.
The flake.nix in nufmt came before we had https://github.com/nushell/integrations, it should probably be moved there as well.

we can have inputs.nupm.url = ... inputs.nupm.flake = false, then nupm will get pinned to the most recent commit on the rev and is available as a store path via inputs.nupm

You can absolutely package this outside of the source repo (this is how nixpkgs works). However, some users can find this quite cumbersome, for example nix run github:nushell/nushell is much easier to remember than nix run sourcehut:~mangoiv/nu-shell.nix.

I mean, yes, it's related to the project, but we could quickly get our repository cluttered with all the different package manager files that would ultimately be our responsibility to maintain.

I'm not sure I understand this comment as it seems very speculative. I never implied all package formats should be included in this repo. I would also like to point out that I volunteered to maintain these files.

The flake.nix in nufmt came before we had https://github.com/nushell/integrations, it should probably be moved there as well.

To be fair, this pr existed before that repository as well.
Seeing as the nufmt flake being accepted is the only reason I even opened this, I will close this.
Thanks very much for your time @kubouch @MangoIV!

You can absolutely package this outside of the source repo (this is how nixpkgs works). However, some users can find this quite cumbersome, for example nix run github:nushell/nushell is much easier to remember than nix run sourcehut:~mangoiv/nu-shell.nix.

To make it less cumbersome, we started the nushell/integrations repo, so at least related package manager files could be in one place under the nushell org. Feel free to put it there.

I'm not sure I understand this comment as it seems very speculative. I never implied all package formats should be included in this repo. I would also like to point out that I volunteered to maintain these files.

Once we accept something to our codebase, it is ultimately the core team's responsibility to maintain it (or remove it if we can't maintain it). People come and go, so if you were in a situation unable to maintain it in the future it would fall on us. But it's great to see people wanting to help out and maintain stuff, I'd be happy to put the flake nushell/integrations.

To be fair, this pr existed before that repository as well.

Yeah, somehow I didn't notice it earlier.

I'd be happy to put the flake nushell/integrations.

Such a flake would be quite a bit more complex as it would eventually hold derivations for many nushell projects and I'm not comfortable maintaining something like that, although I would love to use/contribute to it should someone take the initiative.
I can solve all these problems within my own projects so it isn't a big deal to me, I was just trying to upstream a solution.
Thanks again!


ENH: update package version

Hi! This is the friendly automated conda-forge-webservice.
I've started a version update as instructed in #8.
I'm currently searching for new versions and will update this PR shortly if I find one! Thank you for waiting!
Fixes #8

@conda-forge-admin, please rerun bot


lisa_shell: fix reported URL

Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries,
requiring API requests to either:

originate from pages served by this server
(validated with XSRF cookie and toekn)
authenticate with a token

This patch adds support to generate a random token and report it in the
complete URL thus allowing the user to properly get the complete address
where her server is running.
Signed-off-by: Patrick Bellasi<EMAIL_ADDRESS>

@bjackman give it a try when you can and then merge... it's not urgent ;-)


missing information in h_str

Information

Qiskit Terra version:
Python version:
Operating system:

What is the current behavior?
Channel indices are missing in device Hamiltonian information.
['_SUM[i,0,19,wq{i}/2*(I{i}-Z{i})]',
 '_SUM[i,0,19,Omegad{i}*D||X]',
...
 'Omegad*U0||X',
 'Omegad*U1||X',
 'Omegad*U2||X',
 'Omegad*U3||X',
 'Omegad*U4||X',
...
 'Omegad*U40||X',
 'Omegad*U43||X',
 'Omegad*U42||X',
 'Omegad*U45||X',
 'Omegad*U44||X',
...
 '_SUM[i,0,19,Omegam{i}*(M{i}||C{i}+M{i}||A{i})]']

Steps to reproduce the problem
see configuration().hamiltonian['h_str']
What is the expected behavior?
X, D and Omegad requires corresponding channel index.
Suggested solutions

Closed with the release of v2.2.1 backend code.


After using unique method on Collection it breaks json output

Laravel Version: 8.65
PHP Version: 8.0
Database Driver & Version: pgsql

Description:
I have a collection that I am returning as a JSON response
and now if I remove any elements from the collection it breaks the JSON response as follows
Code in routes/web.php
Route::get('/', function () {
    $users = User::all();
    $myCollection = collect($users);
    foreach ($users as $user) {
        $user->approved = true;
    }
    $user7 = User::find(7);
    $user7->approved = false;
    $myCollection->push($user7);
    $user11 = User::create([
        'name' => 'User 11',
        'email' =><EMAIL_ADDRESS>        'password' => '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', // password
    ]);
    $myCollection->push($user11);
    return response()->json($myCollection);
});

returning JSON looks like this without using unique
[
    {
        "id": 1,
        "name": "Dr. Anastasia Ferry",
        "email"<EMAIL_ADDRESS>        "email_verified_at": "2022-01-28T17:40:28.000000Z",
        "created_at": "2022-01-28T17:40:28.000000Z",
        "updated_at": "2022-01-28T17:40:28.000000Z",
        "approved": true
    },
   ...
]

but if I use unique in the following way it breaks my JSON output
in route/web.php
instead of return response()->json($myCollection); If I do return response()->json($myCollection->unique('id'));
the json out put breaks to
{
    "0": {
        "id": 1,
        "name": "Dr. Anastasia Ferry",
        "email"<EMAIL_ADDRESS>        "email_verified_at": "2022-01-28T17:40:28.000000Z",
        "created_at": "2022-01-28T17:40:28.000000Z",
        "updated_at": "2022-01-28T17:40:28.000000Z",
        "approved": true
    },
    "1": {
        "id": 2,
        "name": "Ms. Renee Konopelski DDS",
        "email"<EMAIL_ADDRESS>        "email_verified_at": "2022-01-28T17:40:28.000000Z",
        "created_at": "2022-01-28T17:40:28.000000Z",
        "updated_at": "2022-01-28T17:40:28.000000Z",
        "approved": true
    },
...
}

so instead of an array, it becomes an object now
Steps To Reproduce:
Step 1: Create Fresh Laravel Project
Step 2: Do Migration by using command php artisan migrate
Step 3: Generate some random users by running User::factory()->count(50)->create(); in tinker
Step 4: Paste Following Code into the routes/web.php file
Route::get('/', function () {
    $users = User::all();
    $myCollection = collect($users);
    foreach ($users as $user) {
        $user->approved = true;
    }
    $user7 = User::find(7);
    $user7->approved = false;
    $myCollection->push($user7);
    $user11 = User::create([
        'name' => 'User 11',
        'email' =><EMAIL_ADDRESS>        'password' => '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', // password
    ]);
    $myCollection->push($user11);
    return response()->json($myCollection->unique('id'));
});

@rushi7997 Does it work if you use ->unique(...)->values()->all() instead? Looks like that should give you an array- https://laravel.com/docs/8.x/collections#method-unique

@cheryllium Yes, You are correct!
Thank you so much
I felt like that was an issue. but it was my mistake. I should read the docs carefully.
anyway closing this issue.


Clarify local build instructions

I stumbled into this when I was attempting to build it locally. The naive approach of just running cargo build in wasmtime just gives you the CLI, not the c-api.

👍


Replace DockerHub dependency

Change FROM image location to quay.io mirror location.

Need an OWNERS file for approve, so green button merging instead.


rke2: fix the update script

Description of changes

This PR set the correct working directory for the update script. At the same time, because each update script will pass the version attribute of the updated package as an environment variable (PDATE_NIX_OLD_VERSION). This is unnecessary to use nix-instantiate to calculate OLD_VERSION.
By the way, the package versions of rke2, rke2_latest and rke2_testing have been updated.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

By the way, the package versions of rke2, rke2_latest and rke2_testing have been updated.

Please split that to a different commit.

@Aleksanaa Thank you for your review. It has been split.

please split and reword https://github.com/NixOS/nixpkgs/pull/326716/commits/51d74b875c100838a1a1efdf5ff0f6f7de942b80 to follow the pkgnam: oldver -> newver commit schema

It seems you removed the bump commit, is that intentional?

It seems you removed the bump commit, is that intentional?

Yes, I think we should create a new PR to update the package version after merging this PR


pancake sorting

sorting array with minimum possible reversals.

the sorting is called is pancake sorting. please lool into it.

please confirm if i should add any more.

sir, when will this be merged ?

thank you sir for your attention.