Comment grouping and comment style

Description of Changes

[x] Wrote at least one-line docstrings (for any new functions)
[x] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

I still need a test, but if it looks like it does what we want(I like it) then I'll write a test.
This code relies on the indentation level of the comments in the code giving the user maximum flexibility to fold in whatever(perhaps horrible) way they want. It seem to be inline with how @nerohmot was using them in #11980.
I didn't fix the function definitions inside an if/for/try statement block. That will added a lot additional recursions to the cb0baed2ode and other than in a if __name__  = "__main__" block results is strange code.
Edited for commit b0baed2:
I changed the start of a fold to # << or # region (I personally don't like this but it's what other editors (vscode/pycharm use) and the end of a fold region to be the end of the parent block or an end fold comment # >> or # endregion.
Header comment # ## will not fold the code but will still be grouped according to it's indentation level because otherwise we would have to guess and reading users minds is too tricky ;-)
Non style compliant symbols are also accepted like ###, #<< or #region
Before:

After:

Issue(s) Resolved

Fixes #11980
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: bcolsen

Hello @bcolsen! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/outlineexplorer/widgets.py:

Line 583:1: W293 blank line contains whitespace

Now the only # ##>  comments fold all though # >> might be better.
# ## comments to not fold at the same code level (it will still fold if the it is at a lower indent level) but they cancel a fold at a previous same level.
Current behaviour:

I changed the start of a fold to # << or # region (I personally don't like this but it's what other editors (vscode/pycharm use) and the end of a fold region to be the end of the parent block or an end fold comment # >> or # endregion.
Header comment # ## will not fold the code but will still be grouped according to it's indentation level because otherwise we would have to guess and reading users minds is too tricky ;-)
Non style compliant symbols are also accepted like ###, #<< or #region

This is ready for some user testing for thoughts and general ideas.  If we are happy I can make the tests.
@nerohmot Would this cover the use case that you originally had in mind?

@bcolsen, yes, I think this would do the trick of "organizing" :-)
Hope the tests can be un-blocked, so I can give it a "real world" test drive :-)

I have added test and they are passing!
This is ready for review.

/binder
Some testing code:
# << Section 1
class demo1(object):
    def __init__(self):
        pass

    def foo(self):
        pass

    # << bars 1
    def bar10(self):
        pass

    def bar11(self):
        pass

    def bar12(self):
        # >> comm 0
        pass

    # << bars 2
    def bar20(self):
        # << comm 1
        # ## comm 10
        pass

    def bar21(self):
        # ## comm 1
        pass

    def bar22(self):
        pass
# >>

class demo2(object):
    # ## init
    def __init__(self):
        pass

    def foo(self):
        pass

    # >>> bars 1

    def bar10(self):
        pass

    if True:
        def bar11(self):
            pass

    def bar12(self):
        pass

# region Section 3
class demo3(object):
    # #### bars 001
    def __init__(self):
        pass

    def foo(self):
        pass
# endregion

# ## Main
x = 3
# << Main 1
y = 4
    # << Sub 1
message = "Hello"
mess = "World"
ex = "!"
# endregion

class demo4(object):
    def __init__(self):
        pass

    def foo(self):
        pass

This work needs to be redone in pyls-spyder to work with the LSP architecture used by recent versions of the Outline explorer.
So, I'm afraid we'll have to close it. Sorry for not reviewing it on time @bcolsen.


fix: elixir warning

Fixes the following:
warning: Application.get_env/3 is discouraged in the module body, use Application.compile_env/3 instead

Hi @yordis, thanks for the PR, sorry for the delay in the review. This change does actually break compatibility, as Application.compile_env/3 was introduced in Elixir 1.10, and this lib supports Elixir 1.5 and up.
Anyway, there's another PR doing this exact same change, and we plan on releasing it in a next minor release: https://github.com/toggl/holidefs/pull/44


Search always returns undefined when run in jest unit test

This is a weird one but if you copy all the example code from the readme into a jest unit test the result is always undefined. However the code works fine inside the browser (wrapped in a react component).
I know there are probably lots of differences that could cause this issue but raising here in case other people run into it as well. Hopefully I'll work out what it is and update.

Thanks for that and apologies. The cause was actually that someone else had added a mock for it and I didn't know I was using it!
Also thanks for the great tool :-)

Ah! Makes sense. Your'e welcome!


juju remove-application doesn't fully cleanup metacontroller-operator resources

Description
juju remove-application cannot fully remove the deployed metacontroller-operator-charm resources (statefulset and its running pod).
Steps to reproduce the bug

From a fresh microk8s (after enabling storage, dns, and rbac), run juju bootstrap microk8s micro.
Create a new model juju add-model test.
Deploy metacontroller-operator charm by running juju deploy metacontroller-operator --trust.
After being successfully deployed, remove the deployed charm: juju remove-application metacontroller-operator.
Check microk8s "test" namespace via microk8s kubectl get all -n test. The statefulset metacontroller-operator-charm and its running pod metacontroller-operator-charm-0 did not get removed.

Possible cause
In juju debug-log, I observed the following error:
unit-metacontroller-operator-0: 2022-03-07 16:44:21 ERROR juju.worker.uniter.operation hook "remove" (via hook dispatching script: dispatch) failed: exit status 1
unit-metacontroller-operator-0: 2022-03-07 16:44:21 INFO juju.worker.uniter awaiting error resolution for "remove" hook
unit-metacontroller-operator-0: 2022-03-07 16:44:31 INFO juju.worker.uniter awaiting error resolution for "remove" hook
unit-metacontroller-operator-0: 2022-03-07 16:44:31 ERROR unit.metacontroller-operator/0.juju-log Uncaught exception while in charm code:
Traceback (most recent call last):
  File "./src/charm.py", line 320, in <module>
    main(MetacontrollerOperatorCharm)
  File "/var/lib/juju/agents/unit-metacontroller-operator-0/charm/venv/ops/main.py", line 406, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-metacontroller-operator-0/charm/venv/ops/main.py", line 140, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-metacontroller-operator-0/charm/venv/ops/framework.py", line 278, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-metacontroller-operator-0/charm/venv/ops/framework.py", line 722, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-metacontroller-operator-0/charm/venv/ops/framework.py", line 767, in _reemit
    custom_handler(event)
  File "./src/charm.py", line 139, in _remove
    raise NotImplementedError()
NotImplementedError
unit-metacontroller-operator-0: 2022-03-07 16:44:31 ERROR juju.worker.uniter.operation hook "remove" (via hook dispatching script: dispatch) failed: exit status 1
unit-metacontroller-operator-0: 2022-03-07 16:44:31 INFO juju.worker.uniter awaiting error resolution for "remove" hook

It seems that the problem lies in the remove hook script.
Charm version
metacontroller-operator in charm-hub, revision 2

We (the Juju team) are hitting this too. One of our integration tests deploys and tears down kubeflow-lite which includes this charm, and fails on teardown because of this issue. Maybe the remove hook can just be deleted or commented out until it's needed? In the meantime for this Juju integration we're just going to not worry about teardown failure.

Closed by #12


Secret Notifications

Hi
It possible to receive push notifications to receive secret data from server and not to show it in the notification center even when the app is not in the background.
Thanks in advance

@sunojvijayan Android instructions are here: https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#background-notifications
iOS are here: https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#background-notifications-1

I have an application the node-gcm code is like this
var message = new gcm.Message({
collapseKey: 'demo',
priority: 'high',
contentAvailable: true,
delayWhileIdle: false,
//timeToLive: 3,
restrictedPackageName: "com.name.pack",
dryRun: false,
data: {
title: request.body.titlename,
icon: request.body.icon,
body: request.body.messagetext.slice(0, 150) + "...",
image: request.body.imageurl,
url: request.body.url,
fullmsg: request.body.messagetext,
"content-available": "1"
}
});
It is sending push to my client. And the push works. But what I have to do is capture all push notifications in my client code
push.on('notification', function (data) {
$scope.promoTitle = data.title;
$scope.promoImage = data.image;
$scope.promoDescription = data.fullmsg;
$scope.promoUrl = data.url;
$scope.$apply();
window.location = "#/promotions";
});
and give a local nitification instead of the default push being showed in the device when the app is closed. Currently my code is not working and it is showing default push in the notification bar when i push, even after adding  "content-available": "1" in my code.
Please help


Update qtcreator.rst

Edited the file to include an additional step for the initalization of the platformio project

Thanks! 👍🏾


Simplify generator, allow running on single directory, add README info

Codecov Report

Merging #67 (80092a5) into main (898a29f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   89.53%   89.53%
=======================================
  Files          16       16
  Lines         258      258
=======================================
  Hits          231      231
  Misses         27       27

Flag
Coverage Δ

dotnet
89.53% <ø> (ø)

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


Grunt support

I love gulp but it's possible to add grunt support ?
Thanks.

Instead, use the following code:
var styleguide = require('devbridge-styleguide');
grunt.registerTask('start-styleguide', function () {
  styleguide.startServer();
});

@labs-scnm Wow thanks I will try it. :+1:

Grunt setup is already in readme


Add photos to POI

Removing this issue, it would slow the application down and could pose as copyright infringement unless we take the photos ourselves.


Spectrum startup crash due to Reach Entity Attributes

Mod Name
Spectrum
Mod Homepage
https://modrinth.com/mod/spectrum
Minecraft version
1.20.1
Describe the bug
Game crashes on startup
Steps to reproduce

Run with Connector + Spectrum
Crash
Cry
...

Logs
https://mclo.gs/Jj3kRgz
Additional context
Adding Connector Extras fixes the startup crash.

https://github.com/DaFuqs/Spectrum/issues/329

Please install Connector Extras. Additionally, please do not report issues to Fabric mod authors when using Connector, it's not their job to ensure compatibility with Forge.


Client Allocation Request for: 北京托比咨询有限责任公司

Client Allocation Questions
Core Information

Name: 北京托比咨询有限责任公司
Website / Social Media: http://www.2b.cn/
Region: Greater China
DataCap Requested: 5TiB
Addresses to be Notarized: f1g7ynmax7azy6kbeudidtcxzaljshauupl25itcq
Notary Requested: NeoGe-IPFSMain

Hey @jacky-zhangxueyou, thanks for the request. I have some questions regarding your request. Please describe answers as much specificity as you can.

Can you introduce yourself? Where can I find you online? (Github, Twitter, Linkedin handle, Wechat, etc.)
If you represent an organization, what is the name, nature, registration country, time since inception, and named officers of your organization?
In which region(s) do you intend to use the DataCap?
What is your use case for the DataCap being requested?
Do you plan to specify advanced features when utilizing a DataCap in your storage deal? If so, please specify the feature.
How many miners do you plan on allocating the DataCap? If you have a specific miner(s) you would like to allocate a DataCap, please specify.
Do you agree on providing transparency of DataCap allocation decisions & execution details in public to prevent excessive/unfair self-dealing?

Moreover, I encourage you to take a look of our allocation strategy  and flow which shows how we utilize the assessment.

1.Can you introduce yourself? Where can I find you online? (Github, Twitter, Linkedin handle, Wechat, etc.)
This is Beijing Toby Consulting Co., Ltd found in 2014,We mainly provide Internet e-commerce services for corporate customers.
Official website：http://www.2b.cn/
2.If you represent an organization, what is the name, nature, registration country, time since inception, and named officers of your organization?
Our organization'name is Beijing Toby Consulting Co., Ltd,Registered In Beijing of China,started in 2014 and corporate representative is Ning-bo liu.
3.In which region(s) do you intend to use the DataCap?
China
4.What is your use case for the DataCap being requested?
We want to be able to help enterprise customers store some data backups (including video and pictures) more cheaply.
5.Do you plan to specify advanced features when utilizing a DataCap in your storage deal? If so, please specify the feature.
We will transfer data with miners through offline deal.
6.How many miners do you plan on allocating the DataCap? If you have a specific miner(s) you would like to allocate a DataCap, please specify.
We plan 5-10 miners. We have no specific miner yet.
7.Do you agree on providing transparency of DataCap allocation decisions & execution details in public to prevent excessive/unfair self-dealing?
Yes. info including: deal_id, miner_id, address, dataCID, date etc.

Hey @jacky-zhangxueyou, since my allocation strategy is to build trust progressively, I would allocate 100 GiB to you for the first time. Feel free to request more DataCap when you use up the allocation.

Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network

bafy2bzaceb4cnbja5pavk7c5ujpzk3y5ik5sjkdsgcriyufgqc5qs3nlxam54

Address

f1g7ynmax7azy6kbeudidtcxzaljshauupl25itcq

Datacap Allocated

100GiB

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb4cnbja5pavk7c5ujpzk3y5ik5sjkdsgcriyufgqc5qs3nlxam54


Ignore the bin Directory

Adds the generated bin directory to .gitignore.
/cc @jpeach @stevesloka

Could you sign the commit @danehans to make the bot happy?

Done. Thanks @stevesloka for tagging.


Changing petals colors

This PR changes the petals colors and stages progress speed.

Found a problem running for 30 cameras


don't cache development builds

I have to rm -rf  ~/Library/Caches/deno/plug/ after every rebuild to keep the cache up to date. We should just disable caching local plugins.

I stumbled into this problem today, trying to figure out why my rust changes weren't showing up.  The thing is, for the crates I'm building, I always run in release mode even during development because the crates I'm working with are painfully slow without optimizations.
In addition to not caching development builds, what would you think of having an option to disable caching even for release builds?

@mwcz I agree on disabling cache by default for all local builds (including --release). It doesn't really makes sense to cache it :-)


[Bug]: Resolver attaches comment id when 'fix-me' label is used

We should set COMMENT_ID to 'None' if the fix-me or fix-me-experimental label used. These changes should be implemented in the workflow files.

@openhands-agent please fix this

Fixed by #320


detatch Sync UserName from azureAD from the SetGroupsOnLogin flag.

Might just be a naming issue, eg SetGroupsOnLogin might be intended to be SyncDataOnLogin but if not then groups sync shouldn't stop the name synching??
Might also want to have a  flag for nameSynching?

Hi @mistyn8
Thanks for this PR, will get it into the next version 😸


Adds Batching for Bulk update and insert

Splits the input file into batches of 10k rows with the header
row retained. This feature was limited to a single batch of <10k
records previously. Can now handle very large files.
Go fmt also run which affected other files

Thanks for the PR!


Raising a FailedPayloadsError loses response information for other payloads

In client._send_broker_aware_request (https://github.com/mumrah/kafka-python/blob/master/kafka/client.py#L199), if failed_payloads exists, raising an Exception will cause the lose of the other response information (in acc)
Is there a reason for raising the Exception?  Would it be acceptable to return that information along with the responses instead?

agree -- the current error processing dates back to sept/oct 2013 and could use some love.  have time to submit a PR?

It would be a backwards compatible change - I can try to take a stab at a PR if you're okay with that.

please do - thanks!

see #366 -- FailedPayloads() objects are now returned in the list of responses rather than raised immediately.


Close button not working in settings

Hi,
I've noticed that when you open the settings to change download location, blue "Close" button is not working. You have to use the "x" in the top right corner.

thank you for pointing it out, however at my end it works fine:
https://github.com/paichiwo/tube-getter/assets/37277099/d9258caf-bd8f-41ac-8dea-4b6fcd30eeaf
so the question is which app version are you using and which os. I want to identify that issue and create a fix asap

Hey,
Using v 1.2.1 on windows 10 Pro 22H2.

Also, not sure what does the button right next to settings button, also does nothing to me when I click it.

please use the latest version 1.2.6 it uses new library that lets you download even age restricted videos and works much faster as well - https://github.com/paichiwo/tube-getter/releases/download/v1.2.6/Tube_Getter_v1.2.6.exe
The button next to the settings button should switch theme from light to dark and vice versa. However it doesn't work , I'm aware of it, Please let me know if the issue with close button still exists when using v1.2.6. I will work on it this week and v1.2.7 will be out  this weekend.

I was misled by your readme file, it has the link to v1.2.1 version :)

On version 1.2.6 close button works!
One thing though, I've downloaded 1.2.6 version, but in app itself it shows 1.2.5:

as promised i refactored the whole app and v1.2.7 is ready for use. As far as I know all the bugs have been fixed, and application should work much better. I've done some testing and everythings seems to be fine and working.

https://github.com/paichiwo/tube-getter/releases/download/v1.2.7/Tube_Getter_v1.2.7.exe
Please let me know if you are happy to close this issue

https://github.com/paichiwo/tube-getter/releases/download/v1.2.8/Tube_Getter_v1.2.8.exe is out :)

v2.0 is out: https://github.com/paichiwo/tube-getter/releases/tag/v2.0_rc1


[5.6] Remove ineffective and breaking SQLite code

The code looks like it pads days/months from 1 to 01 when calling whereDay()/whereMonth().
But since the value is added to the bindings before this is called, it has no effect. In the next line $this->parameter() replaces it with the placeholder ?.
It also breaks raw expressions:
DB::table('users')->whereMonth('created_at', DB::raw("strftime('%m', updated_at)"))->toSql();
// expected: select * from "users" where strftime('%m', "created_at") = strftime('%m', updated_at)
// actual:   select * from "users" where strftime('%m', "created_at") = ?

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!


Example code showing up broken

See http://package.elm-lang.org/packages/elm-lang/html/1.0.0/Html-App#programWithFlags.
There should be a block of nicely type-set JavaScript. Instead, a literal piece
```javascript // Program { userID : String, token : String }

var app = Elm.MyApp.fullscreen({ userID: 'Tom', token: '12345' });

appears.
Also, it is strange that the type signature for programWithFlags flows over, instead of being broken by newlines.

Oh, this was a problem in the package, not on the package site.


SweetXML as hard dependency on 0.4.10?

Hi Ben,
just updated ex_aws dependency on my project from 0.4.8 to 0.4.10 and now get this error on compilation:
== Compilation error on file lib/ex_aws/s3/parsers.ex ==
** (CompileError) lib/ex_aws/s3/parsers.ex:3: module SweetXml is not loaded and could not be found
    (elixir) expanding macro: Kernel.if/2
    lib/ex_aws/s3/parsers.ex:2: ExAws.S3.Parsers (module)
    (elixir) lib/kernel/parallel_compiler.ex:97: anonymous fn/4 in Kernel.ParallelCompiler.spawn_compilers/8

could not compile dependency ex_aws, mix compile failed. You can recompile this dependency with `mix deps.compile ex_aws` or update it with `mix deps.update ex_aws

Has SweetXML become a mandatory dependency?
Thanks!

It's still listed as an optional dependency, let me see what's going on.

Not entirely sure what's going on there, the line that's erroring for you is inside this if statement https://github.com/CargoSense/ex_aws/blob/master/lib/ex_aws/s3/parsers.ex#L2 which ought to prevent this kind of thing. Will look into it more.

@benwilson512 imports are lexical, meaning that they are always used regardless of which code path is executed. If you put the if outside of the defmodule it will work, because the module won't even be compiled.
Is there a reason for generating a module with stub functions if SweetXml is not used?

@ericmj so this is weird. Prior to the last release, I had sweet_xml listed as a dev dependency but that was it. While it was merely a development dependency it was entirely possible to have ex_aws as a dep without also having sweet_xml, and would compile. However, after adding it as an optional dependency we now have the above error.
What's the best way to achieve what I want here? The use case here is that streaming functions require that you parse the XML so it can handle pagination and build the list of items. However, such functionality isn't necessary if all you're doing is basic get/put object so I want to make it optional.

The previous configuration of having sweet_xml as a dev dependency was incorrect. Optional and dev work differently so there is no surprise it no longer works.
I gave a suggestion for how to fix it in my previous comment:

If you put the if outside of the defmodule it will work, because the module won't even be compiled.

But to be able to help out more I need to know some information:

Is there a reason for generating a module with stub functions if SweetXml is not used?

In answer to your latter question: At the moment I'm doing https://github.com/CargoSense/ex_aws/blob/master/lib/ex_aws/s3/impl.ex#L53 where if you have sweet_xml installed it'll get parsed, otherwise it won't. On reflection, this probably isn't the right call as it's implicit.
The streaming code should call it explicitly, and the basic impl call should leave it alone. The upcoming changes will make a nicer line between what should parse by default and what shouldn't.

The easiest non breaking change it seems however would just be to have two versions of the same module, one inside each branch of the if,

If I understand it correctly you will get a pretty obscure error message if SweetXml is not present. Why even generate the stub module?

Right now every call to list_objects calls Parsers.parse_list_objects. If SweetXML is present, it'll get parsed, if not, it'll just pass the value along. I didn't want to check for the presence of SweetXML at runtime as that would be a lot of avoidable overhead.

Won't it error if SweetXml is not there anyway? Or is it valid to not parse the response? It feels like you are just going around "fail fast".

It's valid to not parse the response until I've built parsers for every request such that it consistently  returns a parsed value. This is contingent upon generating parsers, a step that is in progress.


[gitops-wg] Add Akuity members

Consent to be added:

[x] Hong Wang @wanghong230
[ ] Jesse Suen @jessesuen
[x] Wojtek Cichoń @wojtekidd
[x] Daniel Hoang @dhpup
[ ] Remington Breeze @rbreeze
[x] Yuan Tang @terrytangyuan

Yes, thanks for adding this!

Yes, thanks for adding this!

Yes, thank you!!

We're only missing @jessesuen

I give consent. Thank you!

Should be OK now @scottrigby


Initial structure

Sumary
Trello card: https://trello.com/c/C1v0wxnJ/6-kick-off-arquitectura-original
Adding initial structure with the Authentication Bootstrapper as entry point to the authentication module.
Adding complete login backend structure: view controller, view model, all models and protocols it needs.
Known issues
Missing view controller tests.

LogIn folder should be Login

Remember to add all i18n message both in english and spanish.

@danielaRiesgo  Remember to a a commit for each comment in the PR.

@danielaRiesgo You need to rebase this branch against master. Everything here is OK after rebasing you can merge this :+1:


Go to definition doesn't seem to work

I think I have it setup properly - I can see errors being underlined, I can see types, but I cannot navigate to definition. Not to other files, not to definition in a same file. I tried original hotkey, custom hotkey and command from menu.
I would appreciate any advice how to make it work.
Atom: 1.13.0
ide-purescript: 0.19.1
pulp: 12.3.0
purs: 0.12.0

Strange, day later it started working even though I did not change tools, project setup or editor settings. 🤨 Not sure what changed.

Go to definition is powered by purs ide which uses a set of source filename globs on startup - one possibility is if the set of globs changed after starting the server (e.g. adding dependencies which aren't picked up)


Cannot get access token in React app accessing protected .NET Core API with Azure B2C

Please follow the issue template below. Failure to do so will result in a delay in answering your question.
Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Description
I'm having issues getting an access token from my React app, trying to access my own .NET Core 3.1 web API. I'm able to login fine and can access the user data, but when I try to get an access token, I get the below error continuously. Would appreciate any help or push in the right direction. Thank you!

Uncaught (in promise) BrowserAuthError: silent_sso_error: Silent SSO could not be completed - insufficient information was provided. Please provide either a loginHint or sid.

Here's what I have:

Set up React app registration (SPA w/ redirect to localhost:3000 using auth code flow)
Set up .NET Core web api app registration (Web w/ redirect to localhost:44347)
Created two scopes for the web api (read and write)
Gave api permission to the spa to the web api scopes

.NET Core 3.1 Web API setup (ref: https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-protected-web-api-app-configuration):

Startup ConfigureServices

services.AddMicrosoftIdentityWebApiAuthentication(Configuration, "AzureAdB2C");

appsettings.json

    "AzureAdB2C": {
       "Instance": "https://{example}.b2clogin.com",
       "ClientId": "{web api Client ID}",
       "TenantId": "xxxxxxxxxxxx",
       "Audience": "https://{example}.onmicrosoft.com/api"
    }

React set up using "@azure/msal-browser": "^2.7.0" and "@azure/msal-react": "^1.0.0-alpha.0" (ref: https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-react):

index.tsx

const configuration: Configuration = {
  auth: {
      clientId: '{SPA Client ID}',
      authority: 'https://{example}.b2clogin.com/{example}.onmicrosoft.com/B2C_1_SignUpIn',
      knownAuthorities: ['{example}.b2clogin.com'],
  },
  cache: {
      cacheLocation: 'localStorage', // This configures where your cache will be stored
      storeAuthStateInCookie: false // Set this to "true" to save cache in cookies
  }
};

const pca = new PublicClientApplication(configuration);
<MsalProvider instance={pca}>
   <App />
</MsalProvider>

App.tsx

  useEffect(() => {
    if (error) {
        login(InteractionType.Popup);
    }
  }, [error, login]);

Accessing the token code

const { instance, accounts, inProgress } = useMsal();

useEffect(() => {
        if (inProgress === 'none' && accounts.length > 0) {
            const request = {
                account: accounts[0],
                scopes: ["https://{example}.onmicrosoft.com/api/scope.read"]
            };
            // Retrieve an access token
            instance.acquireTokenSilent(request)
                .then(response => {
                    console.log('response', response);
                    if (response.accessToken) {
                        console.log('accessToken', response.accessToken);
                        return response.accessToken;
                    }
                    return null;
                })
                .catch(error => console.log('token error', error));
        }
    }, [inProgress, accounts, instance]);

@andrewabril Can you try including the scopes in your login request? There's a known issue with B2C discussed here where B2C only issues refresh tokens that can be exchanged for the scopes used to obtain the RT. In this case it results both in a failed cache lookup for the access token (since this is the first time you're requesting it) and then a failed refresh (since the RT doesn't work for these scopes).
If you're using the useMsalAuthentication hook you can pass it a request that will be used on the login call.

Thank you! I was able to get the access token that way. Still trying to piece it together but at least I know I'm getting a token.
What would best practices be in terms of getting and using the token? I used the useMal() example (https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-react/docs/hooks.md) with useEffect() to get the token, and it's getting called hundreds of times and continuously.

I am facing the same the issue - calling acquireTokenSilent fails to resolve. It seems to dismounting the component causing an infinite loop

@andrewabril This should be addressed in the newest version. Can you try to update to<EMAIL_ADDRESS>and let me know if that fixes it?

It looks like that did fix it - great.
One more thing if you don't mind so I can get this working end to end. I'm getting a CORS error that I didn't have before. I've tried adding specific origins (https://{sample}.onmicrosoft.com,https://{dample}.b2clogin.com,https://login.microsoftonline.com) to my allowed origins config and also allowing all origins with no effect. I've also tried adding Access-Control-Allow-Origin header as "*" in my Options method.
Is there something specific that needs to be done to get CORS to work witb B2C?
Access to XMLHttpRequest at 'http://localhost:5000/api/FixFlipAnalysis' from origin 'http://localhost:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Thanks again for all your help.

@andrewabril Looks like this is happening when your app is calling your API which means this does not have to do with B2C. You may need to configure your API to respond to the OPTIONS request with the Access-Control-Allow-Origin header set and possibly others.
You can read more about CORS here

I don't think the error is entirely accurate. I set up CORS before adding any authentication/authorization into the api and haven't had any issues. I have it allowed to certain sites (localhost and a sentry endpoint), but it breaks after I add auth with b2c.
I will look into it a bit more, but because it only occurs when I add the auth piece to the api, I'm leaning toward it being related to auth/b2c.

@andrewabril You should be able to see which network request is failing the OPTIONS request in your network tab. If it's failing on any of the b2c endpoints take a look at your app registration and double check your redirectUri is configured as type SPA. If it's failing on your own API then it's most likely related to any new headers you are adding to your request.

The CORS issue I was facing was due to incorrect Configuration middleware order. I was calling app.UseCors() after routing and authentication/authorization. Calling that beforehand resolved the CORS issue.
I also used this reference to make sure my ConfigurationServices was correct, https://github.com/AzureAD/microsoft-identity-web/wiki/web-apis.
ConfigurationServices auth set up using Microsoft.Identity.Web
services.AddMicrosoftIdentityWebApiAuthentication(Configuration, "AzureAdB2C");
appsetting.json
"AzureAdB2C": {
    "Instance": "https://{tenant name}.b2clogin.com",
    "ClientId": "xyz123",
    "TenantId": "abc123",
    "Domain": "{tenant name}.onmicrosoft.com",
    "SignUpSignInPolicyId": "b2c_1_signupin",
    "ResetPasswordPolicyId": "b2c_1_passwordreset"
  }

Thanks for all your help!


Game Title
Sea of Thieves
Game Website
https://www.seaofthieves.com/
Anti-Cheat Software
Other
Status of the Anti-Cheat
❔ Unconfirmed
Proof of Mention
N/A

I could not find information on the game actually using some sort of anticheat


Add-on not found

I cannot search the add-on in version 2.83 and version 3.0.0, after installation. Do I need to modify some code parameters in .py or other files?

You don't need to modify anything. This is weird, can you open the console
and see if there's any error when installing the addon?
Window ‣ Toggle System Console
On Mon, Feb 13, 2023, 19:14 xiyunxun @.***> wrote:

I cannot search the add-on in version 2.83 and version 3.0.0, after
installation. Do I need to modify some code parameters in .py or other
files?
—
Reply to this email directly, view it on GitHub
https://github.com/JonathanCamargo/BlendOsim/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHTZXGHGKCGZLZF3N5MOK3WXLZ7XANCNFSM6AAAAAAU3A4DOM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Can you download the release instead of downloading the repository? Or make
sure that the zip file contents are the files directly -not a subfolder-
and try again?
On Mon, Feb 13, 2023, 21:49 xiyunxun @.***> wrote:

[image: 截屏2023-02-14 13 48 16]
https://user-images.githubusercontent.com/34223067/218650561-3d0a5235-621f-499a-a754-bd22796c2ed2.png
—
Reply to this email directly, view it on GitHub
https://github.com/JonathanCamargo/BlendOsim/issues/4#issuecomment-1429156349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHTZXCBSKTQGYTTAP2KDTLWXMMFBANCNFSM6AAAAAAU3A4DOM
.
You are receiving this because you commented.Message ID:
@.***>

I tried again, but there was an error in the program

I've done this many times, but I still can't

Please download the Release instead of doing the download from the
repository main branch.
Or, if you are using what you show in the image, then unzip first, move the
contents so that the code is not inside a subfolder and then zip back.
Addons should have the files directly in the zip and not in a subfolder
inside the zip.
On Tue, Feb 14, 2023, 17:45 xiyunxun @.***> wrote:

[image: 1]
https://user-images.githubusercontent.com/34223067/218906132-161bd8e3-2b37-4d2c-adcf-f79f0e57f2e1.png
[image: 2]
https://user-images.githubusercontent.com/34223067/218906143-e4abbd35-72dd-4e4c-be8e-795a9bf11b33.png
[image: 3]
https://user-images.githubusercontent.com/34223067/218906159-3ffa335f-ba9e-464e-bb1e-90715840b3ef.png
[image: 4]
https://user-images.githubusercontent.com/34223067/218906168-14dc8fd3-000f-4f7b-a64f-e660caaf0675.png
I've done this many times, but I still can't
—
Reply to this email directly, view it on GitHub
https://github.com/JonathanCamargo/BlendOsim/issues/4#issuecomment-1430634982,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHTZXCNX6KQMELV5IUUWFDWXQYNLANCNFSM6AAAAAAU3A4DOM
.
You are receiving this because you commented.Message ID:
@.***>

Thank you for your help. I have successfully installed

How the csv file in the example is converted from opensim？


Protocol gets doubled when using the server_url from the generated fidesctl.toml file

Bug Description
When generating the fidesctl.toml file with fidesctl init the server_url that gets generated is http://localhost. Then subsequent uses of the file results in an error because server_protocol is appended to the server_url resulting in http://http://fidesctl
Steps to Reproduce

Create a .fides directory
Run fidesctl init
Run docker-compose run --rm fidesctl /bin/bash with the following docker-compose file
Run fidesctl status in the docker container.

services:
  fidesctl:
    image: ethyca/fidesctl:lateset
    command: fidesctl webserver
    healthcheck:
      test: ["CMD", "curl", "-f", "http://<IP_ADDRESS>:8000/health"]
      interval: 5s
      timeout: 5s
      retries: 5
    depends_on:
      fidesctl-db:
        condition: service_healthy
    expose:
      - 8080
    ports:
      - "8080:8080"
    environment:
      - FIDESCTL__CLI__SERVER_HOST=http://fidesctl
      - FIDESCTL__CLI__SERVER_PORT=8080
      - FIDESCTL__API__DATABASE_URL=postgres:fidesctl@fidesctl-db:5432/fidesctl
    volumes:
      - type: bind
        source: ./.fides/ # Update this to be the path of your .fides/ folder
        target: /fides/.fides/
        read_only: False

  fidesctl-db:
    image: postgres:12
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 5s
      timeout: 5s
      retries: 5
    volumes:
      - postgres-fidesctl:/var/lib/postgresql/data
    expose:
      - 5432
    ports:
      - "5432:5432"
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=fidesctl
      - POSTGRES_DB=fidesctl

volumes:
  postgres-fidesctl:

Expected behavior
The URL should only contain http:// once.
Screenshots

Environment

Version: latest docker image
OS: Linux
Python Version: 3.8
Docker Version: 20.10.14

Additional context
When running fidesctl init the server_url is generated with this validator which concatenates the server_protocol and server_host resulting in http:localhost in the fidesctl.toml file resulting in the the following config for the cli.
[cli]
analytics_id = "d364070208d491fe88fe0309cce6d509"
server_url = "http://localhost"

From the test files it looks like the expected output is something like:
[cli]
server_host = "fidesctl"
server_port = 8080

And an example of an invalid config as:
[cli]
server_host = "http://invalid"
server_port = "8080"

So it looks like the expected is both to have a server_host instead of a server_url and for the URL to not contain the http://?

I was running some tests trying to find the issue and found that when running outside of docker I don’t get the double http. I haven’t figured out yet what the difference between running the docker image and running without could be.

@sanders41 correct, according to our docs page (https://ethyca.github.io/fides/1.5.2/installation/configuration/#configuration-file) we only want people to be settings the host/port/protocol separately, and it shouldn't be writing server_url out at all!

This doubling is possibly fixed now? I still have the issue when I use the latest image from Docker hub, but can't recreate it any more when working directly in the repo.
It does seem to be still writing the server_url instead of the server_host, server_port, and server_protocol into the fidesctl.toml file when running `fidesctl init', but this no longer causes an error.

Yes, should be good now.


Investigate end-to-end delay in sudden obstacle braking response

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
During several tests, a notable delay has been observed in the autonomous system's response to sudden obstacles, particularly when braking is required.
For instance, at 3:32 in a test discussion, the planning/perception components reacted later than expected.
This issue is not isolated, as searching for "reacts late" in the discussion page reveals multiple instances.
The proposed approach to investigate this involves a systematic test in both the planning simulator and AWSIM, focusing on the time taken from the obstacle's appearance to the initiation of the braking maneuver by the ego vehicle.
Purpose
The purpose of this investigation is to ensure that the response time of the Autoware system to sudden obstacles meets the necessary safety requirements.
By identifying the sources of delay within the system, from perception to actuation, we aim to optimize the response time and enhance the safety and reliability of the autonomous driving system.
Possible approaches

Planning Simulator Test:

Simulate the ego vehicle traveling at 50km/h on a straight path.
Introduce a sudden obstacle at a predetermined emergency braking distance. (Like 40m)
Measure the latency from the obstacle's appearance to the initiation of the braking sequence with millisecond precision.
Analyze where the delays occur most significantly within the system.

AWSIM Test:

Develop a detailed test procedure that spans from point cloud level detection to the end of the control stack.
Measure and document the delays at each stage of the detection and response process.

Definition of done

[ ] The systematic testing and measurement of delays have been completed in both the planning simulator and AWSIM.
[ ] A report detailing the delay times at each stage of the detection and reaction process has been compiled.
[ ] Recommendations for improvements, based on the findings, have been documented.
[ ] All tests and analyses have been peer-reviewed to ensure accuracy and reproducibility.
[ ] Any identified bottlenecks have been addressed with proposed solutions, and a follow-up plan for implementation and testing of these solutions is in place.

We started work on this issue. To see the reaction time, we are currently working on a package. Currently, our target design is:

For the first tests, we investigated only the reactions of the control topics.
Package: https://github.com/brkay54/autoware.universe/tree/feat/reaction-measure-tool/tools/reaction_analyzer
For an easy start, please read the usage part of the readme of the package and also, you can use the LEO-VM-00001. You do not need to edit the entity position in the parameter file, it is already set on LEO-VM-00001 map.
First test results:
15 tests have been made for each case: (obsacle_stop_planner with use_predicted_objects),
(obsacle_stop_planner without use_predicted_objects), (obstacle_cruise_planner).
Case - 1 - obsacle_stop_planner with use_predicted_objects:

Case - 2 - obsacle_stop_planner without use_predicted_objects:

Case - 3 - obsacle_cruise_planner:

For the first reaction tests, use_predicted_objects condition for obstacle_stop_planner is running unstable, reaction time is very high for some cases.

The PR is ready to fix the high reaction times of obstacle_stop_planner when use_predicted_objects is true.
https://github.com/autowarefoundation/autoware.universe/pull/5794
cc @xmfcx @mitsudome-r

Reaction Tests For Perception Pipeline
The purpose of the tests is to measure the reaction time of each node in the Perception Pipeline. To achieve this, we developed a test environment by utilizing the AWSIM. We recorded rosbags in AWSIM to be able to launch the perception pipeline easily on the local devices. The disadvantage of this method is time resolution is about ~10ms because we can get a maximum 100 hz clock frequency. We used the sample_vehicle with awsim_sensor_kit (which has only 1 lidar) and tests were made in the awsim-stable branch but I am going to change the test environment to be able to run in main branches.
Firstly, we wanted to measure the processing time of the pointcloud_preprocessor to see how much time takes on the sensing side. To measure the delay times in the pointcloud_preprocessor pipeline, we added accumulated_time debug information which reports the delay inside of each node. (PR is here)

Because the time resolution is about ~10 ms and the ring_outlier_filter and crop_box_filter processes finished mostly below 10 ms, the results above are not accurate. However, the concatenating process time is higher than 10 ms and we can see that the total pointcloud preprocess finished around ~115 ms on average.  The most time-consuming process is concatenating.
To measure the times in the perception pipeline, we created a test environment by using AWSIM. Firstly, we recorded two different rosbag files: one of them was in an empty area without any obstacle around the ego vehicle, and the other bag file was recorded in an area where there was a car in front of the ego vehicle. In both environments, the ego vehicle is in the same position and stationary, so all the topics except pointcloud topic are the same.
In reaction_analyzer node, we took sample messages from pointcloud topic in the rosbags and we recorded both pointcloud messages (pointcloud message without any object and pointcloud message with the car in front of the vehicle) at node initialization. It publishes the pointcloud without any obstacle at the beginning, when we want to spawn the obstacle, it starts to publish the pointcloud with car in front of the ego. After reaction_analyzer publishing the pointcloud with a car, it starts to search the first messages of the perception pipeline topics.
To be able to run all test environment, steps are explained below:

We should run the rosbag file which will publishes some necessary messages like vehicle_status, gnss_pose etc. to run the Autoware.
We run reaction_analyzer to publish pointcloud messages (firstly publishes empty one, then it publishes the pointcloud with car when we want to spawn the car)
We run autoware by the command: ros2 launch autoware_launch e2e_simulator.launch.xml vehicle_model:=sample_vehicle sensor_model:=awsim_sensor_kit map_path:=[PATH]

Test video:
https://github.com/autowarefoundation/autoware.universe/assets/45468306/7400bd64-345d-4fed-a0c8-3ab0939c6b8b
After the obstacle is spawned (I mean reaction_analyzer starts to publish pointcloud with a car), reaction_analyzer starts to search for the obstacle in predefined topics. When it finds the reacted message, it calculates the time between the spawn command time and the header time of the reacted message. Nodes in the perception pipeline, header times do not have the timing of the process done. Firstly, I had to change the header times of some nodes by changing them to include the current time of the process done.
With this test environment, we made 10 tests with some predefined checkpoints in the perception pipeline:
occupancy_grid_map_outlier: /perception/obstacle_segmentation/pointcloud
voxel_based_compare_map_filter: /perception/object_recognition/detection/pointcloud_map_filtered/pointcloud
lidar_centerpoint: /perception/object_recognition/detection/centerpoint/objects
obstacle_pointcloud_based_validator: /perception/object_recognition/detection/centerpoint/validation/objects
detected_object_feature_remover: /perception/object_recognition/detection/clustering/objects
detection_by_tracker: /perception/object_recognition/detection/detection_by_tracker/objects
object_lanelet_filter: /perception/object_recognition/detection/objects
map_based_prediction: /perception/object_recognition/objects

The results:

Statistics:

As we can see, the DetectedObjects outputs react in around ~200 ms, however, the PredictedObjects output takes much more time (around ~600 ms).
Future Work:

After solving some compatibility issues, I am planning to make these tests in the main branch
The current sensor setup has only 1 lidar, I am planning to use another vehicle setup in the AWSIM which will have more than 1 lidar.

@brkay54 Thank you for your great work. :pray:
Currently, trust counts 3 in the multi-object tracker, object should be detected 3 times before publishing as a tracked object. The result looks reasonable. Also, disabling delay_compensation inside into multi-object tracker module could give better results in this use case, it could add extra delay.

** Weekly Update **

Last week, to be able to run the perception pipeline reaction test, we ran the reaction_analyzer by playing rosbag in another terminal. This causes ~10ms time resolution while measuring the reaction times. This week, I made some changes to the reaction analyzer to be able to record the necessary messages of the rosbag and replay them inside the node. In this way, we can measure the reaction times in the system time.

3 Lidar test environment created by using AWSIM, and I can run perception pipeline tests by using them successfully.

Firstly, I investigated the pointcloud_preprocess pipeline to analyze how much delay we got to get concatenated pointcloud output. For this test, I used 3 Lidar setup and I analyzed the pipeline_latency_ms which we added before:

When I published 3 lidar pointcloud outputs, the pipeline_latency_ms started with a lower latency value:

After 12 minutes:

As you can see, the latency value of the concatenated nodelet of the right lidar is accumulating.
After 10 minutes:

After this higher value, the concatenated pointcloud delay decreases immediately as you can see graph below:

It seems to me a weird behavior. After, some time, I thought that it would be caused by phase differences between lidar output publishers. Then, I added another feature to the reaction analyzer to make it able to publish pointcloud outputs synchronically.
After running the reaction analyzer with synchronically published pointcloud, I couldn't see this accumulated pipeline_latency on the concatenating process:

The concatenated pointcloud delay of the top lidar is higher than others. It is caused by the higher delay of the distortion corrector. Distortion_corrector in the top lidar process takes more time than others because the pointcloud size of the crop_box_filtered_mirror of the top lidar is higher than others. The difference in width between the top lidar and right-left lidars is ~13,000 and it causes ~10ms delay. However, because of this ~10ms delay, the concatenate process is always running with the past pointcloud output of the top lidar. (I didn't try yet but I saw that we can set offset values for the specific pointclouds w.r.t documentation of the concatenate nodelet. I am going to try it.)

For the development phase of the reaction_analyzer, all features were added, just need to clean up the code. And we need to decide how to implement the timestamp reporting process of the perception pipeline. I created an issue for it here.

The Lidar-Only pipeline was measured above, I will also measure the Lidar-Camera pipeline.

Weekly Update

We added reset() function to be able to restart test automatically. By using this, we can test the reaction times multiple times. After launch once, it can test as much as iteration_number and it calculates statistics. Then, it creates CSV file as shown below.

Code cleaned-up and ready for the first review. Usage was explained in detail in readme file.

We realized a bug in perception pipeline, created issue here.

Only blocker is how to define the publishing times of the nodes: https://github.com/autowarefoundation/autoware.universe/issues/6255

Closing because the delays are investigated.


Audio cracking/popping on Lenovo ThinkPad C13 Yoga

The computer plays the audio, but there is a constant background noise of cracking/popping
Boardname: Morphius
Operating System: Fedora Linux 39
Logs: cbmem.tar.gz

Do you have iommu=pt in your cmdline?

Yes, I followed this guide to do that.

Can you send dmesg?

output.txt

Not seeing anything wrong there. Two things you can try: older like (like LTS) or switching audio server (pipewire <-> pulse).

I just tested both possibilites and none of them work. I believe it is not an incompatibility related to the kernel or audio server.
I also noticed a pattern in the audio error. When I play an audio, it works perfectly for 1 or 2 seconds before pausing momentarily. After this, the audio returns, but it starts to crackle. This occurs in both speakers and headphones.
Facts I noticed when doing some tests:

The audio only crackles on speakers and wired headphones; the audio is perfectly clean on bluetooth headphones;
When I share my computer's audio with another device via RTSP, the computer's audio (magically) stops crackling instantly. Once the RTSP connection is broken, the popping occurs again.

Interesting. I'll be getting a Vilboz in a few days so I'll see if I can reproduce when I get it.

Udpate: I noticed that, in reality, the audio is only corrected when the microphone is active. The audio was corrected during the RTSP connection because it activated the microphone. I hope this new information can be useful to you in understanding the reason for the error.

Interesting, I'll see when Vilboz arrives (monday or tuesday).

Any updates on this? I have a similar issue. Audio will also speed up on YouTube after a couple of seconds of playback and start cutting/popping.

Sorry, I forgot about this issue. I can test my Vilboz soon.

I was able to reproduce the speed issues. Funny though that opening the kde sound applet will cause it to start recording the internal mic, which fixes the issue as OP said.

See: https://forum.chrultrabook.com/t/morphius-audio-popping-in-firefox-you-may-need-this-pipewire-patch/717

See: https://forum.chrultrabook.com/t/morphius-audio-popping-in-firefox-you-may-need-this-pipewire-patch/717

Thanks, I updated my system and everything was solved straight away. Thanks for all of your work on this project!

Same here, thanks!


mcontrol chain bit not WARL on triggers 1 & 3

Setting a store address & value breakpoint using chained triggers succeeds in setting and reading back the mcontrol registers if triggers 1 & 2 are used, but the breakpoint is hit on instructions which do not match the second trigger. These are the values read from mcontrol & tdata2 on triggers 1 & 2:
t1 mcontrol 0x2be018c2
t1 tdata2 0xf0040005
t2 mcontrol 0x2be81042
t2 tdata2 0xaaaaaaaa
In my test program the trigger fired on writes to 0xf0040004 which had values other than 0xaaaaaaaa. If I used triggers 0 & 1 instead the data HWBP worked correctly. I also found the chain bit could be set and read back on trigger 3.
The EH1 PRM section on mcontrol notes that attempts to set chain on triggers 1 & 3 are ignored because chaining is only supported on pairs 0/1 and 2/3. RISC-V debug 0.13.2 specifies all tdata registers are WARL so the debugger can determine which features are supported.
This case is likely to come up if a store addr & value HWBP is set after a simple exec HWBP.

Thank you for reporting this issue.  We are looking into it and will report back.

After some internal discussions, we have decided to fix the issue you have reported.  In the next release of the SweRV EH1 core, the chain bit of MCONTROL will have WARL behavior (i.e., the chain bit value will always be '0' for reads of MCONTROL for triggers 1 and 3).
Thank you again for reporting this issue.  Much appreciated!

Thank you very much for looking into this.


Can't write to /usr/lib OS X El Capitan

The private eye beta 2 tries to write to /usr/lib
#!/usr/bin/env bash
profiler=''
if [[ `uname` == 'Linux' ]]; then
   profiler="libmono-profiler-peye.so"
elif [[ `uname` == 'Darwin' ]]; then
   profiler="libmono-profiler-peye.dylib"
fi
echo "Installing Private Eye Profiler..."
echo "/usr/lib/$profiler"
cp $profiler "/usr/lib/$profiler"
echo "Done."

➜  package  sudo ./package_install_profiler.sh
Installing Private Eye Profiler...
/usr/lib/libmono-profiler-peye.dylib
cp: /usr/lib/libmono-profiler-peye.dylib: Operation not permitted
Done.
➜  package

The only option is to disable the  System Integrity Protection .
http://apple.stackexchange.com/questions/208764/cant-write-to-usr-lib

need to check where else mono will reliably load it from. Discovering where mono is sounds like a horrible idea.

if you copy the file to yourmonoinstallation/lib it will also work.

I tried copying to different folders and I still see it not being loaded yet.

➜  package  which mono
/usr/local/bin/mono

Time Elapsed 00:00:00.3096380
The 'peye' profiler wasn't found in the main executable nor could it be loaded from 'mono-profiler-peye'.
You can experiment with your own programs. Look at run_sample_app.sh on how you can do that.

are you in 32 bit mono?
On Sun, Nov 1, 2015 at 2:03 AM, Naveen<EMAIL_ADDRESS>wrote:

I tried copying to different folders and I still see it not being loaded
yet.
➜ package which mono
/usr/local/bin/mono
Time Elapsed 00:00:00.3096380
The 'peye' profiler wasn't found in the main executable nor could it be
loaded from 'mono-profiler-peye'.
You can experiment with your own programs. Look at run_sample_app.sh on
how you can do that.
—
Reply to this email directly or view it on GitHub
https://github.com/PrivateEye/PrivateEye/issues/1#issuecomment-152782175
.

--
Studying for the Turing test

➜  package  mono --version
Mono JIT compiler version 4.2.0 (Stable <IP_ADDRESS>/a224653 Sat Oct 31 19:34:30 EDT 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           normal
	SIGSEGV:       altstack
	Notification:  kqueue
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug
	LLVM:          supported, not enabled.
	GC:            sgen

No

I don't have el capitan here to test. Its a matter of putting it in the
right directory for mono to find it though I wouldn't be surprised in mono
has totally changed it since 3.12/4.02/etc vs 4.2.0
On Sun, Nov 1, 2015 at 2:05 AM, Naveen<EMAIL_ADDRESS>wrote:

➜  package  mono --version
Mono JIT compiler version 4.2.0 (Stable <IP_ADDRESS>/a224653 Sat Oct 31 19:34:30 EDT 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS:           normal
SIGSEGV:       altstack
Notification:  kqueue
Architecture:  amd64
Disabled:      none
Misc:          softdebug
LLVM:          supported, not enabled.
GC:            sgen
No
—
Reply to this email directly or view it on GitHub
https://github.com/PrivateEye/PrivateEye/issues/1#issuecomment-152782240
.

--
Studying for the Turing test


New Azure Auth Provider

#9618
This is the largest chunk of the PRs we're looking for this feature.

could you please provide more description for this PR?

The PR here should provide the information @alanrenmsft https://github.com/microsoft/azuredatastudio/pull/9618
This PR is essentially that one just split into multiple chunks. This provides a new Azure Account Provider that is far less error prone and is ready to upgrade to MSAL when we're unblocked from doing so.


Add an option to useFetch to not consider non-5xx status codes as errors

Describe the feature
When developing a rest API, it's considered good to use semantic status codes for different response types. So I do in my API routes:
import { setResponseStatus } from 'h3'

const enum OperationResultKind {
  Created       = 'Created',
  AlreadyExists = 'AlreadyExists',
  InvalidData   = 'InvalidData',
}

type OperationResult =
| { kind: OperationResultKind.Created; user: User }
| { kind: OperationResultKind.AlreadyExists }
| { kind: OperationResultKind.InvalidData; problems: ValidationProblem[] }

export default defineEventHandler(event => {
  const unvalidatedData = readBody(event)
  const validationResult = // some validation stuff

  if (!validationResult.success) {
    setResponseStatus(event, 400)
    return { kind: OperationResultKind.InvalidData, problems: validationResult.problems }
  }

  const { data } = validationResult

  try {
    const insertedUser = await insertIntoDb(data)
    setResponseStatus(event, 203)
    return { kind: OperationResultKind.Created; user: insertedUser }
  } catch (e) {
    if (/* some error checking */) {
      setResponseStatus(event, 409)
      return { kind: OperationResultKind.AlreadyExists }
    }

    throw e
  }
})

However, when fetching this route with useFetch, I end up with InvalidData and AlreadyExists errors being in the error ref. The thing is that these variants are some type of domain errors and I get no typings for them. The other thing is that the data ref is of type OperationResult, but it only may contain the Created variant so I end up using as to convert types which is not good.
I could return only 2xx status codes to resolve this issue, but I might want to reuse this API in many different projects in the future so status codes must be semantic.
I think that one option for resolving that may be adding some interceptor concept such as in Axios:
axios.get('/user/12345', {
  validateStatus: function (status) {
    return status < 500; // Resolve only if the status code is less than 500
  }
})

Also one would want to use this validation interceptor globally, so it's worth adding this to nuxt.config.ts.
Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

According to HTTP, 5xx is always a server error, so accepting those as a valid response only to get non-runtime relevant types would be kind of semantically wrong, in my opinion. But I understand the struggle, let's what other people think about that.

Lets track in https://github.com/unjs/ofetch/issues/207

This is now implemented.


Manually added publication does not show in overview

Describe the improvement
I manually created the publication https://eliot1.ugent.be/biblio-backend/publication/8630119. I can browse to it, but I cannot find it in the publications overview.

It seems that the publication does not appear in the overview when I do not add particular metadata. When I add myself as author + indicate that I am an UGent author, the publication appears in the overview.
I can always browse to the publication using the biblio id in the url, even if it is not shown in the overview.

creator_id was not set; you could view the publication directly because you have admin rights


Navbar overlapping Heading and Radio button

Screenshots

Probably the fixed navbar caused this . Assign it to me and i will take care

Probably the fixed navbar caused this . Assign it to me and i will take care

all yours @naim16031988


Deutsch!

This looks... Google Translate. My German isn't quite perfect but I notice several issues just skimming over it. Thanks for trying but this isn't quite what I'm looking for


No entities found

Hi there,
I have an Ecowater "eVOLUTION REFINER POWER" model, the integration has bin done, but I see no entities which I can use.
I only see 1 entry, but no entities 👍

Something I am missing in here ?
Many thanks for the work !

Same issue, has anyone solved?

@cedricdelecole are you still suffering from this issue?

I will close this issue due to a lack of activity. Feel free to re-open it if you need @cedricdelecole!


Sublime CPU activity is high, once I enabled the analyzer

Here's the script:
import 'dart:async';

main() {
  var i = 0;
  new Timer.periodic(const Duration(seconds: 1), (_) {
    print('hello ${i++}');
    i.foo();
  });
}

Future doStuff() => new Future.value(true);

Does this happen to you?
Here's my config:
{
	"dart_dartium_path": "/Users/sethladd/homebrew/Cellar/dartium/1.6.0/Chromium.app",
	"dart_linter_active": true,
	"dart_linter_gutter_icon_error": "Packages/Dart/gutter/dartlint-simple-error.png",
	"dart_linter_gutter_icon_info": "Packages/Dart/gutter/dartlint-simple-info.png",
	"dart_linter_gutter_icon_warning": "Packages/Dart/gutter/dartlint-simple-warning.png",
	"dart_linter_on_load": true,
	"dart_linter_on_save": true,
	"dart_linter_show_popup_level": "WARNING",
	"dart_linter_underline_color_error": "C7321C",
	"dart_linter_underline_color_info": "0000FC",
	"dart_linter_underline_color_warning": "F18512",
	"dart_log_level": "error",
	"dart_sdk_path": "/Users/sethladd/homebrew/Cellar/dart/1.6.0/libexec",
	"dart_user_browsers":
	{
	}
}

I'll close this one as the analyzer is on its way out, at least as far as operating in the background is concerned. Users will still be able to see its output if requested explicitly. When dart_style matures, it will be obsoleted.


[5.7] Added CHANGELOG by component for v5.7.8

We had proposition to track changes by components https://github.com/laravel/ideas/issues/1314 for situation when someone used only some components.
In case, if this PR will be accepted then I will add CHANGELOG for v5.7.1-v5.7.7

Hmm, this sounds like a lot of work. I think I will wait for now 😄


Provide user generated scripting with libsql and wasm

Metadata

Status: proposed
Deciders: V-Sekai,
Tags: V-Sekai,

Context and Problem Statement
We want to have user scripting for interactivity for objects, pets and npcs.
Describe the proposed option and how it helps to overcome the problem or limitation
We implement the wasm scripts using libsql and a wasm runtime to be determined.
We had a previous implementation called WASGO. Possible names for the new one is WASGOQuery and WASGO.
Advantages:

WAMR wasn't well liked because it's written in c/c++ and because it's not widely used.
WASMTIME is widely used and used for commercial / financial applications

Disadvantages:

WASMTIME rust is hard to deploy
WAMR is hard to use.

Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams
We ONLY support floating point, integers, strings and byte arrays.

[ ] Compile libsqlite
[ ] Add a wasm engine
[ ] Typed:
[ ] Save a UDF of the notification function of _notification as a string of arbitrary length
[ ] returns a row

Positive Consequences
We can user script our worlds.
Negative Consequences
We cannot get other features in.
Option graveyard

Option: The status quo.
Rejection Reason: This solves nothing.

If this enhancement will not be used often, can it be worked around with a few lines of script?
Knowing what to do is hard.
Is there a reason why this should be core and done by us?
Scriptability is a core feature.
References

V-Sekai
libsql bindgen
wasm udfs in sqlite

Posted as 76e2c681ccfcd21817c8a6bd57d931aae493ce73.


Transitions

This is quite simple, all I'm thinking is a short fade between each wallpaper to make it look a little nicer when it changes.

Unfortunately this is really not possible, as the transition is handled by
Windows, not RW. As far as I know Windows doesn't support yet any
transition animation when changing wallpaper
Il mar 15 ago 2023, 01:28 TriforceofWisdom @.***> ha
scritto:

This is quite simple, all I'm thinking is a short fade between each
wallpaper to make it look a little nicer when it changes.
—
Reply to this email directly, view it on GitHub
https://github.com/Mamiglia/Reddit-Wallpaper/issues/28, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBSX3H6GSBYZ6YJVRYYKPTXVKYCLANCNFSM6AAAAAA3QLNLNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Maybe write the wallpapers into a folder and have windows use it's built in support for slideshows as wallpapers?


better README

Write/generate readme for the project including dev flow, docker setup and prod rollout. Links to the API specs, architecture description

Draft docs added here ff09aa64bf8f1912b23fe70ef9742869557a3ea8


Add unsubscribers to activate context object

We want to make extensions in a way that allows future improvements without massive breaking changes if possible.
We should add some kind of unsubscribers member onto ExecutionActivationContext that is an array of (promises of) unsubscribers or an array of (promises of) objects that have dispose or something along these lines (or maybe we should add one of each since we have each of those, or just stick with one that can accept either and reflect on the object to determine which of these two it is). Similar to VSCode's ExtensionContext.subscriptions (example in their hello world sample extension).
This new stuff on ExecutionActivationContext replaces the return from the extension activate function. Now the extension activate function just returns Promise<void> (no return but it's an async function).
This is to avoid a breaking change with #54 whenever we get to it.

Do you need corresponding follow-up PRs in the template and sneeze-board repos?

I've just been updating the template and letting others update the others lately 😬 but either way. Probably best to make a post in Discord with update instructions if you break something and don't update in other places.


Refactor/internal provider handler

Codecov Report
Patch coverage: 96.77% and project coverage change: +0.02% :tada:

Comparison is base (ffeac66) 91.33% compared to head (6e50174) 91.36%.
Report is 5 commits behind head on dev.

Additional details and impacted files
@@             Coverage Diff              @@
##                dev     #150      +/-   ##
============================================
+ Coverage     91.33%   91.36%   +0.02%
  Complexity     1347     1347
============================================
  Files           132      133       +1
  Lines          3219     3218       -1
  Branches        307      306       -1
============================================
  Hits           2940     2940
  Misses          147      147
+ Partials        132      131       -1

Files Changed
Coverage Δ

...va/cn/crane4j/core/container/ContainerManager.java
100.00% <ø> (ø)

...ser/handler/AbstractAssembleAnnotationHandler.java
90.47% <ø> (ø)

.../parser/handler/AssembleEnumAnnotationHandler.java
88.57% <85.71%> (+2.85%)
:arrow_up:

...e4j/core/container/PartitionContainerProvider.java
88.88% <100.00%> (-1.12%)
:arrow_down:

...arser/handler/AssembleMethodAnnotationHandler.java
91.42% <100.00%> (-1.60%)
:arrow_down:

...ler/InternalProviderAssembleAnnotationHandler.java
100.00% <100.00%> (ø)

...core/support/SimpleCrane4jGlobalConfiguration.java
91.86% <100.00%> (ø)

...sion/spring/DefaultCrane4jSpringConfiguration.java
94.82% <100.00%> (ø)

...j/spring/boot/config/Crane4jAutoConfiguration.java
93.51% <100.00%> (ø)

... and 2 files with indirect coverage changes

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


[CARBONDATA-3765] Refactor Index Metadata for CG and FG Indexes

Why is this PR needed?

CG and FG Indexes support multi-tenant
Refactor DataMap to Index

What changes were proposed in this PR?
CG and FG Indexes support multi-tenant
-> Remove writing datamapschema for cg and fg indexes to system folder
-> Add index related information to tableProperties of main table and hive, as similar to SI, to      support multi-tenancy.
-> All indexes - CG,FG and Secondary Index information will be stored in main table
Does this PR introduce any user interface change?

Yes.

Is any new testcase added?

No

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/886/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2594/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/888/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2596/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/889/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2597/

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2600/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/892/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2609/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/902/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/911/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2620/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/912/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2621/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/915/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2624/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/919/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2628/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2632/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/923/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2636/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/927/

@Indhumathi27 : Just checked few files on high level. Couldn't focus on functionality as there is attracting 300 file rename changes. Suggest to separate rename and functionality(multi-tenant) PR

@ajantha-bhat there are seperate commits for support muti-tenant and datamap refactor in this PR. If still difficult to review, i can raise one more PR

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2677/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/965/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2681/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/969/

We are making cg, fg index like secondary index. But SI is a table, cg fg is not a table. So need separate handling. Which makes code more complex and hard to maintain. @jackylk @qiangcai @indhumathi27

@ajantha-bhat But we are storing only index meta data to carbon table. So, all indexes info will be same

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/978/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2691/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2692/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/979/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/983/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2696/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/988/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2701/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2705/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/992/

@ajantha-bhat Fixed all comments. Please review

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/998/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2710/

please rebase.
LGTM.
I feel two people review is better for this PR as changes are more files and chances of missing some issues are more.
@jackylk , @QiangCai . @akashrn5 , @kunal642 : can anyone else review ?

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2719/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1007/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2723/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1011/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1013/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2725/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1021/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2733/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2741/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1028/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1030/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2743/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1035/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2748/

@Indhumathi27 : It is better to remove system folder disk based schema storage code. If we are not using it anymore.

@ajantha-bhat it has old mv dependency. it will be removed in PR-3692

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1052/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2765/

LGTM


Error while trying to build an image locally from the Docker File

At step
config graphite
ADD conf/opt/graphite/conf/*.conf /opt/graphite/conf/
ADD failed: no source files were specified.  --- Error
Can you please take a look and suggest here. Why is this issue occurring.
@hopsoft

Only these files are seen in the conf directory and opt directory in it.  Any guide here would be helpful, if there is any change .
Step 21/51 : RUN ls -l
---> Running in 229c919b2b78
total 52
-rw-r--r-- 1 root root  1798 Oct 26 18:00 aggregation-rules.conf.example
-rw-r--r-- 1 root root   274 Oct 26 18:00 blacklist.conf.example
-rw-r--r-- 1 root root  2594 Oct 26 18:00 carbon.amqp.conf.example
-rw-r--r-- 1 root root 17809 Oct 26 18:00 carbon.conf.example
-rw-r--r-- 1 root root   888 Oct 26 18:00 relay-rules.conf.example
-rw-r--r-- 1 root root   558 Oct 26 18:00 rewrite-rules.conf.example
-rw-r--r-- 1 root root   827 Oct 26 18:00 storage-aggregation.conf.example
-rw-r--r-- 1 root root   489 Oct 26 18:00 storage-schemas.conf.example
-rw-r--r-- 1 root root   315 Oct 26 18:00 whitelist.conf.example
Removing intermediate container 229c919b2b78
---> 91d513d0da01
Step 22/51 : RUN ls -l conf/opt/graphite/conf/.conf
---> Running in 62d2942d1397
ls: cannot access 'conf/opt/graphite/conf/.conf': No such file or directory


tools/find_deprecated.py for finding deprecation decorators (and remember to remove them :) )

The great work that @Eric-Arellano did annotating all the deprecations with deprecate_func and deprecate_arg allows to quickly find deprecations that needs removal.
This PR adds tools/find_deprecated.py. This utility finds the deprecation decorators and groups them by since parameter. It also checks how many days had passed since the last minor release.
At this point, the current result of running this utility is this:

0.15: Released in August 06, 2020 (1001 days until last minor release)
 - /<redacted>/qiskit/visualization/state_visualization.py:38
 - /<redacted>/qiskit/visualization/state_visualization.py:256
 - /<redacted>/qiskit/visualization/state_visualization.py:364
 - /<redacted>/qiskit/visualization/state_visualization.py:621
 - /<redacted>/qiskit/visualization/state_visualization.py:792

0.16: Released in October 15, 2020 (930 days until last minor release)
 - /<redacted>/qiskit/circuit/library/arithmetic/polynomial_pauli_rotations.py:228

0.17: Released in April 01, 2021 (763 days until last minor release)
 - /<redacted>/qiskit/test/decorators.py:144
 - /<redacted>/qiskit/circuit/bit.py:62
 - /<redacted>/qiskit/circuit/bit.py:84

0.18: Released in July 12, 2021 (660 days until last minor release)
 - /<redacted>/qiskit/algorithms/phase_estimators/phase_estimation_result.py:70
 - /<redacted>/qiskit/opflow/gradients/derivative_base.py:138

0.19: Released in December 06, 2021 (513 days until last minor release)
 - /<redacted>/qiskit/transpiler/instruction_durations.py:173
 - /<redacted>/qiskit/circuit/instructionset.py:98
 - /<redacted>/qiskit/providers/models/backendconfiguration.py:834
 - /<redacted>/qiskit/algorithms/optimizers/adam_amsgrad.py:198
 - /<redacted>/qiskit/algorithms/optimizers/adam_amsgrad.py:199
 - /<redacted>/qiskit/algorithms/optimizers/adam_amsgrad.py:200
 - /<redacted>/qiskit/qobj/__init__.py:84

0.20: Released in March 31, 2022 (398 days until last minor release)
 - /<redacted>/qiskit/visualization/circuit/latex.py:51
 - /<redacted>/qiskit/visualization/circuit/latex.py:52
 - /<redacted>/qiskit/visualization/circuit/latex.py:53
 - /<redacted>/qiskit/visualization/circuit/latex.py:54
 - /<redacted>/qiskit/transpiler/coupling.py:128
 - /<redacted>/qiskit/dagcircuit/dagcircuit.py:529
 - /<redacted>/qiskit/synthesis/evolution/suzuki_trotter.py:54

0.21: Released in June 30, 2022 (308 days until last minor release)
 - /<redacted>/qiskit/execute_function.py:39
 - /<redacted>/qiskit/execute_function.py:40
 - /<redacted>/qiskit/transpiler/passes/scheduling/alap.py:30
 - /<redacted>/qiskit/transpiler/passes/scheduling/asap.py:36
 - /<redacted>/qiskit/transpiler/passes/scheduling/dynamical_decoupling.py:93
 - /<redacted>/qiskit/transpiler/passes/scheduling/alignments/align_measures.py:93
 - /<redacted>/qiskit/transpiler/passes/utils/cx_direction.py:22
 - /<redacted>/qiskit/transpiler/passes/utils/check_cx_direction.py:22
 - /<redacted>/qiskit/algorithms/optimizers/spsa.py:652
 - /<redacted>/qiskit/pulse/transforms/alignments.py:48
 - /<redacted>/qiskit/pulse/transforms/alignments.py:333
 - /<redacted>/qiskit/pulse/transforms/alignments.py:417
 - /<redacted>/qiskit/qpy/interface.py:75

0.22: Released in October 13, 2022 (202 days until last minor release)
 - /<redacted>/qiskit/visualization/counts_visualization.py:60
 - /<redacted>/qiskit/visualization/circuit/_utils.py:199
 - /<redacted>/qiskit/visualization/circuit/_utils.py:287
 - /<redacted>/qiskit/transpiler/passes/calibration/rzx_builder.py:68
 - /<redacted>/qiskit/providers/basicaer/qasm_simulator.py:375
 - /<redacted>/qiskit/pulse/utils.py:113
 - /<redacted>/qiskit/pulse/library/parametric_pulses.py:66
 - /<redacted>/qiskit/pulse/library/parametric_pulses.py:135
 - /<redacted>/qiskit/pulse/library/parametric_pulses.py:247
 - /<redacted>/qiskit/pulse/library/parametric_pulses.py:417
 - /<redacted>/qiskit/pulse/library/parametric_pulses.py:540
 - /<redacted>/qiskit/quantum_info/operators/symplectic/pauli_utils.py:20
 - /<redacted>/qiskit/quantum_info/operators/symplectic/random.py:106

0.23: Released in January 26, 2023 (97 days until last minor release)
 - /<redacted>/qiskit/visualization/state_visualization.py:1294
 - /<redacted>/qiskit/visualization/state_visualization.py:1313
 - /<redacted>/qiskit/visualization/pulse/matplotlib.py:55
 - /<redacted>/qiskit/visualization/pulse/matplotlib.py:292
 - /<redacted>/qiskit/visualization/pulse/matplotlib.py:395
 - /<redacted>/qiskit/visualization/pulse/interpolation.py:28
 - /<redacted>/qiskit/visualization/pulse/interpolation.py:68
 - /<redacted>/qiskit/visualization/pulse/qcstyle.py:32
 - /<redacted>/qiskit/visualization/pulse/qcstyle.py:177
 - /<redacted>/qiskit/transpiler/target.py:244
 - /<redacted>/qiskit/transpiler/passes/synthesis/linear_functions_synthesis.py:30
 - /<redacted>/qiskit/circuit/classicalregister.py:60
 - /<redacted>/qiskit/circuit/quantumregister.py:61
 - /<redacted>/qiskit/pulse/instructions/instruction.py:226
 - /<redacted>/qiskit/pulse/library/symbolic_pulses.py:590
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:505
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:512
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:519
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:526
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:533
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:540
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:547
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:554
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:561
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:958
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:969
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:980
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:991
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:1002
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:1013
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:1024
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:1032
 - /<redacted>/qiskit/qobj/converters/pulse_instruction.py:1043
 - /<redacted>/qiskit/quantum_info/synthesis/two_qubit_decompose.py:1088
 - /<redacted>/qiskit/quantum_info/synthesis/clifford_decompose.py:24
 - /<redacted>/qiskit/quantum_info/synthesis/cnotdihedral_decompose.py:23

0.24: Released in May 04, 2023 (0 days until last minor release)
 - /<redacted>/qiskit/transpiler/target.py:1133
 - /<redacted>/qiskit/transpiler/target.py:1143
 - /<redacted>/qiskit/transpiler/passes/routing/bip_mapping.py:68
 - /<redacted>/qiskit/transpiler/passes/routing/algorithms/bip_model.py:45
 - /<redacted>/qiskit/algorithms/aux_ops_evaluator.py:34
 - /<redacted>/qiskit/algorithms/minimum_eigensolvers/adapt_vqe.py:100
 - /<redacted>/qiskit/algorithms/minimum_eigensolvers/adapt_vqe.py:144
 - /<redacted>/qiskit/algorithms/minimum_eigensolvers/adapt_vqe.py:159
 - /<redacted>/qiskit/algorithms/optimizers/qnspsa.py:258
 - /<redacted>/qiskit/algorithms/optimizers/qnspsa.py:266
 - /<redacted>/qiskit/algorithms/evolvers/real_evolver.py:32
 - /<redacted>/qiskit/algorithms/evolvers/evolution_problem.py:36
 - /<redacted>/qiskit/algorithms/evolvers/evolution_result.py:34
 - /<redacted>/qiskit/algorithms/evolvers/imaginary_evolver.py:32
 - /<redacted>/qiskit/algorithms/evolvers/trotterization/trotter_qrte.py:68
 - /<redacted>/qiskit/algorithms/phase_estimators/hamiltonian_phase_estimation.py:96
 - /<redacted>/qiskit/algorithms/phase_estimators/ipe.py:42
 - /<redacted>/qiskit/algorithms/phase_estimators/phase_estimation.py:84
 - /<redacted>/qiskit/algorithms/amplitude_amplifiers/grover.py:117
 - /<redacted>/qiskit/algorithms/amplitude_amplifiers/grover.py:199
 - /<redacted>/qiskit/algorithms/amplitude_amplifiers/grover.py:213
 - /<redacted>/qiskit/algorithms/eigen_solvers/numpy_eigen_solver.py:51
 - /<redacted>/qiskit/algorithms/eigen_solvers/eigen_solver.py:38
 - /<redacted>/qiskit/algorithms/eigen_solvers/eigen_solver.py:90
 - /<redacted>/qiskit/algorithms/eigen_solvers/vqd.py:100
 - /<redacted>/qiskit/algorithms/eigen_solvers/vqd.py:774
 - /<redacted>/qiskit/algorithms/amplitude_estimators/fae.py:51
 - /<redacted>/qiskit/algorithms/amplitude_estimators/fae.py:113
 - /<redacted>/qiskit/algorithms/amplitude_estimators/fae.py:127
 - /<redacted>/qiskit/algorithms/amplitude_estimators/mlae.py:56
 - /<redacted>/qiskit/algorithms/amplitude_estimators/mlae.py:140
 - /<redacted>/qiskit/algorithms/amplitude_estimators/mlae.py:154
 - /<redacted>/qiskit/algorithms/amplitude_estimators/iae.py:53
 - /<redacted>/qiskit/algorithms/amplitude_estimators/iae.py:136
 - /<redacted>/qiskit/algorithms/amplitude_estimators/iae.py:150
 - /<redacted>/qiskit/algorithms/amplitude_estimators/ae.py:67
 - /<redacted>/qiskit/algorithms/amplitude_estimators/ae.py:135
 - /<redacted>/qiskit/algorithms/amplitude_estimators/ae.py:149
 - /<redacted>/qiskit/algorithms/minimum_eigen_solvers/numpy_minimum_eigen_solver.py:42
 - /<redacted>/qiskit/algorithms/minimum_eigen_solvers/minimum_eigen_solver.py:39
 - /<redacted>/qiskit/algorithms/minimum_eigen_solvers/minimum_eigen_solver.py:96
 - /<redacted>/qiskit/algorithms/minimum_eigen_solvers/vqe.py:130
 - /<redacted>/qiskit/algorithms/minimum_eigen_solvers/vqe.py:671
 - /<redacted>/qiskit/algorithms/minimum_eigen_solvers/qaoa.py:64
 - /<redacted>/qiskit/utils/quantum_instance.py:147
 - /<redacted>/qiskit/utils/run_circuits.py:43
 - /<redacted>/qiskit/utils/run_circuits.py:108
 - /<redacted>/qiskit/utils/measurement_error_mitigation.py:33
 - /<redacted>/qiskit/utils/measurement_error_mitigation.py:81
 - /<redacted>/qiskit/utils/measurement_error_mitigation.py:126
 - /<redacted>/qiskit/utils/measurement_error_mitigation.py:205
 - /<redacted>/qiskit/utils/backend_utils.py:53
 - /<redacted>/qiskit/utils/backend_utils.py:74
 - /<redacted>/qiskit/utils/backend_utils.py:94
 - /<redacted>/qiskit/utils/backend_utils.py:118
 - /<redacted>/qiskit/utils/backend_utils.py:135
 - /<redacted>/qiskit/utils/backend_utils.py:155
 - /<redacted>/qiskit/utils/backend_utils.py:171
 - /<redacted>/qiskit/utils/backend_utils.py:200
 - /<redacted>/qiskit/utils/backend_utils.py:219
 - /<redacted>/qiskit/utils/backend_utils.py:238
 - /<redacted>/qiskit/utils/backend_utils.py:258
 - /<redacted>/qiskit/utils/mitigation/circuits.py:25
 - /<redacted>/qiskit/utils/mitigation/circuits.py:43
 - /<redacted>/qiskit/utils/mitigation/circuits.py:124
 - /<redacted>/qiskit/utils/mitigation/_filters.py:46
 - /<redacted>/qiskit/utils/mitigation/_filters.py:228
 - /<redacted>/qiskit/utils/mitigation/fitters.py:38
 - /<redacted>/qiskit/utils/mitigation/fitters.py:222
 - /<redacted>/qiskit/opflow/utils.py:19
 - /<redacted>/qiskit/opflow/utils.py:40
 - /<redacted>/qiskit/opflow/utils.py:61
 - /<redacted>/qiskit/opflow/exceptions.py:22
 - /<redacted>/qiskit/opflow/operator_globals.py:36
 - /<redacted>/qiskit/opflow/operator_base.py:48
 - /<redacted>/qiskit/opflow/primitive_ops/matrix_op.py:39
 - /<redacted>/qiskit/opflow/primitive_ops/pauli_sum_op.py:37
 - /<redacted>/qiskit/opflow/primitive_ops/primitive_op.py:96
 - /<redacted>/qiskit/opflow/primitive_ops/pauli_op.py:38
 - /<redacted>/qiskit/opflow/primitive_ops/circuit_op.py:34
 - /<redacted>/qiskit/opflow/primitive_ops/tapered_pauli_sum_op.py:38
 - /<redacted>/qiskit/opflow/primitive_ops/tapered_pauli_sum_op.py:91
 - /<redacted>/qiskit/opflow/mixins/tensor.py:31
 - /<redacted>/qiskit/opflow/mixins/star_algebra.py:43
 - /<redacted>/qiskit/opflow/list_ops/summed_op.py:34
 - /<redacted>/qiskit/opflow/list_ops/list_op.py:56
 - /<redacted>/qiskit/opflow/list_ops/tensored_op.py:35
 - /<redacted>/qiskit/opflow/list_ops/composed_op.py:37
 - /<redacted>/qiskit/opflow/state_fns/operator_state_fn.py:40
 - /<redacted>/qiskit/opflow/state_fns/cvar_measurement.py:44
 - /<redacted>/qiskit/opflow/state_fns/sparse_vector_state_fn.py:41
 - /<redacted>/qiskit/opflow/state_fns/dict_state_fn.py:41
 - /<redacted>/qiskit/opflow/state_fns/vector_state_fn.py:40
 - /<redacted>/qiskit/opflow/state_fns/circuit_state_fn.py:47
 - /<redacted>/qiskit/opflow/state_fns/state_fn.py:116
 - /<redacted>/qiskit/opflow/converters/circuit_sampler.py:55
 - /<redacted>/qiskit/opflow/converters/two_qubit_reduction.py:39
 - /<redacted>/qiskit/opflow/converters/converter_base.py:33
 - /<redacted>/qiskit/opflow/converters/abelian_grouper.py:45
 - /<redacted>/qiskit/opflow/converters/dict_to_circuit_sum.py:32
 - /<redacted>/qiskit/opflow/converters/pauli_basis_change.py:59
 - /<redacted>/qiskit/opflow/expectations/matrix_expectation.py:28
 - /<redacted>/qiskit/opflow/expectations/aer_pauli_expectation.py:42
 - /<redacted>/qiskit/opflow/expectations/cvar_expectation.py:58
 - /<redacted>/qiskit/opflow/expectations/expectation_factory.py:39
 - /<redacted>/qiskit/opflow/expectations/expectation_base.py:41
 - /<redacted>/qiskit/opflow/expectations/pauli_expectation.py:45
 - /<redacted>/qiskit/opflow/evolutions/matrix_evolution.py:34
 - /<redacted>/qiskit/opflow/evolutions/pauli_trotter_evolution.py:54
 - /<redacted>/qiskit/opflow/evolutions/evolution_factory.py:28
 - /<redacted>/qiskit/opflow/evolutions/evolved_op.py:43
 - /<redacted>/qiskit/opflow/evolutions/evolution_base.py:33
 - /<redacted>/qiskit/opflow/evolutions/trotterizations/trotter.py:25
 - /<redacted>/qiskit/opflow/evolutions/trotterizations/trotterization_base.py:29
 - /<redacted>/qiskit/opflow/evolutions/trotterizations/suzuki.py:38
 - /<redacted>/qiskit/opflow/evolutions/trotterizations/trotterization_factory.py:26
 - /<redacted>/qiskit/opflow/evolutions/trotterizations/qdrift.py:40
 - /<redacted>/qiskit/opflow/gradients/qfi.py:40
 - /<redacted>/qiskit/opflow/gradients/qfi_base.py:33
 - /<redacted>/qiskit/opflow/gradients/gradient.py:40
 - /<redacted>/qiskit/opflow/gradients/hessian.py:43
 - /<redacted>/qiskit/opflow/gradients/derivative_base.py:50
 - /<redacted>/qiskit/opflow/gradients/natural_gradient.py:55
 - /<redacted>/qiskit/opflow/gradients/hessian_base.py:25
 - /<redacted>/qiskit/opflow/gradients/gradient_base.py:28
 - /<redacted>/qiskit/opflow/gradients/circuit_gradients/circuit_gradient.py:39
 - /<redacted>/qiskit/opflow/gradients/circuit_gradients/lin_comb.py:104
 - /<redacted>/qiskit/opflow/gradients/circuit_gradients/param_shift.py:50
 - /<redacted>/qiskit/opflow/gradients/circuit_qfis/circuit_qfi.py:39
 - /<redacted>/qiskit/opflow/gradients/circuit_qfis/overlap_block_diag.py:42
 - /<redacted>/qiskit/opflow/gradients/circuit_qfis/overlap_diag.py:41
 - /<redacted>/qiskit/opflow/gradients/circuit_qfis/lin_comb_full.py:39
 - /<redacted>/qiskit/quantum_info/operators/symplectic/stabilizer_table.py:172
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:218
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:226
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:232
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:242
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:258
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:270
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:282
 - /<redacted>/qiskit/quantum_info/operators/symplectic/clifford.py:294
 - /<redacted>/qiskit/quantum_info/operators/symplectic/pauli_table.py:130

0.25: Future release
 - /<redacted>/qiskit/transpiler/preset_passmanagers/common.py:550
 - /<redacted>/qiskit/tools/jupyter/library.py:53
 - /<redacted>/qiskit/tools/jupyter/library.py:122
 - /<redacted>/qiskit/tools/jupyter/library.py:142
 - /<redacted>/qiskit/tools/jupyter/library.py:206
 - /<redacted>/qiskit/tools/jupyter/library.py:232
 - /<redacted>/qiskit/tools/jupyter/jupyter_magics.py:178

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.03%) to 85.928%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
93.76%

crates/accelerate/src/vf2_layout.rs
3
94.74%

crates/qasm2/src/lex.rs
4
90.89%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
71403

Relevant Lines:
83096

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
17 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.008%) to 87.008%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
2
91.41%

qiskit/pulse/library/waveform.py
3
93.75%

crates/qasm2/src/parse.rs
12
97.13%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
74053

Relevant Lines:
85111

💛  - Coveralls


animation plugin moved

react-addons-css-transition-group moved to react-transition-group

Thank you!