Recorded metrics are not sent to Stackdriver

I have the following recording rule:
- name: custom_group.rules
      rules:
      - expr: sum(rate(node_cpu_seconds_total{mode!="idle",mode!="iowait"}[3m])) BY (instance, job)
        record: instance:node_cpu_custom:rate:sum

The rule is evaluated and recorded correctly:
Element	Value
instance:node_cpu_custom:rate:sum{instance="<IP_ADDRESS>:9100",job="node-exporter"}	0.6291333333333333
instance:node_cpu_custom:rate:sum{instance="<IP_ADDRESS>:9100",job="node-exporter"}	1.153220537845439

I have also the following config file:
static_metadata:
     - metric: instance:node_cpu_custom:rate:sum
       type: gauge
       help: node cpu ratio

No metric appers in Stackdriver. Also no errors in the stackdriver-prometheus-sidecar logs.
This is just an example of the recorded metric. All other recorded metrics are also not sent to Stackdriver. Raw metrics are exported to Stackdriver as it should be.

Thanks for the report. I filed an internal tracker issue and someone will try to help you soon. If you are willing to try something, could you see if using a metric name without any colons (:) works? It's just a hunch, but worth trying if you have the time.

Nope, replacing colons : with underscore _ does not help

I have a similar issue. I'm exporting a gauge metric and the metric itself is autocreated in Stackdriver with no problems. Labels are correct etc. But all the values are 0 in Stackdriver, even though prometheus clearly shows them varying as containers change status. I've even verified this via the api and getting the raw timeseries from stackdriver.
static_metadata:
     - metric: kube_pod_container_status_waiting_reason
       type: gauge

Other metrics that I've checked seem to work

^ worth noting: this is not a recorded rule, just a collected metric from kube_status. I merely did the explicit static_metadata entry to see if it changed anything.

@oliver-neubauer-ecobee please file a new issue if you're not using recorded metrics. Also the original issue is about metrics not being sent. Metrics sent as 0 values sounds different.

The same issue is in v0.4.1.
In debug log i see target not found message and dropped stat recorded with target_not_found reason.

Thanks for reporting, @soymo. Just want to ask a clarification question: do you see the target not found on recorded metrics  in v0.4.1?
Also if possible, can you create a new issue describing the following setup:

Prometheus

image version
the missing target/metrics
the Prometheus configuration related to the target/metrics

Sidecar

image version
The sidecar configuration related to the target/metrics, if you have any

Thanks!

I confirmed it's a bug and I also see error target_not_found after I created recorded rules and added static_metadata.

Hi @memory - sorry I didn't provide update since last comment. Last time we suspected it's the logic in targetMatch may not be correct.
Based on the comment of this function, it should check match a label if lset has this label set. The existing code checked lset.Get(tl.Name) != tl.Value directly, but lset.Get(tl.Name) will return empty string if lset does not have tl.Name.
I didn't commit a change I was debugging on, so I just created a branch in my personal repository to track the fix. I don't think it's ready to send a PR because I don't think I fully tested it yet. Can you try it out? If you want, you can build on top of it and send a PR for us to fix the bug you are facing.
Last thing - the metric name with ":" inside is not a valid metric type (see naming rules), so you may still won't see metrics if the recorded name is instance:node_cpu_custom:rate:sum as described in https://github.com/Stackdriver/stackdriver-prometheus-sidecar/issues/104#issue-419958292.

@StevenYCChou so, some progress:

If I attempt to forward a recorded metric that aggregates away the job/instance labels, it still fails with the same cache lookup errors. :(

If I include the job/instance labels (suboptimal, but one thing at a time), we get somewhere:

level=debug ts=2019-08-29T15:10:10.164Z caller=client.go:170 component=storage msg="Partial failure calling CreateTimeSeries" err="rpc error: code = InvalidArgument desc = Errors during metric descriptor creation: {(metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile95_rate300s, error: The metric type is invalid.), (metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile99_rate300s, error: The metric type is invalid.)}."

level=warn ts=2019-08-29T15:10:10.164Z caller=queue_manager.go:546 component=queue_manager msg="Unrecoverable error sending samples to remote storage" err="rpc error: code = InvalidArgument desc = Errors during metric descriptor creation: {(metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile95_rate300s, error: The metric type is invalid.), (metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile99_rate300s, error: The metric type is invalid.)}."

The api documentation for metricDescriptors only notes that the type field is a string and doesn't suggest that there are any length/content limitations on it?

Further testing: if I drastically shorten the name of the recorded metric and remove the colons:
      - record: svc_response_latency_ms_q50_r30s
        expr: histogram_quantile(0.50, sum(rate(response_latency_ms_bucket{namespace="default", direction="outbound", dst_service=~".+"}[30s])) by (le, dst_service, instance, job))

...the errors go away, which is good, but now we're back to literally nothing happening on the stackdriver side.  No debug output at all from the sidecar, and external.googleapis.com/prometheus/svc_response_latency_ms_q50_r30s does not appear in the output of metricDescriptors.list

Hi memory@,
Thanks for sharing with us all the troubleshooting information, these are really valuable, and I really appreciate your efforts on it!
First, some comments on job/instance labels:

If I attempt to forward a recorded metric that aggregates away the job/instance labels, it still fails with the same cache lookup errors. :(

Labels job and instance are required for integration with recording rules. Here is a quote from Integration Issues [1]:

Recording rules that change or remove either the job or instance labels aren't supported.

The reason is that stackdriver-prometheus-sidecar uses these two well-known labels to construct a Stackdriver MonitoredResource for your Kubernetes object (it’s also answered in Integration Issues [1])
For the PR you created, I have briefly reviewed it, and I have thought about the following 2 higher-level questions for any recording rules with colons:

How should stackdriver-prometheus-sidecar support recording rules with colons in the metric name? The reason is that colons are suggested reserved for recording rules in Prometheus official document[2].
What metrics generated from Prometheus recording rules stackdriver-prometheus-sidecar should be sent to Stackdriver.

Unfortunately, I don’t have bandwidth before end of Q3 to answer the 2 questions above. I think it requires to come up with reasonable options, and analyze the pros and cons of these options.
For the issue you have here, I’d like to provide a direction to fix the code and a potential workable for recording rules if you don’t mind to try it out, though I couldn’t verify it myself before end of Q3:

Create a PR to fix targetMatch with additional test cases where:

targets has labels more than (job, instance)
recording rules preserves (job, instance)

Use recording rules without colons; and set static metadata with configuration file so stackdriver-prometheus-sidecar can look up the metadata for metrics from recording rules.

Let me know what do you think, @memory .
[1]  https://cloud.google.com/monitoring/kubernetes-engine/prometheus#prometheus_integration_issues
[2] https://prometheus.io/docs/concepts/data_model/

Okay, we're in agreement that forwarding metrics that lack instance/job labels isn't currently supported and it would require a substantial rewrite of the sidecar to support.  I'd gently suggest that given stackdriver's stratospheric per-metric cost, this feels like a limitation that should be addressed at some point: "just forward the raw metrics and do the aggregation on the stackdriver side" is a strategy with in many cases a large number of dollar signs attached to it.  But this is obviously a larger issue than this one particular bug and isn't going to get solved in the short term.
For the nearer-term issues, I'll try to update my PR with the test cases you suggested and update the documentation with a suggested configuration for renaming and properly labelling recorded metrics.

@memory have you checked out the Counter Aggregator feature? It was added for your use case.

@jkohen I did, but unfortunately (a) the raw metrics in question here were histograms, not gauges, and (b) I needed to group them by the labels that I intended to preserve (ie: for every deployment, aggregate the 50/95/99th histogram_quantile for request latency across all of the deployment's pods without having to manually specify each deployment name in the sidecar config); there did not seem to be a way to do either of those things with the counter aggregator although if I missed it I'd be happy to hear it.

@memory it works for counters; I don't think it'll give you the right result for gauges and histograms. It should in principle work for histograms, with some additional work. We need to prioritize that with other work we have on our plates. Once we're ready, we'll make sure it covers your use case. Thanks for the feedback and sorry we don't have a better answer right now.

@StevenYCChou so, some progress:

If I attempt to forward a recorded metric that aggregates away the job/instance labels, it still fails with the same cache lookup errors. :(
If I include the job/instance labels (suboptimal, but one thing at a time), we get somewhere:

level=debug ts=2019-08-29T15:10:10.164Z caller=client.go:170
  component=storage
  msg="Partial failure calling CreateTimeSeries"
  err="rpc error:
    code = InvalidArgument
    desc = Errors during metric descriptor creation:
    {(metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile95_rate300s, error: The metric type is invalid.),
     (metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile99_rate300s, error: The metric type is invalid.)}."

level=warn ts=2019-08-29T15:10:10.164Z caller=queue_manager.go:546
  component=queue_manager
  msg="Unrecoverable error sending samples to remote storage"
  err="rpc error:
    code = InvalidArgument
    desc = Errors during metric descriptor creation:
    {(metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile95_rate300s, error: The metric type is invalid.),
     (metric: external.googleapis.com/prometheus/dst_service:response_latency_ms:histogram_quantile99_rate300s, error: The metric type is invalid.)}."

The api documentation for metricDescriptors only notes that the type field is a string and doesn't suggest that there are any length/content limitations on it?

@memory Just curious - Based on the recording rules you provided, do you try to get quantileX from a Prometheus Histogram?
Prometheus Histogram type will be transformed into Stackdriver Distribution type of timeseries, and you can aggregate by Xth percentile and group by your labels as well.
If you have any other use case beyond the observation I have above, please let me know too.

@StevenYCChou yeah, I'm using recording rules to get a quantile from the prometheus histogram and forwarding it to stackdriver as a simple metric, e.g.:
      - record: recorded_svc_latency_ms_p50_30s
        expr: histogram_quantile(0.50, sum(rate(response_latency_ms_bucket{namespace="default", direction="outbound", dst_service=~".+"}[30s])) by (le, dst_service, instance, job))

Unfortunately, simply forwarding the histogram directly isn't possible for us and is how we got into this situation in the first place. The source histogram has more labels than the current stackdriver limit, so we were attempting to use recording rules to drop/aggregate across labels that we didn't need in stackdriver.

Not sure if this is related, but we also got some metrics that are not properly forwarded to StackDriver. While metrics collected from the services directly are properly propagated, metrics collected from the Pushgateway do not seem to work.
When setting the log level to debug we also got the target not found message for the exact metrics that are missing in StackDriver.
level=debug ts=2019-12-18T16:57:43.193Z caller=series_cache.go:354 component="Prometheus reader" msg="target not found" labels="{__name__=\"core_assortment_articles_total_count\",job=\"core-assortment\"}"

Versions in use are:

stackdriver-prometheus-sidecar 0.6.4
prometheus v2.13.1

I am not sure if this fits into the same issue discussed here, if that is not the case let me know and I will create a separate issue.

I am also getting same issue.
i have record_rule as below
    - record: free_memory_percent
      expr: 100 - 100 * (node_memory_MemFree_bytes / node_memory_MemTotal_bytes)

but unable to see on stackdriver. somehow stackdriver side car not sending this metric.
recorded rule able to see on prometheus metric dashboard.
Please help me here.

It's been about 4 months since the last update to this issue, and nearly a year since it was first opened.  I'm currently tottering along with the workaround from https://github.com/Stackdriver/stackdriver-prometheus-sidecar/pull/159 but it would be nice to have some indication of whether and when this is likely to be fixed upstream.

Gentle ping, one quarter later.  Obviously the pandemic has derailed many a timetable; I hope everyone involved here is healthy and safe and keeping it that way should be everyone's #1 priority.
Somewhere deep below that on the list of priorities: is this on anyone's radar? :)

I have the same problem when trying to send data to local Kubernetes.
Everything is complicated by the fact that I cannot find any similar complete examples in the documentation. Please help if someone has something similar.
We are not talking about custom metrics, but about the metrics of the Kubernetes.
global:
  scrape_interval:     10s
  evaluation_interval: 15s

scrape_configs:
  - job_name: 'k8s_metrics'
    scrape_interval: 10s

    honor_labels: true
    metrics_path: '/federate'

    params:
      'match[]':
        - '{__name__="kube_deployment_labels"}'

    static_configs:
      - targets:
        - 'xxxxxx'

My docker-compose
version: '3.3'

services:
  volumes-provisioner:
    image: hasnat/volumes-provisioner
    environment:
      PROVISION_DIRECTORIES: "65534:65534:0755:/prometheus/data"
    volumes:
      - ./prom_data_k8s:/prometheus/data

  prometheus:
    image: prom/prometheus:v2.19.3
    restart: always
    depends_on:
      - volumes-provisioner
    ports:
    - 9080:9090
    command:
    - --config.file=/etc/prometheus/prometheus.yml
    - --storage.tsdb.min-block-duration=15m
    - --storage.tsdb.retention=24h
    volumes:
    - ./prometheus-old-k8s.yml:/etc/prometheus/prometheus.yml:ro
    - ./prom_data_k8s:/prometheus/data

  sidecar:
    image: gcr.io/stackdriver-prometheus/stackdriver-prometheus-sidecar:0.8.0
    restart: always
    depends_on:
      - volumes-provisioner
      - prometheus
    command:
      - '--prometheus.wal-directory=/prometheus/data/wal'
      - '--prometheus.api-address=http://prometheus:9090/'
      - '--stackdriver.project-id=xxxxx'
      - '--stackdriver.generic.location=k8s_cluster'
      - '--stackdriver.generic.namespace="test-namespace"'
      - '--stackdriver.kubernetes.location=global'
      - '--stackdriver.kubernetes.cluster-name=oldk8s'
      - '--log.level=debug'
    volumes:
      - ./prom_data_k8s:/prometheus/data
      - ./monitoring-metric-uploader.json:/etc/monitoring-metric-uploader.json:ro
    environment:
      - GOOGLE_APPLICATION_CREDENTIALS=/etc/monitoring-metric-uploader.json

level=debug ts=2020-08-05T08:57:16.693Z caller=series_cache.go:354 component="Prometheus reader" msg="target not found" labels="{__name__=\"kube_deployment_labels\",deployment=\"sitepreview-service\",endpoint=\"https-main\",instance=\"<IP_ADDRESS>:8443\",job=\"kube-state-metrics\",label_app=\"sitepreview\",label_chart=\"api-service-chart-0.1.0\",label_heritage=\"Tiller\",label_release=\"sitepreview\",namespace=\"apis\",pod=\"kube-state-metrics-5456d85ddc-j86ld\",service=\"kube-state-metrics\"}"

💥 I found! https://www.padok.fr/en/blog/monitoring-stackdriver-kubernetes

@StevenYCChou  it's approaching a year since the last substantial update on this issue.  Is this expected to be addressed any time soon?

This has also been a bit of a thorn in our side too, would love some idea of getting something like @memory's change into upstream? :)

Hi @qingling128 and welcome to this extremely fun ticket! :) Let me know if I can offer any other details here.

Is there any news on this?

Coming back to this after a long absence, I think several of us (myself very much included) got stuck in a rabbit hole when there is a much simpler solution available for most cases.
With only the code change to targets/cache.go in #159 (and none of the other changes around a magic prefix for recorded , and for at least prometheus recording rules that produce GAUGE and CUMULATIVE metrics, it is possible for the sidecar to forward them with only configuration changes.
For example a recording rule like:
    groups:
    - name: service_aggregations
      rules:
      - record: job:response_total:sum
        expr: sum(response_total{namespace="default", direction="inbound"}) by (app, instance, job, classification, status_code)

Forwarding job:response_total_sum to stackdriver works as long as you use metric_renames to rename the metric to not have colons, and use static_metadata to (if necessary) fix up the type and value:
      metric_renames:
      - from: job:response_total:sum
        to: recorded_job_response_total_cumulative
      static_metadata:
      - metric: recorded_job_response_total_cumulative
        type: counter
        value_type: double
        help: aggregated response totals to each service by job and response code

I have not yet tested to see if this would work for prometheus histograms / stackdriver distributions.
It's a little unclear to me if this was something that would have worked all along and we were all too deep in the weeds to see it, or if something in between the 0.5.0 and 0.8.1 releases made this possible.  In any case I think the main need at this point is the fix to targets/cache and some explicit documentation around the case of recorded metrics: https://github.com/Stackdriver/stackdriver-prometheus-sidecar/pull/266

Coming back to this after a long absence, I think several of us (myself very much included) got stuck in a rabbit hole when there is a much simpler solution available for most cases.
With only the code change to targets/cache.go in #159 (and none of the other changes around a magic prefix for recorded , and for at least prometheus recording rules that produce GAUGE and CUMULATIVE metrics, it is possible for the sidecar to forward them with only configuration changes.
For example a recording rule like:
    groups:
    - name: service_aggregations
      rules:
      - record: job:response_total:sum
        expr: sum(response_total{namespace="default", direction="inbound"}) by (app, instance, job, classification, status_code)

Forwarding job:response_total_sum to stackdriver works as long as you use metric_renames to rename the metric to not have colons, and use static_metadata to (if necessary) fix up the type and value:
      metric_renames:
      - from: job:response_total:sum
        to: recorded_job_response_total_cumulative
      static_metadata:
      - metric: recorded_job_response_total_cumulative
        type: counter
        value_type: double
        help: aggregated response totals to each service by job and response code

I have not yet tested to see if this would work for prometheus histograms / stackdriver distributions.
It's a little unclear to me if this was something that would have worked all along and we were all too deep in the weeds to see it, or if something in between the 0.5.0 and 0.8.1 releases made this possible.  In any case I think the main need at this point is the fix to targets/cache and some explicit documentation around the case of recorded metrics: https://github.com/Stackdriver/stackdriver-prometheus-sidecar/pull/266

(As a small followup: exporting recorded histograms does not seem to currently be possible.  The current code assumes that all recorded metrics are gauges, and attempting to pin the value/value_type as counter/distribution produces an error that distribution is not a supported value type.)

(As a small followup: exporting recorded histograms does not seem to currently be possible.  The current code assumes that all recorded metrics are gauges, and attempting to pin the value/value_type as counter/distribution produces an error that distribution is not a supported value type.)

With the merge of #266 I believe this bug can, at long last, be closed.

#266 has been merged.


peek message not support partitioned topic

Describe the bug
A clear and concise description of what the bug is.
pulsar-admin topics create-partitioned-topic
pulsar-admin topics peek-messages -s sub topic-name-partitioned-0

Throw exception:
Peek messages on a partitioned topic is not allowed

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

pulsar-admin topics create-partitioned-topic
pulsar-admin topics peek-messages -s sub topic-name-partitioned-0

Throw exception:
Peek messages on a partitioned topic is not allowed

Expected behavior
Support peek message for partitioned topic
Remove this check https://github.com/apache/pulsar/blob/983266d480f77543a29a74ac1970280abd9f804b/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/PersistentTopicsBase.java#L2094
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]

Additional context
Add any other context about the problem here.

I will fix it, please assign this issue to me.

@hangc0276 assigned

I have reconfirmed that this command is OK. Now I close the issue
pulsar-admin topics peek-messages -s sub topic-name-partitioned-0


IE 10 fix

Fixed "SCRIPT5045: Assignment to read-only properties is not allowed in strict mode" error in IE 10

hi, thank you for your input. can you please also share about,
elem.style.property = null vs
elem.style.property = '' vs
elem.style.removeProperty('property')
?
example from the code,
https://github.com/ahmednooor/halkaBox.js/blob/master/src/halkaBox.js#L516
thanks.

UPDATE:
elem.style.property = null is buggy.
elem.style.property = "" will be used instead.
i will add the above mentioned change in a couple days.
for now, merging this request.
thanks for the fix.


Crash: Unsupported Swift architecture - sumup 0.7.0

Environment

Flutter channel: stable
Flutter version: 3.10.2
Sumup version: 0.7.0
Xcode version: 14.3.1
macOS version: 13.3.1

Terminal Output Error:
Swift Compiler Error (Xcode): Unsupported Swift architecture
/Users/lcsvcn/Documents/GitHub/super_totem/build/ios/Debug-iphonesimulator/XCFrameworkIntermediates/SumUpSDK/SumUpSDK.framework/Headers/SumUp-GeneratedHeader-Swift.h:262:1

Swift Compiler Error (Xcode): Could not build Objective-C module 'SumUpSDK'
/Users/lcsvcn/.pub-cache/hosted/pub.dev/sumup-0.7.0/ios/Classes/SwiftSumupPlugin.swift:1:7

Could not build the application for the simulator.
Error launching application on iPad Pro (11-inch) (4th generation).

I already tried this post and also to clean all cache (for flutter and podfile). The issue persisted.
Important Note: When I downgrade to sumup version 0.6.1, it works fine. Seems like an issue with version 0.7.0.

Hi @lcsvcn, sorry for the late response. Is this still an issue?

same problem for me work on physical device but not on simulator. I can't update the package with version 0.7.0

Hi @deveasyshop, maybe this is the issue?

I have the same issue

I found the workaround that fixes the issue for me you can use this in Podfile
post_install do |installer|
  installer.pods_project.build_configurations.each do |config|
    config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
  end
end


Publish to Microsoft Store

https://www.microsoft.com/en-us/store/collections/edgeextensions

API is not available atm.


Cleanup platform.js code

Codecov Report

Merging #1346 into master will decrease coverage by 0.48%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1346      +/-   ##
==========================================
- Coverage   93.13%   92.64%   -0.49%
==========================================
  Files          47       47
  Lines        4820     4896      +76
  Branches      537      846     +309
==========================================
+ Hits         4489     4536      +47
- Misses        331      332       +1
- Partials        0       28      +28

Impacted Files
Coverage Δ

browser/services/platform.js
98.14% <100%> (-0.36%)
:arrow_down:

browser/model/devstudio-autoinstall.js
97.29% <0%> (-2.71%)
:arrow_down:

browser/services/request.js
97.61% <0%> (-2.39%)
:arrow_down:

browser/pages/install/controller.js
91.86% <0%> (-1.75%)
:arrow_down:

browser/model/helpers/downloader.js
95.53% <0%> (-1.68%)
:arrow_down:

browser/model/che.js
95% <0%> (-1.62%)
:arrow_down:

browser/pages/account/controller.js
98.61% <0%> (-1.39%)
:arrow_down:

browser/model/cdk.js
97.6% <0%> (-1.16%)
:arrow_down:

browser/model/devstudio-p2-zip.js
64.4% <0%> (-1.12%)
:arrow_down:

browser/model/installable-item.js
92.28% <0%> (-1.03%)
:arrow_down:

... and 26 more

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 e76956f...fabfdad. Read the comment docs.

test this


add views folder with main index bio

We have added a views folder with layout folder -> main.handlebars inside. We've also added index and bio views.

@jock-dalby @lisa-seeto
Good job!


When to stop Training?

I am trying to fine-tune LORA. I am unable to understand when training stops and which is the best checkpoint.
I can see in hyper-parameters we are setting max_iters = 50000. Does it mean training will always happen for 50000 iterations? How will I select the best checkpoint? How can I be sure that training is comleted?

it will save every save_interval and if you sync eval_interval = save_interval, you can select the checkpoint with the lowest loss.
eval_interval = 1000
save_interval = 1000

It would be really nice to enable reporting to wandb to make this a bit easier but you can also add some simple logic to rename the lowest loss checkpoint "best" or something.

(Reposting my answer from Discord)
50k iterations with a micro_batch_size of 4 (like in the lora.py script) means that the training will see 200k samples.
Stanford Alpaca contains 52k instruction pairs, so that means you'll go over your examples 4 times (aka 4 epochs). The original Stanford Alpaca authors ran 3 epochs for LLaMA 7B and 5 epochs for LLaMA 13B, so that is a rather safe choice.
As a rule of thumb, you want to leverage your dataset by doing multiple passes, but avoid overfitting it, so running for a few epochs is reasonable.
At the end of the day though, you will want to run evaluations as in https://github.com/EleutherAI/lm-evaluation-harness and see how your model performs on one or more benchmarks of interest. That's the best way to assess when you should stop.
To run the harness on lit-llama, you can run it from this branch https://github.com/Lightning-AI/lm-evaluation-harness/tree/lit-llama
I have a better solution in the works that doesn't force you to use this fork, but I haven't had the time to wrap it up yet.


JBEHAVE-1530 Restore JDK 8 compatibility

In master https://github.com/jbehave/jbehave-core/commit/2f6b5db31edbd1460ad5a8908802ae09114a60fb


Build error and runtime errors with Java pack fixed

The artifact name built was helloworld.jar but the copy command was referring to different name hence build is failing:
Step 6/8 : COPY --from=BUILD /usr/src/app/target/app.jar /opt/app.jar
lstat usr/src/app/target/app.jar: no such file or directory

Fixed by copying helloworld.jar instead of app.jar

Since the jar being deployed was a thin jar without dependencies, it was not able to find Spark classes and thus failing:

2017-07-03T10:23:49.370518638Z Exception in thread "main" java.lang.BootstrapMethodError: java.lang.NoClassDefFoundError: spark/Request
2017-07-03T10:23:49.373134679Z 	at helloworld.Hello.main(Hello.java:7)
2017-07-03T10:23:49.373163432Z Caused by: java.lang.NoClassDefFoundError: spark/Request
2017-07-03T10:23:49.373167578Z 	... 1 more
2017-07-03T10:23:49.373170484Z Caused by: java.lang.ClassNotFoundException: spark.Request
2017-07-03T10:23:49.373173097Z 	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
2017-07-03T10:23:49.373175661Z 	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
2017-07-03T10:23:49.373178321Z 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
2017-07-03T10:23:49.373180932Z 	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
2017-07-03T10:23:49.373183512Z 	... 1 more

Fixed by using the "-with-dependency" jar

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

otherwise LGTM.

Codecov Report

Merging #216 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #216   +/-   ##
=======================================
  Coverage   32.94%   32.94%
=======================================
  Files          18       18
  Lines        1108     1108
=======================================
  Hits          365      365
  Misses        694      694
  Partials       49       49

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 63a6da1...4cd5ad1. Read the comment docs.

@bacongobbler Fixed.


Glyphs scalling is not accurate

Those are panes separators in tmux, as you can see after mentioned change vertical line is wider than horizontal one, which is in my opinion looks really bad, if you have direct comparison. Mintty does it right. The same font in both cases.
Before commit 70867df077e03a8ac5d4b230e28d64f90e08045e:

After commit 70867df077e03a8ac5d4b230e28d64f90e08045e:

Mintty:

It's not really wider, though, it's just brighter because we're not splitting it on the half pixel... that seems to be consistent with the traditional CP437 rendering of those glyphs (where the verticals are thicker than the horizontals)

I took closeup look and counted pixels it looks like it is 1px wider, but well, as you said it is also brighter, I though it looks brighter because it is wider and you say otherwise :)
Anyhow I didn't notice similar rendering in other terminal emulators. I mean I immediately noticed that something is wrong here. If you google tmux screenshots vertical and horizontal separators looks the same almost everywhere. I use the same font (Hack) in mintty and gnome terminal and looks fine.

Sorry - I didn't see the extra pixel because I trusted my browser's upscaler to use nearest-neighbor :smile:
So, I'm going to resolve this one by design and file a followup work item. Before I do that, though, a bit of backstory and an explanation for why it is the way it is.
In the old terrible days, we could be relatively sure (cf. the traditional console's GDI renderer) that our font sizes were in absolute pixels. This left no possibility of fractional sizes for ascent, descent, or line spacing (as computed by the text layout engine.)
When we moved to using DirectWrite, we started to avail ourselves of the ability to do differential rendering and using an API that lets us only present changed regions (and do really fast scrolling by asking the graphics card to move the region for us.)
Those APIs only work on full pixel boundaries. Unfortunately, fonts are weird and when you try to render them in a nice grid sometimes you need to bump them around by fractional pixels. This didn't jive with the presentation API.
Terminal rounds a glyph's box size up to the nearest pixel, and adjusts the font size inside it for best fit. Doing this broke box/line drawing characters completely: they had gaps in the vertical direction, or gaps in the horizontal direction, because they no longer fit the cells we gave them. Whoops.
#5743 introduced a change that measures the four edges of a box or line glyph for any given font and scales it just a bit to touch the pixel-locked bounds we want to render it in. The result is consistent with the font's style, but stretched out a little bit in certain dimensions.
The tradeoff we made was to have contiguous box-drawing glyphs at the cost of having perfectly-sized box-drawing glyphs.

Other terminal emulators do interesting things:

Gnome-terminal uses little 5x5 bitmaps and stretches them to fill the entire cell.

This results in pixel perfect boxes and shading.

Konsole (KDE) uses line-drawing primitives at the graphics layer to mimic line drawing, and rect-filling primitives with opacity to mimic box drawing.

This also results in pixel-perfect boxes and cool blended shading glyphs.

We chose not to do these things for v1.0 because we learned that certain fonts (monofur is a good one) have their own unique styles for line glyphs (and box fills, but that's beside the point) that we wanted to preserve.
For post-v1, I'm willing to accept that this might not be the best way to handle it. I've filed a followup workitem, #5897, to encourage us to investigate different ways to handle these glyphs.

(The body of commit https://github.com/microsoft/terminal/commit/70867df077e03a8ac5d4b230e28d64f90e08045e has more details about why we chose to do it this way. :smile:)

Thank you for comprehensive answer and creating followup work item 👍


Can't fetch environment document, 404 and 403

I am using Server-Side Environment Keys. The updateEnvironment() operation in Java SDK is throwing an error thus I can’t request flags. I have started calling this operation while debugging the issue with getIdentityFlags().
Flagsmith: error when getting flags. Request: https://edge.api.flagsmith.com/api/v1/environment-document/, Response: Response{protocol=h2, code=404, message=, url=https://edge.api.flagsmith.com/api/v1/environment-document/} body[]

A similar issue happens when I try to fetch identity flags, this time it is 403.
2023-12-15 10:22:39.967 [pool-7-thread-2] ERROR com.flagsmith.FlagsmithClient traceId:  spanId:
                 - Flagsmith: error when getting flags. Request: https://edge.api.flagsmith.com/api/v1/environment-document/, Response: Response{protocol=h2, code=403, message=, url=https://edge.api.flagsmith.com/api/v1/environment-document/} body[]
2023-12-15 10:22:40.172 [Thread-2] ERROR com.flagsmith.FlagsmithClient traceId:  spanId:
                 - Flagsmith: Execution failed on Environment loading.
java.util.concurrent.ExecutionException: com.flagsmith.exceptions.FlagsmithApiError
        at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
        at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2022)
        at com.flagsmith.FlagsmithApiWrapper.getEnvironment(FlagsmithApiWrapper.java:255)
        at com.flagsmith.FlagsmithClient.updateEnvironment(FlagsmithClient.java:55)
        at com.flagsmith.threads.PollingManager$1.run(PollingManager.java:41)
Caused by: com.flagsmith.exceptions.FlagsmithApiError: null
        at com.flagsmith.threads.RequestProcessor.lambda$executeAsync$0(RequestProcessor.java:112)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
2023-12-15 10:22:40.173 [Thread-2] ERROR com.flagsmith.FlagsmithClient traceId:  spanId:
                 - Flagsmith: Unable to update environment from API. No environment configured - using defaultHandler if configured.

with the initialization code
FlagsmithConfig flagsmithConfig = FlagsmithConfig.newBuilder()
                                                 .withLocalEvaluation(true)
                                                 .withEnableAnalytics(true)
                                                 .withEnvironmentRefreshIntervalSeconds(15)
                                                 // .baseUri()
                                                 .build();

return FlagsmithClient.newBuilder()
                      .setApiKey(featureFlagConfig.getString("apiKey"))
                      .withConfiguration(flagsmithConfig)
                      .enableLogging(logger)
                      .enableLogging(FlagsmithLoggerLevel.ERROR)
                      .build();

Version: 7.1.1
JVM: OpenJDK Runtime Environment Corretto-<IP_ADDRESS>.1 (build 11.0.17+8-LTS)

Hi @Dogacel, it sounds like your environment key is not correct. Can you confirm that you are correctly setting the environment key to a server key obtained from the Flagsmith dashboard?
Can you also please confirm if you are using the Flagsmith hosted SaaS product, or self hosting?

Hi @Dogacel, it sounds like your environment key is not correct. Can you confirm that you are correctly setting the environment key to a server key obtained from the Flagsmith dashboard?
Can you also please confirm if you are using the Flagsmith hosted SaaS product, or self hosting?

I am using the hosted SaaS product.
I think my key is correct because if I set the key to be something random, I get this:
com.flagsmith.exceptions.FlagsmithRuntimeError: In order to use local evaluation, please generate a server key in the environment settings page.

But I don't see that with the key.

Hi @Dogacel, were you able to find the cause of this? I'm unable to reproduce and I agree with Matt thinking that this just looks like your server-side API key is not set correctly in your application.
Keep in mind that this error:

In order to use local evaluation, please generate a server key in the environment settings page

only checks that the serverside key starts with ser., to avoid mixing up server-side and client-side environment keys. If you are still getting the same error by setting a key like ser.my_wrong_key, then most likely the key you were trying with is incorrect.
I'll close this issue to clean up old threads, but if you do find anything I'm happy to continue the discussion here.

@rolodato Hi, I think there were two causes:

Incorrect server key.
Server not being behind an https.

I agree that this issue can be closed.


Support custom filename

What problem are you trying to solve with this feature?
My project uses the filename formatting /src/posts/2024/2024-04-11-post-title.md
Describe the solution you'd like
An option that can be set to create the filename based on the date and title properties
Describe alternatives you've considered
Currently creating the post as normal and changing the filename with the date :)

@flamedfury I see how this would be helpful considering the configuration of your site. However, I think this runs the risk of complicating things a bit. I could enable adding the date to the file name in the format you use, but then someone else would want it in a different format.
I guess I could add an option to enable it then let users set the date format mm, mmm, dd, yy, yyyy.  There's likely a library out there that would make this easy.
I'm not in a rush do implement something like this. I'll give it some thought and may get to it. Keep in mind that you can always implement it and submit a PR.
Why don't you make a proposal for how  you would like to see this work configuration-wise so we can start a dialog around it.


gptimer cache  error (IDFGH-10809)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-WROOM
Power Supply used.
USB
What is the expected behavior?
gptimer should work with CONFIG_GPTIMER_ISR_IRAM_SAFE=y
What is the actual behavior?
gptimer causes crash when configured with CONFIG_GPTIMER_ISR_IRAM_SAFE=y
Steps to reproduce.
#include <stdio.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "freertos/queue.h"
#include "driver/gptimer.h"
#include "esp_log.h"
#include "nvs_flash.h"

/*
 This example will generate an cache error when:
.  - build with release 5.1 or current master 53ff7d43db. (5.0 works ok)
  - configured with CONFIG_GPTIMER_ISR_IRAM_SAFE=y

 1) cd esp-idf/examples/peripherals/timer_group
 2) cp -r gptimers gptimers bug_gptimers
 3) cd bug_gptimers
 4) replace file main/gptimers_example_main.c with this file
 5) configure with CONFIG_GPTIMER_ISR_IRAM_SAFE=y
 6) build and flash

*/

/*
 Serial terminal monitor output:

I (32) boot: ESP-IDF v5.2-dev-1962-g53ff7d43db 2nd stage bootloader
I (32) boot: compile time Aug  5 2023 13:54:19
I (34) boot: Multicore bootloader
I (38) boot: chip revision: v1.0
I (42) boot.esp32: SPI Speed      : 40MHz
I (47) boot.esp32: SPI Mode       : DIO
I (51) boot.esp32: SPI Flash Size : 2MB
I (56) boot: Enabling RNG early entropy source...
I (61) boot: Partition Table:
I (65) boot: ## Label            Usage          Type ST Offset   Length
I (72) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (80) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (87) boot:  2 factory          factory app      00 00 00010000 00100000
I (95) boot: End of partition table
I (99) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=0a7c0h ( 42944) map
I (123) esp_image: segment 1: paddr=0001a7e8 vaddr=3ffb0000 size=02128h (  8488) load
I (126) esp_image: segment 2: paddr=0001c918 vaddr=40080000 size=03700h ( 14080) load
I (134) esp_image: segment 3: paddr=00020020 vaddr=400d0020 size=172c0h ( 94912) map
I (171) esp_image: segment 4: paddr=000372e8 vaddr=40083700 size=090f8h ( 37112) load
I (193) boot: Loaded app from partition at offset 0x10000
I (193) boot: Disabling RNG early entropy source...
I (205) cpu_start: Multicore app
I (205) cpu_start: Pro cpu up.
I (205) cpu_start: Starting app cpu, entry point is 0x40081064
0x40081064: call_start_cpu1 at /home/bertw/Android/esp-idf-master/components/esp_system/port/cpu_start.c:170

I (0) cpu_start: App cpu up.
I (223) cpu_start: Pro cpu start user code
I (223) cpu_start: cpu freq: 160000000 Hz
I (223) cpu_start: Application information:
I (228) cpu_start: Project name:     gptimer
I (233) cpu_start: App version:      v5.2-dev-1962-g53ff7d43db
I (239) cpu_start: Compile time:     Aug  5 2023 13:54:15
I (245) cpu_start: ELF file SHA256:  9bdf80011005707f...
I (251) cpu_start: ESP-IDF:          v5.2-dev-1962-g53ff7d43db
I (258) cpu_start: Min chip rev:     v0.0
I (263) cpu_start: Max chip rev:     v3.99
I (267) cpu_start: Chip rev:         v1.0
I (272) heap_init: Initializing. RAM available for dynamic allocation:
I (280) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (285) heap_init: At 3FFB29E0 len 0002D620 (181 KiB): DRAM
I (292) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (298) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (304) heap_init: At 4008C7F8 len 00013808 (78 KiB): IRAM
I (312) spi_flash: detected chip: generic
I (315) spi_flash: flash io: dio
W (319) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (333) app_start: Starting scheduler on CPU0
I (337) app_start: Starting scheduler on CPU1
I (337) main_task: Started on CPU0
I (347) main_task: Calling app_main()
D (347) gptimer: new group (0) @0x3ffaffe8
D (347) gptimer: new gptimer (0,0) at 0x3ffb5af8, resolution=1000000Hz
Guru Meditation Error: Core  0 panic'ed (Cache disabled but cached memory region accessed).

Setting breakpoint at 0x00000000 and returning...

 */

// empty isr callback
IRAM_ATTR static bool  my_on_alarm_isr(gptimer_handle_t timer, const gptimer_alarm_event_data_t *edata, void *user_ctx) {
  return false;
}

static void my_isr_init() {
  gptimer_handle_t gptimer = NULL;
  gptimer_config_t timer_config = { .clk_src = GPTIMER_CLK_SRC_DEFAULT,
                                    .direction = GPTIMER_COUNT_UP,
                                    .resolution_hz = 1 * 1000 * 1000, // 1MHz, 1 tick = 1us
      };
  gptimer_alarm_config_t config = { .alarm_count = 200, .reload_count = 0, .flags = { .auto_reload_on_alarm = 1 } };
  gptimer_event_callbacks_t cbs = { .on_alarm = my_on_alarm_isr };  // the callback is empty and returns false

  ESP_ERROR_CHECK(gptimer_new_timer(&timer_config, &gptimer));
  ESP_ERROR_CHECK(gptimer_set_alarm_action(gptimer, &config));
  ESP_ERROR_CHECK(gptimer_register_event_callbacks(gptimer, &cbs, NULL));
  ESP_ERROR_CHECK(gptimer_enable(gptimer));
  ESP_ERROR_CHECK(gptimer_start(gptimer));
}

void app_main(void)
{
  my_isr_init();   // create and start gptimer with empty callback
  nvs_flash_init();  // This triggers the cache error for some reason.
}

Debug Logs.
No response
More Information.
No response

@zwiebert Confirmed! Thanks for reporting this issue and tried different branches. Why the issue was only on 5.1 and master is that, in this https://github.com/espressif/esp-idf/commit/995b89fbb61c68a079e8a5abecb2063689b6be7c we introduced a HAL API timer_hal_capture_and_get_counter_value which is not placed in the IRAM when only CONFIG_GPTIMER_ISR_IRAM_SAFE is turned on. Currently you can workaround the issue by also enabling the CONFIG_GPTIMER_CTRL_FUNC_IN_IRAM. We will fix that ASAP and backport to 5.1 release branch.


Adds test for SMTP with RFC2231

ie attachment filename split over multiple sections
see https://redmine.openinfosecfoundation.org/issues/4386

Thanks! Merged as a part of #596

Oh I guess there should have been a min-version: 7 for this one


[Components: Data Display] ProgressBar

Visualization of task progress.
e2e tests required.

QA Notes
import {ProgressBar} from @haulmont/react-antd;
Must have prop percent
example:
<ProgressBar percent={50} />
e2e test:
test-pup/example-react-app/progress-bar.test.js


Datagen

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing as this changes are not required


Make this the default vim indent plugin

https://github.com/vim/vim/issues/483#event-706918725

@memeplex Sorry, too late my reply.
I saw the issue.
But, this plugin expects the user to have Python and autopep8 installed.
Therefore, it is inappropriate as vim's standard indent plugin.
(It is bad that standard plugin does not work if there is no specific library)
For that purpose,  vim-python-pep8-indent is more appropriate.
thx

Was there ever an attempt to bring vim-python-pep8-indent into mainline vim?


⚠ Turnos 24x7 has degraded performance

In ac2023a, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1039 ms

Resolved: Turnos 24x7 performance has improved in 8cbdb5b.


feat: added ability to use ollama running remotely

Refs: #171
What does this PR do?
Adds ability to use remote ollama server
Fixes # (issue)
Requirement/Documentation

If there is a requirement document, please, share it here.

Type of change

[x] New feature (non-breaking change which adds functionality)

Mandatory Tasks

[x] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected. Make sure before submmiting this PR you run tests with evaluate.py

@joshbickett would someone have a moment to look at this? It's a really small PR that could be useful to anyone running ollama on remote server.

pls merge this its good

@slapglif @mjspeck I'm re prioritizing this project. I'll try to take a look at this soon


dev: Cargo Update

We have a vulnerability in our dependency graph: https://github.com/keep-starknet-strange/beerus/security/dependabot
We need to run: cargo update and test all functionality to remove

Hello there, may I take this one?

I can't access the link because a 404 error appears.
I ran the cargo update command and the dependencies in the Cargo.lock file were updated to the latest version.
Then, I ran the tests and all of them passed successfully.
Is there anything else I need to do?

I was hoping that would fix the dependency issue, but it looks like it's something else pinned in our helios dependency(chrono -> time):

https://github.com/keep-starknet-strange/beerus/security/dependabot
https://github.com/keep-starknet-strange/beerus/blob/ce16f268e5df4613dc5a487837f7f316e69ad160/Cargo.lock#L797

Do you know another way to remove the nested dependency pin?

appears to have mysteriously resolved itself


Tool use not working for AnthropicChatModel

Hi @jackmpcollins,
It looks like tool use is currently broken for the AnthropicChatModel:
from magentic import prompt, ParallelFunctionCall
from magentic.chat_model.anthropic_chat_model import AnthropicChatModel

def get_weather(city: str) -> str:
    return f"The weather in {city} is 20°C."

@prompt(
    "What is the weather in Cape Town?",
    functions=[get_weather],
    model=AnthropicChatModel(
        model="claude-3-opus",
        temperature=0.2,
    )
)
def _llm() -> str | ParallelFunctionCall: ...

_llm()

Produces the following error:
File ~/miniforge3/envs/copilot-opus/lib/python3.11/site-packages/anthropic/_base_client.py:921, in SyncAPIClient.request(self, cast_to, options, remaining_retries, stream, stream_cls)
    912 def request(
    913     self,
    914     cast_to: Type[ResponseT],
   (...)
    919     stream_cls: type[_StreamT] | None = None,
    920 ) -> ResponseT | _StreamT:
--> 921     return self._request(
    922         cast_to=cast_to,
    923         options=options,
    924         stream=stream,
    925         stream_cls=stream_cls,
    926         remaining_retries=remaining_retries,
    927     )

File ~/miniforge3/envs/copilot-opus/lib/python3.11/site-packages/anthropic/_base_client.py:1019, in SyncAPIClient._request(self, cast_to, options, remaining_retries, stream, stream_cls)
   1016         err.response.read()
   1018     log.debug("Re-raising status error")
-> 1019     raise self._make_status_error_from_response(err.response) from None
   1021 return self._process_response(
   1022     cast_to=cast_to,
   1023     options=options,
   (...)
   1026     stream_cls=stream_cls,
   1027 )

BadRequestError: Error code: 400 - {'type': 'error', 'error': {'type': 'invalid_request_error', 'message': "'claude-3-opus' does not support tool use via API fields."}}

I'm wondering if this breakage doesn't have to do with the public beta launch of tool use for Claude 3 models on 15 May 2024?
That being said, I see magentic uses the same anthropic library call used in the example above. So I'm not quite sure what the issue could be.
I'm on the latest version of anthropic, 0.26.1 and magentic at 0.24.0.

Closing. There was a typo in the model specification (I didn't use the fully-qualified model name: claude-3-opus-20240229). Bizarrely, the Anthropic API throws the tool use error first rather than a model error.


Remove unused icons

Remove info, warning and error icons

@dafortin We use the error icon in our app; are there different icons we should be using, or plans for a more generalized way of presenting an icon with a message?

@gkoy I believe the intention was just to use the ones from core, but that's just assuming that they're the same.  If the notification icons are unique (I believe the warning is and info may be as well) then they should stay.
Error is the same between both projects I believe

It's worth noting that nowhere within this addon are the icons in its own icon pack referenced. There's no reference to the frost-notifier pack in any of the frost-icon instances used in the templates in this addon.

Also @gknoy I didn't see any reference to the frost-notifier icon pack in your app either. So you'll probably be unaffected if we remove it from here.


Versioning and referencing of our specs

@mimayer @cboisson, @joleroi, all - How should we version the specs here and obtain a stable reference URL?
The IRF specs are making good progress, I think we can finish this soon.
(days for a first version, then weeks to have some discussion with others)
@joleroi suggested that we do something similar to the OGIP specs, where a HDU_DOC keyword is used to refer to the specification:
https://heasarc.gsfc.nasa.gov/docs/heasarc/ofwg/docs/ofwg_recomm/r8.html
I'm a bit hesitant to use the https://github.com/gammapy/gamma-astro-data-formats or http://gamma-astro-data-formats.readthedocs.org/ in HDU_DOC in FITS files, because the reference might not be stable enough (e.g. if we decide to move the repo or HTML page hosting for some reason).
Thus my suggestion would be that in early January we tag the repo with a 1.0 version and put it up on https://zenodo.org/ . Then we have a DOI, which is the most stable reference one can get as far as I know.
@zblz @giacomov @woodmd - We'll have to discuss whether it makes sense to keep the astro model specs (and other things I'd like specified, like input / output to sensitivity computations) in the same repo, or whether we split things out into separate repos where development / versioning can occur at a pace that's appropriate for each spec.
We don't have to decide these things now, I suggest we take some time until January to see how the different specs evolve and keep them all here for now.
But I wanted to start the discussion early and hear what you all think about versioning and referencing of our specs.

This was discussed in a HESS FITS telcon today, in preparation of the CTA DATA meeting next week.
We decided that it's useful  0.1 version (git tag and DOI from Zenodo), so I'll do this on Friday:
https://github.com/gammapy/gamma-astro-data-formats/milestones/0.1
Everyone - Please help get the specs and narrative text into shape for the parts you are about!

I've tagged the current master version because this is used in HESS, but there will be significant changes in the coming days. I do not plan to upload this version to Zenodo.
See
https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/releases/tag/v0.1
This tag is picked up by readthedocs:
http://readthedocs.org/projects/gamma-astro-data-formats/versions/
But the version "v0.1" is not displayed correctly yet.
This needs to be implemented in the Sphinx build, e.g. by hand or using https://github.com/warner/python-versioneer .

Moving all  issues from the 0.1 milestone to 0.2 now.

We are preparing the first HESS FITS test data release, and want a stable and archived version of the specs.
We had v0.1 in April 2016 as a very preliminary version:
https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/releases/tag/v0.1
I propose to make the next version in ~ 1 week, and to call it v0.2.
The reasoning for this is that it's still very preliminary and many things are not agreed, so v1.0 IMO sends the wrong message.
@mackaiver (from #33) and all - Is this OK for you, or would you prefer to call it v1.0
The other question is what edits are needed before the release. I see a few points at
https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/milestone/2
but as far as I know, none of those are real issues and they could all be deferred to the the v0.3 milestone.
Is that correct, or is there something that should really be fixed or improved before v0.2?
Is anyone able to help out here, and do the technical work to get proper versioning of the spec, i.e. to git tag, and propagate the version to the docs page, and introduce a changelog, and eventually submit to Zenodo to get a DOI and have it archived. (see comments above, it needs someone that knows how to work with Sphinx and Readthedocs and git a bit to do this)
If I don't hear back here, I plan to do this and make a v0.2 release on Tuesday, May 8.

@mackaiver (from #33) and all - Is this OK for you, or would you prefer to call it v1.0

Ok by me.

👍

All (especially @TarekHC @cboisson @lmohrmann @tony32lin ) - if you have time, please have a final look at the spec: https://gamma-astro-data-formats.readthedocs.io/
Adding proper versioning is the only task left before tagging v0.2 and uploading it to Zenodo. I plan to do that on Monday afternoon.
This will be the basis / reference for the HESS data release and joint Crab paper, so ideally we'd make it a nice and polished document. So if you notice some mistake or would like to change or improve something, please open an issue or PR before Monday noon.

Again, good to go from my side!

At the moment we have version 0.2 in conf.py as well as several specs pages listing HDUVERS.
This is good enough for now, I'm tagging v0.2 now.
In the future, if this project continues, probably something better should be set up, to be clear and automate the process of updating version numbers semi-automatically. In Python projects things like
https://pypi.org/project/bumpversion/ or https://github.com/warner/python-versioneer are used, and they could be used here as well to get dev version numbers and automatic version handling.
So I'll keep this issue open for now, but remove it from the v0.2 milestone.


execute.run doesn't accept TagInstance<'functions'>

It should accept function tags in addition to functions.

Duplicate of #172


Runtime Config Types misses Public Runtime Config

Environment

Operating System: Windows_NT
Node Version:     v16.19.0
Nuxt Version:     3.7.1
CLI Version:      3.7.3
Nitro Version:    2.6.2
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, css, build, modules, googleFonts, hooks, imports, piniaPersistedstate, runtimeConfig, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction

Create a Nuxt App nuxi@latest init my-app
Create a .env with NUXT_PUBLIC_BACKEND_URL="https://localhost:44333"
In the nuxt.config add

runtimeConfig: {
    public: {
      BACKEND_URL: 'https://localhost:1337',
    },
  },

run nuxt prepare
create a component with that script section

<script setup lang="ts">
const runtimeConfig = useRuntimeConfig()
const baseUrl = runtimeConfig.public.BACKEND_URL
</script>

The IDE should not recognize runtimeConfig.public.BACKEND_URL

Describe the bug
After running nuxt prepare all types also the runtime config types should be generated in .nuxt

https://nuxt.com/docs/guide/going-further/runtime-config#manually-typing-runtime-config

In my case, this was true
(.nuxt/types/schema.d.ts)

Interface RuntimeConfig

interface RuntimeConfig {
   app: {
      baseURL: string,
      buildAssetsDir: string,
      cdnURL: string,
   },
   QSD_QSDID: string,
  }

Interface PublicRuntimeConfig

interface PublicRuntimeConfig {
   QSD_BACKEND_URL: string,
   QSD_FRONTEND_URL: string,
   QSD_UPDATE_UNSEEN_TICKETS_INTERVAL_IN_SECONDS: number,
   QSD_KUNDE_ICON_PATH: string,
   QSD_PRODUKT_ICON_PATH: string,
   i18n: {
      experimental: {
         jsTsFormatResource: boolean,
      },
      baseUrl: string,
   },
   persistedState: {
      storage: string,
      debug: boolean,
      cookieOptions: {
         sameSite: string,
         expires: any,
         maxAge: number,
         secure: boolean,
      },
   },
  }

The problem I see, is that the RuntimeConfig Interface does not have a property public: PublicRuntimeConfig;
which is given in<EMAIL_ADDRESS>As I add public: PublicRuntimeConfig;  to the (.nuxt/types/schema.d.ts ) RuntimeConfig interface
interface RuntimeConfig {
   app: {
      baseURL: string,

      buildAssetsDir: string,

      cdnURL: string,
   },
   public: PublicRuntimeConfig; // <<<< this should solve the bug
   QSD_QSDID: string,
  }

the IDE recognize all public ENV and shows their type and autocompletes
Additional context
No response
Logs
No response

Can't repro this anymore.

I am still facing this exact issue in Jetbrains Webstorm.
const useRuntimeConfig: typeof import('../../node_modules/nuxt/dist/app/nuxt')['useRuntimeConfig'] points to the nuxt.d.ts of the node_modules.
export declare function useRuntimeConfig(_event?: H3Event<EventHandlerRequest>): RuntimeConfig;
And that points to<EMAIL_ADDRESS>I will try to find out if I can identify why both files are targeted.. but I think it is not really a issue I am able to fix.


Should probably have a Contributing.md

Find a common one that amounts to 'don't be a jerk'

closed by #27


x/tools/cmd/present: add support for sub bullets

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.11 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jerrin/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/jerrin/gocode"
GOPROXY=""
GORACE=""
GOROOT="/home/jerrin/go-go1.11"
GOTMPDIR=""
GOTOOLDIR="/home/jerrin/go-go1.11/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build014264932=/tmp/go-build -gno-record-gcc-switches"
Go present tool does not currently support sub bullets. This proposal is to add a new syntax to support sub bullets. Lines prefixed with '-- ' will be displayed as a sub bullet.
For example, the following code block produces the slide shown below.
* Title

- bullet 1
-- sub bullet 1.1
- bullet 2
-- sub bullet 2.1
-- sub bullet 2.2

CC @adg


Image resolver

Motivation
I need to transform images, which are in rich text editor. Eg to set max width and type of image by adding query string "w=1200&auto=format"
Proposed solution
Mayme the best solution is to add resolver for images
Additional context
All of supported transformations: https://developer.kenticocloud.com/v1/reference#image-transformation

Implemented in 1.4.0. See https://github.com/Kentico/kentico-cloud-js/blob/master/packages/delivery/DOCS.md#image-processing-inside-rich-text-fields

Thank you


setup-uv on a Windows self-hosted runner can't extract zipped release

After download of the released zip-file on a Windows 11 self-hosted runner (pristine, just factory-reset, long paths enabled), the action fails with the following error
$ C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "$ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.FileSystem } catch { } ; if ((Get-Command -Name Expand-Archive -Module Microsoft.PowerShell.Archive -ErrorAction Ignore)) { Expand-Archive -LiteralPath 'C:\actions-runner\runner-2\_work\_temp\3cf9961a-8f55-4e9d-aa9c-3674d81c98d2' -DestinationPath 'C:\actions-runner\runner-2\_work\_temp\4b8494f9-6c44-4cba-a655-61706ac00844' -Force } else {[System.IO.Compression.ZipFile]::ExtractToDirectory('C:\actions-runner\runner-2\_work\_temp\3cf9961a-8f55-4e9d-aa9c-3674d81c98d2', 'C:\actions-runner\runner-2\_work\_temp\4b8494f9-6c44-4cba-a655-61706ac00844', $true) }"
Expand-Archive :  is not a supported archive file format. .zip is the only supported archive file format.
At line:1 char:210
+ ...  Ignore)) { Expand-Archive -LiteralPath 'C:\actions-runner\runner-2\_ ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:String) [Expand-Archive], IOException
    + FullyQualifiedErrorId : NotSupportedArchiveFileExtension,Expand-Archive

I think the relevant piece is
Expand-Archive -LiteralPath 'C:\actions-runner\runner-2\_work\_temp\3cf9961a-8f55-4e9d-aa9c-3674d81c98d2' -DestinationPath 'C:\actions-runner\runner-2\_work\_temp\4b8494f9-6c44-4cba-a655-61706ac00844' -Force

which, as the error suggests, is trying to expand a file without any extensions.

Thank you for reporting this issue. I will implement a fix.
For the meantime a workaround seems to be updating the Powershell version on your self hosted runner: https://github.com/actions/setup-go/issues/241#issuecomment-1363985056

Thanks for the hint! For reference, turns out my system came with the following PowerShell version:
Name                           Value
----                           -----
PSVersion                      5.1.22621.4249
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.4249
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Installing powershell 7.4 (via winget, but I guess any source works) and rebooting worked!

Can you please test with PowerShell 5.1 and
- name: Install the latest version of uv
  uses: astral-sh/setup-uv@zip-extension

I do not have a custom Windows runner at hand

It indeed works :)
$ C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "$ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.FileSystem } catch { } ; if ((Get-Command -Name Expand-Archive -Module Microsoft.PowerShell.Archive -ErrorAction Ignore)) { Expand-Archive -LiteralPath 'uv-x86_64-pc-windows-msvc.zip' -DestinationPath 'C:\actions-runner\runner-2\_work\_temp\47d952a6-49aa-43f7-a4b6-badc695ca20a' -Force } else {[System.IO.Compression.ZipFile]::ExtractToDirectory('uv-x86_64-pc-windows-msvc.zip', 'C:\actions-runner\runner-2\_work\_temp\47d952a6-49aa-43f7-a4b6-badc695ca20a', $true) }"
Added C:\actions-runner\runner-2\_work\_tool\uv\0.4.30\x86_64 to the path

Nice thank you for testing


Added Leetcode-cn to Chrome Extension

The English version:
Thank you very much for the author's plug-in. Could you add the url of the Chinese interface in Chrom Extension to facilitate the use of users in China
https://leetcode-cn.com/*
The original:
非常感谢作者的插件, 可否在chrom Extension中增加中国区界面的网址 , 方便中国区用户使用

leetcode-cn.com organizes many contests which are not on leetcode.com. As of now, we have covered leetcode.com's contests only. Also, the front-end of leetcode-cn.com is different than leetcode.com, so for enabling browser-extension on leetcode-cn.com,  we have to write additional code for the extension.

leetcode-cn.com organizes many contests which are not on leetcode.com. As of now, we have covered leetcode.com's contests only. Also, the front-end of leetcode-cn.com is different than leetcode.com, so for enabling browser-extension on leetcode-cn.com, we have to write additional code for the extension.

ok, thans for reply


Update webhooks.ts

@MarcosNicolau ,
Currently, there are not types for the nfm_reply on the Webhooks.
Nfm_reply are the replies sent from a user response to a flow.
This is specified here.
Just adding them.

Excellent, thanks!!
Only one thing, could you change the commit message following the conventional commit standard? This is just to make the semantic release ci aware of the changes and trigger a release automatically.


Add community engineer pages

Description
Adding community engineer pages for use as CTA after talks

Closes #https://github.com/pulumi/devrel-team/issues/855


Add /favicon.ico and links

Create favicon.ico using https://favicon.io/favicon-generator
Settings:
Font: Ubuntu
Style: Bold
Text Color: D9D9D9
Background Color: 18181B

It's not fancy, but it should at least prevent this blank file icon which makes the site look broken

Fixes: #371

I think someone would need to verify that it actually works by generating or using the guide/docs locally. I only added the files but didn't teset


管理画面でサーバーログを表示

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Done


Propagate extension failures to user-space (refs #171)

As discussed in #171 I have removed the actor-system stopping behavior, modernized the ConstructrExtension by switching to the new style of extension implementation and added the ability to hook up event handlers to ConstructR failures, for which I added a couple of tests as well. In the context of this work I also removed the deprecated ActorDSL stuff from the multi-jvm test and replaced it with regular actor creation code, as per akka guidelines.

Thanks a lot! I will take a look soon, but not before next week. Apologies for the delay.

No problem at all, we will proceed our experimentation with a local version of our own for the time being. I will also proceed with dealing with the rest of the issues and making the corresponding pull requests so that, hopefully, when you get the time you will have the chance to review them all at once. Cheers!


Live Server is not working with laragon and WAMP

I have configured live server chrome extension but it still lists the content of my project's workspace,
this a screenshot of the extension configuration:

You should not visit the "Live Server Address". Instead visit the "Actual Server Address" and it should work.

@jenstornell Thank you so much

When I right click on a file and Open with Live Server it opens a new chrome page with the live server address and /whatever html file I've just opened. Also using WAMP. Oddly enough the page loads under that but it won't update once I've saved, still have to do it manually.


feat: make error clonable

Overview
This makes candid::Error clonable, which makes it easier for downstream clients to also make their Error types cloneable.
I've made a related PR for agent-rs.
Considered Solutions
I can also work around by using Arc<T> in downstream clients.
Considerations
This shouldn't have any impact on security or performance. Anyone that was interacting directly with the Custom variant may have a breaking change since it is wrapped in an Arc<T> now.

I agree that making a major bump just for this feature is not worth the effort, so I'm fine with leaving this to sleep and in the meantime I will just to_string() downstream.


Khal hasn't started the wiki for the language. -12 points

Get on this Khal. We are waiting.

https://en.wikipedia.org/wiki/Dice_(programming_language)


Dependency package xml2js has a new version available

We have identified a dependency on version 0.4.23 of xml2js. A new version (0.5.0) is available for upgrade.
Following are the steps to upgrade package dependency.

Understand the breaking changes between the version being used and the version you want to upgrade to.

Identify all packages that take a dependency on this package.

Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.

Run rush update to ensure the new version is pulled in.

Make relevant changes to absorb the breaking changes.

Repeat steps 3 to 5 for each of the packages that have a dependency on this package.

Also referenced by #25499 and resolved by #25502


How to set output path?

this script create Scene.js in root of my project

no idea how that would work, a second arg maybe?

@MaxmaxmaximusAWS By default command to write to a new file, if you have admin rights, then it is
echo original_item > target_file.txt

//to see the contents just cat it or nano

cat target_file.txt

You can create  a bash script to do so and chmod it.

Going off of what @algorithmhash said. For what it's worth, here is a pipeline script I made that might help you out.... You'll need to modify it a bit to fit your needs, but it's pretty straightforward. It handles draco-compressing, gltf-jsx, and component output directory.
Usage: ./scripts/pipeline.rb model-name.gltf
https://github.com/Code47X/tanman.dev/blob/master/scripts/pipeline.rb

Going off of what @algorithmhash said. For what it's worth, here is a pipeline script I made that might help you out.... You'll need to modify it a bit to fit your needs, but it's pretty straightforward. It handles draco-compressing, gltf-jsx, and component output directory.
Usage: ./scripts/pipeline.rb model-name.gltf
https://github.com/Code47X/tanman.dev/blob/master/scripts/pipeline.rb

@Code47X looks like that repo is private?
It would be nice to have an --outputDirectory option that could be passed to choose where files are output to.
For example, I have public/scenes that has all of my gltf scenes (i.e. public/scenes/scene1.gltf, public/scenes/scene2.gltf) and want to export them all to src/components/scenes (i.e. src/components/scenes/scene1.tsx, src/components/scenes/scene2.tsx)

@TranquilMarmot Whoops - here is a gist of the pipeline script I mentioned: https://gist.github.com/Code47X/ad0bbbf8ff0aefd5536e9431e66d5f0d
I do agree though, an output directory option would be a nice addition.


Bring changes from BertrandBev 1.1.0

Recently in BertrandBev a few changes were added. We should bring those changes too:

[ ] 43
[ ] 58
[ ] 60
[ ] 62
[ ] 64

Done in https://github.com/akvelon/flutter-code-editor/pull/124


Add front-end testing of page loading, redirections, and html

Functional tests in place, run with Selenium.


Fix link to CONTRIBUTING.md

Tiny typo/link fix to Troubleshooting documentation. No functionality changed, just documentation.
Description
Previous link 404s with https://github.com/github/linguist/blob/master/docs/CONTRIBUTING.md
This corrects it to the intended https://github.com/github/linguist/blob/master/CONTRIBUTING.md

Thanks @Alhadis , I noticed the [issues] and [new-issues] after I raised the PR but wasn't 100% sure if they were supposed to be active links. I looked for GitHub markdown shortcuts to the actions; full URLs are a sensible answer :)
I have made those changes, and one other: changing 'above' to 'here' on the single file link back to README.md.
Thanks for the context with the original documentation split PR !

Great work! We'll merge this once @lildude has given his 👍 of approval.


Style refactor

Smaller chunks of sass files and removing unused styles and found.

For ref, the only bits that are changing are:
 -#modal {
 -  @include sans-font-bold;
 -  color: $gray_light;
 -  width: 400px;
 -  height: 400px;
 -  position: fixed;
 -  z-index: 9999;
 -  border: 4px solid $gray;
 -  padding: 20px 40px;
 -
 -  ul {
 -    padding: 0;
 -    margin-top: 0;
 -
 -    li {
 -      @include sans-font-regular;
 -      margin-top: 0.75em;
 -    }
 -  }
 -}
 -
 -#modal-overlay {
 -  position: absolute;
 -  top: 0;
 -  z-index: 9990;
 -  background-color: $white;
 -}
 -
 -#x {
 -  position: absolute;
 -  right: 20px;
 -  top: 20px;
 -  cursor: pointer;
 -  line-height: 0;
 -  padding: 9px 5px 10px 5px;
 -}
 -
 -#modal-intro,
 -#sig {
 -  margin-top: 20px;
 -}
 -
 -#modal-intro {
 -  font-size: 1.7em;
 -}

There is a bit more of moving things around into separate files with a few more imports but the above is correct.

Thanks @micahtaylor !


Separate EnvFile Configuration between Run Configurations

Expected:

Run Configuration (RC) A: Load app.env.dev
Run Configuration B: Load app.env.test

Problem: The EnvFile configuration is a global config, so if I load app.env.dev in RC A, RC B will load app.env.dev the next time unless I update EnvFile config.

EnvFile is configured per run configuration.

@ashald

EnvFile is configured per run configuration.

We expected this, but it doesn't work as expected. That's why I created this issue. However, I guess you didn't get it.

@ashald
Although this issue is from your plugin and I didn't use PyCharm, however, you said you tested this issue on PyCharm. So I made a record to reproduce this issue on PyCharm.
Steps to reproduce

Install PyCharm.
Install the plugin EnvFile and restart PyCharm.
Create a simple Python program containing 3 files:

main.py:
import os

def print_env():
    print(os.environ['PY_ENV'])

if __name__ == '__main__':
    print_env()

app.env.dev:
PY_ENV=dev

app.env.test:
PY_ENV=test

Create 2 run configurations as recorded in this video [dev] main and [test] main.

https://user-images.githubusercontent.com/6688235/203485140-1ce8dfb7-de62-4fa5-8207-a60b24b8d155.mov
As you can see in the above video:

Note
[dev] main
[test] main

Before updating
app.env.dev (00:05)
app.env.dev (00:06)

After updating
app.env.test (00:20)
app.env.test (00:16)

This means that the env file path is always the same for all run configurations.
Test Environment Information (if necessary)

macOS 12.6.1.
PyCharm 2022.2.3 (Professional Edition).
Python 3.10.8 (Pipenv) (as recorded in the video).
EnvFile 3.4.1.

Finally, I don't know how you reproduced this issue, but I doubt that after recording this video.


[QUESTION] Learning Pathways iconography

WEB PART NOT LOADING: If you are getting the error: "Microsoft 365 learning pathways has a configuration issue. Ask your administrator for assistance". Please review the Diagnosing Pre-Check guidance before submitting your bug.

Submit your question
What is the context of your question

[ ] Installation
[x] Learning Pathways Content
[ ] SharePoint Success Content
[ ] Administration
[ ] Custom Content
[ ] Viewer Web Part

What is your question
Is the only way to change iconography associated with a playlist through the user interface for custom playlists? As the source of the OOTB icons appears to be from GitHub, do you know if they are available for download? If so, where can they be downloaded from?

Provide related screen-shots to help us understand your question

Hello @dwindeler - That is correct to the best of my knowledge. I do not know if the OOTB icons are available for download separately.


Some visualization problem only for Jammu and Kashmir

Some minor visual problem only for J&K state.

I check out this bug. Below 382px (width) this glitch occurs.

Also happens for Andaman and Nicobar islands

Also happens for Andaman and Nicobar islands

Above made PR will fix this issue for all states.

Seems to be fixed


[electron] Automate releaseDate retrieval

This will also prevent having alters for unreleased versions, such as in https://github.com/endoflife-date/endoflife.date/pull/5324.

Expected diff:
diff --git i/products/electron.md w/products/electron.md
index 4aaedef0..4ee50500 100644
--- i/products/electron.md
+++ w/products/electron.md
@@ -30,6 +30,7 @@ auto:
         releaseCycle:
           column: "Electron"
           regex: '^(?P<value>\d+)\.0\.0$'
+        releaseDate: "Stable"
         eol: "EOL"

 releases:
@@ -106,7 +107,7 @@ releases:
     nodeVersion: "18.12"

 -   releaseCycle: "22"
-    releaseDate: 2022-11-30
+    releaseDate: 2022-11-29
     eol: 2023-10-10
     latest: "22.3.27"
     latestReleaseDate: 2023-10-09
@@ -242,7 +243,7 @@ releases:
     nodeVersion: "12.14.0"

 -   releaseCycle: "5"
-    releaseDate: 2019-04-24
+    releaseDate: 2019-04-23
     eol: 2020-02-04


Add History of Cats Section

Add History of Cats Section
Just add the section with a placeholder page under the section.

Hi, can I work adding the cat's history section?

Hi, can I work adding the cat's history section?

Hi, feel free to add some content with some references. Anything is welcomed! Thanks!


ionic2, angularfire2 and firebase working combination?

Hi team,
Does somebody knows if there is a working ionic2, angularfire2 and firebase version combination?
I'm using:
ionic 2.1.0-beta.2
<EMAIL_ADDRESS><EMAIL_ADDRESS>I'm having these unmet peer dependencies:

Thanks!!

You could either wait for Ionic 2 Beta 12 which already using Angular 2 release and Typescript 2 which should be out in a couple of days.
Or you could use angularfire2 beta2 which is still using angular2 RC4.

Hello @Opelor , thanks for opening an issue with us! This will be fixed once beta.12 is out (extremely soon (; ) as it is running on Angular 2 final!


Fix test breaks in (sometimes skipped) integration tests

Coverage remained the same at 16.615% when pulling 65ddc649ec26e77d9c8ac6269ad784ed864d7443 on dt:fixtests into 34e77f13982c24e7858a40f441df8f38051b4a92 on finagle:master.

looks like this has since been duplicated by @jeremyrsmith in #20


Add Versionable.detach() for creating a copy of a model. See #68

Name suggested by @brki in #68.
I have not yet tested this with ForeignKey or ManyToManyField relations.

This was merged in v1.4.5


"@azure/service-bus"

Package Name: @azure/ms-rest-nodeauth && @azure/service-bus
Package Version: 3.0.3 && 1.1.5
Operating system: Windows
[x] nodejs

version: 10.16.1

[x] typescript

version: 3.7.4

Describe the bug
ApplicationTokenCredential generated using loginWithServicePrincipalSecret() function from @azure/ms-rest-nodeauth is cannot be passed to ServiceBusClient.createFromAadTokenCredentials() because of a type mismatch.
To Reproduce
Steps to reproduce the behavior:

Create an instance of ApplicationTokenCredentials using loginWithServicePrincipalSecret()
Try to create an instance of ServiceBusClient using that credential

Expected behavior
Should be able to create an instance of ServiceBusClient using credential without a compile time error.

Here is the full error: Argument of type 'ApplicationTokenCredentials' is not assignable to parameter of type 'ApplicationTokenCredentials | UserTokenCredentials | DeviceTokenCredentials | MSITokenCredentials'.
Type 'import("c:/.../.../.../node_modules/@azure/ms-rest-nodeauth/dist/lib/credentials/applicationTokenCredentials").ApplicationTokenCredentials' is not assignable to type 'import("c:/.../.../.../node_modules/@azure/amqp-common/node_modules/@azure/ms-rest-nodeauth/dist/lib/credentials/applicationTokenCredentials").ApplicationTokenCredentials'.
Property 'getTokenFromCache' is protected but type 'ApplicationTokenCredentialsBase' is not a class derived from 'ApplicationTokenCredentials'.
Downgrading to v2.0.5 of @azure/ms-rest-nodeauth produces the same error.

@daviwil can correct me on this, but I'm not sure that ms-rest-nodeauth is intended to be compatible with @azure/service-bus.
Are you not able to use @azure/identity?

@xirzec this is the documentation comment on ServiceBusClient.createFromAadTokenCredentials() :
"
Creates a ServiceBusClient for the Service Bus Namespace represented by the given host using the TokenCredentials generated using the @azure/ms-rest-nodeauth library.
...
@param credentials — The Token credentials generated by using the @azure/ms-rest-nodeauth library. It can be one of the following:
"

Oh, of course, you're using the 1.x version of service-bus. Sorry, I was looking at the version 7 preview.

Passing the credential as any manages to instantiate a client, but when I attempt to send a message to ServiceBus I get Invalid TokenAudience error. I wonder the first issue is causing the second?

'import("c:/.../.../.../node_modules/@azure/amqp-common/node_modules/@azure/ms-rest-nodeauth/dist/lib/credentials/applicationTokenCredentials"

It seems that amqp-common is depending on a different version of ms-rest-nodeauth than you are.
This seems to be because service-bus 1.1.5 depends on amqp-common 1.0.0-preview11 which incorrectly lists ms-rest-nodeauth as a dependency rather than a dev dependency.
The version it's dragging in is pretty old too: @azure/ms-rest-nodeauth: ^0.9.2
You could try depending on that version of ms-rest-nodeauth to see if that unblocks you?

@xirzec Downgrading @azure/ms-rest-nodeauth to the older version does not work because the credential generated is of type ''TokenCredentialBase"

The any trick for now is probably the right solution. Audience errors makes me think something is going wrong with your credentials. Are you specifying the tokenAudience when you call loginWithServicePrincipalSecret?
const tokenCreds = await loginWithServicePrincipalSecret(clientId, clientSecret, tenantId, {
    tokenAudience: "https://servicebus.azure.net/"
  });

Sorry for the confusion here @ysalo
This issue is actually a duplicate of #8041 which we have been working on.
We are happy to share that we just released an update to the @azure/service-bus package (
version 1.1.6) where we no longer rely on the @azure/ms-rest-nodeauth package.
This allows users to use any version of @azure/ms-rest-nodeauth directly with @azure/service-bus without TypeScript compilation errors.
Thanks for reporting!


Importing the same OPML file creates duplicate feeds

I was having issues with 500 errors with my Google Reader export. It was failing on number 4 of 24. Removed number 4 and it ran fine. After some experimentation it seemed like the combination was somehow causing it to fail.
However, after importing the same file multiple times, I now have duplicates. Be nice if there was some duplication resolution.

I'm no longer personally interested in this. Feel free to reopen (or recreate) if still interested.


how do you make an anulus that's +50, -20 degree around the direction?

Angle only produces a symmetrical pie and I'd like to represent a joint with a + and minus angle where + != minus degree

I've just added some overloads of Arc and Annulus to the 3.0.0 branch (not on UPM, tbd when I release it)
You can see how I've done it here:
https://github.com/vertxxyz/Vertx.Debugging/commit/4c2dcddc603803f8a45f22cfac4d7405e584a16e#diff-5727d04b66b54b516ed110abb20ff49bf9ec74db4a1b2535d655231f801ebce4R948
With a call from the new overloads looking like this:
https://github.com/vertxxyz/Vertx.Debugging/commit/4c2dcddc603803f8a45f22cfac4d7405e584a16e#diff-5727d04b66b54b516ed110abb20ff49bf9ec74db4a1b2535d655231f801ebce4R1020
If you're not using that branch and want to stay on UPM you can adjust the rotation and angle in a similar way.

Thanks, I'll wait for release.


Add minio deployment specifications with OpenEBS storage

What this PR does / why we need it:

Adds minio deployment specifications to the k8s/demo applications
Includes README to setup minio

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #282

Fixed the broken image links


Essemble live error

Please start putting description on what the review is about, plus link to the Github issue.


Upgrade to webpack v5

Webpack 4.46.0 depends on the outdated loader-runner which has issues with the SSL certificate https://stackoverflow.com/a/73027407/556678.


Add FinalForm example to storybook for all form inputs

Form inputs should all have examples in storybook that show how they can be used in Final Form.
Radio buttons currently do this, but examples for DateInput and Input also need to be added.
It looks as though the DateInput is not compatible in its current form.

We now have examples in #887 but they are not in the stories for each component.
I think this should come alongside the new form API in 0.10


??? it expected a socket, but it got socket, and luau is angry at me

We do not have a socket library in the Luau standard library, so I'm not sure how this could work. Could you provide more information about the environment you're working in?

Without more information about the environment you're running in we cannot provide support. I'm going to close this for now.


Fixed bug that the return type of Collection::map()  is invalid sometimes

https://github.com/hyperf/hyperf/pull/6798 重复了


Change Apache's DocumentRoot on docker run

I'm using Laravel so I need Apache to look inside /app/public , instead of /app as the entry point folder. Is there a way to do this on image bootup?

Hi Rei,
Sorry for my stupidity here, I’m not a Laravel guy, could you not just
navigate to /app? Or does it have to be at the root?
Thanks,
Matt
On Tue, 2 Jun 2020 at 19:19, Rei<EMAIL_ADDRESS>wrote:

I'm using Laravel so I need Apache to look inside /app/public , instead
of /app as the entry point folder. Is there a way to do this on image
bootup?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mattrayner/docker-lamp/issues/88, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2XGNWSU5Z3PZPJKGF7PVLRUU7BNANCNFSM4NQ62C5A
.

--
Matt Rayner
http://www.mattrayner.co.uk/

You could also pass your own apache config file in with volumes, something like:
docker run -v custom-apache.conf:/etc/apache2/sites-available/000-default.conf mattrayner/lamp:latest

Let me know if this fixes your issue :)

Hi Matt,,
Whilst that is a solid suggestion, I've found that my app can't run on PHP
7.3 or higher. It needs PHP 7.2. Is there a way to run this PHP version on
your images?
Cheers!
On Mon, 8 Jun 2020 at 22:27, Matt Rayner<EMAIL_ADDRESS>wrote:

You could also pass your own apache config file in with volumes, something
like:
docker run -v custom-apache.conf:/etc/apache2/sites-available/000-default.conf mattrayner/lamp:latest
Let me know if this fixes your issue :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mattrayner/docker-lamp/issues/88#issuecomment-640701386,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE7NG6SPRKBRGPNMOBMCRWTRVT7P5ANCNFSM4NQ62C5A
.

Hi Rei, you would need to look back at the older versions of the image to
find one that is running 7.2, I’ll take a look back and see if I can find
one :-)
On Mon, 8 Jun 2020 at 16:51, Rei<EMAIL_ADDRESS>wrote:

Hi Matt,,
Whilst that is a solid suggestion, I've found that my app can't run on PHP
7.3 or higher. It needs PHP 7.2. Is there a way to run this PHP version on
your images?
Cheers!
On Mon, 8 Jun 2020 at 22:27, Matt Rayner<EMAIL_ADDRESS>wrote:

You could also pass your own apache config file in with volumes,
something
like:
docker run -v
custom-apache.conf:/etc/apache2/sites-available/000-default.conf
mattrayner/lamp:latest
Let me know if this fixes your issue :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/mattrayner/docker-lamp/issues/88#issuecomment-640701386
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AE7NG6SPRKBRGPNMOBMCRWTRVT7P5ANCNFSM4NQ62C5A
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mattrayner/docker-lamp/issues/88#issuecomment-640715006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2XGNXTD2PA5KHADHX3YSTRVUCIZANCNFSM4NQ62C5A
.

--
Matt Rayner
http://www.mattrayner.co.uk/

It looks like 6.2 was available here:
https://github.com/mattrayner/docker-lamp/commit/ad2479d539b9308f18e6977ad3ddc8365542de0c#diff-04c6e90faac2675aa89e2176d2eec7d8
And that looks like it was version 0.4.0 but I didn’t have tagged images
back then so the earliest is 0.5.0 which is 7.3 :-/
I’m not sure I can help with a 7.2 image as it is non-trivial to get a
working image which is not running the latest version
On Mon, 8 Jun 2020 at 17:05, Matthew Rayner<EMAIL_ADDRESS>wrote:

Hi Rei, you would need to look back at the older versions of the image to
find one that is running 7.2, I’ll take a look back and see if I can find
one :-)
On Mon, 8 Jun 2020 at 16:51, Rei<EMAIL_ADDRESS>wrote:

Hi Matt,,
Whilst that is a solid suggestion, I've found that my app can't run on PHP
7.3 or higher. It needs PHP 7.2. Is there a way to run this PHP version on
your images?
Cheers!
On Mon, 8 Jun 2020 at 22:27, Matt Rayner<EMAIL_ADDRESS>wrote:

You could also pass your own apache config file in with volumes,
something
like:
docker run -v
custom-apache.conf:/etc/apache2/sites-available/000-default.conf
mattrayner/lamp:latest
Let me know if this fixes your issue :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/mattrayner/docker-lamp/issues/88#issuecomment-640701386
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AE7NG6SPRKBRGPNMOBMCRWTRVT7P5ANCNFSM4NQ62C5A
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mattrayner/docker-lamp/issues/88#issuecomment-640715006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2XGNXTD2PA5KHADHX3YSTRVUCIZANCNFSM4NQ62C5A
.

--
Matt Rayner
http://www.mattrayner.co.uk/

--
Matt Rayner
http://www.mattrayner.co.uk/

@rei-gun I'm going to close this off for now, please let me know if there is anything further I can do to help
Matt


Toolbar

Refactored exportSubmit to use hooks
Renamed dates util and FilterToolbar
Refactored dashboard to use hooks
Refactored overview to use hooks
Cleaned up details property type
Refactored export modal to use hooks
Added usePrevious hook
Fixed category options
Refactored dataToolbar to use hooks
Added custom useStateCallback hook

Codecov Report

Merging #151 (1ff5e48) into main (565f712) will increase coverage by 0.11%.
The diff coverage is 0.00%.

:exclamation: Current head 1ff5e48 differs from pull request most recent head cadd939. Consider uploading reports for the commit cadd939 to get more accurate results

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #151      +/-   ##
========================================
+ Coverage   6.73%   6.84%   +0.11%
========================================
  Files         41      41
  Lines       1471    1446      -25
  Branches     232     218      -14
========================================
  Hits          99      99
+ Misses      1372    1347      -25

Impacted Files
Coverage Δ

src/routes/components/data-toolbar/DataToolbar.tsx
0.00% <0.00%> (ø)

src/routes/components/export/ExportModal.tsx
0.00% <0.00%> (ø)

src/routes/components/export/ExportSubmit.tsx
0.00% <0.00%> (ø)

src/routes/details/Details.tsx
0.00% <0.00%> (ø)

src/routes/details/FilterToolbar.tsx
0.00% <0.00%> (ø)

src/routes/overview/Overview.tsx
0.00% <0.00%> (ø)

...routes/overview/components/dashboard/Dashboard.tsx
0.00% <0.00%> (ø)

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 565f712...cadd939. Read the comment docs.


⚠ Bofrost.fr has degraded performance

In 9476812, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 946 ms

Resolved: Bofrost.fr performance has improved in d4f4bf9.


Doesn't seem to remove the text

Thanks for your feedback! I'll look into it.

Its working as of 1.2.2

I confirm v1.2.2 fix installation issue.


Duplicate H1s Titled 'Azure Service client library for JavaScript - Version 3.0.1'

The following pages in Docs are all using the same H1 title heading 'Azure Service client library for JavaScript - Version 3.0.1'. First level headings must be unique within a docset.
https://github.com/MicrosoftDocs/azure-docs-sdk-node/blob/main/docs-ref-services/latest/arm-marketplaceordering-readme.md (13,1)
https://github.com/MicrosoftDocs/azure-docs-sdk-node/blob/main/docs-ref-services/latest/arm-powerbidedicated-readme.md (11,1)
https://github.com/MicrosoftDocs/azure-docs-sdk-node/blob/main/docs-ref-services/latest/arm-relay-readme.md (11,1)
These appear to come from: sdk/marketplaceordering/arm-marketplaceordering/README.md, sdk/powerbidedicated/arm-powerbidedicated/README.md, and sdk/relay/arm-relay/README.md.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.13536078,Marketplace Ordering:0.063470505,Docs:0.061572045'

Docs links are not working.

@sima-zhu The links in this issue should work now.

Consolidating into #22197


prepare v4.5.0

New

✨Upgraded Prices.tf (#905) - @Nicklason, @joekiller

Added

✨ an option to show bold characters (#873)
✨🔴 Add resetting item notifications (#879) - @carlosliam

Update/changes

🔄 Update bptf listings (#874, #912) - @arik123
⬆ upgrade socket.io-client module for custom pricer #918
🔎 always check for possible incorrect listing details (#877)

🔎 check for changes in currencies value too (#878)

🔥 remove graceful-fs module (6d9115b)
🔨 fix not save polldata keys if disable notify (#880)
🔎 check banned status only from rep.tf (others as backup) (#887)

✨🔎 an option to check for Marketplace.tf banned status (#881)

🚧 add a failsafe on issue #882 (#895)

Fixes

🩹 possible patch for missing existing items (#872)
🐛 fix unable to counter offer with only keys (#876) - @Preport
🐛 fix bot not playing game after doing other than accepting an offer (#907)
🐛 Fixing minor issues with newlines & Rate limiting (#909) - @brysondev

I am finalizing this, but this still has a problem when creating listings on backpack.tf.
The queue thing in the current @tf2autobot/bptf-listings module is currently still will cause a rate limit if you have thousands of items in your pricelist, and I am not sure where to edit tbh.

Ideally if a rate limit is hit there's some throttle that grows over time. That would probably be wherever the API response is processed. I

Ideally if a rate limit is hit there's some throttle that grows over time. That would probably be wherever the API response is processed.

Yeah true. I guess I will try to fix it in the next update since Nicklason already shut down pricing on the older prices.tf api