No access

Hello it's some time I got problems to be able to access ha's page. Seems hassio is not answering or something like that. Even with Alexa I'm not able to send commands to devices, she sais the device is not answering. I attach the log here, can anybody help me please?
`1028 23:15:52 [Error] :  Bad state: Future already completed
1028 23:15:52 [Error] :  #0      _Completer.completeError (dart:async/future_impl.dart:21)
#1      ConnectionManager._doConnect.. (package:hass_client/managers/connection_manager.class.dart:103)
#2      _rootRunUnary (dart:async/zone.dart:1132)
#3      _CustomZone.runUnary (dart:async/zone.dart:1029)
#4      _FutureListener.handleValue (dart:async/future_impl.dart:137)
#5      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678)
#6      Future._propagateToListeners (dart:async/future_impl.dart:707)
#7      Future._completeWithValue (dart:async/future_impl.dart:522)
#8      Future._asyncComplete. (dart:async/future_impl.dart:552)
#9      _rootRun (dart:async/zone.dart:1124)
#10     _CustomZone.run (dart:async/zone.dart:1021)
#11     _CustomZone.runGuarded (dart:async/zone.dart:923)
#12     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:963)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
1028 23:15:52 [Warning] :  Previous connection attempt pending...
1028 23:15:52 [Warning] :  Previous connection attempt pending...
1028 23:15:52 [Warning] :  Previous connection attempt pending...
1028 23:15:52 [Warning] :  Previous connection attempt pending...
1028 23:15:52 [Warning] :  Previous connection attempt pending...
1028 23:15:52 [Warning] :  Previous connection attempt pending...
1028 23:15:52 [Warning] :  Previous connection attempt pending...
1028 23:16:07 [Debug] :  [Sending] ==> {"type":"get_states","id":8}
1028 23:16:07 [Debug] :  [Sending] ==> {"type":"lovelace/config","id":9}
1028 23:16:07 [Debug] :  [Sending] ==> {"type":"get_config","id":10}
1028 23:16:07 [Debug] :  [Sending] ==> {"type":"get_services","id":11}
1028 23:16:07 [Debug] :  [Sending] ==> {"type":"auth/current_user","id":12}
1028 23:16:07 [Debug] :  [Sending] ==> {"type":"get_panels","id":13}
1028 23:16:07 [Debug] :  [Sending] ==> {"type":"subscribe_events","id":14,"event_type":"state_changed"}
1028 23:16:07 [Warning] :  Can't get services: Instance of 'HAError'
1028 23:16:07 [Warning] :  Can't get user info: Instance of 'HAError'
1028 23:16:07 [Debug] :  AppLifecycleState.inactive
1028 23:16:07 [Debug] :  AppLifecycleState.paused
1028 23:16:24 [Debug] :  AppLifecycleState.inactive
1028 23:16:24 [Debug] :  AppLifecycleState.resumed
1028 23:16:24 [Warning] :  Previous connection attempt pending...
1028 23:16:39 [Debug] :  Settings changed. Saving...
1028 23:16:39 [Debug] :  Settings change event: reconnect=true
1028 23:16:39 [Error] :  Loading settings...
1028 23:16:39 [Error] :  Long-lived token read successful
1028 23:16:39 [Warning] :  Previous connection attempt pending...
1028 23:16:39 [Error] :  Bad state: Future already completed
1028 23:16:39 [Error] :  #0      _Completer.completeError (dart:async/future_impl.dart:21)
#1      ConnectionManager._doConnect.. (package:hass_client/managers/connection_manager.class.dart:103)
#2      _rootRunUnary (dart:async/zone.dart:1132)
#3      _CustomZone.runUnary (dart:async/zone.dart:1029)
#4      _FutureListener.handleValue (dart:async/future_impl.dart:137)
#5      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678)
#6      Future._propagateToListeners (dart:async/future_impl.dart:707)
#7      Future._completeWithValue (dart:async/future_impl.dart:522)
#8      Future._asyncComplete. (dart:async/future_impl.dart:552)
#9      _rootRun (dart:async/zone.dart:1124)
#10     _CustomZone.run (dart:async/zone.dart:1021)
#11     _CustomZone.runGuarded (dart:async/zone.dart:923)
#12     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:963)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
1028 23:16:39 [Warning] :  Previous connection attempt pending...
1028 23:16:39 [Warning] :  Previous connection attempt pending...
1028 23:16:39 [Warning] :  Previous connection attempt pending...
1028 23:16:39 [Warning] :  Previous connection attempt pending...
1028 23:16:39 [Warning] :  Previous connection attempt pending...
1028 23:16:39 [Warning] :  Previous connection attempt pending...
1028 23:16:54 [Error] :  Bad state: Future already completed
1028 23:16:54 [Error] :  #0      _Completer.completeError (dart:async/future_impl.dart:21)
#1      ConnectionManager._doConnect.. (package:hass_client/managers/connection_manager.class.dart:103)
#2      _rootRunUnary (dart:async/zone.dart:1132)
#3      _CustomZone.runUnary (dart:async/zone.dart:1029)
#4      _FutureListener.handleValue (dart:async/future_impl.dart:137)
#5      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678)
#6      Future._propagateToListeners (dart:async/future_impl.dart:707)
#7      Future._completeWithValue (dart:async/future_impl.dart:522)
#8      Future._asyncComplete. (dart:async/future_impl.dart:552)
#9      _rootRun (dart:async/zone.dart:1124)
#10     _CustomZone.run (dart:async/zone.dart:1021)
#11     _CustomZone.runGuarded (dart:async/zone.dart:923)
#12     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:963)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
1028 23:16:54 [Warning] :  Previous data fetch is not completed yet
1028 23:16:54 [Debug] :  [Sending] ==> {"type":"get_states","id":15}
1028 23:16:54 [Debug] :  [Sending] ==> {"type":"get_config","id":16}
1028 23:16:54 [Debug] :  [Sending] ==> {"type":"get_services","id":17}
1028 23:16:54 [Debug] :  [Sending] ==> {"type":"auth/current_user","id":18}
1028 23:16:54 [Debug] :  [Sending] ==> {"type":"get_panels","id":19}
1028 23:16:54 [Debug] :  [Sending] ==> {"type":"subscribe_events","id":20,"event_type":"state_changed"}
1028 23:16:54 [Warning] :  Can't get services: Instance of 'HAError'
1028 23:16:54 [Warning] :  Can't get user info: Instance of 'HAError'
1028 23:17:11 [Debug] :  AppLifecycleState.inactive
1028 23:17:11 [Debug] :  AppLifecycleState.paused
1028 23:18:00 [Error] :  Socket stream Error: WebSocketChannelException: WebSocketChannelException: SocketException: OS Error: Software caused connection abort, errno = 103, address = zanna87.duckdns.org, port = 59390
1028 23:18:47 [Debug] :  AppLifecycleState.inactive
1028 23:18:47 [Debug] :  AppLifecycleState.resumed
1028 23:18:47 [Debug] :  Socket connecting...
1028 23:19:02 [Error] :  Bad state: Future already completed
1028 23:19:02 [Error] :  #0      _Completer.completeError (dart:async/future_impl.dart:21)
#1      ConnectionManager._doConnect.. (package:hass_client/managers/connection_manager.class.dart:103)
#2      _rootRunUnary (dart:async/zone.dart:1132)
#3      _CustomZone.runUnary (dart:async/zone.dart:1029)
#4      _FutureListener.handleValue (dart:async/future_impl.dart:137)
#5      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678)
#6      Future._propagateToListeners (dart:async/future_impl.dart:707)
#7      Future._completeWithValue (dart:async/future_impl.dart:522)
#8      Future._asyncComplete. (dart:async/future_impl.dart:552)
#9      _rootRun (dart:async/zone.dart:1124)
#10     _CustomZone.run (dart:async/zone.dart:1021)
#11     _CustomZone.runGuarded (dart:async/zone.dart:923)
#12     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:963)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
1028 23:19:02 [Warning] :  Previous connection attempt pending...
1028 23:19:02 [Warning] :  Previous connection attempt pending...
1028 23:19:02 [Warning] :  Previous connection attempt pending...
1028 23:19:02 [Warning] :  Previous connection attempt pending...
1028 23:19:02 [Warning] :  Previous connection attempt pending...
1028 23:19:02 [Warning] :  Previous connection attempt pending...
1028 23:19:08 [Debug] :  AppLifecycleState.inactive
1028 23:19:08 [Debug] :  AppLifecycleState.paused
1028 23:19:10 [Debug] :  AppLifecycleState.inactive
1028 23:19:10 [Debug] :  AppLifecycleState.resumed
1028 23:19:10 [Warning] :  Previous connection attempt pending...
1028 23:19:16 [Debug] :  AppLifecycleState.inactive
1028 23:19:16 [Debug] :  AppLifecycleState.paused
1028 23:19:17 [Debug] :  [Sending] ==> {"type":"get_states","id":21}
1028 23:19:17 [Debug] :  [Sending] ==> {"type":"get_config","id":22}
1028 23:19:17 [Debug] :  [Sending] ==> {"type":"get_services","id":23}
1028 23:19:17 [Debug] :  [Sending] ==> {"type":"auth/current_user","id":24}
1028 23:19:17 [Debug] :  [Sending] ==> {"type":"get_panels","id":25}
1028 23:19:17 [Debug] :  [Sending] ==> {"type":"subscribe_events","id":26,"event_type":"state_changed"}
1028 23:19:17 [Warning] :  Can't get services: Instance of 'HAError'
1028 23:19:17 [Warning] :  Can't get user info: Instance of 'HAError'
1028 23:19:25 [Error] :  Bad state: Future already completed
1028 23:19:25 [Error] :  #0      _Completer.completeError (dart:async/future_impl.dart:21)
#1      ConnectionManager._doConnect.. (package:hass_client/managers/connection_manager.class.dart:103)
#2      _rootRunUnary (dart:async/zone.dart:1132)
#3      _CustomZone.runUnary (dart:async/zone.dart:1029)
#4      _FutureListener.handleValue (dart:async/future_impl.dart:137)
#5      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678)
#6      Future._propagateToListeners (dart:async/future_impl.dart:707)
#7      Future._completeWithValue (dart:async/future_impl.dart:522)
#8      Future._asyncComplete. (dart:async/future_impl.dart:552)
#9      _rootRun (dart:async/zone.dart:1124)
#10     _CustomZone.run (dart:async/zone.dart:1021)
#11     _CustomZone.runGuarded (dart:async/zone.dart:923)
#12     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:963)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
1028 23:19:25 [Warning] :  Previous connection attempt pending...
1028 23:19:25 [Warning] :  Previous connection attempt pending...
1028 23:19:25 [Warning] :  Previous connection attempt pending...
1028 23:19:25 [Warning] :  Previous connection attempt pending...
1028 23:19:25 [Warning] :  Previous connection attempt pending...
1028 23:19:25 [Warning] :  Previous connection attempt pending...
1028 23:19:28 [Debug] :  AppLifecycleState.inactive
1028 23:19:28 [Debug] :  AppLifecycleState.resumed
1028 23:19:28 [Warning] :  Previous connection attempt pending...
1028 23:19:37 [Debug] :  AppLifecycleState.inactive
1028 23:19:37 [Debug] :  AppLifecycleState.paused
1028 23:19:39 [Debug] :  AppLifecycleState.inactive
1028 23:19:39 [Debug] :  AppLifecycleState.resumed
1028 23:19:39 [Warning] :  Previous connection attempt pending...
1028 23:19:40 [Debug] :  [Sending] ==> {"type":"get_states","id":27}
1028 23:19:40 [Debug] :  [Sending] ==> {"type":"get_config","id":28}
1028 23:19:40 [Debug] :  [Sending] ==> {"type":"get_services","id":29}
1028 23:19:40 [Debug] :  [Sending] ==> {"type":"auth/current_user","id":30}
1028 23:19:40 [Debug] :  [Sending] ==> {"type":"get_panels","id":31}
1028 23:19:40 [Debug] :  [Sending] ==> {"type":"subscribe_events","id":32,"event_type":"state_changed"}
1028 23:19:40 [Warning] :  Can't get services: Instance of 'HAError'
1028 23:19:40 [Warning] :  Can't get user info: Instance of 'HAError'
`

HA Client is an unofficial Android app for Home Assistant. The issues with Home Assistant itself should be report to Home Assistant repository: https://github.com/home-assistant/home-assistant

Ok, sorry!


Shared Debugging of attached process

Related to #1458
The ability to have a shared debug session, without any project open.
While just debugging a process that the debugger was attached to.
Via the Debug -> Attach to process.
Usecase:
I develop dll's that are loaded into another program.
When my users are having problems I'd like to be able to remote debug without having to use something like teamviewer.
But as they don't have a project file, but instead just dll's with pdb's and a process to attach to which has loaded these dll's, live share doesn't work there.

I'm going to close this for now since we haven't heard significant customer feedback for this. If this is something that folks would like to see us prioritize, please let us know by re-opening/commenting on this bug. Thanks!


Forbid old operator in precondition clauses (requires and checks)

Route whereami information in type checker
Reject old in requires and checks clauses

CI is happy. I merge.


Documentation enhancements

I found it a bit challenging to get the static media wired up. Even though the docs suggesting seeing the upstream repos for more information, they weren't super helpful either.
So that staticfilesfinder can find the js assets, this must be added to INSTALLED_APPS:
'zxcvbn_password',
You refer to form.media, but that doesn't work because the example form in the docs doesn't have a Media: class. However, I think it's easier to just  include JS in the template:
{% load static %}
...
<script src="{% static 'zxcvbn_password/js/zxcvbn.js' %}"></script>
<script src="{% static 'zxcvbn_password/js/password_strength.js' %}"></script>

With that done, it started working but the indicator bar never changed color. Had to add to my css:
.progress-bar-warning {
    background-color: yellow;
}

.progress-bar-danger {
    background-color: red;
}

.progress-bar-success {
    background-color: green;
}

Finally, a little guidance on processing a valid password would be helpful (since we don't see Django's set_password() all that often:
        if form.is_valid():
            user = request.user
            user.set_password(form.cleaned_data['password1'])
            user.save()

I'll do a PR if you approve of the idea.

Thanks for your report. Yes a PR would be much appreciated :) Please separate code and documentation in different PRs of course. Just came back from holidays, lot of work to catch up ^^

Hi -
I actually ended up doing a more manual implementation of zxcvbn rather than using this library. So since I'm not using it, am probably not the best person to do the PR after all. Should be an easy doc tweak though. Thanks!

So, to get back at this:

[x] doc about adding zxcvbn_password in INSTALLED_APPS: done thanks to @beruic
[ ] note about upstream docs: I will remove this note since it does not seem to be helpful
[ ] note about form.media: I will update this note to be more clear: including {{ form.media }} in the JS block of your template will in fact include media from all form's fields and widgets. In this app, the only declared media is in the PasswordStrengthInput widget.
[ ] colors not working: indeed the JS code relies on jquery and bootstrap :confused: I will add a note about these requirements in the README.
[x] guidance about Django's set_password: it's an example among many others, I personally don't use set_password. Usually you just User.objects.create(username=..., password=...) with username and password retrieved from the form cleaned data.

Thanks @shacker for your feedback!


Bug in generic form example.

https://github.com/camunda-consulting/code/blob/4a62d4b44efb126b50f22a6f17273c7c98f8b6da/snippets/camunda-tasklist-examples/camunda-react-app/src/components/GenericForm.js#L6
×
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Check the render method of GenericForm.

https://github.com/camunda-consulting/code/blob/4a62d4b44efb126b50f22a6f17273c7c98f8b6da/snippets/camunda-tasklist-examples/camunda-react-app/src/components/GenericForm.js#L6
×
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Check the render method of GenericForm.

Were you able to solve this problem?

nop. Perhaps stale repo.


Update light curve notebook v20

Replace Twinkles light curve notebook with Stack Club Course light curve notebook so that we are compatible with v20.

Part of #236


using showmonthyeardropdown crashes the web page

Just installed the base version and things were working fine.
However, when I added the attribute showMonthYearDropdown, and then clicked on the down arrow for year, the webpage freezes up and the only way to get out is to kill the page.
I tried showYearDropdown and showMonthdrop down separately, and these seem to work fine.
It appears to be with this specific setting.

This should be fixed with #2132 merged. We will release a new version shortly.

Just installed version 3.0.0 today and it's still crashing using the showMonthYearDropdown option.

Same issues. @ttchuah 's suggesion is a working workaround.

Still crashing, so this is not fixed.
For now @ttchuah's solution is working.

Workaround with minMaxDate is working, however if I put min date to 1900-1-1, the result is enormously long select. There should be scrolling.


Is Bootstrap V4 going to provide different & configurable Grid Gutter sizes?

For example: https://getuikit.com/docs/grid.html#grid-gutter

+1 , Reminds me of no-gutters ( #19107 & added in #21211 )
.no-gutters {
    margin-right: 0;
    margin-left: 0;
    > [class*="col-"] {
      padding-right: 0;
      padding-left: 0;
    }
  }

So, yeah something like small, medium and large-gutters looks a good idea
here is the code for it ,
.small-gutters {
    margin-right: -15px;
    margin-left: -15px;
    > [class*="col-"] {
      padding-right: 15px;
      padding-left: 15px;
    }
  }

.medium-gutters {
    margin-right: -30px;
    margin-left: -30px;
    > [class*="col-"] {
      padding-right: 30px;
      padding-left: 30px;
    }
  }

.large-gutters {
    margin-right: -45px;
    margin-left: -45px;
    > [class*="col-"] {
      padding-right: 45px;
      padding-left: 45px;
    }
  }

Special Note: Small gutters in my example is the one which is the default for bootstrap row

Customizable grid gutters are available by breakpoint, but not with a modifier class. No plans to add such classes at this time.

That's a definite deal-breaker. I've had plenty of occasions I had to do this manually so I'll be choosing a different framework from now on.
Thanks

@gkatsanos Sounds good! While I mentioned there are no plans to add such classes at this time, that doesn't mean they can't be added down the line. I'm not sure if @IamManchanda's solution is the best, but this seems like a rather straightforward modification to make (on our end or your's).

@mdo I'm sorry, do you mind clarifying a bit what you mean by this time" and "down the line" ? It seems as if your former answer and the latter conflict a bit.
Technically the way I see it, the Bootstrap grid is conceived in a way which makes variable grid sizing complex. (even though it's achievable but with side-effects)
FYI I don't want to sound bitter; I've used Bootstrap for over 3 years in very high volume websites. But Designers and Product people want control over the results, and they won't always accept one size gutters in the products they design.
http://ink.sapo.pt/ui-elements/grid/#gutters

I don't see a conflict with those comments—we're not going to add custom gutters beyond the gutter per grid tier at this time. In the future, we might revisit that and better enable folks to change gutters ad hoc on rows/columns.
Styles for such a solution likely look an awful lot like @IamManchanda's code snippet fwiw.

Yeap, @IamManchanda 's solution seems the way to go, but there's the .container-fluid class as well with padding-right and padding-left values which depend on the gutter size, right?

@gkatsanos This comment ( https://github.com/twbs/bootstrap/pull/21211#issuecomment-265346365 ) might help you with your doubts .
Container and container-fluid both have a padding of 15px on right and left. Its just a difference that container is a fixed width ( media query breakpoints ) and whereas container-fluid has a 100% width no matter the device screen size.

@gkatsanos This comment ( https://github.com/twbs/bootstrap/pull/21211#issuecomment-265346365 ) might help you with your doubts .
Container and container-fluid both have a padding of 15px on right and left. Its just a difference that container is a fixed width ( media query breakpoints ) and whereas container-fluid has a 100% width no matter the device screen size.

@IamManchanda I understand that. So If you add a "no-gutters" class on the "row" div, how are you going to modify the left/right padding values of the "container"  (or container-fluid) ?

could you jsbin/codepen your issue you facing with my above code ? @gkatsanos

@IamManchanda Sorry for the slow reply. I made this: http://codepen.io/gkatsanos/pen/WRrZBx . As you can see from the 'debug' borders, the external 'container-fluid' paddings are inconsistent. If you resize down to smaller than 992px viewport, you'll clearly see horizontals scrollbars or extra paddings.. the only workaround is adding extra responsive logic to the gutter sizing classes so they're cancelled when on mobile but still that's far from bulletproof (and it has to do with the way the Bootstrap grid works)

@gkatsanos So do you have any suggested fix ( code ) and a best solution ?
Also , Please use ..... v4 alpha 6 instead of v3.3.7 in your codepen settings

Sorry for the slow reply

No need to be sorry!

The solution would involve radical changes in how the grid is built (solved in other grid systems of other frameworks) and I doubt @mdo would put it forward.

I'd like to raise that issue again.


$interpolateProvider - StartSymbol & EndSymbol

The StartSymbol and EndSymbol from the $interpolateProvider are not used.

Can you be more specific as to why this is an issue?  The default is to use double curly brackets.

Yeah i know. I am using this $interpolateProvide to change the Symbols to [[ & ]] because of some issues with my template engine.
var app = ...
app.config(function($interpolateProvider) {
            $interpolateProvider.startSymbol('[[');
            $interpolateProvider.endSymbol(']]');
});

and on line 13 in the file md-data-table.js you find this:
template.text('{{ name }}');

i've never used this .text function before, therefore i have never issues with custom symbols.

Ah okay, I need to get the start and stop symbols from the $interpolateProvider instead of assuming they will be the double curly brackets.

no big deal ;)
thumbs up for this plugin, i like it!

I just released v0.8.1 to fix this issue. Thanks! I'm happy to hear you like it.


Charset problem after update to 1.7.3

Hi,
after updating to 1.7.3 the titles of all original links before the update are showing with weired chars as shown in the screenshot. I didn't change anything in the database.

Wild shot in the dark with 0.5% chance of improvement: what if you replace 'utf8' with 'utf8mb4' here?
I'm interested to know what it would cause for your previously existing links (same display?) and new links
(from what I understand about utf8, in your case (greek chars) it shouldn't change anything)

No change.
All new links created after the update to 1.7.3 are displayed correctly, only the old ones before the update are wrong.

Same here. Server migration. MySQL dumped and imported into new DB on new server. Special (non-ASCII) characters are garbled now.
Old server:

PHP 5.4.45-0+deb7u14
mysql  Ver 14.14 Distrib 5.5.60
yourls 1.7

New Server:

PHP 7.2.15-0ubuntu<IP_ADDRESS>
mysql  Ver 14.14 Distrib 5.7.25
yourls 1.7.3

Quick'n'dirty fix is:
replace
$charset = yourls_apply_filter( 'db_connect_charset', 'utf8' );
with
$charset = yourls_apply_filter( 'db_connect_charset', 'latin1' );
in /yourls/includes/class-mysql.php:31

Anyone still following this discussion and having titles fucked up, and willing to try something?

@ozh Hello.
I had the same issue with an upgrade from 1.7.1.
I wrote the following migration script and it seems to work fine.
<?php
$db_host = 'mysql';
$db_name = 'db';
$db_user = 'user';
$db_pass = 'user_pass';

# change me
$table = 'url_migrated';

$dbh_latin1 = new PDO("mysql:host=$db_host;dbname=$db_name;charset=latin1", $db_user, $db_pass);
$dbh_utf8 = new PDO("mysql:host=$db_host;dbname=$db_name;charset=utf8", $db_user, $db_pass);

foreach($dbh_latin1->query("SELECT * from $table") as $row) {
#  print_r($row);
  $stmt = $dbh_utf8->prepare("update $table set title = :title where keyword = :keyword");
  $stmt->execute([
    ':keyword' => $row['keyword'],
    ':title' => $row['title'],
  ]);
}

$dbh_latin1 = null;
$dbh_utf8 = null;

Thank you for your wonderful product.


Include resolve migration. Will add tests next.

Let me know when you've done some tests and I'll enable the CircleCI integration


qMasterPassword: 1.2.2 -> git master

Motivation for this change
There have been fixes and translation additions on the master branch, but no release since 2016. Let's pin to the latest commit on the master branch to benefit from all recent changes.
Regarding translations on Darwin, I couldn't find where to put the translation *.qm files so that they'll be read at runtime. Feedback welcome to fix this.
Things done
Tested in all three translated languages and confirmed working:
LANG=de_DE ./result/bin/qMasterPassword
LANG=pl_PL ./result/bin/qMasterPassword
LANG=en_US ./result/bin/qMasterPassword

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@tadeokondrak

Can you open an issue upstream to request a new release? This should not be blocking imo, but still it is nice to start the process.

https://nixos.org/manual/nixpkgs/unstable/#sec-package-naming

If a package is not a release but a commit from a repository, then the version part of the name must be the date of that (fetched) commit. The date must be in "YYYY-MM-DD" format. Also append "unstable" to the name - e.g., "pkgname-unstable-2014-09-23".

(and I think the preferred convention splitting them between pname and version is pkgname-unstable and 2014-09-13)

Thank you for your feedback, I tried to address it. Feel free to review whenever you've got a minute.


Vault configuration in composite profile is not picked up.

Describe the bug
Any vault configuration in composite profile is ignored and instead default values are used.
Given following configuration for config-server:
spring:
  profiles:
    active: composite
  cloud:
    config:
      server:
        composite:
          - type: vault
            host: my-vault-server
            port: 5555

When executing curl -H "X-Config-Token: token" localhost:8888/cook/default config-server should call vault at http://my-vault-server:5555 but instead it calls http://<IP_ADDRESS>:8200.
Sample log
2024-10-16T12:08:27.258+02:00  WARN 69385 --- [configserver] [nio-8888-exec-1] o.s.c.c.s.e.EnvironmentController        : Error getting the Environment with name=cook profiles=default label=null includeOrigin=false

org.springframework.web.client.ResourceAccessException: I/O error on GET request for "http://<IP_ADDRESS>:8200/v1/secret/cook": Connect to http://<IP_ADDRESS>:8200 [/<IP_ADDRESS>] failed: Connection refused
	at org.springframework.web.client.RestTemplate.createResourceAccessException(RestTemplate.java:926) ~[spring-web-6.2.0-20241016.082823-965.jar:6.2.0-SNAPSHOT]
	at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:906) ~[spring-web-6.2.0-20241016.082823-965.jar:6.2.0-SNAPSHOT]
	at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:801) ~[spring-web-6.2.0-20241016.082823-965.jar:6.2.0-SNAPSHOT]
	at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:712) ~[spring-web-6.2.0-20241016.082823-965.jar:6.2.0-SNAPSHOT]
	at org.springframework.vault.core.VaultKeyValueAccessor.lambda$doRead$1(VaultKeyValueAccessor.java:133) ~[spring-vault-core-3.1.2.jar:3.1.2]
	at org.springframework.vault.core.VaultKeyValueAccessor.lambda$doRead$2(VaultKeyValueAccessor.java:166) ~[spring-vault-core-3.1.2.jar:3.1.2]
	at org.springframework.vault.core.VaultTemplate.doWithSession(VaultTemplate.java:451) ~[spring-vault-core-3.1.2.jar:3.1.2]
	at org.springframework.vault.core.VaultKeyValueAccessor.doRead(VaultKeyValueAccessor.java:163) ~[spring-vault-core-3.1.2.jar:3.1.2]
	at org.springframework.vault.core.VaultKeyValueAccessor.doRead(VaultKeyValueAccessor.java:132) ~[spring-vault-core-3.1.2.jar:3.1.2]
	at org.springframework.vault.core.VaultKeyValueAccessor.doRead(VaultKeyValueAccessor.java:107) ~[spring-vault-core-3.1.2.jar:3.1.2]
	at org.springframework.vault.core.VaultKeyValue1Template.get(VaultKeyValue1Template.java:69) ~[spring-vault-core-3.1.2.jar:3.1.2]
	at org.springframework.cloud.config.server.environment.vault.SpringVaultEnvironmentRepository.read(SpringVaultEnvironmentRepository.java:55) ~[classes/:na]
	at org.springframework.cloud.config.server.environment.AbstractVaultEnvironmentRepository.findOne(AbstractVaultEnvironmentRepository.java:107) ~[classes/:na]

NOTE: the behaviour is correct when using vault profile, instead of composite.
spring:
  profiles:
    active: vault
  cloud:
    config:
      server:
        vault:
            host: my-vault-server
            port: 5555

I could have swore there was an issue around this already...but I can't seem to find it.
I seem to remember looking into something similar a while back and discovering that Vault wasn't supported by composite environment repositories (or some properties in the configuration were not supported).  I can't seem to find the issue though.

@ryanjbaxter I'll take a look and try to find a fix.


Contour macos dmg don't have release for intel macbooks, it can be installed for m's apple macbooks

Contour Terminal version
<IP_ADDRESS>47
Installer source
GitHub: release page
Operating System
macOS Sanoma 14.6.1
Architecture
x86-64
Other Software
No response
Steps to reproduce
Download macOs DMG and try to install on Intel's macbook (before 2021)
Expected Behavior
Contours successfully run on this macbook
Actual Behavior
CPU architecture doesn't support for this application
Additional notes
No response

It seems GitHub Actions for the macos-14  runner using arm64 host. https://github.com/actions/runner-images?tab=readme-ov-file#available-images
Intel host avlaible only for GitHub Teams or GitHub Enterprise.
can we use macos-13 for building intel version? is contour code hard linking to macos 14 only?

I am not sure that macos-13 provides compilers with c++20 support, but I think that we can use macos-15-large runners as an open source project (usage time is limited though, so better to use it only for release)

I think that we can use macos-15-large runners as an open source project (usage time is limited though, so better to use it only for release)

@Yaraslaut Why would we need a -large runner so much? Is that because of the Qt self-compilation? Wasn't that only for older Linux builds?

this is x86 runners, macos-15 is arm
macOS 15 beta 	macos-15-large 	[macOS-15](https://github.com/actions/runner-images/blob/main/images/macos/macos-15-Readme.md) 	Endpoint Badge
macOS 15 Arm64 beta 	macos-15 or macos-15-xlarge 	[macOS-15-arm64](https://github.com/actions/runner-images/blob/main/images/macos/macos-15-arm64-Readme.md) 	Endpoint Badge


fix: 🐛 correct error state when initial values provided

Validation errors aren't showing on mount because isFieldError uses
isTouched. The field won't be considered touched until the user clicks
it, which is why we're seeing the current behavior. If we use hasValue
it will show those errors when the field has an initial value.
https://www.loom.com/share/2049ee6738ee477dabb9df1bce9d5596
✅ Closes: #165

Nice fix!
Would this also be a good candidate for a test in the future?
Test to ensure proper error State on initial load?

Yes, we should create a method for testing the error state that can be reused across all the component tests to ensure that their behavior is consistent.

It's been a hot minute since I looked at it but I think this might fix #89 as well.

Yep, confirmed that this will solve that issue as well

:tada: This PR is included in version 4.3.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


dependencyLicenseInfo thinks the project's own license is unspecified

E.g.
$ sbt dependencyLicenseInfo
[info] Loading settings for project global-plugins from build.sbt,idea.sbt ...
[info] Loading global plugins from /home/hhrutz/.sbt/1.0/plugins
[info] Loading settings for project mellite-build from plugins.sbt ...
[info] Loading project definition from /home/hhrutz/Documents/devel/Mellite/project
[info] Loading settings for project mellite from build.sbt ...
[info] Set current project to Mellite (in build file:/home/hhrutz/Documents/devel/Mellite/)
[info] No license specified
[info] 	 de.sciss:mellite_2.12:2.27.0
[info] 	 lucene:lucene:1.4.3
[info] 	 com.sleepycat:je:5.0.104
[info]
[info] AGPL v3+
[info] 	 de.sciss:fscape_2.12:2.17.0
[info] 	 de.sciss:fscape-cdp_2.12:2.17.0
...

So this is run from Mellite project, which is the first line printed in "No license specified". The settings are clear:
licenses := Seq("GNU Affero General Public License v3+" -> url("http://www.gnu.org/licenses/agpl-3.0.txt"))

I also tried licenses in ThisBuild. Perhaps the plugin tries to resolve the artifact which in this case is not yet published. So I guess it should realise if an artifact designes the sbt project itself and receive the license information from there?

Yep, right now it only includes dependencies and gets the information from the dependency resolution layer. We could either keep it that way and remove the first entry or treat it specially by using the sbt information.


use getTopicId instead of getId for generated discourse topics

Need to use getTopicId instead of getId

restarted one job, looked like transient issue


Fix https://github.com/nrc/rustfmt/issues/389

rewrite_string now prefers to look for punctuation to split on, and then goes to the nearest non-escape character as a last resort.

Not sure why this failed the test, it compiles on my machine. Anyone have some wisdom for me?

Not sure why you're getting the parse error, the code looks like it should be fine to me.

I pulled your branch and I also get this error. You could try rebasing - might be a weird merge error.

That was weird, it didn't match my local. Must have been a merge thing. Fixed the parse error by manually updating my fork, but now it is failing with an "arithmetic overflow" on a line that doesn't seem to have that issue.

overflow could be underflow - so presumably cur_start > cur_end

Got it! Was failing the formatting test. It is squeaky clean now.

Could you add some tests please?

Yeah, I'll make these changes and some tests.

I have made the changes.

This looks good to me. Could you squash the some of the commits?

I changed the logic and squashed the commits. One question though - what exactly is the "arithmetic overflow"? I don't fully understand that error.

Arithmetic overflow is the condition that occurs when the result of a computation cannot be represented accurately by its type.
The type usize, for example, can only represent some non-negative numbers. -5 cannot be represented in as usize, so 5usize - 10usize will overflow.
This can also happen when numbers become to large. 128u8 + 128u8 will also overflow, since the largest number that u8 can represent is 255.

Thanks!


Can't disconnect crashed server

Describe the bug
When a backend server that connected to bungeesk crashes it doesn't get removed from bungeesk connections. And even you can't disconnect it manually. So you have to disconnect all servers and connect one by one again.
To Reproduce
Steps to reproduce the behavior:
Connect one of your backend servers to bungeesk
kill the process of thtat backend server
try to disconnect that server in bungee console
Expected behavior
Removal of disconnected connection on bungee side.
Screenshots

Desktop (please complete the following information):

OS: Centos 7 64x
Spigot version: 119
BungeeSK version 2.0.0

Additional context
I have 2 backend servers. One of them are connected and it didn't shown in the bungeesk servers list.
I can't disconnect manually. Both connected and disconnected servers. Everytime I have to disconnect all servers and connect them all one by one again.
You can add keepalive to the plugin. It'll check the connections and if there's no respond it'll disconnects that server and tries to connect again.

Hey!
I also have the same problem but a little bit different :
the lobby can't get the info from the proxy (such as connected players, co servers, etc).
What happens is that the lobby disconnects from the proxy but the proxy doesn't want the lobby to reconnect.
To solve the problem temporarily I have to do bungeesk disconnect <IP_ADDRESS>:30001 in the proxy console to disconnect the lobby then it reconnects itself.
The weirdest thing is that the lobby understands that it is disconnected from the proxy and wants to reconnect but the proxy doesn't allow the connection and says that there is already a server connected with this ip/port exactly like you.
Another amazing thing is that it happens at totally random times xD. So I have to be ready at any time to fix the problem and do what I explained in the paragraph above.
I found these 2 errors (which are the same) that occur in the proxy console when the bug appears (The 2 errors are sure to occur on 2 different days) :
[21:13:39] [Thread-13/ERROR]: Exception in thread "Thread-13" java.lang.NullPointerException: Cannot invoke "net.md_5.bungee.api.connection.Server.getInfo()" because the return value of "net.md_5.bungee.api.connection.ProxiedPlayer.getServer()" is null
[21:13:39] [Thread-13/ERROR]:     at fr.zorg.bungeesk.bungee.sockets.ClientServer.read(ClientServer.java:398)
[21:13:39] [Thread-13/ERROR]:     at java.base/java.lang.Thread.run(Thread.java:833)

[13:02:13] [Thread-10/ERROR]: Exception in thread "Thread-10" java.lang.NullPointerException: Cannot invoke "net.md_5.bungee.api.connection.Server.getInfo()" because the return value of "net.md_5.bungee.api.connection.ProxiedPlayer.getServer()" is null
[13:02:13] [Thread-10/ERROR]:     at fr.zorg.bungeesk.bungee.sockets.ClientServer.read(ClientServer.java:398)
[13:02:13] [Thread-10/ERROR]:     at java.base/java.lang.Thread.run(Thread.java:833)

Configuration
Proxy :

Waterfall 1.19-498
BungeeSK V1.1.1

Lobby :

Paper 1.18.2-302
Skript 2.6.1
BungeeSK 1.1.1

Should be fixed in v2.0.0, download it here

Should be fixed in v2.0.0, download it here

It seemed to be fixed at first but now I had a short internet connection and backend servers disconnected but they still show up in bungee

and also found strange ip in results of /bungeesk servers
<IP_ADDRESS>:0

I disconnected all servers from bungee console with bungeesk disconnect all
but backends still thought they are connected send "s" if client is conned
I manually did disconnect the client and run connect skript.

@ZorgBtw

Can you try using this version please ?

I'll asap


NuttX stm32f7 re-enable dcache with write back

WIP PR for testing NuttX dcache writeback fixes on Jenkins HIL.

fixes https://github.com/PX4/Firmware/issues/12216

Nuttx stm32f7 serial history. https://github.com/PX4/NuttX/commits/px4_firmware_nuttx-7.28%2B/arch/arm/src/stm32f7/stm32_serial.c

@davids5 this is working with the NuttX 7.29 update (https://github.com/PX4/Firmware/pull/12344). I believe the difference is the cache unification. https://groups.google.com/forum/#!searchin/nuttx/cache$20unify|sort:date/nuttx/fGAD89gI6-M/8TV_RLWjCQAJ
https://github.com/PX4/NuttX/commit/64252a298fa550f09abf98b93baed53d077a60b7#diff-2f27829e583fd2f028175d1d9709a719

@PX4/testflights could you try this on all fmu-v5 hardware (pixhawk 4, 4 mini, cuav 5+ and 5 nano)?

Tested on Pixhawk4 v5 f-450
Modes Tested:
Position Mode: no issue
Altitude Mode: no issue
Stabilized Mode: no issue
mission mode : no issues
pr log:
https://review.px4.io/plot_app?log=c6b26152-f3ad-4b96-a9ff-df5b38dea367
master log:
https://review.px4.io/plot_app?log=875cb2b2-79d5-4953-b13b-69fe9dba9c9e

Tested on Pixhawk 4mini v5:
Modes Tested:
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL: Good.
Procedure:
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint activate RTL and see landing behaviour.
Notes:
No issues noted, good flight in general.
Logs:

PR12435: https://review.px4.io/plot_app?log=626630a4-a302-4800-a540-d35c25ff2108

Master: https://review.px4.io/plot_app?log=20ddbd80-9dc5-4702-9ef2-6ac583c01450

Tested on Pixhawk Pro v4:
Modes Tested:

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL: Good.

Procedure:
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint activate RTL and see landing behaviour.
Notes:
No issues noted, good flight in general.
Logs:

PR12435: https://review.px4.io/plot_app?log=a38d33f3-8023-437b-af09-a3d6df75d0bd

Master: https://review.px4.io/plot_app?log=e67424c5-e435-49f1-9b82-c298f5e643d9

Tested on NXP FMUK66 v3:
Modes Tested:

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL: Good.

Procedure:
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint activate RTL and see landing behaviour.
Notes:
No issues noted, good flight in general.
Logs:

PR12435: https://review.px4.io/plot_app?log=c2174d76-f23d-4432-b34a-3c1600c86158

Master: https://review.px4.io/plot_app?log=ab3333a4-175f-40f8-87d3-6dc6b927d0eb

Tested on Pixhack+ v5:
Modes Tested:
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL: Good.
Procedure:
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint activate RTL and see landing behaviour.
Notes:
No issues noted, good flight in general.
Logs:
https://review.px4.io/plot_app?log=9c882101-d3b6-4561-88d8-cbb237ee0385

Last we tested this the PIO changes alone did not fix the issues. Was part of the fix in 7.29?

@dagar OK I understand it now:
The dcache is a 4 way assoc cache it has 128 indexes * 4 ways == 512 entries * 32 byte line size == 16KB cache.
The nuttx 7.28 code arch_invalidate_dcache was purely wrong: taking an address and making a set is fine but invalidating all 4 ways is incorrect. It should have invalidated just one. But that is not how it is suposde to be done.  The correct way to do it is using the MVA (DCCMVAC  -Data cache clean by address to the PoCb) as it is in 7.29
This did not matter in a Write Through scheme because  what was written in the cache was (also) in memory. An invalidate operation would lead to a later read it back. But in write back mode the invalidate lost the data not yet committed to memory.
Adding this to master proves the point by fixing the bad code.
tmpways = 3..0
      do
         {
           sw = ((tmpways << wshift) | (set << sshift));

+           putreg32(sw, NVIC_DCCSW); // Clean (commit to memory dirty entries) all the ways of a set
+           ARM_DSB();
           putreg32(sw, NVIC_DCISW);
         }
       while (tmpways--);

Works.

@dagar rebased on master and force pushed.

Thank you @davids5!

Just some metrics:
This PR with Write Back D:
 PID COMMAND                   CPU(ms) CPU(%)  USED/STACK PRIO(BASE) STATE FD
   0 Idle Task                   23070 59.287   284/  748   0 (  0)  READY  3
   1 hpwork                          0  0.000   344/ 1780 249 (249)  w:sig  3
   2 lpwork                         18  0.084   608/ 1780  50 ( 50)  w:sig  8
   3 init                          826  0.000  1728/ 2604 100 (100)  w:sem  3
   4 wq:manager                      1  0.000   808/ 1172 244 (244)  w:sem  7
 205 top                           366  2.544  1560/ 1884 255 (255)  RUN    3
  17 dataman                        57  0.000   752/ 1180  90 ( 90)  w:sem  4
  20 wq:lp_default                  19  0.084   724/ 1500 205 (205)  w:sem  7
  22 wq:I2C1                       121  0.508   748/ 1244 248 (248)  READY  7
  27 wq:hp_default                   4  0.000   476/ 1500 243 (243)  w:sem  7
  44 wq:SPI1                      4733 19.168   672/ 1244 254 (254)  READY  7
  49 wq:I2C2                         0  0.000   368/ 1244 247 (247)  w:sem  7
  54 wq:I2C3                        80  0.339   748/ 1244 246 (246)  READY  7
  56 wq:SPI5                         0  0.000   368/ 1244 250 (250)  w:sem  7
  63 wq:SPI4                        63  0.339   536/ 1244 251 (251)  READY  7
  80 sensors                       588  2.544  1256/ 1964 238 (238)  w:sem 11
  83 commander                     234  0.848  1564/ 3212 140 (140)  READY  6
  85 commander_low_prio              0  0.000   656/ 2996  50 ( 50)  w:sem  6
  93 mavlink_if0                  1048  3.562  1648/ 2532 100 (100)  READY  4
  94 mavlink_rcv_if0                78  0.339  1336/ 2836 175 (175)  w:sem  4
 134 gps                            53  0.169  1032/ 1516 209 (209)  w:sem  4
 162 mavlink_if1                   410  1.017  1648/ 2484 100 (100)  w:sig  4
 163 mavlink_rcv_if1                76  0.254  1408/ 2836 175 (175)  w:sem  4
 174 ekf2                         1403  6.361  4536/ 6572 239 (239)  w:sem  4
 178 navigator                      27  0.169   888/ 1764 105 (105)  w:sem  4
 204 log_writer_file                 0  0.000   376/ 1164  60 ( 60)  w:sem 24
 201 logger                        118  0.508  1312/ 3644 234 (234)  w:sem 24

Processes: 27 total, 8 running, 19 sleeping, max FDs: 54
CPU usage: 38.85% tasks, 1.87% sched, 59.29% idle
DMA Memory: 5120 total, 1024 used 1536 peak
Uptime: 34.546s total, 23.070s idle
nsh> sd_bench
INFO  [sd_bench] Using block size = 4096 bytes, sync=0
INFO  [sd_bench]
INFO  [sd_bench] Testing Sequential Write Speed...
INFO  [sd_bench]   Run  0:   316.56 KB/s, max write time: 344 ms (=  11.63 KB/s), fsync: 632 ms
INFO  [sd_bench]   Run  1:   432.32 KB/s, max write time: 163 ms (=  24.54 KB/s), fsync: 11 ms
INFO  [sd_bench]   Run  2:   139.47 KB/s, max write time: 972 ms (=   4.12 KB/s), fsync: 5 ms
INFO  [sd_bench]   Run  3:   471.89 KB/s, max write time: 90 ms (=  44.44 KB/s), fsync: 6 ms
INFO  [sd_bench]   Run  4:   468.45 KB/s, max write time: 56 ms (=  71.43 KB/s), fsync: 4 ms
INFO  [sd_bench]   Avg   :   359.18 KB/s
nsh>

This PR with CONFIG_ARMV7M_DCACHE_WRITETHROUGH=y
 PID COMMAND                   CPU(ms) CPU(%)  USED/STACK PRIO(BASE) STATE FD
   0 Idle Task                   12276 59.287   284/  748   0 (  0)  READY  3
   1 hpwork                          0  0.000   344/ 1780 249 (249)  w:sig  3
   2 lpwork                         12  0.084   580/ 1780  50 ( 50)  w:sig  8
   3 init                          821  0.000  1728/ 2604 100 (100)  w:sem  3
   4 wq:manager                      1  0.000   808/ 1172 244 (244)  w:sem  7
 197 top                           213  2.629  1560/ 1884 255 (255)  RUN    3
  17 dataman                        58  0.000   752/ 1180  90 ( 90)  w:sem  4
  20 wq:lp_default                  14  0.084   724/ 1500 205 (205)  w:sem  7
  22 wq:I2C1                        96  0.508   748/ 1244 248 (248)  READY  7
  27 wq:hp_default                   3  0.000   476/ 1500 243 (243)  w:sem  7
  36 wq:SPI1                      3827 19.168   672/ 1244 254 (254)  READY  7
  41 wq:I2C2                         0  0.000   368/ 1244 247 (247)  w:sem  7
  46 wq:I2C3                        66  0.424   748/ 1244 246 (246)  READY  7
  48 wq:SPI5                         0  0.000   368/ 1244 250 (250)  w:sem  7
  55 wq:SPI4                        48  0.339   536/ 1244 251 (251)  READY  7
  72 sensors                       492  2.629  1328/ 1964 238 (238)  w:sem 11
  74 commander                     206  0.763  1624/ 3212 140 (140)  READY  6
  75 commander_low_prio              0  0.000   560/ 2996  50 ( 50)  w:sem  6
  82 mavlink_if0                   879  3.562  1648/ 2532 100 (100)  READY  4
  83 mavlink_rcv_if0                58  0.254  1424/ 2836 175 (175)  w:sem  4
 121 gps                            41  0.254  1008/ 1516 209 (209)  w:sem  4
 153 mavlink_if1                   358  1.102  1648/ 2484 100 (100)  w:sig  4
 154 mavlink_rcv_if1                68  0.339  1336/ 2836 175 (175)  w:sem  4
 166 ekf2                         1096  6.276  4536/ 6572 239 (239)  w:sem  4
 170 navigator                      20  0.169   888/ 1764 105 (105)  w:sem  4
 188 logger                         91  0.508  1312/ 3644 234 (234)  w:sem 24
 191 log_writer_file                 0  0.000   376/ 1164  60 ( 60)  w:sem 24

Processes: 27 total, 8 running, 19 sleeping, max FDs: 54
CPU usage: 39.10% tasks, 1.61% sched, 59.29% idle
DMA Memory: 5120 total, 1024 used 1024 peak
Uptime: 21.213s total, 12.277s idle
nsh> sd_bench
INFO  [sd_bench] Using block size = 4096 bytes, sync=0
INFO  [sd_bench]
INFO  [sd_bench] Testing Sequential Write Speed...
INFO  [sd_bench]   Run  0:   478.79 KB/s, max write time: 19 ms (= 210.53 KB/s), fsync: 6 ms
INFO  [sd_bench]   Run  1:   199.40 KB/s, max write time: 965 ms (=   4.15 KB/s), fsync: 5 ms
INFO  [sd_bench]   Run  2:   481.35 KB/s, max write time: 13 ms (= 307.69 KB/s), fsync: 4 ms
INFO  [sd_bench]   Run  3:   484.63 KB/s, max write time: 14 ms (= 285.71 KB/s), fsync: 4 ms
INFO  [sd_bench]   Run  4:   339.96 KB/s, max write time: 381 ms (=  10.50 KB/s), fsync: 5 ms
INFO  [sd_bench]   Avg   :   395.08 KB/s
nsh>

This PR with NO d-cache
PID COMMAND                   CPU(ms) CPU(%)  USED/STACK PRIO(BASE) STATE FD
   0 Idle Task                   10738 45.292   284/  748   0 (  0)  READY  3
   1 hpwork                          0  0.000   344/ 1780 249 (249)  w:sig  3
   2 lpwork                         23  0.169   580/ 1780  50 ( 50)  w:sig  8
   3 init                          979  0.000  1728/ 2604 100 (100)  w:sem  3
   4 wq:manager                      2  0.000   808/ 1172 244 (244)  w:sem  7
 197 top                           549  4.240  1560/ 1884 255 (255)  RUN    3
  17 dataman                        82  0.000   752/ 1180  90 ( 90)  w:sem  4
  20 wq:lp_default                  25  0.084   856/ 1500 205 (205)  READY  7
  22 wq:I2C1                       167  0.678   748/ 1244 248 (248)  READY  7
  27 wq:hp_default                   5  0.000   632/ 1500 243 (243)  READY  7
  36 wq:SPI1                      5902 24.173   672/ 1244 254 (254)  READY  7
  41 wq:I2C2                         0  0.000   368/ 1244 247 (247)  w:sem  7
  46 wq:I2C3                       116  0.508   748/ 1244 246 (246)  READY  7
  48 wq:SPI5                         0  0.000   368/ 1244 250 (250)  w:sem  7
  55 wq:SPI4                        85  0.424   536/ 1244 251 (251)  READY  7
  72 sensors                       776  3.223  1172/ 1964 238 (238)  w:sem 11
  74 commander                     468  1.272  1576/ 3212 140 (140)  READY  6
  75 commander_low_prio              0  0.000   560/ 2996  50 ( 50)  w:sem  6
  82 mavlink_if0                  1577  4.495  1648/ 2532 100 (100)  READY  4
  83 mavlink_rcv_if0               112  0.254  1424/ 2836 175 (175)  READY  4
 121 gps                            75  0.339  1136/ 1516 209 (209)  w:sem  4
 153 mavlink_if1                   780  1.357  1648/ 2484 100 (100)  w:sig  4
 154 mavlink_rcv_if1               137  0.424  1424/ 2836 175 (175)  w:sem  4
 166 ekf2                         1929  8.481  4536/ 6572 239 (239)  w:sem  4
 170 navigator                      60  0.339   888/ 1764 105 (105)  w:sem  4
 190 log_writer_file                 0  0.000   376/ 1164  60 ( 60)  w:sem 24
 188 logger                        209  0.932  1312/ 3644 234 (234)  w:sem 24

Processes: 27 total, 11 running, 16 sleeping, max FDs: 54
CPU usage: 51.40% tasks, 3.31% sched, 45.29% idle
DMA Memory: 5120 total, 1024 used 1024 peak
Uptime: 25.782s total, 10.739s idle
nsh> sd_bench
INFO  [sd_bench] Using block size = 4096 bytes, sync=0
INFO  [sd_bench]
INFO  [sd_bench] Testing Sequential Write Speed...
INFO  [sd_bench]   Run  0:   331.20 KB/s, max write time: 368 ms (=  10.87 KB/s), fsync: 4 ms
INFO  [sd_bench]   Run  1:   386.68 KB/s, max write time: 272 ms (=  14.71 KB/s), fsync: 5 ms
INFO  [sd_bench]   Run  2:   450.55 KB/s, max write time: 13 ms (= 307.69 KB/s), fsync: 4 ms
INFO  [sd_bench]   Run  3:   324.16 KB/s, max write time: 519 ms (=   7.71 KB/s), fsync: 5 ms
INFO  [sd_bench]   Run  4:   448.22 KB/s, max write time: 17 ms (= 235.29 KB/s), fsync: 4 ms
INFO  [sd_bench]   Avg   :   388.15 KB/s
nsh>


Allow Mbed OS version selection

Allow user to select which version of Mbed OS to use:

master branch
latest stable
specific tag

Not sure that it's really necessary, and it will make the post-gen hook a lot more complex.


The option `qt.style' does not support nested options

I'm trying to use this but I'm getting this error:
error: The option `qt.style' in module `/nix/store/b2xy0gk6sd3fc8zamarfzach5f3wpkvi-source/nixos/modules/config/qt.nix' would be a parent of the following options, but its type `null or one of "adwaita", "adwaita-dark", "adwaita-highcontrast", "adwaita-highcontrastinverse", "bb10bright", "bb10dark", "breeze", "cde", "cleanlooks", "gtk2", "kvantum", "motif", "plastique"' does not support nested options.
        - option(s) with prefix `qt.style.catppuccin' in module `/nix/store/wqmfkfd7kcsa935ky2vf94x5cjz3r2vq-source/modules/home-manager/kvantum.nix'

I am getting this error, is there a fix ?

I got this because I wasn't importing my home manager.
In my current configuration I setup a user in users.nix and import the nix file from users.nix, not from flake directly

I'm having the same problem - @jerbaroo did you get a fix?
importing home manager doesnt help
also see this thread in the catppuccin discord

For me the issue was that I had imported catppuccin.homeManagerModules.catppuccin directly in home-manager.nixosModules.home-manager instead of putting it inside home-manager.users.<name>.
nixpkgs.lib.nixosSystem {
    catppuccin.nixosModules.catppuccin

    home-manager.nixosModules.home-manager {
-        imports = [
-            catppuccin.homeManagerModules.catppuccin
-        ];
+        home-manager.users.foo = {
+            imports = [
+                catppuccin.homeManagerModules.catppuccin
+            ];
+        };
    }
}


SDK3 + Norwegian

Added Norwegian localization and updated app to SDK3

ID Lock 202 Multi is not added as a driver in this app.
The original app is in the Homey App Store (SDK2)
To install this app you need to clone the repo and install the app via CLI

thanks @runely - i merged to my master. Would be great to get this out to the official app and the Homey Community.

I have some commits coming soon. The work I did in this PR does work on already connected devices, but unfortunately not on new devices..


Checkelement with ignored class, throws error with $(element).valid()

I will explain my software need first:
I have a form, inside this form i got some listings, like (add user fieldset), those validated users get added to the form with hidden fields... Its working without problem... I set those inputs as .ignoreMe and on ignore setting i put this class, wonderfull!
However i need some of the to have a checkbox or radiobutton and this is the problem...
Now i will explain the problem:
Those fieldsets are dinamically generated, so i validate the form on submit, and i validate those fields .ignoreMe on user add, or something else... In the time i need it... But if i put a checkbox or a radio the $("#checkbox").valid() throws an error:
Uncaught TypeError: Cannot read property 'name' of undefined jquery.validate.js:723
So i debugged the jquery.validate to find the problem... And the problem is the line 729 inside the method:
validationTargetFor: function( element ) {
			// if radio/checkbox, validate first element in group instead
			if ( this.checkable(element) ) {
				element = this.findByName( element.name ).not(this.settings.ignore)[0];
			}
			return element;
		},

Aparently the line 729 returns no element because the same element is on ignore setting, BUT i am making a manual validation of this field, so it throws the error that the element is undefined...
So i commented the line 729, and its working wonderfull, everything is working, the sublists, the forms, the checkboxes and radios on the normal form and on the sublist form... I dunno why when i removed the .not() from the line 729 it gives me another errors:
Exception occurred when checking element undefined, check the 'required' method. TypeError {stack: (...), message: "Cannot call method 'toLowerCase' of undefined"} jquery.validate.js:570
Uncaught TypeError: Cannot call method 'toLowerCase' of undefined jquery.validate.js:1001
But as i got something like 7 hours debugging and trying to solve the problem i got the easy way for now, BUT maybe the more experienced could get the job done more easily or elegantly...
Tnx for your time.

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


HMAC, HKDF in Move

Move API to derive keys on-chain using hkdf. See hkdf_generate_from_ikm in fastcrypto https://www.rfc-editor.org/rfc/rfc5869
Move API to verify the message and its Message Authenticated Code
Q: how is key being passed in?

Added only hmac for now


Fix partial update coordinates

The addresses are little endian. CircuitPython 8.1.0+ is needed for this to work. (https://github.com/adafruit/circuitpython/pull/7891)

Should https://github.com/adafruit/Adafruit_Blinka_Displayio/blob/main/displayio/_epaperdisplay.py be updated as well?

Ya, but probably not urgent since it is just a stub.


some "mistakes" with this docker image

It seems that there are some mistakes with this docker image so far  .
The following mistakes  are  in script file  "/openvas-check-setup"  inside docker image
Mistake 1:
The code if [ ! -e $CAFILE ]    does not work , it should be  if [ ! -e "$CAFILE" ]  .
Mistake 2:

CAFILE=openvassd -s 2>>$LOG | grep ca_file | sed -e "s/^ca_file = //"

openvassd -s will not show out cafile  , so CAFILE is Null ,  but they are there (/var/lib/openvas/CA/) in fact .
so it will throw out error like this : https://github.com/mikesplain/openvas-docker/issues/262
Mistake 3:
The verison of  OpenVAS Manager inside docker image is 7.0.3,
but "/openvas-check-setup" script will need "6.1"

ERROR: OpenVAS Manager too old or too new: 7.0.3
FIX: Please install OpenVAS Manager 6.1.

This.
I get the error referenced in #262 . Im still trying to figure out a workaround.


Fix name confusion

i think that the bot takes in every single message in a channel, and so multiple bots taking in all are the culprit here.
What I think we need is to be able to have the bot only process messages that are directed @ it.

i think that the bot takes in every single message in a channel, and so multiple bots taking in all are the culprit here.
What I think we need is to be able to have the bot only process messages that are directed @ it.

The magic comes from that not being the case. We are trying to build a multi-agent simulation, so this is the problem we are trying to solve. Right now we have a shouldRespond handler that determines if the bot should respond, using a cheap model. If so, we respond. It's working pretty well, and it follows our ethos that Elizas are "real agents" that strive to mimic human behavior.
I think it's something more simple and technical, but according to the agents, every other agent should just be a user.


Added a sticky header

Description

Made a sticky header using only CSS right now.

Attach Screenshot

Create separate branch next time.


vcpkg doesn't automatically use the x64 triplet with a 64-bit cmake generator & compiler?

Hi,
I use cmake-gui, and select the Visual Studio 16 - 2019 generator. This generator defaults to x64. I then select the vcpkg.cmake file as toolset file, according to the vcpkg documentation.
When the configuring a project in CMake, I get a warning
CMake Warning at C:/Users/Patrik/vcpkg/scripts/buildsystems/vcpkg.cmake:104 (message):
  There are no libraries installed for the Vcpkg triplet x86-windows.
Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.16/Modules/CMakeDetermineSystem.cmake:93 (include)
  CMakeLists.txt:5 (project)

and subsequently no packages are found (because indeed, I don't have any packages installed for the x86-windows triplet).
I can "fix" this by changing the VCPKG_TARGET_TRIPLET to x64-windows and re-running configure.
However, I believe this step has never been necessary before, or has it? Previously, vcpkg would recognise that CMake is using a 64-bit generator and has detected a 64-bit cl.exe and would then automatically set/use the x64-windows triplet.
I updated lots of things recently (vcpkg: pulled latest master, yesterday; VS: 16.4.1; cmake: 3.16.1). But I am pretty sure that previously, I never needed to manually adjust the triplet to x64-windows.
My guess is that the interaction of any of these three components introduced a bug / regression recently?
Thanks.

Hi @patrikhuber thanks for posting this issue.
It's duplicate to #4908. Please refer to this issue.

Since the current behavior is intended. I close this issue now.

Hi @NancyLi1013,
I don't think that #4908 is a duplicate. In #4908, the poster forgets to specify the 64-bit options in the CMake generator.
However, in the VS 2019 CMake Generator, x64 is the default.
So my question to you is: Given a 64-bit CMake Generator (e.g. VS 2019 - x64), is it intended behaviour that vcpkg will select and try to use the x86 triplet, and that the user then subsequently manually has to set VCPKG_TARGET_TRIPLET to x64-windows?
Has this always been the case? It feels to me like this step is unnecessary and was not needed in the past.

Hi @patrikhuber thanks for your feedback.
I have known this issue now. Since VS 2019 has supported x64 by default. This case is different from that in #4908.
Sorry for my mistake.
We need to double confirm about this.

@dan-shaw
Could you help take a look?

@patrikhuber, thanks for bringing this up!
Currently this issue fixed by PR https://github.com/microsoft/vcpkg/pull/9816, could you get latest source and try again? Let me know if it still be a problem for you.


Add a "how to use the fixed header component" section to the docs

Since position: fixed will cause the content below to be rendered under the header, we should show how to use a .mt6 or .h1 element to counteract that behavior so things align as we might expect.

Hi, just wanted to check, what is the best practice for this? And also, when adding class="fixed" (following e.g. http://tachyons.io/components/nav/fixed-semi-transparent/index.html) to my header, I get a vertical position of 16px above my header, and really can't work out why?


A problem about the landmarks output

Hello, thank you for sharing your code. But I have a question, how to get the coordinates of the 68
key-points on 2D input images? Thank you!

@yyssmm Those coordinates are listed in the Data/uv_kpt_ind.txt file.

@wungemach 是说关键点在uv上的位置是固定的吗

@wungemach  To my understanding, the final output of PRNet is the U-V position map which includes 3-D coordinate of vertex corresponding to face model. How can 2-D landmarks be obtained through the position map?

@wungemach To my understanding, the final output of PRNet is the U-V position map which includes 3-D coordinate of vertex corresponding to face model. How can 2-D landmarks be obtained through the position map?

The generated U-V position is (256,256,3)，the fix postion in './Data/uv-data/uv_kpt_ind.txt' directly defines the face keypoints in texture image. And, the 3D/2D landmarks for the input image can be obtained from the third dimension U-V position, that is
pos = prnet.forward()
idx = np.loadtxt('uv_kpt_ind.txt')
2D_kps = pos[idx[:,1],idx[:,0],:-1]
3D_kps = pos[idx[:,1],idx[:,0]]


[📑 Docs]: remove the Streetlights tutorial

What Dev Docs changes are you proposing?
We would like to remove the current Streelights tutorial and have it in four sections as part of the efforts to improve the AsyncAPI documentation.
Code of Conduct

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

@alequetzalli I see that the Streetlights tutorial is already deleted from the website. Should we close this issue?

oh good catch, thanks @akshatnema! 😅
yup!


CASMPET-5767 1.0 : DOCS: Fix typo in cert renewal step

Description
Fixing typo for csm 1.0.x docs
backporting to release/1.2 and main
Checklist Before Merging

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I don't have a JIRA.

/backport release/1.2

/backport main


Idea votes

We need to implement the mechanics of voting for ideas.
For developer role we should display:

A page with a list of pending ideas.
Page of the specific idea.

On the idea page, we display its description, and two buttons "Yes/No".
For the author of this specific idea and stuff, we also display the list of users, who have voted for/against this idea.
The development of this feature involves the creation of new Ops::Ideas::Vote operation.
Also we need dashboard::ideas controller to display ideas.
And also
  resources :ideas do
    resources :votes, only: [:index]
      member do
        put :up
        put :down
      end
    end
  end

Keep in mind, that we should protect system. E.g. when someone has voted - we should check that, to prevent voting from the same user.

Let's send notification about the new idea to the #ideas Slack channel


On todo-databinding, remove logic from layout files and use Custom Setter

I read the previous discussion #72 and understand the approach, but most layout logic could be replaced with @BindingAdapter  annotation and people could see their power, one example
<TextView
        android:layout_width="match_parent"
        android:layout_height="match_parent"
<EMAIL_ADDRESS>        android:textAppearance="?android:attr/textAppearanceMedium"
<EMAIL_ADDRESS>? View.VISIBLE : View.GONE}" />

could be replaced with
<TextView
        android:layout_width="match_parent"
        android:layout_height="match_parent"
<EMAIL_ADDRESS>        android:textAppearance="?android:attr/textAppearanceMedium"
<EMAIL_ADDRESS>
and
public class VisibilityBinding {
    @BindingAdapter({
            "visibility_value"
    })
    public static void bindVisibility(View view, boolean visible) {
        bindVisibility(visible, View.VISIBLE, View.GONE);
    }

    @BindingAdapter({
            "visibility_value",
            "visibility_off"
    })
    public static void bindVisibility(View view, boolean visible, int visibilityOffValue) {
        bindVisibility(visible, View.VISIBLE, visibilityOffValue);
    }

    @BindingAdapter({
            "visibility_value",
            "visibility_off",
            "visibility_on"
    })
    public static void bindVisibility(View view, boolean visible, int visibilityOffValue, int visibilityOnValue) {
        view.setVisibility(visible ? visibilityOnValue : visibilityOffValue);
    }

}

could even create binding app:hidden app:invisible first one use View.GONE for false value, second one use View.INVISIBLE that it's a better naming, and the only logic xml have it's negation mark !
<TextView
        android:layout_width="match_parent"
        android:layout_height="match_parent"
<EMAIL_ADDRESS>        android:textAppearance="?android:attr/textAppearanceMedium"
        app:hidden="@{!stats.showStatus}"

public class VisibilityBinding {
    @BindingAdapter({
            "hidden"
    })
    public static void bindHiddenVisibility(View view, boolean hidden) {
        view.setVisibility(hidden ? View.GONE : View.VISIBLE);
    }

   @BindingAdapter({
            "invisible"
    })
    public static void bindInvisibleVisibility(View view, boolean invisible) {
        view.setVisibility(hidden ? View.INVISIBLE : View.VISIBLE);
    }
}

WDYT guys?

Nice!
It makes the property easier to read and less error prone, however I'm not sure it's worth it for the sample. We could add a "Variations" section to the READMEs linking to issues/prs/branches like this one.
Thoughts?

i think that a "Variations" ™ section in the readme with complex branches it's worth than the use of custom setter, IMHO android databinding it's more that pass objects instances that fill a layout file with data  and update it on value changes.
@BindingAdapter  and @BindingMethod are part of android databinding framework and should be explained here, a project that aims to serve as an example of good practice using databinding.
I know that could be hard to understand the magic behind, but what better than an example in which all the Android community see how it work 😉
in resume i like to see here, no matter if it's in the main todo-databinding branch or in a todo-databinding/custom-setters or whatever name you want. i could do a PR in the way @JoseAlcerreca you finally decide

After talking offline, we decided to add a simple BindingAdapter that toggles visibility between GONE and VISIBLE. Looking forward to your PR, thanks!


No able to split the dataset Using HW2GRAPH and getting nx_graphs as empty

Did you figure it out? I have the similar issue.

Did you figure it out? I have the similar issue.

yes, you have to make changes in config.py file:
https://github.com/AICPS/hw2vec/blob/master/hw2vec/config.py
unzip the dataset from assets folder and give the path of toy dataset

Thanks for your reply. I have figured this problem out and I can run hw2vec now, but when I try to generate a SDF from a RISC-V design that contain multipple .v files. The TopModule file may lose some module, or some module lose some input or output, resulting in a empty of SDF graph. Did your have the same problem?
Best regards
Peng

发件人: Al -Hussain Shaikh @.>
发送时间: 2024年6月7日 2:11
收件人: AICPS/hw2vec @.>
抄送: PWang0220 @.>; Comment @.>
主题: Re: [AICPS/hw2vec] No able to split the dataset Using HW2GRAPH and getting nx_graphs as empty (Issue #21)
Did you figure it out? I have the similar issue.
yes, you have to make changes in config.py file:
https://github.com/AICPS/hw2vec/blob/master/hw2vec/config.py
unzip the dataset from assets folder and give the path of toy dataset
―
Reply to this email directly, view it on GitHubhttps://github.com/AICPS/hw2vec/issues/21#issuecomment-2153120854, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAC4O4VCVHP5TVRUQ4ZR6UDZGCQ5XAVCNFSM6AAAAABAI6AERSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTGEZDAOBVGQ.
You are receiving this because you commented.Message ID: @.***>

Thanks for your reply. I have figured this problem out and I can run hw2vec now, but when I try to generate a SDF from a RISC-V design that contain multipple .v files. The TopModule file may lose some module, or some module lose some input or output, resulting in a empty of SDF graph. Did your have the same problem? Best regards Peng
…
________________________________ 发件人: Al -Hussain Shaikh @.> 发送时间: 2024年6月7日 2:11 收件人: AICPS/hw2vec @.> 抄送: PWang0220 @.>; Comment @.> 主题: Re: [AICPS/hw2vec] No able to split the dataset Using HW2GRAPH and getting nx_graphs as empty (Issue #21) Did you figure it out? I have the similar issue. yes, you have to make changes in config.py file: https://github.com/AICPS/hw2vec/blob/master/hw2vec/config.py unzip the dataset from assets folder and give the path of toy dataset ― Reply to this email directly, view it on GitHub<#21 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAC4O4VCVHP5TVRUQ4ZR6UDZGCQ5XAVCNFSM6AAAAABAI6AERSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTGEZDAOBVGQ. You are receiving this because you commented.Message ID: @.***>

No, I didn't get that problem.

Thanks for your reply. I have figured this problem out and I can run hw2vec now, but when I try to generate a SDF from a RISC-V design that contain multipple .v files. The TopModule file may lose some module, or some module lose some input or output, resulting in a empty of SDF graph. Did your have the same problem? Best regards Peng
…
________________________________ 发件人: Al -Hussain Shaikh @.> 发送时间: 2024年6月7日 2:11 收件人: AICPS/hw2vec @.> 抄送: PWang0220 @.>; Comment @.> 主题: Re: [AICPS/hw2vec] No able to split the dataset Using HW2GRAPH and getting nx_graphs as empty (Issue #21) Did you figure it out? I have the similar issue. yes, you have to make changes in config.py file: https://github.com/AICPS/hw2vec/blob/master/hw2vec/config.py unzip the dataset from assets folder and give the path of toy dataset ― Reply to this email directly, view it on GitHub<#21 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAC4O4VCVHP5TVRUQ4ZR6UDZGCQ5XAVCNFSM6AAAAABAI6AERSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTGEZDAOBVGQ. You are receiving this because you commented.Message ID: @.***>

If you are getting the problem you can check my repo:
https://github.com/alhussain-shaikh/HardwareTrojanDetection-


♻(backend) fix access rights on the invitations API endpoint

Purpose
Only users who have the rights to manage accesses on a document should be allowed to see and manipulate invitations on this document.
Other users should be able to see access rights on the document but only when the corresponding user/team has actually been granted access, not during invitation.
Proposal
Refactor the invitation API endpoint to fix this issue concerning access rights on invitations.
As advised by @qbey, I took this refactoring opportunity to move any code related to permissions on invitations from the serializer to a permission class.
Tests on the invitation API endpoint were copied a bit too fast from https://github.com/numerique-gouv/people and did not respect the code style and testing strategy used in this project so I normalized them while modifying them to fix them following changes in the API code.

@qbey @AntoLC thank you for the fast reviews!
Shippiiiiing :ship:


[typespec - pr] Pipeline tries to validate all specs

In azure-rest-api-specs-pr, the "typespec - pr" pipeline tries to validate all specs, not only the spec changed in my PR:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2918677&view=logs&j=2063e0fe-a0a2-55e0-61f7-89c6b872aac9&t=9960aa89-c013-56d4-0ce8-0421b4283180&l=1112
This pipeline seems to work correctly in azure-rest-api-specs.
It looks like the pipeline didn't even run git diff, which suggests either the source or target branch was empty.
Please also update the scripts to output more diagnostic information when determining which specs to validate.  I would be curious what the script thinks is the "git diff" in this case.

Seems to be fixed in latest version


Acrylic Broken

Windows Terminal version
1.13.10336.0
Windows build number
Microsoft Windows [Version 10.0.19044.1503]
Other Software
No response
Steps to reproduce

Install The Latest Version Of Windows Terminal Preview On Windows 10.
Boom, Title bar Acrylic Broken

Expected Behavior
Acrylic On Title Bar Works
Actual Behavior
Acrylic Title Bar Very White

Could you share your settings.json file?
Does acrylic work anywhere else in the OS?

In case it's not a coincidence, it could be an AMD driver issue.

@zadjii-msft I've been facing the same issue since the v1.13.10336 release of Terminal Preview yesterday. The acrylic has stopped working inside Terminal Preview, and works fine everywhere else in the system.
I have the "useAcrylic" set to True under "defaults" of "profiles" in the settings.json, and it used to work just fine prior to this update.
Attaching my settings.json here (attached as a TEXT file since GitHub doesn't seem to support JSON file uploads: settings.txt

@zadjii-msft This issue resolved itself after a restart. Not sure how, but I don't have the problem anymore.

Huh. Weird. Well, hopefully it was just a one off glitch 😅

@zadjii-msft I've been facing the same issue since the v1.13.10336 release of Terminal Preview yesterday. The acrylic has stopped working inside Terminal Preview, and works fine everywhere else in the system.
I have the "useAcrylic" set to True under "defaults" of "profiles" in the settings.json, and it used to work just fine prior to this update.
Attaching my settings.json here (attached as a TEXT file since GitHub doesn't seem to support JSON file uploads): settings.txt

That Removed All Acrylic For Me

Wanted to report that this issue happens to me as well. I have "useAcrylic": true under defaults, and "useAcrylicInTabRow": true, as well. The outcome is that the acrylic effect is there, but the tab row is significant brighter/whiter than previous versions.
Also, setting "theme": "dark" doesn't change the tab row color - still the same bright white.
I'm using a laptop with Intel CPU/GPU and NVIDIA GPU. By default It's Intel GPU to render.

Maybe It's NVIDIA Issue

Maybe It's NVIDIA Issue

No, it's not. I already clarified that it is using Intel GPU to render. Plus, this problem doesn't exist in any previous versions - nor in any other apps using acrylic - on my computer.
Don't say it is an Intel issue then - I hope this thread doesn't go from blaming AMD to blaming NVIDIA to blaming Intel... That would be a little excessive ;P

Sorry I Didn't see that

Drop-Down Acrylic Works

Title Bar Acrylic Actually Still Works, Just Very White

Can I get a screenshot? I wanna know exactly what I'm looking for here. Light theme + acrylic titlebar does seem... off... in Windows 10, but I'm not sure that's what you're reporting here.

That's exactly the kind of thing I'm looking for. That's great, thanks!

I have The Exact Same Thing Important Parts, Here is An Image Also:

Also Even If The Thing behind The Terminal Is Black, It Is Still White.

system: dark. terminal: dark, 1.12:

system: dark. terminal: dark, 1.13:

wait, how did that happen?
I was just messing around trying to screenshots on Win10, and that first 1.12 SS looks like it has the titlebar partially visible through the acrylic or something. I didn't actually seen that but clearly the SS grabbed it.
Maybe that's what's affecting this. Maybe there's a weird DWM interaction between the system caption buttons. the transparent BG, and HostBackdropAcrylic

OS: light, terminal: system. 1.12

OS: light, terminal: system. 1.13

OS: light, terminal dark 1.12

OS: light, terminal dark 1.13

That's what it is. 🤦♂

Regressed here: #12326 specifically: https://github.com/microsoft/terminal/pull/12326/files#diff-42b8e1723f803ad4ede2b8ca7547b6d2f9e3c12dd764a30e0789f379641e3b19
https://github.com/microsoft/microsoft-ui-xaml/blob/9052972906c8a0a1b6cb5d5c61b27d6d27cd7f11/dev/CommonStyles/Common_themeresources.xaml#L47
<SolidColorBrush x:Key="ApplicationPageBackgroundThemeBrush" Color="{ThemeResource SystemColorWindowColor}" />

So we're clearly evaluating ApplicationPageBackgroundThemeBrush the same as the OS's ApplicationPageBackgroundThemeBrush, not the actual theme at runtime. This is gonna technically be the same thing as #3917, but way more impactful

I wonder if this is because we're doing the titlebar acylic brush creation manually. We're creating the acrylic brush based on the color that's already in TabViewBackground, which at this time is probably the light version of the resource - we haven't set up the RequestedTheme yet.
The dumb solution would be to set RequestedTheme earlier, but that won't fix the hot-reload scenario here. We could theoretically manually re-resolve ApplicationPageBackgroundThemeBrush on a hot-reload, but that seems bodgy.
I don't think that would fix the pane brush either.

Note to self: TitlebarControl's BG is also set to TabViewBackground. That may also have something to do with it. I doubt we can just bind the titlebar's BG to the content's BG

Hokay, I've spent more than enough time on this for now.
Something weird is definitely going on here. I'd like to have a better solution, but I don't. dev/migrie/b/12356-attempt-2 has the latest state of my research into this. Creating a string literal xaml brush, parsing it, inserting it into the page's resources, then examining that brush's color at runtime worked, but only after a call to Dispatcher.RunAsync, so that it happened on a subsequent pass, after the Create call finished. That's mental.
I'm going with the hacky fix, which is in 82dd0e7c4. Just manually set the brush color for now. This is BODGY but hey, it's a good enough hotfix.

Hokay, I've spent more than enough time on this for now.
Something weird is definitely going on here. I'd like to have a better solution, but I don't. dev/migrie/b/12356-attempt-2 has the latest state of my research into this. Creating a string literal xaml brush, parsing it, inserting it into the page's resources, then examining that brush's color at runtime worked, but only after a call to Dispatcher.RunAsync, so that it happened on a subsequent pass, after the Create call finished. That's mental.
I'm going with the hacky fix, which is in 82dd0e7. Just manually set the brush color for now. This is BODGY but hey, it's a good enough hotfix.

How Do I Use This Fix?

The fix was merged in #12460, which we haven't shipped yet. When a build with that fix is released, the bot will come through and ping this thread.
For now, a workaround would be to set your OS theme to match the Terminal theme. (e.g. set the OS to Dark theme)


[push mode] container width not updated when sidebar content changes

Hi, I have a problem using the sidebar in "push" mode: if I change the sidebar's content, because it is dinamically generated, the width of the sidebar container is not updated.
Here is a simple Angular 2 component that shows the problem.
import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  template: `

            I am a growing div

        <ng-sidebar-container>

            <ng-sidebar #sidebar
                [opened]="true"
                [mode]="_mode"
                [position]="'right'"
                [closeOnClickOutside]="false">

                <input type="checkbox" (click)="_toggleMode()" checked="true"> Push mode

                    <button (click)="_changeText()">Change content</button>

{{_content}}

	    </ng-sidebar>

        </ng-sidebar-container>

  `
})
export class AppComponent {
  _mode = 'push';
  _content = 'Some kind of a long content like Lorem Ipsum';

  _toggleMode() {
      if (this._mode === 'over') this._mode = 'push';
      else this._mode = 'over';
  }

  _changeText() {
      if (this._content === 'Simple content')
          this._content = 'Some kind of a long content like Lorem Ipsum';
      else
          this._content = 'Simple content';
  }
}

Clicking on the "change content" button the size of the growing div will not be updated (clicking 2 times on the checkbox "push mode", changing it to "over" and then to "push" again, will "resolve" the problem).
Using the Chrome's inspector tool I saw that there is a

with generated margins. Those not-updated-margins seem to be problem's cause.
Waiting for your reply,
Davide
PS beside that little issue, I think that your Sidebar is great!! :+1: thank you for sharing!

Thanks for reporting this, and also digging into it a little. You're right that the margins aren't automatically updated, but I'll need to think about how to handle that.

Ok, thanks! I'll wait
Regards,
Davide

I decided to add a triggerRerender() function to the sidebar that can be manually called to trigger a re-render for the container, which should solve this issue in a somewhat roundabout way. I wanted to avoid using something like a MutationObserver since it doesn't support IE 10, and it also might be detrimental to performance if the sidebar has a lot of stuff inside it.


Pleco - like app for other languages

Just an idea that occured to me, and a little unrelated to what we're working on right now. While I'm sure that there are many dictionary apps around, the ability to, for example, create flashcards automatically, and combine other learning tools into one place (e.g. document reader) is quite a nice one.

bit out of scope


kelda: Remove kelda.hostIP

This commit removes the kelda.hostIP reference that allows containers
to reference their public IP via their environment variables. The
feature is extremely hard to implement on Kubernetes, and was only used
by the Spark blueprint.
Containers that need this feature should query their public IP at
runtime using a service such as checkip.amazon.com, or pass containers a
floating IP (or DNS name backed by a floating IP) and use placement
rules to ensure the container is scheduled at that floating IP.

Can you also remove the reference to hostIP in the example in the docs? http://docs.kelda.io/#Container

I think removing it from the JSDoc is sufficient (https://github.com/kelda/kelda/pull/1379/files#diff-3f91f27ca724b47373bd64a690860984L997)

Oh, yes, it definitely is! My bad 😀


Method signatures containing references to properties of constrained generic types are resolving through the constraint instead of the supplied type argument

TypeScript Version: nightly (2.2.0-dev.20161203)
I currently find it somewhat hard to precisely describe the issue/suggestion, but I believe this use case should demonstrate it clearly:
type MethodDescriptor = {
	name: string;
	args: any[];
	returnValue: any;
}

function dispatchMethod<M extends MethodDescriptor>(name: M['name'], args: M['args']): M['returnValue'];

type SomeMethodDescriptor = {
	name: "someMethod";
	args: [number, string];
	returnValue: string[];
}

// Currently, there's no compilation error on the the invalid second argument type and the
// return type is inferred as "any" instead of "string[]":
let result = dispatchMethod<SomeMethodDescriptor>("someMethod", ["hello", 35]);

The general idea here is that the types are used unconventionally: not to describe interfaces to run-time objects but as a way to "pack" a set of type arguments into an "object-like" compile-time entity. Perhaps this could be called something like "packed type arguments" or "type argument classes" or maybe "type argument schema containers"? I'm not sure.
Anyway, I was trying to write a general purpose dispatcher that can invoke a set of actions, and that seemed like a more elegant and type safe alternative to the more conventional:
function dispatchMethod<A extends any[], R>(name: string, args: A): R;

dispatchMethod<[number, string], string[]>("someMethod", ["hello", 35]); // <- errors as expected

A convenient way to illustrate this is that:
type MethodDescriptor = {
	name: string;
	args: any[];
	returnValue: any;
}

Represent a set of base constraints to a compile-time "object-like" entity containing type arguments, e.g.

Type of name must be assignable to string.
Type of args must be assignable to any[].
Type of returnValue must be assignable to any.

And:
type SomeMethod = {
	name: "someMethod";
	args: [number, string];
	returnValue: string[];
}

Is an "instance" of that "class", in the sense that it associates more specific types to the properties.
Now:
function dispatchMethod<M extends MethodDescriptor>(name: M['name'], args: M['args']): M['returnValue'];

References the types of properties on the type argument M.
Note that in this example both the types MethodDescriptor and SomeMethod are never actually applied to any concrete run-time object.
I know this may be seen as somewhat abstract so I hope this helps..

In combination with discriminated unions. It is possible to encapsulate the dispatcher in class such that only one "type schema" is actually needed for all supported actions:
type MethodDescriptor = {
	name: string;
	args: any[];
	returnValue: any;
}

class Dispatcher<M extends MethodDescriptor> {
	dispatch(name: M['name'], args: M['args']): M['returnValue'] {
		// ...
	}
}

type StoreMethodDescriptor = {
	name: "store";
	args: [string, number[], boolean];
	returnValue: void;
}

type OpenMethodDescriptor = {
	name: "open";
	args: [string];
	returnValue: void;
}

let dispatcher = new Dispatcher<StoreMethodDescriptor | OpenMethodDescriptor>();

// The correct argument types are inferred and validated automatically using the string literal
// as discriminant:
dispatcher.dispatch("store", ["mydata.txt", [1, 2, 3, 4], true]);

I realized there's a subtle assumption I introduced here in my union example.
Consider this case:
type MyType = { a: string; b: number } | { a: boolean; b: string[] };

function test(x: MyType['a'], y: MyType['b']) {}
test("hi", ["a", "b", "c"]); // <- currently doesn't error

Here, MyType['a'] is currently inferred as string | boolean and MyType['b'] is currently inferred as number | string[], so test("hi", ["a", "b", "c"]) currently doesn't error.
Is this the right way to go? maybe? However, the case I described was slightly different:
class Test<T extends { a: any; b: any }> {
	test(x: T['a'], y: T['b']) {
		// ...
	}
}
const instance = new Test<{ a: string; b: number } | { a: boolean; b: string[] }>;

Should both T['a'] and T['b'] be required to be consistent with a unique member of the union? I'm not completely sure. This could only be seen as a slight ambiguity of the syntax though. Perhaps if there was a helper syntax to "constrain" a type to a single member of a union, something like uniquely extends :
class Test<T extends { a: any; b: any }> {
	test<M uniquely extends T>(x: M['a'], y: M['b']) {
		// ...
	}
}
const instance = new Test<{ a: string; b: number } | { a: boolean; b: string[] }>;

The suggested keyword might not be great though.. perhaps there's a better one..

A simpler alternative to uniquely extends is to use something like specifies instead of extends for the main type parameter:
class Test<T specifies { a: any; b: any }> {
	test(x: T['a'], y: T['b']) {
		// ...
	}
}

const instance = new Test<{ a: string; b: number } | { a: boolean; b: string[] }>();

instance.test("hi", ["a", "b", "c"]); // <-- Errors due to the semantics of "specifies".

Although specifies can be a bit ambiguous as it might suggest the type argument can't be a union (in the sense it must be "specific"), I think the potential confusion is only minor, and the reduced complexity and increased user friendliness may be worth it.
Another advantage of specifies is that it may support future syntax that wouldn't be appropriate for extends. Anyway, the name best name I found so far for this is concept is type schemas, so specifies seems to go well with that.

The issue described in the original post is now fixed by #12770.

@ahejlsberg
Thanks! I'll grab the nightly build tomorrow and see if I can start making use of this new inference capability in my code.
If you find any of these additional ideas I mentioned here interesting feel free to make use of them in the future. They were originally meant as motivating examples. I'm not sure, though, whether I'm in a good position to figure out a whole proposal from them at this point. It would be interesting, perhaps, to first see what other people would do / want to do with these inference patterns and then try to come to some form of understanding what's the 'best' way to approach this.