Eth1 withdrawal credentials (0x01)

Add eth1 withdrawal credentials by specifying a new withdrawal prefix version (0x01) whose content is a 20-byte eth1 address.
Note, this specifies the minimum required commitment and leaves out the end-to-end details on how the beacon chain and eth1 chain/state will handle the withdrawals other than the fact that the ETH will be transferred into the specified address with no payload other than the ETH and this will be triggered/payed for through a normal eth1 TX.
See this ethresearch post for an end-to-end version of how withdrawals might take place. Note, the only important details for this commitment are that 0x01 withdrawals receipts automatically make it to the eth1 chain and then can be consumed through a normal TX that specifies gas/tx-fees and sends the ETH to the destination address.
This opens up eth1 custody options such as smart contract wallets and simple hardware wallet support along with enabling a number of trustless staking pool options

Please let me know if the amount specified in validator.md is clear enough.
I considered creating a fork agnostic folder specs/withdrawal_credentials to specify each withdrawal_credential version independent of any fork. Given that these can't really change once deployed, it might make sense to gather them all in one place. Any thoughts?

Generally speaking I would like to have this in the spec. I think an important function for any Eth1 withdrawal contract is to initiate the validator exit. This is an essential function for any staking pool (where it's not sufficient to use the withdrawal key to initiate exit).
One way to implement it would be to add a function to the withdrawal contract
def isExitable(validatorPubkey) -> bool:

and any Eth1 address can initiate the "Eth2 exit" precompile that will then use this function to check if the contract allows an exit.

I would add that in case of using ETH1_ADDRESS_WITHDRAWAL_PREFIX, Ether will be transferred from fixed SYSTEM_CONTRACT address, with exact address added later, so contracts could easy clarify who is the sender.

Should it be part of the spec what minimal functionality should a contract have if it's an eth1 withdrawal address? i.e. be able to send a simple transaction to a TBD address, receive funds, etc

I would add that in case of using ETH1_ADDRESS_WITHDRAWAL_PREFIX, Ether will be transferred from fixed SYSTEM_CONTRACT address, with exact address added later, so contracts could easy clarify who is the sender.

i'd think specifying a mechanism for the implementation of moving ETH from the beacon chain to the evm userspace is a little premature given the unknowns around the details of the eth1-eth2 merge. (e.g. we could imagine tracking withdrawals outside an actual contract in the EVM)
my understanding of this PR is more to provide a firm(er) commitment to eth withdrawals to today's eth1 so that the use cases that can get away with just this functionality can move ahead w/ development and implementation.
i do think we eventually want a more involved mechanism for eth transfer (e.g. https://github.com/ethereum/eth2.0-specs/issues/2151) but i'd suggest waiting for a clearer understanding of the merge before moving ahead w/ concrete specifics of such a scheme

Should it be part of the spec what minimal functionality must a contract have if it's an eth1 withdrawal address? i.e. be able to send a simple transaction to a TBD address, receive funds, etc.

The PR does specify that the eth1 withdrawal address just needs to be able to accept ETH (e.g. by default as an EOA, or a payable function in a Solidity smart contract). If you look at my prior comment, there is certainly a space for a more complex mechanism for withdrawals (discussion starting here: https://github.com/ethereum/eth2.0-specs/issues/2151) but I'd say that is a another iteration of withdrawal handling once we better understand the eth1-eth2 merge.

it seems that this PR is partially held up b/c of a question around whether eth1-triggered withdrawals are necessary for staking pool functionality.
I suspect that the 0x01 creds here are sufficient for some designs and should probably be set in stone now. Can always add other credential types later. what do folks think?

👍

@zilm13

Ether will be transferred from fixed SYSTEM_CONTRACT address, with exact address added later, so contracts could easy clarify who is the sender.

I'm inclined to not even put this in there as it is not an entirely actionable detail today.
Also, assume this is a contract that can split funds or a multi-sig or something. Receiving extra ETH from non SYSTEM_CONTRACT seems fine in almost all cases 😂

Unstaking BLS to ETH1 - the wagyu gui asks for a 24 word recovery phrase, but metamask offers a 12 word phrase, how to proceed in that case?

I don't know how the wagyu GUI works and you should probably ask the maintainers
You may find more information here: https://launchpad.ethereum.org/en/withdrawals

allnodes.com created a Ledger Nano X compatible tool that ended up working.
https://help.allnodes.com/en/articles/7235575-how-to-change-your-ethereum-withdrawal-credentials-from-0x00-to-0x01-deposit-cli

Add eth1 withdrawal credentials by specifying a new withdrawal prefix version (0x01) whose content is a 20-byte eth1 address.
Note, this specifies the minimum required commitment and leaves out the end-to-end details on how the beacon chain and eth1 chain/state will handle the withdrawals other than the fact that the ETH will be transferred into the specified address with no payload other than the ETH and this will be triggered/payed for through a normal eth1 TX.
See this ethresearch post for an end-to-end version of how withdrawals might take place. Note, the only important details for this commitment are that 0x01 withdrawals receipts automatically make it to the eth1 chain and then can be consumed through a normal TX that specifies gas/tx-fees and sends the ETH to the destination address.
This opens up eth1 custody options such as smart contract wallets and simple hardware wallet support along with enabling a number of trustless staking pool options
Please let me know if the amount specified in validator.md is clear enough.
I considered creating a fork agnostic folder specs/withdrawal_credentials to specify each withdrawal_credential version independent of any fork. Given that these can't really change once deployed, it might make sense to gather them all in one place. Any thoughts?

i need eth


[Bug]: REST API request filters nulls

Is there an existing issue for this?

[X] I have searched the existing issues

Description
send this body in a POST request:
{ 	"hello": null, 	"world": "PP" }
send it to any url, e.g. https://anyurl.com, just run the request to examine the body in the error
You will notice that the body that appsmith sends does not contain the first key, i.e., hello:
"body":{       "world":"PP" }

Steps To Reproduce
explained above
Public Sample App
No response
Environment
Production
Severity
High (Blocker to building or releasing)
Issue video log
No response
Version
Cloud

while this is indeed a frustrating issue, there is a workaround for it: either handle this in js object or in the backend implementation. It is a high priority issue and we have planned it for the next sprint.


[flutter_markdown] code lines in header not rendered properly

Seems the inline code blocks are not properly rendered, they are rendered the same way as in the body text, which results in small code lines in header.
Steps to Reproduce
In the markdown source, write something like:
## This is a header

Lorem ipsum lorem ipsum lorem ipsum lorem ipsum lorem ipsum

## This is another header **with `some inline code`**

Lorem ipsum lorem ipsum lorem ipsum lorem ipsum lorem ipsum

Expected results:
I expect to get similar rendering as in VScode:

Actual results:
This is what I get in the markdown widget:

Using below code sample and running it on latest master and stable, I get same behavior as reported:

 runnable code sample

import 'package:flutter/material.dart';
import 'package:flutter_markdown/flutter_markdown.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MinimalMarkdownDemo(),
    );
  }
}

const String _data = '''
## This is a header

Lorem ipsum lorem ipsum lorem ipsum lorem ipsum lorem ipsum

## This is another header **with `some inline code`**

Lorem ipsum lorem ipsum lorem ipsum lorem ipsum lorem ipsum
''';

class MinimalMarkdownDemo extends StatelessWidget {
  const MinimalMarkdownDemo({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text('Markdown Demo')),
      body: MarkdownBody(
        styleSheet: MarkdownStyleSheet(
          h1Align: WrapAlignment.center,
          h2Align: WrapAlignment.end,
        ),
        data: _data,
      ),
    );
  }
}

 stable, master flutter doctor -v

[[✓] Flutter (Channel stable, 2.10.4, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 2.10.4 at /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (3 days ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.13.0-0.0.pre.277, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 2.13.0-0.0.pre.277 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 13d2381109 (4 hours ago), 2022-03-27 21:00:08 -0400
    • Engine revision 559e259c54
    • Dart version 2.17.0 (build 2.17.0-246.0.dev)
    • DevTools version 2.11.4

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.


Why the beta documentation stopped updating?

So nice documentation,i am looking forward to learning more about it.

The beta documentation is being updated on a regular basis. The content takes some time to be prepared from scratch.

https://github.com/reactjs/reactjs.org/issues/3308#issuecomment-1098103021


timeout error when running from Flex Engine

Hello there,
I am getting an exception when I run my app from  Coogle Cloud Flex engine.  I am running a very simple query that should retrieve 1 row back. When I run this code and I hit the same database from my dev environment, it works fine. Below is the actual dump of the exception.
Thanks in advance for your help.
2018-03-14 13:47:46 default[v1]        Request starting HTTP/1.1 GET http://testdatastoragefromdotnet.appspot.com/api/vehicle?id=1
2018-03-14 13:47:46 default[v1]  info: Microsoft.EntityFrameworkCore.Infrastructure[10403]
2018-03-14 13:47:46 default[v1]        Entity Framework Core 2.0.1-rtm-125 initialized 'fleetContext' using provider 'Npgsql.EntityFrameworkCore.PostgreSQL' with options: None
2018-03-14 13:47:46 default[v1]  info: Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker[1]
2018-03-14 13:47:46 default[v1]        Executing action method Cms.Controllers.VehicleController.Get (GcpCms) with arguments (1) - ModelState is Valid
2018-03-14 13:48:01 default[v1]  fail: Microsoft.EntityFrameworkCore.Database.Connection[20004]
2018-03-14 13:48:01 default[v1]        An error occurred using the connection to database 'fleet' on server 'tcp://x.x.x.x5432'.
2018-03-14 13:48:01 default[v1]  System.TimeoutException: The operation has timed out.     at Npgsql.TaskExtensions.<WithTimeout>d__1.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnector.<ConnectAsync>d__148.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnector.<RawOpen>d__146.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnector.<Open>d__143.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.ConnectorPool.<AllocateLong>d__24.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnection.<Open>d__28.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnection.<>c__DisplayClass26_0.<<OpenAsync>b__0>d.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.<OpenAsync>d__34.MoveNext()
2018-03-14 13:48:01 default[v1]  fail: Microsoft.EntityFrameworkCore.Query[10100]
2018-03-14 13:48:01 default[v1]        An exception occurred in the database while iterating the results of a query for context type 'Cms.DataModel.fleetContext'.
2018-03-14 13:48:01 default[v1]        System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. ---> System.TimeoutException: The operation has timed out.           at Npgsql.TaskExtensions.<WithTimeout>d__1.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Npgsql.NpgsqlConnector.<ConnectAsync>d__148.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Npgsql.NpgsqlConnector.<RawOpen>d__146.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Npgsql.NpgsqlConnector.<Open>d__143.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Npgsql.ConnectorPool.<AllocateLong>d__24.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
2018-03-14 13:48:01 default[v1]           at Npgsql.NpgsqlConnection.<Open>d__28.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Npgsql.NpgsqlConnection.<>c__DisplayClass26_0.<<OpenAsync>b__0>d.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.<OpenAsync>d__34.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable`1.AsyncEnumerator.<BufferlessMoveNext>d__10.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Microsoft.EntityFrameworkCore.Storage.Internal.NpgsqlExecutionStrategy.<ExecuteAsync>d__7`2.MoveNext()
2018-03-14 13:48:01 default[v1]           --- End of inner exception stack trace ---
2018-03-14 13:48:01 default[v1]           at Microsoft.EntityFrameworkCore.Storage.Internal.NpgsqlExecutionStrategy.<ExecuteAsync>d__7`2.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable`1.AsyncEnumerator.<MoveNext>d__9.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
2018-03-14 13:48:01 default[v1]           at System.Linq.AsyncEnumerable.<SingleOrDefault_>d__381`1.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.TaskResultAsyncEnumerable`1.Enumerator.<MoveNext>d__3.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
2018-03-14 13:48:01 default[v1]           at System.Linq.AsyncEnumerable.SelectEnumerableAsyncIterator`2.<MoveNextCore>d__7.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
2018-03-14 13:48:01 default[v1]           at System.Linq.AsyncEnumerable.AsyncIterator`1.<MoveNext>d__10.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]           at Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.ExceptionInterceptor`1.EnumeratorExceptionInterceptor.<MoveNext>d__5.MoveNext()
2018-03-14 13:48:01 default[v1]  System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. ---> System.TimeoutException: The operation has timed out.     at Npgsql.TaskExtensions.<WithTimeout>d__1.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnector.<ConnectAsync>d__148.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnector.<RawOpen>d__146.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnector.<Open>d__143.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.ConnectorPool.<AllocateLong>d__24.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnection.<Open>d__28.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Npgsql.NpgsqlConnection.<>c__DisplayClass26_0.<<OpenAsync>b__0>d.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.<OpenAsync>d__34.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable`1.AsyncEnumerator.<BufferlessMoveNext>d__10.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Storage.Internal.NpgsqlExecutionStrategy.<ExecuteAsync>d__7`2.MoveNext()
2018-03-14 13:48:01 default[v1]     --- End of inner exception stack trace ---
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Storage.Internal.NpgsqlExecutionStrategy.<ExecuteAsync>d__7`2.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable`1.AsyncEnumerator.<MoveNext>d__9.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
2018-03-14 13:48:01 default[v1]     at System.Linq.AsyncEnumerable.<SingleOrDefault_>d__381`1.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.TaskResultAsyncEnumerable`1.Enumerator.<MoveNext>d__3.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
2018-03-14 13:48:01 default[v1]     at System.Linq.AsyncEnumerable.SelectEnumerableAsyncIterator`2.<MoveNextCore>d__7.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
2018-03-14 13:48:01 default[v1]     at System.Linq.AsyncEnumerable.AsyncIterator`1.<MoveNext>d__10.MoveNext()
2018-03-14 13:48:01 default[v1]  --- End of stack trace from previous location where exception was thrown ---
2018-03-14 13:48:01 default[v1]     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-03-14 13:48:01 default[v1]     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-03-14 13:48:01 default[v1]     at Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.ExceptionInterceptor`1.EnumeratorExceptionInterceptor.<MoveNext>d__5.MoveNext()
2018-03-14 13:48:01 default[v1]  fail: Microsoft.EntityFrameworkCore.Query[10100]
2018-03-14 13:48:01 default[v1]        An exception occurred in the database while iterating the results of a query for context type 'Cms.DataModel.fleetContext'.
2018-03-14 13:48:01 default[v1]        System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. ---> System.TimeoutException: The operation has timed out.           at Npgsql.TaskExtensions.<WithTimeout>d__1.MoveNext()
2018-03-14 13:48:01 default[v1]        --- End of stack trace from previous location where exception was thrown ---
2

The stack trace is saying that the connection attempt (OpenAsync()) timed out, this is most likely some sort of network configuration issue that's beyond Npgsql's control. Double-check your Google Cloud settings. As a test, you can also try to connect with (Open()), just to make sure it times out there as well (if it doesn't please let me know).
Am going to close as there doesn't seem to be anything Npgsql-related, but feel free to post back here and I'll reopen if new information shows otherwise.


Add support for HTML5 Audio

I would also like to see support for HTML5 audio.

Hello all verly personalities take blessed, I'm not sure I'd ask to relevant resentz. I'd want to know how to withdraw my reference by PayPal I'd don't know how

@mbaxas9 Can you be more specific about your request here?


bump IREE to latest

Currently trying to get the pad-pack pipline working, it is failing with this gist
https://gist.github.com/nirvedhmeshram/f37ac36a855e56e7836585982638a6a7

@erwei-xilinx I am seeing a new failure, in the loop fusion pass with the air-bump in this PR that is required to match the llvm of the iree bump happening here. Here is a gist with the IR and the failure, could you please confirm this can be reproduced in latest AIR for you?
https://gist.github.com/nirvedhmeshram/b45d47c444e0dd7597d5f1f5ddb20038

The new failure is interesting! The reason is previously in lowering strategy pass we used to attach a {translation_info = #iree_codegen.translation_info<None>} attribute to the hal.executable.export op. But after this PR this is attached to the func.func op that is passed to the aie2xclbin tool which fails with the error
loc("module_matmul_small_1_dispatch_0_amdaie_xclbin_fb.aiecc.mlir":635:185): error: #"iree_codegen"<"translation_info<Custom>"> : 'none' attribute created with unregistered dialect. If this is intended, please call allowUnregisteredDialects() on the MLIRContext, or use -allow-unregistered-dialect with the MLIR opt tool used

There can be several solutions such as deleting the attribute after its purpose is served, trying with the -allow-unregistered-dialect flag but wanted check what the right thing to do is? @MaheshRavishankar

You can add the reconcileTranslationInfo pass as is done here https://github.com/iree-org/iree/blob/e8f4948d5c62beea27a109161b697d9088d5b3bd/compiler/src/iree/compiler/Codegen/LLVMGPU/Passes.cpp#L843
I notice I missed adding this on the CPU side, but this essentially deletes the translation info and sets the values appropriately

Awesome!!! Did you want me to look at the TD tests.

I can take a stab at it on Monday unless I am needed on something higher priority.


Joins across multiple GPUs using P2P

I am interested in the use case where some GPUs are connected by P2P and we perform a join involving data only on these GPUs. Does the current implementation use loads/stores or cudaMemcpy (p2p) or cudaMemcpy (via host)?

Hi
Thanks for your interest in MapD
We currently do not do P2P access in our processing model.
It is on our road map for future release

Thanks @dwayneberry for the reply.


Accept either string or list for conda-env-stripped-path

@amontz @fleimgruber @WJCFerguson anyone else affected by #32, is anyone able to try this version of the function and confirm it fixes the issue? I believe it should, but I'm not sure and don't want to merge another fix that doesn't work :wink:

@necaris This version works for me.

Thank you @amontz!


0.97.0 Could not convert string to float: unknown

Using the latest stable versions of everything. I just noticed that I'm getting the following error:
2019-08-08 09:04:52 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 45, in async_entity_state_listener
    hass, smart_home_config, alexa_changed_entity
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 68, in async_send_changereport_message
    properties = list(alexa_entity.serialize_properties())
  File "/usr/src/homeassistant/homeassistant/components/alexa/entities.py", line 181, in serialize_properties
    for prop in interface.serialize_properties():
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 105, in serialize_properties
    prop_value = self.get_property(prop_name)
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 446, in get_property
    return {"value": float(temp), "scale": API_TEMP_UNITS[unit]}
ValueError: could not convert string to float: 'unknown'

This isn't from the custom component. It's from the built in version. You'll need to open a bug in the main repo.


update System.Collections.Immutable to 1.3.1

Fixes #3629 (I hope)
Quick edit: I've verified that the current version of VS2017 (15.3.5) contains System.Collections.Immutable 1.3.1

@brettfo I took a crack at this too - see https://github.com/Microsoft/visualfsharp/pull/3641 - I spotted some config files that needed binding redirects added too

@brettfo I'll close this in favour of #3641


Callback type check

WHAT?
PR creates a typeof check for callback being passed to the client. and throws an error incase a callback which is not a function is passed.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

should fix https://github.com/sendgrid/sendgrid-nodejs/issues/487#issuecomment-337197205

@adamreisnz @thinkingserious  do give this tiny PR a review when you guys get time.. no hurry :)

Thanks @adamreisnz.. fixed the review comments

@adamreisnz was wondering if this get's merged before the month end am i eligible for some swag 😅

@nitish24p you'd have to ask @thinkingserious or @mbernier, but probably yes ;)

what say @thinkingserious and @mbernier ?? Also if the review is done anything else that i need to do..??

@mbernier can this PR be merged if all is fine?

If @adamreisnz says it's good, that's good enough for me ;)

Hello @nitish24p,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


dagger: 0.2.36 -> 0.3.7

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Please also update sha256 and re-test the build.

After updating the sha256 nix-build -A dagger fails with:
this derivation will be built:
  /nix/store/db70ky9njbakqgl802dpnfbygqjv3g3x-dagger-0.3.7.drv
building '/nix/store/db70ky9njbakqgl802dpnfbygqjv3g3x-dagger-0.3.7.drv'...
unpacking sources
unpacking source archive /nix/store/21crn7xb10n6d2b13smwb58h8yn111bk-source
source root is source
patching sources
configuring
building
Building subPackage ./cmd/dagger
go: -mod may only be set to readonly when in workspace mode, but it is set to "vendor"
        Remove the -mod flag to use the default readonly value,
        or set GOWORK=off to disable workspace mode.
error: builder for '/nix/store/db70ky9njbakqgl802dpnfbygqjv3g3x-dagger-0.3.7.drv' failed with exit code 1;
       last 10 log lines:
       > unpacking sources
       > unpacking source archive /nix/store/21crn7xb10n6d2b13smwb58h8yn111bk-source
       > source root is source
       > patching sources
       > configuring
       > building
       > Building subPackage ./cmd/dagger
       > go: -mod may only be set to readonly when in workspace mode, but it is set to "vendor"
       >         Remove the -mod flag to use the default readonly value,
       >        or set GOWORK=off to disable workspace mode.
       For full logs, run 'nix log /nix/store/db70ky9njbakqgl802dpnfbygqjv3g3x-dagger-0.3.7.drv'.

I updated the hash here: https://github.com/NixOS/nixpkgs/pull/206984


[BEAM-10378] Adding Azure IO FileSystem

Adding an AzureBlobStoreFileSystem to the Java SDK.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.


does gorm support prefix/suffix mapping between struct name and table name?

for example, i want to map struct Employee to table prefix_employee.
xorm has already support this.

Create a method called TableName() on the struct to give a custom name.

thanks @pjebs for your reply. the way you provided means i have to define this TableName() for every struct, i think it will be better if gorm has builtin similar mechanism.

General mapping rules definition/override would be nice for tables as well as columns.

Overwrite the DefaultTableNameHandler method

@jinzhu It doesn't work in using db.AutoMigrate(Model{}) or db.First(Model{}).
Because DefaultNameHandler is called only from ModelStruct.
If a model implements tabler interface, DefaultNameHandler is never called.
So, I create pull request. Please take a look?
https://github.com/jinzhu/gorm/pull/1688


Simple Geometry Contribution and github test case

Preface:
This issue follows the conversation in PR #109 and is purposefully a test case working on the migration described in issue #106.  #109 is still open so we can kick the tires on both approaches.
For discussion of the text of this proposal, use copy and paste content into a comment below and use strikethrough (~~strikethrough~~) and bold (**bold**) text to indicate removed text. E.g. change this to this. An alternative could be: strikthrough(new text in parens in new expected style)
Note that this is probably a very long submission in comparison to typical change requests that would be vetted using github issues. Comments here will likely get long, but it seems that should be OK as long as we remember that it is probably an outlier and is about as long as these would ever get.

Summary
This proposal has been vetted on the CF email list extensively and has gone through a number of iterations. The structure and semantics of the proposed addition below should be close to complete, but this is the first review of proposed text to be added to the CF 1.8 specification. This is entirely new text (section 7.5) to be added just after section 7.4. There is also text to be added as Example E1 in Appendix E. The text should more or less speak for its self, but much more information about the proposal can be seen in the readme here, on the wiki about the specification here, and in the poster here.
The proposed text follows first with a suggested section 7.5 then a suggested example to be added to appendix E.

Section 7.5 Spatial Geometries
For many geospatial applications, data values are associated with a spatial geometry (e.g., the average monthly rainfall in the UK).  Although cells with an arbitrary number of multiple vertices can be described using Section 7.1, "Cell Boundaries", spatial geometries contain an arbitrary number of nodes for each geometry and include line and multipart geometries (e.g., the different islands of the UK).  The approach described here specifies how to encode such geometries following the pattern in 9.3.3 Contiguous ragged array representation and attach them to variables in a way that is consistent with the cell bounds approach.
A geometry is usually thought to be a spatial representation of a real-world feature. It can be disjoint, having multiple parts. Geometry types are limited to point, multipoint, line, multiline, polygon and multipolygon types. Other types exist and may be introduced in a later version of the specification. Similar to other geospatial data formats, geometries are encoded as ordered sets of geospatial nodes. The connection between nodes is assumed to be linear in the coordinate reference system the nodes are defined in. Parametric geometries or otherwise curved features may be supported in the future.
All geometries are made up of one or more nodes. The geometry type specifies the set of topological assumptions to be applied to relate the nodes. For example, multipoint and line geometries are nearly the same except nodes are interpreted as being connected for lines. Lines and polygons are also nearly the same except the first and last nodes must be identical for polygons. Polygons that have holes, such as waterbodies in a land unit, are encoded as a collection of polygon ring parts, each identified as exterior or interior polygons. Multipart geometries, such as multiple lines representing the same river or multiple islands representing the same jurisdiction, are encoded as collections of un-connected points, lines, or polygons that are logically grouped into a single geometry.
While this geometry encoding is applicable to any variable that shares a dimension with a set of geometriesy, the application it was originally designed for requires that the geometry be joined to the instance dimension of a Discrete Sampling Geometry timeSeries featureType. In this case, any data variable can be given a geometry attribute that is to be interpreted as the representative geometry for the quantity held in the variable. An example of this is areal average precipitation over a watershed. An example of line geometry with time series data is given in Appendix E: Cell Methods.
Geometry Variables and Attributes
A set of geometries can be added to a file by inserting all required data variables and a geometry container variable that acts as a container for attributes that describe a set of geometries. A geometry attribute containing the name of a geometry container variable can be added to any variable that shares a dimension with the geometries. The geometry container must hold geometry_type and node_coordinates attributes. Depending on the geometry_type, the geometry container may also need to contain a node_count, part_node_count, and interior_ring attribute. These attributes are described in detail below.
The geometry_type attribute must be carried by a geometry container variable and indicates the type of geometry present. Its allowable values are: point, multipoint, line, multiline, polygon, multipolygon. The node_coordinates attribute must be carried by a geometry container variable and contains the space delimited names of the x and y (and z) variables that contain geometry node coordinates.
For all geometry types except point, the geometry container variable must have a node_count attribute that contains the name of a variable indicating the count of nodes per geometry. Note that the node count may span multiple geometry parts. For multiline, multipolygon, and polygons with holes, the geometry container variable must have a part_node_count attribute that contains the name of a variable indicating the count of nodes per geometry part. Note that because multipoint geometries always have a single node per part, the part_node_count is not required.
For polygon and multipolygon geometries with holes, the geometry container variable must have an interior_ring attribute that contains the name of a variable that indicates if the polygon parts are interior rings (i.e., holes) or not. The variable indicated by the interior_ring attribute should contain the value 0 to indicate an exterior ring polygon and 1 to indicate an interior ring polygon. Note that single part polygons can have interior rings; multipart polygons are distinct in that they have more than one exterior ring.
The variables that contain geometry node coordinate data, indicated by the node_coordinates attribute on the geometry container variable, are also identifiable through the use of a required cf_role attribute. Allowable values are geometry_x_node, geometry_y_node, and geometry_z_node.
Encoding Geometries
Geometry encoding follows a similar pattern to the contiguous ragged array approach in 9.3.3 Contiguous ragged array representation with some modification to suit the spatial geometry use case rather than observational time series. All spatial data are encoded in the variables indicated by the node_coordinates and appropriate cf_role attribute. These node variables should be one dimensional and total number of nodes long. There are three one dimensional variables that are used to break up and interpret the node variabes: node_count, part_node_count, and interior_ring.
For geometry types requiring a node_count attribute, the node count variable should be the number of geometries long and indicate the number of nodes per geometry. For geometry types requireing a part_node_count attribute, the part node count variable should be the number of geometry parts long and indicate the number of nodes per geometry part. For geometry types requireing an interior_ring attribute, the interior ring variable should be the number of geometry parts long and contain 0s and 1s to indicate exterior or interior.
The ecosystem of polygon specifications and software implementations of those specifications varies in how polygons are encoded. Nodes within a polygon exterior or interior ring are typically encoded in opposite clockwise or anticlockwise direction around the polygon. This is important for operations such as caluclating area. CF requires that outer rings be encoded in anticlockwise order and interior rings be encoded in clockwise order. CF also requires that the first and last node in a polygon be identical to ensure polygon rings are complete.
A coordinate reference system (CRS) (referred to as a grid mapping elsewhere in the CF convention) is strictly required for geometries. The normal CF practice, of attaching a grid_mapping attribute--containing the name of a CRS container variable--to a data variable, can be used and the grid_mapping CRS should be assumed to apply to the geometry. However, the normal grid_mapping, which typically applies to auxiliary coordinate variables and remains optional for use with geometries, can be overridden by attaching a crs attribute that contains the name of a CRS container variable to the geometry container variable. If a grid_mapping is not present on a data variable linked to geometry, a crs attribute is required.
Example 7.14. A multipolygon with holes
This example demonstrates the use of all potential attributes and variables for encoding geometries.
dimensions:
  node = 25 ;
  instance = 1 ;
  part = 6 ;
variables:
  double x(node) ;
    x:units = "degrees_east" ;
    x:standard_name = "longitude" ;
    x:cf_role = "geometry_x_node" ;
  double y(node) ;
    y:units = "degrees_north" ;
    y:standard_name = "latitude" ;
    y:cf_role = "geometry_y_node" ;
  float geometry_container ;
    geometry_container:geometry_type = "multipolygon" ;
    geometry_container:node_count = "node_count" ;
    geometry_container:node_coordinates = "x y" ;
    geometry_container:crs = "crs" ;
    geometry_container:part_node_count = "part_node_count" ;
    geometry_container:interior_ring = "interior_ring" ;
  int node_count(instance) ;
    node_count:long_name = "count of coordinates in each instance geometry" ;
  int part_node_count(part) ;
    part_node_count:long_name = "count of nodes in each geometry part" ;
  int interior_ring(part) ;
    interior_ring:long_name = "type of each geometry part" ;
  float crs ;
    crs:grid_mapping_name = "latitude_longitude" ;
    crs:semi_major_axis = 6378137. ;
    crs:inverse_flattening =<PHONE_NUMBER>63 ;
    crs:longitude_of_prime_meridian = 0. ;
// global attributes:
  :Conventions = "CF-1.8" ;
data:
 x = 0, 20, 20, 0, 0, 1, 10, 19, 1, 5, 7, 9, 5, 11, 13, 15, 11, 5, 9, 7, 5,
    11, 15, 13, 11 ;
 y = 0, 0, 20, 20, 0, 1, 5, 1, 1, 15, 19, 15, 15, 15, 19, 15, 15, 25, 25, 29,
    25, 25, 25, 29, 25 ;
 geometry_container = 0. ;
 node_count = 25 ;
 part_node_count = 5, 4, 4, 4, 4, 4 ;
 interior_ring = 0, 1, 1, 1, 0, 0 ;
 crs = 0. ;

Example E.1. Timeseries with geometry.
dimensions:
  instance = 2 ;
  node = 5 ;
  time = 4 ;
variables:
  int time(time) ;
    time:units = "days since 2000-01-01" ;
  double lat(instance) ;
    lat:units = "degrees_north" ;
    lat:standard_name = "latitude" ;
    lat:geometry = "geometry_container" ;
  double lon(instance) ;
    lon:units = "degrees_east" ;
    lon:standard_name = "longitude" ;
    lon:geometry = "geometry_container" ;
  int crs ;
    crs:grid_mapping_name = "latitude_longitude" ;
    crs:longitude_of_prime_meridian = 0.0 ;
    crs:semi_major_axis = 6378137.0 ;
    crs:inverse_flattening =<PHONE_NUMBER>63 ;
  int geometry_container ;
    geometry_container:geometry_type = "line" ;
    geometry_container:node_count = "node_count" ;
    geometry_container:node_coordinates = "x y" ;
  int node_count(instance) ;
  double x(node) ;
    x:units = "degrees_east" ;
    x:standard_name = "longitude" ;
    x:cf_role = "geometry_x_node" ;
  double y(node) ;
    y:units = "degrees_north" ;
    y:standard_name = "latitude" ;
    y:cf_role = "geometry_y_node" ;
  double someData(instance, time) ;
    someData:coordinates = "time lat lon" ;
    someData:grid_mapping = "crs" ;
    someData:geometry = "geometry_container" ;
// global attributes:
  :Conventions = "CF-1.8" ;
  :featureType = "timeSeries" ;
data:
  time = 1, 2, 3, 4 ;
  lat = 30, 50 ;
  lon = 10, 60 ;
  someData =
    1, 2, 3, 4,
    1, 2, 3, 4 ;
  node_count = 3, 2 ;
  x = 30, 10, 40, 50, 50 ;
  y = 10, 30, 40, 60, 50 ;

The time series variable, someData, is associated with line geometries via the geometry attribute. The first line geometry is comprised of three nodes, while the second has two nodes. Client applications unaware of CF geometries can fall back to the lat and lon variables to locate feature instances in space. In this example, lat and lon coordinates are identical to the first node in each line geometry, though any representative point could be used.

Fixed by #115


Attaching at Startup Example Issue: | would parse as a shell metacharacter on unix terminal

Referring to the "Attaching at Startup example", unix terminal would read | as a shell meta- character
Example Given:
java -javaagent:./agent.jar=<IP_ADDRESS>|8000|/path/to/cert.pem -jar ./application.jar
Example output on MacOS Unix terminal:
 % java -javaagent:./agent.jar=<IP_ADDRESS>|8000|/path/to/cert.pem -jar ./application.jar
zsh: no such file or directory: /path/to/cert.pem
zsh: command not found: 8000

Am i using the agent.jar the right way?

Very true! Yes in a shell you'll need to quote that option. I've just updated the example in the README:
java -javaagent:./agent.jar="<IP_ADDRESS>|8000|/path/to/cert.pem" -jar ./application.jar

I think that should resolve this, so I'll close this issue, but let me know if you're still having trouble.

Thank you!


Alternative for when-directive

I just noticed that the "when" direcitve was removed from version 0.13.0 to 0.14.0.
Why was it removed and what can I use instead?
Thanks for your help! ;-)

The when directive essentially just did some caching for you.
Previously, you would use it like so
import { when } from 'lit-html/directives/when';
 let checked = false;
html`
  ${when(checked, () => html`Checkmark is checked`,
         () => html`Checkmark is not checked`)}
`;

and now you use the cache directive like so
import { cache } from 'lit-html/directives/cache';
 let checked = false;
html`
  ${cache(checked ? html`Checkmark is checked` : html`Checkmark is not checked`)}
`;

when combined two different concepts: conditional rendering and template caching. The approach in 0.14.0 is that we just expose the primitives, and you can combine these things on your own.

Conditional rendering
Conditional rendering in 0.14.0 works by using plain JavaScript features. The most common method is by using the ternary operator:
const template = (condition) => html`

    ${
      condition ?
        html`<h2>It's true!<h2>` :
        html`<p>Not really</p>`
    }

`;

You can use any other JavaScript language feature like if conditionals or calling another function or whatever to determine what you render:
const pickSomething = choice => {
  if (choice === 'bold' ) {
    return html`<b>Fat text</b>`
  } else if (choice === 'italic' ) {
    return html`<i>Super slanty</i>`
  } else {
    return html`<span>So plain</span>`
  }
}

const subFunctionTemplate = (choice) => html`

    ${ subFunction(choice) }

`;

You can use an empty template html``  or empty string '' to render nothing. In the next release you can also use the nothing export to render nothing (with pretty much the same effect).
const template = (visible) => html`

    ${ visible ? html`<h1>I'm here<h1>` : '' }

`;

Template Caching
In all the examples above, when you switch between rendering different templates, the previous content is destroyed, and the new template is rendered from scratch. Sometimes you want to be able to switch between templates but have the old content "cached" so you can switch back and forth without causing a complete re-render of the template. This is what the new cache directive is for.
const template = (visible) => html`

    ${ cache( visible ? html`<p>I'm cached<p>` : html`` )}

`;

Just wrap any of the above statements in cache() and it will cache any templates that are rendered in that position. Note that although it may seem that caching is always better than not caching there is a performance overhead. Using cache will make your application consume more memory, and your application will generally be more efficient without cache. I advise you to not use it unless the size of the template is very large and you expect to switch the rendered content often.

You can see a working version of all the examples above in this pen: https://codepen.io/ruphin/pen/XoXNBR?editors=1010
Maybe some of this material is useful somewhere in the docs @arthurevans

JavaScript ternary expressions or other conditional statements are conditionally executed, so you do not get any reference errors when you do this:
const template = (loading) => html`

    ${
      loading ?
        html`<p>Loading...<p>` :
        html`does not use ${ data } until loading is false` )
    }

`;

Non-executed branches of conditionals are not evaluated by JavaScript at all:
# This gives no errors or anything
true ? 'Something' : UndefinedVariable.nonExistantProperty

when needed the additional functional wrapping () => html.. because both branches of the conditional were passed as arguments to a function. JavaScripts evaluates all expressions that are function arguments by default, regardless of how they are used within the function.

Except
let data = null
html`
${cache(loading ? html`loading...` : html`Welcome to ${data.title}`)}
`;

... now errors and stops the template rendering. That was precisely the reason that when used functions to return the templates, so they weren't evaluated.

Your example does not error as long as the invariant loading ^ (data !== undefined) is valid. In other words, as long as data is defined when loading is false, you cannot get an error.

If you use an example where you evaluate a branch that leads to a reference error, it will throw a reference error. The example you used switches between each template, so it will evaluate the falsy branch of the conditional, and lead to a null reference error. This would happen just the same if you were using when.  Behold: https://codepen.io/ruphin/pen/KbVyKg?editors=1010
If you execute a branch of code that references off of null or undefined, your code will break. It's up to the programmer to ensure that this doesn't happen. when never protected you from that.
What when did, is ensure that only one branch is evaluated, and not both. It did so by requiring that you pass both branches as a function, so it could execute only one depending on the provided condition. With JavaScript ternaries or conditionals, you don't have to do that, because they do this by default. In other words, the () => wrappings that you had with when was a workaround to a shortcoming of when, not an added feature.
TLDR; The following two statements are functionally identical, regardless of the content of the templates:
when(condition, () => html`...`, () => html`...`)

cache(condition ? html`...` :  html`...`)

You are correct, I just picked the one where it was toggling the value, duh!
Anyways, now my unsafeHTML is broken ...

@tkroesch Feel free to join the #lit-html channel on the Polymer slack https://polymer.slack.com/


Allow colons (%3A) in percent-encoded paths

Postgres supports percent-encoded paths to allow for connecting to the DB over a domain socket since this change, and it would be super helpful to allow percent-encoded colons as well. That way, dj-database-url could be used with Google Cloud SQL, because its socket names are in the format /cloudsql/{project-id}:{sql-instance-id}. Without percent-encoding the colon, it gets interpreted as an invalid port. Adding it would support connection strings like this, like Postgres:
>>> dj_database_url.parse('mysql://root@%2fcloudsql%2fproject-id%3asql-id/database')
{'ENGINE': 'django.db.backends.mysql', 'HOST': '/cloudsql/project-id:sql-id', 'NAME': 'database', 'CONN_MAX_AGE': 0, 'PASSWORD': '', 'PORT': '', 'USER': 'root'}

I have an existing patch if that would be helpful.

A patch would be great.

Implemented by https://github.com/jazzband/dj-database-url/pull/181 which is now merged


deps: downgrade protobuf to 3.17.3 (not the latest 3.18.0)

@Neenu1995 This version is the same as the version in the last release of the shared-dependencies BOM.
https://search.maven.org/artifact/com.google.cloud/first-party-dependencies/2.2.1/pom

Simply downgrading it failed the check:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for com.google.protobuf:protobuf-java-util:3.17.3 paths to dependency are:
+-com.google.cloud:google-cloud-bigquery:2.1.10-SNAPSHOT
  +-com.google.cloud:google-cloud-core:2.1.4
    +-com.google.protobuf:protobuf-java-util:3.17.3 (managed) <-- com.google.protobuf:protobuf-java-util:3.18.0
...

https://github.com/googleapis/java-shared-dependencies/pull/476/checks?check_run_id=3668210382

Downgrading protobuf to 3.17.3 in java-core to avoid conflicts.
https://github.com/googleapis/java-core/pull/562


Adapter trimming in exomeSeq

I am having issues with adapter contamination in tumor samples from my exomeSeq data. But I don't see an option to trim adapters in exomeSeq config files. When I add the following lines to the config file, it gives the error "yaml.scanner.ScannerError: mapping values are not allowed here
in "/arcusdata/au/pact131_exomeseq/config/exomeseq_config.yaml"
1 trim_reads: atropos
2      adapters: [nextera2]
But I do have adapter content in more than 10% of my sequences. Is this not a high enough number where adapter trimming will be needed?

Originally posted by @audyavar in https://github.com/bcbio/bcbio-nextgen/issues/308#issuecomment-466594931

The error you are getting is because your YAML file is malformed, I think you might not be adding the lines in the right way. https://github.com/bcbio/bcbio-nextgen/blob/master/tests/data/automated/run_info-rnaseq.yaml#L15-L16 has an example of how they should be added.

Closing this as this definitely should be the problem. Hope you got it working!


ItemPredicateParser doesn't support 3rd-party enchant plugin

As in the case mentioned in #1, even though compatibility support is added separately for EcoEnchants, it seems that other plugins get the same error, and it would be tiresome to add separate support for most plugins i think
In fact, I think it might not be just enchantment plugins that have this problem, but other types of plugins as well perhaps
[20:15:04 ERROR]: [ItemPredicateParser] Could not download and or initialize languages
java.lang.IllegalStateException: Could not locate translation-value for key enchantment.minecraft.poisoned_arrows
        at ItemPredicateParser-0.0.7 (1).jar/me.blvckbytes.item_predicate_parser.translation.TranslationRegistry.createEntries(TranslationRegistry.java:111) ~[ItemPredicateParser-0.0.7 (1).jar:?]
        at ItemPredicateParser-0.0.7 (1).jar/me.blvckbytes.item_predicate_parser.translation.TranslationRegistry.initialize(TranslationRegistry.java:47) ~[ItemPredicateParser-0.0.7 (1).jar:?]
        at ItemPredicateParser-0.0.7 (1).jar/me.blvckbytes.item_predicate_parser.translation.LanguageRegistry.initializeTranslationRegistry(LanguageRegistry.java:91) ~[ItemPredicateParser-0.0.7 (1).jar:?]
        at ItemPredicateParser-0.0.7 (1).jar/me.blvckbytes.item_predicate_parser.translation.LanguageRegistry.<init>(LanguageRegistry.java:50) ~[ItemPredicateParser-0.0.7 (1).jar:?]
        at ItemPredicateParser-0.0.7 (1).jar/me.blvckbytes.item_predicate_parser.ItemPredicateParserPlugin.onEnable(ItemPredicateParserPlugin.java:41) ~[ItemPredicateParser-0.0.7 (1).jar:?]
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:288) ~[paper-mojangapi-1.21.1-R0.1-SNAPSHOT.jar:?]
        at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.enablePlugin(PaperPluginInstanceManager.java:202) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.enablePlugin(PaperPluginManagerImpl.java:109) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:520) ~[paper-mojangapi-1.21.1-R0.1-SNAPSHOT.jar:?]
        at org.bukkit.craftbukkit.CraftServer.enablePlugin(CraftServer.java:640) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:589) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:753) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:515) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:329) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1214) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:329) ~[paper-1.21.1.jar:1.21.1-99-1bc02e6]
        at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]

This key is from https://github.com/nulli0n/ExcellentEnchants-spigot

Right, I see - thank you for letting me know! I can easily add support for as many plugins as there are, as long as they provide an API which lets me retrieve the display-name of what hey add to the Registry. But I see what you're getting at: I should probably stop throwing an actual exception, but rather only log a warning-message, to let the user know that they are potentially missing out on some entries which cannot be accessed by the parser.

The latest release should now support ExcellentEnchants, and will no longer throw and thereby disable the plugin if a key cannot be located. Please once again test it locally, :).

Seems to be fine, thanks for your amazing work


Front-end integration for disabled subservers

This PR creates a new SubServerStatus store which checks which services are being run by litd. When loop and pool are not running or are in an error state, the page displays an error message:

Depends on #541

Also for the svg, we might want to tweak the color to be fill="currentColor" instead of fill="none"

ACK to @jbrill's SVG comment!

@itsrachelfish, remember to re-request review from reviewers when ready

@jbrill: review reminder
@itsrachelfish, remember to re-request review from reviewers when ready

@jbrill: review reminder
@itsrachelfish, remember to re-request review from reviewers when ready

@jbrill: review reminder
@itsrachelfish, remember to re-request review from reviewers when ready


feat: may challenge

Closes https://github.com/GaloyMoney/galoy-mobile/issues/3176

@sandipndev e2e are not passing but I'm assuming it's unrelated


Error on npx docusaurus generate-proto-docs

Hi @AnthonyBobsin!
Project looks very cool, been trying to add it to my docusuarus wiki but haven't been able to.
I'm following the instructions.
I have a generated proto_workspace.json in the ./fixtures dir but when I run
npx docusaurus generate-proto-docs, I see the following error
Error: The docs folder does not exist for version "current". A docs folder is expected to be found at protodocs.
    at checkVersionMetadataPaths (/Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/plugin-content-docs/lib/versions.js:233:15)
    at /Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/plugin-content-docs/lib/versions.js:309:51
    at Array.forEach (<anonymous>)
    at Object.readVersionsMetadata (/Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/plugin-content-docs/lib/versions.js:309:22)
    at Object.pluginContentDocs [as plugin] (/Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/plugin-content-docs/lib/index.js:28:41)
    at /Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/core/lib/server/plugins/init.js:149:55
    at Array.map (<anonymous>)
    at Object.initPlugins [as default] (/Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/core/lib/server/plugins/init.js:137:10)
    at externalCommand (/Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/core/lib/commands/external.js:15:35)
    at async run (/Users/aesadde/repos/akorda/docs/node_modules/@docusaurus/core/bin/docusaurus.js:245:5)

Is there anything I'm missing?
Thanks for the help

It turns out that the plugin doesn't generate the directories and file it needs. They need to exist prior to running the tool.


Tokens fixes

The only functional change is to make sure osbs.conf-specific token (whether 'token' or 'token_file') can be overridden.

LGTM


Supervisor compiles on Windows

Signed-off-by: John Howard<EMAIL_ADDRESS>Next step - compiling the supervisor package on Windows @crosbymichael @mlaventure

Jenkins green. Next stop api\grpc...


Unneccesary Java 8 dependency?

Hi,
It appears that the source/target version is not specified in the pom.xml file, and a dependency on Java 8 byte code version is introduced by the machine that creates the jar files (that find their way to Maven Central).
This caused some issues for me at runtime, and thought you might want to know that your library might be more useful to others in Maven Central if you specifically target java 7 (or 6?) in the pom file.

We rely on Java 8 features.
Use boon from the boon project if you want Java 7 support.
https://github.com/boonproject/boon
It also has more docs.


Implement basic test suite

This PR defines the necessary files / configuration entries to make testing available within the project, in addition to a small set of component tests. The main libraries that were used to implement and run the tests are:

Jest: serving as a test runner.
Enzyme: serving as components access point.
Testing-library: serving as components virtual renderer.

Additional changes

The project CI workflow now includes a test step.
The project Makefile now includes a test rule (replacing the one on package.json).
The project README now includes a Testing section.

💥 Caveats
Given Enzyme lack of React 17 support (PR in progress), an alternative adapter was temporarily used.
📚 References

[Youtube] Intro to React Testing
[GitHub] Enzyme lack of React 17 support

Finally, the base image used for the Dockerfile has been updated to node:15.14-alpine.


Do not print sensitive properties' values in logs

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

I can get the idea to.prevent data link, but the implementation seems not elegant.
Coukd you add an annotatio(SecurityConfig) for the module config field? And leverage that flag to output ******(if set) or empty

Hard code would not be a good practice, as OAP is high modularization and easy to add new module as extension.

What do you suggest?

I can get the idea to.prevent data link, but the implementation seems not elegant.
Coukd you add an annotatio(SecurityConfig) for the module config field? And leverage that flag to output ******(if set) or empty

I mean this.
Every module config should take their own responsibilities to declare this.
And the core only hide when needed.

We'd either not to log the configurations at all if you insist hardcode is not an option

I can get the idea to prevent data leak, but the implementation seems not elegant.
Coukd you add an annotatio(SecurityConfig) for the module config field? And leverage that flag to output ******(if set) or empty

That's impossible, when printing the logs the configurations are still in Map type, there is no ModuleConfig type involved at this time, not to say a new annotation

At the same time I think it's unnecessary to do the complex work just for printing logs, I just removed the logs to print configurations.

As a quick fix, the current implementation will work. However, I am totally with @wu-sheng suggestion to "modularize" it and wanted to suggest more or less the same. But as a follow up that could be tackled in the near future.
So, the final solution is to not print any configuration properties, until we implement in a standarized way, isn't it?

The logs are printed too early as soon as they are read, before they are deserialized into the configuration beans, so there is no way to add an annotation to those module config and leverage that annotation to determine whether or not to print the logs, if the logs are really needed they must be moved to somewhere after the configs are deserialized into the configuration beans


[!] Unable to find a specification for Flex when using cocoapods

On the latest cocoapods version (0.37.1), cocoapods generates the following error when doing pod install :[!] Unable to find a specification for `Flex`
To replicate:

Update cocoapods to 0.37.1
pod install

What is the line in your podfile? Perhaps CocoaPods is now case sensitive. The name of the pod is 'FLEX'.
If changing the case doesn't help, I suggest you open an issue with CocoaPods. The FLEX spec does show up in CocoaPods search: https://cocoapods.org/?q=flex

The line is 'Flex'. I'll check to see it 'FLEX' fixes it.


Pull Request: Add "About" Page to LisBook Project

This pull request introduces a new "About" page (about.html) in the LisBook project. The page includes:

A brief description of the LisBook project and its purpose.

A section listing the contributors and maintainers, which includes:

Name
Profile picture or avatar (optional)
GitHub username with a link to their profile
A link to the "About" page included in the navigation bar for easy access.

Styling applied using CSS and Bootstrap to ensure consistency with the overall design of the app.

Testing to verify functionality on both desktop and mobile devices.

Amazing @YakeDev I'm loving your dedication and passion for programming. Keep it up 👍🏼

Amazing @YakeDev I'm loving your dedication and passion for programming. Keep it up 👍🏼

Thank you @Ctoic

Just reviewing your code soon i will merge this one as well.


Fix bug where no egress traffic is allowed in k8s backend

When using the Kubernetes backend, no egress policy is created (since k8s NetworkPolicy does not support egress).
The result is that applying NetworkPolicy causes Pods to lose egress connectivity.  This PR fixes that by using Namespaces to generate Policies which allow traffic based on the Namespace policy (previously done with Calico Profiles).
It also renames the automatically generated Calico Policy names so that it is distinguishable whether the Policy is backed by a NetworkPolicy or a Namespace.

@matthewdupre do you want to take a second look?
I've also added a bunch of testing.


Control Container Capabilities?

This is a feature request, not a bug report.
It looks like the OpenWhisk Invoker automatically drops the Net Admin Capability for all Action containers. Is it possible to keep this capability on a per Action basis?
Invoker with --cap-drop
If not, is it possible to add functionality to configure the capabilities on a per Action basis?
I want this because I have a use case where using tools like tc to throttle bandwidth would be useful. As these are lightweight & periodic tasks, I think FaaS/Serverless via OpenWhisk is the right way to go.
Expected Results
To be able to configure capabilities of container when configuring the Action.
Actual Results
NET_RAW & NET_ADMIN are explicitly stripped by the Invoker. There appears to be no way to configure capabilities.

It's easier to make this a deployment time parameter for the system vs per action. Did you mean per action?

@rabbah - Please bear with me, I'd like to clarify terminology & make sure I'm using it correctly!
I'm currently assuming that what you're saying is that it would be easier to add this feature so it's system-wide & affects all actions equally?

I'm currently assuming that what you're saying is that it would be easier to add this feature so it's system-wide & affects all actions equally?

correct.

I'm guessing it may have inspired the --cap-drop in the Invoker.

I'll defer to @jeremiaswerner and @markusthoemmes on the details but in general yes.
Another relevant question: Are you using kubernetes to deploy opnewhisk?

Yes. Currently evaluating it for my use case on a local minikube setup.

cc @dgrove-oss

You could pretty easily change these from hard coded to system-wide configurations by setting them as default values on the whisk.container-factory.container-args.extra-args config:
https://github.com/apache/incubator-openwhisk/blob/d7c9fd661a8a5b339f20b3f549bfa4fa47124706/core/invoker/src/main/resources/application.conf#L55
(and deleting the hard coded bits in InvokerReactive)
To do this per action may be weird though, since generally you will want to maintain some restrictions over args passed to docker run, I think.
To keep that control, but make it accessible, you might be able to add something like extra-args that are based on image name, so that you (as OW operator) can allow only some specific images to be launched with a different set of args.

Piggy-backing on this thread: What is the exact syntax to use in this case? I want to pass --device=/dev/mydev to docker run. How would that be encoded in extra-args? Thanks!

Figured it out myself: extra-args: { "device": ["/dev/mydev"] }


[THIS PAGE IS BEING MONITORED BY STATE AND FEDERAL LAW ENFORCEMENT](mailto<EMAIL_ADDRESS>

[THIS PAGE IS BEING MONITORED BY STATE AND FEDERAL LAW ENFORCEMENT](mailto<EMAIL_ADDRESS>{153974_2020_SUMMONS__POST_RJI___51}
153974_2020_SUMMONS__POST_RJI___51  8 JULY 2020(NOTARIZED) SUPREME COURT PROCEDURE
{153974_2020_AFFIRMATION_223 - UNLAWFUL FEES}
SUPPORT USC TITLE 18.215 VIOLATED
{153974_2020_DOCKET_31 - ANNE BRANDON - LAURIE ZUCKER - NOTARIZED APRIL 11TH IN CA [00025]}(https://github.com/WILSON-ELSER-STATEFARM-SULLIVAN-ZUCKER/FEDERAL-USE-AND-DISTRIBUTION-ONLY/files/9174077/00031.153974_2020.-.ANNE.BRANDON.-.LAURIE.ZUCKER.-.NOTARIZED.APRIL.11TH.IN.CA.00025.pdf)
THIS PAGE HAS ALREADY BEEN ARCHIVED - AS HAVE ALL THE OTHER INFORMATION
'''https://github.com/BSCPGROUPHOLDINGSLLC/ELSER-AND-DICKER/pull/5'''

@WILSON-ELSER-STATEFARM-SULLIVAN-ZUCKER
Originally posted by @153974-HSI-OXLEY-BANKS-40ACT in https://github.com/WILSON-ELSER-STATEFARM-SULLIVAN-ZUCKER/FEDERAL-USE-AND-DISTRIBUTION-ONLY/pull/12#issuecomment-1207704335

https://saaze2311prdsra.blob.core.windows.net/clean/b67c1a2d29d6ec11a7b5002248307b90/04.12.2022.151652.EY.PWC.MSCO-.pdf


Rename flax.linen to flax.nn?

Are there plans to rename flax.linen to flax.nn eventually?

Hi @PhilipVinc, yes, we actually discussed this during our weekly meeting two weeks back. It seems a good idea. If we do this, we will probably keep the alias linen around to avoid breaking our internal users, but eventually everyone should just be able to do from flax import nn.
Since Linen is around for so long, it isn't really necessary anymore to distinguish between "Flax Linen" and "Flax pre-Linen". Instead, we should probably just call our neural networking library "Flax" 😄 .

I will look into this, but not before the end of the year, so most likely in the beginning of 2023.

Thanks for the info!

bump

@marcvanzee

@PhilipVinc thanks for the reminder. When @marcvanzee is back we'll revisit this. Bear with us.


Catch edge case where the CN and DNSNames on a Certificate have been reordered

What this PR does / why we need it:
Catches an edge case picked up and reported by @damienwebdev when a user changes the common name specified on the certificate, but does not change the overall set of domains listed on the cert (i.e. the names on the cert are re-orded).
Special notes for your reviewer:
This should also be cherry-picked into release-0.4 along with #801 and #802
Release note:
NONE

/retest
/cc @kragniz

it'd be nice to have a test case for this as well

Agreed - the code here is currently not well tested, and thus it'll require test fixtures to be built in order to add a test for this case.
#788 has got a test fixture built for this, which we may be able to port across. Otherwise, we will be adding test cases as part of #788 for all these sorts of things 😄

Bump for GitHub search re-index.


Settings does not allow usernames with numbers

To recreate:

In account management, create a user with username involving letters and numbers
In add-in, go to settings and try to set up the user

Result: application throws error, specifying username may only contain letters and the dot "."

issue has been fixed and will shortly be in pull request

Issue fixed in #11 pull request. Closing ticket.


Route name should allow 0-9

Right now name only accepts [A-Za-z\-] but I'm trying to use it with a customer ID which has 0-9. Happy to PR this if you're interested.
https://github.com/TestArmada/drydock/blob/0b5923816a4951a7db6de1a3f6bf383819449cfe/lib/schemas.js#L25
drydock.jsonRoute({
  name: "ABC0001",
  method: "GET",
  path: "/customers/ABC0001",
  handlers: {
    "success": {
      description: "Return customer ABC0001",
      handler: function () {
        return require("./data/customers-ABC0001.json");
      }
    }
  }
});

PR welcome for this also.  Thanks!


[Automation] Generate Fluent Lite from Swagger customer-insights#package-2017-04

[Automation] Generate Fluent Lite from Swagger customer-insights#package-2017-04

/azp run java - customerinsights - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-customerinsights

Generated mock test lack required properties: https://dev.azure.com/azure-sdk/public/_build/results?buildId=4241179&view=logs&jobId=c3c349d7-cf1d-5cce-4157-37f3077e2ff3&j=c3c349d7-cf1d-5cce-4157-37f3077e2ff3&t=37b5cd15-1e34-5513-7a83-b6bdf4bd3ec7


Search doesn't work

When using the Picker with the Font Awesome Pro Version the search doesn't work, I get the attached error.

could you share a single icon declaration from your icons.yml?

Here are a few examples
500px:
  changes:
    - '4.4'
    - 5.0.0
  label: 500px
  search:
    terms: []
  styles:
    - brands
  unicode: f26e
  voted: false
abacus:
  changes:
    - 5.3.0
  label: Abacus
  search:
    terms:
      - addition
      - ancient
      - arithmetic
      - calculator
      - counting
      - hexadecimal
      - math
      - subtraction
  styles:
    - solid
    - regular
    - light
    - duotone
  unicode: f640
  voted: false
accessible-icon:
  changes:
    - 5.0.0
  label: Accessible Icon
  search:
    terms:
      - accessibility
      - handicap
      - person
      - wheelchair
      - wheelchair-alt
  styles:
    - brands
  unicode: f368
  voted: false

that's strange. They seem identical to the free ones.
Do the free ones wirk for you?

Yes, free ones are working. Maybe it's cause I use it on the site and not a page? But should be similar right? Should I provide you with the whole file?

site or page shouldn't matter, actually I'm doing my tests on the site, too. Would you email me file? it's<EMAIL_ADDRESS>

I have send you a package with all necessary files 😃

Got it :)
it was the cctv icon causing problems, it had 1984 as search term and that was interpreted as number (not a string) therefore the "toLowerCase" function didn't exist.

Just want wo mention the great work so far. Good job!

Works 😃


Missing folder required within Dockerfile

In Dockerfile there is this command: COPY frontend/build . but build folder is missing in GitHub repo.

It gets built during CI
https://github.com/techno-tim/techno-broadlink/blob/master/.github/workflows/main.yml#L25

go to frontend and run
yarn install
and then
yarn build
If you have node > 16 replace line 27 and 28 of package.json with
"start": "react-scripts --openssl-legacy-provider start",
"build": "react-scripts --openssl-legacy-provider build",


WIP: docker content trust signing for images

PR Description
docker content trust signing for images

Commented on the web3signer version of this, but doesn't this break multi arch support?

As discussed, it does appear this breaks multi-arch support. Going to up the review to "request changes" while we sort this out just so no one gets carried away and merges it before then. It can be really easy to miss the fact multi-arch was broken if you are running on intel. :)

Yep, I'll ping once I have this sorted either with arch in the tag or equivalent. Have set the title to WIP

I'm going to close this one for now just to keep things tidy but feel free to reopen if you get back to looking at this.


[Bug]: .puppeteerrc.cjs is ignored in monorepo context

Bug description
Steps to reproduce the problem:

Initiate a monorepo with turborepo and yarn
Add a workspace
Add a .puppeteerrc.cjs file to this workspace that rewrite the cacheDirectory
Run yarn from the root of the monorepo

As I mentionned it in the title, .puppeteerrc.cjs configs are ignored when install command is run elsewhere than the location of the package.json file that installs puppeteer. In a monorepo context, install commands are performed at the root, not in a workspace. It would be great to have some of the configs available through envs, like cacheDirectory.
Puppeteer version
19.5.0
Node.js version
16
npm version
yarn 1
What operating system are you seeing the problem on?
Linux, Windows
Configuration file
No response
Relevant log output
No response

See https://pptr.dev/guides/configuration#environment-variables


@conda-forge-admin, please rerender

Additional comment:
@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/aemcmc-feedstock#14.


Execution page doesn't display execution correctly

https://testnet.iotexscan.io/action/26f776cf89bc0a091fde0458d1d5a7ffdd12fd22f84e4bd0f376ce93530809d1

data = "10f5a5c000000000000000000000000023684c7e4c9a8a67f9ad24cc19650aa2b8863df8"
method = undefined, data = "10f5a5c000000000000000000000000023684c7e4c9a8a67f9ad24cc19650aa2b8863df8"
method


refactor(pirateship): psrowheader to stateless func comp

Testable in pirateship More menu:

replaced by https://github.com/brandingbrand/flagship/pull/507


Decide on gravatar

Either keep it and make the image smaller, or remove it and remove Minerva's dependency on the gravatar plugin.
See this comment.

Vehemently opposed to keeping the gravatar - :hand:

I can't imagine a stronger opinion, the nays carry the day.


Remove Display Version from Azul.Zulu.11.JDK

Newer versions have the proper display version. Since the ISV has had the issue fixed for some time, it seems a better course of action to remove the DisplayVersion from the relatively few manifests that have it rather than updating the manifests without it.

microsoft/winget-cli#4459

Microsoft Reviewers: Open in CodeFlow

Intentionally didn't bump version

URL: https://cdn.azul.com/zulu/bin/zulu11.31.11-ca-jdk11.0.3-win_x64.msi
OK
(Automated message - build 882)


Animation effect on the image when a cursor hovers over it

When you hover over the image, it will appear to "lift" off the page with a smooth animation, along with a subtle shadow effect.
It will enhance the process of ordering any item for the "our coffee selection".

@Mujtabaa07 I will start contributing after 31st of dec.

@Mujtabaa07 Can I start contributing after 31st of dec?

Sure

@Mujtabaa07 Thank you!!

can i help

Hi , I am new to open source and would love to contribute to this project.This issue seems interesting , and i'd like to work on it . could you assign this issue to me?

Hi , I am new to open source and would love to contribute to this project.This issue seems interesting , and i'd like to work on it . could you assign this issue to me?

Sure you can work on it but the issue has been assigned, feel free to raise the new issue and work on


Knapsack - State Rotation

This involves the technique of state rotation in dynamic programming.

According to hacktoberfest 2022 rules you can only make one valid PR in any specific repository, so request you to please not make a lot of contribution in a single repository otherwise it will get marked as spam. Hope you can understand it and will keep in mind from ahead.


mkltfs does not work properly

Description
mkltfs -d /dev/st0 always leads to the following error message,
LTFS11261E Cannot load plugin: /usr/local/lib/ltfs/libdriver-ltotape.so: undefined symbol: fuse_opt_parse
Mount, copy Data to Tape, Restore Data from Tape, unmount is possible without any issues. (Tape was already formated via ltfs in another pc)
Environment

OS:              Linux
Distribution:    Ubuntu 16.04.4 LTS
Architecture:    x86_64
Additional info: -

How to recreate

Thank you for opening the issue.
I think we and IBM never provide the tape backend module "libdriver-ltotape.so". Did you try the code on this repository?
First of all, could you clarify the version of LTFS you are facing this problem?

Hello,
sorry i mixed up some error messages, this is the actual error i get , when i use the current source from this git
LTFS11261E Cannot load plug-in: /usr/local/lib/ltfs/libtape-sg-ibmtape.so: undefined symbol: fuse_opt_parse.
LTFS15008E Cannot open backend 'sg'.

Hi, Thank you for your clarification.
I made a confirmation on my bench, "Ubuntu 16.04.03 xenial". It seems that mkltfs and ltfsck don't link libfuse dynamically on that machine. It is linked in RHEL or CentOS. I don't know what the difference of that at this time.
Could you use the following patch for the time being? I can load libtape-sg-ibmtape.so correctly on my bench. But I need to test this patch doesn't create any side effects on other platforms.
diff --git a/src/tape_drivers/linux/sg-ibmtape/Makefile.am b/src/tape_drivers/linux/sg-ibmtape/Makefile.am
index fe9d00c..6543bbc 100644
--- a/src/tape_drivers/linux/sg-ibmtape/Makefile.am
+++ b/src/tape_drivers/linux/sg-ibmtape/Makefile.am
@@ -41,7 +41,7 @@ AM_LIBTOOLFLAGS = --tag=disable-static
 libtape_sg_ibmtape_la_SOURCES = sg_scsi_tape.c sg_ibmtape.c ibm_tape.c
 libtape_sg_ibmtape_la_DEPENDENCIES = ../../../../messages/tape_linux_sg_ibmtape_dat.o ./libtape_sg_ibmtape_la-reed_solomon_crc.lo ./libtape_sg_ibmtape_la-crc32c_crc.lo
 libtape_sg_ibmtape_la_LIBADD = ../../../../messages/tape_linux_sg_ibmtape_dat.o ./libtape_sg_ibmtape_la-reed_solomon_crc.lo ./libtape_sg_ibmtape_la-crc32c_crc.lo
-libtape_sg_ibmtape_la_LDFLAGS = -avoid-version -module
+libtape_sg_ibmtape_la_LDFLAGS = -avoid-version -module -lfuse
 libtape_sg_ibmtape_la_CPPFLAGS = @AM_CPPFLAGS@ -I ../../.. -I ../..

 ibm_tape.c:

Hello,
thanks for having a look at this issue. Since i am not a  professional, how do i apply this patch ? Thanks in advance

That's the good news that your problem was solved. I will fix this problem in next few days with test on other platforms.
You can use a patch like following process.

Create a text file, like dynamic_link.patch, which has a text from diff to ibm_tape.c: in my previous comment
Goto the top directory of your local repository
Apply the patch using patch command like patch -p1 < dynamic_link.patch

It's a good news that the problem was gone on your environment! I will commit the fix after checking this patch causes another problem on other platforms in a few days.
Following is general info to patch the code.

Create a text file like dynamic-link.patch which has the patch, from diff - to  ibm_tape.c: in my previous comment
Go  to the top directory of the repository
Apply patch using patch command like patch -p1 < dynamic-link.patch

Hi @lucasvr,
Do you know anything about this topic?
On RHEL7/CentOS7, -l fuse is not required to create libtape-sg-ibmtape.so. But on Ubuntu16, it seems to be required. In my understanding, -l fuse is not required because libtape-sg-ibmtape.so is loaded from libltfs.so and libltfs.so links libfuse.so.
I believe the dynamic linker behavior is different from RHEL and Ubuntu. Do you have any knowledge about this difference ?

Just to report the findings that @piste-jp-ibm and I made on this topic:
Ubuntu recently decided to enable --as-needed by default. What that flag does is to attempt to prune dependencies added to LDFLAGS but not actually used by the executable.
The thing is, we link mkltfs to libfuse, but mkltfs itself does not use any function from that library. Rather, what happens is that libtape-sg-ibmtape.so, a loadable "plugin", attempts to use a function from the FUSE library called fuse_opt_parse. Since Ubuntu's linker pruned libfuse from mkltfs, we now get an error when the plugin is loaded, since neither that plugin nor mkltfs have that symbol anymore.
I see two options to fix this problem. The first is to link mkltfs with -Wl,--no-as-needed to prevent the linker from stripping down the dependencies. The second is to apply the patch @piste-jp-ibm posted above. That guarantees that the actual user of the library links to it. That approach will work regardless of the linker flags present at build time.