Excessive ubuntu1804 OS update activity on compute nodes

Required Info:

AWS ParallelCluster version: 2.11.0
Full cluster configuration without any credentials or personal data:

[global]
cluster_template = default
update_check = true
sanity_check = true
[aws]
aws_region_name = us-east-2
[aliases]
ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}
[cluster default]
key_name = <key_name>
base_os = ubuntu1804
scheduler = slurm
vpc_settings = default
scaling_settings = custom
ebs_settings = fs_ebs
efs_settings = fs_efs
master_instance_type = c5.xlarge
queue_settings = intel-spot,intel-noefa-spot
enable_intel_hpc_platform = false
disable_hyperthreading = true
s3_read_resource = <s3_info>
[vpc default]
vpc_id = <vpc_id>
master_subnet_id = <subnet_id>
vpc_security_group_id = <sg_id>
[scaling custom]
scaledown_idletime = 4
[ebs fs_ebs]
shared_dir = data
encrypted = true
volume_type = gp3
volume_size = 60
volume_iops = 3000
volume_throughput = 125
[efs fs_efs]
efs_fs_id = <efs_name>
shared_dir = shared
[queue intel-spot]
compute_resource_settings = c5n-18xlarge
compute_type = spot
enable_efa = true
placement_group = DYNAMIC
[queue intel-noefa-spot]
compute_resource_settings = c5n-18xlarge-noefa
compute_type = spot
enable_efa = false
placement_group = DYNAMIC
[compute_resource c5n-18xlarge]
instance_type = c5n.18xlarge
min_count = 0
initial_count = 0
max_count = 16
[compute_resource c5n-18xlarge-noefa]
instance_type = c5n.18xlarge
min_count = 0
initial_count = 0
max_count = 16
Bug description and how to reproduce:
When running a job on a compute node (via SLURM), ubuntu1804 OS update tasks are taking an excessive amount of time and CPU resource, even after the node (c5n.18xlarge) has been running for 15 mins. This makes it very difficult to do accurate benchmarking of short running jobs. Is it possible to disable the automatic updating of the OS and just use the version in the AMI you provide as is? I know it is good in general to get the fixes in the OS updates, but it would be nice to be able to control this with an option in ParallelCluster (e.g. on the queue or compute_resource settings), or doing the updates manually via adding commands in a post_install script.
Examples of the OS update processes running (from ps -ef on the compute node):
root      1773     1  0 09:10 ?        00:00:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
root      6935  6889 76 09:14 ?        00:02:50 /usr/bin/python3 /usr/bin/unattended-upgrade
root      7684  6935 10 09:18 ?        00:00:00 /usr/bin/python3 /usr/bin/unattended-upgrade
root      7832  7684  0 09:18 ?        00:00:00 /usr/bin/python3 /usr/bin/unattended-upgrade
(after about 10 mins):
root     25026  6935  0 09:22 ?        00:00:00 /usr/bin/python3 /usr/bin/unattended-upgrade
root     25148 25026  0 09:23 pts/1    00:00:00 /usr/bin/dpkg --status-fd 12 --configure --pending
root     25153 25148  0 09:23 pts/1    00:00:00 /bin/sh /var/lib/dpkg/info/linux-headers-5.4.0-1056-aws.postinst configu
root     25154 25153  0 09:23 pts/1    00:00:00 run-parts --report --exit-on-error --arg=5.4.0-1056-aws /etc/kernel/head
root     25155 25154  0 09:23 pts/1    00:00:00 /bin/sh /usr/lib/dkms/dkms_autoinstaller start 5.4.0-1056-aws
root     25161 25155  0 09:23 pts/1    00:00:00 /bin/bash /usr/sbin/dkms autoinstall --kernelver 5.4.0-1056-aws
root     29999 25161  0 09:23 pts/1    00:00:00 /bin/bash /usr/sbin/dkms autoinstall --kernelver 5.4.0-1056-aws
root     30474 29999  0 09:23 pts/1    00:00:00 /bin/bash /usr/sbin/dkms autoinstall --kernelver 5.4.0-1056-aws
root     30475 29999  0 09:23 pts/1    00:00:00 /bin/bash /usr/sbin/dkms autoinstall --kernelver 5.4.0-1056-aws
root     30476 30474  0 09:23 pts/1    00:00:00 make -j4 NV_EXCLUDE_BUILD_MODULES= KERNEL_UNAME=5.4.0-1056-aws IGNORE_CC
root     30482 30476  0 09:23 pts/1    00:00:00 /bin/sh -c make "CC=cc"  -C /lib/modules/5.4.0-1056-aws/build M=/var/lib
root     30483 30482  0 09:23 pts/1    00:00:00 make CC=cc -C /lib/modules/5.4.0-1056-aws/build M=/var/lib/dkms/nvidia/4
root     30913 30483  3 09:23 pts/1    00:00:00 make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia/460.73.01/buil
root     36119 30475  0 09:23 pts/1    00:00:00 sleep 3
root     36322 30913  0 09:24 pts/1    00:00:00 /bin/sh -c set -e;  echo '  CC [M]  /var/lib/dkms/nvidia/460.73.01/build
root     36323 36322  0 09:24 pts/1    00:00:00 cc -Wp,-MD,/var/lib/dkms/nvidia/460.73.01/build/nvidia-uvm/.uvm_va_block
root     36324 36323  0 09:24 pts/1    00:00:00 /usr/lib/gcc/x86_64-linux-gnu/7/cc1 -quiet -nostdinc -I ./arch/x86/inclu
root     36339 30913  0 09:24 pts/1    00:00:00 /bin/sh -c set -e;  echo '  CC [M]  /var/lib/dkms/nvidia/460.73.01/build
root     36340 36339  0 09:24 pts/1    00:00:00 cc -Wp,-MD,/var/lib/dkms/nvidia/460.73.01/build/nvidia-uvm/.uvm_range_gr
root     36341 36340  0 09:24 pts/1    00:00:00 /usr/lib/gcc/x86_64-linux-gnu/7/cc1 -quiet -nostdinc -I ./arch/x86/inclu
root     36356 30913  0 09:24 pts/1    00:00:00 /bin/sh -c set -e;  echo '  CC [M]  /var/lib/dkms/nvidia/460.73.01/build
root     36357 36356  0 09:24 pts/1    00:00:00 cc -Wp,-MD,/var/lib/dkms/nvidia/460.73.01/build/nvidia-uvm/.uvm_thread_c
root     36358 36357  0 09:24 pts/1    00:00:00 /usr/lib/gcc/x86_64-linux-gnu/7/cc1 -quiet -nostdinc -I ./arch/x86/inclu
Additional context:
I haven't tested other OS versions.

Hello @eshpc,
thank you for your feedback.
We are aware of the problematic of unattended upgrades and we are going to improve the situation in the future, starting from next version, see https://github.com/aws/aws-parallelcluster/pull/2915 for example.

Hi @lukeseawalker, thanks for the information. Good to know that it will be improved in the next version. In the meantime, I tried making those changes to /etc/apt/apt.conf.d/20auto-upgrades in my SLURM script, and it helped a lot. (Doing it in a pre-install script would be better of course).

Hello @eshpc,
PCluster version 3.0.0 is out and Ubuntu unattended upgrades are disabled by default


USHIFT-2214: Add missing dependency of microshift-olm on microshift package

/lgtm

/cherrypick release-4.15


https://github.com/datameet/maps

Data source

Please clarify, I don't see address data in that repo.

On Aug 4, 2017, at 06:19, jayaramkasi<EMAIL_ADDRESS>wrote:
Data source
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


docs(translation): GitOps Toolchain - Chinese Version #715

Pre-Checklist
Note: please complete ALL items in the following checklist.

[x] I have read through the CONTRIBUTING.md documentation.
[x] My code has the necessary comments and documentation (if needed).
[x] I have added relevant tests

Description

Translate the GitOps.md into Chinese.
Minor fix in commit-messages.zh.md file.
Related Issues

This PR is related to #715 #720
New Behavior (screenshots if needed)

This PR is the refinement version of #720 with DCO and some review.

@aucker To speed things up, I have updated the doc directly in this PR according to our previous discussion. I hope you don't mind. Merging now. Thanks for your contribution!


config: setup 'arrow-parens' eslint rule

As discussed with @johnjbarton here this rule will force us to use parens in arrow functions.

CI servers fails when eslint fails. Current build pass, so we don't need to fix anything. I fixed 4 cases within this pr.


Console has strange message when running installed version on Mac.

Describe the bug
I checked out the code from develop, built it, and installed using "make install". My install location was set to $HOME/Development/MAIN/install. When I run the VisIt installed there from the console, I see a message printed to the console. When I run VisIt from the out-of-source-build's bin directory, I get no message. This is on Mac 10.12.8.
./install/bin/visit -noconfig
Running: gui3.0.0 -noconfig
Empty filename passed to function
Running: viewer3.0.0 -noconfig -geometry 2207x1337+353+0 -borders 20,0,0,1 -shift 0,0 -preshift 0,0 -defer -host <IP_ADDRESS> -port 5600
Running: mdserver3.0.0 -host <IP_ADDRESS> -port 5601
Helpful additional information
(Please click check boxes AFTER submitting ticket)

[ ] Did VisIt crash?
[ ] Did you get wrong results?

Impact

[ ] High - User productivity significantly degraded
[ ] Medium - User productivity partially degraded
[ ] Low - User productivity trivially degraded

Likelihood

[ ] High - occurrence is not specific to platform, data, config, a combination of operators, queries, etc.
[ ] Medium - neither low nor high likelihood
[ ] Low - occurrence is specific to combination of multiple factors such as configuration, data, platform, etc.

To Reproduce
Run "visit" on the command line after doing "make install".
Expected behavior
VisIt runs but writes a message.
Attachments
Desktop

MacOS 10.12.8
VisIt Version: develop

Additional context

Guessing this is related to a poor usage of Qt somewhere similar to this


Add table turbot_grant and turbot_active_grants

References
Add any related links that will help us understand the resource, including vendor documentation, related GitHub issues, and Go SDK documentation.
I would like to audit who has active grant permissions in my turbot workspace.

@alexama2012 Appreciate using Steampipe & suggestions. Nice to see you for testing this out in the Turbot workspace.
We are looking into this, will keep you updated.

@alexama2012 we have a draft branch ready if you would like to test & check, it satisfies the need would be great. Draft Branch   > Below the steps

git clone https://github.com/turbot/steampipe-plugin-turbot.git  (if first time closing the repo)
cd steampipe-plugin-turbot
run make
This should have the turbot_grant table, you can run against your turbot workspace cred.

Let us know in case of any issues.

FYI Joe.
Martin* Alexander* | Engineer II, Cloud Operations
email @.***  mobile
[image: WOW!]
On Tue, Nov 30, 2021 at 4:50 AM Raj @.***> wrote:

@alexama2012 https://github.com/alexama2012 we have a draft branch
ready if you would like to test & check, it satisfies the need would be
great. Draft Branch
https://github.com/turbot/steampipe-plugin-turbot/tree/issue-12 > Below
the steps

git clone https://github.com/turbot/steampipe-plugin-turbot.git (if
first time closing the repo)
cd steampipe-plugin-turbot
run make
This should have the turbot_grant table, you can run against your
turbot workspace cred.

Let us know in case of any issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/turbot/steampipe-plugin-turbot/issues/12#issuecomment-982518093,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARAOHBOSH4N6L3MFU2DDUB3UOSUA3ANCNFSM5ICFSHZA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Add "Run" lens for binary runnables

Add an easy way to launch the different main methods from VS Code:
Before:

After:

I've decided to omit the ▶ symbol (as done for benches) since it looks a bit weird to me, but here's the version with it, just to compare:

bors r+
Btw, this is also available via a shortcut

Which one?
I've tried ctrl + r, but it does not give anything special:

No luck when I search for run or execute words via Cmd + Shift + P dialogue.

It’s ctrl+r. The cursor should be on main for it to show “run main”

Worked indeed, thanks for the tip.
Just a side note: by default, VS Code already uses ctrl + r for opening the recent project, so this shortcut clashes with it.
But you know that most probably :)


Added a receive flush timeout just prior to launching the next poll when

using a TCP connection.  Without this, a slow response can cause
transaction ID mismatches for the life of this TCP connection (it
never recovers).  This occurs when a remote device does answer, but
it answers too slowly.  The request has already timed out, and when
the next request is launched the previous response is read (rather
than the new one) causing this error.

hi,i think you should change the SetReadDeadline(time.now) to SetReadDeadline(time.now().add(time.millisecod*1))


could not download

Make sure to do the following before submitting your issue - thanks!

[ ] Make sure you're running the latest release. You can find your version number at the bottom of the Help menu in Catch.
[ ] Check the FAQ, your question might be answered there.
[ ] Check for an open issue, and please comment on that issue instead of creating a duplicate.

Hi,
Running latest version:
Every "Check" results in:
default	10:34:44.851254 +0200	com.giorgiocalderolla.Catch.CatchFeedHelper	Could not download http://reflektor.karmorra.info/torrent/03C7321C229C1D510162D90DC998B39378EE8701.torrent: Error Domain=com.giorgiocalderolla.Catch.CatchFeedHelper Code=-7 "Could not download torrent file (bad status code 404)" UserInfo={NSLocalizedDescription=Could not download torrent file (bad status code 404)}
default	10:34:44.851658 +0200	Catch	Feed Helper error (checking feed): Error Domain=com.giorgiocalderolla.Catch.CatchFeedHelper Code=-7 "Could not download torrent file (bad status code 404)" UserInfo={NSLocalizedDescription=Could not download torrent file (bad status code 404)}

Please actually check the FAQ, don’t just check the box mmkay? :)

You are right, sorry.
So that means, I am in a bind, as I can only download using magnets, but then I cannot save to a folder :-)

You can setup a download folder in your torrent client. The thing that doesn’t work is having each show go to its own subfolder.

Or if you meant save the .torrent files, you only will be able to save the magnet links as .webloc files. But you won’t be able to save .torrent files because they do not exist :)

Exactly, that is the issue for me.


update AWS CloudFormation template and cloud-configs

Our good old CloudFormation template now supports Kubernetes 0.16.1 on the latest CoreOS (668.2.0).
I did a lot of cleanup in order to use CoreOS's cloud-init in a more appropriate way, especially regarding flannel and docker services invocation.
Future work may include the cloud provider integration and token distribution via etcd.

@antoineco - Thanks for updating to the latest release!
I just took a look over your change and it looks good but unfortunately you need to rebase before we can merge.

Thanks for the review @roberthbailey, I just rebased


Content is always escaped?

Hey there, first of all thanks so much for this! Such a big help in day to day logging needs.
I'm currently writing a quite involved interface that exchanges data between an ecommerce platform and an ERP system and makes heavy use of logging.
One thing I noticed is that all log lines that get sent to loki are fully escaped.
Is this a Grafana thing, or are they escaped within this crate? I would love to view the logs unescaped for easier handling.
My setup (roughly):
    let (layer, task) = tracing_loki::layer(
        loki_url,
        vec![host, app, log_env].into_iter().collect(),
        Default::default(),
    )?;
    tracing_subscriber::registry()
        .with(layer)
        .with(tracing_subscriber::fmt::Layer::new())
        .with(tracing_subscriber::EnvFilter::from_str(
            "info,tiberius=error,hyper=error",
        )?)
        .init();

Example (a bit mangled to hammer down the point):

                let diff = format_text_diff(&jp.body_html, &sp.body_html);
                warn!(
                    "Beschreibungstext bei {} abweichend.
Abweichungen: {diff}

JTL: '{}',
Shopify: '{}'",
                    jp.handle, jp.body_html, sp.body_html
                );

What gets displayed in grafana:
"Beschreibungstext bei besser-grillen abweichend.\nAbweichungen: Gelöscht in Position 261:\t\t\" \"Hinzugefügt in Position 261:\t\" \"\n\nJTL: ....',\nShopify: ...'\n\nTrace:\n \n ...\n"

In the CLI the correct, unescaped output from the tracing_subscriber layer is shown.
For completeness: I made a small wrapper to include the backtrace in warnings. Shouldn't modiy any escaping tho.

#[macro_export(local_inner_macros)]
macro_rules! warn {
    // warn!("a {} event", "log")
    ($($arg:tt)+) => {{
        let mut a = std::format!($($arg)+);
        a += "\n\nTrace:\n";
        let b = std::backtrace::Backtrace::force_capture();
        let bs = b.to_string();
        a += &bs;
        log::warn!("{a}")
    }};
}

... as always: Trying to get it to run for hours, then write an issue, and find the solution 3 minutes later...
Using {app="ankertau", env="live-de", level=~"warn|error"} | json | line_format {{.message}}`` shows the correct, unescaped text. I'll try to find a more elegant way to display it, but for now it's working nicely.


appcontainers-track2

release for issue: https://github.com/Azure/sdk-release-request/issues/2782

/azp run prepare-pipelines

/azp run js - appcontainers - mgmt - ci


Note: C:\Flutter\flutter.pub-cache\hosted\pub.dartlang.org\cloud_firestore-0.13.5\android\src\main\java\io\flutter\plugins\firebase\cloudfirestore\CloudFirestorePlugin.java uses unchecked or unsafe operations.

Note: C:\Flutter\flutter.pub-cache\hosted\pub.dartlang.org\cloud_firestore-0.13.5\android\src\main\java\io\flutter\plugins\firebase\cloudfirestore\CloudFirestorePlugin.java uses unchecked or unsafe operations.
Why it is showing this warning?

what was the solution ?

i'm facing the same error

It is just a warning when firebase cloudstore package is upgraded to  cloud_firestore: ^0.13.5
You can ignore it, the app still runs.
The warning removed in my case in the following way:
Open build.gradle in android app level build
add this
defaultConfig
{
multiDexEnabled true
}
and add this dependency-
implementation 'androidx.multidex:multidex:2.0.1'
then save-> invalidate and restart->flutter clean->flutter Pub upgrade->flutter Pub get
then Run.

Hi @abhiditi, for what I can see the issue is related to a FlutterFire plugin.
duplicate of https://github.com/FirebaseExtended/flutterfire/issues/1926


F# Language Server crashed 5 times in the last 3 minutes

Describe the bug**
F# Language Server crashed 5 times in the last 3 minutes
Steps to reproduce
On startup
Link to sample reproduction
https://github.com/fable-compiler/fable2-samples/tree/master/minimal
Expected behaviour
Not crashing
Machine info

OS: Ubuntu 20.04.1 LTS
.NET SDK version: 3.1.302
Ionide version: 5.1.0

Additional context
Found this issue: https://github.com/fsprojects/fsharp-language-server/issues/43
Resolved by installing Ionide 4.17 from VSIX

As noted in the Release Notes for Ionide 5.0 and up, .Net 5 is required. Otherwise yes, you'll see this. Closing as designed.

As noted in the Release Notes for Ionide 5.0 and up, .Net 5 is required. Otherwise yes, you'll see this. Closing as designed.

Also, please note that fsprojects/fsharp-language-server is a completely separate LSP implementation from Ionide, and it's very unlikely that issues raised in that repo have a direct correlation or relevance to this project as a result.

Also, please note that fsprojects/fsharp-language-server is a completely separate LSP implementation from Ionide, and it's very unlikely that issues raised in that repo have a direct correlation or relevance to this project as a result.

As noted in the Release Notes for Ionide 5.0 and up, .Net 5 is required. Otherwise yes, you'll see this. Closing as designed.

You should not close this, since your argument is invalid. I have enabled .net core 5.0.100 with a global.json file, the version 5 is active and still see the same error.

Just a comment since I ran into this just now.  The ionide error reporting for wrong dotnet sdk versions seems to be a little fragile and misleading.   I have a global.json file with an older version of the sdk mentioned (6.0.101) and had a newer version installed (6.0.202).  It worked fine when I fixed the global.json file, but the traces in the F# logs are a bit confusing.  The first line is right - there isn't a compatible version installed (compatible with global.json).  The rest of the messages are a little chaotic.  The application --version does not exist ??     Unable to parse sdk version from the string '        6.0.202 [C:\Program Files\dotnet\sdk]'  -  might be hard to do, but the information is there to give the user a simple message - project asks for 6.0.101 and it's not installed.  You appear to have 6.0.202 installed.  This is with the F# console opened.  Without that, you just hear that the F# server crashed 5 times in the last 3 minutes - which isn't a wonderful experience for a novice.
Could not execute because the application was not found or a compatible .NET SDK is not installed.
Possible reasons for this include:
  * You intended to execute a .NET program:
      The application '--version' does not exist.
  * You intended to execute a .NET SDK command:
      A compatible installed .NET SDK for global.json version [6.0.101] from [c:\extproj\Plough.WebApi\global.json] was not found.
      Install the [6.0.101] .NET SDK or update [c:\extproj\Plough.WebApi\global.json] with an installed .NET SDK:
Unhandled exception: System.Exception: Unable to parse sdk version from the string '        6.0.202 [C:\Program Files\dotnet\sdk]'. This value came from running `C:\Program Files\dotnet\dotnet.exe [--version]` at path c:\extproj\Plough.WebApi\src\Plough.WebApi.Client.Dotnet

Ah gotcha - since we're invoking 'dotnet --version' to check versions, if that dotnet can't be invoked by the SDK itself we need to be able to handle that. Makes sense to me.

Exactly,
With wrong global.json (set tp 6.0.101 vs installed 6..0.202)
$ dotnet --version
Could not execute because the application was not found or a compatible .NET SDK is not installed.
Possible reasons for this include:
  * You intended to execute a .NET program:
      The application '--version' does not exist.
  * You intended to execute a .NET SDK command:
      A compatible installed .NET SDK for global.json version [6.0.101] from [C:\extproj\Plough.WebApi\global.json] was not found.
      Install the [6.0.101] .NET SDK or update [C:\extproj\Plough.WebApi\global.json] with an installed .NET SDK:
        6.0.202 [C:\Program Files\dotnet\sdk]

Once global.json is edited to match installed version of sdk
$ dotnet --version
6.0.202

So you'd have to parse that helpful but messy error message to give the GUI user a clue about what's happening.

Just a comment since I ran into this just now. The ionide error reporting for wrong dotnet sdk versions seems to be a little fragile and misleading. I have a global.json file with an older version of the sdk mentioned (6.0.101) and had a newer version installed (6.0.202). It worked fine when I fixed the global.json file, but the traces in the F# logs are a bit confusing. The first line is right - there isn't a compatible version installed (compatible with global.json). The rest of the messages are a little chaotic. The application --version does not exist ??  Unable to parse sdk version from the string ' 6.0.202 [C:\Program Files\dotnet\sdk]' - might be hard to do, but the information is there to give the user a simple message - project asks for 6.0.101 and it's not installed. You appear to have 6.0.202 installed. This is with the F# console opened. Without that, you just hear that the F# server crashed 5 times in the last 3 minutes - which isn't a wonderful experience for a novice.
Could not execute because the application was not found or a compatible .NET SDK is not installed.
Possible reasons for this include:
  * You intended to execute a .NET program:
      The application '--version' does not exist.
  * You intended to execute a .NET SDK command:
      A compatible installed .NET SDK for global.json version [6.0.101] from [c:\extproj\Plough.WebApi\global.json] was not found.
      Install the [6.0.101] .NET SDK or update [c:\extproj\Plough.WebApi\global.json] with an installed .NET SDK:
Unhandled exception: System.Exception: Unable to parse sdk version from the string '        6.0.202 [C:\Program Files\dotnet\sdk]'. This value came from running `C:\Program Files\dotnet\dotnet.exe [--version]` at path c:\extproj\Plough.WebApi\src\Plough.WebApi.Client.Dotnet

I don't think this is my case. I have installed and active the version set up in the global.json.
What I get from the F# output is a reference to a folder path that ionide seems to send, and it breaks it:
Unhandled exception: System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'c:\repos\fs\FirstIonideProject\dotnet' with working directory 'c:\repos\fs\FirstIonideProject'. The system cannot find the file specified.
That dotnet folder is not created by default when scaffolding a F# project. To me ionide seems to be failing to look for the dotnet.exe ?
Give me some clues please on where should I look to correct this. I've checked my system path env var, and the first thing there is the path to dotnet sdk.

Seems my problem was caused by a wrong environment variable:
Wrong:

Correct:


report spam JSPERF

https://jsperf.com/download-drake-more-life-full-album-download

Sigh...

Google reCAPTCHA was implemented in jsPerf v1 (the old PHP-based version). Spam still got through.
See #232 for the discussion on how to tackle this.


PHP executable not found. You need PHP 7 installed and in your PATH

VSCode Version: 1.5.3
OS Version: Windows 10 x64

Hi, Humans.
Steps to Reproduce:

I installed VS code and then the problem started.
I opened VS and then I installed ftp-simple extension.
I opened project next I opened file with php extension.
Then I saw this info

Cannot validate the php file. The php program was not found. Use the 'php.validate.executablePath' setting to configure the location of 'php'

I said okey, and I opened

FIle > Preferences > User Settings > Settings.json

I added this line

// Points to the php executable.
"php.validate.executablePath":"C:\OpenServer\modules\php\PHP-7-x64\php.exe",

The problem is gone.
5. But then I saw new error

PHP executable not found. You need PHP 7 installed and in your PATH

How to solve this error I don't know. Please, help me.

I am having the same problem. I wanted to use the IntelliSense extension for VS Code editor and when I made the path point to version 7 of the php.exe I got from wamp I got the same error.

I had the same error, so I removed the executablePath setting and did the following steps:
Windows search for "environment"
click on edit environment variables (for your acount)
click on the "path" variable and press "Edit..."
click on "new"
write down the path to your php 7 files, for example: D:\php7
(in your case it should be: C:\OpenServer\modules\php\PHP-7-x64 )
When starting visual studio code the error should be gone.

I did change the environment variable path. Still getting the error.

There are multiple failure-modes here, and they all have similar messages, so let's try and to be specific about which one we're talking about.

#
Error message
Source
Resolution

1
Cannot validate the php file. The php program was not found. Use the 'php.validate.executablePath' setting to configure the location of 'php'
built-in PHP validation provider
Set php.validate.executablePath in FIle > Preferences > User Settings > Settings.json or add php to your PATH, which we'll fall back to if php.validate.executablePath is not set

2
Failed to run php using path: {0}. Reason is unknown.
built-in PHP validation provider
??? - try running My\php\validate\executablePath\php.exe -l -n -d log_errors=Off -f myFile.php, and paste the output

3
PHP executable not found. You need PHP 7 installed and in your PATHThe language server needs at least PHP 7 installed and in your PATH. Version found: ' + versionError spawning PHP: ' + err.messageError parsing PHP version. Please check the output of php --version
vscode-php-intellisense extension
Add the path to PHP7 to your environment variables, run where php and php --version to verify. You'll also need to relaunch VSCode (and the cmd line you are launching it from if you changed the environment variables)

So @FAST-JE, it looks like you ran into *#*1 first, you resolved it by adding php.validate.executablePath, and then ran into *#*3.1, so it would be great if you could verify that adding PHP7 to your env. variables resolves the issue. There's also an issue open to make the intellisense engine respect php.validate.executablePath https://github.com/felixfbecker/vscode-php-intellisense/issues/11, cc @felixfbecker
@dkimery256 I have no idea what error you're running into, but hopefully the table above will help narrow it down :smiley:

@dkimery256 oh, and one more thing! Just a hunch... you mentioned you changed the PATH from PHP5 to PHP7, which implies that this is not a new environment config, which implies that you've likely customized your PHP5 ini file, which implies that your PHP7 ini file might have different settings than your PHP5 ini file, which implies that something about those settings might have an effect on whether php commands execute as expected in VSCode or the php intellisense extension, which implies that WAMP has different default settings than default PHP that somehow impact basic execution, which implies that there's a good chance that it's related to some virtual filepath config, as is often the case with "cooked" environment setups.
So in summary, if you get errors after running php --version or php -l -n -d log_errors=Off -f myFile.php, also check your php.ini file, and, in particular, look out for potentially invalid filepaths.

The message is indeed caused by my extension, thanks for clearing that up to detailed @mousetraps.
I'm haven't decided yet what settings "namespace" I should use for PHP IntelliSense. My thought was that the built-in PHP support hopefully soon gets removed from core? Because the validation and completion is conflicting with PHP IntelliSense and causing duplicate entries. Which is one of the reason why I thought it might be a good idea to use a generic php.executablePath setting, instead of php.intellisense.executablePath. Would be nice to hear some opinions on this from VS Code devs.

@mousetraps I Added the path to PHP7 to your environment variables screenshot
and screenshot settings.json
The problem is not solved.

@FAST-JE You need to add the path of the directory, not the path to the exe. If you still experience problems please open an issue at my repository or chat with me on Gitter so we don't spam the VS Code dev folks here.

I'm haven't decided yet what settings "namespace" I should use for PHP IntelliSense. My thought was that the built-in PHP support hopefully soon gets removed from core? Because the validation and completion is conflicting with PHP IntelliSense and causing duplicate entries. Which is one of the reason why I thought it might be a good idea to use a generic php.executablePath setting, instead of php.intellisense.executablePath. Would be nice to hear some opinions on this from VS Code devs.

@felixfbecker I like the idea of using php.executablePath rather than php.validate.executablePath both for the sake of simplification and because that appears to be how the broader ecosystem has tended to evolve (this is what both the Go and Python extensions do).
Also agreed re: removing built-in PHP support, because it appears to be the only language VSCode includes built-in completions for that is not one of the languages that VSCode is actually written in. No guarantees how soon that'll be, but I'll look into the potential implications this week. In the meantime, is there anything you can do to filter out duplicates in the completion list?

Closing this thread, as the primary issue has been resolved. @felixfbecker let's chat further about the executablePath stuff on a separate thread. One of the challenges will be figuring out how to resolve discrepancies with different versions of PHP between different extensions. Would be curious to hear your thoughts.

"php.executablePath":"C:\wamp64\bin\php\php7.0.10\php.exe",

I got this working some time ago, forgot about the thread, sorry.  My problem was that I had my path set right in VS-Code, but my system var path I had included the php.exe in the path and that was causing issues.  Once I pointed my system var to the directory alone and not the exe, everything worked just fine.  Thanks for all the suggestions.

For anyone having this issue, it is due the PATH, you must change your environment PATH.
on Linux: nano ~/.bash_profile
On Windows: Edit environment Variables -> System Variables -> Path. Change the priority

SOLVED:
Added in Settings:
{
    "php.executablePath": "C:\\PHP_7\\php.exe",
    "php.validate.executablePath": "C:\\PHP_7\\php.exe",
    ...
}

For Mac users:
This is what worked for me.
{
"php.executablePath": "/absolute path to your php 7 installation"
}

You installed PHP IntelliSense extension, and this error because of it.
So if you want to fix this problem go to this menu:
File -> Presences -> User Settings
Now you can see 2 window. In the right window add below codes:
{
"php.validate.executablePath": "C:\wamp64\bin\php\php7.0.4\php.exe",
"php.executablePath": "C:\wamp64\bin\php\php7.0.4\php.exe"
}
NOTICE: This address C:\wamp64\bin\php\php7.0.4\php.exe is my php7.exe file address. Replace this address with own php7.exe.
Font: https://stackoverflow.com/questions/40287927/php-executable-not-found-install-php-7-and-add-it-to-your-path-or-set-the-php-e/45784662#45784662

i've added php path to Windows Path then error disappears.

When I added the PHP execuable to the Path variable in windows it fixed the error for me.

@Firegarden Can you ensure when you open a command prompt, that you can type php -v and get your current php version?

Wy not just add a 'dont show option' for this useless function?


Comment not completely exported

Describe the problem
I use this configuration from the template:
  {
    "source": "comment",
    "target": "System.History",
    "mapper": "MapRendered"
  },

I have encountered a case where comment is only partly exported from Jira. Comment is approximately this:

Something something /DWTest/ABCDEF. For now only in dev. Done for the ticket TICKET-209 needs. EXT External User

What happens is that the link and the word "needs" that comes after it simply disappear, so the final comment in imported work item looks like this:

Something something /DWTest/ABCDEF. For now only in dev. Done for the ticket EXT External User

If I remove the mapper from the configuration, the whole text does appear, but of course all the links to both users and tickets will get broken.
The project has several thousand tickets and I am looking for a second instance, but this seems quite a major bug, as my organization relies on having all the comments intact for audit purposes for several years.
To Reproduce
Managed to replicate this consistently. It seems like
[TICKET-123] word [~user]
is the breaking pattern.
Steps to reproduce the behavior:

Create ticket
Add a comment like "something something [TICKET-123] something [~ext_usr]
Export the ticket
In the exported JSON '[TICKET-123] something' will be missing.

Tool version
3.0.284
Attachments
Please attach the following files:
I created a test ticket and tried a few variants of the form to find out how it breaks.
jira-export-log-231220-103620.txt
Also removed irrelevant parts from config.json:
config-elo-rapkeh copy.json

@tenderi I tried to reproduce your issue in Jira Cloud but so far haven't had any luck. Everything seems to work fine.
Maybe you can tell me if have have done something wrong? Otherwise can you identify any particular conditions under which the error happens for you?
Here is my field map:
      {
        "source": "comment",
        "target": "System.History",
        "mapper": "MapRendered"
      },

I tried a few variations of the above pattern:

Here is the corresponding issue in ADO, everything looks good:

Here is the exported issue file for reference: AGILEDEMO-44.json

Weird. I can still reproduce the bug 100% of the cases. The issue must be in the exporter, as the text doesn't even show in the exported file. The behaviour happens in both description and comment fields. I use identical typemap as the one you provided.
We are not using Jira Cloud though, but Jira Server. I don't have experience with Cloud edition, but afaik the cloud version has been updated quite much. I wonder if the links are somehow different?

Description
I think I have another example of this issue....
I have Jira comments that include hyperlinks. The exporter is exporting the commits, but losing the Hyper-Links
As noted above, the export manifest is set to use the MapRendered mapper
  {
        "source": "comment",
        "target": "System.History",
        "mapper": "MapRendered"
      },

If use, what I think is the API call used by the exporter /rest/api/2/issue/<ticket>?expand=changelog, I see the link in the returned in the form [text|url]
 "comment": {
     "startAt": 0,
     "maxResults": 4,
     "total": 4,
     "comments": [
         {
             "self": "<base url>/rest/api/2/issue/34822/comment/75246",
             "id": "75246",
             "author": { .. }
             "body": "A draft script has now been written and merge request created on Gitlab [here|https://<gitlab url>]. It's been assigned to [~another.person] for checking.\r\n\r\nWe're aiming to deliver the estimated response rates by Friday.",
    ....
    },

But if I look in the exported JSON file I find the comment, but don't see the link, or part of the text just after it.
"Fields": [
        {
          "ReferenceName": "System.History",
          "Value": "
A draft script has now been written and merge request created on Gitlab Another Person for checking.
\n\n
We're aiming to deliver the estimated response rates by Friday.
"
        }
      ],

I am using an on-prem Jira instance


Asurine in a Veridium Geode

Is this supposed to be there? There's at least two in this geode. Version 0.1.4

Nvm, I guess this was a "brass" geode. Should have read the page closer lol


Commands as interfaces?

I was wondering if abstracting commands as interfaces instead of classes would be usefull. Command handlers and Validators could be implemented against that interface.
Lets take an hypotetical ICreateProductCommand. This particular command could have different implementations:

CreateProductViewModel: ICreateProductCommand (for use with MVC View, could have some additional properties for View use only, like collections for dropdowns databinding)
CreateProdutctDto: ICreateProductCommand (for use with a WebApi accessed by a mobile device, tailored for json serialization)
CreateProductFromExcel: ICreateProductCommand (wich could be a form a batch writing, part of a totally different Product creation flow)

Is that make sense, or am I looking at it from a wrong perspective? Should I use composition instead (CreateProductViewModel have one CreateProductCommand ou returns a new CreateProductCommand instance)?

Hi Lucianoac,
Sure, a setup as you described could work well, but I personally think the setup in NorthwindTraders with Mediatr is clearer and let me explain why.
We have a very clear distinction between defining the Command - which specifies the operation we want to invoke and contains all the data we need to make that invocation, and the CommandHandler which is the code that actually performs the work once we've passed in a Command instance.
I feel this distinction is less clear when interfaces define the command and implementations of that interface define the command handler.
How would I handle the different kinds of differing use cases you provided?
For me the point of mediatr command/query specifications is that any code that is capable of building a command object can invoke that command - so I would make a CreateProductCommand that contains the common "save product" definition for all three use cases and then get the various paths to build that from their respective WebAPI or MVC controllers etc.
If there is lookup data needed to populate dropdowns etc, I would make that a separate Query.

Hi Brendan,
thanks for your feedback. I find software architecture a fascinating topic and it's very nice to talk about it with someone experienced like yourself. Awesome project by the way! Keep going.

Keep it simple, each command or query represents a single and separate business use case. If there is duplication of logic, push it down. Refer to Jimmy's article Dealing with Duplication in MediatR Handlers
. Happy coding!


No visible @interface for 'PushIOManager' declares the selector 'setDelayRegistration:'

After i update for new version v6.48.3, i have this problem, and cannot build anymore my app, what can i do for this?
No visible @interface for 'PushIOManager' declares the selector 'setDelayRegistration:'

Please make sure that you update the native SDK framework as well. This plugin release is compatible with iOS SDK v6.48.1.

Please make sure that you update the native SDK framework as well. This plugin release is compatible with iOS SDK v6.48.1.

That's it! if i use a 6.49 still having trouble, but if i use 6.48.1, it's works! thank you!


[Feature Request] Output all nodes from canvas flow

Currently, only one output node (that was executed) and it's input nodes are being output when a model is exported. Would it be possible to have all nodes in the flow be output?

Here's a design for this issue:

The edit panel of each node (except the Input document node) should have a checkbox Output this node
If the checkbox is checked, the behavior for the export function should be to include the .xml file for this node (and all its inputs) into the exported package, and add the node name to the list of outputTypes in manifest.json.


Fix NUnitXML support

Following up on #63 (see that PR for tips on quickly testing this module branch):
Added NUnitXML support back in, for those (anyone?) using Vester in CI/CD scenarios.
Just kidding, Invoke-VesterTest, you're gone after all. It was calling Pester over and over again in small spurts, which was terrible for both screen output and XML output.
So now, the logic flow is basically:

Invoke-Vester

User chooses Config, Tests, Remediate, NUnitXML (or accepts defaults)
Get-ChildItem, if necessary, to build the full *.Vester.ps1 test array
For each Config file:

Ensure it's valid
Invoke-Pester on the Vester template

VesterTemplate.Tests.ps1

Receive single config, all tests, remediate preference
Loop through each test one by one:

Determine the scope of the test
Grab $Title/$Desired/$Actual/$Fix from *.Vester.ps1 file
Build the list of relevant VMware inventory objects to test against
Run the test against each object found

Let me know if you find any problems. At this point, I think existing tests just need to be ported to the new format, and we're ready to discuss publishing to the gallery. If you want to help porting tests, please feel free!

Just tested it but it does not seem to work. Everythink works fine except that it does not create any xml file in the path I provided
My workflow:

Run New-VesterConfig -Quiet
i. it create correctly the config file

Run Invoke-Vester -XMLOutputPath .\vester.xml
i. Tests run as usual
ii. no creation of the vester.xml file

Am I missing something ?

I found the bug ... the param is defined as $XMLOutputPath but the variable used everywhere else is $XMLOutputFile.

👍
btw $XMLOutputFile sounds more accurate as we are expected to provide a file...

I'm dumb. I started with Path and then reached @equelin's conclusion that File seems better. Will fix shortly.

:shipit:


scala steward job failed with a compilation error for org.scalatest:scalatest : 3.0.8 -> 3.1.0

https://gitlab.com/tyrcho/michel-steward/-/jobs/365504552
java.io.IOException:
'sbt -batch -no-colors ;scalafixEnable;scalafix https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.0.x/rules/src/main/scala/org/scalatest/autofix/v3_0_x/RenameDeprecatedPackage.scala;test:scalafix
https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.0.x/rules/src/main/scala/org/scalatest/autofix/v3_0_x/RenameDeprecatedPackage.scala;scalafix
https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.1.x/rules/src/main/scala/org/scalatest/autofix/v3_1_x/RewriteDeprecatedNames.scala;test:scalafix
https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.1.x/rules/src/main/scala/org/scalatest/autofix/v3_1_x/RewriteDeprecatedNames.scala'
exited with code 1

The CI job (which simply runs scala steward) failed, I think this exception should be caught by scala steward : it should not rely on scalafix migration to always succeed.

Note: the migration was applied (at least partially) in the MR created by scala steward : https://gitlab.com/tyrcho/approvals-demo-scala/commit/c64eac9c0d6e21278ee348576fd873930856386a

I see the same issue on all projects which use scalatest:
https://gitlab.com/colisweb-open-source/scala-steward/-/jobs/365825891#L202
https://gitlab.com/colisweb-open-source/scala-steward/-/jobs/365825886#L247

I agree that Scala Steward should better handle failed Scalafix migrations. My current thinking is that it should still commit the changes done by the failed migration(s), note in the PR body that there was an error while applying the migrations, and add a tag like failed-scalafix-migrations to the PR body. Maybe the partial Scalafix changes can still be useful and if they are in a separate commit than the version bump, it should be easy to discard them.

I tried this quickfix on my project and it seems to be OK !
It's not as elaborate as what @fthomas suggested (it does not mention in the MR that the migration failed) but I think it's already better than the current behavior.
It kept the scalafix changes in the generated MR : https://gitlab.com/tyrcho/approvals-scala/merge_requests/6/diffs
Here is what the log looks like now:
[info] running (fork) org.scalasteward.core.Main --disable-sandbox --do-not-fork --workspace /tmp/workspace --repos-file /Users/michel/git/katas/michel-steward/repos.md --git-ask-pass /Users/michel/git/katas/michel-steward/pass.sh --git-author-email<EMAIL_ADDRESS>--vcs-type gitlab --vcs-api-host https://gitlab.com/api/v4/ --vcs-login tyrcho
[info] 2019-12-03 14:53:01,120 INFO
[info]   ____            _         ____  _                             _
[info]  / ___|  ___ __ _| | __ _  / ___|| |_ _____      ____ _ _ __ __| |
[info]  \___ \ / __/ _` | |/ _` | \___ \| __/ _ \ \ /\ / / _` | '__/ _` |
[info]   ___) | (_| (_| | | (_| |  ___) | ||  __/\ V  V / (_| | | | (_| |
[info]  |____/ \___\__,_|_|\__,_| |____/ \__\___| \_/\_/ \__,_|_|  \__,_|
[info]  v0.4.0-280-7afc0d2e-20191203-1211
[info]
[info] 2019-12-03 14:53:01,123 INFO  Run self checks
[info] 2019-12-03 14:53:02,411 INFO  Add global sbt plugins
[info] 2019-12-03 14:53:02,447 INFO  Clean workspace /tmp/workspace
[info] 2019-12-03 14:53:02,471 INFO  ──────────── Nurture tyrcho/approvals-scala ────────────
[info] 2019-12-03 14:53:02,473 INFO  Clone and synchronize tyrcho/approvals-scala
[info] 2019-12-03 14:53:05,055 INFO  Find updates for tyrcho/approvals-scala
[info] 2019-12-03 14:53:18,732 INFO  Ignore org.scala-lang:scala-library : 2.12.10 -> 2.13.0 -> 2.13.1 (reason: ignored globally)
[info] 2019-12-03 14:53:18,732 INFO  Ignore org.scala-lang:scala-library:provided : 2.12.10 -> 2.13.0 -> 2.13.1 (reason: ignored globally)
[info] 2019-12-03 14:53:18,782 INFO  Found 3 updates:
[info]   com.lihaoyi:pprint : 0.5.5 -> 0.5.6
[info]   org.scala-sbt:sbt : 1.3.3 -> 1.3.4
[info]   org.scalatest:scalatest : 3.0.8 -> 3.1.0
[info] 2019-12-03 14:53:18,835 INFO  Process update com.lihaoyi:pprint : 0.5.5 -> 0.5.6
[info] 2019-12-03 14:53:19,050 INFO  Found PR https://gitlab.com/tyrcho/approvals-scala/merge_requests/4
[info] 2019-12-03 14:53:19,215 INFO  PR has no conflict with develop
[info] 2019-12-03 14:53:19,264 INFO  Process update org.scala-sbt:sbt : 1.3.3 -> 1.3.4
[info] 2019-12-03 14:53:20,063 INFO  Found PR https://gitlab.com/tyrcho/approvals-scala/merge_requests/5
[info] 2019-12-03 14:53:20,209 INFO  PR has no conflict with develop
[info] 2019-12-03 14:53:20,231 INFO  Process update org.scalatest:scalatest : 3.0.8 -> 3.1.0
[info] 2019-12-03 14:53:20,386 INFO  Applying migrations: NonEmptyList(Migration(org.scalatest,NonEmptyList(scalatest),Version(3.1.0),NonEmptyList(https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.0.x/rules/src/main/scala/org/scalatest/autofix/v3_0_x/RenameDeprecatedPackage.scala, https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.1.x/rules/src/main/scala/org/scalatest/autofix/v3_1_x/RewriteDeprecatedNames.scala)))
[info] 2019-12-03 14:53:45,331 WARN  Could not apply org.scalatest:scalatest : 3.0.8 -> 3.1.0 : java.io.IOException: 'sbt -batch -no-colors ;scalafixEnable;scalafix https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.0.x/rules/src/main/scala/org/scalatest/autofix/v3_0_x/RenameDeprecatedPackage.scala;test:scalafix https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.0.x/rules/src/main/scala/org/scalatest/autofix/v3_0_x/RenameDeprecatedPackage.scala;scalafix https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.1.x/rules/src/main/scala/org/scalatest/autofix/v3_1_x/RewriteDeprecatedNames.scala;test:scalafix https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.1.x/rules/src/main/scala/org/scalatest/autofix/v3_1_x/RewriteDeprecatedNames.scala' exited with code 1
[info] [info] Loading settings for project global-plugins from scala-steward.sbt,scala-steward-scalafix.sbt ...
[info] [info] Loading global plugins from /Users/michel/.sbt/1.0/plugins
[info] [info] Loading settings for project approvals-scala-build from plugins.sbt ...
[info] [info] Loading project definition from /private/tmp/workspace/repos/tyrcho/approvals-scala/project
[info] [warn] There may be incompatibilities among your library dependencies; run 'evicted' to see detailed eviction warnings.
[info] [info] Loading settings for project approvals-scala from build.sbt ...
[info] [info] Set current project to approvals-scala (in build file:/private/tmp/workspace/repos/tyrcho/approvals-scala/)
[info] [info] Set current project to approvals-scala (in build file:/private/tmp/workspace/repos/tyrcho/approvals-scala/)
[info] [info] Compiling 2 Scala sources to /private/tmp/workspace/repos/tyrcho/approvals-scala/target/scala-2.12/classes ...
[info] [info] Done compiling.
[info] [info] Running scalafix on 2 Scala sources
[info] [success] Total time: 8 s, completed Dec 3, 2019, 2:53:40 PM
[info] [info] Compiling 1 Scala source to /private/tmp/workspace/repos/tyrcho/approvals-scala/target/scala-2.12/test-classes ...
[info] [info] Done compiling.
[info] [success] Total time: 2 s, completed Dec 3, 2019, 2:53:42 PM
[info] [info] Running scalafix on 2 Scala sources
[info] [success] Total time: 2 s, completed Dec 3, 2019, 2:53:44 PM
[info] [info] Compiling 1 Scala source to /private/tmp/workspace/repos/tyrcho/approvals-scala/target/scala-2.12/classes ...
[info] [error] /private/tmp/workspace/repos/tyrcho/approvals-scala/src/main/scala/com/github/writethemfirst/Approbation.scala:7:8: object flatspec is not a member of package org.scalatest
[info] [error] import org.scalatest.flatspec
[info] [error]        ^
[info] [error] /private/tmp/workspace/repos/tyrcho/approvals-scala/src/main/scala/com/github/writethemfirst/Approbation.scala:8:31: object should is not a member of package org.scalatest.matchers
[info] [error] import org.scalatest.matchers.should.Matchers
[info] [error]                               ^
[info] [error] /private/tmp/workspace/repos/tyrcho/approvals-scala/src/main/scala/com/github/writethemfirst/Approbation.scala:10:27: not found: value flatspec
[info] [error] class Approbation extends flatspec.FixtureAnyFlatSpec with Matchers {
[info] [error]                           ^
[info] [error] /private/tmp/workspace/repos/tyrcho/approvals-scala/src/main/scala/com/github/writethemfirst/Approbation.scala:10:60: not found: type Matchers
[info] [error] class Approbation extends flatspec.FixtureAnyFlatSpec with Matchers {
[info] [error]                                                            ^
[info] [error] /private/tmp/workspace/repos/tyrcho/approvals-scala/src/main/scala/com/github/writethemfirst/Approbation.scala:19:34: not found: type OneArgTest
[info] [error]   override def withFixture(test: OneArgTest): Outcome = {
[info] [error]                                  ^
[info] [error] 5 errors found
[info] [error] (Compile / compileIncremental) Compilation failed
[info] [error] Total time: 1 s, completed Dec 3, 2019, 2:53:45 PM
[info] 2019-12-03 14:53:45,455 INFO  Trying heuristic 'moduleId'
[info] 2019-12-03 14:53:45,525 INFO  Create branch update/scalatest-3.1.0
[info] 2019-12-03 14:53:45,544 INFO  Commit and push changes
[info] 2019-12-03 14:53:48,120 INFO  Create PR update/scalatest-3.1.0
[info] 2019-12-03 14:54:21,708 INFO  Created PR https://gitlab.com/tyrcho/approvals-scala/merge_requests/6
[info] 2019-12-03 14:54:21,826 INFO  ──────────── Total time: tyrcho/approvals-scala: 1m 19s 353ms ────────────
[info] 2019-12-03 14:54:21,828 INFO  ──────────── Total time: run: 1m 20s 710ms ────────────


Global errors with sync validation

Hi @erikras. Thanks for your work, redux-form V6 is close to perfection now!
I can't seem to get global errors in my form when I use sync validation:

const validate = formData => {
  const errors = {};
  errors._error = 'No way dude';
  return errors;
};

const MyForm = (props) => {
  const {handleSubmit, error} = props;
  const errorPanel = !error ? null : (<Alert> {error} </Alert> );

  // error is always undefined

  return (
    <Form onSubmit={handleSubmit}>

      {errorPanel}

      <Field component={TextInput} name="code" label="Code"/>
      <Field component={TextInput} name="label" label="Label"/>

      <Button type="submit">Create</Button>
    </Form>
  );
};

export default reduxForm({
  form: 'myForm',
  validate
})(MyForm )

Am I doing this right ?
Since #1292 (awesome BTW) there is a workaround, I can see the error in my redux's state with the dev tools:

So I could use connect to grab the error from redux.
On the other hand, when I use async validation, I have the error prop in my form:
// ugly workaround
const async = () => new Promise(resolve => resolve());

  onSubmit = (formData) => {
    return async()
      .then(() => {
          throw new SubmissionError({_error: 'Dats a global error'})
      })

I would be nice if it worked in both modes.
Moreover, the _error seems to be a somewhat undocumented feature, maybe we should add some doc and/or an example.
I could do that if you want.

+1  I'm trying to set _error in my synchronous validation function as well to no avail.

According to the docs for props.error
A generic error for the entire form given by the _error key in the result from the synchronous validation function, the asynchronous validation, or the rejected promise from onSubmit.

so it just looks like a bug

A quick workaround is you can access is through  this.props.syncErrors which does the trick

@geowarin I have the exact same issue, are you still connecting to the store to retrieve the _error property or did you find another way around?

We are experiencing this as well. It comes in as undefined.

This was fixed by #1560. I will comment again here when it has been released.

Fix published in v6.0.0-rc.5.


Update Functions Host version to 2.0.12888

No updates to 3.0?

I am releasing the new v2 Host. For v3, I think Brett will do another release later this week.


Offline after pairing with Google Home

This week attempted to pair node-matter with Google Home (Nest Mini) and was able to pair but device turns "Offline" (not responding). almost immediately.
I haven't used Google Home with node-matter in a few weeks - only Amazon Alexa.
Something changed?
Using Google Home App (Android) version <IP_ADDRESS>

I see this commonly.  Typically, if I wait a while, it will correct itself and show properly. It might also help to stop and restart Google Home, but that just might be me being impatient :-)

@JimBuzbee  Thanks. I think in another thread you had mentioned that you had run into this same problem.

Google needs a Nest Hub device in the same network. Do you have this? The pairing is done by the Google App on your mobile device and then the communication is done only by the Hub. ALso sometimes the App shows "offline" but then when you  "open" the device the status is there.
If all above do not help please provide node.matter debug putput from pairing and such

Just to update,
In my Google Home App, I have 2 locations, 'Home' and 'Office', so I went to the Home page (as opposed to Office) and was able pair and control node-matter.

Could it be that the "nest mini" is connected to the home "Home"? And "office" do not have a hub?

I believe that 'office' does have a hub.  I haven't explored this sufficiently, I look closer at this.

Finally getting to this. Well, office is in the same network as node-matter. In Google Home sometimes the device goes offline and its sporadic, unfortunately.


Deprecating therubyracer for mini_racer

therubyracer is no longer actively maintained. The old maintainer has recommended using mini_racer instead.
Unfortunately, therubyracer is not compatible with new Apple M1 architecture, whereas mini_racer is.

This is going to be addressed shortly.
My company uses this gem as well and has the same issue with the new computers. Hang tight.

see your https://github.com/gi/handlebars-ruby, I suppose this will be solution this tilt adapter ??
Do you need hand/help test for this ?
We are using it, so we could give some time if need some

sound promising looking at your progress on handlebars engine ;-)
only 4 tests won't paste, but I guess this are issues around
https://github.com/rubyjs/mini_racer/issues/225
and
https://github.com/rubyjs/mini_racer/issues/228

Thanks. I'll have something posted shortly.


F/scheduling details

Description
Task card displays details of scheduling (time, period) instead of "Scheduled" text if the task has been scheduled.

@zguo Please, review


CI should build with clang-15

#342 updated the clang/llvm toolchain used by OID to compile from 12 to 15. Currently OID is still built with clang-12 even though it uses the clang-15 libraries, because the integration tests fail when compiled with clang-15. This should be fixed in the CI and to cause less confusion for external users.

Mostly solved with Nix & #508


Give controller init script responsibility for PID

This moves AppScale service pidfiles to /var/run/appscale. It also speeds up appscale down since monit does not hang waiting for the controller process to stop.

https://ocd.appscale.com:8080/job/Daily Build/3147/
The hawkeye failure was due to a connection timeout.
https://ocd.appscale.com:8080/job/Tools-test/1812/

https://ocd.appscale.com:8080/job/Daily Build/3157/
https://ocd.appscale.com:8080/job/Euca-Faststart/1021/

https://github.com/AppScale/appscale-tools/pull/616


Speed up ParseSymbol by avoiding allocations

TODO cleanups - remove stale benchmarks/update them
Test plan
TODO

I tried running the benchmarks against chromium-1.scip (to compare parsing the same symbols), but it looks like the parser is failing to parse the symbols:
@@ -175,7 +175,11 @@ func TestUtf8Validation(t *testing.T) {
 		var sym Symbol
 		for i := 0; i < b.N; i++ {
 			occ := allOccurrences[i]
-			_ = parsePartialSymbolV2(occ.Symbol, true, &sym)
+			err = parsePartialSymbolV2(occ.Symbol, true, &sym)
+			if err != nil {
+				panic(fmt.Sprintf("Failed to parse '%s' with %s", occ.Symbol, err))
+				// fmt.Printf("Failed to parse '%s' with %s", occ.Symbol, err)
+			}
 		}
 	}
 	stdUtf8ValidationOnly := func(b *simpleBenchmark) {

=== RUN   TestUtf8Validation
--- FAIL: TestUtf8Validation (17.96s)
panic: Failed to parse 'cxx . todo-pkg todo-version `apps/switches.h:6:9`!' with unrecognized descriptor "do-pkg " [recovered]
	panic: Failed to parse 'cxx . todo-pkg todo-version `apps/switches.h:6:9`!' with unrecognized descriptor "do-pkg "


Update the option for docker build

- What I did

Update the option 'network' for docker build
Update the format of squash  for docker build
Update the man document

- How I did it
- How to verify it
- Description for the changelog
Update for keep consistency for docker build
Signed-off-by: yuexiao-wang<EMAIL_ADDRESS>

@AkihiroSuda PTAL
Done!


3D UNet

Modulus Pull Request
Description

Closes https://github.com/NVIDIA/modulus/issues/464
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[x] An issue is linked to this pull request.

Dependencies

/blossom-ci

/blossom-ci

/blossom-ci


Add description for alwaysUsePipeline option to user guide

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/lgtm

Way to go
/approve


Could you please add unescape for ' ' ?

sure, want to do a pr?

@jonschlinkert Still interested in having a PR for this?

Still interested in having a PR for this?

yes, absolutely! sorry for the late reply


getPercentile method returns wrong result

Code in getPercentile method is incorrect. When the length sorted array is 2 and quantile is 75, this method will raise an exception as follows:
java.lang.IllegalArgumentException: Unable to get linear index 2: values is greater than length(2)

Actually, for any sorted array with length n, a large enough percentile will get it out of index.
My current version is 1.0.0-beta6
To fix the problem, getPercentile method should be implemented like follows:
protected double getPercentile(double percentile, ArrayList<Double> sorted) {
    /* In here we assume that quantile is in [0, 100] and array 'sorted' is sorted in ascending order */
    if (1 == sorted.size()) {
        /* This is a boundary case */
        /* The only value should be returned without any doubt */
        return sorted.get(0);
    }
    else if (100 == percentile) {
        /* Another boundary case */
        return sorted.get(sorted.size() - 1);
    }
    else {
        /* I just fixed based on original code, which adopted linear interpolation method */
        /* I also referred to 'percentile' method in 'numpy'. They implemented 5 difference method of interpolation */
        double pos_d = percentile / 100.0 * (sorted.size() - 1);
        double pos_floor = FastMath.floor(pos_d);
        int pos = (int) pos_floor;
        double lower = sorted.get(pos);
        double upper = sorted.get(pos + 1);
        return lower + (pos_d - pos_floor) * (upper - lower);
    }
}

Unfortunately it's not that simple.
We implement algorithm that matches Apache Commons Math, and percentile in edge cases (like like case you've highlighted here) do differ indeed. http://commons.apache.org/proper/commons-math/javadocs/api-3.5/org/apache/commons/math3/stat/descriptive/rank/Percentile.html
But at the same time there was missing condition there. I've fixed it, so thanks for highlighting this problem.


Different client and server versions when installing docker on ubuntu (for the first time).

Hi,
I just tried to install docker, using the installation guidelines given on your homepage. When trying to run the hello world test script I was given this error:
Error response from daemon: client and server don't have same version (client : 1.19, server: 1.18)
I realise that there is a known issue with having a higher version client than server, but you might not be aware that it happens straight after install, at least for me.
docker version:
Client version: 1.7.0 Client API version: 1.19 Go version (client): go1.4.2 Git commit (client): 0baf609 OS/Arch (client): linux/amd64 Error response from daemon: client and server don't have same version (client : 1.19, server: 1.18)
docker info:
Error response from daemon: client and server don't have same version (client : 1.19, server: 1.18)
uname -a:
Linux uwp-cookie-machine 3.13.0-55-generic #92-Ubuntu SMP Sun Jun 14 18:32:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
How reproducible:
I haven't tried reinstalling docker, I'm not invested enough to find out the best way of doing this.
Steps to reproduce:

Install docker:     wget -qO- https://get.docker.com/ | sh
Run hello world test script:    docker run hello-world

Hmmm, something is not right here.
The client and the daemon are distributed as a single binary, as such they use the same API version number.

Maybe I just did something weird when I was doing it, or I dont know. Is there any best practice for reinstalling it? I can have a go and see if I just messed something up.

@mappelgren It seems like the client bin you are executing is different from the one being used to fire up the daemon... so maybe you have something in your $PATH

@cpuguy83 I looked through my path and I only found docker at /usr/bin/docker which is the same as I get when I run which docker. Is that what I'm looking for? Another docker in my $PATH, or would it be called something else?

try a find / -name "docker" and see what shows up

I get the same issue in Windows 7.  I downloaded Boot2Docker within the last few days.  When I double-click Boot2Docker Start, it seems to start up fine.  It errors and says I have client 1.19 and server 1.18 when I execute "docker version" or any other docker command.  When I ssh into the VM with "boot2docker ssh", things work.  In that case, I have client 1.18.  I would prefer to run docker outside of the VM though.

Well I finally figured it out.  My boot2docker.iso was still 1.6.2.  I don't know why.  I deleted it many times and I thought I'd be getting the latest one with "boot2docker init".  Finally I downloaded the latest .iso and used the --iso option with boot2docker init.  I think everything's ok now, but that was pretty frustrating.  I'd be really surprised if the all-in-one Windows installer included an old iso.  I have other problems with boot2docker (e.g. boot2docker download/upgrade), but I think I can get around everything now.  As long as I have a way of running docker in Windows without launching a full-blown VM, I'll bear with it.

I'm going to close this issue, because I think the above tips should help getting this resolved, but feel free to comment here if you think additional measures should be taken :-)


Salsa formatting honours tab vs spaces setting only sometimes?

Testing #2218
I have the following settings:
// Place your settings in this file to overwrite default and user settings.
{
	"typescript.tsdk": "C:\\Alex\\salsa\\node_modules\\typescript\\lib",
	"editor.tabSize": 4,
	"editor.insertSpaces": false
}

If I have a function indented with 5 spaces, and choose format, the 5 spaces get replaced with a tab:
function howdyAgain(name) {
     return 'hi';
}

If I have the same function indented with 4 spaces, and choose format, the 4 spaces do not get replaced with a tab:
function howdyAgain(name) {
    return 'hi';
}

This issue was moved to Microsoft/TypeScript#6667


EDID detection error with Qnix 1440p monitor in Linux

Are you using the latest driver? Yes - 5.5 beta

Are you using the latest EVDI version? Yes, the current devel from Github (1.10)

If you are using a DisplayLink device, have you checked 'troubleshooting'
on DisplayLink's website? - Yes

Is this issue related to evdi/kernel? EVDI I believe

Linux distribution and its version- Ubuntu Budgie 20.04

Linux kernel version - x86_64 Linux 5.11.0-43-generic

Xorg version (if used) - 2:1.20.13-1ubuntu1~20.04.2

Desktop environment in use - Budgie

Hi,
I have a Qnix 1440p monitor connected via dual-link DVI (using an active displayport adapter). This setup works well with Displaylink on Windows, but has trouble on Linux. I receive the following  after connecting the monitor in Ubuntu:

evdi: [E] evdi_painter_connect:864 Wrong edid size. Expected 256 but is 128

I got crafty and modified the evdi_painter.c module to calculate the expected_edid_size by looking at the size of the edid struct only (as that was correctly reported as 128).

expected_edid_size = sizeof(struct edid);

This allowed the monitor to be detected by the OS but at the wrong resolution. I then assigned a resolution via xrandr (using cvt/gtf to generate the Modeline)

xrandr --newmode "qnix2560x1440_60.00"  311.83  2560 2744 3024 3488  1440 1441 1444 1490  -HSync +Vsync
xrandr --output DVI-I-1-1 --mode qnix2560x1440_60.00

Now the monitor is fully working at 1440p 60.
I see my dmesg is clogged with wrong EDID's and warnings.

[ 1014.526113] evdi: [I] (card0) Connector state: connected
[ 1014.526131] [drm] EDID checksum is invalid, remainder is 38
[ 1014.526134] Raw EDID:
[ 1014.526137]  	80 43 02 00 80 07 d8 07 04 08 98 08 00 00 38 04
[ 1014.526141]  	3c 04 41 04 65 04 00 00 05 00 00 00 00 00 00 00
[ 1014.526144]  	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 1014.526146]  	00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00
[ 1014.526149]  	14 08 bd 19 4f ac b5 35 22 01 00 00 00 00 ad de
[ 1014.526152]  	31 39 32 30 78 31 30 38 30 00 00 00 00 00 00 00
[ 1014.526154]  	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 1014.526157]  	00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00
[ 1014.526166] evdi evdi.0: [drm] DVI-I-1: EDID invalid.
[ 1014.526172] evdi: [I] (card0) Edid property set

I am wondering how/why this is happening in Ubuntu but not Windows. I can pull the EDID via the Displaylink adapter in Windows.

00 ff ff ff ff ff ff 00 31 d8 00 00 00 00 00 00
05 16 01 03 6d 42 25 78 ea 5e c0 a4 59 4a 98 25
20 50 54 00 00 00 21 c0 01 01 01 01 01 01 01 01
01 01 01 01 01 01 56 5e 00 a0 a0 a0 29 50 30 20
35 00 9a 77 21 00 00 1e 00 00 00 ff 00 4c 69 6e
75 78 20 23 30 0a 20 20 20 20 00 00 00 fd 00 3b
3d 57 59 19 00 0a 20 20 20 20 20 20 00 00 00 fc
00 32 35 36 30 78 31 34 34 30 0a 20 20 20 00 69

Thank you!

Hi! Thanks for reporting this issue. This seems to be a problem in the most recent firmware. It should be fixed in 5.5 full release.

Wonderful, thank you for the update. Appreciate your help and time.

I have a similar or the same issue. I wonder why this is closed while the 5.5 release is not out. I have it with the current 5.5 beta.
evdi: [E] evdi_painter_connect:875 Wrong edid size. Expected 256 but is 128
also no working second display on both 5.13 and 5.15 kernels with a D6000 dock.

The user closed it, but you're right, I'll reopen it until a fix is released

I'm afraid the firmware fix won't make it into the release. I'll keep pushing, and in the meantime, I'm writing a workaround to alleviate the issue.
FYI, the problem should appear only on DisplayPort connections. HDMI should be fine.

@willstare @VGerris would you mind uploading your failing EDIDs, so that we can verify the fix?

hi @displaylink-emajewsk sure, can you explain exactly what to do? I am running a 5.12 kernel now with the stable driver to have things work. Do I need to run the beta driver and 5.13 or newer kernel or can you post a command that will give you what you need? Thank you

@VGerris sure, the edid files for displays connected to our docks should appear in /var/log/displaylink/

Oh, and yes, please use the stable driver, as the one from the beta would be corrupted. Kernel version shouldn't make a difference

DELL U2414H_DELA0.zip
hi, here there are

@VGerris Oh, good news then! We've already checked this one and it works with the new driver. :)

Is that the one that will be releases? I just checked and saw no newer version : https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu . coming soon :)?

Yes :)

@VGerris Hi. Would you please confirm if the newest driver fixed this issue for you? Many thanks

hi @displaylink-emajewsk , yes it works great, also with 5.15 kernel. I am using the nouveau driver. Thank you very much.
This is on Ubuntu 22.04 (dev) using Wayland.

Sorry, this did resolve my issue!! Thanks!


Move from MailHog to MailPit or a better-maintained mail capture tool

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
MailHog is not actively maintained, and there is an alternative solution.
Describe your solution
Mailpit https://github.com/axllent/mailpit is a new default for laravel/sail and laravel/laravel skeleton from v10.x.
It looks like a drop-in replacement, the ports are the same. DDEV can easily migrate to it as well.
Why replace MailHog? - See README.md, there are several good reasons.
Describe alternatives
Continue to use MailHog.
Additional context
There are many places in DDEV where the word "mailhog" is used - it can be tedious to replace them all.
I suggest just updating this line in the ddev-webserver's Dockerfile.
For start, just keep using mailhog name for binary, but use mailpit repo (create a new fork under DDEV org) under the hood.

One thing that has been suggested over the years is to run mailhog in a different container.
One thing you could do here is create an add-on that uses mailpit (overriding the /etc/supervisor config), and we could get some miles on this.

The mailpit add-on sounds good, I'll give it a try.

@stasadev
I created one last week: https://github.com/tyler36/ddev-mailpit

Mailpit does not have feature-parity with Mailhog at the moment.
One feature that is missing is the ability to "release mail".

@tyler36, thank you!
At first, I didn't find the add-on because I missed this issue

https://github.com/ddev/ddev/issues/4795.

I tested the add-on with symfony/mailer, and it works great!
Closing this issue as resolved.

I don't think this issue should be closed as you are correct, MailHog should be phased out in place of MailPit, is there any internal intention on migrating this into core ddev like MailHog?

The conversation has only just started :)  But as @tyler36 says, "Mailpit does not have feature-parity with Mailhog at the moment."

I think a move to Mailpit would be preferable because it's being actively developed.
"release mail" is a feature that Mailhog has, but Mailpit does not. it is something that I have ever used, but came up on Slack the other day. There's an feature request issue on Mailpit #29.
It would be nice if we had a config option to select Mailhog or Mailpit, similar to database type. Having both as addons is OK, but I think we need this service baked into DDEV out of the box.

Probably the best thing to do is incubate as an add-on, then when we have experience with it, it can be brought into the main DDEV tool.

What are other popular mail capture tools?

MailCapture  is pretty basic and hasn't been updated recently.

There is a list of mail transfer agents, but looking at it, we don't really have a good alternative solution for development.
So the most useful at the moment are MailHog and Mailpit.

Other alternatives to MailHog are:

MailPit ( https://github.com/axllent/mailpit - as already mentioned)
Maildev ( https://github.com/maildev/maildev )
Inbucket ( https://github.com/inbucket/inbucket )
Mailocal ( https://github.com/jfoucher/Mailocal )
Sendria ( https://github.com/msztolcman/sendria )

I only tested MailPit, Maildev an Inbucket via docker-composer.*.yaml in one of my local projects. I was not able to launch Inbucket quickly, so I skipped that. MailPit and Maildev were fast up and running. They both seem to be a good MailHog equivalent, whereas MailPit is written in Go (as MailHog is/ was) and Maildev is a NPM/ NodeJS application.
So, if MailHog should be replaced, then I recommened MailPit as well, which FYI Ian Kent (maintainer of MailHog) does as well:
https://github.com/mailhog/MailHog/issues/442#issuecomment-1493415258

Mailpit does not have feature-parity with Mailhog at the moment. One feature that is missing is the ability to "release mail".

SMTP Relay has been implemented already - see: https://github.com/axllent/mailpit/wiki/SMTP-relay

Soething else that is preventing Mailpit from being the new default?
I don't miss any feature and just love Mailpit in comparison to Mailhog. But it offers nice features like dark mode, attachments, plain text mail preview and built-in caniemail.com checker ❤

@Morgy93
Yes, I'm failing in love with Mailpit and it's continued development.
Is there anything else we can improve on the mailpit addon? https://github.com/tyler36/ddev-mailpit

Something else that is preventing Mailpit from being the new default? I don't miss any feature and just love Mailpit in comparison to Mailhog. But it offers nice features like dark mode, attachments, plain text mail preview and built-in caniemail.com checker ❤

We recently noticed that its REST API is different. Not sure if this is a deal-breaker though.

Something else that is preventing Mailpit from being the new default?

Well, nobody has proposed a migration technique or done a PR to implement it. I'm glad that people like it, and are using https://github.com/tyler36/ddev-mailpit
I think maybe the first step toward mailpit would be to promote it to the ddev org. What do you think @tyler36 ?

It is easy to replace MailHog with Mailpit.
The only change needed here:
https://github.com/ddev/ddev/blob/e0b1772bc209dc68ae4c4198f105e8e004b45d4b/containers/ddev-webserver/Dockerfile#L100
Can be tested locally:
echo 'ARG TARGETPLATFORM="linux/amd64"
ENV MAILPIT_VERSION="1.8.2"
RUN set -x \
    && curl --fail -sSL "https://github.com/axllent/mailpit/releases/download/v${MAILPIT_VERSION}/mailpit-linux-${TARGETPLATFORM##linux/}.tar.gz" -o /tmp/mailpit.tar.gz \
    && mkdir -p /tmp/mailpit-unpacked \
    && tar -xzvf /tmp/mailpit.tar.gz -C /tmp/mailpit-unpacked \
    && mv /tmp/mailpit-unpacked/mailpit /usr/local/bin/mailhog \
    && chmod +x /usr/local/bin/mailhog \
    && rm -rf /tmp/mailpit*' > .ddev/web-build/Dockerfile

Well, there's docs changes as well, and changes to the launch command, and then there's the discussion about whether mailpit should run in its own container instead of on the ddev-webserver.

Yes, I just provided what I talked about in the first post of this issue.
Also, I really like the idea of an add-on because it has so many customization options.

Also, I really like the idea of an add-on because it has so many customization options.

Do you think it should remain in core DDEV or are you saying it should become just and add-on? Of course mailhog already has the same customization options.

I mean, it's easier to see what can be changed by looking at the add-on config.
On the other hand, I won't even change the default config since I use it as a simple email viewer.
My opinion: it should remain in the core DDEV.

Thanks. What's your opinion about whether it should remain in ddev-webserver?  That's certainly the simplest path forward as far as code.

then there's the discussion about whether mailpit should run in its own container instead of on the ddev-webserver.

Personally, I lean towards running in it's own container. It's much easier to debug and disable services when they are isolated. With addons, if it's in the web container and theres a problem, it can prevent the web-container from starting.
I'm happy to go with the crowd though.

With addons, if it's in the web container and theres a problem, it can prevent the web-container from starting

I don't think this has happened with mailhog in the entire history of DDEV though...

Three people, three different opinions. 😅
I like the idea of removing Mailhog from the core and using add-ons instead.
It's much more flexible and one could provide an add-on for every other "option" out there. Just as reminder:

Mailhog ( https://github.com/mailhog/MailHog )
MailPit ( https://github.com/axllent/mailpit )
Maildev ( https://github.com/maildev/maildev )
Inbucket ( https://github.com/inbucket/inbucket )
Mailocal ( https://github.com/jfoucher/Mailocal )
Sendria ( https://github.com/msztolcman/sendria )
(Probably more, thanks to @EvilBMP for the list)

Currently, no real "drop-in replacement" is possible, because of the bundled Mailhog. (Global command, ports etc.)
And if Mailpit is abandoned we don't have to care about the bundled package anymore. 😁

I like the idea of removing Mailhog from the core and using add-ons instead.

@Morgy93 Yes, that what I was thinking.

I think having working e-mail handling out of the box with DDEV is a very valuable feature and making it an optional addon would require everyone to always get that addon in a project before that works? It being on a separate container also requires to configure your application to send mails via smtp to that host, whereas it just works right now for example with Drupal.

I think having working e-mail handling out of the box with DDEV is a very valuable feature and making it an optional addon would require everyone to always get that addon in a project before that works

You're right! I've been using DDEV for so long I've gotten use to the idea that tests email are capture and I don't end up spaming<EMAIL_ADDRESS>with alerts and logs.

Yes, the reason DDEV had mailhog from the beginning was to try to prevent escaping emails!

Yes, the reason DDEV had mailhog from the beginning was to try to prevent escaping emails!
I think that is an important feature. I know of two situations where this is life saving.

Your setup requires different unique email addresses following a specific scheme (like a Drupal site with multiple user accounts with different roles for testing all perspectives and evtl. a domain restriction for email addresses). And not all providers or email servers support addresses of the form<EMAIL_ADDRESS>like Google does.
You need to clone a production site for preparing migration tests of new features to it, but can't clean up the databases etc. and replace real addresses with test addresses on the production server for whatever reasons. As of now by just importing the production data into the local DDEV instance and cleanup there you can be sure no email will escape to a real recipient.

Working on this!

Please test and review:

https://github.com/ddev/ddev/pull/5313#issuecomment-1701826686

ddev launch -m does not work. It simply opens the default DDEV project URL without the port. Opening the default DDEV project url with the correct port (as mentioned in ddev status) works correctly though.
Sending mails to localhost:1025 in the web container works as expected and shows them in Mailpit.

@EvilBMP, everything is good on my end.
$ DDEV_DEBUG=true ddev launch -m
FULLURL https://my.ddev.site:8026

Maybe your browser removes the port before opening the link?

@EvilBMP you do have to ddev restart for the new version of the launch command to be installed. It's also possible you have an old launch somewhere besides ~/.ddev/commands/host.

This is now in HEAD


Android & iOS - Manage members screen is blank

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app in a Android or iOS device
Navigate to Edit Workspace settings
Click on manage members

Expected Result:
Manage members screen is fully rendered
Actual Result:
Manage members screen is blank on mobile devices.
Workaround:
None found in Android / iOS.
Platform:

Where is this issue occurring?

Android

Version Number: 1.1.17-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @Santhosh-Sellavel
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1638132040029300
View all open jobs on GitHub

Triggered auto assignment to @tgolen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Triggered auto assignment to @Christinadobrzyn (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Hum, I don't see the same thing on my NewDot app - here are the steps I took

Open the app on iOS device
Tap my my profile > tap C.dobrzyn's workspace
Tap on manage members and I see my admin displayed:

Running v1.1.17-4
@Santhosh-Sellavel can try again with an update version - v1.1.17-4 - to see if you see the same thing?

Yep working fine, I was able to reproduce in version <IP_ADDRESS> or earlier!
But how

Ah great! It seems like there have been several updates over the past 24 hours so I assume something in those updates resolved this. However, I remember always seeing the admin in the previous version so maybe something was in the middle of an update when you caught this.
We're good to close this?

Its good that its resolved now, we can close this one!

Yup this was a regression and taken care of before this issue was created. I think we are good to close.

Reopening this - This is still happening on Android app on version 1.1.17-4

Yep, it is still reproducible. My bad I didn’t verify in android earlier!

Ah, thanks for clarifying @isagoico and @Santhosh-Sellavel!
Created Upwork job
Internal - https://www.upwork.com/ab/applicants/1466605040031260672/job-details
External - https://www.upwork.com/jobs/~01c043b2222fa54500
Hired @Santhosh-Sellavel for reporting - waiting on proposals for the fix!

Triggered auto assignment to @parasharrajat (Exported)

Current assignee @tgolen is eligible for the Exported assigner, not assigning anyone new.

Issue occurs again in iOS again in version <IP_ADDRESS> @puneetlath reported in slack thread

It seems that getFullPolicy https://github.com/Expensify/App/blob/d279c8abf165af6b04032593e99901fe6328b90f/src/pages/workspace/withFullPolicy.js#L93 call is failing for some reason. I am not able to inspect the request in the network. Or don't know how to do that in Flipper.

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Adding the deploy blocker here - this issue is failing PR https://github.com/Expensify/App/pull/6542 in the current regression checklist for iOS and Android.

I'm a little confused. That PR is linked to a different issue: https://github.com/Expensify/App/issues/6287. Was this issue marked as a blocker by mistake to this issue?

@tgolen Nope. Marked this issue as deploy blocker because it's completely blocking us from verifying QA on iOS and Android for this PR https://github.com/Expensify/App/issues/6287.
We usually mark issues that are blocking and/or failing the QA of PRs as deploy blockers.

Oh! I understand now. Got it. Looks like we're still looking for proposals to fix this.

It looks like the employeeList that is being sent back is different on iOS/Android compared to web. On web, the employeeList contains all the employees but on mobile it does not, it just contains the user email. I looked into the logs for this and it seems like the Get request we make for policyIDList in this call is coming up as an empty string on the API side when called from mobile, but when it is called from web it is the correct value.
I'm not sure what is causing this yet, but there's a chance it requires a back end fix so leaving some internal logs here:

Mobile logs (policyIDList is empty)
Web logs (policyIDList has value)

also that the data here is an empty array on Android:
https://github.com/Expensify/App/blob/04d28afec2f090aa23fbca496671ba3d2214003f/src/pages/workspace/WorkspaceMembersPage.js#L248
But not on web.

Can see the employeeList getting returned in Flipper when making the request on Android:

Removed the posting from Upwork since this is being handled internally

This qualifies for reporting bonus right?
@Jag96 or @Christinadobrzyn

@Santhosh-Sellavel correct! I've created an upwork posting for that here and hired you for the job!

I'll keep an eye on this PR and pay @Santhosh-Sellavel at our 7 day after production payment timeframe.

I just notices, there are two active contracts for the same job. cc: @Christinadobrzyn Can you end one contract?

Thanks for letting me know @Santhosh-Sellavel! I think I cancelled one of the contracts but Upworks isn't loading to show which one was cancelled. You might get a message in Upwork about it.
Either way, I will track both of these and make sure to pay you for one of them after the production deployment.

Hey @Santhosh-Sellavel sorry for the delay with this - I just paid you for reporting this in this job. Thanks!
https://www.upwork.com/ab/applicants/1466605040031260672/job-details


add @ljharb/through to the list of allowed deps

For reference, which DT PR requires this to pass?

My latest push to https://github.com/DefinitelyTyped/DefinitelyTyped/pull/71256 :-)


Invariant Violation: requireNativeComponent: "RCTImageView" was not found in the UIManager.

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Run react-native info in your terminal and paste its contents here.
React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
      Memory: 115.80 MB / 6.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 11.0.0 - /usr/local/bin/node
      Yarn: 1.10.0 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    IDEs:
      Android Studio: 3.1 AI-173.4819257
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.3 => 16.6.3
      react-native: 0.57.8 => 0.57.8
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

Description
there is my logs, and the current react-native version is 0.57.8, in the pod file, also write with 'RCTImage', as for those,  how can i resolve this problem
this is log of the simulator
Invariant Violation: requireNativeComponent: "RCTImageView" was not found in the UIManager.

This error is located at:
    in RCTImageView (at Image.ios.js:104)
    in ForwardRef(Image) (at react-chatail/index.js:24)
    in RCTView (at View.js:45)
    in View (at react-chatail/index.js:21)
    in RNHighScores (at renderApplication.js:34)
    in RCTView (at View.js:45)
    in View (at AppContainer.js:98)
    in RCTView (at View.js:45)
    in View (at AppContainer.js:115)
    in AppContainer (at renderApplication.js:33)

getNativeComponentAttributes
    getNativeComponentAttributes.js:29:4
get
    ReactNativeViewConfigRegistry.js:104:25
createInstance
    ReactNativeRenderer-dev.js:3946:53
completeWork
    ReactNativeRenderer-dev.js:13386:12
completeUnitOfWork
    ReactNativeRenderer-dev.js:15893:10
performUnitOfWork
    ReactNativeRenderer-dev.js:16103:30
workLoop
    ReactNativeRenderer-dev.js:16115:41
renderRoot
    ReactNativeRenderer-dev.js:16219:15
performWorkOnRoot
    ReactNativeRenderer-dev.js:17198:17
performWork
    ReactNativeRenderer-dev.js:17099:24
performSyncWork
    ReactNativeRenderer-dev.js:17060:14
requestWork
    ReactNativeRenderer-dev.js:16925:19
scheduleWork
    ReactNativeRenderer-dev.js:16724:16
scheduleRootUpdate
    ReactNativeRenderer-dev.js:17413:15
render
    ReactNativeRenderer-dev.js:18191:20
renderApplication
    renderApplication.js:59:34
run
    AppRegistry.js:101:10
runApplication
    AppRegistry.js:195:26
__callFunction
    MessageQueue.js:349:47
<unknown>
    MessageQueue.js:106:26
__guard
    MessageQueue.js:297:10
callFunctionReturnFlushedQueue
    MessageQueue.js:105:17

those are some pictures of the issue

why closed my issue, as for this issue i can't solve, so hope them to help me

I had a similar issue.  I resolved it by

Making sure pod install was run after updating my Podfile
Ensuring that RCTImage was included in the Xcode project verified via search within the Pod directory
Making sure the name of the build target in Xcode matches the app.json name which also matches the target of your Podfile.

Hope it helps!

There is additional information about this problem in android, here: https://stackoverflow.com/questions/55532052/invariant-violation-requirenativecomponent-rctview-was-not-found-in-the-uima
Copying from this link:
The problem
When i start remote js debugging from the dev menu and reload my react-native app in the android simulator this error appears
Workaround
I experienced this on Android when I tried to start remote JS debugging while JS Dev Mode was turned off. I fixed it by going to the Dev Settings menu and re-enabling dev mode.
Does anybody have an idea about why this happens?

I have same issue:
my env info:::>
React Native Environment Info:
System:
OS: macOS 10.14.4
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 55.31 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.3 - /usr/local/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
IDEs:
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: ^0.59.8 => 0.59.8
npmGlobalPackages:
react-native-cli: 2.0.1
error message i am seeing, at browser dev tool and at simulator ::::>
Unhandled JS Exception: Invariant Violation: requireNativeComponent: "RCTImageView" was not found in the UIManager.
This error is located at:
in RCTImageView (at Image.ios.js:115)
in Image (at NewSession.js:58)
in RCTView (at View.js:45)
in View (at NewSession.js:57)
in RCTView (at View.js:45)
in View (at KeyboardAvoidingView.js:200)
in KeyboardAvoidingView (at NewSession.js:55)
in NewSession (created by ConnectFunction)
in ConnectFunction (at steps.js:96)
in StepManager (created by ConnectFunction)
in ConnectFunction (at Login.js:23)
in RCTView (at View.js:45)
in View (at Login.js:21)
in Login (at views.js:8)
in RCTView (at View.js:45)
in View (at ViewManager.js:13)
in ViewManager (created by ConnectFunction)
in ConnectFunction (at App.js:21)
in RCTView (at View.js:45)
in View (at App.js:20)
in Provider (at App.js:19)
in App (at renderApplication.js:35)
in RCTView (at View.js:45)
in View (at AppContainer.js:98)
in RCTView (at View.js:45)
in View (at AppContainer.js:115)
in AppContainer (at renderApplication.js:34)
reactConsoleErrorHandler @ 7e954ad7-bf1f-414a-b…-5e70fd596c9c:27283
console.error @ 7e954ad7-bf1f-414a-b…-5e70fd596c9c:68243
logToConsole @ 7e954ad7-bf1f-414a-b…-5e70fd596c9c:32780
logIfNoNativeHook @ 7e954ad7-bf1f-414a-b…-5e70fd596c9c:32763
__callFunction @ 7e954ad7-bf1f-414a-b…a-5e70fd596c9c:7265
(anonymous) @ 7e954ad7-bf1f-414a-b…a-5e70fd596c9c:7022
__guard @ 7e954ad7-bf1f-414a-b…a-5e70fd596c9c:7219
callFunctionReturnFlushedQueue @ 7e954ad7-bf1f-414a-b…a-5e70fd596c9c:7021
(anonymous) @ debuggerWorker.js:80
7e954ad7-bf1f-414a-b…-5e70fd596c9c:32984 BugReporting extraData: {AppRegistry.runApplication1: "Running application "myApp" with appParams: …warning are ON, performance optimizations are OFF"}
7e954ad7-bf1f-414a-b…-5e70fd596c9c:32984 BugReporting extraData: {AppRegistry.runApplication1: "Running application "myApp" with appParams: …warning are ON, performance optimizations are OFF"}


fix: install the latest custom Webpack package version

Closes #306

It seems the workaround with latest version 10.0.1 does not work. I am gathering the data, but it should be better not to merge this. Please see #307.


Update fr/messages.po

Blind update, as I didn't find where some of the new fields are shown.

Thank you!


updated changes from PR #1640, without the merge conflicts...

I cannot fix #1640 directly, since I don't have write permissions.
But here is a new version of the PR, with the tst_h_vars2.c conflicts resolved. @brtnfld if you want to update your PR with the tst_h_vars2.c from this PR, then I will take this PR down.
Fixes #1628

I have no issues with using this PR instead. Thanks.

I will take this down until the filter work gets straitened out. This touches some of the same code files...


factory: createExpressionStatement is internal

Search Terms
createExpressionStatement

Suggestion
expose createExpressionStatement for API users

I just noticed that there is a createStatement which creates an ExpressionStatement. This is actually consistent with the inconsistencies of all the other factory functions.
Maybe the misnamed functions should be deprecated in favour of functions with a better name.

PRs welcomed.

I would expose both with a comment.