Allow to configure port for SSH access

What would you like to be added:
Allow to configure SSH port for hosts
Why is this needed:
It's possible that nodes are behind the same public ip, but they are listening to different ssh port
Example cluster.yml:
hosts:
  - address: <IP_ADDRESS>
     port: 2022
  - address: <IP_ADDRESS>
     port: 2023
  ...

There are several ssh options already in the top host level. We could consider moving them under ssh::
hosts:
  - address: <IP_ADDRESS>
     ssh:
       port: 2022
       key_path: ~/.ssh/foo
       proxy_command: xyz

We could then pass that hash almost as-is to Net::SSH.start which would allow the use of any of the Net::SSH.start options:

:auth_methods => an array of authentication methods to try
:bind_address => the IP address on the connecting machine to use in establishing connection. (:bind_address is discarded if :proxy is set.)
:compression => the compression algorithm to use, or true to use whatever is supported.
:compression_level => the compression level to use when sending data
:config => set to true to load the default OpenSSH config files (~/.ssh/config, /etc/ssh_config), or to false to not load them, or to a file-name (or array of file-names) to load those specific configuration files. Defaults to true.
:encryption => the encryption cipher (or ciphers) to use
:forward_agent => set to true if you want the SSH agent connection to be forwarded
:global_known_hosts_file => the location of the global known hosts file. Set to an array if you want to specify multiple global known hosts files. Defaults to %w(/etc/ssh/ssh_known_hosts /etc/ssh/ssh_known_hosts2).
:hmac => the hmac algorithm (or algorithms) to use
:host_key => the host key algorithm (or algorithms) to use
:host_key_alias => the host name to use when looking up or adding a host to a known_hosts dictionary file
:host_name => the real host name or IP to log into. This is used instead of the host parameter, and is primarily only useful when specified in an SSH configuration file. It lets you specify an “alias”, similarly to adding an entry in /etc/hosts but without needing to modify /etc/hosts.
:keepalive => set to true to send a keepalive packet to the SSH server when there's no traffic between the SSH server and Net::SSH client for the keepalive_interval seconds. Defaults to false.
:keepalive_interval => the interval seconds for keepalive. Defaults to 300 seconds.
:keepalive_maxcount => the maximun number of keepalive packet miss allowed.
:kex => the key exchange algorithm (or algorithms) to use
:keys => an array of file names of private keys to use for publickey and hostbased authentication
:key_data => an array of strings, with each element of the array being a raw private key in PEM format.
:keys_only => set to true to use only private keys from keys and key_data parameters, even if ssh-agent offers more identities. This option is intended for situations where ssh-agent offers many different identites.
:logger => the logger instance to use when logging
:max_pkt_size => maximum size we tell the other side that is supported per packet. Default is 0x8000 (32768 bytes). Increase to 0x10000 (65536 bytes) for better performance if your SSH server supports it (most do).
:max_win_size => maximum size we tell the other side that is supported for the window.
:paranoid => either false, true, :very, or :secure specifying how strict host-key verification should be (in increasing order here). You can also provide an own Object which responds to verify. The argument given to verify is a hash consisting of the :key, the :key_blob, the :fingerprint and the :session. Returning true accepts the host key, returning false declines it and closes the connection.
:passphrase => the passphrase to use when loading a private key (default is nil, for no passphrase)
:password => the password to use to login
:port => the port to use when connecting to the remote host
:properties => a hash of key/value pairs to add to the new connection's properties (see Net::SSH::Connection::Session#properties)
:proxy => a proxy instance (see Proxy) to use when connecting
:rekey_blocks_limit => the max number of blocks to process before rekeying
:rekey_limit => the max number of bytes to process before rekeying
:rekey_packet_limit => the max number of packets to process before rekeying
:send_env => an array of local environment variable names to export to the remote environment. Names may be given as String or Regexp.
:timeout => how long to wait for the initial connection to be made
:user => the user name to log in as; this overrides the user parameter, and is primarily only useful when provided via an SSH configuration file.
:user_known_hosts_file => the location of the user known hosts file. Set to an array to specify multiple user known hosts files. Defaults to %w(~/.ssh/known_hosts ~/.ssh/known_hosts2).
:use_agent => Set false to disable the use of ssh-agent. Defaults to true
:verbose => how verbose to be (Logger verbosity constants, Logger::DEBUG is very verbose, Logger::FATAL is all but silent). Logger::FATAL is the default. The symbols :debug, :info, :warn, :error, and :fatal are also supported and are translated to the corresponding Logger constant.


integration test requires storage credentials

How AWS credentials should be provided for an integration test #114?

@dmzaytsev doesn't look like a bug to me, see http://www.yegor256.com/2014/11/24/principles-of-bug-tracking.html#5.-report-when-it-is-broken


Investigate hardening kafka message receive at the proxy

In #989 we found that if you send unexpected bytes at the proxy it could silently hang. We have introduced a hardcoded maximum frame size #997 which would prevent some particular circumstances where we can kill the connection if we receive a giant frame size in the first 4 bytes. However we are still vulnerable to things like clients telling us they want to send us N bytes then never progressing, or sending all but the last byte of a large frame and tying up server memory.
We should investigate what our options are for detecting if a MessageDecoder is not progressing, maybe we could time it out after N seconds of no progress.

+1 Kroxylicious could be internet facing.
in addition to the scenarios listed above, we should guard against a client that opens a connection and never sends any bytes.  we should timeout the connection.   we should also spot a client that sends bytes unreasonable slowly.


pip install fails for python 3

pip3 install fuzzy fails with error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
Ubuntu Xenial all build-dependencies installed and up to date.
System python 3.5.2
package installs fine with system python 2.7.12
fuzzy_python3_error.txt

Python 3 support was added in 1.2, which failed to release due to intermittent test failures. I just re-started the job and it seems to have succeeded now, so I expect to see 1.2 in PyPI soon. Please respond here if that doesn't correct the issue.

Ugh. Even though the test "passed", the deploy failed.

Okay. Latest re-tag of 1.2 succeeded and 1.2 is now in PyPI. Please test installation with that release and report back.

Installed, thank you!


Updated messaging docs & data types

Current dependencies on/for this PR:

main

PR #412   👈

This comment was auto-generated by Graphite.


Alignment issue between hamburger icon and title in drawer layout

Above image explains the problem very well.
Top screenshot is the one I took from the site and below screenshot is the one I took from my browser.

You've probably forgot to set doctype and such. I had the same problem until I came across this:
http://evileyegames.com/article/46-material-design-lite-mdl-fix-menu-icon-vertical-alignment
basically you need to make sure you have...
`<!doctype html>

`
at the top of your html

thanks a lot...
that solved my problem. why didn't i thought of that ???
anyways thanks...


Question: SQL Server "SQL Completion" how to hide database name?

I am using DBeaverEE 5.1.0, and when connecting to Microsoft SQL Server 2016 databases the IntelliSense will show the databases name, which I would like to suppress.  The database names in our environments are long and it makes the feature very difficult to use.
If there is currently no way to do this, is there a way I can default a wider window when the autocomplete comes up?
Example of results showing database name for "master" database when I specifically only specified schema in the query:

I have made sure "Use short object names" is selected, and it doesn't seem to help:

Unfortunately there is no such option at the moment.
I think we could suppress catalog name in FQ names by default.
Mark as FR.

Completion will be improved in 5.1.6.
This particular issue will be also fixed.

I installed 5.2.0 and this looks great.  Thank you so much for turning
these around so quickly.
On Sat, Aug 25, 2018 at 8:04 AM Serge Rider<EMAIL_ADDRESS>wrote:

Closed #3991 https://github.com/dbeaver/dbeaver/issues/3991.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/3991#event-1808971050, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AUOyvWCIOxQCgfCqtncqft2bpwQIdid9ks5uUT0wgaJpZM4V6n-4
.


Disable system fonts on Android (issue 18210)

To avoid introducing any inline "hacks" in the viewer-code this meant adding useSystemFonts to the AppOptions, which thus required some new functionality since the default value should be undefined given how the option is handled in the API; note this code.
Finally, also moves the definition of the development-mode window.isGECKOVIEW property to the HTML file such that it's guaranteed to be set regardless of how and when it's accessed.

/botio-linux preview

/botio integrationtest

/botio unittest

/botio integrationtest

Thank you for fixing this!


Document the meaning of metadata fields displayed in 'sample of failures' preview

I'm not sure how to interpret some of the metadata fields in the example below.
I don't know what version is in relation to and I can take a guess at value, result, pass_count and application_count but it would be good to have them documented.
The documentation (or a link to it) should be proximate to where the fields appear in the interface.

Noting that I wrote some descriptions for developers at https://pelican-backend.readthedocs.io/en/latest/tasks/checks/compiled-release.html
The meta keys should be standardized before being documented (open-contracting/pelican-backend#76).

I think https://github.com/open-contracting/pelican-frontend/issues/49 and https://github.com/open-contracting/pelican-frontend/issues/50 are better solutions to this, as their goal is to render this raw information in an intelligible way, and require less effort from the user (no need to click on a sample first).
I improved the naming of the meta keys for clarity, as part of https://github.com/open-contracting/pelican-backend/issues/76
Otherwise, for now, I added a documentation page (not linked from the UI). The keys are either clear, or can be learned once.


Failing to work with async data from API

Good day.
Please could you kindly assist. I'm failing to work with data asynchronously fetched from an API for the dropdown. It seems I can only work predefined data.
Not sure if I'm making a mistake or there's a special way I need to access the data.
Regards.

Hello there ! What is the problem exactly ?
Currently I have no .fromFuture constructor for the widget to autobuild after an async request. I will look into it and maybe I could add one.
What I would suggest is having a loading flag and keep on loading while your data is being fetched, after that you will have the data you need to populate the dropdown.

Thank you, I'll see if I can try that.
I'd been using set state to update the list variable once the data fetch is complete though the data then isn't available in the dropdown though I can print it in console.

Hmm well that's weird, updating the list and using setState should have updated the dropdown. Would you mind sharing a minimal code to see what is going on ?

Sure, please see below for the minimal version of the class where I'm using the code
`import 'package:dropdown_button2/dropdown_button2.dart';
import 'package:flutter/material.dart';
import 'package:font_awesome_flutter/font_awesome_flutter.dart';
import '../constants.dart';
import '../helpers/network_client.dart';
import '../libraries/custom_multiselect.dart';
import '../libraries/locations_search.dart';
import '../models/country.dart';
import '../pages/search_results.dart';
class SearchForm extends StatefulWidget {
final bool? filterText;
const SearchForm({Key? key, this.filterText}) : super(key: key);
@override
State createState() => _SearchFormState(filterText: filterText);
}
class _SearchFormState extends State {
bool isLoaded = false;
//Search items
List _locations = [];
@override
void initState() {
super.initState();
_searchCriteria();
}
void _searchCriteria() async {
NetworkClient client =
NetworkClient(path: '/search-criteria', method: 'get', parameters: {});
var data = await client.runRequest();
setState(() {
data['locations']['provinces'].forEach((e) {
locations.add(Country(
name: e['name'], id: 'Province${e['id']}', type: 'Province'));
});
});
}
@override
Widget build(BuildContext context) {
return Container(
padding: EdgeInsets.all(kPagePadding),
color: kPrimaryColor,
child: Column(
mainAxisAlignment: MainAxisAlignment.spaceEvenly,
children: [
Padding(
padding: const EdgeInsets.only(bottom: 8.0),
child: LocationsSearch(
searchFieldTextStyle: TextStyle(
height: kTextFieldStyleHeight,
),
items: _locations, // List
fieldToCheck: (c) {
return c.name;
},
itemBuilder: (country) {
return Padding(
padding: const EdgeInsets.all(0),
child: Container(
decoration: BoxDecoration(
borderRadius: BorderRadius.circular(0),
color: Colors.white,
),
child: Container(
decoration: BoxDecoration(
border: Border(
bottom: BorderSide(
color: Colors.grey.shade300,
),
)),
child: Padding(
padding: const EdgeInsets.symmetric(
vertical: 10,
horizontal: 10,
),
child: Row(
children: [
Expanded(
flex: 2,
child: Text(
country.name,
),
),
Expanded(
child: Text(
country.type,
textAlign: TextAlign.right,
style: TextStyle(
color: Colors.grey.shade500,
fontStyle: FontStyle.italic,
),
),
),
],
),
),
),
),
);
},
pickedItemBuilder: (country) {
return Container(
decoration: const BoxDecoration(
color: kPrimaryColor,
),
child: Padding(
padding:
const EdgeInsets.symmetric(horizontal: 8, vertical: 3),
child: Wrap(children: [
RichText(
text: TextSpan(
children: [
TextSpan(
text: country.name + ' ',
style: TextStyle(
color: Colors.white,
),
),
WidgetSpan(
child: Icon(
Icons.cancel,
color: Colors.white,
size: 14.0,
),
),
],
),
),
]),
),
);
},
onTapShowedItem: () {},
onPickedChange: (items) {},
onItemAdded: (item) {},
onItemRemoved: (item) {},
sortShowedItems: true,
sortPickedItems: true,
fuzzySearch: FuzzySearch.jaro,
itemsVisibility: ShowedItemsVisibility.onType,
showSelectAllButton: false,
showClearAllButton: false,
maximumShowItemsHeight: 200,
showedItemsBackgroundColor: Colors.white,
pickedItemsContainerMinHeight: 10,
),
),
],
),
);
}
}
`

Thanks for mentioning this ! There was currently a bug and the item list was not correctly rebuilding. The SDK has been also updated to 2.17.0 with the newest version of the library 2.3.0.

Thank you.


Reserve Radius oscillating

Context
2.0.1 mainnet swarm
Summary
When the reserve capacity was exceeded, the storage radius was expected to transition from 10 to 11.  Unfortunately, some of my nodes went into an oscillation between radius 10 and 11 and have yet to completely settle down.
Expected behavior
Transition should have gone once and stayed at the new level until a substantial change in the swarm reserve population happens.
Actual behavior
Storage radius bounces up and down even though the swarm chunk population is on a steady increase.
Possible solution
No idea at this time, but apparently the triggers for going up and going down are not very stable when at certain levels of reserve population.
Consider the ramifications of an increased reserve radius causing 1/2 of the chunks to be evicted and then the reserve radius going back down.   Those evicted chunks need to be recovered from somewhere, but the pullsync intervals are not reset, so the new radius 10 peers are not re-pulled causing the reserve to be incomplete until it transitions again back to 11.  As much as I hate the load on the swarm when pullsync intervals are reset, it definitely seems necessary when the reserve radius decreases.  But then, please don't fix that until the cause of the radius oscillation is determined and corrected!

I added additional logging to the "reserve radius" logs and see this:
"time"="2024-04-30 17:17:15.653076" "level"="info" "logger"="node/storer" "msg"="reserve radius decrease" "radius"=10 "count"=2068699 "threshold"=2097152
"time"="2024-04-30 17:21:01.485788" "level"="info" "logger"="node/storer" "msg"="reserve radius increase" "radius"=11 "evicted"=0 "target"=1

Now I think I need to get and log the current "reserve in radius" or whatever is triggering the failed eviction pass that results in the radius going back to 11.   And possibly what eviction actually caused it to drop back to 10, although I might actually have that log in place already.

  First note that the "new_size" definitely seems to be tracking the total reserve size, not the size within radius.     Wanted to evict just 1 chunk, but ended up evicting 207,037.   Granted, not enough in itself to trigger a radius change, but that could also be a possibility with a very large batch that somehow dropped 2,000,000 chunks into a single neighborhood.

"time"="2024-04-30 18:02:56.494564" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:03:50.044727" "level"="debug" "logger"="node/storer" "msg"="reserve eviction" "uptoBin"=11 "evicted"=207037 "batchID"="0e8366a6fdac185b6f0327dc89af99e67d9d3b3f2af22432542dc5971065c1df" "new_size"=3987274
"time"="2024-04-30 18:03:50.044736" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=207037 "target"=1 "radius"=11

"time"="2024-04-30 18:17:15.332073" "level"="info" "logger"="node/storer" "msg"="reserve radius decrease" "radius"=10 "count"=2069371 "threshold"=2097152

And yet another iteration with additional logs provided in https://github.com/ldeffenb/bee/tree/d5c2646808030e52f4578c369b5862e8739686b8
It seems like there should be one and only one bit of code controlling reserve radius increase AND decrease and the former should be triggered (maybe) when the total reserve size goes over the capacity.   What seems to be happening is that the "in radius" checker sees the level 11 is under-populated so it lowers it to 10.  But then the evictor fails to make the target (don't ask me why?) so it raises the radius back to 11.  But in fact, the total reserve doesn't have enough chunks in radius 11 to stay there, so it drops to 10, but then eviction (which maybe doesn't actually have the proper batch/bin records to evict properly?) fails to make the target, so it raises it back to 11.   And loop forever.
Maybe the reserve should be ALLOWED to go over-capacity UNTIL an "in radius" actual count can be done.   And maybe there needs to be a routine that evicts EVERYTHING that is OUTSIDE the radius rather than trying to go one batch/bin at a time?   That way it's only the reserve iterator that does it all and doesn't rely on a (potentially incomplete?) batch/bin index to identify which chunks should be evicted?
"time"="2024-04-30 17:35:53.928104" "level"="info" "logger"="node/storer" "msg"="reserve radius decrease" "radius"=10 "count"=2094402 "threshold"=2097152 "size"=4193500
"time"="2024-04-30 17:38:58.669601" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=10
"time"="2024-04-30 17:38:58.831092" "level"="info" "logger"="node/storer" "msg"="reserve radius increase" "radius"=11 "evicted"=0 "target"=1 "size"=4194464
"time"="2024-04-30 17:38:58.832474" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=2 "target"=1 "radius"=11 "size"=4194462
"time"="2024-04-30 17:38:58.832513" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=158 "radius"=11
"time"="2024-04-30 17:38:58.917816" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=366 "target"=158 "radius"=11 "size"=4194096
"time"="2024-04-30 17:56:56.386541" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 17:56:56.496861" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=31 "target"=1 "radius"=11 "size"=4194274
"time"="2024-04-30 17:59:26.417036" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 17:59:26.516763" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=12 "target"=1 "radius"=11 "size"=4194293
"time"="2024-04-30 18:00:07.307659" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:00:07.324519" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=6 "target"=1 "radius"=11 "size"=4194299
"time"="2024-04-30 18:00:15.061460" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:00:15.104545" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=6 "target"=1 "radius"=11 "size"=4194299
"time"="2024-04-30 18:00:31.969674" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:00:32.010658" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=6 "target"=1 "radius"=11 "size"=4194299
"time"="2024-04-30 18:00:41.668824" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:00:41.706487" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=25 "target"=1 "radius"=11 "size"=4194280
"time"="2024-04-30 18:02:18.512184" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:02:18.607418" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=19 "target"=1 "radius"=11 "size"=4194286
"time"="2024-04-30 18:04:10.068743" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:04:10.151247" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=19 "target"=1 "radius"=11 "size"=4194286
"time"="2024-04-30 18:05:40.662497" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:05:40.726525" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=23 "target"=1 "radius"=11 "size"=4194282
"time"="2024-04-30 18:05:54.051621" "level"="info" "logger"="node/storer" "msg"="reserve radius decrease" "radius"=10 "count"=2094768 "threshold"=2097152 "size"=4194287
"time"="2024-04-30 18:06:09.555456" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=10
"time"="2024-04-30 18:06:09.700775" "level"="info" "logger"="node/storer" "msg"="reserve radius increase" "radius"=11 "evicted"=0 "target"=1 "size"=4194334
"time"="2024-04-30 18:06:09.712628" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=3 "target"=1 "radius"=11 "size"=4194331
"time"="2024-04-30 18:06:09.712656" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=27 "radius"=11
"time"="2024-04-30 18:06:09.739441" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=30 "target"=27 "radius"=11 "size"=4194301
"time"="2024-04-30 18:06:10.039841" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:06:10.062060" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=12 "target"=1 "radius"=11 "size"=4194304
"time"="2024-04-30 18:06:10.062941" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:06:10.107416" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=52 "target"=1 "radius"=11 "size"=4194255
"time"="2024-04-30 18:06:10.542226" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:06:10.560749" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=11 "target"=1 "radius"=11 "size"=4194300
"time"="2024-04-30 18:06:10.564554" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:06:10.573865" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=4 "target"=1 "radius"=11 "size"=4194309
"time"="2024-04-30 18:06:10.573887" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=5 "radius"=11
"time"="2024-04-30 18:06:10.587181" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=9 "target"=5 "radius"=11 "size"=4194314
"time"="2024-04-30 18:06:10.587211" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=10 "radius"=11
"time"="2024-04-30 18:06:10.600918" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=13 "target"=10 "radius"=11 "size"=4194311
"time"="2024-04-30 18:06:10.600946" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=7 "radius"=11
"time"="2024-04-30 18:06:10.613411" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=8 "target"=7 "radius"=11 "size"=4194306
"time"="2024-04-30 18:06:10.613444" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=2 "radius"=11
"time"="2024-04-30 18:06:10.628527" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=11 "target"=2 "radius"=11 "size"=4194307
"time"="2024-04-30 18:06:10.628553" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=3 "radius"=11
"time"="2024-04-30 18:06:10.647768" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=14 "target"=3 "radius"=11 "size"=4194309
"time"="2024-04-30 18:06:10.647798" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=5 "radius"=11
"time"="2024-04-30 18:06:10.664820" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=6 "target"=5 "radius"=11 "size"=4194317
"time"="2024-04-30 18:06:10.664846" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=13 "radius"=11
"time"="2024-04-30 18:06:10.731846" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=44 "target"=13 "radius"=11 "size"=4194326
"time"="2024-04-30 18:06:10.731870" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=22 "radius"=11
"time"="2024-04-30 18:06:10.822262" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=31 "target"=22 "radius"=11 "size"=4194339
"time"="2024-04-30 18:06:10.822297" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=35 "radius"=11
"time"="2024-04-30 18:06:10.883174" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=49 "target"=35 "radius"=11 "size"=4194332
"time"="2024-04-30 18:06:10.883207" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=28 "radius"=11
"time"="2024-04-30 18:06:10.927568" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=30 "target"=28 "radius"=11 "size"=4194304
"time"="2024-04-30 18:06:19.749084" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:06:19.799066" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=7 "target"=1 "radius"=11 "size"=4194298
"time"="2024-04-30 18:07:07.214476" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:07:07.272042" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=2 "target"=1 "radius"=11 "size"=4194303
"time"="2024-04-30 18:07:11.888326" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:07:11.922295" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=9 "target"=1 "radius"=11 "size"=4194296
"time"="2024-04-30 18:08:00.044641" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:08:00.114654" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=6 "target"=1 "radius"=11 "size"=4194299
"time"="2024-04-30 18:08:33.836729" "level"="info" "logger"="node/storer" "msg"="unreserve start" "target"=1 "radius"=11
"time"="2024-04-30 18:08:33.950028" "level"="info" "logger"="node/storer" "msg"="unreserve finished" "evicted"=56 "target"=1 "radius"=11 "size"=4194249

Since the batch evictor has been modified to only remove the required number of chunks rather than the entire batch, the oscillation seems to have been fixed.   At least, the radius changes in the sepolia testnet showed no oscillations in 2.1.0-rc2.


custom actions for channels/realtime updates

Currently channels get filtered by action get.
This should be a option. Similar to multi-actions, that can be used by option, there could be use-cases for actions like:

receive: get all realtime updates
receive:created: get only created events
receive:updated: get only updates events
receive:patched: get only patched events
receive:removed: get only removed events

Even with fields and conditions this could become powerful.

This would be a nice addition.
I've been thinking about another feature related to events but not directly related to casl, but still.
We could create one channel per service at startup, and then register clients only when they call a service for the first time and if they have the permissions.
Because apart for a notification system, I don't see any reason to receive events for resources you didn't requested yet.
This could be optional of course, (opt-in or opt-out).
This would reduce the load on the server by reducing the checks for the permissions and the sending of the events.
It would also reduce the amount of data stored on the client if a store is used.
The only downside is that, for each request, it would check if the client is already in the channel ( done automatically in the channels when you add a connection if I remember correctly)

@J3m5: Indeed this is nothing, casl could really help. I moved this to Feathers-Vuex. Maybe it's the wrong place too, but lets see. We'll keep this issue for casl-related things :)


Set restricted notes access for users with a nil value

What's up with this migration?

what we want: admins ==> true, non-admins ==> false for can_view_restricted_notes
original migration sets default ==> false, but that doesn't effect existing users in database
#560

What's up with force: :cascade in schema.rb?

from our friends on stackoverflow: "What is :cascade in rails schema.rb and where did it come from?"
tl;dr -- this isn't relevant for our production database right now, because we don't plan on dropping any tables. but if we run into situations (i.e. keeping staging/production parity?) where we need to, this will prevent missing foreign key issues

cc @erose since this affects the excellent can_view_restricted_notes feature you built


Push 0.7.0 tag to GitHub

@lucasmazza I think this was forgotten when releasing 0.7.0. It shows up fine on RubyGems: https://rubygems.org/gems/has_scope
Thanks for the Rails 5 support! ❤

@kaspth https://github.com/plataformatec/has_scope/releases/tag/v0.7.0 ❤

Thanks!


Install dependencies

Operating system: Debian 9.4
Ruby version:  2.3.3
Browser version: N/A
Last upstream commit: de496848c1e7b7116371ae25944aced1c22c47a9
Following your instructions on https://github.com/lord/slate/wiki/Installing-Slate, I ran:

apt-get install ruby-full

Then once I'd retrieved the Slate code from your repository, in the Slate source directory I ran:

gem install bundler
bundle install

However when I then tried to run:

bundle exec middleman server

I got the following error:

/var/lib/gems/2.3.0/gems/execjs-2.7.0/lib/execjs/runtimes.rb:58:in autodetect': Could not find a JavaScript runtime. See https://github.com/rails/execjs for a list of available runtimes. (ExecJS::RuntimeUnavailable) 	from /var/lib/gems/2.3.0/gems/execjs-2.7.0/lib/execjs.rb:5:in module:ExecJS'
from /var/lib/gems/2.3.0/gems/execjs-2.7.0/lib/execjs.rb:4:in <top (required)>' 	from /var/lib/gems/2.3.0/gems/coffee-script-2.4.1/lib/coffee_script.rb:1:in require'
from /var/lib/gems/2.3.0/gems/coffee-script-2.4.1/lib/coffee_script.rb:1:in <top (required)>' 	from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/renderers/coffee_script.rb:2:in require'
from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/renderers/coffee_script.rb:2:in <top (required)>' 	from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/core_extensions/rendering.rb:11:in require'
from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/core_extensions/rendering.rb:11:in block in <top (required)>' 	from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/extensions.rb:91:in load'
from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/extensions.rb:127:in block in load_settings' 	from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/extensions.rb:125:in each'
from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/extensions.rb:125:in load_settings' 	from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/extension_manager.rb:12:in initialize'
from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/application.rb:263:in new' 	from /var/lib/gems/2.3.0/gems/middleman-core-4.2.1/lib/middleman-core/application.rb:263:in initialize'
from /var/lib/gems/2.3.0/gems/middleman-cli-4.2.1/bin/middleman:49:in new' 	from /var/lib/gems/2.3.0/gems/middleman-cli-4.2.1/bin/middleman:49:in <top (required)>'
from /usr/local/bin/middleman:22:in load' 	from /usr/local/bin/middleman:22:in '

I managed to resolve this by running:

apt-get install nodejs

However this was not obvious and took a lot of figuring out - was there something I missed, or should this dependency be mentioned on https://github.com/lord/slate/wiki/Installing-Slate?

Hi. Added a message to wiki, as you suggested.
@lord Could you review, please?
https://github.com/lord/slate/wiki/Installing-Slate#possible-issues

LGTM, thanks for making that change!


Machine Learning Lab - Can't test as no camera source available on vm

I finished the first part of the machine learning lab - Emotion detection with Face API (cloud) and when I run the app, it is blank since no camera source is available on vm. So there is no way to test it .
The entire lab is dependant on camera and frames being available.

learnt from vendor this is unfortunately not possible today - we will not enable VM hosting for ML at this stage - we may revise later


Generate 'stanley' private SSH key if no one provided in Helm values

Closes #16

After several tries and deeper research, it turns out Helm doesn't provide enough instrumentation to work with autogenerated values and their state.

It's possible to autogenerate SSH private key secret, but it will be generated every time on Helm upgrade which is undesired
It's possible to workaround SSH private key generation only once on install and mark it as unmanaged by Helm (so it's not deleted on upgrade), but it's not possible to transition to user-provided SSH key in helm values after that
It's possible to set SSH private key in values.yaml, but it's not possible to transition to autogenerated if user removed predefined one from Helm values

I've seen other official Helm chart repositories and what they do: allow or autogenerated or predefined secrets without proper transition, meaning user had autogenerated secret on first install (default), they can't change it to custom one having no chance to rotate the secrets afterwards.
With that missing functionality with autogenerated < > predefined value transition I'll keep our Helm values as is until better solution introduced in Helm itself.
There are a lot of discussions around this issue in Helm community and even a WIP PR in links below:

https://github.com/helm/helm/issues/3053
https://github.com/helm/charts/issues/5167
https://github.com/helm/helm/pull/5290

Per https://github.com/helm/helm/issues/3053#issuecomment-628876519 looks like Helm3 has a solution related to this issue via new lookup feature.
We'll need to review this.

#203 includes generating the stanley_rsa ssh key by default. So, if that gets merged then this can probably be closed.


Produce QC report after manual correction

It would be nice to generate a QC report along with manual corrections, so they can be easily reviewed by others.
The idea would be to zip that QC folder and upload it along with a new release of the updated database.

That would add an SCT dependency but i guess we can leave with it?


data.py is generating tiny files from my training data

Hi Ottokart,
I'm playing with punctuator2 in a different setting than punctuation restoration. I'm using it to predict long distance tokens; e.g., the input is a document (around 400 words) and I'm trying to predict a token (or more) inside that document (not actually a punctuation), say a paragraph ending. I don't know if punctuator2 will generalize to such tasks so please let me know if there are any restrictions that are specific to punctuation restoration. Now, everything is fine when I use it to predict punctuations and it performs exceptionally, but when I use it for this unusual task, the data.py script produces tiny files from my training data (remember, most of the time there is only one "punctuation" token in a given ~400-word line representing a document):
$ du -sch data/*
4.0K	dev
4.0K	test
16K	train
152K	vocabulary

Where my text files are:
$ wc *
     180   139630   852376 ep.dev.txt
     180    62584   371250 ep.test.txt
    4588  2007796 12097309 ep.train.txt

This is the error I get when I train:
$ python main.py ep 4 0.02
Using gpu device 0: Tesla K80 (CNMeM is disabled, cuDNN not available)
4 0.02 Model_ep_h4_lr0.02.pcl
Loading previous model state
Number of parameters is 84008
Training...
Total number of training labels: 1029
WARNING: Not enough samples in '../data/dev'. Reduce mini-batch size to 0 or use a dataset with at least 1050 words.
Total number of validation labels: 0
Traceback (most recent call last):
  File "main.py", line 182, in <module>
    ppl = np.exp(total_neg_log_likelihood / total_num_output_samples)
ZeroDivisionError: division by zero

I realize that my data is small, but the tiny data files generated by data.py suggest that text is being omitted. I wonder if there is another reason for this issue related to the code being not designed for such tasks. Will doing any of the following solve my problem:

Use pre-trained vectors.
Collect more training data.
Modify parts of the code (if it's a quick fix).

If none will work, no problem, I'll build my own architecture.
Thank you.
Wael

Hi!
Actually there's even a warning that hints what's wrong: WARNING: Not enough samples in '../data/dev'. Reduce mini-batch size to 0 or use a dataset with at least 1050 words.
So, the solution would be to collect much-much more training data (tens of millions of words at least).
Although, your task seems a little bit more difficult than punctuation restoration, I see no other reason why it shouldn't work at least on some level if you have enough training data.
PS! In your example you have set the hidden layer size to 4. This probably makes the model way too small (try 128 or 256).
PPS!  If that happens, you can reduce the minibatch size from 128 to 64 for example.
Best,
Ottokar


SVGView and tishadow

Do you have any idea how to get this module working with tishadow?
There is some sort of path issue where running the app does not find the svg file.
Error is: [ERROR] [iphone, 8.3, <IP_ADDRESS>] Error: Invalid parameter not satisfying: newSource != nil
Runs fine with straightforward ti compile, but not with ti shadow.

And just to add to this, I can't see a way to trap errors such as calling createView with an non-existent SVG file (i.e. wrong filename or path). Even try/catch doesn't seem to work:
var SVGView = require('com.geraudbourdin.svgview');
var svgView;
try {
svgView = SVGView.createView({
image: 'test.svg',
width: '350',
height: '350',
//top: 0,
//left: 0,
backgroundColor: 'red'
});
} catch (error) {
alert('sgvView is null')
}


pull request for e2e test at 12/31/2016 02:15:17

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


The access token has been obtained for wrong audience or resource error

Describe the bug
The ingress-azure pod goes into CrashLoopBackOff status with the below error when the environment is set to AzureUSGovernmentCloud. The issue does not occur on older versions like 1.6.0
Message="The access token has been obtained for wrong audience or resource 'https://management.azure.com'. It should exactly match with one of the allowed audiences 'https://management.core.usgovcloudapi.net/','https://management.core.usgovcloudapi.net','https://management.usgovcloudapi.net/','https://management.usgovcloudapi.net'.""
To Reproduce
Install 1.7.1 version of the controller.
Ingress Controller details

Output of kubectl describe pod <ingress controller>

Name:             ingress-azure-85dfd8d479-jrkr7
Namespace:        default
Priority:         0
Service Account:  ingress-azure
Node:             aks-agent-21939062-vmss000001/<IP_ADDRESS>
Start Time:       Thu, 22 Jun 2023 15:44:01 +0530
Labels:           aadpodidbinding=ingress-azure
                  app=ingress-azure
                  pod-template-hash=85dfd8d479
                  release=ingress-azure
Annotations:      checksum/config: 98274f88b5466064d64af1b661ded40071725ba3a5cff6cdd8649409143958bc
                  prometheus.io/port: 8123
                  prometheus.io/scrape: true
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/ingress-azure-85dfd8d479
Containers:
  ingress-azure:
    Container ID:   containerd://1ee8b7fb6a4e4bc8427fe3e98ff4dc669205f49dc5c93118e922080f000c77e0
    Image:          mcr.microsoft.com/azure-application-gateway/kubernetes-ingress:1.7.1
    Image ID:       mcr.microsoft.com/azure-application-gateway/kubernetes-ingress@sha256:91a6648b78c65f3b6858441589daabd72146d9a53e896c0e6abf501e870f9d9b
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Fri, 23 Jun 2023 15:28:51 +0530
      Finished:     Fri, 23 Jun 2023 15:28:51 +0530
    Ready:          False
    Restart Count:  283
    Liveness:       http-get http://:8123/health/alive delay=15s timeout=1s period=20s #success=1 #failure=3
    Readiness:      http-get http://:8123/health/ready delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment Variables from:
      ingress-azure  ConfigMap  Optional: false
    Environment:
      AZURE_CLOUD_PROVIDER_LOCATION:  /etc/appgw/azure.json
      AGIC_POD_NAME:                  ingress-azure-85dfd8d479-jrkr7 (v1:metadata.name)
      AGIC_POD_NAMESPACE:             default (v1:metadata.namespace)
    Mounts:
      /etc/appgw/ from azure (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-k28cz (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  azure:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/kubernetes/
    HostPathType:  Directory
  kube-api-access-k28cz:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 op=Exists
Events:
  Type     Reason   Age                    From     Message
  ----     ------   ----                   ----     -------
  Warning  BackOff  3m9s (x6897 over 23h)  kubelet  Back-off restarting failed container

Output of `kubectl logs .

I0623 09:53:37.255339       1 utils.go:114] Using verbosity level 3 from environment variable APPGW_VERBOSITY_LEVEL
I0623 09:53:37.276052       1 supported_apiversion.go:70] server version is: 1.25.5
I0623 09:53:37.286231       1 environment.go:294] KUBERNETES_WATCHNAMESPACE is not set. Watching all available namespaces.
I0623 09:53:37.286249       1 main.go:118] Using User Agent Suffix='ingress-azure-85dfd8d479-jrkr7' when communicating with ARM
I0623 09:53:37.286331       1 main.go:137] Application Gateway Details: Subscription="77f8dc1f-50f0-4867-a60b-1f999873096f" Resource Group="chethan2303-stamp-usgovvirginia-rg" Name="agw-chethan2303-usgovvirginia"
I0623 09:53:37.286346       1 auth.go:58] Creating authorizer using Default Azure Credentials
I0623 09:53:37.286411       1 httpserver.go:57] Starting API Server on :8123
E0623 09:53:37.338618       1 client.go:184] configuration error (bad request) or unauthorized error while performing a GET using the authorizer
E0623 09:53:37.338634       1 client.go:185] stopping GET retries
F0623 09:53:37.338694       1 main.go:175] Failed getting Application Gateway: Code="ErrorApplicationGatewayUnexpectedStatusCode" Message="Unexpected status code '401' while performing a GET on Application Gateway." InnerError="network.ApplicationGatewaysClient#Get: Failure responding to request: StatusCode=401 -- Original Error: autorest/azure: Service returned an error. Status=401 Code="InvalidAuthenticationTokenAudience" Message="The access token has been obtained for wrong audience or resource 'https://management.azure.com'. It should exactly match with one of the allowed audiences 'https://management.core.usgovcloudapi.net/','https://management.core.usgovcloudapi.net','https://management.usgovcloudapi.net/','https://management.usgovcloudapi.net'.""

Any Azure support tickets associated with this issue.
No

This is fixed in AGIC 1.7.2.


JupyterLab 4 compatibility

Make sure that Jupyter Scheduler works with JupyterLab 4.0.0 or later. Update dependencies and documentation.

Possibly relevant Discourse thread about targeting both versions: https://discourse.jupyter.org/t/jlab-extensions-that-target-both-jlab3-and-jlab4/20100

When I right-click on a file in the file browser, the "Create Job" option doesn't spawn the create form. Using the toolbar button in an open notebook does cause the form to appear.


Toptruyen: update domain

Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[x] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[x] Have removed web_hi_res_512.png when adding a new extension

No trailing slash for the baseUrl, and just to check, did you actually test the changes in Android Studio to see if it works?


Update branch protection to use Rulesets

With branch protection rules, when there are required checks for merging into dev:

The release workflow will not be able to fast-forward main->dev to bring the release tag into the main branch, and a PR like #91 will be opened instead.
Notably, eventhough we allow an automation user to bypass a pull request

this has no effect on required status checks:
https://github.com/orgs/community/discussions/43460)
Rulesets allows more fine-grained control and would allow teams to bypass required status checks:
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#about-rulesets

For now, I've disabled the required checks on dev so that the automation will work in the future.


Reloading wizard steps based on inputs given in any wizard page content of the same wizard

[ ] bug
[ X] feature request
[ ] enhancement

### Expected behavior
Is there a way to reload the wizard steps based on the input given in any of the wizard steps(Eg: select box)? Basically want to understand how I can bind the change event in a wizard step page to reload wizard steps .Please help me with an example or documentation for this.

### Environment details

* **Angular version:** 4.0.X

* **Clarity version:** 0.9.X

* **OS and version:** Windows

* **Browser:** [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

@indukr, something like this?
https://plnkr.co/edit/xHPrcAo0ZqJ6vDCZtb80?p=preview

Closing as it seems the plunkr answers the question.

Hey @mathisscott ,
This is what I am looking for. Found it very useful. thanks.


Use JDK ObjectInputFilter instead of spring ConfigurableObjectInputStream

I think it's better to use standard API.
see Java Serialization Filters

Well, the ConfigurableObjectInputStream is still going to be there since it relies on the specific ClassLoader:
/**
 * Special {@link ObjectInputStream} subclass that resolves class names
 * against a specific {@link ClassLoader}.
 *
 * @author Juergen Hoeller
 * @since 2.5.5
 * @see org.springframework.core.serializer.DefaultDeserializer
 */
public class ConfigurableObjectInputStream extends ObjectInputStream {

Please, revise your request about the logic we do in the AllowedListDeserializingMessageConverter to use that ObjectInputFilter instead of resolveClass() override.
Otherwise this is confusing and might be closed without the fix.
Thanks

I made the change: https://github.com/artembilan/spring-amqp/commit/16c9e8f54d74d5343b3cac086e0e58036b0e02c6.
But decided that it is a bit of breaking in the behavior since now we do not throw SecurityException directly, but though some stack trace dictated by the ObjectInputFilter with its InvalidClassException (which is a checked IOException).
So, pushing this to the future when we start a new major version.


makemigrations error

after doing step 'f', I'm in a migrations error.
my error case is that
"/www/django-bona-blog/bona_env/lib/python3.9/site-packages/blog/migrations/0002_auto_20200618_2226.py", line 4, in
import tinymce.models"
I want to know that is a reason of python version or package issue.
And I think, this package is using 'CKEDITOR', and 'tinymce' is different web-editor solution.
I can't find any support informations about 'tinymce' in this readme.

I just make a django new project, and doing following your step.
I don't know whether it is. If not, let me know how I can.

Thank you for bringing my notice to this issue.
TinyMCE was replaced with CKeditor.
I will fix this error and notify you.

Try "python manage.py makemigrations" before doing "python manage.py migrate" and let me know

Follow this guide to install the tinymce package and let me see.

Have the same error, Where is the guide

Follow this guide to install the tinymce package and let me see.

Have the same error, Where is the guide

This is the guide
pip install django-tinymce

Did it work for you by installing it?


Update contact search CSV export for multiple interaction advisers

Description of change
Dependent on https://github.com/uktrade/data-hub-leeloo/pull/1900.
This updates the 'Team of latest interaction' field in the contact search CSV export to use Interaction.dit_participants instead of the old Interaction.dit_team field.
As a result, it now can contain multiple (comma-separated) values and the output column has been renamed 'Teams of latest interaction'.
Only unique values are included (as one team could be on an interaction multiple times if multiple advisers from the team were added to the interaction).
Checklist

[x] Has a new newsfragment been created? Check changelog/README.rst for instructions
[ ] Have any relevant search models been updated?
[ ] Have any relevant fixtures (fixtures/test_data.yaml) been updated?
[ ] Have any relevant select-/prefetch-related field lists in the views and search apps been updated?
[ ] Has the admin site been updated (for new models, fields etc.)?
[ ] Has the README been updated (if needed)?

Do you think that commit 8b23355 should be a fixup? Seeing as it addresses a comment which came up in this review.

Yes, it wasn't marked as one but was meant as one. I'll squash it when rebasing.


QUALITY-1864 - Add the check for include test coverage

Add the check for include_test_coverage when generating coverage information for pytest component and content.

Tests failed!


Aws sdk net v1

Description

Motivation and Context

Testing

Screenshots (if appropriate)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have read the README document
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

@pradhan-sasmita-85 , can you provide the context for this PR, it seems this PR was submitted by mistake.

Closing for lack of activity.


HSEARCH-3047 Implement the missing field types and default bridges compared to Search 5

https://hibernate.atlassian.net/browse/HSEARCH-3047
Reopen this: https://github.com/hibernate/hibernate-search/pull/1880.

@yrodiere I'm addressing some Sonar warnings.

Pull Request Test Coverage Report for Build 1

1033 of 1110 (93.06%)  changed or added relevant lines in 73 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 88.409%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/types/codec/impl/LuceneInstantFieldCodec.java
9
10
90.0%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/gson/impl/JsonElementTypes.java
4
6
66.67%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchByteFieldCodec.java
6
8
75.0%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchDoubleFieldCodec.java
6
8
75.0%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchFloatFieldCodec.java
6
8
75.0%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchShortFieldCodec.java
6
8
75.0%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/types/codec/impl/LuceneByteFieldCodec.java
24
26
92.31%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/types/codec/impl/LuceneDoubleFieldCodec.java
22
24
91.67%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/types/codec/impl/LuceneFloatFieldCodec.java
22
24
91.67%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/types/codec/impl/LuceneShortFieldCodec.java
24
26
92.31%

Totals

Change from base Build 146:
0.4%

Covered Lines:
15568

Relevant Lines:
17609

💛  - Coveralls

@yrodiere thanks for the review, I think I've addressed the comments here. So will you update the documentation? Thanks

I addressed the remaining comments and added documentation. Waiting for CI, then I'll merge it.

Merged. Thanks @fax4ever !

Thanks to you!


Self Assignable Roles

Nadeko v 2.0.0 - updated today. Linux. mint.
Lsar does not list all the roles that can be assigned. listed around 22 of 28. cannot lsar 1 to see the second group either. previously a reaction popped up to allow switching between pages.

Are you sure? try running it again? It might have cleaned up 6 roles

same issue. second group isn't listed. lsar 0 deletes itself and doesn't do anything. all commands log in the terminal. including lsar 0. {the one that is useless}

DM me your database on discord.

Dm'd. rename to nadekobot.db (obviously)

I will forward this to the ofiicial discord bug squashers. The embed was cut short on android. the whole embed shows on canary for linux.


Is konga alive?

No commits since about half a year, no visible activity from the maintainer?
It would be a great pity if we couldn't use konga anymore.
@pantsel ?

I upgarded my kong from 1.X to 2.X. I was totally loving konga in 1.X kong and then found out that konga no longer support for 2.X :'(

I use Konga 0.14.9 with Kong 2.0.x and it is working very well, I'm glad I have Konga, hope it will continue with Kong 2.0 as it is already working very good.
Best regards.

I use Konga 0.14.9 with Kong 2.0.x and it is working very well.
I'm glad I have Konga, and hope it will continue with Kong 2.0 as it is already working fine.
Best regards.

My consumer authentication with api key is not working. Do you use that or does it work for you ?

I have used api key and basic auth, they are both working


Backtest results not displayed

Symptom: After several backtesting sessions, the latest one is not showing proper results on the charts. The Simulation panel shows some numbers but the actual simulation is not displayed on screen.

This error can be seen on the browser's console:

Log files (only last run as there is a weight limit):
D.2019.10.07.T.08.53.14.zip
Data files:
AAJason.1.0.zip

Workspace:
Share - Workspace - BB Pong - BTC - 10 min.txt

I'm closing this case as I think the reason I wasn't seeing the results is because of the situation described in a comment on issue #56.


Node commissioning task is failing at contiv_network : set aci mode

Docker - 1.11.1.CS2
UCP - 1.1.0
Contive Network - v0.1-05-16-2016.08-29-25.UTC
Node - Docker-aci-2-FCH1945V3GF
Status - Service-Master
Ansible/Cluster manager was clonned today only. Error message -
TASK [contiv_network : set aci mode] *******************************************
fatal: [Docker-aci-2-FCH1945V3GF]: FAILED! => {"changed": true, "cmd": "contivctl network global set --fabric-mode aci", "delta": "0:00:00.840968", "end": "2016-05-30 15:36:46.333656", "failed": true, "rc": 3, "start": "2016-05-30 15:36:45.492688", "stderr": "time="2016-05-30T15:36:46+05:30" level=error msg="307 Temporarily Moved for Domain Name Expansion" ", "stdout": "", "stdout_lines": [], "warnings": []}
to retry, use: --limit @/home/cluster-admin/ansible/site.retry
PLAY RECAP *********************************************************************
Docker-aci-2-FCH1945V3GF   : ok=84   changed=37   unreachable=0    failed=1

The same code base worked on SanJose ACI setup which is not behind proxy. This error is being seen on a setup in BLR working behind proxy.
Not well versed on the error message so as to debug this further. Attaching logs from node getting commissioned and cluster manager node.

clusterm-journal.txt
clusterm-status.txt
etcd-journal.txt
etcd-status.txt
netmaster-journal.txt
netmaster-status.txt
netplugin-journal.txt
netplugin-status.txt

@rkharya I think you will need to set no_proxy env variable as well when you run behind proxy. Something like below:
-e {"env": {"no_proxy":"<IP_ADDRESS>,localhost,netmaster"} }

@mapuri Thanks, that helped. Pls. close this issue.

Closing the issue since no_proxy setting fixed it


Updated to 1.6.0: EVGA store gives ERR_CONNECTION_RESET

Just switched to 1.6.0 (remove old folder, clone a fresh new one), and this started happening.
[5:23:49 PM] info :: ℹ selected stores: adorama, amazon, bandh, bestbuy, evga, gamestop, newegg, officedepot
[5:23:49 PM] info :: ℹ selected brands: evga
[5:23:49 PM] info :: ℹ selected models: ftw3 ultra
[5:23:49 PM] info :: ℹ selected series: 3080, 3090
. . . .
[5:25:12 PM] error :: ✖ [evga] evga 3080 ftw3 ultra - net::ERR_CONNECTION_RESET at https://www.evga.com/products/product.aspx?pn=10G-P5-3897-KR
[5:25:42 PM] error :: ✖ [evga] evga 3090 ftw3 ultra - Navigation timeout of 30000 ms exceeded

Just a few minutes ago, this was working under 1.5.0. With the same .env file.
Every other store/card combo seems to be working as expected, therefore omitted from above. Of course, all OUT OF STOCK.
Tuna

I actually think we solved some bugs in 1.6.0. Do you mind trying with the latest main?

# ** All configuration variables are optional **
# Read https://github.com/jef/nvidia-snatcher#customization for help on customizing this file
#############################################################################################

BROWSER_TRUSTED=""
COUNTRY=""
DISCORD_NOTIFY_GROUP=""
DISCORD_WEB_HOOK=""
<EMAIL_ADDRESS><EMAIL_ADDRESS>EMAIL_PASSWORD="********"
HEADLESS=""
IN_STOCK_WAIT_TIME="5"
LOG_LEVEL=""
LOW_BANDWIDTH=""
MAX_PRICE_3070=""
MAX_PRICE_3080=""
MAX_PRICE_3090=""
MICROCENTER_LOCATION=""
NVIDIA_ADD_TO_CART_ATTEMPTS=""
NVIDIA_SESSION_TTL=""
OPEN_BROWSER=""
PAGE_BACKOFF_MIN=""
PAGE_BACKOFF_MAX=""
PAGE_SLEEP_MIN="60000"
PAGE_SLEEP_MAX=""
PAGE_TIMEOUT=""
PHONE_NUMBER="**********"
PHONE_CARRIER="att"
PLAY_SOUND=""
PROXY_ADDRESS=""
PROXY_PORT=""
PUSHBULLET=""
PUSHOVER_TOKEN=""
PUSHOVER_USER=""
PUSHOVER_PRIORITY=""
SCREENSHOT="true"
SHOW_ONLY_BRANDS="evga"
SHOW_ONLY_MODELS="ftw3 ultra"
SHOW_ONLY_SERIES="3080,3090"
SLACK_CHANNEL=""
SLACK_TOKEN=""
SMTP_ADDRESS=""
SMTP_PORT=""
STORES="adorama,amazon,bandh,bestbuy,evga,gamestop,newegg,officedepot"
TELEGRAM_ACCESS_TOKEN=""
TELEGRAM_CHAT_ID=""
TWILIO_ACCOUNT_SID=""
TWILIO_AUTH_TOKEN=""
TWILIO_FROM_NUMBER=""
TWILIO_TO_NUMBER=""
TWITTER_CONSUMER_KEY=""
TWITTER_CONSUMER_SECRET=""
TWITTER_ACCESS_TOKEN_KEY=""
TWITTER_ACCESS_TOKEN_SECRET=""
TWITTER_TWEET_TAGS=""
USER_AGENT="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36"

By the way, I have no idea how to use GIT, sadly. So, all I know is to follow your "git clone" instruction on how to set it up from scratch. Therefore, I simply delete my prev folder, and re-setup with "git clone". If you want me to try out something, I'll need braindead command lines for me to use... :(
Also, I do think one of the changes in the 1.6.0 was related to EVGA container. Can't look it up right now. I will later, if need be.
Thanks for looking at this!

Btw, I did find this interesting: https://github.com/jef/nvidia-snatcher/issues/653#issuecomment-719928734
At least for the store, you could remove it.
As for all the blank .env, I would remove all of them. I don't believe they'll have any side-effect, but do you mind removing them and then testing for me?

Sorry, your last requests came in after I hit the pillow.

2) I guess https://github.com/jef/nvidia-snatcher/issues/653#issuecomment-719928734 does make sense. I was more in favor of keeping evga as a store just in case they removed that process after more availability, and my snatcher would just work as-is instead of me requiring to add evga store back again.
3) I just git clone'd 1.7.0 and used it with the above stripped .env, and the error is still there, but at least I am  getting warned about it! :)
[6:52:37 AM] warn :: evga is deprecated since they only support queuing

Oh, and: I just saw the mention of npm run start:dev on your Developer Notes. Don't know if that is new or if I was just blind before... But that should work well for me going fwd...

Still interesting about evga not being searched...
This is my config:
STORES=evga
HEADLESS=false
USER_AGENT=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36

Seems like the requests are going through. Although the links work. Could be a problem, I'll look into it more.


CT This Disposable has already been disposed, and cannot be disposed again

scenery : top-level-unit-tests : unbuilt?ea
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/scenery/scenery-tests.html?ea
388 out of 389 tests passed. 1 failed.
AlignBox: Multiple Boxes in a Group failed:
Died on test #31 at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/scenery/js/layout/nodes/AlignBoxTests.js:45:7: Assertion failed: This Disposable has already been disposed, and cannot be disposed again
Error: Assertion failed: This Disposable has already been disposed, and cannot be disposed again
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/assert/js/assert.js:28:13)
at AlignBox.Disposable.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:26:19)
at AlignBox.onDisposer (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:33:10)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/TinyEmitter.js:88:39)
at AlignGroup.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:70:25)
at AlignGroup.Disposable.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:27:22)
at Object.<anonymous> (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/scenery/js/layout/nodes/AlignBoxTests.js:114:9)

id: Bayes Puppeteer
Snapshot from 11/28/2022, 2:35:02 AM

----------------------------------

scenery : top-level-unit-tests : unbuilt?ea&brand=phet-io
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/scenery/scenery-tests.html?ea&brand=phet-io
391 out of 392 tests passed. 1 failed.
AlignBox: Multiple Boxes in a Group failed:
Died on test #31 at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/scenery/js/layout/nodes/AlignBoxTests.js:48:7: Assertion failed: This Disposable has already been disposed, and cannot be disposed again
Error: Assertion failed: This Disposable has already been disposed, and cannot be disposed again
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/assert/js/assert.js:28:13)
at AlignBox.Disposable.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:26:19)
at AlignBox.onDisposer (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:33:10)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/TinyEmitter.js:88:39)
at AlignGroup.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:70:25)
at AlignGroup.Disposable.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:27:22)
at Object.<anonymous> (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/scenery/js/layout/nodes/AlignBoxTests.js:121:9)

id: Bayes Puppeteer
Snapshot from 11/28/2022, 2:35:02 AM

----------------------------------

scenery : top-level-unit-tests : unbuilt?ea&brand=phet-io
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/scenery/scenery-tests.html?ea&brand=phet-io
391 out of 392 tests passed. 1 failed.
AlignBox: Multiple Boxes in a Group failed:
Died on test #31 at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/scenery/js/layout/nodes/AlignBoxTests.js:45:7: Assertion failed: This Disposable has already been disposed, and cannot be disposed again
Error: Assertion failed: This Disposable has already been disposed, and cannot be disposed again
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/assert/js/assert.js:28:13)
at AlignBox.Disposable.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:26:19)
at AlignBox.onDisposer (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:33:10)
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/TinyEmitter.js:88:39)
at AlignGroup.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:70:25)
at AlignGroup.Disposable.dispose (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/axon/js/Disposable.js:27:22)
at Object.<anonymous> (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1669628102736/chipper/dist/js/scenery/js/layout/nodes/AlignBoxTests.js:114:9)

id: Bayes Puppeteer
Snapshot from 11/28/2022, 2:35:02 AM

This is me from work over in https://github.com/phetsims/scenery-phet/issues/769

So this fixes things, but I believe it is just a symptom of another problem: How do we generally handle the case where you set a disposer on X and then call X.dispose manually? Is that a bug and we should assert that the disposer didn't trigger the disposal? Should we be graceful?
Above I implemented grace in AlignBox.

Ahha! Writing the above helped me realize that I believe we should in fact be very very strict. If you mark a disposer, and then that is not how you are disposed, then let's assert. I wonder how far we can get with that. I believe it will help cover cases like this where scenery unit tests removed a box and then disposed it, instead of having the group dispose it.

Looking good now.


SpatialFullConvolution in clnn

Hi,
I want to ask you if is possible to convert SpatialFullConvolution for using it in clnn.
Best,
Nick

Hey @bionick87,
if you look at #42 you will see that I've encountered this issue as well, and was underway to port SpatialFullConvolution - the only issue was that distro-cl is forked just before spatialFullConvolution was commited to torch;
I started the merge from upstream, but then a couple of Nvidia cards came over and... yeah, never finished it. If you're up for the task, feel free to review the referenced thread - if I remember correctly, https://github.com/torch/nn/commit/b339dad44739267bd79a0eae0fb158bfcab5991b needs to be ported to clnn, and then https://github.com/ViliusT/clnn/compare/master...ViliusT:feature/spatialFullConv should build fine(ish)


Description

[x] NUC is setup on new network
[x] Plex is successfully up and running
[x] Add integration

Integration URL
https://www.home-assistant.io/integrations/plex/
Automation Idea
No response
New Hardware?
No
Add Amazon / store URL for referencing if new hardware is required
No response

Added via myintegrations
no issues


lxd snap keeps creating 57 MB volume mounts

$ mount | grep snaps/lxd
/var/lib/snapd/snaps/lxd_11381.snap on /snap/lxd/11381 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/lxd_11405.snap on /snap/lxd/11405 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/lxd_11320.snap (deleted) on /media/peter/disk type squashfs (ro,nosuid,nodev,relatime,uhelper=udisks2)
/var/lib/snapd/snaps/lxd_11270.snap (deleted) on /media/peter/disk1 type squashfs (ro,nosuid,nodev,relatime,uhelper=udisks2)
/var/lib/snapd/snaps/lxd_11353.snap (deleted) on /media/peter/disk2 type squashfs (ro,nosuid,nodev,relatime,uhelper=udisks2)

Required information

Distribution: Ubuntu MATE
Distribution version: Bionic
The output of "lxc info" or if that fails:

config:
  core.https_address: '[::]:8443'
  core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIICPDCCAcKgAwIBAgIRAM25aE7omyVaWlM46TNLFtcwCgYIKoZIzj0EAwMwOjEc
    MBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEaMBgGA1UEAwwRcm9vdEBwZXRl
    ci1vZmZpY2UwHhcNMTkwNzEwMjMwNzI5WhcNMjkwNzA3MjMwNzI5WjA6MRwwGgYD
    VQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRowGAYDVQQDDBFyb290QHBldGVyLW9m
    ZmljZTB2MBAGByqGSM49AgEGBSuBBAAiA2IABKlRFxqXjKv7DspXIrsMmI5HQDgu
    wQ8WYKuiM9uePvRTF7nxM6bcHsHfoDb1bf744mDFBhSi61ozE52XPz5sr08aBqmk
    kuioNqu4NLlsj5pI1UWXGpJR1VKECf8ozVa86aOBizCBiDAOBgNVHQ8BAf8EBAMC
    BaAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADBTBgNVHREETDBK
    ggxwZXRlci1vZmZpY2WHBMCoAciHBKwRAAGHBKwTAAGHBKwcAAGHBKwbAAGHBKwa
    AAGHBKwVAAGHBKwUAAGHBKwZAAGHBKwWAAEwCgYIKoZIzj0EAwMDaAAwZQIwM48e
    PagncCnSUVqAQSWXbzm9etHw5kuwRNCHP/yJ5CjkGC+ErAngFqUVyjA/eOAJAjEA
    8m4N3OXk0jNDGOSZz3bRjllFSevZrhMzpwUbJGiP//raYgiXMOcx6mtGWnfohSTE
    -----END CERTIFICATE-----
  certificate_fingerprint: 4793ac341b6ea3453857c458cff26689bd704cf55a0fba458874bc07566642b8
  driver: lxc
  driver_version: 3.2.1
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "false"
    seccomp_listener: "false"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 4.18.0-25-generic
  lxc_features:
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    seccomp_notify: "true"
  project: default
  server: lxd
  server_clustered: false
  server_name: peter-office
  server_pid: 18220
  server_version: "3.15"
  storage: zfs
  storage_version: 0.7.9-3ubuntu6

Issue description
Just having it installed, not using it.  I think it happens when the snap auto-updates.

Yeah, not really something that LXD can do anything about, I'd recommend bringing this up at https://forum.snapcraft.io
snapd keeps the past 3 revisions of the snap mounted (I think?). So that's what you're seeing here.
I believe there is a snapd option to change that down to just 1, or obviously if you're not using lxd, you can just uninstall it.
I'd certainly prefer snapd either use some mount namespace magic to hide those mounts or see more tools setup to just skip over those mounts, but indeed they do still show up in a bunch of places.


[FEATURE] Update http package dependency to version ^0.13.1

It is difficult to manage conflicting dependencies between dialog_flowtter and other packages (namely firebase_auth) as they both utilize different http versions.
Updating the http package dependency version to ^0.13.1 would bring this package up to date with other contemporary packages and would resolve many conflicts.
I've attempted to solve these conflicting dependencies by simply downgrading my http version to no avail, so this seems like a simple enough solution that would facilitate access to all future users.

Hey, that version of http has now migrated to using null-safety. I think for you to use it need to be using Flutter 2.0. Fortunately we have a null-safety version of this package. Update the dependency on your pubspec.yaml to use version 0.3.0 like this dialog_flowtter: ^0.3.0-nullsafety.0
I will check if I can upgrade it without null-safety support so I can publish a 0.2.x version
Let me know if that solved your problem so I can close this issue

That solved my issue!
Thank you for the quick response and for the upkeep on this package! Very much appreciated.


add time counter to logger

[0.000000] [CORE] [DEBUG] : I can go for hours...
[0.018605] [CORE] [DEBUG] : My pullout game is not that strong.
[0.270609] [CORE] [DEBUG] : My pullout game is not that strong.

to see how much time it took for something.

Stardust has a profiler - but this works too.

isn't the profiler just for scope performance testing and for performance testing in general?

Yes


Homework6: Anastasiya Solodukho

Added file with Homework #6

Hello @Stml89,
I changed PR name.
Please, check.


Invalid HAProxy config causes marathon-lb to stop trying

The main problem here is that, if a user sets up options improperly to cause an haproxy configuration error, even after correcting the issue which causes the haproxy config to have a fatal error, marathon-lb will be stuck and not receive new updates and marathon-lb must be restarted to resolve the issue.
I am using SSE mode.
The following are the last log entries from the container:
marathon_lb: reading running config from /marathon-lb/haproxy.cfg
marathon_lb: running config is different from generated config - reloading
marathon_lb: writing config to temp file /tmp/tmp95z_ycw9
marathon_lb: skipping validation. moving temp file /tmp/tmp95z_ycw9 to /marathon-lb/haproxy.cfg
marathon_lb: reloading using sv reload /marathon-lb/service/haproxy
ok: run: /marathon-lb/service/haproxy: (pid 15) 606605s
Reloading haproxy
[ALERT] 174/171924 (7841) : parsing [/marathon-lb/haproxy.cfg:83] : 'option httpchk' cannot handle unexpected argument 'timeout'.
[ALERT] 174/171924 (7841) : Error(s) found in configuration file : /marathon-lb/haproxy.cfg
[ALERT] 174/171924 (7841) : Fatal errors found in configuration.
Invalid config
marathon_lb: received event of type status_update_event

After this point, marathon-lb will no longer attempt to pull new config due to marathon changes.

Indeed, if the config is invalid, it will fail. There isn't much I can do about this, except implore that you carefully test changes before deploying them.

Failing isn't the problem, the problem is that marathon-lb is "dead" and unable to receive any new updates until the container is restarted. Even if someone corrects the issue so that valid config would be generated, it's stuck until the container is restarted.

Yes, that's correct. If you start MLB with an invalid config, HAProxy will never start.

This is the series of events:

Marathon-lb is running fine and has the correct configuration
User inputs a bad option through the Marathon UI
Marathon-lb tries to reload haproxy, and fails
User corrects the option
Marathon-lb no longer receives updates to correct itself
User must restart marathon-lb to retrieve new marathon configuration
Marathon-lb starts HA Proxy fine because config is correct

I just ran a test as you described, and everything seemed to work as expected (i.e., when I fixed the busted label, everything was fine).
What version of MLB are you running? Can you provide any more details such as logs?

Using 1.2.2.
I use this command to start marathon-lb:
docker run -d --name "slave-lb-{{ grains['id'] }}" --restart always -p 80:80 -p 443:443 -p 9090:9090 -e "PORTS=80,443,9090" --privileged=true --volume=/data/marathon-lb/templates:/marathon-lb/templates mesosphere/marathon-lb:v1.2.2 sse --marathon http://marathon.{{ pillar['domain'] }} --skip-validation --group external --health-check

I broke things accidentally by using the marathon ui to enter data instead of json, copying/pasting from marathon stripped out \n which resulted in the following which I entered in another label:
"HAPROXY_0_BACKEND_HTTP_HEALTHCHECK_OPTIONS": "  option  httpchk GET {healthCheckPath} HTTP/1.1\\r\\nHost:\\ test.com  timeout check {healthCheckTimeoutSeconds}s",

This resulted in the timeout line and first server line being put on the option httpchk line.
The logs I pasted in the first message is where the MLB halted; everything up until then was basically normal, until it tried to reload with this bad config. After that point, no new logs were created even after changing Marathon config multiple times (this same thing happened on all 3 MLB instances I have; after fixing the issue and also restarting MLB, things finally worked again). If further logs would be desired I can cause this again (I actually believe I've triggered this a few times recently working with MLB, I just didn't realize this was the cause of why MLB stopped receiving updates until now), just let me know.

Okay, I'll reopen this and investigate when I get a chance.

Thanks!

Maybe the same issue as #230, although I've still not reproduced this.

Please test the mesosphere/marathon-lb:set-socket-timeout image and let me know if that helps.

Been pretty busy with stuff the last couple of days and will be the next few days, but I will test this as soon as I can and report back, thank you!

I'm going to close this under the assumption that #240 resolves it. Please reopen if it happens again.


Regression in Data Filters functionality

Since DBeaver CE 5.1.1, I noticed two issues in the Data Filters functionality

When applying the filter criteria with Ctrl+Enter, a popup indicating Data read is in progress - can't run another appears

In the SQL Editor, this functionality is also broken, though it doesn't show  a popup, it merely does nothing.

Using autocompletion for the SQL Expression immediately applies the filter

start typing the name of a column (e.g. CATA) and press Ctrl+Space

select the wanted column (e.g. CATALOG_NAME) and press Enter

I have the same problem, just when I repeat CTRL + ENTER after click OK in the message's box isn't trigger the error again, but if I try again the autocompletition  the error appear, I mean:

CTRL + SPACE then ENTER -> Error
Click ok in the box that show the error of execution query
CTRL + SPACE then ENTER -> Ok
CTRL + SPACE then ENTER -> Error
Click ok in the box that show the error of execution query
....

@rwalravens this is a bug in Enter key processing. We'll fix it in the next version.
Workarounds:

Use just Enter (without Ctrl) to apply filter criteria. Or click on "Apply filter criteria" toolbar button.
Use mouse double-click to select column name


BeakerExecutor won't run duplicate cacheable steps

Fixes #412

What happens when

The step completes, and later run 2 also wants to run the step?
The step hasn't completed yet, and run 2 wants to run the step?

In (1), run 2 will find the result of the step in the cache when it's trying to figure out if it should should run or not, and so won't run it.
In (2), run 2 will find the existing experiment for the step, and see that it's still running, so will just follow that experiment instead of submitting a new one.


Errors with DATE field as primary key

I have a table with a field of type DATE as a pk.
The build works fine but at run time, working with the object generates errors while trying to convert the pk to string.

Object of class DateTime could not be converted to string

Happens in:

TableMap::addInstanceToPool
Query:findPK

With MySql.

Isn't supported yet.


it not set an arr source in the component;and touch to next image

This issue is a:

Bug report
Feature request
Question / support request
Other

Hi! Thank you for opening an issue. Unfortunately, I cannot understand to what the request or issue here is referencing, so until this is updated to be clearer, I am going to close this.
I will happily reopen the issue if it is made clearer.


.api command is not working

Expected behavior
Should list the apis
Actual behavior
It's showing error API usage not available.
Steps to reproduce

Install the latest taiko
launch repl
run .api

Versions
taiko -v
Version: 1.0.1 (Chromium: 76.0.3803.0) RELEASE

This issue has been verified and found fixed.
Tested version: ef43f50bfcd74ac6512454789151a726adc2b8b7


important-icon not clickable

Expected behavior
In the email list view there is a star icon which appears to be supposed to be clickable. So expectedly, when I click on it the according message should be marked or unmarked (toggle) important.
Actual behavior
Instead once I click on the icon the scroll bar appears and I'm immediately taken to the position on the scrollbar I was (unknowingly) clicking. The same obviously happens when clicking on the star icon while the scroll bar is visible already.
Steps to reproduce

Open the message overview for any email account.
Try to click on the star icon (might possibly work on some phones - doesn't on mine).

Environment
K-9 Mail version: 5.201
Android version: 7.1.1 (Cyanogenmod 14.1-20161225-NIGHTLY)
Phone Model: Oneplus3
Account type (IMAP, POP3, WebDAV/Exchange): IMAP (Though probably not relevant)

duplicate of #894


Update init.py

Updated the init to include the mirror function. This function allows reflection across a line defined by the intersection of two points.

Also updated the tutorial.


Local CI

Hi, I'd like to submit a new CI workflow in order to make future contributions smoother.
CI is based on Nox:

Like tox but config is written in python.
Support both conda and virtualenv without plugins. (use nox -db conda... for conda env).
Elimate the need for multiple conda environments (ci/environment_all_pandas_0_25_3.yml, etc.)

The goals are two-fold:

New-contributor friendly by easily reproducing CI locally.

nox without arguments runs the CI.
Code style, linters, documentation and tests can all be run from nox. nox --list gives all the "sessions" available. I've also added a check to verify that packages defined in setup.py  and requirements-txt.dev are synced.
Running nox locally enables relevant actions: apply black, isort, generate_pip_deps_from_conda.py, build html docs, build html coverage.

Speed up CI (shaved off ~30min) :zap:

Eliminate overlap between extra all and other optional dependencies.
Split independent jobs to reduce overlaps.
Fix conda cache: was cached before creating env, but in practice does not seem to save much time.
Run test_strategies in parallel with pytest-xdist (especially useful on local machine)

Notes:

I moved the tests of extra dependencies in separate folders to easily target specific extras with pytests.
I fixed discrepancies between setup.py requirements and environement.yml/requirements-dev.txt.

sweeeet, this looks great @jeffzi !
CI on Windows is complaining again :/
https://github.com/pandera-dev/pandera/pull/405/checks?check_run_id=1851099847#step:7:76

fyi gonna merge #402 and #401 before this merging this PR, might have to move a few test files around again according to change in directory structure.

Workflow disappeared after this commit https://github.com/pandera-dev/pandera/pull/405/commits/704fcfbe8159bc11a7420e1a95ea427d0954901b...
Unless you have a better idea @cosmicBboy, I will close this PR  and open a new one once #401  is merged.

k, just merged #401


Fixing login page

The problem of the blue background color not being displayed was caused by the container divs margin and the  Components height of 100vh. Form elements got pushed outside of the container div because of that. Set the overflow-y to auto in order to expand the container div. If page shouldn´t be scrollable in mobile landscape view, the my-5 class of the div with the class container would need to be removed.

Super happy I could help out :)


Problem of round-tripping Double values

Problem of round-tripping Double values
Summary
In come cases, the "R" format specifier fails to round-trip a Double value; our recommendation is to use "G17" instead.
Fixes #2919
Details
Some of the Double member documentation noted that "R" doesn't always successfully round-trip values and recommended "G17" instead. But the recommendation isn't consistent: In the standard numeric format strings, the Double structure, and the Single structure topics, "R" was recommended as the way to ensure a Double is round-tripped. This PR makes eliminates the inconsistency.
Internal builds are available as follows:

System.Double structure
System.Single structure
General format specifier, in Custom Numeric Format Strings
Round-trip format specifier, in Custom Numeric Format Strings

Suggested Reviewers
@mairaw @mazong1123 @tarekgh

Is there a way I can look at nicely formatted doc?

Tes @tarekgh. We can post the link here once the build finishes.

@tarekgh here are the links to see the rendered topics:

https://review.docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings?branch=pr-en-us-3101
https://review.docs.microsoft.com/en-us/dotnet/api/system.double?branch=pr-en-us-3101&view=netframework-4.7#Remarks

@tarekgh, I've added links to the sections that I've modified in the Custom Numeric Format Strings topic in the PR description.

For future reference, there is also a rich-diff view for markdown changes:

@rpetrusha I added a couple of comments. other than that it LGTM.

@tarekgh, @tannergooding, I've addressed all of your comments and also made the necessary revisions to the documentation for the Single structure. Changes won't appear, though, until the build completes.

:+1:

This doesn't look as if it ever built. Closing and reopening.

Closing and reopening to restart build.

Looks good now @rpetrusha. Do you want to merge this?

@mairaw, I'll merge it now.


aarch64-unknown-linux-musl double panic on 1.23.0+

This is the current beta channel as of this writing. No idea why it double panics, gonna pin it to 1.22.0

The timing is a bit different, but I wonder if this could be related to rust-lang/rust#48967?


Endian swapping on mac addresses?

A lot of swapendian calls are made, i don't think they are actually needed.
Remove the calls and run unittests.

Done


Replace removed constants with overridable methods

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

We should avoid remove_const, especially when redefining the removed const, as it violates normal assumptions of a "constant".
Surprisingly, there's no cop to disallow this method, except for the narrow case of specs. (There is an open issue for a general DisallowedMethods cop, which has some code snippets, should we want to bother with a custom rule.)

Needs to be merged in sync with https://github.com/Homebrew/homebrew-test-bot/pull/1257 (or, on request, I can update the PR to dual-support constants and methods as an intermediate step.)

or, on request, I can update the PR to dual-support constants and methods as an intermediate step.)

Yes, intermediate step will be necessary to get this merged 👍🏻

Updated PR to maintain dual support until https://github.com/Homebrew/homebrew-test-bot/pull/1257 goes in


/dev/crytpo engine: dereferncing a NULL pointer in digest support code

I've hit a problem with digest support in /dev/crypto engine.
I've run it with gdb, and here's what I've got:
cotequeiroz@gateway ~/src/new/openssl-work $ LD_LIBRARY_PATH=. ./apps/openssl engine -t -c
(devcrypto) /dev/crypto engine
 [DES-CBC, DES-EDE3-CBC, BF-CBC, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-CTR, AES-192-CTR, AES-256-CTR, AES-128-ECB, AES-192-ECB, AES-256-ECB, CAMELLIA-128-CBC, CAMELLIA-192-CBC, CAMELLIA-256-CBC, MD5, SHA1, RIPEMD160, SHA224, SHA256, SHA384, SHA512]
     [ available ]
(rdrand) Intel RDRAND engine
 [RAND]
     [ available ]
(dynamic) Dynamic engine loading support
     [ unavailable ]
cotequeiroz@gateway ~/src/new/openssl-work $ LD_LIBRARY_PATH=. gdb --args ./apps/openssl s_client -connect localhost:443
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./apps/openssl...done.
(gdb) run
Starting program: /home/equeiroz/src/new/openssl-work/apps/openssl s_client -connect localhost:443
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
CONNECTED(0000001F)
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify error:num=20:unable to get local issuer certificate

Program received signal SIGSEGV, Segmentation fault.
digest_cleanup (ctx=<optimized out>) at crypto/engine/eng_devcrypto.c:488
488         if (close(digest_ctx->cfd) < 0) {

I've tried the most obvious workaround, by checking if digest_ctx is NULL and returning 0 or 1, but then it wouldn't connect.  I've tried it with cryptodev 1.9, and master, and with openssl 1.1.1 final and master.
I've tested on mipsel, and others on arm, same problem.  If I disable digest support, then everything works OK, which narrows it down.

Ping @levitte

What happens if you remove line 428, which should look like this?
        close(digest_ctx->cfd);

What I suspect happens is that if a DigestInit fails, the digest contexts are cleaned out and calls the devcrypto cleanup function, which is where you get issues.  So I suspect a double close...

Note that it's possible that I'm fishing in the wrong spot.  I guess I'll have to fire up cryptodev-linux and see if I can trigger that error...  Do you get the same issue if you try some openssl dgst command?

First of all, thanks for looking into this.

What happens if you remove line 428, which should look like this?
        close(digest_ctx->cfd);

I get the same result.
As for the openssl dgst, it works fine, testing all of the digests returned by openssl engine -t -c, and comparing with the library built without the devcryptoeng.
I've added some debugging messages at every _digest_ function, and bailed out of digest_cleanup if digest_ctx == NULL here: https://github.com/cotequeiroz/openssl/commit/6927c212a5c34b472b2e8565d6f2d1b0a6f4a299
Then I've run
openssl s_client -connect localhost:443. If fails, and here's the output: http://termbin.com/qbe5
For comparison, I got back to 3ac6d5ee5372b05aa90cc5c44efbde01bd669e9e, with the old cryptodev engine, added debugging to the digest_  functions as well (https://github.com/cotequeiroz/openssl/commit/d3e82b7f8151e30a984ae3c6b2366fabcdd6cac7), and here's the output of the same command, which suceeds: http://termbin.com/1mab
I can see digest_cleanup being called multiple times with the same session, but the coredump happens the first time in a session in which cleanup was called for the first time.
Cheers

I think I found a clue.  It seems that the error starts at the point where, in old cryptodev, digest_copy is called.  I'm making an assumption here, that in the old code, a new session id is created by copy, where in the new one, the session id is duplicated, and we start to see the double cleanups.

Ah, that makes sense.  PR coming up!

Something isn't quite right. It doesn't crash like it did before, but now it fails:
LD_LIBRARY_PATH=. ./apps/openssl s_client -connect localhost:443
CONNECTED(0000001F)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify error:num=7:certificate signature failure
139866900886528:error:1416D07B:SSL routines:tls_process_key_exchange:bad signature:ssl/statem/statem_clnt.c:2414:
139866900886528:error:02014009:system library:close:Bad file descriptor:crypto/engine/eng_devcrypto.c:495:
---

I ended up posting this in the PR.  BTW, where would you work on this, here or in the PR?

Better to discuss the PR in the PR.