Add OrchestrationStack.process_tasks

This enables direct retirement of a stack from UI.
the retirement spec test is directly modified from service retirement spec.

I have done the refactoring by extracting common logic from vm_or_template, service, orchestration_stack, and configuration_manager_foreman into the new mixin ProcessTasksMixin.

@Fryguy I did not change the existing logic if I did not have to. What you commented make sense. This new version now returns newly created task objects.

@bzwei Looking good!  I guess my only other question is if you know which methods should be public vs private.  If you can mark the private methods in the mixin, this will make the API much clearer.


fix: dotall flag not supported in firefox

Addresses https://github.com/freeCodeCamp/freeCodeCamp/pull/38546#issuecomment-625611675 where it's pointed out that Firefox doesn't support the /s regex flag yet. This workaround matches anything that's not blank.
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #38767

@cmccormack I've confirmed the fix works on my version of Firefox.  If you've got a moment, could you merge if it works for you?

@ojeytonwilliams I am no longer authorized to merge pull requests it seems... maybe @moT01 can help.

Oh, I thought you'd be able to.  Sorry about that!
Anyway, the main thing was to check that the problem was fixed, so it's all good.

Sorry @ojeytonwilliams and @cmccormack, I'm just seeing these comments now. Thank you for confirming this works in different browsers and for the merge.
Also thanks for your original fix @ojeytonwilliams. I definitely would prefer to use the /s flag like you did originally. Hopefully it's supported in Firefox soon.


Semantic token tests on Windows don’t report stdlib declarations as defaultLibrary

I needed to disable quite a few SemanticTokenTests because stdlib symbols are not correctly reported as defaultLibrary on Windows. Investigate why.

Synced to Apple’s issue tracker as rdar://138210224


Feat: add raft config parameters disable_proposal_forwarding

Is your feature request related to a problem? Please describe.
etcd raft provides a config param DisableProposalForwarding which is useful in case the computation to create proposal must be performed on leader node before added to raft log and replicated.
Describe the solution you'd like

Add a configuration option disable_proposal_forwarding with default value is false.

pub struct Config {
    ...
    pub disable_proposal_forwarding: bool,
    ...
}

In step_follower, forward a proposal if there is a valid leader and disable_proposal_forward = false, otherwise return Error::ProposalDropped.

Describe alternatives you've considered
Additional context

Do you want to implement this feature?

Do you want to implement this feature?

yes, I can. Please, assign for this feature.

Thanks!


Server() function doesn't return when using both user:password and proxies

My company server connects to internet through http proxy: <IP_ADDRESS>:3128
I'm trying to feed data from limo
When I try it with curl command, it works:
curl -x http://<IP_ADDRESS>:3128 --user guest:guest -k https://limo.anomali.com/api/v1/taxii2/taxii/

{"api_roots": ["https://limo.anomali.com/api/v1/taxii2/feeds/", "https://limo.anomali.com/api/v1/taxii2/trusted_circles/", "https://limo.anomali.com/api/v1/taxii2/search_filters/"], "contact"<EMAIL_ADDRESS>"default": "https://limo.anomali.com/api/v1/taxii2/feeds/", "description": "TAXII 2.0 Server (guest)", "title": "ThreatStream Taxii 2.0 Server"}

But when I use cti-taxii-client, it doesn't return anything.
api_user = "guest"
api_password = "guest"
taxii_domain = "https://limo.anomali.com/api/v1/taxii2/taxii"
proxy = "<IP_ADDRESS>:3128"
proxies = {
            'http': proxy
        }
        http_conn = _HTTPConnection(proxies=proxies, user=api_user, password=api_password, verify=False)
        server_discovery = Server(url=taxii_domain, conn=http_conn)

What am I doing wrong here? Please help. Thank you!

I was unable to reproduce your issue, but do you need to add http:// to the proxy variable? Another thing you could try is setting the HTTP_PROXY environment variable. We pass the proxies argument to requests.session, so its documentation on proxies applies here too.

Hi clenk,
My code here:
from taxii2client import Server
from taxii2client import Collection, _HTTPConnection

def get_collection_threat_intelligence():
    # request to taxii server
    api_user = "guest"
    api_password = "guest"
    taxii_domain = "https://limo.anomali.com/api/v1/taxii2/taxii/"
    proxy = "http://<IP_ADDRESS>:3128"
    proxies = {
        'http': proxy,
        'https': proxy
    }
    http_conn = _HTTPConnection(proxies=proxies, user=api_user, password=api_password, verify=False)
    server_discovery = Server(url=taxii_domain, conn=http_conn)
    # get api_root
    api_root = server_discovery.api_roots[0]
    # get collections
    print(api_root.collections)
    data = []
    for collection in api_root.collections:
        if collection.can_read:
            temp = {
                'id': collection.id,
                'title': collection.title
            }
            data.append(temp)
    # return collections
    result = {
        'data': data
    }
    return result

if __name__ == "__main__":
    result = get_collection_threat_intelligence()

When I debug to this line print(api_root.collections), it runs forever and never returns anything.
Again, curl works fine.
curl --user guest:guest -k -x http://<IP_ADDRESS>:3128 https://limo.anomali.com/api/v1/taxii2/feeds/collections/

@thangld322, the reason why your request fails in print(api_root.collections) is because ApiRoot objects are creating new Sessions that do not contain the proxies. What I could do is expose the proxies to Server and ApiRoot.
After that is done, you could do the following:
from taxii2client import Server
from taxii2client import Collection, _HTTPConnection

def get_collection_threat_intelligence():
    # request to taxii server
    api_user = "guest"
    api_password = "guest"
    taxii_domain = "https://limo.anomali.com/api/v1/taxii2/taxii/"
    proxy = "http://<IP_ADDRESS>:3128"
    proxies = {
        'http': proxy,
        'https': proxy
    }
    server_discovery = Server(url=taxii_domain, proxies=proxies, user=api_user, password=api_password, verify=False)
    # get api_root
    api_root = server_discovery.api_roots[0]
    # get collections
    print(api_root.collections)
    data = []
    for collection in api_root.collections:
        if collection.can_read:
            temp = {
                'id': collection.id,
                'title': collection.title
            }
            data.append(temp)
    # return collections
    result = {
        'data': data
    }
    return result

if __name__ == "__main__":
    result = get_collection_threat_intelligence()

Note that there is an ongoing issue related to how this should be done in #37. For now, I think we are ok with this change, but it is something that could change in the future as we shape the API.


Make bee start and bee.service run by default without errors

Summary
After a fresh install, starting a bee node automatically as a service or manually with bee start results in a vague error message and a process exit. This is a huge obstacle from a DevRel perspective for developer adoption. The default configuration (or/and config parameter values) should be modified to ensure that the bee node runs without exit errors.
Motivation
Most developers who set out to install and run bee for the first time are faced with an error that is not too obvious how to fix.
This also severely impacts developer adoption from a DevRel perspective.
Running bee start after a fresh install should just work! It should not throw errors or expect dapp developers to rely on documentation to figure out what the error message means.
In a fresh machine with no prior installs:
wget https://github.com/ethersphere/bee/releases/download/v1.11.1/bee_1.11.1_amd64.deb
sudo dpkg -i bee_1.11.1_amd64.deb

# not really needed as bee.service wont start the node anyway
sudo systemctl stop bee

# start bee manually using default configuration
bee start

Implementation
Two possible ways to do this (maybe there are other ways to do this):

Change the default value of blockchain-rpc-endpoint from "" to "https://xdai.fairdatasociety.org/" (as is the case for Swarm Desktop)
Change the default value of swap-enable from true to false  (default start as Ultra Light Node) Probably not the best option

Drawbacks
There might be historical reasons for this, but I can't see any problems with this proposal.

Swarm Desktop starts with swap-enable: false. I advise against implementation 1., as the end user would immediately have to supply xDAI to the node, otherwise it is also an error.

really good idea to review this, thanks for the initiative @rampall, i concur with @Cafe137 - then the user can be directed to find the eth address, fund the node and then convert to light/full

i mentioned it as "Two possible ways", however i see  Swarm Desktop sets both of those parameters in its default (ultra-light mode) configuration :

swap-enable to false
blockchain-rpc-endpoint to a valid url (unless there is the risk of ddosing it)

In the desktop app the decision was made to set the blockchain-rpc-endpoint to a known, reliable public RPC endpoint because a light node in general only accesses it as an effect of a user initiated action from the UI and if there is a problem with it, it can be reported back to the user and worst case scenario the user can change the RPC endpoint to a working one.
This is very different in a case of a full node. It runs in the background and there is a constant communication with the smart contracts, and often this is critical from an operational perspective. For example if a node fails to follow the steps in the protocol defined by the redistribution smart contract, it can be punished (currently with freezing, later with slashing the stakes). So it is imperative that the RPC endpoint is reliable and the node operators are aware of the consequences of choosing an RPC endpoint. This is why currently the documentation recommends the node operators to run their own RPC endpoints as well.
Another important aspect is decentralisation. If there is a recommended RPC endpoint by default and most node operator runs their node with that then in the case of that RPC endpoint goes down may render the whole network unusable, defeating the purpose of using a decentralised network at the first place.


Ligatures not working with any of the flow-nord variants

Hi, first, thank your for this theme. I find your Flow Nord Theme - One dark pro theme the best nord-based theme for logseq and wanted to use it. One problem though, I couldn't solve.
I use fonts with support of ligatures. Inter is my default font (but the problem can be replicated with any font that supports ligatures.
This this simple custom css to change the font:

:root {
 --ls-font-family: "Inter", sans-serif !important;
}

In bonofix or in the logseq default theme, if in a block I writte -> --> ---> ----> it renders like this:

In the default theme:

If I change the theme to the any of the Flow Nord themes, I get, for the exact same block:

i.e., ligatures do not render at all with your theme for some reason. I experimented with various custom.css hacks, I couldn't find a way to get ligatures to work. This happens with any font that supports ligatures, I tested various.
Curiously, insdie code-mirror blocks, no problem, ligatures work if they are enabled like so:
blockquote .CodeMirror pre.CodeMirror-line {
    font-family: "Inter", "Fira Code", monospace !important;
    font-variant-ligatures: normal;
    font-size: 110%;
}

But - I want ligatures to work on normal text blocks too, it's the most important use case for me.
Any suggestion on how to get ligatures to work with the nord theme? any hack on custom.css that fixes this would be wonderful.

I figured a workaround to enable ligatures in this theme, by looking at other themes where ligatures work out of the box. I noticed that most themes have a "font-feature-settings" value almost for every selector, and this theme lacks it.
In short, this fixed my problem:
In custom.css:
:root {
  --ls-font-family: "Inter", sans-serif !important;
  --ml-feature-settings: "ss01" 1, "ss02" 1, "ss03" 1, "ss06" 1, "ss10" 1,
    "ss11" 1, "zero", "onum", "liga" 1, "calt" 1;
  --ls-font-feature-settings: var(--ml-feature-settings);
  --cl-font-family: var(--ls-font-family);
}

html, body {
  /* ligatures in normal blocks work out of the box in the default and bonofix
      themes, no need of the below; however they fail in Flow Nord, issue opened  */
  font-variant-ligatures: normal !important;
  font-feature-settings: var(--ls-font-feature-settings);
}

Sorry for the late reply,  I'll look into it.

Logseq Flow Nord Theme is now use   font-feature-settings: "zero", "liga" 1, "calt" 1; by default.
Please Put the following code in custom.css :
:root {
  --cl-font-family: "Inter", sans-serif;
  --cl-font-feature-settings: "ss01" 1, "ss02" 1, "ss03" 1, "ss06" 1, "ss10" 1, "ss11" 1, "zero", "onum", "liga" 1, "calt" 1;
}

Thanks for your contribution.


Implement submission document redirect endpoint

Generate URLs for documents on Google Drive and Dropbox, and redirect to them from
GET /api/v1/accelerator/deliverables/{deliverableId}/documents/{documentId}.
This is only available for users with Super-Admin, Accelerator Admin, TF Expert,
or Read Only global roles.

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

#1727  👈
#1725
#1724
#1712 : 1 other dependent PR (#1719 )
#1711
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Mar 8, 9:47 AM EST: @sgrimm started a stack merge that includes this pull request via Graphite.


Field search not working

v2.0.6, SQLite.
For one field of type Text in columns.yaml, I set the search capability. As a result, the search is performed on two letters in the second word.

@WebProviderNGO would you mind providing more context please? Maybe some screenshots and what was specifically entered so we can try and replicate.

Closing for now, as there has been no further updates on this issue. Please feel free to get in touch with us if there's still an issue and we'll re-open.


mobile nav menu overlay

I don't believe this div  (lines 17-18) responsible for the overlay should be in the header tag but under it, somewhere around the top of the main element. Placing it in the header tag will only result in an unexpected bug.

It works just fine, the main priority now should be on finishing up with the project before the deadline. We'll deliberate on better ways we could have written the code about later after the submission.


Add documentation for AuthenticationMethod

The following enum needs documentation.
https://github.com/jmg-duarte/nabu/blob/b17a87cf914cbfc967af37af664da091ea7edb53/src/git.rs#L11-L16

Closed by https://github.com/jmg-duarte/nabu/commit/829756da523b60a9adc4a7ae80ab2eb20e5066f8


Update sbt-mdoc to 2.2.20

Updates org.scalameta:sbt-mdoc from 2.2.9 to 2.2.20.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-mdoc" } ]

labels: sbt-plugin-update, semver-patch

Superseded by #202.


Now, "tutorials"  is perfect!

Thanks.  It still needs more efforts.

Hi i have a little questoin about the tutorials. In the  FinRL_StockTrading_NeurIPS_2018.ipynb, there is a config.DOW_30_TICKER when we are trying to fetch the data. I am not exactly sure, but I failed to find the related config(it should be a list of something) in the config file. Could you tell me where is it?

Hi i have a little questoin about the tutorials. In the FinRL_StockTrading_NeurIPS_2018.ipynb, there is a config.DOW_30_TICKER when we are trying to fetch the data. I am not exactly sure, but I failed to find the related config(it should be a list of something) in the config file. Could you tell me where is it?

You can try :
from finrl.apps import config
from finrl.apps import config_tickers
config_tickers.DOW_30_TICKER

Yes, we made some movements.  Thx for pointing it out.

We will revise the notebook. Thanks for reporting it.

Hi i have a little questoin about the tutorials. In the FinRL_StockTrading_NeurIPS_2018.ipynb, there is a config.DOW_30_TICKER when we are trying to fetch the data. I am not exactly sure, but I failed to find the related config(it should be a list of something) in the config file. Could you tell me where is it?

You can try : from finrl.apps import config from finrl.apps import config_tickers
config_tickers.DOW_30_TICKER

Thank you, it helps a lot.


Add package/module generation

Fixes #46

Codecov Report

Merging #47 (3d586ef) into main (cc91f48) will decrease coverage by 0.41%.
The diff coverage is 89.70%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   93.91%   93.50%   -0.42%
==========================================
  Files          15       16       +1
  Lines        2630     2740     +110
==========================================
+ Hits         2470     2562      +92
- Misses        120      133      +13
- Partials       40       45       +5

Impacted Files
Coverage Δ

generator/converter.go
97.03% <28.57%> (-0.33%)
:arrow_down:

ast/cache.go
85.14% <89.15%> (-1.18%)
:arrow_down:

bulk/internal/appender.go
94.66% <100.00%> (ø)

generator/generator.go
50.98% <100.00%> (ø)

generator/moqgen.go
89.91% <100.00%> (ø)

metrics/metrics.go
88.00% <100.00%> (+1.04%)
:arrow_up:

pkg/internal/generator.go
100.00% <100.00%> (ø)

Codecov Report

Merging #47 (3d586ef) into main (cc91f48) will decrease coverage by 0.41%.
The diff coverage is 89.70%.

:exclamation: Current head 3d586ef differs from pull request most recent head e18d068. Consider uploading reports for the commit e18d068 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   93.91%   93.50%   -0.42%
==========================================
  Files          15       16       +1
  Lines        2630     2740     +110
==========================================
+ Hits         2470     2562      +92
- Misses        120      133      +13
- Partials       40       45       +5

Impacted Files
Coverage Δ

generator/converter.go
97.03% <28.57%> (-0.33%)
:arrow_down:

ast/cache.go
85.14% <89.15%> (-1.18%)
:arrow_down:

bulk/internal/appender.go
94.66% <100.00%> (ø)

generator/generator.go
50.98% <100.00%> (ø)

generator/moqgen.go
89.91% <100.00%> (ø)

metrics/metrics.go
88.00% <100.00%> (+1.04%)
:arrow_up:

pkg/internal/generator.go
100.00% <100.00%> (ø)

Codecov Report

Merging #47 (e18d068) into main (cc91f48) will decrease coverage by 0.41%.
The diff coverage is 89.78%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   93.91%   93.50%   -0.42%
==========================================
  Files          15       16       +1
  Lines        2630     2740     +110
==========================================
+ Hits         2470     2562      +92
- Misses        120      133      +13
- Partials       40       45       +5

Impacted Files
Coverage Δ

ast/dsl.go
100.00% <ø> (ø)

generator/converter.go
97.03% <28.57%> (-0.33%)
:arrow_down:

ast/cache.go
85.14% <89.28%> (-1.18%)
:arrow_down:

bulk/internal/appender.go
94.66% <100.00%> (ø)

generator/generator.go
50.98% <100.00%> (ø)

generator/moqgen.go
89.91% <100.00%> (ø)

metrics/metrics.go
88.00% <100.00%> (+1.04%)
:arrow_up:

pkg/internal/generator.go
100.00% <100.00%> (ø)

Codecov Report

Merging #47 (e18d068) into main (cc91f48) will decrease coverage by 0.41%.
The diff coverage is 89.78%.

:exclamation: Current head e18d068 differs from pull request most recent head 97401cf. Consider uploading reports for the commit 97401cf to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   93.91%   93.50%   -0.42%
==========================================
  Files          15       16       +1
  Lines        2630     2740     +110
==========================================
+ Hits         2470     2562      +92
- Misses        120      133      +13
- Partials       40       45       +5

Impacted Files
Coverage Δ

ast/dsl.go
100.00% <ø> (ø)

generator/converter.go
97.03% <28.57%> (-0.33%)
:arrow_down:

ast/cache.go
85.14% <89.28%> (-1.18%)
:arrow_down:

bulk/internal/appender.go
94.66% <100.00%> (ø)

generator/generator.go
50.98% <100.00%> (ø)

generator/moqgen.go
89.91% <100.00%> (ø)

metrics/metrics.go
88.00% <100.00%> (+1.04%)
:arrow_up:

pkg/internal/generator.go
100.00% <100.00%> (ø)

Codecov Report

Merging #47 (97401cf) into main (cc91f48) will decrease coverage by 0.41%.
The diff coverage is 89.78%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   93.91%   93.50%   -0.42%
==========================================
  Files          15       16       +1
  Lines        2630     2740     +110
==========================================
+ Hits         2470     2562      +92
- Misses        120      133      +13
- Partials       40       45       +5

Impacted Files
Coverage Δ

ast/dsl.go
100.00% <ø> (ø)

generator/testmoqs/types.go
0.00% <ø> (ø)

generator/converter.go
97.03% <28.57%> (-0.33%)
:arrow_down:

ast/cache.go
85.14% <89.28%> (-1.18%)
:arrow_down:

bulk/internal/appender.go
94.66% <100.00%> (ø)

generator/generator.go
50.98% <100.00%> (ø)

generator/moqgen.go
89.91% <100.00%> (ø)

metrics/metrics.go
88.00% <100.00%> (+1.04%)
:arrow_up:

pkg/internal/generator.go
100.00% <100.00%> (ø)


Encounter no able to compile

Hi, I have encounter the issues when I compile my program with your plugin
e: C:\Users\user\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\flutter_country_picker-0.1.0\android\src\main\kotlin\rocks\biessek\fluttercountrypicker\FlutterCountryPickerPlugin.kt: (26, 46): Type inference failed. Expected type mismatch: inferred type is ArrayList? but ArrayList was expected
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':flutter_country_picker:compileDebugKotlin'.

Compilation error. See log for more details

The gradle version I used is 'com.android.tools.build:gradle:3.1.2' without set other kotlin plug.
Below logic is how I used your country picker plugin:
Widget countryField(){
if (_isChangeInfo == true ) {

Widget countryMenuList = new Container(
 child: new Row(
    children: <Widget>[
      CountryPicker(
        onChanged: (Country country) {
          setState(() {
            _selected = country;
            _countryName=country.name;
          });
        },
        selectedCountry: _selected,
      ),
      Text(_countryName, style: new TextStyle(color: Colors.black, fontSize: 16.00),),
    ],
  )
);

I've just uploaded 0.1.1. Please upgrade it when available to check if the error persists

It worked after upgrade to 0.1.1. Thanks for upgrade


Kim mb 3230 refactor load transportation office

Description
Creates a swaggerRequest for loadDutyStationTransportationOffice.
Removes old fn and entire ducks file and api file associated with it.
Reviewer Notes
The call was being used in two places: the landing page (Landing/index.jsx) and PaymentRequest.jsx.  I removed the call altogether from PaymentRequest.jsx since we will always have access to the data retrieved from getLoggedInUser, which loads when the user enters the app, and upon any refresh.  At the point in the flow that the customer reaches the payment request page, they cannot edit any fields that would impact the transportation office info, so there is no need to load the office info separately.
Setup

Log in as a service member that is past the profile stage.  You should see the transportation office info on the right of the home page.

Log in as a user that is requesting payment ( you can useppm@continue.requestingpayment).

Go to the weight ticket page

Choose a weight ticket type

Click the checkbox for Full Weight "I'm missing this weight ticket"

See the transportation office name and phone number listed.

Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 5f2c776dc4f0ee1e0937708c585ba7683773657f


Pass different, platform-specific appIds in a single flow

Use case
My app is cross-platform, and its UI and accessibility labels are almost 100% the same across Android and iOS. The only thing that differs is the application ID (Android) and bundle ID (iOS), for historical reasons.
I'd like to be able to run the same flow on both platforms easily. Currently I have to change the appId manually inside the flow, or pass appId as env var, or split my single flow into 3 flows: 2 platform-specific flows and 1 common flow, containing all the test steps.
I think each of these solutions add a bit too much friction for something so basic.
Proposal
appId:
  android: pl.baftek.discoverrudy
  ios: pl.baftek.discoverRudy
---
- clearState
- launchApp
- tapOn: Increment
# ...

I don't quite agree with that -- and I'll use my newly gained superpowers to reopen this issue up for further discussion :)


[release-1.7] Upgrade to latest dependencies

Cherry-pick https://github.com/knative-sandbox/control-protocol/pull/254 to reduce informer cache usage -evankanderson
/cc knative/serving-writers
/assign knative/serving-writers
Produced by: knative-sandbox/knobots/actions/update-deps

/lgtm
/approve


mixed_mode_class_with_missing_properties.swift: This test fails on i3…

…86 with an unoptimized stdlib
XFAIL it to unblock bots.
rdar://35747485

@swift-ci Please smoke test and merge


card updates, ACLS algorithm and image update

WORK IN PROGRESS
Updates:

abg interpretation: minimal
acetaminophen toxicity: minimal
ACLS: update to 2015 guidelines, edit image

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@254f3f2). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #109   +/-   ##
=========================================
  Coverage          ?   49.67%
=========================================
  Files             ?       14
  Lines             ?      155
  Branches          ?       43
=========================================
  Hits              ?       77
  Misses            ?       78
  Partials          ?        0

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 254f3f2...f6f685e. Read the comment docs.


assets not loaded in universal

I have cloned the material + universal tree (why material dependency btw?)
Running the universal build, the following assets all 404, but I can see them in the dist/folder

yarn run universal

(index):9 GET http://localhost:8000/styles.css
(index):10 GET http://localhost:8000/main.css
(index):377 GET http://localhost:8000/index.js
(index):377 GET http://localhost:8000/index.js

yarn start
serves all assets fine
I do note the universal command reports "listening on http://<IP_ADDRESS>:8000" the ip of which looks suspicious. should be <IP_ADDRESS> ?

As mention in some of the other closed issues, universal will be updated when it's stable in angular 4...it was unstable in 2x

@qdouble maybe leave one open and/or remove the duff code or put in big bold letters 'Don't waste your time and energy on Universal in this repo'. What about the stated project goals?

@alastair-todd I can leave this one, open... there were a bunch of other ones that I closed. Universal was basically breaking after ever new update of Angular and was totally unstable, so it wasn't very useable in production...so I stopped using and updating it. Once it's stable, I'll update those branches, but it's just like chasing your tail at this point.
At ng-conf they say they should be releasing docs on using it with ng4, so hopefully I'll be able to update it once that's stable (I'm guessing angular 4.1).

Any solutions?

@zmnv I'm going to start playing around with updating the universal branches to 4.0 today, but I think they said material won't be fully compatible with it until 4.1 or later

@qdouble material isnt important for branch bootrap + universal.
Now yarn run universal doesnt work correctrly :(

@alastair-todd  @zmnv I just merged an update of the main branch to angular 4.1. There still seems to be compatibility issues with material and animations, but it works fine otherwise.
Hopefully it won't be long until everything is working smooth... I'll try to start back making updates more often, but PRs are welcome.

@zmnv just updated the bootstrap branch, everything seems to work fine. Closing this issue, the main material universal branch should be fine once they update material to be compatible.


Error loading anime page

kuro is having trouble opening any anime page at all and when playing an nime it says no links found i thought maybe it was internet issue so i tried to solve it every way i could think of
If applicable, add screenshots to help explain your problem.

Please complete the following information:

Android version: 12 SKQ1.211006.001
App version: 2.1.8
Phone model: poco x3 pro vayu

Additional context
Add any other context about the problem here.

can you please send me an older link of kuro app


Upgrade to latest versions

Depends on https://github.com/Terracotta-OSS/terracotta-platform/pull/1033

Can someone please merge https://github.com/Terracotta-OSS/terracotta-platform/pull/1033 ? I'll do a release train and merge this after


Missing Features (from rewrite)

The rewrite is missing the following features

[ ] Message verification
[ ] Room passwords
[ ] User kicking
[ ] Message chaining

Message chaining is a low priority and is not in the 1.0 checklist (#2)


fix: fix verify not work on PHA

Thank you for creating this PR. We have decided to close this for the reasons mentioned here: https://github.com/boto/botocore/issues/2702#issuecomment-1734208255


bug: Ionic Css 1.2.4 Issue

Type: bug
Ionic Version: 1.x
Platform: android 5.1 webview
Hi, I am updating my ionic css from from 1.0 to 1.2.4 and as a result of that my app shows a blank screen. Any idea why its happing. Thanks

Are there any errors in the console logs? We need more information.

There is no such error mentioning css not found. It just not blank screen, but I noticed that my default controller is being called each time. As I mentioned  if I use css version v1.0.0-beta.1 its working fine. above that I tired 1.2.4, 1.2.3, 1.1.1 all showing blank screen.

One solution I have found to include both css of different version. But there might be an right solution for this.

Beta1  is really old, a lots changed since then.
Have you checked the change log and updated your app?
Does it work in the browser?

Actually I was not aware of the version when started the my project. I got the sample project from the Material Design from the ionic market. This version come with that package.
Browser also showing white blank screen.

Can you please provide a demo or some example that reproduces the issue. I still need more information than "there's a blank screen"

I am also getting a blank screen after upgrading to ionic 1.2.4 from 1.2.1. I just changed the js and css files. Am I supposed to make any changes in the code as well ?

I have debugged the code and found the issue is related to ion slider. My old code was using ion-slides which no longer working.
  <ion-slides  slider="slider" class="sliderBox">
      <ion-slide-page>

Smugglr

Smugglr puts you in touch with a curated set of experts

            <button ng-click="facebook()" class="button button-block">
              Sign in with Facebook
            </button>

      </ion-slide-page>
      <ion-slide-page>

Smugglr

Ask questions and get instant answers across various topics

          <button ng-click="facebook()" class="button button-block">
            Sign in with Facebook
          </button>

      </ion-slide-page>
      <ion-slide-page>

Smugglr

If you happen to like an answer, add that expert to your smugglr network

          <button ng-click="facebook()" class="button button-block">
            Sign in with Facebook
          </button>

      </ion-slide-page>
    </ion-slides>

@AnkB were you also using  ?

Since it has been a little while since there was any activity on this issue i will be closing it, but feel free to respond back if your still having the issue! Thanks again!


[Flake] IAM Integration test - concurrent policy changes. no retry loop.

Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/main/7bdf353c1eaed1d1056f119d6c2d1be2d15b58b0/fedora-34-integration-daily/log-4471ebcd-d237-40e3-b409-8b67a585982e.txt
Step #3: [ RUN      ] IamIntegrationTest.SetIamPolicySuccess
Step #3: google/cloud/iam/integration_tests/iam_integration_test.cc:285: Failure
Step #3: Value of: response
Step #3: Expected: code is equal to OK and message is anything
Step #3:   Actual: 104-byte object <0A-00 00-00 FF-7F 00-00 00-8B 27-01 00-00 00-00 98-00 00-00 00-00 00-00 98-00 00-00 00-00 00-00 00-12 28-01 00-00 00-00 00-4C C0-F4 FF-7F 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00>, whose status is Error in non-idempotent operation SetIamPolicy: There were concurrent policy changes. Please retry the whole read-modify-write with exponential backoff. [ABORTED], with a code that isn't equal to OK, but a message that is anything

@coryan suggests that we implement an optimistic concurrency control loop. And points to spanner as an example.

https://pantheon.corp.google.com/cloud-build/builds;region=us-east1/d2746734-d560-43fd-85a9-840255140c73;step=3?project=cloud-cpp-testing-resources

https://console.cloud.google.com/cloud-build/builds;region=us-east1/62e14247-f0dd-4b9f-bb43-253857356a6c;step=3?project=cloud-cpp-testing-resources


updates to code of conduct for 2022

We should add something about not using curse words when addressing the community & not using (even potentially) offensive jokes to the code of conduct next year.

Done.


Load x_spring, y_spring and labels for hemato dataset

Codecov Report

Merging #150 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #150      +/-   ##
=========================================
+ Coverage   91.57%   91.6%   +0.03%
=========================================
  Files          36      36
  Lines        2029    2037       +8
=========================================
+ Hits         1858    1866       +8
  Misses        171     171

Impacted Files
Coverage Δ

scvi/dataset/hemato.py
100% <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 2186a6e...e2f382a. Read the comment docs.


#467 - Duplicate 404 check in headnode_delete_hnic

Fixes #467

@knikolla could you please merge in the latest haas and push it to your branch so that we can be sure the tests complete?
Thanks!

@henn Something didn't go right during the merge. Creating another pull request.


Fix azure storage key plugin regex

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added

[ ] Docs have been added / updated

[ ] All CI checks are green

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change?

Other information:

do you have a reference of where you took the regex from ?
also.. does it have a test ?

@omryMen
that's the reference
https://github.com/Azure/custom-script-extension-linux/issues/83#issuecomment-269508434
There are two tests for it in tests/plugins/azure_storage_key_test.py (new regex is backward compatible with old one)


Login - Remember Name and Password

Is your feature request related to a problem? Please describe.
I made a lot of accounts because i did not write up my password.
Today i finally wrote down my password.
Describe the solution you'd like
Possible to remember User locally at Login Screen?

Thx. This will be possible in some time but is not top priority.

I have searched a bit on the net and found a possible solution that leverages Windows credential manager.  I will try implementing this today, maybe get it in the next release.

Got this implemented.
Will be part of v0.5.2 release


[DEV-2825]&[DEV-3112]&[DEV-3118]&[DEV-3131] Support Messenger endpoints, remove limitRequest cols, amlCheck minVolume, paymentLinksConfig

Release Checklist
Pre-Release

[ ] Check migrations

No database related infos (sqldb-xxx)
Impact on GS (new/removed columns)

[ ] Check for linter errors (in PR)
[ ] Test basic user operations (on DFX services)

Login/logout
Buy/sell payment request
KYC page

Post-Release

Test basic user operations
Monitor application insights log

[ ] Wait for Services PR
[ ] Add migration


Race and cache mutation detector should be enabled in integration test binaries

Is your feature request related to a problem? Please describe.
We run a lot of controllers meaning races are easily to accidentally write.
Describe the solution you'd like
Our server binaries should run with the race detector (build flag) and cache mutation detector (env var) enabled so that we can catch race conditions in our controllers.
Describe alternatives you've considered
None.
Are you considering submitting a PR for this feature?
N/A

How will this project improvement be tested?

It would be part of our test infra itself.

How does this change the current architecture?
How will this change be backwards compatible?
How will this feature be documented?

Additional context
Add any other context or screenshots about the feature request here.

This also includes the CLI binary we use in our tests.

This is a low priority. Integration test changes will capture this at some point. We can open it again if needed.


feat(paginator): add optional page numbers

Add optional page numbers for displaying navigation on paginator.
Number of visible pages defaults to 3, and is configurable.
Even numbers are rounded up to odd numbers to display equal number
of pages on each side of the current selected page.

Great feature, can't wait for it to be released :)

What is the priority of this merge? We are waiting for it.

What is the status of this pr, can we expect to be merged.

@themitchk any news? @andrewseguin is it still topical? I would try to implement this

Closing due to inactivity and the code still needs rebasing, including support for the MDC-based paginator.


chore: enables service tests

This PR enables service tests. Previously, they were disabled due to an issue with CRT.
CRT would hang on a call to cleanup, because CRT objects were still being held in memory by the SDKDefaultIO singleton.
Additionally, this PR removes the following service tests.

S3 HeadObjectErrorTest and HeadBucketErrorTests. These tests were not accurate. An issue has been created to create new tests that should take their place https://github.com/awslabs/aws-sdk-swift/issues/886
S3 PutObjectTests. These tests are not actually testing any business logic. They are too coupled to the test configuration and seem to just be testing the details in the test.
Route53 tests. Similar to the S3 tests, these aren't actually testing any business logic and appear to just be testing the operation stack configuration in the test itself.

We should prioritize implementing interceptors as interceptors should be the mechanism used by service tests to verify behavior. For example, to test that a certain operation decodes a specific response successfully, we should add an interceptor after the deserialization step that verifies the deserialized output is as we expect. Currently, we duplicate the entire operation stack in the test which is pointless as it doesn't actually test the specific operation.
Issue #
#814
Description of changes

New/existing dependencies impact assessment, if applicable

Conventional Commits

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

per https://www.conventionalcommits.org/en/v1.0.0/#specification this seems to fit more into test category


feat: Extend discovery to support Intel real sense cameras

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[x] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

Make sure a realsense camera is plugged into your device.
Use v4l2-ctl --list-devices to check that the device is recognized by your system and to check the paths of the device.
Build the usb device service using make docker.
Run the edgex core services along with the device service.
Check the discovered devices (http://<IP_ADDRESS>:59881/api/v3/device/service/name/device-usb-camera), make sure that the paths match. Note that only the 1sat, 3rd and 5th paths are saved in the device, as these are the only streaming paths.
Test for rediscovery by deleting the device or restarting the service, etc.
Make sure the paths are updated if ports are changed.

New Dependency Instructions (If applicable)

Validation looks good, provided details of test cases in internal group channel

This PR is based out of https://github.com/edgexfoundry/device-usb-camera/pull/262 whose comments pertaining to this PR have already been addressed. Validation also has been fully done.

Codecov Report

Merging #264 (13798fe) into main (c5a4cd9) will increase coverage by 2.56%.
The diff coverage is 19.73%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff            @@
##            main    #264      +/-   ##
========================================
+ Coverage   2.38%   4.95%   +2.56%
========================================
  Files          8       8
  Lines        879     908      +29
========================================
+ Hits          21      45      +24
- Misses       858     863       +5

Impacted Files
Coverage Δ

internal/driver/device.go
11.42% <ø> (ø)

internal/driver/routes.go
0.00% <0.00%> (ø)

internal/driver/driver.go
4.30% <20.00%> (+4.30%)
:arrow_up:


Change Chartbuilder title to reflect current version number

it's 2.4 but the editor still says 2.0

Done ce987738192a54b0e5f20c8ffc868d3fb613c8f0


refactor metrics exporter deployment

Refactor parts of metrics exporter deployment to simplfy code and keep it readable.
It also fixes bugs related to updating deployment artifacts.

/hold
Testing the changes.

/test ocs-operator-bundle-e2e-aws

/test ocs-operator-bundle-e2e-aws

/cherry-pick release-4.15

/hold
found another issue that is easier to fix in this PR.

/unhold


[Suugestion] Carthage support

Is not a better option to use Carthage instead of CocoaPods ?

@unnamedd tbh b/c I've never used Carthage and I know how to use CocoaPods 😅
I'm actually thinking about dropping CocoaPods altogether to improve build times. This app is <10k lines of Swift and takes forever to compile already...

Gonna close since there's nothing to action yet

@rnystrom is interesting to you if I sent a PR changing from CocoaPods to Carthage?

What would the advantages of Carthage be in this case, @unnamedd?

@basthomas we will have these third libraries pre-compiled, then will add it into project, only the .frameworks. This will made the time to compile be improved and it will remove the needed to have the cocoapods installed to run the project after git clone

🤔, you shouldn't need CocoaPods anyway as the Pods directory is checked in.

@unnamedd sure! I'd take a look.


Make section image recursive

@miltontony ready for review

:+1:

Nice work @saeedmb8 !

@smn Thanks :)


EventArgs as CommandParameter on InvokeCommandAction

Hi,
Is it possible to use event arguments as parameter for commands when using InvokeCommandAction?!
Actually I'm using ItemClick event with behaviors on a ListView & ItemClickEventArgs is the only way to know which item clicked.
Maybe It's good to notice for a reason I can't use SelectedItem, because It's null when you set SelectionMode="None" & also that I'm developing UWP app in C#.
Thanks

By default, that's exactly what will be passed to the command!
Just make sure you don't set theCommandParameter or Converter properties and also that your command execution method can actually receive the parameter!

Oops!
Thank you! I didn't know that!

No problem! Please do close this issue if this solves the problem! 😄

what if I need sender and args?

@HppZ the sender is currently being ignored; if you need it, my advice is to copy the source code for the InvokeCommandAction to your project and change the Execute method to match your needs!

OK, got you, thanks.

maybe you can add this feature.

Hi @PedroLamas , my question is:
Is it possible to binding one property of xxxEventArgs with CommandParameter?
For example, I want pass Uri of NavigationEventArgs. Because NavigationEventArgs belongs to View layer, we'd better not pass it to ViewModel.
<WebView local:WebViewEx.Uri="{Binding LoginUri, Mode=OneTime}">
        <Interactivity:Interaction.Behaviors>
            <Core:EventTriggerBehavior EventName="LoadCompleted">
                <Core:InvokeCommandAction Command="{Binding LoginCommand}" CommandParameter="{Binding Uri}"/>
            </Core:EventTriggerBehavior>
        </Interactivity:Interaction.Behaviors>
    </WebView>
```

@manupstairs Binding to Source property of WebView using ElementName

Thanks @HppZ  for you quickly reply. In fact I tried, it can works if I write
<Core:InvokeCommandAction Command="{Binding LoginCommand}" CommandParameter="{Binding ElementName=webView}"/>
I can find xxxWebView.Source is changed after LoadCompleted event.
But if I just write
<Core:InvokeCommandAction Command="{Binding LoginCommand}" CommandParameter="{Binding Source,ElementName=webView}"/>
The source of WebView will keep the origin value in ViewModel.

@manupstairs you can just create and pass a custom converter that will take the event args and return the uri from it!
Should look something like this:
<WebView local:WebViewEx.Uri="{Binding LoginUri, Mode=OneTime}">
        <Interactivity:Interaction.Behaviors>
            <Core:EventTriggerBehavior EventName="LoadCompleted">
                <Core:InvokeCommandAction Command="{Binding LoginCommand}" InputConverter="{StaticResource MyCustomConverter}"/>
            </Core:EventTriggerBehavior>
        </Interactivity:Interaction.Behaviors>
</WebView>

Very Cool! Thanks Pedrolamas!

Hi, sorry to reopen this issue.
@PedroLamas do you have any sample code for Custom Converter?
Thanks

@bromoapp all you need is a class that implements IValueConverter:
public class MyCustomConverter : Windows.UI.Xaml.Data.IValueConverter
{
    public object Convert(object value, Type targetType, object parameter, string language)
    {
        //implement your conversion operation here

        return null;
    }

    public object ConvertBack(object value, Type targetType, object parameter, string language)
    {
        //you can leave this one like this as it's not required for this case

        throw new NotImplementedException();
    }
}

I want to bind CommandParameter to the a property of the control that triggered the action, for example:
<NavigationView IsSettingsVisible="True">
  <i:Interaction.Behaviors>
    <core:EventTriggerBehavior EventName="ItemInvoked">
      <core:EventTriggerBehavior.Actions>
        <core:InvokeCommandAction Command="{Binding MenuNavigated}"
           CommandParameter="{Binding <InvokeItem>.Tag}" />
      </core:EventTriggerBehavior.Actions>
    </core:EventTriggerBehavior>
  </i:Interaction.Behaviors>
  <NavigationView.MenuItems>
    <NavigationViewItem Icon="Contact" Content="Contacts" Tag="contacts"/>
  </NavigationView.MenuItems>
</NavigationView>

How can I achieve that?

@weitzhandler please don't reply to closed issues with new/different context of the issue itself. As what you wrote is more of a question than an issue, I also recomment that you use StackOverflow, tagging the question with the UWP tag.
Having said that, what you want should be possible by just adding a name to the control (like x:Name="ControlName") and then using {Binding TheControlProperty, ElementName=ControlName}

@PedroLamas tx for your reply
There is no element name, it's auto generated from data-template. I want to refer to the currently selected NavigationViewItem.
Anyway, I switched from using a command to a SelectedItem in my VM and finished.


Add frozen_string_literal statement to all generated .rb files

As @boardfish evoked in https://github.com/github/view_component/pull/1194#issuecomment-1036405220:

it's relatively safe to say that generated components will be new code in new apps, which are likely to default to frozen_string_literal: true

Here are the generated .rb files updated to comply with ViewComponent self coding style.

Can you add a Changelog entry?

Damned, you quick! I was just adding a description to this PR ^^


Updated data-component-scope example

👍  Thank you!
I found a problem in your commit and I have fixed it.

Cool, I'm on the phone and didn't noticed I'm writing dots instead of dashes sorry :)


push! doesn't work correctly

This seems fine:
A = KeyedArray(rand(Int8, 2); index=["a", "b"])
push!(A, 5)

1-dimensional KeyedArray(NamedDimsArray(...)) with keys:
↓   index ∈ 3-element Vector{Any}
And data, 3-element Vector{Int8}:
  ("a")   106
  ("b")  -121
 (3)        5

but:
A

ArgumentError: lengths of key vectors must match size of array (and their axes too)

Stacktrace:
  [1] construction_check
    @ ~/.julia/packages/AxisKeys/pm7Fb/src/struct.jl:30 [inlined]
  [2] KeyedArray
    @ ~/.julia/packages/AxisKeys/pm7Fb/src/struct.jl:17 [inlined]
  [3] KeyedArray
    @ ~/.julia/packages/AxisKeys/pm7Fb/src/struct.jl:20 [inlined]
  [4] unname
    @ ~/.julia/packages/AxisKeys/pm7Fb/src/names.jl:29 [inlined]
  [5] _summary(io::IOContext{IOBuffer}, x::KeyedArray{Int8, 1, NamedDimsArray{(:index,), Int8, 1, Vector{Int8}}, Base.RefValue{Vector{String}}})
    @ AxisKeys ~/.julia/packages/AxisKeys/pm7Fb/src/show.jl:16
  [6] summary
    @ ~/.julia/packages/AxisKeys/pm7Fb/src/show.jl:2 [inlined]
  [7] show(io::IOContext{IOBuffer}, #unused#::MIME{Symbol("text/plain")}, X::KeyedArray{Int8, 1, NamedDimsArray{(:index,), Int8, 1, Vector{Int8}}, Base.RefValue{Vector{String}}})
    @ Base ./arrayshow.jl:337
  [8] limitstringmime(mime::MIME{Symbol("text/plain")}, x::KeyedArray{Int8, 1, NamedDimsArray{(:index,), Int8, 1, Vector{Int8}}, Base.RefValue{Vector{String}}})
...

That's bad, sorry. What should it do?
It can't push its guess into the existing array, since convert(String, 3) is an error. It can't save vcat(A.index, 3) into the original object, as this has the wrong type.
It could make a better guess for strings (but what?) but there will always be stranger types for which it can't make a good guess. Maybe more cases should be made errors?
julia> A = KeyedArray(rand(Int8, 2); index=["a", "b"]);

julia> push!(A, "c" => 55);  # given key has suitable type

julia> A
1-dimensional KeyedArray(NamedDimsArray(...)) with keys:
↓   index ∈ 3-element Vector{String}
And data, 3-element Vector{Int8}:
 ("a")  -25
 ("b")  -64
 ("c")   55

julia> push!(A, 3 => 55);
ERROR: MethodError: no method matching String(::Int64)

julia> C = KeyedArray(rand(Int8, 2); index='a':'b');

julia> push!(C, 55);  # it can guess the next key

julia> C  # immutable C.index has been replaced
1-dimensional KeyedArray(NamedDimsArray(...)) with keys:
↓   index ∈ 3-element StepRange{Char,...}
And data, 3-element Vector{Int8}:
 ('a')  54
 ('b')  88
 ('c')  55


Gradle should always respect the extra attributes when selecting artifacts transforms chains

Expected Behavior

When selecting artifacts transforms chains, Gradle should always respect the extra attributes.
Current Behavior

Only when there is one-step transform matched,  Gradle will respect the extra attributes. But when searching for chains transforms, Gradle ignores the extra attributes requirement of the transform.
Context

Given these three transforms:
Transform1: artifactType=xbundle,  buildType=default ->  artifactType=aar, buildType=debug
Transform2: artifactType=xbundle,  buildType=default ->  artifactType=aar, buildType=release
Transform3: artifactType= aar -> artifactType=classes

Providing a maven dependency in the 'implementation' configuration, likes this:
MavenDependency {artifactType=xbundle,  buildType=default}

Then, we try to get the artifacts with attributes artifactType=aar, buildType=release.
final Configuration implementation = project.getConfigurations().getByName("implementation");
final Configuration test = project.getConfigurations().create("test");
test.setCanBeResolved(true);
test.extendsFrom(implementation);

test.incoming.artifactView(config -> {
                        config.attributes(container -> container.attribute(ARTIFACT_TYPE, "aar"));
                        config.attributes(container -> container.attribute(BUILD_TYPE, "release"));
                    }).getArtifacts();

Gradle should search a chain to transform from {artifactType=xbundle,  buildType=default} to {artifactType=aar,  buildType=release},
And the Transform2 with one depth just works! So gradle just select it, and no conflict occurs! Up to now, artifacts transforms work fine.
Steps to Reproduce (for bugs)

But then, if we try to get the artifacts with attributes artifactType=classes, buildType=release.
There is no one-step transform works, and Gradle will find some candidates can produce 'artifactType=aar'. That's
Transform3: artifactType= aar -> artifactType=classes

Then, Gradle searches for transforms to produce artifactType=aar (Note: gradle will ignore the buildType attribute limit) to create chains. And there are two:
1. artifactType=xbundle,  buildType=default ->  artifactType=aar, buildType=debug
2. artifactType=xbundle,  buildType=default ->  artifactType=aar, buildType=release

So, gradle find two chains to get artifacts like artifactType=classes, buildType=release:
1. artifactType=xbundle,  buildType=default ->  artifactType=aar, buildType=debug
    - artifactType= aar -> artifactType=classes
2. artifactType=xbundle,  buildType=default ->  artifactType=aar, buildType=release
    - artifactType= aar -> artifactType=classes

And, gradle will throw AmbiguousTransformException exception because gradle unable to choose one chains from two path with the same depths.
But I think only the 2nd chains can produce the requested artifacts. Gradle ignore the extra attribute requirement of the transformer when search for chains transforms.
Your Environment

Gradle 4.10.2

Indeed it should fail, and doing this on a project using java-library properly fails, so I think the error is likely in the Android plugin.

@ducrohet You might want to make "buckets" like implementation non-resolvable so users don't run into errors like the one above.

Sorry for confusion.
My code is using the test configuration created by myself. I wrote implementation wrongly.

@oehme Can reopen this issue? The implementation cannot be resolved is not the crux of the problem. I have fixed the issue details.

I created a demo project to produce the issue. https://github.com/noproxy/gradle-issue-7061

Thanks for the clarification. The problem here is that we only consider the end result of the transform chain for matching. Since you have a transform from aar->classes that doesn't preserve buildType, the resulting variants both just have the classes attribute and are thus ambiguous.
I think this is a general limitation of the transformation infrastructure - it's not a partial transformation of the attributes, but a total replacement. @melix this seems to be an extensibility problem, since plugin authors can't be expected to know about all other attributes in existence.


Explore the behavior of bcrypt across different CPUs

📝 error for e6db5ba
docker compose run --rm sandbox node main.mjs
node:internal/modules/cjs/loader:1338
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /usr/src/sandbox-yarn/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node: invalid ELF header
    at Module._extensions..node (node:internal/modules/cjs/loader:1338:18)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/usr/src/sandbox-yarn/node_modules/bcrypt/bcrypt.js:6:16)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.15.0

📝 log for 3bd336c
$ docker build -t sandbox-yarn .
[+] Building 57.8s (10/10) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 220B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 53B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:18.15                                                                                2.8s
 => [internal] load build context                                                                                1.9s
 => => transferring context: 76.04kB                                                                                1.7s
 => [1/5] FROM docker.io/library/node:18.15@sha256:354047346f641fbf9efadac145dd3f328d1ae164680c6a73ffd2a523d605d95f                                                                                42.8s
 => => resolve docker.io/library/node:18.15@sha256:354047346f641fbf9efadac145dd3f328d1ae164680c6a73ffd2a523d605d95f                                                                                0.0s
 => => sha256:354047346f641fbf9efadac145dd3f328d1ae164680c6a73ffd2a523d605d95f 1.21kB / 1.21kB                                                                                0.0s
 => => sha256:16d7247706d3f3c52f0d7a8c73fe5805387d7c8007e1f7b05f6b5ef232ea5551 2.21kB / 2.21kB                                                                                0.0s
 => => sha256:b0248cf3e63c73d0e496a67807d056ca41d5e968b61087e8eca2cf4b9b4d7b99 55.05MB / 55.05MB                                                                                15.9s
 => => sha256:127e97b4daf784e08840a21765f0d4f251192ef2994d0e4a253490f81e63955b 5.17MB / 5.17MB                                                                                0.7s
 => => sha256:0336c50c9f6942b660e433b1086238eec37057c34b14c4e3b28bd7bf05bd84ba 10.88MB / 10.88MB                                                                                4.1s
 => => sha256:9615572c45b7ed230a19f055cf8f15c20124af2eadad8ca19e947bdf775caefe 7.56kB / 7.56kB                                                                                0.0s
 => => sha256:1b89f3c7f7da8adf032a33a75d1b659cee33179ecb88ea0ba75e4fc58ebe63a6 54.58MB / 54.58MB                                                                                18.8s
 => => sha256:2d62772179761f8fddfaed03ed2bdf7078b103b193d18d79a9b49364830d56cf 196.81MB / 196.81MB                                                                                38.4s
 => => sha256:9b293df1e1ca6c5d4ff93529fafef12b0f636ab6a7b739145e9193a6e4af0521 4.20kB / 4.20kB                                                                                16.1s
 => => extracting sha256:b0248cf3e63c73d0e496a67807d056ca41d5e968b61087e8eca2cf4b9b4d7b99                                                                                1.6s
 => => sha256:a77f034fbdc8a1460c2aeeb39596fbffbd6a0ee9db3f747870201d03c4a4e79f 45.58MB / 45.58MB                                                                                26.5s
 => => extracting sha256:127e97b4daf784e08840a21765f0d4f251192ef2994d0e4a253490f81e63955b                                                                                0.2s
 => => extracting sha256:0336c50c9f6942b660e433b1086238eec37057c34b14c4e3b28bd7bf05bd84ba                                                                                0.2s
 => => sha256:87feaa55d9338bbd8be9813b4f9f0a0f0b967d5d257051c879d06c34a634aaa2 2.28MB / 2.28MB                                                                                20.0s
 => => extracting sha256:1b89f3c7f7da8adf032a33a75d1b659cee33179ecb88ea0ba75e4fc58ebe63a6                                                                                1.5s
 => => sha256:f86f7547ad3a3f486b6db40601bf09fc1f3def10ab43d5ac6935cc1c39569699 451B / 451B                                                                                20.2s
 => => extracting sha256:2d62772179761f8fddfaed03ed2bdf7078b103b193d18d79a9b49364830d56cf                                                                                2.8s
 => => extracting sha256:9b293df1e1ca6c5d4ff93529fafef12b0f636ab6a7b739145e9193a6e4af0521                                                                                0.0s
 => => extracting sha256:a77f034fbdc8a1460c2aeeb39596fbffbd6a0ee9db3f747870201d03c4a4e79f                                                                                0.8s
 => => extracting sha256:87feaa55d9338bbd8be9813b4f9f0a0f0b967d5d257051c879d06c34a634aaa2                                                                                0.1s
 => => extracting sha256:f86f7547ad3a3f486b6db40601bf09fc1f3def10ab43d5ac6935cc1c39569699                                                                                0.0s
 => [2/5] WORKDIR /usr/src/sandbox-yarn                                                                                1.1s
 => [3/5] COPY package.json yarn.lock ./                                                                                0.0s
 => [4/5] RUN yarn install --frozen-lockfile                                                                                10.7s
 => [5/5] COPY . .                                                                                0.0s
 => exporting to image                                                                                0.1s
 => => exporting layers                                                                                0.1s
 => => writing image sha256:a763e8af7793a52fe24e253d97e5fd681b22750ebda2942c1de78c7b63cc60df

$ docker run --rm sandbox-yarn
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
$2b$10$RIgx173o3ggjaTNfFjeP3eC5Ahi8dIpE6KHBATOpzRW/g8t6Xbbnm


Fix content when the tag changes

Hello,
When the tag property changes the content is lost because the element is created in the DOM but the content isn't injected.
This pull request calls updateContent when the property tag changes.
Greetings

Thanks for the fix !
I close the PR, because I rebased it on a commit that updated the sample to change the tag value. But kept you as author of the commit even if I changed the double quote to single quote to match the coding style.

So fast, awesome!


Redirected for the login page once tfa setup is confirm

Added the redirect back when the authentication code is invalid.


Replaces manual workaround for Paketo with Maven profile

The former process is too easy to forget and doesn't error either.

Epic!  Thanks @codefromthecrypt


Add autoformatter (Spotless with Maven, Eclipse JDT)

Add Java code auto-formatter config using Spotless (Maven) with the Eclipse JDT formatter. Add a custom Eclipse style XML which closely matches the existing (manual) code style.
To run the auto-formatter, use mvn spotless:apply. This PR does not apply code changes. They will be applied later.
Notable style differences (mainly due to formatter limitations):

80 chars per line will be enforced (except in some odd cases)
Spacing around binary operators will be enforced (mostly)
Even if 2+ arguments fit on a single overflow line, they will still be split 1-per-line
Array initializers will be split 1-per-line
1 space preceding inline comment (previously 2 spaces)
Overflow indentation will be applied in condition expressions

Notable formatter settings:

Comment formatting is DISABLED (required too many manual fixes, maybe we can enable this later)
Off/On Tags are ENABLED via default @formatter:off and @formatter:on comments (some are added in this PR)
"Never join already wrapped lines" is ENABLED to prevent botching already-readable code

Also use Spotless to enforce copyright headers.

I found an intellij plugin named Spotless Gradle. Do you know if this plugin share the same formatting rules?

I found an intellij plugin named Spotless Gradle. Do you know if this plugin share the same formatting rules?

@wuweicaifb - Yeah, I saw that too. Gradle is a different build system though. Perhaps you can see if that plugin still works if you use a dummy build.gradle only holding the Spotless config?


panick when running 'cargo deny check advisories' on project ripasso

Describe the bug
cargo-deny panicked when trying to check advisories.
To Reproduce
Steps to reproduce the behavior:

cargo install cargo-deny
git clone git@github.com:cortex/ripasso.git
cd ripasso
cargo deny check advisories

Expected behavior
Get a list of security problems
Instead got this output:
2020-02-02 15:53:48 [WARN] config path '/tmp/ripasso/deny.toml' doesn't exist, falling back to default config
thread '<unnamed>' panicked at 'internal error: entered unreachable code: the advisory database report contained an advisory
                    that somehow matched a crate we don't know about:
Metadata {
    id: Id {
        kind: RUSTSEC,
        year: Some(
            2019,
        ),
        string: "RUSTSEC-2019-0006",
    },
    package: Name(
        "ncurses",
    ),
    date: Date(
        "2019-06-15",
    ),
    aliases: [],
    references: [],
    collection: Some(
        Crates,
    ),
    categories: [],
    keywords: [],
    cvss: None,
    informational: None,
    obsolete: false,
    url: Some(
        "https://github.com/RustSec/advisory-db/issues/106",
    ),
    title: "Buffer overflow and format vulnerabilities in functions exposed without unsafe",
    description: "`ncurses` exposes functions from the ncurses library which:\n\n- Pass buffers without length to C functions that may write an arbitrary amount of\n  data, leading to a buffer overflow. (`instr`, `mvwinstr`, etc)\n- Passes rust &str to strings expecting C format arguments, allowing hostile\n  input to execute a format string attack, which trivially allows writing\n  arbitrary data to stack memory (functions in the `printw` family).\n",
    patched_versions: [],
    unaffected_versions: [],
}', /home/capitol/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-deny-0.6.2/src/advisories/mod.rs:229:17
stack backtrace:
   0: std::sys_common::backtrace::print
   1: std::panicking::default_hook::{{closure}}
   2: std::panicking::default_hook
   3: std::panicking::rust_panic_with_hook
   4: std::panicking::continue_panic_fmt
   5: std::panicking::begin_panic_fmt
   6: cargo_deny::advisories::check::{{closure}}
   7: cargo_deny::advisories::check
   8: <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
   9: std::panicking::try::do_call
  10: __rust_maybe_catch_panic
  11: <rayon_core::job::HeapJob<BODY> as rayon_core::job::Job>::execute
  12: rayon_core::registry::WorkerThread::wait_until_cold
  13: rayon_core::registry::ThreadBuilder::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Device:

OS: Ubuntu 19.10
Version 0.6.2

Thanks for the repro! Hopefully will have time to look at this tomorrow.

Ok, so I dug a little bit into this, it turns out it's due to how you structured your workspace!
You have a Cargo.toml in your root for ripasso itself, and then additional workspace members are added in the same root toml. So when we get the metadata with that given root crate, cargo says that ripasso is the root of the resolution tree, which krates considers to mean that you've specified a particular crate in a workspace to gather metadata from, in which case it will only add other workspace members that are actually used by that root, which is the exact opposite in your case, as it seems each of the other workspace members depend on the root ripasso, not the other way around.
The rustsec crate works purely on the lockfile, so it says there is an advisory for ncurses, but at that point we have filtered ncurses out of the graph due the aforementioned behavior, resulting in this unreachable case (which will need to be an error instead at least).
I'm actually not sure the what the cleanest way to fix this would be, as I absolutely do want to preserve the behavior of specifying a particular member of a workspace and using that as the singular root of the graph versus the default of using all of the workspace members as root, I just had never checked this against a workspace that was organized this way and missed it.

In the meantime, you can just specify the subdirectory of each of the other workspace members if you wish to check them.

Thanks for the digging and workaround, specifying the members is not a problem, and it showed me a real security problem in one of my dependencies, so it was really useful.


POAP Web APP basic setup

How to run?

Download the github repository
Navigate to the repository and open terminal
In terminal type yarn or npm i
After installation of all packages, edit the .env file
Type yarn dev or npm run dev to run the web app

Screenshots for Mint NFT Feature:

I will start working on other features after approaval on the design :)

I'm not quite sure what I'm doing wrong - when I follow the instructions I can get to a screen that prompts for a sign-in:

But then when click sign in with Xumm I get an error page -

And the GemWallet button doesn't seem to do anything when I click it unfortunately.

(I created my own API key with Xumm, and included it, but it doesn't change whether I have that key in the .env file or not)

(I created my own API key with Xumm, and included it, but it doesn't change whether I have that key in the .env file or not)

In the XUMM APP Dev dashboard there's a field in the bottom "redirection URL". In that we've to add our app url for eg: "localhost:5000" (Apologies should've included this in the points)

I'm not quite sure what I'm doing wrong - when I follow the instructions I can get to a screen that prompts for a sign-in:
But then when click sign in with Xumm I get an error page -
And the GemWallet button doesn't seem to do anything when I click it unfortunately.

You can just navigate to /dashboard
Login is just for the testing purpose (After Gemwallet signin your wallet address will be in console meaning success). I did that cause will have to maintain a separate mongoDB server for that as mentioned in a point as well, separating event attendes and creators

Could you add a README explaining the architecture and include the running instructions?

In the XUMM APP Dev dashboard there's a field in the bottom "redirection URL". In that we've to add our app url for eg: "localhost:5000" (Apologies should've included this in the points)

When I search for redirection URL I can't find any field like that in your repo. Could you maybe add instructions with screenshots to help me figure out how to get that side working?
As for GemWallet - when I click that I don't see anything in the console, maybe those changes haven't been pushed yet? (I double checked that I git pulled beforehand)
Screenshot of what I see after clicking Xumm and then GemWallet buttons.

I will update the readme as soon as possible, till then please look at these videos to get a general idea of the APP
Video links for the pages @JST5000 @JST5000
Login: https://youtu.be/06Woj2gqk4Y
Dashboard: https://youtu.be/rQUnRmruWmI

Video links for the pages @JST5000 @JST5000

Ah, thanks for the videos! Watching now :)
(And already realize that I wasn't seeing anything from Gem because I don't believe I have the extension installed and so I think it was erroring out silently. Could you add a louder error for if that's the case?)

Video links for the pages @JST5000 @JST5000

Ah, thanks for the videos! Watching now :)
(And already realize that I wasn't seeing anything from Gem because I don't believe I have the extension installed and so I think it was erroring out silently. Could you add a louder error for if that's the case?)

Yeah I will add

Once a user logs in, can we auto-populate the Wallet Address field for Mint NFTs? (It's hard to copy from my phone the exact address of my account otherwise)
When I go to mint after logging in with Xumm, I run into an "uncaught type error" (screenshot below) - any idea why that might be?

Full screen


Add Emerge Tools

Thanks for your contribution! This is a template that can make it easier when submitting your contribution:
Your Project: Emerge Tools
Project URL: _https://emergetools.com/_
Category: Analytics
Description: Emerge is a suite of developer tools designed to help teams with app size, performance, snapshot testing, dead code deletion and more. (We love the awesome-ios repo and have used it in all of our experience building mobile apps!)
Inclusion requirements:

[ ] Has 50 GitHub stargazers or more
[X] Only one project/change is in this pull request
[X] Isn't an archived project
[X] Has more than one contributor
[X] Has unit tests, integration tests or UI tests
[X] Addition in alphabetical order (bottom of category)
[X] Supports iOS 12 / tvOS 10 or later
[X] Supports Swift 4 or later
[X] Has a commit from less than 2 years ago
[X] Has a clear README in English

:heart: Awesome iOS Contributors

@jshchnz Thanks for contributing!


Multiple root nodes returned from render function

With the following component template:
<template>
  <split-test name="discovery-experiment">
    <component-a slot="outcome1" chance="3" />
    <component-b slot="outcome2" chance="1" />
  </split-test>
</template>

I see this error:

[Vue warn]: Multiple root nodes returned from render function. Render function should return a single root node.

Looking at the render() function in src/index.js, variations[winner] is returning an Array with a single item in it which Vue does not like.  I am using Vue 2.5.3.

Changing the return statement to read:
 return variations[winner][0]

Fixes the issue for me but I'm not sure if this would work for all usage scenarios.

Hi @aner-perez,
Are you sure that both component-a and component-b contain only one root element? I'll check it for Vue 2.5.3 over the weekend. Meanwhile can you do a little check?
<template>
  <split-test name="discovery-experiment">
    <template slot='A' chance='3'>

A

check

    </template>
    <template slot='B' chance='1'>

B

check

    </template>
  </split-test>
</template>

I get the same error with that template.

I also get the error with this template:
<template>
  <split-test name="discovery-experiment">
    <template slot='A' chance='3'>

A

    </template>
    <template slot='B' chance='1'>

B

    </template>
  </split-test>
</template>

@aner-perez @softbeehive Same problem, any solution for this? If I replace the template tag by an html element the error disappears.
The components I'm outputting all have a single root element.

I was only evaluating this library and Vue at the time so I didn't get further than what was stated above.  I got it to work by making the following change to the vue-a2b source code but I wasn't sure if that was the right thing to do here.
--- a/src/index.js
+++ b/src/index.js
@@ -28,7 +28,9 @@ const VueAB = {
           || randomCandidate(ctx.children)

         storage.entry = {name, winner}
-        return variations[winner]
+               if(variations[winner].length > 1) throw 'VueA2B Error: Only one root node allowed!'
+
+               return variations[winner][0]
       }
     })

Hey folks, this project is kinda abandoned. I used to support it during my time at fromAtoB

Can you recommend another library to use?


[Feature idea]: Blockchained changelogs

Hello,
so there is Sqitch database versioning tool which implements a blockchain for changelog integration. I think this is really a nice feature, since you don't need to give every change an id, instead each change is given it's own integrity checksum and each tag then is also hashed together with the hash of the previous tag.
Liquibase is actually not for away from implementing this, since we have checksums for each <changeSet>, so I guess this wouldn't be so hard to implement.

Thanks @fabiang for submitting this idea. Wanted to make sure you were aware of the post over in forum about ideas for the roadmap? Similarly, on Feb 10 we are having our Liquibase Community Meetup - Share Your Ideas for the 2022 Roadmap and would love to see you there if you haven't already registered.

I like the idea of not needing people to deal with IDs. Git does something similar with hashing.
What's kept me from trying to implement it, though, is that there are times when a changeset validly changes. And if we build the identifier out of the hash, then a change makes it look like a new changeset when it's actually not.
We could do something like having an optional "hash" attribute or something to keep the identifier consistent, but since that original hash is just computed I'm not sure it would be a good user experience to deal with. Seems more complex to deal with than the id/author setup we have now?

One place I've thought about a blockchain type setup could be in collecting a bunch of old changesets up to make it easier to see what has been executed and what has not.
As people get tens of thousands of changesets, the history checking can take a while. But if we could block 9k of those up into a single hashed block somehow, that could speed that up considerably.


A0-4020: Cherry-pick Testnet 13.2 hotfixes to main

Description
This PR cps below commits:
https://github.com/Cardinal-Cryptography/aleph-node/commit/2664b3bf23f8a3e83955c06d5ebf649ae48ce4aa
https://github.com/Cardinal-Cryptography/aleph-node/commit/f43fd9041c5e7006522335bb976cecacbd4c35bb
https://github.com/Cardinal-Cryptography/aleph-node/commit/3b21ef4d5dc2e4aab6030da7844b24d96d326d05
Type of change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

Tesing
E2e pass: https://github.com/Cardinal-Cryptography/aleph-node/actions/runs/8356221052

You probably need to regenerate metada in aleph-client

I tried and got no diff. This is because the pallet operation is already in the runtime. E2e test passes: https://github.com/Cardinal-Cryptography/aleph-node/actions/runs/8356221052


Integrate with Pixiecore to dynamically decide whether to PXE boot and reinstall a machine

Feature Request
Environment
What hardware/cloud provider/hypervisor is being used with Tectonic?
bare-metal
Desired Feature
It would be great if the Tectonic management console would integrate with Pixiecore in API mode. This would allow it to decide dynamically whether to PXE boot and reinstall a node, or whether to just boot from disk (by not serving initrd and kernel information to Pixiecore).

Hey @urzds - thanks for filing this. Will look into this request and get back to you in the next few days!

Although Pixiecore still works with matchbox, it was deprecated in matchbox v0.5.0 (see #397). It does not align with our goals for production clusters.

@mfburnett Thanks for passing this on!
@dghubble Are your goals for / assumptions about production clusters documented in enough detail that I can deduce from that why you don't want to be able to dynamically re-provision systems in this fashion? Is there another documented / recommended way how to address this need?

@dghubble Also, if you don't support pixiecore as a dynamic (i.e. reconfigurable at runtime) proxyDHCP server, what other possibility do I have to set this up?

Pixiecore deprecation details are in the issue linked above, repeated here https://github.com/coreos/matchbox/pull/397. matchbox provides a gRPC API for changing the provisioning profiles for different machines. iPXE is the preferred network boot program (or chaining from PXE to iPXE) and PXE/network services like DHCP, TFTP, and DNS are decoupled from matchbox since datacenters vary widely in existing infrastructure, in our experience.
The specific feature of Pixiecore you're interested in is that it has a bit of state tries to remember that last state of the machine. matchbox does not keep live state about machines like this, though you can use the API to update the matchbox group variable to implement that behavior if you needed it. This problem is better addressed by a machine inventory system designed to store machine stats.


Corrected range problem

Related Issue
#2703
Fixes:  #2703
Description
Corrected nav-bar for all widths

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
900px:

800px:

700px:

600px:

500px:

400px:

300px:

200px:

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@RitiChandak please check the pr.

@RitiChandak Can you please assign the level.
Thank you.


Add to extra paths quick action doesn't resolve import error

Git clone debugpy
Open src/debugpy/server/cli.py
There should be a warning here:

https://github.com/microsoft/debugpy/blob/ef9a67fe150179ee4df9997f9273723c26687fab/src/debugpy/server/cli.py#L388C24-L388C24

Pick the Quick Action to resolve the warning:

Expected result:
Warning goes away.
Actual result:
Nothing changes.

Root cause seems to be the pyproject.toml trumping the settings.json.
Settings.json has this after the change:
{
    "python.analysis.extraPaths": [
        "src/debugpy/_vendored",
        "src/debugpy/_vendored/pydevd",
        "./src/debugpy/_vendored/pydevd/pydevd_attach_to_process",
    ],
}

Pyproject.toml has this:
[tool.pyright]
pythonVersion = "3.8"
include = ["src/**", "tests/**" ]
extraPaths = ["src/debugpy/_vendored/pydevd"]
ignore = ["src/debugpy/_vendored/pydevd", "src/debugpy/_version.py"]
executionEnvironments = [
  { root = "src" }, { root = "." }
]

Looking at the import failure, it looks like it only looks in the src/debugpy/_vendored/pydevd folder

If I add the extra folder to the pyproject.toml, the warning goes away.

looks the extraPath feature currently only support settings.json file.

I'm having a similar issue but I'm not using pyright so I don't have the pyright settings in my pyproject.toml. Adding src/ to my extraPaths still shows the local modules as unable to resolve.

This problem also manifests itself it the .vscode\settings.json file exists. Add extra paths has no effect.


add star component

mapping/star_align: Align .fastq files using STAR.

In general: check the viash config for the use of the correct delimiter when multiple: true. Perhaps also make sure spaces and other delimiters are not being mixed and the description of the argument matches with the chosen delimiter if possible


Adding KubeCarrier project to the landscape

Hi there,
we'd like to add our open source project KubeCarrier to the landscape.
I am aware we are still below the threshold of 300 stars but we get quite some interest for the project and think it is very future oriented: KubeCarrier provides a central framework utilizing Kubernetes Operators and APIs, allowing users to deliver cloud-native service management from one multi-cloud, multi-cluster hub. To us, automating the application layer is the necessary next step of the cloud native journey.
More information on the project in here:
https://www.infoq.com/news/2020/10/kubermatic-announces-kubecarrier/
Looking forward to your feedback. (Uploading the svg now)
Cheers,
Kristin
Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
No cached entry, and KubeCarrier has issues with logo: kubercarrier.svg, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/kubercarrier.svg'

Deploy preview for landscape failed.
Built with commit b1686f104ce1b401eeea42f2973f67a120da7e79
https://app.netlify.com/sites/landscape/deploys/5fa40e2829271100071c6837

@taylorwaggoner : Seems like uploads to Hosted_Logos is disabled. Adding the SVG here.

/lgtm

@KrissiWi the issue is probably that your entry to the landscape.yml shows the logo as "logo: kubercarrier.svg".  If you fix the file name, it should be okay.  Please upload the image to Hosted Logos.  thanks!

Hi @taylorwaggoner,
I just tried with the renamed file but keep getting this error message when clicking on upload file

@KrissiWi are you trying to upload the logo to your branch or directly to master?  Feel free to send the logo to me at<EMAIL_ADDRESS>or attach here and I'll give it a shot. Thanks!

@taylorwaggoner : Thank you very much for the support. Here is the link to the SVG:
https://drive.google.com/file/d/1Q34ZSrXgOhu7I2RVFbwnZIAMRnmLXCnl/view?usp=sharing
I added the png as well in case this is off help.

Thanks again for the support!
Kristin

@KrissiWi I opened a new pull request for this https://github.com/cncf/landscape/pull/1895
Thanks!


build(workflow): same node version on all stages

Motivation
We have completely different node --versions on local development,
build server (even in different jobs) and production.
My suggestion is that we configure the node version in a central file in
the root folder and reference it from everywhere.
For me, any version manager is fine. If I have the choice, I suggest
[asdf-vm]](https://github.com/asdf-vm/asdf).
How to test

Check status checks

One question: Does this mean, that every developer must use asdf?

No, it is completely up to the developer what they use. As written in the README just make sure that you use the node version specified in tool-versions. Use whatever version manager you like.
We just have to save the version in some file. Workflows shall take this file as a reference.
Good?


Fix past key values usage

transformers 4.26.0 broke the usage of past key and values in Optimum:
https://github.com/huggingface/transformers/blob/v4.25.1/src/transformers/models/t5/modeling_t5.py#L1703
vs
https://github.com/huggingface/transformers/blob/v4.26.0/src/transformers/models/t5/modeling_t5.py#L1715
This PR fixes the issue and adds the corresponding test.
Related: https://github.com/huggingface/optimum/pull/756 https://github.com/huggingface/optimum/issues/754

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


End of line character is not visible.

Currently, when running running set list command, the EOL character is invisible. As a temporary workaround, setting hi NonText ctermfg=7 guifg=gray works.

I came across this small problem and fixed it for myself by using the same non-obstrusive color as for the line numberings. Maybe you want to incorporate this small change :)

This is a really helpful fix. It would be great to see it merged into the official repo.
Thanks for the nice theme!


Bosnia and Herzegovina number considered not plausible

What I did

Phony.plausible? '+38766666666'

What happened

Returned false

What I expected to happen and why
Return value true.
Saw another issue on here point to https://www.textmagic.com/free-tools/phone-validator and indicate the number works, so did the same and entered 066666666 for Bosnia and Herzegovina, it thinks this should be valid.
For what it's worth, I've noticed that  Phony.plausible? '+387066666666' does return true, but I'm pretty sure that the zero after the country code shouldn't be there? Sites like the above and so on seem to indicate the zero should be removed... maybe it's valid though?
Note, this isn't the number I originally had, but that belongs to a customer of ours so I'm not using it here. It's the same length, also begins with a 6 and returns the same results for all the checks I've described above.

Hi Daniel
Thanks for the issue entry! 😊 The note is especially helpful.
Do you feel up to the task of improving this and providing a PR? (Some pointers: Bosnia is defined in countries.rb, and the trunk method takes an option, whose … options you can check in TrunkCode) I'm asking because my time is sadly very limited. But always happy to merge a PR 😊
Cheers
Florian


Will node's net or tls modules work using this?

Hi,
I'm wondering if this plugin will allow the use of node's net or tls modules. If not, would the net-browserify module help at all? https://github.com/emersion/net-browserify Or how about tls-browserify: https://github.com/emersion/tls-browserify ? I see you already use https-browserify.

I'd also be interested in knowing if this would shim/emulate use of Node's net module.  We need to create a TCP socket connection where our NativeScript app is the client.

+1 to this.  I'd love to be able to host my socket.io server that my app uses within the app itself.  Errors on child_process, net and tls when I try to do so.


Bump k3s version to v1.24.12+k3s1

Proposed Changes
Bump k3s version from v1.24.11+k3s1 to v1.24.12+k3s1
Checklist

[x] Tested locally
[x] Ran site.yml playbook
[x] Ran reset.yml playbook
[x] Did not add any unnecessary changes
[x] Ran pre-commit install at least once before committing
[x] 🚀

Thank you!


Simplify estimate_order_costs

This would probably look like having a priority of concerns rather than the full cost estimation as now. Possible ordering:

Evaluator / expression order requirement (mandatory).
More favorable mixed dice order.
Skips. highest prefers popping from the top (ascending / backwards or descending / forwards), and lowest from the bottom (descending / backwards or ascending / forwards). (Should skips be added for decks?)
Ascending / backwards if there are no other preferences.

For anything beyond constant factors I would tend to prioritize single-query performance over caching. So pool.lowest() might lose some cache hits when used with both mixed and homogeneous pools.

In a quick test:
from icepool import MultisetEvaluator, d4, d6, d8, d10, d12, Pool, Order
import cProfile

class TestSumEvaluator(MultisetEvaluator):
    def __init__(self, order):
        self._order = order

    def next_state(self, state, outcome, a, b):
        if state is None:
            state = 0
        return state + outcome * a + outcome * b

    def order(self):
        return self._order

evaluator_a = TestSumEvaluator(Order.Ascending)
evaluator_b = TestSumEvaluator(Order.Descending)
mixed_pool = Pool([d6, d8, d10, d12])

cProfile.run('evaluator_a(mixed_pool, mixed_pool)')
cProfile.run('evaluator_b(mixed_pool, mixed_pool)')

The backwards evaluation resulted in
69975 function calls (65244 primitive calls) in 0.024 seconds

while the forwards evaluation resulted in
722621 function calls (661263 primitive calls) in 0.235 seconds

done