Add vital life saver option to disable completely dangerous webassembly not just the V8 engine

Webassembly may make web browsers faster but webassembly is the most important security threat to web browsers despite security paths, and I read news articles saying crypto mining miners cryoptp jacksing use websassembly to steal our cpu gpu power and that cryto mining jacking techniques have evolved to use only little cpu gpu resource to not arouse suspicion .....
i disabled the webassembly optimizer engine V8:
catsxp://settings/content/v8
but I note with sorrow that webassembly is not completely disabled by going to this site to test if the deactivation of the dangerous webassembly is effective:
https://regex101.com/
if webassembly does not work, the site https://regex101.com/ must display me message webseembly is disabled .....
i tried these flags:
--js-flags=--noexpose_wasm --js-flags=--jitless --disable-features=WebAssembly,AsmJsToWebAssembly
--js-flags='--jitless'
but the problem, I put desktop shortcuts of many streaming websites in a folder to organize and save them, the problem the command line doesn't work all time permanently with all sites, i.e. if the web browser is started from a desktop url shortcut of a website, the command line doesn't work anymore, I noticed it when trying to disable webassembly, if the browser starup from a desktop website's url shortcut, the command line of chromium is no longer effective:
in addition many chromiumm command lines are becoming obsolete and there is no clear documentation on the effective command lines and I would like an effective and permanent solution to guarantee my safety against the dangerous web assembly please,
webassembly is dangerous and can cause crypto currency mining which can ruin us and cause harm to ecology and it is the main threat on the internet, the pirates use sophisticated techniques like using a very small power of your processor without realizing it and without clicking on any link despite your web browser is up to date,
and Webassembly Technology (WASM) is enabled by default in web browsers but
WebAssembly may be used, just like JavaScript, to “steal” processing power instead of data. In 2019, an analysis of 150 different Wasm modules found out that about 32% of them were used for cryptocurrency-mining.
https://training.linuxfoundation.org/blog/webassembly-security-now-and-in-the-future/
Though Wasm has been around for a few years, it rose to prominence more recently when it was used for cryptocurrency mining in browsers. This opened a Pandora's box of potential malicious uses of Wasm.
https://www.virusbulletin.com/virusbulletin/2018/10/dark-side-webassembly/
So I think it's necessary for the average user who to have peaceful mind that the resources of his computer are not stolen please!
we hope Mr Alex @Alex313031 will help Mr Shane to add this essential life saver function important for the money saving ecologist, thank you!

It is recommended that developers design it to allow WebAssembly to be enabled for specific websites. Once disabled, certain websites may not function properly.

It is recommended that developers design it to allow WebAssembly to be enabled for specific websites, as some websites and browser extensions may rely on WebAssembly. Directly disabling it could render them non-functional.

@minusmulticoloredper Thanks for advise :) 👍 but i watch many anime from streamng websites that may havy nasty ads crypto miners mining crypto jacking, we can choose  browser  just for watching only streaming videos for safe , another for mail.....webassembly is the danger in this world, i don't need the benefits of webassembly if i can be hacked or my weak cpu power stolen by cryptp miners in eventual streaming websites

i disabled webassembly in frefox for a long time  and i don't have any probelm, we can live without webassembly

I use the NoScript and UBO extension. This gives you a wider choice of tools: exactly what to allow on a web page and what to disable.
I allow scripts to run when really necessary. Scripts from advertising domains and other unnecessary sites are simply cut off.
This is of course troublesome, but it is worth it, both from a security point of view and for the sake of saving resources on weak equipment.

@trimechee
By the way, your Eee PC's CPU should not be susceptible to Meltdown/Spectre vulnerabilities. So, you can worry a little less about security than other users of old hardware
;)


Take/show build information from the buildinfo package

Go 1.18 includes debug/buildinfo which can be useful.

Turns out that debug/buildinfo offers information that we don't want to include in our version message (buildmode, compiler, cgo flags and GO-related flags). When it comes to VCS info offered by debyg/buildinfo, it doesn't help a lot as far because we already have proper git version set in our version and it doesn't help in case if the repo is built outside of the version controle system.
So there's nothing useful we can take from debug/buildinfo at the curent moment.


Design: Initial landing page after Dataverse

Dataset/Dataverse/File Description
Terms of Use
Consult @TaniaSchlatter

close for #88 and #83

close for #88 and #83


Enable PCA955x IO expander in kernel config

Amber has a PCA955 IO expander module. This IC has support in linux kernel, so I think we just need to enable: GPIO_PCA953X and GPIO_PCA953X_IRQ
config GPIO_PCA953X
	tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
	depends on I2C
	help
	  Say yes here to provide access to several register-oriented
	  SMBus I/O expanders, made mostly by NXP or TI.  Compatible
	  models include:

	  4 bits:	pca9536, pca9537

	  8 bits:	max7310, pca9534, pca9538, pca9554, pca9557,
	  		tca6408

	  16 bits:	pca9535, pca9539, pca9555, tca6416

config GPIO_PCA953X_IRQ
	bool "Interrupt controller support for PCA953x"
	depends on GPIO_PCA953X=y
	help
	  Say yes here to enable the pca953x to be used as an interrupt
	  controller. It requires the driver to be built in the kernel.

Fixed by https://github.com/resin-os/resin-raspberrypi/pull/136

Reopening as the PR supposed to fix this had some typos.
Should be now fixed by https://github.com/resin-os/resin-raspberrypi/pull/137

Closing this item as https://github.com/resin-os/resin-raspberrypi/pull/137 was merged


Inspect

Codecov Report
Patch coverage has no change and project coverage change: +16.66 :tada:

Comparison is base (d604cce) 50.00% compared to head (c6049dd) 66.66%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main       #2       +/-   ##
===========================================
+ Coverage   50.00%   66.66%   +16.66%
===========================================
  Files           1        1
  Lines          12       15        +3
===========================================
+ Hits            6       10        +4
+ Misses          6        5        -1

Impacted Files
Coverage Δ

greeting/greeting.go
66.66% <0.00%> (+16.66%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Calling source graph with ?visible=1000000 ends in 500

Using ?visible=1000000 causes 500 on sourcegraph.com, e.g.:
https://sourcegraph.com/crates/openapiv3/-/compare/v1.0.2...v1.0.3?visible=1000000

vs
https://sourcegraph.com/crates/openapiv3/-/compare/v1.0.2...v1.0.3

This specifically relates to https://github.com/search?q=repo%3Amozilla%2Fcargo-vet 1000000&type=code
I dont know why that changed on sourcegraph, but either removing that number completely or reducing it should help

7000 works, 7500 no

Thanks @cemoktra looking into it.

This now ends in 400 but still not working

@cemoktra @bholley unfortunately, we had to put the visible limit back. Bots have been abusing the ?visible=1000000 query string which drove up costs and slowed the service down for others.

@jdorfman can you tell the limit? I can prepare an according MR then

@cemoktra 5 e.g. https://sourcegraph.com/crates/openapiv3/-/compare/v1.0.2...v1.0.3?visible=5

No I mean the maximum.


Switch to miniz_oxide

This also fixes a few instances where decoding should fail. The theory behind these was realized because miniz_oxide forces us to manually flush the decompression at the end of consecutive IDAT chunks which in turns requires us to keep track of this. Don't merge until we have some test cases that ensure this behaviour will not regress. Also, I want to run some perf results and publish them here.


Add Contribution guide and Issue/PR templates

Part 3 of 3
https://github.com/spatialos/gdk-for-unity/pull/571
https://github.com/spatialos/gdk-for-unity-fps-starter-project/pull/54
https://github.com/spatialos/gdk-for-unity-blank-project/pull/3


Removed automation components from beta logic app

Fixed an issue where the beta logic app would not deploy as this was still using automation components to check for the existence of a SharePoint site.
I have updated the ARM template to use the CheckSiteExists logic app in the same way the ProcessTeamRequest 1.0 logic app does.

@abbodh this has been tested today, please approve


The Grid documentation is not easily found

It's not in the menus, and not easily found anywhere else

This also effects "elevation"


[$500] Search - Search results displays recent room but not showing recent message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.95-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:

Launch app
Tap on any admin room
Send a message
Navigate to LHN
Tap on search icon

Expected Result:
When user send message from admin room, and check search results, the admin room is shown on top and similarly message sent must also be shown.
Actual Result:
When user send message from admin room, and check search results, the admin room is shown on top but message sent is not displayed.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/115492554/798a72a8-ded6-49e8-ac69-50703d9bb728

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e4dca8693705ba46
Upwork Job ID:<PHONE_NUMBER>934598144
Last Price Increase: 2023-11-17

Proposal
Please re-state the problem that we are trying to solve in this issue.
Policy's Admins room doesn't show the last message as the secondary label
What is the root cause of that problem?
we force the seconday label to be shown here:
https://github.com/Expensify/App/blob/5d45f0f6c86e97d4ae58ac167b6c162a610b817c/src/libs/OptionsListUtils.js#L1192-L1197
What changes do you think we should make in order to solve the problem?
remove the isPolicyChatAdmin condition and leave this behavior for if we want for not own policies as well or we can make it as false for all cases :
    allReportOptions.push(
            createOption(accountIDs, personalDetails, report, reportActions, {
                showChatPreviewLine,
                forcePolicyNamePreview: isPolicyExpenseChat ? isSearchingSomeonesPolicyExpenseChat : forcePolicyNamePreview,
            }),
        );

OR
    allReportOptions.push(
            createOption(accountIDs, personalDetails, report, reportActions, {
                showChatPreviewLine,
                forcePolicyNamePreview: false
            }),
        );

What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

@anmurali Can we check internally if this is intentional or not? Or a bug?

Just back from weekend. We have to check internally on the expectency with the above

@anmurali Can we check internally if this is intentional or not? Or a bug?

Gentle Ping @anmurali

In general the rooms don't show a preview of latest message. So for now, this is by design.


error building sgx_ucrypto

I'm trying to use sgx_ucrypto::SgxEccHandle to verify a signature
reproduce with this code
When I do
cargo +nightly-2019-11-25 build

I get the following errors:
error[E0432]: unresolved imports `libc::size_t`, `libc::c_int`, `libc::c_void`
 --> /home/abrenzikofer/.cargo/git/checkouts/teaclave-sgx-sdk-be25c2ad2f03718d/93c76de/sgx_ucrypto/src/util.rs:1:12
  |
1 | use libc::{size_t, c_int, c_void};
  |            ^^^^^^  ^^^^^  ^^^^^^ no `c_void` in the root
  |            |       |
  |            |       no `c_int` in the root
  |            no `size_t` in the root

error[E0432]: unresolved imports `libc::EINVAL`, `libc::E2BIG`, `libc::EOVERFLOW`
 --> /home/abrenzikofer/.cargo/git/checkouts/teaclave-sgx-sdk-be25c2ad2f03718d/93c76de/sgx_ucrypto/src/util.rs:2:12
  |
2 | use libc::{EINVAL, E2BIG, EOVERFLOW};
  |            ^^^^^^  ^^^^^  ^^^^^^^^^ no `EOVERFLOW` in the root
  |            |       |
  |            |       no `E2BIG` in the root
  |            no `EINVAL` in the root

error[E0432]: unresolved import `libc::memset`
 --> /home/abrenzikofer/.cargo/git/checkouts/teaclave-sgx-sdk-be25c2ad2f03718d/93c76de/sgx_ucrypto/src/util.rs:3:5
  |
3 | use libc::memset;
  |     ^^^^^^^^^^^^ no `memset` in the root

error[E0599]: no function or associated item named `new` found for type `rdrand::RdRand` in the current scope
  --> /home/abrenzikofer/.cargo/git/checkouts/teaclave-sgx-sdk-be25c2ad2f03718d/93c76de/sgx_ucrypto/src/util.rs:54:35
   |
54 |     let mut rnd = rdrand::RdRand::new().unwrap();
   |                                   ^^^ function or associated item not found in `rdrand::RdRand`

error: aborting due to 4 previous errors

building sgx_ucrypto directly in the teaclave repo works.

the problem occurred because I was accidentalley building sgx_ucrypto for the target wasm32-unknown-unkown too. Had to fix the toml to make this dependency optional for std use case


Corrected Grammatical Errors.

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #12300

Description
Corrected the grammar changes as pointed out in the issue no #12300

@91aman thanks for the PR! Almost there, just need to change the line I've pointed out just a little bit. Let us know in the contributor's chat room if you need any help.

@erictleung I have done the changes as requested by you. Do let me know if any others changes need to be done.

@erictleung Thanks. what are next steps I need to do to get this PR merged?

@91aman ah I was waiting for possibly others to take a look at this PR as well. But this kind of change should be safe to merge. I'll go ahead and merge it. Thanks for contributing! 🎉

@erictleung Awesome thanks :)


Reduce bit operations for header validation

While reading through https://github.com/line/armeria/commit/b597f7a865a527a84ee3d6937075cfbb4470ed20 to understand it, I had to look up what the ~ operator does 😅  I think it's very uncommonly used and better to avoid if it's not necessary to improve readability. I found that because we don't need to presize the BitSet (it's a static final) and BitSet.get efficiently checks characters outside the range of the BitSet, it doesn't seem necessary and we can make the code more readable. What do you think?

How about keeping the & ...MASK check? Most characters will hit that branch and we're gonna same some cycles. We could define the masks without ~, like plain 0xFFF0.

I think the difference in operations is just one, the initial < 0 check that BitSet.get does (otherwise just a shift and compare, similar to mask and compare). But if it's worth it, how about
private static final byte LAST_PROHIBITED_NAME_CHAR = (byte) PROHIBITED_NAME_CHARS.size() - 1;
if (value > LAST_PROHIBITED_NAME_CHAR)

It's a tiny bit less precise than the mask for prohibited names (two additional characters get through > and ?) but keeps the logic more self-contained (no need to have confidence the mask matches the bitset, it's all self-computed).


Remove unnecessary line breaks

log: Remove unnecessary line breaks
log.Errorf is supposed to contain line break by default. This patch
removes the unnecessary line break.

Here is the current log message (without this patch):
time="2017-05-03T11:14:48Z" level=error msg="Error extracting userid metadata from context: context.Background.WithCancel.WithCancel.WithCancel\n"

LGTM


(GH-742) Add empty item template to local source

@punker76 can you please tell me why the empty item template isn't working on the local source?
I have tried to copy/paste your code, but there must be a bit more to it, and hoping that you can help :-)

@gep13 The empty results info should now work for tile and datagrid view.

@gep13 I improved a little bit more here. The trigger for the empty template looks now also to the IsLoaded property to prevent showing it if the user refresh packages. The other one is the 250ms delay on search text box, so that the search is done after this and not directly on every user input.

@punker76 quick question... Does this:

The other one is the 250ms delay on search text box, so that the search is done after this and not directly on every user input.

Take into account the UseDelayedSearch feature?

@gep13 The UseDelayedSearch is currently only for the remote service, because of long running task. IMO the local view doesn’t need that, because the search goes directly to the CollectionView and is faster.

@punker76 that is a great point!  I think we need to update the description to reflect that this only applies to the remote sources, but I can do that separately.


Metrics hard to enable when run as standalone mode

When Gobblin is launched as standalone, SchedulerDaemon starts all Gobblin services (including Gobblin metrics) using the system and custom configurations, but not the job configurations. Usually, users will specify their metrics config in the job configuration, but this means that for standalone, those configurations will be skipped.
Users must specify metrics configurations using the --conffile flag. This needs to be fixed or at least documented.

When launching in stand-alone mode, users can just add the metrics configs to conf/gobblin-standalone.properties, there is no need to use --conffile.
Given the current way Gobblin Metrics works, I think it makes more sense for metrics to be placed in the .properties file rather than the .job files, and I think we should change the documentation to reflect that. This issue documents the problems with Gobblin Metrics before the Metrics-as-a-Service feature was added: https://github.com/linkedin/gobblin/issues/792


Logging driver should receive same file in start/stop request

Cherry-picked from: moby/moby#33583
Signed-off-by: Peter Bücker<EMAIL_ADDRESS>(cherry picked from commit e908e1a357b435d7fab497d51cdd3e58458a0590)
Signed-off-by: Eli Uriegas<EMAIL_ADDRESS>

LGTM


Ankur/quicktemplates

Changing CmdLets for nested environment. Please only deploy this to prod once all the old environments are ported.

Can one of the admins verify this patch?


Kotlin extension should be populated with an earlier api target

The Kotlin extension is compiled against 1.9.x and by default can only be used by Kotlin 1.9 and above.
Unless the extension is using language features that are only accessible in 1.9.x, I recommend setting the apiVersion on the kotlin compiler, which will allow it to generate code with earlier metadata (recommend 1.6.x) and be usable for users with earlier versions of Kotlin.
See https://kotlinlang.org/docs/maven.html#attributes-specific-to-jvm, specifically languageVersion.
Category (place an x in each of the [ ])

[ ] bolt (Bolt for Java)
[ ] bolt-{sub modules} (Bolt for Java - optional modules)
[ ] slack-api-client (Slack API Clients)
[ ] slack-api-model (Slack API Data Models)
[X] slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
[ ] slack-app-backend (The primitive layer of Bolt for Java)

Thanks for the suggestion! Indeed, this could be improved for Kotlin users.

Thanks for the suggestion! Indeed, this could be improved for Kotlin users.

@seratch I submitted a PR. No code changes were required to maintain language and API compat with Kotlin 1.6.

(BTW, the kotlin label on this repo is spelled incorrectly)

(BTW, the kotlin label on this repo is spelled incorrectly)

🤦 Oops, thanks! Fixed.


Model format for exporting xgboost models to disk

https://github.com/dmlc/xgboost/blob/a4f5c862760029c24a5ba29b2a2ef4787058856c/python-package/xgboost/sklearn.py#L263
This warning here for save_model recommends using joblib for python and using the save_model only for a non-python binding of xgboost. If my use case was only restricted to using my model within different python environments only, is there any reason why joblib is recommended over xgboost's save and load other than the aforementioned reason of losing feature names?
I just want to understand the risks of joblib vs xgboost for deploying xgboost models to a different python environment to the one it was built in.

The feature names and types is saved in Python due to possible utf 8 string.  I think it's legacy and can be easily resolved by saving it in cpp, as I couldn't think of a reason why do we care about encodings.  We don't search nor query the encoding dependent string length.  @hcho3

Other than that are there any other caveats of reading in a pickle file vs xgboost binary from a model performance/accuracy standpoint? Fort python, is there a reason for recommending to go with Joblib instead of xgboost binary? In other words does the format we choose impact the predictions at all? Sorry if this is a dumb question but I couldn't find anything in the documentation that states one way or the other.

@akhildp Would you like to take a look at the saving_model.rst in https://github.com/dmlc/xgboost/pull/4732 ?  Before that PR, there's no different other than feature_names and feature_types.  But after that PR there will be.

Also this one https://github.com/dmlc/xgboost/issues/4639

Thanks for pointing this. These are really exciting changes. Is there an ETA for when these PRs may be merged and when 1.0.0 will be out?

My plan is to solve it first and then start bug squashing.  That PR fixes lots of issues especially for dask interface.  But it's also huge so I'm splitting it into smaller parts other can review.  You are more than welcomed to help the process.  There are already a few PRs I made with changes extracted from JSON PR.  Reviews are needed.


[stable/minio] Fix missing colon on StatefulSet

/assign @nitisht

Thanks for the PR @Dijir could you fix the failures pls


apply-details-marker settings is confusing

The setting to show the default marker for a details element reads backward to me.
$apply-details-marker: false means to show the default marker
$apply-details-marker: true means hide it.
I think these should be reversed for clarity. This will need to wait until V3.

Thanks and yes it is confusing. It'll get fixed in V3 so I'll close this as it's logged here.


AVRO-2975: Enable PHP linting and fix its errors

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"

https://issues.apache.org/jira/browse/AVRO-2975
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No additional unit test, since this PR fixes the test itself. I ran ./build.sh clean test in the Docker container locally and confirmed it succeeded.
Commits

[x] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

Thanks for this improvement.  Travis isn't running the CI so I ran a full build on my local machine.


BUG: Webpack freezes at "91% additional asset processing"

Is anyone else experiencing this?
Here's a related issue.
A temporarily solution i found was to comment the devtool webpack property in both production webpack configs.
Solution: try using uglifyjs or commenting babili in the webpack config

This happened to me before when I was trying to get monaco-editor to work with my project. Can't reproduce it now, though. I'll see if I can reproduce it later.

@uppe-r what are your electron, npm, node, and electron-builder versions?

I still can't reproduce it, but at the time I had it failing my electron was on 1.6.2, Node on v6 (probably) and electron-builder on 16.6.0

I am currently experiencing this issue and have been for a little while. Since I was just running dev builds I was manually exiting the process with a "ctrl-c" - I was then able to run the current state with npm run dev just fine. Now that I am trying to package - this has become a bigger issue for me. I will try the devtool: 'eval' approach and see where that leads.

I tried adding the devtool: 'eval'  to my config, it no longer hangs but when the package is done i get this error

Comment the devtool: eval line.

I ended up commenting Babili, seems like changing devtool to eval is not the best (production-wise), even though it worked for me.

I hit this awhile ago & commented-out babili. At the time I remember assuming it had something to do with babel relay but I don't think I ever pinpointed the cause.
in my case it's just the renderer build that's broken, if that's at all helpful

quick update:  adding --max-old-space-size=4076 to the build-renderer command seems to make babili work (albeit after a long hang @ 91%)
eg
"build-renderer": "cross-env NODE_ENV=production node --max-old-space-size=4076 --trace-warnings ...

Do you add that to the root webpack config object?
Like so?
module.exports = {
  "build-renderer": "cross-env NODE_ENV=production node --max-old-space-size=4076 --trace-warnings",
  devtool: 'eval',

Below settings helped me to reduce the heap memory since it will not include the sourceMap file.
devtool: false, // Webpack.

new webpack.optimize.UglifyJsPlugin({
   sourceMap: shouldUseSourceMap
}),

or below code will help for latest webpack uglify plugin.
> npm install uglifyjs-webpack-plugin --save-dev

// conf.js
const UglifyJsPlugin = require('uglifyjs-webpack-plugin');
module.exports = {
  optimization: {
    minimizer: [
      new UglifyJsPlugin({
        sourceMap: true,
      }),
    ],
  },
};

If this still not help to fix the problem. below command helps to increase heap memory and answer link to know more about heap memory is below as well.
node --max-old-space-size=16000 scripts/build.js

https://stackoverflow.com/a/57480923/1533666


Combined dependency upgrades.

@wlonk I don't know you feel generally about having Dependabot open PRs for upgrading sub-dependencies, but I figured it doesn't hurt doing this every so often.

@wlonk I also notice we're using postgres v11.8 on Heroku, but v10.6 locally and on CI -- I'm guessing we should sync those?

@jgerigmeyer looks like our production metecho apps are using postgres 12.3


Problem with Download-OfficeProPlusChannels

Form 14-Jun-17, the script fails to download the updates.
The error seems to be on the line 756, where is called "expand" command.
Here is the error that you get by running the script:
Get-Content : Cannot find path 'C:\Users\ADMIN~1.GAL\AppData\Local\Temp\ReleaseHistory.xml' because it does not exist.
At C:\OfficeUpdates\ToolKit\Download-OfficeProPlusChannels.ps1:759 char:23
+         [xml]$vdxml = Get-Content $baseCabFileName2

Original line 756:
expand $destination2 "$env:TEMP\ReleaseHistory.xml" -f:"ReleaseHistory.xml" | Out-Null
Fixed line 756:
 expand $destination2 "$env:TEMP" -f:"ReleaseHistory.xml" | Out-Null

@gallama1  are you still encountering this issue?  I can't seem to be able to reproduce it.


How many shots are used for evaluation?

Do you use in-context learning the prompt?
How many examples do you use for training? 0-shot, 1-shot, or 2-shot?

Sorry. I don't understand your question. Can you define "shots" more precisely?

Sorry. I don't understand your question. Can you define "shots" more precisely?

Do you use in-context learning the prompt?
How many examples do you use for training? 0-shot, 1-shot, or 2-shot?

ANy update? @ganler

If you are asking about code generation during evaluation, the prompt is provided by the benchmark. Those for instruction-tuned model might include a bit more instruction. Check: https://github.com/evalplus/evalplus/blob/master/codegen/model.py
If you are asking about how we prompt to generate test inputs, check https://github.com/evalplus/evalplus/blob/master/evalplus/gen/chatgpt_gen.py

If you are asking about code generation during evaluation, the prompt is provided by the benchmark. Those for instruction-tuned model might include a bit more instruction. Check: https://github.com/evalplus/evalplus/blob/master/codegen/model.py
If you are asking about how we prompt to generate test inputs, check https://github.com/evalplus/evalplus/blob/master/evalplus/gen/chatgpt_gen.py

Thanks for your quick reply. I am more interested in the evaluation. The code is a bit long, where to look at?
How many shots do you use during the benchmark evaluation?

So if you look at the prompts of humaneval and mbpp, we use the exactly same prompt. I don't understand what you mean by x-shots since the prompt is mostly fixed.

So if you look at the prompts of humaneval and mbpp, we use the exactly same prompt. I don't understand what you mean by x-shots since the prompt is already fixed and you don't have space to tune number of few shots.

Ok, I do not find any description of what you mention here in the paper. Thus, both are zero-shot prompts.

I'm also curious about the effect of in-context learning in code tasks. Are there any code libraries that implement this feature?

Live code bench uses few shot FYI.  But in practice of program synthesis/completion users won't have few shot examples. 😃

Live code bench uses few shot FYI. But in practice of program synthesis/completion users won't have few shot examples. 😃

thx(


PayPal APP Retrieves Incorrect PayPal E-Mail Address and Primary E-Mail Address

PayPal APP's 'Retrieve Live Credentials' function works mostly correctly except for the PayPal E-Mail Address.  The API username is being filled into both PayPal E-Mail Address and Primary E-Mail Address fields.

Thanks for the report. Could you provide an anonymized format of your API username? In the form of:
xxxxxx_api1.xxxxxx.com

My API username is in the form of xxxxxxxxxxx_api3.xxxxxxxx.com.tw


Differentiating between languages in reference selector

Hi,
We've just started localising a lot of our Sanity documents, and our content authors have come across an issue when they try to link to another document, that it's impossible at first glance to tell which language version of the document they are reference. They can click edit to see which version it is, but it can be time consuming.
Is there a way to make the language appear in the reference selector? I imagine it would involve making some sort of custom component that inherits Sanity's ReferenceInput?

👀 Interested in this one as well


Enhancement - Add support for env and ansible vars in inventory validation

When validating the inventory files with the plugin, ansible and environment variables are not evaluated. This causes the validation to fail. When executing the script skipping the validation, the variables are properly evaluated by ansible and doesn't cause any issue.

Add support for the plugin to evaluate the variables for validation

Resolved with PR https://github.com/IBM/zmodstack-solutions/pull/2


Increase default thread pool sizes

Avoid situation described in #529 with default parameters.

Coverage remained the same at 88.795% when pulling d0f4e4b26b9340523e7047aa1e3be10f992dc9ac on tgianos:increaseDefaultThreadPools into 00caca6310ee7a7d6b66a7a9bc4bb585080ad8cb on Netflix:3.0.x.


Background image addon add wrong class name.

This is a very great plugins.
Thank you.
I found a problem.
I used Background image addon.
This add wrong class name.
Befor load : none
After load : lazy-hidden
It has occurred the same thing in the sample.
http://ressio.github.io/lazy-load-xt/demo/bg.htm

The same thing was written.
Sorry...


Segmentation fault when multithreaded

I'm seeing a reproducible segmentation fault when running Racon with 6 or more threads. I don't see this segmentation fault when run with with 5 or fewer threads.
❯❯❯ racon -t6 foo.fq.gz foo.miniasm.paf.gz foo.miniasm.fa
[racon::Polisher::initialize] loaded target sequences
[racon::Polisher::initialize] loaded sequences
[racon::Polisher::initialize] loaded batch of overlaps
[racon::Polisher::initialize] aligned overlap 11/11
Segmentation fault (core dumped)
❯❯❯ racon -t5 foo.fq.gz foo.miniasm.paf.gz foo.miniasm.fa | wc
[racon::Polisher::initialize] loaded target sequences
[racon::Polisher::initialize] loaded sequences
[racon::Polisher::initialize] loaded batch of overlaps
[racon::Polisher::initialize] aligned overlap 11/11
[racon::Polisher::initialize] transformed data into windows
[racon::Polisher::polish] generated consensus for window 11291/11291
      2       2  560217

❯❯❯ gdb racon core.93311
(gdb) bt
#0  0x00000000004b6412 in std::unique_ptr<racon::Window, std::default_delete<racon::Window> >::get() const ()
#1  0x00000000004b257c in std::unique_ptr<racon::Window, std::default_delete<racon::Window> >::operator->() const ()
#2  0x00000000004a36c4 in racon::Polisher::initialize() ()
#3  0x000000000049e0d5 in main ()
(gdb) x/i $pc
=> 0x4b6412 <_ZNKSt10unique_ptrIN5racon6WindowESt14default_deleteIS1_EE3getEv+24>:	mov    (%rax),%rax
(gdb) p/x $rax
$1 = 0x8025fbee8

Can you provide the data that is causing the error? I doubt that it has to do with threading.

I just noticed that the successful run only output a single polished unitig rather than the expected 11 unitigs.

Woops. When I ran the minimap2 alignments, I swapped the query and target. That's clearly pilot error. It'd be better of course if Racon didn't segafult. =)

That should be fixed in the latest version (1.1.1) but I did not yet released it. Try it please :)

Racon 1.1.1 fixes the segfault. Thanks again, Robert!
1.1.0
[racon::Polisher::initialize] loaded target sequences
[racon::Polisher::initialize] loaded sequences
[racon::Polisher::initialize] loaded batch of overlaps
[racon::Polisher::initialize] aligned overlap 11/11
Segmentation fault (core dumped)

1.1.1
[racon::Polisher::initialize] loaded target sequences
[racon::Polisher::initialize] loaded sequences
[racon::Overlap::transmute] error: missing sequence with name utg000001l!

Fixed in release 1.1.1. Changed the message to empty overlap set for when the input files are swapped (due to additional features added soon).


Reconfirmation of Training (Fine-tuning) Details on Stable diffusion

Though you've explained it in issue6, I'd still like to double-check this detail cause I'm confused about the experiement result.
Referring to the official code for stable diffusion fine-tuning and the .sh example, there are two parameters for data transform during fine-tuning, namely args.center_crop and args.random_flip, representing centerCrop / randomCrop, no-Flip / randomFlip respectively.
If using the default parameter settings, it's actually a combination of randomCrop and  no-Flip. Here's the code:
# Preprocessing the datasets.
train_transforms = transforms.Compose(
    [
        transforms.Resize(args.resolution, interpolation=transforms.InterpolationMode.BILINEAR),
        transforms.CenterCrop(args.resolution) if args.center_crop else transforms.RandomCrop(args.resolution),
        transforms.RandomHorizontalFlip() if args.random_flip else transforms.Lambda(lambda x: x),
        transforms.ToTensor(),
        transforms.Normalize([0.5], [0.5]),
    ]
)

I'd like to know which parameter combination you used？
I conducted experiments on various data-augmentation combination based on your methods (COCO dataset, 2500/2500 split, 150,000 steps, as described in your paper).
The experimental results align with yours only for randomCrop+ no-Flip (ASR/AUC: 0.8334/0.9105).  And centerCrop +no-Flip yields higher results (ASR≈0.90). On the other hand, randomCrop+randomFlip  results in much lower performance (ASR≈0.75).
So, did you use the combination of randomCrop and  no-Flip?
Thank you for your time, and I look forward to your response!

We utilized the default parameter settings for data augmentation in fine-tuning. In this case, it should be randomCrop + no-Flip.

I see. Thanks a lot !


Cannot Start Integration with old, inactive vehicle in Bluelink

Version of the integration
2.19.0
Describe the bug
I'm on my 2nd Hyundai EV. The 1st one was a lease and has been returned. Some kind of "ghost" of this car still lives in my Bluelink account, even though Bluelink service is not active on it.
When I try to enable this integration I get the following error:
"Config not ready: Error communicating with the API: 'vehicleStatus'
You can see from the logs that it is correctly accessing the API and pulling the data about my cars.
It looks like the integration is trying to pull data for the old vehicle, which appears as 2020 IONIQ ELECTRIC. In the logs, you can see that this fails:
2024-02-02 11:28:44.370 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - get_vehicle_status response {'errorSubCode': 'GEN', 'systemName': 'BLODS', 'errorSubMessage': 'Feature Status is OFF', 'errorMessage': "We're sorry, this feature is not available according to your latest subscription status.  Please visit the owners website to view and update subscription.", 'errorCode': 502}

I suggest you filter out all vehicles with "enrollmentStatus":"CANCELLED" in their properties.
Debug logs if an error occurred
I'm including the debug logs and attempting to redact all the keys, email addresses, and other account Ids revealed.
2024-02-02 11:22:03.082 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration kia_uvo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-02-02 11:28:42.413 DEBUG (MainThread) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - initial API headers: {'content-type': 'application/json;charset=UTF-8', 'accept': 'application/json, text/plain, */*', 'accept-encoding': 'gzip, deflate, br', 'accept-language': 'en-US,en;q=0.9', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36', 'host': 'api.telematics.hyundaiusa.com', 'origin': 'https://api.telematics.hyundaiusa.com', 'referer': 'https://api.telematics.hyundaiusa.com/login', 'from': 'SPA', 'to': 'ISS', 'language': '0', 'offset': '-5', 'sec-fetch-dest': 'empty', 'sec-fetch-mode': 'cors', 'sec-fetch-site': 'same-origin', 'refresh': 'false', 'encryptFlag': 'false', 'brandIndicator': 'H', 'gen': '2', 'client_id': 'm66129Bb-em93-SPAHYN-bZ91-am4540zp19920', 'clientSecret': 'v558o935-6nne-423i-baa8'}
2024-02-02 11:28:43.034 DEBUG (SyncWorker_7) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Sign In Response {"access_token":"XXX","refresh_token":"XXX","expires_in":"1799","username":"XXX"}
2024-02-02 11:28:43.035 DEBUG (SyncWorker_7) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Access Token Value XXX
2024-02-02 11:28:43.036 DEBUG (SyncWorker_7) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Refresh Token Value XXX
2024-02-02 11:28:43.362 DEBUG (SyncWorker_7) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Get Vehicles Response {"enrolledVehicleDetails":[{"packageDetails":null,"driverDetails":[{"driverAddressDetails":[{"city":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"driver":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[],"tncId":"24","loginId":"XXX","preferredDealerCode":"XXX","driverUserProfile":"N","phones":[],"idmId":"XXX","userId":"XXX","email":"XXX"}}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/electric-shadow/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20201102","svdDay":"01","trim":"EV SE","modelCode":"IONIQ ELECTRIC","ubiCapabilityInd":"Y","vin":"--VIN--","enrollmentId":"XXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"21673","nickName":"2020 IONIQ ELECTRIC","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"E","modelYear":"2020","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"KEY","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/sedan/Dashboard-01.svg","enrollmentType":"INDIVIDUAL","sapColorCode":"USS","bluelinkEnabled":true,"odometerUpdateDate":"20231027064234","fatcAvailable":"Y","color":"GRAY","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"IN-ACTIVE","setOffPeak":"1","mapProvider":"HERE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"T9Y","accessoryCode":"D-AUDIO","nadid":"XXX","mit":"5000","regid":"H00003240617V--VIN--","blueLink":"Y","waypointInd":"NO","billingInd":"N/A","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/electric-shadow/Dashboard-01.png","imat":"5000","additionalVehicleDetails":{"temperatureRange":"true","tmuSleepMode":"Yes","enableHCAModule":"Y","maxTemp":92,"icpParking":0,"remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","vehicleModemType":"4G (AEPEEV.USA.SOP.V115.221011)","icpAACapable":"N","icpDriveThru":0,"dkType":"","dynamicSOCText":"Use the slider above to set a charge limit. Charging will stop when this battery level is reached. The limit cannot be set lower than 50% This setting will override all other charge settings if set.","battDrainFunctOnOff":"N","enableRoadSideAssitanceAAAModule":"Y","idleSpeedinValetAlert":"N","evAlarmOptionInfo":"No","mapOtaAccepted":"N","dkCapable":"N","combinedHeatSettingsEnable":"Y","icpChargingStation":0,"hyundaiHome":"N","wifiHotspotCapable":"N","dkEnrolled":"N","icpAvntCapable":"N","enableEVTrip":"Y","minTemp":62,"icpFuelStation":0,"targetSOCLevelMax":100,"remoteLockConsentForRemoteStartCapable":"No","msCapableOption":"N","icpCPCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No","cpoVehicle":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":false,"targetSOCLevel":"50","rearWindowHeatCapable":"NO","preferredDealerCode":"XXX","hmaModel":"AEEV","series":"IONIQ ELECTRIC","enrollmentStatus":"CANCELLED","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}},{"packageDetails":[{"assetNumber":"XXX","displayCategory":"Connected Care","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Connected Care","startDate":"XXX"},{"assetNumber":"XXX","displayCategory":"Remote","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Remote","startDate":"XXX"},{"assetNumber":"XXX","displayCategory":"Guidance","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Guidance","startDate":"XXX"}],"driverDetails":[{"driverAddressDetails":[{"city":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"driver":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[],"tncId":"24","loginId":"XXX","preferredDealerCode":"XXX","driverUserProfile":"N","phones":[],"idmId":"XXX","userId":"XXX","email":"XXX"}}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/atlas-white/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"seven","enrollmentDate":"20230929","svdDay":"28","trim":"SE","modelCode":"IONIQ 5","ubiCapabilityInd":"Y","vin":"--VIN--","enrollmentId":"XXX","sideMirrorHeatCapable":"YES","ownersuccession":"1","odometer":"2788","nickName":"2023 IONIQ 5","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"E","modelYear":"2023","steeringWheelHeatCapable":"YES","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"KEY","sapColorCode":"SAW","bluelinkEnabled":true,"odometerUpdateDate":"20240201145310","fatcAvailable":"Y","color":"WHITE","maintSyncCapable":"YES","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"1","mapProvider":"HERE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"YGN","accessoryCode":"WAVN 5.0","nadid":"XXX","mit":"7500","regid":"H00005294328V--VIN--","blueLink":"Y","waypointInd":"NO","billingInd":"MONTHLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/atlas-white/Dashboard-01.png","imat":"7500","additionalVehicleDetails":{"temperatureRange":"true","tmuSleepMode":"No","enableHCAModule":"Y","maxTemp":82,"icpParking":1,"remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"Yes","vehicleModemType":"4G (NEEV23.USA.S5W_M.V011.005.231215)","icpAACapable":"Y","icpDriveThru":0,"dkType":"DK TYPE UNKNOWN","dynamicSOCText":"Use the slider above to set a charge limit. Charging will stop when this battery level is reached. The limit cannot be set lower than 50% This setting will override all other charge settings if set.","battDrainFunctOnOff":"N","enableRoadSideAssitanceAAAModule":"Y","idleSpeedinValetAlert":"N","evAlarmOptionInfo":"Yes","mapOtaAccepted":"N","dkCapable":"Y","combinedHeatSettingsEnable":"Y","icpChargingStation":0,"hyundaiHome":"N","wifiHotspotCapable":"Y","dkEnrolled":"N","icpAvntCapable":"Y","enableEVTrip":"Y","minTemp":62,"icpFuelStation":0,"targetSOCLevelMax":100,"remoteLockConsentForRemoteStartCapable":"No","eaPromotion":{"expireOn":"3 years from vehicle purchase date","description":"Electrify America teamed up with Hyundai to offer 250 kWh (approx. 1,000 miles of EPA-estimated driving range*) of complimentary charging on its nationwide ultra-fast charging network. To register, download the Electrify America app, then input your activation code and vehicle's VIN. Contact Electrify America Customer Assistance 24/7 at 1-833-632-2778 or support@electrifyamerica.com for questions about this program.

Learn More.

To claim the complimentary charging for your vehicle enroll in the Electrify America Hyundai Premium Charging Program by clicking here.","enrollmentCode":"XXX"},"msCapableOption":"N","icpCPCapable":"Y","enableValetActivate":"Y","energyConsoleCapable":"No","cpoVehicle":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"targetSOCLevel":"50","rearWindowHeatCapable":"YES","preferredDealerCode":"XXX","hmaModel":"NE1","series":"IONIQ 5","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"Y"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"XXX","street":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"emergencyContacts":[{"firstName":"XXX","lastName":"XXX","contactId":"XXX","phones":[{"number":"XXX","type":"mobile","order":1}],"relationship":"XXX","email":"XXX"}],"user":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[{"number":"XXX","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"},{"number":"XXX","primaryPhoneIndicator":"NO","fccOptIn":"","type":"MOBILE"}],"loginId":"XXX","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"billingAccountNumber":"XXX","appRating":"N","geoLocationConsent":"Y","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"XXX"},"tncFlag":"N","phones":[{"number":"XXX","type":"cell","order":1},{"number":"XXX","type":"cell","order":2}],"idmId":"XXX","userId":"XXX","notificationEmail":"XXX","email":"XXX"}}
2024-02-02 11:28:43.692 DEBUG (SyncWorker_8) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Get Vehicles Response {"enrolledVehicleDetails":[{"packageDetails":null,"driverDetails":[{"driverAddressDetails":[{"city":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"driver":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[],"tncId":"24","loginId":"XXX","preferredDealerCode":"XXX","driverUserProfile":"N","phones":[],"idmId":"XXX","userId":"XXX","email":"XXX"}}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/electric-shadow/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20201102","svdDay":"01","trim":"EV SE","modelCode":"IONIQ ELECTRIC","ubiCapabilityInd":"Y","vin":"--VIN--","enrollmentId":"XXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"21673","nickName":"2020 IONIQ ELECTRIC","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"E","modelYear":"2020","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"KEY","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/sedan/Dashboard-01.svg","enrollmentType":"INDIVIDUAL","sapColorCode":"USS","bluelinkEnabled":true,"odometerUpdateDate":"20231027064234","fatcAvailable":"Y","color":"GRAY","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"IN-ACTIVE","setOffPeak":"1","mapProvider":"HERE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"T9Y","accessoryCode":"D-AUDIO","nadid":"XXX","mit":"5000","regid":"H00003240617V--VIN--","blueLink":"Y","waypointInd":"NO","billingInd":"N/A","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/electric-shadow/Dashboard-01.png","imat":"5000","additionalVehicleDetails":{"temperatureRange":"true","tmuSleepMode":"Yes","enableHCAModule":"Y","maxTemp":92,"icpParking":0,"remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","vehicleModemType":"4G (AEPEEV.USA.SOP.V115.221011)","icpAACapable":"N","icpDriveThru":0,"dkType":"","dynamicSOCText":"Use the slider above to set a charge limit. Charging will stop when this battery level is reached. The limit cannot be set lower than 50% This setting will override all other charge settings if set.","battDrainFunctOnOff":"N","enableRoadSideAssitanceAAAModule":"Y","idleSpeedinValetAlert":"N","evAlarmOptionInfo":"No","mapOtaAccepted":"N","dkCapable":"N","combinedHeatSettingsEnable":"Y","icpChargingStation":0,"hyundaiHome":"N","wifiHotspotCapable":"N","dkEnrolled":"N","icpAvntCapable":"N","enableEVTrip":"Y","minTemp":62,"icpFuelStation":0,"targetSOCLevelMax":100,"remoteLockConsentForRemoteStartCapable":"No","msCapableOption":"N","icpCPCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No","cpoVehicle":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":false,"targetSOCLevel":"50","rearWindowHeatCapable":"NO","preferredDealerCode":"XXX","hmaModel":"AEEV","series":"IONIQ ELECTRIC","enrollmentStatus":"CANCELLED","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}},{"packageDetails":[{"assetNumber":"XXX","displayCategory":"Connected Care","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Connected Care","startDate":"XXX"},{"assetNumber":"XXX","displayCategory":"Remote","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Remote","startDate":"XXX"},{"assetNumber":"XXX","displayCategory":"Guidance","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Guidance","startDate":"XXX"}],"driverDetails":[{"driverAddressDetails":[{"city":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"driver":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[],"tncId":"24","loginId":"XXX","preferredDealerCode":"XXX","driverUserProfile":"N","phones":[],"idmId":"XXX","userId":"XXX","email":"XXX"}}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/atlas-white/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"seven","enrollmentDate":"20230929","svdDay":"28","trim":"SE","modelCode":"IONIQ 5","ubiCapabilityInd":"Y","vin":"--VIN--","enrollmentId":"XXX","sideMirrorHeatCapable":"YES","ownersuccession":"1","odometer":"2788","nickName":"2023 IONIQ 5","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"E","modelYear":"2023","steeringWheelHeatCapable":"YES","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"KEY","sapColorCode":"SAW","bluelinkEnabled":true,"odometerUpdateDate":"20240201145310","fatcAvailable":"Y","color":"WHITE","maintSyncCapable":"YES","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"1","mapProvider":"HERE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"YGN","accessoryCode":"WAVN 5.0","nadid":"XXX","mit":"7500","regid":"H00005294328V--VIN--","blueLink":"Y","waypointInd":"NO","billingInd":"MONTHLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/atlas-white/Dashboard-01.png","imat":"7500","additionalVehicleDetails":{"temperatureRange":"true","tmuSleepMode":"No","enableHCAModule":"Y","maxTemp":82,"icpParking":1,"remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"Yes","vehicleModemType":"4G (NEEV23.USA.S5W_M.V011.005.231215)","icpAACapable":"Y","icpDriveThru":0,"dkType":"DK TYPE UNKNOWN","dynamicSOCText":"Use the slider above to set a charge limit. Charging will stop when this battery level is reached. The limit cannot be set lower than 50% This setting will override all other charge settings if set.","battDrainFunctOnOff":"N","enableRoadSideAssitanceAAAModule":"Y","idleSpeedinValetAlert":"N","evAlarmOptionInfo":"Yes","mapOtaAccepted":"N","dkCapable":"Y","combinedHeatSettingsEnable":"Y","icpChargingStation":0,"hyundaiHome":"N","wifiHotspotCapable":"Y","dkEnrolled":"N","icpAvntCapable":"Y","enableEVTrip":"Y","minTemp":62,"icpFuelStation":0,"targetSOCLevelMax":100,"remoteLockConsentForRemoteStartCapable":"No","eaPromotion":{"expireOn":"3 years from vehicle purchase date","description":"Electrify America teamed up with Hyundai to offer 250 kWh (approx. 1,000 miles of EPA-estimated driving range*) of complimentary charging on its nationwide ultra-fast charging network. To register, download the Electrify America app, then input your activation code and vehicle's VIN. Contact Electrify America Customer Assistance 24/7 at 1-833-632-2778 or support@electrifyamerica.com for questions about this program.

Learn More.

To claim the complimentary charging for your vehicle enroll in the Electrify America Hyundai Premium Charging Program by clicking here.","enrollmentCode":"XXX"},"msCapableOption":"N","icpCPCapable":"Y","enableValetActivate":"Y","energyConsoleCapable":"No","cpoVehicle":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"targetSOCLevel":"50","rearWindowHeatCapable":"YES","preferredDealerCode":"XXX","hmaModel":"NE1","series":"IONIQ 5","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"Y"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"XXX","street":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"emergencyContacts":[{"firstName":"XXX","lastName":"XXX","contactId":"XXX","phones":[{"number":"XXX","type":"mobile","order":1}],"relationship":"XXX","email":"XXX"}],"user":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[{"number":"XXX","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"},{"number":"XXX","primaryPhoneIndicator":"NO","fccOptIn":"","type":"MOBILE"}],"loginId":"XXX","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"billingAccountNumber":"XXX","appRating":"N","geoLocationConsent":"Y","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"XXX"},"tncFlag":"N","phones":[{"number":"XXX","type":"cell","order":1},{"number":"XXX","type":"cell","order":2}],"idmId":"XXX","userId":"XXX","notificationEmail":"XXX","email":"XXX"}}
2024-02-02 11:28:43.695 DEBUG (SyncWorker_8) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - using API headers: {'content-type': 'application/json;charset=UTF-8', 'accept': 'application/json, text/plain, */*', 'accept-encoding': 'gzip, deflate, br', 'accept-language': 'en-US,en;q=0.9', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36', 'host': 'api.telematics.hyundaiusa.com', 'origin': 'https://api.telematics.hyundaiusa.com', 'referer': 'https://api.telematics.hyundaiusa.com/login', 'from': 'SPA', 'to': 'ISS', 'language': '0', 'offset': '-5', 'sec-fetch-dest': 'empty', 'sec-fetch-mode': 'cors', 'sec-fetch-site': 'same-origin', 'refresh': 'false', 'encryptFlag': 'false', 'brandIndicator': 'H', 'gen': '2', 'client_id': 'm66129Bb-em93-SPAHYN-bZ91-am4540zp19920', 'clientSecret': 'v558o935-6nne-423i-baa8', 'username': 'XXX', 'accessToken': 'XXX', 'blueLinkServicePin': '1908', 'registrationId': 'H00003240617V--VIN--', 'vin': '--VIN--'}
2024-02-02 11:28:43.869 DEBUG (SyncWorker_8) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - get_vehicle_status response {'errorSubCode': 'GEN', 'systemName': 'BLODS', 'errorSubMessage': 'Feature Status is OFF', 'errorMessage': "We're sorry, this feature is not available according to your latest subscription status.  Please visit the owners website to view and update subscription.", 'errorCode': 502}
2024-02-02 11:28:44.186 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Get Vehicles Response {"enrolledVehicleDetails":[{"packageDetails":null,"driverDetails":[{"driverAddressDetails":[{"city":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"driver":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[],"tncId":"24","loginId":"XXX","preferredDealerCode":"XXX","driverUserProfile":"N","phones":[],"idmId":"XXX","userId":"XXX","email":"XXX"}}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/electric-shadow/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20201102","svdDay":"01","trim":"EV SE","modelCode":"IONIQ ELECTRIC","ubiCapabilityInd":"Y","vin":"--VIN--","enrollmentId":"XXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"21673","nickName":"2020 IONIQ ELECTRIC","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"E","modelYear":"2020","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"KEY","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/sedan/Dashboard-01.svg","enrollmentType":"INDIVIDUAL","sapColorCode":"USS","bluelinkEnabled":true,"odometerUpdateDate":"20231027064234","fatcAvailable":"Y","color":"GRAY","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"IN-ACTIVE","setOffPeak":"1","mapProvider":"HERE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"T9Y","accessoryCode":"D-AUDIO","nadid":"XXX","mit":"5000","regid":"H00003240617V--VIN--","blueLink":"Y","waypointInd":"NO","billingInd":"N/A","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/ev-se/exterior/base/electric-shadow/Dashboard-01.png","imat":"5000","additionalVehicleDetails":{"temperatureRange":"true","tmuSleepMode":"Yes","enableHCAModule":"Y","maxTemp":92,"icpParking":0,"remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","vehicleModemType":"4G (AEPEEV.USA.SOP.V115.221011)","icpAACapable":"N","icpDriveThru":0,"dkType":"","dynamicSOCText":"Use the slider above to set a charge limit. Charging will stop when this battery level is reached. The limit cannot be set lower than 50% This setting will override all other charge settings if set.","battDrainFunctOnOff":"N","enableRoadSideAssitanceAAAModule":"Y","idleSpeedinValetAlert":"N","evAlarmOptionInfo":"No","mapOtaAccepted":"N","dkCapable":"N","combinedHeatSettingsEnable":"Y","icpChargingStation":0,"hyundaiHome":"N","wifiHotspotCapable":"N","dkEnrolled":"N","icpAvntCapable":"N","enableEVTrip":"Y","minTemp":62,"icpFuelStation":0,"targetSOCLevelMax":100,"remoteLockConsentForRemoteStartCapable":"No","msCapableOption":"N","icpCPCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No","cpoVehicle":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":false,"targetSOCLevel":"50","rearWindowHeatCapable":"NO","preferredDealerCode":"XXX","hmaModel":"AEEV","series":"IONIQ ELECTRIC","enrollmentStatus":"CANCELLED","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2020/ioniq-electric/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}},{"packageDetails":[{"assetNumber":"XXX","displayCategory":"Connected Care","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Connected Care","startDate":"XXX"},{"assetNumber":"XXX","displayCategory":"Remote","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Remote","startDate":"XXX"},{"assetNumber":"XXX","displayCategory":"Guidance","packageId":"XXX","term":"36","renewalDate":"XXX","packageType":"Guidance","startDate":"XXX"}],"driverDetails":[{"driverAddressDetails":[{"city":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"driver":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[],"tncId":"24","loginId":"XXX","preferredDealerCode":"XXX","driverUserProfile":"N","phones":[],"idmId":"XXX","userId":"XXX","email":"XXX"}}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/atlas-white/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"seven","enrollmentDate":"20230929","svdDay":"28","trim":"SE","modelCode":"IONIQ 5","ubiCapabilityInd":"Y","vin":"--VIN--","enrollmentId":"XXX","sideMirrorHeatCapable":"YES","ownersuccession":"1","odometer":"2788","nickName":"2023 IONIQ 5","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"E","modelYear":"2023","steeringWheelHeatCapable":"YES","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"KEY","sapColorCode":"SAW","bluelinkEnabled":true,"odometerUpdateDate":"20240201145310","fatcAvailable":"Y","color":"WHITE","maintSyncCapable":"YES","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"1","mapProvider":"HERE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"YGN","accessoryCode":"WAVN 5.0","nadid":"XXX","mit":"7500","regid":"H00005294328V--VIN--","blueLink":"Y","waypointInd":"NO","billingInd":"MONTHLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/se/exterior/base/atlas-white/Dashboard-01.png","imat":"7500","additionalVehicleDetails":{"temperatureRange":"true","tmuSleepMode":"No","enableHCAModule":"Y","maxTemp":82,"icpParking":1,"remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"Yes","vehicleModemType":"4G (NEEV23.USA.S5W_M.V011.005.231215)","icpAACapable":"Y","icpDriveThru":0,"dkType":"DK TYPE UNKNOWN","dynamicSOCText":"Use the slider above to set a charge limit. Charging will stop when this battery level is reached. The limit cannot be set lower than 50% This setting will override all other charge settings if set.","battDrainFunctOnOff":"N","enableRoadSideAssitanceAAAModule":"Y","idleSpeedinValetAlert":"N","evAlarmOptionInfo":"Yes","mapOtaAccepted":"N","dkCapable":"Y","combinedHeatSettingsEnable":"Y","icpChargingStation":0,"hyundaiHome":"N","wifiHotspotCapable":"Y","dkEnrolled":"N","icpAvntCapable":"Y","enableEVTrip":"Y","minTemp":62,"icpFuelStation":0,"targetSOCLevelMax":100,"remoteLockConsentForRemoteStartCapable":"No","eaPromotion":{"expireOn":"3 years from vehicle purchase date","description":"Electrify America teamed up with Hyundai to offer 250 kWh (approx. 1,000 miles of EPA-estimated driving range*) of complimentary charging on its nationwide ultra-fast charging network. To register, download the Electrify America app, then input your activation code and vehicle's VIN. Contact Electrify America Customer Assistance 24/7 at 1-833-632-2778 or support@electrifyamerica.com for questions about this program.

Learn More.

To claim the complimentary charging for your vehicle enroll in the Electrify America Hyundai Premium Charging Program by clicking here.","enrollmentCode":"XXX"},"msCapableOption":"N","icpCPCapable":"Y","enableValetActivate":"Y","energyConsoleCapable":"No","cpoVehicle":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"targetSOCLevel":"50","rearWindowHeatCapable":"YES","preferredDealerCode":"XXX","hmaModel":"NE1","series":"IONIQ 5","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2023/ioniq-5/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"Y"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"XXX","street":"XXX","postalCode":"XXX","type":"PRIMARY","region":"MA"}],"emergencyContacts":[{"firstName":"XXX","lastName":"XXX","contactId":"XXX","phones":[{"number":"XXX","type":"mobile","order":1}],"relationship":"XXX","email":"XXX"}],"user":{"accountId":"XXX","firstName":"XXX","lastName":"XXX","phonesOptIn":[{"number":"XXX","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"},{"number":"XXX","primaryPhoneIndicator":"NO","fccOptIn":"","type":"MOBILE"}],"loginId":"XXX","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"billingAccountNumber":"XXX","appRating":"N","geoLocationConsent":"Y","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"XXX"},"tncFlag":"N","phones":[{"number":"XXX","type":"cell","order":1},{"number":"XXX","type":"cell","order":2}],"idmId":"XXX","userId":"XXX","notificationEmail":"XXX","email":"XXX"}}
2024-02-02 11:28:44.189 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - using API headers: {'content-type': 'application/json;charset=UTF-8', 'accept': 'application/json, text/plain, */*', 'accept-encoding': 'gzip, deflate, br', 'accept-language': 'en-US,en;q=0.9', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36', 'host': 'api.telematics.hyundaiusa.com', 'origin': 'https://api.telematics.hyundaiusa.com', 'referer': 'https://api.telematics.hyundaiusa.com/login', 'from': 'SPA', 'to': 'ISS', 'language': '0', 'offset': '-5', 'sec-fetch-dest': 'empty', 'sec-fetch-mode': 'cors', 'sec-fetch-site': 'same-origin', 'refresh': 'false', 'encryptFlag': 'false', 'brandIndicator': 'H', 'gen': '2', 'client_id': 'm66129Bb-em93-SPAHYN-bZ91-am4540zp19920', 'clientSecret': 'v558o935-6nne-423i-baa8', 'username': 'XXX', 'accessToken': 'XXX', 'blueLinkServicePin': '1908', 'registrationId': 'H00003240617V--VIN--', 'vin': '--VIN--'}
2024-02-02 11:28:44.370 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - get_vehicle_status response {'errorSubCode': 'GEN', 'systemName': 'BLODS', 'errorSubMessage': 'Feature Status is OFF', 'errorMessage': "We're sorry, this feature is not available according to your latest subscription status.  Please visit the owners website to view and update subscription.", 'errorCode': 502}
2024-02-02 11:28:44.372 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.958 seconds (success: False)

To Reproduce
I think you will need a vehicle with a cancelled bluelink status on your account to see this bug.
Screenshots

Delete the old car or have support remove it and you should be good to go.  To solve this in code would need us to add items I don't have the time for right now.   If someone wants to take on vehicle selection I am open to a PR.


Create an Ember CLI add-on

How would you want an addon to work?

https://github.com/ember-cli/ember-cli-deploy -- basically making an adapter for this


[REQUEST] Install cartridge to cia directly

Hello there!
I have some games cartridges and I thought that it can be a great idea if we can install cartridges directly just like if there were cias. I know we can go to D9 and dump as cias but I don't know if we can install directly. What do you think?
Thanks :)

FBI cannot do that with the level of access it has.


[FEATURE]:  Instantiate a pre-trained model with ZeroInitContext

Describe the feature
It seems not to support instantiating a pre-trained model from a checkpoint with ZeroInitContext.
For example, when instantiating a bert-base using HuggingFace API with ZeroInitContext:
with ZeroInitContext(target_device=torch.cuda.current_device(),
                                    shard_strategy=shard_strategy,
                                    shard_param=True):
    model = BertModel.from_pretrained("bert-base-uncased")

I understand that when using .from_pretrained(), it will first instantiate a model, and then load the state_dict from a pre-trained checkpoint. However, in the ZeroInitContext, when instantiating a model, it then shards the parameters, which will cause the failure of directly loading a pre-trained checkpoint.
Is it possible to instantiate a pre-trained model with ZeroInitContext?
Thanks!

Hi, I impletemented this feature in https://github.com/hpcaitech/ColossalAI/pull/894.
You can install the latest colossalai and try!

Thanks for your reply!
However, when I try to re-install colossalai by the latest repository, it will raise some errors. The part of error information is as follows:
ninja: build stopped: subcommand failed.
      Traceback (most recent call last):
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1740, in _run_ninja_build
          subprocess.run(
        File "/data/anaconda3/envs/bert/lib/python3.8/subprocess.py", line 516, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

      The above exception was the direct cause of the following exception:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/data/project/ColossalAI/setup.py", line 194, in <module>
          setup(
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/__init__.py", line 87, in setup
          return distutils.core.setup(**attrs)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 148, in setup
          return run_commands(dist)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 163, in run_commands
          dist.run_commands()
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands
          self.run_command(cmd)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/dist.py", line 1229, in run_command
          super().run_command(command)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
          cmd_obj.run()
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 299, in run
          self.run_command('build')
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/dist.py", line 1229, in run_command
          super().run_command(command)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
          cmd_obj.run()
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/command/build.py", line 136, in run
          self.run_command(cmd_name)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/dist.py", line 1229, in run_command
          super().run_command(command)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
          cmd_obj.run()
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 79, in run
          _build_ext.run(self)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 339, in run
          self.build_extensions()
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 741, in build_extensions
          build_ext.build_extensions(self)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 448, in build_extensions
          self._build_extensions_serial()
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 473, in _build_extensions_serial
          self.build_extension(ext)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
          _build_ext.build_extension(self, ext)
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 528, in build_extension
          objects = self.compiler.compile(sources,
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 562, in unix_wrap_ninja_compile
          _write_ninja_file_and_compile_objects(
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1419, in _write_ninja_file_and_compile_objects
          _run_ninja_build(
        File "/data/anaconda3/envs/bert/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1756, in _run_ninja_build
          raise RuntimeError(message) from e
      RuntimeError: Error compiling objects for extension
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for colossalai
  Running setup.py clean for colossalai
Failed to build colossalai
Installing collected packages: colossalai
  Running setup.py install for colossalai ... error
  error: subprocess-exited-with-error

  × Running setup.py install for colossalai did not run successfully.
  │ exit code: 1
  ╰─> [641 lines of output]

My environments are as follows:
CUDA version: 11.3,
Python version: 3.8,
Pytorch version: 1.11.0+cu113.
Thanks!

Hi, could you tell me your OS? We only tested colossalai on Linux x86_64, and we are afraid that MacOS and Windows are not supported.

You can also try to install the preview version: https://colossalai.org/download
It contains this feature.

Hi,
I have installed the preview version successfully, and now could load the pre-trained checkpoint!
Thank you!

hello, I encountered a "Import 'colossalai.zero.init_ctx' could not be resolved" problem. Could it caused by the low version of colossalai?
python == 3.9.16
colossalai == 0.2.8


release: 1.4.0

:robot: I have created a release beep boop
1.4.0 (2022-11-16)
Features

add helper function for httpx (953e9ef)
errx: add pkg caller (3274289)
seq: add short uuid (349a8a7)
seq: add sonyflake (19a465b)
seq: add uuid (7d74bda)

Bug Fixes

seq: panic when sonyflake generate fail (b87306a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/starudream/go-lib/releases/tag/v1.4.0 :sunflower:


Option to specify indent style & size

By default, indent is configured with two spaces. Why not provide an option for those who'd rather use 4 spaces (or 8) or even tabs (though this might not be good)?

Sorry, but that won't happen, this is far too much work for little gain. simply change the desired indentation in eslint and run eslint --fix or something.


WebGL warning in 2D on some setups

See the forum post.
This is most likely due to 3D positions being stored in attribute 0 and 2D in attribute 1.  In practice, I don't know if this actually impacts performance on any drivers.

I can reproduce this warning on my machine as well, and it is only in 2D mode:
[.WebGLRenderingContext-0x7fbd53a41690]PERFORMANCE WARNING: Attribute 0 is disabled. This has signficant performance penalty
WebGL: too many errors, no more errors will be reported to the console for this context.

Please let me know if there is anything I can do to support this, even if that means confirming that there is no real performance issue and fixing whatever in the stack is broken.
I am using very recent versions of software (and hardware).  Mainly, the Intel Mesa drivers are very recent (probably more so than most users).  I am using Intel Haswell hardware (ignore the AMD VGA device in the printout below; it's not being used):
$ uname -a
Linux desmas-l 4.0.0-2-amd64 #1 SMP Debian 4.0.5-1a~test (2015-06-17) x86_64 GNU/Linux

$ glxinfo | super_awesome_grep_command_that_doesnt_exist
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.8
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05)
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5)
00:1c.1 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 [8086:8c12] (rev d5)
00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d5)
00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5)
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05)
00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller [8086:8c4b] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Neptune XT [Radeon HD 8970M] [1002:6801] (rev ff)
03:00.0 PCI bridge [0604]: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] [104c:823e] (rev 01)
04:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] [104c:823f] (rev 01)
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader [10ec:5289] (rev 01)
05:00.2 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0a)
06:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)

@nmschulte how many fps do you get (see the top right) if you browse to http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/index.html?stats=true

60 FPS (3D and 2D).  I can turn off VSYNC if you like.

Thanks, no need to turn off VSYNC.  I would not worry about the warning on your setup unless you run into performance problems that you don't experience elsewhere.

It's going to be pretty easy to hit 60 FPS on that demo w/ this hardware doing software rendering.  I doubt the bit of indirection that this is indicating is going to impact the framerate at such low load.  Do you think that test is definitive?  I was thinking that by disabling VSync we could apply some load, but the event-loop nature of JS (that is: "WebGL") might mean it's not applicable.

You could turn on terrain and then zoom into the Grand Canyon.

It didn't seem to have any effect (on FPS, but also visually (screenshots identical minus attribute text)) but in 3D, and only then while the data loads.  Does Cesium actually realize the terrain data in 2D?  I suppose it would be neat for applying time-of-day effects (read: realizing the light from the sun/moon: shadow casting, etc.).

I suspect you're right that Chromium is being overly concerned w/ this message, and in my case (or possibly most w/ recent desktop hardware/software cases) it's superfluous.  But, for the sake of the bug report, how hard is it to change the shaders to always use v-a 0, and is there a reason they're currently not?  Doing so would increase performance on those older implementations, and it probably matters most there too.

Given the age of this report, I'm going to go ahead and close. If this is still an issue, please feel free to leave a comment or re-open. Thanks!


Create tables automatically by ddl

Question
For English only, other languages will not accept.
 (But I indeed need some help)
My question is, how to create actual data node by sql script (ddl).
When using tranditional JDBC-Driver, I can call script runner to do this task (by retrieve the only datasource). But in sharding-jdbc, there are many database (schema) in one instance (e.g, ds0, ds1, ...), I tried using the autowired datasource sharding-jdbc provide, and then using script runner to run ddl, but it seems it doesn't work.
the ddl looks like this:
DROP SCHEMA IF EXISTS USERS;
CREATE SCHEMA USERS;
SET SCHEMA USERS;
DROP TABLE IF EXISTS USER0;
DROP TABLE IF EXISTS USER1;
CREATE TABLE USER0(
                      id bigint primary key not null,
                      username varchar(30) not null,
                      password char(64) not null,
                      email varchar(40) unique not null
);
=
CREATE TABLE USER1(
                      id bigint primary key not null,
                      username varchar(30) not null,
                      password char(64) not null,
                      email varchar(40) unique not null
);
DROP SCHEMA IF EXISTS GOODS;
CREATE SCHEMA GOODS;
SET SCHEMA GOODS;
DROP TABLE IF EXISTS goods;
CREATE TABLE goods(
                      id bigint primary key,
                      user_id bigint not null,
                      name varchar(40) not null,
                      introduction varchar(100) not null,
                      picture_u_r_l char(40) default 'url',
                      kind char(40) default 'unknown',
                      original_price int,
                      current_price int not null,
                      amount int not null,
                      upload_time date not null
);

By the way, is there some convient way to create actual datanode in different database by only one schema, since I rewrite user1 and user2 in the above sql script.
Appericate your wonderful work, and willing to accept rely....

I think we can use a shell script to achieve it.

hi @Sunnycheey
there is no stupid people in this community, only someone familiar or someone unfamiliar with it.
there are a lot of examples for people to start with : shardingsphere exmple
And if I were you, I perfer to have a try for proxy, it's also convenient for DBA or devops :
proxy document
proxy example

ShardingSphere can support DDL, you can try to create your table via logic table name.

Thanks for your all, and thanks for the suggesstion of @taojintianxia , I am going to try sharding-proxy.
Feel free to close the issue.


build(deps): bump github.com/containerd/containerd from 1.6.10 to 1.7.0

Fixes: #903

@kkourt PTAL,Thx!

Is there any update on this pr? :)

merged thanks @zhy76


fix: Updated API

Codecov Report

Merging #61 (1079aab) into main (1718ee9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #61   +/-   ##
=======================================
  Coverage   91.63%   91.63%
=======================================
  Files           8        8
  Lines        1817     1817
  Branches      268      268
=======================================
  Hits         1665     1665
  Misses        151      151
  Partials        1        1

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Document "advisory" issues in the Membrane manual

https://github.com/ajvincent/es7-membrane/issues?q=is%3Aissue+is%3Aopen+label%3Aadvisory


Add disclaimer and warnings to readme

Note that ord is experimental software
Disclaim warranty and liability
Warn about using bitcoin-cli commands and RPC calls on ord wallets
Warn about mixing ordinals and bitcoin funds
Note mainnet restrictions

Maybe add a WARRANTY file that disclaims all warranty and link to it everywhere?


Swap temporary 'e164' to 'mobile'.

What's this PR do?
This pull request finishes up work for storing mobiles in E.164 format.
🚚 Adds a migration which swaps the pre-generated e164 field with the existing mobile. The old field is kept in _old_mobile in case we need to quickly reverse this.*
📱 Always normalize the mobile field in E.164 format (instead of a separate e164 field).
🍂 For backwards compatibility, we'll continue to return the "old" format from the existing API endpoints. I'm adding a ticket to remember to make a v2/users endpoint sometime soon that will return E.164 formatted numbers & removes old fields (like _id, mobilecommons_status, etc.)
How should this be reviewed?
I updated the test suite where it made specific assertions against the database contents, otherwise everything should continue to function exactly the same as it did before!
*Important: This cannot be deployed until the artisan northstar:e164 script is run!! 🚨
Checklist

[ ] Documentation added for changed endpoints.
[x] Tests added for new features/bug fixes.
[ ] Post a message in #api if this includes something that causes a rebuild!

Finished running through the northstar:e164 script on QA & Thor on Friday, and everything looks good. Going to deploy this to those environments to test out the "swap" migration, and then send it on to production once the script finishes running on production as well.


 The commit messages have information on why they were flaky.

I noticed the same on the error recovery test, I fixed one of them, but the other one started working, so I left it alone. Great job.


vue cli not create webpack-simple

hi
I upgraded node js and vue cli . but I can not create new template .

vue init webpack-simple

/usr/local/lib/node_modules/vue-cli/bin/vue-init:60
let template = program.args[0]
^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:374:25)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Function.Module.runMain (module.js:442:10)
    at startup (node.js:136:18)
    at node.js:966:3

node : v4.2.6
npm : 3.5.2
vue-cli : 2.9.1
Thank you for helping me

Use at least node 6
I think that now we should start dropping support for node 4 as node 8 is soon entering LTS

Hi I have the same version issue on the  Windows Linux subsystem.
nodejs is already the newest version (4.2.6~dfsg-1ubuntu4.1).
Is there a way to install a newer version other than apt-get or do I need to go running back to powershell?

Perhaps node verison is too low.
update your node version using
npm install -g n
sudo n stable
sudo npm install npm -g

when you node -v find there is no change, but try to init vue project again.

thx

thx jiujiuwen

Thanks @jiujiuwen

Thanks @jiujiuwen

Thanks @jiujiuwen
(i'm using Ubuntu 17.04)

Obrigado @jiujiuwen resolveu meu priblema tbm. Usando ubuntu 16.4 via vagrant

Thanks @jiujiuwen

Thanks @jiujiuwen


Access tokken from superverisor

Home Assistant release with the issue:
0.92
Operating environment (Hass.io/Docker/Windows/etc.):
HASS.io
Description of problem:
From couple of releases ago when I removed API password from my config I get this error in the logg WARNING (MainThread) [homeassistant.components.http.auth] api_password is going to deprecate. You need to use a bearer token to access /api/states/device_tracker.niklas_presence from <IP_ADDRESS>What I can understand <IP_ADDRESS> is the Hassio supervisor and I can't fins what causing this error. I have tried add trusted_networks in configuration.yaml without any success. I can not find anything that don't work. The device_tracker is working even with the error.

I also get a lot of these errors in the system. logg under Hassio > systems
ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host <IP_ADDRESS>:8123 ssl:False [Connection refused]

I have the same problem, will come back with more info.

when I removed API password from my config

Apparently you did not, otherwise, you will get ERROR message, not WARNING.
This is not a bug, please go to our forum or discord channel for support.

Sorry If I offended you somehow @awarecan That was absolutely not my intention. I have tried to find a solution to this for a long time now, without success. No one, not on the forum or the discord channel can find that I have API password activated in my config, you can take a look for your self if you don't believe us. My configuration.yaml
The only thing we can find is that the ip <IP_ADDRESS> is a internal IP for Hassio. When I remove the device_tracker I get the error "api_password is going to deprecate. You need to use a bearer token to access /api/hassio_auth from <IP_ADDRESS>" and "api_password is going to deprecate. You need to use a bearer token to access /api/hassio_auth from <IP_ADDRESS>" instead. Still the same IP. Then we noticed that more then me have this issue so I decided to create this, because to us it seams as an bug.
Can you then please point me in the right direction how to remove API password more then I have already done?

https://github.com/home-assistant/home-assistant/blob/6a411710dfe84094182146e973a194a89ef931fb/homeassistant/components/http/auth.py#L170-L178
En, my wrong, you got WARNING if you removed legacy api password, otherwise INFO.
Please create an issue in hassio repo. It could be one of your hassio Add-ons still sending X-HA-access HTTP header.


Impossible to return List in swagger when generating typescript client.

When returning a List in a GET call, the typescript client that is generated defaults to
 return _observableOf<PackageObject[]>(null as any);
This gives an error as any is not an array and as such does not contain push, pop... etc.

I have the same problem

I had the same problem when updating from rxjs 6.x to 7.x and found the solution here: #3827
I had still rxJsVersion set to 6.0 in my nswag.json, after setting rxJsVersion  to 7.8 everything generated ok


fix: version and rock name parsing errors (#79)

This PR was supposed to be much longer, but I decided that we were layering on too much complexity with no benefit whatsoever.
This PR fixes #79 in two ways: firstly, it fixes the broken version checking code (and now defaults to the latest version correctly). Secondly, it permits rock names to now also have .s in their names.
Instead of trying to create a generic catch-all parser, I think restricting rocks to this format is both sane and expected. During the big error rewrite, we can issue nice error messages to the user so they're never confused.

I don't see any changes.


fix: responsive landing page banner

Mobile Responsive banner 📐

I  have worked for  under JWOC

Guidelines 🔐
I accept the fact that i have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes  Mobile Responsive banner #188

Screenshots 📷
Here are the pictures of changes that i have made 🔽

Looks perfect @senali-d  !!