Include JEuclid -core and -fop jars in built-in FOP distribution

DITA 1.3 includes built-in integration of MathML and I've implemented a simple plugin to emit MathML as fo:instream-foreign-object content. Using FOP 1.1 and the JEuclid core and fop jars, FOP can render the MathML.
It would be most convenient if the built-in FOP distribution for the org.dita.pdf2 transform included the jars necessary to do MathML rendering.

Just ran in to this with our math usage. With JEuclid copied into the FOP directory, DITA 1.3 math elements render well; without it, they do not.
As delivered, our shipped FOP does not come with JEuclid, and there's no easy way to add it to the FOP-specific classpath:
<taskdef name="fop" classname="org.apache.fop.tools.anttasks.Fop" classpathref="dost.class.path">
      <classpath>
        <fileset dir="${fop.home}">
          <include name="lib/*.jar"/>
          <include name="build/fop.jar"/>
        </fileset>
      </classpath>
    </taskdef>

It looks like right now (unless / until DITA-OT bundles JEuclid), our options re:

Copy it into the FOP dir -- need to remember to copy with each upgrade
Update that classpath ref (with every upgrade) to add a reference to the JAR
Pre-define fop.home to our own copy of FOP that includes JEuclid in the lib directory
Define our own version of the full transform.fo2pdf.fop task and add the library there

Any other options?

The whole classpath in taskdef is the Wrong Way to handle the classpath. The correct way is to add it to global classpath with plugin configuration. The only reason that classpath configuration is still in Ant is historical and will be removed in 3.0.

@drmacro also mentioned adding to global path in Slack. I completely missed the fact that it has @classpathref already, thus pulled in dost.class.path, thought it was just defining its own. User error, brought on by debugging through an IM chat window...

The latest Batik 1.10 libraries bundled with DITA OT 3.x are no longer compatible with Apache JEuclid (JEuclid implements some kind of API method from the DOM events package which has changed). The Apache JEuclid code needs to be slightly modified and then the "jeuclid-core.jar" rebuilt to remove this incompatibility problem.
The last release of JEuclid was in 2010 so it's kind of abandoned.
So if at some point we will want to include JEuclid we will probably need to fork it to the DITA OT organization.

There seems to be ongoing development for JEuclid under https://github.com/rototor/jeuclid .
pls investigate if MathML can be fixed using that fork.


feat: (IAC-486) Update default cadence version value

Changes:
The current default cadence version value is set to LTS "2020.1" which is out of support now, hence updated the cadence version value to latest version LTS "2022.09"
Tests:

With cadence version specified in ansible-vars.yaml, the default value  LTS "2022.1" is picked - DO enabled
With cadence version specified in ansible-vars.yaml, the default value  LTS "2022.1" is picked - DO disabled
Specifying any other cadence value does not cause any issue

Small update here
https://github.com/sassoftware/viya4-deployment/blob/IAC-486/docs/CONFIG-VARS.md?plain=1#L124
2020.1 > 2022.09

Small update here https://github.com/sassoftware/viya4-deployment/blob/IAC-486/docs/CONFIG-VARS.md?plain=1#L124 2020.1 > 2022.09

Good Catch. I'll update it. I noticed V4_CFG_CADENCE_VERSION is present twice in that table, I'll remove the duplicate as well.


Fix Markdown description translation for PolicyReport details

Signed-off-by: Zack Layne<EMAIL_ADDRESS>

/cc @jamestalton

/hold

/unhold

/retest-required


Is lowercase necessary for PIDs?

In the "Requirements" section of the Metadata file description, it notes that the pid:

should follow “snake case”, where letters are lowercase, special characters are removed, and spaces are replaced by underscores

Is the lowercase requirement actually a requirement? Out PIDs and corresponding image files include uppercase characters. We could rename the files... but that turns a seamless production workflow into a slightly more complicated / error-prone one.
Reference:
https://github.com/minicomp/wax_tasks/blob/39f570dc72df65f9d87133e16353913da6bd3d77/lib/wax_tasks/utils.rb#L111

@awoods currently, yes. because wax is maybe first and foremost a teaching tool, we wanted to set really clear expectations for the (meta)data upfront to avoid opaque inconsistencies in collection processing / mapping records to asset files. that said, i'm definitely open to your perspective here.
i've considered making a utility script for bulk renaming files according to wax's preconditions (using the same code you quoted above, for consistency.) the script could also spit out a 2 column CSV with (1) original file names and (2) what they were renamed as, in order to make this process more transparent. would something like that be useful? and if not, what renaming processes were you considering as a backup option to this problem? i'd be curious to know, and it might help inform code changes / documentation additions to fit how folks actually work.

(closing the issue because it's not an issue per se, but we can keep chatting + i can reopen it if action items arise.)

Thanks for the response, @mnyrop .
Currently, the Lake County Library's workflow produces image files like: 00001CC.tif, 00002CC.tif, etc. I was hoping to mount their images directory underneath Wax's "_data" directory, and generate the derivatives. If the filenames have to be lower-cased, then that means I will likely need to create a workflow for copying the renamed files.
Fundamentally, I am wondering if the removal of .downcase in the referenced code would break other elements of Wax.


postinstall jspm dependencies

saves people typing that one extra command
and specify the value for aurelia-app attribute so that the skeleton is more explicit

@capaj  please update the commit messages to follow the Durandal contributing guidelines located here: https://github.com/DurandalProject/about/blob/master/CONTRIBUTING.md#commit
Thanks

It's a nice idea for sure. I think we will hold off for now. We may end up handling this another way long term. I want to see how a few things play out over the next month. Thanks!


Rollup crashes frequently

After successfully deployed a rollup locally I realize that my rollup crashing continously as the log below
root@iZt4ni96r4tp2qzbf1epkoZ:~/astria# kubectl get pods -n astria-dev-cluster -w
NAME                                          READY   STATUS             RESTARTS   AGE
mangozila-local-blockscout-76ff969565-bwwj2   5/6     CrashLoopBackOff   1322       4d17h
mangozila-local-faucet-68df5c8d48-sx87t       1/1     Running            5          4d17h
mangozila-local-geth-5cbc88b5f8-j2xlk         2/3     CrashLoopBackOff   872        4d17h
mangozila-local-blockscout-76ff969565-bwwj2   6/6     Running            1323       4d17h
mangozila-local-blockscout-76ff969565-bwwj2   5/6     Error              1323       4d17h
mangozila-local-blockscout-76ff969565-bwwj2   5/6     CrashLoopBackOff   1323       4d17h
mangozila-local-geth-5cbc88b5f8-j2xlk         3/3     Running            873        4d17h

what cause this error ?

Hey @mangozila thanks for filing a bug, can you provide a little more information to help us debug.
Are you running this rollup locally or on Digital Ocean?
If locally what operating system are you using? Did you use the steps suggested in the guide which would mean you're running Docker Desktop, with Kubernetes in Docker (kind).
To get more details on the specific rollup failure could you run:
kubectl describe po mangozila-local-geth-5cbc88b5f8-j2xlk  -n astria-dev-cluster

This will tell us what container within the pod is failing. There are 3 possibilities:

geth
composer
conductor

We'll also want to look at the logs of the failing container, you can see this with:
kubectl logs mangozila-local-geth-5cbc88b5f8-j2xlk -c <container-name> -n  astria-dev-cluster

Replace <container-name> with one of geth, composer, or conductor
Could you please post the output of these commands in a comment here, thanks!

Looking at the timing of the rollup creation, my assumption is that your rollup is running against the older dusk-1 network as opposed to the newer dusk-2 network which we announced on Monday.
We have turned off the dusk-1 network, but failed to announce our intent to do this and to ensure existing users were informed, that's our mistake and I apologize.
With the transition from dusk-1 to dusk-2 we made changes to the underlying data structure of sequencer blocks, unfortunately this means rollups which were deployed to dusk-1 can't be easily upgraded to use dusk-2.
We recommend redeploying your rollup from scratch following the steps outlined in our updated docs.
You'll also want to make sure you reinstall the astria-cli at v0.2.0 or newer, you can check this by running
astria-cli -V

To validate that your new rollup is using the latest dusk-2 network ensure that the config.sequencer.rpc field in your rollup configuration file is set to https://rpc.sequencer.dusk-2.devnet.astria.org as show in our docs.
global:
  namespace: astria-dev-cluster
  useTTY: false
  logLevel: debug
config:
  rollup:
    name: <YOUR_ROLLUP_NAME>
    chainId: <YOUR_ROLLUP_NAME>-chain
    networkId: '<YOUR_NETWORK_ID>'
    genesisAccounts:
    - address: <GENESIS_ADDRESS>
      balance: '<BALANCE>'
  sequencer:
    initialBlockHeight: <INITIAL_SEQUENCER_BLOCK_HEIGHT>
    websocket: wss://rpc.sequencer.dusk-2.devnet.astria.org/websocket
    rpc: https://rpc.sequencer.dusk-2.devnet.astria.org
ingress:
  hostname: <YOUR_HOSTNAME>
celestia-node:
  config:
    labelPrefix: <YOUR_ROLLUP_NAME>

Looking at the timing of the rollup creation, my assumption is that your rollup is running against the older dusk-1 network as opposed to the newer dusk-2 network which we announced on Monday.
We have turned off the dusk-1 network, but failed to announce our intent to do this and to ensure existing users were informed, that's our mistake and I apologize.
With the transition from dusk-1 to dusk-2 we made changes to the underlying data structure of sequencer blocks, unfortunately this means rollups which were deployed to dusk-1 can't be easily upgraded to use dusk-2.
We recommend redeploying your rollup from scratch following the steps outlined in our updated docs.
You'll also want to make sure you reinstall the astria-cli at v0.2.0 or newer, you can check this by running
astria-cli -V

To validate that your new rollup is using the latest dusk-2 network ensure that the config.sequencer.rpc field in your rollup configuration file is set to https://rpc.sequencer.dusk-2.devnet.astria.org as show in our docs.
global:
  namespace: astria-dev-cluster
  useTTY: false
  logLevel: debug
config:
  rollup:
    name: <YOUR_ROLLUP_NAME>
    chainId: <YOUR_ROLLUP_NAME>-chain
    networkId: '<YOUR_NETWORK_ID>'
    genesisAccounts:
    - address: <GENESIS_ADDRESS>
      balance: '<BALANCE>'
  sequencer:
    initialBlockHeight: <INITIAL_SEQUENCER_BLOCK_HEIGHT>
    websocket: wss://rpc.sequencer.dusk-2.devnet.astria.org/websocket
    rpc: https://rpc.sequencer.dusk-2.devnet.astria.org
ingress:
  hostname: <YOUR_HOSTNAME>
celestia-node:
  config:
    labelPrefix: <YOUR_ROLLUP_NAME>

oh right I didnt notice that the network has changed to dusk-2. okay I will redeploy it and will let you know if this error still occour

Looking at the timing of the rollup creation, my assumption is that your rollup is running against the older dusk-1 network as opposed to the newer dusk-2 network which we announced on Monday.
We have turned off the dusk-1 network, but failed to announce our intent to do this and to ensure existing users were informed, that's our mistake and I apologize.
With the transition from dusk-1 to dusk-2 we made changes to the underlying data structure of sequencer blocks, unfortunately this means rollups which were deployed to dusk-1 can't be easily upgraded to use dusk-2.
We recommend redeploying your rollup from scratch following the steps outlined in our updated docs.
You'll also want to make sure you reinstall the astria-cli at v0.2.0 or newer, you can check this by running
astria-cli -V

To validate that your new rollup is using the latest dusk-2 network ensure that the config.sequencer.rpc field in your rollup configuration file is set to https://rpc.sequencer.dusk-2.devnet.astria.org as show in our docs.
global:
  namespace: astria-dev-cluster
  useTTY: false
  logLevel: debug
config:
  rollup:
    name: <YOUR_ROLLUP_NAME>
    chainId: <YOUR_ROLLUP_NAME>-chain
    networkId: '<YOUR_NETWORK_ID>'
    genesisAccounts:
    - address: <GENESIS_ADDRESS>
      balance: '<BALANCE>'
  sequencer:
    initialBlockHeight: <INITIAL_SEQUENCER_BLOCK_HEIGHT>
    websocket: wss://rpc.sequencer.dusk-2.devnet.astria.org/websocket
    rpc: https://rpc.sequencer.dusk-2.devnet.astria.org
ingress:
  hostname: <YOUR_HOSTNAME>
celestia-node:
  config:
    labelPrefix: <YOUR_ROLLUP_NAME>

root@iZt4ni96r4tp2qzbf1epkoZ:~/dev-cluster# astria-cli sequencer blockheight get --sequencer-url https://rpc.sequencer.dusk-2.devnet.astria.org/
Block Height:
    529718
root@iZt4ni96r4tp2qzbf1epkoZ:~/dev-cluster# astria-cli rollup config create
failed to get sequencer block for initial sequencer height

Caused by:
   0: sequencer client method failed
   1: executing tendermint RPC failed
   2: HTTP request failed with non-200 status code: 502 Bad Gateway

      Location:
   2:     /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9
   3: HTTP request failed with non-200 status code: 502 Bad Gateway

Location:
    /root/astria/crates/astria-cli/src/commands/rollup.rs:117:14
root@iZt4ni96r4tp2qzbf1epkoZ:~/dev-cluster#

when run command astria-cli rollup config createI got this error even after I manually fetched the blockheight

root@iZt4ni96r4tp2qzbf1epkoZ:~/dev-cluster# astria-cli sequencer blockheight get --sequencer-url https://rpc.sequencer.dusk-2.devnet.astria.org/
Block Height:
    529718
root@iZt4ni96r4tp2qzbf1epkoZ:~/dev-cluster# astria-cli rollup config create
failed to get sequencer block for initial sequencer height

Caused by:
   0: sequencer client method failed
   1: executing tendermint RPC failed
   2: HTTP request failed with non-200 status code: 502 Bad Gateway

      Location:
   2:     /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9
   3: HTTP request failed with non-200 status code: 502 Bad Gateway

Location:
    /root/astria/crates/astria-cli/src/commands/rollup.rs:117:14
root@iZt4ni96r4tp2qzbf1epkoZ:~/dev-cluster#

It seems that there is a problem with this file when I I use command curl -L https://github.com/astriaorg/astria/releases/download/cli-v0.2.0/astria-cli-x86_64-unknown-linux-gnu.tar.gz > astria-cli.tar.gz tar -xvzf astria-cli.tar.gz
the problem disappeared when I built from source

closing at it appears solved + devnet is being restarted, please re-open if needed!


ThisOldHouse extractor error

Please follow the guide below

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

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.06.25. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.06.25

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'-f', u'[height=720]', u'--all-subs', u'-o', u'/d/rain-garden-lighting.mp4', u'https://www.thisoldhouse.com/watch/ask-toh-rain-garden-lighting']
[debug] Encodings: locale ANSI_X3.4-1968, fs UTF-8, out UTF-8, pref ANSI_X3.4-1968
[debug] youtube-dl version 2017.06.25
[debug] Python version 2.7.12 - CYGWIN_NT-6.1-WOW-2.7.0-0.306-5-3-i686-32bit
[debug] exe versions: ffmpeg N-83749-g035e932, ffprobe N-83749-g035e932
[debug] Proxy map: {}
[ThisOldHouse] ask-toh-rain-garden-lighting: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError(u'jwplatform',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 433, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/thisoldhouse.py", line 34, in _real_extract
video_id = drupal_settings['jwplatform']['video_id']
KeyError: u'jwplatform'
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 762, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 446, in extract
raise ExtractorError('An extractor error has occurred.', cause=e)
ExtractorError: An extractor error has occurred. (caused by KeyError(u'jwplatform',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Hi @smrss,
It appears the embedded JSON data has been updated on this site.  I will submit a new PR with a fix in place for this shortly.
Cheers,
Parmjit V.


reading of projects is broken

In read.pl, vit reads a list of all available projects to use for tab complation.  However, the parsing of taskwarrior's output is broken, causing vit to include projects like "------" and "  " in the tab completion list.
It should be striaghtforward to reuse the parsing from the task patch of #5.  I'll see if I can get around to fixing this before 1.3.

Sounds good. Indeed, it seems to work well for the tab completion of tags.

@baszoetekouw will you be able to come up with a patch for this soon?

@baszoetekouw I'm guessing you're pretty busy. Should we put this off to v1.4? If I remember correctly, this is not a regression, right?

I think this is not a regression, so I'm taking off the 1.3 milestone.

Since 1.3 is in security-fix-only mode, and read.pl is nowhere to be found on 2.x branch, I guess this issue can be closed?


Online documentation for Set-ProcessMitigation has commands that don't run correctly

Online documentation for Set-ProcessMitigation has the following command:
Set-Processmitigation -Name test.exe -Remove -Disable DEP
Running the command
Set-Processmitigation -Name iexplore.exe -Disable DEP
on a fresh Windows 10 1903 install and then running
Set-Processmitigation -Name -Remove iexplore.exe -Disable DEP
gives the following error:
WARNING: Error while setting DEP: C000000D
The same is true for other applications, system level settings, other mitigation types, and the '-Reset' cmdlet as well.

@e0i - Jumping on to ask, is there a better place to discuss bugs within the Get-ProcessMitigation and Set-ProcessMitigation modules than this repo? We've found quite a few, and it would be nice to be able to get some answers without having to pay $500 every time we've found something wrong.

Hello, @SCLDGit
Yes,
Please consider consulting PowerShell UserVoice channel regarding your product feedback via the following link,
PowerShell UserVoice
You may also check relevant resources and ask the community for any other inquiries via PowerShell Community,
PowerShell Community
Thanks.

Hello @SCLD-FJaramillo ,
ufortunately, I wasn't able to reproduce your issue (for me , command Set-Processmitigation -Name  iexplore.exe -Disable DEP -Remove worked correctly in 1903).

could you please check whether you are running the command as a user that has sufficient permissions?
could you please provide output of Get-Processmitigation -Name  iexplore.exe command?

Thank you

I just tried the cmdlet that you suggested, I'm attaching the results:

I'm running powershell as Administrator in a windows 10 1903 version
Thanks.

Hello @SCLD-FJaramillo ,
Please try the following (it was workaround for error C000000D in Windows 10 1809, hope it will work for 1903 as well): Delete file C:\Windows\Microsoft.NET\assembly\GAC_64\Microsoft.ProcessMitigations.Commands\v4.0_<IP_ADDRESS>__31bf3856ad364e35\Microsoft.ProcessMitigations.Commands.dll and then restart the PC. Then try to run command again.
If it doesn't work, I would recommend to raise a ticket in Microsoft Support Portal.
Thank you

Hi,
I don’t have the file Microsoft.ProcessMitigations.Commands.dll in the suggested location, I checked in the two Windows 10 1903 computers that I’m testing on
Thanks.
From: MaratMussabekov<EMAIL_ADDRESS>Sent: Tuesday, November 5, 2019 6:29 AM
To: MicrosoftDocs/windows-powershell-docs<EMAIL_ADDRESS>Cc: Fredi Jaramillo<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-powershell-docs] Online documentation for Set-ProcessMitigation has commands that don't run correctly (#1429)
Hello @SCLD-FJaramillohttps://github.com/SCLD-FJaramillo ,
Please try the following (it was workaround for error C000000D in Windows 10 1809, hope it will work for 1903 as well): Delete file C:\Windows\Microsoft.NET\assembly\GAC_64\Microsoft.ProcessMitigations.Commands\v4.0_<IP_ADDRESS>__31bf3856ad364e35\Microsoft.ProcessMitigations.Commands.dll and then restart the PC. Then try to run command again.
If it doesn't work, I would recommend to raise a ticket in Microsoft Support Portalhttps://support.microsoft.com.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-powershell-docs/issues/1429?email_source=notifications&email_token=AM4JFMPJDNIFEGIQ7GJSU6DQSFKGTA5CNFSM4I43CZHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDCQQDY#issuecomment-549783567, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4JFMMURZRSXAAIYTKJD2TQSFKGTANCNFSM4I43CZHA.

Dear @SCLD-FJaramillo ,
please also check folders C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.ProcessMitigations.Commands.resources\v4.0_<IP_ADDRESS>_en_31bf3856ad364e35\ and C:\Windows\Microsoft.NET\assembly\GAC_32\Microsoft.ProcessMitigations.Commands\v4.0_<IP_ADDRESS>__31bf3856ad364e35\
Thank you

Hi,
I don’t have the “Microsoft.ProcessMitigations.Commands.resources” folder in the first path, and I don’t have the “Microsoft.ProcessMitigations.Commands” on the second path.
Thanks.
From: MaratMussabekov<EMAIL_ADDRESS>Sent: Thursday, November 7, 2019 1:36 AM
To: MicrosoftDocs/windows-powershell-docs<EMAIL_ADDRESS>Cc: Fredi Jaramillo<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-powershell-docs] Online documentation for Set-ProcessMitigation has commands that don't run correctly (#1429)
Dear @SCLD-FJaramillohttps://github.com/SCLD-FJaramillo ,
please also check folders C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.ProcessMitigations.Commands.resources\v4.0_<IP_ADDRESS>_en_31bf3856ad364e35\ and C:\Windows\Microsoft.NET\assembly\GAC_32\Microsoft.ProcessMitigations.Commands\v4.0_<IP_ADDRESS>__31bf3856ad364e35\
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-powershell-docs/issues/1429?email_source=notifications&email_token=AM4JFMOEJKZ4XSOPNGUIMQLQSOZNDA5CNFSM4I43CZHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDK7LPY#issuecomment-550892991, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4JFMN2LI6E3VEWGR5SKHTQSOZNDANCNFSM4I43CZHA.

Hi @SCLD-FJaramillo,
Did you try to create a support request?
Thank you

We did open a support ticket around four weeks ago(Support Request #<PHONE_NUMBER>06908).
Kenneth Dawkins has been working with us.
Thanks
From: MaratMussabekov<EMAIL_ADDRESS>Sent: Tuesday, November 12, 2019 3:57 AM
To: MicrosoftDocs/windows-powershell-docs<EMAIL_ADDRESS>Cc: Fredi Jaramillo<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-powershell-docs] Online documentation for Set-ProcessMitigation has commands that don't run correctly (#1429)
Hi @SCLD-FJaramillohttps://github.com/SCLD-FJaramillo,
Did you try to create a support request?
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-powershell-docs/issues/1429?email_source=notifications&email_token=AM4JFMNZPCAE7DRYZRAJPTTQTJVT5A5CNFSM4I43CZHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZQH3Y#issuecomment-552797167, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4JFMOJGW5LKDJOYXMIR7LQTJVT5ANCNFSM4I43CZHA.

@SCLD-FJaramillo
The problematic behavior of mentioned commands could not be reproduced and it is better to consult appropriate support channels for this issue, as the issues section of this repository is intended for documentation and content issues only.
Thank you.

Remove the -Remove switch from the command, since it's not a system-level setting you're controlling.  Like so:
Set-Processmitigation -Name iexplore.exe -Disable DEP


rank-profile constants does not work everywhere

Describe the bug
a simple constant in a rank-profile can not be used in all contexts
To Reproduce
Use application with schema:
schema item {
    document item {
        field title type string {
            indexing: summary | index
        }
    }
    rank-profile default {
        constants {
            constant(foo1) double: 0.5
        }
        function makevector() {
            expression: tensor(x[3]):[0.25, constant(foo1), 0.75]
        }
        first-phase {
            expression: sum(makevector())
        }
    }
}

Expected behavior
deploy should work
Result from deploy
Invalid application: Error in rank setup in schema 'item' for content cluster 'search'. Details:
WARNING: invalid rank feature constant(foo1): Constant 'foo1' not found
	  ... needed by function makevector
	  ... needed by function firstphase
ERROR: verification failed: function firstphase (first phase ranking)
ERROR: rank profile 'default': FAIL

Environment (please complete the following information):

OS: CentOS Stream release 8
Infrastructure: self-hosted

Vespa version
8.137.25

similar problems occur when using a constant as input to an onnx model, example:
    rank-profile default {
        constants {
            constant(foo3) tensor(d0[1]): [0.75]
        }
        inputs {
            query(bar3) tensor(d0[1]): [0.25]
        }
        onnx-model myplus {
            file: files/vector_plus.onnx
            input a: constant(foo3)
            input b: query(bar3)
            output out: score
        }
        first-phase {
            expression: sum(onnx(myplus).score)
        }
    }

where the onnx model is a trivial plus of tensor(d0[1]) types; this gives me
Invalid application: Error in rank setup in schema 'item' for content cluster 'search'. Details:
WARNING: invalid rank feature constant(foo3): Constant 'foo3' not found
	  ... needed by rank feature onnx(myplus).score
	  ... needed by function firstphase
ERROR: verification failed: function firstphase (first phase ranking)
ERROR: rank profile 'default': FAIL

this was fixed as part of overhaul/cleanup as part of global-phase work.


Too BIG file for download tests

@Dopervigest I ask your to replace test of dataset module with smaller test file. 45+ Mb is too big in my opinion. Maybe you can prepare test_folder_tree folder as a test case for download.

@Dopervigest , are your finish this?

Partly, the issue with the size of the file is resolved, but i haven't prepared test_folder_tree yet


Average number of annotations

Hi Kim,
COuld you rerun the query for average number of annotations per paper per year, same as in #455 thanks!

Hi Antonia.
I've got the numbers from Chado v57.  They are a different than last time.  That might be because I forgot to include interaction annotations last time.  Some of the averages have gone down which might be because we're now including papers that had only a few interaction annotions.
https://www.dropbox.com/s/363ldm9b9i91g2s/annotations_per_paper_per_year_inc_interactions.csv?dl=0
And here are the average annotations per paper in 5 year bins (1995-1999,2000-2004, etc).  The "2015" bin is just papers from last year.  If you'd like the bins to be 1996-2000, 2001-2005 instead, let me know.
https://www.dropbox.com/s/t3bkr90ry7vghp9/annotations_per_paper_per_year_inc_interactions_bins.csv?dl=0

I should say that these are all the annotations in Chado from every source for each paper.  Is that what you're after?

That sounds good, will let you know tomorrow if there are any problems :)

Yep, I'm not sure we want to include everything from bioGRID
There may be a couple of publications that we want to filter from the interactions (some of the huge mass spec where they reported everything, and Colm Ryan  genetic interaction screen which are really HTP....I think we will have a better idea when we see the graphs ......
If it only includes the interactions curated in canto, it should be fine

If it only includes the interactions curated in canto, it should be fine

OK, I've updated the links above to include only Canto annotations.

OK, I've updated the links above to include only Canto annotations.

Ah, I misread that - so include all ontology annotation but only include interactions from Canto?

yeah that sounds right
On Wed, Feb 17, 2016 at 8:47 PM, Kim Rutherford<EMAIL_ADDRESS>wrote:

OK, I've updated the links above to include only Canto annotations.
Ah, I misread that - so include all ontology annotation but only include
interactions from Canto?
—
Reply to this email directly or view it on GitHub
https://github.com/pombase/pombase-chado/issues/523#issuecomment-185396386
.

--
Antonia Lock, PhD
PomBase Biocurator, http://www.pombase.org
Department of Genetics, Evolution and Environment,
The Darwin Building,
University College London
London WC1E 6BT, UK

OK, here are the annotations per pub per year, but with interactions only from Canto:
https://www.dropbox.com/s/363ldm9b9i91g2s/annotations_per_paper_per_year_inc_interactions.csv?dl=0
and the same, binned in 5 year intervals:
https://www.dropbox.com/s/t3bkr90ry7vghp9/annotations_per_paper_per_year_inc_interactions_bins.csv?dl=0
Let me know if that's OK.


Fix metadata delete

Description
immerjs makes the redux state immutable, this means that we can't make modifications directly to it, so we need to perform a clone before doing the delete of the deleted track
Details
URL to issue
N/A

Link to staging deployment URL (or set N/A)
N/A (no point in staging if we are going to keep testing)

Links to any PRs or resources related to this PR

Integration test branch
master

Merge checklist
Your changes will be ready for merging after all of the steps below have been completed.

Code updates
Have best practices and ongoing refactors being observed in this PR

[ ] Migrated any selector / reducer used to the new format.

Manual/unit testing

[ ] Tested changes using InfraMock locally or no tests required for change, e.g. Kubernetes chart updates.
[ ] Validated that current unit tests for code work as expected and are sufficient for code coverage or no unit tests required for change, e.g. documentation update.
[ ] Unit tests written or no unit tests required for change, e.g. documentation update.

Integration testing
You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.

[x] Started end-to-end tests on the latest commit.

Documentation updates

[ ] Relevant Github READMEs updated or no GitHub README updates required.
[ ] Relevant Wiki pages created/updated or no Wiki updates required.

Optional

[ ] Staging environment is unstaged before merging.
[ ] Photo of a cute animal attached to this PR.

LGTM. Need to remember to make/improve the tests for this

Added a ticket


Service Bus Readme Issue

Section Link

Reason:
Click on these links does not respond.
Suggestion:
1. Update link to:
https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/servicebus/azure-messaging-servicebus#receive-messages
2. Update link to:
https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/servicebus/azure-messaging-servicebus#send-and-receive-from-session-enabled-queues-or-topics
@jongio for notification.

Thanks @hongli19750210 and @v-xuto. Could you please create a PR for it?

Close this issue due to PR #22320  merged.


Helm: additional info for mtu value

This commit adds additional information
on which interfaces the mtu value configures.
Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Are you a user of Cilium? Please add yourself to the Users doc
[x] Thanks for contributing!

/test


Maybe change containers/list to implementations on generics

https://github.com/bahlo/generic-list-go - for example this looks very similar to containers/list but without empty interfaces.
I noticed what the library uses containers/list because my program sometimes crashes
panic: interface conversion: interface {} is nil, not *lru.entry[string,*github.com/Code-Hex/go-generics-cache.Item[string,int64]]

goroutine 241845 [running]:
github.com/Code-Hex/go-generics-cache/policy/lru.(*Cache[...]).delete(...)
 /go/pkg/mod/github.com/!code-!hex/go-generics-cache@v0.0.8/policy/lru/lru.go:118
github.com/Code-Hex/go-generics-cache/policy/lru.(*Cache[...]).deleteOldest(0xc000234330?)
 /go/pkg/mod/github.com/!code-!hex/go-generics-cache@v0.0.8/policy/lru/lru.go:113 +0xed
github.com/Code-Hex/go-generics-cache/policy/lru.(*Cache[...]).Set(0xc00023a048, {0xc0061324b0, 0x42}, 0xc007a885a0)
 /go/pkg/mod/github.com/!code-!hex/go-generics-cache@v0.0.8/policy/lru/lru.go:85 +0x339
github.com/Code-Hex/go-generics-cache.(*Cache[...]).Set(0xc0002340f0, {0xc0061324b0, 0x42}, 0x48, {0x0?, 0x0, 0x0})
 /go/pkg/mod/github.com/!code-!hex/go-generics-cache@v0.0.8/cache.go:158 +0x1f3

It also can be problem in logic (maybe some races)

@mr-tron Thanks for your reporting.
Do you have a minimal code that is reproduced the problem?

No. But i use only get and set functions in parallel threads.
I will try to reproduce later.

@mr-tron I see in parallel.
Thanks a lot!

I will try to reproduce later

MVP. golang 1.18rc1
package main

import (
	cache "github.com/Code-Hex/go-generics-cache"
	"github.com/Code-Hex/go-generics-cache/policy/lru"
	"math/rand"
	"time"
)

var c *cache.Cache[int, int]
func main() {
	c = cache.New(cache.AsLRU[int, int](lru.WithCapacity(10000)))
	for i:= int64(0) ; i < 10 ; i++ {
		go func(i int64) {
			m := rand.New(rand.NewSource(i))
			for {
				c.Set(m.Intn(100000), m.Intn(100000))
				c.Get(m.Intn(100000))
			}
		}(i)
	}
	time.Sleep(time.Minute*10)
}

it usually fails for me in few minutes

@mr-tron Thanks! I fixed at https://github.com/Code-Hex/go-generics-cache/pull/17


type does not work with generics, but does work with explicit defintion

(<T, Fn extends (x: T) => number>(f: Fn) => {
  const g = (x: T) => x;
  const h = (_: T) => 1;
  pipe(g, f);  // This gives a typing error.
  pipe(g, h);  // This works fine.
});

where pipe is defined like this
export type Unary<Input, Output> = (_: Input) => Output;

export type Tail<L extends unknown[]> = L extends
  readonly [unknown, ...infer LTail] ? LTail
  : L;

type UnaryFn<A, R> = (a: A) => R;
type Arg<F> = F extends UnaryFn<infer A, unknown> ? A : never;
type Res<F> = F extends UnaryFn<any, infer R> ? R : never;

type ValidCompose<F1, F2> = Res<F1> extends (Arg<F2> | Promise<Arg<F2>>) ? F1
  : (arg: Arg<F1>) => Arg<F2>;

type ValidPipe<FS> = FS extends [infer F1, infer F2, ...infer Rest]
  ? [ValidCompose<F1, F2>, ...ValidPipe<[F2, ...Rest]>] // tuple length >= 2
  : FS; // tuple length < 2

export const pipe = <Fs extends Func[]>(  ...fs: ValidPipe<Fs>) => null

I couldn't find any reason why the two statements would be treated differently, so I suspect it might have something to do with the implementation of generics.

To expedite the triage process, we need everyone to follow the issue template and instructions.
When you clicked "Create New Issue", the issue form was pre-populated with a template and some instructions. We need you to read those instructions completely, follow them, and then fill in all the fields in that template.
We are not able to assist with issues that don't follow the template instructions as they represent a significantly larger amount of work compared to issues which are correctly specified. Thank you for understanding.


MissingParameterException even though LUIGI_CONFIG_PATH is set?

I am having this MainTask which require TransformToParquet:
class MainTask(luigi.Task):

    def requires(self):
        return TransformToParquet()

    def run(self):
        logging.info('All tasks done.')
        return

    def output(self):
        return self.requires().output()

if __name__ == '__main__':
    luigi.run()
    print('All done.')

This has two input paramters input_file and output_hdfs_file:
class TransformToParquet(PySparkTask):

    input_file = luigi.Parameter()
    output_hdfs_file = luigi.Parameter()

    def requires(self):
        return []

    def output(self):
        return luigi.LocalTarget(self.output_hdfs_file)

    def run(self):
        sc = SparkContext(master=self.master, appName=TransformToParquet.__class__.__name__)
        convert_to_parquet(sc, self.input_file, self.output_hdfs_file)

I have a config file:
[TransformToParquet]
input_file=/media/data/subset_concatenated.txt
output_hdfs_file=/media/data/transformed.parquet

which I am referring to via environment variable LUIGI_CONFIG_PATH.
However, I am getting
    raise parameter.MissingParameterException("%s: requires the '%s' parameter to be set" % (exc_desc, param_name))
luigi.parameter.MissingParameterException: TransformToParquet[args=(), kwargs={}]: requires the 'input_file' parameter to be set

and I just can't see the problem especially since this used to work previously.

Can you set it with command line or default path for the config-file? Perhaps you use luigi namespaces now?

@Tarrasch My apologies - I found the problem ..
I had the following in my pom.xml
    <properties>
        <spring.boot.version>2.0.0.RELEASE</spring.boot.version>
    </properties>

    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.0.1.RELEASE</version>
    </parent>

I changed the version for the parent at some point but didn't change spring.boot.version accordingly. Setting both to the same version resolved the issue.
I just wonder why things didn't get "worse" than FlywayDB just not running the SQL scripts but anyway. Setting both versions to 2.0.1.RELEASE solved the problem.

@Tarrasch I will have to take a look at that tomorrow. I've tried to set it via command line but that didn't change anything. I'm not aware about namespaces - I don't think I'm using that.

Okay, I was able to make this work. I'm not sure what the problem was but it's working again.


weed mount - crashed on rename operation - mount point down

Everytihng works find master, filer and volume.
After the execution of volume.fix.replication the mount is down.
weed version 3.02 / go version go1.18.1 linux/amd64
ubuntu: 18.04 lts
mount command: sudo -u vmail /usr/local/bin/weed mount -nonempty -filer=<IP_ADDRESS>:8888 -dir=/var/vmail -filer.path=/home/seaweed/filer -cacheDir=/var/vmailcache -cacheCapacityMB 4096 -allowOthers &> /var/log/seaweedmount.log
vmail is the owner of /home/seaweed
and of the storage mountpoint /storageboxes/001box
It's a cluster of 3 machine.
seaweedmount.log
This is SeaweedFS version 8000GB 3.02 a4ca3ed1f0c2bcde1d36bb48f81dedc3e1924679 linux amd64
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x1bfd93d]
goroutine 1 [running]:
github.com/chrislusf/seaweedfs/weed/mount.(*InodeToPath).MovePath(0xc0005e83c0, {0xc000365700, 0x38}, {0xc000365740, 0x33})
/github/workspace/weed/mount/inode_to_path.go:168 +0x15d
github.com/chrislusf/seaweedfs/weed/mount.(*WFS).handleRenameResponse(0xc000522900, {0x27d6440, 0xc000106e80}, 0xc00031d220)
/github/workspace/weed/mount/weedfs_rename.go:236 +0x4ba
github.com/chrislusf/seaweedfs/weed/mount.(*WFS).Rename.func1({0x27e8818, 0xc00035f580})
/github/workspace/weed/mount/weedfs_rename.go:199 +0x3fc
github.com/chrislusf/seaweedfs/weed/mount.(*WFS).WithFilerClient.func1.1(0xc000727180)
/github/workspace/weed/mount/wfs_filer_client.go:25 +0x6f
github.com/chrislusf/seaweedfs/weed/pb.WithGrpcClient(0xc5?, 0xc0006935a0, {0xc00027aa90, 0xe}, {0xc000693590?, 0xc000693568?, 0x8?})
/github/workspace/weed/pb/grpc_client_server.go:145 +0x17f
github.com/chrislusf/seaweedfs/weed/mount.(*WFS).WithFilerClient.func1()
/github/workspace/weed/mount/wfs_filer_client.go:23 +0x14d
github.com/chrislusf/seaweedfs/weed/util.Retry({0x2221a29, 0xa}, 0xc0006936b0)
/github/workspace/weed/util/retry.go:16 +0xb1
github.com/chrislusf/seaweedfs/weed/mount.(*WFS).WithFilerClient(0xc0002e70c0?, 0x33?, 0xc0005cb5c0?)
/github/workspace/weed/mount/wfs_filer_client.go:16 +0x66
github.com/chrislusf/seaweedfs/weed/mount.(*WFS).Rename(0xc000522900, 0x18?, 0xc0002e6ec0, {0xc00027aa30, 0x10}, {0xc00027aa05, 0xb})
/github/workspace/weed/mount/weedfs_rename.go:166 +0x4cd
github.com/hanwen/go-fuse/v2/fuse.doRename(0xc000714420, 0xc000604000)
/go/pkg/mod/github.com/hanwen/go-fuse/v2@v2.1.0/fuse/opcode.go:418 +0xf1
github.com/hanwen/go-fuse/v2/fuse.(*Server).handleRequest(0xc000714420, 0xc000604000)
/go/pkg/mod/github.com/hanwen/go-fuse/v2@v2.1.0/fuse/server.go:483 +0x1f3
github.com/hanwen/go-fuse/v2/fuse.(*Server).loop(0xc000714420, 0x20?)
/go/pkg/mod/github.com/hanwen/go-fuse/v2@v2.1.0/fuse/server.go:456 +0x108
github.com/hanwen/go-fuse/v2/fuse.(*Server).Serve(0xc000714420)
/go/pkg/mod/github.com/hanwen/go-fuse/v2@v2.1.0/fuse/server.go:378 +0x35
github.com/chrislusf/seaweedfs/weed/command.RunMount(0x389eb40, 0x12)
/github/workspace/weed/command/mount_std.go:260 +0x1416
github.com/chrislusf/seaweedfs/weed/command.runMount(0x3881ef8?, {0xc000128090?, 0x0, 0x8?})
/github/workspace/weed/command/mount_std.go:55 +0x165
main.main()
/github/workspace/weed/weed.go:81 +0x383

I checked everything several times and I even restarted from zero. it's not working. in my opinion it's not stable.

the trace showed the failure is when renaming on the weed mount. Not related to volume.fix.replication.

Well. I just mounted it and led it run without doing any operation at all on the mount.
It just crashes. Dovecot is running of course. So seems like it has problems with this.
May 11, 2022 21:07:54 Chris Lu @.***>:

the trace showed the failure is when renaming on the weed mount. Not related to volume.fix.replication.
—
Reply to this email directly, view it on GitHub[https://click.shapememory.eu/dl3nyw/Af0FUDqw#issuecomment-1124188992], or unsubscribe[https://click.shapememory.eu/dl3nyw/wsKai1dL].
You are receiving this because you authored the thread.[Tracking image][https://click.shapememory.eu/dl3nyw/ymqkFADX]

it seems doing a rename when it crashes.

I will make a test tomorrow morning. I will stop dovecot completely and see what happens then.

@shapememory any updates?

Hello,
�
I think it had something to do with the fact that I was using NAS mounted directories for the storage part.
�
I will retest seaweedfs on SSD storage to cluster a /var/www directory.
�
From: Chris Lu @.>
Sent: Wednesday, May 25, 2022 8:57 PM
To: chrislusf/seaweedfs @.>
Cc: shapememory @.>; Mention @.>
Subject: Re: [chrislusf/seaweedfs] weed mount - crashed on rename operation - mount point down (Issue #3039)
�
@shapememory https://click.shapememory.eu/dl3nyw/FSuBdiMv  any updates?
—
Reply to this email directly, view it on GitHub https://click.shapememory.eu/dl3nyw/McwtB2dh#issuecomment-1137725699 , or unsubscribe https://click.shapememory.eu/dl3nyw/waPsk52H .
You are receiving this because you were mentioned.  https://click.shapememory.eu/dl3nyw/tiFndWrY Message ID: @.*** @.***> >


[CMake] Reorganize CMakeLists.txt for ASTGen

Remove redundant -Xcc -I -Xcc ${include_path}. All required paths are provided by the dependencies, or include_directories(), and  to swiftc -I is propagated to ClangImporter. So no need to specify them explicitly.
Sink C/C++ interop related options to add_pure_swift_host_library(), and add CXX_INTEROP  option to control them.
Move add_pure_swift_host_library() to each source directory instead of doing everything in lib/ASTGen/CMakeLists.txt

@swift-ci Please smoke test


Fixed URLs and dates.

Please remove the text (Seneca 3.x is due for release late June 2016).

The gitter url is not pointing to the correct address: https://gitter.im/senecajs/seneca

in header the parambulator link is broken

:+1:


Is there a way to generate the flowchart via CLI?

see title

Hello, generating a flowchart via CLI is not supported at the moment, though this feature is included in our Business Suite API roadmap. For now, you can generate a flowchart by visiting https://codeflow.jomimi.com/graph, where you can upload a file or a folder directly.

Obviously there are many cases where sharing a codebase with an external API is an instant no-go.
Bummer.


Stable/1.11.x

fix db conflicts  mysql - postgis
def allow_migrate(self, db, app_label, **hints):

    try:
        db_app_mapping = settings.DB_APPS_MAPPING.get(app_label, DEFAULT_DB_ALIAS)
        #if database are mapped and database check your mapped database ,
        if db_app_mapping != db:
            return False
    except AttributeError:
        pass

    for router in self.routers:
        try:
            method = router.allow_migrate
        except AttributeError:
            # If the router doesn't have a method, skip to the next one.
            continue

        allow = method(db, app_label, **hints)

        if allow is not None:
            return allow
    return True

Hi, I'm not sure what you're proposing exactly. A Trac ticket that explains the issue as well as a test are required. In addition, the pull request should go to the master branch rather than stable/1.11.x.


A member of Agora's class PreImageInfo have been changed.

It changed from distance to height.
Changes should be checked and applied to endpoints that provide validator information.

https://github.com/bosagora/stoa/issues/320


chore: Remove generated Markdown GIF image title

Used a regex \.gif\s+"\w*"\) to find/replace the placeholder title values. Since these are the same as the image file name, they don't add value

@nschonni : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@corob-msft - Would you review the proposed updates? Thanks.

@nschonni Thanks for looking into this. Your intentions are good, but the solution is slightly off. You are right that nobody cares what the original image file name was. The source link text turns into the image's alt text attribute, and the text you deleted turns into the title attribute. However, in three out of three browsers I tried (Edge, Chrome, Firefox) the hover tooltip is populated by the title attribute, not the alt attribute (which is still needed for screen readers, I believe). The preferred solution is not just to remove the useless image file names from the titles, but to replace them with the link text (so, yes, that's also duplicated info, but it has the right effect in real world browsers). I've been doing this on a document-by-document basis as I touched them, but hadn't gone through them wholesale. We probably need the same work done for .png files, as well.
I'll close this PR, since it's not quite what I'd like to see merged. If you're willing to revisit it and run another regex on images that captures the link text and adds or replaces it as the title text, that will get a welcome reception. Thanks for all your contributions!

However, in three out of three browsers I tried (Edge, Chrome, Firefox) the hover tooltip is populated by the title attribute

Correct, but title also doesn't work for keyboard and touch users. There are CSS things that can be driven to expose that info, but if the information should be visable, a figcaption is probably more appropriate

We probably need the same work done for .png files, as well.

That was done separately in #565

I'll close this PR, since it's not quite what I'd like to see merged. If you're willing to revisit it and run another regex on images that captures the link text and adds or replaces it as the title text, that will get a welcome reception.

Nope, I'm just going to delete this. Duplicating the alt text in the title isn't correct either. This was just removing the generated text that gave bad tooltips.


Allow models to contain string-based datetime fields that indicate UTC

Treats the following as valid datetime string values:

2018-11-02T23:59:01.824 (assumed to be UTC)
2018-11-02T23:59:01.824Z (UTC in simplified extended ISO format)
2018-11-02T23:59:01.824+00:00 (GMT, equivalent to UTC)

Fixes #135.

I refactored the tests. Are any other changes needed?

Everything looks good! Thank you for the contribution.
Sorry it took that long to merge this PR.


Create .npmignore

Remove test/ folder from being published with the npm package

thanks for the PR! we already use the files field to whitelist folders to do this:
https://github.com/defunctzombie/node-util/blob/a5a2f846817e34d2f1bee8a02034ee23954918b3/package.json#L18-L21


Issue #164 - Add an option to not download videos to the Hub, if not desired.

Added an option "store_videos_on_hub" that defaults to true, to VideoRecordingOptions.

Just verified that this was fixed in another commit.
You can just specify "videos_to_keep": "0", and it will not even initiate the download, so this patch is no longer needed.


fanbox-dl: 0.27.1 -> 0.27.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/hareku/fanbox-dl/releases.
meta.description for fanbox-dl is: Pixiv FANBOX Downloader
meta.homepage for fanbox-dl is: https://github.com/hareku/fanbox-dl
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.27.2 in filename of file in /nix/store/hkw96ilb1wqchjdq3jxj9xhn8b54kjps-fanbox-dl-0.27.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

fanbox-dl

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/hkw96ilb1wqchjdq3jxj9xhn8b54kjps-fanbox-dl-0.27.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/22520a207c3d8a9ccc32ea6c41148fbaab5393d6#fanbox-dl

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hkw96ilb1wqchjdq3jxj9xhn8b54kjps-fanbox-dl-0.27.2
ls -la /nix/store/hkw96ilb1wqchjdq3jxj9xhn8b54kjps-fanbox-dl-0.27.2/bin

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

x86_64-linux

:white_check_mark: 1 package built:

fanbox-dl

Maintainer pings
cc @moni-dz for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Control Board Rev. B

Should we make a rev. B:

[ ] All 0.1uF capacitors - change from 0402 to 0603

This design is now deprecated


fixed vulnerabilities CVE-2021-40690

Updated cxf to avoid CVE-2021-40690 vulnerabilites

@bjornvester Can you approve & merge this PR? Security scanners are reporting this plugin as unsafe due to the mentioned CVE in cxf, and this is the fix.


CAV-327 - Update hmrc libraries to the latest version

Update HMRC libraries.
Fixed unit tests:

FakeRequest is a POST (not the default of GET)
Location header url does not use routes anymore and as a result the unit tests produce the same results and pass in both IntelliJ and the command line

rebuild

I believe if this branch is rebased with main then the tests will pass

@johno1985 if you are happy can you resolve the 2 above and approve this one please?

Happy to approve


hover col for datetime.date is not formatted

datetime.date(2020, 1, 1)
maybe related to https://github.com/ioam/holoviews/issues/1261?

@ahuang11 This is not reproducible for me, at minimum I'd have to know the element type. I've encountered no issues with Curve or Scatter.


Missing function delete_case_task

Request Type
Feature Request
Problem Description
Hi,
the ability to delete task seems to be missing.
My use-case for this may seems a bit cumbersome, and could need a new bug/feature request: I want to be able to attach informative files (not infected) ZIP,PDF,... to a case, and so that they will be visible on the case main page thus not doing a "file" observbable, but instead creating a dummy task, and inside a dummy task log with the file attached, then I'd like to cleanup the task. Attached files are kept, and visible in the front case page.
Cheers,
-- Mathieu
Amadeus CERT

PR#191 implements this task deletion feature (mimicked from browsser interaction when clicking on task's "Delete" button) with the patch {"status":"Cancel"} request.

Thanks @gelim
This issue and PR unveils an issue in TheHive that lists attachments from deleted tasks, which is wrong.

TheHive that lists attachments from deleted tasks, which is wrong.

heh yes, I finally don't use this workaround and decided to handle attachment on an external webserver, and just build a markdown table listing the files + link in the case description. Additionally that allows me not clobber too much ES with file blobs.
All of that works of course as I just need to attach files at creation time.


Add ability to import a HAR

@pmouawad (Bug 62460):
This can be an interesting way to easily create a Test Plan.
OS: All

I think this would be a really useful feature, and see as the original ticket didn't go into a lot of detail I'll provide my use case. When I need to run a load test on a website I want to capture all of the requests that happen during a page load and replay them through JMeter. The current way of doing this is:

Create an HTTP(S) Test Script Recorder
Create a Recording Controller
Click start on the Test Script Recorder
Configure your browser to use JMeter as a proxy
Load the page, ignoring the TLS warning
Stop the recording
Remove the proxy configuration from your browser
Go through the recorded requests to remove requests from other browser tabs and the browser itself.

This can be a very time consuming process if you need to add many pages to your test plan. Compare this to a potential workflow that uses HAR files.

Open the developer tools in your browser
Load the page
In the Network tab of the dev tools, right click and export as a HAR file.
In JMeter right click on the Thread Group and click "Add HTTP requests from HAR file"

This would indeed be a very useful feature that is highly desirable to add
to the application.
On Fri, Feb 3, 2023 at 9:11 PM Aaron Spaulding @.***>
wrote:

I think this would be a really useful feature, and see as the original
ticket didn't go into a lot of detail I'll provide my use case. When I need
to run a load test on a website I want to capture all of the requests that
happen during a page load and replay them through JMeter. The current way
of doing this is:

Create an HTTP(S) Test Script Recorder
Create a Recording Controller
Click start on the Test Script Recorder
Configure your browser to use JMeter as a proxy
Load the page, ignoring the TLS warning
Stop the recording
Remove the proxy configuration from your browser
Go through the recorded requests to remove requests from other
browser tabs and the browser itself.

This can be a very time consuming process if you need to add many pages to
your test plan. Compare this to a potential workflow that uses HAR files.

Open the developer tools in your browser
Load the page
In the Network tab of the dev tools, right click and export as a HAR
file.
In JMeter right click on the Thread Group and click "Add HTTP
requests from HAR file"

—
Reply to this email directly, view it on GitHub
https://github.com/apache/jmeter/issues/4797#issuecomment-1416286992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXQDSTICBEUGEKJNEV5WQTWVVJ4PANCNFSM6AAAAAAUQTFGEU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Sincerely,
Shay Ginsbourg, M.Sc.
Mobile: 972 54 66 909 15
eMail: @.***
Website: Ginsbourg.co.il http://ginsbourg.co.il/
LinkedIn: linkedin.com/in/shayginsbourg
Office: 57 Kedem St. Jaffa Israel 6817677
Software, Medical, and Mechanical Engineer.
Performance, Automation, and Load Testing Expert.
Regulatory Affairs Consultant.
Freelancer since 2008.


i am geting error in icon

The component is awesome but it wants some updates to do that
i m getting this error
./src/views/History/History.js
Module not found: Can't resolve '@material-ui/icons' in 'E:\ex\coreui-client\src\views\History'

Maybe you need to add to your package.json the '@material-ui/icons' dependencies.
You can find an example here :
https://github.com/stephane-monnot/resume/blob/master/package.json
Indeed, the dependence material ui is not part of react-vertical-timeline package.

add I done that nothing is happening you just forget it I'll manage it by
my own it's information for you
On Thu, Dec 6, 2018 at 10:41 PM Stéphane Monnot<EMAIL_ADDRESS>wrote:

Maybe you need to add to your package.json the '@material-ui/icons'
dependencies.
You can find an example here :
https://github.com/stephane-monnot/resume/blob/master/package.json
Indeed, the dependence material ui is not part of react-vertical-timeline
package.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stephane-monnot/react-vertical-timeline/issues/25#issuecomment-444951162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnGMtuFWufhU2UGzlZg4Nsn44NAt7nHbks5u2U-mgaJpZM4ZCPCP
.


[portBLAS] Add USM support for rotmg

This pull request adds USM support for the rotmg operator and updates the test to align it with the Buffer test.

[X] Do all unit tests pass locally? TestResults_level1_rotmg.html.zip
[X] Have you formatted the code using clang-format?

Hi @andrewtbarker, could you please take a look at this PR and share feedback? Thanks.


Cannot build using bazel 8

❯ bazel build //:fizzbee
2024/12/13 20:52:44 Downloading https://releases.bazel.build/8.0.0/release/bazel-8.0.0-darwin-arm64...
Downloading: 56 MB out of 56 MB (100%)
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
WARNING: Couldn't auto load rules or symbols, because no dependency on module/repository 'rules_android' found. This will result in a failure if there's a reference to those rules or symbols.
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:fizzbee': error loading package '': Unable to find package for @@[unknown repo 'io_bazel_rules_go' requested from @@]//go:def.bzl: The repository '@@[unknown repo 'io_bazel_rules_go' requested from @@]' could not be resolved: No repository visible as '@io_bazel_rules_go' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.
ERROR: error loading package '': Unable to find package for @@[unknown repo 'io_bazel_rules_go' requested from @@]//go:def.bzl: The repository '@@[unknown repo 'io_bazel_rules_go' requested from @@]' could not be resolved: No repository visible as '@io_bazel_rules_go' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.
INFO: Elapsed time: 16.963s
INFO: 0 processes.
ERROR: Build did NOT complete successfully

As a workaround I've told bazelisk to use 7.x, ie:
echo 7.x > .bazelversion

Oops, I don't know why I closed this issue. Reopening it. To track the proper fix.

@tekumara Would you be able to help migrate to Bzlmod


Issue 25 26

Hello @GaetanDu! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file autopycoin/baseclass.py:

Line 37:80: E501 line too long (83 > 79 characters)
Line 52:80: E501 line too long (80 > 79 characters)
Line 55:12: E713 test for membership should be 'not in'
Line 78:17: E713 test for membership should be 'not in'
Line 97:80: E501 line too long (83 > 79 characters)
Line 132:80: E501 line too long (80 > 79 characters)

In the file autopycoin/constant.py:

Line 3:31: W291 trailing whitespace
Line 7:80: E501 line too long (122 > 79 characters)

In the file autopycoin/dataset/generator.py:

Line 64:80: E501 line too long (87 > 79 characters)
Line 175:80: E501 line too long (86 > 79 characters)
Line 176:1: W293 blank line contains whitespace
Line 177:80: E501 line too long (83 > 79 characters)
Line 182:80: E501 line too long (99 > 79 characters)
Line 322:80: E501 line too long (115 > 79 characters)
Line 354:80: E501 line too long (87 > 79 characters)
Line 391:80: E501 line too long (85 > 79 characters)
Line 401:80: E501 line too long (96 > 79 characters)
Line 412:80: E501 line too long (106 > 79 characters)
Line 464:80: E501 line too long (100 > 79 characters)
Line 579:80: E501 line too long (101 > 79 characters)
Line 791:80: E501 line too long (91 > 79 characters)

In the file autopycoin/extension_type.py:

Line 11:1: E302 expected 2 blank lines, found 1
Line 26:80: E501 line too long (85 > 79 characters)
Line 29:80: E501 line too long (84 > 79 characters)
Line 45:80: E501 line too long (132 > 79 characters)
Line 45:102: E252 missing whitespace around parameter equals
Line 45:103: E252 missing whitespace around parameter equals
Line 54:80: E501 line too long (121 > 79 characters)
Line 57:80: E501 line too long (120 > 79 characters)
Line 62:80: E501 line too long (286 > 79 characters)
Line 63:80: E501 line too long (83 > 79 characters)
Line 64:80: E501 line too long (83 > 79 characters)
Line 65:25: E231 missing whitespace after ':'
Line 65:27: E251 unexpected spaces around keyword / parameter equals
Line 65:80: E501 line too long (95 > 79 characters)
Line 67:80: E501 line too long (224 > 79 characters)
Line 68:25: E231 missing whitespace after ':'
Line 68:27: E251 unexpected spaces around keyword / parameter equals
Line 68:80: E501 line too long (91 > 79 characters)
Line 70:80: E501 line too long (191 > 79 characters)
Line 71:80: E501 line too long (133 > 79 characters)
Line 75:80: E501 line too long (110 > 79 characters)
Line 77:80: E501 line too long (176 > 79 characters)
Line 79:80: E501 line too long (139 > 79 characters)
Line 83:80: E501 line too long (92 > 79 characters)
Line 85:80: E501 line too long (141 > 79 characters)
Line 87:80: E501 line too long (104 > 79 characters)
Line 91:80: E501 line too long (111 > 79 characters)
Line 92:80: E501 line too long (96 > 79 characters)
Line 93:80: E501 line too long (112 > 79 characters)
Line 95:80: E501 line too long (124 > 79 characters)
Line 96:80: E501 line too long (119 > 79 characters)
Line 98:80: E501 line too long (88 > 79 characters)
Line 109:80: E501 line too long (90 > 79 characters)
Line 114:80: E501 line too long (87 > 79 characters)
Line 119:80: E501 line too long (88 > 79 characters)
Line 124:80: E501 line too long (103 > 79 characters)
Line 125:80: E501 line too long (81 > 79 characters)
Line 129:80: E501 line too long (100 > 79 characters)
Line 130:80: E501 line too long (96 > 79 characters)
Line 131:80: E501 line too long (114 > 79 characters)
Line 133:80: E501 line too long (126 > 79 characters)
Line 134:80: E501 line too long (107 > 79 characters)
Line 143:80: E501 line too long (116 > 79 characters)
Line 145:80: E501 line too long (83 > 79 characters)
Line 149:80: E501 line too long (104 > 79 characters)
Line 151:80: E501 line too long (152 > 79 characters)
Line 153:80: E501 line too long (119 > 79 characters)
Line 157:80: E501 line too long (163 > 79 characters)
Line 160:80: E501 line too long (89 > 79 characters)
Line 161:80: E501 line too long (92 > 79 characters)
Line 165:80: E501 line too long (108 > 79 characters)
Line 166:80: E501 line too long (91 > 79 characters)
Line 170:80: E501 line too long (102 > 79 characters)
Line 171:80: E501 line too long (95 > 79 characters)
Line 172:80: E501 line too long (113 > 79 characters)
Line 174:80: E501 line too long (125 > 79 characters)
Line 175:80: E501 line too long (110 > 79 characters)
Line 182:80: E501 line too long (148 > 79 characters)
Line 188:80: E501 line too long (81 > 79 characters)
Line 189:80: E501 line too long (107 > 79 characters)
Line 189:108: W291 trailing whitespace
Line 190:80: E501 line too long (108 > 79 characters)
Line 191:80: E501 line too long (96 > 79 characters)
Line 192:80: E501 line too long (96 > 79 characters)
Line 197:80: E501 line too long (116 > 79 characters)
Line 197:117: W291 trailing whitespace
Line 198:36: E128 continuation line under-indented for visual indent
Line 198:80: E501 line too long (108 > 79 characters)
Line 199:80: E501 line too long (96 > 79 characters)
Line 200:80: E501 line too long (96 > 79 characters)
Line 206:80: E501 line too long (124 > 79 characters)
Line 208:80: E501 line too long (86 > 79 characters)
Line 218:80: E501 line too long (102 > 79 characters)
Line 219:80: E501 line too long (88 > 79 characters)
Line 222:80: E501 line too long (93 > 79 characters)
Line 225:80: E501 line too long (105 > 79 characters)
Line 231:69: W291 trailing whitespace
Line 235:80: E501 line too long (83 > 79 characters)
Line 236:80: E501 line too long (83 > 79 characters)
Line 237:25: E231 missing whitespace after ':'
Line 237:27: E251 unexpected spaces around keyword / parameter equals
Line 237:80: E501 line too long (95 > 79 characters)
Line 239:80: E501 line too long (130 > 79 characters)
Line 240:25: E231 missing whitespace after ':'
Line 240:27: E251 unexpected spaces around keyword / parameter equals
Line 240:80: E501 line too long (91 > 79 characters)
Line 242:80: E501 line too long (97 > 79 characters)

In the file autopycoin/layers/__init__.py:

Line 13:17: W291 trailing whitespace
Line 14:21: W291 trailing whitespace

In the file autopycoin/layers/base_layer.py:

Line 9:80: E501 line too long (128 > 79 characters)
Line 44:80: E501 line too long (93 > 79 characters)
Line 45:1: W293 blank line contains whitespace
Line 53:80: E501 line too long (109 > 79 characters)
Line 63:80: E501 line too long (98 > 79 characters)
Line 63:99: W291 trailing whitespace
Line 64:61: W291 trailing whitespace
Line 65:80: E501 line too long (96 > 79 characters)
Line 67:80: E501 line too long (116 > 79 characters)
Line 68:80: E501 line too long (84 > 79 characters)
Line 69:80: E501 line too long (101 > 79 characters)
Line 70:80: E501 line too long (129 > 79 characters)
Line 71:80: E501 line too long (95 > 79 characters)
Line 77:80: E501 line too long (92 > 79 characters)
Line 81:80: E501 line too long (93 > 79 characters)
Line 94:80: E501 line too long (110 > 79 characters)
Line 94:111: W291 trailing whitespace
Line 98:55: E252 missing whitespace around parameter equals
Line 98:56: E252 missing whitespace around parameter equals
Line 98:80: E501 line too long (99 > 79 characters)
Line 108:80: E501 line too long (165 > 79 characters)
Line 108:103: E252 missing whitespace around parameter equals
Line 108:104: E252 missing whitespace around parameter equals
Line 108:151: E252 missing whitespace around parameter equals
Line 108:152: E252 missing whitespace around parameter equals
Line 109:80: E501 line too long (86 > 79 characters)
Line 114:80: E501 line too long (89 > 79 characters)
Line 121:80: E501 line too long (83 > 79 characters)
Line 122:80: E501 line too long (81 > 79 characters)
Line 124:80: E501 line too long (85 > 79 characters)
Line 125:80: E501 line too long (98 > 79 characters)
Line 126:80: E501 line too long (102 > 79 characters)
Line 127:80: E501 line too long (97 > 79 characters)
Line 129:80: E501 line too long (99 > 79 characters)
Line 141:80: E501 line too long (90 > 79 characters)
Line 146:80: E501 line too long (82 > 79 characters)
Line 154:80: E501 line too long (84 > 79 characters)
Line 156:80: E501 line too long (109 > 79 characters)
Line 156:81: E261 at least two spaces before inline comment
Line 158:80: E501 line too long (109 > 79 characters)
Line 161:80: E501 line too long (80 > 79 characters)
Line 163:1: W293 blank line contains whitespace
Line 164:31: W291 trailing whitespace
Line 167:80: E501 line too long (82 > 79 characters)
Line 167:83: W291 trailing whitespace
Line 177:80: E501 line too long (109 > 79 characters)
Line 187:29: E222 multiple spaces after operator
Line 203:80: E501 line too long (100 > 79 characters)
Line 203:101: W291 trailing whitespace
Line 204:62: W291 trailing whitespace
Line 205:80: E501 line too long (96 > 79 characters)
Line 206:80: E501 line too long (133 > 79 characters)
Line 206:134: W291 trailing whitespace
Line 208:80: E501 line too long (118 > 79 characters)
Line 209:80: E501 line too long (84 > 79 characters)
Line 210:80: E501 line too long (104 > 79 characters)
Line 211:80: E501 line too long (131 > 79 characters)
Line 212:80: E501 line too long (95 > 79 characters)
Line 227:80: E501 line too long (110 > 79 characters)
Line 227:111: W291 trailing whitespace
Line 231:58: E252 missing whitespace around parameter equals
Line 231:59: E252 missing whitespace around parameter equals
Line 231:80: E501 line too long (102 > 79 characters)
Line 240:80: E501 line too long (100 > 79 characters)
Line 241:80: E501 line too long (106 > 79 characters)
Line 247:80: E501 line too long (83 > 79 characters)
Line 251:80: E501 line too long (172 > 79 characters)
Line 252:80: E501 line too long (103 > 79 characters)
Line 253:80: E501 line too long (100 > 79 characters)
Line 256:80: E501 line too long (243 > 79 characters)
Line 256:135: E252 missing whitespace around parameter equals
Line 256:175: E252 missing whitespace around parameter equals
Line 256:176: E252 missing whitespace around parameter equals
Line 256:229: E252 missing whitespace around parameter equals
Line 256:230: E252 missing whitespace around parameter equals
Line 258:1: W293 blank line contains whitespace
Line 275:80: E501 line too long (114 > 79 characters)
Line 275:100: E252 missing whitespace around parameter equals
Line 275:101: E252 missing whitespace around parameter equals
Line 280:80: E501 line too long (122 > 79 characters)
Line 280:108: E252 missing whitespace around parameter equals
Line 280:109: E252 missing whitespace around parameter equals
Line 286:80: E501 line too long (101 > 79 characters)
Line 286:87: E252 missing whitespace around parameter equals
Line 286:88: E252 missing whitespace around parameter equals
Line 287:80: E501 line too long (109 > 79 characters)
Line 301:14: W292 no newline at end of file

In the file autopycoin/layers/nbeats_layers.py:

Line 117:80: E501 line too long (107 > 79 characters)
Line 118:80: E501 line too long (107 > 79 characters)
Line 135:23: E222 multiple spaces after operator
Line 137:23: E222 multiple spaces after operator
Line 223:80: E501 line too long (86 > 79 characters)
Line 227:80: E501 line too long (102 > 79 characters)
Line 231:51: W291 trailing whitespace
Line 394:80: E501 line too long (100 > 79 characters)
Line 396:80: E501 line too long (84 > 79 characters)
Line 594:80: E501 line too long (148 > 79 characters)
Line 618:80: E501 line too long (98 > 79 characters)
Line 623:80: E501 line too long (84 > 79 characters)

In the file autopycoin/layers/nbeats_layers_test.py:

Line 249:80: E501 line too long (93 > 79 characters)
Line 362:80: E501 line too long (89 > 79 characters)
Line 466:80: E501 line too long (89 > 79 characters)
Line 491:80: E501 line too long (89 > 79 characters)

In the file autopycoin/losses/losses.py:

Line 37:80: E501 line too long (92 > 79 characters)
Line 61:80: E501 line too long (84 > 79 characters)
Line 226:80: E501 line too long (93 > 79 characters)
Line 235:80: E501 line too long (93 > 79 characters)

In the file autopycoin/models/nbeats.py:

Line 85:80: E501 line too long (164 > 79 characters)
Line 85:86: E252 missing whitespace around parameter equals
Line 85:87: E252 missing whitespace around parameter equals
Line 85:128: E252 missing whitespace around parameter equals
Line 85:129: E252 missing whitespace around parameter equals
Line 87:80: E501 line too long (153 > 79 characters)
Line 170:80: E501 line too long (103 > 79 characters)
Line 171:80: E501 line too long (109 > 79 characters)
Line 274:80: E501 line too long (114 > 79 characters)
Line 305:15: E128 continuation line under-indented for visual indent
Line 306:15: E128 continuation line under-indented for visual indent
Line 307:15: E128 continuation line under-indented for visual indent
Line 308:15: E128 continuation line under-indented for visual indent
Line 309:15: E128 continuation line under-indented for visual indent
Line 310:15: E128 continuation line under-indented for visual indent
Line 311:15: E128 continuation line under-indented for visual indent
Line 312:15: E128 continuation line under-indented for visual indent
Line 315:21: E128 continuation line under-indented for visual indent
Line 316:21: E128 continuation line under-indented for visual indent
Line 317:21: E128 continuation line under-indented for visual indent
Line 318:21: E128 continuation line under-indented for visual indent
Line 319:21: E128 continuation line under-indented for visual indent
Line 320:21: E128 continuation line under-indented for visual indent
Line 321:21: E128 continuation line under-indented for visual indent
Line 323:80: E501 line too long (93 > 79 characters)
Line 699:80: E501 line too long (92 > 79 characters)
Line 700:80: E501 line too long (97 > 79 characters)
Line 702:80: E501 line too long (122 > 79 characters)
Line 703:80: E501 line too long (92 > 79 characters)
Line 719:80: E501 line too long (113 > 79 characters)
Line 731:80: E501 line too long (125 > 79 characters)
Line 732:80: E501 line too long (102 > 79 characters)
Line 733:80: E501 line too long (94 > 79 characters)
Line 734:80: E501 line too long (117 > 79 characters)
Line 783:80: E501 line too long (86 > 79 characters)
Line 785:80: E501 line too long (82 > 79 characters)
Line 791:80: E501 line too long (92 > 79 characters)
Line 796:80: E501 line too long (89 > 79 characters)
Line 797:80: E501 line too long (85 > 79 characters)
Line 800:80: E501 line too long (113 > 79 characters)
Line 801:80: E501 line too long (111 > 79 characters)
Line 803:80: E501 line too long (81 > 79 characters)
Line 804:32: W291 trailing whitespace
Line 805:80: E501 line too long (134 > 79 characters)
Line 807:80: E501 line too long (110 > 79 characters)
Line 809:80: E501 line too long (107 > 79 characters)
Line 816:80: E501 line too long (111 > 79 characters)
Line 833:9: E125 continuation line with same indent as next logical line
Line 837:80: E501 line too long (109 > 79 characters)
Line 839:32: E225 missing whitespace around operator
Line 839:80: E501 line too long (86 > 79 characters)
Line 840:80: E501 line too long (122 > 79 characters)
Line 841:80: E501 line too long (83 > 79 characters)
Line 861:80: E501 line too long (93 > 79 characters)
Line 863:1: W293 blank line contains whitespace
Line 864:80: E501 line too long (82 > 79 characters)
Line 867:9: E731 do not assign a lambda expression, use a def
Line 876:45: E231 missing whitespace after ','
Line 876:79: E231 missing whitespace after ','
Line 876:80: E501 line too long (86 > 79 characters)
Line 885:80: E501 line too long (80 > 79 characters)
Line 891:45: E231 missing whitespace after ','
Line 891:79: E231 missing whitespace after ','
Line 891:80: E501 line too long (86 > 79 characters)
Line 897:80: E501 line too long (91 > 79 characters)
Line 905:12: E222 multiple spaces after operator

In the file autopycoin/models/nbeats_test.py:

Line 241:80: E501 line too long (89 > 79 characters)
Line 246:52: E231 missing whitespace after ','
Line 305:80: E501 line too long (89 > 79 characters)
Line 307:80: E501 line too long (143 > 79 characters)
Line 468:9: E731 do not assign a lambda expression, use a def
Line 468:30: E203 whitespace before ':'
Line 468:31: E231 missing whitespace after ':'
Line 513:80: E501 line too long (92 > 79 characters)
Line 524:80: E501 line too long (95 > 79 characters)
Line 539:9: E731 do not assign a lambda expression, use a def
Line 539:30: E203 whitespace before ':'
Line 582:80: E501 line too long (92 > 79 characters)
Line 593:80: E501 line too long (95 > 79 characters)
Line 629:35: E231 missing whitespace after ','
Line 629:41: E231 missing whitespace after ','
Line 629:44: E231 missing whitespace after ','
Line 636:38: W291 trailing whitespace
Line 637:38: W291 trailing whitespace
Line 638:29: W291 trailing whitespace
Line 639:28: W291 trailing whitespace
Line 700:42: W291 trailing whitespace
Line 701:42: W291 trailing whitespace
Line 702:33: W291 trailing whitespace
Line 703:32: W291 trailing whitespace
Line 708:39: W291 trailing whitespace
Line 745:80: E501 line too long (80 > 79 characters)
Line 746:80: E501 line too long (84 > 79 characters)
Line 751:1: W293 blank line contains whitespace
Line 756:42: W291 trailing whitespace
Line 757:42: W291 trailing whitespace
Line 758:33: W291 trailing whitespace
Line 759:32: W291 trailing whitespace
Line 764:39: W291 trailing whitespace
Line 780:80: E501 line too long (206 > 79 characters)
Line 781:80: E501 line too long (95 > 79 characters)
Line 786:80: E501 line too long (112 > 79 characters)
Line 790:14: W292 no newline at end of file

In the file autopycoin/models/pool.py:

Line 13:1: E302 expected 2 blank lines, found 1
Line 19:68: W291 trailing whitespace
Line 32:80: E501 line too long (86 > 79 characters)
Line 36:80: E501 line too long (84 > 79 characters)
Line 57:38: E252 missing whitespace around parameter equals
Line 57:39: E252 missing whitespace around parameter equals
Line 58:28: E252 missing whitespace around parameter equals
Line 58:29: E252 missing whitespace around parameter equals
Line 72:80: E501 line too long (82 > 79 characters)
Line 82:9: E125 continuation line with same indent as next logical line
Line 83:80: E501 line too long (81 > 79 characters)
Line 92:80: E501 line too long (89 > 79 characters)
Line 93:80: E501 line too long (112 > 79 characters)
Line 105:80: E501 line too long (97 > 79 characters)
Line 106:80: E501 line too long (85 > 79 characters)
Line 110:80: E501 line too long (98 > 79 characters)
Line 112:80: E501 line too long (119 > 79 characters)
Line 121:80: E501 line too long (112 > 79 characters)
Line 123:80: E501 line too long (120 > 79 characters)
Line 129:1: W293 blank line contains whitespace
Line 134:15: E128 continuation line under-indented for visual indent
Line 135:15: E128 continuation line under-indented for visual indent
Line 136:15: E128 continuation line under-indented for visual indent
Line 137:15: E128 continuation line under-indented for visual indent
Line 138:15: E128 continuation line under-indented for visual indent
Line 139:15: E128 continuation line under-indented for visual indent
Line 148:80: E501 line too long (119 > 79 characters)
Line 185:9: E125 continuation line with same indent as next logical line
Line 255:45: E231 missing whitespace after ','
Line 255:79: E231 missing whitespace after ','
Line 255:80: E501 line too long (86 > 79 characters)
Line 263:45: E231 missing whitespace after ','
Line 263:79: E231 missing whitespace after ','
Line 263:80: E501 line too long (86 > 79 characters)
Line 271:45: E231 missing whitespace after ','
Line 271:79: E231 missing whitespace after ','
Line 271:80: E501 line too long (86 > 79 characters)

In the file autopycoin/models/training.py:

Line 40:80: E501 line too long (111 > 79 characters)
Line 45:80: E501 line too long (120 > 79 characters)
Line 47:80: E501 line too long (96 > 79 characters)
Line 50:80: E501 line too long (93 > 79 characters)
Line 55:80: E501 line too long (84 > 79 characters)
Line 58:80: E501 line too long (92 > 79 characters)
Line 81:80: E501 line too long (131 > 79 characters)
Line 86:80: E501 line too long (112 > 79 characters)
Line 90:47: E261 at least two spaces before inline comment
Line 90:80: E501 line too long (80 > 79 characters)
Line 93:80: E501 line too long (114 > 79 characters)
Line 94:80: E501 line too long (119 > 79 characters)
Line 95:80: E501 line too long (83 > 79 characters)
Line 98:80: E501 line too long (114 > 79 characters)
Line 99:80: E501 line too long (101 > 79 characters)
Line 102:80: E501 line too long (98 > 79 characters)
Line 104:80: E501 line too long (127 > 79 characters)
Line 109:80: E501 line too long (92 > 79 characters)
Line 113:80: E501 line too long (93 > 79 characters)
Line 124:55: E252 missing whitespace around parameter equals
Line 124:56: E252 missing whitespace around parameter equals
Line 124:80: E501 line too long (98 > 79 characters)
Line 137:19: E261 at least two spaces before inline comment
Line 137:80: E501 line too long (187 > 79 characters)
Line 154:80: E501 line too long (87 > 79 characters)
Line 169:80: E501 line too long (205 > 79 characters)
Line 177:56: E251 unexpected spaces around keyword / parameter equals
Line 177:80: E501 line too long (96 > 79 characters)
Line 185:80: E501 line too long (165 > 79 characters)
Line 185:103: E252 missing whitespace around parameter equals
Line 185:104: E252 missing whitespace around parameter equals
Line 185:151: E252 missing whitespace around parameter equals
Line 185:152: E252 missing whitespace around parameter equals
Line 186:80: E501 line too long (83 > 79 characters)
Line 193:80: E501 line too long (133 > 79 characters)
Line 195:80: E501 line too long (96 > 79 characters)
Line 196:80: E501 line too long (85 > 79 characters)
Line 198:80: E501 line too long (99 > 79 characters)
Line 199:80: E501 line too long (118 > 79 characters)
Line 200:80: E501 line too long (110 > 79 characters)
Line 208:80: E501 line too long (158 > 79 characters)
Line 209:80: E501 line too long (85 > 79 characters)
Line 211:80: E501 line too long (109 > 79 characters)
Line 212:80: E501 line too long (118 > 79 characters)
Line 213:80: E501 line too long (83 > 79 characters)
Line 214:80: E501 line too long (81 > 79 characters)
Line 222:80: E501 line too long (150 > 79 characters)
Line 222:136: E252 missing whitespace around parameter equals
Line 222:137: E252 missing whitespace around parameter equals
Line 228:80: E501 line too long (95 > 79 characters)
Line 229:80: E501 line too long (102 > 79 characters)
Line 230:80: E501 line too long (105 > 79 characters)
Line 231:80: E501 line too long (87 > 79 characters)
Line 237:80: E501 line too long (117 > 79 characters)
Line 238:80: E501 line too long (102 > 79 characters)
Line 240:80: E501 line too long (103 > 79 characters)
Line 241:80: E501 line too long (82 > 79 characters)
Line 244:80: E501 line too long (118 > 79 characters)
Line 247:80: E501 line too long (162 > 79 characters)
Line 250:80: E501 line too long (95 > 79 characters)
Line 252:1: W293 blank line contains whitespace
Line 256:80: E501 line too long (136 > 79 characters)
Line 257:25: E128 continuation line under-indented for visual indent
Line 257:80: E501 line too long (114 > 79 characters)
Line 258:25: E128 continuation line under-indented for visual indent
Line 258:80: E501 line too long (109 > 79 characters)
Line 262:80: E501 line too long (114 > 79 characters)
Line 263:80: E501 line too long (81 > 79 characters)
Line 265:42: E261 at least two spaces before inline comment
Line 267:80: E501 line too long (98 > 79 characters)
Line 269:80: E501 line too long (137 > 79 characters)
Line 270:80: E501 line too long (98 > 79 characters)
Line 274:80: E501 line too long (94 > 79 characters)
Line 322:80: E501 line too long (87 > 79 characters)
Line 332:58: E252 missing whitespace around parameter equals
Line 332:59: E252 missing whitespace around parameter equals
Line 332:80: E501 line too long (101 > 79 characters)
Line 337:80: E501 line too long (242 > 79 characters)
Line 337:133: E252 missing whitespace around parameter equals
Line 337:134: E252 missing whitespace around parameter equals
Line 337:174: E252 missing whitespace around parameter equals
Line 337:175: E252 missing whitespace around parameter equals
Line 337:228: E252 missing whitespace around parameter equals
Line 337:229: E252 missing whitespace around parameter equals
Line 339:1: W293 blank line contains whitespace
Line 344:80: E501 line too long (91 > 79 characters)
Line 348:80: E501 line too long (134 > 79 characters)
Line 353:159: W292 no newline at end of file

In the file autopycoin/models/training_test.py:

Line 23:1: W293 blank line contains whitespace
Line 24:58: E252 missing whitespace around parameter equals
Line 24:59: E252 missing whitespace around parameter equals
Line 24:80: E501 line too long (93 > 79 characters)
Line 46:1: E302 expected 2 blank lines, found 1
Line 48:58: E252 missing whitespace around parameter equals
Line 48:59: E252 missing whitespace around parameter equals
Line 48:80: E501 line too long (93 > 79 characters)
Line 70:58: E252 missing whitespace around parameter equals
Line 70:59: E252 missing whitespace around parameter equals
Line 70:80: E501 line too long (93 > 79 characters)
Line 90:58: E252 missing whitespace around parameter equals
Line 90:59: E252 missing whitespace around parameter equals
Line 90:80: E501 line too long (93 > 79 characters)
Line 178:39: E261 at least two spaces before inline comment
Line 181:1: W293 blank line contains whitespace
Line 182:5: E303 too many blank lines (2)
Line 184:9: E122 continuation line missing indentation or outdented
Line 185:9: E122 continuation line missing indentation or outdented
Line 186:9: E122 continuation line missing indentation or outdented
Line 186:80: E501 line too long (80 > 79 characters)
Line 187:9: E122 continuation line missing indentation or outdented
Line 187:80: E501 line too long (109 > 79 characters)
Line 188:9: E122 continuation line missing indentation or outdented
Line 188:80: E501 line too long (154 > 79 characters)
Line 189:9: E122 continuation line missing indentation or outdented
Line 195:80: E501 line too long (120 > 79 characters)
Line 198:80: E501 line too long (124 > 79 characters)
Line 202:9: E122 continuation line missing indentation or outdented
Line 202:80: E501 line too long (139 > 79 characters)
Line 203:9: E122 continuation line missing indentation or outdented
Line 203:80: E501 line too long (141 > 79 characters)
Line 204:9: E122 continuation line missing indentation or outdented
Line 204:80: E501 line too long (93 > 79 characters)
Line 205:9: E122 continuation line missing indentation or outdented
Line 205:80: E501 line too long (125 > 79 characters)
Line 206:9: E122 continuation line missing indentation or outdented
Line 206:80: E501 line too long (120 > 79 characters)
Line 207:9: E122 continuation line missing indentation or outdented
Line 208:9: E122 continuation line missing indentation or outdented
Line 208:80: E501 line too long (139 > 79 characters)
Line 214:80: E501 line too long (123 > 79 characters)
Line 217:80: E501 line too long (127 > 79 characters)
Line 218:1: W293 blank line contains whitespace
Line 221:9: E122 continuation line missing indentation or outdented
Line 221:80: E501 line too long (140 > 79 characters)
Line 222:9: E122 continuation line missing indentation or outdented
Line 222:80: E501 line too long (93 > 79 characters)
Line 223:9: E122 continuation line missing indentation or outdented
Line 229:80: E501 line too long (124 > 79 characters)
Line 232:80: E501 line too long (128 > 79 characters)
Line 237:80: E501 line too long (80 > 79 characters)
Line 238:80: E501 line too long (87 > 79 characters)
Line 239:80: E501 line too long (116 > 79 characters)
Line 240:80: E501 line too long (161 > 79 characters)
Line 242:80: E501 line too long (129 > 79 characters)
Line 245:80: E501 line too long (82 > 79 characters)
Line 247:80: E501 line too long (137 > 79 characters)
Line 250:80: E501 line too long (141 > 79 characters)

In the file autopycoin/test_utils/__init__.py:

Line 7:18: E261 at least two spaces before inline comment

In the file autopycoin/test_utils/testing_utils.py:

Line 86:80: E501 line too long (134 > 79 characters)
Line 302:80: E501 line too long (125 > 79 characters)
Line 304:1: W293 blank line contains whitespace
Line 308:80: E501 line too long (119 > 79 characters)
Line 310:80: E501 line too long (81 > 79 characters)
Line 312:80: E501 line too long (139 > 79 characters)
Line 320:80: E501 line too long (86 > 79 characters)
Line 336:43: E231 missing whitespace after ','
Line 336:61: E231 missing whitespace after ','
Line 336:80: E501 line too long (93 > 79 characters)

In the file autopycoin/utils/__init__.py:

Line 1:4: W291 trailing whitespace

In the file autopycoin/utils/data_utils.py:

Line 55:80: E501 line too long (135 > 79 characters)
Line 72:80: E501 line too long (81 > 79 characters)
Line 74:1: W293 blank line contains whitespace
Line 79:80: E501 line too long (96 > 79 characters)
Line 81:80: E501 line too long (87 > 79 characters)
Line 82:1: W293 blank line contains whitespace
Line 85:39: W291 trailing whitespace
Line 90:71: W291 trailing whitespace

In the file autopycoin/utils/data_utils_test.py:

Line 37:80: E501 line too long (95 > 79 characters)


fix(cdk/drag-drop): resolve helper directives with DI for proper hostDirectives support

Currently CdkDrag resolves its helper directives (e.g. handle or preview) using a content query, but that doesn't work when it's applied as a host directive, because no content is being projected.
These changes switch to having the helper directives inject the closest drag directive and register themselves manually.
Fixes #28614.

@crisbeto our app uses some nested drag-drop and this PR has broken the functionality. It seems that the cdkDragHandle is connecting to the wrong cdkDrag. I have not diagnosed exactly the issue yet but will get back to you.

I think the changes in this commit may have caused a dependency injection issue when combining virtual scroll and drag and drop. I've setup a very minimal StackBlitz example to show the issue here: https://stackblitz.com/edit/f2xpkk. If you load the example as it is currently with version 17.2.2, you'll see the following stack trace:
vendor.js:47027 ERROR NullInjectorError: R3InjectorError(Standalone[CdkVirtualScrollAppendOnlyExample])[InjectionToken CDK_DRAG_PARENT -> InjectionToken CDK_DRAG_PARENT -> InjectionToken CDK_DRAG_PARENT]:    NullInjectorError: No provider for InjectionToken CDK_DRAG_PARENT!     at NullInjector.get (vendor.js:44290:21)     at R3Injector.get (vendor.js:44741:27)     at R3Injector.get (vendor.js:44741:27)     at R3Injector.get (vendor.js:44741:27)     at ChainedInjector.get (vendor.js:55693:32)     at lookupTokenUsingModuleInjector (vendor.js:46282:31)     at getOrCreateInjectable (vendor.js:46328:10)     at ɵɵdirectiveInject (vendor.js:49755:17)     at ɵɵinject (vendor.js:43467:59)     at inject (vendor.js:43550:10)
If you go to package.json and set all the angular packages to 17.2.1 and refresh, the page will load with no issues. Is this expected or intentional based on the layout of the component?


Code running with single quotes but not with double quotes ,why?(in the firstnlast function with 'a')

https://github.com/Java-Techie-jt/devops-automation/issues/10

Please stop spamming GitHub repository issues with generic programming questions.
Issues are for reporting bugs or ask for enhancements for specific projects, not for generic off-topic discussions.
It's great that you want to learn programming, but GitHub issues are not the place to ask your questions. StackOverflow.com would be a better fit for those.
You're doing yourself a disservice by spamming random GitHub projects with your questions. All you'll get is being blocked/banned from repositories, possibly even from GitHub as a whole.

Please stop spamming GitHub repository issues with generic programming questions.
Issues are for reporting bugs or ask for enhancements for specific projects, not for generic off-topic discussions.
It's great that you want to learn programming, but GitHub issues are not the place to ask your questions. StackOverflow.com would be a better fit for those.
You're doing yourself a disservice by spamming random GitHub projects with your questions. All you'll get is being blocked/banned from repositories, possibly even from GitHub as a whole.

Okh sir , i am sorry i didn't know about it


add crp4 services

For reference to CRP4 test: https://indico.fnal.gov/event/64497/contributions/290688/attachments/177546/241768/240503_CRP45_reconstruction.pdf


Add telemetry to track user viewport

Background
Getting a better idea of user viewport sizes has long been a request of the design team, so they know the ideal viewport to design for. We should be able to track this metric in Azure App Insights.
Action requested
Add telemetry to track user viewport size.
We expect there to be a difference in viewport sizes between reporting users and patients (patients are more likely to use the app on mobile, since they're texted results) so if possible, we would like to be able to correlate viewport size with the particular page a user is viewing. (Whether this is done as part of the initial metric collection or in a later dashboard will depend on the Azure telemetry library's ability to track viewport.)
Acceptance Criteria
Viewport data is available in Azure App Insights.
Additional context
One of the action items out of the 1/25/23 analytics sync.

A summary of this data is available here


Remove bringup from tests and move some back to presubmit. Reorganize TESTOWNERS.

We renamed a few tests and therefore had to run them in bringup first (https://github.com/flutter/flutter/pull/136463). This removes bringup and moves some of them back to presubmit. Also, reorganize TESTOWNERS since they're running on hostonly now.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Each test has passed in bringup at least twice. Most of them have passed a bunch of times, except Mac_arm64 run_release_test_macos has only run twice and I manually triggered at least one time - I filed an issue about that (https://github.com/flutter/flutter/issues/136499).


[Excursion Funnel] Items caught in excursion funnels will travel for a short distance, but then get teleported to the base of the funnel

Throwing an item into an excursion funnel will cause it to travel along the path as expected for a few seconds, but then suddenly teleport to the base of the funnel and sometimes to the ground below the base.  This happens repeatedly for upwards facing funnels, while with sideways and downwards funnels the item will teleport to the start of the funnel and just fall out of it/get stuck on the ground

Fixed in the rewrite


Injecting data to sandbox using API

Can data be injected into the sandbox via an API, or is the dashboard the only method for doing so?

This can be done via API, see https://plaid.com/docs/sandbox/user-custom/#configuring-the-custom-user-account
"Custom user accounts can be configured and accessed in two ways. The easiest (and recommended) method is by using the Sandbox Users tool, located in the Plaid Dashboard under Developers -> Sandbox. Set the username and configuration object in the Dashboard, then go through the Link flow on Sandbox with that username and any non-empty password. You can also use /sandbox/public_token/create with options.override_username and options.override_password to create a public token for a custom user account while bypassing Link. Alternatively, you can log into Sandbox with the username user_custom and provide the configuration object as the password."
Note that some products are not supported by /sandbox/public_token/create; for those products you won't be able to inject the data via API.


Update Composer dependencies (2019-12-11-00-11)

Visual regression test passed!
View the visual regression test report