Hanging on parsing

Tried jupyter-forward for the first time on our USGS HPC machine.   Was looking good, but then hung on the line:
 Parsing $HOME/.jupyter_forward/log_2022-03-21T07-51-39.txt log file on denali.cr.usgs.gov for jupyter information

Full output:
$ jupyter-forward rsignell@denali --launch-command "srun -A woodshole -N 1 -t 00:30:00" --conda-env pangeo --port 8889
**************************************************** Authenticating ****************************************************Authenticating user (rsignell) from client (IGSAGIEGLTRSI10) to remote host (denali.cr.usgs.gov)
✅ The client is authenticated successfully
*********************************************** Verifying shell location ***********************************************✅ Using shell: /bin/bash
******************************************** Running jupyter sanity checks *********************************************/bin/bash -lc "source activate pangeo && which jupyter"
/home/rsignell/miniconda3/bin/jupyter
***************************************  Creating log file on denali.cr.usgs.gov ***************************************/bin/bash -lc "printenv TMPDIR"
/bin/bash -lc "printenv HOME"
/home/rsignell
/bin/bash -lc "touch $HOME/foobar && rm -rf $HOME/foobar && echo '$HOME is WRITABLE' || echo '$HOME is NOT WRITABLE'"
/home/rsignell is WRITABLE
/bin/bash -lc "mkdir -p $HOME/.jupyter_forward"
✅ Log directory is set to $HOME/.jupyter_forward
/bin/bash -lc "touch $HOME/.jupyter_forward/log_2022-03-21T07-51-39.txt"
✅ Log file is set to $HOME/.jupyter_forward/log_2022-03-21T07-51-39.txt
********************************************** Preparing Batch Job script **********************************************/bin/bash -lc "echo -n '#!' > $HOME/.jupyter_forward/batch_job_script_2022-03-21T07-51-39"
/bin/bash -lc "echo /bin/bash -l >> $HOME/.jupyter_forward/batch_job_script_2022-03-21T07-51-39"
/bin/bash -lc "echo 'source activate pangeo && jupyter lab --no-browser --ip=\$(hostname -f) > $HOME/.jupyter_forward/log_2022-03-21T07-51-39.txt 2>&1' >> $HOME/.jupyter_forward/batch_job_script_2022-03-21T07-51-39"
/bin/bash -lc "chmod +x $HOME/.jupyter_forward/batch_job_script_2022-03-21T07-51-39"
✅ Batch Job script resides in $HOME/.jupyter_forward/batch_job_script_2022-03-21T07-51-39
************************************************ Launching Jupyter Lab *************************************************/bin/bash -c "srun -p compute -N 1 -t 00:30:00 $HOME/.jupyter_forward/batch_job_script_2022-03-21T07-51-39"
🌨   Parsing $HOME/.jupyter_forward/log_2022-03-21T07-51-39.txt log file on denali.cr.usgs.gov for jupyter information   **************************** ❌ Terminated the network 📡 connection to denali.cr.usgs.gov *****************************

The log file looks like:
#!/bin/bash -l
source activate pangeo && jupyter lab --no-browser --ip=$(hostname -f) > /home/rsignell/.jupyter_forward/log_2022-03-21T
08-27-02.txt 2>&1

Hey, @rsignell-usgs!  What's in the $HOME/.jupyter_forward/batch_job_script_2022-03-21T07-51-39 file on denali?

And what about $HOME/.jupyter_forward/log_2022-03-21T07-51-39.txt?

@andersy005, I tried it -- no go:
$  jupyter-forward rsignell@denali  --conda-env pangeo --port 8889
**************************************************** Authenticating ****************************************************
Authenticating user (rsignell) from client (IGSAGIEGLTRSI10) to remote host (denali.cr.usgs.gov)
✅ The client is authenticated successfully
*********************************************** Verifying shell location ***********************************************
✅ Using shell: /bin/bash
******************************************** Running jupyter sanity checks *********************************************
/bin/bash -lc "source activate pangeo && which jupyter"
/home/rsignell/miniconda3/bin/jupyter
***************************************  Creating log file on denali.cr.usgs.gov ***************************************
/bin/bash -lc "printenv TMPDIR"
/bin/bash -lc "printenv HOME"
/home/rsignell
/bin/bash -lc "touch $HOME/foobar && rm -rf $HOME/foobar && echo '$HOME is WRITABLE' || echo '$HOME is NOT WRITABLE'"
/home/rsignell is WRITABLE
/bin/bash -lc "mkdir -p $HOME/.jupyter_forward"
✅ Log directory is set to $HOME/.jupyter_forward
/bin/bash -lc "touch $HOME/.jupyter_forward/log_2022-03-22T12-40-09.txt"
✅ Log file is set to $HOME/.jupyter_forward/log_2022-03-22T12-40-09.txt
nid00038
************************************************ Launching Jupyter Lab *************************************************
/bin/bash -c "source activate pangeo && jupyter lab --no-browser --ip=nid00038 > $HOME/.jupyter_forward/log_2022-03-22T12-40-09.txt 2>&1"

And then it says it's parsing the log file, but the log file is empty.
I'd be happy to screenshare/debug this.

Thanks for trying!

I'd be happy to screenshare/debug this.

I am available in the afternoon (2pm - 3pm Mountain Time).
In the meantime, do you mind downgrading to jupyter-forward v2022.1.15 and trying again? I'm starting to think that the log redirection changes introduced in #138 may have inadvertently broken other things.

Tried the 2022.1.15 version, but still hanging on:
⛈  Parsing $HOME/.jupyter_forward/log.2022-03-22T13-12-21 log file on denali.cr.usgs.gov for jupyter information

I could meet at 4pm ET = 2pm Mountain.   I'll send you a calendar invite.

I'd be happy to join the call as well, if that would be useful.

@rsignell-usgs

I could meet at 4pm ET = 2pm Mountain. I'll send you a calendar invite.

Did you send the invite to my UCAR address? I'm no longer employed at NCAR and that email account has been disabled

We could use https://whereby.com/pangeo

How did this go?

I'll try it in a few minutes. My daughter is sick today, though, so I may not have much time.

I can verify that it hangs when trying to launch a JLab on Cheyenne.

I am going to try looking more closely at this today, assuming I have time.

I'll try it in a few minutes. My daughter is sick today, though, so I may not have much time.

Thank you for looking into this, @kmpaul! I hope she is feeling better

Thanks, @andersy005!  My daughter bounced back to life last night at 3:30am.  😄  So, I'm a bit tired, but everyone is well.

I have some time now if we want to try live debug

I'm running to get some lunch.  Let me ping you in about 10 minutes.

Ok.  I'm now looking at this.  I'm not sure I know how to diagnose the problem, yet.  Hold on.

I've reproduced the problem on my end, and it appears to be caused by jupyter lab --no-browser command ending early.  So, when the parsing of the log file starts, the log file is empty and remains empty.

@kmpaul that's great news for me -- means it not must a weird problem with our system!   So is there anything I can do to help, or just wait?

Well, at this point, I think it's a "just wait" thing.  I can't seem to figure out why the jupyter lab command is exiting early.  I'm trying to reproduce the entire workflow with straight SSH right now.

@rsignell-usgs and @kmpaul, which version of jupyterlab are you running on the remote machine? I'm asking because I am unable to reproduce the issue using the following versions:
$ jupyter --version
Selected Jupyter core packages...
IPython          : 8.0.1
ipykernel        : 6.9.1
ipywidgets       : 7.6.5
jupyter_client   : 7.1.2
jupyter_core     : 4.9.2
jupyter_server   : 1.13.5
jupyterlab       : 3.2.9
nbclient         : 0.5.11
nbconvert        : 6.4.2
nbformat         : 5.1.3
notebook         : 6.4.8
qtconsole        : not installed
traitlets        : 5.1.1

I am using:
(pangeo) kpaul@cheyenne2:~> jupyter --version
Selected Jupyter core packages...
IPython          : 8.1.1
ipykernel        : 6.9.2
ipywidgets       : not installed
jupyter_client   : 7.1.2
jupyter_core     : 4.9.2
jupyter_server   : 1.15.6
jupyterlab       : 3.3.2
nbclient         : 0.5.13
nbconvert        : 6.4.4
nbformat         : 5.2.0
notebook         : 6.4.10
qtconsole        : not installed
traitlets        : 5.1.1

What version of paramiko and fabric are you using, @andersy005?

I am using fabric 2.6.0 and paramiko 2.10.3.

# Name                    Version                   Build  Channel
fabric                    2.6.0              pyhd8ed1ab_1    conda-forge
paramiko                  2.10.3             pyhd8ed1ab_0    conda-forge

What shell are you using on the remote system, @andersy005?

For me, it seems to be due to the Jupyter launch command being run with /bin/bash -c instead of /bin/bash -lc.

If I run the full command:
/bin/bash -c "conda activate pangeo && jupyter lab --no-browser --ip=cheyenne2.cheyenne.ucar.edu > $TMPDIR/.jupyter_forward/log_2022-03-24T13-28-45.txt 2>&1"

with vanilla SSH, it errors out saying that it can't find conda.  But if I change the command to:
/bin/bash -lc "conda activate pangeo && jupyter lab --no-browser --ip=cheyenne2.cheyenne.ucar.edu > $TMPDIR/.jupyter_forward/log_2022-03-24T13-28-45.txt 2>&1"

It works fine.  Makes sense.  You need a login shell to activate conda, right?

That's very weird. How is it that running /bin/bash -c "conda activate" works for you without the -lc flag?

That's very weird. How is it that running /bin/bash -c "conda activate" works for you without the -lc flag?

I thought

The -l flag controls whether or not .bash_profile is sourced, but .bashrc is always sourced
conda was initialized in .bashrc

For me, I know (2) is true -- the following is in .bashrc:
# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/glade/work/mlevy/miniconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/glade/work/mlevy/miniconda3/etc/profile.d/conda.sh" ]; then
        . "/glade/work/mlevy/miniconda3/etc/profile.d/conda.sh"
    else
        export PATH="/glade/work/mlevy/miniconda3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<

Okay.  I just reverted my versions of jupyter to the following:
Selected Jupyter core packages...
IPython          : 8.1.1
ipykernel        : 6.9.2
ipywidgets       : not installed
jupyter_client   : 7.1.2
jupyter_core     : 4.9.2
jupyter_server   : 1.13.5
jupyterlab       : 3.2.9
nbclient         : 0.5.13
nbconvert        : 6.4.4
nbformat         : 5.2.0
notebook         : 6.4.10
qtconsole        : not installed
traitlets        : 5.1.1

And it still fails for me.  So, I don't think it has anything to do with the versions of jupyter on the remote system.

@mnlevy1981:  For me, I am using the system conda module, but the module load conda is being done in .bashrc.  So, I think we are both initializing conda in the same place.
However, it still doesn't explain my experiment.  Try running (from your laptop) the following command:
ssh<EMAIL_ADDRESS>'/bin/bash -c "conda activate"'

and then run
ssh<EMAIL_ADDRESS>'/bin/bash -lc "conda activate"'

The first version (without the -l) fails for me with:
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
To initialize your shell, run

    $ conda init <SHELL_NAME>

Currently supported shells are:
  - bash
  - fish
  - tcsh
  - xonsh
  - zsh
  - powershell

See 'conda init --help' for more information and options.

IMPORTANT: You may need to close and restart your shell after running 'conda init'.

Okay.  Just so we can verify what SSH is doing, I did an experiment to see what files are being executed on the remote system.  I added echo "READING BASHRC FILE" to my ~/.bashrc and echo "READING PROFILE" to my ~/.profile.  Then I ran the previous two commands:
~> ssh<EMAIL_ADDRESS>'/bin/bash -c "conda activate"'
Token_Response:
READING BASHRC FILE

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
To initialize your shell, run

    $ conda init <SHELL_NAME>

Currently supported shells are:
  - bash
  - fish
  - tcsh
  - xonsh
  - zsh
  - powershell

See 'conda init --help' for more information and options.

IMPORTANT: You may need to close and restart your shell after running 'conda init'.

And then:
~> ssh<EMAIL_ADDRESS>'/bin/bash -lc "conda activate"'
Token_Response:
READING BASHRC FILE
READING BASHRC FILE
READING PROFILE

So, it is loading the .bashrc file both times.  (And, just for clarification, my .profile file is basically empty except for the echo command.)  With the -l option, it loads it twice.
So, something tells me that this must have something to do with using LMOD instead of a hand-installed miniconda.

@mnlevy1981: For me, I am using the system conda module, but the module load conda is being done in .bashrc. So, I think we are both initializing conda in the same place.
However, it still doesn't explain my experiment. Try running (from your laptop) the following command:
ssh<EMAIL_ADDRESS>'/bin/bash -c "conda activate"'

and then run
ssh<EMAIL_ADDRESS>'/bin/bash -lc "conda activate"'

Oh, weird - I get the errors with -c but not with -lc as well... and I get the same behavior (-lc works, -c does not) on casper, which is really bizarre because I definitely tested the latest jupyter-forward code by running it on casper.
Regardless, isn't the latest version using -lc for everything except csh and tcsh? https://github.com/ncar-xdev/jupyter-forward/blob/main/jupyter_forward/core.py#L127
        if 'csh' in self.shell:
            command = f'''{self.shell} -c "{command}"'''
        else:
            command = f'''{self.shell} -lc "{command}"'''

Unless the initial conda call isn't using run_command...

No.  There is a separate call on line 198:
https://github.com/ncar-xdev/jupyter-forward/blob/8e34462600699cae6e4a4bacbd31bfd35ab7af29/jupyter_forward/core.py#L198

@mnlevy1981: For me, I am using the system conda module, but the module load conda is being done in .bashrc. So,
Unless the initial conda call isn't using run_command...

Yep.  You guessed it.  😄

Seems like line 198 should be refactored to use run_command with the appropriate kwargs.

No. There is a separate call on line 198:
https://github.com/ncar-xdev/jupyter-forward/blob/8e34462600699cae6e4a4bacbd31bfd35ab7af29/jupyter_forward/core.py#L198

So it looks like the solution is to modify that line
-  self.session.run(f'{self.shell} -c "{command}"', asynchronous=True, pty=True, echo=True)
+  self.run_command(command, asynchronous=True, pty=True, echo=True)

?

Yeah.  😄

I'm glad you were able to reproduce the error without using LMOD.  I was starting to think it had to have something to do with that...  Phew!

@mnlevy1981:  I don't think that change will work because of the asynchronous=True argument.  I think you cannot use run_command in this case.

Or, rather, you need to refactor the run_command to work with asynchronous execution.

Another option is to do something like
        if 'csh' in self.shell:
            self.run_shell = f"{self.shell} -c"
        else:
            self.run_shell = f"{self.shell} -lc"

in _check_shell() and then both run_command() and _launch_jupyter() could rely on f'{self.run_shell} "{command}"'

(or a self._get_run_command() function that returns the proper string)

Yeah.  That might work.  I frankly don't know why run_command(command, asynchronous=True) fails.  It gives this error:
'Promise' object has no attribute 'exited'

At no point does the Jupyter-Forward code reference an exited attribute.

Not sure if this is related but we do use the failed attribute here
https://github.com/ncar-xdev/jupyter-forward/blob/8e34462600699cae6e4a4bacbd31bfd35ab7af29/jupyter_forward/core.py#L131-L132

Yeah.  You got it, @andersy005.  out.failed is a parameter method that executes a call sequence that eventually accesses out.exited, which is not defined on a Promise (only on a Result).

So, I think the proper solution to this is to change the run_command() function like so:
    def run_command(
        self,
        command,
        exit=True,
        warn=True,
        pty=True,
-       hide=None,
        echo=True,
+       asynchronous=False,
        **kwargs,
    ):
        if 'csh' in self.shell:
            command = f'''{self.shell} -c "{command}"'''
        else:
            command = f'''{self.shell} -lc "{command}"'''
-       out = self.session.run(command, warn=warn, pty=pty, hide=hide, echo=echo, **kwargs)
-       if out.failed and exit:
+       out = self.session.run(command, warn=warn, pty=pty, echo=echo, asynchronous=asynchronous, **kwargs)
+       if not asynchronous and exit and out.failed:
            sys.exit(1)
        return out

NOTE: The hide parameter can be removed because it defaults to the same default assumed by invoke's run method.
And then we can change L198 as you suggested @mnlevy1981:
-  self.session.run(f'{self.shell} -c "{command}"', asynchronous=True, pty=True, echo=True)
+  self.run_command(command, asynchronous=True)

This should fix the problem.  Agreed?  Does anyone see any problems with this?  If not, then I'll craft a PR.

I've started #152 to fix this.

Hi,
I am getting the same error...jupyter-forward hangs on parsing. It was working well until Thursday-friday last week. I tried the

@mnlevy1981: For me, I am using the system conda module, but the module load conda is being done in .bashrc. So, I think we are both initializing conda in the same place.
However, it still doesn't explain my experiment. Try running (from your laptop) the following command:
ssh<EMAIL_ADDRESS>'/bin/bash -c "conda activate"'

and then run
ssh<EMAIL_ADDRESS>'/bin/bash -lc "conda activate"'

Oh, weird - I get the errors with -c but not with -lc as well... and I get the same behavior (-lc works, -c does not) on casper, which is really bizarre because I definitely tested the latest jupyter-forward code by running it on casper.
Regardless, isn't the latest version using -lc for everything except csh and tcsh? https://github.com/ncar-xdev/jupyter-forward/blob/main/jupyter_forward/core.py#L127
        if 'csh' in self.shell:
            command = f'''{self.shell} -c "{command}"'''
        else:
            command = f'''{self.shell} -lc "{command}"'''
`

Unless the initial `conda` call isn't using `run_command`...

And I get the same error. With -lc works, with -c it fails.
On the Local machine:

(base) aliraloarca@wilson ~ % jupyter-forward --version

[Jupyter Forward CLI Version: 2022.9.10
(base) aliraloarca@wilson ~ % jupyter --version
Selected Jupyter core packages...
IPython          : 8.17.2
ipykernel        : 6.26.0
ipywidgets       : 8.1.1
jupyter_client   : 8.6.0
jupyter_core     : 5.5.0
jupyter_server   : 2.10.1
jupyterlab       : 4.0.9
nbclient         : 0.8.0
nbconvert        : 7.11.0
nbformat         : 5.9.2
notebook         : 7.0.6
qtconsole        : 5.5.1
traitlets        : 5.13.0](url)

On the remote machine:

(base) wavewatch@ned:~> jupyter --version
Selected Jupyter core packages...
IPython          : 8.17.2
ipykernel        : 6.26.0
ipywidgets       : 8.1.1
jupyter_client   : 8.6.0
jupyter_core     : 5.5.0
jupyter_server   : 2.10.1
jupyterlab       : 4.0.9
nbclient         : 0.8.0
nbconvert        : 7.11.0
nbformat         : 5.9.2
notebook         : 7.0.6
qtconsole        : 5.5.1
traitlets        : 5.13.0

Any thoughts?


Make testRegExp less restrictive

E.g.
/[\uD834\uDF06-\uD834\uDF08a-z]/u

This is perfectly valid ES6 (given the u flag) but it didn’t parse in Esprima before this patch because testRegExp evaluates the regexp without the u flag (as it should, since it aims to support a wide range of browsers/environments).
This patch accounts for this case as well by using a regex to look for \uXXXX escape sequences and replacing them with a hardcoded ASCII letter x (like we previously did for \u{…} escapes).

Thanks for contributing, @mathiasbynens! Can you please rename the added tests files to actually describe the test? migrated_* is a holdover from when we split up the giant monolith test file recently.

Is this related to #1089?

@mikesherov Done.
@ariya This is unrelated to #1089.

The bug was filed as #1114.

LGTM.


fix: config commit --force not work

In the following code snippet, when curveadm.ParseTopology() function returns an error, it will return err.
but  if --force=1 option is set, the logic to update the config should continue to execute.
func runCommit(curveadm *cli.CurveAdm, options commitOptions) error {
	// 1) parse cluster topology
	_, err := curveadm.ParseTopology()
	if err != nil && !skipError(err) {
		return err
	}
}

Case:
(1) For example, for the following config, it has syntax errors(a=1), but the config update will still succeed.
(2) But now if you try to update the config(a: 1), it will fail, reporting a parsing error and unable to proceed the update.
chunkserver_services:
  config:
      a=1

@CodeRusher Thanks your contribute. However, the original intention of this option is to skip the check, not to tolerate any configuration.


Extract exception type name from std::exception_ptr on libstdc++

There's a public function https://github.com/gcc-mirror/gcc/blob/41d6b10e96a1de98e90a7c0378437c3255814b16/libstdc%2B%2B-v3/libsupc%2B%2B/exception_ptr.h#L153 that returns std::type_info of the exception.

Thank you.


strides using negative indices can result in no data -

Reported by Ansley B Manke on 26 Mar 2004 00:03 UTC
LAS scripts set a region, use var,return=istart
and var,return=iend figure out what range to us
to access data, perhaps with strides.  Here is
an example; create a file whose modulo x axis is
180 to 540 and use that to try to plot x=-60:60
use etopo20
set reg/x=180:540
save/clobber/file=shift.nc rose
can data/all
can reg/all
can mem
use shift.nc
set reg/x=-60:60
say rose,r=istart
say rose,r=iend
shade rose[valid data)
Note that mode diag output (below) shows:
rdstride ROSE     C:  9 I:  361  721  J:    1  540  K: -111 -111  L: -111 -111
So at some point the correct data is read.
yes? set mode diag
yes? shade rose[i=-720:-360:5](i=-720:-360:5]
(no)
dealloc  dynamic grid GOV1            ETOPO20X1_ETOPO20Y  NORMAL    NORMAL
getgrid EX#1     C:  5 I:    1    1  J:    1    1  K:    1    1  L:    1    1
allocate dynamic grid (G002)          (AX004)   ETOPO20Y  NORMAL    NORMAL
dealloc  dynamic grid (G002)          (AX004)   ETOPO20Y  NORMAL    NORMAL
allocate dynamic grid (G002)          (AX004)   ETOPO20Y  NORMAL    NORMAL
eval    EX#1     C:  4 I: -111 -111  J:    1  540  K: -111 -111  L: -111 -111
allocate dynamic grid (G002)          (AX004)   ETOPO20Y  NORMAL    NORMAL
strip regrid on X: ROSE --> (G002)           @XACT
strip moduloing ROSE on X axis:  -720  -359
rdstride ROSE     C:  9 I:  361  721  J:    1  540  K: -111 -111  L: -111 -111
doing moduloing ROSE on X axis:   361   721
-DELETE ROSE     M:  1 I:  361  721  J:    1  540  K: -111 -111  L: -111 -111
nulrgd  ROSE     M:  1 I:    1   73  J:    1  540  K: -111 -111  L: -111 -111
-DELETE ROSE     M:  2 I: -720 -359  J:    1  540  K: -111 -111  L: -111 -111
dealloc  dynamic grid (G002)          (AX004)   ETOPO20Y  NORMAL    NORMAL
setting up 2D plot
-DELETE ROSE     M:  2 I:    1   73  J:    1  540  K: -111 -111  L: -111 -111
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/833

Comment by<EMAIL_ADDRESS>on 23 Apr 2004 18:58 UTC
This bug appears NOT to be fixed under linux.  It is fixed
under solaris. We have a test example under
bench/err553_stride_modulo.jnl
use mylon
list var[all missing data under linux, but gets good data under
solaris.  (similar example: use etopo20; list/y=0 rose[i=-400:-40:20](i=-400:-40:20]
lists))
If I check that benchmark output is correct under solaris,
how can we better compare benchmark output from other operating
systems?

Comment by<EMAIL_ADDRESS>on 23 Apr 2004 20:51 UTC
Yes, it is fixed under linux.  The very latest executable
had not been installed on stout and ferret, but they are
now.  The fix is in the executables that are available on
the downloads page.


Docs 11669 1.7 inclusive terminology

https://www.mulesoft.org/jira/browse/DOCS-11669

Closing this PR due to CLA missing. Will recreate at later date


exchangelib -- workaround found

Last week (week of Aug. 23 or so 2017), my python scripts that use exchangelib stopped working on both Linux Ubuntu and Windows 7 64 bit. I traced the issue to this line:
account =<EMAIL_ADDRESS>credentials=credentials,autodiscover=True)
Here are the error messages:
EWS https://outlook.office365.com/EWS/Exchange.asmx, account None: Exception in _get_elements: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/exchangelib/services.py", line 74, in _get_elements response = self._get_response_xml(payload=payload) File "/usr/local/lib/python3.5/dist-packages/exchangelib/services.py", line 161, in _get_response_xml new_version = Version.from_response(requested_api_version=api_version, response=r.text) File "/usr/local/lib/python3.5/dist-packages/exchangelib/version.py", line 248, in from_response api_version_from_server = info.get('Version') or build.api_version() File "/usr/local/lib/python3.5/dist-packages/exchangelib/version.py", line 102, in api_version return self.API_VERSION_MAP[self.major_version][self.minor_version] KeyError: 20
Traceback (most recent call last): File "365debug.py", line 16, in  account =<EMAIL_ADDRESS>credentials=credentials,autodiscover=True) File "/usr/local/lib/python3.5/dist-packages/exchangelib/account.py", line 68, in _init credentials=credentials, verifyssl=verify_ssl) File "/usr/local/lib/python3.5/dist-packages/exchangelib/autodiscover.py", line 186, in discover protocol=protocol) File "/usr/local/lib/python3.5/dist-packages/exchangelib/autodiscover.py", line 330, in _autodiscover_quick verify_ssl=protocol.verify_ssl) File "/usr/local/lib/python3.5/dist-packages/exchangelib/protocol.py", line 173, in _call protocol = super(CachingProtocol, cls).call(args, *kwargs) File "/usr/local/lib/python3.5/dist-packages/exchangelib/protocol.py", line 226, in init self.version = Version.guess(self) File "/usr/local/lib/python3.5/dist-packages/exchangelib/version.py", line 194, in guess return cls._guess_version_from_service(protocol=protocol, hint=api_version) File "/usr/local/lib/python3.5/dist-packages/exchangelib/version.py", line 226, in _guess_version_from_service ResolveNames(protocol=protocol).call(unresolved_entries=[protocol.credentials.username]) File "/usr/local/lib/python3.5/dist-packages/exchangelib/services.py", line 975, in call return_full_contact_data=return_full_contact_data, File "/usr/local/lib/python3.5/dist-packages/exchangelib/services.py", line 74, in _get_elements response = self._get_response_xml(payload=payload) File "/usr/local/lib/python3.5/dist-packages/exchangelib/services.py", line 161, in _get_response_xml new_version = Version.from_response(requested_api_version=api_version, response=r.text) File "/usr/local/lib/python3.5/dist-packages/exchangelib/version.py", line 248, in from_response api_version_from_server = info.get('Version') or build.api_version() File "/usr/local/lib/python3.5/dist-packages/exchangelib/version.py", line 102, in api_version return self.API_VERSION_MAP[self.major_version][self.minor_version] KeyError: 20

The problem for me was that the major_version and minor_version returned by the Exchange Server are of 15 and 20
However the minor_version 20 doesn't exists in the version_map of the library. If you want it to work you can hotfix this by setting hardcoded value to not have a key error.
The file to modify is located in /usr/local/lib/python3.X/dist-packages/exchangelib/version.py
Line 102 I replaced major_version by 15 and minor_version by 1.

Just for the record, this GitHub project is for pyexchange, not exchangelib.


[SPARK-8882][Streaming]Add a new Receiver scheduling mechanism

The design doc: https://docs.google.com/document/d/1ZsoRvHjpISPrDmSjsGzuSu8UjwgbtmoCTzmhgTurHJw/edit?usp=sharing
TODO List

[x] Refactor JobWaiter to avoid creating new Threads for receivers
[x] Fix current unit tests
[x] Add new unit tests for ReceiverScheduler

Merged build triggered.

Merged build started.

Test build #36742 has started for   PR 7276 at commit d9a3e72.

Test build #36742 has finished for   PR 7276 at commit d9a3e72.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36797 has started for   PR 7276 at commit 27acd45.

Merged build triggered.

Merged build started.

Test build #36798 has started for   PR 7276 at commit ca6fe35.

Test build #36797 has finished for   PR 7276 at commit 27acd45.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #36798 timed out     for PR 7276 at commit ca6fe35     after a configured wait of 175m.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #36868 has started for   PR 7276 at commit ca6fe35.

Test build #36868 timed out     for PR 7276 at commit ca6fe35     after a configured wait of 175m.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36919 has started for   PR 7276 at commit 2c86a9e.

Test build #36919 has finished for   PR 7276 at commit 2c86a9e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #37090 has started for   PR 7276 at commit 28d1bee.

Test build #37090 timed out     for PR 7276 at commit 28d1bee     after a configured wait of 175m.

Merged build finished. Test FAILed.

My high-level comment / question: why not use the existing submitJob that returns a SimpleFutureAction rather than defining your own asynchronous version of that method?

My high-level comment / question: why not use the existing submitJob that returns a SimpleFutureAction rather than defining your own asynchronous version of that method?

The problem of SimpleFutureAction is its onComplete calls awaitResult. So if using SimpleFutureAction, each Job needs to block one thread. It means  each running Receiver needs one thread in the driver. It may exhaust threads.
  override def onComplete[U](func: (Try[T]) => U)(implicit executor: ExecutionContext) {
    executor.execute(new Runnable {
      override def run() {
        func(awaitResult())
      }
    })
  }

2 major high-level comments that need significant code changes before we proceed further.

Messaging can be optimized, see other comments
The ReceiverLauncher is becoming quite complex, is it going to be too complex to move it to a separate file?

Merged build triggered.

Merged build started.

I have reverted the changes to core. So this PR won't pass the tests until #7385 is merged. I will update this PR then.

Merged build triggered.

Merged build started.

Test build #37242 has started for   PR 7276 at commit 3b87e4a.

Test build #37242 has finished for   PR 7276 at commit 3b87e4a.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

The ReceiverLauncher is becoming quite complex, is it going to be too complex to move it to a separate file?

How about doing it in a follow-up PR? Moving it to another file would make this PR hard to review.

Merged build triggered.

Merged build started.

Test build #37383 has started for   PR 7276 at commit 5fee132.

Test build #37383 has finished for   PR 7276 at commit 5fee132.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Okay, sounds good.
On Wednesday, July 15, 2015, Shixiong Zhu<EMAIL_ADDRESS>wrote:

The ReceiverLauncher is becoming quite complex, is it going to be too
complex to move it to a separate file?
How about doing it in a follow-up PR? Moving it to another file would make
this PR hard to review.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/7276#issuecomment-121685090.

--
Sent from Gmail Mobile

Since #6294 has been merged, please update this PR. A summary of suggestions made offline.

Lets try to move all the "starting of receivers" into the event loop of ReceiverTracker. So all the receiverTrackignInfo will be updated and accessed in a lock free manner from the event loop.
I encourage you to get rid of ReceiverLauncher if its easy enough.
The scheduling policy and the scheduled location still needs to be discussed further out (what we discussed offline still has drawbacks).

Merged build triggered.

Merged build started.

I reorganized ReceiverTracker to use an event loop, including:

Add fields into ReceiverTrackingInfo to contain all necessary information for ReceiverInfo. When sending ReceiverInfo to StreamingListener, create ReceiverInfo from ReceiverTrackingInfo directly.
Move methods that use ReceiverTrackingInfo into ReceiverTrackerEndpoint so that we can maintain all ReceiverTrackingInfos in an event loop.
Move ReceiverTrackingInfo to a separate file ReceiverTrackingInfo.scala.
Address some code style issues

how does it behave when there are 100 executors, and 100 receivers need to be scheduled in the beginning. ideally there should be 1 receiver per executor

Assume we only have 2 executors and 2 receivers. The current scheduling policy will always return the 2 executors. Then it's possible that 2 receivers run in the same executor. But if returning only 1 executor, we may keep restarting receivers if the location does not match.

@JoshRosen do you know how to get the executor id in a spark job closure?

Test build #37961 has started for   PR 7276 at commit f60d021.

Merged build triggered.

Merged build started.

Test build #37964 has started for   PR 7276 at commit 4e639c4.

Test build #37964 has finished for   PR 7276 at commit 4e639c4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@zsxwing, it looks like SparkEnv has an executorId field that you can use.

Test build #37961 has finished for   PR 7276 at commit f60d021.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

i took a medium-level pass, not too detailed and overall approach into the event loop looks. However I have some high level comments.

In the code refactoring, why did you move all the registerReceiver, deregisterReceiver, etc. into the Endpoint class? That moves around a lot of code, making it hard to review. Also it makes the overall structure more complex - some functionality is in the parent ReceiverTracker class and some are in the EndPoint class, hard to reason about what goes where in the future. Instead the earlier structure had the goal of all the functionality is in the ReceiverTracker, and the Endpoint class was just to going to be the event loop that accesses that functionality. I think its more structured if that is maintained.

I think the scheduling policy needs to be thought through. It may be in the case we need two steps, one of bulk scheduling in the beginning, which tries to distribute it properly (n recvrs in n execs) by setting preferred locations on all of them. Then for every receiver that needs to be restarted, they are scheduled one at a time. The schedulingPolicy can be changed to take an array of receiverIds to accommodate this, initially all the receiverIds are sent, and the locations of all of them returned; then one at a time. How does that sound?

In the code refactoring, why did you move all the registerReceiver, deregisterReceiver, etc. into the Endpoint class? That moves around a lot of code, making it hard to review. Also it makes the overall structure more complex - some functionality is in the parent ReceiverTracker class and some are in the EndPoint class, hard to reason about what goes where in the future. Instead the earlier structure had the goal of all the functionality is in the ReceiverTracker, and the Endpoint class was just to going to be the event loop that accesses that functionality. I think its more structured if that is maintained.

I moved all methods and fields that are only accessed in the endpoint into the endpoint. I feel it's easy to see they are only accessed in the endpoint. However, it really makes this PR hard to review. Let me move them back to the outer class.

Merged build triggered.

Merged build started.

After considering carefully, I think if a receiver has a preferredLocation, it means it's better to run the receiver in this preferredLocation if possible. So I don't clear it when restart a receiver.

Test build #38084 has started for   PR 7276 at commit 8f93c8d.

Test build #38084 has finished for   PR 7276 at commit 8f93c8d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

@zsxwing, it looks like SparkEnv has an executorId field that you can use.

@JoshRosen Thank you. It works.

Test build #1161 has started for   PR 7276 at commit 8f93c8d.

Test build #1161 has finished for   PR 7276 at commit 8f93c8d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test build #1180 has started for   PR 7276 at commit 8f93c8d.

Test build #1180 has finished for   PR 7276 at commit 8f93c8d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Test build #38144 has started for   PR 7276 at commit 05daf9c.

Test build #38144 has finished for   PR 7276 at commit 05daf9c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #38202 has started for   PR 7276 at commit 137b257.

Test build #38202 has finished for   PR 7276 at commit 137b257.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

I think this PR is close to LGTM. I will wait for #7385 to get merged, then this PR can be updated accordingly.

I chatted with @pwendell for his opinion on this, and its fine to merge this as is without the #7385. Once that is merged we can always improve the performance later. Not that its going to really hurt performance in the current state, as it will be just a bunch of sleeping blocked threads, there is not constant thread switching.

@tdas Agree. We can do it later.

Alright, then i am merging this!


Facets and sorting are not working when prefix index is set

Currently default_facet_factory is searching for the unprefixed index name in your RECORDS_REST_FACETS config but when you search the prefixed one is passing here. The same should be taken in consideration for the sorter_factory

Addressed by #256. Needs https://github.com/inveniosoftware/invenio-search/commit/0a6055c1a17ce082c2ef57f00208a0c067b630eb to be released.

Closed via #256, pending release of invenio-records-rest


[polymer-cli] No parser for for file type mjs

Description
Google recommends using .mjs files to maintain parity with NodeJS, but polymer-cli apparently doesn't recognise them as javascript. When running polymer-lint, I got the following error:
$ polymer lint

  <script type="module" src="src/chatter-app.mjs"></script>
                            ~~~~~~~~~~~~~~~~~~~~~

index.html(66,29) error [could-not-load] - Unable to load import: No parser for for file type mjs

Found 1 error.

Also, I think that that error contains a typo.
Versions & Environment

Polymer CLI: 1.8.0
node: v10.9.0
Operating System: MacOS Sierra 10.12.6

Steps to Reproduce
Example:

Create an application project: polymer init application
Rename all javascript files to use the .mjs convention
Change imports and <script> tags accordingly
Lint: polymer lint

Expected Results
No error is thrown
Actual Results
Error is throne: index.html(66,29) error [could-not-load] - Unable to load import: No parser for for file type mjs

Google recommends using .mjs files to maintain parity with NodeJS

Where does Google recommend this?

@aomarks there has been talk in IO, where .mjs has been promoted by Mathias Bynens.

https://youtu.be/mIWCLOftfRw?t=8m6s

@aomarks https://youtu.be/mIWCLOftfRw?t=8m6s

"Google recommends"
Some people at google, who I might or might not vehemently disagree with recommend this (for the sake of a non-existent Node.js feature), but I wouldn't say that Google as a whole recommends it.

@jajaperson or @web-padawan is the lack of this feature causing problems with any third party packages? I wasn't aware of too many that are actually publishing .mjs files yet.

We have tried .mjs in the vaadin-router but declined, because we realised that webpack considers it to be node-specific.

I use unfetch and preact with my Polymer 3 project and that ships with mjs
import 'unfetch/polyfill';
       ~~~~~~~~~~~~~~~~~~

src/entrypoints/compatibility.js(2,8) error [could-not-load] - Unable to load import: No parser for for file type mjs

import { render } from 'preact';
                       ~~~~~~~~

src/common/preact/unmount.js(1,24) error [could-not-load] - Unable to load import: No parser for for file type mjs


Hard to read complete data

The batch parameter on Scanner data structure controls how many cells (not rows) will be retrieved at a time. This means that for it be useful one needs to write code to combines the data from possibly multiple batches so only complete rows are returned to the client code.  This might not be needed with stateless scanners #7 as they have limit parameter which operates on the row level.
I have a piece of code that does that and if there is enough appetite I can open a pull request.
The gist of it is here: https://gist.github.com/pawelpabich/53d5cfc3ef51a083a042. I also have set of tests that covers it.

One more thing, if you don't specify batch parameter then, in my experience, all gets returned at once which might cause Out of Memory exceptions along the way.


Monorepo: push and use latest images for testing

What this PR does / why we need it:
Monorepo: push and use latest images for testing
NONE

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
69c305420d03aaceaf8c495d3e1905d52d3e3a58
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-suite-rbac-auth

prow/e2e-suite-rbac-no_auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-suite-rbac-auth

prow/e2e-suite-rbac-no_auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-suite-rbac-no_auth

prow/e2e-cluster_wide-auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-cluster_wide-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-suite-rbac-auth

prow/e2e-cluster_wide-auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-cluster_wide-auth

prow/e2e-suite-rbac-no_auth.sh
a0d92e44dcd1bf2049ba3d79a2531592b262c887
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-cluster_wide-auth.sh
dfb2a3fe585193036fb75fed06d9097da6fd4bfe
link
/test e2e-cluster_wide-auth

prow/e2e-suite-rbac-no_auth.sh
a0d92e44dcd1bf2049ba3d79a2531592b262c887
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
a0d92e44dcd1bf2049ba3d79a2531592b262c887
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
a0d92e44dcd1bf2049ba3d79a2531592b262c887
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
a0d92e44dcd1bf2049ba3d79a2531592b262c887
link
/test e2e-suite-rbac-auth

prow/e2e-cluster_wide-auth.sh
a0d92e44dcd1bf2049ba3d79a2531592b262c887
link
/test e2e-cluster_wide-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

⭕ ci is failing now :-(. @rshriram seems like a flake.


CIT Resewn

Mod name
CIT Resewn
Curseforge link
https://www.curseforge.com/minecraft/mc-mods/cit-resewn
Other links
https://modrinth.com/mod/cit-resewn
https://github.com/SHsuperCM/CITResewn
What it does
Adds Optifine CIT Compatibility.
Why should it be in the modpack
Optifine Parity.
Cleanest way to add CIT to the pack:

1 mod, with definite compat instead of MCPPPP and Chime.

Categories
New feature, Works like Optifine/Bedrock Edition/Forge/etc

Duplicate of #112


HTTP proxy doesn't seem to be sending URL

I've tested out Duckling with both Lagrange and amfora. With amfora the proxying works as expected (using a URL like http://example.com/) and with Lagrange it does not. Debugging it appears that an address is not included as part of the request.
Happy to help debug more if you'd like.

I've been running Duckling Proxy for quite a while now and have had no issues with it. Could you share some details about your setup?

is the proxy on the localhost or running somewhere else?
which operating systems are Lagrange and the proxy on?
in Lagrange's network setup, did you configure the address using a domain name or IP address?
IPv4 or v6? (not sure if Duckling supports IPv6)

@skyjake Thanks! Happy to provide this info.

I actually deployed this to run on a server and it works that way. So this bug seems to be just localhost.
OSX 12.2.1
I tried both localhost and <IP_ADDRESS>. Sometimes included the port, no change.
IPv4

Yes, that's because the go-gemini library reads the request for the URL but there isn't one, so it crashes when the handler tries to get the URL as as a string.  You will observe that using amfora you do not get that error. I think that Lagrange is not sending the URL when on localhost.

The problem here seems to be (at least on my machine) that I already had a trusted certificate for "localhost:1965" that didn't match Duckling's certificate. This caused the request to be aborted by Lagrange when it found the certificate mismatch. Manually deleting the offending entry from "trusted.2.txt" fixed the problem.
The appropriate fix here is to inform the user about the certificate mismatch and allow them to trust the new certificate of the proxy.

Fix included in v1.13.7.


Dataset used on the Pre-trained model

Could you please tell me on which data set was this pretrained model trained on ? I am a little confused

Hi,
I used Gigaword data available at here.


python: fix fatal in main.py (github #78)

Issue-On: https://github.com/gem5/gem5/issues/78

Hi! In order to have the rest of your CI tests run so we can merge this change, we require your commit to have a Change-Id at the end of the commit message.  Thanks!
f=git rev-parse --git-dir/hooks/commit-msg ; mkdir -p $(dirname $f) ; ' curl -Lo $f https://gerrit-review.googlesource.com/tools/hooks/commit-msg ; chmod +x $f

@powerjg Many thanks! I have updated.


feat(salt): add archlinux support to salt installer

This PR fixes the installer.sh -i salt command for Archlinux.

Verified on Archlinux.
... cut ...

:: Running post-transaction hooks...
(1/2) Reloading system manager configuration...
(2/2) Arming ConditionNeedsUpdate...
 *  INFO: Running install_arch_linux_post()
 *  INFO: Running install_arch_linux_restart_daemons()
 *  INFO: Running daemons_running()
 *  INFO: Salt installed!

kernel before: 5.2.3-arch1-1-ARCH..
kernel after: Name            : linux
Version         : 5.2.3.arch1-1
Description     : The Linux kernel and modules
Architecture    : x86_64
URL             : https://git.archlinux.org/linux.git/log/?h=v5.2.3-arch1
Licenses        : GPL2
Groups          : base
Provides        : None
Depends On      : coreutils  linux-firmware  kmod  mkinitcpio
Optional Deps   : crda: to set the correct wireless channels of your country
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 77.67 MiB
Packager        : Jan Alexander Steffens (heftig<EMAIL_ADDRESS>Build Date      : Fri 26 Jul 2019 18:12:48 AEST
Install Date    : Mon 29 Jul 2019 07:03:22 AEST
Install Reason  : Explicitly installed
Install Script  : Yes
Validated By    : Signature
Reboot if kernel was major-upgraded; if unsure reboot!

cloning salt-formula for OpenSDS ...
... using fork: noelmcloughlin, branch: fixes
Branch 'fixes' set up to track remote branch 'fixes' from 'origin'.
Switched to a new branch 'fixes'

cloning opensds-installer for OpenSDS ...
... using fork: noelmcloughlin, branch: fixes
Branch 'fixes' set up to track remote branch 'fixes' from 'origin'.
Switched to a new branch 'fixes'

Accepted Keys:
archlinux.vagrant.vm
Denied Keys:
Unaccepted Keys:
Rejected Keys:
local:
    ----------
    base:
        - salt.pkgrepo
        - salt.minion
        - salt.master
        - salt.ssh
        - salt.formulas
run salt: this takes a while, please be patient ...
-------------
Succeeded: 34 (changed=29)
Failed:     0
-------------
See full log in [ /tmp/install-opensds-opensds-installer-salt/log.201907300929 ]

///////////////////////////////////////////////////////////////////////////
      congrats:  salt for OpenSDS is now installed
///////////////////////////////////////////////////////////////////////////

Closing to rebase


remove resize directive

Removed the MglMapResizeDirective as it cannot be found in the Stackblitz demo and the map resizes properly on sidenav open and close.

map is being resized automatically when sidenav opens/closes
not found in stackblitz demo

Yes, this is probably because of the transition to resize observer in maplibre...
Great that you removed it!


Add chirp interop flag

Fixes CLI-47

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #298

PR #299   👈

This stack of pull requests is managed by Graphite.

How were each of the threads resolved?

How were each of the threads resolved?

I resolved them instinctively. I should've left them open mb.

@MasterPtato is this pr good to merge? needs an approval.


[Action] TAG ENV maintainer talk Kubecon NA 2024

Description
We would like to submit a maintainer talk to KCCN NA 2024. The talk should highlight what the TAG does and what the TAG was up to in the last half year. There should be enough time to set a focus on one of the topics the TAG was primarily dealing with (it can be one of the projects, a WG or something we talked in discussions). Depending on the outline of the maintainer talk, we ask folks to deliver it. Usually, one of the TAG ENV leads + a WG lead or a contributor that was very engaged.
Outcome
TAG ENV maintainer talk submission for KCCN NA
To-Do

[ ] Write up maintainer talk outline (doc)
[ ] Ask for reviewers
[ ] Submit talk to sessionize (link)

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Comments
As pre discussion; @catblade is going to submit the talk, we will ask to add the co-speaker a month or so before the conference.

Maintainer talk status here:  https://docs.google.com/document/d/10mkZh5SSzMNnbfZUhcg3Jr4NTiYmpXyL20YdXsfWxZo/edit
Request for reviewers.  tag-env-leads told of this in the main channel.

Done and submitted.  :-)

🎉


Only increment runningActivities for non-mocked activities

This is done so that, when the WorkflowTester is dealing with mocked activities, it can skip time. It is a slight refinement on what was initially done in #169.

Hold off on 👀 , need to check something first

Making another attempt at this


jquery pre-requisite in Visual Studio NuGet

I am using Visual Studio 2015 Community edition. There is a repository, called NuGet, that contains extensions for Visual Studio, including Bootstrap.
As part of the extension, there are facilities to update Bootstrap to 3.3.6. The package includes a jQuery dependency (jQuery (>= 1.9.1 && 3.0.0)
Visual Studio 2015 has been updated recently to use jQuery <IP_ADDRESS>, which is causing the following error to appear while attempting to update the Bootstrap extension 3.3.6: dependency: Error		Unable to resolve dependencies. 'jQuery <IP_ADDRESS>' is not compatible with 'bootstrap 3.3.6 constraint: jQuery (>= 1.9.1 && < 3.0.0)'.
Could you please check and advise?
Many thanks,

Approximate duplicate of #16834.


Safari TP 124 improved support for text-indent

[ ] Figure out which state is actually correct

Starting this PR to get the ball rolling:
https://webkit.org/blog/11672/release-notes-for-safari-technology-preview-124/

Enabled hanging and each-line keywords for the text-indent CSS property (r275199)

Looking at https://tests.caniuse.com/css-text-indent, TP 124 certainly improved on TP 123.
TP 123:

TP 124:

However it's not entirely green and also not the same the same as Chrome.
Chrome Canary 92.0.4500.0:

Given that they talk about tests and improving spec compliance in the changeset I'm wondering if https://tests.caniuse.com/css-text-indent is still correct or if support is truly still partial in TP 124.
If it's partial in TP 124, I'd change the PR to a #3, with note 3 stating the buggy behavior of each-line, ideally linking to a WebKit bug.
Neither https://mdn-bcd-collector.appspot.com/tests/css/properties/text-indent nor https://wpt.fyi/results/css/css-text/text-indent seem to cover each-line.
Ah, there are more tests at (wpt.fyi for those):

https://wpt.live/css/css-text/parsing/text-indent-computed.html
https://wpt.live/css/css-text/parsing/text-indent-invalid.html
https://wpt.live/css/css-text/parsing/text-indent-valid.html

buuuut they are the same:
TP 124:

Chrome Canary 92.0.4500.0 (still with #enable-experimental-web-platform-features enabled):

Looking at the spec for each-line

each-line
Indentation affects the first line of each block container and each line after a forced line break (but not lines after a soft wrap break).

my working assumption is that Safari is missing the second part

each line after a forced line break

which https://tests.caniuse.com/css-text-indent checks for by having the <br> but the web-platform-tests don't yet.
Also that's a bug in WebKit then.

Made obsolete by https://github.com/Fyrd/caniuse/pull/6351.


Using "admin" as username without SS_DEFAULT_ADMIN_XX raises exception

Affected Version
php7.1-fpm & mod-php7.1 / framework 4.0.2 / Ubuntu 16.04
Description
Seen in Dev Mode & Live Mode
1). Setup .env file
SS_DEFAULT_ADMIN_USERNAME="admin"
SS_DEFAULT_ADMIN_PASSWORD="password"

2).

[OK]  In frontend login as "admin" with dummy (bad) password
[OK] Observe useful error message

Placing debug logic within public static function create_for_algorithm($algorithm), this method isn't called.
3).

[OK] Remove SS_DEFAULT_ADMIN_USERNAME and SS_DEFAULT_ADMIN_PASSWORD from .env
[OK] In frontend login as "admin" with dummy (bad) password
[FAIL] Observe exception: Uncaught Exception SilverStripe\Security\PasswordEncryptor_NotFoundException: "No implementation found for """ at /path/to/vendor/silverstripe/framework/src/Security/PasswordEncryptor.php line 43

Placing debug logic within public static function create_for_algorithm($algorithm) in the latter case, $algorithm is NULL....in itself this is unnerving as PHP should have warned that $argument cannot be NULL...

Fixed with https://github.com/silverstripe/silverstripe-framework/pull/7836#pullrequestreview-94506540


Fix various linting issues

Looks like it's just down to reduced test coverage, at least partly from the changes in #418. Nothing really exercising any of the Libbi code
 ---------- coverage: platform linux, python 3.9.18-final-0 -----------
Name                                          Stmts   Miss  Cover   Missing
---------------------------------------------------------------------------
custom_components/myenergi/__init__.py           63      7    89%   98-111, 116-117
custom_components/myenergi/binary_sensor.py      33      0   100%
custom_components/myenergi/config_flow.py        66      0   100%
custom_components/myenergi/const.py              17      0   100%
custom_components/myenergi/entity.py             58      0   100%
custom_components/myenergi/number.py            100      1    99%   26
custom_components/myenergi/select.py             95     10    89%   68, 147, 152, 159, 164-166, 170-171, 175
custom_components/myenergi/sensor.py            217     11    95%   494-648
---------------------------------------------------------------------------
TOTAL                                           649     29    96%

Thanks!


Show All option shows only one doc (instead of all docs)

I added the following option to tabular:
lengthMenu: [ [10, 20, 40, 100, -1], [10, 20, 40, 100, "All"] ],

However, the All option shows only one doc (instead of all docs)
The lengthMenu option is described at http://datatables.net/reference/option/lengthMenu

Duplicate of https://github.com/aldeed/meteor-tabular/issues/69


The OT loss is too small.Dose it work?

It's even less than 0:
Epoch 46 Train, Loss: 3.89, OT Loss: -6.02e-07, Wass Distance: 803.41, OT obj value: 113.64, Count Loss: 3.55, TV Loss: 0.35, MSE: 8.88 MAE: 3.55, Cost 24.5 sec

Different losses should not be compared directly. The OT loss and other losses are not computed in the same way. In multi-loss training, what matters is the gradient contribution of each loss component. The OT loss here is basically computed as the sum of Grad_from_OT * parameters.


Allow forge install to specify folder name

Component
Forge
Describe the feature you would like
git submodule allows to specify the destination folder. It seems that forge install gets always the repo name (without the owner). This is sometimes too ambiguous. It would be nice to be able to specify the name of the folder that gets created under  lib and pass it to git submodule add command.
Additional context
No response

We can use something like this:
forge install <alias>@forge:<github org>/<github repo>

Where alias is the destination folder. It's similar to npm install.

@ is already taken for refs: <owner>/<repo>@<commit or branch or tag>

@onbjerg ah okay, I've used = to set the alias in #1315. please let me know what u think. ty!


Feature proposal: fdelete and/or fupdate?

The SQL like syntax makes me think that we could implement fupdate or fdelete?

Sure. As fselect becomes more stable, there come fupdate (kind of chmod ?) and fdelete.

Chmod and chown would be nice.

Perhaps too complex for the scope, but a frename, with RE / expression capture and their usage in replace part would be awesome.
But it needs dry-run (idem for the above, of course) and conflict management...

I made a similar tool in Python, for the purpose of flexible reorganization of files in batch based on regular expression, it is indeed very flexible:
https://github.com/lrq3000/csg_mri_pipelines/blob/master/utils/pathmatcher/pathmatcher.py
This tool has a lot less scope than fselect (ie, pathmatcher.py is only working on paths, not on meta-data), so I would also be very interested if the possibility to do actions on the found files (moving/renaming/copying the input path to an output path with possibly a regex reusing captured groups in input path, deleting).
I think if this functionality is based on regular expression, it would be more easily implemented and have a lot of flexibility. Then, only the operator would change the exact operation done (move/copy/delete), but the output would be solely defined by the regex.

PS: Also my pathmatcer.py tool outputs a text report to be reviewed by the user, with detection of conflicts, if this can help for inspiration. Feel free to ask me questions too.

Why not use something like fselect | xargs | rm -v {}?

Not cross platform.
Le mar. 6 avr. 2021 à 18:22, Niklas Mollenhauer @.***>
a écrit :

Why not use something like fselect | xargs | rm -v {}?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jhspetersson/fselect/issues/10#issuecomment-814253778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIRFXXCN6MUTLIW4ZLN5ETTHMYMVANCNFSM4ETK5YWA
.

Actually we have WSL, WSL2, and a series of other ports that allow us to use xargs natively now if the need arises. That makes fupdate/fdelete irrelevant IMHO.


refactor: update dummy database data

:tada: This PR is included in version 0.51.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


For Azure powershell, I can't find Get-AzWebSiteLog function as the page describes. Is it called something else now?

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 13672b67-22ea-3dda-8b6b-3332c24e6030
Version Independent ID: fdc60aeb-9971-1d9f-a6ba-b3ad818cf0d5
Content: Monitor Azure Functions
Content Source: articles/azure-functions/functions-monitoring.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@pandainlove Thank you for your feedback! We will review and update as appropriate.

Can the updated command name be posted here for searchers?  Thanks!

@pandainlove Can you confirm if you Az Module is installed in the machine from where you are executing the command https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-4.3.0
If it is installed then please verify what is the version using below command:
Get-InstalledModule -Name Az -AllVersions
The latest version is 4.3.0 for Az Modle. If it is not the latest then follow the above document to update the module.
Note: Having both the AzureRM and Az modules installed at the same time is not supported

@MayankBargali-MSFT My Az module version was 3.8.0 and now I updated to 4.3.0 I still don't see Get-AzWebSiteLog. I also checked the documents I can't see anything about this function. I only saw functions starts with Get-AzWebAppxxx.
Or do you mean I need to use Get-AzureWebsiteLog instead? This looks to belongs to a different module called Azure.
I am new with Azure powershell, now I am a little confused which module I am supposed to use. I thought Az will replace AzureRM and Azure modules. Is that correct?
Thanks

@pandainlove Thanks for your response. Yes, Az module will be the replacement of Azure RM : https://azure.microsoft.com/en-in/blog/azure-powershell-cross-platform-az-module-replacing-azurerm/
I have reached out to my team to confirm if there is any az command in PowerShell to stream the logs. For a workaround, you can use any of the methods

azure cli az cmdlet : https://docs.microsoft.com/en-us/azure/azure-functions/functions-monitoring?tabs=cmd
Classic cmdlets: https://docs.microsoft.com/en-us/powershell/module/servicemanagement/azure/get-azurewebsitelog?view=azuresmps-4.0.0
You can also leverage the https://docs.microsoft.com/en-us/azure/app-service/scripts/powershell-monitor

@MayankBargali-MSFT Yes, I am currently using azure cli to monitor the logs. I am trying to stay with az module that's why I reported in this issue Get-AzWebSiteLog doesn't exist. Let me know if your team can finally locate it.
Thanks

@pandainlove I have got an update that there is no equivalent command for now in the az PowerShell module. This will be the feature request and it would be great if you can create the feature request here: https://github.com/Azure/azure-powershell/issues
Thanks for pointing it out and we will update the document to reflect the same.

@pandainlove the current recommendation for the new module is to use the Set-AzWebApp cmdlet, as demonstrated in this Web Apps article. I've just made updates to this article to address this. Thanks for bringing it to our attention. #please-close

@ggailey777 , thanks for the new info provided. I was busy for the past two weeks.
quick question about your example, I don't see how I can tail the log file as the Get-AzureWebsiteLog can do. what solution do I have?
Also, since the ticket is closed, I assume the original document will be updated about missing Get-AzWebsiteLog but it seems still there?...https://docs.microsoft.com/en-us/azure/azure-functions/functions-monitoring?tabs=cmd

@MayankBargali-MSFT , feature request was made.
Thanks.
https://github.com/Azure/azure-powershell/issues/12395


feature: do not delete user input in case sending fails

In case the sending callback function returns "false",
then sending the message is regarded as failed. In such cases
the user input field is not deleted. Then the user might try
to resolve sending issues and try again, without loosing
its message.
Previously the input field was deleted in any case.
If the message is sent to a remote server via network,
the network might be down currently and even on
purpose. Trying to send a message in that situation
had lead to losing the message.
Now, the message is retained until the callback to send
the message returns. The return value is evaluated
for any sign of success. On success, the input field is
cleared and in failure, its content is maintained.

thanks for the contribution!


Sorting results

Tables in alpha order
Columns by ordinal_position

LGTM

Once this is merged, you should tag it v1.0.3.

Thanks @foresmac. Will do.


Using operating system build number is not a good way to build a Windows 10 collection. Build 10240 is Windows 10 1507.

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 08d16473-db61-23bd-7201-f5d7d6a56cc8
Version Independent ID: 468238c8-8fb4-3dff-3485-07daab0c7833
Content: Onboard to the Microsoft Defender ATP service - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-atp/onboarding.md
Product: w10
Technology: windows
GitHub Login: @mjcaparas
Microsoft Alias: macapara

Hello @kimoppalfens ,
could you please clarify why it is not a good way?
Onboarding using configuration manager is supported since Windows 10 1607, so you can create a collection which includes all versions starting with 14393 (which is 1607), as it is described in the article.
Seems pretty good way for me.
Thank you

IIRC, back when I wrote my remark the page said to create a collection for the build version to be equal to 14393, not greater than. As a result now uptodate devices would enroll.

oh, ok, I see now)
Dear @nam31 , I believe the issue could be closed.
Thank you


android: Show message formatting options in compose text input menu bar.

https://cl.ly/d4ecff026e77

Eg: Like bold, and italic menu options shown in the above image.
This will help in formatting message and improve message composing experience.
@zulipbot claim
Let's first focus on #2823, because it requires changes in the RN.

BTW this can also be used in writing markdown 😄
https://cl.ly/05a8ebf7998e

Yeah, but this not being such a key part of the app, and people that write bold/italics on the web app will just try using the *s to do the effect, I don't think it is that important (even if RN supported customizing the context menus by default)


bug: almost empty issue list

The problem found in https://github.com/kezhenxu94/mini-github/issues/6 seems not fixed.

Fixed in the latest version, thanks for reporting bug 😄


Autoselect ComboBox value

If the selection is empty and the user typed an exact match of the option select that option on loss of focus.

https://github.com/adobe/react-spectrum/issues/6275

https://theappsmith.slack.com/archives/C025SE88KNE/p1726755300388869


Require APIClient :scope when using :google_app_default

/cc @tbetbetbe

Coverage decreased (-0.04%) to 93.23% when pulling e68cef7324fad4203011dadb471eec41bea171f1 on remi:require-scopes-with-google_app_default into da25513e06a388f1a0e1a771ae70bc85fa319e02 on google:master.

Coverage decreased (-0.04%) to 93.23% when pulling e68cef7324fad4203011dadb471eec41bea171f1 on remi:require-scopes-with-google_app_default into da25513e06a388f1a0e1a771ae70bc85fa319e02 on google:master.


NTR: specimen collection duration in days or nights

Variable with integer value. What we are recording here is not really the actual duration the trap is set for, but the number of daily collection cycles it is trapping for.  E.g. if traps work at night because mosquitoes are active at night, and you leave it out overnight, that counts as one "day".
old ID:
VBcv_0001009

let's make this more general: specimen collection duration

let's make this more general: specimen collection duration


doc: Fix make in nix-shell

Motivation for this change
When running make manually, makeFlags will not be passed. Let’s just use an environment variable.
Fixes: https://github.com/NixOS/nixpkgs/issues/124743
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[ ] Fits CONTRIBUTING.md.

You can simplify the manual as well https://nixos.org/manual/nixpkgs/unstable/#chap-contributing

Thanks. Done.


Update container publish to push to correct tag

As a Software Engineer, I need to be able to push container images to the correct container name within the hematite/python-base environment

fixed


Feature/release 13 1

Critical Changes
Send Case to Command added fields
Add Dashboards
Feature Request: Warning Conditionally Displayed on Case when Sailor field is empty
Fix Ombudsman Registry Activities Report
Global action for admin/pro dev duties
Hide Log a Call, replace always with Log an Interaction
Homepage Help Component
Lead Fields and Related Items
New Case Email should automatically create an Interaction
OCC Help and Training Page Change Links
OCC Help and Training Page Change Text
Remove Red Cross from Case Reason Picklist
Remove Red Cross from Interaction (Task) page layouts
Sailor First/Middle/Last Name and Suffix plus update WFR to update Name field
Changes
Issues Closed
Unaggregated Pull Requests

Remove Red Cross from Case Reason Picklist [PR148]
Total Count Dashboard [PR147]
Send Case to Command added fields [PR162]
Update cumulusci.yml [PR167]

@Nickers3 - Was just spinning up a scratch org to (finally, sorry...) work on approving some of 1.3. I got this error:
2021-08-02 10:51:40: Exception in task dependencies.add_standard_value_set_entries_leadstatus
LeadStatus standard value set entries require the key 'converted'

@mkolodner was this via Metecho or CCI?

It was via CCI

OK.  @mkolodner will test on my end to see if I can reproduce the error.

@mkolodner it worked for me:
Running task: add_standard_value_set_entries_leadstatus
2021-08-02 10:24:58: ------------------------------------------------------------
2021-08-02 10:24:58:
2021-08-02 10:25:00: Options:
2021-08-02 10:25:00:   api_names:
2021-08-02 10:25:00:     - LeadStatus
2021-08-02 10:25:00:   managed: False
2021-08-02 10:25:00:   namespace_inject: ombudcare
2021-08-02 10:25:00:   entries:
2021-08-02 10:25:00:     - {'label': 'New', 'fullName': 'New'}
2021-08-02 10:25:00:     - {'label': 'New by Sailor', 'fullName': 'New by Sailor'}
2021-08-02 10:25:00:     - {'label': 'Other Commands', 'fullName': 'Other Commands'}
2021-08-02 10:25:00:     - {'label': 'Requires Family Follow-up', 'fullName': 'Requires Family Follow-up'}
2021-08-02 10:25:00:     - {'label': 'Sailor Confirmation', 'fullName': 'Sailor Confirmation'}
2021-08-02 10:25:00:     - {'label': 'Prospective Families', 'fullName': 'Prospective Families'}
2021-08-02 10:25:01: Beginning task: AddValueSetEntries
Mind trying a branch refresh and see if that solves the issue.

@Nickers3  Still errored. Here's the stacktrace:
2021-08-02 11:50:29: Running task: add_standard_value_set_entries_salutation
2021-08-02 11:50:29: ------------------------------------------------------------
2021-08-02 11:50:29:
2021-08-02 11:50:29: Options:
2021-08-02 11:50:29:   api_names:
2021-08-02 11:50:29:     - Salutation
2021-08-02 11:50:29:   managed: False
2021-08-02 11:50:29:   namespace_inject: ombudcare
2021-08-02 11:50:29:   entries:
2021-08-02 11:50:29:     - {'label': 'Mx.', 'fullName': 'Mx.'}
2021-08-02 11:50:30: Beginning task: AddValueSetEntries
2021-08-02 11:50:30:
2021-08-02 11:50:30: Extracting existing metadata...
2021-08-02 11:50:30: Pending
2021-08-02 11:50:31: [Done]
2021-08-02 11:50:32: Loading transformed metadata...
2021-08-02 11:50:32: Beginning task: Deploy
2021-08-02 11:50:32: As user<EMAIL_ADDRESS>2021-08-02 11:50:32: In org: 00D2D000000E8VK
2021-08-02 11:50:32:
2021-08-02 11:50:32: Stripping namespace tokens from metadata for unmanaged deployment
2021-08-02 11:50:32: Cleaning meta.xml files of packageVersion elements for deploy
2021-08-02 11:50:32: Payload size: 904 bytes
2021-08-02 11:50:32: Pending
2021-08-02 11:50:33: [Pending]: next check in 1 seconds
2021-08-02 11:50:34: [Done]
2021-08-02 11:50:35: [Success]: Succeeded
2021-08-02 11:50:35: ------------------------------------------------------------
2021-08-02 11:50:35: Running task: add_standard_value_set_entries_leadstatus
2021-08-02 11:50:35: ------------------------------------------------------------
2021-08-02 11:50:35:
2021-08-02 11:50:43: Options:
2021-08-02 11:50:43:   api_names:
2021-08-02 11:50:43:     - LeadStatus
2021-08-02 11:50:43:   managed: False
2021-08-02 11:50:43:   namespace_inject: ombudcare
2021-08-02 11:50:43:   entries:
2021-08-02 11:50:43:     - {'label': 'New', 'fullName': 'New'}
2021-08-02 11:50:43:     - {'label': 'New by Sailor', 'fullName': 'New by Sailor'}
2021-08-02 11:50:43:     - {'label': 'Other Commands', 'fullName': 'Other Commands'}
2021-08-02 11:50:43:     - {'label': 'Requires Family Follow-up', 'fullName': 'Requires Family Follow-up'}
2021-08-02 11:50:43:     - {'label': 'Sailor Confirmation', 'fullName': 'Sailor Confirmation'}
2021-08-02 11:50:43:     - {'label': 'Prospective Families', 'fullName': 'Prospective Families'}
2021-08-02 11:50:44: Beginning task: AddValueSetEntries
2021-08-02 11:50:44:
2021-08-02 11:50:44: Extracting existing metadata...
2021-08-02 11:50:44: Pending
2021-08-02 11:50:44: [Pending]: next check in 1 seconds
2021-08-02 11:50:46: [Done]
2021-08-02 11:50:47: Exception in task dependencies.add_standard_value_set_entries_leadstatus
LeadStatus standard value set entries require the key 'converted'
Run this command for more information about debugging errors: cci error --help
michaelkolodner@Michaels-MBP OmbudsmanCloudCare % cci error info
Traceback (most recent call last):
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/cli/cci.py", line 78, in main
cli(args[1:], standalone_mode=False, obj=runtime)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/click/core.py", line 829, in call
return self.main(*args, **kwargs)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/click/decorators.py", line 21, in new_func
return f(get_current_context(), *args, **kwargs)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/cli/runtime.py", line 176, in new_func
func(runtime, *args, **kw)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/cli/flow.py", line 158, in flow_run
coordinator.run(org_config)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/core/flowrunner.py", line 422, in run
self._run_step(step)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/core/flowrunner.py", line 463, in _run_step
raise result.exception  # PY3: raise an exception type we control from this exception instead?
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/core/flowrunner.py", line 250, in run_step
task()
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/core/tasks.py", line 149, in call
self.result = self._run_task()
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/tasks/metadata_etl/base.py", line 171, in _run_task
self._transform()
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/tasks/metadata_etl/base.py", line 336, in _transform
transformed_xml = self._transform_entity(tree, unquoted_api_name)
File "/usr/local/Cellar/cumulusci/3.40.1/libexec/lib/python3.9/site-packages/cumulusci/tasks/metadata_etl/value_sets.py", line 56, in _transform_entity
raise TaskOptionsError(LEAD_STATUS_ERR)
cumulusci.core.exceptions.TaskOptionsError: LeadStatus standard value set entries require the key 'converted'
michaelkolodner@Michaels-MBP OmbudsmanCloudCare %

Not sure this helps… but I was able to create a scratch org in Metecho.
Warmly,
Mary

On Aug 2, 2021, at 7:53 AM, Michael Kolodner @.***> wrote:

@Nickers3 - Was just spinning up a scratch org to (finally, sorry...) work on approving some of 1.3. I got this error:
2021-08-02 10:51:40: Exception in task dependencies.add_standard_value_set_entries_leadstatus
LeadStatus standard value set entries require the key 'converted'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks for checking @marycrow!  Seems to be a CCI specific issue then.  @mkolodner are you using the dev_org flow?

Yes, dev_org flow

OK.  @mkolodner, since I can't reproduce on my end, can you test via Metecho?  We can confirm it works via CCI once merged into master and we are running the beta installs.

@lauraetzler @marycrow @mkolodner wanted to see if you all have had a chance to test in Metcho yet?  Any issues or are we ready to move into the beta packaging phase?

I have someone spinning up an epic scratch org now! Do they create a new
branch or use an existing branch?
-Laura
On Thu, Aug 12, 2021, 4:33 PM Nickers3 @.***> wrote:

@lauraetzler https://github.com/lauraetzler @marycrow
https://github.com/marycrow @mkolodner https://github.com/mkolodner
wanted to see if you all have had a chance to test in Metcho yet? Any
issues or are we ready to move into the beta packaging phase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Community/OmbudsmanCloudCare/pull/163#issuecomment-897948542,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASO6ESF2GISMAJHARUY44DLT4QVX7ANCNFSM47VGGZXA
.
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&utm_campaign=notification-email
.

@lauraetzler good question.  The epic org should work right off of the main feature/release-13-1 branch.  If we end up needing to make changes I believe we need to create a new task which would create a new branch and we'd then merge up to the release.

Ok. I will let them know!
On Fri, Aug 13, 2021, 1:49 PM Nickers3 @.***> wrote:

@lauraetzler https://github.com/lauraetzler good question. The epic org
should work right off of the main feature/release-13-1 branch. If we end up
needing to make changes I believe we need to create a new task which would
create a new branch and we'd then merge up to the release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Community/OmbudsmanCloudCare/pull/163#issuecomment-898623381,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASO6ESHDB3UUJMC6D5JBMNDT4VLJXANCNFSM47VGGZXA
.
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&utm_campaign=notification-email
.

Thanks for the contribution! Unfortunately we can't verify the commit author(s): sirgeoffrey<EMAIL_ADDRESS>One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce.com Contributor License Agreement and this Pull Request will be revalidated.

@Nickers3 do you know who this person is and why they're listed as an author for the commit?

@coriobriensfdo I've been doing some commits today to fix a bug and getting the error message upon commit.  I know I have a CLA signed and actually clicked to validate today on one of the commits.

@coriobriensfdo I've been doing some commits today to fix a bug and getting the error message upon commit. I know I have a CLA signed and actually clicked to validate today on one of the commits.

Did a person with the handle of sirgeoffrey help you on any of the commits?

Isn’t that the GitHub user identity?
Warmly,
Mary

On Aug 17, 2021, at 3:02 PM, coriobriensfdo @.***> wrote:

@coriobriensfdo I've been doing some commits today to fix a bug and getting the error message upon commit. I know I have a CLA signed and actually clicked to validate today on one of the commits.
Did a person with the handle of sirgeoffrey help you on any of the commits?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Yeah, @marycrow, sirgeoffrey is the automation user behind all of the github automation magic.

@davidmreed any idea why we'd be getting a CLA missing notification on this branch?  We did some commits to got an error related to the automated sirgeoffrey user.

Yeah, @marycrow, sirgeoffrey is the automation user behind all of the github automation magic.

Oh, hmmmmmm ok let me take a look.

@davidmreed any idea why we'd be getting a CLA missing notification on this branch? We did some commits to got an error related to the automated sirgeoffrey user.

@Nickers3 I manually removed the cla:missing label as it doesn't apply in this case, so can you try again?

@davidmreed any idea why we'd be getting a CLA missing notification on this branch? We did some commits to got an error related to the automated sirgeoffrey user.

@Nickers3 I manually removed the cla:missing label as it doesn't apply in this case, so can you try again?

I've also asked my contact on the SFDC Open Source team that is responsible for the bot to chime in. Fingers crossed we can resolve this shortly. @jimjag

@coriobriensfdo @jimjag after the approval, the sirgeoffrey commits are not passing the Salesforce cla check.  Does the sirgeoffrey bot have to accept the cla agreement to make it valid?

@davidmreed any idea why we'd be getting a CLA missing notification on this branch? We did some commits to got an error related to the automated sirgeoffrey user.

@Nickers3 I manually removed the cla:missing label as it doesn't apply in this case, so can you try again?

I've also asked my contact on the SFDC Open Source team that is responsible for the bot to chime in. Fingers crossed we can resolve this shortly. @jimjag

@Nickers3 Jim said that if there are branch conflicts that need to be fixed, and once done he should be able to resolve the error. Do you see where the conflicts are?

@coriobriensfdo @jimjag after the approval, the sirgeoffrey commits are not passing the Salesforce cla check. Does the sirgeoffrey bot have to accept the cla agreement to make it valid?

I haven't seen that before..... @jimjag have you?

Hello again! My tester ran into this error message when she tried to spin
up a scratch org (it stopped the process partway through.)
Error- 'LeadStatus standard value set entries require the key 'converted'.
Is it possible that we failed to keep "Converted" as a Lead status?
On Thu, Aug 12, 2021 at 6:30 PM Laura Etzler @.***>
wrote:

I have someone spinning up an epic scratch org now! Do they create a new
branch or use an existing branch?
-Laura
On Thu, Aug 12, 2021, 4:33 PM Nickers3 @.***> wrote:

@lauraetzler https://github.com/lauraetzler @marycrow
https://github.com/marycrow @mkolodner https://github.com/mkolodner
wanted to see if you all have had a chance to test in Metcho yet? Any
issues or are we ready to move into the beta packaging phase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Community/OmbudsmanCloudCare/pull/163#issuecomment-897948542,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASO6ESF2GISMAJHARUY44DLT4QVX7ANCNFSM47VGGZXA
.
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&utm_campaign=notification-email
.

@lauraetzler I was doing some work on the lead status missing converted last week so I think I resolved this.  I did a test run via Metecho this morning by creating a scratch org on the feature 1.3 epic and it worked.  Mind seeing if they can create an org now?

Well, mine works, so that's good news. I just asked my tester to try again
as well!
-Laura
On Wed, Aug 25, 2021 at 10:14 AM Nickers3 @.***> wrote:

@lauraetzler https://github.com/lauraetzler I was doing some work on
the lead status missing converted last week so I think I resolved this. I
did a test run via Metecho this morning by creating a scratch org on the
feature 1.3 epic and it worked. Mind seeing if they can create an org now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Community/OmbudsmanCloudCare/pull/163#issuecomment-905538656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASO6ESA4KET4MYPYMS7AOADT6T3DLANCNFSM47VGGZXA
.
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&utm_campaign=notification-email
.

@coriobriensfdo @jimjag after the approval, the sirgeoffrey commits are not passing the Salesforce cla check. Does the sirgeoffrey bot have to accept the cla agreement to make it valid?

I haven't seen that before..... @jimjag have you?

Any progress here?  We're looking to do a beta version of the package today and the cla-missing s a barrier for us to complete the merge.

@coriobriensfdo @jimjag after the approval, the sirgeoffrey commits are not passing the Salesforce cla check. Does the sirgeoffrey bot have to accept the cla agreement to make it valid?

I haven't seen that before..... @jimjag have you?

Any progress here? We're looking to do a beta version of the package today and the cla-missing s a barrier for us to complete the merge.

Bah sorry, they may not have seen the notifications. I've pinged them both on our internal Slack. I'll ping back as soon as I have a resolution. Sorry for the delay!

@Nickers3 I've been told that one of our org Admins (@davidmreed) can remove the CLA check that shouldn't be there, but you'll need to resolve the merge conflicts before it can be merged. Are you already working on those conflicts?

thanks for the update @coriobriensfdo.  We're working through the conflicts now so hopefully by the time we're done with the conflicts, the cla missing could be removed.

thanks for the update @coriobriensfdo. We're working through the conflicts now so hopefully by the time we're done with the conflicts, the cla missing could be removed.

And just a heads up @Nickers3 that the CLA check wasn't a requirement to fulfil technically. The conflicts prevent the merge, but once they were resolved you could have technically merged (or so I'm told ;) )

@coriobriensfdo cool.  We have the conflicts resolved and running the feature test as we speak so once that runs I'll try to merge and let you know if we run into anything.

I set the PR to auto-merge when feature test completes.

Looks like the conflict merging caused an error.  Will debug and fix.


combine target data

avoid separate target data files per output type group

This pull request would do 2 things:

Add examples with an output_type of "cdf".  Resolves issue #13
Create a single, unified data file with target values.  It's unclear whether this is where we are really headed with target values long term, but this is an improvement over what's in the repository now.

The submission validations are failing for a few reasons: we are modifying existing files, we are submitting outside of the time range corresponding to the forecast rounds specified in the file names, and there is a bug in hubValidations checks related to increasing order of probabilities at cdf evaluation points.  I've filed an issue on hubValidations for the third of these, and the first two are expected given that we're creating post hoc examples.