User tracking

Currently there is no tracking and hence no consent popup. But several people mentioned the intention to use Google Analytics in the pilot applications.
I suggest adding an option to add a tracking GA ID to _config.yml that will then insert the tracking scripts/iframe and add a consent banner (with translatable text controlled by the editors).
And then have an option to overwrite the includes if someone has the need to replace the standard GA scripts with a different config or another provider.

For Google Analytics, I think it's appropriate for us to use Consent mode:

Consent mode (beta) allows you to adjust how your Google tags behave based on the consent status of your users. You can indicate whether consent has been granted for Analytics and Ads cookies. Google's tags will dynamically adapt, only utilizing measurement tools for the specified purposes when consent has been given by the user.

If we deny "ad storage" access, then Google Analytics/Google Ads musn't use a hosted portal to add to a user's browsing profile. I expect we can always leave this as denied.
If we also deny "analytics storage" then Google Analytics is only sent "cookieless pings ... for basic measurement and modelling purposes".
It's worth testing, but https://www.simoahava.com/analytics/consent-mode-google-tags/ (and the comments) suggest the "cookieless ping" data isn't shown in Google Analytics, but eventually will be shown somehow.
There is some debate on whether the "cookieless pings" require consent at all. Presumably Google thinks so, otherwise I don't see a purpose to this, but this article ("Can these technologies actually be used without user consent") says the German data regulator says this is not possible:

According to the Orientation Help for Providers of Telemedia from the DSK, reach measurement can indeed represent legitimate interest for the website operator – but is only then necessary in the context of weighing up interests if no personal data is forwarded to third parties (e.g. Google), and the data is not to be used for the operator’s own purposes.

I assume browser privacy extensions, ad blockers etc will continue to block all this anyway.  The only way around that would be to self-host basic analytics (i.e. send "cookieless pings" to a server we control, or process the webserver logs), but we should know what we're trying to measure before starting on something like that.
CC @thomasstjerne for similar issues for COL.

Before proceeding with this issue we should clarify what legal responsibilities GBIF as a host have for how this is done.

I believe this will need the following:

A privacy policy markdown file that is in each HP. GBIF will provide a default, which will need a few minor edits from each installation to e.g. put in contact email addresses. A draft is now with the legal advisors.
A link to the privacy policy in the footer
A user acceptance highlighting the privacy policy, and allowing users to opt-in to the tracking. If they choose to opt out, then no GA should be used.
There should be a means of triggering opt-in again, should the privacy policy change.

An example of this approach is https://datacite.org/
Is this easily feasible, please?

Standard Privacy policy
In the interest of making it easy to get a privacy page: I will add a privacy page to all portals. It will use a new layout type called standardPrivacy. The privacy page can be configured with 4 variables available in _config.yml. The privacy template is not ready for usage yet, but when the theme is updated with the correct version, then so will all the portals privacy page. As a portal owner it is already possible to fill the variables in _config.yml under privacy.
If the portal owners would rather write their own privacy policy, then they can simply delete the file and config again.
See also https://hp-theme.gbif-staging.org/privacy-policy-template
Google analytics
It has always been possible to add google analytics to the portals, but we have now made it easy to do so while getting the users consent. See https://hp-theme.gbif-staging.org/measurements

@timrobertson100
https://github.com/gbif/jekyll-hp-base-theme/blob/master/_includes/privacyTemplate.md
Updating above will update the privacy policy on all pages that use the template. Currently it is just a stub showing how to use the variables and with a button to reset user preferences.

Thank you for making this process easier. Will there be any translations available for the standard template?


Keep $ref dereference when writing the update files

Currently, openapi-format dereferences the OpenAPI documents to do its formatting, sorting, ... and write a dereferenced result.
Investigate the option to leverage: https://www.npmjs.com/package/json-refs to format the OpenAPI documents and update the $ref values in different files.
const jsonRefs = require('json-refs');

const json = {
  "foo": {
    "$ref": "#/bar"
  },
  "bar": {
    "baz": "qux"
  }
};

const options = {
  filter: ['relative', 'remote'],
  loaderOptions: {
    processContent: (res, callback) => callback(undefined, res.text)
  }
};

jsonRefs.resolveRefs(json, options).then(
  (results) => {
    // make changes to the resolved object
    results.resolved.bar.baz = "newValue";
    // write the changes to the $ref locations
    jsonRefs.updateRefs(results.refs, results.resolved).then(
      (updated) => console.log(updated),
      (err) => console.log(err)
    );
  },
  (err) => console.log(err)
);

yes this would be great. in addition we make heavily use of $ref to other files what the best solution to tackle those? format one file after the other?

Cool thanks a lot. I‘ll explore myself options too..

hi @rngtng
With the release 1.24.0 of OpenAPI, we introduced the option to split OpenAPI files in a file/folder structure.
The split is a programmatically break-up of the OpenAPI in 1 main OpenAPI and per path and per component a separate file, with this kind of process flow.
graph TD
    A[Start] --> B[Load OpenAPI Split File]

    B --> C[Apply Bundling]
    C --> D[Apply Filtering]
    D --> E[Apply Sorting]

    E --> F{Split OpenAPI?}

    F -- Yes --> G[Split into Multiple Files]
    F -- No --> H[Save as Single File]

    G --> I[Save Modular Structure]
    H --> I[Save Final Output]

    I --> J[End]

You can give it a try
npx openapi-format https://raw.githubusercontent.com/thim81/openapi-format/refs/heads/main/test/__utils__/train.yaml -o split/train.yaml --split

Let me know what you think of it.


Add a legend to filter types of trees on the map

A TreeLayer component is created for each health value (good, fair, etc.), including empty values.  The MapboxLegendControl component then shows an option to show/hide each layer.

To do:

[X] Figure out how to style the legend icons.
[x] Decide on colors for the various health states.
[x] Add a layer for all the trees that have no health data (like in SF).
[x] Figure out how to share the vector tile source across multiple layers.
[x] Fix visible, disabled scrollbar on Windows.

I've updated the colors based on the mapping suggested in the comment above.  The exact color values are easy to tweak, if needed.  The circles are now opaque, which makes it easier to control their color.  There's a separate layer for trees with health no data, which covers nearly all of SF.

This PR also uses the solid colors in the health slider, so it's clearer where the slider stops are and how they map to the tree colors.
This has been rebased on #109, so that should be merged first.


Nightly CI step - reduce no output timeout for Quorum ATs

Occasionally these hang so we should not keep waiting for output
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if
updates are required.

Changelog

[x] I thought about the changelog and included a changelog update if required.

This would prevent wasting CI credits eg on situations like this where for unknown reason there is no output in 30 min but we wait https://app.circleci.com/pipelines/gh/hyperledger/besu/18238/workflows/5369c0ef-612b-4ada-a61f-d0e87c6d2720/jobs/111221


[Umbrella] Apache Kyuubi Graduation Tasks

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the proposal
The ASF board has approved a resolution to graduate Kyuubi into a full Top Level Project. Thanks to everyone for your help to get to this point.
To transition from the Apache Incubator to a new TLP, there's a few action items we need to do to complete the transition. These are identified by https://incubator.apache.org/guides/transferring.html#life_after_graduation.
Task list

Update Incubator status records

[ ] Update the incubator status file (in svn)
[ ] Update podling status page

Source repo changes

[x] Create JIRA ticket INFRA-24026 to request ASF Infra remove "incubator-" prefix of git repos
https://github.com/apache/incubator-kyuubi
https://github.com/apache/incubator-kyuubi-website
[x] Create JIRA ticket INFRA-24029 to request ASF Infra move dist folder in SVN repositories from the incubator to other locations
old: https://dist.apache.org/repos/dist/release/incubator/kyuubi
new: https://dist.apache.org/repos/dist/release/kyuubi
[x] Post announcement to dev list telling everyone the repo is about repos renaming
https://lists.apache.org/thread/vvs1p8bgxpsp6nldyrd7gd1j0or1wg7n
[x] Post an announcement containing instructions for developers describing how to change their git remotes.
https://lists.apache.org/thread/vvs1p8bgxpsp6nldyrd7gd1j0or1wg7n (same as above)
[ ] Update website, pom.xml, and other resources to point to the new repository location

Source code

[ ] Remove "Incubating" from source code
[ ] Remove DISCLAIMER from git repo
[ ] Remove MATURITY.md from git repo
[ ] Update Release scripts and template
[ ] Update GitHub CI workflows
[ ] Update scripts under dev folder

Websites

[ ] Remove incubating/podding related resources from the website.

Ecosystem

[ ] Remove Incubating from third party projects, including Zeppelin, DBeaver
https://github.com/apache/zeppelin/pull/4540
https://github.com/dbeaver/dbeaver/pull/18575

cc @lightning-L  could you help address the source code part tasks?

cc @lightning-L could you help address the source code part tasks?

ok

I will submit a follow-up PR to close remaining source code tasks

we shall also update the process for becoming a committer or pmc

Correcting grammar and spelling  mistakes  in settings page of docs  in https://github.com/apache/kyuubi/pull/4161 .

Thanks all!


Djibouti Number showing as invalid when its valid

The number +253 77 080000 is a valid phone number from Evatis carrier in Djibouti and is showing up as invalid.

Hi ,
Thanks for reporting the issue.
When adding numbers or ranges of numbers to libphonenumber it is best it we have some supporting documentation to help us. Do you know of any website or other documentation which could help us determine which range or ranges we should add?
Anything you can do to supply evidence for the validity of the number (including screen shots or links to web pages) will be greatly appreciated.

@mcocaro
We can't connect to this specific number. Did you mean to ask for +253 77 08XXXX as a range?
Please provide evidence that this range is assigned to Evatis - without documentation we can't proceed with the change.
Help us help you! Use our contribution guidelines when reporting issues.

@mcocaro
Fixed in release 7.2.6: https://libphonenumber.appspot.com/phonenumberparser?number=%2B253+77+080000


Introduced a custom NATS logger facade

Rewired all STDOUTS to this facade and added extensive unit tests.
Added new logs for dns resolving and socketdataport timeout to showcase usage in 2 examples where logging can be valuable.
No other NATS code or APIs have been touched - also not the log process provisioning code.
This may then be done upon request as well as making the facades interface more convenient with parameters, log level filtering in the stdoutlogger,  etc...
Happy tor receive your feedback and change things as per request.
@scottf FYI and thx again for your time :-)

@stefanLeo Ok so this is not bad, but I can't use it this way. I was okay with only providing a way to handle existing trace statements, not add logging.

I would add a field in Options that accepts a TraceLogger implementations.

The default implementation NatsTraceLogger given by the factory, the output of _trace has to be exactly the same as it was before.
String timeStr = DateTimeFormatter.ISO_TIME.format(LocalDateTime.now());
"[" + timeStr + "] connect trace: " + message

Consider that someone might already be relying on this exact format in their logs, we cannot break this behavior.

I would prepare 2 default implementations, one when isTraceConnection is true and one when it's false. The false is completely empty (no-op), reducing the need to call if (trace) { _trace(...); }, just call the impl directly.

I see you made some changes to ServerPool and SocketDataPortWithWriteTimeout. The best I can offer is if you need logging in here is you will have to write your own and provide them in Options. The logging in  SocketDataPortWithWriteTimeout is actually not meant to be logged. It's actually a workaround for java socket write not having a write timeout like it has a read timeout, i.e. not an error situation, but an error handling situation.

I did incorporate all of your feedback. Thx. I hope I did understand your last point correct... I can change it again if I got it wrong.
The lib should now behave exactly as before this PR in the default option and connecttrace option.
I left in den DNS and Sockettimeout logs for now,  but reduced their log level which means noone will ever see them unless explicitly asked for. If you insist on removing them I will do so. I think providing more logs is better than less and then let the custom logger provided by the lib consumer decide what he/she wants to log or not. Otherwise people are basically blind in production if something happens or have to override and maybe copy code just to get some information about what has happened, which is also dangerous at times...

This is what I was thinking: https://github.com/nats-io/nats.java/pull/1077

I did now make the logger connection specific where needed and removed nooplogger again. This can be covered much better by  log levels and should also improve performance as less objects are created in case logging is disabled. So i.e., it is closer to NoOpLogger than it was before.
Let me know if I have to remove the logs I added - these should not affect performance at all as they are not on the ciritical path.
I was thinking about at a single threadpool for decoupling calls to provided/custom loggers in the first place, but thought that might be an overkill and people can still do so on their own and most logging frameworks anyhow do that today.  I can add that however if you think this is beneficial.
Regarding log and perfomrance in general: I think the world is turning that way as you also do with NATS server adding open telemetry support in 3.11, which I think is an awesome feature. I.e., everyone is adding not only logs but metrics and traces.
At least the C# 2.0 NATS client is producing some logs. Go Client only limited but still providing logs. JS seems to have some console logs as well.. So we are in good company ;-)

As far as the trace logging I'd prefer to use the PR I built as it is consistent with plugging in something per connection.
I've been talking with the client lead. The feedback I'm getting is that adding logging must have a solid use case behind it and cannot affect performance. Connection logging is probably safe since it's not a time sensitive operation like publishing a large volume of messages.
That being said, I'd like to understand your reason for adding the logging where you did and how important it really is.
Also, there is already ConnectionListener which is used for async connection events and can be overridden with a custom implementation. We can certainly add some api to the interface (and have default implementations so as to maintain backward compatibility), and the user's implementation can use whatever logging they want.
The point of all this is that I'm not sure that this is necessary and really need a good reason to be able to defend this to my lead.
Like the place you added to the function that calls connect. This can easily be accomplished by the user logging just before they call this and with trace and/or connection listener it feels like there is already enough information.

@stefanLeo Copied from https://github.com/nats-io/nats.java/pull/1077
Yes. Fully understood. So fhe use cases are from my PoV:

Have an easy integration to grab whatever you log deep inside your code and ingest into my custom logging framework incl. the timestamps etc.
I fully agree that excessive logging ist not a good idea here, but adding logs at some critical points can help a lot with troubleshooting especially for new users who do not yet know what is important for nats to add to as listeners etc...
If the lib provides its set of logs it is much easier for you as a maintainer to debug/analyse issues on a customer site or if anyone opens a bug...
After all it is then your logs and not just some provided by some custom injected logging that may be compleltely wrong and/or it takes you ages to understand those logs.
So far for logging in general. Specifically: With DNS we had issues with the DNS server during failover tests  in Openshift which led to reconnection timeouts of 30+ secs. It took us one week to figure out that the dns part was problematic using a profiling techniques.  I.e., imho whenever something you request from an external system  you should log it and the returned result in case it is something that does not happen all the time e.g.. connection interruptions or abortions, dns resolving, config parsing issues,... things like that.
Simply to make everyones life easier when having to troubleshoot issues or integrate nats.


Feature Request: Keypad Touch support

Problem
There is no support for the Keypad Touch device.
Solution
Support the device. Integrating it as switch maybe? Thank you.
Alternatives
No response
Additional context
No response

What would you like it to do?


App Icon

Prepare any App Icon

Maybe sth really basic like the "info" icon in a primary/accent app color:

cc What's your opinion @Rasmuhamed ?

I choose the "info outline" icon.


Feature/2575 Amend messaging on Send reminders modal

What's included?
Closes #2575
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
Example exercise

Go to the draft applications of an exercise and hit the "Send reminders" button.
Check if the message is updated.

Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
Additional context
Screenshot:

Related permissions
Have permissions been considered for this functionality?

No permission changes required
Permissions have been added / updated. Details:

PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING

@nickaddy I just checked and the notification is enabled on Develop. So you should get the reminder email.


classify different kinds of retainments in dispatching

What happened:
https://github.com/kubernetes-sigs/kubefed/blob/eda276709b8abb69bac2917b513ddd6b682bab9c/pkg/controller/sync/dispatch/managed.go#L212-L218
Now the dispatching codes show that overriding will be done after the retainment, but is it always a wise choice?
What you expected to happen:
IMO, the retainments should be classified to two kinds,

the fields which is generated from local clusters, such as .spec.clusterIP in Service
the fields which should be ignored by kubefed, such as .spec.replicas in Deployment when hpa enabled

For the first kind, I think the overrides should take first place rather than the retainments, but for the second kind, I think the retainments are more important than the overrides, the desired replicas in both template.spec.replicas and overrides should not be cared because the HPA controller will take control of this.
/discussion

Maybe we can separate the function RetainClusterFields into RetainGeneratedClusterFields and RetainRequiredClusterFields to solve this problem.

RetainGeneratedClusterFields

ApplyOverrides

RetainRequiredClusterFields

/remove-lifecycle stale
Still working on this.


Progress page stuck on loading

Seconded, and weird things going on in my profil.

Okay, I'll look into it


roxctl cant connect to central via gRPC with no way to switch to WebSocket

I'm trying to perform an image scan on StackRox via roxctl, but I can't currently because of an error:
$ ./roxctl image check -e "stackrox.cfappsecurity.com:443" --image "ubuntu" --token-file roxapi
ERROR:  Checking image failed: could not check build-time alerts: rpc error: code = Unavailable desc = transport: receiving gRPC response from remote endpoint: 464 , content-type . Retrying after 3 seconds...

The problem with this seems to be the communication between roxctl and the Central service, which, in my cluster, is sistting behind an Amazon ALB, which does not support gRPC. Is there a way of connecting to Central via roxctl, using WebSocket instead of gRPC?

Hi @shodanwashere!
Thanks for checking in. Yes, you can use WebSockets instead of gRPC if your LoadBalancer doesn't support it.
You can prefix the address of central with wss:// to switch to WebSockets 😄
Example:
roxctl sensor generate k8s --central wss://stackrox-central.example.com:443
Feel free to reopen/comment on this issue should you have further problems!


utilize the quota_reset hdfs constant

Yeah, I was wondering what was used by hdfs dfsadmin -clrQuota/hdfs dfsadmin -clrSpaceQuota. @ronny-macmaster all tested out okay?


Develop Tooling Around Gorgonia

Here are some tooling ideas:

A program that detects x := tensor.New(tensor.WithShape(1,2,3)) as something that will definitely fail at runtime (because no Dtype or backing was passed in)
Collorary to the above - detect that this is an ineffectual setting: x := tensor.New(tensor.Of(dt), tensor.WithBacking(a)) - the main reason is the backing type will override the tensor.Of option.
Better graph output - maybe interactive as graphviz doesn't seem to handle big graphs

Perhaps it is worth sticking with the spirit of Go and trying to make sure that code is written to prevent failures at runtime, even without additional tools. I'd certainly expect that of the core functions and types. Maybe by combining default rules (clearly listed in the documentation) and a logging option (whenever defaults override or fill in for user selections).

I think for the most part that's true - most functions and method return an error, leaving it to the user to handle. The only point of contention I have is the New functions - by convention the New functions don't return an error. Rather they panic. Hence the idea.


Edit command unique feature

Resolves #116, #109

Update EditCommandParser to parse unique identifier as well

Add CLI Syntax for unique identifier for edit command

Update EditCommand to support editing student based on unique identifier aside from index

Add size method for ArgumentMultimap class

Add JUnit Tests for EditCommand and EditCommandParser

Update UG

Fix merge conflicts and mispelling. Otherwise LGTM


Supplementary material

Dear author,
Thank you for your insightful works! I am sorry to bother you. Where can the supplementary materials of your paper be found?

Thank you for your comment. I have uploaded it. You can find a link to it on the ReadMe page.


fix typo in get-started-macvlan.md

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks, @BSWANG :)


What the Hell?

Windows Terminal version (or Windows build number)
1.7.1091.0
Other Software
No response
Steps to reproduce
launch Azure Cloud Shell and login
Expected Behavior
No response
Actual Behavior

Do you also get Chinese in the command palette etc., or only in the Azure Cloud Shell?

See also https://github.com/microsoft/terminal/issues/8972#issuecomment-770832800.

@KalleOlaviNiemitalo  I think he's complaining that Azure Cloud Shell immediately exits after connection.

Okay, so it crashed right around the AzureConnection::_StoreCredential code. I wonder if we crashed trying to store the credentials. A feedback hub dump would be informative.
/feedback


ng-include causes Error: only one instance of babel/polyfill is allowed

Since upgrade to 1.2 and passed ng.html/js to .html/js all my ng-include directive cause this error.
WARNING: Tried to load angular more than once.
Error: only one instance of babel/polyfill is allowed
    at Object.eval (eval at <anonymous> (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22), <anonymous>:2963:9)
    at Object.2.core-js/shim (eval at <anonymous> (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22), <anonymous>:2966:4)
    at s (eval at <anonymous> (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22), <anonymous>:2861:254)
    at e (eval at <anonymous> (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22), <anonymous>:2861:425)
    at eval (eval at <anonymous> (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22), <anonymous>:2861:443)
    at eval (eval at <anonymous> (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22), <anonymous>:7124:4)
    at eval (eval at <anonymous> (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22), <anonymous>:7131:3)
    at eval (native)
    at http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:373:22
    at Function.jQuery.extend.globalEval (http://localhost:3000/packages/jquery.js?bd30605bc9f8429d01bae2d29081902d10a6c400:374:7) <ng-include src="'client/layout/footer.html'" include-replace="" class="ng-scope">

However the included templates are rendered in the browser. I can't get what is going wrong. I tried the workaround here

Hi @dagatsoin,
Usualy all the errors and warning the related to multiple loading of packages is related to the way that Meteor handles 404 pages.
If you try to load an HTML that does not exists, you will get 404 and Meteor will give you the main page instead of error.
I think in this case you changed the file names to .html instead of .ng.html and you did not change it in the routes defintion or somewhere else in the code you use the file path.
Can you share your code?
Thanks.

@dagatsoin, I am having the same problem with angular-meteor version 1.2.2. Based on my limited understanding, it seems that two different plugins are trying to load babel/polyfill. I think that one of them is angular-meteor (or one of its dependencies) and the other is ecmascript (or one of its dependencies). I removed the ecmascript package from my project, but it still appears in .meteor/versions because it is apparently still depended on another package, such as the core ddp-server package. I could be completely wrong, but that is my best guess of what our problem is. Unfortunately, I have no idea how to go about solving it.

@canac - can you also share you project's code?

@dotansimha, here you go: https://github.com/canac/meteor-test. Obviously, that is not my real my application, just a stripped down example with just enough code to reproduce the error. Thanks for looking at it!

Thanks @canac.
It is just as I described in my previous comment.
You want to include your file template.html inside your index.html, so you used:

But Meteor compiler saves each template on it's own path, ignoring the index.html location, so the actual code should be:

So when you try to load template.html, you actually get 404 which leads to the main page in Meteor so you get the main page included inside the main page... and that's the reason you get the warnings about loading some packages twice.
@dagatsoin, I think this is also relevent to your issue, so please try this solution as well.

@dotansimha, thank you so much for looking at my code. Unfortunately, the change you suggested did not work for me. Did it work for you with my code? I pushed it to the client branch of my repo if you want to check that I made the change that you meant.
By the way, I did not mention this at first, but I am also getting the WARNING: Tried to load angular more than once warning in my developer console. That might be related to this issue. Then again, it might not.

@canac - Yes, the AngularJS warning is related, it also loaded twice.
Just git cloneed your project again and it works for me, this is the result:

Please try to meteor reset and then run your project again, also make sure you browser is ignoring cache (http://superuser.com/questions/89809/how-to-force-refresh-without-cache-in-google-chrome).
If this does not work for you, please upload your .meteor/versions and .meteor/packages.
Thanks!

@dotansimha The meteor reset worked for me! Thank you so much for your help! Does running that command solve your problem as well, @dagatsoin?

meteor reset did not work for me. So I clean up the .meteor/packages and manually remove ecmascript and accounts-ui
It works fine now.

@dotansimha I had the same issue, after correcting my routes files I was still receiving the error and warning regarding loading Angular twice...meteor reset worked for me!  Thanks so much

I had the same error with my code. And meteor reset  is works for me. But I am confused about this.  @dotansimha Can you describe it? Thanks.

@JackyXiong - meteor reset just resets your project. It also clears your entire data from the Mongo, so actually I think that meteor rebuild might solve the problem aswell without removing the data.

@dotansimha Thank you.But there is no command named meteor rebuild.In your opinion, is meteor rebuild means meteor build again？

@JackyXiong I meant meteor rebuild, it does not documented in the Meteor docs, be it exists, just try :)
You can find a discussion about this issue here: https://github.com/meteor/meteor/issues/5328

I was also getting similar error after step-7(Folder structure) of the angular-meteor tutorial (http://www.angular-meteor.com/tutorials/socially/angular1/folder-structure)  And was fixed after meteor rebuild command.

Indeed it seems appears each time we move a bunch of files into another folder.

If you run meteor rebuild, but still get the error in some page.Check your template path is right again.

I think that in Angular Meteor 1.3 we handle caching better and it does not suppose to happen anymore.
Please let me know if that helped

hi everyone...
I have a situation where i have some json files for translations. if I keep them in public folder they load perfectly well. where as if i keep them in any other folder in Client then i dont know why the angular-meteor does not recognise the path.
I tried putting the file in Client/MyModule/i18n/en.json and tried giving the urlTemplate as
$translateProvider.useLoader('$translatePartialLoader', {             //urlTemplate: '{part}/i18n/{lang}.json' // only works if the file is in public folder             urlTemplate: 'client/fuse/toolbar/i18n/en.json' // does not work.         });
can anyone help me.

@ansaries if it's still an issue, please open a separate issue for that, thank you


Treat qrcode as dependency rather than peerDependency

In version 1.x, qrcode is dependency, but it changed now, it is peerDependency now. I'm really puzzled about what makes this change.
In my opinion, users don't need to install qrcode manually if qrcode is treated as dependency.

For a peer dependency, users can choose the exact version of qrcode as they need, just like Vue components don't list vue package as a dependency but as a peer dependency.

how about use overrides and resolutions properties to replace peer dependency?
https://stackoverflow.com/a/64452515


[google_sign_in] Fix serverAuthCode getToken on iOS

Description
The method of getting serverAuthCode was not correct.
I fixed it and confirmed that my local was able to get it.
here are
try {
  final _googleSignIn = GoogleSignIn(
    scopes: [
      'email',
      'https://www.googleapis.com/auth/contacts.readonly',
    ],
  );
  final googleSignInAccount = await _googleSignIn.signIn();
  final googleSignInAuthentication = await googleSignInAccount.authentication;
  final code = googleSignInAuthentication.serverAuthCode;
  print(code);
} catch (error) {
  print(error);
}

Related Issues

https://github.com/flutter/flutter/issues/57741
https://github.com/flutter/flutter/issues/57712
https://github.com/flutter/plugins/pull/2634
https://github.com/flutter/plugins/pull/2116

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@yamarkz Hey I am pulling from your branch but the app crashes immediatly when google sign in resolves, any idea?
	0   CoreFoundation                      0x00007fff23e3cf0e __exceptionPreprocess + 350 	1   libobjc.A.dylib                     0x00007fff50ba89b2 objc_exception_throw + 48 	2   CoreFoundation                      0x00007fff23ecfa51 _CFThrowFormattedException + 194 	3   CoreFoundation                      0x00007fff23eda4a6 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:].cold.4 + 38 	4   CoreFoundation                      0x00007fff23e9b787 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 247 	5   CoreFoundation                      0x00007fff23e38e11 +[NSDictionary dictionaryWithObjects:forKeys:count:] + 49 	6   Runner                              0x00000001099fe6e4 __49-[FLTGoogleSignInPlugin handleMethodCall:result:]_block_invoke + 452

@scaraux
Thank you for comment.
Do you have the SERVER_CLIENT_ID set to GoogleService-Info.plist ?
I'm able to get serverAuthCode in my environment.

@scaraux
Thank you for comment.
Do you have the SERVER_CLIENT_ID set to GoogleService-Info.plist ?
I'm able to get serverAuthCode in my environment.

If you are talking about passing clientId in the constructor, yes I did

I need this fix to get the serverAuthCode such that I can get a refresh token at the backend side to use google API.
Why when we can expect this to be merged?

I need this fix to get the serverAuthCode such that I can get a refresh token at the backend side to use google API.
By when we can expect this to be merged?

In the meantime you can always do this:
pubspec.yaml
  google_sign_in:
    git:
      url: git@github.com:yamarkz/plugins.git
      path: packages/google_sign_in/google_sign_in
      ref: fix-server-auth-code-get-token

Don't forget to replace it when it's merged

@scaraux I'm trying to reference your project to test it, cause I also need this token in my project, but everytime after login when i try to access anything from the GoogleSignInAccount returned object, I get a crash in my app.
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff23e3cf0e __exceptionPreprocess + 350
	1   libobjc.A.dylib                     0x00007fff50ba89b2 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff23ecfa51 _CFThrowFormattedException + 194
	3   CoreFoundation                      0x00007fff23eda4a6 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:].cold.4 + 38
	4   CoreFoundation                      0x00007fff23e9b787 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 247
	5   CoreFoundation                      0x00007fff23e38e11 +[NSDictionary dictionaryWithObjects:forKeys:count:] + 49
	6   Runner                              0x0000000100e7df94 __49-[FLTGoogleSignInPlugin handleMethodCall:result:]_block_invoke + 452
	7   Runner  <…>
Lost connection to device.

@JonasABR Add server_client_id to your plist or else it keeps crashing

@scaraux
Thank you for comment.
Do you have the SERVER_CLIENT_ID set to GoogleService-Info.plist ?
I'm able to get serverAuthCode in my environment.

I don't have this key in the .plist downloaded from Firebase. There are three Client IDs:

CLIENT_ID
REVERSED_CLIENT_ID
ANDROID_ID

Below are all the keys in the .plist

Can you please guide me.

This been open for a long time and still no conclusion? I particulary really need this feature working in iOS & Android. The android branch is also open for a long time. Wanted to avoid having it locally.

This been open for a long time and still no conclusion? I particulary really need this feature working in iOS & Android. The android branch is also open for a long time. Wanted to avoid having it locally.

Same things here. This is bad. Triage has not been updated in over a month
https://github.com/flutter/plugins/projects/3#card-43160874
I understand this is open source and people have other priorities, let us know if we can do anything.

Guys, we really need this merged. Please...

@stuartmorgan is there anything you can do to get this merged? Been open for NINE months now...

We apologize for the long delay in triaging this PR. We’re in the process of overhauling our PR triage system to respond much more quickly, as well as working through the backlog.
We’re currently working through a large backlog of PRs, and this will require non-trivial review, so it will take some time before we’re able to review it. As explained in CONTRIBUTING.md, votes for the corresponding issue are the primary way we’re prioritizing non-trivial reviews, so we encourage anyone interested in this PR to vote for the corresponding issue.
Note that based on the discussion above it appears that this PR is not correct as-is (not correctly handling nil values in the ObjC code), and it's also missing tests, so wouldn't be mergeable as-is. Addressing the known issues and adding tests would be important steps toward making this reviewable and landable.

I'm sorry that this PR will not be merged.
I have no desire to merge and use this PR, so I will close it.
If you want to use it as a public package, please create a similar PR. Thanks.
@scaraux @stuartmorgan


Test failures from distro package (Gentoo)

This is some test results from Gentoo dev-util/hip-5.6.0 package on several GPUs. There are some test failures:
Radeon RX 6700XT has most failures:
Driver is Linux 6.4 upstream kernel
          6 - directed_tests/Functional/host/hipFloat161.22.3.tst (Subprocess aborted)
        108 - directed_tests/kernel/hipShflTests.tst (Subprocess aborted)
        109 - directed_tests/kernel/hipShflUpDownTest.tst (Subprocess aborted)
        121 - directed_tests/printf/hipPrintfManyWaves.tst (Bus error)
        185 - directed_tests/runtimeApi/memory/hipHostRegister.tst (Subprocess aborted)
        186 - directed_tests/runtimeApi/memory/hipIpcMemAccessTest.tst (Subprocess aborted)
        469 - Unit_hmax_hmin_Tsts (Failed)
        470 - Unit_hmax_hmin_Tsts_Negative (Failed)
        933 - Unit_hipHostRegister_Memcpy - int (Failed)
        934 - Unit_hipHostRegister_Memcpy - float (Failed)
        935 - Unit_hipHostRegister_Memcpy - double (Failed)
        1424 - Unit_HMM_OverSubscriptionTst (Failed)
        1664 - Unit_hipIpcOpenMemHandle_Negative_Open_In_Two_Contexts_Same_Device (Failed)
        1666 - Unit_hipIpcGetMemHandle_Positive_Unique_Handles_Reused_Memory (Failed)
        1669 - Unit_hipIpcCloseMemHandle_Positive_Reference_Counting (Failed)
        1771 - Unit_hipWaitExternalSemaphoresAsync_Vulkan_Positive_Binary_Semaphore (Subprocess aborted)
        1772 - Unit_hipWaitExternalSemaphoresAsync_Vulkan_Positive_Multiple_Semaphores (Subprocess aborted)
        1773 - Unit_hipWaitExternalSemaphoresAsync_Vulkan_Negative_Parameters (Subprocess aborted)
        1774 - Unit_hipSignalExternalSemaphoresAsync_Vulkan_Positive_Binary_Semaphore (Subprocess aborted)
        1775 - Unit_hipSignalExternalSemaphoresAsync_Vulkan_Positive_Multiple_Semaphores (Subprocess aborted)
        1776 - Unit_hipSignalExternalSemaphoresAsync_Vulkan_Negative_Parameters (Subprocess aborted)
        1777 - Unit_hipImportExternalSemaphore_Vulkan_Negative_Parameters (Subprocess aborted)
        1778 - Unit_hipDestroyExternalSemaphore_Vulkan_Negative_Parameters (Subprocess aborted)
        1793 - Unit_hipMemPrefetchAsyncOneToAll (Failed)
        1795 - Stress_printf_ComplexKernelMultStream (Subprocess aborted)
        1797 - Stress_printf_ConstStr (Bus error)
        1798 - Stress_printf_IfElseConditionalStr (Bus error)
        1799 - Stress_printf_IfConditionalStr (Bus error)
        1800 - Stress_printf_VariableStr (Bus error)
        1801 - Stress_printf_DependentCalc (Bus error)
        1802 - Stress_printf_DecimalStr (Bus error)
        1803 - Stress_printf_SharedMem (Bus error)
        1805 - Stress_printf_AtomicCalc (Bus error)
        1811 - Stress_deviceAllocation_malloc_loop_singlekernel (Bus error)
        1831 - Unit_hipIpcMemAccess_Semaphores (Timeout)
        1832 - Unit_hipIpcMemAccess_ParameterValidation (Failed)

Followed by Radeon VII and MI210, which is listed as officially supported GPU:
Radeon VII, Driver is Linux 6.3 upstream kernel:
        6 - directed_tests/Functional/host/hipFloat161.22.3.tst (Subprocess aborted)
        108 - directed_tests/kernel/hipShflTests.tst (Subprocess aborted)
        109 - directed_tests/kernel/hipShflUpDownTest.tst (Subprocess aborted)
        186 - directed_tests/runtimeApi/memory/hipIpcMemAccessTest.tst (Subprocess aborted)
        469 - Unit_hmax_hmin_Tsts (Failed)
        470 - Unit_hmax_hmin_Tsts_Negative (Failed)
        1664 - Unit_hipIpcOpenMemHandle_Negative_Open_In_Two_Contexts_Same_Device (Failed)
        1666 - Unit_hipIpcGetMemHandle_Positive_Unique_Handles_Reused_Memory (Failed)
        1669 - Unit_hipIpcCloseMemHandle_Positive_Reference_Counting (Failed)
        1781 - Unit_hipMemPrefetchAsyncOneToAll (Failed)
        1819 - Unit_hipIpcMemAccess_Semaphores (Timeout)
        1820 - Unit_hipIpcMemAccess_ParameterValidation (Failed)

MI210
Driver is amdgpu-dkms version rocm-5.6.0, installed on Linux 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1.
          6 - directed_tests/Functional/host/hipFloat161.22.3.tst (Subprocess aborted)
        108 - directed_tests/kernel/hipShflTests.tst (Subprocess aborted)
        109 - directed_tests/kernel/hipShflUpDownTest.tst (Subprocess aborted)
        201 - directed_tests/runtimeApi/memory/hipMemcpy-size.tst (Subprocess aborted)
        469 - Unit_hmax_hmin_Tsts (Failed)
        470 - Unit_hmax_hmin_Tsts_Negative (Failed)
        1644 - Unit_hipDeviceSetCacheConfig_Positive_Basic (Failed)
        1645 - Unit_hipDeviceSetCacheConfig_Negative_Parameters (Failed)
        1693 - Unit_hipDeviceSetSharedMemConfig_Positive_Basic (Failed)
        1769 - Unit_hipShflTests (Failed)
        1770 - Unit_runTestShfl_up (Failed)
        1771 - Unit_runTestShfl_Down (Failed)
        1772 - Unit_runTestShfl_Xor (Failed)
        1840 - Unit_malloc_CoherentTst (Failed)
        1841 - Unit_malloc_CoherentTstWthAdvise (Failed)
        1842 - Unit_mmap_CoherentTst (Failed)
        1843 - Unit_mmap_CoherentTstWthAdvise (Failed)

Both are using upstream llvm/clang 16.0.6 and ROCm-5.6.0 user-space packages delivered by Gentoo.
There are some common failures across GPUs. For examples:

hipFloat161.22.3.tst all failed with the same error diff=0.641602.
hipShflTests.tst and hipShflUpDownTest.tst all failed, and it passed in older version of ROCm/HIP
Upstream kernel will omit invalid device pointer in hipIpcMemAccessTest.tst. Unit_hipIpcOpenMemHandle_Negative_Open_In_Two_Contexts_Same_Device Unit_hipIpcGetMemHandle_Positive_Unique_Handles_Reused_Memory Unit_hipIpcCloseMemHandle_Positive_Reference_Counting also emits error, probably related to memory management.
Unit_hmax_hmin_Tsts and Unit_hmax_hmin_Tsts_Negative all failed -- maybe it's related with half precision not fully supported by upstream llvm/clang (such as https://github.com/ROCm-Developer-Tools/HIP/issues/3178)
Radeon RX 6700XT fails many Stress test, probably due to non-ECC memory
The Radeon RX 6700XT installed vulkan sdk, so some vulkan related error comes out
There are many other failures in common or specific to device/kernel driver ...... Please analyze them, and consider fixing them.

Here are the gzip compressed logs: build.log for compilation and testing, and test.log for details of tests. For upstream kernel, there are also lots of amdgpu driver issues during the test, logged in dmesg.log.
6700XT_linux-6.4_build.log.gz
6700XT_linux-6.4_test.log.gz
6700XT_linux-6.4_dmesg.log.gz
MI210_amdgpu-dkms-5.6_build.log.gz
MI210_amdgpu-dkms-5.6_test.log.gz
RadeonVII_linux-6.3_build.log.gz
RadeonVII_linux-6.3_test.log.gz
RadeonVII_linux-6.3_dmesg.log.gz

CCing Debian and Fedora hip maintainers who may be interested in these test results.
@cgmb @emollier @Maxzor @Mystro256

Kernel 6.0+ is not supported yet.
Please refer to https://rocm.docs.amd.com/en/latest/release/gpu_os_support.html#supported-distributions

Kernel 6.0+ is not supported yet.
Please refer to https://rocm.docs.amd.com/en/latest/release/gpu_os_support.html#supported-distributions

I do not think that support matrix is relevent. The kernel listed there are just validated to work on; upstream kernels are known to work for ROCm.
And the value of this issue is indeed test HIP on upstream kernels to see potential bugs

The kernel support matrix contains the list of kernels which are actively being tested/worked on. That list helps differentiate between known to work vs something we actively support, test and fix.
Regarding:

And the value of this issue is indeed test HIP on upstream kernels to see potential bugs

I can put this to the team to see what can be done regarding testing for LTS-only kernels. Get their thoughts on it.

I see. I will try to switch to a supported kernel and run these tests.
I think there are two main sources of test failures: not using well-supported kernel and using upstream LLVM instead of ROCm forked LLVM

Now it seems that HIT tests are deprecated. The catch tests all passed except those related to vulkan, and one stress test failure observed on Radeon VII

Hey @littlewu2508
I think we sorted the printf test out.
Can we close this?

I think we sorted the printf test out.

Thanks for noticing! May I ask which commit the printf test is sorted out? I will try testing again.

The comment of ROCm/clr#41 said that you had low disk space issue which was causing the failure

Ah, thank you for the reminder. Sorry I forgot this!


This will be a pull request on feature branch 1.

This is my pull request 1.

Merged and deleted feature branch.


Convert all functional tests into bona fida tests

I noticed that in the pay-related branches (adc, dac, etc) there's a functional test directory func_tests/ containing functional tests. I think these should all be moved into the tests directory, under a common theme. E.g. adc functional tests should all be kept in a adc/ subdirectory of tests/.

@brunofalmeida thoughts? This would help us track testing more effectively, and enable you to test multiboard functionality using the harness.

Wherever possible we should use the test harness, but there are many cases (especially in PAY and EPS) where it's impossible to use assertions to verify that something works. Examples include motor control, battery charging, and heater control where we need to verify things work using hardware tools and observation.
I suggest we keep separate folders for tests using the test harness and tests that must be run individually. @siddMahen

Maybe the naming scheme isn't obvious, but that was the logic for separating the folders

Ahh I see, that makes sense. Thanks for the clarification.

I'm thinking of PROMPT as an opportunity for the testing framework to wait for some external input

@siddMahen I think for some cases that would work, but there are many cases where we want to run a test for an indefinite amount of time and it's not a one-time program run (usually to see values changing over some time). Examples I can think of include heater temperature control in PAY and voltage/current measurements in EPS.

I see, ok. In that case, independent functional testing makes sense. I'll close this issue.

@siddMahen does the naming scheme tests for harness-based tests and func_tests for individual functional tests make sense, or do you recommend naming the folders differently?

I don't have much preference; I'd be ok with any naming scheme. The harness program accepts any directory so it'll require relatively little modification if we change tests to something else.


MIPS: Some pkg/ tests are very slow

Some tests in pkg/ are very slow on MIPS hardware. They pass fine on the simulator.

This is contingent on getting the MIPS bot back up and running, and we should anyway consider not running these tests there.


chore(ci): use ec2 for build-and-test-differential

Description
How it works
There are 5 consequent jobs:

prevent-no-label-execution
start-runner
build-and-test-differential
clang-tidy-differential
stop-runner

The way it works is,
1. prevent-no-label-execution
This job checks if PR has prevent-no-label-execution tag. If yes, it can continue. If not, workflow stops.
2. start-runner

This job spawns a machine in EC2.

The machine has github-actions-runner in it.

This job then registers this runner to the autowarefoundation/autoware.universe/runners using my personal Github token (which is a secret).

This runner is assigned a special label.

Example runner labels: self-hosted, Linux, X64, o837y  (last one being unique)

This action takes about 1m40s to complete. This delay comes mostly from EC2 instantiating the machine.

I've set the machine to be a c6a.xlarge instance which is a good match for running generic build and test jobs. The machine has 4 vCPU, 8 GiB Memory, 50GB SSD storage. (Powered by 3rd generation AMD EPYC processors)

We can reduce it to a less powerful machine based on testing the performance and the cost.

3. build-and-test-differential

This is 1st the 2 actual jobs we are attempting to run.
It runs specifically on the runners with the unique label that was assigned in the previous job.

Example label: o837y

4. clang-tidy-differential

This is 2nd the 2 actual jobs we are attempting to run.
This is dependent on the success of the previous job (build-and-test-differential)
It runs specifically on the runners with the unique label that was assigned in the previous job.

Example label: o837y

5. stop-runner

Regardless of the success or failure of the previous jobs, this job terminates the instance that was created in the first run.
The runner is also removed from autowarefoundation/autoware.universe/runners using the unique label that had been assigned.

Summary

With this PR merged, there will be as many runners as we have these jobs.

People won't have to wait for a over-burdened runner to pick up their job.

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[X] I've confirmed the contribution guidelines.
[X] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

I've added a detailed description to the first post.

I will probably remove this workflow from the sync-files job until we decide to increase its scope.
https://github.com/autowarefoundation/autoware.universe/blob/main/.github/sync-files.yaml#L46-L58
Related PR: https://github.com/autowarefoundation/autoware.universe/pull/4372#issuecomment-1651924652

Fixed spell check failure in https://github.com/tier4/autoware-spell-check-dict/pull/593.

https://github.com/autowarefoundation/autoware.universe/actions/runs/5716984310/job/15489764848?pr=4458
:( It cannot see the secret, now investigating it.

https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks#about-workflow-runs-from-public-forks

Workflows from forks do not have access to sensitive data such as secrets.

https://docs.github.com/en/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow

With the exception of GITHUB_TOKEN, secrets are not passed to the runner when a workflow is triggered from a forked repository.

I think this whole plan won't work. I will revert this change and add the machine for perpetual running.

@xmfcx How about using GitHub hosted larger runner? Is it out of budget?

@shmpwk In order to use larger GitHub hosted runners, we have to register the organization as either GitHub Team plan or GitHub Enterprise plan as explained here. However, if we upgrade AutowareFoundation's plan, then we have to pay at least $3.67 per user/month. We currently have 173 members added to the organization so that would be extra cost of about $7,600 per year.

@shmpwk in addition to Github Team pricing, c6a.xlarge instance costs $0.153 per hour.
For a month,
$0.153 per hour * 24 hours/day * 30 days/month = $0.153 * 24 * 30 = $110.16
it costs this much.
If the budget was $960 per month, I would prefer having 8 of these self hosted machines.


Multiple executor example to run tasks at different priority levels on RP2040.

I have two different things need to manage, time critical motor/sensor control and networking. One fellow suggest using an InterruptExecutor for higher prio tasks with embassy.
I only found a example for nrf52840, here
Need example for rp2040

@fakusb Thanks for your PR.
I have a question that what if the high priority task is a hardware interrupt, not SWI, let's say I2C1 interrupt?
Can I modify just SWI_IRQ_1 to I2C1_IRQ to let i2c2 interrupt everything else?

You can use any interrupt that's unused. If you are really using I2C1, then the I2C driver is using I2C1_IRQ, you can't use it for an executor at the same time.

You can use any interrupt that's unused. If you are really using I2C1, then the I2C driver is using I2C1_IRQ, you can't use it for an executor at the same time.

Then how to set different priority for different periphal? Let's say I don't want WiFi (spi or pio) interrupt motor driver (pwm)?

you control the priorities of tasks, not peripherals. If you spawn a task in a high-priority executor, everything that task does (including the peripheralsit manages) are high priority.


hm9000_analyzer occasionally causes "monit status" to break

Occasionally, "monit status" on an hm9000 instance will return a failed status instead of detailed process status. This is resolved by restarting the hm9000_analyzer process. I assume this process is occasionally returning something that monit can't handle.
This problem cascades into bosh where "bosh vms DEPLOYMENT" will return an error related to monit. Once hm9000_analyzer is restarted on the offending instance, "bosh vms DEPLOYMENT" will return the list of vms as it should.

This isn't an hm9000 issue but a BOSH issue. There is no interaction between processes and BOSH other than exiting.
You would need to provide more detailed logs to understand what the offending issue is.  Please reopen when you have more detailed information.

This seems to be due to an interaction between hm9000_analyzer and monit. Somehow, when monit tries to retrieve status from this process, it is failing in a way that causes monit to break. hm9000_analyzer is still running in this case. I would disagree that it is a bosh issue in general.
Maybe bosh has another bug in how it handles monit failures, but that's not what I'm referring to here.

There is nothing special here. This process is no different than any other Go process. Unless you show monit logs, I don't know how to help you.
The fact that the process is running would point to a monit issue. Monit is provided and managed by BOSH which is why I am deferring to them.


Stata 14 option limits

@jorpppp pasting the below from our earlier notes. If this is already addressed feel free to close, thanks!

Apparently Stata 14 only allows for 70 options on a command, while the limit is higher in Stata 15 and afterwards. In -xteventplot- we interlace commands with comments, and Stata's parser thinks the comments are options for some reason. So the latest version of -xteventplot- with many graph appearance options is not working on Stata 14 or below.

Summary: In this issue we fixed a bug with the options in `xteventplot' that prevented the command from running in Stata 14 or earlier.


Add docker volume for Caddy config.

Description
Allows reuse of LE generated certs and avoids hitting the LE rate limit when restarting web container.

#143
already add this change

This one came first and should still go in if you want to wait on #143. Think I was missing the volumes section in the other PR anyway so this would be good to put in first.


hasTVPreferredFocus not working on AndroidTV after initial render

Description
It works perfectly on tvOS, but on AndroidTV it looks like hasTVPreferredFocus works only on the initial render, and all subsequent times you would visit the screen or navigate back it is ignored.
I have created a new react-native-tvos project using the latest version (0.69.6-0) and set up a basic demo with some top-level screens & detail screens to reproduce this issue. I'm using @react-navigation/stack.
Would love to see this fixed and will help & assist wherever I can!
Version
0.69.6-0
Output of npx react-native info
System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M2
    Memory: 232.98 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.18.1/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /Users/wouterds/.rbenv/shims/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
    Android SDK:
      API Levels: 26, 28, 30, 31
      Build Tools: 28.0.3, 30.0.2, 30.0.3, 31.0.0
      System Images: android-31 | Google TV ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8609683
    Xcode: 14.1/14B47b - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.17 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.0.0 => 18.0.0
    react-native: Not Found
    react-native-macos: Not Found
    react-native-tvos:  0.69.6-0
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce

Run the example project
Go to a random item from any swimlane
Navigate back

On tvOS the item you navigated back from will be focused using hasTVPreferredFocus, on AndroidTV nothing will be focused and the user will be looking for his cursor that seemingly disappeared. Edit: I'm not sure but maybe it's related to the text nodes getting focus (https://github.com/react-native-tvos/react-native-tvos/issues/389). This also might be related https://github.com/react-native-tvos/react-native-tvos/issues/380.
Snack, code example, screenshot, or link to a repository
Example repository where the issue can be reproduced: @wouterds/react-native-tv-example
https://user-images.githubusercontent.com/1210628/202938737-301e7190-b029-4975-8103-fc90ca25438b.mp4
https://user-images.githubusercontent.com/1210628/203295163-ebbba8ac-1080-412a-8151-dd89d9bea0eb.mp4

Or if there is anything wrong with this setup and I'm missing something I'd gladly hear as well. We have this problem in our production project and in this example project that illustrates the issue.

I have found a *workaround* for AndroidTV (https://github.com/wouterds/react-native-tv-example/pull/1/commits/852b889db67d966670a89104f7873a066d5359f0) that works in my demo project (it's on the feature/experimental-focus branch if you want to try it out).
https://user-images.githubusercontent.com/1210628/203538986-0040b3f5-b9e2-4bf0-9213-79f485e6cc39.mp4
If you force focus through native props with 1ms delay it works, basically something along those lines
setTimeout(() => ref.current.setNativeProps({ hasTVPreferredFocus: true }), 1)

Don't think that needs a lot of explanation that this is just a dirty workaround a not a fix, we should get to the bottom of this.

This is a great find and indicates that the problem is in the Android preferred focus native implementation. Probably the native code is not getting notified when the JS property changes.

This bug also breaks all the nextFocusX properties on AndroidTV.

I think I experienced this as well. Will take a look and fix it if I can reproduce

Realized that I misread the issue. This is not the thing I thought I experienced but still, an important problem. This issue has no connection with hasTVPreferredFocus  IMHO, If I'm not missing something. hasTVPreferredFocus should be called once and only once unless its value change, by design. It's there to determine if the element should gain focus when it appears on the screen for the first time. I think you're expecting too much from that prop. It's certainly possible to use that prop to build a "hacky" solution but it'd be far from ideal.
Anyway, I think managing this is up to you or the system. There's this restoresFocusAfterTransition which tracks when items become hidden/visible and restores the focus. I'm no tvOS expert but I think this does the trick on tvOS and restores the focus. Couldn't find anything similar on Android for this and not sure if Android supports this natively.
I'll create a completely native example (without RN) to see how it works on Android and confirm if it's rather an Android or RN tvOS ( or even, a navigation library ) issue. Then I'll see what we can do to build our own custom solution if it's necessary

It definitely is a problem that didn't exist <= 0.66. The problem is that only the first time the screen mounts it works. But after that no more (by default react-navigation doesn't unmount screens once they rendered).
* only on Android TV

If this was working as you said before 0.66, I'd say that was the broken behavior 😄 Correct me if I'm wrong @douglowder but as I stated before, hasTVPreferredFocus should only be called on the first render and if its value change (like, true -> false or false -> true). So, I think there's no problem with hasTVPreferredFocus in particular with this case, it works fine.
This is a react-navigation (actually, react-native-screens) problem and it should be fixed as @douglowder described here. I've been trying to avoid exactly doing this but Android's focus system is incredibly unreliable, so we have to do this.
I'm working on creating a patch for react-navigation to fix this problem and here's the PoC:
https://user-images.githubusercontent.com/22980987/210457276-e1324d90-a1c2-463b-9187-ba5560503c96.mov
This is maybe like ~10 lines of fix and It is working but I haven't tested it in nested stack scenarios etc. I'll keep working.
I think we should close this issue and continue the discussion under #380


My Actions keep reloading the page

Dont know what i have done  but since i have been trying to working this out but in vain.
i have followed everything done in the example

@thomasdola I can't possibly be of any help if you do not really give more specific information.

You're using which tool? NPM/Bower/Direct include?
Is it keep reloading the page from the start or when you do something?
What are you trying to achieve? Just trying out the component or already put it in your project?

Thank you
it was a bug in my code...
it is working like a charm now...
this library is awesome ...


cancelEdit not working

Hi, I want to be able to cancel my update if the server is not accepting it.
this is part of my code in the controller:
updateItem: function (item) {
$.ajax({
type: "post",
url: '/Mutations/mutations?handler=Update',
contentType: "application/json; charset=utf-8",
dataType: "json",
beforeSend: function (xhr) { xhr.setRequestHeader("X-XSRF-TOKEN", $('input:hidden[name="__RequestVerificationToken"]').val()); },
data: JSON.stringify({ MutId: item.mutId, Status: item.status })
}).done(function (message) {
alert(message);
if (message !== 'Mutation status changed!') {
$('#jsgrid').jsGrid('cancelEdit');
}
});
},
The cancelEdit function gets called but the value in the grid is not reversed to its original value.
what is wrong?

hi , i think that
$('#jsgrid').jsGrid('cancelEdit');
is not what you think it is , this method cancels the editing view when you click edit on a row and reverse it to normal view ie. from input to text view.
currently i think there is no way to do what you want to do , you can do this  for inserting and deleting by overriding loadStrategy finishInsert() and finishDelete(),  check this:http://js-grid.com/docs/#custom-loadstrategy
for example return null from insertItem in controller and in finishInsert() check if deletedItem is null if true then dont delete the data

Hi @Ex0-Ghost I think you are right. it's already an very old issue and I don't know how I did resolve it. I believe I made an other server call to update the row.


No Tags/Releases created for node-red-node-swagger releases

Nick, can we get Tags and Releases created in github when we cut releases for node-red-node-swagger?  Thanks.

Yes of course.
On Mon, 10 Aug 2015 15:30 Donald Woods<EMAIL_ADDRESS>wrote:

Nick, can we get Tags and Releases created in github when we cut releases
for node-red-node-swagger? Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/node-red/node-red-node-swagger/issues/21.

(Am out and about with limited connectivity until Wednesday)
Having merged @lostinthestory's PR, there is the outstanding issue #20 i
assume a PR will be forthcoming for. There is also the question of how to
NLS the iframe content added in that pr. With those resolved we can then do
a new release for you to pick up (pending any other issues raised before
then)
On Mon, 10 Aug 2015 15:30 Nicholas O'Leary<EMAIL_ADDRESS>wrote:

Yes of course.
On Mon, 10 Aug 2015 15:30 Donald Woods<EMAIL_ADDRESS>wrote:

Nick, can we get Tags and Releases created in github when we cut releases
for node-red-node-swagger? Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/node-red/node-red-node-swagger/issues/21.

OK, end of this week is fine.  Didn't know if you could go back in after the fact and add the missing tags and release pointers in github for the already released versions.

Probably can, but will need more than the mobile ui to do it.
On Mon, 10 Aug 2015 16:31 Donald Woods<EMAIL_ADDRESS>wrote:

OK, end of this week is fine. Didn't know if you could go back in after
the fact and add the missing tags and release pointers in github for the
already released versions.
—
Reply to this email directly or view it on GitHub
https://github.com/node-red/node-red-node-swagger/issues/21#issuecomment-129497388
.

#24 should address all outstanding issues.

Done - https://github.com/node-red/node-red-node-swagger/releases/tag/0.1.1


C# syntax error hints disappear after a few seconds

VSCode Version: 1.6.1
OS Version: macOS 10.11.6 (15G1108

C# syntax error hint disappears after a few seconds.
Steps to Reproduce:

make a C# file
install C# plugin (1.4.1)
write a simple C# class
intentionally cause a syntax error.
observe red hints on the syntax error.
wait a couple of seconds, error hints disappear.

I expect this to be a VSCode issue instead of OmniSharp, since the syntax hints did show up correctly, only to disappear in a couple of seconds.

@zeyangl I'll say let's start with OmniSharp as we don't know yet whether OmniSharp regards it as no longer an error after a couple of seconds.

It appears to be fixed in 1.7.1 release. OmniSharp version remains the same though, so probably a nice side effect of some other fix in vscode.

I am still having same issue on Ubuntu 14.04,  insiders and stable Version 1.7.1.
Maybe is because of big projects, the problem doesn't occur when testing a small project.
Initially i was suspecting the auto save feature to have something to do about it, but i tested with all possible options.
Warnings and info remain, but errors disappear about 1.5 seconds after file change (saved or not).

This issue was moved to OmniSharp/omnisharp-vscode#883

I get this same issue on mac, using with unity


Swap continues despite LND <-> peerswapd disconnect

When attempting to disrupt the connection between peerswapd and LND with tcpkill, a swap is still able to complete somehow.
tcpkill seems to be repeatedly killing reconnection attempts. This occurs continuously and is pretty CPU intensive:
When running $ sudo tcpkill -i any -9 port 10009:
<snippet>
<IP_ADDRESS>:10009 > <IP_ADDRESS>:60948: R<PHONE_NUMBER>:4092094968(0) win 0
<IP_ADDRESS>:60948 > <IP_ADDRESS>:10009: R 585885286:585885286(0) win 0
<IP_ADDRESS>:60948 > <IP_ADDRESS>:10009: R 585885791:585885791(0) win 0
<IP_ADDRESS>:60948 > <IP_ADDRESS>:10009: R 585886801:585886801(0) win 0
<IP_ADDRESS>:60948 > <IP_ADDRESS>:10009: R 585888316:585888316(0) win 0
</snippet>

~/.peerswap/log
2022/08/31 19:25:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 122, backoff for 30s
2022/08/31 19:25:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 74, backoff for 30s
2022/08/31 19:25:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 1, backoff for 30s
2022/08/31 19:25:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 74, backoff for 30s
2022/08/31 19:25:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 74, backoff for 30s
2022/08/31 19:25:30 [DEBUG] [grpc_conn]: grpc_retry attempt: 0, got err: rpc error: code = Unavailable desc = error reading from server: read tcp 127
.0.0.1:55296-><IP_ADDRESS>:10009: read: connection reset by peer
2022/08/31 19:25:30 [DEBUG] [grpc_conn]: grpc_retry attempt: 1, backoff for 30s
2022/08/31 19:25:43 [DEBUG] [PaymentWatcher] Swap: f4e37b4d1fb0cbb62b4b40212639001860e446e4b0fce17ada0acdb4434c7d58: Calling paymentCallback
2022/08/31 19:25:43 [DEBUG] [FSM] event:id: f4e37b4d1fb0cbb62b4b40212639001860e446e4b0fce17ada0acdb4434c7d58, Event_OnClaimInvoicePaid on State_SwapI
nSender_AwaitClaimPayment
2022/08/31 19:25:43 [INFO] [Swap:f4e37b4d1fb0cbb62b4b40212639001860e446e4b0fce17ada0acdb4434c7d58] Swap claimed with preimage 814fca92f7a86a52859495e
e9d8af6d8cc356f5e99f6e00a164b1dd25ccb4351
2022/08/31 19:25:43 [DEBUG] [grpc_conn]: grpc_retry attempt: 123, backoff for 30s
2022/08/31 19:25:43 [DEBUG] [grpc_conn]: grpc_retry attempt: 75, backoff for 30s
2022/08/31 19:25:43 [DEBUG] [grpc_conn]: grpc_retry attempt: 75, backoff for 30s
2022/08/31 19:25:43 [DEBUG] [grpc_conn]: grpc_retry attempt: 75, backoff for 30s
2022/08/31 19:26:00 [DEBUG] [RedundantSender]   stop sending messages of type 42077 to 0363b14124d0cd630087cba0cac7145d17ccef4a6de2770dff7a8b1cbaffd4
ed30
2022/08/31 19:26:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 76, backoff for 30s
2022/08/31 19:26:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 76, backoff for 30s
2022/08/31 19:26:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 124, backoff for 30s
2022/08/31 19:26:13 [DEBUG] [grpc_conn]: grpc_retry attempt: 76, backoff for 30s
2022/08/31 19:26:43 [DEBUG] [grpc_conn]: grpc_retry attempt: 77, backoff for 30s

To reproduce:
Initiate a swap. I do not believe it matters if it's a swap out or swap in. Once the swap is in the state: "state": "State_SwapOutSender_AwaitTxConfirmation",, fire up tcpkill with the arguments mentioned above. Then wait. Eventually the swap will complete.

Hey, maybe I am missing the point but what I read from the logs is: you kill the connection (constantly), grpc tries to fix the connection and in the end the necessary Information (preimage) is successfully received?

Yes sounds right. Is this intended behavior? I don't know if this should be an instance where the swap is canceled altogether maybe?

As far as I can tell from your logs this is indeed intended. I will close this for now. If there are any more questions or observed misbehavior, please file a ticket again!


jobs: Fix foodBuffTimer undefined

Fixes #4032
Also solve multiple setTimeout issue by adding 1s cooldown to func
(eat food have an animation lock for more than 1s)

Beyond my ability.
@MaikoTan


The removal of support for master password generation was maybe too hasty.

Is your request related to a problem? Please describe.
Not using master password, where support for management within Secrets Manager is available makes good sense, and should be the default. But the removal of the ability to generate a master password in some cases, seems not to take into account that the Secrets Manager integration is not available in all cases. For example, see Limitations for Secrets Manager integration with Amazon Aurora. One such example is:

DB clusters that are part of an Aurora global database

In those cases, we still need to provide a password. We can of course generate one in the block that implements the module, but it makes sense to still provide it here.
Describe the solution you'd like.
Provide the feature as it was before.
Describe alternatives you've considered.
As mentioned above, the alternative required currently is to generate the password outside the module, which is fine, but it would be a quality of life improvement as it was before to provide it in the module.
Another alternative is to rely on IAM authentication for the cluster, but I'm not entirely sure the implications of this in a global cluster (need to do some testing).

Provide the feature as it was before

You really should look for ways to avoid having the password in plaintext in your statefile. We do not have any plans to re-enable that functionality because its a really poor practice
That said, there is nothing from stopping you from using the random password resource yourself to generate a password and pass it into this module - we want to push users towards the recommended approach (for their own benefit)

Of course one should avoid that. I thought I made it clear I agree with the intent. The only issue is with the stated removal being:

With RDS now supporting the integration with SecretsManager to manage the master user password, the ability to generate a random password has been removed from this module

But RDS doesn't support that in all cases. In those cases, what is your recommendation? I cannot enable IAM authentication without setting a master password. So, without encrypted state support, I'm not clear on the recommended approach here.

If you don't want to go the managed password route, just supply a password as input to your module via master_password. You can even use the random resource like this module previously did if you'd like https://github.com/terraform-aws-modules/terraform-aws-rds-aurora/blob/bf4d92cbf0ff66987eec9dd0fcff66e9b2ae158b/main.tf#L26-L31
  # ...
  manage_master_user_password = false
  master_password = <something>
  # ...

I appreciate you taking the time. Just to clarify, that is precisely what I am doing. I mention that as the alternatives in the opening remarks. I guess my question is, if this is a poor practice, what is the alternative? I do want to go the managed password route; it just isn't supported.


Fix issue where Swift APIs didn't work correctly with type(of:)

Changes:

~Swift APIs that take an object type as a parameter can now properly handle receiving the type name of a Realm private subclass (e.g. a value returned from type(of:) called on an object instance)~ Fix regression.

Fixes #5414.

className is a method we define, and the main point of it is that it returns the name of the user-defined class rather than the names of the generated subclasses. If it's not doing that, that's the bug that needs to be fixed.

This is indeed a regression, caused by a change that I made for 3.0.0. At least we'll get some unit tests out of this PR.

It looks like the 8.3.3 tests are failing after this change. i'll download that version of Xcode tomorrow and investigate further.

Any idea when this will be included in the next release?

We'll cut another release some time this week (probably tomorrow).


fix(oxlint): properly report error

This fixes an incorrect error formatting in the lint runner logic.

Thanks for your contribution!


Warning when adding a new route

Describe the bug
If you add a route you see
Warning: You are calling ReactDOMClient.createRoot() on a container that has already been passed to createRoot() before. Instead, call root.render() on the existing root instead if you want to update it.

and then the page is reloaded
Expected-behavior
The route is added, there is no warning and the page is not reloaded
Reproduction
npm init vaadin
Choose Hilla views
mvn
cp src/main/frontend/views/about-hilla.tsx src/main/frontend/views/about2.tsx after the app is open
System Info
24.4.3

Related to #2552

This might have been solved in the latest version


More accurate datastore/ space monitoring

When monitoring a host's overall datastore/ disk space usage, look at
the filesystems for each datastore (which may be mounted) and sum the
total amounts of free/used/total space for all different mounts under
that directory. This should allow more accurate vm scheduling based on
overall disk space usage on a particular host.

INTERNAL NOTE: merge after new monitoring (#3859) branch is merged

Is there a reason this small improvement couldn't be merged prior to that ie next 5.10 point release?

Totally, didn't take a look at the patch itself....

This looks reasonable, however I suggest to keep the monitor script bash-only.
Can you take a look at https://github.com/xorel/one/commit/77080463cafbc0e845e1124ded701d05a3b80062 ?

This looks like a reasonable approach however stat $dir --printf=%m only prints the mount root or something like that of the filesystem which is different if I have several bind-mount points pointing at the same filesystem.
Replacing the stat commands with something like stat -f $dir --printf=%i works as expected.

Right, the %m doesn't work well for bind-mounts. The %i seems to work better, but for the sake of simplicity, I modified to read the source from df.  Can you check if https://github.com/xorel/one/commit/cbef7749945a911a71d4e103bf14a2b28da02904 works for you?

I made some further changes in monitor_ds, like avoiding multiple running of df or unify var casing.
If you don't mind I will close this PR and proceed with https://github.com/OpenNebula/one/pull/4243

Sounds good thanks!


Oberve LiveData with  Extension function

I used the extension function observe in LiveData to make adjustments to the code in the project, which seems to be more in line with the Kotlin syntax, like this:
From
viewModel.gardenPlantings.observe(viewLifecycleOwner, Observer { plantings ->
    binding.hasPlantings = !plantings.isNullOrEmpty()
})

To
viewModel.gardenPlantings.observe(viewLifecycleOwner) { plantings ->
    binding.hasPlantings = !plantings.isNullOrEmpty()
}

What is the meaning of LGTM?

LGTM stands for Looks Good To Me

thanks

Generally looks great! Can you clean up the minor things with spotless and then we can merge this?

@piotrek1543 You are right.
plants != null means plants is nullable, there is no need to add a comment, but Android Studio will think plants != null is not necessary, like this:

This is because the Room database is declared to be non-nullable, like this:
    @Query("SELECT * FROM plants ORDER BY name")
    fun getPlants(): LiveData<List<Plant>>

You can find his definition here. I think it should be defined as follows:
    @Query("SELECT * FROM plants ORDER BY name")
    fun getPlants(): LiveData<List<Plant>?>

Form LiveData<List<Plant>> To LiveData<List<Plant>?>, From notnull to nullable.
You can find the implementation class PlantDao_Impl.java generated by Room in the app/build/generated/source/kapt/debug/[package_name]/data/PlantDao_Impl.java directory.

Thank you @madroidmaq !
For the .observe extension function issue, can you file an issue at https://developer.android.com/jetpack/docs/feedback?


Invalid handling of auth errors in Things service

BUG REPORT

What were you trying to achieve?
I wanted to make sure the policies mechanism added on mainflux/0.13.0 didn't break anything on our project. So while checking the Things Api I could check some strange behavior when trying to fetch Things that doesn't exist or the User doesn't have access to them. My test was quite simple, I just created a random User and tried to fetch a Thing ID that doesn't exist.

What are the expected results?
404 Not Found same as mainflux/0.12.1

What are the received results?
500 Internal Server Error

What are the steps to reproduce the issue?

curl -s -X POST -H "Content-Type: application/json" http://localhost:8180/users -d '{"email":"hoge@mail.com","password":"12345678"}'
TOKEN=$(curl -s -X POST -H "Content-Type: application/json" http://localhost:8180/tokens -d '{"email":"hoge@mail.com","password":"12345678"}' | jq -r ".token")
curl -s -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $TOKEN" http://localhost:8182/things/123

In what environment did you encounter the issue?
mainflux/0.13.0

Additional information you deem important:
Same thing happens when I have a Thing but I don't have the read policies on Keto to access it. It also throws a 500 Internal Server Error instead of 403 Forbidden as the documentation states.

@fhaze Looks like the migration issue between 0.12.0 and 0.13.0 explained here: #1602

The migration issue is another subject IMHO. I did my tests on a fresh Mainflux/0.13.0 install (not an upgrade scenario).

In that case it's definitelly a bug. Can you delete the Thing? If not, you can probably use the fix from the issue. I remember to have a similar bug some days ago.

@fhaze This PR should fix your issue: https://github.com/mainflux/mainflux/pull/1615


split leading to SRDF failover when using modify_storagegroup_srdf

Hi ,
In recent times i started using and i am new to PyU4V  module , when i tried to send
split command using this line - conn.replication.modify_storagegroup_srdf('autodr_test_r1_SG','split','9')
but its making the SG to go failed over not the split .
can you help  and let me know what am i missing ?

Hi There,
Aside from the examples included in the repo you can also look at my colleagues article on replication with PyU4V here: https://community.emc.com/people/PaulCork/blog/2017/02/07/unisphere-for-vmax-rest-api-examples-episode-3-return-of-the-srdf
This may be of help with your use-case, if not ask a question on the community forums :)
Michael


Release latest changes to Maven Central

Hi,
could you please release latest version of the code to Maven Central. Currently Maven Central has v2.0.0 which is from 16. Nov 2016. This version is also missing the useSchema annotation, which I really need

Hi, would you be able to do this release so I can avoid forking this repo just to do it my self in our internal mvn repo?

This seems to be a good library for testing ldap. I am also looking forward for an update in maven :)

Version 2.0.1 has been released. Sorry for the delay. I don't do Java any more and haven't used this in a long time :)


[resotocore][fix] Load model more efficient.

Description
Load model is now 10K faster.
To-Dos

[x] Add test coverage for new or updated functionality
[x] Lint and test with tox

Codecov Report

Merging #641 (4f2dd71) into main (4d2657f) will increase coverage by 0.09%.
The diff coverage is 95.31%.

@@            Coverage Diff             @@
##             main     #641      +/-   ##
==========================================
+ Coverage   88.93%   89.02%   +0.09%
==========================================
  Files          64       64
  Lines        8531     8531
==========================================
+ Hits         7587     7595       +8
+ Misses        944      936       -8

Flag
Coverage Δ

resotocore
89.02% <95.31%> (+0.09%)
:arrow_up:

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

Impacted Files
Coverage Δ

resotocore/core/cli/command.py
85.85% <0.00%> (ø)

resotocore/core/task/task_description.py
89.80% <0.00%> (ø)

resotocore/core/model/model.py
92.62% <98.21%> (+0.48%)
:arrow_up:

resotocore/core/db/graphdb.py
93.08% <100.00%> (ø)

resotocore/core/task/task_handler.py
84.37% <100.00%> (ø)

resotocore/core/util.py
96.86% <100.00%> (ø)

resotocore/core/web/content_renderer.py
93.75% <0.00%> (+3.47%)
:arrow_up:

Continue to review full report at Codecov.

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


✨ QuickTrace: An Efficient Contour Tracing Algorithm for Defect Robustness Simulation

Description
This PR implements three key methods---Grid Search, Random Sampling, and QuickTrace (based on Contour Tracing)---to identify and analyze the atomic defect operational domain.
Checklist:

[x] The pull request only contains commits that are related to it.
[x] I have added appropriate tests and documentation.
[ ] I have added a changelog entry.
[ ] I have created/adjusted the Python bindings for any new or updated functionality.
[ ] I have made sure that all CI jobs on GitHub pass.
[ ] The pull request introduces no new warnings and follows the project's style guidelines.

Many thanks for the great additions! As this is quite a large PR, I have a few comments here and there. I hope they are helpful to you.

Thank you very much! I will have a look asap.


Graphviz update

Rewritten the schematic generation code to utilize a subgraph-based structure instead of the record-based structure. However, the graphviz orthogonal routing algorithm occasionally produces incorrect routing for certain ports.
Summary by Sourcery
Enhancements:

Refactor schematic generation to use a subgraph-based structure instead of a record-based structure for improved modularity and flexibility.

i fixed the merge conflicts with main
What are the advantages of this PR?
the old schematics look a bit better

the big disadvantage in graphviz as I understand it is that you cannot indicate directionality (and size of nodes). It's not a big issue if you have a relatively well defined schematic such as an mzi or splitter tree. But I am pretty sure this will look pretty weird on a whole chip or even just a general PIC. Wouldn't it be easier to just draw each component according to its bounding box and connect them on points?

@joamatab The advantage of the PR is that it addresses the ortho routing algorithm issue within Graphviz. Currently, the ortho routing algorithm in Graphviz lacks the capability to handle bounding box collisions (the previous PR). As a workaround, I have been introducing calculated gaps artificially. I will try to thicken the lines and see if it improves the visualisation.
@sebastian-goeldi, are you suggesting that we do not render ports and solely focus on drawing the components? And maybe there is some confusion, but I could change the size of nodes in graphviz

I see, for some reason the previous version looks still a bit better, is it possible to show only the port name,

i think instanceName_portName is too long
Ideally there is no gap between instance name and port


Vision & Requirement Updates

This pull request is going to hold the edits to the vision and requirement docs.
As it stands, I've included a third item (for falsifying causal graphs) to our deliverables for the project vision. If you see the doc, I've included my rationale for why we should have an explicit third deliverable. Let me know if any of you disagree with its inclusion!
Beyond this, let me know your thoughts / critiques / suggestions for the vision doc!
@hassanobeid1994, @bouzaghrane

@bouzaghrane let me know if the changes addressed your comments!

Alright, I think I'm done with a first revised draft of the requirements doc.
Can everyone take a look and leave a review with their:

comments on what looks incorrect
questions about what is required vs what has been completed
questions for clarification.

@bouzaghrane, @hassanobeid1994


Purview Catalog Client : delete_by_guid works but delete_by_guids doesn't !!

Package Name: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/purview/azure-purview-catalog
Package Version:
Operating System:
Python Version:  3.7

Describe the bug
A clear and concise description of what the bug is.
delete_by_guid works but delete_by_guids doesn't !!
To Reproduce
Steps to reproduce the behavior:
1.
When I use the following code -> It works :
credential = DefaultAzureCredential()
client = PurviewCatalogClient(endpoint="https://purviewaccount.purview.azure.com", credential=credential)
try:
response = client.entity.delete_by_guid("7436615c-efee-4f54-b09b-54f6f6f60000")
But when I use the following it doesn't work.
credential = DefaultAzureCredential()
client = PurviewCatalogClient(endpoint="https://purviewaccount.purview.azure.com", credential=credential)
try:
response = client.entity.delete_by_guids(["7436615c-efee-4f54-b09b-54f6f6f60000", "8aa0e7a0-6eda-47ae-8469-15f6f6f60000"])
print(response)
Expected behavior
A clear and concise description of what you expected to happen.
I need a way to delete multiple atlas entities at one go.
Please help.
Many customers are waiting for this.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

hello @abandyop, we have identified the fix and have a PR out to fix it. We generally do our releases on our 3 week sprint cadence, which means this fix will be released the first week of February. I want to check in with you and see if this date is ok with you. If you have any extenuating circumstances, please let us know!

Yeah ideally earlier the better, but I'll have to live with the release cycles ... NO problem will check back 2nd week Feb


Document process to load studies with mzXML files

FEATURE REQUEST
Inspiration

mzXML files are too large to place into a GitHub repository as we have done with previous study data. They are also cumbersome to move around and loading of study has become more complex.
Description

We need a documented process that multiple people understand and can follow to process and eventually load newly submitted studies that include mzXML files.
Alternatives

None
Dependencies
None
Comment

None

ISSUE OWNER SECTION
Assumptions

List of assumptions that the code will not explicitly address/check
E.g. We will assume input is correct (explaining why there is no validation)

Limitations

A list of things this work will specifically not do
E.g. This feature will only handle the most frequent use case X

Affected Components

change: File path or DB table ...
add: Environment variable or server setting
delete: External executable or cron job

Requirements

[ ] 1. List of numbered conditions to be met for the feature
[ ] 2. E.g. Every column/row must display a value, i.e. cannot be empty
[ ] 3. Numbers for reference & checkboxes for progress tracking

DESIGN
Interface Change description

None provided
Code Change Description

None provided
Tests

[ ] 1. A description of at least one test for each requirement above.
[ ] 2. E.g. Test for req 2 that there's an exception when display value is ''
[ ] 3. Numbers for reference & checkboxes for progress tracking

Adding documentation is fair, though I would say that it really hasn't changed that much.  In fact I would argue that the only additional complexity is "How do I supply the mzXML files?". And that's got a really straightforward answer: the --mzxml-files option or the mzxml_files yaml item.
And there is documentation in the form of the yaml schema and the commands' help output, which honestly, I think should largely suffice, so a perception of a lack of dcumentation shouldn't really hamper any progress.  I have mentioned on a few occasions that all the changes implemented require (with the exception of optionally supplying mzxml files) no different usage of any of the commands unless you get an error - and the errors pretty much tell you what you need to do.  Each commands' usage contains sufficient information to add context to the yaml settings which can inform a user how to supply the files.
Script by script, we have:

load_study_set - The CLI has not changed.
load_study - The CLI has not changed.
load_animals_and_samples - The CLI has a single new optional option, though it is unnecessary unless you get an error.  Setting the lcms_file in the yaml will automatically provide it to both the animal/sample script and the accucor script, and again, you will not need to provide that file in the most common cases (unless you get an error).

$ python manage.py load_animals_and_samples -h
...
  --lcms-file LCMS_FILE
                        Excel or tab-delimited file containing metadata associated with the liquid chromatography and mass spec instrument run, (e.g. DataRepo/data/tests/small_obob_lcms_metadata/glucose.xlsx). If an excel file is used, it will use the sheet named 'LCMS Metadata' or
                        the first sheet.

The CLI for the load_accucor_msruns has 6 new options that are fairly straightforward, but only the --mzxml-files option is necessary to add mzXML files.  Each option has a representation in the yaml schema.  The mzXML files will get automatically matched to the sample data headers in the accucor file.

$ python manage.py load_accucor_msruns -h
...
  --lcms-file LCMS_FILE
                        Filepath of either an xlsx or csv file containing metadata associated with the liquid chromatography and mass spec instrument run.
  --mzxml-files [MZXML_FILES ...]
                        Filepaths of mzXML files containing instrument run data.
  --lc-protocol-name LC_PROTOCOL_NAME
                        Default LCMethod.name of the liquid chromatography protocol used. Used if --lcms-file is not supplied, or specifies no LC info for a sample.
  --instrument INSTRUMENT
                        Default name of the LCMS instrument that analyzed the samples. Used if --lcms-file is not supplied, or specifies no instrument for a sample.
  --polarity POLARITY   Default ion mode of the LCMS instrument that analyzed the samples. Used if --lcms-file is not supplied, or specifies no polarity for a sample.
  --mz-min MZ_MIN       Default unsigned minimum charge of the MSRun scan range. Only required if a study contains multiple MSRuns with the same polarity. Automatically parsed from mzXML. If unavailable, the minimum medMz value from the accucor/isocorr file is acceptable.
  --mz-max MZ_MAX       Default unsigned maximum charge of the MSRun scan range. Only required if a study contains multiple MSRuns with the same polarity. Automatically parsed from mzXML. If unavailable, the maximum medMz value from the accucor/isocorr file is acceptable.

The other loaders simple had their input file option names changes to --infile.
Let me know what additional information I can provide.

Thanks for the info on the options. That will be helpful when putting together the documentation. To close this issue , we need to document a process for handling incoming submissions, staging the data, communicating with the researcher, and finally loading into production. Basically, updating our internal docs here: https://nplcadmindocs.princeton.edu/index.php/TraceBase#Processing_TraceBase_Study_Submissions

Putting some notes here:

Ideal to ask for sample sheet, a single accucor file, and all mzXML files in one directory.
Download files to staging area on tracebase-dev
Load sample sheet, fix errors, reload until success
Use dry-run to load accucor file and mzXML files (should not be copied during dry run), fix errors, repeat until all issues resolved
Compile YAML file with necessary options, test loading in dev (can this be done after it's already loaded?), mark as ready to load
Use YAML file to load into production from staging area, mark as loaded
Script to cleanup marked directories and notify about old ones (over 1 week?)

Update process ready for review/testing at https://nplcadmindocs.princeton.edu/index.php/TraceBase#Processing_TraceBase_Study_Submissions


Why does the trace output use stderr?

https://github.com/capistrano/capistrano/blob/45e851bdc5ed80970a7be90f080f030aa7386190/lib/capistrano/application.rb#L29
I was expecting trace output to be sent to stdout instead of stderr (since it is quite handy to see the hooks also on successful commands).

It's there because it's trace level output designed for debugging. Many posix tools behave the same way.

I found that the default rake behavior is to output to stdout: http://docs.seattlerb.org/rake/doc/command_line_usage_rdoc.html
But also, I can set it myself using --trace=stdout.

I've reopened the issue, maybe we should revaluate the default. It's a rare issue, but if we're deviating from Rake's behaviour, even if it's easy to fix, I'd be glad of "doing it right"

There seems to be some miscommunication here. The Rake docs specify that stderr is the default.

--trace{=output} (-t)
Turn on invoke/execute tracing. Also enable full backtrace on errors. The output parameter is optional, but if specified it controls where the trace output is sent. If output is stdout, then trace output is directed to standard output. If output is stderr, or if it is missing, then trace output is sent to standard error.

Capistrano is not deviating from this.

Good, I didn't think so. Blame the fact I've been on my feet 24h. Thanks
@mattbrictson
On 4 Jan 2016 10:57 p.m., "Matt Brictson"<EMAIL_ADDRESS>wrote:

There seems to be some miscommunication here. The Rake docs specify that
stderr is the default.
--trace{=output} (-t)
Turn on invoke/execute tracing. Also enable full backtrace on errors. The
output parameter is optional, but if specified it controls where the trace
output is sent. If output is stdout, then trace output is directed to
standard output. If output is stderr, or if it is missing, then trace
output is sent to standard error.
Capistrano is not deviating from this.
—
Reply to this email directly or view it on GitHub
https://github.com/capistrano/capistrano/issues/1550#issuecomment-168823934
.

I must have simply misread the docs, thanks for clarifying. :)