NistBib must fetch / provide all content from the page

For example, NISTIR 8200 (the example in the README) is located here:
https://csrc.nist.gov/publications/detail/nistir/8200/final

However, the fetched version doesn't contain authors or editors:
(
Author(s)
Interagency International Cybersecurity Standardization Working Group (IICS WG)
Editor(s)
Michael Hogan (NIST), Ben Piccarreta (NIST)
)
Published date: should be "November 2018"
URI (DOI): should be https://doi.org/10.6028/NIST.IR.8200
URI (PDF): should be https://nvlpubs.nist.gov/nistpubs/ir/2018/NIST.IR.8200.pdf
(There is no URI (OBP).)
Series: should be "NISTIR" (ping @opoudjis what is the correct way to represent this series?)
<bibitem type="" id="NISTIR8200(DRAFT)">
  <fetched>2019-04-04</fetched>
  <title format="text/plain" language="en" script="Latn">Interagency Report on Status of International Cybersecurity Standardization for the Internet of Things (IoT)</title>
  <uri type="src">https://csrc.nist.gov/publications/detail/nistir/8200/draft</uri>
  <uri type="obp">/CSRC/media/Publications/nistir/8200/draft/documents/nistir8200-draft.pdf</uri>
  <docidentifier type="NIST">NISTIR 8200 (DRAFT)</docidentifier>
  <date type="published">
    <on>2018</on>
  </date>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>National Institute of Standards and Technology</name>
      <abbreviation>NIST</abbreviation>
      <uri>www.nist.gov</uri>
    </organization>
  </contributor>
  <language>en</language>
  <script>Latn</script>
  <abstract format="plain" language="en" script="Latn">The Interagency International Cybersecurity Standardization Working Group (IICS WG) was established in December 2015 by the National Security Council’s Cyber Interagency Policy Committee (NSC Cyber IPC). Its purpose is to coordinate on major issues in international cybersecurity standardization and thereby enhance U.S. federal agency participation in international cybersecurity standardization.Effective U.S. government participation involves coordinating across the U.S. government and working with the U.S. private sector. There is a much greater reliance in the U.S. on the private sector for standards development than in many other countries. Companies and industry groups, academic institutions, professional societies, consumer groups, and other interested parties are major contributors. Further, the many Standards Developing Organizations (SDOs) who provide the infrastructure for the standards development are overwhelmingly private sector organizations.On April 25, 2017, the IICS WG established an Internet of Things (IoT) Task Group to determine the current state of international cybersecurity standards development for IoT. This Report is intended for use by the IICS WG member agencies to assist them in their standards planning and to help to coordinate U.S. government participation in international cybersecurity standardization for IoT. Other organizations may also find this useful in their planning.</abstract>
  <status>
    <stage>95</stage>
    <substage>99</substage>
  </status>
  <copyright>
    <from>2018</from>
    <owner>
      <organization>
        <name>National Institute of Standards and Technology</name>
        <abbreviation>NIST</abbreviation>
        <uri>www.nist.gov</uri>
      </organization>
    </owner>
  </copyright>
</bibitem>

@opoudjis should keywords exist here?

@ronaldtse Authors and Editors are contributors, right? They can be a person or an organization. Are Authors always organizations and Editors persons?

“Author” and “editor” are roles that apply to a contributor. A contributor can be an individual or an organization.

Let me find more examples for you.

@ronaldtse I understand that contributor can be an individuals or an organization. My question is how to distinguish is the contributor individuals or organization?
For example, we have the author "Interagency International Cybersecurity Standardization Working Group (IICS WG)". As a human, I understand it is an organization. But how to make a scrapper distinguish it?

@andrew2net excellent question.
The ones with persons read like this:
Ron Ross (NIST), Kelley Dempsey (NIST), Victoria Pillitteri (NIST)
=> {firstname} {middle-name?} {lastname} ({organization})

The ones that are non-persons are like this:

I think we can assume (for now) that:

Personal names must have (...) to indicate affiliation. If no affiliation, it would be an organization.
The keywords "task", "force", "group" in the name will indicate it is a group, not a person.

@ronaldtse

Published date: should be "November 2018"
the gem scrape date with month but BibliographicItem#to_xml format published date as a year. Should we change this behavior in `iso_bib_item' gem?

Yes, I think this behavior should be change to accept any kind of date. For example, DIN and NIST use "month+year" for edition. ISO uses "year".
The "BibliographicItem" class should be flexible to accept this, but "IsoBibliographicItem" should accept what ISO accepts.

suggest change it when we will extract BibliographicItem from iso-bib-item

Series: should be "NISTIR" (ping @opoudjis what is the correct way to represent this series?)

Series in the bibliographic record must be spelled out with full titles, and the abbreviation should also be provided. The mapping is given in https://github.com/metanorma/metanorma-nist/blob/master/lib/asciidoctor/nist/front.rb. Note that the tables map the user-entered abbreviation from asciidoctor to the Full Title, and to the Series Abbreviation. The former goes into <series><title>, the latter into <series><abbreviation>
      SERIES = {
        "nist-ams": "NIST Advanced Manufacturing Series",
        "building-science": "NIST Building Science Series",
        "nist-fips": "NIST Federal Information Processing Standards",
        "nist-gcr": "NIST Grant/Contract Reports",
        "nist-hb": "NIST Handbook",
        "itl-bulletin": "ITL Bulletin",
        "jpcrd": "Journal of Physical and Chemical Reference Data",
        "nist-jres": "NIST Journal of Research",
        "letter-circular": "NIST Letter Circular",
        "nist-monograph": "NIST Monograph",
        "nist-ncstar": "NIST National Construction Safety Team Act Reports",
        "nist-nsrds": "NIST National Standard Reference Data Series",
        "nistir": "NIST Interagency/Internal Report",
        "product-standards": "NIST Product Standards",
        "nist-sp": "NIST Special Publication",
        "nist-tn": "NIST Technical Note",
        "other": "NIST Other",
        "csrc-white-paper": "CSRC White Paper",
        "csrc-book": "CSRC Book",
        "csrc-use-case": "CSRC Use Case",
        "csrc-building-block": "CSRC Building Block",
      }.freeze

      SERIES_ABBR = {
        "nist-ams": "NIST AMS",
        "building-science": "NIST Building Science Series",
        "nist-fips": "NIST FIPS",
        "nist-gcr": "NISTGCR",
        "nist-hb": "NIST HB",
        "itl-bulletin": "ITL Bulletin",
        "jpcrd": "JPCRD",
        "nist-jres": "NIST JRES",
        "letter-circular": "NIST Letter Circular",
        "nist-monograph": "NIST MN",
        "nist-ncstar": "NIST NCSTAR",
        "nist-nsrds": "NIST NSRDS",
        "nistir": "NISTIR",
        "product-standards": "NIST Product Standards",
        "nist-sp": "NIST SP",
        "nist-tn": "NIST TN",
        "other": "NIST Other",
        "csrc-white-paper": "CSRC White Paper",
        "csrc-book": "CSRC Book",
        "csrc-use-case": "CSRC Use Case",
        "csrc-building-block": "CSRC Building Block",
      }.freeze

@opoudjis should keywords exist here?

Yes. If they are available to populate, you might as well populate them, though I don't foresee them being used.

Yes, I think this behavior should be change to accept any kind of date. For example, DIN and NIST use "month+year" for edition. ISO uses "year".

There's a wrinkle here: year-month dates are legal under ISO, but not under xs:date. Nonetheless, year-month is the correct way to represent such dates, e.g. 2019-04. There is a ticket https://github.com/metanorma/isodoc/issues/90 for me to confirm that such dates do not blow up anything in Metanorma; and if NIST STOPPED DELUGING ME WITH TICKETS, I could actually investigate it.
Use them anyway. If it blows Metanorma up, all the better. :-/

@ronaldtse could you tell me where to find series on https://csrc.nist.gov/publications/detail/nistir/8200/final

@andrew2net "NISTIR" is the name of the series.
In the "NISTIR 8200" publication, there were two documents:

a "state: final" document ("NISTIR 8200 (11/29/18)")
a "state: public-draft" document ("Draft NISTIR 8200 (2/14/18)")

@andrew2net In general, the series abbreviation (in the list I pasted above) is the prefix of the document identifier.

@ronaldtse could you tell me what are security, keyword, and commentperiod? Where can we scrape it?

commentperiod is the period during which public comment can be received on a current draft. It is relevant to bibdata (the details of the current document); it is irrelevant to bibitem (the document being cited), so you can ignore it.
keywords are not going to be included in any citation. There is a bit more of an argument for including them in retrieved bibliographies as databases, so people can search on them; but if you can't find it easily, ignore it.
security is a holdover from another spec (rsd?), and shouldn't be there at all.

@andrew2net I've labeled this screenshot for your reference (https://csrc.nist.gov/publications/detail/sp/800-162/final)

P.S. Not sure where security is from. Where did you see it?

NistBib is not only for Metanorma, but it should retrieve all information related to this bibliographic item. Hence it is supposed to return bibdata (with as much information as possible), not just enough information for rendering citations.

Hence it is supposed to return bibdata (with as much information as possible), not just enough information for rendering citations.

This is scope creep (YET AGAIN), and it means that the schemas that relaton uses are going to have to be flavour-specific after all.

This is not scope creep — nistbib was always supposed to return NIST bibliographic data.

PS its not technically part of metanorma...


WarpReverseScan Exclusive Scan Bug

I think there's a bug with WarpReverseScan Exclusive Scan. If passing a logic warp of 16 threads, then thread 15 will still not be 0, when it should. I think just doing the following will work, but I haven't thought about this problem too much and how it will affect other classes.
    /// Exclusive scan
    // Get exclusive from inclusive
    template <typename ScanOpT>
    __device__ __forceinline__ void ExclusiveReverseScan(
        T              input,              ///< [in] Calling thread's input item.
        T              &exclusive_output,  ///< [out] Calling thread's output item.  May be aliased with \p input.
        ScanOpT        scan_op,            ///< [in] Binary scan operator
        T              &warp_aggregate)    ///< [out] Warp-wide aggregate reduction of input items.
    {
        T inclusive_output;
        InclusiveReverseScan(input, inclusive_output, scan_op);
        exclusive_output = inclusive_output - input;
        // warp_aggregate = cub::ShuffleIndex<LOGICAL_WARP_THREADS>(inclusive_output, 0, member_mask);
        // // initial value unknown
        // exclusive_output = cub::ShuffleDown<LOGICAL_WARP_THREADS>(
        //     inclusive_output, 1, LOGICAL_WARP_THREADS - 1, member_mask
        // );
    }

    /**
     * \brief Computes both inclusive and exclusive reverse scans using the specified binary scan functor across the calling warp.  Because no initial value is supplied, the \p exclusive_output computed for the last warp-lane is undefined.
     */
    template <typename ScanOpT>
    __device__ __forceinline__ void ReverseScan(
        T               input,              ///< [in] Calling thread's input item.
        T               &inclusive_output,  ///< [out] Calling thread's inclusive-scan output item.
        T               &exclusive_output,  ///< [out] Calling thread's exclusive-scan output item.
        ScanOpT         scan_op)            ///< [in] Binary scan operator
    {
        InclusiveReverseScan(input, inclusive_output, scan_op);
        // initial value unknown
        exclusive_output = inclusive_output - input;
        // exclusive_output = cub::ShuffleDown<LOGICAL_WARP_THREADS>(
        //     inclusive_output, 1, LOGICAL_WARP_THREADS - 1, member_mask
        // );
    }

};

I don't know how this affects BlockReverseScan, however, as I'm trying to do a WarpPostfixScan this seemed to fix my issue. I will take a look at ExclusiveReverseScan for BlockReverseScan.

I created a basic example, and it seems not to affect InclusiveScan. There is no API for BlockExclusiveScan, however, if you add something like this.
    template <
        int             ITEMS_PER_THREAD,
        typename        ScanOp,
        typename        BlockPostfixCallbackOp>
    __device__ __forceinline__ void ExclusiveReverseScan(
        T                       (&input)[ITEMS_PER_THREAD],     ///< [in] Calling thread's input items
        T                       (&output)[ITEMS_PER_THREAD],    ///< [out] Calling thread's output items (may be aliased to \p input)
        ScanOp                  scan_op,                        ///< [in] Binary scan functor
        BlockPostfixCallbackOp   &block_postfix_callback_op)    ///< [in-out] [warp0 only] Call-back functor for specifying a block-wide postfix to be applied to the logical input sequence.
    {
        // Reduce consecutive thread items in registers
        T thread_postfix = ThreadReverseReduce(input, scan_op);
        // Exclusive thread block-scan
        ExclusiveReverseScan(thread_postfix, thread_postfix, scan_op, block_postfix_callback_op);
        // Exclusive scan in registers with postfix as seed
        ThreadReverseScanExclusive(input, output, scan_op, thread_postfix);
    }

Then either option still works, which makes me think that thread_partial happens to cover up this issue. Nonetheless, using WarpReverseScan and ExclusiveReverseScan doesn't work if running parallel WarpWide scans.

Ahh looking more into the cub implementation, this is a design choice. I am going to close this issue as it doesn't affect anything. Caused me such a headache when I switched over from int to float for scans, as internally cub will assume 0 for int scans and unknown for float scans. For anyone interested I'll drop the following.
    template <typename ScanOpT, typename IsIntegerT>
    __device__ __forceinline__ void Update(
        T                       /*input*/,          ///< [in]
        T                       &inclusive,         ///< [in, out]
        T                       &exclusive,         ///< [out]
        ScanOpT                 /*scan_op*/,        ///< [in]
        IsIntegerT              /*is_integer*/)     ///< [in]
    {
        // initial value unknown
        exclusive = ShuffleUp<LOGICAL_WARP_THREADS>(inclusive, 1, 0, member_mask);
    }

    /// Update inclusive and exclusive using input and inclusive (specialized for summation of integer types)
    __device__ __forceinline__ void Update(
        T                       input,
        T                       &inclusive,
        T                       &exclusive,
        cub::Sum                /*scan_op*/,
        Int2Type<true>          /*is_integer*/)
    {
        // initial value presumed 0
        exclusive = inclusive - input;
    }


Hourly, semi-hourly tracking

Hi,
It could be a good idea to make it possible to change the feeling every 30-60 mins, because the feeling can change more frequently than every day.

Hey @GEkuL, I'm currently working on a couple of features I've just added to the roadmap on the readme. One of them is support for multiple moods per day.
My struggle at the moment is designing a UX that keeps the interface really simple as this was my primary goal for this app. My current idea is to have the moods for the day show in a horizontally scrolling list below the input like in the design below. What do you think?

@CampbellMG honestly, didn't get the idea fully. Is it possible to revert a missclick?
Is it possible change the mood at any time?
I think it's a good idea that the first row is to set up the mood. And the second one should be showing your mood changed at different time with the option to delete/revert in case of missclick. I believe that the second raw should be able to be hidden or popped up.
Generally I like your design, yet I believe that the second raw should be hidden by default.

This is a much needed feature for me. It would be great if we could edit or remove a past entry. It would also be useful to be able to add a past entry (custom date and time).
I think the design is fine, but it might help if there was a clearer separation between the input row and the history. I don't agree that they should be hidden by default.

@GEkuL You've raised a couple of good points. I'll spend a bit of time reworking this design to take that into account. You can't actually undo a mood entry at the moment, just change it to something else. That would definitely become important if we made this change.
@laurentlbm I'm not sure if this is what you mean but you can add or edit past entries in the existing app. You just select a date from the calendar or date dropdown and select the mood. This might change a bit if we implement this new design.

@CampbellMG actually I think. If you can change the mood for the previous one, it actually means removing the missclick :)

@CampbellMG That's what I meant, but with the ability to specify the time (once this issue is implemented).


Is it possible to send data from browser to node using broadcast-hub ?

Nope, it's pure broadcast. If you need bidirectional communication, I strongly recommend looking into something like real socket.io.

Ok,Thanks


[Question] Using fragments - location doesn't contain hash

I have two links, one created with <Link to='/faq' hash='#whatis'> and the other one created with  that look as following when inspecting element on rendered document:
<a class="" href="/faq#whatis" data-reactid=".<IP_ADDRESS>.0.1.0">...
<a href="/faq#whereq" data-reactid=".<IP_ADDRESS>.0.2.0">...

When I click on the second one, hash is populated in the location object and I'm being taken to the fragment. When I click on the first one, I'm being taken to \faq, hash is not populated in the location object and I'm not being taken to the fragment. Any idea why is that?

Think it's more of a react-router question so moving it there.


Update README_BoundingBox.md

Overview
Currently, Bounding Box does not calculate the box collider boundary if the user didn't explicitly assign a collider. (feedback from Yoyo #3871 ). Updating documentation.

/azp run mrtk_docs


in dual stack environment, support only ipv4 or ipv6 address for SpiderSubnet

What would you like to be added?
In dual stack, support only ipv4 or ipv6 address for SpiderSubnet mode
Reference: https://github.com/spidernet-io/spiderpool/pull/1939
Why is this needed?
No response
How to implement it (if possible)?
No response
Additional context
No response

https://github.com/spidernet-io/spiderpool/pull/2821


GitLens requires a newer version of Git

GitLens requires a newer version of Git (>= 2.7.2) than is currently installed (v12.0.0). Please install a more recent version of Git.

I have the latest version of Github desktop (2.2.2), however GitLens still requests a newer one.
VS Code:
Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

@ensignn GitLens requires a newer version of Git, not GitHub Desktop. But from that message something seems very strange -- as it says you have v12.0.0 of Git, which AFAIK doesn't exist.
Please enable output channel logging by setting "gitlens.outputLevel": "debug" in your settings. This will enable logging to the GitLens channel in the Output pane. Once enabled, please reproduce the issue and attach the log from the GitLens channel.

Analysis:
I had a similar issue on my Mac portable. In my case the error was:

Gitlens requires a newer version of Git (>=2.7.2) than is currently installed (2.6.4 (Apple Git-63)). Please install a more recent version of Git.

Typing git --version the terminal responded with:

git version 2.23.0

That version was installed from https://git-scm.com/.
Typing which git showed me the path to that version of Git. In my case it was located at:

/usr/local/bin/git

Solution:
To fix the issue with Gitlens, open the settings in Visual Studio Code:

press Command+Shift+P
type the word settings
select Preferences: Open Settings (JSON).

Add the following lines to this file and save:
    "git.enabled": true,
    "git.path": "/usr/local/bin/git"

(NOTE: of-course replace the git.path value with whatever value you got back in the terminal if it's different from what I have.)

I'm running into this issue as well.
It seems that GitLens for whatever reason is ignoring the git.path setting, as well as ignoring the path environment variable.

The screenshot shows that my Git versions is <IP_ADDRESS> (at that path), and doing a git --version so it reads from the (Windows) environment variable reads it fine. I've also added that path to the VSC settings.
Since the screenshot was taken, and reading this thread, I also tried @sjee 's suggestion, and added "git.enabled": true, to the settings, as well as doing a which git which showed me /cmd/git; still get the same message every time I restart VSC....
So then I added to the settings "gitlens.outputLevel": "debug" and it shows this:

[2019-11-13 15:34:52:280] [1] GitService.initialize
[2019-11-13 15:34:52:280] [2] GitService.getBuiltInGitApi
[2019-11-13 15:34:52:535] [2] GitService.getBuiltInGitApi completed • 254 ms
[2019-11-13 15:34:52:843] Git found: 2.7.1.windows.2 @ C:\Program Files\Git\cmd\git.exe • 307 ms
[2019-11-13 15:34:52:843] [1] GitService.initialize completed • 562 ms
[2019-11-13 15:34:52:844] Starting repository search in 0 folders
[2019-11-13 15:34:52:845] [3] GitUri.fromUri — e=Uri(vscode-userdata:/c:/Users/kacey/AppData/Roaming/Code/User/settings.json)
[2019-11-13 15:34:52:845] [4] LineAnnotationController.resume
[2019-11-13 15:34:52:846] [4] LineAnnotationController.resume completed • 0 ms
[2019-11-13 15:34:52:846] [5] LineAnnotationController.refresh
[2019-11-13 15:34:52:846] [6] LineAnnotationController.clear
[2019-11-13 15:34:52:846] [6] LineAnnotationController.clear completed • 0 ms
[2019-11-13 15:34:52:855] ShowMessage(error, 'GitLens requires a newer version of Git (>= 2.7.2) than is currently installed (2.7.1.windows.2). Please install a more recent version of Git.', suppressGitVersionWarning, [object Object])
[2019-11-13 15:34:52:857] GitLens (v10.1.2) activated • 913 ms
[2019-11-13 15:34:52:857] [3] GitUri.fromUri returned GitUri(vscode-userdata:/c:/Users/kacey/AppData/Roaming/Code/User/settings.json) • 12 ms
[2019-11-13 15:34:52:857] [7] GitService.getRepository — e=GitUri(vscode-userdata:/c:/Users/kacey/AppData/Roaming/Code/User/settings.json)
[2019-11-13 15:34:52:858] [5] LineAnnotationController.refresh completed • Skipped because there is no valid editor or no valid lines • 11 ms
[2019-11-13 15:34:52:859] [8] LineAnnotationController.onActiveLinesChanged — e=editor=vscode-userdata:/c:/Users/kacey/AppData/Roaming/Code/User/settings.json, lines=undefined, pending=true, reason=editor
[2019-11-13 15:34:52:860] [9] LineAnnotationController.clear
[2019-11-13 15:34:52:860] [9] LineAnnotationController.clear completed • 0 ms
[2019-11-13 15:34:52:860] [8] LineAnnotationController.onActiveLinesChanged completed • 0 ms
[2019-11-13 15:34:53:098] [7] GitService.getRepository returned undefined • 240 ms
[2019-11-13 15:34:53:099] [a] GitService.isTracked returned false • 0 ms — e=GitUri(vscode-userdata:/c:/Users/kacey/AppData/Roaming/Code/User/settings.json)
[2019-11-13 15:34:53:111] [b] LineAnnotationController.onActiveLinesChanged — e=editor=vscode-userdata:/c:/Users/kacey/AppData/Roaming/Code/User/settings.json, lines=undefined, pending=false, reason=editor
[2019-11-13 15:34:53:111] [c] LineAnnotationController.clear
[2019-11-13 15:34:53:111] [c] LineAnnotationController.clear completed • 0 ms
[2019-11-13 15:34:53:111] [b] LineAnnotationController.onActiveLinesChanged completed • 0 ms
[2019-11-13 15:36:23:507] [d] LineAnnotationController.onActiveLinesChanged — e=editor=undefined, lines=undefined, pending=false, reason=editor
[2019-11-13 15:36:23:507] [e] LineAnnotationController.clear
[2019-11-13 15:36:23:507] [e] LineAnnotationController.clear completed • 0 ms
[2019-11-13 15:36:23:507] [d] LineAnnotationController.onActiveLinesChanged completed • 0 ms
[2019-11-13 15:36:26:018] ShowMessage(error, 'GitLens requires a newer version of Git (>= 2.7.2) than is currently installed (2.7.1.windows.2). Please install a more recent version of Git.', suppressGitVersionWarning, [object Object]) returned undefined

As you can see, it's still trying to read from C:\Program Files\Git\cmd\git.exe and I have no idea why since the VSC settings specifically state to use a different one, as well as does the environment variable?
I do realize I could move my git installation to that C:\Program Files\Git folder, but that seems like just a workaround to a bug, and I also want to keep my Git where it's at.

Update:
I uninstalled the version of Git For Windows that was in C:\Program Files\Git\ and now it reads from the settings file properly. Very strange?


Input workflow

Adds samplesheet for sample input. Closes #1 .
PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/seqinspector branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nf-test test main.nf.test -profile test,docker).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

So should we aim to fix the tests in this PR or should we make that it's own PR? @mahesh-panchal

Merge in a working testing dataset to main/dev and then rebase this on top. The tests should then work I think.

Or just push to this branch. I think you should all be able to.


Speed up local action execution

this patch significantly speeds up local action execution (both,
direct and non-direct) by avoiding to construct a (remote) promise
but instead directly scheduling the function bound to the action
as a local thread, while using a simple (local-only) future.
direct actions are executed by directly invoking the function bound to
the function

@sithhell Your comment shave been addressed.


Application wide profiling

As the application grows so is the number of components that create regl commands and relaying on regl.stats and reglCommand.stats is not enough. Some issues:

Currently there is no way to get list of all regl commands, not even their count. Regl commands are one of the most expensive resources especially on init due to code compilation and reducing their number is critical. That would also allow me to iterate over stats of all commands in one place.
List of all buffers, textures etc. could be useful for debugging
Execution time measurement of update calls e.g. texture.subimage can take significant time of run every frame. Any ideas how to handle that? Currently I rely on wrapping update code with console.time/timeEnd and regl._gl.finish()

This is connected to Debugging helper tools

This makes sense and internally regl tracks all this info anyway.  Exposing it would be an easy win.
Do you want to take a shot at this?

Yes, i'll have more time next week and probably start with exposing total counts.
There is also a question of how much of that should be in core? Below is a screenshot of what hopefully will become regl-profiler similar to PerfMeter. It currently depends on wrapping regl.frame, regl.texture, gl.useProgram, gl.drawArrays etc. I had to drill down to gl.* calls as one regl resource can create multiple dependent resources (eg. FBO creates dept buffer by default). Again, total counts currently used for resource ids would help.

Sections from the top:

FPS counter (estimated from 1000ms / frame duration). Always aim for 60fps, yeah right..
Manual labeled timers profiler.time(label), profiler.timeEnd(label) currently using performance.now() and gl.finish(), I should switch to disjoint queries as gl.finish approach doesn't work in Chrome. Used for bigger app subsystems / pipelines.
Active (from regl.stats) vs total resource count. Used to catch errors where I was e.g. creating elements buffer every frame or lot's of temp textures in a dynamic uniform
Primitives count. Used for scene complexity estimation.
Core gl call count per frame. Used to better understand how to nest regl commands (e.g. for shared uniforms) and organise batching.
Command stats (cpu vs gpu time). Currently added manually.

API:
const regl = require('regl')({ profile: true })
const profiler = require('regl-profiler')(regl)

const drawMesh = regl({ .... })

// start measuring CPU and GPU timings for the  given command
profiler.addCommand('drawMesh', drawMesh)

// measure some timespan
profiler.time('init')
...
profiler.timeEnd('init')

// whole frame call back will be measured automatically
regl.frame(() => {
   // draw will attach fixed canvas element in the top right corner and draw stats
   profiler.draw()
})

List of all buffers, textures etc. could be useful for debugging

You can get this and more with the excellent WebGL Inspector extension.

@dcposch I was big fan of WebGL inspector but there is number of issues:

doesn't work in Safari
once enabled it breaks extensions e.g. Float Textures, so it's not usable in any real world app
it's not realtime, i need to capture frame to inspect it
doesn't help with regl related bugs in my app like creating unnecessary buffers every frame

As of late, I have found  Spector.js to be incredibly helpful. It is available as a standalone module you can integrate into your project and also has browser extensions.


Tests are failing

OS: Arch Linux
Bash version: 5.0.7 and 4.4.23 both
Yarn version: 1.16.0
yarn-completion version: 0.14.0
Tests are failing with the following output.
======================================================================
Environment checks
======================================================================
  should match yarn version line in src file........................OK
======================================================================
Checking top-level commands
======================================================================
  should have matching commands.....................................OK
  should have matching global options...............................OK
======================================================================
Checking top-level command options
======================================================================
  [access] should have matching options.............................OK
  [add] should have matching options................................OK
  [audit] should have matching options..........................FAILED
  | ERROR (audit): mismatched options found
  |
  | --groups
  | --level
  [autoclean] should have matching options..........................OK
  [bin] should have matching options................................OK
  [cache] should have matching options..............................OK
  [check] should have matching options..............................OK
  [config] should have matching options.............................OK
  [create] should have matching options.............................OK
  [exec] should have matching options...............................OK
  [generate-lock-entry] should have matching options................OK
  [global] should have matching options.............................OK
  [help] should have matching options...............................OK
  [import] should have matching options.............................OK
  [info] should have matching options...............................OK
  [init] should have matching options...............................OK
  [install] should have matching options............................OK
  [licenses] should have matching options...........................OK
  [link] should have matching options...............................OK
  [list] should have matching options...............................OK
  [login] should have matching options..............................OK
  [logout] should have matching options.............................OK
  [node] should have matching options...............................OK
  [outdated] should have matching options...........................OK
  [owner] should have matching options..............................OK
  [pack] should have matching options...............................OK
  [policies] should have matching options...........................OK
  [publish] should have matching options............................OK
  [remove] should have matching options.............................OK
  [run] should have matching options................................OK
  [tag] should have matching options................................OK
  [team] should have matching options...............................OK
  [unlink] should have matching options.............................OK
  [unplug] should have matching options.............................OK
  [upgrade] should have matching options............................OK
  [upgrade-interactive] should have matching options................OK
  [version] should have matching options............................OK
  [versions] should have matching options...........................OK
  [why] should have matching options................................OK
  [workspace] should have matching options..........................OK
  [workspaces] should have matching options.........................OK

There were 1 failures.

Not able to reproduce this. It's also building fine in CI, so that makes me wonder if it's a machine issue on your end?

In CI, I couldn't see builds with new version (0.14.0).

Are you having a specific issue related to the failure in the build that you pasted or you just letting me know that the build failed?

I am just letting you know.


WebSocket Failure !!!!!!!!

Hi @aphelionz  and orbit team,
There was failure in Websocket.


Encoded user/password in URL should be accepted

Redis version
7.2.5-alpine
Redisson version
3.21.3
Redisson configuration
singleServerConfig:
    address: "redis://default:myP%40ss@redis:6379"

What is the Expected behavior?
encoded URL should be accepted
What is the Actual behavior?
it use encoded password as actual password
Additional information
https://github.com/redisson/redisson/blob/15a14c8e657ff806f7119fd9dc1153c982c92c2d/redisson/src/main/java/org/redisson/misc/RedisURI.java#L59-L67

Which encoding did you apply to the password?

Fixed. Thanks for report


docs: One button to toggle the theme instead of 2 radiobuttons

Is your feature request related to a problem? Please describe.
On my first visit to the docs site I start clicking around the page to test and explore, as I always do. I noticed that the theme toggle is not really a toggle in the sense that you can click the same element twice and have it... toggle.
Subconsciously, because there are only 2 options, I did expect this behavior:

Visit the page, it starts in dark mode due to my preferences
Click the sun icon, it switches to light mode
Click the sun icon again, expecting it to switch back to dark mode
Click the moon icon to get my desired action

Describe the solution you'd like to see
Ideally the theme should toggle regardless of where you click within both label element's parent div.
Like NextAuth does for example:

Describe alternate solutions
Instead of a single button like the example above, keep it as is but have the theme toggle between dark and light regardless whether you click on the sun or the moon.
Additional information
I'm willing to do this! This would be my first time contributing to an open source project then.

I like keeping both icons / the current styling, but I think the entire thing could be the click target instead of just one icon.

I like keeping both icons / the current styling, but I think the entire thing could be the click target instead of just one icon.

Agree, feel free to make a PR for this @muradbuyukasik


f2fs support

f2fs supports the same ioctl() for encryption as ext4, so please add support for this filesystem too. Actual code change is simple:
EXT4_KEY_DESC_PREFIX should be changed from "ext4:" to "f2fs:"
But you also need some user interface change to allow select filesystem.

Actually, there is a lack of info about enabling f2fs encryption and I have the same request, if possible.
Everything that I was able to find is http://www.phoronix.com/scan.php?page=news_item&px=F2FS-Encryption-Linux-4.2

Based on the native encryption support added to EXT4 with the Linux 4.1 kernel, Linux 4.2 is bringing encryption support to the F2FS file-system.
F2FS has been working on native encryption support in tandem with the EXT4 work and now it's been called for merging today into Linux 4.2. Jaegeuk Kim sent in the F2FS feature update for Linux 4.2 and it features per-file encryption support along with new capabilities for FALLOC_FL_ZERO_RANGE (converting a range of file to zeroes), FALLOC_FL_COLLAPSE_RANGE (removes a byte range from a file), and RENAME_WHITEOUT.
The Flash-Friendly File-System for Linux 4.2 also has recovery for broken super-blocks, TRIM improvements, and various fixes.

And no info or article, how could I use it.

It should be quite simple to implement, this is e-mail reply from f2fs kernel maintainer on this issue:
Date: Sun, 24 Jan 2016 17:26:46 -0800
Hi,
Yup, you can use the same ioctl.
But, one thing you need to change should be:
EXT4_KEY_DESC_PREFIX "ext4:"  -->  "f2fs:"
Thanks,
2016-01-24 3:44 GMT-08:00 Andrew Savchenko<EMAIL_ADDRESS>
Hello,
thank you for adding encryption support for f2fs. Is there any
userspace tool (or any other way) to use it? As far as I undestand,
f2fs implements the same ioctl() as ext4, so maybe ext4-crypt [1]
tool can be used of f2fs as well?
[1] https://github.com/gdelugre/ext4-crypt


Pass query as a property to renderSuggestionsContainer

In my application, when user is presented with suggestions, I'd like to display their query at the bottom of the suggestions container.
It doesn't appear that renderSuggestionsContainer is passed the user's search query.

Actually just uncovered the query as children.props.renderItemData.query.
Do you think it's worth passing the query in a higher-order fashion?
Is children.props.renderItemData considered internal/private?

children.props.renderItemData is definitely considered "private", and I don't recommend using it.
Can I ask what exactly are you trying to achieve by showing the query at the bottom? Isn't it clear to users that the displayed suggestions are based on their input? Feel free to add a picture if it helps to explain the reasoning behind this. Before we extend the API, I'd like to make sure that it makes sense from user experience point of view.

I'm working with a form that allows users to submit a question for consideration of being published on the site as an (later answered) Q&A.
As the user types their question, previously-answered/published Q&As are suggested to them, to encourage users to read content that may already have their answer. Without selecting an existing Q&A, submission of the form redirects users to a full question submission form with their query prepopulated.
Going back a bit–at the bottom of the suggestions window, there is linked text like:
Search for: "{{ query }}"
Which is meant to encourage users to search the site using their query; when clicked, the link takes the user to a search page based on their query.

Here's a preview:

Thanks @joshlevinson, it makes perfect sense now!
Thinking about how to extend the API, I feel like just passing query like this:
function renderSuggestionsContainer({ children, query, ...rest })

is probably not a good idea, because those users who don't care about query would still need to destructure it, or otherwise React would complain with something like:

Unknown prop query on <div> tag. Remove this prop from the element.

The only reasonable solution I can think about is to introduce a breaking change:
function renderSuggestionsContainer({ children, query, containerProps })

What do you think?

I couldn't think of a way around the breaking change apart from the deprecation-inducing alternative 🙁

@joshlevinson PR is welcome ;)

In v9.0.0, you can get query in renderSuggestionsContainer.


Cannot support Nacos clustering

Currently, it only get first one Nacos server info from URL to ignore other Nacos servers. such as
nacos://<IP_ADDRESS>:8848?backup=<IP_ADDRESS>:8848,<IP_ADDRESS>:8848
For detail, please see my bug fixing with the following URL
https://github.com/michaelmao999/dubbo-admin/commit/4157fb6b1427557dc2a70a12e4f45a86aec34ce6

I'll check it later


improve whereami output when using with Cloud Run / Cloud Functions

include details like container instance ID and GSA used when running on serverless platform(s) on Google Cloud.
Pull from:
https://cloud.google.com/run/docs/container-contract#metadata-server

Less than ideal but there's a bit of an impedance mismatch when fetching Cloud Run fields since some of the default fields reference "pods" which aren't a thing in CR. {   "cloud_run_instance_id": "0071bb481567295e2eaa3092ab04038a51f7548492e17aa98788ca070921232c81b16bfbad2e14bc928527c8182bb211057c4f2988d01df42206a91b315260e0c9",   "cloud_run_service_account"<EMAIL_ADDRESS>  "host_header": "whereami-4uotx33u2a-uc.a.run.app",   "pod_name": "localhost",   "pod_name_emoji": "8⃣",   "project_id": "am-arg-01",   "timestamp": "2022-12-17T02:24:22",   "zone": "us-central1-1" }

Also the zone field isn't entirely accurate as CR is regional in nature; the -1 suffix is just a default the GCE metadata service applies.


Your Software On Microsoftware Store don't work properly!!

refund?

not my submission. someone claimed it as their own. i already am aware of this but i think there's nothing i can do about it. sorry

huh, seems it has already been taken down.

nigga you got scammed

tiganul got scammed

how much you pay tigane???


feat: add gas-comparison PR bot

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: Closes #163
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

Added changes to CHANGELOG.md

[x] Yes
[ ] No

Other information

@Eikix please approve


Fix SDK version 31 for android

Please fill the template to help you out. Also, please try the Example project compare before submiting the issue when you have certain issue with your project setup.

Version of react-native-audio-recorder-player
3.0.12
Version of React Native
0.64.0
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
Compiles successfully.
Actual behavior
Build Fails.With a message

The minCompileSdk (31) specified in a
dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
is greater than this module's compileSdkVersion (android-29).
Dependency: androidx.browser:browser:1.4.0-alpha01.
AAR metadata file: C:***********.gradle\caches\transforms-2\files-2.1\e032f7b3cd0a51e4352073c0f400ec41\browser-1.4.0-alpha01\META-INF\com\android\build\gradle\aar-metadata.properties.

Steps to reproduce the behavior
Set Target SDK version of the root project to lower than 31. Ex : 29
Run the project on android.
fix:
Replace
implementation "androidx.browser:browser:$androidXBrowser"
With
implementation "androidx.browser:browser:1.3.0"

I have that same problem.

Same problem @hyochan :(. Fixed with @DioSerdar 's solution (implementation "androidx.browser:browser:1.3.0"). Please release new version with that

Might be a good idea to add to your build.gradle(app) defaultConfig if the fix is not available at this moment.
defaultConfig {
    configurations.all {
                // temp fix until https://github.com/hyochan/react-native-audio-recorder-player/issues/388 is resolved
                resolutionStrategy { force 'androidx.browser:browser:1.3.0' }
    }
   ...
}

@robertqin86 Thanks !
I tried to upgrade build target to 31, then update AndroidManifest with android:exported="true", but at the end it fails with Error: Error not specified. when starting a record...
Your fix works !

Should be fixed in 3.2.0. Thanks for the report!

Hi @hyochan , so I updated to the 3.2.0 and I'm still getting this error.
Execution failed for task ':app:checkDebugAarMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
   > The minCompileSdk (31) specified in a
     dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
     is greater than this module's compileSdkVersion (android-30).
     Dependency: androidx.browser:browser:1.4.0-alpha01.
     AAR metadata file: /Users/qinzhengquan/.gradle/caches/transforms-2/files-2.1/ccd71311daac42bf61432e80dec2d0cc/browser-1.4.0-alpha01/META-INF/com/android/build/gradle/aar-metadata.properties.


UV compatibility mode

Self explanatory. Right now Collage bakes the x and y into width and height, amongst other things that GameMaker does not do. Additionally, I'd like to fetch the results from an array instead of only a struct.

Implemented already.


model variable vs base_model

Hello ypwhs,
On the ctc code you are creating a model called model:
model = Model(input=[input_tensor, labels, input_length, label_length], output=[loss_out])
And that is the one you train, but when you make the prediction you use a the model called base_model.
y_pred = base_model.predict(X_test)
Why is that? Is it correct?
Shouldn't you use model.predict? If yes, what would be a correct way to call it, since is waiting for 4 parameters, what should it be sent on "labels", "input_length" and "label_length".
Thank you.

@roccolocko Have you solved this problem?

Due to the limitations of keras, ctc loss must be built in the model, so in fact model is just a training model, base_model is the real model.

@ypwhs Thank you for project and your reply, Got it !


Add a counter of my website

Very nice work! I suppose I could use this instead of self-hosting, if you don't mind :).

Decided to self-host instead.


Fix LocalDnsHelper Batch handling

This should fix both #929 and #930

Coverage increased (+0.009%) to 85.628% when pulling 4643b1a18ef0b6be9fe7da1945271ee7624839b6 on aozarov:dns-alpha-batch into e63bc5315615dc1fbeee93654e1d0fb601b719cc on GoogleCloudPlatform:dns-alpha-batch.

Looks good to me!


Rework the arguments for the DBs

Tweak the ChainDB arguments:

Remove unused fields in CDB:

cdbTraceLedger this was always set to nullTracer, furthermore it would trace the whole LedgerDB.
cdbChunkInfo was never accessed from the ChainDB.
cdbCheckIntegrity was never accessed from the ChainDB.

Transform ChainDbArgs into an isomorphic product of the different arguments of the inner databases.
Define most common operations on ChainDbArgs as separate functions: ensureValidateAll, updateTracer and updateDiskPolicyArgs

Tweak the LgrDB arguments:

LgrDB.cfg and LgrDbArgs.lgrConfig are now LedgerDbCfg (ExtLedgerState blk) instead of TopLevelConfig blk.
defaultArgs no longer expects a filesystem.

Tweak the ImmutableDB arguments:

defaultArgs no longer expects a filesystem.

Tweak the VolatileDB arguments:

defaultArgs no longer expects a filesystem.

Hide the Identity/Defaults types in Ouroboros.Consensus.Util.Args in favor of Complete/Incomplete.
Expose noDefault to replace NoDefault.

I would argue that this also can close https://github.com/IntersectMBO/ouroboros-consensus/issues/630


Sintax hightlight is broken when use String interpolation

Looks like this is related to #31

Bad syntax highlighting when quote marks are used:
fun format(s: String) = s.replace('"', '_') // fails

Workaround:
fun format(s: String) = s.replace("\"", '_') // OK

Original issue was fixed with the release of #40. The quote mark issue still needs to be addressed. I'm not sure of the rules on this repository but it might be worth making a new issue page for the quote issue.


⚠ Fetchers has degraded performance

In 2bfcb26, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 265 ms

Resolved: Fetchers performance has improved in 7a08e51.


cinst -y commandovm.win10.config.fireeye -f "Access is denied"

commandovm.win10.config.fireeye is failing with an "Access is denied" error.

PS C:\WINDOWS\system32> cinst -y commandovm.win10.config.fireeye -f
Chocolatey v0.10.15
[Pending] Removing incomplete install for 'commandovm.win10.config.fireeye'
Installing the following packages:
commandovm.win10.config.fireeye
By installing you accept licenses for the packages.
commandovm.win10.config.fireeye v<IP_ADDRESS> (forced)
commandovm.win10.config.fireeye package files install completed. Performing other installation steps.
Access is denied
[+] Beginning host configuration...
[-] Disabling services
[+] Disabled OpenVPN Services
[+] Disabled Neo4j
[+] Disabled OpenSSH Service
[+] Cleaning up the Desktop
ERROR: Cannot bind argument to parameter 'Path' because it is null.
The install of commandovm.win10.config.fireeye was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1'.
See log for details.
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures

commandovm.win10.config.fireeye (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\choco

To Reproduce
Steps to reproduce the behavior:
I've run the install.ps1, a few items failed such as Docker due to "Enable hypervisor application..." not ticked for VMWare Fusion, re-running I've noticed this error "Access is denied" error.
Log
Write-Host "[!] Done with configuration, shutting down Boxstarter..." -ForegroundColor Green
2019-10-04 14:37:00,318 8044 [DEBUG] - Calling built-in PowerShell host with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters ''']
2019-10-04 14:37:00,318 8044 [DEBUG] - Redirecting System.Management.Automation.resources, Version=<IP_ADDRESS>, Culture=en-GB, PublicKeyToken=31bf3856ad364e35, requested by ''
2019-10-04 14:37:00,428 8044 [ERROR] - Access is denied
2019-10-04 14:37:00,490 8044 [DEBUG] - Host version is 5.1.18362.1, PowerShell Version is '5.1.18362.145' and CLR Version is '4.0.30319.42000'.
2019-10-04 14:37:00,615 8044 [INFO ] - VERBOSE: Exporting function 'Format-FileSize'.
…snip...
2019-10-04 14:37:00,928 8044 [DEBUG] - ---------------------------Script Execution---------------------------
2019-10-04 14:37:00,928 8044 [DEBUG] - Running 'ChocolateyScriptRunner' for commandovm.win10.config.fireeye v<IP_ADDRESS> with packageScript 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye', installArguments: '', packageParameters: '',
2019-10-04 14:37:00,928 8044 [DEBUG] - Running 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1'
2019-10-04 14:37:00,943 8044 [INFO ] - [+] Beginning host configuration...
2019-10-04 14:37:00,959 8044 [INFO ] - [-] Disabling services
2019-10-04 14:37:00,975 8044 [INFO ] - 	[+] Disabled OpenVPN Services
2019-10-04 14:37:00,975 8044 [INFO ] - 	[+] Disabled Neo4j
2019-10-04 14:37:00,990 8044 [INFO ] - 	[+] Disabled OpenSSH Service
2019-10-04 14:37:03,008 8044 [INFO ] - [+] Cleaning up the Desktop
2019-10-04 14:37:05,039 8044 [ERROR] - ERROR: Cannot bind argument to parameter 'Path' because it is null.
2019-10-04 14:37:05,039 8044 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '''] exited with '-1'.
2019-10-04 14:37:05,053 8044 [DEBUG] - Calling command ['"C:\WINDOWS\System32\shutdown.exe" /a']
2019-10-04 14:37:05,100 8044 [DEBUG] - Command ['"C:\WINDOWS\System32\shutdown.exe" /a'] exited with '1116'
2019-10-04 14:37:05,178 8044 [DEBUG] - Capturing package files in 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye'
2019-10-04 14:37:05,210 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\commandovm.win10.config.fireeye.nupkg'
with checksum '5D56F6D7418C51DF6766ECAAC4C13DCE'
2019-10-04 14:37:05,210 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\commandovm.win10.config.fireeye.nuspec'
with checksum '3EDF9F3A856156747DA12DFAA36DFD89'
2019-10-04 14:37:05,225 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\Backgrounds.7z'
with checksum 'C4FAFB484C6DB19DA0E067E2443410F7'
2019-10-04 14:37:05,225 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1'
with checksum 'A37BA8C8B73698F7B653000EB5F44802'
2019-10-04 14:37:05,225 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyuninstall.ps1'
with checksum 'A1D3EBB1CB66DF3EC925CEFEEF31D3E0'
2019-10-04 14:37:05,242 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\CommandoVMLogos.7z'
with checksum 'DE74C7CCF537CF836D3B48DD519C2E86'
2019-10-04 14:37:05,242 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\EnableWinRM.ahk'
with checksum '28D524274BD66E4B57D0381006D0E41A'
2019-10-04 14:37:05,242 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\LightMale_Red.png'
with checksum 'AAFADF1C60DCC1ADD2ED79A58DA30574'
2019-10-04 14:37:05,242 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\readme.txt'
with checksum '8422F60468EE382B888D0AA29586C260'
2019-10-04 14:37:05,242 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\UNCPathSoftening.ahk'
with checksum 'A693F8B2F0D55FB16A6CD50C344D6DF9'
2019-10-04 14:37:05,242 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\WallpaperChanger.exe'
with checksum 'EC9DF03A1A6940711507F6D9973AC1EE'
2019-10-04 14:37:05,242 8044 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\WallpaperChanger.exe.ignore.txt'
with checksum 'D41D8CD98F00B204E9800998ECF8427E'
2019-10-04 14:37:05,256 8044 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\commandovm.win10.config.fireeye.<IP_ADDRESS>.arguments".
2019-10-04 14:37:05,256 8044 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\commandovm.win10.config.fireeye.<IP_ADDRESS>.extra".
2019-10-04 14:37:05,256 8044 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\commandovm.win10.config.fireeye.<IP_ADDRESS>.version".
2019-10-04 14:37:05,256 8044 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\commandovm.win10.config.fireeye.<IP_ADDRESS>.sxs".
2019-10-04 14:37:05,256 8044 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\commandovm.win10.config.fireeye.<IP_ADDRESS>.pin".
2019-10-04 14:37:05,256 8044 [DEBUG] - Attempting to delete directory "C:\ProgramData\chocolatey\lib-bad\commandovm.win10.config.fireeye".
2019-10-04 14:37:05,256 8044 [DEBUG] - Sending message 'HandlePackageResultCompletedMessage' out if there are subscribers...
2019-10-04 14:37:05,271 8044 [ERROR] - The install of commandovm.win10.config.fireeye was NOT successful.
2019-10-04 14:37:05,271 8044 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1'.
See log for details.
2019-10-04 14:37:05,271 8044 [DEBUG] - Moving 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye'
to 'C:\ProgramData\chocolatey\lib-bad\commandovm.win10.config.fireeye'
2019-10-04 14:37:07,304 8044 [DEBUG] - Attempting to delete file "C:\Users\Administrator\AppData\Local\NuGet\Cache\commandovm.win10.config.fireeye.<IP_ADDRESS>.nupkg".
2019-10-04 14:37:07,304 8044 [WARN ] -
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
2019-10-04 14:37:07,318 8044 [INFO ] -
2019-10-04 14:37:07,318 8044 [ERROR] - Failures
2019-10-04 14:37:07,318 8044 [ERROR] -  - commandovm.win10.config.fireeye (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\commandovm.win10.config.fireeye\tools\chocolateyinstall.ps1'.
See log for details.
...snip...
Version

OS: Windows 10 1903

Additional context
This is logged in as Aministrator, running PowerShell as Administrator, and running 'Set-ExecutionPolicy Unrestricted'. The same error happens when just re-running install.ps1

This may have something to do with running the install.ps1 as Administrator (S-1-5-*-500), rather than a separate account added to the Administrators group.

Issue should have been resolved in recent update with improved error handling.


Consumer API: Endpoint for reading the current major version of the Backbone

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration tests.
[x] I ensured that the PR title is good enough for the changelog.
[x] I labeled the PR.

As discussed via chat, 99% of this PR needs to be reworked. I will close this one.


Ability to customize text & logo for different cities

The phrase "Seattle" (and Seattle's logo) are currently hardcoded.
We need to abstract this so other cities can do minimal branding:

Find the hardcoded text 'Seattle', turn it into an environment variable that is part of initial deployment config.
Find the hardcoded logo for Seattle, turn it into another environment variable that references an image file under version control.
Put the logos under version control (e.g. in a logos/ directory)

FYI:  Rochester has provided a logo to Google Fellowship within their sharepoint area.

About customize, here are some other parts to be consider. Although we can still using the same setting, but I believe is better to make certain decision upfront to make it more consistent
rather than spend more time to deal it later on:

Font, color, icon : Right now, the font, the color style, and parts of icons all use Seattle's style, which means, it uses Seattle font, Seattle color and some Seattle icons(icon mixed with some Seattle and some others).

Language
The 8 languages right now are based on Seattle’s language preference, different cities have different language preferences.
Questions to think about:
If we stay in the same setting, how will other parts affect later on? will it cost more time and energy on it? are there any limitations? how far do we want the cities to be customized? will there be more cities? how are we going to scale?

We discussed and for standing ROC up we don't need to edit the fonts/colors just update the images. We are also going to put the roc images in the civiform repo instead of linking out (or sort out CORS issues with having a remote image location)


Dynamic option creation does not play well with Chinese IME

Hi,
Dynamic option creation works well for English. I love it.
But when I tried to input some Chinese chars, the process that IME (Input Method Editor) was composing words got interrupted unexpectedly, then some strange tags were then created (usually with the keystroke I had been inputting).
I tested on the document example page and my test page (ver 4.0.12), on Windows 10 and Debian, with all IME's I had, all got the same issue (except for English input method, obviously).
--
Gilbert Fine

This appears to be a common problem. Making this the primary ticket to track the issue.
https://github.com/select2/select2/issues/5267
https://github.com/select2/select2/issues/5252
https://github.com/select2/select2/pull/5268
https://github.com/select2/select2/issues/5271

Forgot to metion that this issue only occurs when multiple is set, like the example in "Tagging with multi-value select boxes" section.
And I tested on macOS just now. This issue did NOT occur in safari, but occurred in firefox and chrome.

@ruiheng
Select2.prototype._isChangeMutation = function (evt, mutations) {
/Forced to eventually "changed" return false, it is not clear whether there are new problems, but the Chinese input problem solved./
retrun false;
}

@zzbajie 感谢指教。我会找时间试试。

I'm also experiencing this issue. Really urgent to get this fixed.
Anyone have a usable workaround?

This issue begin from ea79a197e0ffe55aa600eed6d18cbd1c804c3176.
I tried commenting out this line and it seems to work.
https://github.com/select2/select2/blob/4.0.13/src/js/select2/core.js#L212
But i cannot understand how this line works, so i cannot decide if it can be deleted ;(

But i cannot understand how this line works, so i cannot decide if it can be deleted ;(

Unfortunately it can't be deleted.
That line allows for Select2 to detect an <option> element being added to the DOM and for it to automatically be picked up by Select2 to display it in the dropdown (for example). This bug is a challenge for me to personally reproduce since I do not use IME, but it would be interesting to understand why the DOM subtree is changing to better understand the issue.
I am also curious if this issue still exists in 4.1.0-beta.1 now that we simplified the subtree handling. My guess is still yes, but it's always good to verify.

@kevin-brown
Thanks now I understand.

I am also curious if this issue still exists in 4.1.0-beta.1 now that we simplified the subtree handling. My guess is still yes, but it's always good to verify.
I confirmed fixes the issue at 4.1.0-beta.1.

I'm looking forward to the release :)


Documentation

Write the documentation of this web app.

Hello, I have used read.me file's content to demonstrate, I can write this type of documentation can you guide me and asign this tasks to me I will give my best to add some value

Hello, from Covaccine
It is a flask based web application to spread awareness on COVID-19 vaccination. As India is going through an intense COVID-19 second wave, awareness regarding vaccination and available resources is the need of the hour. The implementation of the website is fairly simple based on the following technologies.
#How it works? #

The website home page has various resources and information regarding COVID-19 vaccination.
The user can Login/Register to the website to maintain their profile where many new resouces are available

API used

like real-time API COVID tracker update, nearest vaccination centres, donation, profile updates along with much more.

#How to use?#
To run the web application use these commands:

$ export API_KEY= enter your api key
$ export FLASK_APP=application.py
$ flask run


Converting boolean data types from database to 1.0 and 0.0 value metrics?

I run into this INFO log when trying to bring in a boolean data type from the postgres db:
INFO[0088] Unparseable column type - discarding:  pg_importer_table success <nil>
After a little investigation, it seems that the exporter does not handle float conversion of boolean data types to float.  I was thinking we can slap an if statement giving it a 1.0 if true, 0.0 otherwise.  This would be useful to track in Prometheus, especially for alerts when a value becomes true/false.
Is this something that can be incorporated?  I wouldn't mind sending in a PR, just wanted to see get some feedback from anyone.

This seems reasonable, but the PR has linter errors preventing it from being merged at the moment.


pull request for e2e test at 11/14/2016 02:15:10

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix logs for failed builds

It turns out we need to check both the drv and the path to get all logs when remote building. Only checking the path does not return any failed build logs.

fixed in https://github.com/Mic92/nixpkgs-review/pull/174


Bump .buildkite-platform.json for 3.2.12 chef-foundation

openssl.so fix for Windows
Ruby 3.1.6
perl and curl fixes

Description

Related Issue

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

@tpowell-progress rebase on chef-18


💄 chore(docs): Update API sidebar

Current dependencies on/for this PR:

new-dawn

PR #1064   👈

This stack of pull requests is managed by Graphite.


Set timeout for Exec dynamically

When using DNS-01 and a high value for dnssleep the exec may terminate due to a timeout:
Error: /Stage[main]/Acme::Request::Handler/Acme::Request[foobar.example.com]/Exec[issue-certificate-foobar.example.com]/returns: change from 'notrun' to ['0'] failed: Command exceeded timeout

Maybe  we should set the exec timeout dynamically, depending on the value of dnssleep.

I don't think this is strictly necessary. Anyone who requires higher values for Exec timeout should probably set it globally or disable it.


Regression in pcli view address

Describe the bug
pcli view address used to output the requested address, but now it outputs other, unrelated text:
$ cargo run --release --bin pcli -- view address --ephemeral
Account 0: (ephemeral) penumbrav2t1ztuqjfz7vffq86z0gp7u8l3y9s2cqq0zejcmfx28xcuh80fwm9ywt47k4kawlz0x39vqr7lvx8jv2muyusxg03vldzjpx2pwhrf2623fkhkjep9jx60l0tmcdeylcrfxcwq7s4

This breaks composability, since the output of the command can't be used without ad-hoc string parsing, and displays non-useful information (the user knows it's an ephemeral address, because they specified that when running the command!)

It's all good, just wanted to flag it — it's useful to be able to do stuff like "generate a text file with 2,000 of my own addresses" or so on, and that's easier when the text output is minimal.


Some urls of OMK server are not working

I deployed the OMK server in Amazon following this documentation. After that the following URLs mentioned in this documentation are not working.
http://{{your_host_url}}/omk/info
http://{{your_host_url}}/omk/pages/#/upload-form
Kindly request your help to solve this issue. I am a new person to this area.

@KavinduZoysa These URLs are correct. /omk/info/ returns a JSON file with some information about the server. /omk/pages/#/upload-form needs to log in first to be seen.

@KavinduZoysa if you deployed it with posm-build, probably the urls are a bit different.

Thank you @willemarcel. What is the document I need to follow?
I followed this https://github.com/hotosm/OpenMapKitServer/blob/master/docs/posm-build-installation.md. Is it wrong?
This is the URL of my odk server http://<IP_ADDRESS>/. Appreciate if you can check that.

@KavinduZoysa Sorry, I don't have too much knowledge about POSM. If you really need all the tools on POSM, I suggest you to ask for support on https://github.com/posm/posm-build/
If you just need OpenMapKitServer, try with the Dockerfile or see the installation instructions:
https://github.com/hotosm/OpenMapKitServer/blob/master/Dockerfile
https://github.com/hotosm/OpenMapKitServer/blob/master/docs/development-installation.md

@willemarcel thank you for your quick response. Initially, I get the support from POSM and this is the issue I created https://github.com/posm/OpenMapKitServer/issues/129. They have pointed me to this repo and I installed OMK server again by following the readme of this repo.
Yes, as you mentioned I just need to install OMK server. So I prefer to run this docker file in my instance. Kindly request the instruction if possible :-)

@willemarcel , is there any place where I can find the docker image?

@willemarcel, First of all, thanks a lot for your support. By running the DockerFile I was able to start the OMK server.
I have another question. To log in I used admin:admin as username and password. Is that correct?

@KavinduZoysa you can set the users on https://github.com/hotosm/OpenMapKitServer/blob/master/util/users.json . More information about authentication: https://github.com/hotosm/OpenMapKitServer/blob/master/docs/development-installation.md#users-and-roles.
When deploying with Docker, take a special attention to setup a S3 Bucket and enable the S3 sync, that way you have your data copied to S3 after each operation. You can start the S3 bucket with the content of the data dir here on the repository. Docs: https://github.com/hotosm/OpenMapKitServer/blob/master/docs/development-installation.md#data-sync

@willemarcel Thanks a lot for your great support.
I am closing this issue since the issue mentioned in the title was able to fix. Will get back if I found any unclear thing.


Collect attendance data from Nov 30th - Dec 13th

[o] means pinged and waiting for a response
Week of Nov 30th- December 6th

[x] Elizabeth High School @amysorto
[x] San Mateo High School @saescapa
[o] Cherry Hill High School East @Bogidon
[o] Lowell High School

Week of December 7th - 13th

[o] Elizabeth High School @amysorto
[x] San Mateo High School @saescapa
[x] Cherry Hill High School East @Bogidon
[o] Lowell High School

@MaxWofford, I've messaged all of my clubs to setup an attendance collection mechanism.

Make sure to put this information in clubs.hackclub.io as well

Waiting on responses from club leaders.

We decided that it was not that important to have 100% coverage on this at our weekly planning meeting yesterday so for now I'm closing this issue with 7/8 checkboxes checked off.


Fix triggerSubmit propType

I'm currently getting: "Warning: Failed prop type: The prop triggerSubmit is marked as required in *, but its value is undefined."
All uses of the prop are boolean in the code, not sure where the func came from.

Codecov Report

Merging #2747 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2747   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          67      67
  Lines        1384    1384
======================================
  Hits         1384    1384

Impacted Files
Coverage Δ

src/propTypes.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 09a24ad...47fde3f. Read the comment docs.


Unable to capture pages with hash-style routing (single page apps)

Vue's router and many other frameworks used by single page applications usally defaults to a hash mode - i.e it uses the URL hash to simulate a full URL.
Due to how the slugify dependency handles URLs, the # is stripped from the URL - leaving all the pages with identical URLs. I.e, the following all become hb.wopian.me:

hb.wopian.me
hb.wopian.me/#/@wopian
hb.wopian.me/#/anime/cowboy-bebop
hb.wopian.me/#/manga/20th-century-boys

This causes the output of pageres to only contain a single image per resolution showing whichever page was processed last.

hb.wopian.me-1920x1080.png
hb.wopian.me-412x732.png

Unfortunately I'm required to use the hash mode for routing as modifying nginx/apache config files is required for dynamically generated pages (e.g hb.wopian.me/anime/...) - something you can't do with GitHub Pages.
Code
const PageRes = require('pageres')

const pageres = new PageRes({ delay: 10 })
  .src('hb.wopian.me', [ '412x732', '1920x1080' ])
  .src('hb.wopian.me/#/@wopian', [ '412x732', '1920x1080' ])
  .src('https://hb.wopian.me/#/anime/cowboy-bebop', [ '412x732', '1920x1080' ])
  .src('https://hb.wopian.me/#/manga/20th-century-boys', [ '412x732', '1920x1080' ])
  .dest(`${__dirname}/../screenshot`)
  .run()
  .then(() => console.log('done'))

Edit: PhantomJS 2.5.0-development is required to test with this site due to flex usage.

I guess we could strip #/ from the URL path in the filename method. Pull request welcome. Should come with a test.


Fixed missing rest_times decrement on idle.

Codecov Report

Merging #63 (4693bd4) into main (f692203) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #63   +/-   ##
=======================================
  Coverage   89.65%   89.65%
=======================================
  Files          90       90
  Lines        9859     9859
=======================================
  Hits         8839     8839
  Misses       1020     1020


refactor: use async-await

This is part of the Awesome Endeavour: Async Iterators:
ipfs/js-ipfs#1670

This module implements the https://github.com/maxogden/abstract-blob-store interface and should continue to do so.
If a version of this with async/await is required, I suggest that a new module is created.


Adding shards per node constraint for predictability to testClusterGr…

…eenAfterPartialRelocation
Signed-off-by: Ankit Jain<EMAIL_ADDRESS>Description
The test was failing due to some replica shards initializing and completing before last primary shard could finish initializing. Added shards per node constraint to prevent this from happening. The test has become really lightweight, completes in less than 5 seconds mostly and ran locally without any failure more than 500 times
Issues Resolved
#1957
Check List

[x] New functionality includes testing.

[x] All tests pass

[] New functionality has been documented.

[] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

start gradle check

❌   Gradle Check failure 93eb18e Log 2420
Reports 2420

Tests with failures:

org.opensearch.gateway.RecoveryFromGatewayIT.testReuseInFileBasedPeerRecovery

❌   Gradle Check failure 73ccfcc Log 2423

Tests with failures:
org.opensearch.gateway.RecoveryFromGatewayIT.testReuseInFileBasedPeerRecovery
and some centos issue as well

start gradle check

Unrelated error, restart gradle check

start gradle check

start gradle check

start gradle check

start gradle check

✅   Gradle Check success 73ccfcc Log 2521
Reports 2521

Yayy!


windows: navigating text in powershell core 6.2.3

Description of the problem or steps to reproduce
using micro file.txt

open a file with text.

try navigating from word-to-word using keyboard shortcuts. from 1st word to 7th word, by 7 presses.

I tried Ctrl+Up  i.e., cursor control keys.
Actual behavior:
cursor just skips to last word in the line.
expected:
it should work like it does in other editors. and in GitHub web interface.
Specifications
You can use micro -version to get the commit hash.
Version: 1.4.1
Commit hash: 1856891
Compiled on August 10, 2018
OS: Windows 10
Terminal: Poewrshell 6.2.3

cheers tratTalks

also consider adding https://github.com/NationalSecurityAgency/ghidra/tree/master/.github/ISSUE_TEMPLATE
cheers tratTalks


Not detecting diyHue Hub

I've tried to link this to my virtualized diyHue Hue Hub but it does not detect the virtualized bridge. Here's my console log. In between setup commands I pushed the virtual link button, but it's still not detected.
sh-3.2# dmx-hue setup
No bridge found
sh-3.2# dmx-hue setup
No bridge found
sh-3.2#

I'm running dmx-hue on my mac and the installation went without a hitch.
Do you have any tips?
Is it possible to specify a host ip address for dmx-hue setup. Maybe I can specify the ip address of my diyHue instance.

I don't know diyHue and never tried it, so I can't answer for sure if it's compatible.
This is the Hue library used to communicate with the bridge: https://github.com/peter-murray/node-hue-api
Make sure that your mac is on the same network as your Hue bridge to get it detected.
You can also use the --ip option to for the ip address of your diyHue instance and see if it works.

@sinedied How can I specify the --ip tag during setup?

Add it to the when running the command: hue setup --ip <adress>


Commit version bump enhancements

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
This PR follows #9423, which fixed a bug in the commit_version_bump action involving the :settings option. This PR is intended to fix the reasons for the bug, which results from logic that need not be in commit_version_bump. These changes make the action more extensible and flexible.
Description
There are two parts to this change, represented by different commits.

Add an optional :include parameter. There is already an :ignore parameter. This gives devs a back door to add any other configuration files (e.g., package.json) that might also be included in a version bump by explicitly specifying them. This option takes either an array of strings or a comma-separated string.

Add SharedValues::MODIFIED_FILES and Actions::add_modified_files. Passing an array of either relative or absolute paths to add_modified_files adds them to the list of files to be expected in a commit by commit_version_bump. This is stored in the lane_context as a Set to avoid duplication. Multiple actions or invocations of the same action can add to the list. The aggregate list will be added to the expected changes in commit_version_bump. No extra arguments to commit_version_bump are required to enable this feature.

It can be useful for validation to spell out all the files expected to be included in a commit, but paths can be lengthy, and this is error-prone. However, the :include option would be useful for anyone updating a custom configuration file by shelling out to a custom script, e.g.
Using the lane context makes the action a lot more flexible and requires nothing special from the user. This approach could allow commit_version_bump to support Android, for example. The second approach could also be adopted in the existing increment_build_number and increment_version_number actions to avoid having to specify the :xcodeproj parameter in commit_version_bump. Modified files could be passed in the lane context, and commit_version_bump could become much simpler.
To try it out:
git clone https://github.com/jdee/settings-bundle
cd settings-bundle
git checkout commit-version-bump-enhancements
bundle install
bundle exec test # uses the :include parameter
bundle exec group_test # uses the current :settings parameter
bundle exec library_test # uses the lane context (no :settings or :include parameter)

And see the example Fastfile there.

This is hardly urgent, but I had another thought about this:
If there's sufficient interest, I could just contribute the update_settings_bundle action to Fastlane itself and sunset the settings_bundle plugin. The plugin has 100% test coverage and has been through a few releases and bug fixes from the field. The SettingsBundleHelper is very solid and could just be used in commit_version_bump instead of the method in CommitVersionBumpAction to avoid having the same code in two places in different repos.
Of course, not every iOS app has a settings bundle, and not every app that has a settings bundle adds static title entries like the version number. So maybe that action isn't sufficiently general for Fastlane. But in that case, settings bundles will continue to be updated by a plugin, and there's this method in Fastlane that will continue to have to be maintained in parallel. That probably won't happen too often, so maybe it's not a huge problem, but it seems like there's room for improvement.
I still think the approach in this PR is nicer and can make commit_version_bump a lot more general. But there are plenty of options.

I hadn't looked at this in a long time. The include_list_from_param method was unnecessary because I had not yet discovered the joys of FastlaneCore::ConfigurationItem#auto_convert_value. This is one reason I want to add some stuff to the docs on using built-in configuration tools and so on. I'll see what I can come up with this weekend.

@ohayon Done. We can discuss it elsewhere, but I'm not sure I'm in favor of the idea. Then again, I still prefer $:.unshift. Anyway, good to keep things uniform.

@ohayon The :ignore param (almost) predates my acquaintance with Fastlane. It's used here. I think it was added in this PR.


PLZ DO MENTION THE CORRECT STEPS IN DEPLOYING EXECUTIVE DASHBOARD

As of now i am working on developing a executive dashboard and faceing sever failures since from build steps and i execpt some fast suggestion plz

Exec has it's on project. Please do not open issues for it here. We will respond as soon as we can.


[Key Manager] Support configurable protocols (e.g., http/https) in the key manager config.

Motivation
The key manager communicates with the blockchain using a JSON RPC endpoint. However, the key manager currently assumes the use of "https" for this endpoint.
Given that there are deployment scenarios in which one would prefer to use "http" instead of "https" (such as testing, or local deployments of the key manager on the same node as the JSON RPC endpoint), it makes sense to allow the key manager configuration to specify which protocol to use. Note: by default, the config is still set to use "https", unless overridden.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
A local tests still pass.
Related PRs
None.

:umbrella: The latest upstream changes (presumably 13f9f8c71fa718d8f6ab6dd380776c2943fea8bc) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably f0baeb020fef42e9690c04ec883f03d8c331e202) made this pull request unmergeable. Please resolve the merge conflicts.

Thanks, David! 😄

Regarding the logs, I see what you're saying and I've removed them.
Regarding naming, I've gone for "json_rpc_endpoint".

Let me know what you think!

Thanks, David! @bors-libra r=davidiw

:pushpin: Commit eca3c2e has been approved by davidiw

:hourglass: Testing commit eca3c2e83c2105837be0da9935c612f89b4ef6ea with merge e83ea3af11f2116a5c889a3b1c6acb7832d8c1d3...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: davidiw
Pushing e83ea3af11f2116a5c889a3b1c6acb7832d8c1d3 to master...


"Take a tour of IoT Central "button is dead

https://docs.microsoft.com/en-us/azure/iot-central/quick-deploy-iot-central#overview-iot-central-tour
"Take a tour of IoT Central "button is dead https://docs.microsoft.com/en-us/azure/iot-central/quick-deploy-iot-central#overview-iot-central-tour

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

ID: ac080129-df96-f794-3397-999ecc3d1955
Version Independent ID: 69435e73-967c-72ac-b0af-02d6ef4767f2
Content: Create an Azure IoT Central application
Content Source: articles/iot-central/quick-deploy-iot-central.md
Service: iot-central
GitHub Login: @viv-liu
Microsoft Alias: viviali

@aepsicom Thanks for the feedback! We are currently investigating and will update you shortly.

@viv-liu Yes, the link is not working and please have a look at this and update it accordingly.

This will be fixed in#58382 We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


feat(forge): multi chain deployment

follow-ups:

library - linking (currently it just aborts if it the project requires it)
Messy stdout during concurrent operations (simulation / broadcasting / verification)
Unite both single and multi deployment flow once the above two are solved.

Ref #2609 for multi chain verification

@joshieDo FYI #2609 now merged

Still going to add simple tests, but opening the PR already for review.

added tests

Would love if @aureliusbtc @mds1 or @hexonaut took it for a test before we merge

Planning to test this week! Will update here afterwards

We still haven't switched to Foundry deployment yet. It's one of the last things we are still using dapp tools for.
Will test these features when we switch over, but probably not for this PR.

Finally got around to testing this. With this PR I'm seeing a non-descript error. Running: forge script script/DeployExistingTokenBridge.s.sol:DeployExistingTokenBridge --use solc:0.8.14 --rpc-url $ETH_RPC_URL --broadcast --verify -vvvv
Which produces:
The application panicked (crashed).
Message:  called `Option::unwrap()` on a `None` value
Location: evm/src/executor/backend/mod.rs:587

The crash appears to happen on this line when switching forks twice: https://github.com/makerdao/dss-bridge/pull/2/files#diff-e2a54d4d0ad2ae2494877491f14dffba4442e3ada78d1f1aecf7477e1857345aR47

As I said in our Discord chat, I updated to latest here and it seems to work fine now, so not sure what happened. Appears to work great now!

@joshieDo could you resolve conflicts and feel free to merge! nice work.

bump @joshieDo PTAL re: conflicts, would like to merge this week if poss

resolved pretty easily (maybe too easyily..). There were some changes which i was not aware on the master branch, and i'm not quite sure how that may impact this branch
waiting for the CI, and going to run some manual tests meanwhile

manual tests of deployment + verification successfully passed. Pending CI i think we can merge, and tackle the inevitable issues as they come

SHIP IT

So, what's the API look like on this?
https://ethereum.stackexchange.com/search?q=two+chains+foundry
How do I actually use this for a multi-chain deployment?


Non-fallback image generated without -H / --hostonly argument

The tool generates initramfs files as expected as non-fallback and fallback versions. However, the file sizes indicate (e.g. via du -sh /boot/init*) that both files are in fact fallback images. In the script code I also cannot find the -H / --hostonly parameter being passed to dracut.

Sorry, this is apparently an oversight on my part. I will fix this and release the fix immediately.

@xuanruiqi No worries. Thank you for the nice tool btw. :)

I released it on GitHub two weeks ago, but forgot to bump the version on the AUR as well. Now done!


gongsvg sometimes not responsive

Sequence:

see cypress sequence

Problem:

diagram not updated

Workaround:

reload application

On the front the web socket payload seems to be incomplete. LayersAPI pointers encoding are not encoded sometimes.
Is this a problem on the backend ? On the transmission ? On the receiver ?

Analysis:
there is no mutex on the backRepo while it can be written by a commit and sent to the front with a web socket (#524).
this is provoked by the gongdoc that performs a useless commit after the Reset of the stage.


python311Packages.oncalendar: 1.0 -> 1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.oncalendar is: A systemd OnCalendar expression parser and evaluator
meta.homepage for python311Packages.oncalendar is: https://github.com/cuu508/oncalendar
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1 with grep in /nix/store/4l79yxdkd4hh5bkb0lmnwfyrih78p80y-python3.11-oncalendar-1.1
found 1.1 in filename of file in /nix/store/4l79yxdkd4hh5bkb0lmnwfyrih78p80y-python3.11-oncalendar-1.1

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
healthchecks
python311Packages.oncalendar
python312Packages.oncalendar

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4l79yxdkd4hh5bkb0lmnwfyrih78p80y-python3.11-oncalendar-1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix 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 python311Packages.oncalendar https://github.com/r-ryantm/nixpkgs/archive/1a6e0b9a82659ae8a36d1b80aebcabe89f806916.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1a6e0b9a82659ae8a36d1b80aebcabe89f806916#python311Packages.oncalendar

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4l79yxdkd4hh5bkb0lmnwfyrih78p80y-python3.11-oncalendar-1.1
ls -la /nix/store/4l79yxdkd4hh5bkb0lmnwfyrih78p80y-python3.11-oncalendar-1.1/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.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

5 packages built:

healthchecks
python311Packages.oncalendar
python311Packages.oncalendar.dist
python312Packages.oncalendar
python312Packages.oncalendar.dist

Maintainer pings
cc @phaer for testing.

Duplicate of https://github.com/NixOS/nixpkgs/pull/303789


add NicknamePokemon

Short Description:
Fixes:

this is more confusing than usefull

there are a few other example files that would need updating if we're going to do this. Also, we had a wave of reaction by our users that just "plug and play" with having all their pokemon renamed without them wanting that, so the default template should actually be "nickname_template": "" if anything.

This was removed from the json because people copy and paste the example config and didn't want to have everything duplicated. We need a better (different) way to show people all of the different options available to them.

@TheSavior we've got some people that, such as brantje in slack, that have implemented config generators. maybe we should consider maintaining one with the bot as a submodule, which might ease the whole config generation process.


Introduce support for $error outputs

As a strategy for implementing error handling #96, simply

add a convention that errors should lead to an $error output,
treat uncaptured $error outputs as an error at the graph level, and
automatically convert exceptions from within a node to $error outputs (thus recovering current behavior when $error isn't captured).

This distinction is most useful when

errors are often expected (because for instance inputs can be irregular) and there is a well-defined handling strategy (showing something to the user or so)
LLM self-correcting loops where we feed the error back to the LLM and try again

In nested graphs, the include (or soon call) node outputs $error if it catches and uncaptured $error in the called graph.
Uncaptured errors handled in this way should be annotated with the (in the nested case:) graphs and node-ids of the source.

I really like this.

About to submit with a little addition. $error are of type ErrorCapacity, which have

error – instanceof Error that was caught
inputs – Original inputs of the node
descriptor – Metadata about the node

The latter two are automatically added when a node outputs $error and they aren't already specified.
This should help with retrying flows, as otherwise the inputs would already be consumed and now lost. I'm adding descriptor for debugging context, but it might eventually be helpful when we for instance catch errors at a lambda level and retry with a new version of the lambda written by an LLM.

I'm also changing the error behavior of generateText:
Before it didn't output completion, but output filters. This let to silent aborts of graphs, as the subsequent nodes were missing inputs and nothing was looking at filters.
Now it'll either output completion or $error, the latter with filters and safetyFeedback.
I suggest we generally adopt this pattern for nodes that have an expected positive outcome and otherwise negative outcomes.


fix: Testing PR #3

testing
#minor

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 54.605%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
19650

Relevant Lines:
31633

💛  - Coveralls


add ipv6_cidr_block variable to toggle IPv6 VPC association

what

Add ipv6_cidr_block variable to toggle IPv6 VPC association.

why

This change allows the user to decide if IPv6 CIDR block should be associated to the VPC or not, since there are cases where the current behavior (assign_generated_ipv6_cidr_block = true) is not desired.

references

Apparently, issue #15 is not a problem anymore when assign_generated_ipv6_cidr_block = false.  I was able to get empty strings as output of vpc_ipv6_association_id and ipv6_cidr_block.
This PR closes #59

/test all

/rebuild-readme

/test all


Bot does not add label, link to sources & docs for integration

Looking at https://github.com/home-assistant/core/issues/79639 I wondered why the bot didn't add a label although the user did add the integration name and a link to the docs.
Even after adding the label the bot did not add links to docs & sources.
Creating an issue so we don't forget to check it.

Well after creating the issue the bot woke up, I guess this was just delayed, closing


Appending videos with different bit encoding rate

Can i append videos with different encoding bit rate?

Yes you can as the bitrate is not the decisive factor. The decoding configuration (SPS/PPS) needs to be the same. If you don't know what this is have a look at profile/level: You can only append<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(same level/profile is necessary, but not a sufficient condition!)

I ssent you two files on email with different bit encoding rate but other configuration same.I am not able to append it.Please check.Thamks!