[Bug]: New Listener Client API not properly receiving JSON object from client... I think...

What happened?
In updating my listener client to work with the new Listener Client API, I'm having trouble getting TA to receive my JSON object. I am able to establish the connection just fine, but TA doesn't pull in any of the JSON variables and uses defaults.
From my C# client, the SocketIO emit statement is pretty straightforward (paraphrasing my code for clarity):
foreach (Devices device in deviceList) {
    socket.Emit("listenerclient_connect", deviceObj);
}

Where deviceObj are well-formed JSON strings, and look like the following (using a deviceList containing "Cam 1" and "Cam 2" deviceId's as an example):
{"deviceId":"e8a2bd0b","listenerType":"OpenTally Cam 1","canBeReassigned":true,"canBeFlashed":true,"supportsChat":false}
{"deviceId":"9ff13e3d","listenerType":"OpenTally Cam 2","canBeReassigned":true,"canBeFlashed":true,"supportsChat":false}

However, TA establishes the connections with default listenerclient_connect variables:

I have also tried slightly different client syntax like the following with the same issue:
foreach (Devices device in deviceList) {
    client.listenerType = "OpenTally " + device.name;
    client.canBeReassigned = true;
    client.canBeFlashed = true;
    client.supportsChat = false;
    socket.Emit("listenerclient_connect", device.id, listenerType, canBeReassigned, canBeFlashed, supportsChat);
}

Any tips to help me debug?
Version
3.0.1
Distribution
Desktop
OS
Windows
What browsers are you seeing the problem on?
No response
If applicable, What Listener Clients are You Using?
No response
TallyArbiter configuration
{
  "security": {
    "username_producer": "producer",
    "password_producer": "12345",
    "username_settings": "admin",
    "password_settings": "12345"
  },
  "cloud_destinations": [],
  "cloud_keys": [],
  "device_actions": [],
  "device_sources": [],
  "devices": [
    {
      "name": "Cam 1",
      "description": "Cam 1 Tally",
      "linkedBusses": [
        "e393251c",
        "334e4eda"
      ],
      "enabled": true,
      "id": "e8a2bd0b"
    },
    {
      "name": "Cam 2",
      "description": "Cam 2 Tally",
      "linkedBusses": [
        "e393251c",
        "334e4eda"
      ],
      "enabled": true,
      "id": "9ff13e3d"
    }
  ],
  "sources": [],
  "tsl_clients": [],
  "tsl_clients_1secupdate": false,
  "bus_options": [
    {
      "id": "e393251c",
      "label": "Preview",
      "type": "preview",
      "color": "#3fe481",
      "priority": 50
    },
    {
      "id": "334e4eda",
      "label": "Program",
      "type": "program",
      "color": "#e43f5a",
      "priority": 200
    },
    {
      "id": "12c8d699",
      "label": "Aux 1",
      "type": "aux",
      "color": "#0000FF",
      "priority": 100
    },
    {
      "id": "12c8d689",
      "label": "Aux 2",
      "type": "aux",
      "color": "#0000FF",
      "priority": 100
    }
  ],
  "externalAddress": "http://<IP_ADDRESS>:4455/#/tally",
  "remoteErrorReporting": false,
  "uuid": "1a2d8c40"
}

Relevant log output
[12/16/21 12:19 PM] Listener Client Connected. Type: client Device: Cam 1
[12/16/21 12:19 PM] Sending device states to Listener Client: 4cc5c237 - Cam 1
[12/16/21 12:19 PM] Listener Client Connected. Type: client Device: Cam 1
[12/16/21 12:19 PM] Sending device states to Listener Client: 4cc5c237 - Cam 1
[12/16/21 12:19 PM] Sending device states to Listener Client: 9258a705 - Cam 1

Error stacktrace (if applicable)
No response

Wondering if you could run TA from source and console log what is being received. Maybe it’s not being parsed as an object for some reason.

Okay @josephdadams, I have had the most busy Dec - Feb with work I think I've ever had. Things are finally slowing down again so I'm getting back into this.
I had a chance to rebuild TA from source in a dev environment and add an extra line for debugging. TA is indeed receiving my JSON objects as well-formed, but it's still only recognizing it as the same device in TA's UI. Here's the output of TA's log upon connect:
[2022-03-02 11:16:53] info: Received JSON object: {"deviceId":"7714064f","listenerType":"OpenTally_Cam_1","canBeReassigned":true,"canBeFlashed":true,"supportsChat":false}
[2022-03-02 11:16:53] info: Listener Client Connected. Type: client Device: Cam 1
[2022-03-02 11:16:53] info: Sending device states to Listener Client: 1337566d - Cam 1
[2022-03-02 11:16:53] info: Received JSON object: {"deviceId":"3bcc67eb","listenerType":"OpenTally_Cam_2","canBeReassigned":true,"canBeFlashed":true,"supportsChat":false}
[2022-03-02 11:16:53] info: Listener Client Connected. Type: client Device: Cam 1
[2022-03-02 11:16:53] info: Sending device states to Listener Client: 1337566d - Cam 1

Then in TA's UI still only a duplicate of Cam1 is seen, and it's not reassignable despite canBeReassigned=true:

Okay I think I have been able to get it working. The issue is indeed with TA, for some reason the JSON isn't being parsed. I added a line of code within the socket.on('listenerclient_connect', function(obj: ListenerClientConnect) { } function to basically re-parse the JSON as it doesn't seem to be parsed the first go around. Would love to have someone take a look and see if there is a more elegant solution than what I've implemented.
PR #393

Closing since this looks like #393 was merged...


Tss enhancement implementation plan

Related sub issues:
https://github.com/bitnetworkio/bitnetwork/issues/9

Support full node(block sync) - qingrui.shen
Full node needs to be supported for state transition
Tss manager - fletcher.fan
Websocket Server
Request Acceptor
Accpet the request for signing

tx batches need to be submitted to DA
state batches(execution results) need to be submitted to Layer1
from batch submitter
Signing Task Controller
Get the requests to be handled
Confirm the tss members what will join the signing task corresponding to the event via communicating with each tss node
Retrieve the signature by dispatching the signing task to tss members
Govern
Tssnode liveness management
Collect the malicious behaviors of tss nodes, and build the the transaction to submit the slashing tx to Layer1

Tss node - jay.liu
Websocket client
Tss Core
p2p communication
tss algorithm
Request Validation
Batch submitter - Shijiang.Guo
Ask tss manger to generate the signature for tx batches and state batches.
L2geth - Shijiang.Guo Corey.zhang
Fees calculation
Record fees with block ID in TssRewardContract after each block
Contacts

Tss nodes selection - Shijiang Guo, kuk oo

Tss staking contract

Stake bit for selection
Tss members confirm
Tss CPK confirm

Incentive - qingrui.shen fletcher.fan

TssRewardContract(L2):

record tss nodes reward for each block
claim reward for tss nodes

provide entrance for initiating L2ClaimTssReward message(claim reward payload on L2), and calling sendCrossDomainMessage
SCC adjustment

Slashing - Shijiang Guo, kuk oo
Contract(L1) for recording malicious behavior of tss nodes, and slashing stakes for the malicious tss node.

Related sub issue about tss node:
#10


EVP_RAND_CTX_new documentation

EVP_RAND_CTX_new needs to note that the parent random should have locking enabled before any child is created.  A parent must be lockable if it has more than one child.  Not doing so is an error.
Refer: https://github.com/openssl/openssl/pull/13660#discussion_r560847550

Having the code check that the parent can be locked and return an error if not is not correct.
E.g. a parent with a single child doesn't require locking.

Having the code check that the parent can be locked and return an error if not is not correct.
E.g. a parent with a single child doesn't require locking.

A parent must be lockable if it has more than one child

Presumably this is only the case if the children can be accessed concurrently.

A parent must be lockable if it has more than one child

Presumably this is only the case if the children can be accessed concurrently.

Is there also a risk of concurrent access for direct output from the parent and use by the child?

I'm not sure I understand the question.

It may not be a sensical question, so that's understandable, and sorry for being confusing.  (I haven't gotten to look at the guts of EVP_RAND_CTX.)
But basically, we have a setup where we have a chain or tree of RNGs, with the output of one ("parent") used as input to another ("child").  At some point, certainly in the child, the output of an RNG is used directly by the application.  If the output of a parent RNG is used directly by the application, then we need to consider the case of concurrent access from the application making direct requests to the parent and the child making requests to the parent.  If we have something in place that prevents the output of the parent from being exposed directly to the application, then there's no issue -- I just don't know because I haven't had a chance to look.

So long as the parent has had locking enabled, it's all good.  For the built in trio of DRBG's locking is set up properly but if you are setting up your own chains, it will be up to your application to enable it.


Update from Code For America

Pulls in the following PRs from upstream:

https://github.com/codeforamerica/ohana-api/pull/415 (Use QuotaGuard to avoid geocoder rate limits)
https://github.com/codeforamerica/ohana-api/pull/416 (Fix broken headings in Markdown files)
https://github.com/codeforamerica/ohana-api/pull/418 (Update setup_heroku script)
https://github.com/codeforamerica/ohana-api/pull/421 (Expand the use of i18n)
https://github.com/codeforamerica/ohana-api/pull/422 (Remove schema.rb)
https://github.com/codeforamerica/ohana-api/pull/423 (Update gems)

Coverage decreased (-0.0007%) to 99.367% when pulling 1afb30d77481d2d9c65faea561b7f793f90e65a3 on update-from-cfa into dce34cd9d5b611a04b3a86ff0995040f33491e2a on master.


Migration unsuccessful with transformEntries because "Cannot edit archived" and "Cannot publish archived"

I'm trying to do a migration which create a fields and then transform entries creating values for the new field created before.
Expected Behavior
Run the migration, create the field, fill it with the values I create.
Actual Behavior
Field is created correctly, values are generated correctly, but the migration fails because it try to publish an entry which is in status archived.
$ node migrate.js --portal tcom --env test --migration migrations/3.13.0.js
The following migration has been planned

Update Content Type pack

  Create field servicesDescription
    - name: "Services Description"
    - type: "Text"

Publish Content Type pack
Transform entries for pack
  - from: services
  - to: servicesDescription
? Do you want to apply the migration Yes
 √ Update Content Type pack
 > Transform entries for pack
   × Making requests (48/48)
     → Batch failed
🚨  Migration unsuccessful
Batch failed

Error: {"status":"Bad Request","message":"Cannot edit archived","details":{},"url":"https://api.contentful.com:443/spaces/fzchbmaavok4\\environments\\develop\\entries\\2iqxnK1F1aakq24U4C8CSq"}

Error: {"status":"Bad Request","message":"Cannot publish archived","details":{},"url":"https://api.contentful.com:443/spaces/fzchbmaavok4\\environments\\develop\\entries\\2iqxnK1F1aakq24U4C8CSq\\published"}

I have no control on the entries status with the transformEntries migration function. I just provide the transformEntryForLocale function.
So, how can I run this migration skipping the archived entries?
It actually works for the entries that are not archived but the error message is shown and it says "migration unsuccessful", even if it is just partially unsuccessful.
Possible Solution
Parameters on the transformEntries function for choose entries status or just skip the archived entries and return a success message.
Steps to Reproduce
Run any migration with transformEntries function where there are some archived entries.
Environment

Node Version: 8.11.3
Package Manager Version: 5.6.0
Operating System: Windows 10 64-bit
Package Version: 0.10.0

@Khaledgarbaya have there been any progress on this?

This should be fixed by https://github.com/contentful/contentful-migration/pull/143

I think this will need a separate fix from #143
I'm not sure if there is a use case for deriving things from archived entries, but I could imagine there being one. The very simplest way would be to simply filter out any archived entities during fetching.
However, if anyone would have a use case for deriving from archived entities as well, we'll have to make it a bit more complicated than that.
Probably the best in that case would be to filter this in the transform/derive action itself where getEntriesForContentType gets called since it'll be quite a bit more complicated to change the fetching code to be aware of when archived entries might be needed and when not.
Then we will need a new config option for includeArchived, but only for the derive type of actions.
I think I'd prefer if we could simply skip archived entities altogether, and only introduce this as an explicit option later in case someone really needs to derive something from archived entities without moving them back into a draft state.


Split Project2015To2017 into Core and Migrate2017

Move almost everything to a new Core project
Move VS15-related transformations to Migrate2017.Library
Make ProjectConverter.Convert an extension method (95% compatible, new optional/recommended ILogger parameter added)
Retain umbrella-project Project2015To2017 to preserve NuGet package
Move all common properties to Directory.Build.props
Give Project2015To2017Tests a proper name with a dot
Update external NuGet dependencies

P.S. don't worry about 191 changed files - that's mainly moved files.

Since no issues are raised, I'll rebase this against latest master and merge this later today.


[QUESTION] Display gridlines in excel file

Prerequisites

[ x ] Have read and understood: https://github.com/Maatwebsite/Laravel-Excel/blob/3.1/.github/SUPPORT.md
[ x ] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[ x ] Checked that your question isn't already asked before.
[ x ] Filled in the entire issue template

Versions

PHP version: 7.2.33
Laravel version: 6.0
Package version: 3.1

Description
I want to show the gridlines in an exported xlsx file. By default the gridlines do not appear. Is there a function to show the gridlines?
The following is the view file.
Any advice would be much appreciated.
Thanks.
Additional Information
@php
    $checked_item_list = ssget($ui_id, 'checked_item_list', array());
@endphp

        @foreach ($checked_item_list as $name)
            {{ __("player.{$name}") }}
        @endforeach

    @if (isset($players))
        @foreach($players as $player)

                @foreach ($checked_item_list as $name)
                    {{ $player[$name] }}
                @endforeach

        @endforeach
    @endif

Make sure you always check the PhpSpreadsheet for missing functionality: https://phpspreadsheet.readthedocs.io/en/latest/topics/recipes/
$sheet->setShowGridlines(true)


ZEB release timeline?

Hi, great work!
I'm wondering if you have a timeline for the release your proposed benchmark.
Personally I think this is more important than releasing the training code.
I've personally had some issues even downloading the related training sets (e.g. GL3D seems to be down now?).
Maybe authors of those datasets could allow you to bundle only the data used for the benchmark into an easy download (perhaps with some LICENSE restrictions)?

Hello, Johan,
I really like your DKM and RoMa. Their high performance is impressive.
I am eager to release all the code related to gim, including ZEB, as soon as possible.
However, I have been busy with matters related to my doctoral graduation recently, including my thesis and oral defense.
Therefore, as soon as I have some free time, I will continue to push forward with the open source work of gim.
I am glad you are interested in ZEB. Please wait a little longer. I really appreciate your interest and support.

Hello, @Parskatt
Sorry for keeping you waiting. I just released the test data and scripts for ZEB. If you encounter any issues during use, please let me know, and I will resolve them as soon as possible. Thank you for your patience. 🤗


Add "BeOurFriends" section

Description
The section that starts with "מה תקבלו מלהיות חברים בקהילה שלנו", under the quote section.
make sure to follow the figma design.
Relevant files:

components/Home/BeOurFriends.tsx
app/page.tsx

Screenshots
No response
Additional information
If/when creating sub components is necessary, create a new folder called "BeOurFriends" and insert the BeOurFriends.tsx in there, together with all related sub components.

I will take this

you're assigned, good luck @hilell-elsh !


usage for hiearchy accounts

hi
i have to tried to list the accounts in my mcc using:
use Edujugon\GoogleAds\GoogleAds;
use Google\AdsApi\AdWords\v201809\mcm\CustomerService;
use Edujugon\GoogleAds\Session\AdwordsSession;
$userRefreshCredentials = [
    'clientId' => config('google-ads.production.clientId'),
    'clientSecret' => config('google-ads.production.clientSecret'),
    'refreshToken' => config('google-ads.production.refreshToken')
];

$adWordsServices = new GoogleAds();
$session = (new AdwordsSession())->buildWithOAuth(config('google-ads.production.developerToken'),$userRefreshCredentials);
$managedCustomerService = $adWordsServices->service(CustomerService::class, $session)->getService();
$page = $managedCustomerService->getCustomers();
i get this response:
Argument 1 passed to Google\AdsApi\AdWords\AdWordsSessionBuilder::withOAuth2Credential() must implement interface Google\Auth\FetchAuthTokenInterface, array given, called in /home/glanaj/projects/neon/vendor/edujugon/laravel-google-ads/src/src/Session/AdwordsSession.php on line 90

Hi @gezimapi ,
Make sure that your userRefreshCredentials is an instance of \Google\Auth\Credentials\UserRefreshCredentials

Hope this code snippet helps:
use Edujugon\GoogleAds\Auth\OAuth2;

$oAuth = new OAuth2();

$userRefreshCredentials = $oAuth->userCredentials([
    'clientId' => 'XXX',
    'clientSecret' => 'XXX',
    'refreshToken' => 'XXX'
]);

hi ,
Now it works , i have multiple MCC can I set the clientCustomerId to get  only the accounts of one MCC.
Thx in advance


Add support for “yeelight k series wall switch”

https://home.miot-spec.com/spec/yeelink.switch.ylsw7
https://home.miot-spec.com/spec/yeelink.switch.ylsw6
https://home.miot-spec.com/spec/yeelink.switch.ylsw5
https://home.miot-spec.com/spec/yeelink.switch.ylsw4
#1113 #1114 #1098

closes #1113
closes #1114

Thanks!

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v3.3.3


cupy.arange changes system's default encoding

Description
Observed this issue with versions 9.5 and 12.0. On my system (Debian Linux 11.6)
UTF-8 is the default encoding. I've encountered the change of encoding in other situations converting data to/from cupy but the simplest repro is simply calling cp.arange
I first encountered this as an issue with cuDF : https://github.com/rapidsai/cudf/issues/13085
To Reproduce
import locale
import sys

import cupy as cp

print(sys.version_info)
print(cp.__version__)
print(locale.getpreferredencoding()) # UTF-8
a = cp.arange(0, 10)
print(locale.getpreferredencoding()) # ANSI_X3.4-1968

Installation
Conda-Forge (conda install ...)
Environment
sys.version_info(major=3, minor=11, micro=3, releaselevel='final', serial=0)
12.0.0
UTF-8
ANSI_X3.4-1968

Additional Information
No response

Possibly related to https://github.com/cupy/cupy/pull/376 ?

This is not a CuPy issue, but an NVRTC one. Tracked in nvbugs 3833924.

Workaround: https://github.com/NVIDIA/cuda-python/issues/29#issuecomment-1293648955


AddRef the COM ref instead of having a foregroundHandlerCount

Description: Avoid using the foregroundHandler count and use the AddRef everytime we associate a handler to the channelUri which makes the design cleaner.

Not using foregroundHandlerCount integer. Using winrt::event bool operator to check if there are regsitered events.


Error when pygments not installed

The library throws if pygments isn't installed on the system, with no way to catch the error.

Any update on this?

Hi, I am trying to run this module and getting error
Code: var highlight = require("pygments").colorize;
var highlight = require("pygments").colorize;

try {
  highlight('puts "Hello World"', 'ruby', 'console', console.log);
}
catch (error) {
  console.error("Error thrown by pygments");
}

Error:
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: spawn pygmentize ENOENT
    at exports._errnoException (util.js:1020:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:367:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
    at Module.runMain (module.js:606:11)
    at run (bootstrap_node.js:389:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:504:3

Can you please help me here.

You need to have the pygments tool installed along with this library.


(feat) Stabilize dependency

Stabilized the iron dependency so we can cut a release.

Merging since it's trivial and passes.


Feature/mcp hfspace. Suggestion as to whether to extract an AI Category for this and ChatGPT?

Merging as is, but open to suggestions for how to adjust the categorization.


Compatibility with OffsetArrays

I can put OffsetArrays into a ComponentArray, but the offsets are not preserved:
using ComponentArrays, OffsetArrays
B = OffsetArray(randn(6,6), 0:5, 0:5)
C = OffsetArray(randn(6,6), 0:5, 0:5)
V = ComponentArray(b=B, c=C)

B[0,0] # works
V.b[0,0] # ERROR: BoundsError:

Unfortunately this one is kinda on OffsetArrays for not returning an OffsetArray when indexing.
julia> oa = OffsetArray([1, 2, 3, 4], -1)
4-element OffsetArray(::Vector{Int64}, 0:3) with eltype Int64 with indices 0:3:
 1
 2
 3
 4

julia> b = oa[0:2]
3-element Vector{Int64}:
 1
 2
 3

julia> b[0]
ERROR: BoundsError: attempt to access 3-element Vector{Int64} at index [0]
Stacktrace:
 [1] getindex(A::Vector{Int64}, i1::Int64)
   @ Base ./array.jl:924
 [2] top-level scope
   @ REPL[15]:1

There's nothing we could really do other than make OffsetArrays a dependency and maintain methods specifically for it.

And OffsetArrays extension would be nice


itvr 310 - calculate rebate amount

-adds function for getting rebate amount

The most efficient database way would be to collect all application ids from a CRA response, find a queryset using those ids to filter and also specify to load dependent object household member using the ORM https://docs.djangoproject.com/en/4.0/ref/models/querysets/#django.db.models.query.QuerySet.prefetch_related
Then there will only be one database query used to find the data needed for the rebate calculations.

ex: having a funciton somewhere that's taking def (rebate, cra_response):
with rebate -> (orm object with household one to one preloaded),
cra_response -> (only for this orm object's needs ex ([{"sin": "302435839", "year": "2020", "income": "85687"}]
id matching for data parameter purposes happens outside the scope of calling this function


Is it sane to hardcode package versions within the cookbook?

Following on from the spate of bugs opened as a result of the MySQL security fixes that went out over the last few days, I'd like to question the logic of why each package version is hard coded to a specific package? I mentioned this in the 16.04  bug report specifically, but thought it wise to open a specific ticket to discuss this.
It would seem absolutely sensible to give users the option to pin to a specific package via a property of the resource, but surely the default behaviour should be to use the version offered up by the operating system's package manager?
I noticed in another thread that someone has worked around this by passing in :package_version '' to their mysql_server resource, but that doesn't help when other cookbooks utilise it in their own manner (eg the mysql2_chef_gem resource calling mysql_client)

+1 I've just run into this myself, it seems far far too restrictive as it relies on the cookbook maintainers to keep an eye on the latest package versions across every linux distribution and push a new cookbook version each time there's a change. I don't think that's realistic.
Personally I use an aptly mirror to tightly control package versions in our production+dev+test environments to take hard coded version control out of cookbooks which was proving too hard to maintain in my team.

Yes, its insane.
Fastest way to fix it would be to submit a PR.
What is not clear is if there's some reason for it.  In particular I'm worried around keeping the API so that someone can submit major_version "5.6" and get 5.6.x
It looks like some of the shape of the API may be that installing package "mysql" { version "5.6.x.yadda.yadda" } will use the virtual package name to pick the correct mysql-server-5.6 package that offers the "5.6.x" version.  It may be necessary to expand the matching of distro + version to package names in default_client_package_name and default_server_package_name to create functions that return not just the default, but return the correct package name for any major version on any distro.
At any rate, its clear to everyone that this is a bad pattern.

This sounds radical but the obvious solution seems to be to completely eliminate the default_package_version helper, let the package_version property just naturally default to nil.
The version would then default to whatever the distro package managers provide, the latest stable version, which is what we do for everything else anyway.
What am I missing?   My perspective is only MySQL/Ubuntu, perhaps this is not feasible for other combinations?

This seems like the sanest way to fix it - I've manually overridden it with a blank string in my resources. It should be optional rather than explicit.

Isn't the issue here that distros ship multiple different "major_version"s of mysql -- e.g. 5.5.x, 5.6.x, 5.7.x -- and that the cookbook needs to know which version you want in order to set it up correctly and then the package manager needs to install the right "major_version"?
Eliminating the helper gets the common case correct when you just want to take whatever the default is for the distro, but if you want to pick something different from the default then what do you do?
There's clearly other solutions here, though.  One possibility is that you choose either a default of nil (meaning track the default in the distro, and we use some static mapping to know that a given distro defaults to 5.6.x or something) or else you force the user to fully pin the mysql package version "5.7.11-1.el5" and then pull the 5.7 off the start of that string for use as the "major_version".  You could also require the user to specify the package they want to install and to specify the major_version (for all I know maybe you can already do this?  haven't dug into the full shape of the api...)

Certainly in the Debian / Ubuntu world its very rare for a distro to have two major versions of mysql, but if they do then different major versions have different package names; you don't need the explicit minor details of a version number if you do want a specific release. On Ubuntu 16.04 mysql-server-5.7 is the package name and mysql-server also exists as a metapackage which points to the default for the distro.

if you want to pick something different from the default then what do you do?
Just allow the user to pass in a proprety that gets passed to the version property of the package resource? When calling the package resource version isn't a requirement, but it's utilised if it's passed in. As it stands the version is always passed in.

The thing that is frustrating as an end user is that this cookbook seems to have tried to cater for some very complicated edge cases, but instead has actually created more problems for most real world scenarios than it's solved as a result. Lots of other community cookbooks offer similar cross platform installation support without these headaches; in fact this very cookbook used to "just work" in these scenarios. Hopefully we can all come to a common consensus and a bit of refactoring will be all that's needed to make it more usable when the distros push their security updates out.

The problem is that you do need to have the cookbook support people using the different major versions, and you do need to at least optionally support full version pinning.  And I'd agree that its the edge cases that are messing up the cookbook, but I think some of that is based on the shape of the API and that the cookbook is trying to do too much.  For example, if you want full version pinning having to specify both the major version and the exact package version you want to use should mitigate this problem.  Largely its the magic that is trying to convert "5.7" into "5.7.15-0ubuntu<IP_ADDRESS>" which is causing the problem and i'd agree it may be better to just force the user that wants that behavior to specify both.  I think its reasonable to expect people that want to pin to type more and potentially type in redundant information.  However, I don't agree that its that complicated of an edge case -- exact version pinning in production is a pretty basic requirement.
And we may actually be mostly in agreement.  I agree the default_package_version helper needs to go, I just want to make sure that we still support explicit version pins.  I'm also a little worried that the helper fell out of the API design and that the API design may need to change somewhat in order to delete it.
Probably better to discuss this in a PR where there's actual code changes though.  I haven't had the time to tear this cookbook open and figure out what its doing and why, so I can only talk in hand-wavey fashion that simply deleting the helper worries me.  If you submit a PR to delete the helper, then you'll necessarily have to confront any issues that come up and then we can discuss real code, and I might be all worried about nothing...


Add themes example

This is a follow up PR after a discussion with @yyx990803 for a partnership with Creative Tim.
We added a Themes page under Examples with a specific query param for each link allowing to track potential sales coming from Vue.js website.
Vue.js will get 50% of each sale and therefore increase it's Open Collective or Patreon revenue and further support Open Source development.
PR breakdown:

Add new page under "Examples" with Themes
Add new feature that will allow displaying new/updated links by having a red dot near a link

The feature is built in such a way that any link from the navbar can be added

links = [
      {
        title: 'Learn',
        updatedOn: new Date("Fri Mar 1 2019")
      },
      {
        title: 'Examples',
        updatedOn: new Date("Fri Mar 1 2019")
      }
    ]

The red dot will appear for 2 months starting from updatedOn date.
The red dot near the link will disappear as soon as you visit the page and will no longer appear if you visited the corresponding page. This can be used on any links to show that something was updated.
To add a new link go to common.js -> initNewNavLinks and add the link to the array above.
E.g
 {
        title: 'Ecosystem',
        updatedOn: new Date("Sat Mar 2 2019")
 }

Fixed header scrolling and with this occasion updated to smooth-scroll v15.2.1
which supports callback to specify different offsets depending on each link


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #53.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #53

@conda-forge-admin, please rerender

Dear maintainers, this is part of a larger conda-forge-wide cleanup of recipes that were likely using the default channels a while back.
see https://conda-forge.org/docs/user/transitioning_from_defaults/ as to why defaults isn't recommended.
If you require an exception (it doesn't seem like this recipe does) please request one https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/339

Thanks1


uspv: race condition

Hi all,
I've pulled out the upsv package and I'm working to beef it up hopefully to use in OpenBazaar. I'll report bugs as I find them but the first major one I've come across is transactions being sent by the remote peer before the merkle bock is processed.
IngestMerkleBlock parses the block and adds the txid to OKTxids and then TxHandler checks that txid exists in the map before ingesting the tx. If it doesn't exist the tx is rejected. What I'm seeing is TxHandler fires before IngestMerkleBlock is finished causing some txs to be rejected.
I've set it to lock OKMutex when processing the merkle block, which prevents most transactions from being rejected and also prevents the blocks out of order problem. But I'm still seeing some txs being rejected, which I'm not sure yet the cause.

Ah ok just processing all the blocks in the same goroutine solves all the problems.

And it looks like this was my bug as I'm the one who stuck the goroutine in there :p.
Anyway if I find any more issues I will post here.


TransactionalFlow and TransactionalSink support

As a part of issue #36, transactional producer methods are implemented.
They should work in pair with KafkaConsumer.TransactionalSource for exactly once delivery guarantee.
Unfortunately, due to Confluent's driver issue there are missing few important lines in implementation (they are marked with TODO labels). Without them, implementation does not work correctly and tests fail.
With that said, the implementation by itself is finished, and once the transactional support in Confluent driver will be finished we can quickly adopt it. I created issue for that: https://github.com/akkadotnet/Akka.Streams.Kafka/issues/85
For now, I am skipping failing test to let CI checks pass.
P.S. This PR is based on #83 and #84 PRs, so better to merge them first.

@IgorFedchenko more conflicts here

Oh yea, lots of them... Resolved now.


Add Polish translation

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
❌

I just added, not tested.

thks 👍


ng --version reports wrong version number

After installing angular-cli to the latest, the --version command returns version 1.0.0-beta.30 instead of 1.0.0-rc.0
OS?
Windows 10
Versions.
This is what is at issue.
Repro steps.
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli@latest
The log given by the failure.
--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>...
 I update my home machine from 1.0.0-beta.24, and after the update following the above steps, it still says that the version is 1.0.0-beta.24.

Doing ng -v inside the directory of a project will return the local version of the CLI being used, no the global version. This includes folders that have a node_modules folder with the CLI installed in it.
Can you go outside any project directory (say C:\) and try ng -v?

Yes, I am doing this outside a project folder. But, just in case I did it at c:\ and got:
PS C:\> ng -v
angular-cli: 1.0.0-beta.24
node: 6.9.3
os: win32 x64
PS C:\>

It looks like you still have angular-cli installed. Try uninstalling angular-cli and @angular/cli, then reinstalling @angular/cli.
Shout out to @hansl for noticing.

I've done that already, but I'll do it again.

Even after running npm uninstall -g @angular/cli and npm uninstall -g angular-cli then reinstalling, I found that it still didn't work.
I tried an ng -v after uninstalling both, and surprisingly found that it would still output the beta version of angular-cli. I looked in the C:\Program Files\nodejs\node_modules and found a folder called angular-cli. After removing it, and re-installing angular-cli, angular-cli would fail to run afterward.
I gave up, uninstalled nodejs. Deleted C:\Program Files\nodejs and deleted all npm and npm-cache folders from my AppData. Reinstall nodejs, and ran npm install -g @angular/cli@latest.
 I think the answer lies in where that 'angular-cli' folder in 'nodejs/node_modules' came from, and how to properly remove it.

@bklik I know there are cases in windows where npm global installs get out of sync and it really sucks to figure out where the leftover modules are. I think it might be related to nvm.
It's not a CLI issue though... the CLI can't really control that sort of stuff. So in that sense it's not something I want to leave open in this issue tracker.


feat(http-client): content-type detection

Detects the content-type in the response header and sets the responseType accordingly. The mimeType property is also added and holds the mimetype extracted from the content-type.
fixes: https://github.com/aurelia/http-client/issues/34

Would you consider this to be a breaking change? or just enhancements?

i would say just an enhancement because everything works the same like before.
people who were loading anything other than json probably had to use the response property instead of content, now they can use both.

Sounds good. Thanks!
On Mon, Mar 30, 2015 at 11:51 AM, Aaike Van Roekeghem <
<EMAIL_ADDRESS>wrote:

i would say just an enhancement because everything works the same like
before.
people who were loading anything other than json probably had to use the
response property instead of content, now they can use both.
—
Reply to this email directly or view it on GitHub
https://github.com/aurelia/http-client/pull/36#issuecomment-87732000.

--
Rob Eisenberg,
President - Blue Spire
www.durandaljs.com


Configure pre-commit tool for this repo

Rules:

DO NOT commit to master. ever.
ABSOLUTELY NO force pushes allowed for public non-feature branches.
For every feature, create a new branch matching name feature/<issue-number>-<feature-name>.
Submit every feature by creating Pull Request @ github, after that wait for review, fix issues, repeat until approved. If needed rebase the branch on top of master and re-push force it.

[x] I HAVE READ AND UNDERSTOOD THE RULES ABOVE

[x] Install pre-commit locally as follows:

pip install pre-commit
pre-commit install

[x] Create branch called feature/pre-commit-integration
[x] Add .pre-commit-config.yaml config, containing the following hooks:

[x] check-ast
[x] check-yaml
[x] check-merge-conflict
[x] check-docstring-first
[x] debug-statements
[x] double-quote-string-fixer
[x] end-of-file-fixer
[x] flake8
[x] name-tests-test
[x] requirements-txt-fixer
[x] trailing-whitespace
[x] pydocstyle

[x] Check repo using command pre-commit run --all-files, fix all issues and commit fixes as well
[x] Create PR with this branch

@webknjaz https://github.com/kpi-web-guild/django-girls-blog-serhii73/pull/20 - Created the config file.

@serhii73 you wouldn't need to post a comment if you simply linked this issue from PR


Updated reasons for rejection

Context
I want to test this ahead of the next cycle... Just putting this here for now in draft.
Trello ticket here
Changes proposed in this pull request

Guidance to review

Link to Trello card

Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] Required environment variables have been updated added to the Azure KeyVault

@MylesJarvis is this still a thing?

@carlosmartinez yes. I'm shipping at the start of the cycle. I've got a ticket to remind me.

This is now ready for a ✅ . I've spoken to John about it and he's happy with this approach as a test.
We can merge down after that.


Python 3 compatibility

Not extensively tested but I seem to be able to go back and forth. Also note new way to get Python 3 atom/enaml stack and JSONLibrary submodule update.

Coverage increased (+0.1%) to 66.803% when pulling f6055bb4d2700d516ad96c85d824defc2e4aefeb on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

I was able to pip install the dependencies and get it running on OSX for what it's worth:
e.g. pip3 install git+https://github.com/MatthieuDartiailh/enaml.git@python3-parsing
I'm looking into embedding the quince GUI in PyQLab (or visa versa, what better to serve as the node inspector than PyQLab itself?), but looks like the mismatch in PyQt versions will prohibit this for the moment. Seems like it might happen eventually.

Coverage increased (+0.1%) to 66.803% when pulling 2b1717fb70a07d815ed3e44180d17bc48d1ed49b on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

@grahamrow 46c3d97 should fix the kernel issues you were seeing

Coverage decreased (-54.2%) to 12.457% when pulling 46c3d97611d1d632188b8bf4196ef9e053b24775 on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

I'm not sure why this failed unit tests unless it was because conda didn't figure out that it needed to install pyqt. In any case, can we update the Travis script to try both python 2 and python 3 and install the dependencies as you suggest in the new README?

Yep, I'll tackle that.

Coverage increased (+0.4%) to 67.078% when pulling dc47ecfb49a1b18532d316d0a2009e6b73ffd0e2 on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

Coverage increased (+0.4%) to 67.078% when pulling c08ab16176388bcd249fb84ee2bdb95399c52432 on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

Coverage increased (+0.4%) to 67.078% when pulling 69ed6e1a5f1ffe6f5a789da3c820d32720f01b7d on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

Coverage increased (+0.4%) to 67.078% when pulling c7aedc1f02498e014232d5bbe8e99bf579ac0faf on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

Coverage increased (+0.4%) to 67.078% when pulling 23d3fe8add176cf12a79b135fbed0ddd0190a87f on feature/py3-compat into c87969d75e6c83a3d573961a8aa29499efae480e on develop.

@dieris you've probably given this the best real-world workout. Please merge when you're happy.

Coverage increased (+0.4%) to 67.101% when pulling 1603bc5c76b20708bc7b808254b8685469cb7093 on feature/py3-compat into 1d1378122e78dbfeef190a7cb56919c10709b455 on develop.

Coverage increased (+0.5%) to 67.147% when pulling ab2dd50de81c53459c381e21708c6a5303e2c9f7 on feature/py3-compat into 1d1378122e78dbfeef190a7cb56919c10709b455 on develop.

I haven't done through testing but this branch seems to be working for me on Maxwell.

Coverage increased (+0.5%) to 67.147% when pulling 088ba1106e0be13ef46ca95ff3b6b51cd219eb71 on feature/py3-compat into 1d1378122e78dbfeef190a7cb56919c10709b455 on develop.

No I thought you had merged the py3-compat into master.  Seems that wasn't the case.

I'll do a final test before merging. For some reason, I didn't receive any email notifications on this branch in the last 2 days...

I guess I'm still lost...  Wasn't py3-compat on JSONLibraryUtils merged into master?


Add the build configuration

This pipeline configuration builds the application and produces a build for the Release configuration.

This pipeline configuration builds the application and produces a build for the Release configuration.


fix: prevent leaking of -zf-size in -zf-each-breakpoint mixin

Closes https://github.com/zurb/foundation-sites/issues/10818
Note: this also remove some useless logic in @mixin breakpoint

@IamManchanda self-assigned this 2 days ago

poke @IamManchanda


Doesn' t work HACS Music Assistant on restored HAOS

What version of Music Assistant has the issue?
2022.12.1
The problem
Doesn' t work HACS Music Assistant v2022.12.1 on restored HAOS 2023.1.7.
Raspberry Pi 4 rpi4-64 Argon One
Home Assistant OS 2023.1.7
Supervisor 2023.03.1
Operating System 9.5
Frontend 20230110.0 - latest
It used to work fine, but there may have been some error in the acces.
Can it be resolved that until the HA Addon version is stabilized, the HACS version (v2022.12.1) can still be used (e.g. with HAOS 2023.1.7)?
How to reproduce
I restored my previous backup (HAOS 2023.1.7), which still includes the HACS Music Assistant integration (v2022.12.1)
I get the following error message:
Relevant log output
Logger: homeassistant.setup
Source: setup.py:202
First occurred: 7:54:07 PM (1 occurrences)
Last logged: 7:54:07 PM
Setup failed for custom integration mass: Requirements for mass not found<EMAIL_ADDRESS>Full log:
2023-03-15 19:52:44.743 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration mass which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-03-15 19:54:07.531 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration mass: Requirements for mass not found<EMAIL_ADDRESS>

Additional information
No response
What version of Home Assistant Core are your running
2023.1.7
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi

This is strange, restoring the backup should work. We actually had a patch release in january/february.
Are you sure you restored the right backup ? Maybe there is an update waiting in HACS you can install for MA ?
You should be able to run Home Assistant 2023.2.x with Music Assistant 2023.2.1

This is strange, restoring the backup should work. We actually had a patch release in january/february. Are you sure you restored the right backup ? Maybe there is an update waiting in HACS you can install for MA ?
You should be able to run Home Assistant 2023.2.x with Music Assistant 2023.2.1
When reset, HAOS 1.7.2023 and HACS MA 12.1.2022 were loaded.
Unfortunately, MA no longer works, because as soon as HA is available during reset, it gives the above error.
If I delete the MA integration and in HACS, and then want to install it again, it gives the above error.
It used to work until I updated from 1/7/2023 to 3/3/2023.  I restore from backup to no avail.
Currently, HA 2023.1.7 and HACS version 2022.12.1 are up, but they no longer work.
But the addon v2beta doesn't work even with an update.
https://github.com/music-assistant/hass-music-assistant/issues/1144

OP advised this was resolved by rebooting host.


Remove Razor Pages specific things from the MVC (Model-View-Controller) template

Remove https://github.com/aspnet/AspNetCore/blob/a86a811f7b55c03f815b7ac37413a179e6459ba7/src/ProjectTemplates/Web.ProjectTemplates/content/StarterWeb-CSharp/Startup.cs#L123
Remove https://github.com/aspnet/AspNetCore/blob/a86a811f7b55c03f815b7ac37413a179e6459ba7/src/ProjectTemplates/Web.ProjectTemplates/content/StarterWeb-CSharp/Startup.cs#L163

These should only appear in the Razor Pages template

@rynowak pointed out these are probably required for IdentityUI

^^^^

@rynowak does it make sense to wrap these extensions in an (Auth) check?

Sounds like it could be.


Introduce NothingType

So I introduced NothingType, but from what I can tell we're not using this anywhere? This is solely for the benefit of third parties annotating their code to accept NOTHING?

I presume this is based on https://discuss.python.org/t/do-we-need-a-valuealias-in-addition-to-typealias/67609? I guess it needs some docs and a changelog entry?

nudge

Is there any chance at all to test this??


Extend key filtering to nested maps

Hi,
thank you for your work!
I want to suggest to filter invalid map keys also inside nested objects.

Thanks for the contribution @4nduril! Looks good 😎


OS X: downloader GUI crashes in Python 3 when mouse wheel is used for scrolling

I have no idea why is it happening, but when a mouse wheel is used for scrolling the downloader GUI crashes. Keyboard works fine. For Python 3.3 from python.org the exception is the following:
python -m nltk.downloader
showing info http://nltk.github.com/nltk_data/
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/runpy.py", line 160, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/runpy.py", line 73, in _run_code
    exec(code, run_globals)
  File "./nltk/downloader.py", line 2263, in <module>
    halt_on_error=options.halt_on_error)
  File "./nltk/downloader.py", line 656, in download
    self._interactive_download()
  File "./nltk/downloader.py", line 968, in _interactive_download
    DownloaderGUI(self).mainloop()
  File "./nltk/downloader.py", line 1703, in mainloop
    self.top.mainloop(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/tkinter/__init__.py", line 1071, in mainloop
    self.tk.mainloop(n)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfe in position 0: invalid start byte

For Python 3.4 from homebrew the exception is the same.

Looks like this is a Tk issue, solvable by upgrading ActiveTcl:
http://stackoverflow.com/questions/16995969/inertial-scrolling-in-mac-os-x-with-tkinter-and-python
http://bugs.python.org/issue10731
https://sourceforge.net/p/tktoolkit/bugs/2966/


Find the reason attribute when sending topology updates.

The administrative event means an operator executes the action that causes the topology change event, and the network itself generates an operational event.

The 'reason' attribute could not be found, therefore this activity will remain pending in a new pull request.


MouseGuard Localisation

Hello
Could be possible to upgrade MouseGuard Character Sheet to allow translations?

I'll have a look at this ...

done

Thank you a lot! Is it difficult for a githhub newbie to add a russian translation file? Anyway I'll try!
I translate a Roll20 through a main site (Crowdin) and dont understand how quickly a translation become visible for an end user (palyer, DM).

Git is cool and - in my opinion - awkward ... So, of you‘re not familiar with it, it might be easier to send the translation file to someone, who is.
Updates to sheets and translations are published on a weekly base every Tuesday.

I made a translation file ru.json, but now it must be replace to folder "translations"..

@JaegersNet thanks for doing those updates. I've been busy for a bit with life but I love seeing that the MouseGuard sheet is still getting updated. I had a request come in for a Korean translation also so I'll put a PR up for it as soon as I get the translations file. @Gumeg, if you want to send me the file I can submit a PR for you.
Just take a look at https://github.com/Roll20/roll20-character-sheets/blob/master/MouseGuard/translations/ru.json for an example on how to format the document.

@Gumeg Do you want to do translations? Email me at<EMAIL_ADDRESS>and I'll get you an invite to Crowdin. Crowdin is an easy way to add translations and you wont need to know json. :)

@Gumeg Do you want to do translations? Email me at<EMAIL_ADDRESS>and I'll get you an invite to Crowdin. Crowdin is an easy way to add translations and you wont need to know json. :)

Thanks, but i'm allready in. =)


beta.5 Observable typings are missing

RxJS version:
5.0.0-beta.5
Code to reproduce:
Create a simple project using webpack
Actual behavior:
ERROR in webapp/node_modules/rxjs/Observable.d.ts
    (12,6): error TS2304: Cannot find name 'Symbol'.

    ERROR in webapp/node_modules/rxjs/Observable.d.ts
    (15,42): error TS2304: Cannot find name 'Iterable'.

    ERROR in webapp/node_modules/rxjs/Observable.d.ts
    (1,1): error TS2654: Exported external package typings file cannot contain tripleslash references. Please contact the package author to update the package definition.

Additional information:
Not happening if I roll back to beta.4

Thanks, it's related to https://github.com/ReactiveX/rxjs/issues/1568 and PR https://github.com/ReactiveX/rxjs/pull/1582 trying to resolve this issue.

+1

was having this same issue with 5.0.0-beta.2, switching to beta.4 until beta.5 is fixed

Let me close this issue by https://github.com/ReactiveX/rxjs/pull/1582. To try out this with npm package, may need next version publish though. For now, I'd suggest to use b4 until next version published or directly use master branch if available.
Apologies for troubles with new version, will think about more bulletproof way of test / verification per changes in further.

+1

I encountered this issue. RxJS version is 5.0.0-beta.4.
My package.json & tsconfig.json is https://gist.github.com/kubosho/17b5016e4427726381051cf58efb6203#file-package-json


A running version

Can I see a running version of this anywhere?

I'll see if I can get a more permanent solution, but I temporarily set up a demo site here: http://ucfpawn.dyndns.info:3010/
I also updated the README and included step-by-step instructions on how to easily launch your own version.

Anyone have this running somewhere pls?

@milezzz It's a pain to maintain a server for a demo site.  Is there any reason why you can't follow the README and see a demo site running on your local machine?

Is there any reason why you can't follow the README and see a demo site running on your local machine?

http://plbz.it/2jwE3uy

Haha, fair enough. What if I made a bash script so you just have to clone
the repo and run the script to get a demo site?  I can even open the
browser window for you.
On Mon, Jan 9, 2017, 3:45 PM (︶︹︺<EMAIL_ADDRESS>wrote:

Is there any reason why you can't follow the README and see a demo site
running on your local machine?
http://plbz.it/2jwE3uy
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MisterTea/MemeGenerator/issues/1#issuecomment-271444021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASuv0gEeEITUgSOESJ0fvKSxHdyWtE4ks5rQsavgaJpZM4GBtYB
.


Taskbar styles only applied after switching desktop

When switching desktop using three fingers swipe, the taskbar from the new desktop first has default Windows styles with no TaskbarX styles. Only after screen has appeared, new styles are applied and icons are centered. So there is a 1-2sec delay before the taskbar gets the expected styles.

This is what I mean by switching desktops: https://www.youtube.com/watch?v=4tnmXFwLtK0
TaskbarX: <IP_ADDRESS>
Windows: Microsoft Windows [version 10.0.19041.329]
Machine: Surface Book

I only see this issue when switching desktop using three fingers swipe, when I use the Keyboard shortcut (Ctrl + Win + left/right arrow), it works fine.

@warpdesign Did you find a fix yet?

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


Undo/Redo functionality

Its need at least undo/redo for manipulating transforms, adding components, creating entities

This seems to be hard, any ideas on how to do it?

Half done already in the develop branch. The main idea is to automatically track changed components, label them and after editing is complete, save their state to the world change chain. This chain will allow to move undo/redo manner between saved component states. The main difficulty, though, is recreating multiple objects at once with internal references and parental relationships. I'm still thinking about one of two approaches: keep a full "copy" of the world in an internal cache, or delete objects only through signals so that they can be stored in the world change chain.


Resolve libpng warning

Upon startup while using the Qt version, the error libpng warning: gAMA: gamma value out of range is printed several times.
(libpng warning: iCCP: known incorrect sRGB profile also appears from time to time while in solar system mode.)
It seems to be caused by the loading of the images used for the showConstellationPictures setting, and from some Googling it seems like the error is a problem with Qt, though I don't know exactly what. ~If it's not fixable, we could at least hide it by using the javaScriptConsoleMessage() function qt.py by adding libpng not in message to the if condition.~

See https://github.com/WorldWideTelescope/wwt-web-client/issues/177 for the gamma issue

@ojustino will investigate whether we can hide the warnings in the mean time.

You were right that the warnings aren't coming from the JS console, so my method of muting them didn't work. After some more searching it seems like the only way to get rid of this error is to fix the png files that are causing it in the first place, confirming that this is an upstream issue.

Closing this since this is basically out of pywwt's hands, and WorldWideTelescope/wwt-web-client#177 captures the bug in the right place.


Updates React Native with TypeScript post with Babel 7 instructions

Good morning! I wrote this blog post earlier this year, but Babel 7 has since been released with builtin TypeScript support. Since this blog post has become very popular among people looking for TypeScript with React Native, I have been receiving an increasing number of requests from the community to update the blog post to point to Babel 7 instructions.
This pull request adds a section to the introduction of my blog post that gives instructions for Babel 7, includes a brief description of its limitations, and points to workarounds written by @damassi. /cc @ds300 who wrote react-native-typescript-transformer.

Ah awesome, thanks Ash! Gonna review ASAP

Good morning! Looks like these changes are acceptable – could we get this PR merged today? People keep emailing me about the post being outdated 🙈

(sorry Ash, I approved it and forgot to merge 🤦♂ too many green buttons to press)

Haha no worries! GitHub really needs a "merge on green" feature 😄


Enhancement Request: Automatic Disappearance of Tooltips After Hovering for a Specified Duration

Feature Description:
Currently, the tooltip component offers various options for controlling its behavior, such as its position, offset, and visibility triggers. However, it lacks the ability to automatically hide after a specified duration of hovering over the target element.
Proposed Solution:
Introduce a new property, such as hover_duration, to the tooltip component. When this property is set, the tooltip should remain visible as long as the user hovers over the target element. After the specified duration elapses, the tooltip should automatically disappear.
Benefits:
Enhances user experience by providing a more intuitive behavior for tooltips.
Allows developers to easily control the duration for which tooltips remain visible during hovering.

This is a good idea. However, keep in mind that DMC is just a thin wrapper around Mantine which does not seem to support this out of the box. I would suggest to request the enhancement in the upstream Mantine library.


Given Node Pubkey is Invalid

I've been having issues ever since I had my channels force close. Originally I was using Mutiny on my android, but when I attempted internal transfers to phoenix wallet, I had continued time outs. Someone ended up telling me that you will have issues sending 2 self custodial lightning node wallets to each other because they both have to be running. Now I know that, but since then I restored my wallet on my desktop browser (brave). Took a while for proper funds to show up. I just re-synced the on-chain wallet via the debug tools and that refreshed my on chain balance. But now when I try to swap to lightning I get this error: "The given node pubkey is invalid"

Having a hard time sending funds out of lightning. Failed to find route.

Can you share logs again and maybe the destinations you are trying? We can take a look.

It looks like you tried emailing this in, could you go through the github website to attach the file? It looks like it is missing a lot of logs, I don't see any payments being attempted here.

everything seems to be working now. restarted the router and refreshed the wallet. Thanks

Glad you got it


Only update modified_by when an editable field has changed

Fixes #286
Signed-off-by: Rick Elrod<EMAIL_ADDRESS>

I'm fine with doing the more generalized solution in this PR and making sure at least one field in update_fields is editable, if we have an update_fields. But what happens if we aren't given update_fields? What if someone just does
animal.name = "Fredrick"
animal.save()

In that case, we want to update modified_by, but we wouldn't have any way of knowing that we need to.
I think to solve this we'd have to store the values of each field and manually compare that on save if update_fields is None.

I even tried using a signals-based approach, but I don't think that was any better, and everything you read online says "don't use pre_save to update field values in the same model", override save() instead.
But the issue is we have no good way to know which fields changed from save(). This problem is trivial if we assume update_fields is always set. But in the case where it's not set, how do we know if the changed fields are, in fact, editable fields?
I feel like I absolutely have to be missing something here.

I approved, and I just want to leave a comment to set reasonable expectations. Forget the first part of your snippet. What if you load animal and then making no changes just do animal.save()?
I expect that in that case modified_by does get updated. It is not reasonable to detect what diff happened. Django itself doesn't do it, and in other cases where I've seen the app do it, it leads to extra queries, extremely unexpected behaviors, and conflicts with multiple processes working on the same objects.
But return to my example of JobTemplate. It is extremely reasonable to expect (demand!) that the task system always uses update_fields. If this is the system doing something, it should follow best practices. And for fields like last_job in particular, your action should go to great lengths to isolate the change you are making.

This has been updated to use editable when update_fields is given.

@AlanCoding are you good with this new approach?


Subscribe to value changes

I've experienced a problem with the subscription to a specific node with a leaf. I've use the following code, slightly adapted from your example.
I do get the node and its child leaf, but when I change the value of the leaf I do not get an update. Am I doing something wrong or is there an error in the implementation. Most likely I'm wrong and forgot something.
I've had the same results on the user labels of Lawos PowerCore Sources and on Matrix Labels by Riedels Mediornet.
On the Riedel Matrizes the following code worked perfectly.
Looking forward to your solution.
import {EmberClient} from "emberplus-connection";
import {FieldFlags} from "emberplus-connection/dist/model/Command";

const client = new EmberClient(IP, 9000);

const initember = async (): Promise<any> => {
    client.on("error", e => {
        console.log(e);
    });
    await client.connect()
// Get Root info
    const req = await client.getDirectory(client.tree)

    return await req.response
}

const testMethod = async (path: string): Promise<any> => {

    const testNode = await client.getElementByPath(path).then(async (node) => {
        console.log("Get Node: \n")
        console.log(await node)
        return (
          await client.getDirectory(await node, FieldFlags.All, (update) => {
                console.log(update)
            }
          )
        ).response
    }).catch(() => console.log(path + ": Node does not exist."))
    return testNode
}

//Riedels Matrix label
initember().then((x) =>
    testMethod("<IP_ADDRESS>.1.0").then((x => console.log(x))))

Hi,
I've tried to reproduce against the provider from this library but await client.getElementByPath('1.1.1', (v) => console.log(v.contents.value)) works perfectly fine for me. AfaIk we also use subscriptions in production with a lawo mc2 and a powercore.
Can you provide a pcap file with the socket communication?

I captured the traffic to the "Riedel MicroN" with wireshark. Hopefully that might help you solve my problem.
Ember-Communication-Riedel-Mediornet.pcapng.zip

Made further tests with the original Lawo implementation in C. There does the GetDirectory work for value changes of the labels.

And I still have troubles querying the PowerCore Matrix. I get the following error:
error.txt
used this source code:
import {EmberClient} from "emberplus-connection";

const client = new EmberClient("<IP_ADDRESS>", 9001);

const initember = async (): Promise<any> => {
    client.on("error", e => {
        console.log(e);
    });
    await client.connect()
// Get Root info
    const req = await client.getDirectory(client.tree)

    return await req.response
}

const testMethod = async (path: string): Promise<any> => {

    return await client.getElementByPath(path, (v) => console.log(v)).then( node => {
        client.subscribe(node, n => console.log(n))
    })
}

//Path to PowerCore Matrix
initember().then(() =>
  testMethod("1.3.1").then((x => console.log(x))))

could you verify this behavior in your environment?

Sorry, I haven't been able to look at this yet. Hopefully soon!

Hi, with a build from latest master i am getting the same error when trying to access a matrix node on a DHD device:
Error (InvalidAsn1Error]: Expected Oxa0: got 0x0
at newInvalidAsn1Error (/.../node_modules/asni/lib/ber/errors.js:7:13)
at Reader. readSequence (/.../node_modules/asn1/lib/ber/reader.js:188:11)
at decodeMatrixContents (/.../node_modules/emberplus-connection/dist/encodings/ber/decoder/Matrix.js:142:28)
at decodeMatrix (/.../node_modules/emberplus-connection/dist/encodings/ber/decoder/Matrix.js:36:61)
at decodeGenericElement (/.../node_modules/emberplus-connection/dist/encodings/ber/decoder/Tree.js:46:42)
at decodeRootElements (/.../node_modules/emberplus-connection/dist/encodings/ber/decoder/Tree.js:164:24.
at berDecode (/.../node_modules/emberplus-connection/dist/encodings/ber/index.js:59:52)
at S101Codec.<anonymous> (/.../node_modules/emberplus-connection/dist/Ember/Socket/S101Socket.js:32:48)
at S101Codec.emit (node: events: 513:28)
at S101Codec.handleEmberPacket (/.../node_modules /emberplus-connection/dist/S101/S101Codec.js:151:14)

i have the same problem with LAWO vpro8, Riedel micron and LAWO PowerCore

@Nico96R is the error you're seeing the same as with the DHD device? (i.e. Expected 0xa0: got 0x0)
NRK is not currently using subscriptions on matrices so that explains why we haven't seen this. I'm not sure if I can get this prioritised, and I'm also not very familiar with the workings of the asn1 library we use so I'm not sure how hard it is to fix.

Yes it is the same error. The error hasn’t changed since last year.

And I still have troubles querying the PowerCore Matrix. I get the following error: error.txt used this source code:
import {EmberClient} from "emberplus-connection";

const client = new EmberClient("<IP_ADDRESS>", 9001);

const initember = async (): Promise<any> => {
    client.on("error", e => {
        console.log(e);
    });
    await client.connect()
// Get Root info
    const req = await client.getDirectory(client.tree)

    return await req.response
}

const testMethod = async (path: string): Promise<any> => {

    return await client.getElementByPath(path, (v) => console.log(v)).then( node => {
        client.subscribe(node, n => console.log(n))
    })
}

//Path to PowerCore Matrix
initember().then(() =>
  testMethod("1.3.1").then((x => console.log(x))))

could you verify this behavior in your environment?

Unfortunately NRK currently does not have the capacity to look at this issue further, as always we are more than happy to accept pull requests regarding this issue.

I think #38 should fix this problem. It did for me.
The problem is, that the current release doesn't send the "Get Directory" request down until the parameter. It only requests the parent of the of the last given path element.
If you requested path "<IP_ADDRESS>.5" and 5 is the parameter, the last "getDirectory()" was for node 4 instead of 5.


Implement Clear Data Activity

IMPORTANT: Where possible all PRs must be linked to a Github issue

Set android:allowBackup manifest flag to false
Set android:hasFragileUserData to true
Add DataActivity to control app's data clearing action
Add android:manageSpaceActivity manifest setting and activity

Engineer Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
[ ] I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

[ ] I have verified Unit tests have been written for any new feature(s) and edge cases
[ ] I have verified any strings visible on UI components are in the strings.xml file
[ ] I have verifed the CHANGELOG.md file has any notable changes to the codebase
[ ] I have verified the solution has been implemented in a configurable and generic way for reuseable components
[ ] I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

Can you provide the link to the issue?

Yes. To be wrapped up next week


Jessie and node 4.2.1 ?

Hi,
I've just tried installing raspi, however it failed on npm install.
Could there be an incompatibility with Jessie and node 4.2.1 ?
Cheers

Unfortunately node 4 is not supported yet. You can track the upgrade progress at https://github.com/nebrius/raspi-io/issues/35.
In the meantime, I recommend using node 0.12


Crashes when typing in same struct name as field member

Had this happen sometimes.
Take the following example:
enum FooEnum : uint32_t {
    Baz = 0
};

struct Foo 0x1000 {
    int blah;
    int foo_enum_before_i_found_the_enum;
};

Upon trying to insert FooEnum into Foo as a field member, it will crash at this point:
enum FooEnum : uint32_t {
    Baz = 0
};

struct Foo 0x1000 {
    int blah;
    Foo foo_enum_before_i_found_the_enum;
};

Bug was in SdkGenny (fixed in https://github.com/cursey/sdkgenny/commit/f605a27557cac0f6765af2be80f7a98cc71847ab). Updated SdkGenny dependency in dea3b97ba8c05d044fc21adef2a3bd5f37eee152.


Feat/overhauled server

Issue
Closes #76
What is changed / added

Changed scraper to now use puppeteer cluster
Cluster instances scrape different pages to scrape more than 60 events concurrently

Screenshots

https://user-images.githubusercontent.com/43979159/140854714-7053f33a-71df-45b9-923c-8a73fec34351.mp4

Oh ok 👍 can you just approve this, I'll change memory in the next pr.

Oh ok 👍 can you just approve this, I'll change memory in the next pr.

for better tracking let's just make the change on this PR, you could just commit the suggestion I made

Oh ok 👍 can you just approve this, I'll change memory in the next pr.

for better tracking let's just make the change on this PR, you could just commit the suggestion I made

Done!


Java 11 jigsaw modules

We are using Java 11.0.1 and Maven 3.6.0.
When trying to build a java module with module-info.java we created and at first lombok didn't work. However after adding annotationProcessorPaths it gets further along but then we are getting:

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /lombok/dummy/ForceNewRound0.java:[1,1] file should be on source path, or on patch path for module

It seems that a problem is with the following lombok code:

    // Force a new round to reset resolution. The next round will cause this method (process) to be called again.
    forceNewRound((JavacFiler) processingEnv.getFiler());

    private void forceNewRound(JavacFiler filer) {
           if (!filer.newFiles()) {
                   try {
                           JavaFileObject dummy = filer.createSourceFile("lombok.dummy.ForceNewRound" + (dummyCount++));
                           Writer w = dummy.openWriter();
                           w.close();
                   } catch (Exception e) {
                           e.printStackTrace();
                           processingEnv.getMessager().printMessage(Kind.WARNING,
                                           "Can't force a new processing round. Lombok won't work.");
                   }
           }
   }

It seems that this is just some hack that is created a problematic java file to force new round of processing. Can this be replaced with some other (internal?) API?
Any chance to get this fixed somehow? Or some working workaround.
There is a workaround with -sourcepath, but it is messing with IntelliJ (I get modules not found).

Sure
Recap of Lombok issues (maven + java 11):

maven surefire problem when running unit tests (WORKAROUND: forkCount = 0)
lombok not picked up as annotation processor (WORKAROUND: add annotationProcessorPaths)
getting file should be on source path (WORKAROUND: add sourcepath ... but problematic in IntelliJ)

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.22.1</version>
                <configuration>
                    <!-- fix for running unit tests ([ERROR] The forked VM terminated
                         without properly saying goodbye. VM crash or System.exit called?)
                         [DEBUG] Error occurred during initialization of boot layer
                         [DEBUG] java.lang.module.ResolutionException: Module lombok does not read a module that exports org.mapstruct.ap.spi  -->
                    <forkCount>0</forkCount>
                </configuration>
            </plugin>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.8.0</version>
                <configuration>
                    <release>11</release>
                    <annotationProcessorPaths>
                        <path>
                            <groupId>org.projectlombok</groupId>
                            <artifactId>lombok</artifactId>
                            <version>1.18.4</version>
                        </path>
                    </annotationProcessorPaths>
                    <!-- this helps when getting error: file should be on source path, or on patch path for module -->
                    <compilerArgs>
                        <arg>-sourcepath</arg>
                        <arg>${project.basedir}/src/main/java${path.separator}${project.basedir}/target/generated-sources/annotations${path.separator}/</arg>
                    </compilerArgs>
                </configuration>
            </plugin>
        </plugins>
    </build>

Another possible workaround with IntelliJ workaround (disable profile: [ ] update-sourcepath-for-lombok in Maven -> Profiles  toolbox).
    <properties>
        <forkCount>0</forkCount>
    </properties>

    <build>
        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <annotationProcessorPaths>
                        <path>
                            <groupId>org.projectlombok</groupId>
                            <artifactId>lombok</artifactId>
                            <version>1.18.4</version>
                        </path>
                    </annotationProcessorPaths>
                </configuration>
            </plugin>
        </plugins>
    </build>
    <profiles>
        <profile>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <id>update-sourcepath-for-lombok</id>
            <build>
                <plugins>
                    <plugin>
                        <artifactId>maven-compiler-plugin</artifactId>
                        <configuration>
                            <compilerArgs>
                                <arg>-sourcepath</arg>
                                <arg>${project.basedir}/src/main/java${path.separator}${project.basedir}/target/generated-sources/annotations${path.separator}/</arg>
                            </compilerArgs>
                        </configuration>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>

Tested with 1.18.6:

sourcepath  is fixed
annotation processing is still required
surefire is still failing due to missing org.mapstruct.ap.spi
(would it be possible to just add dependency for mapstruct-processor to pom?)

Another possible workaround for last error is adding (instead of forkCount = 0 workaround):
	<dependency>
		<groupId>org.mapstruct</groupId>
		<artifactId>mapstruct-processor</artifactId>
		<version>1.2.0.Final</version>
		<scope>provided</scope>
	</dependency>

Duplicate of #2231


added a resolvedtiles feature

including a class and a first api call to use in grabbing unresolved tilespecs and their reference transforms.

I stubbed out the list of tilespecs method.. is that what you meant?

Yes, that is along the lines of what I was thinking, but now that I think about it, the way transforms (particularly non-leaf) are handled doesn't lend itself to nicely generalized dereferencing, and this is a nonessential feature.  Thanks for stubbing it out, as I would like to come back to it.


[Mention The Feature]: About us page update

Is your feature request related to a problem? Please describe.

Scrolling animation
Using GSAP

Describe the solution you'd like.
GSAP will make the page look very cool and modern
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
https://github.com/user-attachments/assets/7743dd9d-c95c-4779-aa7e-7009aa488833
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

For now the about us page is looking good and don't want any updates further from it.
So I am closing this issue.
Please Understand.


clap: move to derive API

build(deps): bump clap from 2.34.0 to 3.1.15
Signed-off-by: GitHub<EMAIL_ADDRESS>

Codecov Report

Merging #23 (f7194a5) into trunk (0dca7ac) will increase coverage by 0.04%.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##           trunk     #23      +/-   ##
========================================
+ Coverage   3.72%   3.76%   +0.04%
========================================
  Files          6       6
  Lines        188     186       -2
========================================
  Hits           7       7
+ Misses       181     179       -2

Impacted Files
Coverage Δ

src/main.rs
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Use process.env instead of globals

Addresses the todo in #206.  Removes compiler global from source code.  Allows consumers to compile our source and still take advantage of the NODE_ENV.

👻


Footer: Nest Navigation

Overview
We need to nest the navigation in the tablet and mobile breakpoints so that we can have a cleaner UI. This issue is related to #319
Action Items

[ ] For Tablet and Mobile screens, collapse all parent links except for Follow and Newsletter.

@meismith pls modify tablet and mobile per screen shot in Figma file.

I modified the footer for tablet and mobile last week, let me know if we still need to change this

Thanks @meismith this is good.
@mariastudnicka please make sure to title issues correctly. Thanks!


Use startPlayer with an http link

Hello, I try to read files on my server with the module in http but we hear nothing. The module does not work without https ?

It should work but I think it should have mp3 extension.
Related discussion can be found in https://github.com/hyochan/react-native-audio-recorder-player/discussions/479.


Update link to forest-offsets repo in forest-offsets-explainer article

When reading through the "Systematic over-crediting of forest offsets" article I noticed a small typo in a link to https://github.com/carbonplan/forest-offsets. This PR updates the link.
Also, nice article : )

Thanks @jrbourbeau!


Checking for updates stuck when resuming PC from standby

VSCode Version: 1.13.1
OS Version: Win8.1 x64

Steps to Reproduce:

Have a project open in VS Code
Put your PC into standby
Sleep
Get up
Resume PC from standby

"Checking for updates..." will stay greyed out forever, can be fixed by restarting VS Code though.

Reproduces without extensions: Not tested yet but I assume irrelevant

#25632


[Android] Fix Javadoc error

This patch is to fix the error when generating Javadoc for embedding API

@rakuco Please help to review

Please be more specific in both your commit and pull request messages:

What javadoc error are you talking about?
How are you fixing it?
When was it introduced?

done

lgtm, thanks!

merged, please remember to cherry-pick to crosswalk-14 if appropriate.


test: implemented ql tests marked as todo

@gregorwolf  @vobu I have implemented the QL tests that were marked as todo.

this totally slipped through in my inbox flood...sorry!
could you please resolve the conflict? then let's rerun the tests and merge asap.
thx!

Hi @vobu,
I resolved the conflicts.
Cheers,
Sebastian


Unable to associate files with VS Code on Windows 10

I'm well aware how to associate an extension with an application on Windows. I can right-click in Explorer, select, "Open As...", select the application, and make sure "Always open with this app" is checked. Or I can go in to the properties of a file in Explorer, look at "Opens with", and click on "Change". Or I can go to "Choose default apps by file type …", etc. The problem is that none of this is working with VS Code.
I just installed VS Code 1.28.1 yesterday. Currently my .txt files are associated with EmEditor. I change the association to Notepad. No problem. I change the association back to EmEditor. That works.
But if I select the blue "Visual Studio Code" option that appears in the list of applications, nothing changes. The old association remains.
I even tried ignoring the blue icon in the selection list, and manually browsed and selected %LocalAppData%\Programs\Microsoft VS Code\Code.exe as the default editor. That doesn't work, either.
What's going on? Associating VS Code with my text files should be the most basic of basic Windows integration. Why won't it work?

I've also asked this question on https://superuser.com/q/1367659/954883 .

I'm having the same issue, I have VS Code 1.28.2 installed on two computers running Windows 10, one is a user install (installed in %appdata%), the other is a system install (installed in program files). On neither computer am I able to choose VS Code as the default program to open, for example, .cpp files; regardless of whether I right click the file, "open with" or "choose another app", select VSCode and say "always use this to open this", or if I go through the settings app and try choosing VS Code as the default app for .cpp files, the end result is that the change does not apply, and whatever was set before stays there.
I was confused that there weren't more people reporting this issue, but a quick glance around the issue tracker suggests that other users have successfully been able to associate VS Code with file types in explorer, so I'm not sure what we're doing differently.

I tried associating with %LocalAppData%\Programs\Microsoft VS Code\bin\code.cmd, but that just gave me an ugly terminal window in the background, and it still didn't associate *.txt with VS Code.

I can't associate it with any file type. Running win10 1803 and latest user installed vscode.
Tried every possible way:

the usual right click and open with... and then selecting "always use this app" option
right click  -> properties -> click change button for "Opens with:"
Settings -> System -> Choose default apps by file type

After selecting vscode, for example for .py files, nothing changes. Also saw in latest vscode release notes that some sort of fancy icons were added when associated with vscsode which should happen by default now? Perhaps that update mucked things up? https://code.visualstudio.com/updates/v1_28#_file-icons-per-file-type

There is a bug in the last two cumulative updates for 1803 that breaks the Open With dialog as well as other methods of changing the default file association. Perhaps this is the cause of this issue; at least it was mine.
If you look there, under Version 1803, you'll see that the two latest KBs are KB4462919 and KB4458469. If you have any of those, uninstall them, then try again to change the default app for your file. If it works, then I suggest hiding those KBs until a new update is release with, hopefully, a fix for this bug.
If you don't know how to hide an update, look here.

This is actually a Windows bug! https://www.reddit.com/r/windows/comments/9qeijs/cant_set_some_file_associations_properly_anyone/

Wow, that's a pain! That's absolutely it though, because I checked and found out Notepad++ suffers from the same problem.
Here's the thing though, if you register file associations using Notepad++'s preferences window, they apply in Windows Explorer just fine. I couldn't associate CPP files with NP++, but after I told NP++ to associate itself with CPP files, Windows allowed me to change CPP files to NP++ away from VS2015, and I can still change it back and forth even after turning the setting off in NP++. When trying with C files, which I'd never enabled and were also already assigned to VS2015, Windows wouldn't allow me to change it to NP++.
A similar thing happened with PHP files; which I didn't have a default editor for. Telling NP++ to assign itself to PHP files caused Windows to recognize it, and it's still set as the default editor for it even after I turned that setting back off.
Since VS Code offers no way to tell it to assign itself to file types, there's no way to apply this workaround for it. Still, it definitely seems like Windows isn't allowing you to set a program as default until the program registers itself with whatever Windows 10's mechanism for this is.
For sure, I hope a future windows update addresses this.

hopefully... but sounds like they have much bigger fish to fry with the october 1809 release given it is still eating people's files.

There's a workaround!

Download the installer for the latest VS Code (make sure it's the same type; system if you have a system install, user if you have a user install)
One of the options is to have the installer associate supported filetypes with VS Code, make sure it's selected.
Allow VS Code to be reinstalled.

I tried it with my system install, and all of my installed extensions and my preferences have remained intact so far, with the added bonus that I now have working filetype associations for VS Code.
Windows 10 might prompt you when you double click on a file, but will respect VS Code as a selection now.

Funny that you commented on this issue again just today. The Windows build 17134.441 (kb4467682 was released today with a fix for this.