Keyboard not showing on Android using new embedding API

Android keyboard does not show up when tapping a Flutter TextField using the new Android embedding API (io.flutter.embedding.android). There are a few similar issues (#19644, #21370, #21911), but those seem to refer to non-embedding scenarios. They are closed, and I think they're fixed as well since using the "old" API works for us (see below).
Are we using the new API wrong? It doesn't seem to work with io.flutter.embedding.android.FlutterActivity either, which handles the setup for us.
The reason we're experimenting with the new embedding API is that we need to use TextureView instead of SurfaceView so we can animate screen transitions, fades etc. Everything else seems to work fine so far.
I've tested on my Samsung S7 running Android 8.0 as well as an emulator running 6.0, and both have the same issue.
Steps to Reproduce

Create a new Android application with an empty activity
Add flutter to the app as described by https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps
Initialize Flutter manually using the new embedding API

Here's how we initialize Flutter inside the MainActivity:
import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.widget.FrameLayout;

import io.flutter.embedding.android.FlutterView;
import io.flutter.embedding.engine.FlutterEngine;
import io.flutter.embedding.engine.FlutterShellArgs;
import io.flutter.embedding.engine.dart.DartExecutor;
import io.flutter.facade.Flutter;
import io.flutter.view.FlutterMain;

public class MainActivity extends AppCompatActivity {
    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        Flutter.startInitialization(getApplicationContext());
        FlutterShellArgs flutterShellArgs = new FlutterShellArgs(new String[0]);
        FlutterMain.ensureInitializationComplete(getApplicationContext(), flutterShellArgs.toArray());

        FlutterEngine engine = new FlutterEngine(this);
        engine.getNavigationChannel().setInitialRoute("/");
        String appBundlePath = FlutterMain.findAppBundlePath(this);
        DartExecutor.DartEntrypoint entrypoint = new DartExecutor.DartEntrypoint(getResources().getAssets(), appBundlePath, "main");
        engine.getDartExecutor().executeDartEntrypoint(entrypoint);

        FlutterView flutterView = new FlutterView(this, FlutterView.RenderMode.surface);
        flutterView.attachToFlutterEngine(engine);

        FrameLayout container = findViewById(R.id.container);
        container.addView(flutterView);
    }
}

main.dart:
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: Scaffold(
        body: TextField(),
      ),
    );
  }
}

Logs
The InputMethodManager seems to cancel the call to showSoftInput for some reason. I guess DecorView has focus instead of the FlutterView?
2019-04-04 14:46:04.608 27910-27910/com.example.myapplication D/InputMethodManager: showSoftInput - cancel : mServedView != view : DecorView@47040e3[MainActivity]  view : io.flutter.embedding.android.FlutterView{e948ad1 VFE...C.. ........ 0,0-1080,1848}

Output of flutter doctor -v:
[✓] Flutter (Channel dev, v1.4.8, on Linux, locale en_US.UTF-8)
    • Flutter version 1.4.8 at /home/chip/flutter
    • Framework revision fbefd6b816 (3 days ago), 2019-04-01 10:58:30 -0700
    • Engine revision a850016454
    • Dart version 2.2.1 (build 2.2.1-dev.2.1 None)

[✓] Android toolchain - develop for Android devices (Android SDK version
    28.0.3)
    • Android SDK at /home/chip/android/sdk
    • Android NDK location not configured (optional; useful for native
      profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[!] Android Studio (version 3.3)
    • Android Studio at /opt/android-studio
    ✗ Flutter plugin not installed; this adds Flutter specific
      functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)

[!] Android Studio
    • Android Studio at /home/chip/android-studio
    ✗ Flutter plugin not installed; this adds Flutter specific
      functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Connected device (1 available)
    • SM G930F • ce081718cde4393e01 • android-arm64 • Android 8.0.0 (API 26)

! Doctor found issues in 2 categories.

I think I found the cause of the issue - setting the FlutterView to focusable fixes it:
flutterView.setFocusable(true);
flutterView.setFocusableInTouchMode(true);

This is done in the old FlutterView, but seems to be missing in the embedding API:
https://github.com/flutter/engine/blob/d6d45da07e14e14f38b8e220080860ae1c12c87b/shell/platform/android/io/flutter/view/FlutterView.java#L144-L145
Any reason the embedding version of the view is not focusable by default? If not, I can create a pull request :)

@matthew-carroll

@chip2n thanks for reporting. I have confirmed the issue, and confirmed that making FlutterView focusable allows the keyboard to come up.
I have a PR up with the changes here:
https://github.com/flutter/engine/pull/8551

Hello, when can we expect to have this fix in the stable flutter channel ? Thanks

If it's not available yet, then it will be included in the next stable release.


Log partial completion acceptances

Problem:

If a user gets a lengthy autocomplete suggestion, they can accept only part of the suggestion. Ways they can do this:

CMD+Right arrow = accept the word
Typing out part of the acceptance

Change:

If a user accepts part of the autocomplete suggestion, then we log an acceptance event with the charCount.

Implications:

A suggestion can therefore have multiple acceptance events.
Acceptance events need an id so that we can do a COUNT DISTINCT to get a correct completion acceptance rate.
To get the highest fidelity acceptance rate in this partial acceptance world, we want to measure SUM(charCount) for acceptances ÷ SUM(charCount) for suggestions

CC: @kelsey-brown for visibility


curl: (7) Failed to connect to localhost port 8080: Connection refused

I deployed the atsea-sample-shop-app using the instructions provided but when I try to connect to localhost:8080 I get an error. How can I get past this error?
siddjain@goldenrwr-ca0:~/atsea-sample-shop-app$ curl http://localhost:8080
curl: (7) Failed to connect to localhost port 8080: Connection refused
siddjain@goldenrwr-ca0:~/atsea-sample-shop-app$ curl http://goldenrwr-peer1:8080
curl: (7) Failed to connect to goldenrwr-peer1 port 8080: Connection refused

siddjain@goldenrwr-ca0:~/atsea-sample-shop-app$ docker stack ps atsea
ID                  NAME                      IMAGE                                                     NODE                 DESIRED STATE       CURRENT STATE            ERROR                       PORTS
lvsocchhg467        atsea_reverse_proxy.1     dockersamples/atseasampleshopapp_reverse_proxy:latest     goldenrwr-peer1      Running             Running 20 minutes ago
fq6pl30hs2yh        atsea_payment_gateway.1   dockersamples/atseasampleshopapp_payment_gateway:latest   goldenrwr-orderer0   Running             Running 20 minutes ago
1v77pf8y56i2        atsea_visualizer.1        dockersamples/visualizer:stable                           goldenrwr-ca0        Running             Running 20 minutes ago
56eghx4ss6cb        atsea_appserver.1         dockersamples/atsea_app:latest                            goldenrwr-peer1      Running             Running 20 minutes ago
jn10asse4m82        atsea_database.1          dockersamples/atsea_db:latest                             goldenrwr-orderer0   Running             Running 20 minutes ago
r5fzswkbbghz        atsea_reverse_proxy.1     dockersamples/atseasampleshopapp_reverse_proxy:latest     goldenrwr-ca0        Shutdown            Failed 20 minutes ago    "task: non-zero exit (1)"
idrg0djwuy5x        atsea_appserver.2         dockersamples/atsea_app:latest                            goldenrwr-peer0      Running             Running 20 minutes ago

in the logs I can see
atsea_appserver.1.56eghx4ss6cb@goldenrwr-peer1    | 2019-01-15 00:51:28.379  INFO 1 --- [           main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat started on port(s): 8080 (http)
atsea_appserver.1.56eghx4ss6cb@goldenrwr-peer1    | 2019-01-15 00:51:28.390  INFO 1 --- [           main] com.docker.atsea.AtSeaApp                : Started AtSeaApp in 14.796 seconds (JVM running for 15.926)

Changing suspend=y to suspend=n in following
Dockerfile-dev:ENTRYPOINT ["java", "-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005","-jar", "/app/AtSea-0.0.1-SNAPSHOT.jar"]
did the trick

I am equally having the same issue unable to curl the localhost to port 8080. The docker container is running fine as supposed.
curl: (7) Failed connect to localhost:8080; Connection refused

i same the same problem any sloution?

We found several problems in that this docker example does not follow some good practices, such as specifying the concrete versions of the images. We will show the changes to each file below:
database/Dockerfile
Change:
FROM postgres
to
FROM postgres:12
Change the routes to copy the configuration files:
COPY pg_hba.conf /usr/share/postgresql/9.6/
COPY postgresql.conf /usr/share/postgresql/9.6/

to
COPY pg_hba.conf /usr/share/postgresql/12/
COPY postgresql.conf /usr/share/postgresql/12/

app/Dockerfile-dev
change:
ENTRYPOINT ["java","-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005","-jar","/app/AtSea-0.0.1-SNAPSHOT.jar"]

a
ENTRYPOINT ["java","-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005","-jar","/app/AtSea-0.0.1-SNAPSHOT.jar"]

docker-compose-dev.yml
In the services/database/environment section add the following line:
POSTGRES_PASSWORD: gordonpass

Thanks to @jvelez30

Closing issues due to repo archiving. Feel free to fork so it can live on!


public method and classes for external usage

Can I use this private API ?

Unfortunately all classes and methods you marked are part of the internal implementation. We prefer to keep it private to give us more flexibility to change internal implementation details. Please let us know why do you want to make it all open and I'll suggest the best solution for your use case.

I need to draw the concrete shape (Locus) of the SVG in my own UIView, with gradient and all the stuff.
Need to convert your color to UIColor (RenderUtils), to display svg palette (all the colors used in the svg). Why do you keep it private ?  Maybe you can mark ShapeRenderer as public (to render shape in our own UIView)?

All other classes (like CachedLayer, etc.) I've marked because RenderUtils depends on it.


group loot

Group Loot tooltip is not displayed after mouseover, master looter and everything around loot aint working

I have an idea as to why this happens.

tooltop dont show only in instance/raid, in world its ok


Add Thorium browser patches

Description
Performance optimizations from Thorium browser
Who's implementing?

[ ] I'm willing to implement this feature myself

The problem
I used to use this browser, https://github.com/Alex313031/thorium it is not privacy oriented, but it has tons of performance optimizations, and is pretty vanilla, its the same as Chromium but optimized, also, the patches are listed and are applied in a clean way. Maybe you can add these https://thorium.rocks/optimizations.html
Useful links and detailed documentations: https://thorium.rocks/docs/ https://thorium.rocks/misc/dev
Possible solutions
Applying just the compiler optimizations
Alternatives
No response
Additional context
No response

Also interesting https://thorium.rocks/docs/sandbox.html

Please be more specific about which patches you mean exactly. Thorium has lots of patches which are already present in ungoogled-chromium.

I mean these, also they are compiler optimizations listed here https://thorium.rocks/optimizations.html and the sandbox patches are excellent and well explained https://thorium.rocks/docs/sandbox.html

Please be more specific about which patches you mean exactly. Thorium has lots of patches which are already present in ungoogled-chromium.


Update Perovskite WF

Added a new perovskite experiment template called perovskite_demo which is identical to wf1_test except it:

Models actions/parameters of stock preparation

it does this instead of accepting a stock solution from a dropdown
this will allow experimentalist to record nominals and actual values during stock preparation

Array (of length n) parameters now display as string array in a single form rather than n separate forms
Add missing parameters (heat temperatures, mixing speeds and times)

Other update:

add all users to all orgs on python manage.py setup_users

Passes all API tests and all (relevant) database tests.

(still passes all tests)


facial landmarks from video file

HI
example_detection.m is finished successfully ,
but I need to save facial landmarks from video file , how can I do that ?

Hi,
You can use the existing code for facial landmark tracking of video sequences. But, you have to implement the tracking framework using a new model training strategy. You may also have to develop a face detector and a classifier to determine the success/failure in the tracking process.
I have a plan to implement a tracking code but I am very busy this month. I may push a new tracking code to Github later next month (March).
Cheers,

Hi，How to use the code to make a 5-point detection, I know the dataset has 58 landmarks, but I only need to detect 5  key landmarks, what should I do?


Vulnerable Regular Expression

The following regular expression used in parsing the JSON file is vulnerable to ReDoS:
/\s+$/

The slowdown is moderately low: for 50.000 characters around 2 seconds matching time. However, I would still suggest one of the following:

remove the regex,
anchor the regex,
limit the number of characters that can be matched by the repetition,
limit the input size.

If needed, I can provide an actual example showing the slowdown.

@cristianstaicu Yeah I noticed that too , as Snyk warns me about them vulnerabilities  :smile:
I don't have a serious app using this lib but I'm concerned about further uses :thinking:
@get will be there any patches ?!

parsejson is a Method that parses a JSON string and returns a JSON object.
Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. An attacker may pass a specially crafted JSON data, causing the server to hang.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a Regex string and cause the service to hang for a large periods of time.

text quoted from snyk vuln page : Link

It's also worth noting that anyone that uses snyk / nsp & socket.io-client has broken client builds

@d3viant0ne WOW , didn't expect that coming, Why's that?

If you run the nsp or snyk checks in a CI run as a part of your validations, you get a non zero exit code, thus broken as parsejson is a nested dependency of socket.io-client

Any plans to fix this?

Anyone have an update on this anyone? Need a fix soon since some packages we use are using this and is out of our control. Our company's security group is needing this fixed.
I am willing to help out as well and or fix this.

Is there a reason you can't just replace line 20 with data = data.trim()?

Is there a fix for this?

If you're coming in here from an audit log/warning: this package looks to be essentially unmaintained, and in any case your packages, and their dependencies, should be using JSON.parse(...) rather than this package.
You might need to hunt through your package-lock.json dependencies to find which dependency is relying on parsejson: in my case, I needed to upgrade browser-sync.

@cristianstaicu you seem the most familiar with this. Would you (or anyone else) be willing to submit a PR with a patch and or fork the repo with a patch if this repo isn't maintained?

In my case I did:
npm ls parsejson
Which outputted:
<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └─┬<EMAIL_ADDRESS>        └──<EMAIL_ADDRESS>
And fixed using:
npm install<EMAIL_ADDRESS>

This is a CVE with a HIGH rating, and is still open?

I am getting a HIGH rating on a project I started working on:
https://nvd.nist.gov/vuln/detail/CVE-2017-16113


Add some extra's to the requirements

Hope I can save some others some time with this, couldn't make in Fedora because of missing libsodium-devel.
Thanks for making this!

Cool man, good luck!

https://github.com/cathugger/mkp224o/commit/c0ef36f200ca1242094674aae11a7579574801b0 should be fine. I forgot what fedora/rhel used (yum? dnf?) so didn't include instructions for them but I guess it's easier to figure out what to do from debian instructions alone.


Slim Tutorial and Script broken due to Commit 8d1b23d999a563c56236a3d250e18ef825e4e66e

Hey TF Team,
Commit 8d1b23d999a563c56236a3d250e18ef825e4e66e broke the TF Slim Tutorial and TF Slim Script:
https://github.com/tensorflow/models/blob/master/slim/scripts/finetune_inception_v3_on_flowers.sh
Reverting this file to 4d241449aeb3707143c64e1be106cc6828a0d7b0 solves the issue https://github.com/tensorflow/tensorflow/commit/4d241449aeb3707143c64e1be106cc6828a0d7b0#diff-197163b98ebda1e22c3ff820582bf0d5
In the latest TF version as well as the TF rc10 the TF Slim Image Classification is not running.
Tested on Offical Tensorflow Docker GPU Image.
Best Wishes,
Patrick

@annarev, since this is your change, could you take a look

Closing due to lack of recent activity, please reopen if you have further. Please let us know if your issue is not resolved in the latest version. Thanks!

Sorry, I somehow missed this issue earlier. Patrick, let me know if you still see the issue.


Allow including sources besides local from the project directory

See original issue on GitLab
In GitLab by [Gitlab user @tlater] on May 4, 2018, 17:20
Occasionally, it can be useful to include a tarball from the project directory. You may want to, for example, add a handful of symlinks that will turn a flatpak runtime into a usable sysroot. Currently, the only way to do so is to specify the absolute directory to such a tarball in a tar source with the file:// url pattern.
This makes it impossible to share the resulting .bst file without an accompanying script that normalizes this path.
We have an example of this in the integration test suite here - the {project_dir} variable is expanded on-the-fly using python code.
This already partially possible with the local plugin - it's just not possible to do any processing on these sources, so users have to include a normal directory. This is often not sufficient. Git, for example, does not store permissions, which may cause a project to break when it is committed.
One way to solve this would be to add a %{project_dir} variable to buildstream that automatically resolves to the project directory. Users could then specify paths such as file://%{project_dir}/files/sysroot.tar.
The addition of SourceTransform would probably also solve this, but I believe that a slightly simpler solution would be more user friendly here. Why would I need to learn about "SourceTransform" elements if I just want to include a file from my repository?

In GitLab by [Gitlab user @tristanvb] on May 10, 2018, 09:28

You may want to, for example, add a handful of symlinks that will turn a flatpak runtime into a usable sysroot.

This is currently possible without doing anything weird like revisioning a tarball with your project, e.g. see this small example project

One way to solve this would be to add a %{project_dir} variable to buildstream that automatically resolves to the project directory. Users could then specify paths such as file://%{project_dir}/files/sysroot.tar

I would prefer we remain consistent and suggest project-dir, or even project-directory, rather than starting down the path of underscores
I find that this is not a usual use case, is there really an argument for encouraging revisioning of tarballs ?

If you are using git to revision your project, then sure, it is expected that:

You can revision symlinks perfectly well, there is no need for tarball hacks here
You don't have much to say about file permissions, best you can do is executable or not.

In the case that you want to import local files directly and want to have more enhanced permissions, why not write a script element to post process that ?
Conversely, would it not make sense for the import element to gain some features to specify target file permissions, possibly using globbing patterns to specify permissions on groups of files which were added ?
I think that adding features to the import element would be better than encouraging weird things like revisioning of tarballs with the project.

In GitLab by [Gitlab user @tlater] on Nov 29, 2019, 17:42
This has practically been superseded by #1047

In GitLab by [Gitlab user @tlater] on Nov 29, 2019, 17:42
closed


Move topics forward to the search page

Done. You can now access the topics page directly from the search page.


Consolidate the admin panel file in a single folder

Today, the admin panel code leaves between components/admin-panel and components/edit-collective (the legacy folder).  We should consolidate everything under components/admin-panel .

cc @gustavlrsn, for after the new dashboard public release


(chocolatey-core.extension) Remove-Process doesn't actually do anything

(chocolatey-core.extension) Trying to use Remove-Process in a script or directly in PowerShell results in nothing happening and no output, even with the Verbose parameter
Expected Behavior

Process is stopped, I think? If that's not what it's supposed to do, then the documentation is confusing.
Current Behavior

Nothing happening and no output, even with the Verbose parameter
Possible Solution

No idea.
Steps to Reproduce (for bugs)

Tried all of these with no results:
PS C:\WINDOWS\system32> Remove-Process -NameFilter MSIAfterburner* -WithChildren True -Verbose
PS C:\WINDOWS\system32> Remove-Process -NameFilter MSIAfterburner* -WithChildren True -Verbose True
PS C:\WINDOWS\system32> Remove-Process -NameFilter "MSIAfterburner*" -WithChildren True -Verbose True
PS C:\WINDOWS\system32> Remove-Process -NameFilter "MSIAfterburner.*" -WithChildren True -Verbose True
PS C:\WINDOWS\system32> Remove-Process -NameFilter 'MSIAfterburner.*' -WithChildren True -Verbose True

Context

Ultimately trying to update a package install script to kill off some processes prior to install, to avoid the need for a reboot.
Your Environment

Package Version used: 1.3.5
Operating System and version: Windows 10 1909
Chocolatey version: v0.10.15
Install/uninstall gist: N/A

Ended up implementing my own solution for now that seems to work fine. I'm new at PowerShell, so apologies if it's crude:
foreach($procstring in @("MSIAfterburner*","RTSS","RTSSHooksLoader*","EncoderServer*"))
{
  Write-Output "Checking whether process matching $procstring is running..."
  for($i = 1; $i -le 3; $i++)
  {
    if ($i -gt 1)
    {
      Write-Output " Try # $i : Waiting 5 seconds for process to terminate..."
      Start-Sleep -s 5
    }
    $procobj = Get-Process $procstring -ErrorAction SilentlyContinue
    if($procobj -eq $null)
    {
      Write-Output " Try # $i : SUCCESS - No process matching $procstring is running"
      break
    }
    $procid = ($procobj).id
    $procname = ($procobj).Name
    Write-Output " Try # $i : Attempting to stop active process $procname with ID $procid"
    Stop-Process -Id $procid
  }
}

I don't really know where you find the usage of -Verbose True. There is no such argument in the function (and it isn't automatically added since it don't use the CmdLet attribute.
To get the verbose output when you are calling it manually (not inside a chocolatey package) you will need to set the variable: $VerbosePreference="Continue".
However, it is never meant to be called manually outside of a chocolatey package, so you should add the logic to the package first then do choco install msiafterburner --verbose. (you may also find the log for such an install in the $env:ChocolateyInstall\logs\chocolatey.log. We will need that before we can start investigating what the problem could be. (Make sure to look through that file and remove/mask secrets you don't want exposed to the public though).

Process is stopped, I think? If that's not what it's supposed to do, then the documentation is confusing.

Indeed, it is meant to stop the process, and I know it works for at least 1 package (alldup).

Now I'm even more confused:
First, the documentation right here says that you should be able to test any of the functions from PowerShell, which conflicts with the idea they should only need to work in a Chocolatey script: https://github.com/chocolatey-community/chocolatey-coreteampackages/tree/master/extensions/chocolatey-core.extension
Second, I tried it in a Chocolatey script and it didn't do anything there either.
Third, the detailed help for Remove-Process clearly states that it's a cmdlet that supports "common parameters" - including Verbose:

It shows:
# RegEx expression of process name, returned by Get-Process function
[string] $NameFilter

So you can't use wildecard syntax such as MSIAfterburner*, but MSIAfterburner.*.

You can see in my original report that I tried both syntaxes. Also, the first style you mentioned absolutely works fine with both Get-Process and Stop-Process.

Your solution does not gracefully shut down applications, nor does it wait for them so its not really alternative.
If you can create example that I can replicate I could offer help, otherwise, this will be closed in few days.

@HunterZ I did some minor testing with the lines that you posted initially, and I see the problem.
You are treating switch parameters as pure bolean value, this do not work.
Switch parameters do not accept a value (well not in that way anyhow). Remove the True value from -Verbose and -WithChildren.
It will work then, but you will still not get any output due to the -Verbose switch do not work with this function.
Even though the powershell help page mentions that -Verbose is supported, it is not true (this is decided by powershell help page to output, not the function itself).

Now I'm even more confused:

First, the documentation right here says that you should be able to test any of the functions from PowerShell, which conflicts with the idea they should only need to work in a Chocolatey script: /extensions/chocolatey-core.extension@master

Sorry, that is my mistake. I mixed the functions in the core extension with something else.

You are treating switch parameters as pure bolean value, this do not work.

It actually works but requires special syntax: -SwitchParam:$boolValue

@majkinetor which is why I mentioned

well not in that way anyhow

Closing this due to missing feedback (no reproducible problem provided).


Add documentation for a common JSON transaction parameters object

An issue was noticed while working on https://github.com/hashgraph/hedera-sdk-cpp/issues/695 (with #205) that it isn't exactly clear when an additional signature should be applied to a transaction for some tests. The use of the signerKey field should be used to explicitly provide the keys that should sign a transaction.

In addition to allowing signerKeys to be a list and an explicit way to provide extra signatures to a transaction, the scope of this issue is being expanded to create and document a JSON object which will contain all common transaction parameters which can easily be added to our JSON-RPC APIs. This object should include transactionId, maxTransactionFee, etc. This will allow us to test these properties going forward and keeping them documented and consolidated.


What happened to CodeLlaMa-34B?

When I try to select this model in the extension, I get a 503 error. When I went to the repository, I couldn't find this model there. Where did it go?

Is this what you are looking for?

Closing, feel free to re-open if you're still facing issues..


Address already in Use: Unable to Bind

I run a command
sudo goaccess /var/log/apache2/access.log --log-format=COMBINED -a -o /var/www/html/report.html  --real-time-html

However, I am getting the following error over and over again. I tired restarting the apache server but still problem persists.
Fatal error has occurred
Error occured at: src/websocket.c - ws_socket - 2746
Unable to set bind: Address already in use.

You can try to find which process is using the port and kill it. e.g.,
lsof -i tcp:7890

Please also take a look at --addr and --port options if you need to use different settings.

Closing this. Feel free to reopen it if needed.

Thnks
On Feb 14, 2018 7:06 AM, "Gerardo O."<EMAIL_ADDRESS>wrote:
Closed #1007 https://github.com/allinurl/goaccess/issues/1007.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/allinurl/goaccess/issues/1007#event-1472909958, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AhZz7yephn0hQeyRRv655pWQMRw-_Yjxks5tUjiCgaJpZM4R-IPm
.


Font not rendering on Topcoat.io

See attached:

Possible related to https://github.com/topcoat/topcoat/issues/452 ?

Thanks @nnnnic - we're clearing it all out and will have to start from scratch in the next release.


add no servers running forks message

meh, idk, we just dont track them, they exist

good enough, thanks


Bug: Ionic build is broken after upgrading to 0.4.0

My configuration

"@capacitor/core": "2.4.2",
"@ionic/angular": "^5.4.1",
"@angular/core": "~11.1.1",
"eslint": "^7.6.0",
"typescript": "~4.1.3"

Current behavior:
Ionic build with ESLint is causing lining error while running iOS build
Expected behavior:
There should be no linting error in the library
Steps to reproduce:

Use ESLint
Run Ionic build and the error shows up the in console.

Related code:
Shown in the error image
Other information:
My configuration
"@capacitor/core": "2.4.2",
"@ionic/angular": "^5.4.1",
"@angular/core": "~11.1.1",
"eslint": "^7.6.0",
"typescript": "~4.1.3"
Capacitor doctor:
Not required as it is happening while doing Ionic build.

Thank you!
Unfortunately, I could not reproduce the issue. Possibly also because I do not know the rest of the dependencies.
Please provide a minimal, reproducible example (see here).

I will try to get a sample project with the error. thanks for the reply.

Hi, I have a similar issue :
Error: node_modules/@capacitor-community/firebase-crashlytics/node_modules/@capacitor/core/types/definitions-internal.d.ts:16:18 - error TS2430: Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'.
  Types of property 'Plugins' are incompatible.
    Type '{ [pluginName: string]: { [prop: string]: any; }; }' is missing the following properties from type 'PluginRegistry': FirebaseCrashlytic, SignInWithApple, GoogleAuth

16 export interface CapacitorInstance extends CapacitorGlobal {

I believe it is a retrocompatibility problem with Capacitor 3 : in fact, in https://github.com/capacitor-community/firebase-crashlytics/blob/v0.4.0/package.json , we can see the plugin have dependencies to "latest" capacitor version, and this latest version is capacitor 3, that is not fully compatible with the rest of this plugin.
could you, make 0.4.1 version with
"@capacitor/android": "^2.4.8",
"@capacitor/ios": "^2.4.8",

instead of "latest" ?
Thank you !

To reproduce :
git clone https://github.com/capacitor-community/firebase-crashlytics.git
cd firebase-crashlytics
git checkout v0.4.0
npm install #this will download the 'latest' capacitor, that is not compatible with v0.4.0
npm build => failed to compile

@cyril-colin Thank you very much. I have released the changes (npm).


TP2000-1241 Implement new homepage design

TP2000-1241 Implement new homepage design
Why
The current homepage is looking lacklustre and less in keeping with other services under the data portfolio.
What

Applies new header and footer across the application

Updates homepage layout and content to match the design

Uses custom CSS styling in places to conform to design
Removes now unused HomeForm
Replaces workbasket_action.jinja with homepage.jinja template
Displays relevant cards/links/header items according to user permissions

Introduces a new search capability to homepage

Adds a new search form, HomeSearchForm, using an alphanumeric validator and limiting input to 18 chars (longest possible search term for its purpose)
Redirects to the detail view of the tariff element if a match is found
Redirects to the search page if no match is found

Adds unit tests

TODO

Create a dedicated page for Tools to link to in the header providing more descriptive content of their use

Before

After

Codecov Report
Attention: Patch coverage is 92.12598% with 10 lines in your changes are missing coverage. Please review.

Project coverage is 93.10%. Comparing base (ac9b21e) to head (36f39be).
Report is 3 commits behind head on master.

Files
Patch %
Lines

common/views.py
85.91%
5 Missing and 5 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1173      +/-   ##
==========================================
- Coverage   93.11%   93.10%   -0.01%
==========================================
  Files         580      580
  Lines       43646    43705      +59
  Branches     3139     3151      +12
==========================================
+ Hits        40641    40692      +51
- Misses       2394     2396       +2
- Partials      611      617       +6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[BUG] createParam uses "crypto" in next module

The package at "../../../node_modules/next/dist/shared/lib/bloom-filter/base-filter.js" attempted to import the Node standard library module "crypto".
It failed because the native React runtime does not include the Node standard library.

it's works with version "solito": "3.0.0-alpha.1"


#0: Updated CODEOWNER for ttnn/operations/sliding_window

Problem description
Code owner for sliding_window was not set.

@mywoodstock Please confirm.

Please do not merge until @mywoodstock has taken a look


Pathfinding plugin for hexagons

We need a pathfinding plugin for the hexagon example game. This plugin will determine if a unit can reach point B from point A.
The pathfinding needs to take obstacles into account. So as an example a car can not drive over a mountain, but drives 2 times faster on road, than compared to a human. The FlaTWorld works with coordinates, not hexagon indexes, so you have to take that into account. We most likely have to create some utility functions, e.g. a function that calculates nearby hexagon coordinates.
Also using this pathfinding function we can create a unit movement, attack etc. highlighter. So something that shows the player where the selected unit can move to. This might be something that needs to be considered while making the plugin. The actual highlighter will have it's own issue and either this plugin will be extended to hold that functionality or it goes somewhere else.
An extra tip / note regarding this is that, as I understand Scirras engine: Contruct 2 uses webworkers for managing the pathfinding. I think that should be investigated and learned upon.
How about using:
https://github.com/qiao/PathFinding.js/
http://gamedev.stackexchange.com/questions/44812/finding-shortest-path-on-a-hexagonal-grid

In develop branch


are there any new nitro sniper download?

u got any latest nitro sniper download that work fast?

https://github.com/Vedzaa/NitroSniperGo


ISPN-5750 Upgrading to Hibernate Search 5.5.0.Final

Looking...

CI seems to be dead ATM. It will take a while to run this ...

Integrated in master. Thanks @gunnarmorling !

Thanks!


Support for arm architectures

Are there any specific reasons as to why only x86 architectures are listed as supported?
Would it be possible to add support for arm-based architectures in the future?
Cheers,
Ghis

@ghisvail I can remove the restriction but I haven't really tried in ARM.
Would you like me to do that?

I don't think so @ghisvail
I just published<EMAIL_ADDRESS>it's the first version without CPU restriction in package.json.
Would you be so kind to let me know if it works in ARM?

closing due inactivity.


create smartAPI record for idisk

Now that the new pending API for idisk is complete (https://github.com/biothings/pending.api/issues/22), creating an issue to track the creation of a smartAPI record and integration into BTE as a data source.

note that infores IDs are currently draft for this api and idisk as a knowledge source...

For this API, BTE is incorrectly adding the MEDDRA ID prefix to the sub-query from MEDDRA Disease ID -> SmallMolecule...
Log showing incorrect sub-query done:
the q should be just "10017947", not with the MEDDRA prefix...
    {
        "timestamp": "2021-08-23T04:43:31.523Z",
        "level": "DEBUG",
        "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/idisk/query\",\"params\":{\"fields\":\"name,umls\",\"size\":1000},\"data\":\"q=**MEDDRA:10017947**&scopes=has_adverse_effect_on.meddra\",\"method\":\"post\",\"timeout\":50000}",
        "code": null
    },

Setup:

convert this yaml to json and save to<EMAIL_ADDRESS>run a local instance of BTE and POST to the http://localhost:3000/test/query endpoint

Query:
{
    "message": {
        "query_graph": {
            "nodes": {
                "n0": {
                    "categories": ["biolink:Disease"],
                    "ids": ["MEDDRA:10017947"]
                },
                "n1": {
                    "categories": ["biolink:SmallMolecule"]
                }
            },
            "edges": {
                "e01": {
                    "subject": "n0",
                    "object": "n1"
                }
            }
        }
    }
}

Andrew and I discussed this today. We decided to register this API, and integrate it with BTE.
The bug mentioned above may be addressed by #249 and https://github.com/biothings/call-apis.js/issues/26. We can see if the bug continues to show up after and address it then...


chore(main): release 1.2.3

:robot: I have created a release beep boop
1.2.3 (2022-08-18)
Bug Fixes

Add homebrew and main file (0929c07)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cobraz/xlsx-mxlookup/releases/tag/v1.2.3 :sunflower:


spyder warning "IPython >=7.31.1;<8.0.0 : 8.2.0 (NOK)"

On 22.05, Spyder displays a dialog box at every startup:
You have missing dependencies!

# Mandatory:
IPython >=7.31.1;<8.0.0 : 8.2.0 (NOK)

Please install them to avoid this message.

Cc @drewrisinger

Updating spyder to the latest version with the patch below unfortunately does not solve this.
spyder-update.txt

According to https://github.com/spyder-ide/spyder/pull/17282
it seems we can simply do
    substituteInPlace spyder/dependencies.py \
      --replace 'IPYTHON_REQVER = ">=7.31.1;<8.0.0"' 'IPYTHON_REQVER = ">=7.31.1"'


peaclock: init at 0.4.3

Motivation for this change
I wanted to use this clock in my terminal. It's cute!
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)
[X] 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)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

I tried to get this to build on OS X (since the repository says MacOS is supported) using gcc8Stdenv, but it didn't link successfully:
{ stdenv, lib, fetchFromGitHub, cmake, pkgconfig, libpthreadstubs, icu }:

stdenv.mkDerivation rec {
  pname = "peaclock";
  version = "0.4.3";

  src = fetchFromGitHub {
    owner = "octobanana";
    repo = pname;
    rev = version;
    sha256 = "1582vgslhpgbvcd7ipgf1d1razrvgpq1f93q069yr2bbk6xn8i16";
  };

  nativeBuildInputs = [ cmake ];
  buildInputs = [ libpthreadstubs icu ];

  cmakeFlags = [ "-DCMAKEBUILD_TYPE=release" ] ++ lib.optional (stdenv.isDarwin)
    "-DCMAKE_CXX_COMPILER=${stdenv.cc}/bin/c++";

  enableParallelBuilding = true;

  meta = with stdenv.lib; {
    description = "A clock, timer, and stopwatch for the terminal.";
    homepage = "https://octobanana.com/software/peaclock";
    license = licenses.mit;
    platforms = [ "x86_64-darwin" "x86_64-linux" "i686-linux" ];
    maintainers = with maintainers; [ djanatyn ];
  };
}

+  peaclock = callPackage ../applications/misc/peaclock {
+    stdenv = if stdenv.isDarwin then gcc8Stdenv else stdenv;
+  };

Build output:
[ 16%] Building CXX object CMakeFiles/peaclock.dir/src/main.cc.o
[ 50%] Building CXX object CMakeFiles/peaclock.dir/src/ob/string.cc.o
[ 50%] Building CXX object CMakeFiles/peaclock.dir/src/peaclock/tui.cc.o
[ 66%] Building CXX object CMakeFiles/peaclock.dir/src/ob/readline.cc.o
[ 83%] Building CXX object CMakeFiles/peaclock.dir/src/peaclock/peaclock.cc.o
[100%] Linking CXX executable peaclock
ld: warning: option -s is obsolete and being ignored
ld: warning: passed two min versions (10.12.0, 10.12) for platform macOS. Using 10.12.
Undefined symbols for architecture x86_64:
  "std::filesystem::__cxx11::path::has_filename() const", referenced from:
      std::filesystem::__cxx11::path::operator/=(std::filesystem::__cxx11::path const&) in main.cc.o
  "std::filesystem::__cxx11::path::lexically_normal() const", referenced from:
      Tui::mkconfig(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool) in tui.cc.o
  "std::filesystem::__cxx11::path::has_root_directory() const", referenced from:
      std::filesystem::__cxx11::path::operator/=(std::filesystem::__cxx11::path const&) in main.cc.o
  "std::filesystem::__cxx11::path::compare(std::filesystem::__cxx11::path const&) const", referenced from:
      _main in main.cc.o
      Tui::load_config(std::filesystem::__cxx11::path const&) in tui.cc.o
  "std::filesystem::create_directory(std::filesystem::__cxx11::path const&)", referenced from:
      _main in main.cc.o
  "std::filesystem::status(std::filesystem::__cxx11::path const&)", referenced from:
      _main in main.cc.o
      Tui::mkconfig(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool) in tui.cc.o
      Tui::load_config(std::filesystem::__cxx11::path const&) in tui.cc.o
  "std::filesystem::__cxx11::path::_M_split_cmpts()", referenced from:
      std::filesystem::__cxx11::path::path<char [5], std::filesystem::__cxx11::path>(char const (&) [5], std::filesystem::__cxx11::path::format) [clone .isra.274] in main.cc.o
      std::filesystem::__cxx11::path::operator/=(std::filesystem::__cxx11::path const&) in main.cc.o
      std::filesystem::__cxx11::path OB::Parg::get<std::filesystem::__cxx11::path, 0>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) in
 main.cc.o
      _main in main.cc.o
      Tui::mkconfig(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool) in tui.cc.o
      Tui::load_config(std::filesystem::__cxx11::path const&) in tui.cc.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/peaclock.dir/build.make:163: peaclock] Error 1
make[1]: *** [CMakeFiles/Makefile2:95: CMakeFiles/peaclock.dir/all] Error 2
make: *** [Makefile:149: all] Error 2
builder for '/nix/store/g6wdj74dx7s5wjddz69v7z8782wdnjhy-peaclock-0.4.3.drv' failed with exit code 2
error: build of '/nix/store/g6wdj74dx7s5wjddz69v7z8782wdnjhy-peaclock-0.4.3.drv' failed

I was able to build successfully on pinephone, so I added aarch64-linux support.

I tried stdenvClang:
[ 16%] Building CXX object CMakeFiles/peaclock.dir/src/ob/string.cc.o
[ 33%] Building CXX object CMakeFiles/peaclock.dir/src/peaclock/tui.cc.o
[ 50%] Building CXX object CMakeFiles/peaclock.dir/src/main.cc.o
[ 66%] Building CXX object CMakeFiles/peaclock.dir/src/ob/readline.cc.o
[ 83%] Building CXX object CMakeFiles/peaclock.dir/src/peaclock/peaclock.cc.o
[100%] Linking CXX executable peaclock
ld: warning: option -s is obsolete and being ignored
ld: warning: passed two min versions (10.12.0, 10.12) for platform macOS. Using 10.12.
ld: warning: ignoring file CMakeFiles/peaclock.dir/src/main.cc.o, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0xDE 0x
C0 0x17 0x0B 0x00 0x00 0x00 0x00 0x14 0x00 0x00 0x00 0xF4 0x65 0x08 0x00 )
ld: warning: ignoring file CMakeFiles/peaclock.dir/src/ob/string.cc.o, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x
DE 0xC0 0x17 0x0B 0x00 0x00 0x00 0x00 0x14 0x00 0x00 0x00 0xD8 0xB6 0x01 0x00 )
ld: warning: ignoring file CMakeFiles/peaclock.dir/src/peaclock/tui.cc.o, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format (
 0xDE 0xC0 0x17 0x0B 0x00 0x00 0x00 0x00 0x14 0x00 0x00 0x00 0x54 0x35 0x0E 0x00 )
ld: warning: ignoring file CMakeFiles/peaclock.dir/src/ob/readline.cc.o, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format (
0xDE 0xC0 0x17 0x0B 0x00 0x00 0x00 0x00 0x14 0x00 0x00 0x00 0x80 0xB5 0x05 0x00 )
ld: warning: ignoring file CMakeFiles/peaclock.dir/src/peaclock/peaclock.cc.o, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file for
mat ( 0xDE 0xC0 0x17 0x0B 0x00 0x00 0x00 0x00 0x14 0x00 0x00 0x00 0x48 0x44 0x06 0x00 )
Undefined symbols for architecture x86_64:
  "_main", referenced from:
     implicit entry/start for main executable
ld: symbol(s) not found for architecture x86_64
clang-7: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [CMakeFiles/peaclock.dir/build.make:163: peaclock] Error 1
make[1]: *** [CMakeFiles/Makefile2:95: CMakeFiles/peaclock.dir/all] Error 2
make: *** [Makefile:149: all] Error 2
builder for '/nix/store/hkmlb9b88vm01mlvh86dl5f18g0x4zci-peaclock-0.4.3.drv' failed with exit code 2
error: build of '/nix/store/hkmlb9b88vm01mlvh86dl5f18g0x4zci-peaclock-0.4.3.drv' failed

No worries - your changes worked and I got peaclock running on my macbook 🎉 Thank you @r-burns!
I was looking at makeWrapper for setting LC_ALL=C on certain platforms. However, I think it might be best to leave that to be fixed in upstream given that it affects all musl distributions?
If so, I think this is working on all platforms based on my testing.

Now squash the 5 commits to 2 only (the one for the new package maintainer and the other for the package itself).

Also, squash the commits.

Commits squashed, review comments resolved. Thanks for walking me through this, it's so exciting contributing to something I use everyday.

LGTM, LGTBorg.


Naupaka's overall comments, proofreading, revisions

It looks like I changed a ton, but I really didn't change all that much (although there are revisions and tweaks throughout). I just consistently wrapped the lines, which should make diffing much easier in the future. I also regenerated the pdf.

@naupaka, sorry to dredge this up, but quick question/observation about the line wrapping (and apologies If I am pointing out something obvious)
I have always hated the default diff with md as I don't wrap my lines when I write, so a paragraph is just one big line to git.  Is this what you were trying to enforce with the line wrapping so that we could see line by line changes?  If so, that's great but then makes editing a pain because you have to fix line wraps whenever you make a change to the document.
Well this (the diff rendering, not your PR!) was bothering me today and I found the "Rich Diffs", which appear to have been around for a couple of years.  When viewing the diff, the document icon at the top right switches to rich diff and then the changes you want to see appear!
Again, apologies if I am pointing out the obvious...

@jhollist yeah - I know it's a pain... I was trying to make it easier with the default diffs. I didn't know about the rich diffs! That's pretty slick. I guess I had imagined it wouldn't be too much hassle since most people (?) would be writing in vim, so could use vapgqto re-wrap, or emacs, with M-q or CMD-OPT-q in Sublime.  But, perhaps all are still extra effort, and the rich diff it indeed exactly what I was trying to get closer to anyway.


mocha devDependency adds content to node_modules after npm install --production

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[x] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description
Sometime between Wednesday September 30th 2020 and Thursday October 1st 2020, the behavior of mocha during a clean npm install --production changed. Previously, the command resulted in no node_modules folder being created. Since, the command has consitently resulted in the creation of a node_modules folder with the following contents:

define-properties
es-abstract
es-to-primitive
function-bind
has
has-symbols
is-callable
is-date-object
is-regex
is-symbol
object-inspect
object-keys
string.prototype.trimend
string.prototype.trimstart

Steps to Reproduce

git clone https://github.com/danludwig/npm-module-bug-reports.git
cd npm-module-bug-reports/mocha-2020-10-bug
Observe that the ./package.json has only a devDependency on mocha
npm install --production
Observe that a node_modules folder was created with the above listed contents.

Expected behavior: [What you expect to happen]
Assuming the commands to reproduce above were followed, continue with:

cd ../mocha-2020-10-expected
Observe that the ./package.json has only a devDependency on chai
npm install --production
Observe that no node_modules folder was created.

Actual behavior: [What actually happens]

Reproduces how often: [What percentage of the time does it reproduce?]
100% since October 1st 2020. 0% on and before September 30, 2020
Versions

The output of mocha --version and node node_modules/.bin/mocha --version: 8.1.3
The output of node --version: v12.13.0
Your operating system

name and version: Windows 10, MacOS Catalina 10.15.6, Ubuntu 18.04
architecture (32 or 64-bit): 64-bit

Your shell (e.g., bash, zsh, PowerShell, cmd): bash, gitbash, powershell
Your browser and version (if running browser tests): n/a
Any third-party Mocha-related modules (and their versions): n/a
Any code transpiler (e.g., TypeScript, CoffeeScript, Babel) being used (and its version): n/a

Additional Information
This is an important issue as AWS Lambda@Edge code packages have a size limitation of 1048576 bytes, and the automated build tooling provided by AWS SAM will include these node_modules contents, violating the service limit. The only workaround is to add a cleanup step in the build process to delete the node_modules folder after building but before publishing the package for use in Lambda@Edge.

in your test repo, your expected dir has chai in package.json and the bug dir has mocha in package.json
I don't understand this

@boneskull the purpose of that is simply to demonstrate that a dev dependency should not contribute anything to the contents of a node_modules folder when npm install --production is used. I was unable to demonstrate that with the mocha dev dependency. I could have picked something else besides mocha and chai. But if one project contained both mocha and chai as dev dependencies, it would be harder to demonstrate that the node_modules folder contents came from mocha and not other dev dependencies.

OK.  Well, I can certainly reproduce it.  but what I can't do is tell you why it's happening.   this looks like an npm bug to me.  try
$ yarn install --production

and find that node_modules is empty.
it seems to have something to do with the lack of dev: true in the generated package-lock.json.  but even blasting package-lock.json and retrying w/o a lockfile has the same result.

see https://github.com/npm/cli/issues/1113

I'm going to close this as I don't think it's a Mocha bug.  I'm not sure what else to do... I wonder if downgrading npm would help.

@boneskull we've already seen the bug 1113 report at the npm issued board. That bug was reported way back in April, and doesn't explain why we started seeing this behavior in mocha starting on October 1st. I have build artifacts showing that the behavior did not manifest at all up to and including September 30th. Could it be that one of the mocha dependencies, such as eslint, received a version bump where a shrinkwrap was introduced? If that's the case, could this be an issue that could be corrected in mocha by falling back to a lower dependency version?

It's an npm bug for sure, but we can work around it.  Mocha requires promise.allsettled in its production deps, which depends on es-abstract.  es-abstract seems to be the "problem" repo.  If we replace promise.allsettled with a different ponyfill, it avoids installing es-abstract and addresses the issue.

This is great news, thank you. Will keep an eye on #4476


Wrong parameters in python invoke examples

Describe the issue
Example python invoke example is using the wrong variable name, name instead of binding_name:
resp = d.invoke_binding(name='kafkaBinding', operation='create', data='{"message":"Hello World"}')

https://docs.dapr.io/developing-applications/sdks/python/python-client/#interact-with-output-bindings
Expected content
resp = d.invoke_binding(binding_name='kafkaBinding', operation='create', data='{"message":"Hello World"}')

@berndverst - Can you take a look at this?

@msfussell @greenie-msft this was merged 10 days ago -- can you update the git submodule for Python and redeploy the docs?


windows eh-frame-header option

trying bundle gem --ext=rust hello_rust example on windows after ridk enable to get environment
bundle exec rake compile gives me the following error
= note: c:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: unrecognized option '--eh-frame-hdr'
c:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: use the --help option for usage information
collect2.exe: error: ld returned 1 exit status
Googling this error and arriving at https://github.com/avr-rust/blink/issues/23
For anyone else encountering this: The solution is to add "eh-frame-header": false to the target-json file.

Thanks for the report. Which ruby version are you using?

F:\windows\scoop\apps\alacritty\current>gem env
RubyGems Environment:

RUBYGEMS VERSION: 3.4.6
RUBY VERSION: 3.2.0 (2022-12-25 patchlevel 0) [x64-mingw-ucrt]
INSTALLATION DIRECTORY:
f:/windows/tools/ruby/Ruby3.2/lib/ruby/gems/3.2.0
USER INSTALLATION DIRECTORY: f:\windows_home.local\share/gem/ruby/3.2.0
RUBY EXECUTABLE: f:/windows/tools/ruby/Ruby3.2/bin/ruby.exe
GIT EXECUTABLE: F:\windows\scoop\shims/git.EXE
EXECUTABLE DIRECTORY: f:/windows/tools/ruby/Ruby3.2/bin
SPEC CACHE DIRECTORY: f:\windows_home.local\share/gem/specs
SYSTEM CONFIGURATION DIRECTORY: C:/ProgramData
RUBYGEMS PLATFORMS:

ruby
x64-mingw-ucrt

GEM PATHS:

f:/windows/tools/ruby/Ruby3.2/lib/ruby/gems/3.2.0
f:\windows_home.local\share/gem/ruby/3.2.0

GEM CONFIGURATION:

:update_sources => true
:verbose => true
:backtrace => true
:bulk_threshold => 1000
:sources => ["https://rubygems.org/"]
:concurrent_downloads => 8
"gem" => "--document=yri"

REMOTE SOURCES:

https://rubygems.org/

On Tue, Jan 31, 2023 at 5:10 PM Ian Ker-Seymer @.***>
wrote:

Thanks for the report. Which ruby version are you using?
—
Reply to this email directly, view it on GitHub
https://github.com/oxidize-rb/rb-sys/issues/139#issuecomment-1411247616,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABQRLTXNYEX6WYA2RBKLDWVGSWHANCNFSM6AAAAAAUM4AAVU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Any other info you need on this?

Last couple of things:

Can you post the full error output of rake compile?
Also, the output of ruby -rrbconfig -e 'pp RbConfig::CONFIG'?

Also, question for @MSP-Greg, is x64-mingw-ucrt a valid platform for Ruby 3.2? I know it is for 3.1, but does the added support for mswin / msvc make this obsolete?

x64-mingw-ucrt a valid platform for Ruby 3.2?

Yes, it's the only platform that's widely available.

does the added support for mswin / msvc make this obsolete?

At present, no.  It probably won't be replaced by mswin in the immediate future, as there are at least a few popular extension gems that won't compile on mswin.

bundle exec rake compile 2>&1
pp RbConfig::CONFIG
This is after I ran 'ridk enable`

I’m not sure how to fix this issue. Are you still having it?


Adding turtlebot_2dnav to documentation index for hydro

I'd like turtlebot_2dnav to be indexed and documented on ros.or

you need a proper release repo. Please follow the instructions at http://wiki.ros.org/bloom/Tutorials/FirstTimeRelease


Start Conway Imp tests with an initial committee and constitution

Description
This PR is setting an initial committee and constitution for Conway (emulating the ones that  will be defined in genesis).
For this, it was necessary to slightly modify the initialization of the NewEpochState in the Imp framework, to allow initialization actions before returning the state.
Tests were adjusted to only elect a committee if this action is actually meaningful to the test (relying on the initial committee otherwise).
Going through many tests was an opportunity to make some small  improvements:

an attempt to be more disciplined with setting pparams. I have consolidated a few of them
updating some functions to reduce the noise of converting between KeyHash and Credential
removing the duplicated inclusion of a test

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[ ] Self-reviewed the diff

Removed global bindings for committee, and generated them with freshKeyPair instead
Set voting thresholds when initializing and adjusted the tests accordingly
Added initial constitution

If you want to have another look @lehins when you can, thanks!


Move xwrf-data to xarray-contrib

Following up on https://github.com/xarray-contrib/xarray-contrib/issues/6, I forgot to mention that there is an accompanying data repository for xWRF: https://github.com/ncar-xdev/xwrf-data. Would there be any issues with moving this one over as well? Or would some other means for managing the package's data be preferred now under xarray-contrib?

👍🏽 for transferring the data repository

Done!


requirement, test: Remove preresolved dependency optimization

Closes #539

I'm still looking for some large requirements files to test performance with.

I didn't manage to find any ridiculously large requirements files. But I tested across a few and found that there isn't a meaningful performance impact vs just a regular pip install invocation.

Glad to hear it! Yeah, I think we're fine to move ahead here -- feel free to do another patch release to get this out 🙂


Add reallocation capability to bfc_allocator.

This commit mitigates external fragmentation in bfc_allocator by reallocation.
That is, although the sum of regions and unallocated bytes is larger than the
requested bytes but the bfc_allocator still fails to allocate a large enough
contiguous region to fulfill the request due to fragmentation. To avoid this
case, a relocation feature is implemented to deallocate free regions so that
a larger region can be formed.
Note that essentially we are able to play this trick because the underlying GPU
driver will be able to manipulate the vtable to return a region with a contiguous
virtual address space.

Revised based on the received review comments. Please help to take a look again when you have a moment. Thanks.

@tayo do you want to give the final LGTM?

I think it would be wise to add a guard flag so that if this causes problems it can be disabled?  (Unless that's already there and I'm missing it.)

If I'm reading the code correctly, this only helps when allow-growth is on, is that right?  Because we can only free units malloc'ed by individual cudaMalloc calls (these are called "regions" in the code?).  But when allow-growth is off, we malloc one big region, so the only case when we're able to free it is when it's empty, but then there's no need to free it.

If I'm reading the code correctly, this only helps when allow-growth is on, is that right? Because we can only free units malloc'ed by individual cudaMalloc calls (these are called "regions" in the code?). But when allow-growth is off, we malloc one big region, so the only case when we're able to free it is when it's empty, but then there's no need to free it.

That is a correct read. This commit only helps the mode with allow_growth=true, as in the allow_growth=false model the entire memory is just one region (yes, this is a malloc'ed allocation) in the current implementation.
Some data points: I hit this memory segmentation issue with a resent50 model from Joy of Cooking and it has allow_growh=true by default in its implementation. Without the PR, we can only bring up the fp32 model up to batch_size=96 w/ XLA, while vanilla TF can run with batch_size=128. With this PR, XLA can run up to batch_size=160. Somehow surprisingly, even if I set allow_growth=false, XLA cannot bring up the model with batch_size=128.
One more thing I'd like to point out for discussions is that it is possible for this PR to help with the allow_growth=false case, as long as we pre-allocate the entire memory with a set of regions with sizes, e.g., 100MB+200MB+400MB+...+4GB+8GB (instead of one giant region). I did not make the corresponding change because it is not (yet) clear to me if it will hurt some cases.

I think it would be wise to add a guard flag so that if this causes problems it can be disabled? (Unless that's already there and I'm missing it.)

I don't mind and can help to add a guard flag (by introducing an env variable to turn it off?). However, logically, the new feature is only triggered when OOM happens in the original implementation. So, turning off the feature can only hit an OOM when there is an issue executing the new reallocation feature.
That's been said, it may still be possible that having a guard flag can help with debugging? Let me know what you think.

I hit this memory fragmentation issue with a resent50 model from Joy of Cooking and it has allow_growh=true by default in its implementation.

Perhaps this explains some or all of the difference between what you were seeing (lots of OOMs) and what I was seeing (few OOMs) when we last talked about this in our meeting.  allow_growth=true is not the default setting in TensorFlow overall.

However, logically, the new feature is only triggered when OOM happens in the original implementation. So, turning off the feature can only hit an OOM when there is an issue executing the new reallocation feature.

I think some users may prefer to know that they're OOMing instead of hitting potentially pathological slowdowns in their code.  A guard flag would also aid in debugging if we suspect this change could be causing an unexpected problem.  In general guard flags are cheap and can have large benefits.

... Somehow surprisingly, even if I set allow_growth=false, XLA cannot bring up the model with batch_size=128.

Perhaps this explains some or all of the difference between what you were seeing (lots of OOMs) and what I was seeing (few OOMs) when we last talked about this in our meeting. allow_growth=true is not the default setting in TensorFlow overall.

Note that I meant (as quoted above) that in my observed case, setting allow_growth=false does not help. Only allow_growth=true with this PR can bring up the ResNet50 with batch_size not smaller than vanilla TF can do.

I think some users may prefer to know that they're OOMing instead of hitting potentially pathological slowdowns in their code. A guard flag would also aid in debugging if we suspect this change could be causing an unexpected problem. In general guard flags are cheap and can have large benefits.

Will add a guard flag. (Hard to say what users want.)

Note that I meant (as quoted above) that in my observed case, setting allow_growth=false does not help.

Maybe I misunderstand, but I thought you wrote above that with allow_growth=False XLA gets batch 128.  With allow_growth=True and without this PR, XLA gets batch 96.
I don't mean to parse words, but that would suggest to me that allow_growth=False does help, just not as much as you might want?
I agree it is odd that you are able to match TF's batch 160 with allow_growth=True + this PR but not with allow_growth=False.  I don't have an explanation for that, but I think it might be worth trying to understand.

@tayo do you want to give the final LGTM?

Will do after guard flag commit, requested by jlebar

When allow_growth=false, the allocator's constructor begins by claiming the entirety of memory.  When allow_growth=true, the allocator starts by claiming 1MB.
Perhaps starting with one large chunk that is split as needed will more quickly lead to the large-block external fragmentation issue that Trent has observed.  Almost like initializing the state of free memory with a different 'seed'.

Just pushed a new commit adding the guard flag. Please help to take a look. @tayo
I double checked and here are some notes and clarifications:

I was not precise. Both allow_growh=false and allow_growh=true with this PR can do batch_size=160 for my Joy-of-Cooking Resnet50.

So, @jlebar you are right that this explains partial difference between our observations about OOM.

We do have another XLA OOM bug (Joy-of-Cooking GNMT) with allow_growth=false due to internal memory fragmentation.

3. We do have another XLA OOM bug (Joy-of-Cooking GNMT) with allow_growth=false due to internal memory fragmentation.

FYI, there is a max internal fragmentation parameter you could play with, in case you were not aware.
https://github.com/tensorflow/tensorflow/blob/83f4a0c638988a040824081d0224964e1684214a/tensorflow/core/common_runtime/bfc_allocator.cc#L445

I was not precise. Both allow_growh=false and allow_growh=true with this
PR can do batch_size=160 for my Joy-of-Cooking Resnet50.

That is surprising, since we said that this change should have no effect
with allow_growth=false, right?  Do we understand this?
On Fri, Jul 19, 2019, 12:46 PM Tayo Oguntebi<EMAIL_ADDRESS>wrote:

We do have another XLA OOM bug (Joy-of-Cooking GNMT) with
allow_growth=false due to internal memory fragmentation.

FYI, there is a max internal fragmentation parameter you could play with,
in case you were not aware.
https://github.com/tensorflow/tensorflow/blob/83f4a0c638988a040824081d0224964e1684214a/tensorflow/core/common_runtime/bfc_allocator.cc#L445
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/30827?email_source=notifications&email_token=AABEZB62CJAEHVEDWMHIXPDQAIKZTA5CNFSM4IEVUDSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2MSKAI#issuecomment-513352961,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABEZB5YNFRXH22KNWMXS2DQAIKZTANCNFSM4IEVUDSA
.

we said that this change should have no effect with allow_growth=false

I did not agree with this.  This change will have an effect with allow_growth=false.  The value of allow_growth would simply determine the starting state of the free chunk list.  This change takes effect when the OOM is about to occur, by doing the collection pass.

Tayo, Trent agreed with it earlier:
https://github.com/tensorflow/tensorflow/pull/30827#issuecomment-513100384
It's surprising to me that he's now saying that this does have an effect
with allow_growth=false, because I don't see how that can matter.  There is
only one allocation to play with (?), so you can't free and coalesce allocs
like this PR tries to.
On Fri, Jul 19, 2019, 1:11 PM Tayo Oguntebi<EMAIL_ADDRESS>wrote:

we said that this change should have no effect with allow_growth=false
I did not agree with this. This change will have an effect with
allow_growth=false. The value of allow_growth would simply determine the
starting state of the free chunk list. This change takes effect when the
OOM is about to occur, by doing the collection pass.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/30827?email_source=notifications&email_token=AABEZBYV44WMA3P2W7FABODQAINVNA5CNFSM4IEVUDSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2MUCXA#issuecomment-513360220,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABEZB34PB2KJ6KX7B36STTQAINVNANCNFSM4IEVUDSA
.

@jlebar Some natural language ambiguous. Please read the following rephrased sentence again.
Both allow_growh=false without the PR and allow_growh=true with this PR can do batch_size=160 for my Joy-of-Cooking Resnet50.

We do have another XLA OOM bug (Joy-of-Cooking GNMT) with allow_growth=false due to internal memory fragmentation.

FYI, there is a max internal fragmentation parameter you could play with, in case you were not aware.
https://github.com/tensorflow/tensorflow/blob/83f4a0c638988a040824081d0224964e1684214a/tensorflow/core/common_runtime/bfc_allocator.cc#L445

Will play with the parameter later. Thanks for the info.

@jlebar -- Good point
@trentlo -- Can you confirm that with this PR, your runs converge / work as expected?

@trentlo -- Can you confirm that with this PR, your runs converge / work as expected?

Yes, they work as expected. It is some natural language ambiguity as I replied here.
BTW, I just pushed a commit fixing a compilation error observed in the (previous) CI runs. Some compilers do not allow passing const_iterator to std::vector::erase(). It will be good if you can take a look.

Sorry, I am still having difficulty assimilating everything that was said here into a consistent picture of the world.

Note that I meant (as quoted above) that in my observed case, setting allow_growth=false does not help. Only allow_growth=true with this PR brings up the ResNet50 with batch_size not smaller than vanilla TF can do.

This seems unambiguous to me.  But now I'm hearing something which seems to contradict this:

Both allow_growh=false without the PR and allow_growh=true with this PR can do batch_size=160 for my Joy-of-Cooking Resnet50.

I would assume that the first was simply an error, but I am hearing that this is all due to natural language ambiguity, so I am not sure, maybe I'm misunderstanding something here?
Perhaps in the name of clarity we could make the table specifying the max batch size for all combinations of the following booleans?

TF classic vs XLA
allow_growth = true vs false
without this PR vs with this PR

Sorry, I am still having difficulty assimilating everything that was said here into a consistent picture of the world.

No problem. Let's see if we can make things clearer.

Note that I meant (as quoted above) that in my observed case, setting allow_growth=false does not help. Only allow_growth=true with this PR brings up the ResNet50 with batch_size not smaller than vanilla TF can do.

I realized this above statement was wrong after I double checked the experiments. Setting allow_growth=false XLA can do batch_size=160 (PR is irrelevant in this case). Sorry for the confusion.

Both allow_growh=false without the PR and allow_growh=true with this PR can do batch_size=160 for my Joy-of-Cooking Resnet50.

Perhaps in the name of clarity we could make the table specifying the max batch size for all combinations of the following booleans?
* TF classic vs XLA

* allow_growth = true vs false

* without this PR vs with this PR

In the Joy-of-Cooking Resnet50 case,
TF classic: batch_size=160 (PR irrelevant in this case; allow_growth irrelevant too.)
XLA allow_growth=false: batch_size=160 (PR irrelevant in this case)
XLA allow_growth=true without this PR: batch_size=96
XLA allow_growth=true with this PR: batch_size=160
Let me know if this clarifies the discussions.

Let me know if this clarifies the discussions

Yes, thanks a lot!

Thanks for the reviews everyone, I think you got this under control :) Removing myself as a reviewer.


Memory Leak of Client Level

There are 2 cases that are leaking the level (one is an entity and the other is the level itself)
Here is an entity that is still kept alive, maybe nullify after render just like animatable = null on #renderToBuffer
https://github.com/bernie-g/geckolib/blob/8f383deb479cf375d6f01c294361539f446c4a0a/common/src/main/java/software/bernie/geckolib/renderer/GeoArmorRenderer.java#L405
Also, here:
https://github.com/bernie-g/geckolib/blob/8f383deb479cf375d6f01c294361539f446c4a0a/common/src/main/java/software/bernie/geckolib/loading/math/MolangQueries.java#L118
This actor needs to be cleared up on level unload.

1.20.1 down
https://github.com/bernie-g/geckolib/commit/edd9f02c3fd5923d312e85cc1df2ea385698c42c
1.21.1 soon

Done in 1.21.1 as of 4.6.3


macOS: split linting & testing

What does this PR do?
This PR adds a new job that's solely responsible for macos code linting

Motivation
This will hopefully improve our macOS jobs duration by running them in parallel.  https://datadoghq.atlassian.net/browse/APL-2393

Additional Notes
This is based on top of #20856 and the commits from this PR are also included here until the freeze is lifted

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


VS Code becomes unresponsive on startup

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1.59.0
OS Version:  Windows 10 (64-bit), 1909 (OS Build 18363.1679)

Steps to Reproduce:

Attempt to start VS Code

Error Messages:
When running via code --verbose this error is seen in the logs:
[main 2021-08-09T16:14:11.757Z] CodeWindow: detected unresponsive

I also am experiencing this issue after upgrading. Windows 20H2 (OS Build 19042 1083).  Log messages:
C:\Program Files\Microsoft VS Code\bin>code --verbose --log debug --disable-gpu
[main 2021-08-09T16:43:23.650Z] Starting VS Code
[main 2021-08-09T16:43:23.652Z] from: c:\Program Files\Microsoft VS Code\resources\app
[main 2021-08-09T16:43:23.652Z] args: {
_: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
log: 'debug',
status: false,
'prof-startup': false,
'no-cached-data': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': true,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'skip-welcome': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-keytar': false,
'disable-workspace-trust': false,
'disable-crash-reporter': false,
'crash-reporter-id': 'a63e70fc-34d9-4bd3-b7e2-cd788993eafd',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
'no-sandbox': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: 'C:\Users\jshuler\AppData\Roaming\Code\logs\20210809T114323'
}
[main 2021-08-09T16:43:23.654Z] Resolving machine identifier...
[main 2021-08-09T16:43:23.655Z] Resolved machine identifier: fdac09dcbfdfcda0218b57ed64ef646ebce18a10ecf69621cf605822bb691bcb
[main 2021-08-09T16:43:23.655Z] Main->SharedProcess#connect
[main 2021-08-09T16:43:23.679Z] StorageMainService: creating global storage
[main 2021-08-09T16:43:23.679Z] lifecycle (main): phase changed (value: 2)
[main 2021-08-09T16:43:23.680Z] windowsManager#open
[main 2021-08-09T16:43:23.680Z] windowsManager#open pathsToOpen [
{
backupPath: 'C:\Users\jshuler\AppData\Roaming\Code\Backups\1628522663144',
remoteAuthority: undefined
}
]
[main 2021-08-09T16:43:23.682Z] IPC Object URL: Registered new channel vscode:a5c2ba33-5df2-4393-98d7-e1211034fa05.
[main 2021-08-09T16:43:23.682Z] window#validateWindowState: validating window state on 3 display(s) { mode: 0, x: 183, y: 80, width: 1688, height: 887 }
[main 2021-08-09T16:43:23.682Z] window#validateWindowState: multi-monitor working area { x: 0, y: 0, width: 1920, height: 1040 }
[main 2021-08-09T16:43:23.683Z] window#ctor: using window state { mode: 0, x: 183, y: 80, width: 1688, height: 887 }
[main 2021-08-09T16:43:23.683Z] window: using vscode-file:// protocol and V8 cache options: bypassHeatCheck
[main 2021-08-09T16:43:23.744Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-08-09T16:43:23.744Z] lifecycle (main): phase changed (value: 3)
[main 2021-08-09T16:43:23.754Z] update#setState idle
[main 2021-08-09T16:43:23.754Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-09T16:43:23.852Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:43:23.855Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:43:23.978Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:43:23.980Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:43:24.191Z] [File Watcher (node.js)] >> normalized [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:43:24.235Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-09T16:43:38.898Z] CodeWindow: detected unresponsive
[main 2021-08-09T16:43:53.767Z] update#checkForUpdates, state =  idle
[main 2021-08-09T16:43:53.767Z] update#setState checking for updates
[main 2021-08-09T16:43:53.768Z] RequestService#request https://update.code.visualstudio.com/api/update/win32-x64/stable/379476f0e13988d90fab105c5c19e7abc8b1dea8
[main 2021-08-09T16:43:53.768Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-09T16:44:03.465Z] update#setState idle
^CTerminate batch job (Y/N)? y
C:\Program Files\Microsoft VS Code\bin>code --verbose --log debug --disable-extensions --disable-gpu
[main 2021-08-09T16:45:42.591Z] Sending some foreground love to the running instance: 1956
[main 2021-08-09T16:45:42.601Z] Sending env to running instance...
[main 2021-08-09T16:45:42.664Z] Sent env to running instance. Terminating...
[main 2021-08-09T16:45:42.664Z] Lifecycle#kill()
C:\Program Files\Microsoft VS Code\bin>code --verbose --log debug --disable-extensions --disable-gpu
[main 2021-08-09T16:45:57.424Z] Starting VS Code
[main 2021-08-09T16:45:57.426Z] from: c:\Program Files\Microsoft VS Code\resources\app
[main 2021-08-09T16:45:57.426Z] args: {
_: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
log: 'debug',
status: false,
'prof-startup': false,
'no-cached-data': false,
'prof-v8-extensions': false,
'disable-extensions': true,
'disable-gpu': true,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'skip-welcome': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-keytar': false,
'disable-workspace-trust': false,
'disable-crash-reporter': false,
'crash-reporter-id': 'a63e70fc-34d9-4bd3-b7e2-cd788993eafd',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
'no-sandbox': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: 'C:\Users\jshuler\AppData\Roaming\Code\logs\20210809T114557'
}
[main 2021-08-09T16:45:57.428Z] Resolving machine identifier...
[main 2021-08-09T16:45:57.428Z] Resolved machine identifier: fdac09dcbfdfcda0218b57ed64ef646ebce18a10ecf69621cf605822bb691bcb
[main 2021-08-09T16:45:57.429Z] Main->SharedProcess#connect
[main 2021-08-09T16:45:57.485Z] StorageMainService: creating global storage
[main 2021-08-09T16:45:57.485Z] lifecycle (main): phase changed (value: 2)
[main 2021-08-09T16:45:57.486Z] windowsManager#open
[main 2021-08-09T16:45:57.487Z] windowsManager#open pathsToOpen [
{
backupPath: 'C:\Users\jshuler\AppData\Roaming\Code\Backups\1628522663144',
remoteAuthority: undefined
}
]
[main 2021-08-09T16:45:57.489Z] IPC Object URL: Registered new channel vscode:9904a38f-2afe-45c0-ae96-c2c0b738cab4.
[main 2021-08-09T16:45:57.489Z] window#validateWindowState: validating window state on 3 display(s) { mode: 0, x: 183, y: 80, width: 1688, height: 887 }
[main 2021-08-09T16:45:57.489Z] window#validateWindowState: multi-monitor working area { x: 0, y: 0, width: 1920, height: 1040 }
[main 2021-08-09T16:45:57.490Z] window#ctor: using window state { mode: 0, x: 183, y: 80, width: 1688, height: 887 }
[main 2021-08-09T16:45:57.490Z] window: using vscode-file:// protocol and V8 cache options: bypassHeatCheck
[main 2021-08-09T16:45:57.562Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-08-09T16:45:57.562Z] lifecycle (main): phase changed (value: 3)
[main 2021-08-09T16:45:57.571Z] update#setState idle
[main 2021-08-09T16:45:57.571Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-09T16:45:57.671Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:45:57.673Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:45:57.784Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:45:57.787Z] [File Watcher (node.js)] [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:45:57.978Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-09T16:45:57.995Z] [File Watcher (node.js)] >> normalized [CHANGED] c:\Users\jshuler\AppData\Roaming\Code\User\globalStorage
[main 2021-08-09T16:46:12.734Z] CodeWindow: detected unresponsive
[main 2021-08-09T16:46:27.577Z] update#checkForUpdates, state =  idle
[main 2021-08-09T16:46:27.577Z] update#setState checking for updates
[main 2021-08-09T16:46:27.577Z] RequestService#request https://update.code.visualstudio.com/api/update/win32-x64/stable/379476f0e13988d90fab105c5c19e7abc8b1dea8
[main 2021-08-09T16:46:27.578Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-09T16:46:37.210Z] update#setState idle

I'm still experienceing this issue, and cannot currently use VS Code. Please let me know if there is anything else I can provide to help identify the cause.

I switched to the latest Insiders build (details below), and did not have this issue, so it seems to be specific to 1.59.0:
VS Code Insiders details
Version: 1.60.0-insider (user setup)
Commit: f0913d7718bbc4a805cd3a051335b4df60ca5d77
Date: 2021-08-17T05:15:18.727Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.18363

I meet this problem with v1.59.0 too. I download Insiders build for v1.60.0, it works.
The error logs for v1.59.0 as below.
C:\Program Files\Microsoft VS Code>code --verbose --log debug --disable-gpu
C:\Program Files\Microsoft VS Code>
[main 2021-08-18T10:13:46.616Z] Starting VS Code
[main 2021-08-18T10:13:46.617Z] from: c:\Program Files\Microsoft VS Code\resources\app
[main 2021-08-18T10:13:46.618Z] args: {
_: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
log: 'debug',
status: false,
'prof-startup': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': true,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-keytar': false,
'disable-workspace-trust': false,
'disable-crash-reporter': false,
'crash-reporter-id': 'bb19d5b0-139d-4694-9664-13c5f02f0b1d',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: 'C:\Users\yigc\AppData\Roaming\Code\logs\20210818T181346'
}
[main 2021-08-18T10:13:46.620Z] Deleting Chrome cached data path: c:\Users\yigc\AppData\Roaming\Code\Code Cache
[main 2021-08-18T10:13:46.623Z] Resolving machine identifier...
[main 2021-08-18T10:13:46.623Z] Resolved machine identifier: 9b985d50a377d0ad44d3e1c90fffa03daeded6a2c81a634eeeedeb03b579ecad
[main 2021-08-18T10:13:46.628Z] Main->SharedProcess#connect
[main 2021-08-18T10:13:46.640Z] StorageMainService: creating global storage
[main 2021-08-18T10:13:46.640Z] lifecycle (main): phase changed (value: 2)
[main 2021-08-18T10:13:46.641Z] windowsManager#open
[main 2021-08-18T10:13:46.641Z] windowsManager#open pathsToOpen [
{
backupPath: 'C:\Users\yigc\AppData\Roaming\Code\Backups\1629280905269',
remoteAuthority: undefined
}
]
[main 2021-08-18T10:13:46.642Z] IPC Object URL: Registered new channel vscode:f3f708ac-86fc-4f59-87ee-b081f3ebeaf6.
[main 2021-08-18T10:13:46.644Z] window#validateWindowState: validating window state on 3 display(s) { mode: 1, x: 284, y: 76, width: 1032, height: 776 }
[main 2021-08-18T10:13:46.646Z] window#validateWindowState: multi-monitor working area { x: 0, y: 0, width: 1536, height: 824 }
[main 2021-08-18T10:13:46.646Z] window#ctor: using window state { mode: 1, x: 284, y: 76, width: 1032, height: 776 }
[main 2021-08-18T10:13:46.646Z] window#ctor: vscode-file:// protocol is explicitly disabled
[main 2021-08-18T10:13:46.697Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-08-18T10:13:46.698Z] lifecycle (main): phase changed (value: 3)
[main 2021-08-18T10:13:46.703Z] update#setState idle
[main 2021-08-18T10:13:46.703Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-18T10:14:01.824Z] CodeWindow: detected unresponsive
[main 2021-08-18T10:14:16.718Z] update#checkForUpdates, state =  idle
[main 2021-08-18T10:14:16.719Z] update#setState checking for updates
[main 2021-08-18T10:14:16.722Z] RequestService#request https://update.code.visualstudio.com/api/update/win32-x64/stable/507ce72a4466fbb27b715c3722558bb15afa9f48
[main 2021-08-18T10:14:16.724Z] resolveShellEnv(): skipped (Windows)
[main 2021-08-18T10:15:47.741Z] IPC Object URL: Removed channel vscode:f3f708ac-86fc-4f59-87ee-b081f3ebeaf6.
[main 2021-08-18T10:15:47.741Z] Lifecycle#window.on('closed') - window ID 1
[main 2021-08-18T10:15:47.749Z] Lifecycle#onWillShutdown.fire()
[main 2021-08-18T10:15:47.752Z] Lifecycle#app.on(window-all-closed)
[main 2021-08-18T10:15:47.752Z] Lifecycle#app.on(before-quit)
[main 2021-08-18T10:15:47.753Z] Lifecycle#onBeforeShutdown.fire()
[main 2021-08-18T10:15:47.753Z] [WindowsStateHandler] onBeforeShutdown {
lastActiveWindow: {
workspaceIdentifier: undefined,
folder: undefined,
backupPath: 'C:\Users\yigc\AppData\Roaming\Code\Backups\1629280905269',
remoteAuthority: undefined,
uiState: [Object: null prototype] {
mode: 1,
x: 284,
y: 76,
width: 1032,
height: 776
}
},
lastPluginDevelopmentHostWindow: undefined,
openedWindows: []
}
[main 2021-08-18T10:15:47.754Z] Lifecycle#app.on(will-quit)
[main 2021-08-18T10:15:47.760Z] StorageMainService: closed global storage

I also reverted to 1.58.0 and turned off automatic updates - so it is working for now. I'll move to 1.60.0 when it is released.

Still seeing in 1.60.1, so I wouldn't recommend updating yet

Use both --disable-gpu --disable-software-rasterizer

Use both --disable-gpu --disable-software-rasterizer

Thanks! That worked for me too on 1.63.2

Can you test our exploration builds which are based on a newer runtime and see if the unresponsiveness happens without the --disable-gpu --disable-software-rasterizer flags. Thanks!
windows x64 user setup

@deepak1556 1.64 fixes it for me! 🥳
Tested on a non-elevated corporate laptop that usually doesn't let me run half my programs without some sort of trouble. I was using --disable-gpu --disable-software-rasterizer past few months, but it didn't seem to need it in 1.64
@lwblackledge does 1.64 fix it for you too?


IntrinsicFunction and call-args versus call-arg

I've had call-args as a vector of lists working with SubroutineCall and FunctionCall for a while (see Issue #32) . Here is the spec and an example lifted from the lpython .stdout reference outputs:
(s/def ::call-args (s/coll-of ::call-arg)) ;; <~~~ top level of list/vector
(s/def ::call-arg ;; <~~~ second level of list
  (s/coll-of ::expr?
             :min-count 1   ;; Issue 32
             :max-count 1))
(FunctionCall
  2 pow__AT____lpython_overloaded_0__pow
  2 pow
  [((IntegerConstant 2 (Integer 4 []))) ;; <~~~ call-args HERE
   ((IntegerConstant 2 (Integer 4 [])))]
  (Real 8 [])
  (RealConstant 4.000000 (Real 8 [])  )  ())

However, I encountered the following usage in expr_14-6023c49:
(IntrinsicFunction
  Abs
  [(RealBinOp ;; <~~~ not enough nesting
   (Var 2 a3)
   Sub
   (RealConstant 9.000000 (Real 8 []))
   (Real 8 [])  ()  )]
  0
  (Real 8 [])
  ()  )

This has one too few levels of nesting for a call-args. I solved it with a spec like this:
(s/def ::call-arg-or-args
  (s/or :call-arg  ::call-arg
        :call-args ::call-args))

(defmasrtype
  IntrinsicFunction expr
  (intrinsic-ident    call-arg-or-args      overload-id
                      return-type           value?))

I guess this is OK, but it's a little "hinky."

Here is a definition of IntrinsicFunction:
    | IntrinsicFunction(int intrinsic_id, expr* args, int overload_id,
            ttype? type, expr? value)

The arguments are just a list of expressions. They cannot be optional, so there is no double nesting. Everything seems clean? There is no call-arg or call-args for IntrinsicFunction.

We designed IntrinsicFunction to be more strict. No need to check for "nil", since it can't be nil.


Mm t3014 skin tone emoji

Summary
This PR adds Cypress test spec for checking if skin tone emojis are rendering correctly.
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/18162
Related Pull Requests
None
Screenshots
N/A
Release Note
Added Cypress test spec for checking if skin tone emojis are rendering correctly.

Hello @TheLaw1337,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Thanks for participating in Hacktoberfest! You can claim your sticker set here: https://get.printfection.com/hacktober21/4144583267 @TheLaw1337


0.3/mesos consul creds

Move Mesos leader credentials into the Consul K/V tree

@Y4Rv1K can you test this so we can merge it?

Closing this PR since Mesos credentials will be better stored in Vault instead of the Consul K/V. I'll leave the branch intact though for the role changes.


Rename signonotron2 to signon

We can now delete the duplicate jobs in CI and Deployment

👍
Could you also remove vhost_aliases from modules/govuk/manifests/apps/signon.pp?

Done