CSV columns breaking @metadata fields

The Issue
I have experienced a bug with metadata fields assigned by csv columns array
The prooblem with the logstash-filter-csv (2.1.1) plugin was noticed after upgrading to logstash 2.2.0. I have updated our filter to use metadata fields for working fields to prevent the need for mutate { remove => {} }'s.
In the following configuration example, we're parsing pipe delimited syslog messages and assigning nested and metadata fields.
The Config
filter {
   # Example Log Entry
   #2016-02-09T00:00:22.149813+10:00|kern|debug|kernel|redacted-host|redacted-ip|kernel:| IPTABLES-REJECT: IN=em1 OUT= MAC=redacted SRC=redacted DST=redacted LEN=76 TOS=0x00 PREC=0x00 TTL=58 ID=53364 PROTO=UDP SPT=1024 DPT=50953 LEN=56
    csv {
        separator => "|"
        columns   => [ "[@metadata][timestamp]", "[syslog][facility]", "[syslog][severity]", "[syslog][programname]", "host", "[syslog][address]", "[syslog][tag]", "[@metadata][syslogmsg]" ]
        quote_char => "Š"
    }
    date {
        #2015-09-09T15:16:32.563472+10:00 << This is how you save timestamps
        match => [ "[@metadata][timestamp]", "ISO8601" ]
    }
    mutate {
        replace => { "message" => "%{[@metadata][syslogmsg]}" }
    }
    mutate {
        strip => [ "[syslog][facility]", "[syslog][severity]", "[syslog][programname]", "[syslog][short-host]", "[@metadata][source][address]", "[syslog][tag]", "message" ]
        gsub => [ "[syslog][tag]", ":$", "" ]
    }
}
filter {
    grok {
        match => { "message" => "IPTABLES-REJECT: %{GREEDYDATA:[@metadata][body]}" }
        tag_on_failure => ["_iptables-message"]
    }
    kv {
        source => "[@metadata][body]"
        target => "firewall"
    }
    mutate {
        rename => {
            "[firewall][SRC]" => "[@metadata][source][address]"
            "[firewall][SPT]" => "[source][port]"
            "[firewall][DST]" => "[@metadata][destination][address]"
            "[firewall][DPT]" => "[destination][port]"
        }
    }
    if "_iptables-message" not in [tags] {
        mutate {
            remove_field => [ "message" ]
        }
    }
    mutate { add_field => [ "index", "redacted-%{service}-%{type}-%{+YYYY}" ] }
}

Output when the filter was working
Plugin Version: logstash-2.1.1 logstash-filter-csv (2.1.0)
{
  "_index": "redacted-iptables-2016",
  "_type": "iptables",
  "_id": "AVLKA22n3nWhM690Pqau",
  "_score": null,
  "_source": {
    "environment": "All",
    "host": "redacted",
    "offset": 685002,
    "path": "/data/syslog/2016/redacted/iptables-redacted-2016.02.10-redacted.log",
    "service": "usg-syslog",
    "type": "iptables",
    "@version": "1",
    "@timestamp": "2016-02-10T07:09:24.541Z",
    "syslog": {
      "facility": "kern",
      "severity": "debug",
      "programname": "kernel",
      "address": "redacted",
      "tag": "kernel"
    },
    "firewall": {
      "IN": "eno16780032",
      "OUT": "redacted",
      "LEN": "60",
      "TOS": "0x00",
      "PREC": "0x00",
      "TTL": "64",
      "ID": "26168",
      "PROTO": "TCP",
      "WINDOW": "14600",
      "RES": "0x00",
      "URGP": "0"
    },
    "source": {
      "port": "46708",
      "ipv4": "redacted",
      "network": "redacted",
      "geoip": {
        "city_name": "St Lucia",
        "continent_code": "OC",
        "country_code2": "AU",
        "country_code3": "AUS",
        "country_name": "Australia",
        "latitude": -27.4989228,
        "longitude":<PHONE_NUMBER>,
        "timezone": "Australia/Queensland",
        "real_region_name": "Queensland",
        "location": "-27.4989228,<PHONE_NUMBER>"
      }
    },
    "destination": {
      "port": "32638",
      "ipv4": "redacted",
      "network": "redacted",
      "geoip": {
        "city_name": "St Lucia",
        "continent_code": "OC",
        "country_code2": "AU",
        "country_code3": "AUS",
        "country_name": "Australia",
        "latitude": -27.4989228,
        "longitude":<PHONE_NUMBER>,
        "timezone": "Australia/Queensland",
        "real_region_name": "Queensland",
        "location": "-27.4989228,<PHONE_NUMBER>"
      }
    },
    "index": "redacted-iptables-2016"
  },
  "fields": {
    "@timestamp": [
<PHONE_NUMBER>541
    ]
  },
  "sort": [
<PHONE_NUMBER>541
  ]
}

Output after 2.1.1 broke the handling of @metadata fields
Plugin Version: logstash-2.2.0 logstash-filter-csv (2.1.1)

The message field was not replaced by the [@metadata][syslogmsg] value, but instead the string of the replace with field name
The value of the field [@metadata][timestamp] was not parsed by the date filter
The [@metadata] fields were not dropped when exiting the logstash pipeline

{
  "_index": "redacted-iptables-2016",
  "_type": "iptables",
  "_id": "AVLPKb998dOKmzwm1Pw_",
  "_score": null,
  "_source": {
    "environment": "All",
    "host": "redacted",
    "message": "%{[@metadata][syslogmsg]}",
    "offset": 3297765,
    "path": "/data/syslog/2016/redacted/iptables-scripts-2016.02.11-redacted.log",
    "service": "usg-syslog",
    "type": "iptables",
    "@version": "1",
    "@timestamp": "2016-02-11T07:09:23.954Z",
    "@metadata": {
      "timestamp": "2016-02-11T17:09:22.507945+10:00",
      "syslogmsg": " IPTABLES-REJECT: IN=eth1 OUT= MAC=redacted SRC=redacted DST=redacted LEN=52 TOS=0x00 PREC=0x00 TTL=124 ID=10860 DF PROTO=TCP SPT=63121 DPT=80 WINDOW=8192 RES=0x00 SYN URGP=0 "
    },
    "syslog": {
      "facility": "kern",
      "severity": "debug",
      "programname": "kernel",
      "address": "redacted",
      "tag": "kernel"
    },
    "tags": [
      "_iptables-message"
    ],
    "index": "redacted-iptables-2016"
  },
  "fields": {
    "@timestamp": [
<PHONE_NUMBER>954
    ]
  },
  "sort": [
<PHONE_NUMBER>954
  ]
}

The plugin logstash-filter-csv (2.1.0) installed in both logstash 2.2.0 & 2.2.1 avoids the issue, still an issue with logstash-filter-csv (2.1.1).

The plugin logstash-filter-csv (2.1.3) installed in logstash 2.3.0 still exhibits the metadata munging issues. Downgrading to logstash-filter-csv (2.1.0) still bypasses the issue. Seems like I must be the only one suffering from this problem. Maybe I should try to fix it..

I'm not familiar with ruby, but pretty sure I narrowed it down to this commit as it was the only commit between 2.1.0 and 2.1.1 of the plugin that was meaningful.
https://github.com/logstash-plugins/logstash-filter-csv/commit/1eea4e2c2e3811d22938087f1c06283c9ed10e17
Can you provide any insight @colinsurprenant? Thanks :+1:

I also experience this issue, logstash 2.3.2.  For example:

rubydebug { metadata = true }, outputs all metadata but not the ones from the CSV column
rubydebug { metadata = false }, outputs the metadata from the CSV column, but not other metadata

There's enough reports that I think we can confirm this bug.
I had a look at the commit that @berglh mentioned. This line of code is the problem:
>> @target = "hello"; @target = "[#{@target}]" if @target && @target !~ /^\[[^\[\]]+\]$/
=> "[hello]"
>> @target = "[hello]"; @target = "[#{@target}]" if @target && @target !~ /^\[[^\[\]]+\]$/
=> nil
>> @target = "[hello][world]"; @target = "[#{@target}]" if @target && @target !~ /^\[[^\[\]]+\]$/
=> "[[hello][world]]"

The problem is the regex is not quite correct in identifying valid field refs. Specifically nested references like [foo][bar] are not matched and are wrapped with [...] which causes the problem I think is being reported here.

Is anyone sorting out this fix? Downgrading to 2.1.0 isn't an option with the latest logstash.
logstash-filter-csv (= 2.1.0) java depends on
  logstash-core (< 3.0.0, >= 2.0.0.beta2) java

+1

I'll take a look at this.

Reproduced, in a way, using the sample provided in the issue description:

 test config
input {
  generator {
    message => "2016-02-09T00:00:22.149813+10:00|kern|debug|kernel|redacted-host|redacted-ip|kernel:| IPTABLES-REJECT: IN=em1 OUT= MAC=redacted SRC=redacted DST=redacted LEN=76 TOS=0x00 PREC=0x00 TTL=58 ID=53364 PROTO=UDP SPT=1024 DPT=50953 LEN=56"
    count => 1
  }
}

filter {
  csv {
    separator => "|"
      columns   => [ "[@metadata][timestamp]", "[syslog][facility]", "[syslog][severity]", "[syslog][programname]", "host", "[syslog][address]", "[syslog][tag]", "[@metadata][syslogmsg]" ]
      quote_char => "Š"
  }
  date {
    #2015-09-09T15:16:32.563472+10:00 << This is how you save timestamps
    match => [ "[@metadata][timestamp]", "ISO8601" ]
  }
  mutate {
    replace => { "message" => "%{[@metadata][syslogmsg]}" }
  }
  mutate {
    strip => [ "[syslog][facility]", "[syslog][severity]", "[syslog][programname]", "[syslog][short-host]", "[@metadata][source][address]", "[syslog][tag]", "message" ]
      gsub => [ "[syslog][tag]", ":$", "" ]
  }
}

output {
  stdout {
    codec => json_lines
  }
}

sample input:
2016-02-09T00:00:22.149813+10:00|kern|debug|kernel|redacted-host|redacted-ip|kernel:| IPTABLES-REJECT: IN=em1 OUT= MAC=redacted SRC=redacted DST=redacted LEN=76 TOS=0x00 PREC=0x00 TTL=58 ID=53364 PROTO=UDP SPT=1024 DPT=50953 LEN=56

output (pretty-printed json)
{
  "sequence": 0,
  "@timestamp": "2017-06-28T15:44:19.691Z",
  "@metadata": {
    "syslogmsg": " IPTABLES-REJECT: IN=em1 OUT= MAC=redacted SRC=redacted DST=redacted LEN=76 TOS=0x00 PREC=0x00 TTL=58 ID=53364 PROTO=UDP SPT=1024 DPT=50953 LEN=56",
    "timestamp": "2016-02-09T00:00:22.149813+10:00"
  },
  "@version": "1",
  "host": "redacted-host",
  "syslog": {
    "severity": "debug",
    "address": "redacted-ip",
    "programname": "kernel",
    "tag": "kernel",
    "facility": "kern"
  },
  "message": "%{[@metadata][syslogmsg]}"
}

Found the bug. Easy fix. Should have a pR shortly.

I had PR already but didn't write any tests for it. Thanks for looking in
to it.
On 29 Jun. 2017 8:45 am, "Jordan Sissel"<EMAIL_ADDRESS>wrote:

Found the bug. Easy fix. Should have a pR shortly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-filter-csv/issues/24#issuecomment-311813012,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL4NqtqokC6lgAx7vxFYB3aFBrqddLHLks5sItdvgaJpZM4HX9CS
.

@berglh oh I see that now. Thank you! I will fork your PR and add tests. I also found a bug in the field_ref method that has a similar scenario to the @target fix you made.

Thanks @jordansissel for working on this fix !
I'm very interested by this fix !

#52 is a patch for this.

Nice news !


Containers for 1.30.0 have Deno CLI version 1.29.4

> docker run --rm -it denoland/deno:alpine-1.30.0 /bin/sh
As shown above, found this when I was getting a type error on my testing step, due to passing a ReadableStream into Deno.writeFile (A new feature in 1.30.0)

Also on debian

Sorry for the problem. It should be fixed now.


Upload Boo logo

I'm submitting a ...
[] bug report
[x] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

I need to upload the logo of my token. It's doesn't have any, but when try to automerge, it's always fail. I already made the PR. Can you please upload manually please.

Pull Request #4529

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

user was the commiter of https://github.com/solana-labs/token-list/commit/fa67eb343bb39c03ab2e73b7b8b174f218949849
merged


'VBIB' block

Found it in ghostanim_bg_ghostanim_lod0.vmesh_c

-- Block: VBIB  Size: 1336   bytes [+0b padding]
*** Unrecognized block type 'VBIB' (Cannot find a class with a corresponding MResourceBlockType. See the list of blocks in this file above.) ***

This same some idea on the format: https://moddota.com/forums/discussion/comment/1064/#Comment_1064

Done in modelviewer branch.


Move Mac, Android build to the pipeline job

We now have linux builds running with a Jenkinsfile.  This means we can now port the mac build to the Jenkinsfile and run all supported platforms with one pipeline.
@fealebenpae @ironage
Related to #194

Looks like the Mac side was taken care of in #212.

@alebsack / @emanuelez, is adding an Android CI job something that you'd be able to tackle? Even just testing compilation for the supported architectures would be a good first step. We also have #208 tracking running the unit tests on devices.

@bdash Yeah, I have a WIP PR here: #221


Update dependency org.eclipse.jetty:jetty-server to v11

This PR contains the following updates:

Package
Type
Update
Change

org.eclipse.jetty:jetty-server (source)
compile
major
9.4.20.v20190813 -> 11.0.12

⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the logs for more information.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 11.x releases. However, if you upgrade to 11.x manually then Renovate will reenable minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


docs(machines): show examples of shutdown & live forever

:tada: This PR is included in version 0.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Dockerfile: EXPOSE REST API port 8080

As this is needed by the WebUI topology page which interacts with the OTBR REST agent on port 8080

I think you will find the rest port is 8081 not 8080 (thats how it is by default when I use macvlan)
i still like the idea of you including it as an EXPOSE

Thanks :) I've been fiddling around as I've been trying to get Traefik to forward requests so I can have everything running over a single port...


Vulnerable libraries angular JavaScript angular.js 1.5.3 SNYK-npm

AngularJS is in LTS mode
We are no longer accepting changes that are not critical bug fixes into this project.
See https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c for more detail.
i tried to publish an updated version of my android apk, but i had this error and my updated apk get rejected about vulnerable libraries angular !

JavaScript angular.js 1.5.3 SNYK-npm:angular:20171018, SNYK-npm:angular:20180202 assets/www/lib/angular-sanitize/angular-sanitize.js, assets/www/lib/ionic/js/angular/angular-animate.min.js, assets/www/lib/ionic/js/angular/angular-animate.js, assets/www/lib/angular-animate/angular-animate.min.js, assets/www/lib/angular/angular.js, assets/www/lib/angular-sanitize/angular-sanitize.min.js, assets/www/lib/angular-animate/angular-animate.js, assets/www/lib/ionic/js/angular/angular.min.js, assets/www/lib/ionic/js/angular/angular-sanitize.min.js, assets/www/lib/ionic/js/angular/angular-resource.js, assets/www/lib/ionic/js/angular/angular.js, assets/www/lib/ionic/js/angular/angular-resource.min.js, assets/www/lib/ionic/js/angular/angular-sanitize.js, assets/www/lib/angular/angular.min.js

this is the first time i had faced this kind of problem! any help please ?

I'm submitting a ...

[ ] regression from 1.7.0
[ ] security issue
[ ] issue caused by a new browser version
[ ] other

Current behavior:

Expected / new behavior:

Minimal reproduction of the problem with instructions:

AngularJS version: 1.8.x

Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView | Opera XX ]

Anything else:

You need to update AngularJS to the latest version.

and how can i do that ?

This is not the correct place to ask for programming help. You may try othe venues like Stack Overflow. You'll need to describe your situation with more details, though.

ok thanks.


EC2 - Error when passing in TagSpec with 0 tags

Closes #5210

Codecov Report

Merging #5216 (710319d) into master (67cda6d) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #5216   +/-   ##
=======================================
  Coverage   95.87%   95.87%
=======================================
  Files         688      688
  Lines       67823    67829    +6
=======================================
+ Hits        65027    65033    +6
  Misses       2796     2796

Flag
Coverage Δ

servertests
36.48% <50.00%> (-0.01%)
:arrow_down:

unittests
95.81% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/ec2/exceptions.py
97.58% <100.00%> (+0.02%)
:arrow_up:

moto/ec2/responses/_base_response.py
100.00% <100.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 67cda6d...710319d. Read the comment docs.


Coincheck article

Add an article about Coincheck

The perpetrators behind the Coincheck NEM security breach were linked to a Canadian exchange and a Japanese exchange called Zaif.
There is no evidence in the given search results to support this claim.
https://www.jcp.or.jp/akahata/aik17/2018-03-02/2018030201_03_1.html
　"Of the 523 million NEMs, the virtual currency that allegedly leaked from the virtual currency exchange operator Coincheck due to unauthorized access, at least 24 million had been transferred to Zaif, a major virtual currency exchange operator in Japan, by the end of February, this paper has learned."
Tokyo police arrested two men suspected of hacking Coincheck.
The search results indicate that the two men were arrested for acquiring and possessing stolen NEM cryptocurrency from the Coincheck hack, not for actually hacking Coincheck. Therefore, the claim is false.
The Osaka resident stands accused of transacting 24 million NEM coins and potentially accessing around 200 accounts.
There are no search results that provide evidence for or against this claim. Therefore, the verdict is false.
Both individuals were arrested under the provisions of the Punishment of Organized Crimes and Proceeds of Crime Control Act.
There is no evidence in the given search results to support or refute the claim. The search results only mention the Tokyo War Crimes Trials and the Act on Punishment of Organized Crimes and Control of Proceeds of Crime, but there is no information about specific individuals being arrested under this act in relation to the Tokyo Trials.
https://nlnews.jwbni.com/failed-sale-attempt-suspects-arrested-in-coincheck-hacking-case/
In a statement, the Tokyo police said they had arrested two men for allegedly hacking cryptocurrency exchange Coincheck.
The platform was hacked and about $400 million of “NEM” tokens were stolen in January 2018, which is considered one of the largest hacking operations of cryptocurrency exchanges.
The police have been pursuing the perpetrators ever since, and they believe they have now made progress in the case.


fixThumbnailInListing

1. Why is this change necessary?
The thumbnails in listing and detail page aren't defined correct.
Main-problem: on desktops >1920px the original image is loaded - which is superfluous.
On other breakpoints, the thumbnail of size 800px has been loaded, while it's just displayed in size of 200px
2. What does this change do, exactly?
I checked the image sizes in box-image in every breakpoint and defined a value for it.
It looks like, there is no need for max-width, so I removed it :-)
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-10052
Please use this issue to track the state of your pull request.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.7 out of 16 committers have signed the CLA.:white_check_mark: jleifeld:white_check_mark: shyim:white_check_mark: jochenmanz:white_check_mark: tinect:white_check_mark: peterjaap:white_check_mark: MDSLKTR:white_check_mark: JonasMoltke:x: mitelg:x: leichteckig:x: philipgatzka:x: pweyck:x: PaddyS:x: pantrtxp:x: OliverSkroblin:x: Niklas:x: taltholtmannNiklas seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Rebased onto master
Added sizes for gallery-slider in detailpage, cause currently there is still loaded the original file

I tested this PR in regard to the Shopware Boost Day and this Issue(https://github.com/shopwareBoostDay/platform/issues/110). I came to the conclusion that this fix isn't working correctly. The correct image size is loaded but not displayed in the correct size. In this case a thumbnail with a width of 400 pixels was loaded but it is only displayed at a maximum width of 200 pixels.

My setup is a window size of 2048x1002 pixels and a devicePixelRatio of 1.

This is cause your image is not square and in landscape format. This PR fixes the current behaviour of requesting to big images - but in fact doesn't catch mentioned cases.

@raknison Any news? :-)

@tinect, we discussed your changes and while it is great that you are trying to fix this, we have seen a few things with this PR that could cause issues and had a few more things we would also like to change while at it, therefore we are currently favouring doing this fix internally.

@tinect, we discussed your changes and while it is great that you are trying to fix this, we have seen a few things with this PR that could cause issues and had a few more things we would also like to change while at it, therefore we are currently favouring doing this fix internally.

Hey @J-Rahe,
Thank you. But when will it happen? The issue persists so long. 🙈

@tinect we do have an ticket for that but i cant tell you when it is being done. The ticket didn't make it into the current roadmap and is now in the Performance backlog.


Running the Payment run multiple times a day results in multiple DirectPaymentFile rows and overwriting the payment file

If the payment run executes it overwrites an existing payment file (if run multiple times the same day). This could result in a lose of data.

Add a timestamp to the filename.

verified


Fix indentation for lines where scope changes

Fixes #12708
Here's my attempt at fixing it, which solves my use case.

@Ingramz Thanks for tracking this down! Could you add a test for this? See this test for an example of how the test could be written.
Are you able to reproduce this with any of Atom's built-in languages (perhaps markdown with an embedded code block, or HTML with JavaScript or CSS embedded?

@maxbrunsfeld The trick is that the scope has to change on a line where the outer language indents one line before the embedded language, which HTML tags should do in combination with JS/CSS. I'll have to see if this holds and then will add tests.
On a related note, any idea why the algorithm skips indenting lines that consist entirely of a comment? I think there's another bug with that approach.

any idea why the algorithm skips indenting lines that consist entirely of a comment?

Are you referring to this conditional? I think that commented lines are skipped because otherwise, we might falsely think that they contain tokens that would require indentation.
For example, in this code:
if (a) {
  // }
  b()

  // {
  c()
}

If we didn't have that conditional, then b() would be out-dented incorrectly, and c() would be indented incorrectly.

@maxbrunsfeld Yes, I was referring to that conditional.
That behavior currently breaks indenting block comments like for instance in HTML:

@maxbrunsfeld I finally managed to look into this.
Embedded JavaScript fails because this oddity https://github.com/atom/language-html/blob/2868437114869fd8e0036ad242fe815ab7bed36d/grammars/html.cson#L217-L227
Because tag inside end is detected using positive lookbehind, it will stay inside contentName scope, which makes it use the decreaseIndentPattern for source.js.
Embedded CSS fails because the surrounding scope name for embedded CSS style tag contains source.css, which makes it use the decreaseIndentPattern for source.css. https://github.com/atom/language-html/blob/2868437114869fd8e0036ad242fe815ab7bed36d/grammars/html.cson#L123
Yay, more bugs.

File issues please and I'll try to look into those.

For script tags, an issue exists already https://github.com/atom/language-html/issues/82

I rebased this pull request to fix the merge conflicts. Also added a check to ignore scopes from leading whitespace. With recent (yet to be released) language-html fixes, it indents everything as desired no matter how the lines have been indented before re-indenting.
The HTML comment example is unsurprisingly still broken. It can be fixed by stripping comment indent patterns from the language-html settings and enforce a policy that we cannot have indent patterns for comments, although it would be better if there was some thought put into better handling comments.
I am currently looking into a way to filter out all contents of comments except for the punctuation tokens at the beginning / end of the comments and trying to apply the patterns on that string instead. This will allow some basic indentation based on comment punctuation tokens, but will not match any of the contents of the comments, which should make it more flexible compared to the current algorithm.
This approach should fix auto-indent for cases such as this:
if (a) {
    // }
    b()

    c() // {
}

@ingramz Could you please fix the conflicts again
You can use Github's UI to fix the conflict issues.
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github

Due to the 3 years of uninterest from the core team and the nontrivial changes making it more difficult to reapply this pull request verbatim, I will respectfully decline and close the pull request instead.
If someone with merging privileges is interested, I can invest the time to make it work again.


Support for denoised latent images on progress updates

Working on adding preview images to the demo app here https://github.com/huggingface/swift-coreml-diffusers/pull/65
However, I noticed that when accessing the computed property currentImage from StableDiffusionPipeline.Progress at any point before the final step, the images are quite noisy (and can trigger the safety check for some reason.)
This PR just converts the noisy latent images into their denoised versions (for both schedulers) before sending them through to the progress update.
Here's an example:
https://github.com/apple/ml-stable-diffusion/assets/1981179/9bcdf9b8-6ca5-4ca0-a15f-bcb23232c173
Denoised:
https://github.com/apple/ml-stable-diffusion/assets/1981179/8ebd9235-34d7-457a-8056-345e1f9b58ab
Do not erase the below when submitting your pull request:
#########

[x] I agree to the terms outlined in CONTRIBUTING.md

Hi @ZachNagengast, great work! Do you have a measurement on how much (if at all) this reduces the iterations per second throughput?

Hi @atiorh thanks for looking at this - for the DPM scheduler the modelOutputs are already being generated and stored, this just makes them accessible, so shouldn't have an impact there.
For the PNDM scheduler I did some tests on my M2 and it seems negligible using the diffuser app and SD 2.1:
For seed 902, with 25 steps and 5 previews, it took
13.2s without denoising
13.2s with denoising
The main throughput impact seems to be the actual decoding from the latents, which is why it's good that currentImages is a computed property, because we can give the option to run at full speed or slower but more intermediate images.

@atiorh sounds good, do you have a preference between an option in StableDiffusionPipeline.Configuration, or as an additional property in StableDiffusionPipeline.Progress such as currentDenoisedLatentSamples? Or both?
Both might look like this:
    public struct Progress {
        public let pipeline: StableDiffusionPipeline
        public let prompt: String
        public let step: Int
        public let stepCount: Int
        public let currentLatentSamples: [MLShapedArray<Float32>]
        public let currentDenoisedSamples: [MLShapedArray<Float32>]
        public let configuration: Configuration
        public var isSafetyEnabled: Bool {
            pipeline.canSafetyCheck && !configuration.disableSafety
        }
        public var currentImages: [CGImage?] {
            if configuration.useDenoisedSamples { // default false
                try! pipeline.decodeToImages(currentDenoisedSamples, configuration: configuration)
            } else {
                try! pipeline.decodeToImages(currentLatentSamples, configuration: configuration)
            }
        }
    }


Add Test Cases for 'Big Bang Integration Testing'

Add Test Cases for 'Big Bang Integration Testing'

Hi @berry120

Hey, I'd like to take this, please! If someone could link to what's meant by "big bang integration testing" that'd be awesome 👍

Here are some resources in regards to "Big Bang integration testing"
https://www.tutorialspoint.com/software_testing_dictionary/big_bang_testing.htm
https://www.guru99.com/integration-testing.html

Closing issue.


feat: add datadog_trace 1.4.1 release

update datadog_trace with release 1.4.1

:tada: This PR is included in version 1.378.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Yarn nor NPM seem to be reflecting latest changes

Hey everyone. Thank you for having updated the repo. I was struggling to get it to work when I updated my electron version, but I was able to find out your latest pr.
Is there anyway the version can be updated to 1.0.1 so that yarn recognizes it? if I run yarn install eckey it just downloads the regular package 1.0, without the latest changes.
If I run yarn add https://github.com/cryptocoinjs/eckey   it does download the updated code, but since another package depends on 1.0.0 it becomes a mess. Thank you!

The latest changes have been published as 1.0.1


[RFC] Testing api

While the code in this works fine, I think there's a couple of things that I'd want some feedback on first.
Mainly:

Debug runner:

should we try harder to pipe the result back into tests?
should we try to prevent debugging non-c(++) targets? This would require some heuristics (on dependencies) I think.

Testing runner:

should we run tests in series to avoid the testlog issue?
If not, should we fail the tests that couldn't be run? Maybe set all to skipped, that's a state vscode supports

Other than that, just general review :)
Commits are messy, but this grew while learning^^
closes #23

Git History is pretty messy, but I think the code can be merged as is.
The points I stated for the normal test runner are gone now, since I decieded to go with the simpler route to support e.g. TAP based tests as well (I need to setup gtest/tap tests and then look into doing the parallel stuff again, with maybe a patch to meson).
The debugging stuff is as stated, but I think any improvement there can go into dedicated PRs alter on. It's not broken, just missing a feature.


MongoDB - Delete operation

PR https://github.com/kdhrubo/db2rest/pull/501 is merged, closing the ticket


Rudr samples - bikesharing from Microsoft

Added two new Rudr examples by using the existing Microsoft Bikesharing360 samples.
Original BikeSharing 360 for single containers can be found here, and BikeSharing 360 for single containers can be found here.
Multi-container app contains 3 APIs and a UI and single app is a one container app.
BikeSharing360 is a fictitious example of a smart bike-sharing system with 10,000 bikes distributed in 650 stations located throughout New York City and Seattle. Their vision is to provide a modern and personalized experience to riders and to run their business with intelligence.
This was a team effort from Microsoft OCP app dev CSAs.

Could you move the changes to https://github.com/oam-dev/samples ?

@hongchaodeng thanks for the directions. I just created a pull request for the same here, https://github.com/oam-dev/samples/pull/21

@hongchaodeng , a suggestion, it would be great if we can keep a generalized readme file in the root of the https://github.com/oam-dev/samples and keep all of readme files specific to each sample in its own subfolders. The one that we have now in the root is talking about the service tracker sample.

Closing since the PR in the samples repo got merged :)


#447: Add credits link

Resolves #447

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.979%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6449

Relevant Lines:
6557

💛  - Coveralls


Allow to annotate with max. of all four SpliceAI scores

Is your feature request related to a problem? Please describe.
SpliceAI provides four scores. It mostly makes sense to only consider the maximum of them (but it is also important which one was the max.).
Describe the solution you'd like
Implement annotating with max. SpliceAI score and which one was the maximum.
Describe alternatives you've considered
N/A
Additional context
Ideally, this can be generalized and reused for other scores.

CC @xiamaz

Should be done when switching to worker for seqvar filtration.


[Bug]: Natural curve line oscillates, overshoots or undershoots

Tremor Version
3.4.1
Link to minimal reproduction
NA
Steps to reproduce
use as datapoints 0 value and next datapoint as a high value.
What is expected?
interpolation of natural curve not to oscillate, undershoot or overshoot
What is actually happening?
Line Charts using curveType natural interpolate points in an unexpected way, showing misleading values.
This also causes for line to be cut due to overflow.
value would seem to have been higher than 2.3 (not the case):

value would seem to drop below 0 (not the case):

What browsers are you seeing the problem on?
Chrome
Any additional comments?
No response

This is a characteristic of curveType "natural".
Please take a look at the following recharts sample.
(recharts is a library that tremor uses internally.)
https://codesandbox.io/s/recharts-linechart-sample-kc39qq?file=/src/App.tsx

This might not be a bug, it could be a characteristic of the curveType natural.
I've created sample code with recharts.
(recharts is a library used internally by tremor)
https://codesandbox.io/s/recharts-linechart-sample-kc39qq

Indeed! Is there a paricular reason you wanted to use natural? Have you tried monotone?

Added a new curve type monotone which oscillates a lot less. → https://github.com/tremorlabs/tremor/releases/tag/v3.5.0
Also removed the natural curve type from the recommendation in the docs.

thx! will look into it. Monotone was not a documented option


Display of arbitrary markdown associated with a term

This is a kind of inverted gonuts.
While we can easily inject any comment we want onto a term page using fields like comment, we don't have a way of injecting markdown. As an example, see @dosumis' https://github.com/geneontology/annotation_extensions/blob/master/doc/results_in_morphogenesis_of.md
unlike gonuts, we may want to restrict this so the markdown comes from a location like our github, so we can control what goes in via PRs. The markdown could live in the ontology and be edited in Protege but probably a bad idea..
This should be quite simple. We have a new AP that associates a URL with an OWLObject. This resolves to raw md. Or we assume a particular pattern, e.g. a folder in go-ontology/termdocs/<{GO,RO,...}_nnnnn>.md
The md would be rendered using a standard md->html lib

Well, it's almost exactly like GONUTS as far as amigo is concerned: query remote resource, if found, render into section in static page. Easy-peasy--I've been wanting to add a couple of small things to AmiGO recently, and this could be added easily enough.

[ ] add new variable to amigo config and string through
[ ] add external resource subclass to render markdown at URL pattern
[ ] display data in section if data

Rather than a conf variable, could this be an OWLAnnotation on the ontology? That way the conf could be shared across a wide variety of tools. E.g. can imagine a protege plugin that reads this and allows editing of the md in the context of editing the other term info

The difference is that instead of having this be an "optional" add-on, we have to coordinate with the loader.
amigo's flow looks like:

(pre: add extra field to load and thread additional fields through amigo)
call to get term info from solr
from term info, get URL
use external resource subclass to render markdown at URL pattern
display data in section if data


No success on new install

Hello,
This looks really cool, but I'm not able to get a successful response. Not sure if there is a way to tell if the problem is on my end or somewhere else. Logging in to Uconnect works fine with my credentials.
[09:38:49 INF] Now fetching new data...
[09:38:49 INF] Mqtt connection successful
[09:38:50 DBG] {
  "CallId": "<removed>",
  "ErrorCode": 0,
  "ErrorDetails": null,
  "ErrorMessage": null,
  "ApiVersion": 2,
  "StatusCode": 200,
  "StatusReason": "OK",
  "Time": "2022-12-02T15:38:50.432+00:00"
}
[09:38:50 DBG] {
  "UID": "<removed>",
  "SessionInfo": {
    "login_token": "<removed>"
  },
  "CallId": "<removed>",
  "ErrorCode": 0,
  "ErrorDetails": null,
  "ErrorMessage": null,
  "ApiVersion": 2,
  "StatusCode": 200,
  "StatusReason": "OK",
  "Time": "2022-12-02T15:38:50.88+00:00"
}
[09:38:51 DBG] {
  "id_token": "<removed>,
  "CallId": "<removed>",
  "ErrorCode": 0,
  "ErrorDetails": null,
  "ErrorMessage": null,
  "ApiVersion": 2,
  "StatusCode": 200,
  "StatusReason": "OK",
  "Time": "2022-12-02T15:38:51.003+00:00"
}
[09:38:51 DBG] {
  "IdentityId": "<removed>",
  "Token": "<removed>"
}
[09:38:52 WRN] Error connecting to the FIAT API.
This can happen from time to time. Retrying in 15 minutes.
[09:38:52 DBG] Response could not be deserialized to JSON: GET https://channels.sdpr-02.fcagcv.com/v4/accounts/<removed>/vehicles?stage=ALL
[09:38:52 INF] Fetching COMPLETED. Next update in 15 minutes.

what car and which vendor ?
can you control your car with one of the following sites ?
Fiat: https://myuconnect.fiat.com/
Jeep: https://myuconnect.jeep.com/
Ram: https://connect.ramtrucks.com/
Dodge: https://connect.dodge.com/
AlfaRomeo: https://myalfaconnect.alfaromeo.com/

I'm having the same issue with my Jeep in North America. Same credentials work on the uconnect site, but not via FiatChamp. I am seeing the same API error in the log

I did go ahead and get through the first four steps in Postman. I got everything working up to the Congnito part. Now I understand what the existing debug means, and why the whole thing can't be done in Postman.  On Saturday I'll put it in code with some Cognito support and see how much further I get. I did notice in another FIat API project, they were using the real AWS region names in Cognito, like appear in the beginning it IdentityId in the tokenURL response, such as eu-west-1, rather than EUWest1, but I don't know enough about CS to even know what the name is doing there. My IdentityID starts with us-east-1. Probably nothing. I'll play with it some more in a few hours.

Just a quick result while I got through it. Response is 200 and JSON is valid. Error persists. It's in this order:
[09:34:53 DBG] {
"IdentityId": "",
"Token": ""
}
[09:34:54 WRN] Error connecting to the FIAT API.
This can happen from time to time. Retrying in 15 minutes.
[09:34:54 INF] ERROR: Response could not be deserialized to JSON: GET https://channels.sdpr-02.fcagcv.com/v4/accounts//vehicles?stage=ALL
[09:34:54 INF] STATUS: 200
[09:34:54 INF] RESPONSE:
[09:34:54 INF] Fetching COMPLETED. Next update in 15 minutes.

Ah. The "could not be deserialized" error looks like a Flurl error. Like maybe it is trying to convert something in the response or treating something like an array that is actually a string or vice versa. Appears the comms are fine. Let me compare code and output.

Looks to be something with VehicleResponse, but the only thing you seem to be doing with that is getting the VIN.
vehicleResponse.Vehicles.First().Vin
(object)->vehicles[0]->vin is present in the output, so nothing glaring there except for them being all lowercase in the JSON, but I don't think that matters in Microsoft land.
I think I got the more sensitive bits (UserID and VIN) out of this output, but I may have to come back and edit if I missed something. You should be able to run this through the Flurl parser manually and see where it is complaining.

{
  "userid": "12345678901234567890123456789012",
  "version":<PHONE_NUMBER>470,
  "vehicles": [
    {
      "regStatus": "COMPLETED_STAGE_3",
      "color": "BALTIC GREY",
      "tsoBodyCode": "",
      "year": 2022,
      "isCompanyCar": "",
      "navEnabledHU": false,
      "language": "",
      "customerRegStatus": "Y",
      "radio": "",
      "activationSource": "DEALER",
      "nickname": "",
      "company": "FCA",
      "model": "WLXT74",
      "vin": "12345678901234567",
      "tcuType": "2",
      "make": "Jeep",
      "brandCode": "57",
      "soldRegion": "NAFTA",
      "svla": {
        "status": "INACTIVE",
        "timestamp": 0
      },
      "tc": {
        "activation": {
          "version": "v1.23",
          "status": "Accepted"
        },
        "registration": {
          "version": "1.0.0",
          "status": "Accepted"
        }
      },
      "market": "US",
      "modelDescription": "Grand Cherokee 4xe",
      "fuelType": "H",
      "tsoModelYear": "",
      "sdp": "IGNITE",
      "regTimestamp":<PHONE_NUMBER>686,
      "services": [
        {
          "vehicleCapable": true,
          "service": "SVLAAPP",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "SVLA",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "ROC",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "RDU",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "RDL",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "HUC",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "AOTAC",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "BCALL",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "SOS",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ASSIST",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ECALL",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "HBLF",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ASOS",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "DTC",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_FUEL_FINDER",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_PARKING_FINDER",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_ROUTE_DRM",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_SEARCH",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_SPEED_CAMERA",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_TRAFFIC",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_WEATHER",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "PARENT",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "REOFF",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "REON",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "SDV",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "SQDF",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "TA",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "VF",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "VHSG",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "VRC",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "WIFIHOTSPOT",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "FTD",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "IVA",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "IVM",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "PHEV",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "ALEXAVA",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "WIFIP",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "VHS",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "CNOW",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "CSL",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "CP",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "EVNOT",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ELECPAGES",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ORP",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "GSKILLL",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "LASTMILE",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "AOTACI",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ROAD",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "CARE",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ROCRANKINHIBITON",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ROCRANKINHIBITOFF",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "TA_SUP",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "DRIVEMODES",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "RACEOPTIONS",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_MOTA_CELL",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_MOTA_WIFI",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_OB_MOTA_WIFI_CELL",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "BRAND",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "DUMMY",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "DEEPREFRESH",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "FRONTSEAT",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "MACMEDIAAPP",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "L2DATALOG",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "L2MAPSGEO",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "L2GPSCORRECTION",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "TUTORIALS",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ORPPLUS",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ADA_TBM",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "NAV_TOMTOM",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ROCLRPERSDATA",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ROC2",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "ADA_UBI",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": true,
          "service": "CPCHRG2",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "CPA",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": true,
          "service": "CSEV",
          "serviceEnabled": true
        },
        {
          "vehicleCapable": false,
          "service": "TRAILERTP",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "KNGLNKOUT",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "DUMMY_EVAS",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "DUMMY_ENHDCAM",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "DUMMY_TECHFEE",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "DUMMY_WIRECAM",
          "serviceEnabled": false
        },
        {
          "vehicleCapable": false,
          "service": "DUMMY_TRAILERTP",
          "serviceEnabled": false
        }
      ],
      "privacyMode": "INACTIVE",
      "cslProvider": "TOMTOM",
      "subMake": "Jeep",
      "pp": {
        "activation": {
          "version": "1.0.0",
          "status": "Accepted"
        }
      },
      "enrollmentStatus": "COMPLETE",
      "channelFeatures": [
        {
          "featureCode": "100",
          "channels": [
            "CWP",
            "GMA"
          ]
        },
        {
          "featureCode": "f_0097_N",
          "channels": [
            "CWP",
            "GMA"
          ]
        }
      ]
    }
  ]
}

thx for the json output. i think the error is at line 566 when the http client tried to deserialize the response ( https://github.com/wubbl0rz/FiatChamp/blob/master/FiatChampAddon/FiatClient/FiatClient.cs#L566 )
should not be that hard to figure out. i will try to deserialize it by hand as VehicleResponse and see what the actual error from the serializer is.

thats the problem
Error converting value "WLXT74" to type 'System.Int64'. Path 'vehicles[0].model',

fiat model is always a number :smile: sould be easy to fix ... switch from int to string should not break anything.

should work now. pls try 3.0.5.

Just updated to 3.05 and it's working for me. Really appreciate the work to fix this. Thank you! :) FYI I am west coast USA and have 2022 Jeep Grand Cherokee L

Hmm. Not for me I don't think. Got further but still erroring. Looking...

Something related to location it seems. I changed my actual long/lat below, but fairly close
[10:43:24 WRN] Error connecting to the FIAT API.
This can happen from time to time. Retrying in 15 minutes.
[10:43:24 DBG] ERROR: Response could not be deserialized to JSON: GET https://channels.sdpr-02.fcagcv.com/v1/accounts/6e1aedb0a8b5454bb18e6850003150e8/vehicles/1C4RJYE62N8715709/location/lastknown
[10:43:24 DBG] STATUS: 200
[10:43:24 DBG] RESPONSE: {"timeStamp":1670076291636,"longitude":-95.707932,"latitude"32.536167:,"altitude":null,"bearing":null,"isLocationApprox":false}
[10:43:24 INF] Fetching COMPLETED. Next update in 15 minutes.

Maybe not expecting NULL for altitude and bearing?

I do have refresh location configured off. Retrying.

let me check. but good you find all this bugs :grin:

altitude is a double so null might be a problem ... i dont want to know how many workarounds they have implemented in their app to get all this working :smile:  refresh location of does not matter its only for automatic querying new location from the car every N minutes.

No change when location refresh configured ON. Error persists. Altitude and bearing are still NULL.

pls try with 3.0.6

Yuck. I don't have PIN configured in the add-on.
[11:22:13 ERR] Command: DEEPREFRESH ERROR. Maybe wrong pin?
[11:22:13 DBG] Flurl.Http.FlurlHttpException: Call failed with status code 403 (Forbidden): POST https://mfa.fcl-01.fcagcv.com/v1/accounts/<removed>/ignite/pin/authenticate
   at Flurl.Http.FlurlRequest.HandleExceptionAsync(FlurlCall call, Exception ex, CancellationToken token)
   at Flurl.Http.FlurlRequest.SendAsync(HttpMethod verb, HttpContent content, CancellationToken cancellationToken, HttpCompletionOption completionOption)
   at Flurl.Http.FlurlRequest.SendAsync(HttpMethod verb, HttpContent content, CancellationToken cancellationToken, HttpCompletionOption completionOption)
   at Flurl.Http.ResponseExtensions.ReceiveJson[T](Task`1 response)
   at FiatChamp.FiatClient.SendCommand(String vin, String command, String pin, String action) in /home/runner/work/FiatChamp/FiatChamp/FiatChampAddon/FiatClient/FiatClient.cs:line 529
   at Program.<>c__DisplayClass0_0.<<<Main>$>g__TrySendCommand|1>d.MoveNext() in /home/runner/work/FiatChamp/FiatChamp/FiatChampAddon/FiatClient/Program.cs:line 259
[11:22:13 INF] SEND COMMAND VF:
[11:22:13 ERR] Command: VF ERROR. Maybe wrong pin?
[11:22:13 DBG] Flurl.Http.FlurlHttpException: Call failed with status code 403 (Forbidden): POST https://mfa.fcl-01.fcagcv.com/v1/accounts/<removed>/ignite/pin/authenticate
   at Flurl.Http.FlurlRequest.HandleExceptionAsync(FlurlCall call, Exception ex, CancellationToken token)
   at Flurl.Http.FlurlRequest.SendAsync(HttpMethod verb, HttpContent content, CancellationToken cancellationToken, HttpCompletionOption completionOption)
   at Flurl.Http.FlurlRequest.SendAsync(HttpMethod verb, HttpContent content, CancellationToken cancellationToken, HttpCompletionOption completionOption)
   at Flurl.Http.ResponseExtensions.ReceiveJson[T](Task`1 response)
   at FiatChamp.FiatClient.SendCommand(String vin, String command, String pin, String action) in /home/runner/work/FiatChamp/FiatChamp/FiatChampAddon/FiatClient/FiatClient.cs:line 529
   at Program.<>c__DisplayClass0_0.<<<Main>$>g__TrySendCommand|1>d.MoveNext() in /home/runner/work/FiatChamp/FiatChamp/FiatChampAddon/FiatClient/Program.cs:line 259

disable "refresh battery status" and "refresh location"

I have data for the first time! Location and battery have data in HA, so I'm not sure what those refresh settings do, or why changing them fixed the issue.
Documentation says PIN is only needed for write ops.
It looks like HA still creates switches for write ops, but I dare not click them.

nice :+1:  i should rename "refresh battery status" and "refresh location" to "FORCE refresh" or something like that. it will actively request new values from the car. thats why it needs the pin. fiat calls this "commands". if you leave them disabled new data will arrive when the car thinks its a good time to update :smile:
if you like we can make commands work ? thats the only thing i cannot lookup myself without owning a car. because one need to send a command to a real car to see which url and api key is used. all can be seen in browser dev tools i can post a screenshot where to look at.
PS: if no pin is set a "PIN NOT SET" exception should be raised but it looks like thats not the case. i will fix this with next update.

I'll probably mess around with commands.
I think it is cool as a developer to understand user's use-cases, I will tell you that I sought out this add-on because I wanted HA to send a reminder when the EV is at home, battery is not full, and EV is not plugged in. Sometimes we forget to plug it in. Seems like a fairly common use case for people that make it this far in their life instrumentation and automation journey. Strangely it seems like the reminder portion is not yet a commercial feature, at least not for the Stellantis group.
I think it is ok to close this bug, as long as you want me to open new ones for other stuff I find.

alright nice that t works 👍  if you want to lookup comman durls and api keys in the browser tools let me know 🚀


feat: update Tutunota, rebranding as Tuta

[ ] I have read the Contributing Guidelines* for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.

*404 - page not found
Description of Change
Tutanota got rebranded as Tuta
This PR includes:

name changed
alias added
icon replaced
serviceUrl updated
id unchanged

Todo

[ ] open migration in ferdium-app instead of browser

according to #1445
There is an option to migrate saved credentials and a link is shown to do so, but

it wont't work when opened in browser
needs to be opened in ferdium-app

If you don't mind, I would prefer merging #463 instead, as it is pretty much the same and does not change the logo, as described in the PR comments (Tuta just inverts all colors for dark mode).

Thanks for the help, Marc! I appreciate it lots.
I merged the previous PR of this, and you should see the service name update shortly!
We're also updating the broken link you noticed in the PR template in #469.
Have a good evening!
Duplicate of #463

If you don't mind, I would prefer merging #463 instead, as it is pretty much the same and does not change the logo, as described in the PR comments (Tuta just inverts all colors for dark mode).

But this is the look of Tuta Mail, there is no other light mode with the old colors. All screenshots advertising the service show this new neon green look: https://tuta.com

there is no other light mode with the old colors

There are three color schemes available: Light (red on white), Dark (inverted colors), and Blue (blue on white).
The Dark mode simply inverts the colors and this is not the "new" Tuta logo. It has also inverted the colors long before the rebranding, therefore this is not a new change.

All screenshots advertising the service show this new neon green look

If you scroll down on the main website you linked and select the "Contacts" screenshot, it is shown in Light mode, with the non-inverted colors:

I appreciate your input on this matter! However, I have to disagree, as there was definitely no logo change.
The way Tuta chose to implement the Dark mode in their products is unfortunate.
If you would like to use the inverted logo out of preference, do set a custom icon for your service of course!


Stopping Share Screen Does not switch back to camera

Describe the bug
When I am in a video call , I start screen sharing so my camera feed gets replaced with my screen feed, but when I stop sharing my screen using (await agoraEngine?.stopScreenCapture()), it stops the screen share feed, but does not switch back to the camera feed
Expected behavior
Upon Stopping screen sharing , the video feed should be replaced with the camera feed

same problem here..

Which platform are you running into issues with?

Both Android & iOS

Can You Expose this method to be used in the flutter SDK: setVideoSource (newAgoraDefaultSource ())
https://docs.agora.io/en/Voice/API Reference/java/classio_1_1agora_1_1rtc_1_1_rtc_engine.html?platform=Android#aa240e991d12b5240fc5fd362cbc0d521

same issuse

It's a known issue, we will expose a new API to achieve this on the next release.

does any one have solution for screen sharing in android and ios

This fix has been merged to https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/tree/master, you can depend on the agora_rtc_engine as the git package at this time.

This fix has been released agora_rtc_engine: ^5.3.1.
https://pub.dev/packages/agora_rtc_engine

Thank you so much


displaying arabic number characters dynamically

For some reasons I need to display custom number values but I also need them to be set dynamically in java.
By the way I can't use the setDisplayedValues(), method because of array out of bound exception.
Is there any way to do it?

Fixed at v2.4.9.


ng-reflect-model shows correct value but not reflecting in mat select

Crop Type  *

<mat-select   placeholder="Select Crop Type" [(ngModel)]="cropname"  class="select" formControlName="croptype">
<mat-option *ngFor = "let i of Croptype"  [value] = "i">{{i.CropName}}

When i tried to use two way binding to bind dynamic value to ngmodel, ng-reflect-model is updating correct value,but view is not getting updated
In component.ts
Croptype =
[ { CropID: '1', CropName: 'sweetlime', ScientificName: 'CitrusImetta' }, ];
this.cropname=newsortOrder != undefined ? newsortOrder.cropName : '';
when iam updating ngmodel value with below line the above issue occurs
The issue is in following example: https://stackblitz.com/edit/angular-be1gqv?file=src%2Fapp%2Fapp.component.html

The ng-reflect- attributes are mostly there for backwards-compatibility and you shouldn't depend on them, because they won't be set in production mode. Closing the issue, because it's also something that the framework is responsible for.

The ng-reflect- attributes are mostly there for backwards-compatibility and you shouldn't depend on them, because they won't be set in production mode. Closing the issue, because it's also something that the framework is responsible for.

so,please tell the fix for this issue

so,please tell the fix for this issue


Add Snapshot-test-for-Live-Observation

Jira issue:
https://glia.atlassian.net/browse/MOB-2718
What was solved?
Snapshot tests for LO related alert and snackbar
Snapshot image reference PR - https://github.com/salemove/ios-widgets-snapshots/pull/58
Release notes:

[ ] Feature
[X] Ignore
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Tests fixed, added? Unit, acceptance, snapshots?
[ ] Logging necessary for future troubleshooting of customer issues added?

Screenshots:

!squash


Update modules-api-polyfill package to latest

CI failures are due to a change in how @babel/preset-env works. I dug into this with @chadhietala the other day, will try to get master green in a separate PR shortly.

Master was unblocked by #284

finally!


Hidden Messages

Add hidden messages. (Optional)
This is low priority, but would be fun to have. The idea is to add a number of hidden messages that can appear via the spawned fruit. If the player notices, they might decide to track what letters are appearing in order to decipher the hidden message. These messages would start appearing at a later stage of the game, and not towards the beginning.
An example of a hidden message: "You are doing great", "Keep being awesome", "You suck", "Oh hi"...

Another idea i just had for this:
Currently, the snake is rendered as the word "snake", with more 'a's being added in the middle as the snake grows. Because the snake is rendered as characters, the hidden messages could also appear by "scrolling" through the body of the snake. It would be a neat little effect, as well as make the message easier to find/read.


Support iPhone SE iOS 10.2

Please add iPhone SE
Thanks

This should be the last place for a request...

I do not think s...


fix params for old centos/redhat versions

Currently EPEL repository contains the same version of easy-rsa package for all CentOS/RedHat versions:
http://pkgs.org/search/easy-rsa

I am wondering, does this change frequently? Do they add new packages to EPEL during maintenance of a OS version? I don't know this from Debian/Ubuntu. There is a feature freeze and these versions/packages will be kept. Only security fixes will be backported. How does this RedHat/CentOS handle?

From EPEL description:

EPEL (Extra Packages for Enterprise Linux) is a volunteer-based community effort from the Fedora project to create a repository of high-quality add-on packages that complement the Fedora-based Red Hat Enterprise Linux (RHEL) and its compatible spinoffs, such as CentOS and Scientific Linux.

You have to enable It manually and it can be compared with universe repo in Debian. The new packages can be added anytime to this repo. Also it uses feature freeze for exists version, but the rules are not so strict as in base repos.
Also this part of code was incorrect from the beginning because EPEL packages are not related to  minor versions of distro.
  # Redhat/Centos >= 6.4
  } elsif(versioncmp($::operatingsystemrelease, '6.4') >= 0) {
    $additional_packages = ['easy-rsa']
    $easyrsa_source      = '/usr/share/easy-rsa/2.0'
    $systemd             = false

  # Redhat/Centos < 6.4 >= 6
  } elsif(versioncmp($::operatingsystemrelease, '6') >= 0) {
    $easyrsa_source = '/usr/share/openvpn/easy-rsa/2.0'
    $systemd        = false

I don't know when easy-rsa package was added for EPEL 5  (CentOS ~= 5.*). But currently it is there :)


[WIP] Pod setup rethought release 0.6

Backport of pod setup.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

ok to test

/release-note-none

I think we decided do not merge it until we will have the final decision under the master branch.


Update README.md

Warning to use REST-API-KEY when you are not using localhost

It's still not required.  Client keys are no longer strictly necessary with parse-server.  The rest key has no privileges above the client keys here, and all the client keys were considered public... So, they only served to identify the app as a combination of both, and here the app id is sufficient.


Failed to start gauge API - 0.8.1 is failing on alpine images

Describe the bug
Failed to start gauge API - 0.8.1 is failing on alpine images
To Reproduce
Steps (or project) to reproduce the behavior:

Update the gauge-java version to 0.8.1 in https://github.com/getgauge-examples/java-maven-selenium
Run the following

docker run --rm -it -v $(pwd):/usr/src/app -v /Users/${USER}/.m2:/root/.m2 sitture/docker-gauge-java:1.4.3 mvn gauge:validate

Error:
[Gauge]
Failed to start gauge API: Error occurred while waiting for runner process to finish.
Error : exit status 1

Get Support ----------------------------
	Docs:          https://docs.gauge.org
	Bugs:          https://github.com/getgauge/gauge/issues
	Chat:          https://github.com/getgauge/gauge/discussions

Your Environment Information -----------
	linux, 1.4.3, f98dd40
	html-report (4.1.4), java (0.8.0), reportportal (1.13.0), screenshot (0.1.0), xml-report (0.2.3)

➜  java-maven-selenium git:(master) ✗ docker run --rm -it -v $(pwd):/usr/src/app -v /Users/${USER}/.m2:/root/.m2 sitture/docker-gauge-java:1.4.3 gauge -v
Gauge version: 1.4.3
Commit Hash: f98dd40

Plugins
-------
html-report (4.1.4)
java (0.8.0)
reportportal (1.13.0)
screenshot (0.1.0)
xml-report (0.2.3)

Additional context
Add any other context about the problem here.

Hi @haroon-sheikh , it seems the version of gauge-java is 0.8.0 in the log you attached. Is this as what you intended?

Good spot @i-whammy. That was just me testing with different versions, the same issue persists with 0.8.1
[INFO] --- gauge-maven-plugin:1.4.2:validate (default-cli) @ active_admin ---
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000003efe, pid=103, tid=108
#
# JRE version: OpenJDK Runtime Environment (11.0.14+9) (build 11.0.14+9-alpine-r0)
# Java VM: OpenJDK 64-Bit Server VM (11.0.14+9-alpine-r0, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  0x0000000000003efe
#
#
No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /usr/src/app/hs_err_pid103.log
[thread 125 also had an error]
[thread 129 also had an error]
[thread 126 also had an error]
[thread 128 also had an error]
#
# If you would like to submit a bug report, please visit:
#   https://gitlab.alpinelinux.org/alpine/aports/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Error occurred while waiting for runner process to finish.
Error : exit status 1
Error ----------------------------------

[java]
process /usr/bin/java with pid 103 quit unexpectedly. signal: aborted

[Gauge]
Failed to start gauge API: Error occurred while waiting for runner process to finish.
Error : exit status 1

Get Support ----------------------------
	Docs:          https://docs.gauge.org
	Bugs:          https://github.com/getgauge/gauge/issues
	Chat:          https://github.com/getgauge/gauge/discussions

Your Environment Information -----------
	linux, 1.4.3, f98dd40
	html-report (4.1.4), java (0.8.1), reportportal (1.13.0), screenshot (0.1.0), xml-report (0.2.3)

@sriv have you had a chance to look at this? is there anything I can do to help please?

Related to https://github.com/grpc/grpc-java/issues/8751

@zabil @sriv Do you think we can downgrade the grpc version to < 1.42.x? The workaround above works for gauge but break anything else running within the image?


Added an Events Archive page

There's a bit more to it than just that though, take a look at the commits.
I refactored the JavaScript for rendering events, as there was a lot of duplicate logic.
I also changed to using JavaScript's Date.toDateString() to get, e.g. Jul or Wed, rather than depending on two arrays at the start of the file.
Lastly I moved the sidebar out to it's own include, and then created a new base.html template, which the default.html and archive.html templates both extend from, to be used on the index.html and archive.html pages.

:heart: :m: :a: :heavy_multiplication_x: :heart:

We need a business-cat tweaked to catch over-emojification methinks. This looks ace @omgmog :+1:

Mergio, :+1:


Add getAttributeNames polyfill

Hi,
hope I did it right, I tried to polyfill this method https://developer.mozilla.org/en-US/docs/Web/API/Element/getAttributeNames which is very convenient. So much convenient I though it was in every browsers since years... sigh
@JakeChampion could you guide me for the config and stuff? I tried to mimic others polyfills. Thanks.

Thanks for the pull request @JSteunou 👍  This is looking good, I've done an initial review, I will run through the config.json at a later date. The way I usually create the config.json browser list is by checking the MDN page's browser support table.

Yep, I did check support on MDN too, but I'm still in the dark for android, bb, opera mobile & samsung mobile

@JSteunou I will run some tests on those browsers and update the config in this PR 👍

@JSteunou The tests currently fail in IE7. You should be able to replicate this by starting the application via npm start and visiting the urls below in IE7.
- ie/7:
    -> Element.prototype.getAttributeNames should return an empty array when no attributes
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       85 == 0
    -> Element.prototype.getAttributeNames should return the list of all attribute names
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       87 == 2
    -> Element.prototype.getAttributeNames should return the list of all attribute names including id
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       85 == 1
    -> Element.prototype.getAttributeNames should return the list of all attribute names including data attributes
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       87 == 2

Ho my... IE7 ! This far ?! I will try to find one

Ok I think I find why, IE7 does not support Element.prototype.setAttribute. Are you sure to support IE7, there is even no polyfill for Element.prototype.setAttribute and Windows XP last browser is IE8.

@JakeChampion friendly ping ;)
should I ignore IE7 support or add a setAttribute polyfill?

@JSteunou I've updated the tests to work in IE7, they will fail though as the polyfill doesn't work in IE7 because in IE7 the attributes property on Element objects contains 85 items for empty elements. E.G. document.createElement('

').attributes.length === 85

Failing tests on IE7:
Failures:
 - ie/7:
    -> Element.prototype.getAttributeNames should return an empty array when no attributes
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       85 == 0
 - ie/7:
    -> Element.prototype.getAttributeNames should return the list of all attribute names
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       87 == 2
 - ie/7:
    -> Element.prototype.getAttributeNames should return the list of all attribute names including id
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       85 == 1
 - ie/7:
    -> Element.prototype.getAttributeNames should return the list of all attribute names including data attributes
       http://<IP_ADDRESS>:3000/test/tests?mode=targeted&feature=Element.prototype.getAttributeNames
       87 == 2

Damn... still after your changes, still the same error?

@JSteunou That error is because IE7 lists all options in the Element object attributes property instead of only the explicitly set attributes. It is a bug in IE7 that we would need to work around.


Intel Mac not supported?

Using a Mac Book Pro 2020 Intel i5

thanks for raising this... the binary uploaded under releases for macOS was compiled for arm64. I have since compiled for amd64 architecture which should work on Intel Macs.
Do check out releases and try out the amd64 version. You can download it directly here for convenience: lominus-amd64-unsigned-v1.1.2.dmg
Hope to hear back from you on whether Lominus works on Intel Macs. Thanks !

Issue should be resolved. Please reopen if issue persists.


"It works!"  Congratulations!

I love seeing

somewhere on a project!

Haha yeah, PySimpleGUI ended up working out great for what I needed. Still going to be tweaking it a bit but it worked with 0 headache. Also great job on the error messages. I tried to call fullscreen and got an error message that told me exactly how to fix it right in the GUI (e.g. pass finalize=True or call finalize() before maximize).


Update ch11-07-inlining-in-cairo.md Cams Casm

Fixing typo Cams to Casm

This change is

@gaetbout  great! thank you :)


What is the proper way to set the cursor theme?

OS: Arch Linux
WM: wlroots-based
nwg-look: 0.1.1
First off, thanks for this great tool, it very much improves the user experience of theming!
Not sure whether this is a bug, but when picking a cursor theme I still have to set the theme manually in ~/.icons/default/index.theme to make it visible on the plain WM layer/background (on waybar and GUI apps it's working as expected), leaving it blank will make the theme fall back to the "system" cursor.
Any ideas are appreciated,
Thanks again

Somehow I missed it. I will add the editing of this file to the program.


Start using the ci-scripts submodule

Replace old .ci scripts with the new submodule
Migrated env var package to travis.yml

JFYI, anyone with an existing repo will have to update their existing submodules by doing the following -
git submodule update --init --recursive

If that doesn't work you may have to delete the folders .ci, and .git/modules/.ci manually and retry the update.
/cc @robskillington @xichen2020 @kobolog @cw9 @martin-mao @ben-lerner

Coverage decreased (-0.03%) to 77.854% when pulling c5ca89d625f3c6517472aa8cbae0bc86daea5cba on prateek/ci-scripts-submodule into 152f5019b5c66defa6ea35f405449678b792ebb9 on dev.


Remove max gas

Closes #170

Targeted PR against correct branch (see CONTRIBUTING.md)

[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.

[ ] Wrote tests

[ ] Updated relevant documentation (docs/)

[ ] Added  relevant godoc comments.

[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md

[ ] Re-reviewed Files changed in the Github PR explorer

For admin use:

[ ] Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
[ ] Reviewers assigned
[ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

Yeah, sorry, I added the commit message, but forgot to add it to the description
This works for everything but one place, and I don't know why it fails there (thus the Printf). I will try to look later, unless someone else wants to take a look

Closing in favor of #193


use in a program without unit tests?

Is it possible to use this in a situation that unit tests does not exist?
I have an asp.net core app and I want to measure its coverage based on its actual usage in my prod environment.

I'm pretty sure you can use it for that scenario, although coverlet doesn't support this out of the box. You'd have to checkout the code yourself and make all the necessary modifications.


Fix NSRDB download location name check

Fixes #710
This fix should allow location name entered as any string, a city/state pair separated by a comma, or a lat/lon pair separated by a comma followed by a space, comma with no space, or space with no comma.

The error message about "required 'email' parameter" should only happen when you test on a non-NREL version of SAM because the email value comes from the registration process. We can double check this when we build a Beta version.


CB-15203 remove springfox version which are not coming from common pl…

…aces
See detailed description in the commit message.

Follow-up to #11885.


AI-generated Sonarqube issue remediation: remediation_branch-2024-10-24_03-43 -> main

From 2 remediated issues 1 require additional actions

Issue Key
Message
Action

src/main/resources/application.properties:17_https://github.com/cloudply/spring-petclinic_CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
Ensure that the endpoints 'info' and 'health' are properly secured and do not expose sensitive information.

@CodiumAI-Agent /review

PR Reviewer Guide 🔍
Here are some key observations to aid the review process:

⏱ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 Security concerns
Sensitive information exposure: The change in 'application.properties' to expose 'info' and 'health' endpoints could potentially expose sensitive information if these endpoints are not properly secured.
⚡ Recommended focus areas for review
Sensitive Information ExposureThe change to expose only 'info' and 'health' endpoints might still expose sensitive information if not properly secured. Ensure these endpoints do not reveal sensitive data.


No support for Django 1.9

When using in Django 1.9 one can get:
ImportError: cannot import name importlib
django.utils.importlib  was deprecated for Django 1.9

This has been fixed in master, and will be in the next release


[WFCORE-3239] CLIWrapper does not allow for use in multinode tests

https://issues.jboss.org/browse/WFCORE-3239

Core - Full Integration Build 7 outcome was FAILURE using a merge of d814b553cbcabefa3402f2919cde08a71b136d2f
Summary: Tests passed: 3900, ignored: 106; exit code 1 (new) Build time: 01:13:28


Display issue on project website

Hi, I have some issue to read project website : many font character are not available in my locale (en_US) and with my fontset, as you can see below

This website is currently in Chinese. English documentation will be available in the first stable version. For now, please follow the README.
Should you have any problems, feel free to open an issue or comment below.


Make React binding in zero cost

https://github.com/rescript-lang/rescript-react/issues/76

Maybe ignore bs.js from version control as before?

Maybe ignore bs.js from version control as before?

I think it's good to keep .bs.js in source control in this project so that we notice unexpected changes there (like things suddenly being not zero cost anymore) more easily.

Also, good to see this change in the compiler in this PR:
/* react Not a pure module */

->
/* No side effect */

👍

Also, good to see this change in the compiler output in this PR:
/* react Not a pure module */

->
/* No side effect */

(and nothing being exported anymore but the empty submodules) 👍

Indeed!


Publish Nuget package on nuget.org

You've published this with an MIT license so I understand I can just copy the code but it would also be nice if I could just include your code in mine thru NuGet.
I'm willing to help out if you're interested and want any help.

Yeah, please feel free to include it in your NuGet package.

@renmengye Sorry for not being clearer, but I'd like to be able to use a NuGet package for this project (with you credited as the author). I don't think I can create my own NuGet package and publish it as you. I'll gladly submit a PR that you can merge into this repo with the relevant files to create the NuGet package and publish it to nuget.org.
Or, if you're not interested in any of that, I'll just create my own NuGet package and clearly indicate that the code used is from this repo (or my fork of it).

Could you submit a PR for the NuGet please? Great thanks!

@renmengye Will do!

Any chance this lib will be on NuGet?


pipenv: 2022.11.25 -> 2023.2.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pipenv is: "Python Development Workflow for Humans"
meta.homepage for pipenv is: ""
meta.changelog for pipenv is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2022.11.30 with grep in /nix/store/qiggckrafnfhcg3ir5b2y0hd1sk0kpcc-pipenv-2022.11.30
found 2022.11.30 in filename of file in /nix/store/qiggckrafnfhcg3ir5b2y0hd1sk0kpcc-pipenv-2022.11.30

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pipenv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qiggckrafnfhcg3ir5b2y0hd1sk0kpcc-pipenv-2022.11.30 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pipenv https://github.com/r-ryantm/nixpkgs/archive/e513ebbf74fb562ca8cfdf2af2ffc284f1badea7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qiggckrafnfhcg3ir5b2y0hd1sk0kpcc-pipenv-2022.11.30
ls -la /nix/store/qiggckrafnfhcg3ir5b2y0hd1sk0kpcc-pipenv-2022.11.30/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pipenv

Maintainer pings
cc @berdario for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pipenv is: "Python Development Workflow for Humans"
meta.homepage for pipenv is: ""
meta.changelog for pipenv is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2022.12.17 with grep in /nix/store/ws6q4ykfxr6v3cl3zy1ggv25pmlxzlvb-pipenv-2022.12.17
found 2022.12.17 in filename of file in /nix/store/ws6q4ykfxr6v3cl3zy1ggv25pmlxzlvb-pipenv-2022.12.17

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pipenv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ws6q4ykfxr6v3cl3zy1ggv25pmlxzlvb-pipenv-2022.12.17 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pipenv https://github.com/r-ryantm/nixpkgs/archive/5fe67f8ac63aa8bbfef2f855fe90462fbfe9ed01.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ws6q4ykfxr6v3cl3zy1ggv25pmlxzlvb-pipenv-2022.12.17
ls -la /nix/store/ws6q4ykfxr6v3cl3zy1ggv25pmlxzlvb-pipenv-2022.12.17/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pipenv

Maintainer pings
cc @berdario for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pipenv is: "Python Development Workflow for Humans"
meta.homepage for pipenv is: ""
meta.changelog for pipenv is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2022.12.19 with grep in /nix/store/63bikmsjn22c20wcrc0kbr00m54q6r1v-pipenv-2022.12.19
found 2022.12.19 in filename of file in /nix/store/63bikmsjn22c20wcrc0kbr00m54q6r1v-pipenv-2022.12.19

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pipenv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/63bikmsjn22c20wcrc0kbr00m54q6r1v-pipenv-2022.12.19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pipenv https://github.com/r-ryantm/nixpkgs/archive/08e7253fd6f47a352454e31aead479642bb04a5d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/63bikmsjn22c20wcrc0kbr00m54q6r1v-pipenv-2022.12.19
ls -la /nix/store/63bikmsjn22c20wcrc0kbr00m54q6r1v-pipenv-2022.12.19/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pipenv

Maintainer pings
cc @berdario for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pipenv is: Python Development Workflow for Humans
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2023.2.4 with grep in /nix/store/cacxc0i6lz9547ldvxjzdif672qmai37-pipenv-2023.2.4
found 2023.2.4 in filename of file in /nix/store/cacxc0i6lz9547ldvxjzdif672qmai37-pipenv-2023.2.4

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pipenv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cacxc0i6lz9547ldvxjzdif672qmai37-pipenv-2023.2.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pipenv https://github.com/r-ryantm/nixpkgs/archive/3299517e6b24e3767496797ad63d41049c4ceff4.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cacxc0i6lz9547ldvxjzdif672qmai37-pipenv-2023.2.4
ls -la /nix/store/cacxc0i6lz9547ldvxjzdif672qmai37-pipenv-2023.2.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pipenv

Maintainer pings
cc @berdario for testing.


[Sidenav] Need Fixed expanded (open) state

Summary
Building Insights development team needs the component to implement both 2 open states, documented in the Watson IoT PAL -

Flexible expanded (open) state - implemented in current component
Fixed expanded (open) state - still to be implemented.

Additional context
Continuing from https://github.com/IBM/carbon-addons-iot-react/issues/661.

Current behaviour

Go to Storybook link - SideNav Component.
Click on top-left hamburger menu.
Side menu opens in Flexible expanded (open) state as an overlay over the main content

Desired behaviour

Click on top-left hamburger menu.
Side menu changes to Fixed expanded (open) state and displaces the main content area to the right.

Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?

Required by the end of November for next product release.

NB: The core contributors will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!
Available extra resources
What resources do you have to assist this effort?
Possibly one member of the development team, depending on timelines.
Carbon Add-ons for Watson IoT is a collaborative system. We encourage teams to build components and submit them for integration.
Same as this one internally in Maximo Asset Monitor:
https://github.ibm.com/wiotp/monitoring-dashboard/issues/785

Specific timeline issues / requests
As we are starting with the implementation from next week, so please note that requested feature is required before 22-Nov-2019.

:tada: This issue has been resolved in version 2.53.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


WIP: Support CUDA 12

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #32.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Where are my CI configs... lol Anyway, I'll resume tomorrow...

Note to self: I expect to see the CI fails due to missing CuPy for CUDA 12, which is ongoing (https://github.com/conda-forge/cupy-feedstock/pull/199).

Note: We need cuda-nvcc_{{ target_platform }} because of the crt headers (https://github.com/conda-forge/cuda-nvcc-feedstock/issues/8).

All green! @conda-forge/cuquantum Happy to walk you through the changes in this PR offline, since a lot of things are new. We now support both CUDA 11 & 12 in the same conda recipe. Please take a look and let me know if you have any questions. But I'll proceed to merge now.


Example page not working

I've been having the Example page open for some days now checking everything and today the all examples suddenly stopped working.
I've tried it on another browser but it still doesn't work.
I can see the following error in the console:
Uncaught TypeError: Cannot read property 'months' of undefined                           Datepicker.vue:229
(Edit: I'm talking about this page: http://yuche.github.io/vue-strap/)

Clean cache or something, that error was only yesterday because I moved the translations, was corrected last night.

@wffranco I tried to clean cache, i tried in incognito mode (no cookies, cache, etc..) and tried in another browser and it still doesn't work.

Can confirm same error as @VitruxPT, cleared cache and tried via incognito as well

@wffranco I can confirm it too, the examples aren't working.

I separate the language translations yesterday, so maybe you got that error while I was fixing it.

@wffranco I'm getting the error now, not yesterday. It still doesn't work

Same here, my console.log show a error too
Datepicker.vue:296 Uncaught TypeError: Cannot read property 'months' of undefined

I fix my cloned vue-strap locally.

npm install style-loader ( Error happening trying to find this module );
And a dirty try catch in datepicker error;

This line bellow.
return this.text.months[date.getMonth()]
The .text is undefine.

Well, removed the try catch mentioned above and the problem is with translations(this.lang), inside vue-strap-lang.js i change the "en" key to "en-US"
'en-US': {
                daysOfWeek: ['Su', 'Mo', 'Tu', 'We', 'Th', 'Fr', 'Sa'],
                limit: 'Limit reached ({{limit}} items max).',
                loading: 'Loading...',
                minLength: 'Min. Length',
                months: [
                    'January', 'February', 'March', 'April', 'May', 'June',
                    'July', 'August', 'September', 'October', 'November', 'December'
                ],
                notSelected: 'Nothing Selected',
                required: 'Required',
                search: 'Search'
            }

and
var tr = {};
        for (var i in l['en-US']) {
            tr[i] = l[lang][i] || l['en-US'][i];
        }
        return tr;

all components working also the datepicker.

@VitruxPT like I said when I edit, I test in some browsers and all fine (with my default language), just got the error in firefox, so I detect the error later.
Problem fixed. Sorry for the delay, solving other bugs and had some problems merging branches.
Greeting.


ARROW-13606: [R] Actually disable LTO

@github-actions crossbow submit test-r-rhub-debian-gcc-devel-lto-latest

@github-actions crossbow submit test-r-ubuntu-21.04 test-r-gcc-11

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit conda--r4

Not sure why the conda builds didn't kick off, but if my last fix didn't fix them, I'll catch them after the nightlies go.