Add checkbox to hint for unreliable (UDP) topic transport for DisplayFilter based plugins.

Added "Unreliable hint" option to base MessageFilterDisplay template
class.
This allows the user to choose the option to use UDP unreliable TransportHints for high throughput topics in a bandwidth constrained environment where TCP retransmits cause more congestion.

Verified that saving the rviz config shows Unreliable: true for topics selected with the option.
Also verified in wireshark that UDP is correctly used for topics selected and publishers that support it.

Cool, the code changes look good. I'll try to test it out this weekend or the beginning of next week.
Thanks.

This is great! Thanks for the pr. I was also able to see the laser data from stage come over UDP using wireshark.


Container locator customizations

With this PR we can allow different string replacements on the ContainerLocator, simplifying a small customization without the need to reimplement the whole class and rebind the middleware.
Tested changes on ContainerLocator, SP doesn't have tests but change does not break backwards compat. Config should be republished but defaults work anyway.

Thanks


CA-242397: Fix format exception caused by incorrect  chunk reading

Improved the ReadHttpHeaders function, by making sure that a chunk is read fully from the stream (the number of bytes read by the Stream.Read function can be less than the number of bytes requested, so we need to continue reading until the required number of bytes is read)
Signed-off-by: Mihaela Stoica<EMAIL_ADDRESS>

Looks fine. Merging.


Leanplum utilizes bitcode by default and causes errors to occur for other non bitcode pods

Leanplum SDK utilizes Bitcode generation forced into Xcode project. This is as a result of the .podspec ->
https://github.com/Leanplum/Leanplum-iOS-SDK/blob/702cce97404e9aca15f5554139f337a6ca0a4cc4/Leanplum-iOS-SDK.podspec#L30
Errors Received:
bitcode bundle could not be generated because '<PATH_TO_POD_WITHOUT_BITCODE>' was built without full bitcode.
As a user not utilizing Bitcode generation I either have to change this in Xcode after every pod install or pod update. An alternative to fix is to always implement something on the pod level to change the flag of BITCODE_GENERATION_MODE to either marker or no.
Specifications

Version: SDK Version 2.2.+
Platform: iOS
Subsystem: Cocoapods

@kyleleanplum
I'm still experiencing this issue after attempting to update to SDK Version 2.4.0.  Any idea when it might be fixed?
Thanks,
Hino

@hbanzon while we're looking into this, have you tried the option here to override the config settings in the Podfile? https://stackoverflow.com/questions/32640149/disable-bitcode-for-project-and-cocoapods-dependencies-with-xcode7

@e7mac thank you for quick response.  We have evaluated this option and we need this fixed instead in order for us to update beyond v2.1.x of the SDK.

The release 2.4.1 has this fixed


stm32f2 RingBufferedUartRx doesn't automatically start() if background DMA isn't running

I noticed a regression in my application when upgrading from crates.io to current main, it seems the start() detection in read() has stopped working:
// Start background receive if it was not already started
if !r.cr3().read().dmar() {
    self.start()?;
}

When trying to read I consistently get overruns (because the DMA probably isn't running). If I call start() myself it works, until an error occurs and the DMA again doesn't restart.
I tried to bisect but the changes across many APIs made this difficult, but I'm hoping with the specific issue found someone with more domain knowledge can help (I only passively intake what goes on development-wise here).
Will try and add a min repro soon.

Here is the min repro: https://github.com/embassy-rs/embassy/compare/main...MabezDev:embassy:mvp?expand=1
It seems that actually calling start() doesn't help either. Here is the log from running the example:
0.000122 INFO  Hello World!
└─ uart_dma::____embassy_main_task::{async_fn#0} @ src/bin/uart_dma.rs:19
0.000946 TRACE USART: presc=1, div=0x0000008b (mantissa = 8, fraction = 11)
└─ embassy_stm32::usart::configure @ /home/mabez/development/rust/embedded/util/embassy/embassy-stm32/src/fmt.rs:117
0.002441 TRACE Using 16 bit oversampling, desired baudrate: 115200, actual baudrate: 115107
└─ embassy_stm32::usart::configure @ /home/mabez/development/rust/embedded/util/embassy/embassy-stm32/src/fmt.rs:117
5.294006 INFO  Read 1bytes
└─ uart_dma::____embassy_main_task::{async_fn#0} @ src/bin/uart_dma.rs:51
5.295166 ERROR panicked at src/bin/uart_dma.rs:50:47:
called `Result::unwrap()` on an `Err` value: Overrun
└─ panic_probe::print_defmt::print @ /home/mabez/.cargo/registry/src/index.crates.io-6f17d22bba15001f/panic-probe-0.3.1/src/lib.rs:104
Frame 0: "HardFault handler. Cause: Escalated UsageFault (Undefined instruction)." @ 0x08016f4c
Frame 1: __udf @ 0x080072c4 inline
       /home/mabez/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/../asm/inline.rs:181:5
Frame 2: udf @ 0x00000000080072c4
       /home/mabez/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/asm.rs:43:5
Frame 3: print @ 0x0800735a
       /home/mabez/.cargo/registry/src/index.crates.io-6f17d22bba15001f/panic-probe-0.3.1/src/lib.rs:103:1
Error: CPU halted unexpectedly.

Any ideas?

I guess reading 1 byte could mean the DMA simply isn't running at all, and its just pulling one byte from the FIFO and overrunning?

Looking into this issue again, its seems one of the issues has been solved, but I've cornered the other. I've updated the minimal repro, it seems its set_config that breaks things. The DMA fails to start once a call to set_config has been made.

Narrowing it down further, it's the call to self.teardown_uart() that breaks the DMA


RFC: ESIP-11 - Transferring (and bulk) of ethscriptions, through Blobs

Since we are going with CBOR for ESIP-8 #17, it makes transferring (bulk and not) even cheaper because the ethscription size will be static data:;rule=esip6, and blob space is cheap.  This also allows for transferring to multiple different addresses in one go, which can be useful for AIRDROPS to a bunch of people.
It could be something like, CBOR containing transfers which is an array of to, transaction_hash objects.
{
  transfers: [
    { to_address: '0xd9F6...992f', transaction_hash: '0x0cbddcfda...53b7c99dc6'  },
    { to_address: '0x3e7a...e5b5', transaction_hash: '0x1234'  }
    { to_address: '0xF64b...46e8', transaction_hash: '0x567'  }
  ]
}

The from is clear, it's the creator of the blob transaction.
Currently the ESIP-8/CBOR creation should take this into account and only do its stuff when cbor.content is detected.
Here's my handling
const inputData = `0x${fromTxBlobs(blobs)}` as `0x${string}`;

const inputBytes = tryUngzip(hexToBytes(inputData));

// that's not ESIP-8-spec compliant, but i'm handling/support non-cbor-ed blobs too.
const data = inputData.startsWith('0xb90002') ? decodeCborX(inputBytes) : { content: hexToBytes(inputData) };

if (data.content) {
  data.content = tryUngzip(data.content);
  data.size = data.content.length;

  // raw json handling
  let rawJson;
  try {
    const str = bytesToString(data.content);

    rawJson = JSON.parse(str.startsWith('data:') ? str.slice(str.indexOf(',') + 1) : str);
    data.mimetype = 'application/json';
    data.content_json = rawJson;
  } catch {}

  if (!rawJson && data.mimetype && data.mimetype.includes('application/') && data.mimetype.includes('json')) {
    try {
      data.content_json = JSON.parse(bytesToString(data.content));
    } catch {}
  }
}

data.sha = sha256(inputBytes);
data.transaction_hash = txHash;

return data;

And because it's used just as "signaling layer" of changing state that already exists in the system (eg. db/history of ethscriptions ownership changes), these blobs can be skipped of persistrance - eg. not saving them in db like other blobs, cuz it's not really neaded. What will happen is that you'll add these transfers to valid_transfers of the given ethscription in transaction_hash of the transfer object.
cc @RogerPodacter

Cool! I think if we want transfers we should probably have a generic flag that says “treat the blob as if it were the calldata” and then we could use the same format, which is more efficient anyway as it encodes the addresses as bytes instead of hex strings.

Using blobs for accounting purposes is not a good idea due to their temporary nature.

Cool! I think if we want transfers we should probably have a generic flag that says “treat the blob as if it were the calldata” and then we could use the same format, which is more efficient anyway as it encodes the addresses as bytes instead of hex strings.

The "flag" is this cbor.transfers, eg. if the cbor has transfers instead of content, then it's considered transfer operation.
It cannot be just like the regular ESIP-5 bulk transferring, we can support it, but the idea is to be more clear and that with that we support sending to multiple recipients at the same time.  The efficiency isn't a big deal here with blobs, that's why we can be a bit more explicit and do bigger jsons - A; and B - sure the to can be bytes instead, no worries.
As i said in twitter, there are ,and will be more, services and apis and archival nodes that will always save that. It's not like apis or regular centralized services. There whole projects dedicated to just that - saving blobs, us included. CovalentHQ and EthPortalNetwork are examples.

@tunnckoCore By relying on third-party projects, we risk losing data. I think blobs are best used for storing digital art content only.

@CryptoPoltr
It's absolutely the same imho. Whether you depend for the art or for transfering the art.. you still "trust" third parties which isn't an argument and case anyway cuz many will host blob data.
The key is to have as easy as possible ways to run indexers and dbs and make them sync between each other. Then it won't be a case of trust.


List Part Pages are displayed incorrectly in grid layout

1. Describe the bug
If two list part pages are placed in a grid layout on a card page the pages have a minimum unreadable width and cannot be expand.
This behavior comes with version 23. In Version 22 the width was normal.
2. To Reproduce

Create a grid layout in a group of a card page and place two list parts in it:

                    grid(GridForTwoListPars)
                    {
                        part(ListPartPageOne; "List Part Page One")
                        {
                        }
                        part(ListPartPageTwo; "List Part Page Two")
                        {
                        }
                    }

Compile and publish.
Open the webclient and navigate to the page.

3. Expected behavior
The layout in the page should show the list parts side by side, without any empty spaces. In Version 22 this has worked fine.
Here is a Screenshot how it looked like till BC22.5:

4. Actual behavior
Since BC23 the list parts are so narrow that you can't read any field anymore and a wide empty space is right next to them.

5. Versions:

AL Language: 12.1.887908
Visual Studio Code: 1.84.1
Business Central: DE Business Central 23.0 (Platform 23.0.13573.0 + Application 23.0.12034.12676)
List of Visual Studio Code extensions that you have installed: Tested with none except the AL-Language

This is not related to the AL Language Extension.
You should create a support case to get this addressed.
This issue here is nice for other partners as reference, but it won't solve your problem.

Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. The owning team is already aware of this issue, however you can choose to open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


[cfid-4927] Investigate using concourse for running tests and PRs - Story Id: 115060965

Link: https://www.pivotaltracker.com/story/show/115060965
Labels:
Requester: Sree
Estimate: 0.0

Goal is to move away from TRAVIS

Link: https://www.pivotaltracker.com/n/projects/997278/stories/115060965/comments130988569
User: Madhura Bhave

this would require quite a bit of configuration. there would need to be one job per profile. We have added the pullrequest-resource to the concourse deployment which allows tracking multiple branches for a repo. Unstarting because travis is back up and this is not required immediately.
Comment Id: 130988569


Could not download the zip file.

Hello,
Sorry, I am new to this.  I have started with git but I have not yet downloaded any code or application.  The zip file was a good idea, but it did not work for me.  This was step 2 in get the app.  Does anyone have any suggestions other than continuing the git tutorial?
Ed
[Enter feedback here]

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

ID: 38a38919-b557-4723-7ea9-b0fbafbfdc52
Version Independent ID: 2117c374-eda9-906e-392e-c55e1ebf8060
Content: Docker tutorial - Part 1: Build and run the todo list sample app
Content Source: docker/tutorials/your-application.md
Product: visual-studio-windows
Technology: vs-azure
GitHub Login: @nebuk89
Microsoft Alias: ghogen

I've updated the tutorial with some clearer instructions. It should be visible by tomorrow.

Navigate to the repo https://github.com/docker/getting-started, click on the green Code button, choose Download ZIP, then open the downloaded ZIP file, Extract All.


Error starting script on Ubuntu 20.04 LTS

$ az --version
azure-cli                         2.54.0
core                              2.54.0
telemetry                          1.1.0
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location '/opt/az/bin/python3'
Extensions directory '/home/damiano/.azure/cliextensions'
Python (Linux) 3.11.5 (main, Nov  8 2023, 05:21:25) [GCC 9.4.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
$ python3.8 BlobHunter.py
Traceback (most recent call last):
File "BlobHunter.py", line 7, in
from azure.mgmt.resource import SubscriptionClient, ResourceManagementClient
File "/home/damiano/.local/lib/python3.8/site-packages/azure/mgmt/resource/init.py", line 9, in
from .managedapplications import ApplicationClient
File "/home/damiano/.local/lib/python3.8/site-packages/azure/mgmt/resource/managedapplications/init.py", line 9, in
from ._application_client import ApplicationClient
File "/home/damiano/.local/lib/python3.8/site-packages/azure/mgmt/resource/managedapplications/_application_client.py", line 12, in
from msrest import Deserializer, Serializer
File "/home/damiano/.local/lib/python3.8/site-packages/msrest/init.py", line 28, in
from .configuration import Configuration
File "/home/damiano/.local/lib/python3.8/site-packages/msrest/configuration.py", line 38, in
from .universal_http.requests import (
File "/home/damiano/.local/lib/python3.8/site-packages/msrest/universal_http/init.py", line 53, in
from ..exceptions import ClientRequestError, raise_with_traceback
File "/home/damiano/.local/lib/python3.8/site-packages/msrest/exceptions.py", line 31, in
from azure.core.exceptions import SerializationError, DeserializationError
ImportError: cannot import name 'SerializationError' from 'azure.core.exceptions' (/home/damiano/.local/lib/python3.8/site-packages/azure/core/exceptions.py)

Hi @Damianoux,
First of all,
have you installed all the requirements listed in the requirements.txt file?
Additionally, could you please provide information on the versions of the msrest and azure-core libraries installed in your environment?
You can check this using the following command:
pip3 show msrest azure-core

Thanks!


Backup exposure history to transfer to new/reseted phone

Feature description
Create a backup in order to be able to continue using the app without exposure data loss when moving to a new phone. Coming with that restoring the exposure data on a new phone. Preferably, this would be possible moving between iOS and Android.
Problem and motivation
When a user changes their phone all exposure data for the last two weeks is lost. If they can make a backup of the data and restore it on their new phone this data could still be accessible and they could be warned and warn others about the infection.
Is this something you're interested in working on
Yes, from UX POV.

Internal Tracking ID: EXPOSUREAPP-2182

As @corneliusroemer already stated this is not possible in any way and needs to be discussed by the vendors (Google/Apple) of the EN framework.

Thanks for the clarification. I assumed that this is not possible at the current state of the API. I reckon the workaround by @corneliusroemer is an idea though not perfect ;). With this workaround: is it possible to mark oneself as infected on two phones with just one test? Perhaps that would be something to address in the FAQs.

@ma6 The TAN/QR code is only valid for a one time key submission, so no, you cannot push the keys from two phones with one key.😐

https://github.com/corona-warn-app/cwa-app-android/issues/962#issue-671932114

I've exactly this described case. I switched my phone and now all my old contacts are lost. But I noticed that the Google API indeed syncs the contacts, even from old phone. Isn't it possible to pull their information? To my mind, this is a big issue, especially in this time of year and Smartphone season.. (Apple, Google, Samsung, OnePlus all released new phones)

@Xelfmade unless you have root this is unfortunately not possible as long as Google/Apple don't allow it (they store all the keys in their Exposure Notification Framework (ENF)). My recommendation would be this:

Alternatively, one could advise that the old phone could be left at home and only be turned on once a day for two weeks to check for risk encounters. This would be sufficient to receive warnings about risk encounters from days where only the old phone was carried; however, in the unlikely event of receiving a positive test result oneself, one would require an extra TeleTAN to be able to submit diagnosis keys from both phones (I'm not sure whether this is supposed to be possible in such a case).

Yes. All keys are stored in the ENF and will analysed to the same time. There should be a way to accomplish this..
But do you think, everyone will do this, even if they know about it? That's really bad and more over the case of a positive test.

@Xelfmade
I agree that it would be convenient to have an option to export this data to a new phone but unfortunately there is nothing CWA can do about this except forwarding the request to Google/Apple. Whether they will ever allow this? 🤷 As this opens new attack surfaces I wouldn't count on it tbh.

All keys are stored in the ENF and will analysed to the same time. There should be a way to accomplish this..

The stored keys cannot be read (unless you have root) by you or CWA. ENF is fully responsible for handling those and CWA is only getting the final results of the calculation handed over via the API.

But do you think, everyone will do this, even if they know about it? That's really bad and more over the case of a positive test.

You're right: unfortunately not everyone will do this but I hope we'll at least get a FAQ entry which describes the procedure.

Has this been filed as a feature request/bug with Apple/Google?

If there is ever a backup / restore mechanism implemented, it would not only need to include exposure keys, but also any pending test registered through a QR code.

I second this. New phone owners have to carry two phones or lose two weeks of protection.

@DanAmt

New phone owners have to carry two phones or lose two weeks of protection.

https://www.coronawarn.app/en/faq/#new_device advises:

Your old device must be able to perform regular checks for possible encounters. Therefore, leave the device permanently turned on and permanently connected to the Internet.
Keep the old device in a stationary location, e.g., in a specific place in your apartment. If possible, place the device where you can hear or see it so that you are alerted early by a notification of the app.
Actively access the Corona-Warn-App on the old device at least once a day and check your risk status there.

If you carry the old phone with you and exposure logging is activated, then you will pick up new encounters. If possible it is best to just leave the old phone at home where it most likely will not have new encounters, then after two weeks you can disable exposure notifications on the old phone.

Closing this issue as its related internal ticket was set to obsolete.

This is not possible because of ENF restrictions on iOS and Android.


Consolidates and cleans up getTraces thrift query

This deprecates thrift calls for zipkin-web data conversion and
consolidates usage to a getTraces query. We will drop the obsolete
methods in 1.5.0, resulting in a much cleaner thrift api.
Before this change, there was a leaky abstraction between the query and
the web packages. For example, types like TraceCombo were introduced
eventhough they were only a single stage of data conversion and only
used to support one web view. The web component now handles data
conversions directly. Moreover, the web component duplicated work by
doing an id scan which implied looking up spans before looking up spans.
This also cleans up a couple questionable api concerns: adjuster and
binary annotation query.
In practice, there was only one type of adjustment, time-skew, and this
was almost always enabled. The code was confused by an idea that there
would be many types of adjustments, and in some places time-skew was
applied multiple times. This moves it to a boolean flag, just like the
http api.
The binary annotation query in thrift was a weird one. It allows the
user to send a string -> string query only. However, the signature
accepted literally the BinaryAnnotation type, which has other members,
and might not be a string. This clarifies the concern by only accepting
a map of string -> string.

+1 LGTM

belated :+1:

:+1:


lestarch: a few fixes found trying to compile Arduino

A few fixes found while compiling for the Arduino target.

@Joshua-Anderson this is ready.


Kali linux freezes when launched

Hello everyone,
I've just finished installing Kali with crouton. But when i enter sudo startxfce4, i get to the kali first screen but can't move my mouse nor use the keyboard. I assume it's because kali freezes... I have an Asus C300 4gb ram. Does any one knows how to fix it ?
Thanks in advance,
Cheers !

Can you give the output of sudo enter-chroot -n kali croutonversion

Oh i don't understand anything anymore.. I re-installed Kali exactly the same way i did the first time, now i don't even launch kali i have this "Fatal error : no screens found"... Do you know why and how to fix it ? Do you still need the output ?
Thanks !

@PaulBorensztein Probably https://github.com/dnschneid/crouton/issues/1505 However to be sure can you post the output of sudo enter-chroot -n kali croutonversion
If it is indeed the above mentioned issue then you can update your chroot with sudo sh ~/Downloads/crouton -n kali -u -t xiwi Then it will use a chromeos window to run your chroot in, instead of using xorg.
Please close this issue if it is the same as https://github.com/dnschneid/crouton/issues/1505, because it is already tracked there. Thanks.

So after doing
sudo sh ~/Downloads/crouton -n kali -u -t xiwi
I got it working, thanks.
Just before i close the issue, i have a last question. Will it slow the perfomances if I use Kali installed like that instead of the "regular" way ? Is there any possibilities to make it like most of the other people ?
Thanks :+1:

Not much, since you also will not have gpu acceleration with xorg in kalli. For now kali and debian wheezie won't work with xorg, however work is being done to fix it. Keep an eye on #1505 .

Alright, thanks a lot mate for fixing my issue. I'll definitly keep an eye on #1505, I close this issue.
Thanks again ! :)

every time when i start a kali in vmware,it freezes. I am unable to open anything when this occurs.
plz give me any solution regarding this.


Quality index and doc_percent  attribute

Hi there,
First, you are doing a great work, and I'm pleased to use your tool every days.
Did just notice something strange with one of my pods, about doc_percent attribute.
I did notice that documentation and have an influence on quality index, so I decided to document my pods betters. In fact, I didn't support apple docs, only added some comments. So, after all this conversion work, I tried to push an update on one of my pods https://cocoapods.org/pods/NSString+Color, and did notice that I gain some points for the documentation.
The problem is that the points are gone now, and the report tells me that doc_percent is 0
==> http://metrics.cocoapods.org/api/v1/pods/NSString+Color
I just ran appledoc again, and the docset if correctly generated.
So my question, is Am i doing something wrong ? What should I do to make my documentation taken into account ?
Regards

The doc page of the pod (http://cocoadocs.org/docsets/NSString+Color/1.1.3/) seems to be ok and indeed mark it as 100% documented; so the metric should have been updated as well, strange that it hasn't been.
Did you bump your pod version between the one not having any appledoc comments and the one adding them? If your previous undocumented code was already 1.1.3 and you didn't change the pod version it's probably considered the same by the metrics API and this not re-scanned?

Yes. In fact, it was the 1.1.2  release that did update the documentation. The 1.1.3 was to add the new target for library target. May be this new target did false the documentation scan ?
Stranger, the displayed readme on https://cocoapods.org/pods/NSString+Color is not the last available one on https://github.com/nicolasgoutaland/NSString-Color.
By the way, http://cocoadocs.org/docsets/NSString+Color/1.1.3/ is correct.

Hrm, I'm not really sure what went wrong there, I re-ran the docs and you're back up to 100%
http://metrics.cocoapods.org/api/v1/pods/NSString+Color
Thanks for bringing it up, and I'm glad the QIs inspired a better environment for us all, documenting counts :+1:
Will leave open for a week or two to see if any other cases crop up/

Nice !
And the correct ReadMe is back.
Next, I will document my other pods ;)

Closing :+1:


Better prevention of accidental use of a bare . in black- and watchlist

From time to time, people forget that a bare . matches every character, not just the dot itself. The correct syntax is to escape it (\.), which is the intended behaviour 99% of the times.
SmokeDetector could detect cases like

!!/watch example.com

and reply with something like

@Glorfindel Bare dot detected in pattern; you most likely meant to !!/watch example\.com. Use !!/watch-force to override this check.

See https://chat.stackexchange.com/transcript/message/50123380#50123380 + surrounding pages.
It's maybe not necessary for !!/blacklist-keyword and !!/blacklist-username, but it definitely is useful for !!/blacklist-website.

Resolved with 458ca6


NO_NODE error on kafka consumer init.

var kafka = require('kafka-node'),
Consumer = kafka.Consumer,
client = new kafka.Client(),
consumer = new Consumer(
  client,
  [
    { topic: '1234', partition: 0 }
  ]
);
consumer.on('message', function (message) {
  console.log(message);
});

Kafka consumer created using the above code crashes with NO_NODE[-101] error.
Exception: NO_NODE[-101]
    at ConnectionManager.onSocketData (/home/sk/ws/kafka/node_modules/kafka-node/node_modules/node-zookeeper-client/lib/ConnectionManager.js:570:23)
    at Socket.EventEmitter.emit (events.js:95:17)
    at Socket.<anonymous> (_stream_readable.js:746:14)
    at Socket.EventEmitter.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:408:10)
    at emitReadable (_stream_readable.js:404:5)
    at readableAddChunk (_stream_readable.js:165:9)
    at Socket.Readable.push (_stream_readable.js:127:10)
    at TCP.onread (net.js:526:21)

The default zk connectionString is localhost:2181/kafka0.8, so please check your server configuration and change it to yours.

zookeeper.connect=localhost:2181

this is how it comes shipped with kafka. I see, an inherent mismatch between zookeeper & kafka defaults. but anyway, config change is not an issue. when does zookeeper make the node kafka0.8? does it happen, when kafka broker connects to it for the first time? now my zookeeper root node has child nodes like brokers, consumers etc.. does all of them get grouped under kafka0.8 node?

The client can't do this, you should change configure in your Kafka
server.properties and create path kafka0.8 in zk manually.  The easiest way
is set connectionString to localhost:2181.
madhavan020985<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>于2015年2月3日星期二写道：

zookeeper.connect=localhost:2181
this is how it comes shipped with kafka. I see, an inherent mismatch
between zookeeper & kafka defaults. but anyway, config change is not an
issue. when does zookeeper make the node kafka0.8? does it happen, when
kafka broker connects to it for the first time? now my zookeeper root node
has child nodes like brokers, consumers etc.. does all of them get grouped
under kafka0.8 node?
—
Reply to this email directly or view it on GitHub
https://github.com/SOHU-Co/kafka-node/issues/148#issuecomment-72593325.


Why form is not 'dirty' after adding/removing object in array?

I need to save added objects in array & be able to save state, if objects were deleted from array.
In other words, i try to accomplish this behavior:

I have initialised array with 1 object inside
After adding, removing any objects in this array, i expect to have dirty form, but it is not.

Please check gist with this example:
https://gist.github.com/olegkalyta/f6623b5c645c22581650

Shallow equality cannot detect when you change an element inside an array. You need to return a new array without the element you want to remove rather than mutating the existing array.

You mean, explicitly mutate state in my own handle array methods and do not use
formReducer.plugin 'redux-form/ADD_ARRAY_VALUE' ?

In my gist, i use standard methods for adding/removing array elements and i thought, they should return new arrays to change form status to dirty.
Anyway, as @clayne11 adviced, i manually return new arrays in plugin, but it still does not work for me.
https://gist.github.com/olegkalyta/d3a1f8e120576add7e55
@erikras is there some sort of best practise for such task?

This is unfortunately a known bug (#391, #484) that is being taken into consideration for the next version, but for now, I'm afraid you're going to have to do array length checks yourself.

+1 for this being implemented. WRT to form dirtiness, if I touch a field, the form is dirty, so why not apply the same at the form level? If I touch the form by adding or removing fields, the form itself should be dirty.

Please continue the discussion in #391.


.content-wrapper click event not fire on mobile browser?

I find sidebar can't hide when click content-wrapper area in mobile browser(it works in desktop browser), and I find this issue is related to the code below which in the Adminlte initial file. anyone can tell something?
$(".content-wrapper").click(function () {
    //Enable hide menu when clicking on the content-wrapper on small screens
    if ($(window).width() <= (screenSizes.sm - 1) && $("body").hasClass("sidebar-open")) {
        $("body").removeClass('sidebar-open');
    }
});

Please specify the device and the browser. I tested on iPhone 6s Safari and it works.
Thanks!


fixed: kinematic-body physics lagged a frame behind, allowing you to walk through some bodies

Current position and velocity was synced to the physics object AFTER physics sim had been ran, allowing you to walk through some surfaces (particularly spheres and cylinders).
This requires the other PR donmccurdy/aframe-physics-system#60
This now uses the new update mechanism to ensure physics bodies are synced before physics interactions are handled.

Thanks! (Left comments on https://github.com/donmccurdy/aframe-physics-system/pull/60)

Pushed some extra commits on this, merged via #190. Thanks!


Issue while trying to package seaweedfs

Hello,
I get the following error while trying to package seaweedfs (https://github.com/chrislusf/seaweedfs/tree/2.00).
I am using the vgo2nix from the unstable nixos channel (https://nixos.org/channels/nixos-unstable).
╰─[:)] % vgo2nix -dir seaweedfs                                                                                nix-prefetch-git vgo2nix
goPackagePath cloud.google.com/go has rev v0.44.3
goPackagePath cloud.google.com/go/datastore has rev v1.0.0
goPackagePath contrib.go.opencensus.io/exporter/aws has rev 2befc13012d0
goPackagePath contrib.go.opencensus.io/exporter/ocagent has rev v0.5.0
goPackagePath contrib.go.opencensus.io/exporter/stackdriver has rev v0.12.1
goPackagePath contrib.go.opencensus.io/integrations/ocsql has rev v0.1.4
goPackagePath contrib.go.opencensus.io/resource has rev v0.1.1
goPackagePath github.com/Azure/azure-amqp-common-go/v2 has rev v2.1.0
goPackagePath github.com/Azure/azure-pipeline-go has rev v0.2.2
goPackagePath github.com/Azure/azure-sdk-for-go has rev v30.1.0
goPackagePath github.com/Azure/azure-service-bus-go has rev v0.9.1
goPackagePath github.com/Azure/azure-storage-blob-go has rev v0.8.0
goPackagePath github.com/Azure/go-autorest has rev v12.0.0
goPackagePath github.com/BurntSushi/toml has rev v0.3.1
goPackagePath github.com/BurntSushi/xgb has rev 27f122750802
goPackagePath github.com/DataDog/zstd has rev<PHONE_NUMBER>98
goPackagePath github.com/GoogleCloudPlatform/cloudsql-proxy has rev c4ba1fdf4d36
goPackagePath github.com/OneOfOne/xxhash has rev v1.2.2
goPackagePath github.com/Shopify/sarama has rev v1.23.1
goPackagePath github.com/Shopify/toxiproxy has rev v2.1.4
goPackagePath github.com/alecthomas/template has rev a0175ee3bccc
goPackagePath github.com/alecthomas/units has rev 2efee857e7cf
goPackagePath github.com/armon/consul-api has rev eb2c6b5be1b6
goPackagePath github.com/aws/aws-sdk-go has rev v1.33.5
goPackagePath github.com/beorn7/perks has rev v1.0.1
goPackagePath github.com/bgentry/speakeasy has rev v0.1.0
goPackagePath github.com/bitly/go-hostpool has rev a3a6125de932
goPackagePath github.com/bmizerany/assert has rev b7ed37b82869
goPackagePath github.com/buraksezer/consistent has rev 693edf70fd72
goPackagePath github.com/census-instrumentation/opencensus-proto has rev v0.2.1
goPackagePath github.com/cespare/xxhash has rev v1.1.0
goPackagePath github.com/chrislusf/raft has rev v1.0.1
goPackagePath github.com/client9/misspell has rev v0.3.4
goPackagePath github.com/cncf/udpa/go has rev 269d4d468f6f
goPackagePath github.com/cockroachdb/datadriven has rev 80d97fb3cbaa
goPackagePath github.com/coreos/bbolt has rev v1.3.2
goPackagePath github.com/coreos/etcd has rev v3.3.10
goPackagePath github.com/coreos/go-semver has rev v0.3.0
goPackagePath github.com/coreos/go-systemd has rev 95778dfbb74e
goPackagePath github.com/coreos/go-systemd/v22 has rev v22.0.0
goPackagePath github.com/coreos/pkg has rev 399ea9e2e55f
goPackagePath github.com/creack/pty has rev v1.1.7
goPackagePath github.com/davecgh/go-spew has rev v1.1.1
goPackagePath github.com/devigned/tab has rev v0.1.1
goPackagePath github.com/dgrijalva/jwt-go has rev v3.2.0
goPackagePath github.com/dgryski/go-sip13 has rev e10d5fee7954
goPackagePath github.com/dimchansky/utfbom has rev v1.1.0
goPackagePath github.com/disintegration/imaging has rev v1.6.2
goPackagePath github.com/dustin/go-humanize has rev v1.0.0
goPackagePath github.com/eapache/go-resiliency has rev v1.2.0
goPackagePath github.com/eapache/go-xerial-snappy has rev 776d5712da21
goPackagePath github.com/eapache/queue has rev v1.1.0
goPackagePath github.com/envoyproxy/go-control-plane has rev v0.9.4
goPackagePath github.com/envoyproxy/protoc-gen-validate has rev v0.1.0
goPackagePath github.com/facebookgo/clock has rev 600d898af40a
goPackagePath github.com/facebookgo/ensure has rev 63f1cf65ac4c
goPackagePath github.com/facebookgo/stack has rev<PHONE_NUMBER>52
goPackagePath github.com/facebookgo/stats has rev 1b76add642e4
goPackagePath github.com/facebookgo/subset has rev c811ad88dec4
goPackagePath github.com/fatih/color has rev v1.7.0
goPackagePath github.com/fortytw2/leaktest has rev v1.3.0
goPackagePath github.com/frankban/quicktest has rev v1.7.2
goPackagePath github.com/fsnotify/fsnotify has rev v1.4.7
goPackagePath github.com/ghodss/yaml has rev v1.0.0
goPackagePath github.com/go-ini/ini has rev v1.25.4
goPackagePath github.com/go-kit/kit has rev v0.8.0
goPackagePath github.com/go-logfmt/logfmt has rev v0.4.0
goPackagePath github.com/go-redis/redis has rev v6.15.7
goPackagePath github.com/go-sql-driver/mysql has rev v1.5.0
goPackagePath github.com/go-stack/stack has rev v1.8.0
goPackagePath github.com/gobuffalo/attrs has rev a9411de4debd
goPackagePath github.com/gobuffalo/depgen has rev v0.1.0
goPackagePath github.com/gobuffalo/envy has rev v1.7.0
goPackagePath github.com/gobuffalo/flect has rev v0.1.3
goPackagePath github.com/gobuffalo/genny has rev v0.1.1
goPackagePath github.com/gobuffalo/gitgen has rev cc086187d211
goPackagePath github.com/gobuffalo/gogen has rev v0.1.1
goPackagePath github.com/gobuffalo/logger has rev 86e12af44bc2
goPackagePath github.com/gobuffalo/mapi has rev v1.0.2
goPackagePath github.com/gobuffalo/packd has rev v0.1.0
goPackagePath github.com/gobuffalo/packr/v2 has rev v2.2.0
goPackagePath github.com/gobuffalo/syncx has rev 33c29581e754
goPackagePath github.com/gocql/gocql has rev e163eff7a8c6
goPackagePath github.com/godbus/dbus/v5 has rev v5.0.3
goPackagePath github.com/gogo/protobuf has rev 28a6bbf47e48
goPackagePath github.com/golang/glog has rev 23def4e6c14b
goPackagePath github.com/golang/groupcache has rev 869f871628b6
goPackagePath github.com/golang/mock has rev v1.3.1
goPackagePath github.com/golang/protobuf has rev v1.4.2
goPackagePath github.com/golang/snappy has rev v0.0.1
goPackagePath github.com/google/btree has rev v1.0.0
goPackagePath github.com/google/go-cmp has rev v0.5.0
goPackagePath github.com/google/go-replayers/grpcreplay has rev v0.1.0
goPackagePath github.com/google/go-replayers/httpreplay has rev v0.1.0
goPackagePath github.com/google/gofuzz has rev v1.0.0
goPackagePath github.com/google/martian has rev 25dcb96d9e51+incompatible
goPackagePath github.com/google/pprof has rev 54271f7e092f
goPackagePath github.com/google/renameio has rev v0.1.0
goPackagePath github.com/google/subcommands has rev v1.0.1
goPackagePath github.com/google/uuid has rev v1.1.1
goPackagePath github.com/google/wire has rev v0.3.0
goPackagePath github.com/googleapis/gax-go has rev v2.0.2
goPackagePath github.com/googleapis/gax-go/v2 has rev v2.0.5
goPackagePath github.com/gorilla/mux has rev v1.7.4
goPackagePath github.com/gorilla/websocket has rev v1.4.1
goPackagePath github.com/grpc-ecosystem/go-grpc-middleware has rev f849b5445de4
goPackagePath github.com/grpc-ecosystem/go-grpc-prometheus has rev v1.2.0
goPackagePath github.com/grpc-ecosystem/grpc-gateway has rev v1.11.0
goPackagePath github.com/hailocab/go-hostpool has rev e80d13ce29ed
goPackagePath github.com/hashicorp/go-uuid has rev v1.0.1
goPackagePath github.com/hashicorp/golang-lru has rev v0.5.3
goPackagePath github.com/hashicorp/hcl has rev v1.0.0
goPackagePath github.com/hpcloud/tail has rev v1.0.0
goPackagePath github.com/inconshreveable/mousetrap has rev v1.0.0
goPackagePath github.com/jcmturner/gofork has rev v1.0.0
goPackagePath github.com/jmespath/go-jmespath has rev v0.3.0
goPackagePath github.com/joho/godotenv has rev v1.3.0
goPackagePath github.com/jonboulle/clockwork has rev v0.1.0
goPackagePath github.com/json-iterator/go has rev v1.1.10
goPackagePath github.com/jstemmer/go-junit-report has rev af01ea7f8024
goPackagePath github.com/julienschmidt/httprouter has rev v1.2.0
goPackagePath github.com/karlseguin/ccache has rev v2.0.3
goPackagePath github.com/karlseguin/expect has rev v1.0.1
goPackagePath github.com/karrick/godirwalk has rev v1.10.3
goPackagePath github.com/kisielk/errcheck has rev v1.2.0
goPackagePath github.com/kisielk/gotool has rev v1.0.0
goPackagePath github.com/klauspost/compress has rev v1.10.9
goPackagePath github.com/klauspost/cpuid has rev v1.2.1
goPackagePath github.com/klauspost/crc32 has rev v1.2.0
goPackagePath github.com/klauspost/reedsolomon has rev v1.9.2
goPackagePath github.com/konsorten/go-windows-terminal-sequences has rev v1.0.2
goPackagePath github.com/kr/logfmt has rev b84e30acd515
goPackagePath github.com/kr/pretty has rev v0.1.0
goPackagePath github.com/kr/pty has rev v1.1.1
goPackagePath github.com/kr/text has rev v0.1.0
goPackagePath github.com/kurin/blazer has rev v0.5.3
goPackagePath github.com/lib/pq has rev v1.2.0
goPackagePath github.com/magiconair/properties has rev v1.8.1
goPackagePath github.com/mailru/easyjson has rev v0.7.1
goPackagePath github.com/markbates/oncer has rev bf2de49a0be2
goPackagePath github.com/markbates/safe has rev v1.0.1
goPackagePath github.com/mattn/go-colorable has rev v0.1.2
goPackagePath github.com/mattn/go-ieproxy has rev f9202b1cfdeb
goPackagePath github.com/mattn/go-isatty has rev v0.0.8
goPackagePath github.com/mattn/go-runewidth has rev v0.0.4
goPackagePath github.com/matttproud/golang_protobuf_extensions has rev v1.0.1
goPackagePath github.com/mitchellh/go-homedir has rev v1.1.0
goPackagePath github.com/mitchellh/mapstructure has rev v1.1.2
goPackagePath github.com/modern-go/concurrent has rev bacd9c7ef1dd
goPackagePath github.com/modern-go/reflect2 has rev v1.0.1
goPackagePath github.com/montanaflynn/stats has rev 1bf9dbcd8cbe
goPackagePath github.com/mwitkow/go-conntrack has rev cc309e4a2223
goPackagePath github.com/nats-io/jwt has rev v0.2.14
goPackagePath github.com/nats-io/nats-server/v2 has rev v2.0.4
goPackagePath github.com/nats-io/nats.go has rev v1.8.1
goPackagePath github.com/nats-io/nkeys has rev v0.1.0
goPackagePath github.com/nats-io/nuid has rev v1.0.1
goPackagePath github.com/oklog/ulid has rev v1.3.1
goPackagePath github.com/olekukonko/tablewriter has rev a0225b3f23b5
goPackagePath github.com/olivere/elastic/v7 has rev v7.0.19
goPackagePath github.com/onsi/ginkgo has rev v1.10.1
goPackagePath github.com/onsi/gomega has rev v1.7.0
goPackagePath github.com/opentracing/opentracing-go has rev v1.2.0
goPackagePath github.com/pelletier/go-toml has rev v1.4.0
goPackagePath github.com/peterh/liner has rev v1.1.0
goPackagePath github.com/pierrec/lz4 has rev v2.2.7
goPackagePath github.com/pkg/errors has rev v0.9.1
goPackagePath github.com/pkg/profile has rev v1.2.1
goPackagePath github.com/pmezard/go-difflib has rev v1.0.0
goPackagePath github.com/prometheus/client_golang has rev v1.1.0
goPackagePath github.com/prometheus/client_model has rev 14fe0d1b01d4
goPackagePath github.com/prometheus/common has rev v0.6.0
goPackagePath github.com/prometheus/procfs has rev v0.0.4
goPackagePath github.com/prometheus/tsdb has rev v0.7.1
goPackagePath github.com/rakyll/statik has rev v0.1.7
goPackagePath github.com/rcrowley/go-metrics has rev cac0b30c2563
goPackagePath github.com/rogpeppe/fastuuid has rev 6724a57986af
goPackagePath github.com/rogpeppe/go-internal has rev v1.3.0
goPackagePath github.com/seaweedfs/fuse has rev 310228904eff
goPackagePath github.com/seaweedfs/goexif has rev v1.0.2
goPackagePath github.com/sirupsen/logrus has rev v1.4.2
goPackagePath github.com/smartystreets/assertions has rev v1.1.1
goPackagePath github.com/smartystreets/go-aws-auth has rev 0c1422d1fdb9
goPackagePath github.com/smartystreets/gunit has rev v1.3.4
goPackagePath github.com/soheilhy/cmux has rev v0.1.4
goPackagePath github.com/spaolacci/murmur3 has rev v1.1.0
goPackagePath github.com/spf13/afero has rev v1.2.2
goPackagePath github.com/spf13/cast has rev v1.3.0
goPackagePath github.com/spf13/cobra has rev v0.0.3
goPackagePath github.com/spf13/jwalterweatherman has rev v1.1.0
goPackagePath github.com/spf13/pflag has rev v1.0.3
goPackagePath github.com/spf13/viper has rev v1.4.0
goPackagePath github.com/streadway/amqp has rev edfb9018d271
goPackagePath github.com/stretchr/objx has rev v0.2.0
goPackagePath github.com/stretchr/testify has rev v1.5.1
goPackagePath github.com/syndtr/goleveldb has rev v1.0.0
goPackagePath github.com/tidwall/gjson has rev v1.3.2
goPackagePath github.com/tidwall/match has rev v1.0.1
goPackagePath github.com/tidwall/pretty has rev v1.0.0
goPackagePath github.com/tmc/grpc-websocket-proxy has rev 0ad062ec5ee5
goPackagePath github.com/ugorji/go has rev v1.1.4
goPackagePath github.com/urfave/cli has rev v1.20.0
goPackagePath github.com/willf/bitset has rev v1.1.10
goPackagePath github.com/willf/bloom has rev v2.0.3
goPackagePath github.com/wsxiaoys/terminal has rev 0940f3fc43a0
goPackagePath github.com/xdg/scram has rev 7eeb5667e42c
goPackagePath github.com/xdg/stringprep has rev v1.0.0
goPackagePath github.com/xiang90/probing has rev 43a291ad63a2
goPackagePath github.com/xordataexchange/crypt has rev b2862e3d0a77
goPackagePath go.etcd.io/bbolt has rev v1.3.4
goPackagePath go.etcd.io/etcd has rev v3.3.15
goPackagePath go.mongodb.org/mongo-driver has rev v1.3.2
goPackagePath go.opencensus.io has rev v0.22.4
goPackagePath go.uber.org/atomic has rev v1.6.0
goPackagePath go.uber.org/multierr has rev v1.5.0
goPackagePath go.uber.org/tools has rev 2cfd321de3ee
goPackagePath go.uber.org/zap has rev v1.14.1
goPackagePath gocloud.dev has rev v0.16.0
goPackagePath gocloud.dev/pubsub/natspubsub has rev v0.16.0
goPackagePath gocloud.dev/pubsub/rabbitpubsub has rev v0.16.0
goPackagePath golang.org/x/crypto has rev 34f69633bfdc
goPackagePath golang.org/x/exp has rev efd6b22b2522
goPackagePath golang.org/x/image has rev 58c23975cae1
goPackagePath golang.org/x/lint has rev 16217165b5de
goPackagePath golang.org/x/mobile has rev d3739f865fa6
goPackagePath golang.org/x/mod has rev 4bf6d317e70e
goPackagePath golang.org/x/net has rev 16171245cfb2
goPackagePath golang.org/x/oauth2 has rev 0f29369cfe45
goPackagePath golang.org/x/sync has rev 112230192c58
goPackagePath golang.org/x/sys has rev d101bd2416d5
goPackagePath golang.org/x/text has rev v0.3.2
goPackagePath golang.org/x/time has rev 9d24e82272b4
goPackagePath golang.org/x/tools has rev b9c20aec41a5
goPackagePath golang.org/x/xerrors has rev 9bdfabe68543
goPackagePath google.golang.org/api has rev v0.9.0
goPackagePath google.golang.org/appengine has rev v1.6.2
goPackagePath google.golang.org/genproto has rev cb27e3aa2013
goPackagePath google.golang.org/grpc has rev v1.29.1
goPackagePath google.golang.org/protobuf has rev v1.24.0
goPackagePath gopkg.in/alecthomas/kingpin.v2 has rev v2.2.6
goPackagePath gopkg.in/check.v1 has rev 41f04d3bba15
goPackagePath gopkg.in/cheggaaa/pb.v1 has rev v1.0.25
goPackagePath gopkg.in/errgo.v2 has rev v2.1.0
goPackagePath gopkg.in/fsnotify.v1 has rev v1.4.7
goPackagePath gopkg.in/inf.v0 has rev v0.9.1
goPackagePath gopkg.in/jcmturner/aescts.v1 has rev v1.0.1
goPackagePath gopkg.in/jcmturner/dnsutils.v1 has rev v1.0.1
goPackagePath gopkg.in/jcmturner/goidentity.v3 has rev v3.0.0
goPackagePath gopkg.in/jcmturner/gokrb5.v7 has rev v7.3.0
goPackagePath gopkg.in/jcmturner/rpc.v1 has rev v1.1.0
goPackagePath gopkg.in/karlseguin/expect.v1 has rev v1.0.1
goPackagePath gopkg.in/resty.v1 has rev v1.12.0
goPackagePath gopkg.in/tomb.v1 has rev dd632973f1e7
goPackagePath gopkg.in/yaml.v2 has rev v2.2.2
goPackagePath honnef.co/go/tools has rev v0.0.1-2019.2.3
goPackagePath pack.ag/amqp has rev v0.11.2
goPackagePath rsc.io/binaryregexp has rev v0.2.0
goPackagePath sigs.k8s.io/yaml has rev v1.1.0
Fetching github.com/Azure/azure-pipeline-go
Fetching github.com/Azure/azure-amqp-common-go
Fetching github.com/Azure/azure-sdk-for-go
Fetching github.com/Azure/azure-service-bus-go
Fetching github.com/BurntSushi/toml
Fetching github.com/Azure/go-autorest
Fetching github.com/BurntSushi/xgb
Fetching github.com/DataDog/zstd
Fetching github.com/GoogleCloudPlatform/cloudsql-proxy
Fetching github.com/OneOfOne/xxhash
Fetching github.com/Shopify/sarama
Fetching github.com/Azure/azure-storage-blob-go
Fetching github.com/Shopify/toxiproxy
Fetching contrib.go.opencensus.io/integrations/ocsql
Fetching contrib.go.opencensus.io/exporter/stackdriver
Fetching contrib.go.opencensus.io/exporter/ocagent
Fetching contrib.go.opencensus.io/resource
Fetching contrib.go.opencensus.io/exporter/aws
Fetching cloud.google.com/go
Fetching cloud.google.com/go
Finished fetching github.com/OneOfOne/xxhash
Finished fetching github.com/Azure/azure-pipeline-go
Fetching github.com/alecthomas/units
Fetching github.com/alecthomas/template
Finished fetching github.com/Azure/azure-amqp-common-go
Fetching github.com/armon/consul-api
Finished fetching contrib.go.opencensus.io/integrations/ocsql
Fetching github.com/aws/aws-sdk-go
Finished fetching github.com/BurntSushi/toml
Fetching github.com/beorn7/perks
Finished fetching github.com/Azure/azure-service-bus-go
Fetching github.com/bgentry/speakeasy
Finished fetching contrib.go.opencensus.io/resource
Fetching github.com/bitly/go-hostpool
Finished fetching contrib.go.opencensus.io/exporter/stackdriver
Fetching github.com/bmizerany/assert
Finished fetching contrib.go.opencensus.io/exporter/aws
Fetching github.com/buraksezer/consistent
Finished fetching github.com/Azure/azure-storage-blob-go
Fetching github.com/census-instrumentation/opencensus-proto
Finished fetching github.com/Shopify/toxiproxy
Fetching github.com/cespare/xxhash
Finished fetching contrib.go.opencensus.io/exporter/ocagent
Fetching github.com/chrislusf/raft
Finished fetching github.com/Shopify/sarama
Fetching github.com/client9/misspell
Finished fetching github.com/GoogleCloudPlatform/cloudsql-proxy
Fetching github.com/cncf/udpa
Finished fetching github.com/DataDog/zstd
Fetching github.com/cockroachdb/datadriven
Finished fetching github.com/BurntSushi/xgb
Fetching github.com/coreos/bbolt
Finished fetching github.com/Azure/go-autorest
Fetching github.com/coreos/etcd
Finished fetching github.com/alecthomas/units
Fetching github.com/coreos/go-semver
Finished fetching github.com/armon/consul-api
Fetching github.com/coreos/go-systemd
Finished fetching github.com/beorn7/perks
Fetching github.com/coreos/go-systemd
Finished fetching github.com/alecthomas/template
Fetching github.com/coreos/pkg
Finished fetching github.com/bgentry/speakeasy
Fetching github.com/creack/pty
Finished fetching github.com/bitly/go-hostpool
Fetching github.com/davecgh/go-spew
Finished fetching github.com/bmizerany/assert
Fetching github.com/devigned/tab
Finished fetching github.com/cespare/xxhash
Fetching github.com/dgrijalva/jwt-go
Finished fetching github.com/buraksezer/consistent
Fetching github.com/dgryski/go-sip13
Finished fetching github.com/chrislusf/raft
Fetching github.com/dimchansky/utfbom
Finished fetching github.com/cncf/udpa
Fetching github.com/disintegration/imaging
Finished fetching github.com/client9/misspell
Fetching github.com/dustin/go-humanize
Finished fetching github.com/census-instrumentation/opencensus-proto
Fetching github.com/eapache/go-resiliency
Finished fetching github.com/coreos/bbolt
Fetching github.com/eapache/go-xerial-snappy
Finished fetching github.com/coreos/go-semver
Fetching github.com/eapache/queue
Finished fetching github.com/creack/pty
Fetching github.com/envoyproxy/go-control-plane
Finished fetching github.com/devigned/tab
Fetching github.com/envoyproxy/protoc-gen-validate
Finished fetching github.com/coreos/go-systemd
Fetching github.com/facebookgo/clock
Finished fetching github.com/davecgh/go-spew
Fetching github.com/facebookgo/ensure
Finished fetching github.com/coreos/pkg
Fetching github.com/facebookgo/stack
Finished fetching github.com/cockroachdb/datadriven
Fetching github.com/facebookgo/stats
Finished fetching github.com/dgryski/go-sip13
Fetching github.com/facebookgo/subset
Finished fetching github.com/dgrijalva/jwt-go
Fetching github.com/fatih/color
Finished fetching github.com/dimchansky/utfbom
Fetching github.com/fortytw2/leaktest
Finished fetching github.com/coreos/go-systemd
Fetching github.com/frankban/quicktest
Finished fetching github.com/eapache/go-resiliency
Fetching github.com/fsnotify/fsnotify
Finished fetching github.com/dustin/go-humanize
Fetching github.com/ghodss/yaml
Finished fetching github.com/eapache/go-xerial-snappy
Fetching github.com/go-ini/ini
Finished fetching cloud.google.com/go
Fetching github.com/go-kit/kit
Finished fetching github.com/eapache/queue
Fetching github.com/go-logfmt/logfmt
Finished fetching github.com/disintegration/imaging
Fetching github.com/go-redis/redis
Finished fetching github.com/coreos/etcd
Fetching github.com/go-sql-driver/mysql
Finished fetching github.com/facebookgo/clock
Fetching github.com/go-stack/stack
Finished fetching github.com/facebookgo/ensure
Fetching github.com/gobuffalo/attrs
Finished fetching github.com/fortytw2/leaktest
Fetching github.com/gobuffalo/depgen
Finished fetching github.com/facebookgo/stack
Fetching github.com/gobuffalo/envy
Finished fetching github.com/facebookgo/subset
Fetching github.com/gobuffalo/flect
Finished fetching github.com/facebookgo/stats
Fetching github.com/gobuffalo/genny
Finished fetching cloud.google.com/go
Fetching github.com/gobuffalo/gitgen
panic: Error processing import path "cloud.google.com/go/datastore": nix-prefetch-git --fetch-submodules --url https://github.com/googleapis/google-cloud-go --rev v1.0.0 failed:
Initialized empty Git repository in /run/user/1000/git-checkout-tmp-oHUTS2Ub/google-cloud-go/.git/
fatal: couldn't find remote ref refs/tags/v1.0.0
From https://github.com/googleapis/google-cloud-go
 * [new branch]      debrandStackdriver  -> origin/debrandStackdriver
 * [new branch]      gh-pages            -> origin/gh-pages
 * [new branch]      master              -> origin/master
 * [new branch]      pubsub-detach-subscription -> origin/pubsub-detach-subscription
 * [new branch]      pubsub-ordered-keys -> origin/pubsub-ordered-keys
 * [new branch]      regen_gocloud       -> origin/regen_gocloud
 * [new branch]      release-v0.67.0     -> origin/release-v0.67.0
 * [new branch]      unskip-ordered-key-tests -> origin/unskip-ordered-key-tests
 * [new tag]         bigquery/v1.0.0     -> bigquery/v1.0.0
 * [new tag]         bigquery/v1.0.1     -> bigquery/v1.0.1
 * [new tag]         bigquery/v1.1.0     -> bigquery/v1.1.0
 * [new tag]         bigquery/v1.10.0    -> bigquery/v1.10.0
 * [new tag]         bigquery/v1.11.0    -> bigquery/v1.11.0
 * [new tag]         bigquery/v1.2.0     -> bigquery/v1.2.0
 * [new tag]         bigquery/v1.3.0     -> bigquery/v1.3.0
 * [new tag]         bigquery/v1.4.0     -> bigquery/v1.4.0
 * [new tag]         bigquery/v1.5.0     -> bigquery/v1.5.0
 * [new tag]         bigquery/v1.6.0     -> bigquery/v1.6.0
 * [new tag]         bigquery/v1.7.0     -> bigquery/v1.7.0
 * [new tag]         bigquery/v1.8.0     -> bigquery/v1.8.0
 * [new tag]         bigquery/v1.9.0     -> bigquery/v1.9.0
 * [new tag]         bigtable/v1.0.0     -> bigtable/v1.0.0
 * [new tag]         bigtable/v1.1.0     -> bigtable/v1.1.0
 * [new tag]         bigtable/v1.2.0     -> bigtable/v1.2.0
 * [new tag]         bigtable/v1.3.0     -> bigtable/v1.3.0
 * [new tag]         bigtable/v1.4.0     -> bigtable/v1.4.0
 * [new tag]         bigtable/v1.5.0     -> bigtable/v1.5.0
 * [new tag]         bigtable/v1.6.0     -> bigtable/v1.6.0
 * [new tag]         datastore/v1.0.0    -> datastore/v1.0.0
 * [new tag]         datastore/v1.1.0    -> datastore/v1.1.0
 * [new tag]         datastore/v1.2.0    -> datastore/v1.2.0
 * [new tag]         datastore/v1.3.0    -> datastore/v1.3.0
 * [new tag]         firestore/1.1.1     -> firestore/1.1.1
 * [new tag]         firestore/v1.0.0    -> firestore/v1.0.0
 * [new tag]         firestore/v1.1.0    -> firestore/v1.1.0
 * [new tag]         firestore/v1.1.1    -> firestore/v1.1.1
 * [new tag]         firestore/v1.2.0    -> firestore/v1.2.0
 * [new tag]         firestore/v1.3.0    -> firestore/v1.3.0
 * [new tag]         logging/v1.0.0      -> logging/v1.0.0
 * [new tag]         logging/v1.1.0      -> logging/v1.1.0
 * [new tag]         pubsub/v1.0.0       -> pubsub/v1.0.0
 * [new tag]         pubsub/v1.0.1       -> pubsub/v1.0.1
 * [new tag]         pubsub/v1.0.1-beta.ordered.keys -> pubsub/v1.0.1-beta.ordered.keys
 * [new tag]         pubsub/v1.1.0       -> pubsub/v1.1.0
 * [new tag]         pubsub/v1.1.0-beta.ordered.keys -> pubsub/v1.1.0-beta.ordered.keys
 * [new tag]         pubsub/v1.2.0       -> pubsub/v1.2.0
 * [new tag]         pubsub/v1.3.0       -> pubsub/v1.3.0
 * [new tag]         pubsub/v1.3.1       -> pubsub/v1.3.1
 * [new tag]         pubsub/v1.4.0       -> pubsub/v1.4.0
 * [new tag]         pubsub/v1.5.0       -> pubsub/v1.5.0
 * [new tag]         pubsub/v1.6.0       -> pubsub/v1.6.0
 * [new tag]         pubsub/v1.6.1       -> pubsub/v1.6.1
 * [new tag]         pubsub/v1.6.2       -> pubsub/v1.6.2
 * [new tag]         spanner/v1.0.0      -> spanner/v1.0.0
 * [new tag]         spanner/v1.1.0      -> spanner/v1.1.0
 * [new tag]         spanner/v1.10.0     -> spanner/v1.10.0
 * [new tag]         spanner/v1.2.0      -> spanner/v1.2.0
 * [new tag]         spanner/v1.2.1      -> spanner/v1.2.1
 * [new tag]         spanner/v1.3.0      -> spanner/v1.3.0
 * [new tag]         spanner/v1.4.0      -> spanner/v1.4.0
 * [new tag]         spanner/v1.5.0      -> spanner/v1.5.0
 * [new tag]         spanner/v1.5.1      -> spanner/v1.5.1
 * [new tag]         spanner/v1.6.0      -> spanner/v1.6.0
 * [new tag]         spanner/v1.7.0      -> spanner/v1.7.0
 * [new tag]         spanner/v1.8.0      -> spanner/v1.8.0
 * [new tag]         spanner/v1.9.0      -> spanner/v1.9.0
 * [new tag]         storage/v1.0.0      -> storage/v1.0.0
 * [new tag]         storage/v1.1.0      -> storage/v1.1.0
 * [new tag]         storage/v1.1.1      -> storage/v1.1.1
 * [new tag]         storage/v1.1.2      -> storage/v1.1.2
 * [new tag]         storage/v1.10.0     -> storage/v1.10.0
 * [new tag]         storage/v1.11.0     -> storage/v1.11.0
 * [new tag]         storage/v1.2.0      -> storage/v1.2.0
 * [new tag]         storage/v1.2.1      -> storage/v1.2.1
 * [new tag]         storage/v1.3.0      -> storage/v1.3.0
 * [new tag]         storage/v1.4.0      -> storage/v1.4.0
 * [new tag]         storage/v1.5.0      -> storage/v1.5.0
 * [new tag]         storage/v1.6.0      -> storage/v1.6.0
 * [new tag]         storage/v1.7.0      -> storage/v1.7.0
 * [new tag]         storage/v1.8.0      -> storage/v1.8.0
 * [new tag]         storage/v1.9.0      -> storage/v1.9.0
 * [new tag]         v0.1.0              -> v0.1.0
 * [new tag]         v0.10.0             -> v0.10.0
 * [new tag]         v0.11.0             -> v0.11.0
 * [new tag]         v0.12.0             -> v0.12.0
 * [new tag]         v0.13.0             -> v0.13.0
 * [new tag]         v0.14.0             -> v0.14.0
 * [new tag]         v0.15.0             -> v0.15.0
 * [new tag]         v0.16.0             -> v0.16.0
 * [new tag]         v0.17.0             -> v0.17.0
 * [new tag]         v0.18.0             -> v0.18.0
 * [new tag]         v0.19.0             -> v0.19.0
 * [new tag]         v0.2.0              -> v0.2.0
 * [new tag]         v0.20.0             -> v0.20.0
 * [new tag]         v0.21.0             -> v0.21.0
 * [new tag]         v0.22.0             -> v0.22.0
 * [new tag]         v0.23.0             -> v0.23.0
 * [new tag]         v0.24.0             -> v0.24.0
 * [new tag]         v0.25.0             -> v0.25.0
 * [new tag]         v0.26.0             -> v0.26.0
 * [new tag]         v0.27.0             -> v0.27.0
 * [new tag]         v0.28.0             -> v0.28.0
 * [new tag]         v0.29.0             -> v0.29.0
 * [new tag]         v0.3.0              -> v0.3.0
 * [new tag]         v0.30.0             -> v0.30.0
 * [new tag]         v0.31.0             -> v0.31.0
 * [new tag]         v0.32.0             -> v0.32.0
 * [new tag]         v0.33.0             -> v0.33.0
 * [new tag]         v0.33.1             -> v0.33.1
 * [new tag]         v0.34.0             -> v0.34.0
 * [new tag]         v0.35.0             -> v0.35.0
 * [new tag]         v0.35.1             -> v0.35.1
 * [new tag]         v0.36.0             -> v0.36.0
 * [new tag]         v0.37.0             -> v0.37.0
 * [new tag]         v0.37.1             -> v0.37.1
 * [new tag]         v0.37.2             -> v0.37.2
 * [new tag]         v0.37.3             -> v0.37.3
 * [new tag]         v0.37.3+alpha       -> v0.37.3+alpha
 * [new tag]         v0.37.3-alpha       -> v0.37.3-alpha
 * [new tag]         v0.37.4             -> v0.37.4
 * [new tag]         v0.38.0             -> v0.38.0
 * [new tag]         v0.39.0             -> v0.39.0
 * [new tag]         v0.4.0              -> v0.4.0
 * [new tag]         v0.40.0             -> v0.40.0
 * [new tag]         v0.41.0             -> v0.41.0
 * [new tag]         v0.42.0             -> v0.42.0
 * [new tag]         v0.43.0             -> v0.43.0
 * [new tag]         v0.44.0             -> v0.44.0
 * [new tag]         v0.44.1             -> v0.44.1
 * [new tag]         v0.44.2             -> v0.44.2
 * [new tag]         v0.44.3             -> v0.44.3
 * [new tag]         v0.45.0             -> v0.45.0
 * [new tag]         v0.45.1             -> v0.45.1
 * [new tag]         v0.46.0             -> v0.46.0
 * [new tag]         v0.46.1             -> v0.46.1
 * [new tag]         v0.46.2             -> v0.46.2
 * [new tag]         v0.46.3             -> v0.46.3
 * [new tag]         v0.47.0             -> v0.47.0
 * [new tag]         v0.48.0             -> v0.48.0
 * [new tag]         v0.49.0             -> v0.49.0
 * [new tag]         v0.5.0              -> v0.5.0
 * [new tag]         v0.50.0             -> v0.50.0
 * [new tag]         v0.51.0             -> v0.51.0
 * [new tag]         v0.52.0             -> v0.52.0
 * [new tag]         v0.53.0             -> v0.53.0
 * [new tag]         v0.54.0             -> v0.54.0
 * [new tag]         v0.55.0             -> v0.55.0
 * [new tag]         v0.56.0             -> v0.56.0
 * [new tag]         v0.57.0             -> v0.57.0
 * [new tag]         v0.58.0             -> v0.58.0
 * [new tag]         v0.59.0             -> v0.59.0
 * [new tag]         v0.6.0              -> v0.6.0
 * [new tag]         v0.60.0             -> v0.60.0
 * [new tag]         v0.61.0             -> v0.61.0
 * [new tag]         v0.62.0             -> v0.62.0
 * [new tag]         v0.63.0             -> v0.63.0
 * [new tag]         v0.64.0             -> v0.64.0
 * [new tag]         v0.65.0             -> v0.65.0
 * [new tag]         v0.66.0             -> v0.66.0
 * [new tag]         v0.7.0              -> v0.7.0
 * [new tag]         v0.8.0              -> v0.8.0
 * [new tag]         v0.9.0              -> v0.9.0
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
Unable to checkout refs/tags/v1.0.0 from https://github.com/googleapis/google-cloud-go.

goroutine 1 [running]:
main.main()
	/build/go/src/github.com/adisbladis/vgo2nix/main.go:249 +0x6d7

Can you test if it works with #42 ?

I still get an error:
panic: Error processing import path "go.etcd.io/etcd": nix-prefetch-git --fetch-submodules --no-deepClone --url https://github.com/etcd-io/etcd --rev v0.5.0-alpha.5.0.20200425165423-262c93980547 failed:
Initialized empty Git repository in /tmp/git-checkout-tmp-oQA0yyQK/etcd/.git/
fatal: couldn't find remote ref refs/tags/v0.5.0-alpha.5.0.20200425165423-262c93980547
From https://github.com/etcd-io/etcd
 * [new branch]      master         -> origin/master
 * [new branch]      release-0.4    -> origin/release-0.4
 * [new branch]      release-2.0    -> origin/release-2.0
 * [new branch]      release-2.1    -> origin/release-2.1
 * [new branch]      release-2.2    -> origin/release-2.2
 * [new branch]      release-2.3    -> origin/release-2.3
 * [new branch]      release-3.0    -> origin/release-3.0
 * [new branch]      release-3.1    -> origin/release-3.1
 * [new branch]      release-3.2    -> origin/release-3.2
 * [new branch]      release-3.3    -> origin/release-3.3
 * [new branch]      release-3.4    -> origin/release-3.4
 * [new tag]         0              -> 0
 * [new tag]         v0.1.0         -> v0.1.0
 * [new tag]         v0.1.1         -> v0.1.1
 * [new tag]         v0.1.2         -> v0.1.2
 * [new tag]         v0.2.0         -> v0.2.0
 * [new tag]         v0.2.0-rc0     -> v0.2.0-rc0
 * [new tag]         v0.2.0-rc1     -> v0.2.0-rc1
 * [new tag]         v0.2.0-rc2     -> v0.2.0-rc2
 * [new tag]         v0.2.0-rc3     -> v0.2.0-rc3
 * [new tag]         v0.2.0-rc4     -> v0.2.0-rc4
 * [new tag]         v0.3.0         -> v0.3.0
 * [new tag]         v0.4.0         -> v0.4.0
 * [new tag]         v0.4.1         -> v0.4.1
 * [new tag]         v0.4.2         -> v0.4.2
 * [new tag]         v0.4.3         -> v0.4.3
 * [new tag]         v0.4.4         -> v0.4.4
 * [new tag]         v0.4.5         -> v0.4.5
 * [new tag]         v0.4.6         -> v0.4.6
 * [new tag]         v0.4.7         -> v0.4.7
 * [new tag]         v0.4.8         -> v0.4.8
 * [new tag]         v0.4.9         -> v0.4.9
 * [new tag]         v0.5.0-alpha.0 -> v0.5.0-alpha.0
 * [new tag]         v0.5.0-alpha.1 -> v0.5.0-alpha.1
 * [new tag]         v0.5.0-alpha.2 -> v0.5.0-alpha.2
 * [new tag]         v0.5.0-alpha.3 -> v0.5.0-alpha.3
 * [new tag]         v0.5.0-alpha.4 -> v0.5.0-alpha.4
 * [new tag]         v0.5.0-alpha.5 -> v0.5.0-alpha.5
 * [new tag]         v2.0.0         -> v2.0.0
 * [new tag]         v2.0.0-rc.1    -> v2.0.0-rc.1
 * [new tag]         v2.0.1         -> v2.0.1
 * [new tag]         v2.0.10        -> v2.0.10
 * [new tag]         v2.0.11        -> v2.0.11
 * [new tag]         v2.0.12        -> v2.0.12
 * [new tag]         v2.0.13        -> v2.0.13
 * [new tag]         v2.0.2         -> v2.0.2
 * [new tag]         v2.0.3         -> v2.0.3
 * [new tag]         v2.0.4         -> v2.0.4
 * [new tag]         v2.0.5         -> v2.0.5
 * [new tag]         v2.0.6         -> v2.0.6
 * [new tag]         v2.0.7         -> v2.0.7
 * [new tag]         v2.0.8         -> v2.0.8
 * [new tag]         v2.0.9         -> v2.0.9
 * [new tag]         v2.1.0         -> v2.1.0
 * [new tag]         v2.1.0-alpha.0 -> v2.1.0-alpha.0
 * [new tag]         v2.1.0-alpha.1 -> v2.1.0-alpha.1
 * [new tag]         v2.1.0-rc.0    -> v2.1.0-rc.0
 * [new tag]         v2.1.1         -> v2.1.1
 * [new tag]         v2.1.2         -> v2.1.2
 * [new tag]         v2.1.3         -> v2.1.3
 * [new tag]         v2.2.0         -> v2.2.0
 * [new tag]         v2.2.0-alpha.0 -> v2.2.0-alpha.0
 * [new tag]         v2.2.0-alpha.1 -> v2.2.0-alpha.1
 * [new tag]         v2.2.0-rc.0    -> v2.2.0-rc.0
 * [new tag]         v2.2.1         -> v2.2.1
 * [new tag]         v2.2.2         -> v2.2.2
 * [new tag]         v2.2.3         -> v2.2.3
 * [new tag]         v2.2.4         -> v2.2.4
 * [new tag]         v2.2.5         -> v2.2.5
 * [new tag]         v2.3.0         -> v2.3.0
 * [new tag]         v2.3.0-alpha.0 -> v2.3.0-alpha.0
 * [new tag]         v2.3.0-alpha.1 -> v2.3.0-alpha.1
 * [new tag]         v2.3.1         -> v2.3.1
 * [new tag]         v2.3.2         -> v2.3.2
 * [new tag]         v2.3.3         -> v2.3.3
 * [new tag]         v2.3.4         -> v2.3.4
 * [new tag]         v2.3.5         -> v2.3.5
 * [new tag]         v2.3.6         -> v2.3.6
 * [new tag]         v2.3.7         -> v2.3.7
 * [new tag]         v2.3.8         -> v2.3.8
 * [new tag]         v3.0.0         -> v3.0.0
 * [new tag]         v3.0.0-beta.0  -> v3.0.0-beta.0
 * [new tag]         v3.0.1         -> v3.0.1
 * [new tag]         v3.0.10        -> v3.0.10
 * [new tag]         v3.0.11        -> v3.0.11
 * [new tag]         v3.0.12        -> v3.0.12
 * [new tag]         v3.0.13        -> v3.0.13
 * [new tag]         v3.0.14        -> v3.0.14
 * [new tag]         v3.0.15        -> v3.0.15
 * [new tag]         v3.0.16        -> v3.0.16
 * [new tag]         v3.0.17        -> v3.0.17
 * [new tag]         v3.0.2         -> v3.0.2
 * [new tag]         v3.0.3         -> v3.0.3
 * [new tag]         v3.0.4         -> v3.0.4
 * [new tag]         v3.0.5         -> v3.0.5
 * [new tag]         v3.0.6         -> v3.0.6
 * [new tag]         v3.0.7         -> v3.0.7
 * [new tag]         v3.0.8         -> v3.0.8
 * [new tag]         v3.0.9         -> v3.0.9
 * [new tag]         v3.1.0         -> v3.1.0
 * [new tag]         v3.1.0-alpha.0 -> v3.1.0-alpha.0
 * [new tag]         v3.1.0-alpha.1 -> v3.1.0-alpha.1
 * [new tag]         v3.1.0-rc.0    -> v3.1.0-rc.0
 * [new tag]         v3.1.0-rc.1    -> v3.1.0-rc.1
 * [new tag]         v3.1.1         -> v3.1.1
 * [new tag]         v3.1.10        -> v3.1.10
 * [new tag]         v3.1.11        -> v3.1.11
 * [new tag]         v3.1.12        -> v3.1.12
 * [new tag]         v3.1.13        -> v3.1.13
 * [new tag]         v3.1.14        -> v3.1.14
 * [new tag]         v3.1.15        -> v3.1.15
 * [new tag]         v3.1.16        -> v3.1.16
 * [new tag]         v3.1.17        -> v3.1.17
 * [new tag]         v3.1.18        -> v3.1.18
 * [new tag]         v3.1.19        -> v3.1.19
 * [new tag]         v3.1.2         -> v3.1.2
 * [new tag]         v3.1.20        -> v3.1.20
 * [new tag]         v3.1.3         -> v3.1.3
 * [new tag]         v3.1.4         -> v3.1.4
 * [new tag]         v3.1.5         -> v3.1.5
 * [new tag]         v3.1.6         -> v3.1.6
 * [new tag]         v3.1.7         -> v3.1.7
 * [new tag]         v3.1.8         -> v3.1.8
 * [new tag]         v3.1.9         -> v3.1.9
 * [new tag]         v3.2.0         -> v3.2.0
 * [new tag]         v3.2.0-rc.0    -> v3.2.0-rc.0
 * [new tag]         v3.2.0-rc.1    -> v3.2.0-rc.1
 * [new tag]         v3.2.1         -> v3.2.1
 * [new tag]         v3.2.10        -> v3.2.10
 * [new tag]         v3.2.11        -> v3.2.11
 * [new tag]         v3.2.12        -> v3.2.12
 * [new tag]         v3.2.13        -> v3.2.13
 * [new tag]         v3.2.14        -> v3.2.14
 * [new tag]         v3.2.15        -> v3.2.15
 * [new tag]         v3.2.16        -> v3.2.16
 * [new tag]         v3.2.17        -> v3.2.17
 * [new tag]         v3.2.18        -> v3.2.18
 * [new tag]         v3.2.19        -> v3.2.19
 * [new tag]         v3.2.2         -> v3.2.2
 * [new tag]         v3.2.20        -> v3.2.20
 * [new tag]         v3.2.21        -> v3.2.21
 * [new tag]         v3.2.22        -> v3.2.22
 * [new tag]         v3.2.23        -> v3.2.23
 * [new tag]         v3.2.24        -> v3.2.24
 * [new tag]         v3.2.25        -> v3.2.25
 * [new tag]         v3.2.26        -> v3.2.26
 * [new tag]         v3.2.27        -> v3.2.27
 * [new tag]         v3.2.28        -> v3.2.28
 * [new tag]         v3.2.29        -> v3.2.29
 * [new tag]         v3.2.3         -> v3.2.3
 * [new tag]         v3.2.30        -> v3.2.30
 * [new tag]         v3.2.31        -> v3.2.31
 * [new tag]         v3.2.4         -> v3.2.4
 * [new tag]         v3.2.5         -> v3.2.5
 * [new tag]         v3.2.6         -> v3.2.6
 * [new tag]         v3.2.7         -> v3.2.7
 * [new tag]         v3.2.8         -> v3.2.8
 * [new tag]         v3.2.9         -> v3.2.9
 * [new tag]         v3.3.0         -> v3.3.0
 * [new tag]         v3.3.0-rc.0    -> v3.3.0-rc.0
 * [new tag]         v3.3.0-rc.1    -> v3.3.0-rc.1
 * [new tag]         v3.3.0-rc.2    -> v3.3.0-rc.2
 * [new tag]         v3.3.0-rc.3    -> v3.3.0-rc.3
 * [new tag]         v3.3.0-rc.4    -> v3.3.0-rc.4
 * [new tag]         v3.3.1         -> v3.3.1
 * [new tag]         v3.3.10        -> v3.3.10
 * [new tag]         v3.3.11        -> v3.3.11
 * [new tag]         v3.3.12        -> v3.3.12
 * [new tag]         v3.3.13        -> v3.3.13
 * [new tag]         v3.3.14        -> v3.3.14
 * [new tag]         v3.3.14-beta.0 -> v3.3.14-beta.0
 * [new tag]         v3.3.14-rc.0   -> v3.3.14-rc.0
 * [new tag]         v3.3.15        -> v3.3.15
 * [new tag]         v3.3.16        -> v3.3.16
 * [new tag]         v3.3.17        -> v3.3.17
 * [new tag]         v3.3.18        -> v3.3.18
 * [new tag]         v3.3.19        -> v3.3.19
 * [new tag]         v3.3.2         -> v3.3.2
 * [new tag]         v3.3.20        -> v3.3.20
 * [new tag]         v3.3.21        -> v3.3.21
 * [new tag]         v3.3.22        -> v3.3.22
 * [new tag]         v3.3.23        -> v3.3.23
 * [new tag]         v3.3.24        -> v3.3.24
 * [new tag]         v3.3.25        -> v3.3.25
 * [new tag]         v3.3.3         -> v3.3.3
 * [new tag]         v3.3.4         -> v3.3.4
 * [new tag]         v3.3.5         -> v3.3.5
 * [new tag]         v3.3.6         -> v3.3.6
 * [new tag]         v3.3.7         -> v3.3.7
 * [new tag]         v3.3.8         -> v3.3.8
 * [new tag]         v3.3.9         -> v3.3.9
 * [new tag]         v3.4.0         -> v3.4.0
 * [new tag]         v3.4.0-rc.0    -> v3.4.0-rc.0
 * [new tag]         v3.4.0-rc.1    -> v3.4.0-rc.1
 * [new tag]         v3.4.0-rc.2    -> v3.4.0-rc.2
 * [new tag]         v3.4.0-rc.3    -> v3.4.0-rc.3
 * [new tag]         v3.4.0-rc.4    -> v3.4.0-rc.4
 * [new tag]         v3.4.1         -> v3.4.1
 * [new tag]         v3.4.10        -> v3.4.10
 * [new tag]         v3.4.11        -> v3.4.11
 * [new tag]         v3.4.12        -> v3.4.12
 * [new tag]         v3.4.13        -> v3.4.13
 * [new tag]         v3.4.2         -> v3.4.2
 * [new tag]         v3.4.3         -> v3.4.3
 * [new tag]         v3.4.4         -> v3.4.4
 * [new tag]         v3.4.5         -> v3.4.5
 * [new tag]         v3.4.6         -> v3.4.6
 * [new tag]         v3.4.7         -> v3.4.7
 * [new tag]         v3.4.8         -> v3.4.8
 * [new tag]         v3.4.9         -> v3.4.9
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
Unable to checkout refs/tags/v0.5.0-alpha.5.0.20200425165423-262c93980547 from https://github.com/etcd-io/etcd.

goroutine 1 [running]:
main.main()
	/build/go/src/github.com/adisbladis/vgo2nix/main.go:290 +0x6d7

The way I tested was:
git clone https://github.com/SuperSandro2000/vgo2nix
nix-build vgo2nix -I nixpkgs="path to unstable channel"
# doesn't build on the nixos-20.03 channel
git clone -b 2.00 https://github.com/chrislusf/seaweedfs
result/bin/vgo2nix -dir seaweedfs

By the way, what is the advantage of using vgo2nix when you can use buildGoModule
While searching for solutions, I made it work (on the unstable branch):
{ stdenv, buildGoModule, fetchFromGitHub }:
buildGoModule rec {
  name = "seaweedfs-${version}";
  version = "2.00";
  src = fetchFromGitHub {
    owner  = "chrislusf";
    repo   = "seaweedfs";
    rev    = "${version}";
    sha256 = "0i74c6fydsh85hfnzf2fyw0chwcyr9bp74cf2gakwgcsr7h8bz6p";
  };
#   goPackagePath = "weed";
#   goDeps = ./deps.nix;
  subPackages = ["weed"];
  vendorSha256 = "0i8lsz6fplkk2i5k1sxh2l0vqx08qsw7hqr4nikzccg39gkf8znh";
  modSha256 = null;

  meta = with stdenv.lib; {
    inherit (src.meta) homepage;
    description = "SeaweedFS";
    longDescription = "SeaweedFS is a simple and highly scalable distributed file system.";
    license = with licenses; [ apache ];
    maintainers = with maintainers; [ netixx ];
    # platforms = with platforms; linux;
  };
}

By the way, what is the advantage of using vgo2nix when you can use buildGoModule

One is vendoring all dependencies in one nix store entry and the other is creating one for each dependency.


Update usage-analytics-data-model.md

Don't see the tenant office licenses dataset anymore on multiple tenants. This PR removes that from the table..Please review and approve.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/2672

@Sirkkuw Please merge this PR. Thanks

@yogkumgit this topic was recently updated and the PG was involved. I think it is correct.


Flip coin pipeline compiled

Hi @diegolovison please consider unifying the name and use flip_coin_compiled.yaml (without the .py)
`


SassC supporting

SassC supporting. Very difficult to add something helpful for me in readme.
Closes #23.

Looks good to me


Update go 1 18 3

I updated go 1.15.6 -> 1.18.3

@to-lz1 I found that GitHub Actions is disabled in this repo. Is there any reason?

@hirosassa Oh, I didn't notice that. I'm sorry.
I've checked GitHub Actions configuration, but found that I can't enable them myself.
I think "Server Test" and "Client (JS) Test" should be enabled now, and we'll maintain release related jobs afterwards(this may be another PR).

@to-lz1 I enabled some config of GitHub Actions. Could you push some commit to run it?

@hirosassa Sorry for late reply, but I can't figure out why Github Actions still not work.
They seem work well in my forked repo. https://github.com/to-lz1/dsps/actions
Shall I change target branch from main to another new branch?


feat: Promote NsRecord into a core object

... by extending noosphere_core::data::LinkRecord with its functionality, and removing the noosphere_ns dependency on validating records. Fixes #395

Reconfigured to wrap a Ucan, not dissimilar from NsRecord; updating accordingly

Promote noosphere_core::authority::generate_capability(identity: &str, action: SphereAction)
Remove optional DidParser from LinkRecord::validate method
Updated some traits accordingly, similar to what NsRecord needed as a Ucan wrapper (rather than a Jwt wrapper)
Updated method names (with no static methods, dereference was redundant with link, renamed to get_link())


cannot start realsense with roslaunch

Required Info

Camera Model
{D400 }

Firmware Version

Operating System & Version
{Ubuntu16.04LTS

Kernel Version (Linux Only)
4.13.0-36-generic

Platform
PC

SDK Version
{ legacy / 2.10.0 }

Issue Description
The result from
roslaunch realsense_ros_camera rs_camera.launch
is
...[ERROR] [1519547419.761483128]: An exception has been thrown: libusb_bulk_transfer(...) returned LIBUSB_ERROR_IO Last Error: Resource temporarily unavailable [FATAL] [1519547419.761874994]: Failed to load nodelet '/camera/realsense_ros_camera of type realsense_ros_camera/RealSenseNodeFactory to manager realsense_ros_camera_manager' [camera/realsense_ros_camera-3] process has died [pid 2139, exit code 255, cmd /opt/ros/kinetic/lib/nodelet/nodelet load realsense_ros_camera/RealSenseNodeFactory realsense_ros_camera_manager __name:=realsense_ros_camera __log:=/home/yuki/.ros/log/1c2f9e16-1a06-11e8-a924-d4258b2da0d7/camera-realsense_ros_camera-3.log]. log file: /home/yuki/.ros/log/1c2f9e16-1a06-11e8-a924-d4258b2da0d7/camera-realsense_ros_camera-3*.log ^C[camera/realsense_ros_camera_manager-2] killing on exit [ INFO] [1519547422.255184747]: Interrupt Signal is received! Terminating RealSense Node... [camera/realsense_ros_camera_manager-2] escalating to SIGTERM
i used sudo chmod 666 /dev/video...commando, but there was no change.

Hello @agari1229, have you managed to streaming using LibRealSense tools such as realsense-viewer or rs-capture?
Also, could you please provide the output of rs-enumerate-devices?

i could solve the problem by applying the patch of uvcvideo.
i referred ti the following two.
url1
url2
Thanks.


Logout Button Confirm Dialogue

Logout button on Hub doesn't log out immediately and informs user that only way to log back in is with a QRCode.
Optional: button in dialogue to direct to generate activity

Just implemented and tested this on my branch. Not closing until a pull request to Staging is merged, however.


Typescript+JSX Syntax Highlighting in generator functions

From @nmain on July 11, 2018 18:43

VSCode Version: 1.25.0 (ia32)
OS Version: Windows 10

Steps to Reproduce:

Create a .tsx file with the following content:

class Baz { }

class F {
	public *foo() {
		yield <Baz />;
	}

	public fuu() {
		return <Baz />;
	}
}

Look at the syntax highlighting.  The first <Baz /> won't have the correct syntax highlighting.

Does this issue occur when all extensions are disabled?: Yes
Copied from original issue: Microsoft/vscode#54091

From @vscodebot[bot] on July 11, 2018 18:43
(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

Syntax highlighting stopped working (#51553)

The problem here seems to be yield with a jsx expression


Add text annotation component to API

Goal
Create a component that allows users to highlight phrases in text content and annotate them.
Intended use
NER tagging. See https://prodi.gy/docs/named-entity-recognition#manual-patterns
Specifics
The component can have two major properties: tags: List[str] and content: str. The content (markdown allowed, like in ui.text()) is rendered as a block of text. The tags are rendered as clickable elements that tag the highlighted text.
On submit, the component can send this array:
[
   { text: 'Europe', tag: 'continent' },
   { text: 'fish and chips', tag: 'food' },
]

TBD

What should we call this? ui.annotator()?
What should the UX be? Select tag first and then highlight text? Or vice-versa? Or something else?

@lo5 this came up as a customer feature request again with Prodigy given as a comparison.  How feasible is this?

@tkmaker - We can prioritize - just needs a good API design, should be straightforward to implement. @mturoci?

I can start implementing this once the API is agreed.
http://doccano.herokuapp.com/demo/named-entity-recognition/# - seems very neat as of UX. We could maybe also include color and shortcut to the proposed tags attr.

How about this?
ui.annotator(
  name='foo',
  tags=[
    ui.annotator_tag(name='p', label='Person', color='$red'),
    ui.annotator_tag(name='o', label='Org', color='$green'),
  ],
  items=[
    ui.annotator_item(text='Killer Mike', tag='p'),
    ui.annotator_item(text=' is a member of the hip hop supergroup '), # no tag
    ui.annotator_item(text='Run the Jewels', tag='o'),
  ],
)`

This way, the component can be initialized with annotated text, and the return path can contain an identical data structure:
{
  { text: "Killer Mike", tag: "p" },
  { text: " is a member of the hip hop supergroup " },
  { text: "Run the Jewels", tag: "o" ),
}

Note: No shortcut for now - let's think about that in a future version.

@mturoci tagged 0.15 for now, but we can ship with 0.14 if ready.

The http://doccano.herokuapp.com/demo/named-entity-recognition/#  example requires a user to first highlight text and click on the entity every time after the selection. It might better to first allow a user to click on an entity eg "ORG" and then select one or more orgs in the text. That way they dont have to keep specifying what the entity is.

@tkmaker If I understand correctly, you're suggesting that a tag works more like a highlighter?

@tkmaker If I understand correctly, you're suggesting that a tag works more like a highlighter?

Yes similar to what Prodigy does: https://prodi.gy/demo

OK. @shivam5992 @mtanco?

@lo5 the proposed solution looks good and will be helpful.


Add setup.py and some simple tests for the python/proto interface

To use:
$ python setup.py build_py
$ python setup.py install
$ python ord_schema/proto/ord_schema_pb2_test.py

After this is merged, I'll update the CI to run these tests automatically.

FYI I'm using Google python style: http://google.github.io/styleguide/pyguide.html

Thanks! I like absl a lot; we use it internally and absl.flags has the best flag parsing setup I've seen: https://abseil.io/docs/python/guides/flags


bring to front & send to back buttons

so user can organise which object shows on the front which ones are at the back.

I thought about the same thing but the problem is time :)


get_stream_ctrl_format_size(...) returns Invalid mode on some examples, not on others

After building on macOS Sierra 10.12.6 and running cpp-tutorial-1-depth, the following occurs:

With an R200 plugged in: Everything works as normal
With the SR300 plugged in:

There are 1 connected RealSense devices.

Using device 0, an Intel RealSense SR300
    Serial number:<PHONE_NUMBER>48
    Firmware version: <IP_ADDRESS>
rs::error was thrown when calling rs_start_source(device:0x7fc9dd002a20, source:VIDEO):
    get_stream_ctrl_format_size(...) returned Invalid mode

When running cpp-config-ui, however, the SR300 works as expected.
What am I missing?
Here is the CMake output if needed
-- Info: REALSENSE_VERSION_STRING=1.12.2
-- The C compiler identification is GNU 7.2.0
-- The CXX compiler identification is GNU 7.2.0
-- Checking whether C compiler has -isysroot
-- Checking whether C compiler has -isysroot - yes
-- Checking whether C compiler supports OSX deployment target flag
-- Checking whether C compiler supports OSX deployment target flag - yes
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Check for working CXX compiler: /usr/bin/g++
-- Check for working CXX compiler: /usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Performing Test COMPILER_SUPPORTS_CXX0X
-- Performing Test COMPILER_SUPPORTS_CXX0X - Success
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Checking for one of the modules 'libusb-1.0'
-- Found OpenGL: /System/Library/Frameworks/OpenGL.framework
-- Configuring done
CMake Warning (dev):
  Policy CMP0042 is not set: MACOSX_RPATH is enabled by default.  Run "cmake
  --help-policy CMP0042" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

  MACOSX_RPATH is not specified for the following targets:

   realsense

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Generating done

Tested on the development branch, worked fine.


Is it possible to have a transparent background

I've tried
background: 'rgba(0,0,0,1)'

But I get a black background

Have you tried transparent?

@SamVerschueren Thanks, that was it


Optimize frontend bundle size season

Rabbit season

231 tests were run on f7ed7f8c. ❌ 2 Failed, ⚠ 4 Flaked. View Full Report ↗

❌ 2 Failed

Test Name
Failure Summary
Logs

[chromium] should show the FAQ page correctly.
The expected text "Real SaaS App" was not found in the page, and the FAQ heading was not visible.
Logs ↗

[chromium] should load the pricing page correctly.

Logs ↗

⚠ 4 Flakes

Test Name
Failure Summary
Logs

[chromium] should navigate to the dashboard after login correctly.
The test timed out waiting for the dashboard to be displayed after login.
Logs ↗

[chromium] should return list of users correctly.

Logs ↗

[chromium] should display error message for invalid login correctly.
The expected status code 401 was not received, instead a function was returned.
Logs ↗

[chromium] should login with credentials correctly correctly.

Logs ↗

settings


Port bit parsers to v5

Addresses #892 .
As the bits parsers are the only parsers that change the input type, previously inferred types now have to be explicitly named. This mostly affects tests and benchmarks in the crate; most users of the crate will likely explicitly type the input, which aids inference.
bits/mod.rd includes impl ParseError<I> for ((I, usize), ErrorKind) and impl ParseError<(I, usize)> for (I, ErrorKind) in order to satisfy trait bounds on combinators.

Hello, could you rebase your PR? It's a bit hard to review in that state

It looks like something is still wrong with the rebase (looking at the commits). could you check?

Ah thanks! I've managed to fix the history up.

why do you get type inference issues in 1025aa1d0787a27af60 ? Which Rust version are you using? Ideally there should only be e64f3ca7ca38 in the PR, the rest is unrelated

the CI indicates a test is failing: https://travis-ci.org/Geal/nom/jobs/546233532#L1285

I'll try to review the entire code this afternoon

why do you get type inference issues in 1025aa1 ? Which Rust version are you using? Ideally there should only be e64f3ca in the PR, the rest is unrelated

I'm on 1.35.0, and this is error I get when running cargo test.

The compiler is unable to infer between ParseError<I> and ParseError<(I, usize)> for
(I, ErrorKind), so you have to specify the full type of E in IResult<I, O, E>.

the CI indicates a test is failing: https://travis-ci.org/Geal/nom/jobs/546233532#L1285

I'll need to port over the code from bits.rs:124-127 that does a checked mul.

I didn't get an error for the issue_848_overflow_incomplete_bits_to_bytes test when I ran cargo test because it requires the regexp feature, which I think might be an incorrect configuration. Just an FYI.

ok, I think I know where the issue comes from. If we only take e64f3ca and apply this (ignoring the errors with crate:: import):
diff --git a/src/bits/macros.rs b/src/bits/macros.rs
index eeadbe5..d8c30c4 100755
--- a/src/bits/macros.rs
+++ b/src/bits/macros.rs
@@ -169,7 +169,7 @@ mod tests {
     assert_eq!(ch((&sl[..1], 0)), Err(Err::Incomplete(Needed::Size(5))));
   }

-  fn ch_bytes(input: &[u8]) -> IResult<&[u8], (u8, u8), ((&[u8], usize), ErrorKind)> {
+  fn ch_bytes(input: &[u8]) -> IResult<&[u8], (u8, u8), (&[u8], ErrorKind)> {
     bits!(input, ch)
   }

@@ -219,7 +219,7 @@ mod tests {
     }
   }

-  fn take_uint(input: (&[u8], usize), take: usize) -> IResult<(&[u8], usize), FakeUint, (&[u8], ErrorKind)> {
+  fn take_uint(input: (&[u8], usize), take: usize) -> IResult<(&[u8], usize), FakeUint, ((&[u8], usize), ErrorKind)> {
     take_bits!(input, take)
   }

diff --git a/src/bits/mod.rs b/src/bits/mod.rs
index d6935dd..ae5a815 100755
--- a/src/bits/mod.rs
+++ b/src/bits/mod.rs
@@ -62,6 +62,7 @@ where
   }
 }

+/*
 impl<I> ParseError<(I, usize)> for (I, ErrorKind) {
   fn from_error_kind((input, _): (I, usize), kind: ErrorKind) -> (I, ErrorKind) {
     (input, kind)
@@ -81,6 +82,7 @@ impl<I> ParseError<I> for ((I, usize), ErrorKind) {
     other
   }
 }
+*/

 /// Converts a byte-level input to a bit-level input, for consumption by a parser that uses bits.
 ///
@@ -103,10 +105,10 @@ impl<I> ParseError<I> for ((I, usize), ErrorKind) {
 ///
 /// assert_eq!(take_4_bits( sl ), Ok( (&sl[1..], 0xA) ));
 /// ```
-pub fn bits<I, O, E: ParseError<(I, usize)>, P>(parser: P) -> impl Fn(I) -> IResult<I, O, E>
+pub fn bits<I, O, E1: ParseError<(I, usize)>+Into<E2>, E2: ParseError<I>, P>(parser: P) -> impl Fn(I) -> IResult<I, O, E2>
 where
   I: InputIter<Item = u8> + Slice<RangeFrom<usize>>,
-  P: Fn((I, usize)) -> IResult<(I, usize), O, E>,
+  P: Fn((I, usize)) -> IResult<(I, usize), O, E1>,
 {
   move |input: I| match parser((input, 0)) {
     Ok(((rest, offset), res)) => {
@@ -114,16 +116,16 @@ where
       Ok((rest.slice(byte_index..), res))
     }
     Err(Err::Incomplete(n)) => Err(Err::Incomplete(n.map(|u| u / 8 + 1))),
-    Err(Err::Error(e)) => Err(Err::Error(e)),
-    Err(Err::Failure(e)) => Err(Err::Failure(e)),
+    Err(Err::Error(e)) => Err(Err::Error(e.into())),
+    Err(Err::Failure(e)) => Err(Err::Failure(e.into())),
   }
 }

 #[doc(hidden)]
-pub fn bitsc<I, O, E: ParseError<(I, usize)>, P>(input: I, parser: P) -> IResult<I, O, E>
+pub fn bitsc<I, O, E1: ParseError<(I, usize)>+Into<E2>, E2: ParseError<I>, P>(input: I, parser: P) -> IResult<I, O, E2>
 where
   I: InputIter<Item = u8> + Slice<RangeFrom<usize>>,
-  P: Fn((I, usize)) -> IResult<(I, usize), O, E>,
+  P: Fn((I, usize)) -> IResult<(I, usize), O, E1>,
 {
   bits(parser)(input)
 }
@@ -153,10 +155,10 @@ where
 ///
 /// assert_eq!(parse( input ), Ok(( &[][..], (0xd, 0xea, &[0xbe, 0xaf][..]) )));
 /// ```
-pub fn bytes<I, O, E: ParseError<I>, P>(parser: P) -> impl Fn((I, usize)) -> IResult<(I, usize), O, E>
+pub fn bytes<I, O, E1: ParseError<I>+Into<E2>, E2: ParseError<(I, usize)>, P>(parser: P) -> impl Fn((I, usize)) -> IResult<(I, usize), O, E2>
 where
   I: InputIter<Item = u8> + Slice<RangeFrom<usize>>,
-  P: Fn(I) -> IResult<I, O, E>,
+  P: Fn(I) -> IResult<I, O, E1>,
 {
   move |(input, offset): (I, usize)| {
     let inner = if offset % 8 != 0 {
@@ -164,16 +166,20 @@ where
     } else {
       input.slice((offset / 8)..)
     };
-    let (rest, res) = parser(inner)?;
-    Ok(((rest, 0), res))
+    match parser(inner) {
+      Ok((rest, res)) => Ok(((rest, 0), res)),
+      Err(Err::Incomplete(n)) => Err(Err::Incomplete(n.map(|u| u * 8))),
+      Err(Err::Error(e)) => Err(Err::Error(e.into())),
+      Err(Err::Failure(e)) => Err(Err::Failure(e.into())),
+    }
   }
 }

 #[doc(hidden)]
-pub fn bytesc<I, O, E: ParseError<I>, P>(input: (I, usize), parser: P) -> IResult<(I, usize), O, E>
+pub fn bytesc<I, O, E1: ParseError<I>+Into<E2>, E2: ParseError<(I, usize)>, P>(input: (I, usize), parser: P) -> IResult<(I, usize), O, E2>
 where
   I: InputIter<Item = u8> + Slice<RangeFrom<usize>>,
-  P: Fn(I) -> IResult<I, O, E>,
+  P: Fn(I) -> IResult<I, O, E1>,
 {
   bytes(parser)(input)
 }

From what I understand, you inverted the way errors were returned. bits! generates a parser that takes a I as input and returns a IResult<I, T, E> with E: ParseError<I>: https://github.com/Geal/nom/blob/master/src/bits.rs#L19
while the new bits function returns a IResult<I, T, E> with E: ParseError<(I, usize)>: https://github.com/Geal/nom/pull/957/commits/e64f3ca7ca38078d60a0e99056fc59c0b3e49a39#diff-c182431a163705ad034394497e21d004R106
If you take the modifications I show on bits, bitsc, bytes and bytesc, you can avoid the ParseError modifications, and revert all the changes made to the tests.
As an example, the bits_to_bytes test previously had a ch_bytes with (&[u8], ErrorKind) as error type: https://github.com/Geal/nom/blob/master/src/bits.rs#L324-L327

So I took this route initially when I first encountered the ParseError trait bound problem. The issue is that for the default error type (I, ErrorKind), any non-local trait implementation on the I generic type will not compile due to orphan rules.
// This will fail to compile.
impl<I> From<((I, usize), ErrorKind)> for (I, ErrorKind) { .. }

That's why I had to use the ParseError trait to create the necessary polymorphism.
If you're amenable to it, we can still use a From style impl by creating a newtype for (I, ErrorKind), maybe something like this.
pub struct NomError<I>((I, ErrorKind));

This solves the orphan rules problem, and is recommended in that error message.

why would there be an issue with orphan rules from within nom's code?

oh, right, I see what you mean. I'll test some things and see if I can fix this

I've rewritten from scratch in c71ddc6, 51ce76a, 0313c1d and 1aeea19, it was easier than going through all the tests that were modified.
Instead of using a From implementation that suffers from the orphan rules, there's an internal trait for error conversion. This is not the prettiest solution, but it minimizes the impact of the change.
Thank you so much for your help!


Query: Fixes Persisted continuationToken issue by turning off ODE by default (#4413) and Fixes bug in OrderByCrossPartitionQueryPipelineStage to ensure that errors in inner pipeline creation are bubbled up (#4419)

Pull Request Template
Description
Cherry-pick of merged pr:
https://github.com/Azure/azure-cosmos-dotnet-v3/pull/4413
Also contains cherry-pick of:
https://github.com/Azure/azure-cosmos-dotnet-v3/commit/08338af632dcbda8d2afdce756a57ea45b09a745
Type of change
Please delete options that are not relevant.

[] Bug fix (non-breaking change which fixes an issue)
[] New feature (non-breaking change which adds functionality)
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] This change requires a documentation update

Closing issues
To automatically close an issue: closes #IssueNumber

This PR is now no-op since another change subsumed all cherry picks that were intended to go in as part of this change:
https://github.com/Azure/azure-cosmos-dotnet-v3/commit/299b86a97998f9bc807352d02698ad73763a451f#diff-f422eefcb9a18445788c16c749c10183eae1300584517d9a6954957fb8e4e8cd