What's proper SW name? :)

OK, guys - we need to settle, what's the proper name of SW
Is it:

Service Workers
ServiceWorkers
Service Worker
ServiceWorker

Various examples of usage from the web :)

Service Workers
@jeffposnick - http://updates.html5rocks.com/2015/02/offline-first-with-sw-precache

ServiceWorkers
@jakearchibald - http://jakearchibald.com/2014/using-serviceworker-today/

Service Worker
https://notifications.spec.whatwg.org/#service-worker-api

ServiceWorker
https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorker_API (in title, in text it's 'service worker' so technically it's the fifth one)

Combos:
@slightlyoff  - Name of this repo is "ServiceWorker", at the end of the URL https://slightlyoff.github.io/ServiceWorker/spec/service_worker/ is "service_worker" and in  title h1 there's Service Workers
Some problems that this small issue introduces:

SW is now included in Platinum Elements in Polymer. Let's see what tags are there: "serviceworker" and "service-worker". On Stack Overflow? [service-worker]
It'd be nice to measure people interest in this topic after ex. Google I/O - but what phrase should we use?

Additionaly, it actually means also something else (The service workers strike), so we should be extra-careful.
It's the last moment, when we still can control it somehow (until hundreds of blogs will write some article about SW, using different names) - so let's do it :)

I believe the editorial team settled on "service worker" when it came to http://www.html5rocks.com/en/tutorials/service-worker/introduction/

In the first header there's "Service Worker" while in paragraph there's "service worker" :P

and in code in console.log "ServiceWorker" ;)

Well, the headers I can forgive, because they're capitalised. Eg "How to Register and Install a Service Worker"

"How to use Service Worker" article's subtitle is not capitalized :)

I think it should be "service worker". Similar to "worker" and "shared worker".

If you can make that consistent with some PRs, that'd be appreciated.

I agree with "service worker". I'll do some grammar nazi work

If you can make that consistent with some PRs, that’d be appreciated.

PR: #818.


Fix caching Q client issue.

The code fixes reusing the Q client across slack users. We now cache a Q Client for each slack user.
Issue #, if available:
Description of changes
Below are the changes included in the PR.

Fix q client caching issue.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Merging changes to develop branch


board/intel-nuc Support for Intel Pro I210 Gigabit Networking via IGB

To enable support for PCI Express Intel network cards, would the change take place here?
resin-intel/layers/meta-resin-genericx86/recipes-kernel/linux/linux-yocto_%.bbappend
https://github.com/resin-os/resin-intel/blob/master/layers/meta-resin-genericx86/recipes-kernel/linux/linux-yocto_%25.bbappend
#
# Support Intel(R) 82575/82576 PCI-Express Gigabit Ethernet
#
RESIN_CONFIGS_append = " igb"
RESIN_CONFIGS_DEPS[igb] = " \
    CONFIG_PCI=m \
    "
RESIN_CONFIGS[igb] = " \
    CONFIG_IGB=m \
    "

I am unable to use  bitbake linux-yocto -c menuconfig. without build failure. Unsure what additional IGB configs must be included to enable this driver.

Can't seem to figure out how to add a label. This is related to board/intel-nuc

Can't seem to figure out how to add a label.

I think only people with write-access to the repo have the ability to add labels :wink:

CC @floion


HOSTEDCP-1478: Request serving node scheduler that uses HC size label

What this PR does / why we need it:
Introduces a new scheduler that is only enabled if cluster size tagging is enabled. It takes into consideration the size label of a particular hosted cluster to select nodes where the cluster's request serving pods are scheduled and applies settings configured in the cluster sizing configuration to the hosted cluster.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #HOSTEDCP-1478
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[x] This change includes unit tests.

@sjenning @muraee thx! comments addressed

lgtm

/lgtm

/override "Red Hat Konflux / hypershift-operator-main-on-pull-request"


New best model with 16 hidden

Note: While 16 hidden works just as well as 32, it takes much longer to train. I had to leave this run for 4 days. 32 works overnight.


Update documentation on Data Commons Architecture

Update architecture documentation in the repo to match scope of technical deep dive and also include the discussions about data management / security so this can serve as a reference with data stakeholders once we go public.

With several datasets presently represented in the Data Commons, it would be great to identify the key issues those datasets raise in terms of licensing, sourcing, update frequency, metadata, etc., and then use those themes to spell out the best practices intended by the architecture and the implementation.  I won't be offended if one of the pipelines I created is revealed to fall short of the goals in one or more categories!


Not working for dotnet build

Am I doing something wrong here, is there required configuration?  I'm on Linux.
$ dotnet --version
6.0.201
dotnet new console
dotnet add package Nullable.Extended.Analyzer --version 1.10.4539
dotnet run

// See https://aka.ms/new-console-template for more information
Console.WriteLine("Hello, World!");
string envstring = Environment.GetEnvironmentVariable("DOESNOTEXIST")!;
Console.WriteLine("This is null: {0}", envstring);

Does not trigger any warnings.
Tried adding this but the file is not being created
   <NullableExtendedAnalyzer>
          <LogFile>/tmp/foo.log</LogFile>
      </NullableExtendedAnalyzer>

I'm only using this with MSBuild on Windows.
If the analyzer is not invoked in your scenario, that's rather an issue with dotnet, not the analyzer.

Thanks.  I can find absolutely zero documentation about using analyzers with dotnet build, but I will keep looking and update this ticket if I get it working.
By the way, thank you for this awesome project, I hope I get it working.  We heavily discourage obj! and use __unwrap(obj) instead:
public class correctness_is_always_job_one
{
    public static T __unwrap<T>(T? obj) {
        if (obj is null) {
            throw new ArgumentNullException();
        }
        return obj;
    }
}

The new dotnet 6.0 "implicit global usings" makes it zero friction for all source code to access __unwrap:
  <ItemGroup>
      <Using Include="CPCommon.correctness_is_always_job_one" Static="True" />
  </ItemGroup>


Add enough functions to bring up a LUKS device

This provides enough functionality to perform a simple LUKS device bringup.

Merged, thanks a lot!


Populate Determination message from Detemination message template

Fixes #2809
Add description here.

Works well.
I see this feature is only there for Request and Concept and Proposal workflows. Other two workflows Request with external review and Request with community review are not included.
cc: @frjo, we can put it on test and test it there.

@sks444 Can you test it again, I have update the code to use Request workflow determination message templates for RequestExt and RequestComm. Actually, it is for all workflows other than the Request, Concept and ConceptProposal(as these three are already there in admin).

@sandeepsajan0, great, this works perfectly for Request, RequestComm, and for Concept in concept and proposal.
For RequestExt the messages doesn't populate. And for Proposal in concept and proposal, messages from request workflow gets populated. Can you verify on that once?

@sks444 I checked, and there was a name mismatch issue (Proposal got replaced by ConceptProposal). But it is working fine for both RequestExt and RequestCom for me. Can you please check if there is any cache issue(because I faced it but for all workflows)?

Now on test.


can we streamline the staging dockerfile?

our staging dockerfile is currently:
FROM tiangolo/uvicorn-gunicorn:python3.7-alpine3.8
LABEL authors="Nathan Sheffield, Michal Stolarczyk"

COPY . /app
RUN apk update
RUN apk add make automake gcc g++ subversion python3-dev
RUN pip install https://github.com/databio/yacman/archive/dev.zip
RUN pip install https://github.com/refgenie/refgenconf/archive/dev.zip
RUN pip install https://github.com/databio/henge/archive/master.zip
RUN pip install https://github.com/refgenie/seqcol/archive/master.zip
RUN pip install .

can we streamline some of this? I think we can remove henge/seqcol since we've embedded those now.
But can we also remove make, automake, gcc, g+, subversion ?

Related to #96

yes, it's definitely possible. I just used this one for development.


use more scoped imports in phobos

code (@MartinNowak) reported this on 2014-08-04T18:12:15Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=13253
CC List

andrei (@andralex)
dbugreporter
hsteoh
ilyayaroshenko

Description
There are too many unconditional global imports in phobos.

This unnecessarily slows down compilation, especially when only a single symbol of a module is needed. Recently I speeded-up dub [1] and found that just importing std.conv (only for to!string(__VERSION__)) already took ~150ms. Removing the import reduced the compile times for dub's compiler probe file [2] to ~3ms.

There are some ideas to make (static) imports lazy and we have some root to reduce the amount of work being done when importing a module (issue 13242).

We should still try to use more scoped (function-local) imports (better yet, scoped selective imports). Not only will this reduce compiles times for most D project, it also clearly specifies dependencies and helps to avoid no-longer used imports.

[1]: https://github.com/D-Programming-Language/dub/pull/388
[2]: https://github.com/D-Programming-Language/dub/commit/c9b685101cb5376d4ba4aa8ede4f8c9d346cd8de#diff-1c354aed609b1fe48ee6e2bb20fe396d

code (@MartinNowak) commented on 2014-11-07T15:31:03Z
https://github.com/D-Programming-Language/phobos/pull/2658

ilyayaroshenko commented on 2014-11-07T20:57:36Z
https://github.com/D-Programming-Language/phobos/pull/2659

dbugreporter commented on 2014-08-28T07:57:52Z
Beware of issue 10378 though. Using scoped imports means you have to be aware of every symbol in that module or you'll risk surprising behavior since there is no conflict detection.

ilyayaroshenko commented on 2014-11-07T21:41:26Z
std.range package
https://github.com/D-Programming-Language/phobos/pull/2661

ilyayaroshenko commented on 2014-11-08T23:53:30Z
https://github.com/D-Programming-Language/phobos/pull/2665
https://github.com/D-Programming-Language/phobos/pull/2666
https://github.com/D-Programming-Language/phobos/pull/2667

ilyayaroshenko commented on 2014-11-10T12:31:01Z
https://github.com/D-Programming-Language/phobos/pull/2678
https://github.com/D-Programming-Language/phobos/pull/2679
https://github.com/D-Programming-Language/phobos/pull/2680

andrei (@andralex) commented on 2017-12-20T00:35:23Z
https://github.com/dlang/phobos/pull/5948

ilyayaroshenko commented on 2014-11-20T18:49:29Z
https://github.com/D-Programming-Language/phobos/pull/2705
https://github.com/D-Programming-Language/phobos/pull/2706
https://github.com/D-Programming-Language/phobos/pull/2707
https://github.com/D-Programming-Language/phobos/pull/2708
https://github.com/D-Programming-Language/phobos/pull/2709
https://github.com/D-Programming-Language/phobos/pull/2710
https://github.com/D-Programming-Language/phobos/pull/2711
https://github.com/D-Programming-Language/phobos/pull/2712
https://github.com/D-Programming-Language/phobos/pull/2713
https://github.com/D-Programming-Language/phobos/pull/2714
https://github.com/D-Programming-Language/phobos/pull/2715
https://github.com/D-Programming-Language/phobos/pull/2716
https://github.com/D-Programming-Language/phobos/pull/2717
https://github.com/D-Programming-Language/phobos/pull/2718
https://github.com/D-Programming-Language/phobos/pull/2719
https://github.com/D-Programming-Language/phobos/pull/2720

Use scope imports in std.container package
https://github.com/D-Programming-Language/phobos/pull/2721

https://github.com/D-Programming-Language/phobos/pull/2722

fix binaryFun
https://github.com/D-Programming-Language/phobos/pull/2723

https://github.com/D-Programming-Language/phobos/pull/2725
https://github.com/D-Programming-Language/phobos/pull/2726
https://github.com/D-Programming-Language/phobos/pull/2727
https://github.com/D-Programming-Language/phobos/pull/2728
https://github.com/D-Programming-Language/phobos/pull/2729
https://github.com/D-Programming-Language/phobos/pull/2731

move format to std.format
https://github.com/D-Programming-Language/phobos/pull/2732

https://github.com/D-Programming-Language/phobos/pull/2733
https://github.com/D-Programming-Language/phobos/pull/2744

ilyayaroshenko commented on 2014-11-13T14:56:14Z
See also:
https://github.com/D-Programming-Language/phobos/pull/2700
https://github.com/D-Programming-Language/phobos/pull/2701

ilyayaroshenko commented on 2014-11-14T05:26:13Z
See also
https://github.com/D-Programming-Language/phobos/pull/2701

ilyayaroshenko commented on 2014-11-09T15:04:22Z
https://github.com/D-Programming-Language/phobos/pull/2669
https://github.com/D-Programming-Language/phobos/pull/2670
https://github.com/D-Programming-Language/phobos/pull/2671
https://github.com/D-Programming-Language/phobos/pull/2672
https://github.com/D-Programming-Language/phobos/pull/2673

ilyayaroshenko commented on 2014-11-13T09:52:53Z
https://github.com/D-Programming-Language/phobos/pull/2694
https://github.com/D-Programming-Language/phobos/pull/2695
https://github.com/D-Programming-Language/phobos/pull/2696

ilyayaroshenko commented on 2014-11-10T13:44:49Z
https://github.com/D-Programming-Language/phobos/pull/2681


DXF image files do not use the fallback image on search results list

Describe the bug
DXF images do not use the image fallback on the search listing page.
Environment

AEM Version: 6.4
Asset Share Commons Version: 1.6.0

To Reproduce
Steps to reproduce the behavior:

Install default Asset Share Commons
Load a .dxf file to your DAM (meta type image/vnd.dxf)
Execute a search on asset share where this file shows in the results list

Expected behavior
Placeholder image should display for DXF files, as they cannot be rendered from their original rendition.

Example DXF file:
Tyrannosaurus.DXF.zip

merged to develop and slated for 1.6.10


Use docs.rs for documentation

There are some inter-documentation links that have been updated as well.
The docs.rs team is working on support for custom documentation builds https://github.com/onur/docs.rs/pull/73. I went ahead and added the relevant metadata tag in Cargo.toml to support building all features of chatbot.

Inter-doc links were checked with the wonderful https://wummel.github.io/linkchecker/ tool.


Date field type

There should be a date field type for inputting dates in ISO 8601 format. An editor could present the field using the platform’s standard date picker, with an affordance for unset or malformed values. iD could use either <input type="date"> or <input type="datetime-local">. openstreetmap/iD#8951 requests a “Today” button to go along with it.
id-tagging-schema has several fields where this field type would apply:

Last Survey Date (survey:date)
Population Date (population:date)
Date Sunk (wreck:date_sunk)
Last Checked Date (check_date)
Start Date (start_date)
Expected Opening Date (opening_date)

OpenHistoricalMap’s fork of iD would benefit from this field type for its Start Date (start_date) and End Date (end_date) fields, which appear universally. A validator rule (OpenHistoricalMap/iD#138) has been critical for keeping the data well-formed, but users still find a plain text field to be more intimidating than a date picker, especially when working with sources like newspaper articles that say something like “last Friday”.


Vulnerability roundup 85: p7zip-17.01: 2 advisories [7.8]

search, files

[x] CVE-2017-17969 CVSSv3=7.8 (nixos-unstable)
[x] CVE-2018-5996 CVSSv3=7.8 (nixos-unstable)

Scanned versions: nixos-unstable: 22c98819ccd. May contain false positives.
Cc @7c6f434c

nixos-unstable uses an upstream that has specific commits that claim to fix these CVEs


fix second paragraph of each chapter

As described in #738, if a chapter has more than one paragraph in
introduction, only the first paragraph is imported on the website.
This is due to the #at method only selecting the first matching XPath
node.

@peff can you merge this, please?

Yeah, sorry for the delay; I needed to first figure out how to actually regenerate the book content in production.
Thanks so much for your help here and on the double-escaping issue.


Bump Yosys

This bumps Yosys solving the issue with recent changes in the mainline: https://github.com/chipsalliance/synlig/issues/1961
I've adjusted the references to Yosys' functions so that the plugin compiles.
There are Parsing Tests in Synlig which run simulation. Right now Yosys fails simulation if there are blackboxes. In such cases we should get rid of the simulation part.
Some tests are added to the skiplist as Yosys is unable to produce results that would be used in the Formal Verification tests.

Currently this PR uses a fork of Yosys in order to show that the tests pass when we revert one commit in Yosys.
We need to find a proper solution to get this working with the mainline Yosys.
See https://github.com/antmicro/yosys/commit/7afc568cfa46bf5aac0a7708bd38a6c950b56820


Enable-AzSqlManagedInstanceAdvancedThreatProtection

At the moment there are available commandlets for manipulating the Advanced threat protection settings of a managed instance:
eg: Get-AzSqlDatabaseAdvancedThreatProtectionSetting , Get-AzSqlServerAdvancedThreatProtectionSetting
However, these only work for Databases and SqlServers, but not for a Managed Instance.
It would be really helpful to have a commandlet specific for the Managed Instances.

Thanks for your question. Please provide us with the link to the documentation you are referring to so we can better assist.

Is there any update? Please share the link to the doc you are following.

Hey Karishma, here is the link for the documentation: https://docs.microsoft.com/en-us/powershell/module/az.sql/get-azsqldatabaseadvancedthreatprotectionsetting?view=azps-3.7.0
For the feature-request I mentioned, there is no documentation yet as this doesn't exist: Get-AzManagedInstanceAdvancedThreatProtectionSetting

@steve19922 Thank you for the feedback.
This is already in the product teams backlog.
You can follow the issue here
We will proceed to close this issue now.


Add support for Nethereum FunctionMessage-derived methods

Given the following code:
[Function("deposit")]
public class DepositFunction : FunctionMessage
{
}

var deposit = new DepositFunction()
{
    FromAddress = someAddress,
    AmountToSend = Web3.Convert.ToWei(tokensRequested * AppState.CurrentSale.MintPrice)
};

I need to be able to call something like MetaMaskService.SendTransaction(contractAddress, deposit);, and have it properly construct the entire transaction (including the properties in ContractMessageBase).
I need it to be functionally equivalent to this, without the convoluted architecture or setup hassle.
Thanks!

This library does not have easy helpers yet for ERC20 transfers. It would be very useful to have these helpers. I'm not actively developing them right now, a PR is always welcome.

Hello! This was closed as completed, is there some code I can see for the implementation?

Yes, I'd love to see some code for this. But there was no PR submitted yet? Are you still planning on submitting the PR? Then I will reopen.


Improve preferred names by boosting certain prefixes in choosing preferred name

This PR starts the process of improving preferred names, including:

Synonym files used to use only the label of the most preferred identifier. This PR changes that so that it uses the label of the first identifier with a label. Should close #142.
A first stab at implementing "boosted prefixes" configured by Biolink type, so that we can specify that for e.g. biolink:ChemicalEntity, we should boost certain prefixes when it comes to chooses preferred_name.

The idea for doing this comes from https://github.com/TranslatorSRI/Babel/issues/158#issuecomment-1769215304
Note that this will only set the preferred_name for NameRes, not NodeNorm, which calculates it on the fly. Changing that will either require adding the preferred label to the database or to duplicate this algorithm there. I prefer the former approach, but that's definitely something we'll need to consider in the next release.

The current preferred name boost prefixes are:
  "preferred_name_boost_prefixes": {
    "biolink:ChemicalEntity": [
      "DRUGBANK",
      "GTOPDB",
      "DrugCentral",
      "CHEMBL.COMPOUND",
      "RXCUI",
      "PUBCHEM.COMPOUND",
      "CHEBI",
      "HMDB"
    ]
  }

This ended up getting merged in PR #201. I'll move one minor update into PR #235 and close this PR.


Bug related to fish version

related => https://github.com/fisherman/anicode/issues/9
P.D.: I will do the fix, probably on sunday

Solved with commit 04d50c81e7f5aa2f56c86497713a14807c6bb5cb


Mixed up source and destination port configuration in Virtual network firewall rules video

I think there might be an inaccuracy in the video in the Virtual network firewall rules section:
https://learn.microsoft.com/en-gb/azure/azure-sql/database/network-access-controls-overview?view=azuresql#virtual-network-firewall-rules
From about the 3:30 mark in this (the 2nd video on the page) there is an inaccuracy in the demo NSG rule created.
The source port is likely to be an RFC 6335 Ephemeral port (https://en.wikipedia.org/wiki/Ephemeral_port) and a * or 49152-65535 would be appropriate but the destination ports should be the 1433, 11000-11999 range which is what the SQL database is listening on.

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

ID: 9ce162b8-052d-776e-3be2-0562cdbf365f
Version Independent ID: 2f062c81-c485-0c69-89b1-031b66a8a79b
Content: Network Access Controls - Azure SQL Database & Azure Synapse Analytics
Content Source: azure-sql/database/network-access-controls-overview.md
Service: sql-database
Sub-service: security
GitHub Login: @rohitnayakmsft
Microsoft Alias: rohitna

@chucklebrother Thank you for your feedback. We will review this and make an update if appropriate.

@chucklebrother  Thanks for the call out. Since I cannot edit this video I shall instead remove it from the docs to avoid confusion.

Hi @chucklebrother , thanks for bringing this to our attention! We've processed a change to remove the video. I'll go ahead and close out this Git Issue but please feel free to comment should you need anything further.
Thanks again and I hope you have a wonderful rest of your day!
Masha from the SQL Docs team
#assign:MashaMSFT
#please-close


Add a "Reviewed by Hound" badge and clean up other badges

The duplicate hound review can be avoided by going to Branch Settings and disabling hound. The capitalized version of Hound is the one you want.

LGTM, thanks!


Missing rpm packages in http://binaries.projectcalico.org/rpm/calico-3.22/

Missing rpm packages calico-common, calico-felix, and felix-debuginfo in http://binaries.projectcalico.org/rpm/calico-3.22/. Also, getting the error below when trying to install calico-3.21.
Error: Package: calico-felix-3.21.2-1.el7.x86_64 (calico)
Requires: libc.so.6(GLIBC_2.22)(64bit)

Thanks for raising this - I think I've spotted a bug in our packaging tools that was missing this package.
I just reuploaded those RPMs to please give it another try and see if it looks any better.

Hm, actually my re upload. Let me double check this.

I'm using Centos 7 workloads. My packages are up to date. I'm getting the following when installing calico-felix-3.21.2-1.el7.x86_64 (calico).

yum -y install calico-felix
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile

base: repos.forethought.net
epel: mirror.dal.nexril.net
extras: mirror.dal.nexril.net
updates: ftpmirror.your.org
Resolving Dependencies
--> Running transaction check
---> Package calico-felix.x86_64 0:3.21.2-1.el7 will be installed
--> Processing Dependency: conntrack-tools for package: calico-felix-3.21.2-1.el7.x86_64
--> Processing Dependency: iptables-utils for package: calico-felix-3.21.2-1.el7.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.22)(64bit) for package: calico-felix-3.21.2-1.el7.x86_64
--> Processing Dependency: calico-common for package: calico-felix-3.21.2-1.el7.x86_64
--> Running transaction check
---> Package calico-common.x86_64 0:3.21.2-1.el7 will be installed
---> Package calico-felix.x86_64 0:3.21.2-1.el7 will be installed
--> Processing Dependency: libc.so.6(GLIBC_2.22)(64bit) for package: calico-felix-3.21.2-1.el7.x86_64
---> Package conntrack-tools.x86_64 0:1.4.4-7.el7 will be installed
--> Processing Dependency: libnetfilter_cttimeout.so.1(LIBNETFILTER_CTTIMEOUT_1.1)(64bit) for package: conntrack-tools-1.4.4-7.el7.x86_64
--> Processing Dependency: libnetfilter_cttimeout.so.1(LIBNETFILTER_CTTIMEOUT_1.0)(64bit) for package: conntrack-tools-1.4.4-7.el7.x86_64
--> Processing Dependency: libnetfilter_cthelper.so.0(LIBNETFILTER_CTHELPER_1.0)(64bit) for package: conntrack-tools-1.4.4-7.el7.x86_64
--> Processing Dependency: libnetfilter_queue.so.1()(64bit) for package: conntrack-tools-1.4.4-7.el7.x86_64
--> Processing Dependency: libnetfilter_cttimeout.so.1()(64bit) for package: conntrack-tools-1.4.4-7.el7.x86_64
--> Processing Dependency: libnetfilter_cthelper.so.0()(64bit) for package: conntrack-tools-1.4.4-7.el7.x86_64
---> Package iptables-utils.x86_64 0:1.4.21-35.el7 will be installed
--> Running transaction check
---> Package calico-felix.x86_64 0:3.21.2-1.el7 will be installed
--> Processing Dependency: libc.so.6(GLIBC_2.22)(64bit) for package: calico-felix-3.21.2-1.el7.x86_64
---> Package libnetfilter_cthelper.x86_64 0:1.0.0-11.el7 will be installed
---> Package libnetfilter_cttimeout.x86_64 0:1.0.0-7.el7 will be installed
---> Package libnetfilter_queue.x86_64 0:1.0.2-2.el7_2 will be installed
--> Finished Dependency Resolution
Error: Package: calico-felix-3.21.2-1.el7.x86_64 (calico)
Requires: libc.so.6(GLIBC_2.22)(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

root@vmc7test psommers]# rpm -qa | grep glibc
glibc-common-2.17-325.el7_9.x86_64
glibc-devel-2.17-325.el7_9.x86_64
glibc-2.17-325.el7_9.x86_64
glibc-headers-2.17-325.el7_9.x86_64

Requires: libc.so.6(GLIBC_2.22)(64bit)

What versions of glibc do you have on the machine?

Looks like the package requires 2.22 now. I'm not sure when or why that requirement was introduced, will try to track that down.


Tailwindize incentive details (new calc only)

Test Plan
Flip back and forth between this and prod, making sure they're
pixel-identical. Do this at all 3 layouts (w < 640, 640 <= w < 768,
and 768 <= x).

That's pretty satisfying honestly, and I didn't think our CSS was all that bad:


SectionList misses scrollTo* methods

I'm planning to switch from ListView to SectionList, but find that I can't perform any scrollTo* methods, they are defined in VirtualizedList but not in VirtualizedSectionList. At least scrollToOffset should be implemented.
I'd like to send a PR, but I'm afraid to break the docs, and I don't know whether should we implement scrollToIndex and scrollToItem as they are different from FlatList
Perhaps a new method scrollToSection could be added too, it's a common use case in a contact list
@sahrens

Yeah I punted on this but I agree it's important. Maybe scrollToIndexInSection({sectionKey: string, index: number})?

IMO, scrollTo* is a bit complex, especially the scrollToOffset({ animated: boolean?, offset: number }), now that it receives a object, what about simplify them to a single method scrollTo(params) where the params is in a shape of { animated: boolean?, offset: number?, index: number?, item: object?, sectionKey: string? } or scrollToOffset(offset: number, animated: boolean?)
And the renderItem(info: {item: object, index: number}) -> renderItem(item: object, index: number)
Those are just some of my thoughts when I'm trying to switch from ListView to SectionList
Thanks for your great effort to create such a wonderful component

I appreciate the input, but here is the reasoning:
scrollTo* is more explicit and makes the API more clearly self documenting and simpler to flow-type, especially with composition.
renderItem(info: {...}) makes it easier to pull out just the info you care about in an order-independent way, and gives us the option value to add more data in the future in a backwards compatible way.

Has anyone started work on this? Don't want to duplicate efforts if so, otherwise I may have time to try it out. Although I'll defer to @sahrens if he already has thoughts on how to implement 😄

No one is working on it to my knowledge so a PR would be appreciated :)
Just need to figure out the right API since we need to account for sections. I'll let you take a stab at it and we can iterate in review, just cc me in the PR summary.

@jpshelley 👍

@jpshelley, can you have a look to sticky section header support too? ;)

@mediaxtend PRs get merged faster if broken into smaller 'sections', so you should probably submit a new issue for it.

Sticky headers are already in master.

@jpshelley, got it for the next time! :innocent:
@sahrens, I thought they were not because I've read:

Sticky headers are not yet supported.

(https://github.com/facebook/react-native/blob/master/Libraries/Lists/SectionList.js#L111)

If you need sticky section header support, use ListView for now.

(https://github.com/facebook/react-native/blob/master/Libraries/Lists/SectionList.js#L149)
I have to test this.

Oh ha, forgot to update that comment!

@sahrens I started a branch on this work here and wanted to get your (and others) thoughts on the API.
https://github.com/jpshelley/react-native/tree/SectionList-AddScrollToSupport
I'm basically just making a wrapper call to the underlying VirtualizedSectionList which calls the VirtualizedList. The scrollToEnd is a fairly trivial function to show the implementation, with scrollToIndexInSection a suitable next candidate to add imo and which could take a little bit more work.

Thoughts on the implementation?
Thoughts on how many methods we should add before submitting a PR (scrollToEnd, scrollToIndexInSection, etc like the FlatList)?

An internal client needed scrollToIndexAtSection support so I already added it in master (as scrollToLocation - maybe naming could be better, what do you think?). I think scrollToEnd can be done via getScrollResponder so not a big deal, but if you want to put up a PR for it I'll take a look.

We might end up using https://github.com/expo/react-native-invertible-scroll-view for our ScrollComponent for what I'm working on anyways so good timing 😄  We can ditch the branch I created in favor of yours and probably close this issue if @nihgwu agrees

The 44-th version has released but scrollTo method is not added :(
When are you going to release it?

You can browse the code by branch here: https://github.com/facebook/react-native/branches
Looks like 0.45 hasn't been cut yet, so you can look at master and see scrollToPosition has been added:
https://github.com/facebook/react-native/blob/master/Libraries/Lists/SectionList.js
So it should be in v0.45 which will ship the beginning of next month since we're on a monthly release schedule.
You can run off master if you want, just update your package.json.

Any tip on how to use it? Do you pass it as a prop to Sectionlist list. Is it like:
<SectionList scrollToEnd={{} ...props />

or as a ref?

@sahrens Thank you, I've found the method scrollToLocation, and it's working for a normal SectionList. Because I use Animated.event with nativeDriver when onScroll so I need to wrap this SectionList with createAnimatedComponent to be AnimatedSectionList. The problem appears that there's no method scrollToLocation for AnimatedSectionList. Please support this method for createAnimatedComponent(SectionList).

It's a method, so call it on the ref.
createAnimatedComponent exposes a getNode Method which provides access to scrollToLocation and any other methods on the wrapped component.

@sahrens Version 0.45 is already up and scrollToLocation is documented, but I can't really find an example. Would be awesome if you could give me an hint how can I get the index in renderSectionHeader and scroll to that section index?
Thanks in advance

@RUIFERNANDE5
how your component looks like, can you post your example of how did you get this feature working?
I am trying to get this feature working too, but I can't find any example.

@RUIFERNANDE5 I tried something similar but it doesn't scrolling to desired position
this.tableList.scrollToLocation({animated: true,sectionIndex:0, itemIndex: 5, viewPosition:0.5});
my sectionslist looks something like this
<SectionList
                  ref={(ref) => { this.tableList = ref; }}
                  renderItem={this.renderItem.bind(this)}
                  renderSectionHeader={this.renderSectionHeader.bind(this)}
                  getItemLayout={this.getItemLayout.bind(this)}
                  sections={tables}
                  stickySectionHeadersEnabled={true}
                  keyExtractor={this.keyExtractor.bind(this)}
                />

+1 for scrollTo or scrollToOffset

A workaround in the absence of these methods is to work back to the VirtualizedList and directly access them there. This requires using underscored, undocumented methods and so should only be used in a pinch.
For example:

//…

componentDidMount() {
  this.refs.list._wrapperListRef._listRef.scrollToOffset({offset: 0})
}

//…

<SectionList ref="list" {…otherProps} />

//…

+1 for scrollTo()

@RUIFERNANDE5 Maybe your getItemLayout method is not correct, you can try remove that

@manjeets12 Maybe your getItemLayout method is not correct, you can try remove that

spent days on this.
scrollToLocation does not work even with getItemLayout specified until the rendering of the list is completed. The only way I got it to work is by wrapping the scrollToLocation in a setTimeout of 10 seconds. (dev / android)
Even with a 5 second timeout, it would still only scroll partially towards the correct position.
Is there anyway to know when the list is rendered and ready ?

You could add an onLayout callback to your last item and do the scrollTo once that fires, although something else funky might be going on if a 5 second timeout doesn't work. Did you try setting initialScrollIndex?

Thanks @sahrens will give onLayout a try. though the list always initial renders as empty so onLayout will not fire again once the data is updated.
I tried initialScrollIndex and it results in only the very first section header being rendered. I tried with initialScrollIndex > 0 and it had the same result for any value I tried.. never tried with 0 though.

onLayout doesn't work.
The logs are interesting. I subscribe to an event in each list item and I log each subscription. The list size is small ~100 items. I can see that the initial viewable items render really quick ~7 items with the initial render set to 15.  I can see that onLayout fires after about 30 subscription. I trigger the scrollToLocation onLayout to the middle index (i = 50)  however it doesn't scroll to that location. Stops around the 30th.
If I wait about 5-6 seconds.. I finally see a total of 100 subscriptions logged.  So the scrollToLocation only works after componentDidMount has been applied to every single item in the list. I subscribe to the event in the componentDidMount of the list item component.

@steobrien your solution works on ios but doesn't seem to on android, at least with my preliminary testing.

Thanks @JeremyBradshaw7, I've updated the comment.


Replace create-react-app

the ui is built using create-react-app which is now dead 1 2
the react team now recommends different tools like full frameworks (next, remix) or vite. I think vite would be the best choice

I had a quick look, and I agree that Vite is probably the best choice.

I had a quick look, and I agree that Vite is probably the best choice.

There is a new project that looks promising too:
https://www.farmfe.org/
https://github.com/farm-fe/farm
If someone wants to check this out. It's fully compatible with Vite plugins also and a so much faster (as it's written in Rust). This project recently released the v1 (stable) so from now it's production ready.
@offizium-berndstorath I see you have already done the migration but if you like the idea it might be a good PR for the future ;)

@RotaN8 it indeed looks promising. maybe if it gains some tranction, but otherwise industry standards are good enough imo. vite uses esbuild (go) and swc (rust) so its plenty fast

Totally agree! Only sharing for future consideration maybe ;) Thanks for your PR btw.


userTaxFormRequiredBeforePayment should use a GraphQL loader

The places where we check if W9 tax form is required for users, in expense.userTaxFormRequiredBeforePayment (GQLV1) and expense.requiredLegalDocuments (API V2) are not using GraphQL loaders.
It's not a big deal yet because the places where we show this on lists (mainly, the host dashboard) make a single query for each expense (see https://github.com/opencollective/opencollective/issues/2519). But as we're going to revamp the host dashboard and eventually add the tags on list expenses list, it would be great to improve that.

:gift: :money_with_wings: A $200 bounty was attached to this issue. Anyone submitting a Pull Request will be rewarded with $200 when the Pull Request is reviewed, accepted and merged.
:arrow_right: More info

@Betree Taking on this

Bumped the complexity to medium and adapted the bounty

Note: with expense process actions coming to the expenses list, we'll need to add the fields on the expenses page query once we have the proper loaders to back them

:trophy: This issue has been completed by @flickz
To claim the $500 bounty, you can either:

Submit an invoice to https://opencollective.com/engineering/expenses/new (please mention the issue number)
Or ask for an Open Collective gift card of the same value (to donate to other collectives)


Add templates for Issues and Pull requests

@octobilly 100

@octobilly 1

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @xjjaid13, @ylck, @lagitany, @ieliwb, @wuyumin, @manxiaqu, @ybcan, @driftWithToyota86, @smartbigant, @Joyky

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @wzhua, @myreadlove, @valtab, @feixiao, @betterenvi, @afei101, @samniu, @Netzhangheng, @algorime-it, @XueSeason


fix: allow assets with multiple policies/contracts to be parsed/federated/contracted correctly.

WHAT
Fixes a bug related to catalogue interpretation in the agent plane
WHY
A bug appeared in the integration test when BMW assigned multiple contracts to a graph asset.
FURTHER NOTES
Closes #120

@SebastianBezold may I request your assistance/assign you to that PR?


Webpack 4: devtool: 'source-map' makes an error

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Adding devtool: 'source-map' to my config causes the error
ERROR in ./src/index.js
Module build failed: Error: Cannot find module 'source-map'
    at Function.Module._resolveFilename (module.js:543:15)
    at Function.Module._load (module.js:470:25)
    at Module.require (module.js:593:17)
    at require (/home/trusktr/Downloads/src/trusktr+infamous/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at _sourceMap (/home/trusktr/Downloads/src/trusktr+builder-js-package/node_modules/@babel/generator/lib/source-map.js:9:37)
    at SourceMap.get (/home/trusktr/Downloads/src/trusktr+builder-js-package/node_modules/@babel/generator/lib/source-map.js:32:40)
    at Object.get [as map] (/home/trusktr/Downloads/src/trusktr+builder-js-package/node_modules/@babel/generator/lib/buffer.js:58:33)
    at generateCode (/home/trusktr/Downloads/src/trusktr+builder-js-package/node_modules/@babel/core/lib/transformation/file/generate.js:101:27)
    at runSync (/home/trusktr/Downloads/src/trusktr+builder-js-package/node_modules/@babel/core/lib/transformation/index.js:48:58)
    at runAsync (/home/trusktr/Downloads/src/trusktr+builder-js-package/node_modules/@babel/core/lib/transformation/index.js:35:14)
    at /home/trusktr/Downloads/src/trusktr+builder-js-package/node_modules/@babel/core/lib/transform.js:34:34
    at process._tickCallback (internal/process/next_tick.js:112:11)

If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/trusktr/lowclass/tree/webpack-issue-7149
Check out that branch and run
npm i
./node_modules/.bin/webpack --config ./node_modules/builder-js-package/config/webpack.config.js

What is the expected behavior?
No error, with source map emitted.
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
Webpack 4.6.0
Node 9.9.0

Okay, it's working now in the reproduction, not sure what changed.


RegExp

Goja uses two regular expression libraries:

regexp
github.com/dlclark/regexp2

I found some behaviors that are inconsistent with JavaScript regular expression.
1.lastIndex > 0 with ^ assertion
In both regexp wrappers, goja simply truncates the first start UTF-16 code units and calls the matcher.
https://github.com/dop251/goja/blob/f19759604c88e17c96c01c568e10ee1e5d0912ad/regexp.go#L30-L38
https://github.com/dop251/goja/blob/f19759604c88e17c96c01c568e10ee1e5d0912ad/regexp.go#L218-L221
This makes the first character of the truncated substring always the line start:
'aaa'.match(/^a/g); // should return ['a'], actually ['a', 'a', 'a']

2. matches' index with regexp2
var re = /(?=)a/; // a hack to use regexp2
re.exec('\ud83d\ude02a').index // should return 2, actually 1

3. . in regexp
/./.exec('\ud83d\ude02')[0] // should return '\ud83d', actually '\ud83d\ude02'

Incidentally, I have been looking into this recently. Could you check this branch: https://github.com/dop251/goja/tree/regexp
It's still work in progress, but all the cases you've mentioned should work.


Care plan   arv treatment resource dev  fig 44

For the ART Regimen product, I retained the item #TDF/3TC/DTG from the HIV IG.
Use the description found in: https://en.wikipedia.org/wiki/Dolutegravir/lamivudine/tenofovir#Society_and_culture

New Branch created to updated with master


Intellisense should offer super()-calls when overwriting inherited methods

In a subclass, I can type "def so" and get an autocompletion popup offering "def some_method" with the complete signature from a parent class I inherit from. I would like these stubs to contain a super call (e.g., super(SubClass, self).some_method(argument1, argument2).
If the method should better be empty by design (not knowing whether a super call makes sense), it would be nice to be able to type "super" and get the full super call offered as IntelliSense completion.

This will be fixed in the next Pylance release (though not the old form, as we don't support Python 2).

This issue has been fixed in version 2020.12.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#2020120-2-december-2020

This is a good feature, but can this remains as an option?
Sometimes we may don't add the super call (when implementing interfaces/abstract classes, for instance)


prevent app.listen() from completing before swagger is ready

@brianparry @jlongever @dalebremner @abildw @srinia6

:+1:
Joys of a callback heavy language :-)

:+1:
Works awesome!!!

:+1:

@zyoung51's PR already resolved this by using promisfy().  https://github.com/RackHD/on-http/pull/99/files#diff-9c7deffd71e2db721d0aa18017844613R158

:+1:
:)


Use subcategories in qBittorrent for new link style

The new style of linking to tracker subdirs in linkDir can leverage the use of subcategories. I've tested this on 4.6.2 and 4.5.3 but this is supported on all versions. However only 4.6.x displays it correctly in the WebUI. Previous versions essentially treat it like separate categories.
https://github.com/cross-seed/cross-seed/blob/d28a977e4402942d3e82ffd0bdcb0e814f87c78a/src/clients/QBittorrent.ts#L301-L308
Only change required is:
category: legacyLinking ? dataCategory : ${dataCategory}/${tracker}
qBittorrent will automatically create the categories if they don't exist.
Considering this is only a visual clutter issue on older versions if they disable legacyLinking, I think it would be worth it to implement now rather than later.

My understanding is that the WebUI doesn't support subcats at all in <4.6.x qbittorrent, meaning I'm not sure this is actually utilizing subcats and not just a path with a forward slash in it.
Also, because of this it would require duplicateCategories to be made in category.cross-seed/tracker I believe....
AutoTMM is a huge hassle.

Using new system for tagging torrents.

Subcategories are just a visual feature to translate categories with / to a tree view on the UI.
This can be tested by creating a subcategory via the UI and then turning the settings off.

But the subcategory settings doesn't need to be enabled, a / in category is creating a subfolder with AutoTMM even in earlier versions, I just tested 4.3.9:

It's working at least since 2016 https://github.com/qbittorrent/qBittorrent/issues/5995
AutoTMM's only issue is that it moves files even when multiple torrents are pointing at the same file (from flat cross-seed linking) killing the other torrents, but with v6 this weakness is worked around.

But the subcategory settings doesn't need to be enabled, a / in category is creating a subfolder with AutoTMM even in earlier versions, I just tested 4.3.9:  It's working at least since 2016 qbittorrent/qBittorrent#5995

I think that's more of the fact that there is a / and its not sanitized - and just results in a child directory, not that it's exactly a sub-category.
Either way, given our tendency to emphasize the value of linking with v6, I'm not entirely sure where subcategories would come into play unless you had linking disabled.
I'm not a qbittorrent user, but would be curious what you thought the use-case would be for such a thing, especially given that they would like return with the slash (i'd assume) and then just append the normal .cross-seed? Is that the behavior you would be desiring? Or are you just commenting to clarify?

I think it's an intentional design and not the lack of sanitation, given that it is programmed to create the sub-directories as well.
It would work exactly how non-flat linking works in v6 right now, but instead of AutoTMM disabled and explicit save path defined for the tracker, it would define sub-categorizes for each tracker and would allow AutoTMM to work. Not sure if duplicateCategories should be considered with flatLinking disabled, afaik it doesn't make much sense.
But admittedly for hardlinked files the AutoTMM is not that useful, given that moving to a different drive would break the hardlinks, so I think we can consider this just a clarification.

With linking enabled duplicateCategories only affects the tags.
I'm not sure about this implementation, but it makes a bit of sense how you're describing it, however it does present the issue of users on pre 4.6 (or whenever subcats were introduced to the UI) potentially not wanting to use this.
I don't really touch qbittorrent to this respect, so it would be a team decision on whether to support it and likely something that @ShanaryS would be in charge of, given that he's the qbittorrent user on the dev team.
Curious as to what his thoughts are and any pitfalls that may come from doing things this way.

This can be done, but cross-seed will still disable autoTMM for simplicity. But lots of users won't benefit from this since it's new and lots of alternative webuis don't support it either.
It would be a cosmetic thing but the user would be able to enable autoTMM if they need it.


Enable Java Client / JobWorker Metrics

Zeebe's java-client has JobWorker metrics and explicitly enabling it on spring-zeebe
This is a first cut to introduce the JobWorker metrics.
2 JobWorker metrics are now added

zeebe.client.worker.job.activated

{
  "name": "zeebe.client.worker.job.activated",
  "measurements": [
    {
      "statistic": "COUNT",
      "value": 1
    }
  ],
  "availableTags": []
}

zeebe.client.worker.job.handled

{
  "name": "zeebe.client.worker.job.handled",
  "measurements": [
    {
      "statistic": "COUNT",
      "value": 1
    }
  ],
  "availableTags": []
}

Couple of thoughts:

I think we should use the MetricsRecorder provided by Spring Boot which is injected into this class in MeterRegistry (see MicrometerMetricsRecorder)
It looks like the Java Client added some magic around building their own MetricsRecorder, but only if Micrometer is on the classpath. I think we should avoid using this in the Spring environment alltogether.

I think therefore me might need to copy the creation of the JobWorkerMetrics class, as this seems to be required:
https://github.com/camunda/zeebe/blob/503ae8e5da9cade1a9471e436051542a0a78d0ee/clients/java/src/main/java/io/camunda/zeebe/client/impl/worker/metrics/MicrometerJobWorkerMetricsBuilderImpl.java#L44-47
In essence, this is a good example, where we replicate Spring magic in the Java client, which even can make some trouble in the spring integration now (but haven't looked at all the details).
Does this make sense?
Then I think we should adjust this - so that all Spring-zeebe uses the MeterRegistry from Spring (as people could create their own if they want - then this should be used - to stick to normal Spring principles). WDYT @1nb0und ?

Then I think we should adjust this - so that all Spring-zeebe uses the MeterRegistry from Spring (as people could create their own if they want - then this should be used - to stick to normal Spring principles). WDYT @1nb0und ?

Those are good points. It makes sense to tap into the existing metrics recorder rather. Will adjust.

Please let us know how we can make the integration with Spring easier for you. As MetricsRecorder seems to be spring-zeebe specific, maybe instead you can simply create an adapter which bridges that and JobWorkerMetrics?
Something like:
public final class MetricsRecordJobWorkerMetricsAdapter implements JobWorkerMetrics {
  private final MetricsRecorder delegate;

  public MetricsRecordJobWorkerMetricsAdapter(final MetricsRecorder delegate) {
    this.delegate = delegate;
  }

  @Override
  public void jobActivated(final int count) {
    delegate.increase("zeebe.client.worker.job", "activated", count);
  }

  @Override
  public void jobHandled(final int count) {
    delegate.increase("zeebe.client.worker.job", "handled", count);
  }
}

You can then use it:
client
  .newWorker()
  .type("type")
  .handler(...)
  .metrics(new MetricsRecordJobWorkerMetricsAdapter(metricsRecorder))
  .open();

Our metric names are actually part of the public API (MicrometerJobWorkerMetricsBuilder.Names), but unfortunately we don't split between the metric and the action, so it wouldn't work out of the box with the MetricsRecord API.

Ok I'm understanding the problem space now. What was happening previously was since zeebe-client didnt have any metrics implementation, it was spring-zeebe who provided it via the MetricsRecorder. Now that the zeebe-client implemented it, I would need to reconcile the two and ensure its done in a clean manner.
Thank you both for your insights.

We are now passing metrics from zeebe-client to spring-zeebe thru a bridge class. Also this ensures the creation of metrics in Spring will be in a single place at MetricsRecorder.
Looking in the future for multiple clients like Operate and TaskList, if they have metrics to be exposed, then there will be multiple bridges/adapters which all gets translated in MetricsRecorder


#315: Single line comments can terminate with EOF

Resolves #315.

:+1:

:+1:

Thanks for the prompt fix!


I have an one line text image.I want to split word by word. Can anyone help me

This template is for miscellaneous issues not covered by the other issue categories.
For questions on how to work with TensorFlow, or support for problems that are not verified bugs in TensorFlow, please go to StackOverflow.
If you are reporting a vulnerability, please use the dedicated reporting process.
For high-level discussions about TensorFlow, please post to<EMAIL_ADDRESS>for questions about the development or internal workings of TensorFlow, or if you would like to know how to contribute to TensorFlow, please post to<EMAIL_ADDRESS>

This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.


fix(forge): ensure contract managing fork is  persistent

Motivation
Fixes #8004
Test contract that manage forks (create / select / roll) should be made persistent, otherwise their state can be lost

Solution

ensure caller is persistent for create, select and roll fork cheatcodes

I think we can do this in Backend::select_fork instead? It already has some similar logic

The problem with this approach is that we don't have the original msg.sender from cheat context available in Backend::select_fork/roll_fork - we can add it as an additional param but I don't think we should mix them, wdyt?

I think we can do this in Backend::select_fork instead? It already has some similar logic

The problem with this approach is that we don't have the original msg.sender from cheat context available in Backend::select_fork/roll_fork - we can add it as an additional param but I don't think we should mix them, wdyt?

Also important to note that this does not resolve this issue for some weird cases when forks are switched deep in call stack, but I don't think this can be solved without separately tracking call stack

Yep, the scope of this PR is to make sure test contracts that use fork cheatcodes are persistent, see https://github.com/foundry-rs/foundry/issues/8004#issuecomment-2135568075

I think we can do this in Backend::select_fork instead? It already has some similar logic
The problem with this approach is that we don't have the original msg.sender from cheat context available in
Backend::select_fork/roll_fork - we can add it as an additional param but I don't think we should mix them, wdyt?

Right, I think we can keep it as is for now
I just don't want persist_caller to become the new correct_sender_nonce which ended up in many random places and caused weird bugs. But persist_caller usecase seem pretty narrow so it's probably fine


Scp

Codecov Report

Merging #2660 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #2660   +/-   ##
=======================================
  Coverage   94.38%   94.38%
=======================================
  Files         166      166
  Lines       19563    19563
=======================================
  Hits        18465    18465
  Misses       1098     1098

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 28e897e...5d605d0. Read the comment docs.

Thanks!!


Consider implementing Ord for all types

This is fun issue. In rust-analyzer, we observed a couple of crashes with experimental proc-macro support enabled. Investigation showed that the root cause here is a non-determenistic derive-more proc macro -- rust-analyzer's incremental computation framework assumes that everything is pure and just dies in flames if it is not the case.
The non-determinism in derive-more was due to the usage of std::collection::HashMap, which is not something syn can help with. However, a trivial fix of using BTreeMap instead of HashMap didn't work, because not everything is Ord, and so a more involved fix with a custom hasher was implemented: https://github.com/JelteF/derive_more/issues/124#issuecomment-624843857
I wonder if it makes sense for syn to provide Ord impls, so that obvious way to make stuff deterministic just works?

This would probably be a big performance hit - nondeterministic proc macros because of HashMaps should use deterministic hashers.
(It's actually amazing that rust-analyzer is catching these cases).

This would probably be a big performance hit

Not sure -- I think time to expand proc macros is usually not that important? I haven't measured this, but my gut feeling is that the impact of proc-macro itself is usually dwarfed by the time to compile the macro itself + the time to compile the code, generated by macro. So, I'd say "when writing proc macros, use BTreeMap" is a sound advice. It also has a minor benefit that the output is sorted naturally, and not pseudo random, which helps when you look at the output of proc macros.

It's actually amazing that rust-analyzer is catching these cases

Kudos to @edwin0cheng for connected the dots on this one. The original crash was quite bewildering and not obviously connected to non-determinism somewhere deep inside proc macro. To clarify, we already "fixed" the issue on rust-analyzer's side by making sure that we never GC expansions from proc-macros, though, long-term, I hope we'll have deterministic-by-construction proc macros in the future, via wasm.

Not sure -- I think time to expand proc macros is usually not that important?

Er, sorry, I meant a performance hit on compile times for syn to implement these traits. syn already has a feature extra-traits which has "Debug, Eq, PartialEq, Hash impls for all syntax tree types.". I guess adding Ord to that wouldn't necessarily be bad, but would likely increase compiletimes quite a bit I imagine.

Although it is not directly related to syn crate, But I would like to point out that, as mention by @bjorn3 in the original RA issue, one of the problems of non-deterministic build in proc-macro is,  crates using it have non reproducible builds. And it is very hard to find out.

I think I would prefer not to do this, and instead recommend a deterministic hasher as the recommended approach.


Feature: programmatically decrease heading levels within the editor.

I'm working on re-using Lexical for both - using it for a naive page builder as well as offering users to create their own blog posts.
It would be nice if Lexical had some prop that would control the heading levels (their tags). For example, a prop decreaseHeadingBy (or something less verbose) could take in an integer that would then reduce the heading level of the one that user inputs by the provided amount.
Example usage:
const initialConfig = {
    editorState: emptyEditor ? undefined : undefined,
    nodes: [...Nodes],
    // ....
    decreaseHeadingBy: 1
  };

And the above would result in:

Heading 2, when user selects Heading 1
Heading 3, when user selects Heading 2
etc ...

# Why?
This would be nice for SEO and Lighthouse, since if a platform developer creates layout with Heading as <h1 /> baked into the design and then user adds another Heading 1 in their article (not perhaps knowing the ins and outs of SEO best practices), the page would result in 2 <h1 /> headings.

You should be able to achieve this without a configuration option. Can you just prevent the user from inserting H1s in cases where they shouldn't? Alternatively, you could have a transform that adjusts the level of HeadingNodes. Mutation listeners might also work for this case.

@acywatson thank you for the suggestions, that's awesome. I will look into those options, but - before I do (or after I do, not the point, haha) - I would love to argue that this type of functionality could potentially be easy to add to the core features for folks who are well-versed in the ins and outs of Lexical transformations/mutation listeners, while at the same time it could be quite tedious and time consuming for those who are new to Lexical and Rich Text editors in general.
Additionally, I would argue that this functionality could be quite useful to many, what do you think? All above mere thoughts... :)

It's probably true that it'd be easier for us to do, but we created the plugin system because we wanted to library to be extensible for use cases like this without us having to develop and maintain an API for every imaginable use case. In this instance, a plugin could be as simple as:
export function MaxHeadingPlugin(props: { maxHeadingLevel: 1 | 2 | 3 | 4 | 5 }) {
  registerNodeTransform(HeadingNode, (node) => {
   const level = parseInt(node.getTag()[1]);
    if (level > maxHeadingLevel) {
      node.setTag(`h${maxHeadingLevel}`);
    }
  })
}

<LexicalComposer>
  <MaxHeadingPlugin maxHeadingLevel={2}
</LexicalComposer>

Not that hard to write, but then when people start using it and asking for small changes to it and asking questions about why it works this way or why it doesn't work that way, it becomes more of a burden.  That's why we encourage people to do these things on their own unless they serve a pretty broad use case.

I'm gonna close this one for now - appreciate the feedback and ideas!

Hey @acywatson sorry missed the reply : )
Thanks so much for clarifying and the snippet, pretty neat!
The reasoning is quite understandable too and makes sense, thanks again!


Showing the sessionizer doesn't work after adding a path

I copied the config, but when i add the path
/home/user/repos
Then the hotkey for showing the sessionizer doesn't work anymore.
i have fd version 10.2.0

Okay, thank you for opening the issue I will look into it later today.

Can you try putting sessionizer.apply_to_config(config) below your config.keys = { ... } and remove any other calls to the function. If you have this already and it does not work it would be helpful if you could send a config in which the problem occurs, thank you

That didnt work unfortunately...
Here is my config
-- Pull the wezterm api
local wezterm = require("wezterm")
local act = wezterm.action
local mux = wezterm.mux

-- This table holds configuration
local config = {}

-- Better error messages by using the config builder
if wezterm.config_builder then
	config = wezterm.config_builder()
end

--------------------
-- STARTUP CONFIG --
--------------------

local is_linux <const> = wezterm.target_triple:find("linux") ~= nil

if not is_linux then
	config.default_domain = "WSL:Ubuntu"
	wsl_domains = {
		{
			name = "WSL:Ubuntu-22.04",
			distribution = "Ubuntu-22.04",
			default_cwd = "/home/sondrejk",
		},
	}
else
	config.default_domain = "local"
end

------------------------
-- APPEARANCE CONFIGS --
------------------------

config.font = wezterm.font("JetBrains Mono")
config.color_scheme = "GruvboxDark"

----------
-- TABS --
----------

local function get_current_working_dir(tab)
	local current_dir = tab.active_pane and tab.active_pane.current_working_dir or { file_path = "" }
	local HOME_DIR = string.format("file://%s", os.getenv("HOME"))

	return current_dir == HOME_DIR and "." or string.gsub(current_dir.file_path, "(.*[/\\])(.*)", "%2")
end

-- tab title
wezterm.on("format-tab-title", function(tab, tabs, panes, config, hover, max_width)
	local has_unseen_output = false
	if not tab.is_active then
		for _, pane in ipairs(tab.panes) do
			if pane.has_unseen_output then
				has_unseen_output = true
				break
			end
		end
	end

	local cwd = wezterm.format({
		{ Attribute = { Intensity = "Bold" } },
		{ Text = get_current_working_dir(tab) },
	})

	local title = string.format(" [%s] %s", tab.tab_index + 1, cwd)

	if has_unseen_output then
		return {
			{ Foreground = { Color = "#8866bb" } },
			{ Text = title },
		}
	end

	return {
		{ Text = title },
	}
end)

--------------
-- VIM MODE --
--------------

-- WIP

----------------
-- WORKSPACES --
----------------

-- load plugin
local workspace_switcher = wezterm.plugin.require("https://github.com/MLFlexer/smart_workspace_switcher.wezterm")
config.default_workspace = "~/repos"

local sessionizer = wezterm.plugin.require("https://github.com/mikkasendke/sessionizer.wezterm")
sessionizer.config = {
	paths = {
		"/home/sondrejk/repos/",
	},
}

-------------
-- KEYMAPS --
-------------

-- timeout_milliseconds defaults to 1000 and can be omitted
config.leader = { key = "a", mods = "CTRL", timeout_milliseconds = 1000 }
config.keys = {

	-- Making panes and exiting them
	{ key = "v", mods = "LEADER", action = wezterm.action.SplitHorizontal({ domain = "CurrentPaneDomain" }) },
	{ key = "h", mods = "LEADER", action = wezterm.action.SplitVertical({ domain = "CurrentPaneDomain" }) },
	{ key = "q", mods = "LEADER", action = wezterm.action.CloseCurrentPane({ confirm = false }) },

	-- Tabs
	{ key = "t", mods = "LEADER", action = act.SpawnTab("DefaultDomain") },

	-- Send "CTRL-A" to the terminal when pressing CTRL-A, CTRL-A
	{ key = "a", mods = "LEADER", action = wezterm.action.SendKey({ key = "a", mods = "CTRL" }) },

	-- Navigation and resizing panes using hjkl
	{ key = "h", mods = "SHIFT|CTRL", action = act.ActivatePaneDirection("Left") },
	{ key = "h", mods = "SHIFT|ALT|CTRL", action = act.AdjustPaneSize({ "Left", 10 }) },
	{ key = "l", mods = "SHIFT|CTRL", action = act.ActivatePaneDirection("Right") },
	{ key = "l", mods = "SHIFT|ALT|CTRL", action = act.AdjustPaneSize({ "Right", 10 }) },
	{ key = "k", mods = "SHIFT|CTRL", action = act.ActivatePaneDirection("Up") },
	{ key = "k", mods = "SHIFT|ALT|CTRL", action = act.AdjustPaneSize({ "Up", 10 }) },
	{ key = "j", mods = "SHIFT|CTRL", action = act.ActivatePaneDirection("Down") },
	{ key = "j", mods = "SHIFT|ALT|CTRL", action = act.AdjustPaneSize({ "Down", 10 }) },

	-- Navigating tabs
	{ key = "h", mods = "SHIFT|ALT", action = act.ActivateTabRelative(-1) },
	{ key = "l", mods = "SHIFT|ALT", action = act.ActivateTabRelative(1) },

	-- Workspace hotkeys
	{ key = "d", mods = "LEADER", action = act.SwitchToWorkspace({ name = "dotfiles" }) },
	{ key = "s", mods = "LEADER", action = workspace_switcher.switch_workspace() },
	{ key = "f", mods = "LEADER", action = sessionizer.show },
}

sessionizer.apply_to_config(config, true)
return config

oh yeah removing the , true from sessionizer.apply_to_config(config, true) so it's just sessionizer.apply_to_config(config) should fix it (the true is to disable default binds). There will be a big change coming soon though which might also alter this but I'll try to stay backwards compatible and you'd have to manually update anyway so yeah

Oh okay, unfortunately I can not replicate this, but it might be that it fails to run fd this happened to someone before, to be sure you could look at the debug overlay (ctrl+shift+p) the error message is something like no such file or directory (os error 2). If it is this you can run which fd in your terminal and put the path in here:
sessionizer.config = {
    paths = {
        "/home/sondrejk/repos/",
    },
    command_options = {
        fd_path = -- here your fd path
    }
}

there is an update coming soon though which will fix such things

it should at least fail in the scope where we run fd

Sorry for the late reply!
I did as you suggested and got this:
> sessionizer.show
runtime error: [string "repl"]:1: attempt to index a nil value (global 'sessionizer')
stack traceback:
        [string "repl"]:1: in main chunk
12:15:49.670 ERROR wezterm_gui::termwindow > while processing user-defined-0 event: No such file or directory (os error 2)
stack traceback:
        [C]: in local 'poll'
        [string "?"]:4: in function 'wezterm.run_child_process'
        ...esZssessionizersDswezterm/plugin/sessionizer/entries.lua:70: in upvalue 'apply_commands'
        ...esZssessionizersDswezterm/plugin/sessionizer/entries.lua:90: in function 'sessionizer.entries.get_entries'
        ...omsZsmikkasendkesZssessionizersDswezterm/plugin/init.lua:21: in function <...omsZsmikkasendkesZssessionizersDswezterm/plugin/init.lua:19>

I did which fd and got this path:
/home/linuxbrew/.linuxbrew/bin/fd
Added this to my config:
sessionizer.config = {
  paths = {
    "/home/sondrejk/repos/",
  },
  command_options = {
    fd_path = "/home/linuxbrew/.linuxbrew/bin/fd",
  },
}

And yet it still doesn't work...

@sondrejk no problem. This is a bit weird, it definitely fails to find the fd binary, [string "?"]:4: in function 'wezterm.run_child_process' and with the correct absolute path it should be able to find it. Now there are two options for what it could be either the fd_path option is not present in your local version (it was added a while ago) or there is some kind of permission issue. What @itsisak said would probably fix both (but it is not the cleanest solution), but what also might fix it (if it only is because the option is not present) is updating the plugin. There is require "wezterm".plugin.update_all() but to me the easiest was just deleting ~/.local/share/wezterm/plugins/httpssCssZssZsgithubsDscomsZsmikkasendkesZssessionizersDswezterm which is where wezterm automatically downloads the plugin (idk if the last directory is always the same but it should be similar). Thanks for your patience

@mikkasendke Deleting this folder worked! However the ~/.local/share/wezterm/plugins/ did not exist for me (on mac), but I found the corresponing folder at ~/Library/Application Support/wezterm/plugins/httpssCssZssZsgithubsDscomsZsmikkasendkesZssessionizersDswezterm. Perhaps this is an issue for plugins on macs in general and not only this one.


Prevent creating a duplicate report when uploading attachment

When we upload the attachment in the report form and then save the report, 2 report forms are created and the attachment is related to the first created report.
Closes AB#902
User changes

When users add an attachment, the report form will be automatically saved and related to the attachment and they can see uploaded attachment on report page.

Superuser changes

None

Admin changes

None

System admin changes

[ ] anet.yml or anet-dictionary.yml needs change
[ ] db needs migration
[ ] documentation has changed
[ ] graphql schema has changed

Checklist

[x] Described the user behavior in PR body
[x] Referenced/updated all related issues
[x] commits follow a repo#issue: Title title format and these 7 rules
[x] commits have a clean history, otherwise PR may be squash-merged
[ ] Added and/or updated unit tests
[ ] Added and/or updated e2e tests
[ ] Added and/or updated data migrations
[ ] Updated documentation
[ ] Resolved all build errors and warnings
[ ] Opened debt issues for anything not resolved here

Obsoleted by #4445.


BoxShadow not working on android phones

Description
BoxShadow not working on on HUAWEI P20 pro  and RedMi.
Expecting:

Result:

Environment
Weex SDK Version: 0.18.0-beta-3
JS Framework Version: 0.24.5
platform: android
osVersion: 8.1.0
appGroup: WXApp
appName: WXSample
appVersion: 0.18.0-beta-3
deviceModel: CLT-AL01
deviceWidth: 1080
deviceHeight: 2240
Update: Here is another Android phone which also has the same issue ——

Broken Example
Following URL is copied from official playground demo:
dotwe.org/vue/190d8baf578fb7b4efd82f19322a69da
Steps to Reproduce

Download latest playground app from https://weex.apache.org/tools/playground.html.

Follow one of these steps:

Exampels > Others > Basic Styles > Box Shaow
Exampels > Others > Basic Styles > Watermelon
Exampels > Others > Basic Styles > Psudo-classes

There many box-shadow problem, we will look into it when available. Not sure when we will solve the problem.

#1720
#1988

As described in the document, box-shadow is not supported on Android anymore.
The implement of box-shadow relies on a bug of Android, which is fixed by Google. It's time to say goodbye to box-shadow.


Demiurge Wallet - New demiurge account not getting created correctly if relevant tab is closed

Version: v1.3.1
Environment: local
Steps to Reproduce:

Open localhost:8080 and click on Demiurge Wallet
Create new account
Login with new account credentials (e.g. username: newAdmin)
Click on 'Create Identity' followed by 'Save Identity'
Copy the DID and close the tab
Goto homepage again and click on Demiurge Wallet
Login with existing user credentials
Add the DID to the ePI Admin Group
Login again with username: newAdmin
Click on Groups

The page keeps on loading forever as shown below:

Facing same issue even in the very first login continuing with the same tab.

Open Demiurge Wallet (HTTPs URL)
Create new account
Login with new account credentials
Click on 'Create Identity' followed by 'Save Identity'
Get the dashboard loaded
Click on Groups
Click on "ePI Write Group"


About the size of base graph

Thank you for your work. I want to ask why do you change the size of base graph, and why the sizes of base graphs are different in the training and testing?

Hi,
Thanks for your interests. In Section 3.1 of our paper, we stated that "Besides, we include graphs with large bases to further magnify the distribution gaps". This is also following https://arxiv.org/abs/1905.02850 since we are also interested whether the GNNs can generalize to larger graphs.

Thank you for your reply which addresses my questions.


update tslint with eslint and typescript-eslint

Because TSLint is deprecated, I changed the docs to point to ESLint with an additional note of the TypeScript ESlint libray.

Learn Build status updates of commit bf61dac:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error: download-failed] Download failed for file 'https://ops/buildconfig/?name=azure-documents&locale=en-us&repository_url=https://github.com/MicrosoftDocs/azure-docs&publish_repository_url=https://github.com/MicrosoftDocs/azure-docs-pr&branch=main&xref_endpoint=&xref_query_tags=/dotnet,/python'. Try closing and reopening the PR. If you get this Error again, file an issue.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit bf61dac:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error: download-failed] Download failed for file 'https://ops/buildconfig/?name=azure-documents&locale=en-us&repository_url=https://github.com/MicrosoftDocs/azure-docs&publish_repository_url=https://github.com/MicrosoftDocs/azure-docs-pr&branch=main&xref_endpoint=&xref_query_tags=/dotnet,/python'. Try closing and reopening the PR. If you get this Error again, file an issue.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Close/reopen to clear validation error.

Learn Build status updates of commit bf61dac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/security/develop/security-code-analysis-overview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


GCDAsyncUdpSocket sendto error = EINPROGRESS

I've been digging through the code and this part feels off.
Around GCDAsyncUdpSocket.m:4200 it is checking if the result < 0 and marking it as a failure.  But if I look at the error number, it is 36, and that is EINPROGRESS.  What should actually happen at this point?  Should it treat it as success?
if (result == 0) 	{ 		waitingForSocket = YES; 	} 	else if (result < 0) 	{         int errorCode = EINPROGRESS; 		if (errorCode == EAGAIN) 			waitingForSocket = YES;         else if (errorCode == EINPROGRESS || errorCode == EALREADY) {             // Just let it through         } 		else 			socketError = [self errnoErrorWithReason:@"Error in send() function."]; 	}

Actually, just noticed I had an error, the errno is actually 65 EHOSTUNREACH.
Now why is EHOSTUNREACH being returned?

GCDAsyncUdpSocket is a dependency. You might have better luck asking there.
No route to host is likely going to be because you don't have the Multicast Entitlement. This is certainly why requests fail in iOS 14.5 or above. We requested that entitlement and added it to our project and now requests work again.


"Cannot read property 'match' of undefined" on ng serve --c local after updating to 6.0.8

- [ x ] bug report -> please search issues before submitting
- [ ] feature request

Versions
Angular CLI: 6.0.8
Node: 8.9.0
OS: darwin x64
Angular: 6.0.7
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router, upgrade

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.0.10
@angular-devkit/build-optimizer   0.4.9
@angular-devkit/core              0.4.9
@angular-devkit/schematics        0.4.9
@angular/cdk                      6.3.1
@angular/cli                      6.0.8
@angular/material                 6.3.1
@ngtools/json-schema              1.1.0
@ngtools/webpack                  6.0.0-beta.9
@schematics/angular               0.4.9
@schematics/package-update        0.4.9
@schematics/update                0.6.8
rxjs                              6.2.1
typescript                        2.7.2
webpack                           4.14.0

Repro steps

update angular/cli 1.7.3 to 6.0.8
Run ng build -c local

configuration of my angular.json
"configurations": {
            "local": {
              "fileReplacements": [
                {
                  "from": "src/environments/environment.local.ts",
                  "to": "dist/environments/environment.local.ts"
                }
              ]
            },
            "dev": {
              "fileReplacements": [
                {
                  "from": "src/environments/environment.ts",
                  "to": "dist/environments/environment.ts"
                }
              ]
            },
            "production": {
              "optimization": true,
              "outputHashing": "all",
              "sourceMap": false,
              "extractCss": true,
              "namedChunks": false,
              "aot": true,
              "extractLicenses": true,
              "vendorChunk": false,
              "buildOptimizer": true,
              "fileReplacements": [
                {
                  "from": "src/environments/environment.prod.ts",
                  "to": "dist/environments/environment.prod.ts"
                }
              ]
            }
          }

The log given by the failure
Cannot read property 'match' of undefined
TypeError: Cannot read property 'match' of undefined
    at Object.normalize (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/core/src/virtual-fs/path.js:178:14)
    at options.fileReplacements.forEach (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/src/browser/index.js:99:55)
    at Array.forEach (<anonymous>)
    at BrowserBuilder.buildWebpackConfig (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/src/browser/index.js:98:34)
    at Observable.rxjs_1.Observable.obs [as _subscribe] (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/src/dev-server/index.js:36:50)
    at Observable._trySubscribe (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/Observable.js:43:25)
    at Observable.subscribe (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/Observable.js:29:22)
    at /Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/util/subscribeTo.js:22:31
    at Object.subscribeToResult (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/util/subscribeToResult.js:7:45)
    at MergeMapSubscriber._innerSub (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/mergeMap.js:75:38)
    at MergeMapSubscriber._tryNext (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/mergeMap.js:72:14)
    at MergeMapSubscriber._next (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/mergeMap.js:55:18)
    at MergeMapSubscriber.Subscriber.next (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/Subscriber.js:64:18)
    at MergeMapSubscriber.notifyNext (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/mergeMap.js:84:26)
    at InnerSubscriber._next (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/InnerSubscriber.js:25:21)
    at InnerSubscriber.Subscriber.next (/Users/komuro-m1/workspace/vagrant_work/apps/angular/potaufeu2/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/Subscriber.js:64:18)

Mention any other details that might be useful
ng serve : no error
 ng serve -c local : error
ng build --prod error ( same error )

Sorry, I resolved it. It seem to cause of version missmatch. I run command ng new and confirmed versions bellow.
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        0.6.8
@angular/cli                      6.0.8
@angular/material                 6.3.2
@ngtools/webpack                  6.0.8
@schematics/angular               0.6.8
@schematics/update                0.6.8
rxjs                              6.2.1
typescript                        2.7.2
webpack                           4.8.3

I run npm install and install same version with above in my project, so ng serve command become has no errors.
So, I close this issue.


v6 issue with styling introduced built-in formly-group element

Question
The new v6 introduces a formly-field and a form-group as per link below
https://formly.dev/docs/guide/migration#10-formly-root-field
How do I apply a css class to the shown element?

@gkamperis Did you find any solution for this?


[4DVolume] put back the scalar test

From this issue https://github.com/Inria-Asclepios/medInria-public/issues/385
Put back the original if condition which was in the function before https://github.com/Inria-Asclepios/medInria-public/pull/338 in order to visualize 4D images.

@fcollot it's needed for the release


Fix SCCP use list update for op3

There's a typo: op2 was checked twice but op1 was not checked.
Found using static analysis.

I used PVS studio for this one. It is available for free to use for open source software.


feat: update golang-github-youmark-pkcs8 to 1.1

Go package to parse and convert private keys in PKCS#8 format (library)
Issue: https://github.com/deepin-community/sig-deepin-sysdev-team/issues/552
Log: update repo

/lgtm
/approve


Use Gnosis instead of GnosisChain logo

Align with branding guidelines (and long-term goal of just branding as Gnosis)

@dan-gnosis Excuse my ignorance here, but is the thinking here that the docs site represents everything have to do with Gnosis in general vs GnosisChain in specific?


Add Ctrl_pad

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.
If you're unsure about the format, make sure to check out the Orpheuspad example and follow the format there.
If this PR isn't a submission, that's okay too! If there's anything about this PR template that seems confusing, let me know in #hackpad on the slack!

Hey! Super clean design, but the LCD doesn't seem to be fully connected! (see below) if this is a mistake on my end, let me know and you'll be approved :)

I think I used the wrong footprint for this one, gonna update everything to match with the 4 pin version.

Hey, just updated the case files and the PCB! If I missed anything feel free to ask, thanks!

Good stuff! Everything looks great. Get your hackpad here: https://forms.hackclub.com/hackpad


Vim9: "++name" cannot be followed by another command separated with bar

Describe the bug
In Vim9 script, ++name cannot be followed by another command, separated with a bar.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    var name = 123
    ++name | echo name
EOF
)

E1022 is raised:
E1022: Type or initialization required

Expected behavior
No error is raised; 124 is echo'ed.
Environment

Vim version: 8.2 Included patches: 1-3039
OS: Ubuntu 20.04.2 LTS
Terminal: XTerm(353)

Additional context
If this is working as intended, then:

the error message should be more clear
the limitation should be documented in the help

Regarding 1., I don't understand why Vim complains about a missing type/initialization.  This makes sense when we run something like:
vim9script
var name

E1022: Type or initialization required

But that's not what we're doing here.  Neither ++name nor echo name are declaring a variable.

In Vim9 script, ++name cannot be followed by another command, separated with a bar.

But it can be preceded by another command separated with a bar:
vim9script
var name = 123 | ++name
echo name

124