[error]: GPTAssistantAgent doesn't work with gpt model from Microsoft Azure

I am trying to apply the gpt-4-1106 model from Microsoft Azure to run the GPTAssistantAgent. Then I got error:
    _Error code: 404 - {'error': {'code': '404', 'message': 'Resource not found'}}
    httpx.HTTPStatusError: Client error '404 Resource Not Found' for url 'https://my azure openai base url/openai/deployments/gpt-4-1106/assistants'
    For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404

    During handling of the above exception, another exception occurred:

      File "/home/yzj/LLM_project/writer_v0.0/writer.py", line 60, in <module>
        planner = GPTAssistantAgent(
    openai.NotFoundError: Error code: 404 - {'error': {'code': '404', 'message': 'Resource not found'}}_

my oai_config_list is as below:
{         "model":"gpt-4-1106",         "api_type":"azure",         "base_url": "****",         "api_key":"****" },
Is this because the GPTAssistantAgent only run with OpenAI api?

@gagb fyi

@YuanZongjian , GPTAssistantAgent uses the OpenAssistant API which is not available on Azure yet.

@YuanZongjian , GPTAssistantAgent uses the OpenAssistant API which is not available on Azure yet.

Okay, I see. Thank you

May I ask if I cannot use the base_url "localhost:8000/v1" when using the FastChat API on the local end? I encountered an openai.notfounderror with the GPTAssistantAgent, too. The error code is 404.
I have another question:
Is there any difference between running a Python program with GPTAssistantAgent and UserProxyAgent?
It seems like the code interpreter function and the "run Python" function in UserProxyAgent are very similar.
Thank you for your answer.


Use Application Insights exception tracing for application insights sample

Addressing this issue: https://github.com/microsoft/BotBuilder-Samples/issues/2082

@Kaiqb Let me know when you have some time, i'd like to discuss this change and what (if anything) we want to add/change for documentation (maybe on this page).


XYZ class causes layer deviation when using html2canvas printinga a picture

I user XYZ class as the source to add arcgis tiled layer. The code below:
const arcgisXYZTileSource = new XYZ({
tileGrid: tileGrid,
projection: EPSG:${spatialReference.wkid},
url: serverUrl,
tilePixelRatio: 2,
crossOrigin: "anonymous",
});
If I want to use html2canvas ,the layer which I added by XYZ will skew from the orign;

If I use TileArcGISRest class as the source,the picture is normal.
const arcgisXYZTileSource = new ArcGISTileLayer({
tileGrid: tileGrid,
projection: EPSG:${spatialReference.wkid},
url: serverUrl,
tilePixelRatio: 2,
crossOrigin: "anonymous",
});

The same problem can be seen if options.tilePixelRatio = 2; is specified if https://openlayers.org/en/latest/examples/print-to-scale.html tilePixelRatio is not a supported option for ol/source/TileArcGISRest which suggests tilePixelRatio: 2 is the incorrect value for the ol/source/XYZ setup regardless of whether html2canvas works with sources having differing pixel ratios.

The same problem can be seen if options.tilePixelRatio = 2; is specified if https://openlayers.org/en/latest/examples/print-to-scale.html tilePixelRatio is not a supported option for ol/source/TileArcGISRest which suggests tilePixelRatio: 2 is the incorrect value for the ol/source/XYZ setup regardless of whether html2canvas works with sources having differing pixel ratios.
Thannks.I solved this problem by  options.tilePixelRatio = 1 with XYZ source


[PORT] Porting adaptiveexpressions tests to xunit

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/4138

Fixes #4085
Changed projects

AdaptiveExpressions.Tests

N/A


Reaper Scans no pages error but webview works

Source information
Reaper Scans 1.4.54
Source language
English
Steps to reproduce

Click new chapter. (Solo Resurrection is what I was trying to read)
No pages error pops up
Click webview
Webview works fine as if no issue

Expected behavior
Clicking new chapter loads the chapter.
Actual behavior
Clicking new chapter gives no pages error.
Mihon/Tachiyomi version
0.16.5
Android version
Android  version 14
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Seems like chapters uploaded before today load fine, but new chapters get the error


Running two top-level targets with overlapping third party Rust crates results in cascading build failures

Description
When running two top-level targets that have overlapping third party Rust crate dependencies with targets generated by reindeer, cascading build failures will occur.
Reproduction
This can be reproduced when they’re run at the same time in two different terminals. First, create two Rust binaries that depend on at least one of the same third party Rust crates (let's call them foo and bar). Then, vendor the third party rust crates with reindeer and then run each target in two different terminals.
One terminal:
buck2 run :foo

Another terminal:
buck2 run :bar

You will see multiple errors in each terminal.
Here's an example from the first terminal:
Local command returned non-zero exit code 1                                                                                [14/1076]
Reproduce locally: `/usr/bin/env "PYTHONPATH=buck-out/v2/gen/prelude/213ed1b7ab869379/rust/tools/__rustc_action__/__rust ...<omitted>... t/213ed1b7ab869379/third-party/rus
t/__strsim-0.10.0__/rlib-pic-static_pic-link/strsim-link-diag.args (run `buck2 log what-failed` to get the full command)`
stdout:
stderr:
error: failed to create encoded metadata from file: No such file or directory (os error 2)

error: aborting due to previous error

Action failed: root//third-party/rust:adler-1.0.2 (rustc rlib-pic-static_pic-link/adler-link rlib,pic,link [diag])
Local command returned non-zero exit code 1
Reproduce locally: `/usr/bin/env "PYTHONPATH=buck-out/v2/gen/prelude/213ed1b7ab869379/rust/tools/__rustc_action__/__rust ...<omitted>... root/213ed1b7ab869379/third-party/
rust/__adler-1.0.2__/rlib-pic-static_pic-link/adler-link-diag.args (run `buck2 log what-failed` to get the full command)`
stdout:
stderr:
error: couldn't create a temp dir: No such file or directory (os error 2) at path "/Users/nick/src/si/buck-out/v2/gen/root/213ed1b7ab869379/third-party/rust/__adler-1.0.2_
_/rlib-pic-static_pic-link/extras/libadler/rmetaYIVsgh"

error: aborting due to previous error

Here's an example from the second terminal:
error: Failed to load argument file: IO Error: /Users/nick/src/si/buck-out/v2/tmp/root/213ed1b7ab869379/third-party/rust/__anstyle-1.0.0__/rustc/_buck_936af9e130ade2[0/47]
tc-args-b9fle1tv.txt: No such file or directory (os error 2)

Action failed: root//third-party/rust:hashbrown-0.12.3 (rustc rlib-pic-static_pic-link/hashbrown-link rlib,pic,link [diag])
Local command returned non-zero exit code 1
Reproduce locally: `/usr/bin/env "PYTHONPATH=buck-out/v2/gen/prelude/213ed1b7ab869379/rust/tools/__rustc_action__/__rust ...<omitted>... d1b7ab869379/third-party/rust/__ha
shbrown-0.12.3__/rlib-pic-static_pic-link/hashbrown-link-diag.args (run `buck2 log what-failed` to get the full command)`
stdout:
stderr:
error: could not write output to buck-out/v2/gen/root/213ed1b7ab869379/third-party/rust/__hashbrown-0.12.3__/rlib-pic-static_pic-link/extras/libhashbrown/hashbrown-174a03d
2.hashbrown.5a421c79-cgu.0.rcgu.o: No such file or directory

error: aborting due to previous error

Build ID: b8817a51-747b-43ab-8692-a1fa0b0d814e
Jobs completed: 2.0 K. Time elapsed: 3.6s. Cache hits: 0%. Commands: 82 (cached: 0, remote: 0, local: 82)
BUILD FAILED
Failed to build 'root//third-party/rust:hashbrown-0.12.3 (prelude//platforms:default#213ed1b7ab869379)'

Additional Thoughts

This appears to be OS/ARCH agnostic
I am wondering if DICE is working as intended here as I would expect the third party crate to be built once (wherever its seen in the graph first) and its output to be used for both binaries

As an aside, thanks for this great project!

It's generally expected that you'd use isolation directories for concurrent builds. At least for LSPs at fb, isolation directories are used to prevent LSP-spawned processes from clobbering terminal-spawned process and vice-versa.
(Speaking only as a user of Buck2, not as a member of the team, I'd love to have more fine-grained locking inside of Buck2, but I understand that it might be very tricky to implement.)

I think this is a slightly different thing? The buck2 daemon for me seems to do this correctly - if I run 5 different run targets in quick succession, which have overlapping build requirements, the daemon knows that it should wait on another concurrent build to make progress. We see this behavior consistently for roughly half of our team.
For the other half, they consistently just get build failures (that, indeed, look like isolation issues.) But it feels like this is one of the primary use cases for buck2 - being able to have the build daemon and the more granular build graph handle this kind of optimization. Certainly for those of us who have it working, it is, as the kids say, super sweet. So the issue does feel somehow more fundamental.

@davidbarsky also, it makes sense that the LSP would want a separate isolation directory, because you don't want your editor to ever block another build. This is a slightly different problem. :)

Adding onto what @adamhjk said: in his terminal panes, there are logs containing waiting on another command task (or similar wording, cannot recall precisely). In my terminal panes, I don't see those logs at all, and each buck2 invocation appears to just continue as if they were building in isolation.

@adamhjk Yup, it probably is: I ran this by Wendy—I don't think she's on GitHub—and she said that she suspects that "the buckconfigs for controlling concurrent command behavior is not enabled".
(I'm not sure how to enable it, as I unknowingly messaged her while she was on a road trip.)

Cool! we can dig around. I think it's related to this FAQ entry not quite doing what we expect:
https://buck2.build/docs/faq/common_issues/#are-multiple-concurrent-commands-supported

Doesn't seem to be a documented config option that turns this behavior on or off.

I'm guessing you want this
In app/buck2_server/src/daemon/state.rs there's this code that should control it
        let nested_invocation_config = root_config
            .parse::<NestedInvocation>("buck2", "nested_invocation")?
            .unwrap_or(NestedInvocation::Run);

        let parallel_invocation_config = root_config
            .parse::<ParallelInvocation>("buck2", "parallel_invocation")?
            .unwrap_or(ParallelInvocation::Run);

Used in .buckconfig as
[buck2]
  /// other keys
  parallel_invocation = run | block | error
  nested_invocation = run | error

On Mon, Jun 5, 2023 at 7:45 AM Thomas Orozco @.***>
wrote:

We really should flip the default for this to have the "correct" behavior.
I'll send a diff for it

Isn’t the default “run” tho, which is the correct behavior?

Isn’t the default “run” tho, which is the correct behavior?

The default is run, but to get correct behavior, you'd need:
[buck2]
  parallel_invocation = block
  nested_invocation = error
  dice_cleanup = block

Thank you @krallin! Haven't tried it yet, but I will soon.


Fix #353 - Add settings option for password length.

Add settings option for password length.
Use password length for password validation and password generation.

@obuchmann I have just done some minor code cleanup and renamed password_length to min_password_length where applicable to make it clear this is a minimum password length. I'll be happy to include this in release 1.5.0 of the User plugin after some testing. I have tested it myself and it works well.

I just did a test run of these changes. Everything is working as expected :+1:
Great work @obuchmann and @bennothommo 	!

Done @LukeTowers. :)


Improve handling of accounts where email address is verified

Some users get stuck on the holding page after having verified their email in another channel. This leads to a poor user experience.
In the case where the email address has been verified, the user should no longer be stuck on the holding page. The use should also not have the option of sending another verification message (which will "fail" with a cryptic error message as the email address has already been verified -- but the user doesn't see that, they see only a "unable to verify, try again later" message)
Some places where this could be improved:

before sending a new email verification message, check the status of the email address. Only send the verification message if the email address is not verified.
on each page load, check the status of the email address. Should the holding page reload itself periodically?

Now that we're using Auth0's "Safelink" system, we're seeing nearly zero users who are stuck on the email address validation holding page.


Added svc privilege check patch and fixed SMDH in Makefile.

Allowing for now, since we don't know why changing the ACL is insufficient.

I just figured I'd throw it in since it's such a simple change in the
interim.
On Apr 5, 2015 12:02 PM, "Myriachan"<EMAIL_ADDRESS>wrote:

Merged #1 https://github.com/Myriachan/libkhax/pull/1.
—
Reply to this email directly or view it on GitHub
https://github.com/Myriachan/libkhax/pull/1#event-273680654.


GH-194: Make KafkaEmbedded as a bean

Fixes: spring-projects/spring-kafka#194
To avoid concurrent calls of the shutdown hooks make an KafkaEmbedded
as a Lifecycle to let ApplicationContext to call stop() before
destroying itself
That way the Kafka servers and zookeeper and also working directory
are destroyed and removed before JMV shutdown hooks
and FileNotFoundException /tmp/kafka-3266968904825284552/replication-offset-checkpoint.tmp
should disappear

Cool!
We should add some docs above here. Something like...

It is generally recommended to use the rule as a @ClassRule to avoid starting/stopping the broker between tests (and use a different topic for each test). If you are using Spring's test application context caching, you can also declare a KafkaEmbedded bean, so a single broker can be used across multiple test classes.

(plus some example configuration).

Yeah,,, I also thought about something like @EmbeddedKafka on the test class level, but since I'm not familiar with the Spring Test Framework caching magic, I'm not sure that registering bean from that level would work as expected...
Just need to get some feedback from @hoaz to go ahead!

Let's don't cherry-pick!
No issue from our side.
This feature can just be available from the 2.0 version

Merged as 6b5c0878e440ff7a5f8a1b79afb754a42b51f226


etcdmain: let user provide a name w/o initial-cluster update

Currently this doesn't work if a user wants to try out a single machine
cluster but change the name for whatever reason. This is because the
name is always "default" and the
./bin/etcd -name 'baz'

This solves our problem on CoreOS where the default is ETCD_NAME=%m.

This is a cherry pick of https://github.com/coreos/etcd/pull/2534

the approach lgtm


Unable to list workspace or create connexion using self hosted airbyte python sdk

Does the Airbyte API Python SDK support self-hosted Airbyte setups on localhost (port 8000) using abctl?
I'm trying to list workspaces, set up new sources and create connexions using the python SDK and i'm not able to make it work.
here is the code i'm using to make it run:

@terencecho


Visualization

Hello! Thank you for publishing the code. I wonder how to visualization the graph as your paper.

This is visualized by chemdraw software.
On Thu, Jan 28, 2021 at 7:05 AM Ball<EMAIL_ADDRESS>wrote:

Hello! Thank you for publishing the code. I wonder how to visualization
the graph as your paper.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wengong-jin/iclr19-graph2graph/issues/7, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AATGYLCVZHACNZY3QB5DNFLS4FHKJANCNFSM4WW6FOEA
.

This is visualized by chemdraw software.
On Thu, Jan 28, 2021 at 7:05 AM Ball<EMAIL_ADDRESS>wrote:

Hello! Thank you for publishing the code. I wonder how to visualization
the graph as your paper.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wengong-jin/iclr19-graph2graph/issues/7, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AATGYLCVZHACNZY3QB5DNFLS4FHKJANCNFSM4WW6FOEA
.

Get, Thank u!

Get, Thank u!


Revert "[HUDI-2856] Bit cask disk map delete modified"

Reverts apache/hudi#4116
Reason: We encounter repetitive errors from BitCaskDiskMap during writes due to apache/hudi#4116.
14:23:40.363 [task-thread-hudi-sink-0] ERROR org.apache.hudi.common.util.collection.BitCaskDiskMap - BitCaskDisMap close error
java.nio.channels.ClosedChannelException: null
	at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:110) ~[?:1.8.0_265]
	at sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:379) ~[?:1.8.0_265]
	at org.apache.hudi.common.util.collection.BitCaskDiskMap.close(BitCaskDiskMap.java:270) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.hudi.common.util.collection.ExternalSpillableMap.close(ExternalSpillableMap.java:261) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.hudi.connect.writers.BufferedConnectWriter.flushRecords(BufferedConnectWriter.java:121) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.hudi.connect.writers.AbstractConnectWriter.close(AbstractConnectWriter.java:95) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.hudi.connect.transaction.ConnectTransactionParticipant.cleanupOngoingTransaction(ConnectTransactionParticipant.java:249) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.hudi.connect.transaction.ConnectTransactionParticipant.handleAckCommit(ConnectTransactionParticipant.java:209) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.hudi.connect.transaction.ConnectTransactionParticipant.processRecords(ConnectTransactionParticipant.java:127) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.hudi.connect.HoodieSinkTask.put(HoodieSinkTask.java:114) [hudi-kafka-connect-bundle-0.10.0-rc2.jar:0.10.0-rc2]
	at org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:581) [connect-runtime-3.0.0.jar:?]
	at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:329) [connect-runtime-3.0.0.jar:?]
	at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:232) [connect-runtime-3.0.0.jar:?]
	at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:201) [connect-runtime-3.0.0.jar:?]
	at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:186) [connect-runtime-3.0.0.jar:?]
	at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:241) [connect-runtime-3.0.0.jar:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_265]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_265]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_265]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_265]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_265]

Can we give some explanation why this exception throws with the #4116, the code logic does not change ? The only difference is that the new code may throw exception in the finally block ? Is that the reason for your error ?

And the line that throws exception ~line 270 should not be affected by #4116 right ?

Can we give some explanation why this exception throws with the #4116, the code logic does not change ? The only difference is that the new code may throw exception in the finally block ? Is that the reason for your error ?

After simply reverting #4116 the exception goes away.  Currently, I don't understand why the changes from #4116 introduce the exception. Therefore, we should revert it now and revisit the changes after the 0.10.0 release for safety and time-being.

@danny0405 : Can we go ahead and merge this in. Or do you have any clarifications.

@danny0405 : Can we go ahead and merge this in. Or do you have any clarifications.

We can, would merge it.

@xuzifu666 @danny0405  I filed a ticket for further investigation: HUDI-2944

I filed a ticket for further investigation: HUDI-2944. Feel free to take it on.

i review the change from 4116，the logic is not different. the exception need to be confirm by more times. @yihua


Roadmap to sass or ultility classes tailwind migrate in near future ?

Just question from my own! Not bug reports. I can't find any somewhere place for put my question

Just question from my own! Not bug reports. I can't find any somewhere place for put my question

Hi Dear mrtuvn
Please ask your question on community discussion section
thank you

No plans for sass.
We have a few classes to simplify content creation in the admin panel: https://github.com/breezefront/theme-frontend-breeze-blank/blob/master/web/css/base/_helpers.less. But we cannot add all of the classes to the sources because it will increase CSS size.


Unable to Enable RTL Mode in Streamlit-AgGrid Component

I encountered an issue when attempting to enable RTL mode in the Streamlit-AgGrid component.
The AgGrid component remains in LTR (Left-to-Right) mode even after specifying enableRTL: true in the grid options.
Thank you for your attention to this matter. Enabling RTL mode would greatly benefit users who require right-to-left direction support for their applications.

Could you please provide an example script for me to investigate?


Feature request: Scan multiple subnets

This might be out of scope for the project though since arp-scan is limited to the local network only.

I believe it your benefit some home users and small companies witch can check new devices added to the network and identify possible rogue equipment.

This is definitely the feature I'd need to be make this viable.
I currently use PiHole + Unifi console to fulfil this job on five subnets, so it'd be nice to have a GUI and have a dedicated tool for this job.

I'm thinking about replacing arp-scan with my own tool, but that needs time and some research

Instead of arp, would listening for dhcp be a potentially better solution?

I am able to scan multiple subnets by putting the container on multiple vlans/networks

AFAIK: ARP can only get neighboring nodes, so only for those subnet its part of, it can't go into a different network and query that table.
Maybe this could be implemented by changing the backend from arp-scan to nmap  (e.g. nmap -sn <IP_ADDRESS>/24
)?

I think my question fits in this topic. I am using docker-compose to start WYL. As interface I have put eth0 and it finds only devices in 172.x.x.x network which I think are the docker interfaces. What I need is to scan for all the subnets I have in my network: <IP_ADDRESS>/24, <IP_ADDRESS>/24 and <IP_ADDRESS>/24. Can this be done?

Is this gonna happen?

I haven't taken a look at the actual code but moving over to nmap should in theory not be too difficult and would allow scanning multiple subnets. I have made my own script that does this and notifies if it detects new devices. It's rudimentary but works well. https://github.com/broizter/openwrt-device-scanner/blob/main/device-scanner.sh

And it's possible to scan /16 network ?

+1

Done in v2. Here is how-to: https://github.com/aceberg/WatchYourLAN/blob/main/docs/VLAN_ARP_SCAN.md#3-arp_strs-for-vlans-docker0-and-other-complicated-scans


Correct activation unit order in cities

Let's say two units (unit1=active and unit2=fortified) are in a city and the unit1 is waiting for its order. If the fortified unit2 is activated, it gets immediately active, and unit1 is disregarded. This should be corrected, as in the original Civ1 in this case unit1 is still first active, and only then is unit2 activated.

This issue has been fixed: 47b36621453744ede2fae1a219ec00f16e00dc46


fixing multiomics wellness kp api x-bte annotation

changing query method to POST, templating so that BTE can batch-query
fixing reverse operations (not specified quite correctly)

Should make BTE faster at answering queries...
Also message Arpita in Multiomics team over her list of operations =/= this review's...

would also want to use this (no PR yet): https://github.com/biothings/bte_trapi_query_graph_handler/tree/wellness_batch_query


Update and Enhance ChoiceListUtilsTest

Description
This pull request enhances the ChoiceListUtilsTest class  by adding the testcase of update for ChoiceUtil.
Changes Made

Added test cases for updating   choice lists.

Test Cases Added

testUpdateChoiceList: Updates an existing choice list.

This PR  solve this  issuse
Screenshots  to demonstrate the test is passed

@NiranjanNlc I switched the branches to development because we generally put new code in development for testing before going to master branch. Can you resolve the conflicts? The README file has updates in master branch as part of people's work on documentation that has not been moved into development yet. This is a good opportunity to learn about Git merging.

Thanks @wbrunette , i am able to resolve the commit .


Update badges and docs link

Fixes the documentation, repository, and Travis badge links under Cargo.toml and README.
Also adds crates.io and licensing badges.

Good catch on the changed links for the badges, I didn't even think of that

Thanks :beers:


Duplex interaction in a stream

I think it is somewhat implicit that on a stream either the requester or the responder can send DATA,  REQUEST_N, CANCEL and other frames for a true full duplex interaction per stream but is not obvious, specially for someone coming from a ReactiveStreams/ RxJava background as the streams there are unidirectional i.e. only the producer sends onNext, onComplete, onError and the subscriber sends requestN.
I think it will help to clarify typical interactions in various request types. Also, this can be a good place to define what is illegal in any interaction.

I think the sections covering sequences spell this out clearly. What is missing there?
In terms of legal/illegal, we still need to spell out what is the reaction to unexpected frames. Ignore? Close Stream? send RST equivalent? close connection?

This was my incorrect assumption that data can flow either ways in a stream. In offline discussions, it was clarified that wasn't the case. For the usecases where data should flow in either directions, there should be two streams initiated between the peers.


Possible security Issue - Watchbog

Hi everyone,
I am using bottle for my python application (with the integrated server). The bottle app is deployed on a docker linux container.
My machine was recently infected by the following malware : watchbog (cryptomining software).
According on some information I found on the internet (like here : https://ubuntuforums.org/showthread.php?t=2410137), the software probably entered via a security vulnerability in SolR (apache : http://lucene.apache.org/solr/).
Since I'm not using this software or any other apache one, I was wondering if a vulnerability might have slipped through Bottle's side? Is that possible? Does bottle use an apache module for example (I don't think so though) ?
My current load balancer is an HAProxy, and I am using bjoern as a WSGI Server.
Python version: 2.7.6
Bottle version: 0.12.16
Linux ubuntu: 16.04.6 LTS
Thanks in advance for your opinions.
Sacha

The only way I can think of, is when you are using signed cookies (with a secret) and the secret was leaked. Then an attacker could inject malformed pickle data, which leads to remote code execution. (This is documented and not an issue if you are not using signed cookies with the pickle serializer). Otherwise, there is not much of an attack surface within bottle itself. The application could be vulnerable, of cause.

Thank you for your suggestion, but I do not use any cookies on my app. But I will keep looking into it !
I also post this issue, in case someone else find this malware when using a python/bottle app.

As I said, within bottle itself there is little to no attack surface. Bottle does not write any files, and does not execute any remote code (with the signed-cookie/pickle exception). Its is much more likely that either the application running on bottle, or the docker image itself were compromised.


Add ChallengeProviderTimeout type to acme package

There was what I perceived as a problem with my Gandi ChallengeProvider in #133. Because of Gandi's long DNS record propagation time (in my tests, up to 25 minutes), I had to alter the timeout the acme package used when checking for record propagation. However, this affected all the DNS providers, the remainder of which just require the existing 30 second timeout. Forcing them all to have a 40 minute timeout for the sake of Gandi seemed... wrong?
This PR adds a new ChallengeProviderTimeout type to the acme package which allows for implementing DNS providers that require an unsually long timeout when checking for record propagation. In fact, although it would only be necessary for DNS providers like Gandi at present, it need not be solely for DNS providers. There could be in the future some yet not-invented challenge type, for which the same problem occured.
The Gandi provider in #133 has been altered to use this new interface, so all the remaining DNS providers will now use the 30 second timeout again as normal.
Thoughts?

Out of curiosity, is there any reason this couldn't have been made a command-line option (like --dns-timeout)? Making the timeout configurable on the command line would be a more general-purpose solution. That way if one of the existing providers happens to be propagating more slowly than configured in the code, the user can address the issue without having to modify the code.

A command line flag could be useful. It depends how many people (other than me and you) are having problems I suppose. If this gets accepted, I'd be happy to add a separate PR for one (I've just seen #149).
However a command line flag alone does not solve the use case of using the library without the CLI. Also, the way this PR works, the knowledge of what a good value for the timeout is is put into the provider itself (by it implementing the Timeout method). And each provider probably knows best what it's own timeout should be.

An alternative way would be to return an extra value via the Present method, altering its signature. But that forces all providers to think about a timeout, when it may not be relevant for them (eg http-01) or they just need the default value (most of the DNS providers).

Wouldn't it make more sense to just push the timeout into the provider entirely and providing a default via a const?

Hi xenolf. Forgive me, but I'm not 100% certain I understand your idea, so I'll state what I think you mean.
At the moment the value of the timeout is needed by the waitFor in dnsChallenge.Solve, which with this PR it finds by calling the provider's Timeout method.
When you say push the timeout into the provider, do you mean that the Present method of each provider must call waitFor itself? i.e. each provider's Present must contain the following
    waitFor(timeout, 30, func() (bool, error) {
        return preCheckDNS(fqdn, value)
    })

where a default timeout value can be found from a constant?
If you meant something else, I apologise, but could you elaborate? If you did mean that then of course that would work, but I passed on this strategy initially since it meant modifying the providers. However, if you think that's better then no problems. We can do that :) In some ways I do think it is better not to introduce extra exported API if we can help it.

Do we still need this to deal with higher than average propagation latencies for specific providers now that acme.WaitFor is exported? The Gandi providers can just invoke the wait routine within its DNSProvider.Present() implementation, right?

Hi @janeczku. I am happy to abandon this PR and just call acme.WaitFor from Present as you suggest. However in order to do so, as you can see from the code snippit above, I'll need preCheckDNS to be exported (or checkDNSPropagation), since I don't want to duplicate all that DNS code in the provider. Presently in #144, only WaitFor is exported which isn't quite enough. If we export preCheckDNS (and probably it's type preCheckDNSFunc too) I'm good as far as I can see. Is this the way forward @xenolf?

However in order to do so, as you can see from the code snippit above, I'll need preCheckDNS to be exported

Right... totally missed that!

I'm not sure if we should push the functionality of calling preCheckDNS down into the providers... I'd rather leave that in the library code to ensure it get's called.
I like the idea more of just giving the providers the ability to customize the timer.

@xenolf, so will this patch suffice then (once it's fixed for #144)? Or is there a better way?
Hi @janeczku. I'm not sure I understand your point about the 30 second interval. Bear in mind that you get the default 2 second interval/30 second timout unless you specify the optional Timeout() method to signal an extended timeout. Only then do you get the 30 second interval. Given that people are going to be specifying timeouts in the range of around 2 minutes -> 1 hour, I thought that 30 seconds was reasonable. Would would you suggest as a better value?

Given that the semantics of WaitFor have changed in #144, I have just rebased this PR to sit on top of #144.

I'm not sure I understand your point about the 30 second interval. Bear in mind that you get the default 2 second interval/30 second timout unless you specify the optional Timeout() method to signal an extended timeout. Only then do you get the 30 second interval.

This exactly.

Given that people are going to be specifying timeouts in the range of around 2 minutes -> 1 hour, I thought that 30 seconds was reasonable. What would you suggest as a better value?

1 hour? Good lord, i must have overlooked the PR for the mail order DNS provider... :laughing:
But seriously now: A 30 seconds interval will slow down things for those providers that are in the more typical range of propagation delay between maybe 2 to 120 seconds. For example, Digital Ocean usually propagates within 2-3 seconds but can spike up to 60-80 seconds. Hence i would specify the ChallengeProviderTimeout for DO as 90 seconds.
With the proposed 30 seconds interval a DO certificate requests that would now complete in maybe ~6 seconds with the default 2 seconds interval would suddenly take ~6+30 seconds.
Now, seeing that we are adding an additional interface anyway, we might as well make it so:
type ChallengeProviderTimeout interface {
	ChallengeProvider
	Timeout() time.Duration
	Interval() time.Duration
}

Otherwise i strongly suggest to set the interval to not higher than 5 seconds.
What do you think?

@janeczku, the way this PR was intended to be used, I was not expecting any of the existing providers currently in master to specify Timeout (just as they don't at present). It is purely for the Gandi, Namecheap and other future providers who are, as you say, "mail order DNS" ;) Of course a 30 second interval will slow down Cloudflare. Hence Cloudflare should not (just as now) specify Timeout method, and so gets the fast timeout=60/interval=2. That is the default case in the type switch.
30 seconds is appropriate, however, for when interval is in the range 60 seconds -> 1 hour though? No?
 If so, why? I thought it worked just fine with the current default of timeout=60/interval=2?
If cloudflare or other can spike to 80 seconds, I suggest the default timeout is changed to 80 seconds. This PR was only intended for the real slow coaches. I don't think I made myself too clear about it's intended use though, for which I apologise. I'm learning this github stuff ;)

If you think that all providers should specify Timeout then we can just do away with ChallengeProviderTimeout altogether and move Timeout into ChallengeProvider. But then you have the case that HTTP and TLS ChallengeProviders have to define Timeout methods when timeout has not real meaning for them since everything is done by lego.

If cloudflare or other can spike to 80 seconds, I suggest the default timeout is changed to 80 seconds.

What if another provider needs 90 seconds? There is no one sane default wait time that fits all.
That's why any implementation of a custom timeout should not be tuned to fit a specific provider (like those that propagate within 2 mins to 1 hour per your example). It should be general enough to be usable by any provider that may need to make use of it.
If thats not the case than it does not belong in the main library, but in the provider package.

Ok. I understand your point I think. You object to a hard line where interval suddenly changes from 2 seconds to 30 seconds, since there will always be some value for timeout you could choose (e.g. 90 seconds when the default is 80) where interval will then be inappropriate. I've understood you right, I accept that as a valid criticism.
In that case how about this?  We change WaitFor to do away with the interval parameter altogether so its signature is then just this:
WaitFor(timeout time.Duration, f func() (bool, error)) error

Internally we then make it set interval itself based on timeout. How about something like
interval := timeout / 60

where timeout has a minimum value of 60 seconds. What do you think?

If that's too simplistic, we could make WaitFor do exponential backoff, but the simple solution above would address your points?

I felt like doing a bit of math, so here's a more complicated idea for automatic setting of interval based on timeout. Set successive values of interval in WaitFor based on the terms of the geometric series 2, 2r 2r^2, 2r^3, ..... for a value of r=1.016111. Why this value? It was so that after 1 hour the interval is approximately 60 seconds. You then have the following nice properties:

Total time (seconds)
check #
interval (seconds)

0
1
2

60.97
26
2.98

300.85
78
6.85

3611.57
214
60.19

So you can see that for a 60 second timeout, interval stays below 3 seconds, for 5 minutes it's under 7 seconds,  but for a timeout of 1 hour it raises to 60 seconds, but requires only 214 checks, which I don't think is unreasonable for 1 hour.
Anyone like this idea?

I have implemented the geometric progression idea to have a look at. I can always discard it if people don't like it. It's an additional commit on this PR.
To verify it actually does what I say it does, run the following program which measures the elapsed time and interval time. It will print the lines of the table above (including the missing lines :) )
func main() {
    initialTime := time.Now()
    lastTime := initialTime
    lastSince := time.Since(initialTime)
    n := 1
    acme.WaitFor(3700*time.Second, 2*time.Second, func() (bool, error) {
        if n-1 > 0 {
            fmt.Println(lastSince.Seconds(), n-1, time.Now().Sub(lastTime))
        }
        lastTime = time.Now()
        lastSince = time.Since(initialTime)
        n++
        return false, nil
    })
}

@xi2 I am all in changing the wait function to using an incremental sleep based on retry count.
I would re-evaluate the way you implement this though. You don't need the math package to get an exponential increment. Hint: sleep := 2000 + (10 << uint(retryCount))
But better yet, just use a plain simple linear function from 1 to 30 seconds.

@janeczku. Great that you agree in principle to changing waitFor in this way.
I have modified the commit so that no sum of the progression is made,  and there is no use of the math package any more. Just a simple
interval *= ratio

each loop interation. So the numbers in the table above remain the same (assuming negligable time in the poll function).
If however we were to use a linear increment each time as you suggest, I don't think the numbers work quite as nicely for lower timeout values? e.g. if we used sleep := 2 + d*retryCount and we choose a value of d so that after one hour the sleep is 60 seconds (say d=0.495453) we would get the following

Total time (seconds)
check #
next interval (seconds)

0
1
2

64.65
14
8.44

309.74
33
17.85

3656.11
119
60.54

So the the interval goes up too quickly for lower timeout users? What do you think? Are things better now there is no use of math package?

@xi2 Here is an example of calculating exponential delay using bitwise shift operator.
This will result in small interval times within the first 30 seconds and a maximum interval of 35 seconds after one minute.
http://play.golang.org/p/EYHKgi0F7i

@janeczku. Thank you for your example on play.golang.org. I ran the program and observed what it did. While I agree fully with your previous point about removing unnecessary use of the math package, which I did of course, I don't see the benefit of increasing the interval via a bit shift operator vs using the existing approach of a float multiply. The code is not performance sensitive, and I think the multiply code is slightly more readable.
However, I really want this PR to get to whatever state @xenolf wants it to be in, so it can be merged. If @xenolf wants to use the exact algorithm from http://play.golang.org/p/EYHKgi0F7i I will change it to that without delay. If he wants something else, I will change it to that also. Basically, whatever he wants I will do! :) Thanks again for your many good suggestions @janeczku.
What shall it be @xenolf?

I really do not have a strong opinion on this. I think it's fine as is but I'd introduce a maximum interval so it doesn't grow indefinitely.

Maximum interval set max(initialInterval,60*time.Second). This caps the increasing interval at 60 seconds, but allows for intentionally setting a large interval such as 5 minutes.

It would seem to me that the ChallengeProviderTimeout definition really belongs in provider.go, alongside that of ChallengeProvider, so I have moved it there.

I like the addition of exponential backoff in the WaitFor function, but it feels like the growth rate is too slow.  With namecheap, where it can take as long as 30 minutes for a change to propagate, the lego client ends up spamming DNS requests every 3 to 5 seconds for the first 5 minutes or so.  A simple doubling algorithm, as follows, would be sufficient:
func WaitFor(timeout, interval time.Duration, f func() (bool, error)) error {
	var lastErr string
	maxInterval := 60 * time.Second
	timeup := time.After(timeout)

	for {
		select {
		case <-timeup:
			return fmt.Errorf("Time limit exceeded. Last error: %s", lastErr)
		default:
		}

		stop, err := f()
		if stop {
			return nil
		}
		if err != nil {
			lastErr = err.Error()
		}

		if interval > maxInterval {
			interval = maxInterval
		}

		time.Sleep(interval * time.Second)
		interval = interval * 2
	}
}

For DNS providers that provide rapid responses, the algorithm will easily get you a response within 30 seconds (and 4 DNS requests).  Whereas with a slow provider, you'll quickly be requesting once per minute, which is where you'd want to be anyway.

Thanks for your feedback, @beevik. I notice that the code you have posted is more or less exactly what is in the PR, but with a higher multiplier each loop iteration. So it seems that the only issue is the correct and appropriate multiplier to use.
With a multiplier of 2.0 as you suggest, the interval does raise very quickly. By my reckoning it hits 30 seconds after total waiting time of just 30 seconds. And this being too long was @janeczku's original complaint that motivated changing WaitFor in the first place.
Since @janeczku also had a higher multiplier in his suggested code, and you have suggested the current multiplier is spamming, I have raised it. It now hits 60 seconds after 20 minutes (instead of 60 minutes) and stays there. I hope that is a more appropriate value and you no longer feel it is spamming. The revised numbers are:

Total time (seconds)
Poll#
Next interval (seconds)

0
1
2

64.75
21
5.11

301.93
46
16.49

1235.25
74
60.00

>1200
>74
60.00

Ultimately though I think there is going to be no value that pleases everyone. This has proved far more contentious than I had envisaged! So it may be down to @xenolf to make an executive decision. I personally do not care at all what the multiplier is (as long is it isn't spamming), since Gandi take 20 minutes anyway. And I have it automated and running in what amounts to a cron job, so I'm never actually waiting for it either. I just don't want it to timeout! :)

The only solution which would maybe cater to "everyone" is probably to allow customisation of the initial interval. This way we can adjust the interval to a high number for providers we know take longer to propagate.

Right you are @xenolf . This was actually @janeczku's suggestion way back in this thread:
type ChallengeProviderTimeout interface {
    ChallengeProvider
    Timeout() time.Duration
    Interval() time.Duration
}

which I didn't action at the time, but maybe is the best idea (sorry @janeczku!). Before I change things again, is there any need for interval growth at all if were are all specifying the interval in the provider? e.g. I could just specify Gandi as timeout=40*time.Minute/interval=60*time.Second and be done with it. Interval growth would seem an unnecesary complication?

I have gone ahead and implemented this. While I was at it I have squashed the commits, since they had gone round in circles trying things, and arrived almost back at the beginning.
As I said, I have removed the interval growth, since it now seems unnecessary, but if I have overlooked a reason to keep it then please say and it can come back from the dead :)

Looking good in my opinion. Maybe we could mention the default values for the timeout / interval on the type to get it into godoc.

Thanks @xenolf! I've made the comment changes you suggest. Please read over the comments again.

I meant "package acme", but you are right that it is confusing the way it is written. I have now used your exact suggested wording. Thanks.


Using Vagrant behind corporate proxy

using the module vagrant-proxyconf it is possible to configure the proxy during the machine start. As a bonus, the fix for bug 589 :)

See docs: http://docs.drupalvm.com/en/latest/extending/vagrantfile/#example-using-drupal-vm-behind-a-corporate-proxy-with-vagrant-proxyconf
I'd rather not add the proxy stuff to the global default config, because it's a very small percentage of users who have to deal with all of it.


Add disable hotkey to anti-drag plugin.

This pull request adds the control key as a hotkey to disable the anti-dragging functionality when the onShiftOnly setting is disabled which makes re-organizing the inventory while the plugin is enabled less cumbersome with a long delay.

Upon re-reviewing this, as written, this does not work properly when holding Ctrl and opening the bank. Also it sets held when pressing and releasing Ctrl which isn't correct. I've authored https://github.com/Nightfirecat/runelite/commit/3a9cec27de818623a096486762d870a3e202f04a which splits Ctrl holds into a separate field and references that when opening the bank. @Unholypanda Can you confirm that this linked commit works as you would expect?

Tested your version and it seems to work properly in the bank. Sorry if I didn't do the testing process properly I'm kinda new to using Git collaboratively. I just copied your changes into my repository, tested, and pushed the updated code.

Added in cc2ed2311bec808193fbae382cadf4a973f64b20


Add NSX-T Receiver to contrib

Receiver:
https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/nsxtreceiver
Resolves: #215
Resolves: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/14788

Hi, thanks to all for your support!
If I understand well I'll find nsxt receiver in v0.62.0 in few days?

@msartor92, that's correct. The release is scheduled for today, should be available later in the day.


Add support for D3D tearing and waitable swapchains

[x] https://github.com/mellinoe/veldrid/pull/484
[x] https://github.com/mellinoe/veldrid/pull/485
[x] New veldrid release

Input lag testing (PresentMon/CapFrameX):

Mode
Input lag [Bound]

Before
~70ms

New (no flags, never the case)
29.3ms [24.5ms ~ 34.0ms]

AllowTearing (fullscreen)
2ms [0.8ms - 3.0ms]

WaitForNextFrameReady() (windowed/borderless)
12ms [5.4ms - 19.3ms]

Historically, tearing has only been a thing in fullscreen mode and so I've kept it that way for now, however do note that it can also be applied in borderless ("exclusive fullscreen" does not exist in D3D).

When I spam alt-enter to toggle the display mode really fast, every now and again I can enter a wrong state such as this:

Not really sure what's going on there.

Ah, I thought that was just my VM acting up. Will investigate.

Will be fixed by https://github.com/ppy/veldrid/commit/068700a0a645f4af3ce37ba8d2ea95c7aaeb884d

Wrong sizing issue is fixed for me with the latest changes 👍
I've also done some one-shot testing on my setup with capframex and while I'm not sure how to interpret the results exactly, it seems better?

current master
this PR

primary monitor (165Hz)

secondary monitor (60Hz)


add end/terminate/finish operator

for usecases where you need to do
.do(update$ => {
  this._router.go('/somewhere');
})
.fitler(() => false)

or similar
so you could do
.end(() => this._router.go('/somewhere'));

instead

At least as a workaround, one could also have a closing action to dispatch:
.do(update$ => {
  this._router.go('/somewhere');
})
.map(_ => MyActions.navigateSomewhereSucceeded());

https://gitter.im/ngrx/effects?at=578906018423d0842436fb49

@Effect({ dispatch: false })


CB-18243. Monitoring UMS credential should be created if monitoring r…

…elated settings are set (not databus one).
See detailed description in the commit message.

could you add unit test? I see there are some already in place, but this doesn't seems to be covered well

actually that was discovered by a Unit test, there is a large refactor that's happening right now, but as this issue could cause deploy failure or silent errors on VMs i created a PR for this - as the refactor review could consume a bit more time (at least im expecting this)
the UT on that branch for this: https://github.com/hortonworks/cloudbreak/commit/f42a5e97a48b8b35325f2ac05e34cdaa0e1c3122#diff-2508f81be668d7d2fca4c4306d15b7846e093168e6b92e780f9d685d8e334f85R123


CELTS Manage Service Learning Faculty

See CELTS Admin Wireframe: https://balsamiq-wireframes.appspot.com/?state={"action":"open","ids":["1etrefTLsvWQntesh5_TDdC66TRVzRpHf"],"userId":"109665407847548855125"}
The slide titled "1. Admin Email Past Prof" is what we want this page to look like.
This is the page where admins will add and remove faculty who will receive information about service learning courses and who will be able to create service learning courses.

 CELTS #127: CELTS Manage Service Learning Faculty


If experiment_data.save() fails it should raise an exception

https://github.com/Qiskit/qiskit-experiments/blob/049436a3d184adb51bb559316483cd44f1e2c925/qiskit_experiments/framework/experiment_data.py#L1339
Here; if you hit this condition the experiment data is not saved, but the function returns as if it had saved.  In the context of, for example launching a bunch of experiments from a loop, this could cause a user to lose a lot of data.  (or am I missing something here?)

I agree; no reason not to raise an error here if we already have the (new) suppress_errors flag.

I put in a fix for this in #1278. Note that if you were calling save(), which is what most users do, it already raises an error when there's no service: https://github.com/Qiskit-Extensions/qiskit-experiments/blob/f33bed7e143b68bd53243c061c603bb5216c9e54/qiskit_experiments/framework/experiment_data.py#L1696-L1705
So the new fix is only for the case when someone calls save_metadata() separately to save only the metadata.


Jstorm runner working in progress

For sharing with @kennknowles for discussion.
merge commit c1e8156 contains many code from bastiliu.

And, nice work getting all of this done! Thanks @bastiliu also!

We have addressed most of the comments in https://github.com/apache/beam/pull/3624/files
I am closing this one.


[BUG] No NgModule metadata found for 'BrowserAppModule'

Hi,
I'm having a problem on my application that when I try to build universal:aot, I get the following error message on browser console:
No NgModule metadata found for 'BrowserAppModule'.
and the application won't run properly.

@JoaoPauloCMarra were you able to fix this? I'm also having a similar issue.

@bhardwajvarun I have fixed this problem, check this https://github.com/nhutcorp/angular-webpack2-starter

I  can confirm bug:
master
$ git checkout master
$ npm install
$ npm run prodserver

Then : No NgModule metadata found for 'BrowserAppModule'
no-universal-support
$ git checkout no-universal-support
$ sed -i 's|dist/client|dist|' prodserver.js webpack.config.ts
$ npm install
$ npm run prodserver

Then : No NgModule metadata found for 'BrowserAppModule'
minimal branch
$ git checkout minimal
$ sed -i 's|dist/client|dist|' prodserver.js webpack.config.ts
$ npm install
$ npm run prodserver

Then : No NgModule metadata found for 'BrowserAppModule'
Full Stack
zone.js:195 Uncaught Error: No NgModule metadata found for 'BrowserAppModule'.
    at NgModuleResolver.resolve (compiler.es5.js:14063)
    at CompileMetadataResolver.getNgModuleMetadata (compiler.es5.js:14647)
    at JitCompiler._loadModules (compiler.es5.js:25814)
    at JitCompiler._compileModuleAndComponents (compiler.es5.js:25773)
    at JitCompiler.compileModuleAsync (compiler.es5.js:25735)
    at PlatformRef_._bootstrapModuleWithZone (core.es5.js:5016)
    at PlatformRef_.bootstrapModule (core.es5.js:5002)
    at HTMLDocument.main (main.browser.ts:25)
    at ZoneDelegate.invokeTask (zone.js:424)
    at Zone.runTask (zone.js:191)

I tried @nhutcorp patch without success:
diff --git a/package.json b/package.json
index 4fb5d86..3566c8b 100644
--- a/package.json
+++ b/package.json
@@ -75,7 +75,7 @@
     "zone.js": "~0.8.9"
   },
   "devDependencies": {
-    "@ngtools/webpack": "^1.3.1",
+    "@ngtools/webpack": "1.4.1",
     "@types/express": "~4.0.35",
     "@types/ip": "~0.0.29",
     "@types/jasmine": "2.5.43",

@sbechet let's try this https://github.com/nhutcorp/angular-webpack2-starter/commit/d92ffaf03c844e9ecfa8dfc8528b50138a4cc81c
I have update @ngtools/webpack to latest and re-added some old files for fix the "No NgModule metadata found ..." problem.

Hello nhutcorp, thank you very much, AOT is working perfectly now!


Data and benchmarking for the new object detection models

TODO:

[x] upload data to gdrive and baidu pan
[x] add link in download_data.py
[x] add samples in the front readme
[x] add notes in each model's readme on where the original sample images can be fetched
[x] benchmark configs for nanodet and yolox
[x] update benchmark data for nanodet and yolox

👍


[ADP-3350] Conversion to/from Read.ChainPoint

This pull request adds conversion function to/from the data type ChainPoint that belongs to the Cardano.Wallet.Read hierarchy.
This includes

Conversions to/from legacy types in primitive
Conversions to/from types in ouroboros-consensus for the networking layer

Comments

The goal is to eventually remove the old primitive types. However, we add conversions Read.ChainPoint ⟷ ChainPoint here in order to have more control over the source code impact of future pull requests. Specifically, we can then change the types in NetworkLayer from ChainPoint to Read.ChainPoint while touching only a small portion of the code in Cardano.Wallet thanks to a cleverly inserted conversion.

Issue Number
ADP-3350

Thanks for the review! 🙏

Some food for thought ... Should we at some point in future think about adding roundtrips checking

Ah. Fair enough. This particular code be "obviously correct", and the type checker imposes strong constraints on what it can do, but there is always undefined or typos. Testing the roundtrip ouroboros-consensus ⟷ ChainPoint may be a sensible idea, whereas I would skip it for the Read.ChainPoint ⟷ ChainPoint as it involves a legacy type.


proposed changes to auth docs update

Proposed changes against https://github.com/netlify/netlify-cms/pull/751.

Merging to continue edits & discussion in #751


Create assert_lt instruction

We need to create an assert_lt and assert_lt.<imm> instructions to be able to conveniently check the validity of the stack top element. It will be used primarily for checked shift and rotate instructions emulation.

Closing this for the reason described in #1157.


add kubernetes yaml files

Here is a working setup with yaml files ready to be applied with
kubectl apply -f .

@nicholasklem thanks for this PR. I will take a look soon.


Doc: Remove Duplicate Instruction for All Permission Policy Module Removal

Hey, I just made a Pull Request!
In PR #26727, I missed point 1 and added documentation for the removal of the permission policy module in point 6. Since the instruction is already covered in point 1, this PR is to remove the duplicate instruction.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@jhaals @vinzscam FY!


[SPARK-13663] [CORE] Upgrade Snappy Java to <IP_ADDRESS>

What changes were proposed in this pull request?
Update snappy to <IP_ADDRESS> to pull in a single fix -- the OOM fix we already worked around.
Supersedes https://github.com/apache/spark/pull/11524
How was this patch tested?
Jenkins tests.

Test build #52826 has started for PR 11631 at commit 5c05f1a.

Test build #52826 has finished for PR 11631 at commit 5c05f1a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52826/
Test PASSed.

Merged build finished. Test PASSed.


Enhancement: Merge Rust imports using rustfmt

Use imports_granularity = "Crate" in rustfmt to merge Rust imports (for cleaner imports).
What this does?

Example

We should create a rustfmt.toml file for this. I would like to see comments wrapped to 80 chars


Address Label

Hello, how can I extract who these addresses belong to from the XML file. Is it possible to extract the tags for these addresses?

how can I extract who these addresses belong to from the XML file

I'm not familiar with the exact layout of the XML file. You probably have to take a look for yourself.

Is it possible to extract the tags for these addresses?

Sure. But I do not know what tags you mean.

I want to know which cryptocurrency addresses belong to whom.
Thank you.


I have a few loaders that I want added to the list

po-loader
nunjucks-loader

nunjucks-loader needs a lot of work.

If you think they are ready for the public, feel free to add them to the list... (Edit button top right)

@sokra I can see where I added it to the source almost four months ago but its not showing up on the live page.


Problem getting Requiem

I'll tell you right away this is not a bug or a mistake, i am interested in how to get a requiem for a gold exeperience

Get 1 mil exp points, then use a Stand arrow.


Where is the source code for typescriptServices.js?

I wanted to get the source code for monaco-editor/dev/vs/language/typescript/lib/typescriptServices.js, but I didn't find it,where can I find it?
Thank you!

guess it's in TypeScript repo


Implemented a more reliable means to tint the Toolbar Overflow button

Previously, the overflow icon was found by searching the toolbars for views matching the overflow’s content description.
This proved unreliable.. Hard to know exactly why, but in some cases findViewsWithText() was failing to find the overflow image view, so it didn’t get themed correctly.
This change just retrieves the overflow icon via toolbar.getOverflowIcon(), tints it, then sets it again via toolbar.setOverflowIcon().

It looks like your commit before I merged master failed on Travis, it's most likely due to code formatting

No probs, I'll check it out.

If my interpretation of the Travis logs is correct:

/home/travis/build/afollestad/aesthetic/sample/src/main/java/com/afollestad/aestheticsample/MainActivity.java uses or overrides a deprecated API.

The issue appears to be the MenuItemCompat.getActionView() call in MainActivity#42 (getActionView() is deprecated).

This appears fixed in my pull request


[FX-4608] Migrate Badge to TailwindCSS

FX-4608
Description
Migrate Badge to TailwindCSS.
How to test

Temploy
FIXME: Add the steps describing how to verify your changes

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests (visual tests included)

Breaking change

[x] ~codemod is created and showcased in the changeset~
[x] ~test alpha package of Picasso in StaffPortal~

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers


Improve config management

Follow up of https://github.com/giantswarm/grafana-multi-tenant-proxy/pull/149

I guess this PR should be a draft until new MTP is released?

It should but you cannot switch from non draft to draft :(

Oh you can but it's hidden :D


cleaned up code

I propose few minor code cleanups to the specter module.
All other changes are the diff between stepansnigirev/HWI:specter and bitcoincore/HWI:master, better to be received independently before merging this PR
Last, but not least, bitcoincore/HWI:master has changed the HardwareWalletClient.display_address signature, so probably the implementation of that method should change accordingly in the specter module

Thanks!


[bug] Continuous writes on a disk drive

Checklist:

[x] I am not using Home Assistant. Or: a developer has told me to come here.
[x] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog and my problem is not mentioned there.

Build/Run method

[x] Docker
[ ] PKG
[ ] Snap package
[ ] Manually built (git clone - yarn install - yarn run build )

Zwavejs2Mqtt version:  5.8.0
Z-Wave JS version: 8.4.1
Describe the bug
I'm migrating my HA docker volumes to NFS share.
I realized that after starting of zwavejs2mqtt container, there is a regular disk activity on my Synology NAS -> every 1s.
What can be observed is that there are 2 files in /store folder:

*.metadata.jsonl.lock
*.values.jsonl.lock

There are always up-to-date, maybe the system continuously touches them. (sorry for missing knowledge about how it really works).
There is no activity on Zwave network as there is only a zwave controller and one smoke detector which is in sleep mode.
To Reproduce
Steps to reproduce the behavior:

Run zwavejs2mqtt docker image
Observe disk activity

Additional context
I disabled all possible logging and "issue" is still there.
Making also further thoughts how this may influence also SD card lifetime, considering that a lot of HASS users may run it on RPIs.
Used HW is RPi-4 2Gb, having boot and rootfs on NFS share.

With the next release, you can change the directory in which the lockfiles are created, see https://github.com/zwave-js/node-zwave-js/pull/3526
If that points to a RAM FS, it should work


The reverse tunnel does not return the connection object

I am trying to capture the ready event from the connection but the function tunnel.reverse() always return undefined.
var conn = tunnel.reverse({
  host: host,
  username: 'root',
  dstHost: '<IP_ADDRESS>', // bind to all interfaces (see hint in the readme)
  dstPort: dstPort,
  //localHost: '<IP_ADDRESS>', // default
  //localPort: localPort
}, function(error, clientConnection) {
  console.log(clientConnection._forwarding);
});

//This fails since conn is undefined
conn.on('ready', function(){
});

Thanks again. Please use the new https://github.com/agebrock/reverse-tunnel-ssh


Backblaze B2 Big File Copy stuck at 100%

I am using rclone 1.30 64bit on Linux Ubuntu 16.04.
I was migrating files from Amazon Cloud drive to Backblaze B2. It works fine with small files (e.g. 1GB), but when I was copying large files (e.g. 8GB ISO files) it would copy them, but never finish them. In the stats it will just show "100% done" and do nothing. It will even crash eventually.
The command I used was
./rclone copy acd:/ISO backblaze:FastnetBackup/ISO --transfers=8 --stats=3s
then eventually it would just show
Linux/CentOS-7-x86_64-Everything-1503-01.iso: 100% done. avg: 6456.3, cur: 0.0 kByte/s.
However, instead of moving on to other transfers, it is stuck. This is a problem because all the other large ISOs get stuck as well.

Can you send me a log with -v of it happening please?
What do you mean by "It will even crash eventually" - was there an error message?
Can you copy one of those files from acd to local disk? And then from local disk to b2? Just trying to work out where the problem is!
Thanks
Nick

`root@ubuntu-512mb-sfo1-01:~/rclone-v1.30-linux-amd64# ./rclone copy acd:/ISO/Linux backblaze:FastnetBackup/ISO/Linux --transfers=8 --stats=10s -v
2016/06/30 12:26:16 rclone: Version "v1.30" starting with parameters ["./rclone" "copy" "acd:/ISO/Linux" "backblaze:FastnetBackup/ISO/Linux" "--transfers=8" "--stats=10s" "-v"]
2016/06/30 12:26:18 Linux: Failed to read metadata: object "Linux" not found
2016/06/30 12:26:18 Amazon cloud drive root 'ISO/Linux': Modify window not supported
2016/06/30 12:26:18 Amazon cloud drive root 'ISO/Linux': Building file list
2016/06/30 12:26:18 B2 bucket FastnetBackup path ISO/Linux/: Building file list
2016/06/30 12:26:18 Amazon cloud drive root 'ISO/Linux': Reading ""
2016/06/30 12:26:18 B2 bucket FastnetBackup path ISO/Linux/: Done building file list
2016/06/30 12:26:18 Amazon cloud drive root 'ISO/Linux': Finished reading ""
2016/06/30 12:26:18 Amazon cloud drive root 'ISO/Linux': Done building file list
2016/06/30 12:26:18 B2 bucket FastnetBackup path ISO/Linux/: Waiting for checks to finish
2016/06/30 12:26:18 Fedora-Live-Workstation-x86_64-23-10.iso: Sizes identical
2016/06/30 12:26:18 Fedora-Server-netinst-x86_64-23.iso: Sizes identical
2016/06/30 12:26:18 Fedora-Server-netinst-x86_64-23.iso: Unchanged skipping
2016/06/30 12:26:18 Fedora-Live-Workstation-x86_64-23-10.iso: Unchanged skipping
2016/06/30 12:26:18 ubuntu-16.04-server-amd64.iso: Sizes identical
2016/06/30 12:26:18 ubuntu-16.04-server-amd64.iso: Unchanged skipping
2016/06/30 12:26:18 CentOS-7-x86_64-LiveGNOME.iso: Sizes identical
2016/06/30 12:26:18 CentOS-7-x86_64-LiveGNOME.iso: Unchanged skipping
2016/06/30 12:26:18 ubuntu-16.04-desktop-amd64.iso: Sizes identical
2016/06/30 12:26:18 ubuntu-16.04-desktop-amd64.iso: Unchanged skipping
2016/06/30 12:26:18 F23-x86_64-CINN-20160512.iso: Sizes identical
2016/06/30 12:26:18 F23-x86_64-CINN-20160512.iso: Unchanged skipping
2016/06/30 12:26:18 B2 bucket FastnetBackup path ISO/Linux/: Waiting for transfers to finish
2016/06/30 12:26:19 CentOS-7-x86_64-Everything-1503-01.iso: Starting upload of large file in 76 chunks (id "4_z1a7a3e18055c9cd955580718_f201ce83af21ba2da_d20160630_m162619_c001_v0001029_t0022")
2016/06/30 12:26:24 CentOS-7-x86_64-Everything-1503-01.iso: Sending chunk 1 length 100663296
2016/06/30 12:26:28
Transferred:     141.140MBytes (11.904MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:       11.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso:  7% done. avg: 5119.8, cur: 2719.2 kByte/s. ETA: 3m42s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 11049.0, cur: 5166.6 kByte/s. ETA: 23m35s

2016/06/30 12:26:38
Transferred:     205.530MBytes (9.404MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:       21.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso: 17% done. avg: 5894.4, cur: 4641.6 kByte/s. ETA: 1m56s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 5202.1, cur: 2652.0 kByte/s. ETA: 45m58s

2016/06/30 12:26:48
Transferred:     282.187MBytes (8.858MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:       31.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso: 29% done. avg: 6568.0, cur: 6223.2 kByte/s. ETA: 1m14s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 3401.9, cur: 1361.2 kByte/s. ETA: 1h29m34s

2016/06/30 12:26:58
Transferred:     424.609MBytes (10.144MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:       41.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso: 51% done. avg: 8621.9, cur: 10718.8 kByte/s. ETA: 29s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 2527.3, cur:  698.7 kByte/s. ETA: 2h54m29s

2016/06/30 12:27:08
Transferred:     715.952MBytes (13.806MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:       51.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso: 97% done. avg: 12948.3, cur: 20190.5 kByte/s. ETA: 0s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 2010.4, cur:  358.6 kByte/s. ETA: 5h39m57s

2016/06/30 12:27:18
Transferred:         732MBytes (11.834MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:      1m1.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso: 100% done. avg: 11033.1, cur: 10962.8 kByte/s. ETA: 0s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 1669.1, cur:  184.1 kByte/s. ETA: 11h2m19s

2016/06/30 12:27:28
Transferred:     737.815MBytes (10.268MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:     1m11.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso: 100% done. avg: 9434.8, cur: 5627.1 kByte/s. ETA: 0s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 1513.3, cur:  369.2 kByte/s. ETA: 5h29m57s

2016/06/30 12:27:28 CentOS-7-x86_64-Everything-1503-01.iso: Received error: unexpected EOF - low level retry 1/10
2016/06/30 12:27:28 CentOS-7-x86_64-Everything-1503-01.iso: Removing failed copy
2016/06/30 12:27:29 CentOS-7-x86_64-Everything-1503-01.iso: Starting upload of large file in 76 chunks (id "4_z1a7a3e18055c9cd955580718_f201ce83af21ba2e1_d20160630_m162729_c001_v0001029_t0013")
2016/06/30 12:27:36 CentOS-7-x86_64-Everything-1503-01.iso: Sending chunk 1 length 100663296
2016/06/30 12:27:38
Transferred:     837.097MBytes (10.226MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:     1m21.8s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso: 100% done. avg: 8240.9, cur: 2888.3 kByte/s. ETA: 0s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 11940.6, cur: 5509.3 kByte/s. ETA: 22m7s

`
The error crash was some IO write error. I am not able to reproduce it. Might have been my mistake with choosing --transfers=40!
When I copy from local (ISO/Linux backblaze:FastnetBackup/Linux) it seems to work:
`2016/06/30 12:29:39 CentOS-7-x86_64-Everything-1503-01.iso: Starting upload of large file in 76 chunks (id "4_z1a7a3e18055c9cd955580718_f20043bd69a6233f9_d20160630_m162939_c001_v0001029_t0044")
2016/06/30 12:29:41 CentOS-7-x86_64-Everything-1503-01.iso: Sending chunk 1 length 100663296
2016/06/30 12:29:47
Transferred:     140.312MBytes (1.552MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:     1m30.4s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso:  6% done. avg:  545.5, cur:  397.4 kByte/s. ETA: 25m24s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 12929.9, cur: 50553.4 kByte/s. ETA: 2m24s

2016/06/30 12:29:57
Transferred:     145.957MBytes (1.454MByte/s)
Errors:                 0
Checks:                 6
Transferred:            0
Elapsed time:     1m40.4s
Transferring:

      CentOS-7-x86_64-Minimal-1503-01.iso:  7% done. avg:  549.0, cur:  323.3 kByte/s. ETA: 30m56s

   CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 5584.6, cur: 25948.6 kByte/s. ETA: 4m41s

`
For some reason the upload to backblaze seems to be very slow at the moment. But I have verified earlier that copying from the local disk works for sure.

Thanks for that!
I can see something odd in the logs
2016/06/30 12:27:28 CentOS-7-x86_64-Everything-1503-01.iso: Received error: unexpected EOF - low level retry 1/10
2016/06/30 12:27:28 CentOS-7-x86_64-Everything-1503-01.iso: Removing failed copy
2016/06/30 12:27:29 CentOS-7-x86_64-Everything-1503-01.iso: Starting upload of large file in 76 chunks

It looked like it retried the whole file, rather than retrying just the chunk which is odd.
I don't think that explains the getting stuck at 100% though - do you have a log of that?

Sadly no logs for the 100% issue.

Figured out what that log means - it means that reading from ACD gave the unexpected EOF error.
Any chance you could try to replicate the issue and get me a log with -v?
Thanks

It seems that the error is not showing up anymore.
However, large file copies still seem to be very slow to B2. Not sure why that is.
The 100% stuck error still appears though.
root@ubuntu-512mb-sfo1-01:~/rclone-v1.30-linux-amd64# ./rclone copy acd:/ISO/Linux backblaze:testbac/test/ -v --stats=10s
2016/07/01 11:39:41 rclone: Version "v1.30" starting with parameters ["./rclone" "copy" "acd:/ISO/Linux" "backblaze:testbac/test/" "-v" "--stats=10s"]
2016/07/01 11:39:43 test: Failed to read metadata: object "test" not found
2016/07/01 11:39:43 Amazon cloud drive root 'ISO/Linux': Modify window not supported
2016/07/01 11:39:43 Amazon cloud drive root 'ISO/Linux': Building file list
2016/07/01 11:39:43 Amazon cloud drive root 'ISO/Linux': Reading ""
2016/07/01 11:39:43 B2 bucket testbac path test/: Building file list
2016/07/01 11:39:43 B2 bucket testbac path test/: Done building file list
2016/07/01 11:39:44 Amazon cloud drive root 'ISO/Linux': Finished reading ""
2016/07/01 11:39:44 Amazon cloud drive root 'ISO/Linux': Done building file list
2016/07/01 11:39:44 B2 bucket testbac path test/: Waiting for checks to finish
2016/07/01 11:39:44 B2 bucket testbac path test/: Waiting for transfers to finish
2016/07/01 11:39:45 CentOS-7-x86_64-Everything-1503-01.iso: Starting upload of large file in 76 chunks (id "4_zaa7ace78156cac7955580718_f200b90fcd31add5b_d20160701_m153945_c001_v0001029_t0017")
2016/07/01 11:39:53
Transferred:     130.240MBytes (10.974MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:       11.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso:  7% done. avg: 10424.0, cur: 4836.7 kByte/s. ETA: 4m4s
 *                 ubuntu-16.04-server-amd64.iso:  0% done. avg:  622.4, cur: 1198.2 kByte/s. ETA: 9m15s
 *                ubuntu-16.04-desktop-amd64.iso:  1% done. avg: 2460.6, cur: 1645.9 kByte/s. ETA: 14m28s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  0% done. avg: 1651.8, cur:  959.9 kByte/s. ETA: 2h8m28s

2016/07/01 11:40:03
Transferred:     435.211MBytes (19.902MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:       21.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 21% done. avg: 14587.7, cur: 11248.3 kByte/s. ETA: 1m28s
 *                 ubuntu-16.04-server-amd64.iso:  1% done. avg:  431.1, cur:  730.5 kByte/s. ETA: 15m7s
 *                ubuntu-16.04-desktop-amd64.iso:  6% done. avg: 4986.8, cur: 4417.5 kByte/s. ETA: 5m6s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  0% done. avg: 3689.7, cur: 3089.0 kByte/s. ETA: 39m37s

2016/07/01 11:40:06 CentOS-7-x86_64-Everything-1503-01.iso: Sending chunk 1 length 100663296
2016/07/01 11:40:13
Transferred:     738.761MBytes (23.181MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:       31.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 34% done. avg: 15018.3, cur: 13649.4 kByte/s. ETA: 1m1s
 *                 ubuntu-16.04-server-amd64.iso:  8% done. avg: 1960.6, cur: 2756.1 kByte/s. ETA: 3m43s
 *                ubuntu-16.04-desktop-amd64.iso: 11% done. avg: 5847.6, cur: 5949.2 kByte/s. ETA: 3m35s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 3445.9, cur: 2947.0 kByte/s. ETA: 41m22s

2016/07/01 11:40:23
Transferred:       1.086GBytes (26.568MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:       41.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 48% done. avg: 15913.0, cur: 16097.9 kByte/s. ETA: 40s
 *                 ubuntu-16.04-server-amd64.iso: 22% done. avg: 3982.9, cur: 6341.4 kByte/s. ETA: 1m21s
 *                ubuntu-16.04-desktop-amd64.iso: 18% done. avg: 6935.1, cur: 8125.5 kByte/s. ETA: 2m25s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 2552.0, cur: 1512.7 kByte/s. ETA: 1h20m36s

2016/07/01 11:40:33
Transferred:       1.538GBytes (30.357MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:       51.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 64% done. avg: 16755.2, cur: 18214.3 kByte/s. ETA: 24s
 *                 ubuntu-16.04-server-amd64.iso: 35% done. avg: 4882.8, cur: 7393.5 kByte/s. ETA: 58s
 *                ubuntu-16.04-desktop-amd64.iso: 30% done. avg: 9081.8, cur: 12738.2 kByte/s. ETA: 1m18s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  1% done. avg: 2332.1, cur: 1476.2 kByte/s. ETA: 1h22m25s

2016/07/01 11:40:38 CentOS-7-x86_64-Everything-1503-01.iso: Sending chunk 2 length 100663296
2016/07/01 11:40:43
Transferred:       1.970GBytes (32.602MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      1m1.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 73% done. avg: 15924.2, cur: 15108.9 kByte/s. ETA: 22s
 *                 ubuntu-16.04-server-amd64.iso: 50% done. avg: 5803.5, cur: 8805.1 kByte/s. ETA: 37s
 *                ubuntu-16.04-desktop-amd64.iso: 40% done. avg: 10064.0, cur: 13639.6 kByte/s. ETA: 1m2s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  2% done. avg: 3359.5, cur: 4469.1 kByte/s. ETA: 26m54s

2016/07/01 11:40:53
Transferred:       2.432GBytes (34.651MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     1m11.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 85% done. avg: 15793.8, cur: 15176.8 kByte/s. ETA: 12s
 *                 ubuntu-16.04-server-amd64.iso: 75% done. avg: 7458.5, cur: 12925.6 kByte/s. ETA: 12s
 *                ubuntu-16.04-desktop-amd64.iso: 52% done. avg: 10973.5, cur: 15021.5 kByte/s. ETA: 46s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  2% done. avg: 2869.3, cur: 2293.9 kByte/s. ETA: 52m26s

2016/07/01 11:41:03
Transferred:       2.899GBytes (36.252MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     1m21.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 99% done. avg: 16052.6, cur: 16579.1 kByte/s. ETA: 0s
 *                 ubuntu-16.04-server-amd64.iso: 99% done. avg: 8513.9, cur: 14255.8 kByte/s. ETA: 0s
 *                ubuntu-16.04-desktop-amd64.iso: 62% done. avg: 11525.2, cur: 15057.3 kByte/s. ETA: 35s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  2% done. avg: 2503.6, cur: 1177.5 kByte/s. ETA: 1h42m9s

2016/07/01 11:41:12 CentOS-7-x86_64-Everything-1503-01.iso: Sending chunk 3 length 100663296
2016/07/01 11:41:13
Transferred:       3.100GBytes (34.553MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     1m31.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 100% done. avg: 14329.9, cur: 9188.8 kByte/s. ETA: 0s
 *                 ubuntu-16.04-server-amd64.iso: 100% done. avg: 7601.8, cur: 7605.6 kByte/s. ETA: 0s
 *                ubuntu-16.04-desktop-amd64.iso: 69% done. avg: 11366.5, cur: 12566.8 kByte/s. ETA: 34s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  3% done. avg: 3331.4, cur: 5843.8 kByte/s. ETA: 20m18s

2016/07/01 11:41:23
Transferred:       3.237GBytes (32.536MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     1m41.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 100% done. avg: 12880.7, cur: 4716.5 kByte/s. ETA: 0s
 *                 ubuntu-16.04-server-amd64.iso: 100% done. avg: 6828.4, cur: 3903.9 kByte/s. ETA: 0s
 *                ubuntu-16.04-desktop-amd64.iso: 79% done. avg: 11665.8, cur: 13577.3 kByte/s. ETA: 21s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  3% done. avg: 2993.5, cur: 2999.5 kByte/s. ETA: 39m33s

2016/07/01 11:42:55 CentOS-7-x86_64-Everything-1503-01.iso: Sending chunk 6 length 100663296
2016/07/01 11:43:03
Transferred:       3.800GBytes (19.274MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     3m21.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 100% done. avg: 6401.8, cur:    6.0 kByte/s. ETA: 0s
 *                 ubuntu-16.04-server-amd64.iso: 100% done. avg: 3383.5, cur:    5.0 kByte/s. ETA: 0s
 *                ubuntu-16.04-desktop-amd64.iso: 100% done. avg: 7289.7, cur:   63.9 kByte/s. ETA: 0s
 *        CentOS-7-x86_64-Everything-1503-01.iso:  7% done. avg: 2971.0, cur: 3139.6 kByte/s. ETA: 36m13s

Looks like if I wait long enough, it eventually finishes the 100% thing:
2016/07/01 11:44:13
Transferred:       3.987GBytes (15.018MByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     4m31.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 100% done. avg: 4734.8, cur:    0.1 kByte/s. ETA: 0s
 *                 ubuntu-16.04-server-amd64.iso: 100% done. avg: 2500.5, cur:    0.0 kByte/s. ETA: 0s
 *                ubuntu-16.04-desktop-amd64.iso: 100% done. avg: 5393.1, cur:    0.6 kByte/s. ETA: 0s
 *        CentOS-7-x86_64-Everything-1503-01.iso: 10% done. avg: 2928.7, cur: 2077.2 kByte/s. ETA: 53m10s

2016/07/01 11:44:18 ubuntu-16.04-server-amd64.iso: Copied (new)
2016/07/01 11:44:23
Transferred:       4.113GBytes (14.941MByte/s)
Errors:                 0
Checks:                 0
Transferred:            1
Elapsed time:     4m41.8s
Transferring:
 *                  F23-x86_64-CINN-20160512.iso: 100% done. avg: 4565.0, cur:    0.0 kByte/s. ETA: 0s
 *                 CentOS-7-x86_64-LiveGNOME.iso:  4% done. avg: 12823.2, cur: 3940.1 kByte/s. ETA: 4m48s
 *                ubuntu-16.04-desktop-amd64.iso: 100% done. avg: 5200.0, cur:    0.3 kByte/s. ETA: 0s
 *        CentOS-7-x86_64-Everything-1503-01.iso: 11% done. avg: 3107.6, cur: 4957.6 kByte/s.  ETA: 0s
 *                 CentOS-7-x86_64-LiveGNOME.iso: 14% done. avg: 12383.3, cur: 7767.7 kByte/s. ETA: 2m10s
 *        CentOS-7-x86_64-Everything-1503-01.iso: 11% done. avg: 3066.4, cur: 3726.4 kByte/s. ETA: 29m12s
 *      Fedora-Live-Workstation-x86_64-23-10.iso:  1% done. avg: 4773.4, cur: 1649.7 kByte/s. ETA: 14m20s

I've realised this is the same issue as #/587 - it is to do with the internal buffering on large file uploads for B2.  We read the file into memory in 96MB chunks very quickly - then while we upload the last of these chunks the transfer speed drops to 0.
You can see from the Transferred:       3.100GBytes (34.553MByte/s) lines that everything is proceeding properly.
@klauspost we discussed this before didn't we - did we ever make an issue about it?

That makes sense.
So would changing the chunk size make this issue more tolerable?

It is purely a display problem - the transfer is happening properly. Unfortunately rclone already uses the minimum chunk size so you can't make it smaller (which would help).
One thing you could try is to set a --bwlimit of about the capacity of your Internet connection - that will probably work.
I need to think of a better way of accounting the transfers so they display properly in this case.

The display problem was fixed as part of #602 and is now in the v1.33 release!


Document Code in C# Scripts

Scope
We need to document all the code in the files inside Assets/Scripts path
To do:

Understand the all the code/classes/methods/functions in the files and their conecctions with other classes in other scripts
Document these files in a format similar to JavaDoc for example, but for C# scripts.
Explain what each class, each method, each function, each flow control, etc. does. We need to have all these scripts fully documented.

How to apply?
Please follow the contribution guidelines in the readme file

Hi @jimenezz22  can I work on this?
I'm a frontend and smart contract developer and I'd love to contribute to this project.
Here are the links to some comprehensive documentations I've contributed here on onlydust that have also been merged: https://github.com/Flex-NFT-Marketplace/Flex-Marketplace-Contract/pull/107,
https://github.com/sivicstudio/starkludo/pull/102,
https://github.com/horuslabsio/tokenbound-contract-docs/pull/12

@jimenezz22,
I am a developer with some expirence in build programs using C programming language. In addition to building programs, I am also an experienced Technical writer and have contribute to several technical documents on the ODhack platform and other side the ODhack platform. Below are some of my previous merged document:
Tokenbound-contract, cairo-book, About Etherscan
kindly assign

Hi @NueloSE @Iwueseiter
thank you for your interests to contribute to ByteBeats, we will start assigning issues when the ODHack 9 starts on October 24 and issues will be assigned through OnlyDust

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hi! I’m Anwar a Software Developer with +3 years of experience, and I would love
continue making contribution to this project
I'm also a member of the Dojo Coding community From CR.
How I plan on tackling this issue
I will carefully go through each file, class, method, and function, and identify how they connect with other scripts and components.
I will explain:
What the class is responsible for.
The purpose of each method and its parameters.
The logic behind flow controls
The documentation will ensure that the entire structure is clear and concise, making the code easier to understand and maintain.
For reference, I have experience in documenting projects, including my contribution to Horus Labs Tokenbound Contract Docs, and I have worked on documentation tasks in ByteBeastsBackend.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have vast experience producing clear, comprehensive documentation in both JavaScript and C#. My expertise with C# development has given me a solid understanding of object-oriented programming ideas and documentation guidelines.
:)
How I plan on tackling this issue
For this documentation work, I would first go through all of the scripts in the Assets/Scripts directory to understand their functionality and linkages. I'd use C# XML documentation comments to describe classes, methods, and properties, assuring IntelliSense compatibility. I would focus on documenting method arguments, return values, and class relationships in C#, comparable to JavaDoc approach.  I would be excited if i am granted to work on this task :)

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
ello @ i'm a frontend developer and an experienced technical writer i would love to work on this issue
Pleasee kindly assign :)

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello can I be assigned this please? I am a blockchain developer and I'm also good at documentations. Below are some of the documentations I've done that were merged:
https://github.com/dojoengine/book/pull/308,
https://github.com/keep-starknet-strange/joyboy/pull/143,
https://github.com/Scaffold-Stark/ss2-docs/pull/31,
https://github.com/horuslabsio/Starknet-Scaffold/pull/94,
https://github.com/Hyle-org/examples/pull/15,
https://github.com/Hyle-org/examples/pull/16,
https://github.com/horuslabsio/tokenbound-contract-docs/pull/11.
How I plan on tackling this issue
Here are some documentations I did that were merged:ByteBuildersLabs/ ByteBeastsFrontend #96
Hello can I be assigned this please? I am a blockchain developer and I'm also good at documentations. Below are some of the documentations I've done that were merged:
https://github.com/dojoengine/book/pull/308,
https://github.com/keep-starknet-strange/joyboy/pull/143,
To write a comprehensive and correctly formatted documentation:

I’ll start by carefully reviewing each C# file inside the Assets/Scripts directory, to understand how each class, method, or function interacts with others, noting dependencies, inheritance, and flow control.
I’ll make sure to add comments, and tags like , , and  to explain functionality.
I’ll run a build and check if all tooltips and comments are properly displayed in my IDE.

Please I’m ready to work, assign me please.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i have experience in game dev as well as blockchain previously as personal projects and OS, so hoping to make use of them here and mark my first odhack contribution
How I plan on tackling this issue
let me put my documentation skills to use

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hey guys, Bruno here from the dojo coding community. I´ve been working for the past 4 years with c# and in big companies like the one Im right one (Mercado Libre) so I have encountered a lot of documentation.
How I plan on tackling this issue
I would read the current docs and all the code that needs to be documented and understand what each class, function, etc... works.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have a strong background in C# development, which includes extensive experience in understanding complex code structures and effectively documenting them. My expertise in programming standards enables me to provide clear, concise, and comprehensive documentation that enhances code maintainability and facilitates easier onboarding for new contributors.
How I plan on tackling this issue
To document the code in the Assets/Scripts directory, I will thoroughly review each script to understand its functionality and interactions. I will use a JavaDoc-like format tailored for C#, providing detailed explanations for each class, method, and flow control. Consistency in style and terminology will be prioritized, and I will seek feedback from maintainers to ensure accuracy and completeness. This approach will create clear and valuable documentation for current and future contributors.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hi!, my name is Joseph Poveda.
I am a student of the Systems Programming degree, I am a recent member of the Dojo Coding community, where I am getting started in the world of Web3.
I have basic knowledge of different programming languages and thanks to this I hope to be able to resolve the issue.
How I plan on tackling this issue
To address the problem, I would start by reading the Redme, a step that I have taken, because in previous days I was studying the project to understand it in a better way, after this I would understand each section of the code to see how it works and with this document it, so that it is more understandable.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I started my programming career as Java developer. I have a very strong background in object oriented programming and writing professional code documentations.
Am also a frontend Developer, smart contract developer and technical writer. Am familiar with c# syntax and deeply understand its object oriented programming approach. I have written several technical articles. I have written a succefully merged documentation in OD hack. I can write professional code documentations for your c# program similar to JavaDoc for Java programs.
How I plan on tackling this issue
My first approach in writing a professional documentation for this task would be to understand the code/classes/methods/functions in the files and their connections with other classes in other scripts. This would help me breakdown and understand every class, each method, each function, each flow control, etc. in the code base. After a detailed understanding of the code base i would write a simple, clear, concise and professional documentation that a 12 year old can read and understand.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello
I am a software engineer from Costa Rica and a member of Dojo Coding. I am new to the community. I have worked with technologies such as JavaScript, Node.js, PHP, Java, C#, Typescript. I also have basic knowledge of using git. I would love to have the opportunity to help with this problem and contribute to your project.
How I plan on tackling this issue

Understand the Code
To create excellent code documentation, I think the key is to understand the code, know the purpose of the classes and methods that were implemented, and understand the flow control, identify control structures such as loops, conditionals, etc., and how it affects the overall behavior of the system.

Add Comments
The next thing to do is add comments to the classes with a brief description of what they represent and what they do. After that, the description of the variables is done. Regarding the control flows (such as loops, conditionals, etc.), a brief description of what they do is done, and what the conditions are for a loop to start or end, for example. And finally, comments on class connections, if a class or method is related to another class or script, add explanations in the comments to clarify these connections.

Recommendation Some considerations to take with the documentation, I have seen documentation that is done in XML style to follow a standard.

Personally, it can take 2 to 5 days to complete a well-done documentation depending on the project's completion
.
We look forward to receiving your comments!
Kind regards, Yarex Espinoza Naranjo.

I'm a javascript dev. A new-comer here, willing and ready to contribute to solve the issue.

I’d like to help with this.
I have strong research skills (5+ years) in computer engineering works, which makes a suitable candidate for this role. I

gm @NueloSE assigned to you

gm @NueloSE any updates?

gm @jimenezz22 making a PR today.


✨Implement the following queries relating to a client

cc @adamcogan, @AttackOnMorty, @pierssinclairssw @brydeno
Hi @jimmidier,
As per the screenshot below, I tried to query about the client “Northwind” but the bot couldn’t find any results.

[ ] Please investigate
[ ] I would like the following questions/queries to work

Tell me about Northwind?
Tell me about the client Northwind?
Tell me about the project Northwind?
Who works on Northwind?

Figure: chatlog with SophieBot in relation to the client Northwind

Jim,
I wouldn't think of this as a bug. The requirements you were implementing were fulfilled. Jack has just suggested some new features.

Jim, I wouldn't think of this as a bug. The requirements you were implementing were fulfilled. Jack has just suggested some new features.

Hi @brydeno
Thanks for the note. Jack has suggested some new features in the sample queries list, but I've also received bugs from the screenshot he posted

cc @AttackOnMorty
As per the comments above,
Tasks

[ ] Please investigate
[ ] I would like the following questions/queries to work

Tell me about Northwind?
Tell me about the client Northwind?
Tell me about the project Northwind?
Who works on Northwind?
Who will be working for Campion?

[ ] Improve LUIS model to improve the answers for the four queries in the screenshot above

tell me about [the (client | project)]Northwind
who works on Northwind