Commits Incorrectly Fail Due To linebreak-style Issues On Windows When Git Config core.autocrlf = true

I forked your repository to commit a small change, which I intended to contribute back to your repo via pull request. However, after I made the change using my Windows computer and attempted to commit by running npm run commit and answering the commitizen prompts, the commit failed to complete due to lint errors in a number of files which I never even touched. Specifically, the linebreak-style lint rule was complaining that a number of files had CRLF linebreak characters instead of LF characters. I completely understand why this check is in place, as Windows editors often silently convert LF to CRLF, and if left unchecked this can cause problems for other systems (not to mention strange behavior from Git itself) if those changed linebreak characters get committed back into the repository and pushed to the remote.
However, in my case I have the global git config flag core.autocrlf (see documentation) set to true on my Windows machine (it applies to all repositories on my machine). This resolves the linebreak character issue by causing Git to automatically covert LF characters to CRLF in my working directory when checking out files from the repository, and then automatically converting CRLF back to LF when file changes are staged to the index (and subsequently committed to the repository). This ensures that the repository always has LF characters, while also enabling Windows users who set core.autocrlf to true to have CRLF used instead in the files in their working directories.
Unfortunately, the way you currently have your lint rules configured, every time someone tries to commit it checks the linebreak characters in every file in the working directory, even if that file is not staged to be committed. This is causing all of my commit attempts to fail, as even though the files which I changed and staged to be committed have the correct LF linebreak characters (as core.autocrlf=true converted 'CRLF' back to 'LF' in those files when I staged them), your lint check is still detecting the CRLF characters in all of the other files in my working directory, even though I never made changes to them and did not stage them (those files have CRLF characters because core.autocrlf=true converted LF to CRLF when the files were checked out into my working directory).
I would suggest changing your lint checks for linebreak-style to only be run on whatever is currently staged in the index, instead of on every file in the working directory, if that is possible. Otherwise, anyone on a Windows machine who has their global Git config for core.autocrlf set to true will never be able to commit (setting core.autocrlf to true on Windows machines is best practice, as it prevents Git from ever committing CRLF characters into the repo accidentally).

Hi there! Thank you so much for digging into this issue so thoroughly! I've added .gitattributes to the project. If you could please re-clone everything it should work ok for you now. Sorry about that. Most of my repos have this now.


"add legacy moniker"

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

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

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


Viewing List Objects in VSCODE

When you use Rstudio you can view lists in beautiful way, as you can see each level as a table.

but in vscode, the lists are hard to navigate as they show in scattered way.

I hope you can add this feature to the extension!

Hi,
Yes, I also have found this problem.
Viewing lists is the only thing I prefer from RStudio, it's so much more comfortable. I work with phylogenies and my lists are quite big, VScode's viewer expands them automatically and they take forever...
I would love it if lists opened in a collapsed form at least, and it would be great to see more information about them like @Zahrawi pointed out!

@jimenamateo @Zahrawi
Just as a comment - I am using the jsonedit function of the listviewer package. It's quite convenient and IMHO serves the purpose you've been looking for.
`library(tidyverse)
library(listviewer)
df_l <- mtcars %>%
nest(,.by=cyl)
listviewer::jsonedit(df_l$data)
`

Thank you @werkstattcodes, your jsonedit function shows the list directly collapsed, so I don't have to collapse it myself, but it is still a very uncomfortable way of seeing the information.
It would be great to have every element as a table, like the gif @datasciencemedicine shared!

Totally agree! For me, this is the major downside of using R in VS Code instead of RStudio and the only reason I still switch back to RStudio from time to time.  Also experienced VS Code crashing when trying to view some of these lists.

Same here!
It is very difficult to work with large nested lists (compared to RStudio). If you could provide a mechanism to represent lists following RStudio's fashion it would be great 😀

Hello. I also join this request. I am working with a list composed of data frames and can't view anything when I run View().

However, in Rstudio it works fine.


Contributions fix

Coverage increased (+0.07%) to 88.3% when pulling 59ef28d544b9e8b254c69cdfff1223e6fadad33b on contributions-fix into ec8de0624dcb1b85afb0297a73ef4f29c1f483fe on master.


Implement IPC shutdown

Description
This PR implements IPC shutdown for the Node API.
Linked issue

Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

How to merge
Send the message bors r+ to merge this PR. For more information, see
docs/how-to/bors.md.

bors r+

Bors is waiting for macOS builds. We must fix that.
bors r+

Updated because cross-compilation PR was merged.
bors r+


Placing Blocks

@beeperdeeper089 @apachano Does this need to be reopened seeing as the blocks need to be readded?

Yes 😢
That's so sad, Alexa play Despacito

We can create a proper new task at a later date once we get to that point, imo.


implement project preference read settings endpoint

Describe your change here.
Endpoint to expose read permissions for Project Preferences
Review checklist

[x] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[x] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[x] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

The two different before_actions set either the resource instance var (update) or the project UPP scope (read). Both would need to raise an exception if the user is unauthorized, since reading these should be restricted to project owners/collabs and admins. I’m not sure if a user themself should be able to read their own UPP, @lcjohnso?

We do not currently allow access to a user's own UPP resources, and I see no persuasive reason to enable that permission. Unless it is more difficult to exclude rather than include user read permissions, proceed with granting read permissions to project owner/collabs only.


fix repeated verifier pings

@pyc92 @0xthk this is more critical as it makes the giveaway page unreliable at the moment


Dev morteza

I am just testing pull request.

Codecov Report

Merging #3 (b37ed64) into main (de85950) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff          @@
##            main      #3   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          1       1
  Lines         11      11
=====================================
  Misses        11      11

Impacted Files
Coverage Δ

src/GetData.jl
0.00% <0.00%> (ø)

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


electron window is not opening in ubuntu 16 LTs

I follow these steps
      # Clone the Quick Start repository
          $ git clone https://github.com/electron/electron-quick-start

      # Go into the repository
         $ cd electron-quick-start

     # Install the dependencies and run
        $ npm install && npm start

       node --version v9.2.0
       npm --version 4.2.0
       electron verison 1.6.15

after this only icon get highlighted the electron window is not opening

Thank you for taking the time to report this issue and helping to make Electron better.
We are sorry that we do not always have the capacity to look at all reported issues in a timely manner. There have been many changes in Electron since this issue was reported and it may have been fixed in that time.
The version of Electron this issue was reported on,1.6.15, has been superseded by newer releases -- the latest in that series is 1.6.17. In addition, there are newer branches that supersede that series. It would help us greatly if you could test this issue with the latest stable version, 1.8.3.
I'm setting the more-information-needed label for the above reasons. After you've responded, please @ me in a followup comment.
Thanks in advance! Your help is appreciated.

We haven't gotten a response to our questions in our comment https://github.com/electron/electron-quick-start/issues/177#issuecomment-372315185. With only the information that is currently in the issue, we don't have enough information to take action. In this event, i'm going to go ahead and close this but can reopen should you follow up with more info!


bump gradlew version to 7.2

Summary
bump gradlew version to 7.2
Description
Related Issue
https://bitquill.atlassian.net/browse/AD-464
Additional Reviewers
@affonsoBQ
@andiem-bq
@alexey-temnikov
@birschick-bq

close for now


Twitter adapter in bot composer nodejs

How can I install the twitter adapter in a bot based on nodejs in composer app?
Describe the bug
Version
Composer version 2.1.2
Browser

[X] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[X] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Click on 'bot' built on NodeJS
Click on package-manager
Search adapter-twitter

I expect that the adapter-twitter is avaiable and
https://www.npmjs.com/package/@botbuildercommunity/adapter-twitter
Screenshots

@diegofn, these docs explain how to build a package for use in Composer. Unfortunately, they don't explain how to do this for an NPM package which is what I am looking into. I'll let you know what I find.


Stacked columns not stacking

Checklist

[X] I updated the card to the latest version available
[X] I cleared the cache of my browser
[X] I verified that I'm really running the lastest version in my browser console (no, I did an in place file upgrade, and restarted HASS)
[X] I checked if there is another issue opened with the same problem

Describe the bug
Vanilla test by changing the default example to a stacked bar chart… , no stacking, all columns are separated
Version of the card
Version: downloaded today, can't find version number
To Reproduce
This is the configuration I used:
type: custom:apexcharts-card
apex_config:
  stacked: true
header:
  show: true
  title: ApexCharts-Card
  show_states: true
  colorize_states: true
series:
  - entity: sensor.power_consumption
    type: column
    data_generator: |
      // REMOVE ME
      const now = new Date();
      const data = [];
      for(let i = 0; i <= 24; i++) {
        data.push([now.getTime() - i * 1000 * 60 * 60, Math.floor((Math.random() * 10) + 1)])
      }
      return data.reverse();
  - entity: sensor.power_generation
    type: column
    data_generator: |
      // REMOVE ME
      const now = new Date();
      const data = [];
      for(let i = 0; i <= 24; i++) {
        data.push([now.getTime() - i * 1000 * 60 * 60, Math.floor((Math.random() * 10) + 1)])
      }
      return data.reverse();

Screenshots
If applicable, add screenshots to help explain your problem.
Expected behavior
Bars to be stacked instead of placed next to each other
Desktop (please complete the following information):

Browser Chrome
Version 95.0.4638.69

Smartphone (please complete the following information):

Device: Huwaei P30 lite
OS: Android 11
Browser Chrome

That's because your config is wrong. stacked is a main config option:
type: custom:apexcharts-card
stacked: true
[...]

Sigh - that solved all my problems, thank you very much!


Stdlib cleanup: Separate success and failure epilogues [P2]

This was done in https://github.com/libra/libra/pull/4302


Considering adding CI service integration

To let package do test automatically, it will be good to integrate CI services.
I think we have two popular CI services and we can choose one of them to accomplish this issue.

GitHub actions
Travis CI

@gerardojbaez, do you have any idea about this :)?
Once this issue is accepted, I think I can work on this.

What about both? and circleCI

What about both? and circleCI
…

Using all of these CI services? I think choosing one of them is good enough.


Tar processing 1 has wrong recipe icon

Mod source
Factorio Mod Portal
Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[X] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[ ] Other

What is the problem?

-[ ] Tar is shown as an output,
-[ ] anthracene oil is missing,
-[ ] creosote is missing, and
-[ ] carbolic is there for no reason.
Steps to reproduce
see image
Additional context
No response
Log file
No response

This has been addressed here. Thank you for the report!

That link is 404

Its an oversight on my part, the link is to the graphics Repo which is private


DEQ for Vision Transformer

Since the DEQ tech has achieved performance competitive with the state-of-the-art deep networks on Transformer based LM and CNN-based Image Recognition tasks, do the authors have plans to adapt DEQ for vision transformer architecture?

Hi @wyvernbai ,
Thanks for the question. I have thought about it but never got my hands on it.

Thanks for your reply.


Differentiable AP

With the latest commit, we got a differentiable version of AP in the AP_ad branch. The issue, is that it is too slow, as it takes around 110 ms to compute the gradient!

100 ms get from the projectant calculation
10 ms comes from the interpolations, which actually use DataInterpolations to work
Fixing the following two issues should give back a good performance!


Updating documentation about new features

Copied from trello card.
@antw @ChaelKruip what is the usual place documentation is written?
Do we use the general github wiki?

I've started using the ETMoses GitHub wiki for "plain language" descriptions of the technical aspects of the project. It doesn't have much at the moment, though.
Information aimed at end-users (customers) tends to go in the documentation repository. Personally, I think project-specific docs for end-users should also go in the project wiki – rather than the documentation repository – but that's not my call to make.

Personally, I think project-specific docs for end-users should also go in the project wiki – rather than the documentation repository – but that's not my call to make.

I agree.

@antw @ChaelKruip what is the usual place documentation is written?

I've only written user documentation in the documentation repo (as @antw mentioned above). I agree with @antw that technical documentation should go in the project wiki.
What I would like to do in the coming weeks is update/extend the user documentation and incorporate it into the front-end.

Personally, I think project-specific docs for end-users should also go in the project wiki – rather than the documentation repository – but that's not my call to make.

I agree but have not been practicing it :blush: I'll correct my mistakes ASAP


473 implement svg icon in table view

Resolve #473

Issue for follow up work for adding docs icon to card view is in #547.


Support messaging for file changes

Just thinking about collaborative use cases I wonder if gaia hub could support web socket connections for the multi-reader contexts.
That way clients could get notified when files they are interested in (hosted on hubs of other users) change.
This is just an idea at this point, no idea about the implementation implications. Just looking for feedback.

This has certainly been discussed internally and is highly desired by some core team members, although I'm not sure about current thinking as to when it may be tackled. @jcnelson @kantai @hstove thoughts?

My understanding is that the consensus among the core devs is that Gaia is for storage and only storage.  Messaging is a separate concern that should be handled by a separate service.  There is no consensus on whether or not Blockstack should develop a messaging protocol, nor is there consensus on what such a messaging protocol would look like.
The closest to consensus we have gotten is a "mailbox" API for Gaia, which would allow one user Alice to inform another user Bob that she has written data in a particular application for him to read.  I hesitate to call this messaging in the sense that it provides any RTC guarantee, since the purpose of the mailbox abstraction is to bootstrap app-specific notifications.
The forum post is here.  If implemented, each (user, application) pair would get a small amount of space on a Gaia hub to post a limited number of notifications.  This could be used to bootstrap a synchronous communication channel (like a websocket), such as by having Alice convey to Bob a rendezvous address or a shared URL.

 since the purpose of the mailbox abstraction is to bootstrap app-specific notifications.

The proposed solution seems to make a lot of assumptions about the use case.
IMO notifying about data that has changed should absolutely be a storage layer concern. If we want to build increasingly sophisticated apps on top of gaia we need a solid base layer that provides capabilities that can be layered on, including event based notification.
Implementing it anywhere other than in the storage layer would introduce unnecessary complexities and make it generally less reliable and also less general (requiring work arounds if the use case doesn't fit exactly).
I was thinking blockstack.js could expose an event notifier function (as is idiomatic in JavaScript) like:
function notifyOnFileChanged(blockstackId, appURL, fileName, callBack) {...}

This would enable arbitrary layers to be built on top of it, for whatever use cases apps need. The function could actually be implemented now via polling but it would be great to have web-socket support as well and only use polling as a fallback.
I don't understand the downsides of this nor how this breaks that gaia should deal with storage and only storage. Messaging use cases are only one potential reason for having this.
The approach I'm getting at might be compared to the way you can listen to changes in the browsers LocalStorage, a very useful feature that can be used to trigger all sorts of behaviour.

The way gaia works right now, reads and writes are essentially separate concerns -- where the gaia hub itself only concerns itself with writes, and reads are handled by the backends. This has two main benefits. First, the backends are usually deeply optimized for high read throughput, in order for the gaia hub to support the kind of read throughput that, say, a CDN'd backend provides, would require an engineering effort that is probably doomed. By keeping reads out of the gaia server, we sidestep this concern. Second, gaia hubs should be targeted at being user-deployable, and a chief benefit of separating reads from writes is that other users don't ever need to know where my gaia hub is, and I can hide, or even have it firewalled completely to only accept incoming requests from my devices.
The problem with notifying on file changes is that it breaks the separation between reads and writes. I think there's ways to get notifications via websockets, but I think that those ways should probably be separate from gaia hubs -- we've been circling the design of an indexer system for a while, and I think it may make sense to implement a notification functionality there -- basically a user's profile indicates which indexer they post notifications to, and then their gaia hub will relay notifications to that specific indexer, and the developer's notification requests would be handled by that indexer. That way, the gaia hub is still only a writer. The system is a little more complex that way, but this could mostly be masked to the developer.

The problem with notifying on file changes is that it breaks the separation between reads and writes.

How so? Notifying of changed files can be completely embedded in the write side. After returning to the client, fire a notification to listening socket connections.

a chief benefit of separating reads from writes is that other users don't ever need to know where my gaia hub is

I don't quite understand this argument. The write endpoint is looked up via indirection from the profile. The ws endpoint could be on the same endpoint just a dedicated port, or path or potentially also looked up. A trivial implementation could easily be < 100 lines of code and just as simple to deploy.

How so? Notifying of changed files can be completely embedded in the write side. After returning to the client, fire a notification to listening socket connections.

A request to be notified on writes is roughly equivalent to a delayed read. It's like saying "I want to read this file, once it is updated" or "I want to read metadata, once it is updated". This is important, because writes scale with the number of devices capable of writing to single hub (small set: usually under ten, but almost always under 100), but reads (and notification requests) scale with the number of people interested in the content (a twitter account could be responsible for tens of millions).

I don't quite understand this argument. The write endpoint is looked up via indirection from the profile. The ws endpoint could be on the same endpoint just a dedicated port, or path or potentially also looked up. A trivial implementation could easily be < 100 lines of code and just as simple to deploy.

Yeah, this is kind of confusingly documented, but the URL in the profile is the read endpoint, not the write endpoint. For the default gaia hub, one is easy to infer from the other (the write endpoint is hub.blockstack.org and the read endpoint is gaia.blockstack.org), but for other hubs, that wouldn't be possible (or desirable), because there isn't a well known set of them.

The proposed solution seems to make a lot of assumptions about the use case.

On the contrary, it assumes as little as possible about the needs of the application.  The problem with trying to build a notifyOnFileChanged() mechanism is that it would hide a lot of implementation complexity that is squarely in the application's domain.  Example concerns:

what happens when one user can't access a STUN server?

is the STUN server down?
is the STUN server malicious?
is the STUN server blocked?
are there fallback STUN servers that the user must configure?
are there alternatives to STUN that should be tried before giving up?

what communication media are used?

websockets?
IRC?
long polls?
comet?
something entirely new?

what are the privacy implications of real-time notifications?

can users be tracked if they communicate over a real-time medium?
can users opt out?  how is this preference conveyed to the application?
does the system work well with tor? i2c?
does the system work well with firewalls?

how would the method degrade gracefully if realtime delivery cannot be guaranteed?

does it revert to polling?  if so, what are the network bandwidth and power usage are concerns?
what happens if a malicious users DDoS's another user by sending them too many messages?
what happens if messages are lost? duplicated? replayed?
what happens if the application's write access pattern is bursty?  does the system batch messages?

who runs the relay servers?

how are they discovered?
are the enumerable?
can they be private?
can users select them?  If not, how are they selected?
who pays for them?

These are just a few things that come to mind.  There is no right or wrong solution to address these concerns.  The point I'm trying to make is that each application developer will answer these questions differently.  That indicates to me that real-time communication is the application developer's responsibility for now.  That said, if there are common solutions and a set of de facto libraries for dealing with this problem emerge, then we can think about including them in blockstack.js.

IMO notifying about data that has changed should absolutely be a storage layer concern. If we want to build increasingly sophisticated apps on top of gaia we need a solid base layer that provides capabilities that can be layered on, including event based notification.
Implementing it anywhere other than in the storage layer would introduce unnecessary complexities and make it generally less reliable and also less general (requiring work arounds if the use case doesn't fit exactly).

I agree that it is a useful feature.  The point I'm trying to make is that the implementation details of the feature are going to be application-specific, because there are application-specific concerns that it has to address.  A good solution for one application may be a terrible solution for another.

Thank you both for your answers. I now better understand the tradeoffs and pitfalls of my suggestion. I don't have time to go deeper into this right now but will keep thinking about it keeping this discussion in mind.

We had a pretty detailed conversation about this internally.  Will post notes on the forum sometime this week.  The TL;DR is that it should be possible to add this, provided the user selects their own notification relay mechanism (e.g. a redis server) and links it into their profile for apps to discover.

We iterated a bit more, and found that there's still too many degrees of freedom to write up a useful specification.  However, the forum thread here is instructive: https://forum.blockstack.org/t/proposal-gaia-hub-inboxes/5114
My current position is that real-time messaging should be its own library.

@jcnelson thanks for pointing me towards that forum thread, although it appears to concern the concept of a mailbox more than one of messaging – is that correct? And if so, is there a forum thread that more directly concerns messaging
I want to make sure we untangle the two considerations the best we can to keep things straight, but I'm aware we've often discussed them concurrently and comparatively to date.

Yes -- we're focusing first on the mailbox spec, and we'll worry about messaging later.  Messaging is a much more difficult problem to solve, since the "correct" solution will depend ultimately on what the app needs.  However, nearly every reasonable messaging solution needs a bootstrap mechanism that allows Alice and Bob to begin communicating.  Mailboxes solve this problem.

Ok let's continue the conversation about mailboxes over here then: https://github.com/blockstack/gaia/issues/107
@bodymindarts just to check in with you – do mailboxes sound sufficiently for your needs, or would you still need messaging per this issue even if mailboxes were supported?
If you're not familiar with mailboxes yet, I'd recommend checking out @kantai's forum post here: https://forum.blockstack.org/t/proposal-gaia-hub-inboxes/5114

@markmhx for now my assumption is that the mailboxes idea should work for our needs.

@bodymindarts fantastic, thanks!

Closing this issue due to lack of activity. Please feel free to comment if this should be re-opened.


Add subprogram copying capability

This IS a VHDL Mode capability to be able to copy subprogram definition and paste as a declaration or body.  I need to research to see if there are different commands than port copy.

Beginning work on this for 1.4.

Bulk completed.  Ironing out some bugs.

Feature added in 1.4.0


I can't send Twitch emotes

I can't or I don't know how to

did you turn on Twitch Emotes in the Emote Setting?

you'll need this until jiiks finally accepts the PR with all the fixes


Hover on instance fields doesn't always work

Post #32083, with the following example:
class Foo {
  final int _a;
  final int _b;
  int _c;

  Foo(this._a) :
    _b = 7 {
      _c = 21;
  }
}

void main() {
  var f = new Foo(42);
  print(f._c);
}

Hover works on the fields (declaration site) for _a and _c, but not _b.
Stepping into the constructor from main also stops on those same field declarations and the constructor itself.  That is surprising but does correspond to the 5 lines in the generated code:
    this[_a] = null;
    this[_c] = null;
    this[_a] = a;
    this[_b] = 7;
    this[_c] = 21;

@jmesserly

Chatted about this:

null assignment to _a is redundant code, we can eliminate that
null assignment to _c is required (JS interop requires fields to be null rather than undefined) and we can't trust the body _c =  will be executed before this is visible (in this particular example of it's safe, because Foo extends Object and the assignment is the very first statement and the value expression doesn't use this ... but in general we don't know that)
stepping behavior onto fields is intentional because fields can have initializers. Perhaps we should suppress it for implicit null fields (but that would break hover on them...)
we don't step on _b fieldbecause it has a constructor initializer and that's the hoverable expression we mark.
we could add a comment this[_b] or something like that for the _b field. It's tricky because whether it's necessary or not depends on how the constructors are written are whether the constructor itself ended up marking the field (as happened for _a and _c here)
note that public fields won't have this problem, because of their virtual accessors, they should always support hover.

we can probably build on https://dart-review.googlesource.com/#/c/sdk/+/42085, though it'll need a few more tweaks. There's not a sensible node to put the comment on, so we'll have to add an empty statement or something like that, and make sure to filter out all fields that were already mapped by the constructor or by a virtual accessor pair.

@vsmenon ...this is actually worse than I thought. I don't think this can be fixed without Chrome support.
A few problems:
The hover spans for most field initializers above only work inside the constructor, because that's the scope they're marked in.
Even using a comment to mark the span, it doesn't work in a method unless that method already uses the field. I suspect it's because the private field symbol isn't captured in the closure, so V8 thinks the symbol isn't in scope.
Also virtual fields don't work consistently either. Currently, hover for obj.foo (a call site) will show the virtual getter(/setter) and allow jumping/breakpoints and "step into" for field getters/setters. However that breaks hover on the field declaration.
This all makes sense--the whole notion of declaration site hovering is not a thing in JS, because JS doesn't have "declaration site" for fields. (indeed, TypeScript does not map them: https://sokra.github.io/source-map-visualization/#typescript)
We may need to give up on declaration site hovering. (and perhaps we can change stepping on constructor field init so it's only the intiailzier expressions that are marked.)


Add diagnostics from lsp-status plugin

I've created the component to show diagnostics from lsp-status. It differs from built-in LSP diagnostics because it also has info and hints counters.
Also I'm going to create two more components with function name and LSP status from the lsp-status. Shall I create two separate PRs or just add all of that to this one?

One pull request per component would be ideal. Thanks!

After last pull request there are now conflicts. After you solve them I will merge and do some formatting.
I think we should put the lsp-status bubbles in their own folder, what do you think?

I think we should put the lsp-status bubbles in their own folder, what do you think?

Good idea, I'll do it.

Merged. Gonna make some formatting and then merge to master.


Implements prefer english names setting for MapQuest API in config.ini

Which adds English as accepted header to MapQuest requests and results in the response location names being mostly in English not their native country language.
Just to illustrate the case take a look at my terminal logs and the names of the folders changing from Russian and Arabic language into English after setting the new flag in config.ini using nano editor.
Before
$ nano ~/.elodie/config.ini ### I've set prefer_english_names=False

After
$ nano ~/.elodie/config.ini ### I've set prefer_english_names=True
$ rm ~/.elodie/location.json
$ rm ~/.elodie/hash.json

Coverage decreased (-2.2%) to 90.954% when pulling a9a6e4b7048f998cf29a4c09f58580666aae2c3d on DZamataev:master into 91bf1815757322fc91936a96633aa051cff09ac3 on jmathai:master.

Sorry but i'm not much into Python too write good enough unit tests. Will account for the other changes requested and update.

Sounds good. Why don't you make the suggested changes and I will submit a PR to your branch with tests and then I can merge it.

@jmathai I've also added command line argument to put files in different folders like so:

It looks like there is a bug in this code, with bool being used to test the string input.  This will evaluate to True even when False is specified.  See #369.

This bug is fixed in PR 370 and closes issue #369 (Prefer English names logic is broken).
This uses the standard routine distutils.util.strtobool to check the string provided in config.ini.  This will correctly interpret: y, yes, t, true, on, 1, false, n, no, f, false, off, 0 and is case-insensitive.
I'm not sure how this slipped through the tests before...


APS-130: Quick updates to the headings on some sections to make it ea…

…sier for users to understand what they’re doing
Context

Changes in this PR
Quick updates to the headings on some sections to make it easier for users to understand what they’re doing
Workflow becomes becomes "Task Allocation"
"Placement details" becomes "CRU Dashboard"
"Placement requests" becomes "Match"
Screenshots of UI changes
Before

After

Release checklist
As part of our continuous deployment strategy we must ensure that this work is
ready to be released at any point. Before merging to main we must first
confirm:
Pre merge checklist

[ ] Have all changes to any dependencies been deployed to both preprod and
production in a backwards compatible way? (This includes our API,
infrastructure, third-party integrations and any secrets or environment variables)
[ ] Has a required data migration been included in this change or been done in
advance?

Post merge checklist
Once we've merged we now need to release this through to production before
considering it done.
Find the build-and-deploy job in CircleCI
and work through the following steps:

[ ] Has the product manager asked to provide approval for this feature?

[ ] Has the product manager approved?

[ ] Manually approve release to preprod
[ ] Verify change released to preprod
[ ] Manually approve release to prod
[ ] Verify change released to production

Should a release fail at any step, you as the author should now lead the work to
fix it as soon as possible.

Thanks for making the changes, please can you squash the commits before merging?


command bob works for some reason

Getting /usr/lib/ruby/3.0.0/open-uri.rb:364:in open_http': 404 Not Found (OpenURI::HTTPError) from /usr/lib/ruby/3.0.0/open-uri.rb:741:in buffer_open' from /usr/lib/ruby/3.0.0/open-uri.rb:212:in block in open_loop' from /usr/lib/ruby/3.0.0/open-uri.rb:210:in catch' from /usr/lib/ruby/3.0.0/open-uri.rb:210:in open_loop' from /usr/lib/ruby/3.0.0/open-uri.rb:151:in open_uri' from /usr/lib/ruby/3.0.0/open-uri.rb:721:in open' from /usr/lib/ruby/3.0.0/open-uri.rb:29:in open' from /home/dada/Latte/core/latte.rb:15:in getPkgfile' from /home/dada/Latte/core/latte.rb:11:in findPkg' from /home/dada/Latte/core/latte.rb:43:in `'

The error above means there is no such package

The bug here is that is trying to do latte add

closed due to being stale


Fixed "Time until fully vested" display

Summary
Minor fix, but I can assume that after converting all references of TIME to RUG when forking wonderland, you had accidentally replaced Time to Rug. Obviously on the contract the reference for lastRug doesn't exist.
How would you like PR's to be made? Perhaps making a template would be good.

@GhostWalker562 we do not do PRs on master. Please move to dev as your working branch and PR to staging. The pipeline will pick up the PR and create a preview for closed testing and a lead will move it to a release PR on master.


Where is openzeppelin-solidity/contracts/token/ERC20/StandardToken.sol?

I think I'm gonna use ERC20.sol they have the same codes for StandardToken.sol base in this video https://www.youtube.com/watch?v=_ikc4Ct7wvk.

As you can see https://github.com/OpenZeppelin/openzeppelin-solidity/issues/1478, it does not exists anymore. OZv2 has changed a "bit".

This is generally how to achieve the same effect https://github.com/OpenZeppelin/openzeppelin-solidity/blob/master/contracts/examples/SimpleToken.sol

@obernardovieira Yeah im aware.. so what is the replacement of StandardToken.sol?

@snario Yes im using this

2. Find/Replace StandardToken / BurnableToken / MintableToken to ERC20
There's no StandardToken anymore, only ERC20.

Hi,
Please update the docs with the same.
I also created a pull request in Truffle Examples repository to reflect the change
https://github.com/trufflesuite/trufflesuite.com/pull/216

Thank you @pRoy24 for updating the docs! @kennblvnp please see this newly updated section: https://github.com/trufflesuite/trufflesuite.com/blob/master/src/tutorials/robust-smart-contracts-with-openzeppelin.md#creating-the-tutorialtoken-smart-contract

@CruzMolina @pRoy24  thanks everyone!

Thanks a lot everyone for this! :clap:


Fallback code for demo app

Automatically try & switch between DX/Metal/OpenGL/Raster

Display failed layers in Example / PanelLayers


tag ?

Hi,
Can you tag a new version with the latest few fixes ?
Thanks

Latest tag is based off the latest commit (v2.1.2)... There are a few PRs I've not merged yet, though - is that what you're asking for?

@weierophinney Sorry it seems that somehow I could only see tag 2.1.1

I've just tagged 2.2.0 as well: https://github.com/weierophinney/changelog_generator/releases/tag/v2.2.0


Attack Range

After changing /sentinel Attackrange, the sentinel no longer detects targets automatically. It only fights back when damaged.

What'd you change it to 0.o

That's rather short...

most plugins measure distance in blocks. so 2 blocks away for a swords is short? I would have to say your answer is short...

Can I ask what command you used?
/sentinel attackrange isn't a command.

Awaiting response:
Type below once you have a response and we'll reopen and continue this issue :)


Update utils.py

change some words and expressions in docstrings of utils.py.

Good job, but some of the modifications are not clear or should be drawn back.


Create the Account and Vendor data containers

Wrote an Account class that has the designated fields associated with a billing configuration account. Created a Vendor class that has the designated fields associated with a billing configuration vendor.

@googlebot I signed it!


Prepare build pipeline for new version of Testcontainers .NET, closes…

I added the first part of the build pipeline, see #41. I will create new issues for the remaining tasks, tomorrow.
@isen-ng I already removed the the StyleCop configurations. I guess it is enough to put your .editorconfig into the project.
@swissarmykirpan Could you please update appveyor.yml? You just have call the Cake tasks in the single AppVeyor stages, like (for Unix use build.sh):

build.ps1 --target=Clean.
build.ps1 --target=Restore-NuGet-Packages.
build.ps1 --target=Build.
build.ps1 --target=Test.

You will find the test results in test-results and the coverage file in test-coverage.

@swissarmykirpan need your approval or dismissal of your review to merge this.

apologies, guys - I should have approved and merged this one first, but saw the message too late!

Sorry Andre, I managed to rebase your branch against develop successfully!

This is now mergable again!

As I said, those changes are inconsistent line endings and ok. We should merge them, or we will get them within another PR. Every file is lf expect those two.


test

Codecov Report

Merging #2 (5604ceb) into main (5d1a722) will increase coverage by 8.54%.
The diff coverage is 42.94%.

@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
+ Coverage   42.23%   50.77%   +8.54%
==========================================
  Files          21       28       +7
  Lines         457      451       -6
==========================================
+ Hits          193      229      +36
+ Misses        264      222      -42

Impacted Files
Coverage Δ

lib/src/parser/json/author.dart
100.00% <ø> (ø)

lib/src/parser/json/author.g.dart
100.00% <ø> (ø)

lib/src/parser/json/catalogEntry.dart
0.00% <ø> (ø)

lib/src/parser/json/catalogEntry.g.dart
0.00% <ø> (ø)

lib/src/parser/json/chapter.dart
40.90% <0.00%> (ø)

lib/src/parser/json/chapterID.g.dart
50.00% <ø> (ø)

lib/src/parser/json/id.g.dart
100.00% <ø> (ø)

lib/src/parser/json/post.g.dart
100.00% <ø> (ø)

lib/src/parser/sources/parseSource.dart
0.00% <0.00%> (ø)

lib/src/scraper/eval.dart
0.00% <0.00%> (ø)

... and 18 more

Continue to review full report at Codecov.

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


Method System.Numerics.Vector2 ImGuiNET.ImGui.CalcTextSize(System.String) Not Found.

After upgrading from 1.88 to 189.6 I get the following error when trying to use Imgui.CalcTextSize :
{"Method not found: 'System.Numerics.Vector2 ImGuiNET.ImGui.CalcTextSize(System.String)'."}
Any ideas?

you may wanna re-compile the whole project. What we did going from 1.88 to 1.89+ is a backward incompatible change.
Following is the code I tested and it works fine on my side.

            string abc = "foo";
            var kkk = ImGui.CalcTextSize(abc);
            ImGui.Text(kkk.ToString());

Please share the code here so I can reproduce the issue on my side.

Crap you are right, I was using a local imgui.net dll on one of my projects. Works as intended.


update addon status from more than one collectors

Signed-off-by: marcolan018<EMAIL_ADDRESS>https://issues.redhat.com/browse/ACM-1930

/retest


The same code and input will have different results in different environments.

In both environments, the results for text are the same, but the results for images will be significantly different. . .

Why does this happen?

The same input, after passing this function, the result becomes different.


kinematics_config argument is needed?

Trying to use it on real robot with Moveit, and I am trying to use it with limited version since otherwise it can create unwanted dangerous situations.
However even though I can connect to robot with certain IP, when run the command suggested I got this error
roslaunch ur_robot_driver ur5_bringup.launch robot_ip:=<IP_ADDRESS> limited:=true
unused args [kinematics_config] for include of [/home/meric/c_ws/src/universal_robot/ur_description/launch/ur5_upload.launch]
The traceback for the exception was written to the log file

Any Ideas?

please say how you solved it


[Feat] Badge

custom properties:

Header string
Appearance NotificationType
IsOpaque

effect:

A badge control is not a bad idea but to be more useful, I think it should be a control that could be shown on another like this :

Otherwise it multiply controls for something people's can do themselves too easily 🤔

i think that could be InfoBadge
these changes are indeed not so useful :(


Add tensor compare ops

e.g. where, clamp, clamp_min, clamp_max

Please hold on. I m porting a suite, which gated clamp's bugs on IPEX.

https://github.com/intel/torch-xpu-ops/pull/81

All comments in https://github.com/intel/torch-xpu-ops/pull/47 have been resolved.


Support Python >3.5

Installing fails using Python 3.6 and later as provided in current conda distribution. Bottleneck package dependency seems to fail to install.

I'd love to see the requirement for bottleneck fall off. Packages consumers can still use it, and the codebase is already set up to eagerly load it if available in the environment, else fall back to numpy.
@twiecki and team, open to maintaining bottleneck support but dropping it as a requirement ? We've seen some packaging issues with it (off an on) over the years.

Yes, should be optional.

@seanlseymour I may work on a PR later this week, unless you have already started on it.

No, I haven’t started anything here. Would appreciate!
Sean

On Aug 21, 2019, at 3:30 PM, Calvin DeBoer<EMAIL_ADDRESS>wrote:
@seanlseymour I may work on a PR later this week, unless you have already started on it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you!

On Aug 23, 2019, at 1:59 PM, Thomas Wiecki<EMAIL_ADDRESS>wrote:
Closed #113 https://github.com/quantopian/empyrical/issues/113 via #115 https://github.com/quantopian/empyrical/pull/115.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/quantopian/empyrical/issues/113?email_source=notifications&email_token=ADAIU6LQFNJO2JUE5ATRTXTQGBFSXA5CNFSM4ILN2MJ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTHKHPYQ#event-2580838370, or mute the thread https://github.com/notifications/unsubscribe-auth/ADAIU6IVOYMHTOLRF4O5FDDQGBFSXANCNFSM4ILN2MJQ.

@cgdeboer I'm new maintainer of bottleneck and would appreciate it if you could open an issue with some details on the packaging issues you've encountered, as the upcoming release of 1.3.0 should solve them: https://github.com/pydata/bottleneck


Add documentation to ShardCloseCode and AuditLogEventType

Summary
Added documentation to ShardCloseCode and AuditLogEventType
Checklist

[x] I have run nox and all the pipelines have passed.
[x] I have made unittests according to the code I have added/modified/deleted.

Related issues
Nothing related.

Also, changelog fragment is missing :)

@davfsa

I am not too sure about adding documentation to the shard close codes, but I wouldn't mind it. It seems a bit arbitrary

What about the 4000-4999? as found here mdn it does state that those close codes are private, and therefore unique. I was thinking adding it to all of them just looked nicer imo.

Yeah, that's part of the spec, 4xxx range is for individual use after agreement. It's fine leaving them documented ig.
Would you mind fixing the docstring issue (wrapping with triple quotes instead of single) and I think this is good to merge

was literally just doing that right now haha.


Navigation controls not working

In my dashboards I have navigation buttons to navigate between dashboards and copy filters from one to the other. This works in DSZ but in DSW clicking the button calls a request but it doesn't do anything
Here is my navigation button. It uses parameter SETTINGS and $$$FILTERS token
<control name="" action="navigate" target="*" targetProperty="_DeepSee.UserPortal.DashboardViewer.zen?DASHBOARD=fnb_ds_dashboard_hosp_pohybyPacienta/PrevzatZ.dashboard&SETTINGS=FILTER:$$$FILTERS" location="widget" type="auto" controlClass="" label="Převzat Z" title="Podle vybraných omezení zobrazí interní překlady Na pracoviště" value="" text="" readOnly="false" valueList="" displayList="" activeWhen="">       <valueRequired>false</valueRequired>     </control>
If it is not possible to use this button, is there another way to implement navigation in DSW?

Hi, @sacen ! Only "New window" navigate control is supported at the moment. You can try to use it for your dashboard. But hope we'll add the support of other controls in near future or you can make it and send the pull request.

@sacen, you can join skype and provide the case with your issue to let us fix it.


builder: Include font build dependencies in meta table

I'm contemplating storing the build dependencies in every font's "meta" table. We have a situation where many designers haven't pinned the dependencies so we don't truly know what was used. By genning this table at build time, we can be certain of the dependencies.
I've just checked pyftsubset and it'll drop this table by default, which seems like something we'd want to do for this use case. I'd love the fonts in the google/fonts repo to have this table. I don't mind if the fonts on fonts.google.com don't have it.
I've talked about this idea with Cosimo but I'm interested in hearing from everyone else.
This idea has already been discussed in 2017, https://github.com/googlefonts/fontmake/issues/251.
In the next post, I'll workout how big this table will be using Cosimo's dependency lister, https://gist.github.com/anthrotype/531a425c8a0ba5ee975bc2ec8add7b82

Using Cosimo's script, we get the following sizes:
gftools: 2kb, 1kb (zipped)
fontmake: 369b, 438b (zipped)
I'll see what size I can get the gftools deps down if I remove the dependencies which are not used for generating fonts.

Actually, Idk if it's worth bothering trying to compress gftools more than just zipping it since the fonts we serve won't have this data. Are we able to spare 1kb?

of course you want either gftools or fontmake, not both, since fontmake is a dependency of gftools, you probably only want gftools' deps.

the dependencies which are not used for generating fonts.

you could place things in extras..  maybe the gftools builder should be in its own distribution..

Idk if it's worth bothering trying to compress

only if you care about retaining the data for shipping fonts, which I think we do not want

of course you want either gftools or fontmake, not both, since fontmake is a dependency of gftools, you probably only want gftools' deps.

The size results I've posted were done by running your gist on gftools and fontmake separately. the gftools dependencies will list fontmake. Personally, I'd prefer if we use the gftools deps since it includes vttLib, ttfautohinter etc so it'll make remaking the fonts much easier,

Idk if it's worth bothering trying to compress

only if you care about retaining the data for shipping fonts, which I think we do not want

Exactly so I'm tempted to leave it as is. Shall I go ahead and open a draft pr with a sketch?


Add Schemas as a submodule of www.openmicroscopy.org

Replaces https://github.com/ome/www.openmicroscopy.org/pull/286 but with the same goal i.e. re-include the published OME schemas under www.openmicroscopy.org/Schemas/ as part of the static Jekyll website.
As opposed to #286, most of the logic has been migrated to a submodule which is included in this repository (like https://github.com/ome/www.openmicroscopy.org/pull/403).
Summarizing the main features:

https://github.com/ome/schemas/commit/3cfad445e0e781a7e3053d0b92a9e97d1d7114c9 extracts the history of the publish script used for generating the www.openmicroscopy.org/Schemas pages
https://github.com/ome/schemas/commit/b93e63d01ed4f6c8a1cca5383b87e478225447d0 adds some Maven infrastructure for consuming org.openmicroscopy:specification and building the HTML pages
https://github.com/ome/schemas/commit/320f4555de00e71076001bb93c6e62c40b0bdf0e adds a GitHub action to generate the /Schemas page and auto-push the changes on push to master - see https://github.com/ome/schemas/commit/151dac31d982597b8847b793d6dbc87d3406b4a5 for an example
https://github.com/ome/schemas/blob/master/.github/dependabot.yml configures GitHub dependabot to open PRs on new releases of the specification/plugins - see https://github.com/ome/schemas/pull/1 followed byhttps://github.com/ome/schemas/commit/fdc888ead257b1a8dad0017075fb2e37426fc2d4 for an example of how this logic should keep the Schemas in sync with the released artifact

From the HEAD of this branch, building locally gives me

This certainly matches my expectations from #403 but is even simpler. As mentioned elsewhere, I can see doing something more advanced for future versions (e.g. schemas.openmicroscopy.org) but this information will need to remain available at /Schemas permanently. This seems like a good way of doing it. :+1:

Now staged at https://snoopycrimecop.github.io/www.openmicroscopy.org/Schemas/ for review


Fix Gradient warning

Type Gradient needs to have a [Serializable] annotation for property drawer integration to work
UnityEngine.Debug:LogError(Object)
FullInspector.Internal.fiGenericPropertyDrawerPropertyEditor`2:.ctor() (at /Users/jdufault/Personal/FI/Project/Assets/FullInspector2/Core/Editor/PropertyEditors/fiGenericPropertyDrawerPropertyEditorManager.cs:24)
FullInspector.Internal.GradientPropertyEditor:.ctor()

See http://forum.unity3d.com/threads/full-inspector-inspector-and-serialization-for-structs-dicts-generics-interfaces.224270/page-26#post-2666048

Looks like there is already a "UnityEngine" namespace check which I've verified covers Gradient. The latest build in Access should have the code.


rcar_h3ulcb: can: failed to run RTR test cases

Describe the bug
While running tests/drivers/can/api test cases on Renesas R-Car platforms, the test suite fail on RTR related tests added with #47903.
The CAN controller that is equipping these boards is not able to support standard ID frames, extended ID frames & remote frames at the same time.
When the driver has been written, we then chosen to support std id and ext id frames but not remote frames.
With the new test cases, CAN API test suite is now failing on send_receive_rtr, test_send_receive_std_id_rtr and test_send_receive_ext_id_rtr when ran on R-Car boards.
RTR related test cases should maybe be disabled for R-Car boards.
To Reproduce

west build -b rcar_h3ulcb_cr7 tests/drivers/can/api/
(terminal n°2) picocom -b 115200 /dev/ttyUSB0
west flash
(terminal n°2) See timeout

or

./scripts/twister -p rcar_h3ulcb_cr7 --device-testing -T tests/drivers/can/api/ --device-serial /dev/ttyUSB0 -vv -i
See error

Expected behavior
Test case should pass as expected.
Impact
The test case drivers.can.api failing, complete twister test suite is then also concerned and is reporting errors.
Logs and console output
DEBUG   - DEVICE: *** Booting Zephyr OS build zephyr-v3.1.0-5073-g7dc414e0cb9a  ***
DEBUG   - DEVICE: Running TESTSUITE can_api
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_add_filter
DEBUG   - DEVICE: PASS - test_add_filter in 0.001 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_filters_added_while_stopped
DEBUG   - DEVICE: PASS - test_filters_added_while_stopped in 0.037 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_filters_preserved_through_bitrate_change
DEBUG   - DEVICE: PASS - test_filters_preserved_through_bitrate_change in 0.076 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_filters_preserved_through_mode_change
DEBUG   - DEVICE: PASS - test_filters_preserved_through_mode_change in 0.035 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_get_capabilities
DEBUG   - DEVICE: PASS - test_get_capabilities in 0.001 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_get_core_clock
DEBUG   - DEVICE: PASS - test_get_core_clock in 0.001 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_get_state
DEBUG   - DEVICE: PASS - test_get_state in 0.001 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_max_ext_filters
DEBUG   - DEVICE: PASS - test_max_ext_filters in 0.001 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_max_std_filters
DEBUG   - DEVICE: PASS - test_max_std_filters in 0.001 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_receive_timeout
DEBUG   - DEVICE: PASS - test_receive_timeout in 0.103 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_recover
DEBUG   - DEVICE: PASS - test_recover in 0.001 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_recover_while_stopped
DEBUG   - DEVICE: PASS - test_recover_while_stopped in 0.037 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_and_forget
DEBUG   - DEVICE: PASS - test_send_and_forget in 0.002 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_callback
DEBUG   - DEVICE: PASS - test_send_callback in 0.002 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_invalid_dlc
DEBUG   - DEVICE: E: DLC of 9 exceeds maximum (8)
DEBUG   - DEVICE: PASS - test_send_invalid_dlc in 0.003 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_ext_id
DEBUG   - DEVICE: PASS - test_send_receive_ext_id in 0.009 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_ext_id_masked
DEBUG   - DEVICE: PASS - test_send_receive_ext_id_masked in 0.004 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_ext_id_rtr
DEBUG   - Waiting for device rcar_h3ulcb_cr7 to become available
DEBUG   - DEVICE:
DEBUG   - DEVICE: Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/can/api/src/main.c:667: send_receive_rtr: (err not equal to 0)
DEBUG   - DEVICE: receive timeout
DEBUG   - DEVICE: FAIL - test_send_receive_ext_id_rtr in 0.230 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_msgq
DEBUG   - DEVICE: PASS - test_send_receive_msgq in 0.018 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_std_id
DEBUG   - DEVICE: PASS - test_send_receive_std_id in 0.004 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_std_id_masked
DEBUG   - DEVICE: PASS - test_send_receive_std_id_masked in 0.004 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_std_id_rtr
DEBUG   - DEVICE:
DEBUG   - DEVICE: Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/can/api/src/main.c:667: send_receive_rtr: (err not equal to 0)
DEBUG   - DEVICE: receive timeout
DEBUG   - DEVICE: FAIL - test_send_receive_std_id_rtr in 0.235 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_send_receive_wrong_id
DEBUG   - Waiting for device rcar_h3ulcb_cr7 to become available
DEBUG   - Timed out while monitoring serial output on rcar_h3ulcb_cr7
DEBUG   - run status: rcar_h3ulcb_cr7/tests/drivers/can/api/drivers.can.api error
INFO    - 4/6 rcar_h3ulcb_cr7           tests/drivers/can/api/drivers.can.api              FAILED No Console Output(Timeout) (device 64.741s)

Environment (please complete the following information):

OS: Linux Ubuntu 20.04
Zephyr SDK 0.15.0
Commit SHA : anything at the top of 097cb049168137f8d2c7520363d0b43803197578 (sha from main)

@aaillet If I understand correctly, this is an issue in the receive path where the R-Car CAN controller supports two RX FIFOs, which are currently configured for STD ID data frames in FIFO0, and EXT ID data frames in FIFO1?

@aaillet If I understand correctly, this is an issue in the receive path where the R-Car CAN controller supports two RX FIFOs, which are currently configured for STD ID data frames in FIFO0, and EXT ID data frames in FIFO1?

Yes, exactly !
Each FIFO is configured by two registers:

IDE to select STD or EXT ID
RTR to select between data and remote frames

As you said, current configuration is:

FIFO0 accepting STD ID data frames
FIFO1 accepting EXT ID data frames

@aaillet Please see #50286 for a proposed fix.


NO-ISSUE: Fix the rpm copr repository to stable branch

Oh, I updated the building-images.md acordingly, this needs re-approval.


A little more information about cli-client?

Since I'm still debugging why the mic doesn't respond, it would be helpful to add a note about how to actually access the cli-client in the section where you introduce that.
I tried ./start-mycroft.sh cli but got a bunch of errors.
I tried running ovos-cli-client and got this log:

2023-03-03 00:57:15.430 - OVOS - ovos_config.models:load_local:95 - DEBUG - Configuration /home/ovos/.local/lib/python3.9/site-packages/mycroft/configuration/mycroft.conf loaded
2023-03-03 00:57:15.578 - OVOS - ovos_config.models:load_local:99 - DEBUG - Configuration '/etc/mycroft/mycroft.conf' not defined, skipping
2023-03-03 00:57:15.713 - OVOS - ovos_config.models:load_local:99 - DEBUG - Configuration '/home/ovos/.config/mycroft/web_cache.json' not defined, skipping
2023-03-03 00:57:15.859 - OVOS - ovos_config.models:load_local:95 - DEBUG - Configuration /home/ovos/.config/mycroft/mycroft.conf loaded
2023-03-03 00:57:16.005 - OVOS - ovos_config.models:load_local:99 - DEBUG - Configuration '/etc/xdg/mycroft/mycroft.conf' not defined, skipping
2023-03-03 00:57:16.146 - OVOS - ovos_config.models:load_local:99 - DEBUG - Configuration '/home/ovos/.mycroft/mycroft.conf' not defined, skipping
Traceback (most recent call last):
  File "/home/ovos/.local/bin/ovos-cli-client", line 5, in <module>
    from ovos_cli_client.__main__ import main
  File "/home/ovos/.local/lib/python3.9/site-packages/ovos_cli_client/__main__.py", line 24, in <module>
    from ovos_cli_client.text_client import (
  File "/home/ovos/.local/lib/python3.9/site-packages/ovos_cli_client/text_client.py", line 37, in <module>
    locale.setlocale(locale.LC_ALL, "")  # Set LC_ALL to user default
  File "/usr/lib/python3.9/locale.py", line 610, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting

Nevermind, I figured it out by changing my etc/default/locale file like they did in the answer to this question

Also, did you set the locale with sudo raspi-config

Yes, I used sudo raspi-config.

If you set those devices as active using alsamixer do you get any change?

Here's what I tried:
alsamixer
F3 (Show playback controls)
F6 (Select sound card)
Selected UACDemoV1.0
Enter
F4 (Show capture controls)
F6 (Select sound card)
Selected USB Camera-B<IP_ADDRESS>
Enter
At this point it exits alsamixer and I get the error:
cannot load mixer: Invalid argument

Try a reboot and see if things load properly after that.  There may need to be a .asoundrc file according to this site
https://9to5answer.com/alsamixer-cannot-open-mixer-invalid-argument

I tried reboot but that didn't change anything. I have followed the steps there but when I run ovos@raspberrypi:/etc $ cat /proc/asound/cards  I see
                      bcm2835 Headphones
 1 [vc4hdmi        ]: vc4-hdmi - vc4-hdmi
                      vc4-hdmi
 2 [CameraB409241  ]: USB-Audio - USB Camera-B<IP_ADDRESS>
                      OmniVision Technologies, Inc. USB Camera-B<IP_ADDRESS> at usb-3f980000.usb-1.3, hi
 3 [UACDemoV10     ]: USB-Audio - UACDemoV1.0
                      Jieli Technology UACDemoV1.0 at usb-3f980000.usb-1.4, full speed

I tried changing the values in asound.conf to 2 or 3 but no difference so far.

No, both say pa_context_connect() failed: Connection refused

Pulseaudio is not running
systemctl --user restart pulseaudio

you may also have to disable suspend-on-idle in default.pa also
sudo sed -i -e "s/^load-module module-suspend-on-idle/#load-module module-suspend-on-idle/" /etc/pulse/default.pa
systemctl --user restart pulseaudio

@dickorydock Has this been resolved?

I believe that these have been resolved in the dev branch.  I am closing this but feel free to open another with new information


Not able to connect with fleet API from different region - IN

Tried to get the vehicle data after authentication using access_token, getting below error while calling vet API. Any solution?
Steps followed:

https://auth.tesla.com/oauth2/v3/authorize 👍
https://auth.tesla.com/oauth2/v3/token 👍
https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles ❌ 👇

{
  "error": "Account 183156b7d536-4458-9e56-b9a70d90a5b5 must be registered in the current region https://fleet-api.prd.na.vn.cloud.tesla.com, please see https://developer.tesla.com/docs/fleet-api#register"
}

Have you called the /api/1/partner_accounts endpoint with your partner authentication token?
https://developer.tesla.com/docs/fleet-api#register

I have same problem , did you solve it ?

Have you called the endpoint the message links to? It completes registration of your developer account.
https://developer.tesla.com/docs/fleet-api#register

Have you called the endpoint the message links to? It completes registration of your developer account.
https://developer.tesla.com/docs/fleet-api#register
Yes
1, I put the key, https:///.well-known/appspecific/com.tesla.3p.public-key.pem.

I run this code by using node js.
const myHeaders = new Headers();
myHeaders.append("Content-Type", "application/json");
myHeaders.append("Authorization", Bearer ${process.env.TESLA_API_TOKEN});

const body = JSON.stringify({
"domain": "my domain"
});
const requestOptions = {
method: 'POST',
headers: myHeaders,
body,
redirect: 'follow'
};
fetch("https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts", requestOptions)
.then(response => response.json())
.then(result => console.log(result))
.catch(error => console.log('error', error));
Am I wrong ?

Have you called the endpoint the message links to? It completes registration of your developer account.
https://developer.tesla.com/docs/fleet-api#register

Do I need to install Tesla Vehicle Command SDK ?

@zerocooling I emailed you. You seem to have not called the endpoint with a partner authentication token.

Can you please take a look , which part I need to fix ?
nst myHeaders = new Headers();
myHeaders.append("Content-Type", "application/json");
myHeaders.append("Authorization", Bearer ${process.env.AUTHORIZATION_TOKEN} );
const body = JSON.stringify({
"domain": "
https://tesla-watch-app.com/.well-known/appspecific/com.tesla.3p.public-key.pem
."
});
const requestOptions = {
method: 'POST',
headers: myHeaders,
body,
redirect: 'follow'
};
fetch("https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts",
requestOptions)
.then(response => response.json())
.then(result => console.log(result))
.catch(error => console.log('error', error));
2024년 2월 17일 (토) 오후 4:17, Patrick Demers @.***>님이 작성:

@zerocooling https://github.com/zerocooling I emailed you. You seem to
have not called the endpoint with a partner authentication token.
—
Reply to this email directly, view it on GitHub
https://github.com/teslamotors/vehicle-command/issues/176#issuecomment-1950613884,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABR4W4X34ZDPFTHCZ4ATYVTYUFCARAVCNFSM6AAAAABDEGUDYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGYYTGOBYGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Is the AUTHORIZATION_TOKEN coming from a call to POST https://auth.tesla.com/oauth2/v3/token?
Have you confirmed environment variable is being loaded correctly?
Your domain should just be tesla-watch-app.com.
What response are you getting from your call?

Is the AUTHORIZATION_TOKEN coming from a call to POST
https://auth.tesla.com/oauth2/v3/token? -
{"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InE0dHg3Q1UyYzI2V1BiemwxZjZjanM3QnhzayJ9.eyJpc3MiOiJodHRwczovL2F1dGgudGVzbGEuY29tL29hdXRoMi92My9udHMiLCJhenAiOiIyMjQ0ZDIxYjZjZWUtNDRhOC04YTE0LTBjZmNmNjBhMWVjNSIsInN1YiI6ImI5ZWY0YjQwLWZjNTktNGM5Ny1iZDQyLWJmNDQxN2Q1NzdlYiIsImF1ZCI6WyJodHRwczovL2ZsZWV0LWFwaS5wcmQubmEudm4uY2xvdWQudGVzbGEuY29tIiwiaHR0cHM6Ly9mbGVldC1hcGkucHJkLmV1LnZuLmNsb3VkLnRlc2xhLmNvbSIsImh0dHBzOi8vYXV0aC50ZXNsYS5jb20vb2F1dGgyL3YzL3VzZXJpbmZvIl0sInNjcCI6WyJ2ZWhpY2xlX2RldmljZV9kYXRhIl0sImFtciI6WyJwd2QiLCJtZmEiLCJvdHAiXSwiZXhwIjoxNzA4MjQ3NzI3LCJpYXQiOjE3MDgyMTg5MjcsIm91X2NvZGUiOiJOQSIsImxvY2FsZSI6ImVuLVVTIiwiYXV0aF90aW1lIjoxNzA4MjE4OTI3fQ.gAjNcjd_OqrFD_Mkh3c7hc0wjzsJI4BUom0wsQVUTn2yLdwb5jXv4jlvjy87aq4k7sq7tkCFBtQYl78rkaulNwBCw7cfZaGyEA24eqBpF2v2zaFKiQw9XKNhlUJhhiKHJLk-fal-WR3Fgl-lBi4C-YO_dRSUZn3tm_-fFKFeaNaMBlC0la3NCdd4NjH-XYVESwOCY5B3sdn6tDeiFyvqjtUaZf11ka71jGOEHKfZLLUS4_aAs_4SQXMpNElghc7oWuVdUa3q6Q--2v65X-5JAP1MM6LW14ZyQD_ikgaRYLFPe79uoD9NnkT7lI2xWBX4zMgNmkWlsZ3GU-h7CcgDcA","id_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InE0dHg3Q1UyYzI2V1BiemwxZjZjanM3QnhzayJ9.eyJpc3MiOiJodHRwczovL2F1dGgudGVzbGEuY29tL29hdXRoMi92My9udHMiLCJhdWQiOiIyMjQ0ZDIxYjZjZWUtNDRhOC04YTE0LTBjZmNmNjBhMWVjNSIsInN1YiI6ImI5ZWY0YjQwLWZjNTktNGM5Ny1iZDQyLWJmNDQxN2Q1NzdlYiIsImV4cCI6MTcwODI0NzcyNywiaWF0IjoxNzA4MjE4OTI3LCJhdXRoX3RpbWUiOjE3MDgyMTg5MjcsImFtciI6WyJwd2QiLCJtZmEiLCJvdHAiXSwidXBkYXRlZF9hdCI6MTY1ODM3ODU4MH0.yHFUlM8rzH7o1lvAx3_T2uBUomFsJ7v4uGapnocC_U8lRXiotep6BbniCTjVTyJXNxDmw0bsEVIl7lHXfDPdV_zrCLtu5j2UCFZbwAPeScx1VM_cDh_2SSE9vST-eS-5EvlC5yNIIyzqf9fkGsmkmwro8vSTp6ZLNqSs3cgOWW1RF4KnlUlpVNugTG_xVWo7EHaM8-ViZCJBuuyJcHfe3HBgasft0JjbH2KO8AuOmt-OInLayXXeHlxML_k4kPqvCwuMLWdoihBOnhRlNZqeWmp3t08zEkIM0RzVXSfrgyeVqd4cxqTAd_useVeElt2gRgerGbSLl53Rmw3e4x_VXA","expires_in":28800,"state":"CA","token_type":"Bearer"}
   *  I took the access token*

Have you confirmed environment variable is being loaded correctly?

Yes

Your domain should just be tesla-watch-app.com.

I changed "telsa-watch-app.com"

What response are you getting from your call?

error: 'Account 2244d21b6cee-44a8-8a14-0cfcf60a1ec5 must be
registered in the current region
https://fleet-api.prd.na.vn.cloud.tesla.com, please see
https://developer.tesla.com/docs/fleet-api#register'

2024년 2월 17일 (토) 오후 5:05, Patrick Demers @.***>님이 작성:

Is the AUTHORIZATION_TOKEN coming from a call to POST
https://auth.tesla.com/oauth2/v3/token?
Have you confirmed environment variable is being loaded correctly?
Your domain should just be tesla-watch-app.com.
What response are you getting from your call?

—
Reply to this email directly, view it on GitHub
https://github.com/teslamotors/vehicle-command/issues/176#issuecomment-1950686458,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABR4W4XJ4ALN7O67JB2TBU3YUFHWVAVCNFSM6AAAAABDEGUDYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGY4DMNBVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Also, this is post file
// The data you want to send via POST
$fields = [
'grant_type' => 'authorization_code',
'client_id' => '2244d21b6cee-44a8-8a14-0cfcf60a1ec5',
'client_secret' => 'ta-secret.Ty5STbtXNq$***',
'code' => $code,
'audience' => 'https://fleet-api.prd.na.vn.cloud.tesla.com',
'redirect_uri' => 'http://localhost:8012/redirect',
'scope' => 'openid offline_access user_data vehicle_device_data
vehicle_cmds vehicle_charging_cmds'
];
    // URL to send the POST request to
    $url = 'https://auth.tesla.com/oauth2/v3/token';

    // Initialize cURL session
    $ch = curl_init($url);

    $headers = [
        'Content-Type: application/x-www-form-urlencoded'
    ];

    // Set cURL options
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_HEADER,$headers);
    curl_setopt($ch, CURLOPT_POST, true);
    curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));

    // Execute the POST request
    $response = curl_exec($ch);

2024년 2월 17일 (토) 오후 5:18, jeong-min lee @.***>님이 작성:

Is the AUTHORIZATION_TOKEN coming from a call to POST
https://auth.tesla.com/oauth2/v3/token? -
{"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InE0dHg3Q1UyYzI2V1BiemwxZjZjanM3QnhzayJ9.eyJpc3MiOiJodHRwczovL2F1dGgudGVzbGEuY29tL29hdXRoMi92My9udHMiLCJhenAiOiIyMjQ0ZDIxYjZjZWUtNDRhOC04YTE0LTBjZmNmNjBhMWVjNSIsInN1YiI6ImI5ZWY0YjQwLWZjNTktNGM5Ny1iZDQyLWJmNDQxN2Q1NzdlYiIsImF1ZCI6WyJodHRwczovL2ZsZWV0LWFwaS5wcmQubmEudm4uY2xvdWQudGVzbGEuY29tIiwiaHR0cHM6Ly9mbGVldC1hcGkucHJkLmV1LnZuLmNsb3VkLnRlc2xhLmNvbSIsImh0dHBzOi8vYXV0aC50ZXNsYS5jb20vb2F1dGgyL3YzL3VzZXJpbmZvIl0sInNjcCI6WyJ2ZWhpY2xlX2RldmljZV9kYXRhIl0sImFtciI6WyJwd2QiLCJtZmEiLCJvdHAiXSwiZXhwIjoxNzA4MjQ3NzI3LCJpYXQiOjE3MDgyMTg5MjcsIm91X2NvZGUiOiJOQSIsImxvY2FsZSI6ImVuLVVTIiwiYXV0aF90aW1lIjoxNzA4MjE4OTI3fQ.gAjNcjd_OqrFD_Mkh3c7hc0wjzsJI4BUom0wsQVUTn2yLdwb5jXv4jlvjy87aq4k7sq7tkCFBtQYl78rkaulNwBCw7cfZaGyEA24eqBpF2v2zaFKiQw9XKNhlUJhhiKHJLk-fal-WR3Fgl-lBi4C-YO_dRSUZn3tm_-fFKFeaNaMBlC0la3NCdd4NjH-XYVESwOCY5B3sdn6tDeiFyvqjtUaZf11ka71jGOEHKfZLLUS4_aAs_4SQXMpNElghc7oWuVdUa3q6Q--2v65X-5JAP1MM6LW14ZyQD_ikgaRYLFPe79uoD9NnkT7lI2xWBX4zMgNmkWlsZ3GU-h7CcgDcA","id_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InE0dHg3Q1UyYzI2V1BiemwxZjZjanM3QnhzayJ9.eyJpc3MiOiJodHRwczovL2F1dGgudGVzbGEuY29tL29hdXRoMi92My9udHMiLCJhdWQiOiIyMjQ0ZDIxYjZjZWUtNDRhOC04YTE0LTBjZmNmNjBhMWVjNSIsInN1YiI6ImI5ZWY0YjQwLWZjNTktNGM5Ny1iZDQyLWJmNDQxN2Q1NzdlYiIsImV4cCI6MTcwODI0NzcyNywiaWF0IjoxNzA4MjE4OTI3LCJhdXRoX3RpbWUiOjE3MDgyMTg5MjcsImFtciI6WyJwd2QiLCJtZmEiLCJvdHAiXSwidXBkYXRlZF9hdCI6MTY1ODM3ODU4MH0.yHFUlM8rzH7o1lvAx3_T2uBUomFsJ7v4uGapnocC_U8lRXiotep6BbniCTjVTyJXNxDmw0bsEVIl7lHXfDPdV_zrCLtu5j2UCFZbwAPeScx1VM_cDh_2SSE9vST-eS-5EvlC5yNIIyzqf9fkGsmkmwro8vSTp6ZLNqSs3cgOWW1RF4KnlUlpVNugTG_xVWo7EHaM8-ViZCJBuuyJcHfe3HBgasft0JjbH2KO8AuOmt-OInLayXXeHlxML_k4kPqvCwuMLWdoihBOnhRlNZqeWmp3t08zEkIM0RzVXSfrgyeVqd4cxqTAd_useVeElt2gRgerGbSLl53Rmw3e4x_VXA","expires_in":28800,"state":"CA","token_type":"Bearer"}
   *  I took the access token*

Have you confirmed environment variable is being loaded correctly?

Yes

Your domain should just be tesla-watch-app.com.

I changed "telsa-watch-app.com"

What response are you getting from your call?

error: 'Account 2244d21b6cee-44a8-8a14-0cfcf60a1ec5 must be
registered in the current region
https://fleet-api.prd.na.vn.cloud.tesla.com, please see
https://developer.tesla.com/docs/fleet-api#register'

2024년 2월 17일 (토) 오후 5:05, Patrick Demers @.***>님이 작성:

Is the AUTHORIZATION_TOKEN coming from a call to POST
https://auth.tesla.com/oauth2/v3/token?
Have you confirmed environment variable is being loaded correctly?
Your domain should just be tesla-watch-app.com.
What response are you getting from your call?

—
Reply to this email directly, view it on GitHub
https://github.com/teslamotors/vehicle-command/issues/176#issuecomment-1950686458,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABR4W4XJ4ALN7O67JB2TBU3YUFHWVAVCNFSM6AAAAABDEGUDYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGY4DMNBVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

1.Is the AUTHORIZATION_TOKEN coming from a call to POST https://auth.tesla.com/oauth2/v3/token?
token is fine
2.Have you confirmed environment variable is being loaded correctly?
I checked it
3.Your domain should just be tesla-watch-app.com.
ok
4.What response are you getting from your call?
I still got the same error, even I changed us, eu, and cn.
{
error: 'Account 2244d21b6cee-44a8-8a14-0cfcf60a1ec5 must be registered in the current region https://fleet-api.prd.na.vn.cloud.tesla.com, please see https://developer.tesla.com/docs/fleet-api#register'
}

Simple script I just verified to be working. The curl snippets in documentation also work just fine.
const TOKEN_URL = 'https://auth.tesla.com/oauth2/v3/token'
const REGISTER_URL = 'https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts';

const { CLIENT_ID, CLIENT_SECRET, AUDIENCE, DOMAIN } = process.env;

const run = async () => {
    const urlencoded = new URLSearchParams();
    urlencoded.append("scope", "openid vehicle_device_data vehicle_cmds offline_access");
    urlencoded.append("audience", AUDIENCE);
    urlencoded.append("grant_type", "client_credentials");
    urlencoded.append("client_id", CLIENT_ID);
    urlencoded.append("client_secret", CLIENT_SECRET);

    const {access_token} = await fetch(TOKEN_URL, {
        body: urlencoded,
        method: 'POST',
        headers: {
            'Content-Type': 'application/x-www-form-urlencoded'
        }
    }).then(res => res.json());

    const res = await fetch(REGISTER_URL, {
        body: JSON.stringify({domain: DOMAIN}),
        method: 'POST',
        headers: {
            'Content-Type': 'application/json',
            'Authorization': `Bearer ${access_token}`
        },
    }).then(res => res.json());
    console.log(res);
};

run();

Confirmed via email the issue is resolved.

I am still having this issue. I am using AWS API Gateway from us-west-2 (Oregon), and I receive the same error as OP:
{     "error": "Account cf974e2618fb-4a7d-8ddb-52b9e166b6c1 must be registered in the current region https://fleet-api.prd.na.vn.cloud.tesla.com, please see https://developer.tesla.com/docs/fleet-api#register" }
I am using a valid authorization token, with proper headers, and my public key is hosted on my domain at the /.well-known/appspecific/com.tesla.3p.public-key.pem endpoint.
I receive the error upon attempting to register, submitting a POST request to https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts
For some reason GET https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/dx/charging/history is the only request that returns the requested information. Any other vehicle-related request returns the region error. I can create and refresh tokens just fine.
Help would be greatly appreciated.

@gilbertorobles24 please make sure you call the register endpoint using a partner account token.

It works! Yeah I went back to check the docs for the "partner authentication token". Apparently I was using a "Third Party Token". The difference was that third party token is generated with grant type authorization_code and partner authentication token for registration is generated using client_credentials grant type. Additionally, the register endpoint requires setting header Accept: application/json. Thanks a lot!

So if using a local host you wont be able to register an account as the allowed origin will have to be able to server a public key. I'm currently hosting my public key on github but it looks like that wont work as github is a different domain to localhost.

Simple script I just verified to be working. The curl snippets in documentation also work just fine.
const TOKEN_URL = 'https://auth.tesla.com/oauth2/v3/token'
const REGISTER_URL = 'https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts';

const { CLIENT_ID, CLIENT_SECRET, AUDIENCE, DOMAIN } = process.env;

const run = async () => {
    const urlencoded = new URLSearchParams();
    urlencoded.append("scope", "openid vehicle_device_data vehicle_cmds offline_access");
    urlencoded.append("audience", AUDIENCE);
    urlencoded.append("grant_type", "client_credentials");
    urlencoded.append("client_id", CLIENT_ID);
    urlencoded.append("client_secret", CLIENT_SECRET);

    const {access_token} = await fetch(TOKEN_URL, {
        body: urlencoded,
        method: 'POST',
        headers: {
            'Content-Type': 'application/x-www-form-urlencoded'
        }
    }).then(res => res.json());

    const res = await fetch(REGISTER_URL, {
        body: JSON.stringify({domain: DOMAIN}),
        method: 'POST',
        headers: {
            'Content-Type': 'application/json',
            'Authorization': `Bearer ${access_token}`
        },
    }).then(res => res.json());
    console.log(res);
};

run();

This was very helpful, thank you!


Add/tests

Created tests and script for running tests.

fixes #39

@mikebarr24 This is great, thanks! Just some minor comments.

That should be the requested changes made to the PR. Let me know if that's grand and thanks for the feedback.
I'll get a look at the next part this coming week.

@mikebarr24 This looks great - thanks for making those changes.


[Microsoft.DeviceRegistry] Added spec for Microsoft.DeviceRegistry RP version 2023-11-01-preview

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[x] Other, please clarify:

We are going Public Preview just with Assets and AssetEndpointProfiles.
We went to office hours with this stackoverflow question and the suggestion was to create a new API version for the main public repo with just the Resource Types we are going Public Preview with.
Previously approved 2023-10-01-preview API review PR from azure-rest-api-specs-pr repo is here.

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Hi @davidemontanari! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

Its impossible to tell what changes you are introducing with this version. Please follow this and fix the PR to clearly show the changes in a commit separate from the base commit.

/pr RequestMerge


pf-select: Typeahead Search

Component name:

pf-select

Design specification updates
A new typeahead variant for pf-select.
Refer: https://www.patternfly.org/components/menus/select/#typeahead

Accessibility updates
Refer: https://www.patternfly.org/components/menus/select/#typeahead

This is blocking an open issue on CP - trouble shooting dropdown


package request: couchbase

Project description
Couchbase is a document-oriented database.
Metadata

homepage URL: https://www.couchbase.com/
source URL: https://github.com/couchbase/manifest
license: apache
platforms: linux, darwin

I ended up not needing couchbase, so I'll close this to help maintainers focus on other requests. Feel free to comment if someone else wants this package


“clearButtonContent” don't work

Hi there. Congrats for the great plugin!
At angularjs 1.4.9
code:
language:'zh-CN',
defaultDate:defaultDate,
animationDuration:200,
buttonsToDisplay: [ "SetButton", "ClearButton"],
clearButtonContent: "取消"

just clearButtonContent don't work.

Hi,
Thank You.
If you want a quick fix you can make changes in following lines of DateTimePicker.js

Line 175
Replace

this.settings = $.extend({}, $.DateTimePicker.defaults, options, $.DateTimePicker.i18n[sLanguage]);

with
this.settings = $.extend({}, $.DateTimePicker.defaults, $.DateTimePicker.i18n[sLanguage], options);

Line 2569
Replace

oDTP.settings = $.extend({}, $.DateTimePicker.defaults, oDTP.options, $.DateTimePicker.i18n[sLanguage]);

with
oDTP.settings = $.extend({}, $.DateTimePicker.defaults, $.DateTimePicker.i18n[sLanguage], oDTP.options);

I will update plugin afterwards.

Thank you so much!


Enable the user to set the location of settings.json

Problem
Currently, the location of settings.json is fixed to be either one of the three locations only:

Proposal
Give the user the ability to specify the location via an environment variable, so that the user doesn't have to create any garbage windows shortcut inside some weird folder that ends with some random nonsense like 8wekyb3d8bbwe.
Use case
By allowing the user to specify the location of settings.json cleanly (i.e. without resorting to creating a windows shortcut), it also enables the user to cleanly move it to a folder where the user might have config files for other applications all under one folder.
For example, I use a number of applications on Windows and they all either respect XDG_CONFIG_HOME and/or XDG_DATA_HOME, or provide their own custom environment variables that enable me to move config and data files to a folder of my choice (without having to create garbage shortcuts), making them very easy for me to find as the files are very neatly organized "under one roof".

FWIW, 8wekyb3d8bbwe actually isn't just "randome nonsense" - it's actually part of the Terminal's unique identifier that we get from the Microsoft Store. %localappdata%\packages\{{package family name}}\LocalState is kinda the well-known path for a package to put their data.
You may also be interested in Portable Mode, though, that lacks the benefit of auto-updating.
Otherwise, we've  also got the following threads:

#6687
#2933


Request new repo for sharing monitoring scripts used for RHDP with the community

Type of repository request
Creation of a new repository
Requested name for the repository
rhdp-monitoring-scripts
Repository Description
Scripts for monitoring various components of Red Hat infrastructure.
Associated CoP
GPTE/RHPDS/RHDP platform (as with agnosticd/babylon/anarchy/etc)
Admin Access
gpte-admins
Write Access
gpte
Read Access
public
Additional details
These are the scripts that we use to monitor the RHPDS/RHDP infrastructure and which will likely be useful to the rest of the community, for things like basic monitoring OCPvirt.

Review request:
cc: @redhat-cop/container-cop-core

https://github.com/redhat-cop/rhdp-monitoring-scripts

Thank you, @garethahealy!
I'll start populating with our cop- and/or community-relevant monitoring scripts!


I'm working with a report, where I have some logo for which I am dynamically assigning width and height in properties, considering aspect ratio and other calc.
I also have some other images in the report, suppose a list of students with an avatar.
The issue I'm facing is that, when properties are passed to the Logo, the same properties forcefully reflect on the student avatar images too.
I tried passing a blank object to properties, such that default way of placing the images based on the placeholder works for the student avatars.
Problem is: Image for avatars are not taking the placeholder size when properties are not passed to them, they take properties from last element.

PS:
This happens with the avatar images even if I do
Sablon.content(:image, path)
Sablon.content(:image, path, properties)
Sablon.content(:image, path, properties: {})
Sablon.content(:image, path, properties: {width: nil, height: nil})

but it works fine when a width or height is explicitly gievn like
Sablon.content(:image, path, properties: { width: "2cm", height: "2cm" })
And my Logo image is doing
Sablon.content(:image, path, properties: { width: "3cm", height: "5cm" })

@stadelmanma is there any progress on this? It this repo being worked upon?

@nikhilgoyal22 I haven't worked on this issue for awhile, the general problem here is that the xpath selector is not specific enough.


feat: integrate scenario-specific relationships and attributes

closes #838
/claim #838

@tolgaOzen can you review this pr :)

Hello @aazam-gh, can you update the commit titles according to the standards outlined in https://www.conventionalcommits.org/en/v1.0.0/?

Hi @tolgaOzen I have updated the commit title

if this bounty  is closed ? @tolgaOzen
if yes please reward the individual or may be give update.


Why is go to definition useless at this point?

Type: Bug
The following directory structure exists. I open src in vscode as workspace.
Directory tree view is like :
src
 |-calculation
    |-base_class.py
    |-particular_class.py
 |-db_related_module
    |-db_class.py

and each module has:
base_class.py
class BaseClass():

    def __init__(self, DbClass):
        self.db_cls = DbClass

particular_class.py
from base_class import BaseClass
from db_related_module.db_class import DbClass

class ParticularCalClass(BaseClass):

    def __init__(self):
        super().__init__(
            DbClass
        )

    def some_calculation(self):
        do_db_stuff = self.db_cls
        ret = do_db_stuff.execute_sql()
        return ret

def main():
    calc_cls = ParticularCalClass()
    print(calc_cls.some_calculation())

main()

db_class.py
class DbClass():

    def __init__(self):
        pass

    def execute_sql():
        return "execute some sql"

Here I would like to jump from particular_class.py
ret = do_db_stuff.execute_sql()

to db_class.py
def execute_sql():

as it is the definition.
But unable to go to definition.

Both Ctrl+Click and F12 have no effect
Extension version: 2022.20.1
VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Xeon(R) Silver 4310 CPU @ 2.10GHz (8 x 2095)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: disabled_off

Load (avg)
undefined

Memory (System)
12.46GB (5.90GB free)

Process Argv
--crash-reporter-id 85d2ef9b-c1a0-4650-bde2-81115cb1e6e8

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1:30587005
282f8724:30602487
3d0df643:30613357
89544117:30613380
fim-prod:30623723

Need to add an annotation to base_class.py.. but i dont think you want to do that.
from db_related_module.db_class import DbClass

class BaseClass():

    def __init__(self, DbClass: DbClass):
        self.db_cls = DbClass

This code repros it too:
class MyClass:
    pass

class BaseClass:
    def __init__(self, other):
        self.other = other

    def get_other(self):
        return self.other

class SubClass(BaseClass):
    def __init__(self, other):
        super.__init__(other)

y = SubClass(MyClass)

x = y.get_other()

Type of x is unknown.
But this works:
y = BaseClass(MyClass)
x = y.get_other()

Type of x is Type[MyClass]

This is working as designed.
You need to provide a type annotation for the input parameter for the class constructor. Without this, the type of the instance variable db_cls cannot be inferred.
class BaseClass:
    def __init__(self, db_cls: type[DbClass]):
        self.db_cls = db_cls

Alternatively, you could annotate the type of the instance variable db_cls directly, in which case it doesn't need to be inferred.
class BaseClass:
    def __init__(self, db_cls):
        self.db_cls: type[DbClass] = db_cls

@rchiodo, it works when you directly invoke the BaseClass constructor (y = BaseClass(MyClass)) because of the "pseudo-generic" support in pyright. If a class has a constructor whose types are unannotated, pyright effectively treats it as though it's a generic class where each input parameter for the constructor is a type variable. In the example above, it effectively treats BaseClass as BaseClass[T], and the type of the call BaseClass(MyClass) evaluates to BaseClass[type[MyClass]]. The inferred type of the instance variable is T, which is specialized to type[MyClass] in this case.

@erictraut how come the 'pseudo-generic' support isn't being applied to SubClass? Or maybe it is but that isn't passing through to BaseClass?

Psuedo-generic support works only when you directly call the constructor. Keep in mind that a static analyzer doesn't actually "run" the code, so simulation of nested function calls isn't really feasible.


Cannot rerun after interrupting with CTRL+C

I interrupted the script using CTRL+C, now I have trouble running it again:
Creating the directories if neccessary
Linking profile.d file for reboot message
ln: failed to create symbolic link '/etc/update-motd.d/85-upgrade': File exists
Makefile:12: recipe for target 'install' failed
make: *** [install] Error 1

HI @muranyia,
Please uninstall make uninstall then reinstall


Extend the max save file limit beyond 4

Namely talking about multiplayer settings (loadouts) here. If you're like me and enjoy saving your different setups, 4 doesn't cut it lol
https://github.com/fgsfdsfgs/perfect_dark/assets/66316465/b1e10851-c1f0-4580-b905-c9e439320d76

I guess I could try just expanding the EEPROM size.

While I have no idea how the feasible it would be right now, another option is make it kinda work like how the original, and some emulators do now, with memory cards. Maybe a Memory Card file alongside the eeprom file, and could even do additional ones, just like the N64, up to how many controllers were plugged in. Another bonus of that is then it would make swapping saves, characters and settings files easier.

That is quite possible.

I would like to point out a problem that may be related to the author. When checked with a hex editor, the eeprom.bin file does not delete old profile information. It does not revert to a blank state, as was the case when creating a new save with a profile, or when renaming or copying a profile. I think that over time, this could corrupt the save.