Need to make all 9 tests in test1.yaml work on derecho

I tried to run the workflow for the standard tests on derecho, but all failed for me!
Here is what I did:

I am in the develop branch of MPAS-Workflow after cloning the workflow.
Then do 'source env-setup/machine.csh', as I use tcsh. Now I am in the Jim's Cylc-8 python env.
Then I type './test.csh', it produced a lot of warning or Error message below during submission, but should be Ok according to Tao.

Directory: /glade/work/liuz/pandac2024/MPAS-Workflow
setenv: Variable name must contain alphanumeric characters.
./submit.csh (INFO): Generating the scenario-specific MPAS-Workflow directory
./submit.csh cd /glade/derecho/scratch/liuz/pandac/liuz_ForecastFromGFSAnalysesMPT_TEST/MPAS-Workflow
Directory: /glade/derecho/scratch/liuz/pandac/liuz_ForecastFromGFSAnalysesMPT_TEST/MPAS-Workflow
./submit.csh conda activate /glade/work/jwittig/conda-envs/my-cylc8.2

CondaError: Run 'conda init' before 'conda activate'

./submit.csh cylc version: 8.2.2
./submit.csh (INFO): checking if a suite with the same name is already running
./submit.csh (INFO): confirmed that a cylc suite named liuz_ForecastFromGFSAnalysesMPT_TEST is not already running
./submit.csh (INFO): starting a new suite...
./submit.csh cylcWorkDir /glade/derecho/scratch/liuz/cylc-run
./submit.csh SuiteName liuz_ForecastFromGFSAnalysesMPT_TEST
./submit.csh mainScriptDir /glade/derecho/scratch/liuz/pandac/liuz_ForecastFromGFSAnalysesMPT_TEST/MPAS-Workflow
./submit.csh cylc install --run-name=liuz_ForecastFromGFSAnalysesMPT_TEST
WorkflowFilesError: Failed to install from /glade/derecho/scratch/liuz/pandac/liuz_ForecastFromGFSAnalysesMPT_TEST/MPAS-Workflow: previous installations were from /glade/derecho/scratch/liuz/pandac/liuz_3dvar_OIE120km_WarmStart_TEST/MPAS-Workflow
./submit.csh cylc validate MPAS-Workflow/liuz_ForecastFromGFSAnalysesMPT_TEST
WARNING - deprecated items were automatically upgraded in "workflow definition"
WARNING -  * (8.0.0) [visualization] - DELETED (OBSOLETE)
WARNING -  * (8.0.0) [scheduling]max active cycle points -> [scheduling]runahead limit - "4" -> "P3"
WARNING -  * (8.0.0) [runtime][Clean][job]execution retry delays -> [runtime][Clean]execution retry delays - value unchanged

I see one problem with cold-start test cases is the obs2ioda.x issue, as noted in this issue https://github.com/NCAR/MPAS-Workflow/issues/261, but do not know why other tests all failed or stopped from cylc log files in /glade/u/home/liuz/cylc-run/MPAS-Workflow. Note that I did not change anything in the workflow, just using the current settings of paths.

Anyone recently tried the workflow with test.csh? Am I missing something in the steps I listed.
We'd better make all standard tests work on derecho with 2.1 code.

Hi Jake, Would you please copy my .cylc/flow/global.cylc on my home dir to your global.cylc first?

Thank you @junmeiban . It seems running after copying your global.cylc file below.
[platforms]
    # The localhost platform is available by default
    # [[localhost]]
    #     hosts = localhost
    #     install target = localhost
    [[pbs_cluster]]
        hosts = localhost
        job runner = pbs
        install target = localhost
    [install]
       [[symlink dirs]]
          [[[localhost]]]
            run = /glade/derecho/scratch/$USER/

My previous global.cylc copied from Tao, which missed the symlink part, so cylc-run was under 'home' instead of 'scratch' space. But it was consistent with the online README of the workflow document.
@jim-p-w Can you update online readme for the global.cylc file? Also README should mention the step to 'source machine.csh/sh'. There was a step to 'source cheyenne.csh' in the old readme. It is missing in the current readme.

Does anyone have a newly-compiled obs2ioda.x somewhere on derecho to fix the issue https://github.com/NCAR/MPAS-Workflow/issues/261?

Please find my obs2ioda-v2.x under /glade/work/taosun/Derecho/MPAS/Obs2IODA/src

In cylc 8, we can use cylc tui $workflow-id to check the status of a running suite.

@mos3r3n We should use the standard version of obs2ioda instead of your modified version. @zhumingying may have one build code of obs2ioda as she recently ran some obs conversion.

@liujake Regarding the README file in the develop branch, I think the steps are correct.
It is no longer necessary to source env-setup/machine.csh or env-setup/machine.sh.
The symlink section of the $HOME/.cylc/flow/global.cylc is optional. If you don't have that section, data files will be created in $HOME, but the workflows should run (assuming there's room in $HOME).
Note the cylc configuration file in $HOME/.cylc now needs to be in a subdirectory called flow, and is now named global.cylc,
so the config file has changed from $HOME/.cylc/global.rc to $HOME/.cylc/flow/global.cylc

@jim-p-w Yes. I have global.cylc under $HOME/.cylc/flow. But if no having 'optional' symlink section, my test.csh failed. With this section, it worked Ok with apparently 6 of 9 successful. 2 failed ColdStart ones below are due to the old obs2ioda.x used:
3dvar_O30kmIE60km_ColdStart_TEST
liuz_3dvar_OIE120km_ColdStart_TEST

Another failing one is
3denvar_O30kmIE60km_WarmStart_TEST

in the DA step, but without an error message in
/glade/derecho/scratch/liuz/pandac/liuz_3denvar_O30kmIE60km_WarmStart_TEST/CyclingDA/2018041500/run/mem001/jedi.log

So you can run test.csh successfully (e.g., 6 of 9) without the symlink section in your global.cylc?

@jim-p-w 'source env-setup' is to activate your python environment with cylc-8 installation. I do not understand why it is optional? You meant we can use the standard CISL python env or spack-stack's python env? If so, we still need to inform in the README that what/how to load those python/cylc-8 environment before run test.csh, right?

@liujake The scripts and python code set up the environment. It is loading the cylc 8 environment installed in /glade/work/jwittig/conda-envs/my-cylc8.2
I am running a bash shell, I will need to retest running tcsh. That won't happen till tomorrow (it can take a day for a new shell to get set up on derecho using SAM).
I am running w/o the symlink section in ~/.cylc/flow/global.cylc, and the workflows are running. This will also take a while for results, all of my jobs being submitted to compute nodes are stuck in the queue.

I have not compiled obs2ioda-v2 in Derecho. I processed observations in
Casper using the old executable obs2ioda-v2.x, which was compiled in
Cheyenne and worked well in Casper.
On Mon, Jan 22, 2024 at 2:13 PM Zhiquan (Jake) Liu @.***>
wrote:

Assigned #278 https://github.com/NCAR/MPAS-Workflow/issues/278 to
@zhumingying https://github.com/zhumingying.
—
Reply to this email directly, view it on GitHub
https://github.com/NCAR/MPAS-Workflow/issues/278#event-11562063335, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFASISMJCHOGZQA6HU4YFVDYP3I63AVCNFSM6AAAAABCF36EUCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGU3DEMBWGMZTGNI
.
You are receiving this because you were assigned.Message ID:
@.***>

Hi @liujake, my global.cylc (in /glade/u/home/ivette/.cylc/flow) does not contain the symlink section and the experiments are running successfully:
    # The localhost platform is available by default
    # [[localhost]]
    #     hosts = localhost
    #     install target = localhost
    [[pbs_cluster]]
        hosts = localhost
        job runner = pbs
        install target = localhost

One thing I should point out is that I added the lines below to my .bashrc, which seems to be enough to be able to submit the suites, given that it loads the right python environment. We may need to revisit this in the Readme and the machine.sh/machine.csh script.
export CYLC_ENV=/glade/work/jwittig/conda-envs/my-cylc8.2
source /etc/profile.d/z00_modules.sh
module purge
module load ncarenv/23.09
module load conda/latest

conda activate $CYLC_ENV

I ran the test 3denvar_O30kmIE60km_WarmStart_TEST and it seems to fail because of memory issues. In the scenario yaml (test/testinput/3denvar_O30kmIE60km_WarmStart.yaml) we specify memory: 45GB, which overwrites the default value (235GB) in scenarios/defaults/variational.yaml. I ran another test removing that part from that test scenario yaml file and it completed successfully. We should open a PR to fix this.
Regarding the ColdStart tasks, I made a new compilation on Cheyenne (to solve the issue https://github.com/NCAR/MPAS-Workflow/issues/261) that seems to be working on Derecho. I just ran 3dvar_OIE120km_ColdStart_TEST and it worked correctly using the obs2ioda executable in /glade/campaign/mmm/parc/ivette/pandac/fork_obs2ioda/obs2ioda/obs2ioda-v2/src. You can take a look at my results in /glade/derecho/scratch/ivette/pandac/ivette_3dvar_OIE120km_ColdStart_TEST_2/Observations/2022020106.

@ibanos90 Thanks for testing and fixing the issues. Feel free to make a PR with your fixes.

And It is a mystery to me about whether we need symlink section in global.cylc.

And It is a mystery to me about whether we need symlink section in global.cylc.

Yeah, I don't understand it either. I think it should be fine as long as we have space in the home directory.

Yes, I tried to run the experiment of O30kmIE60km with CrIS, it failed on
forecast if we use default setting of 1X128 or 2X128 processors, we need to
set:
forecast:
job:
30km:

  nodes: 1

  PEPerNode: 128

  memory: 235GB

Job ID    User    Queue Nodes NCPUs NGPUs Finish Time  Req Mem Used
Mem(GB)  Avg CPU (%) Elapsed ( h) Job Name
2855797 zhuming   cpu      1   128     0 01-19T12:02     45.0         45.0
26.6      0.01  Forecast1.20180424T1200Z.MPAS-Worflow
2885135   zhuming    cpu     2   256     0 01-22T16:56     90.0
90.0         43.5         0.01
Forecast1.20180425T0000Z.MPAS-Workflow-zhuming_3dhybrid-60-60-iter_O30kmI60km_VarBC_bnd_iasi_cris
2881537   zhuming     cpu     1   128     0 01-22T11:49    235.0
133.9        100.0         0.28
Forecast1.20180424T1800Z.MPAS-Workflow-zhuming_3dhybrid-60-60-iter_O30kmI60km_VarBC_bnd_iasi_cris
2887419   zhuming      cpu     2   256     0 01-22T21:26    470.0
140.4        100.0         0.10
Forecast1.20180425T0600Z.MPAS-Workflow-zhuming_3dhybrid-60-60-iter_O30kmI60km_VarBC_bnd_iasi_cris
Zhuming
On Tue, Jan 23, 2024 at 11:39 AM ibanos90 @.***> wrote:

Hi @liujake https://github.com/liujake, my global.cylc (in
/glade/u/home/ivette/.cylc/flow) does not contain the symlink section and
the experiments are running successfully:
# The localhost platform is available by default
# [[localhost]]
#     hosts = localhost
#     install target = localhost
[[pbs_cluster]]
    hosts = localhost
    job runner = pbs
    install target = localhost

One thing I should point out is that I added the lines below to my
.bashrc, which seems to be enough to be able to submit the suites, given
that it loads the right python environment. We may need to revisit this in
the Readme and the machine.sh/machine.csh script.
export CYLC_ENV=/glade/work/jwittig/conda-envs/my-cylc8.2
source /etc/profile.d/z00_modules.sh
module purge
module load ncarenv/23.09
module load conda/latest
conda activate $CYLC_ENV
I ran the test 3denvar_O30kmIE60km_WarmStart_TEST and it seems to fail
because of memory issues. In the scenario yaml (
test/testinput/3denvar_O30kmIE60km_WarmStart.yaml) we specify memory: 45GB,
which overwrites the default value (235GB) in
scenarios/defaults/variational.yaml. I ran another test removing that
part from that test scenario yaml file and it completed successfully. We
should open a PR to fix this.
Regarding the ColdStart tasks, I made a new compilation on Cheyenne (to
solve the issue #261 https://github.com/NCAR/MPAS-Workflow/issues/261)
that seems to be working on Derecho. I just ran
3dvar_OIE120km_ColdStart_TEST and it worked correctly using the obs2ioda
executable in
/glade/campaign/mmm/parc/ivette/pandac/fork_obs2ioda/obs2ioda/obs2ioda-v2/src.
You can take a look at my results in
/glade/derecho/scratch/ivette/pandac/ivette_3dvar_OIE120km_ColdStart_TEST_2/Observations/2022020106
.
—
Reply to this email directly, view it on GitHub
https://github.com/NCAR/MPAS-Workflow/issues/278#issuecomment-1906694816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFASISJO5IAGBCBUHZSEHPLYP77WJAVCNFSM6AAAAABCF36EUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGY4TIOBRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ibanos90  When I do a grep, I see other places with 45GB. You may want to fix them all in once.
initialize/applications/EnKF.py:      'memory': {'def': '45GB', 't': str},
initialize/applications/Forecast.py:      'memory': {'def': '45GB', 'typ': str},
initialize/applications/HofX.py:      'memory': {'def': '45GB', 'typ': str},
initialize/applications/RTPP.py:        'memory': {'def': '45GB', 'typ': str},
initialize/applications/Variational.py:      'memory': {'def': '45GB', 'typ': str},
initialize/config/Task.py:  maxMemPerNode = "45GB"
initialize/post/VerifyModel.py:      'memory': {'def': '45GB', 'typ': str},
initialize/post/VerifyObs.py:      'memory': {'def': '45GB', 'typ': str},
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/enkf.yaml:          # 16 x 8 PE x 2 omp : 90.5 min., 480 GB, 45GB/node
scenarios/defaults/enkf.yaml:          # 16 x 8 PE x 4 omp : 92.5 min., 480 GB, 45GB/node
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/enkf.yaml:          memory: 45GB
scenarios/defaults/rtpp.yaml:      memory: 45GB
scenarios/defaults/variational.yaml:          memory: 45GB
scenarios/defaults/variational.yaml:          ##memory: 45GB
test/testinput/3denvar_O30kmIE60km_WarmStart.yaml:          memory: 45GB
test/testinput/3dvar_O30kmIE60km_ColdStart.yaml:          memory: 45GB

And I do not know specifying memory is still necessary on derecho. Remember that we specify it as 45GB or 109GB on cheyenne because that will request the regular nodes or 'large-memory' nodes for a job. But all Derecho's nodes have the same 235GB memory. Perhaps we should simply comment out or remove those lines.

Hi @liujake, I just run the tests with ColdStart and they are completing successfully for me. I asked @junmeiban to run one of the ColdStart test and the Observations generation worked without issues, using the obs2ioda.x executable that is already specified in initialize/framework/Build.py. However, just to make sure, would you try one more time running one of the ColdStart tests using the current develop branch?

Ok. Then I am closing this issue.

Just double checked that all three 3dvar tests (out of 9 tests) pass.
They are 3dvar_OIE120km_WarmStart, 3dvar_OIE120km_ColdStart, and 3dvar_O30kmIE60km_ColdStart.

Just double checked that all three 3dvar tests (out of 9 tests) pass. They are 3dvar_OIE120km_WarmStart, 3dvar_OIE120km_ColdStart, and 3dvar_O30kmIE60km_ColdStart.

Great, thanks for letting us know!


Importing a restored DB

I currently have an aurora postgresql DB deployed with this module. If I create a new DB from a cluster snapshot, is it possible to use terraform with this module to import the new DB so that I can continue to manage the new DB via terraform?

yes @shmick ! you can set the snapshot_identifier variable to point to your snapshot, either the snapshot name or ARN are acceptable

Thanks for the info @bryantbiggs, I wasn't aware that you could create a new DB from a snapshot_identifier with this module.
That's really helpful!

anytime, happy to help!


run_circuit.py raises an error because of a changes in terra

Informations

Qiskit Aqua version: 0.4.2
Python version: Python 3.6.5
Operating system: Mac OS 10.13.6

qiskit/aqua/utils/run_circuits.py raises the following error because a file name qiskit/compiler/assemble_circuits.py has been changed to  qiskit/compiler/assembler.py in terra.
The following error showed up when I ran unit tests in test_clique.py of Qiskit Aqua.
ImportError: Failed to import test module: test_clique
Traceback (most recent call last):
  File "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
    module = __import__(module_name)
  File "/Users/matsuo/github/pr-integer/aqua-integer/test/test_clique.py", line 20, in <module>
    from test.common import QiskitAquaTestCase
  File "/Users/matsuo/github/pr-integer/aqua-integer/test/common.py", line 27, in <module>
    from qiskit.aqua import __path__ as qiskit_aqua_path
  File "/Users/matsuo/github/pr-integer/aqua-integer/qiskit/aqua/__init__.py", line 31, in <module>
    from .utils.backend_utils import (get_aer_backend,
  File "/Users/matsuo/github/pr-integer/aqua-integer/qiskit/aqua/utils/__init__.py", line 33, in <module>
    from .run_circuits import compile_and_run_circuits, find_regs_by_name
  File "/Users/matsuo/github/pr-integer/aqua-integer/qiskit/aqua/utils/run_circuits.py", line 27, in <module>
    from qiskit.compiler import assemble_circuits
ImportError: cannot import name 'assemble_circuits'

The following commit could be the related to the cause.
https://github.com/Qiskit/qiskit-terra/commit/65fd9d7a5e2fa868c55132b11f90f67102efab38
What is the current behavior?
The following ImportError raises.
ImportError: cannot import name 'assemble_circuits'
Steps to reproduce the problem
Run unit tests in test_clique.py of Qiskit Aqua.
What is the expected behavior?
assembler.py needs to be imported properly.
Suggested solutions
Change import's name from from qiskit.compiler import assemble_circuits to from qiskit.compiler import assembler

addressed in https://github.com/Qiskit/qiskit-aqua/pull/487


Set "VUE_APP_API_BASE_URL" environment variable from base image "crawlabteam/crawlab"

Is your feature request related to a problem? Please describe.
I am trying to run crawlab under a different base url, localhost/web1. Setting CRAWLAB_BASE_URL: "web1" and VUE_APP_API_BASE_URL: "web1"on the latest crawlabteam/crawlab image does not cause a change. I am forcing the change by updating docker-start-master.sh to be
if [ "${CRAWLAB_BASE_URL}" = "" ];
then
	:
else
	indexpath=/app/dist/index.html
	sed -i "s?/js/?${CRAWLAB_BASE_URL}/js/?g" ${indexpath}
	sed -i "s?/css/?${CRAWLAB_BASE_URL}/css/?g" ${indexpath}
fi

# start nginx
service nginx start

# start seaweedfs server
seaweedfsDataPath=/data/seaweedfs
if [ -e ${seaweedfsDataPath} ]; then
	:
else
	mkdir -p ${seaweedfsDataPath}
fi
weed server \
	-dir /data \
	-master.dir ${seaweedfsDataPath} \
	-volume.dir.idx ${seaweedfsDataPath} \
	-ip localhost \
	-volume.port 9999 \
	-filer \
	>> /var/log/weed.log 2>&1 &

https://gist.github.com/zerafachris/215bb1c3aabe262b65363e73731ca4b3.js
and
pulling the latest version of crawlab and updating crawlab/frontend/.env.docker to be VUE_APP_API_BASE_URL=/web1/api
Describe the solution you'd like
Is there a way to have VUE_APP_API_BASE_URL as an environment variable for base image "crawlabteam/crawlab" so I do not have to build from source every time?

I had a look at the code and proposed the following solution https://github.com/crawlab-team/crawlab/pull/1050

Took a look and it seems fine. Let me double check on develop branch.

Solution merged in https://github.com/crawlab-team/crawlab/pull/1050

Solution merged in https://github.com/crawlab-team/crawlab/pull/1050


Changing date prop of Calendar component not updating the Calendar UI

I've added a custom header to the calendar, where I'm allowing the change of date with prev and next buttons.
Clicking these buttons, the date is being updated and passed on to the Calendar component. But the Calendar UI remains the same. It does not change to the date. Swipping on the calendar works, but not via an external state.
Here is my code
import React, { useState } from 'react';
import { Calendar as BigCalendar } from 'react-native-big-calendar';

import CalendarHeader from './CalenderHeader';

export default function Calendar() {
  const [date, setDate] = useState<Date>(new Date());

  const handleDateChange = (updatedDate: Date) => {
    setDate(() => new Date(updatedDate));
  };

  return (
    <>
      <CalendarHeader date={date} onDateChange={handleDateChange} />
      <BigCalendar
        ampm
        mode="day"
        date={date}
        events={[
          {
            title: 'Meeting 0',
            start: new Date(date.getFullYear(), date.getMonth(), date.getDate() - 1, 3, 0),
            end: new Date(date.getFullYear(), date.getMonth(), date.getDate() - 1, 5, 0),
          },
          {
            title: 'Meeting',
            start: new Date(date.getFullYear(), date.getMonth(), date.getDate(), 10, 0),
            end: new Date(date.getFullYear(), date.getMonth(), date.getDate(), 11, 0),
          },
          {
            title: 'Coffee break',
            start: new Date(date.getFullYear(), date.getMonth(), date.getDate(), 4 + 12, 15),
            end: new Date(date.getFullYear(), date.getMonth(), date.getDate(), 4 + 12, 40),
          },
        ]}
        overlapOffset={100}
        height={680}
        renderHeader={() => null}
      />
    </>
  );
}

Here is the CalenderHeader
import React from 'react';
import { add as addDuration } from 'date-fns';

import { Text, Wrapper, Button } from '@flurn/pandora/components';
import { DateFormats, formatDate } from '@flurn/pandora/utils';

interface CalendarHeaderProps {
  date: Date;
  onDateChange: (date: Date) => void;
}

export default function CalendarHeader(props: CalendarHeaderProps): JSX.Element {
  const { date, onDateChange } = props;

  const handleDateChange = (change: number) => () => {
    onDateChange(addDuration(date, { days: change }));
  };

  return (
    <Wrapper justifyContent="space-evenly" flexDirection="row" alignItems="center" my={12}>
      <Button fullWidth={false} primary={false} label="< Prev" onPress={handleDateChange(-1)} />
      <Text bold>{formatDate({ date1: date.toString(), option: DateFormats.Day })}</Text>
      <Button fullWidth={false} primary={false} label="Next >" onPress={handleDateChange(+1)} />
    </Wrapper>
  );
}

This is happening on both Android and iOS. Tested on android device and iOS simulator.
Here is the behavior -
https://user-images.githubusercontent.com/12946926/127954631-3765fb86-8eb5-47f5-869b-8df198b2feea.mp4
In the above video, you can see that initially swiping on the screen takes me to the previous date. But when I try to click on the header buttons, I see a flicker but the current day calendar does not change.

Thanks for reporting.
Which platform are you trouble in? and how your CalendarHeader looks like?
It does not happen when I tried on the web - please check it the following files.

src: https://github.com/acro5piano/react-native-big-calendar/blob/master/stories/full-customization.stories.tsx
story: https://react-native-big-calendar.netlify.app/?path=/story/full-customization--main

Thanks

Thanks for reporting.
Which platform are you trouble in? and how your CalendarHeader looks like?
It does not happen when I tried on the web - please check it the following files.

src: https://github.com/acro5piano/react-native-big-calendar/blob/master/stories/full-customization.stories.tsx
story: https://react-native-big-calendar.netlify.app/?path=/story/full-customization--main

Thanks

I've tried it on both android and ios.

It's strange.

Just runned into this issue too, the date state coming from the context updates the Header component but not the Calendar component, any news?

It's the same thing with the mode prop, when I try to change its value with a variable, nothing changes, and the component defaults to the "week" mode.

Found out what I was doing wrong, I was trying to use the context on the component that was using the provider, that is why it was all undefined, the mode and date props are working properly on my android.


Add metrics tests

This PR does some cleaning jobs of metrics:
(1) Add time loggings for metrics related methods
(2) Reduce the heavy string operations by memorizing the result of escapePath
(3) Reduce the call for METRIC_REGISTRY.getGauges() since each getGauges call traverse the whole metrics and make a full copy of gauges.
(4) Add the MetricsStoreTest and MetricsSystemTest

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8210/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8211/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8217/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8221/
Test FAILed.

Tests in error:
alluxio.client.fs.FreeAndDeleteIntegrationTest.deleteDir(alluxio.client.fs.FreeAndDeleteIntegrationTest)
Run 1: FreeAndDeleteIntegrationTest.deleteDir:146 » TestTimedOut test timed out after...
Run 2: FreeAndDeleteIntegrationTest.deleteDir:148 » TestTimedOut test timed out after...
alluxio.job.master.JobMasterIntegrationTest.cancel(alluxio.job.master.JobMasterIntegrationTest)
Run 1: JobMasterIntegrationTest.cancel:246 » Timeout Timed out waiting for job 158163...
Run 2: JobMasterIntegrationTest.cancel:246 » Timeout Timed out waiting for job 158163...

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8225/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8226/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8228/
Test PASSed.

alluxio-bot, merge this please


setProfile not working.

i just found this library, addItem is working fine but when i use setProfile it doesn't work.
Cannot resolve method.
Error:(616, 9) error: cannot find symbol method setProfile(DrawerProfile)

setProfile() was removed in favor of addProfile().
In your case it should be replaced with:
clearProfiles();
addProfile();

I'll update the Readme 😉

@heinrichreimer Thanks alot !  Worked.


add gyro packaging

Hello! I'm working on a zig package manager called gyro, formerly known as zkg as I've added a proper packaging system involving a semi-centralized package index at astrolabe.pm.
With your blessing I'd love to add some packaging metadata so that this library can be added to the index (the package system uses semantic versioning where sub v1 versions aren't treated differently). The index has a concept of users, but I haven't added auth yet so I'm just manually curating and managing packages until I have that plugged in, so would you like me to publish this under the username kooparse?

Hi @mattnite, yes that's fine. I saw your project, I like it. Also, it would be nice to be able to brew install gyro on macOS! :-)

Hi @mattnite, yes that's fine. I saw your project, I like it. Also, it would be nice to be able to brew install gyro on macOS! :-)


Stale pid file when running on docker-compose

Hello I've got the following error message when running the container with docker-compose:
28/11/2019 -- 15:41:31 - <Error> - [ERRCODE: SC_ERR_INITIALIZATION(45)] - pid file '/var/run/suricata.pid' exists and Suricata appears to be running. Aborting!

I've found a work around by adding on docker-entrypoint.sh the following command:
SURICATA_PID=/var/run/suricata.pid

if [ -e ${SURICATA_PID} ]; then
    rm -f ${SURICATA_PID}
fi

But it will not work if the user specifies a different .pid file. Is there a better solution?

The latest version of this container does not create a pid file. Are you running an older version? Or have you modified it to drop a configuration file?

Hello, yes you are right I did some tests and in one of those I've set the pid in the configuration file, and forgot to remove it.
I've just re-tested right now disabling that setting and it worked like a charm. Sorry for wasting your time :)
While we are there do you think your container is suitable for production? I left it runnig with --af-packet for a day and it looks rock solid.

If you really need a pid file, keep in mind that if Suricata drops privileges (as this docker container will do by default provided the container as the required capabilities), Suricata is unable to cleanup the pid file itself as its owned by root. On research of this, it appears to be the correct "unix" thing to do. The systemd unit file we ship is smart enough to deal with, but this container doesn't use systemd.
One issue you might run into when using a pidfile, is that a stop and start of a container will lead to this stale pid file error.

While we are there do you think your container is suitable for production? I left it runnig with --af-packet for a day and it looks rock solid.

I don't see why its any less suitable than a package provided by a distribution and my default choice of build options satisfies your needs (I may add more build options by default). The images are also rebuilt nightly using Github Actions to make sure they are always based on the most recent base image with all updates, etc.


⚠ Bofrost.lu has degraded performance

In ddd7072, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2226 ms

Resolved: Bofrost.lu performance has improved in 33b5b12 after 13 minutes.


[BUG] 100% CPU usage with idle cache

Thank you for this library @maypok86
Description
Creating a cache leads to one core being utilized at 100%. Creating multiple caches bumps this by one core at a time.
To Reproduce
Steps to reproduce the behavior:
package main

import "github.com/maypok86/otter"

// We assign this so that we're sure it doesn't get garbage collected
var Cache *otter.Cache[string, string]

func main() {
	b, err := otter.NewBuilder[string, string](1_000)
	if err != nil {
		panic(err)
	}

	c, err := b.Build()
	if err != nil {
		panic(err)
	}

	Cache = c

	// Block forever
	select {}
}

Expected behavior
CPU usage is negligible.
Environment

OS: Both in Linux/Ubuntu and MacOS

Additional context
I believe the issue lies in the goroutine spawned here https://github.com/maypok86/otter/blob/main/cache.go#L74

Thank you for the issue! It's actually a very nasty problem that is caused by this loop here. Since we can't do the same as standard channels (aka gopark and etc). For now, I just added checking for queue emptiness and sending goroutine to wait by standard channels without serious performance loss.

@gzuidhof I think I fixed the bug. However, it is still unclear how to write a test that would cover this bug. Please let me know if it's fixed for you too.

Okay, I can't reproduce this bug anymore, so I'll close this issue.


Characters not appearing in 2nd release

I recently downloaded the second release and after setting it up, the characters, text boxes, and .webm backgrounds did not appear in OBS. The only thing that would appear was the "VS" and caster overlay. I understand this may be a simple error on my part, but I wanted to alert you nonetheless as I am reverting to the prior release for the time being.

Oh boy first issue! Unfortunately, I can't reproduce this one. That sounds like every element that needs to be changed isn't loading. V2 has changed all those methods to use more modern, native libraries, so I'll assume that's whats failing in your case. Are you using the latest version of OBS? (v25 as of now).

Yes, I'm using OBS v25.0.8.

Is it possible I need to update any JS libraries or any windows drivers?

That should all be handled by the chromium inside OBS. Also for the record, that issue also happens when the javascript doesn't load at all. Nowadays local files can't load javascripts by default for security reasons, but the OBS browser source will skip this (you can quickly test this by just opening the html files on your actual browser). But that would be weird because you said v1 worked for you.
You could always test if that's actually the problem here by opening a local server and telling the browser to look after the url of the local server + the file. You can easily do this with an IDE like Visual Studio Code or Atom and installing a local server extension. But yeah, this shouldn't be necessary.

That doesn't seem to be the problem. I attempted to use Streamlabs OBS to give it a shot, but the issue still remained. I don't know what else could be the issue, but no worries if it's not working out, I can just use V1.

Also, the regular overlay (not the vs screen) works and updates just fine.

I know what the problem is. I've been doing some tweaking with custom art and stuff, and I must've messed up the scripts file in the process. Apologies if I wasted any of your time!


Support Debezium

It would be very nice to have Debezium support with simple configuration options. Since the project has support for databases, Kafka and Zookeeper; it'd be nice to have changes stream through Debezium and play on scenarios easily.

Pull request welcome ;)


[Bug]: Invalid derivation path

Current Behavior
I am trying to connect Gnosis Safe with Ledger HD wallet using a custom derivation path for the Ethereum Classic chain (as well the Ethereum Classic Ledger App). When setting a custom derivation path m/44'/61'/0'/0/0, I receive the error m/44'/61'/0'/0/0 is not a valid derivation path.
This way I am not able to pick the account I want from Ledger.

I am sorry, if this is not the correct repo, but based on modal that is powered by Blocknative, I thought that this is a good candidate.
Expected Behavior
To connect with Ledger, getting the correct address from the Ledger's Ethereum Classic app.
Steps To Reproduce
No response
What package is effected by this issue?
@web3-onboard/ledger
Is this a build or a runtime issue?
Runtime
Package Version
xyz
Node Version
No response
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Anything else?
No response
Sanity Check

[X] If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.

hey @ziogaschr! Yes you are in the right spot! Does this only occur for you in Gnosis safe? Either way we'll take a look, if appropriate issue a fix, and update this issue with any details. 👍🏾
Thanks for pointing this out!

@ziogaschr we are supporting Gnosis as they update to Onboard v2 (renamed Web3-Onboard) and I believe they are in the later stages of final testing. I can confirm this feature does work properly on W3O(Onboard v2) and returns the proper ETHC address. I will update here as that transition progresses!

Thanks a lot for the updates.
@Adamj1232 is there an ETA you can share for when Gnosis Safe will release the new version with Onboard v2?

@ziogaschr I do not have an ETA but it seems they are moving along quickly. I will let you know when we hear about release with W3O support

Thanks a lot @Adamj1232

@ziogaschr We have released the fix for V1 and notified Gnosis. They said they are deprecating the current Safe and releasing a full rewrite at the beginning of October. That should help with this issue.
Since it will be handled on their end and we have the issue fixed and have notified platforms using Onboard I will close the issue for now. If any other issues arise please feel free to comment here. Thank you again!

Thanks @Adamj1232. Great support, you've done what possible at your end, thanks.


Unable to find element where attribute starts with a name

I cannot find a way to get elements with classes that starts with a name. ie:
$('[class^="value"]') <-- starts with string
$('[class$="value"]') <-- ends with string
$('[class~="value"]') <-- i believe this is the contains string version

Is this possibe?

Actually I found a solution on the cheerio repository
https://github.com/cheeriojs/cheerio/issues/811#issuecomment-180999819


Requesting support for BeagleBone AI-64 board

HI Team,
Really like the balena environment and keen to stay with it. We've been doing some initial work with RPi's which has been pretty good, but now we're moving to something with more power - BeagleBone AI-64.
Hoping you can advise if i can use existing beagle images, or failing that release a specific image for the BeagleBone AI-64 board.
Cheers,
Khan

Hi @KhanMechAI,
I'm sorry we missed this and didn't reply sooner! I was just looking at something else and noticed your message.
We are actually in process of adding the BeagleBone AI-64 now. It will take a bit more time, as there are some pieces missing from upstream Yocto meta-ti layers, but we're working on it. We can let you know here when it's added if you're still interested in making use of it!


Operator does not come up with latest yaml file in dev branch on vanilla k8

Describe the bug
Operator does not come up with latest yaml file in dev branch on vanilla k8
To Reproduce
Steps to reproduce the behavior:
Operator does not come up with latest yaml file in dev branch on vanilla k8
[root@kubespray1 ]# kubectl apply -f  ibm-spectrum-scale-csi-operator-dev.yaml
error: error validating "ibm-spectrum-scale-csi-operator-dev.yaml": error validating data: [ValidationError(Deployment.spec.template.spec.containers[0].securityContext): unknown field "hostIPC" in io.k8s.api.core.v1.SecurityContext, ValidationError(Deployment.spec.template.spec.containers[0].securityContext): unknown field "hostNetwork" in io.k8s.api.core.v1.SecurityContext, ValidationError(Deployment.spec.template.spec.containers[0].securityContext): unknown field "hostPID" in io.k8s.api.core.v1.SecurityContext]; if you choose to ignore these errors, turn validation off with --validate=false

Expected behavior
Operator should come up
Environment
[root@kubespray1 ]# kubectl get nodes
NAME         STATUS   ROLES    AGE    VERSION
kubespray1   Ready    master   320d   v1.14.3
kubespray2   Ready    <none>   320d   v1.14.3
kubespray3   Ready    <none>   320d   v1.14.3

The issue was following a CASE recommendation, I've since  commented it out.

Closing, after approval on PR from @Jainbrt


MemoryAllocationError calling midiInOpen

Stumbled into this issue while running it
Unhandled Exception: NAudio.MmException: MemoryAllocationError calling midiInOpen
   at NAudio.Midi.MidiIn..ctor(Int32 deviceNo)
   at MidiAccess.MidiInformation.GetInputDeviceWithName(String name)
   at MidiAccess.Controller..ctor(String inputDeviceName, String outputDeviceName)
   at nanoKontrol2OBS.Kontrol2OBS..ctor(String url, String password, LogEventHandler statusCallback, LogEventHandler warningCallback, LogEventHandler infoCallback)
   at ConsoleExecutable.Executable..ctor(String url, String password)
   at ConsoleExecutable.Executable.Main(String[] args)

Problem seems to originate from NAudio library.
https://github.com/naudio/NAudio
Seems like there is an issue with opening your MIDI-Device. Is more than 1 program trying to use it?
You need to download the KORG driver https://www.korg.com/us/support/download/product/0/159/ to be able to connect to KORG nanoKontrol2 with more than 1 program.

I have fixed by resinstalling it thanks


Stop talking like nerds in error messages

I recently came across this in PR 730 which exposes server-side errors in forms.

Can we make this error message and others like written as if users may see them? For example, "datastore" is an abstract concept. Perhaps a better error message would be...

This email address not recognized. Please enter the email associated with your kolide account.

This is no longer necessary


Errors on connect

Version
5.3.4
Browser and OS info
Safari 14.0.3 / Mac OS Big Sur 11.2.2
Steps to reproduce
Attempt to connect dev tools to app.
What is expected?
Successful connection.
What is actually happening?
Dev tools UI partially loads and the following console errors are printed:
[Error] Unhandled Promise Rejection: TypeError: null is not an object (evaluating 'record.rootInstance.VUE_DEVTOOLS_UID = rootId')
(anonymous function) (localhost:1261)
promiseReactionJob
[Error] Unhandled Promise Rejection: TypeError: null is not an object (evaluating 'ctx.currentAppRecord.id')
getComponentInstance (localhost:1500)
(anonymous function) (localhost:1425)
asyncFunctionResume
(anonymous function) (localhost:1715)
emit (localhost:11402)
_emit (localhost:3561)
forEach
(anonymous function) (localhost:3493)
(anonymous function) (localhost:7395)
(anonymous function) (localhost:13630)
(anonymous function) (localhost:13588)
(anonymous function) (localhost:7237)
(anonymous function) (localhost:7395)
(anonymous function) (localhost:13078)
(anonymous function) (localhost:7237)
(anonymous function) (localhost:7395)
(anonymous function) (localhost:14912)
(anonymous function) (localhost:13068)
(anonymous function) (localhost:7237)
(anonymous function) (localhost:7395)
(anonymous function) (localhost:7955)
(anonymous function) (localhost:7772)
(anonymous function) (localhost:7395)
(anonymous function) (localhost:8402)
(anonymous function) (localhost:8394)
(anonymous function) (localhost:9575)

No prior issues with this app until I wiped my hd and upgraded from older versions of Safari, devtools, and macOS (Catalina) to latest version for all three. Using <script src="http://localhost:8098"></script> in my <head> tag.

Devtools works as expected with a new Vue 3 app. The aforementioned project uses Vue 2.6.12.

Any updates on this? I'm getting the same errors


Question: Data parallel vs Split model training

The currently implemented setup allows to split the model across multiple GPUs by distributing the layers.
Is this approach prefered over having the same model on multiple GPUs and doing data parallel training by increasing the batch size?
What are pros and cons of the two approaches?

If doing data parallel training, you place multiple layers on a single GPU.  This works well if you have enough RAM to perform the computations of multiple layers all on a single GPU.  Otherwise you'll run out of memory quickly.  Just FYI; this kind of question is better suited for stack overflow or tensorflow discuss mailing list.


Add partial support for Stream commands

Adds support for the following commands not related to groups/consumers: XADD, XDEL, XLEN, XRANGE, XREVRANGE, XTRIM.

Nice, can you fix the tests?

Updated, apart from a couple of typos it was related to stream-node-max-entries config that we need to control for deterministic tests. I moved it from setUp and tearDown to the individual tests to just run them on supported versions.
The potential problem here is if you have one failure the config will never be reset for the test run (even worse locally: never). I could add try-catch blocks around the test, but if you can think of any better way to handle it I'm all ears

I've relaxed the permissions, so workflows always run 🥲

Thanks for the test fixes, I assume a re-run would resolve this. If they are too unable we can tweak them later. Thanks for the contribution!


Register a birth Libya

Trello card: https://trello.com/c/b4Gim4JW/210-30-june-changes-to-registering-a-birth-in-libya-content-change-request
Factcheck
Register a birth Libya
Expected Changes
URL on GOV.UK
* Selecting Libya should send you straight to an outcome
Before

After

@leenagupte could you please accommodate your commits to 50 chars for the title and 72 characters per line in the description

@pmanrubia Done.

Thank you @leenagupte. Still, the lines of the description are not 72 characters max. I guess you are doing it because Github is able to wrap it nicely, but there are other editors out there that are not that smart /user friendly (particularly terminal-based editors). So, I would follow the conventions until it is agreed that this is not necessary any more.

@pmanrubia Oops! I was in a rush and only did the titles. Fixed now.

Great work @leenagupte LGTM


Deprecate (0.6.x) and remove (master) CrossProject.settingSets

Link: CrossProject.settingSets
It was removed from Project in sbt 1.x: https://github.com/sbt/sbt/pull/3068/files#diff-de5d62c45e935f985b9d89ee74531dedL210

Fixed in #2867.


Add CCACHE support in CI

CCACHE is in fact already available, but a few cosmetic changes are required.
Most of the support is provided in the background by the gitlab-runner setup. You can see its effect on a few jobs where the cache was already built like all jobs on the AMD machine:
https://gitlab.com/ginkgo-project/ginkgo-public-ci/-/jobs/1166039002 (2 minutes to compile/test ginkgo core).
What this PR does on top of it:

Propagate some CCACHE environment variables set by gitlab-runner to ensure they are available/used
Review the way developer tools information is printed and add a bunch of CCACHE related information.

I will write a separate writeup on how this works behind the scene. Together with other CI improvements, our setup is quite complex so a general review document is long overdue at least for safekeeping...

@pratikvn that is already part of another PR, #721 I think. HIP sadly won't get any performance improvements due to their custom build system, but CUDA might :)

Is the CCACHE_DIR unique for different compiler and library?
Is the CCACHE_DIR read-only in these job? there is no race condition when two jobs with the same property compile.

The CCACHE DIR is read-write, the jobs need to update the cache to the last state.
In short:

CCACHE uses the build directories (fullpaths) in their hash: different jobs (which use different build directories) create different entries in CCACHE, see this link
CCACHE supports concurrent write, can be shared, and the default mode takes precaution against the few race conditions which can happen, see  this link.

About speedups on CUDA, see this job: https://gitlab.com/ginkgo-project/ginkgo-public-ci/-/jobs/1166112739
5 minutes to build Ginkgo with CUDA and OpenMP. The testing seems to take the most time now, probably because of contention on the CUDA card.


Recommendation: make sbatch output files follow same naming convention as other files

sbatch output files are named according to the type of analysis done. All other files have "0XX_" prefixes, which simplifies visualisation. The outputs could be renamed to follow the same convention.

done.


More ways to visualize neural networks

http://arxiv.org/abs/1603.02518

Closing stale issue: cleanup.


Iterator.Key() API no longer returns a copy of the key

Context
Closes #156.
Changes
Note: this is a breaking change.
The:

Iterator.Key() API implementations of levelDB, badgerDB, and pebbleDB no longer return a copy of the key.
Iterator.Value() API implementations of levelDB and pebbleDB no longer return a copy of the value.

Rather, as the updated docs reflect, the caller is responsible for creating a copy of the slice if they want to modify it.
See my further comments about rocksdb and badgerdb below.

Unfortunately, I don't think we can avoid the copy in rocksdb Key() implementation.
Under the hood, the library we use allocates and returns a C array, which is subject to C's memory resource policy.
But Go's memory management can't keep track of any memory allocated in the C library.
Therefore, to ensure there are no memory leaks call Free(), as the current implementation does.
In short, my understanding is that we need the copy of the key in order to free its memory allocated in the C library, thus avoiding possible memory leaks.

We can't avoid the copy in the Value() API of badgerDB either.
Namely, badgerDB exposes 2 APIs to retrieve a value:
func (item *Item) Value(fn func(val []byte) error) error
func (item *Item) ValueCopy(dst []byte) ([]byte, error)

Note:

Item.Value does not return the value. Instead, it wants a closure that works on it directly inside the library's boundaries. The Value method will call fn passing the value we want to retrieve as an argument []byte. To extract it we must do something like:var valueCopy []byte
err = item.Value(func(val []byte) error {
    // Make a copy of the value.
    valueCopy = append([]byte{}, val...)
    return nil
})

That is, we have to manually copy the value.
Item.ValueCopy creates a copy for us and returns it.

In both cases, the library returns as a copy of the original value; it offers no possibility of accessing the original value directly.

Given the discussion above, addressing #168 makes the library behave inconsistently depending on the underlying database used. Specifically, some databases require callers to make copies of key and value, while others do not. Consequently, users cannot switch between databases without first checking the behavior of their Key() and Value() APIs and adapting their code accordingly.

Note: this is a breaking change.

That's debatable because, in the Iterator documentation we say read-only []byte, although we don't mention anything about the lifetime of the pointer.

Note: this is a breaking change.

That's debatable because, in the Iterator documentation we say read-only []byte, although we don't mention anything about the lifetime of the pointer.

I see your point.
The Iterator interface docs states:
// As with DB, keys and values should be considered read-only, and must be copied before they are
// modified.

therefore, users of the library know that they must create a copy, thus these changes shouldn't break anything.

Could you add a changelog entry? btw we're using https://github.com/informalsystems/unclog


Time to parse N args scales quadratically with N, can result in very long parse times under certain conditions

Hello, I've been using this parsing library for a project I'm working on and I've come across a condition where the parsing function was taking a very long time to complete. With a large number of elements in the input arguments array (a few hundred at least), parsing was taking multiple minutes to complete. Having a few hundred argument array elements could probably be considered a weird edge case condition and the manner in which I'm using the library isn't exactly the same as the intended purpose of parsing command line app arguments, but I figured I'd bring it up anyway if it's considered worth further investigation.
I narrowed down the delay to definitely be within this libs code and not a behavior in my own code, but I wanted to also find out exactly how the parsing performance was scaling. I wrote up a simple C# project that demonstrates how an increasing number of arg array elements impacts the time it takes to parse from the array. The source code and an example of the results are below:
Repro Source (.Net Core 1.1 with CommandLineParser 2.1.1-beta)
CommandLineRepro.zip
Example

In writing this repro project, I also learned that the parsing time scales linearly with the number of public fields available in the target parse object (which sounds reasonable). The above example was performed with an arguments object that had only one field. To consider the results of an object that had 10 fields you could multiply those times by 10, in this scenario the time to parse would reach multiple seconds shortly after the args array exceeds 32 in length and will quickly ramp up from there.

I've noticed the same problem.
The main problem is that the library creates enumerables and then enumerate those multiple times.
I've created a fork where I fixed the problem.
https://github.com/deng0/commandline/commit/95ff7f6ca235bf0fb3778b6bb77b9e6f1193f058


Provide images for the arm64 architecture

What is currently missing?
First world problem, but it would be awesome to have arm64 images. The main use (for us) would be for development and integration testing on Apple silicone.
How could this be improved?
Add or modify the container build step to also produce arm64 images.
Is this a feature you would work on yourself?
If you support the idea, then yes. The change itself should be straight forward.
[x] I plan to open a pull request for this feature

I second this.
Curious if you've tried building the image in docker desktop for apple silicone. I've been able to successfully build other images using "platform: linux/amd64" in the docker compose and run them ok with what I believe is docker emulating the architecture. However, I get connection errors when trying to connect to this image from bitnami/kafka.

A quick test shows that building the image and starting the container works without any issues. Unfortunately I didn't have the time yet to set up a proper integration test


Authorization header 'Basic' invalid.

Please if you can help me why I always get this error the first time I call a function, the second time I run it then it works.
FileMaker Version: 18
Php Version : 7.4
This is a mistake:
{"messages":[{"message":"Request validation failed: Parameter (Authorization) is required","code":"10"}],"response":{}}
   BlueFeather\EloquentFileMaker\Exceptions\FileMakerDataApiException

  Authorization header 'Basic' invalid.

  at vendor/bluefeather/eloquent-filemaker/src/Services/FileMakerConnection.php:167
    163▕                             // API token is expired. We should expire it in the cache so it isn't used again.
    164▕                             $this->forgetSessionToken();
    165▕                             return;
    166▕                         default:
    167▕                             throw new FileMakerDataApiException($message['message'], $code);
    168▕                     }
    169▕                 }
    170▕             }
    171▕         } else{

      +7 vendor frames
  8   app/Console/Commands/SyncFileMakerDB.php:93
      Illuminate\Database\Eloquent\Model::__callStatic("count", [])

Thanks a lot for the reply.

What are the sequence of function calls you're doing in your PHP? Can you post your code block? It looks like the credentials are invalid, but I wouldn't expect it to work on your second call.

Thanks for reporting.
This is the connection in the .env file:
FM_DB_HOST = filemaker01.server
FM_DB_USERNAME = apirest
FM_DB_PASSWORD = vkjfkdjskfs

this is the database connection in database.php
        'DATABASENAME' => [
            'driver' => 'filemaker',
            'host' => env ('FM_DB_HOST', ''),
            'database' => 'DATABASENAME',
            'username' => env ('FM_DB_USERNAME', ''),
            'password' => env ('FM_DB_PASSWORD', ''),
            'prefix' => env ('FM_DB_PREFIX', ''),
            'version' => env ('FM_DB_VERSION', 'vLatest'),
            'protocol' => env ('FM_DB_PROTOCOL', 'https'),
        ],

DATABASENAME class
<? php

namespace App \ Models \ FileMaker \ DATABASENAME;

use App \ Traits \ FormatsAttributeNames;
use BlueFeather \ EloquentFileMaker \ Database \ Eloquent \ FMModel;
use Illuminate \ Database \ Eloquent \ Factories \ HasFactory;

class DATABASENAME extends FMModel
{
    use HasFactory;
    use FormatsAttributeNames;

    protected $ connection = 'DATABASENAME';
    protected $ layout = 'ApiLayout';

    protected $ fieldMapping = [
        'Article (1)' => 'Article',
        'Article2' => 'Article2',
        'BestellNr2' => 'Bestellnr_2',
    ];
}

and I have now created a command that synchronizes data from FileMaker to Mysql DB
protected $ signature = 'sync-filemaker-db {db}';

 public function handle ()
   {
       switch ($ this-> argument ('db')) {
           case 'DATABASENAME':
               $ this-> handleDATABASE ();
               break;
           default:
               $ this-> error ('No valid database provided');
               return 1;
       }

       return 0;
   }

   public static function> handleDATABASE ()
   {
       $ offset = 0;

       $ count = DATABASENAME :: count ();
       while ($ offset <$ count) {
           DATABASENAME :: offset ($ offset) -> get () -> each (function (DATABASENAME $ item) use (& $ offset) {
               $ recordId = (int) $ item-> getRecordId ();

               MYSQLTABLENAME :: updateOrCreate ([
                   'record_id' => $ recordId,
               ], DATABASENAME :: formatAttributeNames ($ item-> getAttributes ()));

               $ offset ++;
           });
       }
     dump ($ offset);
   }

and then I call my command:
php artisan sync-filemaker-db DATABASENAME
and then every time I first call the command php artisan sync-filemaker-db DATABASENAME this error pops up:
BlueFeather\EloquentFileMaker\Exceptions\FileMakerDataApiException

Authorization header 'Basic' invalid.

at C:\xampp\htdocs\enterprise-service-bus\vendor\bluefeather\eloquent-filemaker\src\Services\FileMakerConnection.php:167

 163▕                             // API token is expired. We should expire it in the cache so it isn't used again.
 164▕                             $this->forgetSessionToken();
 165▕                             return;
 166▕                         default:
"https://filemaker01.server/fmi/data/vLatest/databases/DATABASENAME/layouts/ApiLayout/records/", [])

And the second time I call her again, and so every next time she does everything.
Does the library take the Token and then use it, but the old one stays with her, I don't know what else could be the problem?

can you please help me with my problem with FileMaker?
https://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21
[https://opengraph.githubassets.com/458d315148251df5335a303218065025bad385ebe0001b62817c1be21b7c39da/BlueFeatherGroup/eloquent-filemaker/issues/21]https://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21
Authorization header 'Basic' invalid. · Issue #21 · BlueFeatherGroup/eloquent-filemakerhttps://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21
Please if you can help me why I always get this error the first time I call a function, the second time I run it then it works. FileMaker Version: 18 Php Version : 7.4 This is a mistake: {"mes...
github.com

Von: Smef @.>
Gesendet: Dienstag, 28. Juni 2022 19:57
An: BlueFeatherGroup/eloquent-filemaker @.>
Cc: hekler91 @.>; Manual @.>
Betreff: Re: [BlueFeatherGroup/eloquent-filemaker] Authorization header 'Basic' invalid. (Issue #21)
What are the sequence of function calls you're doing in your PHP? Can you post your code block? It looks like the credentials are invalid, but I wouldn't expect it to work on your second call.
—
Reply to this email directly, view it on GitHubhttps://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21#issuecomment-1169047236, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKFJTDGEG56K2PKOOROREJ3VRM4KFANCNFSM52BEN6CA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Are you using FileMaker Cloud or regular self-hosted FMS?

Ah, never mind. That wouldn't be the issue here.

Yes, I’ve seen you issue and haven’t had time to set up a new app and test
environment to attempt to reproduce this yet. It’s on my list to look at.
--
David Nahodyl
@.***
https://bluefeathergroup.com
(770) 765-6258
On June 29, 2022 at 3:19:06 PM, hekler91 @.***) wrote:
can you please help me with my problem with FileMaker?
https://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21
[
https://opengraph.githubassets.com/458d315148251df5335a303218065025bad385ebe0001b62817c1be21b7c39da/BlueFeatherGroup/eloquent-filemaker/issues/21
]https://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21
Authorization header 'Basic' invalid. · Issue #21 ·
BlueFeatherGroup/eloquent-filemaker<
https://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21>
Please if you can help me why I always get this error the first time I call
a function, the second time I run it then it works. FileMaker Version: 18
Php Version : 7.4 This is a mistake: {"mes...
github.com

Von: Smef @.>
Gesendet: Dienstag, 28. Juni 2022 19:57
An: BlueFeatherGroup/eloquent-filemaker @.>
Cc: hekler91 @.>; Manual @.>
Betreff: Re: [BlueFeatherGroup/eloquent-filemaker] Authorization header
'Basic' invalid. (Issue #21)
What are the sequence of function calls you're doing in your PHP? Can you
post your code block? It looks like the credentials are invalid, but I
wouldn't expect it to work on your second call.
—
Reply to this email directly, view it on GitHub<
https://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21#issuecomment-1169047236>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AKFJTDGEG56K2PKOOROREJ3VRM4KFANCNFSM52BEN6CA

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/BlueFeatherGroup/eloquent-filemaker/issues/21#issuecomment-1170393825,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCA6RSDUZ6PTNGHLCZ4ER3VRSOSTANCNFSM52BEN6CA
.
You are receiving this because you commented.Message ID:
@.***>

Thanks for your response. We don't use the Cloud, FileMaker is installed on our internal server.
Okay, please look into this problem as soon as you are able. I don't know what to do anymore, and it's very important to me that the code works. Thank you for your time.

I hope to get an answer soon. This problem is really bothering my application. :(

Could you set up an extremely simple public test project I could clone? That would help diagnose the issue.

When creating a simple test application, I came to the decision that there is an error somewhere in my code. (something is blocking the Token) So I created the whole project again and it works great now. I apologize for my mistake and thank you for your support.


template

template how to use？template Invalid attribute?

Sorry I don't understand what this issue is about.


make polars dataframe display more informative

Suggestion
Instead of displaying the first 50 rows of the df, maybe :

display the first and last n rows (without overlap)
importantly display the shape of the dataframe on top

This would make the deno kernel behave similarly to the python kernel.
What do you think ?

Sounds great to me. While I'll take a PR for it, I tend to just use the version built directly into polars now. There's no need to use this library for display. Here's the place to make it happen:
https://github.com/pola-rs/nodejs-polars/blob/95191dfdc9abcee12dc09533aaeb608d596006e1/polars/dataframe.ts#L1925-L1936

I think most everything from in this repo has moved into Deno.jupyter.display directly so that it isn't needed anymore. I'm going to have to double check, but I just use the built in stuff now.

I think most everything from in this repo has moved into Deno.jupyter.display directly so that it isn't needed anymore.

Indeed, this is what it seems, from my trials.

For reference in case somebody follows the same train of thought, I found that:

this deno PR#20656 is the most informative page
only primitive Deno.jupyter.broacast is important, the others are essentially thin wrappers on it.

The default display of a TS object, presumably using a default [Symbol.for('jupyter.display')](), is still quite obscure.
In the case of this example:

I observed that:

no mimetype among those officially listed renders the object as as the absence of [Symbol.for('jupyter.display')]()
using Deno.jupyter.broadcast inside [Symbol.for('jupyter.display')]() works partially (it does display the result but then returns an error :thinking: )


FramesSignal::sample optimizations

Hi! While benchmarking various audio libraries I've noticed that the current implementation of FramesSignal::sample (which currently consumes most of the time in oddio::run) has less than optimal performance. This PR contains substantial performance with minor code changes:

Added a few missing #[inlines]: the largest perf improvements of 30%-40%
Replaced two calls to Frames::get with one call Frames::get_pair: reduces the number of checks in the fast path (removes a few conditional expressions and allows the optimizer to remove the bound checks), improvement of 5-10%
(The least obvious improvement) Replaced f64 with f32 in the main loop in FramesSignal::sample by splitting the f64 position into the isize base and the f32 offset. The loss of precision looks extremely minor given that the sample should be called frequently with small buffer sizes (a few hundreds milliseconds at most). This removes the f64 -> f32 conversion in inner loop in Frames::interpolate and gives another 5-10% perf improvement.
(Controversial improvement) Replaced f32::trunc with f32.to_int_unchecked::<isize>. This massively (30+%) improves performance with default x86-64 builds due to trunc being a libm call before x86-64-v2 (SSE4.1). The performance on aarch64 is unchanged. While there are probably almost no pre-SSE4.1 CPUs in active use, I feel that the default experience (running cargo build without any flags) matters. The use of unsafe to_int_unchecked slightly improves the performance, but it can be changed to f32 as isize with minor performance hit.

All the improvements have been tested using three CPUs: Intel Core (MacBook Pro 16 Late 2019), AMD EPYC 7003 (Hetzner Cloud) and Snapdragon 888 (Samsung S21FE).
Similar optimizations (2 and 4 in particular) can be applied to Stream::sample as well.
Profile before the changes:

Thanks =)

Can you confirm that the inline annotations on generic functions, specifically, have an effect?

Sure, here is a profile of the same benchmark with all the changes from this PR applied:

Exactly how big is the difference from as isize, though?

For aarch64 the difference is exactly zero because the ISA is very nice and the float -> int conversion is already saturating: https://rust.godbolt.org/z/bGjnc1M34. For the x86-64 (including the x86-64-v2) the compiler has to add the comparison and the conditional move: https://rust.godbolt.org/z/bnjoeox7Y. In my tests the perf improvement for unsafe version on Intel was ~5%, while the AMD showed ~10% improvement.

Sure, here is a profile of the same benchmark with all the changes from this PR applied:

Ah, I see e.g. lerp was not inlined before, though bimap was. I guess it must be a heuristic weight thing? Well, I'll take it.

In my tests the perf improvement for unsafe version on Intel was ~5%, while the AMD showed ~10% improvement.

Oh, wow, let's definitely keep that then!

I looked around for a bit and took the liberty of improving Cycles::sample. Apart from the usual suspects (f64 -> f32, f32::trunc()) it also computed an integer modulo and floating point modulo (the latter becoming a function call into libc both on x86-64 and aarch64) in the inner loop. Replacing floating point modulo with a branch was the most important in this case: 30-50% perf wins.
Here's the profile before removing floating point modulo.

On the unrelated note: I tried adding a happy path to the Gain (the gain is constant) and probably hit a bug? If the size of out buffer is smaller than the SMOOTHING_PERIOD, then the gain progress gets reset on each sample here: https://github.com/Ralith/oddio/blob/main/src/gain.rs#L92 and the gain change looks like alpha^-t, not linear.

Back on topic: play_buffered in SpatialScene is slower than it can be for the usual reasons (too much work done per-sample in Ring::sample). The easiest way is probably to copy the chunked sampling from play to play_buffered and then change Ring::sample to output multiple samples at once (the code should be an almost copy-paste from Cycle::sample). I can do this if you are ok with these changes.

I tried adding a happy path to the Gain (for the case when the gain is constant) and probably hit a bug?

Good catch, I can handle the fix for that.

The easiest way is probably to copy the chunked sampling from play to play_buffered

I'm not sure what this means, but improvements there are certainly welcome, and it makes sense that similar fixes to what you've been doing can be applied. Maybe that should be a separate PR, though? There's a lot of great stuff here I'd like to get merged rather than trapped behind review for independent code.

Maybe that should be a separate PR, though?

Oh, absolutely! This PR is already getting unwieldy.


Deep watching geojson causes performance issues and circular reference errors

Currently the geojson preforms a deep watch, as you can see here by the true value.
This causes performance issues with large complex objects.
It causes maximum stack errors on object that have circular references.
Is it possible to remove the deep watch, and still get the desired behavior?

Yes, you're totally right. I'm going to change the  deep $watch by the $watchCollection shallow watcher.
Thanks for reporting.

Thanks so much! Any word on a release date for this change?
On Tuesday, January 13, 2015, David Rubert<EMAIL_ADDRESS>wrote:

Closed #595
https://github.com/tombatossals/angular-leaflet-directive/issues/595.
—
Reply to this email directly or view it on GitHub
https://github.com/tombatossals/angular-leaflet-directive/issues/595#event-217928836
.

--
Matt Miller
Web Master
609-335-4417
<EMAIL_ADDRESS>https://www.superpedestrian.com/
https://www.google.com/url?q=https%3A%2F%2Fwww.superpedestrian.com%2F&sa=D&sntz=1&usg=AFQjCNHLEDFaMLgggeXL8rh4gGlNfN0WSA

Superpedestrian Inc.
84 Hamilton St.
Cambridge, MA 02139
This message is intended only for the addressee named above.  If you are
not the intended recipient of this message, you are hereby notified that
you must not use, disseminate, or copy it in any form or take any action in
reliance upon it.  If you have received this message in error, please
delete it and any copies of it from your email system and reply immediately
to the sender at the address shown above.  This message may contain
confidential and/or proprietary information.  Neither confidentiality, nor
any proprietary rights are intended to be waived or lost by any error in
transmission.

I'm merging some pending changes and solving some issues, I suppose we can increment the versión number by the end of the week.


issue with creating sail account and group in docker build

Sail Version: v1.4.12
Laravel Version: 8.0
PHP Version: 8.0
Database Driver & Version: - N/A

Description:
Error occurs when building docker image. Throws this error
ERROR [ 7/12] RUN groupadd --force -g $WWWGROUP sail                                                                         0.4s

[ 7/12] RUN groupadd --force -g $WWWGROUP sail:
#10 0.336 groupadd: invalid group ID 'sail'

executor failed running [/bin/sh -c groupadd --force -g $WWWGROUP sail]: exit code: 3
The terminal process "/bin/bash '-c', 'docker build --pull --rm -f "vendor/laravel/sail/runtimes/8.0/Dockerfile" -t vendorportal:latest "vendor/laravel/sail/runtimes/8.0"'" terminated with exit code: 1.
Steps To Reproduce:
run command in terminal
docker build --pull --rm -f "vendor/laravel/sail/runtimes/8.0/Dockerfile" -t vendorportal:latest "vendor/laravel/sail/runtimes/8.0

docker build won't work with Sail out of the box. Build script requires some arguments, in your case WWWGROUP, which your current user group. Sail commands set it automatically:
https://github.com/laravel/sail/blob/d1a91b03885c9c29bc2d88d61a4b10bd1f678156/bin/sail#L26
Use sail build or try adding --build-arg WWWGROUP=$(id -g) to your build command.

We only support the documented way that Sail works.

I also stumbled on this issue. So you meant with "the documented way that Sail works"' is by using ./vendor/bin/sail up? CMIIW


Issue installing package on MacOS

I'm on MacOS Sierra V. 10.12.1 trying to install the latest of this package which at this time is 0.1.2 and I just updated node to try to fix errors to v7.2.1
When attempting to run the npm install ... command I am getting errors
npm install ancs --save

><EMAIL_ADDRESS>install /Users/jordanriser/workspace/ancs-test/node_modules/xpc-connection
> node-gyp rebuild

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
  CXX(target) Release/obj.target/binding/src/XpcConnection.o
../src/XpcConnection.cpp:143:44: warning: 'GetRealNamedProperty' is deprecated
      [-Wdeprecated-declarations]
      Local<Value> propertyValue = object->GetRealNamedProperty(property...
                                           ^
/Users/jordanriser/.node-gyp/7.2.1/include/node/v8.h:2949:30: note:
      'GetRealNamedProperty' has been explicitly marked deprecated here
                Local<Value> GetRealNamedProperty(Local<String> key));
                             ^
1 warning generated.
  SOLINK_MODULE(target) Release/binding.node

><EMAIL_ADDRESS>install /Users/jordanriser/workspace/ancs-test/node_modules/noble
> node-gyp rebuild

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
  LINK(target) Release/hci-ble
Undefined symbols for architecture x86_64:
  "_main", referenced from:
      start in crt1.10.6.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/hci-ble] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/jordanriser/.nvm/versions/node/v7.2.1/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Darwin 16.1.0
gyp ERR! command "/Users/jordanriser/.nvm/versions/node/v7.2.1/bin/node" "/Users/jordanriser/.nvm/versions/node/v7.2.1/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/jordanriser/workspace/ancs-test/node_modules/noble
gyp ERR! node -v v7.2.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! Darwin 16.1.0
npm ERR! argv "/Users/jordanriser/.nvm/versions/node/v7.2.1/bin/node" "/Users/jordanriser/.nvm/versions/node/v7.2.1/bin/npm" "install" "ancs" "--save"
npm ERR! node v7.2.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the noble package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs noble
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls noble
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jordanriser/workspace/ancs-test/npm-debug.log

@Jordan4jc my guess is noble doesn't support Node.js v7 as of now ...

What version of node should I be using? I have NVM so I can use a specific version of node for just this project. I see noble is a very old version? Can this be updated without breaking any functionality so that it can be used with a newer version of node?

@Jordan4jc

What version of node should I be using?

Node.js 6.x works for me.

I see noble is a very old version?

You can try to update to the latest version of noble and submit a pull request if all is good.

Are there any plans to update this lib to work with more recent versions of Node? Version 6 is a bit out of date.


add vue-awesome-form

I have written a component named vue-awesome-form, thank you.

I have update the documentation to English, thank you.

Thanks!


[JN-602] Update README.md

DESCRIPTION
updating admin-ui instructions to use HTTPS=true.  Removing obsolete env vars as those are now handled server-side
TO TEST:  (simple manual steps for confirming core behavior -- used for pre-release checks)

test failure is false positive -- ticket created to address


Invoking documentStore Issue() error

@superical, I came across this problem when issuing the certificate via the documentStore.issue() function. Apparently, I could only come out with 2 conclusion.
Firstly

The merkle root of my signature is too long. This is not possible as it indeed passed the validate schema and signature check after wrapping and signing but when I tally with the openAttest docs it is slightly longer in length.

Secondly

I signed the wrong document array. Because when I generated the wrapped documents, 2 objects were created as a result. 1 with id as an extra attribute in the wrappedDocument[]. However, this is also not possible as I tried updating either of the 2 objects from the array and none succeeded.

@superical much help needed. Thanks.

Please share code we can't really help otherwise

Same repo as before. (Master branch)
Demo Repo

  async issueDocument() {     if (this.documentStore && this.merkleRoot) {       this.web3Service.issueDocument(this.documentStore, this.merkleRoot).then((result: ContractReceipt) => {         console.log(result)         this.deployedContractAddress = result.contractAddress;       })     }   }

 async issueDocument() { if (this.documentStore && this.merkleRoot) { this.web3Service.issueDocument(this.documentStore, this.merkleRoot).then((result: ContractReceipt) => { console.log(result) this.deployedContractAddress = result.contractAddress; }) } } component.ts async issueDocument(documentStore: UpgradableDocumentStore, address: string): Promise<ContractReceipt> { const tx = await documentStore.issue(address); const receipt = await tx.wait(); return receipt } web3Service.ts

I had a look at your example repo. I'm not sure how to replicate your issue in your example app unless you provide more info on this but I'm guessing you are referring to the part when clicking on the issue button? I've tried to issue a doc and it went through successfully.🤔

 async issueDocument() { if (this.documentStore && this.merkleRoot) { this.web3Service.issueDocument(this.documentStore, this.merkleRoot).then((result: ContractReceipt) => { console.log(result) this.deployedContractAddress = result.contractAddress; }) } } component.ts async issueDocument(documentStore: UpgradableDocumentStore, address: string): Promise<ContractReceipt> { const tx = await documentStore.issue(address); const receipt = await tx.wait(); return receipt } web3Service.ts

I had a look at your example repo. I'm not sure how to replicate your issue in your example app unless you provide more info on this but I'm guessing you are referring to the part when clicking on the issue button? I've tried to issue a doc and it went through successfully.🤔

The process flow is like this:

click the Connect Document Store button
upload an unwrapped document in json format from Store Configurations
Then click Issue Certificate
The error will surfaced.

I had log the necessary information in chrome debug console.

You are using a wrong merkleroot:
this.merkleRoot = signedDocument.proof[0].signature;

You probably want to be doing this instead:
this.merkleRoot = signedDocument.signature.merkleRoot;

You are using a wrong merkleroot:
this.merkleRoot = signedDocument.proof[0].signature;

You probably want to be doing this instead:
this.merkleRoot = signedDocument.signature.merkleRoot;

I tried this though..... however, my wrapping will never give me 0x.... and therefore throwing an invalid arraryify value whenever I issue it.

Here's what I did and it worked for me in your demo repo:
this.merkleRoot = `0x${signedDocument.signature.merkleRoot}`;

Here's what I did and it worked for me in your demo repo:
this.merkleRoot = `0x${signedDocument.signature.merkleRoot}`;

Oh, alright thanks.


feat(STONEINTG-1065): let users rerun ALL tests

Before this commit, a user can only rerun one test at a time by adding the "run" label on snapshot with the name of ITS they want to rerun.
After this commit, a user can add the value of "all" in the "run" label of snapshot to automatically rerun ALL the tests easily.

Maintainers will complete the following section

[ ] Commit messages are descriptive enough (hints)
[ ] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

Codecov Report
Attention: Patch coverage is 45.00000% with 33 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@342df94). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

internal/controller/snapshot/snapshot_adapter.go
45.00%
27 Missing and 6 partials :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #912   +/-   ##
=======================================
  Coverage        ?   66.27%
=======================================
  Files           ?       43
  Lines           ?     5714
  Branches        ?        0
=======================================
  Hits            ?     3787
  Misses          ?     1594
  Partials        ?      333

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

/retest

/retest


replace, rather than add, theme elements to a base theme.

made a small change to my-gg-theme.R to replace (rather than add) a base theme's elements, as advocated for in the new Using ggplot2 in packages vignette.
ps this package is a really amazing idea! I'd been thinking about how to make writing new themes more approachable for colleagues, and I think this format will really help.

Thank you so much! Good catches and really appreciate your taking the time! Glad if it seems at all useful 🙂


please help me find a case to realize the snmp server, support v1,v2,v3,support get,set,trap.

please help me find a case to realize the snmp server, support v1,v2,v3, support get,set,trap,
logic is to return different data according to oid,
I did not see such a case in the examples directory.
thanks for you.

What cases can I refer to to achieve the desired functionality?

Resolved in https://github.com/lextudio/pysnmp/issues/158


filter-lines.jar or other JAR file is corrupted

If this happens to you, please make a comment on this issue!
I will respond and update the misc/ with a fresh, uncorrupted version.

Or, I will make a Python script to do what I request of with the filter-lines program. It is simple filter applications for tab-separated data.

Hi Seth, I'm getting the Error: Invalid or corrupt jarfile ../../software/filter-lines.jar error. Is there a workaround? Thanks in advance.

The workaround is to write a simple Python script to filter the IBD segments file. For me, the Java jarfile has been corrupted a few times over two years. Are you in a rush, in which case I could email you a copy of an uncorrupted jarfile? Otherwise, I can try to write the proposed Python script and modifications to the Snakemake rules in a couple weeks.

Note the branch threaded-py-io where I addressed this issue.


Bots do not receive tier 4, 5 neutral items.

Usually we play turbo and games doesn´t last too long, but in some rare games that are long we noticed that bots do not receive tier 4, 5 neutral items.

Apologies for the delay.  I don't check this page nearly as often as I should.
In all of my testing, when neutral items get doled at all, they do so properly through tier 5. There are two different issues I've identified for your turbo use case:

The default timings are based on normal mode (since I don't play turbo). Unfortunately, I can't seem to find a good way to ask the game what GameMode it's in (GetGameMode() from the global bot lua doesn't work for my scripts since they're not bots and I guess Valve is giving me a different sandbox). This means I can't fix the timings based on mode intrinsically; but I could give to you a file that would have turbo timings in it.
What I did discover in solo testing (which is dicey anyway, since the code wants 5 humans on one team) is that some of the time in turbo games, the script more or less fails to initialize successfully.  This is most obvious at the ~0:48 mark when it's supposed to tell you what it thinks the bot roles are. You'll get the "Bot roles have been determined" chat message, but there won't be a table following it because the Bots table in my code is somehow nil.  It's truly bizarre. At any rate, in that case, the whole script won't do anything, and any items the bots get will be because they found them themselves. I suspect the cases where you don't see tier 4s and 5s are manifestations of this issue.

My testing seems to indicate that things are more likely to work in turbo games if you start the bots once everyone has loaded into the map, rather than the picking phase. I'm guessing (but it is a SWAG) that some of the things that the script wants to do in different game phases are slightly borked since turbo evidently hastens things like the strategy phase (If you start the script late it runs catch up on its own, rather than waiting for game events).
I'd suggest paying attention to the role determination message. If you see the full 1-5 table with the bot names and their skill levels and what not, then I'd expect your items to drop.  If you don't see that. then the script isn't actually doing anything at all.  Apologies for the problems; turbo wasn't a mode I considered.
I'll try to do some more testing over the next few days, but a few patches back the vconsole broke for me, and debugging is a colossal PITA now, so it will probably be slow.

Hey. Thanks for the answer. Yeah please give me file with turbo timings in it.
Also i noticed when there is less than 4 players then bots items are bugged, for example i use FretBots script with Beginners AI script since they are hardest of them all and some bots just do not finish their item builds and get stuck, dropping some items somewhere, because i found Jugger's cornucopia for battlefury near the secret shop and he didn't finish battlefury and was having some items that requires battlefury in his inventory whole game.

The items that are purchased by the bots are entirely driven by the base script; anything that they can't build properly is not something that this script can fix.  All it does is provide gold/stat/xp/neutral item bonuses.


New version has removed video_code property?

Hi there, Embedder is awesome but I've just updated a client site using it and found you've removed the video_code property which breaks the site? I need this for some custom functionality for the youtube videos being loaded. Is this property still available anywhere?

Hi @markstewie - I don't think we've ever used a video_code property, but we do have embed_code - is that what you're looking for?

Hey @A-P now you say that, I think I actually might have made a custom modification to the plugin originally to add this but forgot that I did this. Sorry!


Build(deps): Bump keycloak-js from 19.0.1 to 19.0.2 (#4042)

Pull request opened by the merge tool on behalf of #4042

Merged in 1bca752e8316861431b95e94aa067ca0c8434c78


ENH: Add EpicsSignalNoValidation

Description

Adds a no-validation EpicsSignal, which does not wait to verify the readback on set.

Motivation and Context
#1021
We're trying to work on this as part of the 2022 Epics Codeathon.
How Has This Been Tested?
Tests added.
Where Has This Been Documented?
This PR, docstrings, etc

I apologize for the tiny commits, I have not yet gotten ophyd CI to work locally.

Tests seem to be stuck, maybe an issue similar to what Zach was seeing on his PR's?

Ok let's get this in :+1:


[FEATURE_REQ] add service icon for SAP Cloud Identity Authentication + SAP Cloud ALM

I used this AIO setup. I cannot find any icon for CALM or IAS.

Hi @piejanssens , thx for the feedback in the provide library (xml) IAS and IPS are included:

Can you please check on your side as well ?
thx and best, Fabian

@piejanssens I try to fix the AIO config in the next days.
For the topic of Cloud ALM I will check and come back asap.
best,
Fabian


Not possible to install Istio chart without specific namespace

Setup

Rancher version: 2.7.2
Browser type & version: Chrome

Describe the bug
Not possible to install Istio chart without specific namespace.
To Reproduce
Install Istio without namespace.
Result
Error received: namespaces "istio-system" not found
Expected Result
It installs
Screenshots

Additional context

This is a candidate to pull back into Q3 if there's time.

We have a team confluence page with some minor details about charts and annotations. There's also the public docs https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/helm-charts-in-rancher/create-apps. First breadcrumb would be to confirm the charts catalog.cattle.io/namespace annotation

Adding e2e tests: https://github.com/rancher/dashboard/issues/9719


python311Packages.google-cloud-iot: 2.9.1 -> 2.9.2

Changelog: https://github.com/googleapis/python-iot/blob/v2.9.2/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 241901 run on x86_64-linux 1

4 packages built:

python310Packages.google-cloud-iot
python310Packages.google-cloud-iot.dist
python311Packages.google-cloud-iot
python311Packages.google-cloud-iot.dist


support filename_ext_filter

Reference: https://github.com/informatics-isi-edu/ermrest/blob/master/user-doc/annotation.md#2017-asset
This is important for enforcing data standard rules. I.e., if I only want jpeg and png in a "thumbnail" table and want to safeguard against tiff (which don't render online) that an unknowing user might upload. We have many more examples beyond this simple one.

This is already supported in ermrestJS. Closing this issue. There is a corresponding issue in chaise here.


File attachament Feature to ChatBot

Can you help me in adding the image Upload functioanlity in this module?
This will be a great help to me.

can you help me adding webpages to the chatbot which i created though jquery ?

can you help me adding webpages to the chatbot which i created though jquery ?


added support for @wdio/sync

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other

What is the current behavior?
Typings for @wdio/sync are not supported.
What is the new behavior?
Typings for @wdio/sync are supported.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
To make typings work at all I had to include the following to my tsconfig.json:
// ...
"include": [
    "node_modules/wdio-visual-regression/build/index.d.ts",
    // ...
  ]

Hi. Thank for your PR. I'm not sure that Matcher can work with wdio sync mode. Did you check it?

I just integrated wdio-visual-regression today and it works just fine for me :)
I am no export but I figure @wdio/sync just wraps all browser commands (including custom ones) using fiber.

In such a case let's merge it. Good job :+1:


Example of resource generalization

This is an example of how endpoint generalization can be done and have a meta resource from which all endpoints depend.
In this case is to perform a simple get all info from the logged in user, but this could be extended to any endpoint.
This is because most endpoints should only need:

The base model.
The query to the database (either user or a particular object)
The schema to validate the data.

If you need more examples to decide if you want to go with this route I can generalize more this endpoint or another so we can see that it is compatible with any endpoint
Tell me what you think

You should check the other PR as the meta_resource file is in there as I added it by mistake in an earlier commit.


Design Idp provider creation and linking

Some ui forms/flows are too technical and not user friendly.
Acceptance criteria

[ ] Design a better flow for identity provider creation/adding to policy

Current flow:

Go to the login policy of the organisation
Create a new identity provider at the bottom of the page:

Link the created identity provider in the policy at the top of the page:

Choose the provider created before in step 2

In my opinion the users don't realize, that they need to configure a new idp first in the bottom section, and then need to link it in the policy.
Maybe we can directly add a button in the linking process to create a new provider? so if I cant find the provider I like to choose, I can directly create a new custom configruation

@juergrinaldi can you please check if this information is enough for you?

I just checked with the v2 version and the process and made my changes accordingly.

I simply added a button to add a role within the dialog for the authorization. that way you can create a new role when needed without leaving the current dialog.
the button simply opens the dialog for 'new role' (as is on the corresponding page) and goes back to the authorization dialog afterwards with the new role pre-selected (for convenience).
Also a slight change in the wording for the primary button just to avoid confusion.

@fgerschwiler i put the issue back into 'backlog' and changed some labels, for the further work on the issue.

@peintnermax can we close this issue?

yes we can. I will track the add role button in another issue.


Rename Compile to Compiling to fix tense

This only applies to Clang targets. Swift targets will be fixed in llbuild separately, but the tests have been modified in preperation.

I don't think we want to change this. It is consistent with Xcode's log reporting as well.

But it’s inconsistent in tense to the « Linking » tool and to Ninja’s « Building » messages.

Maybe we should rename Linking.. to Link.. then?

Makes less sense to me, but I'll bow down to whatever decision is taken.

I don't remember the exact reason for this wording but maybe @ddunbar does?

We definitely should be consistent.
I think Xcode's log may be different, because it is usually viewed after the fact, so its not actually compiling any more. The running status in the console is more often viewed as a status of the progress, but not a persistent artifact in a log (even though it does appear as both).
I'd probably use "Compiling", but don't have a strong opinion other than that we should be consistent.

ok, then I am also fine with anything.

I originally went with Compiling because:

I'm getting quite used to and liking NInja's Building ...
Compile/Link, as verbs, feel more like actions to be taken, not status updates

As usual, consistency trumps everything, but I lean slightly towards the "summary of action" phrasing that we currently use in Xcode, for example "Compile Foo.c", "Link Bar".
Status in a progress bar can be reported separately of the phrasing of the action itself. For example, I've seen build tools use Unicode symbols to indicate this in a rather nice way (I might not have picked the right characters that have metrics consistent to each other in whatever font they'll show up with, but you get the point):

○ Compile Foo.c (in progress)
✓ Compile Foo.c (done, success)
✗ Compile Foo.c (done, error)

Otherwise, I think you have to argue that the phrasing itself should change depending on how the log is being viewed. If "Compiling Foo.c" shows up in a log after the build has finished, it reads awkwardly. Similarly, "Compiled Foo.c" doesn't work for an in-progress build. Logs won't always be displayed in an environment where their content can be dynamically updated (like the Xcode build log or Ninja progress thingy) -- they have to be committed to static files eventually.
"Compile Foo.c" is more grammatically neutral, and can read well in past, present, and future tenses.

"Compile Foo.c" is more grammatically neutral, and can read well in past, present, and future tenses.

While I understand the logic, Compile feels slightly weird to me. Also, most of the build systems out there use the -ing tense:

Buck
Ninja
Ant

How do we decide?

Let's take this change.

@swift-ci smoke test


I don't get notification with app is killed

Hello good afternoon.
I am implementing the Firebase routine using the data load.
In the onMessageReceived method I receive the information both in the foreground and in the background. (from there I do my actions, including I trigger the notification using the local notification)
However, when I kill the app and trigger the push, I don't receive any data. Actually, I get paid, but when I open the app again.
Sensation that he is on hold, and only acts when the application is opened.
Can someone help me?
this.firebase.onMessageReceived().subscribe((notification: any) => {       console.log(new Date(Date.now()).toLocaleString());       console.log(notification);         console.log("Message type: " + notification.messageType);     });

You did not complete the issue template so it's unclear what platform or device you are testing on, whether you have tested using the example project or exactly how to reproduce the issue.
Please read the guidelines for reporting issues and if you still think an issue exists which is a genuine suspected bug (and not a support request) then open and new issue and complete the issue template in full.


add local icon and move provider icon

this fixes a small layout bug, and supposedly uses the foundation styles
(too bad those styles are not repected by the bolt back-end)

Have I ever mentioned how awesome you are? :+1: