avahi-daemon intermittent behaviour

resin local scan did not show an Intel NUC device running a dev image.
systemctl status avahi-daemon showed that avahi had not registered the ip/interface to respond.
systemctl restart avahi-daemon fixes things
Have not been able to reproduce this yet.
Possibly linked with https://github.com/resin-os/meta-resin/issues/409
 Front conversations

Copied from Front/FD thread:
I've looked into this in a fair bit of detail. I am running several virtual NUCs, as well as a couple of Pis, most in development mode, one in production. Correctly, the production devices do not show up (although they do correctly advertise themselves but are dropped by resin-cli as a Docker client connection to them cannot be established). One of the virtual NUCs exhibits the behaviour seen by the customer.
However, the reason that it doesn't initially show up is because on-device Avahi is not (but only in this particular instance) conforming to the DNS-SD spec., particularly this section (https://tools.ietf.org/html/rfc6763#section-12.1):
When including a DNS-SD Service Instance Enumeration or Selective
Instance Enumeration (subtype) PTR record in a response packet, the
server/responder SHOULD include the following additional records:
o  The SRV record(s) named in the PTR rdata.
o  The TXT record(s) named in the PTR rdata.
o  All address records (type "A" and "AAAA") named in the SRV rdata.
What's actually happening is that Avahi is only returning a PTR record, and not the additional SRV and A/AAAA records expected by the DNS-SD client. Not only does resin-discoverable-services not resolve it (as it has not SRV/A record to resolve), but neither does Avahi (under Linux as a client) or dns-sd (under OSX as a client). avahi-discover does show the device (which is what the customer supplied to us in screenshots) but if you attempt to get more information on it, it reports a timeout error (because it actually has no further information to resolve the client). Subsequently, no client can actually determine the correct address for the device that doesn't show up. Wiresharking proves this theory.
Unfortunately, this means we're beholden to Avahi to correctly send responses. What is interesting is that eventually the device appears to recover and send all the records. The time period this occurs in is variable, however, but I've seen it recover after an hour (although it's entirely possible it may never recover). I can't see any changes in the Avahi source between v0.6.32 (which I'm seeing this happen on) and v0.7 (which the Pi3s are running and are not having issues with (so far)).
This is not a great situation, as although it seems to be happening with NUC images atm, it could potentially occur with any device type (assuming 0.7 is still affected), and looks to be some sort of bug in Avahi which (probably) clears after a period of time.
There's a potential way round this, which is to add some extra code to our resin-io-modules/mdns fork of the MDNS module, to specifically request SRC/A/AAAA records should we get a PTR record with no other RRs. This is not in the spec., but should force the failing on-device Avahi to specifically broadcast these records for us. It's a possible way forward, at least.


[FR] Add --external-downloader  --external-downloader-args

A detailed description of the proposed feature
--external-downloader --external-downloader-args allow brew to use an external tool to download files. With these flags added, we can use aria2 like so:
--external-downloader aria2c  --external-downloader-args '-c -j 3 -x 3 -s 3 -k 1M'
The motivation for the feature
These flags allow users to use their own downloader, which can help increase speed and stability. I guess most contributors here enjoy high-speed internet, but in a lot of rural places and developed countries, internet connection is a lot more unstable/slow. Especially since the pandemic, this issue has become more prominent. The default downloader sometimes stalls on slow connections, and can't use split connections.
How the feature would be relevant to at least 90% of Homebrew users
Any person can sometimes encounter a bad connection that benefits from a good downloader. This is especially true since the people who benefit the most from this addition are the ones with the least voice.
This feature had been previously requested in the legacy repo, too, by someone else. It follows the Unix philosophy of allowing each tool to do one thing well and delegate tasks to other tools.
What alternatives to the feature have been considered
As far as I know, there have not been any alternatives. brew used to not support resuming broken downloads, which was really bad, but aside from that, nothing seems to be considered.
If the core maintainers are not willing to work on this, please provide some instructions for which parts of the code base need changes, and I'll send a PR when I have time.

@MikeMcQuaid Why close the issue without comment?

https://github.com/Homebrew/brew/blob/master/.github/ISSUE_TEMPLATE/bug.md#please-note-we-will-close-your-issue-without-comment-if-you-delete-do-not-read-or-do-not-fill-out-the-issue-checklist-below-and-provide-all-the-requested-information-if-you-repeatedly-fail-to-use-the-issue-template-we-will-block-you-from-ever-submitting-issues-to-homebrew-again

@MikeMcQuaid I've updated the issue to follow the guidelines.

brew used to not support resuming broken downloads, which was really bad, but aside from that, nothing seems to be considered.

Homebrew does support resuming broken downloads.
I'm not sure about this for a new PR. We'd consider it but it would need to handle all proxy settings etc. and be opt-in/optional. The relevant code would probably be in download_strategy.rb and I'd suggest it would be an environment variable like HOMEBREW_DOWNLOADER and HOMEBREW_DOWNLOADER_ARGS or something similar.


False positive "no-unused-import": user-defined value type defined as constant

In the UD60x18 value type^1 in my PRBMath library, there is a constant called ZERO:
https://github.com/PaulRBerg/prb-math/blob/28055f6cd9a2367f9ad7ab6c8e01c9ac8e9acc61/src/ud60x18/Constants.sol#L51
Importing and using this constant leads to an "imported name ZERO is not used" error:
pragma solidity >=0.8.19 <0.9.0;

import { UD60x18, ZERO } from<EMAIL_ADDRESS>
contract SetProtocolFee_Integration_Fuzz_Test {
    function testFuzz_SetProtocolFee(UD60x18 newProtocolFee) external {
        newProtocolFee = _bound(newProtocolFee, 1, MAX_FEE);
    }
}

The other two issues make complete sense, but I think I'm missing something here. How is ZERO used?

Sorry @fvictorio, I have clipped the relevant code 😁
Edited the OP


Nick: Watch bytenex.com

Nick requests the watch of the watch_keyword bytenex\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bytenex\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Bug With Top When Using TCR and Windows Responsive Fix

Describe the bug
The top part of the window is cut off when using TCR and Windows Responsive Fix
Expected behavior
The top of the window not be cut off like when using TCR and the normal responsive.css
Screenshots (optional)

Changing @import 'includes/cascade-responsive-windows-fix.css to @import 'includes/cascade-responsive.css fixes the cut off top but then obviously doesn't move elements correctly in windows.

Hmm, this is odd. I can't reproduce this behaviour, so it might be something device specific. It wouldn't be the first thing that is drastically different on other devices.
I would assume the issue lies somewhere within the top margin of the #nav-bar, so playing around with the 12px value on line 3 and 6 might resolve this.


Append 'humans_time' value to json representation of Message

For fetching messages by ajax

Thank you @zhengfen


train_val prototxt

Hello, Could you please provide the train_val.prototxt file?
I would like to do some fine-tuning but it seems like the number of blobs for the batchnorm layers are not the same between the training and deploy models.

except data layers and loss/acc layers, the main body of the training and deploy prototxt files should be the same. please check your training prototxt files.

thanks for your reply. Is it possible for your to share your train_val.prototxt file?

they are actually the same.
so if you have any troubles, would you please provide your error infomation?

there seems to be an inconsistency between the batchnormalization layers definition in the mobilenet_deploy.prototxt and that of the provided Caffe model. More specifically, for ? I get the following error message:
ERROR: Check failed: target_blobs.size() == source_layer.blobs_size() (5 vs. 3) Incompatible number of blobs for layer conv1/bn

do you use the official caffe?
batch_norm_layer has only 3 blobs.
please take a look at: https://github.com/BVLC/caffe/blob/master/src/caffe/layers/batch_norm_layer.cpp#L25

I am using nvCaffe and the NVIDIA Digits environment for fine-tuning

please take a look at https://github.com/NVIDIA/caffe/blob/caffe-0.16/src/caffe/layers/batch_norm_layer.cpp#L25
  scale_bias_ = false;
  scale_bias_ = param.scale_bias(); // by default = false;
  if (param.has_scale_filler() || param.has_bias_filler()) { // implicit set
    scale_bias_ = true;
  }

  if (this->blobs_.size() > 0) {
    LOG(INFO) << "Skipping parameter initialization";
  } else {
    if (scale_bias_)
      this->blobs_.resize(5);
    else
      this->blobs_.resize(3);

please confirm that you set scale_bias false, and have no scale_filler or bias_filler for batch norm layers.

many thanks for your reply. As I am very new to Caffe, could you please let me know exactly how to do that?

please update your caffe to newest one from:  https://github.com/NVIDIA/caffe/
and the default param settings would be ok for you.

thanks for your reply. I have upgraded the caffe but still face the same problem. Any help on how to resolve this is greatly appreciated.
I need take a good look at it.


Add missing fields on IntegrationPlatform custom resource to support platform controller operator

Part of #3397

still relevant

please assign this one to me


Update minimist dependency in bower-config

We need to bump minimist version to at least 1.2.2 in bower-config package or deprecate it.
Here are the vulnerability reports: #1, #2

It has been already updated to version 0.2.1 which has this CVE patched


Build directory not cleared before build "all" targets

Build directory is not cleared before rebuilding all targets.
Normally, the expectation is that:

building one or specific set of targets - do not clear
building all targets - rimraf the build dir before building

Options:

Can be done via cli before "npm run build" with a rimraf command.
Can be done in code in the build script

Example for rollup.config.mjs in the default export
  // if building a specific format, do not remove build.
  if (!targets.length && existsSync(`build`)) {
    await fs.rm(`build`, { recursive: true });
  }

I ran into an issue that confused me when I thought some files were not being built.  They are no longer part of the build but were left there from 3 weeks ago.  Clearing the directory on full builds will ensure this does not happen again.
It will also ensure extra files are not published to npm bloating the bundle size.  For example "common.js" in the shaders directory, removed in a commit a few weeks ago, in a recent publish.

The build command should probably build the TypeScript declarations too then.

keen to do all this @epreston ? I'd love to have this.

On the way.

Ready for review.  A little re-org for clarity and the normal clean-up logic on "build all".

Yes, I got hit by this yesterday and it took me a while to figure out what is missing. It'd be great to add.

@willeastcott , @mvaligursky , @kungfooman
A command already exists to build types after the library is built.
npm run build:publish
It is defined as:
"build:publish": "npm run build && npm run build:types",
You can be confident that it is clean because the first command purges the directory.

Hi interesting .. personally I'd remove the publish target and make the build do this.
@slimbuck @willeastcott - any thoughts?

Can I speed up the build 10x first by swapping a few rollup plugins ?  Then we add to it ?
The best in class plugin for this at the moment does both at the same time.  Worth taking a look at.

Sure, create a separate issue / pr and go for it, keen to see what it is.


Consider sandsmark-notificationd for notifications

Consider replacing dunst with a visually optimized fork of sandsmark-notificationd. It looks reasonably simple and is written in Qt which means it would be able to handle HiDPI properly, unlike what we have now.

Possibly integrate into Menu?


fix index out of range in ProcessExtensions.EnvToDictionary

This is to address the exception below.   There are many potential index-out-of-length issues where we incremented i and used it without checking whether it was out of length.    I started fixing by adding checking here and there and the codes become hard to maintain and understand.   I decided to rewrite and simplify it.   I have done a backward compatibility comparison between old vs. new implementations against various processes to make sure no regression.
at Kudu.Core.Infrastructure.ProcessExtensions.EnvToDictionary(Byte[] env)
   at Kudu.Core.Infrastructure.ProcessExtensions.GetEnvironmentVariablesCore(IntPtr hProcess)
   at Kudu.Core.Infrastructure.ProcessExtensions.GetEnvironmentVariables(Process process)
   at Kudu.Services.Performance.ProcessController.SafeGetValue[T](Func`1 func, T defaultValue)

It does look much simpler this way.
:shipit:


Dash handling

Hi,
I would be perfect to handle the dash syntax :
- (dash)
    A dash indicates that no substitution should be performed (the existing path is passed through untouched). This is used when a flag (see below) needs to be applied without changing the path.

It would be possible to write something like this :
'^/data/(.*)$ - [L]',

instead of
'^/data/(.*)$ /data/$1 [L]'

@astik sound useful. Do you mind land a PR?


Adds solution to LeetCode problems

Last stone weight
Middle of linked list

Hey @shivangdubey What kind of description are you looking for?


[Feature] Add more apps in the demo

Hard code more apps in the demo for a better view and comprehension.

fixed in #17


Failed to execute control_tower lambda

Hey everyone,
I faced issue during starting backend test.
Installation was carried out for local instance according to the instructions.
All containers are fine.

Loki error:
Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/interceptor-1.0.0-py3.6.egg/interceptor/run.py", line 137, in execute_lambda LambdaExecutor(task, event, galloper_url, token).execute_lambda() File "/usr/local/lib/python3.6/site-packages/interceptor-1.0.0-py3.6.egg/interceptor/lambda_executor.py", line 39, in execute_lambda environment=env_vars) File "/usr/local/lib/python3.6/site-packages/docker-3.6.0-py3.6.egg/docker/models/containers.py", line 808, in run container, exit_status, command, image, out docker.errors.ContainerError: Command '['lambda.handler', '[{"container": "getcarrier/perfmeter:<IP_ADDRESS>", "execution_params": "{\\"cmd\\": \\"-n -t /mnt/jmeter/site.jmx -Jtest_name=Test7 -Jtest.type=default -Jcomparison_db=comparison_1 -Jtelegraf_db=telegraf_1 -Jinflux.host=<IP_ADDRESS> -Jinflux.db=jmeter_1 -Jgalloper_url=http://<IP_ADDRESS> -Jinflux.password=password -Jinflux.port=8086 -Jloki_port=3100 -Jloki_host=http://<IP_ADDRESS> -Jinflux.username=admin\\", \\"cpu_cores_limit\\": \\"1\\", \\"memory_limit\\": \\"1\\", \\"influxdb_host\\": \\"<IP_ADDRESS>\\", \\"influxdb_user\\": \\"admin\\", \\"influxdb_password\\": \\"password\\", \\"influxdb_database\\": \\"gatling_1\\", \\"influxdb_comparison\\": \\"comparison_1\\", \\"influxdb_telegraf\\": \\"telegraf_1\\", \\"loki_host\\": \\"http://<IP_ADDRESS>\\", \\"loki_port\\": \\"3100\\"}", "cc_env_vars": {"RABBIT_HOST": "<IP_ADDRESS>", "RABBIT_USER": "user", "RABBIT_PASSWORD": "password", "RABBIT_VHOST": "carrier", "GALLOPER_WEB_HOOK": "http://<IP_ADDRESS>/task/44096b2e-5ec1-487a-977c-0d3779e5726b"}, "bucket": "tests", "job_name": "Test7", "artifact": "site.zip", "job_type": "perfmeter", "concurrency": 1, "channel": "default", "junit": "True", "quality_gate": "True", "save_reports": "True", "email_recipients": "", "test_id": "e8439cdc-6d89-413b-aee2-32956552ab31"}]']' in image 'getcarrier/lambda:python3.7' returned non-zero exit status 1: b"\x1b[32mSTART RequestId: 288bd421-a8b0-1826-6b7a-0fbae9561743 Version: $LATEST\x1b[0m\n[ERROR] Runtime.ImportModuleError: Unable to import module 'lambda': No module named 'lambda'\nTraceback (most recent call last):\n\x1b[32mEND RequestId: 288bd421-a8b0-1826-6b7a-0fbae9561743\x1b[0m\n\x1b[32mREPORT RequestId: 288bd421-a8b0-1826-6b7a-0fbae9561743\tInit Duration: 213.77 ms\tDuration: 7.08 ms\tBilled Duration: 8 ms\tMemory Size: 1536 MB\tMax Memory Used: 17 MB\t\x1b[0m\n"
Please tell what could be the problem?
Thanks in advance!

Hi @IvanKr12
You need to generate auth token for your project to start a test. You can find instructions at the end of this guide - https://github.com/carrier-io/carrier-io/wiki/Project-And-Users
By the way this repository is used for new Carrier platform. If you will have any more issues with Carrier 2.5 please create them for that repo - Galloper
Thanks

Hi @hunkom
Problem solved after generation auth token.
Thanks a lot!


IE11 Compatibility?

Describe your question
Bit of a long shot - any idea on IE11 compatibility for ChartJS.Blazor for server-side?  I'm using daddoon's Blazor/Polyfill which covers most basic scenarios, but I get a SCRIPT1002 Syntax Error on ChartJsBlazorInterop.js (3,1) in IE11's console.  Are there any extra polyfills I might need?
Which Blazor project type is your question related to?

Server-Side

Which charts is this question related to?
All charts

As far as I understand, IE11 doesn't support js-classes (source). Since we're using classes, you might need to add support for those or rewrite the js. However, I don't know how you would achieve the first option and I understand that the second option isn't much more desirable.
Sadly, I don't think I can help you directly (I'm simply not experienced enough with this stuff) but I think these links might help you:

Support for ES6 in Internet Explorer 11 (StackOverflow)
IE11 gives SCRIPT1002 error when defining class in javascript (StackOverflow)

IE11

Just.
Let.
It.
Die.
🤣 🤣 🤣 🤣

As far as I understand, IE11 doesn't support js-classes (source). Since we're using classes, you might need to add support for those or rewrite the js. However, I don't know how you would achieve the first option and I understand that the second option isn't much more desirable.
Sadly, I don't think I can help you directly (I'm simply not experienced enough with this stuff) but I think these links might help you:

Support for ES6 in Internet Explorer 11 (StackOverflow)
IE11 gives SCRIPT1002 error when defining class in javascript (StackOverflow)

Many thanks!  I'll take a good look at these this week and see how far I get.  If I achieve anything I'll report back here.

IE11

Just.
Let.
It.
Die.
🤣 🤣 🤣 🤣

Hahha mate, I'll be the first in line with the baseball bat to put IE11 out of its misery.  But legacy support for legacy software on legacy hardware used by legacy (near retirement, surely) users means I have to cover all bases.  Even if those bases are constructed from termite-infested plywood.

Hahha mate, I'll be the first in line with the baseball bat to put IE11 out of its misery. But legacy support for legacy software on legacy hardware used by legacy (near retirement, surely) users means I have to cover all bases. Even if those bases are constructed from termite-infested plywood.

I know, I already had the same problem with another project ;)

Looking good so far.
Thanks to the pointers above about the use of ES6 class() and the SO threads, I looked into using Babel to transpile ChartJSBlazorInterop.js down to ES5.  I gave that a go, and then changed the script tag in _host to be conditional:
<!-- This is the glue between the C# code and the ChartJs charts -->     <script type="text/javascript">         if (/MSIE \d|Trident.*rv:/.test(navigator.userAgent)) {             document.write('<script src="ChartJsBlazorInterop.js"  type="text/javascript" language="javascript"><\/script>');         }         else {             document.write('<script src="_content/ChartJs.Blazor/ChartJsBlazorInterop.js" type="text/javascript" language="javascript"><\/script>');         }     </script>
So an IE11 user will use the transpiled version (which I've stuffed into wwwroot), everyone else takes the original one from the nuget package.  And it seems to work - I can see charts in IE11, blazor, server-side.  I'll be back to moan if I hit any snags further down the line.
I know it's debatable if this effort is worth it for IE11's sake.  And I'll have to use babel to transpile each time the Interop.js file changes in an update to keep them synchronised.  But it's an option for those of us who are stuck in the dim and distant past.

I'm glad you got it working! I think for now this is the best you can do.
@mariusmuntean Would you consider not using ES6 features in order to make it compatible with IE11 and below or should we just leave it as is and let people transpile if necessary? I don't know how many ES6 features we use apart from classes and I also don't know how much effort it would be considering we're using typescript, not javascript. I'd be fine with leaving it as is and letting people transpile (sorry @fudgeboy2000) since not many people rely on it and also since the ts-interop shouldn't change too often (if it does, we should definitely consider making it compatible).

I was surprised by how easy it was to get babel setup and doing its thing - it's a small extra build step for devs in my unfortunate position considering how easy the ChartJS.Blazor package makes adding charts.  A small price to pay, and hopefully this thread will help others who have to put up with IE11 in their lives.

@fudgeboy2000 great job!
I'm really glad you got it working and then documented it here.
In my opinion it should work even easier than using Babel. Nothing against Babel, but there's no need for an extra step. Instead, just do this:

In the tsconfig.json adjust the target to ES5
Reference something like core-js in you _Host.cshtml BEFORE referencing the updated ChartJs interop file.
Profit!

If anyone has a Windows machine at hand and is willing to test this out, I'd appreciate if they can document the results here.
@Joelius300 you're right, I wouldn't downgrade the traspilation target that much. After consulting  a colleague on this issue, I think that the added complexity, increased download size and/or loss of performance aren't worth it.
On the other hand, if it turns out that there are many people who need this, I would be willing to add a second CD pipeline that publishes another Nuget package for supporting older browsers.

Should we leave this issue open? Maybe link to it in the readme where we mention what browsers we support (we do that right 🙄) and then close?
The wiki has been long dead so until we have proper documentation, this would have to go into the readme. Or we just leave it and people will search for it and find it.
Opinions?


Add Diagnostic Logs cluster template

Problem
Implement Diagnostic Logs cluster
Change overview
Added the zap template for Diagnostic Logs cluster
Testing
No testing is required, this PR is not functional, tests will be added in the following PR when the feature is functional.

/rebase

/rebase


refactor the Node class to extract the transferableNodes from it

Transferable nodes are not really an attribute of nodes. They are saved separately from the node in the database and need to be manually excluded from the data field, if they are present, before saving to the DB. They should just not be there. There should be another way to get them if/when they are required, which is not often in Transition itself.
That's for Transition. The capnp cache can remain like this (as it is sort of an API now).

I disagree about the capnp cache. We duplicate the data about each Node the way is it at the moment. It would probably be way faster if we'd had a data structure more like the one in the database.

I disagree about the capnp cache. We duplicate the data about each Node the way is it at the moment. It would probably be way faster if we'd had a data structure more like the one in the database.

I agree with that, but changing that requires changing 1- trRouting, 2- Transition, 3- json2capnp in sync or by incrementing some major version where we have none... Or we yolo our way there, hoping noone else is using transition outside us now ;-)

I think it would be pretty safe to change. The file format is not really documented, so if someone is using it, it's a little bit at their own risk... Once we have something a bit more solid, we could think about versionning.

But yes, refartoring the file format could be done in a separate step.


Update training-LSTM.md

Add a link to training an LSTM model using the Paperspace tutorial.

thanks! We should update the repo README as well: https://github.com/ml5js/training-lstm
Do you want to submit a PR there too?

Noticing this never got merged. Great resource to link to and yes we should add it to training-lstm! I'll open an issue there.


Remove unwanted files

Currently, master has some undesired files since the last merge. Strangely, gitignore is not ignoring the what it is supposed to ignore.
This branch intends to clean up all these files

@nathanshammah .gitignore seems to be working fine now


Add capability of directly assigning PFs to Pods

The original SRIOV-CNI was enhanced with the capability of directly assigning PFs to Pods:
https://github.com/hustcat/sriov-cni/commit/793ec5dcc67fc5ec54d4bd244461a7baf8950609
The use-cases -mostly TelCo related- mentioned by the commit are still valid, and could be satisfied with the merging of the code, and the introduction of the pfOnly configuration parameter.
The code could be further enhanced by defining the interworking between the newly introduced pfOnly, and the already existing dpdk configuration options.
When both are defined the plugin could first bind the PF directly to the configured DPDK kernel driver, then assign it to the Pod via its PCI address.
Such enhancement would basically unite the best of both plugins: capability of directly assigning PFs to Pods, but via the PFs PCI address, while also taking care of the management of the PF's control plane.
I don't think the existing plugin can serve this use-case right now, but feel free to correct me if I missed something!
I (and/or some of my colleagues) could also handle the contribution in case the idea is welcomed, but I wanted to open a discussion about it first.

I would also love to see this feature.
In Kubevirt case, we need to be able to safely validate SR-IOV for our cluster. in CI environment, Kubevirt cluster is running inside an OpenShift pod. To be able to validate SR-IOV support for Kubevirt, we need to be able to deploy SR-IOV device plugin and CNI inside this pod. It means that we should first propagate PFs into the pod. We would like to use SR-IOV DP / CNI for that. Basically, we would have SR-IOV DP / CNI running in two places: 1) at the bottom layer to propagate PF into CI pod; and 2) as part of Kubevirt cluster, to allocate VFs from allocated PFs to virtual machines.
We were looking into building some custom mechanism to propagate PFs into CI pods, but figured that maybe we can reuse the same components on both layers.

@zshi-redhat, I don't see a pfOnly option in the current master of SR-IOV CNI.  Could you point me to it? SRIOV DP is able to detect the PF when I set "sriovMode" : false" , but the SRIOV CNI is failing while creating the pod with this error :
Multus: Err in tearing down failed plugins: Multus: error in invoke Delegate add - "sriov": SRIOV-CNI failed to load netconf: lstat /sys/bus/pci/devices/0000:01:00.0/physfn/net: no such file or directory
Could you help?


java.lang.ClassNotFoundException: Didn't find class "androidx.core.content.ContextCompat" on path: DexPathList

Hi, after upgrading Flutter I receive this exception when trying to discover Bluetooth devices:

[ERROR:flutter/shell/platform/android/platform_view_android_jni.cc(39)] java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/core/content/ContextCompat;
E/flutter (18058): 	at com.tablemi.flutter_bluetooth_basic.FlutterBluetoothBasicPlugin.onMethodCall(FlutterBluetoothBasicPlugin.java:92)
E/flutter (18058): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:231)
E/flutter (18058): 	at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:93)
E/flutter (18058): 	at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:642)
E/flutter (18058): 	at android.os.MessageQueue.nativePollOnce(Native Method)
E/flutter (18058): 	at android.os.MessageQueue.next(MessageQueue.java:325)
E/flutter (18058): 	at android.os.Looper.loop(Looper.java:142)
E/flutter (18058): 	at android.app.ActivityThread.main(ActivityThread.java:6518)
E/flutter (18058): 	at java.lang.reflect.Method.invoke(Native Method)
E/flutter (18058): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
E/flutter (18058): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
E/flutter (18058): Caused by: java.lang.ClassNotFoundException: Didn't find class "androidx.core.content.ContextCompat" on path: DexPathList

• Flutter version 1.12.13+hotfix.8 at C:\Flutter
• Framework revision 0b8abb4724 (3 weeks ago), 2020-02-11 11:44:36 -0800
• Engine revision e1e6ced81d
• Dart version 2.7.0

Fixed by moving to AndroidX.

Hi @DmitrySikorsky ,
Thank you for your feedback.
Does this plugin work as expected for you under Android X? Are you able to find any Bluetooth devices?

Yes, it works fine.


Make sure to respect port flags and configuration

- Summary
Fixes: https://github.com/netlify/cli/issues/438
Fixes: https://github.com/netlify/cli/issues/563

- Test plan
Specify port in your netlify.toml, like so:
[dev]
    port = 2021

Run netlify dev and make sure it is running on port 2021 (if is is not in use by another process).
Run netlify dev --port=2025 and verify that it's running on port 2025.

- Description for the changelog
Reset port, targetPort and functionsPort on settings object with values from flags having the highest priority, then configuration file (netlify.toml etc) and then site detectors.

- A picture of a cute animal (not mandatory but encouraged)
🦁

I'm thinking of removing the option to specify functionsPort since that is used internally only, and not accessed by users directly. I think it just adds to the confusion. What do you think @ehmicky @erquhart


Handle undefined input

Closes #4

Thanks for creating a PR! I will get this merged and updated in the next day or two when I get some time to test


How many times do you need to train the robot arm to reach the target position well?

It is very helpful to experience reinforcement learning simulation using your examples.
I'm running through your examples, but it's hard to see that reinforcement learning is working.
How many times can you tell if you've reached 80% of your target?

Currently, there is no way to reach the goal now since it is taking random action. Soon I will implement some RL algorithms as TD3 or SAC, to solve the task
What you have now is just the environment


python312Packages.pysigma: 0.10.10 -> 0.11.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.pysigma is: Library to parse and convert Sigma rules into queries
meta.homepage for python312Packages.pysigma is: https://github.com/SigmaHQ/pySigma
meta.changelog for python312Packages.pysigma is: https://github.com/SigmaHQ/pySigma/releases/tag/v0.11.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.11.2 with grep in /nix/store/k7iha695lwvbcrhv11v5ipg6iz6vdi3x-python3.12-pysigma-0.11.2
found 0.11.2 in filename of file in /nix/store/k7iha695lwvbcrhv11v5ipg6iz6vdi3x-python3.12-pysigma-0.11.2

Rebuild report (if merged into master) (click to expand)

19 total rebuild path(s)

19 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.pysigma
python311Packages.pysigma-backend-elasticsearch
python311Packages.pysigma-backend-insightidr
python311Packages.pysigma-backend-opensearch
python311Packages.pysigma-backend-qradar
python311Packages.pysigma-backend-splunk
python311Packages.pysigma-pipeline-crowdstrike
python311Packages.pysigma-pipeline-sysmon
python311Packages.pysigma-pipeline-windows
python312Packages.pysigma
python312Packages.pysigma-backend-elasticsearch
python312Packages.pysigma-backend-insightidr
python312Packages.pysigma-backend-opensearch
python312Packages.pysigma-backend-qradar
python312Packages.pysigma-backend-splunk
python312Packages.pysigma-pipeline-crowdstrike
python312Packages.pysigma-pipeline-sysmon
python312Packages.pysigma-pipeline-windows
sigma-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k7iha695lwvbcrhv11v5ipg6iz6vdi3x-python3.12-pysigma-0.11.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.pysigma https://github.com/r-ryantm/nixpkgs/archive/1628e677713d31007debce783869c648d1e90222.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1628e677713d31007debce783869c648d1e90222#python312Packages.pysigma

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k7iha695lwvbcrhv11v5ipg6iz6vdi3x-python3.12-pysigma-0.11.2
ls -la /nix/store/k7iha695lwvbcrhv11v5ipg6iz6vdi3x-python3.12-pysigma-0.11.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

15 packages failed to build:

python311Packages.pysigma-backend-elasticsearch
python311Packages.pysigma-backend-opensearch
python311Packages.pysigma-backend-qradar
python311Packages.pysigma-backend-splunk
python311Packages.pysigma-pipeline-crowdstrike
python311Packages.pysigma-pipeline-sysmon
python311Packages.pysigma-pipeline-windows
python312Packages.pysigma-backend-elasticsearch
python312Packages.pysigma-backend-opensearch
python312Packages.pysigma-backend-qradar
python312Packages.pysigma-backend-splunk
python312Packages.pysigma-pipeline-crowdstrike
python312Packages.pysigma-pipeline-sysmon
python312Packages.pysigma-pipeline-windows
sigma-cli

4 packages built:

python311Packages.pysigma
python311Packages.pysigma-backend-insightidr
python312Packages.pysigma
python312Packages.pysigma-backend-insightidr

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.pysigma is: Library to parse and convert Sigma rules into queries
meta.homepage for python312Packages.pysigma is: https://github.com/SigmaHQ/pySigma
meta.changelog for python312Packages.pysigma is: https://github.com/SigmaHQ/pySigma/releases/tag/v0.11.3
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.11.3 with grep in /nix/store/d5209hxcbq0lz9glgi0ksszidiirza8f-python3.12-pysigma-0.11.3
found 0.11.3 in filename of file in /nix/store/d5209hxcbq0lz9glgi0ksszidiirza8f-python3.12-pysigma-0.11.3

Rebuild report (if merged into master) (click to expand)

19 total rebuild path(s)

19 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.pysigma
python311Packages.pysigma-backend-elasticsearch
python311Packages.pysigma-backend-insightidr
python311Packages.pysigma-backend-opensearch
python311Packages.pysigma-backend-qradar
python311Packages.pysigma-backend-splunk
python311Packages.pysigma-pipeline-crowdstrike
python311Packages.pysigma-pipeline-sysmon
python311Packages.pysigma-pipeline-windows
python312Packages.pysigma
python312Packages.pysigma-backend-elasticsearch
python312Packages.pysigma-backend-insightidr
python312Packages.pysigma-backend-opensearch
python312Packages.pysigma-backend-qradar
python312Packages.pysigma-backend-splunk
python312Packages.pysigma-pipeline-crowdstrike
python312Packages.pysigma-pipeline-sysmon
python312Packages.pysigma-pipeline-windows
sigma-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d5209hxcbq0lz9glgi0ksszidiirza8f-python3.12-pysigma-0.11.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.pysigma https://github.com/r-ryantm/nixpkgs/archive/7fc676b34d4858c0f062fefd2f97c62d60109247.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7fc676b34d4858c0f062fefd2f97c62d60109247#python312Packages.pysigma

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d5209hxcbq0lz9glgi0ksszidiirza8f-python3.12-pysigma-0.11.3
ls -la /nix/store/d5209hxcbq0lz9glgi0ksszidiirza8f-python3.12-pysigma-0.11.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

30 packages failed to build:

python311Packages.pysigma-backend-elasticsearch
python311Packages.pysigma-backend-elasticsearch.dist
python311Packages.pysigma-backend-opensearch
python311Packages.pysigma-backend-opensearch.dist
python311Packages.pysigma-backend-qradar
python311Packages.pysigma-backend-qradar.dist
python311Packages.pysigma-backend-splunk
python311Packages.pysigma-backend-splunk.dist
python311Packages.pysigma-pipeline-crowdstrike
python311Packages.pysigma-pipeline-crowdstrike.dist
python311Packages.pysigma-pipeline-sysmon
python311Packages.pysigma-pipeline-sysmon.dist
python311Packages.pysigma-pipeline-windows
python311Packages.pysigma-pipeline-windows.dist
python312Packages.pysigma-backend-elasticsearch
python312Packages.pysigma-backend-elasticsearch.dist
python312Packages.pysigma-backend-opensearch
python312Packages.pysigma-backend-opensearch.dist
python312Packages.pysigma-backend-qradar
python312Packages.pysigma-backend-qradar.dist
python312Packages.pysigma-backend-splunk
python312Packages.pysigma-backend-splunk.dist
python312Packages.pysigma-pipeline-crowdstrike
python312Packages.pysigma-pipeline-crowdstrike.dist
python312Packages.pysigma-pipeline-sysmon
python312Packages.pysigma-pipeline-sysmon.dist
python312Packages.pysigma-pipeline-windows
python312Packages.pysigma-pipeline-windows.dist
sigma-cli
sigma-cli.dist

8 packages built:

python311Packages.pysigma
python311Packages.pysigma-backend-insightidr
python311Packages.pysigma-backend-insightidr.dist
python311Packages.pysigma.dist
python312Packages.pysigma
python312Packages.pysigma-backend-insightidr
python312Packages.pysigma-backend-insightidr.dist
python312Packages.pysigma.dist

Maintainer pings
cc @fabaff for testing.


Sprockets::SassFunctions end up returning Ruby Sass to SassC (bad)

If a custom Sass function that wraps an existing Sprockets::SassFunctions method calls super, it ends up returning a Sass type, which has no #to_native method defined on it, then makes SassC blow up.
This is kinda awkward to test since the code that depends on the #to_native is in sassc-ruby/functions_helper.rb but the code that introduces Sass functions that return a Ruby Sass type is in sassc-rails/rails/functions.rb
I’m going to test this in sassc-rails for now and prepare a PR, but I’m open to feedback.

@bolandrm (This also means that https://github.com/bolandrm/sassc-ruby/commit/9bde3184c3a1c9ccc22c608aba4e9990349e5193 will break sassc-rails so please let me get in a fix before we release a new version.)

@bolandrm Okay, I’ve got the PRs in https://github.com/bolandrm/sassc-ruby/pull/16 and https://github.com/bolandrm/sassc-rails/pull/31
I’m not a fan of monkeypatching Ruby Sass types like this, but I think it’s a small enough and obvious enough alteration that it’s the best way forward, given our options.
We get test coverage for this change through existing tests in sassc-rails that check that the asset url methods and such work.
I also investigated an approach to fixing this purely on the sassc-ruby side that did something like a value.extend(SassC::Script::NativeColor) on the return values of Sprockets’ Sass functions, but I felt like it made more sense to have the code live in sassc-rails, since it’s where this issue is caused.

Handling on SassC-Ruby end


Error while trying to load "Passive Tree and Jewels"

Same issue here.

That is fixed in the latest update.


stable/logstash statefulset fix

What this PR does / why we need it:
logstash stateful set is currently missing spec.updateStrategy even though we set it in the values file! this changes that
Which issue this PR fixes
no issue reported yet!
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@swirsky
Would you mind to sign DCO please? Thank you.
Here is how to sign: https://github.com/helm/charts/pull/18642/checks?check_run_id=291646886

/ok-to-test

Could this be re-opened? It's still needed, I think


Cannot build project depending on serde using Cargo from 2017

Problem
I was expecting to be able to build an old project with a cargo.lock and correct rustc, but it fails because of a registry parsing error for an unrelated version of serde
Steps
$ git clone https://github.com/aidanhs/ayzim.git
$ rustup default rustup default nightly-2017-03-03
~/ayzim $ cargo --version
cargo 0.18.0-nightly (19ea423 2017-03-02)
~/ayzim $ cargo build --verbose
error: failed to parse registry's information for: serde

Caused by:
  Feature `derive` depends on `serde_derive` which is not an optional dependency.
Consider adding `optional = true` to the dependency

Possible Solution(s)
I think when trying to parse the registry, my version of cargo should lazily apply validation checks to versions being considered instead of eagerly validating all versions. Unfortunately even doing this doesn't help my really old version of cargo and I don't really want to update the project...I just want to build it!
Notes
No response
Version
$ cargo --version --verbose
cargo 0.18.0-nightly (19ea423 2017-03-02)
release: 0.18.0
commit-hash: 19ea4238114ea94c3fde0b623618e75accd70a66
commit-date: 2017-03-02

You are absolutely correct that that would be a better behavior for cargo to have, in fact that behavior was added way back in version 0.19. Which is one version off from being able to help you. We work incredibly hard to add new functionality in such a way that old cargos will continue to work, I am very sorry that we failed in this case. The new functionality has been stable for a long time so there's no easy way to back it out. And without a time machine we have no way of changing outdated versions of cargo people are still using.

Thanks the reply, fair enough. Is it easy to find the oldest nightly containing the cargo with this fix?

Probably cargo-bisect-rustc can do the job?


Fix amount of files in bundle

What type of PR is this?
/kind failing-test
What this PR does / why we need it:
cni-plugins removed their LICENSE and README.md from the existing release. We're now fixing the amount of files to make the CI pass again.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

@cri-o/cri-o-maintainers PTAL

/lgtm


Sql injection feature

I dont see any mention of prevention of sql injection in the documentation or the code, in rails active record handles this, does waterline do the same thing? If not can i get a feature request for this
https://github.com/balderdashy/sails/issues/1221#issuecomment-30969708

I tested, value like abc'; delete from user; will be escape to abc\'; delete from user_account;


Fix verify_merkle_branch

Issue
After we use progressive Merkle tree for the deposits, the deposit validation needs to updated to https://github.com/ethereum/deposit_contract/pull/13 since now the non-leaf empty nodes are also merkleized.
Proposed solution

Update the spec when https://github.com/ethereum/deposit_contract/pull/13 is merged.
(Recommend) Rename verify_merkle_branch to verify_merkle_proof because it's proof, not just branch.

I was mistaken for how processing deposits works and also verify_merkle_branch is agnostic of the implementation details of the tree.
Closing https://github.com/ethereum/deposit_contract/pull/13 and this issue. Though 2. probably still stands.

I think this can be closed. Please reopen if not :)


Implement issue #25

Coverage decreased (-0.2%) to 47.396% when pulling 2eb12eef427f46735b61ccf83c1dd76ece64bc7c on issue_25 into 722651e31062e144c36927038966a7f208912c0a on master.


Allow Simple Data Formats

For ease of implementation we chose to have set data formats for each of the types of plot. This can be a bit painful for simpler data (especially for time series data). Consider allowing each of the plots to accept multiple formats for the data.
I'd like to allow for more "flat" data to be used without having to explicitly specify the layer structure. For instance, instead of having to do this:
data = [
    { label: 'Layer 1', values: [ {time: 0, y: 0}, ... ] }
]

one could simply define the same single layer data set like so:
data = [ {time: 0, y: 0}, ... ]

Additionally it would be nice to allow for a series of basic numbers:
data = [ 0, 1, 2, 3, 20302 ]

For basic plots we could simply use the index as the x value. For real-time plots it's less nice since the time parameter expects a unix timestamp. Perhaps we could just count back from the current second in the browser?
Either way having simpler data formats should make it easier to get up and running with the library. And one can always use a more formal format as needed.

Yes


Support for configurable debug origin/port (issue 1429)

This PR adds support for configurable debug origin/port information as discussed in https://github.com/facebook/react-native/issues/1429 .
Summary
Here is a brief summary of my changes:

I added a new target called ReactWithoutPackager to React.xcodeproj that is a copy of the React target but does not execute the launchPackager.command script.
UIExplorer now links against libReactWithoutPackager.a, which attracts the ReactWithoutPackager target w/o launchPackager.command.
I added support for --origin parameter to packager.sh
I added a run script to UIExplorer that launches launchPackager.command with --origin and --port parameters.
Because I am now passing --origin and --port as parameters to launchPackager.command and open w/t --args does not seem to work with Terminal, I changed that code to using osascript instead.

Changing the port number
This is a screenshot after changing the port number to 8086 in Info.plist and rebuilding UIExplorer:

Backwards compatibility
I decided to make this change backwards compatible so clients can choose to continue using the old hard-coded origin/port (http://localhost:8081). The main reason is that many devs probably pick an example project and start modifying it to fit their needs. If we required Info.plist entries for origin/port values those old modified examples would break.
Usage in examples
At this point I only modified UIExplorer to show that origin/port can be configured. But I could change all examples if needed.
Utility function
There are three places where I added code that looks up the values for origin/port from Info.plist. That code is fairly trivial but could still be extracted and shared as a utility function. Please advise if that is necessary and let me know where I should add that utility function to.

I believe @frantic is the best person to review this

Good work, thank you! But I feel like we should probably do the other way around - have React target be pure and ReactWithPackager do what React target does now. @nicklockwood / @tadeuzagallo - do you think my suggestion makes sence?

@frantic fwiw I agree with that structure, and would take it a step further by skipping ReactWithPackager and just having SampleApp, UIExplorer, TicTacToe, etc... call the packager from their own pbxproj files.

@frantic @ide Thanks for the feedback. This is one of my weekend projects, please expect some delays etc.
Just to confirm: You and @ide suggest switching the default so Info.plist is supported by the React target and only the ReactWithPackager would launch the packager, correct?
Now, you guys realize that that will break modified old projects. The react-native Get Started section says:
Quick start
- npm install -g react-native-cli
- react-native init AwesomeProject

All those old AwesomeProjects will be broken if the React target stops launching the packager.  Are you ok with that? Can you just add a 'Breaking Changes' section to the next release and we all move on with our lives?

Ok, I've made the following changes:

replaced 'origin' with 'protocol' + 'hostname' as suggested by @ide
moved the debug URL creation code to its own utility function as suggested by @frantic
moved launch mechanics out to launchPackager.command as suggested by @frantic
removed launch script from React project and added launch scripts to examples as suggested by @ide

But:

I had to revert one line from facebook@1acca01, see https://github.com/facebook/react-native/issues/1654
this change will break old projects.

Breaking changes: required/optional changes.
If you have an old project and update your react-native module to this version then your old project will not launch the packager, because I removed the launch script from the React project.
Here are the changes that are required/optional...
REQUIRED: Add a launch script
Add a run script to your project with this line
$SRCROOT/../../packager/launchPackager.command ${INFOPLIST_FILE}`

OPTIONAL: Use RCTWebSocketExecutorURL
Use RCTWebSocketExecutorURL from RCTUtils.h for creating your jsCodeLocation in AppDelegate.m, i.e.
jsCodeLocation = RCTWebSocketExecutorURL(@"/Examples/SampleApp/index.ios.bundle");

OPTIONAL: Add a RCTWebSocketExecutor dictionary
Add a RCTWebSocketExecutor dictionary for custom settings to your Info.plist, i.e.

Please let me know if this looks good to you.
If so I'll squash/rebase my PR.
Thx!

Hmm, Travis CI build failed. It looks like I need to add the launch scripts to every test targets. Give me a minute!

One remaining problem is that packager.json runs packager.sh for the scripts/start and bin/react-native-start those will always launch the packager with the default settings, that is, port=8081.

@frantic I am a little bit puzzled why Travis CI is failing.
2015-06-21 22:27:29.662 [info][tid:com.facebook.React.JavaScript] "Running application "AppEventsTest" with appParams: {"rootTag":1,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF"
2015-06-21 22:27:29.672 [error][tid:com.facebook.React.JavaScript] "Error: Invariant Violation: Application AppEventsTest has not been registered. This is either due to a require() error during initialization or failure to call AppRegistry.registerComponent.
 stack:
  runApplication          IntegrationTestsA…:36107
  jsCall                  IntegrationTestsA…:7411
  _callFunction           IntegrationTestsA…:7679
  <unknown>               IntegrationTestsA…:7708
  <unknown>               IntegrationTestsA…:7702
  perform                 IntegrationTestsA…:6198
  batchedUpdates          IntegrationTestsA…:14132
  batchedUpdates          IntegrationTestsA…:4741
  <unknown>               IntegrationTestsA…:7701
  applyWithErrorReporter  IntegrationTestsA…:7446
  guardReturn             IntegrationTestsA…:7468
  processBatch            IntegrationTestsA…:7700
 URL: http://localhost:8081/Examples/UIExplorer/UIExplorerIntegrationTests/js/IntegrationTestsApp.includeRequire.runModule.bundle?dev=true
 line: 1762
 message: Invariant Violation: Application AppEventsTest has not been registered. This is either due to a require() error during initialization or failure to call AppRegistry.registerComponent."

I even removed my workaround for https://github.com/facebook/react-native/issues/1654 . But that didn't help either. Would you know what's going on here? Thanks!

I can now at least reproduce the problem locally w/t  rm -rf node_modules && npm install && ./scripts/objc-test.sh...

Ok, I found the problem (don't ask how I found it): react-native's package.json requires version 5.4.3 for the babel node nodule. Unfortunately babel's package.json sloppily accepts ^5.4.3 for babel-core. Now, if you start with a fresh clone (as Travis CI does) you'll end up with babel 5.4.3 using babel-core 5.6.2 (which is the latest babel-core version). Here is the problem: babel-core 5.6.2 will break ./scripts/objc-test.sh tests. The version that works is babel-core 5.5.6.
For that reason this PR contains this workaround. In package.json I explicitly request babel-core 5.5.6:
    "babel": "5.4.3",
    "babel-core": "5.5.6",

Would somebody please figure out why babel-core 5.6.2 breaks the build loop?

The build loop failed because the flow server is busy:
Flow server launched for /private/tmp/react-native-x3yOQW0y/EndToEndTest
Spawned flow server (child pid=2838)
Logs will go to /var/folders/vy/rcv48w3j4w79llzf_x6qnvw40000gn/T/flow/zSprivatezStmpzSreact-native-x3yOQW0yzSEndToEndTest.log
The flow server will be ready in a moment.
Error: flow server is busy
Error: flow server is busy
Error: flow server is busy
No errors!
[Info] Loading settings for scheme 'EndToEndTest' ...

That's not really my problem, is it?

flow server is busy is just a warning, after that it says No errors and continues the build, so that's not the reason for the failure. This is:
/Users/travis/Library/Developer/Xcode/DerivedData/EndToEndTest-bmjlkbqwxoavxthdezsighobnyjh/Build/Intermediates/EndToEndTest.build/Debug-iphonesimulator/EndToEndTest.build/Script-4CED847C1B3756CA00715E21.sh: line 2: /tmp/react-native-x3yOQW0y/EndToEndTest/../../packager/launchPackager.command: No such file or directory

Speak English or just meet me somewhere to discuss this matter

@frantic Ah, thanks! I'll look into it. BTW, I think none of the PRs pass the build loop right now because of  babel-core 5.6.2. Is somebody looking at it?

Here is the problem: babel-core 5.6.2 will break ./scripts/objc-test.sh tests.

I'm looking into this now. What makes you think babel is the reason? Could you please compare packager output bundles?

Looks like displayName annotations are missing...

What makes you think babel is the reason?

My local version was not showing the problem. Then I found that the difference was the build loop using babel-core 5.6.2 while my local version that worked used babel-core 5.5.6. When I added babel-core 5.5.6  to package.json the ./scripts/objc-test.sh passed.
The problem could be something completely different. But that one line makes the problem go away.

Finally, Travis CI passed! Please let me know if you want me to make more changes. Otherwise I'd be ready to rebase/squash. Cheers.

@frantic Ready for review. I've merged the tip of master. Travis CI build passes.

@frantic Is there still interest in this PR? Travis CI passed 17 days ago. I need to know whether there is still interest in my changes before I commit more time into keeping this branch in sync with master.

@nicklockwood wondering what do you think about this

Something new here? Today i had a really hard time to figure out how to debug on a real device. In the end i manually changed "localhost" to my ip address in all 4 files. Maybe we should write it to the troubleshooting page.

@ms88privat This PR has been on my TODO list for quite a while. But lately I've been just too busy. There is also one open question whether protocol, hostname, and port should be separate fields.
@ide @frantic: Hey guys, can I get a quick yay/nay on the discussion in https://github.com/facebook/react-native/pull/1546#discussion-diff-34632065 and https://github.com/facebook/react-native/pull/1546#discussion-diff-34632468 ?
In a nutshell @frantic questions whether it makes sense to have protocol, hostname, and port as separate fields. Instead he suggests we should just use one URL. I think it will be better to have separate fields.
Final vote?

Either approach is fine with me since neither really blocks the other. I do like being able to configure just the hostname because I use mycomputername.local instead of localhost for example.

@frantic Hi, I have made all the additional changes as requested:

Info.plist: url instead of protocol plus hostname
renamed RCTWebSocketExecutorURL to RCTPackagerURL
I fixed the nits too.
All tests pass.
Are we getting closer?

This looks good! Would love to get this merged so we can start building some tooling around it.

@jsierles Me too! It is unclear to me who is assigned to this PR. Is it @frantic ?
(And in the meantime this branch got out of sync again...)

It looks like the URL schema for loading the JS files has changed. But I think somebody missed to adjust the Movies and SampleApp examples... What about the iOS templates?

Tests are passing But I didn't do anything except for merging master:
Merge made by the 'recursive' strategy.
 website/jsdocs/jsdocs.js             |  29 ++++++++----
 website/layout/AutodocsLayout.js     | 142 ++++++++++++++++++++++++++++++++++++++++----------------
 website/server/extractDocs.js        |   3 +-
 website/src/react-native/showcase.js |   6 +++
 4 files changed, 130 insertions(+), 50 deletions(-)

I don't see how those changes could fix the build loop.
Is it possible that the build/test loop sometimes just randomly fails?

@frantic @ide @nicklockwood Would anybody of you be so kind and review this PR? Thanks!

@frantic @ide @nicklockwood It looks like nobody is interested in this PR. I'll leave it open for another 7 days. But then I'll close this PR if I don't hear back from you guys.

@bparadie - can you rebase?
@nicklockwood - do you have any time for this?
cc @vjeux this looks useful

Just to add my 2c here. This issue is important because it stops developers from getting on board as quickly as possible with debugging from devices. We still have to manually update RCTWebSocketManager.m, and these changes are overwritten when updating React Native. Now that hot reloading is a reality in React Native projects, it's even more important.

Time is up. I am closing this PR.

Hmm, too bad on this one. Given android is out now, maybe it's time to look at a single cross platform solution that doesn't depend on plist files or anything platform-specific. A global config file - maybe package.json?

Sad, this is something that would be really useful.

I've posted this on product pains so it would be great if you could upvote it there and show the react-native team that this is an important feature https://productpains.com/post/react-native/allow-packager-port-to-be-configurable-change-from-8081/


Can you provide a configuration in tsconfig that requires the function to manually specify the return value type, which helps with code readability and maintenance

🔍 Search Terms
return value type
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
Can you provide a configuration in tsconfig that requires the function to manually specify the return value type, which helps with code readability and maintenance, this is a option config item
📃 Motivating Example
helps with code readability and maintenance
💻 Use Cases

What do you want to use this for?
function func(aa:string): number {...}
let a = (b: number): string => {...}

What shortcomings exist with current approaches?

What workarounds are you using in the meantime?

You can use ESLint for this: https://typescript-eslint.io/rules/explicit-function-return-type/

This seems like a linter's job


wdomirror: init at unstable-2021-01-08

Motivation for this change
Adds a small tool which mirrors the display to a window, useful for wlroots compositors which do not have mirroring capabilities, ex. sway.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114316 at b6c1dc84 run on aarch64-linux 1

1 package failed to build:

wdomirror

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/wayland/wdomirror/default.nix:26:3:
   |
26 |   installPhase = ''
   |   ^


authenticator code not coming out

i added the google authenticator but the six digit number is not coming out, i mean the code. what will i do? or is there any version that i can use? please write me back because i need it for security purpose. thank you.

Can you confirm if your secret is encoded in Base32?
You can check if there is any character out of Base32 alphabet. See Base32 alphabet from https://en.wikipedia.org/wiki/Base32#RFC_4648_Base32_alphabet


Multiple connections & threads from a single process

I tried wrapping Connection with Arc in order to use it across multiple thread only to run into an error, InnerConnection is wrapped in a RefCell.
Per the duckdb docs, multiple reads and writes should be possible from a single process, the python lib allows that and I was wondering if there's a way to achieve this.
My current implementation involves creating a database with Connection::open("file_name") and subsequently calling this same function within each thread; it didn't work as I kept getting an error of the file being used by an existing process.
Is there something I'm missing? my current option to use channel mpsc where the consumer will hold a connection to the database and do the insertion from the producers within the multiple threads.
Thank you for the great work.

@dowusu care to sure your findings? What worked in the end the best for you?

I ended up with something that looks like the below;  btw try_clone works as advertised & I replaced my channel implementation which serialises access to duckdb on a single thread with multiple connection.
pub struct MemCache {
    conn: Connection,
    conf: PrestoSettings,
}

impl MemCache {
    pub fn new(conf: PrestoSettings) -> Result<Self> {
        let conn = Connection::open_in_memory()?;
        info!("Creating an in-memory database.");

        Ok(Self { conn, conf })
    }

      pub fn get_connection(&self) -> Result<Connection> {
        self.conn.try_clone()
       }
    }

Usage was along these lines
let db = MemCache::new(config);

for i in 0..10 {
    let conn = db.get_connection().expect("Handle the error, I've not had a single failure");
    thread::spawn(move || {
       // you can work with the connection object/struct
   });
}

I hope this helps. Thank you.

I ended up with something that looks like the below; btw try_clone works as advertised & I replaced my channel implementation which serialises access to duckdb on a single thread with multiple connection.
pub struct MemCache {
    conn: Connection,
    conf: PrestoSettings,
}

impl MemCache {
    pub fn new(conf: PrestoSettings) -> Result<Self> {
        let conn = Connection::open_in_memory()?;
        info!("Creating an in-memory database.");

        Ok(Self { conn, conf })
    }

      pub fn get_connection(&self) -> Result<Connection> {
        self.conn.try_clone()
       }
    }

Usage was along these lines
let db = MemCache::new(config);

for i in 0..10 {
    let conn = db.get_connection().expect("Handle the error, I've not had a single failure");
    thread::spawn(move || {
       // you can work with the connection object/struct
   });
}

I hope this helps. Thank you.

Nice! Thanks for the reply!


DB creation error

I am getting an error building out the DB.  I think it has to do with the version of ruby and mysql.  it looks like this problem has been fixed in the latest version but still persists in 2.1.0  will fluxday work with the current ruby?
rake db:migrate
(in /root/fluxday)
==  CreateProjects: migrating =================================================
-- create_table(:projects)
rake aborted!
StandardError: An error has occurred, all later migrations canceled:
Mysql2::Error: All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead: CREATE TABLE projects (id int(11) DEFAULT NULL auto_increment PRIMARY KEY, name varchar(255), code varchar(255), description text, is_deleted tinyint(1) DEFAULT 0, created_at datetime, updated_at datetime) ENGINE=InnoDB

Duplicate of #5 ?

aah, yeah, that looks to be the same issue.  Closing


Move assets/ to resources/assets/, move templates/ to resources/views/

assets -> resources/assets/
templates -> resources/views/

now more inline with laravel/blade

renamed the title of this PR and pushed some new commits:

assets -> resources/assets/
templates -> resources/views/


Crashes trying to create DM channels for new game

Deployed to heroku. On first match (and every subsequent match), app crashed before game begun.
Getting DM channel for jeremy
Getting DM channel for eric
No open channel found, opening one using U0P8WHNMP
/app/node_modules/rx/dist/rx.js:579
    throw e;
          ^
TypeError: undefined is not a function
    at _loop (/app/src/texas-holdem.js:491:34)
    at TexasHoldem.dealPlayerCards (/app/src/texas-holdem.js:484:45)
    at TexasHoldem.playHand (/app/src/texas-holdem.js:103:10)
    at /app/src/texas-holdem.js:56:27
    at /app/node_modules/rx/dist/rx.js:4924:20
    at tryCatcher (/app/node_modules/rx/dist/rx.js:567:29)
    at InnerObserver.onNext (/app/node_modules/rx/dist/rx.js:4806:43)
    at InnerObserver.tryCatcher (/app/node_modules/rx/dist/rx.js:567:29)
    at AutoDetachObserverPrototype.next (/app/node_modules/rx/dist/rx.js:5274:51)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/app/node_modules/rx/dist/rx.js:1710:35)

npm ERR! Linux 3.13.0-85-generic
npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `node src/main.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node src/main.js'.
npm ERR! This is most likely a problem with the slack-poker-bot package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node src/main.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls slack-poker-bot
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /app/npm-debug.log

Ran locally, got this error on game start:
Getting DM channel for jeremy
/Users/jhummel/github/slack-poker-bot/node_modules/rx/dist/rx.js:579
    throw e;
    ^

TypeError: SlackApiRx.getOrOpenDm.subscribe is not a function
    at _loop (/Users/jhummel/github/slack-poker-bot/src/texas-holdem.js:491:34)
    at TexasHoldem.dealPlayerCards (/Users/jhummel/github/slack-poker-bot/src/texas-holdem.js:484:45)
    at TexasHoldem.playHand (/Users/jhummel/github/slack-poker-bot/src/texas-holdem.js:103:10)
    at /Users/jhummel/github/slack-poker-bot/src/texas-holdem.js:56:27
    at /Users/jhummel/github/slack-poker-bot/node_modules/rx/dist/rx.js:4924:20
    at tryCatcher (/Users/jhummel/github/slack-poker-bot/node_modules/rx/dist/rx.js:567:29)
    at InnerObserver.onNext (/Users/jhummel/github/slack-poker-bot/node_modules/rx/dist/rx.js:4806:43)
    at InnerObserver.tryCatcher (/Users/jhummel/github/slack-poker-bot/node_modules/rx/dist/rx.js:567:29)
    at AutoDetachObserverPrototype.next (/Users/jhummel/github/slack-poker-bot/node_modules/rx/dist/rx.js:5274:51)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/jhummel/github/slack-poker-bot/node_modules/rx/dist/rx.js:1710:35)

Issue seems to occur on the first game with a new player who hasn't had a DM with the bot before. Once the game crashes with the new player and is restarted, it works next time.

confirmed i have the same


added isInRole() method with has() alias

See issue #56.
I used the built-in Meteor.user() method, which will automatically throw a Error: Meteor.userId can only be invoked in method calls. Use this.userId in publish functions. error when called in the wrong place. After that, the call is passed on to userIsInRole.

What is a process of this pull request? It would be great if this would be addressed.

@rijk, was there something else you wanted to do with this or is it ready to merge/test?

Hm, this was a while back.. I think it was good to go but I couldn't get the tests to pass.

Yea, I think this should be done a bit better. The implementation has few improvements possible. For example, currently you try to access DDP._CurrentInvocation.get always when there is an error, this is possibly hiding some other errors.
I will look into this and make a similar pull request, if this is OK?

Sure @mitar , go ahead!

I made a separate package which makes Meteor.userId() (and Meteor.user()) work inside a publish context. I think this is better than putting this into this package, because it is independent problem from it.
Now, having some sugar/simpler functions to make checks for the current user might be something useful, but should be then a separate pull request.

I am closing this in favor of discussion in #56. Let's decide there what we should do about this and then add only has function, if we decide to go further with this.


Conversational Chain Error 429

System Info
Today, all of a sudden I'm getting a error status code 429 using the Conversation chain. Nothing has changed, expect the day I've run the script. Any ideas?
It works with the normal LLM chain, so it must be to do with the Conversation Chain not working or the memories.
Using Flowise.
Chrome
@hwchase17
@agola11
Who can help?
No response
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
Request failed with status code 429 and body {"error":{"message":"Rate limit reached for 10KTPM-200RPM in organization org-ByeURhCRRujcKf7u7QrlrudH on tokens per min. Limit: 10000 / min. Please try again in 6ms. Contact us through our help center at help.openai.com if you continue to have issues.","type":"tokens","param":null,"code":"rate_limit_exceeded"}}
Expected behavior
I expect the LLM chain to write the content.

Your conversation chain may have accumulated too much chat history(>10000 tokens). I think if you set a max token for your memory it should work. Example : memory=ConversationTokenBufferMemory(llm=OpenAI(), max_token_limit=600)

I guess its possible. What memory do you use? Some of the memory types do make additional calls(primarily to summarize) to the LLM


<---More---> kind of output using shellstream

Good Day.!
I have been using Posh-SSH for automating linux & Unix boxes which is awesome.
In this case I am using shellstream method to get the output .
Shellstream method is working properly as I am getting the output but it is partial and not full.
Kindly help in getting the Full output.. Thanks!

I have been using Posh-SSH for automating linux & Unix boxes which is awesome.
In this case I am using shellstream method to get the output .
Shellstream method is working properly as I am getting the output but it is partial and not full.
Kindly help in getting the Full output.. Thanks!

Reply to this email directly, view it on GitHub, or unsubscribe.

$stream.Write("Show disk`n") - already a backtick n is in place along with the code. should I give one more?

Yes, you read your stream in a loop until you get the more string using regex and send another and keep doing it untill you get a prompt, you will need to write  a regex that will match om the specific prompt for the device
Sent from my iPhone

On Jul 29, 2020, at 3:23 PM, Deepan824<EMAIL_ADDRESS>wrote:

$stream.Write("Show disk`n") - already a backtick n is in place along with the code. should I give one more?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you so much Carlos 👍  :-)


Avoid character '' for interpolation

Is your feature request related to a problem? Please describe.
It gives issues when you have to work with Windows paths: ('\(path.dirData)\\(dbname)\', '\(path.dirData)\\(dbname)\foo\')
Describe the solution you'd like
I think that the characters $(string) or even {{string}} are better to define an interpolation, since they are not widely used into a text or path.
At bash, $(var) is used; the Go templates use {{string}}.

CUE is a JSON superset, which put limitations on the choice of interpolation syntax if one wants to have just a single string syntax (which is ideal). The most obvious illegal sequence one can create in JSON is one starting with \ followed by an unsupported escaped character. This is how we ended up with \(. There is precedence for this in other languages too.
Note that, "${foo}" is a valid JSON string, so one would need an additional mechanism to indicate whether strings should be interpolated or not (like @"%{foo}"). This is not ideal.
I'm not sure what this issue is here, but note that you can use the #"\(foo)"# syntax to include a literal \( in strings. To mix both, use #"\(foo)\#(foo)"#, etc.

Also, we don't take language changes lightly. We are moving towards stabilizing the language. I know that we recently changed the syntax of definitions, but this was to address some serious shortcomings of the previous approach. The benefit in this case fare outweighed sticking with the status quo.

Closing as the requested functionality is not possible and escape delimiters should be sufficient to address the issue.

This issue has been migrated to https://github.com/cue-lang/cue/issues/433.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


CVE-2023-5129

Describe the bug
Kiwi needs to fix CVE-2023-5129 ASAP
I'm pretty sure there was an open issue for CVE-2023-5129, but somehow it disappeared.

Also CVE-2023-5217. It doesn't look so great when serious security issues mysteriously disappear from the issue tracker. I'll just hope it was an accident, because I wouldn't want to consider the implications of the alternative.

Glad I'm not the only one that noticed it. Here's the original email notifications as proof:

How certain are we that Kiwi is indeed affected by this issue, i.e. uses its own (old) libwebp library?
Is there a website that allows you to check if a browser is vulnerable?

How certain are we that Kiwi is indeed affected by this issue, i.e. uses its own (old) libwebp library? Is there a website that allows you to check if a browser is vulnerable?

Not certain. But it seems likely given that the browser renders webp and vpx files and hasn't been given the latest patches. Enough that I'm not using it in the meantime.

It's also worth mentioning that the CVEs were published in late September, while the last commit was in mid August.

The Chromium version in Kiwi's latest commit says it's in 105.0.5195.24.

@ggtylerr Interesting, because I took a look at what Kiwi says on my Android phone (installed via the Playstore) and it reports 116.0.5845.72. Therefore, much more recent than 105, but still affected, apparently.
@htsmi Fair enough! I thought of the possibility that Kiwi may render webp (and/or even vpx) media using a system wide API or library. But I have to admit that I have no clear understanding of the internals. I just wanted to bring the possibility into play.

@ggtylerr Interesting, because I took a look at what Kiwi says on my Android phone (installed via the Playstore) and it reports 116.0.5845.72. Therefore, much more recent than 105, but still affected, apparently.

That is a bit interesting but it turns out that there's an action workflow that automatically updates chromium and makes a release. Here's the release that has that version.
Either way, the release was made a full month before the two vulns were published, so it's definitely not patched.

@kiwibrowser do you intend to release an updated version soon? If you're not able to fix security holes in a timely manner, it is not responsible to continue the project (IMO).

@kiwibrowser do you intend to release an updated version soon? If you're not able to fix security holes in a timely manner, it is not responsible to continue the project (IMO).

To be fair, it is a small development team doing FOSS work.
That being said, it's very troubling that they haven't even commented on this, much less release a patch. The only response so far is the issue being deleted, which, like @htsmi said, doesn't look good.
I'll be notifying the FFUpdater team and Google soon if this isn't resolved. These are two major vulns and they're still publicly available without any notice.

To be fair, it is a small development team doing FOSS work.

That's right. It is still irresponsible to keep a software with known serious vulnerabilities ready for download. It should at least be removed from Google Play.

New release 🎉
https://github.com/kiwibrowser/src.next/releases/tag/6453943399
now 116.0.5845.240


4.2 regression: TS2345: argument is not assignable to a parameter of a generic type

Bug Report
Mapped type's element is not assignable to type T | undefined where T is unconstrained
🔎 Search Terms
mapped types, TS2345, generic, not assignable
🕗 Version & Regression Information
Regression in TS 4.2.3
⏯ Playground Link
Playground link with relevant code
💻 Code
type MyMap<M extends object> = {
    [K in keyof M]: {
        x: number
    }
}

declare function g<T>(value?: T): void;

function f<M extends object>(mymap: MyMap<M>, k: keyof any) {
    const elemofM = mymap[k as keyof M]
    g(elemofM)
    //~~~~~~~ TS2345: Argument of type '{ x: number; }' is not assignable to parameter of type 'MyMap<M>[keyof M]'.
}

🙁 Actual behavior
error TS2345: Argument of type '{ x: number; }' is not assignable to parameter of type 'MyMap[keyof M]'.
🙂 Expected behavior
No error (it was not in TS 4.1)

Repro that fails in both 4.1 and 4.2:
function f<M extends object>(mymap: MyMap<M>, k: keyof M, z: { x: number }) {
    const q1: MyMap<M>[keyof M] = z;  // Ok
    const q2: MyMap<M>[keyof M] | undefined = z;  // Error
    const q3: MyMap<M>[keyof M] | string = z;  // Ok
}

It only fails for unions with undefined or null. The issue is a missing normalization step in code that eliminates undefined and null from target unions in order to improve the error reporting experience.


Make LIKE queries with wildcards work

Hacked up something ugly, but it seem to work... Feel very free to make a nicer solution :)

Closing this :)


only polyfill node's global fetch when it's definitely undefined

Description
When you're using the Lit SDK in combination with packages that load WASM modules, the global node-fetch override breaks local / data-url file imports. We noticed this when running lit along the new web3.storage SDK.  Its wasm-bindgen generated code actually loads the binaries using a data: url (see https://github.com/web3-storage/fr32-sha2-256-trunc254-padded-binary-tree-multihash/blame/main/gen/wasm.js#L284C32-L284C32) which works fine with any fetch in node and browser environments but that's not supported by node-fetch < version 3.
Here's a project that uses both libraries: https://github.com/elmariachi111/w3up-next-sample. yarn & yarn build this to see the error messages.
-> alternatively we'd suggest to bump your node-fetch version.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[o] New feature (non-breaking change which adds functionality)
[o] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[o] This change requires a documentation update

How Has This Been Tested?

[x] yarn test:unit (fails 4 suites on my box, same as the branch's base)
[o] yarn test:e2e doesnt run out of the box, had to skip it

tested this with a compiled version on a demo project of ours (based on Next 13.5.6 & @web3-storage/w3up-client ^12.0.0)
Checklist:

[?] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[o] I have commented my code, particularly in hard-to-understand areas
[o] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[o] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[o] Any dependent changes have been merged and published in downstream modules

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@elmariachi111 thank you for flagging this. you bring up a great point on wasm_bidgen targets auto loading API's. In general we should be checking if there is already a definition before overriding.


Submitting a parameter form on a saved dashboard reflects ?sql= in query string

This means that if a dashboard has a large amount of SQL in the saved queries - too much for the hosting provider's request URL length limit - the user will get an error.
Oddly it only happens if you submit the form starting at /dashboard/example/ - if you start at /dashboard/example/?date=x (prefilling the form) hitting submit doesn't include the SQL in the resulting URL.

Weirdly I can't replicate this outside of the VIAL example where it first happened - even though VIAL is running 0.11a0 and so is simonwillison.net

Aha! The bug only shows itself if there was an error in the SQL when executed without the parameters - since that causes the SQL to be displayed back again in a textarea.

https://simonwillison.net/dashboard/issue-74-demo/ exhibits the bug now.


can't ssh to running PWD

Hello, I have seen it should be possible to SSH to running instance. I have also checked issue https://github.com/play-with-docker/play-with-docker/issues/196 and links inside, but that didn't help.
There is probably a new feature in PWD which is showing the ssh, but even copying it doesn't work.
In comparison with how-to, the address provided in the link to copy contains "ïp" at the begining (ie. ssh<EMAIL_ADDRESS>and looks like it's using standard port 22, not 1022.
However, the attempts are rejected always. It looks as the only allowed auth mechanism is with keys. I tried to add my public ssh key to the machine's authorized_keys, but that still didn't help.
Could you please check? The ssh would be a very nice function, making things a lot easier.
And maybe if things have changed, it would be good to fix the how-to on https://medium.com/@marcosnils/pwd-ssh-c12080ea11d1

Hey @jimo4242 do you still have issues?. What error do you get?

Am Having the same exact issue.

Hi, @marcosnils Any reason why you close the issue?

@marcosnils It's working now, thanks.

Yes, because I've requested for more information and nobody is providing it. Seems to me like it's a dupe of https://github.com/play-with-docker/play-with-docker/issues/196 but I can't do anything unless I got more info. Just tried sshing into a PWD instance and it works.

There's no need to set the port to 1022 anymore. You can just use ssh<EMAIL_ADDRESS>

I see. With this I however get Permission denied (publickey). Do I need to set something up?

i am having the same issue

To all those who are here for same issue.
Thanks @sidebo
#247 solved my  problem.

Run ssh-keygen and fill out name of file and empty passphrase.
Run ssh -i <File name entered in first step> <docker ssh address>. Example: ssh -i ida_rsa<EMAIL_ADDRESS>

To all those who are here for same issue.
Thanks @sidebo
#247 solved my problem.
1. Run `ssh-keygen` and fill out name of file and empty passphrase.

2. Run `ssh -i <File name entered in first step> <docker ssh address>`. Example: `ssh -i ida_rsa<EMAIL_ADDRESS>

Hello, I did this and still get the same error
Permission denied (publickey)
I'm on Fedora 33

For anyone getting this error 👇
Permission denied (publickey).
I solved it by just creating ssh keys like this
my environment:

Ubuntu (WSL2)

ssh-keygen
accept all defaults and it worked for me the next time I tried to ssh into the running playground docker machine.

In ubuntu 22, in u need to gen keys like:
ssh-keygen -t ed25519 -P "" -f ~/.ssh/id_ed25519
then do regular ssh x@y    #-i was not req in my case

@gitdlnow I used it in Ubuntu 23.10. It worked. I think most people here are from ubuntu only.

In ubuntu 22, in u need to gen keys like: ssh-keygen -t ed25519 -P "" -f ~/.ssh/id_ed25519 then do regular ssh x@y #-i was not req in my case

@gitdlnow This worked for me. So rsa is not the correct key format to use in this authentication.

To all those who are here for same issue. Thanks @sidebo #247 solved my problem.

Run ssh-keygen and fill out name of file and empty passphrase.
Run ssh -i <File name entered in first step> <docker ssh address>. Example: ssh -i ida_rsa<EMAIL_ADDRESS>

Thank you its worke fo me

To those using windows + gitbash like me
Use these steps [works as of Aug 2024]
S-1) Create the key pair by ssh-keygen -t ed255 -P "" -f ~/.ssh/id_ed255
S-2) Copy ssh like shown below

S-3) Connect using the command
 ssh -i ~/.ssh/id_ed255<EMAIL_ADDRESS>


Tooltip and Popover don't work while inside a Dialog

I believe this has to do with (from a glance of the source) the fact that they both use FloatingPortal and I'm guessing there is a clash in z-index, leading to them not showing.

Any fix for this?

i tried <Tooltip content={tooltip} className=" !z-9999999"> but it did not work


angular 9.0.0-rc.2 Cannot read property 'onDestroy' of undefined

I'm using nrwl NX and jest.
When I run jest I'm getting
TypeError: Cannot read property 'onDestroy' of undefined

node_modules/@ngneat/until-destroy/bundles/ng:/@ngneat/until-destroy/lib/until-destroy.ts:32:48
at Object.__decorate (../../../../node_modules/tslib/tslib.js:93:99)

Has anything changed in the latests RC's that could cause this to happen?

Update
I forked and updated until-destroy to the latest angular rc release, but the tests work, so it hasn't got anything to do with angular/core.
Nx uses the library jest-preset-angular and nx is currently using version 7.1.1
jest-preset-angular has released a version 8.0.0, but nx still hasn't updated to that version, so that might fix it.
The only thing i can think of is that jest-preset-angular doesn't compile to ivy code and thus ɵcmp will be null.
But I'm not sure how to get around it, or if I just have to wait for nx to catch up to angular 9. :(

Hi, this is our peer dependencies requirements:
"peerDependencies": {
  "@angular/core": ">=9.0.0-next.10"
}

So I guess you'll have to wait or use the older version.

I have some issue when try run my app in storybook. I can't use old version, because i use Ivy.

This lib really useful, but we had to remove because of this bug.

We have the same issue in storybook using Ivy

For some reason, Storybook doesn't use Angular Ivy with my setup and I had the same error. I added postinstall script with ngcc option to package.json according to the official docs and now everything works well.
After making these changes you may need to delete node_modules (rm -rf) and install them again.
P.S. to check if Ivy enabled you can import it from angular/core
import { Component, OnInit, ɵivyEnabled as ivyEnabled, OnDestroy } from '@angular/core';

ngOnInit(): void {
    console.log('ivyEnabled', ivyEnabled);
}


modelviz: use get_model_compat and look up missing app_label

Fixes https://github.com/django-extensions/django-extensions/issues/881.

Coverage decreased (-0.005%) to 32.113% when pulling 3665f3421b4d53aab55c298ce2e6b38c818c9d01 on blueyed:graph-models-use-model-compat into 5bda5ca6a16fefaf9a2334e247beb5b055365dce on django-extensions:master.

Coverage decreased (-0.005%) to 32.113% when pulling dba191e04ee1f64452a8e018c29536f9622c16de on blueyed:graph-models-use-model-compat into 5bda5ca6a16fefaf9a2334e247beb5b055365dce on django-extensions:master.

Thanks !


Run button missing

version of Unfold
0.41.0
browser
Chrome  131.0.6778.205
Describe your issue
Hello, first I want to thank you for the awaysome theme. I love it and I will use it in future for sure!
So, the problem I have and as I see not only I is that "RUN" button is missing in actions block.
After spending some time reviewing the code, I discovered the following which was the problem for my case:

In actions.html > within the block actions-submit > the x-show attribute in the button tag was causing the problem. See the pictures below!

Why you removed several questions from the issue template?

I filled these fields that I thought were important. If are mandatory, I will fill them as well. Let me know.

please answer all questions. I believe you fill your answer there.


Add space for iPhone status bar

Issue
When starting the display in portrait mode, a space is carved out for the status bar. Upon transitioning the display to landscape mode and back to portrait mode, the safari webapp recalculates the status bar dimensions and for some reason converts it to black-transparent. There should be a soft-fix for this.
The below images illustrate this transition. Notice the status bar on the left of the display.

... transition to landscape and back to portrait ...

Proposed Fix
When the display starts up, if it is running on an iPhone and is in portrait mode, it should save the dimensions of the screen. If it ever returns to portrait mode from landscape and the screen width has increased, it should fill the gap with black and float right, creating space for the status bar.

Mostly addressed with commit 5d33455. Still has the following issues on iPhone only:
Issue 1
Occurs when force reloading the display from portrait mode (through the inspector, after the system has accounted for the status bar space) and then going from landscape to portrait.

The display is too tall and overflows on the right side

Issue 2
Occurs when opening the display in landscape mode and going to portrait:

Status bar is still wrong
The display is too tall and overflows on the right side


[downloader/hls] fix to do unpad after decrypt

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[ ] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[ ] Covered the code with tests (note that PRs without tests will be REJECTED)
Not done specifically. Consider to be satisfied by the Description below.
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Resolves #30208.
unpad after decrypt seems to be needed from the start of supporting AES-128 in hlsnative downloader.
In ref 1. draft-pantos-http-live-streaming-17#section-<IP_ADDRESS> (now RFC 8216) in hls.py, it is described as:
An encryption method of AES-128 signals that Media Segments are completely encrypted using the Advanced Encryption Standard [AES_128] with a 128-bit key, Cipher Block Chaining, and PKCS7 padding [RFC5652]. (bold is by me)
It's hard to believe that not doing unpad didn't cause problems other than #30208 for a long time, but it seems to have been actually processed well by ffmpeg (when merge or fixup).
To confirm this, I made files from encrypted hls streams by youtube-dl ... --hls-prefer-native --fixup never without and with unpad (version 2021.12.17 and 2021.12.17 plus this PR), then did ffmpeg -loglevel trace -i INPUT -c copy -bitexact OUTPUT for both.
The OUTPUT files were identical, and in the log of without unpad INPUT, there were extra messages like [mpegts @ 0x7f886d803c00] Probe: 8192, score: 44, dvhs_score: -3, fec_score: -1 almost as many as the number of fragments, indicating skipping the paddings I guess.

I am by no means a subject expert, but I have reviewed the changes and the code in this PR is according to the CBC mode decryption example in the used crypto library's documentation:
https://pycryptodome.readthedocs.io/en/latest/src/cipher/classic.html#cbc-mode-1

Great to fix such an irritating bug with 1 line: let's hope we can release this soon, somehow.

PR from @kikuyan whose account was deleted.

Instead of importing unpad(), pull this from yt-dlp's aes.py
def unpad_pkcs7(data):
    return data[:-compat_ord(data[-1])]

and apply it to the decrypted bytes. Also consider pulling the rest of the Python AES decryption as an alternative to imported routines.


Get-PowerAppConnector is missing.

I just installed the module.  I don't have this command.

@ComputerHabit2  What is this "Get-PowerAppConnector"? In what documentation are you seeing it mentioned? Please provide a URL.

Hello,  Thanks for writing back.
I am trying to find what I was doing when I came across this.  I think I was trying to install the module.
When it was installing I was getting an error.
I did track down some module that is calling this command.
https://www.powershellgallery.com/packages/Microsoft.PowerApps.Administration.PowerShell/2.0.127/Content/Microsoft.PowerApps.Administration.PowerShell.psm1

Get-PowerAppConnector is defined in module Microsoft.PowerApps.PowerShell.  Microsoft documentation at https://learn.microsoft.com/en-us/power-platform/admin/powerapps-powershell#module-installation shows that we should be importing both for things to work correctly.

Maybe I was just having a bad connectivity day.  The link above was the article I was following.  Last week when installing the module there was a delay completing also.

I just ran the commands on another system with no issues.


Update the 'Ready' Status in Firebase to 'Ready For Pickup'

Successfully updated the 'Ready' Status in Firebase to 'Ready For Pickup'.


Allow defining a custom GazePointer

Describe the problem
https://github.com/microsoft/MixedRealityToolkit-Unity/pull/5610#discussion_r313096956

While being able to define your own GazeProvider means you also are able to define your own InternalGazePointer; it isn't very easily discoverable.

Related to https://github.com/microsoft/MixedRealityToolkit-Unity/issues/5545

Also, being able to implement your own GazePointer and provide that to the GazeProvider seems like a feature that's missing; given that user-defined pointer definition is available for all other pointer types.

Following up with Ken to see if there's anything else here we need